From 73bb4562ed5724f1694ce7f0efb61854d0fdef5a Mon Sep 17 00:00:00 2001 From: zammad-sync Date: Wed, 13 Nov 2024 14:30:35 +0100 Subject: [PATCH] Maintenance: Translations update from translations.zammad.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Special thanks to the amazing translation team. You rock! 💪 Co-authored-by: Weblate --- locale/cs/LC_MESSAGES/admin-docs.po | 13708 ++++++------ locale/da/LC_MESSAGES/admin-docs.po | 13680 ++++++------ locale/de/LC_MESSAGES/admin-docs.po | 22977 +++++++++++---------- locale/es/LC_MESSAGES/admin-docs.po | 14527 +++++++------ locale/es_CO/LC_MESSAGES/admin-docs.po | 13680 ++++++------ locale/es_MX/LC_MESSAGES/admin-docs.po | 13680 ++++++------ locale/fa/LC_MESSAGES/admin-docs.po | 13680 ++++++------ locale/fr/LC_MESSAGES/admin-docs.po | 14133 +++++++------ locale/fr_CA/LC_MESSAGES/admin-docs.po | 15120 +++++++------- locale/hr/LC_MESSAGES/admin-docs.po | 13776 ++++++------ locale/hu/LC_MESSAGES/admin-docs.po | 13680 ++++++------ locale/it/LC_MESSAGES/admin-docs.po | 13706 ++++++------ locale/nl/LC_MESSAGES/admin-docs.po | 13680 ++++++------ locale/pl/LC_MESSAGES/admin-docs.po | 13775 ++++++------ locale/pt_BR/LC_MESSAGES/admin-docs.po | 14440 +++++++------ locale/ru/LC_MESSAGES/admin-docs.po | 13708 ++++++------ locale/sr/LC_MESSAGES/admin-docs.po | 22143 ++++++++++---------- locale/sv/LC_MESSAGES/admin-docs.po | 13716 ++++++------ locale/th/LC_MESSAGES/admin-docs.po | 13680 ++++++------ locale/tr/LC_MESSAGES/admin-docs.po | 16879 ++++++++------- locale/zh_Hans/LC_MESSAGES/admin-docs.po | 13750 ++++++------ 21 files changed, 154957 insertions(+), 157161 deletions(-) diff --git a/locale/cs/LC_MESSAGES/admin-docs.po b/locale/cs/LC_MESSAGES/admin-docs.po index 156c0dce..ee6a14c9 100644 --- a/locale/cs/LC_MESSAGES/admin-docs.po +++ b/locale/cs/LC_MESSAGES/admin-docs.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Zammad\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-11-06 10:31+0100\n" +"POT-Creation-Date: 2024-11-12 16:31+0100\n" "PO-Revision-Date: 2023-09-23 01:11+0000\n" "Last-Translator: Tomáš Kovařík \n" "Language-Team: Czech Checklist `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:56 msgid "``admin.channel_email``" msgstr "" -#: ../manage/roles/admin-permissions.rst:54 #: ../manage/roles/admin-permissions.rst:57 msgid ":doc:`Channels > Email `" msgstr "" -#: ../manage/roles/admin-permissions.rst:56 #: ../manage/roles/admin-permissions.rst:59 msgid "``admin.channel_facebook``" msgstr "" -#: ../manage/roles/admin-permissions.rst:57 #: ../manage/roles/admin-permissions.rst:60 msgid ":doc:`Channels > Facebook `" msgstr "" -#: ../manage/roles/admin-permissions.rst:58 #: ../manage/roles/admin-permissions.rst:61 msgid "" "Accessing Facebook tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:59 #: ../manage/roles/admin-permissions.rst:62 msgid "``admin.channel_formular``" msgstr "" -#: ../manage/roles/admin-permissions.rst:60 #: ../manage/roles/admin-permissions.rst:63 msgid ":doc:`Channels > Form `" msgstr "" -#: ../manage/roles/admin-permissions.rst:62 #: ../manage/roles/admin-permissions.rst:65 msgid "``admin.channel_google``" msgstr "" -#: ../manage/roles/admin-permissions.rst:63 #: ../manage/roles/admin-permissions.rst:66 msgid ":doc:`Channels > Google `" msgstr "" -#: ../manage/roles/admin-permissions.rst:65 #: ../manage/roles/admin-permissions.rst:68 msgid "``admin.channel_microsoft365``" msgstr "" -#: ../manage/roles/admin-permissions.rst:66 #: ../manage/roles/admin-permissions.rst:69 msgid ":doc:`Channels > Microsoft 365 `" msgstr "" -#: ../manage/roles/admin-permissions.rst:68 #: ../manage/roles/admin-permissions.rst:71 msgid "``admin.channel_sms``" msgstr "" -#: ../manage/roles/admin-permissions.rst:69 #: ../manage/roles/admin-permissions.rst:72 msgid ":doc:`Channels > SMS `" msgstr "" -#: ../manage/roles/admin-permissions.rst:71 #: ../manage/roles/admin-permissions.rst:74 msgid "``admin.channel_telegram``" msgstr "" -#: ../manage/roles/admin-permissions.rst:72 #: ../manage/roles/admin-permissions.rst:75 msgid ":doc:`Channels > Telegram `" msgstr "" -#: ../manage/roles/admin-permissions.rst:73 #: ../manage/roles/admin-permissions.rst:76 msgid "" "Accessing Telegram tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:74 #: ../manage/roles/admin-permissions.rst:77 msgid "``admin.channel_twitter``" msgstr "" -#: ../manage/roles/admin-permissions.rst:75 #: ../manage/roles/admin-permissions.rst:78 msgid ":doc:`Channels > Twitter `" msgstr "" -#: ../manage/roles/admin-permissions.rst:76 #: ../manage/roles/admin-permissions.rst:79 msgid "" "Accessing Twitter/X tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:77 #: ../manage/roles/admin-permissions.rst:80 msgid "``admin.channel_web``" msgstr "" -#: ../manage/roles/admin-permissions.rst:78 #: ../manage/roles/admin-permissions.rst:81 msgid ":doc:`Channels > Web `" msgstr "" -#: ../manage/roles/admin-permissions.rst:80 +#: ../manage/roles/admin-permissions.rst:83 +msgid "``admin.channel_whatsapp``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:84 +msgid ":doc:`Channels > Whatsapp `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:86 msgid "``admin.core_workflows``" msgstr "" -#: ../manage/roles/admin-permissions.rst:81 #: ../manage/roles/admin-permissions.rst:87 msgid ":doc:`System > Core Workflows `" msgstr "" -#: ../manage/roles/admin-permissions.rst:83 #: ../manage/roles/admin-permissions.rst:89 msgid "``admin.data_privacy``" msgstr "" -#: ../manage/roles/admin-permissions.rst:84 #: ../manage/roles/admin-permissions.rst:90 msgid ":doc:`System > Data Privacy `" msgstr "" -#: ../manage/roles/admin-permissions.rst:85 #: ../manage/roles/admin-permissions.rst:91 msgid "" "🔥 Be careful, it allows users to permanently delete data on the system." msgstr "" -#: ../manage/roles/admin-permissions.rst:86 #: ../manage/roles/admin-permissions.rst:92 msgid "``admin.group``" msgstr "" -#: ../manage/roles/admin-permissions.rst:87 #: ../manage/roles/admin-permissions.rst:93 msgid ":doc:`Manage > Groups `" msgstr "" -#: ../manage/roles/admin-permissions.rst:89 #: ../manage/roles/admin-permissions.rst:95 msgid "``admin.integration``" msgstr "" -#: ../manage/roles/admin-permissions.rst:90 #: ../manage/roles/admin-permissions.rst:96 msgid ":doc:`System > Integrations `" msgstr "" -#: ../manage/roles/admin-permissions.rst:92 #: ../manage/roles/admin-permissions.rst:98 msgid "``admin.knowledge_base``" msgstr "" -#: ../manage/roles/admin-permissions.rst:93 #: ../manage/roles/admin-permissions.rst:99 msgid ":doc:`Manage > Knowledge Base `" msgstr "" @@ -8564,57 +8547,46 @@ msgid "" "knowledge-base.html#editing-answers>`." msgstr "" -#: ../manage/roles/admin-permissions.rst:98 #: ../manage/roles/admin-permissions.rst:104 msgid "``admin.macro``" msgstr "" -#: ../manage/roles/admin-permissions.rst:99 #: ../manage/roles/admin-permissions.rst:105 msgid ":doc:`Manage > Macros `" msgstr "" -#: ../manage/roles/admin-permissions.rst:100 #: ../manage/roles/admin-permissions.rst:106 msgid "In some cases, macros may also require ``admin.tag``" msgstr "" -#: ../manage/roles/admin-permissions.rst:101 #: ../manage/roles/admin-permissions.rst:107 msgid "``admin.maintenance``" msgstr "" -#: ../manage/roles/admin-permissions.rst:102 #: ../manage/roles/admin-permissions.rst:108 msgid ":doc:`System > Maintenance `" msgstr "" -#: ../manage/roles/admin-permissions.rst:104 #: ../manage/roles/admin-permissions.rst:110 msgid "``admin.monitoring``" msgstr "" -#: ../manage/roles/admin-permissions.rst:105 #: ../manage/roles/admin-permissions.rst:111 msgid ":doc:`System > Monitoring `" msgstr "" -#: ../manage/roles/admin-permissions.rst:107 #: ../manage/roles/admin-permissions.rst:113 msgid "``admin.object``" msgstr "" -#: ../manage/roles/admin-permissions.rst:108 #: ../manage/roles/admin-permissions.rst:114 msgid ":doc:`System > Objects `" msgstr "" -#: ../manage/roles/admin-permissions.rst:110 #: ../manage/roles/admin-permissions.rst:116 msgid "``admin.organization``" msgstr "" -#: ../manage/roles/admin-permissions.rst:111 #: ../manage/roles/admin-permissions.rst:117 msgid ":doc:`Manage > Organizations `" msgstr "" @@ -8631,202 +8603,210 @@ msgstr "" msgid "They can even edit an organization's name, domain, and notes!" msgstr "" -#: ../manage/roles/admin-permissions.rst:115 #: ../manage/roles/admin-permissions.rst:121 msgid "``admin.overview``" msgstr "" -#: ../manage/roles/admin-permissions.rst:116 #: ../manage/roles/admin-permissions.rst:122 msgid ":doc:`Manage > Overviews`" msgstr "" -#: ../manage/roles/admin-permissions.rst:118 +#: ../manage/roles/admin-permissions.rst:124 +msgid "``admin.public_links``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:125 +msgid ":doc:`Manage > Public Links `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:127 msgid "``admin.package``" msgstr "" -#: ../manage/roles/admin-permissions.rst:119 #: ../manage/roles/admin-permissions.rst:128 msgid ":doc:`System > Packages `" msgstr "" -#: ../manage/roles/admin-permissions.rst:121 #: ../manage/roles/admin-permissions.rst:130 msgid "``admin.report_profile``" msgstr "" -#: ../manage/roles/admin-permissions.rst:122 #: ../manage/roles/admin-permissions.rst:131 msgid ":doc:`Manage > Report Profiles `" msgstr "" -#: ../manage/roles/admin-permissions.rst:123 #: ../manage/roles/admin-permissions.rst:132 msgid "Access to view reports: ``report``" msgstr "" -#: ../manage/roles/admin-permissions.rst:124 #: ../manage/roles/admin-permissions.rst:133 msgid "``admin.role``" msgstr "" -#: ../manage/roles/admin-permissions.rst:125 #: ../manage/roles/admin-permissions.rst:134 msgid ":doc:`Manage > Roles `" msgstr "" -#: ../manage/roles/admin-permissions.rst:127 #: ../manage/roles/admin-permissions.rst:136 msgid "``admin.scheduler``" msgstr "" -#: ../manage/roles/admin-permissions.rst:128 #: ../manage/roles/admin-permissions.rst:137 msgid ":doc:`Manage > Scheduler `" msgstr "" -#: ../manage/roles/admin-permissions.rst:129 #: ../manage/roles/admin-permissions.rst:138 msgid "For automation on tickets" msgstr "" -#: ../manage/roles/admin-permissions.rst:130 #: ../manage/roles/admin-permissions.rst:139 msgid "``admin.security``" msgstr "" -#: ../manage/roles/admin-permissions.rst:131 #: ../manage/roles/admin-permissions.rst:140 msgid ":doc:`Settings > Security `" msgstr "" -#: ../manage/roles/admin-permissions.rst:132 #: ../manage/roles/admin-permissions.rst:141 msgid "Settings of Zammad. This also covers third party authentications." msgstr "" -#: ../manage/roles/admin-permissions.rst:133 #: ../manage/roles/admin-permissions.rst:142 msgid "``admin.session``" msgstr "" -#: ../manage/roles/admin-permissions.rst:134 #: ../manage/roles/admin-permissions.rst:143 msgid ":doc:`System > Sessions `" msgstr "" -#: ../manage/roles/admin-permissions.rst:136 #: ../manage/roles/admin-permissions.rst:145 msgid "``admin.setting_system``" msgstr "" -#: ../manage/roles/admin-permissions.rst:137 #: ../manage/roles/admin-permissions.rst:146 msgid ":doc:`Settings > System `" msgstr "" -#: ../manage/roles/admin-permissions.rst:139 #: ../manage/roles/admin-permissions.rst:148 msgid "``admin.sla``" msgstr "" -#: ../manage/roles/admin-permissions.rst:140 #: ../manage/roles/admin-permissions.rst:149 msgid ":doc:`Manage > SLAs `" msgstr "" -#: ../manage/roles/admin-permissions.rst:142 +#: ../manage/roles/admin-permissions.rst:151 +msgid "``admin.system_report``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:152 +msgid ":doc:`System > System Report `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:154 msgid "``admin.tag``" msgstr "" -#: ../manage/roles/admin-permissions.rst:143 #: ../manage/roles/admin-permissions.rst:155 msgid ":doc:`Manage > Tags `" msgstr "" -#: ../manage/roles/admin-permissions.rst:145 #: ../manage/roles/admin-permissions.rst:157 msgid "``admin.template``" msgstr "" -#: ../manage/roles/admin-permissions.rst:146 #: ../manage/roles/admin-permissions.rst:158 msgid ":doc:`Manage > Templates `" msgstr "" -#: ../manage/roles/admin-permissions.rst:148 #: ../manage/roles/admin-permissions.rst:160 msgid "``admin.text_module``" msgstr "" -#: ../manage/roles/admin-permissions.rst:149 #: ../manage/roles/admin-permissions.rst:161 msgid ":doc:`Manage > Text Modules `" msgstr "" -#: ../manage/roles/admin-permissions.rst:151 #: ../manage/roles/admin-permissions.rst:163 msgid "``admin.ticket``" msgstr "" -#: ../manage/roles/admin-permissions.rst:152 #: ../manage/roles/admin-permissions.rst:164 msgid ":doc:`Settings > Tickets `" msgstr "" -#: ../manage/roles/admin-permissions.rst:153 #: ../manage/roles/admin-permissions.rst:165 msgid "Does not grant access to :doc:`/misc/composer`" msgstr "" -#: ../manage/roles/admin-permissions.rst:154 +#: ../manage/roles/admin-permissions.rst:166 +msgid "``admin.ticket_auto_assignment``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:167 +msgid ":ref:`Settings > Ticket > Auto Assignment `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:169 +msgid "``admin.ticket_duplicate_detection``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:170 +msgid ":ref:`Settings > Ticket > Duplicate Detection `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:172 +msgid "``admin.ticket_priority``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:173 +msgid ":ref:`System > Objects >Ticket Priority `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:175 +msgid "``admin.ticket_state``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:176 +msgid ":ref:`System > Objects >Ticket State `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:178 msgid "``admin.time_accounting``" msgstr "" -#: ../manage/roles/admin-permissions.rst:155 #: ../manage/roles/admin-permissions.rst:179 msgid ":doc:`Manage > Time Accounting `" msgstr "" -#: ../manage/roles/admin-permissions.rst:156 #: ../manage/roles/admin-permissions.rst:180 msgid "Also allows the export of timekeeping records." msgstr "" -#: ../manage/roles/admin-permissions.rst:157 #: ../manage/roles/admin-permissions.rst:181 msgid "``admin.translation``" msgstr "" -#: ../manage/roles/admin-permissions.rst:158 #: ../manage/roles/admin-permissions.rst:182 msgid ":doc:`System > Translations `" msgstr "" -#: ../manage/roles/admin-permissions.rst:159 #: ../manage/roles/admin-permissions.rst:183 msgid "Also enables inline translation" msgstr "" -#: ../manage/roles/admin-permissions.rst:160 #: ../manage/roles/admin-permissions.rst:184 msgid "``admin.trigger``" msgstr "" -#: ../manage/roles/admin-permissions.rst:161 #: ../manage/roles/admin-permissions.rst:185 msgid ":doc:`Manage > Triggers `" msgstr "" -#: ../manage/roles/admin-permissions.rst:163 #: ../manage/roles/admin-permissions.rst:187 msgid "``admin.user``" msgstr "" -#: ../manage/roles/admin-permissions.rst:164 #: ../manage/roles/admin-permissions.rst:188 msgid ":doc:`Manage > Users `" msgstr "" @@ -8845,6 +8825,14 @@ msgid "" "from-users-perspective>` ." msgstr "" +#: ../manage/roles/admin-permissions.rst:193 +msgid "``admin.webhook``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:194 +msgid ":doc:`Manage > Webhook `" +msgstr "" + #: ../manage/roles/agent-permissions.rst:2 msgid "Agent Permissions" msgstr "" @@ -9264,36 +9252,45 @@ msgid "than the user that generated them." msgstr "" #: ../manage/roles/user-preferences-permissions.rst:43 +msgid "``user_preferences.appearance``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:44 +msgid "Appearance configuration" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "Users can switch between dark, light and" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "automatic mode." +msgstr "" + #: ../manage/roles/user-preferences-permissions.rst:47 msgid "``user_preferences.avatar``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:44 #: ../manage/roles/user-preferences-permissions.rst:48 msgid "Avatar settings" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:45 #: ../manage/roles/user-preferences-permissions.rst:49 msgid "Override the default Gravatar with a custom avatar" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:46 #: ../manage/roles/user-preferences-permissions.rst:50 msgid "``user_preferences.calendar``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:47 #: ../manage/roles/user-preferences-permissions.rst:51 msgid "Configure the calendar feed" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:49 #: ../manage/roles/user-preferences-permissions.rst:53 msgid "``user_preferences.device``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:50 #: ../manage/roles/user-preferences-permissions.rst:54 msgid "Manage device login sessions" msgstr "" @@ -9310,22 +9307,18 @@ msgstr "" msgid "To learn more, see :doc:`/manage/trigger/system-notifications`." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:54 #: ../manage/roles/user-preferences-permissions.rst:58 msgid "``user_preferences.language``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:55 #: ../manage/roles/user-preferences-permissions.rst:59 msgid "Configure the UI locale/language" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:57 #: ../manage/roles/user-preferences-permissions.rst:61 msgid "``user_preferences.linked_accounts``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:58 #: ../manage/roles/user-preferences-permissions.rst:62 msgid "Account linking" msgstr "" @@ -9349,7 +9342,6 @@ msgstr "" msgid "is the only way users can utilize third-party logins." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:63 #: ../manage/roles/user-preferences-permissions.rst:67 msgid "``user_preferences.notifications``" msgstr "" @@ -9377,7 +9369,6 @@ msgstr "" msgid "Customers can't receive ticket notifications at all." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:69 #: ../manage/roles/user-preferences-permissions.rst:73 msgid "``user_preferences.out_of_office``" msgstr "" @@ -9402,7 +9393,6 @@ msgstr "" msgid "they're replacing." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:75 #: ../manage/roles/user-preferences-permissions.rst:79 msgid "``user_preferences.overview_sorting``" msgstr "" @@ -9431,12 +9421,10 @@ msgstr "" msgid "overviews has no effect on custom orders." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:82 #: ../manage/roles/user-preferences-permissions.rst:86 msgid "``user_preferences.password``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:83 #: ../manage/roles/user-preferences-permissions.rst:87 msgid "Change account password" msgstr "" @@ -9453,7 +9441,6 @@ msgstr "" msgid "your only allowed authentication method." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:87 #: ../manage/roles/user-preferences-permissions.rst:91 msgid "``user_preferences.two_factor_authentication``" msgstr "" @@ -9490,7 +9477,7 @@ msgstr "" #: ../manage/scheduler.rst:19 msgid "" -"Schedulers can be used to send periodic reminder emails. Use :doc:`/system/" +"Schedulers can be used to send periodic reminder emails. Use :doc:`/misc/" "variables` to build highly-customized email templates." msgstr "" @@ -10486,7 +10473,7 @@ msgstr "" #: ../manage/text-modules.rst:57 msgid "" -"The example text modules below use :doc:`/system/variables` to dynamically " +"The example text modules below use :doc:`/misc/variables` to dynamically " "insert information like the customer's or agent's names." msgstr "" @@ -10826,8 +10813,8 @@ msgstr "" #: ../misc/object-conditions/basics.rst:144 #: ../misc/object-conditions/basics.rst:160 #: ../misc/object-conditions/basics.rst:168 -#: ../misc/object-conditions/basics.rst:178 ../settings/ticket.rst:2 -#: ../system/variables/ticket.rst:2 +#: ../misc/object-conditions/basics.rst:178 ../misc/variables/ticket.rst:2 +#: ../settings/ticket.rst:2 msgid "Ticket" msgstr "" @@ -11061,7 +11048,7 @@ msgstr "" #: ../manage/trigger/how-do-they-work.rst:79 msgid "" -"Certain actions (such as *email*, *SMS* and *notes*) support :doc:`/system/" +"Certain actions (such as *email*, *SMS* and *notes*) support :doc:`/misc/" "variables`, which can be used to build highly-customized message templates." msgstr "" @@ -11090,7 +11077,7 @@ msgstr "" msgid "" "You can also combine static text with placeholders for text fields. Remember " "that the placeholders' values have to be known during trigger runtime. Learn " -"more about :doc:`/system/variables`." +"more about :doc:`/misc/variables`." msgstr "" #: ../manage/trigger/how-do-they-work.rst:105 @@ -12055,7 +12042,7 @@ msgstr "" msgid "" "When switched on, a code editor will be shown below, where you can configure " "custom payload for your webhook in JSON format. To insert supported :doc:`/" -"system/variables` use ``::`` or ``#{`` shortcuts for autocomplete." +"misc/variables` use ``::`` or ``#{`` shortcuts for autocomplete." msgstr "" #: ../manage/webhook/add.rst:103 @@ -14633,11946 +14620,11837 @@ msgid "" "powerful conditions with AND/OR relations." msgstr "" -#: ../settings/branding.rst:10 -msgid "Product Name" +#: ../misc/variables.rst:2 +msgid "Variables" msgstr "" -#: ../settings/branding.rst:7 +#: ../misc/variables.rst:4 msgid "" -"Defines the name of the application, shown in the web interface, tabs and " -"title bar of the web browser." +"Please note that this is just an overview of available variables. It might " +"be incomplete or variables might not be available within some functions. If " +"you're missing variables or are not sure if something is not working as " +"expected, feel free to ask over at the `Community `_." msgstr "" -#: ../settings/branding.rst:10 -msgid "Default value: ``Zammad Helpdesk``" +#: ../misc/variables.rst:10 +msgid "" +"Variables can be called by typing ``::`` (just like text modules in the " +"frontend), as long as you're in a supported text field within the backend. " +"Zammad will display all variables being available within this context and " +"replace it to the variable as soon as you selected an entry." msgstr "" -#: ../settings/branding.rst:13 -msgid "Will be shown in the app and is included in email footers." +#: ../misc/variables.rst:15 +msgid "" +"You have an empty field which you referenced and it appears as ``-``? That's " +"currently working as designed - you might want to ensure that these fields " +"always have a value." msgstr "" -#: ../settings/branding.rst:19 -msgid "Logo" +#: ../misc/variables.rst:20 +msgid "Variable Categories" msgstr "" -#: ../settings/branding.rst:16 -msgid "Defines the logo of the application, shown in the login page of Zammad." +#: ../misc/variables.rst:31 +msgid "Wait, What About Custom Objects?" msgstr "" -#: ../settings/branding.rst:18 +#: ../misc/variables.rst:33 msgid "" -"Ensure to hit the \"Submit\" button after uploading the logo. Otherwise your " -"change will not be saved." +"Good point! Of course, we can't predict what objects you might create, but " +"we can give you a hint on how to put the puzzle together to get your custom " +"values." msgstr "" -#: ../settings/branding.rst:22 +#: ../misc/variables.rst:36 msgid "" -"Allows to set the default language of the Zammad instance. The here defined " -"locale mostly acts as a fallback for:" -msgstr "" - -#: ../settings/branding.rst:25 -msgid "user preferences (if Zammad can't detect the users locale)" +"For this, we'll talk about the inner part of the variable (so everything " +"within ``#{}``), please put the outer part around to have a valid variable. " +"The first part of the variable name consist of the object type. Currently " +"these are:" msgstr "" -#: ../settings/branding.rst:26 -msgid "CSV output (reporting, time accounting)" +#: ../misc/variables.rst:41 +msgid "Ticket (``ticket``)" msgstr "" -#: ../settings/branding.rst:30 -msgid "Define the timezone of your Zammad installation." +#: ../misc/variables.rst:42 +msgid "User (``user``)" msgstr "" -#: ../settings/branding.rst:32 -msgid "" -"This does not have any effect on timings for your agents or how Zammad " -"stores date and time values." +#: ../misc/variables.rst:43 +msgid "Organization (``organization``)" msgstr "" -#: ../settings/branding.rst:35 -msgid "Changing this value has direct consequences on the following areas:" +#: ../misc/variables.rst:44 +msgid "Group (``group``)" msgstr "" -#: ../settings/branding.rst:37 -msgid ":doc:`/manage/scheduler` tasks" +#: ../misc/variables.rst:46 +msgid "" +"The second part is the name of the attribute. This is the name you define " +"during object creation and can be found within the object attribute menu at " +"any time. The first and second part of a variable is divided by a point, e." +"g.: ``ticket.number`` which will in total be ``#{ticket.number}``." msgstr "" -#: ../settings/branding.rst:38 -msgid "search indexing (and thus reporting)" +#: ../misc/variables.rst:51 +msgid "" +"Now, in some situations it's possible that you'll need to use a third part. " +"The best example for such a situation would be a ``select`` or ``tree-" +"select`` field which will by default return the key value, not it's display " +"name. For this, just extend your variable with ``.value``. This will result " +"in ``#{ticket.select.value}``." msgstr "" -#: ../settings/branding.rst:40 -msgid "calendar subscriptions" +#: ../misc/variables.rst:60 +msgid "Using Translated Variables" msgstr "" -#: ../settings/branding.rst:41 -msgid "browser printing" +#: ../misc/variables.rst:62 +msgid "" +"If you want to use a translated variable in triggers or schedulers, you can " +"extend the placeholder like this: ``#{t(ticket.state.name)}``. The ``t`` " +"tells Zammad to search for fitting translated strings. The used output " +"language is based on the system language of Zammad which you can set in the " +"admin panel under :doc:`/settings/branding` or based on the selected locale " +"in the trigger/scheduler edit dialog." msgstr "" -#: ../settings/branding.rst:43 +#: ../misc/variables.rst:69 msgid "" -"Please note that some of above are fallbacks in case Zammad could not detect " -"the agents timezone correctly." +"A possible use-case: you want to send your customers updates on tickets via " +"trigger or scheduler which should include the state of the ticket. Using the " +"default ``#{ticket.state.name}`` (without the translation flag ``t()``) " +"would lead to the output of the original (english) name of the state." msgstr "" -#: ../settings/branding.rst:77 -msgid "Pretty Date" +#: ../misc/variables.rst:75 +msgid "Date and Time Formatting" msgstr "" -#: ../settings/branding.rst:47 +#: ../misc/variables.rst:77 msgid "" -"This setting allows you to define how Zammad should display time stamps " -"within the interface to all users." +"The system (trigger/scheduler selected) locale and timezone predefines a " +"default format of date and timestamp. This format is customizable by using " +"the ``dt()`` method." msgstr "" -#: ../settings/branding.rst:50 -msgid "" -"This does not have any effect on how Zammad returns e.g. time values via " -"variables." +#: ../misc/variables.rst:79 +msgid "The method arguments are as follows:" msgstr "" -#: ../settings/branding.rst:77 -msgid "Choose in between the following options:" +#: ../misc/variables.rst:81 +msgid "The date or timestamp variable you want to format." msgstr "" -#: ../settings/branding.rst:64 -msgid "relative" +#: ../misc/variables.rst:82 +msgid "The output format string." msgstr "" -#: ../settings/branding.rst:55 +#: ../misc/variables.rst:83 +msgid "The timezone to apply (optional)." +msgstr "" + +#: ../misc/variables.rst:85 +#: ../system/objects/external-data-source-example.rst:23 +msgid "**Example:**" +msgstr "" + +#: ../misc/variables.rst:86 msgid "" -"This timestamp shows a relative time span until it switches to a date. Over " -"time, it will change as follows:" +"``#{dt(ticket.updated_at, \"%A %Y-%m-%d %H:%M in the office\", \"Europe/" +"Berlin\")}``" msgstr "" -#: ../settings/branding.rst:58 -msgid "just now" +#: ../misc/variables.rst:87 +msgid "Monday, 2024-03-18 15:31 in the office" msgstr "" -#: ../settings/branding.rst:59 -msgid "5 minutes ago" +#: ../misc/variables.rst:89 +msgid "" +"If you want to use our example, make sure to paste the string above without " +"formatting (``CTRL+Shift+v``), otherwise it won't work." msgstr "" -#: ../settings/branding.rst:60 -msgid "3 days 1 hour ago" +#: ../misc/variables.rst:93 +msgid "The following table lists available format directives:" msgstr "" -#: ../settings/branding.rst:61 -msgid "``03/04/2022``" +#: ../misc/variables.rst:99 +msgid "Parameter" msgstr "" -#: ../settings/branding.rst:63 -msgid "Hovering the timestamp helps, you'll always get a clean timestamp then." +#: ../misc/variables.rst:102 +msgid "``%Y``" msgstr "" -#: ../settings/branding.rst:71 -msgid "absolute" +#: ../misc/variables.rst:103 +msgid "Year with 4 digits" msgstr "" -#: ../settings/branding.rst:67 -msgid "" -"This timestamp always includes the week day. For one week after creation, " -"the timestamp will not contain the date itself: Thursday 18:35." +#: ../misc/variables.rst:104 +msgid "Use ``%y`` for year with 2 digits" msgstr "" -#: ../settings/branding.rst:71 -msgid "After a week it will switch to: ``Friday 4. Mar 16:00``." +#: ../misc/variables.rst:105 +msgid "``%m``" msgstr "" -#: ../settings/branding.rst:76 -msgid "timestamp" +#: ../misc/variables.rst:106 +msgid "Month of year (as number with zero-padding)" msgstr "" -#: ../settings/branding.rst:74 -msgid "" -"This will cause Zammad to show a complete timestamp according to your locale " -"defaults. For English this could be e.g. ``2022/12/03 2:40 pm`` or for " -"German e.g. ``12.03.2022 14:40``." +#: ../misc/variables.rst:107 +msgid "Use ``%-m`` for month without zero-padding" msgstr "" -#: ../settings/branding.rst:78 -msgid "Default setting: ``relative``." +#: ../misc/variables.rst:108 +msgid "``%d``" msgstr "" -#: ../settings/security.rst:2 -msgid "Security" +#: ../misc/variables.rst:109 +msgid "Day of month (as number with zero-padding)" msgstr "" -#: ../settings/security.rst:4 -msgid "" -"For your overview we split each tab within security settings into its own " -"page:" +#: ../misc/variables.rst:110 +msgid "Use ``%e`` for day without zero-padding" msgstr "" -#: ../settings/security/base.rst:2 ../settings/system/base.rst:2 -#: ../settings/ticket.rst:8 -msgid "Base" +#: ../misc/variables.rst:111 +msgid "``%H``" msgstr "" -#: ../settings/security/base.rst:5 -msgid "New User Accounts" +#: ../misc/variables.rst:112 +msgid "Hour of day in 24h notation with zero-padding" msgstr "" -#: ../settings/security/base.rst:9 -msgid "" -"Activates the `register as a new customer` function on the login page. If " -"set to ``no`` only administrators or agents can create new accounts manually." +#: ../misc/variables.rst:113 +msgid "Use ``%k`` for hour without zero-padding" msgstr "" -#: ../settings/security/base.rst:13 ../settings/security/base.rst:38 -#: ../settings/security/base.rst:66 -msgid "Default setting: ``yes``" +#: ../misc/variables.rst:114 +msgid "``%I``" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing activated \"New User Accounts\" setting" +#: ../misc/variables.rst:115 +msgid "Hour of day in 12h notation with zero-padding" msgstr "" -#: ../settings/security/base.rst:22 +#: ../misc/variables.rst:116 msgid "" -"Deactivation of above function **does not** deactivate automatic account " -"creation! This means: If a user writes e.g. an email to Zammad and has no " -"account yet, Zammad will automatically create the account. User accounts are " -"a direct dependency of tickets and thus technically mandatory." +"Use ``%l`` for hour without zero-padding and ``%p`` / ``%P`` for meridian " +"indicator" msgstr "" -#: ../settings/security/base.rst:29 -msgid "Lost Password" +#: ../misc/variables.rst:117 +msgid "``%M``" msgstr "" -#: ../settings/security/base.rst:33 -msgid "" -"Activates the `lost password` function on the login page. If set to ``no`` " -"only administrators may change the user's password - users may update their " -"own password if they're still logged in and they have the required :doc:" -"`permission `." +#: ../misc/variables.rst:118 +msgid "Minute of hour" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing activated \"Lost Password\" setting" +#: ../misc/variables.rst:120 +msgid "``%S``" msgstr "" -#: ../settings/security/base.rst:49 -msgid "" -"With third party authentications - but especially LDAP - you may want to " -"disable this function. Zammad **will not** change third party login " -"passwords and instead set or change the local password!" +#: ../misc/variables.rst:121 +msgid "Second of Minute" msgstr "" -#: ../settings/security/base.rst:56 -msgid "Password Login" +#: ../misc/variables.rst:123 +msgid "``%A``" msgstr "" -#: ../settings/security/base.rst:60 -msgid "" -"Activates the username & password login by default and if no third-party " -"login is activated. Disabling password login on the Zammad login page only " -"takes effect if you enable any :doc:`third-party`." +#: ../misc/variables.rst:124 +msgid "Weekday name" msgstr "" -#: ../settings/security/base.rst:64 -msgid "See :doc:`third-party` for supported third-party logins." +#: ../misc/variables.rst:125 +msgid "Use ``%a`` for abbreviated name or ``%^A`` for uppercase name" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing de-activated \"Password Login\" setting" +#: ../misc/variables.rst:126 +msgid "``%B``" msgstr "" -#: ../settings/security/base.rst:77 -msgid "" -"To help administrators to overcome \"login issues\", Zammad automatically " -"offers a password request for administrator users. This allows you to adjust " -"Third-Party applications even if the login does no longer work!" +#: ../misc/variables.rst:127 +msgid "Month name" msgstr "" -#: ../settings/security/base.rst:84 -msgid "Session Timeout" +#: ../misc/variables.rst:128 +msgid "Use ``%b`` for abbreviated name" msgstr "" -#: ../settings/security/base.rst:86 -msgid "" -"All settings below by default are set to ``4 weeks``. Session Timeout " -"defines the life time of a users session. As soon as it's reached, Zammad " -"will automatically log off the session in question." +#: ../misc/variables.rst:129 +msgid "``%U``" msgstr "" -#: ../settings/security/base.rst:91 -msgid "" -"Zammad takes the highest value set assigned for the user based on the " -"permissions." +#: ../misc/variables.rst:130 +msgid "Week number of current year" msgstr "" -#: ../settings/security/base.rst:94 -msgid "``admin``" +#: ../misc/variables.rst:131 +msgid "Use ``%W`` for a different calculation method" msgstr "" -#: ../settings/security/base.rst:96 -msgid "``ticket.customer``" +#: ../misc/variables.rst:134 +msgid "" +"We support the known format directives for the Ruby built-in method " +"``strftime`` of the ``DateTime`` class. For more information, see `here " +"`_." msgstr "" -#: ../settings/security/base.rst:97 -msgid "``default`` (fallback if user doesn't have above permissions set)" +#: ../misc/variables/article.rst:2 +msgid "Articles" msgstr "" -#: ../settings/security/base.rst:99 +#: ../misc/variables/article.rst:4 ../misc/variables/config.rst:4 +#: ../misc/variables/current-user.rst:4 ../misc/variables/ticket.rst:4 msgid "" -"All settings act independently from each other allowing you to disable the " -"timeouts for e.g. admins, but not agents." +"If you're missing variables or are not sure if something is not working as " +"expected, feel free to ask over at the `Community `_." msgstr "" -#: ../settings/security/base.rst:115 -#: ../system/integrations/checkmk/api-reference.rst:13 -msgid "Example" +#: ../misc/variables/article.rst:6 +msgid "" +"Below you can find all available ticket article-based variables within " +"Zammad. These can be called via triggers for example. If you're unsure if " +"Zammad does support variables at the point you're at, you can try to type " +"``::`` to check." msgstr "" -#: ../settings/security/base.rst:107 -msgid "Let's suppose you configured the following session timeouts" +#: ../misc/variables/article.rst:9 ../misc/variables/config.rst:9 +#: ../misc/variables/ticket.rst:9 +msgid "" +"The below list gives you an example what kind of data you can expect, it's " +"not intended to explain the data itself." msgstr "" -#: ../settings/security/base.rst:104 -msgid "default: 3 weeks" +#: ../misc/variables/article.rst:11 +msgid "Article Variables" msgstr "" -#: ../settings/security/base.rst:105 -msgid "admin: 2 weeks" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "name" msgstr "" -#: ../settings/security/base.rst:106 -msgid "ticket.agent: 4 weeks" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "variable" msgstr "" -#: ../settings/security/base.rst:107 -msgid "ticket.customer: 1 week" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "example" msgstr "" -#: ../settings/security/base.rst:115 -msgid "This results in the following situations" +#: ../misc/variables/article.rst:1 +msgid "Article > Cc" msgstr "" -#: ../settings/security/base.rst:110 -msgid "a user with ``admin`` permission will have a timeout of 2 weeks" +#: ../misc/variables/article.rst:1 +msgid "``#{article.cc}``" msgstr "" -#: ../settings/security/base.rst:111 -msgid "" -"a user with ``admin`` and ``ticket.agent`` permissions will have a timeout " -"of 2 weeks" +#: ../misc/variables/article.rst:1 +msgid "``jdoe@example.com, company@example.com``" msgstr "" -#: ../settings/security/base.rst:113 -msgid "" -"a user with ``ticket.customer`` permission will have a timeout of 1 week" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Address" msgstr "" -#: ../settings/security/base.rst:115 -msgid "" -"a user with neither ``admin``, ``ticket.agent`` nor ``ticket.customer`` " -"permissions will have a timeout of 3 weeks" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.address}``" msgstr "" -#: ../settings/security/password.rst:4 -msgid "" -"This section allows you to define password requirements for the local user " -"accounts." +#: ../misc/variables/article.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:9 -msgid "" -"Zammad does **not** allow you to change your LDAP password, instead, it will " -"set a password in its local database which might confuse your users. This " -"might be addressed in the future by `#1169 `_." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Department" msgstr "" -#: ../settings/security/password.rst:14 -msgid "**Exception for admins**" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.department}``" msgstr "" -#: ../settings/security/password.rst:16 -msgid "" -"Please note that below password policies *do not* affect administrators " -"setting passwords on user accounts. While this seems strange and not safe we " -"believe that an administrator knowing an user's password is insecure as well." +#: ../misc/variables/article.rst:1 +msgid "``Sales`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:21 -msgid "The suggested workflow is either:" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Email" msgstr "" -#: ../settings/security/password.rst:23 -msgid "" -"to use third party logins to not require local passwords at all **- or -**" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.email}``" msgstr "" -#: ../settings/security/password.rst:25 -msgid "to require your *user to reset the password* upon first login." +#: ../misc/variables/article.rst:1 +msgid "``jdoe@example.com``" msgstr "" -#: ../settings/security/password.rst:27 -msgid "" -"This way administrators are not required to set a user's password at all!" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Fax" msgstr "" -#: ../settings/security/password.rst:31 -msgid "Maximum Failed Logins" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.fax}``" msgstr "" -#: ../settings/security/password.rst:33 -msgid "" -"You can choose a value between ``4`` and ``20``. This defines how often a " -"login to a user account may fail until Zammad will lock it. Your users can " -"always use the \"forgot password\" function to change their password and " -"unlock their account." -msgstr "" - -#: ../settings/security/password.rst:38 -msgid "The default value is ``10``." +#: ../misc/variables/article.rst:1 +msgid "``+4930123456789`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:42 -msgid "Beside changing the user's password, you can also unlock accounts via" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Firstname" msgstr "" -#: ../settings/security/password.rst:44 -msgid ":ref:`user management list `" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.firstname}``" msgstr "" -#: ../settings/security/password.rst:45 -msgid ":docs:`console `" +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Joe`` or empty if not set" msgstr "" -#: ../settings/security/password.rst:46 -msgid ":docs:`API `" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Lastname" msgstr "" -#: ../settings/security/password.rst:50 -msgid "Failed logins via LDAP no longer lock accounts." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.lastname}``" msgstr "" -#: ../settings/security/password.rst:53 -msgid "2 Lower Case And 2 Upper Case Characters" +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +#: ../misc/variables/ticket.rst:1 +msgid "``Doe`` or empty if not set" msgstr "" -#: ../settings/security/password.rst:55 -msgid "" -"You can add complexity to passwords by enforcing at least 2 upper and lower " -"case characters." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Login" msgstr "" -#: ../settings/security/password.rst:58 ../settings/security/password.rst:83 -msgid "The default value is ``no``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.login}``" msgstr "" -#: ../settings/security/password.rst:62 -msgid "Minimum Length" +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +#: ../misc/variables/ticket.rst:1 +msgid "``jdoe``" msgstr "" -#: ../settings/security/password.rst:64 -msgid "" -"This defines the minimum password length required for users to provide (from " -"``4`` to ``20``)." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Mobile" msgstr "" -#: ../settings/security/password.rst:67 -msgid "The default value is ``6``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.mobile}``" msgstr "" -#: ../settings/security/password.rst:71 -msgid "Digit Required" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Note" msgstr "" -#: ../settings/security/password.rst:73 -msgid "This enforces your users to use at least one digit within the password." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.note}``" msgstr "" -#: ../settings/security/password.rst:75 -msgid "The default value is ``yes``." +#: ../misc/variables/article.rst:1 +msgid "``Some note about user`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:78 -msgid "Special Character Required" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Phone" msgstr "" -#: ../settings/security/password.rst:80 -msgid "" -"This setting allows you to improve your password quality even more by " -"enforcing the password to contain at least one special character." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.phone}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:2 -msgid "SSL Certificates" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > VIP" msgstr "" -#: ../settings/security/ssl-certificates.rst:7 -msgid "" -"Zammad offers the possibility to upload custom certificates and custom " -"Certificate Authority (CA) certificates. This can be useful if you want to " -"connect Zammad the secure way to other systems which are using custom " -"certificates." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.vip}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:12 -msgid "" -"An example usecase might be: You have an internal LDAP server that is not " -"accessible from the internet, and you want a SSL-encrypted connection, using " -"a custom certificate." +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +msgid "``true`` or ``false``" msgstr "" -#: ../settings/security/ssl-certificates.rst:19 -msgid "" -"You should have an existing custom certificate file and/or a custom CA " -"certificate file, which you want to add to Zammad. As filetype ``.crt`` is " -"supported and the certificate format has to be PEM (Base64 ASCII)." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Web" msgstr "" -#: ../settings/security/ssl-certificates.rst:25 -msgid "" -"When you import a custom CA certificate, all certificates generated with " -"this are trusted. This can be useful if you have more than one system/" -"certificate you want to connect to and the certificates are issued from the " -"same custom CA." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.web}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:31 -msgid "Add a Certificate" +#: ../misc/variables/article.rst:1 +msgid "``https://zammad.com`` or empty if not set in user object" msgstr "" -#: ../settings/security/ssl-certificates.rst:33 -msgid "" -"To add a custom certificate or a custom CA certificate, head over to the " -"Admin panel > Settings > Security > SSL Certificates. Here you can find a " -"\"Add SSL Certificate\" button. In the dialog you can either select a " -"certificate file or paste the content of the certificate:" +#: ../misc/variables/article.rst:1 +msgid "Article > Created" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate adding dialog" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_at}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:43 -msgid "" -"After selecting a file or pasting the content of the certificate, click on " -"the \"Add\" button to finally upload it to Zammad. Then, the certificates " -"are immediately effective, no restart or similar required." +#: ../misc/variables/article.rst:1 +msgid "``2019-10-08 15:24:47 UTC``" msgstr "" -#: ../settings/security/ssl-certificates.rst:49 -msgid "" -"Please note that only single certificate files are supported. That means if " -"you want to import a certificate / CA certificate, it must contain **only " -"one** certificate." +#: ../misc/variables/article.rst:1 +msgid "Article > From" msgstr "" -#: ../settings/security/ssl-certificates.rst:54 -msgid "Certificate Overview" +#: ../misc/variables/article.rst:1 +msgid "``#{article.from}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:56 +#: ../misc/variables/article.rst:1 msgid "" -"After you added a certificate, you can see a table with information for each " -"added certificate:" +"``Joe Doe `` may differ, depends on ``FROM`` of send mail" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing table of added certificates" +#: ../misc/variables/article.rst:1 +msgid "Article > Sender > Name" msgstr "" -#: ../settings/security/ssl-certificates.rst:64 -msgid "" -"Here you can download the certificate or delete it, if you don't need it " -"anymore." +#: ../misc/variables/article.rst:1 +msgid "``#{article.sender.name}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:68 -msgid "Deleting Certificates" +#: ../misc/variables/article.rst:1 +msgid "``Customer``, ``Agent`` or ``System``" msgstr "" -#: ../settings/security/ssl-certificates.rst:70 -msgid "" -"If you want to delete a specific certificate, you can do it by clicking on " -"the menu in the actions column and selecting delete:" +#: ../misc/variables/article.rst:1 +msgid "Article > Subject" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate deletion button" +#: ../misc/variables/article.rst:1 +msgid "``#{article.subject}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:79 -msgid "Downloading Certificates" +#: ../misc/variables/article.rst:1 +msgid "``My amazing subject``" msgstr "" -#: ../settings/security/ssl-certificates.rst:81 -msgid "" -"If you want to download your certificates, you can do this as well via " -"corresponding action buttons." +#: ../misc/variables/article.rst:1 +msgid "Article > Text" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate download button" +#: ../misc/variables/article.rst:1 +msgid "``#{article.body}``" msgstr "" -#: ../settings/security/third-party.rst:13 -msgid "Login Providers" +#: ../misc/variables/article.rst:1 +msgid "``Test`` without formatting (plain)" msgstr "" -#: ../settings/security/third-party.rst:2 -msgid "Third-Party Applications" +#: ../misc/variables/article.rst:1 +msgid "Article > TicketID" msgstr "" -#: ../settings/security/third-party.rst:4 -msgid "" -"Third party authentication is a great way to help your users to login to " -"Zammad more easily. If the account is yet unknown, Zammad will create a new " -"user automatically, without the user needed to interact (e.g. type in his " -"name). Another big advantage of this feature is that your user doesn't need " -"to remember another password." +#: ../misc/variables/article.rst:1 +msgid "``#{article.ticket_id}``" msgstr "" -#: ../settings/security/third-party.rst:10 -msgid "" -"You can deactivate logging in via :ref:`security_password_login` if any of " -"the mentioned authentication providers are enabled in your instance." +#: ../misc/variables/article.rst:1 +msgid "``1`` (not ticket number)" msgstr "" -#: ../settings/security/third-party.rst:27 -msgid "" -"We're currently missing documentation for the following login providers:" +#: ../misc/variables/article.rst:1 +msgid "Article > To" msgstr "" -#: ../settings/security/third-party.rst:29 -msgid "LinkedIn" +#: ../misc/variables/article.rst:1 +msgid "``#{article.to}``" msgstr "" -#: ../settings/security/third-party.rst:30 -msgid "Weibo" +#: ../misc/variables/article.rst:1 +msgid "``helpdesk@example.com``" msgstr "" -#: ../settings/security/third-party.rst:35 -msgid "Automatic Account Link on Initial Logon" +#: ../misc/variables/article.rst:1 +msgid "Article > Type > Name" msgstr "" -#: ../settings/security/third-party.rst:37 -msgid "" -"In general there's two possible options for Zammad on how to deal with " -"already known users as they try to authenticate against a third-party " -"application. By default, Zammad will not automatically link \"unknown\" " -"authentication providers to existing accounts." +#: ../misc/variables/article.rst:1 +msgid "``#{article.type.name}``" msgstr "" -#: ../settings/security/third-party.rst:42 +#: ../misc/variables/article.rst:1 msgid "" -"This means that the user has to manually link authentication providers to " -"their accounts (for more about this :user-docs:`consult the user " -"documentation `)." +"``email`` (`list of article types `_)" msgstr "" -#: ../settings/security/third-party.rst:46 -msgid "" -"Sometimes this doesn't come in handy as this also means you'll receive error " -"messages about \"email address being in use already\" for (yet) unknown " -"third-party authentication methods." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Address" msgstr "" -#: ../settings/security/third-party.rst:50 -msgid "" -"If you want to allow your users to always be able to log in, no matter what, " -"you may want to enable ``Automatic account link on initial logon``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.address}``" msgstr "" -#: ../settings/security/third-party.rst:None -msgid "" -"Screenshot highlighting the \"Automatic account link on initial logon\"\n" -"setting" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Department" msgstr "" -#: ../settings/security/third-party.rst:60 -msgid "Automatic Account Linking Notification" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.department}``" msgstr "" -#: ../settings/security/third-party.rst:64 -msgid "" -"To improve security and your users awareness, you can enable Zammad to " -"notify your users when a new third-party application has been linked to " -"their account." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Email" msgstr "" -#: ../settings/security/third-party.rst:68 -msgid "" -"This notification is sent out once per third-party application. Zammad does " -"also mention the method used, e.g.: ``Microsoft``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.email}``" msgstr "" -#: ../settings/security/third-party.rst:71 -msgid "By default this setting is not active (set to ``no``)." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Fax" msgstr "" -#: ../settings/security/third-party.rst:0 -msgid "" -"Screenshot showing sample notification mail after initial\n" -"third-party linking" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.fax}``" msgstr "" -#: ../settings/security/third-party.rst:85 -msgid "" -"This notification is only sent if the account in question already exists. If " -"the login via the third-party also creates the missing account, the " -"notification will be skipped." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Firstname" msgstr "" -#: ../settings/security/third-party.rst:89 -msgid "This means it only affects:" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.firstname}``" msgstr "" -#: ../settings/security/third-party.rst:91 -msgid "manual account linking within the third-party page of the users profile" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Lastname" msgstr "" -#: ../settings/security/third-party.rst:92 -msgid "" -"logging into an existing local account by utilizing the *automatic account " -"link on initial logon* functionality" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.lastname}``" msgstr "" -#: ../settings/security/third-party.rst:None -msgid "" -"Screenshot showing the \"automatic account linking notification\"\n" -"setting" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Login" msgstr "" -#: ../settings/security/third-party.rst:100 -msgid "No User Creation on Logon" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.login}``" msgstr "" -#: ../settings/security/third-party.rst:102 -msgid "" -"By default, Zammad will create a new user account if the user logs in via a " -"third-party application and the account doesn't exist yet." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Mobile" msgstr "" -#: ../settings/security/third-party.rst:105 -msgid "" -"If you want to prevent Zammad from creating new accounts on logon, you can " -"disable this feature by setting ``No user creation on logon`` to ``yes``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.mobile}``" msgstr "" -#: ../settings/security/third-party.rst:None -msgid "Screenshot showing the \"no user creation on logon\" setting" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Note" msgstr "" -#: ../settings/security/third-party/facebook.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via Facebook To do " -"so, you need to follow these steps:" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.note}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:9 -msgid "Register Facebook App" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Phone" msgstr "" -#: ../settings/security/third-party/facebook.rst:11 -msgid "" -"Visit [https://developers.facebook.com/apps/] and click on \"Add a new App\"" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.phone}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "initial page" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > VIP" msgstr "" -#: ../settings/security/third-party/facebook.rst:17 -msgid "After that enter the app settings" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.vip}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "Create App" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Web" msgstr "" -#: ../settings/security/third-party/facebook.rst:22 -msgid "Navigate to \"Settings\" and fill in this infromation" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.web}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "App Settings" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated" msgstr "" -#: ../settings/security/third-party/facebook.rst:27 -msgid "Navigate to app review and Check \"Make [appname] public?\"" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_at}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "App Review" +#: ../misc/variables/article.rst:1 +msgid "Article > Visibility" msgstr "" -#: ../settings/security/third-party/facebook.rst:35 -msgid "Configure Zammad as Facebook App" +#: ../misc/variables/article.rst:1 +msgid "``#{article.internal}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:37 -msgid "" -"Navigate to \"Admin -> Security -> Third Party Applications\" and enter the " -"App ID and the App Secret. You can find this Key in the Dashbard of your " -"Facebok app." +#: ../misc/variables/article.rst:1 +msgid "``false`` or ``true`` (false if not internal)" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "Zammad Configuration" +#: ../misc/variables/article.rst:1 +msgid "Article Text as HTML (not referenced)" msgstr "" -#: ../settings/security/third-party/facebook.rst:44 -#: ../settings/security/third-party/github.rst:43 -#: ../settings/security/third-party/gitlab.rst:46 -msgid "" -"Now you can link accounts via \"Avatar -> Profile -> Link Accounts\" or " -"login via Zammad login page." +#: ../misc/variables/article.rst:1 +msgid "``#{article.body_as_html}``" msgstr "" -#: ../settings/security/third-party/github.rst:2 -#: ../system/integrations/github.rst:2 -msgid "GitHub" +#: ../misc/variables/article.rst:1 +msgid "``Test`` with formatting" msgstr "" -#: ../settings/security/third-party/github.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via GitHub. To " -"activate the quick login you need to enable OAuth for GitHub." +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "Ticket > Article#" msgstr "" -#: ../settings/security/third-party/github.rst:8 -msgid "Register GitHub App" +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "``#{ticket.article_count}``" msgstr "" -#: ../settings/security/third-party/github.rst:10 -msgid "" -"Visit https://www.github.com/settings/applications/new and enter the app " -"settings. As callback URL enter \"https://zammad_host/auth/github/callback\" " -"where zammad_host has to be replaced with your Zammad FQDN" +#: ../misc/variables/article.rst:1 +msgid "``1`` number of ticket articles" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "Register OAuth app on www.github.com" +#: ../misc/variables/config.rst:2 +msgid "Config" msgstr "" -#: ../settings/security/third-party/github.rst:19 -msgid "Configure Zammad as GitHub App" +#: ../misc/variables/config.rst:6 +msgid "" +"Below you'll find config related variables. These hold useful configuration " +"information that you can use within e.g. triggers to show necessary " +"information to your customer." msgstr "" -#: ../settings/security/third-party/github.rst:21 -msgid "" -"Enter the \"APP ID\" and the \"APP SECRET\" from the GitHub OAUTH " -"Applications Dashboard" +#: ../misc/variables/config.rst:11 +msgid "Config Variables" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub config in Zammad admin interface" +#: ../misc/variables/config.rst:1 +msgid "Config > Fully Qualified Domain Name" msgstr "" -#: ../settings/security/third-party/github.rst:28 -msgid "" -"After you configured the GitHub credentials and activated the login method, " -"you should see a new icon on the login page." +#: ../misc/variables/config.rst:1 +msgid "``#{config.fqdn}``" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub logo on login page" +#: ../misc/variables/config.rst:1 +msgid "``zammad.example.com``" msgstr "" -#: ../settings/security/third-party/github.rst:34 -msgid "" -"If you click on the icon you will be redirected to GitHub and see something " -"similar to this:" +#: ../misc/variables/config.rst:1 +msgid "Config > HTTP type" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub oauth page" +#: ../misc/variables/config.rst:1 +msgid "``#{config.http_type}``" msgstr "" -#: ../settings/security/third-party/github.rst:40 -#: ../settings/security/third-party/gitlab.rst:42 -msgid "" -"When you grant the access you will be redirected to your Zammad instance and " -"logged in as a customer." +#: ../misc/variables/config.rst:1 +msgid "``https`` or ``http``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:2 -msgid "Gitlab" +#: ../misc/variables/config.rst:1 +msgid "Config > Organization" msgstr "" -#: ../settings/security/third-party/gitlab.rst:4 +#: ../misc/variables/config.rst:1 +msgid "``#{config.organization}``" +msgstr "" + +#: ../misc/variables/config.rst:1 msgid "" -"It is possible to create a quick login for your helpdesk via Gitlab. To " -"activate the quick login you need to enable OAuth for Gitlab." +"``Zammad GmbH`` value set in `Branding `_" msgstr "" -#: ../settings/security/third-party/gitlab.rst:8 -msgid "Register Gitlab App" +#: ../misc/variables/config.rst:1 +msgid "Config > Product Name" msgstr "" -#: ../settings/security/third-party/gitlab.rst:10 -msgid "To register an app in Gitlab open your profile and select applications." +#: ../misc/variables/config.rst:1 +msgid "``#{config.product_name}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:12 +#: ../misc/variables/config.rst:1 msgid "" -"As callback URL enter \"https://zammad-fqdn/auth/gitlab/callback\" where " -"zammad-fqdn has to be replaced with your Zammad FQDN" +"``Helpdesk`` value set in `Branding `_" msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Register OAuth app on gitlab instance" +#: ../misc/variables/config.rst:1 +msgid "Config > SystemID" msgstr "" -#: ../settings/security/third-party/gitlab.rst:18 -msgid "Just select *read_user* under scopes as in the screenshot and save it." +#: ../misc/variables/config.rst:1 +msgid "``#{config.system_id}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:21 -msgid "Configure Zammad as Gitlab App" +#: ../misc/variables/config.rst:1 +msgid "``31`` (value between 1 and 99)" msgstr "" -#: ../settings/security/third-party/gitlab.rst:23 -msgid "" -"Enter the \"APP ID\" and the \"APP SECRET\" from the Gitlab OAUTH " -"Applications Dashboard and your Gitlab-URL in the \"SITE\" field." +#: ../misc/variables/config.rst:1 +msgid "Config > Ticket Hook" msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab config in Zammad admin interface" +#: ../misc/variables/config.rst:1 +msgid "``#{config.ticket_hook}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:30 -msgid "" -"After you configured the Gitlab credentials and activated the login method, " -"you should see a new icon on the login page." +#: ../misc/variables/config.rst:1 +msgid "``Ticket#``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab logo on login page" +#: ../misc/variables/current-user.rst:2 +msgid "Current User" msgstr "" -#: ../settings/security/third-party/gitlab.rst:36 +#: ../misc/variables/current-user.rst:6 msgid "" -"If you click on the icon you will be redirected to Gitlab and see something " -"similar to this:" +"Current user variables always return values of the current user that caused " +"e.g. a trigger to run." msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab oauth page" +#: ../misc/variables/current-user.rst:8 +msgid "" +"Due to the above fact, these variables are often not (yet) set or available " +"for usage." msgstr "" -#: ../settings/security/third-party/google.rst:4 +#: ../misc/variables/current-user.rst:10 msgid "" -"With some easy and fast steps, you can enable Zammad to authenticate your " -"users via Google." +"In situations where e.g. schedulers or triggers run, this most likely is " +"nothing you want to use." msgstr "" -#: ../settings/security/third-party/google.rst:8 -msgid "Register a Google App" +#: ../misc/variables/current-user.rst:13 +msgid "Current User Variables" msgstr "" -#: ../settings/security/third-party/google.rst:10 -msgid "" -"First of all, we need to create a new project - you can skip this step if " -"you already have one." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Address" msgstr "" -#: ../settings/security/third-party/google.rst:15 -msgid "" -"Use this link to create a new project: https://console.cloud.google.com/" -"projectcreate" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.address}``" msgstr "" -#: ../settings/security/third-party/google.rst:18 -msgid "" -"Now expand the menu, expand \"APIs & Services\" and select \"Credentials\". " -"Go to the tab \"OAuth consent screen\" first and ensure to fill in the " -"requested information - without doing so you can't create credentials!" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set" msgstr "" -#: ../settings/security/third-party/google.rst:None -msgid "Creating a consent screen" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Avatar" msgstr "" -#: ../settings/security/third-party/google.rst:25 -msgid "" -"After filling in and saving the consent screen information, you can go to " -"the \"Credentials\" tab and create new \"OAuth client ID\"-Credentials." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/google.rst:28 -msgid "" -"Fill in the necessary information as follows and replace ``zammad_host`` " -"with your FQDN:" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "avatar picture with width and height in pixel (e.g. 60,60)" msgstr "" -#: ../settings/security/third-party/google.rst:31 -msgid "**Application type** ``[x] Web application``" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created at" msgstr "" -#: ../settings/security/third-party/google.rst:34 -msgid "**Authorized JavaScript origins** ``https://zammad_host/``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_at}``" msgstr "" -#: ../settings/security/third-party/google.rst:37 -msgid "" -"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" -"callback``" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC``" msgstr "" -#: ../settings/security/third-party/google.rst:None -msgid "Adding a new OAuth client ID" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Address" msgstr "" -#: ../settings/security/third-party/google.rst:43 -msgid "" -"After creating the credentials, go to your Zammad installation and navigate " -"to \"Admin > Security > Third Party Applications\" > Google. Enter your " -"Client ID and Client secret here." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.address}``" msgstr "" -#: ../settings/security/third-party/google.rst:None -msgid "Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Avatar" msgstr "" -#: ../settings/security/third-party/google.rst:50 -msgid "After submitting, the login via Google can be used." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:2 -msgid "Microsoft" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Department" msgstr "" -#: ../settings/security/third-party/microsoft.rst:4 -msgid "" -"Zammad's Microsoft connection allows your users with Microsoft accounts to " -"login. This works for Azure users as well and can be an alternative to :doc:" -"`/system/integrations/ldap/index`." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.department}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:10 -msgid "" -"This documentation part does not cover our :doc:`📧 Microsoft 365 email " -"channel `." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Sales`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screenshot showing Microsoft login button on Zammad login screen." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Email" msgstr "" -#: ../settings/security/third-party/microsoft.rst:30 -#: ../settings/security/third-party/microsoft.rst:53 -msgid "Supported account types:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.email}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:22 -msgid "" -"Please note that Zammad only supports these account types (App dependent):" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``jdoe@customer.tld``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:35 -msgid "Avatars of signing in users:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Fax" msgstr "" -#: ../settings/security/third-party/microsoft.rst:33 -msgid "" -"Zammad currently ignores user avatars. If the user is registered with e.g. " -"Gravatar, Zammad will fetch the avatar from there if enabled. See :doc:" -"`Zammad Image Service ` for more." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.fax}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:38 -msgid "Step 1 - Register a Microsoft App for Zammad" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``004930123464789`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:40 -msgid "" -"Login to the `Microsoft Azure Portal `_ and " -"navigate to App registrations to create a new app. Provide the requested " -"information as follows and register your app." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Firstname" msgstr "" -#: ../settings/security/third-party/microsoft.rst:46 -msgid "Name:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.firstname}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:45 -msgid "" -"Any meaningful name fitting, this name will be displayed to users trying to " -"authenticate with this app." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``John`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:49 -msgid "Choose one of the above mentioned account types (see Limitations)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Lastname" msgstr "" -#: ../settings/security/third-party/microsoft.rst:51 -msgid "" -"The correct account type depends on your use case. If you want to use the " -"authentication internal only, choose the first option. If you're unsure, use " -"the \"Help me choose...\" link." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.lastname}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:58 -msgid "Redirect URI (optional):" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Login" msgstr "" -#: ../settings/security/third-party/microsoft.rst:56 -msgid "" -"Select web and provide your callback URL. The callback URL looks like this: " -"``https://zammad.domain.tld/auth/microsoft_office365/callback``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.login}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to register a Microsoft app" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Mobile" msgstr "" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "Within **API permissions** add the following permissions:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.mobile}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:69 -msgid "``User.Read``" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``0049176123456789`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "Contacts" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Note" msgstr "" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "``Contacts.Read``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.note}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:73 -msgid "" -"You can find these permissions within *Microsoft Graph → Delegated " -"permissions*." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Some note to this user`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to add required API permissions" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Phone" msgstr "" -#: ../settings/security/third-party/microsoft.rst:80 -msgid "" -"Within **Certificates & secrets** create a new client secret. Note down the " -"returned secret **value** for later. **Do not** use the secret ID!" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.phone}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to create a new app secret" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``004930123456789`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:88 -msgid "" -"From **Overview** copy your apps *Application (client) ID*. If you're using " -"a single tenant app, please also copy *Directory (tenant) ID*. You now have " -"all required information for Zammad." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > VIP" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to retreive application client and tenant IDs" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.vip}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:98 -msgid "Step 2 - Add App Credentials to Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Web" msgstr "" -#: ../settings/security/third-party/microsoft.rst:100 -msgid "" -"Navigate to Security > Third-party Applications (Tab) within Zammad's admin " -"settings. Scroll down to the section *Authentication via Microsoft* and fill " -"in the required information." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.web}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:105 -msgid "App ID:" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``https://zammad.org`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:105 -msgid "This is your *Application (client) ID*." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Department" msgstr "" -#: ../settings/security/third-party/microsoft.rst:108 -msgid "App secret:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.department}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:108 -msgid "This is your *client secret* (value)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Email" msgstr "" -#: ../settings/security/third-party/microsoft.rst:113 -msgid "App Tenant ID:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.email}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:111 -msgid "" -"**optional** only required for apps that use account type *Accounts in this " -"organizational directory only (Default Directory only - Single tenant).*" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Fax" msgstr "" -#: ../settings/security/third-party/microsoft.rst:115 -msgid "" -"Apply your settings by pressing submit and activate *Authentication via " -"Microsoft*." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.fax}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "" -"Screencast showing how to add app credentials and activating the\n" -"authentication method" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Firstname" msgstr "" -#: ../settings/security/third-party/saml.rst:2 -msgid "SAML" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.firstname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:4 -msgid "" -"Connect your SAML (Security Assertion Markup Language) identity provider as " -"a single sign-on (SSO) method." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Lastname" msgstr "" -#: ../settings/security/third-party/saml.rst:7 -msgid "" -"SAML is an open standard for SSO authentication (among other things). Sign-" -"ins are shared across multiple **service providers** and managed by a " -"central **identity provider** (IdP)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.lastname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:11 -msgid "" -"In this case, the service provider is Zammad, and the IdP is a software " -"service that you either host or subscribe to (*e.g.,* `Keycloak `_, `Redhat SSO Server `_, `ADFS `_, or `Okta `_)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Login" msgstr "" -#: ../settings/security/third-party/saml.rst:18 -msgid "" -"This guide assumes you are already using SAML within your organization (i." -"e., that your IdP is fully set up)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.login}``" msgstr "" -#: ../settings/security/third-party/saml.rst:21 -msgid "" -"Please note: Our instructions are based on connecting Zammad with Keycloak." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Mobile" msgstr "" -#: ../settings/security/third-party/saml.rst:25 -msgid "Step 1: Configure Your IdP" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.mobile}``" msgstr "" -#: ../settings/security/third-party/saml.rst:28 -msgid "Add Zammad as a Client/App" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Note" msgstr "" -#: ../settings/security/third-party/saml.rst:30 -msgid "" -"Import Zammad into your IdP using the XML configuration found at ``https://" -"your.zammad.domain/auth/saml/metadata``." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.note}``" msgstr "" -#: ../settings/security/third-party/saml.rst:33 -msgid "" -"If your IdP doesn't support XML import, you will have to configure Zammad as " -"a new client/app manually using the above XML metadata file for reference." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Domain based assignment" msgstr "" -#: ../settings/security/third-party/saml.rst:36 -msgid "For instance, when you see this tag:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.domain_assignment}``" msgstr "" -#: ../settings/security/third-party/saml.rst:42 -msgid "" -"Set the **Assertion Consumer Service Binding URL** (sometimes also listed as " -"**Valid Redirect URIs**) to ``http://your.zammad.domain/auth/saml/callback``." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Domain" msgstr "" -#: ../settings/security/third-party/saml.rst:47 -msgid "Set Up User Attribute Mapping" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.domain}``" msgstr "" -#: ../settings/security/third-party/saml.rst:49 -msgid "" -"Zammad requests the following user attributes (or “properties”) from the IdP:" +#: ../misc/variables/current-user.rst:1 +msgid "``zammad.com`` or empty if not set" msgstr "" -#: ../settings/security/third-party/saml.rst:51 -msgid "Email address (``email``)" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Name" msgstr "" -#: ../settings/security/third-party/saml.rst:52 -msgid "Full name (``name``)" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.name}``" msgstr "" -#: ../settings/security/third-party/saml.rst:53 -msgid "Given name (``first_name``)" +#: ../misc/variables/current-user.rst:1 +msgid "``Zammad GmbH``" msgstr "" -#: ../settings/security/third-party/saml.rst:54 -msgid "Family name (``last_name``)" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Note" msgstr "" -#: ../settings/security/third-party/saml.rst:56 -msgid "" -"You may need to set up “mappers” (or “mappings”) to tell your IdP how user " -"attributes in SAML correspond to those in Zammad. For a more detailed " -"breakdown, refer to the XML metadata file referenced in the previous section." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.note}``" msgstr "" -#: ../settings/security/third-party/saml.rst:62 -msgid "Per-IdP Instructions" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``A note to the organization of the user`` or empty if not set" msgstr "" -#: ../settings/security/third-party/saml.rst:102 -msgid "Keycloak" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Shared organization" msgstr "" -#: ../settings/security/third-party/saml.rst:65 -msgid "" -"**To add Zammad as a client,** save the XML configuration to disk (``https://" -"your.zammad.domain/auth/saml/metadata``) and use **Clients > Clients list > " -"Import client** in the Keycloak admin panel." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.shared}``" msgstr "" -#: ../settings/security/third-party/saml.rst:70 -msgid "" -"To help Zammad **match its own user accounts to Keycloak users**, create a " -"user attribute (or “property”) mapper. In **Clients list**, click on your " -"newly created Client ID, choose the tab **Client scopes** and click on the " -"link which refers to your Zammad instance. Choose **Add mapper > By " -"configuration > User Property** and create a mapper with the following " -"entries:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > VIP" msgstr "" -#: ../settings/security/third-party/saml.rst:78 -msgid "**Name**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.vip}``" msgstr "" -#: ../settings/security/third-party/saml.rst:80 -msgid "**Mapper Type**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Phone" msgstr "" -#: ../settings/security/third-party/saml.rst:81 -msgid "``User Property``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.phone}``" msgstr "" -#: ../settings/security/third-party/saml.rst:82 -msgid "**Property**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated at" msgstr "" -#: ../settings/security/third-party/saml.rst:83 -msgid "``emailAddress``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_at}``" msgstr "" -#: ../settings/security/third-party/saml.rst:84 -msgid "**SAML Attribute Name**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Address" msgstr "" -#: ../settings/security/third-party/saml.rst:86 -msgid "**SAML Attribute NameFormat**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.address}``" msgstr "" -#: ../settings/security/third-party/saml.rst:87 -msgid "``basic``" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Avatar" msgstr "" -#: ../settings/security/third-party/saml.rst:89 -msgid "" -"In the example above, we're telling Zammad that whenever it receives a SAML " -"login request, it should take the ``email`` property from Keycloak, look for " -"a Zammad user with the same ``email`` attribute, and create a new session " -"for that user." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/saml.rst:95 -msgid "" -"If your Keycloak users' email addresses are stored on another property (*e." -"g.,* ``username``), adjust accordingly." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Department" msgstr "" -#: ../settings/security/third-party/saml.rst:98 -msgid "" -"Back in **Settings**, enter the Client ID (``https://your.zammad.domain/auth/" -"saml/metadata``) in the field **Master SAML Processing URL**." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.department}``" msgstr "" -#: ../settings/security/third-party/saml.rst:101 -msgid "You also need to enable **Sign assertions**." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Email" msgstr "" -#: ../settings/security/third-party/saml.rst:105 -msgid "Step 2: Configure Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.email}``" msgstr "" -#: ../settings/security/third-party/saml.rst:107 -msgid "" -"Enable SAML and enter your IdP's details in the Admin Panel under **Settings " -"> Security > Third Party Applications > Authentication via SAML**:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Fax" msgstr "" -#: ../settings/security/third-party/saml.rst:None -msgid "Example configuration of SAML part 1" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.fax}``" msgstr "" -#: ../settings/security/third-party/saml.rst:119 -msgid "Display name" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Firstname" msgstr "" -#: ../settings/security/third-party/saml.rst:116 -msgid "" -"Allows you to define a custom button name for SAML. This helps your users to " -"understand better what the button on the login page does." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.firstname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:119 -msgid "Defaults to ``SAML``." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Lastname" msgstr "" -#: ../settings/security/third-party/saml.rst:123 -msgid "IDP SSO target URL" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.lastname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:122 -msgid "" -"This is the target URL Zammad shall redirect to when the user presses the " -"SAML button. For Keycloak, this needs to look like https://your.domain/" -"realms/your-realm/protocol/saml" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Login" msgstr "" -#: ../settings/security/third-party/saml.rst:127 -msgid "IDP single logout target URL" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.login}``" msgstr "" -#: ../settings/security/third-party/saml.rst:126 -msgid "" -"This is the URL to which the single logout request and response should be " -"sent." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Mobile" msgstr "" -#: ../settings/security/third-party/saml.rst:131 -msgid "IDP certificate" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.mobile}``" msgstr "" -#: ../settings/security/third-party/saml.rst:130 -msgid "" -"The public certificate of your IDP for Zammad to verify during the callback " -"phase." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Note" msgstr "" -#: ../settings/security/third-party/saml.rst:145 -msgid "IDP certificate fingerprint" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.note}``" msgstr "" -#: ../settings/security/third-party/saml.rst:134 -msgid "" -"The fingerprint of your IDPs public certificate to verify during callback " -"phase." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Phone" msgstr "" -#: ../settings/security/third-party/saml.rst:137 -msgid "🔏 **For the IdP certificate / certificate fingerprint:**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.phone}``" msgstr "" -#: ../settings/security/third-party/saml.rst:139 -msgid "" -"Provide **only one or the other**—do not provide both! (Between the two, we " -"recommend the signing certificate itself: fingerprints use SHA-1, which `has " -"been broken for a while now `_.)" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > VIP" msgstr "" -#: ../settings/security/third-party/saml.rst:144 -msgid "" -"**Keycloak users:** Find your certificate in the Keycloak admin panel under " -"**Realm Settings > Keys > Algorithm: RS256 > Certificate**." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.vip}``" msgstr "" -#: ../settings/security/third-party/saml.rst:151 -msgid "Name identifier format" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``false`` or ``true``" msgstr "" -#: ../settings/security/third-party/saml.rst:148 -msgid "" -"This is the unique identifiers field type. Usually it should be ``urn:oasis:" -"names:tc:SAML:1.1:nameid-format:emailAddress``." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Web" msgstr "" -#: ../settings/security/third-party/saml.rst:151 -msgid "Zammad **expects an email address as unique identifier**!" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.web}``" msgstr "" -#: ../settings/security/third-party/saml.rst:155 -msgid "UID attribute name" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > VIP" msgstr "" -#: ../settings/security/third-party/saml.rst:154 -msgid "" -"Here you can define an attribute that uniquely identifies the user. If " -"unset, the name identifier returned by the IDP is used." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.vip}``" msgstr "" -#: ../settings/security/third-party/saml.rst:None -msgid "Example configuration of SAML part 2" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Web" msgstr "" -#: ../settings/security/third-party/saml.rst:163 -msgid "" -"Decide if the certificate for the connection to the IdP service has to be " -"verified or not (default: ``yes``)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.web}``" msgstr "" -#: ../settings/security/third-party/saml.rst:169 -msgid "Signing & Encrypting" +#: ../misc/variables/ticket.rst:6 +msgid "" +"Below you can find all available ticket-based variables within Zammad. These " +"can be called via triggers for example. If you're unsure if Zammad does " +"support variables at the point you're at, you can try to type ``::`` to " +"check." msgstr "" -#: ../settings/security/third-party/saml.rst:169 -msgid "" -"Define if you want to sign, encrypt, do both or nothing for the requests." +#: ../misc/variables/ticket.rst:12 +msgid "Ticket Variables" msgstr "" -#: ../settings/security/third-party/saml.rst:179 -msgid "Certificate (PEM)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Accounted Time" msgstr "" -#: ../settings/security/third-party/saml.rst:172 -msgid "" -"Paste the public certificate of your Zammad SAML client, if you want to " -"encrypt the requests." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.time_unit}``" msgstr "" -#: ../settings/security/third-party/saml.rst:175 -msgid "Make sure the certificate is:" +#: ../misc/variables/ticket.rst:1 +msgid "``1``, ``2.75`` or empty response" msgstr "" -#: ../settings/security/third-party/saml.rst:177 -msgid "already valid and not yet expired" +#: ../misc/variables/ticket.rst:1 +msgid "``3``, any number of articles existing in the ticket right now" msgstr "" -#: ../settings/security/third-party/saml.rst:178 -msgid "no CA certificate" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Closing time" msgstr "" -#: ../settings/security/third-party/saml.rst:179 -msgid "valid for signing and encrypting" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.close_at}``" msgstr "" -#: ../settings/security/third-party/saml.rst:185 -msgid "Private key (PEM)" +#: ../misc/variables/ticket.rst:1 +msgid "2019-10-07 17:25:00 UTC" msgstr "" -#: ../settings/security/third-party/saml.rst:182 -msgid "" -"Paste the private key of your Zammad SAML client here, if you want to sign " -"the requests." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created at" msgstr "" -#: ../settings/security/third-party/saml.rst:185 -msgid "Make sure the key is an RSA key with a length of at least 2048 bits." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_at}``" msgstr "" -#: ../settings/security/third-party/saml.rst:188 -msgid "Private key secret" +#: ../misc/variables/ticket.rst:1 +msgid "2019-10-07 16:25:00 UTC" msgstr "" -#: ../settings/security/third-party/saml.rst:188 -msgid "If your private key is secured with a secret, you can provide it here." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Address" msgstr "" -#: ../settings/security/third-party/saml.rst:192 -msgid "Your callback URL" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.address}``" msgstr "" -#: ../settings/security/third-party/saml.rst:191 -msgid "" -"This URL is needed for your IdP configuration so it knows where to redirect " -"to after successful authentication." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Avatar" msgstr "" -#: ../settings/security/third-party/saml.rst:194 -msgid "" -"After saving your input by clicking on the \"Submit\" button, Zammad " -"verifies the provided keys/certificates (e.g. if they are valid for signing/" -"encrypting and if they aren't expired)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/saml.rst:199 -msgid "" -"See :ref:`automatic account linking ` for details " -"on how to link existing Zammad accounts to IdP accounts." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Department" msgstr "" -#: ../settings/security/third-party/saml.rst:205 -msgid "Automatic account linking doesn't work" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.department}``" msgstr "" -#: ../settings/security/third-party/saml.rst:206 -msgid "" -"Have you double-checked your IdP's user attribute mapping configuration?" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Email" msgstr "" -#: ../settings/security/third-party/twitter.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via Twitter. To do " -"so, you need to follow these steps:" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.email}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:8 -msgid "Register Twitter App" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Fax" msgstr "" -#: ../settings/security/third-party/twitter.rst:10 -msgid "Go to https://dev.twitter.com/apps and login with your account." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.fax}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:15 -msgid "Click on \"Create App\"" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Firstname" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "new app page" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.firstname}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:20 -msgid "" -"Enter app settings. As \"Callback URL\" you need to enter ``https://" -"zammad_host/api/v1/external_credentials/twitter/callback``. You need to " -"replace ``zammad_host`` with the domain of your Zammad system." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Lastname" msgstr "" -#: ../settings/security/third-party/twitter.rst:24 -msgid "" -"After the app has been created, update the application icon and organization " -"attributes." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.lastname}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "set permissions to receive and send direct messages" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Login" msgstr "" -#: ../settings/security/third-party/twitter.rst:30 -msgid "" -"Next we need to set ``read, write and access direct messages`` permissions " -"for the app." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.login}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "click on Keys & Access Token, note them" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Mobile" msgstr "" -#: ../settings/security/third-party/twitter.rst:36 -msgid "" -"Go to \"Keys and Access Token\" tab and note the \"Consumer Key\" and " -"\"Consumer Secret\"." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.mobile}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:40 -msgid "Configure Zammad as Twitter App" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Note" msgstr "" -#: ../settings/security/third-party/twitter.rst:42 -msgid "" -"Go to \"Admin > Security > Twitter > Third Party Applications > Twitter\" " -"Section." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.note}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "Admin > Security > Third Party Applications" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Phone" msgstr "" -#: ../settings/security/third-party/twitter.rst:48 -msgid "" -"Fill in the \"Twitter Key\" and the \"Twitter Secret\" and click the " -"\"Submit\" button." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.phone}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:51 -msgid "" -"Now you can link accounts via \"Avatar > Profile > Link Accounts\" or login " -"via Zammad login page." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > VIP" msgstr "" -#: ../settings/security/two-factor.rst:11 -msgid "Two-factor Authentication Methods" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.vip}``" msgstr "" -#: ../settings/security/two-factor.rst:2 -msgid "Two-Factor Authentication" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Web" msgstr "" -#: ../settings/security/two-factor.rst:4 -msgid "" -"Two-factor authentication (2FA) enhances the security of Zammad accounts by " -"adding an extra layer of verification beyond a password. It requires users " -"to provide two different types of authentication factors, typically " -"something they know (like a password) and something they possess (like a " -"mobile device or a security token), to ensure that only authorized " -"individuals can access the account." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.web}``" msgstr "" -#: ../settings/security/two-factor.rst:19 -msgid "Enable Recovery Codes" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Address" msgstr "" -#: ../settings/security/two-factor.rst:21 -msgid "" -"Recovery codes are one-time use security codes that can be used by the user " -"if they lose access to their other two-factor authentication methods. They " -"cannot be used on their own, they can only be activated if at least one two-" -"factor authentication method is enabled." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.address}``" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Enable Recovery Codes Setting" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Avatar" msgstr "" -#: ../settings/security/two-factor.rst:30 -msgid "" -"Recovery codes can only be used as a backup method. If enabled, they will be " -"automatically generated for the user once they set up their initial two-" -"factor authentication method." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.avatar(60,60)}``" msgstr "" -#: ../settings/security/two-factor.rst:34 -msgid "" -"The user will be asked to print out or save the generated recovery codes in " -"a safe place. Once used, a recovery code cannot be reused." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Department" msgstr "" -#: ../settings/security/two-factor.rst:37 -msgid "" -"Users will also have an option to regenerate their recovery codes at any " -"time, which invalidates already existing recovery codes and provides them " -"with a list of fresh codes." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.department}``" msgstr "" -#: ../settings/security/two-factor.rst:41 -msgid "" -"After you enable this setting, when the user completes a setup of their " -"initial two-factor authentication method, they will be presented with a list " -"of recovery codes and instructed to save them for later use." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Email" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Recovery Codes Generation Modal Dialog" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.email}``" msgstr "" -#: ../settings/security/two-factor.rst:50 -msgid "Enforce the Set Up of the Two-Factor Authentication" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Fax" msgstr "" -#: ../settings/security/two-factor.rst:52 -msgid "" -"In case you wish to require your users to set up at least one two-factor " -"authentication method for their account, you can do this by selecting " -"specific user roles the requirement applies to in **Enforced for user " -"roles** setting. Of course you must have at least one two-factor " -"authentication method enabled for this setting to take effect." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.fax}``" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Enforced for User Roles Setting" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Firstname" msgstr "" -#: ../settings/security/two-factor.rst:62 -msgid "" -"After you change this setting, if the user has one of the selected roles on " -"their account, they will be forced to set up the two-factor authentication " -"upon next sign in or application reload." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.firstname}``" msgstr "" -#: ../settings/security/two-factor.rst:66 -msgid "" -"A modal dialog with instructions will be shown, and they will not be able to " -"do any work before they set up at least one two-factor method." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Lastname" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Modal Dialog for Enforcing Two-Factor Authentication Set Up" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.lastname}``" msgstr "" -#: ../settings/security/two-factor.rst:74 -msgid "Reset Two-Factor Authentication for a Specific User" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Login" msgstr "" -#: ../settings/security/two-factor.rst:76 -msgid "" -"In case an user isn't able to login anymore because of an inaccessible " -"second factor, you can reset the user's 2FA method." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.login}``" msgstr "" -#: ../settings/security/two-factor.rst:79 -msgid "" -"To do this, go to the user management and search for the relevant user. " -"After you found the account, click the button in the action column and " -"select \"Manage Two-Factor Authentication\":" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Mobile" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Context menu in action column in user management" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.mobile}``" msgstr "" -#: ../settings/security/two-factor.rst:87 -msgid "" -"After selecting this, you can see a dialog where you can either reset one " -"2FA method or reset all of the user's 2FA methods:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Note" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Dialog for resetting user's 2FA method" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.note}``" msgstr "" -#: ../settings/security/two-factor.rst:94 -msgid "" -"Choose the fitting one, click on the corresponding \"Remove ...\" button and " -"confirm your action. The user now has to setup a new 2FA method, depending " -"on your 2FA configuration." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Phone" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:2 -msgid "Authenticator App" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.phone}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:4 -msgid "" -"The authenticator app method is a type of two-factor authentication that " -"uses a mobile application to generate one-time codes for account " -"verification. After setting up the authenticator app on their device, the " -"user links it to their Zammad account." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > VIP" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:12 -msgid "" -"When logging in, the user is prompted to enter a time-sensitive code " -"generated by the app, in addition to their password. This code acts as the " -"second factor of authentication, providing an extra layer of security as it " -"changes periodically and is unique to the user's device." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.vip}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:None -msgid "Security Code in Google Authenticator App" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Web" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:22 -msgid "" -"The app generates codes based on a shared secret key stored securely on both " -"the user's device and the server, ensuring a synchronized and secure " -"authentication process. The method of generating the codes is sometimes also " -"called TOTP (time-based one-time password)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.web}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:28 -msgid "Enabling the Authenticator App Method" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Escalation at" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:30 -#: ../settings/security/two-factor/security-keys.rst:28 -msgid "To enable the method, just toggle the switch on in the settings." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.escalation_at}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:None -msgid "Authenticator App Switch in Settings" +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:36 -msgid "" -"Now the users will be able to set up this two-factor authentication method " -"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " -"Once they do, on next sign-in with password, they will be asked to provide " -"an additional security code generated by their mobile device." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > First response" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:2 -msgid "Security Keys" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.first_response_at}``" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:4 -msgid "" -"The security keys method is a type of a two-factor authentication that uses " -"Web Authentication API in the browser for verifying user's identity. The " -"user can register multiple hardware or software security keys with their " -"Zammad account and then they can use it during the sign-in process." +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable yet" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:12 -msgid "" -"When logging in, the user is prompted to provide the same security key they " -"registered with their account, in addition to their password. This key acts " -"as the second factor of authentication, providing an extra layer of security." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Assign Follow-Ups" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:None -msgid "Security Key dialog in Safari on macOS" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_assignment}``" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:21 -msgid "" -"The type of the key can range from hardware USB sticks to passkeys stored in " -"a device of user's choice. Which type can be used depends on the browser " -"flavor and the platform of the user." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Assignment Timeout" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:26 -msgid "Enabling the Security Keys Method" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.assignment_timeout}``" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:None -msgid "Security Keys Switch in Settings" +#: ../misc/variables/ticket.rst:1 +msgid "``20`` or empty if not configured" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:34 -msgid "" -"Now the users will be able to set up this two-factor authentication method " -"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " -"Once they do, on next sign-in with password, they will be asked to provide " -"the same security key they registered during the setup." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Follow-up possible" msgstr "" -#: ../settings/system/system-selfhosted.include.rst:3 -msgid "" -"Below settings are only available to self hosted users. In hosted " -"environments we're handling these settings for you to ensure service " -"stability." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_possible}``" msgstr "" -#: ../settings/system/base.rst:11 -msgid "Fully Qualified Domain Name" +#: ../misc/variables/ticket.rst:1 +msgid "``no`` or ``yes``" msgstr "" -#: ../settings/system/base.rst:7 -msgid "The URL of your Zammad installation." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Name" msgstr "" -#: ../settings/system/base.rst:9 ../settings/system/base.rst:17 -msgid "This setting is used within :doc:`/system/variables` and notifications." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.name}``" msgstr "" -#: ../settings/system/system-base.include.rst:1 -msgid "It is automatically set by the *Getting Started wizard*." +#: ../misc/variables/ticket.rst:1 +msgid "``Sales``" msgstr "" -#: ../settings/system/system-base.include.rst:5 -msgid "Changing this setting also changes callback URLs for your channels etc." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Note" msgstr "" -#: ../settings/system/system-base.include.rst:6 -msgid "This setting can have negative affects on being able to login." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.note}``" msgstr "" -#: ../settings/system/base.rst:19 -msgid "HTTP type" +#: ../misc/variables/ticket.rst:1 +msgid "``Note about this group``" msgstr "" -#: ../settings/system/base.rst:14 -msgid "" -"The HTTP type tells your installation how your clients connect. This is " -"relevant for authentication and cookie security." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > ID" msgstr "" -#: ../settings/system/base.rst:31 -msgid "SystemID" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.id}``" msgstr "" -#: ../settings/system/base.rst:22 -msgid "" -"This ID is being used within your ticket number. In case you're " -"communicating with another ticket system with similar ticket number schemes " -"this ID greatly reduces the risk of false follow ups." +#: ../misc/variables/ticket.rst:1 +msgid "``17``, ``5281``, ..." msgstr "" -#: ../settings/system/base.rst:26 -msgid "" -"The SystemID is randomly selected upon installation of Zammad (``1-99``)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact (agent)" msgstr "" -#: ../settings/system/base.rst:30 -msgid "" -"**Do not** change this setting in a productive system! Your Zammad " -"installation may no longer recognize old ticket number based follow ups upon " -"change!" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_agent_at}``" msgstr "" -#: ../settings/system/frontend.rst:2 -msgid "Frontend" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact (customer)" msgstr "" -#: ../settings/system/frontend.rst:22 -msgid "Core Workflow Ajax Mode" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_customer_at}``" msgstr "" -#: ../settings/system/frontend.rst:6 +#: ../misc/variables/ticket.rst:1 msgid "" -"This setting allows administrators to enforce :doc:`/system/core-workflows` " -"to use Ajax-Calls instead of web sockets. You'll usually only need this if " -"you experience serious issues as noted below." +"``2019-10-07 16:25:00 UTC`` or empty if not applicable yet (Please note " +"`Ticket last contact behavior Settings `_ for this)" msgstr "" -#: ../settings/system/frontend.rst:10 -msgid "**🤓 Possible (technical) reasons**" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact" msgstr "" -#: ../settings/system/frontend.rst:12 -msgid "" -"In some cases, your network structure (e.g. firewalls, proxies) may " -"disconnect long web socket connections. This leads to select fields staying " -"empty (e.g. owner selection *after* selecting your group) or fields not " -"shown / hidden (e.g. when switching to or from pending states, the \"pending " -"till\" field not showing / hiding)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_at}``" msgstr "" -#: ../settings/system/frontend.rst:18 -msgid "" -"Please keep in mind that the Ajax fallback may cause serious pressure on " -"your application server. If you have the choice stick to web sockets." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Number" msgstr "" -#: ../settings/system/frontend.rst:22 -msgid "Default: ``no`` (inactive)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.number}``" msgstr "" -#: ../settings/system/frontend.rst:53 -msgid "Show calendar weeks in the picker of date/datetime fields" +#: ../misc/variables/ticket.rst:1 +msgid "``31001``, ``201910731001``, ..." msgstr "" -#: ../settings/system/frontend.rst:25 -msgid "" -"With this setting you can instruct Zammad to provide week number display " -"globally for all users. Calendar with week number display are usually used " -"in business sectors and may not be relevant for everyone." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain based assignment" msgstr "" -#: ../settings/system/frontend.rst:29 -msgid "" -"This setting affects *all areas* - you'll also see week numbers in the admin " -"panel for e.g. triggers and macros." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain_assignment}``" msgstr "" -#: ../settings/system/frontend.rst:32 -msgid "Default: ``no`` (not shown)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain" msgstr "" -#: ../settings/system/frontend.rst:53 -msgid "Here's the difference:" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain}``" msgstr "" -#: ../settings/system/frontend.rst:0 -msgid "Screenshot showing Zammad's date picker (in the default way)" +#: ../misc/variables/ticket.rst:1 +msgid "``domain.tld`` or empty if not set" msgstr "" -#: ../settings/system/frontend.rst:41 -msgid "Set to ``no``" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Name" msgstr "" -#: ../settings/system/frontend.rst:0 -msgid "" -"Screenshot showing Zammad's date picker with\n" -"week numbers enabled" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.name}``" msgstr "" -#: ../settings/system/frontend.rst:50 -msgid "Set to ``yes``" +#: ../misc/variables/ticket.rst:1 +msgid "``Zammad GmbH`` or empty if not set" msgstr "" -#: ../settings/system/index.rst:4 -msgid "" -"For your overview we split each tab within system settings into its own page:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Note" msgstr "" -#: ../settings/system/index.rst:16 -msgid "Console Based Settings" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.note}``" msgstr "" -#: ../settings/system/index.rst:18 -msgid "" -"There's some console based settings we didn't put into the UI. However, you " -"may find them helpful - you can find them in our :docs:`hidden settings ` section." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Shared organization" msgstr "" -#: ../settings/system/network.rst:2 -msgid "Network" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.shared}``" msgstr "" -#: ../settings/system/network.rst:8 -msgid "" -"The proxy settings can only be saved after successfully testing the proxy " -"connection." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > VIP" msgstr "" -#: ../settings/system/network.rst:15 -msgid "Proxy Address." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.vip}``" msgstr "" -#: ../settings/system/network.rst:12 -msgid "" -"Allows you to provide a proxy server if needed. This is relevant for network " -"communication by Zammad." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Address" msgstr "" -#: ../settings/system/network.rst:15 -msgid "It **does not** affect the update process or Elasticsearch." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.address}``" msgstr "" -#: ../settings/system/network.rst:18 -msgid "Username for proxy connection." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Avatar" msgstr "" -#: ../settings/system/network.rst:18 -msgid "" -"If your proxy server requires authentication, provide the username here." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.avatar(60,60)}``" msgstr "" -#: ../settings/system/network.rst:21 -msgid "Password for proxy connection." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Department" msgstr "" -#: ../settings/system/network.rst:21 -msgid "" -"If your proxy server requires authentication, provide the password here." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.department}``" msgstr "" -#: ../settings/system/network.rst:26 -msgid "No proxy for the following hosts." +#: ../misc/variables/ticket.rst:1 +msgid "``Support`` or empty if not set" msgstr "" -#: ../settings/system/network.rst:24 -msgid "" -"Exception list for hosts you can't or don't want to reach via proxy server." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Email" msgstr "" -#: ../settings/system/network.rst:27 -msgid "Default: ``localhost,127.0.0.0,::1``" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.email}``" msgstr "" -#: ../settings/system/services.rst:2 -msgid "Services" +#: ../misc/variables/ticket.rst:1 +msgid "``agent@company.tld`` or empty if not set" msgstr "" -#: ../settings/system/services.rst:10 -msgid "Image Service" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Fax" msgstr "" -#: ../settings/system/services.rst:5 -msgid "Defines the backend for user and organization image lookups." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.fax}``" msgstr "" -#: ../settings/system/services.rst:7 -msgid "Default: ``Zammad Image Service`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Firstname" msgstr "" -#: ../settings/system/services.rst:9 -msgid "" -"Make sure your on premise installation has ``HTTPS`` access to ``images." -"zammad.com``." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.firstname}``" msgstr "" -#: ../settings/system/services.rst:18 -msgid "Geo Calendar Service" +#: ../misc/variables/ticket.rst:1 +msgid "``Max`` or empty if not set" msgstr "" -#: ../settings/system/services.rst:13 -msgid "" -"Defines the backend for geo calendar lookups. Used for initial calendar " -"setup." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Lastname" msgstr "" -#: ../settings/system/services.rst:16 -msgid "Default: ``Zammad GeoCalendar Service`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.lastname}``" msgstr "" -#: ../settings/system/services.include.rst:2 -msgid "" -"Make sure your on premise installation has ``HTTPS`` access to ``geo.zammad." -"com``." +#: ../misc/variables/ticket.rst:1 +msgid "``Mustermann`` or empty if not set" msgstr "" -#: ../settings/system/services.rst:26 -msgid "Geo IP Service" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Login" msgstr "" -#: ../settings/system/services.rst:21 -msgid "" -"Defines the backend for geo IP lookups. Shows also location of an IP address " -"if an IP address is shown." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.login}``" msgstr "" -#: ../settings/system/services.rst:24 -msgid "Default: ``Zammad GeoIP Service`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "``agent``" msgstr "" -#: ../settings/system/services.rst:32 -msgid "Geo Location Service" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Mobile" msgstr "" -#: ../settings/system/services.rst:29 -msgid "" -"Defines the backend for geo location lookups to store geo locations for " -"addresses." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.mobile}``" msgstr "" -#: ../settings/system/services.rst:32 -msgid "" -"Default: ``OpenStreetMap (ODbL 1.0, http://osm.org/copyright)`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Note" msgstr "" -#: ../settings/system/services.rst:36 -msgid "" -"You can find a detailed privacy information on what we store for how long on " -"our :docs:`Privacy Appendix ` inside of our System " -"Documentation." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.note}``" msgstr "" -#: ../settings/system/storage.rst:2 -msgid "Storage" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Phone" msgstr "" -#: ../settings/system/storage.rst:6 -msgid "" -"Here you can define where Zammad stores attachments for tickets and the " -"knowledge base. By default, we're writing to the ``Database`` - you can " -"switch to ``Filesystem`` or ``Simple Storage (S3)`` at any time. In this " -"case please have a look on the following instructions." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.phone}``" msgstr "" -#: ../settings/system/storage.rst:11 -msgid "" -"If you have a busy Zammad instance, we strongly encourage you to use " -"filesystem storage instead of \"Database\". This will greatly improve system " -"performance (de-crease database load and size)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > VIP" msgstr "" -#: ../settings/system/storage.rst:19 -msgid "Database" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.vip}``" msgstr "" -#: ../settings/system/storage.rst:17 -msgid "" -"This is the default storage method. The attachments are stored directly in " -"the database. If your Zammad instance grows, we recommend one of the other " -"methods to maintain performance." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Web" msgstr "" -#: ../settings/system/storage.rst:38 -msgid "Filesystem" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.web}``" msgstr "" -#: ../settings/system/storage.rst:22 -msgid "" -"This storage method is recommended for all Zammad instances, especially for " -"those with a higher load. If you choose filesystem, your files are written " -"to ``/opt/zammad/storage/``." +#: ../misc/variables/ticket.rst:1 +msgid "``https://zammad.com`` or empty if not set" msgstr "" -#: ../settings/system/storage.rst:26 -msgid "" -"Moving attachments from \"Database\" to \"Filesystem\" can be run during " -"production use. However, you should consider your framework conditions (e.g. " -"bandwidth, system load in production) to define the right moment." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Pending till" msgstr "" -#: ../settings/system/storage.rst:32 -msgid "**You noticed slow updates of Zammad?**" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.pending_time}``" msgstr "" -#: ../settings/system/storage.rst:34 -msgid "" -"While Zammad is beeing updated, it enforces a recursive \"change " -"owner\" (chown) for this directory. For instances with many files this can " -"be time consuming. To mitigate that you can move your files and create a " -"symlink in ``/opt/zammad/storage/`` to the new directory. Of course you have " -"to make sure on your own that the permissions are always correct." +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not set" msgstr "" -#: ../settings/system/storage.rst:95 -msgid "Simple Storage (S3)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Priority > Name" msgstr "" -#: ../settings/system/storage.rst:41 -msgid "" -"To use the Simple Storage (S3), you have to provide some settings, which " -"can't be accessed in the UI (see instructions below)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.priority.name}``" msgstr "" -#: ../settings/system/storage.rst:44 -msgid "" -"⚠️ Please note that the current implementation is in its early stages and can " -"be modified in the future." +#: ../misc/variables/ticket.rst:1 +msgid "``2 normal``" msgstr "" -#: ../settings/system/storage.rst:47 -msgid "" -"The prerequisite is to have access to a S3-compatible storage and to have " -"all necessary parameters available (which depends on your storage provider; " -"if in doubt, please ask there for help)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > State > Name" msgstr "" -#: ../settings/system/storage.rst:51 -msgid "Steps to configure S3:" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.state.name}``" msgstr "" -#: ../settings/system/storage.rst:53 -msgid "" -"Copy ``config/zammad/storage.yml.dist`` to ``config/zammad/storage.yml``" +#: ../misc/variables/ticket.rst:1 +msgid "``new``, ``open``, ..." msgstr "" -#: ../settings/system/storage.rst:54 -msgid "Edit the copied file in one of the following ways:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Tags" msgstr "" -#: ../settings/system/storage.rst:56 -msgid "" -"Either provide your S3 configuration with one attribute per line like in the " -"upper area of the file" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.tags}``" msgstr "" -#: ../settings/system/storage.rst:58 +#: ../misc/variables/ticket.rst:1 msgid "" -"Or provide your S3 configuration as an URL (which you can find at the end of " -"the file). Note: you can also provide this URL as environment variable (:" -"docs:`see system documentation `) without using this yml-file." +"Currently not available, see `Issue 2769 `_" msgstr "" -#: ../settings/system/storage.rst:62 -msgid "" -"We recommend the deletion of the not used configuration style to avoid " -"inconsistencies." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Title" msgstr "" -#: ../settings/system/storage.rst:65 -msgid "Restart Zammad so the config file / environment variable is loaded" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.title}``" msgstr "" -#: ../settings/system/storage.rst:66 +#: ../misc/variables/ticket.rst:1 msgid "" -"Set the \"Storage Method\" in Zammad to ``Simple Storage (S3)`` in Settings " -"> System > Storage and click on \"Submit\". After that, Zammad checks your " -"configuration and the connection to the service and will raise an error " -"message if something is wrong." +"``My amazing Subject`` (normally subject, can be edited within Interface and " +"thus differ)" msgstr "" -#: ../settings/system/storage.rst:72 -msgid "A very simple storage configuration could look like this:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated at" msgstr "" -#: ../settings/system/storage.rst:85 -msgid "" -"Before setting the storage method to ``Simple Storage (S3)`` (step 4), " -"please make sure to have a working setup." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_at}``" msgstr "" -#: ../settings/system/storage.rst:88 -msgid "" -"You can verify this by running ``rails r 'Rails.logger = Logger.new(STDOUT); " -"pp Store::Provider::S3.ping?'`` in your Zammad directory. If everything is " -"fine, you should see ``true``, else you should see ``false`` and a simple " -"error message." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Address" msgstr "" -#: ../settings/system/storage.rst:93 -msgid "" -"If you installed Zammad through a package manager (rather than from source), " -"replace ``rails r`` with ``zammad run rails r`` above. To learn more, see :" -"docs:`Administration via Console `." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.address}``" msgstr "" -#: ../settings/ticket.rst:4 -msgid "" -"Here you can adjust general ticket settings. Additional ones for the ticket " -"composer interface can be found in the :doc:`/misc/composer`." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Avatar" msgstr "" -#: ../settings/ticket.rst:11 -msgid "Ticket Hook (default: ``Ticket#``)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.avatar(60,60)}``" msgstr "" -#: ../settings/ticket.rst:11 -msgid "The identifier for a ticket; *e.g.,* Ticket#, Call#, MyTicket#." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Department" msgstr "" -#: ../settings/ticket.rst:38 -msgid "Ticket Hook Position (default: ``right``)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.department}``" msgstr "" -#: ../settings/ticket.rst:14 -msgid "" -"With this setting you can decide (if) where to insert the ticket number." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Email" msgstr "" -#: ../settings/ticket.rst:20 -msgid "*Right*" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.email}``" msgstr "" -#: ../settings/ticket.rst:17 -msgid "" -"This setting will add the ticket reference on the right site of the subject." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Fax" msgstr "" -#: ../settings/ticket.rst:20 -msgid "Example: ``Some Subject [Ticket#12345]``" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.fax}``" msgstr "" -#: ../settings/ticket.rst:26 -msgid "*Left*" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Firstname" msgstr "" -#: ../settings/ticket.rst:23 -msgid "" -"This setting will add the ticket reference on the left site of the subject." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.firstname}``" msgstr "" -#: ../settings/ticket.rst:26 -msgid "Example: ``[Ticket#12345] Some Subject``" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Lastname" msgstr "" -#: ../settings/ticket.rst:29 -msgid "*None*" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.lastname}``" msgstr "" -#: ../settings/ticket.rst:29 -msgid "This will completely remove ticket references from the subject." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Login" msgstr "" -#: ../settings/ticket.rst:33 -msgid "" -"Please ensure to take a look at :doc:`/channels/email/settings` within the " -"email channel to ensure you have at least one reference that helps Zammad to " -"assign follow-ups correctly." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.login}``" msgstr "" -#: ../settings/ticket.rst:37 -msgid "" -"Disabling this and not setting up any further follow up search will lead to " -"unexpected results!" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Mobile" msgstr "" -#: ../settings/ticket.rst:65 -msgid "" -"Ticket Last Contact Behaviour (default: ``Use the start time of the last " -"customer thread (which may consist of multiple articles).``)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.mobile}``" msgstr "" -#: ../settings/ticket.rst:41 -msgid "" -"This setting changes the way Zammad updates the ``Last Contact`` value of a " -"ticket. This is fairly important for overviews and what you expect upon " -"ticket updates of a customer." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Note" msgstr "" -#: ../settings/ticket.rst:52 -msgid "" -"Use the start time of the last customer thread (which may consist of " -"multiple articles)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.note}``" msgstr "" -#: ../settings/ticket.rst:46 -msgid "" -"If this option is chosen, Zammad will update the last updated value just " -"once if a customer replies. After that, Zammad will wait for an agent to " -"react." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Phone" msgstr "" -#: ../settings/ticket.rst:50 -msgid "" -"This comes in handy if you want to work tickets in the order of their first " -"update. This will not change ticket orders if customers decide to \"bump\" " -"the ticket affected." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.phone}``" msgstr "" -#: ../settings/ticket.rst:57 -msgid "Use the time of the very last customer article." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > VIP" msgstr "" -#: ../settings/ticket.rst:55 -msgid "" -"When setting this option, Zammad will always update the last updated value. " -"This means that if ordering by ``Last Update``, ticket orders will change if " -"customers \"bump\" the ticket." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.vip}``" msgstr "" -#: ../settings/ticket.rst:64 -msgid "Last contact value used on :doc:`/manage/overviews`" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Web" msgstr "" -#: ../settings/ticket.rst:65 -msgid "Last contact value used on :doc:`/manage/trigger`" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.web}``" msgstr "" -#: ../settings/ticket.rst:88 -msgid "" -"Ticket Organization Reassignment (default: ``Update the most recent tickets." -"``)" +#: ../settings/branding.rst:10 +msgid "Product Name" msgstr "" -#: ../settings/ticket.rst:68 +#: ../settings/branding.rst:7 msgid "" -"This setting changes the way Zammad updates the organization field of the " -"tickets whenever the primary organization of a user is changed." -msgstr "" - -#: ../settings/ticket.rst:74 -msgid "Update the most recent tickets." +"Defines the name of the application, shown in the web interface, tabs and " +"title bar of the web browser." msgstr "" -#: ../settings/ticket.rst:72 -msgid "" -"If this option is chosen, Zammad will update the 100 most recent tickets " -"where the user is the ticket customer. The ticket organization field will be " -"automatically set to the new primary organization of the user." +#: ../settings/branding.rst:10 +msgid "Default value: ``Zammad Helpdesk``" msgstr "" -#: ../settings/ticket.rst:88 -msgid "Do not update any tickets." +#: ../settings/branding.rst:13 +msgid "Will be shown in the app and is included in email footers." msgstr "" -#: ../settings/ticket.rst:77 -msgid "" -"When choosing this option, Zammad will not update any tickets when the " -"user's primary organization is changed." +#: ../settings/branding.rst:19 +msgid "Logo" msgstr "" -#: ../settings/ticket.rst:80 -msgid "**Use with care!**" +#: ../settings/branding.rst:16 +msgid "Defines the logo of the application, shown in the login page of Zammad." msgstr "" -#: ../settings/ticket.rst:82 +#: ../settings/branding.rst:18 msgid "" -"Using this option may lead to inconsistencies in the system as the ticket " -"organization may become decoupled from the ticket customer." +"Ensure to hit the \"Submit\" button after uploading the logo. Otherwise your " +"change will not be saved." msgstr "" -#: ../settings/ticket.rst:85 +#: ../settings/branding.rst:22 msgid "" -"However, you may use this option if you wish to maintain :ref:`the shared " -"access ` to the ticket for all organization " -"members of the original organization of the customer." +"Allows to set the default language of the Zammad instance. The here defined " +"locale mostly acts as a fallback for:" msgstr "" -#: ../settings/ticket.rst:110 -msgid "Ticket Number Format (default: ``Increment (SystemID.Counter)``)" +#: ../settings/branding.rst:25 +msgid "user preferences (if Zammad can't detect the users locale)" msgstr "" -#: ../settings/ticket.rst:94 -msgid "" -"This setting defines the way Zammad's ticket number will look. Changing this " -"setting in production will cause follow up detection to fail." +#: ../settings/branding.rst:26 +msgid "CSV output (reporting, time accounting)" msgstr "" -#: ../settings/ticket.rst:102 -msgid "Increment (SystemID.Counter)" +#: ../settings/branding.rst:30 +msgid "Define the timezone of your Zammad installation." msgstr "" -#: ../settings/ticket.rst:98 +#: ../settings/branding.rst:32 msgid "" -"The increment value contains the SystemID (automatically generated during " -"installation) and a increment which counts up with every new Ticket. The " -"increment will automatically get another digit if needed." +"This does not have any effect on timings for your agents or how Zammad " +"stores date and time values." msgstr "" -#: ../settings/ticket.rst:102 -msgid "Examples: ``1010138``, ``1010139``" +#: ../settings/branding.rst:35 +msgid "Changing this value has direct consequences on the following areas:" msgstr "" -#: ../settings/ticket.rst:110 -msgid "Date (Year.Month.Day.SystemID.Counter)" +#: ../settings/branding.rst:37 +msgid ":doc:`/manage/scheduler` tasks" msgstr "" -#: ../settings/ticket.rst:105 -msgid "" -"This version of the ticket number is fairly long. However, because it " -"contains the date of ticket creation, it also allows you to see when the " -"ticket has been created. You may feel familiar with this number format if " -"you've worked with OTRS already." +#: ../settings/branding.rst:38 +msgid "search indexing (and thus reporting)" msgstr "" -#: ../settings/ticket.rst:110 -msgid "Examples: ``201206231010138``, ``201206231010139``" +#: ../settings/branding.rst:40 +msgid "calendar subscriptions" msgstr "" -#: ../settings/ticket.rst:137 -msgid "OPTIONS" +#: ../settings/branding.rst:41 +msgid "browser printing" msgstr "" -#: ../settings/ticket.rst:113 +#: ../settings/branding.rst:43 msgid "" -"The below options allow you to further customize your ticket number. The " -"availability of options differ depending of the chosen ticket number format " -"above." +"Please note that some of above are fallbacks in case Zammad could not detect " +"the agents timezone correctly." msgstr "" -#: ../settings/ticket.rst:122 -msgid "Checksum (default: ``no``)" +#: ../settings/branding.rst:77 +msgid "Pretty Date" msgstr "" -#: ../settings/ticket.rst:118 +#: ../settings/branding.rst:47 msgid "" -"If set to yes, we'll built a checksum to further \"unique\" the ticket " -"number of your system. If you're dealing with many other ticket systems this " -"might help to prevent false positive follow up detection on tickets." +"This setting allows you to define how Zammad should display time stamps " +"within the interface to all users." msgstr "" -#: ../settings/ticket.rst:122 -msgid "This will also add another digit to the ticket number." +#: ../settings/branding.rst:50 +msgid "" +"This does not have any effect on how Zammad returns e.g. time values via " +"variables." msgstr "" -#: ../settings/ticket.rst:137 -msgid "Min. size of Number (default: ``5``)" +#: ../settings/branding.rst:77 +msgid "Choose in between the following options:" msgstr "" -#: ../settings/ticket.rst:125 -msgid "" -"This setting defines the minimum length of your ticket number. If your " -"counter is not yet high enough, Zammad will fill the number with zeros to " -"ensure the wanted length." +#: ../settings/branding.rst:64 +msgid "relative" msgstr "" -#: ../settings/ticket.rst:129 +#: ../settings/branding.rst:55 msgid "" -"Please note that the minimum length is ``3`` (SystemID + at least one digit " -"if below 10). Also, if the length is no longer long enough, the number will " -"automatically get one digit longer. Ticket-Numbers **do not overflow**, thus " -"it's save to keep it at 5 or set it lower if wanted." +"This timestamp shows a relative time span until it switches to a date. Over " +"time, it will change as follows:" msgstr "" -#: ../settings/ticket.rst:135 -msgid "" -"This option is only available if ticket number format is set to " -"``Increment``!" +#: ../settings/branding.rst:58 +msgid "just now" msgstr "" -#: ../settings/ticket.rst:142 -msgid "Auto-Assignment" +#: ../settings/branding.rst:59 +msgid "5 minutes ago" msgstr "" -#: ../settings/ticket.rst:144 -msgid "" -"In a larger Zammad environment, it happens that several agents open the same " -"ticket at the same time. Although collision detection is then effective, the " -"efficiency of processing can be increased by means of the automatic " -"assignment of tickets when a ticket is opened." +#: ../settings/branding.rst:60 +msgid "3 days 1 hour ago" msgstr "" -#: ../settings/ticket.rst:149 -msgid "" -"The automatic assignment of tickets can be activated and configured in the " -"admin area under Settings > Ticket > Auto Assignment." +#: ../settings/branding.rst:61 +msgid "``03/04/2022``" msgstr "" -#: ../settings/ticket.rst:152 -msgid "" -"The auto assignment only works if the ticket has no owner yet. By default, " -"the agent can always reset the ticket owner to ``-`` if needed." +#: ../settings/branding.rst:63 +msgid "Hovering the timestamp helps, you'll always get a clean timestamp then." msgstr "" -#: ../settings/ticket.rst:155 -msgid "" -"If you want to use this function for only specific tickets, you can " -"configure the conditions accordingly to meet your requirement. By default " -"the condition affects all tickets with the state ``open``." +#: ../settings/branding.rst:71 +msgid "absolute" msgstr "" -#: ../settings/ticket.rst:161 +#: ../settings/branding.rst:67 msgid "" -"If you need to exclude users (e.g. a group leader), you can search and " -"select the desired agents in the ``Exception Users`` list. The search " -"function in this area is only effective, if you have too many agents to " -"display at once to help you with the configuration." +"This timestamp always includes the week day. For one week after creation, " +"the timestamp will not contain the date itself: Thursday 18:35." msgstr "" -#: ../settings/ticket.rst:167 -msgid "Notifications" +#: ../settings/branding.rst:71 +msgid "After a week it will switch to: ``Friday 4. Mar 16:00``." msgstr "" -#: ../settings/ticket.rst:191 -msgid "Default Notifications" +#: ../settings/branding.rst:76 +msgid "timestamp" msgstr "" -#: ../settings/ticket.rst:170 +#: ../settings/branding.rst:74 msgid "" -"This setting allows you to configure the default ticket notifications that " -"will be applied to all new agent users (incl. users who were just assigned " -"agent role). Simply change the notification matrix to desired state and " -"press **Save**." +"This will cause Zammad to show a complete timestamp according to your locale " +"defaults. For English this could be e.g. ``2022/12/03 2:40 pm`` or for " +"German e.g. ``12.03.2022 14:40``." msgstr "" -#: ../settings/ticket.rst:175 -msgid "" -"In case an agent already exists, their ticket notification preferences will " -"be preserved. Optionally, you can also **Apply current defaults to all " -"agents**." +#: ../settings/branding.rst:78 +msgid "Default setting: ``relative``." msgstr "" -#: ../settings/ticket.rst:181 -msgid "" -"**Potential time-consuming action:** Applying default ticket notifications " -"to all agent users may take some time to complete, be patient! The exact " -"time will depend on the size of your system and the number of agents." +#: ../settings/security.rst:2 +msgid "Security" msgstr "" -#: ../settings/ticket.rst:185 +#: ../settings/security.rst:4 msgid "" -"**Active agents only!** When current default ticket notifications are " -"applied, only active agent users are considered. In case an agent is re-" -"activated *after* this action, they will still have the old notification " -"configuration." +"For your overview we split each tab within security settings into its own " +"page:" msgstr "" -#: ../settings/ticket.rst:190 +#: ../settings/security/base.rst:2 ../settings/system/base.rst:2 +#: ../settings/ticket.rst:8 +msgid "Base" +msgstr "" + +#: ../settings/security/base.rst:5 +msgid "New User Accounts" +msgstr "" + +#: ../settings/security/base.rst:9 msgid "" -"In case you want to go back to the initial state of ticket notifications, " -"you can click on **Reset to default** button." +"Activates the `register as a new customer` function on the login page. If " +"set to ``no`` only administrators or agents can create new accounts manually." msgstr "" -#: ../settings/ticket.rst:194 ../settings/ticket.rst:196 -msgid "Duplicate Detection" +#: ../settings/security/base.rst:13 ../settings/security/base.rst:38 +#: ../settings/security/base.rst:66 +msgid "Default setting: ``yes``" msgstr "" -#: ../settings/ticket.rst:236 ../settings/ticket.rst:238 -msgid "Detect Duplicate Ticket Creation" +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"New User Accounts\" setting" msgstr "" -#: ../settings/ticket.rst:197 ../settings/ticket.rst:199 +#: ../settings/security/base.rst:22 msgid "" -"This setting turns on the duplicate ticket detection mechanism during ticket " -"creation. If similar tickets are found in the system, a suitable warning " -"will be shown to the user trying to create a ticket." +"Deactivation of above function **does not** deactivate automatic account " +"creation! This means: If a user writes e.g. an email to Zammad and has no " +"account yet, Zammad will automatically create the account. User accounts are " +"a direct dependency of tickets and thus technically mandatory." msgstr "" -#: ../settings/ticket.rst:204 ../settings/ticket.rst:206 -msgid "A Sample Duplicate Ticket Warning" +#: ../settings/security/base.rst:29 +msgid "Lost Password" msgstr "" -#: ../settings/ticket.rst:206 ../settings/ticket.rst:208 +#: ../settings/security/base.rst:33 msgid "" -"You can choose which ticket attributes will be matched by selecting them in " -"**Attributes to compare** field. Only if the ticket attribute value provided " -"by the user in the ticket create form is *equal* with the attribute in an " -"existing ticket, the warning will be shown." +"Activates the `lost password` function on the login page. If set to ``no`` " +"only administrators may change the user's password - users may update their " +"own password if they're still logged in and they have the required :doc:" +"`permission `." msgstr "" -#: ../settings/ticket.rst:211 ../settings/ticket.rst:213 -msgid "**Warning title** and **Warning message** are configurable as well." +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"Lost Password\" setting" msgstr "" -#: ../settings/ticket.rst:213 ../settings/ticket.rst:215 +#: ../settings/security/base.rst:49 msgid "" -"You can limit the detection only to certain user roles. By default, only " -"agents will see the warning." +"With third party authentications - but especially LDAP - you may want to " +"disable this function. Zammad **will not** change third party login " +"passwords and instead set or change the local password!" msgstr "" -#: ../settings/ticket.rst:216 ../settings/ticket.rst:218 -msgid "" -"If you don't want to show the matched tickets as part of the warning, you " -"can set **Show matching ticket(s) in the warning** setting to *no*." +#: ../settings/security/base.rst:56 +msgid "Password Login" msgstr "" -#: ../settings/ticket.rst:219 ../settings/ticket.rst:221 +#: ../settings/security/base.rst:60 msgid "" -"By default, **Permission level for looking up ticket** is set to *User*, " -"which means user permissions will be honored during sarch. The user will " -"see the warning only if tickets they have access to are matched. " -"Alternatively, you can set this setting to *System*, in which case the " -"search will happen within *all* tickets in the system, regardless of user " -"permissions." +"Activates the username & password login by default and if no third-party " +"login is activated. Disabling password login on the Zammad login page only " +"takes effect if you enable any :doc:`third-party`." msgstr "" -#: ../settings/ticket.rst:225 ../settings/ticket.rst:227 -msgid "**🦺 Safety first!**" +#: ../settings/security/base.rst:64 +msgid "See :doc:`third-party` for supported third-party logins." msgstr "" -#: ../settings/ticket.rst:227 ../settings/ticket.rst:229 -msgid "" -"Even if the permission level is set to *System*, the user will not be shown " -"the tickets they don't have access to in the warning, even if they match." +#: ../settings/security/base.rst:0 +msgid "Figure showing de-activated \"Password Login\" setting" msgstr "" -#: ../settings/ticket.rst:231 ../settings/ticket.rst:233 +#: ../settings/security/base.rst:77 msgid "" -"However, just the confirmation about the existence of the tickets in the " -"system may be considered an unwanted information disclosure. Use this option " -"carefully!" +"To help administrators to overcome \"login issues\", Zammad automatically " +"offers a password request for administrator users. This allows you to adjust " +"Third-Party applications even if the login does no longer work!" msgstr "" -#: ../settings/ticket.rst:235 ../settings/ticket.rst:237 -msgid "" -"Finally, you can configure between matching within **All tickets** or **Open " -"tickets** only by setting **Match tickets in following states**. Depending " -"on the current ticket state, a ticket may or not be matched." +#: ../settings/security/base.rst:84 +msgid "Session Timeout" msgstr "" -#: ../system/core-workflows.rst:2 -msgid "Core Workflows" +#: ../settings/security/base.rst:86 +msgid "" +"All settings below by default are set to ``4 weeks``. Session Timeout " +"defines the life time of a users session. As soon as it's reached, Zammad " +"will automatically log off the session in question." msgstr "" -#: ../system/core-workflows.rst:4 +#: ../settings/security/base.rst:91 msgid "" -"Core Workflows allow you to adjust object attributes in many ways. For " -"example:" +"Zammad takes the highest value set assigned for the user based on the " +"permissions." msgstr "" -#: ../system/core-workflows.rst:7 -msgid "show / hide fields" +#: ../settings/security/base.rst:94 +msgid "``admin``" msgstr "" -#: ../system/core-workflows.rst:8 -msgid "adjust mandatory setting" +#: ../settings/security/base.rst:96 +msgid "``ticket.customer``" msgstr "" -#: ../system/core-workflows.rst:9 -msgid "manipulate available options" +#: ../settings/security/base.rst:97 +msgid "``default`` (fallback if user doesn't have above permissions set)" msgstr "" -#: ../system/core-workflows.rst:11 +#: ../settings/security/base.rst:99 msgid "" -"With this, you can provide exactly the information your users really need!" +"All settings act independently from each other allowing you to disable the " +"timeouts for e.g. admins, but not agents." msgstr "" -#: ../system/core-workflows.rst:15 -msgid "" -"If the pre-defined :doc:`/system/objects` are not enough, please add them " -"beforehand." +#: ../settings/security/base.rst:115 +#: ../system/integrations/checkmk/api-reference.rst:13 +msgid "Example" msgstr "" -#: ../system/core-workflows.rst:17 -msgid "" -"If you experience slow or unreliable field updates, please see :ref:`Core " -"Workflow Ajax Modus `" +#: ../settings/security/base.rst:107 +msgid "Let's suppose you configured the following session timeouts" msgstr "" -#: ../system/core-workflows.rst:22 -msgid "" -"This is a very enhanced functionality and can cause unexpected UI behavior. " -"Please ensure to test your use cases after configuration to reduce surprises." +#: ../settings/security/base.rst:104 +msgid "default: 3 weeks" msgstr "" -#: ../system/core-workflows.rst:None -msgid "Dialogue for adding a new workflow" +#: ../settings/security/base.rst:105 +msgid "admin: 2 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:2 -msgid "Core Workflow Condition Operators" +#: ../settings/security/base.rst:106 +msgid "ticket.agent: 4 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:4 -msgid "" -"You might know that there is a separate section for explaining :doc:" -"`condition operators `. Head over there to " -"see a detailed explanation of many conditions and operators." +#: ../settings/security/base.rst:107 +msgid "ticket.customer: 1 week" msgstr "" -#: ../system/core-workflows/condition-operators.rst:8 -msgid "" -"Due to differences to other places in Zammad which are also using conditions " -"(e.g. triggers), you can find a dedicated description of operators for core " -"workflows below." +#: ../settings/security/base.rst:115 +msgid "This results in the following situations" msgstr "" -#: ../system/core-workflows/condition-operators.rst:12 -msgid "" -"Be aware that the availability of the operators depends on the selected " -"attribute and its field type. Some of the operators may only be available " -"for system attributes (e.g. for \"tags\", \"active\")." +#: ../settings/security/base.rst:110 +msgid "a user with ``admin`` permission will have a timeout of 2 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:20 -msgid "Operator" +#: ../settings/security/base.rst:111 +msgid "" +"a user with ``admin`` and ``ticket.agent`` permissions will have a timeout " +"of 2 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:22 -msgid "after (absolute)" +#: ../settings/security/base.rst:113 +msgid "" +"a user with ``ticket.customer`` permission will have a timeout of 1 week" msgstr "" -#: ../system/core-workflows/condition-operators.rst:23 -msgid "Matches if a date/time is after a specific point in time." +#: ../settings/security/base.rst:115 +msgid "" +"a user with neither ``admin``, ``ticket.agent`` nor ``ticket.customer`` " +"permissions will have a timeout of 3 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:24 -msgid "after (relative)" +#: ../settings/security/password.rst:4 +msgid "" +"This section allows you to define password requirements for the local user " +"accounts." msgstr "" -#: ../system/core-workflows/condition-operators.rst:25 -msgid "Matches if a time span after a specified event has passed." +#: ../settings/security/password.rst:9 +msgid "" +"Zammad does **not** allow you to change your LDAP password, instead, it will " +"set a password in its local database which might confuse your users. This " +"might be addressed in the future by `#1169 `_." msgstr "" -#: ../system/core-workflows/condition-operators.rst:26 -msgid "before (absolute)" +#: ../settings/security/password.rst:14 +msgid "**Exception for admins**" msgstr "" -#: ../system/core-workflows/condition-operators.rst:27 -msgid "Matches if a date/time is before a specific point in time." +#: ../settings/security/password.rst:16 +msgid "" +"Please note that below password policies *do not* affect administrators " +"setting passwords on user accounts. While this seems strange and not safe we " +"believe that an administrator knowing an user's password is insecure as well." msgstr "" -#: ../system/core-workflows/condition-operators.rst:28 -msgid "before (relative)" +#: ../settings/security/password.rst:21 +msgid "The suggested workflow is either:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:29 -msgid "Matches if a time span after a specified event has not passed." +#: ../settings/security/password.rst:23 +msgid "" +"to use third party logins to not require local passwords at all **- or -**" msgstr "" -#: ../system/core-workflows/condition-operators.rst:30 -msgid "contains" +#: ../settings/security/password.rst:25 +msgid "to require your *user to reset the password* upon first login." msgstr "" -#: ../system/core-workflows/condition-operators.rst:31 -msgid "Matches if a specified value is present." +#: ../settings/security/password.rst:27 +msgid "" +"This way administrators are not required to set a user's password at all!" msgstr "" -#: ../system/core-workflows/condition-operators.rst:33 -msgid "Matches if all of the specified values are present." +#: ../settings/security/password.rst:31 +msgid "Maximum Failed Logins" msgstr "" -#: ../system/core-workflows/condition-operators.rst:35 -msgid "Matches if none of the specified values are present." +#: ../settings/security/password.rst:33 +msgid "" +"You can choose a value between ``4`` and ``20``. This defines how often a " +"login to a user account may fail until Zammad will lock it. Your users can " +"always use the \"forgot password\" function to change their password and " +"unlock their account." msgstr "" -#: ../system/core-workflows/condition-operators.rst:36 -msgid "contains not" +#: ../settings/security/password.rst:38 +msgid "The default value is ``10``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:37 -msgid "Matches if a specified value is not present." +#: ../settings/security/password.rst:42 +msgid "Beside changing the user's password, you can also unlock accounts via" msgstr "" -#: ../system/core-workflows/condition-operators.rst:39 -msgid "Matches if one specified value is present." +#: ../settings/security/password.rst:44 +msgid ":ref:`user management list `" msgstr "" -#: ../system/core-workflows/condition-operators.rst:41 -msgid "Matches if one specified value is not present." +#: ../settings/security/password.rst:45 +msgid ":docs:`console `" msgstr "" -#: ../system/core-workflows/condition-operators.rst:42 -msgid "does not match regex" +#: ../settings/security/password.rst:46 +msgid ":docs:`API `" msgstr "" -#: ../system/core-workflows/condition-operators.rst:43 -msgid "Matches if content doesn't fit to regex rule." +#: ../settings/security/password.rst:50 +msgid "Failed logins via LDAP no longer lock accounts." msgstr "" -#: ../system/core-workflows/condition-operators.rst:44 -msgid "ends with" +#: ../settings/security/password.rst:53 +msgid "2 Lower Case And 2 Upper Case Characters" msgstr "" -#: ../system/core-workflows/condition-operators.rst:45 -msgid "Matches if content ends with specified value." +#: ../settings/security/password.rst:55 +msgid "" +"You can add complexity to passwords by enforcing at least 2 upper and lower " +"case characters." msgstr "" -#: ../system/core-workflows/condition-operators.rst:46 -msgid "ends with one of" +#: ../settings/security/password.rst:58 ../settings/security/password.rst:83 +msgid "The default value is ``no``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:47 -msgid "Matches if content ends with one of the specified values." +#: ../settings/security/password.rst:62 +msgid "Minimum Length" msgstr "" -#: ../system/core-workflows/condition-operators.rst:48 -msgid "from (relative)" +#: ../settings/security/password.rst:64 +msgid "" +"This defines the minimum password length required for users to provide (from " +"``4`` to ``20``)." msgstr "" -#: ../system/core-workflows/condition-operators.rst:49 -msgid "Matches if date/time is after a period of time after an event." +#: ../settings/security/password.rst:67 +msgid "The default value is ``6``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:51 -msgid "Matches if content is equal to a specified value." +#: ../settings/security/password.rst:71 +msgid "Digit Required" msgstr "" -#: ../system/core-workflows/condition-operators.rst:52 -msgid "is any of" +#: ../settings/security/password.rst:73 +msgid "This enforces your users to use at least one digit within the password." msgstr "" -#: ../system/core-workflows/condition-operators.rst:53 -msgid "Matches if content is equal to any of specified values." +#: ../settings/security/password.rst:75 +msgid "The default value is ``yes``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:54 -msgid "is modified" +#: ../settings/security/password.rst:78 +msgid "Special Character Required" msgstr "" -#: ../system/core-workflows/condition-operators.rst:55 -msgid "Matches if content is modified." +#: ../settings/security/password.rst:80 +msgid "" +"This setting allows you to improve your password quality even more by " +"enforcing the password to contain at least one special character." msgstr "" -#: ../system/core-workflows/condition-operators.rst:57 -#: ../system/core-workflows/condition-operators.rst:61 -msgid "True from the moment of changing content until form submit." +#: ../settings/security/ssl-certificates.rst:2 +msgid "SSL Certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:58 -msgid "is modified to" +#: ../settings/security/ssl-certificates.rst:7 +msgid "" +"Zammad offers the possibility to upload custom certificates and custom " +"Certificate Authority (CA) certificates. This can be useful if you want to " +"connect Zammad the secure way to other systems which are using custom " +"certificates." msgstr "" -#: ../system/core-workflows/condition-operators.rst:59 -msgid "Matches if content is modified to a specific value." +#: ../settings/security/ssl-certificates.rst:12 +msgid "" +"An example usecase might be: You have an internal LDAP server that is not " +"accessible from the internet, and you want a SSL-encrypted connection, using " +"a custom certificate." msgstr "" -#: ../system/core-workflows/condition-operators.rst:62 -msgid "is none of" +#: ../settings/security/ssl-certificates.rst:19 +msgid "" +"You should have an existing custom certificate file and/or a custom CA " +"certificate file, which you want to add to Zammad. As filetype ``.crt`` is " +"supported and the certificate format has to be PEM (Base64 ASCII)." msgstr "" -#: ../system/core-workflows/condition-operators.rst:63 -msgid "Matches if content is none of any specified values." +#: ../settings/security/ssl-certificates.rst:25 +msgid "" +"When you import a custom CA certificate, all certificates generated with " +"this are trusted. This can be useful if you have more than one system/" +"certificate you want to connect to and the certificates are issued from the " +"same custom CA." msgstr "" -#: ../system/core-workflows/condition-operators.rst:65 -msgid "Matches if content is not equal to a specified value." +#: ../settings/security/ssl-certificates.rst:31 +msgid "Add a Certificate" msgstr "" -#: ../system/core-workflows/condition-operators.rst:67 -msgid "Matches if content is present." +#: ../settings/security/ssl-certificates.rst:33 +msgid "" +"To add a custom certificate or a custom CA certificate, head over to the " +"Admin panel > Settings > Security > SSL Certificates. Here you can find a " +"\"Add SSL Certificate\" button. In the dialog you can either select a " +"certificate file or paste the content of the certificate:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:68 -msgid "just changed" +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate adding dialog" msgstr "" -#: ../system/core-workflows/condition-operators.rst:69 -msgid "Matches if content has changed." +#: ../settings/security/ssl-certificates.rst:43 +msgid "" +"After selecting a file or pasting the content of the certificate, click on " +"the \"Add\" button to finally upload it to Zammad. Then, the certificates " +"are immediately effective, no restart or similar required." msgstr "" -#: ../system/core-workflows/condition-operators.rst:71 -#: ../system/core-workflows/condition-operators.rst:75 +#: ../settings/security/ssl-certificates.rst:49 msgid "" -"Only true for the moment of changing content until next form field action/" -"click." +"Please note that only single certificate files are supported. That means if " +"you want to import a certificate / CA certificate, it must contain **only " +"one** certificate." msgstr "" -#: ../system/core-workflows/condition-operators.rst:72 -msgid "just changed to" +#: ../settings/security/ssl-certificates.rst:54 +msgid "Certificate Overview" msgstr "" -#: ../system/core-workflows/condition-operators.rst:73 -msgid "Matches if content has changed to a specified value." +#: ../settings/security/ssl-certificates.rst:56 +msgid "" +"After you added a certificate, you can see a table with information for each " +"added certificate:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:76 -msgid "matches regex" +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing table of added certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:77 -msgid "Matches if value fits to regex rule." -msgstr "" - -#: ../system/core-workflows/condition-operators.rst:79 -msgid "Matches if no content is present." -msgstr "" - -#: ../system/core-workflows/condition-operators.rst:80 -msgid "starts with" +#: ../settings/security/ssl-certificates.rst:64 +msgid "" +"Here you can download the certificate or delete it, if you don't need it " +"anymore." msgstr "" -#: ../system/core-workflows/condition-operators.rst:81 -msgid "Matches if content starts with specified value." +#: ../settings/security/ssl-certificates.rst:68 +msgid "Deleting Certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:82 -msgid "starts with one of" +#: ../settings/security/ssl-certificates.rst:70 +msgid "" +"If you want to delete a specific certificate, you can do it by clicking on " +"the menu in the actions column and selecting delete:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:83 -msgid "Matches if content starts with one of the specified values." +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate deletion button" msgstr "" -#: ../system/core-workflows/condition-operators.rst:84 -msgid "till (relative)" +#: ../settings/security/ssl-certificates.rst:79 +msgid "Downloading Certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:85 -msgid "Matches if date/time is before a period of time before an event." +#: ../settings/security/ssl-certificates.rst:81 +msgid "" +"If you want to download your certificates, you can do this as well via " +"corresponding action buttons." msgstr "" -#: ../system/core-workflows/condition-operators.rst:86 -msgid "today" +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate download button" msgstr "" -#: ../system/core-workflows/condition-operators.rst:87 -msgid "Matches if date/time is today." +#: ../settings/security/third-party.rst:13 +msgid "Login Providers" msgstr "" -#: ../system/core-workflows/condition-operators.rst:88 -msgid "within last (relative)" +#: ../settings/security/third-party.rst:2 +msgid "Third-Party Applications" msgstr "" -#: ../system/core-workflows/condition-operators.rst:89 +#: ../settings/security/third-party.rst:4 msgid "" -"Matches if date/time content is within specified period of time before now." +"Third party authentication is a great way to help your users to login to " +"Zammad more easily. If the account is yet unknown, Zammad will create a new " +"user automatically, without the user needed to interact (e.g. type in his " +"name). Another big advantage of this feature is that your user doesn't need " +"to remember another password." msgstr "" -#: ../system/core-workflows/condition-operators.rst:91 -msgid "within next (relative)" +#: ../settings/security/third-party.rst:10 +msgid "" +"You can deactivate logging in via :ref:`security_password_login` if any of " +"the mentioned authentication providers are enabled in your instance." msgstr "" -#: ../system/core-workflows/condition-operators.rst:92 +#: ../settings/security/third-party.rst:27 msgid "" -"Matches if date/time content is within specified period of time after now." +"We're currently missing documentation for the following login providers:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:2 -msgid "How do they work?" +#: ../settings/security/third-party.rst:29 +msgid "LinkedIn" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:4 -msgid "" -"Core Workflows are executed according to their priority. If two workflows " -"have the same priority, they are executed in alphabetical order based on " -"their **name**." +#: ../settings/security/third-party.rst:30 +msgid "Weibo" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:8 -msgid "" -"Because of the way Core Workflows work, all changes to attributes are " -"checked with the application server - please see :doc:`limitations` for " -"possible issues." +#: ../settings/security/third-party.rst:35 +msgid "Automatic Account Link on Initial Logon" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:12 +#: ../settings/security/third-party.rst:37 msgid "" -"Below we're talking about settings that are important and not self-" -"explanatory." +"In general there's two possible options for Zammad on how to deal with " +"already known users as they try to authenticate against a third-party " +"application. By default, Zammad will not automatically link \"unknown\" " +"authentication providers to existing accounts." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:17 +#: ../settings/security/third-party.rst:42 msgid "" -"Choose the object context you want to run the workflow in. This will decide " -"on your available attributes and actions." -msgstr "" - -#: ../system/core-workflows/how-do-they-work.rst:20 -msgid "Ticket objects also have access to the ticket customer." +"This means that the user has to manually link authentication providers to " +"their accounts (for more about this :user-docs:`consult the user " +"documentation `)." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:25 +#: ../settings/security/third-party.rst:46 msgid "" -"Choose in which situation the workflow is applied. Contexts can be combined " -"to avoid duplicate workflows." +"Sometimes this doesn't come in handy as this also means you'll receive error " +"messages about \"email address being in use already\" for (yet) unknown " +"third-party authentication methods." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:30 -msgid "Creation mask" +#: ../settings/security/third-party.rst:50 +msgid "" +"If you want to allow your users to always be able to log in, no matter what, " +"you may want to enable ``Automatic account link on initial logon``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:29 +#: ../settings/security/third-party.rst:None msgid "" -"If selected, your conditions and actions will affect all applicable creation " -"masks." +"Screenshot highlighting the \"Automatic account link on initial logon\"\n" +"setting" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:34 -msgid "Edit mask" +#: ../settings/security/third-party.rst:60 +msgid "Automatic Account Linking Notification" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:33 +#: ../settings/security/third-party.rst:64 msgid "" -"If selected, your conditions and actions will affect all applicable edit " -"masks." +"To improve security and your users awareness, you can enable Zammad to " +"notify your users when a new third-party application has been linked to " +"their account." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:39 +#: ../settings/security/third-party.rst:68 msgid "" -"Zammad differentiates between selected and saved conditions. These can be " -"combined wherever needed." +"This notification is sent out once per third-party application. Zammad does " +"also mention the method used, e.g.: ``Microsoft``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:42 -msgid "**⚠️ Restrict workflows to specific roles if needed!**" +#: ../settings/security/third-party.rst:71 +msgid "By default this setting is not active (set to ``no``)." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:44 +#: ../settings/security/third-party.rst:0 msgid "" -"By default and unless configured in conditions, workflow rules are executed " -"for **all roles**. This also affects your customers!" +"Screenshot showing sample notification mail after initial\n" +"third-party linking" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:50 -msgid "Selected Conditions" +#: ../settings/security/third-party.rst:85 +msgid "" +"This notification is only sent if the account in question already exists. If " +"the login via the third-party also creates the missing account, the " +"notification will be skipped." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:48 -msgid "" -"These conditions are based on form values and match if an appropriate " -"selection is made (e.g. choosing another group in the ticket without " -"saving). This applies for drafts (active selection) and currently saved " -"values." +#: ../settings/security/third-party.rst:89 +msgid "This means it only affects:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:64 -msgid "Saved Conditions" +#: ../settings/security/third-party.rst:91 +msgid "manual account linking within the third-party page of the users profile" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:53 +#: ../settings/security/third-party.rst:92 msgid "" -"These conditions only match if the selected values are stored in the " -"database. It ignores the current value or selection of the field, as long as " -"the changes are not saved (e.g. performing field operations for an existing " -"ticket, which is viewed/opened by an agent)." +"logging into an existing local account by utilizing the *automatic account " +"link on initial logon* functionality" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:60 +#: ../settings/security/third-party.rst:None msgid "" -"Keep in mind that the value has to be available in the situation where you " -"need it. Otherwise the condition won't match." +"Screenshot showing the \"automatic account linking notification\"\n" +"setting" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:63 -msgid "" -"Example: you can't perform any actions with *saved condition* on a ticket in " -"creation, because there are no saved values at that time." +#: ../settings/security/third-party.rst:100 +msgid "No User Creation on Logon" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:66 +#: ../settings/security/third-party.rst:102 msgid "" -"You can find a description of the condition operators for core workflows :" -"doc:`here `." +"By default, Zammad will create a new user account if the user logs in via a " +"third-party application and the account doesn't exist yet." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:72 +#: ../settings/security/third-party.rst:105 msgid "" -"Which actions should we run on the relevant fields? The possible actions " -"depend on the object type. However, usually you can at least change the " -"visibility and whether the field is mandatory." +"If you want to prevent Zammad from creating new accounts on logon, you can " +"disable this feature by setting ``No user creation on logon`` to ``yes``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:76 -msgid "Be aware that actions are not available for **related** context." +#: ../settings/security/third-party.rst:None +msgid "Screenshot showing the \"no user creation on logon\" setting" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:78 +#: ../settings/security/third-party/facebook.rst:4 msgid "" -"**Example:** Let's assume you are working in the ticket context. While you " -"can have customer *conditions*, you *can't adjust* objects with actions in " -"that scope. That's because this wouldn't have any impact on the ticket " -"dialog. Of course all ticket attributes (state, owner, ...) are available." +"It is possible to create a quick login for your helpdesk via Facebook To do " +"so, you need to follow these steps:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:84 +#: ../settings/security/third-party/facebook.rst:9 +msgid "Register Facebook App" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:11 msgid "" -"Please also have a look at our :doc:`limitations` to be safe from surprises." +"Visit [https://developers.facebook.com/apps/] and click on \"Add a new App\"" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:88 -msgid "Available Operators" +#: ../settings/security/third-party/facebook.rst:None +msgid "initial page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:90 -msgid "The availability of operators depends on the object type and scope." +#: ../settings/security/third-party/facebook.rst:17 +msgid "After that enter the app settings" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:94 -msgid "" -"Please note that actions may or may not restrict API based access to " -"attributes. We're displaying the following icons for your overview to " -"understand these limits better:" +#: ../settings/security/third-party/facebook.rst:None +msgid "Create App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:0 -msgid "|api| This icon indicates the action affects the API." +#: ../settings/security/third-party/facebook.rst:22 +msgid "Navigate to \"Settings\" and fill in this infromation" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:163 -msgid "api" +#: ../settings/security/third-party/facebook.rst:None +msgid "App Settings" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:0 -msgid "|ui| This icon indicates the action only affects the web interface." +#: ../settings/security/third-party/facebook.rst:27 +msgid "Navigate to app review and Check \"Make [appname] public?\"" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:167 -msgid "ui" +#: ../settings/security/third-party/facebook.rst:None +msgid "App Review" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:102 -msgid "show |ui|" +#: ../settings/security/third-party/facebook.rst:35 +msgid "Configure Zammad as Facebook App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:102 -msgid "Display the chosen field. Allows setting of values." -msgstr "" - -#: ../system/core-workflows/how-do-they-work.rst:109 -msgid "hide |ui|" +#: ../settings/security/third-party/facebook.rst:37 +msgid "" +"Navigate to \"Admin -> Security -> Third Party Applications\" and enter the " +"App ID and the App Secret. You can find this Key in the Dashbard of your " +"Facebok app." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:105 -msgid "" -"Hide the chosen field. However, it technically still allows setting the " -"field." +#: ../settings/security/third-party/facebook.rst:None +msgid "Zammad Configuration" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:108 +#: ../settings/security/third-party/facebook.rst:44 +#: ../settings/security/third-party/github.rst:43 +#: ../settings/security/third-party/gitlab.rst:46 msgid "" -"Please note that the field is **not** gone and still contains an existing " -"value (if set)! Consider *remove* instead, if you want this field to be gone." +"Now you can link accounts via \"Avatar -> Profile -> Link Accounts\" or " +"login via Zammad login page." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:112 -msgid "remove |ui|" +#: ../settings/security/third-party/github.rst:2 +#: ../system/integrations/github.rst:2 +msgid "GitHub" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:112 -msgid "Entirely removes the field. The field value will not be evaluated." +#: ../settings/security/third-party/github.rst:4 +msgid "" +"It is possible to create a quick login for your helpdesk via GitHub. To " +"activate the quick login you need to enable OAuth for GitHub." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:115 -msgid "set mandatory |ui| |api|" +#: ../settings/security/third-party/github.rst:8 +msgid "Register GitHub App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:115 -msgid "Sets the field to mandatory." +#: ../settings/security/third-party/github.rst:10 +msgid "" +"Visit https://www.github.com/settings/applications/new and enter the app " +"settings. As callback URL enter \"https://zammad_host/auth/github/callback\" " +"where zammad_host has to be replaced with your Zammad FQDN" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:118 -msgid "set optional |ui| |api|" +#: ../settings/security/third-party/github.rst:None +msgid "Register OAuth app on www.github.com" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:118 -msgid "Sets the field to optional." +#: ../settings/security/third-party/github.rst:19 +msgid "Configure Zammad as GitHub App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:124 -msgid "add option |ui| |api|" +#: ../settings/security/third-party/github.rst:21 +msgid "" +"Enter the \"APP ID\" and the \"APP SECRET\" from the GitHub OAUTH " +"Applications Dashboard" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:121 -msgid "Allows adding options to tree selects or selects." +#: ../settings/security/third-party/github.rst:None +msgid "GitHub config in Zammad admin interface" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:123 +#: ../settings/security/third-party/github.rst:28 msgid "" -"You have to use the \"remove option\" before performing this action. It " -"allows you to use *existing* configured values." +"After you configured the GitHub credentials and activated the login method, " +"you should see a new icon on the login page." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:128 -msgid "remove option |ui| |api|" +#: ../settings/security/third-party/github.rst:None +msgid "GitHub logo on login page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:127 +#: ../settings/security/third-party/github.rst:34 msgid "" -"Allows removing options from tree selects or selects. It allows you to use " -"*existing* configured values." +"If you click on the icon you will be redirected to GitHub and see something " +"similar to this:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:134 -msgid "set fixed to |ui| |api|" +#: ../settings/security/third-party/github.rst:None +msgid "GitHub oauth page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:131 -msgid "Reduces the available options by your selection." +#: ../settings/security/third-party/github.rst:40 +#: ../settings/security/third-party/gitlab.rst:42 +msgid "" +"When you grant the access you will be redirected to your Zammad instance and " +"logged in as a customer." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:133 -msgid "" -"This reduces your workflows in terms of *add option* and *remove option*." +#: ../settings/security/third-party/gitlab.rst:2 +msgid "Gitlab" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:137 -msgid "fill in |ui|" +#: ../settings/security/third-party/gitlab.rst:4 +msgid "" +"It is possible to create a quick login for your helpdesk via Gitlab. To " +"activate the quick login you need to enable OAuth for Gitlab." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:137 -msgid "Allows filling in of string and integer fields with your values." +#: ../settings/security/third-party/gitlab.rst:8 +msgid "Register Gitlab App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:141 -msgid "fill in empty |ui|" +#: ../settings/security/third-party/gitlab.rst:10 +msgid "To register an app in Gitlab open your profile and select applications." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:140 +#: ../settings/security/third-party/gitlab.rst:12 msgid "" -"Allows filling in of string and integer fields with your values **if the " -"field is empty**." +"As callback URL enter \"https://zammad-fqdn/auth/gitlab/callback\" where " +"zammad-fqdn has to be replaced with your Zammad FQDN" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:144 -msgid "select |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Register OAuth app on gitlab instance" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:144 -msgid "Select a specific value within a select, tree select or boolean field." +#: ../settings/security/third-party/gitlab.rst:18 +msgid "Just select *read_user* under scopes as in the screenshot and save it." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:153 -msgid "auto select |ui|" +#: ../settings/security/third-party/gitlab.rst:21 +msgid "Configure Zammad as Gitlab App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:147 -msgid "Helps users with tree select and select fields:" +#: ../settings/security/third-party/gitlab.rst:23 +msgid "" +"Enter the \"APP ID\" and the \"APP SECRET\" from the Gitlab OAUTH " +"Applications Dashboard and your Gitlab-URL in the \"SITE\" field." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:149 -msgid "" -"If the field has only one option available for selection and no value yet, " -"the value will be automatically set." +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab config in Zammad admin interface" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:152 +#: ../settings/security/third-party/gitlab.rst:30 msgid "" -"This option only works if you have one value and doesn't work if there is " -"more than one option available." +"After you configured the Gitlab credentials and activated the login method, " +"you should see a new icon on the login page." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:157 -msgid "set readonly |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab logo on login page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:156 +#: ../settings/security/third-party/gitlab.rst:36 msgid "" -"Allows you to display an attribute as read only (which means no changes are " -"possible)." +"If you click on the icon you will be redirected to Gitlab and see something " +"similar to this:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:161 -msgid "unset readonly |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab oauth page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:160 +#: ../settings/security/third-party/google.rst:4 msgid "" -"In case a workflow set the field in question to read only, you can undo this " -"with option above." +"With some easy and fast steps, you can enable Zammad to authenticate your " +"users via Google." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:172 -msgid "Stop after match" +#: ../settings/security/third-party/google.rst:8 +msgid "Register a Google App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:174 +#: ../settings/security/third-party/google.rst:10 msgid "" -"Here you can decide if other workflows are executed after the current one." +"First of all, we need to create a new project - you can skip this step if " +"you already have one." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:176 +#: ../settings/security/third-party/google.rst:15 msgid "" -"If set to ``no`` (default), further workflows will be executed if they match " -"the condition. In this case, it is possible that your actions from the " -"current workflow can be overwritten by another workflow." +"Use this link to create a new project: https://console.cloud.google.com/" +"projectcreate" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:180 +#: ../settings/security/third-party/google.rst:18 msgid "" -"If set to ``yes``, no further worflows will be executed after the current " -"one." +"Now expand the menu, expand \"APIs & Services\" and select \"Credentials\". " +"Go to the tab \"OAuth consent screen\" first and ensure to fill in the " +"requested information - without doing so you can't create credentials!" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:184 -msgid "Priority" +#: ../settings/security/third-party/google.rst:None +msgid "Creating a consent screen" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:186 +#: ../settings/security/third-party/google.rst:25 msgid "" -"You can define the sequence, in which the workflows are executed. The " -"default value is ``500``." +"After filling in and saving the consent screen information, you can go to " +"the \"Credentials\" tab and create new \"OAuth client ID\"-Credentials." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:189 +#: ../settings/security/third-party/google.rst:28 msgid "" -"The workflows are executed in ascending order by their priority. That means " -"lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." +"Fill in the necessary information as follows and replace ``zammad_host`` " +"with your FQDN:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:2 -msgid "Learn by Example" +#: ../settings/security/third-party/google.rst:31 +msgid "**Application type** ``[x] Web application``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:4 -msgid "" -"This page provides some basic examples for Core Workflows. Of course you can " -"build much more complex workflows if needed." +#: ../settings/security/third-party/google.rst:34 +msgid "**Authorized JavaScript origins** ``https://zammad_host/``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:7 +#: ../settings/security/third-party/google.rst:37 msgid "" -"To learn about Core Workflows in detail, first go to :doc:`how-do-they-work`." +"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" +"callback``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:10 -msgid "Group Based Examples" +#: ../settings/security/third-party/google.rst:None +msgid "Adding a new OAuth client ID" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:12 +#: ../settings/security/third-party/google.rst:43 msgid "" -"All following workflows have the same base configurations. The workflow may " -"not use them all." +"After creating the credentials, go to your Zammad installation and navigate " +"to \"Admin > Security > Third Party Applications\" > Google. Enter your " +"Client ID and Client secret here." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:15 -msgid "Groups:" +#: ../settings/security/third-party/google.rst:None +msgid "Zammad" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:20 -msgid "Attributes:" +#: ../settings/security/third-party/google.rst:50 +msgid "After submitting, the login via Google can be used." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:22 -msgid "Category (Single tree selection field, not mandatory, agents only)" +#: ../settings/security/third-party/microsoft.rst:2 +msgid "Microsoft" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:23 +#: ../settings/security/third-party/microsoft.rst:4 msgid "" -"Approved (Boolean field, not mandatory, not shown, ``false`` as default)" +"Zammad's Microsoft connection allows your users with Microsoft accounts to " +"login. This works for Azure users as well and can be an alternative to :doc:" +"`/system/integrations/ldap/index`." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:24 -msgid "Operating System (Text field, not mandatory, not shown)" +#: ../settings/security/third-party/microsoft.rst:10 +msgid "" +"This documentation part does not cover our :doc:`📧 Microsoft 365 email " +"channel `." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:25 -msgid "Software used (Single selection field, not mandatory, not shown)" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screenshot showing Microsoft login button on Zammad login screen." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:68 -msgid "Group specific values and fields" +#: ../settings/security/third-party/microsoft.rst:30 +#: ../settings/security/third-party/microsoft.rst:53 +msgid "Supported account types:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:28 +#: ../settings/security/third-party/microsoft.rst:22 msgid "" -"This workflow set depends on the category field. It reduces the available " -"set of values based on the group selected." +"Please note that Zammad only supports these account types (App dependent):" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:33 -msgid "Workflow 2nd Level group" +#: ../settings/security/third-party/microsoft.rst:35 +msgid "Avatars of signing in users:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:35 +#: ../settings/security/third-party/microsoft.rst:33 msgid "" -"This reduces the category options to ``2nd Level/*``, ``Internal/*`` and " -"``Others``. It also sets further required fields to mandatory and visible." -msgstr "" - -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for 2nd level" +"Zammad currently ignores user avatars. If the user is registered with e.g. " +"Gravatar, Zammad will fetch the avatar from there if enabled. See :doc:" +"`Zammad Image Service ` for more." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:43 -msgid "Workflow Support group" +#: ../settings/security/third-party/microsoft.rst:38 +msgid "Step 1 - Register a Microsoft App for Zammad" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:45 +#: ../settings/security/third-party/microsoft.rst:40 msgid "" -"This reduces the category options to ``Support/*``, ``Internal/*`` and " -"``Others``. It also sets further required fields to visible." -msgstr "" - -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for support" +"Login to the `Microsoft Azure Portal `_ and " +"navigate to App registrations to create a new app. Provide the requested " +"information as follows and register your app." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:53 -msgid "Workflow Sales group" +#: ../settings/security/third-party/microsoft.rst:46 +msgid "Name:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:55 +#: ../settings/security/third-party/microsoft.rst:45 msgid "" -"This reduces the category options to ``Sales/*``, ``Internal/*`` and " -"``Others``." +"Any meaningful name fitting, this name will be displayed to users trying to " +"authenticate with this app." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for sales" +#: ../settings/security/third-party/microsoft.rst:49 +msgid "Choose one of the above mentioned account types (see Limitations)." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:68 -#: ../system/integrations/slack.rst:88 -msgid "The Result" +#: ../settings/security/third-party/microsoft.rst:51 +msgid "" +"The correct account type depends on your use case. If you want to use the " +"authentication internal only, choose the first option. If you're unsure, use " +"the \"Help me choose...\" link." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:63 -msgid "" -"This is what the agent would experience with the above workflows in place." +#: ../settings/security/third-party/microsoft.rst:58 +msgid "Redirect URI (optional):" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 +#: ../settings/security/third-party/microsoft.rst:56 msgid "" -"Workflow shows objects and limits options based on selections on the group" +"Select web and provide your callback URL. The callback URL looks like this: " +"``https://zammad.domain.tld/auth/microsoft_office365/callback``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:90 -msgid "Approval process" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to register a Microsoft app" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:71 -msgid "" -"In this case ``approved`` is visible to agents by default. For this " -"workflow, an additional role ``Approval person`` is required (no further " -"permissions)." +#: ../settings/security/third-party/microsoft.rst:71 +msgid "Within **API permissions** add the following permissions:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that restricts an approval attribute to specific roles" +#: ../settings/security/third-party/microsoft.rst:69 +msgid "``User.Read``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:81 -msgid "" -"This workflow may work best in combination with a :doc:`trigger ` but technically, this is not required." +#: ../settings/security/third-party/microsoft.rst:71 +msgid "Contacts" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:84 -msgid "" -"Select fields may be a better approach because they allow more values than " -"just a simple ``true`` or ``false``." +#: ../settings/security/third-party/microsoft.rst:71 +msgid "``Contacts.Read``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 +#: ../settings/security/third-party/microsoft.rst:73 msgid "" -"Workflow fixes possible values of \"Approved ?\" to a specific selection " -"depending on the users role" +"You can find these permissions within *Microsoft Graph → Delegated " +"permissions*." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:103 -msgid "State dependent mandatory fields" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to add required API permissions" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:93 +#: ../settings/security/third-party/microsoft.rst:80 msgid "" -"This workflow sets ``Category`` to mandatory if the agent wants to set the " -"states ``closed`` or ``pending close`` to enforce categorization." +"Within **Certificates & secrets** create a new client secret. Note down the " +"returned secret **value** for later. **Do not** use the secret ID!" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that sets fields to mandatory on specific states" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to create a new app secret" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 +#: ../settings/security/third-party/microsoft.rst:88 msgid "" -"Workflow sets category field to mandatory upon choosing closed or pending " -"close as state" +"From **Overview** copy your apps *Application (client) ID*. If you're using " +"a single tenant app, please also copy *Directory (tenant) ID*. You now have " +"all required information for Zammad." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:106 -msgid "Manual Ticket Handover Process" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to retreive application client and tenant IDs" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:108 -msgid "This example covers the handover of a ticket from one agent to another:" +#: ../settings/security/third-party/microsoft.rst:98 +msgid "Step 2 - Add App Credentials to Zammad" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:110 +#: ../settings/security/third-party/microsoft.rst:100 msgid "" -"When the ticket owner is modified, a new text field (\"Handover\") shows up " -"for a comment" +"Navigate to Security > Third-party Applications (Tab) within Zammad's admin " +"settings. Scroll down to the section *Authentication via Microsoft* and fill " +"in the required information." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:112 -msgid "" -"This may only be visible when the owner is changed, therefore it has to be " -"hidden in general" +#: ../settings/security/third-party/microsoft.rst:105 +msgid "App ID:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:114 -msgid "The input in this handover text field is mandatory" +#: ../settings/security/third-party/microsoft.rst:105 +msgid "This is your *Application (client) ID*." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:115 -msgid "" -"After submitting changes, the value of the handover field must be added as " -"an note to the ticket (via trigger)" +#: ../settings/security/third-party/microsoft.rst:108 +msgid "App secret:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:121 -msgid "Hiding handover field" +#: ../settings/security/third-party/microsoft.rst:108 +msgid "This is your *client secret* (value)." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Hiding the handover field in core workflows" +#: ../settings/security/third-party/microsoft.rst:113 +msgid "App Tenant ID:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:126 -msgid "Showing handover field and setting it to mandatory" +#: ../settings/security/third-party/microsoft.rst:111 +msgid "" +"**optional** only required for apps that use account type *Accounts in this " +"organizational directory only (Default Directory only - Single tenant).*" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Showing the handover field and set it as mandatory" +#: ../settings/security/third-party/microsoft.rst:115 +msgid "" +"Apply your settings by pressing submit and activate *Authentication via " +"Microsoft*." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:131 -msgid "Trigger writing handover input to a new article" +#: ../settings/security/third-party/microsoft.rst:None +msgid "" +"Screencast showing how to add app credentials and activating the\n" +"authentication method" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Write handover content to a new article" +#: ../settings/security/third-party/saml.rst:2 +msgid "SAML" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:133 +#: ../settings/security/third-party/saml.rst:4 msgid "" -"As a result, the ticket includes an article of the type note which includes " -"the predefined text and the handover comment." +"Connect your SAML (Security Assertion Markup Language) identity provider as " +"a single sign-on (SSO) method." msgstr "" -#: ../system/core-workflows/limitations.rst:6 -msgid "Core Workflows do not replace Triggers" +#: ../settings/security/third-party/saml.rst:7 +msgid "" +"SAML is an open standard for SSO authentication (among other things). Sign-" +"ins are shared across multiple **service providers** and managed by a " +"central **identity provider** (IdP)." msgstr "" -#: ../system/core-workflows/limitations.rst:5 +#: ../settings/security/third-party/saml.rst:11 msgid "" -"Workflows manipulate the behavior of fields. However, they do not set values " -"in fields because of actions." +"In this case, the service provider is Zammad, and the IdP is a software " +"service that you either host or subscribe to (*e.g.,* `Keycloak `_, `Redhat SSO Server `_, `ADFS `_, or `Okta `_)." msgstr "" -#: ../system/core-workflows/limitations.rst:16 -msgid "API calls are only partly affected" +#: ../settings/security/third-party/saml.rst:18 +msgid "" +"This guide assumes you are already using SAML within your organization (i." +"e., that your IdP is fully set up)." msgstr "" -#: ../system/core-workflows/limitations.rst:9 +#: ../settings/security/third-party/saml.rst:21 msgid "" -"Some options affect UI only and thus do not restrict responses and calls." +"Please note: Our instructions are based on connecting Zammad with Keycloak." msgstr "" -#: ../system/core-workflows/limitations.rst:11 -msgid "This affects the following actions:" +#: ../settings/security/third-party/saml.rst:25 +msgid "Step 1: Configure Your IdP" msgstr "" -#: ../system/core-workflows/limitations.rst:13 -msgid "select" +#: ../settings/security/third-party/saml.rst:28 +msgid "Add Zammad as a Client/App" msgstr "" -#: ../system/core-workflows/limitations.rst:14 -msgid "auto select" +#: ../settings/security/third-party/saml.rst:30 +msgid "" +"Import Zammad into your IdP using the XML configuration found at ``https://" +"your.zammad.domain/auth/saml/metadata``." msgstr "" -#: ../system/core-workflows/limitations.rst:15 -msgid "show" +#: ../settings/security/third-party/saml.rst:33 +msgid "" +"If your IdP doesn't support XML import, you will have to configure Zammad as " +"a new client/app manually using the above XML metadata file for reference." msgstr "" -#: ../system/core-workflows/limitations.rst:16 -msgid "hide" +#: ../settings/security/third-party/saml.rst:36 +msgid "For instance, when you see this tag:" msgstr "" -#: ../system/core-workflows/limitations.rst:25 -msgid "Some fields stay unavailable to customers" +#: ../settings/security/third-party/saml.rst:42 +msgid "" +"Set the **Assertion Consumer Service Binding URL** (sometimes also listed as " +"**Valid Redirect URIs**) to ``http://your.zammad.domain/auth/saml/callback``." msgstr "" -#: ../system/core-workflows/limitations.rst:19 -msgid "" -"For technical and security reasons, some default fields (the pale ones you " -"can't edit) stay unavailable for display and usage on customer permissions." +#: ../settings/security/third-party/saml.rst:47 +msgid "Set Up User Attribute Mapping" msgstr "" -#: ../system/core-workflows/limitations.rst:23 +#: ../settings/security/third-party/saml.rst:49 msgid "" -"If you require your customers to change e.g. priorities, please consider " -"using workarounds via :doc:`/system/objects` and :doc:`/manage/trigger`." +"Zammad requests the following user attributes (or “properties”) from the IdP:" msgstr "" -#: ../system/core-workflows/limitations.rst:29 -msgid "Ticket title changes not supported in edit mask" +#: ../settings/security/third-party/saml.rst:51 +msgid "Email address (``email``)" msgstr "" -#: ../system/core-workflows/limitations.rst:28 -msgid "" -"It is currently not possible to perform changes of the ticket title in the " -"edit mask (e.g. renaming, set to read-only)." +#: ../settings/security/third-party/saml.rst:52 +msgid "Full name (``name``)" msgstr "" -#: ../system/core-workflows/limitations.rst:37 -msgid "What is out of scope of Core Workflows?" +#: ../settings/security/third-party/saml.rst:53 +msgid "Given name (``first_name``)" msgstr "" -#: ../system/core-workflows/limitations.rst:32 -msgid "" -"There are some things that would count as workflow but are either done via :" -"doc:`/manage/trigger` or :doc:`/manage/scheduler`." +#: ../settings/security/third-party/saml.rst:54 +msgid "Family name (``last_name``)" msgstr "" -#: ../system/core-workflows/limitations.rst:35 -msgid "Such as (but not limited to):" +#: ../settings/security/third-party/saml.rst:56 +msgid "" +"You may need to set up “mappers” (or “mappings”) to tell your IdP how user " +"attributes in SAML correspond to those in Zammad. For a more detailed " +"breakdown, refer to the XML metadata file referenced in the previous section." msgstr "" -#: ../system/core-workflows/limitations.rst:37 -msgid "up- or downgrade permissions of users" +#: ../settings/security/third-party/saml.rst:62 +msgid "Per-IdP Instructions" msgstr "" -#: ../system/core-workflows/limitations.rst:38 -msgid "affecting article creation or listing" +#: ../settings/security/third-party/saml.rst:102 +msgid "Keycloak" msgstr "" -#: ../system/data-privacy.rst:2 -msgid "Data Privacy" +#: ../settings/security/third-party/saml.rst:65 +msgid "" +"**To add Zammad as a client,** save the XML configuration to disk (``https://" +"your.zammad.domain/auth/saml/metadata``) and use **Clients > Clients list > " +"Import client** in the Keycloak admin panel." msgstr "" -#: ../system/data-privacy.rst:4 +#: ../settings/security/third-party/saml.rst:70 msgid "" -"For compliance with GDPR and other data privacy laws, you may wish to " -"**permanently delete users from the system**, along with **all of their " -"associated tickets**." +"To help Zammad **match its own user accounts to Keycloak users**, create a " +"user attribute (or “property”) mapper. In **Clients list**, click on your " +"newly created Client ID, choose the tab **Client scopes** and click on the " +"link which refers to your Zammad instance. Choose **Add mapper > By " +"configuration > User Property** and create a mapper with the following " +"entries:" 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 `!" +#: ../settings/security/third-party/saml.rst:78 +msgid "**Name**" msgstr "" -#: ../system/data-privacy.rst:12 -msgid "" -"Access to this panel requires ``admin.data_privacy`` permissions (introduced " -"in Zammad 3.5)." +#: ../settings/security/third-party/saml.rst:80 +msgid "**Mapper Type**" msgstr "" -#: ../system/data-privacy.rst:15 -msgid "" -"On older systems that have not been updated yet, customers can also be :docs:" -"`deleted via the Zammad console `." +#: ../settings/security/third-party/saml.rst:81 +msgid "``User Property``" msgstr "" -#: ../system/data-privacy.rst:22 -msgid "User deletion dialog in the Data Privacy panel" +#: ../settings/security/third-party/saml.rst:82 +msgid "**Property**" msgstr "" -#: ../system/data-privacy.rst:22 -msgid "" -"The user deletion dialog lists some of the tickets that will be removed from " -"the system along with the user." +#: ../settings/security/third-party/saml.rst:83 +msgid "``emailAddress``" msgstr "" -#: ../system/data-privacy.rst:27 -msgid "Deleting Users via GUI" +#: ../settings/security/third-party/saml.rst:84 +msgid "**SAML Attribute Name**" msgstr "" -#: ../system/data-privacy.rst:29 -msgid "🔥 **All deletions are FINAL!**" +#: ../settings/security/third-party/saml.rst:86 +msgid "**SAML Attribute NameFormat**" msgstr "" -#: ../system/data-privacy.rst:31 -msgid "Once you click “Delete”, the action cannot be canceled or undone." +#: ../settings/security/third-party/saml.rst:87 +msgid "``basic``" msgstr "" -#: ../system/data-privacy.rst:33 +#: ../settings/security/third-party/saml.rst:89 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." +"In the example above, we're telling Zammad that whenever it receives a SAML " +"login request, it should take the ``email`` property from Keycloak, look for " +"a Zammad user with the same ``email`` attribute, and create a new session " +"for that user." msgstr "" -#: ../system/data-privacy.rst:36 -msgid "**The following records cannot be deleted:**" +#: ../settings/security/third-party/saml.rst:95 +msgid "" +"If your Keycloak users' email addresses are stored on another property (*e." +"g.,* ``username``), adjust accordingly." msgstr "" -#: ../system/data-privacy.rst:38 -msgid "your own account" +#: ../settings/security/third-party/saml.rst:98 +msgid "" +"Back in **Settings**, enter the Client ID (``https://your.zammad.domain/auth/" +"saml/metadata``) in the field **Master SAML Processing URL**." msgstr "" -#: ../system/data-privacy.rst:39 -msgid "the system's last remaining administrator account" +#: ../settings/security/third-party/saml.rst:101 +msgid "You also need to enable **Sign assertions**." msgstr "" -#: ../system/data-privacy.rst:42 -msgid "Step 1: Find a User / Confirm Deletion" +#: ../settings/security/third-party/saml.rst:105 +msgid "Step 2: Configure Zammad" msgstr "" -#: ../system/data-privacy.rst:44 -msgid "There are three ways to access the user deletion dialog:" +#: ../settings/security/third-party/saml.rst:107 +msgid "" +"Enable SAML and enter your IdP's details in the Admin Panel under **Settings " +"> Security > Third Party Applications > Authentication via SAML**:" msgstr "" -#: ../system/data-privacy.rst:51 -msgid "**from the user's profile**" +#: ../settings/security/third-party/saml.rst:None +msgid "Example configuration of SAML part 1" msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Accessing the user deletion dialog in a user profile" +#: ../settings/security/third-party/saml.rst:119 +msgid "Display name" msgstr "" -#: ../system/data-privacy.rst:51 -msgid "Click **Action > Delete**." +#: ../settings/security/third-party/saml.rst:116 +msgid "" +"Allows you to define a custom button name for SAML. This helps your users to " +"understand better what the button on the login page does." msgstr "" -#: ../system/data-privacy.rst:58 -msgid "**in the “Manage > Users” Admin Panel**" +#: ../settings/security/third-party/saml.rst:119 +msgid "Defaults to ``SAML``." msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Accessing the user deletion dialog under “Users” in the Admin Panel" +#: ../settings/security/third-party/saml.rst:123 +msgid "IDP SSO target URL" msgstr "" -#: ../system/data-privacy.rst:58 -msgid "Use the **⋮ Actions** menu for the target user." +#: ../settings/security/third-party/saml.rst:122 +msgid "" +"This is the target URL Zammad shall redirect to when the user presses the " +"SAML button. For Keycloak, this needs to look like https://your.domain/" +"realms/your-realm/protocol/saml" msgstr "" -#: ../system/data-privacy.rst:66 ../system/data-privacy.rst:104 -msgid "**in the “System > Data Privacy” Admin Panel**" +#: ../settings/security/third-party/saml.rst:127 +msgid "IDP single logout target URL" msgstr "" -#: ../system/data-privacy.rst:0 +#: ../settings/security/third-party/saml.rst:126 msgid "" -"Accessing the user deletion dialog under “Data Privacy” in the Admin Panel" +"This is the URL to which the single logout request and response should be " +"sent." msgstr "" -#: ../system/data-privacy.rst:65 +#: ../settings/security/third-party/saml.rst:131 +msgid "IDP certificate" +msgstr "" + +#: ../settings/security/third-party/saml.rst:130 msgid "" -"Use the **New Deletion Task** button. Search for users by name or email " -"address." +"The public certificate of your IDP for Zammad to verify during the callback " +"phase." msgstr "" -#: ../system/data-privacy.rst:79 -msgid "**Delete organizations**" +#: ../settings/security/third-party/saml.rst:145 +msgid "IDP certificate fingerprint" msgstr "" -#: ../system/data-privacy.rst:69 +#: ../settings/security/third-party/saml.rst:134 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:" +"The fingerprint of your IDPs public certificate to verify during callback " +"phase." msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Deleting an organization via the user deletion dialog" +#: ../settings/security/third-party/saml.rst:137 +msgid "🔏 **For the IdP certificate / certificate fingerprint:**" msgstr "" -#: ../system/data-privacy.rst:78 +#: ../settings/security/third-party/saml.rst:139 msgid "" -"If this option does not appear, make sure there are no pending deletion " -"tasks for other customers from this organization." +"Provide **only one or the other**—do not provide both! (Between the two, we " +"recommend the signing certificate itself: fingerprints use SHA-1, which `has " +"been broken for a while now `_.)" msgstr "" -#: ../system/data-privacy.rst:82 -msgid "Step 2: Monitor Deletion Job Status" +#: ../settings/security/third-party/saml.rst:144 +msgid "" +"**Keycloak users:** Find your certificate in the Keycloak admin panel under " +"**Realm Settings > Keys > Algorithm: RS256 > Certificate**." msgstr "" -#: ../system/data-privacy.rst:84 +#: ../settings/security/third-party/saml.rst:151 +msgid "Name identifier format" +msgstr "" + +#: ../settings/security/third-party/saml.rst:148 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:" +"This is the unique identifiers field type. Usually it should be ``urn:oasis:" +"names:tc:SAML:1.1:nameid-format:emailAddress``." msgstr "" -#: ../system/data-privacy.rst:98 -msgid "**in the Activity Stream**" +#: ../settings/security/third-party/saml.rst:151 +msgid "Zammad **expects an email address as unique identifier**!" msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Activity Stream showing data privacy tasks" +#: ../settings/security/third-party/saml.rst:155 +msgid "UID attribute name" msgstr "" -#: ../system/data-privacy.rst:94 +#: ../settings/security/third-party/saml.rst:154 msgid "" -"For each deleted user, the Activity Stream will be updated twice—once when " -"the task is created, and once when it's complete." +"Here you can define an attribute that uniquely identifies the user. If " +"unset, the name identifier returned by the IDP is used." msgstr "" -#: ../system/data-privacy.rst:97 -msgid "" -"These notifications are only visible to users with ``admin.data_privacy`` " -"permissions." +#: ../settings/security/third-party/saml.rst:None +msgid "Example configuration of SAML part 2" msgstr "" -#: ../system/data-privacy.rst:0 +#: ../settings/security/third-party/saml.rst:163 msgid "" -"The task list within Data Privacy shows removals being in progress and " -"completed." +"Decide if the certificate for the connection to the IdP service has to be " +"verified or not (default: ``yes``)." msgstr "" -#: ../system/data-privacy.rst:107 -msgid "Frequently Asked Questions" +#: ../settings/security/third-party/saml.rst:169 +msgid "Signing & Encrypting" msgstr "" -#: ../system/data-privacy.rst:121 -msgid "What happens if I receive an email from a deleted customer?" -msgstr "" - -#: ../system/data-privacy.rst:110 +#: ../settings/security/third-party/saml.rst:169 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." +"Define if you want to sign, encrypt, do both or nothing for the requests." msgstr "" -#: ../system/data-privacy.rst:115 -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**." +#: ../settings/security/third-party/saml.rst:179 +msgid "Certificate (PEM)" msgstr "" -#: ../system/data-privacy.rst:130 -msgid "What about user information stored in internal notes or other messages?" +#: ../settings/security/third-party/saml.rst:172 +msgid "" +"Paste the public certificate of your Zammad SAML client, if you want to " +"encrypt the requests." msgstr "" -#: ../system/data-privacy.rst:124 -msgid "" -"The deletion process removes **user accounts and associated tickets only**." +#: ../settings/security/third-party/saml.rst:175 +msgid "Make sure the certificate is:" msgstr "" -#: ../system/data-privacy.rst:126 -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." +#: ../settings/security/third-party/saml.rst:177 +msgid "already valid and not yet expired" msgstr "" -#: ../system/data-privacy.rst:137 -msgid "I deleted an user and can still see a message they sent!" +#: ../settings/security/third-party/saml.rst:178 +msgid "no CA certificate" msgstr "" -#: ../system/data-privacy.rst:133 -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." +#: ../settings/security/third-party/saml.rst:179 +msgid "valid for signing and encrypting" msgstr "" -#: ../system/data-privacy.rst:141 -msgid "I removed a customer, now my reporting is off!" +#: ../settings/security/third-party/saml.rst:185 +msgid "Private key (PEM)" msgstr "" -#: ../system/data-privacy.rst:140 +#: ../settings/security/third-party/saml.rst:182 msgid "" -"When removing users and their tickets, all references are removed. This also " -"affects e.g. Reporting - these information are lost." +"Paste the private key of your Zammad SAML client here, if you want to sign " +"the requests." msgstr "" -#: ../system/data-privacy.rst:145 -msgid "How long does Zammad store created tasks?" +#: ../settings/security/third-party/saml.rst:185 +msgid "Make sure the key is an RSA key with a length of at least 2048 bits." msgstr "" -#: ../system/data-privacy.rst:144 -msgid "" -"Please see the on-premise data section of the :docs:`data privacy ` chapter." +#: ../settings/security/third-party/saml.rst:188 +msgid "Private key secret" msgstr "" -#: ../system/data-privacy.rst:150 -msgid "What about re-assigned tickets? I want to delete them, too." +#: ../settings/security/third-party/saml.rst:188 +msgid "If your private key is secured with a secret, you can provide it here." msgstr "" -#: ../system/data-privacy.rst:148 -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." +#: ../settings/security/third-party/saml.rst:192 +msgid "Your callback URL" msgstr "" -#: ../system/data-privacy.rst:154 -msgid "Why are there so many deletion task entries, I didn't create them!" +#: ../settings/security/third-party/saml.rst:191 +msgid "" +"This URL is needed for your IdP configuration so it knows where to redirect " +"to after successful authentication." msgstr "" -#: ../system/data-privacy.rst:153 +#: ../settings/security/third-party/saml.rst:194 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." +"After saving your input by clicking on the \"Submit\" button, Zammad " +"verifies the provided keys/certificates (e.g. if they are valid for signing/" +"encrypting and if they aren't expired)." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:2 -msgid "Admin Panel Reference" +#: ../settings/security/third-party/saml.rst:199 +msgid "" +"See :ref:`automatic account linking ` for details " +"on how to link existing Zammad accounts to IdP accounts." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:None -msgid "Screenshot of Checkmk settings overview" +#: ../settings/security/third-party/saml.rst:205 +msgid "Automatic account linking doesn't work" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:12 +#: ../settings/security/third-party/saml.rst:206 msgid "" -"Which :doc:`group ` should Checkmk tickets be assigned " -"to as a default (*i.e.,* when none is specified)?" +"Have you double-checked your IdP's user attribute mapping configuration?" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:15 -msgid "(Applies to :ref:`API alerts ` only.)" +#: ../settings/security/third-party/twitter.rst:4 +msgid "" +"It is possible to create a quick login for your helpdesk via Twitter. To do " +"so, you need to follow these steps:" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:21 -msgid "Auto close" +#: ../settings/security/third-party/twitter.rst:8 +msgid "Register Twitter App" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:18 -msgid "" -"Should Zammad automatically close tickets if a service has recovered on its " -"own?" +#: ../settings/security/third-party/twitter.rst:10 +msgid "Go to https://dev.twitter.com/apps and login with your account." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:21 -msgid "(Agents will receive notifications for such closures as appropriate.)" +#: ../settings/security/third-party/twitter.rst:15 +msgid "Click on \"Create App\"" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:30 -msgid "Auto-close state" +#: ../settings/security/third-party/twitter.rst:None +msgid "new app page" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:24 -msgid "What ticket state should be applied when “auto-closing” a ticket?" +#: ../settings/security/third-party/twitter.rst:20 +msgid "" +"Enter app settings. As \"Callback URL\" you need to enter ``https://" +"zammad_host/api/v1/external_credentials/twitter/callback``. You need to " +"replace ``zammad_host`` with the domain of your Zammad system." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:26 +#: ../settings/security/third-party/twitter.rst:24 msgid "" -"You can choose from the seven built-in ticket states. If these states aren't " -"enough for you, you can :ref:`define a new ticket state ` for this purpose as well. This can be useful for tracking " -"tickets with :doc:`reports `, for example." +"After the app has been created, update the application icon and organization " +"attributes." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:35 -#: ../system/integrations/cti/includes/recent-logs.include.rst:2 -#: ../system/integrations/ldap/index.rst:74 -#: ../system/integrations/pgp/index.rst:106 -msgid "Recent Logs" +#: ../settings/security/third-party/twitter.rst:None +msgid "set permissions to receive and send direct messages" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:None -msgid "Screenshot of Checkmk \"Recent Logs\" section" +#: ../settings/security/third-party/twitter.rst:30 +msgid "" +"Next we need to set ``read, write and access direct messages`` permissions " +"for the app." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:41 -msgid "" -"If you're having trouble getting Zammad and Checkmk to play nicely together, " -"this section can help you troubleshoot." +#: ../settings/security/third-party/twitter.rst:None +msgid "click on Keys & Access Token, note them" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:44 +#: ../settings/security/third-party/twitter.rst:36 msgid "" -"It contains a record of the fifty most recent transactions that Zammad knows " -"about, including each one's request/response details and return status." +"Go to \"Keys and Access Token\" tab and note the \"Consumer Key\" and " +"\"Consumer Secret\"." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:2 -msgid "API Reference" +#: ../settings/security/third-party/twitter.rst:40 +msgid "Configure Zammad as Twitter App" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:4 +#: ../settings/security/third-party/twitter.rst:42 msgid "" -"For most users, :ref:`the sample scripts from the Setup Guide ` will do the job just fine. But if you want more fine-grained control" -"—for instance, to create high- and low-priority tickets for different types " -"of system events—then you'll have to customize the data those scripts send " -"to Zammad." +"Go to \"Admin > Security > Twitter > Third Party Applications > Twitter\" " +"Section." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:15 -msgid "" -"This custom script will automatically set all tickets it creates to **high " -"priority** and **assign them to charlie@chrispresso.com**." +#: ../settings/security/third-party/twitter.rst:None +msgid "Admin > Security > Third Party Applications" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:32 -msgid "How Does it Work?" +#: ../settings/security/third-party/twitter.rst:48 +msgid "" +"Fill in the \"Twitter Key\" and the \"Twitter Secret\" and click the " +"\"Submit\" button." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:34 +#: ../settings/security/third-party/twitter.rst:51 msgid "" -"There are two kinds of data you can pass to the API, both in the form of key-" -"value pairs:" +"Now you can link accounts via \"Avatar > Profile > Link Accounts\" or login " +"via Zammad login page." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:44 -msgid "Checkmk parameters" +#: ../settings/security/two-factor.rst:11 +msgid "Two-factor Authentication Methods" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:38 -msgid "" -"are required, and make up the **contents** of the resulting tickets/" -"articles. They also determine whether an event creates a new ticket or " -"updates/closes an existing one." +#: ../settings/security/two-factor.rst:2 +msgid "Two-Factor Authentication" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:42 +#: ../settings/security/two-factor.rst:4 msgid "" -"These are the only values used in the sample scripts. **Use them as-is**; " -"technically, they can be customized, but it's hard to imagine a good reason " -"for it." +"Two-factor authentication (2FA) enhances the security of Zammad accounts by " +"adding an extra layer of verification beyond a password. It requires users " +"to provide two different types of authentication factors, typically " +"something they know (like a password) and something they possess (like a " +"mobile device or a security token), to ensure that only authorized " +"individuals can access the account." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:52 -msgid "Ticket attributes" +#: ../settings/security/two-factor.rst:19 +msgid "Enable Recovery Codes" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:47 +#: ../settings/security/two-factor.rst:21 msgid "" -"are optional, and can be used to **adjust settings** on newly created " -"tickets (*e.g.,* set the owner, group, priority, or state)." +"Recovery codes are one-time use security codes that can be used by the user " +"if they lose access to their other two-factor authentication methods. They " +"cannot be used on their own, they can only be activated if at least one two-" +"factor authentication method is enabled." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:50 -msgid "" -"If you want to customize your Checkmk alert script, do it with these. Simply " -"add an extra “form” option for each one (``-F \"key=value\"``) to your " -"script's ``curl`` command line, as in the example above." +#: ../settings/security/two-factor.rst:None +msgid "Enable Recovery Codes Setting" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:54 -msgid "💡 **It's just an API endpoint!**" +#: ../settings/security/two-factor.rst:30 +msgid "" +"Recovery codes can only be used as a backup method. If enabled, they will be " +"automatically generated for the user once they set up their initial two-" +"factor authentication method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:56 +#: ../settings/security/two-factor.rst:34 msgid "" -"When using Checkmk integration, messages need to be formatted in a certain " -"way, but that *doesn't mean the messages actually have to come from Checkmk*." +"The user will be asked to print out or save the generated recovery codes in " +"a safe place. Once used, a recovery code cannot be reused." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:59 +#: ../settings/security/two-factor.rst:37 msgid "" -"If you use another monitoring tool that's not officially supported by " -"Zammad, there's probably a way to make it work with your Checkmk callback " -"URL." +"Users will also have an option to regenerate their recovery codes at any " +"time, which invalidates already existing recovery codes and provides them " +"with a list of fresh codes." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:63 -msgid "Checkmk Parameters" +#: ../settings/security/two-factor.rst:41 +msgid "" +"After you enable this setting, when the user completes a setup of their " +"initial two-factor authentication method, they will be presented with a list " +"of recovery codes and instructed to save them for later use." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:65 -msgid "" -"When a notification is received, Zammad creates a new article containing the " -"details of the event that triggered it:" +#: ../settings/security/two-factor.rst:None +msgid "Recovery Codes Generation Modal Dialog" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:None -msgid "Checkmk article body" +#: ../settings/security/two-factor.rst:50 +msgid "Enforce the Set Up of the Two-Factor Authentication" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:72 +#: ../settings/security/two-factor.rst:52 msgid "" -"These details come from the fields listed below, which correspond to " -"parameters provided by Checkmk (``$NOTIFY_*``)." +"In case you wish to require your users to set up at least one two-factor " +"authentication method for their account, you can do this by selecting " +"specific user roles the requirement applies to in **Enforced for user " +"roles** setting. Of course you must have at least one two-factor " +"authentication method enabled for this setting to take effect." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:75 -msgid "**Required fields are marked with an asterisk (\\*).**" +#: ../settings/security/two-factor.rst:None +msgid "Enforced for User Roles Setting" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:79 -msgid "event_id\\*" +#: ../settings/security/two-factor.rst:62 +msgid "" +"After you change this setting, if the user has one of the selected roles on " +"their account, they will be forced to set up the two-factor authentication " +"upon next sign in or application reload." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:78 +#: ../settings/security/two-factor.rst:66 msgid "" -"A unique ID for the system event. (``$NOTIFY_SERVICEPROBLEMID`` / " -"``$NOTIFY_HOSTPROBLEMID``)" +"A modal dialog with instructions will be shown, and they will not be able to " +"do any work before they set up at least one two-factor method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:86 -msgid "host\\*" +#: ../settings/security/two-factor.rst:None +msgid "Modal Dialog for Enforcing Two-Factor Authentication Set Up" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:82 +#: ../settings/security/two-factor.rst:74 +msgid "Reset Two-Factor Authentication for a Specific User" +msgstr "" + +#: ../settings/security/two-factor.rst:76 msgid "" -"The hostname of the system that the event originated from. " -"(``$NOTIFY_HOSTNAME``)" +"In case an user isn't able to login anymore because of an inaccessible " +"second factor, you can reset the user's 2FA method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:85 +#: ../settings/security/two-factor.rst:79 msgid "" -"Used to determine if a new event belongs to an existing ticket. Also used in " -"the subject line of the resulting article (“ is ”)." +"To do this, go to the user management and search for the relevant user. " +"After you found the account, click the button in the action column and " +"select \"Manage Two-Factor Authentication\":" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:96 -msgid "service" +#: ../settings/security/two-factor.rst:None +msgid "Context menu in action column in user management" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:89 +#: ../settings/security/two-factor.rst:87 msgid "" -"The name of the service that the event originated from. " -"(``$NOTIFY_SERVICEDESC``)" +"After selecting this, you can see a dialog where you can either reset one " +"2FA method or reset all of the user's 2FA methods:" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:92 -msgid "Used to determine if a new event belongs to an existing ticket." +#: ../settings/security/two-factor.rst:None +msgid "Dialog for resetting user's 2FA method" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:94 -#: ../system/integrations/checkmk/api-reference.rst:110 -msgid "Displayed as ``-`` when omitted." +#: ../settings/security/two-factor.rst:94 +msgid "" +"Choose the fitting one, click on the corresponding \"Remove ...\" button and " +"confirm your action. The user now has to setup a new 2FA method, depending " +"on your 2FA configuration." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:104 -msgid "state\\*" +#: ../settings/security/two-factor/authenticator-app.rst:2 +msgid "Authenticator App" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:99 +#: ../settings/security/two-factor/authenticator-app.rst:4 msgid "" -"The current state of the service or host in question. " -"(``$NOTIFY_SERVICESTATE`` / ``$NOTIFY_HOSTSTATE``)" +"The authenticator app method is a type of two-factor authentication that " +"uses a mobile application to generate one-time codes for account " +"verification. After setting up the authenticator app on their device, the " +"user links it to their Zammad account." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:102 +#: ../settings/security/two-factor/authenticator-app.rst:12 msgid "" -"Used to detect when a ticket should be auto-closed (*i.e.,* on ``OK``/" -"``UP``). Also used in the subject line of the resulting article (“ is " -"”)." +"When logging in, the user is prompted to enter a time-sensitive code " +"generated by the app, in addition to their password. This code acts as the " +"second factor of authentication, providing an extra layer of security as it " +"changes periodically and is unique to the user's device." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:110 -msgid "text" +#: ../settings/security/two-factor/authenticator-app.rst:None +msgid "Security Code in Google Authenticator App" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:107 +#: ../settings/security/two-factor/authenticator-app.rst:22 msgid "" -"The output of the process that triggered the event. " -"(``$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" +"The app generates codes based on a shared secret key stored securely on both " +"the user's device and the server, ensuring a synchronized and secure " +"authentication process. The method of generating the codes is sometimes also " +"called TOTP (time-based one-time password)." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:121 -msgid "" -"The Object Manager attribute panel displays built-in and custom\n" -"attribute names." +#: ../settings/security/two-factor/authenticator-app.rst:28 +msgid "Enabling the Authenticator App Method" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:121 -msgid "Find a complete list of ticket attributes in the Object Manager." +#: ../settings/security/two-factor/authenticator-app.rst:30 +#: ../settings/security/two-factor/security-keys.rst:28 +msgid "To enable the method, just toggle the switch on in the settings." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:123 -msgid "" -"Ticket attributes are entirely optional, and can be used to customize the " -"tickets that Checkmk creates. (Note that these attributes will be ignored if " -"a new event belongs to an existing ticket.)" +#: ../settings/security/two-factor/authenticator-app.rst:None +msgid "Authenticator App Switch in Settings" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:128 +#: ../settings/security/two-factor/authenticator-app.rst:36 msgid "" -"Why would you want to do this? Maybe you have only one IT guy, and all " -"system monitoring issues should be automatically assigned to him. Or, maybe " -"you're creating multiple notification rules so that database outages take " -"higher priority than disk space warnings." +"Now the users will be able to set up this two-factor authentication method " +"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " +"Once they do, on next sign-in with password, they will be asked to provide " +"an additional security code generated by their mobile device." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:135 -msgid "In most cases, you'll probably want to set one of the following:" +#: ../settings/security/two-factor/security-keys.rst:2 +msgid "Security Keys" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:137 -msgid "group" +#: ../settings/security/two-factor/security-keys.rst:4 +msgid "" +"The security keys method is a type of a two-factor authentication that uses " +"Web Authentication API in the browser for verifying user's identity. The " +"user can register multiple hardware or software security keys with their " +"Zammad account and then they can use it during the sign-in process." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:139 -msgid "state" +#: ../settings/security/two-factor/security-keys.rst:12 +msgid "" +"When logging in, the user is prompted to provide the same security key they " +"registered with their account, in addition to their password. This key acts " +"as the second factor of authentication, providing an extra layer of security." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:140 -msgid "priority" +#: ../settings/security/two-factor/security-keys.rst:None +msgid "Security Key dialog in Safari on macOS" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:142 +#: ../settings/security/two-factor/security-keys.rst:21 msgid "" -"but in practice, you can set almost any attribute, including :doc:`custom " -"ones you created through the Object Manager `." -msgstr "" - -#: ../system/integrations/checkmk/api-reference.rst:145 -msgid "Please note that the following attributes are **not customizable**:" +"The type of the key can range from hardware USB sticks to passkeys stored in " +"a device of user's choice. Which type can be used depends on the browser " +"flavor and the platform of the user." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:147 -msgid "title" +#: ../settings/security/two-factor/security-keys.rst:26 +msgid "Enabling the Security Keys Method" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:148 -msgid "id" +#: ../settings/security/two-factor/security-keys.rst:None +msgid "Security Keys Switch in Settings" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:149 -msgid "ticket number" +#: ../settings/security/two-factor/security-keys.rst:34 +msgid "" +"Now the users will be able to set up this two-factor authentication method " +"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " +"Once they do, on next sign-in with password, they will be asked to provide " +"the same security key they registered during the setup." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:151 -msgid "created_by_id" +#: ../settings/system/system-selfhosted.include.rst:3 +msgid "" +"Below settings are only available to self hosted users. In hosted " +"environments we're handling these settings for you to ensure service " +"stability." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:152 -msgid "updated_by_id" +#: ../settings/system/base.rst:11 +msgid "Fully Qualified Domain Name" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:155 -msgid "Which Values Can Be Set?" +#: ../settings/system/base.rst:7 +msgid "The URL of your Zammad installation." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:157 -msgid "😵 **Invalid values → unpredictable behavior**" +#: ../settings/system/base.rst:9 ../settings/system/base.rst:17 +msgid "This setting is used within :doc:`/misc/variables` and notifications." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:159 -msgid "" -"If you provide a value that Zammad doesn't understand (*e.g.,* ``-F " -"\"priority=high\"``), it's not always clear what will happen. In some cases, " -"a ticket will be created with the default values instead - but in others, it " -"may not be created at all!" +#: ../settings/system/system-base.include.rst:1 +msgid "It is automatically set by the *Getting Started wizard*." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:164 -msgid "So what values does Zammad understand, then? Well, it depends..." +#: ../settings/system/system-base.include.rst:5 +msgid "Changing this setting also changes callback URLs for your channels etc." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:168 -msgid "Use an email address or username:" +#: ../settings/system/system-base.include.rst:6 +msgid "This setting can have negative affects on being able to login." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:190 -msgid "group & priority" +#: ../settings/system/base.rst:19 +msgid "HTTP type" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:175 -msgid "Refer to the dropdown menus in the ticket pane:" +#: ../settings/system/base.rst:14 +msgid "" +"The HTTP type tells your installation how your clients connect. This is " +"relevant for authentication and cookie security." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:0 -msgid "See possible values for certain attributes in the ticket pane." +#: ../settings/system/base.rst:31 +msgid "SystemID" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:187 -msgid "🙅 **Ticket state CANNOT be set this way!**" +#: ../settings/system/base.rst:22 +msgid "" +"This ID is being used within your ticket number. In case you're " +"communicating with another ticket system with similar ticket number schemes " +"this ID greatly reduces the risk of false follow ups." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:189 +#: ../settings/system/base.rst:26 msgid "" -"Why? Because ``-F \"state=...\"`` is already used :ref:`as a Checkmk " -"parameter `." +"The SystemID is randomly selected upon installation of Zammad (``1-99``)." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:222 -msgid "Everything Else" +#: ../settings/system/base.rst:30 +msgid "" +"**Do not** change this setting in a productive system! Your Zammad " +"installation may no longer recognize old ticket number based follow ups upon " +"change!" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:193 -msgid "" -"To set any other attributes, it helps to know your way around the :docs:" -"`rails console `. Valid values are those that you can " -"set with a string:" +#: ../settings/system/frontend.rst:2 +msgid "Frontend" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:218 -msgid "These values can then be passed directly to the API:" +#: ../settings/system/frontend.rst:22 +msgid "Core Workflow Ajax Mode" msgstr "" -#: ../system/integrations/checkmk/index.rst:16 -msgid "How does it work?" +#: ../settings/system/frontend.rst:6 +msgid "" +"This setting allows administrators to enforce :doc:`/system/core-workflows` " +"to use Ajax-Calls instead of web sockets. You'll usually only need this if " +"you experience serious issues as noted below." msgstr "" -#: ../system/integrations/checkmk/index.rst:2 -msgid "Checkmk" +#: ../settings/system/frontend.rst:10 +msgid "**🤓 Possible (technical) reasons**" msgstr "" -#: ../system/integrations/checkmk/index.rst:4 +#: ../settings/system/frontend.rst:12 msgid "" -"`Checkmk `_ is a powerful IT monitoring tool that can " -"send real-time status alerts to Zammad via email or REST API. Set these " -"alerts up in Checkmk, and Zammad will automatically create, update, and " -"close tickets based on the health of your system:" +"In some cases, your network structure (e.g. firewalls, proxies) may " +"disconnect long web socket connections. This leads to select fields staying " +"empty (e.g. owner selection *after* selecting your group) or fields not " +"shown / hidden (e.g. when switching to or from pending states, the \"pending " +"till\" field not showing / hiding)." msgstr "" -#: ../system/integrations/checkmk/index.rst:14 -msgid "Screenshot of ticket created by Checkmk notifications" +#: ../settings/system/frontend.rst:18 +msgid "" +"Please keep in mind that the Ajax fallback may cause serious pressure on " +"your application server. If you have the choice stick to web sockets." msgstr "" -#: ../system/integrations/checkmk/index.rst:14 -msgid "Multiple alerts, same ticket." +#: ../settings/system/frontend.rst:22 +msgid "Default: ``no`` (inactive)" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:2 -msgid "Setup Guide" +#: ../settings/system/frontend.rst:53 +msgid "Show calendar weeks in the picker of date/datetime fields" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:4 +#: ../settings/system/frontend.rst:25 msgid "" -"Whenever the Checkmk integration is enabled, Zammad listens for messages on " -"its API and over email. As long as those messages follow the required " -"format, Zammad will create new tickets (or find and update existing ones) " -"based on the message contents." +"With this setting you can instruct Zammad to provide week number display " +"globally for all users. Calendar with week number display are usually used " +"in business sectors and may not be relevant for everyone." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:10 +#: ../settings/system/frontend.rst:29 msgid "" -"That means that “setting up Checkmk integration” is simply a matter of " -"**adding configuration to your Checkmk site**: telling it when to send these " -"messages and what to say. To do that, you'll need to create a new " -"**notification rule** (see `Checkmk's official docs `_ for help with that)." +"This setting affects *all areas* - you'll also see week numbers in the admin " +"panel for e.g. triggers and macros." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:17 -msgid "" -"As part of this new rule, you'll have to choose a **notification method** " -"(*i.e.,* a script to execute whenever the rule is triggered). This script " -"will be written by you (samples below), and contain the logic for sending " -"API/email messages to Zammad:" +#: ../settings/system/frontend.rst:32 +msgid "Default: ``no`` (not shown)" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:26 -msgid "Checkmk \"New Rule\" dialog" +#: ../settings/system/frontend.rst:53 +msgid "Here's the difference:" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:26 -msgid "" -"Find your custom scripts in the Checkmk WATO under **Notifications > New " -"Rule > Notification Method**." +#: ../settings/system/frontend.rst:0 +msgid "Screenshot showing Zammad's date picker (in the default way)" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:29 -msgid "" -"Once you're done setting up your new rule, you're all set! New tickets " -"should start coming in and auto-updating any time your rule is triggered." +#: ../settings/system/frontend.rst:41 +msgid "Set to ``no``" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:33 +#: ../settings/system/frontend.rst:0 msgid "" -"(If you need help troubleshooting, be sure to check the :ref:`checkmk-recent-" -"logs`.)" +"Screenshot showing Zammad's date picker with\n" +"week numbers enabled" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:38 -msgid "API Alerts" +#: ../settings/system/frontend.rst:50 +msgid "Set to ``yes``" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:40 +#: ../settings/system/index.rst:4 msgid "" -"To add these scripts in the Checkmk WATO, copy them into your Checkmk " -"installation directory and make them executable. (Be sure to replace the " -"``zammad.example.com`` callback URL with the one found in your admin panel.)" +"For your overview we split each tab within system settings into its own page:" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:60 -msgid "Service notification" +#: ../settings/system/index.rst:16 +msgid "Console Based Settings" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:46 +#: ../settings/system/index.rst:18 msgid "" -"For updates on the status of the software running on your server (*e.g.,* " -"postgres)." +"There's some console based settings we didn't put into the UI. However, you " +"may find them helpful - you can find them in our :docs:`hidden settings ` section." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:75 -msgid "Host notification" +#: ../settings/system/network.rst:2 +msgid "Network" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:63 -msgid "For updates on the status of the server itself." +#: ../settings/system/network.rst:8 +msgid "" +"The proxy settings can only be saved after successfully testing the proxy " +"connection." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:77 -msgid "🤔 **What's with all the env vars?**" +#: ../settings/system/network.rst:15 +msgid "Proxy Address." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:79 +#: ../settings/system/network.rst:12 msgid "" -"Whenever Checkmk runs these scripts, it needs to provide some information " -"about the event that triggered the notification. This information is passed " -"in the form of these ``$NOTIFY_*`` environment variables." +"Allows you to provide a proxy server if needed. This is relevant for network " +"communication by Zammad." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:85 -msgid "" -"You can specify additional parameters to pass to the script when you're " -"setting up your notification rule, but the ones you see here are all " -"provided by default." +#: ../settings/system/network.rst:15 +msgid "It **does not** affect the update process or Elasticsearch." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:90 -msgid "Email Alerts" +#: ../settings/system/network.rst:18 +msgid "Username for proxy connection." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:94 +#: ../settings/system/network.rst:18 msgid "" -"🐞 **There are known bugs** in Zammad's processing of email from Checkmk. " -"This section will be completed once they have been resolved. (Learn more at " -"GitHub issues `#2377 `_ & " -"`#2180 `_.)" +"If your proxy server requires authentication, provide the username here." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:100 -msgid "In the meantime, we encourage you to set up API alerts instead." +#: ../settings/system/network.rst:21 +msgid "Password for proxy connection." msgstr "" -#: ../system/integrations/clearbit.rst:2 -msgid "Clearbit" +#: ../settings/system/network.rst:21 +msgid "" +"If your proxy server requires authentication, provide the password here." msgstr "" -#: ../system/integrations/clearbit.rst:4 +#: ../settings/system/network.rst:26 +msgid "No proxy for the following hosts." +msgstr "" + +#: ../settings/system/network.rst:24 msgid "" -"With our Clearbit integration, you can easily enrich the information " -"provided by Zammad. If the customers or agents email address is known to " -"Clearbit, it will share all information it has regarding the user with " -"Zammad. Those information can include the following:" +"Exception list for hosts you can't or don't want to reach via proxy server." msgstr "" -#: ../system/integrations/clearbit.rst:9 -msgid "Avatar" +#: ../settings/system/network.rst:27 +msgid "Default: ``localhost,127.0.0.0,::1``" msgstr "" -#: ../system/integrations/clearbit.rst:10 -msgid "Address information" +#: ../settings/system/services.rst:2 +msgid "Services" msgstr "" -#: ../system/integrations/clearbit.rst:11 -msgid "Website information" +#: ../settings/system/services.rst:10 +msgid "Image Service" msgstr "" -#: ../system/integrations/clearbit.rst:12 -msgid "A BIO (as Note by default)" +#: ../settings/system/services.rst:5 +msgid "Defines the backend for user and organization image lookups." msgstr "" -#: ../system/integrations/clearbit.rst:14 -msgid "" -"If needed, you can add further custom objects and add mappings to them, so " -"the Clearbit information can be filled within the database. In general you " -"can get any information from Clearbit, as long as you have a mapping to an " -"Zammad object." +#: ../settings/system/services.rst:7 +msgid "Default: ``Zammad Image Service`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:21 +#: ../settings/system/services.rst:9 msgid "" -"Clearbit does have a mapping of fields like LDAP and Exchange have, but does " -"not \"win\" against Zammad information. This means that if you have e.g. the " -"last name field filled in already and Clearbit has other information on " -"that, it will not be updated." +"Make sure your on premise installation has ``HTTPS`` access to ``images." +"zammad.com``." msgstr "" -#: ../system/integrations/clearbit.rst:26 -msgid "" -"However: If let's say the last name has been set by Clearbit and Zammad " -"notices that the last name on the Clearbit source has changed, Zammad will " -"also update this value." +#: ../settings/system/services.rst:18 +msgid "Geo Calendar Service" msgstr "" -#: ../system/integrations/clearbit.rst:33 +#: ../settings/system/services.rst:13 msgid "" -"The configuration of Clearbit is really easy and done fast! Just login to " -"your Clearbit-Account, go to \"API\" and copy the secret-API-Key." +"Defines the backend for geo calendar lookups. Used for initial calendar " +"setup." msgstr "" -#: ../system/integrations/clearbit.rst:38 -msgid "" -"Now change to your Zammad instance, go to Integrations (System) -> Clearbit " -"in the admin panel. Paste your API-Key into the API-Key-Field and decide if " -"Zammad should create unknown Organizations automatically, if the user does " -"not have one yet (and Clearbit knows it). The shared option decides if the " -"new organizations Zammad creates with Clearbit should be shared ones." +#: ../settings/system/services.rst:16 +msgid "Default: ``Zammad GeoCalendar Service`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:47 +#: ../settings/system/services.include.rst:2 msgid "" -"If you're unsure what option to choose, better stick with \"no\". You can " -"also learn more about :doc:`/manage/organizations/index`." +"Make sure your on premise installation has ``HTTPS`` access to ``geo.zammad." +"com``." msgstr "" -#: ../system/integrations/clearbit.rst:52 -msgid "" -"The Mapping option works similar to the mapping within the Exchange and LDAP " -"sync. You can add further mappings for e.g. custom fields if you need more " -"information that Clearbit can provide." +#: ../settings/system/services.rst:26 +msgid "Geo IP Service" msgstr "" -#: ../system/integrations/clearbit.rst:58 +#: ../settings/system/services.rst:21 msgid "" -"If you want to add more Clearbit fields and want to learn more about " -"available fields on their API, you can take a look at their `API " -"documentation `_." +"Defines the backend for geo IP lookups. Shows also location of an IP address " +"if an IP address is shown." msgstr "" -#: ../system/integrations/clearbit.rst:62 -msgid "" -"If you're happy with the above chosen Settings and your mapping, just save " -"the changes and enable Clearbit integration. Zammad will now start polling " -"the Clearbit API as users contact you." +#: ../settings/system/services.rst:24 +msgid "Default: ``Zammad GeoIP Service`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:68 -msgid "" -"Zammad does not synchronize with Clearbit on a regular basis, but on demand " -"if needed. This saves API calls." +#: ../settings/system/services.rst:32 +msgid "Geo Location Service" msgstr "" -#: ../system/integrations/clearbit.rst:73 +#: ../settings/system/services.rst:29 msgid "" -"Below the Settings and Mappings, you'll find our Integration log. You can " -"see what requests Zammad sent to Clearbit and also the APIs Response." +"Defines the backend for geo location lookups to store geo locations for " +"addresses." msgstr "" -#: ../system/integrations/clearbit.rst:78 +#: ../settings/system/services.rst:32 msgid "" -"By the way, you can also view the API log on the Clearbit website - the " -"information seen is basically the same." -msgstr "" - -#: ../system/integrations/clearbit.rst:84 -msgid "Example When Adding a User" +"Default: ``OpenStreetMap (ODbL 1.0, http://osm.org/copyright)`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:86 +#: ../settings/system/services.rst:36 msgid "" -"To show you how fast information is added, we added a small Screencast " -"below. This shows the creation of the User Alex from Clearbit. As we already " -"set the last name of Alex to \"X\", Zammad did not update it. What Zammad " -"did was to add further information it received from Clearbit." +"You can find a detailed privacy information on what we store for how long on " +"our :docs:`Privacy Appendix ` inside of our System " +"Documentation." msgstr "" -#: ../system/integrations/cti/generic.rst:2 -msgid "CTI (generic)" +#: ../settings/system/storage.rst:2 +msgid "Storage" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:1 +#: ../settings/system/storage.rst:6 msgid "" -"This integration enables Zammad to provide a caller log to your agents. With " -"this your agents can greet your customers by their name and are supported by " -"Zammad with automatically opening a new ticket dialog or the user profile." +"Here you can define where Zammad stores attachments for tickets and the " +"knowledge base. By default, we're writing to the ``Database`` - you can " +"switch to ``Filesystem`` or ``Simple Storage (S3)`` at any time. In this " +"case please have a look on the following instructions." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:6 +#: ../settings/system/storage.rst:11 msgid "" -"Click the toggle next to the heading to activate or deactivate this " -"integration." +"If you have a busy Zammad instance, we strongly encourage you to use " +"filesystem storage instead of \"Database\". This will greatly improve system " +"performance (de-crease database load and size)." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:9 -msgid "" -"If you want to learn more on how your agents can use this function, please " -"refer the :user-docs:`user documentation `." +#: ../settings/system/storage.rst:19 +msgid "Database" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:14 +#: ../settings/system/storage.rst:17 msgid "" -"Automatically opening new ticket dialogues or user profiles requires agent " -"to extension mapping - see more below." -msgstr "" - -#: ../system/integrations/cti/includes/introduction.include.rst:20 -msgid "Please note the following limitations to reduce confusion later on:" +"This is the default storage method. The attachments are stored directly in " +"the database. If your Zammad instance grows, we recommend one of the other " +"methods to maintain performance." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:22 -msgid "CTI integrations provide caller log functions only." +#: ../settings/system/storage.rst:38 +msgid "Filesystem" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:23 +#: ../settings/system/storage.rst:22 msgid "" -"This integration does not provide any VoIP functionalities; you can't make " -"phone calls from within Zammad." +"This storage method is recommended for all Zammad instances, especially for " +"those with a higher load. If you choose filesystem, your files are written " +"to ``/opt/zammad/storage/``." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:25 +#: ../settings/system/storage.rst:26 msgid "" -"If your browser supports ``tel``-URLs, you can click on phone numbers for " -"automatic dialing. This requires additional software / configuration on your " -"agent's computers." +"Moving attachments from \"Database\" to \"Filesystem\" can be run during " +"production use. However, you should consider your framework conditions (e.g. " +"bandwidth, system load in production) to define the right moment." msgstr "" -#: ../system/integrations/cti/generic.rst:9 -#: ../system/integrations/cti/placetel.rst:14 -#: ../system/integrations/cti/sipgate.rst:14 -msgid "Please provide the following requirements:" +#: ../settings/system/storage.rst:32 +msgid "**You noticed slow updates of Zammad?**" msgstr "" -#: ../system/integrations/cti/generic.rst:11 +#: ../settings/system/storage.rst:34 msgid "" -"A telephone system that supports webhooks (outbound) (best option are those " -"that allow customizing the calls)." +"While Zammad is beeing updated, it enforces a recursive \"change " +"owner\" (chown) for this directory. For instances with many files this can " +"be time consuming. To mitigate that you can move your files and create a " +"symlink in ``/opt/zammad/storage/`` to the new directory. Of course you have " +"to make sure on your own that the permissions are always correct." msgstr "" -#: ../system/integrations/cti/generic.rst:13 -msgid "A unique Call-ID during the call session." +#: ../settings/system/storage.rst:95 +msgid "Simple Storage (S3)" msgstr "" -#: ../system/integrations/cti/generic.rst:14 -msgid "Call event data (both numbers and direction)." +#: ../settings/system/storage.rst:41 +msgid "" +"To use the Simple Storage (S3), you have to provide some settings, which " +"can't be accessed in the UI (see instructions below)." msgstr "" -#: ../system/integrations/cti/generic.rst:15 -msgid "Your Zammad instance must be reachable for your telephony system." +#: ../settings/system/storage.rst:44 +msgid "" +"⚠️ Please note that the current implementation is in its early stages and can " +"be modified in the future." msgstr "" -#: ../system/integrations/cti/generic.rst:17 +#: ../settings/system/storage.rst:47 msgid "" -"If you want to learn more on what kind of requests are supported by Zammad " -"and what it expects, please consult our :docs:`CTI-API documentation `." +"The prerequisite is to have access to a S3-compatible storage and to have " +"all necessary parameters available (which depends on your storage provider; " +"if in doubt, please ask there for help)." msgstr "" -#: ../system/integrations/cti/generic.rst:22 -#: ../system/integrations/cti/placetel.rst:27 -#: ../system/integrations/cti/sipgate.rst:30 -msgid "Available Settings" +#: ../settings/system/storage.rst:51 +msgid "Steps to configure S3:" msgstr "" -#: ../system/integrations/cti/generic.rst:29 -#: ../system/integrations/cti/placetel.rst:41 -#: ../system/integrations/cti/sipgate.rst:40 -msgid "Endpoint Settings" +#: ../settings/system/storage.rst:53 +msgid "" +"Copy ``config/zammad/storage.yml.dist`` to ``config/zammad/storage.yml``" msgstr "" -#: ../system/integrations/cti/generic.rst:25 -msgid "" -"Zammad will list your generic CTI endpoint here. It contains a unique token " -"so ensure to keep this URL save." +#: ../settings/system/storage.rst:54 +msgid "Edit the copied file in one of the following ways:" msgstr "" -#: ../system/integrations/cti/generic.rst:28 +#: ../settings/system/storage.rst:56 msgid "" -"You'll need this endpoint for your PBX to talk to Zammad, see :docs:`CTI-API " -"documentation `." +"Either provide your S3 configuration with one attribute per line like in the " +"upper area of the file" msgstr "" -#: ../system/integrations/cti/includes/important-dont-forget-saving.include.rst:3 +#: ../settings/system/storage.rst:58 msgid "" -"All following options **do not save automatically**. Always use the Save " -"button on the lower end of the integration page!" +"Or provide your S3 configuration as an URL (which you can find at the end of " +"the file). Note: you can also provide this URL as environment variable (:" +"docs:`see system documentation `) without using this yml-file." msgstr "" -#: ../system/integrations/cti/generic.rst:43 -#: ../system/integrations/cti/placetel.rst:49 -#: ../system/integrations/cti/sipgate.rst:52 -msgid "Call Settings" +#: ../settings/system/storage.rst:62 +msgid "" +"We recommend the deletion of the not used configuration style to avoid " +"inconsistencies." msgstr "" -#: ../system/integrations/cti/generic.rst:39 -#: ../system/integrations/cti/placetel.rst:49 -#: ../system/integrations/cti/sipgate.rst:37 -#: ../system/integrations/cti/sipgate.rst:50 -msgid "Inbound" +#: ../settings/system/storage.rst:65 +msgid "Restart Zammad so the config file / environment variable is loaded" msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:1 +#: ../settings/system/storage.rst:66 msgid "" -"This option allows you to block specific incoming caller IDs. It allows you " -"to temporarily reject e.g. spam callers without having to contact providers " -"or PBX administrators." +"Set the \"Storage Method\" in Zammad to ``Simple Storage (S3)`` in Settings " +"> System > Storage and click on \"Submit\". After that, Zammad checks your " +"configuration and the connection to the service and will raise an error " +"message if something is wrong." msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:11 -msgid "Caller ID to block" +#: ../settings/system/storage.rst:72 +msgid "A very simple storage configuration could look like this:" msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 -msgid "Provide caller IDs to block in ``E.164`` format." +#: ../settings/system/storage.rst:85 +msgid "" +"Before setting the storage method to ``Simple Storage (S3)`` (step 4), " +"please make sure to have a working setup." msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:8 +#: ../settings/system/storage.rst:88 msgid "" -"Your telephony system has to support this function. Zammad will send a " -"``reject`` response which will cause your telephony system to hang up the " -"call. To callers this usually will feel like the line is busy." +"You can verify this by running ``rails r 'Rails.logger = Logger.new(STDOUT); " +"pp Store::Provider::S3.ping?'`` in your Zammad directory. If everything is " +"fine, you should see ``true``, else you should see ``false`` and a simple " +"error message." msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:14 +#: ../settings/system/storage.rst:93 msgid "" -"Provide a meaningful note for your fellow administrators to remind yourself " -"why you've chosen to block the number." +"If you installed Zammad through a package manager (rather than from source), " +"replace ``rails r`` with ``zammad run rails r`` above. To learn more, see :" +"docs:`Administration via Console `." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 -#: ../system/integrations/cti/includes/outbound-calls.include.rst:17 -#: ../system/integrations/cti/sipgate.rst:40 -msgid "Outbound" +#: ../settings/ticket.rst:4 +msgid "" +"Here you can adjust general ticket settings. Additional ones for the ticket " +"composer interface can be found in the :doc:`/misc/composer`." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:1 -msgid "" -"In many cases you may want to use a different caller ID depending on the " -"destination you're calling. This may apply due to specific connection rates " -"to other countries or because you want your customer to feel you're calling " -"from the same country." +#: ../settings/ticket.rst:11 +msgid "Ticket Hook (default: ``Ticket#``)" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:6 -msgid "This option expects ``E.164`` number formats." +#: ../settings/ticket.rst:11 +msgid "The identifier for a ticket; *e.g.,* Ticket#, Call#, MyTicket#." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 -msgid "Destination caller ID" +#: ../settings/ticket.rst:38 +msgid "Ticket Hook Position (default: ``right``)" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:5 -msgid "The caller ID or number you're trying to call." +#: ../settings/ticket.rst:14 +msgid "" +"With this setting you can decide (if) where to insert the ticket number." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:7 -msgid "You can use wildcards for e.g. country specific outbound numbers like:" +#: ../settings/ticket.rst:20 +msgid "*Right*" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:9 -msgid "``49*`` for Germany" +#: ../settings/ticket.rst:17 +msgid "" +"This setting will add the ticket reference on the right site of the subject." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:10 -msgid "``4930*`` for Berlin / Germany landlines" +#: ../settings/ticket.rst:20 +msgid "Example: ``Some Subject [Ticket#12345]``" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 -msgid "``33*`` for France" +#: ../settings/ticket.rst:26 +msgid "*Left*" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:15 -msgid "Set Outbound caller ID" +#: ../settings/ticket.rst:23 +msgid "" +"This setting will add the ticket reference on the left site of the subject." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:14 -msgid "" -"The outbound caller ID to set (the number your customer sees on his display) " -"in ``E.164`` number format." +#: ../settings/ticket.rst:26 +msgid "Example: ``[Ticket#12345] Some Subject``" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 -msgid "Provide a short description for fellow administrators." +#: ../settings/ticket.rst:29 +msgid "*None*" msgstr "" -#: ../system/integrations/cti/includes/generic-cti-support-note.includes.rst:3 -msgid "" -"This option requires your PBX to send a specific request to Zammad *before " -"dialing*. Please consult the :docs:`CTI API ` in case " -"you're not sure." +#: ../settings/ticket.rst:29 +msgid "This will completely remove ticket references from the subject." msgstr "" -#: ../system/integrations/cti/generic.rst:52 -#: ../system/integrations/cti/placetel.rst:54 -#: ../system/integrations/cti/sipgate.rst:59 -msgid "Other Settings" +#: ../settings/ticket.rst:33 +msgid "" +"Please ensure to take a look at :doc:`/channels/email/settings` within the " +"email channel to ensure you have at least one reference that helps Zammad to " +"assign follow-ups correctly." msgstr "" -#: ../system/integrations/cti/includes/other-settings-intro.include.rst:1 +#: ../settings/ticket.rst:37 msgid "" -"Below you can find all available additional settings for this CTI " -"integration. For your overview we're sorting them by appearance and " -"reference their description first." +"Disabling this and not setting up any further follow up search will lead to " +"unexpected results!" msgstr "" -#: ../system/integrations/cti/includes/default-caller-id.include.rst:2 -#: ../system/integrations/cti/includes/default-caller-id.include.rst:1 -msgid "Default caller ID for outbound calls" +#: ../settings/ticket.rst:65 +msgid "" +"Ticket Last Contact Behaviour (default: ``Use the start time of the last " +"customer thread (which may consist of multiple articles).``)" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:16 -#: ../system/integrations/cti/includes/records-caller-log.include.rst:15 -msgid "Shown records in caller log" +#: ../settings/ticket.rst:41 +msgid "" +"This setting changes the way Zammad updates the ``Last Contact`` value of a " +"ticket. This is fairly important for overviews and what you expect upon " +"ticket updates of a customer." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:2 +#: ../settings/ticket.rst:52 msgid "" -"Allows you to set the number of shown caller log entries for all users. You " -"can choose from the following values:" +"Use the start time of the last customer thread (which may consist of " +"multiple articles)." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:5 -msgid "60 (default)" +#: ../settings/ticket.rst:46 +msgid "" +"If this option is chosen, Zammad will update the last updated value just " +"once if a customer replies. After that, Zammad will wait for an agent to " +"react." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:6 -msgid "120" +#: ../settings/ticket.rst:50 +msgid "" +"This comes in handy if you want to work tickets in the order of their first " +"update. This will not change ticket orders if customers decide to \"bump\" " +"the ticket affected." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:7 -msgid "180" +#: ../settings/ticket.rst:57 +msgid "Use the time of the very last customer article." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:8 -msgid "240" +#: ../settings/ticket.rst:55 +msgid "" +"When setting this option, Zammad will always update the last updated value. " +"This means that if ordering by ``Last Update``, ticket orders will change if " +"customers \"bump\" the ticket." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:9 -msgid "300" +#: ../settings/ticket.rst:64 +msgid "Last contact value used on :doc:`/manage/overviews`" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:11 -msgid "**🥵 Potential performance issue**" +#: ../settings/ticket.rst:65 +msgid "Last contact value used on :doc:`/manage/trigger`" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:13 +#: ../settings/ticket.rst:88 msgid "" -"Setting this setting higher than 60 may cause serious performance issues on " -"very busy instances. Keep in mind that this setting causes Zammad to poll " -"and send up to 300 records to *all active agent sessions* in very short time " -"periods." +"Ticket Organization Reassignment (default: ``Update the most recent tickets." +"``)" msgstr "" -#: ../system/integrations/cti/generic.rst:73 -msgid "Caller Log Filter" +#: ../settings/ticket.rst:68 +msgid "" +"This setting changes the way Zammad updates the organization field of the " +"tickets whenever the primary organization of a user is changed." msgstr "" -#: ../system/integrations/cti/generic.rst:55 -msgid "" -"This function allows you to provide call information based on e.g. queues " -"only to agents that really need the information." +#: ../settings/ticket.rst:74 +msgid "Update the most recent tickets." msgstr "" -#: ../system/integrations/cti/generic.rst:58 +#: ../settings/ticket.rst:72 msgid "" -"Why? If you have a team for several countries or departments, you don't want " -"to bug your agents from other departments. Leaving these options empty will " -"fallback to showing everything to everyone." +"If this option is chosen, Zammad will update the 100 most recent tickets " +"where the user is the ticket customer. The ticket organization field will be " +"automatically set to the new primary organization of the user." msgstr "" -#: ../system/integrations/cti/generic.rst:64 -msgid "Destination caller ID or Queue" +#: ../settings/ticket.rst:88 +msgid "Do not update any tickets." msgstr "" -#: ../system/integrations/cti/generic.rst:63 +#: ../settings/ticket.rst:77 msgid "" -"This depends on your PBX and usually is either a queue ID, phone number or " -"extension." +"When choosing this option, Zammad will not update any tickets when the " +"user's primary organization is changed." msgstr "" -#: ../system/integrations/cti/generic.rst:69 -msgid "Agents" +#: ../settings/ticket.rst:80 +msgid "**Use with care!**" msgstr "" -#: ../system/integrations/cti/generic.rst:67 +#: ../settings/ticket.rst:82 msgid "" -"Select the agents that are responsible for the group. These agents will then " -"see caller log entries and call notifications fitting to said queue." +"Using this option may lead to inconsistencies in the system as the ticket " +"organization may become decoupled from the ticket customer." msgstr "" -#: ../system/integrations/cti/generic.rst:0 +#: ../settings/ticket.rst:85 msgid "" -"Screenshot showing the caller log filter table with pre filled sample data" +"However, you may use this option if you wish to maintain :ref:`the shared " +"access ` to the ticket for all organization " +"members of the original organization of the customer." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:6 -msgid "" -"With recent logs Zammad allows you to view the latest calls for the CTI " -"functionality. This usually comes in handy, when you're looking for errors." +#: ../settings/ticket.rst:110 +msgid "Ticket Number Format (default: ``Increment (SystemID.Counter)``)" msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:0 +#: ../settings/ticket.rst:94 msgid "" -"Screenshot showing several incoming requests within Recent logs section." +"This setting defines the way Zammad's ticket number will look. Changing this " +"setting in production will cause follow up detection to fail." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:16 -msgid "I'm just here to clear floats up." +#: ../settings/ticket.rst:102 +msgid "Increment (SystemID.Counter)" msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:20 +#: ../settings/ticket.rst:98 msgid "" -"By clicking on the entry of interest, Zammad will provide more details on " -"the call in question. You'll see the payload it received and also the " -"response that was sent." +"The increment value contains the SystemID (automatically generated during " +"installation) and a increment which counts up with every new Ticket. The " +"increment will automatically get another digit if needed." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:0 -msgid "" -"Screenshot showing detailed information of a specific log entry of recent " -"logs" +#: ../settings/ticket.rst:102 +msgid "Examples: ``1010138``, ``1010139``" msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:31 -msgid "x" +#: ../settings/ticket.rst:110 +msgid "Date (Year.Month.Day.SystemID.Counter)" msgstr "" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 -#: ../system/integrations/cti/includes/troubleshooting.include.rst:9 -msgid "My Phone page stays blank, signalling does work..." +#: ../settings/ticket.rst:105 +msgid "" +"This version of the ticket number is fairly long. However, because it " +"contains the date of ticket creation, it also allows you to see when the " +"ticket has been created. You may feel familiar with this number format if " +"you've worked with OTRS already." msgstr "" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:5 -msgid "" -"If you've made sure that signalling works (check Recent logs) and your " -"Caller Log still stays empty, please ensure that you only configured one CTI " -"integration version. Specifically defining more than one agent mapping on " -"the different integration variants will be the issue." +#: ../settings/ticket.rst:110 +msgid "Examples: ``201206231010138``, ``201206231010139``" msgstr "" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 -msgid "Clear the not needed agent mapping and reload your browser page." +#: ../settings/ticket.rst:137 +msgid "OPTIONS" msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:1 +#: ../settings/ticket.rst:113 msgid "" -"By mapping your agents extension to their existing Zammad users, Zammad can " -"provide a new ticket dialog or open the user profile for the agent that " -"picks up the call." +"The below options allow you to further customize your ticket number. The " +"availability of options differ depending of the chosen ticket number format " +"above." msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:5 -msgid "" -"This speeds up ticket aiding, no matter if it's for existing tickets or new " -"ones!" +#: ../settings/ticket.rst:122 +msgid "Checksum (default: ``no``)" msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:8 +#: ../settings/ticket.rst:118 msgid "" -"To see it work from the agent's perspective, have a look on :user-docs:`user " -"documentation `." +"If set to yes, we'll built a checksum to further \"unique\" the ticket " +"number of your system. If you're dealing with many other ticket systems this " +"might help to prevent false positive follow up detection on tickets." msgstr "" -#: ../system/integrations/cti/placetel.rst:2 -msgid "Placetel CTI" +#: ../settings/ticket.rst:122 +msgid "This will also add another digit to the ticket number." msgstr "" -#: ../system/integrations/cti/placetel.rst:16 -msgid "You need an administrative Placetel account for your organization." +#: ../settings/ticket.rst:137 +msgid "Min. size of Number (default: ``5``)" msgstr "" -#: ../system/integrations/cti/placetel.rst:17 -#: ../system/integrations/cti/sipgate.rst:20 +#: ../settings/ticket.rst:125 msgid "" -"Your Zammad instance must be allowed to communicate to external services." +"This setting defines the minimum length of your ticket number. If your " +"counter is not yet high enough, Zammad will fill the number with zeros to " +"ensure the wanted length." msgstr "" -#: ../system/integrations/cti/placetel.rst:18 -msgid "Placetel must be able to reach your Zammad instance." -msgstr "" - -#: ../system/integrations/cti/placetel.rst:22 -msgid ":doc:`provider-configurations/placetel`" -msgstr "" - -#: ../system/integrations/cti/placetel.rst:21 +#: ../settings/ticket.rst:129 msgid "" -"Learn how to configure Placetel to enable Zammad and Placetel to communicate " -"with each other." +"Please note that the minimum length is ``3`` (SystemID + at least one digit " +"if below 10). Also, if the length is no longer long enough, the number will " +"automatically get one digit longer. Ticket-Numbers **do not overflow**, thus " +"it's save to keep it at 5 or set it lower if wanted." msgstr "" -#: ../system/integrations/cti/placetel.rst:32 +#: ../settings/ticket.rst:135 msgid "" -"The here listed endpoint settings are relevant for the :doc:`integration " -"configuration with Placetel `." +"This option is only available if ticket number format is set to " +"``Increment``!" msgstr "" -#: ../system/integrations/cti/placetel.rst:37 -#: ../system/integrations/i-doit.rst:53 -msgid "Endpoint" +#: ../settings/ticket.rst:142 +msgid "Auto-Assignment" msgstr "" -#: ../system/integrations/cti/placetel.rst:36 +#: ../settings/ticket.rst:144 msgid "" -"This endpoint will be required for the Zammad integration within the " -"Placetel web interface." -msgstr "" - -#: ../system/integrations/cti/placetel.rst:41 -msgid "API Token" +"In a larger Zammad environment, it happens that several agents open the same " +"ticket at the same time. Although collision detection is then effective, the " +"efficiency of processing can be increased by means of the automatic " +"assignment of tickets when a ticket is opened." msgstr "" -#: ../system/integrations/cti/placetel.rst:40 +#: ../settings/ticket.rst:149 msgid "" -"You'll receive this token within the ``Web API`` menu. Make sure to copy " -"this value, it's only shown once!" -msgstr "" - -#: ../system/integrations/cti/placetel.rst:71 -#: ../system/integrations/cti/sipgate.rst:77 -msgid "Phone Extension to Agent Mapping" +"The automatic assignment of tickets can be activated and configured in the " +"admin area under Settings > Ticket > Auto Assignment." msgstr "" -#: ../system/integrations/cti/placetel.rst:0 -msgid "Screenshot showing sample user mappings in between Placetel and Zammad" +#: ../settings/ticket.rst:152 +msgid "" +"The auto assignment only works if the ticket has no owner yet. By default, " +"the agent can always reset the ticket owner to ``-`` if needed." msgstr "" -#: ../system/integrations/cti/placetel.rst:64 +#: ../settings/ticket.rst:155 msgid "" -"You can find your agents Placetel username combination required within ⚙️ PBX " -"→ VoIP destinations. Within the \"Advanced settings\" section you're looking " -"for \"SIP user name\" and \"SIP server\"." +"If you want to use this function for only specific tickets, you can " +"configure the conditions accordingly to meet your requirement. By default " +"the condition affects all tickets with the state ``open``." msgstr "" -#: ../system/integrations/cti/placetel.rst:68 -msgid "Combine these two like so: ``@``." +#: ../settings/ticket.rst:161 +msgid "" +"If you need to exclude users (e.g. a group leader), you can search and " +"select the desired agents in the ``Exception Users`` list. The search " +"function in this area is only effective, if you have too many agents to " +"display at once to help you with the configuration." msgstr "" -#: ../system/integrations/cti/placetel.rst:0 -msgid "Sample VoIP credentials for a Placetel user" +#: ../settings/ticket.rst:167 +msgid "Notifications" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:2 -msgid "Setup Placetel connection for Zammad" +#: ../settings/ticket.rst:191 +msgid "Default Notifications" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:6 +#: ../settings/ticket.rst:170 msgid "" -"This configuration step requires a *full* administrative Placetel account. " -"You may receive forbidden error messages with Placetel in case your " -"permissions are not high enough." +"This setting allows you to configure the default ticket notifications that " +"will be applied to all new agent users (incl. users who were just assigned " +"agent role). Simply change the notification matrix to desired state and " +"press **Save**." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:10 +#: ../settings/ticket.rst:175 msgid "" -"The following actions can be configured via the `Placetel web interface " -"`_." -msgstr "" - -#: ../system/integrations/cti/provider-configurations/placetel.rst:29 -msgid "Step 1: Activate Zammad integration" +"In case an agent already exists, their ticket notification preferences will " +"be preserved. Optionally, you can also **Apply current defaults to all " +"agents**." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:14 +#: ../settings/ticket.rst:181 msgid "" -"Within Integrations, scroll down to Partner integrations and select Zammad." +"**Potential time-consuming action:** Applying default ticket notifications " +"to all agent users may take some time to complete, be patient! The exact " +"time will depend on the size of your system and the number of agents." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:17 +#: ../settings/ticket.rst:185 msgid "" -"You can alternatively filter by \"Ticket Systems\" to reduce the number of " -"entries on the page. You'll still want to look for Partner integrations. 🤓" +"**Active agents only!** When current default ticket notifications are " +"applied, only active agent users are considered. In case an agent is re-" +"activated *after* this action, they will still have the old notification " +"configuration." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:21 +#: ../settings/ticket.rst:190 msgid "" -"Within the Zammad integration now press \"Activate\". A new tab ``API`` " -"becomes available - open this tab." +"In case you want to go back to the initial state of ticket notifications, " +"you can click on **Reset to default** button." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:24 -msgid "" -"Now tick \"Enable Call Control / Notify API\" and paste the Placetel " -"endpoint from your Zammad instance into the field \"URL of your API " -"endpoint\". Save to apply the settings" +#: ../settings/ticket.rst:196 +msgid "Duplicate Detection" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 -msgid "Screencast showing how to activate the Zammad integration" +#: ../settings/ticket.rst:238 +msgid "Detect Duplicate Ticket Creation" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:51 -msgid "Step 2: Generate API Token for Placetel" +#: ../settings/ticket.rst:199 +msgid "" +"This setting turns on the duplicate ticket detection mechanism during ticket " +"creation. If similar tickets are found in the system, a suitable warning " +"will be shown to the user trying to create a ticket." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:32 -msgid "" -"Go back to the integrations page and scroll down to \"Web API\". Generate a " -"new API token by using the \"Create a new API token\" button." +#: ../settings/ticket.rst:206 +msgid "A Sample Duplicate Ticket Warning" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:37 +#: ../settings/ticket.rst:208 msgid "" -"If you already generated a token either use your existing token or reset it " -"by using above mentioned button. Placetel will ask you to conform this reset." +"You can choose which ticket attributes will be matched by selecting them in " +"**Attributes to compare** field. Only if the ticket attribute value provided " +"by the user in the ticket create form is *equal* with the attribute in an " +"existing ticket, the warning will be shown." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:41 -msgid "" -"Please keep in mind that existing API scripts may no longer work due to " -"token resets!" +#: ../settings/ticket.rst:213 +msgid "**Warning title** and **Warning message** are configurable as well." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:44 +#: ../settings/ticket.rst:215 msgid "" -"Copy the provided API token and insert it into the \"API Token\" field " -"within Zammad's Placetel integration." +"You can limit the detection only to certain user roles. By default, only " +"agents will see the warning." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:47 +#: ../settings/ticket.rst:218 msgid "" -"Apply your changes by using the \"Save\" button on the bottom of the " -"Placetel integration page and activate the Placetel integration." +"If you don't want to show the matched tickets as part of the warning, you " +"can set **Show matching ticket(s) in the warning** setting to *no*." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +#: ../settings/ticket.rst:221 msgid "" -"Screencast showing how to retrieve an API token from Placetel for Zammad" +"By default, **Permission level for looking up ticket** is set to *User*, " +"which means user permissions will be honored during sarch. The user will " +"see the warning only if tickets they have access to are matched. " +"Alternatively, you can set this setting to *System*, in which case the " +"search will happen within *all* tickets in the system, regardless of user " +"permissions." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:73 -#: ../system/integrations/cti/provider-configurations/sipgate.rst:77 -msgid "Step 3: Restrict the numbers to notify on" +#: ../settings/ticket.rst:227 +msgid "**🦺 Safety first!**" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:54 +#: ../settings/ticket.rst:229 msgid "" -"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " -"the the Integrations page of the Placetel web interface, go to \"Notify " -"API\"." +"Even if the permission level is set to *System*, the user will not be shown " +"the tickets they don't have access to in the warning, even if they match." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:58 +#: ../settings/ticket.rst:233 msgid "" -"Lower on the page Placetel allows you to restrict the numbers to notify on. " -"You'll find this within the \"External routing API\" part." +"However, just the confirmation about the existence of the tickets in the " +"system may be considered an unwanted information disclosure. Use this option " +"carefully!" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +#: ../settings/ticket.rst:237 msgid "" -"Screenshot showing a sample selection of phone numbers to use for the " -"Placetels notify API" +"Finally, you can configure between matching within **All tickets** or **Open " +"tickets** only by setting **Match tickets in following states**. Depending " +"on the current ticket state, a ticket may or not be matched." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:66 -msgid "" -"This menu point also provides a API request log from Placetel view. Just " -"open \"Recent responses of your API endpoint\" to learn more." +#: ../system/core-workflows.rst:2 +msgid "Core Workflows" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:69 +#: ../system/core-workflows.rst:4 msgid "" -"If you want to see Zammad's perspective, use the \"Recent Logs\" part from " -"within the Placetel integration page." +"Core Workflows allow you to adjust object attributes in many ways. For " +"example:" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 -msgid "Screenshot showing sample log entries for Placetels API calls to Zammad" +#: ../system/core-workflows.rst:7 +msgid "show / hide fields" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:77 -msgid "Step 4 (optional): Further configurations for Placetel" +#: ../system/core-workflows.rst:8 +msgid "adjust mandatory setting" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:76 +#: ../system/core-workflows.rst:9 +msgid "manipulate available options" +msgstr "" + +#: ../system/core-workflows.rst:11 msgid "" -"If needed, you can now configure Zammad's Placetel integration in more " -"detail. You can learn more about your options here: :ref:`Placetel " -"integration settings `." +"With this, you can provide exactly the information your users really need!" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:2 -msgid "Setup Sipgate connection for Zammad" +#: ../system/core-workflows.rst:15 +msgid "" +"If the pre-defined :doc:`/system/objects` are not enough, please add them " +"beforehand." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +#: ../system/core-workflows.rst:17 msgid "" -"Sipgate has no english web interface which is why this documentation page is " -"mixing up languages badly." +"If you experience slow or unreliable field updates, please see :ref:`Core " +"Workflow Ajax Modus `" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +#: ../system/core-workflows.rst:22 msgid "" -"Please also note that the availability of API addons highly depends on your " -"package trier. Usage of sipgate.io packages *is not free*, please check " -"their `pricing page `_ before!" +"This is a very enhanced functionality and can cause unexpected UI behavior. " +"Please ensure to test your use cases after configuration to reduce surprises." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:35 -msgid "Step 1: Book sipgate.io package" +#: ../system/core-workflows.rst:None +msgid "Dialogue for adding a new workflow" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:13 -msgid "Skip to step 2 if you already have the package booked!" +#: ../system/core-workflows/condition-operators.rst:2 +msgid "Core Workflow Condition Operators" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:15 +#: ../system/core-workflows/condition-operators.rst:4 msgid "" -"Login to an administrative Sipgate account and navigate to " -"``Accountverwaltung``. You'll see several different options depending on " -"your booked packages. Select ``Verträge & Produkte`` to continue." +"You might know that there is a separate section for explaining :doc:" +"`condition operators `. Head over there to " +"see a detailed explanation of many conditions and operators." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:19 +#: ../system/core-workflows/condition-operators.rst:8 msgid "" -"Scroll down to the section ``Zusätzliche Produkte buchen`` and look for " -"``sipgate.io`` - select this product by using the ``Produkte anzeigen``-" -"Button." -msgstr "" - -#: ../system/integrations/cti/provider-configurations/sipgate.rst:23 -msgid "" -"On the next page select either one of the ``sipgate.io`` packages or ``Push-" -"API Package Free``. Follow the dialogue by booking the addon. You'll be " -"returned to your contract overview and now should see the selected addon in " -"your list." +"Due to differences to other places in Zammad which are also using conditions " +"(e.g. triggers), you can find a dedicated description of operators for core " +"workflows below." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:30 +#: ../system/core-workflows/condition-operators.rst:12 msgid "" -"The availability for ``sipgate.io`` packages and their levels highly depends " -"on the overall account type and product you've booked with Sipgate." +"Be aware that the availability of the operators depends on the selected " +"attribute and its field type. Some of the operators may only be available " +"for system attributes (e.g. for \"tags\", \"active\")." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screencast showing the process on how to book the required sipgate.io addon" +#: ../system/core-workflows/condition-operators.rst:20 +msgid "Operator" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:52 -msgid "Step 2: Configure webhook for Zammad" +#: ../system/core-workflows/condition-operators.rst:22 +msgid "after (absolute)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:38 -msgid "" -"Within your ``Accountverwaltung`` navicate to your product ``sipgate.io``. " -"In the newly opened tab, switch from \"Clients\" to \"Webhooks\" and paste " -"the endpoint URLs from your Zammad instance like so:" +#: ../system/core-workflows/condition-operators.rst:23 +msgid "Matches if a date/time is after a specific point in time." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:42 -msgid "Inbound endpoint to \"Incoming\"" +#: ../system/core-workflows/condition-operators.rst:24 +msgid "after (relative)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:43 -msgid "Outbound endpoint to \"Outgoing\"" +#: ../system/core-workflows/condition-operators.rst:25 +msgid "Matches if a time span after a specified event has passed." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:47 -msgid "" -"Ensure to select at least one call group or phoneline within \"Sources\". " -"Other wise Sipgate will not indicate any incoming or outgoing calls to " -"Zammad." +#: ../system/core-workflows/condition-operators.rst:26 +msgid "before (absolute)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screencast showing how to add Zammad's endpoint URLs to sipgate.ios webhook " -"configuration" +#: ../system/core-workflows/condition-operators.rst:27 +msgid "Matches if a date/time is before a specific point in time." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:55 -msgid "" -"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " -"the Webhooks → URLs section of Sipgate you can select which *sources* " -"Sipgate should notify Zammad about in- and outgoing calls." +#: ../system/core-workflows/condition-operators.rst:28 +msgid "before (relative)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:59 -msgid "" -"Use either specific phone lines or use the option \"Use for all phonelines " -"and groups\" to notify Zammad about all existing lines of your Sipgate " -"account." +#: ../system/core-workflows/condition-operators.rst:29 +msgid "Matches if a time span after a specified event has not passed." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screenshot showing a sample selection of phone numbers to use for the " -"Sipgates webhooks API" +#: ../system/core-workflows/condition-operators.rst:30 +msgid "contains" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:68 -msgid "This section also allows you to enable a Debug log." +#: ../system/core-workflows/condition-operators.rst:31 +msgid "Matches if a specified value is present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "Screenshot showing an enabled Debug log option" +#: ../system/core-workflows/condition-operators.rst:33 +msgid "Matches if all of the specified values are present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:73 -msgid "" -"After enabling you can use the Debug log section to see all sent webhook " -"calls to Zammad. You'll also can see the response." +#: ../system/core-workflows/condition-operators.rst:35 +msgid "Matches if none of the specified values are present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screenshot showing sample log entries for Sipgates webhook calls to Zammad" +#: ../system/core-workflows/condition-operators.rst:36 +msgid "contains not" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:81 -msgid "Step 4 (optional): Further configurations for Sipgate" +#: ../system/core-workflows/condition-operators.rst:37 +msgid "Matches if a specified value is not present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:80 -msgid "" -"If needed, you can now configure Zammad's Sipgate integration in more " -"detail. You can learn more about your options here: :ref:`Sipgate " -"integration settings `." +#: ../system/core-workflows/condition-operators.rst:39 +msgid "Matches if one specified value is present." msgstr "" -#: ../system/integrations/cti/sipgate.rst:2 -msgid "Sipgate (sipgate.io)" +#: ../system/core-workflows/condition-operators.rst:41 +msgid "Matches if one specified value is not present." msgstr "" -#: ../system/integrations/cti/sipgate.rst:16 -msgid "You need an administrative Sipgate account for your organization." +#: ../system/core-workflows/condition-operators.rst:42 +msgid "does not match regex" msgstr "" -#: ../system/integrations/cti/sipgate.rst:17 -msgid "" -"Zammad requires a ``sipgate.io`` addon from the feature store (please note " -"that API calls are not free with Sipgate. Rates may apply and differ from " -"account to account)." +#: ../system/core-workflows/condition-operators.rst:43 +msgid "Matches if content doesn't fit to regex rule." msgstr "" -#: ../system/integrations/cti/sipgate.rst:21 -msgid "Sipgate must be able to reach your Zammad instance." +#: ../system/core-workflows/condition-operators.rst:44 +msgid "ends with" msgstr "" -#: ../system/integrations/cti/sipgate.rst:25 -msgid ":doc:`provider-configurations/sipgate`" +#: ../system/core-workflows/condition-operators.rst:45 +msgid "Matches if content ends with specified value." msgstr "" -#: ../system/integrations/cti/sipgate.rst:24 -msgid "" -"Learn how to configure Sipgate to enable Zammad and Sipgate to communicate " -"with each other." +#: ../system/core-workflows/condition-operators.rst:46 +msgid "ends with one of" msgstr "" -#: ../system/integrations/cti/sipgate.rst:33 -msgid "" -"Below endpoint settings affect the :doc:`sipgate.io configuration `." +#: ../system/core-workflows/condition-operators.rst:47 +msgid "Matches if content ends with one of the specified values." msgstr "" -#: ../system/integrations/cti/sipgate.rst:37 -msgid "This endpoint is required for incoming call hooks." +#: ../system/core-workflows/condition-operators.rst:48 +msgid "from (relative)" msgstr "" -#: ../system/integrations/cti/sipgate.rst:40 -msgid "This endpoint is required for outgoing call hooks." +#: ../system/core-workflows/condition-operators.rst:49 +msgid "Matches if date/time is after a period of time after an event." msgstr "" -#: ../system/integrations/cti/sipgate.rst:0 -msgid "Screenshot showing sample user mappings in between Sipgate and Zammad" +#: ../system/core-workflows/condition-operators.rst:51 +msgid "Matches if content is equal to a specified value." msgstr "" -#: ../system/integrations/cti/sipgate.rst:69 -msgid "" -"You can find your agent's Sipgate username within ``Accountverwaltung → " -"Benutzer``. You're looking for the SIP-ID." +#: ../system/core-workflows/condition-operators.rst:52 +msgid "is any of" msgstr "" -#: ../system/integrations/cti/sipgate.rst:0 -msgid "Sample VoIP credentials for a Sipgate user" +#: ../system/core-workflows/condition-operators.rst:53 +msgid "Matches if content is equal to any of specified values." msgstr "" -#: ../system/integrations/cti/sipgate.rst:77 -msgid "Users with several devices also have several SIP-IDs." +#: ../system/core-workflows/condition-operators.rst:54 +msgid "is modified" msgstr "" -#: ../system/integrations/elasticsearch.rst:2 -msgid "Elasticsearch (SaaS)" +#: ../system/core-workflows/condition-operators.rst:55 +msgid "Matches if content is modified." msgstr "" -#: ../system/integrations/elasticsearch.rst:4 -msgid "" -"The Elasticsearch integration allows you to create a read-only user to use " -"with your favorite reporting tool (e.g. like Grafana)." +#: ../system/core-workflows/condition-operators.rst:57 +#: ../system/core-workflows/condition-operators.rst:61 +msgid "True from the moment of changing content until form submit." msgstr "" -#: ../system/integrations/elasticsearch.rst:7 -msgid "" -"If you want to take full advantage of the Zammad reporting, have a look at " -"our :docs:`Grafana ` " -"setup page as well." +#: ../system/core-workflows/condition-operators.rst:58 +msgid "is modified to" msgstr "" -#: ../system/integrations/elasticsearch.rst:11 -#: ../system/subscription/index.rst:7 -msgid "**🚧 Hosted environment specific 🚧**" +#: ../system/core-workflows/condition-operators.rst:59 +msgid "Matches if content is modified to a specific value." msgstr "" -#: ../system/integrations/elasticsearch.rst:13 -msgid "" -"This integration is only available for Hosted setups. In order to use " -"Elasticsearch you'll need the **Plus** subscription." +#: ../system/core-workflows/condition-operators.rst:62 +msgid "is none of" msgstr "" -#: ../system/integrations/elasticsearch.rst:16 -msgid "" -"Self hosted users have all the control over their self hosted Elasticsearch " -"instances." +#: ../system/core-workflows/condition-operators.rst:63 +msgid "Matches if content is none of any specified values." msgstr "" -#: ../system/integrations/elasticsearch.rst:None -msgid "Elasticsearch integration page on SaaS environments" +#: ../system/core-workflows/condition-operators.rst:65 +msgid "Matches if content is not equal to a specified value." msgstr "" -#: ../system/integrations/elasticsearch.rst:27 -msgid "" -"Please note the following limitations of Elasticsearch access on hosted " -"environments:" +#: ../system/core-workflows/condition-operators.rst:67 +msgid "Matches if content is present." msgstr "" -#: ../system/integrations/elasticsearch.rst:30 -msgid "access to the Elasticsearch index is read-only access" +#: ../system/core-workflows/condition-operators.rst:68 +msgid "just changed" msgstr "" -#: ../system/integrations/elasticsearch.rst:31 -msgid "currently you're limited to user only" +#: ../system/core-workflows/condition-operators.rst:69 +msgid "Matches if content has changed." msgstr "" -#: ../system/integrations/elasticsearch.rst:32 +#: ../system/core-workflows/condition-operators.rst:71 +#: ../system/core-workflows/condition-operators.rst:75 msgid "" -"Reporting tools that require to write into the indexes (like Kibana) are not " -"supported" +"Only true for the moment of changing content until next form field action/" +"click." msgstr "" -#: ../system/integrations/elasticsearch.rst:34 -msgid "IP access restriction is currently not yet supported" +#: ../system/core-workflows/condition-operators.rst:72 +msgid "just changed to" msgstr "" -#: ../system/integrations/elasticsearch.rst:37 -msgid "Activating Elasticsearch Access" +#: ../system/core-workflows/condition-operators.rst:73 +msgid "Matches if content has changed to a specified value." msgstr "" -#: ../system/integrations/elasticsearch.rst:39 -msgid "" -"By default external access to your Elasticsearch index is not active. You " -"can enable the integration at any time if needed." +#: ../system/core-workflows/condition-operators.rst:76 +msgid "matches regex" msgstr "" -#: ../system/integrations/elasticsearch.rst:42 -msgid "" -"Please ensure to note down the password provided - you won't have access to " -"it afterwards." +#: ../system/core-workflows/condition-operators.rst:77 +msgid "Matches if value fits to regex rule." msgstr "" -#: ../system/integrations/elasticsearch.rst:None -msgid "Screencast showing activation of Elasticsearch integration" +#: ../system/core-workflows/condition-operators.rst:79 +msgid "Matches if no content is present." msgstr "" -#: ../system/integrations/elasticsearch.rst:51 -msgid "Connection Settings" +#: ../system/core-workflows/condition-operators.rst:80 +msgid "starts with" msgstr "" -#: ../system/integrations/elasticsearch.rst:53 -msgid "" -"This section holds the most important general information for accessing your " -"Elasticsearch indexes - such as:" -msgstr "" - -#: ../system/integrations/elasticsearch.rst:57 -msgid "A unique subdomain that does not tell your real instance URL." +#: ../system/core-workflows/condition-operators.rst:81 +msgid "Matches if content starts with specified value." msgstr "" -#: ../system/integrations/elasticsearch.rst:61 -msgid "Software" +#: ../system/core-workflows/condition-operators.rst:82 +msgid "starts with one of" msgstr "" -#: ../system/integrations/elasticsearch.rst:60 -msgid "" -"The major version of the search index being used. This is required by some " -"Reporting tools like Grafana." +#: ../system/core-workflows/condition-operators.rst:83 +msgid "Matches if content starts with one of the specified values." msgstr "" -#: ../system/integrations/elasticsearch.rst:64 -msgid "Authentication" +#: ../system/core-workflows/condition-operators.rst:84 +msgid "till (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:64 -msgid "The authentication type being supported. ``Basic Authentication``" +#: ../system/core-workflows/condition-operators.rst:85 +msgid "Matches if date/time is before a period of time before an event." msgstr "" -#: ../system/integrations/elasticsearch.rst:67 -msgid "Available Indexes" +#: ../system/core-workflows/condition-operators.rst:86 +msgid "today" msgstr "" -#: ../system/integrations/elasticsearch.rst:69 -msgid "" -"Within this section we're displaying the -in our opinion- most important " -"indexes for a Zammad instance." +#: ../system/core-workflows/condition-operators.rst:87 +msgid "Matches if date/time is today." msgstr "" -#: ../system/integrations/elasticsearch.rst:72 -msgid "" -"If you require all indexes or our listing is not good enough for you, point " -"your browser to the URL we're providing and append ``/_aliases?" -"pretty=true``. The result should look like this: ``https://.zammad.com/" -"_aliases?pretty=true``." +#: ../system/core-workflows/condition-operators.rst:88 +msgid "within last (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:77 +#: ../system/core-workflows/condition-operators.rst:89 msgid "" -"Your browser will automatically ask for your credentials - you'll then see " -"something like this:" +"Matches if date/time content is within specified period of time before now." msgstr "" -#: ../system/integrations/elasticsearch.rst:125 -msgid "Credentials" +#: ../system/core-workflows/condition-operators.rst:91 +msgid "within next (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:127 +#: ../system/core-workflows/condition-operators.rst:92 msgid "" -"Within this section Zammad displays your available users. The password is " -"provided once (upon activation) and cannot be retrieved after that." +"Matches if date/time content is within specified period of time after now." msgstr "" -#: ../system/integrations/elasticsearch.rst:131 -msgid "" -"If you need to change or reset your Elasticsearch user password, use the " -"\"Reset password\" button in the credentials table. Doing so creates a brand " -"new password for the account in question. This change is immediate, keep in " -"mind that this may affect third party tools connected to your instance." +#: ../system/core-workflows/how-do-they-work.rst:2 +msgid "How do they work?" msgstr "" -#: ../system/integrations/exchange.rst:2 -msgid "Exchange" +#: ../system/core-workflows/how-do-they-work.rst:4 +msgid "" +"Core Workflows are executed according to their priority. If two workflows " +"have the same priority, they are executed in alphabetical order based on " +"their **name**." msgstr "" -#: ../system/integrations/exchange.rst:4 +#: ../system/core-workflows/how-do-they-work.rst:8 msgid "" -"With Zammad's Exchange integration, you can easily use existing address " -"books without having to update more than one source." +"Because of the way Core Workflows work, all changes to attributes are " +"checked with the application server - please see :doc:`limitations` for " +"possible issues." msgstr "" -#: ../system/integrations/exchange.rst:7 +#: ../system/core-workflows/how-do-they-work.rst:12 msgid "" -"However, you should refrain from syncing all addresses, as the results may " -"not be what you expect (Exchange collects huge amounts of addresses). A " -"central address book of your company to sync makes more sense, as you can " -"ensure that Zammad gets only the data you need and want. Apart from this, it " -"is even not possible to sync the Global Address List (GAL) of your Exchange " -"system with Zammad." +"Below we're talking about settings that are important and not self-" +"explanatory." msgstr "" -#: ../system/integrations/exchange.rst:16 +#: ../system/core-workflows/how-do-they-work.rst:17 msgid "" -"**Exchange and LDAP:** The exchange sync can be overruled by Zammad's LDAP " -"integration. If you have the same users in both sources, the LDAP version " -"will always be Zammad's pick." +"Choose the object context you want to run the workflow in. This will decide " +"on your available attributes and actions." msgstr "" -#: ../system/integrations/exchange.rst:19 -msgid "" -"**One way sync:** the Exchange sync is one way. Exchange => Zammad. Changes " -"to your users inside of Zammad might be overwritten by the Exchange sync." +#: ../system/core-workflows/how-do-they-work.rst:20 +msgid "Ticket objects also have access to the ticket customer." msgstr "" -#: ../system/integrations/exchange.rst:24 +#: ../system/core-workflows/how-do-they-work.rst:25 msgid "" -"To configure Exchange integration, simply go to the System > Integrations > " -"Exchange in the admin panel. Press \"change\" and follow the wizard for " -"adding the needed Exchange information to Zammad. On the last two steps " -"Zammad will ask you for the address book(s) and your desired attribute " -"mapping. By default, Zammad only maps email address, first- and lastname. " -"Technically, you can map any Exchange object to a Zammad user object (this " -"also works for custom objects!)." +"Choose in which situation the workflow is applied. Contexts can be combined " +"to avoid duplicate workflows." msgstr "" -#: ../system/integrations/exchange.rst:35 -msgid "" -"If the SSL verification fails while connecting to Exchange, Zammad will ask " -"you to turn it off temporarily." +#: ../system/core-workflows/how-do-they-work.rst:30 +msgid "Creation mask" msgstr "" -#: ../system/integrations/exchange.rst:38 +#: ../system/core-workflows/how-do-they-work.rst:29 msgid "" -"Please be aware that **turning off SSL verification is a security risk**. It " -"should only be used temporarily or for testing purposes. If turned off, " -"there is no verification of the certificate, which means that every " -"presented certificate will be accepted." +"If selected, your conditions and actions will affect all applicable creation " +"masks." msgstr "" -#: ../system/integrations/exchange.rst:43 -msgid "" -"After pressing Continue, Zammad will check if the configuration is okay. You " -"can then enable Exchange and start your first sync. The sync will then run " -"hourly - if you need to change mappings or the address book(s), you can " -"change the configuration at any time." +#: ../system/core-workflows/how-do-they-work.rst:34 +msgid "Edit mask" msgstr "" -#: ../system/integrations/exchange.rst:50 +#: ../system/core-workflows/how-do-they-work.rst:33 msgid "" -"After the sync has finished, you can find the new Exchange contacts under " -"\"Users\". Zammad integrates them just as normal users." +"If selected, your conditions and actions will affect all applicable edit " +"masks." msgstr "" -#: ../system/integrations/exchange.rst:55 +#: ../system/core-workflows/how-do-they-work.rst:39 msgid "" -"In some cases you might see unique IDs as \"Login\" instead of the email " -"address. This is normal and doesn't affect the login or email mapping for " -"that entry." +"Zammad differentiates between selected and saved conditions. These can be " +"combined wherever needed." msgstr "" -#: ../system/integrations/github.rst:4 -msgid "" -"Use GitHub integration to track GitHub issues directly within Zammad " -"tickets. Add issue hyperlinks and get a live summary of metadata like status " -"(open/closed), assignee, labels, and more." +#: ../system/core-workflows/how-do-they-work.rst:42 +msgid "**⚠️ Restrict workflows to specific roles if needed!**" msgstr "" -#: ../system/integrations/github.rst:8 -msgid "Please note that our GitHub integration does not support pull requests." +#: ../system/core-workflows/how-do-they-work.rst:44 +msgid "" +"By default and unless configured in conditions, workflow rules are executed " +"for **all roles**. This also affects your customers!" msgstr "" -#: ../system/integrations/github.rst:None -msgid "Integration page for GitHub" +#: ../system/core-workflows/how-do-they-work.rst:50 +msgid "Selected Conditions" msgstr "" -#: ../system/integrations/github.rst:18 +#: ../system/core-workflows/how-do-they-work.rst:48 msgid "" -"In your GitHub settings, create a new API token under **Developer settings > " -"Personal access tokens > Generate new token**. Leave the **Scopes** section " -"empty." +"These conditions are based on form values and match if an appropriate " +"selection is made (e.g. choosing another group in the ticket without " +"saving). This applies for drafts (active selection) and currently saved " +"values." msgstr "" -#: ../system/integrations/github.rst:0 ../system/integrations/gitlab.rst:0 -msgid "Screencast showing how to create a new API token" +#: ../system/core-workflows/how-do-they-work.rst:64 +msgid "Saved Conditions" msgstr "" -#: ../system/integrations/github.rst:27 -msgid "Create a new API key with no scopes/privileges." +#: ../system/core-workflows/how-do-they-work.rst:53 +msgid "" +"These conditions only match if the selected values are stored in the " +"database. It ignores the current value or selection of the field, as long as " +"the changes are not saved (e.g. performing field operations for an existing " +"ticket, which is viewed/opened by an agent)." msgstr "" -#: ../system/integrations/github.rst:29 -msgid "🔒 **Will this work for private repos?**" +#: ../system/core-workflows/how-do-they-work.rst:60 +msgid "" +"Keep in mind that the value has to be available in the situation where you " +"need it. Otherwise the condition won't match." msgstr "" -#: ../system/integrations/github.rst:31 +#: ../system/core-workflows/how-do-they-work.rst:63 msgid "" -"No. To link private repo issues, **use the** ``repo`` **scope instead**. " -"Bear in mind that the resulting token will have `lots of permissions that it " -"doesn't actually need `_, which presents a security risk if your token ever falls into " -"the wrong hands." +"Example: you can't perform any actions with *saved condition* on a ticket in " +"creation, because there are no saved values at that time." msgstr "" -#: ../system/integrations/github.rst:37 +#: ../system/core-workflows/how-do-they-work.rst:66 msgid "" -"Unfortunately, because of how GitHub's OAuth token scopes are set up, this " -"is the only way to link issues on private repos." +"You can find a description of the condition operators for core workflows :" +"doc:`here `." msgstr "" -#: ../system/integrations/github.rst:40 -msgid "Enter your new API token in Zammad and enable GitHub integration." +#: ../system/core-workflows/how-do-they-work.rst:72 +msgid "" +"Which actions should we run on the relevant fields? The possible actions " +"depend on the object type. However, usually you can at least change the " +"visibility and whether the field is mandatory." msgstr "" -#: ../system/integrations/github.rst:0 -msgid "Screencast showing how to configure Zammad's GitHub integration" +#: ../system/core-workflows/how-do-they-work.rst:76 +msgid "Be aware that actions are not available for **related** context." msgstr "" -#: ../system/integrations/github.rst:47 +#: ../system/core-workflows/how-do-they-work.rst:78 msgid "" -"Use the default API endpoint (``https://api.github.com/graphql``) unless " -"you're using GitHub Enterprise Server." +"**Example:** Let's assume you are working in the ticket context. While you " +"can have customer *conditions*, you *can't adjust* objects with actions in " +"that scope. That's because this wouldn't have any impact on the ticket " +"dialog. Of course all ticket attributes (state, owner, ...) are available." msgstr "" -#: ../system/integrations/github.rst:50 +#: ../system/core-workflows/how-do-they-work.rst:84 msgid "" -"Once completed, a new GitHub issues tab will appear in the ticket pane. 🎉" +"Please also have a look at our :doc:`limitations` to be safe from surprises." msgstr "" -#: ../system/integrations/github.rst:59 ../system/integrations/gitlab.rst:52 -msgid "Token verification is taking a long time" +#: ../system/core-workflows/how-do-they-work.rst:88 +msgid "Available Operators" msgstr "" -#: ../system/integrations/github.rst:56 ../system/integrations/gitlab.rst:49 -msgid "" -"Slight delays are normal (<2 min.), especially for systems under heavy load." +#: ../system/core-workflows/how-do-they-work.rst:90 +msgid "The availability of operators depends on the object type and scope." msgstr "" -#: ../system/integrations/github.rst:58 +#: ../system/core-workflows/how-do-they-work.rst:94 msgid "" -"Self-hosted administrators, please check your network settings to ensure " -"that your Zammad server can reach ``api.github.com``." +"Please note that actions may or may not restrict API based access to " +"attributes. We're displaying the following icons for your overview to " +"understand these limits better:" msgstr "" -#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 -msgid "I reloaded the page and now the API token is gone" +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|api| This icon indicates the action affects the API." msgstr "" -#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 -msgid "" -"This may indicate that Zammad is still verifying your API token. Try " -"reloading the page again in a couple minutes." +#: ../system/core-workflows/how-do-they-work.rst:163 +msgid "api" msgstr "" -#: ../system/integrations/gitlab.rst:2 -msgid "GitLab" +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|ui| This icon indicates the action only affects the web interface." msgstr "" -#: ../system/integrations/gitlab.rst:4 -msgid "" -"Use GitLab integration to track GitLab issues directly within Zammad " -"tickets. Add issue hyperlinks and get a live summary of metadata like status " -"(open/closed), assignee, labels, and more." +#: ../system/core-workflows/how-do-they-work.rst:167 +msgid "ui" msgstr "" -#: ../system/integrations/gitlab.rst:8 -msgid "" -"Please note that our GitLab integration does not support merge requests." +#: ../system/core-workflows/how-do-they-work.rst:102 +msgid "show |ui|" msgstr "" -#: ../system/integrations/gitlab.rst:None -msgid "Integration page for GitLab" +#: ../system/core-workflows/how-do-they-work.rst:102 +msgid "Display the chosen field. Allows setting of values." msgstr "" -#: ../system/integrations/gitlab.rst:18 -msgid "" -"In your GitLab preferences, create a new API token under **Access Tokens**." +#: ../system/core-workflows/how-do-they-work.rst:109 +msgid "hide |ui|" msgstr "" -#: ../system/integrations/gitlab.rst:20 -msgid "Under **Select scopes**, choose ``read_api`` only." +#: ../system/core-workflows/how-do-they-work.rst:105 +msgid "" +"Hide the chosen field. However, it technically still allows setting the " +"field." msgstr "" -#: ../system/integrations/gitlab.rst:27 -msgid "🔒 **If you wish to link issues on any private repos...**" +#: ../system/core-workflows/how-do-they-work.rst:108 +msgid "" +"Please note that the field is **not** gone and still contains an existing " +"value (if set)! Consider *remove* instead, if you want this field to be gone." msgstr "" -#: ../system/integrations/gitlab.rst:29 -msgid "Your API token must belong to an account with access to those repos." +#: ../system/core-workflows/how-do-they-work.rst:112 +msgid "remove |ui|" msgstr "" -#: ../system/integrations/gitlab.rst:31 -msgid "Enter your new API token in Zammad and enable GitLab integration." +#: ../system/core-workflows/how-do-they-work.rst:112 +msgid "Entirely removes the field. The field value will not be evaluated." msgstr "" -#: ../system/integrations/gitlab.rst:0 -msgid "Screencast showing how to configure Zammad's GitLab integration" +#: ../system/core-workflows/how-do-they-work.rst:115 +msgid "set mandatory |ui| |api|" msgstr "" -#: ../system/integrations/gitlab.rst:40 -msgid "" -"Use the default API endpoint (``https://gitlab.com/api/graphql``) unless " -"you're a self-hosted GitLab user." +#: ../system/core-workflows/how-do-they-work.rst:115 +msgid "Sets the field to mandatory." msgstr "" -#: ../system/integrations/gitlab.rst:43 -msgid "" -"Once completed, a new GitLab issues tab will appear in the ticket pane. 🎉" +#: ../system/core-workflows/how-do-they-work.rst:118 +msgid "set optional |ui| |api|" msgstr "" -#: ../system/integrations/gitlab.rst:51 -msgid "" -"Self-hosted administrators, please check your network settings to ensure " -"that your Zammad server can reach ``gitlab.com``." +#: ../system/core-workflows/how-do-they-work.rst:118 +msgid "Sets the field to optional." msgstr "" -#: ../system/integrations/i-doit.rst:2 -msgid "i-doit" +#: ../system/core-workflows/how-do-they-work.rst:124 +msgid "add option |ui| |api|" msgstr "" -#: ../system/integrations/i-doit.rst:4 -msgid "" -"`i-doit `_ is an open-source **configuration " -"management database** - in other words, a tool for keeping tabs on every " -"single piece of your physical and digital infrastructure, from network " -"equipment to virtual machines on down to the faceplates on your rack shelves " -"and more." +#: ../system/core-workflows/how-do-they-work.rst:121 +msgid "Allows adding options to tree selects or selects." msgstr "" -#: ../system/integrations/i-doit.rst:10 +#: ../system/core-workflows/how-do-they-work.rst:123 msgid "" -"What's that got to do with Zammad? Well, if you used tickets to track issues " -"with all that hardware, you might start wishing there was a way they could " -"talk to each other." -msgstr "" - -#: ../system/integrations/i-doit.rst:14 -msgid "Zammad gives you two:" +"You have to use the \"remove option\" before performing this action. It " +"allows you to use *existing* configured values." msgstr "" -#: ../system/integrations/i-doit.rst:17 -msgid "1. Add i-doit Links to Zammad Tickets" +#: ../system/core-workflows/how-do-they-work.rst:128 +msgid "remove option |ui| |api|" msgstr "" -#: ../system/integrations/i-doit.rst:20 ../system/integrations/i-doit.rst:80 -msgid "What Users See" +#: ../system/core-workflows/how-do-they-work.rst:127 +msgid "" +"Allows removing options from tree selects or selects. It allows you to use " +"*existing* configured values." msgstr "" -#: ../system/integrations/i-doit.rst:26 -msgid "i-doit integration in Zammad's ticket pane" +#: ../system/core-workflows/how-do-they-work.rst:134 +msgid "set fixed to |ui| |api|" msgstr "" -#: ../system/integrations/i-doit.rst:26 -msgid "" -"The i-doit integration will appear under a new 🖨 tab in the ticket pane." +#: ../system/core-workflows/how-do-they-work.rst:131 +msgid "Reduces the available options by your selection." msgstr "" -#: ../system/integrations/i-doit.rst:28 +#: ../system/core-workflows/how-do-they-work.rst:133 msgid "" -"i-doit integration puts a new tab in Zammad's ticket pane where you can add " -"links to existing i-doit devices for easy reference. (See our :user-docs:" -"`user documentation ` to learn " -"how it works in practice)." +"This reduces your workflows in terms of *add option* and *remove option*." msgstr "" -#: ../system/integrations/i-doit.rst:36 ../system/integrations/i-doit.rst:93 -msgid "How to Set it Up" +#: ../system/core-workflows/how-do-they-work.rst:137 +msgid "fill in |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:38 -msgid "" -"It requires i-doit's `API Add-on `_. Make sure to have it properly set up. Use the following setting:" +#: ../system/core-workflows/how-do-they-work.rst:137 +msgid "Allows filling in of string and integer fields with your values." msgstr "" -#: ../system/integrations/i-doit.rst:42 -msgid "Active: ``Yes``" +#: ../system/core-workflows/how-do-they-work.rst:141 +msgid "fill in empty |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:43 -msgid "Enforce authentication by username and password: ``No``" +#: ../system/core-workflows/how-do-they-work.rst:140 +msgid "" +"Allows filling in of string and integer fields with your values **if the " +"field is empty**." msgstr "" -#: ../system/integrations/i-doit.rst:45 -msgid "" -"To set it up, enable the integration in the Zammad admin panel under " -"**System > Integrations > i-doit**:" +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "select |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "i-doit settings within the integration pages" +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "Select a specific value within a select, tree select or boolean field." msgstr "" -#: ../system/integrations/i-doit.rst:53 -msgid "The root URL of your i-doit installation." +#: ../system/core-workflows/how-do-they-work.rst:153 +msgid "auto select |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:62 -msgid "API token" +#: ../system/core-workflows/how-do-they-work.rst:147 +msgid "Helps users with tree select and select fields:" msgstr "" -#: ../system/integrations/i-doit.rst:56 +#: ../system/core-workflows/how-do-they-work.rst:149 msgid "" -"Found in the i-doit admin panel under **Interfaces / external data > JSON-" -"RPC API > Common Settings**." +"If the field has only one option available for selection and no value yet, " +"the value will be automatically set." msgstr "" -#: ../system/integrations/i-doit.rst:0 -msgid "i-doit administration interface with API configuration" +#: ../system/core-workflows/how-do-they-work.rst:152 +msgid "" +"This option only works if you have one value and doesn't work if there is " +"more than one option available." msgstr "" -#: ../system/integrations/i-doit.rst:67 -msgid "Client ID" +#: ../system/core-workflows/how-do-they-work.rst:157 +msgid "set readonly |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:65 -msgid "A unique name to identify Zammad within i-doit." +#: ../system/core-workflows/how-do-they-work.rst:156 +msgid "" +"Allows you to display an attribute as read only (which means no changes are " +"possible)." msgstr "" -#: ../system/integrations/i-doit.rst:67 -msgid "(Zammad does not require you to enter a value here, but i-doit might!)" +#: ../system/core-workflows/how-do-they-work.rst:161 +msgid "unset readonly |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:70 +#: ../system/core-workflows/how-do-they-work.rst:160 msgid "" -"Here you can decide if the certificate of your i-doit system has to be " -"verified or not. In case you are using custom certificates, please have a " -"look at :doc:`how to add them to Zammad `." -msgstr "" - -#: ../system/integrations/i-doit.rst:77 -msgid "2. List / Create Zammad Tickets in i-doit" +"In case a workflow set the field in question to read only, you can undo this " +"with option above." msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "Zammad integration in i-doit's device view" +#: ../system/core-workflows/how-do-they-work.rst:172 +msgid "Stop after match" msgstr "" -#: ../system/integrations/i-doit.rst:86 +#: ../system/core-workflows/how-do-they-work.rst:174 msgid "" -"i-doit's ticket system integration gives you a way to see all the tickets " -"for a given device without ever leaving i-doit. (See our :user-docs:`user " -"documentation ` to learn how it " -"works in practice)." +"Here you can decide if other workflows are executed after the current one." msgstr "" -#: ../system/integrations/i-doit.rst:95 +#: ../system/core-workflows/how-do-they-work.rst:176 msgid "" -"Enable this integration in the i-doit admin panel under **Interfaces / " -"external data > Trouble Ticket System (TTS) > Configuration**:" +"If set to ``no`` (default), further workflows will be executed if they match " +"the condition. In this case, it is possible that your actions from the " +"current workflow can be overwritten by another workflow." msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "i-doit administration interface with TTS configuration" +#: ../system/core-workflows/how-do-they-work.rst:180 +msgid "" +"If set to ``yes``, no further worflows will be executed after the current " +"one." msgstr "" -#: ../system/integrations/i-doit.rst:104 -msgid "TTS-Type" +#: ../system/core-workflows/how-do-they-work.rst:184 +msgid "Priority" msgstr "" -#: ../system/integrations/i-doit.rst:104 -msgid "``Zammad``" +#: ../system/core-workflows/how-do-they-work.rst:186 +msgid "" +"You can define the sequence, in which the workflows are executed. The " +"default value is ``500``." msgstr "" -#: ../system/integrations/i-doit.rst:115 -msgid "Username / Password" +#: ../system/core-workflows/how-do-they-work.rst:189 +msgid "" +"The workflows are executed in ascending order by their priority. That means " +"lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." msgstr "" -#: ../system/integrations/i-doit.rst:107 -msgid "Login credentials for a Zammad agent." +#: ../system/core-workflows/learn-by-example.rst:2 +msgid "Learn by Example" msgstr "" -#: ../system/integrations/i-doit.rst:109 +#: ../system/core-workflows/learn-by-example.rst:4 msgid "" -"This agent must have **read permission** for all :doc:`groups ` that plan on using the i-doit integration." +"This page provides some basic examples for Core Workflows. Of course you can " +"build much more complex workflows if needed." msgstr "" -#: ../system/integrations/i-doit.rst:113 +#: ../system/core-workflows/learn-by-example.rst:7 msgid "" -"You may even wish to create a dedicated agent account just for this " -"integration (otherwise, if the agent ever changes her password, you will " -"have to remember to update it here)." +"To learn about Core Workflows in detail, first go to :doc:`how-do-they-work`." msgstr "" -#: ../system/integrations/i-doit.rst:117 -msgid "URL incl. protocol" +#: ../system/core-workflows/learn-by-example.rst:10 +msgid "Group Based Examples" msgstr "" -#: ../system/integrations/i-doit.rst:118 -msgid "``https://your.zammad.domain``" +#: ../system/core-workflows/learn-by-example.rst:12 +msgid "" +"All following workflows have the same base configurations. The workflow may " +"not use them all." msgstr "" -#: ../system/integrations/index.rst:2 -msgid "Integrations" +#: ../system/core-workflows/learn-by-example.rst:15 +msgid "Groups:" msgstr "" -#: ../system/integrations/index.rst:4 +#: ../system/core-workflows/learn-by-example.rst:20 +msgid "Attributes:" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:22 +msgid "Category (Single tree selection field, not mandatory, agents only)" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:23 msgid "" -"Zammad offers numerous integrations that add rich features to your instance." +"Approved (Boolean field, not mandatory, not shown, ``false`` as default)" msgstr "" -#: ../system/integrations/index.rst:6 -msgid "We're still working on this part of our documentation, stay tight!" +#: ../system/core-workflows/learn-by-example.rst:24 +msgid "Operating System (Text field, not mandatory, not shown)" msgstr "" -#: ../system/integrations/index.rst:10 -msgid "Integrations for Phone Systems" +#: ../system/core-workflows/learn-by-example.rst:25 +msgid "Software used (Single selection field, not mandatory, not shown)" msgstr "" -#: ../system/integrations/index.rst:14 -msgid "" -"Your VoIP provider or telephony system is not listed? Possibly your provider " -"supports Zammad by using the generic CTI - if you're unsure ask your " -"provider." +#: ../system/core-workflows/learn-by-example.rst:68 +msgid "Group specific values and fields" msgstr "" -#: ../system/integrations/index.rst:18 +#: ../system/core-workflows/learn-by-example.rst:28 msgid "" -"Provider does not support Zammad? Consider creating a `feature request in " -"the Zammad Community `_." +"This workflow set depends on the category field. It reduces the available " +"set of values based on the group selected." msgstr "" -#: ../system/integrations/index.rst:31 -msgid "Integrations for Authentication and Customers" +#: ../system/core-workflows/learn-by-example.rst:33 +msgid "Workflow 2nd Level group" msgstr "" -#: ../system/integrations/index.rst:44 -msgid "Integrations for Monitoring Systems" +#: ../system/core-workflows/learn-by-example.rst:35 +msgid "" +"This reduces the category options to ``2nd Level/*``, ``Internal/*`` and " +"``Others``. It also sets further required fields to mandatory and visible." msgstr "" -#: ../system/integrations/index.rst:46 -msgid "This section currently misses the following integrations:" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for 2nd level" msgstr "" -#: ../system/integrations/index.rst:48 -msgid "Icinga" +#: ../system/core-workflows/learn-by-example.rst:43 +msgid "Workflow Support group" msgstr "" -#: ../system/integrations/index.rst:49 -msgid "Monit" +#: ../system/core-workflows/learn-by-example.rst:45 +msgid "" +"This reduces the category options to ``Support/*``, ``Internal/*`` and " +"``Others``. It also sets further required fields to visible." msgstr "" -#: ../system/integrations/index.rst:50 -msgid "Nagios" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for support" msgstr "" -#: ../system/integrations/index.rst:60 -msgid "Integrations for Issue Trackers" +#: ../system/core-workflows/learn-by-example.rst:53 +msgid "Workflow Sales group" msgstr "" -#: ../system/integrations/index.rst:70 -msgid "Other Integrations" +#: ../system/core-workflows/learn-by-example.rst:55 +msgid "" +"This reduces the category options to ``Sales/*``, ``Internal/*`` and " +"``Others``." msgstr "" -#: ../system/integrations/index.rst:72 -msgid "" -"This section will hold any other integration that can't be grouped up (yet)." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for sales" msgstr "" -#: ../system/integrations/ldap/index.rst:2 -msgid "LDAP / Active Directory" +#: ../system/core-workflows/learn-by-example.rst:68 +#: ../system/integrations/slack.rst:88 +msgid "The Result" msgstr "" -#: ../system/integrations/ldap/index.rst:4 +#: ../system/core-workflows/learn-by-example.rst:63 msgid "" -"Zammad comes with a powerful LDAP integration that allows you to have a " -"single source of truth. By this you reduce the number of login credentials " -"your user has to remember." +"This is what the agent would experience with the above workflows in place." msgstr "" -#: ../system/integrations/ldap/index.rst:10 +#: ../system/core-workflows/learn-by-example.rst:0 msgid "" -"The LDAP source is also a perfect candidate for Zammad's :docs:`Kerberos " -"Single Sign-On ` but also works as addition " -"to other :doc:`/settings/security/third-party`." +"Workflow shows objects and limits options based on selections on the group" msgstr "" -#: ../system/integrations/ldap/index.rst:None -msgid "Zammands LDAP management page" +#: ../system/core-workflows/learn-by-example.rst:90 +msgid "Approval process" msgstr "" -#: ../system/integrations/ldap/index.rst:25 -msgid "📝 :doc:`manage`" +#: ../system/core-workflows/learn-by-example.rst:71 +msgid "" +"In this case ``approved`` is visible to agents by default. For this " +"workflow, an additional role ``Approval person`` is required (no further " +"permissions)." msgstr "" -#: ../system/integrations/ldap/index.rst:25 -msgid "Add, modify, remove or re-arrange your LDAP-Sources as needed." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that restricts an approval attribute to specific roles" msgstr "" -#: ../system/integrations/ldap/index.rst:30 -msgid "Before you continue, please note the following limitations." +#: ../system/core-workflows/learn-by-example.rst:81 +msgid "" +"This workflow may work best in combination with a :doc:`trigger ` but technically, this is not required." msgstr "" -#: ../system/integrations/ldap/index.rst:32 -msgid "Mapping / Synchronizing organizations is not possible" +#: ../system/core-workflows/learn-by-example.rst:84 +msgid "" +"Select fields may be a better approach because they allow more values than " +"just a simple ``true`` or ``false``." msgstr "" -#: ../system/integrations/ldap/index.rst:36 +#: ../system/core-workflows/learn-by-example.rst:0 msgid "" -"You may want to consider using domain based assignments to overcome this " -"issue. Learn more on :doc:`/manage/organizations/index`." +"Workflow fixes possible values of \"Approved ?\" to a specific selection " +"depending on the users role" msgstr "" -#: ../system/integrations/ldap/index.rst:39 +#: ../system/core-workflows/learn-by-example.rst:103 +msgid "State dependent mandatory fields" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:93 msgid "" -"Zammad's LDAP sync is one way. Editing user settings or permissions may be " -"overwritten upon the next sync depending on your configuration." +"This workflow sets ``Category`` to mandatory if the agent wants to set the " +"states ``closed`` or ``pending close`` to enforce categorization." msgstr "" -#: ../system/integrations/ldap/index.rst:41 -msgid "Nested groups are not supported." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that sets fields to mandatory on specific states" msgstr "" -#: ../system/integrations/ldap/index.rst:42 -msgid "Synchronizing user avatars from LDAP is not supported." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "" +"Workflow sets category field to mandatory upon choosing closed or pending " +"close as state" msgstr "" -#: ../system/integrations/ldap/index.rst:43 -msgid "Unlike user filters, group filters cannot be changed." +#: ../system/core-workflows/learn-by-example.rst:106 +msgid "Manual Ticket Handover Process" msgstr "" -#: ../system/integrations/ldap/index.rst:44 -msgid "" -"When a user originates from an LDAP server, Zammad will try to verify the " -"login credentials against LDAP first - if this fails Zammad will check its " -"local database." +#: ../system/core-workflows/learn-by-example.rst:108 +msgid "This example covers the handover of a ticket from one agent to another:" msgstr "" -#: ../system/integrations/ldap/index.rst:50 +#: ../system/core-workflows/learn-by-example.rst:110 msgid "" -"Users can have local passwords even if they're LDAP users! You can learn " -"more about user accounts in general on :doc:`/manage/users/index`." +"When the ticket owner is modified, a new text field (\"Handover\") shows up " +"for a comment" msgstr "" -#: ../system/integrations/ldap/index.rst:54 +#: ../system/core-workflows/learn-by-example.rst:112 msgid "" -"When several LDAP sources contain the same user (meaning the same email " -"address), the user in question will be updated with every source configured. " -"*The last LDAP source will win.*" +"This may only be visible when the owner is changed, therefore it has to be " +"hidden in general" msgstr "" -#: ../system/integrations/ldap/index.rst:58 -msgid "" -"This is subject to change with `Issue 4109 `_ in the future." +#: ../system/core-workflows/learn-by-example.rst:114 +msgid "The input in this handover text field is mandatory" msgstr "" -#: ../system/integrations/ldap/index.rst:60 +#: ../system/core-workflows/learn-by-example.rst:115 msgid "" -"Synchronization statistics currently affect *all* configured LDAP sources. " -"This also applies for newly added or updated sources." +"After submitting changes, the value of the handover field must be added as " +"an note to the ticket (via trigger)" msgstr "" -#: ../system/integrations/ldap/index.rst:63 -msgid "" -"This is subject to change with `Issue 4108 `_ in the future." +#: ../system/core-workflows/learn-by-example.rst:121 +msgid "Hiding handover field" msgstr "" -#: ../system/integrations/ldap/index.rst:65 -msgid "" -"Zammad currently has limited fallback server support. You can workaround " -"this by providing several sources - however, ensure to have the exact same " -"configuration on your fallback." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Hiding the handover field in core workflows" msgstr "" -#: ../system/integrations/ldap/index.rst:69 -msgid "" -"This is subject to improve with `Issue 4107 `_ in the future." +#: ../system/core-workflows/learn-by-example.rst:126 +msgid "Showing handover field and setting it to mandatory" msgstr "" -#: ../system/integrations/ldap/index.rst:76 -msgid "" -"This section holds all requests Zammad handled for all LDAP sources. These " -"entries can either contain synchronization information or logins " -"(authentication attempts via Zammad's login interface)." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Showing the handover field and set it as mandatory" msgstr "" -#: ../system/integrations/ldap/index.rst:80 -msgid "" -"By clicking on any request, Zammad will provide even more information. The " -"provided information can be useful when something does not work as expected." +#: ../system/core-workflows/learn-by-example.rst:131 +msgid "Trigger writing handover input to a new article" msgstr "" -#: ../system/integrations/ldap/index.rst:85 -msgid "" -"Especially a LDAP synchronization can cause many log entries. The web " -"interface will always limit the number of shown entries to the last 50 " -"entries." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Write handover content to a new article" msgstr "" -#: ../system/integrations/ldap/index.rst:None +#: ../system/core-workflows/learn-by-example.rst:133 msgid "" -"Screencast showing LDAP integration log entries and a detail view on\n" -"an entry." +"As a result, the ticket includes an article of the type note which includes " +"the predefined text and the handover comment." msgstr "" -#: ../system/integrations/ldap/manage.rst:2 -msgid "Manage LDAP-Sources" +#: ../system/core-workflows/limitations.rst:6 +msgid "Core Workflows do not replace Triggers" msgstr "" -#: ../system/integrations/ldap/manage.rst:6 +#: ../system/core-workflows/limitations.rst:5 msgid "" -"Please keep in mind all current limitations for the LDAP synchronization. " -"This will help to understand scopes of the following operations better." +"Workflows manipulate the behavior of fields. However, they do not set values " +"in fields because of actions." msgstr "" -#: ../system/integrations/ldap/manage.rst:65 -msgid "Add new source" +#: ../system/core-workflows/limitations.rst:16 +msgid "API calls are only partly affected" msgstr "" -#: ../system/integrations/ldap/manage.rst:10 +#: ../system/core-workflows/limitations.rst:9 msgid "" -"Using the *New Source* button allows you to add new LDAP sources to your " -"installation. You're not limited in the number of sources, however, keep in " -"mind that many sources will also take more time to synchronize." +"Some options affect UI only and thus do not restrict responses and calls." msgstr "" -#: ../system/integrations/ldap/manage.rst:14 -msgid "" -"You can choose between different encryption types, namely *SSL* and " -"*STARTTLS* or none of them (\"*No SSL*\"). If you choose *SSL* or " -"*STARTTLS*, Zammad will display an additional *SSL verification* option that " -"allows you to disable the verification, e.g. for self-signed SSL " -"certificates. You can also tell Zammad to use a different port by appending " -"``:`` to your hostname/IP." +#: ../system/core-workflows/limitations.rst:11 +msgid "This affects the following actions:" msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "" -"Screenshot of configuring a new LDAP source with SSL encryption and SSL " -"verification" +#: ../system/core-workflows/limitations.rst:13 +msgid "select" msgstr "" -#: ../system/integrations/ldap/manage.rst:26 -msgid "" -"New Source with SSL transport security enabled and certificate verification" +#: ../system/core-workflows/limitations.rst:14 +msgid "auto select" msgstr "" -#: ../system/integrations/ldap/manage.rst:30 -msgid "" -"Using an user filter can be a good idea if you only require a small subset " -"of your LDAP users in Zammad." +#: ../system/core-workflows/limitations.rst:15 +msgid "show" msgstr "" -#: ../system/integrations/ldap/manage.rst:42 -msgid "This especially affects inactive users" +#: ../system/core-workflows/limitations.rst:16 +msgid "hide" msgstr "" -#: ../system/integrations/ldap/manage.rst:34 -msgid "" -"As every LDAP behaves differently on which attributes and how they are set, " -"Zammad doesn't care about any flags." +#: ../system/core-workflows/limitations.rst:25 +msgid "Some fields stay unavailable to customers" msgstr "" -#: ../system/integrations/ldap/manage.rst:37 +#: ../system/core-workflows/limitations.rst:19 msgid "" -"Users that no longer are returned by your LDAP source will automatically be " -"set to inactive. Zammad assumes that the user was deactivated." +"For technical and security reasons, some default fields (the pale ones you " +"can't edit) stay unavailable for display and usage on customer permissions." msgstr "" -#: ../system/integrations/ldap/manage.rst:41 +#: ../system/core-workflows/limitations.rst:23 msgid "" -"Users will never be removed automatically! If you want to remove obsolete " -"users, use :doc:`/system/data-privacy`." +"If you require your customers to change e.g. priorities, please consider " +"using workarounds via :doc:`/system/objects` and :doc:`/manage/trigger`." msgstr "" -#: ../system/integrations/ldap/manage.rst:46 -msgid "Active Directory admins" +#: ../system/core-workflows/limitations.rst:29 +msgid "Ticket title changes not supported in edit mask" msgstr "" -#: ../system/integrations/ldap/manage.rst:45 +#: ../system/core-workflows/limitations.rst:28 msgid "" -"Active Directories are quite specific on how to filter for active users only " -"- please see the `Microsoft documentation `_ for more " -"information." +"It is currently not possible to perform changes of the ticket title in the " +"edit mask (e.g. renaming, set to read-only)." msgstr "" -#: ../system/integrations/ldap/manage.rst:51 -msgid "" -"*Do not* manually write pathes of either LDAP attributes or groups. If " -"Zammad does not display them, it either cannot find them or you have a lot " -"of users that don't have the attributes populated." +#: ../system/core-workflows/limitations.rst:37 +msgid "What is out of scope of Core Workflows?" msgstr "" -#: ../system/integrations/ldap/manage.rst:55 +#: ../system/core-workflows/limitations.rst:32 msgid "" -"Zammad will always only return attributes that are filled - this reduces the " -"returned list of attributes greatly." +"There are some things that would count as workflow but are either done via :" +"doc:`/manage/trigger` or :doc:`/manage/scheduler`." msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing how to add a new LDAP source" +#: ../system/core-workflows/limitations.rst:35 +msgid "Such as (but not limited to):" msgstr "" -#: ../system/integrations/ldap/manage.rst:63 -msgid "" -"If your LDAP system doesn't allow anonymous bind, Zammad detects it and " -"provides you an editable \"Base DN\" *text* field instead of a prefilled " -"*select* field." +#: ../system/core-workflows/limitations.rst:37 +msgid "up- or downgrade permissions of users" msgstr "" -#: ../system/integrations/ldap/manage.rst:81 -msgid "Review or edit existing source" +#: ../system/core-workflows/limitations.rst:38 +msgid "affecting article creation or listing" msgstr "" -#: ../system/integrations/ldap/manage.rst:68 +#: ../system/data-privacy.rst:2 +msgid "Data Privacy" +msgstr "" + +#: ../system/data-privacy.rst:4 msgid "" -"Clicking on a LDAP source will provide a configuration and mapping overview." +"For compliance with GDPR and other data privacy laws, you may wish to " +"**permanently delete users from the system**, along with **all of their " +"associated tickets**." msgstr "" -#: ../system/integrations/ldap/manage.rst:70 +#: ../system/data-privacy.rst:8 msgid "" -"If needed you can then use the *Change* button to update either the name, " -"active state or the whole configuration. If you're changing the whole " -"configuration, the dialogue will be identical to the source creation." +"You can create manual deletion tasks or even automated deletion tasks for " +"tickets and users based on custom conditions via :doc:`scheduler `!" msgstr "" -#: ../system/integrations/ldap/manage.rst:76 +#: ../system/data-privacy.rst:12 msgid "" -"Did your LDAP server change? Different LDAP servers have different " -"structures and default attributes. This causes the LDAP synchronization to " -"likely fail. Consider removing the affected source and re-add it." +"Access to this panel requires ``admin.data_privacy`` permissions (introduced " +"in Zammad 3.5)." msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing the update of the source name." +#: ../system/data-privacy.rst:15 +msgid "" +"On older systems that have not been updated yet, customers can also be :docs:" +"`deleted via the Zammad console `." msgstr "" -#: ../system/integrations/ldap/manage.rst:89 -msgid "Re-arrange LDAP source's order" +#: ../system/data-privacy.rst:22 +msgid "User deletion dialog in the Data Privacy panel" msgstr "" -#: ../system/integrations/ldap/manage.rst:84 +#: ../system/data-privacy.rst:22 msgid "" -"You can change the synchronization order for each source at any time. Zammad " -"will synchronize the sources from top to bottom." +"The user deletion dialog lists some of the tickets that will be removed from " +"the system along with the user." msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "" -"Screencasting showing how to change the source order by using\n" -"drag and drop." +#: ../system/data-privacy.rst:27 +msgid "Deleting Users via GUI" msgstr "" -#: ../system/integrations/ldap/manage.rst:101 -msgid "Remove a source" +#: ../system/data-privacy.rst:29 +msgid "🔥 **All deletions are FINAL!**" msgstr "" -#: ../system/integrations/ldap/manage.rst:92 -msgid "" -"If you no longer need the a LDAP source or simply want to start over, you " -"can remove them at any time. This will not remove synchronized users, data " -"synchronized or permissions." +#: ../system/data-privacy.rst:31 +msgid "Once you click “Delete”, the action cannot be canceled or undone." msgstr "" -#: ../system/integrations/ldap/manage.rst:98 +#: ../system/data-privacy.rst:33 msgid "" -"Not sure if you'd need the source later on? Set the source to inactive " -"instead of removing it - see *Review or edit existing source* for more." +"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." msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing how to remove LDAP sources." +#: ../system/data-privacy.rst:36 +msgid "**The following records cannot be deleted:**" msgstr "" -#: ../system/integrations/pgp/index.rst:2 -msgid "PGP" +#: ../system/data-privacy.rst:38 +msgid "your own account" msgstr "" -#: ../system/integrations/pgp/index.rst:7 -msgid "" -"Pretty Good Privacy (PGP) is another method for secure email communication. " -"With PGP, you can exchange **signed** and **encrypted** messages with others." +#: ../system/data-privacy.rst:39 +msgid "the system's last remaining administrator account" msgstr "" -#: ../system/integrations/pgp/index.rst:13 -#: ../system/integrations/smime/index.rst:17 -msgid "Signing" +#: ../system/data-privacy.rst:42 +msgid "Step 1: Find a User / Confirm Deletion" msgstr "" -#: ../system/integrations/pgp/index.rst:11 -msgid "is a proof that a message hasn't been manipulated on its way." +#: ../system/data-privacy.rst:44 +msgid "There are three ways to access the user deletion dialog:" msgstr "" -#: ../system/integrations/pgp/index.rst:13 -msgid "" -"In other words, it guarantees message **integrity** and **authenticity**." +#: ../system/data-privacy.rst:51 +msgid "**from the user's profile**" msgstr "" -#: ../system/integrations/pgp/index.rst:19 -#: ../system/integrations/smime/index.rst:22 -msgid "Encryption" +#: ../system/data-privacy.rst:0 +msgid "Accessing the user deletion dialog in a user profile" msgstr "" -#: ../system/integrations/pgp/index.rst:16 -#: ../system/integrations/smime/index.rst:20 -msgid "" -"scrambles a message so that it can only be unscrambled by the intended " -"recipient." +#: ../system/data-privacy.rst:51 +msgid "Click **Action > Delete**." msgstr "" -#: ../system/integrations/pgp/index.rst:19 -msgid "" -"In other words, it guarantees message **privacy** and **data security**." +#: ../system/data-privacy.rst:58 +msgid "**in the “Manage > Users” Admin Panel**" msgstr "" -#: ../system/integrations/pgp/index.rst:25 -msgid "Screenshot of ticket creation with encrypt and sign buttons" +#: ../system/data-privacy.rst:0 +msgid "Accessing the user deletion dialog under “Users” in the Admin Panel" msgstr "" -#: ../system/integrations/pgp/index.rst:25 -msgid "" -"Once PGP has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " -"appear in the ticket composer." +#: ../system/data-privacy.rst:58 +msgid "Use the **⋮ Actions** menu for the target user." msgstr "" -#: ../system/integrations/pgp/index.rst:28 -msgid "**Sign button not visible?**" +#: ../system/data-privacy.rst:66 ../system/data-privacy.rst:104 +msgid "**in the “System > Data Privacy” Admin Panel**" msgstr "" -#: ../system/integrations/pgp/index.rst:30 +#: ../system/data-privacy.rst:0 msgid "" -"Please note that the signing of emails is based on the outgoing email " -"account. That means you have to choose a group with a sender email account, " -"which has a private key assigned." +"Accessing the user deletion dialog under “Data Privacy” in the Admin Panel" msgstr "" -#: ../system/integrations/pgp/index.rst:35 -msgid "Handling of Keys" +#: ../system/data-privacy.rst:65 +msgid "" +"Use the **New Deletion Task** button. Search for users by name or email " +"address." msgstr "" -#: ../system/integrations/pgp/index.rst:36 -msgid "" -"To use the PGP function, you have to enable the integration (PGP) by " -"switching the toggle to *enabled*." +#: ../system/data-privacy.rst:79 +msgid "**Delete organizations**" msgstr "" -#: ../system/integrations/pgp/index.rst:39 +#: ../system/data-privacy.rst:69 msgid "" -"You can add keys by clicking the *add key* button. The keys can be imported " -"from a file or you can paste the content of the key in the text box." +"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:" msgstr "" -#: ../system/integrations/pgp/index.rst:42 -msgid "**Which keys do I have to import?**" +#: ../system/data-privacy.rst:0 +msgid "Deleting an organization via the user deletion dialog" msgstr "" -#: ../system/integrations/pgp/index.rst:44 +#: ../system/data-privacy.rst:78 msgid "" -"For **signing** *outgoing* emails, you have to import the private key of " -"your Zammad email account." +"If this option does not appear, make sure there are no pending deletion " +"tasks for other customers from this organization." msgstr "" -#: ../system/integrations/pgp/index.rst:47 -msgid "" -"For **encrypting** *outgoing* emails, you have to import the public key of " -"the customer's email account." +#: ../system/data-privacy.rst:82 +msgid "Step 2: Monitor Deletion Job Status" msgstr "" -#: ../system/integrations/pgp/index.rst:50 +#: ../system/data-privacy.rst:84 msgid "" -"For **verifying the signature** of signed *incoming* emails, you have to " -"import the public key of the customer." +"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:" msgstr "" -#: ../system/integrations/pgp/index.rst:53 -msgid "" -"For **decrypting** of encrypted *incoming* emails, you have to import the " -"private key of your Zammad email account." +#: ../system/data-privacy.rst:98 +msgid "**in the Activity Stream**" msgstr "" -#: ../system/integrations/pgp/index.rst:57 -msgid "Import Keys From a File" +#: ../system/data-privacy.rst:0 +msgid "Activity Stream showing data privacy tasks" msgstr "" -#: ../system/integrations/pgp/index.rst:58 -msgid "You can import keys from a file in the section **Upload key**:" +#: ../system/data-privacy.rst:94 +msgid "" +"For each deleted user, the Activity Stream will be updated twice—once when " +"the task is created, and once when it's complete." msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of adding a key via file" +#: ../system/data-privacy.rst:97 +msgid "" +"These notifications are only visible to users with ``admin.data_privacy`` " +"permissions." msgstr "" -#: ../system/integrations/pgp/index.rst:64 +#: ../system/data-privacy.rst:0 msgid "" -"**Supported file formats:** ASCII-armor as well as binary GPG format " -"(basically any GPG supported key format) is supported here." +"The task list within Data Privacy shows removals being in progress and " +"completed." msgstr "" -#: ../system/integrations/pgp/index.rst:68 -msgid "Import Keys by Pasting the Content" +#: ../system/data-privacy.rst:107 +msgid "Frequently Asked Questions" msgstr "" -#: ../system/integrations/pgp/index.rst:69 -msgid "You can also paste the key's content in the section **paste key**:" +#: ../system/data-privacy.rst:121 +msgid "What happens if I receive an email from a deleted customer?" msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of adding a key via pasting" +#: ../system/data-privacy.rst:110 +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/integrations/pgp/index.rst:75 +#: ../system/data-privacy.rst:115 msgid "" -"**Supported format:** Please note that only ASCII-armor is supported here." +"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**." msgstr "" -#: ../system/integrations/pgp/index.rst:78 -msgid "Deleting Keys" +#: ../system/data-privacy.rst:130 +msgid "What about user information stored in internal notes or other messages?" msgstr "" -#: ../system/integrations/pgp/index.rst:79 +#: ../system/data-privacy.rst:124 msgid "" -"If you want to delete a specific key, you can do it by clicking on the menu " -"in the *actions* column and select **delete**:" +"The deletion process removes **user accounts and associated tickets only**." msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of deleting a key" +#: ../system/data-privacy.rst:126 +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." msgstr "" -#: ../system/integrations/pgp/index.rst:88 -msgid "Downloading Keys" +#: ../system/data-privacy.rst:137 +msgid "I deleted an user and can still see a message they sent!" msgstr "" -#: ../system/integrations/pgp/index.rst:89 +#: ../system/data-privacy.rst:133 msgid "" -"If you want to download your keys, you can do this as well via corresponding " -"action buttons. Depending on the key, you can choose wether you want to " -"download the private or the public key." +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:95 -#: ../system/integrations/smime/manage-certificates.rst:76 -msgid "Default Behavior" +#: ../system/data-privacy.rst:141 +msgid "I removed a customer, now my reporting is off!" msgstr "" -#: ../system/integrations/pgp/index.rst:96 +#: ../system/data-privacy.rst:140 msgid "" -"Here you can adjust on per group basis, if *sign* and *encryption* is on or " -"off by default. Please be aware, that agents can always override the setting " -"for each individual article." +"When removing users and their tickets, all references are removed. This also " +"affects e.g. Reporting - these information are lost." msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Adjusting default behavior on per group basis" +#: ../system/data-privacy.rst:145 +msgid "How long does Zammad store created tasks?" msgstr "" -#: ../system/integrations/pgp/index.rst:107 +#: ../system/data-privacy.rst:144 msgid "" -"Here you can see the last actions regarding signing and encryption and if " -"they were successful." -msgstr "" - -#: ../system/integrations/pgp/index.rst:117 -msgid "**Sign button is not visible, but keys are imported.**" +"Please see the on-premise data section of the :docs:`data privacy ` chapter." msgstr "" -#: ../system/integrations/pgp/index.rst:115 -msgid "Did you choose a group in the ticket?" +#: ../system/data-privacy.rst:150 +msgid "What about re-assigned tickets? I want to delete them, too." msgstr "" -#: ../system/integrations/pgp/index.rst:116 +#: ../system/data-privacy.rst:148 msgid "" -"Did you import a private key for the email adress, which is used for " -"outgoing emails in the group?" +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:122 -msgid "**How to obtain keys?**" +#: ../system/data-privacy.rst:154 +msgid "Why are there so many deletion task entries, I didn't create them!" msgstr "" -#: ../system/integrations/pgp/index.rst:120 +#: ../system/data-privacy.rst:153 msgid "" -"You can create them yourself! There are some good tutorials on the web on " -"how to create them. Providing keys to Zammad is a prerequisite to use the " -"PGP feature." -msgstr "" - -#: ../system/integrations/pgp/index.rst:127 -msgid "**It says a passphrase is needed, but I haven't got one.**" +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:125 -msgid "" -"If the key is secured with a passphrase, you have to provide it for the " -"import in Zammad. It is possible that keys may have an empty passphrase. " -"However, this is *not* recommended." +#: ../system/integrations/checkmk/admin-panel-reference.rst:2 +msgid "Admin Panel Reference" msgstr "" -#: ../system/integrations/pgp/index.rst:132 -msgid "**How do my customers get my new key?**" +#: ../system/integrations/checkmk/admin-panel-reference.rst:None +msgid "Screenshot of Checkmk settings overview" msgstr "" -#: ../system/integrations/pgp/index.rst:130 +#: ../system/integrations/checkmk/admin-panel-reference.rst:12 msgid "" -"You have to provide your **public** key in advance. Your customer also has " -"to configure PGP in their email workflow and import your public key. The " -"other way round, you have to get the public key of your customer and have to " -"import it to Zammad." +"Which :doc:`group ` should Checkmk tickets be assigned " +"to as a default (*i.e.,* when none is specified)?" msgstr "" -#: ../system/integrations/slack.rst:2 -msgid "Slack" +#: ../system/integrations/checkmk/admin-panel-reference.rst:15 +msgid "(Applies to :ref:`API alerts ` only.)" msgstr "" -#: ../system/integrations/slack.rst:4 -msgid "**⚠️ Deprecation warning ⚠️**" +#: ../system/integrations/checkmk/admin-panel-reference.rst:21 +msgid "Auto close" msgstr "" -#: ../system/integrations/slack.rst:6 +#: ../system/integrations/checkmk/admin-panel-reference.rst:18 msgid "" -"Zammad 7 will no longer support this dedicated Slack integration. It is " -"recommended to switch to :doc:`pre-defined webhooks ` instead. Existing Slack integrations should " -"be migrated manually before this feature is dropped." +"Should Zammad automatically close tickets if a service has recovered on its " +"own?" msgstr "" -#: ../system/integrations/slack.rst:14 -msgid "" -"In order to use this feature, please add a new Slack app to your Workspace. " -"The App you need is called ``Incoming WebHooks`` ." +#: ../system/integrations/checkmk/admin-panel-reference.rst:21 +msgid "(Agents will receive notifications for such closures as appropriate.)" msgstr "" -#: ../system/integrations/slack.rst:18 -msgid "Why Do I Need This Feature?" +#: ../system/integrations/checkmk/admin-panel-reference.rst:30 +msgid "Auto-close state" msgstr "" -#: ../system/integrations/slack.rst:20 -msgid "" -"If you're already using Slack for your team communication, you'll love this " -"feature! Our Slack integration can push ticket notifications about the last " -"ticket article based on the following events:" +#: ../system/integrations/checkmk/admin-panel-reference.rst:24 +msgid "What ticket state should be applied when “auto-closing” a ticket?" msgstr "" -#: ../system/integrations/slack.rst:24 -msgid "on Ticket creation" +#: ../system/integrations/checkmk/admin-panel-reference.rst:26 +msgid "" +"You can choose from the seven built-in ticket states. If these states aren't " +"enough for you, you can :ref:`define a new ticket state ` for this purpose as well. This can be useful for tracking " +"tickets with :doc:`reports `, for example." msgstr "" -#: ../system/integrations/slack.rst:25 -msgid "on Ticket updates" +#: ../system/integrations/checkmk/admin-panel-reference.rst:35 +#: ../system/integrations/cti/includes/recent-logs.include.rst:2 +#: ../system/integrations/ldap/index.rst:74 +#: ../system/integrations/pgp/index.rst:106 +msgid "Recent Logs" msgstr "" -#: ../system/integrations/slack.rst:26 -msgid "on reached reminders" +#: ../system/integrations/checkmk/admin-panel-reference.rst:None +msgid "Screenshot of Checkmk \"Recent Logs\" section" msgstr "" -#: ../system/integrations/slack.rst:27 -msgid "a Ticket has escalated" +#: ../system/integrations/checkmk/admin-panel-reference.rst:41 +msgid "" +"If you're having trouble getting Zammad and Checkmk to play nicely together, " +"this section can help you troubleshoot." msgstr "" -#: ../system/integrations/slack.rst:28 -msgid "a Ticket is going to escalate" +#: ../system/integrations/checkmk/admin-panel-reference.rst:44 +msgid "" +"It contains a record of the fifty most recent transactions that Zammad knows " +"about, including each one's request/response details and return status." msgstr "" -#: ../system/integrations/slack.rst:30 -msgid "" -"Zammad will provide the Ticket title, a direct link to the Ticket, the event " -"type (creation, updated, escalation), the customer, time and the last " -"article that has triggered the notification." +#: ../system/integrations/checkmk/api-reference.rst:2 +msgid "API Reference" msgstr "" -#: ../system/integrations/slack.rst:34 +#: ../system/integrations/checkmk/api-reference.rst:4 msgid "" -"This will give you further options, as you can see e.g. escalating tickets " -"that are assigned to an agent that's e.g. absent. You can interact faster, " -"as you might see problems earlier (or even before the problem gets one)." +"For most users, :ref:`the sample scripts from the Setup Guide ` will do the job just fine. But if you want more fine-grained control" +"—for instance, to create high- and low-priority tickets for different types " +"of system events—then you'll have to customize the data those scripts send " +"to Zammad." msgstr "" -#: ../system/integrations/slack.rst:38 +#: ../system/integrations/checkmk/api-reference.rst:15 msgid "" -"If needed and wanted, you can even discuss directly about the topic before " -"sending an answer to the customer. Another possible use case would be a " -"agent monitoring new agents and their answers to tickets." +"This custom script will automatically set all tickets it creates to **high " +"priority** and **assign them to charlie@chrispresso.com**." msgstr "" -#: ../system/integrations/slack.rst:44 -#, fuzzy -msgid "Configure the Integration" -msgstr "Konfigurace widgetu Chat" +#: ../system/integrations/checkmk/api-reference.rst:32 +msgid "How Does it Work?" +msgstr "" -#: ../system/integrations/slack.rst:46 +#: ../system/integrations/checkmk/api-reference.rst:34 msgid "" -"First of all, please go to your slack workspace - go to administration => " -"Manage Apps. If you don't have an app yet, you can simply add a new one - " -"just search for ``Incoming WebHooks`` and customize the app to your needs." +"There are two kinds of data you can pass to the API, both in the form of key-" +"value pairs:" msgstr "" -#: ../system/integrations/slack.rst:50 -msgid "" -"Choose (or create) the channel Zammad should post it's information to and " -"press on \"Add Incoming WebHooks integration\". If you're ready, copy the " -"provided WebHook URL and go to your Zammad installation." +#: ../system/integrations/checkmk/api-reference.rst:44 +msgid "Checkmk parameters" msgstr "" -#: ../system/integrations/slack.rst:56 +#: ../system/integrations/checkmk/api-reference.rst:38 msgid "" -"You need administrative rights on the Slack Workspace. The link to the app " -"directory is normally ``https://[workspace-name].slack.com/apps`` ." +"are required, and make up the **contents** of the resulting tickets/" +"articles. They also determine whether an event creates a new ticket or " +"updates/closes an existing one." msgstr "" -#: ../system/integrations/slack.rst:63 +#: ../system/integrations/checkmk/api-reference.rst:42 msgid "" -"To configure the slack integration, log in to Zammad and go to Integrations " -"(System) => Slack in the admin panel." +"These are the only values used in the sample scripts. **Use them as-is**; " +"technically, they can be customized, but it's hard to imagine a good reason " +"for it." msgstr "" -#: ../system/integrations/slack.rst:66 -msgid "" -"Here you can choose on what evens Zammad should post information about a " -"ticket to your Slack channel. Next you need to device what groups shall be " -"affected by this, as anybody with access to that specific Slack channel can " -"read at least parts of the ticket this might be a privacy issue, if you " -"select the wrong groups. The username is simply the name that Zammad uses as " -"display name inside the Slack chat. The channel defines the Slack channel " -"the information is being posted in. As last option, you can set a custom " -"icon for posting to slack." +#: ../system/integrations/checkmk/api-reference.rst:52 +msgid "Ticket attributes" msgstr "" -#: ../system/integrations/slack.rst:74 +#: ../system/integrations/checkmk/api-reference.rst:47 msgid "" -"When you're ready, just hit \"Submit\" and enable the integration. Zammad " -"will now post new ticket information based on the trigger you chose. Below " -"the options you have the recent log that shows the latest requests to Slack " -"for debugging if needed." +"are optional, and can be used to **adjust settings** on newly created " +"tickets (*e.g.,* set the owner, group, priority, or state)." msgstr "" -#: ../system/integrations/slack.rst:81 +#: ../system/integrations/checkmk/api-reference.rst:50 msgid "" -"If you leave the Icon URL empty, Zammad will use the Zammad logo instead. " -"The icon should be a square PNG file." +"If you want to customize your Checkmk alert script, do it with these. Simply " +"add an extra “form” option for each one (``-F \"key=value\"``) to your " +"script's ``curl`` command line, as in the example above." msgstr "" -#: ../system/integrations/slack.rst:90 -msgid "" -"The following figure shows how it will look if you choose to receive updates " -"on created and updated tickets. On every post Zammad sends to the Slack " -"channel, you can create new threads to discuss about the new article." +#: ../system/integrations/checkmk/api-reference.rst:54 +msgid "💡 **It's just an API endpoint!**" msgstr "" -#: ../system/integrations/slack.rst:96 +#: ../system/integrations/checkmk/api-reference.rst:56 msgid "" -"If you just want to keep track of soon escalating or already escalated " -"tickets, it will look the the following figure. Zammad changes the color in " -"front of the post so you can easily see the state of the ticket." +"When using Checkmk integration, messages need to be formatted in a certain " +"way, but that *doesn't mean the messages actually have to come from Checkmk*." msgstr "" -#: ../system/integrations/slack.rst:102 +#: ../system/integrations/checkmk/api-reference.rst:59 msgid "" -"If you change the state, Zammad will also put information on what state the " -"ticket gets and (if pending state) the date until it pends. You'll also " -"recognize the color codes in front of posts on slack, as they are exact the " -"same the ticket state colors you'll see in Zammad!" +"If you use another monitoring tool that's not officially supported by " +"Zammad, there's probably a way to make it work with your Checkmk callback " +"URL." msgstr "" -#: ../system/integrations/smime/index.rst:2 -msgid "S/MIME" +#: ../system/integrations/checkmk/api-reference.rst:63 +msgid "Checkmk Parameters" msgstr "" -#: ../system/integrations/smime/index.rst:11 +#: ../system/integrations/checkmk/api-reference.rst:65 msgid "" -"S/MIME is the most widely-supported method for secure email communication. " -"With S/MIME, you can exchange **signed** and **encrypted** messages with " -"others." +"When a notification is received, Zammad creates a new article containing the " +"details of the event that triggered it:" msgstr "" -#: ../system/integrations/smime/index.rst:15 -msgid "" -"is proof that a message hasn't been tampered with or sent by an impersonator." +#: ../system/integrations/checkmk/api-reference.rst:None +msgid "Checkmk article body" msgstr "" -#: ../system/integrations/smime/index.rst:17 +#: ../system/integrations/checkmk/api-reference.rst:72 msgid "" -"In other words, it guarantees a message's **integrity** and **authenticity**." +"These details come from the fields listed below, which correspond to " +"parameters provided by Checkmk (``$NOTIFY_*``)." msgstr "" -#: ../system/integrations/smime/index.rst:22 -msgid "In other words, it guarantees **privacy** and **data security**." +#: ../system/integrations/checkmk/api-reference.rst:75 +msgid "**Required fields are marked with an asterisk (\\*).**" msgstr "" -#: ../system/integrations/smime/index.rst:28 -msgid "Screencast demo of S/MIME features for both new tickets and replies" +#: ../system/integrations/checkmk/api-reference.rst:79 +msgid "event_id\\*" msgstr "" -#: ../system/integrations/smime/index.rst:28 +#: ../system/integrations/checkmk/api-reference.rst:78 msgid "" -"Once S/MIME has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " -"appear in the ticket composer." +"A unique ID for the system event. (``$NOTIFY_SERVICEPROBLEMID`` / " +"``$NOTIFY_HOSTPROBLEMID``)" msgstr "" -#: ../system/integrations/smime/index.rst:32 -msgid ":doc:`🔪 Prerequisites `" +#: ../system/integrations/checkmk/api-reference.rst:86 +msgid "host\\*" msgstr "" -#: ../system/integrations/smime/index.rst:31 +#: ../system/integrations/checkmk/api-reference.rst:82 msgid "" -"New to S/MIME? This section helps you to find certificate providers and " -"points out Limitations." -msgstr "" - -#: ../system/integrations/smime/index.rst:35 -msgid ":doc:`📝 Manage Certificates `" -msgstr "" - -#: ../system/integrations/smime/index.rst:35 -msgid "Add and download certificates; configure group default behaviors." +"The hostname of the system that the event originated from. " +"(``$NOTIFY_HOSTNAME``)" msgstr "" -#: ../system/integrations/smime/index.rst:38 -msgid ":doc:`😦 Troubleshooting `" +#: ../system/integrations/checkmk/api-reference.rst:85 +msgid "" +"Used to determine if a new event belongs to an existing ticket. Also used in " +"the subject line of the resulting article (“ is ”)." msgstr "" -#: ../system/integrations/smime/index.rst:38 -msgid "Took a wrong turn? About recent logs and common issues." +#: ../system/integrations/checkmk/api-reference.rst:96 +msgid "service" msgstr "" -#: ../system/integrations/smime/index.rst:43 +#: ../system/integrations/checkmk/api-reference.rst:89 msgid "" -"For more details on how S/MIME integration works on the agent side, see the :" -"user-docs:`user docs `." +"The name of the service that the event originated from. " +"(``$NOTIFY_SERVICEDESC``)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:2 -msgid "Manage Certificates" +#: ../system/integrations/checkmk/api-reference.rst:92 +msgid "Used to determine if a new event belongs to an existing ticket." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:4 -msgid "" -"S/MIME is **disabled by default**. Enable it to start adding certificates." +#: ../system/integrations/checkmk/api-reference.rst:94 +#: ../system/integrations/checkmk/api-reference.rst:110 +msgid "Displayed as ``-`` when omitted." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:10 -msgid "Dialogue to add new certificates or private keys" +#: ../system/integrations/checkmk/api-reference.rst:104 +msgid "state\\*" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:10 +#: ../system/integrations/checkmk/api-reference.rst:99 msgid "" -"Manage certificates in the Admin Panel under **System > Integrations > S/" -"MIME**. Certificates may be pasted in as plain text or uploaded from a file." +"The current state of the service or host in question. " +"(``$NOTIFY_SERVICESTATE`` / ``$NOTIFY_HOSTSTATE``)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:14 -msgid "Add Certificate Data" +#: ../system/integrations/checkmk/api-reference.rst:102 +msgid "" +"Used to detect when a ticket should be auto-closed (*i.e.,* on ``OK``/" +"``UP``). Also used in the subject line of the resulting article (“ is " +"”)." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:36 -msgid "Add Certificate" +#: ../system/integrations/checkmk/api-reference.rst:110 +msgid "text" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:17 +#: ../system/integrations/checkmk/api-reference.rst:107 msgid "" -"Import public-key certificates for both your own organization and your " -"contacts." +"The output of the process that triggered the event. " +"(``$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:19 +#: ../system/integrations/checkmk/api-reference.rst:121 msgid "" -"You can also add a bunch of certificates in one go by providing a single " -"file with all relevant certificates." +"The Object Manager attribute panel displays built-in and custom\n" +"attribute names." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:22 -msgid "🕵️ **ALWAYS verify certificates in-person or over the phone!**" +#: ../system/integrations/checkmk/api-reference.rst:121 +msgid "Find a complete list of ticket attributes in the Object Manager." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:24 +#: ../system/integrations/checkmk/api-reference.rst:123 msgid "" -"The whole point of signatures is to alert you when someone is trying to " -"pretend to be someone they're not. Never accept a certificate from someone " -"online without verifying it first." -msgstr "" - -#: ../system/integrations/smime/manage-certificates.rst:28 -msgid "📇 **What about trusted certificate authorities?**" +"Ticket attributes are entirely optional, and can be used to customize the " +"tickets that Checkmk creates. (Note that these attributes will be ignored if " +"a new event belongs to an existing ticket.)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:30 +#: ../system/integrations/checkmk/api-reference.rst:128 msgid "" -"In some cases (e.g. when dealing with large enterprises), you may be given a " -"certificate for an entire CA, rather than a single contact. Add it here to " -"trust *all* certificates issued by that CA." +"Why would you want to do this? Maybe you have only one IT guy, and all " +"system monitoring issues should be automatically assigned to him. Or, maybe " +"you're creating multiple notification rules so that database outages take " +"higher priority than disk space warnings." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:35 -msgid "" -"Commercial CAs can usually be verified online. Zammad does not include a " -"list of built-in, trusted CAs." +#: ../system/integrations/checkmk/api-reference.rst:135 +msgid "In most cases, you'll probably want to set one of the following:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:57 -msgid "Add Private Key" +#: ../system/integrations/checkmk/api-reference.rst:137 +msgid "group" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:39 -msgid "" -"Once you've added a public-key certificate, you can import its matching " -"private key." +#: ../system/integrations/checkmk/api-reference.rst:139 +msgid "state" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:42 -msgid "" -"Private keys are for **your own organization only**; never ask your contacts " -"for their private keys." +#: ../system/integrations/checkmk/api-reference.rst:140 +msgid "priority" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:0 +#: ../system/integrations/checkmk/api-reference.rst:142 msgid "" -"S/MIME integration showing configured certificates and possible issues with " -"Logging" +"but in practice, you can set almost any attribute, including :doc:`custom " +"ones you created through the Object Manager `." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:50 -msgid "" -"A note is displayed on certificates with a matching private key (see line 2)." +#: ../system/integrations/checkmk/api-reference.rst:145 +msgid "Please note that the following attributes are **not customizable**:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:52 -msgid "📤 **Certificates and private keys must be uploaded separately.**" +#: ../system/integrations/checkmk/api-reference.rst:147 +msgid "title" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:54 -msgid "" -"If your certificate and private key are bundled together in the same file or " -"PEM block, import it twice (once using each button)." +#: ../system/integrations/checkmk/api-reference.rst:148 +msgid "id" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:57 -msgid "Please note that bulk imports of private keys are not possible." +#: ../system/integrations/checkmk/api-reference.rst:149 +msgid "ticket number" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:60 -msgid "Download Certificate Data" +#: ../system/integrations/checkmk/api-reference.rst:151 +msgid "created_by_id" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:62 -msgid "" -"You can download the earlier provided certificates and private keys at any " -"time from your Zammad instance." +#: ../system/integrations/checkmk/api-reference.rst:152 +msgid "updated_by_id" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:65 +#: ../system/integrations/checkmk/api-reference.rst:155 +msgid "Which Values Can Be Set?" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:157 +msgid "😵 **Invalid values → unpredictable behavior**" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:159 msgid "" -"Please note that passphrase-protected private keys stay protected and when " -"you download them, you have to know the passphrase to use them after " -"downloading." +"If you provide a value that Zammad doesn't understand (*e.g.,* ``-F " +"\"priority=high\"``), it's not always clear what will happen. In some cases, " +"a ticket will be created with the default values instead - but in others, it " +"may not be created at all!" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:73 -msgid "Dialogue to download certificates or private keys" +#: ../system/integrations/checkmk/api-reference.rst:164 +msgid "So what values does Zammad understand, then? Well, it depends..." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:73 -msgid "Download stored certificates and their keys" +#: ../system/integrations/checkmk/api-reference.rst:168 +msgid "Use an email address or username:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:78 -msgid "" -"The ticket composer will set all outgoing messages to **signed and " -"encrypted** by default (assuming the required certificates exist)." +#: ../system/integrations/checkmk/api-reference.rst:190 +msgid "group & priority" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:82 -msgid "These defaults can be modified on a per-group basis:" +#: ../system/integrations/checkmk/api-reference.rst:175 +msgid "Refer to the dropdown menus in the ticket pane:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:None -msgid "Zammad allowing to choose the default behavior on per group basis" +#: ../system/integrations/checkmk/api-reference.rst:0 +msgid "See possible values for certain attributes in the ticket pane." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:89 +#: ../system/integrations/checkmk/api-reference.rst:187 +msgid "🙅 **Ticket state CANNOT be set this way!**" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:189 msgid "" -"Of course, agents can always manually change these settings on each email " -"they send out." +"Why? Because ``-F \"state=...\"`` is already used :ref:`as a Checkmk " +"parameter `." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:4 -msgid "A certificate *and* private key for your own organization" +#: ../system/integrations/checkmk/api-reference.rst:222 +msgid "Everything Else" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:6 +#: ../system/integrations/checkmk/api-reference.rst:193 msgid "" -"(Use this to ✒️ **sign outgoing messages** and 🔓 **decrypt incoming " -"messages**.)" +"To set any other attributes, it helps to know your way around the :docs:" +"`rails console `. Valid values are those that you can " +"set with a string:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:9 -msgid "" -"Certificates belonging your contacts, or their issuing certificate authority " -"(CA)" +#: ../system/integrations/checkmk/api-reference.rst:218 +msgid "These values can then be passed directly to the API:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:11 -msgid "" -"(Use these to ✅ **verify incoming message signatures** and 🔒 **encrypt " -"outgoing messages**.)" +#: ../system/integrations/checkmk/index.rst:16 +msgid "How does it work?" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:14 -msgid "🙋 **I'm new to S/MIME. Where can I get a certificate?**" +#: ../system/integrations/checkmk/index.rst:2 +msgid "Checkmk" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:16 +#: ../system/integrations/checkmk/index.rst:4 msgid "" -"The easiest way to get certificates is to buy an annual subscription through " -"a commercial CA, such as:" +"`Checkmk `_ is a powerful IT monitoring tool that can " +"send real-time status alerts to Zammad via email or REST API. Set these " +"alerts up in Checkmk, and Zammad will automatically create, update, and " +"close tickets based on the health of your system:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:19 -msgid "" -"`Sectigo (formerly Comodo) `_" +#: ../system/integrations/checkmk/index.rst:14 +msgid "Screenshot of ticket created by Checkmk notifications" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:20 -msgid "`Secorio `_" +#: ../system/integrations/checkmk/index.rst:14 +msgid "Multiple alerts, same ticket." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:21 -msgid "`GlobalSign `_" +#: ../system/integrations/checkmk/setup-guide.rst:2 +msgid "Setup Guide" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:23 -msgid "(Zammad is not affiliated with these CAs in any way.)" +#: ../system/integrations/checkmk/setup-guide.rst:4 +msgid "" +"Whenever the Checkmk integration is enabled, Zammad listens for messages on " +"its API and over email. As long as those messages follow the required " +"format, Zammad will create new tickets (or find and update existing ones) " +"based on the message contents." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:25 +#: ../system/integrations/checkmk/setup-guide.rst:10 msgid "" -"You can also generate your own self-signed certificates, but the process is " -"complicated and usually 🙅 **involves extra work for your contacts**." +"That means that “setting up Checkmk integration” is simply a matter of " +"**adding configuration to your Checkmk site**: telling it when to send these " +"messages and what to say. To do that, you'll need to create a new " +"**notification rule** (see `Checkmk's official docs `_ for help with that)." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:29 +#: ../system/integrations/checkmk/setup-guide.rst:17 msgid "" -"Bear in mind that 🤝 **S/MIME only works if the other party is using it, too." -"**" +"As part of this new rule, you'll have to choose a **notification method** " +"(*i.e.,* a script to execute whenever the rule is triggered). This script " +"will be written by you (samples below), and contain the logic for sending " +"API/email messages to Zammad:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:32 -msgid "Certificate and Private Key Checks on Upload" +#: ../system/integrations/checkmk/setup-guide.rst:26 +msgid "Checkmk \"New Rule\" dialog" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:34 +#: ../system/integrations/checkmk/setup-guide.rst:26 msgid "" -"The certificate and public key validation is based on the ``X509v3`` " -"extensions." +"Find your custom scripts in the Checkmk WATO under **Notifications > New " +"Rule > Notification Method**." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:49 -msgid "Uploading a *client certificate*?" +#: ../system/integrations/checkmk/setup-guide.rst:29 +msgid "" +"Once you're done setting up your new rule, you're all set! New tickets " +"should start coming in and auto-updating any time your rule is triggered." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:41 -msgid "The following attributes are required then:" +#: ../system/integrations/checkmk/setup-guide.rst:33 +msgid "" +"(If you need help troubleshooting, be sure to check the :ref:`checkmk-recent-" +"logs`.)" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:39 -msgid "Subject Alternative Name (at least one email address has to be present)" +#: ../system/integrations/checkmk/setup-guide.rst:38 +msgid "API Alerts" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:40 -msgid "Key Usage (``Digital Signature`` and/or ``Key Encipherment``)" +#: ../system/integrations/checkmk/setup-guide.rst:40 +msgid "" +"To add these scripts in the Checkmk WATO, copy them into your Checkmk " +"installation directory and make them executable. (Be sure to replace the " +"``zammad.example.com`` callback URL with the one found in your admin panel.)" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:41 -msgid "Public key algorithm (either ``RSA`` or ``EC``)" +#: ../system/integrations/checkmk/setup-guide.rst:60 +msgid "Service notification" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:43 +#: ../system/integrations/checkmk/setup-guide.rst:46 msgid "" -"The Extended Key Usage attribute is optional. If the certificate provides " -"the named attribute, than it must contain the value ``E-mail Protection``." +"For updates on the status of the software running on your server (*e.g.,* " +"postgres)." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:46 -msgid "" -"Please note that any usable email adress has to be prefixed with ``email:`` " -"or ``rfc822:``." +#: ../system/integrations/checkmk/setup-guide.rst:75 +msgid "Host notification" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:49 -msgid "The named public key algorithms are mandatory for private keys as well." +#: ../system/integrations/checkmk/setup-guide.rst:63 +msgid "For updates on the status of the server itself." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:54 -msgid "Uploading a *CA certificate*?" +#: ../system/integrations/checkmk/setup-guide.rst:77 +msgid "🤔 **What's with all the env vars?**" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:52 +#: ../system/integrations/checkmk/setup-guide.rst:79 msgid "" -"In the case of an uploaded CA certificate, providing the value ``CA:TRUE`` " -"in the attribute *Basic Contstraints*, the previously mentioned attributes " -"are not verified." +"Whenever Checkmk runs these scripts, it needs to provide some information " +"about the event that triggered the notification. This information is passed " +"in the form of these ``$NOTIFY_*`` environment variables." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:56 +#: ../system/integrations/checkmk/setup-guide.rst:85 msgid "" -"In general, the usage of any expired (``Not After``) or not yet valid (``Not " -"Before``) certificate is denied for outgoing emails." +"You can specify additional parameters to pass to the script when you're " +"setting up your notification rule, but the ones you see here are all " +"provided by default." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:59 -msgid "Example certificate:" +#: ../system/integrations/checkmk/setup-guide.rst:90 +msgid "Email Alerts" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:85 +#: ../system/integrations/checkmk/setup-guide.rst:94 msgid "" -"Please note that Zammad will distrust senders by default. This means that " -"you're always required to provide certificate data, no matter if for signing " -"or encrypting." -msgstr "" - -#: ../system/integrations/smime/prerequisites.rst:89 -msgid "This is by design and can't be adjusted." +"🐞 **There are known bugs** in Zammad's processing of email from Checkmk. " +"This section will be completed once they have been resolved. (Learn more at " +"GitHub issues `#2377 `_ & " +"`#2180 `_.)" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:4 -msgid "" -"All of the system's latest S/MIME activity is displayed in the **Recent " -"Logs** section." +#: ../system/integrations/checkmk/setup-guide.rst:100 +msgid "In the meantime, we encourage you to set up API alerts instead." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:11 -msgid "Sample entries of in- and outgoing S/MIME related emails." +#: ../system/integrations/clearbit.rst:2 +msgid "Clearbit" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:11 +#: ../system/integrations/clearbit.rst:4 msgid "" -"Logs report the status and details of all mail, both incoming and outgoing, " -"that used signing/verification or encryption/decryption." +"With our Clearbit integration, you can easily enrich the information " +"provided by Zammad. If the customers or agents email address is known to " +"Clearbit, it will share all information it has regarding the user with " +"Zammad. Those information can include the following:" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:14 -msgid "" -"This log does **not** include email sent by :doc:`triggers ` or the :doc:`scheduler `. For those, check your " -"``production.log``." +#: ../system/integrations/clearbit.rst:9 +msgid "Avatar" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:20 -msgid "Common Issues" +#: ../system/integrations/clearbit.rst:10 +msgid "Address information" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:30 -msgid "I received a signed/encrypted email before I set up S/MIME integration" -msgstr "" - -#: ../system/integrations/smime/troubleshooting.rst:23 -msgid "" -"No problem. Once S/MIME has been enabled and the appropriate certificates " -"have been added, agents will be prompted to retry verification/decryption on " -"matching emails." -msgstr "" - -#: ../system/integrations/smime/troubleshooting.rst:0 -msgid "Screenshot of user prompt to retry decryption" +#: ../system/integrations/clearbit.rst:11 +msgid "Website information" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:38 -msgid "The 🔒 **Encrypt** button is disabled" +#: ../system/integrations/clearbit.rst:12 +msgid "A BIO (as Note by default)" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:33 -msgid "Have you added the recipient's certificate?" +#: ../system/integrations/clearbit.rst:14 +msgid "" +"If needed, you can add further custom objects and add mappings to them, so " +"the Clearbit information can be filled within the database. In general you " +"can get any information from Clearbit, as long as you have a mapping to an " +"Zammad object." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:34 -msgid "Are you sure the recipient's certificate is valid?" +#: ../system/integrations/clearbit.rst:21 +msgid "" +"Clearbit does have a mapping of fields like LDAP and Exchange have, but does " +"not \"win\" against Zammad information. This means that if you have e.g. the " +"last name field filled in already and Clearbit has other information on " +"that, it will not be updated." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:35 -msgid "Have you checked your ``production.log`` for more details?" +#: ../system/integrations/clearbit.rst:26 +msgid "" +"However: If let's say the last name has been set by Clearbit and Zammad " +"notices that the last name on the Clearbit source has changed, Zammad will " +"also update this value." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:37 +#: ../system/integrations/clearbit.rst:33 msgid "" -"If encryption doesn't work in the composer, it won't work in :doc:`triggers " -"` or the :doc:`scheduler ` either!" +"The configuration of Clearbit is really easy and done fast! Just login to " +"your Clearbit-Account, go to \"API\" and copy the secret-API-Key." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:42 -msgid "The ✅ **Sign** button is disabled" +#: ../system/integrations/clearbit.rst:38 +msgid "" +"Now change to your Zammad instance, go to Integrations (System) -> Clearbit " +"in the admin panel. Paste your API-Key into the API-Key-Field and decide if " +"Zammad should create unknown Organizations automatically, if the user does " +"not have one yet (and Clearbit knows it). The shared option decides if the " +"new organizations Zammad creates with Clearbit should be shared ones." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:41 +#: ../system/integrations/clearbit.rst:47 msgid "" -"Have you added **both the certificate and private key** for your " -"organization?" +"If you're unsure what option to choose, better stick with \"no\". You can " +"also learn more about :doc:`/manage/organizations/index`." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:42 +#: ../system/integrations/clearbit.rst:52 msgid "" -"Does the email address on the certificate match the email address of the " -"agent/group composing the email?" +"The Mapping option works similar to the mapping within the Exchange and LDAP " +"sync. You can add further mappings for e.g. custom fields if you need more " +"information that Clearbit can provide." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:45 -msgid "Error: “Fingerprint already taken”" +#: ../system/integrations/clearbit.rst:58 +msgid "" +"If you want to add more Clearbit fields and want to learn more about " +"available fields on their API, you can take a look at their `API " +"documentation `_." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:45 -msgid "Are you sure you haven't added this certificate already?" +#: ../system/integrations/clearbit.rst:62 +msgid "" +"If you're happy with the above chosen Settings and your mapping, just save " +"the changes and enable Clearbit integration. Zammad will now start polling " +"the Clearbit API as users contact you." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:48 -msgid "Error: “❌ invalid byte sequence in UTF-8”" +#: ../system/integrations/clearbit.rst:68 +msgid "" +"Zammad does not synchronize with Clearbit on a regular basis, but on demand " +"if needed. This saves API calls." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:48 -msgid "Please ensure to provide PEM formatted certificate and keys." +#: ../system/integrations/clearbit.rst:73 +msgid "" +"Below the Settings and Mappings, you'll find our Integration log. You can " +"see what requests Zammad sent to Clearbit and also the APIs Response." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:49 -msgid "Did you check if the provided file is a valid certificate or key?" +#: ../system/integrations/clearbit.rst:78 +msgid "" +"By the way, you can also view the API log on the Clearbit website - the " +"information seen is basically the same." msgstr "" -#: ../system/integrations/zabbix.rst:2 -msgid "Zabbix Integration" +#: ../system/integrations/clearbit.rst:84 +msgid "Example When Adding a User" msgstr "" -#: ../system/integrations/zabbix.rst:5 +#: ../system/integrations/clearbit.rst:86 msgid "" -"This guide describes how to integrate your Zabbix 5.4 installation with " -"Zammad using the Zabbix webhook feature. This guide will provide " -"instructions on setting up a media type, a user and an action in Zabbix." +"To show you how fast information is added, we added a small Screencast " +"below. This shows the creation of the User Alex from Clearbit. As we already " +"set the last name of Alex to \"X\", Zammad did not update it. What Zammad " +"did was to add further information it received from Clearbit." msgstr "" -#: ../system/integrations/zabbix.rst:12 -msgid "Zammad with enabled HTTP Token Authentication" +#: ../system/integrations/cti/generic.rst:2 +msgid "CTI (generic)" msgstr "" -#: ../system/integrations/zabbix.rst:13 -msgid "Zabbix version 5.4 or higher" +#: ../system/integrations/cti/includes/introduction.include.rst:1 +msgid "" +"This integration enables Zammad to provide a caller log to your agents. With " +"this your agents can greet your customers by their name and are supported by " +"Zammad with automatically opening a new ticket dialog or the user profile." msgstr "" -#: ../system/integrations/zabbix.rst:16 -msgid "Setting up a Zammad" +#: ../system/integrations/cti/includes/introduction.include.rst:6 +msgid "" +"Click the toggle next to the heading to activate or deactivate this " +"integration." msgstr "" -#: ../system/integrations/zabbix.rst:18 -msgid "Enable **API Token Access** in Settings > System > API." +#: ../system/integrations/cti/includes/introduction.include.rst:9 +msgid "" +"If you want to learn more on how your agents can use this function, please " +"refer the :user-docs:`user documentation `." msgstr "" -#: ../system/integrations/zabbix.rst:20 +#: ../system/integrations/cti/includes/introduction.include.rst:14 msgid "" -"Create a **new user** for a Zabbix alerter with an **email address** and " -"create a personal user token with **ticket.agent** permissions." +"Automatically opening new ticket dialogues or user profiles requires agent " +"to extension mapping - see more below." msgstr "" -#: ../system/integrations/zabbix.rst:24 -msgid "Zabbix Webhook Configuration" +#: ../system/integrations/cti/includes/introduction.include.rst:20 +msgid "Please note the following limitations to reduce confusion later on:" msgstr "" -#: ../system/integrations/zabbix.rst:27 -msgid "Create a Global Macro" +#: ../system/integrations/cti/includes/introduction.include.rst:22 +msgid "CTI integrations provide caller log functions only." msgstr "" -#: ../system/integrations/zabbix.rst:29 +#: ../system/integrations/cti/includes/introduction.include.rst:23 msgid "" -"Before setting up the **Webhook**, you need to setup the global macro " -"**{$ZABBIX.URL}**, which must contain the **URL** to the **Zabbix frontend**." +"This integration does not provide any VoIP functionalities; you can't make " +"phone calls from within Zammad." msgstr "" -#: ../system/integrations/zabbix.rst:33 +#: ../system/integrations/cti/includes/introduction.include.rst:25 msgid "" -"In the **Administration** > **Media types** section, import the `Template`_." +"If your browser supports ``tel``-URLs, you can click on phone numbers for " +"automatic dialing. This requires additional software / configuration on your " +"agent's computers." msgstr "" -#: ../system/integrations/zabbix.rst:38 -msgid "Open the added **Zammad** media type and set:" +#: ../system/integrations/cti/generic.rst:9 +#: ../system/integrations/cti/placetel.rst:14 +#: ../system/integrations/cti/sipgate.rst:14 +msgid "Please provide the following requirements:" msgstr "" -#: ../system/integrations/zabbix.rst:40 -msgid "**zammad\\_access\\_token** to the your **Personal User Token**" +#: ../system/integrations/cti/generic.rst:11 +msgid "" +"A telephone system that supports webhooks (outbound) (best option are those " +"that allow customizing the calls)." msgstr "" -#: ../system/integrations/zabbix.rst:41 -msgid "" -"**zammad\\_url** to the **frontend URL** of your **Zammad** installation" +#: ../system/integrations/cti/generic.rst:13 +msgid "A unique Call-ID during the call session." msgstr "" -#: ../system/integrations/zabbix.rst:43 -msgid "**zammad\\_customer** to your **Zammad user email**." +#: ../system/integrations/cti/generic.rst:14 +msgid "Call event data (both numbers and direction)." msgstr "" -#: ../system/integrations/zabbix.rst:44 -msgid "" -"**zammad\\_enable\\_tags** to **true** or **false** to enable or disable " -"trigger tags. **Important**: if you enable tag support, each tag is set with " -"a separate request." +#: ../system/integrations/cti/generic.rst:15 +msgid "Your Zammad instance must be reachable for your telephony system." msgstr "" -#: ../system/integrations/zabbix.rst:48 +#: ../system/integrations/cti/generic.rst:17 msgid "" -"If you want to prioritize issues according to **severity** values in Zabbix, " -"you can define mapping parameters:" +"If you want to learn more on what kind of requests are supported by Zammad " +"and what it expects, please consult our :docs:`CTI-API documentation `." msgstr "" -#: ../system/integrations/zabbix.rst:51 -msgid "**severity\\_**: Zammad priority ID" +#: ../system/integrations/cti/generic.rst:22 +#: ../system/integrations/cti/placetel.rst:27 +#: ../system/integrations/cti/sipgate.rst:30 +msgid "Available Settings" msgstr "" -#: ../system/integrations/zabbix.rst:53 -msgid "Click the **Update** button to save the **Webhook** settings." +#: ../system/integrations/cti/generic.rst:29 +#: ../system/integrations/cti/placetel.rst:41 +#: ../system/integrations/cti/sipgate.rst:40 +msgid "Endpoint Settings" msgstr "" -#: ../system/integrations/zabbix.rst:55 +#: ../system/integrations/cti/generic.rst:25 msgid "" -"To receive notifications in **Zammad**, you need to create a **Zabbix user** " -"and add **Media** with the **Zammad** type." +"Zammad will list your generic CTI endpoint here. It contains a unique token " +"so ensure to keep this URL save." msgstr "" -#: ../system/integrations/zabbix.rst:58 +#: ../system/integrations/cti/generic.rst:28 msgid "" -"For **Send to**: enter any text, as this value is not used, but is required." +"You'll need this endpoint for your PBX to talk to Zammad, see :docs:`CTI-API " +"documentation `." msgstr "" -#: ../system/integrations/zabbix.rst:61 +#: ../system/integrations/cti/includes/important-dont-forget-saving.include.rst:3 msgid "" -"For more information, use the `Zabbix documentation `_." +"All following options **do not save automatically**. Always use the Save " +"button on the lower end of the integration page!" msgstr "" -#: ../system/maintenance.rst:2 -msgid "Maintenance" +#: ../system/integrations/cti/generic.rst:43 +#: ../system/integrations/cti/placetel.rst:49 +#: ../system/integrations/cti/sipgate.rst:52 +msgid "Call Settings" msgstr "" -#: ../system/maintenance.rst:4 +#: ../system/integrations/cti/generic.rst:39 +#: ../system/integrations/cti/placetel.rst:49 +#: ../system/integrations/cti/sipgate.rst:37 +#: ../system/integrations/cti/sipgate.rst:50 +msgid "Inbound" +msgstr "" + +#: ../system/integrations/cti/includes/inbound-calls.include.rst:1 msgid "" -"Zammad comes with a maintenance mode that you can use for e.g. updating the " -"instance or changing settings while restricting availability and functions." +"This option allows you to block specific incoming caller IDs. It allows you " +"to temporarily reject e.g. spam callers without having to contact providers " +"or PBX administrators." msgstr "" -#: ../system/maintenance.rst:13 -msgid "Mode" +#: ../system/integrations/cti/includes/inbound-calls.include.rst:11 +msgid "Caller ID to block" msgstr "" -#: ../system/maintenance.rst:8 -msgid "The mode setting allows you to enable or disable the maintenance mode." +#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 +msgid "Provide caller IDs to block in ``E.164`` format." msgstr "" -#: ../system/maintenance.rst:10 -msgid "Defaults to *off*." -msgstr "" - -#: ../system/maintenance.rst:12 -msgid "" -"The maintenance mode will restrict access to administrative roles only. This " -"means agents and customers are logged off." -msgstr "" - -#: ../system/maintenance.rst:23 -msgid "@Login" -msgstr "" - -#: ../system/maintenance.rst:16 -msgid "" -"This setting allows you to provide a login message within a green banner " -"above the login screen. Click into the green banner in the settings page to " -"adjust your message. To activate the message, activate the *@Login* setting." -msgstr "" - -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing the default login message within the\n" -"settings page" -msgstr "" - -#: ../system/maintenance.rst:26 -msgid "" -"Send an informative message to **all active sessions**. This comes handy to " -"inform your agents e.g. about mayor outages or to force reloads after " -"configuration changes." -msgstr "" - -#: ../system/maintenance.rst:31 -msgid "This is the messages title (slightly bigger than the normal message)." -msgstr "" - -#: ../system/maintenance.rst:34 -msgid "The text you want to provide to your logged in sessions." -msgstr "" - -#: ../system/maintenance.rst:39 -msgid "Reload application" -msgstr "" - -#: ../system/maintenance.rst:37 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:8 msgid "" -"Selecting this option will change the message acceptance button from *Close* " -"(with nothing happening) to *Continue session*, which forces the application " -"to reload." +"Your telephony system has to support this function. Zammad will send a " +"``reject`` response which will cause your telephony system to hang up the " +"call. To callers this usually will feel like the line is busy." msgstr "" -#: ../system/maintenance.rst:43 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:14 msgid "" -"If you have customers that are logged in to Zammad, they'll also be notified " -"if they're active in that moment." -msgstr "" - -#: ../system/maintenance.rst:48 -msgid "Example without reload application" +"Provide a meaningful note for your fellow administrators to remind yourself " +"why you've chosen to block the number." msgstr "" -#: ../system/maintenance.rst:52 -msgid "" -"Message setting within Zammad's admin settings without ticket reload " -"application setting." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:17 +#: ../system/integrations/cti/sipgate.rst:40 +msgid "Outbound" msgstr "" -#: ../system/maintenance.rst:0 +#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:1 msgid "" -"Screenshot showing the send message settings without ticket\n" -"reload application set" +"In many cases you may want to use a different caller ID depending on the " +"destination you're calling. This may apply due to specific connection rates " +"to other countries or because you want your customer to feel you're calling " +"from the same country." msgstr "" -#: ../system/maintenance.rst:61 ../system/maintenance.rst:85 -msgid "" -"The modal all other active sessions will see upon pressing *Send to clients*." +#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:6 +msgid "This option expects ``E.164`` number formats." msgstr "" -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing modal caused by maintenance's message\n" -"without reload application ticket" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 +msgid "Destination caller ID" msgstr "" -#: ../system/maintenance.rst:72 -msgid "Example with reload application" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:5 +msgid "The caller ID or number you're trying to call." msgstr "" -#: ../system/maintenance.rst:76 -msgid "" -"Message setting within Zammad's admin settings with ticket reload " -"application setting." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:7 +msgid "You can use wildcards for e.g. country specific outbound numbers like:" msgstr "" -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing the send message settings with ticket\n" -"reload application set" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:9 +msgid "``49*`` for Germany" msgstr "" -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing modal caused by maintenance's message\n" -"with reload application ticket" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:10 +msgid "``4930*`` for Berlin / Germany landlines" msgstr "" -#: ../system/monitoring.rst:2 -msgid "Monitoring" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 +msgid "``33*`` for France" msgstr "" -#: ../system/monitoring.rst:4 -msgid "" -"This function is only available in self hosted instances. If you use Zammad " -"in our cloud, we are monitoring the system on our own and take steps to fix " -"potential problems directly." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:15 +msgid "Set Outbound caller ID" msgstr "" -#: ../system/monitoring.rst:11 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:14 msgid "" -"On the monitoring page, you can see the current health state of Zammad under " -"\"*Current Status*\" at the bottom. This can be useful if you want to have a " -"look if everything is up and running. As an example, you could have a look " -"in the monitoring when you assume that some emails aren't processed from " -"Zammad." +"The outbound caller ID to set (the number your customer sees on his display) " +"in ``E.164`` number format." msgstr "" -#: ../system/monitoring.rst:17 -msgid "**Can't receive an email and the monitoring response is \"healthy\"?**" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 +msgid "Provide a short description for fellow administrators." msgstr "" -#: ../system/monitoring.rst:19 +#: ../system/integrations/cti/includes/generic-cti-support-note.includes.rst:3 msgid "" -"Zammad will just inform you about unprocessable emails. This is not the case " -"for oversized emails. You can adjust the maximum email size in :doc:`../" -"channels/email/settings`." +"This option requires your PBX to send a specific request to Zammad *before " +"dialing*. Please consult the :docs:`CTI API ` in case " +"you're not sure." msgstr "" -#: ../system/monitoring.rst:24 -msgid "Monitoring API" +#: ../system/integrations/cti/generic.rst:52 +#: ../system/integrations/cti/placetel.rst:54 +#: ../system/integrations/cti/sipgate.rst:59 +msgid "Other Settings" msgstr "" -#: ../system/monitoring.rst:26 +#: ../system/integrations/cti/includes/other-settings-intro.include.rst:1 msgid "" -"Beside the indication in the monitoring page, you can also use an external " -"monitoring tool to monitor Zammad's health. To request the health of Zammad, " -"you need to provide the API key (token) to the external monitoring tool. You " -"can copy the token from the \"*Current Token*\" field as well as the whole " -"API endpoint of your system (\"*Health Check*\" field), in which the API " -"token is already included." +"Below you can find all available additional settings for this CTI " +"integration. For your overview we're sorting them by appearance and " +"reference their description first." msgstr "" -#: ../system/monitoring.rst:37 -msgid "Screenshot showing Current Token and Health Check" +#: ../system/integrations/cti/includes/default-caller-id.include.rst:2 +#: ../system/integrations/cti/includes/default-caller-id.include.rst:1 +msgid "Default caller ID for outbound calls" msgstr "" -#: ../system/monitoring.rst:37 -msgid "Screenshot showing Token and Health Check" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:16 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:15 +msgid "Shown records in caller log" msgstr "" -#: ../system/monitoring.rst:39 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:2 msgid "" -"In addition to that, you can reset the auto-generated token to make sure " -"that already configured monitoring systems won't work anymore. So, please " -"use this \"*Reset*\" button only if you know what you do!" -msgstr "" - -#: ../system/monitoring.rst:44 -msgid "Example Output" -msgstr "" - -#: ../system/monitoring.rst:0 -msgid "No issues found" -msgstr "" - -#: ../system/monitoring.rst:48 ../system/monitoring.rst:60 -msgid "**Indicator in Zammad**:" -msgstr "" - -#: ../system/monitoring.rst:0 -msgid "Screenshot showing monitoring with no issues" -msgstr "" - -#: ../system/monitoring.rst:54 ../system/monitoring.rst:66 -msgid "**API response**::" -msgstr "" - -#: ../system/monitoring.rst:0 -msgid "Issues were found" +"Allows you to set the number of shown caller log entries for all users. You " +"can choose from the following values:" msgstr "" -#: ../system/monitoring.rst:0 -msgid "Screenshot showing monitoring with issues" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:5 +msgid "60 (default)" msgstr "" -#: ../system/objects.rst:2 -msgid "Objects" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:6 +msgid "120" msgstr "" -#: ../system/objects.rst:4 -msgid "" -"In Zammad you can add your own fields to tickets, users, organizations and " -"even groups (these are called \"objects\"). This can be useful if you need " -"to add further information to a ticket or any other object in Zammad and the " -"information doesn't fit in any existing field." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:7 +msgid "180" msgstr "" -#: ../system/objects.rst:11 -msgid "" -"Try to avoid deleting attributes (and disable them instead) as Zammad might " -"run into unexpected conditions if they are referenced somewhere." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:8 +msgid "240" msgstr "" -#: ../system/objects.rst:16 -msgid "" -"Here's an overview of object attributes. On the upper right you can add new " -"attributes. By default, there will be no custom fields - standard attributes " -"will be grayed out, you can't delete or change those. You can edit custom " -"attributes (they are displayed in black font and have a trash bin on the " -"right side) just by clicking on them." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:9 +msgid "300" msgstr "" -#: ../system/objects.rst:24 -msgid "" -"Attributes you add to Zammad, no matter if they have default values or not, " -"will not update existing information. This means a new ticket field " -"technically will be empty unless you populate it." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:11 +msgid "**🥵 Potential performance issue**" msgstr "" -#: ../system/objects.rst:28 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:13 msgid "" -"Especially in ticket scope this also means that newly added attributes will " -"be indicated as \"changed\" to agents that view the ticket. This may " -"interfere with Zammad's tabs behavior." +"Setting this setting higher than 60 may cause serious performance issues on " +"very busy instances. Keep in mind that this setting causes Zammad to poll " +"and send up to 300 records to *all active agent sessions* in very short time " +"periods." msgstr "" -#: ../system/objects.rst:40 -msgid "Ordering Attributes" +#: ../system/integrations/cti/generic.rst:73 +msgid "Caller Log Filter" msgstr "" -#: ../system/objects.rst:42 +#: ../system/integrations/cti/generic.rst:55 msgid "" -"Since Zammad introduced :doc:`/system/core-workflows` the need to have a " -"custom positioning for attributes has become more important than ever." +"This function allows you to provide call information based on e.g. queues " +"only to agents that really need the information." msgstr "" -#: ../system/objects.rst:45 +#: ../system/integrations/cti/generic.rst:58 msgid "" -"To adjust the position of such an attribute, simply click on the attribute " -"entry in question, scroll down and adjust the position number. Please note " -"that you cannot change the positioning of default attributes." +"Why? If you have a team for several countries or departments, you don't want " +"to bug your agents from other departments. Leaving these options empty will " +"fallback to showing everything to everyone." msgstr "" -#: ../system/objects.rst:49 -msgid "" -"In case two attributes have the same position value, Zammad will sort " -"alphabetically by name automatically." +#: ../system/integrations/cti/generic.rst:64 +msgid "Destination caller ID or Queue" msgstr "" -#: ../system/objects.rst:None +#: ../system/integrations/cti/generic.rst:63 msgid "" -"Screenshot showing custom attribute entries ordered in between default ones" +"This depends on your PBX and usually is either a queue ID, phone number or " +"extension." msgstr "" -#: ../system/objects.rst:56 -msgid "Updating Database After Adding or Editing Attributes" +#: ../system/integrations/cti/generic.rst:69 +msgid "Agents" msgstr "" -#: ../system/objects.rst:58 +#: ../system/integrations/cti/generic.rst:67 msgid "" -"When adding or changing attributes, Zammad will not apply the changes " -"instantly, but instead shows you the changed attributes first. If you're " -"ready to go, just click on \"Update database\" to apply the changes to " -"Zammad. If you made a mistake or just want to discard your changes, click " -"\"Discard changes\"." +"Select the agents that are responsible for the group. These agents will then " +"see caller log entries and call notifications fitting to said queue." msgstr "" -#: ../system/objects.rst:64 +#: ../system/integrations/cti/generic.rst:0 msgid "" -"After applying the changes with \"Update Database\", a restart of Zammad is " -"**mandatory**. If you don't perform it, you may experience unexpected " -"behavior or even errors. You may want to do this kind of configuration " -"during maintenance windows." +"Screenshot showing the caller log filter table with pre filled sample data" msgstr "" -#: ../system/objects.rst:72 +#: ../system/integrations/cti/includes/recent-logs.include.rst:6 msgid "" -"Changes on objects require you to update the database to apply these changes." -msgstr "" - -#: ../system/objects.rst:75 -msgid "**🤓 Service restarts can be automated**" -msgstr "" - -#: ../system/objects.rst:0 -msgid "Hosted environments automatically restart for you." +"With recent logs Zammad allows you to view the latest calls for the CTI " +"functionality. This usually comes in handy, when you're looking for errors." msgstr "" -#: ../system/objects.rst:0 +#: ../system/integrations/cti/includes/recent-logs.include.rst:0 msgid "" -"If you're using a self-hosted installation you can use :docs:`environment " -"variables `" -msgstr "" - -#: ../system/objects.rst:82 -msgid "System Attributes" +"Screenshot showing several incoming requests within Recent logs section." msgstr "" -#: ../system/objects.rst:84 -msgid "" -"Zammad comes with pre-configured attributes. Some of them can't be edited " -"via UI (or at all). This is required for proper operation of Zammad and not " -"a bug." +#: ../system/integrations/cti/includes/recent-logs.include.rst:16 +msgid "I'm just here to clear floats up." msgstr "" -#: ../system/objects.rst:90 -msgid "Ticket State" +#: ../system/integrations/cti/includes/recent-logs.include.rst:20 +msgid "" +"By clicking on the entry of interest, Zammad will provide more details on " +"the call in question. You'll see the payload it received and also the " +"response that was sent." msgstr "" -#: ../system/objects.rst:92 +#: ../system/integrations/cti/includes/recent-logs.include.rst:0 msgid "" -"If the pre-configured states aren't enough for you or you want to change " -"them, you can do so by clicking on the cogwheel icon in the state row in the " -"ticket tab. But you should be careful when changing pre-configured states. " -"This can lead to unwanted behavior in some cases." +"Screenshot showing detailed information of a specific log entry of recent " +"logs" msgstr "" -#: ../system/objects.rst:None -msgid "Screenshot showing highlighted ticket state attribute" +#: ../system/integrations/cti/includes/recent-logs.include.rst:31 +msgid "x" msgstr "" -#: ../system/objects.rst:122 -msgid "Handling of states" +#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 +#: ../system/integrations/cti/includes/troubleshooting.include.rst:9 +msgid "My Phone page stays blank, signalling does work..." msgstr "" -#: ../system/objects.rst:102 +#: ../system/integrations/cti/includes/troubleshooting.include.rst:5 msgid "" -"In the state configuration screen, you can add new states, disable states or " -"change states." +"If you've made sure that signalling works (check Recent logs) and your " +"Caller Log still stays empty, please ensure that you only configured one CTI " +"integration version. Specifically defining more than one agent mapping on " +"the different integration variants will be the issue." msgstr "" -#: ../system/objects.rst:0 -msgid "Screenshot showing table of default ticket states" +#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 +msgid "Clear the not needed agent mapping and reload your browser page." msgstr "" -#: ../system/objects.rst:110 +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:1 msgid "" -"To add a new state, click on the \"New Ticket State\" button in the top " -"right corner. To change an existing state, simply click on the affected " -"state. This opens an edit dialog." +"By mapping your agents extension to their existing Zammad users, Zammad can " +"provide a new ticket dialog or open the user profile for the agent that " +"picks up the call." msgstr "" -#: ../system/objects.rst:114 +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:5 msgid "" -"You can also clone a state or set them to \"Default for new tickets\" or " -"\"Default for follow-ups\" by clicking on the ⁝ action button and select the " -"desired function." +"This speeds up ticket aiding, no matter if it's for existing tickets or new " +"ones!" msgstr "" -#: ../system/objects.rst:118 +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:8 msgid "" -"*Default for new tickets* means that this state is used for every newly " -"created ticket." +"To see it work from the agent's perspective, have a look on :user-docs:`user " +"documentation `." msgstr "" -#: ../system/objects.rst:121 -msgid "" -"*Default for follow-ups* means that this state is used if the ticket is re-" -"opened after it was closed." +#: ../system/integrations/cti/placetel.rst:2 +msgid "Placetel CTI" msgstr "" -#: ../system/objects.rst:171 -msgid "Ticket state in detail" +#: ../system/integrations/cti/placetel.rst:16 +msgid "You need an administrative Placetel account for your organization." msgstr "" -#: ../system/objects.rst:125 +#: ../system/integrations/cti/placetel.rst:17 +#: ../system/integrations/cti/sipgate.rst:20 msgid "" -"Below you can find a description for each field and option. Please head over " -"to the :ref:`example ` to see the edit dialog." +"Your Zammad instance must be allowed to communicate to external services." msgstr "" -#: ../system/objects.rst:129 -msgid "" -"This is the name of the state and what you and your agents are seeing when " -"choosing a state somewhere (e.g. in tickets, trigger configuration)." +#: ../system/integrations/cti/placetel.rst:18 +msgid "Placetel must be able to reach your Zammad instance." msgstr "" -#: ../system/objects.rst:137 -msgid "" -"There are different state types you can choose from. By default, Zammad " -"comes with one state per state type." +#: ../system/integrations/cti/placetel.rst:22 +msgid ":doc:`provider-configurations/placetel`" msgstr "" -#: ../system/objects.rst:140 +#: ../system/integrations/cti/placetel.rst:21 msgid "" -"**new**: for states for tickets that are new and it hasn't been worked on " -"them" +"Learn how to configure Placetel to enable Zammad and Placetel to communicate " +"with each other." msgstr "" -#: ../system/objects.rst:142 +#: ../system/integrations/cti/placetel.rst:32 msgid "" -"**open**: for states for tickets that are in progress and agents are working " -"on them" -msgstr "" - -#: ../system/objects.rst:144 -msgid "**merged**: for states for tickets that are merged with other tickets" +"The here listed endpoint settings are relevant for the :doc:`integration " +"configuration with Placetel `." msgstr "" -#: ../system/objects.rst:145 -msgid "" -"**pending reminder**: for states for tickets that are in progress and you " -"want to set a reminder. (default example: *pending reminder*)" +#: ../system/integrations/cti/placetel.rst:37 +#: ../system/integrations/i-doit.rst:53 +msgid "Endpoint" msgstr "" -#: ../system/objects.rst:147 +#: ../system/integrations/cti/placetel.rst:36 msgid "" -"**pending action**: for states for tickets that are waiting for a specified " -"time and then change their state (default example: *pending close*)" +"This endpoint will be required for the Zammad integration within the " +"Placetel web interface." msgstr "" -#: ../system/objects.rst:150 -msgid "" -"**closed**: for states for tickets that are finished and do not need to be " -"processed further" +#: ../system/integrations/cti/placetel.rst:41 +msgid "API Token" msgstr "" -#: ../system/objects.rst:153 +#: ../system/integrations/cti/placetel.rst:40 msgid "" -"⚠️ Choosing the correct state type is important! If you are in doubt, have a " -"look on the default states and their types!" +"You'll receive this token within the ``Web API`` menu. Make sure to copy " +"this value, it's only shown once!" msgstr "" -#: ../system/objects.rst:158 -msgid "Ignore escalation" +#: ../system/integrations/cti/placetel.rst:71 +#: ../system/integrations/cti/sipgate.rst:77 +msgid "Phone Extension to Agent Mapping" msgstr "" -#: ../system/objects.rst:157 -msgid "" -"Here you can define whether tickets of this state will count to escalation " -"time or not." +#: ../system/integrations/cti/placetel.rst:0 +msgid "Screenshot showing sample user mappings in between Placetel and Zammad" msgstr "" -#: ../system/objects.rst:161 +#: ../system/integrations/cti/placetel.rst:64 msgid "" -"You can create a note for the state to inform other admins about the state. " -"This has no effect on tickets." +"You can find your agents Placetel username combination required within ⚙️ PBX " +"→ VoIP destinations. Within the \"Advanced settings\" section you're looking " +"for \"SIP user name\" and \"SIP server\"." msgstr "" -#: ../system/objects.rst:165 -msgid "Set the state to *active* or *inactive*." +#: ../system/integrations/cti/placetel.rst:68 +msgid "Combine these two like so: ``@``." msgstr "" -#: ../system/objects.rst:167 -msgid "" -"it is technically possible to set all states to inactive. To keep Zammad " -"working in such a case, the inactive flag of one of the states is ignored." +#: ../system/integrations/cti/placetel.rst:0 +msgid "Sample VoIP credentials for a Placetel user" msgstr "" -#: ../system/objects.rst:194 -msgid "Ticket state example" +#: ../system/integrations/cti/provider-configurations/placetel.rst:2 +msgid "Setup Placetel connection for Zammad" msgstr "" -#: ../system/objects.rst:174 +#: ../system/integrations/cti/provider-configurations/placetel.rst:6 msgid "" -"Let's assume we want to create a new state which indicates that the ticket " -"has to wait for a response of a third party (e.g. service contractor or " -"manufacturer) and we want to to be able to set a reminder." +"This configuration step requires a *full* administrative Placetel account. " +"You may receive forbidden error messages with Placetel in case your " +"permissions are not high enough." msgstr "" -#: ../system/objects.rst:178 +#: ../system/integrations/cti/provider-configurations/placetel.rst:10 msgid "" -"First we give the new state a proper name. In this example we call it " -"\"waiting for manufacturer\"." +"The following actions can be configured via the `Placetel web interface " +"`_." msgstr "" -#: ../system/objects.rst:181 -msgid "" -"As state type we choose \"pending reminder\". This indicates that the ticket " -"is still open and we can set a reminder. This reminder can be useful if our " -"manufacturer sometimes isn't responding or we want to remind him to give us " -"an answer." +#: ../system/integrations/cti/provider-configurations/placetel.rst:29 +msgid "Step 1: Activate Zammad integration" msgstr "" -#: ../system/objects.rst:186 +#: ../system/integrations/cti/provider-configurations/placetel.rst:14 msgid "" -"We choose \"no\" for \"ignore escalation\" because we want to escalate the " -"tickets even if we are waiting on the manufacturer's feedback." -msgstr "" - -#: ../system/objects.rst:189 -msgid "The **result** in the creation dialog will look like this:" +"Within Integrations, scroll down to Partner integrations and select Zammad." msgstr "" -#: ../system/objects.rst:0 -msgid "Screenshot showing ticket state creation dialog with example" +#: ../system/integrations/cti/provider-configurations/placetel.rst:17 +msgid "" +"You can alternatively filter by \"Ticket Systems\" to reduce the number of " +"entries on the page. You'll still want to look for Partner integrations. 🤓" msgstr "" -#: ../system/objects.rst:197 ../system/objects.rst:199 -msgid "Ticket Priority" +#: ../system/integrations/cti/provider-configurations/placetel.rst:21 +msgid "" +"Within the Zammad integration now press \"Activate\". A new tab ``API`` " +"becomes available - open this tab." msgstr "" -#: ../system/objects.rst:199 ../system/objects.rst:201 +#: ../system/integrations/cti/provider-configurations/placetel.rst:24 msgid "" -"If the pre-configured priorities aren't enough for you or you want to change " -"them, you can do so by clicking on the cogwheel icon in the priority row in " -"the ticket tab:" +"Now tick \"Enable Call Control / Notify API\" and paste the Placetel " +"endpoint from your Zammad instance into the field \"URL of your API " +"endpoint\". Save to apply the settings" msgstr "" -#: ../system/objects.rst:None -msgid "Screenshot showing highlighted ticket priority attribute" +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "Screencast showing how to activate the Zammad integration" msgstr "" -#: ../system/objects.rst:224 ../system/objects.rst:226 -msgid "Handling of priorities" +#: ../system/integrations/cti/provider-configurations/placetel.rst:51 +msgid "Step 2: Generate API Token for Placetel" msgstr "" -#: ../system/objects.rst:208 ../system/objects.rst:210 +#: ../system/integrations/cti/provider-configurations/placetel.rst:32 msgid "" -"In the priority configuration screen, you can add new priorities, disable " -"priorities or change priorities." +"Go back to the integrations page and scroll down to \"Web API\". Generate a " +"new API token by using the \"Create a new API token\" button." msgstr "" -#: ../system/objects.rst:0 -msgid "Screenshot showing table of default ticket priorities" +#: ../system/integrations/cti/provider-configurations/placetel.rst:37 +msgid "" +"If you already generated a token either use your existing token or reset it " +"by using above mentioned button. Placetel will ask you to conform this reset." msgstr "" -#: ../system/objects.rst:216 ../system/objects.rst:218 +#: ../system/integrations/cti/provider-configurations/placetel.rst:41 msgid "" -"To add a new priority, click on the \"New Priority\" button in the top right " -"corner. To change an existing priority, simply click on the affected " -"priority. This opens an edit dialog." +"Please keep in mind that existing API scripts may no longer work due to " +"token resets!" msgstr "" -#: ../system/objects.rst:220 ../system/objects.rst:222 +#: ../system/integrations/cti/provider-configurations/placetel.rst:44 msgid "" -"You can also clone a priority or set them to \"Default for new tickets\" by " -"clicking on the ⁝ action button and select the desired function." +"Copy the provided API token and insert it into the \"API Token\" field " +"within Zammad's Placetel integration." msgstr "" -#: ../system/objects.rst:223 ../system/objects.rst:225 +#: ../system/integrations/cti/provider-configurations/placetel.rst:47 msgid "" -"*Default for new tickets* means that this priority is used for every newly " -"created ticket." +"Apply your changes by using the \"Save\" button on the bottom of the " +"Placetel integration page and activate the Placetel integration." msgstr "" -#: ../system/objects.rst:246 ../system/objects.rst:248 -msgid "Priorities in detail" +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "" +"Screencast showing how to retrieve an API token from Placetel for Zammad" msgstr "" -#: ../system/objects.rst:227 ../system/objects.rst:229 -msgid "Below you can find a description for each field and option." +#: ../system/integrations/cti/provider-configurations/placetel.rst:73 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:77 +msgid "Step 3: Restrict the numbers to notify on" msgstr "" -#: ../system/objects.rst:230 ../system/objects.rst:232 +#: ../system/integrations/cti/provider-configurations/placetel.rst:54 msgid "" -"This is the name of the priority and what you and your agents are seeing " -"when choosing a priority somewhere (e.g. in tickets, trigger configuration)." +"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " +"the the Integrations page of the Placetel web interface, go to \"Notify " +"API\"." msgstr "" -#: ../system/objects.rst:240 ../system/objects.rst:242 -msgid "Highlight color" +#: ../system/integrations/cti/provider-configurations/placetel.rst:58 +msgid "" +"Lower on the page Placetel allows you to restrict the numbers to notify on. " +"You'll find this within the \"External routing API\" part." msgstr "" -#: ../system/objects.rst:235 ../system/objects.rst:237 +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 msgid "" -"Switch between *Low priority* (light blue), *High priority* (red) and - " -"(default). This affects the displayed color for ticket titles in overviews." +"Screenshot showing a sample selection of phone numbers to use for the " +"Placetels notify API" msgstr "" -#: ../system/objects.rst:239 ../system/objects.rst:241 -msgid "The color options are currently limited to the mentioned options." +#: ../system/integrations/cti/provider-configurations/placetel.rst:66 +msgid "" +"This menu point also provides a API request log from Placetel view. Just " +"open \"Recent responses of your API endpoint\" to learn more." msgstr "" -#: ../system/objects.rst:243 ../system/objects.rst:245 +#: ../system/integrations/cti/provider-configurations/placetel.rst:69 msgid "" -"You can create a note for the priority to inform other admins about the " -"priority. This has no effect on tickets." +"If you want to see Zammad's perspective, use the \"Recent Logs\" part from " +"within the Placetel integration page." msgstr "" -#: ../system/objects.rst:247 ../system/objects.rst:249 -msgid "Set the priority to *active* or *inactive*." +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "Screenshot showing sample log entries for Placetels API calls to Zammad" msgstr "" -#: ../system/objects/external-data-source-example.rst:2 -msgid "External Data Source" +#: ../system/integrations/cti/provider-configurations/placetel.rst:77 +msgid "Step 4 (optional): Further configurations for Placetel" msgstr "" -#: ../system/objects/external-data-source-example.rst:4 +#: ../system/integrations/cti/provider-configurations/placetel.rst:76 msgid "" -"We assume you already had a look on :doc:`types` where you can find a " -"description of the individual fields." +"If needed, you can now configure Zammad's Placetel integration in more " +"detail. You can learn more about your options here: :ref:`Placetel " +"integration settings `." msgstr "" -#: ../system/objects/external-data-source-example.rst:7 -msgid "" -"To reproduce this example, choose a category you want to add a custom field, " -"click on *New Attribute* and select *External data source field* under " -"*Format*." +#: ../system/integrations/cti/provider-configurations/sipgate.rst:2 +msgid "Setup Sipgate connection for Zammad" msgstr "" -#: ../system/objects/external-data-source-example.rst:11 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"Our example story is to fetch data from an external product database. We " -"want to add our products to the tickets so that the products can be searched " -"and chosen from a list and also create a link to the product website." -msgstr "" - -#: ../system/objects/external-data-source-example.rst:16 -msgid "Base configuration" -msgstr "" - -#: ../system/objects/external-data-source-example.rst:None -msgid "Initial steps to configure external data source object type" +"Sipgate has no english web interface which is why this documentation page is " +"mixing up languages badly." msgstr "" -#: ../system/objects/external-data-source-example.rst:23 -#: ../system/variables.rst:85 -msgid "**Example:**" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "" +"Please also note that the availability of API addons highly depends on your " +"package trier. Usage of sipgate.io packages *is not free*, please check " +"their `pricing page `_ before!" msgstr "" -#: ../system/objects/external-data-source-example.rst:25 -msgid "Name: *product*" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:35 +msgid "Step 1: Book sipgate.io package" msgstr "" -#: ../system/objects/external-data-source-example.rst:26 -msgid "Display: *Product*" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:13 +msgid "Skip to step 2 if you already have the package booked!" msgstr "" -#: ../system/objects/external-data-source-example.rst:29 -msgid "External data source configuration" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:15 +msgid "" +"Login to an administrative Sipgate account and navigate to " +"``Accountverwaltung``. You'll see several different options depending on " +"your booked packages. Select ``Verträge & Produkte`` to continue." msgstr "" -#: ../system/objects/external-data-source-example.rst:31 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:19 msgid "" -"First, enter the search URL making sure it contains ``#{search.term}`` as a " -"parameter:" +"Scroll down to the section ``Zusätzliche Produkte buchen`` and look for " +"``sipgate.io`` - select this product by using the ``Produkte anzeigen``-" +"Button." msgstr "" -#: ../system/objects/external-data-source-example.rst:34 -msgid "**Example:** ``https://dummyjson.com/products/search?q=#{search.term}``" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:23 +msgid "" +"On the next page select either one of the ``sipgate.io`` packages or ``Push-" +"API Package Free``. Follow the dialogue by booking the addon. You'll be " +"returned to your contract overview and now should see the selected addon in " +"your list." msgstr "" -#: ../system/objects/external-data-source-example.rst:36 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:30 msgid "" -"After that, head down to the preview section and enter a search input for " -"the external data source." +"The availability for ``sipgate.io`` packages and their levels highly depends " +"on the overall account type and product you've booked with Sipgate." msgstr "" -#: ../system/objects/external-data-source-example.rst:39 -msgid "**Example:** ``mac``" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "" +"Screencast showing the process on how to book the required sipgate.io addon" msgstr "" -#: ../system/objects/external-data-source-example.rst:41 -msgid "Then you can find a preview of the response data below:" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:52 +msgid "Step 2: Configure webhook for Zammad" msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of JSON response based on search term" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:38 +msgid "" +"Within your ``Accountverwaltung`` navicate to your product ``sipgate.io``. " +"In the newly opened tab, switch from \"Clients\" to \"Webhooks\" and paste " +"the endpoint URLs from your Zammad instance like so:" msgstr "" -#: ../system/objects/external-data-source-example.rst:48 -msgid "" -"We recommend using the preview to have a look on the structure. There is a " -"top-level element called ``products``. One level below, you can find the " -"attributes ``id`` and ``title``." +#: ../system/integrations/cti/provider-configurations/sipgate.rst:42 +msgid "Inbound endpoint to \"Incoming\"" msgstr "" -#: ../system/objects/external-data-source-example.rst:52 -msgid "**Search result response based on search from example:**" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:43 +msgid "Outbound endpoint to \"Outgoing\"" msgstr "" -#: ../system/objects/external-data-source-example.rst:119 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:47 msgid "" -"To tell the remote system that the desired data is located below the " -"``products`` level, you have to put it in the field *Search result list key*." +"Ensure to select at least one call group or phoneline within \"Sources\". " +"Other wise Sipgate will not indicate any incoming or outgoing calls to " +"Zammad." msgstr "" -#: ../system/objects/external-data-source-example.rst:122 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"After inserting ``products`` in the mentioned field, you get an extended " -"preview. You can find an additional box *Search result list* with a JSON " -"structure. This is the same response as before but stripped from the upper " -"``products`` element by the external data source." +"Screencast showing how to add Zammad's endpoint URLs to sipgate.ios webhook " +"configuration" msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of JSON response search result list" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:55 +msgid "" +"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " +"the Webhooks → URLs section of Sipgate you can select which *sources* " +"Sipgate should notify Zammad about in- and outgoing calls." msgstr "" -#: ../system/objects/external-data-source-example.rst:132 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:59 msgid "" -"Now you need to provide the keys for the search result values and labels. As " -"already mentioned, we are looking for the ``id`` and the ``title`` of our " -"products. If you haven't already, it is now a good time to look at the " -"preview of the *Search result list*." +"Use either specific phone lines or use the option \"Use for all phonelines " +"and groups\" to notify Zammad about all existing lines of your Sipgate " +"account." msgstr "" -#: ../system/objects/external-data-source-example.rst:197 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"After locating our two keys, we insert them in *search result value key* " -"(``id``) and in *Search result label key* (``title``)." +"Screenshot showing a sample selection of phone numbers to use for the " +"Sipgates webhooks API" msgstr "" -#: ../system/objects/external-data-source-example.rst:200 -msgid "" -"Basically, we configured the external data source already and we can see a " -"table in the preview section:" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:68 +msgid "This section also allows you to enable a Debug log." msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of product table based on search term" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "Screenshot showing an enabled Debug log option" msgstr "" -#: ../system/objects/external-data-source-example.rst:208 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:73 msgid "" -"According to our example story, now just the *Link template* is missing." +"After enabling you can use the Debug log section to see all sent webhook " +"calls to Zammad. You'll also can see the response." msgstr "" -#: ../system/objects/external-data-source-example.rst:210 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"Please note that this is an optional feature. If you don't want to use such " -"links, of course you don't have to configure it." +"Screenshot showing sample log entries for Sipgates webhook calls to Zammad" msgstr "" -#: ../system/objects/external-data-source-example.rst:213 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:81 +msgid "Step 4 (optional): Further configurations for Sipgate" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:80 msgid "" -"We can add now an address where additional product information can be found." +"If needed, you can now configure Zammad's Sipgate integration in more " +"detail. You can learn more about your options here: :ref:`Sipgate " +"integration settings `." msgstr "" -#: ../system/objects/external-data-source-example.rst:215 -msgid "Example: ``https://your_domain.com/q=#{ticket.product}``" +#: ../system/integrations/cti/sipgate.rst:2 +msgid "Sipgate (sipgate.io)" msgstr "" -#: ../system/objects/external-data-source-example.rst:217 -msgid "In the example, the parameter means:" +#: ../system/integrations/cti/sipgate.rst:16 +msgid "You need an administrative Sipgate account for your organization." msgstr "" -#: ../system/objects/external-data-source-example.rst:219 -msgid "``#{}``: \"Frame\" for the insertion of information" +#: ../system/integrations/cti/sipgate.rst:17 +msgid "" +"Zammad requires a ``sipgate.io`` addon from the feature store (please note " +"that API calls are not free with Sipgate. Rates may apply and differ from " +"account to account)." msgstr "" -#: ../system/objects/external-data-source-example.rst:220 -msgid "``ticket``: object level, where you create your custom object" +#: ../system/integrations/cti/sipgate.rst:21 +msgid "Sipgate must be able to reach your Zammad instance." msgstr "" -#: ../system/objects/external-data-source-example.rst:221 -msgid "``product``: name of the (custom) object" +#: ../system/integrations/cti/sipgate.rst:25 +msgid ":doc:`provider-configurations/sipgate`" msgstr "" -#: ../system/objects/external-data-source-example.rst:223 +#: ../system/integrations/cti/sipgate.rst:24 msgid "" -"After configuring your *Link template*, there will be another column in the " -"preview. Hovering on the icons in the *Link* column will show you where it " -"forwards you." +"Learn how to configure Sipgate to enable Zammad and Sipgate to communicate " +"with each other." msgstr "" -#: ../system/objects/external-data-source-example.rst:232 +#: ../system/integrations/cti/sipgate.rst:33 msgid "" -"In our example, one of the links looks like: https://your_domain.com/q=6, " -"where the 6 is the product id." +"Below endpoint settings affect the :doc:`sipgate.io configuration `." msgstr "" -#: ../system/objects/external-data-source-example.rst:235 -msgid "You can find more information regarding the URL in :doc:`types`." +#: ../system/integrations/cti/sipgate.rst:37 +msgid "This endpoint is required for incoming call hooks." msgstr "" -#: ../system/objects/includes/adding-values-hint.include.rst:3 -msgid "" -"Adding values can be tricky for first timers, don't forget to press \"➕ " -"Add\" after typing your values. Otherwise you may loose a value." +#: ../system/integrations/cti/sipgate.rst:40 +msgid "This endpoint is required for outgoing call hooks." msgstr "" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:1 -#: ../system/objects/includes/reposition-values.include.rst:1 -msgid "**↕️ This field type allows the positioning of its values ↔️**" +#: ../system/integrations/cti/sipgate.rst:0 +msgid "Screenshot showing sample user mappings in between Sipgate and Zammad" msgstr "" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:3 +#: ../system/integrations/cti/sipgate.rst:69 msgid "" -"In order to re-arrange the field values, first edit the field. Then you can " -"use ☰ to drag the values in question to the correct position. If you want to " -"change the layer depth, double click on ☰. With it you can cycle through the " -"available layers." +"You can find your agent's Sipgate username within ``Accountverwaltung → " +"Benutzer``. You're looking for the SIP-ID." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:0 +msgid "Sample VoIP credentials for a Sipgate user" msgstr "" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:8 -msgid "When you're ready, submit your changes to save the object attribute." +#: ../system/integrations/cti/sipgate.rst:77 +msgid "Users with several devices also have several SIP-IDs." msgstr "" -#: :0 ../system/objects/types.rst:0 -msgid "" -"Screencast showing how to re-position values on tree select like\n" -"fields" +#: ../system/integrations/elasticsearch.rst:2 +msgid "Elasticsearch (SaaS)" msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:3 +#: ../system/integrations/elasticsearch.rst:4 msgid "" -"In order to re-arrange the field values, edit the field and scroll below the " -"values. Make sure to tick the option \"Use custom option sort\"." +"The Elasticsearch integration allows you to create a read-only user to use " +"with your favorite reporting tool (e.g. like Grafana)." msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:8 +#: ../system/integrations/elasticsearch.rst:7 msgid "" -"If you do not tick this field, all manual positioning you did above will be " -"lost upon saving! ☠️" +"If you want to take full advantage of the Zammad reporting, have a look at " +"our :docs:`Grafana ` " +"setup page as well." msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:11 -msgid "" -"Now use ☰ to drag the values in question to the correct position. When " -"you're ready, submit your changes to save the object attribute." +#: ../system/integrations/elasticsearch.rst:11 ../system/subscription.rst:7 +msgid "**🚧 Hosted environment specific 🚧**" msgstr "" -#: :0 ../system/objects/types.rst:0 -msgid "Screencast showing how to re-position values" +#: ../system/integrations/elasticsearch.rst:13 +msgid "" +"This integration is only available for Hosted setups. In order to use " +"Elasticsearch you'll need the **Plus** subscription." msgstr "" -#: ../system/objects/includes/url-template-hint.include.rst:3 +#: ../system/integrations/elasticsearch.rst:16 msgid "" -"This field allows using :ref:`URL fields (Link Templates) `." +"Self hosted users have all the control over their self hosted Elasticsearch " +"instances." msgstr "" -#: ../system/objects/permissions.rst:2 -#, fuzzy -msgid "Attribute Permissions" -msgstr "Verze" +#: ../system/integrations/elasticsearch.rst:None +msgid "Elasticsearch integration page on SaaS environments" +msgstr "" -#: ../system/objects/permissions.rst:7 +#: ../system/integrations/elasticsearch.rst:27 msgid "" -"In the object attributes configuration you can define if a field is shown " -"and if the input in the field is mandatory, separated by different screens " -"and for different :doc:`roles/permissions `." +"Please note the following limitations of Elasticsearch access on hosted " +"environments:" msgstr "" -#: ../system/objects/permissions.rst:17 -msgid "Screenshot shows object attribute permission table" +#: ../system/integrations/elasticsearch.rst:30 +msgid "access to the Elasticsearch index is read-only access" msgstr "" -#: ../system/objects/permissions.rst:17 -msgid "" -"Some of the possible permissions and screen options for a user object " -"attribute." +#: ../system/integrations/elasticsearch.rst:31 +msgid "currently you're limited to user only" msgstr "" -#: ../system/objects/permissions.rst:19 +#: ../system/integrations/elasticsearch.rst:32 msgid "" -"Based on the object context (ticket, agent, organization, user), the " -"selectable roles (to be precise: the required permissions) and screens " -"differ. Be aware that these settings aren't affecting data creation via " -"other channels than the UI." +"Reporting tools that require to write into the indexes (like Kibana) are not " +"supported" msgstr "" -#: ../system/objects/permissions.rst:24 -msgid "" -"If you want to have further customization possibilities, you should have a " -"look at the :doc:`core workflows `." +#: ../system/integrations/elasticsearch.rst:34 +msgid "IP access restriction is currently not yet supported" msgstr "" -#: ../system/objects/permissions.rst:28 -msgid "Screens" +#: ../system/integrations/elasticsearch.rst:37 +msgid "Activating Elasticsearch Access" msgstr "" -#: ../system/objects/permissions.rst:30 +#: ../system/integrations/elasticsearch.rst:39 msgid "" -"In the table below you can find an overview about the different permissions " -"and the available screens Zammad distinguishes between." +"By default external access to your Elasticsearch index is not active. You " +"can enable the integration at any time if needed." msgstr "" -#: ../system/objects/permissions.rst:37 -msgid "Screen" +#: ../system/integrations/elasticsearch.rst:42 +msgid "" +"Please ensure to note down the password provided - you won't have access to " +"it afterwards." msgstr "" -#: ../system/objects/permissions.rst:38 -msgid "Available for" +#: ../system/integrations/elasticsearch.rst:None +msgid "Screencast showing activation of Elasticsearch integration" msgstr "" -#: ../system/objects/permissions.rst:40 -msgid "create" +#: ../system/integrations/elasticsearch.rst:51 +msgid "Connection Settings" msgstr "" -#: ../system/objects/permissions.rst:41 ../system/objects/permissions.rst:52 -#: ../system/objects/permissions.rst:59 ../system/objects/permissions.rst:73 -msgid "admin.user" +#: ../system/integrations/elasticsearch.rst:53 +msgid "" +"This section holds the most important general information for accessing your " +"Elasticsearch indexes - such as:" msgstr "" -#: ../system/objects/permissions.rst:42 ../system/objects/permissions.rst:53 -#: ../system/objects/permissions.rst:60 -msgid "admin.organization" +#: ../system/integrations/elasticsearch.rst:57 +msgid "A unique subdomain that does not tell your real instance URL." msgstr "" -#: ../system/objects/permissions.rst:43 ../system/objects/permissions.rst:54 -#: ../system/objects/permissions.rst:61 -msgid "admin.group" +#: ../system/integrations/elasticsearch.rst:61 +msgid "Software" msgstr "" -#: ../system/objects/permissions.rst:44 -msgid "Creation dialog for not yet existing data" +#: ../system/integrations/elasticsearch.rst:60 +msgid "" +"The major version of the search index being used. This is required by some " +"Reporting tools like Grafana." msgstr "" -#: ../system/objects/permissions.rst:45 -msgid "create_middle" +#: ../system/integrations/elasticsearch.rst:64 +msgid "Authentication" msgstr "" -#: ../system/objects/permissions.rst:46 ../system/objects/permissions.rst:50 -#: ../system/objects/permissions.rst:57 ../system/objects/permissions.rst:66 -#: ../system/objects/permissions.rst:70 -msgid "ticket.customer" +#: ../system/integrations/elasticsearch.rst:64 +msgid "The authentication type being supported. ``Basic Authentication``" msgstr "" -#: ../system/objects/permissions.rst:47 ../system/objects/permissions.rst:51 -#: ../system/objects/permissions.rst:58 ../system/objects/permissions.rst:69 -msgid "ticket.agent" +#: ../system/integrations/elasticsearch.rst:67 +msgid "Available Indexes" msgstr "" -#: ../system/objects/permissions.rst:48 -msgid "Ticket create dialog (middle section)" +#: ../system/integrations/elasticsearch.rst:69 +msgid "" +"Within this section we're displaying the -in our opinion- most important " +"indexes for a Zammad instance." msgstr "" -#: ../system/objects/permissions.rst:49 -msgid "edit" +#: ../system/integrations/elasticsearch.rst:72 +msgid "" +"If you require all indexes or our listing is not good enough for you, point " +"your browser to the URL we're providing and append ``/_aliases?" +"pretty=true``. The result should look like this: ``https://.zammad.com/" +"_aliases?pretty=true``." msgstr "" -#: ../system/objects/permissions.rst:55 -msgid "Editing dialog for already existing data" +#: ../system/integrations/elasticsearch.rst:77 +msgid "" +"Your browser will automatically ask for your credentials - you'll then see " +"something like this:" msgstr "" -#: ../system/objects/permissions.rst:56 -msgid "view" +#: ../system/integrations/elasticsearch.rst:125 +msgid "Credentials" msgstr "" -#: ../system/objects/permissions.rst:62 -msgid "View-only dialog for already existing data" +#: ../system/integrations/elasticsearch.rst:127 +msgid "" +"Within this section Zammad displays your available users. The password is " +"provided once (upon activation) and cannot be retrieved after that." msgstr "" -#: ../system/objects/permissions.rst:64 -msgid "(e.g. user or organization from search)" +#: ../system/integrations/elasticsearch.rst:131 +msgid "" +"If you need to change or reset your Elasticsearch user password, use the " +"\"Reset password\" button in the credentials table. Doing so creates a brand " +"new password for the account in question. This change is immediate, keep in " +"mind that this may affect third party tools connected to your instance." msgstr "" -#: ../system/objects/permissions.rst:65 -msgid "signup" +#: ../system/integrations/exchange.rst:2 +msgid "Exchange" msgstr "" -#: ../system/objects/permissions.rst:67 -msgid "Sign-up screen for new customers" +#: ../system/integrations/exchange.rst:4 +msgid "" +"With Zammad's Exchange integration, you can easily use existing address " +"books without having to update more than one source." msgstr "" -#: ../system/objects/permissions.rst:68 -msgid "invite_customer" +#: ../system/integrations/exchange.rst:7 +msgid "" +"However, you should refrain from syncing all addresses, as the results may " +"not be what you expect (Exchange collects huge amounts of addresses). A " +"central address book of your company to sync makes more sense, as you can " +"ensure that Zammad gets only the data you need and want. Apart from this, it " +"is even not possible to sync the Global Address List (GAL) of your Exchange " +"system with Zammad." msgstr "" -#: ../system/objects/permissions.rst:71 +#: ../system/integrations/exchange.rst:16 msgid "" -"Customer invitation screen (from :doc:`First Steps ` area)" +"**Exchange and LDAP:** The exchange sync can be overruled by Zammad's LDAP " +"integration. If you have the same users in both sources, the LDAP version " +"will always be Zammad's pick." msgstr "" -#: ../system/objects/permissions.rst:72 -msgid "invite_agent" +#: ../system/integrations/exchange.rst:19 +msgid "" +"**One way sync:** the Exchange sync is one way. Exchange => Zammad. Changes " +"to your users inside of Zammad might be overwritten by the Exchange sync." msgstr "" -#: ../system/objects/permissions.rst:74 +#: ../system/integrations/exchange.rst:24 msgid "" -"Agent invitation screen (from :doc:`First Steps ` area)" +"To configure Exchange integration, simply go to the System > Integrations > " +"Exchange in the admin panel. Press \"change\" and follow the wizard for " +"adding the needed Exchange information to Zammad. On the last two steps " +"Zammad will ask you for the address book(s) and your desired attribute " +"mapping. By default, Zammad only maps email address, first- and lastname. " +"Technically, you can map any Exchange object to a Zammad user object (this " +"also works for custom objects!)." msgstr "" -#: ../system/objects/permissions.rst:78 -msgid "Screen Options" +#: ../system/integrations/exchange.rst:35 +msgid "" +"If the SSL verification fails while connecting to Exchange, Zammad will ask " +"you to turn it off temporarily." msgstr "" -#: ../system/objects/permissions.rst:80 +#: ../system/integrations/exchange.rst:38 msgid "" -"For the different screens you can select \"show\" and \"required\" options." +"Please be aware that **turning off SSL verification is a security risk**. It " +"should only be used temporarily or for testing purposes. If turned off, " +"there is no verification of the certificate, which means that every " +"presented certificate will be accepted." msgstr "" -#: ../system/objects/permissions.rst:82 -msgid "**shown:** Show (check) or hide (uncheck) a field." +#: ../system/integrations/exchange.rst:43 +msgid "" +"After pressing Continue, Zammad will check if the configuration is okay. You " +"can then enable Exchange and start your first sync. The sync will then run " +"hourly - if you need to change mappings or the address book(s), you can " +"change the configuration at any time." msgstr "" -#: ../system/objects/permissions.rst:83 +#: ../system/integrations/exchange.rst:50 msgid "" -"**required:** Set a field to mandatory (check). Forces users (via UI and " -"API) to populate the field." +"After the sync has finished, you can find the new Exchange contacts under " +"\"Users\". Zammad integrates them just as normal users." msgstr "" -#: ../system/objects/types.rst:7 -msgid "Example external data source" +#: ../system/integrations/exchange.rst:55 +msgid "" +"In some cases you might see unique IDs as \"Login\" instead of the email " +"address. This is normal and doesn't affect the login or email mapping for " +"that entry." +msgstr "" + +#: ../system/integrations/github.rst:4 +msgid "" +"Use GitHub integration to track GitHub issues directly within Zammad " +"tickets. Add issue hyperlinks and get a live summary of metadata like status " +"(open/closed), assignee, labels, and more." msgstr "" -#: ../system/objects/types.rst:2 -msgid "Attribute types" +#: ../system/integrations/github.rst:8 +msgid "Please note that our GitHub integration does not support pull requests." msgstr "" -#: ../system/objects/types.rst:4 -msgid "" -"When adding a new object attribute, you can choose between the following " -"attribute types." +#: ../system/integrations/github.rst:None +msgid "Integration page for GitHub" msgstr "" -#: ../system/objects/types.rst:14 +#: ../system/integrations/github.rst:18 msgid "" -"You cannot change the attribute format / type as soon as it is applied. If " -"you no longer need an object attribute, consider disabling it instead of " -"removing." +"In your GitHub settings, create a new API token under **Developer settings > " +"Personal access tokens > Generate new token**. Leave the **Scopes** section " +"empty." msgstr "" -#: ../system/objects/types.rst:18 -msgid "**What about the translation of my attributes?**" +#: ../system/integrations/github.rst:0 ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to create a new API token" msgstr "" -#: ../system/objects/types.rst:20 -msgid "" -"For some attribute types you can decide if they should be translatable or " -"not. To be precise, it works only for the selectable fields because the " -"possible choices are known and limited. For the following attribute types, " -"you can set the translatable flag:" +#: ../system/integrations/github.rst:27 +msgid "Create a new API key with no scopes/privileges." msgstr "" -#: ../system/objects/types.rst:25 -msgid "*Boolean field*" +#: ../system/integrations/github.rst:29 +msgid "🔒 **Will this work for private repos?**" msgstr "" -#: ../system/objects/types.rst:26 -msgid "*Single selection field*" +#: ../system/integrations/github.rst:31 +msgid "" +"No. To link private repo issues, **use the** ``repo`` **scope instead**. " +"Bear in mind that the resulting token will have `lots of permissions that it " +"doesn't actually need `_, which presents a security risk if your token ever falls into " +"the wrong hands." msgstr "" -#: ../system/objects/types.rst:27 -msgid "*Multiple selection field*" +#: ../system/integrations/github.rst:37 +msgid "" +"Unfortunately, because of how GitHub's OAuth token scopes are set up, this " +"is the only way to link issues on private repos." msgstr "" -#: ../system/objects/types.rst:28 -msgid "*Single tree selection field*" +#: ../system/integrations/github.rst:40 +msgid "Enter your new API token in Zammad and enable GitHub integration." msgstr "" -#: ../system/objects/types.rst:29 -msgid "*Multiple tree selection field*" +#: ../system/integrations/github.rst:0 +msgid "Screencast showing how to configure Zammad's GitHub integration" msgstr "" -#: ../system/objects/types.rst:31 +#: ../system/integrations/github.rst:47 msgid "" -"For these types, you can find an additional field *Translate field contents*:" +"Use the default API endpoint (``https://api.github.com/graphql``) unless " +"you're using GitHub Enterprise Server." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Screenshot showing translatable attribute types" +#: ../system/integrations/github.rst:50 +msgid "" +"Once completed, a new GitHub issues tab will appear in the ticket pane. 🎉" msgstr "" -#: ../system/objects/types.rst:38 -msgid "Screenshot with example of translatable attribute type" +#: ../system/integrations/github.rst:59 ../system/integrations/gitlab.rst:52 +msgid "Token verification is taking a long time" msgstr "" -#: ../system/objects/types.rst:45 -msgid "Boolean field" +#: ../system/integrations/github.rst:56 ../system/integrations/gitlab.rst:49 +msgid "" +"Slight delays are normal (<2 min.), especially for systems under heavy load." msgstr "" -#: ../system/objects/types.rst:41 +#: ../system/integrations/github.rst:58 msgid "" -"Provides a drop-down field with display values for ``true`` and ``false``. " -"Setting a default is mandatory." +"Self-hosted administrators, please check your network settings to ensure " +"that your Zammad server can reach ``api.github.com``." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Boolean fields" +#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 +msgid "I reloaded the page and now the API token is gone" msgstr "" -#: ../system/objects/types.rst:55 -msgid "Date field" +#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 +msgid "" +"This may indicate that Zammad is still verifying your API token. Try " +"reloading the page again in a couple minutes." msgstr "" -#: ../system/objects/types.rst:48 -msgid "Provides a date picker field and does not allow default values." +#: ../system/integrations/gitlab.rst:2 +msgid "GitLab" msgstr "" -#: ../system/objects/types.rst:52 -msgid "Default time diff (hours)" +#: ../system/integrations/gitlab.rst:4 +msgid "" +"Use GitLab integration to track GitLab issues directly within Zammad " +"tickets. Add issue hyperlinks and get a live summary of metadata like status " +"(open/closed), assignee, labels, and more." msgstr "" -#: ../system/objects/types.rst:51 +#: ../system/integrations/gitlab.rst:8 msgid "" -"This setting helps the user by highlighting the day from now plus the " -"provided value. It *does not* pre-fill the field." +"Please note that our GitLab integration does not support merge requests." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Date fields" +#: ../system/integrations/gitlab.rst:None +msgid "Integration page for GitLab" msgstr "" -#: ../system/objects/types.rst:73 -msgid "Date & time field" +#: ../system/integrations/gitlab.rst:18 +msgid "" +"In your GitLab preferences, create a new API token under **Access Tokens**." msgstr "" -#: ../system/objects/types.rst:58 -msgid "Provides a date and time picker – does not allow default values" +#: ../system/integrations/gitlab.rst:20 +msgid "Under **Select scopes**, choose ``read_api`` only." msgstr "" -#: ../system/objects/types.rst:62 -msgid "Allow future" +#: ../system/integrations/gitlab.rst:27 +msgid "🔒 **If you wish to link issues on any private repos...**" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Forbid dates and times in the future." +#: ../system/integrations/gitlab.rst:29 +msgid "Your API token must belong to an account with access to those repos." msgstr "" -#: ../system/objects/types.rst:66 -msgid "Allow past" +#: ../system/integrations/gitlab.rst:31 +msgid "Enter your new API token in Zammad and enable GitLab integration." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Forbid dates and times in the past." +#: ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to configure Zammad's GitLab integration" msgstr "" -#: ../system/objects/types.rst:70 -msgid "Default time diff (minutes)" +#: ../system/integrations/gitlab.rst:40 +msgid "" +"Use the default API endpoint (``https://gitlab.com/api/graphql``) unless " +"you're a self-hosted GitLab user." msgstr "" -#: ../system/objects/types.rst:69 +#: ../system/integrations/gitlab.rst:43 msgid "" -"This setting helps the user by highlighting the day from now plus the " -"provided value. It does not pre-fill the field." +"Once completed, a new GitLab issues tab will appear in the ticket pane. 🎉" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Date & time fields" +#: ../system/integrations/gitlab.rst:51 +msgid "" +"Self-hosted administrators, please check your network settings to ensure " +"that your Zammad server can reach ``gitlab.com``." msgstr "" -#: ../system/objects/types.rst:86 -msgid "Integer field" +#: ../system/integrations/i-doit.rst:2 +msgid "i-doit" msgstr "" -#: ../system/objects/types.rst:76 +#: ../system/integrations/i-doit.rst:4 msgid "" -"Provides an input field that allows integer usage only. You may define a " -"default value. You cannot enforce comma separation." +"`i-doit `_ is an open-source **configuration " +"management database** - in other words, a tool for keeping tabs on every " +"single piece of your physical and digital infrastructure, from network " +"equipment to virtual machines on down to the faceplates on your rack shelves " +"and more." msgstr "" -#: ../system/objects/types.rst:80 -msgid "Minimal" +#: ../system/integrations/i-doit.rst:10 +msgid "" +"What's that got to do with Zammad? Well, if you used tickets to track issues " +"with all that hardware, you might start wishing there was a way they could " +"talk to each other." msgstr "" -#: ../system/objects/types.rst:80 -msgid "The minimal value the field accepts." +#: ../system/integrations/i-doit.rst:14 +msgid "Zammad gives you two:" msgstr "" -#: ../system/objects/types.rst:83 -msgid "Maximal" +#: ../system/integrations/i-doit.rst:17 +msgid "1. Add i-doit Links to Zammad Tickets" msgstr "" -#: ../system/objects/types.rst:83 -msgid "The maximum value the field accepts." +#: ../system/integrations/i-doit.rst:20 ../system/integrations/i-doit.rst:80 +msgid "What Users See" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Integer fields" +#: ../system/integrations/i-doit.rst:26 +msgid "i-doit integration in Zammad's ticket pane" msgstr "" -#: ../system/objects/types.rst:99 -msgid "Multiple selection field" +#: ../system/integrations/i-doit.rst:26 +msgid "" +"The i-doit integration will appear under a new 🖨 tab in the ticket pane." msgstr "" -#: ../system/objects/types.rst:89 +#: ../system/integrations/i-doit.rst:28 msgid "" -"Provides a selection field that allows the selection of one or more out of " -"several. This field does allow setting a default value." +"i-doit integration puts a new tab in Zammad's ticket pane where you can add " +"links to existing i-doit devices for easy reference. (See our :user-docs:" +"`user documentation ` to learn " +"how it works in practice)." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Multiple selection fields" +#: ../system/integrations/i-doit.rst:36 ../system/integrations/i-doit.rst:93 +msgid "How to Set it Up" msgstr "" -#: ../system/objects/types.rst:112 -msgid "Single selection field" +#: ../system/integrations/i-doit.rst:38 +msgid "" +"It requires i-doit's `API Add-on `_. Make sure to have it properly set up. Use the following setting:" msgstr "" -#: ../system/objects/types.rst:102 +#: ../system/integrations/i-doit.rst:42 +msgid "Active: ``Yes``" +msgstr "" + +#: ../system/integrations/i-doit.rst:43 +msgid "Enforce authentication by username and password: ``No``" +msgstr "" + +#: ../system/integrations/i-doit.rst:45 msgid "" -"Provides a drop-down field that allows selection of one value out of " -"several. This field does allow setting a default value." +"To set it up, enable the integration in the Zammad admin panel under " +"**System > Integrations > i-doit**:" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Single selection fields" +#: ../system/integrations/i-doit.rst:None +msgid "i-doit settings within the integration pages" msgstr "" -#: ../system/objects/types.rst:142 -msgid "Textarea field" +#: ../system/integrations/i-doit.rst:53 +msgid "The root URL of your i-doit installation." msgstr "" -#: ../system/objects/types.rst:115 -msgid "" -"Provides a text area input field (multiple lines) and thus allows e.g. new " -"lines. You can set a default field value." +#: ../system/integrations/i-doit.rst:62 +msgid "API token" msgstr "" -#: ../system/objects/types.rst:120 +#: ../system/integrations/i-doit.rst:56 msgid "" -"Please note that this field *does not* support text formatting or HTML " -"content (rich text)." +"Found in the i-doit admin panel under **Interfaces / external data > JSON-" +"RPC API > Common Settings**." +msgstr "" + +#: ../system/integrations/i-doit.rst:0 +msgid "i-doit administration interface with API configuration" msgstr "" -#: ../system/objects/types.rst:123 -msgid "**🥵 This field can consume a lot of visual space**" +#: ../system/integrations/i-doit.rst:67 +msgid "Client ID" msgstr "" -#: ../system/objects/types.rst:125 -msgid "" -"Depending on where you use this field type, it may use a lot of visual space " -"if you provide a lot of text. This may be an issue to work with." +#: ../system/integrations/i-doit.rst:65 +msgid "A unique name to identify Zammad within i-doit." msgstr "" -#: ../system/objects/types.rst:130 -msgid "Default" +#: ../system/integrations/i-doit.rst:67 +msgid "(Zammad does not require you to enter a value here, but i-doit might!)" msgstr "" -#: ../system/objects/types.rst:129 +#: ../system/integrations/i-doit.rst:70 msgid "" -"The here provided text will be shown within the text area field or new data " -"sets." +"Here you can decide if the certificate of your i-doit system has to be " +"verified or not. In case you are using custom certificates, please have a " +"look at :doc:`how to add them to Zammad `." msgstr "" -#: ../system/objects/types.rst:134 ../system/objects/types.rst:160 -msgid "Maxlength" +#: ../system/integrations/i-doit.rst:77 +msgid "2. List / Create Zammad Tickets in i-doit" msgstr "" -#: ../system/objects/types.rst:0 ../system/objects/types.rst:160 -msgid "You can pick the maximum length of the field." +#: ../system/integrations/i-doit.rst:None +msgid "Zammad integration in i-doit's device view" msgstr "" -#: ../system/objects/types.rst:0 -msgid "The default length of this object is ``500``." +#: ../system/integrations/i-doit.rst:86 +msgid "" +"i-doit's ticket system integration gives you a way to see all the tickets " +"for a given device without ever leaving i-doit. (See our :user-docs:`user " +"documentation ` to learn how it " +"works in practice)." msgstr "" -#: ../system/objects/types.rst:139 -msgid "Rows" +#: ../system/integrations/i-doit.rst:95 +msgid "" +"Enable this integration in the i-doit admin panel under **Interfaces / " +"external data > Trouble Ticket System (TTS) > Configuration**:" msgstr "" -#: ../system/objects/types.rst:0 -msgid "" -"Change the number of rows to dislay so that you can use only the space you " -"really need." +#: ../system/integrations/i-doit.rst:None +msgid "i-doit administration interface with TTS configuration" msgstr "" -#: ../system/objects/types.rst:0 -msgid "The default number of rows is ``4``." +#: ../system/integrations/i-doit.rst:104 +msgid "TTS-Type" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Textarea fields" +#: ../system/integrations/i-doit.rst:104 +msgid "``Zammad``" msgstr "" -#: ../system/objects/types.rst:165 -msgid "Text field" +#: ../system/integrations/i-doit.rst:115 +msgid "Username / Password" msgstr "" -#: ../system/objects/types.rst:145 -msgid "Provides a text field (one line) and allows choosing a default value." +#: ../system/integrations/i-doit.rst:107 +msgid "Login credentials for a Zammad agent." msgstr "" -#: ../system/objects/types.rst:148 +#: ../system/integrations/i-doit.rst:109 msgid "" -"Defines the type of the input field. This allows e.g. your browser to ensure " -"that you provide the specific type." +"This agent must have **read permission** for all :doc:`groups ` that plan on using the i-doit integration." msgstr "" -#: ../system/objects/types.rst:152 -msgid "Currently available:" +#: ../system/integrations/i-doit.rst:113 +msgid "" +"You may even wish to create a dedicated agent account just for this " +"integration (otherwise, if the agent ever changes her password, you will " +"have to remember to update it here)." msgstr "" -#: ../system/objects/types.rst:155 -msgid "Phone" +#: ../system/integrations/i-doit.rst:117 +msgid "URL incl. protocol" msgstr "" -#: ../system/objects/types.rst:156 -msgid "Text" +#: ../system/integrations/i-doit.rst:118 +msgid "``https://your.zammad.domain``" msgstr "" -#: ../system/objects/types.rst:157 -msgid "Url *(URL fields disable link-template availability)*" +#: ../system/integrations/index.rst:2 +msgid "Integrations" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Text fields" +#: ../system/integrations/index.rst:4 +msgid "" +"Zammad offers numerous integrations that add rich features to your instance." msgstr "" -#: ../system/objects/types.rst:174 -msgid "Single tree selection field" +#: ../system/integrations/index.rst:6 +msgid "We're still working on this part of our documentation, stay tight!" msgstr "" -#: ../system/objects/types.rst:168 +#: ../system/integrations/index.rst:10 +msgid "Integrations for Phone Systems" +msgstr "" + +#: ../system/integrations/index.rst:14 msgid "" -"Provides a select-like field with up to 6 layers of options. Does not allow " -"setting a default value." +"Your VoIP provider or telephony system is not listed? Possibly your provider " +"supports Zammad by using the generic CTI - if you're unsure ask your " +"provider." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Tree Select fields" +#: ../system/integrations/index.rst:18 +msgid "" +"Provider does not support Zammad? Consider creating a `feature request in " +"the Zammad Community `_." msgstr "" -#: ../system/objects/types.rst:183 -msgid "Multiple tree selection field" +#: ../system/integrations/index.rst:31 +msgid "Integrations for Authentication and Customers" msgstr "" -#: ../system/objects/types.rst:177 -msgid "" -"Provides a select-like field with up to 6 layers of options allowing the " -"selection of multiple values. Does not allow setting a default value." +#: ../system/integrations/index.rst:44 +msgid "Integrations for Monitoring Systems" msgstr "" -#: ../system/objects/types.rst:302 -msgid "External Data Source field" +#: ../system/integrations/index.rst:46 +msgid "This section currently misses the following integrations:" msgstr "" -#: ../system/objects/types.rst:186 -msgid "" -"Provides a searchable field which fetches data from an external system. This " -"can be useful if you have data outside of Zammad and don't want to maintain " -"both data sources." +#: ../system/integrations/index.rst:48 +msgid "Icinga" msgstr "" -#: ../system/objects/types.rst:190 -msgid "The feature works as follows:" +#: ../system/integrations/index.rst:49 +msgid "Monit" msgstr "" -#: ../system/objects/types.rst:192 -msgid "" -"Zammad sends a query with a search string (free text from agent or based on " -"a variable) in a pre-defined format (\"Search URL\") to an external system." +#: ../system/integrations/index.rst:50 +msgid "Nagios" msgstr "" -#: ../system/objects/types.rst:195 -msgid "" -"This external system searches for matches and provides a response as a JSON " -"structure to Zammad." +#: ../system/integrations/index.rst:60 +msgid "Integrations for Issue Trackers" msgstr "" -#: ../system/objects/types.rst:197 -msgid "" -"Zammad just looks for the defined list and value keys, reads the content and " -"displays the value to the user. There is no search on Zammad side." +#: ../system/integrations/index.rst:70 +msgid "Other Integrations" msgstr "" -#: ../system/objects/types.rst:201 +#: ../system/integrations/index.rst:72 msgid "" -"The usage of a PostgreSQL database for Zammad is required. In any other " -"case, Zammad will hide the external data source type and you are not able to " -"use it. If you want to use this feature, consider to :docs:`migrate your " -"database `." +"This section will hold any other integration that can't be grouped up (yet)." msgstr "" -#: ../system/objects/types.rst:205 -msgid "Currently, only ``GET`` is supported as request method." +#: ../system/integrations/ldap/index.rst:2 +msgid "LDAP / Active Directory" msgstr "" -#: ../system/objects/types.rst:206 +#: ../system/integrations/ldap/index.rst:4 msgid "" -"The data structure must be in JSON format and provide the objects in an " -"array." +"Zammad comes with a powerful LDAP integration that allows you to have a " +"single source of truth. By this you reduce the number of login credentials " +"your user has to remember." msgstr "" -#: ../system/objects/types.rst:208 +#: ../system/integrations/ldap/index.rst:10 msgid "" -"The endpoint for the external data source has to support search. On Zammad " -"side, there is no search/logic implemented; however, you can define the " -"output key and value based on the result(s) from the response (which " -"provides already filtered content based on the search)." +"The LDAP source is also a perfect candidate for Zammad's :docs:`Kerberos " +"Single Sign-On ` but also works as addition " +"to other :doc:`/settings/security/third-party`." msgstr "" -#: ../system/objects/types.rst:212 -msgid "" -"If you receive more results as expected, your external data source search " -"may not work properly or the structure of the URL is not correct. You should " -"get in touch with a responsible person from the external system." +#: ../system/integrations/ldap/index.rst:None +msgid "Zammands LDAP management page" msgstr "" -#: ../system/objects/types.rst:217 -msgid "" -"Please have a look :doc:`at our example `, where you can find a possible configuration for a public " -"dummy endpoint." +#: ../system/integrations/ldap/index.rst:25 +msgid "📝 :doc:`manage`" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for external data source fields" +#: ../system/integrations/ldap/index.rst:25 +msgid "Add, modify, remove or re-arrange your LDAP-Sources as needed." msgstr "" -#: ../system/objects/types.rst:242 -msgid "Search URL" +#: ../system/integrations/ldap/index.rst:30 +msgid "Before you continue, please note the following limitations." msgstr "" -#: ../system/objects/types.rst:227 -msgid "" -"Set your endpoint where Zammad fetches the data. Please make sure to include " -"a valid search :doc:`variable <../variables>` as an URL parameter. Example " -"for a free text search at user input: ``#{search.term}``" +#: ../system/integrations/ldap/index.rst:32 +msgid "Mapping / Synchronizing organizations is not possible" msgstr "" -#: ../system/objects/types.rst:232 +#: ../system/integrations/ldap/index.rst:36 msgid "" -"If in doubt, ask the responsible person for the external data source how " -"they expect the strucuture of the URL." +"You may want to consider using domain based assignments to overcome this " +"issue. Learn more on :doc:`/manage/organizations/index`." msgstr "" -#: ../system/objects/types.rst:236 +#: ../system/integrations/ldap/index.rst:39 msgid "" -"Depending on your search variable, the preview might work or not. The reason " -"is that the context might not be available and it is no bug." +"Zammad's LDAP sync is one way. Editing user settings or permissions may be " +"overwritten upon the next sync depending on your configuration." msgstr "" -#: ../system/objects/types.rst:239 -msgid "" -"Please also make sure to use a variable which is available in your object " -"context. For example you won't be able to search for a ticket in a user " -"object context." +#: ../system/integrations/ldap/index.rst:41 +msgid "Nested groups are not supported." msgstr "" -#: ../system/objects/types.rst:252 -msgid "SSL Verification" +#: ../system/integrations/ldap/index.rst:42 +msgid "Synchronizing user avatars from LDAP is not supported." msgstr "" -#: ../system/objects/types.rst:245 -msgid "Here you can switch the SSL verification to no." +#: ../system/integrations/ldap/index.rst:43 +msgid "Unlike user filters, group filters cannot be changed." msgstr "" -#: ../system/objects/types.rst:249 +#: ../system/integrations/ldap/index.rst:44 msgid "" -"If your external data source system is using self signed certificates, " -"please have a look :doc:`here ` for " -"further information about how to handle them in Zammad, so you can keep the " -"SSL verification activated." +"When a user originates from an LDAP server, Zammad will try to verify the " +"login credentials against LDAP first - if this fails Zammad will check its " +"local database." +msgstr "" + +#: ../system/integrations/ldap/index.rst:50 +msgid "" +"Users can have local passwords even if they're LDAP users! You can learn " +"more about user accounts in general on :doc:`/manage/users/index`." msgstr "" -#: ../system/objects/types.rst:258 -msgid "HTTP Authentication" +#: ../system/integrations/ldap/index.rst:54 +msgid "" +"When several LDAP sources contain the same user (meaning the same email " +"address), the user in question will be updated with every source configured. " +"*The last LDAP source will win.*" msgstr "" -#: ../system/objects/types.rst:255 +#: ../system/integrations/ldap/index.rst:58 msgid "" -"If your external data source requires an authentication, you can set it " -"here. You can leave it empty or choose between *Basic Authentication* or " -"*Authentication Token* (selecting one of the two methods leads to additional " -"fields where you can enter your credentials/token)." +"This is subject to change with `Issue 4109 `_ in the future." msgstr "" -#: ../system/objects/types.rst:265 -msgid "Search result list key" +#: ../system/integrations/ldap/index.rst:60 +msgid "" +"Synchronization statistics currently affect *all* configured LDAP sources. " +"This also applies for newly added or updated sources." msgstr "" -#: ../system/objects/types.rst:261 +#: ../system/integrations/ldap/index.rst:63 msgid "" -"Defines the level in the JSON structure which provides the list with search " -"results. You can leave it empty, if the data is already provided as an " -"array. If you have to go deeper in the structure, you can provide a path " -"with ``.`` as separators, e.g. ``key.subkey.sub-sub-key``." +"This is subject to change with `Issue 4108 `_ in the future." msgstr "" -#: ../system/objects/types.rst:271 -msgid "Search result value key" +#: ../system/integrations/ldap/index.rst:65 +msgid "" +"Zammad currently has limited fallback server support. You can workaround " +"this by providing several sources - however, ensure to have the exact same " +"configuration on your fallback." msgstr "" -#: ../system/objects/types.rst:268 +#: ../system/integrations/ldap/index.rst:69 msgid "" -"Defines the attribute in the structure in which your external data source " -"provides the *value* for your data. An example would be a product *number*. " -"If you have to go deeper in the structure, you can provide a path with ``.`` " -"as separators, e.g. ``key.subkey.sub-sub-key``." +"This is subject to improve with `Issue 4107 `_ in the future." msgstr "" -#: ../system/objects/types.rst:277 -msgid "Search result label key" +#: ../system/integrations/ldap/index.rst:76 +msgid "" +"This section holds all requests Zammad handled for all LDAP sources. These " +"entries can either contain synchronization information or logins " +"(authentication attempts via Zammad's login interface)." msgstr "" -#: ../system/objects/types.rst:274 +#: ../system/integrations/ldap/index.rst:80 msgid "" -"Defines the attribute in the structure in which your external data source " -"provides the *label* for your data. An example would be a product *name*. If " -"you have to go deeper in the structure, you can provide a path with ``.`` as " -"separators, e.g. ``key.subkey.sub-sub-key``." +"By clicking on any request, Zammad will provide even more information. The " +"provided information can be useful when something does not work as expected." msgstr "" -#: ../system/objects/types.rst:280 +#: ../system/integrations/ldap/index.rst:85 msgid "" -"In the preview area, you can find the following items (depending on your " -"configuration above):" +"Especially a LDAP synchronization can cause many log entries. The web " +"interface will always limit the number of shown entries to the last 50 " +"entries." msgstr "" -#: ../system/objects/types.rst:283 +#: ../system/integrations/ldap/index.rst:None msgid "" -"**Error/hint message** (only if configuration is not complete): Zammad tells " -"you, if there is a problem and what you should change in your configuration." +"Screencast showing LDAP integration log entries and a detail view on\n" +"an entry." msgstr "" -#: ../system/objects/types.rst:286 -msgid "" -"**Search field**: search for an existing attribute in the data source to get " -"a preview. This is required for the fields below to show up." +#: ../system/integrations/ldap/manage.rst:2 +msgid "Manage LDAP-Sources" msgstr "" -#: ../system/objects/types.rst:288 +#: ../system/integrations/ldap/manage.rst:6 msgid "" -"**Search result response** (only if configuration is not complete): here you " -"can find a syntax highlighted JSON preview of the response, based on the " -"search term you entered." +"Please keep in mind all current limitations for the LDAP synchronization. " +"This will help to understand scopes of the following operations better." msgstr "" -#: ../system/objects/types.rst:291 -msgid "" -"**Search result list** (only if *search result list key* is properly set): " -"output of the structure under the configured *search result list key*." +#: ../system/integrations/ldap/manage.rst:65 +msgid "Add new source" msgstr "" -#: ../system/objects/types.rst:294 +#: ../system/integrations/ldap/manage.rst:10 msgid "" -"**Preview table** (when fully configured): Zammad shows you a table which " -"includes the found items based on the search string (value, label and " -"optional link). You can use this preview if you don't have the complete data " -"structure of the external system in mind." +"Using the *New Source* button allows you to add new LDAP sources to your " +"installation. You're not limited in the number of sources, however, keep in " +"mind that many sources will also take more time to synchronize." msgstr "" -#: ../system/objects/types.rst:299 +#: ../system/integrations/ldap/manage.rst:14 msgid "" -"An example of a configured external data source field from agent perspective:" +"You can choose between different encryption types, namely *SSL* and " +"*STARTTLS* or none of them (\"*No SSL*\"). If you choose *SSL* or " +"*STARTTLS*, Zammad will display an additional *SSL verification* option that " +"allows you to disable the verification, e.g. for self-signed SSL " +"certificates. You can also tell Zammad to use a different port by appending " +"``:`` to your hostname/IP." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Screencast showing the search for a product in a ticket" +#: ../system/integrations/ldap/manage.rst:0 +msgid "" +"Screenshot of configuring a new LDAP source with SSL encryption and SSL " +"verification" msgstr "" -#: ../system/objects/types.rst:307 -msgid "URL fields (Link-Template)" +#: ../system/integrations/ldap/manage.rst:26 +msgid "" +"New Source with SSL transport security enabled and certificate verification" msgstr "" -#: ../system/objects/types.rst:311 +#: ../system/integrations/ldap/manage.rst:30 msgid "" -"This function is restricted to Text, Select and External data source types " -"only." +"Using an user filter can be a good idea if you only require a small subset " +"of your LDAP users in Zammad." msgstr "" -#: ../system/objects/types.rst:314 -msgid "" -"Link-Templates are an amazing way to dynamically generate URLs. They allow " -"you to integrate other systems better without having to manually copy data " -"from Zammad if possible." +#: ../system/integrations/ldap/manage.rst:42 +msgid "This especially affects inactive users" msgstr "" -#: ../system/objects/types.rst:320 +#: ../system/integrations/ldap/manage.rst:34 msgid "" -"Another great way of communicating with another system may be Zammad's :doc:" -"`Webhooks `." +"As every LDAP behaves differently on which attributes and how they are set, " +"Zammad doesn't care about any flags." msgstr "" -#: ../system/objects/types.rst:323 +#: ../system/integrations/ldap/manage.rst:37 msgid "" -"After filling a link-template enabled field, an URL icon will appear on its " -"right. Clicking on the icon opens a new tab." +"Users that no longer are returned by your LDAP source will automatically be " +"set to inactive. Zammad assumes that the user was deactivated." msgstr "" -#: ../system/objects/types.rst:328 +#: ../system/integrations/ldap/manage.rst:41 msgid "" -"Even though Zammad displays the link template within object edit and create " -"screens, the function is optional. It's only active if you populate the " -"field." +"Users will never be removed automatically! If you want to remove obsolete " +"users, use :doc:`/system/data-privacy`." msgstr "" -#: ../system/objects/types.rst:333 -msgid "" -"What's the difference between URL and text fields with link template...?!" +#: ../system/integrations/ldap/manage.rst:46 +msgid "Active Directory admins" msgstr "" -#: ../system/objects/types.rst:335 +#: ../system/integrations/ldap/manage.rst:45 msgid "" -"Both fields have different use cases. Use ``text`` type text fields when " -"ever you have a *static* url that requires dynamic parameters. If you " -"require a drag & drop like field that you can put in any URL, use ``URL`` " -"type text fields." +"Active Directories are quite specific on how to filter for active users only " +"- please see the `Microsoft documentation `_ for more " +"information." msgstr "" -#: ../system/objects/types.rst:340 +#: ../system/integrations/ldap/manage.rst:51 msgid "" -"The difference is easier to spot when comparing the fields directly, below " -"screencast shows the result - the dynamic approach uses existing values in " -"the moment of updating to built the URL - e.g. ``https://google.com/search?" -"q=cookies`` - while the URL approach uses the actual URL of the field - e.g. " -"``https://zammad.com``." +"*Do not* manually write pathes of either LDAP attributes or groups. If " +"Zammad does not display them, it either cannot find them or you have a lot " +"of users that don't have the attributes populated." msgstr "" -#: ../system/objects/types.rst:None +#: ../system/integrations/ldap/manage.rst:55 msgid "" -"Screencast showing the differents in between URL and text type fields with " -"actual values" +"Zammad will always only return attributes that are filled - this reduces the " +"returned list of attributes greatly." msgstr "" -#: ../system/objects/types.rst:352 -msgid "How does this work...?!" +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing how to add a new LDAP source" msgstr "" -#: ../system/objects/types.rst:354 +#: ../system/integrations/ldap/manage.rst:63 msgid "" -"As an example, let's say you have an attribute called ``amazing_attribute`` " -"and you want to open a google search directly with the input from that field." +"If your LDAP system doesn't allow anonymous bind, Zammad detects it and " +"provides you an editable \"Base DN\" *text* field instead of a prefilled " +"*select* field." msgstr "" -#: ../system/objects/types.rst:357 -msgid "" -"Providing the link-template field below allows you to do so: ``https://www." -"google.com/search?q=#{ticket.amazing_attribute}``" +#: ../system/integrations/ldap/manage.rst:81 +msgid "Review or edit existing source" msgstr "" -#: ../system/objects/types.rst:362 +#: ../system/integrations/ldap/manage.rst:68 msgid "" -"You can use any :doc:`Zammad variable ` as long as it's " -"available in the moment you need it." +"Clicking on a LDAP source will provide a configuration and mapping overview." msgstr "" -#: ../system/objects/types.rst:365 +#: ../system/integrations/ldap/manage.rst:70 msgid "" -"As a result, you are redirected to Google with a search for the value of the " -"attribute, if you click on the button in the ticket (as you can see in the " -"screencast above)." -msgstr "" - -#: ../system/packages.rst:2 -msgid "Packages" +"If needed you can then use the *Change* button to update either the name, " +"active state or the whole configuration. If you're changing the whole " +"configuration, the dialogue will be identical to the source creation." msgstr "" -#: ../system/packages.rst:4 -msgid "That's the package management-area." +#: ../system/integrations/ldap/manage.rst:76 +msgid "" +"Did your LDAP server change? Different LDAP servers have different " +"structures and default attributes. This causes the LDAP synchronization to " +"likely fail. Consider removing the affected source and re-add it." msgstr "" -#: ../system/packages.rst:6 -msgid "Individual add-ons for Zammad can be installed and managed here." +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing the update of the source name." msgstr "" -#: ../system/sessions.rst:2 -msgid "Sessions" +#: ../system/integrations/ldap/manage.rst:89 +msgid "Re-arrange LDAP source's order" msgstr "" -#: ../system/sessions.rst:4 +#: ../system/integrations/ldap/manage.rst:84 msgid "" -"Sessions management allows reviewing currently known user sessions and " -"allows to end these. The session timeout is affected by :ref:" -"`security_session_timeout` configurations from security settings." +"You can change the synchronization order for each source at any time. Zammad " +"will synchronize the sources from top to bottom." msgstr "" -#: ../system/sessions.rst:None -msgid "Screenshot showing Zammad's session management" +#: ../system/integrations/ldap/manage.rst:0 +msgid "" +"Screencasting showing how to change the source order by using\n" +"drag and drop." msgstr "" -#: ../system/sessions.rst:13 -msgid "Zammad will provide the following information:" +#: ../system/integrations/ldap/manage.rst:101 +msgid "Remove a source" msgstr "" -#: ../system/sessions.rst:16 +#: ../system/integrations/ldap/manage.rst:92 msgid "" -"The user account this session entry belongs to. It can be normal if a user " -"has several sessions in the list. This can be due to changed browser " -"information or if you use e.g. single sign on methods where the user does " -"not use the log off button." +"If you no longer need the a LDAP source or simply want to start over, you " +"can remove them at any time. This will not remove synchronized users, data " +"synchronized or permissions." msgstr "" -#: ../system/sessions.rst:22 -msgid "Browser" +#: ../system/integrations/ldap/manage.rst:98 +msgid "" +"Not sure if you'd need the source later on? Set the source to inactive " +"instead of removing it - see *Review or edit existing source* for more." msgstr "" -#: ../system/sessions.rst:22 -msgid "The browser agent communicated to Zammad." +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing how to remove LDAP sources." msgstr "" -#: ../system/sessions.rst:40 -msgid "Location" +#: ../system/integrations/pgp/index.rst:2 +msgid "PGP" msgstr "" -#: ../system/sessions.rst:25 +#: ../system/integrations/pgp/index.rst:7 msgid "" -"The anticipated location based on the users IP address. Depending on the IP " -"address the result shown may differ. This option depends on :doc:`/settings/" -"system/services`." +"Pretty Good Privacy (PGP) is another method for secure email communication. " +"With PGP, you can exchange **signed** and **encrypted** messages with others." msgstr "" -#: ../system/sessions.rst:29 -msgid "The following information can be shown:" +#: ../system/integrations/pgp/index.rst:13 +#: ../system/integrations/smime/index.rst:17 +msgid "Signing" msgstr "" -#: ../system/sessions.rst:33 -msgid "IP address" +#: ../system/integrations/pgp/index.rst:11 +msgid "is a proof that a message hasn't been manipulated on its way." msgstr "" -#: ../system/sessions.rst:32 +#: ../system/integrations/pgp/index.rst:13 msgid "" -"Either if you set *Geo IP services* to inactive or you're using internal IP " -"address which do not provide location information." +"In other words, it guarantees message **integrity** and **authenticity**." msgstr "" -#: ../system/sessions.rst:40 -msgid "Country (or Country + City)" +#: ../system/integrations/pgp/index.rst:19 +#: ../system/integrations/smime/index.rst:22 +msgid "Encryption" msgstr "" -#: ../system/sessions.rst:36 +#: ../system/integrations/pgp/index.rst:16 +#: ../system/integrations/smime/index.rst:20 msgid "" -"If *Geo IP services* is enabled only. Depends on how detailed the available " -"IP address information are." +"scrambles a message so that it can only be unscrambled by the intended " +"recipient." msgstr "" -#: ../system/sessions.rst:39 +#: ../system/integrations/pgp/index.rst:19 msgid "" -"Be aware that results can be inaccurate - this technically is not an error." +"In other words, it guarantees message **privacy** and **data security**." msgstr "" -#: ../system/sessions.rst:43 -msgid "Age" +#: ../system/integrations/pgp/index.rst:25 +msgid "Screenshot of ticket creation with encrypt and sign buttons" msgstr "" -#: ../system/sessions.rst:43 -msgid "Provides the time when the session initially has been created." +#: ../system/integrations/pgp/index.rst:25 +msgid "" +"Once PGP has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " +"appear in the ticket composer." msgstr "" -#: ../system/sessions.rst:50 -msgid "Update" +#: ../system/integrations/pgp/index.rst:28 +msgid "**Sign button not visible?**" msgstr "" -#: ../system/sessions.rst:46 +#: ../system/integrations/pgp/index.rst:30 msgid "" -"Provides the time the user used this session to open Zammad. This timestamp " -"is only updated if the user e.g. reloads, not during normal work on tickets." +"Please note that the signing of emails is based on the outgoing email " +"account. That means you have to choose a group with a sender email account, " +"which has a private key assigned." msgstr "" -#: ../system/sessions.rst:50 -msgid "This timestamp is being used for the session timeout." +#: ../system/integrations/pgp/index.rst:35 +msgid "Handling of Keys" msgstr "" -#: ../system/sessions.rst:53 +#: ../system/integrations/pgp/index.rst:36 msgid "" -"Use the delete button to remove a single session on behalf of your user." -msgstr "" - -#: ../system/subscription/billing.rst:2 -msgid "Billing" +"To use the PGP function, you have to enable the integration (PGP) by " +"switching the toggle to *enabled*." msgstr "" -#: ../system/subscription/billing.rst:4 +#: ../system/integrations/pgp/index.rst:39 msgid "" -"Within the billing tab you can control all billing relevant information like " -"invoices, billing address and the option to cancel your subscription." +"You can add keys by clicking the *add key* button. The keys can be imported " +"from a file or you can paste the content of the key in the text box." msgstr "" -#: ../system/subscription/billing.rst:33 -msgid "Billing information" +#: ../system/integrations/pgp/index.rst:42 +msgid "**Which keys do I have to import?**" msgstr "" -#: ../system/subscription/billing.rst:8 +#: ../system/integrations/pgp/index.rst:44 msgid "" -"All adjusted billing information below only affect future invoices. If your " -"invoice was issued wrong, please contact `our sales team `_." +"For **signing** *outgoing* emails, you have to import the private key of " +"your Zammad email account." msgstr "" -#: ../system/subscription/billing.rst:14 -msgid "Billing address" +#: ../system/integrations/pgp/index.rst:47 +msgid "" +"For **encrypting** *outgoing* emails, you have to import the public key of " +"the customer's email account." msgstr "" -#: ../system/subscription/billing.rst:13 +#: ../system/integrations/pgp/index.rst:50 msgid "" -"Provide your company address here, make sure to include the companies name " -"in case required. This address will be referenced on your invoice." +"For **verifying the signature** of signed *incoming* emails, you have to " +"import the public key of the customer." msgstr "" -#: ../system/subscription/billing.rst:18 -msgid "VAT ID" +#: ../system/integrations/pgp/index.rst:53 +msgid "" +"For **decrypting** of encrypted *incoming* emails, you have to import the " +"private key of your Zammad email account." msgstr "" -#: ../system/subscription/billing.rst:17 -msgid "" -"Provide your VAT ID here. If applicable your invoice will not contain German " -"VAT. Please make sure to pay the VAT in your country as required." +#: ../system/integrations/pgp/index.rst:57 +msgid "Import Keys From a File" msgstr "" -#: ../system/subscription/billing.rst:27 -msgid "Billing Email Address" +#: ../system/integrations/pgp/index.rst:58 +msgid "You can import keys from a file in the section **Upload key**:" msgstr "" -#: ../system/subscription/billing.rst:21 -msgid "" -"Usually the instance owner (the person that registered the instance) will " -"receive all emails including the invoices. In case you have your own billing " -"department, you can provide their email address here." +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of adding a key via file" msgstr "" -#: ../system/subscription/billing.rst:25 +#: ../system/integrations/pgp/index.rst:64 msgid "" -"All billing relevant information will then be sent to this email address." +"**Supported file formats:** ASCII-armor as well as binary GPG format " +"(basically any GPG supported key format) is supported here." msgstr "" -#: ../system/subscription/billing.rst:27 -msgid "Invoices are sent as attachment (PDF) to this email address." +#: ../system/integrations/pgp/index.rst:68 +msgid "Import Keys by Pasting the Content" msgstr "" -#: ../system/subscription/billing.rst:29 -msgid "" -"Don't forget to press the *Submit* button after you changed above settings." +#: ../system/integrations/pgp/index.rst:69 +msgid "You can also paste the key's content in the section **paste key**:" msgstr "" -#: ../system/subscription/billing.rst:0 -msgid "" -"Screenshot showing options for billing information within the\n" -"subscription menu" +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of adding a key via pasting" msgstr "" -#: ../system/subscription/billing.rst:70 -msgid "Payment history" +#: ../system/integrations/pgp/index.rst:75 +msgid "" +"**Supported format:** Please note that only ASCII-armor is supported here." msgstr "" -#: ../system/subscription/billing.rst:36 -msgid "" -"The payment history will display a history of all paid invoices. At this " -"point you can also download these in case you need them again." +#: ../system/integrations/pgp/index.rst:78 +msgid "Deleting Keys" msgstr "" -#: ../system/subscription/billing.rst:41 +#: ../system/integrations/pgp/index.rst:79 msgid "" -"You will only find *paid* invoices here. Invoices that are to be billed are " -"not available before the payment is completed." +"If you want to delete a specific key, you can do it by clicking on the menu " +"in the *actions* column and select **delete**:" msgstr "" -#: ../system/subscription/billing.rst:46 -msgid "Date" +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of deleting a key" msgstr "" -#: ../system/subscription/billing.rst:46 -msgid "Date of the invoice creation." +#: ../system/integrations/pgp/index.rst:88 +msgid "Downloading Keys" msgstr "" -#: ../system/subscription/billing.rst:49 -msgid "Amount" +#: ../system/integrations/pgp/index.rst:89 +msgid "" +"If you want to download your keys, you can do this as well via corresponding " +"action buttons. Depending on the key, you can choose wether you want to " +"download the private or the public key." msgstr "" -#: ../system/subscription/billing.rst:49 -msgid "Invoice total including VAT if applicable." +#: ../system/integrations/pgp/index.rst:95 +#: ../system/integrations/smime/manage-certificates.rst:76 +msgid "Default Behavior" msgstr "" -#: ../system/subscription/billing.rst:52 +#: ../system/integrations/pgp/index.rst:96 msgid "" -"Contains contract period (monthly or yearly) and hosted plan for the " -"subscription period in question." +"Here you can adjust on per group basis, if *sign* and *encryption* is on or " +"off by default. Please be aware, that agents can always override the setting " +"for each individual article." msgstr "" -#: ../system/subscription/billing.rst:63 -msgid "Payment method / Service period" +#: ../system/integrations/pgp/index.rst:None +msgid "Adjusting default behavior on per group basis" msgstr "" -#: ../system/subscription/billing.rst:56 +#: ../system/integrations/pgp/index.rst:107 msgid "" -"Used bank account or credit card as well as the subscription period the " -"invoice is about." +"Here you can see the last actions regarding signing and encryption and if " +"they were successful." msgstr "" -#: ../system/subscription/billing.rst:61 -msgid "" -"It might happen that the invoice date and subscription period differ. This " -"is nothing to worry about, the subscription periods will be accounted later " -"on." +#: ../system/integrations/pgp/index.rst:117 +msgid "**Sign button is not visible, but keys are imported.**" msgstr "" -#: ../system/subscription/billing.rst:67 -msgid "Receipt" +#: ../system/integrations/pgp/index.rst:115 +msgid "Did you choose a group in the ticket?" msgstr "" -#: ../system/subscription/billing.rst:66 +#: ../system/integrations/pgp/index.rst:116 msgid "" -"Use the arrow to download the invoice in question. You can download all " -"available invoices any time you need to here!" -msgstr "" - -#: ../system/subscription/billing.rst:0 -msgid "Screenshot showing payment history of a hosted instance" +"Did you import a private key for the email adress, which is used for " +"outgoing emails in the group?" msgstr "" -#: ../system/subscription/billing.rst:94 -msgid "Do you want to cancel your subscription?" +#: ../system/integrations/pgp/index.rst:122 +msgid "**How to obtain keys?**" msgstr "" -#: ../system/subscription/billing.rst:73 +#: ../system/integrations/pgp/index.rst:120 msgid "" -"In case you no longer want to use Zammad's SaaS, you can cancel your " -"subscription by using the red *Yes, please cancel my subscription* button." +"You can create them yourself! There are some good tutorials on the web on " +"how to create them. Providing keys to Zammad is a prerequisite to use the " +"PGP feature." msgstr "" -#: ../system/subscription/billing.rst:76 -msgid "" -"Your subscription will end the day after your trial or billing period ends." +#: ../system/integrations/pgp/index.rst:127 +msgid "**It says a passphrase is needed, but I haven't got one.**" msgstr "" -#: ../system/subscription/billing.rst:80 +#: ../system/integrations/pgp/index.rst:125 msgid "" -"We will remind you about your cancelled subscription several times up front. " -"After the subscription ended all instance data will be removed. A restore " -"*is not* possible after that point!" -msgstr "" - -#: ../system/subscription/billing.rst:0 -msgid "Screencast showing how to cancel a subscription" +"If the key is secured with a passphrase, you have to provide it for the " +"import in Zammad. It is possible that keys may have an empty passphrase. " +"However, this is *not* recommended." msgstr "" -#: ../system/subscription/billing.rst:87 -msgid "**😖 Cancelled by accident?**" +#: ../system/integrations/pgp/index.rst:132 +msgid "**How do my customers get my new key?**" msgstr "" -#: ../system/subscription/billing.rst:89 +#: ../system/integrations/pgp/index.rst:130 msgid "" -"You can always undo the cancellation via the *Yes, undo the cancellation of " -"my subscription* button up to the last subscription day!" +"You have to provide your **public** key in advance. Your customer also has " +"to configure PGP in their email workflow and import your public key. The " +"other way round, you have to get the public key of your customer and have to " +"import it to Zammad." msgstr "" -#: ../system/subscription/billing.rst:0 -msgid "" -"Screenshot showing a red button to cancel the subscription\n" -"cancellation" +#: ../system/integrations/slack.rst:2 +msgid "Slack" msgstr "" -#: ../system/subscription/index.rst:2 -msgid "Subscription (SaaS)" +#: ../system/integrations/slack.rst:4 +msgid "**⚠️ Deprecation warning ⚠️**" msgstr "" -#: ../system/subscription/index.rst:4 +#: ../system/integrations/slack.rst:6 msgid "" -"The subscription settings page allows you to configure your instances " -"package and number of agents required." +"Zammad 7 will no longer support this dedicated Slack integration. It is " +"recommended to switch to :doc:`pre-defined webhooks ` instead. Existing Slack integrations should " +"be migrated manually before this feature is dropped." msgstr "" -#: ../system/subscription/index.rst:9 +#: ../system/integrations/slack.rst:14 msgid "" -"This setting section is only available for Hosted setups. If you're looking " -"for on premise support contracts, please see the `Zammad pricing page " -"`_." +"In order to use this feature, please add a new Slack app to your Workspace. " +"The App you need is called ``Incoming WebHooks`` ." +msgstr "" + +#: ../system/integrations/slack.rst:18 +msgid "Why Do I Need This Feature?" msgstr "" -#: ../system/subscription/index.rst:20 +#: ../system/integrations/slack.rst:20 msgid "" -"The subscription section currently consists of two tabs: Plan & Billing. For " -"your overview we've divided those two tabs into independent sub pages:" +"If you're already using Slack for your team communication, you'll love this " +"feature! Our Slack integration can push ticket notifications about the last " +"ticket article based on the following events:" msgstr "" -#: ../system/subscription/index.rst:25 -msgid ":doc:`💰 Subscription plan `" +#: ../system/integrations/slack.rst:24 +msgid "on Ticket creation" msgstr "" -#: ../system/subscription/index.rst:24 -msgid "" -"Everything affecting your instance subscription functions like number of " -"agents, package and payment method." +#: ../system/integrations/slack.rst:25 +msgid "on Ticket updates" msgstr "" -#: ../system/subscription/index.rst:28 -msgid ":doc:`🧾 Subscription billing `" +#: ../system/integrations/slack.rst:26 +msgid "on reached reminders" msgstr "" -#: ../system/subscription/index.rst:28 -msgid "" -"Everything regarding billing address, invoices and account cancellation." +#: ../system/integrations/slack.rst:27 +msgid "a Ticket has escalated" msgstr "" -#: ../system/subscription/index.rst:33 -msgid "FAQ" +#: ../system/integrations/slack.rst:28 +msgid "a Ticket is going to escalate" msgstr "" -#: ../system/subscription/index.rst:37 -msgid "I set up a trial account but am missing functions to test" +#: ../system/integrations/slack.rst:30 +msgid "" +"Zammad will provide the Ticket title, a direct link to the Ticket, the event " +"type (creation, updated, escalation), the customer, time and the last " +"article that has triggered the notification." msgstr "" -#: ../system/subscription/index.rst:36 +#: ../system/integrations/slack.rst:34 msgid "" -"The trial instance is running within the professional package allowing up to " -"three agents." +"This will give you further options, as you can see e.g. escalating tickets " +"that are assigned to an agent that's e.g. absent. You can interact faster, " +"as you might see problems earlier (or even before the problem gets one)." msgstr "" -#: ../system/subscription/index.rst:40 -msgid "Can I change package within the trial?" +#: ../system/integrations/slack.rst:38 +msgid "" +"If needed and wanted, you can even discuss directly about the topic before " +"sending an answer to the customer. Another possible use case would be a " +"agent monitoring new agents and their answers to tickets." msgstr "" -#: ../system/subscription/index.rst:40 -msgid "No. As soon as the package is changed the subscription begins." -msgstr "" +#: ../system/integrations/slack.rst:44 +#, fuzzy +msgid "Configure the Integration" +msgstr "Konfigurace widgetu Chat" -#: ../system/subscription/index.rst:45 -msgid "What happens to my trial instance after the trial period ended?" +#: ../system/integrations/slack.rst:46 +msgid "" +"First of all, please go to your slack workspace - go to administration => " +"Manage Apps. If you don't have an app yet, you can simply add a new one - " +"just search for ``Incoming WebHooks`` and customize the app to your needs." msgstr "" -#: ../system/subscription/index.rst:43 +#: ../system/integrations/slack.rst:50 msgid "" -"Your instance will automatically be canceled for you. Please see *What " -"happens to my instance after it has been canceled?* for more." +"Choose (or create) the channel Zammad should post it's information to and " +"press on \"Add Incoming WebHooks integration\". If you're ready, copy the " +"provided WebHook URL and go to your Zammad installation." msgstr "" -#: ../system/subscription/index.rst:58 -msgid "What happens to my instance after it has been canceled?" +#: ../system/integrations/slack.rst:56 +msgid "" +"You need administrative rights on the Slack Workspace. The link to the app " +"directory is normally ``https://[workspace-name].slack.com/apps`` ." msgstr "" -#: ../system/subscription/index.rst:48 -msgid "That depends slightly on your instance state:" +#: ../system/integrations/slack.rst:63 +msgid "" +"To configure the slack integration, log in to Zammad and go to Integrations " +"(System) => Slack in the admin panel." msgstr "" -#: ../system/subscription/index.rst:54 -msgid "Trial instance" +#: ../system/integrations/slack.rst:66 +msgid "" +"Here you can choose on what evens Zammad should post information about a " +"ticket to your Slack channel. Next you need to device what groups shall be " +"affected by this, as anybody with access to that specific Slack channel can " +"read at least parts of the ticket this might be a privacy issue, if you " +"select the wrong groups. The username is simply the name that Zammad uses as " +"display name inside the Slack chat. The channel defines the Slack channel " +"the information is being posted in. As last option, you can set a custom " +"icon for posting to slack." msgstr "" -#: ../system/subscription/index.rst:51 +#: ../system/integrations/slack.rst:74 msgid "" -"If you're still on trial, we will ice your instance and remind you once " -"again about your instance. We then will wait some days and remove your " -"instance from our system. This is the last time we will inform you by Email." +"When you're ready, just hit \"Submit\" and enable the integration. Zammad " +"will now post new ticket information based on the trigger you chose. Below " +"the options you have the recent log that shows the latest requests to Slack " +"for debugging if needed." msgstr "" -#: ../system/subscription/index.rst:58 -msgid "Paid instance" +#: ../system/integrations/slack.rst:81 +msgid "" +"If you leave the Icon URL empty, Zammad will use the Zammad logo instead. " +"The icon should be a square PNG file." msgstr "" -#: ../system/subscription/index.rst:57 +#: ../system/integrations/slack.rst:90 msgid "" -"If you're a paying customer and canceled your subscription, the instance " -"removal will take place the day after your last subscription day." +"The following figure shows how it will look if you choose to receive updates " +"on created and updated tickets. On every post Zammad sends to the Slack " +"channel, you can create new threads to discuss about the new article." msgstr "" -#: ../system/subscription/index.rst:60 -msgid "Can removed instances be restored?" +#: ../system/integrations/slack.rst:96 +msgid "" +"If you just want to keep track of soon escalating or already escalated " +"tickets, it will look the the following figure. Zammad changes the color in " +"front of the post so you can easily see the state of the ticket." msgstr "" -#: ../system/subscription/index.rst:61 -msgid "No. Once your instance has been removed, a restoration is not possible." +#: ../system/integrations/slack.rst:102 +msgid "" +"If you change the state, Zammad will also put information on what state the " +"ticket gets and (if pending state) the date until it pends. You'll also " +"recognize the color codes in front of posts on slack, as they are exact the " +"same the ticket state colors you'll see in Zammad!" msgstr "" -#: ../system/subscription/plan.rst:2 ../system/subscription/plan.rst:38 -msgid "Plan" +#: ../system/integrations/smime/index.rst:2 +msgid "S/MIME" msgstr "" -#: ../system/subscription/plan.rst:16 -msgid "Subscription" +#: ../system/integrations/smime/index.rst:11 +msgid "" +"S/MIME is the most widely-supported method for secure email communication. " +"With S/MIME, you can exchange **signed** and **encrypted** messages with " +"others." msgstr "" -#: ../system/subscription/plan.rst:5 +#: ../system/integrations/smime/index.rst:15 msgid "" -"On the top of the subscription summary you'll find the number of used and " -"available (booked) agent seats. By using the *see more* link you can also " -"expand an agent list to see the currently configured active agents. This " -"list *does not* count accounts with admin permissions only." +"is proof that a message hasn't been tampered with or sent by an impersonator." msgstr "" -#: ../system/subscription/plan.rst:0 +#: ../system/integrations/smime/index.rst:17 msgid "" -"Within subscription you can always see how many agents are still\n" -"available to add and who uses the seats." +"In other words, it guarantees a message's **integrity** and **authenticity**." msgstr "" -#: ../system/subscription/plan.rst:14 -msgid "" -"Learn more on how to manage your agents in general :doc:`here `." +#: ../system/integrations/smime/index.rst:22 +msgid "In other words, it guarantees **privacy** and **data security**." msgstr "" -#: ../system/subscription/plan.rst:19 -msgid "" -"This section gives you an overview of the available plans and their " -"functions / limits. If you require a more detailed table, check our " -"`detailed pricing table `_ for more." +#: ../system/integrations/smime/index.rst:28 +msgid "Screencast demo of S/MIME features for both new tickets and replies" msgstr "" -#: ../system/subscription/plan.rst:23 +#: ../system/integrations/smime/index.rst:28 msgid "" -"Your selection in this step will decide on the base agent price and e.g. " -"agent limits that might apply in the summary step." +"Once S/MIME has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " +"appear in the ticket composer." msgstr "" -#: ../system/subscription/plan.rst:26 -msgid "" -"The green *Selected* button will also tell you what plan you're currently in." +#: ../system/integrations/smime/index.rst:32 +msgid ":doc:`🔪 Prerequisites `" msgstr "" -#: ../system/subscription/plan.rst:30 +#: ../system/integrations/smime/index.rst:31 msgid "" -"Trial instances are running at Professional with 3 agents. The plan cannot " -"be changed during the trial for technical reasons, if you require more " -"agents for testing, please contact `our sales team `_ with a reason for the raise request." +"New to S/MIME? This section helps you to find certificate providers and " +"points out Limitations." msgstr "" -#: ../system/subscription/plan.rst:0 -msgid "" -"Screenshot showing three available packages for a hosted Zammad\n" -"instance" +#: ../system/integrations/smime/index.rst:35 +msgid ":doc:`📝 Manage Certificates `" msgstr "" -#: ../system/subscription/plan.rst:83 -msgid "Summary" +#: ../system/integrations/smime/index.rst:35 +msgid "Add and download certificates; configure group default behaviors." msgstr "" -#: ../system/subscription/plan.rst:41 -msgid "" -"In this section you can adjust the settings of the previous selected plan." +#: ../system/integrations/smime/index.rst:38 +msgid ":doc:`😦 Troubleshooting `" msgstr "" -#: ../system/subscription/plan.rst:45 -msgid "" -"Note that upgrading (more agents, higher package) is always possible, " -"however, downgrading will only happen when your billing period renews." +#: ../system/integrations/smime/index.rst:38 +msgid "Took a wrong turn? About recent logs and common issues." msgstr "" -#: ../system/subscription/plan.rst:49 +#: ../system/integrations/smime/index.rst:43 msgid "" -"Upgrading resets your billing period and existing credit will be deducted " -"from the new total." +"For more details on how S/MIME integration works on the agent side, see the :" +"user-docs:`user docs `." msgstr "" -#: ../system/subscription/plan.rst:58 -msgid "Billing cycle" +#: ../system/integrations/smime/manage-certificates.rst:2 +msgid "Manage Certificates" msgstr "" -#: ../system/subscription/plan.rst:53 +#: ../system/integrations/smime/manage-certificates.rst:4 msgid "" -"You can choose between either monthly or yearly billing. The price per agent " -"will be cheaper if you decide for yearly billing." +"S/MIME is **disabled by default**. Enable it to start adding certificates." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:10 +msgid "Dialogue to add new certificates or private keys" msgstr "" -#: ../system/subscription/plan.rst:56 +#: ../system/integrations/smime/manage-certificates.rst:10 msgid "" -"If you're still trying out things and are unsure of the right package for " -"your instance, you may want to choose monthly first and then upgrade to " -"yearly when you're sure." +"Manage certificates in the Admin Panel under **System > Integrations > S/" +"MIME**. Certificates may be pasted in as plain text or uploaded from a file." msgstr "" -#: ../system/subscription/plan.rst:66 -msgid "Plan: (Starter|Professional|Plus) - Agents" +#: ../system/integrations/smime/manage-certificates.rst:14 +msgid "Add Certificate Data" msgstr "" -#: ../system/subscription/plan.rst:61 -msgid "Choose the number of agents you require for your instance." +#: ../system/integrations/smime/manage-certificates.rst:36 +msgid "Add Certificate" msgstr "" -#: ../system/subscription/plan.rst:63 +#: ../system/integrations/smime/manage-certificates.rst:17 msgid "" -"Keep in mind that some packages may have agent limits. Depending on the " -"previous chosen package, you won't be able to exceed specific agent numbers. " -"Also note that setting less agents than currently configured is not possible." +"Import public-key certificates for both your own organization and your " +"contacts." msgstr "" -#: ../system/subscription/plan.rst:69 -msgid "Total" +#: ../system/integrations/smime/manage-certificates.rst:19 +msgid "" +"You can also add a bunch of certificates in one go by providing a single " +"file with all relevant certificates." msgstr "" -#: ../system/subscription/plan.rst:69 -msgid "This will be the net total you're going to be billed." +#: ../system/integrations/smime/manage-certificates.rst:22 +msgid "🕵️ **ALWAYS verify certificates in-person or over the phone!**" msgstr "" -#: ../system/subscription/plan.rst:71 +#: ../system/integrations/smime/manage-certificates.rst:24 msgid "" -"By using the *Update subscription* button, the instance package will be " -"adjusted immediately. If you didn't provide a payment method yet, Zammad " -"will request you to provide one at this point." +"The whole point of signatures is to alert you when someone is trying to " +"pretend to be someone they're not. Never accept a certificate from someone " +"online without verifying it first." msgstr "" -#: ../system/subscription/plan.rst:77 -msgid "" -"In case you're still within the trial period, this means that the trial will " -"be over immediately!" +#: ../system/integrations/smime/manage-certificates.rst:28 +msgid "📇 **What about trusted certificate authorities?**" msgstr "" -#: ../system/subscription/plan.rst:80 -msgid "Down- or upgrading during the trial period *is not* possible." +#: ../system/integrations/smime/manage-certificates.rst:30 +msgid "" +"In some cases (e.g. when dealing with large enterprises), you may be given a " +"certificate for an entire CA, rather than a single contact. Add it here to " +"trust *all* certificates issued by that CA." msgstr "" -#: ../system/subscription/plan.rst:0 -msgid "Screenshot showing payment options and a pricing summary" +#: ../system/integrations/smime/manage-certificates.rst:35 +msgid "" +"Commercial CAs can usually be verified online. Zammad does not include a " +"list of built-in, trusted CAs." msgstr "" -#: ../system/subscription/plan.rst:99 -msgid "Payment method" +#: ../system/integrations/smime/manage-certificates.rst:57 +msgid "Add Private Key" msgstr "" -#: ../system/subscription/plan.rst:86 -msgid "You can pay via credit card or SEPA mandate." +#: ../system/integrations/smime/manage-certificates.rst:39 +msgid "" +"Once you've added a public-key certificate, you can import its matching " +"private key." msgstr "" -#: ../system/subscription/plan.rst:91 -msgid "Credit card" +#: ../system/integrations/smime/manage-certificates.rst:42 +msgid "" +"Private keys are for **your own organization only**; never ask your contacts " +"for their private keys." msgstr "" -#: ../system/subscription/plan.rst:89 +#: ../system/integrations/smime/manage-certificates.rst:0 msgid "" -"Simply follow the dialogue by clicking *authorize* and confirm -if required " -"by your bank- your consent to Zammad using your card for the payments." +"S/MIME integration showing configured certificates and possible issues with " +"Logging" msgstr "" -#: ../system/subscription/plan.rst:95 -msgid "SEPA" +#: ../system/integrations/smime/manage-certificates.rst:50 +msgid "" +"A note is displayed on certificates with a matching private key (see line 2)." msgstr "" -#: ../system/subscription/plan.rst:94 -msgid "" -"Provide the requested information of the bank account holder and update if " -"you're ready. You'll then receive an email with the SEPA mandate." +#: ../system/integrations/smime/manage-certificates.rst:52 +msgid "📤 **Certificates and private keys must be uploaded separately.**" msgstr "" -#: ../system/subscription/plan.rst:97 +#: ../system/integrations/smime/manage-certificates.rst:54 msgid "" -"Technically there's also the possibility to pay via invoice, however - this " -"method only applies to a fairly low number of instances. Please contact `our " -"sales team `_ for more information." +"If your certificate and private key are bundled together in the same file or " +"PEM block, import it twice (once using each button)." msgstr "" -#: ../system/translations.rst:2 -msgid "Translations" +#: ../system/integrations/smime/manage-certificates.rst:57 +msgid "Please note that bulk imports of private keys are not possible." msgstr "" -#: ../system/translations.rst:4 -msgid "" -"Translations of Zammad are processed centrally in our `Weblate instance " -"`_. This allows non-developers to review " -"and update translation texts of the language they actually speak." +#: ../system/integrations/smime/manage-certificates.rst:60 +msgid "Download Certificate Data" msgstr "" -#: ../system/translations.rst:9 +#: ../system/integrations/smime/manage-certificates.rst:62 msgid "" -"Your language is in an incomplete translation state or has typos? Please " -"consider helping us in sorting this out! All you need is either a GitHub " -"account or to register directly in our instance." +"You can download the earlier provided certificates and private keys at any " +"time from your Zammad instance." msgstr "" -#: ../system/translations.rst:13 +#: ../system/integrations/smime/manage-certificates.rst:65 msgid "" -"Did you know? This is also where the documentation translations are handled. " -"🤓" +"Please note that passphrase-protected private keys stay protected and when " +"you download them, you have to know the passphrase to use them after " +"downloading." msgstr "" -#: ../system/translations.rst:15 -msgid "" -"Have a look in our :docs:`contribution section ` in the system documentation to get started!" +#: ../system/integrations/smime/manage-certificates.rst:73 +msgid "Dialogue to download certificates or private keys" msgstr "" -#: ../system/translations.rst:20 -msgid "Local Translations" +#: ../system/integrations/smime/manage-certificates.rst:73 +msgid "Download stored certificates and their keys" msgstr "" -#: ../system/translations.rst:22 +#: ../system/integrations/smime/manage-certificates.rst:78 msgid "" -"Apart from these system translations, there's still local translations you " -"can manage. This is relevant if you added custom objects that require " -"translations or even custom states and priorities." +"The ticket composer will set all outgoing messages to **signed and " +"encrypted** by default (assuming the required certificates exist)." msgstr "" -#: ../system/translations.rst:None -msgid "Translation management screen within the admin menu" +#: ../system/integrations/smime/manage-certificates.rst:82 +msgid "These defaults can be modified on a per-group basis:" msgstr "" -#: ../system/translations.rst:31 -msgid "Updating Translations" +#: ../system/integrations/smime/manage-certificates.rst:None +msgid "Zammad allowing to choose the default behavior on per group basis" msgstr "" -#: ../system/translations.rst:33 +#: ../system/integrations/smime/manage-certificates.rst:89 msgid "" -"Because of how Zammad ships translations, the only way to update the system " -"translations is to update your Zammad installation. The benefit of this is " -"that you no longer need internet access during a Zammad upgrade as the " -"package has everything it requires already." +"Of course, agents can always manually change these settings on each email " +"they send out." msgstr "" -#: ../system/translations.rst:39 -msgid "Translation of Custom Objects" +#: ../system/integrations/smime/prerequisites.rst:4 +msgid "A certificate *and* private key for your own organization" msgstr "" -#: ../system/translations.rst:41 +#: ../system/integrations/smime/prerequisites.rst:6 msgid "" -"No problem at all! You can customize any translation locally, even if it is " -"not initially provided by the system." +"(Use this to ✒️ **sign outgoing messages** and 🔓 **decrypt incoming " +"messages**.)" msgstr "" -#: ../system/translations.rst:44 +#: ../system/integrations/smime/prerequisites.rst:9 msgid "" -"Translation is supported for a broad number of features, including but not " -"limited to custom:" -msgstr "" - -#: ../system/translations.rst:47 -msgid "Object Attributes" +"Certificates belonging your contacts, or their issuing certificate authority " +"(CA)" msgstr "" -#: ../system/translations.rst:48 -msgid "Ticket Macros" +#: ../system/integrations/smime/prerequisites.rst:11 +msgid "" +"(Use these to ✅ **verify incoming message signatures** and 🔒 **encrypt " +"outgoing messages**.)" msgstr "" -#: ../system/translations.rst:49 -msgid "Ticket Overviews" +#: ../system/integrations/smime/prerequisites.rst:14 +msgid "🙋 **I'm new to S/MIME. Where can I get a certificate?**" msgstr "" -#: ../system/translations.rst:50 -msgid "Ticket Priorities" +#: ../system/integrations/smime/prerequisites.rst:16 +msgid "" +"The easiest way to get certificates is to buy an annual subscription through " +"a commercial CA, such as:" msgstr "" -#: ../system/translations.rst:51 -msgid "Ticket States" +#: ../system/integrations/smime/prerequisites.rst:19 +msgid "" +"`Sectigo (formerly Comodo) `_" msgstr "" -#: ../system/translations.rst:54 -msgid "Customizing Translations" +#: ../system/integrations/smime/prerequisites.rst:20 +msgid "`Secorio `_" msgstr "" -#: ../system/translations.rst:56 -msgid "" -"Within the translation screen, simply click on the **New Translation** " -"button." +#: ../system/integrations/smime/prerequisites.rst:21 +msgid "`GlobalSign `_" msgstr "" -#: ../system/translations.rst:None -msgid "New translation dialog" +#: ../system/integrations/smime/prerequisites.rst:23 +msgid "(Zammad is not affiliated with these CAs in any way.)" msgstr "" -#: ../system/translations.rst:62 +#: ../system/integrations/smime/prerequisites.rst:25 msgid "" -"In the dialog you can immediately enter the exact translation source (if you " -"know it) and your custom translation text for it and click **Submit**." +"You can also generate your own self-signed certificates, but the process is " +"complicated and usually 🙅 **involves extra work for your contacts**." msgstr "" -#: ../system/translations.rst:65 +#: ../system/integrations/smime/prerequisites.rst:29 msgid "" -"Alternatively, try to search for translation suggestions in the list below. " -"Selecting an item from the list will pre-fill the translation source for you " -"and then you can just enter your custom translation." +"Bear in mind that 🤝 **S/MIME only works if the other party is using it, too." +"**" msgstr "" -#: ../system/translations.rst:69 -msgid "" -"The target language will always default to your current language selection. " -"If you need to translate for a different language, simply change the " -"selection before submitting." +#: ../system/integrations/smime/prerequisites.rst:32 +msgid "Certificate and Private Key Checks on Upload" msgstr "" -#: ../system/translations.rst:73 +#: ../system/integrations/smime/prerequisites.rst:34 msgid "" -"All your custom translations will show up in the overview table when added. " -"And they will even persist across Zammad updates!" +"The certificate and public key validation is based on the ``X509v3`` " +"extensions." msgstr "" -#: ../system/translations.rst:76 -msgid "" -"Make sure to reload your browser if a translated string is not displayed." +#: ../system/integrations/smime/prerequisites.rst:49 +msgid "Uploading a *client certificate*?" msgstr "" -#: ../system/translations.rst:80 -msgid "Reverting to Original Translations" +#: ../system/integrations/smime/prerequisites.rst:41 +msgid "The following attributes are required then:" msgstr "" -#: ../system/translations.rst:82 -msgid "" -"If you want to revert a custom translation to original text, simply use the " -"appropriate action within the row of the overview table." +#: ../system/integrations/smime/prerequisites.rst:39 +msgid "Subject Alternative Name (at least one email address has to be present)" msgstr "" -#: ../system/translations.rst:85 -msgid "" -"Depending on the type of the translation source, the action has a slightly " -"different name:" +#: ../system/integrations/smime/prerequisites.rst:40 +msgid "Key Usage (``Digital Signature`` and/or ``Key Encipherment``)" msgstr "" -#: ../system/translations.rst:88 -msgid "**Reset** for customized system translations" +#: ../system/integrations/smime/prerequisites.rst:41 +msgid "Public key algorithm (either ``RSA`` or ``EC``)" msgstr "" -#: ../system/translations.rst:89 -msgid "**Remove** for customized local translations" +#: ../system/integrations/smime/prerequisites.rst:43 +msgid "" +"The Extended Key Usage attribute is optional. If the certificate provides " +"the named attribute, than it must contain the value ``E-mail Protection``." msgstr "" -#: ../system/translations.rst:91 +#: ../system/integrations/smime/prerequisites.rst:46 msgid "" -"In both cases, the action will remove the customized translation after a " -"confirmation." +"Please note that any usable email adress has to be prefixed with ``email:`` " +"or ``rfc822:``." msgstr "" -#: ../system/translations.rst:None -msgid "Screenshot showing the location of the Remove action" +#: ../system/integrations/smime/prerequisites.rst:49 +msgid "The named public key algorithms are mandatory for private keys as well." msgstr "" -#: ../system/translations.rst:99 -msgid "Inline Translations" +#: ../system/integrations/smime/prerequisites.rst:54 +msgid "Uploading a *CA certificate*?" msgstr "" -#: ../system/translations.rst:101 +#: ../system/integrations/smime/prerequisites.rst:52 msgid "" -"If you prefer a more hands-on approach, you can activate the inline or on-" -"screen translation feature by pressing ``ctrl`` + ``alt`` + ``t`` at any " -"time and on any screen." +"In the case of an uploaded CA certificate, providing the value ``CA:TRUE`` " +"in the attribute *Basic Contstraints*, the previously mentioned attributes " +"are not verified." msgstr "" -#: ../system/translations.rst:105 +#: ../system/integrations/smime/prerequisites.rst:56 msgid "" -"All customizable translation texts will be highlighted for you on the " -"screen. Just click into the highlighted area and update the text in place." -msgstr "" - -#: ../system/translations.rst:None -msgid "Inline translation mode activated for the Overview screen" +"In general, the usage of any expired (``Not After``) or not yet valid (``Not " +"Before``) certificate is denied for outgoing emails." msgstr "" -#: ../system/translations.rst:112 -msgid "" -"When finished editing, simply press ``ctrl`` + ``alt`` + ``t`` again to " -"deactivate." +#: ../system/integrations/smime/prerequisites.rst:59 +msgid "Example certificate:" msgstr "" -#: ../system/translations.rst:117 +#: ../system/integrations/smime/prerequisites.rst:85 msgid "" -"Even though it's available on any screen, the inline translation feature " -"requires admin permissions. It works only for the current language " -"selection. If you need to translate a different language, first change the " -"language in your :user-docs:`profile settings `." +"Please note that Zammad will distrust senders by default. This means that " +"you're always required to provide certificate data, no matter if for signing " +"or encrypting." msgstr "" -#: ../system/variables.rst:2 -msgid "Variables" +#: ../system/integrations/smime/prerequisites.rst:89 +msgid "This is by design and can't be adjusted." msgstr "" -#: ../system/variables.rst:4 +#: ../system/integrations/smime/troubleshooting.rst:4 msgid "" -"Please note that this is just an overview of available variables. It might " -"be incomplete or variables might not be available within some functions. If " -"you're missing variables or are not sure if something is not working as " -"expected, feel free to ask over at the `Community `_." +"All of the system's latest S/MIME activity is displayed in the **Recent " +"Logs** section." msgstr "" -#: ../system/variables.rst:10 -msgid "" -"Variables can be called by typing ``::`` (just like text modules in the " -"frontend), as long as you're in a supported text field within the backend. " -"Zammad will display all variables being available within this context and " -"replace it to the variable as soon as you selected an entry." +#: ../system/integrations/smime/troubleshooting.rst:11 +msgid "Sample entries of in- and outgoing S/MIME related emails." msgstr "" -#: ../system/variables.rst:15 +#: ../system/integrations/smime/troubleshooting.rst:11 msgid "" -"You have an empty field which you referenced and it appears as ``-``? That's " -"currently working as designed - you might want to ensure that these fields " -"always have a value." +"Logs report the status and details of all mail, both incoming and outgoing, " +"that used signing/verification or encryption/decryption." msgstr "" -#: ../system/variables.rst:20 -msgid "Variable Categories" +#: ../system/integrations/smime/troubleshooting.rst:14 +msgid "" +"This log does **not** include email sent by :doc:`triggers ` or the :doc:`scheduler `. For those, check your " +"``production.log``." msgstr "" -#: ../system/variables.rst:31 -msgid "Wait, What About Custom Objects?" +#: ../system/integrations/smime/troubleshooting.rst:20 +msgid "Common Issues" msgstr "" -#: ../system/variables.rst:33 -msgid "" -"Good point! Of course, we can't predict what objects you might create, but " -"we can give you a hint on how to put the puzzle together to get your custom " -"values." +#: ../system/integrations/smime/troubleshooting.rst:30 +msgid "I received a signed/encrypted email before I set up S/MIME integration" msgstr "" -#: ../system/variables.rst:36 +#: ../system/integrations/smime/troubleshooting.rst:23 msgid "" -"For this, we'll talk about the inner part of the variable (so everything " -"within ``#{}``), please put the outer part around to have a valid variable. " -"The first part of the variable name consist of the object type. Currently " -"these are:" +"No problem. Once S/MIME has been enabled and the appropriate certificates " +"have been added, agents will be prompted to retry verification/decryption on " +"matching emails." msgstr "" -#: ../system/variables.rst:41 -msgid "Ticket (``ticket``)" +#: ../system/integrations/smime/troubleshooting.rst:0 +msgid "Screenshot of user prompt to retry decryption" msgstr "" -#: ../system/variables.rst:42 -msgid "User (``user``)" +#: ../system/integrations/smime/troubleshooting.rst:38 +msgid "The 🔒 **Encrypt** button is disabled" msgstr "" -#: ../system/variables.rst:43 -msgid "Organization (``organization``)" +#: ../system/integrations/smime/troubleshooting.rst:33 +msgid "Have you added the recipient's certificate?" msgstr "" -#: ../system/variables.rst:44 -msgid "Group (``group``)" +#: ../system/integrations/smime/troubleshooting.rst:34 +msgid "Are you sure the recipient's certificate is valid?" msgstr "" -#: ../system/variables.rst:46 -msgid "" -"The second part is the name of the object. This is the name you define " -"during object creation and can be found within the object menu at any time. " -"The first and second part of a variable is divided by a point, e.g.: " -"``ticket.number`` which will in total be ``#{ticket.number}``." +#: ../system/integrations/smime/troubleshooting.rst:35 +msgid "Have you checked your ``production.log`` for more details?" msgstr "" -#: ../system/variables.rst:51 +#: ../system/integrations/smime/troubleshooting.rst:37 msgid "" -"Now, in some situations it's possible that you'll need to use a third part. " -"The best example for such a situation would be a ``select`` or ``tree-" -"select`` field which will by default return the key value, not it's display " -"name. For this, just extend your variable with ``.value``. This will result " -"in ``#{ticket.select.value}``." +"If encryption doesn't work in the composer, it won't work in :doc:`triggers " +"` or the :doc:`scheduler ` either!" msgstr "" -#: ../system/variables.rst:60 -msgid "Using Translated Variables" +#: ../system/integrations/smime/troubleshooting.rst:42 +msgid "The ✅ **Sign** button is disabled" msgstr "" -#: ../system/variables.rst:62 +#: ../system/integrations/smime/troubleshooting.rst:41 msgid "" -"If you want to use a translated variable in triggers or schedulers, you can " -"extend the placeholder like this: ``#{t(ticket.state.name)}``. The ``t`` " -"tells Zammad to search for fitting translated strings. The used output " -"language is based on the system language of Zammad which you can set in the " -"admin panel under :doc:`/settings/branding` or based on the selected locale " -"in the trigger/scheduler edit dialog." +"Have you added **both the certificate and private key** for your " +"organization?" msgstr "" -#: ../system/variables.rst:69 +#: ../system/integrations/smime/troubleshooting.rst:42 msgid "" -"A possible use-case: you want to send your customers updates on tickets via " -"trigger or scheduler which should include the state of the ticket. Using the " -"default ``#{ticket.state.name}`` (without the translation flag ``t()``) " -"would lead to the output of the original (english) name of the state." +"Does the email address on the certificate match the email address of the " +"agent/group composing the email?" msgstr "" -#: ../system/variables.rst:75 -msgid "Date and Time Formatting" +#: ../system/integrations/smime/troubleshooting.rst:45 +msgid "Error: “Fingerprint already taken”" msgstr "" -#: ../system/variables.rst:77 -msgid "" -"The system (trigger/scheduler selected) locale and timezone predefines a " -"default format of date and timestamp. This format is customizable by using " -"the ``dt()`` method." +#: ../system/integrations/smime/troubleshooting.rst:45 +msgid "Are you sure you haven't added this certificate already?" msgstr "" -#: ../system/variables.rst:79 -msgid "The method arguments are as follows:" +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Error: “❌ invalid byte sequence in UTF-8”" msgstr "" -#: ../system/variables.rst:81 -msgid "The date or timestamp variable you want to format." +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Please ensure to provide PEM formatted certificate and keys." msgstr "" -#: ../system/variables.rst:82 -msgid "The output format string." +#: ../system/integrations/smime/troubleshooting.rst:49 +msgid "Did you check if the provided file is a valid certificate or key?" msgstr "" -#: ../system/variables.rst:83 -msgid "The timezone to apply (optional)." +#: ../system/integrations/zabbix.rst:2 +msgid "Zabbix Integration" msgstr "" -#: ../system/variables.rst:86 +#: ../system/integrations/zabbix.rst:5 msgid "" -"``#{dt(ticket.updated_at, \"%A %Y-%m-%d %H:%M in the office\", \"Europe/" -"Berlin\")}``" +"This guide describes how to integrate your Zabbix 5.4 installation with " +"Zammad using the Zabbix webhook feature. This guide will provide " +"instructions on setting up a media type, a user and an action in Zabbix." msgstr "" -#: ../system/variables.rst:87 -msgid "Monday, 2024-03-18 15:31 in the office" +#: ../system/integrations/zabbix.rst:12 +msgid "Zammad with enabled HTTP Token Authentication" msgstr "" -#: ../system/variables.rst:89 -msgid "" -"If you want to use our example, make sure to paste the string above without " -"formatting (``CTRL+Shift+v``), otherwise it won't work." +#: ../system/integrations/zabbix.rst:13 +msgid "Zabbix version 5.4 or higher" msgstr "" -#: ../system/variables.rst:93 -msgid "The following table lists available format directives:" +#: ../system/integrations/zabbix.rst:16 +msgid "Setting up a Zammad" msgstr "" -#: ../system/variables.rst:99 -msgid "Parameter" +#: ../system/integrations/zabbix.rst:18 +msgid "Enable **API Token Access** in Settings > System > API." msgstr "" -#: ../system/variables.rst:102 -msgid "``%Y``" +#: ../system/integrations/zabbix.rst:20 +msgid "" +"Create a **new user** for a Zabbix alerter with an **email address** and " +"create a personal user token with **ticket.agent** permissions." msgstr "" -#: ../system/variables.rst:103 -msgid "Year with 4 digits" +#: ../system/integrations/zabbix.rst:24 +msgid "Zabbix Webhook Configuration" msgstr "" -#: ../system/variables.rst:104 -msgid "Use ``%y`` for year with 2 digits" +#: ../system/integrations/zabbix.rst:27 +msgid "Create a Global Macro" msgstr "" -#: ../system/variables.rst:105 -msgid "``%m``" +#: ../system/integrations/zabbix.rst:29 +msgid "" +"Before setting up the **Webhook**, you need to setup the global macro " +"**{$ZABBIX.URL}**, which must contain the **URL** to the **Zabbix frontend**." msgstr "" -#: ../system/variables.rst:106 -msgid "Month of year (as number with zero-padding)" +#: ../system/integrations/zabbix.rst:33 +msgid "" +"In the **Administration** > **Media types** section, import the `Template`_." msgstr "" -#: ../system/variables.rst:107 -msgid "Use ``%-m`` for month without zero-padding" +#: ../system/integrations/zabbix.rst:38 +msgid "Open the added **Zammad** media type and set:" msgstr "" -#: ../system/variables.rst:108 -msgid "``%d``" +#: ../system/integrations/zabbix.rst:40 +msgid "**zammad\\_access\\_token** to the your **Personal User Token**" msgstr "" -#: ../system/variables.rst:109 -msgid "Day of month (as number with zero-padding)" +#: ../system/integrations/zabbix.rst:41 +msgid "" +"**zammad\\_url** to the **frontend URL** of your **Zammad** installation" msgstr "" -#: ../system/variables.rst:110 -msgid "Use ``%e`` for day without zero-padding" +#: ../system/integrations/zabbix.rst:43 +msgid "**zammad\\_customer** to your **Zammad user email**." msgstr "" -#: ../system/variables.rst:111 -msgid "``%H``" +#: ../system/integrations/zabbix.rst:44 +msgid "" +"**zammad\\_enable\\_tags** to **true** or **false** to enable or disable " +"trigger tags. **Important**: if you enable tag support, each tag is set with " +"a separate request." msgstr "" -#: ../system/variables.rst:112 -msgid "Hour of day in 24h notation with zero-padding" +#: ../system/integrations/zabbix.rst:48 +msgid "" +"If you want to prioritize issues according to **severity** values in Zabbix, " +"you can define mapping parameters:" msgstr "" -#: ../system/variables.rst:113 -msgid "Use ``%k`` for hour without zero-padding" +#: ../system/integrations/zabbix.rst:51 +msgid "**severity\\_**: Zammad priority ID" msgstr "" -#: ../system/variables.rst:114 -msgid "``%I``" +#: ../system/integrations/zabbix.rst:53 +msgid "Click the **Update** button to save the **Webhook** settings." msgstr "" -#: ../system/variables.rst:115 -msgid "Hour of day in 12h notation with zero-padding" +#: ../system/integrations/zabbix.rst:55 +msgid "" +"To receive notifications in **Zammad**, you need to create a **Zabbix user** " +"and add **Media** with the **Zammad** type." msgstr "" -#: ../system/variables.rst:116 +#: ../system/integrations/zabbix.rst:58 msgid "" -"Use ``%l`` for hour without zero-padding and ``%p`` / ``%P`` for meridian " -"indicator" +"For **Send to**: enter any text, as this value is not used, but is required." msgstr "" -#: ../system/variables.rst:117 -msgid "``%M``" +#: ../system/integrations/zabbix.rst:61 +msgid "" +"For more information, use the `Zabbix documentation `_." msgstr "" -#: ../system/variables.rst:118 -msgid "Minute of hour" +#: ../system/maintenance.rst:2 +msgid "Maintenance" msgstr "" -#: ../system/variables.rst:120 -msgid "``%S``" +#: ../system/maintenance.rst:4 +msgid "" +"Zammad comes with a maintenance mode that you can use for e.g. updating the " +"instance or changing settings while restricting availability and functions." msgstr "" -#: ../system/variables.rst:121 -msgid "Second of Minute" +#: ../system/maintenance.rst:13 +msgid "Mode" msgstr "" -#: ../system/variables.rst:123 -msgid "``%A``" +#: ../system/maintenance.rst:8 +msgid "The mode setting allows you to enable or disable the maintenance mode." msgstr "" -#: ../system/variables.rst:124 -msgid "Weekday name" +#: ../system/maintenance.rst:10 +msgid "Defaults to *off*." msgstr "" -#: ../system/variables.rst:125 -msgid "Use ``%a`` for abbreviated name or ``%^A`` for uppercase name" +#: ../system/maintenance.rst:12 +msgid "" +"The maintenance mode will restrict access to administrative roles only. This " +"means agents and customers are logged off." msgstr "" -#: ../system/variables.rst:126 -msgid "``%B``" +#: ../system/maintenance.rst:23 +msgid "@Login" msgstr "" -#: ../system/variables.rst:127 -msgid "Month name" +#: ../system/maintenance.rst:16 +msgid "" +"This setting allows you to provide a login message within a green banner " +"above the login screen. Click into the green banner in the settings page to " +"adjust your message. To activate the message, activate the *@Login* setting." msgstr "" -#: ../system/variables.rst:128 -msgid "Use ``%b`` for abbreviated name" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing the default login message within the\n" +"settings page" msgstr "" -#: ../system/variables.rst:129 -msgid "``%U``" +#: ../system/maintenance.rst:26 +msgid "" +"Send an informative message to **all active sessions**. This comes handy to " +"inform your agents e.g. about mayor outages or to force reloads after " +"configuration changes." msgstr "" -#: ../system/variables.rst:130 -msgid "Week number of current year" +#: ../system/maintenance.rst:31 +msgid "This is the messages title (slightly bigger than the normal message)." msgstr "" -#: ../system/variables.rst:131 -msgid "Use ``%W`` for a different calculation method" +#: ../system/maintenance.rst:34 +msgid "The text you want to provide to your logged in sessions." msgstr "" -#: ../system/variables.rst:134 -msgid "" -"We support the known format directives for the Ruby built-in method " -"``strftime`` of the ``DateTime`` class. For more information, see `here " -"`_." +#: ../system/maintenance.rst:39 +msgid "Reload application" msgstr "" -#: ../system/variables/article.rst:2 -msgid "Articles" +#: ../system/maintenance.rst:37 +msgid "" +"Selecting this option will change the message acceptance button from *Close* " +"(with nothing happening) to *Continue session*, which forces the application " +"to reload." msgstr "" -#: ../system/variables/article.rst:4 ../system/variables/config.rst:4 -#: ../system/variables/current-user.rst:4 ../system/variables/ticket.rst:4 +#: ../system/maintenance.rst:43 msgid "" -"If you're missing variables or are not sure if something is not working as " -"expected, feel free to ask over at the `Community `_." +"If you have customers that are logged in to Zammad, they'll also be notified " +"if they're active in that moment." msgstr "" -#: ../system/variables/article.rst:6 -msgid "" -"Below you can find all available ticket article-based variables within " -"Zammad. These can be called via Triggers for example. If you're unsure if " -"Zammad does support variables at the point you're at, you can try to type " -"``::`` to check." +#: ../system/maintenance.rst:48 +msgid "Example without reload application" msgstr "" -#: ../system/variables/article.rst:9 ../system/variables/config.rst:9 -#: ../system/variables/ticket.rst:9 +#: ../system/maintenance.rst:52 msgid "" -"The below list gives you an example what kind of data you can expect, it's " -"not intended to explain the data itself." +"Message setting within Zammad's admin settings without ticket reload " +"application setting." msgstr "" -#: ../system/variables/article.rst:11 -msgid "Article Variables" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing the send message settings without ticket\n" +"reload application set" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "name" +#: ../system/maintenance.rst:61 ../system/maintenance.rst:85 +msgid "" +"The modal all other active sessions will see upon pressing *Send to clients*." msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "variable" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing modal caused by maintenance's message\n" +"without reload application ticket" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "example" +#: ../system/maintenance.rst:72 +msgid "Example with reload application" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Web" +#: ../system/maintenance.rst:76 +msgid "" +"Message setting within Zammad's admin settings with ticket reload " +"application setting." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.web}``" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing the send message settings with ticket\n" +"reload application set" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``https://zammad.com`` or empty if not set in user object" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing modal caused by maintenance's message\n" +"with reload application ticket" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > VIP" +#: ../system/monitoring.rst:2 +msgid "Monitoring" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.vip}``" +#: ../system/monitoring.rst:4 +msgid "" +"This function is only available in self hosted instances. If you use Zammad " +"in our cloud, we are monitoring the system on our own and take steps to fix " +"potential problems directly." msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -msgid "``true`` or ``false``" +#: ../system/monitoring.rst:11 +msgid "" +"On the monitoring page, you can see the current health state of Zammad under " +"\"*Current Status*\" at the bottom. This can be useful if you want to have a " +"look if everything is up and running. As an example, you could have a look " +"in the monitoring when you assume that some emails aren't processed from " +"Zammad." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Phone" +#: ../system/monitoring.rst:17 +msgid "**Can't receive an email and the monitoring response is \"healthy\"?**" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.phone}``" +#: ../system/monitoring.rst:19 +msgid "" +"Zammad will just inform you about unprocessable emails. This is not the case " +"for oversized emails. You can adjust the maximum email size in :doc:`../" +"channels/email/settings`." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``+4930123456789`` or empty if not set in user object" +#: ../system/monitoring.rst:24 +msgid "Monitoring API" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Note" +#: ../system/monitoring.rst:26 +msgid "" +"Beside the indication in the monitoring page, you can also use an external " +"monitoring tool to monitor Zammad's health. To request the health of Zammad, " +"you need to provide the API key (token) to the external monitoring tool. You " +"can copy the token from the \"*Current Token*\" field as well as the whole " +"API endpoint of your system (\"*Health Check*\" field), in which the API " +"token is already included." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.note}``" +#: ../system/monitoring.rst:37 +msgid "Screenshot showing Current Token and Health Check" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Some note about user`` or empty if not set in user object" +#: ../system/monitoring.rst:37 +msgid "Screenshot showing Token and Health Check" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Mobile" +#: ../system/monitoring.rst:39 +msgid "" +"In addition to that, you can reset the auto-generated token to make sure " +"that already configured monitoring systems won't work anymore. So, please " +"use this \"*Reset*\" button only if you know what you do!" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.mobile}``" +#: ../system/monitoring.rst:44 +msgid "Example Output" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Login" +#: ../system/monitoring.rst:0 +msgid "No issues found" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.login}``" +#: ../system/monitoring.rst:48 ../system/monitoring.rst:60 +msgid "**Indicator in Zammad**:" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -#: ../system/variables/ticket.rst:1 -msgid "``jdoe``" +#: ../system/monitoring.rst:0 +msgid "Screenshot showing monitoring with no issues" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Lastname" +#: ../system/monitoring.rst:54 ../system/monitoring.rst:66 +msgid "**API response**::" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.lastname}``" +#: ../system/monitoring.rst:0 +msgid "Issues were found" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -#: ../system/variables/ticket.rst:1 -msgid "``Doe`` or empty if not set" +#: ../system/monitoring.rst:0 +msgid "Screenshot showing monitoring with issues" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Firstname" +#: ../system/objects.rst:2 +msgid "Objects" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.firstname}``" +#: ../system/objects.rst:4 +msgid "" +"In Zammad you can add your own fields to tickets, users, organizations and " +"even groups (these are called \"objects\"). This can be useful if you need " +"to add further information to a ticket or any other object in Zammad and the " +"information doesn't fit in any existing field." msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "``Joe`` or empty if not set" +#: ../system/objects.rst:11 +msgid "" +"Try to avoid deleting attributes (and disable them instead) as Zammad might " +"run into unexpected conditions if they are referenced somewhere." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Fax" +#: ../system/objects.rst:16 +msgid "" +"Here's an overview of object attributes. On the upper right you can add new " +"attributes. By default, there will be no custom fields - standard attributes " +"will be grayed out, you can't delete or change those. You can edit custom " +"attributes (they are displayed in black font and have a trash bin on the " +"right side) just by clicking on them." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.fax}``" +#: ../system/objects.rst:24 +msgid "" +"Attributes you add to Zammad, no matter if they have default values or not, " +"will not update existing information. This means a new ticket field " +"technically will be empty unless you populate it." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Email" +#: ../system/objects.rst:28 +msgid "" +"Especially in ticket scope this also means that newly added attributes will " +"be indicated as \"changed\" to agents that view the ticket. This may " +"interfere with Zammad's tabs behavior." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.email}``" +#: ../system/objects.rst:40 +msgid "Ordering Attributes" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``jdoe@example.com``" +#: ../system/objects.rst:42 +msgid "" +"Since Zammad introduced :doc:`/system/core-workflows` the need to have a " +"custom positioning for attributes has become more important than ever." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Department" +#: ../system/objects.rst:45 +msgid "" +"To adjust the position of such an attribute, simply click on the attribute " +"entry in question, scroll down and adjust the position number. Please note " +"that you cannot change the positioning of default attributes." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.department}``" +#: ../system/objects.rst:49 +msgid "" +"In case two attributes have the same position value, Zammad will sort " +"alphabetically by name automatically." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Sales`` or empty if not set in user object" +#: ../system/objects.rst:None +msgid "" +"Screenshot showing custom attribute entries ordered in between default ones" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Address" +#: ../system/objects.rst:56 +msgid "Updating Database After Adding or Editing Attributes" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.address}``" +#: ../system/objects.rst:58 +msgid "" +"When adding or changing attributes, Zammad will not apply the changes " +"instantly, but instead shows you the changed attributes first. If you're " +"ready to go, just click on \"Update database\" to apply the changes to " +"Zammad. If you made a mistake or just want to discard your changes, click " +"\"Discard changes\"." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Some street 1, 12345 Berlin`` or empty if not set in user object" +#: ../system/objects.rst:64 +msgid "" +"After applying the changes with \"Update Database\", a restart of Zammad is " +"**mandatory**. If you don't perform it, you may experience unexpected " +"behavior or even errors. You may want to do this kind of configuration " +"during maintenance windows." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated" +#: ../system/objects.rst:72 +msgid "" +"Changes on objects require you to update the database to apply these changes." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_at}``" +#: ../system/objects.rst:75 +msgid "**🤓 Service restarts can be automated**" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``2019-10-08 15:24:47 UTC``" +#: ../system/objects.rst:0 +msgid "Hosted environments automatically restart for you." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Type > Name" +#: ../system/objects.rst:0 +msgid "" +"If you're using a self-hosted installation you can use :docs:`environment " +"variables `" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.type.name}``" +#: ../system/objects.rst:82 +msgid "System Attributes" msgstr "" -#: ../system/variables/article.rst:1 +#: ../system/objects.rst:84 msgid "" -"``email`` (`list of article types `_)" +"Zammad comes with pre-configured attributes. Some of them can't be edited " +"via UI (or at all). This is required for proper operation of Zammad and not " +"a bug." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > To" +#: ../system/objects.rst:90 +msgid "Ticket State" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.to}``" +#: ../system/objects.rst:92 +msgid "" +"If the pre-configured states aren't enough for you or you want to change " +"them, you can do so by clicking on the cogwheel icon in the state row in the " +"ticket tab. But you should be careful when changing pre-configured states. " +"This can lead to unwanted behavior in some cases." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``helpdesk@example.com``" +#: ../system/objects.rst:None +msgid "Screenshot showing highlighted ticket state attribute" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > TicketID" +#: ../system/objects.rst:122 +msgid "Handling of states" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.ticket_id}``" +#: ../system/objects.rst:102 +msgid "" +"In the state configuration screen, you can add new states, disable states or " +"change states." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``1`` (not ticket number)" +#: ../system/objects.rst:0 +msgid "Screenshot showing table of default ticket states" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Subject" +#: ../system/objects.rst:110 +msgid "" +"To add a new state, click on the \"New Ticket State\" button in the top " +"right corner. To change an existing state, simply click on the affected " +"state. This opens an edit dialog." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.subject}``" +#: ../system/objects.rst:114 +msgid "" +"You can also clone a state or set them to \"Default for new tickets\" or " +"\"Default for follow-ups\" by clicking on the ⁝ action button and select the " +"desired function." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``My amazing subject``" +#: ../system/objects.rst:118 +msgid "" +"*Default for new tickets* means that this state is used for every newly " +"created ticket." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Sender > Name" +#: ../system/objects.rst:121 +msgid "" +"*Default for follow-ups* means that this state is used if the ticket is re-" +"opened after it was closed." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.sender.name}``" +#: ../system/objects.rst:171 +msgid "Ticket state in detail" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Customer``, ``Agent`` or ``System``" +#: ../system/objects.rst:125 +msgid "" +"Below you can find a description for each field and option. Please head over " +"to the :ref:`example ` to see the edit dialog." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Visibility" +#: ../system/objects.rst:129 +msgid "" +"This is the name of the state and what you and your agents are seeing when " +"choosing a state somewhere (e.g. in tickets, trigger configuration)." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.internal}``" +#: ../system/objects.rst:137 +msgid "" +"There are different state types you can choose from. By default, Zammad " +"comes with one state per state type." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``false`` or ``true`` (false if not internal)" +#: ../system/objects.rst:140 +msgid "" +"**new**: for states for tickets that are new and it hasn't been worked on " +"them" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > From" +#: ../system/objects.rst:142 +msgid "" +"**open**: for states for tickets that are in progress and agents are working " +"on them" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.from}``" +#: ../system/objects.rst:144 +msgid "**merged**: for states for tickets that are merged with other tickets" msgstr "" -#: ../system/variables/article.rst:1 +#: ../system/objects.rst:145 msgid "" -"``Joe Doe `` may differ, depends on ``FROM`` of send mail" +"**pending reminder**: for states for tickets that are in progress and you " +"want to set a reminder. (default example: *pending reminder*)" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Web" +#: ../system/objects.rst:147 +msgid "" +"**pending action**: for states for tickets that are waiting for a specified " +"time and then change their state (default example: *pending close*)" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.web}``" +#: ../system/objects.rst:150 +msgid "" +"**closed**: for states for tickets that are finished and do not need to be " +"processed further" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > VIP" +#: ../system/objects.rst:153 +msgid "" +"⚠️ Choosing the correct state type is important! If you are in doubt, have a " +"look on the default states and their types!" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.vip}``" +#: ../system/objects.rst:158 +msgid "Ignore escalation" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Phone" +#: ../system/objects.rst:157 +msgid "" +"Here you can define whether tickets of this state will count to escalation " +"time or not." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.phone}``" +#: ../system/objects.rst:161 +msgid "" +"You can create a note for the state to inform other admins about the state. " +"This has no effect on tickets." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Note" +#: ../system/objects.rst:165 +msgid "Set the state to *active* or *inactive*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.note}``" +#: ../system/objects.rst:167 +msgid "" +"it is technically possible to set all states to inactive. To keep Zammad " +"working in such a case, the inactive flag of one of the states is ignored." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Mobile" +#: ../system/objects.rst:194 +msgid "Ticket state example" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.mobile}``" +#: ../system/objects.rst:174 +msgid "" +"Let's assume we want to create a new state which indicates that the ticket " +"has to wait for a response of a third party (e.g. service contractor or " +"manufacturer) and we want to to be able to set a reminder." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Login" +#: ../system/objects.rst:178 +msgid "" +"First we give the new state a proper name. In this example we call it " +"\"waiting for manufacturer\"." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.login}``" +#: ../system/objects.rst:181 +msgid "" +"As state type we choose \"pending reminder\". This indicates that the ticket " +"is still open and we can set a reminder. This reminder can be useful if our " +"manufacturer sometimes isn't responding or we want to remind him to give us " +"an answer." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Lastname" +#: ../system/objects.rst:186 +msgid "" +"We choose \"no\" for \"ignore escalation\" because we want to escalate the " +"tickets even if we are waiting on the manufacturer's feedback." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.lastname}``" +#: ../system/objects.rst:189 +msgid "The **result** in the creation dialog will look like this:" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Firstname" +#: ../system/objects.rst:0 +msgid "Screenshot showing ticket state creation dialog with example" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.firstname}``" +#: ../system/objects.rst:199 +msgid "Ticket Priority" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Fax" +#: ../system/objects.rst:201 +msgid "" +"If the pre-configured priorities aren't enough for you or you want to change " +"them, you can do so by clicking on the cogwheel icon in the priority row in " +"the ticket tab:" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.fax}``" +#: ../system/objects.rst:None +msgid "Screenshot showing highlighted ticket priority attribute" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Email" +#: ../system/objects.rst:226 +msgid "Handling of priorities" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.email}``" +#: ../system/objects.rst:210 +msgid "" +"In the priority configuration screen, you can add new priorities, disable " +"priorities or change priorities." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Department" +#: ../system/objects.rst:0 +msgid "Screenshot showing table of default ticket priorities" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.department}``" +#: ../system/objects.rst:218 +msgid "" +"To add a new priority, click on the \"New Priority\" button in the top right " +"corner. To change an existing priority, simply click on the affected " +"priority. This opens an edit dialog." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Address" +#: ../system/objects.rst:222 +msgid "" +"You can also clone a priority or set them to \"Default for new tickets\" by " +"clicking on the ⁝ action button and select the desired function." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.address}``" +#: ../system/objects.rst:225 +msgid "" +"*Default for new tickets* means that this priority is used for every newly " +"created ticket." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created" +#: ../system/objects.rst:248 +msgid "Priorities in detail" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_at}``" +#: ../system/objects.rst:229 +msgid "Below you can find a description for each field and option." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Cc" +#: ../system/objects.rst:232 +msgid "" +"This is the name of the priority and what you and your agents are seeing " +"when choosing a priority somewhere (e.g. in tickets, trigger configuration)." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.cc}``" +#: ../system/objects.rst:242 +msgid "Highlight color" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``jdoe@example.com, company@example.com``" +#: ../system/objects.rst:237 +msgid "" +"Switch between *Low priority* (light blue), *High priority* (red) and - " +"(default). This affects the displayed color for ticket titles in overviews." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Text" +#: ../system/objects.rst:241 +msgid "The color options are currently limited to the mentioned options." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.body}``" +#: ../system/objects.rst:245 +msgid "" +"You can create a note for the priority to inform other admins about the " +"priority. This has no effect on tickets." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Test`` without formatting (plain)" +#: ../system/objects.rst:249 +msgid "Set the priority to *active* or *inactive*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article Text as HTML (not referenced)" +#: ../system/objects/external-data-source-example.rst:2 +msgid "External Data Source" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.body_as_html}``" +#: ../system/objects/external-data-source-example.rst:4 +msgid "" +"We assume you already had a look on :doc:`types` where you can find a " +"description of the individual fields." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Test`` with formatting" +#: ../system/objects/external-data-source-example.rst:7 +msgid "" +"To reproduce this example, choose a category you want to add a custom field, " +"click on *New Attribute* and select *External data source field* under " +"*Format*." msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "Ticket > Article#" +#: ../system/objects/external-data-source-example.rst:11 +msgid "" +"Our example story is to fetch data from an external product database. We " +"want to add our products to the tickets so that the products can be searched " +"and chosen from a list and also create a link to the product website." msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "``#{ticket.article_count}``" +#: ../system/objects/external-data-source-example.rst:16 +msgid "Base configuration" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``1`` number of ticket articles" +#: ../system/objects/external-data-source-example.rst:None +msgid "Initial steps to configure external data source object type" msgstr "" -#: ../system/variables/config.rst:2 -msgid "Config" +#: ../system/objects/external-data-source-example.rst:25 +msgid "Name: *product*" msgstr "" -#: ../system/variables/config.rst:6 -msgid "" -"Below you'll find config related variables. These hold useful configuration " -"information that you can use within e.g. triggers to show necessary " -"information to your customer." +#: ../system/objects/external-data-source-example.rst:26 +msgid "Display: *Product*" msgstr "" -#: ../system/variables/config.rst:11 -msgid "Config Variables" +#: ../system/objects/external-data-source-example.rst:29 +msgid "External data source configuration" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Fully Qualified Domain Name" +#: ../system/objects/external-data-source-example.rst:31 +msgid "" +"First, enter the search URL making sure it contains ``#{search.term}`` as a " +"parameter:" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.fqdn}``" +#: ../system/objects/external-data-source-example.rst:34 +msgid "**Example:** ``https://dummyjson.com/products/search?q=#{search.term}``" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``zammad.example.com``" +#: ../system/objects/external-data-source-example.rst:36 +msgid "" +"After that, head down to the preview section and enter a search input for " +"the external data source." msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Ticket Hook" +#: ../system/objects/external-data-source-example.rst:39 +msgid "**Example:** ``mac``" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.ticket_hook}``" +#: ../system/objects/external-data-source-example.rst:41 +msgid "Then you can find a preview of the response data below:" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``Ticket#``" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of JSON response based on search term" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > HTTP type" +#: ../system/objects/external-data-source-example.rst:48 +msgid "" +"We recommend using the preview to have a look on the structure. There is a " +"top-level element called ``products``. One level below, you can find the " +"attributes ``id`` and ``title``." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.http_type}``" +#: ../system/objects/external-data-source-example.rst:52 +msgid "**Search result response based on search from example:**" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``https`` or ``http``" +#: ../system/objects/external-data-source-example.rst:119 +msgid "" +"To tell the remote system that the desired data is located below the " +"``products`` level, you have to put it in the field *Search result list key*." msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > SystemID" +#: ../system/objects/external-data-source-example.rst:122 +msgid "" +"After inserting ``products`` in the mentioned field, you get an extended " +"preview. You can find an additional box *Search result list* with a JSON " +"structure. This is the same response as before but stripped from the upper " +"``products`` element by the external data source." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.system_id}``" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of JSON response search result list" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``31`` (value between 1 and 99)" +#: ../system/objects/external-data-source-example.rst:132 +msgid "" +"Now you need to provide the keys for the search result values and labels. As " +"already mentioned, we are looking for the ``id`` and the ``title`` of our " +"products. If you haven't already, it is now a good time to look at the " +"preview of the *Search result list*." msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Organization" +#: ../system/objects/external-data-source-example.rst:197 +msgid "" +"After locating our two keys, we insert them in *search result value key* " +"(``id``) and in *Search result label key* (``title``)." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.organization}``" +#: ../system/objects/external-data-source-example.rst:200 +msgid "" +"Basically, we configured the external data source already and we can see a " +"table in the preview section:" msgstr "" -#: ../system/variables/config.rst:1 -msgid "" -"``Zammad GmbH`` value set in `Branding `_" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of product table based on search term" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Product Name" +#: ../system/objects/external-data-source-example.rst:208 +msgid "" +"According to our example story, now just the *Link template* is missing." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.product_name}``" +#: ../system/objects/external-data-source-example.rst:210 +msgid "" +"Please note that this is an optional feature. If you don't want to use such " +"links, of course you don't have to configure it." msgstr "" -#: ../system/variables/config.rst:1 +#: ../system/objects/external-data-source-example.rst:213 msgid "" -"``Helpdesk`` value set in `Branding `_" +"We can add now an address where additional product information can be found." msgstr "" -#: ../system/variables/current-user.rst:2 -msgid "Current User" +#: ../system/objects/external-data-source-example.rst:215 +msgid "Example: ``https://your_domain.com/q=#{ticket.product}``" msgstr "" -#: ../system/variables/current-user.rst:6 -msgid "" -"Current user variables always return values of the current user that caused " -"e.g. a trigger to run." +#: ../system/objects/external-data-source-example.rst:217 +msgid "In the example, the parameter means:" msgstr "" -#: ../system/variables/current-user.rst:8 -msgid "" -"Due to the above fact, these variables are often not (yet) set or available " -"for usage." +#: ../system/objects/external-data-source-example.rst:219 +msgid "``#{}``: \"Frame\" for the insertion of information" msgstr "" -#: ../system/variables/current-user.rst:10 -msgid "" -"In situations where e.g. schedulers or triggers run, this most likely is " -"nothing you want to use." +#: ../system/objects/external-data-source-example.rst:220 +msgid "``ticket``: object level, where you create your custom object" msgstr "" -#: ../system/variables/current-user.rst:13 -msgid "Current User Variables" +#: ../system/objects/external-data-source-example.rst:221 +msgid "``product``: name of the (custom) object" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Web" +#: ../system/objects/external-data-source-example.rst:223 +msgid "" +"After configuring your *Link template*, there will be another column in the " +"preview. Hovering on the icons in the *Link* column will show you where it " +"forwards you." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.web}``" +#: ../system/objects/external-data-source-example.rst:232 +msgid "" +"In our example, one of the links looks like: https://your_domain.com/q=6, " +"where the 6 is the product id." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``https://zammad.org`` or empty if not set" +#: ../system/objects/external-data-source-example.rst:235 +msgid "You can find more information regarding the URL in :doc:`types`." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > VIP" +#: ../system/objects/includes/adding-values-hint.include.rst:3 +msgid "" +"Adding values can be tricky for first timers, don't forget to press \"➕ " +"Add\" after typing your values. Otherwise you may loose a value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.vip}``" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:1 +#: ../system/objects/includes/reposition-values.include.rst:1 +msgid "**↕️ This field type allows the positioning of its values ↔️**" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``false`` or ``true``" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:3 +msgid "" +"In order to re-arrange the field values, first edit the field. Then you can " +"use ☰ to drag the values in question to the correct position. If you want to " +"change the layer depth, double click on ☰. With it you can cycle through the " +"available layers." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Web" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:8 +msgid "When you're ready, submit your changes to save the object attribute." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.web}``" +#: :0 ../system/objects/types.rst:0 +msgid "" +"Screencast showing how to re-position values on tree select like\n" +"fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > VIP" +#: ../system/objects/includes/reposition-values.include.rst:3 +msgid "" +"In order to re-arrange the field values, edit the field and scroll below the " +"values. Make sure to tick the option \"Use custom option sort\"." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.vip}``" +#: ../system/objects/includes/reposition-values.include.rst:8 +msgid "" +"If you do not tick this field, all manual positioning you did above will be " +"lost upon saving! ☠️" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Phone" +#: ../system/objects/includes/reposition-values.include.rst:11 +msgid "" +"Now use ☰ to drag the values in question to the correct position. When " +"you're ready, submit your changes to save the object attribute." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.phone}``" +#: :0 ../system/objects/types.rst:0 +msgid "Screencast showing how to re-position values" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``004930123456789`` or empty if not set" +#: ../system/objects/includes/url-template-hint.include.rst:3 +msgid "" +"This field allows using :ref:`URL fields (Link Templates) `." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Note" +#: ../system/objects/permissions.rst:2 +#, fuzzy +msgid "Attribute Permissions" +msgstr "Verze" + +#: ../system/objects/permissions.rst:7 +msgid "" +"In the object attributes configuration you can define if a field is shown " +"and if the input in the field is mandatory, separated by different screens " +"and for different :doc:`roles/permissions `." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.note}``" +#: ../system/objects/permissions.rst:17 +msgid "Screenshot shows object attribute permission table" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Some note to this user`` or empty if not set" +#: ../system/objects/permissions.rst:17 +msgid "" +"Some of the possible permissions and screen options for a user object " +"attribute." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Mobile" +#: ../system/objects/permissions.rst:19 +msgid "" +"Based on the object context (ticket, agent, organization, user), the " +"selectable roles (to be precise: the required permissions) and screens " +"differ. Be aware that these settings aren't affecting data creation via " +"other channels than the UI." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.mobile}``" +#: ../system/objects/permissions.rst:24 +msgid "" +"If you want to have further customization possibilities, you should have a " +"look at the :doc:`core workflows `." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``0049176123456789`` or empty if not set" +#: ../system/objects/permissions.rst:28 +msgid "Screens" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Login" +#: ../system/objects/permissions.rst:30 +msgid "" +"In the table below you can find an overview about the different permissions " +"and the available screens Zammad distinguishes between." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.login}``" +#: ../system/objects/permissions.rst:37 +msgid "Screen" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Lastname" +#: ../system/objects/permissions.rst:38 +msgid "Available for" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.lastname}``" +#: ../system/objects/permissions.rst:40 +msgid "create" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Firstname" +#: ../system/objects/permissions.rst:41 ../system/objects/permissions.rst:52 +#: ../system/objects/permissions.rst:59 ../system/objects/permissions.rst:73 +msgid "admin.user" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.firstname}``" +#: ../system/objects/permissions.rst:42 ../system/objects/permissions.rst:53 +#: ../system/objects/permissions.rst:60 +msgid "admin.organization" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``John`` or empty if not set" +#: ../system/objects/permissions.rst:43 ../system/objects/permissions.rst:54 +#: ../system/objects/permissions.rst:61 +msgid "admin.group" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Fax" +#: ../system/objects/permissions.rst:44 +msgid "Creation dialog for not yet existing data" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.fax}``" +#: ../system/objects/permissions.rst:45 +msgid "create_middle" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``004930123464789`` or empty if not set" +#: ../system/objects/permissions.rst:46 ../system/objects/permissions.rst:50 +#: ../system/objects/permissions.rst:57 ../system/objects/permissions.rst:66 +#: ../system/objects/permissions.rst:70 +msgid "ticket.customer" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Email" +#: ../system/objects/permissions.rst:47 ../system/objects/permissions.rst:51 +#: ../system/objects/permissions.rst:58 ../system/objects/permissions.rst:69 +msgid "ticket.agent" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.email}``" +#: ../system/objects/permissions.rst:48 +msgid "Ticket create dialog (middle section)" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``jdoe@customer.tld``" +#: ../system/objects/permissions.rst:49 +msgid "edit" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Department" +#: ../system/objects/permissions.rst:55 +msgid "Editing dialog for already existing data" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.department}``" +#: ../system/objects/permissions.rst:56 +msgid "view" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Sales`` or empty if not set" +#: ../system/objects/permissions.rst:62 +msgid "View-only dialog for already existing data" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Avatar" +#: ../system/objects/permissions.rst:64 +msgid "(e.g. user or organization from search)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.avatar(60,60)}``" +#: ../system/objects/permissions.rst:65 +msgid "signup" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "avatar picture with width and height in pixel (e.g. 60,60)" +#: ../system/objects/permissions.rst:67 +msgid "Sign-up screen for new customers" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Address" +#: ../system/objects/permissions.rst:68 +msgid "invite_customer" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.address}``" +#: ../system/objects/permissions.rst:71 +msgid "" +"Customer invitation screen (from :doc:`First Steps ` area)" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Some street 1, 12345 Berlin`` or empty if not set" +#: ../system/objects/permissions.rst:72 +msgid "invite_agent" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated at" +#: ../system/objects/permissions.rst:74 +msgid "" +"Agent invitation screen (from :doc:`First Steps ` area)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_at}``" +#: ../system/objects/permissions.rst:78 +msgid "Screen Options" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC``" +#: ../system/objects/permissions.rst:80 +msgid "" +"For the different screens you can select \"show\" and \"required\" options." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Phone" +#: ../system/objects/permissions.rst:82 +msgid "**shown:** Show (check) or hide (uncheck) a field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.phone}``" +#: ../system/objects/permissions.rst:83 +msgid "" +"**required:** Set a field to mandatory (check). Forces users (via UI and " +"API) to populate the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Shared organization" +#: ../system/objects/types.rst:7 +msgid "Example external data source" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.shared}``" +#: ../system/objects/types.rst:2 +msgid "Attribute types" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Note" +#: ../system/objects/types.rst:4 +msgid "" +"When adding a new object attribute, you can choose between the following " +"attribute types." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.note}``" +#: ../system/objects/types.rst:14 +msgid "" +"You cannot change the attribute format / type as soon as it is applied. If " +"you no longer need an object attribute, consider disabling it instead of " +"removing." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``A note to the organization of the user`` or empty if not set" +#: ../system/objects/types.rst:18 +msgid "**What about the translation of my attributes?**" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Name" +#: ../system/objects/types.rst:20 +msgid "" +"For some attribute types you can decide if they should be translatable or " +"not. To be precise, it works only for the selectable fields because the " +"possible choices are known and limited. For the following attribute types, " +"you can set the translatable flag:" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.name}``" +#: ../system/objects/types.rst:25 +msgid "*Boolean field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``Zammad GmbH``" +#: ../system/objects/types.rst:26 +msgid "*Single selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Domain based assignment" +#: ../system/objects/types.rst:27 +msgid "*Multiple selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.domain_assignment}``" +#: ../system/objects/types.rst:28 +msgid "*Single tree selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Domain" +#: ../system/objects/types.rst:29 +msgid "*Multiple tree selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.domain}``" +#: ../system/objects/types.rst:31 +msgid "" +"For these types, you can find an additional field *Translate field contents*:" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``zammad.com`` or empty if not set" +#: ../system/objects/types.rst:0 +msgid "Screenshot showing translatable attribute types" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > VIP" +#: ../system/objects/types.rst:38 +msgid "Screenshot with example of translatable attribute type" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.vip}``" +#: ../system/objects/types.rst:45 +msgid "Boolean field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Note" +#: ../system/objects/types.rst:41 +msgid "" +"Provides a drop-down field with display values for ``true`` and ``false``. " +"Setting a default is mandatory." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.note}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Boolean fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Mobile" +#: ../system/objects/types.rst:55 +msgid "Date field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.mobile}``" +#: ../system/objects/types.rst:48 +msgid "Provides a date picker field and does not allow default values." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Login" +#: ../system/objects/types.rst:52 +msgid "Default time diff (hours)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.login}``" +#: ../system/objects/types.rst:51 +msgid "" +"This setting helps the user by highlighting the day from now plus the " +"provided value. It *does not* pre-fill the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Lastname" +#: ../system/objects/types.rst:0 +msgid "Available settings for Date fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.lastname}``" +#: ../system/objects/types.rst:73 +msgid "Date & time field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Firstname" +#: ../system/objects/types.rst:58 +msgid "Provides a date and time picker – does not allow default values" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.firstname}``" +#: ../system/objects/types.rst:62 +msgid "Allow future" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Fax" +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the future." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.fax}``" +#: ../system/objects/types.rst:66 +msgid "Allow past" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Email" +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the past." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.email}``" +#: ../system/objects/types.rst:70 +msgid "Default time diff (minutes)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Department" +#: ../system/objects/types.rst:69 +msgid "" +"This setting helps the user by highlighting the day from now plus the " +"provided value. It does not pre-fill the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.department}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Date & time fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Web" +#: ../system/objects/types.rst:86 +msgid "Integer field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.web}``" +#: ../system/objects/types.rst:76 +msgid "" +"Provides an input field that allows integer usage only. You may define a " +"default value. You cannot enforce comma separation." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > VIP" +#: ../system/objects/types.rst:80 +msgid "Minimal" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.vip}``" +#: ../system/objects/types.rst:80 +msgid "The minimal value the field accepts." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Phone" +#: ../system/objects/types.rst:83 +msgid "Maximal" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.phone}``" +#: ../system/objects/types.rst:83 +msgid "The maximum value the field accepts." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Note" +#: ../system/objects/types.rst:0 +msgid "Available settings for Integer fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.note}``" +#: ../system/objects/types.rst:99 +msgid "Multiple selection field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Mobile" +#: ../system/objects/types.rst:89 +msgid "" +"Provides a selection field that allows the selection of one or more out of " +"several. This field does allow setting a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.mobile}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Multiple selection fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Login" +#: ../system/objects/types.rst:112 +msgid "Single selection field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.login}``" +#: ../system/objects/types.rst:102 +msgid "" +"Provides a drop-down field that allows selection of one value out of " +"several. This field does allow setting a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Lastname" +#: ../system/objects/types.rst:0 +msgid "Available settings for Single selection fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.lastname}``" +#: ../system/objects/types.rst:142 +msgid "Textarea field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Firstname" +#: ../system/objects/types.rst:115 +msgid "" +"Provides a text area input field (multiple lines) and thus allows e.g. new " +"lines. You can set a default field value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.firstname}``" +#: ../system/objects/types.rst:120 +msgid "" +"Please note that this field *does not* support text formatting or HTML " +"content (rich text)." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Fax" +#: ../system/objects/types.rst:123 +msgid "**🥵 This field can consume a lot of visual space**" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.fax}``" +#: ../system/objects/types.rst:125 +msgid "" +"Depending on where you use this field type, it may use a lot of visual space " +"if you provide a lot of text. This may be an issue to work with." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Email" +#: ../system/objects/types.rst:130 +msgid "Default" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.email}``" +#: ../system/objects/types.rst:129 +msgid "" +"The here provided text will be shown within the text area field or new data " +"sets." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Department" +#: ../system/objects/types.rst:134 ../system/objects/types.rst:160 +msgid "Maxlength" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.department}``" +#: ../system/objects/types.rst:0 ../system/objects/types.rst:160 +msgid "You can pick the maximum length of the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Avatar" +#: ../system/objects/types.rst:0 +msgid "The default length of this object is ``500``." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.avatar(60,60)}``" +#: ../system/objects/types.rst:139 +msgid "Rows" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Address" +#: ../system/objects/types.rst:0 +msgid "" +"Change the number of rows to dislay so that you can use only the space you " +"really need." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.address}``" +#: ../system/objects/types.rst:0 +msgid "The default number of rows is ``4``." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created at" +#: ../system/objects/types.rst:0 +msgid "Available settings for Textarea fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_at}``" +#: ../system/objects/types.rst:165 +msgid "Text field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Avatar" +#: ../system/objects/types.rst:145 +msgid "Provides a text field (one line) and allows choosing a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.avatar(60,60)}``" +#: ../system/objects/types.rst:148 +msgid "" +"Defines the type of the input field. This allows e.g. your browser to ensure " +"that you provide the specific type." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Address" +#: ../system/objects/types.rst:152 +msgid "Currently available:" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.address}``" +#: ../system/objects/types.rst:155 +msgid "Phone" msgstr "" -#: ../system/variables/ticket.rst:6 -msgid "" -"Below you can find all available ticket-based variables within Zammad. These " -"can be called via Triggers for example. If you're unsure if Zammad does " -"support variables at the point you're at, you can try to type ``::`` to " -"check." +#: ../system/objects/types.rst:156 +msgid "Text" msgstr "" -#: ../system/variables/ticket.rst:12 -msgid "Ticket Variables" +#: ../system/objects/types.rst:157 +msgid "Url *(URL fields disable link-template availability)*" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Web" +#: ../system/objects/types.rst:0 +msgid "Available settings for Text fields" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.web}``" +#: ../system/objects/types.rst:174 +msgid "Single tree selection field" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > VIP" +#: ../system/objects/types.rst:168 +msgid "" +"Provides a select-like field with up to 6 layers of options. Does not allow " +"setting a default value." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.vip}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Tree Select fields" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Phone" +#: ../system/objects/types.rst:183 +msgid "Multiple tree selection field" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.phone}``" +#: ../system/objects/types.rst:177 +msgid "" +"Provides a select-like field with up to 6 layers of options allowing the " +"selection of multiple values. Does not allow setting a default value." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Note" +#: ../system/objects/types.rst:302 +msgid "External Data Source field" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.note}``" +#: ../system/objects/types.rst:186 +msgid "" +"Provides a searchable field which fetches data from an external system. This " +"can be useful if you have data outside of Zammad and don't want to maintain " +"both data sources." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Mobile" +#: ../system/objects/types.rst:190 +msgid "The feature works as follows:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.mobile}``" +#: ../system/objects/types.rst:192 +msgid "" +"Zammad sends a query with a search string (free text from agent or based on " +"a variable) in a pre-defined format (\"Search URL\") to an external system." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Login" +#: ../system/objects/types.rst:195 +msgid "" +"This external system searches for matches and provides a response as a JSON " +"structure to Zammad." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.login}``" +#: ../system/objects/types.rst:197 +msgid "" +"Zammad just looks for the defined list and value keys, reads the content and " +"displays the value to the user. There is no search on Zammad side." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Lastname" +#: ../system/objects/types.rst:201 +msgid "" +"The usage of a PostgreSQL database for Zammad is required. In any other " +"case, Zammad will hide the external data source type and you are not able to " +"use it. If you want to use this feature, consider to :docs:`migrate your " +"database `." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.lastname}``" +#: ../system/objects/types.rst:205 +msgid "Currently, only ``GET`` is supported as request method." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Firstname" +#: ../system/objects/types.rst:206 +msgid "" +"The data structure must be in JSON format and provide the objects in an " +"array." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.firstname}``" +#: ../system/objects/types.rst:208 +msgid "" +"The endpoint for the external data source has to support search. On Zammad " +"side, there is no search/logic implemented; however, you can define the " +"output key and value based on the result(s) from the response (which " +"provides already filtered content based on the search)." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Fax" +#: ../system/objects/types.rst:212 +msgid "" +"If you receive more results as expected, your external data source search " +"may not work properly or the structure of the URL is not correct. You should " +"get in touch with a responsible person from the external system." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.fax}``" +#: ../system/objects/types.rst:217 +msgid "" +"Please have a look :doc:`at our example `, where you can find a possible configuration for a public " +"dummy endpoint." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Email" +#: ../system/objects/types.rst:0 +msgid "Available settings for external data source fields" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.email}``" +#: ../system/objects/types.rst:242 +msgid "Search URL" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Department" +#: ../system/objects/types.rst:227 +msgid "" +"Set your endpoint where Zammad fetches the data. Please make sure to include " +"a valid search :doc:`variable ` as an URL parameter. " +"Example for a free text search at user input: ``#{search.term}``" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.department}``" +#: ../system/objects/types.rst:232 +msgid "" +"If in doubt, ask the responsible person for the external data source how " +"they expect the structure of the URL." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Avatar" +#: ../system/objects/types.rst:236 +msgid "" +"Depending on your search variable, the preview might work or not. The reason " +"is that the context might not be available and it is no bug." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.avatar(60,60)}``" +#: ../system/objects/types.rst:239 +msgid "" +"Please also make sure to use a variable which is available in your object " +"context. For example you won't be able to search for a ticket in a user " +"object context." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Address" +#: ../system/objects/types.rst:252 +msgid "SSL Verification" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.address}``" +#: ../system/objects/types.rst:245 +msgid "Here you can switch the SSL verification to no." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated at" +#: ../system/objects/types.rst:249 +msgid "" +"If your external data source system is using self signed certificates, " +"please have a look :doc:`here ` for " +"further information about how to handle them in Zammad, so you can keep the " +"SSL verification activated." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_at}``" +#: ../system/objects/types.rst:258 +msgid "HTTP Authentication" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Title" +#: ../system/objects/types.rst:255 +msgid "" +"If your external data source requires an authentication, you can set it " +"here. You can leave it empty or choose between *Basic Authentication* or " +"*Authentication Token* (selecting one of the two methods leads to additional " +"fields where you can enter your credentials/token)." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.title}``" +#: ../system/objects/types.rst:265 +msgid "Search result list key" msgstr "" -#: ../system/variables/ticket.rst:1 +#: ../system/objects/types.rst:261 msgid "" -"``My amazing Subject`` (normally subject, can be edited within Interface and " -"thus differ)" +"Defines the level in the JSON structure which provides the list with search " +"results. You can leave it empty, if the data is already provided as an " +"array. If you have to go deeper in the structure, you can provide a path " +"with ``.`` as separators, e.g. ``key.subkey.sub-sub-key``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Accounted Time" +#: ../system/objects/types.rst:271 +msgid "Search result value key" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.time_unit}``" +#: ../system/objects/types.rst:268 +msgid "" +"Defines the attribute in the structure in which your external data source " +"provides the *value* for your data. An example would be a product *number*. " +"If you have to go deeper in the structure, you can provide a path with ``.`` " +"as separators, e.g. ``key.subkey.sub-sub-key``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``1``, ``2.75`` or empty response" +#: ../system/objects/types.rst:277 +msgid "Search result label key" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Tags" +#: ../system/objects/types.rst:274 +msgid "" +"Defines the attribute in the structure in which your external data source " +"provides the *label* for your data. An example would be a product *name*. If " +"you have to go deeper in the structure, you can provide a path with ``.`` as " +"separators, e.g. ``key.subkey.sub-sub-key``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.tags}``" +#: ../system/objects/types.rst:280 +msgid "" +"In the preview area, you can find the following items (depending on your " +"configuration above):" msgstr "" -#: ../system/variables/ticket.rst:1 +#: ../system/objects/types.rst:283 msgid "" -"Currently not available, see `Issue 2769 `_" +"**Error/hint message** (only if configuration is not complete): Zammad tells " +"you, if there is a problem and what you should change in your configuration." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > State > Name" +#: ../system/objects/types.rst:286 +msgid "" +"**Search field**: search for an existing attribute in the data source to get " +"a preview. This is required for the fields below to show up." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.state.name}``" +#: ../system/objects/types.rst:288 +msgid "" +"**Search result response** (only if configuration is not complete): here you " +"can find a syntax highlighted JSON preview of the response, based on the " +"search term you entered." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``new``, ``open``, ..." +#: ../system/objects/types.rst:291 +msgid "" +"**Search result list** (only if *search result list key* is properly set): " +"output of the structure under the configured *search result list key*." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Priority > Name" +#: ../system/objects/types.rst:294 +msgid "" +"**Preview table** (when fully configured): Zammad shows you a table which " +"includes the found items based on the search string (value, label and " +"optional link). You can use this preview if you don't have the complete data " +"structure of the external system in mind." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.priority.name}``" +#: ../system/objects/types.rst:299 +msgid "" +"An example of a configured external data source field from agent perspective:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2 normal``" +#: ../system/objects/types.rst:0 +msgid "Screencast showing the search for a product in a ticket" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Pending till" +#: ../system/objects/types.rst:307 +msgid "URL fields (Link-Template)" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.pending_time}``" +#: ../system/objects/types.rst:311 +msgid "" +"This function is restricted to Text, Select and External data source types " +"only." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not set" +#: ../system/objects/types.rst:314 +msgid "" +"Link-Templates are an amazing way to dynamically generate URLs. They allow " +"you to integrate other systems better without having to manually copy data " +"from Zammad if possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Web" +#: ../system/objects/types.rst:320 +msgid "" +"Another great way of communicating with another system may be Zammad's :doc:" +"`Webhooks `." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.web}``" +#: ../system/objects/types.rst:323 +msgid "" +"After filling a link-template enabled field, an URL icon will appear on its " +"right. Clicking on the icon opens a new tab." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``https://zammad.com`` or empty if not set" +#: ../system/objects/types.rst:328 +msgid "" +"Even though Zammad displays the link template within object edit and create " +"screens, the function is optional. It's only active if you populate the " +"field." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > VIP" +#: ../system/objects/types.rst:333 +msgid "" +"What's the difference between URL and text fields with link template...?!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.vip}``" +#: ../system/objects/types.rst:335 +msgid "" +"Both fields have different use cases. Use ``text`` type text fields when " +"ever you have a *static* url that requires dynamic parameters. If you " +"require a drag & drop like field that you can put in any URL, use ``URL`` " +"type text fields." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Phone" +#: ../system/objects/types.rst:340 +msgid "" +"The difference is easier to spot when comparing the fields directly, below " +"screencast shows the result - the dynamic approach uses existing values in " +"the moment of updating to built the URL - e.g. ``https://google.com/search?" +"q=cookies`` - while the URL approach uses the actual URL of the field - e.g. " +"``https://zammad.com``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.phone}``" +#: ../system/objects/types.rst:None +msgid "" +"Screencast showing the differents in between URL and text type fields with " +"actual values" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Note" +#: ../system/objects/types.rst:352 +msgid "How does this work...?!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.note}``" +#: ../system/objects/types.rst:354 +msgid "" +"As an example, let's say you have an attribute called ``amazing_attribute`` " +"and you want to open a google search directly with the input from that field." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Mobile" +#: ../system/objects/types.rst:357 +msgid "" +"Providing the link-template field below allows you to do so: ``https://www." +"google.com/search?q=#{ticket.amazing_attribute}``" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.mobile}``" +#: ../system/objects/types.rst:362 +msgid "" +"You can use any :doc:`Zammad variable ` as long as it's " +"available in the moment you need it." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Login" +#: ../system/objects/types.rst:365 +msgid "" +"As a result, you are redirected to Google with a search for the value of the " +"attribute, if you click on the button in the ticket (as you can see in the " +"screencast above)." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.login}``" +#: ../system/packages.rst:2 +msgid "Packages" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``agent``" +#: ../system/packages.rst:4 +msgid "That's the package management-area." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Lastname" +#: ../system/packages.rst:6 +msgid "Individual add-ons for Zammad can be installed and managed here." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.lastname}``" +#: ../system/sessions.rst:2 +msgid "Sessions" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Mustermann`` or empty if not set" +#: ../system/sessions.rst:4 +msgid "" +"Sessions management allows reviewing currently known user sessions and " +"allows to end these. The session timeout is affected by :ref:" +"`security_session_timeout` configurations from security settings." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Firstname" +#: ../system/sessions.rst:None +msgid "Screenshot showing Zammad's session management" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.firstname}``" +#: ../system/sessions.rst:13 +msgid "Zammad will provide the following information:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Max`` or empty if not set" +#: ../system/sessions.rst:16 +msgid "" +"The user account this session entry belongs to. It can be normal if a user " +"has several sessions in the list. This can be due to changed browser " +"information or if you use e.g. single sign on methods where the user does " +"not use the log off button." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Fax" +#: ../system/sessions.rst:22 +msgid "Browser" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.fax}``" +#: ../system/sessions.rst:22 +msgid "The browser agent communicated to Zammad." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Email" +#: ../system/sessions.rst:40 +msgid "Location" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.email}``" +#: ../system/sessions.rst:25 +msgid "" +"The anticipated location based on the users IP address. Depending on the IP " +"address the result shown may differ. This option depends on :doc:`/settings/" +"system/services`." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``agent@company.tld`` or empty if not set" +#: ../system/sessions.rst:29 +msgid "The following information can be shown:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Department" +#: ../system/sessions.rst:33 +msgid "IP address" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.department}``" +#: ../system/sessions.rst:32 +msgid "" +"Either if you set *Geo IP services* to inactive or you're using internal IP " +"address which do not provide location information." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Support`` or empty if not set" +#: ../system/sessions.rst:40 +msgid "Country (or Country + City)" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Avatar" +#: ../system/sessions.rst:36 +msgid "" +"If *Geo IP services* is enabled only. Depends on how detailed the available " +"IP address information are." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.avatar(60,60)}``" +#: ../system/sessions.rst:39 +msgid "" +"Be aware that results can be inaccurate - this technically is not an error." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Address" +#: ../system/sessions.rst:43 +msgid "Age" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.address}``" +#: ../system/sessions.rst:43 +msgid "Provides the time when the session initially has been created." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Shared organization" +#: ../system/sessions.rst:50 +msgid "Update" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.shared}``" +#: ../system/sessions.rst:46 +msgid "" +"Provides the time the user used this session to open Zammad. This timestamp " +"is only updated if the user e.g. reloads, not during normal work on tickets." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Note" +#: ../system/sessions.rst:50 +msgid "This timestamp is being used for the session timeout." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.note}``" +#: ../system/sessions.rst:53 +msgid "" +"Use the delete button to remove a single session on behalf of your user." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Name" +#: ../system/subscription.rst:2 +msgid "Subscription (SaaS)" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.name}``" +#: ../system/subscription.rst:4 +msgid "" +"The subscription settings page allows you to configure your instances " +"package and number of agents required." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Zammad GmbH`` or empty if not set" +#: ../system/subscription.rst:9 +msgid "" +"This setting section is only available for Hosted setups. If you're looking " +"for on premise support contracts, please see the `Zammad pricing page " +"`_." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Domain based assignment" +#: ../system/subscription.rst:14 ../system/subscription.rst:34 +msgid "Plan" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.domain_assignment}``" +#: ../system/subscription.rst:16 +msgid "" +"Here you can set up everything affecting your instance subscription " +"functions like number of agents and package." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Domain" +#: ../system/subscription.rst:19 +msgid "" +"On top of the page you can find a subscription summary. You'll find the " +"number of used and available (booked) agent seats there. By using the *see " +"more* link you can also expand an agent list to see the currently configured " +"active agents. This list *does not* count accounts with admin permissions " +"only." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.domain}``" +#: ../system/subscription.rst:None +msgid "" +"Within subscription you can always see how many agents are still\n" +"available to add and who uses the seats." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``domain.tld`` or empty if not set" +#: ../system/subscription.rst:29 +msgid "" +"Learn more on how to manage your agents in general :doc:`here `." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > VIP" +#: ../system/subscription.rst:36 +msgid "" +"This section gives you an overview of the available plans and their " +"functions / limits. If you require a more detailed table, check our " +"`detailed pricing table `_ for more." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.vip}``" +#: ../system/subscription.rst:40 +msgid "" +"Your selection in this step will decide on the base agent price and e.g. " +"agent limits that might apply in the summary step." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Number" +#: ../system/subscription.rst:43 +msgid "" +"The green *Selected* button will also tell you what plan you're currently in." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.number}``" +#: ../system/subscription.rst:47 +msgid "" +"Trial instances are running at Professional with 3 agents. The plan cannot " +"be changed during the trial for technical reasons, if you require more " +"agents for testing, please contact `our sales team `_ with a reason for the raise request." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``31001``, ``201910731001``, ..." +#: ../system/subscription.rst:None +msgid "" +"Screenshot showing three available packages for a hosted Zammad\n" +"instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > ID" +#: ../system/subscription.rst:57 +msgid "" +"At the bottom of this block you can find a summary where you can adjust the " +"settings of the previous selected plan." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.id}``" +#: ../system/subscription.rst:62 +msgid "" +"Note that upgrading (more agents, higher package) is always possible, " +"however, downgrading will only happen when your billing period renews." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``17``, ``5281``, ..." +#: ../system/subscription.rst:66 +msgid "" +"Upgrading resets your billing period and existing credit will be deducted " +"from the new total." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact (customer)" +#: ../system/subscription.rst:75 +msgid "Billing cycle" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_customer_at}``" +#: ../system/subscription.rst:70 +msgid "" +"You can choose between either monthly or yearly billing. The price per agent " +"will be cheaper if you decide for yearly billing." msgstr "" -#: ../system/variables/ticket.rst:1 +#: ../system/subscription.rst:73 msgid "" -"``2019-10-07 16:25:00 UTC`` or empty if not applicable yet (Please note " -"`Ticket last contact behavior Settings `_ for this)" +"If you're still trying out things and are unsure of the right package for " +"your instance, you may want to choose monthly first and then upgrade to " +"yearly when you're sure." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact" +#: ../system/subscription.rst:83 +msgid "Plan: (Starter|Professional|Plus) - Agents" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_at}``" +#: ../system/subscription.rst:78 +msgid "Choose the number of agents you require for your instance." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact (agent)" +#: ../system/subscription.rst:80 +msgid "" +"Keep in mind that some packages may have agent limits. Depending on the " +"previous chosen package, you won't be able to exceed specific agent numbers. " +"Also note that setting less agents than currently configured is not possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_agent_at}``" +#: ../system/subscription.rst:86 +msgid "Total" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable yet" +#: ../system/subscription.rst:86 +msgid "This will be the net total you're going to be billed." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Note" +#: ../system/subscription.rst:88 +msgid "" +"By using the *Update subscription* button, the instance package will be " +"adjusted immediately. If you didn't provide a payment method yet, Zammad " +"will request you to provide one at this point." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.note}``" +#: ../system/subscription.rst:94 +msgid "" +"In case you're still within the trial period, this means that the trial will " +"be over immediately!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Note about this group``" +#: ../system/subscription.rst:97 +msgid "Down- or upgrading during the trial period *is not* possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Name" +#: ../system/subscription.rst:None +msgid "Screenshot showing payment options and a pricing summary" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.name}``" +#: ../system/subscription.rst:103 +msgid "Billing Information" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Sales``" +#: ../system/subscription.rst:105 +msgid "" +"You can control all billing relevant information like invoices, billing " +"address and the option to cancel your subscription." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Follow-up possible" +#: ../system/subscription.rst:108 +msgid "" +"All adjusted billing information below only affect future invoices. If your " +"invoice was issued wrong, please contact `our sales team `_." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.follow_up_possible}``" +#: ../system/subscription.rst:114 +msgid "Billing address" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``no`` or ``yes``" +#: ../system/subscription.rst:113 +msgid "" +"Provide your company address here, make sure to include the companies name " +"in case required. This address will be referenced on your invoice." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Assign Follow-Ups" +#: ../system/subscription.rst:118 +msgid "VAT ID" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.follow_up_assignment}``" +#: ../system/subscription.rst:117 +msgid "" +"Provide your VAT ID here. If applicable your invoice will not contain German " +"VAT. Please make sure to pay the VAT in your country as required." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Assignment Timeout" +#: ../system/subscription.rst:127 +msgid "Billing Email Address" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.assignment_timeout}``" +#: ../system/subscription.rst:121 +msgid "" +"Usually the instance owner (the person that registered the instance) will " +"receive all emails including the invoices. In case you have your own billing " +"department, you can provide their email address here." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``20`` or empty if not configured" +#: ../system/subscription.rst:125 +msgid "" +"All billing relevant information will then be sent to this email address." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > First response" +#: ../system/subscription.rst:127 +msgid "Invoices are sent as attachment (PDF) to this email address." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.first_response_at}``" +#: ../system/subscription.rst:129 +msgid "" +"Don't forget to press the *Update billing information* button after you " +"changed above settings." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Escalation at" +#: ../system/subscription.rst:None +msgid "" +"Screenshot showing options for billing information within the\n" +"subscription menu" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.escalation_at}``" +#: ../system/subscription.rst:137 +msgid "Payment Method" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable" +#: ../system/subscription.rst:139 +msgid "You can pay via credit card or SEPA mandate." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Web" +#: ../system/subscription.rst:144 +msgid "Credit card" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.web}``" +#: ../system/subscription.rst:142 +msgid "" +"Simply follow the dialogue by clicking *authorize credit card* and confirm -" +"if required by your bank- your consent to Zammad using your card for the " +"payments." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > VIP" +#: ../system/subscription.rst:148 +msgid "SEPA Direct Debit" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.vip}``" +#: ../system/subscription.rst:147 +msgid "" +"Provide the requested information of the bank account holder and update if " +"you're ready. You'll then receive an email with the SEPA mandate." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Phone" +#: ../system/subscription.rst:150 +msgid "" +"Technically there's also the possibility to pay via invoice, however - this " +"method only applies to a fairly low number of instances. Please contact `our " +"sales team `_ for more information." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.phone}``" +#: ../system/subscription.rst:156 +msgid "Cancel Subscription" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Note" +#: ../system/subscription.rst:158 +msgid "" +"Do you want to cancel your subscription? In case you no longer want to use " +"Zammad's SaaS, you can cancel your subscription by using the red *Yes, " +"please cancel my subscription* button." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.note}``" +#: ../system/subscription.rst:162 +msgid "" +"To cancel the description, enter the FQDN of your Zammad instance and " +"provide a reason for your cancellation." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Mobile" +#: ../system/subscription.rst:165 +msgid "" +"Your subscription will end the day after your trial or billing period ends." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.mobile}``" +#: ../system/subscription.rst:None +msgid "Screenshot showing subscription cancellation dialog" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Login" +#: ../system/subscription.rst:174 +msgid "" +"We will remind you about your cancelled subscription several times up front. " +"After the subscription ended all instance data will be removed. A restore " +"*is not* possible after that point!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.login}``" +#: ../system/subscription.rst:178 +msgid "**😖 Cancelled by accident?**" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Lastname" +#: ../system/subscription.rst:180 +msgid "" +"You can always undo the cancellation via the *Yes, undo the cancellation of " +"my subscription* button up to the last subscription day!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.lastname}``" +#: ../system/subscription.rst:0 +msgid "" +"Screenshot showing a red button to cancel the subscription\n" +"cancellation" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Firstname" +#: ../system/subscription.rst:189 +msgid "Payment History" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.firstname}``" +#: ../system/subscription.rst:191 +msgid "" +"The payment history will display a history of all paid invoices. At this " +"point you can also download these in case you need them again." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Fax" +#: ../system/subscription.rst:196 +msgid "" +"You will only find *paid* invoices here. Invoices that are to be billed are " +"not available before the payment is completed." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.fax}``" +#: ../system/subscription.rst:201 +msgid "Date" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Email" +#: ../system/subscription.rst:201 +msgid "Date of the invoice creation." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.email}``" +#: ../system/subscription.rst:204 +msgid "Amount" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Department" +#: ../system/subscription.rst:204 +msgid "Invoice total including VAT if applicable." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.department}``" +#: ../system/subscription.rst:207 +msgid "" +"Contains contract period (monthly or yearly) and hosted plan for the " +"subscription period in question." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Avatar" +#: ../system/subscription.rst:218 +msgid "Payment method / Service period" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.avatar(60,60)}``" +#: ../system/subscription.rst:211 +msgid "" +"Used bank account or credit card as well as the subscription period the " +"invoice is about." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Address" +#: ../system/subscription.rst:216 +msgid "" +"It might happen that the invoice date and subscription period differ. This " +"is nothing to worry about, the subscription periods will be accounted later " +"on." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.address}``" +#: ../system/subscription.rst:222 +msgid "Receipt" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Web" +#: ../system/subscription.rst:221 +msgid "" +"Use the arrow to download the invoice in question. You can download all " +"available invoices any time you need to here!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.web}``" +#: ../system/subscription.rst:None +msgid "Screenshot showing payment history of a hosted instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > VIP" +#: ../system/subscription.rst:229 +msgid "FAQ" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.vip}``" +#: ../system/subscription.rst:233 +msgid "I set up a trial account but am missing functions to test" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Phone" +#: ../system/subscription.rst:232 +msgid "" +"The trial instance is running within the professional package allowing up to " +"three agents." +msgstr "" + +#: ../system/subscription.rst:236 +msgid "Can I change package within the trial?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.phone}``" +#: ../system/subscription.rst:236 +msgid "No. As soon as the package is changed the subscription begins." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Note" +#: ../system/subscription.rst:241 +msgid "What happens to my trial instance after the trial period ended?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.note}``" +#: ../system/subscription.rst:239 +msgid "" +"Your instance will automatically be canceled for you. Please see *What " +"happens to my instance after it has been canceled?* for more." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Mobile" +#: ../system/subscription.rst:254 +msgid "What happens to my instance after it has been canceled?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.mobile}``" +#: ../system/subscription.rst:244 +msgid "That depends slightly on your instance state:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Login" +#: ../system/subscription.rst:250 +msgid "Trial instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.login}``" +#: ../system/subscription.rst:247 +msgid "" +"If you're still on trial, we will ice your instance and remind you once " +"again about your instance. We then will wait some days and remove your " +"instance from our system. This is the last time we will inform you by Email." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Lastname" +#: ../system/subscription.rst:254 +msgid "Paid instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.lastname}``" +#: ../system/subscription.rst:253 +msgid "" +"If you're a paying customer and canceled your subscription, the instance " +"removal will take place the day after your last subscription day." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Firstname" +#: ../system/subscription.rst:256 +msgid "Can removed instances be restored?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.firstname}``" +#: ../system/subscription.rst:257 +msgid "No. Once your instance has been removed, a restoration is not possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Fax" +#: ../system/system-report.rst:2 +msgid "System Report" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.fax}``" +#: ../system/system-report.rst:4 +msgid "" +"In this place you can't configure Zammad. Instead you can obtain a system " +"report about Zammad and its configuration." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Email" +#: ../system/system-report.rst:7 +msgid "" +"See the description in Zammad for an explanation. You can even find a " +"preview of the included data below the **Download** button." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.email}``" +#: ../system/system-report.rst:10 +msgid "" +"Zammad never sends this automatically to anyone. It is a manual process only " +"to provide better support based on your configuration." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Department" +#: ../system/translations.rst:2 +msgid "Translations" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.department}``" +#: ../system/translations.rst:4 +msgid "" +"Translations of Zammad are processed centrally in our `Weblate instance " +"`_. This allows non-developers to review " +"and update translation texts of the language they actually speak." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Avatar" +#: ../system/translations.rst:9 +msgid "" +"Your language is in an incomplete translation state or has typos? Please " +"consider helping us in sorting this out! All you need is either a GitHub " +"account or to register directly in our instance." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.avatar(60,60)}``" +#: ../system/translations.rst:13 +msgid "" +"Did you know? This is also where the documentation translations are handled. " +"🤓" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Address" +#: ../system/translations.rst:15 +msgid "" +"Have a look in our :docs:`contribution section ` in the system documentation to get started!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.address}``" +#: ../system/translations.rst:20 +msgid "Local Translations" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created at" +#: ../system/translations.rst:22 +msgid "" +"Apart from these system translations, there's still local translations you " +"can manage. This is relevant if you added custom objects that require " +"translations or even custom states and priorities." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_at}``" +#: ../system/translations.rst:None +msgid "Translation management screen within the admin menu" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "2019-10-07 16:25:00 UTC" +#: ../system/translations.rst:31 +msgid "Updating Translations" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Closing time" +#: ../system/translations.rst:33 +msgid "" +"Because of how Zammad ships translations, the only way to update the system " +"translations is to update your Zammad installation. The benefit of this is " +"that you no longer need internet access during a Zammad upgrade as the " +"package has everything it requires already." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.close_at}``" +#: ../system/translations.rst:39 +msgid "Translation of Custom Objects" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "2019-10-07 17:25:00 UTC" +#: ../system/translations.rst:41 +msgid "" +"No problem at all! You can customize any translation locally, even if it is " +"not initially provided by the system." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``3``, any number of articles existing in the ticket right now" +#: ../system/translations.rst:44 +msgid "" +"Translation is supported for a broad number of features, including but not " +"limited to custom:" msgstr "" -#: ../system/version.rst:2 -msgid "Version" -msgstr "Verze" - -#: ../system/version.rst:4 -msgid "Shows which version is currently being used on your Zammad-instance." +#: ../system/translations.rst:47 +msgid "Object Attributes" msgstr "" -#: ../manage/roles/admin-permissions.rst:53 -msgid "``admin.checklist``" +#: ../system/translations.rst:48 +msgid "Ticket Macros" msgstr "" -#: ../manage/roles/admin-permissions.rst:54 -msgid ":doc:`Manage > Checklist `" +#: ../system/translations.rst:49 +msgid "Ticket Overviews" msgstr "" -#: ../manage/roles/admin-permissions.rst:83 -msgid "``admin.channel_whatsapp``" +#: ../system/translations.rst:50 +msgid "Ticket Priorities" msgstr "" -#: ../manage/roles/admin-permissions.rst:84 -msgid ":doc:`Channels > Whatsapp `" +#: ../system/translations.rst:51 +msgid "Ticket States" msgstr "" -#: ../manage/roles/admin-permissions.rst:124 -msgid "``admin.public_links``" +#: ../system/translations.rst:54 +msgid "Customizing Translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:125 -msgid ":doc:`Manage > Public Links `" +#: ../system/translations.rst:56 +msgid "" +"Within the translation screen, simply click on the **New Translation** " +"button." msgstr "" -#: ../manage/roles/admin-permissions.rst:151 -msgid "``admin.system_report``" +#: ../system/translations.rst:None +msgid "New translation dialog" msgstr "" -#: ../manage/roles/admin-permissions.rst:152 -msgid ":doc:`System > System Report `" +#: ../system/translations.rst:62 +msgid "" +"In the dialog you can immediately enter the exact translation source (if you " +"know it) and your custom translation text for it and click **Submit**." msgstr "" -#: ../manage/roles/admin-permissions.rst:166 -msgid "``admin.ticket_auto_assignment``" +#: ../system/translations.rst:65 +msgid "" +"Alternatively, try to search for translation suggestions in the list below. " +"Selecting an item from the list will pre-fill the translation source for you " +"and then you can just enter your custom translation." msgstr "" -#: ../manage/roles/admin-permissions.rst:167 -msgid ":ref:`Settings > Ticket > Auto Assignment `" +#: ../system/translations.rst:69 +msgid "" +"The target language will always default to your current language selection. " +"If you need to translate for a different language, simply change the " +"selection before submitting." msgstr "" -#: ../manage/roles/admin-permissions.rst:169 -msgid "``admin.ticket_duplicate_detection``" +#: ../system/translations.rst:73 +msgid "" +"All your custom translations will show up in the overview table when added. " +"And they will even persist across Zammad updates!" msgstr "" -#: ../manage/roles/admin-permissions.rst:170 -msgid ":ref:`Settings > Ticket > Duplicate Detection `" +#: ../system/translations.rst:76 +msgid "" +"Make sure to reload your browser if a translated string is not displayed." msgstr "" -#: ../manage/roles/admin-permissions.rst:172 -msgid "``admin.ticket_priority``" +#: ../system/translations.rst:80 +msgid "Reverting to Original Translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:173 -msgid ":ref:`System > Objects >Ticket Priority `" +#: ../system/translations.rst:82 +msgid "" +"If you want to revert a custom translation to original text, simply use the " +"appropriate action within the row of the overview table." msgstr "" -#: ../manage/roles/admin-permissions.rst:175 -msgid "``admin.ticket_state``" +#: ../system/translations.rst:85 +msgid "" +"Depending on the type of the translation source, the action has a slightly " +"different name:" msgstr "" -#: ../manage/roles/admin-permissions.rst:176 -msgid ":ref:`System > Objects >Ticket State `" +#: ../system/translations.rst:88 +msgid "**Reset** for customized system translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:193 -msgid "``admin.webhook``" +#: ../system/translations.rst:89 +msgid "**Remove** for customized local translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:194 -msgid ":doc:`Manage > Webhook `" +#: ../system/translations.rst:91 +msgid "" +"In both cases, the action will remove the customized translation after a " +"confirmation." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:43 -msgid "``user_preferences.appearance``" +#: ../system/translations.rst:None +msgid "Screenshot showing the location of the Remove action" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:44 -msgid "Appearance configuration" +#: ../system/translations.rst:99 +msgid "Inline Translations" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:0 -msgid "Users can switch between dark, light and" +#: ../system/translations.rst:101 +msgid "" +"If you prefer a more hands-on approach, you can activate the inline or on-" +"screen translation feature by pressing ``ctrl`` + ``alt`` + ``t`` at any " +"time and on any screen." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:0 -msgid "automatic mode." +#: ../system/translations.rst:105 +msgid "" +"All customizable translation texts will be highlighted for you on the " +"screen. Just click into the highlighted area and update the text in place." msgstr "" -#: ../system/system-report.rst:2 -msgid "System Report" +#: ../system/translations.rst:None +msgid "Inline translation mode activated for the Overview screen" msgstr "" -#: ../system/system-report.rst:4 +#: ../system/translations.rst:112 msgid "" -"In this place you can't configure Zammad. Instead you can obtain a system " -"report about Zammad and its configuration." +"When finished editing, simply press ``ctrl`` + ``alt`` + ``t`` again to " +"deactivate." msgstr "" -#: ../system/system-report.rst:7 +#: ../system/translations.rst:117 msgid "" -"See the description in Zammad for an explanation. You can even find a " -"preview of the included data below the **Download** button." +"Even though it's available on any screen, the inline translation feature " +"requires admin permissions. It works only for the current language " +"selection. If you need to translate a different language, first change the " +"language in your :user-docs:`profile settings `." msgstr "" -#: ../system/system-report.rst:10 -msgid "" -"Zammad never sends this automatically to anyone. It is a manual process only " -"to provide better support based on your configuration." +#: ../system/version.rst:2 +msgid "Version" +msgstr "Verze" + +#: ../system/version.rst:4 +msgid "Shows which version is currently being used on your Zammad-instance." msgstr "" #, fuzzy diff --git a/locale/da/LC_MESSAGES/admin-docs.po b/locale/da/LC_MESSAGES/admin-docs.po index 6f692f5f..0de2c86e 100644 --- a/locale/da/LC_MESSAGES/admin-docs.po +++ b/locale/da/LC_MESSAGES/admin-docs.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Zammad\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-11-06 10:31+0100\n" +"POT-Creation-Date: 2024-11-12 16:31+0100\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -1040,12 +1040,12 @@ msgstr "" #: ../manage/roles/agent-permissions.rst:31 #: ../manage/roles/user-preferences-permissions.rst:37 #: ../manage/scheduler.rst:108 ../manage/webhook/add.rst:116 +#: ../misc/variables.rst:101 #: ../system/integrations/cti/includes/inbound-calls.include.rst:15 #: ../system/integrations/cti/includes/outbound-calls.include.rst:18 #: ../system/integrations/cti/includes/inbound-calls.include.rst:14 #: ../system/integrations/cti/includes/outbound-calls.include.rst:17 -#: ../system/objects.rst:162 ../system/objects.rst:244 -#: ../system/variables.rst:101 ../system/objects.rst:246 +#: ../system/objects.rst:162 ../system/objects.rst:246 msgid "Note" msgstr "" @@ -2257,7 +2257,7 @@ msgstr "" #: ../channels/email/signatures.rst:22 msgid "" "To individualize the signatures, it is possible to automatically load " -"specific information into a signature via :doc:`/system/variables`. All " +"specific information into a signature via :doc:`/misc/variables`. All " "information stored on the ticket, assigned customers or agents can be " "inserted. This makes it possible to design the signature individually. To " "load a list of available variables, enter two colons (``::``) into the " @@ -2550,7 +2550,7 @@ msgstr "" #: ../channels/form.rst:19 ../manage/groups/settings.rst:14 #: ../manage/scheduler.rst:39 ../manage/slas/how-do-they-work.rst:26 #: ../manage/templates.rst:33 ../system/objects.rst:130 -#: ../system/objects.rst:232 ../system/objects.rst:234 +#: ../system/objects.rst:234 msgid "Name" msgstr "" @@ -2579,7 +2579,7 @@ msgstr "" #: ../manage/macros/how-do-they-work.rst:0 ../manage/overviews.rst:0 #: ../manage/scheduler.rst:111 ../manage/templates.rst:43 #: ../manage/webhook/add.rst:123 ../system/objects.rst:169 -#: ../system/objects.rst:246 ../system/objects.rst:248 +#: ../system/objects.rst:248 msgid "Active" msgstr "" @@ -2921,10 +2921,9 @@ msgid "Default value" msgstr "" #: ../channels/form.rst:219 ../manage/public-links.rst:47 -#: ../misc/object-conditions/basics.rst:64 +#: ../misc/object-conditions/basics.rst:64 ../misc/variables.rst:100 #: ../system/core-workflows/condition-operators.rst:21 -#: ../system/objects/permissions.rst:39 ../system/subscription/billing.rst:53 -#: ../system/variables.rst:100 +#: ../system/objects/permissions.rst:39 ../system/subscription.rst:208 msgid "Description" msgstr "" @@ -5908,7 +5907,7 @@ msgstr "" msgid "System" msgstr "" -#: ../index.rst:87 ../index.rst:88 +#: ../index.rst:87 msgid "Misc" msgstr "" @@ -7142,7 +7141,7 @@ msgstr "" #: ../manage/macros/how-do-they-work.rst:28 msgid "" "Unlike triggers, the scheduler, and text modules, macro actions do **not** " -"support the use of :doc:`/system/variables`." +"support the use of :doc:`/misc/variables`." msgstr "" #: ../manage/macros/how-do-they-work.rst:32 @@ -8370,165 +8369,149 @@ msgid "Accessing chat for agents: ``chat.agent``" msgstr "" #: ../manage/roles/admin-permissions.rst:53 +msgid "``admin.checklist``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:54 +msgid ":doc:`Manage > Checklist `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:56 msgid "``admin.channel_email``" msgstr "" -#: ../manage/roles/admin-permissions.rst:54 #: ../manage/roles/admin-permissions.rst:57 msgid ":doc:`Channels > Email `" msgstr "" -#: ../manage/roles/admin-permissions.rst:56 #: ../manage/roles/admin-permissions.rst:59 msgid "``admin.channel_facebook``" msgstr "" -#: ../manage/roles/admin-permissions.rst:57 #: ../manage/roles/admin-permissions.rst:60 msgid ":doc:`Channels > Facebook `" msgstr "" -#: ../manage/roles/admin-permissions.rst:58 #: ../manage/roles/admin-permissions.rst:61 msgid "" "Accessing Facebook tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:59 #: ../manage/roles/admin-permissions.rst:62 msgid "``admin.channel_formular``" msgstr "" -#: ../manage/roles/admin-permissions.rst:60 #: ../manage/roles/admin-permissions.rst:63 msgid ":doc:`Channels > Form `" msgstr "" -#: ../manage/roles/admin-permissions.rst:62 #: ../manage/roles/admin-permissions.rst:65 msgid "``admin.channel_google``" msgstr "" -#: ../manage/roles/admin-permissions.rst:63 #: ../manage/roles/admin-permissions.rst:66 msgid ":doc:`Channels > Google `" msgstr "" -#: ../manage/roles/admin-permissions.rst:65 #: ../manage/roles/admin-permissions.rst:68 msgid "``admin.channel_microsoft365``" msgstr "" -#: ../manage/roles/admin-permissions.rst:66 #: ../manage/roles/admin-permissions.rst:69 msgid ":doc:`Channels > Microsoft 365 `" msgstr "" -#: ../manage/roles/admin-permissions.rst:68 #: ../manage/roles/admin-permissions.rst:71 msgid "``admin.channel_sms``" msgstr "" -#: ../manage/roles/admin-permissions.rst:69 #: ../manage/roles/admin-permissions.rst:72 msgid ":doc:`Channels > SMS `" msgstr "" -#: ../manage/roles/admin-permissions.rst:71 #: ../manage/roles/admin-permissions.rst:74 msgid "``admin.channel_telegram``" msgstr "" -#: ../manage/roles/admin-permissions.rst:72 #: ../manage/roles/admin-permissions.rst:75 msgid ":doc:`Channels > Telegram `" msgstr "" -#: ../manage/roles/admin-permissions.rst:73 #: ../manage/roles/admin-permissions.rst:76 msgid "" "Accessing Telegram tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:74 #: ../manage/roles/admin-permissions.rst:77 msgid "``admin.channel_twitter``" msgstr "" -#: ../manage/roles/admin-permissions.rst:75 #: ../manage/roles/admin-permissions.rst:78 msgid ":doc:`Channels > Twitter `" msgstr "" -#: ../manage/roles/admin-permissions.rst:76 #: ../manage/roles/admin-permissions.rst:79 msgid "" "Accessing Twitter/X tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:77 #: ../manage/roles/admin-permissions.rst:80 msgid "``admin.channel_web``" msgstr "" -#: ../manage/roles/admin-permissions.rst:78 #: ../manage/roles/admin-permissions.rst:81 msgid ":doc:`Channels > Web `" msgstr "" -#: ../manage/roles/admin-permissions.rst:80 +#: ../manage/roles/admin-permissions.rst:83 +msgid "``admin.channel_whatsapp``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:84 +msgid ":doc:`Channels > Whatsapp `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:86 msgid "``admin.core_workflows``" msgstr "" -#: ../manage/roles/admin-permissions.rst:81 #: ../manage/roles/admin-permissions.rst:87 msgid ":doc:`System > Core Workflows `" msgstr "" -#: ../manage/roles/admin-permissions.rst:83 #: ../manage/roles/admin-permissions.rst:89 msgid "``admin.data_privacy``" msgstr "" -#: ../manage/roles/admin-permissions.rst:84 #: ../manage/roles/admin-permissions.rst:90 msgid ":doc:`System > Data Privacy `" msgstr "" -#: ../manage/roles/admin-permissions.rst:85 #: ../manage/roles/admin-permissions.rst:91 msgid "" "🔥 Be careful, it allows users to permanently delete data on the system." msgstr "" -#: ../manage/roles/admin-permissions.rst:86 #: ../manage/roles/admin-permissions.rst:92 msgid "``admin.group``" msgstr "" -#: ../manage/roles/admin-permissions.rst:87 #: ../manage/roles/admin-permissions.rst:93 msgid ":doc:`Manage > Groups `" msgstr "" -#: ../manage/roles/admin-permissions.rst:89 #: ../manage/roles/admin-permissions.rst:95 msgid "``admin.integration``" msgstr "" -#: ../manage/roles/admin-permissions.rst:90 #: ../manage/roles/admin-permissions.rst:96 msgid ":doc:`System > Integrations `" msgstr "" -#: ../manage/roles/admin-permissions.rst:92 #: ../manage/roles/admin-permissions.rst:98 msgid "``admin.knowledge_base``" msgstr "" -#: ../manage/roles/admin-permissions.rst:93 #: ../manage/roles/admin-permissions.rst:99 msgid ":doc:`Manage > Knowledge Base `" msgstr "" @@ -8548,57 +8531,46 @@ msgid "" "knowledge-base.html#editing-answers>`." msgstr "" -#: ../manage/roles/admin-permissions.rst:98 #: ../manage/roles/admin-permissions.rst:104 msgid "``admin.macro``" msgstr "" -#: ../manage/roles/admin-permissions.rst:99 #: ../manage/roles/admin-permissions.rst:105 msgid ":doc:`Manage > Macros `" msgstr "" -#: ../manage/roles/admin-permissions.rst:100 #: ../manage/roles/admin-permissions.rst:106 msgid "In some cases, macros may also require ``admin.tag``" msgstr "" -#: ../manage/roles/admin-permissions.rst:101 #: ../manage/roles/admin-permissions.rst:107 msgid "``admin.maintenance``" msgstr "" -#: ../manage/roles/admin-permissions.rst:102 #: ../manage/roles/admin-permissions.rst:108 msgid ":doc:`System > Maintenance `" msgstr "" -#: ../manage/roles/admin-permissions.rst:104 #: ../manage/roles/admin-permissions.rst:110 msgid "``admin.monitoring``" msgstr "" -#: ../manage/roles/admin-permissions.rst:105 #: ../manage/roles/admin-permissions.rst:111 msgid ":doc:`System > Monitoring `" msgstr "" -#: ../manage/roles/admin-permissions.rst:107 #: ../manage/roles/admin-permissions.rst:113 msgid "``admin.object``" msgstr "" -#: ../manage/roles/admin-permissions.rst:108 #: ../manage/roles/admin-permissions.rst:114 msgid ":doc:`System > Objects `" msgstr "" -#: ../manage/roles/admin-permissions.rst:110 #: ../manage/roles/admin-permissions.rst:116 msgid "``admin.organization``" msgstr "" -#: ../manage/roles/admin-permissions.rst:111 #: ../manage/roles/admin-permissions.rst:117 msgid ":doc:`Manage > Organizations `" msgstr "" @@ -8615,202 +8587,210 @@ msgstr "" msgid "They can even edit an organization's name, domain, and notes!" msgstr "" -#: ../manage/roles/admin-permissions.rst:115 #: ../manage/roles/admin-permissions.rst:121 msgid "``admin.overview``" msgstr "" -#: ../manage/roles/admin-permissions.rst:116 #: ../manage/roles/admin-permissions.rst:122 msgid ":doc:`Manage > Overviews`" msgstr "" -#: ../manage/roles/admin-permissions.rst:118 +#: ../manage/roles/admin-permissions.rst:124 +msgid "``admin.public_links``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:125 +msgid ":doc:`Manage > Public Links `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:127 msgid "``admin.package``" msgstr "" -#: ../manage/roles/admin-permissions.rst:119 #: ../manage/roles/admin-permissions.rst:128 msgid ":doc:`System > Packages `" msgstr "" -#: ../manage/roles/admin-permissions.rst:121 #: ../manage/roles/admin-permissions.rst:130 msgid "``admin.report_profile``" msgstr "" -#: ../manage/roles/admin-permissions.rst:122 #: ../manage/roles/admin-permissions.rst:131 msgid ":doc:`Manage > Report Profiles `" msgstr "" -#: ../manage/roles/admin-permissions.rst:123 #: ../manage/roles/admin-permissions.rst:132 msgid "Access to view reports: ``report``" msgstr "" -#: ../manage/roles/admin-permissions.rst:124 #: ../manage/roles/admin-permissions.rst:133 msgid "``admin.role``" msgstr "" -#: ../manage/roles/admin-permissions.rst:125 #: ../manage/roles/admin-permissions.rst:134 msgid ":doc:`Manage > Roles `" msgstr "" -#: ../manage/roles/admin-permissions.rst:127 #: ../manage/roles/admin-permissions.rst:136 msgid "``admin.scheduler``" msgstr "" -#: ../manage/roles/admin-permissions.rst:128 #: ../manage/roles/admin-permissions.rst:137 msgid ":doc:`Manage > Scheduler `" msgstr "" -#: ../manage/roles/admin-permissions.rst:129 #: ../manage/roles/admin-permissions.rst:138 msgid "For automation on tickets" msgstr "" -#: ../manage/roles/admin-permissions.rst:130 #: ../manage/roles/admin-permissions.rst:139 msgid "``admin.security``" msgstr "" -#: ../manage/roles/admin-permissions.rst:131 #: ../manage/roles/admin-permissions.rst:140 msgid ":doc:`Settings > Security `" msgstr "" -#: ../manage/roles/admin-permissions.rst:132 #: ../manage/roles/admin-permissions.rst:141 msgid "Settings of Zammad. This also covers third party authentications." msgstr "" -#: ../manage/roles/admin-permissions.rst:133 #: ../manage/roles/admin-permissions.rst:142 msgid "``admin.session``" msgstr "" -#: ../manage/roles/admin-permissions.rst:134 #: ../manage/roles/admin-permissions.rst:143 msgid ":doc:`System > Sessions `" msgstr "" -#: ../manage/roles/admin-permissions.rst:136 #: ../manage/roles/admin-permissions.rst:145 msgid "``admin.setting_system``" msgstr "" -#: ../manage/roles/admin-permissions.rst:137 #: ../manage/roles/admin-permissions.rst:146 msgid ":doc:`Settings > System `" msgstr "" -#: ../manage/roles/admin-permissions.rst:139 #: ../manage/roles/admin-permissions.rst:148 msgid "``admin.sla``" msgstr "" -#: ../manage/roles/admin-permissions.rst:140 #: ../manage/roles/admin-permissions.rst:149 msgid ":doc:`Manage > SLAs `" msgstr "" -#: ../manage/roles/admin-permissions.rst:142 +#: ../manage/roles/admin-permissions.rst:151 +msgid "``admin.system_report``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:152 +msgid ":doc:`System > System Report `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:154 msgid "``admin.tag``" msgstr "" -#: ../manage/roles/admin-permissions.rst:143 #: ../manage/roles/admin-permissions.rst:155 msgid ":doc:`Manage > Tags `" msgstr "" -#: ../manage/roles/admin-permissions.rst:145 #: ../manage/roles/admin-permissions.rst:157 msgid "``admin.template``" msgstr "" -#: ../manage/roles/admin-permissions.rst:146 #: ../manage/roles/admin-permissions.rst:158 msgid ":doc:`Manage > Templates `" msgstr "" -#: ../manage/roles/admin-permissions.rst:148 #: ../manage/roles/admin-permissions.rst:160 msgid "``admin.text_module``" msgstr "" -#: ../manage/roles/admin-permissions.rst:149 #: ../manage/roles/admin-permissions.rst:161 msgid ":doc:`Manage > Text Modules `" msgstr "" -#: ../manage/roles/admin-permissions.rst:151 #: ../manage/roles/admin-permissions.rst:163 msgid "``admin.ticket``" msgstr "" -#: ../manage/roles/admin-permissions.rst:152 #: ../manage/roles/admin-permissions.rst:164 msgid ":doc:`Settings > Tickets `" msgstr "" -#: ../manage/roles/admin-permissions.rst:153 #: ../manage/roles/admin-permissions.rst:165 msgid "Does not grant access to :doc:`/misc/composer`" msgstr "" -#: ../manage/roles/admin-permissions.rst:154 +#: ../manage/roles/admin-permissions.rst:166 +msgid "``admin.ticket_auto_assignment``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:167 +msgid ":ref:`Settings > Ticket > Auto Assignment `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:169 +msgid "``admin.ticket_duplicate_detection``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:170 +msgid ":ref:`Settings > Ticket > Duplicate Detection `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:172 +msgid "``admin.ticket_priority``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:173 +msgid ":ref:`System > Objects >Ticket Priority `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:175 +msgid "``admin.ticket_state``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:176 +msgid ":ref:`System > Objects >Ticket State `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:178 msgid "``admin.time_accounting``" msgstr "" -#: ../manage/roles/admin-permissions.rst:155 #: ../manage/roles/admin-permissions.rst:179 msgid ":doc:`Manage > Time Accounting `" msgstr "" -#: ../manage/roles/admin-permissions.rst:156 #: ../manage/roles/admin-permissions.rst:180 msgid "Also allows the export of timekeeping records." msgstr "" -#: ../manage/roles/admin-permissions.rst:157 #: ../manage/roles/admin-permissions.rst:181 msgid "``admin.translation``" msgstr "" -#: ../manage/roles/admin-permissions.rst:158 #: ../manage/roles/admin-permissions.rst:182 msgid ":doc:`System > Translations `" msgstr "" -#: ../manage/roles/admin-permissions.rst:159 #: ../manage/roles/admin-permissions.rst:183 msgid "Also enables inline translation" msgstr "" -#: ../manage/roles/admin-permissions.rst:160 #: ../manage/roles/admin-permissions.rst:184 msgid "``admin.trigger``" msgstr "" -#: ../manage/roles/admin-permissions.rst:161 #: ../manage/roles/admin-permissions.rst:185 msgid ":doc:`Manage > Triggers `" msgstr "" -#: ../manage/roles/admin-permissions.rst:163 #: ../manage/roles/admin-permissions.rst:187 msgid "``admin.user``" msgstr "" -#: ../manage/roles/admin-permissions.rst:164 #: ../manage/roles/admin-permissions.rst:188 msgid ":doc:`Manage > Users `" msgstr "" @@ -8829,6 +8809,14 @@ msgid "" "from-users-perspective>` ." msgstr "" +#: ../manage/roles/admin-permissions.rst:193 +msgid "``admin.webhook``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:194 +msgid ":doc:`Manage > Webhook `" +msgstr "" + #: ../manage/roles/agent-permissions.rst:2 msgid "Agent Permissions" msgstr "" @@ -9247,36 +9235,45 @@ msgid "than the user that generated them." msgstr "" #: ../manage/roles/user-preferences-permissions.rst:43 +msgid "``user_preferences.appearance``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:44 +msgid "Appearance configuration" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "Users can switch between dark, light and" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "automatic mode." +msgstr "" + #: ../manage/roles/user-preferences-permissions.rst:47 msgid "``user_preferences.avatar``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:44 #: ../manage/roles/user-preferences-permissions.rst:48 msgid "Avatar settings" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:45 #: ../manage/roles/user-preferences-permissions.rst:49 msgid "Override the default Gravatar with a custom avatar" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:46 #: ../manage/roles/user-preferences-permissions.rst:50 msgid "``user_preferences.calendar``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:47 #: ../manage/roles/user-preferences-permissions.rst:51 msgid "Configure the calendar feed" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:49 #: ../manage/roles/user-preferences-permissions.rst:53 msgid "``user_preferences.device``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:50 #: ../manage/roles/user-preferences-permissions.rst:54 msgid "Manage device login sessions" msgstr "" @@ -9293,22 +9290,18 @@ msgstr "" msgid "To learn more, see :doc:`/manage/trigger/system-notifications`." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:54 #: ../manage/roles/user-preferences-permissions.rst:58 msgid "``user_preferences.language``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:55 #: ../manage/roles/user-preferences-permissions.rst:59 msgid "Configure the UI locale/language" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:57 #: ../manage/roles/user-preferences-permissions.rst:61 msgid "``user_preferences.linked_accounts``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:58 #: ../manage/roles/user-preferences-permissions.rst:62 msgid "Account linking" msgstr "" @@ -9332,7 +9325,6 @@ msgstr "" msgid "is the only way users can utilize third-party logins." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:63 #: ../manage/roles/user-preferences-permissions.rst:67 msgid "``user_preferences.notifications``" msgstr "" @@ -9359,7 +9351,6 @@ msgstr "" msgid "Customers can't receive ticket notifications at all." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:69 #: ../manage/roles/user-preferences-permissions.rst:73 msgid "``user_preferences.out_of_office``" msgstr "" @@ -9384,7 +9375,6 @@ msgstr "" msgid "they're replacing." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:75 #: ../manage/roles/user-preferences-permissions.rst:79 msgid "``user_preferences.overview_sorting``" msgstr "" @@ -9413,12 +9403,10 @@ msgstr "" msgid "overviews has no effect on custom orders." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:82 #: ../manage/roles/user-preferences-permissions.rst:86 msgid "``user_preferences.password``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:83 #: ../manage/roles/user-preferences-permissions.rst:87 msgid "Change account password" msgstr "" @@ -9435,7 +9423,6 @@ msgstr "" msgid "your only allowed authentication method." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:87 #: ../manage/roles/user-preferences-permissions.rst:91 msgid "``user_preferences.two_factor_authentication``" msgstr "" @@ -9472,7 +9459,7 @@ msgstr "" #: ../manage/scheduler.rst:19 msgid "" -"Schedulers can be used to send periodic reminder emails. Use :doc:`/system/" +"Schedulers can be used to send periodic reminder emails. Use :doc:`/misc/" "variables` to build highly-customized email templates." msgstr "" @@ -10468,7 +10455,7 @@ msgstr "" #: ../manage/text-modules.rst:57 msgid "" -"The example text modules below use :doc:`/system/variables` to dynamically " +"The example text modules below use :doc:`/misc/variables` to dynamically " "insert information like the customer's or agent's names." msgstr "" @@ -10808,8 +10795,8 @@ msgstr "" #: ../misc/object-conditions/basics.rst:144 #: ../misc/object-conditions/basics.rst:160 #: ../misc/object-conditions/basics.rst:168 -#: ../misc/object-conditions/basics.rst:178 ../settings/ticket.rst:2 -#: ../system/variables/ticket.rst:2 +#: ../misc/object-conditions/basics.rst:178 ../misc/variables/ticket.rst:2 +#: ../settings/ticket.rst:2 msgid "Ticket" msgstr "" @@ -11043,7 +11030,7 @@ msgstr "" #: ../manage/trigger/how-do-they-work.rst:79 msgid "" -"Certain actions (such as *email*, *SMS* and *notes*) support :doc:`/system/" +"Certain actions (such as *email*, *SMS* and *notes*) support :doc:`/misc/" "variables`, which can be used to build highly-customized message templates." msgstr "" @@ -11072,7 +11059,7 @@ msgstr "" msgid "" "You can also combine static text with placeholders for text fields. Remember " "that the placeholders' values have to be known during trigger runtime. Learn " -"more about :doc:`/system/variables`." +"more about :doc:`/misc/variables`." msgstr "" #: ../manage/trigger/how-do-they-work.rst:105 @@ -12037,7 +12024,7 @@ msgstr "" msgid "" "When switched on, a code editor will be shown below, where you can configure " "custom payload for your webhook in JSON format. To insert supported :doc:`/" -"system/variables` use ``::`` or ``#{`` shortcuts for autocomplete." +"misc/variables` use ``::`` or ``#{`` shortcuts for autocomplete." msgstr "" #: ../manage/webhook/add.rst:103 @@ -14614,11942 +14601,11833 @@ msgid "" "powerful conditions with AND/OR relations." msgstr "" -#: ../settings/branding.rst:10 -msgid "Product Name" +#: ../misc/variables.rst:2 +msgid "Variables" msgstr "" -#: ../settings/branding.rst:7 +#: ../misc/variables.rst:4 msgid "" -"Defines the name of the application, shown in the web interface, tabs and " -"title bar of the web browser." +"Please note that this is just an overview of available variables. It might " +"be incomplete or variables might not be available within some functions. If " +"you're missing variables or are not sure if something is not working as " +"expected, feel free to ask over at the `Community `_." msgstr "" -#: ../settings/branding.rst:10 -msgid "Default value: ``Zammad Helpdesk``" +#: ../misc/variables.rst:10 +msgid "" +"Variables can be called by typing ``::`` (just like text modules in the " +"frontend), as long as you're in a supported text field within the backend. " +"Zammad will display all variables being available within this context and " +"replace it to the variable as soon as you selected an entry." msgstr "" -#: ../settings/branding.rst:13 -msgid "Will be shown in the app and is included in email footers." +#: ../misc/variables.rst:15 +msgid "" +"You have an empty field which you referenced and it appears as ``-``? That's " +"currently working as designed - you might want to ensure that these fields " +"always have a value." msgstr "" -#: ../settings/branding.rst:19 -msgid "Logo" +#: ../misc/variables.rst:20 +msgid "Variable Categories" msgstr "" -#: ../settings/branding.rst:16 -msgid "Defines the logo of the application, shown in the login page of Zammad." +#: ../misc/variables.rst:31 +msgid "Wait, What About Custom Objects?" msgstr "" -#: ../settings/branding.rst:18 +#: ../misc/variables.rst:33 msgid "" -"Ensure to hit the \"Submit\" button after uploading the logo. Otherwise your " -"change will not be saved." +"Good point! Of course, we can't predict what objects you might create, but " +"we can give you a hint on how to put the puzzle together to get your custom " +"values." msgstr "" -#: ../settings/branding.rst:22 +#: ../misc/variables.rst:36 msgid "" -"Allows to set the default language of the Zammad instance. The here defined " -"locale mostly acts as a fallback for:" -msgstr "" - -#: ../settings/branding.rst:25 -msgid "user preferences (if Zammad can't detect the users locale)" +"For this, we'll talk about the inner part of the variable (so everything " +"within ``#{}``), please put the outer part around to have a valid variable. " +"The first part of the variable name consist of the object type. Currently " +"these are:" msgstr "" -#: ../settings/branding.rst:26 -msgid "CSV output (reporting, time accounting)" +#: ../misc/variables.rst:41 +msgid "Ticket (``ticket``)" msgstr "" -#: ../settings/branding.rst:30 -msgid "Define the timezone of your Zammad installation." +#: ../misc/variables.rst:42 +msgid "User (``user``)" msgstr "" -#: ../settings/branding.rst:32 -msgid "" -"This does not have any effect on timings for your agents or how Zammad " -"stores date and time values." +#: ../misc/variables.rst:43 +msgid "Organization (``organization``)" msgstr "" -#: ../settings/branding.rst:35 -msgid "Changing this value has direct consequences on the following areas:" +#: ../misc/variables.rst:44 +msgid "Group (``group``)" msgstr "" -#: ../settings/branding.rst:37 -msgid ":doc:`/manage/scheduler` tasks" +#: ../misc/variables.rst:46 +msgid "" +"The second part is the name of the attribute. This is the name you define " +"during object creation and can be found within the object attribute menu at " +"any time. The first and second part of a variable is divided by a point, e." +"g.: ``ticket.number`` which will in total be ``#{ticket.number}``." msgstr "" -#: ../settings/branding.rst:38 -msgid "search indexing (and thus reporting)" +#: ../misc/variables.rst:51 +msgid "" +"Now, in some situations it's possible that you'll need to use a third part. " +"The best example for such a situation would be a ``select`` or ``tree-" +"select`` field which will by default return the key value, not it's display " +"name. For this, just extend your variable with ``.value``. This will result " +"in ``#{ticket.select.value}``." msgstr "" -#: ../settings/branding.rst:40 -msgid "calendar subscriptions" +#: ../misc/variables.rst:60 +msgid "Using Translated Variables" msgstr "" -#: ../settings/branding.rst:41 -msgid "browser printing" +#: ../misc/variables.rst:62 +msgid "" +"If you want to use a translated variable in triggers or schedulers, you can " +"extend the placeholder like this: ``#{t(ticket.state.name)}``. The ``t`` " +"tells Zammad to search for fitting translated strings. The used output " +"language is based on the system language of Zammad which you can set in the " +"admin panel under :doc:`/settings/branding` or based on the selected locale " +"in the trigger/scheduler edit dialog." msgstr "" -#: ../settings/branding.rst:43 +#: ../misc/variables.rst:69 msgid "" -"Please note that some of above are fallbacks in case Zammad could not detect " -"the agents timezone correctly." +"A possible use-case: you want to send your customers updates on tickets via " +"trigger or scheduler which should include the state of the ticket. Using the " +"default ``#{ticket.state.name}`` (without the translation flag ``t()``) " +"would lead to the output of the original (english) name of the state." msgstr "" -#: ../settings/branding.rst:77 -msgid "Pretty Date" +#: ../misc/variables.rst:75 +msgid "Date and Time Formatting" msgstr "" -#: ../settings/branding.rst:47 +#: ../misc/variables.rst:77 msgid "" -"This setting allows you to define how Zammad should display time stamps " -"within the interface to all users." +"The system (trigger/scheduler selected) locale and timezone predefines a " +"default format of date and timestamp. This format is customizable by using " +"the ``dt()`` method." msgstr "" -#: ../settings/branding.rst:50 -msgid "" -"This does not have any effect on how Zammad returns e.g. time values via " -"variables." +#: ../misc/variables.rst:79 +msgid "The method arguments are as follows:" msgstr "" -#: ../settings/branding.rst:77 -msgid "Choose in between the following options:" +#: ../misc/variables.rst:81 +msgid "The date or timestamp variable you want to format." msgstr "" -#: ../settings/branding.rst:64 -msgid "relative" +#: ../misc/variables.rst:82 +msgid "The output format string." msgstr "" -#: ../settings/branding.rst:55 +#: ../misc/variables.rst:83 +msgid "The timezone to apply (optional)." +msgstr "" + +#: ../misc/variables.rst:85 +#: ../system/objects/external-data-source-example.rst:23 +msgid "**Example:**" +msgstr "" + +#: ../misc/variables.rst:86 msgid "" -"This timestamp shows a relative time span until it switches to a date. Over " -"time, it will change as follows:" +"``#{dt(ticket.updated_at, \"%A %Y-%m-%d %H:%M in the office\", \"Europe/" +"Berlin\")}``" msgstr "" -#: ../settings/branding.rst:58 -msgid "just now" +#: ../misc/variables.rst:87 +msgid "Monday, 2024-03-18 15:31 in the office" msgstr "" -#: ../settings/branding.rst:59 -msgid "5 minutes ago" +#: ../misc/variables.rst:89 +msgid "" +"If you want to use our example, make sure to paste the string above without " +"formatting (``CTRL+Shift+v``), otherwise it won't work." msgstr "" -#: ../settings/branding.rst:60 -msgid "3 days 1 hour ago" +#: ../misc/variables.rst:93 +msgid "The following table lists available format directives:" msgstr "" -#: ../settings/branding.rst:61 -msgid "``03/04/2022``" +#: ../misc/variables.rst:99 +msgid "Parameter" msgstr "" -#: ../settings/branding.rst:63 -msgid "Hovering the timestamp helps, you'll always get a clean timestamp then." +#: ../misc/variables.rst:102 +msgid "``%Y``" msgstr "" -#: ../settings/branding.rst:71 -msgid "absolute" +#: ../misc/variables.rst:103 +msgid "Year with 4 digits" msgstr "" -#: ../settings/branding.rst:67 -msgid "" -"This timestamp always includes the week day. For one week after creation, " -"the timestamp will not contain the date itself: Thursday 18:35." +#: ../misc/variables.rst:104 +msgid "Use ``%y`` for year with 2 digits" msgstr "" -#: ../settings/branding.rst:71 -msgid "After a week it will switch to: ``Friday 4. Mar 16:00``." +#: ../misc/variables.rst:105 +msgid "``%m``" msgstr "" -#: ../settings/branding.rst:76 -msgid "timestamp" +#: ../misc/variables.rst:106 +msgid "Month of year (as number with zero-padding)" msgstr "" -#: ../settings/branding.rst:74 -msgid "" -"This will cause Zammad to show a complete timestamp according to your locale " -"defaults. For English this could be e.g. ``2022/12/03 2:40 pm`` or for " -"German e.g. ``12.03.2022 14:40``." +#: ../misc/variables.rst:107 +msgid "Use ``%-m`` for month without zero-padding" msgstr "" -#: ../settings/branding.rst:78 -msgid "Default setting: ``relative``." +#: ../misc/variables.rst:108 +msgid "``%d``" msgstr "" -#: ../settings/security.rst:2 -msgid "Security" +#: ../misc/variables.rst:109 +msgid "Day of month (as number with zero-padding)" msgstr "" -#: ../settings/security.rst:4 -msgid "" -"For your overview we split each tab within security settings into its own " -"page:" +#: ../misc/variables.rst:110 +msgid "Use ``%e`` for day without zero-padding" msgstr "" -#: ../settings/security/base.rst:2 ../settings/system/base.rst:2 -#: ../settings/ticket.rst:8 -msgid "Base" +#: ../misc/variables.rst:111 +msgid "``%H``" msgstr "" -#: ../settings/security/base.rst:5 -msgid "New User Accounts" +#: ../misc/variables.rst:112 +msgid "Hour of day in 24h notation with zero-padding" msgstr "" -#: ../settings/security/base.rst:9 -msgid "" -"Activates the `register as a new customer` function on the login page. If " -"set to ``no`` only administrators or agents can create new accounts manually." +#: ../misc/variables.rst:113 +msgid "Use ``%k`` for hour without zero-padding" msgstr "" -#: ../settings/security/base.rst:13 ../settings/security/base.rst:38 -#: ../settings/security/base.rst:66 -msgid "Default setting: ``yes``" +#: ../misc/variables.rst:114 +msgid "``%I``" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing activated \"New User Accounts\" setting" +#: ../misc/variables.rst:115 +msgid "Hour of day in 12h notation with zero-padding" msgstr "" -#: ../settings/security/base.rst:22 +#: ../misc/variables.rst:116 msgid "" -"Deactivation of above function **does not** deactivate automatic account " -"creation! This means: If a user writes e.g. an email to Zammad and has no " -"account yet, Zammad will automatically create the account. User accounts are " -"a direct dependency of tickets and thus technically mandatory." +"Use ``%l`` for hour without zero-padding and ``%p`` / ``%P`` for meridian " +"indicator" msgstr "" -#: ../settings/security/base.rst:29 -msgid "Lost Password" +#: ../misc/variables.rst:117 +msgid "``%M``" msgstr "" -#: ../settings/security/base.rst:33 -msgid "" -"Activates the `lost password` function on the login page. If set to ``no`` " -"only administrators may change the user's password - users may update their " -"own password if they're still logged in and they have the required :doc:" -"`permission `." +#: ../misc/variables.rst:118 +msgid "Minute of hour" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing activated \"Lost Password\" setting" +#: ../misc/variables.rst:120 +msgid "``%S``" msgstr "" -#: ../settings/security/base.rst:49 -msgid "" -"With third party authentications - but especially LDAP - you may want to " -"disable this function. Zammad **will not** change third party login " -"passwords and instead set or change the local password!" +#: ../misc/variables.rst:121 +msgid "Second of Minute" msgstr "" -#: ../settings/security/base.rst:56 -msgid "Password Login" +#: ../misc/variables.rst:123 +msgid "``%A``" msgstr "" -#: ../settings/security/base.rst:60 -msgid "" -"Activates the username & password login by default and if no third-party " -"login is activated. Disabling password login on the Zammad login page only " -"takes effect if you enable any :doc:`third-party`." +#: ../misc/variables.rst:124 +msgid "Weekday name" msgstr "" -#: ../settings/security/base.rst:64 -msgid "See :doc:`third-party` for supported third-party logins." +#: ../misc/variables.rst:125 +msgid "Use ``%a`` for abbreviated name or ``%^A`` for uppercase name" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing de-activated \"Password Login\" setting" +#: ../misc/variables.rst:126 +msgid "``%B``" msgstr "" -#: ../settings/security/base.rst:77 -msgid "" -"To help administrators to overcome \"login issues\", Zammad automatically " -"offers a password request for administrator users. This allows you to adjust " -"Third-Party applications even if the login does no longer work!" +#: ../misc/variables.rst:127 +msgid "Month name" msgstr "" -#: ../settings/security/base.rst:84 -msgid "Session Timeout" +#: ../misc/variables.rst:128 +msgid "Use ``%b`` for abbreviated name" msgstr "" -#: ../settings/security/base.rst:86 -msgid "" -"All settings below by default are set to ``4 weeks``. Session Timeout " -"defines the life time of a users session. As soon as it's reached, Zammad " -"will automatically log off the session in question." +#: ../misc/variables.rst:129 +msgid "``%U``" msgstr "" -#: ../settings/security/base.rst:91 -msgid "" -"Zammad takes the highest value set assigned for the user based on the " -"permissions." +#: ../misc/variables.rst:130 +msgid "Week number of current year" msgstr "" -#: ../settings/security/base.rst:94 -msgid "``admin``" +#: ../misc/variables.rst:131 +msgid "Use ``%W`` for a different calculation method" msgstr "" -#: ../settings/security/base.rst:96 -msgid "``ticket.customer``" +#: ../misc/variables.rst:134 +msgid "" +"We support the known format directives for the Ruby built-in method " +"``strftime`` of the ``DateTime`` class. For more information, see `here " +"`_." msgstr "" -#: ../settings/security/base.rst:97 -msgid "``default`` (fallback if user doesn't have above permissions set)" +#: ../misc/variables/article.rst:2 +msgid "Articles" msgstr "" -#: ../settings/security/base.rst:99 +#: ../misc/variables/article.rst:4 ../misc/variables/config.rst:4 +#: ../misc/variables/current-user.rst:4 ../misc/variables/ticket.rst:4 msgid "" -"All settings act independently from each other allowing you to disable the " -"timeouts for e.g. admins, but not agents." +"If you're missing variables or are not sure if something is not working as " +"expected, feel free to ask over at the `Community `_." msgstr "" -#: ../settings/security/base.rst:115 -#: ../system/integrations/checkmk/api-reference.rst:13 -msgid "Example" +#: ../misc/variables/article.rst:6 +msgid "" +"Below you can find all available ticket article-based variables within " +"Zammad. These can be called via triggers for example. If you're unsure if " +"Zammad does support variables at the point you're at, you can try to type " +"``::`` to check." msgstr "" -#: ../settings/security/base.rst:107 -msgid "Let's suppose you configured the following session timeouts" +#: ../misc/variables/article.rst:9 ../misc/variables/config.rst:9 +#: ../misc/variables/ticket.rst:9 +msgid "" +"The below list gives you an example what kind of data you can expect, it's " +"not intended to explain the data itself." msgstr "" -#: ../settings/security/base.rst:104 -msgid "default: 3 weeks" +#: ../misc/variables/article.rst:11 +msgid "Article Variables" msgstr "" -#: ../settings/security/base.rst:105 -msgid "admin: 2 weeks" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "name" msgstr "" -#: ../settings/security/base.rst:106 -msgid "ticket.agent: 4 weeks" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "variable" msgstr "" -#: ../settings/security/base.rst:107 -msgid "ticket.customer: 1 week" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "example" msgstr "" -#: ../settings/security/base.rst:115 -msgid "This results in the following situations" +#: ../misc/variables/article.rst:1 +msgid "Article > Cc" msgstr "" -#: ../settings/security/base.rst:110 -msgid "a user with ``admin`` permission will have a timeout of 2 weeks" +#: ../misc/variables/article.rst:1 +msgid "``#{article.cc}``" msgstr "" -#: ../settings/security/base.rst:111 -msgid "" -"a user with ``admin`` and ``ticket.agent`` permissions will have a timeout " -"of 2 weeks" +#: ../misc/variables/article.rst:1 +msgid "``jdoe@example.com, company@example.com``" msgstr "" -#: ../settings/security/base.rst:113 -msgid "" -"a user with ``ticket.customer`` permission will have a timeout of 1 week" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Address" msgstr "" -#: ../settings/security/base.rst:115 -msgid "" -"a user with neither ``admin``, ``ticket.agent`` nor ``ticket.customer`` " -"permissions will have a timeout of 3 weeks" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.address}``" msgstr "" -#: ../settings/security/password.rst:4 -msgid "" -"This section allows you to define password requirements for the local user " -"accounts." +#: ../misc/variables/article.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:9 -msgid "" -"Zammad does **not** allow you to change your LDAP password, instead, it will " -"set a password in its local database which might confuse your users. This " -"might be addressed in the future by `#1169 `_." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Department" msgstr "" -#: ../settings/security/password.rst:14 -msgid "**Exception for admins**" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.department}``" msgstr "" -#: ../settings/security/password.rst:16 -msgid "" -"Please note that below password policies *do not* affect administrators " -"setting passwords on user accounts. While this seems strange and not safe we " -"believe that an administrator knowing an user's password is insecure as well." +#: ../misc/variables/article.rst:1 +msgid "``Sales`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:21 -msgid "The suggested workflow is either:" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Email" msgstr "" -#: ../settings/security/password.rst:23 -msgid "" -"to use third party logins to not require local passwords at all **- or -**" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.email}``" msgstr "" -#: ../settings/security/password.rst:25 -msgid "to require your *user to reset the password* upon first login." +#: ../misc/variables/article.rst:1 +msgid "``jdoe@example.com``" msgstr "" -#: ../settings/security/password.rst:27 -msgid "" -"This way administrators are not required to set a user's password at all!" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Fax" msgstr "" -#: ../settings/security/password.rst:31 -msgid "Maximum Failed Logins" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.fax}``" msgstr "" -#: ../settings/security/password.rst:33 -msgid "" -"You can choose a value between ``4`` and ``20``. This defines how often a " -"login to a user account may fail until Zammad will lock it. Your users can " -"always use the \"forgot password\" function to change their password and " -"unlock their account." -msgstr "" - -#: ../settings/security/password.rst:38 -msgid "The default value is ``10``." +#: ../misc/variables/article.rst:1 +msgid "``+4930123456789`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:42 -msgid "Beside changing the user's password, you can also unlock accounts via" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Firstname" msgstr "" -#: ../settings/security/password.rst:44 -msgid ":ref:`user management list `" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.firstname}``" msgstr "" -#: ../settings/security/password.rst:45 -msgid ":docs:`console `" +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Joe`` or empty if not set" msgstr "" -#: ../settings/security/password.rst:46 -msgid ":docs:`API `" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Lastname" msgstr "" -#: ../settings/security/password.rst:50 -msgid "Failed logins via LDAP no longer lock accounts." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.lastname}``" msgstr "" -#: ../settings/security/password.rst:53 -msgid "2 Lower Case And 2 Upper Case Characters" +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +#: ../misc/variables/ticket.rst:1 +msgid "``Doe`` or empty if not set" msgstr "" -#: ../settings/security/password.rst:55 -msgid "" -"You can add complexity to passwords by enforcing at least 2 upper and lower " -"case characters." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Login" msgstr "" -#: ../settings/security/password.rst:58 ../settings/security/password.rst:83 -msgid "The default value is ``no``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.login}``" msgstr "" -#: ../settings/security/password.rst:62 -msgid "Minimum Length" +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +#: ../misc/variables/ticket.rst:1 +msgid "``jdoe``" msgstr "" -#: ../settings/security/password.rst:64 -msgid "" -"This defines the minimum password length required for users to provide (from " -"``4`` to ``20``)." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Mobile" msgstr "" -#: ../settings/security/password.rst:67 -msgid "The default value is ``6``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.mobile}``" msgstr "" -#: ../settings/security/password.rst:71 -msgid "Digit Required" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Note" msgstr "" -#: ../settings/security/password.rst:73 -msgid "This enforces your users to use at least one digit within the password." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.note}``" msgstr "" -#: ../settings/security/password.rst:75 -msgid "The default value is ``yes``." +#: ../misc/variables/article.rst:1 +msgid "``Some note about user`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:78 -msgid "Special Character Required" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Phone" msgstr "" -#: ../settings/security/password.rst:80 -msgid "" -"This setting allows you to improve your password quality even more by " -"enforcing the password to contain at least one special character." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.phone}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:2 -msgid "SSL Certificates" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > VIP" msgstr "" -#: ../settings/security/ssl-certificates.rst:7 -msgid "" -"Zammad offers the possibility to upload custom certificates and custom " -"Certificate Authority (CA) certificates. This can be useful if you want to " -"connect Zammad the secure way to other systems which are using custom " -"certificates." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.vip}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:12 -msgid "" -"An example usecase might be: You have an internal LDAP server that is not " -"accessible from the internet, and you want a SSL-encrypted connection, using " -"a custom certificate." +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +msgid "``true`` or ``false``" msgstr "" -#: ../settings/security/ssl-certificates.rst:19 -msgid "" -"You should have an existing custom certificate file and/or a custom CA " -"certificate file, which you want to add to Zammad. As filetype ``.crt`` is " -"supported and the certificate format has to be PEM (Base64 ASCII)." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Web" msgstr "" -#: ../settings/security/ssl-certificates.rst:25 -msgid "" -"When you import a custom CA certificate, all certificates generated with " -"this are trusted. This can be useful if you have more than one system/" -"certificate you want to connect to and the certificates are issued from the " -"same custom CA." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.web}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:31 -msgid "Add a Certificate" +#: ../misc/variables/article.rst:1 +msgid "``https://zammad.com`` or empty if not set in user object" msgstr "" -#: ../settings/security/ssl-certificates.rst:33 -msgid "" -"To add a custom certificate or a custom CA certificate, head over to the " -"Admin panel > Settings > Security > SSL Certificates. Here you can find a " -"\"Add SSL Certificate\" button. In the dialog you can either select a " -"certificate file or paste the content of the certificate:" +#: ../misc/variables/article.rst:1 +msgid "Article > Created" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate adding dialog" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_at}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:43 -msgid "" -"After selecting a file or pasting the content of the certificate, click on " -"the \"Add\" button to finally upload it to Zammad. Then, the certificates " -"are immediately effective, no restart or similar required." +#: ../misc/variables/article.rst:1 +msgid "``2019-10-08 15:24:47 UTC``" msgstr "" -#: ../settings/security/ssl-certificates.rst:49 -msgid "" -"Please note that only single certificate files are supported. That means if " -"you want to import a certificate / CA certificate, it must contain **only " -"one** certificate." +#: ../misc/variables/article.rst:1 +msgid "Article > From" msgstr "" -#: ../settings/security/ssl-certificates.rst:54 -msgid "Certificate Overview" +#: ../misc/variables/article.rst:1 +msgid "``#{article.from}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:56 +#: ../misc/variables/article.rst:1 msgid "" -"After you added a certificate, you can see a table with information for each " -"added certificate:" +"``Joe Doe `` may differ, depends on ``FROM`` of send mail" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing table of added certificates" +#: ../misc/variables/article.rst:1 +msgid "Article > Sender > Name" msgstr "" -#: ../settings/security/ssl-certificates.rst:64 -msgid "" -"Here you can download the certificate or delete it, if you don't need it " -"anymore." +#: ../misc/variables/article.rst:1 +msgid "``#{article.sender.name}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:68 -msgid "Deleting Certificates" +#: ../misc/variables/article.rst:1 +msgid "``Customer``, ``Agent`` or ``System``" msgstr "" -#: ../settings/security/ssl-certificates.rst:70 -msgid "" -"If you want to delete a specific certificate, you can do it by clicking on " -"the menu in the actions column and selecting delete:" +#: ../misc/variables/article.rst:1 +msgid "Article > Subject" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate deletion button" +#: ../misc/variables/article.rst:1 +msgid "``#{article.subject}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:79 -msgid "Downloading Certificates" +#: ../misc/variables/article.rst:1 +msgid "``My amazing subject``" msgstr "" -#: ../settings/security/ssl-certificates.rst:81 -msgid "" -"If you want to download your certificates, you can do this as well via " -"corresponding action buttons." +#: ../misc/variables/article.rst:1 +msgid "Article > Text" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate download button" +#: ../misc/variables/article.rst:1 +msgid "``#{article.body}``" msgstr "" -#: ../settings/security/third-party.rst:13 -msgid "Login Providers" +#: ../misc/variables/article.rst:1 +msgid "``Test`` without formatting (plain)" msgstr "" -#: ../settings/security/third-party.rst:2 -msgid "Third-Party Applications" +#: ../misc/variables/article.rst:1 +msgid "Article > TicketID" msgstr "" -#: ../settings/security/third-party.rst:4 -msgid "" -"Third party authentication is a great way to help your users to login to " -"Zammad more easily. If the account is yet unknown, Zammad will create a new " -"user automatically, without the user needed to interact (e.g. type in his " -"name). Another big advantage of this feature is that your user doesn't need " -"to remember another password." +#: ../misc/variables/article.rst:1 +msgid "``#{article.ticket_id}``" msgstr "" -#: ../settings/security/third-party.rst:10 -msgid "" -"You can deactivate logging in via :ref:`security_password_login` if any of " -"the mentioned authentication providers are enabled in your instance." +#: ../misc/variables/article.rst:1 +msgid "``1`` (not ticket number)" msgstr "" -#: ../settings/security/third-party.rst:27 -msgid "" -"We're currently missing documentation for the following login providers:" +#: ../misc/variables/article.rst:1 +msgid "Article > To" msgstr "" -#: ../settings/security/third-party.rst:29 -msgid "LinkedIn" +#: ../misc/variables/article.rst:1 +msgid "``#{article.to}``" msgstr "" -#: ../settings/security/third-party.rst:30 -msgid "Weibo" +#: ../misc/variables/article.rst:1 +msgid "``helpdesk@example.com``" msgstr "" -#: ../settings/security/third-party.rst:35 -msgid "Automatic Account Link on Initial Logon" +#: ../misc/variables/article.rst:1 +msgid "Article > Type > Name" msgstr "" -#: ../settings/security/third-party.rst:37 -msgid "" -"In general there's two possible options for Zammad on how to deal with " -"already known users as they try to authenticate against a third-party " -"application. By default, Zammad will not automatically link \"unknown\" " -"authentication providers to existing accounts." +#: ../misc/variables/article.rst:1 +msgid "``#{article.type.name}``" msgstr "" -#: ../settings/security/third-party.rst:42 +#: ../misc/variables/article.rst:1 msgid "" -"This means that the user has to manually link authentication providers to " -"their accounts (for more about this :user-docs:`consult the user " -"documentation `)." +"``email`` (`list of article types `_)" msgstr "" -#: ../settings/security/third-party.rst:46 -msgid "" -"Sometimes this doesn't come in handy as this also means you'll receive error " -"messages about \"email address being in use already\" for (yet) unknown " -"third-party authentication methods." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Address" msgstr "" -#: ../settings/security/third-party.rst:50 -msgid "" -"If you want to allow your users to always be able to log in, no matter what, " -"you may want to enable ``Automatic account link on initial logon``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.address}``" msgstr "" -#: ../settings/security/third-party.rst:None -msgid "" -"Screenshot highlighting the \"Automatic account link on initial logon\"\n" -"setting" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Department" msgstr "" -#: ../settings/security/third-party.rst:60 -msgid "Automatic Account Linking Notification" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.department}``" msgstr "" -#: ../settings/security/third-party.rst:64 -msgid "" -"To improve security and your users awareness, you can enable Zammad to " -"notify your users when a new third-party application has been linked to " -"their account." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Email" msgstr "" -#: ../settings/security/third-party.rst:68 -msgid "" -"This notification is sent out once per third-party application. Zammad does " -"also mention the method used, e.g.: ``Microsoft``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.email}``" msgstr "" -#: ../settings/security/third-party.rst:71 -msgid "By default this setting is not active (set to ``no``)." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Fax" msgstr "" -#: ../settings/security/third-party.rst:0 -msgid "" -"Screenshot showing sample notification mail after initial\n" -"third-party linking" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.fax}``" msgstr "" -#: ../settings/security/third-party.rst:85 -msgid "" -"This notification is only sent if the account in question already exists. If " -"the login via the third-party also creates the missing account, the " -"notification will be skipped." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Firstname" msgstr "" -#: ../settings/security/third-party.rst:89 -msgid "This means it only affects:" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.firstname}``" msgstr "" -#: ../settings/security/third-party.rst:91 -msgid "manual account linking within the third-party page of the users profile" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Lastname" msgstr "" -#: ../settings/security/third-party.rst:92 -msgid "" -"logging into an existing local account by utilizing the *automatic account " -"link on initial logon* functionality" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.lastname}``" msgstr "" -#: ../settings/security/third-party.rst:None -msgid "" -"Screenshot showing the \"automatic account linking notification\"\n" -"setting" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Login" msgstr "" -#: ../settings/security/third-party.rst:100 -msgid "No User Creation on Logon" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.login}``" msgstr "" -#: ../settings/security/third-party.rst:102 -msgid "" -"By default, Zammad will create a new user account if the user logs in via a " -"third-party application and the account doesn't exist yet." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Mobile" msgstr "" -#: ../settings/security/third-party.rst:105 -msgid "" -"If you want to prevent Zammad from creating new accounts on logon, you can " -"disable this feature by setting ``No user creation on logon`` to ``yes``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.mobile}``" msgstr "" -#: ../settings/security/third-party.rst:None -msgid "Screenshot showing the \"no user creation on logon\" setting" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Note" msgstr "" -#: ../settings/security/third-party/facebook.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via Facebook To do " -"so, you need to follow these steps:" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.note}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:9 -msgid "Register Facebook App" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Phone" msgstr "" -#: ../settings/security/third-party/facebook.rst:11 -msgid "" -"Visit [https://developers.facebook.com/apps/] and click on \"Add a new App\"" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.phone}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "initial page" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > VIP" msgstr "" -#: ../settings/security/third-party/facebook.rst:17 -msgid "After that enter the app settings" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.vip}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "Create App" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Web" msgstr "" -#: ../settings/security/third-party/facebook.rst:22 -msgid "Navigate to \"Settings\" and fill in this infromation" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.web}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "App Settings" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated" msgstr "" -#: ../settings/security/third-party/facebook.rst:27 -msgid "Navigate to app review and Check \"Make [appname] public?\"" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_at}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "App Review" +#: ../misc/variables/article.rst:1 +msgid "Article > Visibility" msgstr "" -#: ../settings/security/third-party/facebook.rst:35 -msgid "Configure Zammad as Facebook App" +#: ../misc/variables/article.rst:1 +msgid "``#{article.internal}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:37 -msgid "" -"Navigate to \"Admin -> Security -> Third Party Applications\" and enter the " -"App ID and the App Secret. You can find this Key in the Dashbard of your " -"Facebok app." +#: ../misc/variables/article.rst:1 +msgid "``false`` or ``true`` (false if not internal)" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "Zammad Configuration" +#: ../misc/variables/article.rst:1 +msgid "Article Text as HTML (not referenced)" msgstr "" -#: ../settings/security/third-party/facebook.rst:44 -#: ../settings/security/third-party/github.rst:43 -#: ../settings/security/third-party/gitlab.rst:46 -msgid "" -"Now you can link accounts via \"Avatar -> Profile -> Link Accounts\" or " -"login via Zammad login page." +#: ../misc/variables/article.rst:1 +msgid "``#{article.body_as_html}``" msgstr "" -#: ../settings/security/third-party/github.rst:2 -#: ../system/integrations/github.rst:2 -msgid "GitHub" +#: ../misc/variables/article.rst:1 +msgid "``Test`` with formatting" msgstr "" -#: ../settings/security/third-party/github.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via GitHub. To " -"activate the quick login you need to enable OAuth for GitHub." +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "Ticket > Article#" msgstr "" -#: ../settings/security/third-party/github.rst:8 -msgid "Register GitHub App" +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "``#{ticket.article_count}``" msgstr "" -#: ../settings/security/third-party/github.rst:10 -msgid "" -"Visit https://www.github.com/settings/applications/new and enter the app " -"settings. As callback URL enter \"https://zammad_host/auth/github/callback\" " -"where zammad_host has to be replaced with your Zammad FQDN" +#: ../misc/variables/article.rst:1 +msgid "``1`` number of ticket articles" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "Register OAuth app on www.github.com" +#: ../misc/variables/config.rst:2 +msgid "Config" msgstr "" -#: ../settings/security/third-party/github.rst:19 -msgid "Configure Zammad as GitHub App" +#: ../misc/variables/config.rst:6 +msgid "" +"Below you'll find config related variables. These hold useful configuration " +"information that you can use within e.g. triggers to show necessary " +"information to your customer." msgstr "" -#: ../settings/security/third-party/github.rst:21 -msgid "" -"Enter the \"APP ID\" and the \"APP SECRET\" from the GitHub OAUTH " -"Applications Dashboard" +#: ../misc/variables/config.rst:11 +msgid "Config Variables" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub config in Zammad admin interface" +#: ../misc/variables/config.rst:1 +msgid "Config > Fully Qualified Domain Name" msgstr "" -#: ../settings/security/third-party/github.rst:28 -msgid "" -"After you configured the GitHub credentials and activated the login method, " -"you should see a new icon on the login page." +#: ../misc/variables/config.rst:1 +msgid "``#{config.fqdn}``" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub logo on login page" +#: ../misc/variables/config.rst:1 +msgid "``zammad.example.com``" msgstr "" -#: ../settings/security/third-party/github.rst:34 -msgid "" -"If you click on the icon you will be redirected to GitHub and see something " -"similar to this:" +#: ../misc/variables/config.rst:1 +msgid "Config > HTTP type" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub oauth page" +#: ../misc/variables/config.rst:1 +msgid "``#{config.http_type}``" msgstr "" -#: ../settings/security/third-party/github.rst:40 -#: ../settings/security/third-party/gitlab.rst:42 -msgid "" -"When you grant the access you will be redirected to your Zammad instance and " -"logged in as a customer." +#: ../misc/variables/config.rst:1 +msgid "``https`` or ``http``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:2 -msgid "Gitlab" +#: ../misc/variables/config.rst:1 +msgid "Config > Organization" msgstr "" -#: ../settings/security/third-party/gitlab.rst:4 +#: ../misc/variables/config.rst:1 +msgid "``#{config.organization}``" +msgstr "" + +#: ../misc/variables/config.rst:1 msgid "" -"It is possible to create a quick login for your helpdesk via Gitlab. To " -"activate the quick login you need to enable OAuth for Gitlab." +"``Zammad GmbH`` value set in `Branding `_" msgstr "" -#: ../settings/security/third-party/gitlab.rst:8 -msgid "Register Gitlab App" +#: ../misc/variables/config.rst:1 +msgid "Config > Product Name" msgstr "" -#: ../settings/security/third-party/gitlab.rst:10 -msgid "To register an app in Gitlab open your profile and select applications." +#: ../misc/variables/config.rst:1 +msgid "``#{config.product_name}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:12 +#: ../misc/variables/config.rst:1 msgid "" -"As callback URL enter \"https://zammad-fqdn/auth/gitlab/callback\" where " -"zammad-fqdn has to be replaced with your Zammad FQDN" +"``Helpdesk`` value set in `Branding `_" msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Register OAuth app on gitlab instance" +#: ../misc/variables/config.rst:1 +msgid "Config > SystemID" msgstr "" -#: ../settings/security/third-party/gitlab.rst:18 -msgid "Just select *read_user* under scopes as in the screenshot and save it." +#: ../misc/variables/config.rst:1 +msgid "``#{config.system_id}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:21 -msgid "Configure Zammad as Gitlab App" +#: ../misc/variables/config.rst:1 +msgid "``31`` (value between 1 and 99)" msgstr "" -#: ../settings/security/third-party/gitlab.rst:23 -msgid "" -"Enter the \"APP ID\" and the \"APP SECRET\" from the Gitlab OAUTH " -"Applications Dashboard and your Gitlab-URL in the \"SITE\" field." +#: ../misc/variables/config.rst:1 +msgid "Config > Ticket Hook" msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab config in Zammad admin interface" +#: ../misc/variables/config.rst:1 +msgid "``#{config.ticket_hook}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:30 -msgid "" -"After you configured the Gitlab credentials and activated the login method, " -"you should see a new icon on the login page." +#: ../misc/variables/config.rst:1 +msgid "``Ticket#``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab logo on login page" +#: ../misc/variables/current-user.rst:2 +msgid "Current User" msgstr "" -#: ../settings/security/third-party/gitlab.rst:36 +#: ../misc/variables/current-user.rst:6 msgid "" -"If you click on the icon you will be redirected to Gitlab and see something " -"similar to this:" +"Current user variables always return values of the current user that caused " +"e.g. a trigger to run." msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab oauth page" +#: ../misc/variables/current-user.rst:8 +msgid "" +"Due to the above fact, these variables are often not (yet) set or available " +"for usage." msgstr "" -#: ../settings/security/third-party/google.rst:4 +#: ../misc/variables/current-user.rst:10 msgid "" -"With some easy and fast steps, you can enable Zammad to authenticate your " -"users via Google." +"In situations where e.g. schedulers or triggers run, this most likely is " +"nothing you want to use." msgstr "" -#: ../settings/security/third-party/google.rst:8 -msgid "Register a Google App" +#: ../misc/variables/current-user.rst:13 +msgid "Current User Variables" msgstr "" -#: ../settings/security/third-party/google.rst:10 -msgid "" -"First of all, we need to create a new project - you can skip this step if " -"you already have one." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Address" msgstr "" -#: ../settings/security/third-party/google.rst:15 -msgid "" -"Use this link to create a new project: https://console.cloud.google.com/" -"projectcreate" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.address}``" msgstr "" -#: ../settings/security/third-party/google.rst:18 -msgid "" -"Now expand the menu, expand \"APIs & Services\" and select \"Credentials\". " -"Go to the tab \"OAuth consent screen\" first and ensure to fill in the " -"requested information - without doing so you can't create credentials!" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set" msgstr "" -#: ../settings/security/third-party/google.rst:None -msgid "Creating a consent screen" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Avatar" msgstr "" -#: ../settings/security/third-party/google.rst:25 -msgid "" -"After filling in and saving the consent screen information, you can go to " -"the \"Credentials\" tab and create new \"OAuth client ID\"-Credentials." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/google.rst:28 -msgid "" -"Fill in the necessary information as follows and replace ``zammad_host`` " -"with your FQDN:" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "avatar picture with width and height in pixel (e.g. 60,60)" msgstr "" -#: ../settings/security/third-party/google.rst:31 -msgid "**Application type** ``[x] Web application``" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created at" msgstr "" -#: ../settings/security/third-party/google.rst:34 -msgid "**Authorized JavaScript origins** ``https://zammad_host/``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_at}``" msgstr "" -#: ../settings/security/third-party/google.rst:37 -msgid "" -"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" -"callback``" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC``" msgstr "" -#: ../settings/security/third-party/google.rst:None -msgid "Adding a new OAuth client ID" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Address" msgstr "" -#: ../settings/security/third-party/google.rst:43 -msgid "" -"After creating the credentials, go to your Zammad installation and navigate " -"to \"Admin > Security > Third Party Applications\" > Google. Enter your " -"Client ID and Client secret here." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.address}``" msgstr "" -#: ../settings/security/third-party/google.rst:None -msgid "Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Avatar" msgstr "" -#: ../settings/security/third-party/google.rst:50 -msgid "After submitting, the login via Google can be used." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:2 -msgid "Microsoft" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Department" msgstr "" -#: ../settings/security/third-party/microsoft.rst:4 -msgid "" -"Zammad's Microsoft connection allows your users with Microsoft accounts to " -"login. This works for Azure users as well and can be an alternative to :doc:" -"`/system/integrations/ldap/index`." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.department}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:10 -msgid "" -"This documentation part does not cover our :doc:`📧 Microsoft 365 email " -"channel `." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Sales`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screenshot showing Microsoft login button on Zammad login screen." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Email" msgstr "" -#: ../settings/security/third-party/microsoft.rst:30 -#: ../settings/security/third-party/microsoft.rst:53 -msgid "Supported account types:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.email}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:22 -msgid "" -"Please note that Zammad only supports these account types (App dependent):" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``jdoe@customer.tld``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:35 -msgid "Avatars of signing in users:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Fax" msgstr "" -#: ../settings/security/third-party/microsoft.rst:33 -msgid "" -"Zammad currently ignores user avatars. If the user is registered with e.g. " -"Gravatar, Zammad will fetch the avatar from there if enabled. See :doc:" -"`Zammad Image Service ` for more." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.fax}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:38 -msgid "Step 1 - Register a Microsoft App for Zammad" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``004930123464789`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:40 -msgid "" -"Login to the `Microsoft Azure Portal `_ and " -"navigate to App registrations to create a new app. Provide the requested " -"information as follows and register your app." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Firstname" msgstr "" -#: ../settings/security/third-party/microsoft.rst:46 -msgid "Name:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.firstname}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:45 -msgid "" -"Any meaningful name fitting, this name will be displayed to users trying to " -"authenticate with this app." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``John`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:49 -msgid "Choose one of the above mentioned account types (see Limitations)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Lastname" msgstr "" -#: ../settings/security/third-party/microsoft.rst:51 -msgid "" -"The correct account type depends on your use case. If you want to use the " -"authentication internal only, choose the first option. If you're unsure, use " -"the \"Help me choose...\" link." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.lastname}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:58 -msgid "Redirect URI (optional):" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Login" msgstr "" -#: ../settings/security/third-party/microsoft.rst:56 -msgid "" -"Select web and provide your callback URL. The callback URL looks like this: " -"``https://zammad.domain.tld/auth/microsoft_office365/callback``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.login}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to register a Microsoft app" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Mobile" msgstr "" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "Within **API permissions** add the following permissions:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.mobile}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:69 -msgid "``User.Read``" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``0049176123456789`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "Contacts" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Note" msgstr "" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "``Contacts.Read``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.note}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:73 -msgid "" -"You can find these permissions within *Microsoft Graph → Delegated " -"permissions*." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Some note to this user`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to add required API permissions" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Phone" msgstr "" -#: ../settings/security/third-party/microsoft.rst:80 -msgid "" -"Within **Certificates & secrets** create a new client secret. Note down the " -"returned secret **value** for later. **Do not** use the secret ID!" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.phone}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to create a new app secret" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``004930123456789`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:88 -msgid "" -"From **Overview** copy your apps *Application (client) ID*. If you're using " -"a single tenant app, please also copy *Directory (tenant) ID*. You now have " -"all required information for Zammad." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > VIP" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to retreive application client and tenant IDs" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.vip}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:98 -msgid "Step 2 - Add App Credentials to Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Web" msgstr "" -#: ../settings/security/third-party/microsoft.rst:100 -msgid "" -"Navigate to Security > Third-party Applications (Tab) within Zammad's admin " -"settings. Scroll down to the section *Authentication via Microsoft* and fill " -"in the required information." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.web}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:105 -msgid "App ID:" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``https://zammad.org`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:105 -msgid "This is your *Application (client) ID*." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Department" msgstr "" -#: ../settings/security/third-party/microsoft.rst:108 -msgid "App secret:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.department}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:108 -msgid "This is your *client secret* (value)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Email" msgstr "" -#: ../settings/security/third-party/microsoft.rst:113 -msgid "App Tenant ID:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.email}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:111 -msgid "" -"**optional** only required for apps that use account type *Accounts in this " -"organizational directory only (Default Directory only - Single tenant).*" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Fax" msgstr "" -#: ../settings/security/third-party/microsoft.rst:115 -msgid "" -"Apply your settings by pressing submit and activate *Authentication via " -"Microsoft*." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.fax}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "" -"Screencast showing how to add app credentials and activating the\n" -"authentication method" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Firstname" msgstr "" -#: ../settings/security/third-party/saml.rst:2 -msgid "SAML" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.firstname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:4 -msgid "" -"Connect your SAML (Security Assertion Markup Language) identity provider as " -"a single sign-on (SSO) method." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Lastname" msgstr "" -#: ../settings/security/third-party/saml.rst:7 -msgid "" -"SAML is an open standard for SSO authentication (among other things). Sign-" -"ins are shared across multiple **service providers** and managed by a " -"central **identity provider** (IdP)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.lastname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:11 -msgid "" -"In this case, the service provider is Zammad, and the IdP is a software " -"service that you either host or subscribe to (*e.g.,* `Keycloak `_, `Redhat SSO Server `_, `ADFS `_, or `Okta `_)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Login" msgstr "" -#: ../settings/security/third-party/saml.rst:18 -msgid "" -"This guide assumes you are already using SAML within your organization (i." -"e., that your IdP is fully set up)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.login}``" msgstr "" -#: ../settings/security/third-party/saml.rst:21 -msgid "" -"Please note: Our instructions are based on connecting Zammad with Keycloak." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Mobile" msgstr "" -#: ../settings/security/third-party/saml.rst:25 -msgid "Step 1: Configure Your IdP" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.mobile}``" msgstr "" -#: ../settings/security/third-party/saml.rst:28 -msgid "Add Zammad as a Client/App" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Note" msgstr "" -#: ../settings/security/third-party/saml.rst:30 -msgid "" -"Import Zammad into your IdP using the XML configuration found at ``https://" -"your.zammad.domain/auth/saml/metadata``." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.note}``" msgstr "" -#: ../settings/security/third-party/saml.rst:33 -msgid "" -"If your IdP doesn't support XML import, you will have to configure Zammad as " -"a new client/app manually using the above XML metadata file for reference." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Domain based assignment" msgstr "" -#: ../settings/security/third-party/saml.rst:36 -msgid "For instance, when you see this tag:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.domain_assignment}``" msgstr "" -#: ../settings/security/third-party/saml.rst:42 -msgid "" -"Set the **Assertion Consumer Service Binding URL** (sometimes also listed as " -"**Valid Redirect URIs**) to ``http://your.zammad.domain/auth/saml/callback``." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Domain" msgstr "" -#: ../settings/security/third-party/saml.rst:47 -msgid "Set Up User Attribute Mapping" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.domain}``" msgstr "" -#: ../settings/security/third-party/saml.rst:49 -msgid "" -"Zammad requests the following user attributes (or “properties”) from the IdP:" +#: ../misc/variables/current-user.rst:1 +msgid "``zammad.com`` or empty if not set" msgstr "" -#: ../settings/security/third-party/saml.rst:51 -msgid "Email address (``email``)" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Name" msgstr "" -#: ../settings/security/third-party/saml.rst:52 -msgid "Full name (``name``)" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.name}``" msgstr "" -#: ../settings/security/third-party/saml.rst:53 -msgid "Given name (``first_name``)" +#: ../misc/variables/current-user.rst:1 +msgid "``Zammad GmbH``" msgstr "" -#: ../settings/security/third-party/saml.rst:54 -msgid "Family name (``last_name``)" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Note" msgstr "" -#: ../settings/security/third-party/saml.rst:56 -msgid "" -"You may need to set up “mappers” (or “mappings”) to tell your IdP how user " -"attributes in SAML correspond to those in Zammad. For a more detailed " -"breakdown, refer to the XML metadata file referenced in the previous section." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.note}``" msgstr "" -#: ../settings/security/third-party/saml.rst:62 -msgid "Per-IdP Instructions" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``A note to the organization of the user`` or empty if not set" msgstr "" -#: ../settings/security/third-party/saml.rst:102 -msgid "Keycloak" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Shared organization" msgstr "" -#: ../settings/security/third-party/saml.rst:65 -msgid "" -"**To add Zammad as a client,** save the XML configuration to disk (``https://" -"your.zammad.domain/auth/saml/metadata``) and use **Clients > Clients list > " -"Import client** in the Keycloak admin panel." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.shared}``" msgstr "" -#: ../settings/security/third-party/saml.rst:70 -msgid "" -"To help Zammad **match its own user accounts to Keycloak users**, create a " -"user attribute (or “property”) mapper. In **Clients list**, click on your " -"newly created Client ID, choose the tab **Client scopes** and click on the " -"link which refers to your Zammad instance. Choose **Add mapper > By " -"configuration > User Property** and create a mapper with the following " -"entries:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > VIP" msgstr "" -#: ../settings/security/third-party/saml.rst:78 -msgid "**Name**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.vip}``" msgstr "" -#: ../settings/security/third-party/saml.rst:80 -msgid "**Mapper Type**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Phone" msgstr "" -#: ../settings/security/third-party/saml.rst:81 -msgid "``User Property``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.phone}``" msgstr "" -#: ../settings/security/third-party/saml.rst:82 -msgid "**Property**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated at" msgstr "" -#: ../settings/security/third-party/saml.rst:83 -msgid "``emailAddress``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_at}``" msgstr "" -#: ../settings/security/third-party/saml.rst:84 -msgid "**SAML Attribute Name**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Address" msgstr "" -#: ../settings/security/third-party/saml.rst:86 -msgid "**SAML Attribute NameFormat**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.address}``" msgstr "" -#: ../settings/security/third-party/saml.rst:87 -msgid "``basic``" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Avatar" msgstr "" -#: ../settings/security/third-party/saml.rst:89 -msgid "" -"In the example above, we're telling Zammad that whenever it receives a SAML " -"login request, it should take the ``email`` property from Keycloak, look for " -"a Zammad user with the same ``email`` attribute, and create a new session " -"for that user." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/saml.rst:95 -msgid "" -"If your Keycloak users' email addresses are stored on another property (*e." -"g.,* ``username``), adjust accordingly." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Department" msgstr "" -#: ../settings/security/third-party/saml.rst:98 -msgid "" -"Back in **Settings**, enter the Client ID (``https://your.zammad.domain/auth/" -"saml/metadata``) in the field **Master SAML Processing URL**." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.department}``" msgstr "" -#: ../settings/security/third-party/saml.rst:101 -msgid "You also need to enable **Sign assertions**." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Email" msgstr "" -#: ../settings/security/third-party/saml.rst:105 -msgid "Step 2: Configure Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.email}``" msgstr "" -#: ../settings/security/third-party/saml.rst:107 -msgid "" -"Enable SAML and enter your IdP's details in the Admin Panel under **Settings " -"> Security > Third Party Applications > Authentication via SAML**:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Fax" msgstr "" -#: ../settings/security/third-party/saml.rst:None -msgid "Example configuration of SAML part 1" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.fax}``" msgstr "" -#: ../settings/security/third-party/saml.rst:119 -msgid "Display name" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Firstname" msgstr "" -#: ../settings/security/third-party/saml.rst:116 -msgid "" -"Allows you to define a custom button name for SAML. This helps your users to " -"understand better what the button on the login page does." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.firstname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:119 -msgid "Defaults to ``SAML``." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Lastname" msgstr "" -#: ../settings/security/third-party/saml.rst:123 -msgid "IDP SSO target URL" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.lastname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:122 -msgid "" -"This is the target URL Zammad shall redirect to when the user presses the " -"SAML button. For Keycloak, this needs to look like https://your.domain/" -"realms/your-realm/protocol/saml" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Login" msgstr "" -#: ../settings/security/third-party/saml.rst:127 -msgid "IDP single logout target URL" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.login}``" msgstr "" -#: ../settings/security/third-party/saml.rst:126 -msgid "" -"This is the URL to which the single logout request and response should be " -"sent." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Mobile" msgstr "" -#: ../settings/security/third-party/saml.rst:131 -msgid "IDP certificate" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.mobile}``" msgstr "" -#: ../settings/security/third-party/saml.rst:130 -msgid "" -"The public certificate of your IDP for Zammad to verify during the callback " -"phase." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Note" msgstr "" -#: ../settings/security/third-party/saml.rst:145 -msgid "IDP certificate fingerprint" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.note}``" msgstr "" -#: ../settings/security/third-party/saml.rst:134 -msgid "" -"The fingerprint of your IDPs public certificate to verify during callback " -"phase." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Phone" msgstr "" -#: ../settings/security/third-party/saml.rst:137 -msgid "🔏 **For the IdP certificate / certificate fingerprint:**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.phone}``" msgstr "" -#: ../settings/security/third-party/saml.rst:139 -msgid "" -"Provide **only one or the other**—do not provide both! (Between the two, we " -"recommend the signing certificate itself: fingerprints use SHA-1, which `has " -"been broken for a while now `_.)" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > VIP" msgstr "" -#: ../settings/security/third-party/saml.rst:144 -msgid "" -"**Keycloak users:** Find your certificate in the Keycloak admin panel under " -"**Realm Settings > Keys > Algorithm: RS256 > Certificate**." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.vip}``" msgstr "" -#: ../settings/security/third-party/saml.rst:151 -msgid "Name identifier format" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``false`` or ``true``" msgstr "" -#: ../settings/security/third-party/saml.rst:148 -msgid "" -"This is the unique identifiers field type. Usually it should be ``urn:oasis:" -"names:tc:SAML:1.1:nameid-format:emailAddress``." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Web" msgstr "" -#: ../settings/security/third-party/saml.rst:151 -msgid "Zammad **expects an email address as unique identifier**!" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.web}``" msgstr "" -#: ../settings/security/third-party/saml.rst:155 -msgid "UID attribute name" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > VIP" msgstr "" -#: ../settings/security/third-party/saml.rst:154 -msgid "" -"Here you can define an attribute that uniquely identifies the user. If " -"unset, the name identifier returned by the IDP is used." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.vip}``" msgstr "" -#: ../settings/security/third-party/saml.rst:None -msgid "Example configuration of SAML part 2" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Web" msgstr "" -#: ../settings/security/third-party/saml.rst:163 -msgid "" -"Decide if the certificate for the connection to the IdP service has to be " -"verified or not (default: ``yes``)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.web}``" msgstr "" -#: ../settings/security/third-party/saml.rst:169 -msgid "Signing & Encrypting" +#: ../misc/variables/ticket.rst:6 +msgid "" +"Below you can find all available ticket-based variables within Zammad. These " +"can be called via triggers for example. If you're unsure if Zammad does " +"support variables at the point you're at, you can try to type ``::`` to " +"check." msgstr "" -#: ../settings/security/third-party/saml.rst:169 -msgid "" -"Define if you want to sign, encrypt, do both or nothing for the requests." +#: ../misc/variables/ticket.rst:12 +msgid "Ticket Variables" msgstr "" -#: ../settings/security/third-party/saml.rst:179 -msgid "Certificate (PEM)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Accounted Time" msgstr "" -#: ../settings/security/third-party/saml.rst:172 -msgid "" -"Paste the public certificate of your Zammad SAML client, if you want to " -"encrypt the requests." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.time_unit}``" msgstr "" -#: ../settings/security/third-party/saml.rst:175 -msgid "Make sure the certificate is:" +#: ../misc/variables/ticket.rst:1 +msgid "``1``, ``2.75`` or empty response" msgstr "" -#: ../settings/security/third-party/saml.rst:177 -msgid "already valid and not yet expired" +#: ../misc/variables/ticket.rst:1 +msgid "``3``, any number of articles existing in the ticket right now" msgstr "" -#: ../settings/security/third-party/saml.rst:178 -msgid "no CA certificate" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Closing time" msgstr "" -#: ../settings/security/third-party/saml.rst:179 -msgid "valid for signing and encrypting" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.close_at}``" msgstr "" -#: ../settings/security/third-party/saml.rst:185 -msgid "Private key (PEM)" +#: ../misc/variables/ticket.rst:1 +msgid "2019-10-07 17:25:00 UTC" msgstr "" -#: ../settings/security/third-party/saml.rst:182 -msgid "" -"Paste the private key of your Zammad SAML client here, if you want to sign " -"the requests." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created at" msgstr "" -#: ../settings/security/third-party/saml.rst:185 -msgid "Make sure the key is an RSA key with a length of at least 2048 bits." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_at}``" msgstr "" -#: ../settings/security/third-party/saml.rst:188 -msgid "Private key secret" +#: ../misc/variables/ticket.rst:1 +msgid "2019-10-07 16:25:00 UTC" msgstr "" -#: ../settings/security/third-party/saml.rst:188 -msgid "If your private key is secured with a secret, you can provide it here." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Address" msgstr "" -#: ../settings/security/third-party/saml.rst:192 -msgid "Your callback URL" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.address}``" msgstr "" -#: ../settings/security/third-party/saml.rst:191 -msgid "" -"This URL is needed for your IdP configuration so it knows where to redirect " -"to after successful authentication." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Avatar" msgstr "" -#: ../settings/security/third-party/saml.rst:194 -msgid "" -"After saving your input by clicking on the \"Submit\" button, Zammad " -"verifies the provided keys/certificates (e.g. if they are valid for signing/" -"encrypting and if they aren't expired)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/saml.rst:199 -msgid "" -"See :ref:`automatic account linking ` for details " -"on how to link existing Zammad accounts to IdP accounts." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Department" msgstr "" -#: ../settings/security/third-party/saml.rst:205 -msgid "Automatic account linking doesn't work" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.department}``" msgstr "" -#: ../settings/security/third-party/saml.rst:206 -msgid "" -"Have you double-checked your IdP's user attribute mapping configuration?" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Email" msgstr "" -#: ../settings/security/third-party/twitter.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via Twitter. To do " -"so, you need to follow these steps:" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.email}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:8 -msgid "Register Twitter App" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Fax" msgstr "" -#: ../settings/security/third-party/twitter.rst:10 -msgid "Go to https://dev.twitter.com/apps and login with your account." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.fax}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:15 -msgid "Click on \"Create App\"" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Firstname" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "new app page" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.firstname}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:20 -msgid "" -"Enter app settings. As \"Callback URL\" you need to enter ``https://" -"zammad_host/api/v1/external_credentials/twitter/callback``. You need to " -"replace ``zammad_host`` with the domain of your Zammad system." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Lastname" msgstr "" -#: ../settings/security/third-party/twitter.rst:24 -msgid "" -"After the app has been created, update the application icon and organization " -"attributes." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.lastname}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "set permissions to receive and send direct messages" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Login" msgstr "" -#: ../settings/security/third-party/twitter.rst:30 -msgid "" -"Next we need to set ``read, write and access direct messages`` permissions " -"for the app." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.login}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "click on Keys & Access Token, note them" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Mobile" msgstr "" -#: ../settings/security/third-party/twitter.rst:36 -msgid "" -"Go to \"Keys and Access Token\" tab and note the \"Consumer Key\" and " -"\"Consumer Secret\"." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.mobile}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:40 -msgid "Configure Zammad as Twitter App" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Note" msgstr "" -#: ../settings/security/third-party/twitter.rst:42 -msgid "" -"Go to \"Admin > Security > Twitter > Third Party Applications > Twitter\" " -"Section." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.note}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "Admin > Security > Third Party Applications" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Phone" msgstr "" -#: ../settings/security/third-party/twitter.rst:48 -msgid "" -"Fill in the \"Twitter Key\" and the \"Twitter Secret\" and click the " -"\"Submit\" button." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.phone}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:51 -msgid "" -"Now you can link accounts via \"Avatar > Profile > Link Accounts\" or login " -"via Zammad login page." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > VIP" msgstr "" -#: ../settings/security/two-factor.rst:11 -msgid "Two-factor Authentication Methods" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.vip}``" msgstr "" -#: ../settings/security/two-factor.rst:2 -msgid "Two-Factor Authentication" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Web" msgstr "" -#: ../settings/security/two-factor.rst:4 -msgid "" -"Two-factor authentication (2FA) enhances the security of Zammad accounts by " -"adding an extra layer of verification beyond a password. It requires users " -"to provide two different types of authentication factors, typically " -"something they know (like a password) and something they possess (like a " -"mobile device or a security token), to ensure that only authorized " -"individuals can access the account." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.web}``" msgstr "" -#: ../settings/security/two-factor.rst:19 -msgid "Enable Recovery Codes" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Address" msgstr "" -#: ../settings/security/two-factor.rst:21 -msgid "" -"Recovery codes are one-time use security codes that can be used by the user " -"if they lose access to their other two-factor authentication methods. They " -"cannot be used on their own, they can only be activated if at least one two-" -"factor authentication method is enabled." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.address}``" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Enable Recovery Codes Setting" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Avatar" msgstr "" -#: ../settings/security/two-factor.rst:30 -msgid "" -"Recovery codes can only be used as a backup method. If enabled, they will be " -"automatically generated for the user once they set up their initial two-" -"factor authentication method." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.avatar(60,60)}``" msgstr "" -#: ../settings/security/two-factor.rst:34 -msgid "" -"The user will be asked to print out or save the generated recovery codes in " -"a safe place. Once used, a recovery code cannot be reused." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Department" msgstr "" -#: ../settings/security/two-factor.rst:37 -msgid "" -"Users will also have an option to regenerate their recovery codes at any " -"time, which invalidates already existing recovery codes and provides them " -"with a list of fresh codes." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.department}``" msgstr "" -#: ../settings/security/two-factor.rst:41 -msgid "" -"After you enable this setting, when the user completes a setup of their " -"initial two-factor authentication method, they will be presented with a list " -"of recovery codes and instructed to save them for later use." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Email" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Recovery Codes Generation Modal Dialog" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.email}``" msgstr "" -#: ../settings/security/two-factor.rst:50 -msgid "Enforce the Set Up of the Two-Factor Authentication" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Fax" msgstr "" -#: ../settings/security/two-factor.rst:52 -msgid "" -"In case you wish to require your users to set up at least one two-factor " -"authentication method for their account, you can do this by selecting " -"specific user roles the requirement applies to in **Enforced for user " -"roles** setting. Of course you must have at least one two-factor " -"authentication method enabled for this setting to take effect." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.fax}``" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Enforced for User Roles Setting" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Firstname" msgstr "" -#: ../settings/security/two-factor.rst:62 -msgid "" -"After you change this setting, if the user has one of the selected roles on " -"their account, they will be forced to set up the two-factor authentication " -"upon next sign in or application reload." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.firstname}``" msgstr "" -#: ../settings/security/two-factor.rst:66 -msgid "" -"A modal dialog with instructions will be shown, and they will not be able to " -"do any work before they set up at least one two-factor method." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Lastname" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Modal Dialog for Enforcing Two-Factor Authentication Set Up" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.lastname}``" msgstr "" -#: ../settings/security/two-factor.rst:74 -msgid "Reset Two-Factor Authentication for a Specific User" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Login" msgstr "" -#: ../settings/security/two-factor.rst:76 -msgid "" -"In case an user isn't able to login anymore because of an inaccessible " -"second factor, you can reset the user's 2FA method." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.login}``" msgstr "" -#: ../settings/security/two-factor.rst:79 -msgid "" -"To do this, go to the user management and search for the relevant user. " -"After you found the account, click the button in the action column and " -"select \"Manage Two-Factor Authentication\":" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Mobile" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Context menu in action column in user management" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.mobile}``" msgstr "" -#: ../settings/security/two-factor.rst:87 -msgid "" -"After selecting this, you can see a dialog where you can either reset one " -"2FA method or reset all of the user's 2FA methods:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Note" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Dialog for resetting user's 2FA method" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.note}``" msgstr "" -#: ../settings/security/two-factor.rst:94 -msgid "" -"Choose the fitting one, click on the corresponding \"Remove ...\" button and " -"confirm your action. The user now has to setup a new 2FA method, depending " -"on your 2FA configuration." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Phone" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:2 -msgid "Authenticator App" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.phone}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:4 -msgid "" -"The authenticator app method is a type of two-factor authentication that " -"uses a mobile application to generate one-time codes for account " -"verification. After setting up the authenticator app on their device, the " -"user links it to their Zammad account." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > VIP" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:12 -msgid "" -"When logging in, the user is prompted to enter a time-sensitive code " -"generated by the app, in addition to their password. This code acts as the " -"second factor of authentication, providing an extra layer of security as it " -"changes periodically and is unique to the user's device." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.vip}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:None -msgid "Security Code in Google Authenticator App" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Web" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:22 -msgid "" -"The app generates codes based on a shared secret key stored securely on both " -"the user's device and the server, ensuring a synchronized and secure " -"authentication process. The method of generating the codes is sometimes also " -"called TOTP (time-based one-time password)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.web}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:28 -msgid "Enabling the Authenticator App Method" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Escalation at" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:30 -#: ../settings/security/two-factor/security-keys.rst:28 -msgid "To enable the method, just toggle the switch on in the settings." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.escalation_at}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:None -msgid "Authenticator App Switch in Settings" +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:36 -msgid "" -"Now the users will be able to set up this two-factor authentication method " -"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " -"Once they do, on next sign-in with password, they will be asked to provide " -"an additional security code generated by their mobile device." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > First response" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:2 -msgid "Security Keys" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.first_response_at}``" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:4 -msgid "" -"The security keys method is a type of a two-factor authentication that uses " -"Web Authentication API in the browser for verifying user's identity. The " -"user can register multiple hardware or software security keys with their " -"Zammad account and then they can use it during the sign-in process." +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable yet" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:12 -msgid "" -"When logging in, the user is prompted to provide the same security key they " -"registered with their account, in addition to their password. This key acts " -"as the second factor of authentication, providing an extra layer of security." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Assign Follow-Ups" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:None -msgid "Security Key dialog in Safari on macOS" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_assignment}``" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:21 -msgid "" -"The type of the key can range from hardware USB sticks to passkeys stored in " -"a device of user's choice. Which type can be used depends on the browser " -"flavor and the platform of the user." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Assignment Timeout" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:26 -msgid "Enabling the Security Keys Method" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.assignment_timeout}``" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:None -msgid "Security Keys Switch in Settings" +#: ../misc/variables/ticket.rst:1 +msgid "``20`` or empty if not configured" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:34 -msgid "" -"Now the users will be able to set up this two-factor authentication method " -"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " -"Once they do, on next sign-in with password, they will be asked to provide " -"the same security key they registered during the setup." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Follow-up possible" msgstr "" -#: ../settings/system/system-selfhosted.include.rst:3 -msgid "" -"Below settings are only available to self hosted users. In hosted " -"environments we're handling these settings for you to ensure service " -"stability." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_possible}``" msgstr "" -#: ../settings/system/base.rst:11 -msgid "Fully Qualified Domain Name" +#: ../misc/variables/ticket.rst:1 +msgid "``no`` or ``yes``" msgstr "" -#: ../settings/system/base.rst:7 -msgid "The URL of your Zammad installation." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Name" msgstr "" -#: ../settings/system/base.rst:9 ../settings/system/base.rst:17 -msgid "This setting is used within :doc:`/system/variables` and notifications." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.name}``" msgstr "" -#: ../settings/system/system-base.include.rst:1 -msgid "It is automatically set by the *Getting Started wizard*." +#: ../misc/variables/ticket.rst:1 +msgid "``Sales``" msgstr "" -#: ../settings/system/system-base.include.rst:5 -msgid "Changing this setting also changes callback URLs for your channels etc." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Note" msgstr "" -#: ../settings/system/system-base.include.rst:6 -msgid "This setting can have negative affects on being able to login." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.note}``" msgstr "" -#: ../settings/system/base.rst:19 -msgid "HTTP type" +#: ../misc/variables/ticket.rst:1 +msgid "``Note about this group``" msgstr "" -#: ../settings/system/base.rst:14 -msgid "" -"The HTTP type tells your installation how your clients connect. This is " -"relevant for authentication and cookie security." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > ID" msgstr "" -#: ../settings/system/base.rst:31 -msgid "SystemID" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.id}``" msgstr "" -#: ../settings/system/base.rst:22 -msgid "" -"This ID is being used within your ticket number. In case you're " -"communicating with another ticket system with similar ticket number schemes " -"this ID greatly reduces the risk of false follow ups." +#: ../misc/variables/ticket.rst:1 +msgid "``17``, ``5281``, ..." msgstr "" -#: ../settings/system/base.rst:26 -msgid "" -"The SystemID is randomly selected upon installation of Zammad (``1-99``)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact (agent)" msgstr "" -#: ../settings/system/base.rst:30 -msgid "" -"**Do not** change this setting in a productive system! Your Zammad " -"installation may no longer recognize old ticket number based follow ups upon " -"change!" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_agent_at}``" msgstr "" -#: ../settings/system/frontend.rst:2 -msgid "Frontend" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact (customer)" msgstr "" -#: ../settings/system/frontend.rst:22 -msgid "Core Workflow Ajax Mode" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_customer_at}``" msgstr "" -#: ../settings/system/frontend.rst:6 +#: ../misc/variables/ticket.rst:1 msgid "" -"This setting allows administrators to enforce :doc:`/system/core-workflows` " -"to use Ajax-Calls instead of web sockets. You'll usually only need this if " -"you experience serious issues as noted below." +"``2019-10-07 16:25:00 UTC`` or empty if not applicable yet (Please note " +"`Ticket last contact behavior Settings `_ for this)" msgstr "" -#: ../settings/system/frontend.rst:10 -msgid "**🤓 Possible (technical) reasons**" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact" msgstr "" -#: ../settings/system/frontend.rst:12 -msgid "" -"In some cases, your network structure (e.g. firewalls, proxies) may " -"disconnect long web socket connections. This leads to select fields staying " -"empty (e.g. owner selection *after* selecting your group) or fields not " -"shown / hidden (e.g. when switching to or from pending states, the \"pending " -"till\" field not showing / hiding)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_at}``" msgstr "" -#: ../settings/system/frontend.rst:18 -msgid "" -"Please keep in mind that the Ajax fallback may cause serious pressure on " -"your application server. If you have the choice stick to web sockets." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Number" msgstr "" -#: ../settings/system/frontend.rst:22 -msgid "Default: ``no`` (inactive)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.number}``" msgstr "" -#: ../settings/system/frontend.rst:53 -msgid "Show calendar weeks in the picker of date/datetime fields" +#: ../misc/variables/ticket.rst:1 +msgid "``31001``, ``201910731001``, ..." msgstr "" -#: ../settings/system/frontend.rst:25 -msgid "" -"With this setting you can instruct Zammad to provide week number display " -"globally for all users. Calendar with week number display are usually used " -"in business sectors and may not be relevant for everyone." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain based assignment" msgstr "" -#: ../settings/system/frontend.rst:29 -msgid "" -"This setting affects *all areas* - you'll also see week numbers in the admin " -"panel for e.g. triggers and macros." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain_assignment}``" msgstr "" -#: ../settings/system/frontend.rst:32 -msgid "Default: ``no`` (not shown)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain" msgstr "" -#: ../settings/system/frontend.rst:53 -msgid "Here's the difference:" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain}``" msgstr "" -#: ../settings/system/frontend.rst:0 -msgid "Screenshot showing Zammad's date picker (in the default way)" +#: ../misc/variables/ticket.rst:1 +msgid "``domain.tld`` or empty if not set" msgstr "" -#: ../settings/system/frontend.rst:41 -msgid "Set to ``no``" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Name" msgstr "" -#: ../settings/system/frontend.rst:0 -msgid "" -"Screenshot showing Zammad's date picker with\n" -"week numbers enabled" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.name}``" msgstr "" -#: ../settings/system/frontend.rst:50 -msgid "Set to ``yes``" +#: ../misc/variables/ticket.rst:1 +msgid "``Zammad GmbH`` or empty if not set" msgstr "" -#: ../settings/system/index.rst:4 -msgid "" -"For your overview we split each tab within system settings into its own page:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Note" msgstr "" -#: ../settings/system/index.rst:16 -msgid "Console Based Settings" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.note}``" msgstr "" -#: ../settings/system/index.rst:18 -msgid "" -"There's some console based settings we didn't put into the UI. However, you " -"may find them helpful - you can find them in our :docs:`hidden settings ` section." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Shared organization" msgstr "" -#: ../settings/system/network.rst:2 -msgid "Network" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.shared}``" msgstr "" -#: ../settings/system/network.rst:8 -msgid "" -"The proxy settings can only be saved after successfully testing the proxy " -"connection." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > VIP" msgstr "" -#: ../settings/system/network.rst:15 -msgid "Proxy Address." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.vip}``" msgstr "" -#: ../settings/system/network.rst:12 -msgid "" -"Allows you to provide a proxy server if needed. This is relevant for network " -"communication by Zammad." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Address" msgstr "" -#: ../settings/system/network.rst:15 -msgid "It **does not** affect the update process or Elasticsearch." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.address}``" msgstr "" -#: ../settings/system/network.rst:18 -msgid "Username for proxy connection." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Avatar" msgstr "" -#: ../settings/system/network.rst:18 -msgid "" -"If your proxy server requires authentication, provide the username here." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.avatar(60,60)}``" msgstr "" -#: ../settings/system/network.rst:21 -msgid "Password for proxy connection." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Department" msgstr "" -#: ../settings/system/network.rst:21 -msgid "" -"If your proxy server requires authentication, provide the password here." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.department}``" msgstr "" -#: ../settings/system/network.rst:26 -msgid "No proxy for the following hosts." +#: ../misc/variables/ticket.rst:1 +msgid "``Support`` or empty if not set" msgstr "" -#: ../settings/system/network.rst:24 -msgid "" -"Exception list for hosts you can't or don't want to reach via proxy server." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Email" msgstr "" -#: ../settings/system/network.rst:27 -msgid "Default: ``localhost,127.0.0.0,::1``" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.email}``" msgstr "" -#: ../settings/system/services.rst:2 -msgid "Services" +#: ../misc/variables/ticket.rst:1 +msgid "``agent@company.tld`` or empty if not set" msgstr "" -#: ../settings/system/services.rst:10 -msgid "Image Service" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Fax" msgstr "" -#: ../settings/system/services.rst:5 -msgid "Defines the backend for user and organization image lookups." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.fax}``" msgstr "" -#: ../settings/system/services.rst:7 -msgid "Default: ``Zammad Image Service`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Firstname" msgstr "" -#: ../settings/system/services.rst:9 -msgid "" -"Make sure your on premise installation has ``HTTPS`` access to ``images." -"zammad.com``." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.firstname}``" msgstr "" -#: ../settings/system/services.rst:18 -msgid "Geo Calendar Service" +#: ../misc/variables/ticket.rst:1 +msgid "``Max`` or empty if not set" msgstr "" -#: ../settings/system/services.rst:13 -msgid "" -"Defines the backend for geo calendar lookups. Used for initial calendar " -"setup." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Lastname" msgstr "" -#: ../settings/system/services.rst:16 -msgid "Default: ``Zammad GeoCalendar Service`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.lastname}``" msgstr "" -#: ../settings/system/services.include.rst:2 -msgid "" -"Make sure your on premise installation has ``HTTPS`` access to ``geo.zammad." -"com``." +#: ../misc/variables/ticket.rst:1 +msgid "``Mustermann`` or empty if not set" msgstr "" -#: ../settings/system/services.rst:26 -msgid "Geo IP Service" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Login" msgstr "" -#: ../settings/system/services.rst:21 -msgid "" -"Defines the backend for geo IP lookups. Shows also location of an IP address " -"if an IP address is shown." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.login}``" msgstr "" -#: ../settings/system/services.rst:24 -msgid "Default: ``Zammad GeoIP Service`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "``agent``" msgstr "" -#: ../settings/system/services.rst:32 -msgid "Geo Location Service" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Mobile" msgstr "" -#: ../settings/system/services.rst:29 -msgid "" -"Defines the backend for geo location lookups to store geo locations for " -"addresses." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.mobile}``" msgstr "" -#: ../settings/system/services.rst:32 -msgid "" -"Default: ``OpenStreetMap (ODbL 1.0, http://osm.org/copyright)`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Note" msgstr "" -#: ../settings/system/services.rst:36 -msgid "" -"You can find a detailed privacy information on what we store for how long on " -"our :docs:`Privacy Appendix ` inside of our System " -"Documentation." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.note}``" msgstr "" -#: ../settings/system/storage.rst:2 -msgid "Storage" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Phone" msgstr "" -#: ../settings/system/storage.rst:6 -msgid "" -"Here you can define where Zammad stores attachments for tickets and the " -"knowledge base. By default, we're writing to the ``Database`` - you can " -"switch to ``Filesystem`` or ``Simple Storage (S3)`` at any time. In this " -"case please have a look on the following instructions." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.phone}``" msgstr "" -#: ../settings/system/storage.rst:11 -msgid "" -"If you have a busy Zammad instance, we strongly encourage you to use " -"filesystem storage instead of \"Database\". This will greatly improve system " -"performance (de-crease database load and size)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > VIP" msgstr "" -#: ../settings/system/storage.rst:19 -msgid "Database" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.vip}``" msgstr "" -#: ../settings/system/storage.rst:17 -msgid "" -"This is the default storage method. The attachments are stored directly in " -"the database. If your Zammad instance grows, we recommend one of the other " -"methods to maintain performance." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Web" msgstr "" -#: ../settings/system/storage.rst:38 -msgid "Filesystem" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.web}``" msgstr "" -#: ../settings/system/storage.rst:22 -msgid "" -"This storage method is recommended for all Zammad instances, especially for " -"those with a higher load. If you choose filesystem, your files are written " -"to ``/opt/zammad/storage/``." +#: ../misc/variables/ticket.rst:1 +msgid "``https://zammad.com`` or empty if not set" msgstr "" -#: ../settings/system/storage.rst:26 -msgid "" -"Moving attachments from \"Database\" to \"Filesystem\" can be run during " -"production use. However, you should consider your framework conditions (e.g. " -"bandwidth, system load in production) to define the right moment." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Pending till" msgstr "" -#: ../settings/system/storage.rst:32 -msgid "**You noticed slow updates of Zammad?**" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.pending_time}``" msgstr "" -#: ../settings/system/storage.rst:34 -msgid "" -"While Zammad is beeing updated, it enforces a recursive \"change " -"owner\" (chown) for this directory. For instances with many files this can " -"be time consuming. To mitigate that you can move your files and create a " -"symlink in ``/opt/zammad/storage/`` to the new directory. Of course you have " -"to make sure on your own that the permissions are always correct." +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not set" msgstr "" -#: ../settings/system/storage.rst:95 -msgid "Simple Storage (S3)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Priority > Name" msgstr "" -#: ../settings/system/storage.rst:41 -msgid "" -"To use the Simple Storage (S3), you have to provide some settings, which " -"can't be accessed in the UI (see instructions below)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.priority.name}``" msgstr "" -#: ../settings/system/storage.rst:44 -msgid "" -"⚠️ Please note that the current implementation is in its early stages and can " -"be modified in the future." +#: ../misc/variables/ticket.rst:1 +msgid "``2 normal``" msgstr "" -#: ../settings/system/storage.rst:47 -msgid "" -"The prerequisite is to have access to a S3-compatible storage and to have " -"all necessary parameters available (which depends on your storage provider; " -"if in doubt, please ask there for help)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > State > Name" msgstr "" -#: ../settings/system/storage.rst:51 -msgid "Steps to configure S3:" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.state.name}``" msgstr "" -#: ../settings/system/storage.rst:53 -msgid "" -"Copy ``config/zammad/storage.yml.dist`` to ``config/zammad/storage.yml``" +#: ../misc/variables/ticket.rst:1 +msgid "``new``, ``open``, ..." msgstr "" -#: ../settings/system/storage.rst:54 -msgid "Edit the copied file in one of the following ways:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Tags" msgstr "" -#: ../settings/system/storage.rst:56 -msgid "" -"Either provide your S3 configuration with one attribute per line like in the " -"upper area of the file" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.tags}``" msgstr "" -#: ../settings/system/storage.rst:58 +#: ../misc/variables/ticket.rst:1 msgid "" -"Or provide your S3 configuration as an URL (which you can find at the end of " -"the file). Note: you can also provide this URL as environment variable (:" -"docs:`see system documentation `) without using this yml-file." +"Currently not available, see `Issue 2769 `_" msgstr "" -#: ../settings/system/storage.rst:62 -msgid "" -"We recommend the deletion of the not used configuration style to avoid " -"inconsistencies." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Title" msgstr "" -#: ../settings/system/storage.rst:65 -msgid "Restart Zammad so the config file / environment variable is loaded" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.title}``" msgstr "" -#: ../settings/system/storage.rst:66 +#: ../misc/variables/ticket.rst:1 msgid "" -"Set the \"Storage Method\" in Zammad to ``Simple Storage (S3)`` in Settings " -"> System > Storage and click on \"Submit\". After that, Zammad checks your " -"configuration and the connection to the service and will raise an error " -"message if something is wrong." +"``My amazing Subject`` (normally subject, can be edited within Interface and " +"thus differ)" msgstr "" -#: ../settings/system/storage.rst:72 -msgid "A very simple storage configuration could look like this:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated at" msgstr "" -#: ../settings/system/storage.rst:85 -msgid "" -"Before setting the storage method to ``Simple Storage (S3)`` (step 4), " -"please make sure to have a working setup." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_at}``" msgstr "" -#: ../settings/system/storage.rst:88 -msgid "" -"You can verify this by running ``rails r 'Rails.logger = Logger.new(STDOUT); " -"pp Store::Provider::S3.ping?'`` in your Zammad directory. If everything is " -"fine, you should see ``true``, else you should see ``false`` and a simple " -"error message." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Address" msgstr "" -#: ../settings/system/storage.rst:93 -msgid "" -"If you installed Zammad through a package manager (rather than from source), " -"replace ``rails r`` with ``zammad run rails r`` above. To learn more, see :" -"docs:`Administration via Console `." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.address}``" msgstr "" -#: ../settings/ticket.rst:4 -msgid "" -"Here you can adjust general ticket settings. Additional ones for the ticket " -"composer interface can be found in the :doc:`/misc/composer`." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Avatar" msgstr "" -#: ../settings/ticket.rst:11 -msgid "Ticket Hook (default: ``Ticket#``)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.avatar(60,60)}``" msgstr "" -#: ../settings/ticket.rst:11 -msgid "The identifier for a ticket; *e.g.,* Ticket#, Call#, MyTicket#." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Department" msgstr "" -#: ../settings/ticket.rst:38 -msgid "Ticket Hook Position (default: ``right``)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.department}``" msgstr "" -#: ../settings/ticket.rst:14 -msgid "" -"With this setting you can decide (if) where to insert the ticket number." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Email" msgstr "" -#: ../settings/ticket.rst:20 -msgid "*Right*" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.email}``" msgstr "" -#: ../settings/ticket.rst:17 -msgid "" -"This setting will add the ticket reference on the right site of the subject." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Fax" msgstr "" -#: ../settings/ticket.rst:20 -msgid "Example: ``Some Subject [Ticket#12345]``" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.fax}``" msgstr "" -#: ../settings/ticket.rst:26 -msgid "*Left*" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Firstname" msgstr "" -#: ../settings/ticket.rst:23 -msgid "" -"This setting will add the ticket reference on the left site of the subject." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.firstname}``" msgstr "" -#: ../settings/ticket.rst:26 -msgid "Example: ``[Ticket#12345] Some Subject``" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Lastname" msgstr "" -#: ../settings/ticket.rst:29 -msgid "*None*" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.lastname}``" msgstr "" -#: ../settings/ticket.rst:29 -msgid "This will completely remove ticket references from the subject." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Login" msgstr "" -#: ../settings/ticket.rst:33 -msgid "" -"Please ensure to take a look at :doc:`/channels/email/settings` within the " -"email channel to ensure you have at least one reference that helps Zammad to " -"assign follow-ups correctly." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.login}``" msgstr "" -#: ../settings/ticket.rst:37 -msgid "" -"Disabling this and not setting up any further follow up search will lead to " -"unexpected results!" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Mobile" msgstr "" -#: ../settings/ticket.rst:65 -msgid "" -"Ticket Last Contact Behaviour (default: ``Use the start time of the last " -"customer thread (which may consist of multiple articles).``)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.mobile}``" msgstr "" -#: ../settings/ticket.rst:41 -msgid "" -"This setting changes the way Zammad updates the ``Last Contact`` value of a " -"ticket. This is fairly important for overviews and what you expect upon " -"ticket updates of a customer." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Note" msgstr "" -#: ../settings/ticket.rst:52 -msgid "" -"Use the start time of the last customer thread (which may consist of " -"multiple articles)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.note}``" msgstr "" -#: ../settings/ticket.rst:46 -msgid "" -"If this option is chosen, Zammad will update the last updated value just " -"once if a customer replies. After that, Zammad will wait for an agent to " -"react." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Phone" msgstr "" -#: ../settings/ticket.rst:50 -msgid "" -"This comes in handy if you want to work tickets in the order of their first " -"update. This will not change ticket orders if customers decide to \"bump\" " -"the ticket affected." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.phone}``" msgstr "" -#: ../settings/ticket.rst:57 -msgid "Use the time of the very last customer article." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > VIP" msgstr "" -#: ../settings/ticket.rst:55 -msgid "" -"When setting this option, Zammad will always update the last updated value. " -"This means that if ordering by ``Last Update``, ticket orders will change if " -"customers \"bump\" the ticket." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.vip}``" msgstr "" -#: ../settings/ticket.rst:64 -msgid "Last contact value used on :doc:`/manage/overviews`" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Web" msgstr "" -#: ../settings/ticket.rst:65 -msgid "Last contact value used on :doc:`/manage/trigger`" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.web}``" msgstr "" -#: ../settings/ticket.rst:88 -msgid "" -"Ticket Organization Reassignment (default: ``Update the most recent tickets." -"``)" +#: ../settings/branding.rst:10 +msgid "Product Name" msgstr "" -#: ../settings/ticket.rst:68 +#: ../settings/branding.rst:7 msgid "" -"This setting changes the way Zammad updates the organization field of the " -"tickets whenever the primary organization of a user is changed." -msgstr "" - -#: ../settings/ticket.rst:74 -msgid "Update the most recent tickets." +"Defines the name of the application, shown in the web interface, tabs and " +"title bar of the web browser." msgstr "" -#: ../settings/ticket.rst:72 -msgid "" -"If this option is chosen, Zammad will update the 100 most recent tickets " -"where the user is the ticket customer. The ticket organization field will be " -"automatically set to the new primary organization of the user." +#: ../settings/branding.rst:10 +msgid "Default value: ``Zammad Helpdesk``" msgstr "" -#: ../settings/ticket.rst:88 -msgid "Do not update any tickets." +#: ../settings/branding.rst:13 +msgid "Will be shown in the app and is included in email footers." msgstr "" -#: ../settings/ticket.rst:77 -msgid "" -"When choosing this option, Zammad will not update any tickets when the " -"user's primary organization is changed." +#: ../settings/branding.rst:19 +msgid "Logo" msgstr "" -#: ../settings/ticket.rst:80 -msgid "**Use with care!**" +#: ../settings/branding.rst:16 +msgid "Defines the logo of the application, shown in the login page of Zammad." msgstr "" -#: ../settings/ticket.rst:82 +#: ../settings/branding.rst:18 msgid "" -"Using this option may lead to inconsistencies in the system as the ticket " -"organization may become decoupled from the ticket customer." +"Ensure to hit the \"Submit\" button after uploading the logo. Otherwise your " +"change will not be saved." msgstr "" -#: ../settings/ticket.rst:85 +#: ../settings/branding.rst:22 msgid "" -"However, you may use this option if you wish to maintain :ref:`the shared " -"access ` to the ticket for all organization " -"members of the original organization of the customer." +"Allows to set the default language of the Zammad instance. The here defined " +"locale mostly acts as a fallback for:" msgstr "" -#: ../settings/ticket.rst:110 -msgid "Ticket Number Format (default: ``Increment (SystemID.Counter)``)" +#: ../settings/branding.rst:25 +msgid "user preferences (if Zammad can't detect the users locale)" msgstr "" -#: ../settings/ticket.rst:94 -msgid "" -"This setting defines the way Zammad's ticket number will look. Changing this " -"setting in production will cause follow up detection to fail." +#: ../settings/branding.rst:26 +msgid "CSV output (reporting, time accounting)" msgstr "" -#: ../settings/ticket.rst:102 -msgid "Increment (SystemID.Counter)" +#: ../settings/branding.rst:30 +msgid "Define the timezone of your Zammad installation." msgstr "" -#: ../settings/ticket.rst:98 +#: ../settings/branding.rst:32 msgid "" -"The increment value contains the SystemID (automatically generated during " -"installation) and a increment which counts up with every new Ticket. The " -"increment will automatically get another digit if needed." +"This does not have any effect on timings for your agents or how Zammad " +"stores date and time values." msgstr "" -#: ../settings/ticket.rst:102 -msgid "Examples: ``1010138``, ``1010139``" +#: ../settings/branding.rst:35 +msgid "Changing this value has direct consequences on the following areas:" msgstr "" -#: ../settings/ticket.rst:110 -msgid "Date (Year.Month.Day.SystemID.Counter)" +#: ../settings/branding.rst:37 +msgid ":doc:`/manage/scheduler` tasks" msgstr "" -#: ../settings/ticket.rst:105 -msgid "" -"This version of the ticket number is fairly long. However, because it " -"contains the date of ticket creation, it also allows you to see when the " -"ticket has been created. You may feel familiar with this number format if " -"you've worked with OTRS already." +#: ../settings/branding.rst:38 +msgid "search indexing (and thus reporting)" msgstr "" -#: ../settings/ticket.rst:110 -msgid "Examples: ``201206231010138``, ``201206231010139``" +#: ../settings/branding.rst:40 +msgid "calendar subscriptions" msgstr "" -#: ../settings/ticket.rst:137 -msgid "OPTIONS" +#: ../settings/branding.rst:41 +msgid "browser printing" msgstr "" -#: ../settings/ticket.rst:113 +#: ../settings/branding.rst:43 msgid "" -"The below options allow you to further customize your ticket number. The " -"availability of options differ depending of the chosen ticket number format " -"above." +"Please note that some of above are fallbacks in case Zammad could not detect " +"the agents timezone correctly." msgstr "" -#: ../settings/ticket.rst:122 -msgid "Checksum (default: ``no``)" +#: ../settings/branding.rst:77 +msgid "Pretty Date" msgstr "" -#: ../settings/ticket.rst:118 +#: ../settings/branding.rst:47 msgid "" -"If set to yes, we'll built a checksum to further \"unique\" the ticket " -"number of your system. If you're dealing with many other ticket systems this " -"might help to prevent false positive follow up detection on tickets." +"This setting allows you to define how Zammad should display time stamps " +"within the interface to all users." msgstr "" -#: ../settings/ticket.rst:122 -msgid "This will also add another digit to the ticket number." +#: ../settings/branding.rst:50 +msgid "" +"This does not have any effect on how Zammad returns e.g. time values via " +"variables." msgstr "" -#: ../settings/ticket.rst:137 -msgid "Min. size of Number (default: ``5``)" +#: ../settings/branding.rst:77 +msgid "Choose in between the following options:" msgstr "" -#: ../settings/ticket.rst:125 -msgid "" -"This setting defines the minimum length of your ticket number. If your " -"counter is not yet high enough, Zammad will fill the number with zeros to " -"ensure the wanted length." +#: ../settings/branding.rst:64 +msgid "relative" msgstr "" -#: ../settings/ticket.rst:129 +#: ../settings/branding.rst:55 msgid "" -"Please note that the minimum length is ``3`` (SystemID + at least one digit " -"if below 10). Also, if the length is no longer long enough, the number will " -"automatically get one digit longer. Ticket-Numbers **do not overflow**, thus " -"it's save to keep it at 5 or set it lower if wanted." +"This timestamp shows a relative time span until it switches to a date. Over " +"time, it will change as follows:" msgstr "" -#: ../settings/ticket.rst:135 -msgid "" -"This option is only available if ticket number format is set to " -"``Increment``!" +#: ../settings/branding.rst:58 +msgid "just now" msgstr "" -#: ../settings/ticket.rst:142 -msgid "Auto-Assignment" +#: ../settings/branding.rst:59 +msgid "5 minutes ago" msgstr "" -#: ../settings/ticket.rst:144 -msgid "" -"In a larger Zammad environment, it happens that several agents open the same " -"ticket at the same time. Although collision detection is then effective, the " -"efficiency of processing can be increased by means of the automatic " -"assignment of tickets when a ticket is opened." +#: ../settings/branding.rst:60 +msgid "3 days 1 hour ago" msgstr "" -#: ../settings/ticket.rst:149 -msgid "" -"The automatic assignment of tickets can be activated and configured in the " -"admin area under Settings > Ticket > Auto Assignment." +#: ../settings/branding.rst:61 +msgid "``03/04/2022``" msgstr "" -#: ../settings/ticket.rst:152 -msgid "" -"The auto assignment only works if the ticket has no owner yet. By default, " -"the agent can always reset the ticket owner to ``-`` if needed." +#: ../settings/branding.rst:63 +msgid "Hovering the timestamp helps, you'll always get a clean timestamp then." msgstr "" -#: ../settings/ticket.rst:155 -msgid "" -"If you want to use this function for only specific tickets, you can " -"configure the conditions accordingly to meet your requirement. By default " -"the condition affects all tickets with the state ``open``." +#: ../settings/branding.rst:71 +msgid "absolute" msgstr "" -#: ../settings/ticket.rst:161 +#: ../settings/branding.rst:67 msgid "" -"If you need to exclude users (e.g. a group leader), you can search and " -"select the desired agents in the ``Exception Users`` list. The search " -"function in this area is only effective, if you have too many agents to " -"display at once to help you with the configuration." +"This timestamp always includes the week day. For one week after creation, " +"the timestamp will not contain the date itself: Thursday 18:35." msgstr "" -#: ../settings/ticket.rst:167 -msgid "Notifications" +#: ../settings/branding.rst:71 +msgid "After a week it will switch to: ``Friday 4. Mar 16:00``." msgstr "" -#: ../settings/ticket.rst:191 -msgid "Default Notifications" +#: ../settings/branding.rst:76 +msgid "timestamp" msgstr "" -#: ../settings/ticket.rst:170 +#: ../settings/branding.rst:74 msgid "" -"This setting allows you to configure the default ticket notifications that " -"will be applied to all new agent users (incl. users who were just assigned " -"agent role). Simply change the notification matrix to desired state and " -"press **Save**." +"This will cause Zammad to show a complete timestamp according to your locale " +"defaults. For English this could be e.g. ``2022/12/03 2:40 pm`` or for " +"German e.g. ``12.03.2022 14:40``." msgstr "" -#: ../settings/ticket.rst:175 -msgid "" -"In case an agent already exists, their ticket notification preferences will " -"be preserved. Optionally, you can also **Apply current defaults to all " -"agents**." +#: ../settings/branding.rst:78 +msgid "Default setting: ``relative``." msgstr "" -#: ../settings/ticket.rst:181 -msgid "" -"**Potential time-consuming action:** Applying default ticket notifications " -"to all agent users may take some time to complete, be patient! The exact " -"time will depend on the size of your system and the number of agents." +#: ../settings/security.rst:2 +msgid "Security" msgstr "" -#: ../settings/ticket.rst:185 +#: ../settings/security.rst:4 msgid "" -"**Active agents only!** When current default ticket notifications are " -"applied, only active agent users are considered. In case an agent is re-" -"activated *after* this action, they will still have the old notification " -"configuration." +"For your overview we split each tab within security settings into its own " +"page:" msgstr "" -#: ../settings/ticket.rst:190 +#: ../settings/security/base.rst:2 ../settings/system/base.rst:2 +#: ../settings/ticket.rst:8 +msgid "Base" +msgstr "" + +#: ../settings/security/base.rst:5 +msgid "New User Accounts" +msgstr "" + +#: ../settings/security/base.rst:9 msgid "" -"In case you want to go back to the initial state of ticket notifications, " -"you can click on **Reset to default** button." +"Activates the `register as a new customer` function on the login page. If " +"set to ``no`` only administrators or agents can create new accounts manually." msgstr "" -#: ../settings/ticket.rst:194 ../settings/ticket.rst:196 -msgid "Duplicate Detection" +#: ../settings/security/base.rst:13 ../settings/security/base.rst:38 +#: ../settings/security/base.rst:66 +msgid "Default setting: ``yes``" msgstr "" -#: ../settings/ticket.rst:236 ../settings/ticket.rst:238 -msgid "Detect Duplicate Ticket Creation" +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"New User Accounts\" setting" msgstr "" -#: ../settings/ticket.rst:197 ../settings/ticket.rst:199 +#: ../settings/security/base.rst:22 msgid "" -"This setting turns on the duplicate ticket detection mechanism during ticket " -"creation. If similar tickets are found in the system, a suitable warning " -"will be shown to the user trying to create a ticket." +"Deactivation of above function **does not** deactivate automatic account " +"creation! This means: If a user writes e.g. an email to Zammad and has no " +"account yet, Zammad will automatically create the account. User accounts are " +"a direct dependency of tickets and thus technically mandatory." msgstr "" -#: ../settings/ticket.rst:204 ../settings/ticket.rst:206 -msgid "A Sample Duplicate Ticket Warning" +#: ../settings/security/base.rst:29 +msgid "Lost Password" msgstr "" -#: ../settings/ticket.rst:206 ../settings/ticket.rst:208 +#: ../settings/security/base.rst:33 msgid "" -"You can choose which ticket attributes will be matched by selecting them in " -"**Attributes to compare** field. Only if the ticket attribute value provided " -"by the user in the ticket create form is *equal* with the attribute in an " -"existing ticket, the warning will be shown." +"Activates the `lost password` function on the login page. If set to ``no`` " +"only administrators may change the user's password - users may update their " +"own password if they're still logged in and they have the required :doc:" +"`permission `." msgstr "" -#: ../settings/ticket.rst:211 ../settings/ticket.rst:213 -msgid "**Warning title** and **Warning message** are configurable as well." +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"Lost Password\" setting" msgstr "" -#: ../settings/ticket.rst:213 ../settings/ticket.rst:215 +#: ../settings/security/base.rst:49 msgid "" -"You can limit the detection only to certain user roles. By default, only " -"agents will see the warning." +"With third party authentications - but especially LDAP - you may want to " +"disable this function. Zammad **will not** change third party login " +"passwords and instead set or change the local password!" msgstr "" -#: ../settings/ticket.rst:216 ../settings/ticket.rst:218 -msgid "" -"If you don't want to show the matched tickets as part of the warning, you " -"can set **Show matching ticket(s) in the warning** setting to *no*." +#: ../settings/security/base.rst:56 +msgid "Password Login" msgstr "" -#: ../settings/ticket.rst:219 ../settings/ticket.rst:221 +#: ../settings/security/base.rst:60 msgid "" -"By default, **Permission level for looking up ticket** is set to *User*, " -"which means user permissions will be honored during sarch. The user will " -"see the warning only if tickets they have access to are matched. " -"Alternatively, you can set this setting to *System*, in which case the " -"search will happen within *all* tickets in the system, regardless of user " -"permissions." +"Activates the username & password login by default and if no third-party " +"login is activated. Disabling password login on the Zammad login page only " +"takes effect if you enable any :doc:`third-party`." msgstr "" -#: ../settings/ticket.rst:225 ../settings/ticket.rst:227 -msgid "**🦺 Safety first!**" +#: ../settings/security/base.rst:64 +msgid "See :doc:`third-party` for supported third-party logins." msgstr "" -#: ../settings/ticket.rst:227 ../settings/ticket.rst:229 -msgid "" -"Even if the permission level is set to *System*, the user will not be shown " -"the tickets they don't have access to in the warning, even if they match." +#: ../settings/security/base.rst:0 +msgid "Figure showing de-activated \"Password Login\" setting" msgstr "" -#: ../settings/ticket.rst:231 ../settings/ticket.rst:233 +#: ../settings/security/base.rst:77 msgid "" -"However, just the confirmation about the existence of the tickets in the " -"system may be considered an unwanted information disclosure. Use this option " -"carefully!" +"To help administrators to overcome \"login issues\", Zammad automatically " +"offers a password request for administrator users. This allows you to adjust " +"Third-Party applications even if the login does no longer work!" msgstr "" -#: ../settings/ticket.rst:235 ../settings/ticket.rst:237 -msgid "" -"Finally, you can configure between matching within **All tickets** or **Open " -"tickets** only by setting **Match tickets in following states**. Depending " -"on the current ticket state, a ticket may or not be matched." +#: ../settings/security/base.rst:84 +msgid "Session Timeout" msgstr "" -#: ../system/core-workflows.rst:2 -msgid "Core Workflows" +#: ../settings/security/base.rst:86 +msgid "" +"All settings below by default are set to ``4 weeks``. Session Timeout " +"defines the life time of a users session. As soon as it's reached, Zammad " +"will automatically log off the session in question." msgstr "" -#: ../system/core-workflows.rst:4 +#: ../settings/security/base.rst:91 msgid "" -"Core Workflows allow you to adjust object attributes in many ways. For " -"example:" +"Zammad takes the highest value set assigned for the user based on the " +"permissions." msgstr "" -#: ../system/core-workflows.rst:7 -msgid "show / hide fields" +#: ../settings/security/base.rst:94 +msgid "``admin``" msgstr "" -#: ../system/core-workflows.rst:8 -msgid "adjust mandatory setting" +#: ../settings/security/base.rst:96 +msgid "``ticket.customer``" msgstr "" -#: ../system/core-workflows.rst:9 -msgid "manipulate available options" +#: ../settings/security/base.rst:97 +msgid "``default`` (fallback if user doesn't have above permissions set)" msgstr "" -#: ../system/core-workflows.rst:11 +#: ../settings/security/base.rst:99 msgid "" -"With this, you can provide exactly the information your users really need!" +"All settings act independently from each other allowing you to disable the " +"timeouts for e.g. admins, but not agents." msgstr "" -#: ../system/core-workflows.rst:15 -msgid "" -"If the pre-defined :doc:`/system/objects` are not enough, please add them " -"beforehand." +#: ../settings/security/base.rst:115 +#: ../system/integrations/checkmk/api-reference.rst:13 +msgid "Example" msgstr "" -#: ../system/core-workflows.rst:17 -msgid "" -"If you experience slow or unreliable field updates, please see :ref:`Core " -"Workflow Ajax Modus `" +#: ../settings/security/base.rst:107 +msgid "Let's suppose you configured the following session timeouts" msgstr "" -#: ../system/core-workflows.rst:22 -msgid "" -"This is a very enhanced functionality and can cause unexpected UI behavior. " -"Please ensure to test your use cases after configuration to reduce surprises." +#: ../settings/security/base.rst:104 +msgid "default: 3 weeks" msgstr "" -#: ../system/core-workflows.rst:None -msgid "Dialogue for adding a new workflow" +#: ../settings/security/base.rst:105 +msgid "admin: 2 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:2 -msgid "Core Workflow Condition Operators" +#: ../settings/security/base.rst:106 +msgid "ticket.agent: 4 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:4 -msgid "" -"You might know that there is a separate section for explaining :doc:" -"`condition operators `. Head over there to " -"see a detailed explanation of many conditions and operators." +#: ../settings/security/base.rst:107 +msgid "ticket.customer: 1 week" msgstr "" -#: ../system/core-workflows/condition-operators.rst:8 -msgid "" -"Due to differences to other places in Zammad which are also using conditions " -"(e.g. triggers), you can find a dedicated description of operators for core " -"workflows below." +#: ../settings/security/base.rst:115 +msgid "This results in the following situations" msgstr "" -#: ../system/core-workflows/condition-operators.rst:12 -msgid "" -"Be aware that the availability of the operators depends on the selected " -"attribute and its field type. Some of the operators may only be available " -"for system attributes (e.g. for \"tags\", \"active\")." +#: ../settings/security/base.rst:110 +msgid "a user with ``admin`` permission will have a timeout of 2 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:20 -msgid "Operator" +#: ../settings/security/base.rst:111 +msgid "" +"a user with ``admin`` and ``ticket.agent`` permissions will have a timeout " +"of 2 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:22 -msgid "after (absolute)" +#: ../settings/security/base.rst:113 +msgid "" +"a user with ``ticket.customer`` permission will have a timeout of 1 week" msgstr "" -#: ../system/core-workflows/condition-operators.rst:23 -msgid "Matches if a date/time is after a specific point in time." +#: ../settings/security/base.rst:115 +msgid "" +"a user with neither ``admin``, ``ticket.agent`` nor ``ticket.customer`` " +"permissions will have a timeout of 3 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:24 -msgid "after (relative)" +#: ../settings/security/password.rst:4 +msgid "" +"This section allows you to define password requirements for the local user " +"accounts." msgstr "" -#: ../system/core-workflows/condition-operators.rst:25 -msgid "Matches if a time span after a specified event has passed." +#: ../settings/security/password.rst:9 +msgid "" +"Zammad does **not** allow you to change your LDAP password, instead, it will " +"set a password in its local database which might confuse your users. This " +"might be addressed in the future by `#1169 `_." msgstr "" -#: ../system/core-workflows/condition-operators.rst:26 -msgid "before (absolute)" +#: ../settings/security/password.rst:14 +msgid "**Exception for admins**" msgstr "" -#: ../system/core-workflows/condition-operators.rst:27 -msgid "Matches if a date/time is before a specific point in time." +#: ../settings/security/password.rst:16 +msgid "" +"Please note that below password policies *do not* affect administrators " +"setting passwords on user accounts. While this seems strange and not safe we " +"believe that an administrator knowing an user's password is insecure as well." msgstr "" -#: ../system/core-workflows/condition-operators.rst:28 -msgid "before (relative)" +#: ../settings/security/password.rst:21 +msgid "The suggested workflow is either:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:29 -msgid "Matches if a time span after a specified event has not passed." +#: ../settings/security/password.rst:23 +msgid "" +"to use third party logins to not require local passwords at all **- or -**" msgstr "" -#: ../system/core-workflows/condition-operators.rst:30 -msgid "contains" +#: ../settings/security/password.rst:25 +msgid "to require your *user to reset the password* upon first login." msgstr "" -#: ../system/core-workflows/condition-operators.rst:31 -msgid "Matches if a specified value is present." +#: ../settings/security/password.rst:27 +msgid "" +"This way administrators are not required to set a user's password at all!" msgstr "" -#: ../system/core-workflows/condition-operators.rst:33 -msgid "Matches if all of the specified values are present." +#: ../settings/security/password.rst:31 +msgid "Maximum Failed Logins" msgstr "" -#: ../system/core-workflows/condition-operators.rst:35 -msgid "Matches if none of the specified values are present." +#: ../settings/security/password.rst:33 +msgid "" +"You can choose a value between ``4`` and ``20``. This defines how often a " +"login to a user account may fail until Zammad will lock it. Your users can " +"always use the \"forgot password\" function to change their password and " +"unlock their account." msgstr "" -#: ../system/core-workflows/condition-operators.rst:36 -msgid "contains not" +#: ../settings/security/password.rst:38 +msgid "The default value is ``10``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:37 -msgid "Matches if a specified value is not present." +#: ../settings/security/password.rst:42 +msgid "Beside changing the user's password, you can also unlock accounts via" msgstr "" -#: ../system/core-workflows/condition-operators.rst:39 -msgid "Matches if one specified value is present." +#: ../settings/security/password.rst:44 +msgid ":ref:`user management list `" msgstr "" -#: ../system/core-workflows/condition-operators.rst:41 -msgid "Matches if one specified value is not present." +#: ../settings/security/password.rst:45 +msgid ":docs:`console `" msgstr "" -#: ../system/core-workflows/condition-operators.rst:42 -msgid "does not match regex" +#: ../settings/security/password.rst:46 +msgid ":docs:`API `" msgstr "" -#: ../system/core-workflows/condition-operators.rst:43 -msgid "Matches if content doesn't fit to regex rule." +#: ../settings/security/password.rst:50 +msgid "Failed logins via LDAP no longer lock accounts." msgstr "" -#: ../system/core-workflows/condition-operators.rst:44 -msgid "ends with" +#: ../settings/security/password.rst:53 +msgid "2 Lower Case And 2 Upper Case Characters" msgstr "" -#: ../system/core-workflows/condition-operators.rst:45 -msgid "Matches if content ends with specified value." +#: ../settings/security/password.rst:55 +msgid "" +"You can add complexity to passwords by enforcing at least 2 upper and lower " +"case characters." msgstr "" -#: ../system/core-workflows/condition-operators.rst:46 -msgid "ends with one of" +#: ../settings/security/password.rst:58 ../settings/security/password.rst:83 +msgid "The default value is ``no``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:47 -msgid "Matches if content ends with one of the specified values." +#: ../settings/security/password.rst:62 +msgid "Minimum Length" msgstr "" -#: ../system/core-workflows/condition-operators.rst:48 -msgid "from (relative)" +#: ../settings/security/password.rst:64 +msgid "" +"This defines the minimum password length required for users to provide (from " +"``4`` to ``20``)." msgstr "" -#: ../system/core-workflows/condition-operators.rst:49 -msgid "Matches if date/time is after a period of time after an event." +#: ../settings/security/password.rst:67 +msgid "The default value is ``6``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:51 -msgid "Matches if content is equal to a specified value." +#: ../settings/security/password.rst:71 +msgid "Digit Required" msgstr "" -#: ../system/core-workflows/condition-operators.rst:52 -msgid "is any of" +#: ../settings/security/password.rst:73 +msgid "This enforces your users to use at least one digit within the password." msgstr "" -#: ../system/core-workflows/condition-operators.rst:53 -msgid "Matches if content is equal to any of specified values." +#: ../settings/security/password.rst:75 +msgid "The default value is ``yes``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:54 -msgid "is modified" +#: ../settings/security/password.rst:78 +msgid "Special Character Required" msgstr "" -#: ../system/core-workflows/condition-operators.rst:55 -msgid "Matches if content is modified." +#: ../settings/security/password.rst:80 +msgid "" +"This setting allows you to improve your password quality even more by " +"enforcing the password to contain at least one special character." msgstr "" -#: ../system/core-workflows/condition-operators.rst:57 -#: ../system/core-workflows/condition-operators.rst:61 -msgid "True from the moment of changing content until form submit." +#: ../settings/security/ssl-certificates.rst:2 +msgid "SSL Certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:58 -msgid "is modified to" +#: ../settings/security/ssl-certificates.rst:7 +msgid "" +"Zammad offers the possibility to upload custom certificates and custom " +"Certificate Authority (CA) certificates. This can be useful if you want to " +"connect Zammad the secure way to other systems which are using custom " +"certificates." msgstr "" -#: ../system/core-workflows/condition-operators.rst:59 -msgid "Matches if content is modified to a specific value." +#: ../settings/security/ssl-certificates.rst:12 +msgid "" +"An example usecase might be: You have an internal LDAP server that is not " +"accessible from the internet, and you want a SSL-encrypted connection, using " +"a custom certificate." msgstr "" -#: ../system/core-workflows/condition-operators.rst:62 -msgid "is none of" +#: ../settings/security/ssl-certificates.rst:19 +msgid "" +"You should have an existing custom certificate file and/or a custom CA " +"certificate file, which you want to add to Zammad. As filetype ``.crt`` is " +"supported and the certificate format has to be PEM (Base64 ASCII)." msgstr "" -#: ../system/core-workflows/condition-operators.rst:63 -msgid "Matches if content is none of any specified values." +#: ../settings/security/ssl-certificates.rst:25 +msgid "" +"When you import a custom CA certificate, all certificates generated with " +"this are trusted. This can be useful if you have more than one system/" +"certificate you want to connect to and the certificates are issued from the " +"same custom CA." msgstr "" -#: ../system/core-workflows/condition-operators.rst:65 -msgid "Matches if content is not equal to a specified value." +#: ../settings/security/ssl-certificates.rst:31 +msgid "Add a Certificate" msgstr "" -#: ../system/core-workflows/condition-operators.rst:67 -msgid "Matches if content is present." +#: ../settings/security/ssl-certificates.rst:33 +msgid "" +"To add a custom certificate or a custom CA certificate, head over to the " +"Admin panel > Settings > Security > SSL Certificates. Here you can find a " +"\"Add SSL Certificate\" button. In the dialog you can either select a " +"certificate file or paste the content of the certificate:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:68 -msgid "just changed" +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate adding dialog" msgstr "" -#: ../system/core-workflows/condition-operators.rst:69 -msgid "Matches if content has changed." +#: ../settings/security/ssl-certificates.rst:43 +msgid "" +"After selecting a file or pasting the content of the certificate, click on " +"the \"Add\" button to finally upload it to Zammad. Then, the certificates " +"are immediately effective, no restart or similar required." msgstr "" -#: ../system/core-workflows/condition-operators.rst:71 -#: ../system/core-workflows/condition-operators.rst:75 +#: ../settings/security/ssl-certificates.rst:49 msgid "" -"Only true for the moment of changing content until next form field action/" -"click." +"Please note that only single certificate files are supported. That means if " +"you want to import a certificate / CA certificate, it must contain **only " +"one** certificate." msgstr "" -#: ../system/core-workflows/condition-operators.rst:72 -msgid "just changed to" +#: ../settings/security/ssl-certificates.rst:54 +msgid "Certificate Overview" msgstr "" -#: ../system/core-workflows/condition-operators.rst:73 -msgid "Matches if content has changed to a specified value." +#: ../settings/security/ssl-certificates.rst:56 +msgid "" +"After you added a certificate, you can see a table with information for each " +"added certificate:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:76 -msgid "matches regex" +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing table of added certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:77 -msgid "Matches if value fits to regex rule." -msgstr "" - -#: ../system/core-workflows/condition-operators.rst:79 -msgid "Matches if no content is present." -msgstr "" - -#: ../system/core-workflows/condition-operators.rst:80 -msgid "starts with" +#: ../settings/security/ssl-certificates.rst:64 +msgid "" +"Here you can download the certificate or delete it, if you don't need it " +"anymore." msgstr "" -#: ../system/core-workflows/condition-operators.rst:81 -msgid "Matches if content starts with specified value." +#: ../settings/security/ssl-certificates.rst:68 +msgid "Deleting Certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:82 -msgid "starts with one of" +#: ../settings/security/ssl-certificates.rst:70 +msgid "" +"If you want to delete a specific certificate, you can do it by clicking on " +"the menu in the actions column and selecting delete:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:83 -msgid "Matches if content starts with one of the specified values." +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate deletion button" msgstr "" -#: ../system/core-workflows/condition-operators.rst:84 -msgid "till (relative)" +#: ../settings/security/ssl-certificates.rst:79 +msgid "Downloading Certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:85 -msgid "Matches if date/time is before a period of time before an event." +#: ../settings/security/ssl-certificates.rst:81 +msgid "" +"If you want to download your certificates, you can do this as well via " +"corresponding action buttons." msgstr "" -#: ../system/core-workflows/condition-operators.rst:86 -msgid "today" +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate download button" msgstr "" -#: ../system/core-workflows/condition-operators.rst:87 -msgid "Matches if date/time is today." +#: ../settings/security/third-party.rst:13 +msgid "Login Providers" msgstr "" -#: ../system/core-workflows/condition-operators.rst:88 -msgid "within last (relative)" +#: ../settings/security/third-party.rst:2 +msgid "Third-Party Applications" msgstr "" -#: ../system/core-workflows/condition-operators.rst:89 +#: ../settings/security/third-party.rst:4 msgid "" -"Matches if date/time content is within specified period of time before now." +"Third party authentication is a great way to help your users to login to " +"Zammad more easily. If the account is yet unknown, Zammad will create a new " +"user automatically, without the user needed to interact (e.g. type in his " +"name). Another big advantage of this feature is that your user doesn't need " +"to remember another password." msgstr "" -#: ../system/core-workflows/condition-operators.rst:91 -msgid "within next (relative)" +#: ../settings/security/third-party.rst:10 +msgid "" +"You can deactivate logging in via :ref:`security_password_login` if any of " +"the mentioned authentication providers are enabled in your instance." msgstr "" -#: ../system/core-workflows/condition-operators.rst:92 +#: ../settings/security/third-party.rst:27 msgid "" -"Matches if date/time content is within specified period of time after now." +"We're currently missing documentation for the following login providers:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:2 -msgid "How do they work?" +#: ../settings/security/third-party.rst:29 +msgid "LinkedIn" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:4 -msgid "" -"Core Workflows are executed according to their priority. If two workflows " -"have the same priority, they are executed in alphabetical order based on " -"their **name**." +#: ../settings/security/third-party.rst:30 +msgid "Weibo" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:8 -msgid "" -"Because of the way Core Workflows work, all changes to attributes are " -"checked with the application server - please see :doc:`limitations` for " -"possible issues." +#: ../settings/security/third-party.rst:35 +msgid "Automatic Account Link on Initial Logon" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:12 +#: ../settings/security/third-party.rst:37 msgid "" -"Below we're talking about settings that are important and not self-" -"explanatory." +"In general there's two possible options for Zammad on how to deal with " +"already known users as they try to authenticate against a third-party " +"application. By default, Zammad will not automatically link \"unknown\" " +"authentication providers to existing accounts." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:17 +#: ../settings/security/third-party.rst:42 msgid "" -"Choose the object context you want to run the workflow in. This will decide " -"on your available attributes and actions." -msgstr "" - -#: ../system/core-workflows/how-do-they-work.rst:20 -msgid "Ticket objects also have access to the ticket customer." +"This means that the user has to manually link authentication providers to " +"their accounts (for more about this :user-docs:`consult the user " +"documentation `)." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:25 +#: ../settings/security/third-party.rst:46 msgid "" -"Choose in which situation the workflow is applied. Contexts can be combined " -"to avoid duplicate workflows." +"Sometimes this doesn't come in handy as this also means you'll receive error " +"messages about \"email address being in use already\" for (yet) unknown " +"third-party authentication methods." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:30 -msgid "Creation mask" +#: ../settings/security/third-party.rst:50 +msgid "" +"If you want to allow your users to always be able to log in, no matter what, " +"you may want to enable ``Automatic account link on initial logon``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:29 +#: ../settings/security/third-party.rst:None msgid "" -"If selected, your conditions and actions will affect all applicable creation " -"masks." +"Screenshot highlighting the \"Automatic account link on initial logon\"\n" +"setting" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:34 -msgid "Edit mask" +#: ../settings/security/third-party.rst:60 +msgid "Automatic Account Linking Notification" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:33 +#: ../settings/security/third-party.rst:64 msgid "" -"If selected, your conditions and actions will affect all applicable edit " -"masks." +"To improve security and your users awareness, you can enable Zammad to " +"notify your users when a new third-party application has been linked to " +"their account." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:39 +#: ../settings/security/third-party.rst:68 msgid "" -"Zammad differentiates between selected and saved conditions. These can be " -"combined wherever needed." +"This notification is sent out once per third-party application. Zammad does " +"also mention the method used, e.g.: ``Microsoft``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:42 -msgid "**⚠️ Restrict workflows to specific roles if needed!**" +#: ../settings/security/third-party.rst:71 +msgid "By default this setting is not active (set to ``no``)." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:44 +#: ../settings/security/third-party.rst:0 msgid "" -"By default and unless configured in conditions, workflow rules are executed " -"for **all roles**. This also affects your customers!" +"Screenshot showing sample notification mail after initial\n" +"third-party linking" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:50 -msgid "Selected Conditions" +#: ../settings/security/third-party.rst:85 +msgid "" +"This notification is only sent if the account in question already exists. If " +"the login via the third-party also creates the missing account, the " +"notification will be skipped." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:48 -msgid "" -"These conditions are based on form values and match if an appropriate " -"selection is made (e.g. choosing another group in the ticket without " -"saving). This applies for drafts (active selection) and currently saved " -"values." +#: ../settings/security/third-party.rst:89 +msgid "This means it only affects:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:64 -msgid "Saved Conditions" +#: ../settings/security/third-party.rst:91 +msgid "manual account linking within the third-party page of the users profile" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:53 +#: ../settings/security/third-party.rst:92 msgid "" -"These conditions only match if the selected values are stored in the " -"database. It ignores the current value or selection of the field, as long as " -"the changes are not saved (e.g. performing field operations for an existing " -"ticket, which is viewed/opened by an agent)." +"logging into an existing local account by utilizing the *automatic account " +"link on initial logon* functionality" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:60 +#: ../settings/security/third-party.rst:None msgid "" -"Keep in mind that the value has to be available in the situation where you " -"need it. Otherwise the condition won't match." +"Screenshot showing the \"automatic account linking notification\"\n" +"setting" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:63 -msgid "" -"Example: you can't perform any actions with *saved condition* on a ticket in " -"creation, because there are no saved values at that time." +#: ../settings/security/third-party.rst:100 +msgid "No User Creation on Logon" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:66 +#: ../settings/security/third-party.rst:102 msgid "" -"You can find a description of the condition operators for core workflows :" -"doc:`here `." +"By default, Zammad will create a new user account if the user logs in via a " +"third-party application and the account doesn't exist yet." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:72 +#: ../settings/security/third-party.rst:105 msgid "" -"Which actions should we run on the relevant fields? The possible actions " -"depend on the object type. However, usually you can at least change the " -"visibility and whether the field is mandatory." +"If you want to prevent Zammad from creating new accounts on logon, you can " +"disable this feature by setting ``No user creation on logon`` to ``yes``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:76 -msgid "Be aware that actions are not available for **related** context." +#: ../settings/security/third-party.rst:None +msgid "Screenshot showing the \"no user creation on logon\" setting" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:78 +#: ../settings/security/third-party/facebook.rst:4 msgid "" -"**Example:** Let's assume you are working in the ticket context. While you " -"can have customer *conditions*, you *can't adjust* objects with actions in " -"that scope. That's because this wouldn't have any impact on the ticket " -"dialog. Of course all ticket attributes (state, owner, ...) are available." +"It is possible to create a quick login for your helpdesk via Facebook To do " +"so, you need to follow these steps:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:84 +#: ../settings/security/third-party/facebook.rst:9 +msgid "Register Facebook App" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:11 msgid "" -"Please also have a look at our :doc:`limitations` to be safe from surprises." +"Visit [https://developers.facebook.com/apps/] and click on \"Add a new App\"" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:88 -msgid "Available Operators" +#: ../settings/security/third-party/facebook.rst:None +msgid "initial page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:90 -msgid "The availability of operators depends on the object type and scope." +#: ../settings/security/third-party/facebook.rst:17 +msgid "After that enter the app settings" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:94 -msgid "" -"Please note that actions may or may not restrict API based access to " -"attributes. We're displaying the following icons for your overview to " -"understand these limits better:" +#: ../settings/security/third-party/facebook.rst:None +msgid "Create App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:0 -msgid "|api| This icon indicates the action affects the API." +#: ../settings/security/third-party/facebook.rst:22 +msgid "Navigate to \"Settings\" and fill in this infromation" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:163 -msgid "api" +#: ../settings/security/third-party/facebook.rst:None +msgid "App Settings" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:0 -msgid "|ui| This icon indicates the action only affects the web interface." +#: ../settings/security/third-party/facebook.rst:27 +msgid "Navigate to app review and Check \"Make [appname] public?\"" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:167 -msgid "ui" +#: ../settings/security/third-party/facebook.rst:None +msgid "App Review" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:102 -msgid "show |ui|" +#: ../settings/security/third-party/facebook.rst:35 +msgid "Configure Zammad as Facebook App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:102 -msgid "Display the chosen field. Allows setting of values." -msgstr "" - -#: ../system/core-workflows/how-do-they-work.rst:109 -msgid "hide |ui|" +#: ../settings/security/third-party/facebook.rst:37 +msgid "" +"Navigate to \"Admin -> Security -> Third Party Applications\" and enter the " +"App ID and the App Secret. You can find this Key in the Dashbard of your " +"Facebok app." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:105 -msgid "" -"Hide the chosen field. However, it technically still allows setting the " -"field." +#: ../settings/security/third-party/facebook.rst:None +msgid "Zammad Configuration" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:108 +#: ../settings/security/third-party/facebook.rst:44 +#: ../settings/security/third-party/github.rst:43 +#: ../settings/security/third-party/gitlab.rst:46 msgid "" -"Please note that the field is **not** gone and still contains an existing " -"value (if set)! Consider *remove* instead, if you want this field to be gone." +"Now you can link accounts via \"Avatar -> Profile -> Link Accounts\" or " +"login via Zammad login page." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:112 -msgid "remove |ui|" +#: ../settings/security/third-party/github.rst:2 +#: ../system/integrations/github.rst:2 +msgid "GitHub" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:112 -msgid "Entirely removes the field. The field value will not be evaluated." +#: ../settings/security/third-party/github.rst:4 +msgid "" +"It is possible to create a quick login for your helpdesk via GitHub. To " +"activate the quick login you need to enable OAuth for GitHub." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:115 -msgid "set mandatory |ui| |api|" +#: ../settings/security/third-party/github.rst:8 +msgid "Register GitHub App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:115 -msgid "Sets the field to mandatory." +#: ../settings/security/third-party/github.rst:10 +msgid "" +"Visit https://www.github.com/settings/applications/new and enter the app " +"settings. As callback URL enter \"https://zammad_host/auth/github/callback\" " +"where zammad_host has to be replaced with your Zammad FQDN" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:118 -msgid "set optional |ui| |api|" +#: ../settings/security/third-party/github.rst:None +msgid "Register OAuth app on www.github.com" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:118 -msgid "Sets the field to optional." +#: ../settings/security/third-party/github.rst:19 +msgid "Configure Zammad as GitHub App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:124 -msgid "add option |ui| |api|" +#: ../settings/security/third-party/github.rst:21 +msgid "" +"Enter the \"APP ID\" and the \"APP SECRET\" from the GitHub OAUTH " +"Applications Dashboard" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:121 -msgid "Allows adding options to tree selects or selects." +#: ../settings/security/third-party/github.rst:None +msgid "GitHub config in Zammad admin interface" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:123 +#: ../settings/security/third-party/github.rst:28 msgid "" -"You have to use the \"remove option\" before performing this action. It " -"allows you to use *existing* configured values." +"After you configured the GitHub credentials and activated the login method, " +"you should see a new icon on the login page." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:128 -msgid "remove option |ui| |api|" +#: ../settings/security/third-party/github.rst:None +msgid "GitHub logo on login page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:127 +#: ../settings/security/third-party/github.rst:34 msgid "" -"Allows removing options from tree selects or selects. It allows you to use " -"*existing* configured values." +"If you click on the icon you will be redirected to GitHub and see something " +"similar to this:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:134 -msgid "set fixed to |ui| |api|" +#: ../settings/security/third-party/github.rst:None +msgid "GitHub oauth page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:131 -msgid "Reduces the available options by your selection." +#: ../settings/security/third-party/github.rst:40 +#: ../settings/security/third-party/gitlab.rst:42 +msgid "" +"When you grant the access you will be redirected to your Zammad instance and " +"logged in as a customer." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:133 -msgid "" -"This reduces your workflows in terms of *add option* and *remove option*." +#: ../settings/security/third-party/gitlab.rst:2 +msgid "Gitlab" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:137 -msgid "fill in |ui|" +#: ../settings/security/third-party/gitlab.rst:4 +msgid "" +"It is possible to create a quick login for your helpdesk via Gitlab. To " +"activate the quick login you need to enable OAuth for Gitlab." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:137 -msgid "Allows filling in of string and integer fields with your values." +#: ../settings/security/third-party/gitlab.rst:8 +msgid "Register Gitlab App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:141 -msgid "fill in empty |ui|" +#: ../settings/security/third-party/gitlab.rst:10 +msgid "To register an app in Gitlab open your profile and select applications." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:140 +#: ../settings/security/third-party/gitlab.rst:12 msgid "" -"Allows filling in of string and integer fields with your values **if the " -"field is empty**." +"As callback URL enter \"https://zammad-fqdn/auth/gitlab/callback\" where " +"zammad-fqdn has to be replaced with your Zammad FQDN" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:144 -msgid "select |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Register OAuth app on gitlab instance" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:144 -msgid "Select a specific value within a select, tree select or boolean field." +#: ../settings/security/third-party/gitlab.rst:18 +msgid "Just select *read_user* under scopes as in the screenshot and save it." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:153 -msgid "auto select |ui|" +#: ../settings/security/third-party/gitlab.rst:21 +msgid "Configure Zammad as Gitlab App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:147 -msgid "Helps users with tree select and select fields:" +#: ../settings/security/third-party/gitlab.rst:23 +msgid "" +"Enter the \"APP ID\" and the \"APP SECRET\" from the Gitlab OAUTH " +"Applications Dashboard and your Gitlab-URL in the \"SITE\" field." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:149 -msgid "" -"If the field has only one option available for selection and no value yet, " -"the value will be automatically set." +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab config in Zammad admin interface" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:152 +#: ../settings/security/third-party/gitlab.rst:30 msgid "" -"This option only works if you have one value and doesn't work if there is " -"more than one option available." +"After you configured the Gitlab credentials and activated the login method, " +"you should see a new icon on the login page." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:157 -msgid "set readonly |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab logo on login page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:156 +#: ../settings/security/third-party/gitlab.rst:36 msgid "" -"Allows you to display an attribute as read only (which means no changes are " -"possible)." +"If you click on the icon you will be redirected to Gitlab and see something " +"similar to this:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:161 -msgid "unset readonly |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab oauth page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:160 +#: ../settings/security/third-party/google.rst:4 msgid "" -"In case a workflow set the field in question to read only, you can undo this " -"with option above." +"With some easy and fast steps, you can enable Zammad to authenticate your " +"users via Google." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:172 -msgid "Stop after match" +#: ../settings/security/third-party/google.rst:8 +msgid "Register a Google App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:174 +#: ../settings/security/third-party/google.rst:10 msgid "" -"Here you can decide if other workflows are executed after the current one." +"First of all, we need to create a new project - you can skip this step if " +"you already have one." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:176 +#: ../settings/security/third-party/google.rst:15 msgid "" -"If set to ``no`` (default), further workflows will be executed if they match " -"the condition. In this case, it is possible that your actions from the " -"current workflow can be overwritten by another workflow." +"Use this link to create a new project: https://console.cloud.google.com/" +"projectcreate" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:180 +#: ../settings/security/third-party/google.rst:18 msgid "" -"If set to ``yes``, no further worflows will be executed after the current " -"one." +"Now expand the menu, expand \"APIs & Services\" and select \"Credentials\". " +"Go to the tab \"OAuth consent screen\" first and ensure to fill in the " +"requested information - without doing so you can't create credentials!" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:184 -msgid "Priority" +#: ../settings/security/third-party/google.rst:None +msgid "Creating a consent screen" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:186 +#: ../settings/security/third-party/google.rst:25 msgid "" -"You can define the sequence, in which the workflows are executed. The " -"default value is ``500``." +"After filling in and saving the consent screen information, you can go to " +"the \"Credentials\" tab and create new \"OAuth client ID\"-Credentials." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:189 +#: ../settings/security/third-party/google.rst:28 msgid "" -"The workflows are executed in ascending order by their priority. That means " -"lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." +"Fill in the necessary information as follows and replace ``zammad_host`` " +"with your FQDN:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:2 -msgid "Learn by Example" +#: ../settings/security/third-party/google.rst:31 +msgid "**Application type** ``[x] Web application``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:4 -msgid "" -"This page provides some basic examples for Core Workflows. Of course you can " -"build much more complex workflows if needed." +#: ../settings/security/third-party/google.rst:34 +msgid "**Authorized JavaScript origins** ``https://zammad_host/``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:7 +#: ../settings/security/third-party/google.rst:37 msgid "" -"To learn about Core Workflows in detail, first go to :doc:`how-do-they-work`." +"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" +"callback``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:10 -msgid "Group Based Examples" +#: ../settings/security/third-party/google.rst:None +msgid "Adding a new OAuth client ID" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:12 +#: ../settings/security/third-party/google.rst:43 msgid "" -"All following workflows have the same base configurations. The workflow may " -"not use them all." +"After creating the credentials, go to your Zammad installation and navigate " +"to \"Admin > Security > Third Party Applications\" > Google. Enter your " +"Client ID and Client secret here." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:15 -msgid "Groups:" +#: ../settings/security/third-party/google.rst:None +msgid "Zammad" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:20 -msgid "Attributes:" +#: ../settings/security/third-party/google.rst:50 +msgid "After submitting, the login via Google can be used." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:22 -msgid "Category (Single tree selection field, not mandatory, agents only)" +#: ../settings/security/third-party/microsoft.rst:2 +msgid "Microsoft" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:23 +#: ../settings/security/third-party/microsoft.rst:4 msgid "" -"Approved (Boolean field, not mandatory, not shown, ``false`` as default)" +"Zammad's Microsoft connection allows your users with Microsoft accounts to " +"login. This works for Azure users as well and can be an alternative to :doc:" +"`/system/integrations/ldap/index`." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:24 -msgid "Operating System (Text field, not mandatory, not shown)" +#: ../settings/security/third-party/microsoft.rst:10 +msgid "" +"This documentation part does not cover our :doc:`📧 Microsoft 365 email " +"channel `." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:25 -msgid "Software used (Single selection field, not mandatory, not shown)" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screenshot showing Microsoft login button on Zammad login screen." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:68 -msgid "Group specific values and fields" +#: ../settings/security/third-party/microsoft.rst:30 +#: ../settings/security/third-party/microsoft.rst:53 +msgid "Supported account types:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:28 +#: ../settings/security/third-party/microsoft.rst:22 msgid "" -"This workflow set depends on the category field. It reduces the available " -"set of values based on the group selected." +"Please note that Zammad only supports these account types (App dependent):" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:33 -msgid "Workflow 2nd Level group" +#: ../settings/security/third-party/microsoft.rst:35 +msgid "Avatars of signing in users:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:35 +#: ../settings/security/third-party/microsoft.rst:33 msgid "" -"This reduces the category options to ``2nd Level/*``, ``Internal/*`` and " -"``Others``. It also sets further required fields to mandatory and visible." -msgstr "" - -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for 2nd level" +"Zammad currently ignores user avatars. If the user is registered with e.g. " +"Gravatar, Zammad will fetch the avatar from there if enabled. See :doc:" +"`Zammad Image Service ` for more." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:43 -msgid "Workflow Support group" +#: ../settings/security/third-party/microsoft.rst:38 +msgid "Step 1 - Register a Microsoft App for Zammad" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:45 +#: ../settings/security/third-party/microsoft.rst:40 msgid "" -"This reduces the category options to ``Support/*``, ``Internal/*`` and " -"``Others``. It also sets further required fields to visible." -msgstr "" - -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for support" +"Login to the `Microsoft Azure Portal `_ and " +"navigate to App registrations to create a new app. Provide the requested " +"information as follows and register your app." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:53 -msgid "Workflow Sales group" +#: ../settings/security/third-party/microsoft.rst:46 +msgid "Name:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:55 +#: ../settings/security/third-party/microsoft.rst:45 msgid "" -"This reduces the category options to ``Sales/*``, ``Internal/*`` and " -"``Others``." +"Any meaningful name fitting, this name will be displayed to users trying to " +"authenticate with this app." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for sales" +#: ../settings/security/third-party/microsoft.rst:49 +msgid "Choose one of the above mentioned account types (see Limitations)." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:68 -#: ../system/integrations/slack.rst:88 -msgid "The Result" +#: ../settings/security/third-party/microsoft.rst:51 +msgid "" +"The correct account type depends on your use case. If you want to use the " +"authentication internal only, choose the first option. If you're unsure, use " +"the \"Help me choose...\" link." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:63 -msgid "" -"This is what the agent would experience with the above workflows in place." +#: ../settings/security/third-party/microsoft.rst:58 +msgid "Redirect URI (optional):" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 +#: ../settings/security/third-party/microsoft.rst:56 msgid "" -"Workflow shows objects and limits options based on selections on the group" +"Select web and provide your callback URL. The callback URL looks like this: " +"``https://zammad.domain.tld/auth/microsoft_office365/callback``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:90 -msgid "Approval process" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to register a Microsoft app" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:71 -msgid "" -"In this case ``approved`` is visible to agents by default. For this " -"workflow, an additional role ``Approval person`` is required (no further " -"permissions)." +#: ../settings/security/third-party/microsoft.rst:71 +msgid "Within **API permissions** add the following permissions:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that restricts an approval attribute to specific roles" +#: ../settings/security/third-party/microsoft.rst:69 +msgid "``User.Read``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:81 -msgid "" -"This workflow may work best in combination with a :doc:`trigger ` but technically, this is not required." +#: ../settings/security/third-party/microsoft.rst:71 +msgid "Contacts" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:84 -msgid "" -"Select fields may be a better approach because they allow more values than " -"just a simple ``true`` or ``false``." +#: ../settings/security/third-party/microsoft.rst:71 +msgid "``Contacts.Read``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 +#: ../settings/security/third-party/microsoft.rst:73 msgid "" -"Workflow fixes possible values of \"Approved ?\" to a specific selection " -"depending on the users role" +"You can find these permissions within *Microsoft Graph → Delegated " +"permissions*." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:103 -msgid "State dependent mandatory fields" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to add required API permissions" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:93 +#: ../settings/security/third-party/microsoft.rst:80 msgid "" -"This workflow sets ``Category`` to mandatory if the agent wants to set the " -"states ``closed`` or ``pending close`` to enforce categorization." +"Within **Certificates & secrets** create a new client secret. Note down the " +"returned secret **value** for later. **Do not** use the secret ID!" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that sets fields to mandatory on specific states" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to create a new app secret" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 +#: ../settings/security/third-party/microsoft.rst:88 msgid "" -"Workflow sets category field to mandatory upon choosing closed or pending " -"close as state" +"From **Overview** copy your apps *Application (client) ID*. If you're using " +"a single tenant app, please also copy *Directory (tenant) ID*. You now have " +"all required information for Zammad." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:106 -msgid "Manual Ticket Handover Process" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to retreive application client and tenant IDs" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:108 -msgid "This example covers the handover of a ticket from one agent to another:" +#: ../settings/security/third-party/microsoft.rst:98 +msgid "Step 2 - Add App Credentials to Zammad" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:110 +#: ../settings/security/third-party/microsoft.rst:100 msgid "" -"When the ticket owner is modified, a new text field (\"Handover\") shows up " -"for a comment" +"Navigate to Security > Third-party Applications (Tab) within Zammad's admin " +"settings. Scroll down to the section *Authentication via Microsoft* and fill " +"in the required information." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:112 -msgid "" -"This may only be visible when the owner is changed, therefore it has to be " -"hidden in general" +#: ../settings/security/third-party/microsoft.rst:105 +msgid "App ID:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:114 -msgid "The input in this handover text field is mandatory" +#: ../settings/security/third-party/microsoft.rst:105 +msgid "This is your *Application (client) ID*." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:115 -msgid "" -"After submitting changes, the value of the handover field must be added as " -"an note to the ticket (via trigger)" +#: ../settings/security/third-party/microsoft.rst:108 +msgid "App secret:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:121 -msgid "Hiding handover field" +#: ../settings/security/third-party/microsoft.rst:108 +msgid "This is your *client secret* (value)." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Hiding the handover field in core workflows" +#: ../settings/security/third-party/microsoft.rst:113 +msgid "App Tenant ID:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:126 -msgid "Showing handover field and setting it to mandatory" +#: ../settings/security/third-party/microsoft.rst:111 +msgid "" +"**optional** only required for apps that use account type *Accounts in this " +"organizational directory only (Default Directory only - Single tenant).*" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Showing the handover field and set it as mandatory" +#: ../settings/security/third-party/microsoft.rst:115 +msgid "" +"Apply your settings by pressing submit and activate *Authentication via " +"Microsoft*." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:131 -msgid "Trigger writing handover input to a new article" +#: ../settings/security/third-party/microsoft.rst:None +msgid "" +"Screencast showing how to add app credentials and activating the\n" +"authentication method" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Write handover content to a new article" +#: ../settings/security/third-party/saml.rst:2 +msgid "SAML" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:133 +#: ../settings/security/third-party/saml.rst:4 msgid "" -"As a result, the ticket includes an article of the type note which includes " -"the predefined text and the handover comment." +"Connect your SAML (Security Assertion Markup Language) identity provider as " +"a single sign-on (SSO) method." msgstr "" -#: ../system/core-workflows/limitations.rst:6 -msgid "Core Workflows do not replace Triggers" +#: ../settings/security/third-party/saml.rst:7 +msgid "" +"SAML is an open standard for SSO authentication (among other things). Sign-" +"ins are shared across multiple **service providers** and managed by a " +"central **identity provider** (IdP)." msgstr "" -#: ../system/core-workflows/limitations.rst:5 +#: ../settings/security/third-party/saml.rst:11 msgid "" -"Workflows manipulate the behavior of fields. However, they do not set values " -"in fields because of actions." +"In this case, the service provider is Zammad, and the IdP is a software " +"service that you either host or subscribe to (*e.g.,* `Keycloak `_, `Redhat SSO Server `_, `ADFS `_, or `Okta `_)." msgstr "" -#: ../system/core-workflows/limitations.rst:16 -msgid "API calls are only partly affected" +#: ../settings/security/third-party/saml.rst:18 +msgid "" +"This guide assumes you are already using SAML within your organization (i." +"e., that your IdP is fully set up)." msgstr "" -#: ../system/core-workflows/limitations.rst:9 +#: ../settings/security/third-party/saml.rst:21 msgid "" -"Some options affect UI only and thus do not restrict responses and calls." +"Please note: Our instructions are based on connecting Zammad with Keycloak." msgstr "" -#: ../system/core-workflows/limitations.rst:11 -msgid "This affects the following actions:" +#: ../settings/security/third-party/saml.rst:25 +msgid "Step 1: Configure Your IdP" msgstr "" -#: ../system/core-workflows/limitations.rst:13 -msgid "select" +#: ../settings/security/third-party/saml.rst:28 +msgid "Add Zammad as a Client/App" msgstr "" -#: ../system/core-workflows/limitations.rst:14 -msgid "auto select" +#: ../settings/security/third-party/saml.rst:30 +msgid "" +"Import Zammad into your IdP using the XML configuration found at ``https://" +"your.zammad.domain/auth/saml/metadata``." msgstr "" -#: ../system/core-workflows/limitations.rst:15 -msgid "show" +#: ../settings/security/third-party/saml.rst:33 +msgid "" +"If your IdP doesn't support XML import, you will have to configure Zammad as " +"a new client/app manually using the above XML metadata file for reference." msgstr "" -#: ../system/core-workflows/limitations.rst:16 -msgid "hide" +#: ../settings/security/third-party/saml.rst:36 +msgid "For instance, when you see this tag:" msgstr "" -#: ../system/core-workflows/limitations.rst:25 -msgid "Some fields stay unavailable to customers" +#: ../settings/security/third-party/saml.rst:42 +msgid "" +"Set the **Assertion Consumer Service Binding URL** (sometimes also listed as " +"**Valid Redirect URIs**) to ``http://your.zammad.domain/auth/saml/callback``." msgstr "" -#: ../system/core-workflows/limitations.rst:19 -msgid "" -"For technical and security reasons, some default fields (the pale ones you " -"can't edit) stay unavailable for display and usage on customer permissions." +#: ../settings/security/third-party/saml.rst:47 +msgid "Set Up User Attribute Mapping" msgstr "" -#: ../system/core-workflows/limitations.rst:23 +#: ../settings/security/third-party/saml.rst:49 msgid "" -"If you require your customers to change e.g. priorities, please consider " -"using workarounds via :doc:`/system/objects` and :doc:`/manage/trigger`." +"Zammad requests the following user attributes (or “properties”) from the IdP:" msgstr "" -#: ../system/core-workflows/limitations.rst:29 -msgid "Ticket title changes not supported in edit mask" +#: ../settings/security/third-party/saml.rst:51 +msgid "Email address (``email``)" msgstr "" -#: ../system/core-workflows/limitations.rst:28 -msgid "" -"It is currently not possible to perform changes of the ticket title in the " -"edit mask (e.g. renaming, set to read-only)." +#: ../settings/security/third-party/saml.rst:52 +msgid "Full name (``name``)" msgstr "" -#: ../system/core-workflows/limitations.rst:37 -msgid "What is out of scope of Core Workflows?" +#: ../settings/security/third-party/saml.rst:53 +msgid "Given name (``first_name``)" msgstr "" -#: ../system/core-workflows/limitations.rst:32 -msgid "" -"There are some things that would count as workflow but are either done via :" -"doc:`/manage/trigger` or :doc:`/manage/scheduler`." +#: ../settings/security/third-party/saml.rst:54 +msgid "Family name (``last_name``)" msgstr "" -#: ../system/core-workflows/limitations.rst:35 -msgid "Such as (but not limited to):" +#: ../settings/security/third-party/saml.rst:56 +msgid "" +"You may need to set up “mappers” (or “mappings”) to tell your IdP how user " +"attributes in SAML correspond to those in Zammad. For a more detailed " +"breakdown, refer to the XML metadata file referenced in the previous section." msgstr "" -#: ../system/core-workflows/limitations.rst:37 -msgid "up- or downgrade permissions of users" +#: ../settings/security/third-party/saml.rst:62 +msgid "Per-IdP Instructions" msgstr "" -#: ../system/core-workflows/limitations.rst:38 -msgid "affecting article creation or listing" +#: ../settings/security/third-party/saml.rst:102 +msgid "Keycloak" msgstr "" -#: ../system/data-privacy.rst:2 -msgid "Data Privacy" +#: ../settings/security/third-party/saml.rst:65 +msgid "" +"**To add Zammad as a client,** save the XML configuration to disk (``https://" +"your.zammad.domain/auth/saml/metadata``) and use **Clients > Clients list > " +"Import client** in the Keycloak admin panel." msgstr "" -#: ../system/data-privacy.rst:4 +#: ../settings/security/third-party/saml.rst:70 msgid "" -"For compliance with GDPR and other data privacy laws, you may wish to " -"**permanently delete users from the system**, along with **all of their " -"associated tickets**." +"To help Zammad **match its own user accounts to Keycloak users**, create a " +"user attribute (or “property”) mapper. In **Clients list**, click on your " +"newly created Client ID, choose the tab **Client scopes** and click on the " +"link which refers to your Zammad instance. Choose **Add mapper > By " +"configuration > User Property** and create a mapper with the following " +"entries:" 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 `!" +#: ../settings/security/third-party/saml.rst:78 +msgid "**Name**" msgstr "" -#: ../system/data-privacy.rst:12 -msgid "" -"Access to this panel requires ``admin.data_privacy`` permissions (introduced " -"in Zammad 3.5)." +#: ../settings/security/third-party/saml.rst:80 +msgid "**Mapper Type**" msgstr "" -#: ../system/data-privacy.rst:15 -msgid "" -"On older systems that have not been updated yet, customers can also be :docs:" -"`deleted via the Zammad console `." +#: ../settings/security/third-party/saml.rst:81 +msgid "``User Property``" msgstr "" -#: ../system/data-privacy.rst:22 -msgid "User deletion dialog in the Data Privacy panel" +#: ../settings/security/third-party/saml.rst:82 +msgid "**Property**" msgstr "" -#: ../system/data-privacy.rst:22 -msgid "" -"The user deletion dialog lists some of the tickets that will be removed from " -"the system along with the user." +#: ../settings/security/third-party/saml.rst:83 +msgid "``emailAddress``" msgstr "" -#: ../system/data-privacy.rst:27 -msgid "Deleting Users via GUI" +#: ../settings/security/third-party/saml.rst:84 +msgid "**SAML Attribute Name**" msgstr "" -#: ../system/data-privacy.rst:29 -msgid "🔥 **All deletions are FINAL!**" +#: ../settings/security/third-party/saml.rst:86 +msgid "**SAML Attribute NameFormat**" msgstr "" -#: ../system/data-privacy.rst:31 -msgid "Once you click “Delete”, the action cannot be canceled or undone." +#: ../settings/security/third-party/saml.rst:87 +msgid "``basic``" msgstr "" -#: ../system/data-privacy.rst:33 +#: ../settings/security/third-party/saml.rst:89 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." +"In the example above, we're telling Zammad that whenever it receives a SAML " +"login request, it should take the ``email`` property from Keycloak, look for " +"a Zammad user with the same ``email`` attribute, and create a new session " +"for that user." msgstr "" -#: ../system/data-privacy.rst:36 -msgid "**The following records cannot be deleted:**" +#: ../settings/security/third-party/saml.rst:95 +msgid "" +"If your Keycloak users' email addresses are stored on another property (*e." +"g.,* ``username``), adjust accordingly." msgstr "" -#: ../system/data-privacy.rst:38 -msgid "your own account" +#: ../settings/security/third-party/saml.rst:98 +msgid "" +"Back in **Settings**, enter the Client ID (``https://your.zammad.domain/auth/" +"saml/metadata``) in the field **Master SAML Processing URL**." msgstr "" -#: ../system/data-privacy.rst:39 -msgid "the system's last remaining administrator account" +#: ../settings/security/third-party/saml.rst:101 +msgid "You also need to enable **Sign assertions**." msgstr "" -#: ../system/data-privacy.rst:42 -msgid "Step 1: Find a User / Confirm Deletion" +#: ../settings/security/third-party/saml.rst:105 +msgid "Step 2: Configure Zammad" msgstr "" -#: ../system/data-privacy.rst:44 -msgid "There are three ways to access the user deletion dialog:" +#: ../settings/security/third-party/saml.rst:107 +msgid "" +"Enable SAML and enter your IdP's details in the Admin Panel under **Settings " +"> Security > Third Party Applications > Authentication via SAML**:" msgstr "" -#: ../system/data-privacy.rst:51 -msgid "**from the user's profile**" +#: ../settings/security/third-party/saml.rst:None +msgid "Example configuration of SAML part 1" msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Accessing the user deletion dialog in a user profile" +#: ../settings/security/third-party/saml.rst:119 +msgid "Display name" msgstr "" -#: ../system/data-privacy.rst:51 -msgid "Click **Action > Delete**." +#: ../settings/security/third-party/saml.rst:116 +msgid "" +"Allows you to define a custom button name for SAML. This helps your users to " +"understand better what the button on the login page does." msgstr "" -#: ../system/data-privacy.rst:58 -msgid "**in the “Manage > Users” Admin Panel**" +#: ../settings/security/third-party/saml.rst:119 +msgid "Defaults to ``SAML``." msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Accessing the user deletion dialog under “Users” in the Admin Panel" +#: ../settings/security/third-party/saml.rst:123 +msgid "IDP SSO target URL" msgstr "" -#: ../system/data-privacy.rst:58 -msgid "Use the **⋮ Actions** menu for the target user." +#: ../settings/security/third-party/saml.rst:122 +msgid "" +"This is the target URL Zammad shall redirect to when the user presses the " +"SAML button. For Keycloak, this needs to look like https://your.domain/" +"realms/your-realm/protocol/saml" msgstr "" -#: ../system/data-privacy.rst:66 ../system/data-privacy.rst:104 -msgid "**in the “System > Data Privacy” Admin Panel**" +#: ../settings/security/third-party/saml.rst:127 +msgid "IDP single logout target URL" msgstr "" -#: ../system/data-privacy.rst:0 +#: ../settings/security/third-party/saml.rst:126 msgid "" -"Accessing the user deletion dialog under “Data Privacy” in the Admin Panel" +"This is the URL to which the single logout request and response should be " +"sent." msgstr "" -#: ../system/data-privacy.rst:65 +#: ../settings/security/third-party/saml.rst:131 +msgid "IDP certificate" +msgstr "" + +#: ../settings/security/third-party/saml.rst:130 msgid "" -"Use the **New Deletion Task** button. Search for users by name or email " -"address." +"The public certificate of your IDP for Zammad to verify during the callback " +"phase." msgstr "" -#: ../system/data-privacy.rst:79 -msgid "**Delete organizations**" +#: ../settings/security/third-party/saml.rst:145 +msgid "IDP certificate fingerprint" msgstr "" -#: ../system/data-privacy.rst:69 +#: ../settings/security/third-party/saml.rst:134 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:" +"The fingerprint of your IDPs public certificate to verify during callback " +"phase." msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Deleting an organization via the user deletion dialog" +#: ../settings/security/third-party/saml.rst:137 +msgid "🔏 **For the IdP certificate / certificate fingerprint:**" msgstr "" -#: ../system/data-privacy.rst:78 +#: ../settings/security/third-party/saml.rst:139 msgid "" -"If this option does not appear, make sure there are no pending deletion " -"tasks for other customers from this organization." +"Provide **only one or the other**—do not provide both! (Between the two, we " +"recommend the signing certificate itself: fingerprints use SHA-1, which `has " +"been broken for a while now `_.)" msgstr "" -#: ../system/data-privacy.rst:82 -msgid "Step 2: Monitor Deletion Job Status" +#: ../settings/security/third-party/saml.rst:144 +msgid "" +"**Keycloak users:** Find your certificate in the Keycloak admin panel under " +"**Realm Settings > Keys > Algorithm: RS256 > Certificate**." msgstr "" -#: ../system/data-privacy.rst:84 +#: ../settings/security/third-party/saml.rst:151 +msgid "Name identifier format" +msgstr "" + +#: ../settings/security/third-party/saml.rst:148 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:" +"This is the unique identifiers field type. Usually it should be ``urn:oasis:" +"names:tc:SAML:1.1:nameid-format:emailAddress``." msgstr "" -#: ../system/data-privacy.rst:98 -msgid "**in the Activity Stream**" +#: ../settings/security/third-party/saml.rst:151 +msgid "Zammad **expects an email address as unique identifier**!" msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Activity Stream showing data privacy tasks" +#: ../settings/security/third-party/saml.rst:155 +msgid "UID attribute name" msgstr "" -#: ../system/data-privacy.rst:94 +#: ../settings/security/third-party/saml.rst:154 msgid "" -"For each deleted user, the Activity Stream will be updated twice—once when " -"the task is created, and once when it's complete." +"Here you can define an attribute that uniquely identifies the user. If " +"unset, the name identifier returned by the IDP is used." msgstr "" -#: ../system/data-privacy.rst:97 -msgid "" -"These notifications are only visible to users with ``admin.data_privacy`` " -"permissions." +#: ../settings/security/third-party/saml.rst:None +msgid "Example configuration of SAML part 2" msgstr "" -#: ../system/data-privacy.rst:0 +#: ../settings/security/third-party/saml.rst:163 msgid "" -"The task list within Data Privacy shows removals being in progress and " -"completed." +"Decide if the certificate for the connection to the IdP service has to be " +"verified or not (default: ``yes``)." msgstr "" -#: ../system/data-privacy.rst:107 -msgid "Frequently Asked Questions" +#: ../settings/security/third-party/saml.rst:169 +msgid "Signing & Encrypting" msgstr "" -#: ../system/data-privacy.rst:121 -msgid "What happens if I receive an email from a deleted customer?" -msgstr "" - -#: ../system/data-privacy.rst:110 +#: ../settings/security/third-party/saml.rst:169 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." +"Define if you want to sign, encrypt, do both or nothing for the requests." msgstr "" -#: ../system/data-privacy.rst:115 -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**." +#: ../settings/security/third-party/saml.rst:179 +msgid "Certificate (PEM)" msgstr "" -#: ../system/data-privacy.rst:130 -msgid "What about user information stored in internal notes or other messages?" +#: ../settings/security/third-party/saml.rst:172 +msgid "" +"Paste the public certificate of your Zammad SAML client, if you want to " +"encrypt the requests." msgstr "" -#: ../system/data-privacy.rst:124 -msgid "" -"The deletion process removes **user accounts and associated tickets only**." +#: ../settings/security/third-party/saml.rst:175 +msgid "Make sure the certificate is:" msgstr "" -#: ../system/data-privacy.rst:126 -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." +#: ../settings/security/third-party/saml.rst:177 +msgid "already valid and not yet expired" msgstr "" -#: ../system/data-privacy.rst:137 -msgid "I deleted an user and can still see a message they sent!" +#: ../settings/security/third-party/saml.rst:178 +msgid "no CA certificate" msgstr "" -#: ../system/data-privacy.rst:133 -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." +#: ../settings/security/third-party/saml.rst:179 +msgid "valid for signing and encrypting" msgstr "" -#: ../system/data-privacy.rst:141 -msgid "I removed a customer, now my reporting is off!" +#: ../settings/security/third-party/saml.rst:185 +msgid "Private key (PEM)" msgstr "" -#: ../system/data-privacy.rst:140 +#: ../settings/security/third-party/saml.rst:182 msgid "" -"When removing users and their tickets, all references are removed. This also " -"affects e.g. Reporting - these information are lost." +"Paste the private key of your Zammad SAML client here, if you want to sign " +"the requests." msgstr "" -#: ../system/data-privacy.rst:145 -msgid "How long does Zammad store created tasks?" +#: ../settings/security/third-party/saml.rst:185 +msgid "Make sure the key is an RSA key with a length of at least 2048 bits." msgstr "" -#: ../system/data-privacy.rst:144 -msgid "" -"Please see the on-premise data section of the :docs:`data privacy ` chapter." +#: ../settings/security/third-party/saml.rst:188 +msgid "Private key secret" msgstr "" -#: ../system/data-privacy.rst:150 -msgid "What about re-assigned tickets? I want to delete them, too." +#: ../settings/security/third-party/saml.rst:188 +msgid "If your private key is secured with a secret, you can provide it here." msgstr "" -#: ../system/data-privacy.rst:148 -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." +#: ../settings/security/third-party/saml.rst:192 +msgid "Your callback URL" msgstr "" -#: ../system/data-privacy.rst:154 -msgid "Why are there so many deletion task entries, I didn't create them!" +#: ../settings/security/third-party/saml.rst:191 +msgid "" +"This URL is needed for your IdP configuration so it knows where to redirect " +"to after successful authentication." msgstr "" -#: ../system/data-privacy.rst:153 +#: ../settings/security/third-party/saml.rst:194 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." +"After saving your input by clicking on the \"Submit\" button, Zammad " +"verifies the provided keys/certificates (e.g. if they are valid for signing/" +"encrypting and if they aren't expired)." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:2 -msgid "Admin Panel Reference" +#: ../settings/security/third-party/saml.rst:199 +msgid "" +"See :ref:`automatic account linking ` for details " +"on how to link existing Zammad accounts to IdP accounts." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:None -msgid "Screenshot of Checkmk settings overview" +#: ../settings/security/third-party/saml.rst:205 +msgid "Automatic account linking doesn't work" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:12 +#: ../settings/security/third-party/saml.rst:206 msgid "" -"Which :doc:`group ` should Checkmk tickets be assigned " -"to as a default (*i.e.,* when none is specified)?" +"Have you double-checked your IdP's user attribute mapping configuration?" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:15 -msgid "(Applies to :ref:`API alerts ` only.)" +#: ../settings/security/third-party/twitter.rst:4 +msgid "" +"It is possible to create a quick login for your helpdesk via Twitter. To do " +"so, you need to follow these steps:" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:21 -msgid "Auto close" +#: ../settings/security/third-party/twitter.rst:8 +msgid "Register Twitter App" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:18 -msgid "" -"Should Zammad automatically close tickets if a service has recovered on its " -"own?" +#: ../settings/security/third-party/twitter.rst:10 +msgid "Go to https://dev.twitter.com/apps and login with your account." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:21 -msgid "(Agents will receive notifications for such closures as appropriate.)" +#: ../settings/security/third-party/twitter.rst:15 +msgid "Click on \"Create App\"" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:30 -msgid "Auto-close state" +#: ../settings/security/third-party/twitter.rst:None +msgid "new app page" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:24 -msgid "What ticket state should be applied when “auto-closing” a ticket?" +#: ../settings/security/third-party/twitter.rst:20 +msgid "" +"Enter app settings. As \"Callback URL\" you need to enter ``https://" +"zammad_host/api/v1/external_credentials/twitter/callback``. You need to " +"replace ``zammad_host`` with the domain of your Zammad system." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:26 +#: ../settings/security/third-party/twitter.rst:24 msgid "" -"You can choose from the seven built-in ticket states. If these states aren't " -"enough for you, you can :ref:`define a new ticket state ` for this purpose as well. This can be useful for tracking " -"tickets with :doc:`reports `, for example." +"After the app has been created, update the application icon and organization " +"attributes." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:35 -#: ../system/integrations/cti/includes/recent-logs.include.rst:2 -#: ../system/integrations/ldap/index.rst:74 -#: ../system/integrations/pgp/index.rst:106 -msgid "Recent Logs" +#: ../settings/security/third-party/twitter.rst:None +msgid "set permissions to receive and send direct messages" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:None -msgid "Screenshot of Checkmk \"Recent Logs\" section" +#: ../settings/security/third-party/twitter.rst:30 +msgid "" +"Next we need to set ``read, write and access direct messages`` permissions " +"for the app." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:41 -msgid "" -"If you're having trouble getting Zammad and Checkmk to play nicely together, " -"this section can help you troubleshoot." +#: ../settings/security/third-party/twitter.rst:None +msgid "click on Keys & Access Token, note them" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:44 +#: ../settings/security/third-party/twitter.rst:36 msgid "" -"It contains a record of the fifty most recent transactions that Zammad knows " -"about, including each one's request/response details and return status." +"Go to \"Keys and Access Token\" tab and note the \"Consumer Key\" and " +"\"Consumer Secret\"." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:2 -msgid "API Reference" +#: ../settings/security/third-party/twitter.rst:40 +msgid "Configure Zammad as Twitter App" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:4 +#: ../settings/security/third-party/twitter.rst:42 msgid "" -"For most users, :ref:`the sample scripts from the Setup Guide ` will do the job just fine. But if you want more fine-grained control" -"—for instance, to create high- and low-priority tickets for different types " -"of system events—then you'll have to customize the data those scripts send " -"to Zammad." +"Go to \"Admin > Security > Twitter > Third Party Applications > Twitter\" " +"Section." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:15 -msgid "" -"This custom script will automatically set all tickets it creates to **high " -"priority** and **assign them to charlie@chrispresso.com**." +#: ../settings/security/third-party/twitter.rst:None +msgid "Admin > Security > Third Party Applications" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:32 -msgid "How Does it Work?" +#: ../settings/security/third-party/twitter.rst:48 +msgid "" +"Fill in the \"Twitter Key\" and the \"Twitter Secret\" and click the " +"\"Submit\" button." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:34 +#: ../settings/security/third-party/twitter.rst:51 msgid "" -"There are two kinds of data you can pass to the API, both in the form of key-" -"value pairs:" +"Now you can link accounts via \"Avatar > Profile > Link Accounts\" or login " +"via Zammad login page." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:44 -msgid "Checkmk parameters" +#: ../settings/security/two-factor.rst:11 +msgid "Two-factor Authentication Methods" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:38 -msgid "" -"are required, and make up the **contents** of the resulting tickets/" -"articles. They also determine whether an event creates a new ticket or " -"updates/closes an existing one." +#: ../settings/security/two-factor.rst:2 +msgid "Two-Factor Authentication" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:42 +#: ../settings/security/two-factor.rst:4 msgid "" -"These are the only values used in the sample scripts. **Use them as-is**; " -"technically, they can be customized, but it's hard to imagine a good reason " -"for it." +"Two-factor authentication (2FA) enhances the security of Zammad accounts by " +"adding an extra layer of verification beyond a password. It requires users " +"to provide two different types of authentication factors, typically " +"something they know (like a password) and something they possess (like a " +"mobile device or a security token), to ensure that only authorized " +"individuals can access the account." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:52 -msgid "Ticket attributes" +#: ../settings/security/two-factor.rst:19 +msgid "Enable Recovery Codes" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:47 +#: ../settings/security/two-factor.rst:21 msgid "" -"are optional, and can be used to **adjust settings** on newly created " -"tickets (*e.g.,* set the owner, group, priority, or state)." +"Recovery codes are one-time use security codes that can be used by the user " +"if they lose access to their other two-factor authentication methods. They " +"cannot be used on their own, they can only be activated if at least one two-" +"factor authentication method is enabled." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:50 -msgid "" -"If you want to customize your Checkmk alert script, do it with these. Simply " -"add an extra “form” option for each one (``-F \"key=value\"``) to your " -"script's ``curl`` command line, as in the example above." +#: ../settings/security/two-factor.rst:None +msgid "Enable Recovery Codes Setting" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:54 -msgid "💡 **It's just an API endpoint!**" +#: ../settings/security/two-factor.rst:30 +msgid "" +"Recovery codes can only be used as a backup method. If enabled, they will be " +"automatically generated for the user once they set up their initial two-" +"factor authentication method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:56 +#: ../settings/security/two-factor.rst:34 msgid "" -"When using Checkmk integration, messages need to be formatted in a certain " -"way, but that *doesn't mean the messages actually have to come from Checkmk*." +"The user will be asked to print out or save the generated recovery codes in " +"a safe place. Once used, a recovery code cannot be reused." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:59 +#: ../settings/security/two-factor.rst:37 msgid "" -"If you use another monitoring tool that's not officially supported by " -"Zammad, there's probably a way to make it work with your Checkmk callback " -"URL." +"Users will also have an option to regenerate their recovery codes at any " +"time, which invalidates already existing recovery codes and provides them " +"with a list of fresh codes." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:63 -msgid "Checkmk Parameters" +#: ../settings/security/two-factor.rst:41 +msgid "" +"After you enable this setting, when the user completes a setup of their " +"initial two-factor authentication method, they will be presented with a list " +"of recovery codes and instructed to save them for later use." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:65 -msgid "" -"When a notification is received, Zammad creates a new article containing the " -"details of the event that triggered it:" +#: ../settings/security/two-factor.rst:None +msgid "Recovery Codes Generation Modal Dialog" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:None -msgid "Checkmk article body" +#: ../settings/security/two-factor.rst:50 +msgid "Enforce the Set Up of the Two-Factor Authentication" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:72 +#: ../settings/security/two-factor.rst:52 msgid "" -"These details come from the fields listed below, which correspond to " -"parameters provided by Checkmk (``$NOTIFY_*``)." +"In case you wish to require your users to set up at least one two-factor " +"authentication method for their account, you can do this by selecting " +"specific user roles the requirement applies to in **Enforced for user " +"roles** setting. Of course you must have at least one two-factor " +"authentication method enabled for this setting to take effect." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:75 -msgid "**Required fields are marked with an asterisk (\\*).**" +#: ../settings/security/two-factor.rst:None +msgid "Enforced for User Roles Setting" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:79 -msgid "event_id\\*" +#: ../settings/security/two-factor.rst:62 +msgid "" +"After you change this setting, if the user has one of the selected roles on " +"their account, they will be forced to set up the two-factor authentication " +"upon next sign in or application reload." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:78 +#: ../settings/security/two-factor.rst:66 msgid "" -"A unique ID for the system event. (``$NOTIFY_SERVICEPROBLEMID`` / " -"``$NOTIFY_HOSTPROBLEMID``)" +"A modal dialog with instructions will be shown, and they will not be able to " +"do any work before they set up at least one two-factor method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:86 -msgid "host\\*" +#: ../settings/security/two-factor.rst:None +msgid "Modal Dialog for Enforcing Two-Factor Authentication Set Up" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:82 +#: ../settings/security/two-factor.rst:74 +msgid "Reset Two-Factor Authentication for a Specific User" +msgstr "" + +#: ../settings/security/two-factor.rst:76 msgid "" -"The hostname of the system that the event originated from. " -"(``$NOTIFY_HOSTNAME``)" +"In case an user isn't able to login anymore because of an inaccessible " +"second factor, you can reset the user's 2FA method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:85 +#: ../settings/security/two-factor.rst:79 msgid "" -"Used to determine if a new event belongs to an existing ticket. Also used in " -"the subject line of the resulting article (“ is ”)." +"To do this, go to the user management and search for the relevant user. " +"After you found the account, click the button in the action column and " +"select \"Manage Two-Factor Authentication\":" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:96 -msgid "service" +#: ../settings/security/two-factor.rst:None +msgid "Context menu in action column in user management" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:89 +#: ../settings/security/two-factor.rst:87 msgid "" -"The name of the service that the event originated from. " -"(``$NOTIFY_SERVICEDESC``)" +"After selecting this, you can see a dialog where you can either reset one " +"2FA method or reset all of the user's 2FA methods:" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:92 -msgid "Used to determine if a new event belongs to an existing ticket." +#: ../settings/security/two-factor.rst:None +msgid "Dialog for resetting user's 2FA method" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:94 -#: ../system/integrations/checkmk/api-reference.rst:110 -msgid "Displayed as ``-`` when omitted." +#: ../settings/security/two-factor.rst:94 +msgid "" +"Choose the fitting one, click on the corresponding \"Remove ...\" button and " +"confirm your action. The user now has to setup a new 2FA method, depending " +"on your 2FA configuration." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:104 -msgid "state\\*" +#: ../settings/security/two-factor/authenticator-app.rst:2 +msgid "Authenticator App" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:99 +#: ../settings/security/two-factor/authenticator-app.rst:4 msgid "" -"The current state of the service or host in question. " -"(``$NOTIFY_SERVICESTATE`` / ``$NOTIFY_HOSTSTATE``)" +"The authenticator app method is a type of two-factor authentication that " +"uses a mobile application to generate one-time codes for account " +"verification. After setting up the authenticator app on their device, the " +"user links it to their Zammad account." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:102 +#: ../settings/security/two-factor/authenticator-app.rst:12 msgid "" -"Used to detect when a ticket should be auto-closed (*i.e.,* on ``OK``/" -"``UP``). Also used in the subject line of the resulting article (“ is " -"”)." +"When logging in, the user is prompted to enter a time-sensitive code " +"generated by the app, in addition to their password. This code acts as the " +"second factor of authentication, providing an extra layer of security as it " +"changes periodically and is unique to the user's device." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:110 -msgid "text" +#: ../settings/security/two-factor/authenticator-app.rst:None +msgid "Security Code in Google Authenticator App" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:107 +#: ../settings/security/two-factor/authenticator-app.rst:22 msgid "" -"The output of the process that triggered the event. " -"(``$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" +"The app generates codes based on a shared secret key stored securely on both " +"the user's device and the server, ensuring a synchronized and secure " +"authentication process. The method of generating the codes is sometimes also " +"called TOTP (time-based one-time password)." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:121 -msgid "" -"The Object Manager attribute panel displays built-in and custom\n" -"attribute names." +#: ../settings/security/two-factor/authenticator-app.rst:28 +msgid "Enabling the Authenticator App Method" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:121 -msgid "Find a complete list of ticket attributes in the Object Manager." +#: ../settings/security/two-factor/authenticator-app.rst:30 +#: ../settings/security/two-factor/security-keys.rst:28 +msgid "To enable the method, just toggle the switch on in the settings." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:123 -msgid "" -"Ticket attributes are entirely optional, and can be used to customize the " -"tickets that Checkmk creates. (Note that these attributes will be ignored if " -"a new event belongs to an existing ticket.)" +#: ../settings/security/two-factor/authenticator-app.rst:None +msgid "Authenticator App Switch in Settings" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:128 +#: ../settings/security/two-factor/authenticator-app.rst:36 msgid "" -"Why would you want to do this? Maybe you have only one IT guy, and all " -"system monitoring issues should be automatically assigned to him. Or, maybe " -"you're creating multiple notification rules so that database outages take " -"higher priority than disk space warnings." +"Now the users will be able to set up this two-factor authentication method " +"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " +"Once they do, on next sign-in with password, they will be asked to provide " +"an additional security code generated by their mobile device." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:135 -msgid "In most cases, you'll probably want to set one of the following:" +#: ../settings/security/two-factor/security-keys.rst:2 +msgid "Security Keys" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:137 -msgid "group" +#: ../settings/security/two-factor/security-keys.rst:4 +msgid "" +"The security keys method is a type of a two-factor authentication that uses " +"Web Authentication API in the browser for verifying user's identity. The " +"user can register multiple hardware or software security keys with their " +"Zammad account and then they can use it during the sign-in process." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:139 -msgid "state" +#: ../settings/security/two-factor/security-keys.rst:12 +msgid "" +"When logging in, the user is prompted to provide the same security key they " +"registered with their account, in addition to their password. This key acts " +"as the second factor of authentication, providing an extra layer of security." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:140 -msgid "priority" +#: ../settings/security/two-factor/security-keys.rst:None +msgid "Security Key dialog in Safari on macOS" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:142 +#: ../settings/security/two-factor/security-keys.rst:21 msgid "" -"but in practice, you can set almost any attribute, including :doc:`custom " -"ones you created through the Object Manager `." -msgstr "" - -#: ../system/integrations/checkmk/api-reference.rst:145 -msgid "Please note that the following attributes are **not customizable**:" +"The type of the key can range from hardware USB sticks to passkeys stored in " +"a device of user's choice. Which type can be used depends on the browser " +"flavor and the platform of the user." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:147 -msgid "title" +#: ../settings/security/two-factor/security-keys.rst:26 +msgid "Enabling the Security Keys Method" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:148 -msgid "id" +#: ../settings/security/two-factor/security-keys.rst:None +msgid "Security Keys Switch in Settings" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:149 -msgid "ticket number" +#: ../settings/security/two-factor/security-keys.rst:34 +msgid "" +"Now the users will be able to set up this two-factor authentication method " +"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " +"Once they do, on next sign-in with password, they will be asked to provide " +"the same security key they registered during the setup." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:151 -msgid "created_by_id" +#: ../settings/system/system-selfhosted.include.rst:3 +msgid "" +"Below settings are only available to self hosted users. In hosted " +"environments we're handling these settings for you to ensure service " +"stability." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:152 -msgid "updated_by_id" +#: ../settings/system/base.rst:11 +msgid "Fully Qualified Domain Name" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:155 -msgid "Which Values Can Be Set?" +#: ../settings/system/base.rst:7 +msgid "The URL of your Zammad installation." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:157 -msgid "😵 **Invalid values → unpredictable behavior**" +#: ../settings/system/base.rst:9 ../settings/system/base.rst:17 +msgid "This setting is used within :doc:`/misc/variables` and notifications." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:159 -msgid "" -"If you provide a value that Zammad doesn't understand (*e.g.,* ``-F " -"\"priority=high\"``), it's not always clear what will happen. In some cases, " -"a ticket will be created with the default values instead - but in others, it " -"may not be created at all!" +#: ../settings/system/system-base.include.rst:1 +msgid "It is automatically set by the *Getting Started wizard*." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:164 -msgid "So what values does Zammad understand, then? Well, it depends..." +#: ../settings/system/system-base.include.rst:5 +msgid "Changing this setting also changes callback URLs for your channels etc." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:168 -msgid "Use an email address or username:" +#: ../settings/system/system-base.include.rst:6 +msgid "This setting can have negative affects on being able to login." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:190 -msgid "group & priority" +#: ../settings/system/base.rst:19 +msgid "HTTP type" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:175 -msgid "Refer to the dropdown menus in the ticket pane:" +#: ../settings/system/base.rst:14 +msgid "" +"The HTTP type tells your installation how your clients connect. This is " +"relevant for authentication and cookie security." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:0 -msgid "See possible values for certain attributes in the ticket pane." +#: ../settings/system/base.rst:31 +msgid "SystemID" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:187 -msgid "🙅 **Ticket state CANNOT be set this way!**" +#: ../settings/system/base.rst:22 +msgid "" +"This ID is being used within your ticket number. In case you're " +"communicating with another ticket system with similar ticket number schemes " +"this ID greatly reduces the risk of false follow ups." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:189 +#: ../settings/system/base.rst:26 msgid "" -"Why? Because ``-F \"state=...\"`` is already used :ref:`as a Checkmk " -"parameter `." +"The SystemID is randomly selected upon installation of Zammad (``1-99``)." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:222 -msgid "Everything Else" +#: ../settings/system/base.rst:30 +msgid "" +"**Do not** change this setting in a productive system! Your Zammad " +"installation may no longer recognize old ticket number based follow ups upon " +"change!" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:193 -msgid "" -"To set any other attributes, it helps to know your way around the :docs:" -"`rails console `. Valid values are those that you can " -"set with a string:" +#: ../settings/system/frontend.rst:2 +msgid "Frontend" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:218 -msgid "These values can then be passed directly to the API:" +#: ../settings/system/frontend.rst:22 +msgid "Core Workflow Ajax Mode" msgstr "" -#: ../system/integrations/checkmk/index.rst:16 -msgid "How does it work?" +#: ../settings/system/frontend.rst:6 +msgid "" +"This setting allows administrators to enforce :doc:`/system/core-workflows` " +"to use Ajax-Calls instead of web sockets. You'll usually only need this if " +"you experience serious issues as noted below." msgstr "" -#: ../system/integrations/checkmk/index.rst:2 -msgid "Checkmk" +#: ../settings/system/frontend.rst:10 +msgid "**🤓 Possible (technical) reasons**" msgstr "" -#: ../system/integrations/checkmk/index.rst:4 +#: ../settings/system/frontend.rst:12 msgid "" -"`Checkmk `_ is a powerful IT monitoring tool that can " -"send real-time status alerts to Zammad via email or REST API. Set these " -"alerts up in Checkmk, and Zammad will automatically create, update, and " -"close tickets based on the health of your system:" +"In some cases, your network structure (e.g. firewalls, proxies) may " +"disconnect long web socket connections. This leads to select fields staying " +"empty (e.g. owner selection *after* selecting your group) or fields not " +"shown / hidden (e.g. when switching to or from pending states, the \"pending " +"till\" field not showing / hiding)." msgstr "" -#: ../system/integrations/checkmk/index.rst:14 -msgid "Screenshot of ticket created by Checkmk notifications" +#: ../settings/system/frontend.rst:18 +msgid "" +"Please keep in mind that the Ajax fallback may cause serious pressure on " +"your application server. If you have the choice stick to web sockets." msgstr "" -#: ../system/integrations/checkmk/index.rst:14 -msgid "Multiple alerts, same ticket." +#: ../settings/system/frontend.rst:22 +msgid "Default: ``no`` (inactive)" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:2 -msgid "Setup Guide" +#: ../settings/system/frontend.rst:53 +msgid "Show calendar weeks in the picker of date/datetime fields" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:4 +#: ../settings/system/frontend.rst:25 msgid "" -"Whenever the Checkmk integration is enabled, Zammad listens for messages on " -"its API and over email. As long as those messages follow the required " -"format, Zammad will create new tickets (or find and update existing ones) " -"based on the message contents." +"With this setting you can instruct Zammad to provide week number display " +"globally for all users. Calendar with week number display are usually used " +"in business sectors and may not be relevant for everyone." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:10 +#: ../settings/system/frontend.rst:29 msgid "" -"That means that “setting up Checkmk integration” is simply a matter of " -"**adding configuration to your Checkmk site**: telling it when to send these " -"messages and what to say. To do that, you'll need to create a new " -"**notification rule** (see `Checkmk's official docs `_ for help with that)." +"This setting affects *all areas* - you'll also see week numbers in the admin " +"panel for e.g. triggers and macros." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:17 -msgid "" -"As part of this new rule, you'll have to choose a **notification method** " -"(*i.e.,* a script to execute whenever the rule is triggered). This script " -"will be written by you (samples below), and contain the logic for sending " -"API/email messages to Zammad:" +#: ../settings/system/frontend.rst:32 +msgid "Default: ``no`` (not shown)" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:26 -msgid "Checkmk \"New Rule\" dialog" +#: ../settings/system/frontend.rst:53 +msgid "Here's the difference:" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:26 -msgid "" -"Find your custom scripts in the Checkmk WATO under **Notifications > New " -"Rule > Notification Method**." +#: ../settings/system/frontend.rst:0 +msgid "Screenshot showing Zammad's date picker (in the default way)" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:29 -msgid "" -"Once you're done setting up your new rule, you're all set! New tickets " -"should start coming in and auto-updating any time your rule is triggered." +#: ../settings/system/frontend.rst:41 +msgid "Set to ``no``" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:33 +#: ../settings/system/frontend.rst:0 msgid "" -"(If you need help troubleshooting, be sure to check the :ref:`checkmk-recent-" -"logs`.)" +"Screenshot showing Zammad's date picker with\n" +"week numbers enabled" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:38 -msgid "API Alerts" +#: ../settings/system/frontend.rst:50 +msgid "Set to ``yes``" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:40 +#: ../settings/system/index.rst:4 msgid "" -"To add these scripts in the Checkmk WATO, copy them into your Checkmk " -"installation directory and make them executable. (Be sure to replace the " -"``zammad.example.com`` callback URL with the one found in your admin panel.)" +"For your overview we split each tab within system settings into its own page:" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:60 -msgid "Service notification" +#: ../settings/system/index.rst:16 +msgid "Console Based Settings" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:46 +#: ../settings/system/index.rst:18 msgid "" -"For updates on the status of the software running on your server (*e.g.,* " -"postgres)." +"There's some console based settings we didn't put into the UI. However, you " +"may find them helpful - you can find them in our :docs:`hidden settings ` section." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:75 -msgid "Host notification" +#: ../settings/system/network.rst:2 +msgid "Network" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:63 -msgid "For updates on the status of the server itself." +#: ../settings/system/network.rst:8 +msgid "" +"The proxy settings can only be saved after successfully testing the proxy " +"connection." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:77 -msgid "🤔 **What's with all the env vars?**" +#: ../settings/system/network.rst:15 +msgid "Proxy Address." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:79 +#: ../settings/system/network.rst:12 msgid "" -"Whenever Checkmk runs these scripts, it needs to provide some information " -"about the event that triggered the notification. This information is passed " -"in the form of these ``$NOTIFY_*`` environment variables." +"Allows you to provide a proxy server if needed. This is relevant for network " +"communication by Zammad." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:85 -msgid "" -"You can specify additional parameters to pass to the script when you're " -"setting up your notification rule, but the ones you see here are all " -"provided by default." +#: ../settings/system/network.rst:15 +msgid "It **does not** affect the update process or Elasticsearch." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:90 -msgid "Email Alerts" +#: ../settings/system/network.rst:18 +msgid "Username for proxy connection." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:94 +#: ../settings/system/network.rst:18 msgid "" -"🐞 **There are known bugs** in Zammad's processing of email from Checkmk. " -"This section will be completed once they have been resolved. (Learn more at " -"GitHub issues `#2377 `_ & " -"`#2180 `_.)" +"If your proxy server requires authentication, provide the username here." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:100 -msgid "In the meantime, we encourage you to set up API alerts instead." +#: ../settings/system/network.rst:21 +msgid "Password for proxy connection." msgstr "" -#: ../system/integrations/clearbit.rst:2 -msgid "Clearbit" +#: ../settings/system/network.rst:21 +msgid "" +"If your proxy server requires authentication, provide the password here." msgstr "" -#: ../system/integrations/clearbit.rst:4 +#: ../settings/system/network.rst:26 +msgid "No proxy for the following hosts." +msgstr "" + +#: ../settings/system/network.rst:24 msgid "" -"With our Clearbit integration, you can easily enrich the information " -"provided by Zammad. If the customers or agents email address is known to " -"Clearbit, it will share all information it has regarding the user with " -"Zammad. Those information can include the following:" +"Exception list for hosts you can't or don't want to reach via proxy server." msgstr "" -#: ../system/integrations/clearbit.rst:9 -msgid "Avatar" +#: ../settings/system/network.rst:27 +msgid "Default: ``localhost,127.0.0.0,::1``" msgstr "" -#: ../system/integrations/clearbit.rst:10 -msgid "Address information" +#: ../settings/system/services.rst:2 +msgid "Services" msgstr "" -#: ../system/integrations/clearbit.rst:11 -msgid "Website information" +#: ../settings/system/services.rst:10 +msgid "Image Service" msgstr "" -#: ../system/integrations/clearbit.rst:12 -msgid "A BIO (as Note by default)" +#: ../settings/system/services.rst:5 +msgid "Defines the backend for user and organization image lookups." msgstr "" -#: ../system/integrations/clearbit.rst:14 -msgid "" -"If needed, you can add further custom objects and add mappings to them, so " -"the Clearbit information can be filled within the database. In general you " -"can get any information from Clearbit, as long as you have a mapping to an " -"Zammad object." +#: ../settings/system/services.rst:7 +msgid "Default: ``Zammad Image Service`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:21 +#: ../settings/system/services.rst:9 msgid "" -"Clearbit does have a mapping of fields like LDAP and Exchange have, but does " -"not \"win\" against Zammad information. This means that if you have e.g. the " -"last name field filled in already and Clearbit has other information on " -"that, it will not be updated." +"Make sure your on premise installation has ``HTTPS`` access to ``images." +"zammad.com``." msgstr "" -#: ../system/integrations/clearbit.rst:26 -msgid "" -"However: If let's say the last name has been set by Clearbit and Zammad " -"notices that the last name on the Clearbit source has changed, Zammad will " -"also update this value." +#: ../settings/system/services.rst:18 +msgid "Geo Calendar Service" msgstr "" -#: ../system/integrations/clearbit.rst:33 +#: ../settings/system/services.rst:13 msgid "" -"The configuration of Clearbit is really easy and done fast! Just login to " -"your Clearbit-Account, go to \"API\" and copy the secret-API-Key." +"Defines the backend for geo calendar lookups. Used for initial calendar " +"setup." msgstr "" -#: ../system/integrations/clearbit.rst:38 -msgid "" -"Now change to your Zammad instance, go to Integrations (System) -> Clearbit " -"in the admin panel. Paste your API-Key into the API-Key-Field and decide if " -"Zammad should create unknown Organizations automatically, if the user does " -"not have one yet (and Clearbit knows it). The shared option decides if the " -"new organizations Zammad creates with Clearbit should be shared ones." +#: ../settings/system/services.rst:16 +msgid "Default: ``Zammad GeoCalendar Service`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:47 +#: ../settings/system/services.include.rst:2 msgid "" -"If you're unsure what option to choose, better stick with \"no\". You can " -"also learn more about :doc:`/manage/organizations/index`." +"Make sure your on premise installation has ``HTTPS`` access to ``geo.zammad." +"com``." msgstr "" -#: ../system/integrations/clearbit.rst:52 -msgid "" -"The Mapping option works similar to the mapping within the Exchange and LDAP " -"sync. You can add further mappings for e.g. custom fields if you need more " -"information that Clearbit can provide." +#: ../settings/system/services.rst:26 +msgid "Geo IP Service" msgstr "" -#: ../system/integrations/clearbit.rst:58 +#: ../settings/system/services.rst:21 msgid "" -"If you want to add more Clearbit fields and want to learn more about " -"available fields on their API, you can take a look at their `API " -"documentation `_." +"Defines the backend for geo IP lookups. Shows also location of an IP address " +"if an IP address is shown." msgstr "" -#: ../system/integrations/clearbit.rst:62 -msgid "" -"If you're happy with the above chosen Settings and your mapping, just save " -"the changes and enable Clearbit integration. Zammad will now start polling " -"the Clearbit API as users contact you." +#: ../settings/system/services.rst:24 +msgid "Default: ``Zammad GeoIP Service`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:68 -msgid "" -"Zammad does not synchronize with Clearbit on a regular basis, but on demand " -"if needed. This saves API calls." +#: ../settings/system/services.rst:32 +msgid "Geo Location Service" msgstr "" -#: ../system/integrations/clearbit.rst:73 +#: ../settings/system/services.rst:29 msgid "" -"Below the Settings and Mappings, you'll find our Integration log. You can " -"see what requests Zammad sent to Clearbit and also the APIs Response." +"Defines the backend for geo location lookups to store geo locations for " +"addresses." msgstr "" -#: ../system/integrations/clearbit.rst:78 +#: ../settings/system/services.rst:32 msgid "" -"By the way, you can also view the API log on the Clearbit website - the " -"information seen is basically the same." -msgstr "" - -#: ../system/integrations/clearbit.rst:84 -msgid "Example When Adding a User" +"Default: ``OpenStreetMap (ODbL 1.0, http://osm.org/copyright)`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:86 +#: ../settings/system/services.rst:36 msgid "" -"To show you how fast information is added, we added a small Screencast " -"below. This shows the creation of the User Alex from Clearbit. As we already " -"set the last name of Alex to \"X\", Zammad did not update it. What Zammad " -"did was to add further information it received from Clearbit." +"You can find a detailed privacy information on what we store for how long on " +"our :docs:`Privacy Appendix ` inside of our System " +"Documentation." msgstr "" -#: ../system/integrations/cti/generic.rst:2 -msgid "CTI (generic)" +#: ../settings/system/storage.rst:2 +msgid "Storage" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:1 +#: ../settings/system/storage.rst:6 msgid "" -"This integration enables Zammad to provide a caller log to your agents. With " -"this your agents can greet your customers by their name and are supported by " -"Zammad with automatically opening a new ticket dialog or the user profile." +"Here you can define where Zammad stores attachments for tickets and the " +"knowledge base. By default, we're writing to the ``Database`` - you can " +"switch to ``Filesystem`` or ``Simple Storage (S3)`` at any time. In this " +"case please have a look on the following instructions." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:6 +#: ../settings/system/storage.rst:11 msgid "" -"Click the toggle next to the heading to activate or deactivate this " -"integration." +"If you have a busy Zammad instance, we strongly encourage you to use " +"filesystem storage instead of \"Database\". This will greatly improve system " +"performance (de-crease database load and size)." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:9 -msgid "" -"If you want to learn more on how your agents can use this function, please " -"refer the :user-docs:`user documentation `." +#: ../settings/system/storage.rst:19 +msgid "Database" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:14 +#: ../settings/system/storage.rst:17 msgid "" -"Automatically opening new ticket dialogues or user profiles requires agent " -"to extension mapping - see more below." -msgstr "" - -#: ../system/integrations/cti/includes/introduction.include.rst:20 -msgid "Please note the following limitations to reduce confusion later on:" +"This is the default storage method. The attachments are stored directly in " +"the database. If your Zammad instance grows, we recommend one of the other " +"methods to maintain performance." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:22 -msgid "CTI integrations provide caller log functions only." +#: ../settings/system/storage.rst:38 +msgid "Filesystem" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:23 +#: ../settings/system/storage.rst:22 msgid "" -"This integration does not provide any VoIP functionalities; you can't make " -"phone calls from within Zammad." +"This storage method is recommended for all Zammad instances, especially for " +"those with a higher load. If you choose filesystem, your files are written " +"to ``/opt/zammad/storage/``." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:25 +#: ../settings/system/storage.rst:26 msgid "" -"If your browser supports ``tel``-URLs, you can click on phone numbers for " -"automatic dialing. This requires additional software / configuration on your " -"agent's computers." +"Moving attachments from \"Database\" to \"Filesystem\" can be run during " +"production use. However, you should consider your framework conditions (e.g. " +"bandwidth, system load in production) to define the right moment." msgstr "" -#: ../system/integrations/cti/generic.rst:9 -#: ../system/integrations/cti/placetel.rst:14 -#: ../system/integrations/cti/sipgate.rst:14 -msgid "Please provide the following requirements:" +#: ../settings/system/storage.rst:32 +msgid "**You noticed slow updates of Zammad?**" msgstr "" -#: ../system/integrations/cti/generic.rst:11 +#: ../settings/system/storage.rst:34 msgid "" -"A telephone system that supports webhooks (outbound) (best option are those " -"that allow customizing the calls)." +"While Zammad is beeing updated, it enforces a recursive \"change " +"owner\" (chown) for this directory. For instances with many files this can " +"be time consuming. To mitigate that you can move your files and create a " +"symlink in ``/opt/zammad/storage/`` to the new directory. Of course you have " +"to make sure on your own that the permissions are always correct." msgstr "" -#: ../system/integrations/cti/generic.rst:13 -msgid "A unique Call-ID during the call session." +#: ../settings/system/storage.rst:95 +msgid "Simple Storage (S3)" msgstr "" -#: ../system/integrations/cti/generic.rst:14 -msgid "Call event data (both numbers and direction)." +#: ../settings/system/storage.rst:41 +msgid "" +"To use the Simple Storage (S3), you have to provide some settings, which " +"can't be accessed in the UI (see instructions below)." msgstr "" -#: ../system/integrations/cti/generic.rst:15 -msgid "Your Zammad instance must be reachable for your telephony system." +#: ../settings/system/storage.rst:44 +msgid "" +"⚠️ Please note that the current implementation is in its early stages and can " +"be modified in the future." msgstr "" -#: ../system/integrations/cti/generic.rst:17 +#: ../settings/system/storage.rst:47 msgid "" -"If you want to learn more on what kind of requests are supported by Zammad " -"and what it expects, please consult our :docs:`CTI-API documentation `." +"The prerequisite is to have access to a S3-compatible storage and to have " +"all necessary parameters available (which depends on your storage provider; " +"if in doubt, please ask there for help)." msgstr "" -#: ../system/integrations/cti/generic.rst:22 -#: ../system/integrations/cti/placetel.rst:27 -#: ../system/integrations/cti/sipgate.rst:30 -msgid "Available Settings" +#: ../settings/system/storage.rst:51 +msgid "Steps to configure S3:" msgstr "" -#: ../system/integrations/cti/generic.rst:29 -#: ../system/integrations/cti/placetel.rst:41 -#: ../system/integrations/cti/sipgate.rst:40 -msgid "Endpoint Settings" +#: ../settings/system/storage.rst:53 +msgid "" +"Copy ``config/zammad/storage.yml.dist`` to ``config/zammad/storage.yml``" msgstr "" -#: ../system/integrations/cti/generic.rst:25 -msgid "" -"Zammad will list your generic CTI endpoint here. It contains a unique token " -"so ensure to keep this URL save." +#: ../settings/system/storage.rst:54 +msgid "Edit the copied file in one of the following ways:" msgstr "" -#: ../system/integrations/cti/generic.rst:28 +#: ../settings/system/storage.rst:56 msgid "" -"You'll need this endpoint for your PBX to talk to Zammad, see :docs:`CTI-API " -"documentation `." +"Either provide your S3 configuration with one attribute per line like in the " +"upper area of the file" msgstr "" -#: ../system/integrations/cti/includes/important-dont-forget-saving.include.rst:3 +#: ../settings/system/storage.rst:58 msgid "" -"All following options **do not save automatically**. Always use the Save " -"button on the lower end of the integration page!" +"Or provide your S3 configuration as an URL (which you can find at the end of " +"the file). Note: you can also provide this URL as environment variable (:" +"docs:`see system documentation `) without using this yml-file." msgstr "" -#: ../system/integrations/cti/generic.rst:43 -#: ../system/integrations/cti/placetel.rst:49 -#: ../system/integrations/cti/sipgate.rst:52 -msgid "Call Settings" +#: ../settings/system/storage.rst:62 +msgid "" +"We recommend the deletion of the not used configuration style to avoid " +"inconsistencies." msgstr "" -#: ../system/integrations/cti/generic.rst:39 -#: ../system/integrations/cti/placetel.rst:49 -#: ../system/integrations/cti/sipgate.rst:37 -#: ../system/integrations/cti/sipgate.rst:50 -msgid "Inbound" +#: ../settings/system/storage.rst:65 +msgid "Restart Zammad so the config file / environment variable is loaded" msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:1 +#: ../settings/system/storage.rst:66 msgid "" -"This option allows you to block specific incoming caller IDs. It allows you " -"to temporarily reject e.g. spam callers without having to contact providers " -"or PBX administrators." +"Set the \"Storage Method\" in Zammad to ``Simple Storage (S3)`` in Settings " +"> System > Storage and click on \"Submit\". After that, Zammad checks your " +"configuration and the connection to the service and will raise an error " +"message if something is wrong." msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:11 -msgid "Caller ID to block" +#: ../settings/system/storage.rst:72 +msgid "A very simple storage configuration could look like this:" msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 -msgid "Provide caller IDs to block in ``E.164`` format." +#: ../settings/system/storage.rst:85 +msgid "" +"Before setting the storage method to ``Simple Storage (S3)`` (step 4), " +"please make sure to have a working setup." msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:8 +#: ../settings/system/storage.rst:88 msgid "" -"Your telephony system has to support this function. Zammad will send a " -"``reject`` response which will cause your telephony system to hang up the " -"call. To callers this usually will feel like the line is busy." +"You can verify this by running ``rails r 'Rails.logger = Logger.new(STDOUT); " +"pp Store::Provider::S3.ping?'`` in your Zammad directory. If everything is " +"fine, you should see ``true``, else you should see ``false`` and a simple " +"error message." msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:14 +#: ../settings/system/storage.rst:93 msgid "" -"Provide a meaningful note for your fellow administrators to remind yourself " -"why you've chosen to block the number." +"If you installed Zammad through a package manager (rather than from source), " +"replace ``rails r`` with ``zammad run rails r`` above. To learn more, see :" +"docs:`Administration via Console `." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 -#: ../system/integrations/cti/includes/outbound-calls.include.rst:17 -#: ../system/integrations/cti/sipgate.rst:40 -msgid "Outbound" +#: ../settings/ticket.rst:4 +msgid "" +"Here you can adjust general ticket settings. Additional ones for the ticket " +"composer interface can be found in the :doc:`/misc/composer`." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:1 -msgid "" -"In many cases you may want to use a different caller ID depending on the " -"destination you're calling. This may apply due to specific connection rates " -"to other countries or because you want your customer to feel you're calling " -"from the same country." +#: ../settings/ticket.rst:11 +msgid "Ticket Hook (default: ``Ticket#``)" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:6 -msgid "This option expects ``E.164`` number formats." +#: ../settings/ticket.rst:11 +msgid "The identifier for a ticket; *e.g.,* Ticket#, Call#, MyTicket#." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 -msgid "Destination caller ID" +#: ../settings/ticket.rst:38 +msgid "Ticket Hook Position (default: ``right``)" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:5 -msgid "The caller ID or number you're trying to call." +#: ../settings/ticket.rst:14 +msgid "" +"With this setting you can decide (if) where to insert the ticket number." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:7 -msgid "You can use wildcards for e.g. country specific outbound numbers like:" +#: ../settings/ticket.rst:20 +msgid "*Right*" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:9 -msgid "``49*`` for Germany" +#: ../settings/ticket.rst:17 +msgid "" +"This setting will add the ticket reference on the right site of the subject." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:10 -msgid "``4930*`` for Berlin / Germany landlines" +#: ../settings/ticket.rst:20 +msgid "Example: ``Some Subject [Ticket#12345]``" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 -msgid "``33*`` for France" +#: ../settings/ticket.rst:26 +msgid "*Left*" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:15 -msgid "Set Outbound caller ID" +#: ../settings/ticket.rst:23 +msgid "" +"This setting will add the ticket reference on the left site of the subject." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:14 -msgid "" -"The outbound caller ID to set (the number your customer sees on his display) " -"in ``E.164`` number format." +#: ../settings/ticket.rst:26 +msgid "Example: ``[Ticket#12345] Some Subject``" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 -msgid "Provide a short description for fellow administrators." +#: ../settings/ticket.rst:29 +msgid "*None*" msgstr "" -#: ../system/integrations/cti/includes/generic-cti-support-note.includes.rst:3 -msgid "" -"This option requires your PBX to send a specific request to Zammad *before " -"dialing*. Please consult the :docs:`CTI API ` in case " -"you're not sure." +#: ../settings/ticket.rst:29 +msgid "This will completely remove ticket references from the subject." msgstr "" -#: ../system/integrations/cti/generic.rst:52 -#: ../system/integrations/cti/placetel.rst:54 -#: ../system/integrations/cti/sipgate.rst:59 -msgid "Other Settings" +#: ../settings/ticket.rst:33 +msgid "" +"Please ensure to take a look at :doc:`/channels/email/settings` within the " +"email channel to ensure you have at least one reference that helps Zammad to " +"assign follow-ups correctly." msgstr "" -#: ../system/integrations/cti/includes/other-settings-intro.include.rst:1 +#: ../settings/ticket.rst:37 msgid "" -"Below you can find all available additional settings for this CTI " -"integration. For your overview we're sorting them by appearance and " -"reference their description first." +"Disabling this and not setting up any further follow up search will lead to " +"unexpected results!" msgstr "" -#: ../system/integrations/cti/includes/default-caller-id.include.rst:2 -#: ../system/integrations/cti/includes/default-caller-id.include.rst:1 -msgid "Default caller ID for outbound calls" +#: ../settings/ticket.rst:65 +msgid "" +"Ticket Last Contact Behaviour (default: ``Use the start time of the last " +"customer thread (which may consist of multiple articles).``)" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:16 -#: ../system/integrations/cti/includes/records-caller-log.include.rst:15 -msgid "Shown records in caller log" +#: ../settings/ticket.rst:41 +msgid "" +"This setting changes the way Zammad updates the ``Last Contact`` value of a " +"ticket. This is fairly important for overviews and what you expect upon " +"ticket updates of a customer." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:2 +#: ../settings/ticket.rst:52 msgid "" -"Allows you to set the number of shown caller log entries for all users. You " -"can choose from the following values:" +"Use the start time of the last customer thread (which may consist of " +"multiple articles)." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:5 -msgid "60 (default)" +#: ../settings/ticket.rst:46 +msgid "" +"If this option is chosen, Zammad will update the last updated value just " +"once if a customer replies. After that, Zammad will wait for an agent to " +"react." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:6 -msgid "120" +#: ../settings/ticket.rst:50 +msgid "" +"This comes in handy if you want to work tickets in the order of their first " +"update. This will not change ticket orders if customers decide to \"bump\" " +"the ticket affected." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:7 -msgid "180" +#: ../settings/ticket.rst:57 +msgid "Use the time of the very last customer article." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:8 -msgid "240" +#: ../settings/ticket.rst:55 +msgid "" +"When setting this option, Zammad will always update the last updated value. " +"This means that if ordering by ``Last Update``, ticket orders will change if " +"customers \"bump\" the ticket." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:9 -msgid "300" +#: ../settings/ticket.rst:64 +msgid "Last contact value used on :doc:`/manage/overviews`" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:11 -msgid "**🥵 Potential performance issue**" +#: ../settings/ticket.rst:65 +msgid "Last contact value used on :doc:`/manage/trigger`" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:13 +#: ../settings/ticket.rst:88 msgid "" -"Setting this setting higher than 60 may cause serious performance issues on " -"very busy instances. Keep in mind that this setting causes Zammad to poll " -"and send up to 300 records to *all active agent sessions* in very short time " -"periods." +"Ticket Organization Reassignment (default: ``Update the most recent tickets." +"``)" msgstr "" -#: ../system/integrations/cti/generic.rst:73 -msgid "Caller Log Filter" +#: ../settings/ticket.rst:68 +msgid "" +"This setting changes the way Zammad updates the organization field of the " +"tickets whenever the primary organization of a user is changed." msgstr "" -#: ../system/integrations/cti/generic.rst:55 -msgid "" -"This function allows you to provide call information based on e.g. queues " -"only to agents that really need the information." +#: ../settings/ticket.rst:74 +msgid "Update the most recent tickets." msgstr "" -#: ../system/integrations/cti/generic.rst:58 +#: ../settings/ticket.rst:72 msgid "" -"Why? If you have a team for several countries or departments, you don't want " -"to bug your agents from other departments. Leaving these options empty will " -"fallback to showing everything to everyone." +"If this option is chosen, Zammad will update the 100 most recent tickets " +"where the user is the ticket customer. The ticket organization field will be " +"automatically set to the new primary organization of the user." msgstr "" -#: ../system/integrations/cti/generic.rst:64 -msgid "Destination caller ID or Queue" +#: ../settings/ticket.rst:88 +msgid "Do not update any tickets." msgstr "" -#: ../system/integrations/cti/generic.rst:63 +#: ../settings/ticket.rst:77 msgid "" -"This depends on your PBX and usually is either a queue ID, phone number or " -"extension." +"When choosing this option, Zammad will not update any tickets when the " +"user's primary organization is changed." msgstr "" -#: ../system/integrations/cti/generic.rst:69 -msgid "Agents" +#: ../settings/ticket.rst:80 +msgid "**Use with care!**" msgstr "" -#: ../system/integrations/cti/generic.rst:67 +#: ../settings/ticket.rst:82 msgid "" -"Select the agents that are responsible for the group. These agents will then " -"see caller log entries and call notifications fitting to said queue." +"Using this option may lead to inconsistencies in the system as the ticket " +"organization may become decoupled from the ticket customer." msgstr "" -#: ../system/integrations/cti/generic.rst:0 +#: ../settings/ticket.rst:85 msgid "" -"Screenshot showing the caller log filter table with pre filled sample data" +"However, you may use this option if you wish to maintain :ref:`the shared " +"access ` to the ticket for all organization " +"members of the original organization of the customer." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:6 -msgid "" -"With recent logs Zammad allows you to view the latest calls for the CTI " -"functionality. This usually comes in handy, when you're looking for errors." +#: ../settings/ticket.rst:110 +msgid "Ticket Number Format (default: ``Increment (SystemID.Counter)``)" msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:0 +#: ../settings/ticket.rst:94 msgid "" -"Screenshot showing several incoming requests within Recent logs section." +"This setting defines the way Zammad's ticket number will look. Changing this " +"setting in production will cause follow up detection to fail." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:16 -msgid "I'm just here to clear floats up." +#: ../settings/ticket.rst:102 +msgid "Increment (SystemID.Counter)" msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:20 +#: ../settings/ticket.rst:98 msgid "" -"By clicking on the entry of interest, Zammad will provide more details on " -"the call in question. You'll see the payload it received and also the " -"response that was sent." +"The increment value contains the SystemID (automatically generated during " +"installation) and a increment which counts up with every new Ticket. The " +"increment will automatically get another digit if needed." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:0 -msgid "" -"Screenshot showing detailed information of a specific log entry of recent " -"logs" +#: ../settings/ticket.rst:102 +msgid "Examples: ``1010138``, ``1010139``" msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:31 -msgid "x" +#: ../settings/ticket.rst:110 +msgid "Date (Year.Month.Day.SystemID.Counter)" msgstr "" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 -#: ../system/integrations/cti/includes/troubleshooting.include.rst:9 -msgid "My Phone page stays blank, signalling does work..." +#: ../settings/ticket.rst:105 +msgid "" +"This version of the ticket number is fairly long. However, because it " +"contains the date of ticket creation, it also allows you to see when the " +"ticket has been created. You may feel familiar with this number format if " +"you've worked with OTRS already." msgstr "" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:5 -msgid "" -"If you've made sure that signalling works (check Recent logs) and your " -"Caller Log still stays empty, please ensure that you only configured one CTI " -"integration version. Specifically defining more than one agent mapping on " -"the different integration variants will be the issue." +#: ../settings/ticket.rst:110 +msgid "Examples: ``201206231010138``, ``201206231010139``" msgstr "" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 -msgid "Clear the not needed agent mapping and reload your browser page." +#: ../settings/ticket.rst:137 +msgid "OPTIONS" msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:1 +#: ../settings/ticket.rst:113 msgid "" -"By mapping your agents extension to their existing Zammad users, Zammad can " -"provide a new ticket dialog or open the user profile for the agent that " -"picks up the call." +"The below options allow you to further customize your ticket number. The " +"availability of options differ depending of the chosen ticket number format " +"above." msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:5 -msgid "" -"This speeds up ticket aiding, no matter if it's for existing tickets or new " -"ones!" +#: ../settings/ticket.rst:122 +msgid "Checksum (default: ``no``)" msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:8 +#: ../settings/ticket.rst:118 msgid "" -"To see it work from the agent's perspective, have a look on :user-docs:`user " -"documentation `." +"If set to yes, we'll built a checksum to further \"unique\" the ticket " +"number of your system. If you're dealing with many other ticket systems this " +"might help to prevent false positive follow up detection on tickets." msgstr "" -#: ../system/integrations/cti/placetel.rst:2 -msgid "Placetel CTI" +#: ../settings/ticket.rst:122 +msgid "This will also add another digit to the ticket number." msgstr "" -#: ../system/integrations/cti/placetel.rst:16 -msgid "You need an administrative Placetel account for your organization." +#: ../settings/ticket.rst:137 +msgid "Min. size of Number (default: ``5``)" msgstr "" -#: ../system/integrations/cti/placetel.rst:17 -#: ../system/integrations/cti/sipgate.rst:20 +#: ../settings/ticket.rst:125 msgid "" -"Your Zammad instance must be allowed to communicate to external services." +"This setting defines the minimum length of your ticket number. If your " +"counter is not yet high enough, Zammad will fill the number with zeros to " +"ensure the wanted length." msgstr "" -#: ../system/integrations/cti/placetel.rst:18 -msgid "Placetel must be able to reach your Zammad instance." -msgstr "" - -#: ../system/integrations/cti/placetel.rst:22 -msgid ":doc:`provider-configurations/placetel`" -msgstr "" - -#: ../system/integrations/cti/placetel.rst:21 +#: ../settings/ticket.rst:129 msgid "" -"Learn how to configure Placetel to enable Zammad and Placetel to communicate " -"with each other." +"Please note that the minimum length is ``3`` (SystemID + at least one digit " +"if below 10). Also, if the length is no longer long enough, the number will " +"automatically get one digit longer. Ticket-Numbers **do not overflow**, thus " +"it's save to keep it at 5 or set it lower if wanted." msgstr "" -#: ../system/integrations/cti/placetel.rst:32 +#: ../settings/ticket.rst:135 msgid "" -"The here listed endpoint settings are relevant for the :doc:`integration " -"configuration with Placetel `." +"This option is only available if ticket number format is set to " +"``Increment``!" msgstr "" -#: ../system/integrations/cti/placetel.rst:37 -#: ../system/integrations/i-doit.rst:53 -msgid "Endpoint" +#: ../settings/ticket.rst:142 +msgid "Auto-Assignment" msgstr "" -#: ../system/integrations/cti/placetel.rst:36 +#: ../settings/ticket.rst:144 msgid "" -"This endpoint will be required for the Zammad integration within the " -"Placetel web interface." -msgstr "" - -#: ../system/integrations/cti/placetel.rst:41 -msgid "API Token" +"In a larger Zammad environment, it happens that several agents open the same " +"ticket at the same time. Although collision detection is then effective, the " +"efficiency of processing can be increased by means of the automatic " +"assignment of tickets when a ticket is opened." msgstr "" -#: ../system/integrations/cti/placetel.rst:40 +#: ../settings/ticket.rst:149 msgid "" -"You'll receive this token within the ``Web API`` menu. Make sure to copy " -"this value, it's only shown once!" -msgstr "" - -#: ../system/integrations/cti/placetel.rst:71 -#: ../system/integrations/cti/sipgate.rst:77 -msgid "Phone Extension to Agent Mapping" +"The automatic assignment of tickets can be activated and configured in the " +"admin area under Settings > Ticket > Auto Assignment." msgstr "" -#: ../system/integrations/cti/placetel.rst:0 -msgid "Screenshot showing sample user mappings in between Placetel and Zammad" +#: ../settings/ticket.rst:152 +msgid "" +"The auto assignment only works if the ticket has no owner yet. By default, " +"the agent can always reset the ticket owner to ``-`` if needed." msgstr "" -#: ../system/integrations/cti/placetel.rst:64 +#: ../settings/ticket.rst:155 msgid "" -"You can find your agents Placetel username combination required within ⚙️ PBX " -"→ VoIP destinations. Within the \"Advanced settings\" section you're looking " -"for \"SIP user name\" and \"SIP server\"." +"If you want to use this function for only specific tickets, you can " +"configure the conditions accordingly to meet your requirement. By default " +"the condition affects all tickets with the state ``open``." msgstr "" -#: ../system/integrations/cti/placetel.rst:68 -msgid "Combine these two like so: ``@``." +#: ../settings/ticket.rst:161 +msgid "" +"If you need to exclude users (e.g. a group leader), you can search and " +"select the desired agents in the ``Exception Users`` list. The search " +"function in this area is only effective, if you have too many agents to " +"display at once to help you with the configuration." msgstr "" -#: ../system/integrations/cti/placetel.rst:0 -msgid "Sample VoIP credentials for a Placetel user" +#: ../settings/ticket.rst:167 +msgid "Notifications" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:2 -msgid "Setup Placetel connection for Zammad" +#: ../settings/ticket.rst:191 +msgid "Default Notifications" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:6 +#: ../settings/ticket.rst:170 msgid "" -"This configuration step requires a *full* administrative Placetel account. " -"You may receive forbidden error messages with Placetel in case your " -"permissions are not high enough." +"This setting allows you to configure the default ticket notifications that " +"will be applied to all new agent users (incl. users who were just assigned " +"agent role). Simply change the notification matrix to desired state and " +"press **Save**." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:10 +#: ../settings/ticket.rst:175 msgid "" -"The following actions can be configured via the `Placetel web interface " -"`_." -msgstr "" - -#: ../system/integrations/cti/provider-configurations/placetel.rst:29 -msgid "Step 1: Activate Zammad integration" +"In case an agent already exists, their ticket notification preferences will " +"be preserved. Optionally, you can also **Apply current defaults to all " +"agents**." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:14 +#: ../settings/ticket.rst:181 msgid "" -"Within Integrations, scroll down to Partner integrations and select Zammad." +"**Potential time-consuming action:** Applying default ticket notifications " +"to all agent users may take some time to complete, be patient! The exact " +"time will depend on the size of your system and the number of agents." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:17 +#: ../settings/ticket.rst:185 msgid "" -"You can alternatively filter by \"Ticket Systems\" to reduce the number of " -"entries on the page. You'll still want to look for Partner integrations. 🤓" +"**Active agents only!** When current default ticket notifications are " +"applied, only active agent users are considered. In case an agent is re-" +"activated *after* this action, they will still have the old notification " +"configuration." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:21 +#: ../settings/ticket.rst:190 msgid "" -"Within the Zammad integration now press \"Activate\". A new tab ``API`` " -"becomes available - open this tab." +"In case you want to go back to the initial state of ticket notifications, " +"you can click on **Reset to default** button." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:24 -msgid "" -"Now tick \"Enable Call Control / Notify API\" and paste the Placetel " -"endpoint from your Zammad instance into the field \"URL of your API " -"endpoint\". Save to apply the settings" +#: ../settings/ticket.rst:196 +msgid "Duplicate Detection" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 -msgid "Screencast showing how to activate the Zammad integration" +#: ../settings/ticket.rst:238 +msgid "Detect Duplicate Ticket Creation" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:51 -msgid "Step 2: Generate API Token for Placetel" +#: ../settings/ticket.rst:199 +msgid "" +"This setting turns on the duplicate ticket detection mechanism during ticket " +"creation. If similar tickets are found in the system, a suitable warning " +"will be shown to the user trying to create a ticket." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:32 -msgid "" -"Go back to the integrations page and scroll down to \"Web API\". Generate a " -"new API token by using the \"Create a new API token\" button." +#: ../settings/ticket.rst:206 +msgid "A Sample Duplicate Ticket Warning" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:37 +#: ../settings/ticket.rst:208 msgid "" -"If you already generated a token either use your existing token or reset it " -"by using above mentioned button. Placetel will ask you to conform this reset." +"You can choose which ticket attributes will be matched by selecting them in " +"**Attributes to compare** field. Only if the ticket attribute value provided " +"by the user in the ticket create form is *equal* with the attribute in an " +"existing ticket, the warning will be shown." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:41 -msgid "" -"Please keep in mind that existing API scripts may no longer work due to " -"token resets!" +#: ../settings/ticket.rst:213 +msgid "**Warning title** and **Warning message** are configurable as well." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:44 +#: ../settings/ticket.rst:215 msgid "" -"Copy the provided API token and insert it into the \"API Token\" field " -"within Zammad's Placetel integration." +"You can limit the detection only to certain user roles. By default, only " +"agents will see the warning." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:47 +#: ../settings/ticket.rst:218 msgid "" -"Apply your changes by using the \"Save\" button on the bottom of the " -"Placetel integration page and activate the Placetel integration." +"If you don't want to show the matched tickets as part of the warning, you " +"can set **Show matching ticket(s) in the warning** setting to *no*." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +#: ../settings/ticket.rst:221 msgid "" -"Screencast showing how to retrieve an API token from Placetel for Zammad" +"By default, **Permission level for looking up ticket** is set to *User*, " +"which means user permissions will be honored during sarch. The user will " +"see the warning only if tickets they have access to are matched. " +"Alternatively, you can set this setting to *System*, in which case the " +"search will happen within *all* tickets in the system, regardless of user " +"permissions." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:73 -#: ../system/integrations/cti/provider-configurations/sipgate.rst:77 -msgid "Step 3: Restrict the numbers to notify on" +#: ../settings/ticket.rst:227 +msgid "**🦺 Safety first!**" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:54 +#: ../settings/ticket.rst:229 msgid "" -"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " -"the the Integrations page of the Placetel web interface, go to \"Notify " -"API\"." +"Even if the permission level is set to *System*, the user will not be shown " +"the tickets they don't have access to in the warning, even if they match." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:58 +#: ../settings/ticket.rst:233 msgid "" -"Lower on the page Placetel allows you to restrict the numbers to notify on. " -"You'll find this within the \"External routing API\" part." +"However, just the confirmation about the existence of the tickets in the " +"system may be considered an unwanted information disclosure. Use this option " +"carefully!" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +#: ../settings/ticket.rst:237 msgid "" -"Screenshot showing a sample selection of phone numbers to use for the " -"Placetels notify API" +"Finally, you can configure between matching within **All tickets** or **Open " +"tickets** only by setting **Match tickets in following states**. Depending " +"on the current ticket state, a ticket may or not be matched." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:66 -msgid "" -"This menu point also provides a API request log from Placetel view. Just " -"open \"Recent responses of your API endpoint\" to learn more." +#: ../system/core-workflows.rst:2 +msgid "Core Workflows" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:69 +#: ../system/core-workflows.rst:4 msgid "" -"If you want to see Zammad's perspective, use the \"Recent Logs\" part from " -"within the Placetel integration page." +"Core Workflows allow you to adjust object attributes in many ways. For " +"example:" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 -msgid "Screenshot showing sample log entries for Placetels API calls to Zammad" +#: ../system/core-workflows.rst:7 +msgid "show / hide fields" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:77 -msgid "Step 4 (optional): Further configurations for Placetel" +#: ../system/core-workflows.rst:8 +msgid "adjust mandatory setting" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:76 +#: ../system/core-workflows.rst:9 +msgid "manipulate available options" +msgstr "" + +#: ../system/core-workflows.rst:11 msgid "" -"If needed, you can now configure Zammad's Placetel integration in more " -"detail. You can learn more about your options here: :ref:`Placetel " -"integration settings `." +"With this, you can provide exactly the information your users really need!" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:2 -msgid "Setup Sipgate connection for Zammad" +#: ../system/core-workflows.rst:15 +msgid "" +"If the pre-defined :doc:`/system/objects` are not enough, please add them " +"beforehand." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +#: ../system/core-workflows.rst:17 msgid "" -"Sipgate has no english web interface which is why this documentation page is " -"mixing up languages badly." +"If you experience slow or unreliable field updates, please see :ref:`Core " +"Workflow Ajax Modus `" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +#: ../system/core-workflows.rst:22 msgid "" -"Please also note that the availability of API addons highly depends on your " -"package trier. Usage of sipgate.io packages *is not free*, please check " -"their `pricing page `_ before!" +"This is a very enhanced functionality and can cause unexpected UI behavior. " +"Please ensure to test your use cases after configuration to reduce surprises." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:35 -msgid "Step 1: Book sipgate.io package" +#: ../system/core-workflows.rst:None +msgid "Dialogue for adding a new workflow" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:13 -msgid "Skip to step 2 if you already have the package booked!" +#: ../system/core-workflows/condition-operators.rst:2 +msgid "Core Workflow Condition Operators" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:15 +#: ../system/core-workflows/condition-operators.rst:4 msgid "" -"Login to an administrative Sipgate account and navigate to " -"``Accountverwaltung``. You'll see several different options depending on " -"your booked packages. Select ``Verträge & Produkte`` to continue." +"You might know that there is a separate section for explaining :doc:" +"`condition operators `. Head over there to " +"see a detailed explanation of many conditions and operators." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:19 +#: ../system/core-workflows/condition-operators.rst:8 msgid "" -"Scroll down to the section ``Zusätzliche Produkte buchen`` and look for " -"``sipgate.io`` - select this product by using the ``Produkte anzeigen``-" -"Button." -msgstr "" - -#: ../system/integrations/cti/provider-configurations/sipgate.rst:23 -msgid "" -"On the next page select either one of the ``sipgate.io`` packages or ``Push-" -"API Package Free``. Follow the dialogue by booking the addon. You'll be " -"returned to your contract overview and now should see the selected addon in " -"your list." +"Due to differences to other places in Zammad which are also using conditions " +"(e.g. triggers), you can find a dedicated description of operators for core " +"workflows below." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:30 +#: ../system/core-workflows/condition-operators.rst:12 msgid "" -"The availability for ``sipgate.io`` packages and their levels highly depends " -"on the overall account type and product you've booked with Sipgate." +"Be aware that the availability of the operators depends on the selected " +"attribute and its field type. Some of the operators may only be available " +"for system attributes (e.g. for \"tags\", \"active\")." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screencast showing the process on how to book the required sipgate.io addon" +#: ../system/core-workflows/condition-operators.rst:20 +msgid "Operator" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:52 -msgid "Step 2: Configure webhook for Zammad" +#: ../system/core-workflows/condition-operators.rst:22 +msgid "after (absolute)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:38 -msgid "" -"Within your ``Accountverwaltung`` navicate to your product ``sipgate.io``. " -"In the newly opened tab, switch from \"Clients\" to \"Webhooks\" and paste " -"the endpoint URLs from your Zammad instance like so:" +#: ../system/core-workflows/condition-operators.rst:23 +msgid "Matches if a date/time is after a specific point in time." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:42 -msgid "Inbound endpoint to \"Incoming\"" +#: ../system/core-workflows/condition-operators.rst:24 +msgid "after (relative)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:43 -msgid "Outbound endpoint to \"Outgoing\"" +#: ../system/core-workflows/condition-operators.rst:25 +msgid "Matches if a time span after a specified event has passed." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:47 -msgid "" -"Ensure to select at least one call group or phoneline within \"Sources\". " -"Other wise Sipgate will not indicate any incoming or outgoing calls to " -"Zammad." +#: ../system/core-workflows/condition-operators.rst:26 +msgid "before (absolute)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screencast showing how to add Zammad's endpoint URLs to sipgate.ios webhook " -"configuration" +#: ../system/core-workflows/condition-operators.rst:27 +msgid "Matches if a date/time is before a specific point in time." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:55 -msgid "" -"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " -"the Webhooks → URLs section of Sipgate you can select which *sources* " -"Sipgate should notify Zammad about in- and outgoing calls." +#: ../system/core-workflows/condition-operators.rst:28 +msgid "before (relative)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:59 -msgid "" -"Use either specific phone lines or use the option \"Use for all phonelines " -"and groups\" to notify Zammad about all existing lines of your Sipgate " -"account." +#: ../system/core-workflows/condition-operators.rst:29 +msgid "Matches if a time span after a specified event has not passed." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screenshot showing a sample selection of phone numbers to use for the " -"Sipgates webhooks API" +#: ../system/core-workflows/condition-operators.rst:30 +msgid "contains" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:68 -msgid "This section also allows you to enable a Debug log." +#: ../system/core-workflows/condition-operators.rst:31 +msgid "Matches if a specified value is present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "Screenshot showing an enabled Debug log option" +#: ../system/core-workflows/condition-operators.rst:33 +msgid "Matches if all of the specified values are present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:73 -msgid "" -"After enabling you can use the Debug log section to see all sent webhook " -"calls to Zammad. You'll also can see the response." +#: ../system/core-workflows/condition-operators.rst:35 +msgid "Matches if none of the specified values are present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screenshot showing sample log entries for Sipgates webhook calls to Zammad" +#: ../system/core-workflows/condition-operators.rst:36 +msgid "contains not" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:81 -msgid "Step 4 (optional): Further configurations for Sipgate" +#: ../system/core-workflows/condition-operators.rst:37 +msgid "Matches if a specified value is not present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:80 -msgid "" -"If needed, you can now configure Zammad's Sipgate integration in more " -"detail. You can learn more about your options here: :ref:`Sipgate " -"integration settings `." +#: ../system/core-workflows/condition-operators.rst:39 +msgid "Matches if one specified value is present." msgstr "" -#: ../system/integrations/cti/sipgate.rst:2 -msgid "Sipgate (sipgate.io)" +#: ../system/core-workflows/condition-operators.rst:41 +msgid "Matches if one specified value is not present." msgstr "" -#: ../system/integrations/cti/sipgate.rst:16 -msgid "You need an administrative Sipgate account for your organization." +#: ../system/core-workflows/condition-operators.rst:42 +msgid "does not match regex" msgstr "" -#: ../system/integrations/cti/sipgate.rst:17 -msgid "" -"Zammad requires a ``sipgate.io`` addon from the feature store (please note " -"that API calls are not free with Sipgate. Rates may apply and differ from " -"account to account)." +#: ../system/core-workflows/condition-operators.rst:43 +msgid "Matches if content doesn't fit to regex rule." msgstr "" -#: ../system/integrations/cti/sipgate.rst:21 -msgid "Sipgate must be able to reach your Zammad instance." +#: ../system/core-workflows/condition-operators.rst:44 +msgid "ends with" msgstr "" -#: ../system/integrations/cti/sipgate.rst:25 -msgid ":doc:`provider-configurations/sipgate`" +#: ../system/core-workflows/condition-operators.rst:45 +msgid "Matches if content ends with specified value." msgstr "" -#: ../system/integrations/cti/sipgate.rst:24 -msgid "" -"Learn how to configure Sipgate to enable Zammad and Sipgate to communicate " -"with each other." +#: ../system/core-workflows/condition-operators.rst:46 +msgid "ends with one of" msgstr "" -#: ../system/integrations/cti/sipgate.rst:33 -msgid "" -"Below endpoint settings affect the :doc:`sipgate.io configuration `." +#: ../system/core-workflows/condition-operators.rst:47 +msgid "Matches if content ends with one of the specified values." msgstr "" -#: ../system/integrations/cti/sipgate.rst:37 -msgid "This endpoint is required for incoming call hooks." +#: ../system/core-workflows/condition-operators.rst:48 +msgid "from (relative)" msgstr "" -#: ../system/integrations/cti/sipgate.rst:40 -msgid "This endpoint is required for outgoing call hooks." +#: ../system/core-workflows/condition-operators.rst:49 +msgid "Matches if date/time is after a period of time after an event." msgstr "" -#: ../system/integrations/cti/sipgate.rst:0 -msgid "Screenshot showing sample user mappings in between Sipgate and Zammad" +#: ../system/core-workflows/condition-operators.rst:51 +msgid "Matches if content is equal to a specified value." msgstr "" -#: ../system/integrations/cti/sipgate.rst:69 -msgid "" -"You can find your agent's Sipgate username within ``Accountverwaltung → " -"Benutzer``. You're looking for the SIP-ID." +#: ../system/core-workflows/condition-operators.rst:52 +msgid "is any of" msgstr "" -#: ../system/integrations/cti/sipgate.rst:0 -msgid "Sample VoIP credentials for a Sipgate user" +#: ../system/core-workflows/condition-operators.rst:53 +msgid "Matches if content is equal to any of specified values." msgstr "" -#: ../system/integrations/cti/sipgate.rst:77 -msgid "Users with several devices also have several SIP-IDs." +#: ../system/core-workflows/condition-operators.rst:54 +msgid "is modified" msgstr "" -#: ../system/integrations/elasticsearch.rst:2 -msgid "Elasticsearch (SaaS)" +#: ../system/core-workflows/condition-operators.rst:55 +msgid "Matches if content is modified." msgstr "" -#: ../system/integrations/elasticsearch.rst:4 -msgid "" -"The Elasticsearch integration allows you to create a read-only user to use " -"with your favorite reporting tool (e.g. like Grafana)." +#: ../system/core-workflows/condition-operators.rst:57 +#: ../system/core-workflows/condition-operators.rst:61 +msgid "True from the moment of changing content until form submit." msgstr "" -#: ../system/integrations/elasticsearch.rst:7 -msgid "" -"If you want to take full advantage of the Zammad reporting, have a look at " -"our :docs:`Grafana ` " -"setup page as well." +#: ../system/core-workflows/condition-operators.rst:58 +msgid "is modified to" msgstr "" -#: ../system/integrations/elasticsearch.rst:11 -#: ../system/subscription/index.rst:7 -msgid "**🚧 Hosted environment specific 🚧**" +#: ../system/core-workflows/condition-operators.rst:59 +msgid "Matches if content is modified to a specific value." msgstr "" -#: ../system/integrations/elasticsearch.rst:13 -msgid "" -"This integration is only available for Hosted setups. In order to use " -"Elasticsearch you'll need the **Plus** subscription." +#: ../system/core-workflows/condition-operators.rst:62 +msgid "is none of" msgstr "" -#: ../system/integrations/elasticsearch.rst:16 -msgid "" -"Self hosted users have all the control over their self hosted Elasticsearch " -"instances." +#: ../system/core-workflows/condition-operators.rst:63 +msgid "Matches if content is none of any specified values." msgstr "" -#: ../system/integrations/elasticsearch.rst:None -msgid "Elasticsearch integration page on SaaS environments" +#: ../system/core-workflows/condition-operators.rst:65 +msgid "Matches if content is not equal to a specified value." msgstr "" -#: ../system/integrations/elasticsearch.rst:27 -msgid "" -"Please note the following limitations of Elasticsearch access on hosted " -"environments:" +#: ../system/core-workflows/condition-operators.rst:67 +msgid "Matches if content is present." msgstr "" -#: ../system/integrations/elasticsearch.rst:30 -msgid "access to the Elasticsearch index is read-only access" +#: ../system/core-workflows/condition-operators.rst:68 +msgid "just changed" msgstr "" -#: ../system/integrations/elasticsearch.rst:31 -msgid "currently you're limited to user only" +#: ../system/core-workflows/condition-operators.rst:69 +msgid "Matches if content has changed." msgstr "" -#: ../system/integrations/elasticsearch.rst:32 +#: ../system/core-workflows/condition-operators.rst:71 +#: ../system/core-workflows/condition-operators.rst:75 msgid "" -"Reporting tools that require to write into the indexes (like Kibana) are not " -"supported" +"Only true for the moment of changing content until next form field action/" +"click." msgstr "" -#: ../system/integrations/elasticsearch.rst:34 -msgid "IP access restriction is currently not yet supported" +#: ../system/core-workflows/condition-operators.rst:72 +msgid "just changed to" msgstr "" -#: ../system/integrations/elasticsearch.rst:37 -msgid "Activating Elasticsearch Access" +#: ../system/core-workflows/condition-operators.rst:73 +msgid "Matches if content has changed to a specified value." msgstr "" -#: ../system/integrations/elasticsearch.rst:39 -msgid "" -"By default external access to your Elasticsearch index is not active. You " -"can enable the integration at any time if needed." +#: ../system/core-workflows/condition-operators.rst:76 +msgid "matches regex" msgstr "" -#: ../system/integrations/elasticsearch.rst:42 -msgid "" -"Please ensure to note down the password provided - you won't have access to " -"it afterwards." +#: ../system/core-workflows/condition-operators.rst:77 +msgid "Matches if value fits to regex rule." msgstr "" -#: ../system/integrations/elasticsearch.rst:None -msgid "Screencast showing activation of Elasticsearch integration" +#: ../system/core-workflows/condition-operators.rst:79 +msgid "Matches if no content is present." msgstr "" -#: ../system/integrations/elasticsearch.rst:51 -msgid "Connection Settings" +#: ../system/core-workflows/condition-operators.rst:80 +msgid "starts with" msgstr "" -#: ../system/integrations/elasticsearch.rst:53 -msgid "" -"This section holds the most important general information for accessing your " -"Elasticsearch indexes - such as:" -msgstr "" - -#: ../system/integrations/elasticsearch.rst:57 -msgid "A unique subdomain that does not tell your real instance URL." +#: ../system/core-workflows/condition-operators.rst:81 +msgid "Matches if content starts with specified value." msgstr "" -#: ../system/integrations/elasticsearch.rst:61 -msgid "Software" +#: ../system/core-workflows/condition-operators.rst:82 +msgid "starts with one of" msgstr "" -#: ../system/integrations/elasticsearch.rst:60 -msgid "" -"The major version of the search index being used. This is required by some " -"Reporting tools like Grafana." +#: ../system/core-workflows/condition-operators.rst:83 +msgid "Matches if content starts with one of the specified values." msgstr "" -#: ../system/integrations/elasticsearch.rst:64 -msgid "Authentication" +#: ../system/core-workflows/condition-operators.rst:84 +msgid "till (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:64 -msgid "The authentication type being supported. ``Basic Authentication``" +#: ../system/core-workflows/condition-operators.rst:85 +msgid "Matches if date/time is before a period of time before an event." msgstr "" -#: ../system/integrations/elasticsearch.rst:67 -msgid "Available Indexes" +#: ../system/core-workflows/condition-operators.rst:86 +msgid "today" msgstr "" -#: ../system/integrations/elasticsearch.rst:69 -msgid "" -"Within this section we're displaying the -in our opinion- most important " -"indexes for a Zammad instance." +#: ../system/core-workflows/condition-operators.rst:87 +msgid "Matches if date/time is today." msgstr "" -#: ../system/integrations/elasticsearch.rst:72 -msgid "" -"If you require all indexes or our listing is not good enough for you, point " -"your browser to the URL we're providing and append ``/_aliases?" -"pretty=true``. The result should look like this: ``https://.zammad.com/" -"_aliases?pretty=true``." +#: ../system/core-workflows/condition-operators.rst:88 +msgid "within last (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:77 +#: ../system/core-workflows/condition-operators.rst:89 msgid "" -"Your browser will automatically ask for your credentials - you'll then see " -"something like this:" +"Matches if date/time content is within specified period of time before now." msgstr "" -#: ../system/integrations/elasticsearch.rst:125 -msgid "Credentials" +#: ../system/core-workflows/condition-operators.rst:91 +msgid "within next (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:127 +#: ../system/core-workflows/condition-operators.rst:92 msgid "" -"Within this section Zammad displays your available users. The password is " -"provided once (upon activation) and cannot be retrieved after that." +"Matches if date/time content is within specified period of time after now." msgstr "" -#: ../system/integrations/elasticsearch.rst:131 -msgid "" -"If you need to change or reset your Elasticsearch user password, use the " -"\"Reset password\" button in the credentials table. Doing so creates a brand " -"new password for the account in question. This change is immediate, keep in " -"mind that this may affect third party tools connected to your instance." +#: ../system/core-workflows/how-do-they-work.rst:2 +msgid "How do they work?" msgstr "" -#: ../system/integrations/exchange.rst:2 -msgid "Exchange" +#: ../system/core-workflows/how-do-they-work.rst:4 +msgid "" +"Core Workflows are executed according to their priority. If two workflows " +"have the same priority, they are executed in alphabetical order based on " +"their **name**." msgstr "" -#: ../system/integrations/exchange.rst:4 +#: ../system/core-workflows/how-do-they-work.rst:8 msgid "" -"With Zammad's Exchange integration, you can easily use existing address " -"books without having to update more than one source." +"Because of the way Core Workflows work, all changes to attributes are " +"checked with the application server - please see :doc:`limitations` for " +"possible issues." msgstr "" -#: ../system/integrations/exchange.rst:7 +#: ../system/core-workflows/how-do-they-work.rst:12 msgid "" -"However, you should refrain from syncing all addresses, as the results may " -"not be what you expect (Exchange collects huge amounts of addresses). A " -"central address book of your company to sync makes more sense, as you can " -"ensure that Zammad gets only the data you need and want. Apart from this, it " -"is even not possible to sync the Global Address List (GAL) of your Exchange " -"system with Zammad." +"Below we're talking about settings that are important and not self-" +"explanatory." msgstr "" -#: ../system/integrations/exchange.rst:16 +#: ../system/core-workflows/how-do-they-work.rst:17 msgid "" -"**Exchange and LDAP:** The exchange sync can be overruled by Zammad's LDAP " -"integration. If you have the same users in both sources, the LDAP version " -"will always be Zammad's pick." +"Choose the object context you want to run the workflow in. This will decide " +"on your available attributes and actions." msgstr "" -#: ../system/integrations/exchange.rst:19 -msgid "" -"**One way sync:** the Exchange sync is one way. Exchange => Zammad. Changes " -"to your users inside of Zammad might be overwritten by the Exchange sync." +#: ../system/core-workflows/how-do-they-work.rst:20 +msgid "Ticket objects also have access to the ticket customer." msgstr "" -#: ../system/integrations/exchange.rst:24 +#: ../system/core-workflows/how-do-they-work.rst:25 msgid "" -"To configure Exchange integration, simply go to the System > Integrations > " -"Exchange in the admin panel. Press \"change\" and follow the wizard for " -"adding the needed Exchange information to Zammad. On the last two steps " -"Zammad will ask you for the address book(s) and your desired attribute " -"mapping. By default, Zammad only maps email address, first- and lastname. " -"Technically, you can map any Exchange object to a Zammad user object (this " -"also works for custom objects!)." +"Choose in which situation the workflow is applied. Contexts can be combined " +"to avoid duplicate workflows." msgstr "" -#: ../system/integrations/exchange.rst:35 -msgid "" -"If the SSL verification fails while connecting to Exchange, Zammad will ask " -"you to turn it off temporarily." +#: ../system/core-workflows/how-do-they-work.rst:30 +msgid "Creation mask" msgstr "" -#: ../system/integrations/exchange.rst:38 +#: ../system/core-workflows/how-do-they-work.rst:29 msgid "" -"Please be aware that **turning off SSL verification is a security risk**. It " -"should only be used temporarily or for testing purposes. If turned off, " -"there is no verification of the certificate, which means that every " -"presented certificate will be accepted." +"If selected, your conditions and actions will affect all applicable creation " +"masks." msgstr "" -#: ../system/integrations/exchange.rst:43 -msgid "" -"After pressing Continue, Zammad will check if the configuration is okay. You " -"can then enable Exchange and start your first sync. The sync will then run " -"hourly - if you need to change mappings or the address book(s), you can " -"change the configuration at any time." +#: ../system/core-workflows/how-do-they-work.rst:34 +msgid "Edit mask" msgstr "" -#: ../system/integrations/exchange.rst:50 +#: ../system/core-workflows/how-do-they-work.rst:33 msgid "" -"After the sync has finished, you can find the new Exchange contacts under " -"\"Users\". Zammad integrates them just as normal users." +"If selected, your conditions and actions will affect all applicable edit " +"masks." msgstr "" -#: ../system/integrations/exchange.rst:55 +#: ../system/core-workflows/how-do-they-work.rst:39 msgid "" -"In some cases you might see unique IDs as \"Login\" instead of the email " -"address. This is normal and doesn't affect the login or email mapping for " -"that entry." +"Zammad differentiates between selected and saved conditions. These can be " +"combined wherever needed." msgstr "" -#: ../system/integrations/github.rst:4 -msgid "" -"Use GitHub integration to track GitHub issues directly within Zammad " -"tickets. Add issue hyperlinks and get a live summary of metadata like status " -"(open/closed), assignee, labels, and more." +#: ../system/core-workflows/how-do-they-work.rst:42 +msgid "**⚠️ Restrict workflows to specific roles if needed!**" msgstr "" -#: ../system/integrations/github.rst:8 -msgid "Please note that our GitHub integration does not support pull requests." +#: ../system/core-workflows/how-do-they-work.rst:44 +msgid "" +"By default and unless configured in conditions, workflow rules are executed " +"for **all roles**. This also affects your customers!" msgstr "" -#: ../system/integrations/github.rst:None -msgid "Integration page for GitHub" +#: ../system/core-workflows/how-do-they-work.rst:50 +msgid "Selected Conditions" msgstr "" -#: ../system/integrations/github.rst:18 +#: ../system/core-workflows/how-do-they-work.rst:48 msgid "" -"In your GitHub settings, create a new API token under **Developer settings > " -"Personal access tokens > Generate new token**. Leave the **Scopes** section " -"empty." +"These conditions are based on form values and match if an appropriate " +"selection is made (e.g. choosing another group in the ticket without " +"saving). This applies for drafts (active selection) and currently saved " +"values." msgstr "" -#: ../system/integrations/github.rst:0 ../system/integrations/gitlab.rst:0 -msgid "Screencast showing how to create a new API token" +#: ../system/core-workflows/how-do-they-work.rst:64 +msgid "Saved Conditions" msgstr "" -#: ../system/integrations/github.rst:27 -msgid "Create a new API key with no scopes/privileges." +#: ../system/core-workflows/how-do-they-work.rst:53 +msgid "" +"These conditions only match if the selected values are stored in the " +"database. It ignores the current value or selection of the field, as long as " +"the changes are not saved (e.g. performing field operations for an existing " +"ticket, which is viewed/opened by an agent)." msgstr "" -#: ../system/integrations/github.rst:29 -msgid "🔒 **Will this work for private repos?**" +#: ../system/core-workflows/how-do-they-work.rst:60 +msgid "" +"Keep in mind that the value has to be available in the situation where you " +"need it. Otherwise the condition won't match." msgstr "" -#: ../system/integrations/github.rst:31 +#: ../system/core-workflows/how-do-they-work.rst:63 msgid "" -"No. To link private repo issues, **use the** ``repo`` **scope instead**. " -"Bear in mind that the resulting token will have `lots of permissions that it " -"doesn't actually need `_, which presents a security risk if your token ever falls into " -"the wrong hands." +"Example: you can't perform any actions with *saved condition* on a ticket in " +"creation, because there are no saved values at that time." msgstr "" -#: ../system/integrations/github.rst:37 +#: ../system/core-workflows/how-do-they-work.rst:66 msgid "" -"Unfortunately, because of how GitHub's OAuth token scopes are set up, this " -"is the only way to link issues on private repos." +"You can find a description of the condition operators for core workflows :" +"doc:`here `." msgstr "" -#: ../system/integrations/github.rst:40 -msgid "Enter your new API token in Zammad and enable GitHub integration." +#: ../system/core-workflows/how-do-they-work.rst:72 +msgid "" +"Which actions should we run on the relevant fields? The possible actions " +"depend on the object type. However, usually you can at least change the " +"visibility and whether the field is mandatory." msgstr "" -#: ../system/integrations/github.rst:0 -msgid "Screencast showing how to configure Zammad's GitHub integration" +#: ../system/core-workflows/how-do-they-work.rst:76 +msgid "Be aware that actions are not available for **related** context." msgstr "" -#: ../system/integrations/github.rst:47 +#: ../system/core-workflows/how-do-they-work.rst:78 msgid "" -"Use the default API endpoint (``https://api.github.com/graphql``) unless " -"you're using GitHub Enterprise Server." +"**Example:** Let's assume you are working in the ticket context. While you " +"can have customer *conditions*, you *can't adjust* objects with actions in " +"that scope. That's because this wouldn't have any impact on the ticket " +"dialog. Of course all ticket attributes (state, owner, ...) are available." msgstr "" -#: ../system/integrations/github.rst:50 +#: ../system/core-workflows/how-do-they-work.rst:84 msgid "" -"Once completed, a new GitHub issues tab will appear in the ticket pane. 🎉" +"Please also have a look at our :doc:`limitations` to be safe from surprises." msgstr "" -#: ../system/integrations/github.rst:59 ../system/integrations/gitlab.rst:52 -msgid "Token verification is taking a long time" +#: ../system/core-workflows/how-do-they-work.rst:88 +msgid "Available Operators" msgstr "" -#: ../system/integrations/github.rst:56 ../system/integrations/gitlab.rst:49 -msgid "" -"Slight delays are normal (<2 min.), especially for systems under heavy load." +#: ../system/core-workflows/how-do-they-work.rst:90 +msgid "The availability of operators depends on the object type and scope." msgstr "" -#: ../system/integrations/github.rst:58 +#: ../system/core-workflows/how-do-they-work.rst:94 msgid "" -"Self-hosted administrators, please check your network settings to ensure " -"that your Zammad server can reach ``api.github.com``." +"Please note that actions may or may not restrict API based access to " +"attributes. We're displaying the following icons for your overview to " +"understand these limits better:" msgstr "" -#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 -msgid "I reloaded the page and now the API token is gone" +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|api| This icon indicates the action affects the API." msgstr "" -#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 -msgid "" -"This may indicate that Zammad is still verifying your API token. Try " -"reloading the page again in a couple minutes." +#: ../system/core-workflows/how-do-they-work.rst:163 +msgid "api" msgstr "" -#: ../system/integrations/gitlab.rst:2 -msgid "GitLab" +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|ui| This icon indicates the action only affects the web interface." msgstr "" -#: ../system/integrations/gitlab.rst:4 -msgid "" -"Use GitLab integration to track GitLab issues directly within Zammad " -"tickets. Add issue hyperlinks and get a live summary of metadata like status " -"(open/closed), assignee, labels, and more." +#: ../system/core-workflows/how-do-they-work.rst:167 +msgid "ui" msgstr "" -#: ../system/integrations/gitlab.rst:8 -msgid "" -"Please note that our GitLab integration does not support merge requests." +#: ../system/core-workflows/how-do-they-work.rst:102 +msgid "show |ui|" msgstr "" -#: ../system/integrations/gitlab.rst:None -msgid "Integration page for GitLab" +#: ../system/core-workflows/how-do-they-work.rst:102 +msgid "Display the chosen field. Allows setting of values." msgstr "" -#: ../system/integrations/gitlab.rst:18 -msgid "" -"In your GitLab preferences, create a new API token under **Access Tokens**." +#: ../system/core-workflows/how-do-they-work.rst:109 +msgid "hide |ui|" msgstr "" -#: ../system/integrations/gitlab.rst:20 -msgid "Under **Select scopes**, choose ``read_api`` only." +#: ../system/core-workflows/how-do-they-work.rst:105 +msgid "" +"Hide the chosen field. However, it technically still allows setting the " +"field." msgstr "" -#: ../system/integrations/gitlab.rst:27 -msgid "🔒 **If you wish to link issues on any private repos...**" +#: ../system/core-workflows/how-do-they-work.rst:108 +msgid "" +"Please note that the field is **not** gone and still contains an existing " +"value (if set)! Consider *remove* instead, if you want this field to be gone." msgstr "" -#: ../system/integrations/gitlab.rst:29 -msgid "Your API token must belong to an account with access to those repos." +#: ../system/core-workflows/how-do-they-work.rst:112 +msgid "remove |ui|" msgstr "" -#: ../system/integrations/gitlab.rst:31 -msgid "Enter your new API token in Zammad and enable GitLab integration." +#: ../system/core-workflows/how-do-they-work.rst:112 +msgid "Entirely removes the field. The field value will not be evaluated." msgstr "" -#: ../system/integrations/gitlab.rst:0 -msgid "Screencast showing how to configure Zammad's GitLab integration" +#: ../system/core-workflows/how-do-they-work.rst:115 +msgid "set mandatory |ui| |api|" msgstr "" -#: ../system/integrations/gitlab.rst:40 -msgid "" -"Use the default API endpoint (``https://gitlab.com/api/graphql``) unless " -"you're a self-hosted GitLab user." +#: ../system/core-workflows/how-do-they-work.rst:115 +msgid "Sets the field to mandatory." msgstr "" -#: ../system/integrations/gitlab.rst:43 -msgid "" -"Once completed, a new GitLab issues tab will appear in the ticket pane. 🎉" +#: ../system/core-workflows/how-do-they-work.rst:118 +msgid "set optional |ui| |api|" msgstr "" -#: ../system/integrations/gitlab.rst:51 -msgid "" -"Self-hosted administrators, please check your network settings to ensure " -"that your Zammad server can reach ``gitlab.com``." +#: ../system/core-workflows/how-do-they-work.rst:118 +msgid "Sets the field to optional." msgstr "" -#: ../system/integrations/i-doit.rst:2 -msgid "i-doit" +#: ../system/core-workflows/how-do-they-work.rst:124 +msgid "add option |ui| |api|" msgstr "" -#: ../system/integrations/i-doit.rst:4 -msgid "" -"`i-doit `_ is an open-source **configuration " -"management database** - in other words, a tool for keeping tabs on every " -"single piece of your physical and digital infrastructure, from network " -"equipment to virtual machines on down to the faceplates on your rack shelves " -"and more." +#: ../system/core-workflows/how-do-they-work.rst:121 +msgid "Allows adding options to tree selects or selects." msgstr "" -#: ../system/integrations/i-doit.rst:10 +#: ../system/core-workflows/how-do-they-work.rst:123 msgid "" -"What's that got to do with Zammad? Well, if you used tickets to track issues " -"with all that hardware, you might start wishing there was a way they could " -"talk to each other." -msgstr "" - -#: ../system/integrations/i-doit.rst:14 -msgid "Zammad gives you two:" +"You have to use the \"remove option\" before performing this action. It " +"allows you to use *existing* configured values." msgstr "" -#: ../system/integrations/i-doit.rst:17 -msgid "1. Add i-doit Links to Zammad Tickets" +#: ../system/core-workflows/how-do-they-work.rst:128 +msgid "remove option |ui| |api|" msgstr "" -#: ../system/integrations/i-doit.rst:20 ../system/integrations/i-doit.rst:80 -msgid "What Users See" +#: ../system/core-workflows/how-do-they-work.rst:127 +msgid "" +"Allows removing options from tree selects or selects. It allows you to use " +"*existing* configured values." msgstr "" -#: ../system/integrations/i-doit.rst:26 -msgid "i-doit integration in Zammad's ticket pane" +#: ../system/core-workflows/how-do-they-work.rst:134 +msgid "set fixed to |ui| |api|" msgstr "" -#: ../system/integrations/i-doit.rst:26 -msgid "" -"The i-doit integration will appear under a new 🖨 tab in the ticket pane." +#: ../system/core-workflows/how-do-they-work.rst:131 +msgid "Reduces the available options by your selection." msgstr "" -#: ../system/integrations/i-doit.rst:28 +#: ../system/core-workflows/how-do-they-work.rst:133 msgid "" -"i-doit integration puts a new tab in Zammad's ticket pane where you can add " -"links to existing i-doit devices for easy reference. (See our :user-docs:" -"`user documentation ` to learn " -"how it works in practice)." +"This reduces your workflows in terms of *add option* and *remove option*." msgstr "" -#: ../system/integrations/i-doit.rst:36 ../system/integrations/i-doit.rst:93 -msgid "How to Set it Up" +#: ../system/core-workflows/how-do-they-work.rst:137 +msgid "fill in |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:38 -msgid "" -"It requires i-doit's `API Add-on `_. Make sure to have it properly set up. Use the following setting:" +#: ../system/core-workflows/how-do-they-work.rst:137 +msgid "Allows filling in of string and integer fields with your values." msgstr "" -#: ../system/integrations/i-doit.rst:42 -msgid "Active: ``Yes``" +#: ../system/core-workflows/how-do-they-work.rst:141 +msgid "fill in empty |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:43 -msgid "Enforce authentication by username and password: ``No``" +#: ../system/core-workflows/how-do-they-work.rst:140 +msgid "" +"Allows filling in of string and integer fields with your values **if the " +"field is empty**." msgstr "" -#: ../system/integrations/i-doit.rst:45 -msgid "" -"To set it up, enable the integration in the Zammad admin panel under " -"**System > Integrations > i-doit**:" +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "select |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "i-doit settings within the integration pages" +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "Select a specific value within a select, tree select or boolean field." msgstr "" -#: ../system/integrations/i-doit.rst:53 -msgid "The root URL of your i-doit installation." +#: ../system/core-workflows/how-do-they-work.rst:153 +msgid "auto select |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:62 -msgid "API token" +#: ../system/core-workflows/how-do-they-work.rst:147 +msgid "Helps users with tree select and select fields:" msgstr "" -#: ../system/integrations/i-doit.rst:56 +#: ../system/core-workflows/how-do-they-work.rst:149 msgid "" -"Found in the i-doit admin panel under **Interfaces / external data > JSON-" -"RPC API > Common Settings**." +"If the field has only one option available for selection and no value yet, " +"the value will be automatically set." msgstr "" -#: ../system/integrations/i-doit.rst:0 -msgid "i-doit administration interface with API configuration" +#: ../system/core-workflows/how-do-they-work.rst:152 +msgid "" +"This option only works if you have one value and doesn't work if there is " +"more than one option available." msgstr "" -#: ../system/integrations/i-doit.rst:67 -msgid "Client ID" +#: ../system/core-workflows/how-do-they-work.rst:157 +msgid "set readonly |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:65 -msgid "A unique name to identify Zammad within i-doit." +#: ../system/core-workflows/how-do-they-work.rst:156 +msgid "" +"Allows you to display an attribute as read only (which means no changes are " +"possible)." msgstr "" -#: ../system/integrations/i-doit.rst:67 -msgid "(Zammad does not require you to enter a value here, but i-doit might!)" +#: ../system/core-workflows/how-do-they-work.rst:161 +msgid "unset readonly |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:70 +#: ../system/core-workflows/how-do-they-work.rst:160 msgid "" -"Here you can decide if the certificate of your i-doit system has to be " -"verified or not. In case you are using custom certificates, please have a " -"look at :doc:`how to add them to Zammad `." -msgstr "" - -#: ../system/integrations/i-doit.rst:77 -msgid "2. List / Create Zammad Tickets in i-doit" +"In case a workflow set the field in question to read only, you can undo this " +"with option above." msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "Zammad integration in i-doit's device view" +#: ../system/core-workflows/how-do-they-work.rst:172 +msgid "Stop after match" msgstr "" -#: ../system/integrations/i-doit.rst:86 +#: ../system/core-workflows/how-do-they-work.rst:174 msgid "" -"i-doit's ticket system integration gives you a way to see all the tickets " -"for a given device without ever leaving i-doit. (See our :user-docs:`user " -"documentation ` to learn how it " -"works in practice)." +"Here you can decide if other workflows are executed after the current one." msgstr "" -#: ../system/integrations/i-doit.rst:95 +#: ../system/core-workflows/how-do-they-work.rst:176 msgid "" -"Enable this integration in the i-doit admin panel under **Interfaces / " -"external data > Trouble Ticket System (TTS) > Configuration**:" +"If set to ``no`` (default), further workflows will be executed if they match " +"the condition. In this case, it is possible that your actions from the " +"current workflow can be overwritten by another workflow." msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "i-doit administration interface with TTS configuration" +#: ../system/core-workflows/how-do-they-work.rst:180 +msgid "" +"If set to ``yes``, no further worflows will be executed after the current " +"one." msgstr "" -#: ../system/integrations/i-doit.rst:104 -msgid "TTS-Type" +#: ../system/core-workflows/how-do-they-work.rst:184 +msgid "Priority" msgstr "" -#: ../system/integrations/i-doit.rst:104 -msgid "``Zammad``" +#: ../system/core-workflows/how-do-they-work.rst:186 +msgid "" +"You can define the sequence, in which the workflows are executed. The " +"default value is ``500``." msgstr "" -#: ../system/integrations/i-doit.rst:115 -msgid "Username / Password" +#: ../system/core-workflows/how-do-they-work.rst:189 +msgid "" +"The workflows are executed in ascending order by their priority. That means " +"lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." msgstr "" -#: ../system/integrations/i-doit.rst:107 -msgid "Login credentials for a Zammad agent." +#: ../system/core-workflows/learn-by-example.rst:2 +msgid "Learn by Example" msgstr "" -#: ../system/integrations/i-doit.rst:109 +#: ../system/core-workflows/learn-by-example.rst:4 msgid "" -"This agent must have **read permission** for all :doc:`groups ` that plan on using the i-doit integration." +"This page provides some basic examples for Core Workflows. Of course you can " +"build much more complex workflows if needed." msgstr "" -#: ../system/integrations/i-doit.rst:113 +#: ../system/core-workflows/learn-by-example.rst:7 msgid "" -"You may even wish to create a dedicated agent account just for this " -"integration (otherwise, if the agent ever changes her password, you will " -"have to remember to update it here)." +"To learn about Core Workflows in detail, first go to :doc:`how-do-they-work`." msgstr "" -#: ../system/integrations/i-doit.rst:117 -msgid "URL incl. protocol" +#: ../system/core-workflows/learn-by-example.rst:10 +msgid "Group Based Examples" msgstr "" -#: ../system/integrations/i-doit.rst:118 -msgid "``https://your.zammad.domain``" +#: ../system/core-workflows/learn-by-example.rst:12 +msgid "" +"All following workflows have the same base configurations. The workflow may " +"not use them all." msgstr "" -#: ../system/integrations/index.rst:2 -msgid "Integrations" +#: ../system/core-workflows/learn-by-example.rst:15 +msgid "Groups:" msgstr "" -#: ../system/integrations/index.rst:4 +#: ../system/core-workflows/learn-by-example.rst:20 +msgid "Attributes:" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:22 +msgid "Category (Single tree selection field, not mandatory, agents only)" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:23 msgid "" -"Zammad offers numerous integrations that add rich features to your instance." +"Approved (Boolean field, not mandatory, not shown, ``false`` as default)" msgstr "" -#: ../system/integrations/index.rst:6 -msgid "We're still working on this part of our documentation, stay tight!" +#: ../system/core-workflows/learn-by-example.rst:24 +msgid "Operating System (Text field, not mandatory, not shown)" msgstr "" -#: ../system/integrations/index.rst:10 -msgid "Integrations for Phone Systems" +#: ../system/core-workflows/learn-by-example.rst:25 +msgid "Software used (Single selection field, not mandatory, not shown)" msgstr "" -#: ../system/integrations/index.rst:14 -msgid "" -"Your VoIP provider or telephony system is not listed? Possibly your provider " -"supports Zammad by using the generic CTI - if you're unsure ask your " -"provider." +#: ../system/core-workflows/learn-by-example.rst:68 +msgid "Group specific values and fields" msgstr "" -#: ../system/integrations/index.rst:18 +#: ../system/core-workflows/learn-by-example.rst:28 msgid "" -"Provider does not support Zammad? Consider creating a `feature request in " -"the Zammad Community `_." +"This workflow set depends on the category field. It reduces the available " +"set of values based on the group selected." msgstr "" -#: ../system/integrations/index.rst:31 -msgid "Integrations for Authentication and Customers" +#: ../system/core-workflows/learn-by-example.rst:33 +msgid "Workflow 2nd Level group" msgstr "" -#: ../system/integrations/index.rst:44 -msgid "Integrations for Monitoring Systems" +#: ../system/core-workflows/learn-by-example.rst:35 +msgid "" +"This reduces the category options to ``2nd Level/*``, ``Internal/*`` and " +"``Others``. It also sets further required fields to mandatory and visible." msgstr "" -#: ../system/integrations/index.rst:46 -msgid "This section currently misses the following integrations:" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for 2nd level" msgstr "" -#: ../system/integrations/index.rst:48 -msgid "Icinga" +#: ../system/core-workflows/learn-by-example.rst:43 +msgid "Workflow Support group" msgstr "" -#: ../system/integrations/index.rst:49 -msgid "Monit" +#: ../system/core-workflows/learn-by-example.rst:45 +msgid "" +"This reduces the category options to ``Support/*``, ``Internal/*`` and " +"``Others``. It also sets further required fields to visible." msgstr "" -#: ../system/integrations/index.rst:50 -msgid "Nagios" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for support" msgstr "" -#: ../system/integrations/index.rst:60 -msgid "Integrations for Issue Trackers" +#: ../system/core-workflows/learn-by-example.rst:53 +msgid "Workflow Sales group" msgstr "" -#: ../system/integrations/index.rst:70 -msgid "Other Integrations" +#: ../system/core-workflows/learn-by-example.rst:55 +msgid "" +"This reduces the category options to ``Sales/*``, ``Internal/*`` and " +"``Others``." msgstr "" -#: ../system/integrations/index.rst:72 -msgid "" -"This section will hold any other integration that can't be grouped up (yet)." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for sales" msgstr "" -#: ../system/integrations/ldap/index.rst:2 -msgid "LDAP / Active Directory" +#: ../system/core-workflows/learn-by-example.rst:68 +#: ../system/integrations/slack.rst:88 +msgid "The Result" msgstr "" -#: ../system/integrations/ldap/index.rst:4 +#: ../system/core-workflows/learn-by-example.rst:63 msgid "" -"Zammad comes with a powerful LDAP integration that allows you to have a " -"single source of truth. By this you reduce the number of login credentials " -"your user has to remember." +"This is what the agent would experience with the above workflows in place." msgstr "" -#: ../system/integrations/ldap/index.rst:10 +#: ../system/core-workflows/learn-by-example.rst:0 msgid "" -"The LDAP source is also a perfect candidate for Zammad's :docs:`Kerberos " -"Single Sign-On ` but also works as addition " -"to other :doc:`/settings/security/third-party`." +"Workflow shows objects and limits options based on selections on the group" msgstr "" -#: ../system/integrations/ldap/index.rst:None -msgid "Zammands LDAP management page" +#: ../system/core-workflows/learn-by-example.rst:90 +msgid "Approval process" msgstr "" -#: ../system/integrations/ldap/index.rst:25 -msgid "📝 :doc:`manage`" +#: ../system/core-workflows/learn-by-example.rst:71 +msgid "" +"In this case ``approved`` is visible to agents by default. For this " +"workflow, an additional role ``Approval person`` is required (no further " +"permissions)." msgstr "" -#: ../system/integrations/ldap/index.rst:25 -msgid "Add, modify, remove or re-arrange your LDAP-Sources as needed." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that restricts an approval attribute to specific roles" msgstr "" -#: ../system/integrations/ldap/index.rst:30 -msgid "Before you continue, please note the following limitations." +#: ../system/core-workflows/learn-by-example.rst:81 +msgid "" +"This workflow may work best in combination with a :doc:`trigger ` but technically, this is not required." msgstr "" -#: ../system/integrations/ldap/index.rst:32 -msgid "Mapping / Synchronizing organizations is not possible" +#: ../system/core-workflows/learn-by-example.rst:84 +msgid "" +"Select fields may be a better approach because they allow more values than " +"just a simple ``true`` or ``false``." msgstr "" -#: ../system/integrations/ldap/index.rst:36 +#: ../system/core-workflows/learn-by-example.rst:0 msgid "" -"You may want to consider using domain based assignments to overcome this " -"issue. Learn more on :doc:`/manage/organizations/index`." +"Workflow fixes possible values of \"Approved ?\" to a specific selection " +"depending on the users role" msgstr "" -#: ../system/integrations/ldap/index.rst:39 +#: ../system/core-workflows/learn-by-example.rst:103 +msgid "State dependent mandatory fields" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:93 msgid "" -"Zammad's LDAP sync is one way. Editing user settings or permissions may be " -"overwritten upon the next sync depending on your configuration." +"This workflow sets ``Category`` to mandatory if the agent wants to set the " +"states ``closed`` or ``pending close`` to enforce categorization." msgstr "" -#: ../system/integrations/ldap/index.rst:41 -msgid "Nested groups are not supported." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that sets fields to mandatory on specific states" msgstr "" -#: ../system/integrations/ldap/index.rst:42 -msgid "Synchronizing user avatars from LDAP is not supported." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "" +"Workflow sets category field to mandatory upon choosing closed or pending " +"close as state" msgstr "" -#: ../system/integrations/ldap/index.rst:43 -msgid "Unlike user filters, group filters cannot be changed." +#: ../system/core-workflows/learn-by-example.rst:106 +msgid "Manual Ticket Handover Process" msgstr "" -#: ../system/integrations/ldap/index.rst:44 -msgid "" -"When a user originates from an LDAP server, Zammad will try to verify the " -"login credentials against LDAP first - if this fails Zammad will check its " -"local database." +#: ../system/core-workflows/learn-by-example.rst:108 +msgid "This example covers the handover of a ticket from one agent to another:" msgstr "" -#: ../system/integrations/ldap/index.rst:50 +#: ../system/core-workflows/learn-by-example.rst:110 msgid "" -"Users can have local passwords even if they're LDAP users! You can learn " -"more about user accounts in general on :doc:`/manage/users/index`." +"When the ticket owner is modified, a new text field (\"Handover\") shows up " +"for a comment" msgstr "" -#: ../system/integrations/ldap/index.rst:54 +#: ../system/core-workflows/learn-by-example.rst:112 msgid "" -"When several LDAP sources contain the same user (meaning the same email " -"address), the user in question will be updated with every source configured. " -"*The last LDAP source will win.*" +"This may only be visible when the owner is changed, therefore it has to be " +"hidden in general" msgstr "" -#: ../system/integrations/ldap/index.rst:58 -msgid "" -"This is subject to change with `Issue 4109 `_ in the future." +#: ../system/core-workflows/learn-by-example.rst:114 +msgid "The input in this handover text field is mandatory" msgstr "" -#: ../system/integrations/ldap/index.rst:60 +#: ../system/core-workflows/learn-by-example.rst:115 msgid "" -"Synchronization statistics currently affect *all* configured LDAP sources. " -"This also applies for newly added or updated sources." +"After submitting changes, the value of the handover field must be added as " +"an note to the ticket (via trigger)" msgstr "" -#: ../system/integrations/ldap/index.rst:63 -msgid "" -"This is subject to change with `Issue 4108 `_ in the future." +#: ../system/core-workflows/learn-by-example.rst:121 +msgid "Hiding handover field" msgstr "" -#: ../system/integrations/ldap/index.rst:65 -msgid "" -"Zammad currently has limited fallback server support. You can workaround " -"this by providing several sources - however, ensure to have the exact same " -"configuration on your fallback." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Hiding the handover field in core workflows" msgstr "" -#: ../system/integrations/ldap/index.rst:69 -msgid "" -"This is subject to improve with `Issue 4107 `_ in the future." +#: ../system/core-workflows/learn-by-example.rst:126 +msgid "Showing handover field and setting it to mandatory" msgstr "" -#: ../system/integrations/ldap/index.rst:76 -msgid "" -"This section holds all requests Zammad handled for all LDAP sources. These " -"entries can either contain synchronization information or logins " -"(authentication attempts via Zammad's login interface)." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Showing the handover field and set it as mandatory" msgstr "" -#: ../system/integrations/ldap/index.rst:80 -msgid "" -"By clicking on any request, Zammad will provide even more information. The " -"provided information can be useful when something does not work as expected." +#: ../system/core-workflows/learn-by-example.rst:131 +msgid "Trigger writing handover input to a new article" msgstr "" -#: ../system/integrations/ldap/index.rst:85 -msgid "" -"Especially a LDAP synchronization can cause many log entries. The web " -"interface will always limit the number of shown entries to the last 50 " -"entries." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Write handover content to a new article" msgstr "" -#: ../system/integrations/ldap/index.rst:None +#: ../system/core-workflows/learn-by-example.rst:133 msgid "" -"Screencast showing LDAP integration log entries and a detail view on\n" -"an entry." +"As a result, the ticket includes an article of the type note which includes " +"the predefined text and the handover comment." msgstr "" -#: ../system/integrations/ldap/manage.rst:2 -msgid "Manage LDAP-Sources" +#: ../system/core-workflows/limitations.rst:6 +msgid "Core Workflows do not replace Triggers" msgstr "" -#: ../system/integrations/ldap/manage.rst:6 +#: ../system/core-workflows/limitations.rst:5 msgid "" -"Please keep in mind all current limitations for the LDAP synchronization. " -"This will help to understand scopes of the following operations better." +"Workflows manipulate the behavior of fields. However, they do not set values " +"in fields because of actions." msgstr "" -#: ../system/integrations/ldap/manage.rst:65 -msgid "Add new source" +#: ../system/core-workflows/limitations.rst:16 +msgid "API calls are only partly affected" msgstr "" -#: ../system/integrations/ldap/manage.rst:10 +#: ../system/core-workflows/limitations.rst:9 msgid "" -"Using the *New Source* button allows you to add new LDAP sources to your " -"installation. You're not limited in the number of sources, however, keep in " -"mind that many sources will also take more time to synchronize." +"Some options affect UI only and thus do not restrict responses and calls." msgstr "" -#: ../system/integrations/ldap/manage.rst:14 -msgid "" -"You can choose between different encryption types, namely *SSL* and " -"*STARTTLS* or none of them (\"*No SSL*\"). If you choose *SSL* or " -"*STARTTLS*, Zammad will display an additional *SSL verification* option that " -"allows you to disable the verification, e.g. for self-signed SSL " -"certificates. You can also tell Zammad to use a different port by appending " -"``:`` to your hostname/IP." +#: ../system/core-workflows/limitations.rst:11 +msgid "This affects the following actions:" msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "" -"Screenshot of configuring a new LDAP source with SSL encryption and SSL " -"verification" +#: ../system/core-workflows/limitations.rst:13 +msgid "select" msgstr "" -#: ../system/integrations/ldap/manage.rst:26 -msgid "" -"New Source with SSL transport security enabled and certificate verification" +#: ../system/core-workflows/limitations.rst:14 +msgid "auto select" msgstr "" -#: ../system/integrations/ldap/manage.rst:30 -msgid "" -"Using an user filter can be a good idea if you only require a small subset " -"of your LDAP users in Zammad." +#: ../system/core-workflows/limitations.rst:15 +msgid "show" msgstr "" -#: ../system/integrations/ldap/manage.rst:42 -msgid "This especially affects inactive users" +#: ../system/core-workflows/limitations.rst:16 +msgid "hide" msgstr "" -#: ../system/integrations/ldap/manage.rst:34 -msgid "" -"As every LDAP behaves differently on which attributes and how they are set, " -"Zammad doesn't care about any flags." +#: ../system/core-workflows/limitations.rst:25 +msgid "Some fields stay unavailable to customers" msgstr "" -#: ../system/integrations/ldap/manage.rst:37 +#: ../system/core-workflows/limitations.rst:19 msgid "" -"Users that no longer are returned by your LDAP source will automatically be " -"set to inactive. Zammad assumes that the user was deactivated." +"For technical and security reasons, some default fields (the pale ones you " +"can't edit) stay unavailable for display and usage on customer permissions." msgstr "" -#: ../system/integrations/ldap/manage.rst:41 +#: ../system/core-workflows/limitations.rst:23 msgid "" -"Users will never be removed automatically! If you want to remove obsolete " -"users, use :doc:`/system/data-privacy`." +"If you require your customers to change e.g. priorities, please consider " +"using workarounds via :doc:`/system/objects` and :doc:`/manage/trigger`." msgstr "" -#: ../system/integrations/ldap/manage.rst:46 -msgid "Active Directory admins" +#: ../system/core-workflows/limitations.rst:29 +msgid "Ticket title changes not supported in edit mask" msgstr "" -#: ../system/integrations/ldap/manage.rst:45 +#: ../system/core-workflows/limitations.rst:28 msgid "" -"Active Directories are quite specific on how to filter for active users only " -"- please see the `Microsoft documentation `_ for more " -"information." +"It is currently not possible to perform changes of the ticket title in the " +"edit mask (e.g. renaming, set to read-only)." msgstr "" -#: ../system/integrations/ldap/manage.rst:51 -msgid "" -"*Do not* manually write pathes of either LDAP attributes or groups. If " -"Zammad does not display them, it either cannot find them or you have a lot " -"of users that don't have the attributes populated." +#: ../system/core-workflows/limitations.rst:37 +msgid "What is out of scope of Core Workflows?" msgstr "" -#: ../system/integrations/ldap/manage.rst:55 +#: ../system/core-workflows/limitations.rst:32 msgid "" -"Zammad will always only return attributes that are filled - this reduces the " -"returned list of attributes greatly." +"There are some things that would count as workflow but are either done via :" +"doc:`/manage/trigger` or :doc:`/manage/scheduler`." msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing how to add a new LDAP source" +#: ../system/core-workflows/limitations.rst:35 +msgid "Such as (but not limited to):" msgstr "" -#: ../system/integrations/ldap/manage.rst:63 -msgid "" -"If your LDAP system doesn't allow anonymous bind, Zammad detects it and " -"provides you an editable \"Base DN\" *text* field instead of a prefilled " -"*select* field." +#: ../system/core-workflows/limitations.rst:37 +msgid "up- or downgrade permissions of users" msgstr "" -#: ../system/integrations/ldap/manage.rst:81 -msgid "Review or edit existing source" +#: ../system/core-workflows/limitations.rst:38 +msgid "affecting article creation or listing" msgstr "" -#: ../system/integrations/ldap/manage.rst:68 +#: ../system/data-privacy.rst:2 +msgid "Data Privacy" +msgstr "" + +#: ../system/data-privacy.rst:4 msgid "" -"Clicking on a LDAP source will provide a configuration and mapping overview." +"For compliance with GDPR and other data privacy laws, you may wish to " +"**permanently delete users from the system**, along with **all of their " +"associated tickets**." msgstr "" -#: ../system/integrations/ldap/manage.rst:70 +#: ../system/data-privacy.rst:8 msgid "" -"If needed you can then use the *Change* button to update either the name, " -"active state or the whole configuration. If you're changing the whole " -"configuration, the dialogue will be identical to the source creation." +"You can create manual deletion tasks or even automated deletion tasks for " +"tickets and users based on custom conditions via :doc:`scheduler `!" msgstr "" -#: ../system/integrations/ldap/manage.rst:76 +#: ../system/data-privacy.rst:12 msgid "" -"Did your LDAP server change? Different LDAP servers have different " -"structures and default attributes. This causes the LDAP synchronization to " -"likely fail. Consider removing the affected source and re-add it." +"Access to this panel requires ``admin.data_privacy`` permissions (introduced " +"in Zammad 3.5)." msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing the update of the source name." +#: ../system/data-privacy.rst:15 +msgid "" +"On older systems that have not been updated yet, customers can also be :docs:" +"`deleted via the Zammad console `." msgstr "" -#: ../system/integrations/ldap/manage.rst:89 -msgid "Re-arrange LDAP source's order" +#: ../system/data-privacy.rst:22 +msgid "User deletion dialog in the Data Privacy panel" msgstr "" -#: ../system/integrations/ldap/manage.rst:84 +#: ../system/data-privacy.rst:22 msgid "" -"You can change the synchronization order for each source at any time. Zammad " -"will synchronize the sources from top to bottom." +"The user deletion dialog lists some of the tickets that will be removed from " +"the system along with the user." msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "" -"Screencasting showing how to change the source order by using\n" -"drag and drop." +#: ../system/data-privacy.rst:27 +msgid "Deleting Users via GUI" msgstr "" -#: ../system/integrations/ldap/manage.rst:101 -msgid "Remove a source" +#: ../system/data-privacy.rst:29 +msgid "🔥 **All deletions are FINAL!**" msgstr "" -#: ../system/integrations/ldap/manage.rst:92 -msgid "" -"If you no longer need the a LDAP source or simply want to start over, you " -"can remove them at any time. This will not remove synchronized users, data " -"synchronized or permissions." +#: ../system/data-privacy.rst:31 +msgid "Once you click “Delete”, the action cannot be canceled or undone." msgstr "" -#: ../system/integrations/ldap/manage.rst:98 +#: ../system/data-privacy.rst:33 msgid "" -"Not sure if you'd need the source later on? Set the source to inactive " -"instead of removing it - see *Review or edit existing source* for more." +"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." msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing how to remove LDAP sources." +#: ../system/data-privacy.rst:36 +msgid "**The following records cannot be deleted:**" msgstr "" -#: ../system/integrations/pgp/index.rst:2 -msgid "PGP" +#: ../system/data-privacy.rst:38 +msgid "your own account" msgstr "" -#: ../system/integrations/pgp/index.rst:7 -msgid "" -"Pretty Good Privacy (PGP) is another method for secure email communication. " -"With PGP, you can exchange **signed** and **encrypted** messages with others." +#: ../system/data-privacy.rst:39 +msgid "the system's last remaining administrator account" msgstr "" -#: ../system/integrations/pgp/index.rst:13 -#: ../system/integrations/smime/index.rst:17 -msgid "Signing" +#: ../system/data-privacy.rst:42 +msgid "Step 1: Find a User / Confirm Deletion" msgstr "" -#: ../system/integrations/pgp/index.rst:11 -msgid "is a proof that a message hasn't been manipulated on its way." +#: ../system/data-privacy.rst:44 +msgid "There are three ways to access the user deletion dialog:" msgstr "" -#: ../system/integrations/pgp/index.rst:13 -msgid "" -"In other words, it guarantees message **integrity** and **authenticity**." +#: ../system/data-privacy.rst:51 +msgid "**from the user's profile**" msgstr "" -#: ../system/integrations/pgp/index.rst:19 -#: ../system/integrations/smime/index.rst:22 -msgid "Encryption" +#: ../system/data-privacy.rst:0 +msgid "Accessing the user deletion dialog in a user profile" msgstr "" -#: ../system/integrations/pgp/index.rst:16 -#: ../system/integrations/smime/index.rst:20 -msgid "" -"scrambles a message so that it can only be unscrambled by the intended " -"recipient." +#: ../system/data-privacy.rst:51 +msgid "Click **Action > Delete**." msgstr "" -#: ../system/integrations/pgp/index.rst:19 -msgid "" -"In other words, it guarantees message **privacy** and **data security**." +#: ../system/data-privacy.rst:58 +msgid "**in the “Manage > Users” Admin Panel**" msgstr "" -#: ../system/integrations/pgp/index.rst:25 -msgid "Screenshot of ticket creation with encrypt and sign buttons" +#: ../system/data-privacy.rst:0 +msgid "Accessing the user deletion dialog under “Users” in the Admin Panel" msgstr "" -#: ../system/integrations/pgp/index.rst:25 -msgid "" -"Once PGP has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " -"appear in the ticket composer." +#: ../system/data-privacy.rst:58 +msgid "Use the **⋮ Actions** menu for the target user." msgstr "" -#: ../system/integrations/pgp/index.rst:28 -msgid "**Sign button not visible?**" +#: ../system/data-privacy.rst:66 ../system/data-privacy.rst:104 +msgid "**in the “System > Data Privacy” Admin Panel**" msgstr "" -#: ../system/integrations/pgp/index.rst:30 +#: ../system/data-privacy.rst:0 msgid "" -"Please note that the signing of emails is based on the outgoing email " -"account. That means you have to choose a group with a sender email account, " -"which has a private key assigned." +"Accessing the user deletion dialog under “Data Privacy” in the Admin Panel" msgstr "" -#: ../system/integrations/pgp/index.rst:35 -msgid "Handling of Keys" +#: ../system/data-privacy.rst:65 +msgid "" +"Use the **New Deletion Task** button. Search for users by name or email " +"address." msgstr "" -#: ../system/integrations/pgp/index.rst:36 -msgid "" -"To use the PGP function, you have to enable the integration (PGP) by " -"switching the toggle to *enabled*." +#: ../system/data-privacy.rst:79 +msgid "**Delete organizations**" msgstr "" -#: ../system/integrations/pgp/index.rst:39 +#: ../system/data-privacy.rst:69 msgid "" -"You can add keys by clicking the *add key* button. The keys can be imported " -"from a file or you can paste the content of the key in the text box." +"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:" msgstr "" -#: ../system/integrations/pgp/index.rst:42 -msgid "**Which keys do I have to import?**" +#: ../system/data-privacy.rst:0 +msgid "Deleting an organization via the user deletion dialog" msgstr "" -#: ../system/integrations/pgp/index.rst:44 +#: ../system/data-privacy.rst:78 msgid "" -"For **signing** *outgoing* emails, you have to import the private key of " -"your Zammad email account." +"If this option does not appear, make sure there are no pending deletion " +"tasks for other customers from this organization." msgstr "" -#: ../system/integrations/pgp/index.rst:47 -msgid "" -"For **encrypting** *outgoing* emails, you have to import the public key of " -"the customer's email account." +#: ../system/data-privacy.rst:82 +msgid "Step 2: Monitor Deletion Job Status" msgstr "" -#: ../system/integrations/pgp/index.rst:50 +#: ../system/data-privacy.rst:84 msgid "" -"For **verifying the signature** of signed *incoming* emails, you have to " -"import the public key of the customer." +"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:" msgstr "" -#: ../system/integrations/pgp/index.rst:53 -msgid "" -"For **decrypting** of encrypted *incoming* emails, you have to import the " -"private key of your Zammad email account." +#: ../system/data-privacy.rst:98 +msgid "**in the Activity Stream**" msgstr "" -#: ../system/integrations/pgp/index.rst:57 -msgid "Import Keys From a File" +#: ../system/data-privacy.rst:0 +msgid "Activity Stream showing data privacy tasks" msgstr "" -#: ../system/integrations/pgp/index.rst:58 -msgid "You can import keys from a file in the section **Upload key**:" +#: ../system/data-privacy.rst:94 +msgid "" +"For each deleted user, the Activity Stream will be updated twice—once when " +"the task is created, and once when it's complete." msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of adding a key via file" +#: ../system/data-privacy.rst:97 +msgid "" +"These notifications are only visible to users with ``admin.data_privacy`` " +"permissions." msgstr "" -#: ../system/integrations/pgp/index.rst:64 +#: ../system/data-privacy.rst:0 msgid "" -"**Supported file formats:** ASCII-armor as well as binary GPG format " -"(basically any GPG supported key format) is supported here." +"The task list within Data Privacy shows removals being in progress and " +"completed." msgstr "" -#: ../system/integrations/pgp/index.rst:68 -msgid "Import Keys by Pasting the Content" +#: ../system/data-privacy.rst:107 +msgid "Frequently Asked Questions" msgstr "" -#: ../system/integrations/pgp/index.rst:69 -msgid "You can also paste the key's content in the section **paste key**:" +#: ../system/data-privacy.rst:121 +msgid "What happens if I receive an email from a deleted customer?" msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of adding a key via pasting" +#: ../system/data-privacy.rst:110 +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/integrations/pgp/index.rst:75 +#: ../system/data-privacy.rst:115 msgid "" -"**Supported format:** Please note that only ASCII-armor is supported here." +"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**." msgstr "" -#: ../system/integrations/pgp/index.rst:78 -msgid "Deleting Keys" +#: ../system/data-privacy.rst:130 +msgid "What about user information stored in internal notes or other messages?" msgstr "" -#: ../system/integrations/pgp/index.rst:79 +#: ../system/data-privacy.rst:124 msgid "" -"If you want to delete a specific key, you can do it by clicking on the menu " -"in the *actions* column and select **delete**:" +"The deletion process removes **user accounts and associated tickets only**." msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of deleting a key" +#: ../system/data-privacy.rst:126 +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." msgstr "" -#: ../system/integrations/pgp/index.rst:88 -msgid "Downloading Keys" +#: ../system/data-privacy.rst:137 +msgid "I deleted an user and can still see a message they sent!" msgstr "" -#: ../system/integrations/pgp/index.rst:89 +#: ../system/data-privacy.rst:133 msgid "" -"If you want to download your keys, you can do this as well via corresponding " -"action buttons. Depending on the key, you can choose wether you want to " -"download the private or the public key." +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:95 -#: ../system/integrations/smime/manage-certificates.rst:76 -msgid "Default Behavior" +#: ../system/data-privacy.rst:141 +msgid "I removed a customer, now my reporting is off!" msgstr "" -#: ../system/integrations/pgp/index.rst:96 +#: ../system/data-privacy.rst:140 msgid "" -"Here you can adjust on per group basis, if *sign* and *encryption* is on or " -"off by default. Please be aware, that agents can always override the setting " -"for each individual article." +"When removing users and their tickets, all references are removed. This also " +"affects e.g. Reporting - these information are lost." msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Adjusting default behavior on per group basis" +#: ../system/data-privacy.rst:145 +msgid "How long does Zammad store created tasks?" msgstr "" -#: ../system/integrations/pgp/index.rst:107 +#: ../system/data-privacy.rst:144 msgid "" -"Here you can see the last actions regarding signing and encryption and if " -"they were successful." -msgstr "" - -#: ../system/integrations/pgp/index.rst:117 -msgid "**Sign button is not visible, but keys are imported.**" +"Please see the on-premise data section of the :docs:`data privacy ` chapter." msgstr "" -#: ../system/integrations/pgp/index.rst:115 -msgid "Did you choose a group in the ticket?" +#: ../system/data-privacy.rst:150 +msgid "What about re-assigned tickets? I want to delete them, too." msgstr "" -#: ../system/integrations/pgp/index.rst:116 +#: ../system/data-privacy.rst:148 msgid "" -"Did you import a private key for the email adress, which is used for " -"outgoing emails in the group?" +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:122 -msgid "**How to obtain keys?**" +#: ../system/data-privacy.rst:154 +msgid "Why are there so many deletion task entries, I didn't create them!" msgstr "" -#: ../system/integrations/pgp/index.rst:120 +#: ../system/data-privacy.rst:153 msgid "" -"You can create them yourself! There are some good tutorials on the web on " -"how to create them. Providing keys to Zammad is a prerequisite to use the " -"PGP feature." -msgstr "" - -#: ../system/integrations/pgp/index.rst:127 -msgid "**It says a passphrase is needed, but I haven't got one.**" +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:125 -msgid "" -"If the key is secured with a passphrase, you have to provide it for the " -"import in Zammad. It is possible that keys may have an empty passphrase. " -"However, this is *not* recommended." +#: ../system/integrations/checkmk/admin-panel-reference.rst:2 +msgid "Admin Panel Reference" msgstr "" -#: ../system/integrations/pgp/index.rst:132 -msgid "**How do my customers get my new key?**" +#: ../system/integrations/checkmk/admin-panel-reference.rst:None +msgid "Screenshot of Checkmk settings overview" msgstr "" -#: ../system/integrations/pgp/index.rst:130 +#: ../system/integrations/checkmk/admin-panel-reference.rst:12 msgid "" -"You have to provide your **public** key in advance. Your customer also has " -"to configure PGP in their email workflow and import your public key. The " -"other way round, you have to get the public key of your customer and have to " -"import it to Zammad." +"Which :doc:`group ` should Checkmk tickets be assigned " +"to as a default (*i.e.,* when none is specified)?" msgstr "" -#: ../system/integrations/slack.rst:2 -msgid "Slack" +#: ../system/integrations/checkmk/admin-panel-reference.rst:15 +msgid "(Applies to :ref:`API alerts ` only.)" msgstr "" -#: ../system/integrations/slack.rst:4 -msgid "**⚠️ Deprecation warning ⚠️**" +#: ../system/integrations/checkmk/admin-panel-reference.rst:21 +msgid "Auto close" msgstr "" -#: ../system/integrations/slack.rst:6 +#: ../system/integrations/checkmk/admin-panel-reference.rst:18 msgid "" -"Zammad 7 will no longer support this dedicated Slack integration. It is " -"recommended to switch to :doc:`pre-defined webhooks ` instead. Existing Slack integrations should " -"be migrated manually before this feature is dropped." +"Should Zammad automatically close tickets if a service has recovered on its " +"own?" msgstr "" -#: ../system/integrations/slack.rst:14 -msgid "" -"In order to use this feature, please add a new Slack app to your Workspace. " -"The App you need is called ``Incoming WebHooks`` ." +#: ../system/integrations/checkmk/admin-panel-reference.rst:21 +msgid "(Agents will receive notifications for such closures as appropriate.)" msgstr "" -#: ../system/integrations/slack.rst:18 -msgid "Why Do I Need This Feature?" +#: ../system/integrations/checkmk/admin-panel-reference.rst:30 +msgid "Auto-close state" msgstr "" -#: ../system/integrations/slack.rst:20 -msgid "" -"If you're already using Slack for your team communication, you'll love this " -"feature! Our Slack integration can push ticket notifications about the last " -"ticket article based on the following events:" +#: ../system/integrations/checkmk/admin-panel-reference.rst:24 +msgid "What ticket state should be applied when “auto-closing” a ticket?" msgstr "" -#: ../system/integrations/slack.rst:24 -msgid "on Ticket creation" +#: ../system/integrations/checkmk/admin-panel-reference.rst:26 +msgid "" +"You can choose from the seven built-in ticket states. If these states aren't " +"enough for you, you can :ref:`define a new ticket state ` for this purpose as well. This can be useful for tracking " +"tickets with :doc:`reports `, for example." msgstr "" -#: ../system/integrations/slack.rst:25 -msgid "on Ticket updates" +#: ../system/integrations/checkmk/admin-panel-reference.rst:35 +#: ../system/integrations/cti/includes/recent-logs.include.rst:2 +#: ../system/integrations/ldap/index.rst:74 +#: ../system/integrations/pgp/index.rst:106 +msgid "Recent Logs" msgstr "" -#: ../system/integrations/slack.rst:26 -msgid "on reached reminders" +#: ../system/integrations/checkmk/admin-panel-reference.rst:None +msgid "Screenshot of Checkmk \"Recent Logs\" section" msgstr "" -#: ../system/integrations/slack.rst:27 -msgid "a Ticket has escalated" +#: ../system/integrations/checkmk/admin-panel-reference.rst:41 +msgid "" +"If you're having trouble getting Zammad and Checkmk to play nicely together, " +"this section can help you troubleshoot." msgstr "" -#: ../system/integrations/slack.rst:28 -msgid "a Ticket is going to escalate" +#: ../system/integrations/checkmk/admin-panel-reference.rst:44 +msgid "" +"It contains a record of the fifty most recent transactions that Zammad knows " +"about, including each one's request/response details and return status." msgstr "" -#: ../system/integrations/slack.rst:30 -msgid "" -"Zammad will provide the Ticket title, a direct link to the Ticket, the event " -"type (creation, updated, escalation), the customer, time and the last " -"article that has triggered the notification." +#: ../system/integrations/checkmk/api-reference.rst:2 +msgid "API Reference" msgstr "" -#: ../system/integrations/slack.rst:34 +#: ../system/integrations/checkmk/api-reference.rst:4 msgid "" -"This will give you further options, as you can see e.g. escalating tickets " -"that are assigned to an agent that's e.g. absent. You can interact faster, " -"as you might see problems earlier (or even before the problem gets one)." +"For most users, :ref:`the sample scripts from the Setup Guide ` will do the job just fine. But if you want more fine-grained control" +"—for instance, to create high- and low-priority tickets for different types " +"of system events—then you'll have to customize the data those scripts send " +"to Zammad." msgstr "" -#: ../system/integrations/slack.rst:38 +#: ../system/integrations/checkmk/api-reference.rst:15 msgid "" -"If needed and wanted, you can even discuss directly about the topic before " -"sending an answer to the customer. Another possible use case would be a " -"agent monitoring new agents and their answers to tickets." +"This custom script will automatically set all tickets it creates to **high " +"priority** and **assign them to charlie@chrispresso.com**." msgstr "" -#: ../system/integrations/slack.rst:44 -msgid "Configure the Integration" +#: ../system/integrations/checkmk/api-reference.rst:32 +msgid "How Does it Work?" msgstr "" -#: ../system/integrations/slack.rst:46 +#: ../system/integrations/checkmk/api-reference.rst:34 msgid "" -"First of all, please go to your slack workspace - go to administration => " -"Manage Apps. If you don't have an app yet, you can simply add a new one - " -"just search for ``Incoming WebHooks`` and customize the app to your needs." +"There are two kinds of data you can pass to the API, both in the form of key-" +"value pairs:" msgstr "" -#: ../system/integrations/slack.rst:50 -msgid "" -"Choose (or create) the channel Zammad should post it's information to and " -"press on \"Add Incoming WebHooks integration\". If you're ready, copy the " -"provided WebHook URL and go to your Zammad installation." +#: ../system/integrations/checkmk/api-reference.rst:44 +msgid "Checkmk parameters" msgstr "" -#: ../system/integrations/slack.rst:56 +#: ../system/integrations/checkmk/api-reference.rst:38 msgid "" -"You need administrative rights on the Slack Workspace. The link to the app " -"directory is normally ``https://[workspace-name].slack.com/apps`` ." +"are required, and make up the **contents** of the resulting tickets/" +"articles. They also determine whether an event creates a new ticket or " +"updates/closes an existing one." msgstr "" -#: ../system/integrations/slack.rst:63 +#: ../system/integrations/checkmk/api-reference.rst:42 msgid "" -"To configure the slack integration, log in to Zammad and go to Integrations " -"(System) => Slack in the admin panel." +"These are the only values used in the sample scripts. **Use them as-is**; " +"technically, they can be customized, but it's hard to imagine a good reason " +"for it." msgstr "" -#: ../system/integrations/slack.rst:66 -msgid "" -"Here you can choose on what evens Zammad should post information about a " -"ticket to your Slack channel. Next you need to device what groups shall be " -"affected by this, as anybody with access to that specific Slack channel can " -"read at least parts of the ticket this might be a privacy issue, if you " -"select the wrong groups. The username is simply the name that Zammad uses as " -"display name inside the Slack chat. The channel defines the Slack channel " -"the information is being posted in. As last option, you can set a custom " -"icon for posting to slack." +#: ../system/integrations/checkmk/api-reference.rst:52 +msgid "Ticket attributes" msgstr "" -#: ../system/integrations/slack.rst:74 +#: ../system/integrations/checkmk/api-reference.rst:47 msgid "" -"When you're ready, just hit \"Submit\" and enable the integration. Zammad " -"will now post new ticket information based on the trigger you chose. Below " -"the options you have the recent log that shows the latest requests to Slack " -"for debugging if needed." +"are optional, and can be used to **adjust settings** on newly created " +"tickets (*e.g.,* set the owner, group, priority, or state)." msgstr "" -#: ../system/integrations/slack.rst:81 +#: ../system/integrations/checkmk/api-reference.rst:50 msgid "" -"If you leave the Icon URL empty, Zammad will use the Zammad logo instead. " -"The icon should be a square PNG file." +"If you want to customize your Checkmk alert script, do it with these. Simply " +"add an extra “form” option for each one (``-F \"key=value\"``) to your " +"script's ``curl`` command line, as in the example above." msgstr "" -#: ../system/integrations/slack.rst:90 -msgid "" -"The following figure shows how it will look if you choose to receive updates " -"on created and updated tickets. On every post Zammad sends to the Slack " -"channel, you can create new threads to discuss about the new article." +#: ../system/integrations/checkmk/api-reference.rst:54 +msgid "💡 **It's just an API endpoint!**" msgstr "" -#: ../system/integrations/slack.rst:96 +#: ../system/integrations/checkmk/api-reference.rst:56 msgid "" -"If you just want to keep track of soon escalating or already escalated " -"tickets, it will look the the following figure. Zammad changes the color in " -"front of the post so you can easily see the state of the ticket." +"When using Checkmk integration, messages need to be formatted in a certain " +"way, but that *doesn't mean the messages actually have to come from Checkmk*." msgstr "" -#: ../system/integrations/slack.rst:102 +#: ../system/integrations/checkmk/api-reference.rst:59 msgid "" -"If you change the state, Zammad will also put information on what state the " -"ticket gets and (if pending state) the date until it pends. You'll also " -"recognize the color codes in front of posts on slack, as they are exact the " -"same the ticket state colors you'll see in Zammad!" +"If you use another monitoring tool that's not officially supported by " +"Zammad, there's probably a way to make it work with your Checkmk callback " +"URL." msgstr "" -#: ../system/integrations/smime/index.rst:2 -msgid "S/MIME" +#: ../system/integrations/checkmk/api-reference.rst:63 +msgid "Checkmk Parameters" msgstr "" -#: ../system/integrations/smime/index.rst:11 +#: ../system/integrations/checkmk/api-reference.rst:65 msgid "" -"S/MIME is the most widely-supported method for secure email communication. " -"With S/MIME, you can exchange **signed** and **encrypted** messages with " -"others." +"When a notification is received, Zammad creates a new article containing the " +"details of the event that triggered it:" msgstr "" -#: ../system/integrations/smime/index.rst:15 -msgid "" -"is proof that a message hasn't been tampered with or sent by an impersonator." +#: ../system/integrations/checkmk/api-reference.rst:None +msgid "Checkmk article body" msgstr "" -#: ../system/integrations/smime/index.rst:17 +#: ../system/integrations/checkmk/api-reference.rst:72 msgid "" -"In other words, it guarantees a message's **integrity** and **authenticity**." +"These details come from the fields listed below, which correspond to " +"parameters provided by Checkmk (``$NOTIFY_*``)." msgstr "" -#: ../system/integrations/smime/index.rst:22 -msgid "In other words, it guarantees **privacy** and **data security**." +#: ../system/integrations/checkmk/api-reference.rst:75 +msgid "**Required fields are marked with an asterisk (\\*).**" msgstr "" -#: ../system/integrations/smime/index.rst:28 -msgid "Screencast demo of S/MIME features for both new tickets and replies" +#: ../system/integrations/checkmk/api-reference.rst:79 +msgid "event_id\\*" msgstr "" -#: ../system/integrations/smime/index.rst:28 +#: ../system/integrations/checkmk/api-reference.rst:78 msgid "" -"Once S/MIME has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " -"appear in the ticket composer." +"A unique ID for the system event. (``$NOTIFY_SERVICEPROBLEMID`` / " +"``$NOTIFY_HOSTPROBLEMID``)" msgstr "" -#: ../system/integrations/smime/index.rst:32 -msgid ":doc:`🔪 Prerequisites `" +#: ../system/integrations/checkmk/api-reference.rst:86 +msgid "host\\*" msgstr "" -#: ../system/integrations/smime/index.rst:31 +#: ../system/integrations/checkmk/api-reference.rst:82 msgid "" -"New to S/MIME? This section helps you to find certificate providers and " -"points out Limitations." +"The hostname of the system that the event originated from. " +"(``$NOTIFY_HOSTNAME``)" msgstr "" -#: ../system/integrations/smime/index.rst:35 -msgid ":doc:`📝 Manage Certificates `" +#: ../system/integrations/checkmk/api-reference.rst:85 +msgid "" +"Used to determine if a new event belongs to an existing ticket. Also used in " +"the subject line of the resulting article (“ is ”)." msgstr "" -#: ../system/integrations/smime/index.rst:35 -msgid "Add and download certificates; configure group default behaviors." +#: ../system/integrations/checkmk/api-reference.rst:96 +msgid "service" msgstr "" -#: ../system/integrations/smime/index.rst:38 -msgid ":doc:`😦 Troubleshooting `" +#: ../system/integrations/checkmk/api-reference.rst:89 +msgid "" +"The name of the service that the event originated from. " +"(``$NOTIFY_SERVICEDESC``)" msgstr "" -#: ../system/integrations/smime/index.rst:38 -msgid "Took a wrong turn? About recent logs and common issues." +#: ../system/integrations/checkmk/api-reference.rst:92 +msgid "Used to determine if a new event belongs to an existing ticket." msgstr "" -#: ../system/integrations/smime/index.rst:43 -msgid "" -"For more details on how S/MIME integration works on the agent side, see the :" -"user-docs:`user docs `." +#: ../system/integrations/checkmk/api-reference.rst:94 +#: ../system/integrations/checkmk/api-reference.rst:110 +msgid "Displayed as ``-`` when omitted." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:2 -msgid "Manage Certificates" +#: ../system/integrations/checkmk/api-reference.rst:104 +msgid "state\\*" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:4 +#: ../system/integrations/checkmk/api-reference.rst:99 msgid "" -"S/MIME is **disabled by default**. Enable it to start adding certificates." +"The current state of the service or host in question. " +"(``$NOTIFY_SERVICESTATE`` / ``$NOTIFY_HOSTSTATE``)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:10 -msgid "Dialogue to add new certificates or private keys" +#: ../system/integrations/checkmk/api-reference.rst:102 +msgid "" +"Used to detect when a ticket should be auto-closed (*i.e.,* on ``OK``/" +"``UP``). Also used in the subject line of the resulting article (“ is " +"”)." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:10 +#: ../system/integrations/checkmk/api-reference.rst:110 +msgid "text" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:107 msgid "" -"Manage certificates in the Admin Panel under **System > Integrations > S/" -"MIME**. Certificates may be pasted in as plain text or uploaded from a file." +"The output of the process that triggered the event. " +"(``$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:14 -msgid "Add Certificate Data" +#: ../system/integrations/checkmk/api-reference.rst:121 +msgid "" +"The Object Manager attribute panel displays built-in and custom\n" +"attribute names." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:36 -msgid "Add Certificate" +#: ../system/integrations/checkmk/api-reference.rst:121 +msgid "Find a complete list of ticket attributes in the Object Manager." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:17 +#: ../system/integrations/checkmk/api-reference.rst:123 msgid "" -"Import public-key certificates for both your own organization and your " -"contacts." +"Ticket attributes are entirely optional, and can be used to customize the " +"tickets that Checkmk creates. (Note that these attributes will be ignored if " +"a new event belongs to an existing ticket.)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:19 +#: ../system/integrations/checkmk/api-reference.rst:128 msgid "" -"You can also add a bunch of certificates in one go by providing a single " -"file with all relevant certificates." +"Why would you want to do this? Maybe you have only one IT guy, and all " +"system monitoring issues should be automatically assigned to him. Or, maybe " +"you're creating multiple notification rules so that database outages take " +"higher priority than disk space warnings." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:22 -msgid "🕵️ **ALWAYS verify certificates in-person or over the phone!**" +#: ../system/integrations/checkmk/api-reference.rst:135 +msgid "In most cases, you'll probably want to set one of the following:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:24 -msgid "" -"The whole point of signatures is to alert you when someone is trying to " -"pretend to be someone they're not. Never accept a certificate from someone " -"online without verifying it first." +#: ../system/integrations/checkmk/api-reference.rst:137 +msgid "group" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:28 -msgid "📇 **What about trusted certificate authorities?**" +#: ../system/integrations/checkmk/api-reference.rst:139 +msgid "state" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:30 -msgid "" -"In some cases (e.g. when dealing with large enterprises), you may be given a " -"certificate for an entire CA, rather than a single contact. Add it here to " -"trust *all* certificates issued by that CA." +#: ../system/integrations/checkmk/api-reference.rst:140 +msgid "priority" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:35 +#: ../system/integrations/checkmk/api-reference.rst:142 msgid "" -"Commercial CAs can usually be verified online. Zammad does not include a " -"list of built-in, trusted CAs." +"but in practice, you can set almost any attribute, including :doc:`custom " +"ones you created through the Object Manager `." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:57 -msgid "Add Private Key" +#: ../system/integrations/checkmk/api-reference.rst:145 +msgid "Please note that the following attributes are **not customizable**:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:39 -msgid "" -"Once you've added a public-key certificate, you can import its matching " -"private key." +#: ../system/integrations/checkmk/api-reference.rst:147 +msgid "title" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:42 -msgid "" -"Private keys are for **your own organization only**; never ask your contacts " -"for their private keys." +#: ../system/integrations/checkmk/api-reference.rst:148 +msgid "id" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:0 -msgid "" -"S/MIME integration showing configured certificates and possible issues with " -"Logging" +#: ../system/integrations/checkmk/api-reference.rst:149 +msgid "ticket number" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:50 -msgid "" -"A note is displayed on certificates with a matching private key (see line 2)." +#: ../system/integrations/checkmk/api-reference.rst:151 +msgid "created_by_id" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:52 -msgid "📤 **Certificates and private keys must be uploaded separately.**" +#: ../system/integrations/checkmk/api-reference.rst:152 +msgid "updated_by_id" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:54 -msgid "" -"If your certificate and private key are bundled together in the same file or " -"PEM block, import it twice (once using each button)." -msgstr "" - -#: ../system/integrations/smime/manage-certificates.rst:57 -msgid "Please note that bulk imports of private keys are not possible." +#: ../system/integrations/checkmk/api-reference.rst:155 +msgid "Which Values Can Be Set?" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:60 -msgid "Download Certificate Data" +#: ../system/integrations/checkmk/api-reference.rst:157 +msgid "😵 **Invalid values → unpredictable behavior**" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:62 +#: ../system/integrations/checkmk/api-reference.rst:159 msgid "" -"You can download the earlier provided certificates and private keys at any " -"time from your Zammad instance." +"If you provide a value that Zammad doesn't understand (*e.g.,* ``-F " +"\"priority=high\"``), it's not always clear what will happen. In some cases, " +"a ticket will be created with the default values instead - but in others, it " +"may not be created at all!" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:65 -msgid "" -"Please note that passphrase-protected private keys stay protected and when " -"you download them, you have to know the passphrase to use them after " -"downloading." +#: ../system/integrations/checkmk/api-reference.rst:164 +msgid "So what values does Zammad understand, then? Well, it depends..." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:73 -msgid "Dialogue to download certificates or private keys" +#: ../system/integrations/checkmk/api-reference.rst:168 +msgid "Use an email address or username:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:73 -msgid "Download stored certificates and their keys" +#: ../system/integrations/checkmk/api-reference.rst:190 +msgid "group & priority" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:78 -msgid "" -"The ticket composer will set all outgoing messages to **signed and " -"encrypted** by default (assuming the required certificates exist)." +#: ../system/integrations/checkmk/api-reference.rst:175 +msgid "Refer to the dropdown menus in the ticket pane:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:82 -msgid "These defaults can be modified on a per-group basis:" +#: ../system/integrations/checkmk/api-reference.rst:0 +msgid "See possible values for certain attributes in the ticket pane." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:None -msgid "Zammad allowing to choose the default behavior on per group basis" +#: ../system/integrations/checkmk/api-reference.rst:187 +msgid "🙅 **Ticket state CANNOT be set this way!**" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:89 +#: ../system/integrations/checkmk/api-reference.rst:189 msgid "" -"Of course, agents can always manually change these settings on each email " -"they send out." +"Why? Because ``-F \"state=...\"`` is already used :ref:`as a Checkmk " +"parameter `." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:4 -msgid "A certificate *and* private key for your own organization" +#: ../system/integrations/checkmk/api-reference.rst:222 +msgid "Everything Else" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:6 +#: ../system/integrations/checkmk/api-reference.rst:193 msgid "" -"(Use this to ✒️ **sign outgoing messages** and 🔓 **decrypt incoming " -"messages**.)" +"To set any other attributes, it helps to know your way around the :docs:" +"`rails console `. Valid values are those that you can " +"set with a string:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:9 -msgid "" -"Certificates belonging your contacts, or their issuing certificate authority " -"(CA)" +#: ../system/integrations/checkmk/api-reference.rst:218 +msgid "These values can then be passed directly to the API:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:11 -msgid "" -"(Use these to ✅ **verify incoming message signatures** and 🔒 **encrypt " -"outgoing messages**.)" +#: ../system/integrations/checkmk/index.rst:16 +msgid "How does it work?" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:14 -msgid "🙋 **I'm new to S/MIME. Where can I get a certificate?**" +#: ../system/integrations/checkmk/index.rst:2 +msgid "Checkmk" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:16 +#: ../system/integrations/checkmk/index.rst:4 msgid "" -"The easiest way to get certificates is to buy an annual subscription through " -"a commercial CA, such as:" +"`Checkmk `_ is a powerful IT monitoring tool that can " +"send real-time status alerts to Zammad via email or REST API. Set these " +"alerts up in Checkmk, and Zammad will automatically create, update, and " +"close tickets based on the health of your system:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:19 -msgid "" -"`Sectigo (formerly Comodo) `_" +#: ../system/integrations/checkmk/index.rst:14 +msgid "Screenshot of ticket created by Checkmk notifications" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:20 -msgid "`Secorio `_" +#: ../system/integrations/checkmk/index.rst:14 +msgid "Multiple alerts, same ticket." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:21 -msgid "`GlobalSign `_" +#: ../system/integrations/checkmk/setup-guide.rst:2 +msgid "Setup Guide" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:23 -msgid "(Zammad is not affiliated with these CAs in any way.)" +#: ../system/integrations/checkmk/setup-guide.rst:4 +msgid "" +"Whenever the Checkmk integration is enabled, Zammad listens for messages on " +"its API and over email. As long as those messages follow the required " +"format, Zammad will create new tickets (or find and update existing ones) " +"based on the message contents." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:25 +#: ../system/integrations/checkmk/setup-guide.rst:10 msgid "" -"You can also generate your own self-signed certificates, but the process is " -"complicated and usually 🙅 **involves extra work for your contacts**." +"That means that “setting up Checkmk integration” is simply a matter of " +"**adding configuration to your Checkmk site**: telling it when to send these " +"messages and what to say. To do that, you'll need to create a new " +"**notification rule** (see `Checkmk's official docs `_ for help with that)." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:29 +#: ../system/integrations/checkmk/setup-guide.rst:17 msgid "" -"Bear in mind that 🤝 **S/MIME only works if the other party is using it, too." -"**" +"As part of this new rule, you'll have to choose a **notification method** " +"(*i.e.,* a script to execute whenever the rule is triggered). This script " +"will be written by you (samples below), and contain the logic for sending " +"API/email messages to Zammad:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:32 -msgid "Certificate and Private Key Checks on Upload" +#: ../system/integrations/checkmk/setup-guide.rst:26 +msgid "Checkmk \"New Rule\" dialog" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:34 +#: ../system/integrations/checkmk/setup-guide.rst:26 msgid "" -"The certificate and public key validation is based on the ``X509v3`` " -"extensions." +"Find your custom scripts in the Checkmk WATO under **Notifications > New " +"Rule > Notification Method**." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:49 -msgid "Uploading a *client certificate*?" +#: ../system/integrations/checkmk/setup-guide.rst:29 +msgid "" +"Once you're done setting up your new rule, you're all set! New tickets " +"should start coming in and auto-updating any time your rule is triggered." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:41 -msgid "The following attributes are required then:" +#: ../system/integrations/checkmk/setup-guide.rst:33 +msgid "" +"(If you need help troubleshooting, be sure to check the :ref:`checkmk-recent-" +"logs`.)" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:39 -msgid "Subject Alternative Name (at least one email address has to be present)" +#: ../system/integrations/checkmk/setup-guide.rst:38 +msgid "API Alerts" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:40 -msgid "Key Usage (``Digital Signature`` and/or ``Key Encipherment``)" +#: ../system/integrations/checkmk/setup-guide.rst:40 +msgid "" +"To add these scripts in the Checkmk WATO, copy them into your Checkmk " +"installation directory and make them executable. (Be sure to replace the " +"``zammad.example.com`` callback URL with the one found in your admin panel.)" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:41 -msgid "Public key algorithm (either ``RSA`` or ``EC``)" +#: ../system/integrations/checkmk/setup-guide.rst:60 +msgid "Service notification" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:43 +#: ../system/integrations/checkmk/setup-guide.rst:46 msgid "" -"The Extended Key Usage attribute is optional. If the certificate provides " -"the named attribute, than it must contain the value ``E-mail Protection``." +"For updates on the status of the software running on your server (*e.g.,* " +"postgres)." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:46 -msgid "" -"Please note that any usable email adress has to be prefixed with ``email:`` " -"or ``rfc822:``." +#: ../system/integrations/checkmk/setup-guide.rst:75 +msgid "Host notification" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:49 -msgid "The named public key algorithms are mandatory for private keys as well." +#: ../system/integrations/checkmk/setup-guide.rst:63 +msgid "For updates on the status of the server itself." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:54 -msgid "Uploading a *CA certificate*?" +#: ../system/integrations/checkmk/setup-guide.rst:77 +msgid "🤔 **What's with all the env vars?**" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:52 +#: ../system/integrations/checkmk/setup-guide.rst:79 msgid "" -"In the case of an uploaded CA certificate, providing the value ``CA:TRUE`` " -"in the attribute *Basic Contstraints*, the previously mentioned attributes " -"are not verified." +"Whenever Checkmk runs these scripts, it needs to provide some information " +"about the event that triggered the notification. This information is passed " +"in the form of these ``$NOTIFY_*`` environment variables." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:56 +#: ../system/integrations/checkmk/setup-guide.rst:85 msgid "" -"In general, the usage of any expired (``Not After``) or not yet valid (``Not " -"Before``) certificate is denied for outgoing emails." +"You can specify additional parameters to pass to the script when you're " +"setting up your notification rule, but the ones you see here are all " +"provided by default." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:59 -msgid "Example certificate:" +#: ../system/integrations/checkmk/setup-guide.rst:90 +msgid "Email Alerts" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:85 +#: ../system/integrations/checkmk/setup-guide.rst:94 msgid "" -"Please note that Zammad will distrust senders by default. This means that " -"you're always required to provide certificate data, no matter if for signing " -"or encrypting." +"🐞 **There are known bugs** in Zammad's processing of email from Checkmk. " +"This section will be completed once they have been resolved. (Learn more at " +"GitHub issues `#2377 `_ & " +"`#2180 `_.)" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:89 -msgid "This is by design and can't be adjusted." +#: ../system/integrations/checkmk/setup-guide.rst:100 +msgid "In the meantime, we encourage you to set up API alerts instead." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:4 -msgid "" -"All of the system's latest S/MIME activity is displayed in the **Recent " -"Logs** section." +#: ../system/integrations/clearbit.rst:2 +msgid "Clearbit" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:11 -msgid "Sample entries of in- and outgoing S/MIME related emails." +#: ../system/integrations/clearbit.rst:4 +msgid "" +"With our Clearbit integration, you can easily enrich the information " +"provided by Zammad. If the customers or agents email address is known to " +"Clearbit, it will share all information it has regarding the user with " +"Zammad. Those information can include the following:" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:11 -msgid "" -"Logs report the status and details of all mail, both incoming and outgoing, " -"that used signing/verification or encryption/decryption." +#: ../system/integrations/clearbit.rst:9 +msgid "Avatar" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:14 -msgid "" -"This log does **not** include email sent by :doc:`triggers ` or the :doc:`scheduler `. For those, check your " -"``production.log``." +#: ../system/integrations/clearbit.rst:10 +msgid "Address information" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:20 -msgid "Common Issues" +#: ../system/integrations/clearbit.rst:11 +msgid "Website information" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:30 -msgid "I received a signed/encrypted email before I set up S/MIME integration" +#: ../system/integrations/clearbit.rst:12 +msgid "A BIO (as Note by default)" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:23 +#: ../system/integrations/clearbit.rst:14 msgid "" -"No problem. Once S/MIME has been enabled and the appropriate certificates " -"have been added, agents will be prompted to retry verification/decryption on " -"matching emails." +"If needed, you can add further custom objects and add mappings to them, so " +"the Clearbit information can be filled within the database. In general you " +"can get any information from Clearbit, as long as you have a mapping to an " +"Zammad object." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:0 -msgid "Screenshot of user prompt to retry decryption" +#: ../system/integrations/clearbit.rst:21 +msgid "" +"Clearbit does have a mapping of fields like LDAP and Exchange have, but does " +"not \"win\" against Zammad information. This means that if you have e.g. the " +"last name field filled in already and Clearbit has other information on " +"that, it will not be updated." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:38 -msgid "The 🔒 **Encrypt** button is disabled" +#: ../system/integrations/clearbit.rst:26 +msgid "" +"However: If let's say the last name has been set by Clearbit and Zammad " +"notices that the last name on the Clearbit source has changed, Zammad will " +"also update this value." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:33 -msgid "Have you added the recipient's certificate?" +#: ../system/integrations/clearbit.rst:33 +msgid "" +"The configuration of Clearbit is really easy and done fast! Just login to " +"your Clearbit-Account, go to \"API\" and copy the secret-API-Key." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:34 -msgid "Are you sure the recipient's certificate is valid?" +#: ../system/integrations/clearbit.rst:38 +msgid "" +"Now change to your Zammad instance, go to Integrations (System) -> Clearbit " +"in the admin panel. Paste your API-Key into the API-Key-Field and decide if " +"Zammad should create unknown Organizations automatically, if the user does " +"not have one yet (and Clearbit knows it). The shared option decides if the " +"new organizations Zammad creates with Clearbit should be shared ones." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:35 -msgid "Have you checked your ``production.log`` for more details?" +#: ../system/integrations/clearbit.rst:47 +msgid "" +"If you're unsure what option to choose, better stick with \"no\". You can " +"also learn more about :doc:`/manage/organizations/index`." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:37 +#: ../system/integrations/clearbit.rst:52 msgid "" -"If encryption doesn't work in the composer, it won't work in :doc:`triggers " -"` or the :doc:`scheduler ` either!" +"The Mapping option works similar to the mapping within the Exchange and LDAP " +"sync. You can add further mappings for e.g. custom fields if you need more " +"information that Clearbit can provide." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:42 -msgid "The ✅ **Sign** button is disabled" +#: ../system/integrations/clearbit.rst:58 +msgid "" +"If you want to add more Clearbit fields and want to learn more about " +"available fields on their API, you can take a look at their `API " +"documentation `_." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:41 +#: ../system/integrations/clearbit.rst:62 msgid "" -"Have you added **both the certificate and private key** for your " -"organization?" +"If you're happy with the above chosen Settings and your mapping, just save " +"the changes and enable Clearbit integration. Zammad will now start polling " +"the Clearbit API as users contact you." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:42 +#: ../system/integrations/clearbit.rst:68 msgid "" -"Does the email address on the certificate match the email address of the " -"agent/group composing the email?" +"Zammad does not synchronize with Clearbit on a regular basis, but on demand " +"if needed. This saves API calls." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:45 -msgid "Error: “Fingerprint already taken”" +#: ../system/integrations/clearbit.rst:73 +msgid "" +"Below the Settings and Mappings, you'll find our Integration log. You can " +"see what requests Zammad sent to Clearbit and also the APIs Response." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:45 -msgid "Are you sure you haven't added this certificate already?" +#: ../system/integrations/clearbit.rst:78 +msgid "" +"By the way, you can also view the API log on the Clearbit website - the " +"information seen is basically the same." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:48 -msgid "Error: “❌ invalid byte sequence in UTF-8”" +#: ../system/integrations/clearbit.rst:84 +msgid "Example When Adding a User" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:48 -msgid "Please ensure to provide PEM formatted certificate and keys." +#: ../system/integrations/clearbit.rst:86 +msgid "" +"To show you how fast information is added, we added a small Screencast " +"below. This shows the creation of the User Alex from Clearbit. As we already " +"set the last name of Alex to \"X\", Zammad did not update it. What Zammad " +"did was to add further information it received from Clearbit." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:49 -msgid "Did you check if the provided file is a valid certificate or key?" +#: ../system/integrations/cti/generic.rst:2 +msgid "CTI (generic)" msgstr "" -#: ../system/integrations/zabbix.rst:2 -msgid "Zabbix Integration" +#: ../system/integrations/cti/includes/introduction.include.rst:1 +msgid "" +"This integration enables Zammad to provide a caller log to your agents. With " +"this your agents can greet your customers by their name and are supported by " +"Zammad with automatically opening a new ticket dialog or the user profile." msgstr "" -#: ../system/integrations/zabbix.rst:5 +#: ../system/integrations/cti/includes/introduction.include.rst:6 msgid "" -"This guide describes how to integrate your Zabbix 5.4 installation with " -"Zammad using the Zabbix webhook feature. This guide will provide " -"instructions on setting up a media type, a user and an action in Zabbix." +"Click the toggle next to the heading to activate or deactivate this " +"integration." msgstr "" -#: ../system/integrations/zabbix.rst:12 -msgid "Zammad with enabled HTTP Token Authentication" +#: ../system/integrations/cti/includes/introduction.include.rst:9 +msgid "" +"If you want to learn more on how your agents can use this function, please " +"refer the :user-docs:`user documentation `." msgstr "" -#: ../system/integrations/zabbix.rst:13 -msgid "Zabbix version 5.4 or higher" +#: ../system/integrations/cti/includes/introduction.include.rst:14 +msgid "" +"Automatically opening new ticket dialogues or user profiles requires agent " +"to extension mapping - see more below." msgstr "" -#: ../system/integrations/zabbix.rst:16 -msgid "Setting up a Zammad" +#: ../system/integrations/cti/includes/introduction.include.rst:20 +msgid "Please note the following limitations to reduce confusion later on:" msgstr "" -#: ../system/integrations/zabbix.rst:18 -msgid "Enable **API Token Access** in Settings > System > API." +#: ../system/integrations/cti/includes/introduction.include.rst:22 +msgid "CTI integrations provide caller log functions only." msgstr "" -#: ../system/integrations/zabbix.rst:20 +#: ../system/integrations/cti/includes/introduction.include.rst:23 msgid "" -"Create a **new user** for a Zabbix alerter with an **email address** and " -"create a personal user token with **ticket.agent** permissions." +"This integration does not provide any VoIP functionalities; you can't make " +"phone calls from within Zammad." msgstr "" -#: ../system/integrations/zabbix.rst:24 -msgid "Zabbix Webhook Configuration" +#: ../system/integrations/cti/includes/introduction.include.rst:25 +msgid "" +"If your browser supports ``tel``-URLs, you can click on phone numbers for " +"automatic dialing. This requires additional software / configuration on your " +"agent's computers." msgstr "" -#: ../system/integrations/zabbix.rst:27 -msgid "Create a Global Macro" +#: ../system/integrations/cti/generic.rst:9 +#: ../system/integrations/cti/placetel.rst:14 +#: ../system/integrations/cti/sipgate.rst:14 +msgid "Please provide the following requirements:" msgstr "" -#: ../system/integrations/zabbix.rst:29 +#: ../system/integrations/cti/generic.rst:11 msgid "" -"Before setting up the **Webhook**, you need to setup the global macro " -"**{$ZABBIX.URL}**, which must contain the **URL** to the **Zabbix frontend**." +"A telephone system that supports webhooks (outbound) (best option are those " +"that allow customizing the calls)." msgstr "" -#: ../system/integrations/zabbix.rst:33 -msgid "" -"In the **Administration** > **Media types** section, import the `Template`_." +#: ../system/integrations/cti/generic.rst:13 +msgid "A unique Call-ID during the call session." msgstr "" -#: ../system/integrations/zabbix.rst:38 -msgid "Open the added **Zammad** media type and set:" +#: ../system/integrations/cti/generic.rst:14 +msgid "Call event data (both numbers and direction)." msgstr "" -#: ../system/integrations/zabbix.rst:40 -msgid "**zammad\\_access\\_token** to the your **Personal User Token**" +#: ../system/integrations/cti/generic.rst:15 +msgid "Your Zammad instance must be reachable for your telephony system." msgstr "" -#: ../system/integrations/zabbix.rst:41 +#: ../system/integrations/cti/generic.rst:17 msgid "" -"**zammad\\_url** to the **frontend URL** of your **Zammad** installation" +"If you want to learn more on what kind of requests are supported by Zammad " +"and what it expects, please consult our :docs:`CTI-API documentation `." msgstr "" -#: ../system/integrations/zabbix.rst:43 -msgid "**zammad\\_customer** to your **Zammad user email**." +#: ../system/integrations/cti/generic.rst:22 +#: ../system/integrations/cti/placetel.rst:27 +#: ../system/integrations/cti/sipgate.rst:30 +msgid "Available Settings" msgstr "" -#: ../system/integrations/zabbix.rst:44 -msgid "" -"**zammad\\_enable\\_tags** to **true** or **false** to enable or disable " -"trigger tags. **Important**: if you enable tag support, each tag is set with " -"a separate request." +#: ../system/integrations/cti/generic.rst:29 +#: ../system/integrations/cti/placetel.rst:41 +#: ../system/integrations/cti/sipgate.rst:40 +msgid "Endpoint Settings" msgstr "" -#: ../system/integrations/zabbix.rst:48 +#: ../system/integrations/cti/generic.rst:25 msgid "" -"If you want to prioritize issues according to **severity** values in Zabbix, " -"you can define mapping parameters:" -msgstr "" - -#: ../system/integrations/zabbix.rst:51 -msgid "**severity\\_**: Zammad priority ID" -msgstr "" - -#: ../system/integrations/zabbix.rst:53 -msgid "Click the **Update** button to save the **Webhook** settings." +"Zammad will list your generic CTI endpoint here. It contains a unique token " +"so ensure to keep this URL save." msgstr "" -#: ../system/integrations/zabbix.rst:55 +#: ../system/integrations/cti/generic.rst:28 msgid "" -"To receive notifications in **Zammad**, you need to create a **Zabbix user** " -"and add **Media** with the **Zammad** type." +"You'll need this endpoint for your PBX to talk to Zammad, see :docs:`CTI-API " +"documentation `." msgstr "" -#: ../system/integrations/zabbix.rst:58 +#: ../system/integrations/cti/includes/important-dont-forget-saving.include.rst:3 msgid "" -"For **Send to**: enter any text, as this value is not used, but is required." +"All following options **do not save automatically**. Always use the Save " +"button on the lower end of the integration page!" msgstr "" -#: ../system/integrations/zabbix.rst:61 -msgid "" -"For more information, use the `Zabbix documentation `_." +#: ../system/integrations/cti/generic.rst:43 +#: ../system/integrations/cti/placetel.rst:49 +#: ../system/integrations/cti/sipgate.rst:52 +msgid "Call Settings" msgstr "" -#: ../system/maintenance.rst:2 -msgid "Maintenance" +#: ../system/integrations/cti/generic.rst:39 +#: ../system/integrations/cti/placetel.rst:49 +#: ../system/integrations/cti/sipgate.rst:37 +#: ../system/integrations/cti/sipgate.rst:50 +msgid "Inbound" msgstr "" -#: ../system/maintenance.rst:4 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:1 msgid "" -"Zammad comes with a maintenance mode that you can use for e.g. updating the " -"instance or changing settings while restricting availability and functions." +"This option allows you to block specific incoming caller IDs. It allows you " +"to temporarily reject e.g. spam callers without having to contact providers " +"or PBX administrators." msgstr "" -#: ../system/maintenance.rst:13 -msgid "Mode" +#: ../system/integrations/cti/includes/inbound-calls.include.rst:11 +msgid "Caller ID to block" msgstr "" -#: ../system/maintenance.rst:8 -msgid "The mode setting allows you to enable or disable the maintenance mode." +#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 +msgid "Provide caller IDs to block in ``E.164`` format." msgstr "" -#: ../system/maintenance.rst:10 -msgid "Defaults to *off*." +#: ../system/integrations/cti/includes/inbound-calls.include.rst:8 +msgid "" +"Your telephony system has to support this function. Zammad will send a " +"``reject`` response which will cause your telephony system to hang up the " +"call. To callers this usually will feel like the line is busy." msgstr "" -#: ../system/maintenance.rst:12 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:14 msgid "" -"The maintenance mode will restrict access to administrative roles only. This " -"means agents and customers are logged off." -msgstr "" - -#: ../system/maintenance.rst:23 -msgid "@Login" -msgstr "" - -#: ../system/maintenance.rst:16 -msgid "" -"This setting allows you to provide a login message within a green banner " -"above the login screen. Click into the green banner in the settings page to " -"adjust your message. To activate the message, activate the *@Login* setting." -msgstr "" - -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing the default login message within the\n" -"settings page" -msgstr "" - -#: ../system/maintenance.rst:26 -msgid "" -"Send an informative message to **all active sessions**. This comes handy to " -"inform your agents e.g. about mayor outages or to force reloads after " -"configuration changes." -msgstr "" - -#: ../system/maintenance.rst:31 -msgid "This is the messages title (slightly bigger than the normal message)." -msgstr "" - -#: ../system/maintenance.rst:34 -msgid "The text you want to provide to your logged in sessions." -msgstr "" - -#: ../system/maintenance.rst:39 -msgid "Reload application" -msgstr "" - -#: ../system/maintenance.rst:37 -msgid "" -"Selecting this option will change the message acceptance button from *Close* " -"(with nothing happening) to *Continue session*, which forces the application " -"to reload." -msgstr "" - -#: ../system/maintenance.rst:43 -msgid "" -"If you have customers that are logged in to Zammad, they'll also be notified " -"if they're active in that moment." -msgstr "" - -#: ../system/maintenance.rst:48 -msgid "Example without reload application" +"Provide a meaningful note for your fellow administrators to remind yourself " +"why you've chosen to block the number." msgstr "" -#: ../system/maintenance.rst:52 -msgid "" -"Message setting within Zammad's admin settings without ticket reload " -"application setting." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:17 +#: ../system/integrations/cti/sipgate.rst:40 +msgid "Outbound" msgstr "" -#: ../system/maintenance.rst:0 +#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:1 msgid "" -"Screenshot showing the send message settings without ticket\n" -"reload application set" +"In many cases you may want to use a different caller ID depending on the " +"destination you're calling. This may apply due to specific connection rates " +"to other countries or because you want your customer to feel you're calling " +"from the same country." msgstr "" -#: ../system/maintenance.rst:61 ../system/maintenance.rst:85 -msgid "" -"The modal all other active sessions will see upon pressing *Send to clients*." +#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:6 +msgid "This option expects ``E.164`` number formats." msgstr "" -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing modal caused by maintenance's message\n" -"without reload application ticket" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 +msgid "Destination caller ID" msgstr "" -#: ../system/maintenance.rst:72 -msgid "Example with reload application" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:5 +msgid "The caller ID or number you're trying to call." msgstr "" -#: ../system/maintenance.rst:76 -msgid "" -"Message setting within Zammad's admin settings with ticket reload " -"application setting." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:7 +msgid "You can use wildcards for e.g. country specific outbound numbers like:" msgstr "" -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing the send message settings with ticket\n" -"reload application set" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:9 +msgid "``49*`` for Germany" msgstr "" -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing modal caused by maintenance's message\n" -"with reload application ticket" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:10 +msgid "``4930*`` for Berlin / Germany landlines" msgstr "" -#: ../system/monitoring.rst:2 -msgid "Monitoring" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 +msgid "``33*`` for France" msgstr "" -#: ../system/monitoring.rst:4 -msgid "" -"This function is only available in self hosted instances. If you use Zammad " -"in our cloud, we are monitoring the system on our own and take steps to fix " -"potential problems directly." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:15 +msgid "Set Outbound caller ID" msgstr "" -#: ../system/monitoring.rst:11 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:14 msgid "" -"On the monitoring page, you can see the current health state of Zammad under " -"\"*Current Status*\" at the bottom. This can be useful if you want to have a " -"look if everything is up and running. As an example, you could have a look " -"in the monitoring when you assume that some emails aren't processed from " -"Zammad." +"The outbound caller ID to set (the number your customer sees on his display) " +"in ``E.164`` number format." msgstr "" -#: ../system/monitoring.rst:17 -msgid "**Can't receive an email and the monitoring response is \"healthy\"?**" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 +msgid "Provide a short description for fellow administrators." msgstr "" -#: ../system/monitoring.rst:19 +#: ../system/integrations/cti/includes/generic-cti-support-note.includes.rst:3 msgid "" -"Zammad will just inform you about unprocessable emails. This is not the case " -"for oversized emails. You can adjust the maximum email size in :doc:`../" -"channels/email/settings`." +"This option requires your PBX to send a specific request to Zammad *before " +"dialing*. Please consult the :docs:`CTI API ` in case " +"you're not sure." msgstr "" -#: ../system/monitoring.rst:24 -msgid "Monitoring API" +#: ../system/integrations/cti/generic.rst:52 +#: ../system/integrations/cti/placetel.rst:54 +#: ../system/integrations/cti/sipgate.rst:59 +msgid "Other Settings" msgstr "" -#: ../system/monitoring.rst:26 +#: ../system/integrations/cti/includes/other-settings-intro.include.rst:1 msgid "" -"Beside the indication in the monitoring page, you can also use an external " -"monitoring tool to monitor Zammad's health. To request the health of Zammad, " -"you need to provide the API key (token) to the external monitoring tool. You " -"can copy the token from the \"*Current Token*\" field as well as the whole " -"API endpoint of your system (\"*Health Check*\" field), in which the API " -"token is already included." +"Below you can find all available additional settings for this CTI " +"integration. For your overview we're sorting them by appearance and " +"reference their description first." msgstr "" -#: ../system/monitoring.rst:37 -msgid "Screenshot showing Current Token and Health Check" +#: ../system/integrations/cti/includes/default-caller-id.include.rst:2 +#: ../system/integrations/cti/includes/default-caller-id.include.rst:1 +msgid "Default caller ID for outbound calls" msgstr "" -#: ../system/monitoring.rst:37 -msgid "Screenshot showing Token and Health Check" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:16 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:15 +msgid "Shown records in caller log" msgstr "" -#: ../system/monitoring.rst:39 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:2 msgid "" -"In addition to that, you can reset the auto-generated token to make sure " -"that already configured monitoring systems won't work anymore. So, please " -"use this \"*Reset*\" button only if you know what you do!" -msgstr "" - -#: ../system/monitoring.rst:44 -msgid "Example Output" -msgstr "" - -#: ../system/monitoring.rst:0 -msgid "No issues found" -msgstr "" - -#: ../system/monitoring.rst:48 ../system/monitoring.rst:60 -msgid "**Indicator in Zammad**:" -msgstr "" - -#: ../system/monitoring.rst:0 -msgid "Screenshot showing monitoring with no issues" -msgstr "" - -#: ../system/monitoring.rst:54 ../system/monitoring.rst:66 -msgid "**API response**::" -msgstr "" - -#: ../system/monitoring.rst:0 -msgid "Issues were found" -msgstr "" - -#: ../system/monitoring.rst:0 -msgid "Screenshot showing monitoring with issues" -msgstr "" - -#: ../system/objects.rst:2 -msgid "Objects" +"Allows you to set the number of shown caller log entries for all users. You " +"can choose from the following values:" msgstr "" -#: ../system/objects.rst:4 -msgid "" -"In Zammad you can add your own fields to tickets, users, organizations and " -"even groups (these are called \"objects\"). This can be useful if you need " -"to add further information to a ticket or any other object in Zammad and the " -"information doesn't fit in any existing field." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:5 +msgid "60 (default)" msgstr "" -#: ../system/objects.rst:11 -msgid "" -"Try to avoid deleting attributes (and disable them instead) as Zammad might " -"run into unexpected conditions if they are referenced somewhere." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:6 +msgid "120" msgstr "" -#: ../system/objects.rst:16 -msgid "" -"Here's an overview of object attributes. On the upper right you can add new " -"attributes. By default, there will be no custom fields - standard attributes " -"will be grayed out, you can't delete or change those. You can edit custom " -"attributes (they are displayed in black font and have a trash bin on the " -"right side) just by clicking on them." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:7 +msgid "180" msgstr "" -#: ../system/objects.rst:24 -msgid "" -"Attributes you add to Zammad, no matter if they have default values or not, " -"will not update existing information. This means a new ticket field " -"technically will be empty unless you populate it." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:8 +msgid "240" msgstr "" -#: ../system/objects.rst:28 -msgid "" -"Especially in ticket scope this also means that newly added attributes will " -"be indicated as \"changed\" to agents that view the ticket. This may " -"interfere with Zammad's tabs behavior." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:9 +msgid "300" msgstr "" -#: ../system/objects.rst:40 -msgid "Ordering Attributes" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:11 +msgid "**🥵 Potential performance issue**" msgstr "" -#: ../system/objects.rst:42 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:13 msgid "" -"Since Zammad introduced :doc:`/system/core-workflows` the need to have a " -"custom positioning for attributes has become more important than ever." +"Setting this setting higher than 60 may cause serious performance issues on " +"very busy instances. Keep in mind that this setting causes Zammad to poll " +"and send up to 300 records to *all active agent sessions* in very short time " +"periods." msgstr "" -#: ../system/objects.rst:45 -msgid "" -"To adjust the position of such an attribute, simply click on the attribute " -"entry in question, scroll down and adjust the position number. Please note " -"that you cannot change the positioning of default attributes." +#: ../system/integrations/cti/generic.rst:73 +msgid "Caller Log Filter" msgstr "" -#: ../system/objects.rst:49 +#: ../system/integrations/cti/generic.rst:55 msgid "" -"In case two attributes have the same position value, Zammad will sort " -"alphabetically by name automatically." +"This function allows you to provide call information based on e.g. queues " +"only to agents that really need the information." msgstr "" -#: ../system/objects.rst:None +#: ../system/integrations/cti/generic.rst:58 msgid "" -"Screenshot showing custom attribute entries ordered in between default ones" +"Why? If you have a team for several countries or departments, you don't want " +"to bug your agents from other departments. Leaving these options empty will " +"fallback to showing everything to everyone." msgstr "" -#: ../system/objects.rst:56 -msgid "Updating Database After Adding or Editing Attributes" +#: ../system/integrations/cti/generic.rst:64 +msgid "Destination caller ID or Queue" msgstr "" -#: ../system/objects.rst:58 +#: ../system/integrations/cti/generic.rst:63 msgid "" -"When adding or changing attributes, Zammad will not apply the changes " -"instantly, but instead shows you the changed attributes first. If you're " -"ready to go, just click on \"Update database\" to apply the changes to " -"Zammad. If you made a mistake or just want to discard your changes, click " -"\"Discard changes\"." +"This depends on your PBX and usually is either a queue ID, phone number or " +"extension." msgstr "" -#: ../system/objects.rst:64 -msgid "" -"After applying the changes with \"Update Database\", a restart of Zammad is " -"**mandatory**. If you don't perform it, you may experience unexpected " -"behavior or even errors. You may want to do this kind of configuration " -"during maintenance windows." +#: ../system/integrations/cti/generic.rst:69 +msgid "Agents" msgstr "" -#: ../system/objects.rst:72 +#: ../system/integrations/cti/generic.rst:67 msgid "" -"Changes on objects require you to update the database to apply these changes." +"Select the agents that are responsible for the group. These agents will then " +"see caller log entries and call notifications fitting to said queue." msgstr "" -#: ../system/objects.rst:75 -msgid "**🤓 Service restarts can be automated**" +#: ../system/integrations/cti/generic.rst:0 +msgid "" +"Screenshot showing the caller log filter table with pre filled sample data" msgstr "" -#: ../system/objects.rst:0 -msgid "Hosted environments automatically restart for you." +#: ../system/integrations/cti/includes/recent-logs.include.rst:6 +msgid "" +"With recent logs Zammad allows you to view the latest calls for the CTI " +"functionality. This usually comes in handy, when you're looking for errors." msgstr "" -#: ../system/objects.rst:0 +#: ../system/integrations/cti/includes/recent-logs.include.rst:0 msgid "" -"If you're using a self-hosted installation you can use :docs:`environment " -"variables `" +"Screenshot showing several incoming requests within Recent logs section." msgstr "" -#: ../system/objects.rst:82 -msgid "System Attributes" +#: ../system/integrations/cti/includes/recent-logs.include.rst:16 +msgid "I'm just here to clear floats up." msgstr "" -#: ../system/objects.rst:84 +#: ../system/integrations/cti/includes/recent-logs.include.rst:20 msgid "" -"Zammad comes with pre-configured attributes. Some of them can't be edited " -"via UI (or at all). This is required for proper operation of Zammad and not " -"a bug." -msgstr "" - -#: ../system/objects.rst:90 -msgid "Ticket State" +"By clicking on the entry of interest, Zammad will provide more details on " +"the call in question. You'll see the payload it received and also the " +"response that was sent." msgstr "" -#: ../system/objects.rst:92 +#: ../system/integrations/cti/includes/recent-logs.include.rst:0 msgid "" -"If the pre-configured states aren't enough for you or you want to change " -"them, you can do so by clicking on the cogwheel icon in the state row in the " -"ticket tab. But you should be careful when changing pre-configured states. " -"This can lead to unwanted behavior in some cases." +"Screenshot showing detailed information of a specific log entry of recent " +"logs" msgstr "" -#: ../system/objects.rst:None -msgid "Screenshot showing highlighted ticket state attribute" +#: ../system/integrations/cti/includes/recent-logs.include.rst:31 +msgid "x" msgstr "" -#: ../system/objects.rst:122 -msgid "Handling of states" +#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 +#: ../system/integrations/cti/includes/troubleshooting.include.rst:9 +msgid "My Phone page stays blank, signalling does work..." msgstr "" -#: ../system/objects.rst:102 +#: ../system/integrations/cti/includes/troubleshooting.include.rst:5 msgid "" -"In the state configuration screen, you can add new states, disable states or " -"change states." +"If you've made sure that signalling works (check Recent logs) and your " +"Caller Log still stays empty, please ensure that you only configured one CTI " +"integration version. Specifically defining more than one agent mapping on " +"the different integration variants will be the issue." msgstr "" -#: ../system/objects.rst:0 -msgid "Screenshot showing table of default ticket states" +#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 +msgid "Clear the not needed agent mapping and reload your browser page." msgstr "" -#: ../system/objects.rst:110 +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:1 msgid "" -"To add a new state, click on the \"New Ticket State\" button in the top " -"right corner. To change an existing state, simply click on the affected " -"state. This opens an edit dialog." +"By mapping your agents extension to their existing Zammad users, Zammad can " +"provide a new ticket dialog or open the user profile for the agent that " +"picks up the call." msgstr "" -#: ../system/objects.rst:114 +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:5 msgid "" -"You can also clone a state or set them to \"Default for new tickets\" or " -"\"Default for follow-ups\" by clicking on the ⁝ action button and select the " -"desired function." +"This speeds up ticket aiding, no matter if it's for existing tickets or new " +"ones!" msgstr "" -#: ../system/objects.rst:118 +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:8 msgid "" -"*Default for new tickets* means that this state is used for every newly " -"created ticket." +"To see it work from the agent's perspective, have a look on :user-docs:`user " +"documentation `." msgstr "" -#: ../system/objects.rst:121 -msgid "" -"*Default for follow-ups* means that this state is used if the ticket is re-" -"opened after it was closed." +#: ../system/integrations/cti/placetel.rst:2 +msgid "Placetel CTI" msgstr "" -#: ../system/objects.rst:171 -msgid "Ticket state in detail" +#: ../system/integrations/cti/placetel.rst:16 +msgid "You need an administrative Placetel account for your organization." msgstr "" -#: ../system/objects.rst:125 +#: ../system/integrations/cti/placetel.rst:17 +#: ../system/integrations/cti/sipgate.rst:20 msgid "" -"Below you can find a description for each field and option. Please head over " -"to the :ref:`example ` to see the edit dialog." +"Your Zammad instance must be allowed to communicate to external services." msgstr "" -#: ../system/objects.rst:129 -msgid "" -"This is the name of the state and what you and your agents are seeing when " -"choosing a state somewhere (e.g. in tickets, trigger configuration)." +#: ../system/integrations/cti/placetel.rst:18 +msgid "Placetel must be able to reach your Zammad instance." msgstr "" -#: ../system/objects.rst:137 -msgid "" -"There are different state types you can choose from. By default, Zammad " -"comes with one state per state type." +#: ../system/integrations/cti/placetel.rst:22 +msgid ":doc:`provider-configurations/placetel`" msgstr "" -#: ../system/objects.rst:140 +#: ../system/integrations/cti/placetel.rst:21 msgid "" -"**new**: for states for tickets that are new and it hasn't been worked on " -"them" +"Learn how to configure Placetel to enable Zammad and Placetel to communicate " +"with each other." msgstr "" -#: ../system/objects.rst:142 +#: ../system/integrations/cti/placetel.rst:32 msgid "" -"**open**: for states for tickets that are in progress and agents are working " -"on them" -msgstr "" - -#: ../system/objects.rst:144 -msgid "**merged**: for states for tickets that are merged with other tickets" +"The here listed endpoint settings are relevant for the :doc:`integration " +"configuration with Placetel `." msgstr "" -#: ../system/objects.rst:145 -msgid "" -"**pending reminder**: for states for tickets that are in progress and you " -"want to set a reminder. (default example: *pending reminder*)" +#: ../system/integrations/cti/placetel.rst:37 +#: ../system/integrations/i-doit.rst:53 +msgid "Endpoint" msgstr "" -#: ../system/objects.rst:147 +#: ../system/integrations/cti/placetel.rst:36 msgid "" -"**pending action**: for states for tickets that are waiting for a specified " -"time and then change their state (default example: *pending close*)" +"This endpoint will be required for the Zammad integration within the " +"Placetel web interface." msgstr "" -#: ../system/objects.rst:150 -msgid "" -"**closed**: for states for tickets that are finished and do not need to be " -"processed further" +#: ../system/integrations/cti/placetel.rst:41 +msgid "API Token" msgstr "" -#: ../system/objects.rst:153 +#: ../system/integrations/cti/placetel.rst:40 msgid "" -"⚠️ Choosing the correct state type is important! If you are in doubt, have a " -"look on the default states and their types!" +"You'll receive this token within the ``Web API`` menu. Make sure to copy " +"this value, it's only shown once!" msgstr "" -#: ../system/objects.rst:158 -msgid "Ignore escalation" +#: ../system/integrations/cti/placetel.rst:71 +#: ../system/integrations/cti/sipgate.rst:77 +msgid "Phone Extension to Agent Mapping" msgstr "" -#: ../system/objects.rst:157 -msgid "" -"Here you can define whether tickets of this state will count to escalation " -"time or not." +#: ../system/integrations/cti/placetel.rst:0 +msgid "Screenshot showing sample user mappings in between Placetel and Zammad" msgstr "" -#: ../system/objects.rst:161 +#: ../system/integrations/cti/placetel.rst:64 msgid "" -"You can create a note for the state to inform other admins about the state. " -"This has no effect on tickets." +"You can find your agents Placetel username combination required within ⚙️ PBX " +"→ VoIP destinations. Within the \"Advanced settings\" section you're looking " +"for \"SIP user name\" and \"SIP server\"." msgstr "" -#: ../system/objects.rst:165 -msgid "Set the state to *active* or *inactive*." +#: ../system/integrations/cti/placetel.rst:68 +msgid "Combine these two like so: ``@``." msgstr "" -#: ../system/objects.rst:167 -msgid "" -"it is technically possible to set all states to inactive. To keep Zammad " -"working in such a case, the inactive flag of one of the states is ignored." +#: ../system/integrations/cti/placetel.rst:0 +msgid "Sample VoIP credentials for a Placetel user" msgstr "" -#: ../system/objects.rst:194 -msgid "Ticket state example" +#: ../system/integrations/cti/provider-configurations/placetel.rst:2 +msgid "Setup Placetel connection for Zammad" msgstr "" -#: ../system/objects.rst:174 +#: ../system/integrations/cti/provider-configurations/placetel.rst:6 msgid "" -"Let's assume we want to create a new state which indicates that the ticket " -"has to wait for a response of a third party (e.g. service contractor or " -"manufacturer) and we want to to be able to set a reminder." +"This configuration step requires a *full* administrative Placetel account. " +"You may receive forbidden error messages with Placetel in case your " +"permissions are not high enough." msgstr "" -#: ../system/objects.rst:178 +#: ../system/integrations/cti/provider-configurations/placetel.rst:10 msgid "" -"First we give the new state a proper name. In this example we call it " -"\"waiting for manufacturer\"." +"The following actions can be configured via the `Placetel web interface " +"`_." msgstr "" -#: ../system/objects.rst:181 -msgid "" -"As state type we choose \"pending reminder\". This indicates that the ticket " -"is still open and we can set a reminder. This reminder can be useful if our " -"manufacturer sometimes isn't responding or we want to remind him to give us " -"an answer." +#: ../system/integrations/cti/provider-configurations/placetel.rst:29 +msgid "Step 1: Activate Zammad integration" msgstr "" -#: ../system/objects.rst:186 +#: ../system/integrations/cti/provider-configurations/placetel.rst:14 msgid "" -"We choose \"no\" for \"ignore escalation\" because we want to escalate the " -"tickets even if we are waiting on the manufacturer's feedback." -msgstr "" - -#: ../system/objects.rst:189 -msgid "The **result** in the creation dialog will look like this:" +"Within Integrations, scroll down to Partner integrations and select Zammad." msgstr "" -#: ../system/objects.rst:0 -msgid "Screenshot showing ticket state creation dialog with example" +#: ../system/integrations/cti/provider-configurations/placetel.rst:17 +msgid "" +"You can alternatively filter by \"Ticket Systems\" to reduce the number of " +"entries on the page. You'll still want to look for Partner integrations. 🤓" msgstr "" -#: ../system/objects.rst:197 ../system/objects.rst:199 -msgid "Ticket Priority" +#: ../system/integrations/cti/provider-configurations/placetel.rst:21 +msgid "" +"Within the Zammad integration now press \"Activate\". A new tab ``API`` " +"becomes available - open this tab." msgstr "" -#: ../system/objects.rst:199 ../system/objects.rst:201 +#: ../system/integrations/cti/provider-configurations/placetel.rst:24 msgid "" -"If the pre-configured priorities aren't enough for you or you want to change " -"them, you can do so by clicking on the cogwheel icon in the priority row in " -"the ticket tab:" +"Now tick \"Enable Call Control / Notify API\" and paste the Placetel " +"endpoint from your Zammad instance into the field \"URL of your API " +"endpoint\". Save to apply the settings" msgstr "" -#: ../system/objects.rst:None -msgid "Screenshot showing highlighted ticket priority attribute" +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "Screencast showing how to activate the Zammad integration" msgstr "" -#: ../system/objects.rst:224 ../system/objects.rst:226 -msgid "Handling of priorities" +#: ../system/integrations/cti/provider-configurations/placetel.rst:51 +msgid "Step 2: Generate API Token for Placetel" msgstr "" -#: ../system/objects.rst:208 ../system/objects.rst:210 +#: ../system/integrations/cti/provider-configurations/placetel.rst:32 msgid "" -"In the priority configuration screen, you can add new priorities, disable " -"priorities or change priorities." +"Go back to the integrations page and scroll down to \"Web API\". Generate a " +"new API token by using the \"Create a new API token\" button." msgstr "" -#: ../system/objects.rst:0 -msgid "Screenshot showing table of default ticket priorities" +#: ../system/integrations/cti/provider-configurations/placetel.rst:37 +msgid "" +"If you already generated a token either use your existing token or reset it " +"by using above mentioned button. Placetel will ask you to conform this reset." msgstr "" -#: ../system/objects.rst:216 ../system/objects.rst:218 +#: ../system/integrations/cti/provider-configurations/placetel.rst:41 msgid "" -"To add a new priority, click on the \"New Priority\" button in the top right " -"corner. To change an existing priority, simply click on the affected " -"priority. This opens an edit dialog." +"Please keep in mind that existing API scripts may no longer work due to " +"token resets!" msgstr "" -#: ../system/objects.rst:220 ../system/objects.rst:222 +#: ../system/integrations/cti/provider-configurations/placetel.rst:44 msgid "" -"You can also clone a priority or set them to \"Default for new tickets\" by " -"clicking on the ⁝ action button and select the desired function." +"Copy the provided API token and insert it into the \"API Token\" field " +"within Zammad's Placetel integration." msgstr "" -#: ../system/objects.rst:223 ../system/objects.rst:225 +#: ../system/integrations/cti/provider-configurations/placetel.rst:47 msgid "" -"*Default for new tickets* means that this priority is used for every newly " -"created ticket." +"Apply your changes by using the \"Save\" button on the bottom of the " +"Placetel integration page and activate the Placetel integration." msgstr "" -#: ../system/objects.rst:246 ../system/objects.rst:248 -msgid "Priorities in detail" +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "" +"Screencast showing how to retrieve an API token from Placetel for Zammad" msgstr "" -#: ../system/objects.rst:227 ../system/objects.rst:229 -msgid "Below you can find a description for each field and option." +#: ../system/integrations/cti/provider-configurations/placetel.rst:73 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:77 +msgid "Step 3: Restrict the numbers to notify on" msgstr "" -#: ../system/objects.rst:230 ../system/objects.rst:232 +#: ../system/integrations/cti/provider-configurations/placetel.rst:54 msgid "" -"This is the name of the priority and what you and your agents are seeing " -"when choosing a priority somewhere (e.g. in tickets, trigger configuration)." +"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " +"the the Integrations page of the Placetel web interface, go to \"Notify " +"API\"." msgstr "" -#: ../system/objects.rst:240 ../system/objects.rst:242 -msgid "Highlight color" +#: ../system/integrations/cti/provider-configurations/placetel.rst:58 +msgid "" +"Lower on the page Placetel allows you to restrict the numbers to notify on. " +"You'll find this within the \"External routing API\" part." msgstr "" -#: ../system/objects.rst:235 ../system/objects.rst:237 +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 msgid "" -"Switch between *Low priority* (light blue), *High priority* (red) and - " -"(default). This affects the displayed color for ticket titles in overviews." +"Screenshot showing a sample selection of phone numbers to use for the " +"Placetels notify API" msgstr "" -#: ../system/objects.rst:239 ../system/objects.rst:241 -msgid "The color options are currently limited to the mentioned options." +#: ../system/integrations/cti/provider-configurations/placetel.rst:66 +msgid "" +"This menu point also provides a API request log from Placetel view. Just " +"open \"Recent responses of your API endpoint\" to learn more." msgstr "" -#: ../system/objects.rst:243 ../system/objects.rst:245 +#: ../system/integrations/cti/provider-configurations/placetel.rst:69 msgid "" -"You can create a note for the priority to inform other admins about the " -"priority. This has no effect on tickets." +"If you want to see Zammad's perspective, use the \"Recent Logs\" part from " +"within the Placetel integration page." msgstr "" -#: ../system/objects.rst:247 ../system/objects.rst:249 -msgid "Set the priority to *active* or *inactive*." +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "Screenshot showing sample log entries for Placetels API calls to Zammad" msgstr "" -#: ../system/objects/external-data-source-example.rst:2 -msgid "External Data Source" +#: ../system/integrations/cti/provider-configurations/placetel.rst:77 +msgid "Step 4 (optional): Further configurations for Placetel" msgstr "" -#: ../system/objects/external-data-source-example.rst:4 +#: ../system/integrations/cti/provider-configurations/placetel.rst:76 msgid "" -"We assume you already had a look on :doc:`types` where you can find a " -"description of the individual fields." +"If needed, you can now configure Zammad's Placetel integration in more " +"detail. You can learn more about your options here: :ref:`Placetel " +"integration settings `." msgstr "" -#: ../system/objects/external-data-source-example.rst:7 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:2 +msgid "Setup Sipgate connection for Zammad" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"To reproduce this example, choose a category you want to add a custom field, " -"click on *New Attribute* and select *External data source field* under " -"*Format*." +"Sipgate has no english web interface which is why this documentation page is " +"mixing up languages badly." msgstr "" -#: ../system/objects/external-data-source-example.rst:11 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"Our example story is to fetch data from an external product database. We " -"want to add our products to the tickets so that the products can be searched " -"and chosen from a list and also create a link to the product website." +"Please also note that the availability of API addons highly depends on your " +"package trier. Usage of sipgate.io packages *is not free*, please check " +"their `pricing page `_ before!" msgstr "" -#: ../system/objects/external-data-source-example.rst:16 -msgid "Base configuration" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:35 +msgid "Step 1: Book sipgate.io package" msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Initial steps to configure external data source object type" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:13 +msgid "Skip to step 2 if you already have the package booked!" msgstr "" -#: ../system/objects/external-data-source-example.rst:23 -#: ../system/variables.rst:85 -msgid "**Example:**" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:15 +msgid "" +"Login to an administrative Sipgate account and navigate to " +"``Accountverwaltung``. You'll see several different options depending on " +"your booked packages. Select ``Verträge & Produkte`` to continue." msgstr "" -#: ../system/objects/external-data-source-example.rst:25 -msgid "Name: *product*" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:19 +msgid "" +"Scroll down to the section ``Zusätzliche Produkte buchen`` and look for " +"``sipgate.io`` - select this product by using the ``Produkte anzeigen``-" +"Button." msgstr "" -#: ../system/objects/external-data-source-example.rst:26 -msgid "Display: *Product*" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:23 +msgid "" +"On the next page select either one of the ``sipgate.io`` packages or ``Push-" +"API Package Free``. Follow the dialogue by booking the addon. You'll be " +"returned to your contract overview and now should see the selected addon in " +"your list." msgstr "" -#: ../system/objects/external-data-source-example.rst:29 -msgid "External data source configuration" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:30 +msgid "" +"The availability for ``sipgate.io`` packages and their levels highly depends " +"on the overall account type and product you've booked with Sipgate." msgstr "" -#: ../system/objects/external-data-source-example.rst:31 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"First, enter the search URL making sure it contains ``#{search.term}`` as a " -"parameter:" +"Screencast showing the process on how to book the required sipgate.io addon" msgstr "" -#: ../system/objects/external-data-source-example.rst:34 -msgid "**Example:** ``https://dummyjson.com/products/search?q=#{search.term}``" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:52 +msgid "Step 2: Configure webhook for Zammad" msgstr "" -#: ../system/objects/external-data-source-example.rst:36 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:38 msgid "" -"After that, head down to the preview section and enter a search input for " -"the external data source." +"Within your ``Accountverwaltung`` navicate to your product ``sipgate.io``. " +"In the newly opened tab, switch from \"Clients\" to \"Webhooks\" and paste " +"the endpoint URLs from your Zammad instance like so:" msgstr "" -#: ../system/objects/external-data-source-example.rst:39 -msgid "**Example:** ``mac``" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:42 +msgid "Inbound endpoint to \"Incoming\"" msgstr "" -#: ../system/objects/external-data-source-example.rst:41 -msgid "Then you can find a preview of the response data below:" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:43 +msgid "Outbound endpoint to \"Outgoing\"" msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of JSON response based on search term" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:47 +msgid "" +"Ensure to select at least one call group or phoneline within \"Sources\". " +"Other wise Sipgate will not indicate any incoming or outgoing calls to " +"Zammad." msgstr "" -#: ../system/objects/external-data-source-example.rst:48 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"We recommend using the preview to have a look on the structure. There is a " -"top-level element called ``products``. One level below, you can find the " -"attributes ``id`` and ``title``." +"Screencast showing how to add Zammad's endpoint URLs to sipgate.ios webhook " +"configuration" msgstr "" -#: ../system/objects/external-data-source-example.rst:52 -msgid "**Search result response based on search from example:**" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:55 +msgid "" +"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " +"the Webhooks → URLs section of Sipgate you can select which *sources* " +"Sipgate should notify Zammad about in- and outgoing calls." msgstr "" -#: ../system/objects/external-data-source-example.rst:119 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:59 msgid "" -"To tell the remote system that the desired data is located below the " -"``products`` level, you have to put it in the field *Search result list key*." +"Use either specific phone lines or use the option \"Use for all phonelines " +"and groups\" to notify Zammad about all existing lines of your Sipgate " +"account." msgstr "" -#: ../system/objects/external-data-source-example.rst:122 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"After inserting ``products`` in the mentioned field, you get an extended " -"preview. You can find an additional box *Search result list* with a JSON " -"structure. This is the same response as before but stripped from the upper " -"``products`` element by the external data source." +"Screenshot showing a sample selection of phone numbers to use for the " +"Sipgates webhooks API" msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of JSON response search result list" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:68 +msgid "This section also allows you to enable a Debug log." msgstr "" -#: ../system/objects/external-data-source-example.rst:132 -msgid "" -"Now you need to provide the keys for the search result values and labels. As " -"already mentioned, we are looking for the ``id`` and the ``title`` of our " -"products. If you haven't already, it is now a good time to look at the " -"preview of the *Search result list*." +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "Screenshot showing an enabled Debug log option" msgstr "" -#: ../system/objects/external-data-source-example.rst:197 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:73 msgid "" -"After locating our two keys, we insert them in *search result value key* " -"(``id``) and in *Search result label key* (``title``)." +"After enabling you can use the Debug log section to see all sent webhook " +"calls to Zammad. You'll also can see the response." msgstr "" -#: ../system/objects/external-data-source-example.rst:200 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"Basically, we configured the external data source already and we can see a " -"table in the preview section:" -msgstr "" - -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of product table based on search term" +"Screenshot showing sample log entries for Sipgates webhook calls to Zammad" msgstr "" -#: ../system/objects/external-data-source-example.rst:208 -msgid "" -"According to our example story, now just the *Link template* is missing." +#: ../system/integrations/cti/provider-configurations/sipgate.rst:81 +msgid "Step 4 (optional): Further configurations for Sipgate" msgstr "" -#: ../system/objects/external-data-source-example.rst:210 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:80 msgid "" -"Please note that this is an optional feature. If you don't want to use such " -"links, of course you don't have to configure it." +"If needed, you can now configure Zammad's Sipgate integration in more " +"detail. You can learn more about your options here: :ref:`Sipgate " +"integration settings `." msgstr "" -#: ../system/objects/external-data-source-example.rst:213 -msgid "" -"We can add now an address where additional product information can be found." +#: ../system/integrations/cti/sipgate.rst:2 +msgid "Sipgate (sipgate.io)" msgstr "" -#: ../system/objects/external-data-source-example.rst:215 -msgid "Example: ``https://your_domain.com/q=#{ticket.product}``" +#: ../system/integrations/cti/sipgate.rst:16 +msgid "You need an administrative Sipgate account for your organization." msgstr "" -#: ../system/objects/external-data-source-example.rst:217 -msgid "In the example, the parameter means:" +#: ../system/integrations/cti/sipgate.rst:17 +msgid "" +"Zammad requires a ``sipgate.io`` addon from the feature store (please note " +"that API calls are not free with Sipgate. Rates may apply and differ from " +"account to account)." msgstr "" -#: ../system/objects/external-data-source-example.rst:219 -msgid "``#{}``: \"Frame\" for the insertion of information" +#: ../system/integrations/cti/sipgate.rst:21 +msgid "Sipgate must be able to reach your Zammad instance." msgstr "" -#: ../system/objects/external-data-source-example.rst:220 -msgid "``ticket``: object level, where you create your custom object" +#: ../system/integrations/cti/sipgate.rst:25 +msgid ":doc:`provider-configurations/sipgate`" msgstr "" -#: ../system/objects/external-data-source-example.rst:221 -msgid "``product``: name of the (custom) object" +#: ../system/integrations/cti/sipgate.rst:24 +msgid "" +"Learn how to configure Sipgate to enable Zammad and Sipgate to communicate " +"with each other." msgstr "" -#: ../system/objects/external-data-source-example.rst:223 +#: ../system/integrations/cti/sipgate.rst:33 msgid "" -"After configuring your *Link template*, there will be another column in the " -"preview. Hovering on the icons in the *Link* column will show you where it " -"forwards you." +"Below endpoint settings affect the :doc:`sipgate.io configuration `." msgstr "" -#: ../system/objects/external-data-source-example.rst:232 -msgid "" -"In our example, one of the links looks like: https://your_domain.com/q=6, " -"where the 6 is the product id." +#: ../system/integrations/cti/sipgate.rst:37 +msgid "This endpoint is required for incoming call hooks." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:40 +msgid "This endpoint is required for outgoing call hooks." msgstr "" -#: ../system/objects/external-data-source-example.rst:235 -msgid "You can find more information regarding the URL in :doc:`types`." +#: ../system/integrations/cti/sipgate.rst:0 +msgid "Screenshot showing sample user mappings in between Sipgate and Zammad" msgstr "" -#: ../system/objects/includes/adding-values-hint.include.rst:3 +#: ../system/integrations/cti/sipgate.rst:69 msgid "" -"Adding values can be tricky for first timers, don't forget to press \"➕ " -"Add\" after typing your values. Otherwise you may loose a value." +"You can find your agent's Sipgate username within ``Accountverwaltung → " +"Benutzer``. You're looking for the SIP-ID." msgstr "" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:1 -#: ../system/objects/includes/reposition-values.include.rst:1 -msgid "**↕️ This field type allows the positioning of its values ↔️**" +#: ../system/integrations/cti/sipgate.rst:0 +msgid "Sample VoIP credentials for a Sipgate user" msgstr "" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:3 -msgid "" -"In order to re-arrange the field values, first edit the field. Then you can " -"use ☰ to drag the values in question to the correct position. If you want to " -"change the layer depth, double click on ☰. With it you can cycle through the " -"available layers." +#: ../system/integrations/cti/sipgate.rst:77 +msgid "Users with several devices also have several SIP-IDs." msgstr "" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:8 -msgid "When you're ready, submit your changes to save the object attribute." +#: ../system/integrations/elasticsearch.rst:2 +msgid "Elasticsearch (SaaS)" msgstr "" -#: :0 ../system/objects/types.rst:0 +#: ../system/integrations/elasticsearch.rst:4 msgid "" -"Screencast showing how to re-position values on tree select like\n" -"fields" +"The Elasticsearch integration allows you to create a read-only user to use " +"with your favorite reporting tool (e.g. like Grafana)." msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:3 +#: ../system/integrations/elasticsearch.rst:7 msgid "" -"In order to re-arrange the field values, edit the field and scroll below the " -"values. Make sure to tick the option \"Use custom option sort\"." +"If you want to take full advantage of the Zammad reporting, have a look at " +"our :docs:`Grafana ` " +"setup page as well." msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:8 -msgid "" -"If you do not tick this field, all manual positioning you did above will be " -"lost upon saving! ☠️" +#: ../system/integrations/elasticsearch.rst:11 ../system/subscription.rst:7 +msgid "**🚧 Hosted environment specific 🚧**" msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:11 +#: ../system/integrations/elasticsearch.rst:13 msgid "" -"Now use ☰ to drag the values in question to the correct position. When " -"you're ready, submit your changes to save the object attribute." -msgstr "" - -#: :0 ../system/objects/types.rst:0 -msgid "Screencast showing how to re-position values" +"This integration is only available for Hosted setups. In order to use " +"Elasticsearch you'll need the **Plus** subscription." msgstr "" -#: ../system/objects/includes/url-template-hint.include.rst:3 +#: ../system/integrations/elasticsearch.rst:16 msgid "" -"This field allows using :ref:`URL fields (Link Templates) `." +"Self hosted users have all the control over their self hosted Elasticsearch " +"instances." msgstr "" -#: ../system/objects/permissions.rst:2 -msgid "Attribute Permissions" +#: ../system/integrations/elasticsearch.rst:None +msgid "Elasticsearch integration page on SaaS environments" msgstr "" -#: ../system/objects/permissions.rst:7 +#: ../system/integrations/elasticsearch.rst:27 msgid "" -"In the object attributes configuration you can define if a field is shown " -"and if the input in the field is mandatory, separated by different screens " -"and for different :doc:`roles/permissions `." +"Please note the following limitations of Elasticsearch access on hosted " +"environments:" msgstr "" -#: ../system/objects/permissions.rst:17 -msgid "Screenshot shows object attribute permission table" +#: ../system/integrations/elasticsearch.rst:30 +msgid "access to the Elasticsearch index is read-only access" msgstr "" -#: ../system/objects/permissions.rst:17 -msgid "" -"Some of the possible permissions and screen options for a user object " -"attribute." +#: ../system/integrations/elasticsearch.rst:31 +msgid "currently you're limited to user only" msgstr "" -#: ../system/objects/permissions.rst:19 +#: ../system/integrations/elasticsearch.rst:32 msgid "" -"Based on the object context (ticket, agent, organization, user), the " -"selectable roles (to be precise: the required permissions) and screens " -"differ. Be aware that these settings aren't affecting data creation via " -"other channels than the UI." +"Reporting tools that require to write into the indexes (like Kibana) are not " +"supported" msgstr "" -#: ../system/objects/permissions.rst:24 -msgid "" -"If you want to have further customization possibilities, you should have a " -"look at the :doc:`core workflows `." +#: ../system/integrations/elasticsearch.rst:34 +msgid "IP access restriction is currently not yet supported" msgstr "" -#: ../system/objects/permissions.rst:28 -msgid "Screens" +#: ../system/integrations/elasticsearch.rst:37 +msgid "Activating Elasticsearch Access" msgstr "" -#: ../system/objects/permissions.rst:30 +#: ../system/integrations/elasticsearch.rst:39 msgid "" -"In the table below you can find an overview about the different permissions " -"and the available screens Zammad distinguishes between." -msgstr "" - -#: ../system/objects/permissions.rst:37 -msgid "Screen" +"By default external access to your Elasticsearch index is not active. You " +"can enable the integration at any time if needed." msgstr "" -#: ../system/objects/permissions.rst:38 -msgid "Available for" +#: ../system/integrations/elasticsearch.rst:42 +msgid "" +"Please ensure to note down the password provided - you won't have access to " +"it afterwards." msgstr "" -#: ../system/objects/permissions.rst:40 -msgid "create" +#: ../system/integrations/elasticsearch.rst:None +msgid "Screencast showing activation of Elasticsearch integration" msgstr "" -#: ../system/objects/permissions.rst:41 ../system/objects/permissions.rst:52 -#: ../system/objects/permissions.rst:59 ../system/objects/permissions.rst:73 -msgid "admin.user" +#: ../system/integrations/elasticsearch.rst:51 +msgid "Connection Settings" msgstr "" -#: ../system/objects/permissions.rst:42 ../system/objects/permissions.rst:53 -#: ../system/objects/permissions.rst:60 -msgid "admin.organization" +#: ../system/integrations/elasticsearch.rst:53 +msgid "" +"This section holds the most important general information for accessing your " +"Elasticsearch indexes - such as:" msgstr "" -#: ../system/objects/permissions.rst:43 ../system/objects/permissions.rst:54 -#: ../system/objects/permissions.rst:61 -msgid "admin.group" +#: ../system/integrations/elasticsearch.rst:57 +msgid "A unique subdomain that does not tell your real instance URL." msgstr "" -#: ../system/objects/permissions.rst:44 -msgid "Creation dialog for not yet existing data" +#: ../system/integrations/elasticsearch.rst:61 +msgid "Software" msgstr "" -#: ../system/objects/permissions.rst:45 -msgid "create_middle" +#: ../system/integrations/elasticsearch.rst:60 +msgid "" +"The major version of the search index being used. This is required by some " +"Reporting tools like Grafana." msgstr "" -#: ../system/objects/permissions.rst:46 ../system/objects/permissions.rst:50 -#: ../system/objects/permissions.rst:57 ../system/objects/permissions.rst:66 -#: ../system/objects/permissions.rst:70 -msgid "ticket.customer" +#: ../system/integrations/elasticsearch.rst:64 +msgid "Authentication" msgstr "" -#: ../system/objects/permissions.rst:47 ../system/objects/permissions.rst:51 -#: ../system/objects/permissions.rst:58 ../system/objects/permissions.rst:69 -msgid "ticket.agent" +#: ../system/integrations/elasticsearch.rst:64 +msgid "The authentication type being supported. ``Basic Authentication``" msgstr "" -#: ../system/objects/permissions.rst:48 -msgid "Ticket create dialog (middle section)" +#: ../system/integrations/elasticsearch.rst:67 +msgid "Available Indexes" msgstr "" -#: ../system/objects/permissions.rst:49 -msgid "edit" +#: ../system/integrations/elasticsearch.rst:69 +msgid "" +"Within this section we're displaying the -in our opinion- most important " +"indexes for a Zammad instance." msgstr "" -#: ../system/objects/permissions.rst:55 -msgid "Editing dialog for already existing data" +#: ../system/integrations/elasticsearch.rst:72 +msgid "" +"If you require all indexes or our listing is not good enough for you, point " +"your browser to the URL we're providing and append ``/_aliases?" +"pretty=true``. The result should look like this: ``https://.zammad.com/" +"_aliases?pretty=true``." msgstr "" -#: ../system/objects/permissions.rst:56 -msgid "view" +#: ../system/integrations/elasticsearch.rst:77 +msgid "" +"Your browser will automatically ask for your credentials - you'll then see " +"something like this:" msgstr "" -#: ../system/objects/permissions.rst:62 -msgid "View-only dialog for already existing data" +#: ../system/integrations/elasticsearch.rst:125 +msgid "Credentials" msgstr "" -#: ../system/objects/permissions.rst:64 -msgid "(e.g. user or organization from search)" +#: ../system/integrations/elasticsearch.rst:127 +msgid "" +"Within this section Zammad displays your available users. The password is " +"provided once (upon activation) and cannot be retrieved after that." msgstr "" -#: ../system/objects/permissions.rst:65 -msgid "signup" +#: ../system/integrations/elasticsearch.rst:131 +msgid "" +"If you need to change or reset your Elasticsearch user password, use the " +"\"Reset password\" button in the credentials table. Doing so creates a brand " +"new password for the account in question. This change is immediate, keep in " +"mind that this may affect third party tools connected to your instance." msgstr "" -#: ../system/objects/permissions.rst:67 -msgid "Sign-up screen for new customers" +#: ../system/integrations/exchange.rst:2 +msgid "Exchange" msgstr "" -#: ../system/objects/permissions.rst:68 -msgid "invite_customer" +#: ../system/integrations/exchange.rst:4 +msgid "" +"With Zammad's Exchange integration, you can easily use existing address " +"books without having to update more than one source." msgstr "" -#: ../system/objects/permissions.rst:71 +#: ../system/integrations/exchange.rst:7 msgid "" -"Customer invitation screen (from :doc:`First Steps ` area)" +"However, you should refrain from syncing all addresses, as the results may " +"not be what you expect (Exchange collects huge amounts of addresses). A " +"central address book of your company to sync makes more sense, as you can " +"ensure that Zammad gets only the data you need and want. Apart from this, it " +"is even not possible to sync the Global Address List (GAL) of your Exchange " +"system with Zammad." msgstr "" -#: ../system/objects/permissions.rst:72 -msgid "invite_agent" +#: ../system/integrations/exchange.rst:16 +msgid "" +"**Exchange and LDAP:** The exchange sync can be overruled by Zammad's LDAP " +"integration. If you have the same users in both sources, the LDAP version " +"will always be Zammad's pick." msgstr "" -#: ../system/objects/permissions.rst:74 +#: ../system/integrations/exchange.rst:19 msgid "" -"Agent invitation screen (from :doc:`First Steps ` area)" +"**One way sync:** the Exchange sync is one way. Exchange => Zammad. Changes " +"to your users inside of Zammad might be overwritten by the Exchange sync." msgstr "" -#: ../system/objects/permissions.rst:78 -msgid "Screen Options" +#: ../system/integrations/exchange.rst:24 +msgid "" +"To configure Exchange integration, simply go to the System > Integrations > " +"Exchange in the admin panel. Press \"change\" and follow the wizard for " +"adding the needed Exchange information to Zammad. On the last two steps " +"Zammad will ask you for the address book(s) and your desired attribute " +"mapping. By default, Zammad only maps email address, first- and lastname. " +"Technically, you can map any Exchange object to a Zammad user object (this " +"also works for custom objects!)." msgstr "" -#: ../system/objects/permissions.rst:80 +#: ../system/integrations/exchange.rst:35 msgid "" -"For the different screens you can select \"show\" and \"required\" options." +"If the SSL verification fails while connecting to Exchange, Zammad will ask " +"you to turn it off temporarily." msgstr "" -#: ../system/objects/permissions.rst:82 -msgid "**shown:** Show (check) or hide (uncheck) a field." +#: ../system/integrations/exchange.rst:38 +msgid "" +"Please be aware that **turning off SSL verification is a security risk**. It " +"should only be used temporarily or for testing purposes. If turned off, " +"there is no verification of the certificate, which means that every " +"presented certificate will be accepted." msgstr "" -#: ../system/objects/permissions.rst:83 +#: ../system/integrations/exchange.rst:43 msgid "" -"**required:** Set a field to mandatory (check). Forces users (via UI and " -"API) to populate the field." -msgstr "" - -#: ../system/objects/types.rst:7 -msgid "Example external data source" +"After pressing Continue, Zammad will check if the configuration is okay. You " +"can then enable Exchange and start your first sync. The sync will then run " +"hourly - if you need to change mappings or the address book(s), you can " +"change the configuration at any time." msgstr "" -#: ../system/objects/types.rst:2 -msgid "Attribute types" +#: ../system/integrations/exchange.rst:50 +msgid "" +"After the sync has finished, you can find the new Exchange contacts under " +"\"Users\". Zammad integrates them just as normal users." msgstr "" -#: ../system/objects/types.rst:4 +#: ../system/integrations/exchange.rst:55 msgid "" -"When adding a new object attribute, you can choose between the following " -"attribute types." +"In some cases you might see unique IDs as \"Login\" instead of the email " +"address. This is normal and doesn't affect the login or email mapping for " +"that entry." msgstr "" -#: ../system/objects/types.rst:14 +#: ../system/integrations/github.rst:4 msgid "" -"You cannot change the attribute format / type as soon as it is applied. If " -"you no longer need an object attribute, consider disabling it instead of " -"removing." +"Use GitHub integration to track GitHub issues directly within Zammad " +"tickets. Add issue hyperlinks and get a live summary of metadata like status " +"(open/closed), assignee, labels, and more." msgstr "" -#: ../system/objects/types.rst:18 -msgid "**What about the translation of my attributes?**" +#: ../system/integrations/github.rst:8 +msgid "Please note that our GitHub integration does not support pull requests." msgstr "" -#: ../system/objects/types.rst:20 -msgid "" -"For some attribute types you can decide if they should be translatable or " -"not. To be precise, it works only for the selectable fields because the " -"possible choices are known and limited. For the following attribute types, " -"you can set the translatable flag:" +#: ../system/integrations/github.rst:None +msgid "Integration page for GitHub" msgstr "" -#: ../system/objects/types.rst:25 -msgid "*Boolean field*" +#: ../system/integrations/github.rst:18 +msgid "" +"In your GitHub settings, create a new API token under **Developer settings > " +"Personal access tokens > Generate new token**. Leave the **Scopes** section " +"empty." msgstr "" -#: ../system/objects/types.rst:26 -msgid "*Single selection field*" +#: ../system/integrations/github.rst:0 ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to create a new API token" msgstr "" -#: ../system/objects/types.rst:27 -msgid "*Multiple selection field*" +#: ../system/integrations/github.rst:27 +msgid "Create a new API key with no scopes/privileges." msgstr "" -#: ../system/objects/types.rst:28 -msgid "*Single tree selection field*" +#: ../system/integrations/github.rst:29 +msgid "🔒 **Will this work for private repos?**" msgstr "" -#: ../system/objects/types.rst:29 -msgid "*Multiple tree selection field*" +#: ../system/integrations/github.rst:31 +msgid "" +"No. To link private repo issues, **use the** ``repo`` **scope instead**. " +"Bear in mind that the resulting token will have `lots of permissions that it " +"doesn't actually need `_, which presents a security risk if your token ever falls into " +"the wrong hands." msgstr "" -#: ../system/objects/types.rst:31 +#: ../system/integrations/github.rst:37 msgid "" -"For these types, you can find an additional field *Translate field contents*:" +"Unfortunately, because of how GitHub's OAuth token scopes are set up, this " +"is the only way to link issues on private repos." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Screenshot showing translatable attribute types" +#: ../system/integrations/github.rst:40 +msgid "Enter your new API token in Zammad and enable GitHub integration." msgstr "" -#: ../system/objects/types.rst:38 -msgid "Screenshot with example of translatable attribute type" +#: ../system/integrations/github.rst:0 +msgid "Screencast showing how to configure Zammad's GitHub integration" msgstr "" -#: ../system/objects/types.rst:45 -msgid "Boolean field" +#: ../system/integrations/github.rst:47 +msgid "" +"Use the default API endpoint (``https://api.github.com/graphql``) unless " +"you're using GitHub Enterprise Server." msgstr "" -#: ../system/objects/types.rst:41 +#: ../system/integrations/github.rst:50 msgid "" -"Provides a drop-down field with display values for ``true`` and ``false``. " -"Setting a default is mandatory." +"Once completed, a new GitHub issues tab will appear in the ticket pane. 🎉" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Boolean fields" +#: ../system/integrations/github.rst:59 ../system/integrations/gitlab.rst:52 +msgid "Token verification is taking a long time" msgstr "" -#: ../system/objects/types.rst:55 -msgid "Date field" +#: ../system/integrations/github.rst:56 ../system/integrations/gitlab.rst:49 +msgid "" +"Slight delays are normal (<2 min.), especially for systems under heavy load." msgstr "" -#: ../system/objects/types.rst:48 -msgid "Provides a date picker field and does not allow default values." +#: ../system/integrations/github.rst:58 +msgid "" +"Self-hosted administrators, please check your network settings to ensure " +"that your Zammad server can reach ``api.github.com``." msgstr "" -#: ../system/objects/types.rst:52 -msgid "Default time diff (hours)" +#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 +msgid "I reloaded the page and now the API token is gone" msgstr "" -#: ../system/objects/types.rst:51 +#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 msgid "" -"This setting helps the user by highlighting the day from now plus the " -"provided value. It *does not* pre-fill the field." -msgstr "" - -#: ../system/objects/types.rst:0 -msgid "Available settings for Date fields" +"This may indicate that Zammad is still verifying your API token. Try " +"reloading the page again in a couple minutes." msgstr "" -#: ../system/objects/types.rst:73 -msgid "Date & time field" +#: ../system/integrations/gitlab.rst:2 +msgid "GitLab" msgstr "" -#: ../system/objects/types.rst:58 -msgid "Provides a date and time picker – does not allow default values" +#: ../system/integrations/gitlab.rst:4 +msgid "" +"Use GitLab integration to track GitLab issues directly within Zammad " +"tickets. Add issue hyperlinks and get a live summary of metadata like status " +"(open/closed), assignee, labels, and more." msgstr "" -#: ../system/objects/types.rst:62 -msgid "Allow future" +#: ../system/integrations/gitlab.rst:8 +msgid "" +"Please note that our GitLab integration does not support merge requests." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Forbid dates and times in the future." +#: ../system/integrations/gitlab.rst:None +msgid "Integration page for GitLab" msgstr "" -#: ../system/objects/types.rst:66 -msgid "Allow past" +#: ../system/integrations/gitlab.rst:18 +msgid "" +"In your GitLab preferences, create a new API token under **Access Tokens**." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Forbid dates and times in the past." +#: ../system/integrations/gitlab.rst:20 +msgid "Under **Select scopes**, choose ``read_api`` only." msgstr "" -#: ../system/objects/types.rst:70 -msgid "Default time diff (minutes)" +#: ../system/integrations/gitlab.rst:27 +msgid "🔒 **If you wish to link issues on any private repos...**" msgstr "" -#: ../system/objects/types.rst:69 -msgid "" -"This setting helps the user by highlighting the day from now plus the " -"provided value. It does not pre-fill the field." +#: ../system/integrations/gitlab.rst:29 +msgid "Your API token must belong to an account with access to those repos." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Date & time fields" +#: ../system/integrations/gitlab.rst:31 +msgid "Enter your new API token in Zammad and enable GitLab integration." msgstr "" -#: ../system/objects/types.rst:86 -msgid "Integer field" +#: ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to configure Zammad's GitLab integration" msgstr "" -#: ../system/objects/types.rst:76 +#: ../system/integrations/gitlab.rst:40 msgid "" -"Provides an input field that allows integer usage only. You may define a " -"default value. You cannot enforce comma separation." +"Use the default API endpoint (``https://gitlab.com/api/graphql``) unless " +"you're a self-hosted GitLab user." msgstr "" -#: ../system/objects/types.rst:80 -msgid "Minimal" +#: ../system/integrations/gitlab.rst:43 +msgid "" +"Once completed, a new GitLab issues tab will appear in the ticket pane. 🎉" msgstr "" -#: ../system/objects/types.rst:80 -msgid "The minimal value the field accepts." +#: ../system/integrations/gitlab.rst:51 +msgid "" +"Self-hosted administrators, please check your network settings to ensure " +"that your Zammad server can reach ``gitlab.com``." msgstr "" -#: ../system/objects/types.rst:83 -msgid "Maximal" +#: ../system/integrations/i-doit.rst:2 +msgid "i-doit" msgstr "" -#: ../system/objects/types.rst:83 -msgid "The maximum value the field accepts." +#: ../system/integrations/i-doit.rst:4 +msgid "" +"`i-doit `_ is an open-source **configuration " +"management database** - in other words, a tool for keeping tabs on every " +"single piece of your physical and digital infrastructure, from network " +"equipment to virtual machines on down to the faceplates on your rack shelves " +"and more." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Integer fields" +#: ../system/integrations/i-doit.rst:10 +msgid "" +"What's that got to do with Zammad? Well, if you used tickets to track issues " +"with all that hardware, you might start wishing there was a way they could " +"talk to each other." msgstr "" -#: ../system/objects/types.rst:99 -msgid "Multiple selection field" +#: ../system/integrations/i-doit.rst:14 +msgid "Zammad gives you two:" msgstr "" -#: ../system/objects/types.rst:89 -msgid "" -"Provides a selection field that allows the selection of one or more out of " -"several. This field does allow setting a default value." +#: ../system/integrations/i-doit.rst:17 +msgid "1. Add i-doit Links to Zammad Tickets" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Multiple selection fields" +#: ../system/integrations/i-doit.rst:20 ../system/integrations/i-doit.rst:80 +msgid "What Users See" msgstr "" -#: ../system/objects/types.rst:112 -msgid "Single selection field" +#: ../system/integrations/i-doit.rst:26 +msgid "i-doit integration in Zammad's ticket pane" msgstr "" -#: ../system/objects/types.rst:102 +#: ../system/integrations/i-doit.rst:26 msgid "" -"Provides a drop-down field that allows selection of one value out of " -"several. This field does allow setting a default value." +"The i-doit integration will appear under a new 🖨 tab in the ticket pane." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Single selection fields" +#: ../system/integrations/i-doit.rst:28 +msgid "" +"i-doit integration puts a new tab in Zammad's ticket pane where you can add " +"links to existing i-doit devices for easy reference. (See our :user-docs:" +"`user documentation ` to learn " +"how it works in practice)." msgstr "" -#: ../system/objects/types.rst:142 -msgid "Textarea field" +#: ../system/integrations/i-doit.rst:36 ../system/integrations/i-doit.rst:93 +msgid "How to Set it Up" msgstr "" -#: ../system/objects/types.rst:115 +#: ../system/integrations/i-doit.rst:38 msgid "" -"Provides a text area input field (multiple lines) and thus allows e.g. new " -"lines. You can set a default field value." +"It requires i-doit's `API Add-on `_. Make sure to have it properly set up. Use the following setting:" msgstr "" -#: ../system/objects/types.rst:120 -msgid "" -"Please note that this field *does not* support text formatting or HTML " -"content (rich text)." +#: ../system/integrations/i-doit.rst:42 +msgid "Active: ``Yes``" msgstr "" -#: ../system/objects/types.rst:123 -msgid "**🥵 This field can consume a lot of visual space**" +#: ../system/integrations/i-doit.rst:43 +msgid "Enforce authentication by username and password: ``No``" msgstr "" -#: ../system/objects/types.rst:125 +#: ../system/integrations/i-doit.rst:45 msgid "" -"Depending on where you use this field type, it may use a lot of visual space " -"if you provide a lot of text. This may be an issue to work with." +"To set it up, enable the integration in the Zammad admin panel under " +"**System > Integrations > i-doit**:" msgstr "" -#: ../system/objects/types.rst:130 -msgid "Default" +#: ../system/integrations/i-doit.rst:None +msgid "i-doit settings within the integration pages" msgstr "" -#: ../system/objects/types.rst:129 -msgid "" -"The here provided text will be shown within the text area field or new data " -"sets." +#: ../system/integrations/i-doit.rst:53 +msgid "The root URL of your i-doit installation." msgstr "" -#: ../system/objects/types.rst:134 ../system/objects/types.rst:160 -msgid "Maxlength" +#: ../system/integrations/i-doit.rst:62 +msgid "API token" msgstr "" -#: ../system/objects/types.rst:0 ../system/objects/types.rst:160 -msgid "You can pick the maximum length of the field." +#: ../system/integrations/i-doit.rst:56 +msgid "" +"Found in the i-doit admin panel under **Interfaces / external data > JSON-" +"RPC API > Common Settings**." msgstr "" -#: ../system/objects/types.rst:0 -msgid "The default length of this object is ``500``." +#: ../system/integrations/i-doit.rst:0 +msgid "i-doit administration interface with API configuration" msgstr "" -#: ../system/objects/types.rst:139 -msgid "Rows" +#: ../system/integrations/i-doit.rst:67 +msgid "Client ID" msgstr "" -#: ../system/objects/types.rst:0 -msgid "" -"Change the number of rows to dislay so that you can use only the space you " -"really need." +#: ../system/integrations/i-doit.rst:65 +msgid "A unique name to identify Zammad within i-doit." msgstr "" -#: ../system/objects/types.rst:0 -msgid "The default number of rows is ``4``." +#: ../system/integrations/i-doit.rst:67 +msgid "(Zammad does not require you to enter a value here, but i-doit might!)" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Textarea fields" +#: ../system/integrations/i-doit.rst:70 +msgid "" +"Here you can decide if the certificate of your i-doit system has to be " +"verified or not. In case you are using custom certificates, please have a " +"look at :doc:`how to add them to Zammad `." msgstr "" -#: ../system/objects/types.rst:165 -msgid "Text field" +#: ../system/integrations/i-doit.rst:77 +msgid "2. List / Create Zammad Tickets in i-doit" msgstr "" -#: ../system/objects/types.rst:145 -msgid "Provides a text field (one line) and allows choosing a default value." +#: ../system/integrations/i-doit.rst:None +msgid "Zammad integration in i-doit's device view" msgstr "" -#: ../system/objects/types.rst:148 +#: ../system/integrations/i-doit.rst:86 msgid "" -"Defines the type of the input field. This allows e.g. your browser to ensure " -"that you provide the specific type." +"i-doit's ticket system integration gives you a way to see all the tickets " +"for a given device without ever leaving i-doit. (See our :user-docs:`user " +"documentation ` to learn how it " +"works in practice)." msgstr "" -#: ../system/objects/types.rst:152 -msgid "Currently available:" +#: ../system/integrations/i-doit.rst:95 +msgid "" +"Enable this integration in the i-doit admin panel under **Interfaces / " +"external data > Trouble Ticket System (TTS) > Configuration**:" msgstr "" -#: ../system/objects/types.rst:155 -msgid "Phone" +#: ../system/integrations/i-doit.rst:None +msgid "i-doit administration interface with TTS configuration" msgstr "" -#: ../system/objects/types.rst:156 -msgid "Text" +#: ../system/integrations/i-doit.rst:104 +msgid "TTS-Type" msgstr "" -#: ../system/objects/types.rst:157 -msgid "Url *(URL fields disable link-template availability)*" +#: ../system/integrations/i-doit.rst:104 +msgid "``Zammad``" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Text fields" +#: ../system/integrations/i-doit.rst:115 +msgid "Username / Password" msgstr "" -#: ../system/objects/types.rst:174 -msgid "Single tree selection field" +#: ../system/integrations/i-doit.rst:107 +msgid "Login credentials for a Zammad agent." msgstr "" -#: ../system/objects/types.rst:168 +#: ../system/integrations/i-doit.rst:109 msgid "" -"Provides a select-like field with up to 6 layers of options. Does not allow " -"setting a default value." +"This agent must have **read permission** for all :doc:`groups ` that plan on using the i-doit integration." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Tree Select fields" +#: ../system/integrations/i-doit.rst:113 +msgid "" +"You may even wish to create a dedicated agent account just for this " +"integration (otherwise, if the agent ever changes her password, you will " +"have to remember to update it here)." msgstr "" -#: ../system/objects/types.rst:183 -msgid "Multiple tree selection field" +#: ../system/integrations/i-doit.rst:117 +msgid "URL incl. protocol" msgstr "" -#: ../system/objects/types.rst:177 -msgid "" -"Provides a select-like field with up to 6 layers of options allowing the " -"selection of multiple values. Does not allow setting a default value." +#: ../system/integrations/i-doit.rst:118 +msgid "``https://your.zammad.domain``" msgstr "" -#: ../system/objects/types.rst:302 -msgid "External Data Source field" +#: ../system/integrations/index.rst:2 +msgid "Integrations" msgstr "" -#: ../system/objects/types.rst:186 +#: ../system/integrations/index.rst:4 msgid "" -"Provides a searchable field which fetches data from an external system. This " -"can be useful if you have data outside of Zammad and don't want to maintain " -"both data sources." +"Zammad offers numerous integrations that add rich features to your instance." msgstr "" -#: ../system/objects/types.rst:190 -msgid "The feature works as follows:" +#: ../system/integrations/index.rst:6 +msgid "We're still working on this part of our documentation, stay tight!" msgstr "" -#: ../system/objects/types.rst:192 -msgid "" -"Zammad sends a query with a search string (free text from agent or based on " -"a variable) in a pre-defined format (\"Search URL\") to an external system." +#: ../system/integrations/index.rst:10 +msgid "Integrations for Phone Systems" msgstr "" -#: ../system/objects/types.rst:195 +#: ../system/integrations/index.rst:14 msgid "" -"This external system searches for matches and provides a response as a JSON " -"structure to Zammad." +"Your VoIP provider or telephony system is not listed? Possibly your provider " +"supports Zammad by using the generic CTI - if you're unsure ask your " +"provider." msgstr "" -#: ../system/objects/types.rst:197 +#: ../system/integrations/index.rst:18 msgid "" -"Zammad just looks for the defined list and value keys, reads the content and " -"displays the value to the user. There is no search on Zammad side." +"Provider does not support Zammad? Consider creating a `feature request in " +"the Zammad Community `_." msgstr "" -#: ../system/objects/types.rst:201 -msgid "" -"The usage of a PostgreSQL database for Zammad is required. In any other " -"case, Zammad will hide the external data source type and you are not able to " -"use it. If you want to use this feature, consider to :docs:`migrate your " -"database `." +#: ../system/integrations/index.rst:31 +msgid "Integrations for Authentication and Customers" msgstr "" -#: ../system/objects/types.rst:205 -msgid "Currently, only ``GET`` is supported as request method." +#: ../system/integrations/index.rst:44 +msgid "Integrations for Monitoring Systems" msgstr "" -#: ../system/objects/types.rst:206 -msgid "" -"The data structure must be in JSON format and provide the objects in an " -"array." +#: ../system/integrations/index.rst:46 +msgid "This section currently misses the following integrations:" msgstr "" -#: ../system/objects/types.rst:208 -msgid "" -"The endpoint for the external data source has to support search. On Zammad " -"side, there is no search/logic implemented; however, you can define the " -"output key and value based on the result(s) from the response (which " -"provides already filtered content based on the search)." +#: ../system/integrations/index.rst:48 +msgid "Icinga" msgstr "" -#: ../system/objects/types.rst:212 -msgid "" -"If you receive more results as expected, your external data source search " -"may not work properly or the structure of the URL is not correct. You should " -"get in touch with a responsible person from the external system." +#: ../system/integrations/index.rst:49 +msgid "Monit" msgstr "" -#: ../system/objects/types.rst:217 -msgid "" -"Please have a look :doc:`at our example `, where you can find a possible configuration for a public " -"dummy endpoint." +#: ../system/integrations/index.rst:50 +msgid "Nagios" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for external data source fields" +#: ../system/integrations/index.rst:60 +msgid "Integrations for Issue Trackers" msgstr "" -#: ../system/objects/types.rst:242 -msgid "Search URL" +#: ../system/integrations/index.rst:70 +msgid "Other Integrations" msgstr "" -#: ../system/objects/types.rst:227 +#: ../system/integrations/index.rst:72 msgid "" -"Set your endpoint where Zammad fetches the data. Please make sure to include " -"a valid search :doc:`variable <../variables>` as an URL parameter. Example " -"for a free text search at user input: ``#{search.term}``" +"This section will hold any other integration that can't be grouped up (yet)." msgstr "" -#: ../system/objects/types.rst:232 -msgid "" -"If in doubt, ask the responsible person for the external data source how " -"they expect the strucuture of the URL." +#: ../system/integrations/ldap/index.rst:2 +msgid "LDAP / Active Directory" msgstr "" -#: ../system/objects/types.rst:236 +#: ../system/integrations/ldap/index.rst:4 msgid "" -"Depending on your search variable, the preview might work or not. The reason " -"is that the context might not be available and it is no bug." +"Zammad comes with a powerful LDAP integration that allows you to have a " +"single source of truth. By this you reduce the number of login credentials " +"your user has to remember." msgstr "" -#: ../system/objects/types.rst:239 +#: ../system/integrations/ldap/index.rst:10 msgid "" -"Please also make sure to use a variable which is available in your object " -"context. For example you won't be able to search for a ticket in a user " -"object context." -msgstr "" - -#: ../system/objects/types.rst:252 -msgid "SSL Verification" +"The LDAP source is also a perfect candidate for Zammad's :docs:`Kerberos " +"Single Sign-On ` but also works as addition " +"to other :doc:`/settings/security/third-party`." msgstr "" -#: ../system/objects/types.rst:245 -msgid "Here you can switch the SSL verification to no." +#: ../system/integrations/ldap/index.rst:None +msgid "Zammands LDAP management page" msgstr "" -#: ../system/objects/types.rst:249 -msgid "" -"If your external data source system is using self signed certificates, " -"please have a look :doc:`here ` for " -"further information about how to handle them in Zammad, so you can keep the " -"SSL verification activated." +#: ../system/integrations/ldap/index.rst:25 +msgid "📝 :doc:`manage`" msgstr "" -#: ../system/objects/types.rst:258 -msgid "HTTP Authentication" +#: ../system/integrations/ldap/index.rst:25 +msgid "Add, modify, remove or re-arrange your LDAP-Sources as needed." msgstr "" -#: ../system/objects/types.rst:255 -msgid "" -"If your external data source requires an authentication, you can set it " -"here. You can leave it empty or choose between *Basic Authentication* or " -"*Authentication Token* (selecting one of the two methods leads to additional " -"fields where you can enter your credentials/token)." +#: ../system/integrations/ldap/index.rst:30 +msgid "Before you continue, please note the following limitations." msgstr "" -#: ../system/objects/types.rst:265 -msgid "Search result list key" +#: ../system/integrations/ldap/index.rst:32 +msgid "Mapping / Synchronizing organizations is not possible" msgstr "" -#: ../system/objects/types.rst:261 +#: ../system/integrations/ldap/index.rst:36 msgid "" -"Defines the level in the JSON structure which provides the list with search " -"results. You can leave it empty, if the data is already provided as an " -"array. If you have to go deeper in the structure, you can provide a path " -"with ``.`` as separators, e.g. ``key.subkey.sub-sub-key``." +"You may want to consider using domain based assignments to overcome this " +"issue. Learn more on :doc:`/manage/organizations/index`." msgstr "" -#: ../system/objects/types.rst:271 -msgid "Search result value key" +#: ../system/integrations/ldap/index.rst:39 +msgid "" +"Zammad's LDAP sync is one way. Editing user settings or permissions may be " +"overwritten upon the next sync depending on your configuration." msgstr "" -#: ../system/objects/types.rst:268 -msgid "" -"Defines the attribute in the structure in which your external data source " -"provides the *value* for your data. An example would be a product *number*. " -"If you have to go deeper in the structure, you can provide a path with ``.`` " -"as separators, e.g. ``key.subkey.sub-sub-key``." +#: ../system/integrations/ldap/index.rst:41 +msgid "Nested groups are not supported." msgstr "" -#: ../system/objects/types.rst:277 -msgid "Search result label key" +#: ../system/integrations/ldap/index.rst:42 +msgid "Synchronizing user avatars from LDAP is not supported." msgstr "" -#: ../system/objects/types.rst:274 -msgid "" -"Defines the attribute in the structure in which your external data source " -"provides the *label* for your data. An example would be a product *name*. If " -"you have to go deeper in the structure, you can provide a path with ``.`` as " -"separators, e.g. ``key.subkey.sub-sub-key``." +#: ../system/integrations/ldap/index.rst:43 +msgid "Unlike user filters, group filters cannot be changed." msgstr "" -#: ../system/objects/types.rst:280 +#: ../system/integrations/ldap/index.rst:44 msgid "" -"In the preview area, you can find the following items (depending on your " -"configuration above):" +"When a user originates from an LDAP server, Zammad will try to verify the " +"login credentials against LDAP first - if this fails Zammad will check its " +"local database." msgstr "" -#: ../system/objects/types.rst:283 +#: ../system/integrations/ldap/index.rst:50 msgid "" -"**Error/hint message** (only if configuration is not complete): Zammad tells " -"you, if there is a problem and what you should change in your configuration." +"Users can have local passwords even if they're LDAP users! You can learn " +"more about user accounts in general on :doc:`/manage/users/index`." msgstr "" -#: ../system/objects/types.rst:286 +#: ../system/integrations/ldap/index.rst:54 msgid "" -"**Search field**: search for an existing attribute in the data source to get " -"a preview. This is required for the fields below to show up." +"When several LDAP sources contain the same user (meaning the same email " +"address), the user in question will be updated with every source configured. " +"*The last LDAP source will win.*" msgstr "" -#: ../system/objects/types.rst:288 +#: ../system/integrations/ldap/index.rst:58 msgid "" -"**Search result response** (only if configuration is not complete): here you " -"can find a syntax highlighted JSON preview of the response, based on the " -"search term you entered." +"This is subject to change with `Issue 4109 `_ in the future." msgstr "" -#: ../system/objects/types.rst:291 +#: ../system/integrations/ldap/index.rst:60 msgid "" -"**Search result list** (only if *search result list key* is properly set): " -"output of the structure under the configured *search result list key*." +"Synchronization statistics currently affect *all* configured LDAP sources. " +"This also applies for newly added or updated sources." msgstr "" -#: ../system/objects/types.rst:294 +#: ../system/integrations/ldap/index.rst:63 msgid "" -"**Preview table** (when fully configured): Zammad shows you a table which " -"includes the found items based on the search string (value, label and " -"optional link). You can use this preview if you don't have the complete data " -"structure of the external system in mind." +"This is subject to change with `Issue 4108 `_ in the future." msgstr "" -#: ../system/objects/types.rst:299 +#: ../system/integrations/ldap/index.rst:65 msgid "" -"An example of a configured external data source field from agent perspective:" +"Zammad currently has limited fallback server support. You can workaround " +"this by providing several sources - however, ensure to have the exact same " +"configuration on your fallback." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Screencast showing the search for a product in a ticket" +#: ../system/integrations/ldap/index.rst:69 +msgid "" +"This is subject to improve with `Issue 4107 `_ in the future." msgstr "" -#: ../system/objects/types.rst:307 -msgid "URL fields (Link-Template)" +#: ../system/integrations/ldap/index.rst:76 +msgid "" +"This section holds all requests Zammad handled for all LDAP sources. These " +"entries can either contain synchronization information or logins " +"(authentication attempts via Zammad's login interface)." msgstr "" -#: ../system/objects/types.rst:311 +#: ../system/integrations/ldap/index.rst:80 msgid "" -"This function is restricted to Text, Select and External data source types " -"only." +"By clicking on any request, Zammad will provide even more information. The " +"provided information can be useful when something does not work as expected." msgstr "" -#: ../system/objects/types.rst:314 +#: ../system/integrations/ldap/index.rst:85 msgid "" -"Link-Templates are an amazing way to dynamically generate URLs. They allow " -"you to integrate other systems better without having to manually copy data " -"from Zammad if possible." +"Especially a LDAP synchronization can cause many log entries. The web " +"interface will always limit the number of shown entries to the last 50 " +"entries." msgstr "" -#: ../system/objects/types.rst:320 +#: ../system/integrations/ldap/index.rst:None msgid "" -"Another great way of communicating with another system may be Zammad's :doc:" -"`Webhooks `." +"Screencast showing LDAP integration log entries and a detail view on\n" +"an entry." msgstr "" -#: ../system/objects/types.rst:323 -msgid "" -"After filling a link-template enabled field, an URL icon will appear on its " -"right. Clicking on the icon opens a new tab." +#: ../system/integrations/ldap/manage.rst:2 +msgid "Manage LDAP-Sources" msgstr "" -#: ../system/objects/types.rst:328 +#: ../system/integrations/ldap/manage.rst:6 msgid "" -"Even though Zammad displays the link template within object edit and create " -"screens, the function is optional. It's only active if you populate the " -"field." +"Please keep in mind all current limitations for the LDAP synchronization. " +"This will help to understand scopes of the following operations better." msgstr "" -#: ../system/objects/types.rst:333 -msgid "" -"What's the difference between URL and text fields with link template...?!" +#: ../system/integrations/ldap/manage.rst:65 +msgid "Add new source" msgstr "" -#: ../system/objects/types.rst:335 +#: ../system/integrations/ldap/manage.rst:10 msgid "" -"Both fields have different use cases. Use ``text`` type text fields when " -"ever you have a *static* url that requires dynamic parameters. If you " -"require a drag & drop like field that you can put in any URL, use ``URL`` " -"type text fields." +"Using the *New Source* button allows you to add new LDAP sources to your " +"installation. You're not limited in the number of sources, however, keep in " +"mind that many sources will also take more time to synchronize." msgstr "" -#: ../system/objects/types.rst:340 +#: ../system/integrations/ldap/manage.rst:14 msgid "" -"The difference is easier to spot when comparing the fields directly, below " -"screencast shows the result - the dynamic approach uses existing values in " -"the moment of updating to built the URL - e.g. ``https://google.com/search?" -"q=cookies`` - while the URL approach uses the actual URL of the field - e.g. " -"``https://zammad.com``." +"You can choose between different encryption types, namely *SSL* and " +"*STARTTLS* or none of them (\"*No SSL*\"). If you choose *SSL* or " +"*STARTTLS*, Zammad will display an additional *SSL verification* option that " +"allows you to disable the verification, e.g. for self-signed SSL " +"certificates. You can also tell Zammad to use a different port by appending " +"``:`` to your hostname/IP." msgstr "" -#: ../system/objects/types.rst:None +#: ../system/integrations/ldap/manage.rst:0 msgid "" -"Screencast showing the differents in between URL and text type fields with " -"actual values" +"Screenshot of configuring a new LDAP source with SSL encryption and SSL " +"verification" msgstr "" -#: ../system/objects/types.rst:352 -msgid "How does this work...?!" +#: ../system/integrations/ldap/manage.rst:26 +msgid "" +"New Source with SSL transport security enabled and certificate verification" msgstr "" -#: ../system/objects/types.rst:354 +#: ../system/integrations/ldap/manage.rst:30 msgid "" -"As an example, let's say you have an attribute called ``amazing_attribute`` " -"and you want to open a google search directly with the input from that field." +"Using an user filter can be a good idea if you only require a small subset " +"of your LDAP users in Zammad." msgstr "" -#: ../system/objects/types.rst:357 -msgid "" -"Providing the link-template field below allows you to do so: ``https://www." -"google.com/search?q=#{ticket.amazing_attribute}``" +#: ../system/integrations/ldap/manage.rst:42 +msgid "This especially affects inactive users" msgstr "" -#: ../system/objects/types.rst:362 +#: ../system/integrations/ldap/manage.rst:34 msgid "" -"You can use any :doc:`Zammad variable ` as long as it's " -"available in the moment you need it." +"As every LDAP behaves differently on which attributes and how they are set, " +"Zammad doesn't care about any flags." msgstr "" -#: ../system/objects/types.rst:365 +#: ../system/integrations/ldap/manage.rst:37 msgid "" -"As a result, you are redirected to Google with a search for the value of the " -"attribute, if you click on the button in the ticket (as you can see in the " -"screencast above)." +"Users that no longer are returned by your LDAP source will automatically be " +"set to inactive. Zammad assumes that the user was deactivated." msgstr "" -#: ../system/packages.rst:2 -msgid "Packages" +#: ../system/integrations/ldap/manage.rst:41 +msgid "" +"Users will never be removed automatically! If you want to remove obsolete " +"users, use :doc:`/system/data-privacy`." msgstr "" -#: ../system/packages.rst:4 -msgid "That's the package management-area." +#: ../system/integrations/ldap/manage.rst:46 +msgid "Active Directory admins" msgstr "" -#: ../system/packages.rst:6 -msgid "Individual add-ons for Zammad can be installed and managed here." +#: ../system/integrations/ldap/manage.rst:45 +msgid "" +"Active Directories are quite specific on how to filter for active users only " +"- please see the `Microsoft documentation `_ for more " +"information." msgstr "" -#: ../system/sessions.rst:2 -msgid "Sessions" +#: ../system/integrations/ldap/manage.rst:51 +msgid "" +"*Do not* manually write pathes of either LDAP attributes or groups. If " +"Zammad does not display them, it either cannot find them or you have a lot " +"of users that don't have the attributes populated." msgstr "" -#: ../system/sessions.rst:4 +#: ../system/integrations/ldap/manage.rst:55 msgid "" -"Sessions management allows reviewing currently known user sessions and " -"allows to end these. The session timeout is affected by :ref:" -"`security_session_timeout` configurations from security settings." +"Zammad will always only return attributes that are filled - this reduces the " +"returned list of attributes greatly." msgstr "" -#: ../system/sessions.rst:None -msgid "Screenshot showing Zammad's session management" +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing how to add a new LDAP source" msgstr "" -#: ../system/sessions.rst:13 -msgid "Zammad will provide the following information:" +#: ../system/integrations/ldap/manage.rst:63 +msgid "" +"If your LDAP system doesn't allow anonymous bind, Zammad detects it and " +"provides you an editable \"Base DN\" *text* field instead of a prefilled " +"*select* field." msgstr "" -#: ../system/sessions.rst:16 -msgid "" -"The user account this session entry belongs to. It can be normal if a user " -"has several sessions in the list. This can be due to changed browser " -"information or if you use e.g. single sign on methods where the user does " -"not use the log off button." +#: ../system/integrations/ldap/manage.rst:81 +msgid "Review or edit existing source" msgstr "" -#: ../system/sessions.rst:22 -msgid "Browser" +#: ../system/integrations/ldap/manage.rst:68 +msgid "" +"Clicking on a LDAP source will provide a configuration and mapping overview." msgstr "" -#: ../system/sessions.rst:22 -msgid "The browser agent communicated to Zammad." +#: ../system/integrations/ldap/manage.rst:70 +msgid "" +"If needed you can then use the *Change* button to update either the name, " +"active state or the whole configuration. If you're changing the whole " +"configuration, the dialogue will be identical to the source creation." msgstr "" -#: ../system/sessions.rst:40 -msgid "Location" +#: ../system/integrations/ldap/manage.rst:76 +msgid "" +"Did your LDAP server change? Different LDAP servers have different " +"structures and default attributes. This causes the LDAP synchronization to " +"likely fail. Consider removing the affected source and re-add it." msgstr "" -#: ../system/sessions.rst:25 -msgid "" -"The anticipated location based on the users IP address. Depending on the IP " -"address the result shown may differ. This option depends on :doc:`/settings/" -"system/services`." +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing the update of the source name." msgstr "" -#: ../system/sessions.rst:29 -msgid "The following information can be shown:" +#: ../system/integrations/ldap/manage.rst:89 +msgid "Re-arrange LDAP source's order" msgstr "" -#: ../system/sessions.rst:33 -msgid "IP address" +#: ../system/integrations/ldap/manage.rst:84 +msgid "" +"You can change the synchronization order for each source at any time. Zammad " +"will synchronize the sources from top to bottom." msgstr "" -#: ../system/sessions.rst:32 +#: ../system/integrations/ldap/manage.rst:0 msgid "" -"Either if you set *Geo IP services* to inactive or you're using internal IP " -"address which do not provide location information." +"Screencasting showing how to change the source order by using\n" +"drag and drop." msgstr "" -#: ../system/sessions.rst:40 -msgid "Country (or Country + City)" +#: ../system/integrations/ldap/manage.rst:101 +msgid "Remove a source" msgstr "" -#: ../system/sessions.rst:36 +#: ../system/integrations/ldap/manage.rst:92 msgid "" -"If *Geo IP services* is enabled only. Depends on how detailed the available " -"IP address information are." +"If you no longer need the a LDAP source or simply want to start over, you " +"can remove them at any time. This will not remove synchronized users, data " +"synchronized or permissions." msgstr "" -#: ../system/sessions.rst:39 +#: ../system/integrations/ldap/manage.rst:98 msgid "" -"Be aware that results can be inaccurate - this technically is not an error." +"Not sure if you'd need the source later on? Set the source to inactive " +"instead of removing it - see *Review or edit existing source* for more." msgstr "" -#: ../system/sessions.rst:43 -msgid "Age" +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing how to remove LDAP sources." msgstr "" -#: ../system/sessions.rst:43 -msgid "Provides the time when the session initially has been created." +#: ../system/integrations/pgp/index.rst:2 +msgid "PGP" msgstr "" -#: ../system/sessions.rst:50 -msgid "Update" +#: ../system/integrations/pgp/index.rst:7 +msgid "" +"Pretty Good Privacy (PGP) is another method for secure email communication. " +"With PGP, you can exchange **signed** and **encrypted** messages with others." msgstr "" -#: ../system/sessions.rst:46 -msgid "" -"Provides the time the user used this session to open Zammad. This timestamp " -"is only updated if the user e.g. reloads, not during normal work on tickets." +#: ../system/integrations/pgp/index.rst:13 +#: ../system/integrations/smime/index.rst:17 +msgid "Signing" msgstr "" -#: ../system/sessions.rst:50 -msgid "This timestamp is being used for the session timeout." +#: ../system/integrations/pgp/index.rst:11 +msgid "is a proof that a message hasn't been manipulated on its way." msgstr "" -#: ../system/sessions.rst:53 +#: ../system/integrations/pgp/index.rst:13 msgid "" -"Use the delete button to remove a single session on behalf of your user." +"In other words, it guarantees message **integrity** and **authenticity**." msgstr "" -#: ../system/subscription/billing.rst:2 -msgid "Billing" +#: ../system/integrations/pgp/index.rst:19 +#: ../system/integrations/smime/index.rst:22 +msgid "Encryption" msgstr "" -#: ../system/subscription/billing.rst:4 +#: ../system/integrations/pgp/index.rst:16 +#: ../system/integrations/smime/index.rst:20 msgid "" -"Within the billing tab you can control all billing relevant information like " -"invoices, billing address and the option to cancel your subscription." -msgstr "" - -#: ../system/subscription/billing.rst:33 -msgid "Billing information" +"scrambles a message so that it can only be unscrambled by the intended " +"recipient." msgstr "" -#: ../system/subscription/billing.rst:8 +#: ../system/integrations/pgp/index.rst:19 msgid "" -"All adjusted billing information below only affect future invoices. If your " -"invoice was issued wrong, please contact `our sales team `_." +"In other words, it guarantees message **privacy** and **data security**." msgstr "" -#: ../system/subscription/billing.rst:14 -msgid "Billing address" +#: ../system/integrations/pgp/index.rst:25 +msgid "Screenshot of ticket creation with encrypt and sign buttons" msgstr "" -#: ../system/subscription/billing.rst:13 +#: ../system/integrations/pgp/index.rst:25 msgid "" -"Provide your company address here, make sure to include the companies name " -"in case required. This address will be referenced on your invoice." +"Once PGP has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " +"appear in the ticket composer." msgstr "" -#: ../system/subscription/billing.rst:18 -msgid "VAT ID" +#: ../system/integrations/pgp/index.rst:28 +msgid "**Sign button not visible?**" msgstr "" -#: ../system/subscription/billing.rst:17 +#: ../system/integrations/pgp/index.rst:30 msgid "" -"Provide your VAT ID here. If applicable your invoice will not contain German " -"VAT. Please make sure to pay the VAT in your country as required." +"Please note that the signing of emails is based on the outgoing email " +"account. That means you have to choose a group with a sender email account, " +"which has a private key assigned." msgstr "" -#: ../system/subscription/billing.rst:27 -msgid "Billing Email Address" +#: ../system/integrations/pgp/index.rst:35 +msgid "Handling of Keys" msgstr "" -#: ../system/subscription/billing.rst:21 +#: ../system/integrations/pgp/index.rst:36 msgid "" -"Usually the instance owner (the person that registered the instance) will " -"receive all emails including the invoices. In case you have your own billing " -"department, you can provide their email address here." +"To use the PGP function, you have to enable the integration (PGP) by " +"switching the toggle to *enabled*." msgstr "" -#: ../system/subscription/billing.rst:25 +#: ../system/integrations/pgp/index.rst:39 msgid "" -"All billing relevant information will then be sent to this email address." +"You can add keys by clicking the *add key* button. The keys can be imported " +"from a file or you can paste the content of the key in the text box." msgstr "" -#: ../system/subscription/billing.rst:27 -msgid "Invoices are sent as attachment (PDF) to this email address." +#: ../system/integrations/pgp/index.rst:42 +msgid "**Which keys do I have to import?**" msgstr "" -#: ../system/subscription/billing.rst:29 +#: ../system/integrations/pgp/index.rst:44 msgid "" -"Don't forget to press the *Submit* button after you changed above settings." +"For **signing** *outgoing* emails, you have to import the private key of " +"your Zammad email account." msgstr "" -#: ../system/subscription/billing.rst:0 +#: ../system/integrations/pgp/index.rst:47 msgid "" -"Screenshot showing options for billing information within the\n" -"subscription menu" -msgstr "" - -#: ../system/subscription/billing.rst:70 -msgid "Payment history" +"For **encrypting** *outgoing* emails, you have to import the public key of " +"the customer's email account." msgstr "" -#: ../system/subscription/billing.rst:36 +#: ../system/integrations/pgp/index.rst:50 msgid "" -"The payment history will display a history of all paid invoices. At this " -"point you can also download these in case you need them again." +"For **verifying the signature** of signed *incoming* emails, you have to " +"import the public key of the customer." msgstr "" -#: ../system/subscription/billing.rst:41 +#: ../system/integrations/pgp/index.rst:53 msgid "" -"You will only find *paid* invoices here. Invoices that are to be billed are " -"not available before the payment is completed." +"For **decrypting** of encrypted *incoming* emails, you have to import the " +"private key of your Zammad email account." msgstr "" -#: ../system/subscription/billing.rst:46 -msgid "Date" +#: ../system/integrations/pgp/index.rst:57 +msgid "Import Keys From a File" msgstr "" -#: ../system/subscription/billing.rst:46 -msgid "Date of the invoice creation." +#: ../system/integrations/pgp/index.rst:58 +msgid "You can import keys from a file in the section **Upload key**:" msgstr "" -#: ../system/subscription/billing.rst:49 -msgid "Amount" +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of adding a key via file" msgstr "" -#: ../system/subscription/billing.rst:49 -msgid "Invoice total including VAT if applicable." +#: ../system/integrations/pgp/index.rst:64 +msgid "" +"**Supported file formats:** ASCII-armor as well as binary GPG format " +"(basically any GPG supported key format) is supported here." msgstr "" -#: ../system/subscription/billing.rst:52 -msgid "" -"Contains contract period (monthly or yearly) and hosted plan for the " -"subscription period in question." +#: ../system/integrations/pgp/index.rst:68 +msgid "Import Keys by Pasting the Content" msgstr "" -#: ../system/subscription/billing.rst:63 -msgid "Payment method / Service period" +#: ../system/integrations/pgp/index.rst:69 +msgid "You can also paste the key's content in the section **paste key**:" msgstr "" -#: ../system/subscription/billing.rst:56 -msgid "" -"Used bank account or credit card as well as the subscription period the " -"invoice is about." +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of adding a key via pasting" msgstr "" -#: ../system/subscription/billing.rst:61 +#: ../system/integrations/pgp/index.rst:75 msgid "" -"It might happen that the invoice date and subscription period differ. This " -"is nothing to worry about, the subscription periods will be accounted later " -"on." +"**Supported format:** Please note that only ASCII-armor is supported here." msgstr "" -#: ../system/subscription/billing.rst:67 -msgid "Receipt" +#: ../system/integrations/pgp/index.rst:78 +msgid "Deleting Keys" msgstr "" -#: ../system/subscription/billing.rst:66 +#: ../system/integrations/pgp/index.rst:79 msgid "" -"Use the arrow to download the invoice in question. You can download all " -"available invoices any time you need to here!" +"If you want to delete a specific key, you can do it by clicking on the menu " +"in the *actions* column and select **delete**:" msgstr "" -#: ../system/subscription/billing.rst:0 -msgid "Screenshot showing payment history of a hosted instance" +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of deleting a key" msgstr "" -#: ../system/subscription/billing.rst:94 -msgid "Do you want to cancel your subscription?" +#: ../system/integrations/pgp/index.rst:88 +msgid "Downloading Keys" msgstr "" -#: ../system/subscription/billing.rst:73 +#: ../system/integrations/pgp/index.rst:89 msgid "" -"In case you no longer want to use Zammad's SaaS, you can cancel your " -"subscription by using the red *Yes, please cancel my subscription* button." +"If you want to download your keys, you can do this as well via corresponding " +"action buttons. Depending on the key, you can choose wether you want to " +"download the private or the public key." msgstr "" -#: ../system/subscription/billing.rst:76 -msgid "" -"Your subscription will end the day after your trial or billing period ends." +#: ../system/integrations/pgp/index.rst:95 +#: ../system/integrations/smime/manage-certificates.rst:76 +msgid "Default Behavior" msgstr "" -#: ../system/subscription/billing.rst:80 +#: ../system/integrations/pgp/index.rst:96 msgid "" -"We will remind you about your cancelled subscription several times up front. " -"After the subscription ended all instance data will be removed. A restore " -"*is not* possible after that point!" +"Here you can adjust on per group basis, if *sign* and *encryption* is on or " +"off by default. Please be aware, that agents can always override the setting " +"for each individual article." msgstr "" -#: ../system/subscription/billing.rst:0 -msgid "Screencast showing how to cancel a subscription" +#: ../system/integrations/pgp/index.rst:None +msgid "Adjusting default behavior on per group basis" msgstr "" -#: ../system/subscription/billing.rst:87 -msgid "**😖 Cancelled by accident?**" +#: ../system/integrations/pgp/index.rst:107 +msgid "" +"Here you can see the last actions regarding signing and encryption and if " +"they were successful." msgstr "" -#: ../system/subscription/billing.rst:89 -msgid "" -"You can always undo the cancellation via the *Yes, undo the cancellation of " -"my subscription* button up to the last subscription day!" +#: ../system/integrations/pgp/index.rst:117 +msgid "**Sign button is not visible, but keys are imported.**" +msgstr "" + +#: ../system/integrations/pgp/index.rst:115 +msgid "Did you choose a group in the ticket?" msgstr "" -#: ../system/subscription/billing.rst:0 +#: ../system/integrations/pgp/index.rst:116 msgid "" -"Screenshot showing a red button to cancel the subscription\n" -"cancellation" +"Did you import a private key for the email adress, which is used for " +"outgoing emails in the group?" msgstr "" -#: ../system/subscription/index.rst:2 -msgid "Subscription (SaaS)" +#: ../system/integrations/pgp/index.rst:122 +msgid "**How to obtain keys?**" msgstr "" -#: ../system/subscription/index.rst:4 +#: ../system/integrations/pgp/index.rst:120 msgid "" -"The subscription settings page allows you to configure your instances " -"package and number of agents required." +"You can create them yourself! There are some good tutorials on the web on " +"how to create them. Providing keys to Zammad is a prerequisite to use the " +"PGP feature." msgstr "" -#: ../system/subscription/index.rst:9 -msgid "" -"This setting section is only available for Hosted setups. If you're looking " -"for on premise support contracts, please see the `Zammad pricing page " -"`_." +#: ../system/integrations/pgp/index.rst:127 +msgid "**It says a passphrase is needed, but I haven't got one.**" msgstr "" -#: ../system/subscription/index.rst:20 +#: ../system/integrations/pgp/index.rst:125 msgid "" -"The subscription section currently consists of two tabs: Plan & Billing. For " -"your overview we've divided those two tabs into independent sub pages:" +"If the key is secured with a passphrase, you have to provide it for the " +"import in Zammad. It is possible that keys may have an empty passphrase. " +"However, this is *not* recommended." msgstr "" -#: ../system/subscription/index.rst:25 -msgid ":doc:`💰 Subscription plan `" +#: ../system/integrations/pgp/index.rst:132 +msgid "**How do my customers get my new key?**" msgstr "" -#: ../system/subscription/index.rst:24 +#: ../system/integrations/pgp/index.rst:130 msgid "" -"Everything affecting your instance subscription functions like number of " -"agents, package and payment method." +"You have to provide your **public** key in advance. Your customer also has " +"to configure PGP in their email workflow and import your public key. The " +"other way round, you have to get the public key of your customer and have to " +"import it to Zammad." +msgstr "" + +#: ../system/integrations/slack.rst:2 +msgid "Slack" msgstr "" -#: ../system/subscription/index.rst:28 -msgid ":doc:`🧾 Subscription billing `" +#: ../system/integrations/slack.rst:4 +msgid "**⚠️ Deprecation warning ⚠️**" msgstr "" -#: ../system/subscription/index.rst:28 +#: ../system/integrations/slack.rst:6 msgid "" -"Everything regarding billing address, invoices and account cancellation." +"Zammad 7 will no longer support this dedicated Slack integration. It is " +"recommended to switch to :doc:`pre-defined webhooks ` instead. Existing Slack integrations should " +"be migrated manually before this feature is dropped." msgstr "" -#: ../system/subscription/index.rst:33 -msgid "FAQ" +#: ../system/integrations/slack.rst:14 +msgid "" +"In order to use this feature, please add a new Slack app to your Workspace. " +"The App you need is called ``Incoming WebHooks`` ." msgstr "" -#: ../system/subscription/index.rst:37 -msgid "I set up a trial account but am missing functions to test" +#: ../system/integrations/slack.rst:18 +msgid "Why Do I Need This Feature?" msgstr "" -#: ../system/subscription/index.rst:36 +#: ../system/integrations/slack.rst:20 msgid "" -"The trial instance is running within the professional package allowing up to " -"three agents." +"If you're already using Slack for your team communication, you'll love this " +"feature! Our Slack integration can push ticket notifications about the last " +"ticket article based on the following events:" msgstr "" -#: ../system/subscription/index.rst:40 -msgid "Can I change package within the trial?" +#: ../system/integrations/slack.rst:24 +msgid "on Ticket creation" msgstr "" -#: ../system/subscription/index.rst:40 -msgid "No. As soon as the package is changed the subscription begins." +#: ../system/integrations/slack.rst:25 +msgid "on Ticket updates" msgstr "" -#: ../system/subscription/index.rst:45 -msgid "What happens to my trial instance after the trial period ended?" +#: ../system/integrations/slack.rst:26 +msgid "on reached reminders" msgstr "" -#: ../system/subscription/index.rst:43 -msgid "" -"Your instance will automatically be canceled for you. Please see *What " -"happens to my instance after it has been canceled?* for more." +#: ../system/integrations/slack.rst:27 +msgid "a Ticket has escalated" msgstr "" -#: ../system/subscription/index.rst:58 -msgid "What happens to my instance after it has been canceled?" +#: ../system/integrations/slack.rst:28 +msgid "a Ticket is going to escalate" msgstr "" -#: ../system/subscription/index.rst:48 -msgid "That depends slightly on your instance state:" +#: ../system/integrations/slack.rst:30 +msgid "" +"Zammad will provide the Ticket title, a direct link to the Ticket, the event " +"type (creation, updated, escalation), the customer, time and the last " +"article that has triggered the notification." msgstr "" -#: ../system/subscription/index.rst:54 -msgid "Trial instance" +#: ../system/integrations/slack.rst:34 +msgid "" +"This will give you further options, as you can see e.g. escalating tickets " +"that are assigned to an agent that's e.g. absent. You can interact faster, " +"as you might see problems earlier (or even before the problem gets one)." msgstr "" -#: ../system/subscription/index.rst:51 +#: ../system/integrations/slack.rst:38 msgid "" -"If you're still on trial, we will ice your instance and remind you once " -"again about your instance. We then will wait some days and remove your " -"instance from our system. This is the last time we will inform you by Email." +"If needed and wanted, you can even discuss directly about the topic before " +"sending an answer to the customer. Another possible use case would be a " +"agent monitoring new agents and their answers to tickets." msgstr "" -#: ../system/subscription/index.rst:58 -msgid "Paid instance" +#: ../system/integrations/slack.rst:44 +msgid "Configure the Integration" msgstr "" -#: ../system/subscription/index.rst:57 +#: ../system/integrations/slack.rst:46 msgid "" -"If you're a paying customer and canceled your subscription, the instance " -"removal will take place the day after your last subscription day." +"First of all, please go to your slack workspace - go to administration => " +"Manage Apps. If you don't have an app yet, you can simply add a new one - " +"just search for ``Incoming WebHooks`` and customize the app to your needs." msgstr "" -#: ../system/subscription/index.rst:60 -msgid "Can removed instances be restored?" +#: ../system/integrations/slack.rst:50 +msgid "" +"Choose (or create) the channel Zammad should post it's information to and " +"press on \"Add Incoming WebHooks integration\". If you're ready, copy the " +"provided WebHook URL and go to your Zammad installation." msgstr "" -#: ../system/subscription/index.rst:61 -msgid "No. Once your instance has been removed, a restoration is not possible." +#: ../system/integrations/slack.rst:56 +msgid "" +"You need administrative rights on the Slack Workspace. The link to the app " +"directory is normally ``https://[workspace-name].slack.com/apps`` ." msgstr "" -#: ../system/subscription/plan.rst:2 ../system/subscription/plan.rst:38 -msgid "Plan" +#: ../system/integrations/slack.rst:63 +msgid "" +"To configure the slack integration, log in to Zammad and go to Integrations " +"(System) => Slack in the admin panel." msgstr "" -#: ../system/subscription/plan.rst:16 -msgid "Subscription" +#: ../system/integrations/slack.rst:66 +msgid "" +"Here you can choose on what evens Zammad should post information about a " +"ticket to your Slack channel. Next you need to device what groups shall be " +"affected by this, as anybody with access to that specific Slack channel can " +"read at least parts of the ticket this might be a privacy issue, if you " +"select the wrong groups. The username is simply the name that Zammad uses as " +"display name inside the Slack chat. The channel defines the Slack channel " +"the information is being posted in. As last option, you can set a custom " +"icon for posting to slack." msgstr "" -#: ../system/subscription/plan.rst:5 +#: ../system/integrations/slack.rst:74 msgid "" -"On the top of the subscription summary you'll find the number of used and " -"available (booked) agent seats. By using the *see more* link you can also " -"expand an agent list to see the currently configured active agents. This " -"list *does not* count accounts with admin permissions only." +"When you're ready, just hit \"Submit\" and enable the integration. Zammad " +"will now post new ticket information based on the trigger you chose. Below " +"the options you have the recent log that shows the latest requests to Slack " +"for debugging if needed." msgstr "" -#: ../system/subscription/plan.rst:0 +#: ../system/integrations/slack.rst:81 msgid "" -"Within subscription you can always see how many agents are still\n" -"available to add and who uses the seats." +"If you leave the Icon URL empty, Zammad will use the Zammad logo instead. " +"The icon should be a square PNG file." msgstr "" -#: ../system/subscription/plan.rst:14 +#: ../system/integrations/slack.rst:90 msgid "" -"Learn more on how to manage your agents in general :doc:`here `." +"The following figure shows how it will look if you choose to receive updates " +"on created and updated tickets. On every post Zammad sends to the Slack " +"channel, you can create new threads to discuss about the new article." msgstr "" -#: ../system/subscription/plan.rst:19 +#: ../system/integrations/slack.rst:96 msgid "" -"This section gives you an overview of the available plans and their " -"functions / limits. If you require a more detailed table, check our " -"`detailed pricing table `_ for more." +"If you just want to keep track of soon escalating or already escalated " +"tickets, it will look the the following figure. Zammad changes the color in " +"front of the post so you can easily see the state of the ticket." msgstr "" -#: ../system/subscription/plan.rst:23 +#: ../system/integrations/slack.rst:102 msgid "" -"Your selection in this step will decide on the base agent price and e.g. " -"agent limits that might apply in the summary step." +"If you change the state, Zammad will also put information on what state the " +"ticket gets and (if pending state) the date until it pends. You'll also " +"recognize the color codes in front of posts on slack, as they are exact the " +"same the ticket state colors you'll see in Zammad!" msgstr "" -#: ../system/subscription/plan.rst:26 -msgid "" -"The green *Selected* button will also tell you what plan you're currently in." +#: ../system/integrations/smime/index.rst:2 +msgid "S/MIME" msgstr "" -#: ../system/subscription/plan.rst:30 +#: ../system/integrations/smime/index.rst:11 msgid "" -"Trial instances are running at Professional with 3 agents. The plan cannot " -"be changed during the trial for technical reasons, if you require more " -"agents for testing, please contact `our sales team `_ with a reason for the raise request." +"S/MIME is the most widely-supported method for secure email communication. " +"With S/MIME, you can exchange **signed** and **encrypted** messages with " +"others." msgstr "" -#: ../system/subscription/plan.rst:0 +#: ../system/integrations/smime/index.rst:15 msgid "" -"Screenshot showing three available packages for a hosted Zammad\n" -"instance" +"is proof that a message hasn't been tampered with or sent by an impersonator." msgstr "" -#: ../system/subscription/plan.rst:83 -msgid "Summary" +#: ../system/integrations/smime/index.rst:17 +msgid "" +"In other words, it guarantees a message's **integrity** and **authenticity**." msgstr "" -#: ../system/subscription/plan.rst:41 -msgid "" -"In this section you can adjust the settings of the previous selected plan." +#: ../system/integrations/smime/index.rst:22 +msgid "In other words, it guarantees **privacy** and **data security**." msgstr "" -#: ../system/subscription/plan.rst:45 -msgid "" -"Note that upgrading (more agents, higher package) is always possible, " -"however, downgrading will only happen when your billing period renews." +#: ../system/integrations/smime/index.rst:28 +msgid "Screencast demo of S/MIME features for both new tickets and replies" msgstr "" -#: ../system/subscription/plan.rst:49 +#: ../system/integrations/smime/index.rst:28 msgid "" -"Upgrading resets your billing period and existing credit will be deducted " -"from the new total." +"Once S/MIME has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " +"appear in the ticket composer." msgstr "" -#: ../system/subscription/plan.rst:58 -msgid "Billing cycle" +#: ../system/integrations/smime/index.rst:32 +msgid ":doc:`🔪 Prerequisites `" msgstr "" -#: ../system/subscription/plan.rst:53 +#: ../system/integrations/smime/index.rst:31 msgid "" -"You can choose between either monthly or yearly billing. The price per agent " -"will be cheaper if you decide for yearly billing." +"New to S/MIME? This section helps you to find certificate providers and " +"points out Limitations." msgstr "" -#: ../system/subscription/plan.rst:56 -msgid "" -"If you're still trying out things and are unsure of the right package for " -"your instance, you may want to choose monthly first and then upgrade to " -"yearly when you're sure." +#: ../system/integrations/smime/index.rst:35 +msgid ":doc:`📝 Manage Certificates `" msgstr "" -#: ../system/subscription/plan.rst:66 -msgid "Plan: (Starter|Professional|Plus) - Agents" +#: ../system/integrations/smime/index.rst:35 +msgid "Add and download certificates; configure group default behaviors." msgstr "" -#: ../system/subscription/plan.rst:61 -msgid "Choose the number of agents you require for your instance." +#: ../system/integrations/smime/index.rst:38 +msgid ":doc:`😦 Troubleshooting `" msgstr "" -#: ../system/subscription/plan.rst:63 -msgid "" -"Keep in mind that some packages may have agent limits. Depending on the " -"previous chosen package, you won't be able to exceed specific agent numbers. " -"Also note that setting less agents than currently configured is not possible." +#: ../system/integrations/smime/index.rst:38 +msgid "Took a wrong turn? About recent logs and common issues." msgstr "" -#: ../system/subscription/plan.rst:69 -msgid "Total" +#: ../system/integrations/smime/index.rst:43 +msgid "" +"For more details on how S/MIME integration works on the agent side, see the :" +"user-docs:`user docs `." msgstr "" -#: ../system/subscription/plan.rst:69 -msgid "This will be the net total you're going to be billed." +#: ../system/integrations/smime/manage-certificates.rst:2 +msgid "Manage Certificates" msgstr "" -#: ../system/subscription/plan.rst:71 +#: ../system/integrations/smime/manage-certificates.rst:4 msgid "" -"By using the *Update subscription* button, the instance package will be " -"adjusted immediately. If you didn't provide a payment method yet, Zammad " -"will request you to provide one at this point." +"S/MIME is **disabled by default**. Enable it to start adding certificates." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:10 +msgid "Dialogue to add new certificates or private keys" msgstr "" -#: ../system/subscription/plan.rst:77 +#: ../system/integrations/smime/manage-certificates.rst:10 msgid "" -"In case you're still within the trial period, this means that the trial will " -"be over immediately!" +"Manage certificates in the Admin Panel under **System > Integrations > S/" +"MIME**. Certificates may be pasted in as plain text or uploaded from a file." msgstr "" -#: ../system/subscription/plan.rst:80 -msgid "Down- or upgrading during the trial period *is not* possible." +#: ../system/integrations/smime/manage-certificates.rst:14 +msgid "Add Certificate Data" msgstr "" -#: ../system/subscription/plan.rst:0 -msgid "Screenshot showing payment options and a pricing summary" +#: ../system/integrations/smime/manage-certificates.rst:36 +msgid "Add Certificate" msgstr "" -#: ../system/subscription/plan.rst:99 -msgid "Payment method" +#: ../system/integrations/smime/manage-certificates.rst:17 +msgid "" +"Import public-key certificates for both your own organization and your " +"contacts." msgstr "" -#: ../system/subscription/plan.rst:86 -msgid "You can pay via credit card or SEPA mandate." +#: ../system/integrations/smime/manage-certificates.rst:19 +msgid "" +"You can also add a bunch of certificates in one go by providing a single " +"file with all relevant certificates." msgstr "" -#: ../system/subscription/plan.rst:91 -msgid "Credit card" +#: ../system/integrations/smime/manage-certificates.rst:22 +msgid "🕵️ **ALWAYS verify certificates in-person or over the phone!**" msgstr "" -#: ../system/subscription/plan.rst:89 +#: ../system/integrations/smime/manage-certificates.rst:24 msgid "" -"Simply follow the dialogue by clicking *authorize* and confirm -if required " -"by your bank- your consent to Zammad using your card for the payments." +"The whole point of signatures is to alert you when someone is trying to " +"pretend to be someone they're not. Never accept a certificate from someone " +"online without verifying it first." msgstr "" -#: ../system/subscription/plan.rst:95 -msgid "SEPA" +#: ../system/integrations/smime/manage-certificates.rst:28 +msgid "📇 **What about trusted certificate authorities?**" msgstr "" -#: ../system/subscription/plan.rst:94 +#: ../system/integrations/smime/manage-certificates.rst:30 msgid "" -"Provide the requested information of the bank account holder and update if " -"you're ready. You'll then receive an email with the SEPA mandate." +"In some cases (e.g. when dealing with large enterprises), you may be given a " +"certificate for an entire CA, rather than a single contact. Add it here to " +"trust *all* certificates issued by that CA." msgstr "" -#: ../system/subscription/plan.rst:97 +#: ../system/integrations/smime/manage-certificates.rst:35 msgid "" -"Technically there's also the possibility to pay via invoice, however - this " -"method only applies to a fairly low number of instances. Please contact `our " -"sales team `_ for more information." +"Commercial CAs can usually be verified online. Zammad does not include a " +"list of built-in, trusted CAs." msgstr "" -#: ../system/translations.rst:2 -msgid "Translations" +#: ../system/integrations/smime/manage-certificates.rst:57 +msgid "Add Private Key" msgstr "" -#: ../system/translations.rst:4 +#: ../system/integrations/smime/manage-certificates.rst:39 msgid "" -"Translations of Zammad are processed centrally in our `Weblate instance " -"`_. This allows non-developers to review " -"and update translation texts of the language they actually speak." +"Once you've added a public-key certificate, you can import its matching " +"private key." msgstr "" -#: ../system/translations.rst:9 +#: ../system/integrations/smime/manage-certificates.rst:42 msgid "" -"Your language is in an incomplete translation state or has typos? Please " -"consider helping us in sorting this out! All you need is either a GitHub " -"account or to register directly in our instance." +"Private keys are for **your own organization only**; never ask your contacts " +"for their private keys." msgstr "" -#: ../system/translations.rst:13 +#: ../system/integrations/smime/manage-certificates.rst:0 msgid "" -"Did you know? This is also where the documentation translations are handled. " -"🤓" +"S/MIME integration showing configured certificates and possible issues with " +"Logging" msgstr "" -#: ../system/translations.rst:15 +#: ../system/integrations/smime/manage-certificates.rst:50 msgid "" -"Have a look in our :docs:`contribution section ` in the system documentation to get started!" +"A note is displayed on certificates with a matching private key (see line 2)." msgstr "" -#: ../system/translations.rst:20 -msgid "Local Translations" +#: ../system/integrations/smime/manage-certificates.rst:52 +msgid "📤 **Certificates and private keys must be uploaded separately.**" msgstr "" -#: ../system/translations.rst:22 +#: ../system/integrations/smime/manage-certificates.rst:54 msgid "" -"Apart from these system translations, there's still local translations you " -"can manage. This is relevant if you added custom objects that require " -"translations or even custom states and priorities." +"If your certificate and private key are bundled together in the same file or " +"PEM block, import it twice (once using each button)." msgstr "" -#: ../system/translations.rst:None -msgid "Translation management screen within the admin menu" +#: ../system/integrations/smime/manage-certificates.rst:57 +msgid "Please note that bulk imports of private keys are not possible." msgstr "" -#: ../system/translations.rst:31 -msgid "Updating Translations" +#: ../system/integrations/smime/manage-certificates.rst:60 +msgid "Download Certificate Data" msgstr "" -#: ../system/translations.rst:33 +#: ../system/integrations/smime/manage-certificates.rst:62 msgid "" -"Because of how Zammad ships translations, the only way to update the system " -"translations is to update your Zammad installation. The benefit of this is " -"that you no longer need internet access during a Zammad upgrade as the " -"package has everything it requires already." +"You can download the earlier provided certificates and private keys at any " +"time from your Zammad instance." msgstr "" -#: ../system/translations.rst:39 -msgid "Translation of Custom Objects" +#: ../system/integrations/smime/manage-certificates.rst:65 +msgid "" +"Please note that passphrase-protected private keys stay protected and when " +"you download them, you have to know the passphrase to use them after " +"downloading." msgstr "" -#: ../system/translations.rst:41 -msgid "" -"No problem at all! You can customize any translation locally, even if it is " -"not initially provided by the system." +#: ../system/integrations/smime/manage-certificates.rst:73 +msgid "Dialogue to download certificates or private keys" msgstr "" -#: ../system/translations.rst:44 +#: ../system/integrations/smime/manage-certificates.rst:73 +msgid "Download stored certificates and their keys" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:78 msgid "" -"Translation is supported for a broad number of features, including but not " -"limited to custom:" +"The ticket composer will set all outgoing messages to **signed and " +"encrypted** by default (assuming the required certificates exist)." msgstr "" -#: ../system/translations.rst:47 -msgid "Object Attributes" +#: ../system/integrations/smime/manage-certificates.rst:82 +msgid "These defaults can be modified on a per-group basis:" msgstr "" -#: ../system/translations.rst:48 -msgid "Ticket Macros" +#: ../system/integrations/smime/manage-certificates.rst:None +msgid "Zammad allowing to choose the default behavior on per group basis" msgstr "" -#: ../system/translations.rst:49 -msgid "Ticket Overviews" +#: ../system/integrations/smime/manage-certificates.rst:89 +msgid "" +"Of course, agents can always manually change these settings on each email " +"they send out." msgstr "" -#: ../system/translations.rst:50 -msgid "Ticket Priorities" +#: ../system/integrations/smime/prerequisites.rst:4 +msgid "A certificate *and* private key for your own organization" msgstr "" -#: ../system/translations.rst:51 -msgid "Ticket States" +#: ../system/integrations/smime/prerequisites.rst:6 +msgid "" +"(Use this to ✒️ **sign outgoing messages** and 🔓 **decrypt incoming " +"messages**.)" msgstr "" -#: ../system/translations.rst:54 -msgid "Customizing Translations" +#: ../system/integrations/smime/prerequisites.rst:9 +msgid "" +"Certificates belonging your contacts, or their issuing certificate authority " +"(CA)" msgstr "" -#: ../system/translations.rst:56 +#: ../system/integrations/smime/prerequisites.rst:11 msgid "" -"Within the translation screen, simply click on the **New Translation** " -"button." +"(Use these to ✅ **verify incoming message signatures** and 🔒 **encrypt " +"outgoing messages**.)" msgstr "" -#: ../system/translations.rst:None -msgid "New translation dialog" +#: ../system/integrations/smime/prerequisites.rst:14 +msgid "🙋 **I'm new to S/MIME. Where can I get a certificate?**" msgstr "" -#: ../system/translations.rst:62 +#: ../system/integrations/smime/prerequisites.rst:16 msgid "" -"In the dialog you can immediately enter the exact translation source (if you " -"know it) and your custom translation text for it and click **Submit**." +"The easiest way to get certificates is to buy an annual subscription through " +"a commercial CA, such as:" msgstr "" -#: ../system/translations.rst:65 +#: ../system/integrations/smime/prerequisites.rst:19 msgid "" -"Alternatively, try to search for translation suggestions in the list below. " -"Selecting an item from the list will pre-fill the translation source for you " -"and then you can just enter your custom translation." +"`Sectigo (formerly Comodo) `_" msgstr "" -#: ../system/translations.rst:69 -msgid "" -"The target language will always default to your current language selection. " -"If you need to translate for a different language, simply change the " -"selection before submitting." +#: ../system/integrations/smime/prerequisites.rst:20 +msgid "`Secorio `_" msgstr "" -#: ../system/translations.rst:73 -msgid "" -"All your custom translations will show up in the overview table when added. " -"And they will even persist across Zammad updates!" +#: ../system/integrations/smime/prerequisites.rst:21 +msgid "`GlobalSign `_" msgstr "" -#: ../system/translations.rst:76 -msgid "" -"Make sure to reload your browser if a translated string is not displayed." +#: ../system/integrations/smime/prerequisites.rst:23 +msgid "(Zammad is not affiliated with these CAs in any way.)" msgstr "" -#: ../system/translations.rst:80 -msgid "Reverting to Original Translations" +#: ../system/integrations/smime/prerequisites.rst:25 +msgid "" +"You can also generate your own self-signed certificates, but the process is " +"complicated and usually 🙅 **involves extra work for your contacts**." msgstr "" -#: ../system/translations.rst:82 +#: ../system/integrations/smime/prerequisites.rst:29 msgid "" -"If you want to revert a custom translation to original text, simply use the " -"appropriate action within the row of the overview table." +"Bear in mind that 🤝 **S/MIME only works if the other party is using it, too." +"**" msgstr "" -#: ../system/translations.rst:85 +#: ../system/integrations/smime/prerequisites.rst:32 +msgid "Certificate and Private Key Checks on Upload" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:34 msgid "" -"Depending on the type of the translation source, the action has a slightly " -"different name:" +"The certificate and public key validation is based on the ``X509v3`` " +"extensions." msgstr "" -#: ../system/translations.rst:88 -msgid "**Reset** for customized system translations" +#: ../system/integrations/smime/prerequisites.rst:49 +msgid "Uploading a *client certificate*?" msgstr "" -#: ../system/translations.rst:89 -msgid "**Remove** for customized local translations" +#: ../system/integrations/smime/prerequisites.rst:41 +msgid "The following attributes are required then:" msgstr "" -#: ../system/translations.rst:91 -msgid "" -"In both cases, the action will remove the customized translation after a " -"confirmation." +#: ../system/integrations/smime/prerequisites.rst:39 +msgid "Subject Alternative Name (at least one email address has to be present)" msgstr "" -#: ../system/translations.rst:None -msgid "Screenshot showing the location of the Remove action" +#: ../system/integrations/smime/prerequisites.rst:40 +msgid "Key Usage (``Digital Signature`` and/or ``Key Encipherment``)" msgstr "" -#: ../system/translations.rst:99 -msgid "Inline Translations" +#: ../system/integrations/smime/prerequisites.rst:41 +msgid "Public key algorithm (either ``RSA`` or ``EC``)" msgstr "" -#: ../system/translations.rst:101 +#: ../system/integrations/smime/prerequisites.rst:43 msgid "" -"If you prefer a more hands-on approach, you can activate the inline or on-" -"screen translation feature by pressing ``ctrl`` + ``alt`` + ``t`` at any " -"time and on any screen." +"The Extended Key Usage attribute is optional. If the certificate provides " +"the named attribute, than it must contain the value ``E-mail Protection``." msgstr "" -#: ../system/translations.rst:105 +#: ../system/integrations/smime/prerequisites.rst:46 msgid "" -"All customizable translation texts will be highlighted for you on the " -"screen. Just click into the highlighted area and update the text in place." +"Please note that any usable email adress has to be prefixed with ``email:`` " +"or ``rfc822:``." msgstr "" -#: ../system/translations.rst:None -msgid "Inline translation mode activated for the Overview screen" +#: ../system/integrations/smime/prerequisites.rst:49 +msgid "The named public key algorithms are mandatory for private keys as well." msgstr "" -#: ../system/translations.rst:112 +#: ../system/integrations/smime/prerequisites.rst:54 +msgid "Uploading a *CA certificate*?" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:52 msgid "" -"When finished editing, simply press ``ctrl`` + ``alt`` + ``t`` again to " -"deactivate." +"In the case of an uploaded CA certificate, providing the value ``CA:TRUE`` " +"in the attribute *Basic Contstraints*, the previously mentioned attributes " +"are not verified." msgstr "" -#: ../system/translations.rst:117 +#: ../system/integrations/smime/prerequisites.rst:56 msgid "" -"Even though it's available on any screen, the inline translation feature " -"requires admin permissions. It works only for the current language " -"selection. If you need to translate a different language, first change the " -"language in your :user-docs:`profile settings `." +"In general, the usage of any expired (``Not After``) or not yet valid (``Not " +"Before``) certificate is denied for outgoing emails." msgstr "" -#: ../system/variables.rst:2 -msgid "Variables" +#: ../system/integrations/smime/prerequisites.rst:59 +msgid "Example certificate:" msgstr "" -#: ../system/variables.rst:4 +#: ../system/integrations/smime/prerequisites.rst:85 msgid "" -"Please note that this is just an overview of available variables. It might " -"be incomplete or variables might not be available within some functions. If " -"you're missing variables or are not sure if something is not working as " -"expected, feel free to ask over at the `Community `_." +"Please note that Zammad will distrust senders by default. This means that " +"you're always required to provide certificate data, no matter if for signing " +"or encrypting." msgstr "" -#: ../system/variables.rst:10 -msgid "" -"Variables can be called by typing ``::`` (just like text modules in the " -"frontend), as long as you're in a supported text field within the backend. " -"Zammad will display all variables being available within this context and " -"replace it to the variable as soon as you selected an entry." +#: ../system/integrations/smime/prerequisites.rst:89 +msgid "This is by design and can't be adjusted." msgstr "" -#: ../system/variables.rst:15 +#: ../system/integrations/smime/troubleshooting.rst:4 msgid "" -"You have an empty field which you referenced and it appears as ``-``? That's " -"currently working as designed - you might want to ensure that these fields " -"always have a value." +"All of the system's latest S/MIME activity is displayed in the **Recent " +"Logs** section." msgstr "" -#: ../system/variables.rst:20 -msgid "Variable Categories" +#: ../system/integrations/smime/troubleshooting.rst:11 +msgid "Sample entries of in- and outgoing S/MIME related emails." msgstr "" -#: ../system/variables.rst:31 -msgid "Wait, What About Custom Objects?" +#: ../system/integrations/smime/troubleshooting.rst:11 +msgid "" +"Logs report the status and details of all mail, both incoming and outgoing, " +"that used signing/verification or encryption/decryption." msgstr "" -#: ../system/variables.rst:33 +#: ../system/integrations/smime/troubleshooting.rst:14 msgid "" -"Good point! Of course, we can't predict what objects you might create, but " -"we can give you a hint on how to put the puzzle together to get your custom " -"values." +"This log does **not** include email sent by :doc:`triggers ` or the :doc:`scheduler `. For those, check your " +"``production.log``." +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:20 +msgid "Common Issues" +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:30 +msgid "I received a signed/encrypted email before I set up S/MIME integration" msgstr "" -#: ../system/variables.rst:36 +#: ../system/integrations/smime/troubleshooting.rst:23 msgid "" -"For this, we'll talk about the inner part of the variable (so everything " -"within ``#{}``), please put the outer part around to have a valid variable. " -"The first part of the variable name consist of the object type. Currently " -"these are:" +"No problem. Once S/MIME has been enabled and the appropriate certificates " +"have been added, agents will be prompted to retry verification/decryption on " +"matching emails." msgstr "" -#: ../system/variables.rst:41 -msgid "Ticket (``ticket``)" +#: ../system/integrations/smime/troubleshooting.rst:0 +msgid "Screenshot of user prompt to retry decryption" msgstr "" -#: ../system/variables.rst:42 -msgid "User (``user``)" +#: ../system/integrations/smime/troubleshooting.rst:38 +msgid "The 🔒 **Encrypt** button is disabled" msgstr "" -#: ../system/variables.rst:43 -msgid "Organization (``organization``)" +#: ../system/integrations/smime/troubleshooting.rst:33 +msgid "Have you added the recipient's certificate?" msgstr "" -#: ../system/variables.rst:44 -msgid "Group (``group``)" +#: ../system/integrations/smime/troubleshooting.rst:34 +msgid "Are you sure the recipient's certificate is valid?" msgstr "" -#: ../system/variables.rst:46 -msgid "" -"The second part is the name of the object. This is the name you define " -"during object creation and can be found within the object menu at any time. " -"The first and second part of a variable is divided by a point, e.g.: " -"``ticket.number`` which will in total be ``#{ticket.number}``." +#: ../system/integrations/smime/troubleshooting.rst:35 +msgid "Have you checked your ``production.log`` for more details?" msgstr "" -#: ../system/variables.rst:51 +#: ../system/integrations/smime/troubleshooting.rst:37 msgid "" -"Now, in some situations it's possible that you'll need to use a third part. " -"The best example for such a situation would be a ``select`` or ``tree-" -"select`` field which will by default return the key value, not it's display " -"name. For this, just extend your variable with ``.value``. This will result " -"in ``#{ticket.select.value}``." +"If encryption doesn't work in the composer, it won't work in :doc:`triggers " +"` or the :doc:`scheduler ` either!" msgstr "" -#: ../system/variables.rst:60 -msgid "Using Translated Variables" +#: ../system/integrations/smime/troubleshooting.rst:42 +msgid "The ✅ **Sign** button is disabled" msgstr "" -#: ../system/variables.rst:62 +#: ../system/integrations/smime/troubleshooting.rst:41 msgid "" -"If you want to use a translated variable in triggers or schedulers, you can " -"extend the placeholder like this: ``#{t(ticket.state.name)}``. The ``t`` " -"tells Zammad to search for fitting translated strings. The used output " -"language is based on the system language of Zammad which you can set in the " -"admin panel under :doc:`/settings/branding` or based on the selected locale " -"in the trigger/scheduler edit dialog." +"Have you added **both the certificate and private key** for your " +"organization?" msgstr "" -#: ../system/variables.rst:69 +#: ../system/integrations/smime/troubleshooting.rst:42 msgid "" -"A possible use-case: you want to send your customers updates on tickets via " -"trigger or scheduler which should include the state of the ticket. Using the " -"default ``#{ticket.state.name}`` (without the translation flag ``t()``) " -"would lead to the output of the original (english) name of the state." +"Does the email address on the certificate match the email address of the " +"agent/group composing the email?" msgstr "" -#: ../system/variables.rst:75 -msgid "Date and Time Formatting" +#: ../system/integrations/smime/troubleshooting.rst:45 +msgid "Error: “Fingerprint already taken”" msgstr "" -#: ../system/variables.rst:77 -msgid "" -"The system (trigger/scheduler selected) locale and timezone predefines a " -"default format of date and timestamp. This format is customizable by using " -"the ``dt()`` method." +#: ../system/integrations/smime/troubleshooting.rst:45 +msgid "Are you sure you haven't added this certificate already?" msgstr "" -#: ../system/variables.rst:79 -msgid "The method arguments are as follows:" +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Error: “❌ invalid byte sequence in UTF-8”" msgstr "" -#: ../system/variables.rst:81 -msgid "The date or timestamp variable you want to format." +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Please ensure to provide PEM formatted certificate and keys." msgstr "" -#: ../system/variables.rst:82 -msgid "The output format string." +#: ../system/integrations/smime/troubleshooting.rst:49 +msgid "Did you check if the provided file is a valid certificate or key?" msgstr "" -#: ../system/variables.rst:83 -msgid "The timezone to apply (optional)." +#: ../system/integrations/zabbix.rst:2 +msgid "Zabbix Integration" msgstr "" -#: ../system/variables.rst:86 +#: ../system/integrations/zabbix.rst:5 msgid "" -"``#{dt(ticket.updated_at, \"%A %Y-%m-%d %H:%M in the office\", \"Europe/" -"Berlin\")}``" +"This guide describes how to integrate your Zabbix 5.4 installation with " +"Zammad using the Zabbix webhook feature. This guide will provide " +"instructions on setting up a media type, a user and an action in Zabbix." msgstr "" -#: ../system/variables.rst:87 -msgid "Monday, 2024-03-18 15:31 in the office" +#: ../system/integrations/zabbix.rst:12 +msgid "Zammad with enabled HTTP Token Authentication" msgstr "" -#: ../system/variables.rst:89 -msgid "" -"If you want to use our example, make sure to paste the string above without " -"formatting (``CTRL+Shift+v``), otherwise it won't work." +#: ../system/integrations/zabbix.rst:13 +msgid "Zabbix version 5.4 or higher" msgstr "" -#: ../system/variables.rst:93 -msgid "The following table lists available format directives:" +#: ../system/integrations/zabbix.rst:16 +msgid "Setting up a Zammad" msgstr "" -#: ../system/variables.rst:99 -msgid "Parameter" +#: ../system/integrations/zabbix.rst:18 +msgid "Enable **API Token Access** in Settings > System > API." msgstr "" -#: ../system/variables.rst:102 -msgid "``%Y``" +#: ../system/integrations/zabbix.rst:20 +msgid "" +"Create a **new user** for a Zabbix alerter with an **email address** and " +"create a personal user token with **ticket.agent** permissions." msgstr "" -#: ../system/variables.rst:103 -msgid "Year with 4 digits" +#: ../system/integrations/zabbix.rst:24 +msgid "Zabbix Webhook Configuration" msgstr "" -#: ../system/variables.rst:104 -msgid "Use ``%y`` for year with 2 digits" +#: ../system/integrations/zabbix.rst:27 +msgid "Create a Global Macro" msgstr "" -#: ../system/variables.rst:105 -msgid "``%m``" +#: ../system/integrations/zabbix.rst:29 +msgid "" +"Before setting up the **Webhook**, you need to setup the global macro " +"**{$ZABBIX.URL}**, which must contain the **URL** to the **Zabbix frontend**." msgstr "" -#: ../system/variables.rst:106 -msgid "Month of year (as number with zero-padding)" +#: ../system/integrations/zabbix.rst:33 +msgid "" +"In the **Administration** > **Media types** section, import the `Template`_." msgstr "" -#: ../system/variables.rst:107 -msgid "Use ``%-m`` for month without zero-padding" +#: ../system/integrations/zabbix.rst:38 +msgid "Open the added **Zammad** media type and set:" msgstr "" -#: ../system/variables.rst:108 -msgid "``%d``" +#: ../system/integrations/zabbix.rst:40 +msgid "**zammad\\_access\\_token** to the your **Personal User Token**" msgstr "" -#: ../system/variables.rst:109 -msgid "Day of month (as number with zero-padding)" +#: ../system/integrations/zabbix.rst:41 +msgid "" +"**zammad\\_url** to the **frontend URL** of your **Zammad** installation" msgstr "" -#: ../system/variables.rst:110 -msgid "Use ``%e`` for day without zero-padding" +#: ../system/integrations/zabbix.rst:43 +msgid "**zammad\\_customer** to your **Zammad user email**." msgstr "" -#: ../system/variables.rst:111 -msgid "``%H``" +#: ../system/integrations/zabbix.rst:44 +msgid "" +"**zammad\\_enable\\_tags** to **true** or **false** to enable or disable " +"trigger tags. **Important**: if you enable tag support, each tag is set with " +"a separate request." msgstr "" -#: ../system/variables.rst:112 -msgid "Hour of day in 24h notation with zero-padding" +#: ../system/integrations/zabbix.rst:48 +msgid "" +"If you want to prioritize issues according to **severity** values in Zabbix, " +"you can define mapping parameters:" msgstr "" -#: ../system/variables.rst:113 -msgid "Use ``%k`` for hour without zero-padding" +#: ../system/integrations/zabbix.rst:51 +msgid "**severity\\_**: Zammad priority ID" msgstr "" -#: ../system/variables.rst:114 -msgid "``%I``" +#: ../system/integrations/zabbix.rst:53 +msgid "Click the **Update** button to save the **Webhook** settings." msgstr "" -#: ../system/variables.rst:115 -msgid "Hour of day in 12h notation with zero-padding" +#: ../system/integrations/zabbix.rst:55 +msgid "" +"To receive notifications in **Zammad**, you need to create a **Zabbix user** " +"and add **Media** with the **Zammad** type." msgstr "" -#: ../system/variables.rst:116 +#: ../system/integrations/zabbix.rst:58 msgid "" -"Use ``%l`` for hour without zero-padding and ``%p`` / ``%P`` for meridian " -"indicator" +"For **Send to**: enter any text, as this value is not used, but is required." msgstr "" -#: ../system/variables.rst:117 -msgid "``%M``" +#: ../system/integrations/zabbix.rst:61 +msgid "" +"For more information, use the `Zabbix documentation `_." msgstr "" -#: ../system/variables.rst:118 -msgid "Minute of hour" +#: ../system/maintenance.rst:2 +msgid "Maintenance" msgstr "" -#: ../system/variables.rst:120 -msgid "``%S``" +#: ../system/maintenance.rst:4 +msgid "" +"Zammad comes with a maintenance mode that you can use for e.g. updating the " +"instance or changing settings while restricting availability and functions." msgstr "" -#: ../system/variables.rst:121 -msgid "Second of Minute" +#: ../system/maintenance.rst:13 +msgid "Mode" msgstr "" -#: ../system/variables.rst:123 -msgid "``%A``" +#: ../system/maintenance.rst:8 +msgid "The mode setting allows you to enable or disable the maintenance mode." msgstr "" -#: ../system/variables.rst:124 -msgid "Weekday name" +#: ../system/maintenance.rst:10 +msgid "Defaults to *off*." msgstr "" -#: ../system/variables.rst:125 -msgid "Use ``%a`` for abbreviated name or ``%^A`` for uppercase name" +#: ../system/maintenance.rst:12 +msgid "" +"The maintenance mode will restrict access to administrative roles only. This " +"means agents and customers are logged off." msgstr "" -#: ../system/variables.rst:126 -msgid "``%B``" +#: ../system/maintenance.rst:23 +msgid "@Login" msgstr "" -#: ../system/variables.rst:127 -msgid "Month name" +#: ../system/maintenance.rst:16 +msgid "" +"This setting allows you to provide a login message within a green banner " +"above the login screen. Click into the green banner in the settings page to " +"adjust your message. To activate the message, activate the *@Login* setting." msgstr "" -#: ../system/variables.rst:128 -msgid "Use ``%b`` for abbreviated name" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing the default login message within the\n" +"settings page" msgstr "" -#: ../system/variables.rst:129 -msgid "``%U``" +#: ../system/maintenance.rst:26 +msgid "" +"Send an informative message to **all active sessions**. This comes handy to " +"inform your agents e.g. about mayor outages or to force reloads after " +"configuration changes." msgstr "" -#: ../system/variables.rst:130 -msgid "Week number of current year" +#: ../system/maintenance.rst:31 +msgid "This is the messages title (slightly bigger than the normal message)." msgstr "" -#: ../system/variables.rst:131 -msgid "Use ``%W`` for a different calculation method" +#: ../system/maintenance.rst:34 +msgid "The text you want to provide to your logged in sessions." msgstr "" -#: ../system/variables.rst:134 +#: ../system/maintenance.rst:39 +msgid "Reload application" +msgstr "" + +#: ../system/maintenance.rst:37 msgid "" -"We support the known format directives for the Ruby built-in method " -"``strftime`` of the ``DateTime`` class. For more information, see `here " -"`_." +"Selecting this option will change the message acceptance button from *Close* " +"(with nothing happening) to *Continue session*, which forces the application " +"to reload." msgstr "" -#: ../system/variables/article.rst:2 -msgid "Articles" +#: ../system/maintenance.rst:43 +msgid "" +"If you have customers that are logged in to Zammad, they'll also be notified " +"if they're active in that moment." msgstr "" -#: ../system/variables/article.rst:4 ../system/variables/config.rst:4 -#: ../system/variables/current-user.rst:4 ../system/variables/ticket.rst:4 +#: ../system/maintenance.rst:48 +msgid "Example without reload application" +msgstr "" + +#: ../system/maintenance.rst:52 msgid "" -"If you're missing variables or are not sure if something is not working as " -"expected, feel free to ask over at the `Community `_." +"Message setting within Zammad's admin settings without ticket reload " +"application setting." msgstr "" -#: ../system/variables/article.rst:6 +#: ../system/maintenance.rst:0 msgid "" -"Below you can find all available ticket article-based variables within " -"Zammad. These can be called via Triggers for example. If you're unsure if " -"Zammad does support variables at the point you're at, you can try to type " -"``::`` to check." +"Screenshot showing the send message settings without ticket\n" +"reload application set" msgstr "" -#: ../system/variables/article.rst:9 ../system/variables/config.rst:9 -#: ../system/variables/ticket.rst:9 +#: ../system/maintenance.rst:61 ../system/maintenance.rst:85 msgid "" -"The below list gives you an example what kind of data you can expect, it's " -"not intended to explain the data itself." +"The modal all other active sessions will see upon pressing *Send to clients*." msgstr "" -#: ../system/variables/article.rst:11 -msgid "Article Variables" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing modal caused by maintenance's message\n" +"without reload application ticket" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "name" +#: ../system/maintenance.rst:72 +msgid "Example with reload application" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "variable" +#: ../system/maintenance.rst:76 +msgid "" +"Message setting within Zammad's admin settings with ticket reload " +"application setting." msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "example" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing the send message settings with ticket\n" +"reload application set" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Web" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing modal caused by maintenance's message\n" +"with reload application ticket" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.web}``" +#: ../system/monitoring.rst:2 +msgid "Monitoring" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``https://zammad.com`` or empty if not set in user object" +#: ../system/monitoring.rst:4 +msgid "" +"This function is only available in self hosted instances. If you use Zammad " +"in our cloud, we are monitoring the system on our own and take steps to fix " +"potential problems directly." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > VIP" +#: ../system/monitoring.rst:11 +msgid "" +"On the monitoring page, you can see the current health state of Zammad under " +"\"*Current Status*\" at the bottom. This can be useful if you want to have a " +"look if everything is up and running. As an example, you could have a look " +"in the monitoring when you assume that some emails aren't processed from " +"Zammad." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.vip}``" +#: ../system/monitoring.rst:17 +msgid "**Can't receive an email and the monitoring response is \"healthy\"?**" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -msgid "``true`` or ``false``" +#: ../system/monitoring.rst:19 +msgid "" +"Zammad will just inform you about unprocessable emails. This is not the case " +"for oversized emails. You can adjust the maximum email size in :doc:`../" +"channels/email/settings`." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Phone" +#: ../system/monitoring.rst:24 +msgid "Monitoring API" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.phone}``" +#: ../system/monitoring.rst:26 +msgid "" +"Beside the indication in the monitoring page, you can also use an external " +"monitoring tool to monitor Zammad's health. To request the health of Zammad, " +"you need to provide the API key (token) to the external monitoring tool. You " +"can copy the token from the \"*Current Token*\" field as well as the whole " +"API endpoint of your system (\"*Health Check*\" field), in which the API " +"token is already included." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``+4930123456789`` or empty if not set in user object" +#: ../system/monitoring.rst:37 +msgid "Screenshot showing Current Token and Health Check" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Note" +#: ../system/monitoring.rst:37 +msgid "Screenshot showing Token and Health Check" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.note}``" +#: ../system/monitoring.rst:39 +msgid "" +"In addition to that, you can reset the auto-generated token to make sure " +"that already configured monitoring systems won't work anymore. So, please " +"use this \"*Reset*\" button only if you know what you do!" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Some note about user`` or empty if not set in user object" +#: ../system/monitoring.rst:44 +msgid "Example Output" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Mobile" +#: ../system/monitoring.rst:0 +msgid "No issues found" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.mobile}``" +#: ../system/monitoring.rst:48 ../system/monitoring.rst:60 +msgid "**Indicator in Zammad**:" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Login" +#: ../system/monitoring.rst:0 +msgid "Screenshot showing monitoring with no issues" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.login}``" +#: ../system/monitoring.rst:54 ../system/monitoring.rst:66 +msgid "**API response**::" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -#: ../system/variables/ticket.rst:1 -msgid "``jdoe``" +#: ../system/monitoring.rst:0 +msgid "Issues were found" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Lastname" +#: ../system/monitoring.rst:0 +msgid "Screenshot showing monitoring with issues" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.lastname}``" +#: ../system/objects.rst:2 +msgid "Objects" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -#: ../system/variables/ticket.rst:1 -msgid "``Doe`` or empty if not set" +#: ../system/objects.rst:4 +msgid "" +"In Zammad you can add your own fields to tickets, users, organizations and " +"even groups (these are called \"objects\"). This can be useful if you need " +"to add further information to a ticket or any other object in Zammad and the " +"information doesn't fit in any existing field." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Firstname" +#: ../system/objects.rst:11 +msgid "" +"Try to avoid deleting attributes (and disable them instead) as Zammad might " +"run into unexpected conditions if they are referenced somewhere." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.firstname}``" +#: ../system/objects.rst:16 +msgid "" +"Here's an overview of object attributes. On the upper right you can add new " +"attributes. By default, there will be no custom fields - standard attributes " +"will be grayed out, you can't delete or change those. You can edit custom " +"attributes (they are displayed in black font and have a trash bin on the " +"right side) just by clicking on them." msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "``Joe`` or empty if not set" +#: ../system/objects.rst:24 +msgid "" +"Attributes you add to Zammad, no matter if they have default values or not, " +"will not update existing information. This means a new ticket field " +"technically will be empty unless you populate it." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Fax" +#: ../system/objects.rst:28 +msgid "" +"Especially in ticket scope this also means that newly added attributes will " +"be indicated as \"changed\" to agents that view the ticket. This may " +"interfere with Zammad's tabs behavior." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.fax}``" +#: ../system/objects.rst:40 +msgid "Ordering Attributes" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Email" +#: ../system/objects.rst:42 +msgid "" +"Since Zammad introduced :doc:`/system/core-workflows` the need to have a " +"custom positioning for attributes has become more important than ever." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.email}``" +#: ../system/objects.rst:45 +msgid "" +"To adjust the position of such an attribute, simply click on the attribute " +"entry in question, scroll down and adjust the position number. Please note " +"that you cannot change the positioning of default attributes." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``jdoe@example.com``" +#: ../system/objects.rst:49 +msgid "" +"In case two attributes have the same position value, Zammad will sort " +"alphabetically by name automatically." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Department" +#: ../system/objects.rst:None +msgid "" +"Screenshot showing custom attribute entries ordered in between default ones" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.department}``" +#: ../system/objects.rst:56 +msgid "Updating Database After Adding or Editing Attributes" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Sales`` or empty if not set in user object" +#: ../system/objects.rst:58 +msgid "" +"When adding or changing attributes, Zammad will not apply the changes " +"instantly, but instead shows you the changed attributes first. If you're " +"ready to go, just click on \"Update database\" to apply the changes to " +"Zammad. If you made a mistake or just want to discard your changes, click " +"\"Discard changes\"." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Address" +#: ../system/objects.rst:64 +msgid "" +"After applying the changes with \"Update Database\", a restart of Zammad is " +"**mandatory**. If you don't perform it, you may experience unexpected " +"behavior or even errors. You may want to do this kind of configuration " +"during maintenance windows." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.address}``" +#: ../system/objects.rst:72 +msgid "" +"Changes on objects require you to update the database to apply these changes." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Some street 1, 12345 Berlin`` or empty if not set in user object" +#: ../system/objects.rst:75 +msgid "**🤓 Service restarts can be automated**" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated" +#: ../system/objects.rst:0 +msgid "Hosted environments automatically restart for you." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_at}``" +#: ../system/objects.rst:0 +msgid "" +"If you're using a self-hosted installation you can use :docs:`environment " +"variables `" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``2019-10-08 15:24:47 UTC``" +#: ../system/objects.rst:82 +msgid "System Attributes" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Type > Name" +#: ../system/objects.rst:84 +msgid "" +"Zammad comes with pre-configured attributes. Some of them can't be edited " +"via UI (or at all). This is required for proper operation of Zammad and not " +"a bug." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.type.name}``" +#: ../system/objects.rst:90 +msgid "Ticket State" msgstr "" -#: ../system/variables/article.rst:1 +#: ../system/objects.rst:92 msgid "" -"``email`` (`list of article types `_)" +"If the pre-configured states aren't enough for you or you want to change " +"them, you can do so by clicking on the cogwheel icon in the state row in the " +"ticket tab. But you should be careful when changing pre-configured states. " +"This can lead to unwanted behavior in some cases." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > To" +#: ../system/objects.rst:None +msgid "Screenshot showing highlighted ticket state attribute" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.to}``" +#: ../system/objects.rst:122 +msgid "Handling of states" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``helpdesk@example.com``" +#: ../system/objects.rst:102 +msgid "" +"In the state configuration screen, you can add new states, disable states or " +"change states." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > TicketID" +#: ../system/objects.rst:0 +msgid "Screenshot showing table of default ticket states" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.ticket_id}``" +#: ../system/objects.rst:110 +msgid "" +"To add a new state, click on the \"New Ticket State\" button in the top " +"right corner. To change an existing state, simply click on the affected " +"state. This opens an edit dialog." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``1`` (not ticket number)" +#: ../system/objects.rst:114 +msgid "" +"You can also clone a state or set them to \"Default for new tickets\" or " +"\"Default for follow-ups\" by clicking on the ⁝ action button and select the " +"desired function." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Subject" +#: ../system/objects.rst:118 +msgid "" +"*Default for new tickets* means that this state is used for every newly " +"created ticket." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.subject}``" +#: ../system/objects.rst:121 +msgid "" +"*Default for follow-ups* means that this state is used if the ticket is re-" +"opened after it was closed." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``My amazing subject``" +#: ../system/objects.rst:171 +msgid "Ticket state in detail" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Sender > Name" +#: ../system/objects.rst:125 +msgid "" +"Below you can find a description for each field and option. Please head over " +"to the :ref:`example ` to see the edit dialog." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.sender.name}``" +#: ../system/objects.rst:129 +msgid "" +"This is the name of the state and what you and your agents are seeing when " +"choosing a state somewhere (e.g. in tickets, trigger configuration)." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Customer``, ``Agent`` or ``System``" +#: ../system/objects.rst:137 +msgid "" +"There are different state types you can choose from. By default, Zammad " +"comes with one state per state type." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Visibility" +#: ../system/objects.rst:140 +msgid "" +"**new**: for states for tickets that are new and it hasn't been worked on " +"them" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.internal}``" +#: ../system/objects.rst:142 +msgid "" +"**open**: for states for tickets that are in progress and agents are working " +"on them" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``false`` or ``true`` (false if not internal)" +#: ../system/objects.rst:144 +msgid "**merged**: for states for tickets that are merged with other tickets" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > From" +#: ../system/objects.rst:145 +msgid "" +"**pending reminder**: for states for tickets that are in progress and you " +"want to set a reminder. (default example: *pending reminder*)" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.from}``" +#: ../system/objects.rst:147 +msgid "" +"**pending action**: for states for tickets that are waiting for a specified " +"time and then change their state (default example: *pending close*)" msgstr "" -#: ../system/variables/article.rst:1 +#: ../system/objects.rst:150 msgid "" -"``Joe Doe `` may differ, depends on ``FROM`` of send mail" +"**closed**: for states for tickets that are finished and do not need to be " +"processed further" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Web" +#: ../system/objects.rst:153 +msgid "" +"⚠️ Choosing the correct state type is important! If you are in doubt, have a " +"look on the default states and their types!" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.web}``" +#: ../system/objects.rst:158 +msgid "Ignore escalation" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > VIP" +#: ../system/objects.rst:157 +msgid "" +"Here you can define whether tickets of this state will count to escalation " +"time or not." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.vip}``" +#: ../system/objects.rst:161 +msgid "" +"You can create a note for the state to inform other admins about the state. " +"This has no effect on tickets." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Phone" +#: ../system/objects.rst:165 +msgid "Set the state to *active* or *inactive*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.phone}``" +#: ../system/objects.rst:167 +msgid "" +"it is technically possible to set all states to inactive. To keep Zammad " +"working in such a case, the inactive flag of one of the states is ignored." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Note" +#: ../system/objects.rst:194 +msgid "Ticket state example" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.note}``" +#: ../system/objects.rst:174 +msgid "" +"Let's assume we want to create a new state which indicates that the ticket " +"has to wait for a response of a third party (e.g. service contractor or " +"manufacturer) and we want to to be able to set a reminder." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Mobile" +#: ../system/objects.rst:178 +msgid "" +"First we give the new state a proper name. In this example we call it " +"\"waiting for manufacturer\"." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.mobile}``" +#: ../system/objects.rst:181 +msgid "" +"As state type we choose \"pending reminder\". This indicates that the ticket " +"is still open and we can set a reminder. This reminder can be useful if our " +"manufacturer sometimes isn't responding or we want to remind him to give us " +"an answer." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Login" +#: ../system/objects.rst:186 +msgid "" +"We choose \"no\" for \"ignore escalation\" because we want to escalate the " +"tickets even if we are waiting on the manufacturer's feedback." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.login}``" +#: ../system/objects.rst:189 +msgid "The **result** in the creation dialog will look like this:" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Lastname" +#: ../system/objects.rst:0 +msgid "Screenshot showing ticket state creation dialog with example" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.lastname}``" +#: ../system/objects.rst:199 +msgid "Ticket Priority" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Firstname" +#: ../system/objects.rst:201 +msgid "" +"If the pre-configured priorities aren't enough for you or you want to change " +"them, you can do so by clicking on the cogwheel icon in the priority row in " +"the ticket tab:" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.firstname}``" +#: ../system/objects.rst:None +msgid "Screenshot showing highlighted ticket priority attribute" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Fax" +#: ../system/objects.rst:226 +msgid "Handling of priorities" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.fax}``" +#: ../system/objects.rst:210 +msgid "" +"In the priority configuration screen, you can add new priorities, disable " +"priorities or change priorities." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Email" +#: ../system/objects.rst:0 +msgid "Screenshot showing table of default ticket priorities" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.email}``" +#: ../system/objects.rst:218 +msgid "" +"To add a new priority, click on the \"New Priority\" button in the top right " +"corner. To change an existing priority, simply click on the affected " +"priority. This opens an edit dialog." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Department" +#: ../system/objects.rst:222 +msgid "" +"You can also clone a priority or set them to \"Default for new tickets\" by " +"clicking on the ⁝ action button and select the desired function." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.department}``" +#: ../system/objects.rst:225 +msgid "" +"*Default for new tickets* means that this priority is used for every newly " +"created ticket." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Address" +#: ../system/objects.rst:248 +msgid "Priorities in detail" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.address}``" +#: ../system/objects.rst:229 +msgid "Below you can find a description for each field and option." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created" +#: ../system/objects.rst:232 +msgid "" +"This is the name of the priority and what you and your agents are seeing " +"when choosing a priority somewhere (e.g. in tickets, trigger configuration)." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_at}``" +#: ../system/objects.rst:242 +msgid "Highlight color" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Cc" +#: ../system/objects.rst:237 +msgid "" +"Switch between *Low priority* (light blue), *High priority* (red) and - " +"(default). This affects the displayed color for ticket titles in overviews." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.cc}``" +#: ../system/objects.rst:241 +msgid "The color options are currently limited to the mentioned options." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``jdoe@example.com, company@example.com``" +#: ../system/objects.rst:245 +msgid "" +"You can create a note for the priority to inform other admins about the " +"priority. This has no effect on tickets." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Text" +#: ../system/objects.rst:249 +msgid "Set the priority to *active* or *inactive*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.body}``" +#: ../system/objects/external-data-source-example.rst:2 +msgid "External Data Source" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Test`` without formatting (plain)" +#: ../system/objects/external-data-source-example.rst:4 +msgid "" +"We assume you already had a look on :doc:`types` where you can find a " +"description of the individual fields." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article Text as HTML (not referenced)" +#: ../system/objects/external-data-source-example.rst:7 +msgid "" +"To reproduce this example, choose a category you want to add a custom field, " +"click on *New Attribute* and select *External data source field* under " +"*Format*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.body_as_html}``" +#: ../system/objects/external-data-source-example.rst:11 +msgid "" +"Our example story is to fetch data from an external product database. We " +"want to add our products to the tickets so that the products can be searched " +"and chosen from a list and also create a link to the product website." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Test`` with formatting" +#: ../system/objects/external-data-source-example.rst:16 +msgid "Base configuration" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "Ticket > Article#" +#: ../system/objects/external-data-source-example.rst:None +msgid "Initial steps to configure external data source object type" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "``#{ticket.article_count}``" +#: ../system/objects/external-data-source-example.rst:25 +msgid "Name: *product*" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``1`` number of ticket articles" +#: ../system/objects/external-data-source-example.rst:26 +msgid "Display: *Product*" msgstr "" -#: ../system/variables/config.rst:2 -msgid "Config" +#: ../system/objects/external-data-source-example.rst:29 +msgid "External data source configuration" msgstr "" -#: ../system/variables/config.rst:6 +#: ../system/objects/external-data-source-example.rst:31 msgid "" -"Below you'll find config related variables. These hold useful configuration " -"information that you can use within e.g. triggers to show necessary " -"information to your customer." +"First, enter the search URL making sure it contains ``#{search.term}`` as a " +"parameter:" msgstr "" -#: ../system/variables/config.rst:11 -msgid "Config Variables" +#: ../system/objects/external-data-source-example.rst:34 +msgid "**Example:** ``https://dummyjson.com/products/search?q=#{search.term}``" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Fully Qualified Domain Name" +#: ../system/objects/external-data-source-example.rst:36 +msgid "" +"After that, head down to the preview section and enter a search input for " +"the external data source." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.fqdn}``" +#: ../system/objects/external-data-source-example.rst:39 +msgid "**Example:** ``mac``" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``zammad.example.com``" +#: ../system/objects/external-data-source-example.rst:41 +msgid "Then you can find a preview of the response data below:" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Ticket Hook" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of JSON response based on search term" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.ticket_hook}``" +#: ../system/objects/external-data-source-example.rst:48 +msgid "" +"We recommend using the preview to have a look on the structure. There is a " +"top-level element called ``products``. One level below, you can find the " +"attributes ``id`` and ``title``." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``Ticket#``" +#: ../system/objects/external-data-source-example.rst:52 +msgid "**Search result response based on search from example:**" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > HTTP type" +#: ../system/objects/external-data-source-example.rst:119 +msgid "" +"To tell the remote system that the desired data is located below the " +"``products`` level, you have to put it in the field *Search result list key*." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.http_type}``" +#: ../system/objects/external-data-source-example.rst:122 +msgid "" +"After inserting ``products`` in the mentioned field, you get an extended " +"preview. You can find an additional box *Search result list* with a JSON " +"structure. This is the same response as before but stripped from the upper " +"``products`` element by the external data source." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``https`` or ``http``" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of JSON response search result list" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > SystemID" +#: ../system/objects/external-data-source-example.rst:132 +msgid "" +"Now you need to provide the keys for the search result values and labels. As " +"already mentioned, we are looking for the ``id`` and the ``title`` of our " +"products. If you haven't already, it is now a good time to look at the " +"preview of the *Search result list*." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.system_id}``" +#: ../system/objects/external-data-source-example.rst:197 +msgid "" +"After locating our two keys, we insert them in *search result value key* " +"(``id``) and in *Search result label key* (``title``)." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``31`` (value between 1 and 99)" +#: ../system/objects/external-data-source-example.rst:200 +msgid "" +"Basically, we configured the external data source already and we can see a " +"table in the preview section:" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Organization" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of product table based on search term" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.organization}``" +#: ../system/objects/external-data-source-example.rst:208 +msgid "" +"According to our example story, now just the *Link template* is missing." msgstr "" -#: ../system/variables/config.rst:1 +#: ../system/objects/external-data-source-example.rst:210 msgid "" -"``Zammad GmbH`` value set in `Branding `_" +"Please note that this is an optional feature. If you don't want to use such " +"links, of course you don't have to configure it." msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Product Name" +#: ../system/objects/external-data-source-example.rst:213 +msgid "" +"We can add now an address where additional product information can be found." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.product_name}``" +#: ../system/objects/external-data-source-example.rst:215 +msgid "Example: ``https://your_domain.com/q=#{ticket.product}``" msgstr "" -#: ../system/variables/config.rst:1 -msgid "" -"``Helpdesk`` value set in `Branding `_" +#: ../system/objects/external-data-source-example.rst:217 +msgid "In the example, the parameter means:" +msgstr "" + +#: ../system/objects/external-data-source-example.rst:219 +msgid "``#{}``: \"Frame\" for the insertion of information" msgstr "" -#: ../system/variables/current-user.rst:2 -msgid "Current User" +#: ../system/objects/external-data-source-example.rst:220 +msgid "``ticket``: object level, where you create your custom object" msgstr "" -#: ../system/variables/current-user.rst:6 -msgid "" -"Current user variables always return values of the current user that caused " -"e.g. a trigger to run." +#: ../system/objects/external-data-source-example.rst:221 +msgid "``product``: name of the (custom) object" msgstr "" -#: ../system/variables/current-user.rst:8 +#: ../system/objects/external-data-source-example.rst:223 msgid "" -"Due to the above fact, these variables are often not (yet) set or available " -"for usage." +"After configuring your *Link template*, there will be another column in the " +"preview. Hovering on the icons in the *Link* column will show you where it " +"forwards you." msgstr "" -#: ../system/variables/current-user.rst:10 +#: ../system/objects/external-data-source-example.rst:232 msgid "" -"In situations where e.g. schedulers or triggers run, this most likely is " -"nothing you want to use." -msgstr "" - -#: ../system/variables/current-user.rst:13 -msgid "Current User Variables" +"In our example, one of the links looks like: https://your_domain.com/q=6, " +"where the 6 is the product id." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Web" +#: ../system/objects/external-data-source-example.rst:235 +msgid "You can find more information regarding the URL in :doc:`types`." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.web}``" +#: ../system/objects/includes/adding-values-hint.include.rst:3 +msgid "" +"Adding values can be tricky for first timers, don't forget to press \"➕ " +"Add\" after typing your values. Otherwise you may loose a value." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``https://zammad.org`` or empty if not set" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:1 +#: ../system/objects/includes/reposition-values.include.rst:1 +msgid "**↕️ This field type allows the positioning of its values ↔️**" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > VIP" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:3 +msgid "" +"In order to re-arrange the field values, first edit the field. Then you can " +"use ☰ to drag the values in question to the correct position. If you want to " +"change the layer depth, double click on ☰. With it you can cycle through the " +"available layers." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.vip}``" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:8 +msgid "When you're ready, submit your changes to save the object attribute." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``false`` or ``true``" +#: :0 ../system/objects/types.rst:0 +msgid "" +"Screencast showing how to re-position values on tree select like\n" +"fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Web" +#: ../system/objects/includes/reposition-values.include.rst:3 +msgid "" +"In order to re-arrange the field values, edit the field and scroll below the " +"values. Make sure to tick the option \"Use custom option sort\"." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.web}``" +#: ../system/objects/includes/reposition-values.include.rst:8 +msgid "" +"If you do not tick this field, all manual positioning you did above will be " +"lost upon saving! ☠️" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > VIP" +#: ../system/objects/includes/reposition-values.include.rst:11 +msgid "" +"Now use ☰ to drag the values in question to the correct position. When " +"you're ready, submit your changes to save the object attribute." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.vip}``" +#: :0 ../system/objects/types.rst:0 +msgid "Screencast showing how to re-position values" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Phone" +#: ../system/objects/includes/url-template-hint.include.rst:3 +msgid "" +"This field allows using :ref:`URL fields (Link Templates) `." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.phone}``" +#: ../system/objects/permissions.rst:2 +msgid "Attribute Permissions" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``004930123456789`` or empty if not set" +#: ../system/objects/permissions.rst:7 +msgid "" +"In the object attributes configuration you can define if a field is shown " +"and if the input in the field is mandatory, separated by different screens " +"and for different :doc:`roles/permissions `." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Note" +#: ../system/objects/permissions.rst:17 +msgid "Screenshot shows object attribute permission table" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.note}``" +#: ../system/objects/permissions.rst:17 +msgid "" +"Some of the possible permissions and screen options for a user object " +"attribute." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Some note to this user`` or empty if not set" +#: ../system/objects/permissions.rst:19 +msgid "" +"Based on the object context (ticket, agent, organization, user), the " +"selectable roles (to be precise: the required permissions) and screens " +"differ. Be aware that these settings aren't affecting data creation via " +"other channels than the UI." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Mobile" +#: ../system/objects/permissions.rst:24 +msgid "" +"If you want to have further customization possibilities, you should have a " +"look at the :doc:`core workflows `." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.mobile}``" +#: ../system/objects/permissions.rst:28 +msgid "Screens" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``0049176123456789`` or empty if not set" +#: ../system/objects/permissions.rst:30 +msgid "" +"In the table below you can find an overview about the different permissions " +"and the available screens Zammad distinguishes between." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Login" +#: ../system/objects/permissions.rst:37 +msgid "Screen" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.login}``" +#: ../system/objects/permissions.rst:38 +msgid "Available for" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Lastname" +#: ../system/objects/permissions.rst:40 +msgid "create" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.lastname}``" +#: ../system/objects/permissions.rst:41 ../system/objects/permissions.rst:52 +#: ../system/objects/permissions.rst:59 ../system/objects/permissions.rst:73 +msgid "admin.user" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Firstname" +#: ../system/objects/permissions.rst:42 ../system/objects/permissions.rst:53 +#: ../system/objects/permissions.rst:60 +msgid "admin.organization" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.firstname}``" +#: ../system/objects/permissions.rst:43 ../system/objects/permissions.rst:54 +#: ../system/objects/permissions.rst:61 +msgid "admin.group" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``John`` or empty if not set" +#: ../system/objects/permissions.rst:44 +msgid "Creation dialog for not yet existing data" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Fax" +#: ../system/objects/permissions.rst:45 +msgid "create_middle" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.fax}``" +#: ../system/objects/permissions.rst:46 ../system/objects/permissions.rst:50 +#: ../system/objects/permissions.rst:57 ../system/objects/permissions.rst:66 +#: ../system/objects/permissions.rst:70 +msgid "ticket.customer" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``004930123464789`` or empty if not set" +#: ../system/objects/permissions.rst:47 ../system/objects/permissions.rst:51 +#: ../system/objects/permissions.rst:58 ../system/objects/permissions.rst:69 +msgid "ticket.agent" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Email" +#: ../system/objects/permissions.rst:48 +msgid "Ticket create dialog (middle section)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.email}``" +#: ../system/objects/permissions.rst:49 +msgid "edit" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``jdoe@customer.tld``" +#: ../system/objects/permissions.rst:55 +msgid "Editing dialog for already existing data" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Department" +#: ../system/objects/permissions.rst:56 +msgid "view" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.department}``" +#: ../system/objects/permissions.rst:62 +msgid "View-only dialog for already existing data" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Sales`` or empty if not set" +#: ../system/objects/permissions.rst:64 +msgid "(e.g. user or organization from search)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Avatar" +#: ../system/objects/permissions.rst:65 +msgid "signup" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.avatar(60,60)}``" +#: ../system/objects/permissions.rst:67 +msgid "Sign-up screen for new customers" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "avatar picture with width and height in pixel (e.g. 60,60)" +#: ../system/objects/permissions.rst:68 +msgid "invite_customer" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Address" +#: ../system/objects/permissions.rst:71 +msgid "" +"Customer invitation screen (from :doc:`First Steps ` area)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.address}``" +#: ../system/objects/permissions.rst:72 +msgid "invite_agent" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Some street 1, 12345 Berlin`` or empty if not set" +#: ../system/objects/permissions.rst:74 +msgid "" +"Agent invitation screen (from :doc:`First Steps ` area)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated at" +#: ../system/objects/permissions.rst:78 +msgid "Screen Options" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_at}``" +#: ../system/objects/permissions.rst:80 +msgid "" +"For the different screens you can select \"show\" and \"required\" options." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC``" +#: ../system/objects/permissions.rst:82 +msgid "**shown:** Show (check) or hide (uncheck) a field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Phone" +#: ../system/objects/permissions.rst:83 +msgid "" +"**required:** Set a field to mandatory (check). Forces users (via UI and " +"API) to populate the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.phone}``" +#: ../system/objects/types.rst:7 +msgid "Example external data source" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Shared organization" +#: ../system/objects/types.rst:2 +msgid "Attribute types" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.shared}``" +#: ../system/objects/types.rst:4 +msgid "" +"When adding a new object attribute, you can choose between the following " +"attribute types." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Note" +#: ../system/objects/types.rst:14 +msgid "" +"You cannot change the attribute format / type as soon as it is applied. If " +"you no longer need an object attribute, consider disabling it instead of " +"removing." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.note}``" +#: ../system/objects/types.rst:18 +msgid "**What about the translation of my attributes?**" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``A note to the organization of the user`` or empty if not set" +#: ../system/objects/types.rst:20 +msgid "" +"For some attribute types you can decide if they should be translatable or " +"not. To be precise, it works only for the selectable fields because the " +"possible choices are known and limited. For the following attribute types, " +"you can set the translatable flag:" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Name" +#: ../system/objects/types.rst:25 +msgid "*Boolean field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.name}``" +#: ../system/objects/types.rst:26 +msgid "*Single selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``Zammad GmbH``" +#: ../system/objects/types.rst:27 +msgid "*Multiple selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Domain based assignment" +#: ../system/objects/types.rst:28 +msgid "*Single tree selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.domain_assignment}``" +#: ../system/objects/types.rst:29 +msgid "*Multiple tree selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Domain" +#: ../system/objects/types.rst:31 +msgid "" +"For these types, you can find an additional field *Translate field contents*:" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.domain}``" +#: ../system/objects/types.rst:0 +msgid "Screenshot showing translatable attribute types" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``zammad.com`` or empty if not set" +#: ../system/objects/types.rst:38 +msgid "Screenshot with example of translatable attribute type" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > VIP" +#: ../system/objects/types.rst:45 +msgid "Boolean field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.vip}``" +#: ../system/objects/types.rst:41 +msgid "" +"Provides a drop-down field with display values for ``true`` and ``false``. " +"Setting a default is mandatory." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Note" +#: ../system/objects/types.rst:0 +msgid "Available settings for Boolean fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.note}``" +#: ../system/objects/types.rst:55 +msgid "Date field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Mobile" +#: ../system/objects/types.rst:48 +msgid "Provides a date picker field and does not allow default values." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.mobile}``" +#: ../system/objects/types.rst:52 +msgid "Default time diff (hours)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Login" +#: ../system/objects/types.rst:51 +msgid "" +"This setting helps the user by highlighting the day from now plus the " +"provided value. It *does not* pre-fill the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.login}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Date fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Lastname" +#: ../system/objects/types.rst:73 +msgid "Date & time field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.lastname}``" +#: ../system/objects/types.rst:58 +msgid "Provides a date and time picker – does not allow default values" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Firstname" +#: ../system/objects/types.rst:62 +msgid "Allow future" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.firstname}``" +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the future." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Fax" +#: ../system/objects/types.rst:66 +msgid "Allow past" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.fax}``" +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the past." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Email" +#: ../system/objects/types.rst:70 +msgid "Default time diff (minutes)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.email}``" +#: ../system/objects/types.rst:69 +msgid "" +"This setting helps the user by highlighting the day from now plus the " +"provided value. It does not pre-fill the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Department" +#: ../system/objects/types.rst:0 +msgid "Available settings for Date & time fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.department}``" +#: ../system/objects/types.rst:86 +msgid "Integer field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Web" +#: ../system/objects/types.rst:76 +msgid "" +"Provides an input field that allows integer usage only. You may define a " +"default value. You cannot enforce comma separation." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.web}``" +#: ../system/objects/types.rst:80 +msgid "Minimal" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > VIP" +#: ../system/objects/types.rst:80 +msgid "The minimal value the field accepts." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.vip}``" +#: ../system/objects/types.rst:83 +msgid "Maximal" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Phone" +#: ../system/objects/types.rst:83 +msgid "The maximum value the field accepts." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.phone}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Integer fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Note" +#: ../system/objects/types.rst:99 +msgid "Multiple selection field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.note}``" +#: ../system/objects/types.rst:89 +msgid "" +"Provides a selection field that allows the selection of one or more out of " +"several. This field does allow setting a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Mobile" +#: ../system/objects/types.rst:0 +msgid "Available settings for Multiple selection fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.mobile}``" +#: ../system/objects/types.rst:112 +msgid "Single selection field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Login" +#: ../system/objects/types.rst:102 +msgid "" +"Provides a drop-down field that allows selection of one value out of " +"several. This field does allow setting a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.login}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Single selection fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Lastname" +#: ../system/objects/types.rst:142 +msgid "Textarea field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.lastname}``" +#: ../system/objects/types.rst:115 +msgid "" +"Provides a text area input field (multiple lines) and thus allows e.g. new " +"lines. You can set a default field value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Firstname" +#: ../system/objects/types.rst:120 +msgid "" +"Please note that this field *does not* support text formatting or HTML " +"content (rich text)." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.firstname}``" +#: ../system/objects/types.rst:123 +msgid "**🥵 This field can consume a lot of visual space**" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Fax" +#: ../system/objects/types.rst:125 +msgid "" +"Depending on where you use this field type, it may use a lot of visual space " +"if you provide a lot of text. This may be an issue to work with." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.fax}``" +#: ../system/objects/types.rst:130 +msgid "Default" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Email" +#: ../system/objects/types.rst:129 +msgid "" +"The here provided text will be shown within the text area field or new data " +"sets." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.email}``" +#: ../system/objects/types.rst:134 ../system/objects/types.rst:160 +msgid "Maxlength" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Department" +#: ../system/objects/types.rst:0 ../system/objects/types.rst:160 +msgid "You can pick the maximum length of the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.department}``" +#: ../system/objects/types.rst:0 +msgid "The default length of this object is ``500``." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Avatar" +#: ../system/objects/types.rst:139 +msgid "Rows" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.avatar(60,60)}``" +#: ../system/objects/types.rst:0 +msgid "" +"Change the number of rows to dislay so that you can use only the space you " +"really need." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Address" +#: ../system/objects/types.rst:0 +msgid "The default number of rows is ``4``." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.address}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Textarea fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created at" +#: ../system/objects/types.rst:165 +msgid "Text field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_at}``" +#: ../system/objects/types.rst:145 +msgid "Provides a text field (one line) and allows choosing a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Avatar" +#: ../system/objects/types.rst:148 +msgid "" +"Defines the type of the input field. This allows e.g. your browser to ensure " +"that you provide the specific type." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.avatar(60,60)}``" +#: ../system/objects/types.rst:152 +msgid "Currently available:" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Address" +#: ../system/objects/types.rst:155 +msgid "Phone" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.address}``" +#: ../system/objects/types.rst:156 +msgid "Text" msgstr "" -#: ../system/variables/ticket.rst:6 -msgid "" -"Below you can find all available ticket-based variables within Zammad. These " -"can be called via Triggers for example. If you're unsure if Zammad does " -"support variables at the point you're at, you can try to type ``::`` to " -"check." +#: ../system/objects/types.rst:157 +msgid "Url *(URL fields disable link-template availability)*" msgstr "" -#: ../system/variables/ticket.rst:12 -msgid "Ticket Variables" +#: ../system/objects/types.rst:0 +msgid "Available settings for Text fields" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Web" +#: ../system/objects/types.rst:174 +msgid "Single tree selection field" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.web}``" +#: ../system/objects/types.rst:168 +msgid "" +"Provides a select-like field with up to 6 layers of options. Does not allow " +"setting a default value." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > VIP" +#: ../system/objects/types.rst:0 +msgid "Available settings for Tree Select fields" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.vip}``" +#: ../system/objects/types.rst:183 +msgid "Multiple tree selection field" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Phone" +#: ../system/objects/types.rst:177 +msgid "" +"Provides a select-like field with up to 6 layers of options allowing the " +"selection of multiple values. Does not allow setting a default value." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.phone}``" +#: ../system/objects/types.rst:302 +msgid "External Data Source field" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Note" +#: ../system/objects/types.rst:186 +msgid "" +"Provides a searchable field which fetches data from an external system. This " +"can be useful if you have data outside of Zammad and don't want to maintain " +"both data sources." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.note}``" +#: ../system/objects/types.rst:190 +msgid "The feature works as follows:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Mobile" +#: ../system/objects/types.rst:192 +msgid "" +"Zammad sends a query with a search string (free text from agent or based on " +"a variable) in a pre-defined format (\"Search URL\") to an external system." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.mobile}``" +#: ../system/objects/types.rst:195 +msgid "" +"This external system searches for matches and provides a response as a JSON " +"structure to Zammad." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Login" +#: ../system/objects/types.rst:197 +msgid "" +"Zammad just looks for the defined list and value keys, reads the content and " +"displays the value to the user. There is no search on Zammad side." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.login}``" +#: ../system/objects/types.rst:201 +msgid "" +"The usage of a PostgreSQL database for Zammad is required. In any other " +"case, Zammad will hide the external data source type and you are not able to " +"use it. If you want to use this feature, consider to :docs:`migrate your " +"database `." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Lastname" +#: ../system/objects/types.rst:205 +msgid "Currently, only ``GET`` is supported as request method." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.lastname}``" +#: ../system/objects/types.rst:206 +msgid "" +"The data structure must be in JSON format and provide the objects in an " +"array." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Firstname" +#: ../system/objects/types.rst:208 +msgid "" +"The endpoint for the external data source has to support search. On Zammad " +"side, there is no search/logic implemented; however, you can define the " +"output key and value based on the result(s) from the response (which " +"provides already filtered content based on the search)." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.firstname}``" +#: ../system/objects/types.rst:212 +msgid "" +"If you receive more results as expected, your external data source search " +"may not work properly or the structure of the URL is not correct. You should " +"get in touch with a responsible person from the external system." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Fax" +#: ../system/objects/types.rst:217 +msgid "" +"Please have a look :doc:`at our example `, where you can find a possible configuration for a public " +"dummy endpoint." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.fax}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for external data source fields" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Email" +#: ../system/objects/types.rst:242 +msgid "Search URL" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.email}``" +#: ../system/objects/types.rst:227 +msgid "" +"Set your endpoint where Zammad fetches the data. Please make sure to include " +"a valid search :doc:`variable ` as an URL parameter. " +"Example for a free text search at user input: ``#{search.term}``" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Department" +#: ../system/objects/types.rst:232 +msgid "" +"If in doubt, ask the responsible person for the external data source how " +"they expect the structure of the URL." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.department}``" +#: ../system/objects/types.rst:236 +msgid "" +"Depending on your search variable, the preview might work or not. The reason " +"is that the context might not be available and it is no bug." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Avatar" +#: ../system/objects/types.rst:239 +msgid "" +"Please also make sure to use a variable which is available in your object " +"context. For example you won't be able to search for a ticket in a user " +"object context." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.avatar(60,60)}``" +#: ../system/objects/types.rst:252 +msgid "SSL Verification" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Address" +#: ../system/objects/types.rst:245 +msgid "Here you can switch the SSL verification to no." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.address}``" +#: ../system/objects/types.rst:249 +msgid "" +"If your external data source system is using self signed certificates, " +"please have a look :doc:`here ` for " +"further information about how to handle them in Zammad, so you can keep the " +"SSL verification activated." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated at" +#: ../system/objects/types.rst:258 +msgid "HTTP Authentication" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_at}``" +#: ../system/objects/types.rst:255 +msgid "" +"If your external data source requires an authentication, you can set it " +"here. You can leave it empty or choose between *Basic Authentication* or " +"*Authentication Token* (selecting one of the two methods leads to additional " +"fields where you can enter your credentials/token)." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Title" +#: ../system/objects/types.rst:265 +msgid "Search result list key" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.title}``" +#: ../system/objects/types.rst:261 +msgid "" +"Defines the level in the JSON structure which provides the list with search " +"results. You can leave it empty, if the data is already provided as an " +"array. If you have to go deeper in the structure, you can provide a path " +"with ``.`` as separators, e.g. ``key.subkey.sub-sub-key``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "" -"``My amazing Subject`` (normally subject, can be edited within Interface and " -"thus differ)" +#: ../system/objects/types.rst:271 +msgid "Search result value key" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Accounted Time" +#: ../system/objects/types.rst:268 +msgid "" +"Defines the attribute in the structure in which your external data source " +"provides the *value* for your data. An example would be a product *number*. " +"If you have to go deeper in the structure, you can provide a path with ``.`` " +"as separators, e.g. ``key.subkey.sub-sub-key``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.time_unit}``" +#: ../system/objects/types.rst:277 +msgid "Search result label key" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``1``, ``2.75`` or empty response" +#: ../system/objects/types.rst:274 +msgid "" +"Defines the attribute in the structure in which your external data source " +"provides the *label* for your data. An example would be a product *name*. If " +"you have to go deeper in the structure, you can provide a path with ``.`` as " +"separators, e.g. ``key.subkey.sub-sub-key``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Tags" +#: ../system/objects/types.rst:280 +msgid "" +"In the preview area, you can find the following items (depending on your " +"configuration above):" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.tags}``" +#: ../system/objects/types.rst:283 +msgid "" +"**Error/hint message** (only if configuration is not complete): Zammad tells " +"you, if there is a problem and what you should change in your configuration." msgstr "" -#: ../system/variables/ticket.rst:1 +#: ../system/objects/types.rst:286 msgid "" -"Currently not available, see `Issue 2769 `_" +"**Search field**: search for an existing attribute in the data source to get " +"a preview. This is required for the fields below to show up." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > State > Name" +#: ../system/objects/types.rst:288 +msgid "" +"**Search result response** (only if configuration is not complete): here you " +"can find a syntax highlighted JSON preview of the response, based on the " +"search term you entered." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.state.name}``" +#: ../system/objects/types.rst:291 +msgid "" +"**Search result list** (only if *search result list key* is properly set): " +"output of the structure under the configured *search result list key*." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``new``, ``open``, ..." +#: ../system/objects/types.rst:294 +msgid "" +"**Preview table** (when fully configured): Zammad shows you a table which " +"includes the found items based on the search string (value, label and " +"optional link). You can use this preview if you don't have the complete data " +"structure of the external system in mind." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Priority > Name" +#: ../system/objects/types.rst:299 +msgid "" +"An example of a configured external data source field from agent perspective:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.priority.name}``" +#: ../system/objects/types.rst:0 +msgid "Screencast showing the search for a product in a ticket" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2 normal``" +#: ../system/objects/types.rst:307 +msgid "URL fields (Link-Template)" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Pending till" +#: ../system/objects/types.rst:311 +msgid "" +"This function is restricted to Text, Select and External data source types " +"only." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.pending_time}``" +#: ../system/objects/types.rst:314 +msgid "" +"Link-Templates are an amazing way to dynamically generate URLs. They allow " +"you to integrate other systems better without having to manually copy data " +"from Zammad if possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not set" +#: ../system/objects/types.rst:320 +msgid "" +"Another great way of communicating with another system may be Zammad's :doc:" +"`Webhooks `." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Web" +#: ../system/objects/types.rst:323 +msgid "" +"After filling a link-template enabled field, an URL icon will appear on its " +"right. Clicking on the icon opens a new tab." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.web}``" +#: ../system/objects/types.rst:328 +msgid "" +"Even though Zammad displays the link template within object edit and create " +"screens, the function is optional. It's only active if you populate the " +"field." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``https://zammad.com`` or empty if not set" +#: ../system/objects/types.rst:333 +msgid "" +"What's the difference between URL and text fields with link template...?!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > VIP" +#: ../system/objects/types.rst:335 +msgid "" +"Both fields have different use cases. Use ``text`` type text fields when " +"ever you have a *static* url that requires dynamic parameters. If you " +"require a drag & drop like field that you can put in any URL, use ``URL`` " +"type text fields." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.vip}``" +#: ../system/objects/types.rst:340 +msgid "" +"The difference is easier to spot when comparing the fields directly, below " +"screencast shows the result - the dynamic approach uses existing values in " +"the moment of updating to built the URL - e.g. ``https://google.com/search?" +"q=cookies`` - while the URL approach uses the actual URL of the field - e.g. " +"``https://zammad.com``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Phone" +#: ../system/objects/types.rst:None +msgid "" +"Screencast showing the differents in between URL and text type fields with " +"actual values" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.phone}``" +#: ../system/objects/types.rst:352 +msgid "How does this work...?!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Note" +#: ../system/objects/types.rst:354 +msgid "" +"As an example, let's say you have an attribute called ``amazing_attribute`` " +"and you want to open a google search directly with the input from that field." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.note}``" +#: ../system/objects/types.rst:357 +msgid "" +"Providing the link-template field below allows you to do so: ``https://www." +"google.com/search?q=#{ticket.amazing_attribute}``" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Mobile" +#: ../system/objects/types.rst:362 +msgid "" +"You can use any :doc:`Zammad variable ` as long as it's " +"available in the moment you need it." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.mobile}``" +#: ../system/objects/types.rst:365 +msgid "" +"As a result, you are redirected to Google with a search for the value of the " +"attribute, if you click on the button in the ticket (as you can see in the " +"screencast above)." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Login" +#: ../system/packages.rst:2 +msgid "Packages" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.login}``" +#: ../system/packages.rst:4 +msgid "That's the package management-area." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``agent``" +#: ../system/packages.rst:6 +msgid "Individual add-ons for Zammad can be installed and managed here." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Lastname" +#: ../system/sessions.rst:2 +msgid "Sessions" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.lastname}``" +#: ../system/sessions.rst:4 +msgid "" +"Sessions management allows reviewing currently known user sessions and " +"allows to end these. The session timeout is affected by :ref:" +"`security_session_timeout` configurations from security settings." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Mustermann`` or empty if not set" +#: ../system/sessions.rst:None +msgid "Screenshot showing Zammad's session management" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Firstname" +#: ../system/sessions.rst:13 +msgid "Zammad will provide the following information:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.firstname}``" +#: ../system/sessions.rst:16 +msgid "" +"The user account this session entry belongs to. It can be normal if a user " +"has several sessions in the list. This can be due to changed browser " +"information or if you use e.g. single sign on methods where the user does " +"not use the log off button." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Max`` or empty if not set" +#: ../system/sessions.rst:22 +msgid "Browser" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Fax" +#: ../system/sessions.rst:22 +msgid "The browser agent communicated to Zammad." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.fax}``" +#: ../system/sessions.rst:40 +msgid "Location" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Email" +#: ../system/sessions.rst:25 +msgid "" +"The anticipated location based on the users IP address. Depending on the IP " +"address the result shown may differ. This option depends on :doc:`/settings/" +"system/services`." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.email}``" +#: ../system/sessions.rst:29 +msgid "The following information can be shown:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``agent@company.tld`` or empty if not set" +#: ../system/sessions.rst:33 +msgid "IP address" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Department" +#: ../system/sessions.rst:32 +msgid "" +"Either if you set *Geo IP services* to inactive or you're using internal IP " +"address which do not provide location information." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.department}``" +#: ../system/sessions.rst:40 +msgid "Country (or Country + City)" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Support`` or empty if not set" +#: ../system/sessions.rst:36 +msgid "" +"If *Geo IP services* is enabled only. Depends on how detailed the available " +"IP address information are." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Avatar" +#: ../system/sessions.rst:39 +msgid "" +"Be aware that results can be inaccurate - this technically is not an error." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.avatar(60,60)}``" +#: ../system/sessions.rst:43 +msgid "Age" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Address" +#: ../system/sessions.rst:43 +msgid "Provides the time when the session initially has been created." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.address}``" +#: ../system/sessions.rst:50 +msgid "Update" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Shared organization" +#: ../system/sessions.rst:46 +msgid "" +"Provides the time the user used this session to open Zammad. This timestamp " +"is only updated if the user e.g. reloads, not during normal work on tickets." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.shared}``" +#: ../system/sessions.rst:50 +msgid "This timestamp is being used for the session timeout." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Note" +#: ../system/sessions.rst:53 +msgid "" +"Use the delete button to remove a single session on behalf of your user." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.note}``" +#: ../system/subscription.rst:2 +msgid "Subscription (SaaS)" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Name" +#: ../system/subscription.rst:4 +msgid "" +"The subscription settings page allows you to configure your instances " +"package and number of agents required." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.name}``" +#: ../system/subscription.rst:9 +msgid "" +"This setting section is only available for Hosted setups. If you're looking " +"for on premise support contracts, please see the `Zammad pricing page " +"`_." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Zammad GmbH`` or empty if not set" +#: ../system/subscription.rst:14 ../system/subscription.rst:34 +msgid "Plan" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Domain based assignment" +#: ../system/subscription.rst:16 +msgid "" +"Here you can set up everything affecting your instance subscription " +"functions like number of agents and package." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.domain_assignment}``" +#: ../system/subscription.rst:19 +msgid "" +"On top of the page you can find a subscription summary. You'll find the " +"number of used and available (booked) agent seats there. By using the *see " +"more* link you can also expand an agent list to see the currently configured " +"active agents. This list *does not* count accounts with admin permissions " +"only." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Domain" +#: ../system/subscription.rst:None +msgid "" +"Within subscription you can always see how many agents are still\n" +"available to add and who uses the seats." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.domain}``" +#: ../system/subscription.rst:29 +msgid "" +"Learn more on how to manage your agents in general :doc:`here `." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``domain.tld`` or empty if not set" +#: ../system/subscription.rst:36 +msgid "" +"This section gives you an overview of the available plans and their " +"functions / limits. If you require a more detailed table, check our " +"`detailed pricing table `_ for more." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > VIP" +#: ../system/subscription.rst:40 +msgid "" +"Your selection in this step will decide on the base agent price and e.g. " +"agent limits that might apply in the summary step." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.vip}``" +#: ../system/subscription.rst:43 +msgid "" +"The green *Selected* button will also tell you what plan you're currently in." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Number" +#: ../system/subscription.rst:47 +msgid "" +"Trial instances are running at Professional with 3 agents. The plan cannot " +"be changed during the trial for technical reasons, if you require more " +"agents for testing, please contact `our sales team `_ with a reason for the raise request." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.number}``" +#: ../system/subscription.rst:None +msgid "" +"Screenshot showing three available packages for a hosted Zammad\n" +"instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``31001``, ``201910731001``, ..." +#: ../system/subscription.rst:57 +msgid "" +"At the bottom of this block you can find a summary where you can adjust the " +"settings of the previous selected plan." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > ID" +#: ../system/subscription.rst:62 +msgid "" +"Note that upgrading (more agents, higher package) is always possible, " +"however, downgrading will only happen when your billing period renews." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.id}``" +#: ../system/subscription.rst:66 +msgid "" +"Upgrading resets your billing period and existing credit will be deducted " +"from the new total." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``17``, ``5281``, ..." +#: ../system/subscription.rst:75 +msgid "Billing cycle" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact (customer)" +#: ../system/subscription.rst:70 +msgid "" +"You can choose between either monthly or yearly billing. The price per agent " +"will be cheaper if you decide for yearly billing." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_customer_at}``" +#: ../system/subscription.rst:73 +msgid "" +"If you're still trying out things and are unsure of the right package for " +"your instance, you may want to choose monthly first and then upgrade to " +"yearly when you're sure." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "" -"``2019-10-07 16:25:00 UTC`` or empty if not applicable yet (Please note " -"`Ticket last contact behavior Settings `_ for this)" +#: ../system/subscription.rst:83 +msgid "Plan: (Starter|Professional|Plus) - Agents" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact" +#: ../system/subscription.rst:78 +msgid "Choose the number of agents you require for your instance." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_at}``" +#: ../system/subscription.rst:80 +msgid "" +"Keep in mind that some packages may have agent limits. Depending on the " +"previous chosen package, you won't be able to exceed specific agent numbers. " +"Also note that setting less agents than currently configured is not possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact (agent)" +#: ../system/subscription.rst:86 +msgid "Total" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_agent_at}``" +#: ../system/subscription.rst:86 +msgid "This will be the net total you're going to be billed." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable yet" +#: ../system/subscription.rst:88 +msgid "" +"By using the *Update subscription* button, the instance package will be " +"adjusted immediately. If you didn't provide a payment method yet, Zammad " +"will request you to provide one at this point." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Note" +#: ../system/subscription.rst:94 +msgid "" +"In case you're still within the trial period, this means that the trial will " +"be over immediately!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.note}``" +#: ../system/subscription.rst:97 +msgid "Down- or upgrading during the trial period *is not* possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Note about this group``" +#: ../system/subscription.rst:None +msgid "Screenshot showing payment options and a pricing summary" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Name" +#: ../system/subscription.rst:103 +msgid "Billing Information" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.name}``" +#: ../system/subscription.rst:105 +msgid "" +"You can control all billing relevant information like invoices, billing " +"address and the option to cancel your subscription." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Sales``" +#: ../system/subscription.rst:108 +msgid "" +"All adjusted billing information below only affect future invoices. If your " +"invoice was issued wrong, please contact `our sales team `_." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Follow-up possible" +#: ../system/subscription.rst:114 +msgid "Billing address" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.follow_up_possible}``" +#: ../system/subscription.rst:113 +msgid "" +"Provide your company address here, make sure to include the companies name " +"in case required. This address will be referenced on your invoice." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``no`` or ``yes``" +#: ../system/subscription.rst:118 +msgid "VAT ID" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Assign Follow-Ups" +#: ../system/subscription.rst:117 +msgid "" +"Provide your VAT ID here. If applicable your invoice will not contain German " +"VAT. Please make sure to pay the VAT in your country as required." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.follow_up_assignment}``" +#: ../system/subscription.rst:127 +msgid "Billing Email Address" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Assignment Timeout" +#: ../system/subscription.rst:121 +msgid "" +"Usually the instance owner (the person that registered the instance) will " +"receive all emails including the invoices. In case you have your own billing " +"department, you can provide their email address here." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.assignment_timeout}``" +#: ../system/subscription.rst:125 +msgid "" +"All billing relevant information will then be sent to this email address." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``20`` or empty if not configured" +#: ../system/subscription.rst:127 +msgid "Invoices are sent as attachment (PDF) to this email address." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > First response" +#: ../system/subscription.rst:129 +msgid "" +"Don't forget to press the *Update billing information* button after you " +"changed above settings." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.first_response_at}``" +#: ../system/subscription.rst:None +msgid "" +"Screenshot showing options for billing information within the\n" +"subscription menu" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Escalation at" +#: ../system/subscription.rst:137 +msgid "Payment Method" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.escalation_at}``" +#: ../system/subscription.rst:139 +msgid "You can pay via credit card or SEPA mandate." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable" +#: ../system/subscription.rst:144 +msgid "Credit card" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Web" +#: ../system/subscription.rst:142 +msgid "" +"Simply follow the dialogue by clicking *authorize credit card* and confirm -" +"if required by your bank- your consent to Zammad using your card for the " +"payments." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.web}``" +#: ../system/subscription.rst:148 +msgid "SEPA Direct Debit" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > VIP" +#: ../system/subscription.rst:147 +msgid "" +"Provide the requested information of the bank account holder and update if " +"you're ready. You'll then receive an email with the SEPA mandate." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.vip}``" +#: ../system/subscription.rst:150 +msgid "" +"Technically there's also the possibility to pay via invoice, however - this " +"method only applies to a fairly low number of instances. Please contact `our " +"sales team `_ for more information." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Phone" +#: ../system/subscription.rst:156 +msgid "Cancel Subscription" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.phone}``" +#: ../system/subscription.rst:158 +msgid "" +"Do you want to cancel your subscription? In case you no longer want to use " +"Zammad's SaaS, you can cancel your subscription by using the red *Yes, " +"please cancel my subscription* button." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Note" +#: ../system/subscription.rst:162 +msgid "" +"To cancel the description, enter the FQDN of your Zammad instance and " +"provide a reason for your cancellation." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.note}``" +#: ../system/subscription.rst:165 +msgid "" +"Your subscription will end the day after your trial or billing period ends." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Mobile" +#: ../system/subscription.rst:None +msgid "Screenshot showing subscription cancellation dialog" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.mobile}``" +#: ../system/subscription.rst:174 +msgid "" +"We will remind you about your cancelled subscription several times up front. " +"After the subscription ended all instance data will be removed. A restore " +"*is not* possible after that point!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Login" +#: ../system/subscription.rst:178 +msgid "**😖 Cancelled by accident?**" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.login}``" +#: ../system/subscription.rst:180 +msgid "" +"You can always undo the cancellation via the *Yes, undo the cancellation of " +"my subscription* button up to the last subscription day!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Lastname" +#: ../system/subscription.rst:0 +msgid "" +"Screenshot showing a red button to cancel the subscription\n" +"cancellation" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.lastname}``" +#: ../system/subscription.rst:189 +msgid "Payment History" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Firstname" +#: ../system/subscription.rst:191 +msgid "" +"The payment history will display a history of all paid invoices. At this " +"point you can also download these in case you need them again." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.firstname}``" +#: ../system/subscription.rst:196 +msgid "" +"You will only find *paid* invoices here. Invoices that are to be billed are " +"not available before the payment is completed." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Fax" +#: ../system/subscription.rst:201 +msgid "Date" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.fax}``" +#: ../system/subscription.rst:201 +msgid "Date of the invoice creation." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Email" +#: ../system/subscription.rst:204 +msgid "Amount" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.email}``" +#: ../system/subscription.rst:204 +msgid "Invoice total including VAT if applicable." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Department" +#: ../system/subscription.rst:207 +msgid "" +"Contains contract period (monthly or yearly) and hosted plan for the " +"subscription period in question." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.department}``" +#: ../system/subscription.rst:218 +msgid "Payment method / Service period" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Avatar" +#: ../system/subscription.rst:211 +msgid "" +"Used bank account or credit card as well as the subscription period the " +"invoice is about." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.avatar(60,60)}``" +#: ../system/subscription.rst:216 +msgid "" +"It might happen that the invoice date and subscription period differ. This " +"is nothing to worry about, the subscription periods will be accounted later " +"on." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Address" +#: ../system/subscription.rst:222 +msgid "Receipt" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.address}``" +#: ../system/subscription.rst:221 +msgid "" +"Use the arrow to download the invoice in question. You can download all " +"available invoices any time you need to here!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Web" +#: ../system/subscription.rst:None +msgid "Screenshot showing payment history of a hosted instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.web}``" +#: ../system/subscription.rst:229 +msgid "FAQ" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > VIP" +#: ../system/subscription.rst:233 +msgid "I set up a trial account but am missing functions to test" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.vip}``" +#: ../system/subscription.rst:232 +msgid "" +"The trial instance is running within the professional package allowing up to " +"three agents." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Phone" +#: ../system/subscription.rst:236 +msgid "Can I change package within the trial?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.phone}``" +#: ../system/subscription.rst:236 +msgid "No. As soon as the package is changed the subscription begins." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Note" +#: ../system/subscription.rst:241 +msgid "What happens to my trial instance after the trial period ended?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.note}``" +#: ../system/subscription.rst:239 +msgid "" +"Your instance will automatically be canceled for you. Please see *What " +"happens to my instance after it has been canceled?* for more." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Mobile" +#: ../system/subscription.rst:254 +msgid "What happens to my instance after it has been canceled?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.mobile}``" +#: ../system/subscription.rst:244 +msgid "That depends slightly on your instance state:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Login" +#: ../system/subscription.rst:250 +msgid "Trial instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.login}``" +#: ../system/subscription.rst:247 +msgid "" +"If you're still on trial, we will ice your instance and remind you once " +"again about your instance. We then will wait some days and remove your " +"instance from our system. This is the last time we will inform you by Email." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Lastname" +#: ../system/subscription.rst:254 +msgid "Paid instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.lastname}``" +#: ../system/subscription.rst:253 +msgid "" +"If you're a paying customer and canceled your subscription, the instance " +"removal will take place the day after your last subscription day." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Firstname" +#: ../system/subscription.rst:256 +msgid "Can removed instances be restored?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.firstname}``" +#: ../system/subscription.rst:257 +msgid "No. Once your instance has been removed, a restoration is not possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Fax" +#: ../system/system-report.rst:2 +msgid "System Report" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.fax}``" +#: ../system/system-report.rst:4 +msgid "" +"In this place you can't configure Zammad. Instead you can obtain a system " +"report about Zammad and its configuration." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Email" +#: ../system/system-report.rst:7 +msgid "" +"See the description in Zammad for an explanation. You can even find a " +"preview of the included data below the **Download** button." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.email}``" +#: ../system/system-report.rst:10 +msgid "" +"Zammad never sends this automatically to anyone. It is a manual process only " +"to provide better support based on your configuration." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Department" +#: ../system/translations.rst:2 +msgid "Translations" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.department}``" +#: ../system/translations.rst:4 +msgid "" +"Translations of Zammad are processed centrally in our `Weblate instance " +"`_. This allows non-developers to review " +"and update translation texts of the language they actually speak." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Avatar" +#: ../system/translations.rst:9 +msgid "" +"Your language is in an incomplete translation state or has typos? Please " +"consider helping us in sorting this out! All you need is either a GitHub " +"account or to register directly in our instance." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.avatar(60,60)}``" +#: ../system/translations.rst:13 +msgid "" +"Did you know? This is also where the documentation translations are handled. " +"🤓" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Address" +#: ../system/translations.rst:15 +msgid "" +"Have a look in our :docs:`contribution section ` in the system documentation to get started!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.address}``" +#: ../system/translations.rst:20 +msgid "Local Translations" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created at" +#: ../system/translations.rst:22 +msgid "" +"Apart from these system translations, there's still local translations you " +"can manage. This is relevant if you added custom objects that require " +"translations or even custom states and priorities." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_at}``" +#: ../system/translations.rst:None +msgid "Translation management screen within the admin menu" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "2019-10-07 16:25:00 UTC" +#: ../system/translations.rst:31 +msgid "Updating Translations" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Closing time" +#: ../system/translations.rst:33 +msgid "" +"Because of how Zammad ships translations, the only way to update the system " +"translations is to update your Zammad installation. The benefit of this is " +"that you no longer need internet access during a Zammad upgrade as the " +"package has everything it requires already." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.close_at}``" +#: ../system/translations.rst:39 +msgid "Translation of Custom Objects" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "2019-10-07 17:25:00 UTC" +#: ../system/translations.rst:41 +msgid "" +"No problem at all! You can customize any translation locally, even if it is " +"not initially provided by the system." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``3``, any number of articles existing in the ticket right now" +#: ../system/translations.rst:44 +msgid "" +"Translation is supported for a broad number of features, including but not " +"limited to custom:" msgstr "" -#: ../system/version.rst:2 -msgid "Version" +#: ../system/translations.rst:47 +msgid "Object Attributes" msgstr "" -#: ../system/version.rst:4 -msgid "Shows which version is currently being used on your Zammad-instance." +#: ../system/translations.rst:48 +msgid "Ticket Macros" msgstr "" -#: ../manage/roles/admin-permissions.rst:53 -msgid "``admin.checklist``" +#: ../system/translations.rst:49 +msgid "Ticket Overviews" msgstr "" -#: ../manage/roles/admin-permissions.rst:54 -msgid ":doc:`Manage > Checklist `" +#: ../system/translations.rst:50 +msgid "Ticket Priorities" msgstr "" -#: ../manage/roles/admin-permissions.rst:83 -msgid "``admin.channel_whatsapp``" +#: ../system/translations.rst:51 +msgid "Ticket States" msgstr "" -#: ../manage/roles/admin-permissions.rst:84 -msgid ":doc:`Channels > Whatsapp `" +#: ../system/translations.rst:54 +msgid "Customizing Translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:124 -msgid "``admin.public_links``" +#: ../system/translations.rst:56 +msgid "" +"Within the translation screen, simply click on the **New Translation** " +"button." msgstr "" -#: ../manage/roles/admin-permissions.rst:125 -msgid ":doc:`Manage > Public Links `" +#: ../system/translations.rst:None +msgid "New translation dialog" msgstr "" -#: ../manage/roles/admin-permissions.rst:151 -msgid "``admin.system_report``" +#: ../system/translations.rst:62 +msgid "" +"In the dialog you can immediately enter the exact translation source (if you " +"know it) and your custom translation text for it and click **Submit**." msgstr "" -#: ../manage/roles/admin-permissions.rst:152 -msgid ":doc:`System > System Report `" +#: ../system/translations.rst:65 +msgid "" +"Alternatively, try to search for translation suggestions in the list below. " +"Selecting an item from the list will pre-fill the translation source for you " +"and then you can just enter your custom translation." msgstr "" -#: ../manage/roles/admin-permissions.rst:166 -msgid "``admin.ticket_auto_assignment``" +#: ../system/translations.rst:69 +msgid "" +"The target language will always default to your current language selection. " +"If you need to translate for a different language, simply change the " +"selection before submitting." msgstr "" -#: ../manage/roles/admin-permissions.rst:167 -msgid ":ref:`Settings > Ticket > Auto Assignment `" +#: ../system/translations.rst:73 +msgid "" +"All your custom translations will show up in the overview table when added. " +"And they will even persist across Zammad updates!" msgstr "" -#: ../manage/roles/admin-permissions.rst:169 -msgid "``admin.ticket_duplicate_detection``" +#: ../system/translations.rst:76 +msgid "" +"Make sure to reload your browser if a translated string is not displayed." msgstr "" -#: ../manage/roles/admin-permissions.rst:170 -msgid ":ref:`Settings > Ticket > Duplicate Detection `" +#: ../system/translations.rst:80 +msgid "Reverting to Original Translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:172 -msgid "``admin.ticket_priority``" +#: ../system/translations.rst:82 +msgid "" +"If you want to revert a custom translation to original text, simply use the " +"appropriate action within the row of the overview table." msgstr "" -#: ../manage/roles/admin-permissions.rst:173 -msgid ":ref:`System > Objects >Ticket Priority `" +#: ../system/translations.rst:85 +msgid "" +"Depending on the type of the translation source, the action has a slightly " +"different name:" msgstr "" -#: ../manage/roles/admin-permissions.rst:175 -msgid "``admin.ticket_state``" +#: ../system/translations.rst:88 +msgid "**Reset** for customized system translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:176 -msgid ":ref:`System > Objects >Ticket State `" +#: ../system/translations.rst:89 +msgid "**Remove** for customized local translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:193 -msgid "``admin.webhook``" +#: ../system/translations.rst:91 +msgid "" +"In both cases, the action will remove the customized translation after a " +"confirmation." msgstr "" -#: ../manage/roles/admin-permissions.rst:194 -msgid ":doc:`Manage > Webhook `" +#: ../system/translations.rst:None +msgid "Screenshot showing the location of the Remove action" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:43 -msgid "``user_preferences.appearance``" +#: ../system/translations.rst:99 +msgid "Inline Translations" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:44 -msgid "Appearance configuration" +#: ../system/translations.rst:101 +msgid "" +"If you prefer a more hands-on approach, you can activate the inline or on-" +"screen translation feature by pressing ``ctrl`` + ``alt`` + ``t`` at any " +"time and on any screen." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:0 -msgid "Users can switch between dark, light and" +#: ../system/translations.rst:105 +msgid "" +"All customizable translation texts will be highlighted for you on the " +"screen. Just click into the highlighted area and update the text in place." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:0 -msgid "automatic mode." +#: ../system/translations.rst:None +msgid "Inline translation mode activated for the Overview screen" msgstr "" -#: ../system/system-report.rst:2 -msgid "System Report" +#: ../system/translations.rst:112 +msgid "" +"When finished editing, simply press ``ctrl`` + ``alt`` + ``t`` again to " +"deactivate." msgstr "" -#: ../system/system-report.rst:4 +#: ../system/translations.rst:117 msgid "" -"In this place you can't configure Zammad. Instead you can obtain a system " -"report about Zammad and its configuration." +"Even though it's available on any screen, the inline translation feature " +"requires admin permissions. It works only for the current language " +"selection. If you need to translate a different language, first change the " +"language in your :user-docs:`profile settings `." msgstr "" -#: ../system/system-report.rst:7 -msgid "" -"See the description in Zammad for an explanation. You can even find a " -"preview of the included data below the **Download** button." +#: ../system/version.rst:2 +msgid "Version" msgstr "" -#: ../system/system-report.rst:10 -msgid "" -"Zammad never sends this automatically to anyone. It is a manual process only " -"to provide better support based on your configuration." +#: ../system/version.rst:4 +msgid "Shows which version is currently being used on your Zammad-instance." msgstr "" diff --git a/locale/de/LC_MESSAGES/admin-docs.po b/locale/de/LC_MESSAGES/admin-docs.po index 1c802cd6..b30a417b 100644 --- a/locale/de/LC_MESSAGES/admin-docs.po +++ b/locale/de/LC_MESSAGES/admin-docs.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Zammad\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-11-06 10:31+0100\n" +"POT-Creation-Date: 2024-11-12 16:31+0100\n" "PO-Revision-Date: 2024-11-07 08:45+0000\n" "Last-Translator: Ralf Schmid \n" "Language-Team: German Checklist `" +msgstr "doc:`Verwalten> Checklisten `" + #: ../manage/roles/admin-permissions.rst:56 msgid "``admin.channel_email``" msgstr "``admin.channel_email``" -#: ../manage/roles/admin-permissions.rst:54 #: ../manage/roles/admin-permissions.rst:57 msgid ":doc:`Channels > Email `" msgstr ":doc:`Kanäle > Email `" -#: ../manage/roles/admin-permissions.rst:56 #: ../manage/roles/admin-permissions.rst:59 msgid "``admin.channel_facebook``" msgstr "``admin.channel_facebook``" -#: ../manage/roles/admin-permissions.rst:57 #: ../manage/roles/admin-permissions.rst:60 msgid ":doc:`Channels > Facebook `" msgstr ":doc:`Kanäle > Facebook `" -#: ../manage/roles/admin-permissions.rst:58 #: ../manage/roles/admin-permissions.rst:61 msgid "" "Accessing Facebook tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" "Zugriff auf Facebook Tickets für Agenten: :doc:`/manage/groups/access-levels`" -#: ../manage/roles/admin-permissions.rst:59 #: ../manage/roles/admin-permissions.rst:62 msgid "``admin.channel_formular``" msgstr "``admin.channel_formular``" -#: ../manage/roles/admin-permissions.rst:60 #: ../manage/roles/admin-permissions.rst:63 msgid ":doc:`Channels > Form `" msgstr ":doc:`Kanäle > Formulare `" -#: ../manage/roles/admin-permissions.rst:62 #: ../manage/roles/admin-permissions.rst:65 msgid "``admin.channel_google``" msgstr "``admin.channel_google``" -#: ../manage/roles/admin-permissions.rst:63 #: ../manage/roles/admin-permissions.rst:66 msgid ":doc:`Channels > Google `" msgstr ":doc:`Kanäle > Google `" -#: ../manage/roles/admin-permissions.rst:65 #: ../manage/roles/admin-permissions.rst:68 msgid "``admin.channel_microsoft365``" msgstr "``admin.channel_microsoft365``" -#: ../manage/roles/admin-permissions.rst:66 #: ../manage/roles/admin-permissions.rst:69 msgid ":doc:`Channels > Microsoft 365 `" msgstr ":doc:`Kanäle > Microsoft 365 `" -#: ../manage/roles/admin-permissions.rst:68 #: ../manage/roles/admin-permissions.rst:71 msgid "``admin.channel_sms``" msgstr "``admin.channel_sms``" -#: ../manage/roles/admin-permissions.rst:69 #: ../manage/roles/admin-permissions.rst:72 msgid ":doc:`Channels > SMS `" msgstr ":doc:`Kanäle > SMS `" -#: ../manage/roles/admin-permissions.rst:71 #: ../manage/roles/admin-permissions.rst:74 msgid "``admin.channel_telegram``" msgstr "``admin.channel_telegram``" -#: ../manage/roles/admin-permissions.rst:72 #: ../manage/roles/admin-permissions.rst:75 msgid ":doc:`Channels > Telegram `" msgstr ":doc:`Kanäle > Telegram `" -#: ../manage/roles/admin-permissions.rst:73 #: ../manage/roles/admin-permissions.rst:76 msgid "" "Accessing Telegram tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" "Zugriff auf Telegram-Tickets für Agenten: :doc:`/manage/groups/access-levels`" -#: ../manage/roles/admin-permissions.rst:74 #: ../manage/roles/admin-permissions.rst:77 msgid "``admin.channel_twitter``" msgstr "``admin.channel_twitter``" -#: ../manage/roles/admin-permissions.rst:75 #: ../manage/roles/admin-permissions.rst:78 msgid ":doc:`Channels > Twitter `" msgstr ":doc:`Kanäle > Twitter `" -#: ../manage/roles/admin-permissions.rst:76 #: ../manage/roles/admin-permissions.rst:79 msgid "" "Accessing Twitter/X tickets for agents: :doc:`/manage/groups/access-levels`" @@ -10690,37 +10690,38 @@ msgstr "" "Zugriff auf Twitter/X-Tickets für Agenten: :doc:`/manage/groups/access-" "levels`" -#: ../manage/roles/admin-permissions.rst:77 #: ../manage/roles/admin-permissions.rst:80 msgid "``admin.channel_web``" msgstr "``admin.channel_web``" -#: ../manage/roles/admin-permissions.rst:78 #: ../manage/roles/admin-permissions.rst:81 msgid ":doc:`Channels > Web `" msgstr ":doc:`Kanäle > Web `" -#: ../manage/roles/admin-permissions.rst:80 +#: ../manage/roles/admin-permissions.rst:83 +msgid "``admin.channel_whatsapp``" +msgstr "``admin.channel_whatsapp``" + +#: ../manage/roles/admin-permissions.rst:84 +msgid ":doc:`Channels > Whatsapp `" +msgstr "doc:`Kanäle > Whatsapp `" + #: ../manage/roles/admin-permissions.rst:86 msgid "``admin.core_workflows``" msgstr "``admin.core_workflows``" -#: ../manage/roles/admin-permissions.rst:81 #: ../manage/roles/admin-permissions.rst:87 msgid ":doc:`System > Core Workflows `" msgstr ":doc:`System > Core-Workflows `" -#: ../manage/roles/admin-permissions.rst:83 #: ../manage/roles/admin-permissions.rst:89 msgid "``admin.data_privacy``" msgstr "``admin.data_privacy``" -#: ../manage/roles/admin-permissions.rst:84 #: ../manage/roles/admin-permissions.rst:90 msgid ":doc:`System > Data Privacy `" msgstr ":doc:`System > Datenschutz `" -#: ../manage/roles/admin-permissions.rst:85 #: ../manage/roles/admin-permissions.rst:91 msgid "" "🔥 Be careful, it allows users to permanently delete data on the system." @@ -10728,32 +10729,26 @@ msgstr "" "🔥 Seien Sie vorsichtig, es erlaubt Benutzern, Daten auf dem System " "dauerhaft zu löschen." -#: ../manage/roles/admin-permissions.rst:86 #: ../manage/roles/admin-permissions.rst:92 msgid "``admin.group``" msgstr "``admin.group``" -#: ../manage/roles/admin-permissions.rst:87 #: ../manage/roles/admin-permissions.rst:93 msgid ":doc:`Manage > Groups `" msgstr ":doc:`Verwalten > Gruppen `" -#: ../manage/roles/admin-permissions.rst:89 #: ../manage/roles/admin-permissions.rst:95 msgid "``admin.integration``" msgstr "``admin.integration``" -#: ../manage/roles/admin-permissions.rst:90 #: ../manage/roles/admin-permissions.rst:96 msgid ":doc:`System > Integrations `" msgstr ":doc:`System > Integrationen `" -#: ../manage/roles/admin-permissions.rst:92 #: ../manage/roles/admin-permissions.rst:98 msgid "``admin.knowledge_base``" msgstr "``admin.knowledge_base``" -#: ../manage/roles/admin-permissions.rst:93 #: ../manage/roles/admin-permissions.rst:99 msgid ":doc:`Manage > Knowledge Base `" msgstr ":doc:`Verwalten > Knowledge Base `" @@ -10777,59 +10772,48 @@ msgstr "" "Stellen Sie sicher, dass Sie die :user-docs:`Sichtbarkeit ` in der Antwort überprüfen." -#: ../manage/roles/admin-permissions.rst:98 #: ../manage/roles/admin-permissions.rst:104 msgid "``admin.macro``" msgstr "``admin.macro``" -#: ../manage/roles/admin-permissions.rst:99 #: ../manage/roles/admin-permissions.rst:105 msgid ":doc:`Manage > Macros `" msgstr ":doc:`Verwalten > Makros`" -#: ../manage/roles/admin-permissions.rst:100 #: ../manage/roles/admin-permissions.rst:106 msgid "In some cases, macros may also require ``admin.tag``" msgstr "" "In einigen Fällen erfordern Makros möglicherweise auch die Berechtigung " "``admin.tag``" -#: ../manage/roles/admin-permissions.rst:101 #: ../manage/roles/admin-permissions.rst:107 msgid "``admin.maintenance``" msgstr "``admin.maintenance``" -#: ../manage/roles/admin-permissions.rst:102 #: ../manage/roles/admin-permissions.rst:108 msgid ":doc:`System > Maintenance `" msgstr ":doc:`System > Wartung `" -#: ../manage/roles/admin-permissions.rst:104 #: ../manage/roles/admin-permissions.rst:110 msgid "``admin.monitoring``" msgstr "``admin.monitoring``" -#: ../manage/roles/admin-permissions.rst:105 #: ../manage/roles/admin-permissions.rst:111 msgid ":doc:`System > Monitoring `" msgstr ":doc:`System > Monitoring `" -#: ../manage/roles/admin-permissions.rst:107 #: ../manage/roles/admin-permissions.rst:113 msgid "``admin.object``" msgstr "``admin.object``" -#: ../manage/roles/admin-permissions.rst:108 #: ../manage/roles/admin-permissions.rst:114 msgid ":doc:`System > Objects `" msgstr ":doc:`System > Objekte `" -#: ../manage/roles/admin-permissions.rst:110 #: ../manage/roles/admin-permissions.rst:116 msgid "``admin.organization``" msgstr "``admin.organization``" -#: ../manage/roles/admin-permissions.rst:111 #: ../manage/roles/admin-permissions.rst:117 msgid ":doc:`Manage > Organizations `" msgstr ":doc:`Verwalten > Organisationen `" @@ -10848,204 +10832,214 @@ msgstr "" "Sie können sogar den Namen, die Domain und die Notizen einer Organisation " "bearbeiten!" -#: ../manage/roles/admin-permissions.rst:115 #: ../manage/roles/admin-permissions.rst:121 msgid "``admin.overview``" msgstr "``admin.overview``" -#: ../manage/roles/admin-permissions.rst:116 #: ../manage/roles/admin-permissions.rst:122 msgid ":doc:`Manage > Overviews`" msgstr ":doc:`Verwalten > Übersichten `" -#: ../manage/roles/admin-permissions.rst:118 +#: ../manage/roles/admin-permissions.rst:124 +msgid "``admin.public_links``" +msgstr "``admin.public_links``" + +#: ../manage/roles/admin-permissions.rst:125 +msgid ":doc:`Manage > Public Links `" +msgstr "doc:`Verwalten > Öffentliche Links `" + #: ../manage/roles/admin-permissions.rst:127 msgid "``admin.package``" msgstr "``admin.package``" -#: ../manage/roles/admin-permissions.rst:119 #: ../manage/roles/admin-permissions.rst:128 msgid ":doc:`System > Packages `" msgstr ":doc:`System > Pakete `" -#: ../manage/roles/admin-permissions.rst:121 #: ../manage/roles/admin-permissions.rst:130 msgid "``admin.report_profile``" msgstr "``admin.report_profile``" -#: ../manage/roles/admin-permissions.rst:122 #: ../manage/roles/admin-permissions.rst:131 msgid ":doc:`Manage > Report Profiles `" msgstr ":doc:`Verwalten > Report-Profile `" -#: ../manage/roles/admin-permissions.rst:123 #: ../manage/roles/admin-permissions.rst:132 msgid "Access to view reports: ``report``" msgstr "Zugang zu Berichten: ``report``" -#: ../manage/roles/admin-permissions.rst:124 #: ../manage/roles/admin-permissions.rst:133 msgid "``admin.role``" msgstr "``admin.role``" -#: ../manage/roles/admin-permissions.rst:125 #: ../manage/roles/admin-permissions.rst:134 msgid ":doc:`Manage > Roles `" msgstr "doc:`Verwalten > Rollen `" -#: ../manage/roles/admin-permissions.rst:127 #: ../manage/roles/admin-permissions.rst:136 msgid "``admin.scheduler``" msgstr "``admin.scheduler``" -#: ../manage/roles/admin-permissions.rst:128 #: ../manage/roles/admin-permissions.rst:137 msgid ":doc:`Manage > Scheduler `" msgstr "doc:`Verwalten > Automatisierung `" -#: ../manage/roles/admin-permissions.rst:129 #: ../manage/roles/admin-permissions.rst:138 msgid "For automation on tickets" msgstr "Für die Automatisierung von Tickets" -#: ../manage/roles/admin-permissions.rst:130 #: ../manage/roles/admin-permissions.rst:139 msgid "``admin.security``" msgstr "``admin.security``" -#: ../manage/roles/admin-permissions.rst:131 #: ../manage/roles/admin-permissions.rst:140 msgid ":doc:`Settings > Security `" msgstr ":doc:`Einstellungen > Sicherheit `" -#: ../manage/roles/admin-permissions.rst:132 #: ../manage/roles/admin-permissions.rst:141 msgid "Settings of Zammad. This also covers third party authentications." msgstr "" "Einstellungen von Zammad. Dies gilt auch für die Authentifizierung über " "Drittanbietern." -#: ../manage/roles/admin-permissions.rst:133 #: ../manage/roles/admin-permissions.rst:142 msgid "``admin.session``" msgstr "``admin.session``" -#: ../manage/roles/admin-permissions.rst:134 #: ../manage/roles/admin-permissions.rst:143 msgid ":doc:`System > Sessions `" msgstr ":doc:`System > Sitzungen `" -#: ../manage/roles/admin-permissions.rst:136 #: ../manage/roles/admin-permissions.rst:145 msgid "``admin.setting_system``" msgstr "``admin.setting_system``" -#: ../manage/roles/admin-permissions.rst:137 #: ../manage/roles/admin-permissions.rst:146 msgid ":doc:`Settings > System `" msgstr ":doc:`Einstellungen > System `" -#: ../manage/roles/admin-permissions.rst:139 #: ../manage/roles/admin-permissions.rst:148 msgid "``admin.sla``" msgstr "``admin.sla``" -#: ../manage/roles/admin-permissions.rst:140 #: ../manage/roles/admin-permissions.rst:149 msgid ":doc:`Manage > SLAs `" msgstr ":doc:`Verwalten > SLAs `" -#: ../manage/roles/admin-permissions.rst:142 +#: ../manage/roles/admin-permissions.rst:151 +msgid "``admin.system_report``" +msgstr "``admin.system_report``" + +#: ../manage/roles/admin-permissions.rst:152 +msgid ":doc:`System > System Report `" +msgstr ":doc:`System > System-Bericht `" + #: ../manage/roles/admin-permissions.rst:154 msgid "``admin.tag``" msgstr "``admin.tag``" -#: ../manage/roles/admin-permissions.rst:143 #: ../manage/roles/admin-permissions.rst:155 msgid ":doc:`Manage > Tags `" msgstr ":doc:`Verwalten > Tags `" -#: ../manage/roles/admin-permissions.rst:145 #: ../manage/roles/admin-permissions.rst:157 msgid "``admin.template``" msgstr "``admin.template``" -#: ../manage/roles/admin-permissions.rst:146 #: ../manage/roles/admin-permissions.rst:158 msgid ":doc:`Manage > Templates `" msgstr ":doc:`Verwalten > Textbausteine `" -#: ../manage/roles/admin-permissions.rst:148 #: ../manage/roles/admin-permissions.rst:160 msgid "``admin.text_module``" msgstr "``admin.text_module``" -#: ../manage/roles/admin-permissions.rst:149 #: ../manage/roles/admin-permissions.rst:161 msgid ":doc:`Manage > Text Modules `" msgstr ":doc:`Verwalten > Textbausteine `" -#: ../manage/roles/admin-permissions.rst:151 #: ../manage/roles/admin-permissions.rst:163 msgid "``admin.ticket``" msgstr "``admin.ticket``" -#: ../manage/roles/admin-permissions.rst:152 #: ../manage/roles/admin-permissions.rst:164 msgid ":doc:`Settings > Tickets `" msgstr ":doc:`Einstellungen > Tickets `" -#: ../manage/roles/admin-permissions.rst:153 #: ../manage/roles/admin-permissions.rst:165 msgid "Does not grant access to :doc:`/misc/composer`" msgstr "Gewährt keinen Zugriff auf :doc:`/misc/composer`" -#: ../manage/roles/admin-permissions.rst:154 +#: ../manage/roles/admin-permissions.rst:166 +msgid "``admin.ticket_auto_assignment``" +msgstr "``admin.ticket_auto_assignment``" + +#: ../manage/roles/admin-permissions.rst:167 +msgid ":ref:`Settings > Ticket > Auto Assignment `" +msgstr "" +":ref:`Einstellungen > Ticket > Automatische Zuweisung `" + +#: ../manage/roles/admin-permissions.rst:169 +msgid "``admin.ticket_duplicate_detection``" +msgstr "``admin.ticket_duplicate_detection``" + +#: ../manage/roles/admin-permissions.rst:170 +msgid ":ref:`Settings > Ticket > Duplicate Detection `" +msgstr "" +":ref:`Einstellungen > Ticket > Duplikaterkennung `" + +#: ../manage/roles/admin-permissions.rst:172 +msgid "``admin.ticket_priority``" +msgstr "``admin.ticket_priority``" + +#: ../manage/roles/admin-permissions.rst:173 +msgid ":ref:`System > Objects >Ticket Priority `" +msgstr ":ref:`System > Objekte >Ticket-Priorität `" + +#: ../manage/roles/admin-permissions.rst:175 +msgid "``admin.ticket_state``" +msgstr "``admin.ticket_state``" + +#: ../manage/roles/admin-permissions.rst:176 +msgid ":ref:`System > Objects >Ticket State `" +msgstr ":ref:`System > Objekte >Ticket-Status `" + #: ../manage/roles/admin-permissions.rst:178 msgid "``admin.time_accounting``" msgstr "``admin.time_accounting``" -#: ../manage/roles/admin-permissions.rst:155 #: ../manage/roles/admin-permissions.rst:179 msgid ":doc:`Manage > Time Accounting `" msgstr ":doc:`Verwalten > Zeiterfassung `" -#: ../manage/roles/admin-permissions.rst:156 #: ../manage/roles/admin-permissions.rst:180 msgid "Also allows the export of timekeeping records." msgstr "Ermöglicht auch den Export von Zeiterfassungsdaten." -#: ../manage/roles/admin-permissions.rst:157 #: ../manage/roles/admin-permissions.rst:181 msgid "``admin.translation``" msgstr "``admin.translation``" -#: ../manage/roles/admin-permissions.rst:158 #: ../manage/roles/admin-permissions.rst:182 msgid ":doc:`System > Translations `" msgstr ":doc:`System > Übersetzungen `" -#: ../manage/roles/admin-permissions.rst:159 #: ../manage/roles/admin-permissions.rst:183 msgid "Also enables inline translation" msgstr "Ermöglicht auch Inline-Übersetzung" -#: ../manage/roles/admin-permissions.rst:160 #: ../manage/roles/admin-permissions.rst:184 msgid "``admin.trigger``" msgstr "``admin.trigger``" -#: ../manage/roles/admin-permissions.rst:161 #: ../manage/roles/admin-permissions.rst:185 msgid ":doc:`Manage > Triggers `" msgstr ":doc:`Verwalten > Trigger `" -#: ../manage/roles/admin-permissions.rst:163 #: ../manage/roles/admin-permissions.rst:187 msgid "``admin.user``" msgstr "``admin.user``" -#: ../manage/roles/admin-permissions.rst:164 #: ../manage/roles/admin-permissions.rst:188 msgid ":doc:`Manage > Users `" msgstr ":doc:`Verwalten > Benutzer `" @@ -11066,6 +11060,14 @@ msgstr "" "🏴‍☠️ Mit dieser Berechtigung können Benutzer :ref:`die Sitzungen anderer " "Benutzer übernehmen ` ." +#: ../manage/roles/admin-permissions.rst:193 +msgid "``admin.webhook``" +msgstr "``admin.webhook``" + +#: ../manage/roles/admin-permissions.rst:194 +msgid ":doc:`Manage > Webhook `" +msgstr "doc:`Verwalten > Webhook `" + #: ../manage/roles/agent-permissions.rst:2 msgid "Agent Permissions" msgstr "Agenten-Berechtigungen" @@ -11572,36 +11574,45 @@ msgid "than the user that generated them." msgstr "als der Benutzer, der sie erstellt hat." #: ../manage/roles/user-preferences-permissions.rst:43 +msgid "``user_preferences.appearance``" +msgstr "``user_preferences.appearance``" + +#: ../manage/roles/user-preferences-permissions.rst:44 +msgid "Appearance configuration" +msgstr "Konfiguration Aussehen" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "Users can switch between dark, light and" +msgstr "Benutzer können zwischen Dunkel-, Hell- und" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "automatic mode." +msgstr "Auutomatik-Modus wechseln." + #: ../manage/roles/user-preferences-permissions.rst:47 msgid "``user_preferences.avatar``" msgstr "``user_preferences.avatar``" -#: ../manage/roles/user-preferences-permissions.rst:44 #: ../manage/roles/user-preferences-permissions.rst:48 msgid "Avatar settings" msgstr "Avatar-Einstellungen" -#: ../manage/roles/user-preferences-permissions.rst:45 #: ../manage/roles/user-preferences-permissions.rst:49 msgid "Override the default Gravatar with a custom avatar" msgstr "Überschreiben Sie den Standard-Gravatar mit einem eigenen Avatar" -#: ../manage/roles/user-preferences-permissions.rst:46 #: ../manage/roles/user-preferences-permissions.rst:50 msgid "``user_preferences.calendar``" msgstr "``user_preferences.calendar``" -#: ../manage/roles/user-preferences-permissions.rst:47 #: ../manage/roles/user-preferences-permissions.rst:51 msgid "Configure the calendar feed" msgstr "Konfigurieren Sie den Kalender-Feed" -#: ../manage/roles/user-preferences-permissions.rst:49 #: ../manage/roles/user-preferences-permissions.rst:53 msgid "``user_preferences.device``" msgstr "``user_preferences.device``" -#: ../manage/roles/user-preferences-permissions.rst:50 #: ../manage/roles/user-preferences-permissions.rst:54 msgid "Manage device login sessions" msgstr "Verwalten von Login Sitzungen" @@ -11619,22 +11630,18 @@ msgstr "" msgid "To learn more, see :doc:`/manage/trigger/system-notifications`." msgstr "Mehr erfahren Sie unter :doc:`/manage/trigger/system-notifications`." -#: ../manage/roles/user-preferences-permissions.rst:54 #: ../manage/roles/user-preferences-permissions.rst:58 msgid "``user_preferences.language``" msgstr "``user_preferences.language``" -#: ../manage/roles/user-preferences-permissions.rst:55 #: ../manage/roles/user-preferences-permissions.rst:59 msgid "Configure the UI locale/language" msgstr "Konfigurieren Sie die Sprache der Benutzeroberfläche" -#: ../manage/roles/user-preferences-permissions.rst:57 #: ../manage/roles/user-preferences-permissions.rst:61 msgid "``user_preferences.linked_accounts``" msgstr "``user_preferences.linked_accounts``" -#: ../manage/roles/user-preferences-permissions.rst:58 #: ../manage/roles/user-preferences-permissions.rst:62 msgid "Account linking" msgstr "Verknüpfte Konten" @@ -11663,7 +11670,6 @@ msgstr "" "ist dies die einzige Möglichkeit für Benutzer, Logins von Drittanbietern zu " "verwenden." -#: ../manage/roles/user-preferences-permissions.rst:63 #: ../manage/roles/user-preferences-permissions.rst:67 msgid "``user_preferences.notifications``" msgstr "``user_preferences.notifications``" @@ -11692,7 +11698,6 @@ msgstr "" msgid "Customers can't receive ticket notifications at all." msgstr "Kunden können überhaupt keine Ticket-Benachrichtigungen erhalten." -#: ../manage/roles/user-preferences-permissions.rst:69 #: ../manage/roles/user-preferences-permissions.rst:73 msgid "``user_preferences.out_of_office``" msgstr "``user_preferences.out_of_office``" @@ -11718,7 +11723,6 @@ msgstr "" msgid "they're replacing." msgstr "den sie ersetzen." -#: ../manage/roles/user-preferences-permissions.rst:75 #: ../manage/roles/user-preferences-permissions.rst:79 msgid "``user_preferences.overview_sorting``" msgstr "``user_preferences.overview_sorting``" @@ -11748,12 +11752,10 @@ msgid "overviews has no effect on custom orders." msgstr "" "von Übersichten hat keine Auswirkungen auf benutzerdefinierte Anpassungen." -#: ../manage/roles/user-preferences-permissions.rst:82 #: ../manage/roles/user-preferences-permissions.rst:86 msgid "``user_preferences.password``" msgstr "``user_preferences.password``" -#: ../manage/roles/user-preferences-permissions.rst:83 #: ../manage/roles/user-preferences-permissions.rst:87 msgid "Change account password" msgstr "Account Kennwort ändern" @@ -11772,7 +11774,6 @@ msgstr "falls Sie einen Identitätsserver eines Drittanbieters (wie LDAP)" msgid "your only allowed authentication method." msgstr "als Ihre einzige zulässige Authentifizierungsmethode verwenden." -#: ../manage/roles/user-preferences-permissions.rst:87 #: ../manage/roles/user-preferences-permissions.rst:91 msgid "``user_preferences.two_factor_authentication``" msgstr "``user_preferences.two_factor_authentication``" @@ -11815,8 +11816,12 @@ msgstr "" "konfigurieren, die für diese Objekte ausgeführt werden sollen." #: ../manage/scheduler.rst:19 +#, fuzzy +#| msgid "" +#| "Schedulers can be used to send periodic reminder emails. Use :doc:`/" +#| "system/variables` to build highly-customized email templates." msgid "" -"Schedulers can be used to send periodic reminder emails. Use :doc:`/system/" +"Schedulers can be used to send periodic reminder emails. Use :doc:`/misc/" "variables` to build highly-customized email templates." msgstr "" "Automatisierungen können verwendet werden, um periodische Erinnerungs-E-" @@ -13065,8 +13070,12 @@ msgstr "" "modules.html>`." #: ../manage/text-modules.rst:57 +#, fuzzy +#| msgid "" +#| "The example text modules below use :doc:`/system/variables` to " +#| "dynamically insert information like the customer's or agent's names." msgid "" -"The example text modules below use :doc:`/system/variables` to dynamically " +"The example text modules below use :doc:`/misc/variables` to dynamically " "insert information like the customer's or agent's names." msgstr "" "Die folgenden Beispiel-Textbausteine verwenden :doc:`/system/variables`, um " @@ -13482,8 +13491,8 @@ msgstr "Erstellt am" #: ../misc/object-conditions/basics.rst:144 #: ../misc/object-conditions/basics.rst:160 #: ../misc/object-conditions/basics.rst:168 -#: ../misc/object-conditions/basics.rst:178 ../settings/ticket.rst:2 -#: ../system/variables/ticket.rst:2 +#: ../misc/object-conditions/basics.rst:178 ../misc/variables/ticket.rst:2 +#: ../settings/ticket.rst:2 msgid "Ticket" msgstr "Ticket" @@ -13767,8 +13776,13 @@ msgid "When creating a trigger, define your changes here:" msgstr "Wenn Sie einen Trigger erstellen, definieren Sie hier Ihre Änderungen:" #: ../manage/trigger/how-do-they-work.rst:79 +#, fuzzy +#| msgid "" +#| "Certain actions (such as *email*, *SMS* and *notes*) support :doc:`/" +#| "system/variables`, which can be used to build highly-customized message " +#| "templates." msgid "" -"Certain actions (such as *email*, *SMS* and *notes*) support :doc:`/system/" +"Certain actions (such as *email*, *SMS* and *notes*) support :doc:`/misc/" "variables`, which can be used to build highly-customized message templates." msgstr "" "Bestimmte Aktionen (z.B. *E-Mail*, *SMS* und *Notizen*) unterstützen :doc:`/" @@ -13804,10 +13818,15 @@ msgstr "" "oder *relativ* angegeben werden." #: ../manage/trigger/how-do-they-work.rst:92 +#, fuzzy +#| msgid "" +#| "You can also combine static text with placeholders for text fields. " +#| "Remember that the placeholders' values have to be known during trigger " +#| "runtime. Learn more about :doc:`/system/variables`." msgid "" "You can also combine static text with placeholders for text fields. Remember " "that the placeholders' values have to be known during trigger runtime. Learn " -"more about :doc:`/system/variables`." +"more about :doc:`/misc/variables`." msgstr "" "Sie können auch statischen Text mit Platzhaltern für Textfelder kombinieren. " "Beachten Sie, dass die Werte der Platzhalter zum Ausführungszeitpunkt des " @@ -15050,10 +15069,16 @@ msgstr "" "`webhook-payload-default` an den Endpunkt." #: ../manage/webhook/add.rst:98 +#, fuzzy +#| msgid "" +#| "When switched on, a code editor will be shown below, where you can " +#| "configure custom payload for your webhook in JSON format. To insert " +#| "supported :doc:`/system/variables` use ``::`` or ``#{`` shortcuts for " +#| "autocomplete." msgid "" "When switched on, a code editor will be shown below, where you can configure " "custom payload for your webhook in JSON format. To insert supported :doc:`/" -"system/variables` use ``::`` or ``#{`` shortcuts for autocomplete." +"misc/variables` use ``::`` or ``#{`` shortcuts for autocomplete." msgstr "" "Nach dem aktivieren wird unten ein Code-Editor angezeigt, in dem Sie " "benutzerdefinierte Payloads für Ihren Webhook im JSON-Format konfigurieren " @@ -18157,14740 +18182,14734 @@ msgstr "" "Erfahren Sie, wie Sie mit dem Expertenmodus von Zammad noch " "leistungsfähigere Bedingungen mit UND/ODER-Beziehungen erstellen können." -#: ../settings/branding.rst:10 -msgid "Product Name" -msgstr "Produktname" +#: ../misc/variables.rst:2 +msgid "Variables" +msgstr "Variablen" -#: ../settings/branding.rst:7 +#: ../misc/variables.rst:4 msgid "" -"Defines the name of the application, shown in the web interface, tabs and " -"title bar of the web browser." -msgstr "" -"Legt den Namen der Applikation fest, welcher im Web-Interface, in Tabs und " -"in der Titelseite des Webbrowsers angezeigt wird." - -#: ../settings/branding.rst:10 -msgid "Default value: ``Zammad Helpdesk``" -msgstr "Standardwert: ``Zammad Helpdesk``" - -#: ../settings/branding.rst:13 -msgid "Will be shown in the app and is included in email footers." -msgstr "Wird in der App und in der E-Mail-Fußzeile angezeigt." - -#: ../settings/branding.rst:19 -msgid "Logo" -msgstr "Logo" - -#: ../settings/branding.rst:16 -msgid "Defines the logo of the application, shown in the login page of Zammad." +"Please note that this is just an overview of available variables. It might " +"be incomplete or variables might not be available within some functions. If " +"you're missing variables or are not sure if something is not working as " +"expected, feel free to ask over at the `Community `_." msgstr "" -"Legt das Logo der Anwendung fest, das auf der Anmeldeseite von Zammad " -"angezeigt wird." +"Bitte beachten Sie, dass dies nur eine Übersicht der verfügbaren Variablen " +"ist. Manche Variablen können in bestimmten Funktionen inkompatibel oder " +"nicht verfügbar sein. Wenn Sie Variablen vermissen oder sich nicht sicher " +"sind, ob diese wie erwartet funktionieren, fragen Sie sehr gern in unserer " +"`Community `_ nach." -#: ../settings/branding.rst:18 +#: ../misc/variables.rst:10 msgid "" -"Ensure to hit the \"Submit\" button after uploading the logo. Otherwise your " -"change will not be saved." +"Variables can be called by typing ``::`` (just like text modules in the " +"frontend), as long as you're in a supported text field within the backend. " +"Zammad will display all variables being available within this context and " +"replace it to the variable as soon as you selected an entry." msgstr "" -"Klicken Sie nach dem Hochladen des Logos auf die Schaltfläche \"Senden\". " -"Andernfalls wird Ihre Änderung nicht gespeichert." +"Variablen können durch Eingabe von ``::`` aufgerufen werden (genau wie " +"Textbausteine im Frontend), solange man sich in einem unterstützten Textfeld " +"im Backend befindet. Zammad zeigt alle Variablen an, die in diesem Kontext " +"verfügbar sind und ersetzt sie durch die Variable, sobald Sie einen Eintrag " +"ausgewählt haben." -#: ../settings/branding.rst:22 +#: ../misc/variables.rst:15 msgid "" -"Allows to set the default language of the Zammad instance. The here defined " -"locale mostly acts as a fallback for:" -msgstr "" -"Ermöglicht es, die Standardsprache der Zammad-Instanz festzulegen. Die hier " -"definierte Region dient meist als Fallback für:" - -#: ../settings/branding.rst:25 -msgid "user preferences (if Zammad can't detect the users locale)" +"You have an empty field which you referenced and it appears as ``-``? That's " +"currently working as designed - you might want to ensure that these fields " +"always have a value." msgstr "" -"Benutzereinstellungen (wenn Zammad die Region des Benutzers nicht erkennen " -"kann)" +"Haben Sie ein leeres Feld, auf das Sie verweisen, und es erscheint als ``-" +"``? Das funktioniert derzeit wie vorgesehen - Sie sollten sicherstellen, " +"dass diese Felder immer einen Wert beinhalten." -#: ../settings/branding.rst:26 -msgid "CSV output (reporting, time accounting)" -msgstr "CSV-Ausgabe (Berichte, Zeiterfassung)" +#: ../misc/variables.rst:20 +msgid "Variable Categories" +msgstr "Variablen Kategorien" -#: ../settings/branding.rst:30 -msgid "Define the timezone of your Zammad installation." -msgstr "Legen Sie die Zeitzone für Ihre Zammad-Installation fest." +#: ../misc/variables.rst:31 +msgid "Wait, What About Custom Objects?" +msgstr "Moment, was ist mit benutzerdefinierten Objekten?" -#: ../settings/branding.rst:32 +#: ../misc/variables.rst:33 msgid "" -"This does not have any effect on timings for your agents or how Zammad " -"stores date and time values." +"Good point! Of course, we can't predict what objects you might create, but " +"we can give you a hint on how to put the puzzle together to get your custom " +"values." msgstr "" -"Dies hat keine Auswirkung auf die Zeiteinteilung Ihrer Agenten oder darauf, " -"wie Zammad Datums- und Zeitwerte speichert." +"Das ist ein guter Punkt! Natürlich können wir nicht vorhersagen, welche " +"Objekte Sie erstellen werden, aber wir können Ihnen einen Hinweis geben, wie " +"Sie Ihre eigenen Werte verwenden können." -#: ../settings/branding.rst:35 -msgid "Changing this value has direct consequences on the following areas:" +#: ../misc/variables.rst:36 +msgid "" +"For this, we'll talk about the inner part of the variable (so everything " +"within ``#{}``), please put the outer part around to have a valid variable. " +"The first part of the variable name consist of the object type. Currently " +"these are:" msgstr "" -"Die Änderung dieses Wertes hat direkte Auswirkungen auf die folgenden " -"Bereiche:" +"Hier geht es um den inneren Teil der Variable (also alles innerhalb von ``#{}" +"``). Bitte fügen Sie den äußeren Teil hinzu, um eine gültige Variable zu " +"erhalten. Der erste Teil des Variablennamens besteht aus dem Objekttyp. " +"Derzeit sind dies:" -#: ../settings/branding.rst:37 -msgid ":doc:`/manage/scheduler` tasks" -msgstr ":doc:`/manage/scheduler` Aufgaben" +#: ../misc/variables.rst:41 +msgid "Ticket (``ticket``)" +msgstr "Ticket (``ticket``)" -#: ../settings/branding.rst:38 -msgid "search indexing (and thus reporting)" -msgstr "Suchindexierung (und damit Berichte)" +#: ../misc/variables.rst:42 +msgid "User (``user``)" +msgstr "Benutzer (``user``)" -#: ../settings/branding.rst:40 -msgid "calendar subscriptions" -msgstr "Kalender-Abonnements" +#: ../misc/variables.rst:43 +msgid "Organization (``organization``)" +msgstr "Organisation (``organization``)" -#: ../settings/branding.rst:41 -msgid "browser printing" -msgstr "Drucken im Browser" +#: ../misc/variables.rst:44 +msgid "Group (``group``)" +msgstr "Gruppe (``group``)" -#: ../settings/branding.rst:43 +#: ../misc/variables.rst:46 +#, fuzzy +#| msgid "" +#| "The second part is the name of the object. This is the name you define " +#| "during object creation and can be found within the object menu at any " +#| "time. The first and second part of a variable is divided by a point, e." +#| "g.: ``ticket.number`` which will in total be ``#{ticket.number}``." msgid "" -"Please note that some of above are fallbacks in case Zammad could not detect " -"the agents timezone correctly." +"The second part is the name of the attribute. This is the name you define " +"during object creation and can be found within the object attribute menu at " +"any time. The first and second part of a variable is divided by a point, e." +"g.: ``ticket.number`` which will in total be ``#{ticket.number}``." msgstr "" -"Bitte beachten Sie, dass es sich bei einigen der obigen Optionen um " -"Fallbacks handelt, falls Zammad die Zeitzone des Agenten nicht korrekt " -"erkennen konnte." - -#: ../settings/branding.rst:77 -msgid "Pretty Date" -msgstr "Schönes Datum" +"Der zweite Teil ist der Name des Objektattributs. Diesen Namen legen Sie bei " +"der Objektattributerstellung fest und Sie können ihn jederzeit im Objektmenü " +"in den Einstellungen wiederfinden. Der erste und zweite Teil einer Variablen " +"wird durch einen Punkt getrennt, z.B.: ``ticket.number``, was im Ergebnis " +"``#{ticket.number}`` ergibt." -#: ../settings/branding.rst:47 +#: ../misc/variables.rst:51 msgid "" -"This setting allows you to define how Zammad should display time stamps " -"within the interface to all users." +"Now, in some situations it's possible that you'll need to use a third part. " +"The best example for such a situation would be a ``select`` or ``tree-" +"select`` field which will by default return the key value, not it's display " +"name. For this, just extend your variable with ``.value``. This will result " +"in ``#{ticket.select.value}``." msgstr "" -"Mit dieser Einstellung können Sie festlegen, wie Zammad Zeitstempel für alle " -"Benutzer anzeigen soll." +"In manchen Situationen ist es möglich, dass Sie einen dritten Teil verwenden " +"müssen. Das beste Beispiel für eine solche Situation wäre ein ``Auswahl``- " +"oder ``Baumauswahl``-Feld, das standardmäßig den Schlüsselwert und nicht den " +"Anzeigenamen zurückgibt. Erweitern Sie dazu einfach Ihre Variable mit ``." +"value``. Das Ergebnis ist dann ``#{ticket.select.value}``." -#: ../settings/branding.rst:50 +#: ../misc/variables.rst:60 +msgid "Using Translated Variables" +msgstr "Verwendung übersetzter Variablen" + +#: ../misc/variables.rst:62 msgid "" -"This does not have any effect on how Zammad returns e.g. time values via " -"variables." +"If you want to use a translated variable in triggers or schedulers, you can " +"extend the placeholder like this: ``#{t(ticket.state.name)}``. The ``t`` " +"tells Zammad to search for fitting translated strings. The used output " +"language is based on the system language of Zammad which you can set in the " +"admin panel under :doc:`/settings/branding` or based on the selected locale " +"in the trigger/scheduler edit dialog." msgstr "" -"Dies hat keinen Einfluss darauf, wie Zammad z.B. Zeitwerte über Variablen " -"ausgibt." +"Wenn Sie eine übersetzte Variable in Triggern oder Automatisierungen " +"verwenden möchten, können Sie den Platzhalter wie folgt erweitern: " +"``#{t(ticket.status.name)}``. Das ``t`` sagt Zammad, dass es nach passenden " +"übersetzten Zeichenketten suchen soll. Die verwendete Ausgabesprache basiert " +"auf der Systemsprache von Zammad, die Sie im Admin-Panel unter :doc:`/" +"settings/branding` einstellen können oder basierend auf der ausgewählten " +"Sprache im Trigger-/Automatisierungs-Dialog." -#: ../settings/branding.rst:77 -msgid "Choose in between the following options:" -msgstr "Wählen Sie zwischen den folgenden Optionen:" +#: ../misc/variables.rst:69 +msgid "" +"A possible use-case: you want to send your customers updates on tickets via " +"trigger or scheduler which should include the state of the ticket. Using the " +"default ``#{ticket.state.name}`` (without the translation flag ``t()``) " +"would lead to the output of the original (english) name of the state." +msgstr "" +"Ein möglicher Anwendungsfall: Sie möchten Ihren Kunden per Trigger oder " +"Scheduler Updates zu Tickets schicken, die den Status des Tickets enthalten " +"sollen. Die Verwendung des Standardwertes ``#{ticket.state.name}`` (ohne das " +"Übersetzungsflag ``t()``) würde zur Ausgabe des ursprünglichen (englischen) " +"Namens des Status führen." -#: ../settings/branding.rst:64 -msgid "relative" -msgstr "relativ" +#: ../misc/variables.rst:75 +msgid "Date and Time Formatting" +msgstr "Formatierung von Datum und Uhrzeit" -#: ../settings/branding.rst:55 +#: ../misc/variables.rst:77 msgid "" -"This timestamp shows a relative time span until it switches to a date. Over " -"time, it will change as follows:" +"The system (trigger/scheduler selected) locale and timezone predefines a " +"default format of date and timestamp. This format is customizable by using " +"the ``dt()`` method." msgstr "" -"Dieser Zeitstempel zeigt eine relative Zeitspanne an, bis er zu einem Datum " -"wechselt. Im Laufe der Zeit ändert er sich wie folgt:" +"Die Sprache und Zeitzone des Systems (oder in Trigger/Automatisierung " +"ausgewählt) gibt ein Standardformat für Datum und Zeitstempel vor. Dieses " +"Format kann mit Hilfe der Methode ``dt()`` angepasst werden." -#: ../settings/branding.rst:58 -msgid "just now" -msgstr "gerade eben" +#: ../misc/variables.rst:79 +msgid "The method arguments are as follows:" +msgstr "Die Argumente der Methode lauten wie folgt:" -#: ../settings/branding.rst:59 -msgid "5 minutes ago" -msgstr "vor 5 Minuten" +#: ../misc/variables.rst:81 +msgid "The date or timestamp variable you want to format." +msgstr "Die Datums- oder Zeitstempelvariable, die Sie formatieren möchten." -#: ../settings/branding.rst:60 -msgid "3 days 1 hour ago" -msgstr "vor 3 Tagen 1 Stunde" +#: ../misc/variables.rst:82 +msgid "The output format string." +msgstr "Die Zeichenkette für das Ausgabeformat." -#: ../settings/branding.rst:61 -msgid "``03/04/2022``" -msgstr "``03/04/2022``" +#: ../misc/variables.rst:83 +msgid "The timezone to apply (optional)." +msgstr "Die zu verwendende Zeitzone (optional)." -#: ../settings/branding.rst:63 -msgid "Hovering the timestamp helps, you'll always get a clean timestamp then." +#: ../misc/variables.rst:85 +#: ../system/objects/external-data-source-example.rst:23 +msgid "**Example:**" +msgstr "**Beispiel:**" + +#: ../misc/variables.rst:86 +msgid "" +"``#{dt(ticket.updated_at, \"%A %Y-%m-%d %H:%M in the office\", \"Europe/" +"Berlin\")}``" msgstr "" -"Wenn Sie den Mauszeiger über den Zeitstempel bewegen, erhalten Sie immer " -"einen detaillierten Zeitstempel." +"``#{dt(ticket.updated_at, \"%A %Y-%m-%d %H:%M im Büro\", \"Europa/Berlin\")}" +"``" -#: ../settings/branding.rst:71 -msgid "absolute" -msgstr "absolut" +#: ../misc/variables.rst:87 +msgid "Monday, 2024-03-18 15:31 in the office" +msgstr "Montag, 2024-03-18 15:31 im Büro" -#: ../settings/branding.rst:67 +#: ../misc/variables.rst:89 msgid "" -"This timestamp always includes the week day. For one week after creation, " -"the timestamp will not contain the date itself: Thursday 18:35." +"If you want to use our example, make sure to paste the string above without " +"formatting (``CTRL+Shift+v``), otherwise it won't work." msgstr "" -"Dieser Zeitstempel enthält immer den Wochentag. Innerhalb einer Woche nach " -"der Erstellung enthält der Zeitstempel nicht das Datum selbst: Donnerstag " -"18:35." +"Wenn Sie unser Beispiel verwenden wollen, fügen Sie die obige Zeichenkette " +"ohne Formatierung ein (``STRG+Umschalt+v``), andernfalls funktioniert es " +"nicht." -#: ../settings/branding.rst:71 -msgid "After a week it will switch to: ``Friday 4. Mar 16:00``." -msgstr "Nach einer Woche wechselt sie zu: ``Freitag 4. März 16:00``." +#: ../misc/variables.rst:93 +msgid "The following table lists available format directives:" +msgstr "" +"In der folgenden Tabelle sind die verfügbaren Formatparameter aufgeführt:" -#: ../settings/branding.rst:76 -msgid "timestamp" -msgstr "Zeitstempel" +#: ../misc/variables.rst:99 +msgid "Parameter" +msgstr "Parameter" -#: ../settings/branding.rst:74 -msgid "" -"This will cause Zammad to show a complete timestamp according to your locale " -"defaults. For English this could be e.g. ``2022/12/03 2:40 pm`` or for " -"German e.g. ``12.03.2022 14:40``." -msgstr "" -"Dies veranlasst Zammad, einen vollständigen Zeitstempel gemäß den " -"Standardeinstellungen Ihrer Region anzuzeigen. Für Englisch ist das z.B. " -"``2022/12/03 2:40 pm`` oder für Deutsch ``12.03.2022 14:40``." +#: ../misc/variables.rst:102 +msgid "``%Y``" +msgstr "``%Y``" -#: ../settings/branding.rst:78 -msgid "Default setting: ``relative``." -msgstr "Standardeinstellung: ``relativ``." +#: ../misc/variables.rst:103 +msgid "Year with 4 digits" +msgstr "Jahr mit 4 Ziffern" -#: ../settings/security.rst:2 -msgid "Security" -msgstr "Sicherheit" +#: ../misc/variables.rst:104 +msgid "Use ``%y`` for year with 2 digits" +msgstr "Verwenden Sie ``%y`` für Jahreszahlen mit 2 Ziffern" -#: ../settings/security.rst:4 -msgid "" -"For your overview we split each tab within security settings into its own " -"page:" -msgstr "" -"Der Übersicht halber haben wir jeden Tab der Sicherheitseinstellungen in " -"eine eigene Seite aufgeteilt:" +#: ../misc/variables.rst:105 +msgid "``%m``" +msgstr "``%m``" -#: ../settings/security/base.rst:2 ../settings/system/base.rst:2 -#: ../settings/ticket.rst:8 -msgid "Base" -msgstr "Basis" +#: ../misc/variables.rst:106 +msgid "Month of year (as number with zero-padding)" +msgstr "Monat des Jahres (als Zahl, ggf. mit vorangestellter Null)" -#: ../settings/security/base.rst:5 -msgid "New User Accounts" -msgstr "Neue Benutzer-Konten" +#: ../misc/variables.rst:107 +msgid "Use ``%-m`` for month without zero-padding" +msgstr "Verwenden Sie ``%-m`` für den Monat ohne vorangestellte Null" -#: ../settings/security/base.rst:9 -msgid "" -"Activates the `register as a new customer` function on the login page. If " -"set to ``no`` only administrators or agents can create new accounts manually." +#: ../misc/variables.rst:108 +msgid "``%d``" +msgstr "``%d``" + +#: ../misc/variables.rst:109 +msgid "Day of month (as number with zero-padding)" +msgstr "Tag des Monats (als Zahl, ggf. mit vorangestellter Null)" + +#: ../misc/variables.rst:110 +msgid "Use ``%e`` for day without zero-padding" +msgstr "Verwenden Sie ``%e`` für Tage ohne vorangestellte Null" + +#: ../misc/variables.rst:111 +msgid "``%H``" +msgstr "``%H``" + +#: ../misc/variables.rst:112 +msgid "Hour of day in 24h notation with zero-padding" msgstr "" -"Aktiviert die Funktion \"Als neuer Kunde registrieren\" auf der Login-Seite. " -"Wenn diese Funktion auf ``Nein`` gesetzt ist, können nur Administratoren " -"oder Agenten neue Konten manuell erstellen." +"Stunde des Tages in 24-Stunden-Schreibweise, ggf. mit vorangestellter Null" -#: ../settings/security/base.rst:13 ../settings/security/base.rst:38 -#: ../settings/security/base.rst:66 -msgid "Default setting: ``yes``" -msgstr "Standardeinstellung: ``Ja``" +#: ../misc/variables.rst:113 +msgid "Use ``%k`` for hour without zero-padding" +msgstr "Verwenden Sie ``%k`` für Stunden ohne führende Null" -#: ../settings/security/base.rst:0 -msgid "Figure showing activated \"New User Accounts\" setting" -msgstr "Abbildung zeigt die aktivierte Einstellung \"Neue Benutzerkonten\"" +#: ../misc/variables.rst:114 +msgid "``%I``" +msgstr "``%I``" -#: ../settings/security/base.rst:22 +#: ../misc/variables.rst:115 +msgid "Hour of day in 12h notation with zero-padding" +msgstr "Uhrzeit im 12-Stunden-Format, ggf. mit vorangestellter Null" + +#: ../misc/variables.rst:116 msgid "" -"Deactivation of above function **does not** deactivate automatic account " -"creation! This means: If a user writes e.g. an email to Zammad and has no " -"account yet, Zammad will automatically create the account. User accounts are " -"a direct dependency of tickets and thus technically mandatory." +"Use ``%l`` for hour without zero-padding and ``%p`` / ``%P`` for meridian " +"indicator" msgstr "" -"Die Deaktivierung der obigen Funktion **deaktiviert nicht** die automatische " -"Kontoerstellung! Dies bedeutet: Wenn ein Benutzer z.B. eine E-Mail an Zammad " -"schreibt und noch kein Konto hat, wird Zammad das Konto automatisch " -"erstellen. Benutzerkonten sind eine direkte Abhängigkeit von Tickets und " -"somit technisch zwingend erforderlich." +"Verwenden Sie ``%l`` für die Stunde ohne vorangestellte Null und ``%p`` / " +"``%P`` für den Tageszeit-Indikator" -#: ../settings/security/base.rst:29 -msgid "Lost Password" -msgstr "Passwort verloren" +#: ../misc/variables.rst:117 +msgid "``%M``" +msgstr "``%M``" -#: ../settings/security/base.rst:33 -msgid "" -"Activates the `lost password` function on the login page. If set to ``no`` " -"only administrators may change the user's password - users may update their " -"own password if they're still logged in and they have the required :doc:" -"`permission `." -msgstr "" -"Aktiviert die Funktion `Kennwort vergessen` auf der Login-Seite. Wenn auf " -"``nein`` gesetzt, können nur Administratoren das Passwort des Benutzers " -"ändern - Benutzer können ihr eigenes Passwort aktualisieren, wenn sie noch " -"eingeloggt sind und die erforderliche :doc:`Berechtigung ` haben." +#: ../misc/variables.rst:118 +msgid "Minute of hour" +msgstr "Minute der Stunde" -#: ../settings/security/base.rst:0 -msgid "Figure showing activated \"Lost Password\" setting" -msgstr "Abbildung zeigt die aktivierte Einstellung \"Passwort verloren\"" +#: ../misc/variables.rst:120 +msgid "``%S``" +msgstr "``%S``" -#: ../settings/security/base.rst:49 -msgid "" -"With third party authentications - but especially LDAP - you may want to " -"disable this function. Zammad **will not** change third party login " -"passwords and instead set or change the local password!" -msgstr "" -"Bei einer Authentifizierung durch einen Drittanbieter - vor allem aber bei " -"LDAP - sollten Sie diese Funktion deaktivieren. Zammad **ändert keine** " -"Login-Passwörter von Drittanbietern und setzt oder ändert stattdessen das " -"lokale Passwort!" +#: ../misc/variables.rst:121 +msgid "Second of Minute" +msgstr "Sekunde der Minute" -#: ../settings/security/base.rst:56 -msgid "Password Login" -msgstr "Passwort-Anmeldung" +#: ../misc/variables.rst:123 +msgid "``%A``" +msgstr "``%A``" -#: ../settings/security/base.rst:60 -msgid "" -"Activates the username & password login by default and if no third-party " -"login is activated. Disabling password login on the Zammad login page only " -"takes effect if you enable any :doc:`third-party`." +#: ../misc/variables.rst:124 +msgid "Weekday name" +msgstr "Name des Wochentags" + +#: ../misc/variables.rst:125 +msgid "Use ``%a`` for abbreviated name or ``%^A`` for uppercase name" msgstr "" -"Aktiviert standardmäßig die Anmeldung mit Benutzernamen und Passwort wenn " -"keine Drittanbieteranmeldung aktiviert ist. Die Deaktivierung der Passwort-" -"Anmeldung auf der Zammad-Anmeldeseite wird nur wirksam, wenn Sie eine :doc:" -"`third-party` Anmeldung aktivieren." +"Verwenden Sie ``%a`` für abgekürzte Namen oder ``%^A`` für den Name in " +"Großbuchstaben" -#: ../settings/security/base.rst:64 -msgid "See :doc:`third-party` for supported third-party logins." -msgstr "Siehe :doc:`third-party` für unterstützte Drittanbieter-Logins." +#: ../misc/variables.rst:126 +msgid "``%B``" +msgstr "``%B``" -#: ../settings/security/base.rst:0 -msgid "Figure showing de-activated \"Password Login\" setting" -msgstr "Abbildung zeigt die deaktivierte Einstellung \"Passwort Anmeldung\"" +#: ../misc/variables.rst:127 +msgid "Month name" +msgstr "Name des Monats" -#: ../settings/security/base.rst:77 -msgid "" -"To help administrators to overcome \"login issues\", Zammad automatically " -"offers a password request for administrator users. This allows you to adjust " -"Third-Party applications even if the login does no longer work!" -msgstr "" -"Um Administratoren bei \"Anmelde-Problemen\" zu helfen, bietet Zammad " -"automatisch eine Passwortabfrage für Administrator-Benutzer an. Dies " -"ermöglicht es Ihnen, Anwendungen von Drittanbietern anzupassen, auch wenn " -"der Login nicht mehr funktioniert!" +#: ../misc/variables.rst:128 +msgid "Use ``%b`` for abbreviated name" +msgstr "Verwenden Sie ``%b`` für den abgekürzte Namen" -#: ../settings/security/base.rst:84 -msgid "Session Timeout" -msgstr "Sitzungs-Timeout" +#: ../misc/variables.rst:129 +msgid "``%U``" +msgstr "``%U``" -#: ../settings/security/base.rst:86 -msgid "" -"All settings below by default are set to ``4 weeks``. Session Timeout " -"defines the life time of a users session. As soon as it's reached, Zammad " -"will automatically log off the session in question." -msgstr "" -"Alle folgenden Einstellungen sind standardmäßig auf ``4 Wochen`` " -"eingestellt. Session Timeout definiert die Lebenszeit einer Benutzersitzung. " -"Sobald sie erreicht ist, meldet Zammad die betreffende Sitzung automatisch " -"ab." +#: ../misc/variables.rst:130 +msgid "Week number of current year" +msgstr "Wochennummer des laufenden Jahres" -#: ../settings/security/base.rst:91 +#: ../misc/variables.rst:131 +msgid "Use ``%W`` for a different calculation method" +msgstr "Verwenden Sie ``%W`` für eine andere Berechnungsmethode" + +#: ../misc/variables.rst:134 msgid "" -"Zammad takes the highest value set assigned for the user based on the " -"permissions." +"We support the known format directives for the Ruby built-in method " +"``strftime`` of the ``DateTime`` class. For more information, see `here " +"`_." msgstr "" -"Zammad nimmt den höchsten Wert, der dem Benutzer aufgrund der Berechtigungen " -"zugewiesen wurde." +"Wir unterstützen die bekannten Formatparameter für die in Ruby eingebaute " +"Methode ``strftime`` der Klasse ``DateTime``. Für weitere Informationen " +"siehe `hier `_." -#: ../settings/security/base.rst:94 -msgid "``admin``" -msgstr "``admin``" +#: ../misc/variables/article.rst:2 +msgid "Articles" +msgstr "Artikel" -#: ../settings/security/base.rst:96 -msgid "``ticket.customer``" -msgstr "``ticket.customer``" +#: ../misc/variables/article.rst:4 ../misc/variables/config.rst:4 +#: ../misc/variables/current-user.rst:4 ../misc/variables/ticket.rst:4 +msgid "" +"If you're missing variables or are not sure if something is not working as " +"expected, feel free to ask over at the `Community `_." +msgstr "" +"Wenn Sie Variablen vermissen oder sich nicht sicher sind, ob diese wie " +"erwartet funktionieren, fragen Sie gern in unserer `Community `_ nach." -#: ../settings/security/base.rst:97 -msgid "``default`` (fallback if user doesn't have above permissions set)" +#: ../misc/variables/article.rst:6 +#, fuzzy +#| msgid "" +#| "Below you can find all available ticket article-based variables within " +#| "Zammad. These can be called via Triggers for example. If you're unsure if " +#| "Zammad does support variables at the point you're at, you can try to type " +#| "``::`` to check." +msgid "" +"Below you can find all available ticket article-based variables within " +"Zammad. These can be called via triggers for example. If you're unsure if " +"Zammad does support variables at the point you're at, you can try to type " +"``::`` to check." msgstr "" -"``default`` (Fallback, wenn der Benutzer die oben genannten Berechtigungen " -"nicht hat)" +"Nachfolgend finden Sie alle verfügbaren Ticketartikel-basierten Variablen in " +"Zammad. Diese können z.B. über Trigger aufgerufen werden. Wenn Sie sich " +"nicht sicher sind, ob Zammad an der von Ihnen gewünschten Stelle Variablen " +"unterstützt, können Sie das prüfen indem Sie ``::`` einzugeben." -#: ../settings/security/base.rst:99 +#: ../misc/variables/article.rst:9 ../misc/variables/config.rst:9 +#: ../misc/variables/ticket.rst:9 msgid "" -"All settings act independently from each other allowing you to disable the " -"timeouts for e.g. admins, but not agents." +"The below list gives you an example what kind of data you can expect, it's " +"not intended to explain the data itself." msgstr "" -"Alle Einstellungen wirken unabhängig voneinander, so dass Sie z.B. nur die " -"Timeouts für Admins deaktivieren können." +"Die folgende Liste gibt Ihnen ein Beispiel dafür, welche Art von Daten Sie " +"erwarten können. Sie ist nicht dazu gedacht, die Daten selbst zu erklären." -#: ../settings/security/base.rst:115 -#: ../system/integrations/checkmk/api-reference.rst:13 -msgid "Example" -msgstr "Beispiel" +#: ../misc/variables/article.rst:11 +msgid "Article Variables" +msgstr "Artikel-Variablen" -#: ../settings/security/base.rst:107 -msgid "Let's suppose you configured the following session timeouts" -msgstr "Angenommen, Sie haben die folgenden Sitzungs-Timeouts konfiguriert" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "name" +msgstr "Name" -#: ../settings/security/base.rst:104 -msgid "default: 3 weeks" -msgstr "Standard: 3 Wochen" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "variable" +msgstr "Variable" -#: ../settings/security/base.rst:105 -msgid "admin: 2 weeks" -msgstr "admin: 2 Wochen" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "example" +msgstr "Beispiel" -#: ../settings/security/base.rst:106 -msgid "ticket.agent: 4 weeks" -msgstr "ticket.agent: 4 Wochen" +#: ../misc/variables/article.rst:1 +msgid "Article > Cc" +msgstr "Artikel > CC" -#: ../settings/security/base.rst:107 -msgid "ticket.customer: 1 week" -msgstr "ticket.customer: 1 Woche" +#: ../misc/variables/article.rst:1 +msgid "``#{article.cc}``" +msgstr "``#{article.cc}``" -#: ../settings/security/base.rst:115 -msgid "This results in the following situations" -msgstr "Daraus ergibt sich folgendes Szenario" +#: ../misc/variables/article.rst:1 +msgid "``jdoe@example.com, company@example.com``" +msgstr "``jdoe@example.com, firma@example.com``" -#: ../settings/security/base.rst:110 -msgid "a user with ``admin`` permission will have a timeout of 2 weeks" -msgstr "" -"ein Benutzer mit der Berechtigung ``admin`` hat einen Timeout von 2 Wochen" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Address" +msgstr "Artikel > Erstellt von > Adresse" -#: ../settings/security/base.rst:111 -msgid "" -"a user with ``admin`` and ``ticket.agent`` permissions will have a timeout " -"of 2 weeks" -msgstr "" -"ein Benutzer mit den Rechten ``admin`` und ``ticket.agent`` hat einen " -"Timeout von 2 Wochen" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.address}``" +msgstr "``#{article.created_by.address}``" -#: ../settings/security/base.rst:113 -msgid "" -"a user with ``ticket.customer`` permission will have a timeout of 1 week" +#: ../misc/variables/article.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set in user object" msgstr "" -"ein Benutzer mit der Berechtigung ``ticket.customer`` hat einen Timeout von " -"1 Woche" +"``Irgendeine Straße 1, 12345 Berlin`` oder leer wenn nicht am Benutzerobjekt " +"gesetzt" -#: ../settings/security/base.rst:115 -msgid "" -"a user with neither ``admin``, ``ticket.agent`` nor ``ticket.customer`` " -"permissions will have a timeout of 3 weeks" -msgstr "" -"ein Benutzer, der weder ``admin``, ``ticket.agent`` noch ``ticket.customer`` " -"Rechte hat, hat einen Timeout von 3 Wochen" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Department" +msgstr "Artikel > Erstellt von > Abteilung" -#: ../settings/security/password.rst:4 -msgid "" -"This section allows you to define password requirements for the local user " -"accounts." -msgstr "" -"In diesem Bereich können Sie die Anforderungen an das Passwort für die " -"lokalen Benutzerkonten festlegen." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.department}``" +msgstr "``#{article.created_by.department}``" -#: ../settings/security/password.rst:9 -msgid "" -"Zammad does **not** allow you to change your LDAP password, instead, it will " -"set a password in its local database which might confuse your users. This " -"might be addressed in the future by `#1169 `_." -msgstr "" -"Zammad erlaubt das Ändern des LDAP-Passworts **nicht**. Stattdessen wird ein " -"Passwort in der lokalen Datenbank gesetzt, was zu Verwirrung führen könnte. " -"Dies kann zukünftig durch `#1169 `_ behoben." +#: ../misc/variables/article.rst:1 +msgid "``Sales`` or empty if not set in user object" +msgstr "``Sales`` oder leer wenn nicht am Benutzerobjekt gesetzt" -#: ../settings/security/password.rst:14 -msgid "**Exception for admins**" -msgstr "**Ausnahme für Administratoren**" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Email" +msgstr "Artikel > Erstellt von > Email" -#: ../settings/security/password.rst:16 -msgid "" -"Please note that below password policies *do not* affect administrators " -"setting passwords on user accounts. While this seems strange and not safe we " -"believe that an administrator knowing an user's password is insecure as well." -msgstr "" -"Bitte beachten Sie, dass die unten aufgeführten Passwortrichtlinien *nicht* " -"das manuelle Setzen von Passwörtern für Benutzer durch Administratoren " -"betrifft. Das mag inkonsistent und seltsam wirken, aber wir sind der " -"Meinung, dass es ebenfalls nicht sicher ist, wenn ein Administrator das " -"Passwort eines Benutzers kennt." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.email}``" +msgstr "``#{article.created_by.email}``" -#: ../settings/security/password.rst:21 -msgid "The suggested workflow is either:" -msgstr "Die vorgeschlagene Vorgehensweise ist entweder:" +#: ../misc/variables/article.rst:1 +msgid "``jdoe@example.com``" +msgstr "``jdoe@example.com``" -#: ../settings/security/password.rst:23 -msgid "" -"to use third party logins to not require local passwords at all **- or -**" -msgstr "" -"Anmeldung von Drittanbietern zu verwenden, um keine lokalen Passwörter mehr " -"zu benötigen **- oder -**" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Fax" +msgstr "Artikel > Erstellt von > Fax" -#: ../settings/security/password.rst:25 -msgid "to require your *user to reset the password* upon first login." -msgstr "" -"dass Ihr Benutzer bei der ersten Anmeldung sein *Kennwort zurücksetzen* muss." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.fax}``" +msgstr "``#{article.created_by.fax}``" -#: ../settings/security/password.rst:27 -msgid "" -"This way administrators are not required to set a user's password at all!" -msgstr "" -"Auf diese Weise müssen Administratoren das Passwort eines Benutzers " -"überhaupt nicht festlegen!" +#: ../misc/variables/article.rst:1 +msgid "``+4930123456789`` or empty if not set in user object" +msgstr "``+4930123456789`` oder leer wenn nicht im Benutzerobjekt gesetzt" -#: ../settings/security/password.rst:31 -msgid "Maximum Failed Logins" -msgstr "Maximale Anzahl fehlgeschlagener Anmeldungen" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Firstname" +msgstr "Artikel > Erstellt von > Vorname" -#: ../settings/security/password.rst:33 -msgid "" -"You can choose a value between ``4`` and ``20``. This defines how often a " -"login to a user account may fail until Zammad will lock it. Your users can " -"always use the \"forgot password\" function to change their password and " -"unlock their account." -msgstr "" -"Sie können einen Wert zwischen ``4`` und ``20`` wählen. Dieser Wert legt " -"fest, wie oft eine Anmeldung bei einem Benutzerkonto fehlschlagen darf, bis " -"Zammad es sperrt. Ihre Benutzer können jederzeit die Funktion \"Passwort " -"vergessen\" verwenden, um ihr Passwort zu ändern und ihr Konto zu entsperren." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.firstname}``" +msgstr "``#{article.created_by.firstname}``" -#: ../settings/security/password.rst:38 -msgid "The default value is ``10``." -msgstr "Der Standardwert ist ``10``." +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Joe`` or empty if not set" +msgstr "``Joe`` oder leer wenn nicht gesetzt" -#: ../settings/security/password.rst:42 -msgid "Beside changing the user's password, you can also unlock accounts via" -msgstr "" -"Neben der Änderung des Benutzerkennworts können Sie Konten auch entsperren " -"über" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Lastname" +msgstr "Artikel > Erstellt von > Nachname" -#: ../settings/security/password.rst:44 -msgid ":ref:`user management list `" -msgstr ":ref:`Benutzerverwaltung `" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.lastname}``" +msgstr "``#{article.created_by.lastname}``" -#: ../settings/security/password.rst:45 -msgid ":docs:`console `" -msgstr ":docs:`Konsole `" +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +#: ../misc/variables/ticket.rst:1 +msgid "``Doe`` or empty if not set" +msgstr "``Doe`` oder leer wenn nicht gesetzt" -#: ../settings/security/password.rst:46 -msgid ":docs:`API `" -msgstr ":docs:`API `" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Login" +msgstr "Artikel > Erstellt von > Login" -#: ../settings/security/password.rst:50 -msgid "Failed logins via LDAP no longer lock accounts." -msgstr "Fehlgeschlagene Anmeldungen über LDAP sperren keine Konten mehr." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.login}``" +msgstr "``#{article.created_by.login}``" -#: ../settings/security/password.rst:53 -msgid "2 Lower Case And 2 Upper Case Characters" -msgstr "2 Kleinbuchstaben und 2 Großbuchstaben" +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +#: ../misc/variables/ticket.rst:1 +msgid "``jdoe``" +msgstr "``jdoe``" -#: ../settings/security/password.rst:55 -msgid "" -"You can add complexity to passwords by enforcing at least 2 upper and lower " -"case characters." -msgstr "" -"Sie können die Komplexität von Passwörtern erhöhen, indem Sie mindestens 2 " -"Groß- und Kleinbuchstaben vorschreiben." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Mobile" +msgstr "Artikel > Erstellt von > Mobil" -#: ../settings/security/password.rst:58 ../settings/security/password.rst:83 -msgid "The default value is ``no``." -msgstr "Der Standardwert ist ``nein``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.mobile}``" +msgstr "``#{article.created_by.mobile}``" -#: ../settings/security/password.rst:62 -msgid "Minimum Length" -msgstr "Minimale Länge" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Note" +msgstr "Artikel > Erstellt von > Notiz" -#: ../settings/security/password.rst:64 -msgid "" -"This defines the minimum password length required for users to provide (from " -"``4`` to ``20``)." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.note}``" +msgstr "``#{article.created_by.note}``" + +#: ../misc/variables/article.rst:1 +msgid "``Some note about user`` or empty if not set in user object" msgstr "" -"Dies definiert die minimale Passwortlänge, die Benutzer einhalten müssen " -"(von ``4`` bis ``20``)." +"``Eine Notiz über den Benutzer`` oder leer wenn nicht am Benutzerobjekt " +"gesetzt" -#: ../settings/security/password.rst:67 -msgid "The default value is ``6``." -msgstr "Der Standardwert ist ``6``." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Phone" +msgstr "Artikel > Erstellt von > Telefon" -#: ../settings/security/password.rst:71 -msgid "Digit Required" -msgstr "Ziffer benötigt" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.phone}``" +msgstr "``#{article.created_by.phone}``" -#: ../settings/security/password.rst:73 -msgid "This enforces your users to use at least one digit within the password." -msgstr "" -"Dadurch müssen Ihre Benutzer mindestens eine Ziffer im Passwort verwenden." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > VIP" +msgstr "Artikel > Erstellt von > VIP" -#: ../settings/security/password.rst:75 -msgid "The default value is ``yes``." -msgstr "Der Standardwert ist ``Ja``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.vip}``" +msgstr "``#{article.created_by.vip}``" -#: ../settings/security/password.rst:78 -msgid "Special Character Required" -msgstr "Sonderzeichen erforderlich" +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +msgid "``true`` or ``false``" +msgstr "``true`` oder ``false``" -#: ../settings/security/password.rst:80 -msgid "" -"This setting allows you to improve your password quality even more by " -"enforcing the password to contain at least one special character." -msgstr "" -"Mit dieser Einstellung können Sie die Stärke Ihres Passworts noch weiter " -"erhöhen, indem das Passwort mindestens ein Sonderzeichen enthalten muss." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Web" +msgstr "Artikel > Erstellt von > Web" -#: ../settings/security/ssl-certificates.rst:2 -msgid "SSL Certificates" -msgstr "SSL-Zertifikate" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.web}``" +msgstr "``#{article.created_by.web}``" -#: ../settings/security/ssl-certificates.rst:7 -msgid "" -"Zammad offers the possibility to upload custom certificates and custom " -"Certificate Authority (CA) certificates. This can be useful if you want to " -"connect Zammad the secure way to other systems which are using custom " -"certificates." -msgstr "" -"Zammad bietet die Möglichkeit, benutzerdefinierte Zertifikate und " -"benutzerdefinierte Zertifikate der Zertifizierungsstelle (Certificate " -"Authority, CA) hochzuladen. Dies kann nützlich sein, wenn Sie Zammad auf " -"sichere Weise mit anderen Systemen verbinden wollen, die eigene Zertifikate " -"verwenden." +#: ../misc/variables/article.rst:1 +msgid "``https://zammad.com`` or empty if not set in user object" +msgstr "``https://zammad.com`` oder leer wenn nicht im Benutzerobjekt gesetzt" -#: ../settings/security/ssl-certificates.rst:12 -msgid "" -"An example usecase might be: You have an internal LDAP server that is not " -"accessible from the internet, and you want a SSL-encrypted connection, using " -"a custom certificate." -msgstr "" -"Ein Beispielanwendungsfall könnte sein: Sie haben einen internen LDAP-" -"Server, der nicht über das Internet zugänglich ist und Sie möchten zu diesem " -"eine SSL-verschlüsselte Verbindung mit einem benutzerdefinierten Zertifikat " -"herstellen." +#: ../misc/variables/article.rst:1 +msgid "Article > Created" +msgstr "Artikel > Erstellt" -#: ../settings/security/ssl-certificates.rst:19 -msgid "" -"You should have an existing custom certificate file and/or a custom CA " -"certificate file, which you want to add to Zammad. As filetype ``.crt`` is " -"supported and the certificate format has to be PEM (Base64 ASCII)." -msgstr "" -"Sie sollten eine bestehende Zertifikatsdatei und/oder eine CA-" -"Zertifikatsdatei haben, die Sie zu Zammad hinzufügen möchten. Als Dateityp " -"wird ``.crt`` unterstützt und das Zertifikatsformat muss PEM (Base64 ASCII) " -"sein." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_at}``" +msgstr "``#{article.created_at}``" -#: ../settings/security/ssl-certificates.rst:25 -msgid "" -"When you import a custom CA certificate, all certificates generated with " -"this are trusted. This can be useful if you have more than one system/" -"certificate you want to connect to and the certificates are issued from the " -"same custom CA." -msgstr "" -"Wenn Sie ein eigenes CA-Zertifikat importieren, werden alle mit diesem " -"Zertifikat erzeugten Zertifikate als vertrauenswürdig eingestuft. Dies kann " -"nützlich sein, wenn Sie mehr als ein System/Zertifikat haben, mit dem Sie " -"sich verbinden möchten, und die Zertifikate von derselben CA ausgestellt " -"wurden." +#: ../misc/variables/article.rst:1 +msgid "``2019-10-08 15:24:47 UTC``" +msgstr "``2019-10-08 15:24:47 UTC``" -#: ../settings/security/ssl-certificates.rst:31 -msgid "Add a Certificate" -msgstr "Zertifikat hinzufügen" +#: ../misc/variables/article.rst:1 +msgid "Article > From" +msgstr "Artikel > Von" -#: ../settings/security/ssl-certificates.rst:33 +#: ../misc/variables/article.rst:1 +msgid "``#{article.from}``" +msgstr "``#{article.from}``" + +#: ../misc/variables/article.rst:1 msgid "" -"To add a custom certificate or a custom CA certificate, head over to the " -"Admin panel > Settings > Security > SSL Certificates. Here you can find a " -"\"Add SSL Certificate\" button. In the dialog you can either select a " -"certificate file or paste the content of the certificate:" +"``Joe Doe `` may differ, depends on ``FROM`` of send mail" msgstr "" -"Um ein benutzerdefiniertes Zertifikat oder ein benutzerdefiniertes CA-" -"Zertifikat hinzuzufügen, gehen Sie zu Admin Panel > Einstellungen > " -"Sicherheit > SSL-Zertifikate. Hier finden Sie eine Schaltfläche \"SSL-" -"Zertifikat hinzufügen\". In dem Dialog können Sie entweder eine " -"Zertifikatsdatei auswählen oder den Inhalt des Zertifikats einfügen:" +"``Joe Doe `` kann abweichen, kommt auf ``FROM`` der " +"gesendeten E-Mail an" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate adding dialog" -msgstr "Screenshot zeigt Dialog zum Hinzufügen von Zertifikaten" +#: ../misc/variables/article.rst:1 +msgid "Article > Sender > Name" +msgstr "Artikel > Sender > Name" -#: ../settings/security/ssl-certificates.rst:43 -msgid "" -"After selecting a file or pasting the content of the certificate, click on " -"the \"Add\" button to finally upload it to Zammad. Then, the certificates " -"are immediately effective, no restart or similar required." -msgstr "" -"Nachdem Sie eine Datei ausgewählt oder den Inhalt des Zertifikats eingefügt " -"haben, klicken Sie auf die Schaltfläche \"Hinzufügen\", um es schließlich in " -"Zammad hochzuladen. Danach sind die Zertifikate sofort wirksam, es ist kein " -"Neustart oder ähnliches erforderlich." +#: ../misc/variables/article.rst:1 +msgid "``#{article.sender.name}``" +msgstr "``#{article.sender.name}``" -#: ../settings/security/ssl-certificates.rst:49 -msgid "" -"Please note that only single certificate files are supported. That means if " -"you want to import a certificate / CA certificate, it must contain **only " -"one** certificate." -msgstr "" -"Bitte beachten Sie, dass nur Dateien mit einzelne Zertifikaten unterstützt " -"werden. Das heißt, wenn Sie ein Zertifikat / CA-Zertifikat importieren " -"möchten, darf es **nur ein** Zertifikat enthalten." +#: ../misc/variables/article.rst:1 +msgid "``Customer``, ``Agent`` or ``System``" +msgstr "``Customer``, ``Agent`` oder ``System``" -#: ../settings/security/ssl-certificates.rst:54 -msgid "Certificate Overview" -msgstr "Zertifikat Übersicht" +#: ../misc/variables/article.rst:1 +msgid "Article > Subject" +msgstr "Artikel > Betreff" -#: ../settings/security/ssl-certificates.rst:56 -msgid "" -"After you added a certificate, you can see a table with information for each " -"added certificate:" -msgstr "" -"Nachdem Sie ein Zertifikat hinzugefügt haben, sehen Sie eine Tabelle mit " -"Informationen zu jedem hinzugefügten Zertifikat:" +#: ../misc/variables/article.rst:1 +msgid "``#{article.subject}``" +msgstr "``#{article.subject}``" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing table of added certificates" -msgstr "Screenshot zeigt Tabelle mit den hinzugefügten Zertifikaten" +#: ../misc/variables/article.rst:1 +msgid "``My amazing subject``" +msgstr "``Mein tolles Betreff``" -#: ../settings/security/ssl-certificates.rst:64 -msgid "" -"Here you can download the certificate or delete it, if you don't need it " -"anymore." -msgstr "" -"Hier können Sie das Zertifikat herunterladen oder es löschen, wenn Sie es " -"nicht mehr benötigen." +#: ../misc/variables/article.rst:1 +msgid "Article > Text" +msgstr "Artikel > Text" -#: ../settings/security/ssl-certificates.rst:68 -msgid "Deleting Certificates" -msgstr "Löschen von Zertifikaten" +#: ../misc/variables/article.rst:1 +msgid "``#{article.body}``" +msgstr "``#{article.body}``" -#: ../settings/security/ssl-certificates.rst:70 -msgid "" -"If you want to delete a specific certificate, you can do it by clicking on " -"the menu in the actions column and selecting delete:" -msgstr "" -"Wenn Sie ein bestimmtes Zertifikat löschen möchten, können Sie dies tun, " -"indem Sie auf das Menü in der Spalte \"Aktionen\" klicken und \"Löschen\" " -"auswählen:" +#: ../misc/variables/article.rst:1 +msgid "``Test`` without formatting (plain)" +msgstr "``Test`` ohne Formatierung" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate deletion button" -msgstr "Screenshot zeigt Schaltfläche zum Löschen von Zertifikaten" +#: ../misc/variables/article.rst:1 +msgid "Article > TicketID" +msgstr "Artikel > Ticket-ID" -#: ../settings/security/ssl-certificates.rst:79 -msgid "Downloading Certificates" -msgstr "Herunterladen von Zertifikaten" +#: ../misc/variables/article.rst:1 +msgid "``#{article.ticket_id}``" +msgstr "``#{article.ticket_id}``" -#: ../settings/security/ssl-certificates.rst:81 -msgid "" -"If you want to download your certificates, you can do this as well via " -"corresponding action buttons." -msgstr "" -"Wenn Sie Ihre Zertifikate herunterladen möchten, können Sie dies ebenfalls " -"über entsprechende Aktionsschaltflächen tun." +#: ../misc/variables/article.rst:1 +msgid "``1`` (not ticket number)" +msgstr "``1`` (nicht Ticketnummer)" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate download button" -msgstr "Screenshot zeigt Schaltfläche zum Herunterladen des Zertifikats" +#: ../misc/variables/article.rst:1 +msgid "Article > To" +msgstr "Artikel > An" -#: ../settings/security/third-party.rst:13 -msgid "Login Providers" -msgstr "Login-Anbieter" +#: ../misc/variables/article.rst:1 +msgid "``#{article.to}``" +msgstr "``#{article.to}``" -#: ../settings/security/third-party.rst:2 -msgid "Third-Party Applications" -msgstr "Anwendungen von Drittanbietern" +#: ../misc/variables/article.rst:1 +msgid "``helpdesk@example.com``" +msgstr "``helpdesk@example.com``" -#: ../settings/security/third-party.rst:4 -msgid "" -"Third party authentication is a great way to help your users to login to " -"Zammad more easily. If the account is yet unknown, Zammad will create a new " -"user automatically, without the user needed to interact (e.g. type in his " -"name). Another big advantage of this feature is that your user doesn't need " -"to remember another password." -msgstr "" -"Die Authentifizierung von Drittanbietern ist eine gute Möglichkeit, Ihren " -"Benutzern die Anmeldung bei Zammad zu erleichtern. Wenn das Benutzerkonto " -"noch nicht bekannt ist, erstellt Zammad automatisch einen neuen Benutzer, " -"ohne dass der Benutzer etwas unternehmen muss (z.B. seinen Namen eingeben). " -"Ein weiterer großer Vorteil dieser Funktion ist, dass der Benutzer sich kein " -"zusätzliches Passwort merken muss." +#: ../misc/variables/article.rst:1 +msgid "Article > Type > Name" +msgstr "Artikel > Typ > Name" -#: ../settings/security/third-party.rst:10 +#: ../misc/variables/article.rst:1 +msgid "``#{article.type.name}``" +msgstr "``#{article.type.name}``" + +#: ../misc/variables/article.rst:1 msgid "" -"You can deactivate logging in via :ref:`security_password_login` if any of " -"the mentioned authentication providers are enabled in your instance." +"``email`` (`list of article types `_)" msgstr "" -"Sie können das Einloggen mittels :ref:`security_password_login` " -"deaktivieren, wenn einer der genannten Authentifizierungsanbieter in Ihrer " -"Instanz aktiviert ist." +"``email`` (`Liste der Artikeltypen `_)" -#: ../settings/security/third-party.rst:27 -msgid "" -"We're currently missing documentation for the following login providers:" -msgstr "Aktuell fehlt die Dokumentation für die folgenden Login-Provider:" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Address" +msgstr "Artikel > Aktualisiert von > Adresse" -#: ../settings/security/third-party.rst:29 -msgid "LinkedIn" -msgstr "LinkedIn" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.address}``" +msgstr "``#{article.updated_by.address}``" -#: ../settings/security/third-party.rst:30 -msgid "Weibo" -msgstr "Weibo" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Department" +msgstr "Artikel > Aktualisiert von > Abteilung" -#: ../settings/security/third-party.rst:35 -msgid "Automatic Account Link on Initial Logon" -msgstr "Automatische Kontoverbindung bei der Erstanmeldung" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.department}``" +msgstr "``#{article.updated_by.department}``" -#: ../settings/security/third-party.rst:37 -msgid "" -"In general there's two possible options for Zammad on how to deal with " -"already known users as they try to authenticate against a third-party " -"application. By default, Zammad will not automatically link \"unknown\" " -"authentication providers to existing accounts." -msgstr "" -"In Zammad gibt es zwei Möglichkeiten, wie mit bereits bekannten Benutzern " -"umgegangen werden kann, wenn eine Authentifizierung über eine " -"Drittanbieteranwendung erfolgt. Standardmäßig verknüpft Zammad " -"\"unbekannte\" Authentifizierungsanbieter nicht automatisch mit bestehenden " -"Konten." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Email" +msgstr "Artikel > Aktualisiert von > Email" -#: ../settings/security/third-party.rst:42 -msgid "" -"This means that the user has to manually link authentication providers to " -"their accounts (for more about this :user-docs:`consult the user " -"documentation `)." -msgstr "" -"Dies bedeutet, dass der Benutzer die Authentifizierungsanbieter manuell mit " -"seinen Konten verknüpfen muss (weitere Informationen hierzu finden Sie in " -"der :user-docs:`Benutzerdokumentation `)." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.email}``" +msgstr "``#{article.updated_by.email}``" -#: ../settings/security/third-party.rst:46 -msgid "" -"Sometimes this doesn't come in handy as this also means you'll receive error " -"messages about \"email address being in use already\" for (yet) unknown " -"third-party authentication methods." -msgstr "" -"Das ist nicht immer hilfreich, da Sie dann auch Fehlermeldungen über " -"\"bereits verwendete E-Mail-Adressen\" für (noch) unbekannte " -"Authentifizierungsmethoden von Drittanbietern erhalten." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Fax" +msgstr "Artikel > Aktualisiert von > Fax" -#: ../settings/security/third-party.rst:50 -msgid "" -"If you want to allow your users to always be able to log in, no matter what, " -"you may want to enable ``Automatic account link on initial logon``." -msgstr "" -"Wenn Sie es Ihren Benutzern ermöglichen wollen, sich immer anzumelden, " -"sollten Sie ``Automatische Kontoverbindung bei der Erstanmeldung`` " -"aktivieren." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.fax}``" +msgstr "``#{article.updated_by.fax}``" -#: ../settings/security/third-party.rst:None -msgid "" -"Screenshot highlighting the \"Automatic account link on initial logon\"\n" -"setting" -msgstr "" -"Screenshot mit Hervorhebung der Einstellung \"Automatische Kontoverbindung " -"bei der Erstanmeldung\"" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Firstname" +msgstr "Artikel > Aktualisiert von > Vorname" -#: ../settings/security/third-party.rst:60 -msgid "Automatic Account Linking Notification" -msgstr "Automatische Benachrichtigung beim Verknüpfen von Accounts" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.firstname}``" +msgstr "``#{article.updated_by.firstname}``" -#: ../settings/security/third-party.rst:64 -msgid "" -"To improve security and your users awareness, you can enable Zammad to " -"notify your users when a new third-party application has been linked to " -"their account." -msgstr "" -"Um die Sicherheit zu verbessern können Sie Ihre Nutzer durch Zammad " -"benachrichtigen lassen, wenn eine neue Drittanbieteranwendung mit ihrem " -"Konto verknüpft wurde." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Lastname" +msgstr "Artikel > Aktualisiert von > Nachname" -#: ../settings/security/third-party.rst:68 -msgid "" -"This notification is sent out once per third-party application. Zammad does " -"also mention the method used, e.g.: ``Microsoft``." -msgstr "" -"Diese Benachrichtigung wird einmal pro Drittanwendung verschickt. Darin " -"enthalten ist auch die verwendete Methode, z.B.: ``Microsoft``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.lastname}``" +msgstr "``#{article.updated_by.lastname}``" -#: ../settings/security/third-party.rst:71 -msgid "By default this setting is not active (set to ``no``)." -msgstr "" -"Standardmäßig ist diese Einstellung nicht aktiv (auf ``nein`` gesetzt)." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Login" +msgstr "Artikel > Aktualisiert von > Login" -#: ../settings/security/third-party.rst:0 -msgid "" -"Screenshot showing sample notification mail after initial\n" -"third-party linking" -msgstr "" -"Screenshot mit Beispiel einer Benachrichtigungsmail nach der ersten " -"Verknüpfung mit Drittanbieter-Login" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.login}``" +msgstr "``#{article.updated_by.login}``" -#: ../settings/security/third-party.rst:85 -msgid "" -"This notification is only sent if the account in question already exists. If " -"the login via the third-party also creates the missing account, the " -"notification will be skipped." -msgstr "" -"Diese Benachrichtigung wird nur gesendet, wenn das betreffende Konto bereits " -"existiert. Wenn die Anmeldung über den Drittanbieter auch das fehlende Konto " -"erstellt, wird die Benachrichtigung übersprungen." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Mobile" +msgstr "Artikel > Aktualisiert von > Mobil" -#: ../settings/security/third-party.rst:89 -msgid "This means it only affects:" -msgstr "Dies bedeutet, dass es nur Auswirkungen hat auf:" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.mobile}``" +msgstr "``#{article.updated_by.mobile}``" -#: ../settings/security/third-party.rst:91 -msgid "manual account linking within the third-party page of the users profile" -msgstr "" -"manuelle Verknüpfung des Benutzerprofils mit einem Konto auf der " -"Drittanbieterseite" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Note" +msgstr "Artikel > Aktualisiert von > Notiz" -#: ../settings/security/third-party.rst:92 -msgid "" -"logging into an existing local account by utilizing the *automatic account " -"link on initial logon* functionality" -msgstr "" -"Einloggen in ein bestehendes lokales Konto durch Nutzung der Funktion " -"*Automatische Kontoverbindung bei der Erstanmeldung*." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.note}``" +msgstr "``#{article.updated_by.note}``" -#: ../settings/security/third-party.rst:None -msgid "" -"Screenshot showing the \"automatic account linking notification\"\n" -"setting" -msgstr "" -"Screenshot mit der Einstellung \"Automatische Kontoverbindung bei der " -"Erstanmeldung\"" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Phone" +msgstr "Artikel > Aktualisiert von > Telefon" -#: ../settings/security/third-party.rst:100 -msgid "No User Creation on Logon" -msgstr "Keine Erstellung von Benutzern bei der Anmeldung" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.phone}``" +msgstr "``#{article.updated_by.phone}``" -#: ../settings/security/third-party.rst:102 -msgid "" -"By default, Zammad will create a new user account if the user logs in via a " -"third-party application and the account doesn't exist yet." -msgstr "" -"Standardmäßig erstellt Zammad ein neues Benutzerkonto, wenn sich der " -"Benutzer über eine Drittanbieteranwendung anmeldet und das Konto noch nicht " -"existiert." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > VIP" +msgstr "Artikel > Aktualisiert von > VIP" -#: ../settings/security/third-party.rst:105 -msgid "" -"If you want to prevent Zammad from creating new accounts on logon, you can " -"disable this feature by setting ``No user creation on logon`` to ``yes``." -msgstr "" -"Wenn Sie verhindern wollen, dass Zammad bei der Anmeldung neue Konten " -"anlegt, können Sie diese Funktion deaktivieren, indem Sie ``Keine Erstellung " -"von Benutzern bei der Anmeldung`` auf ``ja`` setzen." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.vip}``" +msgstr "``#{article.updated_by.vip}``" -#: ../settings/security/third-party.rst:None -msgid "Screenshot showing the \"no user creation on logon\" setting" -msgstr "" -"Screenshot zeigt die Einstellung \"keine Erstellung von Benutzern bei der " -"Anmeldung\"" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Web" +msgstr "Artikel > Aktualisiert von > Web" -#: ../settings/security/third-party/facebook.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via Facebook To do " -"so, you need to follow these steps:" -msgstr "" -"Es ist möglich, eine Anmeldung über Facebook zu erstellen. Dazu müssen Sie " -"die folgenden Schritte ausführen:" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.web}``" +msgstr "``#{article.updated_by.web}``" -#: ../settings/security/third-party/facebook.rst:9 -msgid "Register Facebook App" -msgstr "Facebook-App registrieren" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated" +msgstr "Artikel > Aktualisiert" -#: ../settings/security/third-party/facebook.rst:11 -msgid "" -"Visit [https://developers.facebook.com/apps/] and click on \"Add a new App\"" -msgstr "" -"Besuchen Sie [https://developers.facebook.com/apps/] und klicken Sie auf " -"\"Eine neue App hinzufügen\"" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_at}``" +msgstr "``#{article.updated_at}``" -#: ../settings/security/third-party/facebook.rst:None -msgid "initial page" -msgstr "Startseite" +#: ../misc/variables/article.rst:1 +msgid "Article > Visibility" +msgstr "Artikel > Sichtbarkeit" -#: ../settings/security/third-party/facebook.rst:17 -msgid "After that enter the app settings" -msgstr "Geben Sie danach die Einstellungen der App ein" +#: ../misc/variables/article.rst:1 +msgid "``#{article.internal}``" +msgstr "``#{article.internal}``" -#: ../settings/security/third-party/facebook.rst:None -msgid "Create App" -msgstr "App erstellen" +#: ../misc/variables/article.rst:1 +msgid "``false`` or ``true`` (false if not internal)" +msgstr "``false`` oder ``true`` (false wenn nicht intern)" -#: ../settings/security/third-party/facebook.rst:22 -msgid "Navigate to \"Settings\" and fill in this infromation" -msgstr "" -"Navigieren Sie zu \"Einstellungen\" und geben Sie diese Informationen ein" +#: ../misc/variables/article.rst:1 +msgid "Article Text as HTML (not referenced)" +msgstr "Artikel-Text als HTML (nicht referenziert)" -#: ../settings/security/third-party/facebook.rst:None -msgid "App Settings" -msgstr "App-Einstellungen" +#: ../misc/variables/article.rst:1 +msgid "``#{article.body_as_html}``" +msgstr "``#{article.body_as_html}``" -#: ../settings/security/third-party/facebook.rst:27 -msgid "Navigate to app review and Check \"Make [appname] public?\"" -msgstr "" -"Navigieren Sie zur App-Prüfung und setzen Sie einen Haken bei \"[Appname] " -"öffentlich machen?\"" +#: ../misc/variables/article.rst:1 +msgid "``Test`` with formatting" +msgstr "``Test`` mit Formatierung" -#: ../settings/security/third-party/facebook.rst:None -msgid "App Review" -msgstr "App-Prüfung" +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "Ticket > Article#" +msgstr "Ticket > Artikel#" -#: ../settings/security/third-party/facebook.rst:35 -msgid "Configure Zammad as Facebook App" -msgstr "Zammad als Facebook-App konfigurieren" +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "``#{ticket.article_count}``" +msgstr "``#{ticket.article_count}``" -#: ../settings/security/third-party/facebook.rst:37 -msgid "" -"Navigate to \"Admin -> Security -> Third Party Applications\" and enter the " -"App ID and the App Secret. You can find this Key in the Dashbard of your " -"Facebok app." -msgstr "" -"Navigieren Sie zu \"Einstellungen > Sicherheit > Anwendungen von " -"Drittanbietern\" und geben Sie die App-ID und das App-Secret ein. Sie finden " -"die beiden Werte im Dashbard Ihrer Facebok-App." +#: ../misc/variables/article.rst:1 +msgid "``1`` number of ticket articles" +msgstr "``1`` Anzahl der Ticket-Artikel" -#: ../settings/security/third-party/facebook.rst:None -msgid "Zammad Configuration" -msgstr "Zammad Konfiguration" +#: ../misc/variables/config.rst:2 +msgid "Config" +msgstr "Konfiguration" -#: ../settings/security/third-party/facebook.rst:44 -#: ../settings/security/third-party/github.rst:43 -#: ../settings/security/third-party/gitlab.rst:46 +#: ../misc/variables/config.rst:6 msgid "" -"Now you can link accounts via \"Avatar -> Profile -> Link Accounts\" or " -"login via Zammad login page." +"Below you'll find config related variables. These hold useful configuration " +"information that you can use within e.g. triggers to show necessary " +"information to your customer." msgstr "" -"Jetzt können Sie Konten über \"Avatar > Profil > Verknüpfte Konten\" " -"verknüpfen oder sich über die Zammad-Login-Seite anmelden." - -#: ../settings/security/third-party/github.rst:2 -#: ../system/integrations/github.rst:2 -msgid "GitHub" -msgstr "GitHub" +"Unten finden Sie konfigurationsbezogene Variablen. Diese beinhalten " +"nützliche Informationen zur Konfigurationen die in z.B. Triggern zum " +"Anzeigen notwendiger Informationen für die Kunden genutzt werden können." -#: ../settings/security/third-party/github.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via GitHub. To " -"activate the quick login you need to enable OAuth for GitHub." -msgstr "" -"Es ist möglich, eine Anmeldung über GitHub zu erstellen. Um diese zu " -"aktivieren, müssen Sie OAuth für GitHub aktivieren." +#: ../misc/variables/config.rst:11 +msgid "Config Variables" +msgstr "Konfigurations-Variablen" -#: ../settings/security/third-party/github.rst:8 -msgid "Register GitHub App" -msgstr "GitHub-App registrieren" +#: ../misc/variables/config.rst:1 +msgid "Config > Fully Qualified Domain Name" +msgstr "Konfiguration > Vollständig qualifizierter Domänenname" -#: ../settings/security/third-party/github.rst:10 -msgid "" -"Visit https://www.github.com/settings/applications/new and enter the app " -"settings. As callback URL enter \"https://zammad_host/auth/github/callback\" " -"where zammad_host has to be replaced with your Zammad FQDN" -msgstr "" -"Besuchen Sie https://www.github.com/settings/applications/new und geben Sie " -"die App-Einstellungen ein. Geben Sie als Callback-URL \"https://zammad_host/" -"auth/github/callback\" ein, wobei zammad_host durch Ihren Zammad-FQDN " -"ersetzt werden muss" +#: ../misc/variables/config.rst:1 +msgid "``#{config.fqdn}``" +msgstr "``#{config.fqdn}``" -#: ../settings/security/third-party/github.rst:None -msgid "Register OAuth app on www.github.com" -msgstr "OAuth-App auf www.github.com registrieren" +#: ../misc/variables/config.rst:1 +msgid "``zammad.example.com``" +msgstr "``zammad.example.com``" -#: ../settings/security/third-party/github.rst:19 -msgid "Configure Zammad as GitHub App" -msgstr "Zammad als GitHub-Anwendung konfigurieren" +#: ../misc/variables/config.rst:1 +msgid "Config > HTTP type" +msgstr "Konfiguration > HTTP-Typ" -#: ../settings/security/third-party/github.rst:21 -msgid "" -"Enter the \"APP ID\" and the \"APP SECRET\" from the GitHub OAUTH " -"Applications Dashboard" -msgstr "" -"Geben Sie die \"APP ID\" und das \"APP SECRET\" aus dem GitHub OAUTH " -"Applications Dashboard ein" +#: ../misc/variables/config.rst:1 +msgid "``#{config.http_type}``" +msgstr "``#{config.http_type}``" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub config in Zammad admin interface" -msgstr "GitHub-Konfiguration im Zammad Admin-Bereich" +#: ../misc/variables/config.rst:1 +msgid "``https`` or ``http``" +msgstr "``https`` oder ``http``" -#: ../settings/security/third-party/github.rst:28 -msgid "" -"After you configured the GitHub credentials and activated the login method, " -"you should see a new icon on the login page." -msgstr "" -"Nachdem Sie die GitHub-Zugangsdaten konfiguriert und die Anmeldemethode " -"aktiviert haben, sollten Sie ein neues Symbol auf der Anmeldeseite sehen." +#: ../misc/variables/config.rst:1 +msgid "Config > Organization" +msgstr "Konfiguration > Organisation" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub logo on login page" -msgstr "GitHub-Logo auf der Anmeldeseite" +#: ../misc/variables/config.rst:1 +msgid "``#{config.organization}``" +msgstr "``#{config.organization}``" -#: ../settings/security/third-party/github.rst:34 +#: ../misc/variables/config.rst:1 msgid "" -"If you click on the icon you will be redirected to GitHub and see something " -"similar to this:" +"``Zammad GmbH`` value set in `Branding `_" msgstr "" -"Wenn Sie auf das Symbol klicken, werden Sie zu GitHub weitergeleitet und " -"sehen einen Dialog ähnlich dem folgenden:" - -#: ../settings/security/third-party/github.rst:None -msgid "GitHub oauth page" -msgstr "GitHub oauth Seite" +"``Zammad GmbH`` Wert wird unter `Branding `_ gesetzt" -#: ../settings/security/third-party/github.rst:40 -#: ../settings/security/third-party/gitlab.rst:42 -msgid "" -"When you grant the access you will be redirected to your Zammad instance and " -"logged in as a customer." -msgstr "" -"Wenn Sie den Zugang gewähren, werden Sie zu Ihrer Zammad-Instanz " -"weitergeleitet und eingeloggt." +#: ../misc/variables/config.rst:1 +msgid "Config > Product Name" +msgstr "Konfiguration > Produktname" -#: ../settings/security/third-party/gitlab.rst:2 -msgid "Gitlab" -msgstr "Gitlab" +#: ../misc/variables/config.rst:1 +msgid "``#{config.product_name}``" +msgstr "``#{config.product_name}``" -#: ../settings/security/third-party/gitlab.rst:4 +#: ../misc/variables/config.rst:1 msgid "" -"It is possible to create a quick login for your helpdesk via Gitlab. To " -"activate the quick login you need to enable OAuth for Gitlab." +"``Helpdesk`` value set in `Branding `_" msgstr "" -"Es ist möglich, eine Anmeldung über Gitlab zu erstellen. Um diese zu " -"aktivieren, müssen Sie OAuth für Gitlab aktivieren." +"``Helpdesk`` Wert wird unter `Branding `_ gesetzt" -#: ../settings/security/third-party/gitlab.rst:8 -msgid "Register Gitlab App" -msgstr "Gitlab-App registrieren" +#: ../misc/variables/config.rst:1 +msgid "Config > SystemID" +msgstr "Konfiguration > System-ID" -#: ../settings/security/third-party/gitlab.rst:10 -msgid "To register an app in Gitlab open your profile and select applications." -msgstr "" -"Um eine Anwendung in Gitlab zu registrieren, öffnen Sie Ihr Profil und " -"wählen Sie Anwendungen." +#: ../misc/variables/config.rst:1 +msgid "``#{config.system_id}``" +msgstr "``#{config.system_id}``" -#: ../settings/security/third-party/gitlab.rst:12 -msgid "" -"As callback URL enter \"https://zammad-fqdn/auth/gitlab/callback\" where " -"zammad-fqdn has to be replaced with your Zammad FQDN" -msgstr "" -"Als Callback-URL geben Sie \"https://zammad-fqdn/auth/gitlab/callback\" ein, " -"wobei zammad-fqdn durch Ihren Zammad-FQDN ersetzt werden muss" +#: ../misc/variables/config.rst:1 +msgid "``31`` (value between 1 and 99)" +msgstr "``31`` (Wert zwischen 1 und 99)" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Register OAuth app on gitlab instance" -msgstr "OAuth-Anwendung auf Gitlab-Instanz registrieren" +#: ../misc/variables/config.rst:1 +msgid "Config > Ticket Hook" +msgstr "Konfiguration > Ticket-Hook" -#: ../settings/security/third-party/gitlab.rst:18 -msgid "Just select *read_user* under scopes as in the screenshot and save it." -msgstr "" -"Wählen Sie nur *read_user* unter scopes wie im Screenshot und speichern Sie." +#: ../misc/variables/config.rst:1 +msgid "``#{config.ticket_hook}``" +msgstr "``#{config.ticket_hook}``" -#: ../settings/security/third-party/gitlab.rst:21 -msgid "Configure Zammad as Gitlab App" -msgstr "Zammad als Gitlab-Anwendung konfigurieren" +#: ../misc/variables/config.rst:1 +msgid "``Ticket#``" +msgstr "``Ticket#``" -#: ../settings/security/third-party/gitlab.rst:23 +#: ../misc/variables/current-user.rst:2 +msgid "Current User" +msgstr "Aktueller Benutzer" + +#: ../misc/variables/current-user.rst:6 msgid "" -"Enter the \"APP ID\" and the \"APP SECRET\" from the Gitlab OAUTH " -"Applications Dashboard and your Gitlab-URL in the \"SITE\" field." +"Current user variables always return values of the current user that caused " +"e.g. a trigger to run." msgstr "" -"Geben Sie die \"APP ID\" und das \"APP SECRET\" aus dem Gitlab OAUTH " -"Applications Dashboard und Ihre Gitlab-URL in das Feld \"SITE\" ein." - -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab config in Zammad admin interface" -msgstr "Gitlab-Konfiguration in der Zammad-Verwaltungsoberfläche" +"Variablen für den aktuellen Benutzer geben immer die Werte zurück, die den z." +"B. Trigger ausgelöst haben." -#: ../settings/security/third-party/gitlab.rst:30 +#: ../misc/variables/current-user.rst:8 msgid "" -"After you configured the Gitlab credentials and activated the login method, " -"you should see a new icon on the login page." +"Due to the above fact, these variables are often not (yet) set or available " +"for usage." msgstr "" -"Nachdem Sie die Gitlab-Anmeldedaten konfiguriert und die Anmeldemethode " -"aktiviert haben, sollten Sie ein neues Symbol auf der Anmeldeseite sehen." - -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab logo on login page" -msgstr "Gitlab-Logo auf der Anmeldeseite" +"Aus diesem Grund sind diese Variablen oft (noch) nicht gesetzt oder stehen " +"nicht zur Verfügung." -#: ../settings/security/third-party/gitlab.rst:36 +#: ../misc/variables/current-user.rst:10 msgid "" -"If you click on the icon you will be redirected to Gitlab and see something " -"similar to this:" +"In situations where e.g. schedulers or triggers run, this most likely is " +"nothing you want to use." msgstr "" -"Wenn Sie auf das Symbol klicken, werden Sie zu Gitlab weitergeleitet und " -"sehen einen Dialog ähnlich dem folgenden:" +"In Situationen, in denen z.B. Automatisierungen oder Trigger laufen, werden " +"Sie das höchstwahrscheinlich nicht verwenden wollen." -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab oauth page" -msgstr "Gitlab oauth Seite" +#: ../misc/variables/current-user.rst:13 +msgid "Current User Variables" +msgstr "Aktueller Benutzer-Variablen" -#: ../settings/security/third-party/google.rst:4 -msgid "" -"With some easy and fast steps, you can enable Zammad to authenticate your " -"users via Google." -msgstr "" -"In ein paar Schritten können Sie in Zammad die Authentifizierung über Google " -"aktivieren." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Address" +msgstr "Aktueller Benutzer > Adresse" -#: ../settings/security/third-party/google.rst:8 -msgid "Register a Google App" -msgstr "Eine Google-App registrieren" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.address}``" +msgstr "``#{user.address}``" -#: ../settings/security/third-party/google.rst:10 -msgid "" -"First of all, we need to create a new project - you can skip this step if " -"you already have one." -msgstr "" -"Zunächst müssen wir ein neues Projekt erstellen - Sie können diesen Schritt " -"überspringen, wenn Sie bereits ein Projekt haben." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set" +msgstr "``Irgendeine Straße 1, 12345 Berlin`` oder leer wenn nicht gesetzt" -#: ../settings/security/third-party/google.rst:15 -msgid "" -"Use this link to create a new project: https://console.cloud.google.com/" -"projectcreate" -msgstr "" -"Verwenden Sie diesen Link, um ein neues Projekt zu erstellen: https://" -"console.cloud.google.com/projectcreate" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Avatar" +msgstr "Aktueller Benutzer > Avatar" -#: ../settings/security/third-party/google.rst:18 -msgid "" -"Now expand the menu, expand \"APIs & Services\" and select \"Credentials\". " -"Go to the tab \"OAuth consent screen\" first and ensure to fill in the " -"requested information - without doing so you can't create credentials!" -msgstr "" -"Erweitern Sie nun das Menü, erweitern Sie \"APIs & Services\" und wählen Sie " -"\"Credentials\". Gehen Sie zuerst auf die Registerkarte \"OAuth consent " -"screen\" und geben Sie die erforderlichen Informationen ein - ohne diese " -"Angaben können Sie keine Anmeldung erstellen!" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.avatar(60,60)}``" +msgstr "``#{user.avatar(60,60)}``" -#: ../settings/security/third-party/google.rst:None -msgid "Creating a consent screen" -msgstr "Erstellen eines Einwilligungs-Dialogs" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "avatar picture with width and height in pixel (e.g. 60,60)" +msgstr "Avatarbild mit Breite und Höhe in Pixel (z.B. 60,60)" -#: ../settings/security/third-party/google.rst:25 -msgid "" -"After filling in and saving the consent screen information, you can go to " -"the \"Credentials\" tab and create new \"OAuth client ID\"-Credentials." -msgstr "" -"Nach dem Ausfüllen und Speichern der Informationen auf dem Einwilligungs-" -"Dialog können Sie auf die Registerkarte \"Credentials\" wechseln und neue " -"\"OAuth client ID\"-Credentials erstellen." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created at" +msgstr "Aktueller Benutzer > Erstellt am" -#: ../settings/security/third-party/google.rst:28 -msgid "" -"Fill in the necessary information as follows and replace ``zammad_host`` " -"with your FQDN:" -msgstr "" -"Geben Sie die erforderlichen Informationen wie folgt ein und ersetzen Sie " -"``zammad_host`` durch Ihren FQDN:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_at}``" +msgstr "``#{user.created_at}``" -#: ../settings/security/third-party/google.rst:31 -msgid "**Application type** ``[x] Web application``" -msgstr "**Application type** ``[x] Web application``" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC``" +msgstr "``2019-10-07 16:25:00 UTC``" -#: ../settings/security/third-party/google.rst:34 -msgid "**Authorized JavaScript origins** ``https://zammad_host/``" -msgstr "**Authorized JavaScript origins** ``https://zammad_host/``" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Address" +msgstr "Aktueller Benutzer > Erstellt von > Adresse" -#: ../settings/security/third-party/google.rst:37 -msgid "" -"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" -"callback``" -msgstr "" -"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" -"callback``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.address}``" +msgstr "``#{user.created_by.address}``" -#: ../settings/security/third-party/google.rst:None -msgid "Adding a new OAuth client ID" -msgstr "Hinzufügen einer neuen OAuth-Client-ID" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Avatar" +msgstr "Aktueller Benutzer > Erstellt von > Avatar" -#: ../settings/security/third-party/google.rst:43 -msgid "" -"After creating the credentials, go to your Zammad installation and navigate " -"to \"Admin > Security > Third Party Applications\" > Google. Enter your " -"Client ID and Client secret here." -msgstr "" -"Nachdem Sie die Zugangsdaten erstellt haben, gehen Sie zu Ihrer Zammad-" -"Installation und navigieren Sie zu \"Einstellungen > Sicherheit > " -"Anwendungen von Drittanbietern\" > Google. Geben Sie hier Ihre Client-ID und " -"Ihr Client-Secret ein." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.avatar(60,60)}``" +msgstr "``#{user.created_by.avatar(60,60)}``" -#: ../settings/security/third-party/google.rst:None -msgid "Zammad" -msgstr "Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Department" +msgstr "Aktueller Benutzer > Erstellt von > Abteilung" -#: ../settings/security/third-party/google.rst:50 -msgid "After submitting, the login via Google can be used." -msgstr "Nach dem Speichern kann der Login über Google verwendet werden." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.department}``" +msgstr "``#{user.created_by.department}``" -#: ../settings/security/third-party/microsoft.rst:2 -msgid "Microsoft" -msgstr "Microsoft" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Sales`` or empty if not set" +msgstr "``Verkauf`` oder leer wenn nicht gesetzt" -#: ../settings/security/third-party/microsoft.rst:4 -msgid "" -"Zammad's Microsoft connection allows your users with Microsoft accounts to " -"login. This works for Azure users as well and can be an alternative to :doc:" -"`/system/integrations/ldap/index`." -msgstr "" -"Die Microsoft-Andingung von Zammad ermöglicht Ihren Benutzern die Anmeldung " -"mit einem Microsoft-Konto. Dies funktioniert auch für Azure-Benutzer und " -"kann eine Alternative zu :doc:`/system/integrations/ldap/index` sein." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Email" +msgstr "Aktueller Benutzer > Erstellt von > Email" -#: ../settings/security/third-party/microsoft.rst:10 -msgid "" -"This documentation part does not cover our :doc:`📧 Microsoft 365 email " -"channel `." -msgstr "" -"Dieser Teil der Dokumentation deckt nicht unseren :doc:`📧 Microsoft 365-" -"Kanal ` ab." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.email}``" +msgstr "``#{user.created_by.email}``" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screenshot showing Microsoft login button on Zammad login screen." -msgstr "Screenshot der Microsoft-Anmeldung auf dem Anmeldedialog von Zammad." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``jdoe@customer.tld``" +msgstr "``jdoe@kunde.tld``" -#: ../settings/security/third-party/microsoft.rst:30 -#: ../settings/security/third-party/microsoft.rst:53 -msgid "Supported account types:" -msgstr "Unterstützte Konten-Typen:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Fax" +msgstr "Aktueller Benutzer > Erstellt von > Fax" -#: ../settings/security/third-party/microsoft.rst:22 -msgid "" -"Please note that Zammad only supports these account types (App dependent):" -msgstr "" -"Bitte beachten Sie, dass Zammad nur diese Kontotypen unterstützt (App-" -"abhängig):" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.fax}``" +msgstr "``#{user.created_by.fax}``" -#: ../settings/security/third-party/microsoft.rst:35 -msgid "Avatars of signing in users:" -msgstr "Avatare der angemeldeten Benutzer:" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``004930123464789`` or empty if not set" +msgstr "``004930123464789`` oder leer wenn nicht gesetzt" -#: ../settings/security/third-party/microsoft.rst:33 -msgid "" -"Zammad currently ignores user avatars. If the user is registered with e.g. " -"Gravatar, Zammad will fetch the avatar from there if enabled. See :doc:" -"`Zammad Image Service ` for more." -msgstr "" -"Zammad ignoriert derzeit Benutzeravatare. Wenn der Benutzer z.B. bei " -"Gravatar registriert ist, bezieht Zammad den Avatar von dort, falls " -"aktiviert. Siehe :doc:`Zammad Bilder Service ` für " -"mehr." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Firstname" +msgstr "Aktueller Benutzer > Erstellt von > Vorname" -#: ../settings/security/third-party/microsoft.rst:38 -msgid "Step 1 - Register a Microsoft App for Zammad" -msgstr "Schritt 1 - Registrieren einer Microsoft-App für Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.firstname}``" +msgstr "``#{user.created_by.firstname}``" -#: ../settings/security/third-party/microsoft.rst:40 -msgid "" -"Login to the `Microsoft Azure Portal `_ and " -"navigate to App registrations to create a new app. Provide the requested " -"information as follows and register your app." -msgstr "" -"Melden Sie sich im `Microsoft Azure Portal `_ an " -"und navigieren Sie zu App-Registrierungen, um eine neue App zu erstellen. " -"Geben Sie die erforderlichen Informationen wie folgt an und registrieren Sie " -"Ihre App." - -#: ../settings/security/third-party/microsoft.rst:46 -msgid "Name:" -msgstr "Name:" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``John`` or empty if not set" +msgstr "``John`` oder leer wenn nicht gesetzt" -#: ../settings/security/third-party/microsoft.rst:45 -msgid "" -"Any meaningful name fitting, this name will be displayed to users trying to " -"authenticate with this app." -msgstr "" -"Wählen Sie einen aussagekräftigen Namen. Dieser wird Benutzern angezeigt, " -"die versuchen, sich mit dieser Anwendung zu authentifizieren." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Lastname" +msgstr "Aktueller Benutzer > Erstellt von > Nachname" -#: ../settings/security/third-party/microsoft.rst:49 -msgid "Choose one of the above mentioned account types (see Limitations)." -msgstr "" -"Wählen Sie einen der oben genannten Kontotypen (siehe Einschränkungen)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.lastname}``" +msgstr "``#{user.created_by.lastname}``" -#: ../settings/security/third-party/microsoft.rst:51 -msgid "" -"The correct account type depends on your use case. If you want to use the " -"authentication internal only, choose the first option. If you're unsure, use " -"the \"Help me choose...\" link." -msgstr "" -"Der richtige Kontotyp hängt von Ihrem Anwendungsfall ab. Wenn Sie nur die " -"interne Authentifizierung verwenden möchten, wählen Sie die erste Option. " -"Wenn Sie unsicher sind, verwenden Sie den Link \"Hilfe bei der Auswahl...\"." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Login" +msgstr "Aktueller Benutzer > Erstellt von > Login" -#: ../settings/security/third-party/microsoft.rst:58 -msgid "Redirect URI (optional):" -msgstr "Redirect URI (optional):" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.login}``" +msgstr "``#{user.created_by.login}``" -#: ../settings/security/third-party/microsoft.rst:56 -msgid "" -"Select web and provide your callback URL. The callback URL looks like this: " -"``https://zammad.domain.tld/auth/microsoft_office365/callback``" -msgstr "" -"Wählen Sie Web und geben Sie Ihre Callback-URL an. Die Callback-URL sieht " -"wie folgt aus: ``https://zammad.domain.tld/auth/microsoft_office365/" -"callback``" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Mobile" +msgstr "Aktueller Benutzer > Erstellt von > Mobil" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to register a Microsoft app" -msgstr "Screencast zeigt, wie man eine Microsoft-Anwendung registriert" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.mobile}``" +msgstr "``#{user.created_by.mobile}``" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "Within **API permissions** add the following permissions:" -msgstr "" -"Fügen Sie unter **API-Berechtigungen** die folgenden Berechtigungen hinzu:" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``0049176123456789`` or empty if not set" +msgstr "``0049176123456789`` oder leer wenn nicht gesetzt" -#: ../settings/security/third-party/microsoft.rst:69 -msgid "``User.Read``" -msgstr "``User.Read``" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Note" +msgstr "Aktueller Benutzer > Erstellt von > Notiz" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "Contacts" -msgstr "Contacts" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.note}``" +msgstr "``#{user.created_by.note}``" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "``Contacts.Read``" -msgstr "``Contacts.Read``" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Some note to this user`` or empty if not set" +msgstr "``Eine Notiz zu diesem Benutzer`` oder leer wenn nicht gesetzt" -#: ../settings/security/third-party/microsoft.rst:73 -msgid "" -"You can find these permissions within *Microsoft Graph → Delegated " -"permissions*." -msgstr "" -"Sie finden diese Berechtigungen unter *Microsoft Graph → Delegated " -"permissions*." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Phone" +msgstr "Aktueller Benutzer > Erstellt von > Telefon" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to add required API permissions" -msgstr "" -"Screencast zeigt, wie man die erforderlichen API-Berechtigungen hinzufügt" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.phone}``" +msgstr "``#{user.created_by.phone}``" -#: ../settings/security/third-party/microsoft.rst:80 -msgid "" -"Within **Certificates & secrets** create a new client secret. Note down the " -"returned secret **value** for later. **Do not** use the secret ID!" -msgstr "" -"Erstellen Sie unter **Zertifikate & Secrets** ein neues Client-Secret. " -"Notieren Sie sich den zurückgegebenen **Wert** des Geheimnisses für später. " -"**Verwenden Sie nicht** die geheime ID!" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``004930123456789`` or empty if not set" +msgstr "``004930123456789`` oder leer wenn nicht gesetzt" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to create a new app secret" -msgstr "Screencast zeigt, wie man ein neues Anwendungs-Secret erstellt" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > VIP" +msgstr "Aktueller Benutzer > Erstellt von > VIP" -#: ../settings/security/third-party/microsoft.rst:88 -msgid "" -"From **Overview** copy your apps *Application (client) ID*. If you're using " -"a single tenant app, please also copy *Directory (tenant) ID*. You now have " -"all required information for Zammad." -msgstr "" -"Kopieren Sie aus **Übersicht** die *Anwendungs-(Client-)ID* Ihrer Anwendung. " -"Wenn Sie ein Single-Tenant-App verwenden, kopieren Sie bitte auch " -"*Verzeichnis (Tenant) ID*. Sie haben nun alle erforderlichen Informationen " -"für Zammad." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.vip}``" +msgstr "``#{user.created_by.vip}``" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to retreive application client and tenant IDs" -msgstr "" -"Screencast zeigt, wie man die IDs von Client Anwendungen und Tenants abruft" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Web" +msgstr "Aktueller Benutzer > Erstellt von > Web" -#: ../settings/security/third-party/microsoft.rst:98 -msgid "Step 2 - Add App Credentials to Zammad" -msgstr "Schritt 2 - Hinzufügen der Anmeldedaten in Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.web}``" +msgstr "``#{user.created_by.web}``" -#: ../settings/security/third-party/microsoft.rst:100 -msgid "" -"Navigate to Security > Third-party Applications (Tab) within Zammad's admin " -"settings. Scroll down to the section *Authentication via Microsoft* and fill " -"in the required information." -msgstr "" -"Navigieren Sie zu Sicherheit > Anwendungen von Drittanbietern " -"(Registerkarte) in den Verwaltungseinstellungen von Zammad. Scrollen Sie " -"nach unten zum Abschnitt *Anmelden über Microsoft* und geben Sie die " -"erforderlichen Informationen ein." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``https://zammad.org`` or empty if not set" +msgstr "``https://zammad.org`` oder leer wenn nicht gesetzt" -#: ../settings/security/third-party/microsoft.rst:105 -msgid "App ID:" -msgstr "App ID:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Department" +msgstr "Aktueller Benutzer > Abteilung" -#: ../settings/security/third-party/microsoft.rst:105 -msgid "This is your *Application (client) ID*." -msgstr "Dies ist Ihre *Anwendungs-(Client-)ID*." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.department}``" +msgstr "``#{user.department}``" -#: ../settings/security/third-party/microsoft.rst:108 -msgid "App secret:" -msgstr "App-Secret:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Email" +msgstr "Aktueller Benutzer > Email" -#: ../settings/security/third-party/microsoft.rst:108 -msgid "This is your *client secret* (value)." -msgstr "Dies ist Ihr *Client Secret* (Wert)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.email}``" +msgstr "``#{user.email}``" -#: ../settings/security/third-party/microsoft.rst:113 -msgid "App Tenant ID:" -msgstr "App Tenant ID:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Fax" +msgstr "Aktueller Benutzer > Fax" -#: ../settings/security/third-party/microsoft.rst:111 -msgid "" -"**optional** only required for apps that use account type *Accounts in this " -"organizational directory only (Default Directory only - Single tenant).*" -msgstr "" -"**optional** nur erforderlich für Anwendungen, die den Kontotyp *Accounts in " -"this organizational directory only (Default Directory only - Single tenant).*" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.fax}``" +msgstr "``#{user.fax}``" -#: ../settings/security/third-party/microsoft.rst:115 -msgid "" -"Apply your settings by pressing submit and activate *Authentication via " -"Microsoft*." -msgstr "" -"Übernehmen Sie Ihre Einstellungen, indem Sie auf Senden klicken und " -"*Authentifizierung über Microsoft* aktivieren." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Firstname" +msgstr "Aktueller Benutzer > Vorname" -#: ../settings/security/third-party/microsoft.rst:None -msgid "" -"Screencast showing how to add app credentials and activating the\n" -"authentication method" -msgstr "" -"Screencast zum Hinzufügen von Anmeldeinformationen für die Anwendung und zum " -"Aktivieren der\n" -"Authentifizierungsmethode" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.firstname}``" +msgstr "``#{user.firstname}``" -#: ../settings/security/third-party/saml.rst:2 -msgid "SAML" -msgstr "SAML" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Lastname" +msgstr "Aktueller Benutzer > Nachname" -#: ../settings/security/third-party/saml.rst:4 -msgid "" -"Connect your SAML (Security Assertion Markup Language) identity provider as " -"a single sign-on (SSO) method." -msgstr "" -"Verbinden Sie Ihren SAML (Security Assertion Markup Language) " -"Identitätsanbieter als Single-Sign-On-Methode (SSO)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.lastname}``" +msgstr "``#{user.lastname}``" -#: ../settings/security/third-party/saml.rst:7 -msgid "" -"SAML is an open standard for SSO authentication (among other things). Sign-" -"ins are shared across multiple **service providers** and managed by a " -"central **identity provider** (IdP)." -msgstr "" -"SAML ist (u.a.) ein offener Standard für die SSO-Authentifizierung. " -"Anmeldungen werden von mehreren **Dienstanbietern** gemeinsam genutzt und " -"von einem zentralen **Identitätsanbieter** (IdP) verwaltet." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Login" +msgstr "Aktueller Benutzer > Login" -#: ../settings/security/third-party/saml.rst:11 -msgid "" -"In this case, the service provider is Zammad, and the IdP is a software " -"service that you either host or subscribe to (*e.g.,* `Keycloak `_, `Redhat SSO Server `_, `ADFS `_, or `Okta `_)." -msgstr "" -"In diesem Fall ist der Dienstanbieter Zammad, und der IdP ist ein " -"Softwaredienst, den Sie entweder selbst hosten oder abonnieren (*z.B.* " -"`Keycloak `_, `Redhat SSO Server `_, `ADFS `_, " -"oder `Okta `_)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.login}``" +msgstr "``#{user.login}``" -#: ../settings/security/third-party/saml.rst:18 -msgid "" -"This guide assumes you are already using SAML within your organization (i." -"e., that your IdP is fully set up)." -msgstr "" -"Die Anleitung geht davon aus, dass Sie SAML bereits in Ihrer Organisation " -"verwenden (d.h. dass Ihr IdP vollständig eingerichtet ist)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Mobile" +msgstr "Aktueller Benutzer > Mobil" -#: ../settings/security/third-party/saml.rst:21 -msgid "" -"Please note: Our instructions are based on connecting Zammad with Keycloak." -msgstr "" -"Bitte beachten Sie: Unsere Anleitung basiert auf der Anbindung von Keycloak." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.mobile}``" +msgstr "``#{user.mobile}``" -#: ../settings/security/third-party/saml.rst:25 -msgid "Step 1: Configure Your IdP" -msgstr "Schritt 1: Konfigurieren Sie Ihren IdP" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Note" +msgstr "Aktueller Benutzer > Notiz" -#: ../settings/security/third-party/saml.rst:28 -msgid "Add Zammad as a Client/App" -msgstr "Zammad als Client/Anwendung hinzufügen" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.note}``" +msgstr "``#{user.note}``" -#: ../settings/security/third-party/saml.rst:30 -msgid "" -"Import Zammad into your IdP using the XML configuration found at ``https://" -"your.zammad.domain/auth/saml/metadata``." -msgstr "" -"Importieren Sie Zammad in Ihren IdP unter Verwendung der XML-Konfiguration, " -"die Sie unter ``https://your.zammad.domain/auth/saml/metadata`` finden." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Domain based assignment" +msgstr "Aktueller Benutzer > Organisation > Domain basierte Zuordnung" -#: ../settings/security/third-party/saml.rst:33 -msgid "" -"If your IdP doesn't support XML import, you will have to configure Zammad as " -"a new client/app manually using the above XML metadata file for reference." -msgstr "" -"Wenn Ihr IdP den XML-Import nicht unterstützt, müssen Sie Zammad manuell als " -"neuen Client/App konfigurieren und dabei die oben genannte XML-Metadaten-" -"Datei als Referenz verwenden." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.domain_assignment}``" +msgstr "``#{user.organization.domain_assignment}``" -#: ../settings/security/third-party/saml.rst:36 -msgid "For instance, when you see this tag:" -msgstr "Wenn Sie zum Beispiel diesen Tag sehen:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Domain" +msgstr "Aktueller Benutzer > Organisation > Domain" -#: ../settings/security/third-party/saml.rst:42 -msgid "" -"Set the **Assertion Consumer Service Binding URL** (sometimes also listed as " -"**Valid Redirect URIs**) to ``http://your.zammad.domain/auth/saml/callback``." -msgstr "" -"Setzen Sie die **Assertion Consumer Service Binding URL** (manchmal auch als " -"**Valid Redirect URIs** bezeichnet) auf ``http://your.zammad.domain/auth/" -"saml/callback``." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.domain}``" +msgstr "``#{user.organization.domain}``" -#: ../settings/security/third-party/saml.rst:47 -msgid "Set Up User Attribute Mapping" -msgstr "Benutzerattribut-Zuordnung einrichten" +#: ../misc/variables/current-user.rst:1 +msgid "``zammad.com`` or empty if not set" +msgstr "``zammad.com`` oder leer wenn nicht gesetzt" -#: ../settings/security/third-party/saml.rst:49 -msgid "" -"Zammad requests the following user attributes (or “properties”) from the IdP:" -msgstr "" -"Zammad fordert die folgenden Benutzerattribute (oder \"Eigenschaften\") vom " -"IdP an:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Name" +msgstr "Aktueller Benutzer > Organisation > Name" -#: ../settings/security/third-party/saml.rst:51 -msgid "Email address (``email``)" -msgstr "E-Mail Adresse (``email``)" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.name}``" +msgstr "``#{user.organization.name}``" -#: ../settings/security/third-party/saml.rst:52 -msgid "Full name (``name``)" -msgstr "Vollständiger Name (``name``)" +#: ../misc/variables/current-user.rst:1 +msgid "``Zammad GmbH``" +msgstr "``Zammad GmbH``" -#: ../settings/security/third-party/saml.rst:53 -msgid "Given name (``first_name``)" -msgstr "Vorname (``first_name``)" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Note" +msgstr "Aktueller Benutzer > Organisation > Notiz" -#: ../settings/security/third-party/saml.rst:54 -msgid "Family name (``last_name``)" -msgstr "Nachname (``last_name``)" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.note}``" +msgstr "``#{user.organization.note}``" -#: ../settings/security/third-party/saml.rst:56 -msgid "" -"You may need to set up “mappers” (or “mappings”) to tell your IdP how user " -"attributes in SAML correspond to those in Zammad. For a more detailed " -"breakdown, refer to the XML metadata file referenced in the previous section." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``A note to the organization of the user`` or empty if not set" msgstr "" -"Möglicherweise müssen Sie \"Mapper\" (oder \"Mappings\") einrichten, um " -"Ihrem IdP mitzuteilen, welche Benutzerattribute in SAML mit welchen in " -"Zammad übereinstimmen. Eine detailliertere Aufschlüsselung finden Sie in der " -"XML-Metadaten-Datei, auf die im vorherigen Abschnitt verwiesen wurde." +"``Eine Notiz in der Organisation des Benutzers`` oder leer, wenn nicht " +"gesetzt" -#: ../settings/security/third-party/saml.rst:62 -msgid "Per-IdP Instructions" -msgstr "Informationen für verschiedene IdP" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Shared organization" +msgstr "Aktueller Benutzer > Organisation > Geteilte Organisation" -#: ../settings/security/third-party/saml.rst:102 -msgid "Keycloak" -msgstr "Keycloak" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.shared}``" +msgstr "``#{user.organization.shared}``" -#: ../settings/security/third-party/saml.rst:65 -msgid "" -"**To add Zammad as a client,** save the XML configuration to disk (``https://" -"your.zammad.domain/auth/saml/metadata``) and use **Clients > Clients list > " -"Import client** in the Keycloak admin panel." -msgstr "" -"**Um Zammad als Client hinzuzufügen,** speichern Sie die XML-Konfiguration " -"auf Ihrem Rechner (``https://your.zammad.domain/auth/saml/metadata``) und " -"verwenden Sie **Clients > Clients list > Import client** im Keycloak Admin " -"Panel." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > VIP" +msgstr "Aktueller Benutzer > Organisation > VIP" -#: ../settings/security/third-party/saml.rst:70 -msgid "" -"To help Zammad **match its own user accounts to Keycloak users**, create a " -"user attribute (or “property”) mapper. In **Clients list**, click on your " -"newly created Client ID, choose the tab **Client scopes** and click on the " -"link which refers to your Zammad instance. Choose **Add mapper > By " -"configuration > User Property** and create a mapper with the following " -"entries:" -msgstr "" -"Um Zammad bei der **Zuordnung der Benutzerkonten zu Keycloak-Benutzern** zu " -"helfen, erstellen Sie einen Benutzerattribut- (oder \"Eigenschafts-\")-" -"Mapper. Klicken Sie in der **Clientl list** auf Ihre neu erstellte Client-" -"ID, wählen Sie den Reiter **Client scopes** und klicken Sie auf den Link, " -"der auf Ihre Zammad-Instanz verweist. Wählen Sie **Add mapper > By " -"configuration > User Property** und erstellen Sie einen Mapper mit den " -"folgenden Einträgen:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.vip}``" +msgstr "``#{user.organization.vip}``" -#: ../settings/security/third-party/saml.rst:78 -msgid "**Name**" -msgstr "**Name**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Phone" +msgstr "Aktueller Benutzer > Telefon" -#: ../settings/security/third-party/saml.rst:80 -msgid "**Mapper Type**" -msgstr "**Mapper-Typ**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.phone}``" +msgstr "``#{user.phone}``" -#: ../settings/security/third-party/saml.rst:81 -msgid "``User Property``" -msgstr "``User Property``" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated at" +msgstr "Aktueller Benutzer > Aktualisiert am" -#: ../settings/security/third-party/saml.rst:82 -msgid "**Property**" -msgstr "**Property**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_at}``" +msgstr "``#{user.updated_at}``" -#: ../settings/security/third-party/saml.rst:83 -msgid "``emailAddress``" -msgstr "``emailAddress``" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Address" +msgstr "Aktueller Benutzer > Aktualisiert von > Adresse" -#: ../settings/security/third-party/saml.rst:84 -msgid "**SAML Attribute Name**" -msgstr "**SAML Attribute Name**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.address}``" +msgstr "``#{user.updated_by.address}``" -#: ../settings/security/third-party/saml.rst:86 -msgid "**SAML Attribute NameFormat**" -msgstr "**SAML Attribute NameFormat**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Avatar" +msgstr "Aktueller Benutzer > Aktualisiert von > Avatar" -#: ../settings/security/third-party/saml.rst:87 -msgid "``basic``" -msgstr "``basic``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.avatar(60,60)}``" +msgstr "``#{user.updated_by.avatar(60,60)}``" -#: ../settings/security/third-party/saml.rst:89 -msgid "" -"In the example above, we're telling Zammad that whenever it receives a SAML " -"login request, it should take the ``email`` property from Keycloak, look for " -"a Zammad user with the same ``email`` attribute, and create a new session " -"for that user." -msgstr "" -"Im obigen Beispiel weisen wir Zammad an, dass es bei jeder SAML-" -"Anmeldeanfrage die Eigenschaft ``email`` von Keycloak nehmen, nach einem " -"Zammad-Benutzer mit demselben ``email``-Attribut suchen und eine neue " -"Sitzung für diesen Benutzer erstellen soll." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Department" +msgstr "Aktueller Benutzer > Aktualisiert von > Abteilung" -#: ../settings/security/third-party/saml.rst:95 -msgid "" -"If your Keycloak users' email addresses are stored on another property (*e." -"g.,* ``username``), adjust accordingly." -msgstr "" -"Wenn die E-Mail-Adressen Ihrer Keycloak-Benutzer in einer anderen " -"Eigenschaft gespeichert sind (*z.B.* ``username``), passen Sie sie " -"entsprechend an." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.department}``" +msgstr "``#{user.updated_by.department}``" -#: ../settings/security/third-party/saml.rst:98 -msgid "" -"Back in **Settings**, enter the Client ID (``https://your.zammad.domain/auth/" -"saml/metadata``) in the field **Master SAML Processing URL**." -msgstr "" -"Geben Sie in den **Einstellungen** die Client-ID (``https://your.zammad." -"domain/auth/saml/metadata``) in das Feld **Master SAML Processing URL** ein." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Email" +msgstr "Aktueller Benutzer > Aktualisiert von > Email" -#: ../settings/security/third-party/saml.rst:101 -msgid "You also need to enable **Sign assertions**." -msgstr "Sie müssen auch **Sign Assertions** aktivieren." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.email}``" +msgstr "``#{user.updated_by.email}``" -#: ../settings/security/third-party/saml.rst:105 -msgid "Step 2: Configure Zammad" -msgstr "Schritt 2: Zammad konfigurieren" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Fax" +msgstr "Aktueller Benutzer > Aktualisiert von > Fax" -#: ../settings/security/third-party/saml.rst:107 -msgid "" -"Enable SAML and enter your IdP's details in the Admin Panel under **Settings " -"> Security > Third Party Applications > Authentication via SAML**:" -msgstr "" -"Aktivieren Sie SAML und geben Sie die Details Ihres IdP im Admin Bereich " -"unter **Einstellungen > Sicherheit > Anwendungen von Drittanbietern > " -"Anmeldung über SAML** ein:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.fax}``" +msgstr "``#{user.updated_by.fax}``" -#: ../settings/security/third-party/saml.rst:None -msgid "Example configuration of SAML part 1" -msgstr "Beispielkonfiguration von SAML Teil 1" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Firstname" +msgstr "Aktueller Benutzer > Aktualisiert von > Vorname" -#: ../settings/security/third-party/saml.rst:119 -msgid "Display name" -msgstr "Anzeigename" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.firstname}``" +msgstr "``#{user.updated_by.firstname}``" -#: ../settings/security/third-party/saml.rst:116 -msgid "" -"Allows you to define a custom button name for SAML. This helps your users to " -"understand better what the button on the login page does." -msgstr "" -"Ermöglicht es Ihnen, einen eigenen Namen für den SAML-Button zu definieren. " -"Das kann hilfreich sein, damit Ihre Benutzer verstehen, was die Schaltfläche " -"auf der Anmeldeseite genau bewirkt." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Lastname" +msgstr "Aktueller Benutzer > Aktualisiert von > Nachname" -#: ../settings/security/third-party/saml.rst:119 -msgid "Defaults to ``SAML``." -msgstr "Die Voreinstellung ist ``SAML``." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.lastname}``" +msgstr "``#{user.updated_by.lastname}``" -#: ../settings/security/third-party/saml.rst:123 -msgid "IDP SSO target URL" -msgstr "IDP SSO Ziel-URL" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Login" +msgstr "Aktueller Benutzer > Aktualisiert bei > Login" -#: ../settings/security/third-party/saml.rst:122 -msgid "" -"This is the target URL Zammad shall redirect to when the user presses the " -"SAML button. For Keycloak, this needs to look like https://your.domain/" -"realms/your-realm/protocol/saml" -msgstr "" -"Dies ist die Ziel-URL, zu der Zammad umleiten soll, wenn der Benutzer die " -"SAML-Schaltfläche anklickt. Für Keycloak muss dies wie folgt aussehen: " -"https://your.domain/realms/your-realm/protocol/saml." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.login}``" +msgstr "``#{user.updated_by.login}``" -#: ../settings/security/third-party/saml.rst:127 -msgid "IDP single logout target URL" -msgstr "IDP Ziel-URL für Einzel-Abmeldung" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Mobile" +msgstr "Aktueller Benutzer > Aktualisiert von > Mobil" -#: ../settings/security/third-party/saml.rst:126 -msgid "" -"This is the URL to which the single logout request and response should be " -"sent." -msgstr "" -"Dies ist die URL, an die die einzelne Abmeldeanforderung gesendet werden " -"soll." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.mobile}``" +msgstr "``#{user.updated_by.mobile}``" -#: ../settings/security/third-party/saml.rst:131 -msgid "IDP certificate" -msgstr "IDP-Zertifikat" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Note" +msgstr "Aktueller Benutzer > Aktualisiert von > Notiz" -#: ../settings/security/third-party/saml.rst:130 -msgid "" -"The public certificate of your IDP for Zammad to verify during the callback " -"phase." -msgstr "" -"Das öffentliche Zertifikat Ihres IDP, das Zammad während des \"Callbacks\" " -"überprüfen soll." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.note}``" +msgstr "``#{user.updated_by.note}``" -#: ../settings/security/third-party/saml.rst:145 -msgid "IDP certificate fingerprint" -msgstr "Fingerabdruck IDP-Zertifikat" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Phone" +msgstr "Aktueller Benutzer > Aktualisiert von > Telefon" -#: ../settings/security/third-party/saml.rst:134 -msgid "" -"The fingerprint of your IDPs public certificate to verify during callback " -"phase." -msgstr "" -"Der Fingerabdruck Ihres öffentlichen IDP-Zertifikats, der während des " -"\"Callbacks\" geprüft wird." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.phone}``" +msgstr "``#{user.updated_by.phone}``" -#: ../settings/security/third-party/saml.rst:137 -msgid "🔏 **For the IdP certificate / certificate fingerprint:**" -msgstr "🔏 **Für das IdP-Zertifikat / den Zertifikatsfingerabdruck:**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > VIP" +msgstr "Aktueller Benutzer > Aktualisiert von > VIP" -#: ../settings/security/third-party/saml.rst:139 -msgid "" -"Provide **only one or the other**—do not provide both! (Between the two, we " -"recommend the signing certificate itself: fingerprints use SHA-1, which `has " -"been broken for a while now `_.)" -msgstr "" -"Verwenden Sie **nur eine der Varianten**. Wir empfehlen die Verwendung des " -"Zertifikats selbst: Fingerabdrücke verwenden SHA-1, das `seit einiger Zeit " -"als unsicher gilt `_)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.vip}``" +msgstr "``#{user.updated_by.vip}``" -#: ../settings/security/third-party/saml.rst:144 -msgid "" -"**Keycloak users:** Find your certificate in the Keycloak admin panel under " -"**Realm Settings > Keys > Algorithm: RS256 > Certificate**." -msgstr "" -"**Keycloak-Anwender:** Sie finden Ihr Zertifikat im Keycloak-" -"Administrationsbereich unter **Realm Settings > Keys > Algorithm: RS256 > " -"Certificate**." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``false`` or ``true``" +msgstr "``false`` oder ``true``" -#: ../settings/security/third-party/saml.rst:151 -msgid "Name identifier format" -msgstr "Name Identifier Format" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Web" +msgstr "Aktueller Benutzer > Aktualisiert von > Web" -#: ../settings/security/third-party/saml.rst:148 -msgid "" -"This is the unique identifiers field type. Usually it should be ``urn:oasis:" -"names:tc:SAML:1.1:nameid-format:emailAddress``." -msgstr "" -"Dies ist der Feldtyp für unique identifiers (eindeutige Kennung). " -"Normalerweise ist es ``urn:oasis:names:tc:SAML:1.1:nameid-format:" -"emailAddress``." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.web}``" +msgstr "``#{user.updated_by.web}``" -#: ../settings/security/third-party/saml.rst:151 -msgid "Zammad **expects an email address as unique identifier**!" -msgstr "Zammad **erwartet eine E-Mail-Adresse als eindeutigen Identifikator**!" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > VIP" +msgstr "Aktueller Benutzer > VIP" -#: ../settings/security/third-party/saml.rst:155 -msgid "UID attribute name" -msgstr "Name des UID-Attributs" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.vip}``" +msgstr "``#{user.vip}``" -#: ../settings/security/third-party/saml.rst:154 -msgid "" -"Here you can define an attribute that uniquely identifies the user. If " -"unset, the name identifier returned by the IDP is used." -msgstr "" -"Hier können Sie ein Attribut zur eindeutigen Identifizierung des Benutzers " -"festlegen. Wenn es nicht gesetzt ist, wird der von der IDP zurückgegebene " -"Namensbezeichner verwendet." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Web" +msgstr "Aktueller Benutzer > Web" -#: ../settings/security/third-party/saml.rst:None -msgid "Example configuration of SAML part 2" -msgstr "Beispielkonfiguration von SAML Teil 2" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.web}``" +msgstr "``#{user.web}``" -#: ../settings/security/third-party/saml.rst:163 +#: ../misc/variables/ticket.rst:6 +#, fuzzy +#| msgid "" +#| "Below you can find all available ticket-based variables within Zammad. " +#| "These can be called via Triggers for example. If you're unsure if Zammad " +#| "does support variables at the point you're at, you can try to type ``::`` " +#| "to check." msgid "" -"Decide if the certificate for the connection to the IdP service has to be " -"verified or not (default: ``yes``)." +"Below you can find all available ticket-based variables within Zammad. These " +"can be called via triggers for example. If you're unsure if Zammad does " +"support variables at the point you're at, you can try to type ``::`` to " +"check." msgstr "" -"Entscheiden Sie, ob das Zertifikat für die Verbindung zum IdP-Dienst " -"verifiziert werden muss oder nicht (Standard: ``Ja``)." +"Unten finden Sie alle verfügbaren ticketbasierten Variablen in Zammad. Diese " +"können zum Beispiel in Triggern aufgerufen werden. Wenn Sie unsicher sind, " +"welche Variablen an diesem Punkt unterstützt, tippen Sie einfach ``::`` zum " +"Prüfen." -#: ../settings/security/third-party/saml.rst:169 -msgid "Signing & Encrypting" -msgstr "Signieren & Verschlüsseln" +#: ../misc/variables/ticket.rst:12 +msgid "Ticket Variables" +msgstr "Ticket-Variablen" -#: ../settings/security/third-party/saml.rst:169 -msgid "" -"Define if you want to sign, encrypt, do both or nothing for the requests." -msgstr "" -"Legen Sie fest, ob Sie die Anfragen signieren, verschlüsseln, beides oder " -"nichts tun wollen." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Accounted Time" +msgstr "Ticket > erfasste Zeit" -#: ../settings/security/third-party/saml.rst:179 -msgid "Certificate (PEM)" -msgstr "Zertifikat (PEM)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.time_unit}``" +msgstr "``#{ticket.time_unit}``" -#: ../settings/security/third-party/saml.rst:172 -msgid "" -"Paste the public certificate of your Zammad SAML client, if you want to " -"encrypt the requests." +#: ../misc/variables/ticket.rst:1 +msgid "``1``, ``2.75`` or empty response" +msgstr "``1``, ``2.75`` oder leere Ausgabe" + +#: ../misc/variables/ticket.rst:1 +msgid "``3``, any number of articles existing in the ticket right now" msgstr "" -"Fügen Sie das öffentliche Zertifikat Ihres Zammad SAML-Clients ein, wenn Sie " -"die Anfragen verschlüsseln möchten." +"``3``, eine beliebige Anzahl von Artikeln, die derzeit im Ticket vorhanden " +"sind" -#: ../settings/security/third-party/saml.rst:175 -msgid "Make sure the certificate is:" -msgstr "Vergewissern Sie sich, dass das Zertifikat:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Closing time" +msgstr "Ticket > Schließzeit" -#: ../settings/security/third-party/saml.rst:177 -msgid "already valid and not yet expired" -msgstr "bereits gültig und noch nicht abgelaufen ist" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.close_at}``" +msgstr "``#{ticket.close_at}``" -#: ../settings/security/third-party/saml.rst:178 -msgid "no CA certificate" -msgstr "kein CA-Zertifikat ist" +#: ../misc/variables/ticket.rst:1 +msgid "2019-10-07 17:25:00 UTC" +msgstr "2019-10-07 17:25:00 UTC" -#: ../settings/security/third-party/saml.rst:179 -msgid "valid for signing and encrypting" -msgstr "gültig zum Signieren und Verschlüsseln ist" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created at" +msgstr "Ticket > Erstellt am" -#: ../settings/security/third-party/saml.rst:185 -msgid "Private key (PEM)" -msgstr "Privater Schlüssel (PEM)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_at}``" +msgstr "``#{ticket.created_at}``" -#: ../settings/security/third-party/saml.rst:182 -msgid "" -"Paste the private key of your Zammad SAML client here, if you want to sign " -"the requests." -msgstr "" -"Fügen Sie hier den privaten Schlüssel Ihres Zammad SAML-Clients ein, wenn " -"Sie die Anfragen signieren möchten." +#: ../misc/variables/ticket.rst:1 +msgid "2019-10-07 16:25:00 UTC" +msgstr "2019-10-07 16:25:00 UTC" -#: ../settings/security/third-party/saml.rst:185 -msgid "Make sure the key is an RSA key with a length of at least 2048 bits." -msgstr "" -"Stellen Sie sicher, dass der Schlüssel ein RSA-Schlüssel mit einer Länge von " -"mindestens 2048 Bit ist." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Address" +msgstr "Ticket > Erstellt von > Adresse" -#: ../settings/security/third-party/saml.rst:188 -msgid "Private key secret" -msgstr "Geheimnis des privaten Schlüssels" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.address}``" +msgstr "``#{ticket.created_by.address}``" -#: ../settings/security/third-party/saml.rst:188 -msgid "If your private key is secured with a secret, you can provide it here." -msgstr "" -"Wenn Ihr privater Schlüssel mit einem Passwort gesichert ist, können Sie es " -"hier angeben." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Avatar" +msgstr "Ticket > Erstellt von > Avatar" -#: ../settings/security/third-party/saml.rst:192 -msgid "Your callback URL" -msgstr "Ihre Callback-URL" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.avatar(60,60)}``" +msgstr "``#{ticket.created_by.avatar(60,60)}``" -#: ../settings/security/third-party/saml.rst:191 -msgid "" -"This URL is needed for your IdP configuration so it knows where to redirect " -"to after successful authentication." -msgstr "" -"Diese URL wird für die IdP-Konfiguration benötigt, damit dieser weiß, wohin " -"er nach erfolgreicher Authentifizierung weiterleiten muss." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Department" +msgstr "Ticket > Erstellt von > Abteilung" -#: ../settings/security/third-party/saml.rst:194 -msgid "" -"After saving your input by clicking on the \"Submit\" button, Zammad " -"verifies the provided keys/certificates (e.g. if they are valid for signing/" -"encrypting and if they aren't expired)." -msgstr "" -"Nachdem Sie Ihre Eingaben durch Klicken auf die Schaltfläche \"Absenden\" " -"gespeichert haben, überprüft Zammad die bereitgestellten Schlüssel/" -"Zertifikate (z.B. ob sie zum Signieren/Verschlüsseln gültig und nicht " -"abgelaufen sind)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.department}``" +msgstr "``#{ticket.created_by.department}``" -#: ../settings/security/third-party/saml.rst:199 -msgid "" -"See :ref:`automatic account linking ` for details " -"on how to link existing Zammad accounts to IdP accounts." -msgstr "" -"Siehe :ref:`automatische Kontoverknüpfung ` für " -"Details zur Verknüpfung bestehender Zammad-Konten mit IdP-Konten." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Email" +msgstr "Ticket > Erstellt von > Email" -#: ../settings/security/third-party/saml.rst:205 -msgid "Automatic account linking doesn't work" -msgstr "Automatische Kontoverknüpfung funktioniert nicht" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.email}``" +msgstr "``#{ticket.created_by.email}``" -#: ../settings/security/third-party/saml.rst:206 -msgid "" -"Have you double-checked your IdP's user attribute mapping configuration?" -msgstr "" -"Haben Sie die Konfiguration der Benutzerattribut-Zuordnung Ihres IdP " -"überprüft?" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Fax" +msgstr "Ticket > Erstellt von > Fax" -#: ../settings/security/third-party/twitter.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via Twitter. To do " -"so, you need to follow these steps:" -msgstr "" -"Es ist möglich, eine Anmeldung über Twitter zu erstellen. Dazu müssen Sie " -"die folgenden Schritte ausführen:" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.fax}``" +msgstr "``#{ticket.created_by.fax}``" -#: ../settings/security/third-party/twitter.rst:8 -msgid "Register Twitter App" -msgstr "Twitter-App registrieren" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Firstname" +msgstr "Ticket > Erstellt von > Vorname" -#: ../settings/security/third-party/twitter.rst:10 -msgid "Go to https://dev.twitter.com/apps and login with your account." -msgstr "" -"Rufen Sie https://dev.twitter.com/apps auf und melden Sie sich mit Ihrem " -"Konto an." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.firstname}``" +msgstr "``#{ticket.created_by.firstname}``" -#: ../settings/security/third-party/twitter.rst:15 -msgid "Click on \"Create App\"" -msgstr "Klicken Sie auf \"Create App\"" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Lastname" +msgstr "Ticket > Erstellt von > Nachname" -#: ../settings/security/third-party/twitter.rst:None -msgid "new app page" -msgstr "neue App Seite" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.lastname}``" +msgstr "``#{ticket.created_by.lastname}``" -#: ../settings/security/third-party/twitter.rst:20 -msgid "" -"Enter app settings. As \"Callback URL\" you need to enter ``https://" -"zammad_host/api/v1/external_credentials/twitter/callback``. You need to " -"replace ``zammad_host`` with the domain of your Zammad system." -msgstr "" -"Geben Sie die App-Einstellungen ein. Als \"Callback URL\" müssen Sie " -"``https://zammad_host/api/v1/external_credentials/twitter/callback`` " -"eingeben. Ersetzen Sie ``zammad_host`` durch die Domain Ihres Zammad-Systems." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Login" +msgstr "Ticket > Erstellt von > Login" -#: ../settings/security/third-party/twitter.rst:24 -msgid "" -"After the app has been created, update the application icon and organization " -"attributes." -msgstr "" -"Nachdem die Anwendung erstellt wurde, aktualisieren Sie das Anwendungssymbol " -"und die Organisationsattribute." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.login}``" +msgstr "``#{ticket.created_by.login}``" -#: ../settings/security/third-party/twitter.rst:None -msgid "set permissions to receive and send direct messages" -msgstr "" -"Berechtigungen zum Empfangen und Senden von Direktnachrichten festlegen" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Mobile" +msgstr "Ticket > Erstellt von > Mobil" -#: ../settings/security/third-party/twitter.rst:30 -msgid "" -"Next we need to set ``read, write and access direct messages`` permissions " -"for the app." -msgstr "" -"Als Nächstes müssen wir die Berechtigungen ``read, write and access direct " -"messages`` Berechtigungen für die Anwendung festlegen." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.mobile}``" +msgstr "``#{ticket.created_by.mobile}``" -#: ../settings/security/third-party/twitter.rst:None -msgid "click on Keys & Access Token, note them" -msgstr "Klicken Sie auf Schlüssel & Zugangstoken, notieren Sie sie" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Note" +msgstr "Ticket > Erstellt von > Notiz" -#: ../settings/security/third-party/twitter.rst:36 -msgid "" -"Go to \"Keys and Access Token\" tab and note the \"Consumer Key\" and " -"\"Consumer Secret\"." -msgstr "" -"Gehen Sie zum Tab \"Keys and Access Token\" und notieren Sie sich den " -"\"Consumer Key\" und das \"Consumer Secret\"." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.note}``" +msgstr "``#{ticket.created_by.note}``" -#: ../settings/security/third-party/twitter.rst:40 -msgid "Configure Zammad as Twitter App" -msgstr "Zammad als Twitter-App konfigurieren" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Phone" +msgstr "Ticket > Erstellt von > Telefon" -#: ../settings/security/third-party/twitter.rst:42 -msgid "" -"Go to \"Admin > Security > Twitter > Third Party Applications > Twitter\" " -"Section." -msgstr "" -"Gehen Sie zu \"Einstellungen > Sicherheit > Anwendungen von Drittanbietern > " -"Twitter\"" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.phone}``" +msgstr "``#{ticket.created_by.phone}``" -#: ../settings/security/third-party/twitter.rst:None -msgid "Admin > Security > Third Party Applications" -msgstr "Verwaltung > Sicherheit > Anwendungen von Drittanbietern" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > VIP" +msgstr "Ticket > Erstellt von > VIP" -#: ../settings/security/third-party/twitter.rst:48 -msgid "" -"Fill in the \"Twitter Key\" and the \"Twitter Secret\" and click the " -"\"Submit\" button." -msgstr "" -"Geben Sie den \"Twitter Key\" und das \"Twitter Secret\" ein und klicken Sie " -"auf die Schaltfläche \"Übermitteln\"." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.vip}``" +msgstr "``#{ticket.created_by.vip}``" -#: ../settings/security/third-party/twitter.rst:51 -msgid "" -"Now you can link accounts via \"Avatar > Profile > Link Accounts\" or login " -"via Zammad login page." -msgstr "" -"Jetzt können Sie Konten über \"Avatar > Profil > Verknüpfte Konten\" " -"verknüpfen oder sich über die Zammad-Login-Seite anmelden." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Web" +msgstr "Ticket > Erstellt von > Web" -#: ../settings/security/two-factor.rst:11 -msgid "Two-factor Authentication Methods" -msgstr "Methoden für Zwei-Faktor-Authentifizierung" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.web}``" +msgstr "``#{ticket.created_by.web}``" -#: ../settings/security/two-factor.rst:2 -msgid "Two-Factor Authentication" -msgstr "Zwei-Faktor-Authentifizierung" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Address" +msgstr "Ticket > Kunde > Adresse" -#: ../settings/security/two-factor.rst:4 -msgid "" -"Two-factor authentication (2FA) enhances the security of Zammad accounts by " -"adding an extra layer of verification beyond a password. It requires users " -"to provide two different types of authentication factors, typically " -"something they know (like a password) and something they possess (like a " -"mobile device or a security token), to ensure that only authorized " -"individuals can access the account." -msgstr "" -"Die Zwei-Faktor-Authentifizierung (2FA) erweitert die Sicherheit von Zammad-" -"Konten, indem eine zusätzliche Prüfung neben einem Passwort erforderlich " -"ist. Benutzer müssen über zwei verschiedene Faktoren verfügen, um " -"sicherzustellen, dass Sie berechtigt sind, auf das Konto zuzugreifen. " -"Typischerweise ist das etwas, was die Benutzer wissen (wie ein Passwort) und " -"etwas, das sie besitzen (wie ein Mobilgerät oder ein Security-Token)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.address}``" +msgstr "``#{ticket.customer.address}``" -#: ../settings/security/two-factor.rst:19 -msgid "Enable Recovery Codes" -msgstr "Wiederherstellungs-Codes aktivieren" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Avatar" +msgstr "Ticket > Kunde > Avatar" -#: ../settings/security/two-factor.rst:21 -msgid "" -"Recovery codes are one-time use security codes that can be used by the user " -"if they lose access to their other two-factor authentication methods. They " -"cannot be used on their own, they can only be activated if at least one two-" -"factor authentication method is enabled." -msgstr "" -"Wiederherstellungscodes sind einmalig verwendbare Sicherheitscodes, die vom " -"Benutzer verwendet werden können, wenn er den Zugang zu seinen anderen Zwei-" -"Faktor-Authentifizierungsmethoden verliert. Sie können nicht allein " -"verwendet werden, sondern können nur aktiviert werden, wenn mindestens eine " -"Zwei-Faktor-Authentifizierungsmethode aktiviert ist." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.avatar(60,60)}``" +msgstr "``#{ticket.customer.avatar(60,60)}``" -#: ../settings/security/two-factor.rst:None -msgid "Enable Recovery Codes Setting" -msgstr "Einstellung Wiederherstellungscodes aktivieren" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Department" +msgstr "Ticket > Kunde > Abteilung" -#: ../settings/security/two-factor.rst:30 -msgid "" -"Recovery codes can only be used as a backup method. If enabled, they will be " -"automatically generated for the user once they set up their initial two-" -"factor authentication method." -msgstr "" -"Wiederherstellungscodes können nur als Backup-Methode verwendet werden. Wenn " -"sie aktiviert sind, werden sie automatisch für den Benutzer generiert, " -"sobald er seine erste Zwei-Faktor-Authentifizierungsmethode eingerichtet hat." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.department}``" +msgstr "``#{ticket.customer.department}``" -#: ../settings/security/two-factor.rst:34 -msgid "" -"The user will be asked to print out or save the generated recovery codes in " -"a safe place. Once used, a recovery code cannot be reused." -msgstr "" -"Der Benutzer wird aufgefordert, die generierten Wiederherstellungscodes " -"auszudrucken oder an einem sicheren Ort zu speichern. Ein einmal verwendeter " -"Wiederherstellungscode kann nicht wiederverwendet werden." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Email" +msgstr "Ticket > Kunde > Email" -#: ../settings/security/two-factor.rst:37 -msgid "" -"Users will also have an option to regenerate their recovery codes at any " -"time, which invalidates already existing recovery codes and provides them " -"with a list of fresh codes." -msgstr "" -"Die Nutzer haben außerdem die Möglichkeit, ihre Wiederherstellungscodes " -"jederzeit neu zu generieren, wodurch bereits vorhandene " -"Wiederherstellungscodes ungültig werden und sie eine Liste mit neuen Codes " -"erhalten." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.email}``" +msgstr "``#{ticket.customer.email}``" -#: ../settings/security/two-factor.rst:41 -msgid "" -"After you enable this setting, when the user completes a setup of their " -"initial two-factor authentication method, they will be presented with a list " -"of recovery codes and instructed to save them for later use." -msgstr "" -"Nachdem Sie diese Einstellung aktiviert haben, wird dem Benutzer nach " -"Abschluss der Einrichtung seiner Zwei-Faktor-Authentifizierungsmethode eine " -"Liste mit Wiederherstellungscodes angezeigt, die er zur späteren Verwendung " -"speichern kann." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Fax" +msgstr "Ticket > Kunde > Fax" -#: ../settings/security/two-factor.rst:None -msgid "Recovery Codes Generation Modal Dialog" -msgstr "Dialog zur Erzeugung von Wiederherstellungscodes" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.fax}``" +msgstr "``#{ticket.customer.fax}``" -#: ../settings/security/two-factor.rst:50 -msgid "Enforce the Set Up of the Two-Factor Authentication" -msgstr "Einrichtung der Zwei-Faktor-Authentifizierung erzwingen" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Firstname" +msgstr "Ticket > Kunde > Vorname" -#: ../settings/security/two-factor.rst:52 -msgid "" -"In case you wish to require your users to set up at least one two-factor " -"authentication method for their account, you can do this by selecting " -"specific user roles the requirement applies to in **Enforced for user " -"roles** setting. Of course you must have at least one two-factor " -"authentication method enabled for this setting to take effect." -msgstr "" -"Wenn Sie von Ihren Benutzern verlangen wollen, dass sie mindestens eine Zwei-" -"Faktor-Authentifizierungsmethode für ihr Konto einrichten, können Sie dies " -"tun, indem Sie in der Einstellung **Für Benutzer-Rollen erzwingen** " -"bestimmte Benutzerrollen auswählen, für die die Anforderung gilt. Natürlich " -"müssen Sie mindestens eine Zwei-Faktor-Authentifizierungsmethode aktiviert " -"haben, damit diese Einstellung wirksam wird." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.firstname}``" +msgstr "``#{ticket.customer.firstname}``" -#: ../settings/security/two-factor.rst:None -msgid "Enforced for User Roles Setting" -msgstr "Verpflichtend für Benutzerrollen" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Lastname" +msgstr "Ticket > Kunde > Nachname" -#: ../settings/security/two-factor.rst:62 -msgid "" -"After you change this setting, if the user has one of the selected roles on " -"their account, they will be forced to set up the two-factor authentication " -"upon next sign in or application reload." -msgstr "" -"Nachdem Sie diese Einstellung geändert haben, werden Benutzer mit der " -"entsprechenden Rolle gezwungen, die Zwei-Faktor-Authentifizierung bei der " -"nächsten Anmeldung oder beim erneuten Laden der Anwendung einzurichten." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.lastname}``" +msgstr "``#{ticket.customer.lastname}``" -#: ../settings/security/two-factor.rst:66 -msgid "" -"A modal dialog with instructions will be shown, and they will not be able to " -"do any work before they set up at least one two-factor method." -msgstr "" -"Es wird ein Dialogfeld mit Anweisungen angezeigt und sie können erst dann " -"weiter arbeiten, wenn sie mindestens eine Zwei-Faktor-Methode eingerichtet " -"haben." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Login" +msgstr "Ticket > Kunde > Login" -#: ../settings/security/two-factor.rst:None -msgid "Modal Dialog for Enforcing Two-Factor Authentication Set Up" -msgstr "Dialog zur Erzwingung der Zwei-Faktoren-Authentifizierung" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.login}``" +msgstr "``#{ticket.customer.login}``" -#: ../settings/security/two-factor.rst:74 -msgid "Reset Two-Factor Authentication for a Specific User" -msgstr "Zwei-Faktor-Authentifizierung für bestimmte User zurücksetzen" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Mobile" +msgstr "Ticket > Kunde > Mobil" -#: ../settings/security/two-factor.rst:76 -msgid "" -"In case an user isn't able to login anymore because of an inaccessible " -"second factor, you can reset the user's 2FA method." -msgstr "" -"Falls sich ein Benutzer aufgrund eine nicht verfügbaren Zwei-Faktor-Methode " -"nicht mehr anmelden kann, können Sie die 2FA-Methode des Benutzers " -"zurücksetzen." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.mobile}``" +msgstr "``#{ticket.customer.mobile}``" -#: ../settings/security/two-factor.rst:79 -msgid "" -"To do this, go to the user management and search for the relevant user. " -"After you found the account, click the button in the action column and " -"select \"Manage Two-Factor Authentication\":" -msgstr "" -"Gehen Sie dazu in die Benutzerverwaltung und suchen Sie nach dem " -"entsprechenden Benutzer. Nachdem Sie das Konto gefunden haben, klicken Sie " -"auf den Button in der Aktionsspalte und wählen Sie \"Zwei-Faktor-" -"Authentifizierung verwalten\":" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Note" +msgstr "Ticket > Kunde > Notiz" -#: ../settings/security/two-factor.rst:None -msgid "Context menu in action column in user management" -msgstr "Kontextmenü in der Aktionsspalte der Benutzerverwaltung" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.note}``" +msgstr "``#{ticket.customer.note}``" -#: ../settings/security/two-factor.rst:87 -msgid "" -"After selecting this, you can see a dialog where you can either reset one " -"2FA method or reset all of the user's 2FA methods:" -msgstr "" -"Nachdem Sie dies ausgewählt haben, sehen Sie einen Dialog, in dem Sie " -"entweder eine 2FA-Methode oder alle 2FA-Methoden des Benutzers zurücksetzen " -"können:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Phone" +msgstr "Ticket > Kunde > Telefon" -#: ../settings/security/two-factor.rst:None -msgid "Dialog for resetting user's 2FA method" -msgstr "Dialog zum Zurücksetzen der 2FA-Methode des Benutzers" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.phone}``" +msgstr "``#{ticket.customer.phone}``" -#: ../settings/security/two-factor.rst:94 -msgid "" -"Choose the fitting one, click on the corresponding \"Remove ...\" button and " -"confirm your action. The user now has to setup a new 2FA method, depending " -"on your 2FA configuration." -msgstr "" -"Wählen Sie die passende aus, klicken Sie auf die entsprechende Schaltfläche " -"\"... entfernen\" und bestätigen Sie Ihre Aktion. Der Benutzer muss nun " -"abhängig von Ihrer 2FA-Konfiguration eine neue 2FA-Methode einrichten." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > VIP" +msgstr "Ticket > Kunde > VIP" -#: ../settings/security/two-factor/authenticator-app.rst:2 -msgid "Authenticator App" -msgstr "Authentifizierungs-App" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.vip}``" +msgstr "``#{ticket.customer.vip}``" -#: ../settings/security/two-factor/authenticator-app.rst:4 -msgid "" -"The authenticator app method is a type of two-factor authentication that " -"uses a mobile application to generate one-time codes for account " -"verification. After setting up the authenticator app on their device, the " -"user links it to their Zammad account." -msgstr "" -"Die Authentifizierungs-App ist eine Methode der Zwei-Faktor-" -"Authentifizierung, bei der eine mobile App (\"Authentifizierungs-App\") " -"Einmal-Codes generiert, die beim Anmelden geprüft werden. Nachdem die " -"Benutzer eine Authentifizierungs-App auf Ihrem Gerät eingerichtet haben, " -"können diese die App mit ihr Zammad-Konto verknüpfen." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Web" +msgstr "Ticket > Kunde > Web" -#: ../settings/security/two-factor/authenticator-app.rst:12 -msgid "" -"When logging in, the user is prompted to enter a time-sensitive code " -"generated by the app, in addition to their password. This code acts as the " -"second factor of authentication, providing an extra layer of security as it " -"changes periodically and is unique to the user's device." -msgstr "" -"Bei der Anmeldung wird der Nutzer aufgefordert, zusätzlich zu seinem " -"Passwort einen von der App generierten zeitabhängigen Code einzugeben. " -"Dieser Code dient als zweiter Authentifizierungsfaktor und bietet eine " -"zusätzliche Sicherheitsebene, da er sich regelmäßig ändert und nur auf dem " -"Gerät des Nutzers vorhanden ist." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.web}``" +msgstr "``#{ticket.customer.web}``" -#: ../settings/security/two-factor/authenticator-app.rst:None -msgid "Security Code in Google Authenticator App" -msgstr "Sicherheits-Code in der Google Authenticator App" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Escalation at" +msgstr "Ticket > Eskalation am" -#: ../settings/security/two-factor/authenticator-app.rst:22 -msgid "" -"The app generates codes based on a shared secret key stored securely on both " -"the user's device and the server, ensuring a synchronized and secure " -"authentication process. The method of generating the codes is sometimes also " -"called TOTP (time-based one-time password)." -msgstr "" -"Die App generiert Codes auf der Grundlage eines gemeinsam genutzten geheimen " -"Schlüssels, der sowohl auf dem Gerät des Nutzers als auch auf dem Server " -"sicher gespeichert ist, wodurch ein synchronisierter und sicherer " -"Authentifizierungsprozess gewährleistet wird. Die Methode zur Generierung " -"der Codes wird manchmal auch als TOTP (time-based one-time password) " -"bezeichnet." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.escalation_at}``" +msgstr "``#{ticket.escalation_at}``" -#: ../settings/security/two-factor/authenticator-app.rst:28 -msgid "Enabling the Authenticator App Method" -msgstr "Aktivieren der Authenticator App-Methode" +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable" +msgstr "``2019-10-07 16:25:00 UTC`` oder leer, falls nicht zutreffend" -#: ../settings/security/two-factor/authenticator-app.rst:30 -#: ../settings/security/two-factor/security-keys.rst:28 -msgid "To enable the method, just toggle the switch on in the settings." -msgstr "" -"Um die Methode zu aktivieren, schalten Sie sie einfach in den Einstellungen " -"ein, indem Sie den Schalter aktivieren." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > First response" +msgstr "Ticket > Erste Reaktion" -#: ../settings/security/two-factor/authenticator-app.rst:None -msgid "Authenticator App Switch in Settings" -msgstr "Authenticator App Schalter in den Einstellungen" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.first_response_at}``" +msgstr "``#{ticket.first_response_at}``" -#: ../settings/security/two-factor/authenticator-app.rst:36 -msgid "" -"Now the users will be able to set up this two-factor authentication method " -"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " -"Once they do, on next sign-in with password, they will be asked to provide " -"an additional security code generated by their mobile device." -msgstr "" -"Jetzt können die Nutzer diese Zwei-Faktor-Authentifizierungsmethode für ihre " -"Konten über \"Avatar > Profil > Passwort & Authentifizierung\" einrichten. " -"Sobald sie dies getan haben, werden sie bei der nächsten Anmeldung mit " -"Passwort aufgefordert, einen zusätzlichen Sicherheitscode einzugeben, der " -"von ihrem Mobilgerät generiert wird." +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable yet" +msgstr "``2019-10-07 16:25:00 UTC`` oder leer, wenn noch nicht zutreffend" -#: ../settings/security/two-factor/security-keys.rst:2 -msgid "Security Keys" -msgstr "Sicherheits-Schlüssel" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Assign Follow-Ups" +msgstr "Ticket > Gruppe > Zuweisung bei Nachfrage" -#: ../settings/security/two-factor/security-keys.rst:4 -msgid "" -"The security keys method is a type of a two-factor authentication that uses " -"Web Authentication API in the browser for verifying user's identity. The " -"user can register multiple hardware or software security keys with their " -"Zammad account and then they can use it during the sign-in process." -msgstr "" -"Die Sicherheitsschlüssel-Methode ist eine Art der Zwei-Faktor-" -"Authentifizierung, die die Web-Authentifizierungs-API im Browser zur " -"Überprüfung der Identität des Benutzers verwendet. Der Benutzer kann mehrere " -"Hardware- oder Softwareschlüssel mit seinem Zammad-Konto registrieren und " -"diese dann während des Anmeldevorgangs verwenden." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_assignment}``" +msgstr "``#{ticket.group.follow_up_assignment}``" -#: ../settings/security/two-factor/security-keys.rst:12 -msgid "" -"When logging in, the user is prompted to provide the same security key they " -"registered with their account, in addition to their password. This key acts " -"as the second factor of authentication, providing an extra layer of security." -msgstr "" -"Bei der Anmeldung wird der Benutzer aufgefordert, zusätzlich zu seinem " -"Passwort den hinterlegten Sicherheitsschlüssel anzugeben, den er für sein " -"Konto registriert hat. Dieser Schlüssel dient als zweiter " -"Authentifizierungsfaktor und bietet eine zusätzliche Sicherheitsebene." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Assignment Timeout" +msgstr "Ticket > Gruppe > Zeitliche Zuweisungsüberschreitung" -#: ../settings/security/two-factor/security-keys.rst:None -msgid "Security Key dialog in Safari on macOS" -msgstr "Sicherheitsschlüssel-Dialog in Safari unter macOS" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.assignment_timeout}``" +msgstr "``#{ticket.group.assignment_timeout}``" -#: ../settings/security/two-factor/security-keys.rst:21 -msgid "" -"The type of the key can range from hardware USB sticks to passkeys stored in " -"a device of user's choice. Which type can be used depends on the browser " -"flavor and the platform of the user." -msgstr "" -"Die Art des Schlüssels kann von Hardware-USB-Sticks bis zu Passkeys reichen, " -"die in einem Gerät der Wahl des Nutzers gespeichert sind. Welcher Typ " -"verwendet werden kann, hängt von der Browser-Variante und der Plattform des " -"Nutzers ab." +#: ../misc/variables/ticket.rst:1 +msgid "``20`` or empty if not configured" +msgstr "``20`` oder leer, wenn nicht konfiguriert" -#: ../settings/security/two-factor/security-keys.rst:26 -msgid "Enabling the Security Keys Method" -msgstr "Aktivieren der Sicherheitsschlüssel-Methode" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Follow-up possible" +msgstr "Ticket > Gruppe > Nachfrage möglich" -#: ../settings/security/two-factor/security-keys.rst:None -msgid "Security Keys Switch in Settings" -msgstr "Schalter für Sicherheitsschlüssel in den Einstellungen" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_possible}``" +msgstr "``#{ticket.group.follow_up_possible}``" -#: ../settings/security/two-factor/security-keys.rst:34 -msgid "" -"Now the users will be able to set up this two-factor authentication method " -"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " -"Once they do, on next sign-in with password, they will be asked to provide " -"the same security key they registered during the setup." -msgstr "" -"Jetzt können die Nutzer diese Zwei-Faktor-Authentifizierungsmethode für ihre " -"Konten über \"Avatar > Profil > Passwort & Authentifizierung\" einrichten. " -"Sobald sie dies getan haben, werden sie bei der nächsten Anmeldung mit " -"Passwort aufgefordert, den Sicherheitsschlüssel bereitzustellen, den sie in " -"ihrem Konto hinterlegt haben." +#: ../misc/variables/ticket.rst:1 +msgid "``no`` or ``yes``" +msgstr "``Nein`` oder ``Ja``" -#: ../settings/system/system-selfhosted.include.rst:3 -msgid "" -"Below settings are only available to self hosted users. In hosted " -"environments we're handling these settings for you to ensure service " -"stability." -msgstr "" -"Die nachstehenden Einstellungen sind nur für self-hosting Benutzer " -"verfügbar. In unserem Hosting übernehmen wir diese Einstellungen für Sie, um " -"die Stabilität des Dienstes zu gewährleisten." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Name" +msgstr "Ticket > Gruppe > Name" -#: ../settings/system/base.rst:11 -msgid "Fully Qualified Domain Name" -msgstr "Fully Qualified Domain Name" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.name}``" +msgstr "``#{ticket.group.name}``" -#: ../settings/system/base.rst:7 -msgid "The URL of your Zammad installation." -msgstr "Die URL Ihrer Zammad-Installation." +#: ../misc/variables/ticket.rst:1 +msgid "``Sales``" +msgstr "``Verkauf``" -#: ../settings/system/base.rst:9 ../settings/system/base.rst:17 -msgid "This setting is used within :doc:`/system/variables` and notifications." -msgstr "" -"Diese Einstellung wird in :doc:`/system/variables` und Benachrichtigungen " -"verwendet." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Note" +msgstr "Ticket > Gruppe > Notiz" -#: ../settings/system/system-base.include.rst:1 -msgid "It is automatically set by the *Getting Started wizard*." -msgstr "" -"Diese Einstellung wird automatisch durch den *Einrichtungsassistenten* " -"festgelegt." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.note}``" +msgstr "``#{ticket.group.note}``" -#: ../settings/system/system-base.include.rst:5 -msgid "Changing this setting also changes callback URLs for your channels etc." -msgstr "" -"Durch die Änderung dieser Einstellung werden auch die Callback-URLs für Ihre " -"Kanäle usw. geändert." +#: ../misc/variables/ticket.rst:1 +msgid "``Note about this group``" +msgstr "``Notiz über diese Gruppe``" -#: ../settings/system/system-base.include.rst:6 -msgid "This setting can have negative affects on being able to login." -msgstr "Diese Einstellung kann zu Schwierigkeiten bei der Anmeldung führen." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > ID" +msgstr "Ticket > ID" -#: ../settings/system/base.rst:19 -msgid "HTTP type" -msgstr "HTTP-Typ" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.id}``" +msgstr "``#{ticket.id}``" -#: ../settings/system/base.rst:14 -msgid "" -"The HTTP type tells your installation how your clients connect. This is " -"relevant for authentication and cookie security." -msgstr "" -"Der HTTP-Typ teilt Ihrer Installation mit, wie sich Ihre Clients verbinden. " -"Dies ist wichtig für die Authentifizierung und die Cookie-Sicherheit." +#: ../misc/variables/ticket.rst:1 +msgid "``17``, ``5281``, ..." +msgstr "``17``, ``5281``, ..." -#: ../settings/system/base.rst:31 -msgid "SystemID" -msgstr "SystemID" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact (agent)" +msgstr "Ticket > letzter Kontakt (Agent)" -#: ../settings/system/base.rst:22 -msgid "" -"This ID is being used within your ticket number. In case you're " -"communicating with another ticket system with similar ticket number schemes " -"this ID greatly reduces the risk of false follow ups." -msgstr "" -"Diese ID wird in Ihrer Ticketnummer verwendet. Für den Fall, dass Sie mit " -"einem anderen Ticketsystem mit ähnlichen Nummernschema kommunizieren, " -"verringert diese ID das Risiko falscher Zuordnungen erheblich." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_agent_at}``" +msgstr "``#{ticket.last_contact_agent_at}``" -#: ../settings/system/base.rst:26 -msgid "" -"The SystemID is randomly selected upon installation of Zammad (``1-99``)." -msgstr "" -"Die SystemID wird bei der Installation von Zammad zufällig gesetzt " -"(``1-99``)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact (customer)" +msgstr "Ticket > letzter Kontakt (Kunde)" -#: ../settings/system/base.rst:30 +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_customer_at}``" +msgstr "``#{ticket.last_contact_customer_at}``" + +#: ../misc/variables/ticket.rst:1 msgid "" -"**Do not** change this setting in a productive system! Your Zammad " -"installation may no longer recognize old ticket number based follow ups upon " -"change!" +"``2019-10-07 16:25:00 UTC`` or empty if not applicable yet (Please note " +"`Ticket last contact behavior Settings `_ for this)" msgstr "" -"**Ändern Sie diese Einstellung nicht** in einem produktiven System! Ihre " -"Zammad-Installation erkennt bei einer Änderung möglicherweise auf alten " -"Ticketnummern basierende Rückfragen nicht mehr!" - -#: ../settings/system/frontend.rst:2 -msgid "Frontend" -msgstr "Frontend" +"``2019-10-07 16:25:00 UTC`` oder leer, wenn noch nicht zutreffend (bitte " +"beachten Sie hierzu `Ticketeinstellung letzter Kontakt `_)" -#: ../settings/system/frontend.rst:22 -msgid "Core Workflow Ajax Mode" -msgstr "Core Workflow Ajax Modus" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact" +msgstr "Ticket > letzter Kontakt" -#: ../settings/system/frontend.rst:6 -msgid "" -"This setting allows administrators to enforce :doc:`/system/core-workflows` " -"to use Ajax-Calls instead of web sockets. You'll usually only need this if " -"you experience serious issues as noted below." -msgstr "" -"Mit dieser Einstellung können Administratoren erzwingen, dass :doc:`/system/" -"core-workflows` Ajax-Aufrufe anstelle von Web-Sockets verwendet werden. Dies " -"ist in der Regel nur dann erforderlich, wenn schwerwiegende Probleme " -"auftreten (siehe unten)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_at}``" +msgstr "``#{ticket.last_contact_at}``" -#: ../settings/system/frontend.rst:10 -msgid "**🤓 Possible (technical) reasons**" -msgstr "**🤓 Mögliche (technische) Gründe**" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Number" +msgstr "Ticket > Nummer" -#: ../settings/system/frontend.rst:12 -msgid "" -"In some cases, your network structure (e.g. firewalls, proxies) may " -"disconnect long web socket connections. This leads to select fields staying " -"empty (e.g. owner selection *after* selecting your group) or fields not " -"shown / hidden (e.g. when switching to or from pending states, the \"pending " -"till\" field not showing / hiding)." -msgstr "" -"In einigen Fällen kann es vorkommen, dass Ihr Netzwerk (z.B. Firewalls, " -"Proxys) lange Web-Socket-Verbindungen unterbricht. Dies führt dazu, dass " -"Auswahlfelder leer bleiben (z.B. Auswahl des Besitzers *nach* " -"Gruppenauswahl) oder Felder nicht angezeigt/ausgeblendet werden (z.B. beim " -"Wechsel in oder in den Status \"Warten auf\" wird das Feld \"Warten bis\" " -"nicht angezeigt/ausgeblendet)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.number}``" +msgstr "``#{ticket.number}``" -#: ../settings/system/frontend.rst:18 -msgid "" -"Please keep in mind that the Ajax fallback may cause serious pressure on " -"your application server. If you have the choice stick to web sockets." -msgstr "" -"Bitte bedenken Sie, dass der Ajax-Fallback Ihren Server stark belasten kann. " -"Wenn Sie die Wahl haben, bleiben Sie bei Web-Sockets." +#: ../misc/variables/ticket.rst:1 +msgid "``31001``, ``201910731001``, ..." +msgstr "``31001``, ``201910731001``, ..." -#: ../settings/system/frontend.rst:22 -msgid "Default: ``no`` (inactive)" -msgstr "Voreinstellung: ``nein`` (inaktiv)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain based assignment" +msgstr "Ticket > Organisation > Domain basierte Zuordnung" -#: ../settings/system/frontend.rst:53 -msgid "Show calendar weeks in the picker of date/datetime fields" -msgstr "Kalenderwochen im Datums-Auswahlfeld anzeigen" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain_assignment}``" +msgstr "``#{ticket.organization.domain_assignment}``" -#: ../settings/system/frontend.rst:25 -msgid "" -"With this setting you can instruct Zammad to provide week number display " -"globally for all users. Calendar with week number display are usually used " -"in business sectors and may not be relevant for everyone." -msgstr "" -"Mit dieser Einstellung können Sie Zammad die Kalenderwochen global für alle " -"Benutzer in entsprechenden Auswahlfeldern anzeigen lassen. Kalender mit " -"Wochennummern werden nur in manchen Geschäftsbereichen verwendet und sind " -"möglicherweise nicht für jeden relevant." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain" +msgstr "Ticket > Organisation > Domain" -#: ../settings/system/frontend.rst:29 -msgid "" -"This setting affects *all areas* - you'll also see week numbers in the admin " -"panel for e.g. triggers and macros." -msgstr "" -"Diese Einstellung wirkt sich auf *alle Bereiche* aus - Sie sehen die " -"Wochennummern auch im Verwaltungsbereich für z.B. Trigger und Makros." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain}``" +msgstr "``#{ticket.organization.domain}``" -#: ../settings/system/frontend.rst:32 -msgid "Default: ``no`` (not shown)" -msgstr "Voreinstellung: ``nein`` (nicht angezeigt)" +#: ../misc/variables/ticket.rst:1 +msgid "``domain.tld`` or empty if not set" +msgstr "``domain.tld`` oder leer wenn nicht gesetzt" -#: ../settings/system/frontend.rst:53 -msgid "Here's the difference:" -msgstr "Hier sehen Sie den Unterschied:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Name" +msgstr "Ticket > Organisation > Name" -#: ../settings/system/frontend.rst:0 -msgid "Screenshot showing Zammad's date picker (in the default way)" -msgstr "Screenshot mit Datumsauswahl von Zammad (Standardeinstellung)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.name}``" +msgstr "``#{ticket.organization.name}``" -#: ../settings/system/frontend.rst:41 -msgid "Set to ``no``" -msgstr "Auf ``Nein`` gesetzt" +#: ../misc/variables/ticket.rst:1 +msgid "``Zammad GmbH`` or empty if not set" +msgstr "``Zammad GmbH`` oder leer wenn nicht gesetzt" -#: ../settings/system/frontend.rst:0 -msgid "" -"Screenshot showing Zammad's date picker with\n" -"week numbers enabled" -msgstr "" -"Screenshot zeigt die Datumsauswahl von Zammad mit aktivierten Kalenderwochen" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Note" +msgstr "Ticket > Organisation > Notiz" -#: ../settings/system/frontend.rst:50 -msgid "Set to ``yes``" -msgstr "Auf ``Ja`` gesetzt" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.note}``" +msgstr "``#{ticket.organization.note}``" -#: ../settings/system/index.rst:4 -msgid "" -"For your overview we split each tab within system settings into its own page:" -msgstr "" -"Der Übersicht halber haben wir jeden Tab der Systemeinstellungen in eine " -"eigene Seite aufgeteilt:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Shared organization" +msgstr "Ticket > Organisation > geteilte Organisation" -#: ../settings/system/index.rst:16 -msgid "Console Based Settings" -msgstr "Konsolenbasierte Einstellungen" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.shared}``" +msgstr "``#{ticket.organization.shared}``" -#: ../settings/system/index.rst:18 -msgid "" -"There's some console based settings we didn't put into the UI. However, you " -"may find them helpful - you can find them in our :docs:`hidden settings ` section." -msgstr "" -"Es gibt einige Konsolen-Einstellungen, die nicht in der Benutzeroberfläche " -"vorgenommen werden können. Falls Sie mehr dazu erfahren wollen können Sie " -"diese unter :docs:`versteckte Einstellungen` in der Systemdokumentation finden." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > VIP" +msgstr "Ticket > Organisation > VIP" -#: ../settings/system/network.rst:2 -msgid "Network" -msgstr "Netzwerk" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.vip}``" +msgstr "``#{ticket.organization.vip}``" -#: ../settings/system/network.rst:8 -msgid "" -"The proxy settings can only be saved after successfully testing the proxy " -"connection." -msgstr "" -"Die Proxy-Einstellungen können erst nach erfolgreichem Testen der Proxy-" -"Verbindung gespeichert werden." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Address" +msgstr "Ticket > Besitzer > Adresse" -#: ../settings/system/network.rst:15 -msgid "Proxy Address." -msgstr "Proxy-Adresse." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.address}``" +msgstr "``#{ticket.owner.address}``" -#: ../settings/system/network.rst:12 -msgid "" -"Allows you to provide a proxy server if needed. This is relevant for network " -"communication by Zammad." -msgstr "" -"Ermöglicht es Ihnen, bei Bedarf einen Proxyserver bereitzustellen. Dies ist " -"für die Netzwerkkommunikation von Zammad relevant." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Avatar" +msgstr "Ticket > Besitzer > Avatar" -#: ../settings/system/network.rst:15 -msgid "It **does not** affect the update process or Elasticsearch." -msgstr "" -"Sie **beeinflusst nicht** den Aktualisierungsprozess und Elasticsearch." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.avatar(60,60)}``" +msgstr "``#{ticket.owner.avatar(60,60)}``" -#: ../settings/system/network.rst:18 -msgid "Username for proxy connection." -msgstr "Benutzername für Verbindung zum Proxy." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Department" +msgstr "Ticket > Besitzer > Abteilung" -#: ../settings/system/network.rst:18 -msgid "" -"If your proxy server requires authentication, provide the username here." -msgstr "" -"Wenn Ihr Proxyserver eine Authentifizierung erfordert, geben Sie hier den " -"Benutzernamen an." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.department}``" +msgstr "``#{ticket.owner.department}``" -#: ../settings/system/network.rst:21 -msgid "Password for proxy connection." -msgstr "Passwort für Verbindung zum Proxy." +#: ../misc/variables/ticket.rst:1 +msgid "``Support`` or empty if not set" +msgstr "``Support`` oder leer wenn nicht gesetzt" -#: ../settings/system/network.rst:21 -msgid "" -"If your proxy server requires authentication, provide the password here." -msgstr "" -"Wenn Ihr Proxyserver eine Authentifizierung erfordert, geben Sie hier das " -"Passwort ein." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Email" +msgstr "Ticket > Besitzer > Email" -#: ../settings/system/network.rst:26 -msgid "No proxy for the following hosts." -msgstr "Keinen Proxy für die folgenden Hosts verwenden." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.email}``" +msgstr "``#{ticket.owner.email}``" -#: ../settings/system/network.rst:24 -msgid "" -"Exception list for hosts you can't or don't want to reach via proxy server." -msgstr "" -"Ausnahmeliste für Hosts, die Sie nicht über den Proxyserver erreichen können " -"oder wollen." +#: ../misc/variables/ticket.rst:1 +msgid "``agent@company.tld`` or empty if not set" +msgstr "``agent@firma.tld`` oder leer wenn nicht gesetzt" -#: ../settings/system/network.rst:27 -msgid "Default: ``localhost,127.0.0.0,::1``" -msgstr "Voreinstellung: ``localhost,127.0.0.0,::1``" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Fax" +msgstr "Ticket > Besitzer > Fax" -#: ../settings/system/services.rst:2 -msgid "Services" -msgstr "Dienste" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.fax}``" +msgstr "``#{ticket.owner.fax}``" -#: ../settings/system/services.rst:10 -msgid "Image Service" -msgstr "Bilder-Dienst" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Firstname" +msgstr "Ticket > Besitzer > Vorname" -#: ../settings/system/services.rst:5 -msgid "Defines the backend for user and organization image lookups." -msgstr "" -"Definierte das Backend für Bildersuchen von Benutzern und Organisationen." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.firstname}``" +msgstr "``#{ticket.owner.firstname}``" -#: ../settings/system/services.rst:7 -msgid "Default: ``Zammad Image Service`` (active)" -msgstr "Standard: ``Zammad Image Service`` (aktiv)" +#: ../misc/variables/ticket.rst:1 +msgid "``Max`` or empty if not set" +msgstr "``Max`` oder leer wenn nicht gesetzt" -#: ../settings/system/services.rst:9 -msgid "" -"Make sure your on premise installation has ``HTTPS`` access to ``images." -"zammad.com``." -msgstr "" -"Stellen Sie sicher, dass Ihre Installation vor Ort per ``HTTPS`` Zugriff auf " -"``images.zammad.com`` hat." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Lastname" +msgstr "Ticket > Besitzer > Nachname" -#: ../settings/system/services.rst:18 -msgid "Geo Calendar Service" -msgstr "Geo-Kalender-Dienst" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.lastname}``" +msgstr "``#{ticket.owner.lastname}``" -#: ../settings/system/services.rst:13 -msgid "" -"Defines the backend for geo calendar lookups. Used for initial calendar " -"setup." -msgstr "" -"Definiert das Backend für Geo-Kalender-Lookups. Wird für die " -"Kalendereinrichtung verwendet." +#: ../misc/variables/ticket.rst:1 +msgid "``Mustermann`` or empty if not set" +msgstr "``Mustermann`` oder leer wenn nicht gesetzt" -#: ../settings/system/services.rst:16 -msgid "Default: ``Zammad GeoCalendar Service`` (active)" -msgstr "Standard: ``Zammad GeoCalendar Service`` (aktiv)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Login" +msgstr "Ticket > Besitzer > Login" -#: ../settings/system/services.include.rst:2 -msgid "" -"Make sure your on premise installation has ``HTTPS`` access to ``geo.zammad." -"com``." -msgstr "" -"Stellen Sie sicher, dass Ihre Installation vor Ort per ``HTTPS`` Zugriff auf " -"``geo.zammad.com`` hat." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.login}``" +msgstr "``#{ticket.owner.login}``" -#: ../settings/system/services.rst:26 -msgid "Geo IP Service" -msgstr "Geo-IP-Service" +#: ../misc/variables/ticket.rst:1 +msgid "``agent``" +msgstr "``agent``" -#: ../settings/system/services.rst:21 -msgid "" -"Defines the backend for geo IP lookups. Shows also location of an IP address " -"if an IP address is shown." -msgstr "" -"Definiert das Backend für Geo-IP-Lookups. Zeigt auch den Standort einer IP-" -"Adresse an, wenn eine IP-Adresse angezeigt wird." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Mobile" +msgstr "Ticket > Besitzer > Mobil" -#: ../settings/system/services.rst:24 -msgid "Default: ``Zammad GeoIP Service`` (active)" -msgstr "Voreinstellung: ``Zammad GeoIP Service`` (aktiv)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.mobile}``" +msgstr "``#{ticket.owner.mobile}``" -#: ../settings/system/services.rst:32 -msgid "Geo Location Service" -msgstr "Geo-Lokalisierungs-Service" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Note" +msgstr "Ticket > Besitzer > Notiz" -#: ../settings/system/services.rst:29 -msgid "" -"Defines the backend for geo location lookups to store geo locations for " -"addresses." -msgstr "" -"Definiert das Backend für Geo-Standortabfragen, um Geo-Standorte für IP-" -"Adressen zu speichern." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.note}``" +msgstr "``#{ticket.owner.note}``" -#: ../settings/system/services.rst:32 -msgid "" -"Default: ``OpenStreetMap (ODbL 1.0, http://osm.org/copyright)`` (active)" -msgstr "" -"Voreinstellung: ``OpenStreetMap (ODbL 1.0, http://osm.org/copyright)`` " -"(aktiv)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Phone" +msgstr "Ticket > Besitzer > Telefon" -#: ../settings/system/services.rst:36 -msgid "" -"You can find a detailed privacy information on what we store for how long on " -"our :docs:`Privacy Appendix ` inside of our System " -"Documentation." -msgstr "" -"Detaillierte Informationen zum Datenschutz, was wir wie lange speichern, " -"finden Sie in unserem :docs:`Datenschutzhinweisen ` " -"in unserer Systemdokumentation." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.phone}``" +msgstr "``#{ticket.owner.phone}``" -#: ../settings/system/storage.rst:2 -msgid "Storage" -msgstr "Speicher" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > VIP" +msgstr "Ticket > Besitzer > VIP" -#: ../settings/system/storage.rst:6 -msgid "" -"Here you can define where Zammad stores attachments for tickets and the " -"knowledge base. By default, we're writing to the ``Database`` - you can " -"switch to ``Filesystem`` or ``Simple Storage (S3)`` at any time. In this " -"case please have a look on the following instructions." -msgstr "" -"Hier können Sie festlegen, wo Zammad Anhänge für Tickets und die Knowledge " -"Base speichert. Standardmäßig wird die ``Datenbank`` dafür verwendet - Sie " -"können jederzeit auf ``Dateisystem`` oder ``Simple Storage (S3)`` " -"umschalten. Schauen Sie sich dazu bitte die folgende Anleitung an." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.vip}``" +msgstr "``#{ticket.owner.vip}``" -#: ../settings/system/storage.rst:11 -msgid "" -"If you have a busy Zammad instance, we strongly encourage you to use " -"filesystem storage instead of \"Database\". This will greatly improve system " -"performance (de-crease database load and size)." -msgstr "" -"Wenn Sie eine ausgelastete Zammad-Instanz haben, empfehlen wir Ihnen " -"dringend, \"Dateisystem\" anstelle von \"Datenbank\" als Speichermethode zu " -"verwenden. Dies wird die Systemleistung erheblich verbessern (Verringerung " -"der Datenbanklast und -größe)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Web" +msgstr "Ticket > Besitzer > Web" -#: ../settings/system/storage.rst:19 -msgid "Database" -msgstr "Datenbank" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.web}``" +msgstr "``#{ticket.owner.web}``" -#: ../settings/system/storage.rst:17 -msgid "" -"This is the default storage method. The attachments are stored directly in " -"the database. If your Zammad instance grows, we recommend one of the other " -"methods to maintain performance." -msgstr "" -"Dies ist die Standard-Speichermethode. Die Anhänge werden direkt in der " -"Datenbank gespeichert. Wenn Ihre Zammad-Instanz wächst, empfehlen wir eine " -"der anderen Methoden, um keine Einschränkungen bzgl. Leistung zu bekommen." +#: ../misc/variables/ticket.rst:1 +msgid "``https://zammad.com`` or empty if not set" +msgstr "``https://zammad.com`` oder leer wenn nicht gesetzt" -#: ../settings/system/storage.rst:38 -msgid "Filesystem" -msgstr "Dateisystem" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Pending till" +msgstr "Ticket > warten bis" -#: ../settings/system/storage.rst:22 -msgid "" -"This storage method is recommended for all Zammad instances, especially for " -"those with a higher load. If you choose filesystem, your files are written " -"to ``/opt/zammad/storage/``." -msgstr "" -"Diese Speichermethode wird für alle Zammad-Instanzen empfohlen, insbesondere " -"für solche mit einer höheren Last. Wenn Sie Dateisystem wählen, werden Ihre " -"Dateien nach ``/opt/zammad/storage/`` geschrieben." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.pending_time}``" +msgstr "``#{ticket.pending_time}``" -#: ../settings/system/storage.rst:26 -msgid "" -"Moving attachments from \"Database\" to \"Filesystem\" can be run during " -"production use. However, you should consider your framework conditions (e.g. " -"bandwidth, system load in production) to define the right moment." -msgstr "" -"Das Verschieben von Anhängen aus der Datenbank in das Dateisystem kann " -"während des Betriebs von Zammad durchgeführt werden. Sie sollten jedoch Ihre " -"Rahmenbedingungen (z.B. Bandbreite, Systemlast in der Produktion) " -"berücksichtigen, um den richtigen Zeitpunkt zu bestimmen." +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not set" +msgstr "``2019-10-07 16:25:00 UTC`` oder leer wenn nicht gesetzt" -#: ../settings/system/storage.rst:32 -msgid "**You noticed slow updates of Zammad?**" -msgstr "**Haben Sie langsame Aktualisierungen von Zammad festgestellt?**" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Priority > Name" +msgstr "Ticket > Priorität > Name" -#: ../settings/system/storage.rst:34 -msgid "" -"While Zammad is beeing updated, it enforces a recursive \"change " -"owner\" (chown) for this directory. For instances with many files this can " -"be time consuming. To mitigate that you can move your files and create a " -"symlink in ``/opt/zammad/storage/`` to the new directory. Of course you have " -"to make sure on your own that the permissions are always correct." -msgstr "" -"Während Zammad aktualisiert wird, wird das ganze Verzeichnis rekursiv per " -"\"change owner\" (chown) aktualisiert. Für Instanzen mit vielen Dateien kann " -"dies sehr zeitaufwendig sein. Um das zu vermeiden, können Sie Ihre Dateien " -"verschieben und eine symbolische Verlinkung (Symlink) in ``/opt/zammad/" -"storage/`` auf das neue Verzeichnis erstellen. Natürlich müssen Sie dann " -"selbst dafür sorgen, dass die Berechtigungen immer korrekt sind." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.priority.name}``" +msgstr "``#{ticket.priority.name}``" -#: ../settings/system/storage.rst:95 -msgid "Simple Storage (S3)" -msgstr "Simple Storage (S3)" +#: ../misc/variables/ticket.rst:1 +msgid "``2 normal``" +msgstr "``2 normal``" -#: ../settings/system/storage.rst:41 -msgid "" -"To use the Simple Storage (S3), you have to provide some settings, which " -"can't be accessed in the UI (see instructions below)." -msgstr "" -"Um Simple Storage (S3) zu nutzen, müssen Sie einige Einstellungen vornehmen, " -"die nicht über die Benutzeroberfläche zugänglich sind (siehe Anleitung " -"unten)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > State > Name" +msgstr "Ticket > Status > Name" -#: ../settings/system/storage.rst:44 -msgid "" -"⚠️ Please note that the current implementation is in its early stages and can " -"be modified in the future." -msgstr "" -"⚠️ Bitte beachten Sie, dass sich die derzeitige Umsetzung noch im " -"Anfangsstadium befindet und sich in Zukunft Änderungen ergeben können." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.state.name}``" +msgstr "``#{ticket.state.name}``" -#: ../settings/system/storage.rst:47 -msgid "" -"The prerequisite is to have access to a S3-compatible storage and to have " -"all necessary parameters available (which depends on your storage provider; " -"if in doubt, please ask there for help)." -msgstr "" -"Voraussetzung ist, dass Sie Zugang zu einem S3-kompatiblen Speicher haben " -"und alle notwendigen Parameter vorliegen (das hängt von Ihrem " -"Speicheranbieter ab; im Zweifelsfall fragen Sie bitte dort nach)." +#: ../misc/variables/ticket.rst:1 +msgid "``new``, ``open``, ..." +msgstr "``new``, ``open``, ..." -#: ../settings/system/storage.rst:51 -msgid "Steps to configure S3:" -msgstr "Schritte zur Konfiguration von S3:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Tags" +msgstr "Ticket > Schlagworte" -#: ../settings/system/storage.rst:53 +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.tags}``" +msgstr "``#{ticket.tags}``" + +#: ../misc/variables/ticket.rst:1 msgid "" -"Copy ``config/zammad/storage.yml.dist`` to ``config/zammad/storage.yml``" +"Currently not available, see `Issue 2769 `_" msgstr "" -"Kopieren Sie ``config/zammad/storage.yml.dist`` nach ``config/zammad/storage." -"yml``" +"Derzeit nicht verfügbar, siehe `Issue 2769 `_" -#: ../settings/system/storage.rst:54 -msgid "Edit the copied file in one of the following ways:" -msgstr "Bearbeiten Sie die kopierte Datei auf eine der folgenden Arten:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Title" +msgstr "Ticket > Titel" -#: ../settings/system/storage.rst:56 -msgid "" -"Either provide your S3 configuration with one attribute per line like in the " -"upper area of the file" -msgstr "" -"Entweder Sie erstellen Ihre S3-Konfiguration mit einem Attribut pro Zeile " -"wie im oberen Bereich der Datei" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.title}``" +msgstr "``#{ticket.title}``" -#: ../settings/system/storage.rst:58 +#: ../misc/variables/ticket.rst:1 msgid "" -"Or provide your S3 configuration as an URL (which you can find at the end of " -"the file). Note: you can also provide this URL as environment variable (:" -"docs:`see system documentation `) without using this yml-file." +"``My amazing Subject`` (normally subject, can be edited within Interface and " +"thus differ)" msgstr "" -"Oder Sie geben Ihre S3-Konfiguration als URL an (die Sie am Ende der Datei " -"finden). Hinweis: Sie können diese URL auch als Umgebungsvariable angeben (:" -"docs:`siehe System Documentation `) , ohne diese yml-Datei zu verwenden." +"``Mein super Betreff`` (normalerweise Betreff, kann im Interface bearbeitet " +"werden und somit abweichen)" -#: ../settings/system/storage.rst:62 -msgid "" -"We recommend the deletion of the not used configuration style to avoid " -"inconsistencies." -msgstr "" -"Wir empfehlen die Löschung der nicht verwendeten Konfiguration, um " -"Inkonsistenzen zu vermeiden." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated at" +msgstr "Ticket > Aktualisiert am" -#: ../settings/system/storage.rst:65 -msgid "Restart Zammad so the config file / environment variable is loaded" -msgstr "" -"Zammad neu starten, damit die Konfigurationsdatei / Umgebungsvariable " -"geladen wird" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_at}``" +msgstr "``#{ticket.updated_at}``" -#: ../settings/system/storage.rst:66 -msgid "" -"Set the \"Storage Method\" in Zammad to ``Simple Storage (S3)`` in Settings " -"> System > Storage and click on \"Submit\". After that, Zammad checks your " -"configuration and the connection to the service and will raise an error " -"message if something is wrong." -msgstr "" -"Setzen Sie die \"Speichermethode\" in Zammad auf ``Simple Storage (S3)`` in " -"Einstellungen > System > Speicher und klicken Sie auf \"Übermitteln\". " -"Danach überprüft Zammad Ihre Konfiguration und die Verbindung zum Dienst und " -"gibt eine Fehlermeldung aus, wenn etwas nicht stimmt." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Address" +msgstr "Ticket > Aktualisiert von > Adresse" -#: ../settings/system/storage.rst:72 -msgid "A very simple storage configuration could look like this:" -msgstr "Eine sehr einfache Speicherkonfiguration könnte wie folgt aussehen:" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.address}``" +msgstr "``#{ticket.updated_by.address}``" -#: ../settings/system/storage.rst:85 -msgid "" -"Before setting the storage method to ``Simple Storage (S3)`` (step 4), " -"please make sure to have a working setup." -msgstr "" -"Bevor Sie die Speichermethode auf ``Simple Storage (S3)`` einstellen " -"(Schritt 4), stellen Sie bitte sicher, dass Sie ein funktionierendes Setup " -"haben." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Avatar" +msgstr "Ticket > Aktualisiert von > Avatar" -#: ../settings/system/storage.rst:88 -msgid "" -"You can verify this by running ``rails r 'Rails.logger = Logger.new(STDOUT); " -"pp Store::Provider::S3.ping?'`` in your Zammad directory. If everything is " -"fine, you should see ``true``, else you should see ``false`` and a simple " -"error message." -msgstr "" -"Sie können dies überprüfen, indem Sie ``rails r 'Rails.logger = Logger." -"new(STDOUT); pp Store::Provider::S3.ping?'`` in Ihrem Zammad Verzeichnis " -"ausführen. Wenn alles in Ordnung ist, wird ein ``true`` ausgegeben, " -"ansonsten wird ``false`` und eine einfache Fehlermeldung ausgegeben." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.avatar(60,60)}``" +msgstr "``#{ticket.updated_by.avatar(60,60)}``" -#: ../settings/system/storage.rst:93 -msgid "" -"If you installed Zammad through a package manager (rather than from source), " -"replace ``rails r`` with ``zammad run rails r`` above. To learn more, see :" -"docs:`Administration via Console `." -msgstr "" -"Sofern Sie Zammad über einen Paketmanager (keine Source-Installation) " -"installiert haben, ersetzen Sie ``rails r`` mit ``zammad run rails r``. Für " -"weitere Information siehe :docs:`Administration via Konsole `." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Department" +msgstr "Ticket > Aktualisiert von > Abteilung" -#: ../settings/ticket.rst:4 -msgid "" -"Here you can adjust general ticket settings. Additional ones for the ticket " -"composer interface can be found in the :doc:`/misc/composer`." -msgstr "" -"Hier können Sie allgemeine Einstellungen für Tickets vornehmen. Zusätzliche " -"Einstellungen finden Sie im :doc:`/misc/composer`." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.department}``" +msgstr "``#{ticket.updated_by.department}``" -#: ../settings/ticket.rst:11 -msgid "Ticket Hook (default: ``Ticket#``)" -msgstr "Ticket-Hook (Standard: ``Ticket#``)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Email" +msgstr "Ticket > Aktualisiert von > Email" -#: ../settings/ticket.rst:11 -msgid "The identifier for a ticket; *e.g.,* Ticket#, Call#, MyTicket#." -msgstr "Die Bezeichnung für ein Ticket; *z.B.* Ticket#, Anruf#, MeinTicket#." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.email}``" +msgstr "``#{ticket.updated_by.email}``" -#: ../settings/ticket.rst:38 -msgid "Ticket Hook Position (default: ``right``)" -msgstr "Position des Ticket-Hooks (Standard: ``rechts``)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Fax" +msgstr "Ticket > Aktualisiert von > Fax" -#: ../settings/ticket.rst:14 -msgid "" -"With this setting you can decide (if) where to insert the ticket number." -msgstr "" -"Mit dieser Einstellung können Sie festlegen, ob und wo die Ticketnummer " -"eingefügt werden soll." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.fax}``" +msgstr "``#{ticket.updated_by.fax}``" -#: ../settings/ticket.rst:20 -msgid "*Right*" -msgstr "*Rechts*" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Firstname" +msgstr "Ticket > Aktualisiert von > Vorname" -#: ../settings/ticket.rst:17 -msgid "" -"This setting will add the ticket reference on the right site of the subject." -msgstr "" -"Mit dieser Einstellung wird die Ticketreferenz auf der rechten Seite des " -"Betreffs hinzugefügt." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.firstname}``" +msgstr "``#{ticket.updated_by.firstname}``" -#: ../settings/ticket.rst:20 -msgid "Example: ``Some Subject [Ticket#12345]``" -msgstr "Beispiel: ``Ein Betreff [Ticket#12345]``" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Lastname" +msgstr "Ticket > Aktualisiert von > Nachname" -#: ../settings/ticket.rst:26 -msgid "*Left*" -msgstr "*Links*" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.lastname}``" +msgstr "``#{ticket.updated_by.lastname}``" -#: ../settings/ticket.rst:23 -msgid "" -"This setting will add the ticket reference on the left site of the subject." -msgstr "" -"Mit dieser Einstellung wird die Ticketreferenz auf der linken Seite des " -"Betreffs hinzugefügt." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Login" +msgstr "Ticket > Aktualisiert von > Login" -#: ../settings/ticket.rst:26 -msgid "Example: ``[Ticket#12345] Some Subject``" -msgstr "Beispiel: ``[Ticket#12345] Ein Betreff``" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.login}``" +msgstr "``#{ticket.updated_by.login}``" -#: ../settings/ticket.rst:29 -msgid "*None*" -msgstr "*Keine*" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Mobile" +msgstr "Ticket > Aktualisiert von > Mobil" -#: ../settings/ticket.rst:29 -msgid "This will completely remove ticket references from the subject." -msgstr "Dies entfernt vollständige Ticket-Referenzen aus dem Betreff." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.mobile}``" +msgstr "``#{ticket.updated_by.mobile}``" -#: ../settings/ticket.rst:33 -msgid "" -"Please ensure to take a look at :doc:`/channels/email/settings` within the " -"email channel to ensure you have at least one reference that helps Zammad to " -"assign follow-ups correctly." -msgstr "" -"Bitte werfen Sie vorab einen Blick auf :doc:`/channels/email/settings` " -"innerhalb des E-Mail-Kanals und stellen sicher, dass Sie mindestens eine " -"Referenz für die Zuordnung von Tickets bei Rückfragen eingerichtet haben." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Note" +msgstr "Ticket > Aktualisiert von > Notiz" -#: ../settings/ticket.rst:37 -msgid "" -"Disabling this and not setting up any further follow up search will lead to " -"unexpected results!" -msgstr "" -"Wenn Sie diese Funktion deaktivieren und keine andere Zuordnung eingerichtet " -"haben, wird dies zu unerwarteten Ergebnissen führen!" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.note}``" +msgstr "``#{ticket.updated_by.note}``" -#: ../settings/ticket.rst:65 -msgid "" -"Ticket Last Contact Behaviour (default: ``Use the start time of the last " -"customer thread (which may consist of multiple articles).``)" -msgstr "" -"Verhalten der Aktualisierung des letzter Kundenkontakts (Standard: " -"``Verwenden Sie die Startzeit des letzten Kunden-Threads (der aus mehreren " -"Artikeln bestehen kann).``)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Phone" +msgstr "Ticket > Aktualisiert von > Telefon" -#: ../settings/ticket.rst:41 -msgid "" -"This setting changes the way Zammad updates the ``Last Contact`` value of a " -"ticket. This is fairly important for overviews and what you expect upon " -"ticket updates of a customer." -msgstr "" -"Diese Einstellung ändert die Art und Weise, wie Zammad den ``Letzten " -"Kontakt`` eines Tickets aktualisiert. Dies ist wichtig für Übersichten und " -"für das Verhalten bei Ticketaktualisierungen." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.phone}``" +msgstr "``#{ticket.updated_by.phone}``" -#: ../settings/ticket.rst:52 -msgid "" -"Use the start time of the last customer thread (which may consist of " -"multiple articles)." -msgstr "" -"Verwenden Sie die Startzeit des letzten Kunden-Threads (der aus mehreren " -"Artikeln bestehen kann)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > VIP" +msgstr "Ticket > Aktualisiert von > VIP" -#: ../settings/ticket.rst:46 -msgid "" -"If this option is chosen, Zammad will update the last updated value just " -"once if a customer replies. After that, Zammad will wait for an agent to " -"react." -msgstr "" -"Wenn diese Option gewählt wird, wird Zammad den zuletzt aktualisierten Wert " -"nur einmal aktualisieren, wenn ein Kunde antwortet. Danach wartet Zammad auf " -"die Reaktion eines Agenten." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.vip}``" +msgstr "``#{ticket.updated_by.vip}``" -#: ../settings/ticket.rst:50 -msgid "" -"This comes in handy if you want to work tickets in the order of their first " -"update. This will not change ticket orders if customers decide to \"bump\" " -"the ticket affected." -msgstr "" -"Dies ist praktisch, wenn Sie Tickets in der Reihenfolge ihrer ersten " -"Aktualisierung bearbeiten möchten. Die Reihenfolge der Tickets ändert sich " -"nicht, wenn die Kunden beschließen, das Ticket mit einer erneuten Rückfrage " -"zu aktualisieren." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Web" +msgstr "Ticket > Aktualisiert von > Web" -#: ../settings/ticket.rst:57 -msgid "Use the time of the very last customer article." -msgstr "Verwenden Sie den Zeitpunkt des allerletzten Kundenartikels." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.web}``" +msgstr "``#{ticket.updated_by.web}``" -#: ../settings/ticket.rst:55 +#: ../settings/branding.rst:10 +msgid "Product Name" +msgstr "Produktname" + +#: ../settings/branding.rst:7 msgid "" -"When setting this option, Zammad will always update the last updated value. " -"This means that if ordering by ``Last Update``, ticket orders will change if " -"customers \"bump\" the ticket." +"Defines the name of the application, shown in the web interface, tabs and " +"title bar of the web browser." msgstr "" -"Wenn diese Option gesetzt ist, wird Zammad immer den Wert der letzten " -"Aktualisierung verwenden. Die Reihenfolge der Tickets ändert sich, wenn die " -"Kunden beschließen, das Ticket mit einer erneuten Rückfrage zu aktualisieren." +"Legt den Namen der Applikation fest, welcher im Web-Interface, in Tabs und " +"in der Titelseite des Webbrowsers angezeigt wird." -#: ../settings/ticket.rst:64 -msgid "Last contact value used on :doc:`/manage/overviews`" -msgstr "Letzter Kontakt für :doc:`/manage/overviews` verwendet" +#: ../settings/branding.rst:10 +msgid "Default value: ``Zammad Helpdesk``" +msgstr "Standardwert: ``Zammad Helpdesk``" -#: ../settings/ticket.rst:65 -msgid "Last contact value used on :doc:`/manage/trigger`" -msgstr "Letzter Kontakt für :doc:`/manage/trigger` verwendet" +#: ../settings/branding.rst:13 +msgid "Will be shown in the app and is included in email footers." +msgstr "Wird in der App und in der E-Mail-Fußzeile angezeigt." -#: ../settings/ticket.rst:88 -msgid "" -"Ticket Organization Reassignment (default: ``Update the most recent tickets." -"``)" +#: ../settings/branding.rst:19 +msgid "Logo" +msgstr "Logo" + +#: ../settings/branding.rst:16 +msgid "Defines the logo of the application, shown in the login page of Zammad." msgstr "" -"Neuzuweisung der Ticket-Organisation (Voreinstellung: ``Die neuesten Tickets " -"aktualisieren.``)" +"Legt das Logo der Anwendung fest, das auf der Anmeldeseite von Zammad " +"angezeigt wird." -#: ../settings/ticket.rst:68 +#: ../settings/branding.rst:18 msgid "" -"This setting changes the way Zammad updates the organization field of the " -"tickets whenever the primary organization of a user is changed." +"Ensure to hit the \"Submit\" button after uploading the logo. Otherwise your " +"change will not be saved." msgstr "" -"Diese Einstellung definiert, ob Zammad die Organisation der Tickets " -"aktualisiert, wenn die primäre Organisation eines Benutzers geändert wird." - -#: ../settings/ticket.rst:74 -msgid "Update the most recent tickets." -msgstr "Die neuesten Tickets aktualisieren." +"Klicken Sie nach dem Hochladen des Logos auf die Schaltfläche \"Senden\". " +"Andernfalls wird Ihre Änderung nicht gespeichert." -#: ../settings/ticket.rst:72 +#: ../settings/branding.rst:22 msgid "" -"If this option is chosen, Zammad will update the 100 most recent tickets " -"where the user is the ticket customer. The ticket organization field will be " -"automatically set to the new primary organization of the user." +"Allows to set the default language of the Zammad instance. The here defined " +"locale mostly acts as a fallback for:" msgstr "" -"Wenn diese Option gewählt wird, aktualisiert Zammad die letzten 100 Tickets, " -"bei denen der Benutzer der Kunde ist. Das Feld Ticketorganisation wird " -"automatisch auf die neue Primärorganisation des Benutzers gesetzt." - -#: ../settings/ticket.rst:88 -msgid "Do not update any tickets." -msgstr "Keine Tickets aktualisieren." +"Ermöglicht es, die Standardsprache der Zammad-Instanz festzulegen. Die hier " +"definierte Region dient meist als Fallback für:" -#: ../settings/ticket.rst:77 -msgid "" -"When choosing this option, Zammad will not update any tickets when the " -"user's primary organization is changed." +#: ../settings/branding.rst:25 +msgid "user preferences (if Zammad can't detect the users locale)" msgstr "" -"Wenn Sie diese Option wählen, wird Zammad keine Tickets aktualisieren, wenn " -"die primäre Organisation des Benutzers geändert wird." +"Benutzereinstellungen (wenn Zammad die Region des Benutzers nicht erkennen " +"kann)" -#: ../settings/ticket.rst:80 -msgid "**Use with care!**" -msgstr "**Mit Vorsicht verwenden!**" +#: ../settings/branding.rst:26 +msgid "CSV output (reporting, time accounting)" +msgstr "CSV-Ausgabe (Berichte, Zeiterfassung)" -#: ../settings/ticket.rst:82 +#: ../settings/branding.rst:30 +msgid "Define the timezone of your Zammad installation." +msgstr "Legen Sie die Zeitzone für Ihre Zammad-Installation fest." + +#: ../settings/branding.rst:32 msgid "" -"Using this option may lead to inconsistencies in the system as the ticket " -"organization may become decoupled from the ticket customer." +"This does not have any effect on timings for your agents or how Zammad " +"stores date and time values." msgstr "" -"Die Verwendung dieser Option kann zu Inkonsistenzen im System führen, da " -"dadurch die Ticketorganisation vom Ticketkunden entkoppelt werden kann." +"Dies hat keine Auswirkung auf die Zeiteinteilung Ihrer Agenten oder darauf, " +"wie Zammad Datums- und Zeitwerte speichert." -#: ../settings/ticket.rst:85 -msgid "" -"However, you may use this option if you wish to maintain :ref:`the shared " -"access ` to the ticket for all organization " -"members of the original organization of the customer." +#: ../settings/branding.rst:35 +msgid "Changing this value has direct consequences on the following areas:" msgstr "" -"Sie können diese Option jedoch verwenden, wenn Sie :ref:`den gemeinsamen " -"Zugriff ` auf das Ticket für alle " -"Organisationsmitglieder der ursprünglichen Organisation des Kunden " -"beibehalten möchten." +"Die Änderung dieses Wertes hat direkte Auswirkungen auf die folgenden " +"Bereiche:" -#: ../settings/ticket.rst:110 -msgid "Ticket Number Format (default: ``Increment (SystemID.Counter)``)" -msgstr "Ticket-Nummer-Format (Standard: ``Inkrement (SystemID.Zähler)``)" +#: ../settings/branding.rst:37 +msgid ":doc:`/manage/scheduler` tasks" +msgstr ":doc:`/manage/scheduler` Aufgaben" -#: ../settings/ticket.rst:94 -msgid "" -"This setting defines the way Zammad's ticket number will look. Changing this " -"setting in production will cause follow up detection to fail." -msgstr "" -"Diese Einstellung legt fest, wie die Ticketnummer durch Zammad vergeben " -"werden soll. Wird diese Einstellung im Produktivbetrieb geändert, schlägt " -"die Zuordnung bei Rückfragen von Kunden fehl." +#: ../settings/branding.rst:38 +msgid "search indexing (and thus reporting)" +msgstr "Suchindexierung (und damit Berichte)" -#: ../settings/ticket.rst:102 -msgid "Increment (SystemID.Counter)" -msgstr "Inkrement (SystemID.Zähler)" +#: ../settings/branding.rst:40 +msgid "calendar subscriptions" +msgstr "Kalender-Abonnements" -#: ../settings/ticket.rst:98 +#: ../settings/branding.rst:41 +msgid "browser printing" +msgstr "Drucken im Browser" + +#: ../settings/branding.rst:43 msgid "" -"The increment value contains the SystemID (automatically generated during " -"installation) and a increment which counts up with every new Ticket. The " -"increment will automatically get another digit if needed." +"Please note that some of above are fallbacks in case Zammad could not detect " +"the agents timezone correctly." msgstr "" -"Der Wert enthält die SystemID (die bei der Installation automatisch " -"generiert wird) und ein Inkrement, das bei jedem neuen Ticket hochgezählt " -"wird. Das Inkrement erhält bei Bedarf automatisch eine weitere Stelle, wenn " -"der maximal mögliche Wert erreicht ist." +"Bitte beachten Sie, dass es sich bei einigen der obigen Optionen um " +"Fallbacks handelt, falls Zammad die Zeitzone des Agenten nicht korrekt " +"erkennen konnte." -#: ../settings/ticket.rst:102 -msgid "Examples: ``1010138``, ``1010139``" -msgstr "Beispiele: ``1010138``, ``1010139``" +#: ../settings/branding.rst:77 +msgid "Pretty Date" +msgstr "Schönes Datum" -#: ../settings/ticket.rst:110 -msgid "Date (Year.Month.Day.SystemID.Counter)" -msgstr "Datum (Jahr.Monat.Tag.SystemID.Zähler)" +#: ../settings/branding.rst:47 +msgid "" +"This setting allows you to define how Zammad should display time stamps " +"within the interface to all users." +msgstr "" +"Mit dieser Einstellung können Sie festlegen, wie Zammad Zeitstempel für alle " +"Benutzer anzeigen soll." -#: ../settings/ticket.rst:105 +#: ../settings/branding.rst:50 msgid "" -"This version of the ticket number is fairly long. However, because it " -"contains the date of ticket creation, it also allows you to see when the " -"ticket has been created. You may feel familiar with this number format if " -"you've worked with OTRS already." +"This does not have any effect on how Zammad returns e.g. time values via " +"variables." msgstr "" -"Diese Version der Ticketnummer ist ziemlich lang. Da sie jedoch das Datum " -"der Ticket-Erstellung enthält, können Sie damit erkennen, wann das Ticket " -"erstellt wurde. Wenn Sie bereits mit OTRS gearbeitet haben, werden Sie mit " -"diesem Nummernformat vertraut sein." +"Dies hat keinen Einfluss darauf, wie Zammad z.B. Zeitwerte über Variablen " +"ausgibt." -#: ../settings/ticket.rst:110 -msgid "Examples: ``201206231010138``, ``201206231010139``" -msgstr "Beispiele: ``201206231010138``, ``201206231010139``" +#: ../settings/branding.rst:77 +msgid "Choose in between the following options:" +msgstr "Wählen Sie zwischen den folgenden Optionen:" -#: ../settings/ticket.rst:137 -msgid "OPTIONS" -msgstr "Optionen" +#: ../settings/branding.rst:64 +msgid "relative" +msgstr "relativ" -#: ../settings/ticket.rst:113 +#: ../settings/branding.rst:55 msgid "" -"The below options allow you to further customize your ticket number. The " -"availability of options differ depending of the chosen ticket number format " -"above." +"This timestamp shows a relative time span until it switches to a date. Over " +"time, it will change as follows:" msgstr "" -"Mit den folgenden Optionen können Sie Ihre Ticketnummer weiter anpassen. Die " -"Verfügbarkeit der Optionen hängt von dem oben gewählten Ticketnummernformat " -"ab." +"Dieser Zeitstempel zeigt eine relative Zeitspanne an, bis er zu einem Datum " +"wechselt. Im Laufe der Zeit ändert er sich wie folgt:" -#: ../settings/ticket.rst:122 -msgid "Checksum (default: ``no``)" -msgstr "Prüfsumme (Voreinstellung: ``nein``)" +#: ../settings/branding.rst:58 +msgid "just now" +msgstr "gerade eben" -#: ../settings/ticket.rst:118 -msgid "" -"If set to yes, we'll built a checksum to further \"unique\" the ticket " -"number of your system. If you're dealing with many other ticket systems this " -"might help to prevent false positive follow up detection on tickets." -msgstr "" -"Wenn Sie diese Option auf \"Ja\" setzen wird eine Prüfsumme gebildet, um die " -"Ticketnummer Ihres Systems weiter \"eindeutig\" zu machen. Wenn Sie mit " -"vielen anderen Ticketsystemen zu tun haben, kann dies eine falsche Zuordnung " -"von Tickets zu verhindern." +#: ../settings/branding.rst:59 +msgid "5 minutes ago" +msgstr "vor 5 Minuten" -#: ../settings/ticket.rst:122 -msgid "This will also add another digit to the ticket number." -msgstr "Dadurch wird der Ticketnummer eine weitere Ziffer hinzugefügt." +#: ../settings/branding.rst:60 +msgid "3 days 1 hour ago" +msgstr "vor 3 Tagen 1 Stunde" -#: ../settings/ticket.rst:137 -msgid "Min. size of Number (default: ``5``)" -msgstr "Minimale Länge der Zahl (Standard: ``5``)" +#: ../settings/branding.rst:61 +msgid "``03/04/2022``" +msgstr "``03/04/2022``" -#: ../settings/ticket.rst:125 -msgid "" -"This setting defines the minimum length of your ticket number. If your " -"counter is not yet high enough, Zammad will fill the number with zeros to " -"ensure the wanted length." +#: ../settings/branding.rst:63 +msgid "Hovering the timestamp helps, you'll always get a clean timestamp then." msgstr "" -"Diese Einstellung legt die Mindestlänge Ihrer Ticketnummer fest. Wenn Ihr " -"Zähler noch nicht hoch genug ist, wird Zammad die Nummer mit Nullen " -"auffüllen, um die gewünschte Länge zu erreichen." +"Wenn Sie den Mauszeiger über den Zeitstempel bewegen, erhalten Sie immer " +"einen detaillierten Zeitstempel." -#: ../settings/ticket.rst:129 -msgid "" -"Please note that the minimum length is ``3`` (SystemID + at least one digit " -"if below 10). Also, if the length is no longer long enough, the number will " -"automatically get one digit longer. Ticket-Numbers **do not overflow**, thus " -"it's save to keep it at 5 or set it lower if wanted." -msgstr "" -"Bitte beachten Sie, dass die Mindestlänge ``3`` beträgt (SystemID + " -"mindestens eine Stelle, falls unter 10). Wenn die Länge nicht mehr " -"ausreicht, wird die Nummer automatisch um eine Stelle länger. Ticket-Nummern " -"wiederholen sich nicht, daher ist es sicher, die Länge auf 5 oder niedriger " -"zu setzen." +#: ../settings/branding.rst:71 +msgid "absolute" +msgstr "absolut" -#: ../settings/ticket.rst:135 +#: ../settings/branding.rst:67 msgid "" -"This option is only available if ticket number format is set to " -"``Increment``!" +"This timestamp always includes the week day. For one week after creation, " +"the timestamp will not contain the date itself: Thursday 18:35." msgstr "" -"Diese Option ist nur verfügbar, wenn das Ticket-Nummer-Format auf " -"``InKrement`` gesetzt ist!" +"Dieser Zeitstempel enthält immer den Wochentag. Innerhalb einer Woche nach " +"der Erstellung enthält der Zeitstempel nicht das Datum selbst: Donnerstag " +"18:35." -#: ../settings/ticket.rst:142 -msgid "Auto-Assignment" -msgstr "Automatische Zuweisung" +#: ../settings/branding.rst:71 +msgid "After a week it will switch to: ``Friday 4. Mar 16:00``." +msgstr "Nach einer Woche wechselt sie zu: ``Freitag 4. März 16:00``." -#: ../settings/ticket.rst:144 -msgid "" -"In a larger Zammad environment, it happens that several agents open the same " -"ticket at the same time. Although collision detection is then effective, the " -"efficiency of processing can be increased by means of the automatic " -"assignment of tickets when a ticket is opened." -msgstr "" -"In einer größeren Zammad-Umgebung kommt es vor, dass mehrere Agenten ein " -"Ticket gleichzeitig öffnen. Obwohl das in Zammad entsprechend angezeigt " -"wird, kann die Effizienz der Bearbeitung durch die automatische Zuweisung " -"von Tickets erhöht werden." +#: ../settings/branding.rst:76 +msgid "timestamp" +msgstr "Zeitstempel" -#: ../settings/ticket.rst:149 +#: ../settings/branding.rst:74 msgid "" -"The automatic assignment of tickets can be activated and configured in the " -"admin area under Settings > Ticket > Auto Assignment." +"This will cause Zammad to show a complete timestamp according to your locale " +"defaults. For English this could be e.g. ``2022/12/03 2:40 pm`` or for " +"German e.g. ``12.03.2022 14:40``." msgstr "" -"Die automatische Zuweisung von Tickets kann im Adminbereich unter " -"Einstellungen > Ticket > Automatische Zuweisung aktiviert und konfiguriert " -"werden." +"Dies veranlasst Zammad, einen vollständigen Zeitstempel gemäß den " +"Standardeinstellungen Ihrer Region anzuzeigen. Für Englisch ist das z.B. " +"``2022/12/03 2:40 pm`` oder für Deutsch ``12.03.2022 14:40``." -#: ../settings/ticket.rst:152 -msgid "" -"The auto assignment only works if the ticket has no owner yet. By default, " -"the agent can always reset the ticket owner to ``-`` if needed." -msgstr "" -"Die automatische Zuweisung wird nur ausgeführt, wenn das Ticket noch keinen " -"Besitzer hat. Standardmäßig kann der Agent den Besitzer des Tickets bei " -"Bedarf jederzeit auf ``-`` zurücksetzen." +#: ../settings/branding.rst:78 +msgid "Default setting: ``relative``." +msgstr "Standardeinstellung: ``relativ``." -#: ../settings/ticket.rst:155 -msgid "" -"If you want to use this function for only specific tickets, you can " -"configure the conditions accordingly to meet your requirement. By default " -"the condition affects all tickets with the state ``open``." -msgstr "" -"Wenn Sie diese Funktion nur für bestimmte Anfragen verwenden möchten, können " -"Sie eine Bedingungen dafür konfigurieren. Standardmäßig wirkt sich Funktion " -"auf alle Tickets mit dem Status ``offen`` aus." +#: ../settings/security.rst:2 +msgid "Security" +msgstr "Sicherheit" -#: ../settings/ticket.rst:161 +#: ../settings/security.rst:4 msgid "" -"If you need to exclude users (e.g. a group leader), you can search and " -"select the desired agents in the ``Exception Users`` list. The search " -"function in this area is only effective, if you have too many agents to " -"display at once to help you with the configuration." +"For your overview we split each tab within security settings into its own " +"page:" msgstr "" -"Wenn Sie Benutzer ausschließen wollen (z.B. einen Gruppenleiter), können Sie " -"die gewünschten Agenten in der Liste ``Ausgenommene Benutzer`` suchen und " -"auswählen. Die Suchfunktion in diesem Bereich ist nur dann aktiv, wenn es " -"mehr Agenten gibt als angezeigt werden können." +"Der Übersicht halber haben wir jeden Tab der Sicherheitseinstellungen in " +"eine eigene Seite aufgeteilt:" -#: ../settings/ticket.rst:167 -msgid "Notifications" -msgstr "Benachrichtigungen" +#: ../settings/security/base.rst:2 ../settings/system/base.rst:2 +#: ../settings/ticket.rst:8 +msgid "Base" +msgstr "Basis" -#: ../settings/ticket.rst:191 -msgid "Default Notifications" -msgstr "Standard-Benachrichtigungen" +#: ../settings/security/base.rst:5 +msgid "New User Accounts" +msgstr "Neue Benutzer-Konten" -#: ../settings/ticket.rst:170 +#: ../settings/security/base.rst:9 msgid "" -"This setting allows you to configure the default ticket notifications that " -"will be applied to all new agent users (incl. users who were just assigned " -"agent role). Simply change the notification matrix to desired state and " -"press **Save**." +"Activates the `register as a new customer` function on the login page. If " +"set to ``no`` only administrators or agents can create new accounts manually." msgstr "" -"Mit dieser Einstellung können Sie die Standard-Ticket-Benachrichtigungen " -"konfigurieren, die auf alle neuen Agenten-Benutzer angewendet werden " -"(einschließlich Benutzer, denen gerade eine Agentenrolle zugewiesen wurde). " -"Ändern Sie einfach die Benachrichtigungsmatrix auf den gewünschten Status " -"und drücken Sie **Speichern**." +"Aktiviert die Funktion \"Als neuer Kunde registrieren\" auf der Login-Seite. " +"Wenn diese Funktion auf ``Nein`` gesetzt ist, können nur Administratoren " +"oder Agenten neue Konten manuell erstellen." -#: ../settings/ticket.rst:175 +#: ../settings/security/base.rst:13 ../settings/security/base.rst:38 +#: ../settings/security/base.rst:66 +msgid "Default setting: ``yes``" +msgstr "Standardeinstellung: ``Ja``" + +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"New User Accounts\" setting" +msgstr "Abbildung zeigt die aktivierte Einstellung \"Neue Benutzerkonten\"" + +#: ../settings/security/base.rst:22 msgid "" -"In case an agent already exists, their ticket notification preferences will " -"be preserved. Optionally, you can also **Apply current defaults to all " -"agents**." +"Deactivation of above function **does not** deactivate automatic account " +"creation! This means: If a user writes e.g. an email to Zammad and has no " +"account yet, Zammad will automatically create the account. User accounts are " +"a direct dependency of tickets and thus technically mandatory." msgstr "" -"Falls ein Agent bereits existiert werden seine " -"Benachrichtungungseinstellungen beibehalten. Optional können Sie auch " -"**Standardwerte für alle Agenten setzen** verwenden, um bereits existierende " -"Einstellungen für bestehende Agenten zu überschreiben." +"Die Deaktivierung der obigen Funktion **deaktiviert nicht** die automatische " +"Kontoerstellung! Dies bedeutet: Wenn ein Benutzer z.B. eine E-Mail an Zammad " +"schreibt und noch kein Konto hat, wird Zammad das Konto automatisch " +"erstellen. Benutzerkonten sind eine direkte Abhängigkeit von Tickets und " +"somit technisch zwingend erforderlich." -#: ../settings/ticket.rst:181 +#: ../settings/security/base.rst:29 +msgid "Lost Password" +msgstr "Passwort verloren" + +#: ../settings/security/base.rst:33 msgid "" -"**Potential time-consuming action:** Applying default ticket notifications " -"to all agent users may take some time to complete, be patient! The exact " -"time will depend on the size of your system and the number of agents." +"Activates the `lost password` function on the login page. If set to ``no`` " +"only administrators may change the user's password - users may update their " +"own password if they're still logged in and they have the required :doc:" +"`permission `." msgstr "" -"**Potenziell langandauernde Aktion:** Die Anwendung von Standard-Ticket-" -"Benachrichtigungen auf alle Agenten-Benutzer kann einige Zeit in Anspruch " -"nehmen, haben Sie Geduld! Die genaue Zeit hängt von der Größe Ihres Systems " -"und der Anzahl der Agenten ab." +"Aktiviert die Funktion `Kennwort vergessen` auf der Login-Seite. Wenn auf " +"``nein`` gesetzt, können nur Administratoren das Passwort des Benutzers " +"ändern - Benutzer können ihr eigenes Passwort aktualisieren, wenn sie noch " +"eingeloggt sind und die erforderliche :doc:`Berechtigung ` haben." -#: ../settings/ticket.rst:185 +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"Lost Password\" setting" +msgstr "Abbildung zeigt die aktivierte Einstellung \"Passwort verloren\"" + +#: ../settings/security/base.rst:49 msgid "" -"**Active agents only!** When current default ticket notifications are " -"applied, only active agent users are considered. In case an agent is re-" -"activated *after* this action, they will still have the old notification " -"configuration." +"With third party authentications - but especially LDAP - you may want to " +"disable this function. Zammad **will not** change third party login " +"passwords and instead set or change the local password!" msgstr "" -"**Nur aktive Agenten!** Wenn die aktuellen Standard-Ticket-" -"Benachrichtigungen angewendet werden, werden nur aktive Agenten " -"berücksichtigt. Falls ein Agent *nach* dieser Aktion reaktiviert wird, hat " -"er noch die alte Benachrichtigungskonfiguration." +"Bei einer Authentifizierung durch einen Drittanbieter - vor allem aber bei " +"LDAP - sollten Sie diese Funktion deaktivieren. Zammad **ändert keine** " +"Login-Passwörter von Drittanbietern und setzt oder ändert stattdessen das " +"lokale Passwort!" -#: ../settings/ticket.rst:190 +#: ../settings/security/base.rst:56 +msgid "Password Login" +msgstr "Passwort-Anmeldung" + +#: ../settings/security/base.rst:60 msgid "" -"In case you want to go back to the initial state of ticket notifications, " -"you can click on **Reset to default** button." +"Activates the username & password login by default and if no third-party " +"login is activated. Disabling password login on the Zammad login page only " +"takes effect if you enable any :doc:`third-party`." msgstr "" -"Wenn Sie zur Standardkonfiguration der Ticketbenachrichtigungen zurückkehren " -"möchten, können Sie auf die Schaltfläche **Standardwerte wiederherstellen** " -"klicken." +"Aktiviert standardmäßig die Anmeldung mit Benutzernamen und Passwort wenn " +"keine Drittanbieteranmeldung aktiviert ist. Die Deaktivierung der Passwort-" +"Anmeldung auf der Zammad-Anmeldeseite wird nur wirksam, wenn Sie eine :doc:" +"`third-party` Anmeldung aktivieren." -#: ../settings/ticket.rst:194 ../settings/ticket.rst:196 -msgid "Duplicate Detection" -msgstr "Duplikaterkennung" +#: ../settings/security/base.rst:64 +msgid "See :doc:`third-party` for supported third-party logins." +msgstr "Siehe :doc:`third-party` für unterstützte Drittanbieter-Logins." -#: ../settings/ticket.rst:236 ../settings/ticket.rst:238 -msgid "Detect Duplicate Ticket Creation" -msgstr "Ticket Duplikaterkennung" +#: ../settings/security/base.rst:0 +msgid "Figure showing de-activated \"Password Login\" setting" +msgstr "Abbildung zeigt die deaktivierte Einstellung \"Passwort Anmeldung\"" -#: ../settings/ticket.rst:197 ../settings/ticket.rst:199 +#: ../settings/security/base.rst:77 msgid "" -"This setting turns on the duplicate ticket detection mechanism during ticket " -"creation. If similar tickets are found in the system, a suitable warning " -"will be shown to the user trying to create a ticket." -msgstr "" -"Diese Einstellung schaltet den Mechanismus zur Erkennung von doppelten " -"Tickets ein. Wenn ähnliche Tickets im System gefunden werden, wird dem " -"Benutzer, der versucht, ein Ticket zu erstellen, eine entsprechende Warnung " -"angezeigt." - -#: ../settings/ticket.rst:204 ../settings/ticket.rst:206 -msgid "A Sample Duplicate Ticket Warning" -msgstr "Ein Beispiel für eine Warnung zu doppelten Tickets" - -#: ../settings/ticket.rst:206 ../settings/ticket.rst:208 -msgid "" -"You can choose which ticket attributes will be matched by selecting them in " -"**Attributes to compare** field. Only if the ticket attribute value provided " -"by the user in the ticket create form is *equal* with the attribute in an " -"existing ticket, the warning will be shown." +"To help administrators to overcome \"login issues\", Zammad automatically " +"offers a password request for administrator users. This allows you to adjust " +"Third-Party applications even if the login does no longer work!" msgstr "" -"Sie können wählen, welche Ticketattribute abgeglichen werden sollen, indem " -"Sie diese im Feld **Attribute, die zu vergleichen sind** auswählen. Die " -"Duplikat-Warnung wird nur angezeigt, wenn die Werte der Ticketattribute in " -"mehreren Tickets *gleich* sind." - -#: ../settings/ticket.rst:211 ../settings/ticket.rst:213 -msgid "**Warning title** and **Warning message** are configurable as well." -msgstr "**Warnungstitel** und **Warnmeldung** sind ebenfalls konfigurierbar." +"Um Administratoren bei \"Anmelde-Problemen\" zu helfen, bietet Zammad " +"automatisch eine Passwortabfrage für Administrator-Benutzer an. Dies " +"ermöglicht es Ihnen, Anwendungen von Drittanbietern anzupassen, auch wenn " +"der Login nicht mehr funktioniert!" -#: ../settings/ticket.rst:213 ../settings/ticket.rst:215 -msgid "" -"You can limit the detection only to certain user roles. By default, only " -"agents will see the warning." -msgstr "" -"Sie können die Erkennung auf bestimmte Benutzerrollen beschränken. " -"Standardmäßig wird die Warnung nur für Agenten angezeigt." +#: ../settings/security/base.rst:84 +msgid "Session Timeout" +msgstr "Sitzungs-Timeout" -#: ../settings/ticket.rst:216 ../settings/ticket.rst:218 +#: ../settings/security/base.rst:86 msgid "" -"If you don't want to show the matched tickets as part of the warning, you " -"can set **Show matching ticket(s) in the warning** setting to *no*." +"All settings below by default are set to ``4 weeks``. Session Timeout " +"defines the life time of a users session. As soon as it's reached, Zammad " +"will automatically log off the session in question." msgstr "" -"Wenn Sie die passenden Tickets nicht als Teil der Warnung anzeigen möchten, " -"können Sie die Einstellung **Zeige passende(s) Ticket(s) in der Warnung** " -"auf *nein* setzen." +"Alle folgenden Einstellungen sind standardmäßig auf ``4 Wochen`` " +"eingestellt. Session Timeout definiert die Lebenszeit einer Benutzersitzung. " +"Sobald sie erreicht ist, meldet Zammad die betreffende Sitzung automatisch " +"ab." -#: ../settings/ticket.rst:219 ../settings/ticket.rst:221 +#: ../settings/security/base.rst:91 msgid "" -"By default, **Permission level for looking up ticket** is set to *User*, " -"which means user permissions will be honored during sarch. The user will " -"see the warning only if tickets they have access to are matched. " -"Alternatively, you can set this setting to *System*, in which case the " -"search will happen within *all* tickets in the system, regardless of user " +"Zammad takes the highest value set assigned for the user based on the " "permissions." msgstr "" -"Standardmäßig ist **Berechtigungsstufe für Ticket-Suchvorgänge** auf " -"*Benutzer* eingestellt. Das bedeutet, dass die Benutzerrechte bei der Suche " -"beachtet werden. Der Benutzer sieht die Warnung nur, wenn Tickets, auf die " -"er Zugriff hat, übereinstimmen. Alternativ können Sie diese Einstellung auf " -"*System* setzen. In diesem Fall wird die Suche in *allen* Tickets im System " -"durchgeführt, unabhängig von den Benutzerrechten." +"Zammad nimmt den höchsten Wert, der dem Benutzer aufgrund der Berechtigungen " +"zugewiesen wurde." -#: ../settings/ticket.rst:225 ../settings/ticket.rst:227 -msgid "**🦺 Safety first!**" -msgstr "**🦺 Sicherheit geht vor!**" +#: ../settings/security/base.rst:94 +msgid "``admin``" +msgstr "``admin``" -#: ../settings/ticket.rst:227 ../settings/ticket.rst:229 -msgid "" -"Even if the permission level is set to *System*, the user will not be shown " -"the tickets they don't have access to in the warning, even if they match." -msgstr "" -"Auch wenn die Berechtigungsstufe auf *System* eingestellt ist, werden dem " -"Benutzer die Tickets, auf die er keinen Zugriff hat, in der Warnung nicht " -"angezeigt, selbst wenn sie übereinstimmen." +#: ../settings/security/base.rst:96 +msgid "``ticket.customer``" +msgstr "``ticket.customer``" -#: ../settings/ticket.rst:231 ../settings/ticket.rst:233 -msgid "" -"However, just the confirmation about the existence of the tickets in the " -"system may be considered an unwanted information disclosure. Use this option " -"carefully!" +#: ../settings/security/base.rst:97 +msgid "``default`` (fallback if user doesn't have above permissions set)" msgstr "" -"Die bloße Bestätigung über die Existenz der Tickets im System kann jedoch " -"als unerwünschte Weitergabe von Informationen angesehen werden. Verwenden " -"Sie diese Option mit Vorsicht!" +"``default`` (Fallback, wenn der Benutzer die oben genannten Berechtigungen " +"nicht hat)" -#: ../settings/ticket.rst:235 ../settings/ticket.rst:237 +#: ../settings/security/base.rst:99 msgid "" -"Finally, you can configure between matching within **All tickets** or **Open " -"tickets** only by setting **Match tickets in following states**. Depending " -"on the current ticket state, a ticket may or not be matched." +"All settings act independently from each other allowing you to disable the " +"timeouts for e.g. admins, but not agents." msgstr "" -"Schließlich können Sie festlegen, ob der Abgleich nur für **Alle Tickets** " -"oder nur für **Offene Tickets** erfolgen soll, indem Sie **Vergleiche " -"Tickets in folgenden Status** einstellen. Je nach aktuellem Ticketstatus " -"erfolgt die Prüfung oder nicht." +"Alle Einstellungen wirken unabhängig voneinander, so dass Sie z.B. nur die " +"Timeouts für Admins deaktivieren können." -#: ../system/core-workflows.rst:2 -msgid "Core Workflows" -msgstr "Core Workflows" +#: ../settings/security/base.rst:115 +#: ../system/integrations/checkmk/api-reference.rst:13 +msgid "Example" +msgstr "Beispiel" -#: ../system/core-workflows.rst:4 -msgid "" -"Core Workflows allow you to adjust object attributes in many ways. For " -"example:" -msgstr "" -"Mit Core Workflows können Sie Objektattribute auf vielfältige Weise " -"anpassen. Zum Beispiel:" +#: ../settings/security/base.rst:107 +msgid "Let's suppose you configured the following session timeouts" +msgstr "Angenommen, Sie haben die folgenden Sitzungs-Timeouts konfiguriert" -#: ../system/core-workflows.rst:7 -msgid "show / hide fields" -msgstr "Felder anzeigen / verstecken" +#: ../settings/security/base.rst:104 +msgid "default: 3 weeks" +msgstr "Standard: 3 Wochen" -#: ../system/core-workflows.rst:8 -msgid "adjust mandatory setting" -msgstr "Pflichtfelder anpassen" +#: ../settings/security/base.rst:105 +msgid "admin: 2 weeks" +msgstr "admin: 2 Wochen" -#: ../system/core-workflows.rst:9 -msgid "manipulate available options" -msgstr "verfügbare Optionen anpassen" +#: ../settings/security/base.rst:106 +msgid "ticket.agent: 4 weeks" +msgstr "ticket.agent: 4 Wochen" -#: ../system/core-workflows.rst:11 +#: ../settings/security/base.rst:107 +msgid "ticket.customer: 1 week" +msgstr "ticket.customer: 1 Woche" + +#: ../settings/security/base.rst:115 +msgid "This results in the following situations" +msgstr "Daraus ergibt sich folgendes Szenario" + +#: ../settings/security/base.rst:110 +msgid "a user with ``admin`` permission will have a timeout of 2 weeks" +msgstr "" +"ein Benutzer mit der Berechtigung ``admin`` hat einen Timeout von 2 Wochen" + +#: ../settings/security/base.rst:111 msgid "" -"With this, you can provide exactly the information your users really need!" +"a user with ``admin`` and ``ticket.agent`` permissions will have a timeout " +"of 2 weeks" msgstr "" -"Auf diese Weise können Sie genau die Informationen bereitstellen, die Ihre " -"Nutzer wirklich brauchen!" +"ein Benutzer mit den Rechten ``admin`` und ``ticket.agent`` hat einen " +"Timeout von 2 Wochen" -#: ../system/core-workflows.rst:15 +#: ../settings/security/base.rst:113 msgid "" -"If the pre-defined :doc:`/system/objects` are not enough, please add them " -"beforehand." +"a user with ``ticket.customer`` permission will have a timeout of 1 week" msgstr "" -"Wenn die vordefinierten :doc:`/system/objects` nicht ausreichen, fügen Sie " -"eigene bitte vorher hinzu." +"ein Benutzer mit der Berechtigung ``ticket.customer`` hat einen Timeout von " +"1 Woche" -#: ../system/core-workflows.rst:17 +#: ../settings/security/base.rst:115 msgid "" -"If you experience slow or unreliable field updates, please see :ref:`Core " -"Workflow Ajax Modus `" +"a user with neither ``admin``, ``ticket.agent`` nor ``ticket.customer`` " +"permissions will have a timeout of 3 weeks" msgstr "" -"Wenn Sie langsame oder unzuverlässige Feldaktualisierungen feststellen, " -"lesen Sie bitte :ref:`Core Workflow Ajax Modus `" +"ein Benutzer, der weder ``admin``, ``ticket.agent`` noch ``ticket.customer`` " +"Rechte hat, hat einen Timeout von 3 Wochen" -#: ../system/core-workflows.rst:22 +#: ../settings/security/password.rst:4 msgid "" -"This is a very enhanced functionality and can cause unexpected UI behavior. " -"Please ensure to test your use cases after configuration to reduce surprises." +"This section allows you to define password requirements for the local user " +"accounts." msgstr "" -"Dies ist eine sehr mächtige Funktionalität und kann zu unerwartetem " -"Verhalten der Benutzeroberfläche führen. Bitte stellen Sie sicher, dass Sie " -"Ihre Anwendungsfälle nach der Konfiguration testen, um Überraschungen zu " -"vermeiden." +"In diesem Bereich können Sie die Anforderungen an das Passwort für die " +"lokalen Benutzerkonten festlegen." -#: ../system/core-workflows.rst:None -msgid "Dialogue for adding a new workflow" -msgstr "Dialog zum Hinzufügen eines neuen Workflows" +#: ../settings/security/password.rst:9 +msgid "" +"Zammad does **not** allow you to change your LDAP password, instead, it will " +"set a password in its local database which might confuse your users. This " +"might be addressed in the future by `#1169 `_." +msgstr "" +"Zammad erlaubt das Ändern des LDAP-Passworts **nicht**. Stattdessen wird ein " +"Passwort in der lokalen Datenbank gesetzt, was zu Verwirrung führen könnte. " +"Dies kann zukünftig durch `#1169 `_ behoben." -#: ../system/core-workflows/condition-operators.rst:2 -msgid "Core Workflow Condition Operators" -msgstr "Core Workflow Bedingungsoperatoren" +#: ../settings/security/password.rst:14 +msgid "**Exception for admins**" +msgstr "**Ausnahme für Administratoren**" -#: ../system/core-workflows/condition-operators.rst:4 +#: ../settings/security/password.rst:16 msgid "" -"You might know that there is a separate section for explaining :doc:" -"`condition operators `. Head over there to " -"see a detailed explanation of many conditions and operators." +"Please note that below password policies *do not* affect administrators " +"setting passwords on user accounts. While this seems strange and not safe we " +"believe that an administrator knowing an user's password is insecure as well." msgstr "" -"Sie wissen vielleicht, dass es einen separaten Bereich zur Erläuterung von :" -"doc:`Bedingungsoperatoren ` gibt. Dort " -"finden Sie eine detaillierte Erklärung vieler Bedingungen und Operatoren." +"Bitte beachten Sie, dass die unten aufgeführten Passwortrichtlinien *nicht* " +"das manuelle Setzen von Passwörtern für Benutzer durch Administratoren " +"betrifft. Das mag inkonsistent und seltsam wirken, aber wir sind der " +"Meinung, dass es ebenfalls nicht sicher ist, wenn ein Administrator das " +"Passwort eines Benutzers kennt." -#: ../system/core-workflows/condition-operators.rst:8 +#: ../settings/security/password.rst:21 +msgid "The suggested workflow is either:" +msgstr "Die vorgeschlagene Vorgehensweise ist entweder:" + +#: ../settings/security/password.rst:23 msgid "" -"Due to differences to other places in Zammad which are also using conditions " -"(e.g. triggers), you can find a dedicated description of operators for core " -"workflows below." +"to use third party logins to not require local passwords at all **- or -**" msgstr "" -"Aufgrund von Unterschieden zu anderen Bereichen in Zammad, die ebenfalls " -"Bedingungen verwenden (z.B. Trigger) , finden Sie weiter unten eine " -"Beschreibung der Operatoren speziell für Core-Workflows." +"Anmeldung von Drittanbietern zu verwenden, um keine lokalen Passwörter mehr " +"zu benötigen **- oder -**" -#: ../system/core-workflows/condition-operators.rst:12 +#: ../settings/security/password.rst:25 +msgid "to require your *user to reset the password* upon first login." +msgstr "" +"dass Ihr Benutzer bei der ersten Anmeldung sein *Kennwort zurücksetzen* muss." + +#: ../settings/security/password.rst:27 msgid "" -"Be aware that the availability of the operators depends on the selected " -"attribute and its field type. Some of the operators may only be available " -"for system attributes (e.g. for \"tags\", \"active\")." +"This way administrators are not required to set a user's password at all!" msgstr "" -"Beachten Sie, dass die Verfügbarkeit der Operatoren von dem ausgewählten " -"Attribut und seinem Feldtyp abhängt. Einige der Operatoren sind " -"möglicherweise nur für Systemattribute verfügbar (z.B. für \"Tags\", " -"\"Aktiv\")." - -#: ../system/core-workflows/condition-operators.rst:20 -msgid "Operator" -msgstr "Operator" +"Auf diese Weise müssen Administratoren das Passwort eines Benutzers " +"überhaupt nicht festlegen!" -#: ../system/core-workflows/condition-operators.rst:22 -msgid "after (absolute)" -msgstr "nach (absolut)" +#: ../settings/security/password.rst:31 +msgid "Maximum Failed Logins" +msgstr "Maximale Anzahl fehlgeschlagener Anmeldungen" -#: ../system/core-workflows/condition-operators.rst:23 -msgid "Matches if a date/time is after a specific point in time." +#: ../settings/security/password.rst:33 +msgid "" +"You can choose a value between ``4`` and ``20``. This defines how often a " +"login to a user account may fail until Zammad will lock it. Your users can " +"always use the \"forgot password\" function to change their password and " +"unlock their account." msgstr "" -"Trifft zu, wenn ein Datum/Uhrzeit nach einem definierten Zeitpunkt liegt." +"Sie können einen Wert zwischen ``4`` und ``20`` wählen. Dieser Wert legt " +"fest, wie oft eine Anmeldung bei einem Benutzerkonto fehlschlagen darf, bis " +"Zammad es sperrt. Ihre Benutzer können jederzeit die Funktion \"Passwort " +"vergessen\" verwenden, um ihr Passwort zu ändern und ihr Konto zu entsperren." -#: ../system/core-workflows/condition-operators.rst:24 -msgid "after (relative)" -msgstr "nach (relativ)" +#: ../settings/security/password.rst:38 +msgid "The default value is ``10``." +msgstr "Der Standardwert ist ``10``." -#: ../system/core-workflows/condition-operators.rst:25 -msgid "Matches if a time span after a specified event has passed." +#: ../settings/security/password.rst:42 +msgid "Beside changing the user's password, you can also unlock accounts via" msgstr "" -"Trifft zu, wenn eine Zeitspanne nach einem bestimmten Ereignis vergangen ist." - -#: ../system/core-workflows/condition-operators.rst:26 -msgid "before (absolute)" -msgstr "vor (absolut)" +"Neben der Änderung des Benutzerkennworts können Sie Konten auch entsperren " +"über" -#: ../system/core-workflows/condition-operators.rst:27 -msgid "Matches if a date/time is before a specific point in time." -msgstr "" -"Trifft zu, wenn ein Datum/Uhrzeit vor einem definierten Zeitpunkt liegt." +#: ../settings/security/password.rst:44 +msgid ":ref:`user management list `" +msgstr ":ref:`Benutzerverwaltung `" -#: ../system/core-workflows/condition-operators.rst:28 -msgid "before (relative)" -msgstr "vor (relativ)" +#: ../settings/security/password.rst:45 +msgid ":docs:`console `" +msgstr ":docs:`Konsole `" -#: ../system/core-workflows/condition-operators.rst:29 -msgid "Matches if a time span after a specified event has not passed." -msgstr "Trifft zu während einer definierten Zeitspanne nach einem Ereignis." +#: ../settings/security/password.rst:46 +msgid ":docs:`API `" +msgstr ":docs:`API `" -#: ../system/core-workflows/condition-operators.rst:30 -msgid "contains" -msgstr "enthält" +#: ../settings/security/password.rst:50 +msgid "Failed logins via LDAP no longer lock accounts." +msgstr "Fehlgeschlagene Anmeldungen über LDAP sperren keine Konten mehr." -#: ../system/core-workflows/condition-operators.rst:31 -msgid "Matches if a specified value is present." -msgstr "Trifft zu, wenn ein definierter Wert vorhanden ist." +#: ../settings/security/password.rst:53 +msgid "2 Lower Case And 2 Upper Case Characters" +msgstr "2 Kleinbuchstaben und 2 Großbuchstaben" -#: ../system/core-workflows/condition-operators.rst:33 -msgid "Matches if all of the specified values are present." -msgstr "Trifft zu, wenn alle definierten Werte vorhanden sind." +#: ../settings/security/password.rst:55 +msgid "" +"You can add complexity to passwords by enforcing at least 2 upper and lower " +"case characters." +msgstr "" +"Sie können die Komplexität von Passwörtern erhöhen, indem Sie mindestens 2 " +"Groß- und Kleinbuchstaben vorschreiben." -#: ../system/core-workflows/condition-operators.rst:35 -msgid "Matches if none of the specified values are present." -msgstr "Trifft zu, wenn keiner der definierten Werte vorhanden ist." +#: ../settings/security/password.rst:58 ../settings/security/password.rst:83 +msgid "The default value is ``no``." +msgstr "Der Standardwert ist ``nein``." -#: ../system/core-workflows/condition-operators.rst:36 -msgid "contains not" -msgstr "enthält nicht" +#: ../settings/security/password.rst:62 +msgid "Minimum Length" +msgstr "Minimale Länge" -#: ../system/core-workflows/condition-operators.rst:37 -msgid "Matches if a specified value is not present." -msgstr "Trifft zu, wenn ein definierter Wert nicht vorhanden ist." +#: ../settings/security/password.rst:64 +msgid "" +"This defines the minimum password length required for users to provide (from " +"``4`` to ``20``)." +msgstr "" +"Dies definiert die minimale Passwortlänge, die Benutzer einhalten müssen " +"(von ``4`` bis ``20``)." -#: ../system/core-workflows/condition-operators.rst:39 -msgid "Matches if one specified value is present." -msgstr "Trifft zu, wenn ein definierter Wert vorhanden ist." +#: ../settings/security/password.rst:67 +msgid "The default value is ``6``." +msgstr "Der Standardwert ist ``6``." -#: ../system/core-workflows/condition-operators.rst:41 -msgid "Matches if one specified value is not present." -msgstr "Trifft zu, wenn ein definierter Wert nicht vorhanden ist." +#: ../settings/security/password.rst:71 +msgid "Digit Required" +msgstr "Ziffer benötigt" -#: ../system/core-workflows/condition-operators.rst:42 -msgid "does not match regex" -msgstr "passt nicht auf regex" +#: ../settings/security/password.rst:73 +msgid "This enforces your users to use at least one digit within the password." +msgstr "" +"Dadurch müssen Ihre Benutzer mindestens eine Ziffer im Passwort verwenden." -#: ../system/core-workflows/condition-operators.rst:43 -msgid "Matches if content doesn't fit to regex rule." -msgstr "Trifft zu, wenn der Inhalt nicht der Regex-Regel entspricht." +#: ../settings/security/password.rst:75 +msgid "The default value is ``yes``." +msgstr "Der Standardwert ist ``Ja``." -#: ../system/core-workflows/condition-operators.rst:44 -msgid "ends with" -msgstr "endet auf" +#: ../settings/security/password.rst:78 +msgid "Special Character Required" +msgstr "Sonderzeichen erforderlich" -#: ../system/core-workflows/condition-operators.rst:45 -msgid "Matches if content ends with specified value." -msgstr "Trifft zu, wenn der Inhalt mit dem definierten Wert endet." +#: ../settings/security/password.rst:80 +msgid "" +"This setting allows you to improve your password quality even more by " +"enforcing the password to contain at least one special character." +msgstr "" +"Mit dieser Einstellung können Sie die Stärke Ihres Passworts noch weiter " +"erhöhen, indem das Passwort mindestens ein Sonderzeichen enthalten muss." -#: ../system/core-workflows/condition-operators.rst:46 -msgid "ends with one of" -msgstr "endet auf eins von" +#: ../settings/security/ssl-certificates.rst:2 +msgid "SSL Certificates" +msgstr "SSL-Zertifikate" -#: ../system/core-workflows/condition-operators.rst:47 -msgid "Matches if content ends with one of the specified values." -msgstr "Trifft zu, wenn der Inhalt mit einem der definierten Werte endet." +#: ../settings/security/ssl-certificates.rst:7 +msgid "" +"Zammad offers the possibility to upload custom certificates and custom " +"Certificate Authority (CA) certificates. This can be useful if you want to " +"connect Zammad the secure way to other systems which are using custom " +"certificates." +msgstr "" +"Zammad bietet die Möglichkeit, benutzerdefinierte Zertifikate und " +"benutzerdefinierte Zertifikate der Zertifizierungsstelle (Certificate " +"Authority, CA) hochzuladen. Dies kann nützlich sein, wenn Sie Zammad auf " +"sichere Weise mit anderen Systemen verbinden wollen, die eigene Zertifikate " +"verwenden." -#: ../system/core-workflows/condition-operators.rst:48 -msgid "from (relative)" -msgstr "von vor (relativ)" +#: ../settings/security/ssl-certificates.rst:12 +msgid "" +"An example usecase might be: You have an internal LDAP server that is not " +"accessible from the internet, and you want a SSL-encrypted connection, using " +"a custom certificate." +msgstr "" +"Ein Beispielanwendungsfall könnte sein: Sie haben einen internen LDAP-" +"Server, der nicht über das Internet zugänglich ist und Sie möchten zu diesem " +"eine SSL-verschlüsselte Verbindung mit einem benutzerdefinierten Zertifikat " +"herstellen." -#: ../system/core-workflows/condition-operators.rst:49 -msgid "Matches if date/time is after a period of time after an event." +#: ../settings/security/ssl-certificates.rst:19 +msgid "" +"You should have an existing custom certificate file and/or a custom CA " +"certificate file, which you want to add to Zammad. As filetype ``.crt`` is " +"supported and the certificate format has to be PEM (Base64 ASCII)." msgstr "" -"Trifft zu, wenn Datum/Uhrzeit nach einer definierten Zeitspanne nach einem " -"Ereignis liegen." +"Sie sollten eine bestehende Zertifikatsdatei und/oder eine CA-" +"Zertifikatsdatei haben, die Sie zu Zammad hinzufügen möchten. Als Dateityp " +"wird ``.crt`` unterstützt und das Zertifikatsformat muss PEM (Base64 ASCII) " +"sein." -#: ../system/core-workflows/condition-operators.rst:51 -msgid "Matches if content is equal to a specified value." -msgstr "Trifft zu, wenn der Inhalt gleich dem definierten Wert ist." +#: ../settings/security/ssl-certificates.rst:25 +msgid "" +"When you import a custom CA certificate, all certificates generated with " +"this are trusted. This can be useful if you have more than one system/" +"certificate you want to connect to and the certificates are issued from the " +"same custom CA." +msgstr "" +"Wenn Sie ein eigenes CA-Zertifikat importieren, werden alle mit diesem " +"Zertifikat erzeugten Zertifikate als vertrauenswürdig eingestuft. Dies kann " +"nützlich sein, wenn Sie mehr als ein System/Zertifikat haben, mit dem Sie " +"sich verbinden möchten, und die Zertifikate von derselben CA ausgestellt " +"wurden." -#: ../system/core-workflows/condition-operators.rst:52 -msgid "is any of" -msgstr "ist eins von" +#: ../settings/security/ssl-certificates.rst:31 +msgid "Add a Certificate" +msgstr "Zertifikat hinzufügen" -#: ../system/core-workflows/condition-operators.rst:53 -msgid "Matches if content is equal to any of specified values." +#: ../settings/security/ssl-certificates.rst:33 +msgid "" +"To add a custom certificate or a custom CA certificate, head over to the " +"Admin panel > Settings > Security > SSL Certificates. Here you can find a " +"\"Add SSL Certificate\" button. In the dialog you can either select a " +"certificate file or paste the content of the certificate:" msgstr "" -"Trifft zu, wenn der Inhalt mit einem der definierten Werte übereinstimmt." - -#: ../system/core-workflows/condition-operators.rst:54 -msgid "is modified" -msgstr "ist geändert" +"Um ein benutzerdefiniertes Zertifikat oder ein benutzerdefiniertes CA-" +"Zertifikat hinzuzufügen, gehen Sie zu Admin Panel > Einstellungen > " +"Sicherheit > SSL-Zertifikate. Hier finden Sie eine Schaltfläche \"SSL-" +"Zertifikat hinzufügen\". In dem Dialog können Sie entweder eine " +"Zertifikatsdatei auswählen oder den Inhalt des Zertifikats einfügen:" -#: ../system/core-workflows/condition-operators.rst:55 -msgid "Matches if content is modified." -msgstr "Trifft zu, wenn der Inhalt geändert wurde." +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate adding dialog" +msgstr "Screenshot zeigt Dialog zum Hinzufügen von Zertifikaten" -#: ../system/core-workflows/condition-operators.rst:57 -#: ../system/core-workflows/condition-operators.rst:61 -msgid "True from the moment of changing content until form submit." +#: ../settings/security/ssl-certificates.rst:43 +msgid "" +"After selecting a file or pasting the content of the certificate, click on " +"the \"Add\" button to finally upload it to Zammad. Then, the certificates " +"are immediately effective, no restart or similar required." msgstr "" -"Wahr ab dem Zeitpunkt der Änderung des Inhalts bis zum Absenden des " -"Formulars." +"Nachdem Sie eine Datei ausgewählt oder den Inhalt des Zertifikats eingefügt " +"haben, klicken Sie auf die Schaltfläche \"Hinzufügen\", um es schließlich in " +"Zammad hochzuladen. Danach sind die Zertifikate sofort wirksam, es ist kein " +"Neustart oder ähnliches erforderlich." -#: ../system/core-workflows/condition-operators.rst:58 -msgid "is modified to" -msgstr "ist geändert auf" - -#: ../system/core-workflows/condition-operators.rst:59 -msgid "Matches if content is modified to a specific value." -msgstr "Trifft zu, wenn der Inhalt auf einen definiertene Wert geändert wurde." - -#: ../system/core-workflows/condition-operators.rst:62 -msgid "is none of" -msgstr "ist keins von" - -#: ../system/core-workflows/condition-operators.rst:63 -msgid "Matches if content is none of any specified values." -msgstr "Trifft zu, wenn der Inhalt keinem der definierten Werte entspricht." - -#: ../system/core-workflows/condition-operators.rst:65 -msgid "Matches if content is not equal to a specified value." -msgstr "Trifft zu, wenn der Inhalt nicht gleich dem definierten Wert ist." - -#: ../system/core-workflows/condition-operators.rst:67 -msgid "Matches if content is present." -msgstr "Trifft zu, wenn ein Inhalt vorhanden ist." - -#: ../system/core-workflows/condition-operators.rst:68 -msgid "just changed" -msgstr "gerade geändert" +#: ../settings/security/ssl-certificates.rst:49 +msgid "" +"Please note that only single certificate files are supported. That means if " +"you want to import a certificate / CA certificate, it must contain **only " +"one** certificate." +msgstr "" +"Bitte beachten Sie, dass nur Dateien mit einzelne Zertifikaten unterstützt " +"werden. Das heißt, wenn Sie ein Zertifikat / CA-Zertifikat importieren " +"möchten, darf es **nur ein** Zertifikat enthalten." -#: ../system/core-workflows/condition-operators.rst:69 -msgid "Matches if content has changed." -msgstr "Trifft zu, wenn sich der Inhalt gerade geändert hat." +#: ../settings/security/ssl-certificates.rst:54 +msgid "Certificate Overview" +msgstr "Zertifikat Übersicht" -#: ../system/core-workflows/condition-operators.rst:71 -#: ../system/core-workflows/condition-operators.rst:75 +#: ../settings/security/ssl-certificates.rst:56 msgid "" -"Only true for the moment of changing content until next form field action/" -"click." +"After you added a certificate, you can see a table with information for each " +"added certificate:" msgstr "" -"Nur zutreffend für den Moment der Änderung des Inhalts bis zur nächsten " -"Formularfeldaktion/zum nächsten Mausklick." +"Nachdem Sie ein Zertifikat hinzugefügt haben, sehen Sie eine Tabelle mit " +"Informationen zu jedem hinzugefügten Zertifikat:" -#: ../system/core-workflows/condition-operators.rst:72 -msgid "just changed to" -msgstr "gerade geändert auf" +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing table of added certificates" +msgstr "Screenshot zeigt Tabelle mit den hinzugefügten Zertifikaten" -#: ../system/core-workflows/condition-operators.rst:73 -msgid "Matches if content has changed to a specified value." +#: ../settings/security/ssl-certificates.rst:64 +msgid "" +"Here you can download the certificate or delete it, if you don't need it " +"anymore." msgstr "" -"Trifft zu, wenn sich der Inhalt gerade auf einen definierten Wert geändert " -"hat." +"Hier können Sie das Zertifikat herunterladen oder es löschen, wenn Sie es " +"nicht mehr benötigen." -#: ../system/core-workflows/condition-operators.rst:76 -msgid "matches regex" -msgstr "passt auf regex" +#: ../settings/security/ssl-certificates.rst:68 +msgid "Deleting Certificates" +msgstr "Löschen von Zertifikaten" -#: ../system/core-workflows/condition-operators.rst:77 -msgid "Matches if value fits to regex rule." -msgstr "Trifft zu, wenn der Wert der Regex-Regel entspricht." +#: ../settings/security/ssl-certificates.rst:70 +msgid "" +"If you want to delete a specific certificate, you can do it by clicking on " +"the menu in the actions column and selecting delete:" +msgstr "" +"Wenn Sie ein bestimmtes Zertifikat löschen möchten, können Sie dies tun, " +"indem Sie auf das Menü in der Spalte \"Aktionen\" klicken und \"Löschen\" " +"auswählen:" -#: ../system/core-workflows/condition-operators.rst:79 -msgid "Matches if no content is present." -msgstr "Trifft zu, wenn kein Inhalt vorhanden ist." +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate deletion button" +msgstr "Screenshot zeigt Schaltfläche zum Löschen von Zertifikaten" -#: ../system/core-workflows/condition-operators.rst:80 -msgid "starts with" -msgstr "beginnt mit" +#: ../settings/security/ssl-certificates.rst:79 +msgid "Downloading Certificates" +msgstr "Herunterladen von Zertifikaten" -#: ../system/core-workflows/condition-operators.rst:81 -msgid "Matches if content starts with specified value." -msgstr "Trifft zu, wenn der Inhalt mit dem definierten Wert beginnt." +#: ../settings/security/ssl-certificates.rst:81 +msgid "" +"If you want to download your certificates, you can do this as well via " +"corresponding action buttons." +msgstr "" +"Wenn Sie Ihre Zertifikate herunterladen möchten, können Sie dies ebenfalls " +"über entsprechende Aktionsschaltflächen tun." -#: ../system/core-workflows/condition-operators.rst:82 -msgid "starts with one of" -msgstr "beginnt mit eins von" +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate download button" +msgstr "Screenshot zeigt Schaltfläche zum Herunterladen des Zertifikats" -#: ../system/core-workflows/condition-operators.rst:83 -msgid "Matches if content starts with one of the specified values." -msgstr "Trifft zu, wenn der Inhalt mit einem der definierten Werte beginnt." +#: ../settings/security/third-party.rst:13 +msgid "Login Providers" +msgstr "Login-Anbieter" -#: ../system/core-workflows/condition-operators.rst:84 -msgid "till (relative)" -msgstr "bis in (relativ)" +#: ../settings/security/third-party.rst:2 +msgid "Third-Party Applications" +msgstr "Anwendungen von Drittanbietern" -#: ../system/core-workflows/condition-operators.rst:85 -msgid "Matches if date/time is before a period of time before an event." +#: ../settings/security/third-party.rst:4 +msgid "" +"Third party authentication is a great way to help your users to login to " +"Zammad more easily. If the account is yet unknown, Zammad will create a new " +"user automatically, without the user needed to interact (e.g. type in his " +"name). Another big advantage of this feature is that your user doesn't need " +"to remember another password." msgstr "" -"Triff zu, wenn Datum/Uhrzeit vor einem definierten Zeitraum vor einem " -"Ereignis liegt." +"Die Authentifizierung von Drittanbietern ist eine gute Möglichkeit, Ihren " +"Benutzern die Anmeldung bei Zammad zu erleichtern. Wenn das Benutzerkonto " +"noch nicht bekannt ist, erstellt Zammad automatisch einen neuen Benutzer, " +"ohne dass der Benutzer etwas unternehmen muss (z.B. seinen Namen eingeben). " +"Ein weiterer großer Vorteil dieser Funktion ist, dass der Benutzer sich kein " +"zusätzliches Passwort merken muss." -#: ../system/core-workflows/condition-operators.rst:86 -msgid "today" -msgstr "heute" +#: ../settings/security/third-party.rst:10 +msgid "" +"You can deactivate logging in via :ref:`security_password_login` if any of " +"the mentioned authentication providers are enabled in your instance." +msgstr "" +"Sie können das Einloggen mittels :ref:`security_password_login` " +"deaktivieren, wenn einer der genannten Authentifizierungsanbieter in Ihrer " +"Instanz aktiviert ist." -#: ../system/core-workflows/condition-operators.rst:87 -msgid "Matches if date/time is today." -msgstr "Trifft zu, wenn Datum/Uhrzeit heute ist." +#: ../settings/security/third-party.rst:27 +msgid "" +"We're currently missing documentation for the following login providers:" +msgstr "Aktuell fehlt die Dokumentation für die folgenden Login-Provider:" -#: ../system/core-workflows/condition-operators.rst:88 -msgid "within last (relative)" -msgstr "innerhalb letzter (relativ)" +#: ../settings/security/third-party.rst:29 +msgid "LinkedIn" +msgstr "LinkedIn" -#: ../system/core-workflows/condition-operators.rst:89 -msgid "" -"Matches if date/time content is within specified period of time before now." -msgstr "" -"Triff zu, wenn Datum/Uhrzeit innerhalb der definierten Zeitspann vor jetzt " -"liegt." +#: ../settings/security/third-party.rst:30 +msgid "Weibo" +msgstr "Weibo" -#: ../system/core-workflows/condition-operators.rst:91 -msgid "within next (relative)" -msgstr "innerhalb nächster (relativ)" +#: ../settings/security/third-party.rst:35 +msgid "Automatic Account Link on Initial Logon" +msgstr "Automatische Kontoverbindung bei der Erstanmeldung" -#: ../system/core-workflows/condition-operators.rst:92 +#: ../settings/security/third-party.rst:37 msgid "" -"Matches if date/time content is within specified period of time after now." +"In general there's two possible options for Zammad on how to deal with " +"already known users as they try to authenticate against a third-party " +"application. By default, Zammad will not automatically link \"unknown\" " +"authentication providers to existing accounts." msgstr "" -"Trifft zu, wenn Datum/Uhrzeit innerhalb der definierten Zeitspanne nach " -"jetzt liegt." - -#: ../system/core-workflows/how-do-they-work.rst:2 -msgid "How do they work?" -msgstr "Wie funktionieren sie?" +"In Zammad gibt es zwei Möglichkeiten, wie mit bereits bekannten Benutzern " +"umgegangen werden kann, wenn eine Authentifizierung über eine " +"Drittanbieteranwendung erfolgt. Standardmäßig verknüpft Zammad " +"\"unbekannte\" Authentifizierungsanbieter nicht automatisch mit bestehenden " +"Konten." -#: ../system/core-workflows/how-do-they-work.rst:4 +#: ../settings/security/third-party.rst:42 msgid "" -"Core Workflows are executed according to their priority. If two workflows " -"have the same priority, they are executed in alphabetical order based on " -"their **name**." +"This means that the user has to manually link authentication providers to " +"their accounts (for more about this :user-docs:`consult the user " +"documentation `)." msgstr "" -"Core-Workflows werden entsprechend ihrer Priorität ausgeführt. Wenn zwei " -"Workflows die gleiche Priorität haben, werden sie in alphabetischer " -"Reihenfolge auf der Grundlage ihres **Namens** ausgeführt." +"Dies bedeutet, dass der Benutzer die Authentifizierungsanbieter manuell mit " +"seinen Konten verknüpfen muss (weitere Informationen hierzu finden Sie in " +"der :user-docs:`Benutzerdokumentation `)." -#: ../system/core-workflows/how-do-they-work.rst:8 +#: ../settings/security/third-party.rst:46 msgid "" -"Because of the way Core Workflows work, all changes to attributes are " -"checked with the application server - please see :doc:`limitations` for " -"possible issues." +"Sometimes this doesn't come in handy as this also means you'll receive error " +"messages about \"email address being in use already\" for (yet) unknown " +"third-party authentication methods." msgstr "" -"Aufgrund der Funktionsweise von Core Workflows werden alle Änderungen an " -"Attributen auf dem Anwendungsserver überprüft - bitte lesen Sie :doc:" -"`limitations` für mögliche Probleme." +"Das ist nicht immer hilfreich, da Sie dann auch Fehlermeldungen über " +"\"bereits verwendete E-Mail-Adressen\" für (noch) unbekannte " +"Authentifizierungsmethoden von Drittanbietern erhalten." -#: ../system/core-workflows/how-do-they-work.rst:12 +#: ../settings/security/third-party.rst:50 msgid "" -"Below we're talking about settings that are important and not self-" -"explanatory." +"If you want to allow your users to always be able to log in, no matter what, " +"you may want to enable ``Automatic account link on initial logon``." msgstr "" -"Im Folgenden geht es um Einstellungen, die wichtig und nicht selbsterklärend " -"sind." +"Wenn Sie es Ihren Benutzern ermöglichen wollen, sich immer anzumelden, " +"sollten Sie ``Automatische Kontoverbindung bei der Erstanmeldung`` " +"aktivieren." -#: ../system/core-workflows/how-do-they-work.rst:17 +#: ../settings/security/third-party.rst:None msgid "" -"Choose the object context you want to run the workflow in. This will decide " -"on your available attributes and actions." +"Screenshot highlighting the \"Automatic account link on initial logon\"\n" +"setting" msgstr "" -"Wählen Sie den Objektkontext, in dem Sie den Workflow ausführen möchten. " -"Dies entscheidet über die verfügbaren Attribute und Aktionen." +"Screenshot mit Hervorhebung der Einstellung \"Automatische Kontoverbindung " +"bei der Erstanmeldung\"" -#: ../system/core-workflows/how-do-they-work.rst:20 -msgid "Ticket objects also have access to the ticket customer." -msgstr "Ticketobjekte haben auch Zugriff auf den Ticketkunden." +#: ../settings/security/third-party.rst:60 +msgid "Automatic Account Linking Notification" +msgstr "Automatische Benachrichtigung beim Verknüpfen von Accounts" -#: ../system/core-workflows/how-do-they-work.rst:25 +#: ../settings/security/third-party.rst:64 msgid "" -"Choose in which situation the workflow is applied. Contexts can be combined " -"to avoid duplicate workflows." +"To improve security and your users awareness, you can enable Zammad to " +"notify your users when a new third-party application has been linked to " +"their account." msgstr "" -"Wählen Sie aus, in welcher Situation der Workflow angewendet werden soll. Im " -"Feld \"Kontext\" können mehrere Einträge gewählt werden, um doppelte Core " -"Workflows zu vermeiden." - -#: ../system/core-workflows/how-do-they-work.rst:30 -msgid "Creation mask" -msgstr "Erstellmaske" +"Um die Sicherheit zu verbessern können Sie Ihre Nutzer durch Zammad " +"benachrichtigen lassen, wenn eine neue Drittanbieteranwendung mit ihrem " +"Konto verknüpft wurde." -#: ../system/core-workflows/how-do-they-work.rst:29 +#: ../settings/security/third-party.rst:68 msgid "" -"If selected, your conditions and actions will affect all applicable creation " -"masks." +"This notification is sent out once per third-party application. Zammad does " +"also mention the method used, e.g.: ``Microsoft``." msgstr "" -"Wenn Sie diese Option wählen, wirken sich Ihre Bedingungen und Aktionen auf " -"alle anwendbaren Erstellungsmasken aus." +"Diese Benachrichtigung wird einmal pro Drittanwendung verschickt. Darin " +"enthalten ist auch die verwendete Methode, z.B.: ``Microsoft``." -#: ../system/core-workflows/how-do-they-work.rst:34 -msgid "Edit mask" -msgstr "Bearbeitungsmaske" +#: ../settings/security/third-party.rst:71 +msgid "By default this setting is not active (set to ``no``)." +msgstr "" +"Standardmäßig ist diese Einstellung nicht aktiv (auf ``nein`` gesetzt)." -#: ../system/core-workflows/how-do-they-work.rst:33 +#: ../settings/security/third-party.rst:0 msgid "" -"If selected, your conditions and actions will affect all applicable edit " -"masks." +"Screenshot showing sample notification mail after initial\n" +"third-party linking" msgstr "" -"Wenn Sie diese Option auswählen, wirken sich Ihre Bedingungen und Aktionen " -"auf alle zutreffenden Bearbeitungsmasken aus." +"Screenshot mit Beispiel einer Benachrichtigungsmail nach der ersten " +"Verknüpfung mit Drittanbieter-Login" -#: ../system/core-workflows/how-do-they-work.rst:39 +#: ../settings/security/third-party.rst:85 msgid "" -"Zammad differentiates between selected and saved conditions. These can be " -"combined wherever needed." +"This notification is only sent if the account in question already exists. If " +"the login via the third-party also creates the missing account, the " +"notification will be skipped." msgstr "" -"Zammad unterscheidet zwischen ausgewählten und gespeicherten Bedingungen. " -"Diese können bei Bedarf kombiniert werden." +"Diese Benachrichtigung wird nur gesendet, wenn das betreffende Konto bereits " +"existiert. Wenn die Anmeldung über den Drittanbieter auch das fehlende Konto " +"erstellt, wird die Benachrichtigung übersprungen." -#: ../system/core-workflows/how-do-they-work.rst:42 -msgid "**⚠️ Restrict workflows to specific roles if needed!**" +#: ../settings/security/third-party.rst:89 +msgid "This means it only affects:" +msgstr "Dies bedeutet, dass es nur Auswirkungen hat auf:" + +#: ../settings/security/third-party.rst:91 +msgid "manual account linking within the third-party page of the users profile" msgstr "" -"**⚠️ Schränken Sie Core Workflows auf bestimmte Rollen ein, falls " -"erforderlich!**" +"manuelle Verknüpfung des Benutzerprofils mit einem Konto auf der " +"Drittanbieterseite" -#: ../system/core-workflows/how-do-they-work.rst:44 +#: ../settings/security/third-party.rst:92 msgid "" -"By default and unless configured in conditions, workflow rules are executed " -"for **all roles**. This also affects your customers!" +"logging into an existing local account by utilizing the *automatic account " +"link on initial logon* functionality" msgstr "" -"Standardmäßig werden Workflow-Regeln für **alle Rollen** ausgeführt, sofern " -"nichts anderes in den Bedingungen konfiguriert wurde. Dies betrifft auch " -"Ihre Kunden!" - -#: ../system/core-workflows/how-do-they-work.rst:50 -msgid "Selected Conditions" -msgstr "Ausgewählte Bedingungen" +"Einloggen in ein bestehendes lokales Konto durch Nutzung der Funktion " +"*Automatische Kontoverbindung bei der Erstanmeldung*." -#: ../system/core-workflows/how-do-they-work.rst:48 +#: ../settings/security/third-party.rst:None msgid "" -"These conditions are based on form values and match if an appropriate " -"selection is made (e.g. choosing another group in the ticket without " -"saving). This applies for drafts (active selection) and currently saved " -"values." +"Screenshot showing the \"automatic account linking notification\"\n" +"setting" msgstr "" -"Diese Bedingungen basieren auf Formularwerten und treffen zu, wenn eine " -"entsprechende Auswahl getroffen wird (z.B. Auswahl einer anderen Gruppe im " -"Ticket ohne Speichern). Dies gilt für Entwürfe (aktive Auswahl) und aktuell " -"gespeicherte Werte." +"Screenshot mit der Einstellung \"Automatische Kontoverbindung bei der " +"Erstanmeldung\"" -#: ../system/core-workflows/how-do-they-work.rst:64 -msgid "Saved Conditions" -msgstr "Gespeicherte Bedingungen" +#: ../settings/security/third-party.rst:100 +msgid "No User Creation on Logon" +msgstr "Keine Erstellung von Benutzern bei der Anmeldung" -#: ../system/core-workflows/how-do-they-work.rst:53 +#: ../settings/security/third-party.rst:102 msgid "" -"These conditions only match if the selected values are stored in the " -"database. It ignores the current value or selection of the field, as long as " -"the changes are not saved (e.g. performing field operations for an existing " -"ticket, which is viewed/opened by an agent)." +"By default, Zammad will create a new user account if the user logs in via a " +"third-party application and the account doesn't exist yet." msgstr "" -"Diese Bedingungen treffen nur zu, wenn die ausgewählten Werte in der " -"Datenbank gespeichert sind. Der aktuelle Wert oder die Auswahl des Feldes " -"wird ignoriert, solange die Änderungen nicht gespeichert werden (z.B. bei " -"der Durchführung von Änderungen an einem bestehenden Ticket, das von einem " -"Agenten angesehen/geöffnet wird)." +"Standardmäßig erstellt Zammad ein neues Benutzerkonto, wenn sich der " +"Benutzer über eine Drittanbieteranwendung anmeldet und das Konto noch nicht " +"existiert." -#: ../system/core-workflows/how-do-they-work.rst:60 +#: ../settings/security/third-party.rst:105 msgid "" -"Keep in mind that the value has to be available in the situation where you " -"need it. Otherwise the condition won't match." +"If you want to prevent Zammad from creating new accounts on logon, you can " +"disable this feature by setting ``No user creation on logon`` to ``yes``." msgstr "" -"Denken Sie daran, dass der Wert zum Zeitpunkt der Ausführung verfügbar sein " -"muss. Andernfalls wird die Bedingung nicht erfüllt." +"Wenn Sie verhindern wollen, dass Zammad bei der Anmeldung neue Konten " +"anlegt, können Sie diese Funktion deaktivieren, indem Sie ``Keine Erstellung " +"von Benutzern bei der Anmeldung`` auf ``ja`` setzen." -#: ../system/core-workflows/how-do-they-work.rst:63 -msgid "" -"Example: you can't perform any actions with *saved condition* on a ticket in " -"creation, because there are no saved values at that time." +#: ../settings/security/third-party.rst:None +msgid "Screenshot showing the \"no user creation on logon\" setting" msgstr "" -"Beispiel: Sie können keine Aktionen mit *gespeicherter Bedingung* für ein " -"Ticket durchführen, das gerade erstellt wird, da es zu diesem Zeitpunkt " -"keine gespeicherten Werte gibt." +"Screenshot zeigt die Einstellung \"keine Erstellung von Benutzern bei der " +"Anmeldung\"" -#: ../system/core-workflows/how-do-they-work.rst:66 +#: ../settings/security/third-party/facebook.rst:4 msgid "" -"You can find a description of the condition operators for core workflows :" -"doc:`here `." +"It is possible to create a quick login for your helpdesk via Facebook To do " +"so, you need to follow these steps:" msgstr "" -"Eine Beschreibung der Bedingungsoperatoren für Core Workflows finden Sie :" -"doc:`hier `." +"Es ist möglich, eine Anmeldung über Facebook zu erstellen. Dazu müssen Sie " +"die folgenden Schritte ausführen:" -#: ../system/core-workflows/how-do-they-work.rst:72 +#: ../settings/security/third-party/facebook.rst:9 +msgid "Register Facebook App" +msgstr "Facebook-App registrieren" + +#: ../settings/security/third-party/facebook.rst:11 msgid "" -"Which actions should we run on the relevant fields? The possible actions " -"depend on the object type. However, usually you can at least change the " -"visibility and whether the field is mandatory." +"Visit [https://developers.facebook.com/apps/] and click on \"Add a new App\"" msgstr "" -"Welche Aktionen sollen ausgeführt werden? Die möglichen Aktionen hängen vom " -"Objekttyp ab. Normalerweise können Sie jedoch mindestens die Sichtbarkeit " -"ändern und angeben, ob das Feld ein Pflichtfeld ist." +"Besuchen Sie [https://developers.facebook.com/apps/] und klicken Sie auf " +"\"Eine neue App hinzufügen\"" -#: ../system/core-workflows/how-do-they-work.rst:76 -msgid "Be aware that actions are not available for **related** context." -msgstr "" -"Beachten Sie, dass Aktionen nicht verfügbar sind für in Beziehungen stehende " -"Objekte." +#: ../settings/security/third-party/facebook.rst:None +msgid "initial page" +msgstr "Startseite" -#: ../system/core-workflows/how-do-they-work.rst:78 -msgid "" -"**Example:** Let's assume you are working in the ticket context. While you " -"can have customer *conditions*, you *can't adjust* objects with actions in " -"that scope. That's because this wouldn't have any impact on the ticket " -"dialog. Of course all ticket attributes (state, owner, ...) are available." +#: ../settings/security/third-party/facebook.rst:17 +msgid "After that enter the app settings" +msgstr "Geben Sie danach die Einstellungen der App ein" + +#: ../settings/security/third-party/facebook.rst:None +msgid "Create App" +msgstr "App erstellen" + +#: ../settings/security/third-party/facebook.rst:22 +msgid "Navigate to \"Settings\" and fill in this infromation" msgstr "" -"**Beispiel:** Nehmen wir an, Sie arbeiten im Ticket-Kontext. Sie können zwar " -"*Bedingungen* haben, die sich auf Kunden beziehen, aber Sie können *keine " -"Anpassungen mit Aktionen* in diesem Kontext vornehmen. Das liegt daran, dass " -"dies keine Auswirkung auf den Ticket-Dialog haben würde. Natürlich sind alle " -"Ticket-Attribute (Status, Besitzer, ...) verfügbar." +"Navigieren Sie zu \"Einstellungen\" und geben Sie diese Informationen ein" -#: ../system/core-workflows/how-do-they-work.rst:84 -msgid "" -"Please also have a look at our :doc:`limitations` to be safe from surprises." +#: ../settings/security/third-party/facebook.rst:None +msgid "App Settings" +msgstr "App-Einstellungen" + +#: ../settings/security/third-party/facebook.rst:27 +msgid "Navigate to app review and Check \"Make [appname] public?\"" msgstr "" -"Bitte beachten Sie auch unsere :doc:`limitations`, um vor Überraschungen " -"sicher zu sein." +"Navigieren Sie zur App-Prüfung und setzen Sie einen Haken bei \"[Appname] " +"öffentlich machen?\"" -#: ../system/core-workflows/how-do-they-work.rst:88 -msgid "Available Operators" -msgstr "Verfügbare Operatoren" +#: ../settings/security/third-party/facebook.rst:None +msgid "App Review" +msgstr "App-Prüfung" -#: ../system/core-workflows/how-do-they-work.rst:90 -msgid "The availability of operators depends on the object type and scope." -msgstr "Die Verfügbarkeit von Operatoren hängt von dem Objekt ab." +#: ../settings/security/third-party/facebook.rst:35 +msgid "Configure Zammad as Facebook App" +msgstr "Zammad als Facebook-App konfigurieren" -#: ../system/core-workflows/how-do-they-work.rst:94 +#: ../settings/security/third-party/facebook.rst:37 msgid "" -"Please note that actions may or may not restrict API based access to " -"attributes. We're displaying the following icons for your overview to " -"understand these limits better:" +"Navigate to \"Admin -> Security -> Third Party Applications\" and enter the " +"App ID and the App Secret. You can find this Key in the Dashbard of your " +"Facebok app." msgstr "" -"Bitte beachten Sie, dass Aktionen den API-basierten Zugriff auf Attribute " -"einschränken können, aber nicht müssen. Wir zeigen Ihnen die folgenden " -"Symbole an, damit Sie die Einschränkungen besser verstehen:" - -#: ../system/core-workflows/how-do-they-work.rst:0 -msgid "|api| This icon indicates the action affects the API." -msgstr "|api| Dieses Symbol zeigt an, dass die Aktion die API betrifft." +"Navigieren Sie zu \"Einstellungen > Sicherheit > Anwendungen von " +"Drittanbietern\" und geben Sie die App-ID und das App-Secret ein. Sie finden " +"die beiden Werte im Dashbard Ihrer Facebok-App." -#: ../system/core-workflows/how-do-they-work.rst:163 -msgid "api" -msgstr "api" +#: ../settings/security/third-party/facebook.rst:None +msgid "Zammad Configuration" +msgstr "Zammad Konfiguration" -#: ../system/core-workflows/how-do-they-work.rst:0 -msgid "|ui| This icon indicates the action only affects the web interface." +#: ../settings/security/third-party/facebook.rst:44 +#: ../settings/security/third-party/github.rst:43 +#: ../settings/security/third-party/gitlab.rst:46 +msgid "" +"Now you can link accounts via \"Avatar -> Profile -> Link Accounts\" or " +"login via Zammad login page." msgstr "" -"|ui| Dieses Symbol zeigt an, dass die Aktion nur die Weboberfläche betrifft." +"Jetzt können Sie Konten über \"Avatar > Profil > Verknüpfte Konten\" " +"verknüpfen oder sich über die Zammad-Login-Seite anmelden." -#: ../system/core-workflows/how-do-they-work.rst:167 -msgid "ui" -msgstr "ui" - -#: ../system/core-workflows/how-do-they-work.rst:102 -msgid "show |ui|" -msgstr "anzeigen |ui|" - -#: ../system/core-workflows/how-do-they-work.rst:102 -msgid "Display the chosen field. Allows setting of values." -msgstr "Zeigt das ausgewählte Feld an. Ermöglicht die Einstellung von Werten." - -#: ../system/core-workflows/how-do-they-work.rst:109 -msgid "hide |ui|" -msgstr "verstecken |ui|" +#: ../settings/security/third-party/github.rst:2 +#: ../system/integrations/github.rst:2 +msgid "GitHub" +msgstr "GitHub" -#: ../system/core-workflows/how-do-they-work.rst:105 +#: ../settings/security/third-party/github.rst:4 msgid "" -"Hide the chosen field. However, it technically still allows setting the " -"field." +"It is possible to create a quick login for your helpdesk via GitHub. To " +"activate the quick login you need to enable OAuth for GitHub." msgstr "" -"Ausblenden des gewählten Feldes. Technisch gesehen kann das Feld aber immer " -"noch eingestellt werden." +"Es ist möglich, eine Anmeldung über GitHub zu erstellen. Um diese zu " +"aktivieren, müssen Sie OAuth für GitHub aktivieren." -#: ../system/core-workflows/how-do-they-work.rst:108 +#: ../settings/security/third-party/github.rst:8 +msgid "Register GitHub App" +msgstr "GitHub-App registrieren" + +#: ../settings/security/third-party/github.rst:10 msgid "" -"Please note that the field is **not** gone and still contains an existing " -"value (if set)! Consider *remove* instead, if you want this field to be gone." +"Visit https://www.github.com/settings/applications/new and enter the app " +"settings. As callback URL enter \"https://zammad_host/auth/github/callback\" " +"where zammad_host has to be replaced with your Zammad FQDN" msgstr "" -"Bitte beachten Sie, dass das Feld **nicht** verschwunden ist und immer noch " -"einen vorhandenen Wert enthält (falls gesetzt)! Ziehen Sie stattdessen " -"*entfernen* in Betracht, wenn Sie wollen, dass dieses Feld wirklich " -"verschwindet." - -#: ../system/core-workflows/how-do-they-work.rst:112 -msgid "remove |ui|" -msgstr "entfernen |ui|" - -#: ../system/core-workflows/how-do-they-work.rst:112 -msgid "Entirely removes the field. The field value will not be evaluated." -msgstr "Entfernt das Feld vollständig. Der Feldwert wird nicht ausgewertet." +"Besuchen Sie https://www.github.com/settings/applications/new und geben Sie " +"die App-Einstellungen ein. Geben Sie als Callback-URL \"https://zammad_host/" +"auth/github/callback\" ein, wobei zammad_host durch Ihren Zammad-FQDN " +"ersetzt werden muss" -#: ../system/core-workflows/how-do-they-work.rst:115 -msgid "set mandatory |ui| |api|" -msgstr "als erforderlich festlegen |ui| |api|" +#: ../settings/security/third-party/github.rst:None +msgid "Register OAuth app on www.github.com" +msgstr "OAuth-App auf www.github.com registrieren" -#: ../system/core-workflows/how-do-they-work.rst:115 -msgid "Sets the field to mandatory." -msgstr "Definiert das Feld als Pflichtfeld." +#: ../settings/security/third-party/github.rst:19 +msgid "Configure Zammad as GitHub App" +msgstr "Zammad als GitHub-Anwendung konfigurieren" -#: ../system/core-workflows/how-do-they-work.rst:118 -msgid "set optional |ui| |api|" -msgstr "als optional festlegen |ui| |api|" +#: ../settings/security/third-party/github.rst:21 +msgid "" +"Enter the \"APP ID\" and the \"APP SECRET\" from the GitHub OAUTH " +"Applications Dashboard" +msgstr "" +"Geben Sie die \"APP ID\" und das \"APP SECRET\" aus dem GitHub OAUTH " +"Applications Dashboard ein" -#: ../system/core-workflows/how-do-they-work.rst:118 -msgid "Sets the field to optional." -msgstr "Definiert das Feld als optionales Feld." +#: ../settings/security/third-party/github.rst:None +msgid "GitHub config in Zammad admin interface" +msgstr "GitHub-Konfiguration im Zammad Admin-Bereich" -#: ../system/core-workflows/how-do-they-work.rst:124 -msgid "add option |ui| |api|" -msgstr "Option hinzufügen |ui| |api|" +#: ../settings/security/third-party/github.rst:28 +msgid "" +"After you configured the GitHub credentials and activated the login method, " +"you should see a new icon on the login page." +msgstr "" +"Nachdem Sie die GitHub-Zugangsdaten konfiguriert und die Anmeldemethode " +"aktiviert haben, sollten Sie ein neues Symbol auf der Anmeldeseite sehen." -#: ../system/core-workflows/how-do-they-work.rst:121 -msgid "Allows adding options to tree selects or selects." -msgstr "Ermöglicht das Hinzufügen von Optionen zu Auswahlen und Baumauswahlen." +#: ../settings/security/third-party/github.rst:None +msgid "GitHub logo on login page" +msgstr "GitHub-Logo auf der Anmeldeseite" -#: ../system/core-workflows/how-do-they-work.rst:123 +#: ../settings/security/third-party/github.rst:34 msgid "" -"You have to use the \"remove option\" before performing this action. It " -"allows you to use *existing* configured values." +"If you click on the icon you will be redirected to GitHub and see something " +"similar to this:" msgstr "" -"Bevor Sie diese Aktion durchführen, müssen Sie die Option \"Entfernen\" " -"verwenden. Im Anschluss können Sie damit *vorhandene* konfigurierte Werte " -"verwenden." +"Wenn Sie auf das Symbol klicken, werden Sie zu GitHub weitergeleitet und " +"sehen einen Dialog ähnlich dem folgenden:" -#: ../system/core-workflows/how-do-they-work.rst:128 -msgid "remove option |ui| |api|" -msgstr "Option entfernen |ui| |api|" +#: ../settings/security/third-party/github.rst:None +msgid "GitHub oauth page" +msgstr "GitHub oauth Seite" -#: ../system/core-workflows/how-do-they-work.rst:127 +#: ../settings/security/third-party/github.rst:40 +#: ../settings/security/third-party/gitlab.rst:42 msgid "" -"Allows removing options from tree selects or selects. It allows you to use " -"*existing* configured values." +"When you grant the access you will be redirected to your Zammad instance and " +"logged in as a customer." msgstr "" -"Ermöglicht das Entfernen von Optionen aus Baumauswahl oder Auswahl-Feldern. " -"Damit können Sie *vorhandene* konfigurierte Werte verwenden." - -#: ../system/core-workflows/how-do-they-work.rst:134 -msgid "set fixed to |ui| |api|" -msgstr "fest eingestellt auf |ui| |api|" +"Wenn Sie den Zugang gewähren, werden Sie zu Ihrer Zammad-Instanz " +"weitergeleitet und eingeloggt." -#: ../system/core-workflows/how-do-they-work.rst:131 -msgid "Reduces the available options by your selection." -msgstr "Reduziert die verfügbaren Optionen um Ihre Auswahl." +#: ../settings/security/third-party/gitlab.rst:2 +msgid "Gitlab" +msgstr "Gitlab" -#: ../system/core-workflows/how-do-they-work.rst:133 +#: ../settings/security/third-party/gitlab.rst:4 msgid "" -"This reduces your workflows in terms of *add option* and *remove option*." +"It is possible to create a quick login for your helpdesk via Gitlab. To " +"activate the quick login you need to enable OAuth for Gitlab." msgstr "" -"Dies reduziert Ihre Workflows bzgl. *Option hinzufügen* und *Option " -"entfernen*." - -#: ../system/core-workflows/how-do-they-work.rst:137 -msgid "fill in |ui|" -msgstr "befüllen mit |ui|" +"Es ist möglich, eine Anmeldung über Gitlab zu erstellen. Um diese zu " +"aktivieren, müssen Sie OAuth für Gitlab aktivieren." -#: ../system/core-workflows/how-do-they-work.rst:137 -msgid "Allows filling in of string and integer fields with your values." -msgstr "Ermöglicht die Befüllung von Text- und Zahlen-Feldern mit einem Wert." +#: ../settings/security/third-party/gitlab.rst:8 +msgid "Register Gitlab App" +msgstr "Gitlab-App registrieren" -#: ../system/core-workflows/how-do-they-work.rst:141 -msgid "fill in empty |ui|" -msgstr "befüllen mit (wenn leer) |ui|" +#: ../settings/security/third-party/gitlab.rst:10 +msgid "To register an app in Gitlab open your profile and select applications." +msgstr "" +"Um eine Anwendung in Gitlab zu registrieren, öffnen Sie Ihr Profil und " +"wählen Sie Anwendungen." -#: ../system/core-workflows/how-do-they-work.rst:140 +#: ../settings/security/third-party/gitlab.rst:12 msgid "" -"Allows filling in of string and integer fields with your values **if the " -"field is empty**." +"As callback URL enter \"https://zammad-fqdn/auth/gitlab/callback\" where " +"zammad-fqdn has to be replaced with your Zammad FQDN" msgstr "" -"Ermöglicht die Befüllung von Text- und Zahlen-Feldern mit einem Wert **wenn " -"das Feld leer ist**." +"Als Callback-URL geben Sie \"https://zammad-fqdn/auth/gitlab/callback\" ein, " +"wobei zammad-fqdn durch Ihren Zammad-FQDN ersetzt werden muss" -#: ../system/core-workflows/how-do-they-work.rst:144 -msgid "select |ui|" -msgstr "auswählen |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Register OAuth app on gitlab instance" +msgstr "OAuth-Anwendung auf Gitlab-Instanz registrieren" -#: ../system/core-workflows/how-do-they-work.rst:144 -msgid "Select a specific value within a select, tree select or boolean field." +#: ../settings/security/third-party/gitlab.rst:18 +msgid "Just select *read_user* under scopes as in the screenshot and save it." msgstr "" -"Wählen Sie einen bestimmten Wert innerhalb eines Auswahl-, Baumauswahl- oder " -"Boolean-Feldes aus." - -#: ../system/core-workflows/how-do-they-work.rst:153 -msgid "auto select |ui|" -msgstr "automatisch auswählen |ui|" +"Wählen Sie nur *read_user* unter scopes wie im Screenshot und speichern Sie." -#: ../system/core-workflows/how-do-they-work.rst:147 -msgid "Helps users with tree select and select fields:" -msgstr "Hilft den Benutzern bei Baumauswahl- und Auswahlfeldern:" +#: ../settings/security/third-party/gitlab.rst:21 +msgid "Configure Zammad as Gitlab App" +msgstr "Zammad als Gitlab-Anwendung konfigurieren" -#: ../system/core-workflows/how-do-they-work.rst:149 +#: ../settings/security/third-party/gitlab.rst:23 msgid "" -"If the field has only one option available for selection and no value yet, " -"the value will be automatically set." +"Enter the \"APP ID\" and the \"APP SECRET\" from the Gitlab OAUTH " +"Applications Dashboard and your Gitlab-URL in the \"SITE\" field." msgstr "" -"Wenn für das Feld nur eine Option zur Auswahl steht und noch kein Wert " -"vorhanden ist, wird der Wert automatisch gesetzt." +"Geben Sie die \"APP ID\" und das \"APP SECRET\" aus dem Gitlab OAUTH " +"Applications Dashboard und Ihre Gitlab-URL in das Feld \"SITE\" ein." -#: ../system/core-workflows/how-do-they-work.rst:152 +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab config in Zammad admin interface" +msgstr "Gitlab-Konfiguration in der Zammad-Verwaltungsoberfläche" + +#: ../settings/security/third-party/gitlab.rst:30 msgid "" -"This option only works if you have one value and doesn't work if there is " -"more than one option available." +"After you configured the Gitlab credentials and activated the login method, " +"you should see a new icon on the login page." msgstr "" -"Diese Option funktioniert nur, wenn Sie genau einen Wert haben. Sie " -"funktioniert nicht, wenn mehr als eine Option verfügbar ist." +"Nachdem Sie die Gitlab-Anmeldedaten konfiguriert und die Anmeldemethode " +"aktiviert haben, sollten Sie ein neues Symbol auf der Anmeldeseite sehen." -#: ../system/core-workflows/how-do-they-work.rst:157 -msgid "set readonly |ui|" -msgstr "als schreibgeschützt festlegen |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab logo on login page" +msgstr "Gitlab-Logo auf der Anmeldeseite" -#: ../system/core-workflows/how-do-they-work.rst:156 +#: ../settings/security/third-party/gitlab.rst:36 msgid "" -"Allows you to display an attribute as read only (which means no changes are " -"possible)." +"If you click on the icon you will be redirected to Gitlab and see something " +"similar to this:" msgstr "" -"Ermöglicht die schreibgeschützte Anzeige eines Attributs (was bedeutet, dass " -"keine Änderungen möglich sind)." +"Wenn Sie auf das Symbol klicken, werden Sie zu Gitlab weitergeleitet und " +"sehen einen Dialog ähnlich dem folgenden:" -#: ../system/core-workflows/how-do-they-work.rst:161 -msgid "unset readonly |ui|" -msgstr "als änderbar festlegen |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab oauth page" +msgstr "Gitlab oauth Seite" -#: ../system/core-workflows/how-do-they-work.rst:160 +#: ../settings/security/third-party/google.rst:4 msgid "" -"In case a workflow set the field in question to read only, you can undo this " -"with option above." +"With some easy and fast steps, you can enable Zammad to authenticate your " +"users via Google." msgstr "" -"Falls ein Workflow das betreffende Feld auf schreibgeschützt gesetzt hat, " -"können Sie dies mit der obigen Option rückgängig machen." +"In ein paar Schritten können Sie in Zammad die Authentifizierung über Google " +"aktivieren." -#: ../system/core-workflows/how-do-they-work.rst:172 -msgid "Stop after match" -msgstr "Nach Treffer stoppen" +#: ../settings/security/third-party/google.rst:8 +msgid "Register a Google App" +msgstr "Eine Google-App registrieren" -#: ../system/core-workflows/how-do-they-work.rst:174 +#: ../settings/security/third-party/google.rst:10 msgid "" -"Here you can decide if other workflows are executed after the current one." +"First of all, we need to create a new project - you can skip this step if " +"you already have one." msgstr "" -"Hier können Sie festlegen, ob andere Workflows nach dem aktuellen ausgeführt " -"werden." +"Zunächst müssen wir ein neues Projekt erstellen - Sie können diesen Schritt " +"überspringen, wenn Sie bereits ein Projekt haben." -#: ../system/core-workflows/how-do-they-work.rst:176 +#: ../settings/security/third-party/google.rst:15 msgid "" -"If set to ``no`` (default), further workflows will be executed if they match " -"the condition. In this case, it is possible that your actions from the " -"current workflow can be overwritten by another workflow." +"Use this link to create a new project: https://console.cloud.google.com/" +"projectcreate" msgstr "" -"Bei der Einstellung ``Nein`` (Standard) werden weitere Workflows ausgeführt, " -"wenn sie die Bedingung erfüllen. In diesem Fall ist es möglich, dass Ihre " -"Aktionen aus dem aktuellen Workflow von einem anderen Workflow überschrieben " -"werden." +"Verwenden Sie diesen Link, um ein neues Projekt zu erstellen: https://" +"console.cloud.google.com/projectcreate" -#: ../system/core-workflows/how-do-they-work.rst:180 +#: ../settings/security/third-party/google.rst:18 msgid "" -"If set to ``yes``, no further worflows will be executed after the current " -"one." +"Now expand the menu, expand \"APIs & Services\" and select \"Credentials\". " +"Go to the tab \"OAuth consent screen\" first and ensure to fill in the " +"requested information - without doing so you can't create credentials!" msgstr "" -"Wird der Wert auf ``Ja`` gesetzt, werden nach dem aktuellen keine weiteren " -"Workflows mehr ausgeführt." +"Erweitern Sie nun das Menü, erweitern Sie \"APIs & Services\" und wählen Sie " +"\"Credentials\". Gehen Sie zuerst auf die Registerkarte \"OAuth consent " +"screen\" und geben Sie die erforderlichen Informationen ein - ohne diese " +"Angaben können Sie keine Anmeldung erstellen!" -#: ../system/core-workflows/how-do-they-work.rst:184 -msgid "Priority" -msgstr "Priorität" +#: ../settings/security/third-party/google.rst:None +msgid "Creating a consent screen" +msgstr "Erstellen eines Einwilligungs-Dialogs" -#: ../system/core-workflows/how-do-they-work.rst:186 +#: ../settings/security/third-party/google.rst:25 msgid "" -"You can define the sequence, in which the workflows are executed. The " -"default value is ``500``." +"After filling in and saving the consent screen information, you can go to " +"the \"Credentials\" tab and create new \"OAuth client ID\"-Credentials." msgstr "" -"Sie können die Reihenfolge festlegen, in der die Arbeitsabläufe ausgeführt " -"werden. Der Standardwert ist ``500``." +"Nach dem Ausfüllen und Speichern der Informationen auf dem Einwilligungs-" +"Dialog können Sie auf die Registerkarte \"Credentials\" wechseln und neue " +"\"OAuth client ID\"-Credentials erstellen." -#: ../system/core-workflows/how-do-they-work.rst:189 +#: ../settings/security/third-party/google.rst:28 msgid "" -"The workflows are executed in ascending order by their priority. That means " -"lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." +"Fill in the necessary information as follows and replace ``zammad_host`` " +"with your FQDN:" msgstr "" -"Die Workflows werden in aufsteigender Reihenfolge nach ihrer Priorität " -"ausgeführt. Das heißt, niedrigere Werte (z.B. ``100``) werden vor höheren (z." -"B. ``999``) ausgeführt." +"Geben Sie die erforderlichen Informationen wie folgt ein und ersetzen Sie " +"``zammad_host`` durch Ihren FQDN:" -#: ../system/core-workflows/learn-by-example.rst:2 -msgid "Learn by Example" -msgstr "Lernen Sie anhand von Beispielen" +#: ../settings/security/third-party/google.rst:31 +msgid "**Application type** ``[x] Web application``" +msgstr "**Application type** ``[x] Web application``" -#: ../system/core-workflows/learn-by-example.rst:4 -msgid "" -"This page provides some basic examples for Core Workflows. Of course you can " -"build much more complex workflows if needed." -msgstr "" -"Diese Seite enthält einige grundlegende Beispiele für Core Workflows. " -"Natürlich können Sie bei Bedarf auch komplexere Workflows erstellen." +#: ../settings/security/third-party/google.rst:34 +msgid "**Authorized JavaScript origins** ``https://zammad_host/``" +msgstr "**Authorized JavaScript origins** ``https://zammad_host/``" -#: ../system/core-workflows/learn-by-example.rst:7 +#: ../settings/security/third-party/google.rst:37 msgid "" -"To learn about Core Workflows in detail, first go to :doc:`how-do-they-work`." +"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" +"callback``" msgstr "" -"Um mehr über Core Workflows im Detail zu erfahren, gehen Sie zuerst zu :doc:" -"`how-do-they-work`." +"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" +"callback``" -#: ../system/core-workflows/learn-by-example.rst:10 -msgid "Group Based Examples" -msgstr "Gruppenbasierte Beispiele" +#: ../settings/security/third-party/google.rst:None +msgid "Adding a new OAuth client ID" +msgstr "Hinzufügen einer neuen OAuth-Client-ID" -#: ../system/core-workflows/learn-by-example.rst:12 +#: ../settings/security/third-party/google.rst:43 msgid "" -"All following workflows have the same base configurations. The workflow may " -"not use them all." +"After creating the credentials, go to your Zammad installation and navigate " +"to \"Admin > Security > Third Party Applications\" > Google. Enter your " +"Client ID and Client secret here." msgstr "" -"Alle folgenden Workflows haben die gleichen Basiskonfigurationen. Der " -"Workflow muss nicht alle Konfigurationen verwenden." +"Nachdem Sie die Zugangsdaten erstellt haben, gehen Sie zu Ihrer Zammad-" +"Installation und navigieren Sie zu \"Einstellungen > Sicherheit > " +"Anwendungen von Drittanbietern\" > Google. Geben Sie hier Ihre Client-ID und " +"Ihr Client-Secret ein." -#: ../system/core-workflows/learn-by-example.rst:15 -msgid "Groups:" -msgstr "Gruppen:" +#: ../settings/security/third-party/google.rst:None +msgid "Zammad" +msgstr "Zammad" -#: ../system/core-workflows/learn-by-example.rst:20 -msgid "Attributes:" -msgstr "Attribute:" +#: ../settings/security/third-party/google.rst:50 +msgid "After submitting, the login via Google can be used." +msgstr "Nach dem Speichern kann der Login über Google verwendet werden." -#: ../system/core-workflows/learn-by-example.rst:22 -msgid "Category (Single tree selection field, not mandatory, agents only)" -msgstr "Kategorie (Einfach-Baumauswahl-Feld, kein Pflichtfeld, nur Agenten)" +#: ../settings/security/third-party/microsoft.rst:2 +msgid "Microsoft" +msgstr "Microsoft" -#: ../system/core-workflows/learn-by-example.rst:23 +#: ../settings/security/third-party/microsoft.rst:4 msgid "" -"Approved (Boolean field, not mandatory, not shown, ``false`` as default)" +"Zammad's Microsoft connection allows your users with Microsoft accounts to " +"login. This works for Azure users as well and can be an alternative to :doc:" +"`/system/integrations/ldap/index`." msgstr "" -"Genehmigt (Boolean-Feld, kein Pflichtfeld, versteckt, ``false`` als Standard)" +"Die Microsoft-Andingung von Zammad ermöglicht Ihren Benutzern die Anmeldung " +"mit einem Microsoft-Konto. Dies funktioniert auch für Azure-Benutzer und " +"kann eine Alternative zu :doc:`/system/integrations/ldap/index` sein." -#: ../system/core-workflows/learn-by-example.rst:24 -msgid "Operating System (Text field, not mandatory, not shown)" -msgstr "Betriebssystem (Textfeld, kein Pflichtfeld, versteckt)" +#: ../settings/security/third-party/microsoft.rst:10 +msgid "" +"This documentation part does not cover our :doc:`📧 Microsoft 365 email " +"channel `." +msgstr "" +"Dieser Teil der Dokumentation deckt nicht unseren :doc:`📧 Microsoft 365-" +"Kanal ` ab." -#: ../system/core-workflows/learn-by-example.rst:25 -msgid "Software used (Single selection field, not mandatory, not shown)" -msgstr "Verwendete Software (Einfachauswahl-Feld, kein Pflichtfeld, versteckt)" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screenshot showing Microsoft login button on Zammad login screen." +msgstr "Screenshot der Microsoft-Anmeldung auf dem Anmeldedialog von Zammad." -#: ../system/core-workflows/learn-by-example.rst:68 -msgid "Group specific values and fields" -msgstr "Gruppenspezifische Werte und Felder" +#: ../settings/security/third-party/microsoft.rst:30 +#: ../settings/security/third-party/microsoft.rst:53 +msgid "Supported account types:" +msgstr "Unterstützte Konten-Typen:" -#: ../system/core-workflows/learn-by-example.rst:28 +#: ../settings/security/third-party/microsoft.rst:22 msgid "" -"This workflow set depends on the category field. It reduces the available " -"set of values based on the group selected." +"Please note that Zammad only supports these account types (App dependent):" msgstr "" -"Dieser Workflow hängt vom Kategorie-Feld ab. Es verringert die möglichen " -"auswählbaren Werte auf der Grundlage der ausgewählten Gruppe." +"Bitte beachten Sie, dass Zammad nur diese Kontotypen unterstützt (App-" +"abhängig):" -#: ../system/core-workflows/learn-by-example.rst:33 -msgid "Workflow 2nd Level group" -msgstr "Workflow 2nd Level Gruppe" +#: ../settings/security/third-party/microsoft.rst:35 +msgid "Avatars of signing in users:" +msgstr "Avatare der angemeldeten Benutzer:" -#: ../system/core-workflows/learn-by-example.rst:35 +#: ../settings/security/third-party/microsoft.rst:33 msgid "" -"This reduces the category options to ``2nd Level/*``, ``Internal/*`` and " -"``Others``. It also sets further required fields to mandatory and visible." +"Zammad currently ignores user avatars. If the user is registered with e.g. " +"Gravatar, Zammad will fetch the avatar from there if enabled. See :doc:" +"`Zammad Image Service ` for more." msgstr "" -"Dies reduziert die Kategorieoptionen auf ``2nd Level/*``, ``Internal/*`` und " -"``Others``. Außerdem werden weitere erforderliche Felder als Pflichtfelder " -"und sichtbar gesetzt." - -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for 2nd level" -msgstr "Beispiel-Workflow, der bestimmte Werte und Felder für 2nd Level zeigt" +"Zammad ignoriert derzeit Benutzeravatare. Wenn der Benutzer z.B. bei " +"Gravatar registriert ist, bezieht Zammad den Avatar von dort, falls " +"aktiviert. Siehe :doc:`Zammad Bilder Service ` für " +"mehr." -#: ../system/core-workflows/learn-by-example.rst:43 -msgid "Workflow Support group" -msgstr "Workflow Support Gruppe" +#: ../settings/security/third-party/microsoft.rst:38 +msgid "Step 1 - Register a Microsoft App for Zammad" +msgstr "Schritt 1 - Registrieren einer Microsoft-App für Zammad" -#: ../system/core-workflows/learn-by-example.rst:45 +#: ../settings/security/third-party/microsoft.rst:40 msgid "" -"This reduces the category options to ``Support/*``, ``Internal/*`` and " -"``Others``. It also sets further required fields to visible." +"Login to the `Microsoft Azure Portal `_ and " +"navigate to App registrations to create a new app. Provide the requested " +"information as follows and register your app." msgstr "" -"Dieser Workflow reduziert die möglichen Kategorien auf ``Support/*``, " -"``Intern/*`` und ``Others``. Außerdem werden weitere Felder auf sichtbar und " -"als Pflichtfeld gesetzt." - -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for support" -msgstr "Beispiel-Workflow, der bestimmte Werte und Felder für Support zeigt" +"Melden Sie sich im `Microsoft Azure Portal `_ an " +"und navigieren Sie zu App-Registrierungen, um eine neue App zu erstellen. " +"Geben Sie die erforderlichen Informationen wie folgt an und registrieren Sie " +"Ihre App." -#: ../system/core-workflows/learn-by-example.rst:53 -msgid "Workflow Sales group" -msgstr "Workflow Sales Gruppe" +#: ../settings/security/third-party/microsoft.rst:46 +msgid "Name:" +msgstr "Name:" -#: ../system/core-workflows/learn-by-example.rst:55 +#: ../settings/security/third-party/microsoft.rst:45 msgid "" -"This reduces the category options to ``Sales/*``, ``Internal/*`` and " -"``Others``." +"Any meaningful name fitting, this name will be displayed to users trying to " +"authenticate with this app." msgstr "" -"Dies reduziert die möglichen Kategorien auf ``Sales/*``, ``Internal/*`` und " -"``Others``." - -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for sales" -msgstr "Beispiel-Workflow, der bestimmte Werte und Felder für Sales zeigt" - -#: ../system/core-workflows/learn-by-example.rst:68 -#: ../system/integrations/slack.rst:88 -msgid "The Result" -msgstr "Das Ergebnis" +"Wählen Sie einen aussagekräftigen Namen. Dieser wird Benutzern angezeigt, " +"die versuchen, sich mit dieser Anwendung zu authentifizieren." -#: ../system/core-workflows/learn-by-example.rst:63 -msgid "" -"This is what the agent would experience with the above workflows in place." +#: ../settings/security/third-party/microsoft.rst:49 +msgid "Choose one of the above mentioned account types (see Limitations)." msgstr "" -"Dies zeigt die Agenten-Sicht bei Anwendung der oben genannten Workflows." +"Wählen Sie einen der oben genannten Kontotypen (siehe Einschränkungen)." -#: ../system/core-workflows/learn-by-example.rst:0 +#: ../settings/security/third-party/microsoft.rst:51 msgid "" -"Workflow shows objects and limits options based on selections on the group" +"The correct account type depends on your use case. If you want to use the " +"authentication internal only, choose the first option. If you're unsure, use " +"the \"Help me choose...\" link." msgstr "" -"Workflow zeigt Objektattribute an und schränkt die Optionen basierend auf " -"der Auswahl in der Gruppe ein" +"Der richtige Kontotyp hängt von Ihrem Anwendungsfall ab. Wenn Sie nur die " +"interne Authentifizierung verwenden möchten, wählen Sie die erste Option. " +"Wenn Sie unsicher sind, verwenden Sie den Link \"Hilfe bei der Auswahl...\"." -#: ../system/core-workflows/learn-by-example.rst:90 -msgid "Approval process" -msgstr "Genehmigungsprozess" +#: ../settings/security/third-party/microsoft.rst:58 +msgid "Redirect URI (optional):" +msgstr "Redirect URI (optional):" -#: ../system/core-workflows/learn-by-example.rst:71 +#: ../settings/security/third-party/microsoft.rst:56 msgid "" -"In this case ``approved`` is visible to agents by default. For this " -"workflow, an additional role ``Approval person`` is required (no further " -"permissions)." +"Select web and provide your callback URL. The callback URL looks like this: " +"``https://zammad.domain.tld/auth/microsoft_office365/callback``" msgstr "" -"In diesem Fall ist ``approved`` standardmäßig für Agenten sichtbar. Für " -"diesen Workflow wird eine zusätzliche Rolle ``Approval person`` benötigt " -"(keine weiteren Berechtigungen)." +"Wählen Sie Web und geben Sie Ihre Callback-URL an. Die Callback-URL sieht " +"wie folgt aus: ``https://zammad.domain.tld/auth/microsoft_office365/" +"callback``" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that restricts an approval attribute to specific roles" -msgstr "" -"Beispiel-Workflow, der den Genehmigungs-Status auf bestimmte Rollen " -"einschränkt" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to register a Microsoft app" +msgstr "Screencast zeigt, wie man eine Microsoft-Anwendung registriert" -#: ../system/core-workflows/learn-by-example.rst:81 -msgid "" -"This workflow may work best in combination with a :doc:`trigger ` but technically, this is not required." +#: ../settings/security/third-party/microsoft.rst:71 +msgid "Within **API permissions** add the following permissions:" msgstr "" -"Dieser Workflow funktioniert am besten in Kombination mit einem :doc:" -"`Trigger `, aber technisch ist das nicht unbedingt " -"erforderlich." +"Fügen Sie unter **API-Berechtigungen** die folgenden Berechtigungen hinzu:" -#: ../system/core-workflows/learn-by-example.rst:84 -msgid "" -"Select fields may be a better approach because they allow more values than " -"just a simple ``true`` or ``false``." -msgstr "" -"Auswahlfelder können besser geeignet sein, da sie mehr Werte zulassen als " -"nur ein einfaches ``true`` oder ``false``." +#: ../settings/security/third-party/microsoft.rst:69 +msgid "``User.Read``" +msgstr "``User.Read``" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "" -"Workflow fixes possible values of \"Approved ?\" to a specific selection " -"depending on the users role" -msgstr "" -"Der Workflow legt die möglichen Werte von \"Approved ?\" auf eine bestimmte " -"Auswahl fest, die von der Rolle des Benutzers abhängt" +#: ../settings/security/third-party/microsoft.rst:71 +msgid "Contacts" +msgstr "Contacts" -#: ../system/core-workflows/learn-by-example.rst:103 -msgid "State dependent mandatory fields" -msgstr "Vom Status abhängige Pflichtfelder" +#: ../settings/security/third-party/microsoft.rst:71 +msgid "``Contacts.Read``" +msgstr "``Contacts.Read``" -#: ../system/core-workflows/learn-by-example.rst:93 +#: ../settings/security/third-party/microsoft.rst:73 msgid "" -"This workflow sets ``Category`` to mandatory if the agent wants to set the " -"states ``closed`` or ``pending close`` to enforce categorization." +"You can find these permissions within *Microsoft Graph → Delegated " +"permissions*." msgstr "" -"Dieser Workflow legt ``Category`` als Pflichtfeld fest, wenn der Agent die " -"Tickets auf ``geschlossen`` oder ``Warten auf Schließen`` setzen will, um " -"die Kategorisierung zu erzwingen." +"Sie finden diese Berechtigungen unter *Microsoft Graph → Delegated " +"permissions*." -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that sets fields to mandatory on specific states" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to add required API permissions" msgstr "" -"Beispiel-Workflow, der Felder abhängig vom Ticketstatus als Pflichtfeld " -"definiert" +"Screencast zeigt, wie man die erforderlichen API-Berechtigungen hinzufügt" -#: ../system/core-workflows/learn-by-example.rst:0 +#: ../settings/security/third-party/microsoft.rst:80 msgid "" -"Workflow sets category field to mandatory upon choosing closed or pending " -"close as state" +"Within **Certificates & secrets** create a new client secret. Note down the " +"returned secret **value** for later. **Do not** use the secret ID!" msgstr "" -"Der Workflow definiert das Kategorie-Feld als Pflichtfeld, wenn als Status " -"\"geschlossen\" oder \"warten auf Schließen\" gewählt wird" - -#: ../system/core-workflows/learn-by-example.rst:106 -msgid "Manual Ticket Handover Process" -msgstr "Prozess manuelle Ticketübergabe" +"Erstellen Sie unter **Zertifikate & Secrets** ein neues Client-Secret. " +"Notieren Sie sich den zurückgegebenen **Wert** des Geheimnisses für später. " +"**Verwenden Sie nicht** die geheime ID!" -#: ../system/core-workflows/learn-by-example.rst:108 -msgid "This example covers the handover of a ticket from one agent to another:" -msgstr "" -"In diesem Beispiel geht es um die Übergabe eines Tickets von einem Agenten " -"an einen anderen:" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to create a new app secret" +msgstr "Screencast zeigt, wie man ein neues Anwendungs-Secret erstellt" -#: ../system/core-workflows/learn-by-example.rst:110 +#: ../settings/security/third-party/microsoft.rst:88 msgid "" -"When the ticket owner is modified, a new text field (\"Handover\") shows up " -"for a comment" +"From **Overview** copy your apps *Application (client) ID*. If you're using " +"a single tenant app, please also copy *Directory (tenant) ID*. You now have " +"all required information for Zammad." msgstr "" -"Wenn der Besitzer des Tickets geändert wird, wird ein neues Textfeld " -"(\"Handover\") für einen Kommentar eingeblendet" +"Kopieren Sie aus **Übersicht** die *Anwendungs-(Client-)ID* Ihrer Anwendung. " +"Wenn Sie ein Single-Tenant-App verwenden, kopieren Sie bitte auch " +"*Verzeichnis (Tenant) ID*. Sie haben nun alle erforderlichen Informationen " +"für Zammad." -#: ../system/core-workflows/learn-by-example.rst:112 -msgid "" -"This may only be visible when the owner is changed, therefore it has to be " -"hidden in general" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to retreive application client and tenant IDs" msgstr "" -"Dies darf nur sichtbar sein, wenn der Besitzer gewechselt wird, daher muss " -"es grundsätzlich ausgeblendet werden" +"Screencast zeigt, wie man die IDs von Client Anwendungen und Tenants abruft" -#: ../system/core-workflows/learn-by-example.rst:114 -msgid "The input in this handover text field is mandatory" -msgstr "Die Eingabe in dieses Handover-Textfeld ist verpflichtend" +#: ../settings/security/third-party/microsoft.rst:98 +msgid "Step 2 - Add App Credentials to Zammad" +msgstr "Schritt 2 - Hinzufügen der Anmeldedaten in Zammad" -#: ../system/core-workflows/learn-by-example.rst:115 +#: ../settings/security/third-party/microsoft.rst:100 msgid "" -"After submitting changes, the value of the handover field must be added as " -"an note to the ticket (via trigger)" +"Navigate to Security > Third-party Applications (Tab) within Zammad's admin " +"settings. Scroll down to the section *Authentication via Microsoft* and fill " +"in the required information." msgstr "" -"Nach dem Speichern muss der Wert des Handover-Felds als Notiz zum Ticket " -"hinzugefügt werden (mittels Trigger)" +"Navigieren Sie zu Sicherheit > Anwendungen von Drittanbietern " +"(Registerkarte) in den Verwaltungseinstellungen von Zammad. Scrollen Sie " +"nach unten zum Abschnitt *Anmelden über Microsoft* und geben Sie die " +"erforderlichen Informationen ein." -#: ../system/core-workflows/learn-by-example.rst:121 -msgid "Hiding handover field" -msgstr "Ausblenden des Handover-Feldes" +#: ../settings/security/third-party/microsoft.rst:105 +msgid "App ID:" +msgstr "App ID:" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Hiding the handover field in core workflows" -msgstr "Ausblenden des Handover-Felds in Core Workflows" +#: ../settings/security/third-party/microsoft.rst:105 +msgid "This is your *Application (client) ID*." +msgstr "Dies ist Ihre *Anwendungs-(Client-)ID*." -#: ../system/core-workflows/learn-by-example.rst:126 -msgid "Showing handover field and setting it to mandatory" -msgstr "Handover-Feld einblenden und als Pflichtfeld setzen" +#: ../settings/security/third-party/microsoft.rst:108 +msgid "App secret:" +msgstr "App-Secret:" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Showing the handover field and set it as mandatory" -msgstr "Das Handover-Feld anzeigen und als Pflichtfeld festlegen" +#: ../settings/security/third-party/microsoft.rst:108 +msgid "This is your *client secret* (value)." +msgstr "Dies ist Ihr *Client Secret* (Wert)." -#: ../system/core-workflows/learn-by-example.rst:131 -msgid "Trigger writing handover input to a new article" +#: ../settings/security/third-party/microsoft.rst:113 +msgid "App Tenant ID:" +msgstr "App Tenant ID:" + +#: ../settings/security/third-party/microsoft.rst:111 +msgid "" +"**optional** only required for apps that use account type *Accounts in this " +"organizational directory only (Default Directory only - Single tenant).*" msgstr "" -"Trigger für die Erstellung eines neuen Artikels auf Basis des Handover-" -"Inhalts" +"**optional** nur erforderlich für Anwendungen, die den Kontotyp *Accounts in " +"this organizational directory only (Default Directory only - Single tenant).*" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Write handover content to a new article" -msgstr "Handover-Inhalt in einen neuen Artikel schreiben" +#: ../settings/security/third-party/microsoft.rst:115 +msgid "" +"Apply your settings by pressing submit and activate *Authentication via " +"Microsoft*." +msgstr "" +"Übernehmen Sie Ihre Einstellungen, indem Sie auf Senden klicken und " +"*Authentifizierung über Microsoft* aktivieren." -#: ../system/core-workflows/learn-by-example.rst:133 +#: ../settings/security/third-party/microsoft.rst:None msgid "" -"As a result, the ticket includes an article of the type note which includes " -"the predefined text and the handover comment." +"Screencast showing how to add app credentials and activating the\n" +"authentication method" msgstr "" -"Als Ergebnis enthält das Ticket einen Artikel vom Typ Notiz, der den " -"vordefinierten Text und den Inhalt des Handover-Felds enthält." +"Screencast zum Hinzufügen von Anmeldeinformationen für die Anwendung und zum " +"Aktivieren der\n" +"Authentifizierungsmethode" -#: ../system/core-workflows/limitations.rst:6 -msgid "Core Workflows do not replace Triggers" -msgstr "Core Workflows ersetzen nicht Trigger" +#: ../settings/security/third-party/saml.rst:2 +msgid "SAML" +msgstr "SAML" -#: ../system/core-workflows/limitations.rst:5 +#: ../settings/security/third-party/saml.rst:4 msgid "" -"Workflows manipulate the behavior of fields. However, they do not set values " -"in fields because of actions." +"Connect your SAML (Security Assertion Markup Language) identity provider as " +"a single sign-on (SSO) method." msgstr "" -"Workflows verändern Felder und deren Verhalten. Sie setzen jedoch keine " -"Werte in Felder aufgrund von Aktionen." +"Verbinden Sie Ihren SAML (Security Assertion Markup Language) " +"Identitätsanbieter als Single-Sign-On-Methode (SSO)." -#: ../system/core-workflows/limitations.rst:16 -msgid "API calls are only partly affected" -msgstr "API-Calls sind nur teilweise betroffen" +#: ../settings/security/third-party/saml.rst:7 +msgid "" +"SAML is an open standard for SSO authentication (among other things). Sign-" +"ins are shared across multiple **service providers** and managed by a " +"central **identity provider** (IdP)." +msgstr "" +"SAML ist (u.a.) ein offener Standard für die SSO-Authentifizierung. " +"Anmeldungen werden von mehreren **Dienstanbietern** gemeinsam genutzt und " +"von einem zentralen **Identitätsanbieter** (IdP) verwaltet." -#: ../system/core-workflows/limitations.rst:9 +#: ../settings/security/third-party/saml.rst:11 msgid "" -"Some options affect UI only and thus do not restrict responses and calls." +"In this case, the service provider is Zammad, and the IdP is a software " +"service that you either host or subscribe to (*e.g.,* `Keycloak `_, `Redhat SSO Server `_, `ADFS `_, or `Okta `_)." msgstr "" -"Einige Optionen wirken sich nur auf die Benutzeroberfläche aus und schränken " -"daher API requests und responses nicht ein." +"In diesem Fall ist der Dienstanbieter Zammad, und der IdP ist ein " +"Softwaredienst, den Sie entweder selbst hosten oder abonnieren (*z.B.* " +"`Keycloak `_, `Redhat SSO Server `_, `ADFS `_, " +"oder `Okta `_)." -#: ../system/core-workflows/limitations.rst:11 -msgid "This affects the following actions:" -msgstr "Das betrifft die folgenden Aktionen:" - -#: ../system/core-workflows/limitations.rst:13 -msgid "select" -msgstr "auswählen" - -#: ../system/core-workflows/limitations.rst:14 -msgid "auto select" -msgstr "automatisch auswählen" +#: ../settings/security/third-party/saml.rst:18 +msgid "" +"This guide assumes you are already using SAML within your organization (i." +"e., that your IdP is fully set up)." +msgstr "" +"Die Anleitung geht davon aus, dass Sie SAML bereits in Ihrer Organisation " +"verwenden (d.h. dass Ihr IdP vollständig eingerichtet ist)." -#: ../system/core-workflows/limitations.rst:15 -msgid "show" -msgstr "anzeigen" +#: ../settings/security/third-party/saml.rst:21 +msgid "" +"Please note: Our instructions are based on connecting Zammad with Keycloak." +msgstr "" +"Bitte beachten Sie: Unsere Anleitung basiert auf der Anbindung von Keycloak." -#: ../system/core-workflows/limitations.rst:16 -msgid "hide" -msgstr "verstecken" +#: ../settings/security/third-party/saml.rst:25 +msgid "Step 1: Configure Your IdP" +msgstr "Schritt 1: Konfigurieren Sie Ihren IdP" -#: ../system/core-workflows/limitations.rst:25 -msgid "Some fields stay unavailable to customers" -msgstr "Einige Felder bleiben für Kunden unzugänglich" +#: ../settings/security/third-party/saml.rst:28 +msgid "Add Zammad as a Client/App" +msgstr "Zammad als Client/Anwendung hinzufügen" -#: ../system/core-workflows/limitations.rst:19 +#: ../settings/security/third-party/saml.rst:30 msgid "" -"For technical and security reasons, some default fields (the pale ones you " -"can't edit) stay unavailable for display and usage on customer permissions." +"Import Zammad into your IdP using the XML configuration found at ``https://" +"your.zammad.domain/auth/saml/metadata``." msgstr "" -"Aus technischen und sicherheitstechnischen Gründen sind einige " -"Standardfelder (die grauen Felder, die Sie nicht bearbeiten können) für " -"Benutzer mit Kunden-Berechtigung nicht verfügbar." +"Importieren Sie Zammad in Ihren IdP unter Verwendung der XML-Konfiguration, " +"die Sie unter ``https://your.zammad.domain/auth/saml/metadata`` finden." -#: ../system/core-workflows/limitations.rst:23 +#: ../settings/security/third-party/saml.rst:33 msgid "" -"If you require your customers to change e.g. priorities, please consider " -"using workarounds via :doc:`/system/objects` and :doc:`/manage/trigger`." +"If your IdP doesn't support XML import, you will have to configure Zammad as " +"a new client/app manually using the above XML metadata file for reference." msgstr "" -"Wenn Sie möchten dass Ihre Kunden z.B. Prioritäten ändern können, ziehen Sie " -"bitte Workarounds über :doc:`/system/objects` und :doc:`/manage/trigger` in " -"Betracht." +"Wenn Ihr IdP den XML-Import nicht unterstützt, müssen Sie Zammad manuell als " +"neuen Client/App konfigurieren und dabei die oben genannte XML-Metadaten-" +"Datei als Referenz verwenden." -#: ../system/core-workflows/limitations.rst:29 -msgid "Ticket title changes not supported in edit mask" -msgstr "" -"Änderungen des Ticket-Titels werden in der Bearbeitungsmaske nicht " -"unterstützt" +#: ../settings/security/third-party/saml.rst:36 +msgid "For instance, when you see this tag:" +msgstr "Wenn Sie zum Beispiel diesen Tag sehen:" -#: ../system/core-workflows/limitations.rst:28 +#: ../settings/security/third-party/saml.rst:42 msgid "" -"It is currently not possible to perform changes of the ticket title in the " -"edit mask (e.g. renaming, set to read-only)." +"Set the **Assertion Consumer Service Binding URL** (sometimes also listed as " +"**Valid Redirect URIs**) to ``http://your.zammad.domain/auth/saml/callback``." msgstr "" -"Es ist derzeit nicht möglich, in der Bearbeitungsmaske Änderungen am Titel " -"des Tickets vorzunehmen (z.B. umbenennen, auf schreibgeschützt setzen)." +"Setzen Sie die **Assertion Consumer Service Binding URL** (manchmal auch als " +"**Valid Redirect URIs** bezeichnet) auf ``http://your.zammad.domain/auth/" +"saml/callback``." -#: ../system/core-workflows/limitations.rst:37 -msgid "What is out of scope of Core Workflows?" -msgstr "Was fällt nicht in den Anwendungsbereich der Core-Workflows?" +#: ../settings/security/third-party/saml.rst:47 +msgid "Set Up User Attribute Mapping" +msgstr "Benutzerattribut-Zuordnung einrichten" -#: ../system/core-workflows/limitations.rst:32 +#: ../settings/security/third-party/saml.rst:49 msgid "" -"There are some things that would count as workflow but are either done via :" -"doc:`/manage/trigger` or :doc:`/manage/scheduler`." +"Zammad requests the following user attributes (or “properties”) from the IdP:" msgstr "" -"Es gibt einige Dinge, die als Workflow gelten würden, aber entweder über :" -"doc:`/manage/trigger` oder :doc:`/manage/scheduler` erledigt werden." +"Zammad fordert die folgenden Benutzerattribute (oder \"Eigenschaften\") vom " +"IdP an:" -#: ../system/core-workflows/limitations.rst:35 -msgid "Such as (but not limited to):" -msgstr "Zum Beispiel (nicht abschließend):" +#: ../settings/security/third-party/saml.rst:51 +msgid "Email address (``email``)" +msgstr "E-Mail Adresse (``email``)" -#: ../system/core-workflows/limitations.rst:37 -msgid "up- or downgrade permissions of users" -msgstr "Berechtigungen von Benutzern herauf- oder herabstufen" +#: ../settings/security/third-party/saml.rst:52 +msgid "Full name (``name``)" +msgstr "Vollständiger Name (``name``)" -#: ../system/core-workflows/limitations.rst:38 -msgid "affecting article creation or listing" -msgstr "" -"Änderungen mit Auswirkung auf die Erstellung oder Auflistung von Artikeln" +#: ../settings/security/third-party/saml.rst:53 +msgid "Given name (``first_name``)" +msgstr "Vorname (``first_name``)" -#: ../system/data-privacy.rst:2 -msgid "Data Privacy" -msgstr "Datenschutz" +#: ../settings/security/third-party/saml.rst:54 +msgid "Family name (``last_name``)" +msgstr "Nachname (``last_name``)" -#: ../system/data-privacy.rst:4 +#: ../settings/security/third-party/saml.rst:56 msgid "" -"For compliance with GDPR and other data privacy laws, you may wish to " -"**permanently delete users from the system**, along with **all of their " -"associated tickets**." +"You may need to set up “mappers” (or “mappings”) to tell your IdP how user " +"attributes in SAML correspond to those in Zammad. For a more detailed " +"breakdown, refer to the XML metadata file referenced in the previous section." msgstr "" -"Um die DSGVO und andere Datenschutzgesetze einzuhalten ist es ggf. " -"erforderlich, **Benutzer inkl. aller zugehöriger Tickets dauerhaft aus dem " -"System löschen**." +"Möglicherweise müssen Sie \"Mapper\" (oder \"Mappings\") einrichten, um " +"Ihrem IdP mitzuteilen, welche Benutzerattribute in SAML mit welchen in " +"Zammad übereinstimmen. Eine detailliertere Aufschlüsselung finden Sie in der " +"XML-Metadaten-Datei, auf die im vorherigen Abschnitt verwiesen wurde." -#: ../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 `!" -msgstr "" -"Sie können manuelle Löschaufgaben oder sogar automatisierte Löschaufgaben " -"für Tickets und Benutzer, basierend auf benutzerdefinierten Bedingungen, " -"über :doc:`scheduler ` erstellen!" +#: ../settings/security/third-party/saml.rst:62 +msgid "Per-IdP Instructions" +msgstr "Informationen für verschiedene IdP" -#: ../system/data-privacy.rst:12 -msgid "" -"Access to this panel requires ``admin.data_privacy`` permissions (introduced " -"in Zammad 3.5)." -msgstr "" -"Der Zugriff auf diesen Bereich erfordert die Berechtigung ``admin." -"data_privacy`` (eingeführt in Zammad 3.5)." +#: ../settings/security/third-party/saml.rst:102 +msgid "Keycloak" +msgstr "Keycloak" -#: ../system/data-privacy.rst:15 +#: ../settings/security/third-party/saml.rst:65 msgid "" -"On older systems that have not been updated yet, customers can also be :docs:" -"`deleted via the Zammad console `." +"**To add Zammad as a client,** save the XML configuration to disk (``https://" +"your.zammad.domain/auth/saml/metadata``) and use **Clients > Clients list > " +"Import client** in the Keycloak admin panel." msgstr "" -"Auf älteren Systemen, die noch nicht aktualisiert wurden, können Kunden auch " -"über die :docs:`Zammad-Konsole gelöscht werden `." - -#: ../system/data-privacy.rst:22 -msgid "User deletion dialog in the Data Privacy panel" -msgstr "Benutzer-Löschdialog im Datenschutz-Panel" +"**Um Zammad als Client hinzuzufügen,** speichern Sie die XML-Konfiguration " +"auf Ihrem Rechner (``https://your.zammad.domain/auth/saml/metadata``) und " +"verwenden Sie **Clients > Clients list > Import client** im Keycloak Admin " +"Panel." -#: ../system/data-privacy.rst:22 +#: ../settings/security/third-party/saml.rst:70 msgid "" -"The user deletion dialog lists some of the tickets that will be removed from " -"the system along with the user." +"To help Zammad **match its own user accounts to Keycloak users**, create a " +"user attribute (or “property”) mapper. In **Clients list**, click on your " +"newly created Client ID, choose the tab **Client scopes** and click on the " +"link which refers to your Zammad instance. Choose **Add mapper > By " +"configuration > User Property** and create a mapper with the following " +"entries:" msgstr "" -"Im Dialogfeld zum Löschen von Benutzern werden einige der Tickets " -"aufgelistet, die zusammen mit dem Benutzer aus dem System entfernt werden." +"Um Zammad bei der **Zuordnung der Benutzerkonten zu Keycloak-Benutzern** zu " +"helfen, erstellen Sie einen Benutzerattribut- (oder \"Eigenschafts-\")-" +"Mapper. Klicken Sie in der **Clientl list** auf Ihre neu erstellte Client-" +"ID, wählen Sie den Reiter **Client scopes** und klicken Sie auf den Link, " +"der auf Ihre Zammad-Instanz verweist. Wählen Sie **Add mapper > By " +"configuration > User Property** und erstellen Sie einen Mapper mit den " +"folgenden Einträgen:" -#: ../system/data-privacy.rst:27 -msgid "Deleting Users via GUI" -msgstr "Löschen von Benutzern per GUI" +#: ../settings/security/third-party/saml.rst:78 +msgid "**Name**" +msgstr "**Name**" -#: ../system/data-privacy.rst:29 -msgid "🔥 **All deletions are FINAL!**" -msgstr "🔥 **Jede Löschung ist ENDGÜLTIG!**" +#: ../settings/security/third-party/saml.rst:80 +msgid "**Mapper Type**" +msgstr "**Mapper-Typ**" -#: ../system/data-privacy.rst:31 -msgid "Once you click “Delete”, the action cannot be canceled or undone." -msgstr "" -"Sobald Sie auf \"Löschen\" klicken, kann die Aktion nicht mehr abgebrochen " -"oder rückgängig gemacht werden." +#: ../settings/security/third-party/saml.rst:81 +msgid "``User Property``" +msgstr "``User Property``" -#: ../system/data-privacy.rst:33 -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." -msgstr "" -"Jedes Mal, wenn Sie einen Benutzer löschen, werden auch alle seine Tickets " -"gelöscht. Es ist nicht möglich, einen Benutzer zu löschen und seine Tickets " -"zu behalten." +#: ../settings/security/third-party/saml.rst:82 +msgid "**Property**" +msgstr "**Property**" -#: ../system/data-privacy.rst:36 -msgid "**The following records cannot be deleted:**" -msgstr "**Die folgenden Datensätze können nicht gelöscht werden:**" +#: ../settings/security/third-party/saml.rst:83 +msgid "``emailAddress``" +msgstr "``emailAddress``" -#: ../system/data-privacy.rst:38 -msgid "your own account" -msgstr "Ihr eigenes Konto" +#: ../settings/security/third-party/saml.rst:84 +msgid "**SAML Attribute Name**" +msgstr "**SAML Attribute Name**" -#: ../system/data-privacy.rst:39 -msgid "the system's last remaining administrator account" -msgstr "das letzte verbleibende Administratorkonto des Systems" +#: ../settings/security/third-party/saml.rst:86 +msgid "**SAML Attribute NameFormat**" +msgstr "**SAML Attribute NameFormat**" -#: ../system/data-privacy.rst:42 -msgid "Step 1: Find a User / Confirm Deletion" -msgstr "Schritt 1: Benutzer suchen / Löschung bestätigen" +#: ../settings/security/third-party/saml.rst:87 +msgid "``basic``" +msgstr "``basic``" -#: ../system/data-privacy.rst:44 -msgid "There are three ways to access the user deletion dialog:" +#: ../settings/security/third-party/saml.rst:89 +msgid "" +"In the example above, we're telling Zammad that whenever it receives a SAML " +"login request, it should take the ``email`` property from Keycloak, look for " +"a Zammad user with the same ``email`` attribute, and create a new session " +"for that user." msgstr "" -"Es gibt drei Möglichkeiten, den Dialog zum Löschen von Benutzern aufzurufen:" +"Im obigen Beispiel weisen wir Zammad an, dass es bei jeder SAML-" +"Anmeldeanfrage die Eigenschaft ``email`` von Keycloak nehmen, nach einem " +"Zammad-Benutzer mit demselben ``email``-Attribut suchen und eine neue " +"Sitzung für diesen Benutzer erstellen soll." -#: ../system/data-privacy.rst:51 -msgid "**from the user's profile**" -msgstr "**aus dem Profil des Nutzers**" +#: ../settings/security/third-party/saml.rst:95 +msgid "" +"If your Keycloak users' email addresses are stored on another property (*e." +"g.,* ``username``), adjust accordingly." +msgstr "" +"Wenn die E-Mail-Adressen Ihrer Keycloak-Benutzer in einer anderen " +"Eigenschaft gespeichert sind (*z.B.* ``username``), passen Sie sie " +"entsprechend an." -#: ../system/data-privacy.rst:0 -msgid "Accessing the user deletion dialog in a user profile" -msgstr "Dialog zum Löschen von Benutzern in einem Benutzerprofil" +#: ../settings/security/third-party/saml.rst:98 +msgid "" +"Back in **Settings**, enter the Client ID (``https://your.zammad.domain/auth/" +"saml/metadata``) in the field **Master SAML Processing URL**." +msgstr "" +"Geben Sie in den **Einstellungen** die Client-ID (``https://your.zammad." +"domain/auth/saml/metadata``) in das Feld **Master SAML Processing URL** ein." -#: ../system/data-privacy.rst:51 -msgid "Click **Action > Delete**." -msgstr "Klicken Sie auf **Aktion > Löschen**." +#: ../settings/security/third-party/saml.rst:101 +msgid "You also need to enable **Sign assertions**." +msgstr "Sie müssen auch **Sign Assertions** aktivieren." -#: ../system/data-privacy.rst:58 -msgid "**in the “Manage > Users” Admin Panel**" -msgstr "**in den Einstellungen unter \"Verwalten > Benutzer\"**" +#: ../settings/security/third-party/saml.rst:105 +msgid "Step 2: Configure Zammad" +msgstr "Schritt 2: Zammad konfigurieren" -#: ../system/data-privacy.rst:0 -msgid "Accessing the user deletion dialog under “Users” in the Admin Panel" -msgstr "Dialog zum Löschen von Benutzern im Admin Panel" +#: ../settings/security/third-party/saml.rst:107 +msgid "" +"Enable SAML and enter your IdP's details in the Admin Panel under **Settings " +"> Security > Third Party Applications > Authentication via SAML**:" +msgstr "" +"Aktivieren Sie SAML und geben Sie die Details Ihres IdP im Admin Bereich " +"unter **Einstellungen > Sicherheit > Anwendungen von Drittanbietern > " +"Anmeldung über SAML** ein:" -#: ../system/data-privacy.rst:58 -msgid "Use the **⋮ Actions** menu for the target user." -msgstr "Verwenden Sie das Menü **⋮ Aktionen** für den entsprechenden Benutzer." +#: ../settings/security/third-party/saml.rst:None +msgid "Example configuration of SAML part 1" +msgstr "Beispielkonfiguration von SAML Teil 1" -#: ../system/data-privacy.rst:66 ../system/data-privacy.rst:104 -msgid "**in the “System > Data Privacy” Admin Panel**" -msgstr "**in den Einstellungen unter \"System > Datenschutz\"**" +#: ../settings/security/third-party/saml.rst:119 +msgid "Display name" +msgstr "Anzeigename" -#: ../system/data-privacy.rst:0 +#: ../settings/security/third-party/saml.rst:116 msgid "" -"Accessing the user deletion dialog under “Data Privacy” in the Admin Panel" -msgstr "Dialog zum Löschen von Benutzern unter \"Datenschutz\" im Admin Panel" +"Allows you to define a custom button name for SAML. This helps your users to " +"understand better what the button on the login page does." +msgstr "" +"Ermöglicht es Ihnen, einen eigenen Namen für den SAML-Button zu definieren. " +"Das kann hilfreich sein, damit Ihre Benutzer verstehen, was die Schaltfläche " +"auf der Anmeldeseite genau bewirkt." -#: ../system/data-privacy.rst:65 +#: ../settings/security/third-party/saml.rst:119 +msgid "Defaults to ``SAML``." +msgstr "Die Voreinstellung ist ``SAML``." + +#: ../settings/security/third-party/saml.rst:123 +msgid "IDP SSO target URL" +msgstr "IDP SSO Ziel-URL" + +#: ../settings/security/third-party/saml.rst:122 msgid "" -"Use the **New Deletion Task** button. Search for users by name or email " -"address." +"This is the target URL Zammad shall redirect to when the user presses the " +"SAML button. For Keycloak, this needs to look like https://your.domain/" +"realms/your-realm/protocol/saml" msgstr "" -"Verwenden Sie die Schaltfläche **Neue Löschaufgabe**. Suchen Sie nach " -"Benutzern anhand von Namen oder E-Mail-Adressen." +"Dies ist die Ziel-URL, zu der Zammad umleiten soll, wenn der Benutzer die " +"SAML-Schaltfläche anklickt. Für Keycloak muss dies wie folgt aussehen: " +"https://your.domain/realms/your-realm/protocol/saml." -#: ../system/data-privacy.rst:79 -msgid "**Delete organizations**" -msgstr "**Organisationen löschen**" +#: ../settings/security/third-party/saml.rst:127 +msgid "IDP single logout target URL" +msgstr "IDP Ziel-URL für Einzel-Abmeldung" -#: ../system/data-privacy.rst:69 +#: ../settings/security/third-party/saml.rst:126 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:" +"This is the URL to which the single logout request and response should be " +"sent." msgstr "" -"Wenn der zu löschende Kunde der letzte Benutzer in seiner Organisation ist, " -"wird im Dialogfeld zum Löschen von Benutzern die Option **Organisation " -"löschen?** angezeigt:" +"Dies ist die URL, an die die einzelne Abmeldeanforderung gesendet werden " +"soll." -#: ../system/data-privacy.rst:0 -msgid "Deleting an organization via the user deletion dialog" -msgstr "Löschung einer Organisation über den Benutzer löschen Dialog" +#: ../settings/security/third-party/saml.rst:131 +msgid "IDP certificate" +msgstr "IDP-Zertifikat" -#: ../system/data-privacy.rst:78 +#: ../settings/security/third-party/saml.rst:130 msgid "" -"If this option does not appear, make sure there are no pending deletion " -"tasks for other customers from this organization." +"The public certificate of your IDP for Zammad to verify during the callback " +"phase." msgstr "" -"Wenn diese Option nicht angezeigt wird, stellen Sie sicher, dass es keine " -"ausstehenden Löschaufgaben für andere Kunden aus dieser Organisation gibt." +"Das öffentliche Zertifikat Ihres IDP, das Zammad während des \"Callbacks\" " +"überprüfen soll." -#: ../system/data-privacy.rst:82 -msgid "Step 2: Monitor Deletion Job Status" -msgstr "Schritt 2: Status des Löschauftrags prüfen" +#: ../settings/security/third-party/saml.rst:145 +msgid "IDP certificate fingerprint" +msgstr "Fingerabdruck IDP-Zertifikat" -#: ../system/data-privacy.rst:84 +#: ../settings/security/third-party/saml.rst:134 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:" +"The fingerprint of your IDPs public certificate to verify during callback " +"phase." msgstr "" -"Es kann bis zu zehn Minuten dauern, bis das System Ihre Anfrage bearbeitet. " -"Für jeden Benutzer, den Sie löschen, wird eine \"Löschaufgabe\" in die " -"Warteschlange aufgenommen. Sie können den Status dieser Aufgaben an zwei " -"Stellen im Auge behalten:" - -#: ../system/data-privacy.rst:98 -msgid "**in the Activity Stream**" -msgstr "**im Aktivitäts-Verlauf**" +"Der Fingerabdruck Ihres öffentlichen IDP-Zertifikats, der während des " +"\"Callbacks\" geprüft wird." -#: ../system/data-privacy.rst:0 -msgid "Activity Stream showing data privacy tasks" -msgstr "Aktivitäts-Verlauf mit Datenschutzaufgaben" +#: ../settings/security/third-party/saml.rst:137 +msgid "🔏 **For the IdP certificate / certificate fingerprint:**" +msgstr "🔏 **Für das IdP-Zertifikat / den Zertifikatsfingerabdruck:**" -#: ../system/data-privacy.rst:94 +#: ../settings/security/third-party/saml.rst:139 msgid "" -"For each deleted user, the Activity Stream will be updated twice—once when " -"the task is created, and once when it's complete." +"Provide **only one or the other**—do not provide both! (Between the two, we " +"recommend the signing certificate itself: fingerprints use SHA-1, which `has " +"been broken for a while now `_.)" msgstr "" -"Für jeden gelöschten Benutzer wird der Aktivitäts-Verlauf zweimal " -"aktualisiert - einmal bei der Erstellung der Aufgabe und einmal bei ihrer " -"Erledigung." +"Verwenden Sie **nur eine der Varianten**. Wir empfehlen die Verwendung des " +"Zertifikats selbst: Fingerabdrücke verwenden SHA-1, das `seit einiger Zeit " +"als unsicher gilt `_)." -#: ../system/data-privacy.rst:97 +#: ../settings/security/third-party/saml.rst:144 msgid "" -"These notifications are only visible to users with ``admin.data_privacy`` " -"permissions." +"**Keycloak users:** Find your certificate in the Keycloak admin panel under " +"**Realm Settings > Keys > Algorithm: RS256 > Certificate**." msgstr "" -"Diese Benachrichtigungen sind nur für Benutzer mit der Berechtigung ``admin." -"data_privacy`` sichtbar." +"**Keycloak-Anwender:** Sie finden Ihr Zertifikat im Keycloak-" +"Administrationsbereich unter **Realm Settings > Keys > Algorithm: RS256 > " +"Certificate**." -#: ../system/data-privacy.rst:0 +#: ../settings/security/third-party/saml.rst:151 +msgid "Name identifier format" +msgstr "Name Identifier Format" + +#: ../settings/security/third-party/saml.rst:148 msgid "" -"The task list within Data Privacy shows removals being in progress and " -"completed." +"This is the unique identifiers field type. Usually it should be ``urn:oasis:" +"names:tc:SAML:1.1:nameid-format:emailAddress``." msgstr "" -"Die Aufgabenliste im Bereich Datenschutz zeigt die laufenden und " -"abgeschlossenen Löschungen." +"Dies ist der Feldtyp für unique identifiers (eindeutige Kennung). " +"Normalerweise ist es ``urn:oasis:names:tc:SAML:1.1:nameid-format:" +"emailAddress``." -#: ../system/data-privacy.rst:107 -msgid "Frequently Asked Questions" -msgstr "Regelmäßige gestellte Fragen" +#: ../settings/security/third-party/saml.rst:151 +msgid "Zammad **expects an email address as unique identifier**!" +msgstr "Zammad **erwartet eine E-Mail-Adresse als eindeutigen Identifikator**!" -#: ../system/data-privacy.rst:121 -msgid "What happens if I receive an email from a deleted customer?" -msgstr "" -"Was passiert, wenn ich eine E-Mail von einem gelöschten Kunden erhalte?" +#: ../settings/security/third-party/saml.rst:155 +msgid "UID attribute name" +msgstr "Name des UID-Attributs" -#: ../system/data-privacy.rst:110 +#: ../settings/security/third-party/saml.rst:154 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." +"Here you can define an attribute that uniquely identifies the user. If " +"unset, the name identifier returned by the IDP is used." msgstr "" -"Zammad erstellt automatisch einen neuen Benutzer-Account wann immer es eine " -"Nachricht von unbekannten E-Mail-Adressen erhält - das betrifft auch " -"gelöschte Benutzer. Gelöschte Nutzer werden niemals vom Erstellen neuer " -"Tickets abgehalten." +"Hier können Sie ein Attribut zur eindeutigen Identifizierung des Benutzers " +"festlegen. Wenn es nicht gesetzt ist, wird der von der IDP zurückgegebene " +"Namensbezeichner verwendet." -#: ../system/data-privacy.rst:115 +#: ../settings/security/third-party/saml.rst:None +msgid "Example configuration of SAML part 2" +msgstr "Beispielkonfiguration von SAML Teil 2" + +#: ../settings/security/third-party/saml.rst:163 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**." +"Decide if the certificate for the connection to the IdP service has to be " +"verified or not (default: ``yes``)." msgstr "" -"Sollte der unwahrscheinliche Fall eintreten, dass Sie eine E-Mail erhalten, " -"nachdem Sie auf \"Löschen\" geklickt haben und das System Ihren Auftrag " -"bearbeitet hat, wird **das Ticket automatisch entfernt**. Die Ticketnummer " -"für das gelöschte Ticket wird in den Einstellungen unter **System > " -"Datenschutz > Erledigte Vorgänge > Benutzer löschen > Gelöschte Tickets** " -"angezeigt." +"Entscheiden Sie, ob das Zertifikat für die Verbindung zum IdP-Dienst " +"verifiziert werden muss oder nicht (Standard: ``Ja``)." -#: ../system/data-privacy.rst:130 -msgid "What about user information stored in internal notes or other messages?" -msgstr "" -"Was ist mit Benutzerinformationen, die in internen Notizen oder anderen " -"Nachrichten gespeichert sind?" +#: ../settings/security/third-party/saml.rst:169 +msgid "Signing & Encrypting" +msgstr "Signieren & Verschlüsseln" -#: ../system/data-privacy.rst:124 +#: ../settings/security/third-party/saml.rst:169 msgid "" -"The deletion process removes **user accounts and associated tickets only**." +"Define if you want to sign, encrypt, do both or nothing for the requests." msgstr "" -"Beim Löschvorgang werden nur **Benutzerkonten und zugehörige Tickets** " -"entfernt." +"Legen Sie fest, ob Sie die Anfragen signieren, verschlüsseln, beides oder " +"nichts tun wollen." -#: ../system/data-privacy.rst:126 +#: ../settings/security/third-party/saml.rst:179 +msgid "Certificate (PEM)" +msgstr "Zertifikat (PEM)" + +#: ../settings/security/third-party/saml.rst:172 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." +"Paste the public certificate of your Zammad SAML client, if you want to " +"encrypt the requests." msgstr "" -"Wenn es Verweise auf den Namen eines Benutzers oder Informationen gibt, die " -"an anderer Stelle im System gespeichert sind, werden diese Informationen " -"**nicht entfernt**. Grund dafür ist, dass es keine sinnvolle Möglichkeit " -"gibt, diese Informationen zuverlässig zu ermitteln." +"Fügen Sie das öffentliche Zertifikat Ihres Zammad SAML-Clients ein, wenn Sie " +"die Anfragen verschlüsseln möchten." -#: ../system/data-privacy.rst:137 -msgid "I deleted an user and can still see a message they sent!" -msgstr "" -"Ich habe einen Benutzer gelöscht und kann immer noch eine von ihm gesendete " -"Nachricht sehen!" +#: ../settings/security/third-party/saml.rst:175 +msgid "Make sure the certificate is:" +msgstr "Vergewissern Sie sich, dass das Zertifikat:" -#: ../system/data-privacy.rst:133 -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." -msgstr "" -"Tickets können nur zu einem einzigen Kunden gehören, können aber Nachrichten " -"(\"Artikel\") von mehreren Personen enthalten. Wenn Sie einen Benutzer " -"gelöscht haben, aber immer noch Artikel sehen, die er gesendet hat, machen " -"Sie sich keine Sorgen - diese Artikel gehören zu einem Ticket, das jemand " -"anderem gehört, und enthalten keinen Hinweis mehr auf die Identität des " -"Absenders." +#: ../settings/security/third-party/saml.rst:177 +msgid "already valid and not yet expired" +msgstr "bereits gültig und noch nicht abgelaufen ist" -#: ../system/data-privacy.rst:141 -msgid "I removed a customer, now my reporting is off!" -msgstr "Ich habe einen Kunden entfernt, jetzt passt das Reporting nicht mehr!" +#: ../settings/security/third-party/saml.rst:178 +msgid "no CA certificate" +msgstr "kein CA-Zertifikat ist" -#: ../system/data-privacy.rst:140 +#: ../settings/security/third-party/saml.rst:179 +msgid "valid for signing and encrypting" +msgstr "gültig zum Signieren und Verschlüsseln ist" + +#: ../settings/security/third-party/saml.rst:185 +msgid "Private key (PEM)" +msgstr "Privater Schlüssel (PEM)" + +#: ../settings/security/third-party/saml.rst:182 msgid "" -"When removing users and their tickets, all references are removed. This also " -"affects e.g. Reporting - these information are lost." +"Paste the private key of your Zammad SAML client here, if you want to sign " +"the requests." msgstr "" -"Beim Entfernen von Benutzern und deren Tickets werden alle Referenzen " -"entfernt. Dies betrifft z.B. auch das Reporting - diese Informationen sind " -"weg." +"Fügen Sie hier den privaten Schlüssel Ihres Zammad SAML-Clients ein, wenn " +"Sie die Anfragen signieren möchten." -#: ../system/data-privacy.rst:145 -msgid "How long does Zammad store created tasks?" -msgstr "Wie lange speichert Zammad erstellte Aufgaben?" +#: ../settings/security/third-party/saml.rst:185 +msgid "Make sure the key is an RSA key with a length of at least 2048 bits." +msgstr "" +"Stellen Sie sicher, dass der Schlüssel ein RSA-Schlüssel mit einer Länge von " +"mindestens 2048 Bit ist." -#: ../system/data-privacy.rst:144 -msgid "" -"Please see the on-premise data section of the :docs:`data privacy ` chapter." +#: ../settings/security/third-party/saml.rst:188 +msgid "Private key secret" +msgstr "Geheimnis des privaten Schlüssels" + +#: ../settings/security/third-party/saml.rst:188 +msgid "If your private key is secured with a secret, you can provide it here." msgstr "" -"Bitte beachten Sie den Abschnitt über lokale Daten im Kapitel :docs:" -"`Datenschutz `." +"Wenn Ihr privater Schlüssel mit einem Passwort gesichert ist, können Sie es " +"hier angeben." -#: ../system/data-privacy.rst:150 -msgid "What about re-assigned tickets? I want to delete them, too." -msgstr "Was ist mit neu zugewiesenen Tickets? Ich möchte sie auch löschen." +#: ../settings/security/third-party/saml.rst:192 +msgid "Your callback URL" +msgstr "Ihre Callback-URL" -#: ../system/data-privacy.rst:148 +#: ../settings/security/third-party/saml.rst:191 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." +"This URL is needed for your IdP configuration so it knows where to redirect " +"to after successful authentication." msgstr "" -"Es werden nur Tickets gelöscht, die dem entsprechenden Kunden zum Zeitpunkt " -"der Ausführung der Datenschutz-Löschaufgabe zugewiesen sind. Historische " -"Zuweisungen werden bei der Löschung nicht berücksichtigt." +"Diese URL wird für die IdP-Konfiguration benötigt, damit dieser weiß, wohin " +"er nach erfolgreicher Authentifizierung weiterleiten muss." -#: ../system/data-privacy.rst:154 -msgid "Why are there so many deletion task entries, I didn't create them!" +#: ../settings/security/third-party/saml.rst:194 +msgid "" +"After saving your input by clicking on the \"Submit\" button, Zammad " +"verifies the provided keys/certificates (e.g. if they are valid for signing/" +"encrypting and if they aren't expired)." msgstr "" -"Warum gibt es so viele Löschaufgabeneinträge, ich habe sie nicht erstellt!" +"Nachdem Sie Ihre Eingaben durch Klicken auf die Schaltfläche \"Absenden\" " +"gespeichert haben, überprüft Zammad die bereitgestellten Schlüssel/" +"Zertifikate (z.B. ob sie zum Signieren/Verschlüsseln gültig und nicht " +"abgelaufen sind)." -#: ../system/data-privacy.rst:153 +#: ../settings/security/third-party/saml.rst:199 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." +"See :ref:`automatic account linking ` for details " +"on how to link existing Zammad accounts to IdP accounts." msgstr "" -"Die Löschaufgaben können von der :doc:`/manage/scheduler` kommen. Und zwar " -"ist die Aktion *\"Datenschutz-Löschaufgabe hinzufügen\"* für die Einträge " -"verantwortlich." - -#: ../system/integrations/checkmk/admin-panel-reference.rst:2 -msgid "Admin Panel Reference" -msgstr "Admin-Bereich" +"Siehe :ref:`automatische Kontoverknüpfung ` für " +"Details zur Verknüpfung bestehender Zammad-Konten mit IdP-Konten." -#: ../system/integrations/checkmk/admin-panel-reference.rst:None -msgid "Screenshot of Checkmk settings overview" -msgstr "Screenshot der Checkmk-Einstellungen in Zammad" +#: ../settings/security/third-party/saml.rst:205 +msgid "Automatic account linking doesn't work" +msgstr "Automatische Kontoverknüpfung funktioniert nicht" -#: ../system/integrations/checkmk/admin-panel-reference.rst:12 +#: ../settings/security/third-party/saml.rst:206 msgid "" -"Which :doc:`group ` should Checkmk tickets be assigned " -"to as a default (*i.e.,* when none is specified)?" +"Have you double-checked your IdP's user attribute mapping configuration?" msgstr "" -"Welcher :doc:`Gruppe ` sollen Checkmk-Tickets " -"standardmäßig zugewiesen werden (wenn keine angegeben ist)?" - -#: ../system/integrations/checkmk/admin-panel-reference.rst:15 -msgid "(Applies to :ref:`API alerts ` only.)" -msgstr "(Gilt nur für :ref:`API alerts `.)" - -#: ../system/integrations/checkmk/admin-panel-reference.rst:21 -msgid "Auto close" -msgstr "Automatisch schließen" +"Haben Sie die Konfiguration der Benutzerattribut-Zuordnung Ihres IdP " +"überprüft?" -#: ../system/integrations/checkmk/admin-panel-reference.rst:18 +#: ../settings/security/third-party/twitter.rst:4 msgid "" -"Should Zammad automatically close tickets if a service has recovered on its " -"own?" +"It is possible to create a quick login for your helpdesk via Twitter. To do " +"so, you need to follow these steps:" msgstr "" -"Soll Zammad Tickets automatisch schließen, wenn sich ein Dienst von selbst " -"\"erholt\" hat?" +"Es ist möglich, eine Anmeldung über Twitter zu erstellen. Dazu müssen Sie " +"die folgenden Schritte ausführen:" -#: ../system/integrations/checkmk/admin-panel-reference.rst:21 -msgid "(Agents will receive notifications for such closures as appropriate.)" +#: ../settings/security/third-party/twitter.rst:8 +msgid "Register Twitter App" +msgstr "Twitter-App registrieren" + +#: ../settings/security/third-party/twitter.rst:10 +msgid "Go to https://dev.twitter.com/apps and login with your account." msgstr "" -"(Agenten werden gegebenenfalls über solche Schließungen benachrichtigt.)" +"Rufen Sie https://dev.twitter.com/apps auf und melden Sie sich mit Ihrem " +"Konto an." -#: ../system/integrations/checkmk/admin-panel-reference.rst:30 -msgid "Auto-close state" -msgstr "Automatisch-Schließen-Status" +#: ../settings/security/third-party/twitter.rst:15 +msgid "Click on \"Create App\"" +msgstr "Klicken Sie auf \"Create App\"" -#: ../system/integrations/checkmk/admin-panel-reference.rst:24 -msgid "What ticket state should be applied when “auto-closing” a ticket?" -msgstr "" -"Welcher Ticketstatus soll beim \"automatischen Schließen\" eines Tickets " -"angewendet werden?" +#: ../settings/security/third-party/twitter.rst:None +msgid "new app page" +msgstr "neue App Seite" -#: ../system/integrations/checkmk/admin-panel-reference.rst:26 +#: ../settings/security/third-party/twitter.rst:20 msgid "" -"You can choose from the seven built-in ticket states. If these states aren't " -"enough for you, you can :ref:`define a new ticket state ` for this purpose as well. This can be useful for tracking " -"tickets with :doc:`reports `, for example." +"Enter app settings. As \"Callback URL\" you need to enter ``https://" +"zammad_host/api/v1/external_credentials/twitter/callback``. You need to " +"replace ``zammad_host`` with the domain of your Zammad system." msgstr "" -"Sie können aus den sieben eingebauten Ticketstatus wählen. Wenn Ihnen diese " -"Status nicht ausreichen, können Sie auch einen :ref:`neuen Status ` für diesen Zweck definieren. Dies kann z.B. für die " -"Auswertung von Tickets mit :doc:`Berichten ` " -"nützlich sein." - -#: ../system/integrations/checkmk/admin-panel-reference.rst:35 -#: ../system/integrations/cti/includes/recent-logs.include.rst:2 -#: ../system/integrations/ldap/index.rst:74 -#: ../system/integrations/pgp/index.rst:106 -msgid "Recent Logs" -msgstr "Aktuellste Protokolle" - -#: ../system/integrations/checkmk/admin-panel-reference.rst:None -msgid "Screenshot of Checkmk \"Recent Logs\" section" -msgstr "Screenshot des Checkmk-Bereichs \"Aktuellste Protokolle\"" +"Geben Sie die App-Einstellungen ein. Als \"Callback URL\" müssen Sie " +"``https://zammad_host/api/v1/external_credentials/twitter/callback`` " +"eingeben. Ersetzen Sie ``zammad_host`` durch die Domain Ihres Zammad-Systems." -#: ../system/integrations/checkmk/admin-panel-reference.rst:41 +#: ../settings/security/third-party/twitter.rst:24 msgid "" -"If you're having trouble getting Zammad and Checkmk to play nicely together, " -"this section can help you troubleshoot." +"After the app has been created, update the application icon and organization " +"attributes." msgstr "" -"Wenn Sie Probleme bei der Verbindung von Zammad und Checkmk haben kann " -"dieser Abschnitt Ihnen bei der Fehlersuche helfen." +"Nachdem die Anwendung erstellt wurde, aktualisieren Sie das Anwendungssymbol " +"und die Organisationsattribute." -#: ../system/integrations/checkmk/admin-panel-reference.rst:44 +#: ../settings/security/third-party/twitter.rst:None +msgid "set permissions to receive and send direct messages" +msgstr "" +"Berechtigungen zum Empfangen und Senden von Direktnachrichten festlegen" + +#: ../settings/security/third-party/twitter.rst:30 msgid "" -"It contains a record of the fifty most recent transactions that Zammad knows " -"about, including each one's request/response details and return status." +"Next we need to set ``read, write and access direct messages`` permissions " +"for the app." msgstr "" -"Sie enthält eine Aufzeichnung der letzten 50 Einträge, die Zammad bekannt " -"sind, einschließlich der Details zu jeder Anfrage/Antwort und des " -"zurückgegebenen Status." +"Als Nächstes müssen wir die Berechtigungen ``read, write and access direct " +"messages`` Berechtigungen für die Anwendung festlegen." -#: ../system/integrations/checkmk/api-reference.rst:2 -msgid "API Reference" -msgstr "API-Referenz" +#: ../settings/security/third-party/twitter.rst:None +msgid "click on Keys & Access Token, note them" +msgstr "Klicken Sie auf Schlüssel & Zugangstoken, notieren Sie sie" -#: ../system/integrations/checkmk/api-reference.rst:4 -msgid "" -"For most users, :ref:`the sample scripts from the Setup Guide ` will do the job just fine. But if you want more fine-grained control" -"—for instance, to create high- and low-priority tickets for different types " -"of system events—then you'll have to customize the data those scripts send " -"to Zammad." -msgstr "" -"Für die meisten Benutzer sind die :ref:`Beispielskripte aus dem " -"Einrichtungsanleitung ` völlig ausreichend. Wenn Sie " -"jedoch eine feinere Steuerung wünschen, z.B. um Tickets mit hoher und " -"niedriger Priorität für verschiedene Arten von Systemereignissen zu " -"erstellen, müssen Sie die Daten, die diese Skripte an Zammad senden, " -"anpassen." - -#: ../system/integrations/checkmk/api-reference.rst:15 +#: ../settings/security/third-party/twitter.rst:36 msgid "" -"This custom script will automatically set all tickets it creates to **high " -"priority** and **assign them to charlie@chrispresso.com**." +"Go to \"Keys and Access Token\" tab and note the \"Consumer Key\" and " +"\"Consumer Secret\"." msgstr "" -"Dieses benutzerdefinierte Skript setzt alle Tickets, die es erstellt, " -"automatisch auf **hohe Priorität** und **weist sie charlie@chrispresso.com** " -"zu." +"Gehen Sie zum Tab \"Keys and Access Token\" und notieren Sie sich den " +"\"Consumer Key\" und das \"Consumer Secret\"." -#: ../system/integrations/checkmk/api-reference.rst:32 -msgid "How Does it Work?" -msgstr "Wie funktioniert das?" +#: ../settings/security/third-party/twitter.rst:40 +msgid "Configure Zammad as Twitter App" +msgstr "Zammad als Twitter-App konfigurieren" -#: ../system/integrations/checkmk/api-reference.rst:34 +#: ../settings/security/third-party/twitter.rst:42 msgid "" -"There are two kinds of data you can pass to the API, both in the form of key-" -"value pairs:" +"Go to \"Admin > Security > Twitter > Third Party Applications > Twitter\" " +"Section." msgstr "" -"Es gibt zwei Arten von Daten, die Sie an die API übergeben können, beide in " -"Form von Schlüssel-Wert-Paaren:" +"Gehen Sie zu \"Einstellungen > Sicherheit > Anwendungen von Drittanbietern > " +"Twitter\"" -#: ../system/integrations/checkmk/api-reference.rst:44 -msgid "Checkmk parameters" -msgstr "Checkmk-Parameter" +#: ../settings/security/third-party/twitter.rst:None +msgid "Admin > Security > Third Party Applications" +msgstr "Verwaltung > Sicherheit > Anwendungen von Drittanbietern" -#: ../system/integrations/checkmk/api-reference.rst:38 +#: ../settings/security/third-party/twitter.rst:48 msgid "" -"are required, and make up the **contents** of the resulting tickets/" -"articles. They also determine whether an event creates a new ticket or " -"updates/closes an existing one." +"Fill in the \"Twitter Key\" and the \"Twitter Secret\" and click the " +"\"Submit\" button." msgstr "" -"sind erforderlich und bilden den **Inhalt** der resultierenden Tickets/" -"Artikel. Sie bestimmen auch, ob ein Ereignis ein neues Ticket erstellt oder " -"ein bestehendes aktualisiert/schließt." +"Geben Sie den \"Twitter Key\" und das \"Twitter Secret\" ein und klicken Sie " +"auf die Schaltfläche \"Übermitteln\"." -#: ../system/integrations/checkmk/api-reference.rst:42 +#: ../settings/security/third-party/twitter.rst:51 msgid "" -"These are the only values used in the sample scripts. **Use them as-is**; " -"technically, they can be customized, but it's hard to imagine a good reason " -"for it." +"Now you can link accounts via \"Avatar > Profile > Link Accounts\" or login " +"via Zammad login page." msgstr "" -"Dies sind die einzigen Werte, die in den Beispielskripten verwendet werden. " -"**Verwenden Sie sie am besten genau so**. Sie können auch angepasst werden, " -"aber uns fällt kein guter Grund dafür ein." +"Jetzt können Sie Konten über \"Avatar > Profil > Verknüpfte Konten\" " +"verknüpfen oder sich über die Zammad-Login-Seite anmelden." -#: ../system/integrations/checkmk/api-reference.rst:52 -msgid "Ticket attributes" -msgstr "Ticket Attribute" +#: ../settings/security/two-factor.rst:11 +msgid "Two-factor Authentication Methods" +msgstr "Methoden für Zwei-Faktor-Authentifizierung" -#: ../system/integrations/checkmk/api-reference.rst:47 +#: ../settings/security/two-factor.rst:2 +msgid "Two-Factor Authentication" +msgstr "Zwei-Faktor-Authentifizierung" + +#: ../settings/security/two-factor.rst:4 msgid "" -"are optional, and can be used to **adjust settings** on newly created " -"tickets (*e.g.,* set the owner, group, priority, or state)." +"Two-factor authentication (2FA) enhances the security of Zammad accounts by " +"adding an extra layer of verification beyond a password. It requires users " +"to provide two different types of authentication factors, typically " +"something they know (like a password) and something they possess (like a " +"mobile device or a security token), to ensure that only authorized " +"individuals can access the account." msgstr "" -"sind optional und können verwendet werden, um **Einstellungen** für neu " -"erstellte Tickets vorzunehmen (*z.B.* den Besitzer, die Gruppe, die " -"Priorität oder den Status festzulegen)." +"Die Zwei-Faktor-Authentifizierung (2FA) erweitert die Sicherheit von Zammad-" +"Konten, indem eine zusätzliche Prüfung neben einem Passwort erforderlich " +"ist. Benutzer müssen über zwei verschiedene Faktoren verfügen, um " +"sicherzustellen, dass Sie berechtigt sind, auf das Konto zuzugreifen. " +"Typischerweise ist das etwas, was die Benutzer wissen (wie ein Passwort) und " +"etwas, das sie besitzen (wie ein Mobilgerät oder ein Security-Token)." -#: ../system/integrations/checkmk/api-reference.rst:50 +#: ../settings/security/two-factor.rst:19 +msgid "Enable Recovery Codes" +msgstr "Wiederherstellungs-Codes aktivieren" + +#: ../settings/security/two-factor.rst:21 msgid "" -"If you want to customize your Checkmk alert script, do it with these. Simply " -"add an extra “form” option for each one (``-F \"key=value\"``) to your " -"script's ``curl`` command line, as in the example above." +"Recovery codes are one-time use security codes that can be used by the user " +"if they lose access to their other two-factor authentication methods. They " +"cannot be used on their own, they can only be activated if at least one two-" +"factor authentication method is enabled." msgstr "" -"Wenn Sie Ihr Checkmk-Warnskript anpassen wollen, können Sie dies mit diesen " -"tun. Fügen Sie einfach eine zusätzliche \"form\"-Option für jede dieser " -"Optionen (``-F \"key=value\"``) in die ``curl``-Befehlszeile Ihres Skripts " -"ein, wie im obigen Beispiel." +"Wiederherstellungscodes sind einmalig verwendbare Sicherheitscodes, die vom " +"Benutzer verwendet werden können, wenn er den Zugang zu seinen anderen Zwei-" +"Faktor-Authentifizierungsmethoden verliert. Sie können nicht allein " +"verwendet werden, sondern können nur aktiviert werden, wenn mindestens eine " +"Zwei-Faktor-Authentifizierungsmethode aktiviert ist." -#: ../system/integrations/checkmk/api-reference.rst:54 -msgid "💡 **It's just an API endpoint!**" -msgstr "💡 **Es ist nur ein API-Endpunkt!**" +#: ../settings/security/two-factor.rst:None +msgid "Enable Recovery Codes Setting" +msgstr "Einstellung Wiederherstellungscodes aktivieren" -#: ../system/integrations/checkmk/api-reference.rst:56 +#: ../settings/security/two-factor.rst:30 msgid "" -"When using Checkmk integration, messages need to be formatted in a certain " -"way, but that *doesn't mean the messages actually have to come from Checkmk*." +"Recovery codes can only be used as a backup method. If enabled, they will be " +"automatically generated for the user once they set up their initial two-" +"factor authentication method." msgstr "" -"Wenn Sie die Checkmk-Integration verwenden, müssen die Nachrichten auf eine " -"bestimmte Art und Weise formatiert werden, aber das bedeutet *nicht, dass " -"die Nachrichten tatsächlich von Checkmk kommen müssen*." +"Wiederherstellungscodes können nur als Backup-Methode verwendet werden. Wenn " +"sie aktiviert sind, werden sie automatisch für den Benutzer generiert, " +"sobald er seine erste Zwei-Faktor-Authentifizierungsmethode eingerichtet hat." -#: ../system/integrations/checkmk/api-reference.rst:59 +#: ../settings/security/two-factor.rst:34 msgid "" -"If you use another monitoring tool that's not officially supported by " -"Zammad, there's probably a way to make it work with your Checkmk callback " -"URL." +"The user will be asked to print out or save the generated recovery codes in " +"a safe place. Once used, a recovery code cannot be reused." msgstr "" -"Wenn Sie ein anderes Monitoring-Tool verwenden, das nicht offiziell von " -"Zammad unterstützt wird, gibt es wahrscheinlich eine Möglichkeit, es mit " -"Ihrer Checkmk-Callback-URL zum Laufen zu bringen." - -#: ../system/integrations/checkmk/api-reference.rst:63 -msgid "Checkmk Parameters" -msgstr "Checkmk-Parameter" +"Der Benutzer wird aufgefordert, die generierten Wiederherstellungscodes " +"auszudrucken oder an einem sicheren Ort zu speichern. Ein einmal verwendeter " +"Wiederherstellungscode kann nicht wiederverwendet werden." -#: ../system/integrations/checkmk/api-reference.rst:65 +#: ../settings/security/two-factor.rst:37 msgid "" -"When a notification is received, Zammad creates a new article containing the " -"details of the event that triggered it:" +"Users will also have an option to regenerate their recovery codes at any " +"time, which invalidates already existing recovery codes and provides them " +"with a list of fresh codes." msgstr "" -"Wenn eine Benachrichtigung eingeht, erstellt Zammad einen neuen Artikel mit " -"den Einzelheiten des Ereignisses, das die Benachrichtigung ausgelöst hat:" - -#: ../system/integrations/checkmk/api-reference.rst:None -msgid "Checkmk article body" -msgstr "Checkmk Artikelinhalt" +"Die Nutzer haben außerdem die Möglichkeit, ihre Wiederherstellungscodes " +"jederzeit neu zu generieren, wodurch bereits vorhandene " +"Wiederherstellungscodes ungültig werden und sie eine Liste mit neuen Codes " +"erhalten." -#: ../system/integrations/checkmk/api-reference.rst:72 +#: ../settings/security/two-factor.rst:41 msgid "" -"These details come from the fields listed below, which correspond to " -"parameters provided by Checkmk (``$NOTIFY_*``)." +"After you enable this setting, when the user completes a setup of their " +"initial two-factor authentication method, they will be presented with a list " +"of recovery codes and instructed to save them for later use." msgstr "" -"Diese Angaben stammen aus den unten aufgeführten Feldern, die den von " -"Checkmk bereitgestellten Parametern entsprechen (``$NOTIFY_*``)." +"Nachdem Sie diese Einstellung aktiviert haben, wird dem Benutzer nach " +"Abschluss der Einrichtung seiner Zwei-Faktor-Authentifizierungsmethode eine " +"Liste mit Wiederherstellungscodes angezeigt, die er zur späteren Verwendung " +"speichern kann." -#: ../system/integrations/checkmk/api-reference.rst:75 -msgid "**Required fields are marked with an asterisk (\\*).**" -msgstr "**Erforderliche Felder sind mit einem Stern (\\*) gekennzeichnet.**" +#: ../settings/security/two-factor.rst:None +msgid "Recovery Codes Generation Modal Dialog" +msgstr "Dialog zur Erzeugung von Wiederherstellungscodes" -#: ../system/integrations/checkmk/api-reference.rst:79 -msgid "event_id\\*" -msgstr "event_id\\*" +#: ../settings/security/two-factor.rst:50 +msgid "Enforce the Set Up of the Two-Factor Authentication" +msgstr "Einrichtung der Zwei-Faktor-Authentifizierung erzwingen" -#: ../system/integrations/checkmk/api-reference.rst:78 +#: ../settings/security/two-factor.rst:52 msgid "" -"A unique ID for the system event. (``$NOTIFY_SERVICEPROBLEMID`` / " -"``$NOTIFY_HOSTPROBLEMID``)" +"In case you wish to require your users to set up at least one two-factor " +"authentication method for their account, you can do this by selecting " +"specific user roles the requirement applies to in **Enforced for user " +"roles** setting. Of course you must have at least one two-factor " +"authentication method enabled for this setting to take effect." msgstr "" -"Eine eindeutige ID für das Systemereignis. (``$NOTIFY_SERVICEPROBLEMID`` / " -"``$NOTIFY_HOSTPROBLEMID``)" +"Wenn Sie von Ihren Benutzern verlangen wollen, dass sie mindestens eine Zwei-" +"Faktor-Authentifizierungsmethode für ihr Konto einrichten, können Sie dies " +"tun, indem Sie in der Einstellung **Für Benutzer-Rollen erzwingen** " +"bestimmte Benutzerrollen auswählen, für die die Anforderung gilt. Natürlich " +"müssen Sie mindestens eine Zwei-Faktor-Authentifizierungsmethode aktiviert " +"haben, damit diese Einstellung wirksam wird." -#: ../system/integrations/checkmk/api-reference.rst:86 -msgid "host\\*" -msgstr "host\\*" +#: ../settings/security/two-factor.rst:None +msgid "Enforced for User Roles Setting" +msgstr "Verpflichtend für Benutzerrollen" -#: ../system/integrations/checkmk/api-reference.rst:82 +#: ../settings/security/two-factor.rst:62 msgid "" -"The hostname of the system that the event originated from. " -"(``$NOTIFY_HOSTNAME``)" +"After you change this setting, if the user has one of the selected roles on " +"their account, they will be forced to set up the two-factor authentication " +"upon next sign in or application reload." msgstr "" -"Der Hostname des Systems, von dem das Ereignis ausgeht. " -"(``$NOTIFY_HOSTNAME``)" +"Nachdem Sie diese Einstellung geändert haben, werden Benutzer mit der " +"entsprechenden Rolle gezwungen, die Zwei-Faktor-Authentifizierung bei der " +"nächsten Anmeldung oder beim erneuten Laden der Anwendung einzurichten." -#: ../system/integrations/checkmk/api-reference.rst:85 +#: ../settings/security/two-factor.rst:66 msgid "" -"Used to determine if a new event belongs to an existing ticket. Also used in " -"the subject line of the resulting article (“ is ”)." +"A modal dialog with instructions will be shown, and they will not be able to " +"do any work before they set up at least one two-factor method." msgstr "" -"Wird verwendet, um festzustellen, ob ein neues Ereignis zu einem bestehenden " -"Ticket gehört. Wird auch in der Betreffzeile des resultierenden Artikels " -"verwendet (\" ist \")." +"Es wird ein Dialogfeld mit Anweisungen angezeigt und sie können erst dann " +"weiter arbeiten, wenn sie mindestens eine Zwei-Faktor-Methode eingerichtet " +"haben." -#: ../system/integrations/checkmk/api-reference.rst:96 -msgid "service" -msgstr "service" +#: ../settings/security/two-factor.rst:None +msgid "Modal Dialog for Enforcing Two-Factor Authentication Set Up" +msgstr "Dialog zur Erzwingung der Zwei-Faktoren-Authentifizierung" -#: ../system/integrations/checkmk/api-reference.rst:89 -msgid "" -"The name of the service that the event originated from. " -"(``$NOTIFY_SERVICEDESC``)" -msgstr "" -"Der Name des Dienstes, von dem das Ereignis ausgeht. " -"(``$NOTIFY_SERVICEDESC``)" +#: ../settings/security/two-factor.rst:74 +msgid "Reset Two-Factor Authentication for a Specific User" +msgstr "Zwei-Faktor-Authentifizierung für bestimmte User zurücksetzen" -#: ../system/integrations/checkmk/api-reference.rst:92 -msgid "Used to determine if a new event belongs to an existing ticket." +#: ../settings/security/two-factor.rst:76 +msgid "" +"In case an user isn't able to login anymore because of an inaccessible " +"second factor, you can reset the user's 2FA method." msgstr "" -"Wird verwendet, um festzustellen, ob ein neues Ereignis zu einem bestehenden " -"Ticket gehört." +"Falls sich ein Benutzer aufgrund eine nicht verfügbaren Zwei-Faktor-Methode " +"nicht mehr anmelden kann, können Sie die 2FA-Methode des Benutzers " +"zurücksetzen." -#: ../system/integrations/checkmk/api-reference.rst:94 -#: ../system/integrations/checkmk/api-reference.rst:110 -msgid "Displayed as ``-`` when omitted." -msgstr "Wird als ``-`` angezeigt, wenn es weggelassen wird." +#: ../settings/security/two-factor.rst:79 +msgid "" +"To do this, go to the user management and search for the relevant user. " +"After you found the account, click the button in the action column and " +"select \"Manage Two-Factor Authentication\":" +msgstr "" +"Gehen Sie dazu in die Benutzerverwaltung und suchen Sie nach dem " +"entsprechenden Benutzer. Nachdem Sie das Konto gefunden haben, klicken Sie " +"auf den Button in der Aktionsspalte und wählen Sie \"Zwei-Faktor-" +"Authentifizierung verwalten\":" -#: ../system/integrations/checkmk/api-reference.rst:104 -msgid "state\\*" -msgstr "state\\*" +#: ../settings/security/two-factor.rst:None +msgid "Context menu in action column in user management" +msgstr "Kontextmenü in der Aktionsspalte der Benutzerverwaltung" -#: ../system/integrations/checkmk/api-reference.rst:99 +#: ../settings/security/two-factor.rst:87 msgid "" -"The current state of the service or host in question. " -"(``$NOTIFY_SERVICESTATE`` / ``$NOTIFY_HOSTSTATE``)" +"After selecting this, you can see a dialog where you can either reset one " +"2FA method or reset all of the user's 2FA methods:" msgstr "" -"Der aktuelle Zustand des entsprechenden Dienstes oder Hosts. " -"(``$NOTIFY_SERVICESTATE`` / ``$NOTIFY_HOSTSTATE``)" +"Nachdem Sie dies ausgewählt haben, sehen Sie einen Dialog, in dem Sie " +"entweder eine 2FA-Methode oder alle 2FA-Methoden des Benutzers zurücksetzen " +"können:" -#: ../system/integrations/checkmk/api-reference.rst:102 +#: ../settings/security/two-factor.rst:None +msgid "Dialog for resetting user's 2FA method" +msgstr "Dialog zum Zurücksetzen der 2FA-Methode des Benutzers" + +#: ../settings/security/two-factor.rst:94 msgid "" -"Used to detect when a ticket should be auto-closed (*i.e.,* on ``OK``/" -"``UP``). Also used in the subject line of the resulting article (“ is " -"”)." +"Choose the fitting one, click on the corresponding \"Remove ...\" button and " +"confirm your action. The user now has to setup a new 2FA method, depending " +"on your 2FA configuration." msgstr "" -"Wird verwendet, um zu erkennen, wann ein Ticket automatisch geschlossen " -"werden soll (*d.h.* bei ``OK``/``UP``). Wird auch in der Betreffzeile des " -"resultierenden Artikels verwendet (\" ist \")." +"Wählen Sie die passende aus, klicken Sie auf die entsprechende Schaltfläche " +"\"... entfernen\" und bestätigen Sie Ihre Aktion. Der Benutzer muss nun " +"abhängig von Ihrer 2FA-Konfiguration eine neue 2FA-Methode einrichten." -#: ../system/integrations/checkmk/api-reference.rst:110 -msgid "text" -msgstr "text" +#: ../settings/security/two-factor/authenticator-app.rst:2 +msgid "Authenticator App" +msgstr "Authentifizierungs-App" -#: ../system/integrations/checkmk/api-reference.rst:107 +#: ../settings/security/two-factor/authenticator-app.rst:4 msgid "" -"The output of the process that triggered the event. " -"(``$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" +"The authenticator app method is a type of two-factor authentication that " +"uses a mobile application to generate one-time codes for account " +"verification. After setting up the authenticator app on their device, the " +"user links it to their Zammad account." msgstr "" -"Die Ausgabe des Prozesses, der das Ereignis ausgelöst hat. " -"(``$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" +"Die Authentifizierungs-App ist eine Methode der Zwei-Faktor-" +"Authentifizierung, bei der eine mobile App (\"Authentifizierungs-App\") " +"Einmal-Codes generiert, die beim Anmelden geprüft werden. Nachdem die " +"Benutzer eine Authentifizierungs-App auf Ihrem Gerät eingerichtet haben, " +"können diese die App mit ihr Zammad-Konto verknüpfen." -#: ../system/integrations/checkmk/api-reference.rst:121 +#: ../settings/security/two-factor/authenticator-app.rst:12 msgid "" -"The Object Manager attribute panel displays built-in and custom\n" -"attribute names." +"When logging in, the user is prompted to enter a time-sensitive code " +"generated by the app, in addition to their password. This code acts as the " +"second factor of authentication, providing an extra layer of security as it " +"changes periodically and is unique to the user's device." msgstr "" -"Die Attributeinstellungen des Objektmanagers zeigen integrierte und " -"benutzerdefinierte Attributnamen an." +"Bei der Anmeldung wird der Nutzer aufgefordert, zusätzlich zu seinem " +"Passwort einen von der App generierten zeitabhängigen Code einzugeben. " +"Dieser Code dient als zweiter Authentifizierungsfaktor und bietet eine " +"zusätzliche Sicherheitsebene, da er sich regelmäßig ändert und nur auf dem " +"Gerät des Nutzers vorhanden ist." -#: ../system/integrations/checkmk/api-reference.rst:121 -msgid "Find a complete list of ticket attributes in the Object Manager." -msgstr "" -"Eine vollständige Liste der Ticketattribute finden Sie im Objektmanager." +#: ../settings/security/two-factor/authenticator-app.rst:None +msgid "Security Code in Google Authenticator App" +msgstr "Sicherheits-Code in der Google Authenticator App" -#: ../system/integrations/checkmk/api-reference.rst:123 +#: ../settings/security/two-factor/authenticator-app.rst:22 msgid "" -"Ticket attributes are entirely optional, and can be used to customize the " -"tickets that Checkmk creates. (Note that these attributes will be ignored if " -"a new event belongs to an existing ticket.)" +"The app generates codes based on a shared secret key stored securely on both " +"the user's device and the server, ensuring a synchronized and secure " +"authentication process. The method of generating the codes is sometimes also " +"called TOTP (time-based one-time password)." msgstr "" -"Ticket-Attribute sind völlig optional und können verwendet werden, um die " -"Tickets, die Checkmk erstellt, individuell zu gestalten. (Beachten Sie, dass " -"diese Attribute ignoriert werden, wenn ein neues Ereignis zu einem " -"bestehenden Ticket erstellt wird.)" +"Die App generiert Codes auf der Grundlage eines gemeinsam genutzten geheimen " +"Schlüssels, der sowohl auf dem Gerät des Nutzers als auch auf dem Server " +"sicher gespeichert ist, wodurch ein synchronisierter und sicherer " +"Authentifizierungsprozess gewährleistet wird. Die Methode zur Generierung " +"der Codes wird manchmal auch als TOTP (time-based one-time password) " +"bezeichnet." -#: ../system/integrations/checkmk/api-reference.rst:128 -msgid "" -"Why would you want to do this? Maybe you have only one IT guy, and all " -"system monitoring issues should be automatically assigned to him. Or, maybe " -"you're creating multiple notification rules so that database outages take " -"higher priority than disk space warnings." -msgstr "" -"Warum sollten Sie das tun? Vielleicht haben Sie nur einen IT-Mitarbeiter, " -"dem alle Probleme bei der Systemüberwachung automatisch zugewiesen werden " -"sollen. Oder vielleicht erstellen Sie mehrere Benachrichtigungsregeln, so " -"dass Datenbankausfälle höhere Priorität haben als Speicherplatzwarnungen." +#: ../settings/security/two-factor/authenticator-app.rst:28 +msgid "Enabling the Authenticator App Method" +msgstr "Aktivieren der Authenticator App-Methode" -#: ../system/integrations/checkmk/api-reference.rst:135 -msgid "In most cases, you'll probably want to set one of the following:" +#: ../settings/security/two-factor/authenticator-app.rst:30 +#: ../settings/security/two-factor/security-keys.rst:28 +msgid "To enable the method, just toggle the switch on in the settings." msgstr "" -"In den meisten Fällen werden Sie wahrscheinlich eine der folgenden " -"Einstellungen vornehmen wollen:" +"Um die Methode zu aktivieren, schalten Sie sie einfach in den Einstellungen " +"ein, indem Sie den Schalter aktivieren." -#: ../system/integrations/checkmk/api-reference.rst:137 -msgid "group" -msgstr "Gruppe" +#: ../settings/security/two-factor/authenticator-app.rst:None +msgid "Authenticator App Switch in Settings" +msgstr "Authenticator App Schalter in den Einstellungen" -#: ../system/integrations/checkmk/api-reference.rst:139 -msgid "state" -msgstr "Status" +#: ../settings/security/two-factor/authenticator-app.rst:36 +msgid "" +"Now the users will be able to set up this two-factor authentication method " +"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " +"Once they do, on next sign-in with password, they will be asked to provide " +"an additional security code generated by their mobile device." +msgstr "" +"Jetzt können die Nutzer diese Zwei-Faktor-Authentifizierungsmethode für ihre " +"Konten über \"Avatar > Profil > Passwort & Authentifizierung\" einrichten. " +"Sobald sie dies getan haben, werden sie bei der nächsten Anmeldung mit " +"Passwort aufgefordert, einen zusätzlichen Sicherheitscode einzugeben, der " +"von ihrem Mobilgerät generiert wird." -#: ../system/integrations/checkmk/api-reference.rst:140 -msgid "priority" -msgstr "Priorität" +#: ../settings/security/two-factor/security-keys.rst:2 +msgid "Security Keys" +msgstr "Sicherheits-Schlüssel" -#: ../system/integrations/checkmk/api-reference.rst:142 +#: ../settings/security/two-factor/security-keys.rst:4 msgid "" -"but in practice, you can set almost any attribute, including :doc:`custom " -"ones you created through the Object Manager `." +"The security keys method is a type of a two-factor authentication that uses " +"Web Authentication API in the browser for verifying user's identity. The " +"user can register multiple hardware or software security keys with their " +"Zammad account and then they can use it during the sign-in process." msgstr "" -"aber in der Praxis können Sie fast jedes Attribut setzen, einschließlich :" -"doc:`benutzerdefinierter Attribute, die Sie über den Objektmanager ` erstellt haben." +"Die Sicherheitsschlüssel-Methode ist eine Art der Zwei-Faktor-" +"Authentifizierung, die die Web-Authentifizierungs-API im Browser zur " +"Überprüfung der Identität des Benutzers verwendet. Der Benutzer kann mehrere " +"Hardware- oder Softwareschlüssel mit seinem Zammad-Konto registrieren und " +"diese dann während des Anmeldevorgangs verwenden." -#: ../system/integrations/checkmk/api-reference.rst:145 -msgid "Please note that the following attributes are **not customizable**:" +#: ../settings/security/two-factor/security-keys.rst:12 +msgid "" +"When logging in, the user is prompted to provide the same security key they " +"registered with their account, in addition to their password. This key acts " +"as the second factor of authentication, providing an extra layer of security." msgstr "" -"Bitte beachten Sie, dass die folgenden Attribute **nicht angepasst werden " -"können**:" - -#: ../system/integrations/checkmk/api-reference.rst:147 -msgid "title" -msgstr "title" - -#: ../system/integrations/checkmk/api-reference.rst:148 -msgid "id" -msgstr "id" - -#: ../system/integrations/checkmk/api-reference.rst:149 -msgid "ticket number" -msgstr "ticket number" +"Bei der Anmeldung wird der Benutzer aufgefordert, zusätzlich zu seinem " +"Passwort den hinterlegten Sicherheitsschlüssel anzugeben, den er für sein " +"Konto registriert hat. Dieser Schlüssel dient als zweiter " +"Authentifizierungsfaktor und bietet eine zusätzliche Sicherheitsebene." -#: ../system/integrations/checkmk/api-reference.rst:151 -msgid "created_by_id" -msgstr "created_by_id" +#: ../settings/security/two-factor/security-keys.rst:None +msgid "Security Key dialog in Safari on macOS" +msgstr "Sicherheitsschlüssel-Dialog in Safari unter macOS" -#: ../system/integrations/checkmk/api-reference.rst:152 -msgid "updated_by_id" -msgstr "updated_by_id" +#: ../settings/security/two-factor/security-keys.rst:21 +msgid "" +"The type of the key can range from hardware USB sticks to passkeys stored in " +"a device of user's choice. Which type can be used depends on the browser " +"flavor and the platform of the user." +msgstr "" +"Die Art des Schlüssels kann von Hardware-USB-Sticks bis zu Passkeys reichen, " +"die in einem Gerät der Wahl des Nutzers gespeichert sind. Welcher Typ " +"verwendet werden kann, hängt von der Browser-Variante und der Plattform des " +"Nutzers ab." -#: ../system/integrations/checkmk/api-reference.rst:155 -msgid "Which Values Can Be Set?" -msgstr "Welche Werte können eingestellt werden?" +#: ../settings/security/two-factor/security-keys.rst:26 +msgid "Enabling the Security Keys Method" +msgstr "Aktivieren der Sicherheitsschlüssel-Methode" -#: ../system/integrations/checkmk/api-reference.rst:157 -msgid "😵 **Invalid values → unpredictable behavior**" -msgstr "😵 **Ungültige Werte → unvorhersehbares Verhalten**" +#: ../settings/security/two-factor/security-keys.rst:None +msgid "Security Keys Switch in Settings" +msgstr "Schalter für Sicherheitsschlüssel in den Einstellungen" -#: ../system/integrations/checkmk/api-reference.rst:159 +#: ../settings/security/two-factor/security-keys.rst:34 msgid "" -"If you provide a value that Zammad doesn't understand (*e.g.,* ``-F " -"\"priority=high\"``), it's not always clear what will happen. In some cases, " -"a ticket will be created with the default values instead - but in others, it " -"may not be created at all!" +"Now the users will be able to set up this two-factor authentication method " +"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " +"Once they do, on next sign-in with password, they will be asked to provide " +"the same security key they registered during the setup." msgstr "" -"Wenn Sie einen Wert angeben, den Zammad nicht versteht (*z.B.* ``-F " -"\"priority=high\"``), ist nicht immer klar, was passieren wird. In einigen " -"Fällen wird ein Ticket stattdessen mit den Standardwerten erstellt - in " -"anderen Fällen wird es aber vielleicht gar nicht erstellt!" - -#: ../system/integrations/checkmk/api-reference.rst:164 -msgid "So what values does Zammad understand, then? Well, it depends..." -msgstr "Welche Werte versteht Zammad denn nun? Nun, das kommt darauf an..." - -#: ../system/integrations/checkmk/api-reference.rst:168 -msgid "Use an email address or username:" -msgstr "Verwenden Sie eine E-Mail-Adresse oder einen Benutzernamen:" - -#: ../system/integrations/checkmk/api-reference.rst:190 -msgid "group & priority" -msgstr "Gruppe & Priorität" +"Jetzt können die Nutzer diese Zwei-Faktor-Authentifizierungsmethode für ihre " +"Konten über \"Avatar > Profil > Passwort & Authentifizierung\" einrichten. " +"Sobald sie dies getan haben, werden sie bei der nächsten Anmeldung mit " +"Passwort aufgefordert, den Sicherheitsschlüssel bereitzustellen, den sie in " +"ihrem Konto hinterlegt haben." -#: ../system/integrations/checkmk/api-reference.rst:175 -msgid "Refer to the dropdown menus in the ticket pane:" -msgstr "Beachten Sie die Dropdown-Menüs im Ticketbereich:" +#: ../settings/system/system-selfhosted.include.rst:3 +msgid "" +"Below settings are only available to self hosted users. In hosted " +"environments we're handling these settings for you to ensure service " +"stability." +msgstr "" +"Die nachstehenden Einstellungen sind nur für self-hosting Benutzer " +"verfügbar. In unserem Hosting übernehmen wir diese Einstellungen für Sie, um " +"die Stabilität des Dienstes zu gewährleisten." -#: ../system/integrations/checkmk/api-reference.rst:0 -msgid "See possible values for certain attributes in the ticket pane." -msgstr "Siehe mögliche Werte für bestimmte Attribute im Ticketbereich." +#: ../settings/system/base.rst:11 +msgid "Fully Qualified Domain Name" +msgstr "Fully Qualified Domain Name" -#: ../system/integrations/checkmk/api-reference.rst:187 -msgid "🙅 **Ticket state CANNOT be set this way!**" -msgstr "🙅 **Der Ticketstatus kann auf diese Weise NICHT eingestellt werden!**" +#: ../settings/system/base.rst:7 +msgid "The URL of your Zammad installation." +msgstr "Die URL Ihrer Zammad-Installation." -#: ../system/integrations/checkmk/api-reference.rst:189 -msgid "" -"Why? Because ``-F \"state=...\"`` is already used :ref:`as a Checkmk " -"parameter `." +#: ../settings/system/base.rst:9 ../settings/system/base.rst:17 +#, fuzzy +#| msgid "" +#| "This setting is used within :doc:`/system/variables` and notifications." +msgid "This setting is used within :doc:`/misc/variables` and notifications." msgstr "" -"Warum? Weil ``-F \"state=...\"`` bereits :ref:`als ein Checkmk-Parameter " -"` verwendet wird." - -#: ../system/integrations/checkmk/api-reference.rst:222 -msgid "Everything Else" -msgstr "Alles andere" +"Diese Einstellung wird in :doc:`/system/variables` und Benachrichtigungen " +"verwendet." -#: ../system/integrations/checkmk/api-reference.rst:193 -msgid "" -"To set any other attributes, it helps to know your way around the :docs:" -"`rails console `. Valid values are those that you can " -"set with a string:" +#: ../settings/system/system-base.include.rst:1 +msgid "It is automatically set by the *Getting Started wizard*." msgstr "" -"Um andere Attribute zu setzen, hilft es, sich in der :docs:`rails console ` auszukennen. Gültige Werte sind diejenigen, die Sie mit " -"einer Zeichenkette setzen können:" +"Diese Einstellung wird automatisch durch den *Einrichtungsassistenten* " +"festgelegt." -#: ../system/integrations/checkmk/api-reference.rst:218 -msgid "These values can then be passed directly to the API:" -msgstr "Diese Werte können dann direkt an die API übergeben werden:" +#: ../settings/system/system-base.include.rst:5 +msgid "Changing this setting also changes callback URLs for your channels etc." +msgstr "" +"Durch die Änderung dieser Einstellung werden auch die Callback-URLs für Ihre " +"Kanäle usw. geändert." -#: ../system/integrations/checkmk/index.rst:16 -msgid "How does it work?" -msgstr "Wie funktioniert das?" +#: ../settings/system/system-base.include.rst:6 +msgid "This setting can have negative affects on being able to login." +msgstr "Diese Einstellung kann zu Schwierigkeiten bei der Anmeldung führen." -#: ../system/integrations/checkmk/index.rst:2 -msgid "Checkmk" -msgstr "Checkmk" +#: ../settings/system/base.rst:19 +msgid "HTTP type" +msgstr "HTTP-Typ" -#: ../system/integrations/checkmk/index.rst:4 +#: ../settings/system/base.rst:14 msgid "" -"`Checkmk `_ is a powerful IT monitoring tool that can " -"send real-time status alerts to Zammad via email or REST API. Set these " -"alerts up in Checkmk, and Zammad will automatically create, update, and " -"close tickets based on the health of your system:" +"The HTTP type tells your installation how your clients connect. This is " +"relevant for authentication and cookie security." msgstr "" -"`Checkmk `_ ist ein mächtiges IT-Tool für Monitoring, " -"das Echtzeit-Alarme an Zammad via E-Mail oder REST-API senden kann. " -"Konfigurieren Sie die Alarme in Checkmk und Zammad wird automatisch Tickets " -"basierend auf der Systemstatus erstellen, aktualisieren und schließen:" - -#: ../system/integrations/checkmk/index.rst:14 -msgid "Screenshot of ticket created by Checkmk notifications" -msgstr "Screenshot eines durch Checkmk-Benachrichtigungen erstellten Tickets" - -#: ../system/integrations/checkmk/index.rst:14 -msgid "Multiple alerts, same ticket." -msgstr "Mehrere Alarme, dasselbe Ticket." +"Der HTTP-Typ teilt Ihrer Installation mit, wie sich Ihre Clients verbinden. " +"Dies ist wichtig für die Authentifizierung und die Cookie-Sicherheit." -#: ../system/integrations/checkmk/setup-guide.rst:2 -msgid "Setup Guide" -msgstr "Einrichtungs-Anleitung" +#: ../settings/system/base.rst:31 +msgid "SystemID" +msgstr "SystemID" -#: ../system/integrations/checkmk/setup-guide.rst:4 +#: ../settings/system/base.rst:22 msgid "" -"Whenever the Checkmk integration is enabled, Zammad listens for messages on " -"its API and over email. As long as those messages follow the required " -"format, Zammad will create new tickets (or find and update existing ones) " -"based on the message contents." +"This ID is being used within your ticket number. In case you're " +"communicating with another ticket system with similar ticket number schemes " +"this ID greatly reduces the risk of false follow ups." msgstr "" -"Immer wenn die Checkmk-Integration aktiviert ist, lauscht Zammad auf " -"Nachrichten über seine API und per E-Mail. Solange diese Nachrichten dem " -"erforderlichen Format entsprechen, erstellt Zammad neue Tickets (oder findet " -"und aktualisiert bestehende) auf der Grundlage der Nachrichteninhalte." +"Diese ID wird in Ihrer Ticketnummer verwendet. Für den Fall, dass Sie mit " +"einem anderen Ticketsystem mit ähnlichen Nummernschema kommunizieren, " +"verringert diese ID das Risiko falscher Zuordnungen erheblich." -#: ../system/integrations/checkmk/setup-guide.rst:10 +#: ../settings/system/base.rst:26 msgid "" -"That means that “setting up Checkmk integration” is simply a matter of " -"**adding configuration to your Checkmk site**: telling it when to send these " -"messages and what to say. To do that, you'll need to create a new " -"**notification rule** (see `Checkmk's official docs `_ for help with that)." +"The SystemID is randomly selected upon installation of Zammad (``1-99``)." msgstr "" -"Das bedeutet, dass die \"Einrichtung der Checkmk-Integration\" lediglich " -"eine Frage der **Konfiguration Ihrer Checkmk-Seite** ist: Sie müssen ihr " -"mitteilen, wann sie diese Nachrichten senden soll und was sie sagen soll. " -"Dazu müssen Sie eine neue **Benachrichtigungsregel** erstellen (Hilfe dazu " -"finden Sie in der `offiziellen Dokumentation von Checkmk `_ )." +"Die SystemID wird bei der Installation von Zammad zufällig gesetzt " +"(``1-99``)." -#: ../system/integrations/checkmk/setup-guide.rst:17 +#: ../settings/system/base.rst:30 msgid "" -"As part of this new rule, you'll have to choose a **notification method** " -"(*i.e.,* a script to execute whenever the rule is triggered). This script " -"will be written by you (samples below), and contain the logic for sending " -"API/email messages to Zammad:" +"**Do not** change this setting in a productive system! Your Zammad " +"installation may no longer recognize old ticket number based follow ups upon " +"change!" msgstr "" -"Als Teil dieser neuen Regel müssen Sie eine **Benachrichtigungsmethode** " -"wählen (*d.h.* ein Skript, das ausgeführt wird, wenn die Regel ausgelöst " -"wird). Dieses Skript wird von Ihnen geschrieben (Beispiele unten) und " -"enthält die Logik zum Senden von API-/E-Mail-Nachrichten an Zammad:" +"**Ändern Sie diese Einstellung nicht** in einem produktiven System! Ihre " +"Zammad-Installation erkennt bei einer Änderung möglicherweise auf alten " +"Ticketnummern basierende Rückfragen nicht mehr!" -#: ../system/integrations/checkmk/setup-guide.rst:26 -msgid "Checkmk \"New Rule\" dialog" -msgstr "Checkmk Dialog \"New Rule\"" +#: ../settings/system/frontend.rst:2 +msgid "Frontend" +msgstr "Frontend" -#: ../system/integrations/checkmk/setup-guide.rst:26 +#: ../settings/system/frontend.rst:22 +msgid "Core Workflow Ajax Mode" +msgstr "Core Workflow Ajax Modus" + +#: ../settings/system/frontend.rst:6 msgid "" -"Find your custom scripts in the Checkmk WATO under **Notifications > New " -"Rule > Notification Method**." +"This setting allows administrators to enforce :doc:`/system/core-workflows` " +"to use Ajax-Calls instead of web sockets. You'll usually only need this if " +"you experience serious issues as noted below." msgstr "" -"Sie finden Ihre benutzerdefinierten Skripte in der Checkmk WATO unter " -"**Notifications > New Rule > Notification Method**." +"Mit dieser Einstellung können Administratoren erzwingen, dass :doc:`/system/" +"core-workflows` Ajax-Aufrufe anstelle von Web-Sockets verwendet werden. Dies " +"ist in der Regel nur dann erforderlich, wenn schwerwiegende Probleme " +"auftreten (siehe unten)." -#: ../system/integrations/checkmk/setup-guide.rst:29 +#: ../settings/system/frontend.rst:10 +msgid "**🤓 Possible (technical) reasons**" +msgstr "**🤓 Mögliche (technische) Gründe**" + +#: ../settings/system/frontend.rst:12 msgid "" -"Once you're done setting up your new rule, you're all set! New tickets " -"should start coming in and auto-updating any time your rule is triggered." +"In some cases, your network structure (e.g. firewalls, proxies) may " +"disconnect long web socket connections. This leads to select fields staying " +"empty (e.g. owner selection *after* selecting your group) or fields not " +"shown / hidden (e.g. when switching to or from pending states, the \"pending " +"till\" field not showing / hiding)." msgstr "" -"Sobald Sie Ihre neue Regel eingerichtet haben, sind Sie startklar! Neue " -"Tickets sollten nun eingehen und jedes Mal automatisch aktualisiert werden, " -"wenn die Regel ausgelöst wird." +"In einigen Fällen kann es vorkommen, dass Ihr Netzwerk (z.B. Firewalls, " +"Proxys) lange Web-Socket-Verbindungen unterbricht. Dies führt dazu, dass " +"Auswahlfelder leer bleiben (z.B. Auswahl des Besitzers *nach* " +"Gruppenauswahl) oder Felder nicht angezeigt/ausgeblendet werden (z.B. beim " +"Wechsel in oder in den Status \"Warten auf\" wird das Feld \"Warten bis\" " +"nicht angezeigt/ausgeblendet)." -#: ../system/integrations/checkmk/setup-guide.rst:33 +#: ../settings/system/frontend.rst:18 msgid "" -"(If you need help troubleshooting, be sure to check the :ref:`checkmk-recent-" -"logs`.)" +"Please keep in mind that the Ajax fallback may cause serious pressure on " +"your application server. If you have the choice stick to web sockets." msgstr "" -"(Wenn Sie Hilfe bei der Fehlersuche benötigen, sollten Sie die :ref:`checkmk-" -"recent-logs` überprüfen.)" +"Bitte bedenken Sie, dass der Ajax-Fallback Ihren Server stark belasten kann. " +"Wenn Sie die Wahl haben, bleiben Sie bei Web-Sockets." -#: ../system/integrations/checkmk/setup-guide.rst:38 -msgid "API Alerts" -msgstr "API-Warnungen" +#: ../settings/system/frontend.rst:22 +msgid "Default: ``no`` (inactive)" +msgstr "Voreinstellung: ``nein`` (inaktiv)" -#: ../system/integrations/checkmk/setup-guide.rst:40 +#: ../settings/system/frontend.rst:53 +msgid "Show calendar weeks in the picker of date/datetime fields" +msgstr "Kalenderwochen im Datums-Auswahlfeld anzeigen" + +#: ../settings/system/frontend.rst:25 msgid "" -"To add these scripts in the Checkmk WATO, copy them into your Checkmk " -"installation directory and make them executable. (Be sure to replace the " -"``zammad.example.com`` callback URL with the one found in your admin panel.)" +"With this setting you can instruct Zammad to provide week number display " +"globally for all users. Calendar with week number display are usually used " +"in business sectors and may not be relevant for everyone." msgstr "" -"Um diese Skripte in das Checkmk-WATO einzufügen, kopieren Sie sie in Ihr " -"Checkmk-Installationsverzeichnis und machen sie ausführbar. (Stellen Sie " -"sicher, dass Sie die Callback-URL ``zammad.example.com`` durch Ihre " -"ersetzen, die Sie auch im Admin-Bereich finden.)" +"Mit dieser Einstellung können Sie Zammad die Kalenderwochen global für alle " +"Benutzer in entsprechenden Auswahlfeldern anzeigen lassen. Kalender mit " +"Wochennummern werden nur in manchen Geschäftsbereichen verwendet und sind " +"möglicherweise nicht für jeden relevant." -#: ../system/integrations/checkmk/setup-guide.rst:60 -msgid "Service notification" -msgstr "Service-Benachrichtigung" - -#: ../system/integrations/checkmk/setup-guide.rst:46 +#: ../settings/system/frontend.rst:29 msgid "" -"For updates on the status of the software running on your server (*e.g.,* " -"postgres)." +"This setting affects *all areas* - you'll also see week numbers in the admin " +"panel for e.g. triggers and macros." msgstr "" -"Für Updates des Status der Software, die auf Ihrem Server läuft (*z.B.* " -"Postgres)." +"Diese Einstellung wirkt sich auf *alle Bereiche* aus - Sie sehen die " +"Wochennummern auch im Verwaltungsbereich für z.B. Trigger und Makros." -#: ../system/integrations/checkmk/setup-guide.rst:75 -msgid "Host notification" -msgstr "Host-Benachrichtigung" +#: ../settings/system/frontend.rst:32 +msgid "Default: ``no`` (not shown)" +msgstr "Voreinstellung: ``nein`` (nicht angezeigt)" -#: ../system/integrations/checkmk/setup-guide.rst:63 -msgid "For updates on the status of the server itself." -msgstr "Für Updates zum Status des Servers selbst." +#: ../settings/system/frontend.rst:53 +msgid "Here's the difference:" +msgstr "Hier sehen Sie den Unterschied:" -#: ../system/integrations/checkmk/setup-guide.rst:77 -msgid "🤔 **What's with all the env vars?**" -msgstr "🤔 **Was ist mit all den env vars?**" +#: ../settings/system/frontend.rst:0 +msgid "Screenshot showing Zammad's date picker (in the default way)" +msgstr "Screenshot mit Datumsauswahl von Zammad (Standardeinstellung)" -#: ../system/integrations/checkmk/setup-guide.rst:79 -msgid "" -"Whenever Checkmk runs these scripts, it needs to provide some information " -"about the event that triggered the notification. This information is passed " -"in the form of these ``$NOTIFY_*`` environment variables." -msgstr "" -"Jedes Mal, wenn Checkmk diese Skripte ausführt, muss es einige Informationen " -"über das Ereignis, das die Benachrichtigung ausgelöst hat, bereitstellen. " -"Diese Informationen werden in Form der Umgebungsvariablen ``$NOTIFY_*`` " -"übergeben." +#: ../settings/system/frontend.rst:41 +msgid "Set to ``no``" +msgstr "Auf ``Nein`` gesetzt" -#: ../system/integrations/checkmk/setup-guide.rst:85 +#: ../settings/system/frontend.rst:0 msgid "" -"You can specify additional parameters to pass to the script when you're " -"setting up your notification rule, but the ones you see here are all " -"provided by default." +"Screenshot showing Zammad's date picker with\n" +"week numbers enabled" msgstr "" -"Sie können beim Einrichten Ihrer Benachrichtigungsregel zusätzliche " -"Parameter angeben, die an das Skript übergeben werden sollen, aber die hier " -"gezeigten sind alle standardmäßig vorhanden." +"Screenshot zeigt die Datumsauswahl von Zammad mit aktivierten Kalenderwochen" -#: ../system/integrations/checkmk/setup-guide.rst:90 -msgid "Email Alerts" -msgstr "E-Mail-Benachrichtigungen" +#: ../settings/system/frontend.rst:50 +msgid "Set to ``yes``" +msgstr "Auf ``Ja`` gesetzt" -#: ../system/integrations/checkmk/setup-guide.rst:94 +#: ../settings/system/index.rst:4 msgid "" -"🐞 **There are known bugs** in Zammad's processing of email from Checkmk. " -"This section will be completed once they have been resolved. (Learn more at " -"GitHub issues `#2377 `_ & " -"`#2180 `_.)" +"For your overview we split each tab within system settings into its own page:" msgstr "" -"🐞 **Es gibt bekannte Fehler** bei der Verarbeitung von E-Mails von Checkmk " -"durch Zammad. Dieser Abschnitt wird vervollständigt, sobald sie behoben " -"sind. (Erfahren Sie mehr unter GitHub issues `#2377 `_ & `#2180 `_.)" +"Der Übersicht halber haben wir jeden Tab der Systemeinstellungen in eine " +"eigene Seite aufgeteilt:" -#: ../system/integrations/checkmk/setup-guide.rst:100 -msgid "In the meantime, we encourage you to set up API alerts instead." +#: ../settings/system/index.rst:16 +msgid "Console Based Settings" +msgstr "Konsolenbasierte Einstellungen" + +#: ../settings/system/index.rst:18 +msgid "" +"There's some console based settings we didn't put into the UI. However, you " +"may find them helpful - you can find them in our :docs:`hidden settings ` section." msgstr "" -"In der Zwischenzeit empfehlen wir Ihnen, stattdessen API-Benachrichtigungen " -"einzurichten." +"Es gibt einige Konsolen-Einstellungen, die nicht in der Benutzeroberfläche " +"vorgenommen werden können. Falls Sie mehr dazu erfahren wollen können Sie " +"diese unter :docs:`versteckte Einstellungen` in der Systemdokumentation finden." -#: ../system/integrations/clearbit.rst:2 -msgid "Clearbit" -msgstr "Clearbit" +#: ../settings/system/network.rst:2 +msgid "Network" +msgstr "Netzwerk" -#: ../system/integrations/clearbit.rst:4 +#: ../settings/system/network.rst:8 msgid "" -"With our Clearbit integration, you can easily enrich the information " -"provided by Zammad. If the customers or agents email address is known to " -"Clearbit, it will share all information it has regarding the user with " -"Zammad. Those information can include the following:" +"The proxy settings can only be saved after successfully testing the proxy " +"connection." msgstr "" -"Mit unserer Clearbit-Integration können Sie die von Zammad bereitgestellten " -"Informationen ganz einfach erweitern. Wenn die E-Mail-Adresse des Kunden " -"oder Agenten Clearbit bekannt ist, wird es alle Informationen, die es über " -"den Benutzer hat, mit Zammad teilen. Die Informationen können Folgendes " -"umfassen:" +"Die Proxy-Einstellungen können erst nach erfolgreichem Testen der Proxy-" +"Verbindung gespeichert werden." -#: ../system/integrations/clearbit.rst:9 -msgid "Avatar" -msgstr "Avatar" +#: ../settings/system/network.rst:15 +msgid "Proxy Address." +msgstr "Proxy-Adresse." -#: ../system/integrations/clearbit.rst:10 -msgid "Address information" -msgstr "Informationen zur Adresse" +#: ../settings/system/network.rst:12 +msgid "" +"Allows you to provide a proxy server if needed. This is relevant for network " +"communication by Zammad." +msgstr "" +"Ermöglicht es Ihnen, bei Bedarf einen Proxyserver bereitzustellen. Dies ist " +"für die Netzwerkkommunikation von Zammad relevant." -#: ../system/integrations/clearbit.rst:11 -msgid "Website information" -msgstr "Informationen zur Website" +#: ../settings/system/network.rst:15 +msgid "It **does not** affect the update process or Elasticsearch." +msgstr "" +"Sie **beeinflusst nicht** den Aktualisierungsprozess und Elasticsearch." -#: ../system/integrations/clearbit.rst:12 -msgid "A BIO (as Note by default)" -msgstr "Eine Zusammenfassung der Biografie (standardmäßig als Notiz)" +#: ../settings/system/network.rst:18 +msgid "Username for proxy connection." +msgstr "Benutzername für Verbindung zum Proxy." -#: ../system/integrations/clearbit.rst:14 +#: ../settings/system/network.rst:18 msgid "" -"If needed, you can add further custom objects and add mappings to them, so " -"the Clearbit information can be filled within the database. In general you " -"can get any information from Clearbit, as long as you have a mapping to an " -"Zammad object." +"If your proxy server requires authentication, provide the username here." msgstr "" -"Bei Bedarf können Sie weitere benutzerdefinierte Objekte hinzufügen und " -"ihnen Mappings zuweisen. Generell können Sie alle Informationen von Clearbit " -"anzeigen lassen , solange Sie eine Zuordnung zu einem Zammad-Objekt-Atribut " -"eingerichtet haben." +"Wenn Ihr Proxyserver eine Authentifizierung erfordert, geben Sie hier den " +"Benutzernamen an." -#: ../system/integrations/clearbit.rst:21 +#: ../settings/system/network.rst:21 +msgid "Password for proxy connection." +msgstr "Passwort für Verbindung zum Proxy." + +#: ../settings/system/network.rst:21 msgid "" -"Clearbit does have a mapping of fields like LDAP and Exchange have, but does " -"not \"win\" against Zammad information. This means that if you have e.g. the " -"last name field filled in already and Clearbit has other information on " -"that, it will not be updated." +"If your proxy server requires authentication, provide the password here." msgstr "" -"Clearbit hat ein Mapping von Feldern wie LDAP und Exchange, aber es " -"überschreibt keine Zammad-Informationen. Das bedeutet, dass wenn Sie z.B. " -"das Feld für den Nachnamen in Zammad bereits ausgefüllt haben, es von " -"Clearbit nicht überschrieben wird, auch wenn dort andere Informationen " -"vorliegen." +"Wenn Ihr Proxyserver eine Authentifizierung erfordert, geben Sie hier das " +"Passwort ein." -#: ../system/integrations/clearbit.rst:26 +#: ../settings/system/network.rst:26 +msgid "No proxy for the following hosts." +msgstr "Keinen Proxy für die folgenden Hosts verwenden." + +#: ../settings/system/network.rst:24 msgid "" -"However: If let's say the last name has been set by Clearbit and Zammad " -"notices that the last name on the Clearbit source has changed, Zammad will " -"also update this value." +"Exception list for hosts you can't or don't want to reach via proxy server." msgstr "" -"Aber: Wenn der Nachname von Clearbit festgelegt wurde und Zammad feststellt, " -"dass sich der Nachname in der Clearbit-Quelle geändert hat, wird Zammad auch " -"diesen Wert aktualisieren." +"Ausnahmeliste für Hosts, die Sie nicht über den Proxyserver erreichen können " +"oder wollen." -#: ../system/integrations/clearbit.rst:33 -msgid "" -"The configuration of Clearbit is really easy and done fast! Just login to " -"your Clearbit-Account, go to \"API\" and copy the secret-API-Key." +#: ../settings/system/network.rst:27 +msgid "Default: ``localhost,127.0.0.0,::1``" +msgstr "Voreinstellung: ``localhost,127.0.0.0,::1``" + +#: ../settings/system/services.rst:2 +msgid "Services" +msgstr "Dienste" + +#: ../settings/system/services.rst:10 +msgid "Image Service" +msgstr "Bilder-Dienst" + +#: ../settings/system/services.rst:5 +msgid "Defines the backend for user and organization image lookups." msgstr "" -"Die Konfiguration von Clearbit ist wirklich einfach und schnell erledigt! " -"Loggen Sie sich einfach in Ihren Clearbit-Account ein, gehen Sie auf \"API\" " -"und kopieren Sie den geheimen API-Schlüssel." +"Definierte das Backend für Bildersuchen von Benutzern und Organisationen." -#: ../system/integrations/clearbit.rst:38 +#: ../settings/system/services.rst:7 +msgid "Default: ``Zammad Image Service`` (active)" +msgstr "Standard: ``Zammad Image Service`` (aktiv)" + +#: ../settings/system/services.rst:9 msgid "" -"Now change to your Zammad instance, go to Integrations (System) -> Clearbit " -"in the admin panel. Paste your API-Key into the API-Key-Field and decide if " -"Zammad should create unknown Organizations automatically, if the user does " -"not have one yet (and Clearbit knows it). The shared option decides if the " -"new organizations Zammad creates with Clearbit should be shared ones." +"Make sure your on premise installation has ``HTTPS`` access to ``images." +"zammad.com``." msgstr "" -"Wechseln Sie nun zu Ihrer Zammad-Instanz und gehen Sie im Admin-Bereich zu " -"Integrationen (System) > Clearbit. Fügen Sie Ihren API-Schlüssel in das API-" -"SchlüsselFeld ein und entscheiden Sie, ob Zammad automatisch unbekannte " -"Organisationen erstellen soll, wenn der Benutzer noch keine hat (und " -"Clearbit diese kennt). Die Option \"Geteilt\" legt fest, ob die neuen " -"Organisationen, die Zammad aus Clearbit erstellt, \"geteilt\" sein sollen." +"Stellen Sie sicher, dass Ihre Installation vor Ort per ``HTTPS`` Zugriff auf " +"``images.zammad.com`` hat." -#: ../system/integrations/clearbit.rst:47 +#: ../settings/system/services.rst:18 +msgid "Geo Calendar Service" +msgstr "Geo-Kalender-Dienst" + +#: ../settings/system/services.rst:13 msgid "" -"If you're unsure what option to choose, better stick with \"no\". You can " -"also learn more about :doc:`/manage/organizations/index`." +"Defines the backend for geo calendar lookups. Used for initial calendar " +"setup." msgstr "" -"Wenn Sie unsicher sind, welche Option Sie wählen sollen, bleiben Sie besser " -"bei \"nein\". Sie können mehr dazu unter :doc:`/manage/organizations/index` " -"erfahren." +"Definiert das Backend für Geo-Kalender-Lookups. Wird für die " +"Kalendereinrichtung verwendet." -#: ../system/integrations/clearbit.rst:52 +#: ../settings/system/services.rst:16 +msgid "Default: ``Zammad GeoCalendar Service`` (active)" +msgstr "Standard: ``Zammad GeoCalendar Service`` (aktiv)" + +#: ../settings/system/services.include.rst:2 msgid "" -"The Mapping option works similar to the mapping within the Exchange and LDAP " -"sync. You can add further mappings for e.g. custom fields if you need more " -"information that Clearbit can provide." +"Make sure your on premise installation has ``HTTPS`` access to ``geo.zammad." +"com``." msgstr "" -"Die Mapping-Option funktioniert ähnlich wie das Mapping innerhalb des " -"Exchange und LDAP Sync. Sie können weitere Mappings für z.B. " -"benutzerdefinierte Felder hinzufügen, wenn Sie weitere Informationen " -"benötigen, die Clearbit bereitstellen kann." +"Stellen Sie sicher, dass Ihre Installation vor Ort per ``HTTPS`` Zugriff auf " +"``geo.zammad.com`` hat." -#: ../system/integrations/clearbit.rst:58 -msgid "" -"If you want to add more Clearbit fields and want to learn more about " -"available fields on their API, you can take a look at their `API " -"documentation `_." -msgstr "" -"Wenn Sie weitere Clearbit-Felder hinzufügen möchten und mehr über die " -"verfügbaren Felder in der API erfahren möchten, können Sie einen Blick auf " -"deren `API-Dokumentation `_ werfen." +#: ../settings/system/services.rst:26 +msgid "Geo IP Service" +msgstr "Geo-IP-Service" -#: ../system/integrations/clearbit.rst:62 +#: ../settings/system/services.rst:21 msgid "" -"If you're happy with the above chosen Settings and your mapping, just save " -"the changes and enable Clearbit integration. Zammad will now start polling " -"the Clearbit API as users contact you." +"Defines the backend for geo IP lookups. Shows also location of an IP address " +"if an IP address is shown." msgstr "" -"Wenn Sie mit den oben gewählten Einstellungen und Ihrem Mapping zufrieden " -"sind, speichern Sie die Änderungen und aktivieren Sie die Clearbit-" -"Integration. Zammad wird nun die Clearbit-API abfragen, wenn Nutzer Sie " -"kontaktieren." +"Definiert das Backend für Geo-IP-Lookups. Zeigt auch den Standort einer IP-" +"Adresse an, wenn eine IP-Adresse angezeigt wird." -#: ../system/integrations/clearbit.rst:68 +#: ../settings/system/services.rst:24 +msgid "Default: ``Zammad GeoIP Service`` (active)" +msgstr "Voreinstellung: ``Zammad GeoIP Service`` (aktiv)" + +#: ../settings/system/services.rst:32 +msgid "Geo Location Service" +msgstr "Geo-Lokalisierungs-Service" + +#: ../settings/system/services.rst:29 msgid "" -"Zammad does not synchronize with Clearbit on a regular basis, but on demand " -"if needed. This saves API calls." +"Defines the backend for geo location lookups to store geo locations for " +"addresses." msgstr "" -"Zammad synchronisiert sich nicht regelmäßig mit Clearbit, sondern nur bei " -"Bedarf. Das spart API-Aufrufe." +"Definiert das Backend für Geo-Standortabfragen, um Geo-Standorte für IP-" +"Adressen zu speichern." -#: ../system/integrations/clearbit.rst:73 +#: ../settings/system/services.rst:32 msgid "" -"Below the Settings and Mappings, you'll find our Integration log. You can " -"see what requests Zammad sent to Clearbit and also the APIs Response." +"Default: ``OpenStreetMap (ODbL 1.0, http://osm.org/copyright)`` (active)" msgstr "" -"Unterhalb der Einstellungen und Zuordnungen finden Sie unser " -"Integrationsprotokoll. Sie können sehen, welche Anfragen Zammad an Clearbit " -"gesendet hat und auch die API-Antwort." +"Voreinstellung: ``OpenStreetMap (ODbL 1.0, http://osm.org/copyright)`` " +"(aktiv)" -#: ../system/integrations/clearbit.rst:78 +#: ../settings/system/services.rst:36 msgid "" -"By the way, you can also view the API log on the Clearbit website - the " -"information seen is basically the same." +"You can find a detailed privacy information on what we store for how long on " +"our :docs:`Privacy Appendix ` inside of our System " +"Documentation." msgstr "" -"Übrigens können Sie das API-Protokoll auch auf der Clearbit-Website einsehen " -"- die Informationen sind im Grunde die gleichen." +"Detaillierte Informationen zum Datenschutz, was wir wie lange speichern, " +"finden Sie in unserem :docs:`Datenschutzhinweisen ` " +"in unserer Systemdokumentation." -#: ../system/integrations/clearbit.rst:84 -msgid "Example When Adding a User" -msgstr "Beispiel für das Hinzufügen eines Benutzers" +#: ../settings/system/storage.rst:2 +msgid "Storage" +msgstr "Speicher" -#: ../system/integrations/clearbit.rst:86 +#: ../settings/system/storage.rst:6 msgid "" -"To show you how fast information is added, we added a small Screencast " -"below. This shows the creation of the User Alex from Clearbit. As we already " -"set the last name of Alex to \"X\", Zammad did not update it. What Zammad " -"did was to add further information it received from Clearbit." +"Here you can define where Zammad stores attachments for tickets and the " +"knowledge base. By default, we're writing to the ``Database`` - you can " +"switch to ``Filesystem`` or ``Simple Storage (S3)`` at any time. In this " +"case please have a look on the following instructions." msgstr "" -"Um Ihnen zu zeigen, wie schnell Informationen hinzugefügt werden, haben wir " -"unten einen kleinen Screencast eingefügt. Dieser zeigt die Erstellung des " -"Benutzers Alex aus Clearbit. Da wir den Nachnamen von Alex bereits auf \"X\" " -"gesetzt haben, hat Zammad ihn nicht aktualisiert. Zammad hat weitere " -"Informationen hinzuzufügt, die es von Clearbit erhalten hatte." - -#: ../system/integrations/cti/generic.rst:2 -msgid "CTI (generic)" -msgstr "CTI (allgemein)" +"Hier können Sie festlegen, wo Zammad Anhänge für Tickets und die Knowledge " +"Base speichert. Standardmäßig wird die ``Datenbank`` dafür verwendet - Sie " +"können jederzeit auf ``Dateisystem`` oder ``Simple Storage (S3)`` " +"umschalten. Schauen Sie sich dazu bitte die folgende Anleitung an." -#: ../system/integrations/cti/includes/introduction.include.rst:1 +#: ../settings/system/storage.rst:11 msgid "" -"This integration enables Zammad to provide a caller log to your agents. With " -"this your agents can greet your customers by their name and are supported by " -"Zammad with automatically opening a new ticket dialog or the user profile." +"If you have a busy Zammad instance, we strongly encourage you to use " +"filesystem storage instead of \"Database\". This will greatly improve system " +"performance (de-crease database load and size)." msgstr "" -"Diese Integration ermöglicht es Zammad, Ihren Agenten eine Anruferliste zur " -"Verfügung zu stellen. Damit können Ihre Agenten Ihre Kunden mit ihrem Namen " -"begrüßen und werden von Zammad duruch ein automatisches Öffnen eines Ticket-" -"Erstell-Dialogs oder des Benutzerprofils unterstützt." +"Wenn Sie eine ausgelastete Zammad-Instanz haben, empfehlen wir Ihnen " +"dringend, \"Dateisystem\" anstelle von \"Datenbank\" als Speichermethode zu " +"verwenden. Dies wird die Systemleistung erheblich verbessern (Verringerung " +"der Datenbanklast und -größe)." -#: ../system/integrations/cti/includes/introduction.include.rst:6 +#: ../settings/system/storage.rst:19 +msgid "Database" +msgstr "Datenbank" + +#: ../settings/system/storage.rst:17 msgid "" -"Click the toggle next to the heading to activate or deactivate this " -"integration." +"This is the default storage method. The attachments are stored directly in " +"the database. If your Zammad instance grows, we recommend one of the other " +"methods to maintain performance." msgstr "" -"Klicken Sie auf Schalter neben der Überschrift ``Placetel``, um diese " -"Integration zu aktivieren oder zu deaktivieren." +"Dies ist die Standard-Speichermethode. Die Anhänge werden direkt in der " +"Datenbank gespeichert. Wenn Ihre Zammad-Instanz wächst, empfehlen wir eine " +"der anderen Methoden, um keine Einschränkungen bzgl. Leistung zu bekommen." -#: ../system/integrations/cti/includes/introduction.include.rst:9 +#: ../settings/system/storage.rst:38 +msgid "Filesystem" +msgstr "Dateisystem" + +#: ../settings/system/storage.rst:22 msgid "" -"If you want to learn more on how your agents can use this function, please " -"refer the :user-docs:`user documentation `." +"This storage method is recommended for all Zammad instances, especially for " +"those with a higher load. If you choose filesystem, your files are written " +"to ``/opt/zammad/storage/``." msgstr "" -"Wenn Sie mehr darüber erfahren möchten, wie Ihre Agenten diese Funktion " -"nutzen können, lesen Sie bitte die :user-docs:`Benutzerdokumentation `." +"Diese Speichermethode wird für alle Zammad-Instanzen empfohlen, insbesondere " +"für solche mit einer höheren Last. Wenn Sie Dateisystem wählen, werden Ihre " +"Dateien nach ``/opt/zammad/storage/`` geschrieben." -#: ../system/integrations/cti/includes/introduction.include.rst:14 +#: ../settings/system/storage.rst:26 msgid "" -"Automatically opening new ticket dialogues or user profiles requires agent " -"to extension mapping - see more below." +"Moving attachments from \"Database\" to \"Filesystem\" can be run during " +"production use. However, you should consider your framework conditions (e.g. " +"bandwidth, system load in production) to define the right moment." msgstr "" -"Das automatische Öffnen von Ticket-Erstell-Dialogen oder Benutzerprofilen " -"erfordert eine Zuordnung von Agenten in der CTI-Integration - siehe unten." +"Das Verschieben von Anhängen aus der Datenbank in das Dateisystem kann " +"während des Betriebs von Zammad durchgeführt werden. Sie sollten jedoch Ihre " +"Rahmenbedingungen (z.B. Bandbreite, Systemlast in der Produktion) " +"berücksichtigen, um den richtigen Zeitpunkt zu bestimmen." -#: ../system/integrations/cti/includes/introduction.include.rst:20 -msgid "Please note the following limitations to reduce confusion later on:" +#: ../settings/system/storage.rst:32 +msgid "**You noticed slow updates of Zammad?**" +msgstr "**Haben Sie langsame Aktualisierungen von Zammad festgestellt?**" + +#: ../settings/system/storage.rst:34 +msgid "" +"While Zammad is beeing updated, it enforces a recursive \"change " +"owner\" (chown) for this directory. For instances with many files this can " +"be time consuming. To mitigate that you can move your files and create a " +"symlink in ``/opt/zammad/storage/`` to the new directory. Of course you have " +"to make sure on your own that the permissions are always correct." msgstr "" -"Bitte beachten Sie die folgenden Einschränkungen, um spätere Unklarheiten zu " -"vermeiden:" +"Während Zammad aktualisiert wird, wird das ganze Verzeichnis rekursiv per " +"\"change owner\" (chown) aktualisiert. Für Instanzen mit vielen Dateien kann " +"dies sehr zeitaufwendig sein. Um das zu vermeiden, können Sie Ihre Dateien " +"verschieben und eine symbolische Verlinkung (Symlink) in ``/opt/zammad/" +"storage/`` auf das neue Verzeichnis erstellen. Natürlich müssen Sie dann " +"selbst dafür sorgen, dass die Berechtigungen immer korrekt sind." -#: ../system/integrations/cti/includes/introduction.include.rst:22 -msgid "CTI integrations provide caller log functions only." -msgstr "Die CTI-Integration bieten nur Anruferprotokoll-Funktionen." +#: ../settings/system/storage.rst:95 +msgid "Simple Storage (S3)" +msgstr "Simple Storage (S3)" -#: ../system/integrations/cti/includes/introduction.include.rst:23 +#: ../settings/system/storage.rst:41 msgid "" -"This integration does not provide any VoIP functionalities; you can't make " -"phone calls from within Zammad." +"To use the Simple Storage (S3), you have to provide some settings, which " +"can't be accessed in the UI (see instructions below)." msgstr "" -"Diese Integration bietet keine VoIP-Funktionen; Sie können von Zammad aus " -"keine Telefonanrufe tätigen." +"Um Simple Storage (S3) zu nutzen, müssen Sie einige Einstellungen vornehmen, " +"die nicht über die Benutzeroberfläche zugänglich sind (siehe Anleitung " +"unten)." -#: ../system/integrations/cti/includes/introduction.include.rst:25 +#: ../settings/system/storage.rst:44 msgid "" -"If your browser supports ``tel``-URLs, you can click on phone numbers for " -"automatic dialing. This requires additional software / configuration on your " -"agent's computers." +"⚠️ Please note that the current implementation is in its early stages and can " +"be modified in the future." msgstr "" -"Wenn Ihr Browser ``tel``-URLs unterstützt, können Sie auf Telefonnummern " -"klicken, um sie automatisch zu wählen. Dies erfordert zusätzliche Software/" -"Konfiguration auf den Computern Ihrer Mitarbeiter." - -#: ../system/integrations/cti/generic.rst:9 -#: ../system/integrations/cti/placetel.rst:14 -#: ../system/integrations/cti/sipgate.rst:14 -msgid "Please provide the following requirements:" -msgstr "Folgende Anforderungen müssen erfüllt sein:" +"⚠️ Bitte beachten Sie, dass sich die derzeitige Umsetzung noch im " +"Anfangsstadium befindet und sich in Zukunft Änderungen ergeben können." -#: ../system/integrations/cti/generic.rst:11 +#: ../settings/system/storage.rst:47 msgid "" -"A telephone system that supports webhooks (outbound) (best option are those " -"that allow customizing the calls)." +"The prerequisite is to have access to a S3-compatible storage and to have " +"all necessary parameters available (which depends on your storage provider; " +"if in doubt, please ask there for help)." msgstr "" -"Eine Telefonanlage, die Webhooks (ausgehend) unterstützt (am besten solche, " -"die eine individuelle Anpassung der Anrufe ermöglichen)." - -#: ../system/integrations/cti/generic.rst:13 -msgid "A unique Call-ID during the call session." -msgstr "Eine eindeutige Call-ID während der Gesprächssitzung." - -#: ../system/integrations/cti/generic.rst:14 -msgid "Call event data (both numbers and direction)." -msgstr "Daten zu Anrufereignissen (sowohl Nummern als auch Richtung)." +"Voraussetzung ist, dass Sie Zugang zu einem S3-kompatiblen Speicher haben " +"und alle notwendigen Parameter vorliegen (das hängt von Ihrem " +"Speicheranbieter ab; im Zweifelsfall fragen Sie bitte dort nach)." -#: ../system/integrations/cti/generic.rst:15 -msgid "Your Zammad instance must be reachable for your telephony system." -msgstr "Ihre Zammad-Instanz muss für Ihr Telefonsystem erreichbar sein." +#: ../settings/system/storage.rst:51 +msgid "Steps to configure S3:" +msgstr "Schritte zur Konfiguration von S3:" -#: ../system/integrations/cti/generic.rst:17 +#: ../settings/system/storage.rst:53 msgid "" -"If you want to learn more on what kind of requests are supported by Zammad " -"and what it expects, please consult our :docs:`CTI-API documentation `." +"Copy ``config/zammad/storage.yml.dist`` to ``config/zammad/storage.yml``" msgstr "" -"Wenn Sie mehr darüber erfahren möchten, welche Arten von Anfragen von Zammad " -"unterstützt werden und welche Daten erwartet werden, konsultieren Sie bitte " -"unsere :docs:`CTI-API Dokumentation `." +"Kopieren Sie ``config/zammad/storage.yml.dist`` nach ``config/zammad/storage." +"yml``" -#: ../system/integrations/cti/generic.rst:22 -#: ../system/integrations/cti/placetel.rst:27 -#: ../system/integrations/cti/sipgate.rst:30 -msgid "Available Settings" -msgstr "Verfügbare Einstellungen" - -#: ../system/integrations/cti/generic.rst:29 -#: ../system/integrations/cti/placetel.rst:41 -#: ../system/integrations/cti/sipgate.rst:40 -msgid "Endpoint Settings" -msgstr "Endpunkt-Einstellungen" +#: ../settings/system/storage.rst:54 +msgid "Edit the copied file in one of the following ways:" +msgstr "Bearbeiten Sie die kopierte Datei auf eine der folgenden Arten:" -#: ../system/integrations/cti/generic.rst:25 +#: ../settings/system/storage.rst:56 msgid "" -"Zammad will list your generic CTI endpoint here. It contains a unique token " -"so ensure to keep this URL save." +"Either provide your S3 configuration with one attribute per line like in the " +"upper area of the file" msgstr "" -"Zammad listet hier Ihren generischen CTI-Endpunkt auf. Er enthält ein " -"eindeutiges Token. Bitte achten Sie darauf, die URL möglichst geheim zu " -"halten." +"Entweder Sie erstellen Ihre S3-Konfiguration mit einem Attribut pro Zeile " +"wie im oberen Bereich der Datei" -#: ../system/integrations/cti/generic.rst:28 +#: ../settings/system/storage.rst:58 msgid "" -"You'll need this endpoint for your PBX to talk to Zammad, see :docs:`CTI-API " -"documentation `." +"Or provide your S3 configuration as an URL (which you can find at the end of " +"the file). Note: you can also provide this URL as environment variable (:" +"docs:`see system documentation `) without using this yml-file." msgstr "" -"Sie benötigen diesen Endpunkt für Ihre Telefonanlage, um mit Zammad zu " -"sprechen, siehe :docs:`CTI-API Dokumentation `." +"Oder Sie geben Ihre S3-Konfiguration als URL an (die Sie am Ende der Datei " +"finden). Hinweis: Sie können diese URL auch als Umgebungsvariable angeben (:" +"docs:`siehe System Documentation `) , ohne diese yml-Datei zu verwenden." -#: ../system/integrations/cti/includes/important-dont-forget-saving.include.rst:3 +#: ../settings/system/storage.rst:62 msgid "" -"All following options **do not save automatically**. Always use the Save " -"button on the lower end of the integration page!" +"We recommend the deletion of the not used configuration style to avoid " +"inconsistencies." msgstr "" -"Alle folgenden Optionen werden **nicht automatisch gespeichert**. Verwenden " -"Sie immer die Schaltfläche \"Speichern\" am unteren Ende der Seite!" - -#: ../system/integrations/cti/generic.rst:43 -#: ../system/integrations/cti/placetel.rst:49 -#: ../system/integrations/cti/sipgate.rst:52 -msgid "Call Settings" -msgstr "Anruf-Einstellungen" +"Wir empfehlen die Löschung der nicht verwendeten Konfiguration, um " +"Inkonsistenzen zu vermeiden." -#: ../system/integrations/cti/generic.rst:39 -#: ../system/integrations/cti/placetel.rst:49 -#: ../system/integrations/cti/sipgate.rst:37 -#: ../system/integrations/cti/sipgate.rst:50 -msgid "Inbound" -msgstr "Eingehend" +#: ../settings/system/storage.rst:65 +msgid "Restart Zammad so the config file / environment variable is loaded" +msgstr "" +"Zammad neu starten, damit die Konfigurationsdatei / Umgebungsvariable " +"geladen wird" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:1 +#: ../settings/system/storage.rst:66 msgid "" -"This option allows you to block specific incoming caller IDs. It allows you " -"to temporarily reject e.g. spam callers without having to contact providers " -"or PBX administrators." +"Set the \"Storage Method\" in Zammad to ``Simple Storage (S3)`` in Settings " +"> System > Storage and click on \"Submit\". After that, Zammad checks your " +"configuration and the connection to the service and will raise an error " +"message if something is wrong." msgstr "" -"Mit dieser Option können Sie bestimmte eingehende Anrufer-IDs blockieren. So " -"können Sie z.B. Spam-Anrufer vorübergehend abweisen, ohne dass Sie sich an " -"Ihren Provider oder PBX-Administrator wenden müssen." - -#: ../system/integrations/cti/includes/inbound-calls.include.rst:11 -msgid "Caller ID to block" -msgstr "Zu blockierende Caller-ID" +"Setzen Sie die \"Speichermethode\" in Zammad auf ``Simple Storage (S3)`` in " +"Einstellungen > System > Speicher und klicken Sie auf \"Übermitteln\". " +"Danach überprüft Zammad Ihre Konfiguration und die Verbindung zum Dienst und " +"gibt eine Fehlermeldung aus, wenn etwas nicht stimmt." -#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 -msgid "Provide caller IDs to block in ``E.164`` format." -msgstr "Geben Sie die zu blockierenden Anrufer-IDs im Format ``E.164`` an." +#: ../settings/system/storage.rst:72 +msgid "A very simple storage configuration could look like this:" +msgstr "Eine sehr einfache Speicherkonfiguration könnte wie folgt aussehen:" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:8 +#: ../settings/system/storage.rst:85 msgid "" -"Your telephony system has to support this function. Zammad will send a " -"``reject`` response which will cause your telephony system to hang up the " -"call. To callers this usually will feel like the line is busy." +"Before setting the storage method to ``Simple Storage (S3)`` (step 4), " +"please make sure to have a working setup." msgstr "" -"Ihr Telefonsystem muss diese Funktion unterstützen. Zammad sendet eine " -"``Abweisen``-Antwort, die Ihr Telefonsystem veranlasst, den Anruf " -"aufzulegen. Für den Anrufer sieht das normalerweise so aus, als ob die " -"Leitung besetzt wäre." +"Bevor Sie die Speichermethode auf ``Simple Storage (S3)`` einstellen " +"(Schritt 4), stellen Sie bitte sicher, dass Sie ein funktionierendes Setup " +"haben." -#: ../system/integrations/cti/includes/inbound-calls.include.rst:14 +#: ../settings/system/storage.rst:88 msgid "" -"Provide a meaningful note for your fellow administrators to remind yourself " -"why you've chosen to block the number." +"You can verify this by running ``rails r 'Rails.logger = Logger.new(STDOUT); " +"pp Store::Provider::S3.ping?'`` in your Zammad directory. If everything is " +"fine, you should see ``true``, else you should see ``false`` and a simple " +"error message." msgstr "" -"Verfassen Sie eine aussagekräftige Notiz für Ihre Kollegen, warum Sie die " -"Nummer gesperrt haben." - -#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 -#: ../system/integrations/cti/includes/outbound-calls.include.rst:17 -#: ../system/integrations/cti/sipgate.rst:40 -msgid "Outbound" -msgstr "Ausgehend" +"Sie können dies überprüfen, indem Sie ``rails r 'Rails.logger = Logger." +"new(STDOUT); pp Store::Provider::S3.ping?'`` in Ihrem Zammad Verzeichnis " +"ausführen. Wenn alles in Ordnung ist, wird ein ``true`` ausgegeben, " +"ansonsten wird ``false`` und eine einfache Fehlermeldung ausgegeben." -#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:1 +#: ../settings/system/storage.rst:93 msgid "" -"In many cases you may want to use a different caller ID depending on the " -"destination you're calling. This may apply due to specific connection rates " -"to other countries or because you want your customer to feel you're calling " -"from the same country." +"If you installed Zammad through a package manager (rather than from source), " +"replace ``rails r`` with ``zammad run rails r`` above. To learn more, see :" +"docs:`Administration via Console `." msgstr "" -"In vielen Fällen ist es sinnvoll, je nach Zielland eine andere Anrufer-ID zu " -"verwenden. Dies kann aufgrund spezieller Verbindungstarife in andere Länder " -"der Fall sein oder weil Sie Ihren Kunden das Gefühl geben wollen, dass Sie " -"aus demselben Land anrufen." - -#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:6 -msgid "This option expects ``E.164`` number formats." -msgstr "Diese Option erwartet ``E.164`` Nummernformate." - -#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 -msgid "Destination caller ID" -msgstr "Ziel-Caller-ID" - -#: ../system/integrations/cti/includes/outbound-calls.include.rst:5 -msgid "The caller ID or number you're trying to call." -msgstr "Die Anrufer-ID oder die Nummer, die Sie anzurufen versuchen." +"Sofern Sie Zammad über einen Paketmanager (keine Source-Installation) " +"installiert haben, ersetzen Sie ``rails r`` mit ``zammad run rails r``. Für " +"weitere Information siehe :docs:`Administration via Konsole `." -#: ../system/integrations/cti/includes/outbound-calls.include.rst:7 -msgid "You can use wildcards for e.g. country specific outbound numbers like:" +#: ../settings/ticket.rst:4 +msgid "" +"Here you can adjust general ticket settings. Additional ones for the ticket " +"composer interface can be found in the :doc:`/misc/composer`." msgstr "" -"Sie können Platzhalter für z.B. länderspezifische ausgehende Nummern " -"verwenden, wie:" - -#: ../system/integrations/cti/includes/outbound-calls.include.rst:9 -msgid "``49*`` for Germany" -msgstr "``49*`` für Deutschland" +"Hier können Sie allgemeine Einstellungen für Tickets vornehmen. Zusätzliche " +"Einstellungen finden Sie im :doc:`/misc/composer`." -#: ../system/integrations/cti/includes/outbound-calls.include.rst:10 -msgid "``4930*`` for Berlin / Germany landlines" -msgstr "``4930*`` für Berlin / Deutschland Festnetze" +#: ../settings/ticket.rst:11 +msgid "Ticket Hook (default: ``Ticket#``)" +msgstr "Ticket-Hook (Standard: ``Ticket#``)" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 -msgid "``33*`` for France" -msgstr "``33*`` für Frankreich" +#: ../settings/ticket.rst:11 +msgid "The identifier for a ticket; *e.g.,* Ticket#, Call#, MyTicket#." +msgstr "Die Bezeichnung für ein Ticket; *z.B.* Ticket#, Anruf#, MeinTicket#." -#: ../system/integrations/cti/includes/outbound-calls.include.rst:15 -msgid "Set Outbound caller ID" -msgstr "Ausgehende Anrufer-ID einstellen" +#: ../settings/ticket.rst:38 +msgid "Ticket Hook Position (default: ``right``)" +msgstr "Position des Ticket-Hooks (Standard: ``rechts``)" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:14 +#: ../settings/ticket.rst:14 msgid "" -"The outbound caller ID to set (the number your customer sees on his display) " -"in ``E.164`` number format." +"With this setting you can decide (if) where to insert the ticket number." msgstr "" -"Die ausgehende Anrufer-ID (die Nummer, die Ihr Kunde auf seinem Display " -"sieht) im Format ``E.164``." +"Mit dieser Einstellung können Sie festlegen, ob und wo die Ticketnummer " +"eingefügt werden soll." -#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 -msgid "Provide a short description for fellow administrators." -msgstr "Geben Sie eine kurze Beschreibung für andere Administratoren." +#: ../settings/ticket.rst:20 +msgid "*Right*" +msgstr "*Rechts*" -#: ../system/integrations/cti/includes/generic-cti-support-note.includes.rst:3 +#: ../settings/ticket.rst:17 msgid "" -"This option requires your PBX to send a specific request to Zammad *before " -"dialing*. Please consult the :docs:`CTI API ` in case " -"you're not sure." +"This setting will add the ticket reference on the right site of the subject." msgstr "" -"Diese Option erfordert, dass Ihre Telefonanlage eine spezielle Anfrage *vor " -"dem Wählen* an Zammad sendet. Bitte konsultieren Sie die :docs:`CTI API `, falls Sie sich nicht sicher sind." +"Mit dieser Einstellung wird die Ticketreferenz auf der rechten Seite des " +"Betreffs hinzugefügt." -#: ../system/integrations/cti/generic.rst:52 -#: ../system/integrations/cti/placetel.rst:54 -#: ../system/integrations/cti/sipgate.rst:59 -msgid "Other Settings" -msgstr "Andere Einstellungen" +#: ../settings/ticket.rst:20 +msgid "Example: ``Some Subject [Ticket#12345]``" +msgstr "Beispiel: ``Ein Betreff [Ticket#12345]``" -#: ../system/integrations/cti/includes/other-settings-intro.include.rst:1 +#: ../settings/ticket.rst:26 +msgid "*Left*" +msgstr "*Links*" + +#: ../settings/ticket.rst:23 msgid "" -"Below you can find all available additional settings for this CTI " -"integration. For your overview we're sorting them by appearance and " -"reference their description first." +"This setting will add the ticket reference on the left site of the subject." msgstr "" -"Nachfolgend finden Sie alle verfügbaren zusätzlichen Einstellungen für die " -"CTI-Integration. Sie sind sortiert nach dem Auftreten in der Admin-" -"Oberfläche in Zammad." +"Mit dieser Einstellung wird die Ticketreferenz auf der linken Seite des " +"Betreffs hinzugefügt." -#: ../system/integrations/cti/includes/default-caller-id.include.rst:2 -#: ../system/integrations/cti/includes/default-caller-id.include.rst:1 -msgid "Default caller ID for outbound calls" -msgstr "Standard-Rufnummer für ausgehende Anrufe" +#: ../settings/ticket.rst:26 +msgid "Example: ``[Ticket#12345] Some Subject``" +msgstr "Beispiel: ``[Ticket#12345] Ein Betreff``" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:16 -#: ../system/integrations/cti/includes/records-caller-log.include.rst:15 -msgid "Shown records in caller log" -msgstr "Anzahl der Einträge im Anrufprotokoll" +#: ../settings/ticket.rst:29 +msgid "*None*" +msgstr "*Keine*" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:2 +#: ../settings/ticket.rst:29 +msgid "This will completely remove ticket references from the subject." +msgstr "Dies entfernt vollständige Ticket-Referenzen aus dem Betreff." + +#: ../settings/ticket.rst:33 msgid "" -"Allows you to set the number of shown caller log entries for all users. You " -"can choose from the following values:" +"Please ensure to take a look at :doc:`/channels/email/settings` within the " +"email channel to ensure you have at least one reference that helps Zammad to " +"assign follow-ups correctly." msgstr "" -"Ermöglicht es Ihnen, die Anzahl der angezeigten Anruf-Protokolleinträge für " -"alle Benutzer festzulegen. Sie können zwischen den folgenden Werten wählen:" - -#: ../system/integrations/cti/includes/records-caller-log.include.rst:5 -msgid "60 (default)" -msgstr "60 (Standard)" - -#: ../system/integrations/cti/includes/records-caller-log.include.rst:6 -msgid "120" -msgstr "120" - -#: ../system/integrations/cti/includes/records-caller-log.include.rst:7 -msgid "180" -msgstr "180" - -#: ../system/integrations/cti/includes/records-caller-log.include.rst:8 -msgid "240" -msgstr "240" - -#: ../system/integrations/cti/includes/records-caller-log.include.rst:9 -msgid "300" -msgstr "300" - -#: ../system/integrations/cti/includes/records-caller-log.include.rst:11 -msgid "**🥵 Potential performance issue**" -msgstr "**🥵 Mögliches Performance-Problem**" +"Bitte werfen Sie vorab einen Blick auf :doc:`/channels/email/settings` " +"innerhalb des E-Mail-Kanals und stellen sicher, dass Sie mindestens eine " +"Referenz für die Zuordnung von Tickets bei Rückfragen eingerichtet haben." -#: ../system/integrations/cti/includes/records-caller-log.include.rst:13 +#: ../settings/ticket.rst:37 msgid "" -"Setting this setting higher than 60 may cause serious performance issues on " -"very busy instances. Keep in mind that this setting causes Zammad to poll " -"and send up to 300 records to *all active agent sessions* in very short time " -"periods." +"Disabling this and not setting up any further follow up search will lead to " +"unexpected results!" msgstr "" -"Wenn Sie diese Einstellung auf mehr als 60 setzen, kann dies bei sehr stark " -"ausgelasteten Instanzen zu ernsthaften Performance-Problemen führen. " -"Beachten Sie, dass diese Einstellung bewirkt, dass Zammad in sehr kurzen " -"Zeiträumen bis zu 300 Datensätze bei *allen aktiven Agentensitzungen* " -"anfragt und sendet." - -#: ../system/integrations/cti/generic.rst:73 -msgid "Caller Log Filter" -msgstr "Anrufprotokoll-Filter" +"Wenn Sie diese Funktion deaktivieren und keine andere Zuordnung eingerichtet " +"haben, wird dies zu unerwarteten Ergebnissen führen!" -#: ../system/integrations/cti/generic.rst:55 +#: ../settings/ticket.rst:65 msgid "" -"This function allows you to provide call information based on e.g. queues " -"only to agents that really need the information." +"Ticket Last Contact Behaviour (default: ``Use the start time of the last " +"customer thread (which may consist of multiple articles).``)" msgstr "" -"Mit dieser Funktion können Sie Anrufprotokolle basierend auf Warteschleifen " -"oder Nummern nur den Agenten zur Verfügung stellen, die diese Informationen " -"wirklich benötigen." +"Verhalten der Aktualisierung des letzter Kundenkontakts (Standard: " +"``Verwenden Sie die Startzeit des letzten Kunden-Threads (der aus mehreren " +"Artikeln bestehen kann).``)" -#: ../system/integrations/cti/generic.rst:58 +#: ../settings/ticket.rst:41 msgid "" -"Why? If you have a team for several countries or departments, you don't want " -"to bug your agents from other departments. Leaving these options empty will " -"fallback to showing everything to everyone." +"This setting changes the way Zammad updates the ``Last Contact`` value of a " +"ticket. This is fairly important for overviews and what you expect upon " +"ticket updates of a customer." msgstr "" -"Warum? Wenn Sie ein Team für mehrere Länder oder Abteilungen haben, möchten " -"Sie nicht, dass Ihre Mitarbeiter aus anderen Abteilungen gestört werden. " -"Wenn Sie diese Optionen leer lassen, wird wieder alles für alle angezeigt." - -#: ../system/integrations/cti/generic.rst:64 -msgid "Destination caller ID or Queue" -msgstr "Ziel-Caller-ID oder Queue" +"Diese Einstellung ändert die Art und Weise, wie Zammad den ``Letzten " +"Kontakt`` eines Tickets aktualisiert. Dies ist wichtig für Übersichten und " +"für das Verhalten bei Ticketaktualisierungen." -#: ../system/integrations/cti/generic.rst:63 +#: ../settings/ticket.rst:52 msgid "" -"This depends on your PBX and usually is either a queue ID, phone number or " -"extension." +"Use the start time of the last customer thread (which may consist of " +"multiple articles)." msgstr "" -"Dies hängt von Ihrer Telefonanlage ab und ist in der Regel entweder eine " -"Warteschlangen-ID, eine Telefonnummer oder eine Durchwahl." - -#: ../system/integrations/cti/generic.rst:69 -msgid "Agents" -msgstr "Agenten" +"Verwenden Sie die Startzeit des letzten Kunden-Threads (der aus mehreren " +"Artikeln bestehen kann)." -#: ../system/integrations/cti/generic.rst:67 +#: ../settings/ticket.rst:46 msgid "" -"Select the agents that are responsible for the group. These agents will then " -"see caller log entries and call notifications fitting to said queue." +"If this option is chosen, Zammad will update the last updated value just " +"once if a customer replies. After that, Zammad will wait for an agent to " +"react." msgstr "" -"Wählen Sie die Agenten aus, die für die Gruppe zuständig sind. Diese Agenten " -"sehen dann Anruferprotokolle und Anrufbenachrichtigungen, die zu dieser " -"Warteschleife gehören." +"Wenn diese Option gewählt wird, wird Zammad den zuletzt aktualisierten Wert " +"nur einmal aktualisieren, wenn ein Kunde antwortet. Danach wartet Zammad auf " +"die Reaktion eines Agenten." -#: ../system/integrations/cti/generic.rst:0 +#: ../settings/ticket.rst:50 msgid "" -"Screenshot showing the caller log filter table with pre filled sample data" +"This comes in handy if you want to work tickets in the order of their first " +"update. This will not change ticket orders if customers decide to \"bump\" " +"the ticket affected." msgstr "" -"Screenshot der Anrufprotokoll-Filtertabelle mit vorausgefüllten Beispieldaten" +"Dies ist praktisch, wenn Sie Tickets in der Reihenfolge ihrer ersten " +"Aktualisierung bearbeiten möchten. Die Reihenfolge der Tickets ändert sich " +"nicht, wenn die Kunden beschließen, das Ticket mit einer erneuten Rückfrage " +"zu aktualisieren." -#: ../system/integrations/cti/includes/recent-logs.include.rst:6 -msgid "" -"With recent logs Zammad allows you to view the latest calls for the CTI " -"functionality. This usually comes in handy, when you're looking for errors." -msgstr "" -"Mit den \"Aktuellsten Protokollen\" ermöglicht es Zammad Ihnen, die letzten " -"Anrufe für die CTI-Integration zu sehen. Das kann im Fehlerfall hilfreich " -"sein." +#: ../settings/ticket.rst:57 +msgid "Use the time of the very last customer article." +msgstr "Verwenden Sie den Zeitpunkt des allerletzten Kundenartikels." -#: ../system/integrations/cti/includes/recent-logs.include.rst:0 +#: ../settings/ticket.rst:55 msgid "" -"Screenshot showing several incoming requests within Recent logs section." +"When setting this option, Zammad will always update the last updated value. " +"This means that if ordering by ``Last Update``, ticket orders will change if " +"customers \"bump\" the ticket." msgstr "" -"Screenshot mit mehreren eingehenden Anfragen im Abschnitt \"Aktuellste " -"Protokolle\"." +"Wenn diese Option gesetzt ist, wird Zammad immer den Wert der letzten " +"Aktualisierung verwenden. Die Reihenfolge der Tickets ändert sich, wenn die " +"Kunden beschließen, das Ticket mit einer erneuten Rückfrage zu aktualisieren." -#: ../system/integrations/cti/includes/recent-logs.include.rst:16 -msgid "I'm just here to clear floats up." -msgstr "Ich bin nur ein Hilfskonstrukt." +#: ../settings/ticket.rst:64 +msgid "Last contact value used on :doc:`/manage/overviews`" +msgstr "Letzter Kontakt für :doc:`/manage/overviews` verwendet" -#: ../system/integrations/cti/includes/recent-logs.include.rst:20 +#: ../settings/ticket.rst:65 +msgid "Last contact value used on :doc:`/manage/trigger`" +msgstr "Letzter Kontakt für :doc:`/manage/trigger` verwendet" + +#: ../settings/ticket.rst:88 msgid "" -"By clicking on the entry of interest, Zammad will provide more details on " -"the call in question. You'll see the payload it received and also the " -"response that was sent." +"Ticket Organization Reassignment (default: ``Update the most recent tickets." +"``)" msgstr "" -"Wenn Sie auf den gewünschten Eintrag klicken, zeigt Zammad weitere " -"Einzelheiten zu dem betreffenden Anruf an. Sie sehen dann den empfangenen " -"Payload und die gesendete Antwort." +"Neuzuweisung der Ticket-Organisation (Voreinstellung: ``Die neuesten Tickets " +"aktualisieren.``)" -#: ../system/integrations/cti/includes/recent-logs.include.rst:0 +#: ../settings/ticket.rst:68 msgid "" -"Screenshot showing detailed information of a specific log entry of recent " -"logs" +"This setting changes the way Zammad updates the organization field of the " +"tickets whenever the primary organization of a user is changed." msgstr "" -"Screenshot mit detaillierten Informationen zu einem bestimmten " -"Protokolleintrag der Aktuellsten Protokolle" +"Diese Einstellung definiert, ob Zammad die Organisation der Tickets " +"aktualisiert, wenn die primäre Organisation eines Benutzers geändert wird." -#: ../system/integrations/cti/includes/recent-logs.include.rst:31 -msgid "x" -msgstr "x" +#: ../settings/ticket.rst:74 +msgid "Update the most recent tickets." +msgstr "Die neuesten Tickets aktualisieren." -#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 -#: ../system/integrations/cti/includes/troubleshooting.include.rst:9 -msgid "My Phone page stays blank, signalling does work..." +#: ../settings/ticket.rst:72 +msgid "" +"If this option is chosen, Zammad will update the 100 most recent tickets " +"where the user is the ticket customer. The ticket organization field will be " +"automatically set to the new primary organization of the user." msgstr "" -"Meine Telefonliste bleibt leer, die Anruf-Signalisierung funktioniert..." +"Wenn diese Option gewählt wird, aktualisiert Zammad die letzten 100 Tickets, " +"bei denen der Benutzer der Kunde ist. Das Feld Ticketorganisation wird " +"automatisch auf die neue Primärorganisation des Benutzers gesetzt." -#: ../system/integrations/cti/includes/troubleshooting.include.rst:5 +#: ../settings/ticket.rst:88 +msgid "Do not update any tickets." +msgstr "Keine Tickets aktualisieren." + +#: ../settings/ticket.rst:77 msgid "" -"If you've made sure that signalling works (check Recent logs) and your " -"Caller Log still stays empty, please ensure that you only configured one CTI " -"integration version. Specifically defining more than one agent mapping on " -"the different integration variants will be the issue." +"When choosing this option, Zammad will not update any tickets when the " +"user's primary organization is changed." msgstr "" -"Wenn Sie sich in den \"Aktuellsten Protokollen\" vergewissert haben, dass " -"die Anruf-Signalisierung funktioniert und Ihr Anruferprotokoll trotzdem leer " -"bleibt, stellen Sie bitte sicher, dass Sie nur eine CTI-Integration " -"konfiguriert haben. Wenn Sie mehr als eine Agentenzuordnung in verschiedenen " -"Integrationen definieren, ist das wahrscheinlich das Problem." +"Wenn Sie diese Option wählen, wird Zammad keine Tickets aktualisieren, wenn " +"die primäre Organisation des Benutzers geändert wird." -#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 -msgid "Clear the not needed agent mapping and reload your browser page." -msgstr "" -"Löschen Sie die Zuordnung nicht benötigter Agenten und laden Sie Ihre " -"Browserseite neu." +#: ../settings/ticket.rst:80 +msgid "**Use with care!**" +msgstr "**Mit Vorsicht verwenden!**" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:1 +#: ../settings/ticket.rst:82 msgid "" -"By mapping your agents extension to their existing Zammad users, Zammad can " -"provide a new ticket dialog or open the user profile for the agent that " -"picks up the call." +"Using this option may lead to inconsistencies in the system as the ticket " +"organization may become decoupled from the ticket customer." msgstr "" -"Indem Sie die Durchwahlen Ihrer Agenten den bestehenden Zammad-Benutzern " -"zuordnen, kann Zammad einen neuen Ticket-Dialog bereitstellen oder das " -"Benutzerprofil des Anrufers für den Agenten öffnen, der den Anruf " -"entgegennimmt." +"Die Verwendung dieser Option kann zu Inkonsistenzen im System führen, da " +"dadurch die Ticketorganisation vom Ticketkunden entkoppelt werden kann." -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:5 +#: ../settings/ticket.rst:85 msgid "" -"This speeds up ticket aiding, no matter if it's for existing tickets or new " -"ones!" +"However, you may use this option if you wish to maintain :ref:`the shared " +"access ` to the ticket for all organization " +"members of the original organization of the customer." msgstr "" -"Das beschleunigt die Bearbeitung von Tickets, egal ob es sich um bestehende " -"oder neue Tickets handelt!" +"Sie können diese Option jedoch verwenden, wenn Sie :ref:`den gemeinsamen " +"Zugriff ` auf das Ticket für alle " +"Organisationsmitglieder der ursprünglichen Organisation des Kunden " +"beibehalten möchten." -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:8 +#: ../settings/ticket.rst:110 +msgid "Ticket Number Format (default: ``Increment (SystemID.Counter)``)" +msgstr "Ticket-Nummer-Format (Standard: ``Inkrement (SystemID.Zähler)``)" + +#: ../settings/ticket.rst:94 msgid "" -"To see it work from the agent's perspective, have a look on :user-docs:`user " -"documentation `." +"This setting defines the way Zammad's ticket number will look. Changing this " +"setting in production will cause follow up detection to fail." msgstr "" -"Um zu sehen, wie es aus der Sicht von Agenten funktioniert, sehen Sie sich :" -"user-docs:`Benutzerdokumentation ` an." - -#: ../system/integrations/cti/placetel.rst:2 -msgid "Placetel CTI" -msgstr "Placetel CTI" +"Diese Einstellung legt fest, wie die Ticketnummer durch Zammad vergeben " +"werden soll. Wird diese Einstellung im Produktivbetrieb geändert, schlägt " +"die Zuordnung bei Rückfragen von Kunden fehl." -#: ../system/integrations/cti/placetel.rst:16 -msgid "You need an administrative Placetel account for your organization." -msgstr "Sie benötigen ein Placetel-Administrator-Konto für Ihre Organisation." +#: ../settings/ticket.rst:102 +msgid "Increment (SystemID.Counter)" +msgstr "Inkrement (SystemID.Zähler)" -#: ../system/integrations/cti/placetel.rst:17 -#: ../system/integrations/cti/sipgate.rst:20 +#: ../settings/ticket.rst:98 msgid "" -"Your Zammad instance must be allowed to communicate to external services." +"The increment value contains the SystemID (automatically generated during " +"installation) and a increment which counts up with every new Ticket. The " +"increment will automatically get another digit if needed." msgstr "" -"Ihre Zammad-Instanz muss mit externen Diensten zu kommunizieren können." +"Der Wert enthält die SystemID (die bei der Installation automatisch " +"generiert wird) und ein Inkrement, das bei jedem neuen Ticket hochgezählt " +"wird. Das Inkrement erhält bei Bedarf automatisch eine weitere Stelle, wenn " +"der maximal mögliche Wert erreicht ist." -#: ../system/integrations/cti/placetel.rst:18 -msgid "Placetel must be able to reach your Zammad instance." -msgstr "Placetel muss in der Lage sein, Ihre Zammad-Instanz zu erreichen." +#: ../settings/ticket.rst:102 +msgid "Examples: ``1010138``, ``1010139``" +msgstr "Beispiele: ``1010138``, ``1010139``" -#: ../system/integrations/cti/placetel.rst:22 -msgid ":doc:`provider-configurations/placetel`" -msgstr ":doc:`provider-configurations/placetel`" +#: ../settings/ticket.rst:110 +msgid "Date (Year.Month.Day.SystemID.Counter)" +msgstr "Datum (Jahr.Monat.Tag.SystemID.Zähler)" -#: ../system/integrations/cti/placetel.rst:21 +#: ../settings/ticket.rst:105 msgid "" -"Learn how to configure Placetel to enable Zammad and Placetel to communicate " -"with each other." +"This version of the ticket number is fairly long. However, because it " +"contains the date of ticket creation, it also allows you to see when the " +"ticket has been created. You may feel familiar with this number format if " +"you've worked with OTRS already." msgstr "" -"Erfahren Sie, wie Sie Placetel konfigurieren, damit Zammad und Placetel " -"miteinander kommunizieren können." +"Diese Version der Ticketnummer ist ziemlich lang. Da sie jedoch das Datum " +"der Ticket-Erstellung enthält, können Sie damit erkennen, wann das Ticket " +"erstellt wurde. Wenn Sie bereits mit OTRS gearbeitet haben, werden Sie mit " +"diesem Nummernformat vertraut sein." -#: ../system/integrations/cti/placetel.rst:32 -msgid "" -"The here listed endpoint settings are relevant for the :doc:`integration " -"configuration with Placetel `." -msgstr "" -"Die hier aufgeführten Endpunkt-Einstellungen sind relevant für die :doc:" -"`Konfiguration der Placetel-Integration `." +#: ../settings/ticket.rst:110 +msgid "Examples: ``201206231010138``, ``201206231010139``" +msgstr "Beispiele: ``201206231010138``, ``201206231010139``" -#: ../system/integrations/cti/placetel.rst:37 -#: ../system/integrations/i-doit.rst:53 -msgid "Endpoint" -msgstr "Endpunkt" +#: ../settings/ticket.rst:137 +msgid "OPTIONS" +msgstr "Optionen" -#: ../system/integrations/cti/placetel.rst:36 +#: ../settings/ticket.rst:113 msgid "" -"This endpoint will be required for the Zammad integration within the " -"Placetel web interface." +"The below options allow you to further customize your ticket number. The " +"availability of options differ depending of the chosen ticket number format " +"above." msgstr "" -"Dieser Endpunkt wird für die Zammad-Integration innerhalb der Placetel-" -"Weboberfläche benötigt." +"Mit den folgenden Optionen können Sie Ihre Ticketnummer weiter anpassen. Die " +"Verfügbarkeit der Optionen hängt von dem oben gewählten Ticketnummernformat " +"ab." -#: ../system/integrations/cti/placetel.rst:41 -msgid "API Token" -msgstr "API-Token" +#: ../settings/ticket.rst:122 +msgid "Checksum (default: ``no``)" +msgstr "Prüfsumme (Voreinstellung: ``nein``)" -#: ../system/integrations/cti/placetel.rst:40 +#: ../settings/ticket.rst:118 msgid "" -"You'll receive this token within the ``Web API`` menu. Make sure to copy " -"this value, it's only shown once!" +"If set to yes, we'll built a checksum to further \"unique\" the ticket " +"number of your system. If you're dealing with many other ticket systems this " +"might help to prevent false positive follow up detection on tickets." msgstr "" -"Dieses Token erhalten Sie im Menü ``Web API``. Achten Sie darauf, diesen " -"Wert zu kopieren, er wird nur einmal angezeigt!" +"Wenn Sie diese Option auf \"Ja\" setzen wird eine Prüfsumme gebildet, um die " +"Ticketnummer Ihres Systems weiter \"eindeutig\" zu machen. Wenn Sie mit " +"vielen anderen Ticketsystemen zu tun haben, kann dies eine falsche Zuordnung " +"von Tickets zu verhindern." -#: ../system/integrations/cti/placetel.rst:71 -#: ../system/integrations/cti/sipgate.rst:77 -msgid "Phone Extension to Agent Mapping" -msgstr "Zuordnung von Telefonanschlüssen zu Agenten" +#: ../settings/ticket.rst:122 +msgid "This will also add another digit to the ticket number." +msgstr "Dadurch wird der Ticketnummer eine weitere Ziffer hinzugefügt." -#: ../system/integrations/cti/placetel.rst:0 -msgid "Screenshot showing sample user mappings in between Placetel and Zammad" -msgstr "" -"Screenshot mit Beispielen für Benutzerzuordnungen zwischen Placetel und " -"Zammad" +#: ../settings/ticket.rst:137 +msgid "Min. size of Number (default: ``5``)" +msgstr "Minimale Länge der Zahl (Standard: ``5``)" -#: ../system/integrations/cti/placetel.rst:64 +#: ../settings/ticket.rst:125 msgid "" -"You can find your agents Placetel username combination required within ⚙️ PBX " -"→ VoIP destinations. Within the \"Advanced settings\" section you're looking " -"for \"SIP user name\" and \"SIP server\"." +"This setting defines the minimum length of your ticket number. If your " +"counter is not yet high enough, Zammad will fill the number with zeros to " +"ensure the wanted length." msgstr "" -"Sie finden die für Ihre Agenten erforderliche Placetel-Benutzernamen-" -"Kombination unter ⚙️ PBX → VoIP destinations. Im Abschnitt \"Advanced " -"settings\" finden Sie \"SIP user name\" und \"SIP server\"." - -#: ../system/integrations/cti/placetel.rst:68 -msgid "Combine these two like so: ``@``." -msgstr "Kombinieren Sie beides wie folgt: ``@``." - -#: ../system/integrations/cti/placetel.rst:0 -msgid "Sample VoIP credentials for a Placetel user" -msgstr "Beispiel für VoIP-Zugangsdaten für einen Placetel-Benutzer" - -#: ../system/integrations/cti/provider-configurations/placetel.rst:2 -msgid "Setup Placetel connection for Zammad" -msgstr "Placetel-Verbindung für Zammad einrichten" +"Diese Einstellung legt die Mindestlänge Ihrer Ticketnummer fest. Wenn Ihr " +"Zähler noch nicht hoch genug ist, wird Zammad die Nummer mit Nullen " +"auffüllen, um die gewünschte Länge zu erreichen." -#: ../system/integrations/cti/provider-configurations/placetel.rst:6 +#: ../settings/ticket.rst:129 msgid "" -"This configuration step requires a *full* administrative Placetel account. " -"You may receive forbidden error messages with Placetel in case your " -"permissions are not high enough." +"Please note that the minimum length is ``3`` (SystemID + at least one digit " +"if below 10). Also, if the length is no longer long enough, the number will " +"automatically get one digit longer. Ticket-Numbers **do not overflow**, thus " +"it's save to keep it at 5 or set it lower if wanted." msgstr "" -"Dieser Konfigurationsschritt erfordert ein *vollständiges* administratives " -"Placetel-Konto. Sie können Fehlermeldungen erhalten, wenn Ihre " -"Berechtigungen dafür nicht ausreichen." +"Bitte beachten Sie, dass die Mindestlänge ``3`` beträgt (SystemID + " +"mindestens eine Stelle, falls unter 10). Wenn die Länge nicht mehr " +"ausreicht, wird die Nummer automatisch um eine Stelle länger. Ticket-Nummern " +"wiederholen sich nicht, daher ist es sicher, die Länge auf 5 oder niedriger " +"zu setzen." -#: ../system/integrations/cti/provider-configurations/placetel.rst:10 +#: ../settings/ticket.rst:135 msgid "" -"The following actions can be configured via the `Placetel web interface " -"`_." +"This option is only available if ticket number format is set to " +"``Increment``!" msgstr "" -"Die folgenden Aktionen können über `Placetels Webschinterface `_ konfiguriert werden." +"Diese Option ist nur verfügbar, wenn das Ticket-Nummer-Format auf " +"``InKrement`` gesetzt ist!" -#: ../system/integrations/cti/provider-configurations/placetel.rst:29 -msgid "Step 1: Activate Zammad integration" -msgstr "Schritt 1: Aktivieren der Zammad-Integration" +#: ../settings/ticket.rst:142 +msgid "Auto-Assignment" +msgstr "Automatische Zuweisung" -#: ../system/integrations/cti/provider-configurations/placetel.rst:14 +#: ../settings/ticket.rst:144 msgid "" -"Within Integrations, scroll down to Partner integrations and select Zammad." +"In a larger Zammad environment, it happens that several agents open the same " +"ticket at the same time. Although collision detection is then effective, the " +"efficiency of processing can be increased by means of the automatic " +"assignment of tickets when a ticket is opened." msgstr "" -"Scrollen Sie innerhalb von Integrationen nach unten zu Partnerintegrationen " -"und wählen Sie Zammad." +"In einer größeren Zammad-Umgebung kommt es vor, dass mehrere Agenten ein " +"Ticket gleichzeitig öffnen. Obwohl das in Zammad entsprechend angezeigt " +"wird, kann die Effizienz der Bearbeitung durch die automatische Zuweisung " +"von Tickets erhöht werden." -#: ../system/integrations/cti/provider-configurations/placetel.rst:17 +#: ../settings/ticket.rst:149 msgid "" -"You can alternatively filter by \"Ticket Systems\" to reduce the number of " -"entries on the page. You'll still want to look for Partner integrations. 🤓" +"The automatic assignment of tickets can be activated and configured in the " +"admin area under Settings > Ticket > Auto Assignment." msgstr "" -"Sie können alternativ nach \"Ticket-Systemen\" filtern, um die Anzahl der " -"Einträge auf der Seite zu reduzieren. 🤓" +"Die automatische Zuweisung von Tickets kann im Adminbereich unter " +"Einstellungen > Ticket > Automatische Zuweisung aktiviert und konfiguriert " +"werden." -#: ../system/integrations/cti/provider-configurations/placetel.rst:21 +#: ../settings/ticket.rst:152 msgid "" -"Within the Zammad integration now press \"Activate\". A new tab ``API`` " -"becomes available - open this tab." +"The auto assignment only works if the ticket has no owner yet. By default, " +"the agent can always reset the ticket owner to ``-`` if needed." msgstr "" -"Innerhalb der Zammad-Integration klicken Sie nun auf \"Aktivieren\". Ein " -"neuer Tab ``API`` wird verfügbar - öffnen Sie diesen Tab." +"Die automatische Zuweisung wird nur ausgeführt, wenn das Ticket noch keinen " +"Besitzer hat. Standardmäßig kann der Agent den Besitzer des Tickets bei " +"Bedarf jederzeit auf ``-`` zurücksetzen." -#: ../system/integrations/cti/provider-configurations/placetel.rst:24 +#: ../settings/ticket.rst:155 msgid "" -"Now tick \"Enable Call Control / Notify API\" and paste the Placetel " -"endpoint from your Zammad instance into the field \"URL of your API " -"endpoint\". Save to apply the settings" +"If you want to use this function for only specific tickets, you can " +"configure the conditions accordingly to meet your requirement. By default " +"the condition affects all tickets with the state ``open``." msgstr "" -"Setzen Sie nun ein Häkchen bei \"Enable Call Control / Notify API\" und " -"fügen Sie den Placetel-Endpunkt aus Ihrer Zammad-Instanz in das Feld \"URL " -"of your API endpoint\" ein. Speichern, um die Einstellungen zu übernehmen" +"Wenn Sie diese Funktion nur für bestimmte Anfragen verwenden möchten, können " +"Sie eine Bedingungen dafür konfigurieren. Standardmäßig wirkt sich Funktion " +"auf alle Tickets mit dem Status ``offen`` aus." -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 -msgid "Screencast showing how to activate the Zammad integration" -msgstr "Screencast, der zeigt, wie die Zammad-Integration aktiviert wird" +#: ../settings/ticket.rst:161 +msgid "" +"If you need to exclude users (e.g. a group leader), you can search and " +"select the desired agents in the ``Exception Users`` list. The search " +"function in this area is only effective, if you have too many agents to " +"display at once to help you with the configuration." +msgstr "" +"Wenn Sie Benutzer ausschließen wollen (z.B. einen Gruppenleiter), können Sie " +"die gewünschten Agenten in der Liste ``Ausgenommene Benutzer`` suchen und " +"auswählen. Die Suchfunktion in diesem Bereich ist nur dann aktiv, wenn es " +"mehr Agenten gibt als angezeigt werden können." -#: ../system/integrations/cti/provider-configurations/placetel.rst:51 -msgid "Step 2: Generate API Token for Placetel" -msgstr "Schritt 2: API-Token für Placetel generieren" +#: ../settings/ticket.rst:167 +msgid "Notifications" +msgstr "Benachrichtigungen" -#: ../system/integrations/cti/provider-configurations/placetel.rst:32 +#: ../settings/ticket.rst:191 +msgid "Default Notifications" +msgstr "Standard-Benachrichtigungen" + +#: ../settings/ticket.rst:170 msgid "" -"Go back to the integrations page and scroll down to \"Web API\". Generate a " -"new API token by using the \"Create a new API token\" button." +"This setting allows you to configure the default ticket notifications that " +"will be applied to all new agent users (incl. users who were just assigned " +"agent role). Simply change the notification matrix to desired state and " +"press **Save**." msgstr "" -"Gehen Sie zurück zur Seite \"Integrationen\" und scrollen Sie nach unten zu " -"\"Web API\". Erzeugen Sie ein neues API-Token, indem Sie die Schaltfläche " -"\"Neues API-Token erstellen\" verwenden." +"Mit dieser Einstellung können Sie die Standard-Ticket-Benachrichtigungen " +"konfigurieren, die auf alle neuen Agenten-Benutzer angewendet werden " +"(einschließlich Benutzer, denen gerade eine Agentenrolle zugewiesen wurde). " +"Ändern Sie einfach die Benachrichtigungsmatrix auf den gewünschten Status " +"und drücken Sie **Speichern**." -#: ../system/integrations/cti/provider-configurations/placetel.rst:37 +#: ../settings/ticket.rst:175 msgid "" -"If you already generated a token either use your existing token or reset it " -"by using above mentioned button. Placetel will ask you to conform this reset." +"In case an agent already exists, their ticket notification preferences will " +"be preserved. Optionally, you can also **Apply current defaults to all " +"agents**." msgstr "" -"Wenn Sie bereits einen Token generiert haben, verwenden Sie entweder Ihren " -"bestehenden Token oder setzen Sie ihn mit der oben genannten Schaltfläche " -"zurück. Placetel wird Sie auffordern, diese Rücksetzung zu bestätigen." +"Falls ein Agent bereits existiert werden seine " +"Benachrichtungungseinstellungen beibehalten. Optional können Sie auch " +"**Standardwerte für alle Agenten setzen** verwenden, um bereits existierende " +"Einstellungen für bestehende Agenten zu überschreiben." -#: ../system/integrations/cti/provider-configurations/placetel.rst:41 +#: ../settings/ticket.rst:181 msgid "" -"Please keep in mind that existing API scripts may no longer work due to " -"token resets!" +"**Potential time-consuming action:** Applying default ticket notifications " +"to all agent users may take some time to complete, be patient! The exact " +"time will depend on the size of your system and the number of agents." msgstr "" -"Bitte beachten Sie, dass bestehende API-Skripte aufgrund der Neu-Generierung " -"des Tokens möglicherweise nicht mehr funktionieren!" +"**Potenziell langandauernde Aktion:** Die Anwendung von Standard-Ticket-" +"Benachrichtigungen auf alle Agenten-Benutzer kann einige Zeit in Anspruch " +"nehmen, haben Sie Geduld! Die genaue Zeit hängt von der Größe Ihres Systems " +"und der Anzahl der Agenten ab." -#: ../system/integrations/cti/provider-configurations/placetel.rst:44 +#: ../settings/ticket.rst:185 msgid "" -"Copy the provided API token and insert it into the \"API Token\" field " -"within Zammad's Placetel integration." +"**Active agents only!** When current default ticket notifications are " +"applied, only active agent users are considered. In case an agent is re-" +"activated *after* this action, they will still have the old notification " +"configuration." msgstr "" -"Kopieren Sie das bereitgestellte API-Token und fügen Sie es in das Feld " -"\"API Token\" in der Placetel-Integration von Zammad ein." +"**Nur aktive Agenten!** Wenn die aktuellen Standard-Ticket-" +"Benachrichtigungen angewendet werden, werden nur aktive Agenten " +"berücksichtigt. Falls ein Agent *nach* dieser Aktion reaktiviert wird, hat " +"er noch die alte Benachrichtigungskonfiguration." -#: ../system/integrations/cti/provider-configurations/placetel.rst:47 +#: ../settings/ticket.rst:190 msgid "" -"Apply your changes by using the \"Save\" button on the bottom of the " -"Placetel integration page and activate the Placetel integration." +"In case you want to go back to the initial state of ticket notifications, " +"you can click on **Reset to default** button." msgstr "" -"Übernehmen Sie Ihre Änderungen über die Schaltfläche \"Speichern\" am " -"unteren Rand der Placetel-Integrationsseite und aktivieren Sie die Placetel-" -"Integration." +"Wenn Sie zur Standardkonfiguration der Ticketbenachrichtigungen zurückkehren " +"möchten, können Sie auf die Schaltfläche **Standardwerte wiederherstellen** " +"klicken." -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +#: ../settings/ticket.rst:196 +msgid "Duplicate Detection" +msgstr "Duplikaterkennung" + +#: ../settings/ticket.rst:238 +msgid "Detect Duplicate Ticket Creation" +msgstr "Ticket Duplikaterkennung" + +#: ../settings/ticket.rst:199 msgid "" -"Screencast showing how to retrieve an API token from Placetel for Zammad" +"This setting turns on the duplicate ticket detection mechanism during ticket " +"creation. If similar tickets are found in the system, a suitable warning " +"will be shown to the user trying to create a ticket." msgstr "" -"Screencast, der zeigt, wie man ein API-Token von Placetel für Zammad abruft" +"Diese Einstellung schaltet den Mechanismus zur Erkennung von doppelten " +"Tickets ein. Wenn ähnliche Tickets im System gefunden werden, wird dem " +"Benutzer, der versucht, ein Ticket zu erstellen, eine entsprechende Warnung " +"angezeigt." -#: ../system/integrations/cti/provider-configurations/placetel.rst:73 -#: ../system/integrations/cti/provider-configurations/sipgate.rst:77 -msgid "Step 3: Restrict the numbers to notify on" -msgstr "Schritt 3: Beschränken Sie die zu benachrichtigenden Nummern" +#: ../settings/ticket.rst:206 +msgid "A Sample Duplicate Ticket Warning" +msgstr "Ein Beispiel für eine Warnung zu doppelten Tickets" -#: ../system/integrations/cti/provider-configurations/placetel.rst:54 +#: ../settings/ticket.rst:208 msgid "" -"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " -"the the Integrations page of the Placetel web interface, go to \"Notify " -"API\"." +"You can choose which ticket attributes will be matched by selecting them in " +"**Attributes to compare** field. Only if the ticket attribute value provided " +"by the user in the ticket create form is *equal* with the attribute in an " +"existing ticket, the warning will be shown." msgstr "" -"Haben Sie viele Nummern, die nicht für die Benachrichtigung in Zammad " -"verwendet werden sollen? Gehen Sie auf der Integrations-Seite der Placetel-" -"Weboberfläche auf \"Notify API\"." +"Sie können wählen, welche Ticketattribute abgeglichen werden sollen, indem " +"Sie diese im Feld **Attribute, die zu vergleichen sind** auswählen. Die " +"Duplikat-Warnung wird nur angezeigt, wenn die Werte der Ticketattribute in " +"mehreren Tickets *gleich* sind." -#: ../system/integrations/cti/provider-configurations/placetel.rst:58 +#: ../settings/ticket.rst:213 +msgid "**Warning title** and **Warning message** are configurable as well." +msgstr "**Warnungstitel** und **Warnmeldung** sind ebenfalls konfigurierbar." + +#: ../settings/ticket.rst:215 msgid "" -"Lower on the page Placetel allows you to restrict the numbers to notify on. " -"You'll find this within the \"External routing API\" part." +"You can limit the detection only to certain user roles. By default, only " +"agents will see the warning." msgstr "" -"Weiter unten auf der Seite ermöglicht Placetel die Einschränkung der zu " -"benachrichtigenden Nummern. Sie finden dies im Abschnitt \"External routing " -"API\"." +"Sie können die Erkennung auf bestimmte Benutzerrollen beschränken. " +"Standardmäßig wird die Warnung nur für Agenten angezeigt." -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +#: ../settings/ticket.rst:218 msgid "" -"Screenshot showing a sample selection of phone numbers to use for the " -"Placetels notify API" +"If you don't want to show the matched tickets as part of the warning, you " +"can set **Show matching ticket(s) in the warning** setting to *no*." msgstr "" -"Screenshot mit einer Beispielauswahl von Telefonnummern für die Placetel " -"Notify API" +"Wenn Sie die passenden Tickets nicht als Teil der Warnung anzeigen möchten, " +"können Sie die Einstellung **Zeige passende(s) Ticket(s) in der Warnung** " +"auf *nein* setzen." -#: ../system/integrations/cti/provider-configurations/placetel.rst:66 +#: ../settings/ticket.rst:221 msgid "" -"This menu point also provides a API request log from Placetel view. Just " -"open \"Recent responses of your API endpoint\" to learn more." +"By default, **Permission level for looking up ticket** is set to *User*, " +"which means user permissions will be honored during sarch. The user will " +"see the warning only if tickets they have access to are matched. " +"Alternatively, you can set this setting to *System*, in which case the " +"search will happen within *all* tickets in the system, regardless of user " +"permissions." msgstr "" -"Dieser Menüpunkt bietet auch ein API-Anfrageprotokoll aus Placetel-Sicht. " -"Öffnen Sie einfach \"Recent responses of your API endpoint\", um mehr zu " -"erfahren." +"Standardmäßig ist **Berechtigungsstufe für Ticket-Suchvorgänge** auf " +"*Benutzer* eingestellt. Das bedeutet, dass die Benutzerrechte bei der Suche " +"beachtet werden. Der Benutzer sieht die Warnung nur, wenn Tickets, auf die " +"er Zugriff hat, übereinstimmen. Alternativ können Sie diese Einstellung auf " +"*System* setzen. In diesem Fall wird die Suche in *allen* Tickets im System " +"durchgeführt, unabhängig von den Benutzerrechten." -#: ../system/integrations/cti/provider-configurations/placetel.rst:69 +#: ../settings/ticket.rst:227 +msgid "**🦺 Safety first!**" +msgstr "**🦺 Sicherheit geht vor!**" + +#: ../settings/ticket.rst:229 msgid "" -"If you want to see Zammad's perspective, use the \"Recent Logs\" part from " -"within the Placetel integration page." +"Even if the permission level is set to *System*, the user will not be shown " +"the tickets they don't have access to in the warning, even if they match." msgstr "" -"Wenn Sie Zammads Perspektive sehen möchten, verwenden Sie den Bereich " -"\"Aktuellste Protokolle\" auf der Placetel-Integrationsseite in Zammad." +"Auch wenn die Berechtigungsstufe auf *System* eingestellt ist, werden dem " +"Benutzer die Tickets, auf die er keinen Zugriff hat, in der Warnung nicht " +"angezeigt, selbst wenn sie übereinstimmen." -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 -msgid "Screenshot showing sample log entries for Placetels API calls to Zammad" +#: ../settings/ticket.rst:233 +msgid "" +"However, just the confirmation about the existence of the tickets in the " +"system may be considered an unwanted information disclosure. Use this option " +"carefully!" msgstr "" -"Screenshot mit Beispielprotokolleinträgen für Placetels API-Anfragen an " -"Zammad" - -#: ../system/integrations/cti/provider-configurations/placetel.rst:77 -msgid "Step 4 (optional): Further configurations for Placetel" -msgstr "Schritt 4 (optional): Weitere Konfigurationen für Placetel" +"Die bloße Bestätigung über die Existenz der Tickets im System kann jedoch " +"als unerwünschte Weitergabe von Informationen angesehen werden. Verwenden " +"Sie diese Option mit Vorsicht!" -#: ../system/integrations/cti/provider-configurations/placetel.rst:76 +#: ../settings/ticket.rst:237 msgid "" -"If needed, you can now configure Zammad's Placetel integration in more " -"detail. You can learn more about your options here: :ref:`Placetel " -"integration settings `." +"Finally, you can configure between matching within **All tickets** or **Open " +"tickets** only by setting **Match tickets in following states**. Depending " +"on the current ticket state, a ticket may or not be matched." msgstr "" -"Bei Bedarf können Sie nun die Placetel-Integration von Zammad detaillierter " -"konfigurieren. Erfahren Sie hier mehr über Ihre Optionen :ref:`Placetel-" -"Integrationseinstellungen `." - -#: ../system/integrations/cti/provider-configurations/sipgate.rst:2 -msgid "Setup Sipgate connection for Zammad" -msgstr "Sipgate-Verbindung für Zammad einrichten" +"Schließlich können Sie festlegen, ob der Abgleich nur für **Alle Tickets** " +"oder nur für **Offene Tickets** erfolgen soll, indem Sie **Vergleiche " +"Tickets in folgenden Status** einstellen. Je nach aktuellem Ticketstatus " +"erfolgt die Prüfung oder nicht." -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Sipgate has no english web interface which is why this documentation page is " -"mixing up languages badly." -msgstr " " +#: ../system/core-workflows.rst:2 +msgid "Core Workflows" +msgstr "Core Workflows" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +#: ../system/core-workflows.rst:4 msgid "" -"Please also note that the availability of API addons highly depends on your " -"package trier. Usage of sipgate.io packages *is not free*, please check " -"their `pricing page `_ before!" +"Core Workflows allow you to adjust object attributes in many ways. For " +"example:" msgstr "" -"Bitte beachten Sie auch, dass die Verfügbarkeit von API-Addons stark von " -"Ihrem Paket abhängt. Die Nutzung von sipgate.io-Paketen ist *nicht " -"kostenlos*, bitte prüfen Sie vorher die `Preisübersicht `_ !" +"Mit Core Workflows können Sie Objektattribute auf vielfältige Weise " +"anpassen. Zum Beispiel:" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:35 -msgid "Step 1: Book sipgate.io package" -msgstr "Schritt 1: Paket sipgate.io buchen" +#: ../system/core-workflows.rst:7 +msgid "show / hide fields" +msgstr "Felder anzeigen / verstecken" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:13 -msgid "Skip to step 2 if you already have the package booked!" -msgstr "Gehen Sie zu Schritt 2, wenn Sie das Paket bereits gebucht haben!" +#: ../system/core-workflows.rst:8 +msgid "adjust mandatory setting" +msgstr "Pflichtfelder anpassen" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:15 +#: ../system/core-workflows.rst:9 +msgid "manipulate available options" +msgstr "verfügbare Optionen anpassen" + +#: ../system/core-workflows.rst:11 msgid "" -"Login to an administrative Sipgate account and navigate to " -"``Accountverwaltung``. You'll see several different options depending on " -"your booked packages. Select ``Verträge & Produkte`` to continue." +"With this, you can provide exactly the information your users really need!" msgstr "" -"Loggen Sie sich in einen administrativen Sipgate-Account ein und navigieren " -"Sie zu ``Accountverwaltung``. Abhängig von Ihren gebuchten Paketen sehen Sie " -"verschiedene Optionen. Wählen Sie ``Verträge & Produkte`` um fortzufahren." +"Auf diese Weise können Sie genau die Informationen bereitstellen, die Ihre " +"Nutzer wirklich brauchen!" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:19 +#: ../system/core-workflows.rst:15 msgid "" -"Scroll down to the section ``Zusätzliche Produkte buchen`` and look for " -"``sipgate.io`` - select this product by using the ``Produkte anzeigen``-" -"Button." +"If the pre-defined :doc:`/system/objects` are not enough, please add them " +"beforehand." msgstr "" -"Scrollen Sie nach unten in den Bereich ``Zusätzliche Produkte buchen`` und " -"suchen Sie nach ``sipgate.io`` - wählen Sie dieses Produkt über den " -"``Produkte anzeigen``-Button aus." +"Wenn die vordefinierten :doc:`/system/objects` nicht ausreichen, fügen Sie " +"eigene bitte vorher hinzu." -#: ../system/integrations/cti/provider-configurations/sipgate.rst:23 +#: ../system/core-workflows.rst:17 msgid "" -"On the next page select either one of the ``sipgate.io`` packages or ``Push-" -"API Package Free``. Follow the dialogue by booking the addon. You'll be " -"returned to your contract overview and now should see the selected addon in " -"your list." +"If you experience slow or unreliable field updates, please see :ref:`Core " +"Workflow Ajax Modus `" msgstr "" -"Auf der nächsten Seite wählen Sie entweder eines der ``sipgate.io`-Pakete " -"oder ``Push-API Package Free``. Folgen Sie dem Dialog, um das Addon zu " -"buchen. Sie gelangen zurück zu Ihrer Vertragsübersicht und sollten nun das " -"ausgewählte Addon in Ihrer Liste sehen." +"Wenn Sie langsame oder unzuverlässige Feldaktualisierungen feststellen, " +"lesen Sie bitte :ref:`Core Workflow Ajax Modus `" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:30 +#: ../system/core-workflows.rst:22 msgid "" -"The availability for ``sipgate.io`` packages and their levels highly depends " -"on the overall account type and product you've booked with Sipgate." +"This is a very enhanced functionality and can cause unexpected UI behavior. " +"Please ensure to test your use cases after configuration to reduce surprises." msgstr "" -"Die Verfügbarkeit von ``sipgate.io``-Paketen und deren Levels hängt von der " -"Art des Accounts und dem Produkt ab, das Sie bei Sipgate gebucht haben." +"Dies ist eine sehr mächtige Funktionalität und kann zu unerwartetem " +"Verhalten der Benutzeroberfläche führen. Bitte stellen Sie sicher, dass Sie " +"Ihre Anwendungsfälle nach der Konfiguration testen, um Überraschungen zu " +"vermeiden." -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screencast showing the process on how to book the required sipgate.io addon" -msgstr "" -"Screencast, der den Prozess der Buchung des benötigten sipgate.io-Addons " -"zeigt" +#: ../system/core-workflows.rst:None +msgid "Dialogue for adding a new workflow" +msgstr "Dialog zum Hinzufügen eines neuen Workflows" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:52 -msgid "Step 2: Configure webhook for Zammad" -msgstr "Schritt 2: Konfigurieren Sie den Webhook für Zammad" +#: ../system/core-workflows/condition-operators.rst:2 +msgid "Core Workflow Condition Operators" +msgstr "Core Workflow Bedingungsoperatoren" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:38 +#: ../system/core-workflows/condition-operators.rst:4 msgid "" -"Within your ``Accountverwaltung`` navicate to your product ``sipgate.io``. " -"In the newly opened tab, switch from \"Clients\" to \"Webhooks\" and paste " -"the endpoint URLs from your Zammad instance like so:" +"You might know that there is a separate section for explaining :doc:" +"`condition operators `. Head over there to " +"see a detailed explanation of many conditions and operators." msgstr "" -"Navigieren Sie innerhalb Ihrer ``Accountverwaltung`` zu Ihrem Produkt " -"``sipgate.io``. Wechseln Sie im neu geöffneten Tab von \"Clients\" zu " -"\"Webhooks\" und fügen Sie die Endpunkt-URLs aus Ihrer Zammad-Instanz wie " -"folgt ein:" - -#: ../system/integrations/cti/provider-configurations/sipgate.rst:42 -msgid "Inbound endpoint to \"Incoming\"" -msgstr "Eingehender Endpunkt auf \"Incoming\"" - -#: ../system/integrations/cti/provider-configurations/sipgate.rst:43 -msgid "Outbound endpoint to \"Outgoing\"" -msgstr "Ausgehender Endpunkt auf \"Outgoing\"" +"Sie wissen vielleicht, dass es einen separaten Bereich zur Erläuterung von :" +"doc:`Bedingungsoperatoren ` gibt. Dort " +"finden Sie eine detaillierte Erklärung vieler Bedingungen und Operatoren." -#: ../system/integrations/cti/provider-configurations/sipgate.rst:47 +#: ../system/core-workflows/condition-operators.rst:8 msgid "" -"Ensure to select at least one call group or phoneline within \"Sources\". " -"Other wise Sipgate will not indicate any incoming or outgoing calls to " -"Zammad." +"Due to differences to other places in Zammad which are also using conditions " +"(e.g. triggers), you can find a dedicated description of operators for core " +"workflows below." msgstr "" -"Stellen Sie sicher, dass Sie mindestens eine Rufgruppe oder Telefonleitung " -"unter \"Sources\" auswählen. Andernfalls wird Sipgate keine eingehenden oder " -"ausgehenden Anrufe an Zammad anzeigen." +"Aufgrund von Unterschieden zu anderen Bereichen in Zammad, die ebenfalls " +"Bedingungen verwenden (z.B. Trigger) , finden Sie weiter unten eine " +"Beschreibung der Operatoren speziell für Core-Workflows." -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +#: ../system/core-workflows/condition-operators.rst:12 msgid "" -"Screencast showing how to add Zammad's endpoint URLs to sipgate.ios webhook " -"configuration" +"Be aware that the availability of the operators depends on the selected " +"attribute and its field type. Some of the operators may only be available " +"for system attributes (e.g. for \"tags\", \"active\")." msgstr "" -"Screencast, der zeigt, wie die Endpunkt-URLs von Zammad zur sipgate.ios-" -"Webhook-Konfiguration hinzugefügt werden" +"Beachten Sie, dass die Verfügbarkeit der Operatoren von dem ausgewählten " +"Attribut und seinem Feldtyp abhängt. Einige der Operatoren sind " +"möglicherweise nur für Systemattribute verfügbar (z.B. für \"Tags\", " +"\"Aktiv\")." -#: ../system/integrations/cti/provider-configurations/sipgate.rst:55 -msgid "" -"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " -"the Webhooks → URLs section of Sipgate you can select which *sources* " -"Sipgate should notify Zammad about in- and outgoing calls." -msgstr "" -"Haben Sie Nummern, die nicht für die Benachrichtigung in Zammad verwendet " -"werden sollen? Im Bereich Webhooks → URLs von Sipgate können Sie auswählen, " -"welche *sources* Sipgate über ein- und ausgehende Anrufe an Zammad " -"benachrichtigen soll." +#: ../system/core-workflows/condition-operators.rst:20 +msgid "Operator" +msgstr "Operator" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:59 -msgid "" -"Use either specific phone lines or use the option \"Use for all phonelines " -"and groups\" to notify Zammad about all existing lines of your Sipgate " -"account." -msgstr "" -"Verwenden Sie entweder bestimmte Telefonleitungen oder verwenden Sie die " -"Option \"Use for all phonelines and groups\", um Zammad über alle " -"vorhandenen Leitungen Ihres Sipgate-Kontos zu informieren." +#: ../system/core-workflows/condition-operators.rst:22 +msgid "after (absolute)" +msgstr "nach (absolut)" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screenshot showing a sample selection of phone numbers to use for the " -"Sipgates webhooks API" +#: ../system/core-workflows/condition-operators.rst:23 +msgid "Matches if a date/time is after a specific point in time." msgstr "" -"Screenshot mit einer Beispielauswahl von Telefonnummern für die Sipgate " -"Webhooks API" - -#: ../system/integrations/cti/provider-configurations/sipgate.rst:68 -msgid "This section also allows you to enable a Debug log." -msgstr "In diesem Abschnitt können Sie auch ein Debug-Protokoll aktivieren." - -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "Screenshot showing an enabled Debug log option" -msgstr "Screenshot zeigt die aktivierte Debug-Funktion" +"Trifft zu, wenn ein Datum/Uhrzeit nach einem definierten Zeitpunkt liegt." -#: ../system/integrations/cti/provider-configurations/sipgate.rst:73 -msgid "" -"After enabling you can use the Debug log section to see all sent webhook " -"calls to Zammad. You'll also can see the response." -msgstr "" -"Nach der Aktivierung können Sie den Abschnitt Debug-Log verwenden, um alle " -"gesendeten Webhook-Aufrufe an Zammad zu sehen. Sie können auch die Antwort " -"sehen." +#: ../system/core-workflows/condition-operators.rst:24 +msgid "after (relative)" +msgstr "nach (relativ)" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screenshot showing sample log entries for Sipgates webhook calls to Zammad" +#: ../system/core-workflows/condition-operators.rst:25 +msgid "Matches if a time span after a specified event has passed." msgstr "" -"Screenshot mit Beispielprotokolleinträgen für Sipgates Webhook-Aufrufe an " -"Zammad" +"Trifft zu, wenn eine Zeitspanne nach einem bestimmten Ereignis vergangen ist." -#: ../system/integrations/cti/provider-configurations/sipgate.rst:81 -msgid "Step 4 (optional): Further configurations for Sipgate" -msgstr "Schritt 4 (optional): Weitere Konfigurationen für Sipgate" +#: ../system/core-workflows/condition-operators.rst:26 +msgid "before (absolute)" +msgstr "vor (absolut)" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:80 -msgid "" -"If needed, you can now configure Zammad's Sipgate integration in more " -"detail. You can learn more about your options here: :ref:`Sipgate " -"integration settings `." +#: ../system/core-workflows/condition-operators.rst:27 +msgid "Matches if a date/time is before a specific point in time." msgstr "" -"Bei Bedarf können Sie nun die Sipgate-Integration von Zammad detaillierter " -"konfigurieren. Erfahren Sie hier mehr über Ihre Optionen: :ref:`Sipgate-" -"Integrationseinstellungen `." +"Trifft zu, wenn ein Datum/Uhrzeit vor einem definierten Zeitpunkt liegt." -#: ../system/integrations/cti/sipgate.rst:2 -msgid "Sipgate (sipgate.io)" -msgstr "Sipgate (sipgate.io)" +#: ../system/core-workflows/condition-operators.rst:28 +msgid "before (relative)" +msgstr "vor (relativ)" -#: ../system/integrations/cti/sipgate.rst:16 -msgid "You need an administrative Sipgate account for your organization." -msgstr "Sie benötigen ein administratives Sipgate-Konto für Ihre Organisation." +#: ../system/core-workflows/condition-operators.rst:29 +msgid "Matches if a time span after a specified event has not passed." +msgstr "Trifft zu während einer definierten Zeitspanne nach einem Ereignis." -#: ../system/integrations/cti/sipgate.rst:17 -msgid "" -"Zammad requires a ``sipgate.io`` addon from the feature store (please note " -"that API calls are not free with Sipgate. Rates may apply and differ from " -"account to account)." -msgstr "" -"Zammad erfordert ein ``sipgate.io`` Addon aus dem Feature Store (bitte " -"beachten Sie, dass API-Aufrufe mit Sipgate nicht kostenlos sind. Es können " -"Gebühren anfallen, die sich von Konto zu Konto unterscheiden)." +#: ../system/core-workflows/condition-operators.rst:30 +msgid "contains" +msgstr "enthält" -#: ../system/integrations/cti/sipgate.rst:21 -msgid "Sipgate must be able to reach your Zammad instance." -msgstr "Sipgate muss in der Lage sein Ihre Zammad-Instanz zu erreichen." +#: ../system/core-workflows/condition-operators.rst:31 +msgid "Matches if a specified value is present." +msgstr "Trifft zu, wenn ein definierter Wert vorhanden ist." -#: ../system/integrations/cti/sipgate.rst:25 -msgid ":doc:`provider-configurations/sipgate`" -msgstr ":doc:`provider-configurations/sipgate`" +#: ../system/core-workflows/condition-operators.rst:33 +msgid "Matches if all of the specified values are present." +msgstr "Trifft zu, wenn alle definierten Werte vorhanden sind." -#: ../system/integrations/cti/sipgate.rst:24 -msgid "" -"Learn how to configure Sipgate to enable Zammad and Sipgate to communicate " -"with each other." -msgstr "" -"Erfahren Sie, wie Sie Sipgate konfigurieren, damit Zammad und Sipgate " -"miteinander kommunizieren können." +#: ../system/core-workflows/condition-operators.rst:35 +msgid "Matches if none of the specified values are present." +msgstr "Trifft zu, wenn keiner der definierten Werte vorhanden ist." -#: ../system/integrations/cti/sipgate.rst:33 -msgid "" -"Below endpoint settings affect the :doc:`sipgate.io configuration `." -msgstr "" -"Die folgenden Endpunkteinstellungen betreffen die :doc:`sipgate.io-" -"Konfiguration `." +#: ../system/core-workflows/condition-operators.rst:36 +msgid "contains not" +msgstr "enthält nicht" -#: ../system/integrations/cti/sipgate.rst:37 -msgid "This endpoint is required for incoming call hooks." -msgstr "Dieser Endpunkt ist für eingehende Anrufe erforderlich." +#: ../system/core-workflows/condition-operators.rst:37 +msgid "Matches if a specified value is not present." +msgstr "Trifft zu, wenn ein definierter Wert nicht vorhanden ist." -#: ../system/integrations/cti/sipgate.rst:40 -msgid "This endpoint is required for outgoing call hooks." -msgstr "Dieser Endpunkt ist für ausgehende Anrufe erforderlich." +#: ../system/core-workflows/condition-operators.rst:39 +msgid "Matches if one specified value is present." +msgstr "Trifft zu, wenn ein definierter Wert vorhanden ist." -#: ../system/integrations/cti/sipgate.rst:0 -msgid "Screenshot showing sample user mappings in between Sipgate and Zammad" -msgstr "" -"Screenshot mit Beispielen für Benutzerzuordnungen zwischen Sipgate und Zammad" +#: ../system/core-workflows/condition-operators.rst:41 +msgid "Matches if one specified value is not present." +msgstr "Trifft zu, wenn ein definierter Wert nicht vorhanden ist." -#: ../system/integrations/cti/sipgate.rst:69 -msgid "" -"You can find your agent's Sipgate username within ``Accountverwaltung → " -"Benutzer``. You're looking for the SIP-ID." -msgstr "" -"Den Sipgate-Benutzernamen Ihres Agenten finden Sie unter ``Accountverwaltung " -"→ Benutzer``. Suchen Sie nach der SIP-ID." +#: ../system/core-workflows/condition-operators.rst:42 +msgid "does not match regex" +msgstr "passt nicht auf regex" -#: ../system/integrations/cti/sipgate.rst:0 -msgid "Sample VoIP credentials for a Sipgate user" -msgstr "Beispiel für VoIP-Anmeldeinformationen für einen Sipgate-Benutzer" +#: ../system/core-workflows/condition-operators.rst:43 +msgid "Matches if content doesn't fit to regex rule." +msgstr "Trifft zu, wenn der Inhalt nicht der Regex-Regel entspricht." -#: ../system/integrations/cti/sipgate.rst:77 -msgid "Users with several devices also have several SIP-IDs." -msgstr "Benutzer mit mehreren Geräten haben auch mehrere SIP-IDs." +#: ../system/core-workflows/condition-operators.rst:44 +msgid "ends with" +msgstr "endet auf" -#: ../system/integrations/elasticsearch.rst:2 -msgid "Elasticsearch (SaaS)" -msgstr "Elasticsearch (SaaS)" +#: ../system/core-workflows/condition-operators.rst:45 +msgid "Matches if content ends with specified value." +msgstr "Trifft zu, wenn der Inhalt mit dem definierten Wert endet." -#: ../system/integrations/elasticsearch.rst:4 -msgid "" -"The Elasticsearch integration allows you to create a read-only user to use " -"with your favorite reporting tool (e.g. like Grafana)." -msgstr "" -"Die Elasticsearch-Integration ermöglicht es Ihnen, einen schreibgeschützten " -"Benutzer zu erstellen, den Sie mit Ihrem bevorzugten Reporting-Tool (z.B. " -"Grafana) verwenden können." +#: ../system/core-workflows/condition-operators.rst:46 +msgid "ends with one of" +msgstr "endet auf eins von" -#: ../system/integrations/elasticsearch.rst:7 -msgid "" -"If you want to take full advantage of the Zammad reporting, have a look at " -"our :docs:`Grafana ` " -"setup page as well." -msgstr "" -"Wenn Sie die Vorteile des Reportings mit Zammad voll ausschöpfen wollen, " -"sollten Sie auch einen Blick auf unsere Seite zur :docs:`Grafana-Einrichtung " -"` werfen." +#: ../system/core-workflows/condition-operators.rst:47 +msgid "Matches if content ends with one of the specified values." +msgstr "Trifft zu, wenn der Inhalt mit einem der definierten Werte endet." -#: ../system/integrations/elasticsearch.rst:11 -#: ../system/subscription/index.rst:7 -msgid "**🚧 Hosted environment specific 🚧**" -msgstr "**🚧 Spezifisch für die gehostete Umgebung 🚧**" +#: ../system/core-workflows/condition-operators.rst:48 +msgid "from (relative)" +msgstr "von vor (relativ)" -#: ../system/integrations/elasticsearch.rst:13 -msgid "" -"This integration is only available for Hosted setups. In order to use " -"Elasticsearch you'll need the **Plus** subscription." +#: ../system/core-workflows/condition-operators.rst:49 +msgid "Matches if date/time is after a period of time after an event." msgstr "" -"Diese Integration steht nur in gehosteten Umgebungen zur Verfügung. Um " -"Elasticsearch nutzen zu können, benötigen Sie ein **Plus** Abonnement." +"Trifft zu, wenn Datum/Uhrzeit nach einer definierten Zeitspanne nach einem " +"Ereignis liegen." -#: ../system/integrations/elasticsearch.rst:16 -msgid "" -"Self hosted users have all the control over their self hosted Elasticsearch " -"instances." -msgstr "" -"Selbstgehostete Nutzer haben die gesamte Kontrolle über ihre selbst " -"gehosteten Elasticsearch-Instanzen." +#: ../system/core-workflows/condition-operators.rst:51 +msgid "Matches if content is equal to a specified value." +msgstr "Trifft zu, wenn der Inhalt gleich dem definierten Wert ist." -#: ../system/integrations/elasticsearch.rst:None -msgid "Elasticsearch integration page on SaaS environments" -msgstr "Seite Elasticsearch-Integrations für SaaS-Umgebungen" +#: ../system/core-workflows/condition-operators.rst:52 +msgid "is any of" +msgstr "ist eins von" -#: ../system/integrations/elasticsearch.rst:27 -msgid "" -"Please note the following limitations of Elasticsearch access on hosted " -"environments:" +#: ../system/core-workflows/condition-operators.rst:53 +msgid "Matches if content is equal to any of specified values." msgstr "" -"Bitte beachten Sie die folgenden Limitierungen für den Elasticsearch-Zugriff " -"auf gehosteten Umgebungen:" +"Trifft zu, wenn der Inhalt mit einem der definierten Werte übereinstimmt." -#: ../system/integrations/elasticsearch.rst:30 -msgid "access to the Elasticsearch index is read-only access" -msgstr "der Zugriff auf Elasticsearch-Indexe ist ein lesender Zugriff" +#: ../system/core-workflows/condition-operators.rst:54 +msgid "is modified" +msgstr "ist geändert" -#: ../system/integrations/elasticsearch.rst:31 -msgid "currently you're limited to user only" -msgstr "Sie sind zur Zeit auf einen Benutzer beschränkt" +#: ../system/core-workflows/condition-operators.rst:55 +msgid "Matches if content is modified." +msgstr "Trifft zu, wenn der Inhalt geändert wurde." -#: ../system/integrations/elasticsearch.rst:32 -msgid "" -"Reporting tools that require to write into the indexes (like Kibana) are not " -"supported" +#: ../system/core-workflows/condition-operators.rst:57 +#: ../system/core-workflows/condition-operators.rst:61 +msgid "True from the moment of changing content until form submit." msgstr "" -"Reporting-Tools die Schreibzugriff auf Indexen benötigen (wie Kibana) werden " -"nicht unterstützt" +"Wahr ab dem Zeitpunkt der Änderung des Inhalts bis zum Absenden des " +"Formulars." -#: ../system/integrations/elasticsearch.rst:34 -msgid "IP access restriction is currently not yet supported" -msgstr "IP-Zugriffsbeschränkung wird zur Zeit noch nicht unterstützt" +#: ../system/core-workflows/condition-operators.rst:58 +msgid "is modified to" +msgstr "ist geändert auf" -#: ../system/integrations/elasticsearch.rst:37 -msgid "Activating Elasticsearch Access" -msgstr "Aktivieren des Elasticsearch-Zugangs" +#: ../system/core-workflows/condition-operators.rst:59 +msgid "Matches if content is modified to a specific value." +msgstr "Trifft zu, wenn der Inhalt auf einen definiertene Wert geändert wurde." -#: ../system/integrations/elasticsearch.rst:39 +#: ../system/core-workflows/condition-operators.rst:62 +msgid "is none of" +msgstr "ist keins von" + +#: ../system/core-workflows/condition-operators.rst:63 +msgid "Matches if content is none of any specified values." +msgstr "Trifft zu, wenn der Inhalt keinem der definierten Werte entspricht." + +#: ../system/core-workflows/condition-operators.rst:65 +msgid "Matches if content is not equal to a specified value." +msgstr "Trifft zu, wenn der Inhalt nicht gleich dem definierten Wert ist." + +#: ../system/core-workflows/condition-operators.rst:67 +msgid "Matches if content is present." +msgstr "Trifft zu, wenn ein Inhalt vorhanden ist." + +#: ../system/core-workflows/condition-operators.rst:68 +msgid "just changed" +msgstr "gerade geändert" + +#: ../system/core-workflows/condition-operators.rst:69 +msgid "Matches if content has changed." +msgstr "Trifft zu, wenn sich der Inhalt gerade geändert hat." + +#: ../system/core-workflows/condition-operators.rst:71 +#: ../system/core-workflows/condition-operators.rst:75 msgid "" -"By default external access to your Elasticsearch index is not active. You " -"can enable the integration at any time if needed." +"Only true for the moment of changing content until next form field action/" +"click." msgstr "" -"Standardmäßig ist der externe Zugriff auf Ihren Elasticsearch-Index nicht " -"aktiv. Sie können die Integration bei Bedarf jederzeit aktivieren." +"Nur zutreffend für den Moment der Änderung des Inhalts bis zur nächsten " +"Formularfeldaktion/zum nächsten Mausklick." -#: ../system/integrations/elasticsearch.rst:42 -msgid "" -"Please ensure to note down the password provided - you won't have access to " -"it afterwards." +#: ../system/core-workflows/condition-operators.rst:72 +msgid "just changed to" +msgstr "gerade geändert auf" + +#: ../system/core-workflows/condition-operators.rst:73 +msgid "Matches if content has changed to a specified value." msgstr "" -"Bitte notieren Sie sich das angegebene Passwort, da Sie später keinen " -"Zugriff mehr darauf haben." +"Trifft zu, wenn sich der Inhalt gerade auf einen definierten Wert geändert " +"hat." -#: ../system/integrations/elasticsearch.rst:None -msgid "Screencast showing activation of Elasticsearch integration" -msgstr "Screencast zeigt Aktivierung der Elasticsearch-Integration" +#: ../system/core-workflows/condition-operators.rst:76 +msgid "matches regex" +msgstr "passt auf regex" -#: ../system/integrations/elasticsearch.rst:51 -msgid "Connection Settings" -msgstr "Verbindungs-Einstellungen" +#: ../system/core-workflows/condition-operators.rst:77 +msgid "Matches if value fits to regex rule." +msgstr "Trifft zu, wenn der Wert der Regex-Regel entspricht." -#: ../system/integrations/elasticsearch.rst:53 -msgid "" -"This section holds the most important general information for accessing your " -"Elasticsearch indexes - such as:" -msgstr "" -"Dieser Abschnitt enthält die wichtigsten allgemeinen Informationen für den " -"Zugriff auf Ihre Elasticsearch-Indizes - wie zum Beispiel:" +#: ../system/core-workflows/condition-operators.rst:79 +msgid "Matches if no content is present." +msgstr "Trifft zu, wenn kein Inhalt vorhanden ist." -#: ../system/integrations/elasticsearch.rst:57 -msgid "A unique subdomain that does not tell your real instance URL." -msgstr "Eine eindeutige Subdomain, die Ihre echte Instanz-URL nicht verrät." +#: ../system/core-workflows/condition-operators.rst:80 +msgid "starts with" +msgstr "beginnt mit" -#: ../system/integrations/elasticsearch.rst:61 -msgid "Software" -msgstr "Software" +#: ../system/core-workflows/condition-operators.rst:81 +msgid "Matches if content starts with specified value." +msgstr "Trifft zu, wenn der Inhalt mit dem definierten Wert beginnt." -#: ../system/integrations/elasticsearch.rst:60 -msgid "" -"The major version of the search index being used. This is required by some " -"Reporting tools like Grafana." +#: ../system/core-workflows/condition-operators.rst:82 +msgid "starts with one of" +msgstr "beginnt mit eins von" + +#: ../system/core-workflows/condition-operators.rst:83 +msgid "Matches if content starts with one of the specified values." +msgstr "Trifft zu, wenn der Inhalt mit einem der definierten Werte beginnt." + +#: ../system/core-workflows/condition-operators.rst:84 +msgid "till (relative)" +msgstr "bis in (relativ)" + +#: ../system/core-workflows/condition-operators.rst:85 +msgid "Matches if date/time is before a period of time before an event." msgstr "" -"Die Hauptversion des verwendeten Suchindexes. Dies wird von einigen " -"Reporting-Tools wie Grafana benötigt." +"Triff zu, wenn Datum/Uhrzeit vor einem definierten Zeitraum vor einem " +"Ereignis liegt." -#: ../system/integrations/elasticsearch.rst:64 -msgid "Authentication" -msgstr "Authentifizierung" +#: ../system/core-workflows/condition-operators.rst:86 +msgid "today" +msgstr "heute" -#: ../system/integrations/elasticsearch.rst:64 -msgid "The authentication type being supported. ``Basic Authentication``" -msgstr "Der unterstützte Authentifizierungstyp. ``Basic Authentication``" +#: ../system/core-workflows/condition-operators.rst:87 +msgid "Matches if date/time is today." +msgstr "Trifft zu, wenn Datum/Uhrzeit heute ist." -#: ../system/integrations/elasticsearch.rst:67 -msgid "Available Indexes" -msgstr "Verfügbare Indexe" +#: ../system/core-workflows/condition-operators.rst:88 +msgid "within last (relative)" +msgstr "innerhalb letzter (relativ)" -#: ../system/integrations/elasticsearch.rst:69 +#: ../system/core-workflows/condition-operators.rst:89 msgid "" -"Within this section we're displaying the -in our opinion- most important " -"indexes for a Zammad instance." +"Matches if date/time content is within specified period of time before now." msgstr "" -"In diesem Abschnitt zeigen wir die - unserer Meinung nach - wichtigsten " -"Indizes für eine Zammad-Instanz an." +"Triff zu, wenn Datum/Uhrzeit innerhalb der definierten Zeitspann vor jetzt " +"liegt." -#: ../system/integrations/elasticsearch.rst:72 -msgid "" -"If you require all indexes or our listing is not good enough for you, point " -"your browser to the URL we're providing and append ``/_aliases?" -"pretty=true``. The result should look like this: ``https://.zammad.com/" -"_aliases?pretty=true``." -msgstr "" -"Wenn Sie alle Indizes benötigen oder Ihnen unsere Auflistung nicht " -"ausreicht, rufen Sie mit Ihrem Browser die von uns angegebene URL auf und " -"fügen Sie ``/_aliases?pretty=true`` hinzu. Das Ergebnis sollte wie folgt " -"aussehen: ``https://.zammad.com/_aliases?pretty=true``." +#: ../system/core-workflows/condition-operators.rst:91 +msgid "within next (relative)" +msgstr "innerhalb nächster (relativ)" -#: ../system/integrations/elasticsearch.rst:77 +#: ../system/core-workflows/condition-operators.rst:92 msgid "" -"Your browser will automatically ask for your credentials - you'll then see " -"something like this:" +"Matches if date/time content is within specified period of time after now." msgstr "" -"Ihr Browser fragt automatisch nach Ihren Zugangsdaten - Sie sehen dann etwas " -"wie das hier:" +"Trifft zu, wenn Datum/Uhrzeit innerhalb der definierten Zeitspanne nach " +"jetzt liegt." -#: ../system/integrations/elasticsearch.rst:125 -msgid "Credentials" -msgstr "Zugangsdaten" +#: ../system/core-workflows/how-do-they-work.rst:2 +msgid "How do they work?" +msgstr "Wie funktionieren sie?" -#: ../system/integrations/elasticsearch.rst:127 +#: ../system/core-workflows/how-do-they-work.rst:4 msgid "" -"Within this section Zammad displays your available users. The password is " -"provided once (upon activation) and cannot be retrieved after that." +"Core Workflows are executed according to their priority. If two workflows " +"have the same priority, they are executed in alphabetical order based on " +"their **name**." msgstr "" -"In diesem Abschnitt zeigt Zammad Ihre verfügbaren Benutzer an. Das Passwort " -"wird einmalig vergeben (bei der Aktivierung) und kann danach nicht mehr " -"abgerufen werden." +"Core-Workflows werden entsprechend ihrer Priorität ausgeführt. Wenn zwei " +"Workflows die gleiche Priorität haben, werden sie in alphabetischer " +"Reihenfolge auf der Grundlage ihres **Namens** ausgeführt." -#: ../system/integrations/elasticsearch.rst:131 +#: ../system/core-workflows/how-do-they-work.rst:8 msgid "" -"If you need to change or reset your Elasticsearch user password, use the " -"\"Reset password\" button in the credentials table. Doing so creates a brand " -"new password for the account in question. This change is immediate, keep in " -"mind that this may affect third party tools connected to your instance." +"Because of the way Core Workflows work, all changes to attributes are " +"checked with the application server - please see :doc:`limitations` for " +"possible issues." msgstr "" -"Wenn Sie das Passwort Ihres Elasticsearch-Benutzers ändern oder zurücksetzen " -"müssen, verwenden Sie die Schaltfläche \"Passwort zurücksetzen\" in der " -"Tabelle mit den Zugangsdaten. Auf diese Weise wird ein neues Passwort für " -"das betreffende Konto erstellt. Diese Änderung wird sofort durchgeführt. " -"Beachten Sie, dass dies Auswirkungen auf Tools von Drittanbietern haben " -"kann, die mit Ihrer Instanz verbunden sind." - -#: ../system/integrations/exchange.rst:2 -msgid "Exchange" -msgstr "Exchange" +"Aufgrund der Funktionsweise von Core Workflows werden alle Änderungen an " +"Attributen auf dem Anwendungsserver überprüft - bitte lesen Sie :doc:" +"`limitations` für mögliche Probleme." -#: ../system/integrations/exchange.rst:4 +#: ../system/core-workflows/how-do-they-work.rst:12 msgid "" -"With Zammad's Exchange integration, you can easily use existing address " -"books without having to update more than one source." +"Below we're talking about settings that are important and not self-" +"explanatory." msgstr "" -"Mit der Exchange-Integration von Zammad können Sie vorhandene Adressbücher " -"verwenden, ohne mehr als eine Datenquelle aktualisieren zu müssen." +"Im Folgenden geht es um Einstellungen, die wichtig und nicht selbsterklärend " +"sind." -#: ../system/integrations/exchange.rst:7 +#: ../system/core-workflows/how-do-they-work.rst:17 msgid "" -"However, you should refrain from syncing all addresses, as the results may " -"not be what you expect (Exchange collects huge amounts of addresses). A " -"central address book of your company to sync makes more sense, as you can " -"ensure that Zammad gets only the data you need and want. Apart from this, it " -"is even not possible to sync the Global Address List (GAL) of your Exchange " -"system with Zammad." +"Choose the object context you want to run the workflow in. This will decide " +"on your available attributes and actions." msgstr "" -"Sie sollten jedoch davon absehen, alle Adressen zu synchronisieren, da die " -"Ergebnisse möglicherweise nicht das sind, was Sie erwarten (Exchange sammelt " -"riesige Mengen an Adressen). Ein zentrales Adressbuch Ihrer Firma zu " -"synchronisieren ist sinnvoller, da Sie so sicherstellen können, dass Zammad " -"nur die Daten erhält, die Sie brauchen und wollen. Abgesehen davon ist es " -"nicht möglich, die Globale Adressliste (GAL) Ihres Exchange-Systems mit " -"Zammad zu synchronisieren." +"Wählen Sie den Objektkontext, in dem Sie den Workflow ausführen möchten. " +"Dies entscheidet über die verfügbaren Attribute und Aktionen." -#: ../system/integrations/exchange.rst:16 +#: ../system/core-workflows/how-do-they-work.rst:20 +msgid "Ticket objects also have access to the ticket customer." +msgstr "Ticketobjekte haben auch Zugriff auf den Ticketkunden." + +#: ../system/core-workflows/how-do-they-work.rst:25 msgid "" -"**Exchange and LDAP:** The exchange sync can be overruled by Zammad's LDAP " -"integration. If you have the same users in both sources, the LDAP version " -"will always be Zammad's pick." +"Choose in which situation the workflow is applied. Contexts can be combined " +"to avoid duplicate workflows." msgstr "" -"**Exchange und LDAP:** Die Exchange-Synchronisierung kann durch die LDAP-" -"Integration von Zammad übersteuert werden. Wenn Sie die gleichen Benutzer in " -"beiden Quellen haben, wird die LDAP-Version immer \"gewinnen\"." +"Wählen Sie aus, in welcher Situation der Workflow angewendet werden soll. Im " +"Feld \"Kontext\" können mehrere Einträge gewählt werden, um doppelte Core " +"Workflows zu vermeiden." -#: ../system/integrations/exchange.rst:19 +#: ../system/core-workflows/how-do-they-work.rst:30 +msgid "Creation mask" +msgstr "Erstellmaske" + +#: ../system/core-workflows/how-do-they-work.rst:29 msgid "" -"**One way sync:** the Exchange sync is one way. Exchange => Zammad. Changes " -"to your users inside of Zammad might be overwritten by the Exchange sync." +"If selected, your conditions and actions will affect all applicable creation " +"masks." msgstr "" -"**Einweg-Synchronisation:** Die Exchange-Synchronisation ist eine Einweg-" -"Synchronisation. Exchange => Zammad. Änderungen an Ihren Benutzern in von " -"Zammad können durch die Exchange-Synchronisierung überschrieben werden." +"Wenn Sie diese Option wählen, wirken sich Ihre Bedingungen und Aktionen auf " +"alle anwendbaren Erstellungsmasken aus." -#: ../system/integrations/exchange.rst:24 +#: ../system/core-workflows/how-do-they-work.rst:34 +msgid "Edit mask" +msgstr "Bearbeitungsmaske" + +#: ../system/core-workflows/how-do-they-work.rst:33 msgid "" -"To configure Exchange integration, simply go to the System > Integrations > " -"Exchange in the admin panel. Press \"change\" and follow the wizard for " -"adding the needed Exchange information to Zammad. On the last two steps " -"Zammad will ask you for the address book(s) and your desired attribute " -"mapping. By default, Zammad only maps email address, first- and lastname. " -"Technically, you can map any Exchange object to a Zammad user object (this " -"also works for custom objects!)." +"If selected, your conditions and actions will affect all applicable edit " +"masks." msgstr "" -"Um die Exchange-Integration zu konfigurieren, gehen Sie einfach zu System > " -"Integrationen > Exchange in den Admin-Einstellungen. Wählen Sie " -"\"Konfigurieren\" und folgen Sie dem Assistenten, um die benötigten Exchange-" -"Informationen zu Zammad hinzuzufügen. In den letzten beiden Schritten fragt " -"Zammad Sie nach dem Adressbuch und der gewünschten Attributzuordnung. " -"Standardmäßig ordnet Zammad nur E-Mail-Adressen, Vor- und Nachnamen zu. " -"Technisch gesehen können Sie jedes Exchange-Objekt einem Zammad-" -"Benutzerobjekt zuordnen (dies funktioniert auch für benutzerdefinierte " -"Objektattribute!)." +"Wenn Sie diese Option auswählen, wirken sich Ihre Bedingungen und Aktionen " +"auf alle zutreffenden Bearbeitungsmasken aus." -#: ../system/integrations/exchange.rst:35 +#: ../system/core-workflows/how-do-they-work.rst:39 msgid "" -"If the SSL verification fails while connecting to Exchange, Zammad will ask " -"you to turn it off temporarily." +"Zammad differentiates between selected and saved conditions. These can be " +"combined wherever needed." msgstr "" -"Wenn die SSL-Überprüfung bei der Verbindung zu Exchange fehlschlägt, fordert " -"Zammad Sie auf, sie vorübergehend zu deaktivieren." +"Zammad unterscheidet zwischen ausgewählten und gespeicherten Bedingungen. " +"Diese können bei Bedarf kombiniert werden." -#: ../system/integrations/exchange.rst:38 -msgid "" -"Please be aware that **turning off SSL verification is a security risk**. It " -"should only be used temporarily or for testing purposes. If turned off, " -"there is no verification of the certificate, which means that every " -"presented certificate will be accepted." +#: ../system/core-workflows/how-do-they-work.rst:42 +msgid "**⚠️ Restrict workflows to specific roles if needed!**" msgstr "" -"Bitte beachten Sie, dass **das Deaktivieren der SSL-Verifizierung ein " -"Sicherheitsrisiko darstellt**. Es sollte nur vorübergehend oder zu " -"Testzwecken verwendet werden. Wenn diese Option deaktiviert ist, findet " -"keine Überprüfung des Zertifikats statt, was bedeutet, dass jedes vorgelegte " -"Zertifikat akzeptiert wird." +"**⚠️ Schränken Sie Core Workflows auf bestimmte Rollen ein, falls " +"erforderlich!**" -#: ../system/integrations/exchange.rst:43 +#: ../system/core-workflows/how-do-they-work.rst:44 msgid "" -"After pressing Continue, Zammad will check if the configuration is okay. You " -"can then enable Exchange and start your first sync. The sync will then run " -"hourly - if you need to change mappings or the address book(s), you can " -"change the configuration at any time." +"By default and unless configured in conditions, workflow rules are executed " +"for **all roles**. This also affects your customers!" msgstr "" -"Nachdem Sie auf Weiter geklickt haben prüft Zammad, ob die Konfiguration in " -"Ordnung ist. Sie können dann Exchange aktivieren und Ihre erste " -"Synchronisierung starten. Die Synchronisierung läuft dann stündlich - wenn " -"Sie Zuordnungen oder das Adressbuch ändern müssen, können Sie die " -"Konfiguration jederzeit ändern." +"Standardmäßig werden Workflow-Regeln für **alle Rollen** ausgeführt, sofern " +"nichts anderes in den Bedingungen konfiguriert wurde. Dies betrifft auch " +"Ihre Kunden!" -#: ../system/integrations/exchange.rst:50 +#: ../system/core-workflows/how-do-they-work.rst:50 +msgid "Selected Conditions" +msgstr "Ausgewählte Bedingungen" + +#: ../system/core-workflows/how-do-they-work.rst:48 msgid "" -"After the sync has finished, you can find the new Exchange contacts under " -"\"Users\". Zammad integrates them just as normal users." +"These conditions are based on form values and match if an appropriate " +"selection is made (e.g. choosing another group in the ticket without " +"saving). This applies for drafts (active selection) and currently saved " +"values." msgstr "" -"Nach Abschluss der Synchronisierung finden Sie die neuen Exchange-Kontakte " -"unter \"Benutzer\". Zammad integriert sie genauso wie normale Benutzer." +"Diese Bedingungen basieren auf Formularwerten und treffen zu, wenn eine " +"entsprechende Auswahl getroffen wird (z.B. Auswahl einer anderen Gruppe im " +"Ticket ohne Speichern). Dies gilt für Entwürfe (aktive Auswahl) und aktuell " +"gespeicherte Werte." -#: ../system/integrations/exchange.rst:55 +#: ../system/core-workflows/how-do-they-work.rst:64 +msgid "Saved Conditions" +msgstr "Gespeicherte Bedingungen" + +#: ../system/core-workflows/how-do-they-work.rst:53 msgid "" -"In some cases you might see unique IDs as \"Login\" instead of the email " -"address. This is normal and doesn't affect the login or email mapping for " -"that entry." +"These conditions only match if the selected values are stored in the " +"database. It ignores the current value or selection of the field, as long as " +"the changes are not saved (e.g. performing field operations for an existing " +"ticket, which is viewed/opened by an agent)." msgstr "" -"In einigen Fällen können Sie eindeutige IDs als \"Login\" anstelle der E-" -"Mail-Adresse sehen. Dies ist normal und hat keinen Einfluss auf die " -"Zuordnung von Login oder E-Mail für diesen Eintrag." +"Diese Bedingungen treffen nur zu, wenn die ausgewählten Werte in der " +"Datenbank gespeichert sind. Der aktuelle Wert oder die Auswahl des Feldes " +"wird ignoriert, solange die Änderungen nicht gespeichert werden (z.B. bei " +"der Durchführung von Änderungen an einem bestehenden Ticket, das von einem " +"Agenten angesehen/geöffnet wird)." -#: ../system/integrations/github.rst:4 +#: ../system/core-workflows/how-do-they-work.rst:60 msgid "" -"Use GitHub integration to track GitHub issues directly within Zammad " -"tickets. Add issue hyperlinks and get a live summary of metadata like status " -"(open/closed), assignee, labels, and more." +"Keep in mind that the value has to be available in the situation where you " +"need it. Otherwise the condition won't match." msgstr "" -"Verwenden Sie die GitHub-Integration, um GitHub-Issues direkt in Zammad-" -"Tickets zu verfolgen. Fügen Sie Hyperlinks zu Issues hinzu und erhalten Sie " -"eine Live-Zusammenfassung von Metadaten wie Status (offen/geschlossen), " -"zugewiesene Personen, Labels und mehr." +"Denken Sie daran, dass der Wert zum Zeitpunkt der Ausführung verfügbar sein " +"muss. Andernfalls wird die Bedingung nicht erfüllt." -#: ../system/integrations/github.rst:8 -msgid "Please note that our GitHub integration does not support pull requests." +#: ../system/core-workflows/how-do-they-work.rst:63 +msgid "" +"Example: you can't perform any actions with *saved condition* on a ticket in " +"creation, because there are no saved values at that time." msgstr "" -"Bitte beachten Sie, dass unsere GitHub-Integration keine Pull-Requests " -"unterstützt." - -#: ../system/integrations/github.rst:None -msgid "Integration page for GitHub" -msgstr "Seite GitHub-Integration in Zammad" +"Beispiel: Sie können keine Aktionen mit *gespeicherter Bedingung* für ein " +"Ticket durchführen, das gerade erstellt wird, da es zu diesem Zeitpunkt " +"keine gespeicherten Werte gibt." -#: ../system/integrations/github.rst:18 +#: ../system/core-workflows/how-do-they-work.rst:66 msgid "" -"In your GitHub settings, create a new API token under **Developer settings > " -"Personal access tokens > Generate new token**. Leave the **Scopes** section " -"empty." +"You can find a description of the condition operators for core workflows :" +"doc:`here `." msgstr "" -"Erstellen Sie in Ihren GitHub-Einstellungen ein neues API-Token unter " -"**Developer settings > Personal access tokens > Generate new token**. Lassen " -"Sie den Abschnitt **Scopes** leer." - -#: ../system/integrations/github.rst:0 ../system/integrations/gitlab.rst:0 -msgid "Screencast showing how to create a new API token" -msgstr "Screencast zeigt Erstellung eines API-Tokens" +"Eine Beschreibung der Bedingungsoperatoren für Core Workflows finden Sie :" +"doc:`hier `." -#: ../system/integrations/github.rst:27 -msgid "Create a new API key with no scopes/privileges." -msgstr "Erstellen Sie einen neuen API-Schlüssel ohne Scopes/Berechtigungen." +#: ../system/core-workflows/how-do-they-work.rst:72 +msgid "" +"Which actions should we run on the relevant fields? The possible actions " +"depend on the object type. However, usually you can at least change the " +"visibility and whether the field is mandatory." +msgstr "" +"Welche Aktionen sollen ausgeführt werden? Die möglichen Aktionen hängen vom " +"Objekttyp ab. Normalerweise können Sie jedoch mindestens die Sichtbarkeit " +"ändern und angeben, ob das Feld ein Pflichtfeld ist." -#: ../system/integrations/github.rst:29 -msgid "🔒 **Will this work for private repos?**" -msgstr "🔒 **Funktioniert das auch für private Repos?**" +#: ../system/core-workflows/how-do-they-work.rst:76 +msgid "Be aware that actions are not available for **related** context." +msgstr "" +"Beachten Sie, dass Aktionen nicht verfügbar sind für in Beziehungen stehende " +"Objekte." -#: ../system/integrations/github.rst:31 +#: ../system/core-workflows/how-do-they-work.rst:78 msgid "" -"No. To link private repo issues, **use the** ``repo`` **scope instead**. " -"Bear in mind that the resulting token will have `lots of permissions that it " -"doesn't actually need `_, which presents a security risk if your token ever falls into " -"the wrong hands." +"**Example:** Let's assume you are working in the ticket context. While you " +"can have customer *conditions*, you *can't adjust* objects with actions in " +"that scope. That's because this wouldn't have any impact on the ticket " +"dialog. Of course all ticket attributes (state, owner, ...) are available." msgstr "" -"Nein. Um private Repos zu verknüpfen, **verwenden Sie stattdessen den** " -"``repo`` **Scope**. Denken Sie daran, dass das resultierende Token `viele " -"Berechtigungen beinhaltet, die es eigentlich nicht braucht `_. Das stellt ein " -"Sicherheitsrisiko dar, falls Ihr Token in die falschen Hände geraten sollte." +"**Beispiel:** Nehmen wir an, Sie arbeiten im Ticket-Kontext. Sie können zwar " +"*Bedingungen* haben, die sich auf Kunden beziehen, aber Sie können *keine " +"Anpassungen mit Aktionen* in diesem Kontext vornehmen. Das liegt daran, dass " +"dies keine Auswirkung auf den Ticket-Dialog haben würde. Natürlich sind alle " +"Ticket-Attribute (Status, Besitzer, ...) verfügbar." -#: ../system/integrations/github.rst:37 +#: ../system/core-workflows/how-do-they-work.rst:84 msgid "" -"Unfortunately, because of how GitHub's OAuth token scopes are set up, this " -"is the only way to link issues on private repos." +"Please also have a look at our :doc:`limitations` to be safe from surprises." msgstr "" -"Leider ist dies aufgrund der Art und Weise, wie die OAuth-Token-Bereiche von " -"GitHub eingerichtet sind, die einzige Möglichkeit, Issues in privaten Repos " -"zu verknüpfen." +"Bitte beachten Sie auch unsere :doc:`limitations`, um vor Überraschungen " +"sicher zu sein." -#: ../system/integrations/github.rst:40 -msgid "Enter your new API token in Zammad and enable GitHub integration." -msgstr "" -"Geben Sie Ihr neues API-Token in Zammad ein und aktivieren Sie die GitHub-" -"Integration." +#: ../system/core-workflows/how-do-they-work.rst:88 +msgid "Available Operators" +msgstr "Verfügbare Operatoren" -#: ../system/integrations/github.rst:0 -msgid "Screencast showing how to configure Zammad's GitHub integration" -msgstr "" -"Screencast zeigt, wie die GitHub-Integration von Zammad konfiguriert wird" +#: ../system/core-workflows/how-do-they-work.rst:90 +msgid "The availability of operators depends on the object type and scope." +msgstr "Die Verfügbarkeit von Operatoren hängt von dem Objekt ab." -#: ../system/integrations/github.rst:47 +#: ../system/core-workflows/how-do-they-work.rst:94 msgid "" -"Use the default API endpoint (``https://api.github.com/graphql``) unless " -"you're using GitHub Enterprise Server." +"Please note that actions may or may not restrict API based access to " +"attributes. We're displaying the following icons for your overview to " +"understand these limits better:" msgstr "" -"Verwenden Sie den Standard-API-Endpunkt (``https://api.github.com/" -"graphql``), es sei denn, Sie verwenden GitHub Enterprise Server." +"Bitte beachten Sie, dass Aktionen den API-basierten Zugriff auf Attribute " +"einschränken können, aber nicht müssen. Wir zeigen Ihnen die folgenden " +"Symbole an, damit Sie die Einschränkungen besser verstehen:" -#: ../system/integrations/github.rst:50 -msgid "" -"Once completed, a new GitHub issues tab will appear in the ticket pane. 🎉" -msgstr "" -"Sobald Sie das erledigt haben wird eine neue Registerkarte für GitHub-Issues " -"im Ticketbereich angezeigt. 🎉" +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|api| This icon indicates the action affects the API." +msgstr "|api| Dieses Symbol zeigt an, dass die Aktion die API betrifft." -#: ../system/integrations/github.rst:59 ../system/integrations/gitlab.rst:52 -msgid "Token verification is taking a long time" -msgstr "Die Token-Verifizierung dauert sehr lange" +#: ../system/core-workflows/how-do-they-work.rst:163 +msgid "api" +msgstr "api" -#: ../system/integrations/github.rst:56 ../system/integrations/gitlab.rst:49 -msgid "" -"Slight delays are normal (<2 min.), especially for systems under heavy load." +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|ui| This icon indicates the action only affects the web interface." msgstr "" -"Leichte Verzögerungen sind normal (<2 Min.), insbesondere bei stark " -"belasteten Systemen." +"|ui| Dieses Symbol zeigt an, dass die Aktion nur die Weboberfläche betrifft." -#: ../system/integrations/github.rst:58 -msgid "" -"Self-hosted administrators, please check your network settings to ensure " -"that your Zammad server can reach ``api.github.com``." -msgstr "" -"Administratoren von selbst gehosteten Instanzen sollten Ihre " -"Netzwerkeinstellungen prüfen und sicherstellen, dass Ihr Zammad-Server ``api." -"github.com`` erreichen kann." +#: ../system/core-workflows/how-do-they-work.rst:167 +msgid "ui" +msgstr "ui" -#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 -msgid "I reloaded the page and now the API token is gone" -msgstr "" -"Ich habe die Seite neu geladen, und jetzt ist das API-Token verschwunden" +#: ../system/core-workflows/how-do-they-work.rst:102 +msgid "show |ui|" +msgstr "anzeigen |ui|" -#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 -msgid "" -"This may indicate that Zammad is still verifying your API token. Try " -"reloading the page again in a couple minutes." -msgstr "" -"Dies kann darauf hindeuten, dass Zammad noch dabei ist, Ihr API-Token zu " -"verifizieren. Versuchen Sie, die Seite in ein paar Minuten noch einmal zu " -"laden." +#: ../system/core-workflows/how-do-they-work.rst:102 +msgid "Display the chosen field. Allows setting of values." +msgstr "Zeigt das ausgewählte Feld an. Ermöglicht die Einstellung von Werten." -#: ../system/integrations/gitlab.rst:2 -msgid "GitLab" -msgstr "GitLab" +#: ../system/core-workflows/how-do-they-work.rst:109 +msgid "hide |ui|" +msgstr "verstecken |ui|" -#: ../system/integrations/gitlab.rst:4 +#: ../system/core-workflows/how-do-they-work.rst:105 msgid "" -"Use GitLab integration to track GitLab issues directly within Zammad " -"tickets. Add issue hyperlinks and get a live summary of metadata like status " -"(open/closed), assignee, labels, and more." +"Hide the chosen field. However, it technically still allows setting the " +"field." msgstr "" -"Verwenden Sie die GitLab-Integration, um GitLab-Issues direkt in Zammad-" -"Tickets zu verfolgen. Fügen Sie Hyperlinks zu Issues hinzu und erhalten Sie " -"eine Live-Zusammenfassung von Metadaten wie Status (offen/geschlossen), " -"zugewiesene Personen, Labels und mehr." +"Ausblenden des gewählten Feldes. Technisch gesehen kann das Feld aber immer " +"noch eingestellt werden." -#: ../system/integrations/gitlab.rst:8 +#: ../system/core-workflows/how-do-they-work.rst:108 msgid "" -"Please note that our GitLab integration does not support merge requests." +"Please note that the field is **not** gone and still contains an existing " +"value (if set)! Consider *remove* instead, if you want this field to be gone." msgstr "" -"Bitte beachten Sie, dass unsere GitLab-Integration keine Merge Requests " -"unterstützt." +"Bitte beachten Sie, dass das Feld **nicht** verschwunden ist und immer noch " +"einen vorhandenen Wert enthält (falls gesetzt)! Ziehen Sie stattdessen " +"*entfernen* in Betracht, wenn Sie wollen, dass dieses Feld wirklich " +"verschwindet." -#: ../system/integrations/gitlab.rst:None -msgid "Integration page for GitLab" -msgstr "Seite GitLab-Integration in Zammad" +#: ../system/core-workflows/how-do-they-work.rst:112 +msgid "remove |ui|" +msgstr "entfernen |ui|" -#: ../system/integrations/gitlab.rst:18 -msgid "" -"In your GitLab preferences, create a new API token under **Access Tokens**." -msgstr "" -"Erstellen Sie in Ihren GitLab-Einstellungen ein neues API-Token unter " -"**Access Tokens**." +#: ../system/core-workflows/how-do-they-work.rst:112 +msgid "Entirely removes the field. The field value will not be evaluated." +msgstr "Entfernt das Feld vollständig. Der Feldwert wird nicht ausgewertet." -#: ../system/integrations/gitlab.rst:20 -msgid "Under **Select scopes**, choose ``read_api`` only." -msgstr "Wählen Sie ausschließlich ``read_api ``unter **Select scopes**." +#: ../system/core-workflows/how-do-they-work.rst:115 +msgid "set mandatory |ui| |api|" +msgstr "als erforderlich festlegen |ui| |api|" -#: ../system/integrations/gitlab.rst:27 -msgid "🔒 **If you wish to link issues on any private repos...**" -msgstr "🔒 **Wenn Sie Issues in privaten Repos verlinken möchten...**" +#: ../system/core-workflows/how-do-they-work.rst:115 +msgid "Sets the field to mandatory." +msgstr "Definiert das Feld als Pflichtfeld." -#: ../system/integrations/gitlab.rst:29 -msgid "Your API token must belong to an account with access to those repos." -msgstr "Ihr API-Token muss zu einem Konto mit Zugriff auf diese Repos gehören." +#: ../system/core-workflows/how-do-they-work.rst:118 +msgid "set optional |ui| |api|" +msgstr "als optional festlegen |ui| |api|" -#: ../system/integrations/gitlab.rst:31 -msgid "Enter your new API token in Zammad and enable GitLab integration." -msgstr "" -"Geben Sie Ihr neues API-Token in Zammad ein und aktivieren Sie die GitLab-" -"Integration." +#: ../system/core-workflows/how-do-they-work.rst:118 +msgid "Sets the field to optional." +msgstr "Definiert das Feld als optionales Feld." -#: ../system/integrations/gitlab.rst:0 -msgid "Screencast showing how to configure Zammad's GitLab integration" -msgstr "Screencast zeigt die Konfiguration der GitHub-Integration in Zammad" +#: ../system/core-workflows/how-do-they-work.rst:124 +msgid "add option |ui| |api|" +msgstr "Option hinzufügen |ui| |api|" -#: ../system/integrations/gitlab.rst:40 -msgid "" -"Use the default API endpoint (``https://gitlab.com/api/graphql``) unless " -"you're a self-hosted GitLab user." -msgstr "" -"Verwenden Sie den Standard-API-Endpunkt (``https://gitlab.com/api/" -"graphql``), es sei denn, Sie hosten GitLab selbst." +#: ../system/core-workflows/how-do-they-work.rst:121 +msgid "Allows adding options to tree selects or selects." +msgstr "Ermöglicht das Hinzufügen von Optionen zu Auswahlen und Baumauswahlen." -#: ../system/integrations/gitlab.rst:43 +#: ../system/core-workflows/how-do-they-work.rst:123 msgid "" -"Once completed, a new GitLab issues tab will appear in the ticket pane. 🎉" +"You have to use the \"remove option\" before performing this action. It " +"allows you to use *existing* configured values." msgstr "" -"Sobald Sie das erledigt haben wird eine neue Registerkarte für GitLab-Issues " -"im Ticketbereich angezeigt. 🎉" +"Bevor Sie diese Aktion durchführen, müssen Sie die Option \"Entfernen\" " +"verwenden. Im Anschluss können Sie damit *vorhandene* konfigurierte Werte " +"verwenden." -#: ../system/integrations/gitlab.rst:51 +#: ../system/core-workflows/how-do-they-work.rst:128 +msgid "remove option |ui| |api|" +msgstr "Option entfernen |ui| |api|" + +#: ../system/core-workflows/how-do-they-work.rst:127 msgid "" -"Self-hosted administrators, please check your network settings to ensure " -"that your Zammad server can reach ``gitlab.com``." +"Allows removing options from tree selects or selects. It allows you to use " +"*existing* configured values." msgstr "" -"Administratoren von selbst gehosteten Zammad-Instanzen sollten Ihre " -"Netzwerkeinstellungen prüfen und sicherstellen, dass Ihr Zammad-Server " -"``gitlab.com`` erreichen kann." +"Ermöglicht das Entfernen von Optionen aus Baumauswahl oder Auswahl-Feldern. " +"Damit können Sie *vorhandene* konfigurierte Werte verwenden." -#: ../system/integrations/i-doit.rst:2 -msgid "i-doit" -msgstr "i-doit" +#: ../system/core-workflows/how-do-they-work.rst:134 +msgid "set fixed to |ui| |api|" +msgstr "fest eingestellt auf |ui| |api|" -#: ../system/integrations/i-doit.rst:4 +#: ../system/core-workflows/how-do-they-work.rst:131 +msgid "Reduces the available options by your selection." +msgstr "Reduziert die verfügbaren Optionen um Ihre Auswahl." + +#: ../system/core-workflows/how-do-they-work.rst:133 msgid "" -"`i-doit `_ is an open-source **configuration " -"management database** - in other words, a tool for keeping tabs on every " -"single piece of your physical and digital infrastructure, from network " -"equipment to virtual machines on down to the faceplates on your rack shelves " -"and more." +"This reduces your workflows in terms of *add option* and *remove option*." msgstr "" -"`i-doit `_ ist eine quelloffene " -"**Konfigurationsverwaltungsdatenbank** - mit anderen Worten, ein Tool, mit " -"dem Sie jedes einzelne Teil Ihrer physischen und digitalen Infrastruktur im " -"Auge behalten können, von der Netzwerkausrüstung über virtuelle Maschinen " -"bis hin zu den Frontblenden Ihrer Rack-Regale und mehr." +"Dies reduziert Ihre Workflows bzgl. *Option hinzufügen* und *Option " +"entfernen*." -#: ../system/integrations/i-doit.rst:10 +#: ../system/core-workflows/how-do-they-work.rst:137 +msgid "fill in |ui|" +msgstr "befüllen mit |ui|" + +#: ../system/core-workflows/how-do-they-work.rst:137 +msgid "Allows filling in of string and integer fields with your values." +msgstr "Ermöglicht die Befüllung von Text- und Zahlen-Feldern mit einem Wert." + +#: ../system/core-workflows/how-do-they-work.rst:141 +msgid "fill in empty |ui|" +msgstr "befüllen mit (wenn leer) |ui|" + +#: ../system/core-workflows/how-do-they-work.rst:140 msgid "" -"What's that got to do with Zammad? Well, if you used tickets to track issues " -"with all that hardware, you might start wishing there was a way they could " -"talk to each other." +"Allows filling in of string and integer fields with your values **if the " +"field is empty**." msgstr "" -"Was hat das mit Zammad zu tun? Wenn Sie mit Tickets Probleme mit Ihrer " -"Hardware verfolgen wünschen Sie sich vielleicht, dass es eine Möglichkeit " -"gibt, dass beide Systeme miteinander kommunizieren." +"Ermöglicht die Befüllung von Text- und Zahlen-Feldern mit einem Wert **wenn " +"das Feld leer ist**." -#: ../system/integrations/i-doit.rst:14 -msgid "Zammad gives you two:" -msgstr "Es gibt zwei Möglichkeiten:" +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "select |ui|" +msgstr "auswählen |ui|" -#: ../system/integrations/i-doit.rst:17 -msgid "1. Add i-doit Links to Zammad Tickets" -msgstr "1. i-doit Links zu Zammad-Tickets hinzufügen" +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "Select a specific value within a select, tree select or boolean field." +msgstr "" +"Wählen Sie einen bestimmten Wert innerhalb eines Auswahl-, Baumauswahl- oder " +"Boolean-Feldes aus." -#: ../system/integrations/i-doit.rst:20 ../system/integrations/i-doit.rst:80 -msgid "What Users See" -msgstr "Was die Nutzer sehen" +#: ../system/core-workflows/how-do-they-work.rst:153 +msgid "auto select |ui|" +msgstr "automatisch auswählen |ui|" -#: ../system/integrations/i-doit.rst:26 -msgid "i-doit integration in Zammad's ticket pane" -msgstr "Integration von i-doit im Zammad Ticketbereich" +#: ../system/core-workflows/how-do-they-work.rst:147 +msgid "Helps users with tree select and select fields:" +msgstr "Hilft den Benutzern bei Baumauswahl- und Auswahlfeldern:" -#: ../system/integrations/i-doit.rst:26 +#: ../system/core-workflows/how-do-they-work.rst:149 msgid "" -"The i-doit integration will appear under a new 🖨 tab in the ticket pane." +"If the field has only one option available for selection and no value yet, " +"the value will be automatically set." msgstr "" -"Die i-doit-Integration wird in einem neuen 🖨 Tab im Ticketbereich angezeigt." +"Wenn für das Feld nur eine Option zur Auswahl steht und noch kein Wert " +"vorhanden ist, wird der Wert automatisch gesetzt." -#: ../system/integrations/i-doit.rst:28 +#: ../system/core-workflows/how-do-they-work.rst:152 msgid "" -"i-doit integration puts a new tab in Zammad's ticket pane where you can add " -"links to existing i-doit devices for easy reference. (See our :user-docs:" -"`user documentation ` to learn " -"how it works in practice)." +"This option only works if you have one value and doesn't work if there is " +"more than one option available." msgstr "" -"Die i-doit-Integration fügt einen neuen Tab im Ticketbereich von Zammad ein, " -"in dem Sie Links zu vorhandenen i-doit-Geräten hinzufügen können, um sie " -"leichter zu finden. (Siehe unsere :user-docs:`Benutzerdokumentation ` für weitere Informationen zur " -"Handhabung in der Praxis)." +"Diese Option funktioniert nur, wenn Sie genau einen Wert haben. Sie " +"funktioniert nicht, wenn mehr als eine Option verfügbar ist." -#: ../system/integrations/i-doit.rst:36 ../system/integrations/i-doit.rst:93 -msgid "How to Set it Up" -msgstr "Einrichtung" +#: ../system/core-workflows/how-do-they-work.rst:157 +msgid "set readonly |ui|" +msgstr "als schreibgeschützt festlegen |ui|" -#: ../system/integrations/i-doit.rst:38 +#: ../system/core-workflows/how-do-they-work.rst:156 msgid "" -"It requires i-doit's `API Add-on `_. Make sure to have it properly set up. Use the following setting:" +"Allows you to display an attribute as read only (which means no changes are " +"possible)." msgstr "" -"Das `API Add-on `_ von i-" -"doit ist dazu erforderlich. Stellen Sie sicher, dass es richtig eingerichtet " -"ist. Verwenden Sie die folgende Einstellung:" - -#: ../system/integrations/i-doit.rst:42 -msgid "Active: ``Yes``" -msgstr "Aktiv: ``Ja``" +"Ermöglicht die schreibgeschützte Anzeige eines Attributs (was bedeutet, dass " +"keine Änderungen möglich sind)." -#: ../system/integrations/i-doit.rst:43 -msgid "Enforce authentication by username and password: ``No``" -msgstr "Authentifizierung mit Benutzername und Passwort erzwingen: ``Nein``" +#: ../system/core-workflows/how-do-they-work.rst:161 +msgid "unset readonly |ui|" +msgstr "als änderbar festlegen |ui|" -#: ../system/integrations/i-doit.rst:45 +#: ../system/core-workflows/how-do-they-work.rst:160 msgid "" -"To set it up, enable the integration in the Zammad admin panel under " -"**System > Integrations > i-doit**:" +"In case a workflow set the field in question to read only, you can undo this " +"with option above." msgstr "" -"Um sie einzurichten, aktivieren Sie die Integration im Zammad-" -"Administrationsbereich unter **System > Integrationen > i-doit**:" - -#: ../system/integrations/i-doit.rst:None -msgid "i-doit settings within the integration pages" -msgstr "i-doit-Einstellungen unter Integrationen" - -#: ../system/integrations/i-doit.rst:53 -msgid "The root URL of your i-doit installation." -msgstr "Die URL Ihrer i-doit-Installation." +"Falls ein Workflow das betreffende Feld auf schreibgeschützt gesetzt hat, " +"können Sie dies mit der obigen Option rückgängig machen." -#: ../system/integrations/i-doit.rst:62 -msgid "API token" -msgstr "API-Token" +#: ../system/core-workflows/how-do-they-work.rst:172 +msgid "Stop after match" +msgstr "Nach Treffer stoppen" -#: ../system/integrations/i-doit.rst:56 +#: ../system/core-workflows/how-do-they-work.rst:174 msgid "" -"Found in the i-doit admin panel under **Interfaces / external data > JSON-" -"RPC API > Common Settings**." -msgstr "" -"Zu finden im i-doit Admin Panel unter **Schnittstellen / externe Daten > " -"JSON-RPC API > Allgemeine Einstellungen**." - -#: ../system/integrations/i-doit.rst:0 -msgid "i-doit administration interface with API configuration" -msgstr "i-doit Verwaltungsoberfläche mit API-Konfiguration" - -#: ../system/integrations/i-doit.rst:67 -msgid "Client ID" -msgstr "Client-ID" - -#: ../system/integrations/i-doit.rst:65 -msgid "A unique name to identify Zammad within i-doit." +"Here you can decide if other workflows are executed after the current one." msgstr "" -"Ein eindeutiger Name zur Identifizierung von Zammad innerhalb von i-doit." +"Hier können Sie festlegen, ob andere Workflows nach dem aktuellen ausgeführt " +"werden." -#: ../system/integrations/i-doit.rst:67 -msgid "(Zammad does not require you to enter a value here, but i-doit might!)" +#: ../system/core-workflows/how-do-they-work.rst:176 +msgid "" +"If set to ``no`` (default), further workflows will be executed if they match " +"the condition. In this case, it is possible that your actions from the " +"current workflow can be overwritten by another workflow." msgstr "" -"(Zammad verlangt nicht, dass Sie hier einen Wert eingeben, aber i-doit " -"schon!)" +"Bei der Einstellung ``Nein`` (Standard) werden weitere Workflows ausgeführt, " +"wenn sie die Bedingung erfüllen. In diesem Fall ist es möglich, dass Ihre " +"Aktionen aus dem aktuellen Workflow von einem anderen Workflow überschrieben " +"werden." -#: ../system/integrations/i-doit.rst:70 +#: ../system/core-workflows/how-do-they-work.rst:180 msgid "" -"Here you can decide if the certificate of your i-doit system has to be " -"verified or not. In case you are using custom certificates, please have a " -"look at :doc:`how to add them to Zammad `." +"If set to ``yes``, no further worflows will be executed after the current " +"one." msgstr "" -"Hier können Sie festlegen, ob das Zertifikat Ihres i-doit-Systems überprüft " -"werden soll oder nicht. Falls Sie benutzerdefinierte Zertifikate verwenden, " -"sehen Sie sich bitte an, wie man diese :doc:`in Zammad hinterlegt `." - -#: ../system/integrations/i-doit.rst:77 -msgid "2. List / Create Zammad Tickets in i-doit" -msgstr "2. Zammad-Tickets in i-doit auflisten / erstellen" +"Wird der Wert auf ``Ja`` gesetzt, werden nach dem aktuellen keine weiteren " +"Workflows mehr ausgeführt." -#: ../system/integrations/i-doit.rst:None -msgid "Zammad integration in i-doit's device view" -msgstr "Zammad-Integration in der Geräteansicht von i-doit" +#: ../system/core-workflows/how-do-they-work.rst:184 +msgid "Priority" +msgstr "Priorität" -#: ../system/integrations/i-doit.rst:86 +#: ../system/core-workflows/how-do-they-work.rst:186 msgid "" -"i-doit's ticket system integration gives you a way to see all the tickets " -"for a given device without ever leaving i-doit. (See our :user-docs:`user " -"documentation ` to learn how it " -"works in practice)." +"You can define the sequence, in which the workflows are executed. The " +"default value is ``500``." msgstr "" -"Die Integration des Ticketsystems in i-doit bietet Ihnen die Möglichkeit, " -"alle Tickets für ein bestimmtes Gerät einzusehen, ohne i-doit zu verlassen " -"(siehe :user-docs:`i-doit Benutzerdokumentation `, um es im praktischen Einsatz zu sehen)." +"Sie können die Reihenfolge festlegen, in der die Arbeitsabläufe ausgeführt " +"werden. Der Standardwert ist ``500``." -#: ../system/integrations/i-doit.rst:95 +#: ../system/core-workflows/how-do-they-work.rst:189 msgid "" -"Enable this integration in the i-doit admin panel under **Interfaces / " -"external data > Trouble Ticket System (TTS) > Configuration**:" +"The workflows are executed in ascending order by their priority. That means " +"lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." msgstr "" -"Aktivieren Sie diese Integration im i-doit Admin Panel unter " -"**Schnittstellen / externe Daten > Trouble Ticket System (TTS) > " -"Konfiguration**:" - -#: ../system/integrations/i-doit.rst:None -msgid "i-doit administration interface with TTS configuration" -msgstr "i-doit Verwaltungsoberfläche mit TTS-Konfiguration" - -#: ../system/integrations/i-doit.rst:104 -msgid "TTS-Type" -msgstr "TTS-Typ" - -#: ../system/integrations/i-doit.rst:104 -msgid "``Zammad``" -msgstr "``Zammad``" - -#: ../system/integrations/i-doit.rst:115 -msgid "Username / Password" -msgstr "Benutzername/Passwort" +"Die Workflows werden in aufsteigender Reihenfolge nach ihrer Priorität " +"ausgeführt. Das heißt, niedrigere Werte (z.B. ``100``) werden vor höheren (z." +"B. ``999``) ausgeführt." -#: ../system/integrations/i-doit.rst:107 -msgid "Login credentials for a Zammad agent." -msgstr "Anmeldedaten für einen Zammad-Agenten." +#: ../system/core-workflows/learn-by-example.rst:2 +msgid "Learn by Example" +msgstr "Lernen Sie anhand von Beispielen" -#: ../system/integrations/i-doit.rst:109 +#: ../system/core-workflows/learn-by-example.rst:4 msgid "" -"This agent must have **read permission** for all :doc:`groups ` that plan on using the i-doit integration." +"This page provides some basic examples for Core Workflows. Of course you can " +"build much more complex workflows if needed." msgstr "" -"Dieser Agent muss **Leseberechtigung** für alle :doc:`Gruppen ` haben, die die i-doit-Integration nutzen wollen." +"Diese Seite enthält einige grundlegende Beispiele für Core Workflows. " +"Natürlich können Sie bei Bedarf auch komplexere Workflows erstellen." -#: ../system/integrations/i-doit.rst:113 +#: ../system/core-workflows/learn-by-example.rst:7 msgid "" -"You may even wish to create a dedicated agent account just for this " -"integration (otherwise, if the agent ever changes her password, you will " -"have to remember to update it here)." +"To learn about Core Workflows in detail, first go to :doc:`how-do-they-work`." msgstr "" -"Möglicherweise möchten Sie sogar ein eigenes Konto für den Agenten " -"einrichten (andernfalls müssen Sie daran denken, das Passwort zu " -"aktualisieren, wenn der Agent sein Passwort ändert)." - -#: ../system/integrations/i-doit.rst:117 -msgid "URL incl. protocol" -msgstr "URL mit Protokoll" - -#: ../system/integrations/i-doit.rst:118 -msgid "``https://your.zammad.domain``" -msgstr "``https://ihre.zammad.domain``" +"Um mehr über Core Workflows im Detail zu erfahren, gehen Sie zuerst zu :doc:" +"`how-do-they-work`." -#: ../system/integrations/index.rst:2 -msgid "Integrations" -msgstr "Integrationen" +#: ../system/core-workflows/learn-by-example.rst:10 +msgid "Group Based Examples" +msgstr "Gruppenbasierte Beispiele" -#: ../system/integrations/index.rst:4 +#: ../system/core-workflows/learn-by-example.rst:12 msgid "" -"Zammad offers numerous integrations that add rich features to your instance." +"All following workflows have the same base configurations. The workflow may " +"not use them all." msgstr "" -"Zammad bietet zahlreiche Integrationen, die Ihre Instanz um umfangreiche " -"Funktionen erweitern." +"Alle folgenden Workflows haben die gleichen Basiskonfigurationen. Der " +"Workflow muss nicht alle Konfigurationen verwenden." -#: ../system/integrations/index.rst:6 -msgid "We're still working on this part of our documentation, stay tight!" -msgstr "" -"Wir arbeiten noch an diesem Teil unserer Dokumentation, bleiben Sie dran!" +#: ../system/core-workflows/learn-by-example.rst:15 +msgid "Groups:" +msgstr "Gruppen:" -#: ../system/integrations/index.rst:10 -msgid "Integrations for Phone Systems" -msgstr "Integrationen für Telefonanlagen" +#: ../system/core-workflows/learn-by-example.rst:20 +msgid "Attributes:" +msgstr "Attribute:" -#: ../system/integrations/index.rst:14 -msgid "" -"Your VoIP provider or telephony system is not listed? Possibly your provider " -"supports Zammad by using the generic CTI - if you're unsure ask your " -"provider." -msgstr "" -"Ihr VoIP-Anbieter oder Ihre Telefonanlage ist nicht aufgeführt? " -"Möglicherweise unterstützt Ihr Anbieter Zammad durch die Verwendung der " -"generischen CTI - wenn Sie unsicher sind, fragen Sie Ihren Anbieter." +#: ../system/core-workflows/learn-by-example.rst:22 +msgid "Category (Single tree selection field, not mandatory, agents only)" +msgstr "Kategorie (Einfach-Baumauswahl-Feld, kein Pflichtfeld, nur Agenten)" -#: ../system/integrations/index.rst:18 +#: ../system/core-workflows/learn-by-example.rst:23 msgid "" -"Provider does not support Zammad? Consider creating a `feature request in " -"the Zammad Community `_." +"Approved (Boolean field, not mandatory, not shown, ``false`` as default)" msgstr "" -"Der Anbieter unterstützt Zammad nicht? Sie können gerne ein `Feature Request " -"in der Zammad Community `_ erstellen." - -#: ../system/integrations/index.rst:31 -msgid "Integrations for Authentication and Customers" -msgstr "Integrationen für Authentifizierung und Kunden" - -#: ../system/integrations/index.rst:44 -msgid "Integrations for Monitoring Systems" -msgstr "Integrationen für Monitoring-Systeme" - -#: ../system/integrations/index.rst:46 -msgid "This section currently misses the following integrations:" -msgstr "In diesem Abschnitt fehlen derzeit die folgenden Integrationen:" - -#: ../system/integrations/index.rst:48 -msgid "Icinga" -msgstr "Icinga" - -#: ../system/integrations/index.rst:49 -msgid "Monit" -msgstr "Monit" +"Genehmigt (Boolean-Feld, kein Pflichtfeld, versteckt, ``false`` als Standard)" -#: ../system/integrations/index.rst:50 -msgid "Nagios" -msgstr "Nagios" +#: ../system/core-workflows/learn-by-example.rst:24 +msgid "Operating System (Text field, not mandatory, not shown)" +msgstr "Betriebssystem (Textfeld, kein Pflichtfeld, versteckt)" -#: ../system/integrations/index.rst:60 -msgid "Integrations for Issue Trackers" -msgstr "Integrationen für Issue-Tracker" +#: ../system/core-workflows/learn-by-example.rst:25 +msgid "Software used (Single selection field, not mandatory, not shown)" +msgstr "Verwendete Software (Einfachauswahl-Feld, kein Pflichtfeld, versteckt)" -#: ../system/integrations/index.rst:70 -msgid "Other Integrations" -msgstr "Andere Integrationen" +#: ../system/core-workflows/learn-by-example.rst:68 +msgid "Group specific values and fields" +msgstr "Gruppenspezifische Werte und Felder" -#: ../system/integrations/index.rst:72 +#: ../system/core-workflows/learn-by-example.rst:28 msgid "" -"This section will hold any other integration that can't be grouped up (yet)." +"This workflow set depends on the category field. It reduces the available " +"set of values based on the group selected." msgstr "" -"In diesem Abschnitt werden alle anderen Integrationen aufgeführt, die (noch) " -"nicht in Gruppen zusammengefasst werden können." +"Dieser Workflow hängt vom Kategorie-Feld ab. Es verringert die möglichen " +"auswählbaren Werte auf der Grundlage der ausgewählten Gruppe." -#: ../system/integrations/ldap/index.rst:2 -msgid "LDAP / Active Directory" -msgstr "LDAP/Active Directory" +#: ../system/core-workflows/learn-by-example.rst:33 +msgid "Workflow 2nd Level group" +msgstr "Workflow 2nd Level Gruppe" -#: ../system/integrations/ldap/index.rst:4 +#: ../system/core-workflows/learn-by-example.rst:35 msgid "" -"Zammad comes with a powerful LDAP integration that allows you to have a " -"single source of truth. By this you reduce the number of login credentials " -"your user has to remember." +"This reduces the category options to ``2nd Level/*``, ``Internal/*`` and " +"``Others``. It also sets further required fields to mandatory and visible." msgstr "" -"Zammad verfügt über eine leistungsstarke LDAP-Integration, die es Ihnen " -"ermöglicht, eine einzige Datenquelle zu haben. Auf diese Weise reduzieren " -"Sie die Anzahl der Anmeldeinformationen, die sich Ihre Benutzer merken " -"müssen." +"Dies reduziert die Kategorieoptionen auf ``2nd Level/*``, ``Internal/*`` und " +"``Others``. Außerdem werden weitere erforderliche Felder als Pflichtfelder " +"und sichtbar gesetzt." -#: ../system/integrations/ldap/index.rst:10 +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for 2nd level" +msgstr "Beispiel-Workflow, der bestimmte Werte und Felder für 2nd Level zeigt" + +#: ../system/core-workflows/learn-by-example.rst:43 +msgid "Workflow Support group" +msgstr "Workflow Support Gruppe" + +#: ../system/core-workflows/learn-by-example.rst:45 msgid "" -"The LDAP source is also a perfect candidate for Zammad's :docs:`Kerberos " -"Single Sign-On ` but also works as addition " -"to other :doc:`/settings/security/third-party`." +"This reduces the category options to ``Support/*``, ``Internal/*`` and " +"``Others``. It also sets further required fields to visible." msgstr "" -"Die LDAP-Quelle ist auch ein perfekter Kandidat für Zammads :docs:`Kerberos " -"Single Sign-On `, funktioniert aber auch als " -"Ergänzung zu anderen :doc:`/settings/security/third-party`." +"Dieser Workflow reduziert die möglichen Kategorien auf ``Support/*``, " +"``Intern/*`` und ``Others``. Außerdem werden weitere Felder auf sichtbar und " +"als Pflichtfeld gesetzt." -#: ../system/integrations/ldap/index.rst:None -msgid "Zammands LDAP management page" -msgstr "Zammands LDAP-Einstellungsseite" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for support" +msgstr "Beispiel-Workflow, der bestimmte Werte und Felder für Support zeigt" -#: ../system/integrations/ldap/index.rst:25 -msgid "📝 :doc:`manage`" -msgstr "📝 :doc:`manage`" +#: ../system/core-workflows/learn-by-example.rst:53 +msgid "Workflow Sales group" +msgstr "Workflow Sales Gruppe" -#: ../system/integrations/ldap/index.rst:25 -msgid "Add, modify, remove or re-arrange your LDAP-Sources as needed." +#: ../system/core-workflows/learn-by-example.rst:55 +msgid "" +"This reduces the category options to ``Sales/*``, ``Internal/*`` and " +"``Others``." msgstr "" -"Sie können Ihre LDAP-Quellen nach Bedarf hinzufügen, ändern, entfernen oder " -"neu anordnen." +"Dies reduziert die möglichen Kategorien auf ``Sales/*``, ``Internal/*`` und " +"``Others``." -#: ../system/integrations/ldap/index.rst:30 -msgid "Before you continue, please note the following limitations." -msgstr "" -"Bevor Sie fortfahren, beachten Sie bitte die folgenden Einschränkungen." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for sales" +msgstr "Beispiel-Workflow, der bestimmte Werte und Felder für Sales zeigt" -#: ../system/integrations/ldap/index.rst:32 -msgid "Mapping / Synchronizing organizations is not possible" -msgstr "Mapping / Synchronisation von Organisationen ist nicht möglich" +#: ../system/core-workflows/learn-by-example.rst:68 +#: ../system/integrations/slack.rst:88 +msgid "The Result" +msgstr "Das Ergebnis" -#: ../system/integrations/ldap/index.rst:36 +#: ../system/core-workflows/learn-by-example.rst:63 msgid "" -"You may want to consider using domain based assignments to overcome this " -"issue. Learn more on :doc:`/manage/organizations/index`." +"This is what the agent would experience with the above workflows in place." msgstr "" -"Um dieses Problem zu umgehen können Sie die Verwendung der domainbasierten " -"Zuweisungen in Betracht ziehen. Erfahren Sie mehr unter :doc:`/manage/" -"organizations/index`." +"Dies zeigt die Agenten-Sicht bei Anwendung der oben genannten Workflows." -#: ../system/integrations/ldap/index.rst:39 +#: ../system/core-workflows/learn-by-example.rst:0 msgid "" -"Zammad's LDAP sync is one way. Editing user settings or permissions may be " -"overwritten upon the next sync depending on your configuration." +"Workflow shows objects and limits options based on selections on the group" msgstr "" -"Die LDAP-Synchronisierung von Zammad funktioniert nur in eine Richtung. Die " -"Bearbeitung von Benutzereinstellungen oder Berechtigungen kann bei der " -"nächsten Synchronisierung überschrieben werden, abhängig von Ihrer " -"Konfiguration." +"Workflow zeigt Objektattribute an und schränkt die Optionen basierend auf " +"der Auswahl in der Gruppe ein" -#: ../system/integrations/ldap/index.rst:41 -msgid "Nested groups are not supported." -msgstr "Verschachtelte Gruppen werden nicht unterstützt." +#: ../system/core-workflows/learn-by-example.rst:90 +msgid "Approval process" +msgstr "Genehmigungsprozess" -#: ../system/integrations/ldap/index.rst:42 -msgid "Synchronizing user avatars from LDAP is not supported." +#: ../system/core-workflows/learn-by-example.rst:71 +msgid "" +"In this case ``approved`` is visible to agents by default. For this " +"workflow, an additional role ``Approval person`` is required (no further " +"permissions)." msgstr "" -"Die Synchronisierung von Benutzeravataren aus LDAP wird nicht unterstützt." +"In diesem Fall ist ``approved`` standardmäßig für Agenten sichtbar. Für " +"diesen Workflow wird eine zusätzliche Rolle ``Approval person`` benötigt " +"(keine weiteren Berechtigungen)." -#: ../system/integrations/ldap/index.rst:43 -msgid "Unlike user filters, group filters cannot be changed." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that restricts an approval attribute to specific roles" msgstr "" -"Im Gegensatz zu den Benutzerfiltern können die Gruppenfilter nicht geändert " -"werden." +"Beispiel-Workflow, der den Genehmigungs-Status auf bestimmte Rollen " +"einschränkt" -#: ../system/integrations/ldap/index.rst:44 +#: ../system/core-workflows/learn-by-example.rst:81 msgid "" -"When a user originates from an LDAP server, Zammad will try to verify the " -"login credentials against LDAP first - if this fails Zammad will check its " -"local database." +"This workflow may work best in combination with a :doc:`trigger ` but technically, this is not required." msgstr "" -"Wenn ein Benutzer von einem LDAP-Server stammt, versucht Zammad zunächst, " -"die Anmeldedaten anhand von LDAP zu überprüfen - wenn dies fehlschlägt, " -"prüft Zammad seine lokale Datenbank." +"Dieser Workflow funktioniert am besten in Kombination mit einem :doc:" +"`Trigger `, aber technisch ist das nicht unbedingt " +"erforderlich." -#: ../system/integrations/ldap/index.rst:50 +#: ../system/core-workflows/learn-by-example.rst:84 msgid "" -"Users can have local passwords even if they're LDAP users! You can learn " -"more about user accounts in general on :doc:`/manage/users/index`." +"Select fields may be a better approach because they allow more values than " +"just a simple ``true`` or ``false``." msgstr "" -"Benutzer können lokale Passwörter haben, auch wenn sie LDAP-Benutzer sind! " -"Sie können mehr über Benutzerkonten im Allgemeinen unter :doc:`/manage/users/" -"index` erfahren." +"Auswahlfelder können besser geeignet sein, da sie mehr Werte zulassen als " +"nur ein einfaches ``true`` oder ``false``." -#: ../system/integrations/ldap/index.rst:54 +#: ../system/core-workflows/learn-by-example.rst:0 msgid "" -"When several LDAP sources contain the same user (meaning the same email " -"address), the user in question will be updated with every source configured. " -"*The last LDAP source will win.*" +"Workflow fixes possible values of \"Approved ?\" to a specific selection " +"depending on the users role" msgstr "" -"Wenn mehrere LDAP-Quellen denselben Benutzer (d.h. dieselbe E-Mail-Adresse) " -"enthalten, wird der betreffende Benutzer aus jeder konfigurierten Quelle " -"aktualisiert. *Die letzte LDAP-Quelle gewinnt schlussendlich.*" +"Der Workflow legt die möglichen Werte von \"Approved ?\" auf eine bestimmte " +"Auswahl fest, die von der Rolle des Benutzers abhängt" -#: ../system/integrations/ldap/index.rst:58 -msgid "" -"This is subject to change with `Issue 4109 `_ in the future." -msgstr "" -"Dies kann sich mit `Issue 4109 `_ in Zukunft ändern." +#: ../system/core-workflows/learn-by-example.rst:103 +msgid "State dependent mandatory fields" +msgstr "Vom Status abhängige Pflichtfelder" -#: ../system/integrations/ldap/index.rst:60 +#: ../system/core-workflows/learn-by-example.rst:93 msgid "" -"Synchronization statistics currently affect *all* configured LDAP sources. " -"This also applies for newly added or updated sources." +"This workflow sets ``Category`` to mandatory if the agent wants to set the " +"states ``closed`` or ``pending close`` to enforce categorization." msgstr "" -"Die Synchronisationsstatistiken betreffen derzeit *alle* konfigurierten LDAP-" -"Quellen. Dies gilt auch für neu hinzugefügte oder aktualisierte Quellen." +"Dieser Workflow legt ``Category`` als Pflichtfeld fest, wenn der Agent die " +"Tickets auf ``geschlossen`` oder ``Warten auf Schließen`` setzen will, um " +"die Kategorisierung zu erzwingen." -#: ../system/integrations/ldap/index.rst:63 -msgid "" -"This is subject to change with `Issue 4108 `_ in the future." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that sets fields to mandatory on specific states" msgstr "" -"Dies kann sich mit `Issue 4108 `_ in Zukunft ändern." +"Beispiel-Workflow, der Felder abhängig vom Ticketstatus als Pflichtfeld " +"definiert" -#: ../system/integrations/ldap/index.rst:65 +#: ../system/core-workflows/learn-by-example.rst:0 msgid "" -"Zammad currently has limited fallback server support. You can workaround " -"this by providing several sources - however, ensure to have the exact same " -"configuration on your fallback." +"Workflow sets category field to mandatory upon choosing closed or pending " +"close as state" msgstr "" -"Zammad bietet derzeit nur begrenzte Unterstützung für Fallback-Server. Sie " -"können dies umgehen, indem Sie mehrere Quellen zur Verfügung stellen - " -"stellen Sie jedoch sicher, dass Sie auf Ihrem Fallback-Server genau dieselbe " -"Konfiguration haben." +"Der Workflow definiert das Kategorie-Feld als Pflichtfeld, wenn als Status " +"\"geschlossen\" oder \"warten auf Schließen\" gewählt wird" -#: ../system/integrations/ldap/index.rst:69 -msgid "" -"This is subject to improve with `Issue 4107 `_ in the future." +#: ../system/core-workflows/learn-by-example.rst:106 +msgid "Manual Ticket Handover Process" +msgstr "Prozess manuelle Ticketübergabe" + +#: ../system/core-workflows/learn-by-example.rst:108 +msgid "This example covers the handover of a ticket from one agent to another:" msgstr "" -"Dies kann zukünftig mit `Issue 4107 `_ verbessert werden." +"In diesem Beispiel geht es um die Übergabe eines Tickets von einem Agenten " +"an einen anderen:" -#: ../system/integrations/ldap/index.rst:76 +#: ../system/core-workflows/learn-by-example.rst:110 msgid "" -"This section holds all requests Zammad handled for all LDAP sources. These " -"entries can either contain synchronization information or logins " -"(authentication attempts via Zammad's login interface)." +"When the ticket owner is modified, a new text field (\"Handover\") shows up " +"for a comment" msgstr "" -"Dieser Abschnitt enthält alle Anfragen an alle LDAP-Quellen. Diese Einträge " -"können entweder Synchronisationsinformationen oder Logins " -"(Authentifizierungsversuche über die Login-Schnittstelle von Zammad) " -"enthalten." +"Wenn der Besitzer des Tickets geändert wird, wird ein neues Textfeld " +"(\"Handover\") für einen Kommentar eingeblendet" -#: ../system/integrations/ldap/index.rst:80 +#: ../system/core-workflows/learn-by-example.rst:112 msgid "" -"By clicking on any request, Zammad will provide even more information. The " -"provided information can be useful when something does not work as expected." +"This may only be visible when the owner is changed, therefore it has to be " +"hidden in general" msgstr "" -"Wenn Sie auf eine Anfrage klicken, stellt Zammad weitere Informationen zur " -"Verfügung. Die bereitgestellten Informationen können nützlich sein, wenn " -"etwas nicht wie erwartet funktioniert." +"Dies darf nur sichtbar sein, wenn der Besitzer gewechselt wird, daher muss " +"es grundsätzlich ausgeblendet werden" -#: ../system/integrations/ldap/index.rst:85 +#: ../system/core-workflows/learn-by-example.rst:114 +msgid "The input in this handover text field is mandatory" +msgstr "Die Eingabe in dieses Handover-Textfeld ist verpflichtend" + +#: ../system/core-workflows/learn-by-example.rst:115 msgid "" -"Especially a LDAP synchronization can cause many log entries. The web " -"interface will always limit the number of shown entries to the last 50 " -"entries." +"After submitting changes, the value of the handover field must be added as " +"an note to the ticket (via trigger)" msgstr "" -"LDAP-Synchronisationen können viele Log-Einträge verursachen. Das " -"Webinterface beschränkt die Anzahl der angezeigten Einträge immer auf die " -"letzten 50 Einträge." +"Nach dem Speichern muss der Wert des Handover-Felds als Notiz zum Ticket " +"hinzugefügt werden (mittels Trigger)" -#: ../system/integrations/ldap/index.rst:None -msgid "" -"Screencast showing LDAP integration log entries and a detail view on\n" -"an entry." -msgstr "Screencast mit LDAP-Protokollen und Detailansicht eines Eintrags." +#: ../system/core-workflows/learn-by-example.rst:121 +msgid "Hiding handover field" +msgstr "Ausblenden des Handover-Feldes" -#: ../system/integrations/ldap/manage.rst:2 -msgid "Manage LDAP-Sources" -msgstr "Verwalten von LDAP-Quellen" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Hiding the handover field in core workflows" +msgstr "Ausblenden des Handover-Felds in Core Workflows" -#: ../system/integrations/ldap/manage.rst:6 -msgid "" -"Please keep in mind all current limitations for the LDAP synchronization. " -"This will help to understand scopes of the following operations better." +#: ../system/core-workflows/learn-by-example.rst:126 +msgid "Showing handover field and setting it to mandatory" +msgstr "Handover-Feld einblenden und als Pflichtfeld setzen" + +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Showing the handover field and set it as mandatory" +msgstr "Das Handover-Feld anzeigen und als Pflichtfeld festlegen" + +#: ../system/core-workflows/learn-by-example.rst:131 +msgid "Trigger writing handover input to a new article" msgstr "" -"Bitte beachten Sie alle aktuellen Einschränkungen für die LDAP-" -"Synchronisation. Dies wird Ihnen helfen, die folgenden Operationen besser zu " -"verstehen." +"Trigger für die Erstellung eines neuen Artikels auf Basis des Handover-" +"Inhalts" -#: ../system/integrations/ldap/manage.rst:65 -msgid "Add new source" -msgstr "Neue Quelle hinzufügen" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Write handover content to a new article" +msgstr "Handover-Inhalt in einen neuen Artikel schreiben" -#: ../system/integrations/ldap/manage.rst:10 +#: ../system/core-workflows/learn-by-example.rst:133 msgid "" -"Using the *New Source* button allows you to add new LDAP sources to your " -"installation. You're not limited in the number of sources, however, keep in " -"mind that many sources will also take more time to synchronize." +"As a result, the ticket includes an article of the type note which includes " +"the predefined text and the handover comment." msgstr "" -"Über die Schaltfläche *Neue Quelle* können Sie neue LDAP-Quellen zu Ihrer " -"Installation hinzufügen. Sie sind in der Anzahl der Quellen nicht " -"beschränkt, bedenken Sie jedoch, dass viele Quellen auch mehr Zeit für die " -"Synchronisierung benötigen." +"Als Ergebnis enthält das Ticket einen Artikel vom Typ Notiz, der den " +"vordefinierten Text und den Inhalt des Handover-Felds enthält." -#: ../system/integrations/ldap/manage.rst:14 +#: ../system/core-workflows/limitations.rst:6 +msgid "Core Workflows do not replace Triggers" +msgstr "Core Workflows ersetzen nicht Trigger" + +#: ../system/core-workflows/limitations.rst:5 msgid "" -"You can choose between different encryption types, namely *SSL* and " -"*STARTTLS* or none of them (\"*No SSL*\"). If you choose *SSL* or " -"*STARTTLS*, Zammad will display an additional *SSL verification* option that " -"allows you to disable the verification, e.g. for self-signed SSL " -"certificates. You can also tell Zammad to use a different port by appending " -"``:`` to your hostname/IP." +"Workflows manipulate the behavior of fields. However, they do not set values " +"in fields because of actions." msgstr "" -"Sie können zwischen verschiedenen Verschlüsselungsarten wählen, nämlich " -"*SSL* und *STARTTLS* oder keine von beiden (\"*kein SSL*\"). Wenn Sie sich " -"für *SSL* oder *STARTTLS* entscheiden, zeigt Zammad eine zusätzliche Option " -"*SSL-Verifizierung* an, mit der Sie die Überprüfung deaktivieren können, z." -"B. für selbst signierte SSL-Zertifikate. Sie können Zammad auch anweisen, " -"einen anderen Port zu verwenden, indem Sie ``:`` an Ihren " -"Hostnamen/IP anhängen." +"Workflows verändern Felder und deren Verhalten. Sie setzen jedoch keine " +"Werte in Felder aufgrund von Aktionen." -#: ../system/integrations/ldap/manage.rst:0 +#: ../system/core-workflows/limitations.rst:16 +msgid "API calls are only partly affected" +msgstr "API-Calls sind nur teilweise betroffen" + +#: ../system/core-workflows/limitations.rst:9 msgid "" -"Screenshot of configuring a new LDAP source with SSL encryption and SSL " -"verification" +"Some options affect UI only and thus do not restrict responses and calls." msgstr "" -"Screenshot der Konfiguration einer neuen LDAP-Quelle mit SSL-Verschlüsselung " -"und SSL-Verifizierung" +"Einige Optionen wirken sich nur auf die Benutzeroberfläche aus und schränken " +"daher API requests und responses nicht ein." -#: ../system/integrations/ldap/manage.rst:26 +#: ../system/core-workflows/limitations.rst:11 +msgid "This affects the following actions:" +msgstr "Das betrifft die folgenden Aktionen:" + +#: ../system/core-workflows/limitations.rst:13 +msgid "select" +msgstr "auswählen" + +#: ../system/core-workflows/limitations.rst:14 +msgid "auto select" +msgstr "automatisch auswählen" + +#: ../system/core-workflows/limitations.rst:15 +msgid "show" +msgstr "anzeigen" + +#: ../system/core-workflows/limitations.rst:16 +msgid "hide" +msgstr "verstecken" + +#: ../system/core-workflows/limitations.rst:25 +msgid "Some fields stay unavailable to customers" +msgstr "Einige Felder bleiben für Kunden unzugänglich" + +#: ../system/core-workflows/limitations.rst:19 msgid "" -"New Source with SSL transport security enabled and certificate verification" +"For technical and security reasons, some default fields (the pale ones you " +"can't edit) stay unavailable for display and usage on customer permissions." msgstr "" -"Neue Quelle mit aktivierter SSL-Verschlüsselung und Zertifikatsüberprüfung" +"Aus technischen und sicherheitstechnischen Gründen sind einige " +"Standardfelder (die grauen Felder, die Sie nicht bearbeiten können) für " +"Benutzer mit Kunden-Berechtigung nicht verfügbar." -#: ../system/integrations/ldap/manage.rst:30 +#: ../system/core-workflows/limitations.rst:23 msgid "" -"Using an user filter can be a good idea if you only require a small subset " -"of your LDAP users in Zammad." +"If you require your customers to change e.g. priorities, please consider " +"using workarounds via :doc:`/system/objects` and :doc:`/manage/trigger`." msgstr "" -"Die Verwendung eines Benutzerfilters kann eine gute Idee sein, wenn Sie nur " -"eine kleine Teilmenge Ihrer LDAP-Benutzer in Zammad benötigen." +"Wenn Sie möchten dass Ihre Kunden z.B. Prioritäten ändern können, ziehen Sie " +"bitte Workarounds über :doc:`/system/objects` und :doc:`/manage/trigger` in " +"Betracht." -#: ../system/integrations/ldap/manage.rst:42 -msgid "This especially affects inactive users" -msgstr "Das betrifft vor allem inaktive Nutzer" +#: ../system/core-workflows/limitations.rst:29 +msgid "Ticket title changes not supported in edit mask" +msgstr "" +"Änderungen des Ticket-Titels werden in der Bearbeitungsmaske nicht " +"unterstützt" -#: ../system/integrations/ldap/manage.rst:34 +#: ../system/core-workflows/limitations.rst:28 msgid "" -"As every LDAP behaves differently on which attributes and how they are set, " -"Zammad doesn't care about any flags." +"It is currently not possible to perform changes of the ticket title in the " +"edit mask (e.g. renaming, set to read-only)." msgstr "" -"Da sich jedes LDAP anders verhält, welche Attribute wie gesetzt werden, " -"kümmert sich Zammad nicht um irgendwelche Flags." +"Es ist derzeit nicht möglich, in der Bearbeitungsmaske Änderungen am Titel " +"des Tickets vorzunehmen (z.B. umbenennen, auf schreibgeschützt setzen)." -#: ../system/integrations/ldap/manage.rst:37 -msgid "" -"Users that no longer are returned by your LDAP source will automatically be " -"set to inactive. Zammad assumes that the user was deactivated." -msgstr "" -"Benutzer, die nicht mehr von Ihrer LDAP-Quelle zurückgegeben werden, werden " -"automatisch auf inaktiv gesetzt. Zammad geht davon aus, dass der Benutzer " -"deaktiviert wurde." +#: ../system/core-workflows/limitations.rst:37 +msgid "What is out of scope of Core Workflows?" +msgstr "Was fällt nicht in den Anwendungsbereich der Core-Workflows?" -#: ../system/integrations/ldap/manage.rst:41 +#: ../system/core-workflows/limitations.rst:32 msgid "" -"Users will never be removed automatically! If you want to remove obsolete " -"users, use :doc:`/system/data-privacy`." +"There are some things that would count as workflow but are either done via :" +"doc:`/manage/trigger` or :doc:`/manage/scheduler`." msgstr "" -"Benutzer werden niemals automatisch entfernt! Wenn Sie veraltete Benutzer " -"entfernen wollen, verwenden Sie :doc:`/system/data-privacy`." - -#: ../system/integrations/ldap/manage.rst:46 -msgid "Active Directory admins" -msgstr "Active Directory-Administratoren" +"Es gibt einige Dinge, die als Workflow gelten würden, aber entweder über :" +"doc:`/manage/trigger` oder :doc:`/manage/scheduler` erledigt werden." -#: ../system/integrations/ldap/manage.rst:45 -msgid "" -"Active Directories are quite specific on how to filter for active users only " -"- please see the `Microsoft documentation `_ for more " -"information." -msgstr "" -"Active Directories sind sehr spezifisch, was die Filterung nach aktiven " -"Benutzern angeht - weitere Informationen finden Sie in der `Microsoft " -"Documentation `_." +#: ../system/core-workflows/limitations.rst:35 +msgid "Such as (but not limited to):" +msgstr "Zum Beispiel (nicht abschließend):" -#: ../system/integrations/ldap/manage.rst:51 -msgid "" -"*Do not* manually write pathes of either LDAP attributes or groups. If " -"Zammad does not display them, it either cannot find them or you have a lot " -"of users that don't have the attributes populated." -msgstr "" -"Editieren Sie *keine* Pfade von LDAP-Attributen oder Gruppen manuell. Wenn " -"Zammad sie nicht anzeigt, kann es sie entweder nicht finden oder Sie haben " -"viele Benutzer, bei denen die Attribute nicht ausgefüllt sind." +#: ../system/core-workflows/limitations.rst:37 +msgid "up- or downgrade permissions of users" +msgstr "Berechtigungen von Benutzern herauf- oder herabstufen" -#: ../system/integrations/ldap/manage.rst:55 -msgid "" -"Zammad will always only return attributes that are filled - this reduces the " -"returned list of attributes greatly." +#: ../system/core-workflows/limitations.rst:38 +msgid "affecting article creation or listing" msgstr "" -"Zammad wird immer nur Attribute zurückgeben, die ausgefüllt sind - dies " -"reduziert die Liste der zurückgegebenen Attribute erheblich." +"Änderungen mit Auswirkung auf die Erstellung oder Auflistung von Artikeln" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing how to add a new LDAP source" -msgstr "Screencast zeigt, wie eine neue LDAP-Quelle hinzugefügt wird" +#: ../system/data-privacy.rst:2 +msgid "Data Privacy" +msgstr "Datenschutz" -#: ../system/integrations/ldap/manage.rst:63 +#: ../system/data-privacy.rst:4 msgid "" -"If your LDAP system doesn't allow anonymous bind, Zammad detects it and " -"provides you an editable \"Base DN\" *text* field instead of a prefilled " -"*select* field." +"For compliance with GDPR and other data privacy laws, you may wish to " +"**permanently delete users from the system**, along with **all of their " +"associated tickets**." msgstr "" -"Wenn Ihr LDAP-System keine anonyme Verbindung zulässt, erkennt Zammad dies " -"und stellt Ihnen ein editierbares *Text*-Feld \"Basis-DN\" anstelle eines " -"vorausgefüllten *Auswahl*-Feldes zur Verfügung." - -#: ../system/integrations/ldap/manage.rst:81 -msgid "Review or edit existing source" -msgstr "Vorhandene Quelle überprüfen oder bearbeiten" +"Um die DSGVO und andere Datenschutzgesetze einzuhalten ist es ggf. " +"erforderlich, **Benutzer inkl. aller zugehöriger Tickets dauerhaft aus dem " +"System löschen**." -#: ../system/integrations/ldap/manage.rst:68 +#: ../system/data-privacy.rst:8 msgid "" -"Clicking on a LDAP source will provide a configuration and mapping overview." +"You can create manual deletion tasks or even automated deletion tasks for " +"tickets and users based on custom conditions via :doc:`scheduler `!" msgstr "" -"Wenn Sie auf eine LDAP-Quelle klicken, erhalten Sie eine Übersicht über die " -"Konfiguration und das Mapping." +"Sie können manuelle Löschaufgaben oder sogar automatisierte Löschaufgaben " +"für Tickets und Benutzer, basierend auf benutzerdefinierten Bedingungen, " +"über :doc:`scheduler ` erstellen!" -#: ../system/integrations/ldap/manage.rst:70 +#: ../system/data-privacy.rst:12 msgid "" -"If needed you can then use the *Change* button to update either the name, " -"active state or the whole configuration. If you're changing the whole " -"configuration, the dialogue will be identical to the source creation." +"Access to this panel requires ``admin.data_privacy`` permissions (introduced " +"in Zammad 3.5)." msgstr "" -"Bei Bedarf können Sie dann die Schaltfläche *Ändern* verwenden, um entweder " -"den Namen, den Status (aktiv oder nicht) oder die gesamte Konfiguration zu " -"aktualisieren. Wenn Sie die gesamte Konfiguration ändern, ist der Dialog " -"identisch mit dem bei der Erstellung der Quelle." +"Der Zugriff auf diesen Bereich erfordert die Berechtigung ``admin." +"data_privacy`` (eingeführt in Zammad 3.5)." -#: ../system/integrations/ldap/manage.rst:76 +#: ../system/data-privacy.rst:15 msgid "" -"Did your LDAP server change? Different LDAP servers have different " -"structures and default attributes. This causes the LDAP synchronization to " -"likely fail. Consider removing the affected source and re-add it." +"On older systems that have not been updated yet, customers can also be :docs:" +"`deleted via the Zammad console `." msgstr "" -"Hat sich Ihr LDAP-Server geändert? Verschiedene LDAP-Server haben " -"unterschiedliche Strukturen und Standardattribute. Dies führt dazu, dass die " -"LDAP-Synchronisierung wahrscheinlich fehlschlägt. Entfernen Sie die " -"betroffene Quelle und fügen Sie sie erneut hinzu." - -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing the update of the source name." -msgstr "Screencast, der die Aktualisierung des Quellennamens zeigt." +"Auf älteren Systemen, die noch nicht aktualisiert wurden, können Kunden auch " +"über die :docs:`Zammad-Konsole gelöscht werden `." -#: ../system/integrations/ldap/manage.rst:89 -msgid "Re-arrange LDAP source's order" -msgstr "Neuordnung der Reihenfolge der LDAP-Quellen" +#: ../system/data-privacy.rst:22 +msgid "User deletion dialog in the Data Privacy panel" +msgstr "Benutzer-Löschdialog im Datenschutz-Panel" -#: ../system/integrations/ldap/manage.rst:84 +#: ../system/data-privacy.rst:22 msgid "" -"You can change the synchronization order for each source at any time. Zammad " -"will synchronize the sources from top to bottom." +"The user deletion dialog lists some of the tickets that will be removed from " +"the system along with the user." msgstr "" -"Sie können die Reihenfolge der Synchronisierung für jede Quelle jederzeit " -"ändern. Zammad synchronisiert die Quellen von oben nach unten." +"Im Dialogfeld zum Löschen von Benutzern werden einige der Tickets " +"aufgelistet, die zusammen mit dem Benutzer aus dem System entfernt werden." -#: ../system/integrations/ldap/manage.rst:0 -msgid "" -"Screencasting showing how to change the source order by using\n" -"drag and drop." -msgstr "Screencasting zeigt, wie man die Reihenfolge der Quellen ändert." +#: ../system/data-privacy.rst:27 +msgid "Deleting Users via GUI" +msgstr "Löschen von Benutzern per GUI" -#: ../system/integrations/ldap/manage.rst:101 -msgid "Remove a source" -msgstr "Eine Quelle entfernen" +#: ../system/data-privacy.rst:29 +msgid "🔥 **All deletions are FINAL!**" +msgstr "🔥 **Jede Löschung ist ENDGÜLTIG!**" -#: ../system/integrations/ldap/manage.rst:92 -msgid "" -"If you no longer need the a LDAP source or simply want to start over, you " -"can remove them at any time. This will not remove synchronized users, data " -"synchronized or permissions." +#: ../system/data-privacy.rst:31 +msgid "Once you click “Delete”, the action cannot be canceled or undone." msgstr "" -"Wenn Sie eine LDAP-Quelle nicht mehr benötigen oder einfach neu beginnen " -"möchten, können Sie sie jederzeit entfernen. Dabei werden weder " -"synchronisierte Benutzer noch synchronisierte Daten oder Berechtigungen " -"entfernt." +"Sobald Sie auf \"Löschen\" klicken, kann die Aktion nicht mehr abgebrochen " +"oder rückgängig gemacht werden." -#: ../system/integrations/ldap/manage.rst:98 +#: ../system/data-privacy.rst:33 msgid "" -"Not sure if you'd need the source later on? Set the source to inactive " -"instead of removing it - see *Review or edit existing source* for more." +"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." msgstr "" -"Sie sind sich nicht sicher, ob Sie die Quelle später noch benötigen? Setzen " -"Sie die Quelle auf inaktiv, anstatt sie zu entfernen - mehr dazu unter " -"*Vorhandene Quelle überprüfen oder bearbeiten*." +"Jedes Mal, wenn Sie einen Benutzer löschen, werden auch alle seine Tickets " +"gelöscht. Es ist nicht möglich, einen Benutzer zu löschen und seine Tickets " +"zu behalten." -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing how to remove LDAP sources." -msgstr "Screencast zeigt, wie LDAP-Quellen entfernt werden können." +#: ../system/data-privacy.rst:36 +msgid "**The following records cannot be deleted:**" +msgstr "**Die folgenden Datensätze können nicht gelöscht werden:**" -#: ../system/integrations/pgp/index.rst:2 -msgid "PGP" -msgstr "PGP" +#: ../system/data-privacy.rst:38 +msgid "your own account" +msgstr "Ihr eigenes Konto" -#: ../system/integrations/pgp/index.rst:7 -msgid "" -"Pretty Good Privacy (PGP) is another method for secure email communication. " -"With PGP, you can exchange **signed** and **encrypted** messages with others." -msgstr "" -"Pretty Good Privacy (PGP) ist eine weitere Methode zur sicheren E-Mail-" -"Kommunikation. Mit PGP können Sie **signierte** und **verschlüsselte** " -"Nachrichten mit anderen austauschen." +#: ../system/data-privacy.rst:39 +msgid "the system's last remaining administrator account" +msgstr "das letzte verbleibende Administratorkonto des Systems" -#: ../system/integrations/pgp/index.rst:13 -#: ../system/integrations/smime/index.rst:17 -msgid "Signing" -msgstr "Signieren" +#: ../system/data-privacy.rst:42 +msgid "Step 1: Find a User / Confirm Deletion" +msgstr "Schritt 1: Benutzer suchen / Löschung bestätigen" -#: ../system/integrations/pgp/index.rst:11 -msgid "is a proof that a message hasn't been manipulated on its way." +#: ../system/data-privacy.rst:44 +msgid "There are three ways to access the user deletion dialog:" msgstr "" -"ist der Beweis, dass eine Nachricht auf dem Weg nicht manipuliert wurde." +"Es gibt drei Möglichkeiten, den Dialog zum Löschen von Benutzern aufzurufen:" -#: ../system/integrations/pgp/index.rst:13 -msgid "" -"In other words, it guarantees message **integrity** and **authenticity**." -msgstr "" -"Mit anderen Worten, es garantiert die **Integrität** und **Authentizität**." +#: ../system/data-privacy.rst:51 +msgid "**from the user's profile**" +msgstr "**aus dem Profil des Nutzers**" -#: ../system/integrations/pgp/index.rst:19 -#: ../system/integrations/smime/index.rst:22 -msgid "Encryption" -msgstr "Verschlüsselung" +#: ../system/data-privacy.rst:0 +msgid "Accessing the user deletion dialog in a user profile" +msgstr "Dialog zum Löschen von Benutzern in einem Benutzerprofil" -#: ../system/integrations/pgp/index.rst:16 -#: ../system/integrations/smime/index.rst:20 -msgid "" -"scrambles a message so that it can only be unscrambled by the intended " -"recipient." -msgstr "" -"verschlüsselt eine Nachricht so, dass sie nur vom gewünschten Empfänger " -"entschlüsselt werden kann." +#: ../system/data-privacy.rst:51 +msgid "Click **Action > Delete**." +msgstr "Klicken Sie auf **Aktion > Löschen**." -#: ../system/integrations/pgp/index.rst:19 -msgid "" -"In other words, it guarantees message **privacy** and **data security**." -msgstr "" -"Mit anderen Worten, es garantiert die **Privatsphäre** und " -"**Datensicherheit** einer Nachricht." +#: ../system/data-privacy.rst:58 +msgid "**in the “Manage > Users” Admin Panel**" +msgstr "**in den Einstellungen unter \"Verwalten > Benutzer\"**" -#: ../system/integrations/pgp/index.rst:25 -msgid "Screenshot of ticket creation with encrypt and sign buttons" -msgstr "" -"Screenshot der Ticketerstellung mit Schaltflächen zum Verschlüsseln und " -"Signieren" +#: ../system/data-privacy.rst:0 +msgid "Accessing the user deletion dialog under “Users” in the Admin Panel" +msgstr "Dialog zum Löschen von Benutzern im Admin Panel" -#: ../system/integrations/pgp/index.rst:25 -msgid "" -"Once PGP has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " -"appear in the ticket composer." -msgstr "" -"Sobald PGP aktiviert ist, erscheinen die Schaltflächen 🔒 **Verschlüsseln** " -"und ✅ **Signieren** in der Ticket Ansicht." +#: ../system/data-privacy.rst:58 +msgid "Use the **⋮ Actions** menu for the target user." +msgstr "Verwenden Sie das Menü **⋮ Aktionen** für den entsprechenden Benutzer." -#: ../system/integrations/pgp/index.rst:28 -msgid "**Sign button not visible?**" -msgstr "**Schaltfläche zum Signieren nicht sichtbar?**" +#: ../system/data-privacy.rst:66 ../system/data-privacy.rst:104 +msgid "**in the “System > Data Privacy” Admin Panel**" +msgstr "**in den Einstellungen unter \"System > Datenschutz\"**" -#: ../system/integrations/pgp/index.rst:30 +#: ../system/data-privacy.rst:0 msgid "" -"Please note that the signing of emails is based on the outgoing email " -"account. That means you have to choose a group with a sender email account, " -"which has a private key assigned." +"Accessing the user deletion dialog under “Data Privacy” in the Admin Panel" +msgstr "Dialog zum Löschen von Benutzern unter \"Datenschutz\" im Admin Panel" + +#: ../system/data-privacy.rst:65 +msgid "" +"Use the **New Deletion Task** button. Search for users by name or email " +"address." msgstr "" -"Bitte beachten Sie, dass das Signieren von E-Mails auf dem ausgehenden E-" -"Mail-Konto basiert. Das heißt, Sie müssen eine Gruppe mit einem Absender-E-" -"Mail-Konto auswählen, dem ein privater Schlüssel zugewiesen ist." +"Verwenden Sie die Schaltfläche **Neue Löschaufgabe**. Suchen Sie nach " +"Benutzern anhand von Namen oder E-Mail-Adressen." -#: ../system/integrations/pgp/index.rst:35 -msgid "Handling of Keys" -msgstr "Verwaltung von Schlüsseln" +#: ../system/data-privacy.rst:79 +msgid "**Delete organizations**" +msgstr "**Organisationen löschen**" -#: ../system/integrations/pgp/index.rst:36 +#: ../system/data-privacy.rst:69 msgid "" -"To use the PGP function, you have to enable the integration (PGP) by " -"switching the toggle to *enabled*." +"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:" msgstr "" -"Um die PGP-Funktion zu nutzen, müssen Sie die Integration (PGP) aktivieren, " -"indem Sie den Schalter auf *aktiviert* stellen." +"Wenn der zu löschende Kunde der letzte Benutzer in seiner Organisation ist, " +"wird im Dialogfeld zum Löschen von Benutzern die Option **Organisation " +"löschen?** angezeigt:" -#: ../system/integrations/pgp/index.rst:39 +#: ../system/data-privacy.rst:0 +msgid "Deleting an organization via the user deletion dialog" +msgstr "Löschung einer Organisation über den Benutzer löschen Dialog" + +#: ../system/data-privacy.rst:78 msgid "" -"You can add keys by clicking the *add key* button. The keys can be imported " -"from a file or you can paste the content of the key in the text box." +"If this option does not appear, make sure there are no pending deletion " +"tasks for other customers from this organization." msgstr "" -"Sie können Schlüssel hinzufügen, indem Sie auf die Schaltfläche *Schlüssel " -"hinzufügen* klicken. Die Schlüssel können aus einer Datei importiert werden " -"oder Sie können den Inhalt des Schlüssels in das Textfeld einfügen." +"Wenn diese Option nicht angezeigt wird, stellen Sie sicher, dass es keine " +"ausstehenden Löschaufgaben für andere Kunden aus dieser Organisation gibt." -#: ../system/integrations/pgp/index.rst:42 -msgid "**Which keys do I have to import?**" -msgstr "**Welche Schlüssel muss ich importieren?**" +#: ../system/data-privacy.rst:82 +msgid "Step 2: Monitor Deletion Job Status" +msgstr "Schritt 2: Status des Löschauftrags prüfen" -#: ../system/integrations/pgp/index.rst:44 +#: ../system/data-privacy.rst:84 msgid "" -"For **signing** *outgoing* emails, you have to import the private key of " -"your Zammad email account." +"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:" msgstr "" -"Zum **Signieren** von *ausgehenden* E-Mails müssen Sie den privaten " -"Schlüssel Ihres Zammad-E-Mail-Kontos importieren." +"Es kann bis zu zehn Minuten dauern, bis das System Ihre Anfrage bearbeitet. " +"Für jeden Benutzer, den Sie löschen, wird eine \"Löschaufgabe\" in die " +"Warteschlange aufgenommen. Sie können den Status dieser Aufgaben an zwei " +"Stellen im Auge behalten:" -#: ../system/integrations/pgp/index.rst:47 +#: ../system/data-privacy.rst:98 +msgid "**in the Activity Stream**" +msgstr "**im Aktivitäts-Verlauf**" + +#: ../system/data-privacy.rst:0 +msgid "Activity Stream showing data privacy tasks" +msgstr "Aktivitäts-Verlauf mit Datenschutzaufgaben" + +#: ../system/data-privacy.rst:94 msgid "" -"For **encrypting** *outgoing* emails, you have to import the public key of " -"the customer's email account." +"For each deleted user, the Activity Stream will be updated twice—once when " +"the task is created, and once when it's complete." msgstr "" -"Für die **Verschlüsselung** von *ausgehenden* E-Mails müssen Sie den " -"öffentlichen Schlüssel des E-Mail-Kontos des Kunden importieren." +"Für jeden gelöschten Benutzer wird der Aktivitäts-Verlauf zweimal " +"aktualisiert - einmal bei der Erstellung der Aufgabe und einmal bei ihrer " +"Erledigung." -#: ../system/integrations/pgp/index.rst:50 +#: ../system/data-privacy.rst:97 msgid "" -"For **verifying the signature** of signed *incoming* emails, you have to " -"import the public key of the customer." +"These notifications are only visible to users with ``admin.data_privacy`` " +"permissions." msgstr "" -"Zur **Prüfung der Signatur** von signierten *eingehenden E-Mails* müssen Sie " -"den öffentlichen Schlüssel des Kunden importieren." +"Diese Benachrichtigungen sind nur für Benutzer mit der Berechtigung ``admin." +"data_privacy`` sichtbar." -#: ../system/integrations/pgp/index.rst:53 +#: ../system/data-privacy.rst:0 msgid "" -"For **decrypting** of encrypted *incoming* emails, you have to import the " -"private key of your Zammad email account." +"The task list within Data Privacy shows removals being in progress and " +"completed." msgstr "" -"Zum **Entschlüsseln** von verschlüsselten *eingehenden E-Mails* müssen Sie " -"den privaten Schlüssel Ihres Zammad-E-Mail-Kontos importieren." +"Die Aufgabenliste im Bereich Datenschutz zeigt die laufenden und " +"abgeschlossenen Löschungen." -#: ../system/integrations/pgp/index.rst:57 -msgid "Import Keys From a File" -msgstr "Importieren von Schlüsseln aus einer Datei" +#: ../system/data-privacy.rst:107 +msgid "Frequently Asked Questions" +msgstr "Regelmäßige gestellte Fragen" -#: ../system/integrations/pgp/index.rst:58 -msgid "You can import keys from a file in the section **Upload key**:" +#: ../system/data-privacy.rst:121 +msgid "What happens if I receive an email from a deleted customer?" msgstr "" -"Sie können Schlüssel aus einer Datei im Abschnitt **Schlüssel hochladen** " -"importieren:" - -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of adding a key via file" -msgstr "Screenshot zeigt das Hinzufügen eines Schlüssels aus eine Datei" +"Was passiert, wenn ich eine E-Mail von einem gelöschten Kunden erhalte?" -#: ../system/integrations/pgp/index.rst:64 +#: ../system/data-privacy.rst:110 msgid "" -"**Supported file formats:** ASCII-armor as well as binary GPG format " -"(basically any GPG supported key format) is supported here." +"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 "" -"**Unterstützte Dateiformate:** Unterstützt werden sowohl das ASCII-Armor- " -"als auch das binäre GPG-Format (grundsätzlich jedes von GPG unterstützte " -"Schlüsselformat)." +"Zammad erstellt automatisch einen neuen Benutzer-Account wann immer es eine " +"Nachricht von unbekannten E-Mail-Adressen erhält - das betrifft auch " +"gelöschte Benutzer. Gelöschte Nutzer werden niemals vom Erstellen neuer " +"Tickets abgehalten." -#: ../system/integrations/pgp/index.rst:68 -msgid "Import Keys by Pasting the Content" -msgstr "Importieren von Schlüsseln durch Einfügen des Inhalts" +#: ../system/data-privacy.rst:115 +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**." +msgstr "" +"Sollte der unwahrscheinliche Fall eintreten, dass Sie eine E-Mail erhalten, " +"nachdem Sie auf \"Löschen\" geklickt haben und das System Ihren Auftrag " +"bearbeitet hat, wird **das Ticket automatisch entfernt**. Die Ticketnummer " +"für das gelöschte Ticket wird in den Einstellungen unter **System > " +"Datenschutz > Erledigte Vorgänge > Benutzer löschen > Gelöschte Tickets** " +"angezeigt." -#: ../system/integrations/pgp/index.rst:69 -msgid "You can also paste the key's content in the section **paste key**:" +#: ../system/data-privacy.rst:130 +msgid "What about user information stored in internal notes or other messages?" msgstr "" -"Sie können den Inhalt des Schlüssels auch in den Abschnitt **Schlüssel " -"einfügen** kopieren:" +"Was ist mit Benutzerinformationen, die in internen Notizen oder anderen " +"Nachrichten gespeichert sind?" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of adding a key via pasting" -msgstr "Screenshot zeigt das Hinzufügen eines Schlüssels durch Einfügen" +#: ../system/data-privacy.rst:124 +msgid "" +"The deletion process removes **user accounts and associated tickets only**." +msgstr "" +"Beim Löschvorgang werden nur **Benutzerkonten und zugehörige Tickets** " +"entfernt." -#: ../system/integrations/pgp/index.rst:75 +#: ../system/data-privacy.rst:126 msgid "" -"**Supported format:** Please note that only ASCII-armor is supported here." +"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." msgstr "" -"**Unterstütztes Format:** Bitte beachten Sie, dass hier nur das ASCII-armor " -"Format unterstützt wird." +"Wenn es Verweise auf den Namen eines Benutzers oder Informationen gibt, die " +"an anderer Stelle im System gespeichert sind, werden diese Informationen " +"**nicht entfernt**. Grund dafür ist, dass es keine sinnvolle Möglichkeit " +"gibt, diese Informationen zuverlässig zu ermitteln." -#: ../system/integrations/pgp/index.rst:78 -msgid "Deleting Keys" -msgstr "Schlüssel Löschen" +#: ../system/data-privacy.rst:137 +msgid "I deleted an user and can still see a message they sent!" +msgstr "" +"Ich habe einen Benutzer gelöscht und kann immer noch eine von ihm gesendete " +"Nachricht sehen!" -#: ../system/integrations/pgp/index.rst:79 +#: ../system/data-privacy.rst:133 msgid "" -"If you want to delete a specific key, you can do it by clicking on the menu " -"in the *actions* column and select **delete**:" +"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." msgstr "" -"Wenn Sie einen bestimmten Schlüssel löschen möchten, können Sie dies tun, " -"indem Sie auf das Menü in der Spalte *Aktionen* klicken und **Löschen** " -"wählen:" - -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of deleting a key" -msgstr "Screenshot zeigt Löschen eines Schlüssels" +"Tickets können nur zu einem einzigen Kunden gehören, können aber Nachrichten " +"(\"Artikel\") von mehreren Personen enthalten. Wenn Sie einen Benutzer " +"gelöscht haben, aber immer noch Artikel sehen, die er gesendet hat, machen " +"Sie sich keine Sorgen - diese Artikel gehören zu einem Ticket, das jemand " +"anderem gehört, und enthalten keinen Hinweis mehr auf die Identität des " +"Absenders." -#: ../system/integrations/pgp/index.rst:88 -msgid "Downloading Keys" -msgstr "Herunterladen von Schlüsseln" +#: ../system/data-privacy.rst:141 +msgid "I removed a customer, now my reporting is off!" +msgstr "Ich habe einen Kunden entfernt, jetzt passt das Reporting nicht mehr!" -#: ../system/integrations/pgp/index.rst:89 +#: ../system/data-privacy.rst:140 msgid "" -"If you want to download your keys, you can do this as well via corresponding " -"action buttons. Depending on the key, you can choose wether you want to " -"download the private or the public key." +"When removing users and their tickets, all references are removed. This also " +"affects e.g. Reporting - these information are lost." msgstr "" -"Wenn Sie Ihre Schlüssel herunterladen möchten, können Sie dies ebenfalls " -"über die entsprechenden Aktionsschaltflächen tun. Je nach Schlüssel können " -"Sie wählen, ob Sie den privaten oder den öffentlichen Schlüssel " -"herunterladen möchten." +"Beim Entfernen von Benutzern und deren Tickets werden alle Referenzen " +"entfernt. Dies betrifft z.B. auch das Reporting - diese Informationen sind " +"weg." -#: ../system/integrations/pgp/index.rst:95 -#: ../system/integrations/smime/manage-certificates.rst:76 -msgid "Default Behavior" -msgstr "Standard-Verhalten" +#: ../system/data-privacy.rst:145 +msgid "How long does Zammad store created tasks?" +msgstr "Wie lange speichert Zammad erstellte Aufgaben?" -#: ../system/integrations/pgp/index.rst:96 +#: ../system/data-privacy.rst:144 msgid "" -"Here you can adjust on per group basis, if *sign* and *encryption* is on or " -"off by default. Please be aware, that agents can always override the setting " -"for each individual article." +"Please see the on-premise data section of the :docs:`data privacy ` chapter." msgstr "" -"Hier können Sie für jede Gruppe einstellen, ob *Signieren* und " -"*Verschlüsselung* standardmäßig ein- oder ausgeschaltet sind. Bitte beachten " -"Sie, dass Agenten die Einstellung für jeden einzelnen Artikel jederzeit " -"überschreiben können." +"Bitte beachten Sie den Abschnitt über lokale Daten im Kapitel :docs:" +"`Datenschutz `." -#: ../system/integrations/pgp/index.rst:None -msgid "Adjusting default behavior on per group basis" -msgstr "Anpassung des Standardverhaltens für jede Gruppe" +#: ../system/data-privacy.rst:150 +msgid "What about re-assigned tickets? I want to delete them, too." +msgstr "Was ist mit neu zugewiesenen Tickets? Ich möchte sie auch löschen." -#: ../system/integrations/pgp/index.rst:107 +#: ../system/data-privacy.rst:148 msgid "" -"Here you can see the last actions regarding signing and encryption and if " -"they were successful." +"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." msgstr "" -"Hier sehen Sie die letzten Aktionen bezüglich Signierung und Verschlüsselung " -"und ob sie erfolgreich waren." +"Es werden nur Tickets gelöscht, die dem entsprechenden Kunden zum Zeitpunkt " +"der Ausführung der Datenschutz-Löschaufgabe zugewiesen sind. Historische " +"Zuweisungen werden bei der Löschung nicht berücksichtigt." -#: ../system/integrations/pgp/index.rst:117 -msgid "**Sign button is not visible, but keys are imported.**" +#: ../system/data-privacy.rst:154 +msgid "Why are there so many deletion task entries, I didn't create them!" msgstr "" -"**Die Schaltfläche \"Signieren\" ist nicht sichtbar, aber die Schlüssel " -"wurden importiert.**" - -#: ../system/integrations/pgp/index.rst:115 -msgid "Did you choose a group in the ticket?" -msgstr "Haben Sie eine Gruppe in dem Ticket ausgewählt?" +"Warum gibt es so viele Löschaufgabeneinträge, ich habe sie nicht erstellt!" -#: ../system/integrations/pgp/index.rst:116 +#: ../system/data-privacy.rst:153 msgid "" -"Did you import a private key for the email adress, which is used for " -"outgoing emails in the group?" +"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." msgstr "" -"Haben Sie einen privaten Schlüssel für die E-Mail-Adresse importiert, die " -"für ausgehende E-Mails in der Gruppe verwendet wird?" +"Die Löschaufgaben können von der :doc:`/manage/scheduler` kommen. Und zwar " +"ist die Aktion *\"Datenschutz-Löschaufgabe hinzufügen\"* für die Einträge " +"verantwortlich." -#: ../system/integrations/pgp/index.rst:122 -msgid "**How to obtain keys?**" -msgstr "**Wie erhält man Schlüssel?**" +#: ../system/integrations/checkmk/admin-panel-reference.rst:2 +msgid "Admin Panel Reference" +msgstr "Admin-Bereich" -#: ../system/integrations/pgp/index.rst:120 +#: ../system/integrations/checkmk/admin-panel-reference.rst:None +msgid "Screenshot of Checkmk settings overview" +msgstr "Screenshot der Checkmk-Einstellungen in Zammad" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:12 msgid "" -"You can create them yourself! There are some good tutorials on the web on " -"how to create them. Providing keys to Zammad is a prerequisite to use the " -"PGP feature." +"Which :doc:`group ` should Checkmk tickets be assigned " +"to as a default (*i.e.,* when none is specified)?" msgstr "" -"Sie können sie selbst erstellen! Es gibt einige gute Anleitungen im " -"Internet, wie man sie erstellt. Die Bereitstellung von Schlüsseln an Zammad " -"ist eine Voraussetzung für die Nutzung der PGP-Funktion." +"Welcher :doc:`Gruppe ` sollen Checkmk-Tickets " +"standardmäßig zugewiesen werden (wenn keine angegeben ist)?" -#: ../system/integrations/pgp/index.rst:127 -msgid "**It says a passphrase is needed, but I haven't got one.**" -msgstr "" -"**Mir wird angezeigt dass eine Passphrase erforderlich ist, aber ich habe " -"keine.**" +#: ../system/integrations/checkmk/admin-panel-reference.rst:15 +msgid "(Applies to :ref:`API alerts ` only.)" +msgstr "(Gilt nur für :ref:`API alerts `.)" -#: ../system/integrations/pgp/index.rst:125 +#: ../system/integrations/checkmk/admin-panel-reference.rst:21 +msgid "Auto close" +msgstr "Automatisch schließen" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:18 msgid "" -"If the key is secured with a passphrase, you have to provide it for the " -"import in Zammad. It is possible that keys may have an empty passphrase. " -"However, this is *not* recommended." +"Should Zammad automatically close tickets if a service has recovered on its " +"own?" msgstr "" -"Wenn der Schlüssel mit einer Passphrase gesichert ist, müssen Sie diese für " -"den Import in Zammad angeben. Es ist möglich, dass die Schlüssel eine leere " -"Passphrase haben. Dies wird jedoch *nicht* empfohlen." +"Soll Zammad Tickets automatisch schließen, wenn sich ein Dienst von selbst " +"\"erholt\" hat?" -#: ../system/integrations/pgp/index.rst:132 -msgid "**How do my customers get my new key?**" -msgstr "**Wie bekommen meine Kunden meinen neuen Schlüssel?**" +#: ../system/integrations/checkmk/admin-panel-reference.rst:21 +msgid "(Agents will receive notifications for such closures as appropriate.)" +msgstr "" +"(Agenten werden gegebenenfalls über solche Schließungen benachrichtigt.)" -#: ../system/integrations/pgp/index.rst:130 +#: ../system/integrations/checkmk/admin-panel-reference.rst:30 +msgid "Auto-close state" +msgstr "Automatisch-Schließen-Status" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:24 +msgid "What ticket state should be applied when “auto-closing” a ticket?" +msgstr "" +"Welcher Ticketstatus soll beim \"automatischen Schließen\" eines Tickets " +"angewendet werden?" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:26 msgid "" -"You have to provide your **public** key in advance. Your customer also has " -"to configure PGP in their email workflow and import your public key. The " -"other way round, you have to get the public key of your customer and have to " -"import it to Zammad." +"You can choose from the seven built-in ticket states. If these states aren't " +"enough for you, you can :ref:`define a new ticket state ` for this purpose as well. This can be useful for tracking " +"tickets with :doc:`reports `, for example." msgstr "" -"Sie müssen Ihren **öffentlichen** Schlüssel im Voraus bereitstellen. Ihr " -"Kunde muss außerdem PGP in seinem E-Mail-Workflow konfigurieren und Ihren " -"öffentlichen Schlüssel importieren. Umgekehrt müssen Sie sich den " -"öffentlichen Schlüssel Ihres Kunden besorgen und ihn in Zammad importieren." +"Sie können aus den sieben eingebauten Ticketstatus wählen. Wenn Ihnen diese " +"Status nicht ausreichen, können Sie auch einen :ref:`neuen Status ` für diesen Zweck definieren. Dies kann z.B. für die " +"Auswertung von Tickets mit :doc:`Berichten ` " +"nützlich sein." -#: ../system/integrations/slack.rst:2 -msgid "Slack" -msgstr "Slack" +#: ../system/integrations/checkmk/admin-panel-reference.rst:35 +#: ../system/integrations/cti/includes/recent-logs.include.rst:2 +#: ../system/integrations/ldap/index.rst:74 +#: ../system/integrations/pgp/index.rst:106 +msgid "Recent Logs" +msgstr "Aktuellste Protokolle" -#: ../system/integrations/slack.rst:4 -msgid "**⚠️ Deprecation warning ⚠️**" -msgstr "**⚠️ Warnung: Abkündigung der Integration ⚠️**" +#: ../system/integrations/checkmk/admin-panel-reference.rst:None +msgid "Screenshot of Checkmk \"Recent Logs\" section" +msgstr "Screenshot des Checkmk-Bereichs \"Aktuellste Protokolle\"" -#: ../system/integrations/slack.rst:6 +#: ../system/integrations/checkmk/admin-panel-reference.rst:41 msgid "" -"Zammad 7 will no longer support this dedicated Slack integration. It is " -"recommended to switch to :doc:`pre-defined webhooks ` instead. Existing Slack integrations should " -"be migrated manually before this feature is dropped." +"If you're having trouble getting Zammad and Checkmk to play nicely together, " +"this section can help you troubleshoot." msgstr "" -"Zammad 7 wird die Slack-Integration nicht mehr unterstützen. Es wird " -"empfohlen, stattdessen auf :doc:`vordefinierte Webhooks ` umzusteigen. Bestehende Slack-Integrationen " -"sollten manuell migriert werden, bevor diese Funktion eingestellt wird." +"Wenn Sie Probleme bei der Verbindung von Zammad und Checkmk haben kann " +"dieser Abschnitt Ihnen bei der Fehlersuche helfen." -#: ../system/integrations/slack.rst:14 +#: ../system/integrations/checkmk/admin-panel-reference.rst:44 msgid "" -"In order to use this feature, please add a new Slack app to your Workspace. " -"The App you need is called ``Incoming WebHooks`` ." +"It contains a record of the fifty most recent transactions that Zammad knows " +"about, including each one's request/response details and return status." msgstr "" -"Um diese Funktion nutzen zu können, fügen Sie bitte eine neue Slack-App zu " -"Ihrem Arbeitsbereich hinzu. Die App, die Sie benötigen, heißt ``Incoming " -"WebHooks``." +"Sie enthält eine Aufzeichnung der letzten 50 Einträge, die Zammad bekannt " +"sind, einschließlich der Details zu jeder Anfrage/Antwort und des " +"zurückgegebenen Status." -#: ../system/integrations/slack.rst:18 -msgid "Why Do I Need This Feature?" -msgstr "Warum brauche ich diese Funktion?" +#: ../system/integrations/checkmk/api-reference.rst:2 +msgid "API Reference" +msgstr "API-Referenz" -#: ../system/integrations/slack.rst:20 +#: ../system/integrations/checkmk/api-reference.rst:4 msgid "" -"If you're already using Slack for your team communication, you'll love this " -"feature! Our Slack integration can push ticket notifications about the last " -"ticket article based on the following events:" +"For most users, :ref:`the sample scripts from the Setup Guide ` will do the job just fine. But if you want more fine-grained control" +"—for instance, to create high- and low-priority tickets for different types " +"of system events—then you'll have to customize the data those scripts send " +"to Zammad." msgstr "" -"Wenn Sie bereits Slack für Ihre Teamkommunikation nutzen, werden Sie diese " -"Funktion lieben! Unsere Slack-Integration kann Ticket-Benachrichtigungen " -"über den letzten Ticket-Artikel basierend auf den folgenden Ereignissen " -"versenden:" - -#: ../system/integrations/slack.rst:24 -msgid "on Ticket creation" -msgstr "bei Ticketerstellung" +"Für die meisten Benutzer sind die :ref:`Beispielskripte aus dem " +"Einrichtungsanleitung ` völlig ausreichend. Wenn Sie " +"jedoch eine feinere Steuerung wünschen, z.B. um Tickets mit hoher und " +"niedriger Priorität für verschiedene Arten von Systemereignissen zu " +"erstellen, müssen Sie die Daten, die diese Skripte an Zammad senden, " +"anpassen." -#: ../system/integrations/slack.rst:25 -msgid "on Ticket updates" -msgstr "bei Ticketaktualisierung" +#: ../system/integrations/checkmk/api-reference.rst:15 +msgid "" +"This custom script will automatically set all tickets it creates to **high " +"priority** and **assign them to charlie@chrispresso.com**." +msgstr "" +"Dieses benutzerdefinierte Skript setzt alle Tickets, die es erstellt, " +"automatisch auf **hohe Priorität** und **weist sie charlie@chrispresso.com** " +"zu." -#: ../system/integrations/slack.rst:26 -msgid "on reached reminders" -msgstr "beim Erreichen einer Erinnerung" +#: ../system/integrations/checkmk/api-reference.rst:32 +msgid "How Does it Work?" +msgstr "Wie funktioniert das?" -#: ../system/integrations/slack.rst:27 -msgid "a Ticket has escalated" -msgstr "ein Ticket ist eskaliert" +#: ../system/integrations/checkmk/api-reference.rst:34 +msgid "" +"There are two kinds of data you can pass to the API, both in the form of key-" +"value pairs:" +msgstr "" +"Es gibt zwei Arten von Daten, die Sie an die API übergeben können, beide in " +"Form von Schlüssel-Wert-Paaren:" -#: ../system/integrations/slack.rst:28 -msgid "a Ticket is going to escalate" -msgstr "ein Ticket ist kurz vorm Eskalieren" +#: ../system/integrations/checkmk/api-reference.rst:44 +msgid "Checkmk parameters" +msgstr "Checkmk-Parameter" -#: ../system/integrations/slack.rst:30 +#: ../system/integrations/checkmk/api-reference.rst:38 msgid "" -"Zammad will provide the Ticket title, a direct link to the Ticket, the event " -"type (creation, updated, escalation), the customer, time and the last " -"article that has triggered the notification." -msgstr "" -"Zammad liefert den Titel des Tickets, einen direkten Link zum Ticket, den " -"Ereignistyp (Erstellung, Aktualisierung, Eskalation), den Kunden, die " -"Uhrzeit und den letzten Artikel, der die Benachrichtigung ausgelöst hat." - -#: ../system/integrations/slack.rst:34 -msgid "" -"This will give you further options, as you can see e.g. escalating tickets " -"that are assigned to an agent that's e.g. absent. You can interact faster, " -"as you might see problems earlier (or even before the problem gets one)." +"are required, and make up the **contents** of the resulting tickets/" +"articles. They also determine whether an event creates a new ticket or " +"updates/closes an existing one." msgstr "" -"Dadurch erhalten Sie weitere Optionen, da Sie z.B. eskalierende Tickets " -"sehen können, die einem Agenten zugewiesen sind, der z.B. abwesend ist. Sie " -"können schneller interagieren, da Sie Probleme früher erkennen können (oder " -"sogar bevor das Problem eines wird)." +"sind erforderlich und bilden den **Inhalt** der resultierenden Tickets/" +"Artikel. Sie bestimmen auch, ob ein Ereignis ein neues Ticket erstellt oder " +"ein bestehendes aktualisiert/schließt." -#: ../system/integrations/slack.rst:38 +#: ../system/integrations/checkmk/api-reference.rst:42 msgid "" -"If needed and wanted, you can even discuss directly about the topic before " -"sending an answer to the customer. Another possible use case would be a " -"agent monitoring new agents and their answers to tickets." +"These are the only values used in the sample scripts. **Use them as-is**; " +"technically, they can be customized, but it's hard to imagine a good reason " +"for it." msgstr "" -"Falls erforderlich und gewünscht, können Sie sogar direkt über das Thema " -"diskutieren, bevor Sie eine Antwort an den Kunden senden. Ein weiterer " -"möglicher Anwendungsfall wäre ein Agent, der neue Agenten und deren " -"Antworten auf Tickets überwacht." +"Dies sind die einzigen Werte, die in den Beispielskripten verwendet werden. " +"**Verwenden Sie sie am besten genau so**. Sie können auch angepasst werden, " +"aber uns fällt kein guter Grund dafür ein." -#: ../system/integrations/slack.rst:44 -msgid "Configure the Integration" -msgstr "Konfiguration der Integration" +#: ../system/integrations/checkmk/api-reference.rst:52 +msgid "Ticket attributes" +msgstr "Ticket Attribute" -#: ../system/integrations/slack.rst:46 +#: ../system/integrations/checkmk/api-reference.rst:47 msgid "" -"First of all, please go to your slack workspace - go to administration => " -"Manage Apps. If you don't have an app yet, you can simply add a new one - " -"just search for ``Incoming WebHooks`` and customize the app to your needs." +"are optional, and can be used to **adjust settings** on newly created " +"tickets (*e.g.,* set the owner, group, priority, or state)." msgstr "" -"Als erstes gehen Sie bitte in Ihren Slack-Arbeitsbereich - gehen Sie zu " -"Administration => Manage Apps. Wenn Sie noch keine App haben, können Sie " -"einfach eine neue hinzufügen - suchen Sie einfach nach ``Incoming WebHooks`` " -"und passen Sie die App an Ihre Bedürfnisse an." +"sind optional und können verwendet werden, um **Einstellungen** für neu " +"erstellte Tickets vorzunehmen (*z.B.* den Besitzer, die Gruppe, die " +"Priorität oder den Status festzulegen)." -#: ../system/integrations/slack.rst:50 +#: ../system/integrations/checkmk/api-reference.rst:50 msgid "" -"Choose (or create) the channel Zammad should post it's information to and " -"press on \"Add Incoming WebHooks integration\". If you're ready, copy the " -"provided WebHook URL and go to your Zammad installation." +"If you want to customize your Checkmk alert script, do it with these. Simply " +"add an extra “form” option for each one (``-F \"key=value\"``) to your " +"script's ``curl`` command line, as in the example above." msgstr "" -"Wählen (oder erstellen) Sie den Kanal, auf dem Zammad seine Informationen " -"veröffentlichen soll, und klicken Sie auf \"Add Incoming WebHooks " -"integration\". Wenn Sie bereit sind, kopieren Sie die bereitgestellte " -"WebHook-URL und gehen Sie zu Ihrer Zammad-Installation." +"Wenn Sie Ihr Checkmk-Warnskript anpassen wollen, können Sie dies mit diesen " +"tun. Fügen Sie einfach eine zusätzliche \"form\"-Option für jede dieser " +"Optionen (``-F \"key=value\"``) in die ``curl``-Befehlszeile Ihres Skripts " +"ein, wie im obigen Beispiel." -#: ../system/integrations/slack.rst:56 -msgid "" -"You need administrative rights on the Slack Workspace. The link to the app " -"directory is normally ``https://[workspace-name].slack.com/apps`` ." -msgstr "" -"Sie benötigen administrative Rechte im Slack Workspace. Der Link zum App-" -"Verzeichnis lautet normalerweise ``https://[workspace-name].slack.com/apps``." +#: ../system/integrations/checkmk/api-reference.rst:54 +msgid "💡 **It's just an API endpoint!**" +msgstr "💡 **Es ist nur ein API-Endpunkt!**" -#: ../system/integrations/slack.rst:63 +#: ../system/integrations/checkmk/api-reference.rst:56 msgid "" -"To configure the slack integration, log in to Zammad and go to Integrations " -"(System) => Slack in the admin panel." +"When using Checkmk integration, messages need to be formatted in a certain " +"way, but that *doesn't mean the messages actually have to come from Checkmk*." msgstr "" -"Um die Slack-Integration zu konfigurieren, loggen Sie sich in Zammad ein und " -"gehen Sie im Adminpanel zu System > Integrationen > Slack." +"Wenn Sie die Checkmk-Integration verwenden, müssen die Nachrichten auf eine " +"bestimmte Art und Weise formatiert werden, aber das bedeutet *nicht, dass " +"die Nachrichten tatsächlich von Checkmk kommen müssen*." -#: ../system/integrations/slack.rst:66 +#: ../system/integrations/checkmk/api-reference.rst:59 msgid "" -"Here you can choose on what evens Zammad should post information about a " -"ticket to your Slack channel. Next you need to device what groups shall be " -"affected by this, as anybody with access to that specific Slack channel can " -"read at least parts of the ticket this might be a privacy issue, if you " -"select the wrong groups. The username is simply the name that Zammad uses as " -"display name inside the Slack chat. The channel defines the Slack channel " -"the information is being posted in. As last option, you can set a custom " -"icon for posting to slack." +"If you use another monitoring tool that's not officially supported by " +"Zammad, there's probably a way to make it work with your Checkmk callback " +"URL." msgstr "" -"Hier können Sie auswählen, an welchen Ereignissen Zammad Informationen über " -"ein Ticket in Ihrem Slack-Kanal posten soll. Als nächstes müssen Sie " -"festlegen, welche Gruppen davon betroffen sein sollen, da jeder, der Zugang " -"zu diesem speziellen Slack-Kanal hat, zumindest Teile des Tickets lesen " -"kann. Es kann ein Datenschutz-Problem sein, wenn Sie die falschen Gruppen " -"auswählen. Der Benutzername ist der Name, den Zammad als Anzeigename " -"innerhalb des Slack-Chats verwendet. Der Kanal definiert den Slack-Kanal, in " -"dem die Information gepostet wird. Als letzte Option können Sie ein " -"benutzerdefiniertes Symbol für das Posten in Slack festlegen." +"Wenn Sie ein anderes Monitoring-Tool verwenden, das nicht offiziell von " +"Zammad unterstützt wird, gibt es wahrscheinlich eine Möglichkeit, es mit " +"Ihrer Checkmk-Callback-URL zum Laufen zu bringen." -#: ../system/integrations/slack.rst:74 -msgid "" -"When you're ready, just hit \"Submit\" and enable the integration. Zammad " -"will now post new ticket information based on the trigger you chose. Below " -"the options you have the recent log that shows the latest requests to Slack " -"for debugging if needed." -msgstr "" -"Wenn Sie soweit sind, klicken Sie auf \"Absenden\" und aktivieren Sie die " -"Integration. Zammad wird nun neue Ticketinformationen basierend auf dem von " -"Ihnen gewählten Trigger posten. Unterhalb der Optionen finden Sie die " -"aktuellsten Protokolleinträge, die die letzten Anfragen an Slack zur " -"Fehlersuche anzeigen, falls erforderlich." +#: ../system/integrations/checkmk/api-reference.rst:63 +msgid "Checkmk Parameters" +msgstr "Checkmk-Parameter" -#: ../system/integrations/slack.rst:81 +#: ../system/integrations/checkmk/api-reference.rst:65 msgid "" -"If you leave the Icon URL empty, Zammad will use the Zammad logo instead. " -"The icon should be a square PNG file." +"When a notification is received, Zammad creates a new article containing the " +"details of the event that triggered it:" msgstr "" -"Wenn Sie die Icon URL leer lassen, wird Zammad stattdessen das Zammad-Logo " -"verwenden. Das Icon sollte eine quadratische PNG-Datei sein." +"Wenn eine Benachrichtigung eingeht, erstellt Zammad einen neuen Artikel mit " +"den Einzelheiten des Ereignisses, das die Benachrichtigung ausgelöst hat:" -#: ../system/integrations/slack.rst:90 -msgid "" -"The following figure shows how it will look if you choose to receive updates " -"on created and updated tickets. On every post Zammad sends to the Slack " -"channel, you can create new threads to discuss about the new article." -msgstr "" -"Die folgende Abbildung zeigt, wie es aussieht, wenn Sie sich dafür " -"entscheiden, Updates für erstellte und aktualisierte Tickets zu erhalten. " -"Bei jedem Beitrag, den Zammad an den Slack-Kanal sendet, können Sie neue " -"Threads erstellen, um über den neuen Artikel zu diskutieren." +#: ../system/integrations/checkmk/api-reference.rst:None +msgid "Checkmk article body" +msgstr "Checkmk Artikelinhalt" -#: ../system/integrations/slack.rst:96 +#: ../system/integrations/checkmk/api-reference.rst:72 msgid "" -"If you just want to keep track of soon escalating or already escalated " -"tickets, it will look the the following figure. Zammad changes the color in " -"front of the post so you can easily see the state of the ticket." +"These details come from the fields listed below, which correspond to " +"parameters provided by Checkmk (``$NOTIFY_*``)." msgstr "" -"Wenn Sie nur den Überblick über bald eskalierende oder bereits eskalierte " -"Tickets behalten möchten, sieht es wie in der folgenden Abbildung aus. " -"Zammad ändert die Farbe vor dem Beitrag, damit Sie den Status des Tickets " -"leicht erkennen können." +"Diese Angaben stammen aus den unten aufgeführten Feldern, die den von " +"Checkmk bereitgestellten Parametern entsprechen (``$NOTIFY_*``)." -#: ../system/integrations/slack.rst:102 +#: ../system/integrations/checkmk/api-reference.rst:75 +msgid "**Required fields are marked with an asterisk (\\*).**" +msgstr "**Erforderliche Felder sind mit einem Stern (\\*) gekennzeichnet.**" + +#: ../system/integrations/checkmk/api-reference.rst:79 +msgid "event_id\\*" +msgstr "event_id\\*" + +#: ../system/integrations/checkmk/api-reference.rst:78 msgid "" -"If you change the state, Zammad will also put information on what state the " -"ticket gets and (if pending state) the date until it pends. You'll also " -"recognize the color codes in front of posts on slack, as they are exact the " -"same the ticket state colors you'll see in Zammad!" +"A unique ID for the system event. (``$NOTIFY_SERVICEPROBLEMID`` / " +"``$NOTIFY_HOSTPROBLEMID``)" msgstr "" -"Wenn Sie den Status ändern, wird Zammad auch Informationen darüber anzeigen, " -"welchen Status das Ticket bekommt und (falls es sich um einen \"Warten auf..." -"\" Status handelt) das Datum, bis zu dem gewartet wird. Sie werden auch die " -"Farbcodes vor den Beiträgen auf Slack erkennen, da sie genau die gleichen " -"sind wie die Farben des Ticketstatus, die Sie in Zammad sehen werden!" +"Eine eindeutige ID für das Systemereignis. (``$NOTIFY_SERVICEPROBLEMID`` / " +"``$NOTIFY_HOSTPROBLEMID``)" -#: ../system/integrations/smime/index.rst:2 -msgid "S/MIME" -msgstr "S/MIME" +#: ../system/integrations/checkmk/api-reference.rst:86 +msgid "host\\*" +msgstr "host\\*" -#: ../system/integrations/smime/index.rst:11 +#: ../system/integrations/checkmk/api-reference.rst:82 msgid "" -"S/MIME is the most widely-supported method for secure email communication. " -"With S/MIME, you can exchange **signed** and **encrypted** messages with " -"others." +"The hostname of the system that the event originated from. " +"(``$NOTIFY_HOSTNAME``)" msgstr "" -"S/MIME ist die am weitesten verbreitete Methode für sichere E-Mail-" -"Kommunikation. Mit S/MIME können Sie **signierte** und **verschlüsselte** " -"Nachrichten mit anderen austauschen." +"Der Hostname des Systems, von dem das Ereignis ausgeht. " +"(``$NOTIFY_HOSTNAME``)" -#: ../system/integrations/smime/index.rst:15 +#: ../system/integrations/checkmk/api-reference.rst:85 msgid "" -"is proof that a message hasn't been tampered with or sent by an impersonator." +"Used to determine if a new event belongs to an existing ticket. Also used in " +"the subject line of the resulting article (“ is ”)." msgstr "" -"ist der Beweis, dass eine Nachricht nicht manipuliert oder von einem " -"Unbekannten gesendet wurde." +"Wird verwendet, um festzustellen, ob ein neues Ereignis zu einem bestehenden " +"Ticket gehört. Wird auch in der Betreffzeile des resultierenden Artikels " +"verwendet (\" ist \")." -#: ../system/integrations/smime/index.rst:17 +#: ../system/integrations/checkmk/api-reference.rst:96 +msgid "service" +msgstr "service" + +#: ../system/integrations/checkmk/api-reference.rst:89 msgid "" -"In other words, it guarantees a message's **integrity** and **authenticity**." +"The name of the service that the event originated from. " +"(``$NOTIFY_SERVICEDESC``)" msgstr "" -"Mit anderen Worten, es garantiert die **Integrität** und **Authentizität** " -"einer Nachricht." +"Der Name des Dienstes, von dem das Ereignis ausgeht. " +"(``$NOTIFY_SERVICEDESC``)" -#: ../system/integrations/smime/index.rst:22 -msgid "In other words, it guarantees **privacy** and **data security**." +#: ../system/integrations/checkmk/api-reference.rst:92 +msgid "Used to determine if a new event belongs to an existing ticket." msgstr "" -"Mit anderen Worten, es garantiert **Privatsphäre** und **Datensicherheit**." +"Wird verwendet, um festzustellen, ob ein neues Ereignis zu einem bestehenden " +"Ticket gehört." -#: ../system/integrations/smime/index.rst:28 -msgid "Screencast demo of S/MIME features for both new tickets and replies" -msgstr "" -"Bildschirmaufzeichnung von S/MIME-Funktionen für neue Tickets und Antworten" +#: ../system/integrations/checkmk/api-reference.rst:94 +#: ../system/integrations/checkmk/api-reference.rst:110 +msgid "Displayed as ``-`` when omitted." +msgstr "Wird als ``-`` angezeigt, wenn es weggelassen wird." -#: ../system/integrations/smime/index.rst:28 +#: ../system/integrations/checkmk/api-reference.rst:104 +msgid "state\\*" +msgstr "state\\*" + +#: ../system/integrations/checkmk/api-reference.rst:99 msgid "" -"Once S/MIME has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " -"appear in the ticket composer." +"The current state of the service or host in question. " +"(``$NOTIFY_SERVICESTATE`` / ``$NOTIFY_HOSTSTATE``)" msgstr "" -"Sobald S/MIME aktiviert ist, erscheinen die Schaltflächen 🔒 " -"**Verschlüsseln** und ✅ **Signieren** in der Ticket Ansicht." - -#: ../system/integrations/smime/index.rst:32 -msgid ":doc:`🔪 Prerequisites `" -msgstr ":doc:`🔪 Voraussetzungen `" +"Der aktuelle Zustand des entsprechenden Dienstes oder Hosts. " +"(``$NOTIFY_SERVICESTATE`` / ``$NOTIFY_HOSTSTATE``)" -#: ../system/integrations/smime/index.rst:31 +#: ../system/integrations/checkmk/api-reference.rst:102 msgid "" -"New to S/MIME? This section helps you to find certificate providers and " -"points out Limitations." -msgstr "" -"Neu in S/MIME? Dieser Abschnitt hilft Ihnen, Zertifikatsanbieter zu finden " -"und weist auf Einschränkungen hin." - -#: ../system/integrations/smime/index.rst:35 -msgid ":doc:`📝 Manage Certificates `" -msgstr ":doc:`📝 Zertifikate verwalten `" - -#: ../system/integrations/smime/index.rst:35 -msgid "Add and download certificates; configure group default behaviors." +"Used to detect when a ticket should be auto-closed (*i.e.,* on ``OK``/" +"``UP``). Also used in the subject line of the resulting article (“ is " +"”)." msgstr "" -"Hinzufügen und Herunterladen von Zertifikaten; Konfigurieren des " -"Standardverhaltens von Gruppen." - -#: ../system/integrations/smime/index.rst:38 -msgid ":doc:`😦 Troubleshooting `" -msgstr ":doc:`😦 Fehlersuche `" +"Wird verwendet, um zu erkennen, wann ein Ticket automatisch geschlossen " +"werden soll (*d.h.* bei ``OK``/``UP``). Wird auch in der Betreffzeile des " +"resultierenden Artikels verwendet (\" ist \")." -#: ../system/integrations/smime/index.rst:38 -msgid "Took a wrong turn? About recent logs and common issues." -msgstr "Sie sind falsch abgebogen? Über Protokolle und häufige Probleme." +#: ../system/integrations/checkmk/api-reference.rst:110 +msgid "text" +msgstr "text" -#: ../system/integrations/smime/index.rst:43 +#: ../system/integrations/checkmk/api-reference.rst:107 msgid "" -"For more details on how S/MIME integration works on the agent side, see the :" -"user-docs:`user docs `." +"The output of the process that triggered the event. " +"(``$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" msgstr "" -"Wie die S/MIME-Integration auf Agenten-Seite funktioniert erfahren Sie in " -"der :user-docs:`Benutzerdokumentation `." - -#: ../system/integrations/smime/manage-certificates.rst:2 -msgid "Manage Certificates" -msgstr "Verwalten von Zertifikaten" +"Die Ausgabe des Prozesses, der das Ereignis ausgelöst hat. " +"(``$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" -#: ../system/integrations/smime/manage-certificates.rst:4 +#: ../system/integrations/checkmk/api-reference.rst:121 msgid "" -"S/MIME is **disabled by default**. Enable it to start adding certificates." +"The Object Manager attribute panel displays built-in and custom\n" +"attribute names." msgstr "" -"S/MIME ist standardmäßig **deaktiviert**. Aktivieren Sie es, um Zertifikaten " -"hinzuzufügen." +"Die Attributeinstellungen des Objektmanagers zeigen integrierte und " +"benutzerdefinierte Attributnamen an." -#: ../system/integrations/smime/manage-certificates.rst:10 -msgid "Dialogue to add new certificates or private keys" -msgstr "Dialog zum Hinzufügen neuer Zertifikate oder privater Schlüssel" +#: ../system/integrations/checkmk/api-reference.rst:121 +msgid "Find a complete list of ticket attributes in the Object Manager." +msgstr "" +"Eine vollständige Liste der Ticketattribute finden Sie im Objektmanager." -#: ../system/integrations/smime/manage-certificates.rst:10 +#: ../system/integrations/checkmk/api-reference.rst:123 msgid "" -"Manage certificates in the Admin Panel under **System > Integrations > S/" -"MIME**. Certificates may be pasted in as plain text or uploaded from a file." +"Ticket attributes are entirely optional, and can be used to customize the " +"tickets that Checkmk creates. (Note that these attributes will be ignored if " +"a new event belongs to an existing ticket.)" msgstr "" -"Verwalten Sie Zertifikate im Admin Panel unter **System > Integrationen > S/" -"MIME**. Die Zertifikate können als einfacher Text eingefügt oder aus einer " -"Datei hochgeladen werden." - -#: ../system/integrations/smime/manage-certificates.rst:14 -msgid "Add Certificate Data" -msgstr "Zertifikatsdaten hinzufügen" - -#: ../system/integrations/smime/manage-certificates.rst:36 -msgid "Add Certificate" -msgstr "Zertifikat hinzufügen" +"Ticket-Attribute sind völlig optional und können verwendet werden, um die " +"Tickets, die Checkmk erstellt, individuell zu gestalten. (Beachten Sie, dass " +"diese Attribute ignoriert werden, wenn ein neues Ereignis zu einem " +"bestehenden Ticket erstellt wird.)" -#: ../system/integrations/smime/manage-certificates.rst:17 +#: ../system/integrations/checkmk/api-reference.rst:128 msgid "" -"Import public-key certificates for both your own organization and your " -"contacts." +"Why would you want to do this? Maybe you have only one IT guy, and all " +"system monitoring issues should be automatically assigned to him. Or, maybe " +"you're creating multiple notification rules so that database outages take " +"higher priority than disk space warnings." msgstr "" -"Importieren Sie Public-Key-Zertifikate sowohl für Ihr eigenes Unternehmen " -"als auch für Ihre Kontakte." +"Warum sollten Sie das tun? Vielleicht haben Sie nur einen IT-Mitarbeiter, " +"dem alle Probleme bei der Systemüberwachung automatisch zugewiesen werden " +"sollen. Oder vielleicht erstellen Sie mehrere Benachrichtigungsregeln, so " +"dass Datenbankausfälle höhere Priorität haben als Speicherplatzwarnungen." -#: ../system/integrations/smime/manage-certificates.rst:19 -msgid "" -"You can also add a bunch of certificates in one go by providing a single " -"file with all relevant certificates." +#: ../system/integrations/checkmk/api-reference.rst:135 +msgid "In most cases, you'll probably want to set one of the following:" msgstr "" -"Sie können auch eine Reihe von Zertifikaten auf einmal hinzufügen, indem Sie " -"eine einzige Datei mit allen relevanten Zertifikaten bereitstellen." +"In den meisten Fällen werden Sie wahrscheinlich eine der folgenden " +"Einstellungen vornehmen wollen:" -#: ../system/integrations/smime/manage-certificates.rst:22 -msgid "🕵️ **ALWAYS verify certificates in-person or over the phone!**" -msgstr "🕵️ **IMMER die Zertifikate persönlich oder telefonisch überprüfen!**" +#: ../system/integrations/checkmk/api-reference.rst:137 +msgid "group" +msgstr "Gruppe" -#: ../system/integrations/smime/manage-certificates.rst:24 -msgid "" -"The whole point of signatures is to alert you when someone is trying to " -"pretend to be someone they're not. Never accept a certificate from someone " -"online without verifying it first." -msgstr "" -"Der Sinn von Signaturen ist es, Sie zu warnen, wenn jemand versucht sich als " -"jemand auszugeben, der er nicht ist. Akzeptieren Sie niemals ein Zertifikat " -"von jemandem, ohne es vorher zu überprüfen." +#: ../system/integrations/checkmk/api-reference.rst:139 +msgid "state" +msgstr "Status" -#: ../system/integrations/smime/manage-certificates.rst:28 -msgid "📇 **What about trusted certificate authorities?**" -msgstr "📇 **Was ist mit vertrauenswürdigen Zertifizierungsstellen?**" +#: ../system/integrations/checkmk/api-reference.rst:140 +msgid "priority" +msgstr "Priorität" -#: ../system/integrations/smime/manage-certificates.rst:30 +#: ../system/integrations/checkmk/api-reference.rst:142 msgid "" -"In some cases (e.g. when dealing with large enterprises), you may be given a " -"certificate for an entire CA, rather than a single contact. Add it here to " -"trust *all* certificates issued by that CA." +"but in practice, you can set almost any attribute, including :doc:`custom " +"ones you created through the Object Manager `." msgstr "" -"In manchen Fällen (z.B. bei großen Unternehmen) kann es vorkommen, dass Sie " -"ein Zertifikat für eine ganze CA erhalten und nicht nur für einen einzelnen " -"Kontakt. Fügen Sie es hier hinzu, um *allen* von dieser CA ausgestellten " -"Zertifikaten zu vertrauen." +"aber in der Praxis können Sie fast jedes Attribut setzen, einschließlich :" +"doc:`benutzerdefinierter Attribute, die Sie über den Objektmanager ` erstellt haben." -#: ../system/integrations/smime/manage-certificates.rst:35 -msgid "" -"Commercial CAs can usually be verified online. Zammad does not include a " -"list of built-in, trusted CAs." +#: ../system/integrations/checkmk/api-reference.rst:145 +msgid "Please note that the following attributes are **not customizable**:" msgstr "" -"Kommerzielle CAs können in der Regel online verifiziert werden. Zammad " -"enthält keine Liste mit eingebauten, vertrauenswürdigen CAs." +"Bitte beachten Sie, dass die folgenden Attribute **nicht angepasst werden " +"können**:" -#: ../system/integrations/smime/manage-certificates.rst:57 -msgid "Add Private Key" -msgstr "Privaten Schlüssel hinzufügen" +#: ../system/integrations/checkmk/api-reference.rst:147 +msgid "title" +msgstr "title" -#: ../system/integrations/smime/manage-certificates.rst:39 -msgid "" -"Once you've added a public-key certificate, you can import its matching " -"private key." -msgstr "" -"Sobald Sie ein öffentliches Zertifikat hinzugefügt haben können Sie den " -"dazugehörigen privaten Schlüssel importieren." +#: ../system/integrations/checkmk/api-reference.rst:148 +msgid "id" +msgstr "id" -#: ../system/integrations/smime/manage-certificates.rst:42 -msgid "" -"Private keys are for **your own organization only**; never ask your contacts " -"for their private keys." -msgstr "" -"Private Schlüssel sind nur für **Ihre eigene Organisation**; fragen Sie " -"niemals Ihre Kontakte nach deren privaten Schlüsseln." +#: ../system/integrations/checkmk/api-reference.rst:149 +msgid "ticket number" +msgstr "ticket number" -#: ../system/integrations/smime/manage-certificates.rst:0 -msgid "" -"S/MIME integration showing configured certificates and possible issues with " -"Logging" -msgstr "" -"S/MIME-Integration mit konfigurierten Zertifikaten und möglichen Problemen " -"mit der Protokollierung" +#: ../system/integrations/checkmk/api-reference.rst:151 +msgid "created_by_id" +msgstr "created_by_id" -#: ../system/integrations/smime/manage-certificates.rst:50 -msgid "" -"A note is displayed on certificates with a matching private key (see line 2)." -msgstr "" -"Bei Zertifikaten mit passendem privaten Schlüssel wird ein Hinweis angezeigt " -"(siehe Zeile 2)." +#: ../system/integrations/checkmk/api-reference.rst:152 +msgid "updated_by_id" +msgstr "updated_by_id" -#: ../system/integrations/smime/manage-certificates.rst:52 -msgid "📤 **Certificates and private keys must be uploaded separately.**" -msgstr "" -"📤 **Zertifikate und private Schlüssel müssen separat hochgeladen werden.**" +#: ../system/integrations/checkmk/api-reference.rst:155 +msgid "Which Values Can Be Set?" +msgstr "Welche Werte können eingestellt werden?" -#: ../system/integrations/smime/manage-certificates.rst:54 +#: ../system/integrations/checkmk/api-reference.rst:157 +msgid "😵 **Invalid values → unpredictable behavior**" +msgstr "😵 **Ungültige Werte → unvorhersehbares Verhalten**" + +#: ../system/integrations/checkmk/api-reference.rst:159 msgid "" -"If your certificate and private key are bundled together in the same file or " -"PEM block, import it twice (once using each button)." +"If you provide a value that Zammad doesn't understand (*e.g.,* ``-F " +"\"priority=high\"``), it's not always clear what will happen. In some cases, " +"a ticket will be created with the default values instead - but in others, it " +"may not be created at all!" msgstr "" -"Wenn Ihr Zertifikat und Ihr privater Schlüssel in derselben Datei oder " -"demselben PEM-Block gebündelt sind, importieren Sie sie zweimal (einmal mit " -"jeder Schaltfläche)." +"Wenn Sie einen Wert angeben, den Zammad nicht versteht (*z.B.* ``-F " +"\"priority=high\"``), ist nicht immer klar, was passieren wird. In einigen " +"Fällen wird ein Ticket stattdessen mit den Standardwerten erstellt - in " +"anderen Fällen wird es aber vielleicht gar nicht erstellt!" -#: ../system/integrations/smime/manage-certificates.rst:57 -msgid "Please note that bulk imports of private keys are not possible." -msgstr "" -"Bitte beachten Sie, dass ein Massenimport von privaten Schlüsseln nicht " -"möglich ist." +#: ../system/integrations/checkmk/api-reference.rst:164 +msgid "So what values does Zammad understand, then? Well, it depends..." +msgstr "Welche Werte versteht Zammad denn nun? Nun, das kommt darauf an..." -#: ../system/integrations/smime/manage-certificates.rst:60 -msgid "Download Certificate Data" -msgstr "Zertifikat herunterladen" +#: ../system/integrations/checkmk/api-reference.rst:168 +msgid "Use an email address or username:" +msgstr "Verwenden Sie eine E-Mail-Adresse oder einen Benutzernamen:" -#: ../system/integrations/smime/manage-certificates.rst:62 -msgid "" -"You can download the earlier provided certificates and private keys at any " -"time from your Zammad instance." -msgstr "" -"Sie können die zuvor bereitgestellten Zertifikate und privaten Schlüssel " -"jederzeit von Ihrer Zammad-Instanz herunterladen." +#: ../system/integrations/checkmk/api-reference.rst:190 +msgid "group & priority" +msgstr "Gruppe & Priorität" -#: ../system/integrations/smime/manage-certificates.rst:65 -msgid "" -"Please note that passphrase-protected private keys stay protected and when " -"you download them, you have to know the passphrase to use them after " -"downloading." -msgstr "" -"Bitte beachten Sie, dass Passphrase geschützte private Schlüssel geschützt " -"bleiben. Wenn Sie sie herunterladen, müssen Sie die Passphrase kennen, um " -"sie nach dem Herunterladen zu verwenden." +#: ../system/integrations/checkmk/api-reference.rst:175 +msgid "Refer to the dropdown menus in the ticket pane:" +msgstr "Beachten Sie die Dropdown-Menüs im Ticketbereich:" -#: ../system/integrations/smime/manage-certificates.rst:73 -msgid "Dialogue to download certificates or private keys" -msgstr "Dialog zum Herunterladen von Zertifikaten oder privaten Schlüsseln" +#: ../system/integrations/checkmk/api-reference.rst:0 +msgid "See possible values for certain attributes in the ticket pane." +msgstr "Siehe mögliche Werte für bestimmte Attribute im Ticketbereich." -#: ../system/integrations/smime/manage-certificates.rst:73 -msgid "Download stored certificates and their keys" -msgstr "Herunterladen gespeicherter Zertifikate und ihrer Schlüssel" +#: ../system/integrations/checkmk/api-reference.rst:187 +msgid "🙅 **Ticket state CANNOT be set this way!**" +msgstr "🙅 **Der Ticketstatus kann auf diese Weise NICHT eingestellt werden!**" -#: ../system/integrations/smime/manage-certificates.rst:78 +#: ../system/integrations/checkmk/api-reference.rst:189 msgid "" -"The ticket composer will set all outgoing messages to **signed and " -"encrypted** by default (assuming the required certificates exist)." +"Why? Because ``-F \"state=...\"`` is already used :ref:`as a Checkmk " +"parameter `." msgstr "" -"Die Ticket-Bearbeitungs-Funktion setzt alle ausgehenden Nachrichten " -"standardmäßig auf **signiert und verschlüsselt** (vorausgesetzt, die " -"erforderlichen Zertifikate sind vorhanden)." - -#: ../system/integrations/smime/manage-certificates.rst:82 -msgid "These defaults can be modified on a per-group basis:" -msgstr "Diese Standardwerte können für jede Gruppe einzeln geändert werden:" +"Warum? Weil ``-F \"state=...\"`` bereits :ref:`als ein Checkmk-Parameter " +"` verwendet wird." -#: ../system/integrations/smime/manage-certificates.rst:None -msgid "Zammad allowing to choose the default behavior on per group basis" -msgstr "Zammad ermöglicht die Auswahl des Standardverhaltens für jede Gruppe" +#: ../system/integrations/checkmk/api-reference.rst:222 +msgid "Everything Else" +msgstr "Alles andere" -#: ../system/integrations/smime/manage-certificates.rst:89 +#: ../system/integrations/checkmk/api-reference.rst:193 msgid "" -"Of course, agents can always manually change these settings on each email " -"they send out." +"To set any other attributes, it helps to know your way around the :docs:" +"`rails console `. Valid values are those that you can " +"set with a string:" msgstr "" -"Natürlich können Agenten diese Einstellungen bei jeder E-Mail, die sie " -"versenden, manuell ändern." +"Um andere Attribute zu setzen, hilft es, sich in der :docs:`rails console ` auszukennen. Gültige Werte sind diejenigen, die Sie mit " +"einer Zeichenkette setzen können:" -#: ../system/integrations/smime/prerequisites.rst:4 -msgid "A certificate *and* private key for your own organization" -msgstr "" -"Ein Zertifikat *und* ein privater Schlüssel für Ihre eigene Organisation" +#: ../system/integrations/checkmk/api-reference.rst:218 +msgid "These values can then be passed directly to the API:" +msgstr "Diese Werte können dann direkt an die API übergeben werden:" -#: ../system/integrations/smime/prerequisites.rst:6 -msgid "" -"(Use this to ✒️ **sign outgoing messages** and 🔓 **decrypt incoming " -"messages**.)" -msgstr "" -"(Verwenden Sie dies, um ✒️ **Ausgehende Nachrichten zu signieren** und 🔓 " -"**Eingehende Nachrichten zu entschlüsseln**.)" +#: ../system/integrations/checkmk/index.rst:16 +msgid "How does it work?" +msgstr "Wie funktioniert das?" -#: ../system/integrations/smime/prerequisites.rst:9 -msgid "" -"Certificates belonging your contacts, or their issuing certificate authority " -"(CA)" -msgstr "" -"Zertifikate, die Ihren Kontakten gehören, oder deren ausstellender " -"Zertifizierungsstelle (CA)" +#: ../system/integrations/checkmk/index.rst:2 +msgid "Checkmk" +msgstr "Checkmk" -#: ../system/integrations/smime/prerequisites.rst:11 +#: ../system/integrations/checkmk/index.rst:4 msgid "" -"(Use these to ✅ **verify incoming message signatures** and 🔒 **encrypt " -"outgoing messages**.)" +"`Checkmk `_ is a powerful IT monitoring tool that can " +"send real-time status alerts to Zammad via email or REST API. Set these " +"alerts up in Checkmk, and Zammad will automatically create, update, and " +"close tickets based on the health of your system:" msgstr "" -"(Verwenden Sie diese, um ✅ **die Signaturen eingehender Nachrichten zu " -"überprüfen** und 🔒 **ausgehende Nachrichten zu verschlüsseln**.)" +"`Checkmk `_ ist ein mächtiges IT-Tool für Monitoring, " +"das Echtzeit-Alarme an Zammad via E-Mail oder REST-API senden kann. " +"Konfigurieren Sie die Alarme in Checkmk und Zammad wird automatisch Tickets " +"basierend auf der Systemstatus erstellen, aktualisieren und schließen:" -#: ../system/integrations/smime/prerequisites.rst:14 -msgid "🙋 **I'm new to S/MIME. Where can I get a certificate?**" -msgstr "🙋 **Ich bin neu in S/MIME. Woher bekomme ich ein Zertifikat?**" +#: ../system/integrations/checkmk/index.rst:14 +msgid "Screenshot of ticket created by Checkmk notifications" +msgstr "Screenshot eines durch Checkmk-Benachrichtigungen erstellten Tickets" -#: ../system/integrations/smime/prerequisites.rst:16 +#: ../system/integrations/checkmk/index.rst:14 +msgid "Multiple alerts, same ticket." +msgstr "Mehrere Alarme, dasselbe Ticket." + +#: ../system/integrations/checkmk/setup-guide.rst:2 +msgid "Setup Guide" +msgstr "Einrichtungs-Anleitung" + +#: ../system/integrations/checkmk/setup-guide.rst:4 msgid "" -"The easiest way to get certificates is to buy an annual subscription through " -"a commercial CA, such as:" +"Whenever the Checkmk integration is enabled, Zammad listens for messages on " +"its API and over email. As long as those messages follow the required " +"format, Zammad will create new tickets (or find and update existing ones) " +"based on the message contents." msgstr "" -"Der einfachste Weg, Zertifikate zu erhalten, ist der Kauf eines " -"Jahresabonnements über eine kommerzielle Zertifizierungsstelle, wie z.B.:" +"Immer wenn die Checkmk-Integration aktiviert ist, lauscht Zammad auf " +"Nachrichten über seine API und per E-Mail. Solange diese Nachrichten dem " +"erforderlichen Format entsprechen, erstellt Zammad neue Tickets (oder findet " +"und aktualisiert bestehende) auf der Grundlage der Nachrichteninhalte." -#: ../system/integrations/smime/prerequisites.rst:19 +#: ../system/integrations/checkmk/setup-guide.rst:10 msgid "" -"`Sectigo (formerly Comodo) `_" +"That means that “setting up Checkmk integration” is simply a matter of " +"**adding configuration to your Checkmk site**: telling it when to send these " +"messages and what to say. To do that, you'll need to create a new " +"**notification rule** (see `Checkmk's official docs `_ for help with that)." msgstr "" -"`Sectigo (ehemals Comodo) `_" +"Das bedeutet, dass die \"Einrichtung der Checkmk-Integration\" lediglich " +"eine Frage der **Konfiguration Ihrer Checkmk-Seite** ist: Sie müssen ihr " +"mitteilen, wann sie diese Nachrichten senden soll und was sie sagen soll. " +"Dazu müssen Sie eine neue **Benachrichtigungsregel** erstellen (Hilfe dazu " +"finden Sie in der `offiziellen Dokumentation von Checkmk `_ )." -#: ../system/integrations/smime/prerequisites.rst:20 -msgid "`Secorio `_" -msgstr "`Secorio `_" +#: ../system/integrations/checkmk/setup-guide.rst:17 +msgid "" +"As part of this new rule, you'll have to choose a **notification method** " +"(*i.e.,* a script to execute whenever the rule is triggered). This script " +"will be written by you (samples below), and contain the logic for sending " +"API/email messages to Zammad:" +msgstr "" +"Als Teil dieser neuen Regel müssen Sie eine **Benachrichtigungsmethode** " +"wählen (*d.h.* ein Skript, das ausgeführt wird, wenn die Regel ausgelöst " +"wird). Dieses Skript wird von Ihnen geschrieben (Beispiele unten) und " +"enthält die Logik zum Senden von API-/E-Mail-Nachrichten an Zammad:" -#: ../system/integrations/smime/prerequisites.rst:21 -msgid "`GlobalSign `_" -msgstr "`GlobalSign `_" +#: ../system/integrations/checkmk/setup-guide.rst:26 +msgid "Checkmk \"New Rule\" dialog" +msgstr "Checkmk Dialog \"New Rule\"" -#: ../system/integrations/smime/prerequisites.rst:23 -msgid "(Zammad is not affiliated with these CAs in any way.)" +#: ../system/integrations/checkmk/setup-guide.rst:26 +msgid "" +"Find your custom scripts in the Checkmk WATO under **Notifications > New " +"Rule > Notification Method**." msgstr "" -"(Zammad ist in keiner Weise mit diesen Zertifizierungsstellen verbunden.)" +"Sie finden Ihre benutzerdefinierten Skripte in der Checkmk WATO unter " +"**Notifications > New Rule > Notification Method**." -#: ../system/integrations/smime/prerequisites.rst:25 +#: ../system/integrations/checkmk/setup-guide.rst:29 msgid "" -"You can also generate your own self-signed certificates, but the process is " -"complicated and usually 🙅 **involves extra work for your contacts**." +"Once you're done setting up your new rule, you're all set! New tickets " +"should start coming in and auto-updating any time your rule is triggered." msgstr "" -"Sie können auch Ihre eigenen selbstsignierten Zertifikate erstellen, aber " -"das Verfahren ist kompliziert und bedeutet in der Regel 🙅 **mehr Arbeit für " -"Ihre Kontakte**." +"Sobald Sie Ihre neue Regel eingerichtet haben, sind Sie startklar! Neue " +"Tickets sollten nun eingehen und jedes Mal automatisch aktualisiert werden, " +"wenn die Regel ausgelöst wird." -#: ../system/integrations/smime/prerequisites.rst:29 +#: ../system/integrations/checkmk/setup-guide.rst:33 msgid "" -"Bear in mind that 🤝 **S/MIME only works if the other party is using it, too." -"**" +"(If you need help troubleshooting, be sure to check the :ref:`checkmk-recent-" +"logs`.)" msgstr "" -"Denken Sie daran, dass 🤝 **S/MIME nur funktioniert, wenn die andere Partei " -"es auch benutzt.**" +"(Wenn Sie Hilfe bei der Fehlersuche benötigen, sollten Sie die :ref:`checkmk-" +"recent-logs` überprüfen.)" -#: ../system/integrations/smime/prerequisites.rst:32 -msgid "Certificate and Private Key Checks on Upload" -msgstr "Überprüfung von Zertifikat und privatem Schlüssel beim Hochladen" +#: ../system/integrations/checkmk/setup-guide.rst:38 +msgid "API Alerts" +msgstr "API-Warnungen" -#: ../system/integrations/smime/prerequisites.rst:34 +#: ../system/integrations/checkmk/setup-guide.rst:40 msgid "" -"The certificate and public key validation is based on the ``X509v3`` " -"extensions." +"To add these scripts in the Checkmk WATO, copy them into your Checkmk " +"installation directory and make them executable. (Be sure to replace the " +"``zammad.example.com`` callback URL with the one found in your admin panel.)" msgstr "" -"Die Validierung von Zertifikaten und öffentlichen Schlüsseln basiert auf den " -"``X509v3``-Erweiterungen." - -#: ../system/integrations/smime/prerequisites.rst:49 -msgid "Uploading a *client certificate*?" -msgstr "Hochladen eines *Kundenzertifikats*?" +"Um diese Skripte in das Checkmk-WATO einzufügen, kopieren Sie sie in Ihr " +"Checkmk-Installationsverzeichnis und machen sie ausführbar. (Stellen Sie " +"sicher, dass Sie die Callback-URL ``zammad.example.com`` durch Ihre " +"ersetzen, die Sie auch im Admin-Bereich finden.)" -#: ../system/integrations/smime/prerequisites.rst:41 -msgid "The following attributes are required then:" -msgstr "Die folgenden Attribute sind dann erforderlich:" +#: ../system/integrations/checkmk/setup-guide.rst:60 +msgid "Service notification" +msgstr "Service-Benachrichtigung" -#: ../system/integrations/smime/prerequisites.rst:39 -msgid "Subject Alternative Name (at least one email address has to be present)" +#: ../system/integrations/checkmk/setup-guide.rst:46 +msgid "" +"For updates on the status of the software running on your server (*e.g.,* " +"postgres)." msgstr "" -"Subject Alternative Name (mindestens eine E-Mail-Adresse muss vorhanden sein)" +"Für Updates des Status der Software, die auf Ihrem Server läuft (*z.B.* " +"Postgres)." -#: ../system/integrations/smime/prerequisites.rst:40 -msgid "Key Usage (``Digital Signature`` and/or ``Key Encipherment``)" -msgstr "Key Usage (``Digital Signature`` und/oder ``Key Encipherment``)" +#: ../system/integrations/checkmk/setup-guide.rst:75 +msgid "Host notification" +msgstr "Host-Benachrichtigung" -#: ../system/integrations/smime/prerequisites.rst:41 -msgid "Public key algorithm (either ``RSA`` or ``EC``)" -msgstr "Algorithmus des öffentlichen Schlüssels (entweder ``RSA`` oder ``EC``)" +#: ../system/integrations/checkmk/setup-guide.rst:63 +msgid "For updates on the status of the server itself." +msgstr "Für Updates zum Status des Servers selbst." -#: ../system/integrations/smime/prerequisites.rst:43 +#: ../system/integrations/checkmk/setup-guide.rst:77 +msgid "🤔 **What's with all the env vars?**" +msgstr "🤔 **Was ist mit all den env vars?**" + +#: ../system/integrations/checkmk/setup-guide.rst:79 msgid "" -"The Extended Key Usage attribute is optional. If the certificate provides " -"the named attribute, than it must contain the value ``E-mail Protection``." +"Whenever Checkmk runs these scripts, it needs to provide some information " +"about the event that triggered the notification. This information is passed " +"in the form of these ``$NOTIFY_*`` environment variables." msgstr "" -"Das Attribut \"Extended Key Usage\" ist optional. Wenn das Zertifikat das " -"genannte Attribut enthält, dann muss es den Wert ``E-mail Protection`` " -"enthalten." +"Jedes Mal, wenn Checkmk diese Skripte ausführt, muss es einige Informationen " +"über das Ereignis, das die Benachrichtigung ausgelöst hat, bereitstellen. " +"Diese Informationen werden in Form der Umgebungsvariablen ``$NOTIFY_*`` " +"übergeben." -#: ../system/integrations/smime/prerequisites.rst:46 +#: ../system/integrations/checkmk/setup-guide.rst:85 msgid "" -"Please note that any usable email adress has to be prefixed with ``email:`` " -"or ``rfc822:``." -msgstr "" -"Bitte beachten Sie, dass jeder verwendbaren Email-Adresse der Zusatz ``email:" -"`` oder ``rfc822:`` vorangestellt werden muss." - -#: ../system/integrations/smime/prerequisites.rst:49 -msgid "The named public key algorithms are mandatory for private keys as well." +"You can specify additional parameters to pass to the script when you're " +"setting up your notification rule, but the ones you see here are all " +"provided by default." msgstr "" -"Die genannten Algorithmen für öffentliche Schlüssel sind auch für private " -"Schlüssel vorgeschrieben." +"Sie können beim Einrichten Ihrer Benachrichtigungsregel zusätzliche " +"Parameter angeben, die an das Skript übergeben werden sollen, aber die hier " +"gezeigten sind alle standardmäßig vorhanden." -#: ../system/integrations/smime/prerequisites.rst:54 -msgid "Uploading a *CA certificate*?" -msgstr "Hochladen eines *CA-Zertifikats*?" +#: ../system/integrations/checkmk/setup-guide.rst:90 +msgid "Email Alerts" +msgstr "E-Mail-Benachrichtigungen" -#: ../system/integrations/smime/prerequisites.rst:52 +#: ../system/integrations/checkmk/setup-guide.rst:94 msgid "" -"In the case of an uploaded CA certificate, providing the value ``CA:TRUE`` " -"in the attribute *Basic Contstraints*, the previously mentioned attributes " -"are not verified." +"🐞 **There are known bugs** in Zammad's processing of email from Checkmk. " +"This section will be completed once they have been resolved. (Learn more at " +"GitHub issues `#2377 `_ & " +"`#2180 `_.)" msgstr "" -"Im Falle eines hochgeladenen CA-Zertifikats, das im Attribut *Basic " -"Contstraints* den Wert ``CA:TRUE`` aufweist, werden die zuvor genannten " -"Attribute nicht überprüft." +"🐞 **Es gibt bekannte Fehler** bei der Verarbeitung von E-Mails von Checkmk " +"durch Zammad. Dieser Abschnitt wird vervollständigt, sobald sie behoben " +"sind. (Erfahren Sie mehr unter GitHub issues `#2377 `_ & `#2180 `_.)" -#: ../system/integrations/smime/prerequisites.rst:56 -msgid "" -"In general, the usage of any expired (``Not After``) or not yet valid (``Not " -"Before``) certificate is denied for outgoing emails." +#: ../system/integrations/checkmk/setup-guide.rst:100 +msgid "In the meantime, we encourage you to set up API alerts instead." msgstr "" -"Im Allgemeinen wird die Verwendung eines abgelaufenen (``Not After``) oder " -"noch nicht gültigen (``Not Before``) Zertifikats für ausgehende E-Mails " -"verweigert." +"In der Zwischenzeit empfehlen wir Ihnen, stattdessen API-Benachrichtigungen " +"einzurichten." -#: ../system/integrations/smime/prerequisites.rst:59 -msgid "Example certificate:" -msgstr "Beispiel für ein Zertifikat:" +#: ../system/integrations/clearbit.rst:2 +msgid "Clearbit" +msgstr "Clearbit" -#: ../system/integrations/smime/prerequisites.rst:85 +#: ../system/integrations/clearbit.rst:4 msgid "" -"Please note that Zammad will distrust senders by default. This means that " -"you're always required to provide certificate data, no matter if for signing " -"or encrypting." +"With our Clearbit integration, you can easily enrich the information " +"provided by Zammad. If the customers or agents email address is known to " +"Clearbit, it will share all information it has regarding the user with " +"Zammad. Those information can include the following:" msgstr "" -"Bitte beachten Sie, dass Zammad Absendern standardmäßig misstraut. Das " -"bedeutet, dass Sie immer Zertifikatsdaten angeben müssen, egal ob zum " -"Signieren oder Verschlüsseln." +"Mit unserer Clearbit-Integration können Sie die von Zammad bereitgestellten " +"Informationen ganz einfach erweitern. Wenn die E-Mail-Adresse des Kunden " +"oder Agenten Clearbit bekannt ist, wird es alle Informationen, die es über " +"den Benutzer hat, mit Zammad teilen. Die Informationen können Folgendes " +"umfassen:" -#: ../system/integrations/smime/prerequisites.rst:89 -msgid "This is by design and can't be adjusted." -msgstr "Das ist so gewollt und kann nicht geändert werden." +#: ../system/integrations/clearbit.rst:9 +msgid "Avatar" +msgstr "Avatar" -#: ../system/integrations/smime/troubleshooting.rst:4 -msgid "" -"All of the system's latest S/MIME activity is displayed in the **Recent " -"Logs** section." -msgstr "" -"Alle aktuellen S/MIME-Aktivitäten des Systems werden im Abschnitt " -"**Aktuellste Protokolle** angezeigt." +#: ../system/integrations/clearbit.rst:10 +msgid "Address information" +msgstr "Informationen zur Adresse" -#: ../system/integrations/smime/troubleshooting.rst:11 -msgid "Sample entries of in- and outgoing S/MIME related emails." -msgstr "Beispieleinträge von ein- und ausgehenden S/MIME-bezogenen E-Mails." +#: ../system/integrations/clearbit.rst:11 +msgid "Website information" +msgstr "Informationen zur Website" -#: ../system/integrations/smime/troubleshooting.rst:11 +#: ../system/integrations/clearbit.rst:12 +msgid "A BIO (as Note by default)" +msgstr "Eine Zusammenfassung der Biografie (standardmäßig als Notiz)" + +#: ../system/integrations/clearbit.rst:14 msgid "" -"Logs report the status and details of all mail, both incoming and outgoing, " -"that used signing/verification or encryption/decryption." +"If needed, you can add further custom objects and add mappings to them, so " +"the Clearbit information can be filled within the database. In general you " +"can get any information from Clearbit, as long as you have a mapping to an " +"Zammad object." msgstr "" -"Die Protokolle enthalten den Status und die Details aller eingehenden und " -"ausgehenden E-Mails, die signiert/verifiziert oder ver- und entschlüsselt " -"wurden." +"Bei Bedarf können Sie weitere benutzerdefinierte Objekte hinzufügen und " +"ihnen Mappings zuweisen. Generell können Sie alle Informationen von Clearbit " +"anzeigen lassen , solange Sie eine Zuordnung zu einem Zammad-Objekt-Atribut " +"eingerichtet haben." -#: ../system/integrations/smime/troubleshooting.rst:14 +#: ../system/integrations/clearbit.rst:21 msgid "" -"This log does **not** include email sent by :doc:`triggers ` or the :doc:`scheduler `. For those, check your " -"``production.log``." +"Clearbit does have a mapping of fields like LDAP and Exchange have, but does " +"not \"win\" against Zammad information. This means that if you have e.g. the " +"last name field filled in already and Clearbit has other information on " +"that, it will not be updated." msgstr "" -"Dieses Protokoll enthält **nicht** E-Mails, die von :doc:`triggers ` oder dem :doc:`scheduler ` gesendet wurden. " -"Prüfen Sie dazu bitte Ihr ``production.log``." - -#: ../system/integrations/smime/troubleshooting.rst:20 -msgid "Common Issues" -msgstr "Häufige Probleme" +"Clearbit hat ein Mapping von Feldern wie LDAP und Exchange, aber es " +"überschreibt keine Zammad-Informationen. Das bedeutet, dass wenn Sie z.B. " +"das Feld für den Nachnamen in Zammad bereits ausgefüllt haben, es von " +"Clearbit nicht überschrieben wird, auch wenn dort andere Informationen " +"vorliegen." -#: ../system/integrations/smime/troubleshooting.rst:30 -msgid "I received a signed/encrypted email before I set up S/MIME integration" +#: ../system/integrations/clearbit.rst:26 +msgid "" +"However: If let's say the last name has been set by Clearbit and Zammad " +"notices that the last name on the Clearbit source has changed, Zammad will " +"also update this value." msgstr "" -"Ich habe eine signierte/verschlüsselte E-Mail erhalten, bevor ich die S/MIME-" -"Integration eingerichtet habe" +"Aber: Wenn der Nachname von Clearbit festgelegt wurde und Zammad feststellt, " +"dass sich der Nachname in der Clearbit-Quelle geändert hat, wird Zammad auch " +"diesen Wert aktualisieren." -#: ../system/integrations/smime/troubleshooting.rst:23 +#: ../system/integrations/clearbit.rst:33 msgid "" -"No problem. Once S/MIME has been enabled and the appropriate certificates " -"have been added, agents will be prompted to retry verification/decryption on " -"matching emails." +"The configuration of Clearbit is really easy and done fast! Just login to " +"your Clearbit-Account, go to \"API\" and copy the secret-API-Key." msgstr "" -"Das ist kein Problem. Sobald S/MIME aktiviert ist und die entsprechenden " -"Zertifikate hinzugefügt wurden, werden die Agenten aufgefordert, die " -"Verifizierung/Entschlüsselung bei entsprechenden E-Mails zu wiederholen." +"Die Konfiguration von Clearbit ist wirklich einfach und schnell erledigt! " +"Loggen Sie sich einfach in Ihren Clearbit-Account ein, gehen Sie auf \"API\" " +"und kopieren Sie den geheimen API-Schlüssel." -#: ../system/integrations/smime/troubleshooting.rst:0 -msgid "Screenshot of user prompt to retry decryption" +#: ../system/integrations/clearbit.rst:38 +msgid "" +"Now change to your Zammad instance, go to Integrations (System) -> Clearbit " +"in the admin panel. Paste your API-Key into the API-Key-Field and decide if " +"Zammad should create unknown Organizations automatically, if the user does " +"not have one yet (and Clearbit knows it). The shared option decides if the " +"new organizations Zammad creates with Clearbit should be shared ones." msgstr "" -"Screenshot mit Benutzeraufforderung, die Entschlüsselung zu wiederholen" - -#: ../system/integrations/smime/troubleshooting.rst:38 -msgid "The 🔒 **Encrypt** button is disabled" -msgstr "Die 🔒 **Verschlüsseln**-Schaltfläche ist deaktiviert" - -#: ../system/integrations/smime/troubleshooting.rst:33 -msgid "Have you added the recipient's certificate?" -msgstr "Haben Sie das Zertifikat des Empfängers hinzugefügt?" - -#: ../system/integrations/smime/troubleshooting.rst:34 -msgid "Are you sure the recipient's certificate is valid?" -msgstr "Sind Sie sicher, dass das Zertifikat des Empfängers gültig ist?" - -#: ../system/integrations/smime/troubleshooting.rst:35 -msgid "Have you checked your ``production.log`` for more details?" -msgstr "Haben Sie Ihr ``production.log`` auf weitere Details überprüft?" +"Wechseln Sie nun zu Ihrer Zammad-Instanz und gehen Sie im Admin-Bereich zu " +"Integrationen (System) > Clearbit. Fügen Sie Ihren API-Schlüssel in das API-" +"SchlüsselFeld ein und entscheiden Sie, ob Zammad automatisch unbekannte " +"Organisationen erstellen soll, wenn der Benutzer noch keine hat (und " +"Clearbit diese kennt). Die Option \"Geteilt\" legt fest, ob die neuen " +"Organisationen, die Zammad aus Clearbit erstellt, \"geteilt\" sein sollen." -#: ../system/integrations/smime/troubleshooting.rst:37 +#: ../system/integrations/clearbit.rst:47 msgid "" -"If encryption doesn't work in the composer, it won't work in :doc:`triggers " -"` or the :doc:`scheduler ` either!" +"If you're unsure what option to choose, better stick with \"no\". You can " +"also learn more about :doc:`/manage/organizations/index`." msgstr "" -"Wenn die Verschlüsselung Ticket-Bereich nicht funktioniert, wird sie auch " -"nicht in :doc:`Triggern ` oder in :doc:`Automatisierungen ` funktionieren!" - -#: ../system/integrations/smime/troubleshooting.rst:42 -msgid "The ✅ **Sign** button is disabled" -msgstr "Die ✅ **Signieren**-Schaltfläche ist deaktiviert" +"Wenn Sie unsicher sind, welche Option Sie wählen sollen, bleiben Sie besser " +"bei \"nein\". Sie können mehr dazu unter :doc:`/manage/organizations/index` " +"erfahren." -#: ../system/integrations/smime/troubleshooting.rst:41 +#: ../system/integrations/clearbit.rst:52 msgid "" -"Have you added **both the certificate and private key** for your " -"organization?" +"The Mapping option works similar to the mapping within the Exchange and LDAP " +"sync. You can add further mappings for e.g. custom fields if you need more " +"information that Clearbit can provide." msgstr "" -"Haben Sie **Zertifikate und privaten Schlüssel** für Ihre Organisation " -"hinzugefügt?" +"Die Mapping-Option funktioniert ähnlich wie das Mapping innerhalb des " +"Exchange und LDAP Sync. Sie können weitere Mappings für z.B. " +"benutzerdefinierte Felder hinzufügen, wenn Sie weitere Informationen " +"benötigen, die Clearbit bereitstellen kann." -#: ../system/integrations/smime/troubleshooting.rst:42 +#: ../system/integrations/clearbit.rst:58 msgid "" -"Does the email address on the certificate match the email address of the " -"agent/group composing the email?" +"If you want to add more Clearbit fields and want to learn more about " +"available fields on their API, you can take a look at their `API " +"documentation `_." msgstr "" -"Stimmt die E-Mail-Adresse aus dem Zertifikat mit der E-Mail-Adresse der " -"Person/Gruppe überein, die die E-Mail verfasst?" - -#: ../system/integrations/smime/troubleshooting.rst:45 -msgid "Error: “Fingerprint already taken”" -msgstr "Fehler: \"Fingerabdruck bereits vorhanden\"" +"Wenn Sie weitere Clearbit-Felder hinzufügen möchten und mehr über die " +"verfügbaren Felder in der API erfahren möchten, können Sie einen Blick auf " +"deren `API-Dokumentation `_ werfen." -#: ../system/integrations/smime/troubleshooting.rst:45 -msgid "Are you sure you haven't added this certificate already?" -msgstr "" -"Sind Sie sicher, dass Sie dieses Zertifikat nicht bereits hinzugefügt haben?" +#: ../system/integrations/clearbit.rst:62 +msgid "" +"If you're happy with the above chosen Settings and your mapping, just save " +"the changes and enable Clearbit integration. Zammad will now start polling " +"the Clearbit API as users contact you." +msgstr "" +"Wenn Sie mit den oben gewählten Einstellungen und Ihrem Mapping zufrieden " +"sind, speichern Sie die Änderungen und aktivieren Sie die Clearbit-" +"Integration. Zammad wird nun die Clearbit-API abfragen, wenn Nutzer Sie " +"kontaktieren." -#: ../system/integrations/smime/troubleshooting.rst:48 -msgid "Error: “❌ invalid byte sequence in UTF-8”" -msgstr "Fehler: \"❌ ungültige Bytefolge in UTF-8\"" +#: ../system/integrations/clearbit.rst:68 +msgid "" +"Zammad does not synchronize with Clearbit on a regular basis, but on demand " +"if needed. This saves API calls." +msgstr "" +"Zammad synchronisiert sich nicht regelmäßig mit Clearbit, sondern nur bei " +"Bedarf. Das spart API-Aufrufe." -#: ../system/integrations/smime/troubleshooting.rst:48 -msgid "Please ensure to provide PEM formatted certificate and keys." +#: ../system/integrations/clearbit.rst:73 +msgid "" +"Below the Settings and Mappings, you'll find our Integration log. You can " +"see what requests Zammad sent to Clearbit and also the APIs Response." msgstr "" -"Bitte stellen Sie sicher, dass Sie das Zertifikat und die Schlüssel im PEM-" -"Format bereitstellen." +"Unterhalb der Einstellungen und Zuordnungen finden Sie unser " +"Integrationsprotokoll. Sie können sehen, welche Anfragen Zammad an Clearbit " +"gesendet hat und auch die API-Antwort." -#: ../system/integrations/smime/troubleshooting.rst:49 -msgid "Did you check if the provided file is a valid certificate or key?" +#: ../system/integrations/clearbit.rst:78 +msgid "" +"By the way, you can also view the API log on the Clearbit website - the " +"information seen is basically the same." msgstr "" -"Haben Sie überprüft, ob es sich bei der bereitgestellten Datei um ein " -"gültiges Zertifikat oder einen gültigen Schlüssel handelt?" +"Übrigens können Sie das API-Protokoll auch auf der Clearbit-Website einsehen " +"- die Informationen sind im Grunde die gleichen." -#: ../system/integrations/zabbix.rst:2 -msgid "Zabbix Integration" -msgstr "Zabbix-Integration" +#: ../system/integrations/clearbit.rst:84 +msgid "Example When Adding a User" +msgstr "Beispiel für das Hinzufügen eines Benutzers" -#: ../system/integrations/zabbix.rst:5 +#: ../system/integrations/clearbit.rst:86 msgid "" -"This guide describes how to integrate your Zabbix 5.4 installation with " -"Zammad using the Zabbix webhook feature. This guide will provide " -"instructions on setting up a media type, a user and an action in Zabbix." +"To show you how fast information is added, we added a small Screencast " +"below. This shows the creation of the User Alex from Clearbit. As we already " +"set the last name of Alex to \"X\", Zammad did not update it. What Zammad " +"did was to add further information it received from Clearbit." msgstr "" -"Diese Anleitung beschreibt, wie Sie Ihre Zabbix 5.4-Installation mit Zammad " -"unter Verwendung der Zabbix-Webhook-Funktion integrieren. Sie enthält " -"Anweisungen zum Einrichten eines Medientyps, eines Benutzers und einer " -"Aktion in Zabbix." +"Um Ihnen zu zeigen, wie schnell Informationen hinzugefügt werden, haben wir " +"unten einen kleinen Screencast eingefügt. Dieser zeigt die Erstellung des " +"Benutzers Alex aus Clearbit. Da wir den Nachnamen von Alex bereits auf \"X\" " +"gesetzt haben, hat Zammad ihn nicht aktualisiert. Zammad hat weitere " +"Informationen hinzuzufügt, die es von Clearbit erhalten hatte." -#: ../system/integrations/zabbix.rst:12 -msgid "Zammad with enabled HTTP Token Authentication" -msgstr "Zammad mit aktivierter HTTP-Token-Authentifizierung" +#: ../system/integrations/cti/generic.rst:2 +msgid "CTI (generic)" +msgstr "CTI (allgemein)" -#: ../system/integrations/zabbix.rst:13 -msgid "Zabbix version 5.4 or higher" -msgstr "Zabbix Version 5.4 oder höher" +#: ../system/integrations/cti/includes/introduction.include.rst:1 +msgid "" +"This integration enables Zammad to provide a caller log to your agents. With " +"this your agents can greet your customers by their name and are supported by " +"Zammad with automatically opening a new ticket dialog or the user profile." +msgstr "" +"Diese Integration ermöglicht es Zammad, Ihren Agenten eine Anruferliste zur " +"Verfügung zu stellen. Damit können Ihre Agenten Ihre Kunden mit ihrem Namen " +"begrüßen und werden von Zammad duruch ein automatisches Öffnen eines Ticket-" +"Erstell-Dialogs oder des Benutzerprofils unterstützt." -#: ../system/integrations/zabbix.rst:16 -msgid "Setting up a Zammad" -msgstr "Einrichten von Zammad" +#: ../system/integrations/cti/includes/introduction.include.rst:6 +msgid "" +"Click the toggle next to the heading to activate or deactivate this " +"integration." +msgstr "" +"Klicken Sie auf Schalter neben der Überschrift ``Placetel``, um diese " +"Integration zu aktivieren oder zu deaktivieren." -#: ../system/integrations/zabbix.rst:18 -msgid "Enable **API Token Access** in Settings > System > API." +#: ../system/integrations/cti/includes/introduction.include.rst:9 +msgid "" +"If you want to learn more on how your agents can use this function, please " +"refer the :user-docs:`user documentation `." msgstr "" -"Aktivieren Sie **API Token Zugriff** unter Einstellungen > System > API." +"Wenn Sie mehr darüber erfahren möchten, wie Ihre Agenten diese Funktion " +"nutzen können, lesen Sie bitte die :user-docs:`Benutzerdokumentation `." -#: ../system/integrations/zabbix.rst:20 +#: ../system/integrations/cti/includes/introduction.include.rst:14 msgid "" -"Create a **new user** for a Zabbix alerter with an **email address** and " -"create a personal user token with **ticket.agent** permissions." +"Automatically opening new ticket dialogues or user profiles requires agent " +"to extension mapping - see more below." msgstr "" -"Erstellen Sie einen **neuen Benutzer** für eine Zabbix-Benachrichtigung mit " -"einer **E-Mail-Adresse** und erstellen Sie ein persönliches Benutzertoken " -"mit **ticket.agent**-Berechtigungen." +"Das automatische Öffnen von Ticket-Erstell-Dialogen oder Benutzerprofilen " +"erfordert eine Zuordnung von Agenten in der CTI-Integration - siehe unten." -#: ../system/integrations/zabbix.rst:24 -msgid "Zabbix Webhook Configuration" -msgstr "Zabbix Webhook-Konfiguration" +#: ../system/integrations/cti/includes/introduction.include.rst:20 +msgid "Please note the following limitations to reduce confusion later on:" +msgstr "" +"Bitte beachten Sie die folgenden Einschränkungen, um spätere Unklarheiten zu " +"vermeiden:" -#: ../system/integrations/zabbix.rst:27 -msgid "Create a Global Macro" -msgstr "Ein globales Makro erstellen" +#: ../system/integrations/cti/includes/introduction.include.rst:22 +msgid "CTI integrations provide caller log functions only." +msgstr "Die CTI-Integration bieten nur Anruferprotokoll-Funktionen." -#: ../system/integrations/zabbix.rst:29 +#: ../system/integrations/cti/includes/introduction.include.rst:23 msgid "" -"Before setting up the **Webhook**, you need to setup the global macro " -"**{$ZABBIX.URL}**, which must contain the **URL** to the **Zabbix frontend**." +"This integration does not provide any VoIP functionalities; you can't make " +"phone calls from within Zammad." msgstr "" -"Bevor Sie den **Webhook** einrichten, müssen Sie das globale Makro " -"**{$ZABBIX.URL}** einrichten, das die **URL** zum **Zabbix-Frontend** " -"enthalten muss." +"Diese Integration bietet keine VoIP-Funktionen; Sie können von Zammad aus " +"keine Telefonanrufe tätigen." -#: ../system/integrations/zabbix.rst:33 +#: ../system/integrations/cti/includes/introduction.include.rst:25 msgid "" -"In the **Administration** > **Media types** section, import the `Template`_." +"If your browser supports ``tel``-URLs, you can click on phone numbers for " +"automatic dialing. This requires additional software / configuration on your " +"agent's computers." msgstr "" -"Importieren Sie im Bereich **Administration** > **Media types** das " -"`Template`_." - -#: ../system/integrations/zabbix.rst:38 -msgid "Open the added **Zammad** media type and set:" -msgstr "Öffnen Sie den hinzugefügten Medientyp **Zammad** und stellen Sie ein:" +"Wenn Ihr Browser ``tel``-URLs unterstützt, können Sie auf Telefonnummern " +"klicken, um sie automatisch zu wählen. Dies erfordert zusätzliche Software/" +"Konfiguration auf den Computern Ihrer Mitarbeiter." -#: ../system/integrations/zabbix.rst:40 -msgid "**zammad\\_access\\_token** to the your **Personal User Token**" -msgstr "**zammad\\_access\\_token** zu Ihrem **Personal User Token**" +#: ../system/integrations/cti/generic.rst:9 +#: ../system/integrations/cti/placetel.rst:14 +#: ../system/integrations/cti/sipgate.rst:14 +msgid "Please provide the following requirements:" +msgstr "Folgende Anforderungen müssen erfüllt sein:" -#: ../system/integrations/zabbix.rst:41 +#: ../system/integrations/cti/generic.rst:11 msgid "" -"**zammad\\_url** to the **frontend URL** of your **Zammad** installation" -msgstr "**zammad\\_url** zur **frontend URL** Ihrer **Zammad**-Installation" +"A telephone system that supports webhooks (outbound) (best option are those " +"that allow customizing the calls)." +msgstr "" +"Eine Telefonanlage, die Webhooks (ausgehend) unterstützt (am besten solche, " +"die eine individuelle Anpassung der Anrufe ermöglichen)." -#: ../system/integrations/zabbix.rst:43 -msgid "**zammad\\_customer** to your **Zammad user email**." -msgstr "**zammad\\_customer** zu Ihrer **Zammad-Benutzer-E-Mail**." +#: ../system/integrations/cti/generic.rst:13 +msgid "A unique Call-ID during the call session." +msgstr "Eine eindeutige Call-ID während der Gesprächssitzung." -#: ../system/integrations/zabbix.rst:44 -msgid "" -"**zammad\\_enable\\_tags** to **true** or **false** to enable or disable " -"trigger tags. **Important**: if you enable tag support, each tag is set with " -"a separate request." -msgstr "" -"**zammad\\_enable\\_tags** auf **true** oder **false**, um Trigger-Tags zu " -"aktivieren oder zu deaktivieren. **Wichtig**: Wenn Sie die Tag-Unterstützung " -"aktivieren, wird jedes Tag mit einer separaten Anfrage gesetzt." +#: ../system/integrations/cti/generic.rst:14 +msgid "Call event data (both numbers and direction)." +msgstr "Daten zu Anrufereignissen (sowohl Nummern als auch Richtung)." -#: ../system/integrations/zabbix.rst:48 +#: ../system/integrations/cti/generic.rst:15 +msgid "Your Zammad instance must be reachable for your telephony system." +msgstr "Ihre Zammad-Instanz muss für Ihr Telefonsystem erreichbar sein." + +#: ../system/integrations/cti/generic.rst:17 msgid "" -"If you want to prioritize issues according to **severity** values in Zabbix, " -"you can define mapping parameters:" +"If you want to learn more on what kind of requests are supported by Zammad " +"and what it expects, please consult our :docs:`CTI-API documentation `." msgstr "" -"Wenn Sie Probleme in Zabbix nach **Schweregrad** priorisieren möchten, " -"können Sie Zuordnungsparameter definieren:" +"Wenn Sie mehr darüber erfahren möchten, welche Arten von Anfragen von Zammad " +"unterstützt werden und welche Daten erwartet werden, konsultieren Sie bitte " +"unsere :docs:`CTI-API Dokumentation `." -#: ../system/integrations/zabbix.rst:51 -msgid "**severity\\_**: Zammad priority ID" -msgstr "**severity\\_**: Zammad priority ID" +#: ../system/integrations/cti/generic.rst:22 +#: ../system/integrations/cti/placetel.rst:27 +#: ../system/integrations/cti/sipgate.rst:30 +msgid "Available Settings" +msgstr "Verfügbare Einstellungen" -#: ../system/integrations/zabbix.rst:53 -msgid "Click the **Update** button to save the **Webhook** settings." -msgstr "" -"Klicken Sie auf die Schaltfläche **Aktualisieren**, um die **Webhook-" -"Einstellungen** zu speichern." +#: ../system/integrations/cti/generic.rst:29 +#: ../system/integrations/cti/placetel.rst:41 +#: ../system/integrations/cti/sipgate.rst:40 +msgid "Endpoint Settings" +msgstr "Endpunkt-Einstellungen" -#: ../system/integrations/zabbix.rst:55 +#: ../system/integrations/cti/generic.rst:25 msgid "" -"To receive notifications in **Zammad**, you need to create a **Zabbix user** " -"and add **Media** with the **Zammad** type." +"Zammad will list your generic CTI endpoint here. It contains a unique token " +"so ensure to keep this URL save." msgstr "" -"Um Benachrichtigungen in **Zammad** zu erhalten, müssen Sie einen **Zabbix-" -"Benutzer** anlegen und **Medien** mit dem Typ **Zammad** hinzufügen." +"Zammad listet hier Ihren generischen CTI-Endpunkt auf. Er enthält ein " +"eindeutiges Token. Bitte achten Sie darauf, die URL möglichst geheim zu " +"halten." -#: ../system/integrations/zabbix.rst:58 +#: ../system/integrations/cti/generic.rst:28 msgid "" -"For **Send to**: enter any text, as this value is not used, but is required." +"You'll need this endpoint for your PBX to talk to Zammad, see :docs:`CTI-API " +"documentation `." msgstr "" -"Für **Send to**: Geben Sie einen beliebigen Text ein, da dieser Wert nicht " -"verwendet wird, aber erforderlich ist." +"Sie benötigen diesen Endpunkt für Ihre Telefonanlage, um mit Zammad zu " +"sprechen, siehe :docs:`CTI-API Dokumentation `." -#: ../system/integrations/zabbix.rst:61 +#: ../system/integrations/cti/includes/important-dont-forget-saving.include.rst:3 msgid "" -"For more information, use the `Zabbix documentation `_." +"All following options **do not save automatically**. Always use the Save " +"button on the lower end of the integration page!" msgstr "" -"Weitere Informationen finden Sie in der `Zabbix-Dokumentation `_." +"Alle folgenden Optionen werden **nicht automatisch gespeichert**. Verwenden " +"Sie immer die Schaltfläche \"Speichern\" am unteren Ende der Seite!" -#: ../system/maintenance.rst:2 -msgid "Maintenance" -msgstr "Wartung" +#: ../system/integrations/cti/generic.rst:43 +#: ../system/integrations/cti/placetel.rst:49 +#: ../system/integrations/cti/sipgate.rst:52 +msgid "Call Settings" +msgstr "Anruf-Einstellungen" -#: ../system/maintenance.rst:4 +#: ../system/integrations/cti/generic.rst:39 +#: ../system/integrations/cti/placetel.rst:49 +#: ../system/integrations/cti/sipgate.rst:37 +#: ../system/integrations/cti/sipgate.rst:50 +msgid "Inbound" +msgstr "Eingehend" + +#: ../system/integrations/cti/includes/inbound-calls.include.rst:1 msgid "" -"Zammad comes with a maintenance mode that you can use for e.g. updating the " -"instance or changing settings while restricting availability and functions." +"This option allows you to block specific incoming caller IDs. It allows you " +"to temporarily reject e.g. spam callers without having to contact providers " +"or PBX administrators." msgstr "" -"Zammad verfügt über einen Wartungsmodus, den Sie z.B. zum Aktualisieren der " -"Instanz oder zum Ändern von Einstellungen verwenden können, wobei die " -"Verfügbarkeit und die Funktionen eingeschränkt werden." - -#: ../system/maintenance.rst:13 -msgid "Mode" -msgstr "Modus" +"Mit dieser Option können Sie bestimmte eingehende Anrufer-IDs blockieren. So " +"können Sie z.B. Spam-Anrufer vorübergehend abweisen, ohne dass Sie sich an " +"Ihren Provider oder PBX-Administrator wenden müssen." -#: ../system/maintenance.rst:8 -msgid "The mode setting allows you to enable or disable the maintenance mode." -msgstr "" -"Mit dem Modus-Schalter können Sie den Wartungsmodus aktivieren oder " -"deaktivieren." +#: ../system/integrations/cti/includes/inbound-calls.include.rst:11 +msgid "Caller ID to block" +msgstr "Zu blockierende Caller-ID" -#: ../system/maintenance.rst:10 -msgid "Defaults to *off*." -msgstr "Die Standardeinstellung ist *aus*." +#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 +msgid "Provide caller IDs to block in ``E.164`` format." +msgstr "Geben Sie die zu blockierenden Anrufer-IDs im Format ``E.164`` an." -#: ../system/maintenance.rst:12 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:8 msgid "" -"The maintenance mode will restrict access to administrative roles only. This " -"means agents and customers are logged off." +"Your telephony system has to support this function. Zammad will send a " +"``reject`` response which will cause your telephony system to hang up the " +"call. To callers this usually will feel like the line is busy." msgstr "" -"Im Wartungsmodus ist der Zugriff nur auf administrative Rollen beschränkt. " -"Das bedeutet, dass Agenten und Kunden abgemeldet sind." - -#: ../system/maintenance.rst:23 -msgid "@Login" -msgstr "@Login" +"Ihr Telefonsystem muss diese Funktion unterstützen. Zammad sendet eine " +"``Abweisen``-Antwort, die Ihr Telefonsystem veranlasst, den Anruf " +"aufzulegen. Für den Anrufer sieht das normalerweise so aus, als ob die " +"Leitung besetzt wäre." -#: ../system/maintenance.rst:16 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:14 msgid "" -"This setting allows you to provide a login message within a green banner " -"above the login screen. Click into the green banner in the settings page to " -"adjust your message. To activate the message, activate the *@Login* setting." +"Provide a meaningful note for your fellow administrators to remind yourself " +"why you've chosen to block the number." msgstr "" -"Mit dieser Einstellung können Sie eine Login-Nachricht in einem grünen " -"Banner über dem Login-Bildschirm anzeigen. Klicken Sie in das grüne Banner " -"auf der Einstellungsseite, um Ihre Nachricht anzupassen. Um die Nachricht zu " -"aktivieren, aktivieren Sie den Schalter *@Login*." +"Verfassen Sie eine aussagekräftige Notiz für Ihre Kollegen, warum Sie die " +"Nummer gesperrt haben." -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing the default login message within the\n" -"settings page" -msgstr "Screenshot zeigt die Standard-Anmeldung auf der Einstellungsseite" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:17 +#: ../system/integrations/cti/sipgate.rst:40 +msgid "Outbound" +msgstr "Ausgehend" -#: ../system/maintenance.rst:26 +#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:1 msgid "" -"Send an informative message to **all active sessions**. This comes handy to " -"inform your agents e.g. about mayor outages or to force reloads after " -"configuration changes." +"In many cases you may want to use a different caller ID depending on the " +"destination you're calling. This may apply due to specific connection rates " +"to other countries or because you want your customer to feel you're calling " +"from the same country." msgstr "" -"Senden Sie eine informative Nachricht an **alle angemeldeten Benutzer**. " -"Dies ist nützlich, um Ihre Agenten z.B. über größere Ausfälle zu informieren " -"oder um nach Konfigurationsänderungen einen Reload zu erzwingen." +"In vielen Fällen ist es sinnvoll, je nach Zielland eine andere Anrufer-ID zu " +"verwenden. Dies kann aufgrund spezieller Verbindungstarife in andere Länder " +"der Fall sein oder weil Sie Ihren Kunden das Gefühl geben wollen, dass Sie " +"aus demselben Land anrufen." -#: ../system/maintenance.rst:31 -msgid "This is the messages title (slightly bigger than the normal message)." -msgstr "" -"Dies ist der Titel der Nachricht (etwas größer als die normale Nachricht)." +#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:6 +msgid "This option expects ``E.164`` number formats." +msgstr "Diese Option erwartet ``E.164`` Nummernformate." -#: ../system/maintenance.rst:34 -msgid "The text you want to provide to your logged in sessions." -msgstr "Der Text, den Sie Ihren angemeldeten Benutzern senden wollen." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 +msgid "Destination caller ID" +msgstr "Ziel-Caller-ID" -#: ../system/maintenance.rst:39 -msgid "Reload application" -msgstr "Applikation neu laden" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:5 +msgid "The caller ID or number you're trying to call." +msgstr "Die Anrufer-ID oder die Nummer, die Sie anzurufen versuchen." -#: ../system/maintenance.rst:37 -msgid "" -"Selecting this option will change the message acceptance button from *Close* " -"(with nothing happening) to *Continue session*, which forces the application " -"to reload." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:7 +msgid "You can use wildcards for e.g. country specific outbound numbers like:" msgstr "" -"Wenn Sie diese Option wählen, ändert sich die Schaltfläche der " -"Benachrichtigung von *Schließen* (ohne dass etwas passiert) in *Sitzung " -"fortsetzen*, wodurch ein erneutes Laden der Anwendung erzwungen wird." +"Sie können Platzhalter für z.B. länderspezifische ausgehende Nummern " +"verwenden, wie:" -#: ../system/maintenance.rst:43 -msgid "" -"If you have customers that are logged in to Zammad, they'll also be notified " -"if they're active in that moment." -msgstr "" -"Wenn Sie Kunden haben, die bei Zammad eingeloggt sind, werden diese " -"ebenfalls benachrichtigt, wenn sie in diesem Moment aktiv sind." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:9 +msgid "``49*`` for Germany" +msgstr "``49*`` für Deutschland" -#: ../system/maintenance.rst:48 -msgid "Example without reload application" -msgstr "Beispiel ohne Anwendungs-Aktualisierung" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:10 +msgid "``4930*`` for Berlin / Germany landlines" +msgstr "``4930*`` für Berlin / Deutschland Festnetze" -#: ../system/maintenance.rst:52 -msgid "" -"Message setting within Zammad's admin settings without ticket reload " -"application setting." -msgstr "" -"Nachrichteneinstellung in den Verwaltungseinstellungen von Zammad ohne " -"erzwungene Aktualisierung." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 +msgid "``33*`` for France" +msgstr "``33*`` für Frankreich" -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing the send message settings without ticket\n" -"reload application set" -msgstr "" -"Screenshot mit den Einstellungen für das Senden von Nachrichten ohne " -"Aktualisierung der Anwendung" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:15 +msgid "Set Outbound caller ID" +msgstr "Ausgehende Anrufer-ID einstellen" -#: ../system/maintenance.rst:61 ../system/maintenance.rst:85 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:14 msgid "" -"The modal all other active sessions will see upon pressing *Send to clients*." +"The outbound caller ID to set (the number your customer sees on his display) " +"in ``E.164`` number format." msgstr "" -"Der Dialog, den alle anderen aktiven Sitzungen sehen, wenn Sie auf *An " -"Clients senden* drücken." - -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing modal caused by maintenance's message\n" -"without reload application ticket" -msgstr "Screenshot mit Benachrichtigung ohne Aktualisierung der Anwendung" +"Die ausgehende Anrufer-ID (die Nummer, die Ihr Kunde auf seinem Display " +"sieht) im Format ``E.164``." -#: ../system/maintenance.rst:72 -msgid "Example with reload application" -msgstr "Beispiel mit Anwendungs-Aktualisierung" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 +msgid "Provide a short description for fellow administrators." +msgstr "Geben Sie eine kurze Beschreibung für andere Administratoren." -#: ../system/maintenance.rst:76 +#: ../system/integrations/cti/includes/generic-cti-support-note.includes.rst:3 msgid "" -"Message setting within Zammad's admin settings with ticket reload " -"application setting." +"This option requires your PBX to send a specific request to Zammad *before " +"dialing*. Please consult the :docs:`CTI API ` in case " +"you're not sure." msgstr "" -"Nachrichteneinstellung in den Verwaltungseinstellungen von Zammad mit " -"erzwungener Aktualisierung." +"Diese Option erfordert, dass Ihre Telefonanlage eine spezielle Anfrage *vor " +"dem Wählen* an Zammad sendet. Bitte konsultieren Sie die :docs:`CTI API `, falls Sie sich nicht sicher sind." -#: ../system/maintenance.rst:0 +#: ../system/integrations/cti/generic.rst:52 +#: ../system/integrations/cti/placetel.rst:54 +#: ../system/integrations/cti/sipgate.rst:59 +msgid "Other Settings" +msgstr "Andere Einstellungen" + +#: ../system/integrations/cti/includes/other-settings-intro.include.rst:1 msgid "" -"Screenshot showing the send message settings with ticket\n" -"reload application set" +"Below you can find all available additional settings for this CTI " +"integration. For your overview we're sorting them by appearance and " +"reference their description first." msgstr "" -"Screenshot mit den Einstellungen für das Senden von Nachrichten mit " -"Aktualisierung der Anwendung" +"Nachfolgend finden Sie alle verfügbaren zusätzlichen Einstellungen für die " +"CTI-Integration. Sie sind sortiert nach dem Auftreten in der Admin-" +"Oberfläche in Zammad." -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing modal caused by maintenance's message\n" -"with reload application ticket" -msgstr "Screenshot mit Benachrichtigung mit Aktualisierung der Anwendung" +#: ../system/integrations/cti/includes/default-caller-id.include.rst:2 +#: ../system/integrations/cti/includes/default-caller-id.include.rst:1 +msgid "Default caller ID for outbound calls" +msgstr "Standard-Rufnummer für ausgehende Anrufe" -#: ../system/monitoring.rst:2 -msgid "Monitoring" -msgstr "Monitoring (Überwachung)" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:16 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:15 +msgid "Shown records in caller log" +msgstr "Anzahl der Einträge im Anrufprotokoll" -#: ../system/monitoring.rst:4 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:2 msgid "" -"This function is only available in self hosted instances. If you use Zammad " -"in our cloud, we are monitoring the system on our own and take steps to fix " -"potential problems directly." +"Allows you to set the number of shown caller log entries for all users. You " +"can choose from the following values:" msgstr "" -"Diese Funktion ist nur in selbst gehosteten Instanzen verfügbar. Wenn Sie " -"Zammad in unserer Cloud nutzen, überwachen wir das System selbst und " -"ergreifen Maßnahmen, um mögliche Probleme direkt zu beheben." +"Ermöglicht es Ihnen, die Anzahl der angezeigten Anruf-Protokolleinträge für " +"alle Benutzer festzulegen. Sie können zwischen den folgenden Werten wählen:" -#: ../system/monitoring.rst:11 -msgid "" -"On the monitoring page, you can see the current health state of Zammad under " -"\"*Current Status*\" at the bottom. This can be useful if you want to have a " -"look if everything is up and running. As an example, you could have a look " -"in the monitoring when you assume that some emails aren't processed from " -"Zammad." -msgstr "" -"Auf der Monitoring-Seite können Sie den aktuellen Zustand von Zammad unter " -"\"*Aktueller Status*\" am unteren Rand sehen. Dies kann nützlich sein, wenn " -"Sie nachsehen wollen, ob alles funktioniert. Zum Beispiel können Sie einen " -"Blick ins Monitoring werfen, wenn Sie vermuten, dass einige E-Mails von " -"Zammad nicht verarbeitet werden." - -#: ../system/monitoring.rst:17 -msgid "**Can't receive an email and the monitoring response is \"healthy\"?**" -msgstr "" -"**Können Sie keine E-Mail empfangen, aber das Monitoring meldet \"kein " -"Vorfälle\"?**" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:5 +msgid "60 (default)" +msgstr "60 (Standard)" -#: ../system/monitoring.rst:19 -msgid "" -"Zammad will just inform you about unprocessable emails. This is not the case " -"for oversized emails. You can adjust the maximum email size in :doc:`../" -"channels/email/settings`." -msgstr "" -"Zammad informiert Sie nur über nicht verarbeitbare E-Mails. Das ist hingegen " -"bei übergroßen E-Mails nicht der Fall. Sie können die maximale E-Mail-Größe " -"in :doc:`../channels/email/settings` einstellen." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:6 +msgid "120" +msgstr "120" -#: ../system/monitoring.rst:24 -msgid "Monitoring API" -msgstr "Monitoring API" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:7 +msgid "180" +msgstr "180" -#: ../system/monitoring.rst:26 -msgid "" -"Beside the indication in the monitoring page, you can also use an external " -"monitoring tool to monitor Zammad's health. To request the health of Zammad, " -"you need to provide the API key (token) to the external monitoring tool. You " -"can copy the token from the \"*Current Token*\" field as well as the whole " -"API endpoint of your system (\"*Health Check*\" field), in which the API " -"token is already included." -msgstr "" -"Neben der Anzeige auf der Monitoring-Seite können Sie auch ein externes " -"Monitoring-Tool verwenden, um den Zustand von Zammad zu überwachen. Um den " -"Zustand von Zammad abzufragen, müssen Sie dem externen Monitoring-Tool den " -"API-Schlüssel (Token) zur Verfügung stellen. Sie können den Token sowohl aus " -"dem Feld \"*Aktueller Token*\" als auch aus dem gesamten API-Endpunkt Ihres " -"Systems (Feld \"*Gesundheits-Check*\") kopieren, in dem der API-Token " -"bereits enthalten ist." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:8 +msgid "240" +msgstr "240" -#: ../system/monitoring.rst:37 -msgid "Screenshot showing Current Token and Health Check" -msgstr "Screenshot mit aktuellem Token und Gesundheits-Check" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:9 +msgid "300" +msgstr "300" -#: ../system/monitoring.rst:37 -msgid "Screenshot showing Token and Health Check" -msgstr "Screenshot mit Token und Gesundheits-Check" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:11 +msgid "**🥵 Potential performance issue**" +msgstr "**🥵 Mögliches Performance-Problem**" -#: ../system/monitoring.rst:39 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:13 msgid "" -"In addition to that, you can reset the auto-generated token to make sure " -"that already configured monitoring systems won't work anymore. So, please " -"use this \"*Reset*\" button only if you know what you do!" +"Setting this setting higher than 60 may cause serious performance issues on " +"very busy instances. Keep in mind that this setting causes Zammad to poll " +"and send up to 300 records to *all active agent sessions* in very short time " +"periods." msgstr "" -"Darüber hinaus können Sie das automatisch generierte Token zurücksetzen, um " -"sicherzustellen, dass bereits konfigurierte Monitoring-Systeme nicht mehr " -"funktionieren. Bitte verwenden Sie diese Schaltfläche \"*Zurücksetzen*\" " -"nur, wenn Sie wissen, was Sie tun!" - -#: ../system/monitoring.rst:44 -msgid "Example Output" -msgstr "Beispiel Ausgabe" - -#: ../system/monitoring.rst:0 -msgid "No issues found" -msgstr "keine Vorfälle" - -#: ../system/monitoring.rst:48 ../system/monitoring.rst:60 -msgid "**Indicator in Zammad**:" -msgstr "**Indikator in Zammad**:" - -#: ../system/monitoring.rst:0 -msgid "Screenshot showing monitoring with no issues" -msgstr "Screenshot des Monitoring ohne Probleme" - -#: ../system/monitoring.rst:54 ../system/monitoring.rst:66 -msgid "**API response**::" -msgstr "**API-Antwort**::" - -#: ../system/monitoring.rst:0 -msgid "Issues were found" -msgstr "Es wurden Probleme festgestellt" - -#: ../system/monitoring.rst:0 -msgid "Screenshot showing monitoring with issues" -msgstr "Screenshot des Monitoring mit Problemen" +"Wenn Sie diese Einstellung auf mehr als 60 setzen, kann dies bei sehr stark " +"ausgelasteten Instanzen zu ernsthaften Performance-Problemen führen. " +"Beachten Sie, dass diese Einstellung bewirkt, dass Zammad in sehr kurzen " +"Zeiträumen bis zu 300 Datensätze bei *allen aktiven Agentensitzungen* " +"anfragt und sendet." -#: ../system/objects.rst:2 -msgid "Objects" -msgstr "Objekte" +#: ../system/integrations/cti/generic.rst:73 +msgid "Caller Log Filter" +msgstr "Anrufprotokoll-Filter" -#: ../system/objects.rst:4 +#: ../system/integrations/cti/generic.rst:55 msgid "" -"In Zammad you can add your own fields to tickets, users, organizations and " -"even groups (these are called \"objects\"). This can be useful if you need " -"to add further information to a ticket or any other object in Zammad and the " -"information doesn't fit in any existing field." +"This function allows you to provide call information based on e.g. queues " +"only to agents that really need the information." msgstr "" -"In Zammad können Sie Ihre eigenen Felder zu Tickets, Benutzern, " -"Organisationen und sogar Gruppen hinzufügen (diese werden \"Objekte\" " -"genannt). Dies kann nützlich sein, wenn Sie weitere Informationen zu einem " -"Ticket oder einem anderen Objekt in Zammad hinzufügen müssen und die " -"Informationen in kein vorhandenes Feld passen." +"Mit dieser Funktion können Sie Anrufprotokolle basierend auf Warteschleifen " +"oder Nummern nur den Agenten zur Verfügung stellen, die diese Informationen " +"wirklich benötigen." -#: ../system/objects.rst:11 +#: ../system/integrations/cti/generic.rst:58 msgid "" -"Try to avoid deleting attributes (and disable them instead) as Zammad might " -"run into unexpected conditions if they are referenced somewhere." +"Why? If you have a team for several countries or departments, you don't want " +"to bug your agents from other departments. Leaving these options empty will " +"fallback to showing everything to everyone." msgstr "" -"Versuchen Sie, das Löschen von Attributen zu vermeiden (und deaktivieren Sie " -"sie stattdessen), da Zammad unvorhergesehen reagieren kann, wenn irgendwo " -"auf sie verwiesen wird." +"Warum? Wenn Sie ein Team für mehrere Länder oder Abteilungen haben, möchten " +"Sie nicht, dass Ihre Mitarbeiter aus anderen Abteilungen gestört werden. " +"Wenn Sie diese Optionen leer lassen, wird wieder alles für alle angezeigt." -#: ../system/objects.rst:16 +#: ../system/integrations/cti/generic.rst:64 +msgid "Destination caller ID or Queue" +msgstr "Ziel-Caller-ID oder Queue" + +#: ../system/integrations/cti/generic.rst:63 msgid "" -"Here's an overview of object attributes. On the upper right you can add new " -"attributes. By default, there will be no custom fields - standard attributes " -"will be grayed out, you can't delete or change those. You can edit custom " -"attributes (they are displayed in black font and have a trash bin on the " -"right side) just by clicking on them." +"This depends on your PBX and usually is either a queue ID, phone number or " +"extension." msgstr "" -"Hier finden Sie eine Übersicht über die Objektattribute. Oben rechts können " -"Sie neue Attribute hinzufügen. Standardmäßig gibt es keine " -"benutzerdefinierten Felder - Standardattribute sind ausgegraut, Sie können " -"diese nicht löschen oder ändern. Sie können benutzerdefinierte Attribute " -"bearbeiten (sie werden in schwarzer Schrift angezeigt und haben einen " -"Mülleimer auf der rechten Seite), indem Sie einfach auf sie klicken." +"Dies hängt von Ihrer Telefonanlage ab und ist in der Regel entweder eine " +"Warteschlangen-ID, eine Telefonnummer oder eine Durchwahl." -#: ../system/objects.rst:24 +#: ../system/integrations/cti/generic.rst:69 +msgid "Agents" +msgstr "Agenten" + +#: ../system/integrations/cti/generic.rst:67 msgid "" -"Attributes you add to Zammad, no matter if they have default values or not, " -"will not update existing information. This means a new ticket field " -"technically will be empty unless you populate it." +"Select the agents that are responsible for the group. These agents will then " +"see caller log entries and call notifications fitting to said queue." msgstr "" -"Attribute, die Sie zu Zammad hinzufügen, egal ob sie Standardwerte haben " -"oder nicht, aktualisieren bestehende Informationen (z.B. Tickets) nicht. Das " -"bedeutet, dass ein neues Ticketfeld technisch gesehen leer sein wird, wenn " -"Sie es nicht ausfüllen." +"Wählen Sie die Agenten aus, die für die Gruppe zuständig sind. Diese Agenten " +"sehen dann Anruferprotokolle und Anrufbenachrichtigungen, die zu dieser " +"Warteschleife gehören." -#: ../system/objects.rst:28 +#: ../system/integrations/cti/generic.rst:0 msgid "" -"Especially in ticket scope this also means that newly added attributes will " -"be indicated as \"changed\" to agents that view the ticket. This may " -"interfere with Zammad's tabs behavior." +"Screenshot showing the caller log filter table with pre filled sample data" msgstr "" -"Insbesondere im Ticketbereich bedeutet dies auch, dass neu hinzugefügte " -"Attribute den Agenten, die das Ticket ansehen, als \"geändert\" angezeigt " -"werden. Dies kann das Verhalten von Zammad beeinträchtigen." - -#: ../system/objects.rst:40 -msgid "Ordering Attributes" -msgstr "Anordnung der Attribute" +"Screenshot der Anrufprotokoll-Filtertabelle mit vorausgefüllten Beispieldaten" -#: ../system/objects.rst:42 +#: ../system/integrations/cti/includes/recent-logs.include.rst:6 msgid "" -"Since Zammad introduced :doc:`/system/core-workflows` the need to have a " -"custom positioning for attributes has become more important than ever." +"With recent logs Zammad allows you to view the latest calls for the CTI " +"functionality. This usually comes in handy, when you're looking for errors." msgstr "" -"Seit Zammad :doc:`/system/core-workflows` eingeführt hat, ist die " -"Notwendigkeit einer benutzerdefinierten Positionierung für Attribute " -"wichtiger denn je geworden." +"Mit den \"Aktuellsten Protokollen\" ermöglicht es Zammad Ihnen, die letzten " +"Anrufe für die CTI-Integration zu sehen. Das kann im Fehlerfall hilfreich " +"sein." -#: ../system/objects.rst:45 +#: ../system/integrations/cti/includes/recent-logs.include.rst:0 msgid "" -"To adjust the position of such an attribute, simply click on the attribute " -"entry in question, scroll down and adjust the position number. Please note " -"that you cannot change the positioning of default attributes." +"Screenshot showing several incoming requests within Recent logs section." msgstr "" -"Um die Position eines solchen Attributs anzupassen, klicken Sie einfach auf " -"den betreffenden Attributeintrag, scrollen Sie nach unten und passen Sie die " -"Positionsnummer an. Bitte beachten Sie, dass Sie die Positionierung von " -"Standardattributen nicht ändern können." +"Screenshot mit mehreren eingehenden Anfragen im Abschnitt \"Aktuellste " +"Protokolle\"." -#: ../system/objects.rst:49 +#: ../system/integrations/cti/includes/recent-logs.include.rst:16 +msgid "I'm just here to clear floats up." +msgstr "Ich bin nur ein Hilfskonstrukt." + +#: ../system/integrations/cti/includes/recent-logs.include.rst:20 msgid "" -"In case two attributes have the same position value, Zammad will sort " -"alphabetically by name automatically." +"By clicking on the entry of interest, Zammad will provide more details on " +"the call in question. You'll see the payload it received and also the " +"response that was sent." msgstr "" -"Falls zwei Attribute den gleichen Wert haben, sortiert Zammad automatisch " -"alphabetisch nach Namen." +"Wenn Sie auf den gewünschten Eintrag klicken, zeigt Zammad weitere " +"Einzelheiten zu dem betreffenden Anruf an. Sie sehen dann den empfangenen " +"Payload und die gesendete Antwort." -#: ../system/objects.rst:None +#: ../system/integrations/cti/includes/recent-logs.include.rst:0 msgid "" -"Screenshot showing custom attribute entries ordered in between default ones" +"Screenshot showing detailed information of a specific log entry of recent " +"logs" msgstr "" -"Screenshot mit benutzerdefinierten Attributen, die zwischen den " -"Standardattributen angeordnet sind" +"Screenshot mit detaillierten Informationen zu einem bestimmten " +"Protokolleintrag der Aktuellsten Protokolle" -#: ../system/objects.rst:56 -msgid "Updating Database After Adding or Editing Attributes" +#: ../system/integrations/cti/includes/recent-logs.include.rst:31 +msgid "x" +msgstr "x" + +#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 +#: ../system/integrations/cti/includes/troubleshooting.include.rst:9 +msgid "My Phone page stays blank, signalling does work..." msgstr "" -"Aktualisierung der Datenbank nach dem Hinzufügen oder Bearbeiten von " -"Attributen" +"Meine Telefonliste bleibt leer, die Anruf-Signalisierung funktioniert..." -#: ../system/objects.rst:58 +#: ../system/integrations/cti/includes/troubleshooting.include.rst:5 msgid "" -"When adding or changing attributes, Zammad will not apply the changes " -"instantly, but instead shows you the changed attributes first. If you're " -"ready to go, just click on \"Update database\" to apply the changes to " -"Zammad. If you made a mistake or just want to discard your changes, click " -"\"Discard changes\"." +"If you've made sure that signalling works (check Recent logs) and your " +"Caller Log still stays empty, please ensure that you only configured one CTI " +"integration version. Specifically defining more than one agent mapping on " +"the different integration variants will be the issue." msgstr "" -"Wenn Sie Attribute hinzufügen oder ändern, übernimmt Zammad die Änderungen " -"nicht sofort, sondern zeigt Ihnen zunächst die geänderten Attribute an. Wenn " -"Sie fertig sind, klicken Sie einfach auf \"Datenbank aktualisieren\", um die " -"Änderungen in Zammad zu übernehmen. Wenn Sie einen Fehler gemacht haben oder " -"Ihre Änderungen einfach verwerfen wollen, klicken Sie auf \"Änderungen " -"verwerfen\"." +"Wenn Sie sich in den \"Aktuellsten Protokollen\" vergewissert haben, dass " +"die Anruf-Signalisierung funktioniert und Ihr Anruferprotokoll trotzdem leer " +"bleibt, stellen Sie bitte sicher, dass Sie nur eine CTI-Integration " +"konfiguriert haben. Wenn Sie mehr als eine Agentenzuordnung in verschiedenen " +"Integrationen definieren, ist das wahrscheinlich das Problem." -#: ../system/objects.rst:64 -msgid "" -"After applying the changes with \"Update Database\", a restart of Zammad is " -"**mandatory**. If you don't perform it, you may experience unexpected " -"behavior or even errors. You may want to do this kind of configuration " -"during maintenance windows." +#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 +msgid "Clear the not needed agent mapping and reload your browser page." msgstr "" -"Nach der Übernahme der Änderungen mit \"Datenbank aktualisieren\" ist ein " -"Neustart von Zammad **zwingend erforderlich**. Wenn Sie dies nicht tun, kann " -"es zu unerwartetem Verhalten oder sogar zu Fehlern kommen. Sie sollten diese " -"Art der Konfiguration während eines Wartungsfensters durchführen." +"Löschen Sie die Zuordnung nicht benötigter Agenten und laden Sie Ihre " +"Browserseite neu." -#: ../system/objects.rst:72 +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:1 msgid "" -"Changes on objects require you to update the database to apply these changes." +"By mapping your agents extension to their existing Zammad users, Zammad can " +"provide a new ticket dialog or open the user profile for the agent that " +"picks up the call." msgstr "" -"Bei Änderungen an Objekten müssen Sie die Datenbank aktualisieren, um diese " -"Änderungen zu übernehmen." - -#: ../system/objects.rst:75 -msgid "**🤓 Service restarts can be automated**" -msgstr "**🤓 Neustarts können automatisiert werden**" - -#: ../system/objects.rst:0 -msgid "Hosted environments automatically restart for you." -msgstr "Gehostete Instanzen starten automatisch neu." +"Indem Sie die Durchwahlen Ihrer Agenten den bestehenden Zammad-Benutzern " +"zuordnen, kann Zammad einen neuen Ticket-Dialog bereitstellen oder das " +"Benutzerprofil des Anrufers für den Agenten öffnen, der den Anruf " +"entgegennimmt." -#: ../system/objects.rst:0 +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:5 msgid "" -"If you're using a self-hosted installation you can use :docs:`environment " -"variables `" +"This speeds up ticket aiding, no matter if it's for existing tickets or new " +"ones!" msgstr "" -"Wenn Sie eine selbst gehostete Installation verwenden, können Sie :docs:" -"`Umgebungsvariablen ` verwenden" - -#: ../system/objects.rst:82 -msgid "System Attributes" -msgstr "System-Attribute" +"Das beschleunigt die Bearbeitung von Tickets, egal ob es sich um bestehende " +"oder neue Tickets handelt!" -#: ../system/objects.rst:84 +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:8 msgid "" -"Zammad comes with pre-configured attributes. Some of them can't be edited " -"via UI (or at all). This is required for proper operation of Zammad and not " -"a bug." +"To see it work from the agent's perspective, have a look on :user-docs:`user " +"documentation `." msgstr "" -"Zammad wird mit vorkonfigurierten Attributen geliefert. Einige von ihnen " -"können nicht über die Benutzeroberfläche (oder grundsätzlich nicht) " -"bearbeitet werden. Dies ist für den ordnungsgemäßen Betrieb von Zammad " -"erforderlich und kein Fehler." +"Um zu sehen, wie es aus der Sicht von Agenten funktioniert, sehen Sie sich :" +"user-docs:`Benutzerdokumentation ` an." -#: ../system/objects.rst:90 -msgid "Ticket State" -msgstr "Ticket-Status" +#: ../system/integrations/cti/placetel.rst:2 +msgid "Placetel CTI" +msgstr "Placetel CTI" -#: ../system/objects.rst:92 +#: ../system/integrations/cti/placetel.rst:16 +msgid "You need an administrative Placetel account for your organization." +msgstr "Sie benötigen ein Placetel-Administrator-Konto für Ihre Organisation." + +#: ../system/integrations/cti/placetel.rst:17 +#: ../system/integrations/cti/sipgate.rst:20 msgid "" -"If the pre-configured states aren't enough for you or you want to change " -"them, you can do so by clicking on the cogwheel icon in the state row in the " -"ticket tab. But you should be careful when changing pre-configured states. " -"This can lead to unwanted behavior in some cases." +"Your Zammad instance must be allowed to communicate to external services." msgstr "" -"Wenn Ihnen die vorkonfigurierten Status nicht ausreichen oder Sie sie ändern " -"möchten, können Sie dies tun, indem Sie auf das Zahnradsymbol in der " -"Statuszeile im Tab Ticket klicken. Sie sollten jedoch vorsichtig sein, wenn " -"Sie vorkonfigurierte Status ändern. Dies kann in manchen Fällen zu " -"unerwünschtem Verhalten führen." +"Ihre Zammad-Instanz muss mit externen Diensten zu kommunizieren können." -#: ../system/objects.rst:None -msgid "Screenshot showing highlighted ticket state attribute" -msgstr "Screenshot mit hervorgehobenem Ticketstatus-Attribut" +#: ../system/integrations/cti/placetel.rst:18 +msgid "Placetel must be able to reach your Zammad instance." +msgstr "Placetel muss in der Lage sein, Ihre Zammad-Instanz zu erreichen." -#: ../system/objects.rst:122 -msgid "Handling of states" -msgstr "Verwalten von Status" +#: ../system/integrations/cti/placetel.rst:22 +msgid ":doc:`provider-configurations/placetel`" +msgstr ":doc:`provider-configurations/placetel`" -#: ../system/objects.rst:102 +#: ../system/integrations/cti/placetel.rst:21 msgid "" -"In the state configuration screen, you can add new states, disable states or " -"change states." +"Learn how to configure Placetel to enable Zammad and Placetel to communicate " +"with each other." msgstr "" -"Im Statuskonfigurationsbildschirm können Sie neue Status hinzufügen, " -"deaktivieren oder ändern." - -#: ../system/objects.rst:0 -msgid "Screenshot showing table of default ticket states" -msgstr "Screenshot mit Tabelle der Standard-Ticketstatus" +"Erfahren Sie, wie Sie Placetel konfigurieren, damit Zammad und Placetel " +"miteinander kommunizieren können." -#: ../system/objects.rst:110 +#: ../system/integrations/cti/placetel.rst:32 msgid "" -"To add a new state, click on the \"New Ticket State\" button in the top " -"right corner. To change an existing state, simply click on the affected " -"state. This opens an edit dialog." +"The here listed endpoint settings are relevant for the :doc:`integration " +"configuration with Placetel `." msgstr "" -"Um einen neuen Status hinzuzufügen, klicken Sie auf die Schaltfläche \"Neuer " -"Ticketstatus\" in der oberen rechten Ecke. Um einen bestehenden Status zu " -"ändern, klicken Sie einfach auf den betreffenden Status. Daraufhin öffnet " -"sich ein Bearbeitungsdialog." +"Die hier aufgeführten Endpunkt-Einstellungen sind relevant für die :doc:" +"`Konfiguration der Placetel-Integration `." -#: ../system/objects.rst:114 -msgid "" -"You can also clone a state or set them to \"Default for new tickets\" or " -"\"Default for follow-ups\" by clicking on the ⁝ action button and select the " -"desired function." -msgstr "" -"Sie können auch einen Status klonen oder ihn als \"Standard bei neuen " -"Tickets\" oder \"Standard bei Rückfragen\" setzen, indem Sie auf die " -"Schaltfläche ⁝ Aktion klicken und die gewünschte Funktion auswählen." +#: ../system/integrations/cti/placetel.rst:37 +#: ../system/integrations/i-doit.rst:53 +msgid "Endpoint" +msgstr "Endpunkt" -#: ../system/objects.rst:118 +#: ../system/integrations/cti/placetel.rst:36 msgid "" -"*Default for new tickets* means that this state is used for every newly " -"created ticket." +"This endpoint will be required for the Zammad integration within the " +"Placetel web interface." msgstr "" -"*Standard bei neuen Tickets* bedeutet, dass dieser Status für jedes neu " -"erstellte Ticket verwendet wird." +"Dieser Endpunkt wird für die Zammad-Integration innerhalb der Placetel-" +"Weboberfläche benötigt." -#: ../system/objects.rst:121 +#: ../system/integrations/cti/placetel.rst:41 +msgid "API Token" +msgstr "API-Token" + +#: ../system/integrations/cti/placetel.rst:40 msgid "" -"*Default for follow-ups* means that this state is used if the ticket is re-" -"opened after it was closed." +"You'll receive this token within the ``Web API`` menu. Make sure to copy " +"this value, it's only shown once!" msgstr "" -"*Standard bei Rückfragen* bedeutet, dass dieser Status verwendet wird, wenn " -"das Ticket nach seiner Schließung erneut geöffnet wird." +"Dieses Token erhalten Sie im Menü ``Web API``. Achten Sie darauf, diesen " +"Wert zu kopieren, er wird nur einmal angezeigt!" -#: ../system/objects.rst:171 -msgid "Ticket state in detail" -msgstr "Ticketstatus im Detail" +#: ../system/integrations/cti/placetel.rst:71 +#: ../system/integrations/cti/sipgate.rst:77 +msgid "Phone Extension to Agent Mapping" +msgstr "Zuordnung von Telefonanschlüssen zu Agenten" -#: ../system/objects.rst:125 -msgid "" -"Below you can find a description for each field and option. Please head over " -"to the :ref:`example ` to see the edit dialog." +#: ../system/integrations/cti/placetel.rst:0 +msgid "Screenshot showing sample user mappings in between Placetel and Zammad" msgstr "" -"Nachfolgend finden Sie eine Beschreibung für jedes Feld und jede Option. " -"Schauen Sie sich das :ref:`Beispiel ` an, um den " -"Bearbeitungsdialog zu sehen." +"Screenshot mit Beispielen für Benutzerzuordnungen zwischen Placetel und " +"Zammad" -#: ../system/objects.rst:129 +#: ../system/integrations/cti/placetel.rst:64 msgid "" -"This is the name of the state and what you and your agents are seeing when " -"choosing a state somewhere (e.g. in tickets, trigger configuration)." +"You can find your agents Placetel username combination required within ⚙️ PBX " +"→ VoIP destinations. Within the \"Advanced settings\" section you're looking " +"for \"SIP user name\" and \"SIP server\"." msgstr "" -"Dies ist der Name des Status und das, was Sie und Ihre Agenten sehen, wenn " -"sie irgendwo einen Status auswählen (z. B. in Tickets, Triggerkonfiguration)." +"Sie finden die für Ihre Agenten erforderliche Placetel-Benutzernamen-" +"Kombination unter ⚙️ PBX → VoIP destinations. Im Abschnitt \"Advanced " +"settings\" finden Sie \"SIP user name\" und \"SIP server\"." -#: ../system/objects.rst:137 +#: ../system/integrations/cti/placetel.rst:68 +msgid "Combine these two like so: ``@``." +msgstr "Kombinieren Sie beides wie folgt: ``@``." + +#: ../system/integrations/cti/placetel.rst:0 +msgid "Sample VoIP credentials for a Placetel user" +msgstr "Beispiel für VoIP-Zugangsdaten für einen Placetel-Benutzer" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:2 +msgid "Setup Placetel connection for Zammad" +msgstr "Placetel-Verbindung für Zammad einrichten" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:6 msgid "" -"There are different state types you can choose from. By default, Zammad " -"comes with one state per state type." +"This configuration step requires a *full* administrative Placetel account. " +"You may receive forbidden error messages with Placetel in case your " +"permissions are not high enough." msgstr "" -"Es gibt verschiedene Statustypen, aus denen Sie wählen können. Standardmäßig " -"wird Zammad mit einem Status pro Statustyp ausgeliefert." +"Dieser Konfigurationsschritt erfordert ein *vollständiges* administratives " +"Placetel-Konto. Sie können Fehlermeldungen erhalten, wenn Ihre " +"Berechtigungen dafür nicht ausreichen." -#: ../system/objects.rst:140 +#: ../system/integrations/cti/provider-configurations/placetel.rst:10 msgid "" -"**new**: for states for tickets that are new and it hasn't been worked on " -"them" +"The following actions can be configured via the `Placetel web interface " +"`_." msgstr "" -"**Neu**: für Tickets, die neu sind und an denen noch nicht gearbeitet wurde" +"Die folgenden Aktionen können über `Placetels Webschinterface `_ konfiguriert werden." -#: ../system/objects.rst:142 +#: ../system/integrations/cti/provider-configurations/placetel.rst:29 +msgid "Step 1: Activate Zammad integration" +msgstr "Schritt 1: Aktivieren der Zammad-Integration" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:14 msgid "" -"**open**: for states for tickets that are in progress and agents are working " -"on them" +"Within Integrations, scroll down to Partner integrations and select Zammad." msgstr "" -"**offen**: für Tickets, die in Bearbeitung sind und an denen Agenten arbeiten" +"Scrollen Sie innerhalb von Integrationen nach unten zu Partnerintegrationen " +"und wählen Sie Zammad." -#: ../system/objects.rst:144 -msgid "**merged**: for states for tickets that are merged with other tickets" +#: ../system/integrations/cti/provider-configurations/placetel.rst:17 +msgid "" +"You can alternatively filter by \"Ticket Systems\" to reduce the number of " +"entries on the page. You'll still want to look for Partner integrations. 🤓" msgstr "" -"**zusammengefasst**: für Tickets, die mit anderen Tickets zusammengefasst " -"werden" +"Sie können alternativ nach \"Ticket-Systemen\" filtern, um die Anzahl der " +"Einträge auf der Seite zu reduzieren. 🤓" -#: ../system/objects.rst:145 +#: ../system/integrations/cti/provider-configurations/placetel.rst:21 msgid "" -"**pending reminder**: for states for tickets that are in progress and you " -"want to set a reminder. (default example: *pending reminder*)" +"Within the Zammad integration now press \"Activate\". A new tab ``API`` " +"becomes available - open this tab." msgstr "" -"**warten auf Erinnerung**: für Tickets, die in Bearbeitung sind und zu denen " -"Sie eine Erinnerung bekommen möchten. (Standardbeispiel: *Warten auf " -"Erinnerung*)" +"Innerhalb der Zammad-Integration klicken Sie nun auf \"Aktivieren\". Ein " +"neuer Tab ``API`` wird verfügbar - öffnen Sie diesen Tab." -#: ../system/objects.rst:147 +#: ../system/integrations/cti/provider-configurations/placetel.rst:24 msgid "" -"**pending action**: for states for tickets that are waiting for a specified " -"time and then change their state (default example: *pending close*)" +"Now tick \"Enable Call Control / Notify API\" and paste the Placetel " +"endpoint from your Zammad instance into the field \"URL of your API " +"endpoint\". Save to apply the settings" msgstr "" -"**Anstehende Aktion**: für Tickets, die für eine bestimmte Zeit warten und " -"dann ihren Zustand ändern (Standardbeispiel: *Warten auf Schließung*)" +"Setzen Sie nun ein Häkchen bei \"Enable Call Control / Notify API\" und " +"fügen Sie den Placetel-Endpunkt aus Ihrer Zammad-Instanz in das Feld \"URL " +"of your API endpoint\" ein. Speichern, um die Einstellungen zu übernehmen" -#: ../system/objects.rst:150 +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "Screencast showing how to activate the Zammad integration" +msgstr "Screencast, der zeigt, wie die Zammad-Integration aktiviert wird" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:51 +msgid "Step 2: Generate API Token for Placetel" +msgstr "Schritt 2: API-Token für Placetel generieren" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:32 msgid "" -"**closed**: for states for tickets that are finished and do not need to be " -"processed further" +"Go back to the integrations page and scroll down to \"Web API\". Generate a " +"new API token by using the \"Create a new API token\" button." msgstr "" -"**geschlossen**: für Tickets, die abgeschlossen sind und nicht weiter " -"bearbeitet werden müssen" +"Gehen Sie zurück zur Seite \"Integrationen\" und scrollen Sie nach unten zu " +"\"Web API\". Erzeugen Sie ein neues API-Token, indem Sie die Schaltfläche " +"\"Neues API-Token erstellen\" verwenden." -#: ../system/objects.rst:153 +#: ../system/integrations/cti/provider-configurations/placetel.rst:37 msgid "" -"⚠️ Choosing the correct state type is important! If you are in doubt, have a " -"look on the default states and their types!" +"If you already generated a token either use your existing token or reset it " +"by using above mentioned button. Placetel will ask you to conform this reset." msgstr "" -"⚠️ Die Wahl des richtigen Statustyps ist wichtig! Im Zweifelsfall sollten Sie " -"einen Blick auf die Standardstatus und ihre Typen werfen!" - -#: ../system/objects.rst:158 -msgid "Ignore escalation" -msgstr "Eskalation ignorieren" +"Wenn Sie bereits einen Token generiert haben, verwenden Sie entweder Ihren " +"bestehenden Token oder setzen Sie ihn mit der oben genannten Schaltfläche " +"zurück. Placetel wird Sie auffordern, diese Rücksetzung zu bestätigen." -#: ../system/objects.rst:157 +#: ../system/integrations/cti/provider-configurations/placetel.rst:41 msgid "" -"Here you can define whether tickets of this state will count to escalation " -"time or not." +"Please keep in mind that existing API scripts may no longer work due to " +"token resets!" msgstr "" -"Hier können Sie festlegen, ob Tickets dieses Status auf die Eskalationszeit " -"angerechnet werden sollen oder nicht." +"Bitte beachten Sie, dass bestehende API-Skripte aufgrund der Neu-Generierung " +"des Tokens möglicherweise nicht mehr funktionieren!" -#: ../system/objects.rst:161 +#: ../system/integrations/cti/provider-configurations/placetel.rst:44 msgid "" -"You can create a note for the state to inform other admins about the state. " -"This has no effect on tickets." +"Copy the provided API token and insert it into the \"API Token\" field " +"within Zammad's Placetel integration." msgstr "" -"Sie können eine Notiz für den Status erstellen, um andere Administratoren " -"über den Status zu informieren. Dies hat keine Auswirkungen auf Tickets." +"Kopieren Sie das bereitgestellte API-Token und fügen Sie es in das Feld " +"\"API Token\" in der Placetel-Integration von Zammad ein." -#: ../system/objects.rst:165 -msgid "Set the state to *active* or *inactive*." -msgstr "Setzen Sie den Status auf *aktiv* oder *inaktiv*." +#: ../system/integrations/cti/provider-configurations/placetel.rst:47 +msgid "" +"Apply your changes by using the \"Save\" button on the bottom of the " +"Placetel integration page and activate the Placetel integration." +msgstr "" +"Übernehmen Sie Ihre Änderungen über die Schaltfläche \"Speichern\" am " +"unteren Rand der Placetel-Integrationsseite und aktivieren Sie die Placetel-" +"Integration." -#: ../system/objects.rst:167 +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 msgid "" -"it is technically possible to set all states to inactive. To keep Zammad " -"working in such a case, the inactive flag of one of the states is ignored." +"Screencast showing how to retrieve an API token from Placetel for Zammad" msgstr "" -"Es ist technisch möglich, alle Status auf \"inaktiv\" zu setzen. Damit " -"Zammad auch in einem solchen Fall funktioniert, wird das Inaktiv-setzen " -"eines der Status ignoriert." +"Screencast, der zeigt, wie man ein API-Token von Placetel für Zammad abruft" -#: ../system/objects.rst:194 -msgid "Ticket state example" -msgstr "Beispiel für einen Ticketstatus" +#: ../system/integrations/cti/provider-configurations/placetel.rst:73 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:77 +msgid "Step 3: Restrict the numbers to notify on" +msgstr "Schritt 3: Beschränken Sie die zu benachrichtigenden Nummern" -#: ../system/objects.rst:174 +#: ../system/integrations/cti/provider-configurations/placetel.rst:54 msgid "" -"Let's assume we want to create a new state which indicates that the ticket " -"has to wait for a response of a third party (e.g. service contractor or " -"manufacturer) and we want to to be able to set a reminder." +"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " +"the the Integrations page of the Placetel web interface, go to \"Notify " +"API\"." msgstr "" -"Nehmen wir an, wir möchten einen neuen Status erstellen, der anzeigt, dass " -"das Ticket auf eine Antwort eines Dritten (z.B. eines Dienstleisters oder " -"Herstellers) warten muss, und wir möchten eine Erinnerung setzen können." +"Haben Sie viele Nummern, die nicht für die Benachrichtigung in Zammad " +"verwendet werden sollen? Gehen Sie auf der Integrations-Seite der Placetel-" +"Weboberfläche auf \"Notify API\"." -#: ../system/objects.rst:178 +#: ../system/integrations/cti/provider-configurations/placetel.rst:58 msgid "" -"First we give the new state a proper name. In this example we call it " -"\"waiting for manufacturer\"." +"Lower on the page Placetel allows you to restrict the numbers to notify on. " +"You'll find this within the \"External routing API\" part." msgstr "" -"Zunächst geben wir dem neuen Zustand einen Namen. In diesem Beispiel nennen " -"wir ihn \"Warten auf den Hersteller\"." +"Weiter unten auf der Seite ermöglicht Placetel die Einschränkung der zu " +"benachrichtigenden Nummern. Sie finden dies im Abschnitt \"External routing " +"API\"." -#: ../system/objects.rst:181 +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 msgid "" -"As state type we choose \"pending reminder\". This indicates that the ticket " -"is still open and we can set a reminder. This reminder can be useful if our " -"manufacturer sometimes isn't responding or we want to remind him to give us " -"an answer." +"Screenshot showing a sample selection of phone numbers to use for the " +"Placetels notify API" msgstr "" -"Als Statustyp wählen wir \"warten auf Erinnerung\". Dies zeigt an, dass das " -"Ticket noch offen ist und wir eine Erinnerung einstellen können. Diese " -"Erinnerung kann nützlich sein, wenn unser Hersteller manchmal nicht " -"antwortet oder wir ihn daran erinnern wollen, uns eine Antwort zu geben." +"Screenshot mit einer Beispielauswahl von Telefonnummern für die Placetel " +"Notify API" -#: ../system/objects.rst:186 +#: ../system/integrations/cti/provider-configurations/placetel.rst:66 msgid "" -"We choose \"no\" for \"ignore escalation\" because we want to escalate the " -"tickets even if we are waiting on the manufacturer's feedback." +"This menu point also provides a API request log from Placetel view. Just " +"open \"Recent responses of your API endpoint\" to learn more." msgstr "" -"Wir wählen \"nein\" für \"Eskalation ignorieren\", weil wir die Tickets auch " -"dann eskalieren wollen, wenn wir auf die Rückmeldung des Herstellers warten." +"Dieser Menüpunkt bietet auch ein API-Anfrageprotokoll aus Placetel-Sicht. " +"Öffnen Sie einfach \"Recent responses of your API endpoint\", um mehr zu " +"erfahren." -#: ../system/objects.rst:189 -msgid "The **result** in the creation dialog will look like this:" -msgstr "Das **Ergebnis** im Erstellungsdialog sieht dann so aus:" +#: ../system/integrations/cti/provider-configurations/placetel.rst:69 +msgid "" +"If you want to see Zammad's perspective, use the \"Recent Logs\" part from " +"within the Placetel integration page." +msgstr "" +"Wenn Sie Zammads Perspektive sehen möchten, verwenden Sie den Bereich " +"\"Aktuellste Protokolle\" auf der Placetel-Integrationsseite in Zammad." -#: ../system/objects.rst:0 -msgid "Screenshot showing ticket state creation dialog with example" -msgstr "Screenshot zeigt Dialog zur Erstellung eines Ticketstatus mit Beispiel" +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "Screenshot showing sample log entries for Placetels API calls to Zammad" +msgstr "" +"Screenshot mit Beispielprotokolleinträgen für Placetels API-Anfragen an " +"Zammad" -#: ../system/objects.rst:197 ../system/objects.rst:199 -msgid "Ticket Priority" -msgstr "Ticket-Priorität" +#: ../system/integrations/cti/provider-configurations/placetel.rst:77 +msgid "Step 4 (optional): Further configurations for Placetel" +msgstr "Schritt 4 (optional): Weitere Konfigurationen für Placetel" -#: ../system/objects.rst:199 ../system/objects.rst:201 +#: ../system/integrations/cti/provider-configurations/placetel.rst:76 msgid "" -"If the pre-configured priorities aren't enough for you or you want to change " -"them, you can do so by clicking on the cogwheel icon in the priority row in " -"the ticket tab:" +"If needed, you can now configure Zammad's Placetel integration in more " +"detail. You can learn more about your options here: :ref:`Placetel " +"integration settings `." msgstr "" -"Wenn Ihnen die vorkonfigurierten Prioritäten nicht ausreichen oder Sie sie " -"ändern möchten, können Sie dies tun, indem Sie auf das Zahnradsymbol in der " -"Prioritätszeile in der Registerkarte Ticket klicken:" +"Bei Bedarf können Sie nun die Placetel-Integration von Zammad detaillierter " +"konfigurieren. Erfahren Sie hier mehr über Ihre Optionen :ref:`Placetel-" +"Integrationseinstellungen `." -#: ../system/objects.rst:None -msgid "Screenshot showing highlighted ticket priority attribute" -msgstr "Screenshot mit hervorgehobenem Ticketprioritätsattribut" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:2 +msgid "Setup Sipgate connection for Zammad" +msgstr "Sipgate-Verbindung für Zammad einrichten" -#: ../system/objects.rst:224 ../system/objects.rst:226 -msgid "Handling of priorities" -msgstr "Verwalten von Prioritäten" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "" +"Sipgate has no english web interface which is why this documentation page is " +"mixing up languages badly." +msgstr " " -#: ../system/objects.rst:208 ../system/objects.rst:210 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"In the priority configuration screen, you can add new priorities, disable " -"priorities or change priorities." +"Please also note that the availability of API addons highly depends on your " +"package trier. Usage of sipgate.io packages *is not free*, please check " +"their `pricing page `_ before!" msgstr "" -"In der Ansicht für die Prioritätskonfiguration können Sie neue Prioritäten " -"hinzufügen, deaktivieren oder ändern." +"Bitte beachten Sie auch, dass die Verfügbarkeit von API-Addons stark von " +"Ihrem Paket abhängt. Die Nutzung von sipgate.io-Paketen ist *nicht " +"kostenlos*, bitte prüfen Sie vorher die `Preisübersicht `_ !" -#: ../system/objects.rst:0 -msgid "Screenshot showing table of default ticket priorities" -msgstr "Screenshot mit Tabelle der Standard-Ticketprioritäten" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:35 +msgid "Step 1: Book sipgate.io package" +msgstr "Schritt 1: Paket sipgate.io buchen" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:13 +msgid "Skip to step 2 if you already have the package booked!" +msgstr "Gehen Sie zu Schritt 2, wenn Sie das Paket bereits gebucht haben!" -#: ../system/objects.rst:216 ../system/objects.rst:218 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:15 msgid "" -"To add a new priority, click on the \"New Priority\" button in the top right " -"corner. To change an existing priority, simply click on the affected " -"priority. This opens an edit dialog." +"Login to an administrative Sipgate account and navigate to " +"``Accountverwaltung``. You'll see several different options depending on " +"your booked packages. Select ``Verträge & Produkte`` to continue." msgstr "" -"Um eine neue Priorität hinzuzufügen, klicken Sie auf die Schaltfläche \"Neue " -"Priorität\" in der oberen rechten Ecke. Um eine bestehende Priorität zu " -"ändern, klicken Sie einfach auf die betreffende Priorität. Daraufhin öffnet " -"sich ein Bearbeitungsdialog." +"Loggen Sie sich in einen administrativen Sipgate-Account ein und navigieren " +"Sie zu ``Accountverwaltung``. Abhängig von Ihren gebuchten Paketen sehen Sie " +"verschiedene Optionen. Wählen Sie ``Verträge & Produkte`` um fortzufahren." -#: ../system/objects.rst:220 ../system/objects.rst:222 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:19 msgid "" -"You can also clone a priority or set them to \"Default for new tickets\" by " -"clicking on the ⁝ action button and select the desired function." -msgstr "" -"Sie können auch eine Priorität klonen oder sie als \"Standard bei neuen " -"Tickets\" setzen, indem Sie auf die Schaltfläche ⁝ Aktion klicken und die " -"gewünschte Funktion auswählen." - -#: ../system/objects.rst:223 ../system/objects.rst:225 -msgid "" -"*Default for new tickets* means that this priority is used for every newly " -"created ticket." +"Scroll down to the section ``Zusätzliche Produkte buchen`` and look for " +"``sipgate.io`` - select this product by using the ``Produkte anzeigen``-" +"Button." msgstr "" -"*Standard bei neuen Tickets* bedeutet, dass diese Priorität für jedes neu " -"erstellte Ticket verwendet wird." - -#: ../system/objects.rst:246 ../system/objects.rst:248 -msgid "Priorities in detail" -msgstr "Prioritäten im Detail" +"Scrollen Sie nach unten in den Bereich ``Zusätzliche Produkte buchen`` und " +"suchen Sie nach ``sipgate.io`` - wählen Sie dieses Produkt über den " +"``Produkte anzeigen``-Button aus." -#: ../system/objects.rst:227 ../system/objects.rst:229 -msgid "Below you can find a description for each field and option." +#: ../system/integrations/cti/provider-configurations/sipgate.rst:23 +msgid "" +"On the next page select either one of the ``sipgate.io`` packages or ``Push-" +"API Package Free``. Follow the dialogue by booking the addon. You'll be " +"returned to your contract overview and now should see the selected addon in " +"your list." msgstr "" -"Nachfolgend finden Sie eine Beschreibung für jedes Feld und jede Option." +"Auf der nächsten Seite wählen Sie entweder eines der ``sipgate.io`-Pakete " +"oder ``Push-API Package Free``. Folgen Sie dem Dialog, um das Addon zu " +"buchen. Sie gelangen zurück zu Ihrer Vertragsübersicht und sollten nun das " +"ausgewählte Addon in Ihrer Liste sehen." -#: ../system/objects.rst:230 ../system/objects.rst:232 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:30 msgid "" -"This is the name of the priority and what you and your agents are seeing " -"when choosing a priority somewhere (e.g. in tickets, trigger configuration)." +"The availability for ``sipgate.io`` packages and their levels highly depends " +"on the overall account type and product you've booked with Sipgate." msgstr "" -"Dies ist der Name der Priorität und das, was Sie und Ihre Agenten sehen, " -"wenn Sie irgendwo eine Priorität auswählen (z.B. in Tickets, Trigger-" -"Konfiguration)." - -#: ../system/objects.rst:240 ../system/objects.rst:242 -msgid "Highlight color" -msgstr "Highlight-Farbe" +"Die Verfügbarkeit von ``sipgate.io``-Paketen und deren Levels hängt von der " +"Art des Accounts und dem Produkt ab, das Sie bei Sipgate gebucht haben." -#: ../system/objects.rst:235 ../system/objects.rst:237 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"Switch between *Low priority* (light blue), *High priority* (red) and - " -"(default). This affects the displayed color for ticket titles in overviews." +"Screencast showing the process on how to book the required sipgate.io addon" msgstr "" -"Umschalten zwischen *Niedrige Priorität* (hellblau), *Hohe Priorität* (rot) " -"und - (Standard). Dies wirkt sich auf die angezeigte Farbe für Ticket-Titel " -"in Übersichten aus." +"Screencast, der den Prozess der Buchung des benötigten sipgate.io-Addons " +"zeigt" -#: ../system/objects.rst:239 ../system/objects.rst:241 -msgid "The color options are currently limited to the mentioned options." -msgstr "Die Farboptionen sind derzeit auf die genannten Optionen beschränkt." +#: ../system/integrations/cti/provider-configurations/sipgate.rst:52 +msgid "Step 2: Configure webhook for Zammad" +msgstr "Schritt 2: Konfigurieren Sie den Webhook für Zammad" -#: ../system/objects.rst:243 ../system/objects.rst:245 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:38 msgid "" -"You can create a note for the priority to inform other admins about the " -"priority. This has no effect on tickets." +"Within your ``Accountverwaltung`` navicate to your product ``sipgate.io``. " +"In the newly opened tab, switch from \"Clients\" to \"Webhooks\" and paste " +"the endpoint URLs from your Zammad instance like so:" msgstr "" -"Sie können eine Notiz für die Priorität erstellen, um andere Administratoren " -"über die Priorität zu informieren. Dies hat keine Auswirkungen auf Tickets." +"Navigieren Sie innerhalb Ihrer ``Accountverwaltung`` zu Ihrem Produkt " +"``sipgate.io``. Wechseln Sie im neu geöffneten Tab von \"Clients\" zu " +"\"Webhooks\" und fügen Sie die Endpunkt-URLs aus Ihrer Zammad-Instanz wie " +"folgt ein:" -#: ../system/objects.rst:247 ../system/objects.rst:249 -msgid "Set the priority to *active* or *inactive*." -msgstr "Setzen Sie die Priorität auf *aktiv* oder *inaktiv*." +#: ../system/integrations/cti/provider-configurations/sipgate.rst:42 +msgid "Inbound endpoint to \"Incoming\"" +msgstr "Eingehender Endpunkt auf \"Incoming\"" -#: ../system/objects/external-data-source-example.rst:2 -msgid "External Data Source" -msgstr "Externe Datenquelle" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:43 +msgid "Outbound endpoint to \"Outgoing\"" +msgstr "Ausgehender Endpunkt auf \"Outgoing\"" -#: ../system/objects/external-data-source-example.rst:4 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:47 msgid "" -"We assume you already had a look on :doc:`types` where you can find a " -"description of the individual fields." +"Ensure to select at least one call group or phoneline within \"Sources\". " +"Other wise Sipgate will not indicate any incoming or outgoing calls to " +"Zammad." msgstr "" -"Wir gehen davon aus, dass Sie bereits einen Blick auf :doc:`types` geworfen " -"haben, wo Sie eine Beschreibung der einzelnen Felder finden können." +"Stellen Sie sicher, dass Sie mindestens eine Rufgruppe oder Telefonleitung " +"unter \"Sources\" auswählen. Andernfalls wird Sipgate keine eingehenden oder " +"ausgehenden Anrufe an Zammad anzeigen." -#: ../system/objects/external-data-source-example.rst:7 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"To reproduce this example, choose a category you want to add a custom field, " -"click on *New Attribute* and select *External data source field* under " -"*Format*." +"Screencast showing how to add Zammad's endpoint URLs to sipgate.ios webhook " +"configuration" msgstr "" -"Um dieses Beispiel zu reproduzieren, wählen Sie eine Kategorie, der Sie ein " -"benutzerdefiniertes Feld hinzufügen möchten, klicken Sie auf *Neues " -"Attribut* und wählen Sie *Externe Daten-Feld* unter *Format*." +"Screencast, der zeigt, wie die Endpunkt-URLs von Zammad zur sipgate.ios-" +"Webhook-Konfiguration hinzugefügt werden" -#: ../system/objects/external-data-source-example.rst:11 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:55 msgid "" -"Our example story is to fetch data from an external product database. We " -"want to add our products to the tickets so that the products can be searched " -"and chosen from a list and also create a link to the product website." +"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " +"the Webhooks → URLs section of Sipgate you can select which *sources* " +"Sipgate should notify Zammad about in- and outgoing calls." msgstr "" -"In unserem Beispiel geht es darum, Daten aus einer externen Produktdatenbank " -"abzurufen. Wir möchten unsere Produkte zu den Tickets hinzufügen, damit die " -"Produkte gesucht und aus einer Liste ausgewählt werden können, und außerdem " -"einen Link zur Produktwebsite erstellen." - -#: ../system/objects/external-data-source-example.rst:16 -msgid "Base configuration" -msgstr "Basis-Konfiguration" +"Haben Sie Nummern, die nicht für die Benachrichtigung in Zammad verwendet " +"werden sollen? Im Bereich Webhooks → URLs von Sipgate können Sie auswählen, " +"welche *sources* Sipgate über ein- und ausgehende Anrufe an Zammad " +"benachrichtigen soll." -#: ../system/objects/external-data-source-example.rst:None -msgid "Initial steps to configure external data source object type" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:59 +msgid "" +"Use either specific phone lines or use the option \"Use for all phonelines " +"and groups\" to notify Zammad about all existing lines of your Sipgate " +"account." msgstr "" -"Erste Schritte zur Konfiguration des Objekttyps der externen Datenquelle" - -#: ../system/objects/external-data-source-example.rst:23 -#: ../system/variables.rst:85 -msgid "**Example:**" -msgstr "**Beispiel:**" +"Verwenden Sie entweder bestimmte Telefonleitungen oder verwenden Sie die " +"Option \"Use for all phonelines and groups\", um Zammad über alle " +"vorhandenen Leitungen Ihres Sipgate-Kontos zu informieren." -#: ../system/objects/external-data-source-example.rst:25 -msgid "Name: *product*" -msgstr "Name: *product*" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "" +"Screenshot showing a sample selection of phone numbers to use for the " +"Sipgates webhooks API" +msgstr "" +"Screenshot mit einer Beispielauswahl von Telefonnummern für die Sipgate " +"Webhooks API" -#: ../system/objects/external-data-source-example.rst:26 -msgid "Display: *Product*" -msgstr "Display: *Product*" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:68 +msgid "This section also allows you to enable a Debug log." +msgstr "In diesem Abschnitt können Sie auch ein Debug-Protokoll aktivieren." -#: ../system/objects/external-data-source-example.rst:29 -msgid "External data source configuration" -msgstr "Konfiguration der externen Datenquelle" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "Screenshot showing an enabled Debug log option" +msgstr "Screenshot zeigt die aktivierte Debug-Funktion" -#: ../system/objects/external-data-source-example.rst:31 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:73 msgid "" -"First, enter the search URL making sure it contains ``#{search.term}`` as a " -"parameter:" +"After enabling you can use the Debug log section to see all sent webhook " +"calls to Zammad. You'll also can see the response." msgstr "" -"Geben Sie zunächst die Such-URL ein und vergewissern Sie sich, dass sie " -"``#{search.term}`` als Parameter enthält:" +"Nach der Aktivierung können Sie den Abschnitt Debug-Log verwenden, um alle " +"gesendeten Webhook-Aufrufe an Zammad zu sehen. Sie können auch die Antwort " +"sehen." -#: ../system/objects/external-data-source-example.rst:34 -msgid "**Example:** ``https://dummyjson.com/products/search?q=#{search.term}``" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "" +"Screenshot showing sample log entries for Sipgates webhook calls to Zammad" msgstr "" -"**Beispiel:** ``https://dummyjson.com/products/search?q=#{search.term}``" +"Screenshot mit Beispielprotokolleinträgen für Sipgates Webhook-Aufrufe an " +"Zammad" -#: ../system/objects/external-data-source-example.rst:36 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:81 +msgid "Step 4 (optional): Further configurations for Sipgate" +msgstr "Schritt 4 (optional): Weitere Konfigurationen für Sipgate" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:80 msgid "" -"After that, head down to the preview section and enter a search input for " -"the external data source." +"If needed, you can now configure Zammad's Sipgate integration in more " +"detail. You can learn more about your options here: :ref:`Sipgate " +"integration settings `." msgstr "" -"Danach gehen Sie in den Vorschaubereich und geben einen Suchbegriff für die " -"externe Datenquelle ein." - -#: ../system/objects/external-data-source-example.rst:39 -msgid "**Example:** ``mac``" -msgstr "**Beispiel:** ``mac``" +"Bei Bedarf können Sie nun die Sipgate-Integration von Zammad detaillierter " +"konfigurieren. Erfahren Sie hier mehr über Ihre Optionen: :ref:`Sipgate-" +"Integrationseinstellungen `." -#: ../system/objects/external-data-source-example.rst:41 -msgid "Then you can find a preview of the response data below:" -msgstr "Anschließend finden Sie eine Vorschau der Antwortdaten:" +#: ../system/integrations/cti/sipgate.rst:2 +msgid "Sipgate (sipgate.io)" +msgstr "Sipgate (sipgate.io)" -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of JSON response based on search term" -msgstr "Vorschau der JSON-Antwort basierend auf dem Suchbegriff" +#: ../system/integrations/cti/sipgate.rst:16 +msgid "You need an administrative Sipgate account for your organization." +msgstr "Sie benötigen ein administratives Sipgate-Konto für Ihre Organisation." -#: ../system/objects/external-data-source-example.rst:48 +#: ../system/integrations/cti/sipgate.rst:17 msgid "" -"We recommend using the preview to have a look on the structure. There is a " -"top-level element called ``products``. One level below, you can find the " -"attributes ``id`` and ``title``." +"Zammad requires a ``sipgate.io`` addon from the feature store (please note " +"that API calls are not free with Sipgate. Rates may apply and differ from " +"account to account)." msgstr "" -"Wir empfehlen, die Vorschau zu benutzen, um einen Blick auf die Struktur zu " -"werfen. Es gibt ein Top-Level-Element namens ``products``. Eine Ebene " -"darunter finden Sie die Attribute ``id`` und ``title``." +"Zammad erfordert ein ``sipgate.io`` Addon aus dem Feature Store (bitte " +"beachten Sie, dass API-Aufrufe mit Sipgate nicht kostenlos sind. Es können " +"Gebühren anfallen, die sich von Konto zu Konto unterscheiden)." -#: ../system/objects/external-data-source-example.rst:52 -msgid "**Search result response based on search from example:**" -msgstr "**Suchergebnis-Antwort basierend auf der Suche aus dem Beispiel:**" +#: ../system/integrations/cti/sipgate.rst:21 +msgid "Sipgate must be able to reach your Zammad instance." +msgstr "Sipgate muss in der Lage sein Ihre Zammad-Instanz zu erreichen." -#: ../system/objects/external-data-source-example.rst:119 +#: ../system/integrations/cti/sipgate.rst:25 +msgid ":doc:`provider-configurations/sipgate`" +msgstr ":doc:`provider-configurations/sipgate`" + +#: ../system/integrations/cti/sipgate.rst:24 msgid "" -"To tell the remote system that the desired data is located below the " -"``products`` level, you have to put it in the field *Search result list key*." +"Learn how to configure Sipgate to enable Zammad and Sipgate to communicate " +"with each other." msgstr "" -"Um dem entfernten System mitzuteilen, dass sich die gewünschten Daten " -"unterhalb der Ebene ``products`` befinden, müssen Sie dies in das Feld " -"*Search result list key* eintragen." +"Erfahren Sie, wie Sie Sipgate konfigurieren, damit Zammad und Sipgate " +"miteinander kommunizieren können." -#: ../system/objects/external-data-source-example.rst:122 +#: ../system/integrations/cti/sipgate.rst:33 msgid "" -"After inserting ``products`` in the mentioned field, you get an extended " -"preview. You can find an additional box *Search result list* with a JSON " -"structure. This is the same response as before but stripped from the upper " -"``products`` element by the external data source." +"Below endpoint settings affect the :doc:`sipgate.io configuration `." msgstr "" -"Nach dem Einfügen von ``products`` in das genannte Feld, erhalten Sie eine " -"erweiterte Vorschau. Sie können ein zusätzliches Feld *Search result list* " -"mit einer JSON-Struktur finden. Dies ist die gleiche Antwort wie zuvor, aber " -"das obere Element ``products`` wurde von der externen Datenquelle entfernt." +"Die folgenden Endpunkteinstellungen betreffen die :doc:`sipgate.io-" +"Konfiguration `." -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of JSON response search result list" -msgstr "Vorschau der Suchergebnisliste der JSON-Antwort" +#: ../system/integrations/cti/sipgate.rst:37 +msgid "This endpoint is required for incoming call hooks." +msgstr "Dieser Endpunkt ist für eingehende Anrufe erforderlich." -#: ../system/objects/external-data-source-example.rst:132 -msgid "" -"Now you need to provide the keys for the search result values and labels. As " -"already mentioned, we are looking for the ``id`` and the ``title`` of our " -"products. If you haven't already, it is now a good time to look at the " -"preview of the *Search result list*." -msgstr "" -"Nun müssen Sie die Schlüssel für die Werte und Bezeichnungen der " -"Suchergebnisse angeben. Wie bereits erwähnt, suchen wir nach der ``id`` und " -"dem ``title`` unserer Produkte. Wenn Sie es noch nicht getan haben, ist es " -"jetzt ein guter Zeitpunkt, sich die Vorschau der *Suchergebnisliste* " -"anzusehen." +#: ../system/integrations/cti/sipgate.rst:40 +msgid "This endpoint is required for outgoing call hooks." +msgstr "Dieser Endpunkt ist für ausgehende Anrufe erforderlich." -#: ../system/objects/external-data-source-example.rst:197 -msgid "" -"After locating our two keys, we insert them in *search result value key* " -"(``id``) and in *Search result label key* (``title``)." +#: ../system/integrations/cti/sipgate.rst:0 +msgid "Screenshot showing sample user mappings in between Sipgate and Zammad" msgstr "" -"Nachdem wir unsere beiden Schlüssel gefunden haben, fügen wir sie in " -"*Schlüssel Suchergebniswert* (``id``) und in den *Schlüssel " -"Suchergebnisbezeichnung* (``title``) ein." +"Screenshot mit Beispielen für Benutzerzuordnungen zwischen Sipgate und Zammad" -#: ../system/objects/external-data-source-example.rst:200 +#: ../system/integrations/cti/sipgate.rst:69 msgid "" -"Basically, we configured the external data source already and we can see a " -"table in the preview section:" +"You can find your agent's Sipgate username within ``Accountverwaltung → " +"Benutzer``. You're looking for the SIP-ID." msgstr "" -"Im Grunde haben wir die externe Datenquelle bereits konfiguriert, und wir " -"können eine Tabelle im Vorschaubereich sehen:" +"Den Sipgate-Benutzernamen Ihres Agenten finden Sie unter ``Accountverwaltung " +"→ Benutzer``. Suchen Sie nach der SIP-ID." -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of product table based on search term" -msgstr "Vorschau der Produkttabelle auf Basis des Suchbegriffs" +#: ../system/integrations/cti/sipgate.rst:0 +msgid "Sample VoIP credentials for a Sipgate user" +msgstr "Beispiel für VoIP-Anmeldeinformationen für einen Sipgate-Benutzer" -#: ../system/objects/external-data-source-example.rst:208 -msgid "" -"According to our example story, now just the *Link template* is missing." -msgstr "Gemäß unserem Beispiel fehlt jetzt nur noch das *Link-Template*." +#: ../system/integrations/cti/sipgate.rst:77 +msgid "Users with several devices also have several SIP-IDs." +msgstr "Benutzer mit mehreren Geräten haben auch mehrere SIP-IDs." -#: ../system/objects/external-data-source-example.rst:210 -msgid "" -"Please note that this is an optional feature. If you don't want to use such " -"links, of course you don't have to configure it." -msgstr "" -"Bitte beachten Sie, dass dies eine optionale Funktion ist. Wenn Sie solche " -"Links nicht verwenden möchten, müssen Sie sie natürlich auch nicht " -"konfigurieren." +#: ../system/integrations/elasticsearch.rst:2 +msgid "Elasticsearch (SaaS)" +msgstr "Elasticsearch (SaaS)" -#: ../system/objects/external-data-source-example.rst:213 +#: ../system/integrations/elasticsearch.rst:4 msgid "" -"We can add now an address where additional product information can be found." +"The Elasticsearch integration allows you to create a read-only user to use " +"with your favorite reporting tool (e.g. like Grafana)." msgstr "" -"Wir können nun eine Adresse hinzufügen, unter der zusätzliche " -"Produktinformationen zu finden sind." - -#: ../system/objects/external-data-source-example.rst:215 -msgid "Example: ``https://your_domain.com/q=#{ticket.product}``" -msgstr "Beispiel: ``https://ihre_domain.com/q=#{ticket.product}``" - -#: ../system/objects/external-data-source-example.rst:217 -msgid "In the example, the parameter means:" -msgstr "In diesem Beispiel bedeutet der Parameter:" - -#: ../system/objects/external-data-source-example.rst:219 -msgid "``#{}``: \"Frame\" for the insertion of information" -msgstr "``#{}``: \"Rahmen\" für das Einfügen von Informationen" +"Die Elasticsearch-Integration ermöglicht es Ihnen, einen schreibgeschützten " +"Benutzer zu erstellen, den Sie mit Ihrem bevorzugten Reporting-Tool (z.B. " +"Grafana) verwenden können." -#: ../system/objects/external-data-source-example.rst:220 -msgid "``ticket``: object level, where you create your custom object" +#: ../system/integrations/elasticsearch.rst:7 +msgid "" +"If you want to take full advantage of the Zammad reporting, have a look at " +"our :docs:`Grafana ` " +"setup page as well." msgstr "" -"``ticket``: Objektebene, auf der Sie Ihr benutzerdefiniertes Objekt erstellen" +"Wenn Sie die Vorteile des Reportings mit Zammad voll ausschöpfen wollen, " +"sollten Sie auch einen Blick auf unsere Seite zur :docs:`Grafana-Einrichtung " +"` werfen." -#: ../system/objects/external-data-source-example.rst:221 -msgid "``product``: name of the (custom) object" -msgstr "``product``: Name des (benutzerdefinierten) Objekts" +#: ../system/integrations/elasticsearch.rst:11 ../system/subscription.rst:7 +msgid "**🚧 Hosted environment specific 🚧**" +msgstr "**🚧 Spezifisch für die gehostete Umgebung 🚧**" -#: ../system/objects/external-data-source-example.rst:223 +#: ../system/integrations/elasticsearch.rst:13 msgid "" -"After configuring your *Link template*, there will be another column in the " -"preview. Hovering on the icons in the *Link* column will show you where it " -"forwards you." +"This integration is only available for Hosted setups. In order to use " +"Elasticsearch you'll need the **Plus** subscription." msgstr "" -"Nachdem Sie Ihr *Link-Template* konfiguriert haben, wird in der Vorschau " -"eine weitere Spalte angezeigt. Wenn Sie mit der Maus über die Symbole in der " -"Spalte *Link* fahren, sehen Sie, wohin der Link verweist." +"Diese Integration steht nur in gehosteten Umgebungen zur Verfügung. Um " +"Elasticsearch nutzen zu können, benötigen Sie ein **Plus** Abonnement." -#: ../system/objects/external-data-source-example.rst:232 +#: ../system/integrations/elasticsearch.rst:16 msgid "" -"In our example, one of the links looks like: https://your_domain.com/q=6, " -"where the 6 is the product id." +"Self hosted users have all the control over their self hosted Elasticsearch " +"instances." msgstr "" -"In unserem Beispiel sieht einer der Links so aus: https://ihre_domain.com/" -"q=6, wobei die 6 die Produkt-ID ist." +"Selbstgehostete Nutzer haben die gesamte Kontrolle über ihre selbst " +"gehosteten Elasticsearch-Instanzen." -#: ../system/objects/external-data-source-example.rst:235 -msgid "You can find more information regarding the URL in :doc:`types`." -msgstr "Weitere Informationen zur URL finden Sie in :doc:`types`." +#: ../system/integrations/elasticsearch.rst:None +msgid "Elasticsearch integration page on SaaS environments" +msgstr "Seite Elasticsearch-Integrations für SaaS-Umgebungen" -#: ../system/objects/includes/adding-values-hint.include.rst:3 +#: ../system/integrations/elasticsearch.rst:27 msgid "" -"Adding values can be tricky for first timers, don't forget to press \"➕ " -"Add\" after typing your values. Otherwise you may loose a value." +"Please note the following limitations of Elasticsearch access on hosted " +"environments:" msgstr "" -"Das Hinzufügen von Werten kann für Neulinge schwierig sein. Vergessen Sie " -"nicht, nach der Eingabe Ihrer Werte auf \"➕ Hinzufügen\" zu drücken. " -"Andernfalls wird der zuletzt hinzugefügte Wert nicht gespeichert." +"Bitte beachten Sie die folgenden Limitierungen für den Elasticsearch-Zugriff " +"auf gehosteten Umgebungen:" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:1 -#: ../system/objects/includes/reposition-values.include.rst:1 -msgid "**↕️ This field type allows the positioning of its values ↔️**" -msgstr "**↕️ Dieser Feldtyp erlaubt die Positionierung der Werte ↔️**" +#: ../system/integrations/elasticsearch.rst:30 +msgid "access to the Elasticsearch index is read-only access" +msgstr "der Zugriff auf Elasticsearch-Indexe ist ein lesender Zugriff" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:3 +#: ../system/integrations/elasticsearch.rst:31 +msgid "currently you're limited to user only" +msgstr "Sie sind zur Zeit auf einen Benutzer beschränkt" + +#: ../system/integrations/elasticsearch.rst:32 msgid "" -"In order to re-arrange the field values, first edit the field. Then you can " -"use ☰ to drag the values in question to the correct position. If you want to " -"change the layer depth, double click on ☰. With it you can cycle through the " -"available layers." +"Reporting tools that require to write into the indexes (like Kibana) are not " +"supported" msgstr "" -"Um die Feldwerte neu anzuordnen, bearbeiten Sie zunächst das Feld. Dann " -"können Sie mit ☰ die betreffenden Werte an die richtige Stelle ziehen. Wenn " -"Sie die Ebenentiefe ändern möchten, doppelklicken Sie auf ☰. Damit können " -"Sie durch die verfügbaren Ebenen wechseln." +"Reporting-Tools die Schreibzugriff auf Indexen benötigen (wie Kibana) werden " +"nicht unterstützt" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:8 -msgid "When you're ready, submit your changes to save the object attribute." -msgstr "" -"Wenn Sie fertig sind, klicken Sie auf \"Übermitteln\", um das Objektattribut " -"zu speichern." +#: ../system/integrations/elasticsearch.rst:34 +msgid "IP access restriction is currently not yet supported" +msgstr "IP-Zugriffsbeschränkung wird zur Zeit noch nicht unterstützt" -#: :0 ../system/objects/types.rst:0 -msgid "" -"Screencast showing how to re-position values on tree select like\n" -"fields" -msgstr "" -"Screencast zur Neupositionierung von Werten in Feldern wie der Baumauswahl" +#: ../system/integrations/elasticsearch.rst:37 +msgid "Activating Elasticsearch Access" +msgstr "Aktivieren des Elasticsearch-Zugangs" -#: ../system/objects/includes/reposition-values.include.rst:3 +#: ../system/integrations/elasticsearch.rst:39 msgid "" -"In order to re-arrange the field values, edit the field and scroll below the " -"values. Make sure to tick the option \"Use custom option sort\"." +"By default external access to your Elasticsearch index is not active. You " +"can enable the integration at any time if needed." msgstr "" -"Um die Feldwerte neu anzuordnen, bearbeiten Sie das Feld und scrollen Sie " -"unter die Tabelle. Vergewissern Sie sich, dass Sie die Option \"Verwende " -"benutzerdefinierte Sortierung\" aktiviert haben." +"Standardmäßig ist der externe Zugriff auf Ihren Elasticsearch-Index nicht " +"aktiv. Sie können die Integration bei Bedarf jederzeit aktivieren." -#: ../system/objects/includes/reposition-values.include.rst:8 +#: ../system/integrations/elasticsearch.rst:42 msgid "" -"If you do not tick this field, all manual positioning you did above will be " -"lost upon saving! ☠️" +"Please ensure to note down the password provided - you won't have access to " +"it afterwards." msgstr "" -"Wenn Sie das nicht aktiviert haben, gehen alle manuell festgelegten " -"Positionen beim Speichern verloren! ☠️" +"Bitte notieren Sie sich das angegebene Passwort, da Sie später keinen " +"Zugriff mehr darauf haben." -#: ../system/objects/includes/reposition-values.include.rst:11 -msgid "" -"Now use ☰ to drag the values in question to the correct position. When " -"you're ready, submit your changes to save the object attribute." -msgstr "" -"Ziehen Sie nun mit ☰ die Einträge an die richtige Position. Wenn Sie fertig " -"sind, übernehmen Sie Ihre Änderungen, um das Objektattribut zu speichern." +#: ../system/integrations/elasticsearch.rst:None +msgid "Screencast showing activation of Elasticsearch integration" +msgstr "Screencast zeigt Aktivierung der Elasticsearch-Integration" -#: :0 ../system/objects/types.rst:0 -msgid "Screencast showing how to re-position values" -msgstr "Screencast, der zeigt, wie man Einträge neu positioniert" +#: ../system/integrations/elasticsearch.rst:51 +msgid "Connection Settings" +msgstr "Verbindungs-Einstellungen" -#: ../system/objects/includes/url-template-hint.include.rst:3 +#: ../system/integrations/elasticsearch.rst:53 msgid "" -"This field allows using :ref:`URL fields (Link Templates) `." +"This section holds the most important general information for accessing your " +"Elasticsearch indexes - such as:" msgstr "" -"Dieses Feld ermöglicht die Verwendung von :ref:`URL-Feldern (Link-Vorlagen) " -"`." +"Dieser Abschnitt enthält die wichtigsten allgemeinen Informationen für den " +"Zugriff auf Ihre Elasticsearch-Indizes - wie zum Beispiel:" -#: ../system/objects/permissions.rst:2 -msgid "Attribute Permissions" -msgstr "Berechtigungen für Attribute" +#: ../system/integrations/elasticsearch.rst:57 +msgid "A unique subdomain that does not tell your real instance URL." +msgstr "Eine eindeutige Subdomain, die Ihre echte Instanz-URL nicht verrät." -#: ../system/objects/permissions.rst:7 +#: ../system/integrations/elasticsearch.rst:61 +msgid "Software" +msgstr "Software" + +#: ../system/integrations/elasticsearch.rst:60 msgid "" -"In the object attributes configuration you can define if a field is shown " -"and if the input in the field is mandatory, separated by different screens " -"and for different :doc:`roles/permissions `." +"The major version of the search index being used. This is required by some " +"Reporting tools like Grafana." msgstr "" -"In der Konfiguration der Objektattribute können Sie festlegen, ob ein Feld " -"angezeigt wird und ob die Eingabe in das Feld verpflichtend ist, und zwar " -"separat für verschiedene Ansichten und für verschiedene :doc:`Rollen/" -"Berechtigungen `." - -#: ../system/objects/permissions.rst:17 -msgid "Screenshot shows object attribute permission table" -msgstr "Screenshot zeigt Objektattribut-Berechtigungstabelle" +"Die Hauptversion des verwendeten Suchindexes. Dies wird von einigen " +"Reporting-Tools wie Grafana benötigt." -#: ../system/objects/permissions.rst:17 -msgid "" -"Some of the possible permissions and screen options for a user object " -"attribute." -msgstr "" -"Einige der möglichen Berechtigungen und Ansichten für ein Attribut eines " -"Benutzerobjekts." +#: ../system/integrations/elasticsearch.rst:64 +msgid "Authentication" +msgstr "Authentifizierung" -#: ../system/objects/permissions.rst:19 +#: ../system/integrations/elasticsearch.rst:64 +msgid "The authentication type being supported. ``Basic Authentication``" +msgstr "Der unterstützte Authentifizierungstyp. ``Basic Authentication``" + +#: ../system/integrations/elasticsearch.rst:67 +msgid "Available Indexes" +msgstr "Verfügbare Indexe" + +#: ../system/integrations/elasticsearch.rst:69 msgid "" -"Based on the object context (ticket, agent, organization, user), the " -"selectable roles (to be precise: the required permissions) and screens " -"differ. Be aware that these settings aren't affecting data creation via " -"other channels than the UI." +"Within this section we're displaying the -in our opinion- most important " +"indexes for a Zammad instance." msgstr "" -"Je nach Objektkontext (Ticket, Agent, Organisation, Benutzer) unterscheiden " -"sich die auswählbaren Rollen (genauer gesagt: die erforderlichen " -"Berechtigungen) und Ansichten. Beachten Sie, dass diese Einstellungen keinen " -"Einfluss auf die Datenerstellung über andere Kanäle als die " -"Benutzeroberfläche haben." +"In diesem Abschnitt zeigen wir die - unserer Meinung nach - wichtigsten " +"Indizes für eine Zammad-Instanz an." -#: ../system/objects/permissions.rst:24 +#: ../system/integrations/elasticsearch.rst:72 msgid "" -"If you want to have further customization possibilities, you should have a " -"look at the :doc:`core workflows `." +"If you require all indexes or our listing is not good enough for you, point " +"your browser to the URL we're providing and append ``/_aliases?" +"pretty=true``. The result should look like this: ``https://.zammad.com/" +"_aliases?pretty=true``." msgstr "" -"Wenn Sie weitere Anpassungsmöglichkeiten brauchen, sollten Sie einen Blick " -"in die :doc:`Core Workflows ` werfen." - -#: ../system/objects/permissions.rst:28 -msgid "Screens" -msgstr "Ansichten" +"Wenn Sie alle Indizes benötigen oder Ihnen unsere Auflistung nicht " +"ausreicht, rufen Sie mit Ihrem Browser die von uns angegebene URL auf und " +"fügen Sie ``/_aliases?pretty=true`` hinzu. Das Ergebnis sollte wie folgt " +"aussehen: ``https://.zammad.com/_aliases?pretty=true``." -#: ../system/objects/permissions.rst:30 +#: ../system/integrations/elasticsearch.rst:77 msgid "" -"In the table below you can find an overview about the different permissions " -"and the available screens Zammad distinguishes between." +"Your browser will automatically ask for your credentials - you'll then see " +"something like this:" msgstr "" -"In der folgenden Tabelle finden Sie eine Übersicht über die verschiedenen " -"Berechtigungen und die verfügbaren Ansichten, die Zammad unterscheidet." - -#: ../system/objects/permissions.rst:37 -msgid "Screen" -msgstr "Ansicht" - -#: ../system/objects/permissions.rst:38 -msgid "Available for" -msgstr "Verfügbar für" - -#: ../system/objects/permissions.rst:40 -msgid "create" -msgstr "create" - -#: ../system/objects/permissions.rst:41 ../system/objects/permissions.rst:52 -#: ../system/objects/permissions.rst:59 ../system/objects/permissions.rst:73 -msgid "admin.user" -msgstr "admin.user" - -#: ../system/objects/permissions.rst:42 ../system/objects/permissions.rst:53 -#: ../system/objects/permissions.rst:60 -msgid "admin.organization" -msgstr "admin.organization" - -#: ../system/objects/permissions.rst:43 ../system/objects/permissions.rst:54 -#: ../system/objects/permissions.rst:61 -msgid "admin.group" -msgstr "admin.group" - -#: ../system/objects/permissions.rst:44 -msgid "Creation dialog for not yet existing data" -msgstr "Erstellungsdialog für noch nicht vorhandene Daten" - -#: ../system/objects/permissions.rst:45 -msgid "create_middle" -msgstr "create_middle" - -#: ../system/objects/permissions.rst:46 ../system/objects/permissions.rst:50 -#: ../system/objects/permissions.rst:57 ../system/objects/permissions.rst:66 -#: ../system/objects/permissions.rst:70 -msgid "ticket.customer" -msgstr "ticket.customer" - -#: ../system/objects/permissions.rst:47 ../system/objects/permissions.rst:51 -#: ../system/objects/permissions.rst:58 ../system/objects/permissions.rst:69 -msgid "ticket.agent" -msgstr "ticket.agent" - -#: ../system/objects/permissions.rst:48 -msgid "Ticket create dialog (middle section)" -msgstr "Ticket-Erstellungsdialog (mittlerer Bereich)" - -#: ../system/objects/permissions.rst:49 -msgid "edit" -msgstr "edit" - -#: ../system/objects/permissions.rst:55 -msgid "Editing dialog for already existing data" -msgstr "Bearbeitungsdialog für bereits vorhandene Daten" - -#: ../system/objects/permissions.rst:56 -msgid "view" -msgstr "Ansicht" - -#: ../system/objects/permissions.rst:62 -msgid "View-only dialog for already existing data" -msgstr "Lese-Ansicht für bereits vorhandene Daten" - -#: ../system/objects/permissions.rst:64 -msgid "(e.g. user or organization from search)" -msgstr "(z.B. Benutzer oder Organisation über die Suche)" - -#: ../system/objects/permissions.rst:65 -msgid "signup" -msgstr "signup" - -#: ../system/objects/permissions.rst:67 -msgid "Sign-up screen for new customers" -msgstr "Anmelde-Ansicht für neue Kunden" +"Ihr Browser fragt automatisch nach Ihren Zugangsdaten - Sie sehen dann etwas " +"wie das hier:" -#: ../system/objects/permissions.rst:68 -msgid "invite_customer" -msgstr "invite_customer" +#: ../system/integrations/elasticsearch.rst:125 +msgid "Credentials" +msgstr "Zugangsdaten" -#: ../system/objects/permissions.rst:71 +#: ../system/integrations/elasticsearch.rst:127 msgid "" -"Customer invitation screen (from :doc:`First Steps ` area)" +"Within this section Zammad displays your available users. The password is " +"provided once (upon activation) and cannot be retrieved after that." msgstr "" -"Ansicht zur Einladung von Kunden (aus dem Bereich :doc:`Erste Schritte `)" - -#: ../system/objects/permissions.rst:72 -msgid "invite_agent" -msgstr "invite_agent" +"In diesem Abschnitt zeigt Zammad Ihre verfügbaren Benutzer an. Das Passwort " +"wird einmalig vergeben (bei der Aktivierung) und kann danach nicht mehr " +"abgerufen werden." -#: ../system/objects/permissions.rst:74 +#: ../system/integrations/elasticsearch.rst:131 msgid "" -"Agent invitation screen (from :doc:`First Steps ` area)" +"If you need to change or reset your Elasticsearch user password, use the " +"\"Reset password\" button in the credentials table. Doing so creates a brand " +"new password for the account in question. This change is immediate, keep in " +"mind that this may affect third party tools connected to your instance." msgstr "" -"Ansicht für die Einladung von Agenten (aus dem Bereich :doc:`Erste Schritte " -"`)" +"Wenn Sie das Passwort Ihres Elasticsearch-Benutzers ändern oder zurücksetzen " +"müssen, verwenden Sie die Schaltfläche \"Passwort zurücksetzen\" in der " +"Tabelle mit den Zugangsdaten. Auf diese Weise wird ein neues Passwort für " +"das betreffende Konto erstellt. Diese Änderung wird sofort durchgeführt. " +"Beachten Sie, dass dies Auswirkungen auf Tools von Drittanbietern haben " +"kann, die mit Ihrer Instanz verbunden sind." -#: ../system/objects/permissions.rst:78 -msgid "Screen Options" -msgstr "Ansicht Optionen" +#: ../system/integrations/exchange.rst:2 +msgid "Exchange" +msgstr "Exchange" -#: ../system/objects/permissions.rst:80 +#: ../system/integrations/exchange.rst:4 msgid "" -"For the different screens you can select \"show\" and \"required\" options." +"With Zammad's Exchange integration, you can easily use existing address " +"books without having to update more than one source." msgstr "" -"Für die verschiedenen Ansichten können Sie die Optionen \"anzeigen\" und " -"\"erforderlich\" auswählen." +"Mit der Exchange-Integration von Zammad können Sie vorhandene Adressbücher " +"verwenden, ohne mehr als eine Datenquelle aktualisieren zu müssen." -#: ../system/objects/permissions.rst:82 -msgid "**shown:** Show (check) or hide (uncheck) a field." +#: ../system/integrations/exchange.rst:7 +msgid "" +"However, you should refrain from syncing all addresses, as the results may " +"not be what you expect (Exchange collects huge amounts of addresses). A " +"central address book of your company to sync makes more sense, as you can " +"ensure that Zammad gets only the data you need and want. Apart from this, it " +"is even not possible to sync the Global Address List (GAL) of your Exchange " +"system with Zammad." msgstr "" -"**Anzeigen:** Ein Feld anzeigen (Haken gesetzt) oder ausblenden (Haken nicht " -"gesetzt)." +"Sie sollten jedoch davon absehen, alle Adressen zu synchronisieren, da die " +"Ergebnisse möglicherweise nicht das sind, was Sie erwarten (Exchange sammelt " +"riesige Mengen an Adressen). Ein zentrales Adressbuch Ihrer Firma zu " +"synchronisieren ist sinnvoller, da Sie so sicherstellen können, dass Zammad " +"nur die Daten erhält, die Sie brauchen und wollen. Abgesehen davon ist es " +"nicht möglich, die Globale Adressliste (GAL) Ihres Exchange-Systems mit " +"Zammad zu synchronisieren." -#: ../system/objects/permissions.rst:83 +#: ../system/integrations/exchange.rst:16 msgid "" -"**required:** Set a field to mandatory (check). Forces users (via UI and " -"API) to populate the field." +"**Exchange and LDAP:** The exchange sync can be overruled by Zammad's LDAP " +"integration. If you have the same users in both sources, the LDAP version " +"will always be Zammad's pick." msgstr "" -"**Erforderlich:** Setzen Sie ein Feld auf erforderlich (Haken gesetzt), um " -"eine Eingabe (über UI und API) zu erzwingen." - -#: ../system/objects/types.rst:7 -msgid "Example external data source" -msgstr "Beispiel externe Datenquelle" - -#: ../system/objects/types.rst:2 -msgid "Attribute types" -msgstr "Attribut-Typen" +"**Exchange und LDAP:** Die Exchange-Synchronisierung kann durch die LDAP-" +"Integration von Zammad übersteuert werden. Wenn Sie die gleichen Benutzer in " +"beiden Quellen haben, wird die LDAP-Version immer \"gewinnen\"." -#: ../system/objects/types.rst:4 +#: ../system/integrations/exchange.rst:19 msgid "" -"When adding a new object attribute, you can choose between the following " -"attribute types." +"**One way sync:** the Exchange sync is one way. Exchange => Zammad. Changes " +"to your users inside of Zammad might be overwritten by the Exchange sync." msgstr "" -"Wenn Sie ein neues Objektattribut hinzufügen, können Sie zwischen den " -"folgenden Attributtypen wählen." +"**Einweg-Synchronisation:** Die Exchange-Synchronisation ist eine Einweg-" +"Synchronisation. Exchange => Zammad. Änderungen an Ihren Benutzern in von " +"Zammad können durch die Exchange-Synchronisierung überschrieben werden." -#: ../system/objects/types.rst:14 +#: ../system/integrations/exchange.rst:24 msgid "" -"You cannot change the attribute format / type as soon as it is applied. If " -"you no longer need an object attribute, consider disabling it instead of " -"removing." +"To configure Exchange integration, simply go to the System > Integrations > " +"Exchange in the admin panel. Press \"change\" and follow the wizard for " +"adding the needed Exchange information to Zammad. On the last two steps " +"Zammad will ask you for the address book(s) and your desired attribute " +"mapping. By default, Zammad only maps email address, first- and lastname. " +"Technically, you can map any Exchange object to a Zammad user object (this " +"also works for custom objects!)." msgstr "" -"Sie können das Format und den Typ des Attributs nicht mehr ändern, sobald es " -"gespeichert wurde. Wenn Sie ein Objektattribut nicht mehr benötigen, sollten " -"Sie es deaktivieren, anstatt es zu entfernen." - -#: ../system/objects/types.rst:18 -msgid "**What about the translation of my attributes?**" -msgstr "**Was ist mit der Übersetzung meiner Attribute?**" +"Um die Exchange-Integration zu konfigurieren, gehen Sie einfach zu System > " +"Integrationen > Exchange in den Admin-Einstellungen. Wählen Sie " +"\"Konfigurieren\" und folgen Sie dem Assistenten, um die benötigten Exchange-" +"Informationen zu Zammad hinzuzufügen. In den letzten beiden Schritten fragt " +"Zammad Sie nach dem Adressbuch und der gewünschten Attributzuordnung. " +"Standardmäßig ordnet Zammad nur E-Mail-Adressen, Vor- und Nachnamen zu. " +"Technisch gesehen können Sie jedes Exchange-Objekt einem Zammad-" +"Benutzerobjekt zuordnen (dies funktioniert auch für benutzerdefinierte " +"Objektattribute!)." -#: ../system/objects/types.rst:20 +#: ../system/integrations/exchange.rst:35 msgid "" -"For some attribute types you can decide if they should be translatable or " -"not. To be precise, it works only for the selectable fields because the " -"possible choices are known and limited. For the following attribute types, " -"you can set the translatable flag:" +"If the SSL verification fails while connecting to Exchange, Zammad will ask " +"you to turn it off temporarily." msgstr "" -"Für manche Attribut-Typen können Sie definieren, ob diese übersetzbar sein " -"sollen oder nicht. Genauer gesagt funktioniert das für auswählbare Typen " -"weil die möglichen Auswahlmöglichkeiten bekannt und begrenzt sind. Für die " -"folgenden Attribut-Typen können Sie die Übersetzbarkeit festlegen:" - -#: ../system/objects/types.rst:25 -msgid "*Boolean field*" -msgstr "*Boolean-Feld*" - -#: ../system/objects/types.rst:26 -msgid "*Single selection field*" -msgstr "*Einfachauswahl-Feld*" - -#: ../system/objects/types.rst:27 -msgid "*Multiple selection field*" -msgstr "*Mehrfachauswahl-Feld*" - -#: ../system/objects/types.rst:28 -msgid "*Single tree selection field*" -msgstr "*Einfach-Baumauswahl-Feld*" - -#: ../system/objects/types.rst:29 -msgid "*Multiple tree selection field*" -msgstr "*Mehrfach-Baumauswahl-Feld*" +"Wenn die SSL-Überprüfung bei der Verbindung zu Exchange fehlschlägt, fordert " +"Zammad Sie auf, sie vorübergehend zu deaktivieren." -#: ../system/objects/types.rst:31 +#: ../system/integrations/exchange.rst:38 msgid "" -"For these types, you can find an additional field *Translate field contents*:" +"Please be aware that **turning off SSL verification is a security risk**. It " +"should only be used temporarily or for testing purposes. If turned off, " +"there is no verification of the certificate, which means that every " +"presented certificate will be accepted." msgstr "" -"Für diese Typen gibt es ein zusätzliches Feld *Feldinhalte übersetzen*:" - -#: ../system/objects/types.rst:0 -msgid "Screenshot showing translatable attribute types" -msgstr "Screenshot mit übersetzbaren Attributtypen" - -#: ../system/objects/types.rst:38 -msgid "Screenshot with example of translatable attribute type" -msgstr "Screenshot mit Beispiel eines übersetzbaren Attributtyps" +"Bitte beachten Sie, dass **das Deaktivieren der SSL-Verifizierung ein " +"Sicherheitsrisiko darstellt**. Es sollte nur vorübergehend oder zu " +"Testzwecken verwendet werden. Wenn diese Option deaktiviert ist, findet " +"keine Überprüfung des Zertifikats statt, was bedeutet, dass jedes vorgelegte " +"Zertifikat akzeptiert wird." -#: ../system/objects/types.rst:45 -msgid "Boolean field" -msgstr "Boolean-Feld" +#: ../system/integrations/exchange.rst:43 +msgid "" +"After pressing Continue, Zammad will check if the configuration is okay. You " +"can then enable Exchange and start your first sync. The sync will then run " +"hourly - if you need to change mappings or the address book(s), you can " +"change the configuration at any time." +msgstr "" +"Nachdem Sie auf Weiter geklickt haben prüft Zammad, ob die Konfiguration in " +"Ordnung ist. Sie können dann Exchange aktivieren und Ihre erste " +"Synchronisierung starten. Die Synchronisierung läuft dann stündlich - wenn " +"Sie Zuordnungen oder das Adressbuch ändern müssen, können Sie die " +"Konfiguration jederzeit ändern." -#: ../system/objects/types.rst:41 +#: ../system/integrations/exchange.rst:50 msgid "" -"Provides a drop-down field with display values for ``true`` and ``false``. " -"Setting a default is mandatory." +"After the sync has finished, you can find the new Exchange contacts under " +"\"Users\". Zammad integrates them just as normal users." msgstr "" -"Bietet ein Dropdown-Feld mit Anzeigewerten für ``true`` und ``false``. Das " -"Festlegen eines Standardwerts ist erforderlich." +"Nach Abschluss der Synchronisierung finden Sie die neuen Exchange-Kontakte " +"unter \"Benutzer\". Zammad integriert sie genauso wie normale Benutzer." -#: ../system/objects/types.rst:0 -msgid "Available settings for Boolean fields" -msgstr "Verfügbare Einstellungen für boolesche Felder" +#: ../system/integrations/exchange.rst:55 +msgid "" +"In some cases you might see unique IDs as \"Login\" instead of the email " +"address. This is normal and doesn't affect the login or email mapping for " +"that entry." +msgstr "" +"In einigen Fällen können Sie eindeutige IDs als \"Login\" anstelle der E-" +"Mail-Adresse sehen. Dies ist normal und hat keinen Einfluss auf die " +"Zuordnung von Login oder E-Mail für diesen Eintrag." -#: ../system/objects/types.rst:55 -msgid "Date field" -msgstr "Datumsfeld" +#: ../system/integrations/github.rst:4 +msgid "" +"Use GitHub integration to track GitHub issues directly within Zammad " +"tickets. Add issue hyperlinks and get a live summary of metadata like status " +"(open/closed), assignee, labels, and more." +msgstr "" +"Verwenden Sie die GitHub-Integration, um GitHub-Issues direkt in Zammad-" +"Tickets zu verfolgen. Fügen Sie Hyperlinks zu Issues hinzu und erhalten Sie " +"eine Live-Zusammenfassung von Metadaten wie Status (offen/geschlossen), " +"zugewiesene Personen, Labels und mehr." -#: ../system/objects/types.rst:48 -msgid "Provides a date picker field and does not allow default values." -msgstr "Bietet ein Datumsauswahlfeld und lässt keine Standardwerte zu." +#: ../system/integrations/github.rst:8 +msgid "Please note that our GitHub integration does not support pull requests." +msgstr "" +"Bitte beachten Sie, dass unsere GitHub-Integration keine Pull-Requests " +"unterstützt." -#: ../system/objects/types.rst:52 -msgid "Default time diff (hours)" -msgstr "Standard-Zeit-Differenz (Stunden)" +#: ../system/integrations/github.rst:None +msgid "Integration page for GitHub" +msgstr "Seite GitHub-Integration in Zammad" -#: ../system/objects/types.rst:51 +#: ../system/integrations/github.rst:18 msgid "" -"This setting helps the user by highlighting the day from now plus the " -"provided value. It *does not* pre-fill the field." +"In your GitHub settings, create a new API token under **Developer settings > " +"Personal access tokens > Generate new token**. Leave the **Scopes** section " +"empty." msgstr "" -"Diese Einstellung hilft dem Benutzer, indem sie einen Tag hervorhebt, der " -"dem aktuellen Datum plus der Differenz entspricht. Das Feld wird *nicht* " -"vorausgefüllt." +"Erstellen Sie in Ihren GitHub-Einstellungen ein neues API-Token unter " +"**Developer settings > Personal access tokens > Generate new token**. Lassen " +"Sie den Abschnitt **Scopes** leer." -#: ../system/objects/types.rst:0 -msgid "Available settings for Date fields" -msgstr "Verfügbare Einstellungen für Datumsfelder" +#: ../system/integrations/github.rst:0 ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to create a new API token" +msgstr "Screencast zeigt Erstellung eines API-Tokens" -#: ../system/objects/types.rst:73 -msgid "Date & time field" -msgstr "Datum & Zeit-Feld" +#: ../system/integrations/github.rst:27 +msgid "Create a new API key with no scopes/privileges." +msgstr "Erstellen Sie einen neuen API-Schlüssel ohne Scopes/Berechtigungen." -#: ../system/objects/types.rst:58 -msgid "Provides a date and time picker – does not allow default values" -msgstr "Bietet eine Datums- und Zeitauswahl an - erlaubt keine Standardwerte" +#: ../system/integrations/github.rst:29 +msgid "🔒 **Will this work for private repos?**" +msgstr "🔒 **Funktioniert das auch für private Repos?**" -#: ../system/objects/types.rst:62 -msgid "Allow future" -msgstr "Werte in der Zukunft erlauben" +#: ../system/integrations/github.rst:31 +msgid "" +"No. To link private repo issues, **use the** ``repo`` **scope instead**. " +"Bear in mind that the resulting token will have `lots of permissions that it " +"doesn't actually need `_, which presents a security risk if your token ever falls into " +"the wrong hands." +msgstr "" +"Nein. Um private Repos zu verknüpfen, **verwenden Sie stattdessen den** " +"``repo`` **Scope**. Denken Sie daran, dass das resultierende Token `viele " +"Berechtigungen beinhaltet, die es eigentlich nicht braucht `_. Das stellt ein " +"Sicherheitsrisiko dar, falls Ihr Token in die falschen Hände geraten sollte." -#: ../system/objects/types.rst:0 -msgid "Forbid dates and times in the future." -msgstr "Verbietet Datum und Zeit in der Zukunft." +#: ../system/integrations/github.rst:37 +msgid "" +"Unfortunately, because of how GitHub's OAuth token scopes are set up, this " +"is the only way to link issues on private repos." +msgstr "" +"Leider ist dies aufgrund der Art und Weise, wie die OAuth-Token-Bereiche von " +"GitHub eingerichtet sind, die einzige Möglichkeit, Issues in privaten Repos " +"zu verknüpfen." -#: ../system/objects/types.rst:66 -msgid "Allow past" -msgstr "Werte in der Vergangenheit erlauben" +#: ../system/integrations/github.rst:40 +msgid "Enter your new API token in Zammad and enable GitHub integration." +msgstr "" +"Geben Sie Ihr neues API-Token in Zammad ein und aktivieren Sie die GitHub-" +"Integration." -#: ../system/objects/types.rst:0 -msgid "Forbid dates and times in the past." -msgstr "Verbietet Datum und Zeit in der Vergangenheit." +#: ../system/integrations/github.rst:0 +msgid "Screencast showing how to configure Zammad's GitHub integration" +msgstr "" +"Screencast zeigt, wie die GitHub-Integration von Zammad konfiguriert wird" -#: ../system/objects/types.rst:70 -msgid "Default time diff (minutes)" -msgstr "Standard-Zeit-Differenz (Minuten)" +#: ../system/integrations/github.rst:47 +msgid "" +"Use the default API endpoint (``https://api.github.com/graphql``) unless " +"you're using GitHub Enterprise Server." +msgstr "" +"Verwenden Sie den Standard-API-Endpunkt (``https://api.github.com/" +"graphql``), es sei denn, Sie verwenden GitHub Enterprise Server." -#: ../system/objects/types.rst:69 +#: ../system/integrations/github.rst:50 msgid "" -"This setting helps the user by highlighting the day from now plus the " -"provided value. It does not pre-fill the field." +"Once completed, a new GitHub issues tab will appear in the ticket pane. 🎉" msgstr "" -"Diese Einstellung hilft dem Benutzer, indem sie einen Tag hervorhebt, der " -"dem aktuellen Datum plus der Differenz entspricht. Das Feld wird *nicht* " -"vorausgefüllt." +"Sobald Sie das erledigt haben wird eine neue Registerkarte für GitHub-Issues " +"im Ticketbereich angezeigt. 🎉" -#: ../system/objects/types.rst:0 -msgid "Available settings for Date & time fields" -msgstr "Verfügbare Einstellungen für Datum- und Zeitfelder" +#: ../system/integrations/github.rst:59 ../system/integrations/gitlab.rst:52 +msgid "Token verification is taking a long time" +msgstr "Die Token-Verifizierung dauert sehr lange" -#: ../system/objects/types.rst:86 -msgid "Integer field" -msgstr "Zahlen-Feld" +#: ../system/integrations/github.rst:56 ../system/integrations/gitlab.rst:49 +msgid "" +"Slight delays are normal (<2 min.), especially for systems under heavy load." +msgstr "" +"Leichte Verzögerungen sind normal (<2 Min.), insbesondere bei stark " +"belasteten Systemen." -#: ../system/objects/types.rst:76 +#: ../system/integrations/github.rst:58 msgid "" -"Provides an input field that allows integer usage only. You may define a " -"default value. You cannot enforce comma separation." +"Self-hosted administrators, please check your network settings to ensure " +"that your Zammad server can reach ``api.github.com``." msgstr "" -"Bietet ein Eingabefeld, das nur die Verwendung von Ganzzahlen erlaubt. Sie " -"können einen Standardwert definieren. Dezimalstellen sind nicht erlaubt bzw. " -"werden ignoriert." +"Administratoren von selbst gehosteten Instanzen sollten Ihre " +"Netzwerkeinstellungen prüfen und sicherstellen, dass Ihr Zammad-Server ``api." +"github.com`` erreichen kann." -#: ../system/objects/types.rst:80 -msgid "Minimal" -msgstr "Minimum" +#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 +msgid "I reloaded the page and now the API token is gone" +msgstr "" +"Ich habe die Seite neu geladen, und jetzt ist das API-Token verschwunden" -#: ../system/objects/types.rst:80 -msgid "The minimal value the field accepts." -msgstr "Der Mindestwert, den das Feld akzeptiert." +#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 +msgid "" +"This may indicate that Zammad is still verifying your API token. Try " +"reloading the page again in a couple minutes." +msgstr "" +"Dies kann darauf hindeuten, dass Zammad noch dabei ist, Ihr API-Token zu " +"verifizieren. Versuchen Sie, die Seite in ein paar Minuten noch einmal zu " +"laden." -#: ../system/objects/types.rst:83 -msgid "Maximal" -msgstr "Maximum" +#: ../system/integrations/gitlab.rst:2 +msgid "GitLab" +msgstr "GitLab" -#: ../system/objects/types.rst:83 -msgid "The maximum value the field accepts." -msgstr "Der Maximalwert, den das Feld akzeptiert." +#: ../system/integrations/gitlab.rst:4 +msgid "" +"Use GitLab integration to track GitLab issues directly within Zammad " +"tickets. Add issue hyperlinks and get a live summary of metadata like status " +"(open/closed), assignee, labels, and more." +msgstr "" +"Verwenden Sie die GitLab-Integration, um GitLab-Issues direkt in Zammad-" +"Tickets zu verfolgen. Fügen Sie Hyperlinks zu Issues hinzu und erhalten Sie " +"eine Live-Zusammenfassung von Metadaten wie Status (offen/geschlossen), " +"zugewiesene Personen, Labels und mehr." -#: ../system/objects/types.rst:0 -msgid "Available settings for Integer fields" -msgstr "Verfügbare Einstellungen für Integer-Felder" +#: ../system/integrations/gitlab.rst:8 +msgid "" +"Please note that our GitLab integration does not support merge requests." +msgstr "" +"Bitte beachten Sie, dass unsere GitLab-Integration keine Merge Requests " +"unterstützt." -#: ../system/objects/types.rst:99 -msgid "Multiple selection field" -msgstr "Mehrfachauswahl-Feld" +#: ../system/integrations/gitlab.rst:None +msgid "Integration page for GitLab" +msgstr "Seite GitLab-Integration in Zammad" -#: ../system/objects/types.rst:89 +#: ../system/integrations/gitlab.rst:18 msgid "" -"Provides a selection field that allows the selection of one or more out of " -"several. This field does allow setting a default value." +"In your GitLab preferences, create a new API token under **Access Tokens**." msgstr "" -"Bietet ein Auswahlfeld, das die Auswahl von einem oder mehreren Werten " -"ermöglicht. In diesem Feld kann ein Standardwert festgelegt werden." +"Erstellen Sie in Ihren GitLab-Einstellungen ein neues API-Token unter " +"**Access Tokens**." -#: ../system/objects/types.rst:0 -msgid "Available settings for Multiple selection fields" -msgstr "Verfügbare Einstellungen für Mehrfachauswahlfelder" +#: ../system/integrations/gitlab.rst:20 +msgid "Under **Select scopes**, choose ``read_api`` only." +msgstr "Wählen Sie ausschließlich ``read_api ``unter **Select scopes**." -#: ../system/objects/types.rst:112 -msgid "Single selection field" -msgstr "Einfachauswahl-Feld" +#: ../system/integrations/gitlab.rst:27 +msgid "🔒 **If you wish to link issues on any private repos...**" +msgstr "🔒 **Wenn Sie Issues in privaten Repos verlinken möchten...**" -#: ../system/objects/types.rst:102 -msgid "" -"Provides a drop-down field that allows selection of one value out of " -"several. This field does allow setting a default value." +#: ../system/integrations/gitlab.rst:29 +msgid "Your API token must belong to an account with access to those repos." +msgstr "Ihr API-Token muss zu einem Konto mit Zugriff auf diese Repos gehören." + +#: ../system/integrations/gitlab.rst:31 +msgid "Enter your new API token in Zammad and enable GitLab integration." msgstr "" -"Bietet ein Dropdown-Feld, in dem ein Wert aus mehreren ausgewählt werden " -"kann. In diesem Feld kann auch ein Standardwert festgelegt werden." +"Geben Sie Ihr neues API-Token in Zammad ein und aktivieren Sie die GitLab-" +"Integration." -#: ../system/objects/types.rst:0 -msgid "Available settings for Single selection fields" -msgstr "Verfügbare Einstellungen für Einfachauswahl-Felder" +#: ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to configure Zammad's GitLab integration" +msgstr "Screencast zeigt die Konfiguration der GitHub-Integration in Zammad" -#: ../system/objects/types.rst:142 -msgid "Textarea field" -msgstr "Textbereich-Feld" +#: ../system/integrations/gitlab.rst:40 +msgid "" +"Use the default API endpoint (``https://gitlab.com/api/graphql``) unless " +"you're a self-hosted GitLab user." +msgstr "" +"Verwenden Sie den Standard-API-Endpunkt (``https://gitlab.com/api/" +"graphql``), es sei denn, Sie hosten GitLab selbst." -#: ../system/objects/types.rst:115 +#: ../system/integrations/gitlab.rst:43 msgid "" -"Provides a text area input field (multiple lines) and thus allows e.g. new " -"lines. You can set a default field value." +"Once completed, a new GitLab issues tab will appear in the ticket pane. 🎉" msgstr "" -"Bietet ein Eingabefeld für einen Textbereich und ermöglicht u.a. mehrere " -"Zeilen. Sie können einen Standardfeldwert festlegen." +"Sobald Sie das erledigt haben wird eine neue Registerkarte für GitLab-Issues " +"im Ticketbereich angezeigt. 🎉" -#: ../system/objects/types.rst:120 +#: ../system/integrations/gitlab.rst:51 msgid "" -"Please note that this field *does not* support text formatting or HTML " -"content (rich text)." +"Self-hosted administrators, please check your network settings to ensure " +"that your Zammad server can reach ``gitlab.com``." msgstr "" -"Bitte beachten Sie, dass dieses Feld *keine* Textformatierung oder HTML-" -"Inhalte (Rich Text) unterstützt." +"Administratoren von selbst gehosteten Zammad-Instanzen sollten Ihre " +"Netzwerkeinstellungen prüfen und sicherstellen, dass Ihr Zammad-Server " +"``gitlab.com`` erreichen kann." -#: ../system/objects/types.rst:123 -msgid "**🥵 This field can consume a lot of visual space**" -msgstr "**🥵 Dieses Feld kann viel Platz beanspruchen**" +#: ../system/integrations/i-doit.rst:2 +msgid "i-doit" +msgstr "i-doit" -#: ../system/objects/types.rst:125 +#: ../system/integrations/i-doit.rst:4 msgid "" -"Depending on where you use this field type, it may use a lot of visual space " -"if you provide a lot of text. This may be an issue to work with." +"`i-doit `_ is an open-source **configuration " +"management database** - in other words, a tool for keeping tabs on every " +"single piece of your physical and digital infrastructure, from network " +"equipment to virtual machines on down to the faceplates on your rack shelves " +"and more." msgstr "" -"Je nachdem, wo Sie diesen Feldtyp verwenden, kann er viel Platz " -"beanspruchen, wenn Sie viel Text eingeben. Das kann zu Problemen führen." - -#: ../system/objects/types.rst:130 -msgid "Default" -msgstr "Standard" +"`i-doit `_ ist eine quelloffene " +"**Konfigurationsverwaltungsdatenbank** - mit anderen Worten, ein Tool, mit " +"dem Sie jedes einzelne Teil Ihrer physischen und digitalen Infrastruktur im " +"Auge behalten können, von der Netzwerkausrüstung über virtuelle Maschinen " +"bis hin zu den Frontblenden Ihrer Rack-Regale und mehr." -#: ../system/objects/types.rst:129 +#: ../system/integrations/i-doit.rst:10 msgid "" -"The here provided text will be shown within the text area field or new data " -"sets." +"What's that got to do with Zammad? Well, if you used tickets to track issues " +"with all that hardware, you might start wishing there was a way they could " +"talk to each other." msgstr "" -"Der hier eingegebene Text wird im Textfeld oder in neuen Datensätzen " -"angezeigt." +"Was hat das mit Zammad zu tun? Wenn Sie mit Tickets Probleme mit Ihrer " +"Hardware verfolgen wünschen Sie sich vielleicht, dass es eine Möglichkeit " +"gibt, dass beide Systeme miteinander kommunizieren." -#: ../system/objects/types.rst:134 ../system/objects/types.rst:160 -msgid "Maxlength" -msgstr "Maximale Länge" +#: ../system/integrations/i-doit.rst:14 +msgid "Zammad gives you two:" +msgstr "Es gibt zwei Möglichkeiten:" -#: ../system/objects/types.rst:0 ../system/objects/types.rst:160 -msgid "You can pick the maximum length of the field." -msgstr "Sie können die maximale Länge des Feldes wählen." +#: ../system/integrations/i-doit.rst:17 +msgid "1. Add i-doit Links to Zammad Tickets" +msgstr "1. i-doit Links zu Zammad-Tickets hinzufügen" -#: ../system/objects/types.rst:0 -msgid "The default length of this object is ``500``." -msgstr "Die Standardlänge dieses Objekts ist ``500``." +#: ../system/integrations/i-doit.rst:20 ../system/integrations/i-doit.rst:80 +msgid "What Users See" +msgstr "Was die Nutzer sehen" -#: ../system/objects/types.rst:139 -msgid "Rows" -msgstr "Zeilen" +#: ../system/integrations/i-doit.rst:26 +msgid "i-doit integration in Zammad's ticket pane" +msgstr "Integration von i-doit im Zammad Ticketbereich" -#: ../system/objects/types.rst:0 +#: ../system/integrations/i-doit.rst:26 msgid "" -"Change the number of rows to dislay so that you can use only the space you " -"really need." +"The i-doit integration will appear under a new 🖨 tab in the ticket pane." msgstr "" -"Ändern Sie die Anzahl der anzuzeigenden Zeilen, damit nur der wirklich " -"benötigte Platz verwendet wird." - -#: ../system/objects/types.rst:0 -msgid "The default number of rows is ``4``." -msgstr "Die Standardanzahl der Zeilen ist ``4``." - -#: ../system/objects/types.rst:0 -msgid "Available settings for Textarea fields" -msgstr "Verfügbare Einstellungen für Textbereich-Felder" - -#: ../system/objects/types.rst:165 -msgid "Text field" -msgstr "Textfeld" +"Die i-doit-Integration wird in einem neuen 🖨 Tab im Ticketbereich angezeigt." -#: ../system/objects/types.rst:145 -msgid "Provides a text field (one line) and allows choosing a default value." +#: ../system/integrations/i-doit.rst:28 +msgid "" +"i-doit integration puts a new tab in Zammad's ticket pane where you can add " +"links to existing i-doit devices for easy reference. (See our :user-docs:" +"`user documentation ` to learn " +"how it works in practice)." msgstr "" -"Bietet ein Textfeld (eine Zeile) und ermöglicht die Auswahl eines " -"Standardwerts." +"Die i-doit-Integration fügt einen neuen Tab im Ticketbereich von Zammad ein, " +"in dem Sie Links zu vorhandenen i-doit-Geräten hinzufügen können, um sie " +"leichter zu finden. (Siehe unsere :user-docs:`Benutzerdokumentation ` für weitere Informationen zur " +"Handhabung in der Praxis)." -#: ../system/objects/types.rst:148 +#: ../system/integrations/i-doit.rst:36 ../system/integrations/i-doit.rst:93 +msgid "How to Set it Up" +msgstr "Einrichtung" + +#: ../system/integrations/i-doit.rst:38 msgid "" -"Defines the type of the input field. This allows e.g. your browser to ensure " -"that you provide the specific type." +"It requires i-doit's `API Add-on `_. Make sure to have it properly set up. Use the following setting:" msgstr "" -"Legt den Typ des Eingabefeldes fest. So kann z.B. Ihr Browser sicherstellen, " -"dass der richtige Typ eingeben wird." +"Das `API Add-on `_ von i-" +"doit ist dazu erforderlich. Stellen Sie sicher, dass es richtig eingerichtet " +"ist. Verwenden Sie die folgende Einstellung:" -#: ../system/objects/types.rst:152 -msgid "Currently available:" -msgstr "Derzeit verfügbar:" +#: ../system/integrations/i-doit.rst:42 +msgid "Active: ``Yes``" +msgstr "Aktiv: ``Ja``" -#: ../system/objects/types.rst:155 -msgid "Phone" -msgstr "Telefon" +#: ../system/integrations/i-doit.rst:43 +msgid "Enforce authentication by username and password: ``No``" +msgstr "Authentifizierung mit Benutzername und Passwort erzwingen: ``Nein``" -#: ../system/objects/types.rst:156 -msgid "Text" -msgstr "Text" +#: ../system/integrations/i-doit.rst:45 +msgid "" +"To set it up, enable the integration in the Zammad admin panel under " +"**System > Integrations > i-doit**:" +msgstr "" +"Um sie einzurichten, aktivieren Sie die Integration im Zammad-" +"Administrationsbereich unter **System > Integrationen > i-doit**:" -#: ../system/objects/types.rst:157 -msgid "Url *(URL fields disable link-template availability)*" -msgstr "Url *(URL-Felder deaktivieren die Verfügbarkeit von Link-Templates)*" +#: ../system/integrations/i-doit.rst:None +msgid "i-doit settings within the integration pages" +msgstr "i-doit-Einstellungen unter Integrationen" -#: ../system/objects/types.rst:0 -msgid "Available settings for Text fields" -msgstr "Verfügbare Einstellungen für Textfelder" +#: ../system/integrations/i-doit.rst:53 +msgid "The root URL of your i-doit installation." +msgstr "Die URL Ihrer i-doit-Installation." -#: ../system/objects/types.rst:174 -msgid "Single tree selection field" -msgstr "Einfach-Baumauswahl-Feld" +#: ../system/integrations/i-doit.rst:62 +msgid "API token" +msgstr "API-Token" -#: ../system/objects/types.rst:168 +#: ../system/integrations/i-doit.rst:56 msgid "" -"Provides a select-like field with up to 6 layers of options. Does not allow " -"setting a default value." +"Found in the i-doit admin panel under **Interfaces / external data > JSON-" +"RPC API > Common Settings**." msgstr "" -"Bietet ein Auswahl-Feld mit bis zu 6 Ebenen. Erlaubt keine Festlegung eines " -"Standardwerts." +"Zu finden im i-doit Admin Panel unter **Schnittstellen / externe Daten > " +"JSON-RPC API > Allgemeine Einstellungen**." -#: ../system/objects/types.rst:0 -msgid "Available settings for Tree Select fields" -msgstr "Verfügbare Einstellungen für Baumauswahlfelder" +#: ../system/integrations/i-doit.rst:0 +msgid "i-doit administration interface with API configuration" +msgstr "i-doit Verwaltungsoberfläche mit API-Konfiguration" -#: ../system/objects/types.rst:183 -msgid "Multiple tree selection field" -msgstr "Mehrfach-Baumauswahl-Feld" +#: ../system/integrations/i-doit.rst:67 +msgid "Client ID" +msgstr "Client-ID" -#: ../system/objects/types.rst:177 -msgid "" -"Provides a select-like field with up to 6 layers of options allowing the " -"selection of multiple values. Does not allow setting a default value." +#: ../system/integrations/i-doit.rst:65 +msgid "A unique name to identify Zammad within i-doit." msgstr "" -"Bietet ein Auswahl-Feld mit bis zu 6 Ebenen, das die Auswahl mehrerer Werte " -"ermöglicht. Erlaubt keine Festlegung eines Standardwerts." +"Ein eindeutiger Name zur Identifizierung von Zammad innerhalb von i-doit." -#: ../system/objects/types.rst:302 -msgid "External Data Source field" -msgstr "Externe Datenquelle Feld" +#: ../system/integrations/i-doit.rst:67 +msgid "(Zammad does not require you to enter a value here, but i-doit might!)" +msgstr "" +"(Zammad verlangt nicht, dass Sie hier einen Wert eingeben, aber i-doit " +"schon!)" -#: ../system/objects/types.rst:186 +#: ../system/integrations/i-doit.rst:70 msgid "" -"Provides a searchable field which fetches data from an external system. This " -"can be useful if you have data outside of Zammad and don't want to maintain " -"both data sources." +"Here you can decide if the certificate of your i-doit system has to be " +"verified or not. In case you are using custom certificates, please have a " +"look at :doc:`how to add them to Zammad `." msgstr "" -"Bietet ein durchsuchbares Feld, das Daten aus einem externen System abruft. " -"Dies kann nützlich sein, wenn Sie Daten außerhalb von Zammad haben und nicht " -"beide Datenquellen pflegen wollen." +"Hier können Sie festlegen, ob das Zertifikat Ihres i-doit-Systems überprüft " +"werden soll oder nicht. Falls Sie benutzerdefinierte Zertifikate verwenden, " +"sehen Sie sich bitte an, wie man diese :doc:`in Zammad hinterlegt `." -#: ../system/objects/types.rst:190 -msgid "The feature works as follows:" -msgstr "Das funktioniert wie folgt:" +#: ../system/integrations/i-doit.rst:77 +msgid "2. List / Create Zammad Tickets in i-doit" +msgstr "2. Zammad-Tickets in i-doit auflisten / erstellen" -#: ../system/objects/types.rst:192 -msgid "" -"Zammad sends a query with a search string (free text from agent or based on " -"a variable) in a pre-defined format (\"Search URL\") to an external system." -msgstr "" -"Zammad sendet eine Anfrage mit einem Suchstring (freier Text vom Agent oder " -"basierend auf einer Variable) in einem vordefinierten Format (\"Such URL\") " -"an ein externes System." +#: ../system/integrations/i-doit.rst:None +msgid "Zammad integration in i-doit's device view" +msgstr "Zammad-Integration in der Geräteansicht von i-doit" -#: ../system/objects/types.rst:195 +#: ../system/integrations/i-doit.rst:86 msgid "" -"This external system searches for matches and provides a response as a JSON " -"structure to Zammad." +"i-doit's ticket system integration gives you a way to see all the tickets " +"for a given device without ever leaving i-doit. (See our :user-docs:`user " +"documentation ` to learn how it " +"works in practice)." msgstr "" -"Dieses externe System sucht nach Übereinstimmungen und gibt eine Antwort in " -"Form einer JSON-Struktur an Zammad." +"Die Integration des Ticketsystems in i-doit bietet Ihnen die Möglichkeit, " +"alle Tickets für ein bestimmtes Gerät einzusehen, ohne i-doit zu verlassen " +"(siehe :user-docs:`i-doit Benutzerdokumentation `, um es im praktischen Einsatz zu sehen)." -#: ../system/objects/types.rst:197 +#: ../system/integrations/i-doit.rst:95 msgid "" -"Zammad just looks for the defined list and value keys, reads the content and " -"displays the value to the user. There is no search on Zammad side." +"Enable this integration in the i-doit admin panel under **Interfaces / " +"external data > Trouble Ticket System (TTS) > Configuration**:" msgstr "" -"Zammad sucht nur nach den definierten Suchergebnis-Schlüsseln und -Werten, " -"liest den Inhalt und zeigt dem Benutzer den Wert an. Es gibt keine Suche auf " -"der Seite von Zammad." +"Aktivieren Sie diese Integration im i-doit Admin Panel unter " +"**Schnittstellen / externe Daten > Trouble Ticket System (TTS) > " +"Konfiguration**:" -#: ../system/objects/types.rst:201 -msgid "" -"The usage of a PostgreSQL database for Zammad is required. In any other " -"case, Zammad will hide the external data source type and you are not able to " -"use it. If you want to use this feature, consider to :docs:`migrate your " -"database `." -msgstr "" -"Die Verwendung einer PostgreSQL-Datenbank für Zammad ist erforderlich. In " -"jedem anderen Fall wird Zammad den externen Datenquellentyp ausblenden und " -"Sie können ihn nicht verwenden. Wenn Sie diese Funktion nutzen möchten, " -"ziehen Sie bitte eine :docs:`Migration Ihrer Datenbank ` in Erwägung." +#: ../system/integrations/i-doit.rst:None +msgid "i-doit administration interface with TTS configuration" +msgstr "i-doit Verwaltungsoberfläche mit TTS-Konfiguration" -#: ../system/objects/types.rst:205 -msgid "Currently, only ``GET`` is supported as request method." -msgstr "Derzeit wird nur ``GET`` als Anfragemethode unterstützt." +#: ../system/integrations/i-doit.rst:104 +msgid "TTS-Type" +msgstr "TTS-Typ" -#: ../system/objects/types.rst:206 -msgid "" -"The data structure must be in JSON format and provide the objects in an " -"array." -msgstr "" -"Die Datenstruktur muss im JSON-Format sein und die Objekte in einem Array " -"bereitgestellt werden." +#: ../system/integrations/i-doit.rst:104 +msgid "``Zammad``" +msgstr "``Zammad``" -#: ../system/objects/types.rst:208 -msgid "" -"The endpoint for the external data source has to support search. On Zammad " -"side, there is no search/logic implemented; however, you can define the " -"output key and value based on the result(s) from the response (which " -"provides already filtered content based on the search)." -msgstr "" -"Der Endpunkt für die externe Datenquelle muss die Suche unterstützen. Auf " -"Zammad-Seite ist keine Suche/Logik implementiert; Sie können jedoch den " -"Suchergebnis-Schlüssel und -Wert auf der Grundlage des Ergebnisses der " -"Antwort definieren (die bereits gefilterte Inhalte auf der Grundlage der " -"Suche bereitstellt)." +#: ../system/integrations/i-doit.rst:115 +msgid "Username / Password" +msgstr "Benutzername/Passwort" -#: ../system/objects/types.rst:212 +#: ../system/integrations/i-doit.rst:107 +msgid "Login credentials for a Zammad agent." +msgstr "Anmeldedaten für einen Zammad-Agenten." + +#: ../system/integrations/i-doit.rst:109 msgid "" -"If you receive more results as expected, your external data source search " -"may not work properly or the structure of the URL is not correct. You should " -"get in touch with a responsible person from the external system." +"This agent must have **read permission** for all :doc:`groups ` that plan on using the i-doit integration." msgstr "" -"Wenn Sie mehr Ergebnisse als erwartet erhalten, funktioniert die Suche in " -"Ihrer externen Datenquelle möglicherweise nicht richtig oder die Struktur " -"der URL ist nicht korrekt. Sie sollten sich mit einer zuständigen Person des " -"externen Systems in Verbindung setzen." +"Dieser Agent muss **Leseberechtigung** für alle :doc:`Gruppen ` haben, die die i-doit-Integration nutzen wollen." -#: ../system/objects/types.rst:217 +#: ../system/integrations/i-doit.rst:113 msgid "" -"Please have a look :doc:`at our example `, where you can find a possible configuration for a public " -"dummy endpoint." +"You may even wish to create a dedicated agent account just for this " +"integration (otherwise, if the agent ever changes her password, you will " +"have to remember to update it here)." msgstr "" -"Werfen Sie einen Blick :doc:`auf unsere Beispielkonfiguration `, wo Sie eine mögliche Konfiguration " -"mit einen öffentlichen Dummy-Endpunkt finden." +"Möglicherweise möchten Sie sogar ein eigenes Konto für den Agenten " +"einrichten (andernfalls müssen Sie daran denken, das Passwort zu " +"aktualisieren, wenn der Agent sein Passwort ändert)." -#: ../system/objects/types.rst:0 -msgid "Available settings for external data source fields" -msgstr "Verfügbare Einstellungen für externe Datenquelle Felder" +#: ../system/integrations/i-doit.rst:117 +msgid "URL incl. protocol" +msgstr "URL mit Protokoll" -#: ../system/objects/types.rst:242 -msgid "Search URL" -msgstr "Such-URL" +#: ../system/integrations/i-doit.rst:118 +msgid "``https://your.zammad.domain``" +msgstr "``https://ihre.zammad.domain``" -#: ../system/objects/types.rst:227 +#: ../system/integrations/index.rst:2 +msgid "Integrations" +msgstr "Integrationen" + +#: ../system/integrations/index.rst:4 msgid "" -"Set your endpoint where Zammad fetches the data. Please make sure to include " -"a valid search :doc:`variable <../variables>` as an URL parameter. Example " -"for a free text search at user input: ``#{search.term}``" +"Zammad offers numerous integrations that add rich features to your instance." msgstr "" -"Legen Sie den Endpunkt fest, von dem Zammad die Daten abruft. Bitte stellen " -"Sie sicher, dass Sie eine gültige :doc:`Suchvariable <../variables>` als URL-" -"Parameter angeben. Beispiel für eine Freitextsuche bei Benutzereingabe: " -"``#{search.term}``" +"Zammad bietet zahlreiche Integrationen, die Ihre Instanz um umfangreiche " +"Funktionen erweitern." -#: ../system/objects/types.rst:232 -msgid "" -"If in doubt, ask the responsible person for the external data source how " -"they expect the strucuture of the URL." +#: ../system/integrations/index.rst:6 +msgid "We're still working on this part of our documentation, stay tight!" msgstr "" -"Fragen Sie im Zweifelsfall die für die externe Datenquelle verantwortliche " -"Person, wie die Struktur der URL aufgebaut sein muss." +"Wir arbeiten noch an diesem Teil unserer Dokumentation, bleiben Sie dran!" -#: ../system/objects/types.rst:236 +#: ../system/integrations/index.rst:10 +msgid "Integrations for Phone Systems" +msgstr "Integrationen für Telefonanlagen" + +#: ../system/integrations/index.rst:14 msgid "" -"Depending on your search variable, the preview might work or not. The reason " -"is that the context might not be available and it is no bug." +"Your VoIP provider or telephony system is not listed? Possibly your provider " +"supports Zammad by using the generic CTI - if you're unsure ask your " +"provider." msgstr "" -"Je nach Suchvariable kann die Vorschau ggf. nicht funktionieren. Der Grund " -"dafür ist, dass der Objektkontext in der Konfiguration möglicherweise nicht " -"verfügbar ist. Dies ist kein Fehler." +"Ihr VoIP-Anbieter oder Ihre Telefonanlage ist nicht aufgeführt? " +"Möglicherweise unterstützt Ihr Anbieter Zammad durch die Verwendung der " +"generischen CTI - wenn Sie unsicher sind, fragen Sie Ihren Anbieter." -#: ../system/objects/types.rst:239 +#: ../system/integrations/index.rst:18 msgid "" -"Please also make sure to use a variable which is available in your object " -"context. For example you won't be able to search for a ticket in a user " -"object context." +"Provider does not support Zammad? Consider creating a `feature request in " +"the Zammad Community `_." msgstr "" -"Achten Sie bitte auch darauf, dass Sie eine Variable verwenden, die in Ihrem " -"Objektkontext verfügbar ist. Zum Beispiel können Sie in einem " -"Benutzerobjektkontext nicht nach einem Ticket suchen." - -#: ../system/objects/types.rst:252 -msgid "SSL Verification" -msgstr "SSL-Verizifierung" +"Der Anbieter unterstützt Zammad nicht? Sie können gerne ein `Feature Request " +"in der Zammad Community `_ erstellen." -#: ../system/objects/types.rst:245 -msgid "Here you can switch the SSL verification to no." -msgstr "Hier können Sie die SSL-Verifizierung auf nein stellen." +#: ../system/integrations/index.rst:31 +msgid "Integrations for Authentication and Customers" +msgstr "Integrationen für Authentifizierung und Kunden" -#: ../system/objects/types.rst:249 -msgid "" -"If your external data source system is using self signed certificates, " -"please have a look :doc:`here ` for " -"further information about how to handle them in Zammad, so you can keep the " -"SSL verification activated." -msgstr "" -"Wenn Ihr externes Datenquellensystem selbstsignierte Zertifikate verwendet, " -"sehen Sie sich bitte :doc:`SSL Zertifikate ` an. Dort finden Sie weitere Informationen darüber, wie diese " -"in Zammad hinterlegt werden können, damit Sie die SSL-Verifizierung " -"aktiviert lassen können." +#: ../system/integrations/index.rst:44 +msgid "Integrations for Monitoring Systems" +msgstr "Integrationen für Monitoring-Systeme" -#: ../system/objects/types.rst:258 -msgid "HTTP Authentication" -msgstr "HTTP-Authentifizierung" +#: ../system/integrations/index.rst:46 +msgid "This section currently misses the following integrations:" +msgstr "In diesem Abschnitt fehlen derzeit die folgenden Integrationen:" -#: ../system/objects/types.rst:255 -msgid "" -"If your external data source requires an authentication, you can set it " -"here. You can leave it empty or choose between *Basic Authentication* or " -"*Authentication Token* (selecting one of the two methods leads to additional " -"fields where you can enter your credentials/token)." -msgstr "" -"Wenn Ihre externe Datenquelle eine Authentifizierung erfordert, können Sie " -"diese hier hinterlegen. Sie können es leer lassen oder zwischen *Basis " -"Authentifizierung* oder *Token Authentifizierung* wählen (die Auswahl einer " -"der beiden Methoden führt zu zusätzlichen Feldern, in die Sie Ihre " -"Anmeldedaten/Token eingeben können)." +#: ../system/integrations/index.rst:48 +msgid "Icinga" +msgstr "Icinga" -#: ../system/objects/types.rst:265 -msgid "Search result list key" -msgstr "Schlüssel der Suchergebnisliste" +#: ../system/integrations/index.rst:49 +msgid "Monit" +msgstr "Monit" -#: ../system/objects/types.rst:261 -msgid "" -"Defines the level in the JSON structure which provides the list with search " -"results. You can leave it empty, if the data is already provided as an " -"array. If you have to go deeper in the structure, you can provide a path " -"with ``.`` as separators, e.g. ``key.subkey.sub-sub-key``." -msgstr "" -"Definiert die Ebene in der JSON-Struktur, die die Liste mit den " -"Suchergebnissen liefert. Sie können es leer lassen, wenn die Daten bereits " -"als Array bereitgestellt werden. Wenn Sie tiefer in die Struktur gehen " -"müssen, können Sie einen Pfad mit ``.`` als Trennzeichen angeben, z.B. ``key." -"subkey.sub-sub-key``." +#: ../system/integrations/index.rst:50 +msgid "Nagios" +msgstr "Nagios" -#: ../system/objects/types.rst:271 -msgid "Search result value key" -msgstr "Schlüssel Suchergebnis-Wert" +#: ../system/integrations/index.rst:60 +msgid "Integrations for Issue Trackers" +msgstr "Integrationen für Issue-Tracker" -#: ../system/objects/types.rst:268 +#: ../system/integrations/index.rst:70 +msgid "Other Integrations" +msgstr "Andere Integrationen" + +#: ../system/integrations/index.rst:72 msgid "" -"Defines the attribute in the structure in which your external data source " -"provides the *value* for your data. An example would be a product *number*. " -"If you have to go deeper in the structure, you can provide a path with ``.`` " -"as separators, e.g. ``key.subkey.sub-sub-key``." +"This section will hold any other integration that can't be grouped up (yet)." msgstr "" -"Definiert das Attribut in der Struktur, in der Ihre externe Datenquelle den " -"*Wert* für Ihre Daten liefert. Ein Beispiel wäre eine Produkt *Nummer*. Wenn " -"Sie tiefer in die Struktur eindringen müssen, können Sie einen Pfad mit ``." -"`` als Trennzeichen angeben, z.B. ``key.subkey.sub-sub-key``." +"In diesem Abschnitt werden alle anderen Integrationen aufgeführt, die (noch) " +"nicht in Gruppen zusammengefasst werden können." -#: ../system/objects/types.rst:277 -msgid "Search result label key" -msgstr "Schlüssel der Suchergebnisbezeichnung" +#: ../system/integrations/ldap/index.rst:2 +msgid "LDAP / Active Directory" +msgstr "LDAP/Active Directory" -#: ../system/objects/types.rst:274 +#: ../system/integrations/ldap/index.rst:4 msgid "" -"Defines the attribute in the structure in which your external data source " -"provides the *label* for your data. An example would be a product *name*. If " -"you have to go deeper in the structure, you can provide a path with ``.`` as " -"separators, e.g. ``key.subkey.sub-sub-key``." +"Zammad comes with a powerful LDAP integration that allows you to have a " +"single source of truth. By this you reduce the number of login credentials " +"your user has to remember." msgstr "" -"Definiert das Attribut in der Struktur, in der Ihre externe Datenquelle die " -"*Bezeichnung* für Ihre Daten bereitstellt. Ein Beispiel wäre ein Produkt " -"*Name*. Wenn Sie tiefer in die Struktur eindringen müssen, können Sie einen " -"Pfad mit ``.`` als Trennzeichen angeben, z.B. ``key.subkey.sub-sub-key``." +"Zammad verfügt über eine leistungsstarke LDAP-Integration, die es Ihnen " +"ermöglicht, eine einzige Datenquelle zu haben. Auf diese Weise reduzieren " +"Sie die Anzahl der Anmeldeinformationen, die sich Ihre Benutzer merken " +"müssen." -#: ../system/objects/types.rst:280 +#: ../system/integrations/ldap/index.rst:10 msgid "" -"In the preview area, you can find the following items (depending on your " -"configuration above):" +"The LDAP source is also a perfect candidate for Zammad's :docs:`Kerberos " +"Single Sign-On ` but also works as addition " +"to other :doc:`/settings/security/third-party`." msgstr "" -"Im Vorschaubereich finden Sie die folgenden Elemente (abhängig von " -"bisheriger Konfiguration):" +"Die LDAP-Quelle ist auch ein perfekter Kandidat für Zammads :docs:`Kerberos " +"Single Sign-On `, funktioniert aber auch als " +"Ergänzung zu anderen :doc:`/settings/security/third-party`." -#: ../system/objects/types.rst:283 -msgid "" -"**Error/hint message** (only if configuration is not complete): Zammad tells " -"you, if there is a problem and what you should change in your configuration." -msgstr "" -"**Fehler-/Hinweismeldung** (nur wenn die Konfiguration nicht vollständig " -"ist): Zammad sagt Ihnen, ob es ein Problem gibt und was Sie an Ihrer " -"Konfiguration ändern sollten." +#: ../system/integrations/ldap/index.rst:None +msgid "Zammands LDAP management page" +msgstr "Zammands LDAP-Einstellungsseite" -#: ../system/objects/types.rst:286 -msgid "" -"**Search field**: search for an existing attribute in the data source to get " -"a preview. This is required for the fields below to show up." -msgstr "" -"**Suchfeld**: Suchen Sie nach einem vorhandenen Attribut in der Datenquelle, " -"um eine Vorschau zu erhalten. Dies ist erforderlich, damit die nachstehenden " -"Felder angezeigt werden können." +#: ../system/integrations/ldap/index.rst:25 +msgid "📝 :doc:`manage`" +msgstr "📝 :doc:`manage`" -#: ../system/objects/types.rst:288 -msgid "" -"**Search result response** (only if configuration is not complete): here you " -"can find a syntax highlighted JSON preview of the response, based on the " -"search term you entered." +#: ../system/integrations/ldap/index.rst:25 +msgid "Add, modify, remove or re-arrange your LDAP-Sources as needed." msgstr "" -"**Antwort Suchergebnis** (nur wenn die Konfiguration nicht vollständig ist): " -"Hier finden Sie eine syntaktisch hervorgehobene JSON-Vorschau der Antwort, " -"die auf dem eingegebenen Suchbegriff basiert." +"Sie können Ihre LDAP-Quellen nach Bedarf hinzufügen, ändern, entfernen oder " +"neu anordnen." -#: ../system/objects/types.rst:291 -msgid "" -"**Search result list** (only if *search result list key* is properly set): " -"output of the structure under the configured *search result list key*." +#: ../system/integrations/ldap/index.rst:30 +msgid "Before you continue, please note the following limitations." msgstr "" -"**Suchergebnisliste** (nur wenn *Suchergebnislisten-Schlüssel* richtig " -"gesetzt ist): Ausgabe der Struktur unter dem konfigurierten " -"*Suchergebnislisten-Schlüssel*." +"Bevor Sie fortfahren, beachten Sie bitte die folgenden Einschränkungen." -#: ../system/objects/types.rst:294 +#: ../system/integrations/ldap/index.rst:32 +msgid "Mapping / Synchronizing organizations is not possible" +msgstr "Mapping / Synchronisation von Organisationen ist nicht möglich" + +#: ../system/integrations/ldap/index.rst:36 msgid "" -"**Preview table** (when fully configured): Zammad shows you a table which " -"includes the found items based on the search string (value, label and " -"optional link). You can use this preview if you don't have the complete data " -"structure of the external system in mind." +"You may want to consider using domain based assignments to overcome this " +"issue. Learn more on :doc:`/manage/organizations/index`." msgstr "" -"**Vorschau-Tabelle** (wenn vollständig konfiguriert): Zammad zeigt Ihnen " -"eine Tabelle an, die die gefundenen Elemente auf der Grundlage des " -"Suchstrings (Wert, Bezeichnung und optionaler Link) enthält. Sie können " -"diese Vorschau verwenden, wenn Sie nicht die komplette Datenstruktur des " -"externen Systems im Kopf haben." +"Um dieses Problem zu umgehen können Sie die Verwendung der domainbasierten " +"Zuweisungen in Betracht ziehen. Erfahren Sie mehr unter :doc:`/manage/" +"organizations/index`." -#: ../system/objects/types.rst:299 +#: ../system/integrations/ldap/index.rst:39 msgid "" -"An example of a configured external data source field from agent perspective:" +"Zammad's LDAP sync is one way. Editing user settings or permissions may be " +"overwritten upon the next sync depending on your configuration." msgstr "" -"Ein Beispiel für ein eigenes Feld auf Ticketebene vom Typ externe " -"Datenquelle aus der Sicht eines Agenten:" +"Die LDAP-Synchronisierung von Zammad funktioniert nur in eine Richtung. Die " +"Bearbeitung von Benutzereinstellungen oder Berechtigungen kann bei der " +"nächsten Synchronisierung überschrieben werden, abhängig von Ihrer " +"Konfiguration." -#: ../system/objects/types.rst:0 -msgid "Screencast showing the search for a product in a ticket" -msgstr "Screencast zeigt die Suche nach einem Produkt in einem Ticket" +#: ../system/integrations/ldap/index.rst:41 +msgid "Nested groups are not supported." +msgstr "Verschachtelte Gruppen werden nicht unterstützt." -#: ../system/objects/types.rst:307 -msgid "URL fields (Link-Template)" -msgstr "URL-Felder (Link-Template)" +#: ../system/integrations/ldap/index.rst:42 +msgid "Synchronizing user avatars from LDAP is not supported." +msgstr "" +"Die Synchronisierung von Benutzeravataren aus LDAP wird nicht unterstützt." -#: ../system/objects/types.rst:311 -msgid "" -"This function is restricted to Text, Select and External data source types " -"only." +#: ../system/integrations/ldap/index.rst:43 +msgid "Unlike user filters, group filters cannot be changed." msgstr "" -"Diese Funktion ist nur auf die Feldtypen Text-, Auswahl- und Externe " -"Datenquelle beschränkt." +"Im Gegensatz zu den Benutzerfiltern können die Gruppenfilter nicht geändert " +"werden." -#: ../system/objects/types.rst:314 +#: ../system/integrations/ldap/index.rst:44 msgid "" -"Link-Templates are an amazing way to dynamically generate URLs. They allow " -"you to integrate other systems better without having to manually copy data " -"from Zammad if possible." +"When a user originates from an LDAP server, Zammad will try to verify the " +"login credentials against LDAP first - if this fails Zammad will check its " +"local database." msgstr "" -"Link-Templates sind eine hervorragende Möglichkeit, URLs dynamisch zu " -"erzeugen. Sie ermöglichen es Ihnen, andere Systeme zu integrieren, ohne " -"Daten manuell aus Zammad kopieren zu müssen." +"Wenn ein Benutzer von einem LDAP-Server stammt, versucht Zammad zunächst, " +"die Anmeldedaten anhand von LDAP zu überprüfen - wenn dies fehlschlägt, " +"prüft Zammad seine lokale Datenbank." -#: ../system/objects/types.rst:320 +#: ../system/integrations/ldap/index.rst:50 msgid "" -"Another great way of communicating with another system may be Zammad's :doc:" -"`Webhooks `." +"Users can have local passwords even if they're LDAP users! You can learn " +"more about user accounts in general on :doc:`/manage/users/index`." msgstr "" -"Eine weitere gute Möglichkeit, mit anderen Systemen zu kommunizieren, sind " -"die :doc:`Webhooks ` von Zammad." +"Benutzer können lokale Passwörter haben, auch wenn sie LDAP-Benutzer sind! " +"Sie können mehr über Benutzerkonten im Allgemeinen unter :doc:`/manage/users/" +"index` erfahren." -#: ../system/objects/types.rst:323 +#: ../system/integrations/ldap/index.rst:54 msgid "" -"After filling a link-template enabled field, an URL icon will appear on its " -"right. Clicking on the icon opens a new tab." -msgstr "" -"Nach dem Ausfüllen eines Feldes, das mit einem Link-Template versehen ist, " -"erscheint rechts davon ein Symbol. Wenn Sie auf das Symbol klicken, wird ein " -"neuer Tab im Browser geöffnet." - -#: ../system/objects/types.rst:328 -msgid "" -"Even though Zammad displays the link template within object edit and create " -"screens, the function is optional. It's only active if you populate the " -"field." +"When several LDAP sources contain the same user (meaning the same email " +"address), the user in question will be updated with every source configured. " +"*The last LDAP source will win.*" msgstr "" -"Obwohl Zammad das Link-Template in den Ansichten zum Bearbeiten und " -"Erstellen von Objekten anzeigt, ist die Funktion optional. Sie ist nur " -"aktiv, wenn Sie das Feld ausfüllen." +"Wenn mehrere LDAP-Quellen denselben Benutzer (d.h. dieselbe E-Mail-Adresse) " +"enthalten, wird der betreffende Benutzer aus jeder konfigurierten Quelle " +"aktualisiert. *Die letzte LDAP-Quelle gewinnt schlussendlich.*" -#: ../system/objects/types.rst:333 +#: ../system/integrations/ldap/index.rst:58 msgid "" -"What's the difference between URL and text fields with link template...?!" -msgstr "Was ist der Unterschied zwischen URL und Textfeldern mit Linkvorlage?" +"This is subject to change with `Issue 4109 `_ in the future." +msgstr "" +"Dies kann sich mit `Issue 4109 `_ in Zukunft ändern." -#: ../system/objects/types.rst:335 +#: ../system/integrations/ldap/index.rst:60 msgid "" -"Both fields have different use cases. Use ``text`` type text fields when " -"ever you have a *static* url that requires dynamic parameters. If you " -"require a drag & drop like field that you can put in any URL, use ``URL`` " -"type text fields." +"Synchronization statistics currently affect *all* configured LDAP sources. " +"This also applies for newly added or updated sources." msgstr "" -"Beide Felder haben unterschiedliche Verwendungszwecke. Verwenden Sie Felder " -"vom Typ ``Text``, wenn Sie eine *statische* URL haben, die dynamische " -"Parameter erfordert. Wenn Sie ein Feld benötigen, in das Sie eine beliebige " -"statische URL einfügen können, verwenden Sie Textfelder vom Typ ``URL``." +"Die Synchronisationsstatistiken betreffen derzeit *alle* konfigurierten LDAP-" +"Quellen. Dies gilt auch für neu hinzugefügte oder aktualisierte Quellen." -#: ../system/objects/types.rst:340 +#: ../system/integrations/ldap/index.rst:63 msgid "" -"The difference is easier to spot when comparing the fields directly, below " -"screencast shows the result - the dynamic approach uses existing values in " -"the moment of updating to built the URL - e.g. ``https://google.com/search?" -"q=cookies`` - while the URL approach uses the actual URL of the field - e.g. " -"``https://zammad.com``." +"This is subject to change with `Issue 4108 `_ in the future." msgstr "" -"Der Unterschied ist leichter zu erkennen, wenn man die Felder direkt " -"vergleicht. Der folgende Screencast zeigt das Ergebnis - der dynamische " -"Ansatz verwendet die vorhandenen Werte im Moment der Aktualisierung, um die " -"URL zu bilden - z.B. ``https://google.com/search?q=cookies`` - während der " -"URL-Ansatz die aktuelle statische URL des Feldes verwendet - z.B. ``https://" -"zammad.com``." +"Dies kann sich mit `Issue 4108 `_ in Zukunft ändern." -#: ../system/objects/types.rst:None +#: ../system/integrations/ldap/index.rst:65 msgid "" -"Screencast showing the differents in between URL and text type fields with " -"actual values" +"Zammad currently has limited fallback server support. You can workaround " +"this by providing several sources - however, ensure to have the exact same " +"configuration on your fallback." msgstr "" -"Screencast mit den Unterschieden zwischen URL- und Textfeldern mit aktuellen " -"Werten" - -#: ../system/objects/types.rst:352 -msgid "How does this work...?!" -msgstr "Wie funktioniert das?" +"Zammad bietet derzeit nur begrenzte Unterstützung für Fallback-Server. Sie " +"können dies umgehen, indem Sie mehrere Quellen zur Verfügung stellen - " +"stellen Sie jedoch sicher, dass Sie auf Ihrem Fallback-Server genau dieselbe " +"Konfiguration haben." -#: ../system/objects/types.rst:354 +#: ../system/integrations/ldap/index.rst:69 msgid "" -"As an example, let's say you have an attribute called ``amazing_attribute`` " -"and you want to open a google search directly with the input from that field." +"This is subject to improve with `Issue 4107 `_ in the future." msgstr "" -"Nehmen wir an, Sie haben ein Attribut namens ``amazing_attribute`` und " -"möchten eine Google-Suche direkt mit Inhalt aus diesem Feld öffnen." +"Dies kann zukünftig mit `Issue 4107 `_ verbessert werden." -#: ../system/objects/types.rst:357 +#: ../system/integrations/ldap/index.rst:76 msgid "" -"Providing the link-template field below allows you to do so: ``https://www." -"google.com/search?q=#{ticket.amazing_attribute}``" +"This section holds all requests Zammad handled for all LDAP sources. These " +"entries can either contain synchronization information or logins " +"(authentication attempts via Zammad's login interface)." msgstr "" -"Mit dem unten stehenden Link-Template-Feld können Sie dies tun: ``https://" -"www.google.com/search?q=#{ticket.amazing_attribute}``" +"Dieser Abschnitt enthält alle Anfragen an alle LDAP-Quellen. Diese Einträge " +"können entweder Synchronisationsinformationen oder Logins " +"(Authentifizierungsversuche über die Login-Schnittstelle von Zammad) " +"enthalten." -#: ../system/objects/types.rst:362 +#: ../system/integrations/ldap/index.rst:80 msgid "" -"You can use any :doc:`Zammad variable ` as long as it's " -"available in the moment you need it." +"By clicking on any request, Zammad will provide even more information. The " +"provided information can be useful when something does not work as expected." msgstr "" -"Sie können jede :doc:`Zammad-Variable ` verwenden, " -"solange sie in dem Moment, in dem Sie sie brauchen, verfügbar ist." +"Wenn Sie auf eine Anfrage klicken, stellt Zammad weitere Informationen zur " +"Verfügung. Die bereitgestellten Informationen können nützlich sein, wenn " +"etwas nicht wie erwartet funktioniert." -#: ../system/objects/types.rst:365 +#: ../system/integrations/ldap/index.rst:85 msgid "" -"As a result, you are redirected to Google with a search for the value of the " -"attribute, if you click on the button in the ticket (as you can see in the " -"screencast above)." +"Especially a LDAP synchronization can cause many log entries. The web " +"interface will always limit the number of shown entries to the last 50 " +"entries." msgstr "" -"Als Ergebnis werden Sie zu Google mit einer Suche nach dem Inhalt des " -"Attributs weitergeleitet, wenn Sie auf die Schaltfläche im Ticket klicken " -"(wie Sie im Screencast oben sehen können)." +"LDAP-Synchronisationen können viele Log-Einträge verursachen. Das " +"Webinterface beschränkt die Anzahl der angezeigten Einträge immer auf die " +"letzten 50 Einträge." -#: ../system/packages.rst:2 -msgid "Packages" -msgstr "Pakete" +#: ../system/integrations/ldap/index.rst:None +msgid "" +"Screencast showing LDAP integration log entries and a detail view on\n" +"an entry." +msgstr "Screencast mit LDAP-Protokollen und Detailansicht eines Eintrags." -#: ../system/packages.rst:4 -msgid "That's the package management-area." -msgstr "Das ist der Bereich der Paketverwaltung." +#: ../system/integrations/ldap/manage.rst:2 +msgid "Manage LDAP-Sources" +msgstr "Verwalten von LDAP-Quellen" -#: ../system/packages.rst:6 -msgid "Individual add-ons for Zammad can be installed and managed here." +#: ../system/integrations/ldap/manage.rst:6 +msgid "" +"Please keep in mind all current limitations for the LDAP synchronization. " +"This will help to understand scopes of the following operations better." msgstr "" -"Individuelle Add-ons für Zammad können hier installiert und verwaltet werden." +"Bitte beachten Sie alle aktuellen Einschränkungen für die LDAP-" +"Synchronisation. Dies wird Ihnen helfen, die folgenden Operationen besser zu " +"verstehen." -#: ../system/sessions.rst:2 -msgid "Sessions" -msgstr "Sitzungen" +#: ../system/integrations/ldap/manage.rst:65 +msgid "Add new source" +msgstr "Neue Quelle hinzufügen" -#: ../system/sessions.rst:4 +#: ../system/integrations/ldap/manage.rst:10 msgid "" -"Sessions management allows reviewing currently known user sessions and " -"allows to end these. The session timeout is affected by :ref:" -"`security_session_timeout` configurations from security settings." +"Using the *New Source* button allows you to add new LDAP sources to your " +"installation. You're not limited in the number of sources, however, keep in " +"mind that many sources will also take more time to synchronize." msgstr "" -"Die Sitzungsverwaltung ermöglicht die Überprüfung der aktuell bekannten " -"Benutzer-Sitzungen und deren Beendigung. Der Sitzungs-Timeout wird von der :" -"ref:`security_session_timeout` Konfiguration beeinflusst." - -#: ../system/sessions.rst:None -msgid "Screenshot showing Zammad's session management" -msgstr "Screenshot der Sitzungsverwaltung von Zammad" - -#: ../system/sessions.rst:13 -msgid "Zammad will provide the following information:" -msgstr "Zammad stellt die folgenden Informationen zur Verfügung:" +"Über die Schaltfläche *Neue Quelle* können Sie neue LDAP-Quellen zu Ihrer " +"Installation hinzufügen. Sie sind in der Anzahl der Quellen nicht " +"beschränkt, bedenken Sie jedoch, dass viele Quellen auch mehr Zeit für die " +"Synchronisierung benötigen." -#: ../system/sessions.rst:16 +#: ../system/integrations/ldap/manage.rst:14 msgid "" -"The user account this session entry belongs to. It can be normal if a user " -"has several sessions in the list. This can be due to changed browser " -"information or if you use e.g. single sign on methods where the user does " -"not use the log off button." +"You can choose between different encryption types, namely *SSL* and " +"*STARTTLS* or none of them (\"*No SSL*\"). If you choose *SSL* or " +"*STARTTLS*, Zammad will display an additional *SSL verification* option that " +"allows you to disable the verification, e.g. for self-signed SSL " +"certificates. You can also tell Zammad to use a different port by appending " +"``:`` to your hostname/IP." msgstr "" -"Das Benutzerkonto, zu dem dieser Sitzungseintrag gehört. Es kann vorkommen, " -"dass ein Benutzer mehrere Sitzungen in der Liste hat. Dies kann auf " -"geänderte Browser-Informationen zurückzuführen sein oder wenn Sie z.B. " -"Single-Sign-On-Methoden verwenden, bei denen der Benutzer die " -"Abmeldefunktion nicht benutzt." - -#: ../system/sessions.rst:22 -msgid "Browser" -msgstr "Browser" - -#: ../system/sessions.rst:22 -msgid "The browser agent communicated to Zammad." -msgstr "Der Browser-Agent, der an Zammad kommuniziert wurde." - -#: ../system/sessions.rst:40 -msgid "Location" -msgstr "Ort" +"Sie können zwischen verschiedenen Verschlüsselungsarten wählen, nämlich " +"*SSL* und *STARTTLS* oder keine von beiden (\"*kein SSL*\"). Wenn Sie sich " +"für *SSL* oder *STARTTLS* entscheiden, zeigt Zammad eine zusätzliche Option " +"*SSL-Verifizierung* an, mit der Sie die Überprüfung deaktivieren können, z." +"B. für selbst signierte SSL-Zertifikate. Sie können Zammad auch anweisen, " +"einen anderen Port zu verwenden, indem Sie ``:`` an Ihren " +"Hostnamen/IP anhängen." -#: ../system/sessions.rst:25 +#: ../system/integrations/ldap/manage.rst:0 msgid "" -"The anticipated location based on the users IP address. Depending on the IP " -"address the result shown may differ. This option depends on :doc:`/settings/" -"system/services`." +"Screenshot of configuring a new LDAP source with SSL encryption and SSL " +"verification" msgstr "" -"Der ungefähre Standort basiert auf der IP-Adresse des Nutzers. Je nach IP-" -"Adresse kann das angezeigte Ergebnis stark abweichen. Diese Option ist " -"abhängig von :doc:`/settings/system/services`." - -#: ../system/sessions.rst:29 -msgid "The following information can be shown:" -msgstr "Die folgenden Informationen können angezeigt werden:" +"Screenshot der Konfiguration einer neuen LDAP-Quelle mit SSL-Verschlüsselung " +"und SSL-Verifizierung" -#: ../system/sessions.rst:33 -msgid "IP address" -msgstr "IP-Adresse" +#: ../system/integrations/ldap/manage.rst:26 +msgid "" +"New Source with SSL transport security enabled and certificate verification" +msgstr "" +"Neue Quelle mit aktivierter SSL-Verschlüsselung und Zertifikatsüberprüfung" -#: ../system/sessions.rst:32 +#: ../system/integrations/ldap/manage.rst:30 msgid "" -"Either if you set *Geo IP services* to inactive or you're using internal IP " -"address which do not provide location information." +"Using an user filter can be a good idea if you only require a small subset " +"of your LDAP users in Zammad." msgstr "" -"Entweder haben Sie den *Geo-IP-Service* auf inaktiv gesetzt oder Sie " -"verwenden eine interne IP-Adresse, die keine Standortinformationen liefert." +"Die Verwendung eines Benutzerfilters kann eine gute Idee sein, wenn Sie nur " +"eine kleine Teilmenge Ihrer LDAP-Benutzer in Zammad benötigen." -#: ../system/sessions.rst:40 -msgid "Country (or Country + City)" -msgstr "Land (oder Land + Stadt)" +#: ../system/integrations/ldap/manage.rst:42 +msgid "This especially affects inactive users" +msgstr "Das betrifft vor allem inaktive Nutzer" -#: ../system/sessions.rst:36 +#: ../system/integrations/ldap/manage.rst:34 msgid "" -"If *Geo IP services* is enabled only. Depends on how detailed the available " -"IP address information are." +"As every LDAP behaves differently on which attributes and how they are set, " +"Zammad doesn't care about any flags." msgstr "" -"Nur wenn *Geo-IP-Service* aktiviert ist. Hängt davon ab, wie detailliert die " -"verfügbaren IP-Adressinformationen sind." +"Da sich jedes LDAP anders verhält, welche Attribute wie gesetzt werden, " +"kümmert sich Zammad nicht um irgendwelche Flags." -#: ../system/sessions.rst:39 +#: ../system/integrations/ldap/manage.rst:37 msgid "" -"Be aware that results can be inaccurate - this technically is not an error." +"Users that no longer are returned by your LDAP source will automatically be " +"set to inactive. Zammad assumes that the user was deactivated." msgstr "" -"Beachten Sie, dass die Ergebnisse ungenau sein können - dies ist technisch " -"gesehen kein Fehler." - -#: ../system/sessions.rst:43 -msgid "Age" -msgstr "Alter" - -#: ../system/sessions.rst:43 -msgid "Provides the time when the session initially has been created." -msgstr "Gibt die Zeit an, zu der die Sitzung ursprünglich erstellt wurde." - -#: ../system/sessions.rst:50 -msgid "Update" -msgstr "Aktualisierung" +"Benutzer, die nicht mehr von Ihrer LDAP-Quelle zurückgegeben werden, werden " +"automatisch auf inaktiv gesetzt. Zammad geht davon aus, dass der Benutzer " +"deaktiviert wurde." -#: ../system/sessions.rst:46 +#: ../system/integrations/ldap/manage.rst:41 msgid "" -"Provides the time the user used this session to open Zammad. This timestamp " -"is only updated if the user e.g. reloads, not during normal work on tickets." +"Users will never be removed automatically! If you want to remove obsolete " +"users, use :doc:`/system/data-privacy`." msgstr "" -"Gibt den Zeitpunkt an, zu dem der Benutzer diese Sitzung verwendet hat, um " -"Zammad zu öffnen. Dieser Zeitstempel wird nur aktualisiert, wenn der " -"Benutzer z.B. die Seite neu lädt, nicht während der normalen Arbeit an " -"Tickets." +"Benutzer werden niemals automatisch entfernt! Wenn Sie veraltete Benutzer " +"entfernen wollen, verwenden Sie :doc:`/system/data-privacy`." -#: ../system/sessions.rst:50 -msgid "This timestamp is being used for the session timeout." -msgstr "Dieser Zeitstempel wird für den Timeout der Sitzung verwendet." +#: ../system/integrations/ldap/manage.rst:46 +msgid "Active Directory admins" +msgstr "Active Directory-Administratoren" -#: ../system/sessions.rst:53 +#: ../system/integrations/ldap/manage.rst:45 msgid "" -"Use the delete button to remove a single session on behalf of your user." +"Active Directories are quite specific on how to filter for active users only " +"- please see the `Microsoft documentation `_ for more " +"information." msgstr "" -"Verwenden Sie die Schaltfläche \"Löschen\", um eine einzelne Sitzung Ihres " -"Benutzers zu entfernen." - -#: ../system/subscription/billing.rst:2 -msgid "Billing" -msgstr "Abrechnungen" +"Active Directories sind sehr spezifisch, was die Filterung nach aktiven " +"Benutzern angeht - weitere Informationen finden Sie in der `Microsoft " +"Documentation `_." -#: ../system/subscription/billing.rst:4 +#: ../system/integrations/ldap/manage.rst:51 msgid "" -"Within the billing tab you can control all billing relevant information like " -"invoices, billing address and the option to cancel your subscription." +"*Do not* manually write pathes of either LDAP attributes or groups. If " +"Zammad does not display them, it either cannot find them or you have a lot " +"of users that don't have the attributes populated." msgstr "" -"Auf der Registerkarte \"Abrechnung\" können Sie alle abrechnungsrelevanten " -"Informationen wie Rechnungen, Rechnungsadresse und die Option zur Kündigung " -"Ihres Abonnements kontrollieren." - -#: ../system/subscription/billing.rst:33 -msgid "Billing information" -msgstr "Informationen zur Abrechnung" +"Editieren Sie *keine* Pfade von LDAP-Attributen oder Gruppen manuell. Wenn " +"Zammad sie nicht anzeigt, kann es sie entweder nicht finden oder Sie haben " +"viele Benutzer, bei denen die Attribute nicht ausgefüllt sind." -#: ../system/subscription/billing.rst:8 +#: ../system/integrations/ldap/manage.rst:55 msgid "" -"All adjusted billing information below only affect future invoices. If your " -"invoice was issued wrong, please contact `our sales team `_." +"Zammad will always only return attributes that are filled - this reduces the " +"returned list of attributes greatly." msgstr "" -"Alle unten aufgeführten Rechnungsinformationen betreffen nur zukünftige " -"Rechnungen. Sollte eine Rechnung falsch ausgestellt worden sein, wenden Sie " -"sich bitte an `unser Sales-Team `_." +"Zammad wird immer nur Attribute zurückgeben, die ausgefüllt sind - dies " +"reduziert die Liste der zurückgegebenen Attribute erheblich." -#: ../system/subscription/billing.rst:14 -msgid "Billing address" -msgstr "Rechnungsadresse" +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing how to add a new LDAP source" +msgstr "Screencast zeigt, wie eine neue LDAP-Quelle hinzugefügt wird" -#: ../system/subscription/billing.rst:13 +#: ../system/integrations/ldap/manage.rst:63 msgid "" -"Provide your company address here, make sure to include the companies name " -"in case required. This address will be referenced on your invoice." +"If your LDAP system doesn't allow anonymous bind, Zammad detects it and " +"provides you an editable \"Base DN\" *text* field instead of a prefilled " +"*select* field." msgstr "" -"Geben Sie hier die Adresse Ihres Unternehmens und den Namen Ihres " -"Unternehmens an. Diese angaben werden auf Ihrer Rechnung aufgeführt." +"Wenn Ihr LDAP-System keine anonyme Verbindung zulässt, erkennt Zammad dies " +"und stellt Ihnen ein editierbares *Text*-Feld \"Basis-DN\" anstelle eines " +"vorausgefüllten *Auswahl*-Feldes zur Verfügung." -#: ../system/subscription/billing.rst:18 -msgid "VAT ID" -msgstr "Mehrwertsteuernummer" +#: ../system/integrations/ldap/manage.rst:81 +msgid "Review or edit existing source" +msgstr "Vorhandene Quelle überprüfen oder bearbeiten" -#: ../system/subscription/billing.rst:17 +#: ../system/integrations/ldap/manage.rst:68 msgid "" -"Provide your VAT ID here. If applicable your invoice will not contain German " -"VAT. Please make sure to pay the VAT in your country as required." +"Clicking on a LDAP source will provide a configuration and mapping overview." msgstr "" -"Geben Sie hier Ihre Umsatzsteuer-ID an. Falls zutreffend, wird Ihre Rechnung " -"keine deutsche Mehrwertsteuer enthalten. Bitte vergewissern Sie sich, dass " -"Sie die Mehrwertsteuer in Ihrem Land wie erforderlich abführen." - -#: ../system/subscription/billing.rst:27 -msgid "Billing Email Address" -msgstr "Rechnungs-E-Mail-Adresse" +"Wenn Sie auf eine LDAP-Quelle klicken, erhalten Sie eine Übersicht über die " +"Konfiguration und das Mapping." -#: ../system/subscription/billing.rst:21 +#: ../system/integrations/ldap/manage.rst:70 msgid "" -"Usually the instance owner (the person that registered the instance) will " -"receive all emails including the invoices. In case you have your own billing " -"department, you can provide their email address here." +"If needed you can then use the *Change* button to update either the name, " +"active state or the whole configuration. If you're changing the whole " +"configuration, the dialogue will be identical to the source creation." msgstr "" -"Normalerweise erhält der Instanzinhaber (die Person, die die Instanz " -"registriert hat) alle E-Mails einschließlich der Rechnungen. Falls Sie eine " -"eigene Rechnungsabteilung haben, können Sie deren E-Mail-Adresse hier " -"angeben." +"Bei Bedarf können Sie dann die Schaltfläche *Ändern* verwenden, um entweder " +"den Namen, den Status (aktiv oder nicht) oder die gesamte Konfiguration zu " +"aktualisieren. Wenn Sie die gesamte Konfiguration ändern, ist der Dialog " +"identisch mit dem bei der Erstellung der Quelle." -#: ../system/subscription/billing.rst:25 +#: ../system/integrations/ldap/manage.rst:76 msgid "" -"All billing relevant information will then be sent to this email address." +"Did your LDAP server change? Different LDAP servers have different " +"structures and default attributes. This causes the LDAP synchronization to " +"likely fail. Consider removing the affected source and re-add it." msgstr "" -"Alle rechnungsrelevanten Informationen werden dann an diese E-Mail-Adresse " -"gesendet." +"Hat sich Ihr LDAP-Server geändert? Verschiedene LDAP-Server haben " +"unterschiedliche Strukturen und Standardattribute. Dies führt dazu, dass die " +"LDAP-Synchronisierung wahrscheinlich fehlschlägt. Entfernen Sie die " +"betroffene Quelle und fügen Sie sie erneut hinzu." -#: ../system/subscription/billing.rst:27 -msgid "Invoices are sent as attachment (PDF) to this email address." -msgstr "" -"Die Rechnungen werden als Anhang (PDF) an diese E-Mail-Adresse gesendet." +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing the update of the source name." +msgstr "Screencast, der die Aktualisierung des Quellennamens zeigt." + +#: ../system/integrations/ldap/manage.rst:89 +msgid "Re-arrange LDAP source's order" +msgstr "Neuordnung der Reihenfolge der LDAP-Quellen" -#: ../system/subscription/billing.rst:29 +#: ../system/integrations/ldap/manage.rst:84 msgid "" -"Don't forget to press the *Submit* button after you changed above settings." +"You can change the synchronization order for each source at any time. Zammad " +"will synchronize the sources from top to bottom." msgstr "" -"Vergessen Sie nicht, auf die Schaltfläche *Übermitteln* zu klicken, nachdem " -"Sie die obigen Einstellungen geändert haben." +"Sie können die Reihenfolge der Synchronisierung für jede Quelle jederzeit " +"ändern. Zammad synchronisiert die Quellen von oben nach unten." -#: ../system/subscription/billing.rst:0 +#: ../system/integrations/ldap/manage.rst:0 msgid "" -"Screenshot showing options for billing information within the\n" -"subscription menu" -msgstr "" -"Screenshot mit Optionen für Rechnungsinformationen im Menü \"Abonnement\"" +"Screencasting showing how to change the source order by using\n" +"drag and drop." +msgstr "Screencasting zeigt, wie man die Reihenfolge der Quellen ändert." -#: ../system/subscription/billing.rst:70 -msgid "Payment history" -msgstr "Zahlungshistorie" +#: ../system/integrations/ldap/manage.rst:101 +msgid "Remove a source" +msgstr "Eine Quelle entfernen" -#: ../system/subscription/billing.rst:36 +#: ../system/integrations/ldap/manage.rst:92 msgid "" -"The payment history will display a history of all paid invoices. At this " -"point you can also download these in case you need them again." +"If you no longer need the a LDAP source or simply want to start over, you " +"can remove them at any time. This will not remove synchronized users, data " +"synchronized or permissions." msgstr "" -"Der Zahlungsverlauf zeigt eine Übersicht aller bezahlten Rechnungen an. An " -"dieser Stelle können Sie diese auch herunterladen, falls Sie dieser nochmal " -"benötigen." +"Wenn Sie eine LDAP-Quelle nicht mehr benötigen oder einfach neu beginnen " +"möchten, können Sie sie jederzeit entfernen. Dabei werden weder " +"synchronisierte Benutzer noch synchronisierte Daten oder Berechtigungen " +"entfernt." -#: ../system/subscription/billing.rst:41 +#: ../system/integrations/ldap/manage.rst:98 msgid "" -"You will only find *paid* invoices here. Invoices that are to be billed are " -"not available before the payment is completed." +"Not sure if you'd need the source later on? Set the source to inactive " +"instead of removing it - see *Review or edit existing source* for more." msgstr "" -"Sie werden hier nur *bezahlte* Rechnungen finden. Ausgestellte Rechnungen " -"sind nicht verfügbar, bevor die Zahlung eingegangen ist." - -#: ../system/subscription/billing.rst:46 -msgid "Date" -msgstr "Datum" - -#: ../system/subscription/billing.rst:46 -msgid "Date of the invoice creation." -msgstr "Datum der Rechnungserstellung." +"Sie sind sich nicht sicher, ob Sie die Quelle später noch benötigen? Setzen " +"Sie die Quelle auf inaktiv, anstatt sie zu entfernen - mehr dazu unter " +"*Vorhandene Quelle überprüfen oder bearbeiten*." -#: ../system/subscription/billing.rst:49 -msgid "Amount" -msgstr "Betrag" +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing how to remove LDAP sources." +msgstr "Screencast zeigt, wie LDAP-Quellen entfernt werden können." -#: ../system/subscription/billing.rst:49 -msgid "Invoice total including VAT if applicable." -msgstr "Rechnungsbetrag einschließlich Mehrwertsteuer, falls zutreffend." +#: ../system/integrations/pgp/index.rst:2 +msgid "PGP" +msgstr "PGP" -#: ../system/subscription/billing.rst:52 +#: ../system/integrations/pgp/index.rst:7 msgid "" -"Contains contract period (monthly or yearly) and hosted plan for the " -"subscription period in question." +"Pretty Good Privacy (PGP) is another method for secure email communication. " +"With PGP, you can exchange **signed** and **encrypted** messages with others." msgstr "" -"Enthält die Vertragslaufzeit (monatlich oder jährlich) und den Hosting Plan " -"für die betreffende Abonnementdauer." +"Pretty Good Privacy (PGP) ist eine weitere Methode zur sicheren E-Mail-" +"Kommunikation. Mit PGP können Sie **signierte** und **verschlüsselte** " +"Nachrichten mit anderen austauschen." -#: ../system/subscription/billing.rst:63 -msgid "Payment method / Service period" -msgstr "Bezahlmethode / Service-Zeitraum" +#: ../system/integrations/pgp/index.rst:13 +#: ../system/integrations/smime/index.rst:17 +msgid "Signing" +msgstr "Signieren" -#: ../system/subscription/billing.rst:56 -msgid "" -"Used bank account or credit card as well as the subscription period the " -"invoice is about." +#: ../system/integrations/pgp/index.rst:11 +msgid "is a proof that a message hasn't been manipulated on its way." msgstr "" -"Verwendete Bankverbindung oder Kreditkarte sowie der Abonnementzeitraum, auf " -"den sich die Rechnung bezieht." +"ist der Beweis, dass eine Nachricht auf dem Weg nicht manipuliert wurde." -#: ../system/subscription/billing.rst:61 +#: ../system/integrations/pgp/index.rst:13 msgid "" -"It might happen that the invoice date and subscription period differ. This " -"is nothing to worry about, the subscription periods will be accounted later " -"on." +"In other words, it guarantees message **integrity** and **authenticity**." msgstr "" -"Es kann vorkommen, dass das Rechnungsdatum und der Abonnementzeitraum " -"voneinander abweichen. Das ist kein Grund zur Sorge, die Abonnementzeiträume " -"werden später verrechnet." +"Mit anderen Worten, es garantiert die **Integrität** und **Authentizität**." -#: ../system/subscription/billing.rst:67 -msgid "Receipt" -msgstr "Quittung" +#: ../system/integrations/pgp/index.rst:19 +#: ../system/integrations/smime/index.rst:22 +msgid "Encryption" +msgstr "Verschlüsselung" -#: ../system/subscription/billing.rst:66 +#: ../system/integrations/pgp/index.rst:16 +#: ../system/integrations/smime/index.rst:20 msgid "" -"Use the arrow to download the invoice in question. You can download all " -"available invoices any time you need to here!" +"scrambles a message so that it can only be unscrambled by the intended " +"recipient." msgstr "" -"Verwenden Sie den Pfeil, um die betreffende Rechnung herunterzuladen. Sie " -"können alle verfügbaren Rechnungen jederzeit hier herunterladen!" - -#: ../system/subscription/billing.rst:0 -msgid "Screenshot showing payment history of a hosted instance" -msgstr "Screenshot der Zahlungshistorie einer Hosting-Instanz" - -#: ../system/subscription/billing.rst:94 -msgid "Do you want to cancel your subscription?" -msgstr "Wollen Sie Ihr Abonnement kündigen?" +"verschlüsselt eine Nachricht so, dass sie nur vom gewünschten Empfänger " +"entschlüsselt werden kann." -#: ../system/subscription/billing.rst:73 +#: ../system/integrations/pgp/index.rst:19 msgid "" -"In case you no longer want to use Zammad's SaaS, you can cancel your " -"subscription by using the red *Yes, please cancel my subscription* button." +"In other words, it guarantees message **privacy** and **data security**." msgstr "" -"Falls Sie Zammads SaaS nicht mehr nutzen möchten, können Sie Ihr Abonnement " -"über die rote Schaltfläche *Ja, ich möchte mein Abonnement kündigen* " -"kündigen." +"Mit anderen Worten, es garantiert die **Privatsphäre** und " +"**Datensicherheit** einer Nachricht." -#: ../system/subscription/billing.rst:76 -msgid "" -"Your subscription will end the day after your trial or billing period ends." +#: ../system/integrations/pgp/index.rst:25 +msgid "Screenshot of ticket creation with encrypt and sign buttons" msgstr "" -"Ihr Abonnement endet am Tag nach Ablauf Ihres Test- oder " -"Abrechnungszeitraums." +"Screenshot der Ticketerstellung mit Schaltflächen zum Verschlüsseln und " +"Signieren" -#: ../system/subscription/billing.rst:80 +#: ../system/integrations/pgp/index.rst:25 msgid "" -"We will remind you about your cancelled subscription several times up front. " -"After the subscription ended all instance data will be removed. A restore " -"*is not* possible after that point!" +"Once PGP has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " +"appear in the ticket composer." msgstr "" -"Wir werden Sie mehrmals im Voraus an Ihr gekündigtes Abonnement erinnern. " -"Nach Beendigung des Abonnements werden alle Instanzdaten gelöscht. Eine " -"Wiederherstellung ist danach *nicht* möglich!" - -#: ../system/subscription/billing.rst:0 -msgid "Screencast showing how to cancel a subscription" -msgstr "Screencast, der zeigt, wie man ein Abonnement kündigt" +"Sobald PGP aktiviert ist, erscheinen die Schaltflächen 🔒 **Verschlüsseln** " +"und ✅ **Signieren** in der Ticket Ansicht." -#: ../system/subscription/billing.rst:87 -msgid "**😖 Cancelled by accident?**" -msgstr "**😖 Aus Versehen gekündigt?**" +#: ../system/integrations/pgp/index.rst:28 +msgid "**Sign button not visible?**" +msgstr "**Schaltfläche zum Signieren nicht sichtbar?**" -#: ../system/subscription/billing.rst:89 +#: ../system/integrations/pgp/index.rst:30 msgid "" -"You can always undo the cancellation via the *Yes, undo the cancellation of " -"my subscription* button up to the last subscription day!" +"Please note that the signing of emails is based on the outgoing email " +"account. That means you have to choose a group with a sender email account, " +"which has a private key assigned." msgstr "" -"Sie können die Kündigung jederzeit über die Schaltfläche *Ja, meine " -"Abonnement-Kündigung soll widerrufen werden* bis zum letzten Abonnementtag " -"rückgängig machen!" - -#: ../system/subscription/billing.rst:0 -msgid "" -"Screenshot showing a red button to cancel the subscription\n" -"cancellation" -msgstr "Screenshot mit roter Schaltfläche zur Kündigung des Abonnements" +"Bitte beachten Sie, dass das Signieren von E-Mails auf dem ausgehenden E-" +"Mail-Konto basiert. Das heißt, Sie müssen eine Gruppe mit einem Absender-E-" +"Mail-Konto auswählen, dem ein privater Schlüssel zugewiesen ist." -#: ../system/subscription/index.rst:2 -msgid "Subscription (SaaS)" -msgstr "Abonnement (SaaS)" +#: ../system/integrations/pgp/index.rst:35 +msgid "Handling of Keys" +msgstr "Verwaltung von Schlüsseln" -#: ../system/subscription/index.rst:4 +#: ../system/integrations/pgp/index.rst:36 msgid "" -"The subscription settings page allows you to configure your instances " -"package and number of agents required." +"To use the PGP function, you have to enable the integration (PGP) by " +"switching the toggle to *enabled*." msgstr "" -"Auf der Seite mit den Abonnementeinstellungen können Sie Ihr Paket und die " -"Anzahl der benötigten Agenten konfigurieren." +"Um die PGP-Funktion zu nutzen, müssen Sie die Integration (PGP) aktivieren, " +"indem Sie den Schalter auf *aktiviert* stellen." -#: ../system/subscription/index.rst:9 +#: ../system/integrations/pgp/index.rst:39 msgid "" -"This setting section is only available for Hosted setups. If you're looking " -"for on premise support contracts, please see the `Zammad pricing page " -"`_." +"You can add keys by clicking the *add key* button. The keys can be imported " +"from a file or you can paste the content of the key in the text box." msgstr "" -"Dieser Bereich ist nur für Hosted Instanzen verfügbar. Wenn Sie nach " -"Supportverträgen für selbst gehosteten Installationen suchen, sehen Sie sich " -"bitte die `Zammad Preisübersicht `_ an." +"Sie können Schlüssel hinzufügen, indem Sie auf die Schaltfläche *Schlüssel " +"hinzufügen* klicken. Die Schlüssel können aus einer Datei importiert werden " +"oder Sie können den Inhalt des Schlüssels in das Textfeld einfügen." + +#: ../system/integrations/pgp/index.rst:42 +msgid "**Which keys do I have to import?**" +msgstr "**Welche Schlüssel muss ich importieren?**" -#: ../system/subscription/index.rst:20 +#: ../system/integrations/pgp/index.rst:44 msgid "" -"The subscription section currently consists of two tabs: Plan & Billing. For " -"your overview we've divided those two tabs into independent sub pages:" +"For **signing** *outgoing* emails, you have to import the private key of " +"your Zammad email account." msgstr "" -"Der Bereich Abonnement besteht derzeit aus zwei Tabs: Produkt & Abrechnung. " -"Zu Ihrer Übersicht haben wir diese beiden Registerkarten in unabhängige " -"Unterseiten unterteilt:" - -#: ../system/subscription/index.rst:25 -msgid ":doc:`💰 Subscription plan `" -msgstr ":doc:`💰 Abonnement Produkt `" +"Zum **Signieren** von *ausgehenden* E-Mails müssen Sie den privaten " +"Schlüssel Ihres Zammad-E-Mail-Kontos importieren." -#: ../system/subscription/index.rst:24 +#: ../system/integrations/pgp/index.rst:47 msgid "" -"Everything affecting your instance subscription functions like number of " -"agents, package and payment method." +"For **encrypting** *outgoing* emails, you have to import the public key of " +"the customer's email account." msgstr "" -"Alles, was Ihr Abonnement betrifft, wie Anzahl der Agenten, Paket und " -"Zahlungsmethode." - -#: ../system/subscription/index.rst:28 -msgid ":doc:`🧾 Subscription billing `" -msgstr ":doc:`🧾 Abonnement Abrechnungen `" +"Für die **Verschlüsselung** von *ausgehenden* E-Mails müssen Sie den " +"öffentlichen Schlüssel des E-Mail-Kontos des Kunden importieren." -#: ../system/subscription/index.rst:28 +#: ../system/integrations/pgp/index.rst:50 msgid "" -"Everything regarding billing address, invoices and account cancellation." -msgstr "Alles über Rechnungsadresse, Rechnungen und Kündigung." - -#: ../system/subscription/index.rst:33 -msgid "FAQ" -msgstr "FAQ" - -#: ../system/subscription/index.rst:37 -msgid "I set up a trial account but am missing functions to test" +"For **verifying the signature** of signed *incoming* emails, you have to " +"import the public key of the customer." msgstr "" -"Ich habe ein Testkonto eingerichtet, aber mir fehlen Funktionen zum Testen" +"Zur **Prüfung der Signatur** von signierten *eingehenden E-Mails* müssen Sie " +"den öffentlichen Schlüssel des Kunden importieren." -#: ../system/subscription/index.rst:36 +#: ../system/integrations/pgp/index.rst:53 msgid "" -"The trial instance is running within the professional package allowing up to " -"three agents." +"For **decrypting** of encrypted *incoming* emails, you have to import the " +"private key of your Zammad email account." msgstr "" -"Die Testinstanz läuft im Rahmen des Professional-Pakets und erlaubt bis zu " -"drei Agenten." +"Zum **Entschlüsseln** von verschlüsselten *eingehenden E-Mails* müssen Sie " +"den privaten Schlüssel Ihres Zammad-E-Mail-Kontos importieren." -#: ../system/subscription/index.rst:40 -msgid "Can I change package within the trial?" -msgstr "Kann ich innerhalb der Testphase das Paket wechseln?" +#: ../system/integrations/pgp/index.rst:57 +msgid "Import Keys From a File" +msgstr "Importieren von Schlüsseln aus einer Datei" -#: ../system/subscription/index.rst:40 -msgid "No. As soon as the package is changed the subscription begins." -msgstr "Nein. Sobald das Paket gewechselt wird, beginnt das Abonnement." +#: ../system/integrations/pgp/index.rst:58 +msgid "You can import keys from a file in the section **Upload key**:" +msgstr "" +"Sie können Schlüssel aus einer Datei im Abschnitt **Schlüssel hochladen** " +"importieren:" -#: ../system/subscription/index.rst:45 -msgid "What happens to my trial instance after the trial period ended?" -msgstr "Was passiert mit meiner Testinstanz nach Ablauf des Testzeitraums?" +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of adding a key via file" +msgstr "Screenshot zeigt das Hinzufügen eines Schlüssels aus eine Datei" -#: ../system/subscription/index.rst:43 +#: ../system/integrations/pgp/index.rst:64 msgid "" -"Your instance will automatically be canceled for you. Please see *What " -"happens to my instance after it has been canceled?* for more." +"**Supported file formats:** ASCII-armor as well as binary GPG format " +"(basically any GPG supported key format) is supported here." msgstr "" -"Ihre Instanz wird automatisch für Sie gekündigt. Weitere Informationen " -"finden Sie unter *Was passiert mit meiner Instanz, nachdem sie gekündigt " -"wurde?*." +"**Unterstützte Dateiformate:** Unterstützt werden sowohl das ASCII-Armor- " +"als auch das binäre GPG-Format (grundsätzlich jedes von GPG unterstützte " +"Schlüsselformat)." -#: ../system/subscription/index.rst:58 -msgid "What happens to my instance after it has been canceled?" -msgstr "Was passiert mit meiner Instanz, nachdem sie gekündigt wurde?" +#: ../system/integrations/pgp/index.rst:68 +msgid "Import Keys by Pasting the Content" +msgstr "Importieren von Schlüsseln durch Einfügen des Inhalts" -#: ../system/subscription/index.rst:48 -msgid "That depends slightly on your instance state:" -msgstr "Das hängt ein wenig vom Status Ihrer Instanz ab:" +#: ../system/integrations/pgp/index.rst:69 +msgid "You can also paste the key's content in the section **paste key**:" +msgstr "" +"Sie können den Inhalt des Schlüssels auch in den Abschnitt **Schlüssel " +"einfügen** kopieren:" -#: ../system/subscription/index.rst:54 -msgid "Trial instance" -msgstr "Test-Instanz" +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of adding a key via pasting" +msgstr "Screenshot zeigt das Hinzufügen eines Schlüssels durch Einfügen" -#: ../system/subscription/index.rst:51 +#: ../system/integrations/pgp/index.rst:75 msgid "" -"If you're still on trial, we will ice your instance and remind you once " -"again about your instance. We then will wait some days and remove your " -"instance from our system. This is the last time we will inform you by Email." +"**Supported format:** Please note that only ASCII-armor is supported here." msgstr "" -"Wenn Sie sich noch im Testzeitraum befinden, werden wir Ihre Instanz " -"einfrieren und Sie noch einmal an Ihre Instanz erinnern. Wir werden dann " -"einige Tage warten und Ihre Instanz aus unserem System entfernen. Dies ist " -"das letzte Mal, dass wir Sie per E-Mail informieren." +"**Unterstütztes Format:** Bitte beachten Sie, dass hier nur das ASCII-armor " +"Format unterstützt wird." -#: ../system/subscription/index.rst:58 -msgid "Paid instance" -msgstr "Bezahl-Instanz" +#: ../system/integrations/pgp/index.rst:78 +msgid "Deleting Keys" +msgstr "Schlüssel Löschen" -#: ../system/subscription/index.rst:57 +#: ../system/integrations/pgp/index.rst:79 msgid "" -"If you're a paying customer and canceled your subscription, the instance " -"removal will take place the day after your last subscription day." +"If you want to delete a specific key, you can do it by clicking on the menu " +"in the *actions* column and select **delete**:" msgstr "" -"Wenn Sie ein zahlender Kunde sind und Ihr Abonnement gekündigt haben, " -"erfolgt die Entfernung der Instanz am Tag nach Ihrem letzten Abonnementtag." +"Wenn Sie einen bestimmten Schlüssel löschen möchten, können Sie dies tun, " +"indem Sie auf das Menü in der Spalte *Aktionen* klicken und **Löschen** " +"wählen:" -#: ../system/subscription/index.rst:60 -msgid "Can removed instances be restored?" -msgstr "Können entfernte Instanzen wiederhergestellt werden?" +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of deleting a key" +msgstr "Screenshot zeigt Löschen eines Schlüssels" -#: ../system/subscription/index.rst:61 -msgid "No. Once your instance has been removed, a restoration is not possible." -msgstr "" -"Nein. Sobald Ihre Instanz entfernt wurde, ist eine Wiederherstellung nicht " -"mehr möglich." +#: ../system/integrations/pgp/index.rst:88 +msgid "Downloading Keys" +msgstr "Herunterladen von Schlüsseln" -#: ../system/subscription/plan.rst:2 ../system/subscription/plan.rst:38 -msgid "Plan" -msgstr "Produkt" +#: ../system/integrations/pgp/index.rst:89 +msgid "" +"If you want to download your keys, you can do this as well via corresponding " +"action buttons. Depending on the key, you can choose wether you want to " +"download the private or the public key." +msgstr "" +"Wenn Sie Ihre Schlüssel herunterladen möchten, können Sie dies ebenfalls " +"über die entsprechenden Aktionsschaltflächen tun. Je nach Schlüssel können " +"Sie wählen, ob Sie den privaten oder den öffentlichen Schlüssel " +"herunterladen möchten." -#: ../system/subscription/plan.rst:16 -msgid "Subscription" -msgstr "Abonnement" +#: ../system/integrations/pgp/index.rst:95 +#: ../system/integrations/smime/manage-certificates.rst:76 +msgid "Default Behavior" +msgstr "Standard-Verhalten" -#: ../system/subscription/plan.rst:5 +#: ../system/integrations/pgp/index.rst:96 msgid "" -"On the top of the subscription summary you'll find the number of used and " -"available (booked) agent seats. By using the *see more* link you can also " -"expand an agent list to see the currently configured active agents. This " -"list *does not* count accounts with admin permissions only." +"Here you can adjust on per group basis, if *sign* and *encryption* is on or " +"off by default. Please be aware, that agents can always override the setting " +"for each individual article." msgstr "" -"Oben in der Abonnementübersicht finden Sie die Anzahl der verwendeten und " -"verfügbaren (gebuchten) Agentenplätze. Über den Link *Mehr anzeigen* können " -"Sie auch die Liste der Agenten erweitern, um die derzeit konfigurierten " -"aktiven Agenten zu sehen. Diese Liste *zählt nicht* die Konten mit reinen " -"Admin-Rechten." +"Hier können Sie für jede Gruppe einstellen, ob *Signieren* und " +"*Verschlüsselung* standardmäßig ein- oder ausgeschaltet sind. Bitte beachten " +"Sie, dass Agenten die Einstellung für jeden einzelnen Artikel jederzeit " +"überschreiben können." + +#: ../system/integrations/pgp/index.rst:None +msgid "Adjusting default behavior on per group basis" +msgstr "Anpassung des Standardverhaltens für jede Gruppe" -#: ../system/subscription/plan.rst:0 +#: ../system/integrations/pgp/index.rst:107 msgid "" -"Within subscription you can always see how many agents are still\n" -"available to add and who uses the seats." +"Here you can see the last actions regarding signing and encryption and if " +"they were successful." msgstr "" -"Innerhalb des Abonnements können Sie immer sehen, wie viele Agenten noch zur " -"Verfügung stehen und wer die Agenten-Plätze nutzt." +"Hier sehen Sie die letzten Aktionen bezüglich Signierung und Verschlüsselung " +"und ob sie erfolgreich waren." -#: ../system/subscription/plan.rst:14 -msgid "" -"Learn more on how to manage your agents in general :doc:`here `." +#: ../system/integrations/pgp/index.rst:117 +msgid "**Sign button is not visible, but keys are imported.**" msgstr "" -"Erfahren Sie, wie Sie Ihre Agenten im Allgemeinen verwalten :doc:`hier `." +"**Die Schaltfläche \"Signieren\" ist nicht sichtbar, aber die Schlüssel " +"wurden importiert.**" -#: ../system/subscription/plan.rst:19 -msgid "" -"This section gives you an overview of the available plans and their " -"functions / limits. If you require a more detailed table, check our " -"`detailed pricing table `_ for more." -msgstr "" -"Dieser Abschnitt gibt Ihnen einen Überblick über die verfügbaren Tarife und " -"ihre Funktionen / Grenzen. Wenn Sie eine detailliertere Tabelle benötigen, " -"finden Sie weitere Informationen in unserer `detaillierten Preisliste " -"`_." +#: ../system/integrations/pgp/index.rst:115 +msgid "Did you choose a group in the ticket?" +msgstr "Haben Sie eine Gruppe in dem Ticket ausgewählt?" -#: ../system/subscription/plan.rst:23 +#: ../system/integrations/pgp/index.rst:116 msgid "" -"Your selection in this step will decide on the base agent price and e.g. " -"agent limits that might apply in the summary step." +"Did you import a private key for the email adress, which is used for " +"outgoing emails in the group?" msgstr "" -"Ihre Auswahl in diesem Schritt entscheidet über den Basis-Agentenpreis und z." -"B. die Agentenlimits, die Sie in der Zusammenfassung sehen." +"Haben Sie einen privaten Schlüssel für die E-Mail-Adresse importiert, die " +"für ausgehende E-Mails in der Gruppe verwendet wird?" -#: ../system/subscription/plan.rst:26 -msgid "" -"The green *Selected* button will also tell you what plan you're currently in." -msgstr "" -"Die grüne Schaltfläche *Ausgewählt* zeigt Ihnen an, in welchem Tarif Sie " -"sich gerade befinden." +#: ../system/integrations/pgp/index.rst:122 +msgid "**How to obtain keys?**" +msgstr "**Wie erhält man Schlüssel?**" -#: ../system/subscription/plan.rst:30 +#: ../system/integrations/pgp/index.rst:120 msgid "" -"Trial instances are running at Professional with 3 agents. The plan cannot " -"be changed during the trial for technical reasons, if you require more " -"agents for testing, please contact `our sales team `_ with a reason for the raise request." +"You can create them yourself! There are some good tutorials on the web on " +"how to create them. Providing keys to Zammad is a prerequisite to use the " +"PGP feature." msgstr "" -"Die Testinstanzen laufen auf Professional mit 3 Agenten. Der Plan kann aus " -"technischen Gründen während der Testphase nicht geändert werden. Wenn Sie " -"mehr Agenten zum Testen benötigen, wenden Sie sich bitte an `unser Sales " -"Team `_ mit einem Begründung, warum " -"Sie eine Erhöhung benötigen." +"Sie können sie selbst erstellen! Es gibt einige gute Anleitungen im " +"Internet, wie man sie erstellt. Die Bereitstellung von Schlüsseln an Zammad " +"ist eine Voraussetzung für die Nutzung der PGP-Funktion." -#: ../system/subscription/plan.rst:0 -msgid "" -"Screenshot showing three available packages for a hosted Zammad\n" -"instance" +#: ../system/integrations/pgp/index.rst:127 +msgid "**It says a passphrase is needed, but I haven't got one.**" msgstr "" -"Screenshot mit drei verfügbaren Paketen für eine gehostete Zammad-Instanz" - -#: ../system/subscription/plan.rst:83 -msgid "Summary" -msgstr "Zusammenfassung" +"**Mir wird angezeigt dass eine Passphrase erforderlich ist, aber ich habe " +"keine.**" -#: ../system/subscription/plan.rst:41 +#: ../system/integrations/pgp/index.rst:125 msgid "" -"In this section you can adjust the settings of the previous selected plan." +"If the key is secured with a passphrase, you have to provide it for the " +"import in Zammad. It is possible that keys may have an empty passphrase. " +"However, this is *not* recommended." msgstr "" -"In diesem Abschnitt können Sie die Einstellungen des zuvor ausgewählten " -"Plans anpassen." +"Wenn der Schlüssel mit einer Passphrase gesichert ist, müssen Sie diese für " +"den Import in Zammad angeben. Es ist möglich, dass die Schlüssel eine leere " +"Passphrase haben. Dies wird jedoch *nicht* empfohlen." -#: ../system/subscription/plan.rst:45 -msgid "" -"Note that upgrading (more agents, higher package) is always possible, " -"however, downgrading will only happen when your billing period renews." -msgstr "" -"Beachten Sie, dass ein Upgrade (mehr Agenten, höheres Paket) immer möglich " -"ist, ein Downgrade jedoch erst zum Ablauf Ihres Abrechnungszeitraums " -"erfolgen kann." +#: ../system/integrations/pgp/index.rst:132 +msgid "**How do my customers get my new key?**" +msgstr "**Wie bekommen meine Kunden meinen neuen Schlüssel?**" -#: ../system/subscription/plan.rst:49 +#: ../system/integrations/pgp/index.rst:130 msgid "" -"Upgrading resets your billing period and existing credit will be deducted " -"from the new total." +"You have to provide your **public** key in advance. Your customer also has " +"to configure PGP in their email workflow and import your public key. The " +"other way round, you have to get the public key of your customer and have to " +"import it to Zammad." msgstr "" -"Durch das Upgrade wird Ihr Abrechnungszeitraum zurückgesetzt und Ihr " -"bisheriges Guthaben wird vom neuen Gesamtbetrag abgezogen." +"Sie müssen Ihren **öffentlichen** Schlüssel im Voraus bereitstellen. Ihr " +"Kunde muss außerdem PGP in seinem E-Mail-Workflow konfigurieren und Ihren " +"öffentlichen Schlüssel importieren. Umgekehrt müssen Sie sich den " +"öffentlichen Schlüssel Ihres Kunden besorgen und ihn in Zammad importieren." -#: ../system/subscription/plan.rst:58 -msgid "Billing cycle" -msgstr "Abrechnungszyklus" +#: ../system/integrations/slack.rst:2 +msgid "Slack" +msgstr "Slack" -#: ../system/subscription/plan.rst:53 -msgid "" -"You can choose between either monthly or yearly billing. The price per agent " -"will be cheaper if you decide for yearly billing." -msgstr "" -"Sie können zwischen monatlicher und jährlicher Abrechnung wählen. Der Preis " -"pro Agent ist günstiger, wenn Sie sich für eine jährliche Abrechnung " -"entscheiden." +#: ../system/integrations/slack.rst:4 +msgid "**⚠️ Deprecation warning ⚠️**" +msgstr "**⚠️ Warnung: Abkündigung der Integration ⚠️**" -#: ../system/subscription/plan.rst:56 +#: ../system/integrations/slack.rst:6 msgid "" -"If you're still trying out things and are unsure of the right package for " -"your instance, you may want to choose monthly first and then upgrade to " -"yearly when you're sure." +"Zammad 7 will no longer support this dedicated Slack integration. It is " +"recommended to switch to :doc:`pre-defined webhooks ` instead. Existing Slack integrations should " +"be migrated manually before this feature is dropped." msgstr "" -"Wenn Sie noch am Ausprobieren sind und z.B. nicht wissen, welches Paket für " -"Ihre Instanz das richtige ist, sollten Sie sich zunächst für ein monatliches " -"Paket entscheiden und dann auf ein jährliches Paket umsteigen, wenn Sie sich " -"sicher sind." - -#: ../system/subscription/plan.rst:66 -msgid "Plan: (Starter|Professional|Plus) - Agents" -msgstr "Produkt: (Starter|Professional|Plus) - Agenten" - -#: ../system/subscription/plan.rst:61 -msgid "Choose the number of agents you require for your instance." -msgstr "Wählen Sie die Anzahl der Agenten, die Sie für Ihre Instanz benötigen." +"Zammad 7 wird die Slack-Integration nicht mehr unterstützen. Es wird " +"empfohlen, stattdessen auf :doc:`vordefinierte Webhooks ` umzusteigen. Bestehende Slack-Integrationen " +"sollten manuell migriert werden, bevor diese Funktion eingestellt wird." -#: ../system/subscription/plan.rst:63 +#: ../system/integrations/slack.rst:14 msgid "" -"Keep in mind that some packages may have agent limits. Depending on the " -"previous chosen package, you won't be able to exceed specific agent numbers. " -"Also note that setting less agents than currently configured is not possible." +"In order to use this feature, please add a new Slack app to your Workspace. " +"The App you need is called ``Incoming WebHooks`` ." msgstr "" -"Beachten Sie, dass es bei einigen Paketen Obergrenzen für die Anzahl der " -"Agenten gibt. Je nach dem zuvor gewählten Paket können Sie eine bestimmte " -"Anzahl von Agenten nicht überschreiten. Beachten Sie auch, dass es nicht " -"möglich ist, weniger Agenten einzustellen als derzeit konfiguriert sind." - -#: ../system/subscription/plan.rst:69 -msgid "Total" -msgstr "Gesamt" - -#: ../system/subscription/plan.rst:69 -msgid "This will be the net total you're going to be billed." -msgstr "Dies ist der Nettobetrag, der Ihnen in Rechnung gestellt wird." +"Um diese Funktion nutzen zu können, fügen Sie bitte eine neue Slack-App zu " +"Ihrem Arbeitsbereich hinzu. Die App, die Sie benötigen, heißt ``Incoming " +"WebHooks``." -#: ../system/subscription/plan.rst:71 -msgid "" -"By using the *Update subscription* button, the instance package will be " -"adjusted immediately. If you didn't provide a payment method yet, Zammad " -"will request you to provide one at this point." -msgstr "" -"Wenn Sie die Schaltfläche *Abonnement aktualisieren* verwenden, wird Ihr " -"Instanzpaket sofort angepasst. Wenn Sie noch keine Zahlungsmethode angegeben " -"haben, wird Zammad Sie an dieser Stelle auffordern, eine anzugeben." +#: ../system/integrations/slack.rst:18 +msgid "Why Do I Need This Feature?" +msgstr "Warum brauche ich diese Funktion?" -#: ../system/subscription/plan.rst:77 +#: ../system/integrations/slack.rst:20 msgid "" -"In case you're still within the trial period, this means that the trial will " -"be over immediately!" +"If you're already using Slack for your team communication, you'll love this " +"feature! Our Slack integration can push ticket notifications about the last " +"ticket article based on the following events:" msgstr "" -"Falls Sie sich noch im Testzeitraum befinden, wird die Probezeit sofort " -"beendet!" +"Wenn Sie bereits Slack für Ihre Teamkommunikation nutzen, werden Sie diese " +"Funktion lieben! Unsere Slack-Integration kann Ticket-Benachrichtigungen " +"über den letzten Ticket-Artikel basierend auf den folgenden Ereignissen " +"versenden:" -#: ../system/subscription/plan.rst:80 -msgid "Down- or upgrading during the trial period *is not* possible." -msgstr "Ein Down- oder Upgrade während des Testzeitraums ist *nicht* möglich." +#: ../system/integrations/slack.rst:24 +msgid "on Ticket creation" +msgstr "bei Ticketerstellung" -#: ../system/subscription/plan.rst:0 -msgid "Screenshot showing payment options and a pricing summary" -msgstr "Screenshot mit Zahlungsoptionen und einer Preisübersicht" +#: ../system/integrations/slack.rst:25 +msgid "on Ticket updates" +msgstr "bei Ticketaktualisierung" -#: ../system/subscription/plan.rst:99 -msgid "Payment method" -msgstr "Bezahlmethode" +#: ../system/integrations/slack.rst:26 +msgid "on reached reminders" +msgstr "beim Erreichen einer Erinnerung" -#: ../system/subscription/plan.rst:86 -msgid "You can pay via credit card or SEPA mandate." -msgstr "Sie können per Kreditkarte oder SEPA-Mandat bezahlen." +#: ../system/integrations/slack.rst:27 +msgid "a Ticket has escalated" +msgstr "ein Ticket ist eskaliert" -#: ../system/subscription/plan.rst:91 -msgid "Credit card" -msgstr "Kreditkarte" +#: ../system/integrations/slack.rst:28 +msgid "a Ticket is going to escalate" +msgstr "ein Ticket ist kurz vorm Eskalieren" -#: ../system/subscription/plan.rst:89 +#: ../system/integrations/slack.rst:30 msgid "" -"Simply follow the dialogue by clicking *authorize* and confirm -if required " -"by your bank- your consent to Zammad using your card for the payments." +"Zammad will provide the Ticket title, a direct link to the Ticket, the event " +"type (creation, updated, escalation), the customer, time and the last " +"article that has triggered the notification." msgstr "" -"Folgen Sie einfach dem Dialog, indem Sie auf *Autorisieren* klicken und " -"bestätigen Sie - falls von Ihrer Bank verlangt - Ihr Einverständnis, dass " -"Zammad Ihre Karte für die Zahlungen verwendet." - -#: ../system/subscription/plan.rst:95 -msgid "SEPA" -msgstr "SEPA" +"Zammad liefert den Titel des Tickets, einen direkten Link zum Ticket, den " +"Ereignistyp (Erstellung, Aktualisierung, Eskalation), den Kunden, die " +"Uhrzeit und den letzten Artikel, der die Benachrichtigung ausgelöst hat." -#: ../system/subscription/plan.rst:94 +#: ../system/integrations/slack.rst:34 msgid "" -"Provide the requested information of the bank account holder and update if " -"you're ready. You'll then receive an email with the SEPA mandate." +"This will give you further options, as you can see e.g. escalating tickets " +"that are assigned to an agent that's e.g. absent. You can interact faster, " +"as you might see problems earlier (or even before the problem gets one)." msgstr "" -"Geben Sie die angeforderten Informationen des Kontoinhabers an und " -"aktualisieren Sie sie, wenn Sie bereit sind. Sie erhalten dann eine E-Mail " -"mit dem SEPA-Mandat." +"Dadurch erhalten Sie weitere Optionen, da Sie z.B. eskalierende Tickets " +"sehen können, die einem Agenten zugewiesen sind, der z.B. abwesend ist. Sie " +"können schneller interagieren, da Sie Probleme früher erkennen können (oder " +"sogar bevor das Problem eines wird)." -#: ../system/subscription/plan.rst:97 +#: ../system/integrations/slack.rst:38 msgid "" -"Technically there's also the possibility to pay via invoice, however - this " -"method only applies to a fairly low number of instances. Please contact `our " -"sales team `_ for more information." +"If needed and wanted, you can even discuss directly about the topic before " +"sending an answer to the customer. Another possible use case would be a " +"agent monitoring new agents and their answers to tickets." msgstr "" -"Technisch gesehen gibt es auch die Möglichkeit, per Rechnung zu bezahlen, " -"allerdings gilt diese Methode nur für eine relativ geringe Anzahl von " -"Fällen. Bitte kontaktieren Sie `unser Sales Team `_ für weitere Informationen." +"Falls erforderlich und gewünscht, können Sie sogar direkt über das Thema " +"diskutieren, bevor Sie eine Antwort an den Kunden senden. Ein weiterer " +"möglicher Anwendungsfall wäre ein Agent, der neue Agenten und deren " +"Antworten auf Tickets überwacht." -#: ../system/translations.rst:2 -msgid "Translations" -msgstr "Übersetzungen" +#: ../system/integrations/slack.rst:44 +msgid "Configure the Integration" +msgstr "Konfiguration der Integration" -#: ../system/translations.rst:4 +#: ../system/integrations/slack.rst:46 msgid "" -"Translations of Zammad are processed centrally in our `Weblate instance " -"`_. This allows non-developers to review " -"and update translation texts of the language they actually speak." +"First of all, please go to your slack workspace - go to administration => " +"Manage Apps. If you don't have an app yet, you can simply add a new one - " +"just search for ``Incoming WebHooks`` and customize the app to your needs." msgstr "" -"Die Übersetzungen von Zammad werden zentral in unserer `Weblate-Instanz " -"`_ bearbeitet. So können auch Nicht-" -"Entwickler die Übersetzungstexte in der Sprache, die sie tatsächlich " -"sprechen, überprüfen und aktualisieren." +"Als erstes gehen Sie bitte in Ihren Slack-Arbeitsbereich - gehen Sie zu " +"Administration => Manage Apps. Wenn Sie noch keine App haben, können Sie " +"einfach eine neue hinzufügen - suchen Sie einfach nach ``Incoming WebHooks`` " +"und passen Sie die App an Ihre Bedürfnisse an." -#: ../system/translations.rst:9 +#: ../system/integrations/slack.rst:50 msgid "" -"Your language is in an incomplete translation state or has typos? Please " -"consider helping us in sorting this out! All you need is either a GitHub " -"account or to register directly in our instance." -msgstr "" -"Ihre Sprache ist unvollständig oder weist Tippfehler auf? Bitte helfen Sie " -"uns dabei, dies zu beheben! Alles, was Sie brauchen, ist entweder ein GitHub " -"Konto oder eine direkte Registrierung in unserer Instanz." - -#: ../system/translations.rst:13 -msgid "" -"Did you know? This is also where the documentation translations are handled. " -"🤓" +"Choose (or create) the channel Zammad should post it's information to and " +"press on \"Add Incoming WebHooks integration\". If you're ready, copy the " +"provided WebHook URL and go to your Zammad installation." msgstr "" -"Wussten Sie das? Hier werden auch die Übersetzungen der Dokumentation " -"vorgenommen. 🤓" +"Wählen (oder erstellen) Sie den Kanal, auf dem Zammad seine Informationen " +"veröffentlichen soll, und klicken Sie auf \"Add Incoming WebHooks " +"integration\". Wenn Sie bereit sind, kopieren Sie die bereitgestellte " +"WebHook-URL und gehen Sie zu Ihrer Zammad-Installation." -#: ../system/translations.rst:15 +#: ../system/integrations/slack.rst:56 msgid "" -"Have a look in our :docs:`contribution section ` in the system documentation to get started!" +"You need administrative rights on the Slack Workspace. The link to the app " +"directory is normally ``https://[workspace-name].slack.com/apps`` ." msgstr "" -"Werfen Sie einen Blick in unseren :docs:`Contribution Bereich ` in der Systemdokumentation, um loszulegen!" - -#: ../system/translations.rst:20 -msgid "Local Translations" -msgstr "Lokale Übersetzungen" +"Sie benötigen administrative Rechte im Slack Workspace. Der Link zum App-" +"Verzeichnis lautet normalerweise ``https://[workspace-name].slack.com/apps``." -#: ../system/translations.rst:22 +#: ../system/integrations/slack.rst:63 msgid "" -"Apart from these system translations, there's still local translations you " -"can manage. This is relevant if you added custom objects that require " -"translations or even custom states and priorities." +"To configure the slack integration, log in to Zammad and go to Integrations " +"(System) => Slack in the admin panel." msgstr "" -"Abgesehen von diesen Systemübersetzungen können Sie auch noch lokale " -"Übersetzungen verwalten. Dies ist wichtig, wenn Sie benutzerdefinierte " -"Objekte hinzugefügt haben, die Übersetzungen erfordern, oder sogar " -"benutzerdefinierte Status und Prioritäten." - -#: ../system/translations.rst:None -msgid "Translation management screen within the admin menu" -msgstr "Ansicht der Übersetzungsverwaltung im Admin Menü" - -#: ../system/translations.rst:31 -msgid "Updating Translations" -msgstr "Aktualisierung von Übersetzungen" +"Um die Slack-Integration zu konfigurieren, loggen Sie sich in Zammad ein und " +"gehen Sie im Adminpanel zu System > Integrationen > Slack." -#: ../system/translations.rst:33 +#: ../system/integrations/slack.rst:66 msgid "" -"Because of how Zammad ships translations, the only way to update the system " -"translations is to update your Zammad installation. The benefit of this is " -"that you no longer need internet access during a Zammad upgrade as the " -"package has everything it requires already." +"Here you can choose on what evens Zammad should post information about a " +"ticket to your Slack channel. Next you need to device what groups shall be " +"affected by this, as anybody with access to that specific Slack channel can " +"read at least parts of the ticket this might be a privacy issue, if you " +"select the wrong groups. The username is simply the name that Zammad uses as " +"display name inside the Slack chat. The channel defines the Slack channel " +"the information is being posted in. As last option, you can set a custom " +"icon for posting to slack." msgstr "" -"Aufgrund der Art und Weise wie Zammad Übersetzungen ausliefert, ist die " -"Aktualisierung Ihrer Zammad-Installation die einzige Möglichkeit, die " -"Systemübersetzungen zu aktualisieren. Der Vorteil dabei ist, dass Sie " -"während eines Zammad-Upgrades keinen Internetzugang mehr benötigen, da das " -"Paket bereits alles enthält, was es benötigt." - -#: ../system/translations.rst:39 -msgid "Translation of Custom Objects" -msgstr "Übersetzung von benutzerdefinierten Objekten" +"Hier können Sie auswählen, an welchen Ereignissen Zammad Informationen über " +"ein Ticket in Ihrem Slack-Kanal posten soll. Als nächstes müssen Sie " +"festlegen, welche Gruppen davon betroffen sein sollen, da jeder, der Zugang " +"zu diesem speziellen Slack-Kanal hat, zumindest Teile des Tickets lesen " +"kann. Es kann ein Datenschutz-Problem sein, wenn Sie die falschen Gruppen " +"auswählen. Der Benutzername ist der Name, den Zammad als Anzeigename " +"innerhalb des Slack-Chats verwendet. Der Kanal definiert den Slack-Kanal, in " +"dem die Information gepostet wird. Als letzte Option können Sie ein " +"benutzerdefiniertes Symbol für das Posten in Slack festlegen." -#: ../system/translations.rst:41 +#: ../system/integrations/slack.rst:74 msgid "" -"No problem at all! You can customize any translation locally, even if it is " -"not initially provided by the system." +"When you're ready, just hit \"Submit\" and enable the integration. Zammad " +"will now post new ticket information based on the trigger you chose. Below " +"the options you have the recent log that shows the latest requests to Slack " +"for debugging if needed." msgstr "" -"Überhaupt kein Problem! Sie können jede Übersetzung lokal anpassen, auch " -"wenn sie ursprünglich nicht vom System bereitgestellt wurde." +"Wenn Sie soweit sind, klicken Sie auf \"Absenden\" und aktivieren Sie die " +"Integration. Zammad wird nun neue Ticketinformationen basierend auf dem von " +"Ihnen gewählten Trigger posten. Unterhalb der Optionen finden Sie die " +"aktuellsten Protokolleinträge, die die letzten Anfragen an Slack zur " +"Fehlersuche anzeigen, falls erforderlich." -#: ../system/translations.rst:44 +#: ../system/integrations/slack.rst:81 msgid "" -"Translation is supported for a broad number of features, including but not " -"limited to custom:" +"If you leave the Icon URL empty, Zammad will use the Zammad logo instead. " +"The icon should be a square PNG file." msgstr "" -"Die Übersetzung wird für eine große Anzahl von Funktionen unterstützt, " -"einschließlich, aber nicht beschränkt auf benutzerdefinierte:" - -#: ../system/translations.rst:47 -msgid "Object Attributes" -msgstr "Objekt-Attribute" - -#: ../system/translations.rst:48 -msgid "Ticket Macros" -msgstr "Ticket-Makros" - -#: ../system/translations.rst:49 -msgid "Ticket Overviews" -msgstr "Ticket-Übersichten" - -#: ../system/translations.rst:50 -msgid "Ticket Priorities" -msgstr "Ticket-Prioritäten" - -#: ../system/translations.rst:51 -msgid "Ticket States" -msgstr "Ticket-Status" - -#: ../system/translations.rst:54 -msgid "Customizing Translations" -msgstr "Übersetzungen anpassen" +"Wenn Sie die Icon URL leer lassen, wird Zammad stattdessen das Zammad-Logo " +"verwenden. Das Icon sollte eine quadratische PNG-Datei sein." -#: ../system/translations.rst:56 +#: ../system/integrations/slack.rst:90 msgid "" -"Within the translation screen, simply click on the **New Translation** " -"button." +"The following figure shows how it will look if you choose to receive updates " +"on created and updated tickets. On every post Zammad sends to the Slack " +"channel, you can create new threads to discuss about the new article." msgstr "" -"Klicken Sie in der Ansicht \"Übersetzung\" einfach auf die Schaltfläche " -"**Neue Übersetzung**." - -#: ../system/translations.rst:None -msgid "New translation dialog" -msgstr "Dialog neue Übersetzung" +"Die folgende Abbildung zeigt, wie es aussieht, wenn Sie sich dafür " +"entscheiden, Updates für erstellte und aktualisierte Tickets zu erhalten. " +"Bei jedem Beitrag, den Zammad an den Slack-Kanal sendet, können Sie neue " +"Threads erstellen, um über den neuen Artikel zu diskutieren." -#: ../system/translations.rst:62 +#: ../system/integrations/slack.rst:96 msgid "" -"In the dialog you can immediately enter the exact translation source (if you " -"know it) and your custom translation text for it and click **Submit**." +"If you just want to keep track of soon escalating or already escalated " +"tickets, it will look the the following figure. Zammad changes the color in " +"front of the post so you can easily see the state of the ticket." msgstr "" -"In dem Dialog können Sie sofort die genaue Übersetzungsquelle (sofern Sie " -"diese kennen) und Ihren individuellen Übersetzungstext eingeben und auf " -"**Übermitteln** klicken." +"Wenn Sie nur den Überblick über bald eskalierende oder bereits eskalierte " +"Tickets behalten möchten, sieht es wie in der folgenden Abbildung aus. " +"Zammad ändert die Farbe vor dem Beitrag, damit Sie den Status des Tickets " +"leicht erkennen können." -#: ../system/translations.rst:65 +#: ../system/integrations/slack.rst:102 msgid "" -"Alternatively, try to search for translation suggestions in the list below. " -"Selecting an item from the list will pre-fill the translation source for you " -"and then you can just enter your custom translation." +"If you change the state, Zammad will also put information on what state the " +"ticket gets and (if pending state) the date until it pends. You'll also " +"recognize the color codes in front of posts on slack, as they are exact the " +"same the ticket state colors you'll see in Zammad!" msgstr "" -"Alternativ können Sie auch in der Liste unten nach Übersetzungsvorschlägen " -"suchen. Wenn Sie ein Element aus der Liste auswählen, wird die " -"Übersetzungsquelle für Sie vorausgefüllt und Sie können dann einfach Ihre " -"eigene Übersetzung eingeben." +"Wenn Sie den Status ändern, wird Zammad auch Informationen darüber anzeigen, " +"welchen Status das Ticket bekommt und (falls es sich um einen \"Warten auf..." +"\" Status handelt) das Datum, bis zu dem gewartet wird. Sie werden auch die " +"Farbcodes vor den Beiträgen auf Slack erkennen, da sie genau die gleichen " +"sind wie die Farben des Ticketstatus, die Sie in Zammad sehen werden!" -#: ../system/translations.rst:69 +#: ../system/integrations/smime/index.rst:2 +msgid "S/MIME" +msgstr "S/MIME" + +#: ../system/integrations/smime/index.rst:11 msgid "" -"The target language will always default to your current language selection. " -"If you need to translate for a different language, simply change the " -"selection before submitting." +"S/MIME is the most widely-supported method for secure email communication. " +"With S/MIME, you can exchange **signed** and **encrypted** messages with " +"others." msgstr "" -"Als Zielsprache wird immer die von Ihnen gewählte Sprache verwendet. Wenn " -"Sie für eine andere Sprache übersetzen wollen, ändern Sie die Auswahl " -"einfach vor dem Übermitteln." +"S/MIME ist die am weitesten verbreitete Methode für sichere E-Mail-" +"Kommunikation. Mit S/MIME können Sie **signierte** und **verschlüsselte** " +"Nachrichten mit anderen austauschen." -#: ../system/translations.rst:73 +#: ../system/integrations/smime/index.rst:15 msgid "" -"All your custom translations will show up in the overview table when added. " -"And they will even persist across Zammad updates!" +"is proof that a message hasn't been tampered with or sent by an impersonator." msgstr "" -"Alle Ihre benutzerdefinierten Übersetzungen werden in der Übersichtstabelle " -"angezeigt, wenn sie hinzugefügt werden. Und sie bleiben sogar bei " -"Aktualisierungen von Zammad erhalten!" +"ist der Beweis, dass eine Nachricht nicht manipuliert oder von einem " +"Unbekannten gesendet wurde." -#: ../system/translations.rst:76 +#: ../system/integrations/smime/index.rst:17 msgid "" -"Make sure to reload your browser if a translated string is not displayed." +"In other words, it guarantees a message's **integrity** and **authenticity**." msgstr "" -"Aktualisieren Sie die Seite im Browser, falls eine Übersetzung nicht " -"angezeigt wird." +"Mit anderen Worten, es garantiert die **Integrität** und **Authentizität** " +"einer Nachricht." -#: ../system/translations.rst:80 -msgid "Reverting to Original Translations" -msgstr "Zurücksetzen auf Originalübersetzungen" +#: ../system/integrations/smime/index.rst:22 +msgid "In other words, it guarantees **privacy** and **data security**." +msgstr "" +"Mit anderen Worten, es garantiert **Privatsphäre** und **Datensicherheit**." -#: ../system/translations.rst:82 -msgid "" -"If you want to revert a custom translation to original text, simply use the " -"appropriate action within the row of the overview table." +#: ../system/integrations/smime/index.rst:28 +msgid "Screencast demo of S/MIME features for both new tickets and replies" msgstr "" -"Wenn Sie eine benutzerdefinierte Übersetzung auf die ursprüngliche " -"Übersetzung zurücksetzen möchten, verwenden Sie einfach die entsprechende " -"Aktion in der Zeile der Übersichtstabelle." +"Bildschirmaufzeichnung von S/MIME-Funktionen für neue Tickets und Antworten" -#: ../system/translations.rst:85 +#: ../system/integrations/smime/index.rst:28 msgid "" -"Depending on the type of the translation source, the action has a slightly " -"different name:" +"Once S/MIME has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " +"appear in the ticket composer." msgstr "" -"Je nach Art der Übersetzungsquelle hat die Aktion einen etwas anderen Namen:" - -#: ../system/translations.rst:88 -msgid "**Reset** for customized system translations" -msgstr "**Zurücksetzen** für angepasste Systemübersetzungen" +"Sobald S/MIME aktiviert ist, erscheinen die Schaltflächen 🔒 " +"**Verschlüsseln** und ✅ **Signieren** in der Ticket Ansicht." -#: ../system/translations.rst:89 -msgid "**Remove** for customized local translations" -msgstr "**Entfernen** für angepasste lokale Übersetzungen" +#: ../system/integrations/smime/index.rst:32 +msgid ":doc:`🔪 Prerequisites `" +msgstr ":doc:`🔪 Voraussetzungen `" -#: ../system/translations.rst:91 +#: ../system/integrations/smime/index.rst:31 msgid "" -"In both cases, the action will remove the customized translation after a " -"confirmation." +"New to S/MIME? This section helps you to find certificate providers and " +"points out Limitations." msgstr "" -"In beiden Fällen wird die benutzerdefinierte Übersetzung nach einer " -"Bestätigung entfernt." - -#: ../system/translations.rst:None -msgid "Screenshot showing the location of the Remove action" -msgstr "Screenshot, der die Aktion \"Entfernen\" zeigt" +"Neu in S/MIME? Dieser Abschnitt hilft Ihnen, Zertifikatsanbieter zu finden " +"und weist auf Einschränkungen hin." -#: ../system/translations.rst:99 -msgid "Inline Translations" -msgstr "Inline-Übersetzungen" +#: ../system/integrations/smime/index.rst:35 +msgid ":doc:`📝 Manage Certificates `" +msgstr ":doc:`📝 Zertifikate verwalten `" -#: ../system/translations.rst:101 -msgid "" -"If you prefer a more hands-on approach, you can activate the inline or on-" -"screen translation feature by pressing ``ctrl`` + ``alt`` + ``t`` at any " -"time and on any screen." +#: ../system/integrations/smime/index.rst:35 +msgid "Add and download certificates; configure group default behaviors." msgstr "" -"Wenn Sie es lieber etwas praktischer mögen, können Sie die Inline- oder On-" -"Screen-Übersetzung durch Drücken von ``strg`` + ``alt`` + ``t`` jederzeit " -"und in jeder Ansicht aktivieren." +"Hinzufügen und Herunterladen von Zertifikaten; Konfigurieren des " +"Standardverhaltens von Gruppen." -#: ../system/translations.rst:105 +#: ../system/integrations/smime/index.rst:38 +msgid ":doc:`😦 Troubleshooting `" +msgstr ":doc:`😦 Fehlersuche `" + +#: ../system/integrations/smime/index.rst:38 +msgid "Took a wrong turn? About recent logs and common issues." +msgstr "Sie sind falsch abgebogen? Über Protokolle und häufige Probleme." + +#: ../system/integrations/smime/index.rst:43 msgid "" -"All customizable translation texts will be highlighted for you on the " -"screen. Just click into the highlighted area and update the text in place." +"For more details on how S/MIME integration works on the agent side, see the :" +"user-docs:`user docs `." msgstr "" -"Alle anpassbaren Übersetzungstexte werden für Sie auf dem Bildschirm " -"hervorgehoben. Klicken Sie einfach in den markierten Bereich und " -"aktualisieren Sie den Text an Ort und Stelle." +"Wie die S/MIME-Integration auf Agenten-Seite funktioniert erfahren Sie in " +"der :user-docs:`Benutzerdokumentation `." -#: ../system/translations.rst:None -msgid "Inline translation mode activated for the Overview screen" -msgstr "Inline-Übersetzungsmodus für die Ansicht \"Übersicht\"" +#: ../system/integrations/smime/manage-certificates.rst:2 +msgid "Manage Certificates" +msgstr "Verwalten von Zertifikaten" -#: ../system/translations.rst:112 +#: ../system/integrations/smime/manage-certificates.rst:4 msgid "" -"When finished editing, simply press ``ctrl`` + ``alt`` + ``t`` again to " -"deactivate." +"S/MIME is **disabled by default**. Enable it to start adding certificates." msgstr "" -"Wenn Sie mit der Bearbeitung fertig sind, drücken Sie einfach wieder " -"``strg`` + ``alt`` + ``t``, um die Bearbeitung zu deaktivieren." +"S/MIME ist standardmäßig **deaktiviert**. Aktivieren Sie es, um Zertifikaten " +"hinzuzufügen." -#: ../system/translations.rst:117 +#: ../system/integrations/smime/manage-certificates.rst:10 +msgid "Dialogue to add new certificates or private keys" +msgstr "Dialog zum Hinzufügen neuer Zertifikate oder privater Schlüssel" + +#: ../system/integrations/smime/manage-certificates.rst:10 msgid "" -"Even though it's available on any screen, the inline translation feature " -"requires admin permissions. It works only for the current language " -"selection. If you need to translate a different language, first change the " -"language in your :user-docs:`profile settings `." +"Manage certificates in the Admin Panel under **System > Integrations > S/" +"MIME**. Certificates may be pasted in as plain text or uploaded from a file." msgstr "" -"Obwohl die Inline-Übersetzungsfunktion auf jeder Ansicht verfügbar ist, " -"erfordert sie Administratorrechte. Sie funktioniert nur für die aktuelle " -"Sprachauswahl. Wenn Sie eine andere Sprache übersetzen müssen, ändern Sie " -"zunächst die Sprache in Ihren :user-docs:`Profileinstellungen `." +"Verwalten Sie Zertifikate im Admin Panel unter **System > Integrationen > S/" +"MIME**. Die Zertifikate können als einfacher Text eingefügt oder aus einer " +"Datei hochgeladen werden." -#: ../system/variables.rst:2 -msgid "Variables" -msgstr "Variablen" +#: ../system/integrations/smime/manage-certificates.rst:14 +msgid "Add Certificate Data" +msgstr "Zertifikatsdaten hinzufügen" + +#: ../system/integrations/smime/manage-certificates.rst:36 +msgid "Add Certificate" +msgstr "Zertifikat hinzufügen" -#: ../system/variables.rst:4 +#: ../system/integrations/smime/manage-certificates.rst:17 msgid "" -"Please note that this is just an overview of available variables. It might " -"be incomplete or variables might not be available within some functions. If " -"you're missing variables or are not sure if something is not working as " -"expected, feel free to ask over at the `Community `_." +"Import public-key certificates for both your own organization and your " +"contacts." msgstr "" -"Bitte beachten Sie, dass dies nur eine Übersicht der verfügbaren Variablen " -"ist. Manche Variablen können in bestimmten Funktionen inkompatibel oder " -"nicht verfügbar sein. Wenn Sie Variablen vermissen oder sich nicht sicher " -"sind, ob diese wie erwartet funktionieren, fragen Sie sehr gern in unserer " -"`Community `_ nach." +"Importieren Sie Public-Key-Zertifikate sowohl für Ihr eigenes Unternehmen " +"als auch für Ihre Kontakte." -#: ../system/variables.rst:10 +#: ../system/integrations/smime/manage-certificates.rst:19 msgid "" -"Variables can be called by typing ``::`` (just like text modules in the " -"frontend), as long as you're in a supported text field within the backend. " -"Zammad will display all variables being available within this context and " -"replace it to the variable as soon as you selected an entry." +"You can also add a bunch of certificates in one go by providing a single " +"file with all relevant certificates." msgstr "" -"Variablen können durch Eingabe von ``::`` aufgerufen werden (genau wie " -"Textbausteine im Frontend), solange man sich in einem unterstützten Textfeld " -"im Backend befindet. Zammad zeigt alle Variablen an, die in diesem Kontext " -"verfügbar sind und ersetzt sie durch die Variable, sobald Sie einen Eintrag " -"ausgewählt haben." +"Sie können auch eine Reihe von Zertifikaten auf einmal hinzufügen, indem Sie " +"eine einzige Datei mit allen relevanten Zertifikaten bereitstellen." + +#: ../system/integrations/smime/manage-certificates.rst:22 +msgid "🕵️ **ALWAYS verify certificates in-person or over the phone!**" +msgstr "🕵️ **IMMER die Zertifikate persönlich oder telefonisch überprüfen!**" -#: ../system/variables.rst:15 +#: ../system/integrations/smime/manage-certificates.rst:24 msgid "" -"You have an empty field which you referenced and it appears as ``-``? That's " -"currently working as designed - you might want to ensure that these fields " -"always have a value." +"The whole point of signatures is to alert you when someone is trying to " +"pretend to be someone they're not. Never accept a certificate from someone " +"online without verifying it first." msgstr "" -"Haben Sie ein leeres Feld, auf das Sie verweisen, und es erscheint als ``-" -"``? Das funktioniert derzeit wie vorgesehen - Sie sollten sicherstellen, " -"dass diese Felder immer einen Wert beinhalten." - -#: ../system/variables.rst:20 -msgid "Variable Categories" -msgstr "Variablen Kategorien" +"Der Sinn von Signaturen ist es, Sie zu warnen, wenn jemand versucht sich als " +"jemand auszugeben, der er nicht ist. Akzeptieren Sie niemals ein Zertifikat " +"von jemandem, ohne es vorher zu überprüfen." -#: ../system/variables.rst:31 -msgid "Wait, What About Custom Objects?" -msgstr "Moment, was ist mit benutzerdefinierten Objekten?" +#: ../system/integrations/smime/manage-certificates.rst:28 +msgid "📇 **What about trusted certificate authorities?**" +msgstr "📇 **Was ist mit vertrauenswürdigen Zertifizierungsstellen?**" -#: ../system/variables.rst:33 +#: ../system/integrations/smime/manage-certificates.rst:30 msgid "" -"Good point! Of course, we can't predict what objects you might create, but " -"we can give you a hint on how to put the puzzle together to get your custom " -"values." +"In some cases (e.g. when dealing with large enterprises), you may be given a " +"certificate for an entire CA, rather than a single contact. Add it here to " +"trust *all* certificates issued by that CA." msgstr "" -"Das ist ein guter Punkt! Natürlich können wir nicht vorhersagen, welche " -"Objekte Sie erstellen werden, aber wir können Ihnen einen Hinweis geben, wie " -"Sie Ihre eigenen Werte verwenden können." +"In manchen Fällen (z.B. bei großen Unternehmen) kann es vorkommen, dass Sie " +"ein Zertifikat für eine ganze CA erhalten und nicht nur für einen einzelnen " +"Kontakt. Fügen Sie es hier hinzu, um *allen* von dieser CA ausgestellten " +"Zertifikaten zu vertrauen." -#: ../system/variables.rst:36 +#: ../system/integrations/smime/manage-certificates.rst:35 msgid "" -"For this, we'll talk about the inner part of the variable (so everything " -"within ``#{}``), please put the outer part around to have a valid variable. " -"The first part of the variable name consist of the object type. Currently " -"these are:" +"Commercial CAs can usually be verified online. Zammad does not include a " +"list of built-in, trusted CAs." msgstr "" -"Hier geht es um den inneren Teil der Variable (also alles innerhalb von ``#{}" -"``). Bitte fügen Sie den äußeren Teil hinzu, um eine gültige Variable zu " -"erhalten. Der erste Teil des Variablennamens besteht aus dem Objekttyp. " -"Derzeit sind dies:" - -#: ../system/variables.rst:41 -msgid "Ticket (``ticket``)" -msgstr "Ticket (``ticket``)" - -#: ../system/variables.rst:42 -msgid "User (``user``)" -msgstr "Benutzer (``user``)" - -#: ../system/variables.rst:43 -msgid "Organization (``organization``)" -msgstr "Organisation (``organization``)" +"Kommerzielle CAs können in der Regel online verifiziert werden. Zammad " +"enthält keine Liste mit eingebauten, vertrauenswürdigen CAs." -#: ../system/variables.rst:44 -msgid "Group (``group``)" -msgstr "Gruppe (``group``)" +#: ../system/integrations/smime/manage-certificates.rst:57 +msgid "Add Private Key" +msgstr "Privaten Schlüssel hinzufügen" -#: ../system/variables.rst:46 +#: ../system/integrations/smime/manage-certificates.rst:39 msgid "" -"The second part is the name of the object. This is the name you define " -"during object creation and can be found within the object menu at any time. " -"The first and second part of a variable is divided by a point, e.g.: " -"``ticket.number`` which will in total be ``#{ticket.number}``." +"Once you've added a public-key certificate, you can import its matching " +"private key." msgstr "" -"Der zweite Teil ist der Name des Objektattributs. Diesen Namen legen Sie bei " -"der Objektattributerstellung fest und Sie können ihn jederzeit im Objektmenü " -"in den Einstellungen wiederfinden. Der erste und zweite Teil einer Variablen " -"wird durch einen Punkt getrennt, z.B.: ``ticket.number``, was im Ergebnis " -"``#{ticket.number}`` ergibt." +"Sobald Sie ein öffentliches Zertifikat hinzugefügt haben können Sie den " +"dazugehörigen privaten Schlüssel importieren." -#: ../system/variables.rst:51 +#: ../system/integrations/smime/manage-certificates.rst:42 msgid "" -"Now, in some situations it's possible that you'll need to use a third part. " -"The best example for such a situation would be a ``select`` or ``tree-" -"select`` field which will by default return the key value, not it's display " -"name. For this, just extend your variable with ``.value``. This will result " -"in ``#{ticket.select.value}``." +"Private keys are for **your own organization only**; never ask your contacts " +"for their private keys." msgstr "" -"In manchen Situationen ist es möglich, dass Sie einen dritten Teil verwenden " -"müssen. Das beste Beispiel für eine solche Situation wäre ein ``Auswahl``- " -"oder ``Baumauswahl``-Feld, das standardmäßig den Schlüsselwert und nicht den " -"Anzeigenamen zurückgibt. Erweitern Sie dazu einfach Ihre Variable mit ``." -"value``. Das Ergebnis ist dann ``#{ticket.select.value}``." - -#: ../system/variables.rst:60 -msgid "Using Translated Variables" -msgstr "Verwendung übersetzter Variablen" +"Private Schlüssel sind nur für **Ihre eigene Organisation**; fragen Sie " +"niemals Ihre Kontakte nach deren privaten Schlüsseln." -#: ../system/variables.rst:62 +#: ../system/integrations/smime/manage-certificates.rst:0 msgid "" -"If you want to use a translated variable in triggers or schedulers, you can " -"extend the placeholder like this: ``#{t(ticket.state.name)}``. The ``t`` " -"tells Zammad to search for fitting translated strings. The used output " -"language is based on the system language of Zammad which you can set in the " -"admin panel under :doc:`/settings/branding` or based on the selected locale " -"in the trigger/scheduler edit dialog." +"S/MIME integration showing configured certificates and possible issues with " +"Logging" msgstr "" -"Wenn Sie eine übersetzte Variable in Triggern oder Automatisierungen " -"verwenden möchten, können Sie den Platzhalter wie folgt erweitern: " -"``#{t(ticket.status.name)}``. Das ``t`` sagt Zammad, dass es nach passenden " -"übersetzten Zeichenketten suchen soll. Die verwendete Ausgabesprache basiert " -"auf der Systemsprache von Zammad, die Sie im Admin-Panel unter :doc:`/" -"settings/branding` einstellen können oder basierend auf der ausgewählten " -"Sprache im Trigger-/Automatisierungs-Dialog." +"S/MIME-Integration mit konfigurierten Zertifikaten und möglichen Problemen " +"mit der Protokollierung" -#: ../system/variables.rst:69 +#: ../system/integrations/smime/manage-certificates.rst:50 msgid "" -"A possible use-case: you want to send your customers updates on tickets via " -"trigger or scheduler which should include the state of the ticket. Using the " -"default ``#{ticket.state.name}`` (without the translation flag ``t()``) " -"would lead to the output of the original (english) name of the state." +"A note is displayed on certificates with a matching private key (see line 2)." msgstr "" -"Ein möglicher Anwendungsfall: Sie möchten Ihren Kunden per Trigger oder " -"Scheduler Updates zu Tickets schicken, die den Status des Tickets enthalten " -"sollen. Die Verwendung des Standardwertes ``#{ticket.state.name}`` (ohne das " -"Übersetzungsflag ``t()``) würde zur Ausgabe des ursprünglichen (englischen) " -"Namens des Status führen." +"Bei Zertifikaten mit passendem privaten Schlüssel wird ein Hinweis angezeigt " +"(siehe Zeile 2)." -#: ../system/variables.rst:75 -msgid "Date and Time Formatting" -msgstr "Formatierung von Datum und Uhrzeit" +#: ../system/integrations/smime/manage-certificates.rst:52 +msgid "📤 **Certificates and private keys must be uploaded separately.**" +msgstr "" +"📤 **Zertifikate und private Schlüssel müssen separat hochgeladen werden.**" -#: ../system/variables.rst:77 +#: ../system/integrations/smime/manage-certificates.rst:54 msgid "" -"The system (trigger/scheduler selected) locale and timezone predefines a " -"default format of date and timestamp. This format is customizable by using " -"the ``dt()`` method." +"If your certificate and private key are bundled together in the same file or " +"PEM block, import it twice (once using each button)." msgstr "" -"Die Sprache und Zeitzone des Systems (oder in Trigger/Automatisierung " -"ausgewählt) gibt ein Standardformat für Datum und Zeitstempel vor. Dieses " -"Format kann mit Hilfe der Methode ``dt()`` angepasst werden." - -#: ../system/variables.rst:79 -msgid "The method arguments are as follows:" -msgstr "Die Argumente der Methode lauten wie folgt:" - -#: ../system/variables.rst:81 -msgid "The date or timestamp variable you want to format." -msgstr "Die Datums- oder Zeitstempelvariable, die Sie formatieren möchten." - -#: ../system/variables.rst:82 -msgid "The output format string." -msgstr "Die Zeichenkette für das Ausgabeformat." - -#: ../system/variables.rst:83 -msgid "The timezone to apply (optional)." -msgstr "Die zu verwendende Zeitzone (optional)." +"Wenn Ihr Zertifikat und Ihr privater Schlüssel in derselben Datei oder " +"demselben PEM-Block gebündelt sind, importieren Sie sie zweimal (einmal mit " +"jeder Schaltfläche)." -#: ../system/variables.rst:86 -msgid "" -"``#{dt(ticket.updated_at, \"%A %Y-%m-%d %H:%M in the office\", \"Europe/" -"Berlin\")}``" +#: ../system/integrations/smime/manage-certificates.rst:57 +msgid "Please note that bulk imports of private keys are not possible." msgstr "" -"``#{dt(ticket.updated_at, \"%A %Y-%m-%d %H:%M im Büro\", \"Europa/Berlin\")}" -"``" +"Bitte beachten Sie, dass ein Massenimport von privaten Schlüsseln nicht " +"möglich ist." -#: ../system/variables.rst:87 -msgid "Monday, 2024-03-18 15:31 in the office" -msgstr "Montag, 2024-03-18 15:31 im Büro" +#: ../system/integrations/smime/manage-certificates.rst:60 +msgid "Download Certificate Data" +msgstr "Zertifikat herunterladen" -#: ../system/variables.rst:89 +#: ../system/integrations/smime/manage-certificates.rst:62 msgid "" -"If you want to use our example, make sure to paste the string above without " -"formatting (``CTRL+Shift+v``), otherwise it won't work." +"You can download the earlier provided certificates and private keys at any " +"time from your Zammad instance." msgstr "" -"Wenn Sie unser Beispiel verwenden wollen, fügen Sie die obige Zeichenkette " -"ohne Formatierung ein (``STRG+Umschalt+v``), andernfalls funktioniert es " -"nicht." +"Sie können die zuvor bereitgestellten Zertifikate und privaten Schlüssel " +"jederzeit von Ihrer Zammad-Instanz herunterladen." -#: ../system/variables.rst:93 -msgid "The following table lists available format directives:" +#: ../system/integrations/smime/manage-certificates.rst:65 +msgid "" +"Please note that passphrase-protected private keys stay protected and when " +"you download them, you have to know the passphrase to use them after " +"downloading." msgstr "" -"In der folgenden Tabelle sind die verfügbaren Formatparameter aufgeführt:" - -#: ../system/variables.rst:99 -msgid "Parameter" -msgstr "Parameter" - -#: ../system/variables.rst:102 -msgid "``%Y``" -msgstr "``%Y``" - -#: ../system/variables.rst:103 -msgid "Year with 4 digits" -msgstr "Jahr mit 4 Ziffern" +"Bitte beachten Sie, dass Passphrase geschützte private Schlüssel geschützt " +"bleiben. Wenn Sie sie herunterladen, müssen Sie die Passphrase kennen, um " +"sie nach dem Herunterladen zu verwenden." -#: ../system/variables.rst:104 -msgid "Use ``%y`` for year with 2 digits" -msgstr "Verwenden Sie ``%y`` für Jahreszahlen mit 2 Ziffern" +#: ../system/integrations/smime/manage-certificates.rst:73 +msgid "Dialogue to download certificates or private keys" +msgstr "Dialog zum Herunterladen von Zertifikaten oder privaten Schlüsseln" -#: ../system/variables.rst:105 -msgid "``%m``" -msgstr "``%m``" +#: ../system/integrations/smime/manage-certificates.rst:73 +msgid "Download stored certificates and their keys" +msgstr "Herunterladen gespeicherter Zertifikate und ihrer Schlüssel" -#: ../system/variables.rst:106 -msgid "Month of year (as number with zero-padding)" -msgstr "Monat des Jahres (als Zahl, ggf. mit vorangestellter Null)" +#: ../system/integrations/smime/manage-certificates.rst:78 +msgid "" +"The ticket composer will set all outgoing messages to **signed and " +"encrypted** by default (assuming the required certificates exist)." +msgstr "" +"Die Ticket-Bearbeitungs-Funktion setzt alle ausgehenden Nachrichten " +"standardmäßig auf **signiert und verschlüsselt** (vorausgesetzt, die " +"erforderlichen Zertifikate sind vorhanden)." -#: ../system/variables.rst:107 -msgid "Use ``%-m`` for month without zero-padding" -msgstr "Verwenden Sie ``%-m`` für den Monat ohne vorangestellte Null" +#: ../system/integrations/smime/manage-certificates.rst:82 +msgid "These defaults can be modified on a per-group basis:" +msgstr "Diese Standardwerte können für jede Gruppe einzeln geändert werden:" -#: ../system/variables.rst:108 -msgid "``%d``" -msgstr "``%d``" +#: ../system/integrations/smime/manage-certificates.rst:None +msgid "Zammad allowing to choose the default behavior on per group basis" +msgstr "Zammad ermöglicht die Auswahl des Standardverhaltens für jede Gruppe" -#: ../system/variables.rst:109 -msgid "Day of month (as number with zero-padding)" -msgstr "Tag des Monats (als Zahl, ggf. mit vorangestellter Null)" +#: ../system/integrations/smime/manage-certificates.rst:89 +msgid "" +"Of course, agents can always manually change these settings on each email " +"they send out." +msgstr "" +"Natürlich können Agenten diese Einstellungen bei jeder E-Mail, die sie " +"versenden, manuell ändern." -#: ../system/variables.rst:110 -msgid "Use ``%e`` for day without zero-padding" -msgstr "Verwenden Sie ``%e`` für Tage ohne vorangestellte Null" +#: ../system/integrations/smime/prerequisites.rst:4 +msgid "A certificate *and* private key for your own organization" +msgstr "" +"Ein Zertifikat *und* ein privater Schlüssel für Ihre eigene Organisation" -#: ../system/variables.rst:111 -msgid "``%H``" -msgstr "``%H``" +#: ../system/integrations/smime/prerequisites.rst:6 +msgid "" +"(Use this to ✒️ **sign outgoing messages** and 🔓 **decrypt incoming " +"messages**.)" +msgstr "" +"(Verwenden Sie dies, um ✒️ **Ausgehende Nachrichten zu signieren** und 🔓 " +"**Eingehende Nachrichten zu entschlüsseln**.)" -#: ../system/variables.rst:112 -msgid "Hour of day in 24h notation with zero-padding" +#: ../system/integrations/smime/prerequisites.rst:9 +msgid "" +"Certificates belonging your contacts, or their issuing certificate authority " +"(CA)" msgstr "" -"Stunde des Tages in 24-Stunden-Schreibweise, ggf. mit vorangestellter Null" +"Zertifikate, die Ihren Kontakten gehören, oder deren ausstellender " +"Zertifizierungsstelle (CA)" -#: ../system/variables.rst:113 -msgid "Use ``%k`` for hour without zero-padding" -msgstr "Verwenden Sie ``%k`` für Stunden ohne führende Null" +#: ../system/integrations/smime/prerequisites.rst:11 +msgid "" +"(Use these to ✅ **verify incoming message signatures** and 🔒 **encrypt " +"outgoing messages**.)" +msgstr "" +"(Verwenden Sie diese, um ✅ **die Signaturen eingehender Nachrichten zu " +"überprüfen** und 🔒 **ausgehende Nachrichten zu verschlüsseln**.)" -#: ../system/variables.rst:114 -msgid "``%I``" -msgstr "``%I``" +#: ../system/integrations/smime/prerequisites.rst:14 +msgid "🙋 **I'm new to S/MIME. Where can I get a certificate?**" +msgstr "🙋 **Ich bin neu in S/MIME. Woher bekomme ich ein Zertifikat?**" -#: ../system/variables.rst:115 -msgid "Hour of day in 12h notation with zero-padding" -msgstr "Uhrzeit im 12-Stunden-Format, ggf. mit vorangestellter Null" +#: ../system/integrations/smime/prerequisites.rst:16 +msgid "" +"The easiest way to get certificates is to buy an annual subscription through " +"a commercial CA, such as:" +msgstr "" +"Der einfachste Weg, Zertifikate zu erhalten, ist der Kauf eines " +"Jahresabonnements über eine kommerzielle Zertifizierungsstelle, wie z.B.:" -#: ../system/variables.rst:116 +#: ../system/integrations/smime/prerequisites.rst:19 msgid "" -"Use ``%l`` for hour without zero-padding and ``%p`` / ``%P`` for meridian " -"indicator" +"`Sectigo (formerly Comodo) `_" msgstr "" -"Verwenden Sie ``%l`` für die Stunde ohne vorangestellte Null und ``%p`` / " -"``%P`` für den Tageszeit-Indikator" +"`Sectigo (ehemals Comodo) `_" -#: ../system/variables.rst:117 -msgid "``%M``" -msgstr "``%M``" +#: ../system/integrations/smime/prerequisites.rst:20 +msgid "`Secorio `_" +msgstr "`Secorio `_" -#: ../system/variables.rst:118 -msgid "Minute of hour" -msgstr "Minute der Stunde" +#: ../system/integrations/smime/prerequisites.rst:21 +msgid "`GlobalSign `_" +msgstr "`GlobalSign `_" -#: ../system/variables.rst:120 -msgid "``%S``" -msgstr "``%S``" +#: ../system/integrations/smime/prerequisites.rst:23 +msgid "(Zammad is not affiliated with these CAs in any way.)" +msgstr "" +"(Zammad ist in keiner Weise mit diesen Zertifizierungsstellen verbunden.)" -#: ../system/variables.rst:121 -msgid "Second of Minute" -msgstr "Sekunde der Minute" +#: ../system/integrations/smime/prerequisites.rst:25 +msgid "" +"You can also generate your own self-signed certificates, but the process is " +"complicated and usually 🙅 **involves extra work for your contacts**." +msgstr "" +"Sie können auch Ihre eigenen selbstsignierten Zertifikate erstellen, aber " +"das Verfahren ist kompliziert und bedeutet in der Regel 🙅 **mehr Arbeit für " +"Ihre Kontakte**." -#: ../system/variables.rst:123 -msgid "``%A``" -msgstr "``%A``" +#: ../system/integrations/smime/prerequisites.rst:29 +msgid "" +"Bear in mind that 🤝 **S/MIME only works if the other party is using it, too." +"**" +msgstr "" +"Denken Sie daran, dass 🤝 **S/MIME nur funktioniert, wenn die andere Partei " +"es auch benutzt.**" -#: ../system/variables.rst:124 -msgid "Weekday name" -msgstr "Name des Wochentags" +#: ../system/integrations/smime/prerequisites.rst:32 +msgid "Certificate and Private Key Checks on Upload" +msgstr "Überprüfung von Zertifikat und privatem Schlüssel beim Hochladen" -#: ../system/variables.rst:125 -msgid "Use ``%a`` for abbreviated name or ``%^A`` for uppercase name" +#: ../system/integrations/smime/prerequisites.rst:34 +msgid "" +"The certificate and public key validation is based on the ``X509v3`` " +"extensions." msgstr "" -"Verwenden Sie ``%a`` für abgekürzte Namen oder ``%^A`` für den Name in " -"Großbuchstaben" - -#: ../system/variables.rst:126 -msgid "``%B``" -msgstr "``%B``" +"Die Validierung von Zertifikaten und öffentlichen Schlüsseln basiert auf den " +"``X509v3``-Erweiterungen." -#: ../system/variables.rst:127 -msgid "Month name" -msgstr "Name des Monats" +#: ../system/integrations/smime/prerequisites.rst:49 +msgid "Uploading a *client certificate*?" +msgstr "Hochladen eines *Kundenzertifikats*?" -#: ../system/variables.rst:128 -msgid "Use ``%b`` for abbreviated name" -msgstr "Verwenden Sie ``%b`` für den abgekürzte Namen" +#: ../system/integrations/smime/prerequisites.rst:41 +msgid "The following attributes are required then:" +msgstr "Die folgenden Attribute sind dann erforderlich:" -#: ../system/variables.rst:129 -msgid "``%U``" -msgstr "``%U``" +#: ../system/integrations/smime/prerequisites.rst:39 +msgid "Subject Alternative Name (at least one email address has to be present)" +msgstr "" +"Subject Alternative Name (mindestens eine E-Mail-Adresse muss vorhanden sein)" -#: ../system/variables.rst:130 -msgid "Week number of current year" -msgstr "Wochennummer des laufenden Jahres" +#: ../system/integrations/smime/prerequisites.rst:40 +msgid "Key Usage (``Digital Signature`` and/or ``Key Encipherment``)" +msgstr "Key Usage (``Digital Signature`` und/oder ``Key Encipherment``)" -#: ../system/variables.rst:131 -msgid "Use ``%W`` for a different calculation method" -msgstr "Verwenden Sie ``%W`` für eine andere Berechnungsmethode" +#: ../system/integrations/smime/prerequisites.rst:41 +msgid "Public key algorithm (either ``RSA`` or ``EC``)" +msgstr "Algorithmus des öffentlichen Schlüssels (entweder ``RSA`` oder ``EC``)" -#: ../system/variables.rst:134 +#: ../system/integrations/smime/prerequisites.rst:43 msgid "" -"We support the known format directives for the Ruby built-in method " -"``strftime`` of the ``DateTime`` class. For more information, see `here " -"`_." +"The Extended Key Usage attribute is optional. If the certificate provides " +"the named attribute, than it must contain the value ``E-mail Protection``." msgstr "" -"Wir unterstützen die bekannten Formatparameter für die in Ruby eingebaute " -"Methode ``strftime`` der Klasse ``DateTime``. Für weitere Informationen " -"siehe `hier `_." - -#: ../system/variables/article.rst:2 -msgid "Articles" -msgstr "Artikel" +"Das Attribut \"Extended Key Usage\" ist optional. Wenn das Zertifikat das " +"genannte Attribut enthält, dann muss es den Wert ``E-mail Protection`` " +"enthalten." -#: ../system/variables/article.rst:4 ../system/variables/config.rst:4 -#: ../system/variables/current-user.rst:4 ../system/variables/ticket.rst:4 +#: ../system/integrations/smime/prerequisites.rst:46 msgid "" -"If you're missing variables or are not sure if something is not working as " -"expected, feel free to ask over at the `Community `_." +"Please note that any usable email adress has to be prefixed with ``email:`` " +"or ``rfc822:``." msgstr "" -"Wenn Sie Variablen vermissen oder sich nicht sicher sind, ob diese wie " -"erwartet funktionieren, fragen Sie gern in unserer `Community `_ nach." +"Bitte beachten Sie, dass jeder verwendbaren Email-Adresse der Zusatz ``email:" +"`` oder ``rfc822:`` vorangestellt werden muss." + +#: ../system/integrations/smime/prerequisites.rst:49 +msgid "The named public key algorithms are mandatory for private keys as well." +msgstr "" +"Die genannten Algorithmen für öffentliche Schlüssel sind auch für private " +"Schlüssel vorgeschrieben." + +#: ../system/integrations/smime/prerequisites.rst:54 +msgid "Uploading a *CA certificate*?" +msgstr "Hochladen eines *CA-Zertifikats*?" -#: ../system/variables/article.rst:6 +#: ../system/integrations/smime/prerequisites.rst:52 msgid "" -"Below you can find all available ticket article-based variables within " -"Zammad. These can be called via Triggers for example. If you're unsure if " -"Zammad does support variables at the point you're at, you can try to type " -"``::`` to check." +"In the case of an uploaded CA certificate, providing the value ``CA:TRUE`` " +"in the attribute *Basic Contstraints*, the previously mentioned attributes " +"are not verified." msgstr "" -"Nachfolgend finden Sie alle verfügbaren Ticketartikel-basierten Variablen in " -"Zammad. Diese können z.B. über Trigger aufgerufen werden. Wenn Sie sich " -"nicht sicher sind, ob Zammad an der von Ihnen gewünschten Stelle Variablen " -"unterstützt, können Sie das prüfen indem Sie ``::`` einzugeben." +"Im Falle eines hochgeladenen CA-Zertifikats, das im Attribut *Basic " +"Contstraints* den Wert ``CA:TRUE`` aufweist, werden die zuvor genannten " +"Attribute nicht überprüft." -#: ../system/variables/article.rst:9 ../system/variables/config.rst:9 -#: ../system/variables/ticket.rst:9 +#: ../system/integrations/smime/prerequisites.rst:56 msgid "" -"The below list gives you an example what kind of data you can expect, it's " -"not intended to explain the data itself." +"In general, the usage of any expired (``Not After``) or not yet valid (``Not " +"Before``) certificate is denied for outgoing emails." msgstr "" -"Die folgende Liste gibt Ihnen ein Beispiel dafür, welche Art von Daten Sie " -"erwarten können. Sie ist nicht dazu gedacht, die Daten selbst zu erklären." +"Im Allgemeinen wird die Verwendung eines abgelaufenen (``Not After``) oder " +"noch nicht gültigen (``Not Before``) Zertifikats für ausgehende E-Mails " +"verweigert." -#: ../system/variables/article.rst:11 -msgid "Article Variables" -msgstr "Artikel-Variablen" +#: ../system/integrations/smime/prerequisites.rst:59 +msgid "Example certificate:" +msgstr "Beispiel für ein Zertifikat:" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "name" -msgstr "Name" +#: ../system/integrations/smime/prerequisites.rst:85 +msgid "" +"Please note that Zammad will distrust senders by default. This means that " +"you're always required to provide certificate data, no matter if for signing " +"or encrypting." +msgstr "" +"Bitte beachten Sie, dass Zammad Absendern standardmäßig misstraut. Das " +"bedeutet, dass Sie immer Zertifikatsdaten angeben müssen, egal ob zum " +"Signieren oder Verschlüsseln." -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "variable" -msgstr "Variable" +#: ../system/integrations/smime/prerequisites.rst:89 +msgid "This is by design and can't be adjusted." +msgstr "Das ist so gewollt und kann nicht geändert werden." -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "example" -msgstr "Beispiel" +#: ../system/integrations/smime/troubleshooting.rst:4 +msgid "" +"All of the system's latest S/MIME activity is displayed in the **Recent " +"Logs** section." +msgstr "" +"Alle aktuellen S/MIME-Aktivitäten des Systems werden im Abschnitt " +"**Aktuellste Protokolle** angezeigt." -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Web" -msgstr "Artikel > Aktualisiert von > Web" +#: ../system/integrations/smime/troubleshooting.rst:11 +msgid "Sample entries of in- and outgoing S/MIME related emails." +msgstr "Beispieleinträge von ein- und ausgehenden S/MIME-bezogenen E-Mails." -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.web}``" -msgstr "``#{article.updated_by.web}``" +#: ../system/integrations/smime/troubleshooting.rst:11 +msgid "" +"Logs report the status and details of all mail, both incoming and outgoing, " +"that used signing/verification or encryption/decryption." +msgstr "" +"Die Protokolle enthalten den Status und die Details aller eingehenden und " +"ausgehenden E-Mails, die signiert/verifiziert oder ver- und entschlüsselt " +"wurden." -#: ../system/variables/article.rst:1 -msgid "``https://zammad.com`` or empty if not set in user object" -msgstr "``https://zammad.com`` oder leer wenn nicht im Benutzerobjekt gesetzt" +#: ../system/integrations/smime/troubleshooting.rst:14 +msgid "" +"This log does **not** include email sent by :doc:`triggers ` or the :doc:`scheduler `. For those, check your " +"``production.log``." +msgstr "" +"Dieses Protokoll enthält **nicht** E-Mails, die von :doc:`triggers ` oder dem :doc:`scheduler ` gesendet wurden. " +"Prüfen Sie dazu bitte Ihr ``production.log``." -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > VIP" -msgstr "Artikel > Aktualisiert von > VIP" +#: ../system/integrations/smime/troubleshooting.rst:20 +msgid "Common Issues" +msgstr "Häufige Probleme" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.vip}``" -msgstr "``#{article.updated_by.vip}``" +#: ../system/integrations/smime/troubleshooting.rst:30 +msgid "I received a signed/encrypted email before I set up S/MIME integration" +msgstr "" +"Ich habe eine signierte/verschlüsselte E-Mail erhalten, bevor ich die S/MIME-" +"Integration eingerichtet habe" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -msgid "``true`` or ``false``" -msgstr "``true`` oder ``false``" +#: ../system/integrations/smime/troubleshooting.rst:23 +msgid "" +"No problem. Once S/MIME has been enabled and the appropriate certificates " +"have been added, agents will be prompted to retry verification/decryption on " +"matching emails." +msgstr "" +"Das ist kein Problem. Sobald S/MIME aktiviert ist und die entsprechenden " +"Zertifikate hinzugefügt wurden, werden die Agenten aufgefordert, die " +"Verifizierung/Entschlüsselung bei entsprechenden E-Mails zu wiederholen." -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Phone" -msgstr "Artikel > Aktualisiert von > Telefon" +#: ../system/integrations/smime/troubleshooting.rst:0 +msgid "Screenshot of user prompt to retry decryption" +msgstr "" +"Screenshot mit Benutzeraufforderung, die Entschlüsselung zu wiederholen" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.phone}``" -msgstr "``#{article.updated_by.phone}``" +#: ../system/integrations/smime/troubleshooting.rst:38 +msgid "The 🔒 **Encrypt** button is disabled" +msgstr "Die 🔒 **Verschlüsseln**-Schaltfläche ist deaktiviert" -#: ../system/variables/article.rst:1 -msgid "``+4930123456789`` or empty if not set in user object" -msgstr "``+4930123456789`` oder leer wenn nicht im Benutzerobjekt gesetzt" +#: ../system/integrations/smime/troubleshooting.rst:33 +msgid "Have you added the recipient's certificate?" +msgstr "Haben Sie das Zertifikat des Empfängers hinzugefügt?" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Note" -msgstr "Artikel > Aktualisiert von > Notiz" +#: ../system/integrations/smime/troubleshooting.rst:34 +msgid "Are you sure the recipient's certificate is valid?" +msgstr "Sind Sie sicher, dass das Zertifikat des Empfängers gültig ist?" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.note}``" -msgstr "``#{article.updated_by.note}``" +#: ../system/integrations/smime/troubleshooting.rst:35 +msgid "Have you checked your ``production.log`` for more details?" +msgstr "Haben Sie Ihr ``production.log`` auf weitere Details überprüft?" -#: ../system/variables/article.rst:1 -msgid "``Some note about user`` or empty if not set in user object" +#: ../system/integrations/smime/troubleshooting.rst:37 +msgid "" +"If encryption doesn't work in the composer, it won't work in :doc:`triggers " +"` or the :doc:`scheduler ` either!" msgstr "" -"``Eine Notiz über den Benutzer`` oder leer wenn nicht am Benutzerobjekt " -"gesetzt" - -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Mobile" -msgstr "Artikel > Aktualisiert von > Mobil" - -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.mobile}``" -msgstr "``#{article.updated_by.mobile}``" - -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Login" -msgstr "Artikel > Aktualisiert von > Login" +"Wenn die Verschlüsselung Ticket-Bereich nicht funktioniert, wird sie auch " +"nicht in :doc:`Triggern ` oder in :doc:`Automatisierungen ` funktionieren!" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.login}``" -msgstr "``#{article.updated_by.login}``" +#: ../system/integrations/smime/troubleshooting.rst:42 +msgid "The ✅ **Sign** button is disabled" +msgstr "Die ✅ **Signieren**-Schaltfläche ist deaktiviert" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -#: ../system/variables/ticket.rst:1 -msgid "``jdoe``" -msgstr "``jdoe``" +#: ../system/integrations/smime/troubleshooting.rst:41 +msgid "" +"Have you added **both the certificate and private key** for your " +"organization?" +msgstr "" +"Haben Sie **Zertifikate und privaten Schlüssel** für Ihre Organisation " +"hinzugefügt?" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Lastname" -msgstr "Artikel > Aktualisiert von > Nachname" +#: ../system/integrations/smime/troubleshooting.rst:42 +msgid "" +"Does the email address on the certificate match the email address of the " +"agent/group composing the email?" +msgstr "" +"Stimmt die E-Mail-Adresse aus dem Zertifikat mit der E-Mail-Adresse der " +"Person/Gruppe überein, die die E-Mail verfasst?" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.lastname}``" -msgstr "``#{article.updated_by.lastname}``" +#: ../system/integrations/smime/troubleshooting.rst:45 +msgid "Error: “Fingerprint already taken”" +msgstr "Fehler: \"Fingerabdruck bereits vorhanden\"" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -#: ../system/variables/ticket.rst:1 -msgid "``Doe`` or empty if not set" -msgstr "``Doe`` oder leer wenn nicht gesetzt" +#: ../system/integrations/smime/troubleshooting.rst:45 +msgid "Are you sure you haven't added this certificate already?" +msgstr "" +"Sind Sie sicher, dass Sie dieses Zertifikat nicht bereits hinzugefügt haben?" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Firstname" -msgstr "Artikel > Aktualisiert von > Vorname" +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Error: “❌ invalid byte sequence in UTF-8”" +msgstr "Fehler: \"❌ ungültige Bytefolge in UTF-8\"" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.firstname}``" -msgstr "``#{article.updated_by.firstname}``" +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Please ensure to provide PEM formatted certificate and keys." +msgstr "" +"Bitte stellen Sie sicher, dass Sie das Zertifikat und die Schlüssel im PEM-" +"Format bereitstellen." -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "``Joe`` or empty if not set" -msgstr "``Joe`` oder leer wenn nicht gesetzt" +#: ../system/integrations/smime/troubleshooting.rst:49 +msgid "Did you check if the provided file is a valid certificate or key?" +msgstr "" +"Haben Sie überprüft, ob es sich bei der bereitgestellten Datei um ein " +"gültiges Zertifikat oder einen gültigen Schlüssel handelt?" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Fax" -msgstr "Artikel > Aktualisiert von > Fax" +#: ../system/integrations/zabbix.rst:2 +msgid "Zabbix Integration" +msgstr "Zabbix-Integration" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.fax}``" -msgstr "``#{article.updated_by.fax}``" +#: ../system/integrations/zabbix.rst:5 +msgid "" +"This guide describes how to integrate your Zabbix 5.4 installation with " +"Zammad using the Zabbix webhook feature. This guide will provide " +"instructions on setting up a media type, a user and an action in Zabbix." +msgstr "" +"Diese Anleitung beschreibt, wie Sie Ihre Zabbix 5.4-Installation mit Zammad " +"unter Verwendung der Zabbix-Webhook-Funktion integrieren. Sie enthält " +"Anweisungen zum Einrichten eines Medientyps, eines Benutzers und einer " +"Aktion in Zabbix." -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Email" -msgstr "Artikel > Aktualisiert von > Email" +#: ../system/integrations/zabbix.rst:12 +msgid "Zammad with enabled HTTP Token Authentication" +msgstr "Zammad mit aktivierter HTTP-Token-Authentifizierung" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.email}``" -msgstr "``#{article.updated_by.email}``" +#: ../system/integrations/zabbix.rst:13 +msgid "Zabbix version 5.4 or higher" +msgstr "Zabbix Version 5.4 oder höher" -#: ../system/variables/article.rst:1 -msgid "``jdoe@example.com``" -msgstr "``jdoe@example.com``" +#: ../system/integrations/zabbix.rst:16 +msgid "Setting up a Zammad" +msgstr "Einrichten von Zammad" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Department" -msgstr "Artikel > Aktualisiert von > Abteilung" +#: ../system/integrations/zabbix.rst:18 +msgid "Enable **API Token Access** in Settings > System > API." +msgstr "" +"Aktivieren Sie **API Token Zugriff** unter Einstellungen > System > API." -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.department}``" -msgstr "``#{article.updated_by.department}``" - -#: ../system/variables/article.rst:1 -msgid "``Sales`` or empty if not set in user object" -msgstr "``Sales`` oder leer wenn nicht am Benutzerobjekt gesetzt" +#: ../system/integrations/zabbix.rst:20 +msgid "" +"Create a **new user** for a Zabbix alerter with an **email address** and " +"create a personal user token with **ticket.agent** permissions." +msgstr "" +"Erstellen Sie einen **neuen Benutzer** für eine Zabbix-Benachrichtigung mit " +"einer **E-Mail-Adresse** und erstellen Sie ein persönliches Benutzertoken " +"mit **ticket.agent**-Berechtigungen." -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Address" -msgstr "Artikel > Aktualisiert von > Adresse" +#: ../system/integrations/zabbix.rst:24 +msgid "Zabbix Webhook Configuration" +msgstr "Zabbix Webhook-Konfiguration" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.address}``" -msgstr "``#{article.updated_by.address}``" +#: ../system/integrations/zabbix.rst:27 +msgid "Create a Global Macro" +msgstr "Ein globales Makro erstellen" -#: ../system/variables/article.rst:1 -msgid "``Some street 1, 12345 Berlin`` or empty if not set in user object" +#: ../system/integrations/zabbix.rst:29 +msgid "" +"Before setting up the **Webhook**, you need to setup the global macro " +"**{$ZABBIX.URL}**, which must contain the **URL** to the **Zabbix frontend**." msgstr "" -"``Irgendeine Straße 1, 12345 Berlin`` oder leer wenn nicht am Benutzerobjekt " -"gesetzt" +"Bevor Sie den **Webhook** einrichten, müssen Sie das globale Makro " +"**{$ZABBIX.URL}** einrichten, das die **URL** zum **Zabbix-Frontend** " +"enthalten muss." -#: ../system/variables/article.rst:1 -msgid "Article > Updated" -msgstr "Artikel > Aktualisiert" +#: ../system/integrations/zabbix.rst:33 +msgid "" +"In the **Administration** > **Media types** section, import the `Template`_." +msgstr "" +"Importieren Sie im Bereich **Administration** > **Media types** das " +"`Template`_." -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_at}``" -msgstr "``#{article.updated_at}``" +#: ../system/integrations/zabbix.rst:38 +msgid "Open the added **Zammad** media type and set:" +msgstr "Öffnen Sie den hinzugefügten Medientyp **Zammad** und stellen Sie ein:" -#: ../system/variables/article.rst:1 -msgid "``2019-10-08 15:24:47 UTC``" -msgstr "``2019-10-08 15:24:47 UTC``" +#: ../system/integrations/zabbix.rst:40 +msgid "**zammad\\_access\\_token** to the your **Personal User Token**" +msgstr "**zammad\\_access\\_token** zu Ihrem **Personal User Token**" -#: ../system/variables/article.rst:1 -msgid "Article > Type > Name" -msgstr "Artikel > Typ > Name" +#: ../system/integrations/zabbix.rst:41 +msgid "" +"**zammad\\_url** to the **frontend URL** of your **Zammad** installation" +msgstr "**zammad\\_url** zur **frontend URL** Ihrer **Zammad**-Installation" -#: ../system/variables/article.rst:1 -msgid "``#{article.type.name}``" -msgstr "``#{article.type.name}``" +#: ../system/integrations/zabbix.rst:43 +msgid "**zammad\\_customer** to your **Zammad user email**." +msgstr "**zammad\\_customer** zu Ihrer **Zammad-Benutzer-E-Mail**." -#: ../system/variables/article.rst:1 +#: ../system/integrations/zabbix.rst:44 msgid "" -"``email`` (`list of article types `_)" +"**zammad\\_enable\\_tags** to **true** or **false** to enable or disable " +"trigger tags. **Important**: if you enable tag support, each tag is set with " +"a separate request." msgstr "" -"``email`` (`Liste der Artikeltypen `_)" - -#: ../system/variables/article.rst:1 -msgid "Article > To" -msgstr "Artikel > An" - -#: ../system/variables/article.rst:1 -msgid "``#{article.to}``" -msgstr "``#{article.to}``" +"**zammad\\_enable\\_tags** auf **true** oder **false**, um Trigger-Tags zu " +"aktivieren oder zu deaktivieren. **Wichtig**: Wenn Sie die Tag-Unterstützung " +"aktivieren, wird jedes Tag mit einer separaten Anfrage gesetzt." -#: ../system/variables/article.rst:1 -msgid "``helpdesk@example.com``" -msgstr "``helpdesk@example.com``" +#: ../system/integrations/zabbix.rst:48 +msgid "" +"If you want to prioritize issues according to **severity** values in Zabbix, " +"you can define mapping parameters:" +msgstr "" +"Wenn Sie Probleme in Zabbix nach **Schweregrad** priorisieren möchten, " +"können Sie Zuordnungsparameter definieren:" -#: ../system/variables/article.rst:1 -msgid "Article > TicketID" -msgstr "Artikel > Ticket-ID" +#: ../system/integrations/zabbix.rst:51 +msgid "**severity\\_**: Zammad priority ID" +msgstr "**severity\\_**: Zammad priority ID" -#: ../system/variables/article.rst:1 -msgid "``#{article.ticket_id}``" -msgstr "``#{article.ticket_id}``" +#: ../system/integrations/zabbix.rst:53 +msgid "Click the **Update** button to save the **Webhook** settings." +msgstr "" +"Klicken Sie auf die Schaltfläche **Aktualisieren**, um die **Webhook-" +"Einstellungen** zu speichern." -#: ../system/variables/article.rst:1 -msgid "``1`` (not ticket number)" -msgstr "``1`` (nicht Ticketnummer)" +#: ../system/integrations/zabbix.rst:55 +msgid "" +"To receive notifications in **Zammad**, you need to create a **Zabbix user** " +"and add **Media** with the **Zammad** type." +msgstr "" +"Um Benachrichtigungen in **Zammad** zu erhalten, müssen Sie einen **Zabbix-" +"Benutzer** anlegen und **Medien** mit dem Typ **Zammad** hinzufügen." -#: ../system/variables/article.rst:1 -msgid "Article > Subject" -msgstr "Artikel > Betreff" +#: ../system/integrations/zabbix.rst:58 +msgid "" +"For **Send to**: enter any text, as this value is not used, but is required." +msgstr "" +"Für **Send to**: Geben Sie einen beliebigen Text ein, da dieser Wert nicht " +"verwendet wird, aber erforderlich ist." -#: ../system/variables/article.rst:1 -msgid "``#{article.subject}``" -msgstr "``#{article.subject}``" +#: ../system/integrations/zabbix.rst:61 +msgid "" +"For more information, use the `Zabbix documentation `_." +msgstr "" +"Weitere Informationen finden Sie in der `Zabbix-Dokumentation `_." -#: ../system/variables/article.rst:1 -msgid "``My amazing subject``" -msgstr "``Mein tolles Betreff``" +#: ../system/maintenance.rst:2 +msgid "Maintenance" +msgstr "Wartung" -#: ../system/variables/article.rst:1 -msgid "Article > Sender > Name" -msgstr "Artikel > Sender > Name" +#: ../system/maintenance.rst:4 +msgid "" +"Zammad comes with a maintenance mode that you can use for e.g. updating the " +"instance or changing settings while restricting availability and functions." +msgstr "" +"Zammad verfügt über einen Wartungsmodus, den Sie z.B. zum Aktualisieren der " +"Instanz oder zum Ändern von Einstellungen verwenden können, wobei die " +"Verfügbarkeit und die Funktionen eingeschränkt werden." -#: ../system/variables/article.rst:1 -msgid "``#{article.sender.name}``" -msgstr "``#{article.sender.name}``" +#: ../system/maintenance.rst:13 +msgid "Mode" +msgstr "Modus" -#: ../system/variables/article.rst:1 -msgid "``Customer``, ``Agent`` or ``System``" -msgstr "``Customer``, ``Agent`` oder ``System``" +#: ../system/maintenance.rst:8 +msgid "The mode setting allows you to enable or disable the maintenance mode." +msgstr "" +"Mit dem Modus-Schalter können Sie den Wartungsmodus aktivieren oder " +"deaktivieren." -#: ../system/variables/article.rst:1 -msgid "Article > Visibility" -msgstr "Artikel > Sichtbarkeit" +#: ../system/maintenance.rst:10 +msgid "Defaults to *off*." +msgstr "Die Standardeinstellung ist *aus*." -#: ../system/variables/article.rst:1 -msgid "``#{article.internal}``" -msgstr "``#{article.internal}``" +#: ../system/maintenance.rst:12 +msgid "" +"The maintenance mode will restrict access to administrative roles only. This " +"means agents and customers are logged off." +msgstr "" +"Im Wartungsmodus ist der Zugriff nur auf administrative Rollen beschränkt. " +"Das bedeutet, dass Agenten und Kunden abgemeldet sind." -#: ../system/variables/article.rst:1 -msgid "``false`` or ``true`` (false if not internal)" -msgstr "``false`` oder ``true`` (false wenn nicht intern)" +#: ../system/maintenance.rst:23 +msgid "@Login" +msgstr "@Login" -#: ../system/variables/article.rst:1 -msgid "Article > From" -msgstr "Artikel > Von" +#: ../system/maintenance.rst:16 +msgid "" +"This setting allows you to provide a login message within a green banner " +"above the login screen. Click into the green banner in the settings page to " +"adjust your message. To activate the message, activate the *@Login* setting." +msgstr "" +"Mit dieser Einstellung können Sie eine Login-Nachricht in einem grünen " +"Banner über dem Login-Bildschirm anzeigen. Klicken Sie in das grüne Banner " +"auf der Einstellungsseite, um Ihre Nachricht anzupassen. Um die Nachricht zu " +"aktivieren, aktivieren Sie den Schalter *@Login*." -#: ../system/variables/article.rst:1 -msgid "``#{article.from}``" -msgstr "``#{article.from}``" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing the default login message within the\n" +"settings page" +msgstr "Screenshot zeigt die Standard-Anmeldung auf der Einstellungsseite" -#: ../system/variables/article.rst:1 +#: ../system/maintenance.rst:26 msgid "" -"``Joe Doe `` may differ, depends on ``FROM`` of send mail" +"Send an informative message to **all active sessions**. This comes handy to " +"inform your agents e.g. about mayor outages or to force reloads after " +"configuration changes." msgstr "" -"``Joe Doe `` kann abweichen, kommt auf ``FROM`` der " -"gesendeten E-Mail an" - -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Web" -msgstr "Artikel > Erstellt von > Web" +"Senden Sie eine informative Nachricht an **alle angemeldeten Benutzer**. " +"Dies ist nützlich, um Ihre Agenten z.B. über größere Ausfälle zu informieren " +"oder um nach Konfigurationsänderungen einen Reload zu erzwingen." -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.web}``" -msgstr "``#{article.created_by.web}``" +#: ../system/maintenance.rst:31 +msgid "This is the messages title (slightly bigger than the normal message)." +msgstr "" +"Dies ist der Titel der Nachricht (etwas größer als die normale Nachricht)." -#: ../system/variables/article.rst:1 -msgid "Article > Created by > VIP" -msgstr "Artikel > Erstellt von > VIP" +#: ../system/maintenance.rst:34 +msgid "The text you want to provide to your logged in sessions." +msgstr "Der Text, den Sie Ihren angemeldeten Benutzern senden wollen." -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.vip}``" -msgstr "``#{article.created_by.vip}``" +#: ../system/maintenance.rst:39 +msgid "Reload application" +msgstr "Applikation neu laden" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Phone" -msgstr "Artikel > Erstellt von > Telefon" +#: ../system/maintenance.rst:37 +msgid "" +"Selecting this option will change the message acceptance button from *Close* " +"(with nothing happening) to *Continue session*, which forces the application " +"to reload." +msgstr "" +"Wenn Sie diese Option wählen, ändert sich die Schaltfläche der " +"Benachrichtigung von *Schließen* (ohne dass etwas passiert) in *Sitzung " +"fortsetzen*, wodurch ein erneutes Laden der Anwendung erzwungen wird." -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.phone}``" -msgstr "``#{article.created_by.phone}``" +#: ../system/maintenance.rst:43 +msgid "" +"If you have customers that are logged in to Zammad, they'll also be notified " +"if they're active in that moment." +msgstr "" +"Wenn Sie Kunden haben, die bei Zammad eingeloggt sind, werden diese " +"ebenfalls benachrichtigt, wenn sie in diesem Moment aktiv sind." -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Note" -msgstr "Artikel > Erstellt von > Notiz" +#: ../system/maintenance.rst:48 +msgid "Example without reload application" +msgstr "Beispiel ohne Anwendungs-Aktualisierung" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.note}``" -msgstr "``#{article.created_by.note}``" +#: ../system/maintenance.rst:52 +msgid "" +"Message setting within Zammad's admin settings without ticket reload " +"application setting." +msgstr "" +"Nachrichteneinstellung in den Verwaltungseinstellungen von Zammad ohne " +"erzwungene Aktualisierung." -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Mobile" -msgstr "Artikel > Erstellt von > Mobil" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing the send message settings without ticket\n" +"reload application set" +msgstr "" +"Screenshot mit den Einstellungen für das Senden von Nachrichten ohne " +"Aktualisierung der Anwendung" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.mobile}``" -msgstr "``#{article.created_by.mobile}``" +#: ../system/maintenance.rst:61 ../system/maintenance.rst:85 +msgid "" +"The modal all other active sessions will see upon pressing *Send to clients*." +msgstr "" +"Der Dialog, den alle anderen aktiven Sitzungen sehen, wenn Sie auf *An " +"Clients senden* drücken." -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Login" -msgstr "Artikel > Erstellt von > Login" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing modal caused by maintenance's message\n" +"without reload application ticket" +msgstr "Screenshot mit Benachrichtigung ohne Aktualisierung der Anwendung" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.login}``" -msgstr "``#{article.created_by.login}``" +#: ../system/maintenance.rst:72 +msgid "Example with reload application" +msgstr "Beispiel mit Anwendungs-Aktualisierung" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Lastname" -msgstr "Artikel > Erstellt von > Nachname" +#: ../system/maintenance.rst:76 +msgid "" +"Message setting within Zammad's admin settings with ticket reload " +"application setting." +msgstr "" +"Nachrichteneinstellung in den Verwaltungseinstellungen von Zammad mit " +"erzwungener Aktualisierung." -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.lastname}``" -msgstr "``#{article.created_by.lastname}``" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing the send message settings with ticket\n" +"reload application set" +msgstr "" +"Screenshot mit den Einstellungen für das Senden von Nachrichten mit " +"Aktualisierung der Anwendung" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Firstname" -msgstr "Artikel > Erstellt von > Vorname" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing modal caused by maintenance's message\n" +"with reload application ticket" +msgstr "Screenshot mit Benachrichtigung mit Aktualisierung der Anwendung" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.firstname}``" -msgstr "``#{article.created_by.firstname}``" +#: ../system/monitoring.rst:2 +msgid "Monitoring" +msgstr "Monitoring (Überwachung)" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Fax" -msgstr "Artikel > Erstellt von > Fax" +#: ../system/monitoring.rst:4 +msgid "" +"This function is only available in self hosted instances. If you use Zammad " +"in our cloud, we are monitoring the system on our own and take steps to fix " +"potential problems directly." +msgstr "" +"Diese Funktion ist nur in selbst gehosteten Instanzen verfügbar. Wenn Sie " +"Zammad in unserer Cloud nutzen, überwachen wir das System selbst und " +"ergreifen Maßnahmen, um mögliche Probleme direkt zu beheben." -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.fax}``" -msgstr "``#{article.created_by.fax}``" +#: ../system/monitoring.rst:11 +msgid "" +"On the monitoring page, you can see the current health state of Zammad under " +"\"*Current Status*\" at the bottom. This can be useful if you want to have a " +"look if everything is up and running. As an example, you could have a look " +"in the monitoring when you assume that some emails aren't processed from " +"Zammad." +msgstr "" +"Auf der Monitoring-Seite können Sie den aktuellen Zustand von Zammad unter " +"\"*Aktueller Status*\" am unteren Rand sehen. Dies kann nützlich sein, wenn " +"Sie nachsehen wollen, ob alles funktioniert. Zum Beispiel können Sie einen " +"Blick ins Monitoring werfen, wenn Sie vermuten, dass einige E-Mails von " +"Zammad nicht verarbeitet werden." -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Email" -msgstr "Artikel > Erstellt von > Email" +#: ../system/monitoring.rst:17 +msgid "**Can't receive an email and the monitoring response is \"healthy\"?**" +msgstr "" +"**Können Sie keine E-Mail empfangen, aber das Monitoring meldet \"kein " +"Vorfälle\"?**" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.email}``" -msgstr "``#{article.created_by.email}``" +#: ../system/monitoring.rst:19 +msgid "" +"Zammad will just inform you about unprocessable emails. This is not the case " +"for oversized emails. You can adjust the maximum email size in :doc:`../" +"channels/email/settings`." +msgstr "" +"Zammad informiert Sie nur über nicht verarbeitbare E-Mails. Das ist hingegen " +"bei übergroßen E-Mails nicht der Fall. Sie können die maximale E-Mail-Größe " +"in :doc:`../channels/email/settings` einstellen." -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Department" -msgstr "Artikel > Erstellt von > Abteilung" +#: ../system/monitoring.rst:24 +msgid "Monitoring API" +msgstr "Monitoring API" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.department}``" -msgstr "``#{article.created_by.department}``" +#: ../system/monitoring.rst:26 +msgid "" +"Beside the indication in the monitoring page, you can also use an external " +"monitoring tool to monitor Zammad's health. To request the health of Zammad, " +"you need to provide the API key (token) to the external monitoring tool. You " +"can copy the token from the \"*Current Token*\" field as well as the whole " +"API endpoint of your system (\"*Health Check*\" field), in which the API " +"token is already included." +msgstr "" +"Neben der Anzeige auf der Monitoring-Seite können Sie auch ein externes " +"Monitoring-Tool verwenden, um den Zustand von Zammad zu überwachen. Um den " +"Zustand von Zammad abzufragen, müssen Sie dem externen Monitoring-Tool den " +"API-Schlüssel (Token) zur Verfügung stellen. Sie können den Token sowohl aus " +"dem Feld \"*Aktueller Token*\" als auch aus dem gesamten API-Endpunkt Ihres " +"Systems (Feld \"*Gesundheits-Check*\") kopieren, in dem der API-Token " +"bereits enthalten ist." -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Address" -msgstr "Artikel > Erstellt von > Adresse" +#: ../system/monitoring.rst:37 +msgid "Screenshot showing Current Token and Health Check" +msgstr "Screenshot mit aktuellem Token und Gesundheits-Check" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.address}``" -msgstr "``#{article.created_by.address}``" +#: ../system/monitoring.rst:37 +msgid "Screenshot showing Token and Health Check" +msgstr "Screenshot mit Token und Gesundheits-Check" -#: ../system/variables/article.rst:1 -msgid "Article > Created" -msgstr "Artikel > Erstellt" +#: ../system/monitoring.rst:39 +msgid "" +"In addition to that, you can reset the auto-generated token to make sure " +"that already configured monitoring systems won't work anymore. So, please " +"use this \"*Reset*\" button only if you know what you do!" +msgstr "" +"Darüber hinaus können Sie das automatisch generierte Token zurücksetzen, um " +"sicherzustellen, dass bereits konfigurierte Monitoring-Systeme nicht mehr " +"funktionieren. Bitte verwenden Sie diese Schaltfläche \"*Zurücksetzen*\" " +"nur, wenn Sie wissen, was Sie tun!" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_at}``" -msgstr "``#{article.created_at}``" +#: ../system/monitoring.rst:44 +msgid "Example Output" +msgstr "Beispiel Ausgabe" -#: ../system/variables/article.rst:1 -msgid "Article > Cc" -msgstr "Artikel > CC" +#: ../system/monitoring.rst:0 +msgid "No issues found" +msgstr "keine Vorfälle" -#: ../system/variables/article.rst:1 -msgid "``#{article.cc}``" -msgstr "``#{article.cc}``" +#: ../system/monitoring.rst:48 ../system/monitoring.rst:60 +msgid "**Indicator in Zammad**:" +msgstr "**Indikator in Zammad**:" -#: ../system/variables/article.rst:1 -msgid "``jdoe@example.com, company@example.com``" -msgstr "``jdoe@example.com, firma@example.com``" +#: ../system/monitoring.rst:0 +msgid "Screenshot showing monitoring with no issues" +msgstr "Screenshot des Monitoring ohne Probleme" -#: ../system/variables/article.rst:1 -msgid "Article > Text" -msgstr "Artikel > Text" +#: ../system/monitoring.rst:54 ../system/monitoring.rst:66 +msgid "**API response**::" +msgstr "**API-Antwort**::" -#: ../system/variables/article.rst:1 -msgid "``#{article.body}``" -msgstr "``#{article.body}``" +#: ../system/monitoring.rst:0 +msgid "Issues were found" +msgstr "Es wurden Probleme festgestellt" -#: ../system/variables/article.rst:1 -msgid "``Test`` without formatting (plain)" -msgstr "``Test`` ohne Formatierung" +#: ../system/monitoring.rst:0 +msgid "Screenshot showing monitoring with issues" +msgstr "Screenshot des Monitoring mit Problemen" -#: ../system/variables/article.rst:1 -msgid "Article Text as HTML (not referenced)" -msgstr "Artikel-Text als HTML (nicht referenziert)" +#: ../system/objects.rst:2 +msgid "Objects" +msgstr "Objekte" -#: ../system/variables/article.rst:1 -msgid "``#{article.body_as_html}``" -msgstr "``#{article.body_as_html}``" +#: ../system/objects.rst:4 +msgid "" +"In Zammad you can add your own fields to tickets, users, organizations and " +"even groups (these are called \"objects\"). This can be useful if you need " +"to add further information to a ticket or any other object in Zammad and the " +"information doesn't fit in any existing field." +msgstr "" +"In Zammad können Sie Ihre eigenen Felder zu Tickets, Benutzern, " +"Organisationen und sogar Gruppen hinzufügen (diese werden \"Objekte\" " +"genannt). Dies kann nützlich sein, wenn Sie weitere Informationen zu einem " +"Ticket oder einem anderen Objekt in Zammad hinzufügen müssen und die " +"Informationen in kein vorhandenes Feld passen." -#: ../system/variables/article.rst:1 -msgid "``Test`` with formatting" -msgstr "``Test`` mit Formatierung" +#: ../system/objects.rst:11 +msgid "" +"Try to avoid deleting attributes (and disable them instead) as Zammad might " +"run into unexpected conditions if they are referenced somewhere." +msgstr "" +"Versuchen Sie, das Löschen von Attributen zu vermeiden (und deaktivieren Sie " +"sie stattdessen), da Zammad unvorhergesehen reagieren kann, wenn irgendwo " +"auf sie verwiesen wird." -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "Ticket > Article#" -msgstr "Ticket > Artikel#" +#: ../system/objects.rst:16 +msgid "" +"Here's an overview of object attributes. On the upper right you can add new " +"attributes. By default, there will be no custom fields - standard attributes " +"will be grayed out, you can't delete or change those. You can edit custom " +"attributes (they are displayed in black font and have a trash bin on the " +"right side) just by clicking on them." +msgstr "" +"Hier finden Sie eine Übersicht über die Objektattribute. Oben rechts können " +"Sie neue Attribute hinzufügen. Standardmäßig gibt es keine " +"benutzerdefinierten Felder - Standardattribute sind ausgegraut, Sie können " +"diese nicht löschen oder ändern. Sie können benutzerdefinierte Attribute " +"bearbeiten (sie werden in schwarzer Schrift angezeigt und haben einen " +"Mülleimer auf der rechten Seite), indem Sie einfach auf sie klicken." -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "``#{ticket.article_count}``" -msgstr "``#{ticket.article_count}``" +#: ../system/objects.rst:24 +msgid "" +"Attributes you add to Zammad, no matter if they have default values or not, " +"will not update existing information. This means a new ticket field " +"technically will be empty unless you populate it." +msgstr "" +"Attribute, die Sie zu Zammad hinzufügen, egal ob sie Standardwerte haben " +"oder nicht, aktualisieren bestehende Informationen (z.B. Tickets) nicht. Das " +"bedeutet, dass ein neues Ticketfeld technisch gesehen leer sein wird, wenn " +"Sie es nicht ausfüllen." -#: ../system/variables/article.rst:1 -msgid "``1`` number of ticket articles" -msgstr "``1`` Anzahl der Ticket-Artikel" +#: ../system/objects.rst:28 +msgid "" +"Especially in ticket scope this also means that newly added attributes will " +"be indicated as \"changed\" to agents that view the ticket. This may " +"interfere with Zammad's tabs behavior." +msgstr "" +"Insbesondere im Ticketbereich bedeutet dies auch, dass neu hinzugefügte " +"Attribute den Agenten, die das Ticket ansehen, als \"geändert\" angezeigt " +"werden. Dies kann das Verhalten von Zammad beeinträchtigen." -#: ../system/variables/config.rst:2 -msgid "Config" -msgstr "Konfiguration" +#: ../system/objects.rst:40 +msgid "Ordering Attributes" +msgstr "Anordnung der Attribute" -#: ../system/variables/config.rst:6 +#: ../system/objects.rst:42 msgid "" -"Below you'll find config related variables. These hold useful configuration " -"information that you can use within e.g. triggers to show necessary " -"information to your customer." +"Since Zammad introduced :doc:`/system/core-workflows` the need to have a " +"custom positioning for attributes has become more important than ever." msgstr "" -"Unten finden Sie konfigurationsbezogene Variablen. Diese beinhalten " -"nützliche Informationen zur Konfigurationen die in z.B. Triggern zum " -"Anzeigen notwendiger Informationen für die Kunden genutzt werden können." - -#: ../system/variables/config.rst:11 -msgid "Config Variables" -msgstr "Konfigurations-Variablen" - -#: ../system/variables/config.rst:1 -msgid "Config > Fully Qualified Domain Name" -msgstr "Konfiguration > Vollständig qualifizierter Domänenname" +"Seit Zammad :doc:`/system/core-workflows` eingeführt hat, ist die " +"Notwendigkeit einer benutzerdefinierten Positionierung für Attribute " +"wichtiger denn je geworden." -#: ../system/variables/config.rst:1 -msgid "``#{config.fqdn}``" -msgstr "``#{config.fqdn}``" +#: ../system/objects.rst:45 +msgid "" +"To adjust the position of such an attribute, simply click on the attribute " +"entry in question, scroll down and adjust the position number. Please note " +"that you cannot change the positioning of default attributes." +msgstr "" +"Um die Position eines solchen Attributs anzupassen, klicken Sie einfach auf " +"den betreffenden Attributeintrag, scrollen Sie nach unten und passen Sie die " +"Positionsnummer an. Bitte beachten Sie, dass Sie die Positionierung von " +"Standardattributen nicht ändern können." -#: ../system/variables/config.rst:1 -msgid "``zammad.example.com``" -msgstr "``zammad.example.com``" +#: ../system/objects.rst:49 +msgid "" +"In case two attributes have the same position value, Zammad will sort " +"alphabetically by name automatically." +msgstr "" +"Falls zwei Attribute den gleichen Wert haben, sortiert Zammad automatisch " +"alphabetisch nach Namen." -#: ../system/variables/config.rst:1 -msgid "Config > Ticket Hook" -msgstr "Konfiguration > Ticket-Hook" +#: ../system/objects.rst:None +msgid "" +"Screenshot showing custom attribute entries ordered in between default ones" +msgstr "" +"Screenshot mit benutzerdefinierten Attributen, die zwischen den " +"Standardattributen angeordnet sind" -#: ../system/variables/config.rst:1 -msgid "``#{config.ticket_hook}``" -msgstr "``#{config.ticket_hook}``" +#: ../system/objects.rst:56 +msgid "Updating Database After Adding or Editing Attributes" +msgstr "" +"Aktualisierung der Datenbank nach dem Hinzufügen oder Bearbeiten von " +"Attributen" -#: ../system/variables/config.rst:1 -msgid "``Ticket#``" -msgstr "``Ticket#``" +#: ../system/objects.rst:58 +msgid "" +"When adding or changing attributes, Zammad will not apply the changes " +"instantly, but instead shows you the changed attributes first. If you're " +"ready to go, just click on \"Update database\" to apply the changes to " +"Zammad. If you made a mistake or just want to discard your changes, click " +"\"Discard changes\"." +msgstr "" +"Wenn Sie Attribute hinzufügen oder ändern, übernimmt Zammad die Änderungen " +"nicht sofort, sondern zeigt Ihnen zunächst die geänderten Attribute an. Wenn " +"Sie fertig sind, klicken Sie einfach auf \"Datenbank aktualisieren\", um die " +"Änderungen in Zammad zu übernehmen. Wenn Sie einen Fehler gemacht haben oder " +"Ihre Änderungen einfach verwerfen wollen, klicken Sie auf \"Änderungen " +"verwerfen\"." -#: ../system/variables/config.rst:1 -msgid "Config > HTTP type" -msgstr "Konfiguration > HTTP-Typ" +#: ../system/objects.rst:64 +msgid "" +"After applying the changes with \"Update Database\", a restart of Zammad is " +"**mandatory**. If you don't perform it, you may experience unexpected " +"behavior or even errors. You may want to do this kind of configuration " +"during maintenance windows." +msgstr "" +"Nach der Übernahme der Änderungen mit \"Datenbank aktualisieren\" ist ein " +"Neustart von Zammad **zwingend erforderlich**. Wenn Sie dies nicht tun, kann " +"es zu unerwartetem Verhalten oder sogar zu Fehlern kommen. Sie sollten diese " +"Art der Konfiguration während eines Wartungsfensters durchführen." -#: ../system/variables/config.rst:1 -msgid "``#{config.http_type}``" -msgstr "``#{config.http_type}``" +#: ../system/objects.rst:72 +msgid "" +"Changes on objects require you to update the database to apply these changes." +msgstr "" +"Bei Änderungen an Objekten müssen Sie die Datenbank aktualisieren, um diese " +"Änderungen zu übernehmen." -#: ../system/variables/config.rst:1 -msgid "``https`` or ``http``" -msgstr "``https`` oder ``http``" +#: ../system/objects.rst:75 +msgid "**🤓 Service restarts can be automated**" +msgstr "**🤓 Neustarts können automatisiert werden**" -#: ../system/variables/config.rst:1 -msgid "Config > SystemID" -msgstr "Konfiguration > System-ID" +#: ../system/objects.rst:0 +msgid "Hosted environments automatically restart for you." +msgstr "Gehostete Instanzen starten automatisch neu." -#: ../system/variables/config.rst:1 -msgid "``#{config.system_id}``" -msgstr "``#{config.system_id}``" +#: ../system/objects.rst:0 +msgid "" +"If you're using a self-hosted installation you can use :docs:`environment " +"variables `" +msgstr "" +"Wenn Sie eine selbst gehostete Installation verwenden, können Sie :docs:" +"`Umgebungsvariablen ` verwenden" -#: ../system/variables/config.rst:1 -msgid "``31`` (value between 1 and 99)" -msgstr "``31`` (Wert zwischen 1 und 99)" +#: ../system/objects.rst:82 +msgid "System Attributes" +msgstr "System-Attribute" -#: ../system/variables/config.rst:1 -msgid "Config > Organization" -msgstr "Konfiguration > Organisation" +#: ../system/objects.rst:84 +msgid "" +"Zammad comes with pre-configured attributes. Some of them can't be edited " +"via UI (or at all). This is required for proper operation of Zammad and not " +"a bug." +msgstr "" +"Zammad wird mit vorkonfigurierten Attributen geliefert. Einige von ihnen " +"können nicht über die Benutzeroberfläche (oder grundsätzlich nicht) " +"bearbeitet werden. Dies ist für den ordnungsgemäßen Betrieb von Zammad " +"erforderlich und kein Fehler." -#: ../system/variables/config.rst:1 -msgid "``#{config.organization}``" -msgstr "``#{config.organization}``" +#: ../system/objects.rst:90 +msgid "Ticket State" +msgstr "Ticket-Status" -#: ../system/variables/config.rst:1 +#: ../system/objects.rst:92 msgid "" -"``Zammad GmbH`` value set in `Branding `_" +"If the pre-configured states aren't enough for you or you want to change " +"them, you can do so by clicking on the cogwheel icon in the state row in the " +"ticket tab. But you should be careful when changing pre-configured states. " +"This can lead to unwanted behavior in some cases." msgstr "" -"``Zammad GmbH`` Wert wird unter `Branding `_ gesetzt" +"Wenn Ihnen die vorkonfigurierten Status nicht ausreichen oder Sie sie ändern " +"möchten, können Sie dies tun, indem Sie auf das Zahnradsymbol in der " +"Statuszeile im Tab Ticket klicken. Sie sollten jedoch vorsichtig sein, wenn " +"Sie vorkonfigurierte Status ändern. Dies kann in manchen Fällen zu " +"unerwünschtem Verhalten führen." -#: ../system/variables/config.rst:1 -msgid "Config > Product Name" -msgstr "Konfiguration > Produktname" +#: ../system/objects.rst:None +msgid "Screenshot showing highlighted ticket state attribute" +msgstr "Screenshot mit hervorgehobenem Ticketstatus-Attribut" -#: ../system/variables/config.rst:1 -msgid "``#{config.product_name}``" -msgstr "``#{config.product_name}``" +#: ../system/objects.rst:122 +msgid "Handling of states" +msgstr "Verwalten von Status" -#: ../system/variables/config.rst:1 +#: ../system/objects.rst:102 msgid "" -"``Helpdesk`` value set in `Branding `_" +"In the state configuration screen, you can add new states, disable states or " +"change states." msgstr "" -"``Helpdesk`` Wert wird unter `Branding `_ gesetzt" +"Im Statuskonfigurationsbildschirm können Sie neue Status hinzufügen, " +"deaktivieren oder ändern." -#: ../system/variables/current-user.rst:2 -msgid "Current User" -msgstr "Aktueller Benutzer" +#: ../system/objects.rst:0 +msgid "Screenshot showing table of default ticket states" +msgstr "Screenshot mit Tabelle der Standard-Ticketstatus" -#: ../system/variables/current-user.rst:6 +#: ../system/objects.rst:110 msgid "" -"Current user variables always return values of the current user that caused " -"e.g. a trigger to run." +"To add a new state, click on the \"New Ticket State\" button in the top " +"right corner. To change an existing state, simply click on the affected " +"state. This opens an edit dialog." msgstr "" -"Variablen für den aktuellen Benutzer geben immer die Werte zurück, die den z." -"B. Trigger ausgelöst haben." +"Um einen neuen Status hinzuzufügen, klicken Sie auf die Schaltfläche \"Neuer " +"Ticketstatus\" in der oberen rechten Ecke. Um einen bestehenden Status zu " +"ändern, klicken Sie einfach auf den betreffenden Status. Daraufhin öffnet " +"sich ein Bearbeitungsdialog." -#: ../system/variables/current-user.rst:8 +#: ../system/objects.rst:114 msgid "" -"Due to the above fact, these variables are often not (yet) set or available " -"for usage." +"You can also clone a state or set them to \"Default for new tickets\" or " +"\"Default for follow-ups\" by clicking on the ⁝ action button and select the " +"desired function." msgstr "" -"Aus diesem Grund sind diese Variablen oft (noch) nicht gesetzt oder stehen " -"nicht zur Verfügung." +"Sie können auch einen Status klonen oder ihn als \"Standard bei neuen " +"Tickets\" oder \"Standard bei Rückfragen\" setzen, indem Sie auf die " +"Schaltfläche ⁝ Aktion klicken und die gewünschte Funktion auswählen." -#: ../system/variables/current-user.rst:10 +#: ../system/objects.rst:118 msgid "" -"In situations where e.g. schedulers or triggers run, this most likely is " -"nothing you want to use." +"*Default for new tickets* means that this state is used for every newly " +"created ticket." msgstr "" -"In Situationen, in denen z.B. Automatisierungen oder Trigger laufen, werden " -"Sie das höchstwahrscheinlich nicht verwenden wollen." - -#: ../system/variables/current-user.rst:13 -msgid "Current User Variables" -msgstr "Aktueller Benutzer-Variablen" - -#: ../system/variables/current-user.rst:1 -msgid "Current User > Web" -msgstr "Aktueller Benutzer > Web" +"*Standard bei neuen Tickets* bedeutet, dass dieser Status für jedes neu " +"erstellte Ticket verwendet wird." -#: ../system/variables/current-user.rst:1 -msgid "``#{user.web}``" -msgstr "``#{user.web}``" +#: ../system/objects.rst:121 +msgid "" +"*Default for follow-ups* means that this state is used if the ticket is re-" +"opened after it was closed." +msgstr "" +"*Standard bei Rückfragen* bedeutet, dass dieser Status verwendet wird, wenn " +"das Ticket nach seiner Schließung erneut geöffnet wird." -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``https://zammad.org`` or empty if not set" -msgstr "``https://zammad.org`` oder leer wenn nicht gesetzt" +#: ../system/objects.rst:171 +msgid "Ticket state in detail" +msgstr "Ticketstatus im Detail" -#: ../system/variables/current-user.rst:1 -msgid "Current User > VIP" -msgstr "Aktueller Benutzer > VIP" +#: ../system/objects.rst:125 +msgid "" +"Below you can find a description for each field and option. Please head over " +"to the :ref:`example ` to see the edit dialog." +msgstr "" +"Nachfolgend finden Sie eine Beschreibung für jedes Feld und jede Option. " +"Schauen Sie sich das :ref:`Beispiel ` an, um den " +"Bearbeitungsdialog zu sehen." -#: ../system/variables/current-user.rst:1 -msgid "``#{user.vip}``" -msgstr "``#{user.vip}``" +#: ../system/objects.rst:129 +msgid "" +"This is the name of the state and what you and your agents are seeing when " +"choosing a state somewhere (e.g. in tickets, trigger configuration)." +msgstr "" +"Dies ist der Name des Status und das, was Sie und Ihre Agenten sehen, wenn " +"sie irgendwo einen Status auswählen (z. B. in Tickets, Triggerkonfiguration)." -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``false`` or ``true``" -msgstr "``false`` oder ``true``" +#: ../system/objects.rst:137 +msgid "" +"There are different state types you can choose from. By default, Zammad " +"comes with one state per state type." +msgstr "" +"Es gibt verschiedene Statustypen, aus denen Sie wählen können. Standardmäßig " +"wird Zammad mit einem Status pro Statustyp ausgeliefert." -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Web" -msgstr "Aktueller Benutzer > Aktualisiert von > Web" +#: ../system/objects.rst:140 +msgid "" +"**new**: for states for tickets that are new and it hasn't been worked on " +"them" +msgstr "" +"**Neu**: für Tickets, die neu sind und an denen noch nicht gearbeitet wurde" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.web}``" -msgstr "``#{user.updated_by.web}``" +#: ../system/objects.rst:142 +msgid "" +"**open**: for states for tickets that are in progress and agents are working " +"on them" +msgstr "" +"**offen**: für Tickets, die in Bearbeitung sind und an denen Agenten arbeiten" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > VIP" -msgstr "Aktueller Benutzer > Aktualisiert von > VIP" +#: ../system/objects.rst:144 +msgid "**merged**: for states for tickets that are merged with other tickets" +msgstr "" +"**zusammengefasst**: für Tickets, die mit anderen Tickets zusammengefasst " +"werden" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.vip}``" -msgstr "``#{user.updated_by.vip}``" +#: ../system/objects.rst:145 +msgid "" +"**pending reminder**: for states for tickets that are in progress and you " +"want to set a reminder. (default example: *pending reminder*)" +msgstr "" +"**warten auf Erinnerung**: für Tickets, die in Bearbeitung sind und zu denen " +"Sie eine Erinnerung bekommen möchten. (Standardbeispiel: *Warten auf " +"Erinnerung*)" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Phone" -msgstr "Aktueller Benutzer > Aktualisiert von > Telefon" +#: ../system/objects.rst:147 +msgid "" +"**pending action**: for states for tickets that are waiting for a specified " +"time and then change their state (default example: *pending close*)" +msgstr "" +"**Anstehende Aktion**: für Tickets, die für eine bestimmte Zeit warten und " +"dann ihren Zustand ändern (Standardbeispiel: *Warten auf Schließung*)" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.phone}``" -msgstr "``#{user.updated_by.phone}``" +#: ../system/objects.rst:150 +msgid "" +"**closed**: for states for tickets that are finished and do not need to be " +"processed further" +msgstr "" +"**geschlossen**: für Tickets, die abgeschlossen sind und nicht weiter " +"bearbeitet werden müssen" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``004930123456789`` or empty if not set" -msgstr "``004930123456789`` oder leer wenn nicht gesetzt" +#: ../system/objects.rst:153 +msgid "" +"⚠️ Choosing the correct state type is important! If you are in doubt, have a " +"look on the default states and their types!" +msgstr "" +"⚠️ Die Wahl des richtigen Statustyps ist wichtig! Im Zweifelsfall sollten Sie " +"einen Blick auf die Standardstatus und ihre Typen werfen!" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Note" -msgstr "Aktueller Benutzer > Aktualisiert von > Notiz" +#: ../system/objects.rst:158 +msgid "Ignore escalation" +msgstr "Eskalation ignorieren" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.note}``" -msgstr "``#{user.updated_by.note}``" +#: ../system/objects.rst:157 +msgid "" +"Here you can define whether tickets of this state will count to escalation " +"time or not." +msgstr "" +"Hier können Sie festlegen, ob Tickets dieses Status auf die Eskalationszeit " +"angerechnet werden sollen oder nicht." -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Some note to this user`` or empty if not set" -msgstr "``Eine Notiz zu diesem Benutzer`` oder leer wenn nicht gesetzt" +#: ../system/objects.rst:161 +msgid "" +"You can create a note for the state to inform other admins about the state. " +"This has no effect on tickets." +msgstr "" +"Sie können eine Notiz für den Status erstellen, um andere Administratoren " +"über den Status zu informieren. Dies hat keine Auswirkungen auf Tickets." -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Mobile" -msgstr "Aktueller Benutzer > Aktualisiert von > Mobil" +#: ../system/objects.rst:165 +msgid "Set the state to *active* or *inactive*." +msgstr "Setzen Sie den Status auf *aktiv* oder *inaktiv*." -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.mobile}``" -msgstr "``#{user.updated_by.mobile}``" +#: ../system/objects.rst:167 +msgid "" +"it is technically possible to set all states to inactive. To keep Zammad " +"working in such a case, the inactive flag of one of the states is ignored." +msgstr "" +"Es ist technisch möglich, alle Status auf \"inaktiv\" zu setzen. Damit " +"Zammad auch in einem solchen Fall funktioniert, wird das Inaktiv-setzen " +"eines der Status ignoriert." -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``0049176123456789`` or empty if not set" -msgstr "``0049176123456789`` oder leer wenn nicht gesetzt" +#: ../system/objects.rst:194 +msgid "Ticket state example" +msgstr "Beispiel für einen Ticketstatus" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Login" -msgstr "Aktueller Benutzer > Aktualisiert bei > Login" +#: ../system/objects.rst:174 +msgid "" +"Let's assume we want to create a new state which indicates that the ticket " +"has to wait for a response of a third party (e.g. service contractor or " +"manufacturer) and we want to to be able to set a reminder." +msgstr "" +"Nehmen wir an, wir möchten einen neuen Status erstellen, der anzeigt, dass " +"das Ticket auf eine Antwort eines Dritten (z.B. eines Dienstleisters oder " +"Herstellers) warten muss, und wir möchten eine Erinnerung setzen können." -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.login}``" -msgstr "``#{user.updated_by.login}``" +#: ../system/objects.rst:178 +msgid "" +"First we give the new state a proper name. In this example we call it " +"\"waiting for manufacturer\"." +msgstr "" +"Zunächst geben wir dem neuen Zustand einen Namen. In diesem Beispiel nennen " +"wir ihn \"Warten auf den Hersteller\"." -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Lastname" -msgstr "Aktueller Benutzer > Aktualisiert von > Nachname" +#: ../system/objects.rst:181 +msgid "" +"As state type we choose \"pending reminder\". This indicates that the ticket " +"is still open and we can set a reminder. This reminder can be useful if our " +"manufacturer sometimes isn't responding or we want to remind him to give us " +"an answer." +msgstr "" +"Als Statustyp wählen wir \"warten auf Erinnerung\". Dies zeigt an, dass das " +"Ticket noch offen ist und wir eine Erinnerung einstellen können. Diese " +"Erinnerung kann nützlich sein, wenn unser Hersteller manchmal nicht " +"antwortet oder wir ihn daran erinnern wollen, uns eine Antwort zu geben." -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.lastname}``" -msgstr "``#{user.updated_by.lastname}``" +#: ../system/objects.rst:186 +msgid "" +"We choose \"no\" for \"ignore escalation\" because we want to escalate the " +"tickets even if we are waiting on the manufacturer's feedback." +msgstr "" +"Wir wählen \"nein\" für \"Eskalation ignorieren\", weil wir die Tickets auch " +"dann eskalieren wollen, wenn wir auf die Rückmeldung des Herstellers warten." -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Firstname" -msgstr "Aktueller Benutzer > Aktualisiert von > Vorname" +#: ../system/objects.rst:189 +msgid "The **result** in the creation dialog will look like this:" +msgstr "Das **Ergebnis** im Erstellungsdialog sieht dann so aus:" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.firstname}``" -msgstr "``#{user.updated_by.firstname}``" +#: ../system/objects.rst:0 +msgid "Screenshot showing ticket state creation dialog with example" +msgstr "Screenshot zeigt Dialog zur Erstellung eines Ticketstatus mit Beispiel" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``John`` or empty if not set" -msgstr "``John`` oder leer wenn nicht gesetzt" +#: ../system/objects.rst:199 +msgid "Ticket Priority" +msgstr "Ticket-Priorität" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Fax" -msgstr "Aktueller Benutzer > Aktualisiert von > Fax" +#: ../system/objects.rst:201 +msgid "" +"If the pre-configured priorities aren't enough for you or you want to change " +"them, you can do so by clicking on the cogwheel icon in the priority row in " +"the ticket tab:" +msgstr "" +"Wenn Ihnen die vorkonfigurierten Prioritäten nicht ausreichen oder Sie sie " +"ändern möchten, können Sie dies tun, indem Sie auf das Zahnradsymbol in der " +"Prioritätszeile in der Registerkarte Ticket klicken:" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.fax}``" -msgstr "``#{user.updated_by.fax}``" +#: ../system/objects.rst:None +msgid "Screenshot showing highlighted ticket priority attribute" +msgstr "Screenshot mit hervorgehobenem Ticketprioritätsattribut" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``004930123464789`` or empty if not set" -msgstr "``004930123464789`` oder leer wenn nicht gesetzt" +#: ../system/objects.rst:226 +msgid "Handling of priorities" +msgstr "Verwalten von Prioritäten" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Email" -msgstr "Aktueller Benutzer > Aktualisiert von > Email" +#: ../system/objects.rst:210 +msgid "" +"In the priority configuration screen, you can add new priorities, disable " +"priorities or change priorities." +msgstr "" +"In der Ansicht für die Prioritätskonfiguration können Sie neue Prioritäten " +"hinzufügen, deaktivieren oder ändern." -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.email}``" -msgstr "``#{user.updated_by.email}``" +#: ../system/objects.rst:0 +msgid "Screenshot showing table of default ticket priorities" +msgstr "Screenshot mit Tabelle der Standard-Ticketprioritäten" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``jdoe@customer.tld``" -msgstr "``jdoe@kunde.tld``" +#: ../system/objects.rst:218 +msgid "" +"To add a new priority, click on the \"New Priority\" button in the top right " +"corner. To change an existing priority, simply click on the affected " +"priority. This opens an edit dialog." +msgstr "" +"Um eine neue Priorität hinzuzufügen, klicken Sie auf die Schaltfläche \"Neue " +"Priorität\" in der oberen rechten Ecke. Um eine bestehende Priorität zu " +"ändern, klicken Sie einfach auf die betreffende Priorität. Daraufhin öffnet " +"sich ein Bearbeitungsdialog." -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Department" -msgstr "Aktueller Benutzer > Aktualisiert von > Abteilung" +#: ../system/objects.rst:222 +msgid "" +"You can also clone a priority or set them to \"Default for new tickets\" by " +"clicking on the ⁝ action button and select the desired function." +msgstr "" +"Sie können auch eine Priorität klonen oder sie als \"Standard bei neuen " +"Tickets\" setzen, indem Sie auf die Schaltfläche ⁝ Aktion klicken und die " +"gewünschte Funktion auswählen." -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.department}``" -msgstr "``#{user.updated_by.department}``" +#: ../system/objects.rst:225 +msgid "" +"*Default for new tickets* means that this priority is used for every newly " +"created ticket." +msgstr "" +"*Standard bei neuen Tickets* bedeutet, dass diese Priorität für jedes neu " +"erstellte Ticket verwendet wird." -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Sales`` or empty if not set" -msgstr "``Verkauf`` oder leer wenn nicht gesetzt" +#: ../system/objects.rst:248 +msgid "Priorities in detail" +msgstr "Prioritäten im Detail" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Avatar" -msgstr "Aktueller Benutzer > Aktualisiert von > Avatar" +#: ../system/objects.rst:229 +msgid "Below you can find a description for each field and option." +msgstr "" +"Nachfolgend finden Sie eine Beschreibung für jedes Feld und jede Option." -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.avatar(60,60)}``" -msgstr "``#{user.updated_by.avatar(60,60)}``" +#: ../system/objects.rst:232 +msgid "" +"This is the name of the priority and what you and your agents are seeing " +"when choosing a priority somewhere (e.g. in tickets, trigger configuration)." +msgstr "" +"Dies ist der Name der Priorität und das, was Sie und Ihre Agenten sehen, " +"wenn Sie irgendwo eine Priorität auswählen (z.B. in Tickets, Trigger-" +"Konfiguration)." -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "avatar picture with width and height in pixel (e.g. 60,60)" -msgstr "Avatarbild mit Breite und Höhe in Pixel (z.B. 60,60)" +#: ../system/objects.rst:242 +msgid "Highlight color" +msgstr "Highlight-Farbe" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Address" -msgstr "Aktueller Benutzer > Aktualisiert von > Adresse" +#: ../system/objects.rst:237 +msgid "" +"Switch between *Low priority* (light blue), *High priority* (red) and - " +"(default). This affects the displayed color for ticket titles in overviews." +msgstr "" +"Umschalten zwischen *Niedrige Priorität* (hellblau), *Hohe Priorität* (rot) " +"und - (Standard). Dies wirkt sich auf die angezeigte Farbe für Ticket-Titel " +"in Übersichten aus." -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.address}``" -msgstr "``#{user.updated_by.address}``" +#: ../system/objects.rst:241 +msgid "The color options are currently limited to the mentioned options." +msgstr "Die Farboptionen sind derzeit auf die genannten Optionen beschränkt." -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Some street 1, 12345 Berlin`` or empty if not set" -msgstr "``Irgendeine Straße 1, 12345 Berlin`` oder leer wenn nicht gesetzt" +#: ../system/objects.rst:245 +msgid "" +"You can create a note for the priority to inform other admins about the " +"priority. This has no effect on tickets." +msgstr "" +"Sie können eine Notiz für die Priorität erstellen, um andere Administratoren " +"über die Priorität zu informieren. Dies hat keine Auswirkungen auf Tickets." -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated at" -msgstr "Aktueller Benutzer > Aktualisiert am" - -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_at}``" -msgstr "``#{user.updated_at}``" - -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC``" -msgstr "``2019-10-07 16:25:00 UTC``" - -#: ../system/variables/current-user.rst:1 -msgid "Current User > Phone" -msgstr "Aktueller Benutzer > Telefon" +#: ../system/objects.rst:249 +msgid "Set the priority to *active* or *inactive*." +msgstr "Setzen Sie die Priorität auf *aktiv* oder *inaktiv*." -#: ../system/variables/current-user.rst:1 -msgid "``#{user.phone}``" -msgstr "``#{user.phone}``" +#: ../system/objects/external-data-source-example.rst:2 +msgid "External Data Source" +msgstr "Externe Datenquelle" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Shared organization" -msgstr "Aktueller Benutzer > Organisation > Geteilte Organisation" +#: ../system/objects/external-data-source-example.rst:4 +msgid "" +"We assume you already had a look on :doc:`types` where you can find a " +"description of the individual fields." +msgstr "" +"Wir gehen davon aus, dass Sie bereits einen Blick auf :doc:`types` geworfen " +"haben, wo Sie eine Beschreibung der einzelnen Felder finden können." -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.shared}``" -msgstr "``#{user.organization.shared}``" +#: ../system/objects/external-data-source-example.rst:7 +msgid "" +"To reproduce this example, choose a category you want to add a custom field, " +"click on *New Attribute* and select *External data source field* under " +"*Format*." +msgstr "" +"Um dieses Beispiel zu reproduzieren, wählen Sie eine Kategorie, der Sie ein " +"benutzerdefiniertes Feld hinzufügen möchten, klicken Sie auf *Neues " +"Attribut* und wählen Sie *Externe Daten-Feld* unter *Format*." -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Note" -msgstr "Aktueller Benutzer > Organisation > Notiz" +#: ../system/objects/external-data-source-example.rst:11 +msgid "" +"Our example story is to fetch data from an external product database. We " +"want to add our products to the tickets so that the products can be searched " +"and chosen from a list and also create a link to the product website." +msgstr "" +"In unserem Beispiel geht es darum, Daten aus einer externen Produktdatenbank " +"abzurufen. Wir möchten unsere Produkte zu den Tickets hinzufügen, damit die " +"Produkte gesucht und aus einer Liste ausgewählt werden können, und außerdem " +"einen Link zur Produktwebsite erstellen." -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.note}``" -msgstr "``#{user.organization.note}``" +#: ../system/objects/external-data-source-example.rst:16 +msgid "Base configuration" +msgstr "Basis-Konfiguration" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``A note to the organization of the user`` or empty if not set" +#: ../system/objects/external-data-source-example.rst:None +msgid "Initial steps to configure external data source object type" msgstr "" -"``Eine Notiz in der Organisation des Benutzers`` oder leer, wenn nicht " -"gesetzt" +"Erste Schritte zur Konfiguration des Objekttyps der externen Datenquelle" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Name" -msgstr "Aktueller Benutzer > Organisation > Name" +#: ../system/objects/external-data-source-example.rst:25 +msgid "Name: *product*" +msgstr "Name: *product*" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.name}``" -msgstr "``#{user.organization.name}``" +#: ../system/objects/external-data-source-example.rst:26 +msgid "Display: *Product*" +msgstr "Display: *Product*" -#: ../system/variables/current-user.rst:1 -msgid "``Zammad GmbH``" -msgstr "``Zammad GmbH``" +#: ../system/objects/external-data-source-example.rst:29 +msgid "External data source configuration" +msgstr "Konfiguration der externen Datenquelle" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Domain based assignment" -msgstr "Aktueller Benutzer > Organisation > Domain basierte Zuordnung" +#: ../system/objects/external-data-source-example.rst:31 +msgid "" +"First, enter the search URL making sure it contains ``#{search.term}`` as a " +"parameter:" +msgstr "" +"Geben Sie zunächst die Such-URL ein und vergewissern Sie sich, dass sie " +"``#{search.term}`` als Parameter enthält:" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.domain_assignment}``" -msgstr "``#{user.organization.domain_assignment}``" +#: ../system/objects/external-data-source-example.rst:34 +msgid "**Example:** ``https://dummyjson.com/products/search?q=#{search.term}``" +msgstr "" +"**Beispiel:** ``https://dummyjson.com/products/search?q=#{search.term}``" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Domain" -msgstr "Aktueller Benutzer > Organisation > Domain" +#: ../system/objects/external-data-source-example.rst:36 +msgid "" +"After that, head down to the preview section and enter a search input for " +"the external data source." +msgstr "" +"Danach gehen Sie in den Vorschaubereich und geben einen Suchbegriff für die " +"externe Datenquelle ein." -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.domain}``" -msgstr "``#{user.organization.domain}``" +#: ../system/objects/external-data-source-example.rst:39 +msgid "**Example:** ``mac``" +msgstr "**Beispiel:** ``mac``" -#: ../system/variables/current-user.rst:1 -msgid "``zammad.com`` or empty if not set" -msgstr "``zammad.com`` oder leer wenn nicht gesetzt" +#: ../system/objects/external-data-source-example.rst:41 +msgid "Then you can find a preview of the response data below:" +msgstr "Anschließend finden Sie eine Vorschau der Antwortdaten:" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > VIP" -msgstr "Aktueller Benutzer > Organisation > VIP" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of JSON response based on search term" +msgstr "Vorschau der JSON-Antwort basierend auf dem Suchbegriff" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.vip}``" -msgstr "``#{user.organization.vip}``" +#: ../system/objects/external-data-source-example.rst:48 +msgid "" +"We recommend using the preview to have a look on the structure. There is a " +"top-level element called ``products``. One level below, you can find the " +"attributes ``id`` and ``title``." +msgstr "" +"Wir empfehlen, die Vorschau zu benutzen, um einen Blick auf die Struktur zu " +"werfen. Es gibt ein Top-Level-Element namens ``products``. Eine Ebene " +"darunter finden Sie die Attribute ``id`` und ``title``." -#: ../system/variables/current-user.rst:1 -msgid "Current User > Note" -msgstr "Aktueller Benutzer > Notiz" +#: ../system/objects/external-data-source-example.rst:52 +msgid "**Search result response based on search from example:**" +msgstr "**Suchergebnis-Antwort basierend auf der Suche aus dem Beispiel:**" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.note}``" -msgstr "``#{user.note}``" +#: ../system/objects/external-data-source-example.rst:119 +msgid "" +"To tell the remote system that the desired data is located below the " +"``products`` level, you have to put it in the field *Search result list key*." +msgstr "" +"Um dem entfernten System mitzuteilen, dass sich die gewünschten Daten " +"unterhalb der Ebene ``products`` befinden, müssen Sie dies in das Feld " +"*Search result list key* eintragen." -#: ../system/variables/current-user.rst:1 -msgid "Current User > Mobile" -msgstr "Aktueller Benutzer > Mobil" +#: ../system/objects/external-data-source-example.rst:122 +msgid "" +"After inserting ``products`` in the mentioned field, you get an extended " +"preview. You can find an additional box *Search result list* with a JSON " +"structure. This is the same response as before but stripped from the upper " +"``products`` element by the external data source." +msgstr "" +"Nach dem Einfügen von ``products`` in das genannte Feld, erhalten Sie eine " +"erweiterte Vorschau. Sie können ein zusätzliches Feld *Search result list* " +"mit einer JSON-Struktur finden. Dies ist die gleiche Antwort wie zuvor, aber " +"das obere Element ``products`` wurde von der externen Datenquelle entfernt." -#: ../system/variables/current-user.rst:1 -msgid "``#{user.mobile}``" -msgstr "``#{user.mobile}``" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of JSON response search result list" +msgstr "Vorschau der Suchergebnisliste der JSON-Antwort" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Login" -msgstr "Aktueller Benutzer > Login" +#: ../system/objects/external-data-source-example.rst:132 +msgid "" +"Now you need to provide the keys for the search result values and labels. As " +"already mentioned, we are looking for the ``id`` and the ``title`` of our " +"products. If you haven't already, it is now a good time to look at the " +"preview of the *Search result list*." +msgstr "" +"Nun müssen Sie die Schlüssel für die Werte und Bezeichnungen der " +"Suchergebnisse angeben. Wie bereits erwähnt, suchen wir nach der ``id`` und " +"dem ``title`` unserer Produkte. Wenn Sie es noch nicht getan haben, ist es " +"jetzt ein guter Zeitpunkt, sich die Vorschau der *Suchergebnisliste* " +"anzusehen." -#: ../system/variables/current-user.rst:1 -msgid "``#{user.login}``" -msgstr "``#{user.login}``" +#: ../system/objects/external-data-source-example.rst:197 +msgid "" +"After locating our two keys, we insert them in *search result value key* " +"(``id``) and in *Search result label key* (``title``)." +msgstr "" +"Nachdem wir unsere beiden Schlüssel gefunden haben, fügen wir sie in " +"*Schlüssel Suchergebniswert* (``id``) und in den *Schlüssel " +"Suchergebnisbezeichnung* (``title``) ein." -#: ../system/variables/current-user.rst:1 -msgid "Current User > Lastname" -msgstr "Aktueller Benutzer > Nachname" +#: ../system/objects/external-data-source-example.rst:200 +msgid "" +"Basically, we configured the external data source already and we can see a " +"table in the preview section:" +msgstr "" +"Im Grunde haben wir die externe Datenquelle bereits konfiguriert, und wir " +"können eine Tabelle im Vorschaubereich sehen:" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.lastname}``" -msgstr "``#{user.lastname}``" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of product table based on search term" +msgstr "Vorschau der Produkttabelle auf Basis des Suchbegriffs" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Firstname" -msgstr "Aktueller Benutzer > Vorname" +#: ../system/objects/external-data-source-example.rst:208 +msgid "" +"According to our example story, now just the *Link template* is missing." +msgstr "Gemäß unserem Beispiel fehlt jetzt nur noch das *Link-Template*." -#: ../system/variables/current-user.rst:1 -msgid "``#{user.firstname}``" -msgstr "``#{user.firstname}``" +#: ../system/objects/external-data-source-example.rst:210 +msgid "" +"Please note that this is an optional feature. If you don't want to use such " +"links, of course you don't have to configure it." +msgstr "" +"Bitte beachten Sie, dass dies eine optionale Funktion ist. Wenn Sie solche " +"Links nicht verwenden möchten, müssen Sie sie natürlich auch nicht " +"konfigurieren." -#: ../system/variables/current-user.rst:1 -msgid "Current User > Fax" -msgstr "Aktueller Benutzer > Fax" +#: ../system/objects/external-data-source-example.rst:213 +msgid "" +"We can add now an address where additional product information can be found." +msgstr "" +"Wir können nun eine Adresse hinzufügen, unter der zusätzliche " +"Produktinformationen zu finden sind." -#: ../system/variables/current-user.rst:1 -msgid "``#{user.fax}``" -msgstr "``#{user.fax}``" +#: ../system/objects/external-data-source-example.rst:215 +msgid "Example: ``https://your_domain.com/q=#{ticket.product}``" +msgstr "Beispiel: ``https://ihre_domain.com/q=#{ticket.product}``" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Email" -msgstr "Aktueller Benutzer > Email" +#: ../system/objects/external-data-source-example.rst:217 +msgid "In the example, the parameter means:" +msgstr "In diesem Beispiel bedeutet der Parameter:" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.email}``" -msgstr "``#{user.email}``" +#: ../system/objects/external-data-source-example.rst:219 +msgid "``#{}``: \"Frame\" for the insertion of information" +msgstr "``#{}``: \"Rahmen\" für das Einfügen von Informationen" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Department" -msgstr "Aktueller Benutzer > Abteilung" +#: ../system/objects/external-data-source-example.rst:220 +msgid "``ticket``: object level, where you create your custom object" +msgstr "" +"``ticket``: Objektebene, auf der Sie Ihr benutzerdefiniertes Objekt erstellen" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.department}``" -msgstr "``#{user.department}``" +#: ../system/objects/external-data-source-example.rst:221 +msgid "``product``: name of the (custom) object" +msgstr "``product``: Name des (benutzerdefinierten) Objekts" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Web" -msgstr "Aktueller Benutzer > Erstellt von > Web" +#: ../system/objects/external-data-source-example.rst:223 +msgid "" +"After configuring your *Link template*, there will be another column in the " +"preview. Hovering on the icons in the *Link* column will show you where it " +"forwards you." +msgstr "" +"Nachdem Sie Ihr *Link-Template* konfiguriert haben, wird in der Vorschau " +"eine weitere Spalte angezeigt. Wenn Sie mit der Maus über die Symbole in der " +"Spalte *Link* fahren, sehen Sie, wohin der Link verweist." -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.web}``" -msgstr "``#{user.created_by.web}``" +#: ../system/objects/external-data-source-example.rst:232 +msgid "" +"In our example, one of the links looks like: https://your_domain.com/q=6, " +"where the 6 is the product id." +msgstr "" +"In unserem Beispiel sieht einer der Links so aus: https://ihre_domain.com/" +"q=6, wobei die 6 die Produkt-ID ist." -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > VIP" -msgstr "Aktueller Benutzer > Erstellt von > VIP" +#: ../system/objects/external-data-source-example.rst:235 +msgid "You can find more information regarding the URL in :doc:`types`." +msgstr "Weitere Informationen zur URL finden Sie in :doc:`types`." -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.vip}``" -msgstr "``#{user.created_by.vip}``" +#: ../system/objects/includes/adding-values-hint.include.rst:3 +msgid "" +"Adding values can be tricky for first timers, don't forget to press \"➕ " +"Add\" after typing your values. Otherwise you may loose a value." +msgstr "" +"Das Hinzufügen von Werten kann für Neulinge schwierig sein. Vergessen Sie " +"nicht, nach der Eingabe Ihrer Werte auf \"➕ Hinzufügen\" zu drücken. " +"Andernfalls wird der zuletzt hinzugefügte Wert nicht gespeichert." -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Phone" -msgstr "Aktueller Benutzer > Erstellt von > Telefon" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:1 +#: ../system/objects/includes/reposition-values.include.rst:1 +msgid "**↕️ This field type allows the positioning of its values ↔️**" +msgstr "**↕️ Dieser Feldtyp erlaubt die Positionierung der Werte ↔️**" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.phone}``" -msgstr "``#{user.created_by.phone}``" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:3 +msgid "" +"In order to re-arrange the field values, first edit the field. Then you can " +"use ☰ to drag the values in question to the correct position. If you want to " +"change the layer depth, double click on ☰. With it you can cycle through the " +"available layers." +msgstr "" +"Um die Feldwerte neu anzuordnen, bearbeiten Sie zunächst das Feld. Dann " +"können Sie mit ☰ die betreffenden Werte an die richtige Stelle ziehen. Wenn " +"Sie die Ebenentiefe ändern möchten, doppelklicken Sie auf ☰. Damit können " +"Sie durch die verfügbaren Ebenen wechseln." -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Note" -msgstr "Aktueller Benutzer > Erstellt von > Notiz" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:8 +msgid "When you're ready, submit your changes to save the object attribute." +msgstr "" +"Wenn Sie fertig sind, klicken Sie auf \"Übermitteln\", um das Objektattribut " +"zu speichern." -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.note}``" -msgstr "``#{user.created_by.note}``" +#: :0 ../system/objects/types.rst:0 +msgid "" +"Screencast showing how to re-position values on tree select like\n" +"fields" +msgstr "" +"Screencast zur Neupositionierung von Werten in Feldern wie der Baumauswahl" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Mobile" -msgstr "Aktueller Benutzer > Erstellt von > Mobil" +#: ../system/objects/includes/reposition-values.include.rst:3 +msgid "" +"In order to re-arrange the field values, edit the field and scroll below the " +"values. Make sure to tick the option \"Use custom option sort\"." +msgstr "" +"Um die Feldwerte neu anzuordnen, bearbeiten Sie das Feld und scrollen Sie " +"unter die Tabelle. Vergewissern Sie sich, dass Sie die Option \"Verwende " +"benutzerdefinierte Sortierung\" aktiviert haben." -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.mobile}``" -msgstr "``#{user.created_by.mobile}``" +#: ../system/objects/includes/reposition-values.include.rst:8 +msgid "" +"If you do not tick this field, all manual positioning you did above will be " +"lost upon saving! ☠️" +msgstr "" +"Wenn Sie das nicht aktiviert haben, gehen alle manuell festgelegten " +"Positionen beim Speichern verloren! ☠️" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Login" -msgstr "Aktueller Benutzer > Erstellt von > Login" +#: ../system/objects/includes/reposition-values.include.rst:11 +msgid "" +"Now use ☰ to drag the values in question to the correct position. When " +"you're ready, submit your changes to save the object attribute." +msgstr "" +"Ziehen Sie nun mit ☰ die Einträge an die richtige Position. Wenn Sie fertig " +"sind, übernehmen Sie Ihre Änderungen, um das Objektattribut zu speichern." -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.login}``" -msgstr "``#{user.created_by.login}``" +#: :0 ../system/objects/types.rst:0 +msgid "Screencast showing how to re-position values" +msgstr "Screencast, der zeigt, wie man Einträge neu positioniert" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Lastname" -msgstr "Aktueller Benutzer > Erstellt von > Nachname" +#: ../system/objects/includes/url-template-hint.include.rst:3 +msgid "" +"This field allows using :ref:`URL fields (Link Templates) `." +msgstr "" +"Dieses Feld ermöglicht die Verwendung von :ref:`URL-Feldern (Link-Vorlagen) " +"`." -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.lastname}``" -msgstr "``#{user.created_by.lastname}``" +#: ../system/objects/permissions.rst:2 +msgid "Attribute Permissions" +msgstr "Berechtigungen für Attribute" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Firstname" -msgstr "Aktueller Benutzer > Erstellt von > Vorname" +#: ../system/objects/permissions.rst:7 +msgid "" +"In the object attributes configuration you can define if a field is shown " +"and if the input in the field is mandatory, separated by different screens " +"and for different :doc:`roles/permissions `." +msgstr "" +"In der Konfiguration der Objektattribute können Sie festlegen, ob ein Feld " +"angezeigt wird und ob die Eingabe in das Feld verpflichtend ist, und zwar " +"separat für verschiedene Ansichten und für verschiedene :doc:`Rollen/" +"Berechtigungen `." -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.firstname}``" -msgstr "``#{user.created_by.firstname}``" +#: ../system/objects/permissions.rst:17 +msgid "Screenshot shows object attribute permission table" +msgstr "Screenshot zeigt Objektattribut-Berechtigungstabelle" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Fax" -msgstr "Aktueller Benutzer > Erstellt von > Fax" +#: ../system/objects/permissions.rst:17 +msgid "" +"Some of the possible permissions and screen options for a user object " +"attribute." +msgstr "" +"Einige der möglichen Berechtigungen und Ansichten für ein Attribut eines " +"Benutzerobjekts." -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.fax}``" -msgstr "``#{user.created_by.fax}``" +#: ../system/objects/permissions.rst:19 +msgid "" +"Based on the object context (ticket, agent, organization, user), the " +"selectable roles (to be precise: the required permissions) and screens " +"differ. Be aware that these settings aren't affecting data creation via " +"other channels than the UI." +msgstr "" +"Je nach Objektkontext (Ticket, Agent, Organisation, Benutzer) unterscheiden " +"sich die auswählbaren Rollen (genauer gesagt: die erforderlichen " +"Berechtigungen) und Ansichten. Beachten Sie, dass diese Einstellungen keinen " +"Einfluss auf die Datenerstellung über andere Kanäle als die " +"Benutzeroberfläche haben." -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Email" -msgstr "Aktueller Benutzer > Erstellt von > Email" +#: ../system/objects/permissions.rst:24 +msgid "" +"If you want to have further customization possibilities, you should have a " +"look at the :doc:`core workflows `." +msgstr "" +"Wenn Sie weitere Anpassungsmöglichkeiten brauchen, sollten Sie einen Blick " +"in die :doc:`Core Workflows ` werfen." -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.email}``" -msgstr "``#{user.created_by.email}``" +#: ../system/objects/permissions.rst:28 +msgid "Screens" +msgstr "Ansichten" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Department" -msgstr "Aktueller Benutzer > Erstellt von > Abteilung" +#: ../system/objects/permissions.rst:30 +msgid "" +"In the table below you can find an overview about the different permissions " +"and the available screens Zammad distinguishes between." +msgstr "" +"In der folgenden Tabelle finden Sie eine Übersicht über die verschiedenen " +"Berechtigungen und die verfügbaren Ansichten, die Zammad unterscheidet." -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.department}``" -msgstr "``#{user.created_by.department}``" +#: ../system/objects/permissions.rst:37 +msgid "Screen" +msgstr "Ansicht" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Avatar" -msgstr "Aktueller Benutzer > Erstellt von > Avatar" +#: ../system/objects/permissions.rst:38 +msgid "Available for" +msgstr "Verfügbar für" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.avatar(60,60)}``" -msgstr "``#{user.created_by.avatar(60,60)}``" +#: ../system/objects/permissions.rst:40 +msgid "create" +msgstr "create" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Address" -msgstr "Aktueller Benutzer > Erstellt von > Adresse" +#: ../system/objects/permissions.rst:41 ../system/objects/permissions.rst:52 +#: ../system/objects/permissions.rst:59 ../system/objects/permissions.rst:73 +msgid "admin.user" +msgstr "admin.user" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.address}``" -msgstr "``#{user.created_by.address}``" +#: ../system/objects/permissions.rst:42 ../system/objects/permissions.rst:53 +#: ../system/objects/permissions.rst:60 +msgid "admin.organization" +msgstr "admin.organization" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created at" -msgstr "Aktueller Benutzer > Erstellt am" +#: ../system/objects/permissions.rst:43 ../system/objects/permissions.rst:54 +#: ../system/objects/permissions.rst:61 +msgid "admin.group" +msgstr "admin.group" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_at}``" -msgstr "``#{user.created_at}``" +#: ../system/objects/permissions.rst:44 +msgid "Creation dialog for not yet existing data" +msgstr "Erstellungsdialog für noch nicht vorhandene Daten" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Avatar" -msgstr "Aktueller Benutzer > Avatar" +#: ../system/objects/permissions.rst:45 +msgid "create_middle" +msgstr "create_middle" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.avatar(60,60)}``" -msgstr "``#{user.avatar(60,60)}``" +#: ../system/objects/permissions.rst:46 ../system/objects/permissions.rst:50 +#: ../system/objects/permissions.rst:57 ../system/objects/permissions.rst:66 +#: ../system/objects/permissions.rst:70 +msgid "ticket.customer" +msgstr "ticket.customer" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Address" -msgstr "Aktueller Benutzer > Adresse" +#: ../system/objects/permissions.rst:47 ../system/objects/permissions.rst:51 +#: ../system/objects/permissions.rst:58 ../system/objects/permissions.rst:69 +msgid "ticket.agent" +msgstr "ticket.agent" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.address}``" -msgstr "``#{user.address}``" +#: ../system/objects/permissions.rst:48 +msgid "Ticket create dialog (middle section)" +msgstr "Ticket-Erstellungsdialog (mittlerer Bereich)" -#: ../system/variables/ticket.rst:6 -msgid "" -"Below you can find all available ticket-based variables within Zammad. These " -"can be called via Triggers for example. If you're unsure if Zammad does " -"support variables at the point you're at, you can try to type ``::`` to " -"check." -msgstr "" -"Unten finden Sie alle verfügbaren ticketbasierten Variablen in Zammad. Diese " -"können zum Beispiel in Triggern aufgerufen werden. Wenn Sie unsicher sind, " -"welche Variablen an diesem Punkt unterstützt, tippen Sie einfach ``::`` zum " -"Prüfen." +#: ../system/objects/permissions.rst:49 +msgid "edit" +msgstr "edit" -#: ../system/variables/ticket.rst:12 -msgid "Ticket Variables" -msgstr "Ticket-Variablen" +#: ../system/objects/permissions.rst:55 +msgid "Editing dialog for already existing data" +msgstr "Bearbeitungsdialog für bereits vorhandene Daten" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Web" -msgstr "Ticket > Aktualisiert von > Web" +#: ../system/objects/permissions.rst:56 +msgid "view" +msgstr "Ansicht" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.web}``" -msgstr "``#{ticket.updated_by.web}``" +#: ../system/objects/permissions.rst:62 +msgid "View-only dialog for already existing data" +msgstr "Lese-Ansicht für bereits vorhandene Daten" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > VIP" -msgstr "Ticket > Aktualisiert von > VIP" +#: ../system/objects/permissions.rst:64 +msgid "(e.g. user or organization from search)" +msgstr "(z.B. Benutzer oder Organisation über die Suche)" + +#: ../system/objects/permissions.rst:65 +msgid "signup" +msgstr "signup" + +#: ../system/objects/permissions.rst:67 +msgid "Sign-up screen for new customers" +msgstr "Anmelde-Ansicht für neue Kunden" + +#: ../system/objects/permissions.rst:68 +msgid "invite_customer" +msgstr "invite_customer" + +#: ../system/objects/permissions.rst:71 +msgid "" +"Customer invitation screen (from :doc:`First Steps ` area)" +msgstr "" +"Ansicht zur Einladung von Kunden (aus dem Bereich :doc:`Erste Schritte `)" + +#: ../system/objects/permissions.rst:72 +msgid "invite_agent" +msgstr "invite_agent" + +#: ../system/objects/permissions.rst:74 +msgid "" +"Agent invitation screen (from :doc:`First Steps ` area)" +msgstr "" +"Ansicht für die Einladung von Agenten (aus dem Bereich :doc:`Erste Schritte " +"`)" + +#: ../system/objects/permissions.rst:78 +msgid "Screen Options" +msgstr "Ansicht Optionen" + +#: ../system/objects/permissions.rst:80 +msgid "" +"For the different screens you can select \"show\" and \"required\" options." +msgstr "" +"Für die verschiedenen Ansichten können Sie die Optionen \"anzeigen\" und " +"\"erforderlich\" auswählen." + +#: ../system/objects/permissions.rst:82 +msgid "**shown:** Show (check) or hide (uncheck) a field." +msgstr "" +"**Anzeigen:** Ein Feld anzeigen (Haken gesetzt) oder ausblenden (Haken nicht " +"gesetzt)." + +#: ../system/objects/permissions.rst:83 +msgid "" +"**required:** Set a field to mandatory (check). Forces users (via UI and " +"API) to populate the field." +msgstr "" +"**Erforderlich:** Setzen Sie ein Feld auf erforderlich (Haken gesetzt), um " +"eine Eingabe (über UI und API) zu erzwingen." + +#: ../system/objects/types.rst:7 +msgid "Example external data source" +msgstr "Beispiel externe Datenquelle" + +#: ../system/objects/types.rst:2 +msgid "Attribute types" +msgstr "Attribut-Typen" + +#: ../system/objects/types.rst:4 +msgid "" +"When adding a new object attribute, you can choose between the following " +"attribute types." +msgstr "" +"Wenn Sie ein neues Objektattribut hinzufügen, können Sie zwischen den " +"folgenden Attributtypen wählen." + +#: ../system/objects/types.rst:14 +msgid "" +"You cannot change the attribute format / type as soon as it is applied. If " +"you no longer need an object attribute, consider disabling it instead of " +"removing." +msgstr "" +"Sie können das Format und den Typ des Attributs nicht mehr ändern, sobald es " +"gespeichert wurde. Wenn Sie ein Objektattribut nicht mehr benötigen, sollten " +"Sie es deaktivieren, anstatt es zu entfernen." + +#: ../system/objects/types.rst:18 +msgid "**What about the translation of my attributes?**" +msgstr "**Was ist mit der Übersetzung meiner Attribute?**" + +#: ../system/objects/types.rst:20 +msgid "" +"For some attribute types you can decide if they should be translatable or " +"not. To be precise, it works only for the selectable fields because the " +"possible choices are known and limited. For the following attribute types, " +"you can set the translatable flag:" +msgstr "" +"Für manche Attribut-Typen können Sie definieren, ob diese übersetzbar sein " +"sollen oder nicht. Genauer gesagt funktioniert das für auswählbare Typen " +"weil die möglichen Auswahlmöglichkeiten bekannt und begrenzt sind. Für die " +"folgenden Attribut-Typen können Sie die Übersetzbarkeit festlegen:" + +#: ../system/objects/types.rst:25 +msgid "*Boolean field*" +msgstr "*Boolean-Feld*" + +#: ../system/objects/types.rst:26 +msgid "*Single selection field*" +msgstr "*Einfachauswahl-Feld*" + +#: ../system/objects/types.rst:27 +msgid "*Multiple selection field*" +msgstr "*Mehrfachauswahl-Feld*" + +#: ../system/objects/types.rst:28 +msgid "*Single tree selection field*" +msgstr "*Einfach-Baumauswahl-Feld*" + +#: ../system/objects/types.rst:29 +msgid "*Multiple tree selection field*" +msgstr "*Mehrfach-Baumauswahl-Feld*" + +#: ../system/objects/types.rst:31 +msgid "" +"For these types, you can find an additional field *Translate field contents*:" +msgstr "" +"Für diese Typen gibt es ein zusätzliches Feld *Feldinhalte übersetzen*:" + +#: ../system/objects/types.rst:0 +msgid "Screenshot showing translatable attribute types" +msgstr "Screenshot mit übersetzbaren Attributtypen" + +#: ../system/objects/types.rst:38 +msgid "Screenshot with example of translatable attribute type" +msgstr "Screenshot mit Beispiel eines übersetzbaren Attributtyps" + +#: ../system/objects/types.rst:45 +msgid "Boolean field" +msgstr "Boolean-Feld" + +#: ../system/objects/types.rst:41 +msgid "" +"Provides a drop-down field with display values for ``true`` and ``false``. " +"Setting a default is mandatory." +msgstr "" +"Bietet ein Dropdown-Feld mit Anzeigewerten für ``true`` und ``false``. Das " +"Festlegen eines Standardwerts ist erforderlich." + +#: ../system/objects/types.rst:0 +msgid "Available settings for Boolean fields" +msgstr "Verfügbare Einstellungen für boolesche Felder" + +#: ../system/objects/types.rst:55 +msgid "Date field" +msgstr "Datumsfeld" + +#: ../system/objects/types.rst:48 +msgid "Provides a date picker field and does not allow default values." +msgstr "Bietet ein Datumsauswahlfeld und lässt keine Standardwerte zu." + +#: ../system/objects/types.rst:52 +msgid "Default time diff (hours)" +msgstr "Standard-Zeit-Differenz (Stunden)" + +#: ../system/objects/types.rst:51 +msgid "" +"This setting helps the user by highlighting the day from now plus the " +"provided value. It *does not* pre-fill the field." +msgstr "" +"Diese Einstellung hilft dem Benutzer, indem sie einen Tag hervorhebt, der " +"dem aktuellen Datum plus der Differenz entspricht. Das Feld wird *nicht* " +"vorausgefüllt." + +#: ../system/objects/types.rst:0 +msgid "Available settings for Date fields" +msgstr "Verfügbare Einstellungen für Datumsfelder" + +#: ../system/objects/types.rst:73 +msgid "Date & time field" +msgstr "Datum & Zeit-Feld" + +#: ../system/objects/types.rst:58 +msgid "Provides a date and time picker – does not allow default values" +msgstr "Bietet eine Datums- und Zeitauswahl an - erlaubt keine Standardwerte" + +#: ../system/objects/types.rst:62 +msgid "Allow future" +msgstr "Werte in der Zukunft erlauben" + +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the future." +msgstr "Verbietet Datum und Zeit in der Zukunft." + +#: ../system/objects/types.rst:66 +msgid "Allow past" +msgstr "Werte in der Vergangenheit erlauben" + +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the past." +msgstr "Verbietet Datum und Zeit in der Vergangenheit." + +#: ../system/objects/types.rst:70 +msgid "Default time diff (minutes)" +msgstr "Standard-Zeit-Differenz (Minuten)" + +#: ../system/objects/types.rst:69 +msgid "" +"This setting helps the user by highlighting the day from now plus the " +"provided value. It does not pre-fill the field." +msgstr "" +"Diese Einstellung hilft dem Benutzer, indem sie einen Tag hervorhebt, der " +"dem aktuellen Datum plus der Differenz entspricht. Das Feld wird *nicht* " +"vorausgefüllt." + +#: ../system/objects/types.rst:0 +msgid "Available settings for Date & time fields" +msgstr "Verfügbare Einstellungen für Datum- und Zeitfelder" + +#: ../system/objects/types.rst:86 +msgid "Integer field" +msgstr "Zahlen-Feld" + +#: ../system/objects/types.rst:76 +msgid "" +"Provides an input field that allows integer usage only. You may define a " +"default value. You cannot enforce comma separation." +msgstr "" +"Bietet ein Eingabefeld, das nur die Verwendung von Ganzzahlen erlaubt. Sie " +"können einen Standardwert definieren. Dezimalstellen sind nicht erlaubt bzw. " +"werden ignoriert." + +#: ../system/objects/types.rst:80 +msgid "Minimal" +msgstr "Minimum" + +#: ../system/objects/types.rst:80 +msgid "The minimal value the field accepts." +msgstr "Der Mindestwert, den das Feld akzeptiert." + +#: ../system/objects/types.rst:83 +msgid "Maximal" +msgstr "Maximum" + +#: ../system/objects/types.rst:83 +msgid "The maximum value the field accepts." +msgstr "Der Maximalwert, den das Feld akzeptiert." + +#: ../system/objects/types.rst:0 +msgid "Available settings for Integer fields" +msgstr "Verfügbare Einstellungen für Integer-Felder" + +#: ../system/objects/types.rst:99 +msgid "Multiple selection field" +msgstr "Mehrfachauswahl-Feld" + +#: ../system/objects/types.rst:89 +msgid "" +"Provides a selection field that allows the selection of one or more out of " +"several. This field does allow setting a default value." +msgstr "" +"Bietet ein Auswahlfeld, das die Auswahl von einem oder mehreren Werten " +"ermöglicht. In diesem Feld kann ein Standardwert festgelegt werden." + +#: ../system/objects/types.rst:0 +msgid "Available settings for Multiple selection fields" +msgstr "Verfügbare Einstellungen für Mehrfachauswahlfelder" + +#: ../system/objects/types.rst:112 +msgid "Single selection field" +msgstr "Einfachauswahl-Feld" + +#: ../system/objects/types.rst:102 +msgid "" +"Provides a drop-down field that allows selection of one value out of " +"several. This field does allow setting a default value." +msgstr "" +"Bietet ein Dropdown-Feld, in dem ein Wert aus mehreren ausgewählt werden " +"kann. In diesem Feld kann auch ein Standardwert festgelegt werden." + +#: ../system/objects/types.rst:0 +msgid "Available settings for Single selection fields" +msgstr "Verfügbare Einstellungen für Einfachauswahl-Felder" + +#: ../system/objects/types.rst:142 +msgid "Textarea field" +msgstr "Textbereich-Feld" + +#: ../system/objects/types.rst:115 +msgid "" +"Provides a text area input field (multiple lines) and thus allows e.g. new " +"lines. You can set a default field value." +msgstr "" +"Bietet ein Eingabefeld für einen Textbereich und ermöglicht u.a. mehrere " +"Zeilen. Sie können einen Standardfeldwert festlegen." + +#: ../system/objects/types.rst:120 +msgid "" +"Please note that this field *does not* support text formatting or HTML " +"content (rich text)." +msgstr "" +"Bitte beachten Sie, dass dieses Feld *keine* Textformatierung oder HTML-" +"Inhalte (Rich Text) unterstützt." + +#: ../system/objects/types.rst:123 +msgid "**🥵 This field can consume a lot of visual space**" +msgstr "**🥵 Dieses Feld kann viel Platz beanspruchen**" + +#: ../system/objects/types.rst:125 +msgid "" +"Depending on where you use this field type, it may use a lot of visual space " +"if you provide a lot of text. This may be an issue to work with." +msgstr "" +"Je nachdem, wo Sie diesen Feldtyp verwenden, kann er viel Platz " +"beanspruchen, wenn Sie viel Text eingeben. Das kann zu Problemen führen." + +#: ../system/objects/types.rst:130 +msgid "Default" +msgstr "Standard" + +#: ../system/objects/types.rst:129 +msgid "" +"The here provided text will be shown within the text area field or new data " +"sets." +msgstr "" +"Der hier eingegebene Text wird im Textfeld oder in neuen Datensätzen " +"angezeigt." + +#: ../system/objects/types.rst:134 ../system/objects/types.rst:160 +msgid "Maxlength" +msgstr "Maximale Länge" + +#: ../system/objects/types.rst:0 ../system/objects/types.rst:160 +msgid "You can pick the maximum length of the field." +msgstr "Sie können die maximale Länge des Feldes wählen." + +#: ../system/objects/types.rst:0 +msgid "The default length of this object is ``500``." +msgstr "Die Standardlänge dieses Objekts ist ``500``." + +#: ../system/objects/types.rst:139 +msgid "Rows" +msgstr "Zeilen" + +#: ../system/objects/types.rst:0 +msgid "" +"Change the number of rows to dislay so that you can use only the space you " +"really need." +msgstr "" +"Ändern Sie die Anzahl der anzuzeigenden Zeilen, damit nur der wirklich " +"benötigte Platz verwendet wird." + +#: ../system/objects/types.rst:0 +msgid "The default number of rows is ``4``." +msgstr "Die Standardanzahl der Zeilen ist ``4``." + +#: ../system/objects/types.rst:0 +msgid "Available settings for Textarea fields" +msgstr "Verfügbare Einstellungen für Textbereich-Felder" + +#: ../system/objects/types.rst:165 +msgid "Text field" +msgstr "Textfeld" + +#: ../system/objects/types.rst:145 +msgid "Provides a text field (one line) and allows choosing a default value." +msgstr "" +"Bietet ein Textfeld (eine Zeile) und ermöglicht die Auswahl eines " +"Standardwerts." + +#: ../system/objects/types.rst:148 +msgid "" +"Defines the type of the input field. This allows e.g. your browser to ensure " +"that you provide the specific type." +msgstr "" +"Legt den Typ des Eingabefeldes fest. So kann z.B. Ihr Browser sicherstellen, " +"dass der richtige Typ eingeben wird." + +#: ../system/objects/types.rst:152 +msgid "Currently available:" +msgstr "Derzeit verfügbar:" + +#: ../system/objects/types.rst:155 +msgid "Phone" +msgstr "Telefon" + +#: ../system/objects/types.rst:156 +msgid "Text" +msgstr "Text" + +#: ../system/objects/types.rst:157 +msgid "Url *(URL fields disable link-template availability)*" +msgstr "Url *(URL-Felder deaktivieren die Verfügbarkeit von Link-Templates)*" + +#: ../system/objects/types.rst:0 +msgid "Available settings for Text fields" +msgstr "Verfügbare Einstellungen für Textfelder" + +#: ../system/objects/types.rst:174 +msgid "Single tree selection field" +msgstr "Einfach-Baumauswahl-Feld" + +#: ../system/objects/types.rst:168 +msgid "" +"Provides a select-like field with up to 6 layers of options. Does not allow " +"setting a default value." +msgstr "" +"Bietet ein Auswahl-Feld mit bis zu 6 Ebenen. Erlaubt keine Festlegung eines " +"Standardwerts." + +#: ../system/objects/types.rst:0 +msgid "Available settings for Tree Select fields" +msgstr "Verfügbare Einstellungen für Baumauswahlfelder" + +#: ../system/objects/types.rst:183 +msgid "Multiple tree selection field" +msgstr "Mehrfach-Baumauswahl-Feld" + +#: ../system/objects/types.rst:177 +msgid "" +"Provides a select-like field with up to 6 layers of options allowing the " +"selection of multiple values. Does not allow setting a default value." +msgstr "" +"Bietet ein Auswahl-Feld mit bis zu 6 Ebenen, das die Auswahl mehrerer Werte " +"ermöglicht. Erlaubt keine Festlegung eines Standardwerts." + +#: ../system/objects/types.rst:302 +msgid "External Data Source field" +msgstr "Externe Datenquelle Feld" + +#: ../system/objects/types.rst:186 +msgid "" +"Provides a searchable field which fetches data from an external system. This " +"can be useful if you have data outside of Zammad and don't want to maintain " +"both data sources." +msgstr "" +"Bietet ein durchsuchbares Feld, das Daten aus einem externen System abruft. " +"Dies kann nützlich sein, wenn Sie Daten außerhalb von Zammad haben und nicht " +"beide Datenquellen pflegen wollen." + +#: ../system/objects/types.rst:190 +msgid "The feature works as follows:" +msgstr "Das funktioniert wie folgt:" + +#: ../system/objects/types.rst:192 +msgid "" +"Zammad sends a query with a search string (free text from agent or based on " +"a variable) in a pre-defined format (\"Search URL\") to an external system." +msgstr "" +"Zammad sendet eine Anfrage mit einem Suchstring (freier Text vom Agent oder " +"basierend auf einer Variable) in einem vordefinierten Format (\"Such URL\") " +"an ein externes System." + +#: ../system/objects/types.rst:195 +msgid "" +"This external system searches for matches and provides a response as a JSON " +"structure to Zammad." +msgstr "" +"Dieses externe System sucht nach Übereinstimmungen und gibt eine Antwort in " +"Form einer JSON-Struktur an Zammad." + +#: ../system/objects/types.rst:197 +msgid "" +"Zammad just looks for the defined list and value keys, reads the content and " +"displays the value to the user. There is no search on Zammad side." +msgstr "" +"Zammad sucht nur nach den definierten Suchergebnis-Schlüsseln und -Werten, " +"liest den Inhalt und zeigt dem Benutzer den Wert an. Es gibt keine Suche auf " +"der Seite von Zammad." + +#: ../system/objects/types.rst:201 +msgid "" +"The usage of a PostgreSQL database for Zammad is required. In any other " +"case, Zammad will hide the external data source type and you are not able to " +"use it. If you want to use this feature, consider to :docs:`migrate your " +"database `." +msgstr "" +"Die Verwendung einer PostgreSQL-Datenbank für Zammad ist erforderlich. In " +"jedem anderen Fall wird Zammad den externen Datenquellentyp ausblenden und " +"Sie können ihn nicht verwenden. Wenn Sie diese Funktion nutzen möchten, " +"ziehen Sie bitte eine :docs:`Migration Ihrer Datenbank ` in Erwägung." + +#: ../system/objects/types.rst:205 +msgid "Currently, only ``GET`` is supported as request method." +msgstr "Derzeit wird nur ``GET`` als Anfragemethode unterstützt." + +#: ../system/objects/types.rst:206 +msgid "" +"The data structure must be in JSON format and provide the objects in an " +"array." +msgstr "" +"Die Datenstruktur muss im JSON-Format sein und die Objekte in einem Array " +"bereitgestellt werden." + +#: ../system/objects/types.rst:208 +msgid "" +"The endpoint for the external data source has to support search. On Zammad " +"side, there is no search/logic implemented; however, you can define the " +"output key and value based on the result(s) from the response (which " +"provides already filtered content based on the search)." +msgstr "" +"Der Endpunkt für die externe Datenquelle muss die Suche unterstützen. Auf " +"Zammad-Seite ist keine Suche/Logik implementiert; Sie können jedoch den " +"Suchergebnis-Schlüssel und -Wert auf der Grundlage des Ergebnisses der " +"Antwort definieren (die bereits gefilterte Inhalte auf der Grundlage der " +"Suche bereitstellt)." + +#: ../system/objects/types.rst:212 +msgid "" +"If you receive more results as expected, your external data source search " +"may not work properly or the structure of the URL is not correct. You should " +"get in touch with a responsible person from the external system." +msgstr "" +"Wenn Sie mehr Ergebnisse als erwartet erhalten, funktioniert die Suche in " +"Ihrer externen Datenquelle möglicherweise nicht richtig oder die Struktur " +"der URL ist nicht korrekt. Sie sollten sich mit einer zuständigen Person des " +"externen Systems in Verbindung setzen." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.vip}``" -msgstr "``#{ticket.updated_by.vip}``" +#: ../system/objects/types.rst:217 +msgid "" +"Please have a look :doc:`at our example `, where you can find a possible configuration for a public " +"dummy endpoint." +msgstr "" +"Werfen Sie einen Blick :doc:`auf unsere Beispielkonfiguration `, wo Sie eine mögliche Konfiguration " +"mit einen öffentlichen Dummy-Endpunkt finden." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Phone" -msgstr "Ticket > Aktualisiert von > Telefon" +#: ../system/objects/types.rst:0 +msgid "Available settings for external data source fields" +msgstr "Verfügbare Einstellungen für externe Datenquelle Felder" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.phone}``" -msgstr "``#{ticket.updated_by.phone}``" +#: ../system/objects/types.rst:242 +msgid "Search URL" +msgstr "Such-URL" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Note" -msgstr "Ticket > Aktualisiert von > Notiz" +#: ../system/objects/types.rst:227 +#, fuzzy +#| msgid "" +#| "Set your endpoint where Zammad fetches the data. Please make sure to " +#| "include a valid search :doc:`variable <../variables>` as an URL " +#| "parameter. Example for a free text search at user input: ``#{search.term}" +#| "``" +msgid "" +"Set your endpoint where Zammad fetches the data. Please make sure to include " +"a valid search :doc:`variable ` as an URL parameter. " +"Example for a free text search at user input: ``#{search.term}``" +msgstr "" +"Legen Sie den Endpunkt fest, von dem Zammad die Daten abruft. Bitte stellen " +"Sie sicher, dass Sie eine gültige :doc:`Suchvariable <../variables>` als URL-" +"Parameter angeben. Beispiel für eine Freitextsuche bei Benutzereingabe: " +"``#{search.term}``" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.note}``" -msgstr "``#{ticket.updated_by.note}``" +#: ../system/objects/types.rst:232 +#, fuzzy +#| msgid "" +#| "If in doubt, ask the responsible person for the external data source how " +#| "they expect the strucuture of the URL." +msgid "" +"If in doubt, ask the responsible person for the external data source how " +"they expect the structure of the URL." +msgstr "" +"Fragen Sie im Zweifelsfall die für die externe Datenquelle verantwortliche " +"Person, wie die Struktur der URL aufgebaut sein muss." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Mobile" -msgstr "Ticket > Aktualisiert von > Mobil" +#: ../system/objects/types.rst:236 +msgid "" +"Depending on your search variable, the preview might work or not. The reason " +"is that the context might not be available and it is no bug." +msgstr "" +"Je nach Suchvariable kann die Vorschau ggf. nicht funktionieren. Der Grund " +"dafür ist, dass der Objektkontext in der Konfiguration möglicherweise nicht " +"verfügbar ist. Dies ist kein Fehler." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.mobile}``" -msgstr "``#{ticket.updated_by.mobile}``" +#: ../system/objects/types.rst:239 +msgid "" +"Please also make sure to use a variable which is available in your object " +"context. For example you won't be able to search for a ticket in a user " +"object context." +msgstr "" +"Achten Sie bitte auch darauf, dass Sie eine Variable verwenden, die in Ihrem " +"Objektkontext verfügbar ist. Zum Beispiel können Sie in einem " +"Benutzerobjektkontext nicht nach einem Ticket suchen." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Login" -msgstr "Ticket > Aktualisiert von > Login" +#: ../system/objects/types.rst:252 +msgid "SSL Verification" +msgstr "SSL-Verizifierung" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.login}``" -msgstr "``#{ticket.updated_by.login}``" +#: ../system/objects/types.rst:245 +msgid "Here you can switch the SSL verification to no." +msgstr "Hier können Sie die SSL-Verifizierung auf nein stellen." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Lastname" -msgstr "Ticket > Aktualisiert von > Nachname" +#: ../system/objects/types.rst:249 +msgid "" +"If your external data source system is using self signed certificates, " +"please have a look :doc:`here ` for " +"further information about how to handle them in Zammad, so you can keep the " +"SSL verification activated." +msgstr "" +"Wenn Ihr externes Datenquellensystem selbstsignierte Zertifikate verwendet, " +"sehen Sie sich bitte :doc:`SSL Zertifikate ` an. Dort finden Sie weitere Informationen darüber, wie diese " +"in Zammad hinterlegt werden können, damit Sie die SSL-Verifizierung " +"aktiviert lassen können." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.lastname}``" -msgstr "``#{ticket.updated_by.lastname}``" +#: ../system/objects/types.rst:258 +msgid "HTTP Authentication" +msgstr "HTTP-Authentifizierung" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Firstname" -msgstr "Ticket > Aktualisiert von > Vorname" +#: ../system/objects/types.rst:255 +msgid "" +"If your external data source requires an authentication, you can set it " +"here. You can leave it empty or choose between *Basic Authentication* or " +"*Authentication Token* (selecting one of the two methods leads to additional " +"fields where you can enter your credentials/token)." +msgstr "" +"Wenn Ihre externe Datenquelle eine Authentifizierung erfordert, können Sie " +"diese hier hinterlegen. Sie können es leer lassen oder zwischen *Basis " +"Authentifizierung* oder *Token Authentifizierung* wählen (die Auswahl einer " +"der beiden Methoden führt zu zusätzlichen Feldern, in die Sie Ihre " +"Anmeldedaten/Token eingeben können)." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.firstname}``" -msgstr "``#{ticket.updated_by.firstname}``" +#: ../system/objects/types.rst:265 +msgid "Search result list key" +msgstr "Schlüssel der Suchergebnisliste" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Fax" -msgstr "Ticket > Aktualisiert von > Fax" +#: ../system/objects/types.rst:261 +msgid "" +"Defines the level in the JSON structure which provides the list with search " +"results. You can leave it empty, if the data is already provided as an " +"array. If you have to go deeper in the structure, you can provide a path " +"with ``.`` as separators, e.g. ``key.subkey.sub-sub-key``." +msgstr "" +"Definiert die Ebene in der JSON-Struktur, die die Liste mit den " +"Suchergebnissen liefert. Sie können es leer lassen, wenn die Daten bereits " +"als Array bereitgestellt werden. Wenn Sie tiefer in die Struktur gehen " +"müssen, können Sie einen Pfad mit ``.`` als Trennzeichen angeben, z.B. ``key." +"subkey.sub-sub-key``." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.fax}``" -msgstr "``#{ticket.updated_by.fax}``" +#: ../system/objects/types.rst:271 +msgid "Search result value key" +msgstr "Schlüssel Suchergebnis-Wert" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Email" -msgstr "Ticket > Aktualisiert von > Email" +#: ../system/objects/types.rst:268 +msgid "" +"Defines the attribute in the structure in which your external data source " +"provides the *value* for your data. An example would be a product *number*. " +"If you have to go deeper in the structure, you can provide a path with ``.`` " +"as separators, e.g. ``key.subkey.sub-sub-key``." +msgstr "" +"Definiert das Attribut in der Struktur, in der Ihre externe Datenquelle den " +"*Wert* für Ihre Daten liefert. Ein Beispiel wäre eine Produkt *Nummer*. Wenn " +"Sie tiefer in die Struktur eindringen müssen, können Sie einen Pfad mit ``." +"`` als Trennzeichen angeben, z.B. ``key.subkey.sub-sub-key``." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.email}``" -msgstr "``#{ticket.updated_by.email}``" +#: ../system/objects/types.rst:277 +msgid "Search result label key" +msgstr "Schlüssel der Suchergebnisbezeichnung" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Department" -msgstr "Ticket > Aktualisiert von > Abteilung" +#: ../system/objects/types.rst:274 +msgid "" +"Defines the attribute in the structure in which your external data source " +"provides the *label* for your data. An example would be a product *name*. If " +"you have to go deeper in the structure, you can provide a path with ``.`` as " +"separators, e.g. ``key.subkey.sub-sub-key``." +msgstr "" +"Definiert das Attribut in der Struktur, in der Ihre externe Datenquelle die " +"*Bezeichnung* für Ihre Daten bereitstellt. Ein Beispiel wäre ein Produkt " +"*Name*. Wenn Sie tiefer in die Struktur eindringen müssen, können Sie einen " +"Pfad mit ``.`` als Trennzeichen angeben, z.B. ``key.subkey.sub-sub-key``." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.department}``" -msgstr "``#{ticket.updated_by.department}``" +#: ../system/objects/types.rst:280 +msgid "" +"In the preview area, you can find the following items (depending on your " +"configuration above):" +msgstr "" +"Im Vorschaubereich finden Sie die folgenden Elemente (abhängig von " +"bisheriger Konfiguration):" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Avatar" -msgstr "Ticket > Aktualisiert von > Avatar" +#: ../system/objects/types.rst:283 +msgid "" +"**Error/hint message** (only if configuration is not complete): Zammad tells " +"you, if there is a problem and what you should change in your configuration." +msgstr "" +"**Fehler-/Hinweismeldung** (nur wenn die Konfiguration nicht vollständig " +"ist): Zammad sagt Ihnen, ob es ein Problem gibt und was Sie an Ihrer " +"Konfiguration ändern sollten." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.avatar(60,60)}``" -msgstr "``#{ticket.updated_by.avatar(60,60)}``" +#: ../system/objects/types.rst:286 +msgid "" +"**Search field**: search for an existing attribute in the data source to get " +"a preview. This is required for the fields below to show up." +msgstr "" +"**Suchfeld**: Suchen Sie nach einem vorhandenen Attribut in der Datenquelle, " +"um eine Vorschau zu erhalten. Dies ist erforderlich, damit die nachstehenden " +"Felder angezeigt werden können." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Address" -msgstr "Ticket > Aktualisiert von > Adresse" +#: ../system/objects/types.rst:288 +msgid "" +"**Search result response** (only if configuration is not complete): here you " +"can find a syntax highlighted JSON preview of the response, based on the " +"search term you entered." +msgstr "" +"**Antwort Suchergebnis** (nur wenn die Konfiguration nicht vollständig ist): " +"Hier finden Sie eine syntaktisch hervorgehobene JSON-Vorschau der Antwort, " +"die auf dem eingegebenen Suchbegriff basiert." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.address}``" -msgstr "``#{ticket.updated_by.address}``" +#: ../system/objects/types.rst:291 +msgid "" +"**Search result list** (only if *search result list key* is properly set): " +"output of the structure under the configured *search result list key*." +msgstr "" +"**Suchergebnisliste** (nur wenn *Suchergebnislisten-Schlüssel* richtig " +"gesetzt ist): Ausgabe der Struktur unter dem konfigurierten " +"*Suchergebnislisten-Schlüssel*." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated at" -msgstr "Ticket > Aktualisiert am" +#: ../system/objects/types.rst:294 +msgid "" +"**Preview table** (when fully configured): Zammad shows you a table which " +"includes the found items based on the search string (value, label and " +"optional link). You can use this preview if you don't have the complete data " +"structure of the external system in mind." +msgstr "" +"**Vorschau-Tabelle** (wenn vollständig konfiguriert): Zammad zeigt Ihnen " +"eine Tabelle an, die die gefundenen Elemente auf der Grundlage des " +"Suchstrings (Wert, Bezeichnung und optionaler Link) enthält. Sie können " +"diese Vorschau verwenden, wenn Sie nicht die komplette Datenstruktur des " +"externen Systems im Kopf haben." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_at}``" -msgstr "``#{ticket.updated_at}``" +#: ../system/objects/types.rst:299 +msgid "" +"An example of a configured external data source field from agent perspective:" +msgstr "" +"Ein Beispiel für ein eigenes Feld auf Ticketebene vom Typ externe " +"Datenquelle aus der Sicht eines Agenten:" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Title" -msgstr "Ticket > Titel" +#: ../system/objects/types.rst:0 +msgid "Screencast showing the search for a product in a ticket" +msgstr "Screencast zeigt die Suche nach einem Produkt in einem Ticket" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.title}``" -msgstr "``#{ticket.title}``" +#: ../system/objects/types.rst:307 +msgid "URL fields (Link-Template)" +msgstr "URL-Felder (Link-Template)" + +#: ../system/objects/types.rst:311 +msgid "" +"This function is restricted to Text, Select and External data source types " +"only." +msgstr "" +"Diese Funktion ist nur auf die Feldtypen Text-, Auswahl- und Externe " +"Datenquelle beschränkt." + +#: ../system/objects/types.rst:314 +msgid "" +"Link-Templates are an amazing way to dynamically generate URLs. They allow " +"you to integrate other systems better without having to manually copy data " +"from Zammad if possible." +msgstr "" +"Link-Templates sind eine hervorragende Möglichkeit, URLs dynamisch zu " +"erzeugen. Sie ermöglichen es Ihnen, andere Systeme zu integrieren, ohne " +"Daten manuell aus Zammad kopieren zu müssen." -#: ../system/variables/ticket.rst:1 +#: ../system/objects/types.rst:320 msgid "" -"``My amazing Subject`` (normally subject, can be edited within Interface and " -"thus differ)" +"Another great way of communicating with another system may be Zammad's :doc:" +"`Webhooks `." msgstr "" -"``Mein super Betreff`` (normalerweise Betreff, kann im Interface bearbeitet " -"werden und somit abweichen)" - -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Accounted Time" -msgstr "Ticket > erfasste Zeit" - -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.time_unit}``" -msgstr "``#{ticket.time_unit}``" - -#: ../system/variables/ticket.rst:1 -msgid "``1``, ``2.75`` or empty response" -msgstr "``1``, ``2.75`` oder leere Ausgabe" - -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Tags" -msgstr "Ticket > Schlagworte" +"Eine weitere gute Möglichkeit, mit anderen Systemen zu kommunizieren, sind " +"die :doc:`Webhooks ` von Zammad." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.tags}``" -msgstr "``#{ticket.tags}``" +#: ../system/objects/types.rst:323 +msgid "" +"After filling a link-template enabled field, an URL icon will appear on its " +"right. Clicking on the icon opens a new tab." +msgstr "" +"Nach dem Ausfüllen eines Feldes, das mit einem Link-Template versehen ist, " +"erscheint rechts davon ein Symbol. Wenn Sie auf das Symbol klicken, wird ein " +"neuer Tab im Browser geöffnet." -#: ../system/variables/ticket.rst:1 +#: ../system/objects/types.rst:328 msgid "" -"Currently not available, see `Issue 2769 `_" +"Even though Zammad displays the link template within object edit and create " +"screens, the function is optional. It's only active if you populate the " +"field." msgstr "" -"Derzeit nicht verfügbar, siehe `Issue 2769 `_" +"Obwohl Zammad das Link-Template in den Ansichten zum Bearbeiten und " +"Erstellen von Objekten anzeigt, ist die Funktion optional. Sie ist nur " +"aktiv, wenn Sie das Feld ausfüllen." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > State > Name" -msgstr "Ticket > Status > Name" +#: ../system/objects/types.rst:333 +msgid "" +"What's the difference between URL and text fields with link template...?!" +msgstr "Was ist der Unterschied zwischen URL und Textfeldern mit Linkvorlage?" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.state.name}``" -msgstr "``#{ticket.state.name}``" +#: ../system/objects/types.rst:335 +msgid "" +"Both fields have different use cases. Use ``text`` type text fields when " +"ever you have a *static* url that requires dynamic parameters. If you " +"require a drag & drop like field that you can put in any URL, use ``URL`` " +"type text fields." +msgstr "" +"Beide Felder haben unterschiedliche Verwendungszwecke. Verwenden Sie Felder " +"vom Typ ``Text``, wenn Sie eine *statische* URL haben, die dynamische " +"Parameter erfordert. Wenn Sie ein Feld benötigen, in das Sie eine beliebige " +"statische URL einfügen können, verwenden Sie Textfelder vom Typ ``URL``." -#: ../system/variables/ticket.rst:1 -msgid "``new``, ``open``, ..." -msgstr "``new``, ``open``, ..." +#: ../system/objects/types.rst:340 +msgid "" +"The difference is easier to spot when comparing the fields directly, below " +"screencast shows the result - the dynamic approach uses existing values in " +"the moment of updating to built the URL - e.g. ``https://google.com/search?" +"q=cookies`` - while the URL approach uses the actual URL of the field - e.g. " +"``https://zammad.com``." +msgstr "" +"Der Unterschied ist leichter zu erkennen, wenn man die Felder direkt " +"vergleicht. Der folgende Screencast zeigt das Ergebnis - der dynamische " +"Ansatz verwendet die vorhandenen Werte im Moment der Aktualisierung, um die " +"URL zu bilden - z.B. ``https://google.com/search?q=cookies`` - während der " +"URL-Ansatz die aktuelle statische URL des Feldes verwendet - z.B. ``https://" +"zammad.com``." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Priority > Name" -msgstr "Ticket > Priorität > Name" +#: ../system/objects/types.rst:None +msgid "" +"Screencast showing the differents in between URL and text type fields with " +"actual values" +msgstr "" +"Screencast mit den Unterschieden zwischen URL- und Textfeldern mit aktuellen " +"Werten" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.priority.name}``" -msgstr "``#{ticket.priority.name}``" +#: ../system/objects/types.rst:352 +msgid "How does this work...?!" +msgstr "Wie funktioniert das?" -#: ../system/variables/ticket.rst:1 -msgid "``2 normal``" -msgstr "``2 normal``" +#: ../system/objects/types.rst:354 +msgid "" +"As an example, let's say you have an attribute called ``amazing_attribute`` " +"and you want to open a google search directly with the input from that field." +msgstr "" +"Nehmen wir an, Sie haben ein Attribut namens ``amazing_attribute`` und " +"möchten eine Google-Suche direkt mit Inhalt aus diesem Feld öffnen." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Pending till" -msgstr "Ticket > warten bis" +#: ../system/objects/types.rst:357 +msgid "" +"Providing the link-template field below allows you to do so: ``https://www." +"google.com/search?q=#{ticket.amazing_attribute}``" +msgstr "" +"Mit dem unten stehenden Link-Template-Feld können Sie dies tun: ``https://" +"www.google.com/search?q=#{ticket.amazing_attribute}``" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.pending_time}``" -msgstr "``#{ticket.pending_time}``" +#: ../system/objects/types.rst:362 +#, fuzzy +#| msgid "" +#| "You can use any :doc:`Zammad variable ` as long as " +#| "it's available in the moment you need it." +msgid "" +"You can use any :doc:`Zammad variable ` as long as it's " +"available in the moment you need it." +msgstr "" +"Sie können jede :doc:`Zammad-Variable ` verwenden, " +"solange sie in dem Moment, in dem Sie sie brauchen, verfügbar ist." -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not set" -msgstr "``2019-10-07 16:25:00 UTC`` oder leer wenn nicht gesetzt" +#: ../system/objects/types.rst:365 +msgid "" +"As a result, you are redirected to Google with a search for the value of the " +"attribute, if you click on the button in the ticket (as you can see in the " +"screencast above)." +msgstr "" +"Als Ergebnis werden Sie zu Google mit einer Suche nach dem Inhalt des " +"Attributs weitergeleitet, wenn Sie auf die Schaltfläche im Ticket klicken " +"(wie Sie im Screencast oben sehen können)." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Web" -msgstr "Ticket > Besitzer > Web" +#: ../system/packages.rst:2 +msgid "Packages" +msgstr "Pakete" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.web}``" -msgstr "``#{ticket.owner.web}``" +#: ../system/packages.rst:4 +msgid "That's the package management-area." +msgstr "Das ist der Bereich der Paketverwaltung." -#: ../system/variables/ticket.rst:1 -msgid "``https://zammad.com`` or empty if not set" -msgstr "``https://zammad.com`` oder leer wenn nicht gesetzt" +#: ../system/packages.rst:6 +msgid "Individual add-ons for Zammad can be installed and managed here." +msgstr "" +"Individuelle Add-ons für Zammad können hier installiert und verwaltet werden." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > VIP" -msgstr "Ticket > Besitzer > VIP" +#: ../system/sessions.rst:2 +msgid "Sessions" +msgstr "Sitzungen" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.vip}``" -msgstr "``#{ticket.owner.vip}``" +#: ../system/sessions.rst:4 +msgid "" +"Sessions management allows reviewing currently known user sessions and " +"allows to end these. The session timeout is affected by :ref:" +"`security_session_timeout` configurations from security settings." +msgstr "" +"Die Sitzungsverwaltung ermöglicht die Überprüfung der aktuell bekannten " +"Benutzer-Sitzungen und deren Beendigung. Der Sitzungs-Timeout wird von der :" +"ref:`security_session_timeout` Konfiguration beeinflusst." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Phone" -msgstr "Ticket > Besitzer > Telefon" +#: ../system/sessions.rst:None +msgid "Screenshot showing Zammad's session management" +msgstr "Screenshot der Sitzungsverwaltung von Zammad" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.phone}``" -msgstr "``#{ticket.owner.phone}``" +#: ../system/sessions.rst:13 +msgid "Zammad will provide the following information:" +msgstr "Zammad stellt die folgenden Informationen zur Verfügung:" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Note" -msgstr "Ticket > Besitzer > Notiz" +#: ../system/sessions.rst:16 +msgid "" +"The user account this session entry belongs to. It can be normal if a user " +"has several sessions in the list. This can be due to changed browser " +"information or if you use e.g. single sign on methods where the user does " +"not use the log off button." +msgstr "" +"Das Benutzerkonto, zu dem dieser Sitzungseintrag gehört. Es kann vorkommen, " +"dass ein Benutzer mehrere Sitzungen in der Liste hat. Dies kann auf " +"geänderte Browser-Informationen zurückzuführen sein oder wenn Sie z.B. " +"Single-Sign-On-Methoden verwenden, bei denen der Benutzer die " +"Abmeldefunktion nicht benutzt." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.note}``" -msgstr "``#{ticket.owner.note}``" +#: ../system/sessions.rst:22 +msgid "Browser" +msgstr "Browser" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Mobile" -msgstr "Ticket > Besitzer > Mobil" +#: ../system/sessions.rst:22 +msgid "The browser agent communicated to Zammad." +msgstr "Der Browser-Agent, der an Zammad kommuniziert wurde." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.mobile}``" -msgstr "``#{ticket.owner.mobile}``" +#: ../system/sessions.rst:40 +msgid "Location" +msgstr "Ort" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Login" -msgstr "Ticket > Besitzer > Login" +#: ../system/sessions.rst:25 +msgid "" +"The anticipated location based on the users IP address. Depending on the IP " +"address the result shown may differ. This option depends on :doc:`/settings/" +"system/services`." +msgstr "" +"Der ungefähre Standort basiert auf der IP-Adresse des Nutzers. Je nach IP-" +"Adresse kann das angezeigte Ergebnis stark abweichen. Diese Option ist " +"abhängig von :doc:`/settings/system/services`." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.login}``" -msgstr "``#{ticket.owner.login}``" +#: ../system/sessions.rst:29 +msgid "The following information can be shown:" +msgstr "Die folgenden Informationen können angezeigt werden:" -#: ../system/variables/ticket.rst:1 -msgid "``agent``" -msgstr "``agent``" +#: ../system/sessions.rst:33 +msgid "IP address" +msgstr "IP-Adresse" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Lastname" -msgstr "Ticket > Besitzer > Nachname" +#: ../system/sessions.rst:32 +msgid "" +"Either if you set *Geo IP services* to inactive or you're using internal IP " +"address which do not provide location information." +msgstr "" +"Entweder haben Sie den *Geo-IP-Service* auf inaktiv gesetzt oder Sie " +"verwenden eine interne IP-Adresse, die keine Standortinformationen liefert." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.lastname}``" -msgstr "``#{ticket.owner.lastname}``" +#: ../system/sessions.rst:40 +msgid "Country (or Country + City)" +msgstr "Land (oder Land + Stadt)" -#: ../system/variables/ticket.rst:1 -msgid "``Mustermann`` or empty if not set" -msgstr "``Mustermann`` oder leer wenn nicht gesetzt" +#: ../system/sessions.rst:36 +msgid "" +"If *Geo IP services* is enabled only. Depends on how detailed the available " +"IP address information are." +msgstr "" +"Nur wenn *Geo-IP-Service* aktiviert ist. Hängt davon ab, wie detailliert die " +"verfügbaren IP-Adressinformationen sind." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Firstname" -msgstr "Ticket > Besitzer > Vorname" +#: ../system/sessions.rst:39 +msgid "" +"Be aware that results can be inaccurate - this technically is not an error." +msgstr "" +"Beachten Sie, dass die Ergebnisse ungenau sein können - dies ist technisch " +"gesehen kein Fehler." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.firstname}``" -msgstr "``#{ticket.owner.firstname}``" +#: ../system/sessions.rst:43 +msgid "Age" +msgstr "Alter" -#: ../system/variables/ticket.rst:1 -msgid "``Max`` or empty if not set" -msgstr "``Max`` oder leer wenn nicht gesetzt" +#: ../system/sessions.rst:43 +msgid "Provides the time when the session initially has been created." +msgstr "Gibt die Zeit an, zu der die Sitzung ursprünglich erstellt wurde." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Fax" -msgstr "Ticket > Besitzer > Fax" +#: ../system/sessions.rst:50 +msgid "Update" +msgstr "Aktualisierung" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.fax}``" -msgstr "``#{ticket.owner.fax}``" +#: ../system/sessions.rst:46 +msgid "" +"Provides the time the user used this session to open Zammad. This timestamp " +"is only updated if the user e.g. reloads, not during normal work on tickets." +msgstr "" +"Gibt den Zeitpunkt an, zu dem der Benutzer diese Sitzung verwendet hat, um " +"Zammad zu öffnen. Dieser Zeitstempel wird nur aktualisiert, wenn der " +"Benutzer z.B. die Seite neu lädt, nicht während der normalen Arbeit an " +"Tickets." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Email" -msgstr "Ticket > Besitzer > Email" +#: ../system/sessions.rst:50 +msgid "This timestamp is being used for the session timeout." +msgstr "Dieser Zeitstempel wird für den Timeout der Sitzung verwendet." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.email}``" -msgstr "``#{ticket.owner.email}``" +#: ../system/sessions.rst:53 +msgid "" +"Use the delete button to remove a single session on behalf of your user." +msgstr "" +"Verwenden Sie die Schaltfläche \"Löschen\", um eine einzelne Sitzung Ihres " +"Benutzers zu entfernen." -#: ../system/variables/ticket.rst:1 -msgid "``agent@company.tld`` or empty if not set" -msgstr "``agent@firma.tld`` oder leer wenn nicht gesetzt" +#: ../system/subscription.rst:2 +msgid "Subscription (SaaS)" +msgstr "Abonnement (SaaS)" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Department" -msgstr "Ticket > Besitzer > Abteilung" +#: ../system/subscription.rst:4 +msgid "" +"The subscription settings page allows you to configure your instances " +"package and number of agents required." +msgstr "" +"Auf der Seite mit den Abonnementeinstellungen können Sie Ihr Paket und die " +"Anzahl der benötigten Agenten konfigurieren." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.department}``" -msgstr "``#{ticket.owner.department}``" +#: ../system/subscription.rst:9 +msgid "" +"This setting section is only available for Hosted setups. If you're looking " +"for on premise support contracts, please see the `Zammad pricing page " +"`_." +msgstr "" +"Dieser Bereich ist nur für Hosted Instanzen verfügbar. Wenn Sie nach " +"Supportverträgen für selbst gehosteten Installationen suchen, sehen Sie sich " +"bitte die `Zammad Preisübersicht `_ an." -#: ../system/variables/ticket.rst:1 -msgid "``Support`` or empty if not set" -msgstr "``Support`` oder leer wenn nicht gesetzt" +#: ../system/subscription.rst:14 ../system/subscription.rst:34 +msgid "Plan" +msgstr "Produkt" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Avatar" -msgstr "Ticket > Besitzer > Avatar" +#: ../system/subscription.rst:16 +#, fuzzy +#| msgid "" +#| "Everything affecting your instance subscription functions like number of " +#| "agents, package and payment method." +msgid "" +"Here you can set up everything affecting your instance subscription " +"functions like number of agents and package." +msgstr "" +"Alles, was Ihr Abonnement betrifft, wie Anzahl der Agenten, Paket und " +"Zahlungsmethode." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.avatar(60,60)}``" -msgstr "``#{ticket.owner.avatar(60,60)}``" +#: ../system/subscription.rst:19 +#, fuzzy +#| msgid "" +#| "On the top of the subscription summary you'll find the number of used and " +#| "available (booked) agent seats. By using the *see more* link you can also " +#| "expand an agent list to see the currently configured active agents. This " +#| "list *does not* count accounts with admin permissions only." +msgid "" +"On top of the page you can find a subscription summary. You'll find the " +"number of used and available (booked) agent seats there. By using the *see " +"more* link you can also expand an agent list to see the currently configured " +"active agents. This list *does not* count accounts with admin permissions " +"only." +msgstr "" +"Oben in der Abonnementübersicht finden Sie die Anzahl der verwendeten und " +"verfügbaren (gebuchten) Agentenplätze. Über den Link *Mehr anzeigen* können " +"Sie auch die Liste der Agenten erweitern, um die derzeit konfigurierten " +"aktiven Agenten zu sehen. Diese Liste *zählt nicht* die Konten mit reinen " +"Admin-Rechten." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Address" -msgstr "Ticket > Besitzer > Adresse" +#: ../system/subscription.rst:None +msgid "" +"Within subscription you can always see how many agents are still\n" +"available to add and who uses the seats." +msgstr "" +"Innerhalb des Abonnements können Sie immer sehen, wie viele Agenten noch zur " +"Verfügung stehen und wer die Agenten-Plätze nutzt." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.address}``" -msgstr "``#{ticket.owner.address}``" +#: ../system/subscription.rst:29 +msgid "" +"Learn more on how to manage your agents in general :doc:`here `." +msgstr "" +"Erfahren Sie, wie Sie Ihre Agenten im Allgemeinen verwalten :doc:`hier `." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Shared organization" -msgstr "Ticket > Organisation > geteilte Organisation" +#: ../system/subscription.rst:36 +msgid "" +"This section gives you an overview of the available plans and their " +"functions / limits. If you require a more detailed table, check our " +"`detailed pricing table `_ for more." +msgstr "" +"Dieser Abschnitt gibt Ihnen einen Überblick über die verfügbaren Tarife und " +"ihre Funktionen / Grenzen. Wenn Sie eine detailliertere Tabelle benötigen, " +"finden Sie weitere Informationen in unserer `detaillierten Preisliste " +"`_." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.shared}``" -msgstr "``#{ticket.organization.shared}``" +#: ../system/subscription.rst:40 +msgid "" +"Your selection in this step will decide on the base agent price and e.g. " +"agent limits that might apply in the summary step." +msgstr "" +"Ihre Auswahl in diesem Schritt entscheidet über den Basis-Agentenpreis und z." +"B. die Agentenlimits, die Sie in der Zusammenfassung sehen." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Note" -msgstr "Ticket > Organisation > Notiz" +#: ../system/subscription.rst:43 +msgid "" +"The green *Selected* button will also tell you what plan you're currently in." +msgstr "" +"Die grüne Schaltfläche *Ausgewählt* zeigt Ihnen an, in welchem Tarif Sie " +"sich gerade befinden." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.note}``" -msgstr "``#{ticket.organization.note}``" +#: ../system/subscription.rst:47 +msgid "" +"Trial instances are running at Professional with 3 agents. The plan cannot " +"be changed during the trial for technical reasons, if you require more " +"agents for testing, please contact `our sales team `_ with a reason for the raise request." +msgstr "" +"Die Testinstanzen laufen auf Professional mit 3 Agenten. Der Plan kann aus " +"technischen Gründen während der Testphase nicht geändert werden. Wenn Sie " +"mehr Agenten zum Testen benötigen, wenden Sie sich bitte an `unser Sales " +"Team `_ mit einem Begründung, warum " +"Sie eine Erhöhung benötigen." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Name" -msgstr "Ticket > Organisation > Name" +#: ../system/subscription.rst:None +msgid "" +"Screenshot showing three available packages for a hosted Zammad\n" +"instance" +msgstr "" +"Screenshot mit drei verfügbaren Paketen für eine gehostete Zammad-Instanz" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.name}``" -msgstr "``#{ticket.organization.name}``" +#: ../system/subscription.rst:57 +#, fuzzy +#| msgid "" +#| "In this section you can adjust the settings of the previous selected plan." +msgid "" +"At the bottom of this block you can find a summary where you can adjust the " +"settings of the previous selected plan." +msgstr "" +"In diesem Abschnitt können Sie die Einstellungen des zuvor ausgewählten " +"Plans anpassen." -#: ../system/variables/ticket.rst:1 -msgid "``Zammad GmbH`` or empty if not set" -msgstr "``Zammad GmbH`` oder leer wenn nicht gesetzt" +#: ../system/subscription.rst:62 +msgid "" +"Note that upgrading (more agents, higher package) is always possible, " +"however, downgrading will only happen when your billing period renews." +msgstr "" +"Beachten Sie, dass ein Upgrade (mehr Agenten, höheres Paket) immer möglich " +"ist, ein Downgrade jedoch erst zum Ablauf Ihres Abrechnungszeitraums " +"erfolgen kann." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Domain based assignment" -msgstr "Ticket > Organisation > Domain basierte Zuordnung" +#: ../system/subscription.rst:66 +msgid "" +"Upgrading resets your billing period and existing credit will be deducted " +"from the new total." +msgstr "" +"Durch das Upgrade wird Ihr Abrechnungszeitraum zurückgesetzt und Ihr " +"bisheriges Guthaben wird vom neuen Gesamtbetrag abgezogen." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.domain_assignment}``" -msgstr "``#{ticket.organization.domain_assignment}``" +#: ../system/subscription.rst:75 +msgid "Billing cycle" +msgstr "Abrechnungszyklus" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Domain" -msgstr "Ticket > Organisation > Domain" +#: ../system/subscription.rst:70 +msgid "" +"You can choose between either monthly or yearly billing. The price per agent " +"will be cheaper if you decide for yearly billing." +msgstr "" +"Sie können zwischen monatlicher und jährlicher Abrechnung wählen. Der Preis " +"pro Agent ist günstiger, wenn Sie sich für eine jährliche Abrechnung " +"entscheiden." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.domain}``" -msgstr "``#{ticket.organization.domain}``" +#: ../system/subscription.rst:73 +msgid "" +"If you're still trying out things and are unsure of the right package for " +"your instance, you may want to choose monthly first and then upgrade to " +"yearly when you're sure." +msgstr "" +"Wenn Sie noch am Ausprobieren sind und z.B. nicht wissen, welches Paket für " +"Ihre Instanz das richtige ist, sollten Sie sich zunächst für ein monatliches " +"Paket entscheiden und dann auf ein jährliches Paket umsteigen, wenn Sie sich " +"sicher sind." -#: ../system/variables/ticket.rst:1 -msgid "``domain.tld`` or empty if not set" -msgstr "``domain.tld`` oder leer wenn nicht gesetzt" +#: ../system/subscription.rst:83 +msgid "Plan: (Starter|Professional|Plus) - Agents" +msgstr "Produkt: (Starter|Professional|Plus) - Agenten" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > VIP" -msgstr "Ticket > Organisation > VIP" +#: ../system/subscription.rst:78 +msgid "Choose the number of agents you require for your instance." +msgstr "Wählen Sie die Anzahl der Agenten, die Sie für Ihre Instanz benötigen." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.vip}``" -msgstr "``#{ticket.organization.vip}``" +#: ../system/subscription.rst:80 +msgid "" +"Keep in mind that some packages may have agent limits. Depending on the " +"previous chosen package, you won't be able to exceed specific agent numbers. " +"Also note that setting less agents than currently configured is not possible." +msgstr "" +"Beachten Sie, dass es bei einigen Paketen Obergrenzen für die Anzahl der " +"Agenten gibt. Je nach dem zuvor gewählten Paket können Sie eine bestimmte " +"Anzahl von Agenten nicht überschreiten. Beachten Sie auch, dass es nicht " +"möglich ist, weniger Agenten einzustellen als derzeit konfiguriert sind." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Number" -msgstr "Ticket > Nummer" +#: ../system/subscription.rst:86 +msgid "Total" +msgstr "Gesamt" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.number}``" -msgstr "``#{ticket.number}``" +#: ../system/subscription.rst:86 +msgid "This will be the net total you're going to be billed." +msgstr "Dies ist der Nettobetrag, der Ihnen in Rechnung gestellt wird." -#: ../system/variables/ticket.rst:1 -msgid "``31001``, ``201910731001``, ..." -msgstr "``31001``, ``201910731001``, ..." +#: ../system/subscription.rst:88 +msgid "" +"By using the *Update subscription* button, the instance package will be " +"adjusted immediately. If you didn't provide a payment method yet, Zammad " +"will request you to provide one at this point." +msgstr "" +"Wenn Sie die Schaltfläche *Abonnement aktualisieren* verwenden, wird Ihr " +"Instanzpaket sofort angepasst. Wenn Sie noch keine Zahlungsmethode angegeben " +"haben, wird Zammad Sie an dieser Stelle auffordern, eine anzugeben." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > ID" -msgstr "Ticket > ID" +#: ../system/subscription.rst:94 +msgid "" +"In case you're still within the trial period, this means that the trial will " +"be over immediately!" +msgstr "" +"Falls Sie sich noch im Testzeitraum befinden, wird die Probezeit sofort " +"beendet!" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.id}``" -msgstr "``#{ticket.id}``" +#: ../system/subscription.rst:97 +msgid "Down- or upgrading during the trial period *is not* possible." +msgstr "Ein Down- oder Upgrade während des Testzeitraums ist *nicht* möglich." -#: ../system/variables/ticket.rst:1 -msgid "``17``, ``5281``, ..." -msgstr "``17``, ``5281``, ..." +#: ../system/subscription.rst:None +msgid "Screenshot showing payment options and a pricing summary" +msgstr "Screenshot mit Zahlungsoptionen und einer Preisübersicht" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact (customer)" -msgstr "Ticket > letzter Kontakt (Kunde)" +#: ../system/subscription.rst:103 +#, fuzzy +#| msgid "Billing information" +msgid "Billing Information" +msgstr "Informationen zur Abrechnung" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_customer_at}``" -msgstr "``#{ticket.last_contact_customer_at}``" +#: ../system/subscription.rst:105 +#, fuzzy +#| msgid "" +#| "Within the billing tab you can control all billing relevant information " +#| "like invoices, billing address and the option to cancel your subscription." +msgid "" +"You can control all billing relevant information like invoices, billing " +"address and the option to cancel your subscription." +msgstr "" +"Auf der Registerkarte \"Abrechnung\" können Sie alle abrechnungsrelevanten " +"Informationen wie Rechnungen, Rechnungsadresse und die Option zur Kündigung " +"Ihres Abonnements kontrollieren." -#: ../system/variables/ticket.rst:1 +#: ../system/subscription.rst:108 msgid "" -"``2019-10-07 16:25:00 UTC`` or empty if not applicable yet (Please note " -"`Ticket last contact behavior Settings `_ for this)" +"All adjusted billing information below only affect future invoices. If your " +"invoice was issued wrong, please contact `our sales team `_." msgstr "" -"``2019-10-07 16:25:00 UTC`` oder leer, wenn noch nicht zutreffend (bitte " -"beachten Sie hierzu `Ticketeinstellung letzter Kontakt `_)" - -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact" -msgstr "Ticket > letzter Kontakt" - -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_at}``" -msgstr "``#{ticket.last_contact_at}``" +"Alle unten aufgeführten Rechnungsinformationen betreffen nur zukünftige " +"Rechnungen. Sollte eine Rechnung falsch ausgestellt worden sein, wenden Sie " +"sich bitte an `unser Sales-Team `_." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact (agent)" -msgstr "Ticket > letzter Kontakt (Agent)" +#: ../system/subscription.rst:114 +msgid "Billing address" +msgstr "Rechnungsadresse" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_agent_at}``" -msgstr "``#{ticket.last_contact_agent_at}``" +#: ../system/subscription.rst:113 +msgid "" +"Provide your company address here, make sure to include the companies name " +"in case required. This address will be referenced on your invoice." +msgstr "" +"Geben Sie hier die Adresse Ihres Unternehmens und den Namen Ihres " +"Unternehmens an. Diese angaben werden auf Ihrer Rechnung aufgeführt." -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable yet" -msgstr "``2019-10-07 16:25:00 UTC`` oder leer, wenn noch nicht zutreffend" +#: ../system/subscription.rst:118 +msgid "VAT ID" +msgstr "Mehrwertsteuernummer" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Note" -msgstr "Ticket > Gruppe > Notiz" +#: ../system/subscription.rst:117 +msgid "" +"Provide your VAT ID here. If applicable your invoice will not contain German " +"VAT. Please make sure to pay the VAT in your country as required." +msgstr "" +"Geben Sie hier Ihre Umsatzsteuer-ID an. Falls zutreffend, wird Ihre Rechnung " +"keine deutsche Mehrwertsteuer enthalten. Bitte vergewissern Sie sich, dass " +"Sie die Mehrwertsteuer in Ihrem Land wie erforderlich abführen." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.note}``" -msgstr "``#{ticket.group.note}``" +#: ../system/subscription.rst:127 +msgid "Billing Email Address" +msgstr "Rechnungs-E-Mail-Adresse" -#: ../system/variables/ticket.rst:1 -msgid "``Note about this group``" -msgstr "``Notiz über diese Gruppe``" +#: ../system/subscription.rst:121 +msgid "" +"Usually the instance owner (the person that registered the instance) will " +"receive all emails including the invoices. In case you have your own billing " +"department, you can provide their email address here." +msgstr "" +"Normalerweise erhält der Instanzinhaber (die Person, die die Instanz " +"registriert hat) alle E-Mails einschließlich der Rechnungen. Falls Sie eine " +"eigene Rechnungsabteilung haben, können Sie deren E-Mail-Adresse hier " +"angeben." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Name" -msgstr "Ticket > Gruppe > Name" +#: ../system/subscription.rst:125 +msgid "" +"All billing relevant information will then be sent to this email address." +msgstr "" +"Alle rechnungsrelevanten Informationen werden dann an diese E-Mail-Adresse " +"gesendet." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.name}``" -msgstr "``#{ticket.group.name}``" +#: ../system/subscription.rst:127 +msgid "Invoices are sent as attachment (PDF) to this email address." +msgstr "" +"Die Rechnungen werden als Anhang (PDF) an diese E-Mail-Adresse gesendet." -#: ../system/variables/ticket.rst:1 -msgid "``Sales``" -msgstr "``Verkauf``" +#: ../system/subscription.rst:129 +#, fuzzy +#| msgid "" +#| "Don't forget to press the *Submit* button after you changed above " +#| "settings." +msgid "" +"Don't forget to press the *Update billing information* button after you " +"changed above settings." +msgstr "" +"Vergessen Sie nicht, auf die Schaltfläche *Übermitteln* zu klicken, nachdem " +"Sie die obigen Einstellungen geändert haben." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Follow-up possible" -msgstr "Ticket > Gruppe > Nachfrage möglich" +#: ../system/subscription.rst:None +msgid "" +"Screenshot showing options for billing information within the\n" +"subscription menu" +msgstr "" +"Screenshot mit Optionen für Rechnungsinformationen im Menü \"Abonnement\"" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.follow_up_possible}``" -msgstr "``#{ticket.group.follow_up_possible}``" +#: ../system/subscription.rst:137 +#, fuzzy +#| msgid "Payment method" +msgid "Payment Method" +msgstr "Bezahlmethode" -#: ../system/variables/ticket.rst:1 -msgid "``no`` or ``yes``" -msgstr "``Nein`` oder ``Ja``" +#: ../system/subscription.rst:139 +msgid "You can pay via credit card or SEPA mandate." +msgstr "Sie können per Kreditkarte oder SEPA-Mandat bezahlen." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Assign Follow-Ups" -msgstr "Ticket > Gruppe > Zuweisung bei Nachfrage" +#: ../system/subscription.rst:144 +msgid "Credit card" +msgstr "Kreditkarte" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.follow_up_assignment}``" -msgstr "``#{ticket.group.follow_up_assignment}``" +#: ../system/subscription.rst:142 +#, fuzzy +#| msgid "" +#| "Simply follow the dialogue by clicking *authorize* and confirm -if " +#| "required by your bank- your consent to Zammad using your card for the " +#| "payments." +msgid "" +"Simply follow the dialogue by clicking *authorize credit card* and confirm -" +"if required by your bank- your consent to Zammad using your card for the " +"payments." +msgstr "" +"Folgen Sie einfach dem Dialog, indem Sie auf *Autorisieren* klicken und " +"bestätigen Sie - falls von Ihrer Bank verlangt - Ihr Einverständnis, dass " +"Zammad Ihre Karte für die Zahlungen verwendet." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Assignment Timeout" -msgstr "Ticket > Gruppe > Zeitliche Zuweisungsüberschreitung" +#: ../system/subscription.rst:148 +msgid "SEPA Direct Debit" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.assignment_timeout}``" -msgstr "``#{ticket.group.assignment_timeout}``" +#: ../system/subscription.rst:147 +msgid "" +"Provide the requested information of the bank account holder and update if " +"you're ready. You'll then receive an email with the SEPA mandate." +msgstr "" +"Geben Sie die angeforderten Informationen des Kontoinhabers an und " +"aktualisieren Sie sie, wenn Sie bereit sind. Sie erhalten dann eine E-Mail " +"mit dem SEPA-Mandat." -#: ../system/variables/ticket.rst:1 -msgid "``20`` or empty if not configured" -msgstr "``20`` oder leer, wenn nicht konfiguriert" +#: ../system/subscription.rst:150 +msgid "" +"Technically there's also the possibility to pay via invoice, however - this " +"method only applies to a fairly low number of instances. Please contact `our " +"sales team `_ for more information." +msgstr "" +"Technisch gesehen gibt es auch die Möglichkeit, per Rechnung zu bezahlen, " +"allerdings gilt diese Methode nur für eine relativ geringe Anzahl von " +"Fällen. Bitte kontaktieren Sie `unser Sales Team `_ für weitere Informationen." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > First response" -msgstr "Ticket > Erste Reaktion" +#: ../system/subscription.rst:156 +#, fuzzy +#| msgid "Subscription" +msgid "Cancel Subscription" +msgstr "Abonnement" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.first_response_at}``" -msgstr "``#{ticket.first_response_at}``" +#: ../system/subscription.rst:158 +#, fuzzy +#| msgid "" +#| "In case you no longer want to use Zammad's SaaS, you can cancel your " +#| "subscription by using the red *Yes, please cancel my subscription* button." +msgid "" +"Do you want to cancel your subscription? In case you no longer want to use " +"Zammad's SaaS, you can cancel your subscription by using the red *Yes, " +"please cancel my subscription* button." +msgstr "" +"Falls Sie Zammads SaaS nicht mehr nutzen möchten, können Sie Ihr Abonnement " +"über die rote Schaltfläche *Ja, ich möchte mein Abonnement kündigen* " +"kündigen." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Escalation at" -msgstr "Ticket > Eskalation am" +#: ../system/subscription.rst:162 +msgid "" +"To cancel the description, enter the FQDN of your Zammad instance and " +"provide a reason for your cancellation." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.escalation_at}``" -msgstr "``#{ticket.escalation_at}``" +#: ../system/subscription.rst:165 +msgid "" +"Your subscription will end the day after your trial or billing period ends." +msgstr "" +"Ihr Abonnement endet am Tag nach Ablauf Ihres Test- oder " +"Abrechnungszeitraums." -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable" -msgstr "``2019-10-07 16:25:00 UTC`` oder leer, falls nicht zutreffend" +#: ../system/subscription.rst:None +#, fuzzy +#| msgid "Screenshot showing certificate adding dialog" +msgid "Screenshot showing subscription cancellation dialog" +msgstr "Screenshot zeigt Dialog zum Hinzufügen von Zertifikaten" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Web" -msgstr "Ticket > Kunde > Web" +#: ../system/subscription.rst:174 +msgid "" +"We will remind you about your cancelled subscription several times up front. " +"After the subscription ended all instance data will be removed. A restore " +"*is not* possible after that point!" +msgstr "" +"Wir werden Sie mehrmals im Voraus an Ihr gekündigtes Abonnement erinnern. " +"Nach Beendigung des Abonnements werden alle Instanzdaten gelöscht. Eine " +"Wiederherstellung ist danach *nicht* möglich!" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.web}``" -msgstr "``#{ticket.customer.web}``" +#: ../system/subscription.rst:178 +msgid "**😖 Cancelled by accident?**" +msgstr "**😖 Aus Versehen gekündigt?**" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > VIP" -msgstr "Ticket > Kunde > VIP" +#: ../system/subscription.rst:180 +msgid "" +"You can always undo the cancellation via the *Yes, undo the cancellation of " +"my subscription* button up to the last subscription day!" +msgstr "" +"Sie können die Kündigung jederzeit über die Schaltfläche *Ja, meine " +"Abonnement-Kündigung soll widerrufen werden* bis zum letzten Abonnementtag " +"rückgängig machen!" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.vip}``" -msgstr "``#{ticket.customer.vip}``" +#: ../system/subscription.rst:0 +msgid "" +"Screenshot showing a red button to cancel the subscription\n" +"cancellation" +msgstr "Screenshot mit roter Schaltfläche zur Kündigung des Abonnements" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Phone" -msgstr "Ticket > Kunde > Telefon" +#: ../system/subscription.rst:189 +#, fuzzy +#| msgid "Payment history" +msgid "Payment History" +msgstr "Zahlungshistorie" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.phone}``" -msgstr "``#{ticket.customer.phone}``" +#: ../system/subscription.rst:191 +msgid "" +"The payment history will display a history of all paid invoices. At this " +"point you can also download these in case you need them again." +msgstr "" +"Der Zahlungsverlauf zeigt eine Übersicht aller bezahlten Rechnungen an. An " +"dieser Stelle können Sie diese auch herunterladen, falls Sie dieser nochmal " +"benötigen." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Note" -msgstr "Ticket > Kunde > Notiz" +#: ../system/subscription.rst:196 +msgid "" +"You will only find *paid* invoices here. Invoices that are to be billed are " +"not available before the payment is completed." +msgstr "" +"Sie werden hier nur *bezahlte* Rechnungen finden. Ausgestellte Rechnungen " +"sind nicht verfügbar, bevor die Zahlung eingegangen ist." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.note}``" -msgstr "``#{ticket.customer.note}``" +#: ../system/subscription.rst:201 +msgid "Date" +msgstr "Datum" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Mobile" -msgstr "Ticket > Kunde > Mobil" +#: ../system/subscription.rst:201 +msgid "Date of the invoice creation." +msgstr "Datum der Rechnungserstellung." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.mobile}``" -msgstr "``#{ticket.customer.mobile}``" +#: ../system/subscription.rst:204 +msgid "Amount" +msgstr "Betrag" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Login" -msgstr "Ticket > Kunde > Login" +#: ../system/subscription.rst:204 +msgid "Invoice total including VAT if applicable." +msgstr "Rechnungsbetrag einschließlich Mehrwertsteuer, falls zutreffend." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.login}``" -msgstr "``#{ticket.customer.login}``" +#: ../system/subscription.rst:207 +msgid "" +"Contains contract period (monthly or yearly) and hosted plan for the " +"subscription period in question." +msgstr "" +"Enthält die Vertragslaufzeit (monatlich oder jährlich) und den Hosting Plan " +"für die betreffende Abonnementdauer." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Lastname" -msgstr "Ticket > Kunde > Nachname" +#: ../system/subscription.rst:218 +msgid "Payment method / Service period" +msgstr "Bezahlmethode / Service-Zeitraum" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.lastname}``" -msgstr "``#{ticket.customer.lastname}``" +#: ../system/subscription.rst:211 +msgid "" +"Used bank account or credit card as well as the subscription period the " +"invoice is about." +msgstr "" +"Verwendete Bankverbindung oder Kreditkarte sowie der Abonnementzeitraum, auf " +"den sich die Rechnung bezieht." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Firstname" -msgstr "Ticket > Kunde > Vorname" +#: ../system/subscription.rst:216 +msgid "" +"It might happen that the invoice date and subscription period differ. This " +"is nothing to worry about, the subscription periods will be accounted later " +"on." +msgstr "" +"Es kann vorkommen, dass das Rechnungsdatum und der Abonnementzeitraum " +"voneinander abweichen. Das ist kein Grund zur Sorge, die Abonnementzeiträume " +"werden später verrechnet." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.firstname}``" -msgstr "``#{ticket.customer.firstname}``" +#: ../system/subscription.rst:222 +msgid "Receipt" +msgstr "Quittung" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Fax" -msgstr "Ticket > Kunde > Fax" +#: ../system/subscription.rst:221 +msgid "" +"Use the arrow to download the invoice in question. You can download all " +"available invoices any time you need to here!" +msgstr "" +"Verwenden Sie den Pfeil, um die betreffende Rechnung herunterzuladen. Sie " +"können alle verfügbaren Rechnungen jederzeit hier herunterladen!" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.fax}``" -msgstr "``#{ticket.customer.fax}``" +#: ../system/subscription.rst:None +msgid "Screenshot showing payment history of a hosted instance" +msgstr "Screenshot der Zahlungshistorie einer Hosting-Instanz" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Email" -msgstr "Ticket > Kunde > Email" +#: ../system/subscription.rst:229 +msgid "FAQ" +msgstr "FAQ" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.email}``" -msgstr "``#{ticket.customer.email}``" +#: ../system/subscription.rst:233 +msgid "I set up a trial account but am missing functions to test" +msgstr "" +"Ich habe ein Testkonto eingerichtet, aber mir fehlen Funktionen zum Testen" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Department" -msgstr "Ticket > Kunde > Abteilung" +#: ../system/subscription.rst:232 +msgid "" +"The trial instance is running within the professional package allowing up to " +"three agents." +msgstr "" +"Die Testinstanz läuft im Rahmen des Professional-Pakets und erlaubt bis zu " +"drei Agenten." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.department}``" -msgstr "``#{ticket.customer.department}``" +#: ../system/subscription.rst:236 +msgid "Can I change package within the trial?" +msgstr "Kann ich innerhalb der Testphase das Paket wechseln?" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Avatar" -msgstr "Ticket > Kunde > Avatar" +#: ../system/subscription.rst:236 +msgid "No. As soon as the package is changed the subscription begins." +msgstr "Nein. Sobald das Paket gewechselt wird, beginnt das Abonnement." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.avatar(60,60)}``" -msgstr "``#{ticket.customer.avatar(60,60)}``" +#: ../system/subscription.rst:241 +msgid "What happens to my trial instance after the trial period ended?" +msgstr "Was passiert mit meiner Testinstanz nach Ablauf des Testzeitraums?" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Address" -msgstr "Ticket > Kunde > Adresse" +#: ../system/subscription.rst:239 +msgid "" +"Your instance will automatically be canceled for you. Please see *What " +"happens to my instance after it has been canceled?* for more." +msgstr "" +"Ihre Instanz wird automatisch für Sie gekündigt. Weitere Informationen " +"finden Sie unter *Was passiert mit meiner Instanz, nachdem sie gekündigt " +"wurde?*." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.address}``" -msgstr "``#{ticket.customer.address}``" +#: ../system/subscription.rst:254 +msgid "What happens to my instance after it has been canceled?" +msgstr "Was passiert mit meiner Instanz, nachdem sie gekündigt wurde?" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Web" -msgstr "Ticket > Erstellt von > Web" +#: ../system/subscription.rst:244 +msgid "That depends slightly on your instance state:" +msgstr "Das hängt ein wenig vom Status Ihrer Instanz ab:" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.web}``" -msgstr "``#{ticket.created_by.web}``" +#: ../system/subscription.rst:250 +msgid "Trial instance" +msgstr "Test-Instanz" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > VIP" -msgstr "Ticket > Erstellt von > VIP" +#: ../system/subscription.rst:247 +msgid "" +"If you're still on trial, we will ice your instance and remind you once " +"again about your instance. We then will wait some days and remove your " +"instance from our system. This is the last time we will inform you by Email." +msgstr "" +"Wenn Sie sich noch im Testzeitraum befinden, werden wir Ihre Instanz " +"einfrieren und Sie noch einmal an Ihre Instanz erinnern. Wir werden dann " +"einige Tage warten und Ihre Instanz aus unserem System entfernen. Dies ist " +"das letzte Mal, dass wir Sie per E-Mail informieren." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.vip}``" -msgstr "``#{ticket.created_by.vip}``" +#: ../system/subscription.rst:254 +msgid "Paid instance" +msgstr "Bezahl-Instanz" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Phone" -msgstr "Ticket > Erstellt von > Telefon" +#: ../system/subscription.rst:253 +msgid "" +"If you're a paying customer and canceled your subscription, the instance " +"removal will take place the day after your last subscription day." +msgstr "" +"Wenn Sie ein zahlender Kunde sind und Ihr Abonnement gekündigt haben, " +"erfolgt die Entfernung der Instanz am Tag nach Ihrem letzten Abonnementtag." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.phone}``" -msgstr "``#{ticket.created_by.phone}``" +#: ../system/subscription.rst:256 +msgid "Can removed instances be restored?" +msgstr "Können entfernte Instanzen wiederhergestellt werden?" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Note" -msgstr "Ticket > Erstellt von > Notiz" +#: ../system/subscription.rst:257 +msgid "No. Once your instance has been removed, a restoration is not possible." +msgstr "" +"Nein. Sobald Ihre Instanz entfernt wurde, ist eine Wiederherstellung nicht " +"mehr möglich." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.note}``" -msgstr "``#{ticket.created_by.note}``" +#: ../system/system-report.rst:2 +msgid "System Report" +msgstr "System-Bericht" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Mobile" -msgstr "Ticket > Erstellt von > Mobil" +#: ../system/system-report.rst:4 +msgid "" +"In this place you can't configure Zammad. Instead you can obtain a system " +"report about Zammad and its configuration." +msgstr "" +"An dieser Stelle können Sie Zammad nicht konfigurieren. Stattdessen können " +"Sie einen Bericht über Zammad und seine Konfiguration abrufen." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.mobile}``" -msgstr "``#{ticket.created_by.mobile}``" +#: ../system/system-report.rst:7 +msgid "" +"See the description in Zammad for an explanation. You can even find a " +"preview of the included data below the **Download** button." +msgstr "" +"Lesen Sie die Beschreibung in Zammad für eine Erklärung der Funktion. Sie " +"können außerdem eine Vorschau der enthaltenen Daten unter der Schaltfläche " +"**Herunterladen** finden." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Login" -msgstr "Ticket > Erstellt von > Login" +#: ../system/system-report.rst:10 +msgid "" +"Zammad never sends this automatically to anyone. It is a manual process only " +"to provide better support based on your configuration." +msgstr "" +"Zammad sendet diese Daten niemals automatisch an irgendjemanden. Es handelt " +"sich um einen manuellen Prozess, der nur dazu dient, eine bessere " +"Unterstützung in Supportfällen auf der Grundlage Ihrer Konfiguration zu " +"bieten." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.login}``" -msgstr "``#{ticket.created_by.login}``" +#: ../system/translations.rst:2 +msgid "Translations" +msgstr "Übersetzungen" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Lastname" -msgstr "Ticket > Erstellt von > Nachname" +#: ../system/translations.rst:4 +msgid "" +"Translations of Zammad are processed centrally in our `Weblate instance " +"`_. This allows non-developers to review " +"and update translation texts of the language they actually speak." +msgstr "" +"Die Übersetzungen von Zammad werden zentral in unserer `Weblate-Instanz " +"`_ bearbeitet. So können auch Nicht-" +"Entwickler die Übersetzungstexte in der Sprache, die sie tatsächlich " +"sprechen, überprüfen und aktualisieren." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.lastname}``" -msgstr "``#{ticket.created_by.lastname}``" +#: ../system/translations.rst:9 +msgid "" +"Your language is in an incomplete translation state or has typos? Please " +"consider helping us in sorting this out! All you need is either a GitHub " +"account or to register directly in our instance." +msgstr "" +"Ihre Sprache ist unvollständig oder weist Tippfehler auf? Bitte helfen Sie " +"uns dabei, dies zu beheben! Alles, was Sie brauchen, ist entweder ein GitHub " +"Konto oder eine direkte Registrierung in unserer Instanz." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Firstname" -msgstr "Ticket > Erstellt von > Vorname" +#: ../system/translations.rst:13 +msgid "" +"Did you know? This is also where the documentation translations are handled. " +"🤓" +msgstr "" +"Wussten Sie das? Hier werden auch die Übersetzungen der Dokumentation " +"vorgenommen. 🤓" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.firstname}``" -msgstr "``#{ticket.created_by.firstname}``" +#: ../system/translations.rst:15 +msgid "" +"Have a look in our :docs:`contribution section ` in the system documentation to get started!" +msgstr "" +"Werfen Sie einen Blick in unseren :docs:`Contribution Bereich ` in der Systemdokumentation, um loszulegen!" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Fax" -msgstr "Ticket > Erstellt von > Fax" +#: ../system/translations.rst:20 +msgid "Local Translations" +msgstr "Lokale Übersetzungen" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.fax}``" -msgstr "``#{ticket.created_by.fax}``" +#: ../system/translations.rst:22 +msgid "" +"Apart from these system translations, there's still local translations you " +"can manage. This is relevant if you added custom objects that require " +"translations or even custom states and priorities." +msgstr "" +"Abgesehen von diesen Systemübersetzungen können Sie auch noch lokale " +"Übersetzungen verwalten. Dies ist wichtig, wenn Sie benutzerdefinierte " +"Objekte hinzugefügt haben, die Übersetzungen erfordern, oder sogar " +"benutzerdefinierte Status und Prioritäten." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Email" -msgstr "Ticket > Erstellt von > Email" +#: ../system/translations.rst:None +msgid "Translation management screen within the admin menu" +msgstr "Ansicht der Übersetzungsverwaltung im Admin Menü" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.email}``" -msgstr "``#{ticket.created_by.email}``" +#: ../system/translations.rst:31 +msgid "Updating Translations" +msgstr "Aktualisierung von Übersetzungen" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Department" -msgstr "Ticket > Erstellt von > Abteilung" +#: ../system/translations.rst:33 +msgid "" +"Because of how Zammad ships translations, the only way to update the system " +"translations is to update your Zammad installation. The benefit of this is " +"that you no longer need internet access during a Zammad upgrade as the " +"package has everything it requires already." +msgstr "" +"Aufgrund der Art und Weise wie Zammad Übersetzungen ausliefert, ist die " +"Aktualisierung Ihrer Zammad-Installation die einzige Möglichkeit, die " +"Systemübersetzungen zu aktualisieren. Der Vorteil dabei ist, dass Sie " +"während eines Zammad-Upgrades keinen Internetzugang mehr benötigen, da das " +"Paket bereits alles enthält, was es benötigt." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.department}``" -msgstr "``#{ticket.created_by.department}``" +#: ../system/translations.rst:39 +msgid "Translation of Custom Objects" +msgstr "Übersetzung von benutzerdefinierten Objekten" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Avatar" -msgstr "Ticket > Erstellt von > Avatar" +#: ../system/translations.rst:41 +msgid "" +"No problem at all! You can customize any translation locally, even if it is " +"not initially provided by the system." +msgstr "" +"Überhaupt kein Problem! Sie können jede Übersetzung lokal anpassen, auch " +"wenn sie ursprünglich nicht vom System bereitgestellt wurde." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.avatar(60,60)}``" -msgstr "``#{ticket.created_by.avatar(60,60)}``" +#: ../system/translations.rst:44 +msgid "" +"Translation is supported for a broad number of features, including but not " +"limited to custom:" +msgstr "" +"Die Übersetzung wird für eine große Anzahl von Funktionen unterstützt, " +"einschließlich, aber nicht beschränkt auf benutzerdefinierte:" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Address" -msgstr "Ticket > Erstellt von > Adresse" +#: ../system/translations.rst:47 +msgid "Object Attributes" +msgstr "Objekt-Attribute" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.address}``" -msgstr "``#{ticket.created_by.address}``" +#: ../system/translations.rst:48 +msgid "Ticket Macros" +msgstr "Ticket-Makros" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created at" -msgstr "Ticket > Erstellt am" +#: ../system/translations.rst:49 +msgid "Ticket Overviews" +msgstr "Ticket-Übersichten" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_at}``" -msgstr "``#{ticket.created_at}``" +#: ../system/translations.rst:50 +msgid "Ticket Priorities" +msgstr "Ticket-Prioritäten" -#: ../system/variables/ticket.rst:1 -msgid "2019-10-07 16:25:00 UTC" -msgstr "2019-10-07 16:25:00 UTC" +#: ../system/translations.rst:51 +msgid "Ticket States" +msgstr "Ticket-Status" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Closing time" -msgstr "Ticket > Schließzeit" +#: ../system/translations.rst:54 +msgid "Customizing Translations" +msgstr "Übersetzungen anpassen" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.close_at}``" -msgstr "``#{ticket.close_at}``" +#: ../system/translations.rst:56 +msgid "" +"Within the translation screen, simply click on the **New Translation** " +"button." +msgstr "" +"Klicken Sie in der Ansicht \"Übersetzung\" einfach auf die Schaltfläche " +"**Neue Übersetzung**." -#: ../system/variables/ticket.rst:1 -msgid "2019-10-07 17:25:00 UTC" -msgstr "2019-10-07 17:25:00 UTC" +#: ../system/translations.rst:None +msgid "New translation dialog" +msgstr "Dialog neue Übersetzung" -#: ../system/variables/ticket.rst:1 -msgid "``3``, any number of articles existing in the ticket right now" +#: ../system/translations.rst:62 +msgid "" +"In the dialog you can immediately enter the exact translation source (if you " +"know it) and your custom translation text for it and click **Submit**." msgstr "" -"``3``, eine beliebige Anzahl von Artikeln, die derzeit im Ticket vorhanden " -"sind" +"In dem Dialog können Sie sofort die genaue Übersetzungsquelle (sofern Sie " +"diese kennen) und Ihren individuellen Übersetzungstext eingeben und auf " +"**Übermitteln** klicken." -#: ../system/version.rst:2 -msgid "Version" -msgstr "Version" +#: ../system/translations.rst:65 +msgid "" +"Alternatively, try to search for translation suggestions in the list below. " +"Selecting an item from the list will pre-fill the translation source for you " +"and then you can just enter your custom translation." +msgstr "" +"Alternativ können Sie auch in der Liste unten nach Übersetzungsvorschlägen " +"suchen. Wenn Sie ein Element aus der Liste auswählen, wird die " +"Übersetzungsquelle für Sie vorausgefüllt und Sie können dann einfach Ihre " +"eigene Übersetzung eingeben." -#: ../system/version.rst:4 -msgid "Shows which version is currently being used on your Zammad-instance." +#: ../system/translations.rst:69 +msgid "" +"The target language will always default to your current language selection. " +"If you need to translate for a different language, simply change the " +"selection before submitting." msgstr "" -"Zeigt an, welche Version derzeit auf Ihrer Zammad-Instanz verwendet wird." +"Als Zielsprache wird immer die von Ihnen gewählte Sprache verwendet. Wenn " +"Sie für eine andere Sprache übersetzen wollen, ändern Sie die Auswahl " +"einfach vor dem Übermitteln." -#: ../manage/roles/admin-permissions.rst:53 -msgid "``admin.checklist``" -msgstr "``admin.checklist``" +#: ../system/translations.rst:73 +msgid "" +"All your custom translations will show up in the overview table when added. " +"And they will even persist across Zammad updates!" +msgstr "" +"Alle Ihre benutzerdefinierten Übersetzungen werden in der Übersichtstabelle " +"angezeigt, wenn sie hinzugefügt werden. Und sie bleiben sogar bei " +"Aktualisierungen von Zammad erhalten!" -#: ../manage/roles/admin-permissions.rst:54 -msgid ":doc:`Manage > Checklist `" -msgstr "doc:`Verwalten> Checklisten `" +#: ../system/translations.rst:76 +msgid "" +"Make sure to reload your browser if a translated string is not displayed." +msgstr "" +"Aktualisieren Sie die Seite im Browser, falls eine Übersetzung nicht " +"angezeigt wird." -#: ../manage/roles/admin-permissions.rst:83 -msgid "``admin.channel_whatsapp``" -msgstr "``admin.channel_whatsapp``" +#: ../system/translations.rst:80 +msgid "Reverting to Original Translations" +msgstr "Zurücksetzen auf Originalübersetzungen" -#: ../manage/roles/admin-permissions.rst:84 -msgid ":doc:`Channels > Whatsapp `" -msgstr "doc:`Kanäle > Whatsapp `" +#: ../system/translations.rst:82 +msgid "" +"If you want to revert a custom translation to original text, simply use the " +"appropriate action within the row of the overview table." +msgstr "" +"Wenn Sie eine benutzerdefinierte Übersetzung auf die ursprüngliche " +"Übersetzung zurücksetzen möchten, verwenden Sie einfach die entsprechende " +"Aktion in der Zeile der Übersichtstabelle." -#: ../manage/roles/admin-permissions.rst:124 -msgid "``admin.public_links``" -msgstr "``admin.public_links``" +#: ../system/translations.rst:85 +msgid "" +"Depending on the type of the translation source, the action has a slightly " +"different name:" +msgstr "" +"Je nach Art der Übersetzungsquelle hat die Aktion einen etwas anderen Namen:" -#: ../manage/roles/admin-permissions.rst:125 -msgid ":doc:`Manage > Public Links `" -msgstr "doc:`Verwalten > Öffentliche Links `" +#: ../system/translations.rst:88 +msgid "**Reset** for customized system translations" +msgstr "**Zurücksetzen** für angepasste Systemübersetzungen" -#: ../manage/roles/admin-permissions.rst:151 -msgid "``admin.system_report``" -msgstr "``admin.system_report``" +#: ../system/translations.rst:89 +msgid "**Remove** for customized local translations" +msgstr "**Entfernen** für angepasste lokale Übersetzungen" -#: ../manage/roles/admin-permissions.rst:152 -msgid ":doc:`System > System Report `" -msgstr ":doc:`System > System-Bericht `" +#: ../system/translations.rst:91 +msgid "" +"In both cases, the action will remove the customized translation after a " +"confirmation." +msgstr "" +"In beiden Fällen wird die benutzerdefinierte Übersetzung nach einer " +"Bestätigung entfernt." -#: ../manage/roles/admin-permissions.rst:166 -msgid "``admin.ticket_auto_assignment``" -msgstr "``admin.ticket_auto_assignment``" +#: ../system/translations.rst:None +msgid "Screenshot showing the location of the Remove action" +msgstr "Screenshot, der die Aktion \"Entfernen\" zeigt" -#: ../manage/roles/admin-permissions.rst:167 -msgid ":ref:`Settings > Ticket > Auto Assignment `" -msgstr "" -":ref:`Einstellungen > Ticket > Automatische Zuweisung `" +#: ../system/translations.rst:99 +msgid "Inline Translations" +msgstr "Inline-Übersetzungen" -#: ../manage/roles/admin-permissions.rst:169 -msgid "``admin.ticket_duplicate_detection``" -msgstr "``admin.ticket_duplicate_detection``" +#: ../system/translations.rst:101 +msgid "" +"If you prefer a more hands-on approach, you can activate the inline or on-" +"screen translation feature by pressing ``ctrl`` + ``alt`` + ``t`` at any " +"time and on any screen." +msgstr "" +"Wenn Sie es lieber etwas praktischer mögen, können Sie die Inline- oder On-" +"Screen-Übersetzung durch Drücken von ``strg`` + ``alt`` + ``t`` jederzeit " +"und in jeder Ansicht aktivieren." -#: ../manage/roles/admin-permissions.rst:170 -msgid ":ref:`Settings > Ticket > Duplicate Detection `" +#: ../system/translations.rst:105 +msgid "" +"All customizable translation texts will be highlighted for you on the " +"screen. Just click into the highlighted area and update the text in place." msgstr "" -":ref:`Einstellungen > Ticket > Duplikaterkennung `" +"Alle anpassbaren Übersetzungstexte werden für Sie auf dem Bildschirm " +"hervorgehoben. Klicken Sie einfach in den markierten Bereich und " +"aktualisieren Sie den Text an Ort und Stelle." -#: ../manage/roles/admin-permissions.rst:172 -msgid "``admin.ticket_priority``" -msgstr "``admin.ticket_priority``" +#: ../system/translations.rst:None +msgid "Inline translation mode activated for the Overview screen" +msgstr "Inline-Übersetzungsmodus für die Ansicht \"Übersicht\"" -#: ../manage/roles/admin-permissions.rst:173 -msgid ":ref:`System > Objects >Ticket Priority `" -msgstr ":ref:`System > Objekte >Ticket-Priorität `" +#: ../system/translations.rst:112 +msgid "" +"When finished editing, simply press ``ctrl`` + ``alt`` + ``t`` again to " +"deactivate." +msgstr "" +"Wenn Sie mit der Bearbeitung fertig sind, drücken Sie einfach wieder " +"``strg`` + ``alt`` + ``t``, um die Bearbeitung zu deaktivieren." -#: ../manage/roles/admin-permissions.rst:175 -msgid "``admin.ticket_state``" -msgstr "``admin.ticket_state``" +#: ../system/translations.rst:117 +msgid "" +"Even though it's available on any screen, the inline translation feature " +"requires admin permissions. It works only for the current language " +"selection. If you need to translate a different language, first change the " +"language in your :user-docs:`profile settings `." +msgstr "" +"Obwohl die Inline-Übersetzungsfunktion auf jeder Ansicht verfügbar ist, " +"erfordert sie Administratorrechte. Sie funktioniert nur für die aktuelle " +"Sprachauswahl. Wenn Sie eine andere Sprache übersetzen müssen, ändern Sie " +"zunächst die Sprache in Ihren :user-docs:`Profileinstellungen `." -#: ../manage/roles/admin-permissions.rst:176 -msgid ":ref:`System > Objects >Ticket State `" -msgstr ":ref:`System > Objekte >Ticket-Status `" +#: ../system/version.rst:2 +msgid "Version" +msgstr "Version" -#: ../manage/roles/admin-permissions.rst:193 -msgid "``admin.webhook``" -msgstr "``admin.webhook``" +#: ../system/version.rst:4 +msgid "Shows which version is currently being used on your Zammad-instance." +msgstr "" +"Zeigt an, welche Version derzeit auf Ihrer Zammad-Instanz verwendet wird." -#: ../manage/roles/admin-permissions.rst:194 -msgid ":doc:`Manage > Webhook `" -msgstr "doc:`Verwalten > Webhook `" +#~ msgid "Billing" +#~ msgstr "Abrechnungen" -#: ../manage/roles/user-preferences-permissions.rst:43 -msgid "``user_preferences.appearance``" -msgstr "``user_preferences.appearance``" +#~ msgid "Do you want to cancel your subscription?" +#~ msgstr "Wollen Sie Ihr Abonnement kündigen?" -#: ../manage/roles/user-preferences-permissions.rst:44 -msgid "Appearance configuration" -msgstr "Konfiguration Aussehen" +#~ msgid "Screencast showing how to cancel a subscription" +#~ msgstr "Screencast, der zeigt, wie man ein Abonnement kündigt" -#: ../manage/roles/user-preferences-permissions.rst:0 -msgid "Users can switch between dark, light and" -msgstr "Benutzer können zwischen Dunkel-, Hell- und" +#~ msgid "" +#~ "The subscription section currently consists of two tabs: Plan & Billing. " +#~ "For your overview we've divided those two tabs into independent sub pages:" +#~ msgstr "" +#~ "Der Bereich Abonnement besteht derzeit aus zwei Tabs: Produkt & " +#~ "Abrechnung. Zu Ihrer Übersicht haben wir diese beiden Registerkarten in " +#~ "unabhängige Unterseiten unterteilt:" -#: ../manage/roles/user-preferences-permissions.rst:0 -msgid "automatic mode." -msgstr "Auutomatik-Modus wechseln." +#~ msgid ":doc:`💰 Subscription plan `" +#~ msgstr ":doc:`💰 Abonnement Produkt `" -#: ../system/system-report.rst:2 -msgid "System Report" -msgstr "System-Bericht" +#~ msgid ":doc:`🧾 Subscription billing `" +#~ msgstr ":doc:`🧾 Abonnement Abrechnungen `" -#: ../system/system-report.rst:4 -msgid "" -"In this place you can't configure Zammad. Instead you can obtain a system " -"report about Zammad and its configuration." -msgstr "" -"An dieser Stelle können Sie Zammad nicht konfigurieren. Stattdessen können " -"Sie einen Bericht über Zammad und seine Konfiguration abrufen." +#~ msgid "" +#~ "Everything regarding billing address, invoices and account cancellation." +#~ msgstr "Alles über Rechnungsadresse, Rechnungen und Kündigung." -#: ../system/system-report.rst:7 -msgid "" -"See the description in Zammad for an explanation. You can even find a " -"preview of the included data below the **Download** button." -msgstr "" -"Lesen Sie die Beschreibung in Zammad für eine Erklärung der Funktion. Sie " -"können außerdem eine Vorschau der enthaltenen Daten unter der Schaltfläche " -"**Herunterladen** finden." +#~ msgid "Summary" +#~ msgstr "Zusammenfassung" -#: ../system/system-report.rst:10 -msgid "" -"Zammad never sends this automatically to anyone. It is a manual process only " -"to provide better support based on your configuration." -msgstr "" -"Zammad sendet diese Daten niemals automatisch an irgendjemanden. Es handelt " -"sich um einen manuellen Prozess, der nur dazu dient, eine bessere " -"Unterstützung in Supportfällen auf der Grundlage Ihrer Konfiguration zu " -"bieten." +#~ msgid "SEPA" +#~ msgstr "SEPA" #~ msgid "" #~ "Please note that this part of our documentation currently is outdated. We " diff --git a/locale/es/LC_MESSAGES/admin-docs.po b/locale/es/LC_MESSAGES/admin-docs.po index 12f67437..15567d98 100644 --- a/locale/es/LC_MESSAGES/admin-docs.po +++ b/locale/es/LC_MESSAGES/admin-docs.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Zammad\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-11-06 10:31+0100\n" +"POT-Creation-Date: 2024-11-12 16:31+0100\n" "PO-Revision-Date: 2024-10-18 22:00+0000\n" "Last-Translator: Marian \n" "Language-Team: Spanish Checklist `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:56 msgid "``admin.channel_email``" msgstr "" -#: ../manage/roles/admin-permissions.rst:54 #: ../manage/roles/admin-permissions.rst:57 msgid ":doc:`Channels > Email `" msgstr "" -#: ../manage/roles/admin-permissions.rst:56 #: ../manage/roles/admin-permissions.rst:59 msgid "``admin.channel_facebook``" msgstr "" -#: ../manage/roles/admin-permissions.rst:57 #: ../manage/roles/admin-permissions.rst:60 msgid ":doc:`Channels > Facebook `" msgstr "" -#: ../manage/roles/admin-permissions.rst:58 #: ../manage/roles/admin-permissions.rst:61 msgid "" "Accessing Facebook tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:59 #: ../manage/roles/admin-permissions.rst:62 msgid "``admin.channel_formular``" msgstr "" -#: ../manage/roles/admin-permissions.rst:60 #: ../manage/roles/admin-permissions.rst:63 msgid ":doc:`Channels > Form `" msgstr "" -#: ../manage/roles/admin-permissions.rst:62 #: ../manage/roles/admin-permissions.rst:65 msgid "``admin.channel_google``" msgstr "" -#: ../manage/roles/admin-permissions.rst:63 #: ../manage/roles/admin-permissions.rst:66 msgid ":doc:`Channels > Google `" msgstr "" -#: ../manage/roles/admin-permissions.rst:65 #: ../manage/roles/admin-permissions.rst:68 msgid "``admin.channel_microsoft365``" msgstr "" -#: ../manage/roles/admin-permissions.rst:66 #: ../manage/roles/admin-permissions.rst:69 msgid ":doc:`Channels > Microsoft 365 `" msgstr "" -#: ../manage/roles/admin-permissions.rst:68 #: ../manage/roles/admin-permissions.rst:71 msgid "``admin.channel_sms``" msgstr "" -#: ../manage/roles/admin-permissions.rst:69 #: ../manage/roles/admin-permissions.rst:72 msgid ":doc:`Channels > SMS `" msgstr "" -#: ../manage/roles/admin-permissions.rst:71 #: ../manage/roles/admin-permissions.rst:74 msgid "``admin.channel_telegram``" msgstr "" -#: ../manage/roles/admin-permissions.rst:72 #: ../manage/roles/admin-permissions.rst:75 msgid ":doc:`Channels > Telegram `" msgstr "" -#: ../manage/roles/admin-permissions.rst:73 #: ../manage/roles/admin-permissions.rst:76 msgid "" "Accessing Telegram tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:74 #: ../manage/roles/admin-permissions.rst:77 msgid "``admin.channel_twitter``" msgstr "" -#: ../manage/roles/admin-permissions.rst:75 #: ../manage/roles/admin-permissions.rst:78 msgid ":doc:`Channels > Twitter `" msgstr "" -#: ../manage/roles/admin-permissions.rst:76 #: ../manage/roles/admin-permissions.rst:79 msgid "" "Accessing Twitter/X tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:77 #: ../manage/roles/admin-permissions.rst:80 msgid "``admin.channel_web``" msgstr "" -#: ../manage/roles/admin-permissions.rst:78 #: ../manage/roles/admin-permissions.rst:81 msgid ":doc:`Channels > Web `" msgstr "" -#: ../manage/roles/admin-permissions.rst:80 +#: ../manage/roles/admin-permissions.rst:83 +msgid "``admin.channel_whatsapp``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:84 +msgid ":doc:`Channels > Whatsapp `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:86 msgid "``admin.core_workflows``" msgstr "" -#: ../manage/roles/admin-permissions.rst:81 #: ../manage/roles/admin-permissions.rst:87 msgid ":doc:`System > Core Workflows `" msgstr "" -#: ../manage/roles/admin-permissions.rst:83 #: ../manage/roles/admin-permissions.rst:89 msgid "``admin.data_privacy``" msgstr "" -#: ../manage/roles/admin-permissions.rst:84 #: ../manage/roles/admin-permissions.rst:90 msgid ":doc:`System > Data Privacy `" msgstr "" -#: ../manage/roles/admin-permissions.rst:85 #: ../manage/roles/admin-permissions.rst:91 msgid "" "🔥 Be careful, it allows users to permanently delete data on the system." msgstr "" -#: ../manage/roles/admin-permissions.rst:86 #: ../manage/roles/admin-permissions.rst:92 msgid "``admin.group``" msgstr "" -#: ../manage/roles/admin-permissions.rst:87 #: ../manage/roles/admin-permissions.rst:93 msgid ":doc:`Manage > Groups `" msgstr "" -#: ../manage/roles/admin-permissions.rst:89 #: ../manage/roles/admin-permissions.rst:95 msgid "``admin.integration``" msgstr "" -#: ../manage/roles/admin-permissions.rst:90 #: ../manage/roles/admin-permissions.rst:96 msgid ":doc:`System > Integrations `" msgstr "" -#: ../manage/roles/admin-permissions.rst:92 #: ../manage/roles/admin-permissions.rst:98 msgid "``admin.knowledge_base``" msgstr "" -#: ../manage/roles/admin-permissions.rst:93 #: ../manage/roles/admin-permissions.rst:99 msgid ":doc:`Manage > Knowledge Base `" msgstr "" @@ -8702,57 +8685,46 @@ msgid "" "knowledge-base.html#editing-answers>`." msgstr "" -#: ../manage/roles/admin-permissions.rst:98 #: ../manage/roles/admin-permissions.rst:104 msgid "``admin.macro``" msgstr "" -#: ../manage/roles/admin-permissions.rst:99 #: ../manage/roles/admin-permissions.rst:105 msgid ":doc:`Manage > Macros `" msgstr "" -#: ../manage/roles/admin-permissions.rst:100 #: ../manage/roles/admin-permissions.rst:106 msgid "In some cases, macros may also require ``admin.tag``" msgstr "" -#: ../manage/roles/admin-permissions.rst:101 #: ../manage/roles/admin-permissions.rst:107 msgid "``admin.maintenance``" msgstr "" -#: ../manage/roles/admin-permissions.rst:102 #: ../manage/roles/admin-permissions.rst:108 msgid ":doc:`System > Maintenance `" msgstr "" -#: ../manage/roles/admin-permissions.rst:104 #: ../manage/roles/admin-permissions.rst:110 msgid "``admin.monitoring``" msgstr "" -#: ../manage/roles/admin-permissions.rst:105 #: ../manage/roles/admin-permissions.rst:111 msgid ":doc:`System > Monitoring `" msgstr "" -#: ../manage/roles/admin-permissions.rst:107 #: ../manage/roles/admin-permissions.rst:113 msgid "``admin.object``" msgstr "" -#: ../manage/roles/admin-permissions.rst:108 #: ../manage/roles/admin-permissions.rst:114 msgid ":doc:`System > Objects `" msgstr "" -#: ../manage/roles/admin-permissions.rst:110 #: ../manage/roles/admin-permissions.rst:116 msgid "``admin.organization``" msgstr "" -#: ../manage/roles/admin-permissions.rst:111 #: ../manage/roles/admin-permissions.rst:117 msgid ":doc:`Manage > Organizations `" msgstr "" @@ -8769,202 +8741,213 @@ msgstr "" msgid "They can even edit an organization's name, domain, and notes!" msgstr "" -#: ../manage/roles/admin-permissions.rst:115 #: ../manage/roles/admin-permissions.rst:121 msgid "``admin.overview``" msgstr "" -#: ../manage/roles/admin-permissions.rst:116 #: ../manage/roles/admin-permissions.rst:122 msgid ":doc:`Manage > Overviews`" msgstr "" -#: ../manage/roles/admin-permissions.rst:118 +#: ../manage/roles/admin-permissions.rst:124 +msgid "``admin.public_links``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:125 +msgid ":doc:`Manage > Public Links `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:127 msgid "``admin.package``" msgstr "" -#: ../manage/roles/admin-permissions.rst:119 #: ../manage/roles/admin-permissions.rst:128 msgid ":doc:`System > Packages `" msgstr "" -#: ../manage/roles/admin-permissions.rst:121 #: ../manage/roles/admin-permissions.rst:130 msgid "``admin.report_profile``" msgstr "" -#: ../manage/roles/admin-permissions.rst:122 #: ../manage/roles/admin-permissions.rst:131 msgid ":doc:`Manage > Report Profiles `" msgstr "" -#: ../manage/roles/admin-permissions.rst:123 #: ../manage/roles/admin-permissions.rst:132 msgid "Access to view reports: ``report``" msgstr "" -#: ../manage/roles/admin-permissions.rst:124 #: ../manage/roles/admin-permissions.rst:133 msgid "``admin.role``" msgstr "" -#: ../manage/roles/admin-permissions.rst:125 #: ../manage/roles/admin-permissions.rst:134 msgid ":doc:`Manage > Roles `" msgstr "" -#: ../manage/roles/admin-permissions.rst:127 #: ../manage/roles/admin-permissions.rst:136 msgid "``admin.scheduler``" msgstr "" -#: ../manage/roles/admin-permissions.rst:128 #: ../manage/roles/admin-permissions.rst:137 msgid ":doc:`Manage > Scheduler `" msgstr "" -#: ../manage/roles/admin-permissions.rst:129 #: ../manage/roles/admin-permissions.rst:138 msgid "For automation on tickets" msgstr "" -#: ../manage/roles/admin-permissions.rst:130 #: ../manage/roles/admin-permissions.rst:139 msgid "``admin.security``" msgstr "" -#: ../manage/roles/admin-permissions.rst:131 #: ../manage/roles/admin-permissions.rst:140 msgid ":doc:`Settings > Security `" msgstr "" -#: ../manage/roles/admin-permissions.rst:132 #: ../manage/roles/admin-permissions.rst:141 msgid "Settings of Zammad. This also covers third party authentications." msgstr "" -#: ../manage/roles/admin-permissions.rst:133 #: ../manage/roles/admin-permissions.rst:142 msgid "``admin.session``" msgstr "" -#: ../manage/roles/admin-permissions.rst:134 #: ../manage/roles/admin-permissions.rst:143 msgid ":doc:`System > Sessions `" msgstr "" -#: ../manage/roles/admin-permissions.rst:136 #: ../manage/roles/admin-permissions.rst:145 msgid "``admin.setting_system``" msgstr "" -#: ../manage/roles/admin-permissions.rst:137 #: ../manage/roles/admin-permissions.rst:146 msgid ":doc:`Settings > System `" msgstr "" -#: ../manage/roles/admin-permissions.rst:139 #: ../manage/roles/admin-permissions.rst:148 msgid "``admin.sla``" msgstr "" -#: ../manage/roles/admin-permissions.rst:140 #: ../manage/roles/admin-permissions.rst:149 msgid ":doc:`Manage > SLAs `" msgstr "" -#: ../manage/roles/admin-permissions.rst:142 +#: ../manage/roles/admin-permissions.rst:151 +msgid "``admin.system_report``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:152 +msgid ":doc:`System > System Report `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:154 msgid "``admin.tag``" msgstr "" -#: ../manage/roles/admin-permissions.rst:143 #: ../manage/roles/admin-permissions.rst:155 msgid ":doc:`Manage > Tags `" msgstr "" -#: ../manage/roles/admin-permissions.rst:145 #: ../manage/roles/admin-permissions.rst:157 msgid "``admin.template``" msgstr "" -#: ../manage/roles/admin-permissions.rst:146 #: ../manage/roles/admin-permissions.rst:158 msgid ":doc:`Manage > Templates `" msgstr "" -#: ../manage/roles/admin-permissions.rst:148 #: ../manage/roles/admin-permissions.rst:160 msgid "``admin.text_module``" msgstr "" -#: ../manage/roles/admin-permissions.rst:149 #: ../manage/roles/admin-permissions.rst:161 msgid ":doc:`Manage > Text Modules `" msgstr "" -#: ../manage/roles/admin-permissions.rst:151 #: ../manage/roles/admin-permissions.rst:163 msgid "``admin.ticket``" msgstr "" -#: ../manage/roles/admin-permissions.rst:152 #: ../manage/roles/admin-permissions.rst:164 msgid ":doc:`Settings > Tickets `" msgstr "" -#: ../manage/roles/admin-permissions.rst:153 #: ../manage/roles/admin-permissions.rst:165 msgid "Does not grant access to :doc:`/misc/composer`" msgstr "" -#: ../manage/roles/admin-permissions.rst:154 +#: ../manage/roles/admin-permissions.rst:166 +#, fuzzy +msgid "``admin.ticket_auto_assignment``" +msgstr "``#{ticket.group.follow_up_assignment}``" + +#: ../manage/roles/admin-permissions.rst:167 +msgid ":ref:`Settings > Ticket > Auto Assignment `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:169 +msgid "``admin.ticket_duplicate_detection``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:170 +msgid ":ref:`Settings > Ticket > Duplicate Detection `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:172 +#, fuzzy +msgid "``admin.ticket_priority``" +msgstr "prioridad" + +#: ../manage/roles/admin-permissions.rst:173 +msgid ":ref:`System > Objects >Ticket Priority `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:175 +#, fuzzy +msgid "``admin.ticket_state``" +msgstr "Ticket > Creado en" + +#: ../manage/roles/admin-permissions.rst:176 +msgid ":ref:`System > Objects >Ticket State `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:178 msgid "``admin.time_accounting``" msgstr "" -#: ../manage/roles/admin-permissions.rst:155 #: ../manage/roles/admin-permissions.rst:179 msgid ":doc:`Manage > Time Accounting `" msgstr "" -#: ../manage/roles/admin-permissions.rst:156 #: ../manage/roles/admin-permissions.rst:180 msgid "Also allows the export of timekeeping records." msgstr "" -#: ../manage/roles/admin-permissions.rst:157 #: ../manage/roles/admin-permissions.rst:181 msgid "``admin.translation``" msgstr "" -#: ../manage/roles/admin-permissions.rst:158 #: ../manage/roles/admin-permissions.rst:182 msgid ":doc:`System > Translations `" msgstr "" -#: ../manage/roles/admin-permissions.rst:159 #: ../manage/roles/admin-permissions.rst:183 msgid "Also enables inline translation" msgstr "" -#: ../manage/roles/admin-permissions.rst:160 #: ../manage/roles/admin-permissions.rst:184 msgid "``admin.trigger``" msgstr "" -#: ../manage/roles/admin-permissions.rst:161 #: ../manage/roles/admin-permissions.rst:185 msgid ":doc:`Manage > Triggers `" msgstr "" -#: ../manage/roles/admin-permissions.rst:163 #: ../manage/roles/admin-permissions.rst:187 msgid "``admin.user``" msgstr "" -#: ../manage/roles/admin-permissions.rst:164 #: ../manage/roles/admin-permissions.rst:188 msgid ":doc:`Manage > Users `" msgstr "" @@ -8983,6 +8966,14 @@ msgid "" "from-users-perspective>` ." msgstr "" +#: ../manage/roles/admin-permissions.rst:193 +msgid "``admin.webhook``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:194 +msgid ":doc:`Manage > Webhook `" +msgstr "" + #: ../manage/roles/agent-permissions.rst:2 msgid "Agent Permissions" msgstr "" @@ -9403,37 +9394,46 @@ msgid "than the user that generated them." msgstr "" #: ../manage/roles/user-preferences-permissions.rst:43 +msgid "``user_preferences.appearance``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:44 +msgid "Appearance configuration" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "Users can switch between dark, light and" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "automatic mode." +msgstr "" + #: ../manage/roles/user-preferences-permissions.rst:47 msgid "``user_preferences.avatar``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:44 #: ../manage/roles/user-preferences-permissions.rst:48 #, fuzzy msgid "Avatar settings" msgstr "Verificación de correo electrónico" -#: ../manage/roles/user-preferences-permissions.rst:45 #: ../manage/roles/user-preferences-permissions.rst:49 msgid "Override the default Gravatar with a custom avatar" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:46 #: ../manage/roles/user-preferences-permissions.rst:50 msgid "``user_preferences.calendar``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:47 #: ../manage/roles/user-preferences-permissions.rst:51 msgid "Configure the calendar feed" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:49 #: ../manage/roles/user-preferences-permissions.rst:53 msgid "``user_preferences.device``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:50 #: ../manage/roles/user-preferences-permissions.rst:54 msgid "Manage device login sessions" msgstr "" @@ -9450,22 +9450,18 @@ msgstr "" msgid "To learn more, see :doc:`/manage/trigger/system-notifications`." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:54 #: ../manage/roles/user-preferences-permissions.rst:58 msgid "``user_preferences.language``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:55 #: ../manage/roles/user-preferences-permissions.rst:59 msgid "Configure the UI locale/language" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:57 #: ../manage/roles/user-preferences-permissions.rst:61 msgid "``user_preferences.linked_accounts``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:58 #: ../manage/roles/user-preferences-permissions.rst:62 #, fuzzy msgid "Account linking" @@ -9490,7 +9486,6 @@ msgstr "" msgid "is the only way users can utilize third-party logins." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:63 #: ../manage/roles/user-preferences-permissions.rst:67 msgid "``user_preferences.notifications``" msgstr "" @@ -9518,7 +9513,6 @@ msgstr "" msgid "Customers can't receive ticket notifications at all." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:69 #: ../manage/roles/user-preferences-permissions.rst:73 msgid "``user_preferences.out_of_office``" msgstr "" @@ -9543,7 +9537,6 @@ msgstr "" msgid "they're replacing." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:75 #: ../manage/roles/user-preferences-permissions.rst:79 msgid "``user_preferences.overview_sorting``" msgstr "" @@ -9572,12 +9565,10 @@ msgstr "" msgid "overviews has no effect on custom orders." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:82 #: ../manage/roles/user-preferences-permissions.rst:86 msgid "``user_preferences.password``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:83 #: ../manage/roles/user-preferences-permissions.rst:87 msgid "Change account password" msgstr "" @@ -9594,7 +9585,6 @@ msgstr "" msgid "your only allowed authentication method." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:87 #: ../manage/roles/user-preferences-permissions.rst:91 msgid "``user_preferences.two_factor_authentication``" msgstr "" @@ -9631,7 +9621,7 @@ msgstr "" #: ../manage/scheduler.rst:19 msgid "" -"Schedulers can be used to send periodic reminder emails. Use :doc:`/system/" +"Schedulers can be used to send periodic reminder emails. Use :doc:`/misc/" "variables` to build highly-customized email templates." msgstr "" @@ -10629,7 +10619,7 @@ msgstr "" #: ../manage/text-modules.rst:57 msgid "" -"The example text modules below use :doc:`/system/variables` to dynamically " +"The example text modules below use :doc:`/misc/variables` to dynamically " "insert information like the customer's or agent's names." msgstr "" @@ -10970,8 +10960,8 @@ msgstr "" #: ../misc/object-conditions/basics.rst:144 #: ../misc/object-conditions/basics.rst:160 #: ../misc/object-conditions/basics.rst:168 -#: ../misc/object-conditions/basics.rst:178 ../settings/ticket.rst:2 -#: ../system/variables/ticket.rst:2 +#: ../misc/object-conditions/basics.rst:178 ../misc/variables/ticket.rst:2 +#: ../settings/ticket.rst:2 msgid "Ticket" msgstr "" @@ -11205,7 +11195,7 @@ msgstr "" #: ../manage/trigger/how-do-they-work.rst:79 msgid "" -"Certain actions (such as *email*, *SMS* and *notes*) support :doc:`/system/" +"Certain actions (such as *email*, *SMS* and *notes*) support :doc:`/misc/" "variables`, which can be used to build highly-customized message templates." msgstr "" @@ -11234,7 +11224,7 @@ msgstr "" msgid "" "You can also combine static text with placeholders for text fields. Remember " "that the placeholders' values have to be known during trigger runtime. Learn " -"more about :doc:`/system/variables`." +"more about :doc:`/misc/variables`." msgstr "" #: ../manage/trigger/how-do-they-work.rst:105 @@ -12200,7 +12190,7 @@ msgstr "" msgid "" "When switched on, a code editor will be shown below, where you can configure " "custom payload for your webhook in JSON format. To insert supported :doc:`/" -"system/variables` use ``::`` or ``#{`` shortcuts for autocomplete." +"misc/variables` use ``::`` or ``#{`` shortcuts for autocomplete." msgstr "" #: ../manage/webhook/add.rst:103 @@ -14807,12022 +14797,11915 @@ msgid "" "powerful conditions with AND/OR relations." msgstr "" -#: ../settings/branding.rst:10 -msgid "Product Name" +#: ../misc/variables.rst:2 +msgid "Variables" msgstr "" -#: ../settings/branding.rst:7 +#: ../misc/variables.rst:4 msgid "" -"Defines the name of the application, shown in the web interface, tabs and " -"title bar of the web browser." +"Please note that this is just an overview of available variables. It might " +"be incomplete or variables might not be available within some functions. If " +"you're missing variables or are not sure if something is not working as " +"expected, feel free to ask over at the `Community `_." msgstr "" -#: ../settings/branding.rst:10 -msgid "Default value: ``Zammad Helpdesk``" +#: ../misc/variables.rst:10 +msgid "" +"Variables can be called by typing ``::`` (just like text modules in the " +"frontend), as long as you're in a supported text field within the backend. " +"Zammad will display all variables being available within this context and " +"replace it to the variable as soon as you selected an entry." msgstr "" -#: ../settings/branding.rst:13 -msgid "Will be shown in the app and is included in email footers." +#: ../misc/variables.rst:15 +msgid "" +"You have an empty field which you referenced and it appears as ``-``? That's " +"currently working as designed - you might want to ensure that these fields " +"always have a value." msgstr "" -#: ../settings/branding.rst:19 -msgid "Logo" +#: ../misc/variables.rst:20 +msgid "Variable Categories" msgstr "" -#: ../settings/branding.rst:16 -msgid "Defines the logo of the application, shown in the login page of Zammad." +#: ../misc/variables.rst:31 +msgid "Wait, What About Custom Objects?" msgstr "" -#: ../settings/branding.rst:18 +#: ../misc/variables.rst:33 msgid "" -"Ensure to hit the \"Submit\" button after uploading the logo. Otherwise your " -"change will not be saved." +"Good point! Of course, we can't predict what objects you might create, but " +"we can give you a hint on how to put the puzzle together to get your custom " +"values." msgstr "" -#: ../settings/branding.rst:22 +#: ../misc/variables.rst:36 msgid "" -"Allows to set the default language of the Zammad instance. The here defined " -"locale mostly acts as a fallback for:" +"For this, we'll talk about the inner part of the variable (so everything " +"within ``#{}``), please put the outer part around to have a valid variable. " +"The first part of the variable name consist of the object type. Currently " +"these are:" msgstr "" -#: ../settings/branding.rst:25 -msgid "user preferences (if Zammad can't detect the users locale)" +#: ../misc/variables.rst:41 +msgid "Ticket (``ticket``)" msgstr "" -#: ../settings/branding.rst:26 -msgid "CSV output (reporting, time accounting)" +#: ../misc/variables.rst:42 +msgid "User (``user``)" msgstr "" -#: ../settings/branding.rst:30 -msgid "Define the timezone of your Zammad installation." +#: ../misc/variables.rst:43 +msgid "Organization (``organization``)" msgstr "" -#: ../settings/branding.rst:32 -msgid "" -"This does not have any effect on timings for your agents or how Zammad " -"stores date and time values." +#: ../misc/variables.rst:44 +msgid "Group (``group``)" msgstr "" -#: ../settings/branding.rst:35 -msgid "Changing this value has direct consequences on the following areas:" +#: ../misc/variables.rst:46 +msgid "" +"The second part is the name of the attribute. This is the name you define " +"during object creation and can be found within the object attribute menu at " +"any time. The first and second part of a variable is divided by a point, e." +"g.: ``ticket.number`` which will in total be ``#{ticket.number}``." msgstr "" -#: ../settings/branding.rst:37 -msgid ":doc:`/manage/scheduler` tasks" +#: ../misc/variables.rst:51 +msgid "" +"Now, in some situations it's possible that you'll need to use a third part. " +"The best example for such a situation would be a ``select`` or ``tree-" +"select`` field which will by default return the key value, not it's display " +"name. For this, just extend your variable with ``.value``. This will result " +"in ``#{ticket.select.value}``." msgstr "" -#: ../settings/branding.rst:38 -msgid "search indexing (and thus reporting)" +#: ../misc/variables.rst:60 +msgid "Using Translated Variables" msgstr "" -#: ../settings/branding.rst:40 -msgid "calendar subscriptions" +#: ../misc/variables.rst:62 +msgid "" +"If you want to use a translated variable in triggers or schedulers, you can " +"extend the placeholder like this: ``#{t(ticket.state.name)}``. The ``t`` " +"tells Zammad to search for fitting translated strings. The used output " +"language is based on the system language of Zammad which you can set in the " +"admin panel under :doc:`/settings/branding` or based on the selected locale " +"in the trigger/scheduler edit dialog." msgstr "" -#: ../settings/branding.rst:41 -msgid "browser printing" +#: ../misc/variables.rst:69 +msgid "" +"A possible use-case: you want to send your customers updates on tickets via " +"trigger or scheduler which should include the state of the ticket. Using the " +"default ``#{ticket.state.name}`` (without the translation flag ``t()``) " +"would lead to the output of the original (english) name of the state." msgstr "" -#: ../settings/branding.rst:43 -msgid "" -"Please note that some of above are fallbacks in case Zammad could not detect " -"the agents timezone correctly." +#: ../misc/variables.rst:75 +msgid "Date and Time Formatting" msgstr "" -#: ../settings/branding.rst:77 -msgid "Pretty Date" +#: ../misc/variables.rst:77 +msgid "" +"The system (trigger/scheduler selected) locale and timezone predefines a " +"default format of date and timestamp. This format is customizable by using " +"the ``dt()`` method." msgstr "" -#: ../settings/branding.rst:47 -msgid "" -"This setting allows you to define how Zammad should display time stamps " -"within the interface to all users." +#: ../misc/variables.rst:79 +msgid "The method arguments are as follows:" msgstr "" -#: ../settings/branding.rst:50 -msgid "" -"This does not have any effect on how Zammad returns e.g. time values via " -"variables." +#: ../misc/variables.rst:81 +msgid "The date or timestamp variable you want to format." msgstr "" -#: ../settings/branding.rst:77 -msgid "Choose in between the following options:" +#: ../misc/variables.rst:82 +msgid "The output format string." msgstr "" -#: ../settings/branding.rst:64 -msgid "relative" +#: ../misc/variables.rst:83 +msgid "The timezone to apply (optional)." msgstr "" -#: ../settings/branding.rst:55 +#: ../misc/variables.rst:85 +#: ../system/objects/external-data-source-example.rst:23 +#, fuzzy +msgid "**Example:**" +msgstr "Ejemplo" + +#: ../misc/variables.rst:86 msgid "" -"This timestamp shows a relative time span until it switches to a date. Over " -"time, it will change as follows:" +"``#{dt(ticket.updated_at, \"%A %Y-%m-%d %H:%M in the office\", \"Europe/" +"Berlin\")}``" msgstr "" -#: ../settings/branding.rst:58 -msgid "just now" +#: ../misc/variables.rst:87 +msgid "Monday, 2024-03-18 15:31 in the office" msgstr "" -#: ../settings/branding.rst:59 -msgid "5 minutes ago" +#: ../misc/variables.rst:89 +msgid "" +"If you want to use our example, make sure to paste the string above without " +"formatting (``CTRL+Shift+v``), otherwise it won't work." msgstr "" -#: ../settings/branding.rst:60 -msgid "3 days 1 hour ago" +#: ../misc/variables.rst:93 +msgid "The following table lists available format directives:" msgstr "" -#: ../settings/branding.rst:61 -msgid "``03/04/2022``" +#: ../misc/variables.rst:99 +msgid "Parameter" msgstr "" -#: ../settings/branding.rst:63 -msgid "Hovering the timestamp helps, you'll always get a clean timestamp then." +#: ../misc/variables.rst:102 +msgid "``%Y``" msgstr "" -#: ../settings/branding.rst:71 -msgid "absolute" +#: ../misc/variables.rst:103 +msgid "Year with 4 digits" msgstr "" -#: ../settings/branding.rst:67 -msgid "" -"This timestamp always includes the week day. For one week after creation, " -"the timestamp will not contain the date itself: Thursday 18:35." +#: ../misc/variables.rst:104 +msgid "Use ``%y`` for year with 2 digits" msgstr "" -#: ../settings/branding.rst:71 -msgid "After a week it will switch to: ``Friday 4. Mar 16:00``." +#: ../misc/variables.rst:105 +msgid "``%m``" msgstr "" -#: ../settings/branding.rst:76 -msgid "timestamp" +#: ../misc/variables.rst:106 +msgid "Month of year (as number with zero-padding)" msgstr "" -#: ../settings/branding.rst:74 -msgid "" -"This will cause Zammad to show a complete timestamp according to your locale " -"defaults. For English this could be e.g. ``2022/12/03 2:40 pm`` or for " -"German e.g. ``12.03.2022 14:40``." +#: ../misc/variables.rst:107 +msgid "Use ``%-m`` for month without zero-padding" msgstr "" -#: ../settings/branding.rst:78 -msgid "Default setting: ``relative``." +#: ../misc/variables.rst:108 +msgid "``%d``" msgstr "" -#: ../settings/security.rst:2 -msgid "Security" +#: ../misc/variables.rst:109 +msgid "Day of month (as number with zero-padding)" msgstr "" -#: ../settings/security.rst:4 -msgid "" -"For your overview we split each tab within security settings into its own " -"page:" +#: ../misc/variables.rst:110 +msgid "Use ``%e`` for day without zero-padding" msgstr "" -#: ../settings/security/base.rst:2 ../settings/system/base.rst:2 -#: ../settings/ticket.rst:8 -msgid "Base" +#: ../misc/variables.rst:111 +msgid "``%H``" msgstr "" -#: ../settings/security/base.rst:5 -msgid "New User Accounts" +#: ../misc/variables.rst:112 +msgid "Hour of day in 24h notation with zero-padding" msgstr "" -#: ../settings/security/base.rst:9 -msgid "" -"Activates the `register as a new customer` function on the login page. If " -"set to ``no`` only administrators or agents can create new accounts manually." +#: ../misc/variables.rst:113 +msgid "Use ``%k`` for hour without zero-padding" msgstr "" -#: ../settings/security/base.rst:13 ../settings/security/base.rst:38 -#: ../settings/security/base.rst:66 -msgid "Default setting: ``yes``" +#: ../misc/variables.rst:114 +msgid "``%I``" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing activated \"New User Accounts\" setting" +#: ../misc/variables.rst:115 +msgid "Hour of day in 12h notation with zero-padding" msgstr "" -#: ../settings/security/base.rst:22 +#: ../misc/variables.rst:116 msgid "" -"Deactivation of above function **does not** deactivate automatic account " -"creation! This means: If a user writes e.g. an email to Zammad and has no " -"account yet, Zammad will automatically create the account. User accounts are " -"a direct dependency of tickets and thus technically mandatory." +"Use ``%l`` for hour without zero-padding and ``%p`` / ``%P`` for meridian " +"indicator" msgstr "" -#: ../settings/security/base.rst:29 -msgid "Lost Password" +#: ../misc/variables.rst:117 +msgid "``%M``" msgstr "" -#: ../settings/security/base.rst:33 -msgid "" -"Activates the `lost password` function on the login page. If set to ``no`` " -"only administrators may change the user's password - users may update their " -"own password if they're still logged in and they have the required :doc:" -"`permission `." +#: ../misc/variables.rst:118 +msgid "Minute of hour" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing activated \"Lost Password\" setting" +#: ../misc/variables.rst:120 +msgid "``%S``" msgstr "" -#: ../settings/security/base.rst:49 -msgid "" -"With third party authentications - but especially LDAP - you may want to " -"disable this function. Zammad **will not** change third party login " -"passwords and instead set or change the local password!" +#: ../misc/variables.rst:121 +msgid "Second of Minute" msgstr "" -#: ../settings/security/base.rst:56 -msgid "Password Login" +#: ../misc/variables.rst:123 +msgid "``%A``" msgstr "" -#: ../settings/security/base.rst:60 -msgid "" -"Activates the username & password login by default and if no third-party " -"login is activated. Disabling password login on the Zammad login page only " -"takes effect if you enable any :doc:`third-party`." +#: ../misc/variables.rst:124 +msgid "Weekday name" msgstr "" -#: ../settings/security/base.rst:64 -msgid "See :doc:`third-party` for supported third-party logins." +#: ../misc/variables.rst:125 +msgid "Use ``%a`` for abbreviated name or ``%^A`` for uppercase name" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing de-activated \"Password Login\" setting" +#: ../misc/variables.rst:126 +msgid "``%B``" msgstr "" -#: ../settings/security/base.rst:77 -msgid "" -"To help administrators to overcome \"login issues\", Zammad automatically " -"offers a password request for administrator users. This allows you to adjust " -"Third-Party applications even if the login does no longer work!" +#: ../misc/variables.rst:127 +msgid "Month name" msgstr "" -#: ../settings/security/base.rst:84 -msgid "Session Timeout" +#: ../misc/variables.rst:128 +msgid "Use ``%b`` for abbreviated name" msgstr "" -#: ../settings/security/base.rst:86 -msgid "" -"All settings below by default are set to ``4 weeks``. Session Timeout " -"defines the life time of a users session. As soon as it's reached, Zammad " -"will automatically log off the session in question." +#: ../misc/variables.rst:129 +msgid "``%U``" msgstr "" -#: ../settings/security/base.rst:91 -msgid "" -"Zammad takes the highest value set assigned for the user based on the " -"permissions." +#: ../misc/variables.rst:130 +msgid "Week number of current year" msgstr "" -#: ../settings/security/base.rst:94 -msgid "``admin``" +#: ../misc/variables.rst:131 +msgid "Use ``%W`` for a different calculation method" msgstr "" -#: ../settings/security/base.rst:96 -msgid "``ticket.customer``" +#: ../misc/variables.rst:134 +msgid "" +"We support the known format directives for the Ruby built-in method " +"``strftime`` of the ``DateTime`` class. For more information, see `here " +"`_." msgstr "" -#: ../settings/security/base.rst:97 -msgid "``default`` (fallback if user doesn't have above permissions set)" +#: ../misc/variables/article.rst:2 +msgid "Articles" msgstr "" -#: ../settings/security/base.rst:99 +#: ../misc/variables/article.rst:4 ../misc/variables/config.rst:4 +#: ../misc/variables/current-user.rst:4 ../misc/variables/ticket.rst:4 msgid "" -"All settings act independently from each other allowing you to disable the " -"timeouts for e.g. admins, but not agents." +"If you're missing variables or are not sure if something is not working as " +"expected, feel free to ask over at the `Community `_." msgstr "" -#: ../settings/security/base.rst:115 -#: ../system/integrations/checkmk/api-reference.rst:13 -msgid "Example" -msgstr "Ejemplo" +#: ../misc/variables/article.rst:6 +msgid "" +"Below you can find all available ticket article-based variables within " +"Zammad. These can be called via triggers for example. If you're unsure if " +"Zammad does support variables at the point you're at, you can try to type " +"``::`` to check." +msgstr "" -#: ../settings/security/base.rst:107 -msgid "Let's suppose you configured the following session timeouts" +#: ../misc/variables/article.rst:9 ../misc/variables/config.rst:9 +#: ../misc/variables/ticket.rst:9 +msgid "" +"The below list gives you an example what kind of data you can expect, it's " +"not intended to explain the data itself." msgstr "" -#: ../settings/security/base.rst:104 -msgid "default: 3 weeks" +#: ../misc/variables/article.rst:11 +msgid "Article Variables" msgstr "" -#: ../settings/security/base.rst:105 -msgid "admin: 2 weeks" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "name" msgstr "" -#: ../settings/security/base.rst:106 -msgid "ticket.agent: 4 weeks" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "variable" msgstr "" -#: ../settings/security/base.rst:107 -msgid "ticket.customer: 1 week" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "example" msgstr "" -#: ../settings/security/base.rst:115 -msgid "This results in the following situations" +#: ../misc/variables/article.rst:1 +msgid "Article > Cc" msgstr "" -#: ../settings/security/base.rst:110 -msgid "a user with ``admin`` permission will have a timeout of 2 weeks" +#: ../misc/variables/article.rst:1 +msgid "``#{article.cc}``" msgstr "" -#: ../settings/security/base.rst:111 -msgid "" -"a user with ``admin`` and ``ticket.agent`` permissions will have a timeout " -"of 2 weeks" +#: ../misc/variables/article.rst:1 +msgid "``jdoe@example.com, company@example.com``" msgstr "" -#: ../settings/security/base.rst:113 -msgid "" -"a user with ``ticket.customer`` permission will have a timeout of 1 week" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Address" msgstr "" -#: ../settings/security/base.rst:115 -msgid "" -"a user with neither ``admin``, ``ticket.agent`` nor ``ticket.customer`` " -"permissions will have a timeout of 3 weeks" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.address}``" msgstr "" -#: ../settings/security/password.rst:4 -msgid "" -"This section allows you to define password requirements for the local user " -"accounts." +#: ../misc/variables/article.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:9 -msgid "" -"Zammad does **not** allow you to change your LDAP password, instead, it will " -"set a password in its local database which might confuse your users. This " -"might be addressed in the future by `#1169 `_." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Department" msgstr "" -#: ../settings/security/password.rst:14 -msgid "**Exception for admins**" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.department}``" msgstr "" -#: ../settings/security/password.rst:16 -msgid "" -"Please note that below password policies *do not* affect administrators " -"setting passwords on user accounts. While this seems strange and not safe we " -"believe that an administrator knowing an user's password is insecure as well." +#: ../misc/variables/article.rst:1 +msgid "``Sales`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:21 -msgid "The suggested workflow is either:" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Email" msgstr "" -#: ../settings/security/password.rst:23 -msgid "" -"to use third party logins to not require local passwords at all **- or -**" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.email}``" msgstr "" -#: ../settings/security/password.rst:25 -msgid "to require your *user to reset the password* upon first login." +#: ../misc/variables/article.rst:1 +msgid "``jdoe@example.com``" msgstr "" -#: ../settings/security/password.rst:27 -msgid "" -"This way administrators are not required to set a user's password at all!" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Fax" msgstr "" -#: ../settings/security/password.rst:31 -msgid "Maximum Failed Logins" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.fax}``" msgstr "" -#: ../settings/security/password.rst:33 -msgid "" -"You can choose a value between ``4`` and ``20``. This defines how often a " -"login to a user account may fail until Zammad will lock it. Your users can " -"always use the \"forgot password\" function to change their password and " -"unlock their account." +#: ../misc/variables/article.rst:1 +msgid "``+4930123456789`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:38 -msgid "The default value is ``10``." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Firstname" msgstr "" -#: ../settings/security/password.rst:42 -msgid "Beside changing the user's password, you can also unlock accounts via" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.firstname}``" msgstr "" -#: ../settings/security/password.rst:44 -msgid ":ref:`user management list `" +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Joe`` or empty if not set" msgstr "" -#: ../settings/security/password.rst:45 -msgid ":docs:`console `" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Lastname" msgstr "" -#: ../settings/security/password.rst:46 -msgid ":docs:`API `" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.lastname}``" msgstr "" -#: ../settings/security/password.rst:50 -msgid "Failed logins via LDAP no longer lock accounts." +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +#: ../misc/variables/ticket.rst:1 +msgid "``Doe`` or empty if not set" msgstr "" -#: ../settings/security/password.rst:53 -msgid "2 Lower Case And 2 Upper Case Characters" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Login" msgstr "" -#: ../settings/security/password.rst:55 -msgid "" -"You can add complexity to passwords by enforcing at least 2 upper and lower " -"case characters." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.login}``" msgstr "" -#: ../settings/security/password.rst:58 ../settings/security/password.rst:83 -msgid "The default value is ``no``." +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +#: ../misc/variables/ticket.rst:1 +msgid "``jdoe``" msgstr "" -#: ../settings/security/password.rst:62 -msgid "Minimum Length" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Mobile" msgstr "" -#: ../settings/security/password.rst:64 -msgid "" -"This defines the minimum password length required for users to provide (from " -"``4`` to ``20``)." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.mobile}``" msgstr "" -#: ../settings/security/password.rst:67 -msgid "The default value is ``6``." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Note" msgstr "" -#: ../settings/security/password.rst:71 -msgid "Digit Required" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.note}``" msgstr "" -#: ../settings/security/password.rst:73 -msgid "This enforces your users to use at least one digit within the password." +#: ../misc/variables/article.rst:1 +msgid "``Some note about user`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:75 -msgid "The default value is ``yes``." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Phone" msgstr "" -#: ../settings/security/password.rst:78 -msgid "Special Character Required" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.phone}``" msgstr "" -#: ../settings/security/password.rst:80 -msgid "" -"This setting allows you to improve your password quality even more by " -"enforcing the password to contain at least one special character." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > VIP" msgstr "" -#: ../settings/security/ssl-certificates.rst:2 -msgid "SSL Certificates" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.vip}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:7 -msgid "" -"Zammad offers the possibility to upload custom certificates and custom " -"Certificate Authority (CA) certificates. This can be useful if you want to " -"connect Zammad the secure way to other systems which are using custom " -"certificates." +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +msgid "``true`` or ``false``" msgstr "" -#: ../settings/security/ssl-certificates.rst:12 -msgid "" -"An example usecase might be: You have an internal LDAP server that is not " -"accessible from the internet, and you want a SSL-encrypted connection, using " -"a custom certificate." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Web" msgstr "" -#: ../settings/security/ssl-certificates.rst:19 -msgid "" -"You should have an existing custom certificate file and/or a custom CA " -"certificate file, which you want to add to Zammad. As filetype ``.crt`` is " -"supported and the certificate format has to be PEM (Base64 ASCII)." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.web}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:25 -msgid "" -"When you import a custom CA certificate, all certificates generated with " -"this are trusted. This can be useful if you have more than one system/" -"certificate you want to connect to and the certificates are issued from the " -"same custom CA." +#: ../misc/variables/article.rst:1 +msgid "``https://zammad.com`` or empty if not set in user object" msgstr "" -#: ../settings/security/ssl-certificates.rst:31 -msgid "Add a Certificate" +#: ../misc/variables/article.rst:1 +msgid "Article > Created" msgstr "" -#: ../settings/security/ssl-certificates.rst:33 -msgid "" -"To add a custom certificate or a custom CA certificate, head over to the " -"Admin panel > Settings > Security > SSL Certificates. Here you can find a " -"\"Add SSL Certificate\" button. In the dialog you can either select a " -"certificate file or paste the content of the certificate:" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_at}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate adding dialog" +#: ../misc/variables/article.rst:1 +msgid "``2019-10-08 15:24:47 UTC``" msgstr "" -#: ../settings/security/ssl-certificates.rst:43 -msgid "" -"After selecting a file or pasting the content of the certificate, click on " -"the \"Add\" button to finally upload it to Zammad. Then, the certificates " -"are immediately effective, no restart or similar required." +#: ../misc/variables/article.rst:1 +msgid "Article > From" msgstr "" -#: ../settings/security/ssl-certificates.rst:49 -msgid "" -"Please note that only single certificate files are supported. That means if " -"you want to import a certificate / CA certificate, it must contain **only " -"one** certificate." +#: ../misc/variables/article.rst:1 +msgid "``#{article.from}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:54 -msgid "Certificate Overview" +#: ../misc/variables/article.rst:1 +msgid "" +"``Joe Doe `` may differ, depends on ``FROM`` of send mail" msgstr "" -#: ../settings/security/ssl-certificates.rst:56 -msgid "" -"After you added a certificate, you can see a table with information for each " -"added certificate:" +#: ../misc/variables/article.rst:1 +msgid "Article > Sender > Name" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing table of added certificates" +#: ../misc/variables/article.rst:1 +msgid "``#{article.sender.name}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:64 -msgid "" -"Here you can download the certificate or delete it, if you don't need it " -"anymore." +#: ../misc/variables/article.rst:1 +msgid "``Customer``, ``Agent`` or ``System``" msgstr "" -#: ../settings/security/ssl-certificates.rst:68 -#, fuzzy -msgid "Deleting Certificates" -msgstr "Verificación de correo electrónico" +#: ../misc/variables/article.rst:1 +msgid "Article > Subject" +msgstr "" -#: ../settings/security/ssl-certificates.rst:70 -msgid "" -"If you want to delete a specific certificate, you can do it by clicking on " -"the menu in the actions column and selecting delete:" +#: ../misc/variables/article.rst:1 +msgid "``#{article.subject}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate deletion button" +#: ../misc/variables/article.rst:1 +msgid "``My amazing subject``" msgstr "" -#: ../settings/security/ssl-certificates.rst:79 -msgid "Downloading Certificates" +#: ../misc/variables/article.rst:1 +msgid "Article > Text" msgstr "" -#: ../settings/security/ssl-certificates.rst:81 -msgid "" -"If you want to download your certificates, you can do this as well via " -"corresponding action buttons." +#: ../misc/variables/article.rst:1 +msgid "``#{article.body}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate download button" +#: ../misc/variables/article.rst:1 +msgid "``Test`` without formatting (plain)" msgstr "" -#: ../settings/security/third-party.rst:13 -msgid "Login Providers" +#: ../misc/variables/article.rst:1 +msgid "Article > TicketID" msgstr "" -#: ../settings/security/third-party.rst:2 -msgid "Third-Party Applications" +#: ../misc/variables/article.rst:1 +msgid "``#{article.ticket_id}``" msgstr "" -#: ../settings/security/third-party.rst:4 -msgid "" -"Third party authentication is a great way to help your users to login to " -"Zammad more easily. If the account is yet unknown, Zammad will create a new " -"user automatically, without the user needed to interact (e.g. type in his " -"name). Another big advantage of this feature is that your user doesn't need " -"to remember another password." +#: ../misc/variables/article.rst:1 +msgid "``1`` (not ticket number)" msgstr "" -#: ../settings/security/third-party.rst:10 -msgid "" -"You can deactivate logging in via :ref:`security_password_login` if any of " -"the mentioned authentication providers are enabled in your instance." +#: ../misc/variables/article.rst:1 +msgid "Article > To" msgstr "" -#: ../settings/security/third-party.rst:27 -msgid "" -"We're currently missing documentation for the following login providers:" +#: ../misc/variables/article.rst:1 +msgid "``#{article.to}``" msgstr "" -#: ../settings/security/third-party.rst:29 -msgid "LinkedIn" +#: ../misc/variables/article.rst:1 +msgid "``helpdesk@example.com``" msgstr "" -#: ../settings/security/third-party.rst:30 -msgid "Weibo" +#: ../misc/variables/article.rst:1 +msgid "Article > Type > Name" msgstr "" -#: ../settings/security/third-party.rst:35 -#, fuzzy -msgid "Automatic Account Link on Initial Logon" -msgstr "Notificación automática de vinculación de cuentas" +#: ../misc/variables/article.rst:1 +msgid "``#{article.type.name}``" +msgstr "" -#: ../settings/security/third-party.rst:37 +#: ../misc/variables/article.rst:1 msgid "" -"In general there's two possible options for Zammad on how to deal with " -"already known users as they try to authenticate against a third-party " -"application. By default, Zammad will not automatically link \"unknown\" " -"authentication providers to existing accounts." +"``email`` (`list of article types `_)" msgstr "" -#: ../settings/security/third-party.rst:42 -msgid "" -"This means that the user has to manually link authentication providers to " -"their accounts (for more about this :user-docs:`consult the user " -"documentation `)." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Address" msgstr "" -#: ../settings/security/third-party.rst:46 -msgid "" -"Sometimes this doesn't come in handy as this also means you'll receive error " -"messages about \"email address being in use already\" for (yet) unknown " -"third-party authentication methods." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.address}``" msgstr "" -#: ../settings/security/third-party.rst:50 -msgid "" -"If you want to allow your users to always be able to log in, no matter what, " -"you may want to enable ``Automatic account link on initial logon``." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Department" msgstr "" -#: ../settings/security/third-party.rst:None -msgid "" -"Screenshot highlighting the \"Automatic account link on initial logon\"\n" -"setting" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.department}``" msgstr "" -#: ../settings/security/third-party.rst:60 -#, fuzzy -msgid "Automatic Account Linking Notification" -msgstr "Notificación automática de vinculación de cuentas" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Email" +msgstr "" -#: ../settings/security/third-party.rst:64 -msgid "" -"To improve security and your users awareness, you can enable Zammad to " -"notify your users when a new third-party application has been linked to " -"their account." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.email}``" msgstr "" -#: ../settings/security/third-party.rst:68 -msgid "" -"This notification is sent out once per third-party application. Zammad does " -"also mention the method used, e.g.: ``Microsoft``." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Fax" msgstr "" -#: ../settings/security/third-party.rst:71 -msgid "By default this setting is not active (set to ``no``)." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.fax}``" msgstr "" -#: ../settings/security/third-party.rst:0 -msgid "" -"Screenshot showing sample notification mail after initial\n" -"third-party linking" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Firstname" msgstr "" -#: ../settings/security/third-party.rst:85 -msgid "" -"This notification is only sent if the account in question already exists. If " -"the login via the third-party also creates the missing account, the " -"notification will be skipped." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.firstname}``" msgstr "" -#: ../settings/security/third-party.rst:89 -msgid "This means it only affects:" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Lastname" msgstr "" -#: ../settings/security/third-party.rst:91 -msgid "manual account linking within the third-party page of the users profile" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.lastname}``" msgstr "" -#: ../settings/security/third-party.rst:92 -msgid "" -"logging into an existing local account by utilizing the *automatic account " -"link on initial logon* functionality" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Login" msgstr "" -#: ../settings/security/third-party.rst:None -msgid "" -"Screenshot showing the \"automatic account linking notification\"\n" -"setting" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.login}``" msgstr "" -#: ../settings/security/third-party.rst:100 -msgid "No User Creation on Logon" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Mobile" msgstr "" -#: ../settings/security/third-party.rst:102 -msgid "" -"By default, Zammad will create a new user account if the user logs in via a " -"third-party application and the account doesn't exist yet." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.mobile}``" msgstr "" -#: ../settings/security/third-party.rst:105 -msgid "" -"If you want to prevent Zammad from creating new accounts on logon, you can " -"disable this feature by setting ``No user creation on logon`` to ``yes``." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Note" msgstr "" -#: ../settings/security/third-party.rst:None -#, fuzzy -msgid "Screenshot showing the \"no user creation on logon\" setting" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.note}``" msgstr "" -"Captura de pantalla que muestra la configuración básica de una cuenta de " -"correo electrónico entrante" -#: ../settings/security/third-party/facebook.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via Facebook To do " -"so, you need to follow these steps:" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Phone" msgstr "" -#: ../settings/security/third-party/facebook.rst:9 -msgid "Register Facebook App" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.phone}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:11 -msgid "" -"Visit [https://developers.facebook.com/apps/] and click on \"Add a new App\"" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > VIP" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "initial page" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.vip}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:17 -msgid "After that enter the app settings" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Web" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "Create App" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.web}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:22 -msgid "Navigate to \"Settings\" and fill in this infromation" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "App Settings" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_at}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:27 -msgid "Navigate to app review and Check \"Make [appname] public?\"" +#: ../misc/variables/article.rst:1 +msgid "Article > Visibility" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "App Review" +#: ../misc/variables/article.rst:1 +msgid "``#{article.internal}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:35 -msgid "Configure Zammad as Facebook App" +#: ../misc/variables/article.rst:1 +msgid "``false`` or ``true`` (false if not internal)" msgstr "" -#: ../settings/security/third-party/facebook.rst:37 -msgid "" -"Navigate to \"Admin -> Security -> Third Party Applications\" and enter the " -"App ID and the App Secret. You can find this Key in the Dashbard of your " -"Facebok app." +#: ../misc/variables/article.rst:1 +msgid "Article Text as HTML (not referenced)" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "Zammad Configuration" +#: ../misc/variables/article.rst:1 +msgid "``#{article.body_as_html}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:44 -#: ../settings/security/third-party/github.rst:43 -#: ../settings/security/third-party/gitlab.rst:46 -msgid "" -"Now you can link accounts via \"Avatar -> Profile -> Link Accounts\" or " -"login via Zammad login page." +#: ../misc/variables/article.rst:1 +msgid "``Test`` with formatting" msgstr "" -#: ../settings/security/third-party/github.rst:2 -#: ../system/integrations/github.rst:2 -msgid "GitHub" +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "Ticket > Article#" msgstr "" -#: ../settings/security/third-party/github.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via GitHub. To " -"activate the quick login you need to enable OAuth for GitHub." +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "``#{ticket.article_count}``" msgstr "" -#: ../settings/security/third-party/github.rst:8 -msgid "Register GitHub App" +#: ../misc/variables/article.rst:1 +msgid "``1`` number of ticket articles" msgstr "" -#: ../settings/security/third-party/github.rst:10 -msgid "" -"Visit https://www.github.com/settings/applications/new and enter the app " -"settings. As callback URL enter \"https://zammad_host/auth/github/callback\" " -"where zammad_host has to be replaced with your Zammad FQDN" +#: ../misc/variables/config.rst:2 +msgid "Config" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "Register OAuth app on www.github.com" +#: ../misc/variables/config.rst:6 +msgid "" +"Below you'll find config related variables. These hold useful configuration " +"information that you can use within e.g. triggers to show necessary " +"information to your customer." msgstr "" -#: ../settings/security/third-party/github.rst:19 -msgid "Configure Zammad as GitHub App" +#: ../misc/variables/config.rst:11 +msgid "Config Variables" msgstr "" -#: ../settings/security/third-party/github.rst:21 -msgid "" -"Enter the \"APP ID\" and the \"APP SECRET\" from the GitHub OAUTH " -"Applications Dashboard" +#: ../misc/variables/config.rst:1 +msgid "Config > Fully Qualified Domain Name" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub config in Zammad admin interface" +#: ../misc/variables/config.rst:1 +msgid "``#{config.fqdn}``" msgstr "" -#: ../settings/security/third-party/github.rst:28 -msgid "" -"After you configured the GitHub credentials and activated the login method, " -"you should see a new icon on the login page." +#: ../misc/variables/config.rst:1 +msgid "``zammad.example.com``" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub logo on login page" +#: ../misc/variables/config.rst:1 +msgid "Config > HTTP type" msgstr "" -#: ../settings/security/third-party/github.rst:34 -msgid "" -"If you click on the icon you will be redirected to GitHub and see something " -"similar to this:" +#: ../misc/variables/config.rst:1 +msgid "``#{config.http_type}``" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub oauth page" +#: ../misc/variables/config.rst:1 +msgid "``https`` or ``http``" msgstr "" -#: ../settings/security/third-party/github.rst:40 -#: ../settings/security/third-party/gitlab.rst:42 -msgid "" -"When you grant the access you will be redirected to your Zammad instance and " -"logged in as a customer." +#: ../misc/variables/config.rst:1 +msgid "Config > Organization" msgstr "" -#: ../settings/security/third-party/gitlab.rst:2 -msgid "Gitlab" +#: ../misc/variables/config.rst:1 +msgid "``#{config.organization}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:4 +#: ../misc/variables/config.rst:1 msgid "" -"It is possible to create a quick login for your helpdesk via Gitlab. To " -"activate the quick login you need to enable OAuth for Gitlab." +"``Zammad GmbH`` value set in `Branding `_" msgstr "" -#: ../settings/security/third-party/gitlab.rst:8 -msgid "Register Gitlab App" +#: ../misc/variables/config.rst:1 +msgid "Config > Product Name" msgstr "" -#: ../settings/security/third-party/gitlab.rst:10 -msgid "To register an app in Gitlab open your profile and select applications." +#: ../misc/variables/config.rst:1 +msgid "``#{config.product_name}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:12 +#: ../misc/variables/config.rst:1 msgid "" -"As callback URL enter \"https://zammad-fqdn/auth/gitlab/callback\" where " -"zammad-fqdn has to be replaced with your Zammad FQDN" +"``Helpdesk`` value set in `Branding `_" msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Register OAuth app on gitlab instance" +#: ../misc/variables/config.rst:1 +msgid "Config > SystemID" msgstr "" -#: ../settings/security/third-party/gitlab.rst:18 -msgid "Just select *read_user* under scopes as in the screenshot and save it." +#: ../misc/variables/config.rst:1 +msgid "``#{config.system_id}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:21 -msgid "Configure Zammad as Gitlab App" +#: ../misc/variables/config.rst:1 +msgid "``31`` (value between 1 and 99)" msgstr "" -#: ../settings/security/third-party/gitlab.rst:23 -msgid "" -"Enter the \"APP ID\" and the \"APP SECRET\" from the Gitlab OAUTH " -"Applications Dashboard and your Gitlab-URL in the \"SITE\" field." +#: ../misc/variables/config.rst:1 +msgid "Config > Ticket Hook" msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab config in Zammad admin interface" +#: ../misc/variables/config.rst:1 +msgid "``#{config.ticket_hook}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:30 -msgid "" -"After you configured the Gitlab credentials and activated the login method, " -"you should see a new icon on the login page." +#: ../misc/variables/config.rst:1 +msgid "``Ticket#``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab logo on login page" +#: ../misc/variables/current-user.rst:2 +msgid "Current User" msgstr "" -#: ../settings/security/third-party/gitlab.rst:36 +#: ../misc/variables/current-user.rst:6 msgid "" -"If you click on the icon you will be redirected to Gitlab and see something " -"similar to this:" +"Current user variables always return values of the current user that caused " +"e.g. a trigger to run." msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab oauth page" +#: ../misc/variables/current-user.rst:8 +msgid "" +"Due to the above fact, these variables are often not (yet) set or available " +"for usage." msgstr "" -#: ../settings/security/third-party/google.rst:4 +#: ../misc/variables/current-user.rst:10 msgid "" -"With some easy and fast steps, you can enable Zammad to authenticate your " -"users via Google." +"In situations where e.g. schedulers or triggers run, this most likely is " +"nothing you want to use." msgstr "" -#: ../settings/security/third-party/google.rst:8 -msgid "Register a Google App" +#: ../misc/variables/current-user.rst:13 +msgid "Current User Variables" msgstr "" -#: ../settings/security/third-party/google.rst:10 -msgid "" -"First of all, we need to create a new project - you can skip this step if " -"you already have one." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Address" msgstr "" -#: ../settings/security/third-party/google.rst:15 -msgid "" -"Use this link to create a new project: https://console.cloud.google.com/" -"projectcreate" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.address}``" msgstr "" -#: ../settings/security/third-party/google.rst:18 -msgid "" -"Now expand the menu, expand \"APIs & Services\" and select \"Credentials\". " -"Go to the tab \"OAuth consent screen\" first and ensure to fill in the " -"requested information - without doing so you can't create credentials!" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set" msgstr "" -#: ../settings/security/third-party/google.rst:None -msgid "Creating a consent screen" +#: ../misc/variables/current-user.rst:1 +#, fuzzy +msgid "Current User > Avatar" +msgstr "Ticket > Organización > Nota" + +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/google.rst:25 -msgid "" -"After filling in and saving the consent screen information, you can go to " -"the \"Credentials\" tab and create new \"OAuth client ID\"-Credentials." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "avatar picture with width and height in pixel (e.g. 60,60)" msgstr "" -#: ../settings/security/third-party/google.rst:28 -msgid "" -"Fill in the necessary information as follows and replace ``zammad_host`` " -"with your FQDN:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created at" msgstr "" -#: ../settings/security/third-party/google.rst:31 -msgid "**Application type** ``[x] Web application``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_at}``" msgstr "" -#: ../settings/security/third-party/google.rst:34 -msgid "**Authorized JavaScript origins** ``https://zammad_host/``" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC``" msgstr "" -#: ../settings/security/third-party/google.rst:37 -msgid "" -"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" -"callback``" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Address" msgstr "" -#: ../settings/security/third-party/google.rst:None -msgid "Adding a new OAuth client ID" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.address}``" msgstr "" -#: ../settings/security/third-party/google.rst:43 -msgid "" -"After creating the credentials, go to your Zammad installation and navigate " -"to \"Admin > Security > Third Party Applications\" > Google. Enter your " -"Client ID and Client secret here." -msgstr "" +#: ../misc/variables/current-user.rst:1 +#, fuzzy +msgid "Current User > Created by > Avatar" +msgstr "Ticket > Creado por > Apellido" -#: ../settings/security/third-party/google.rst:None -msgid "Zammad" -msgstr "" +#: ../misc/variables/current-user.rst:1 +#, fuzzy +msgid "``#{user.created_by.avatar(60,60)}``" +msgstr "``#{ticket.created_by.lastname}``" -#: ../settings/security/third-party/google.rst:50 -msgid "After submitting, the login via Google can be used." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Department" msgstr "" -#: ../settings/security/third-party/microsoft.rst:2 -msgid "Microsoft" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.department}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:4 -msgid "" -"Zammad's Microsoft connection allows your users with Microsoft accounts to " -"login. This works for Azure users as well and can be an alternative to :doc:" -"`/system/integrations/ldap/index`." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Sales`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:10 -msgid "" -"This documentation part does not cover our :doc:`📧 Microsoft 365 email " -"channel `." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Email" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screenshot showing Microsoft login button on Zammad login screen." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.email}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:30 -#: ../settings/security/third-party/microsoft.rst:53 -msgid "Supported account types:" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``jdoe@customer.tld``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:22 -msgid "" -"Please note that Zammad only supports these account types (App dependent):" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Fax" msgstr "" -#: ../settings/security/third-party/microsoft.rst:35 -msgid "Avatars of signing in users:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.fax}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:33 -msgid "" -"Zammad currently ignores user avatars. If the user is registered with e.g. " -"Gravatar, Zammad will fetch the avatar from there if enabled. See :doc:" -"`Zammad Image Service ` for more." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``004930123464789`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:38 -msgid "Step 1 - Register a Microsoft App for Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Firstname" msgstr "" -#: ../settings/security/third-party/microsoft.rst:40 -msgid "" -"Login to the `Microsoft Azure Portal `_ and " -"navigate to App registrations to create a new app. Provide the requested " -"information as follows and register your app." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.firstname}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:46 -msgid "Name:" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``John`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:45 -msgid "" -"Any meaningful name fitting, this name will be displayed to users trying to " -"authenticate with this app." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Lastname" msgstr "" -#: ../settings/security/third-party/microsoft.rst:49 -msgid "Choose one of the above mentioned account types (see Limitations)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.lastname}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:51 -msgid "" -"The correct account type depends on your use case. If you want to use the " -"authentication internal only, choose the first option. If you're unsure, use " -"the \"Help me choose...\" link." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Login" msgstr "" -#: ../settings/security/third-party/microsoft.rst:58 -msgid "Redirect URI (optional):" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.login}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:56 -msgid "" -"Select web and provide your callback URL. The callback URL looks like this: " -"``https://zammad.domain.tld/auth/microsoft_office365/callback``" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Mobile" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to register a Microsoft app" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.mobile}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "Within **API permissions** add the following permissions:" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``0049176123456789`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:69 -msgid "``User.Read``" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Note" msgstr "" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "Contacts" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.note}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "``Contacts.Read``" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Some note to this user`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:73 -msgid "" -"You can find these permissions within *Microsoft Graph → Delegated " -"permissions*." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Phone" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to add required API permissions" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.phone}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:80 -msgid "" -"Within **Certificates & secrets** create a new client secret. Note down the " -"returned secret **value** for later. **Do not** use the secret ID!" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``004930123456789`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to create a new app secret" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > VIP" msgstr "" -#: ../settings/security/third-party/microsoft.rst:88 -msgid "" -"From **Overview** copy your apps *Application (client) ID*. If you're using " -"a single tenant app, please also copy *Directory (tenant) ID*. You now have " -"all required information for Zammad." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.vip}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to retreive application client and tenant IDs" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Web" msgstr "" -#: ../settings/security/third-party/microsoft.rst:98 -msgid "Step 2 - Add App Credentials to Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.web}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:100 -msgid "" -"Navigate to Security > Third-party Applications (Tab) within Zammad's admin " -"settings. Scroll down to the section *Authentication via Microsoft* and fill " -"in the required information." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``https://zammad.org`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:105 -msgid "App ID:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Department" msgstr "" -#: ../settings/security/third-party/microsoft.rst:105 -msgid "This is your *Application (client) ID*." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.department}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:108 -msgid "App secret:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Email" msgstr "" -#: ../settings/security/third-party/microsoft.rst:108 -msgid "This is your *client secret* (value)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.email}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:113 -msgid "App Tenant ID:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Fax" msgstr "" -#: ../settings/security/third-party/microsoft.rst:111 -msgid "" -"**optional** only required for apps that use account type *Accounts in this " -"organizational directory only (Default Directory only - Single tenant).*" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.fax}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:115 -msgid "" -"Apply your settings by pressing submit and activate *Authentication via " -"Microsoft*." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Firstname" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "" -"Screencast showing how to add app credentials and activating the\n" -"authentication method" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.firstname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:2 -msgid "SAML" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Lastname" msgstr "" -#: ../settings/security/third-party/saml.rst:4 -msgid "" -"Connect your SAML (Security Assertion Markup Language) identity provider as " -"a single sign-on (SSO) method." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.lastname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:7 -msgid "" -"SAML is an open standard for SSO authentication (among other things). Sign-" -"ins are shared across multiple **service providers** and managed by a " -"central **identity provider** (IdP)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Login" msgstr "" -#: ../settings/security/third-party/saml.rst:11 -msgid "" -"In this case, the service provider is Zammad, and the IdP is a software " -"service that you either host or subscribe to (*e.g.,* `Keycloak `_, `Redhat SSO Server `_, `ADFS `_, or `Okta `_)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.login}``" msgstr "" -#: ../settings/security/third-party/saml.rst:18 -msgid "" -"This guide assumes you are already using SAML within your organization (i." -"e., that your IdP is fully set up)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Mobile" msgstr "" -#: ../settings/security/third-party/saml.rst:21 -msgid "" -"Please note: Our instructions are based on connecting Zammad with Keycloak." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.mobile}``" msgstr "" -#: ../settings/security/third-party/saml.rst:25 -msgid "Step 1: Configure Your IdP" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Note" msgstr "" -#: ../settings/security/third-party/saml.rst:28 -msgid "Add Zammad as a Client/App" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.note}``" msgstr "" -#: ../settings/security/third-party/saml.rst:30 -msgid "" -"Import Zammad into your IdP using the XML configuration found at ``https://" -"your.zammad.domain/auth/saml/metadata``." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Domain based assignment" msgstr "" -#: ../settings/security/third-party/saml.rst:33 -msgid "" -"If your IdP doesn't support XML import, you will have to configure Zammad as " -"a new client/app manually using the above XML metadata file for reference." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.domain_assignment}``" msgstr "" -#: ../settings/security/third-party/saml.rst:36 -msgid "For instance, when you see this tag:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Domain" msgstr "" -#: ../settings/security/third-party/saml.rst:42 -msgid "" -"Set the **Assertion Consumer Service Binding URL** (sometimes also listed as " -"**Valid Redirect URIs**) to ``http://your.zammad.domain/auth/saml/callback``." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.domain}``" msgstr "" -#: ../settings/security/third-party/saml.rst:47 -msgid "Set Up User Attribute Mapping" +#: ../misc/variables/current-user.rst:1 +#, fuzzy +msgid "``zammad.com`` or empty if not set" +msgstr "``Federico`` o vació si no esta configurado" + +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Name" msgstr "" -#: ../settings/security/third-party/saml.rst:49 -msgid "" -"Zammad requests the following user attributes (or “properties”) from the IdP:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.name}``" msgstr "" -#: ../settings/security/third-party/saml.rst:51 -msgid "Email address (``email``)" +#: ../misc/variables/current-user.rst:1 +msgid "``Zammad GmbH``" msgstr "" -#: ../settings/security/third-party/saml.rst:52 -msgid "Full name (``name``)" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Note" msgstr "" -#: ../settings/security/third-party/saml.rst:53 -msgid "Given name (``first_name``)" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.note}``" msgstr "" -#: ../settings/security/third-party/saml.rst:54 -msgid "Family name (``last_name``)" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``A note to the organization of the user`` or empty if not set" msgstr "" -#: ../settings/security/third-party/saml.rst:56 -msgid "" -"You may need to set up “mappers” (or “mappings”) to tell your IdP how user " -"attributes in SAML correspond to those in Zammad. For a more detailed " -"breakdown, refer to the XML metadata file referenced in the previous section." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Shared organization" msgstr "" -#: ../settings/security/third-party/saml.rst:62 -msgid "Per-IdP Instructions" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.shared}``" msgstr "" -#: ../settings/security/third-party/saml.rst:102 -msgid "Keycloak" -msgstr "" +#: ../misc/variables/current-user.rst:1 +#, fuzzy +msgid "Current User > Organization > VIP" +msgstr "Ticket > Organización > Nota" -#: ../settings/security/third-party/saml.rst:65 -msgid "" -"**To add Zammad as a client,** save the XML configuration to disk (``https://" -"your.zammad.domain/auth/saml/metadata``) and use **Clients > Clients list > " -"Import client** in the Keycloak admin panel." -msgstr "" +#: ../misc/variables/current-user.rst:1 +#, fuzzy +msgid "``#{user.organization.vip}``" +msgstr "``#{ticket.organization.domain}``" -#: ../settings/security/third-party/saml.rst:70 -msgid "" -"To help Zammad **match its own user accounts to Keycloak users**, create a " -"user attribute (or “property”) mapper. In **Clients list**, click on your " -"newly created Client ID, choose the tab **Client scopes** and click on the " -"link which refers to your Zammad instance. Choose **Add mapper > By " -"configuration > User Property** and create a mapper with the following " -"entries:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Phone" msgstr "" -#: ../settings/security/third-party/saml.rst:78 -msgid "**Name**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.phone}``" msgstr "" -#: ../settings/security/third-party/saml.rst:80 -msgid "**Mapper Type**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated at" msgstr "" -#: ../settings/security/third-party/saml.rst:81 -msgid "``User Property``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_at}``" msgstr "" -#: ../settings/security/third-party/saml.rst:82 -msgid "**Property**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Address" msgstr "" -#: ../settings/security/third-party/saml.rst:83 -msgid "``emailAddress``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.address}``" msgstr "" -#: ../settings/security/third-party/saml.rst:84 -msgid "**SAML Attribute Name**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Avatar" msgstr "" -#: ../settings/security/third-party/saml.rst:86 -msgid "**SAML Attribute NameFormat**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/saml.rst:87 -msgid "``basic``" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Department" msgstr "" -#: ../settings/security/third-party/saml.rst:89 -msgid "" -"In the example above, we're telling Zammad that whenever it receives a SAML " -"login request, it should take the ``email`` property from Keycloak, look for " -"a Zammad user with the same ``email`` attribute, and create a new session " -"for that user." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.department}``" msgstr "" -#: ../settings/security/third-party/saml.rst:95 -msgid "" -"If your Keycloak users' email addresses are stored on another property (*e." -"g.,* ``username``), adjust accordingly." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Email" msgstr "" -#: ../settings/security/third-party/saml.rst:98 -msgid "" -"Back in **Settings**, enter the Client ID (``https://your.zammad.domain/auth/" -"saml/metadata``) in the field **Master SAML Processing URL**." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.email}``" msgstr "" -#: ../settings/security/third-party/saml.rst:101 -msgid "You also need to enable **Sign assertions**." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Fax" msgstr "" -#: ../settings/security/third-party/saml.rst:105 -msgid "Step 2: Configure Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.fax}``" msgstr "" -#: ../settings/security/third-party/saml.rst:107 -msgid "" -"Enable SAML and enter your IdP's details in the Admin Panel under **Settings " -"> Security > Third Party Applications > Authentication via SAML**:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Firstname" msgstr "" -#: ../settings/security/third-party/saml.rst:None -msgid "Example configuration of SAML part 1" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.firstname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:119 -msgid "Display name" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Lastname" msgstr "" -#: ../settings/security/third-party/saml.rst:116 -msgid "" -"Allows you to define a custom button name for SAML. This helps your users to " -"understand better what the button on the login page does." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.lastname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:119 -msgid "Defaults to ``SAML``." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Login" msgstr "" -#: ../settings/security/third-party/saml.rst:123 -msgid "IDP SSO target URL" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.login}``" msgstr "" -#: ../settings/security/third-party/saml.rst:122 -msgid "" -"This is the target URL Zammad shall redirect to when the user presses the " -"SAML button. For Keycloak, this needs to look like https://your.domain/" -"realms/your-realm/protocol/saml" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Mobile" msgstr "" -#: ../settings/security/third-party/saml.rst:127 -msgid "IDP single logout target URL" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.mobile}``" msgstr "" -#: ../settings/security/third-party/saml.rst:126 -msgid "" -"This is the URL to which the single logout request and response should be " -"sent." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Note" msgstr "" -#: ../settings/security/third-party/saml.rst:131 -#, fuzzy -msgid "IDP certificate" -msgstr "Verificación de correo electrónico" - -#: ../settings/security/third-party/saml.rst:130 -msgid "" -"The public certificate of your IDP for Zammad to verify during the callback " -"phase." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.note}``" msgstr "" -#: ../settings/security/third-party/saml.rst:145 -msgid "IDP certificate fingerprint" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Phone" msgstr "" -#: ../settings/security/third-party/saml.rst:134 -msgid "" -"The fingerprint of your IDPs public certificate to verify during callback " -"phase." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.phone}``" msgstr "" -#: ../settings/security/third-party/saml.rst:137 -msgid "🔏 **For the IdP certificate / certificate fingerprint:**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > VIP" msgstr "" -#: ../settings/security/third-party/saml.rst:139 -msgid "" -"Provide **only one or the other**—do not provide both! (Between the two, we " -"recommend the signing certificate itself: fingerprints use SHA-1, which `has " -"been broken for a while now `_.)" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.vip}``" msgstr "" -#: ../settings/security/third-party/saml.rst:144 -msgid "" -"**Keycloak users:** Find your certificate in the Keycloak admin panel under " -"**Realm Settings > Keys > Algorithm: RS256 > Certificate**." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``false`` or ``true``" msgstr "" -#: ../settings/security/third-party/saml.rst:151 -msgid "Name identifier format" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Web" msgstr "" -#: ../settings/security/third-party/saml.rst:148 -msgid "" -"This is the unique identifiers field type. Usually it should be ``urn:oasis:" -"names:tc:SAML:1.1:nameid-format:emailAddress``." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.web}``" msgstr "" -#: ../settings/security/third-party/saml.rst:151 -msgid "Zammad **expects an email address as unique identifier**!" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > VIP" msgstr "" -#: ../settings/security/third-party/saml.rst:155 -msgid "UID attribute name" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.vip}``" msgstr "" -#: ../settings/security/third-party/saml.rst:154 -msgid "" -"Here you can define an attribute that uniquely identifies the user. If " -"unset, the name identifier returned by the IDP is used." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Web" msgstr "" -#: ../settings/security/third-party/saml.rst:None -msgid "Example configuration of SAML part 2" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.web}``" msgstr "" -#: ../settings/security/third-party/saml.rst:163 +#: ../misc/variables/ticket.rst:6 msgid "" -"Decide if the certificate for the connection to the IdP service has to be " -"verified or not (default: ``yes``)." -msgstr "" - -#: ../settings/security/third-party/saml.rst:169 -msgid "Signing & Encrypting" +"Below you can find all available ticket-based variables within Zammad. These " +"can be called via triggers for example. If you're unsure if Zammad does " +"support variables at the point you're at, you can try to type ``::`` to " +"check." msgstr "" -#: ../settings/security/third-party/saml.rst:169 -msgid "" -"Define if you want to sign, encrypt, do both or nothing for the requests." +#: ../misc/variables/ticket.rst:12 +msgid "Ticket Variables" msgstr "" -#: ../settings/security/third-party/saml.rst:179 -msgid "Certificate (PEM)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Accounted Time" msgstr "" -#: ../settings/security/third-party/saml.rst:172 -msgid "" -"Paste the public certificate of your Zammad SAML client, if you want to " -"encrypt the requests." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.time_unit}``" msgstr "" -#: ../settings/security/third-party/saml.rst:175 -#, fuzzy -msgid "Make sure the certificate is:" -msgstr "Verificación de correo electrónico" - -#: ../settings/security/third-party/saml.rst:177 -msgid "already valid and not yet expired" +#: ../misc/variables/ticket.rst:1 +msgid "``1``, ``2.75`` or empty response" msgstr "" -#: ../settings/security/third-party/saml.rst:178 -#, fuzzy -msgid "no CA certificate" -msgstr "Verificación de correo electrónico" - -#: ../settings/security/third-party/saml.rst:179 -msgid "valid for signing and encrypting" +#: ../misc/variables/ticket.rst:1 +msgid "``3``, any number of articles existing in the ticket right now" msgstr "" +"``3``, cualquier número de artículos existiendo en el ticket ahora mismo" -#: ../settings/security/third-party/saml.rst:185 -msgid "Private key (PEM)" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Closing time" +msgstr "Ticket > Tiempo de cierre" -#: ../settings/security/third-party/saml.rst:182 -msgid "" -"Paste the private key of your Zammad SAML client here, if you want to sign " -"the requests." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.close_at}``" +msgstr "``#{ticket.close_at}``" -#: ../settings/security/third-party/saml.rst:185 -msgid "Make sure the key is an RSA key with a length of at least 2048 bits." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "2019-10-07 17:25:00 UTC" +msgstr "2019-10-07 17:25:00 UTC" -#: ../settings/security/third-party/saml.rst:188 -msgid "Private key secret" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created at" +msgstr "Ticket > Creado en" -#: ../settings/security/third-party/saml.rst:188 -msgid "If your private key is secured with a secret, you can provide it here." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_at}``" +msgstr "``#{ticket.created_at}``" -#: ../settings/security/third-party/saml.rst:192 -msgid "Your callback URL" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "2019-10-07 16:25:00 UTC" +msgstr "2019-10-07 16:25:00 UTC" -#: ../settings/security/third-party/saml.rst:191 -msgid "" -"This URL is needed for your IdP configuration so it knows where to redirect " -"to after successful authentication." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Address" +msgstr "Ticket > Creado por > Dirección" -#: ../settings/security/third-party/saml.rst:194 -msgid "" -"After saving your input by clicking on the \"Submit\" button, Zammad " -"verifies the provided keys/certificates (e.g. if they are valid for signing/" -"encrypting and if they aren't expired)." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.address}``" +msgstr "``#{ticket.created_by.address}``" -#: ../settings/security/third-party/saml.rst:199 -msgid "" -"See :ref:`automatic account linking ` for details " -"on how to link existing Zammad accounts to IdP accounts." -msgstr "" +#: ../misc/variables/ticket.rst:1 +#, fuzzy +msgid "Ticket > Created by > Avatar" +msgstr "Ticket > Creado por > Fax" -#: ../settings/security/third-party/saml.rst:205 +#: ../misc/variables/ticket.rst:1 #, fuzzy -msgid "Automatic account linking doesn't work" -msgstr "Notificación automática de vinculación de cuentas" - -#: ../settings/security/third-party/saml.rst:206 -msgid "" -"Have you double-checked your IdP's user attribute mapping configuration?" -msgstr "" - -#: ../settings/security/third-party/twitter.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via Twitter. To do " -"so, you need to follow these steps:" -msgstr "" - -#: ../settings/security/third-party/twitter.rst:8 -msgid "Register Twitter App" -msgstr "" - -#: ../settings/security/third-party/twitter.rst:10 -msgid "Go to https://dev.twitter.com/apps and login with your account." -msgstr "" - -#: ../settings/security/third-party/twitter.rst:15 -msgid "Click on \"Create App\"" -msgstr "" - -#: ../settings/security/third-party/twitter.rst:None -msgid "new app page" -msgstr "" - -#: ../settings/security/third-party/twitter.rst:20 -msgid "" -"Enter app settings. As \"Callback URL\" you need to enter ``https://" -"zammad_host/api/v1/external_credentials/twitter/callback``. You need to " -"replace ``zammad_host`` with the domain of your Zammad system." -msgstr "" - -#: ../settings/security/third-party/twitter.rst:24 -msgid "" -"After the app has been created, update the application icon and organization " -"attributes." -msgstr "" - -#: ../settings/security/third-party/twitter.rst:None -msgid "set permissions to receive and send direct messages" -msgstr "" - -#: ../settings/security/third-party/twitter.rst:30 -msgid "" -"Next we need to set ``read, write and access direct messages`` permissions " -"for the app." -msgstr "" - -#: ../settings/security/third-party/twitter.rst:None -msgid "click on Keys & Access Token, note them" -msgstr "" - -#: ../settings/security/third-party/twitter.rst:36 -msgid "" -"Go to \"Keys and Access Token\" tab and note the \"Consumer Key\" and " -"\"Consumer Secret\"." -msgstr "" - -#: ../settings/security/third-party/twitter.rst:40 -msgid "Configure Zammad as Twitter App" -msgstr "" - -#: ../settings/security/third-party/twitter.rst:42 -msgid "" -"Go to \"Admin > Security > Twitter > Third Party Applications > Twitter\" " -"Section." -msgstr "" - -#: ../settings/security/third-party/twitter.rst:None -msgid "Admin > Security > Third Party Applications" -msgstr "" - -#: ../settings/security/third-party/twitter.rst:48 -msgid "" -"Fill in the \"Twitter Key\" and the \"Twitter Secret\" and click the " -"\"Submit\" button." -msgstr "" - -#: ../settings/security/third-party/twitter.rst:51 -msgid "" -"Now you can link accounts via \"Avatar > Profile > Link Accounts\" or login " -"via Zammad login page." -msgstr "" - -#: ../settings/security/two-factor.rst:11 -msgid "Two-factor Authentication Methods" -msgstr "" - -#: ../settings/security/two-factor.rst:2 -msgid "Two-Factor Authentication" -msgstr "" - -#: ../settings/security/two-factor.rst:4 -msgid "" -"Two-factor authentication (2FA) enhances the security of Zammad accounts by " -"adding an extra layer of verification beyond a password. It requires users " -"to provide two different types of authentication factors, typically " -"something they know (like a password) and something they possess (like a " -"mobile device or a security token), to ensure that only authorized " -"individuals can access the account." -msgstr "" - -#: ../settings/security/two-factor.rst:19 -msgid "Enable Recovery Codes" -msgstr "" - -#: ../settings/security/two-factor.rst:21 -msgid "" -"Recovery codes are one-time use security codes that can be used by the user " -"if they lose access to their other two-factor authentication methods. They " -"cannot be used on their own, they can only be activated if at least one two-" -"factor authentication method is enabled." -msgstr "" - -#: ../settings/security/two-factor.rst:None -msgid "Enable Recovery Codes Setting" -msgstr "" - -#: ../settings/security/two-factor.rst:30 -msgid "" -"Recovery codes can only be used as a backup method. If enabled, they will be " -"automatically generated for the user once they set up their initial two-" -"factor authentication method." -msgstr "" - -#: ../settings/security/two-factor.rst:34 -msgid "" -"The user will be asked to print out or save the generated recovery codes in " -"a safe place. Once used, a recovery code cannot be reused." -msgstr "" - -#: ../settings/security/two-factor.rst:37 -msgid "" -"Users will also have an option to regenerate their recovery codes at any " -"time, which invalidates already existing recovery codes and provides them " -"with a list of fresh codes." -msgstr "" - -#: ../settings/security/two-factor.rst:41 -msgid "" -"After you enable this setting, when the user completes a setup of their " -"initial two-factor authentication method, they will be presented with a list " -"of recovery codes and instructed to save them for later use." -msgstr "" - -#: ../settings/security/two-factor.rst:None -msgid "Recovery Codes Generation Modal Dialog" -msgstr "" - -#: ../settings/security/two-factor.rst:50 -msgid "Enforce the Set Up of the Two-Factor Authentication" -msgstr "" - -#: ../settings/security/two-factor.rst:52 -msgid "" -"In case you wish to require your users to set up at least one two-factor " -"authentication method for their account, you can do this by selecting " -"specific user roles the requirement applies to in **Enforced for user " -"roles** setting. Of course you must have at least one two-factor " -"authentication method enabled for this setting to take effect." -msgstr "" - -#: ../settings/security/two-factor.rst:None -msgid "Enforced for User Roles Setting" -msgstr "" +msgid "``#{ticket.created_by.avatar(60,60)}``" +msgstr "``#{ticket.created_by.lastname}``" -#: ../settings/security/two-factor.rst:62 -msgid "" -"After you change this setting, if the user has one of the selected roles on " -"their account, they will be forced to set up the two-factor authentication " -"upon next sign in or application reload." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Department" +msgstr "Ticket > Creado por > Departamento" -#: ../settings/security/two-factor.rst:66 -msgid "" -"A modal dialog with instructions will be shown, and they will not be able to " -"do any work before they set up at least one two-factor method." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.department}``" +msgstr "``#{ticket.created_by.department}``" -#: ../settings/security/two-factor.rst:None -msgid "Modal Dialog for Enforcing Two-Factor Authentication Set Up" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Email" +msgstr "Ticket > Creado por > Correo Electrónico" -#: ../settings/security/two-factor.rst:74 -msgid "Reset Two-Factor Authentication for a Specific User" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.email}``" +msgstr "``#{ticket.created_by.email}``" -#: ../settings/security/two-factor.rst:76 -msgid "" -"In case an user isn't able to login anymore because of an inaccessible " -"second factor, you can reset the user's 2FA method." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Fax" +msgstr "Ticket > Creado por > Fax" -#: ../settings/security/two-factor.rst:79 -msgid "" -"To do this, go to the user management and search for the relevant user. " -"After you found the account, click the button in the action column and " -"select \"Manage Two-Factor Authentication\":" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.fax}``" +msgstr "``#{ticket.created_by.fax}``" -#: ../settings/security/two-factor.rst:None -msgid "Context menu in action column in user management" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Firstname" +msgstr "Ticket > Creado por > Nombre" -#: ../settings/security/two-factor.rst:87 -msgid "" -"After selecting this, you can see a dialog where you can either reset one " -"2FA method or reset all of the user's 2FA methods:" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.firstname}``" +msgstr "``#{ticket.created_by.firstname}``" -#: ../settings/security/two-factor.rst:None -msgid "Dialog for resetting user's 2FA method" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Lastname" +msgstr "Ticket > Creado por > Apellido" -#: ../settings/security/two-factor.rst:94 -msgid "" -"Choose the fitting one, click on the corresponding \"Remove ...\" button and " -"confirm your action. The user now has to setup a new 2FA method, depending " -"on your 2FA configuration." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.lastname}``" +msgstr "``#{ticket.created_by.lastname}``" -#: ../settings/security/two-factor/authenticator-app.rst:2 -msgid "Authenticator App" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Login" +msgstr "Ticket > Creado por > Acceso" -#: ../settings/security/two-factor/authenticator-app.rst:4 -msgid "" -"The authenticator app method is a type of two-factor authentication that " -"uses a mobile application to generate one-time codes for account " -"verification. After setting up the authenticator app on their device, the " -"user links it to their Zammad account." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.login}``" +msgstr "``#{ticket.created_by.login}``" -#: ../settings/security/two-factor/authenticator-app.rst:12 -msgid "" -"When logging in, the user is prompted to enter a time-sensitive code " -"generated by the app, in addition to their password. This code acts as the " -"second factor of authentication, providing an extra layer of security as it " -"changes periodically and is unique to the user's device." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Mobile" +msgstr "Ticket > Creado por > Celular" -#: ../settings/security/two-factor/authenticator-app.rst:None -msgid "Security Code in Google Authenticator App" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.mobile}``" +msgstr "``#{ticket.created_by.mobile}``" -#: ../settings/security/two-factor/authenticator-app.rst:22 -msgid "" -"The app generates codes based on a shared secret key stored securely on both " -"the user's device and the server, ensuring a synchronized and secure " -"authentication process. The method of generating the codes is sometimes also " -"called TOTP (time-based one-time password)." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Note" +msgstr "Ticket > Creado por > Nota" -#: ../settings/security/two-factor/authenticator-app.rst:28 -msgid "Enabling the Authenticator App Method" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.note}``" +msgstr "``#{ticket.created_by.note}``" -#: ../settings/security/two-factor/authenticator-app.rst:30 -#: ../settings/security/two-factor/security-keys.rst:28 -msgid "To enable the method, just toggle the switch on in the settings." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Phone" +msgstr "Ticket > Creado por > Teléfono" -#: ../settings/security/two-factor/authenticator-app.rst:None -msgid "Authenticator App Switch in Settings" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.phone}``" +msgstr "``#{ticket.created_by.phone}``" -#: ../settings/security/two-factor/authenticator-app.rst:36 -msgid "" -"Now the users will be able to set up this two-factor authentication method " -"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " -"Once they do, on next sign-in with password, they will be asked to provide " -"an additional security code generated by their mobile device." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > VIP" +msgstr "Ticket > Creado por > Persona Muy Importante" -#: ../settings/security/two-factor/security-keys.rst:2 -msgid "Security Keys" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.vip}``" +msgstr "``#{ticket.created_by.vip}``" -#: ../settings/security/two-factor/security-keys.rst:4 -msgid "" -"The security keys method is a type of a two-factor authentication that uses " -"Web Authentication API in the browser for verifying user's identity. The " -"user can register multiple hardware or software security keys with their " -"Zammad account and then they can use it during the sign-in process." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Web" +msgstr "Ticket > Creado por > Web" -#: ../settings/security/two-factor/security-keys.rst:12 -msgid "" -"When logging in, the user is prompted to provide the same security key they " -"registered with their account, in addition to their password. This key acts " -"as the second factor of authentication, providing an extra layer of security." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.web}``" +msgstr "``#{ticket.created_by.web}``" -#: ../settings/security/two-factor/security-keys.rst:None -msgid "Security Key dialog in Safari on macOS" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Address" +msgstr "Ticket > Cliente > Dirección" -#: ../settings/security/two-factor/security-keys.rst:21 -msgid "" -"The type of the key can range from hardware USB sticks to passkeys stored in " -"a device of user's choice. Which type can be used depends on the browser " -"flavor and the platform of the user." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.address}``" +msgstr "``#{ticket.customer.address}``" -#: ../settings/security/two-factor/security-keys.rst:26 -msgid "Enabling the Security Keys Method" -msgstr "" +#: ../misc/variables/ticket.rst:1 +#, fuzzy +msgid "Ticket > Customer > Avatar" +msgstr "Ticket > Cliente> Fax" -#: ../settings/security/two-factor/security-keys.rst:None -msgid "Security Keys Switch in Settings" -msgstr "" +#: ../misc/variables/ticket.rst:1 +#, fuzzy +msgid "``#{ticket.customer.avatar(60,60)}``" +msgstr "``#{ticket.customer.lastname}``" -#: ../settings/security/two-factor/security-keys.rst:34 -msgid "" -"Now the users will be able to set up this two-factor authentication method " -"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " -"Once they do, on next sign-in with password, they will be asked to provide " -"the same security key they registered during the setup." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Department" +msgstr "Ticket > Cliente > Departamento" -#: ../settings/system/system-selfhosted.include.rst:3 -msgid "" -"Below settings are only available to self hosted users. In hosted " -"environments we're handling these settings for you to ensure service " -"stability." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.department}``" +msgstr "``#{ticket.customer.department}``" -#: ../settings/system/base.rst:11 -msgid "Fully Qualified Domain Name" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Email" +msgstr "Ticket > Cliente > Correo Electrónico" -#: ../settings/system/base.rst:7 -msgid "The URL of your Zammad installation." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.email}``" +msgstr "``#{ticket.customer.email}``" -#: ../settings/system/base.rst:9 ../settings/system/base.rst:17 -msgid "This setting is used within :doc:`/system/variables` and notifications." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Fax" +msgstr "Ticket > Cliente> Fax" -#: ../settings/system/system-base.include.rst:1 -msgid "It is automatically set by the *Getting Started wizard*." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.fax}``" +msgstr "``#{ticket.customer.fax}``" -#: ../settings/system/system-base.include.rst:5 -msgid "Changing this setting also changes callback URLs for your channels etc." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Firstname" +msgstr "Ticket > Cliente > Nombre" -#: ../settings/system/system-base.include.rst:6 -msgid "This setting can have negative affects on being able to login." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.firstname}``" +msgstr "``#{ticket.customer.firstname}``" -#: ../settings/system/base.rst:19 -msgid "HTTP type" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Lastname" +msgstr "Ticket > Cliente > Apellido" -#: ../settings/system/base.rst:14 -msgid "" -"The HTTP type tells your installation how your clients connect. This is " -"relevant for authentication and cookie security." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.lastname}``" +msgstr "``#{ticket.customer.lastname}``" -#: ../settings/system/base.rst:31 -msgid "SystemID" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Login" +msgstr "Ticket > Cliente > Acceso" -#: ../settings/system/base.rst:22 -msgid "" -"This ID is being used within your ticket number. In case you're " -"communicating with another ticket system with similar ticket number schemes " -"this ID greatly reduces the risk of false follow ups." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.login}``" +msgstr "``#{ticket.customer.login}``" -#: ../settings/system/base.rst:26 -msgid "" -"The SystemID is randomly selected upon installation of Zammad (``1-99``)." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Mobile" +msgstr "Ticket > Cliente > Celular" -#: ../settings/system/base.rst:30 -msgid "" -"**Do not** change this setting in a productive system! Your Zammad " -"installation may no longer recognize old ticket number based follow ups upon " -"change!" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.mobile}``" +msgstr "``#{ticket.customer.mobile}``" -#: ../settings/system/frontend.rst:2 -msgid "Frontend" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Note" +msgstr "Ticket > Cliente > Nota" -#: ../settings/system/frontend.rst:22 -msgid "Core Workflow Ajax Mode" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.note}``" +msgstr "``#{ticket.customer.note}``" -#: ../settings/system/frontend.rst:6 -msgid "" -"This setting allows administrators to enforce :doc:`/system/core-workflows` " -"to use Ajax-Calls instead of web sockets. You'll usually only need this if " -"you experience serious issues as noted below." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Phone" +msgstr "Ticket > Cliente > Teléfono" -#: ../settings/system/frontend.rst:10 -msgid "**🤓 Possible (technical) reasons**" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.phone}``" +msgstr "``#{ticket.customer.phone}``" -#: ../settings/system/frontend.rst:12 -msgid "" -"In some cases, your network structure (e.g. firewalls, proxies) may " -"disconnect long web socket connections. This leads to select fields staying " -"empty (e.g. owner selection *after* selecting your group) or fields not " -"shown / hidden (e.g. when switching to or from pending states, the \"pending " -"till\" field not showing / hiding)." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > VIP" +msgstr "Ticket > Cliente > Persona Muy Importante" -#: ../settings/system/frontend.rst:18 -msgid "" -"Please keep in mind that the Ajax fallback may cause serious pressure on " -"your application server. If you have the choice stick to web sockets." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.vip}``" +msgstr "``#{ticket.customer.vip}``" -#: ../settings/system/frontend.rst:22 -msgid "Default: ``no`` (inactive)" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Web" +msgstr "Ticket > Cliente > Web" -#: ../settings/system/frontend.rst:53 -msgid "Show calendar weeks in the picker of date/datetime fields" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.web}``" +msgstr "``#{ticket.customer.web}``" -#: ../settings/system/frontend.rst:25 -msgid "" -"With this setting you can instruct Zammad to provide week number display " -"globally for all users. Calendar with week number display are usually used " -"in business sectors and may not be relevant for everyone." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Escalation at" +msgstr "Ticket > Escalación en" -#: ../settings/system/frontend.rst:29 -msgid "" -"This setting affects *all areas* - you'll also see week numbers in the admin " -"panel for e.g. triggers and macros." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.escalation_at}``" +msgstr "``#{ticket.escalation_at}``" -#: ../settings/system/frontend.rst:32 -msgid "Default: ``no`` (not shown)" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable" +msgstr "``2019-10-07 16:25:00 UTC`` o vació si no aplica" -#: ../settings/system/frontend.rst:53 -msgid "Here's the difference:" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > First response" +msgstr "Ticket > Primera respuesta" -#: ../settings/system/frontend.rst:0 -msgid "Screenshot showing Zammad's date picker (in the default way)" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.first_response_at}``" +msgstr "``#{ticket.first_response_at}``" -#: ../settings/system/frontend.rst:41 -msgid "Set to ``no``" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable yet" +msgstr "``2019-10-07 16:25:00 UTC`` o vació si no aplica todavía" -#: ../settings/system/frontend.rst:0 -msgid "" -"Screenshot showing Zammad's date picker with\n" -"week numbers enabled" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Assign Follow-Ups" +msgstr "Ticket > Grupo > Asignar Seguimiento" -#: ../settings/system/frontend.rst:50 -msgid "Set to ``yes``" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_assignment}``" +msgstr "``#{ticket.group.follow_up_assignment}``" -#: ../settings/system/index.rst:4 -msgid "" -"For your overview we split each tab within system settings into its own page:" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Assignment Timeout" +msgstr "Ticket > Grupo > Tiempo de espera de asignación" -#: ../settings/system/index.rst:16 -msgid "Console Based Settings" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.assignment_timeout}``" +msgstr "``#{ticket.group.assignment_timeout}``" -#: ../settings/system/index.rst:18 -msgid "" -"There's some console based settings we didn't put into the UI. However, you " -"may find them helpful - you can find them in our :docs:`hidden settings ` section." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``20`` or empty if not configured" +msgstr "``20`` o vació si no esta configurado" -#: ../settings/system/network.rst:2 -msgid "Network" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Follow-up possible" +msgstr "Ticket > Grupo > Seguimiento posible" -#: ../settings/system/network.rst:8 -msgid "" -"The proxy settings can only be saved after successfully testing the proxy " -"connection." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_possible}``" +msgstr "``#{ticket.group.follow_up_possible}``" -#: ../settings/system/network.rst:15 -msgid "Proxy Address." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``no`` or ``yes``" +msgstr "``no`` o ``si``" -#: ../settings/system/network.rst:12 -msgid "" -"Allows you to provide a proxy server if needed. This is relevant for network " -"communication by Zammad." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Name" +msgstr "Ticket > Grupo > Nombre" -#: ../settings/system/network.rst:15 -msgid "It **does not** affect the update process or Elasticsearch." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.name}``" +msgstr "``#{ticket.group.name}``" -#: ../settings/system/network.rst:18 -msgid "Username for proxy connection." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``Sales``" +msgstr "``Ventas``" -#: ../settings/system/network.rst:18 -msgid "" -"If your proxy server requires authentication, provide the username here." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Note" +msgstr "Ticket > Grupo > Nota" -#: ../settings/system/network.rst:21 -msgid "Password for proxy connection." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.note}``" +msgstr "``#{ticket.group.note}``" -#: ../settings/system/network.rst:21 -msgid "" -"If your proxy server requires authentication, provide the password here." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``Note about this group``" +msgstr "``Nota sobre este grupo``" -#: ../settings/system/network.rst:26 -msgid "No proxy for the following hosts." -msgstr "" +#: ../misc/variables/ticket.rst:1 +#, fuzzy +msgid "Ticket > ID" +msgstr "Ticket > #" -#: ../settings/system/network.rst:24 -msgid "" -"Exception list for hosts you can't or don't want to reach via proxy server." -msgstr "" +#: ../misc/variables/ticket.rst:1 +#, fuzzy +msgid "``#{ticket.id}``" +msgstr "``#{ticket.number}``" -#: ../settings/system/network.rst:27 -msgid "Default: ``localhost,127.0.0.0,::1``" -msgstr "" +#: ../misc/variables/ticket.rst:1 +#, fuzzy +msgid "``17``, ``5281``, ..." +msgstr "``31001``, ``201910731001``, ..." -#: ../settings/system/services.rst:2 -msgid "Services" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact (agent)" +msgstr "Ticket > Ultimo contacto (agente)" -#: ../settings/system/services.rst:10 -msgid "Image Service" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_agent_at}``" +msgstr "``#{ticket.last_contact_agent_at}``" -#: ../settings/system/services.rst:5 -msgid "Defines the backend for user and organization image lookups." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact (customer)" +msgstr "Ticket > Ultimo contacto (cliente)" -#: ../settings/system/services.rst:7 -msgid "Default: ``Zammad Image Service`` (active)" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_customer_at}``" +msgstr "``#{ticket.last_contact_customer_at}``" -#: ../settings/system/services.rst:9 +#: ../misc/variables/ticket.rst:1 +#, fuzzy msgid "" -"Make sure your on premise installation has ``HTTPS`` access to ``images." -"zammad.com``." +"``2019-10-07 16:25:00 UTC`` or empty if not applicable yet (Please note " +"`Ticket last contact behavior Settings `_ for this)" msgstr "" +"``2019-10-07 16:25:00 UTC`` o vació si no es aplicable todavía (Por favor " +"vea `Configuración de ultimo contacto de Ticket `_)" -#: ../settings/system/services.rst:18 -msgid "Geo Calendar Service" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact" +msgstr "Ticket > Ultimo contacto" -#: ../settings/system/services.rst:13 -msgid "" -"Defines the backend for geo calendar lookups. Used for initial calendar " -"setup." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_at}``" +msgstr "``#{ticket.last_contact_at}``" -#: ../settings/system/services.rst:16 -msgid "Default: ``Zammad GeoCalendar Service`` (active)" -msgstr "" +#: ../misc/variables/ticket.rst:1 +#, fuzzy +msgid "Ticket > Number" +msgstr "Ticket > #" -#: ../settings/system/services.include.rst:2 -msgid "" -"Make sure your on premise installation has ``HTTPS`` access to ``geo.zammad." -"com``." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.number}``" +msgstr "``#{ticket.number}``" -#: ../settings/system/services.rst:26 -msgid "Geo IP Service" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``31001``, ``201910731001``, ..." +msgstr "``31001``, ``201910731001``, ..." -#: ../settings/system/services.rst:21 -msgid "" -"Defines the backend for geo IP lookups. Shows also location of an IP address " -"if an IP address is shown." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain based assignment" +msgstr "Ticket > Organización > Asignación basada en dominio" -#: ../settings/system/services.rst:24 -msgid "Default: ``Zammad GeoIP Service`` (active)" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain_assignment}``" +msgstr "``#{ticket.organization.domain_assignment}``" -#: ../settings/system/services.rst:32 -msgid "Geo Location Service" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain" +msgstr "Ticket > Organización > Dominio" -#: ../settings/system/services.rst:29 -msgid "" -"Defines the backend for geo location lookups to store geo locations for " -"addresses." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain}``" +msgstr "``#{ticket.organization.domain}``" -#: ../settings/system/services.rst:32 -msgid "" -"Default: ``OpenStreetMap (ODbL 1.0, http://osm.org/copyright)`` (active)" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``domain.tld`` or empty if not set" +msgstr "``domain.tld`` o vació si no esta configurado" -#: ../settings/system/services.rst:36 -msgid "" -"You can find a detailed privacy information on what we store for how long on " -"our :docs:`Privacy Appendix ` inside of our System " -"Documentation." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Name" +msgstr "Ticket > Organización > Nombre" -#: ../settings/system/storage.rst:2 -msgid "Storage" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.name}``" +msgstr "``#{ticket.organization.name}``" -#: ../settings/system/storage.rst:6 -msgid "" -"Here you can define where Zammad stores attachments for tickets and the " -"knowledge base. By default, we're writing to the ``Database`` - you can " -"switch to ``Filesystem`` or ``Simple Storage (S3)`` at any time. In this " -"case please have a look on the following instructions." +#: ../misc/variables/ticket.rst:1 +msgid "``Zammad GmbH`` or empty if not set" msgstr "" -#: ../settings/system/storage.rst:11 -msgid "" -"If you have a busy Zammad instance, we strongly encourage you to use " -"filesystem storage instead of \"Database\". This will greatly improve system " -"performance (de-crease database load and size)." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Note" +msgstr "Ticket > Organización > Nota" -#: ../settings/system/storage.rst:19 -msgid "Database" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.note}``" +msgstr "``#{ticket.organization.note}``" -#: ../settings/system/storage.rst:17 -msgid "" -"This is the default storage method. The attachments are stored directly in " -"the database. If your Zammad instance grows, we recommend one of the other " -"methods to maintain performance." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Shared organization" +msgstr "Ticket > Organización > Organización compartida" -#: ../settings/system/storage.rst:38 -msgid "Filesystem" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.shared}``" +msgstr "``#{ticket.organization.shared}``" -#: ../settings/system/storage.rst:22 -msgid "" -"This storage method is recommended for all Zammad instances, especially for " -"those with a higher load. If you choose filesystem, your files are written " -"to ``/opt/zammad/storage/``." -msgstr "" +#: ../misc/variables/ticket.rst:1 +#, fuzzy +msgid "Ticket > Organization > VIP" +msgstr "Ticket > Organización > Nota" -#: ../settings/system/storage.rst:26 -msgid "" -"Moving attachments from \"Database\" to \"Filesystem\" can be run during " -"production use. However, you should consider your framework conditions (e.g. " -"bandwidth, system load in production) to define the right moment." -msgstr "" +#: ../misc/variables/ticket.rst:1 +#, fuzzy +msgid "``#{ticket.organization.vip}``" +msgstr "``#{ticket.organization.domain}``" -#: ../settings/system/storage.rst:32 -msgid "**You noticed slow updates of Zammad?**" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Address" +msgstr "Ticket > Dueño > Dirección" -#: ../settings/system/storage.rst:34 -msgid "" -"While Zammad is beeing updated, it enforces a recursive \"change " -"owner\" (chown) for this directory. For instances with many files this can " -"be time consuming. To mitigate that you can move your files and create a " -"symlink in ``/opt/zammad/storage/`` to the new directory. Of course you have " -"to make sure on your own that the permissions are always correct." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.address}``" +msgstr "``#{ticket.owner.address}``" -#: ../settings/system/storage.rst:95 -msgid "Simple Storage (S3)" -msgstr "" +#: ../misc/variables/ticket.rst:1 +#, fuzzy +msgid "Ticket > Owner > Avatar" +msgstr "Ticket > Dueño > Fax" -#: ../settings/system/storage.rst:41 -msgid "" -"To use the Simple Storage (S3), you have to provide some settings, which " -"can't be accessed in the UI (see instructions below)." -msgstr "" +#: ../misc/variables/ticket.rst:1 +#, fuzzy +msgid "``#{ticket.owner.avatar(60,60)}``" +msgstr "``#{ticket.owner.lastname}``" -#: ../settings/system/storage.rst:44 -msgid "" -"⚠️ Please note that the current implementation is in its early stages and can " -"be modified in the future." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Department" +msgstr "Ticket > Dueño > Departamento" -#: ../settings/system/storage.rst:47 -msgid "" -"The prerequisite is to have access to a S3-compatible storage and to have " -"all necessary parameters available (which depends on your storage provider; " -"if in doubt, please ask there for help)." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.department}``" +msgstr "``#{ticket.owner.department}``" -#: ../settings/system/storage.rst:51 -msgid "Steps to configure S3:" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``Support`` or empty if not set" +msgstr "``Soporte`` o vació si no esta configurado" -#: ../settings/system/storage.rst:53 -msgid "" -"Copy ``config/zammad/storage.yml.dist`` to ``config/zammad/storage.yml``" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Email" +msgstr "Ticket > Dueño > Correo electrónico" -#: ../settings/system/storage.rst:54 -msgid "Edit the copied file in one of the following ways:" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.email}``" +msgstr "``#{ticket.owner.email}``" -#: ../settings/system/storage.rst:56 -msgid "" -"Either provide your S3 configuration with one attribute per line like in the " -"upper area of the file" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``agent@company.tld`` or empty if not set" +msgstr "``agent@company.tld`` o vació si no esta configurado" -#: ../settings/system/storage.rst:58 -msgid "" -"Or provide your S3 configuration as an URL (which you can find at the end of " -"the file). Note: you can also provide this URL as environment variable (:" -"docs:`see system documentation `) without using this yml-file." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Fax" +msgstr "Ticket > Dueño > Fax" -#: ../settings/system/storage.rst:62 -msgid "" -"We recommend the deletion of the not used configuration style to avoid " -"inconsistencies." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.fax}``" +msgstr "``#{ticket.owner.fax}``" -#: ../settings/system/storage.rst:65 -msgid "Restart Zammad so the config file / environment variable is loaded" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Firstname" +msgstr "Ticket > Dueño > Nombre" -#: ../settings/system/storage.rst:66 -msgid "" -"Set the \"Storage Method\" in Zammad to ``Simple Storage (S3)`` in Settings " -"> System > Storage and click on \"Submit\". After that, Zammad checks your " -"configuration and the connection to the service and will raise an error " -"message if something is wrong." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.firstname}``" +msgstr "``#{ticket.owner.firstname}``" -#: ../settings/system/storage.rst:72 -msgid "A very simple storage configuration could look like this:" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``Max`` or empty if not set" +msgstr "``Federico`` o vació si no esta configurado" -#: ../settings/system/storage.rst:85 -msgid "" -"Before setting the storage method to ``Simple Storage (S3)`` (step 4), " -"please make sure to have a working setup." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Lastname" +msgstr "Ticket > Dueño > Apellido" + +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.lastname}``" +msgstr "``#{ticket.owner.lastname}``" + +#: ../misc/variables/ticket.rst:1 +msgid "``Mustermann`` or empty if not set" +msgstr "``Caputo`` o vació si no esta configurado" + +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Login" msgstr "" -#: ../settings/system/storage.rst:88 -msgid "" -"You can verify this by running ``rails r 'Rails.logger = Logger.new(STDOUT); " -"pp Store::Provider::S3.ping?'`` in your Zammad directory. If everything is " -"fine, you should see ``true``, else you should see ``false`` and a simple " -"error message." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.login}``" msgstr "" -#: ../settings/system/storage.rst:93 -msgid "" -"If you installed Zammad through a package manager (rather than from source), " -"replace ``rails r`` with ``zammad run rails r`` above. To learn more, see :" -"docs:`Administration via Console `." +#: ../misc/variables/ticket.rst:1 +msgid "``agent``" +msgstr "``agente``" + +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Mobile" msgstr "" -#: ../settings/ticket.rst:4 -msgid "" -"Here you can adjust general ticket settings. Additional ones for the ticket " -"composer interface can be found in the :doc:`/misc/composer`." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.mobile}``" msgstr "" -#: ../settings/ticket.rst:11 -msgid "Ticket Hook (default: ``Ticket#``)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Note" msgstr "" -#: ../settings/ticket.rst:11 -msgid "The identifier for a ticket; *e.g.,* Ticket#, Call#, MyTicket#." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.note}``" msgstr "" -#: ../settings/ticket.rst:38 -msgid "Ticket Hook Position (default: ``right``)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Phone" msgstr "" -#: ../settings/ticket.rst:14 -msgid "" -"With this setting you can decide (if) where to insert the ticket number." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.phone}``" msgstr "" -#: ../settings/ticket.rst:20 -msgid "*Right*" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > VIP" msgstr "" -#: ../settings/ticket.rst:17 -msgid "" -"This setting will add the ticket reference on the right site of the subject." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.vip}``" msgstr "" -#: ../settings/ticket.rst:20 -msgid "Example: ``Some Subject [Ticket#12345]``" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Web" msgstr "" -#: ../settings/ticket.rst:26 -msgid "*Left*" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.web}``" msgstr "" -#: ../settings/ticket.rst:23 -msgid "" -"This setting will add the ticket reference on the left site of the subject." +#: ../misc/variables/ticket.rst:1 +msgid "``https://zammad.com`` or empty if not set" msgstr "" -#: ../settings/ticket.rst:26 -msgid "Example: ``[Ticket#12345] Some Subject``" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Pending till" msgstr "" -#: ../settings/ticket.rst:29 -msgid "*None*" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.pending_time}``" msgstr "" -#: ../settings/ticket.rst:29 -msgid "This will completely remove ticket references from the subject." +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not set" msgstr "" -#: ../settings/ticket.rst:33 -msgid "" -"Please ensure to take a look at :doc:`/channels/email/settings` within the " -"email channel to ensure you have at least one reference that helps Zammad to " -"assign follow-ups correctly." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Priority > Name" msgstr "" -#: ../settings/ticket.rst:37 -msgid "" -"Disabling this and not setting up any further follow up search will lead to " -"unexpected results!" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.priority.name}``" msgstr "" -#: ../settings/ticket.rst:65 -msgid "" -"Ticket Last Contact Behaviour (default: ``Use the start time of the last " -"customer thread (which may consist of multiple articles).``)" +#: ../misc/variables/ticket.rst:1 +msgid "``2 normal``" msgstr "" -#: ../settings/ticket.rst:41 -msgid "" -"This setting changes the way Zammad updates the ``Last Contact`` value of a " -"ticket. This is fairly important for overviews and what you expect upon " -"ticket updates of a customer." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > State > Name" msgstr "" -#: ../settings/ticket.rst:52 -msgid "" -"Use the start time of the last customer thread (which may consist of " -"multiple articles)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.state.name}``" msgstr "" -#: ../settings/ticket.rst:46 -msgid "" -"If this option is chosen, Zammad will update the last updated value just " -"once if a customer replies. After that, Zammad will wait for an agent to " -"react." +#: ../misc/variables/ticket.rst:1 +msgid "``new``, ``open``, ..." msgstr "" -#: ../settings/ticket.rst:50 -msgid "" -"This comes in handy if you want to work tickets in the order of their first " -"update. This will not change ticket orders if customers decide to \"bump\" " -"the ticket affected." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Tags" msgstr "" -#: ../settings/ticket.rst:57 -msgid "Use the time of the very last customer article." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.tags}``" msgstr "" -#: ../settings/ticket.rst:55 +#: ../misc/variables/ticket.rst:1 msgid "" -"When setting this option, Zammad will always update the last updated value. " -"This means that if ordering by ``Last Update``, ticket orders will change if " -"customers \"bump\" the ticket." +"Currently not available, see `Issue 2769 `_" msgstr "" -#: ../settings/ticket.rst:64 -msgid "Last contact value used on :doc:`/manage/overviews`" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Title" msgstr "" -#: ../settings/ticket.rst:65 -msgid "Last contact value used on :doc:`/manage/trigger`" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.title}``" msgstr "" -#: ../settings/ticket.rst:88 +#: ../misc/variables/ticket.rst:1 msgid "" -"Ticket Organization Reassignment (default: ``Update the most recent tickets." -"``)" +"``My amazing Subject`` (normally subject, can be edited within Interface and " +"thus differ)" msgstr "" -#: ../settings/ticket.rst:68 -msgid "" -"This setting changes the way Zammad updates the organization field of the " -"tickets whenever the primary organization of a user is changed." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated at" msgstr "" -#: ../settings/ticket.rst:74 -msgid "Update the most recent tickets." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_at}``" msgstr "" -#: ../settings/ticket.rst:72 -msgid "" -"If this option is chosen, Zammad will update the 100 most recent tickets " -"where the user is the ticket customer. The ticket organization field will be " -"automatically set to the new primary organization of the user." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Address" msgstr "" -#: ../settings/ticket.rst:88 -msgid "Do not update any tickets." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.address}``" msgstr "" -#: ../settings/ticket.rst:77 -msgid "" -"When choosing this option, Zammad will not update any tickets when the " -"user's primary organization is changed." -msgstr "" +#: ../misc/variables/ticket.rst:1 +#, fuzzy +msgid "Ticket > Updated by > Avatar" +msgstr "Ticket > Creado por > Apellido" -#: ../settings/ticket.rst:80 -msgid "**Use with care!**" -msgstr "" +#: ../misc/variables/ticket.rst:1 +#, fuzzy +msgid "``#{ticket.updated_by.avatar(60,60)}``" +msgstr "``#{ticket.created_by.lastname}``" -#: ../settings/ticket.rst:82 -msgid "" -"Using this option may lead to inconsistencies in the system as the ticket " -"organization may become decoupled from the ticket customer." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Department" msgstr "" -#: ../settings/ticket.rst:85 -msgid "" -"However, you may use this option if you wish to maintain :ref:`the shared " -"access ` to the ticket for all organization " -"members of the original organization of the customer." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.department}``" msgstr "" -#: ../settings/ticket.rst:110 -msgid "Ticket Number Format (default: ``Increment (SystemID.Counter)``)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Email" msgstr "" -#: ../settings/ticket.rst:94 -msgid "" -"This setting defines the way Zammad's ticket number will look. Changing this " -"setting in production will cause follow up detection to fail." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.email}``" msgstr "" -#: ../settings/ticket.rst:102 -msgid "Increment (SystemID.Counter)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Fax" msgstr "" -#: ../settings/ticket.rst:98 -msgid "" -"The increment value contains the SystemID (automatically generated during " -"installation) and a increment which counts up with every new Ticket. The " -"increment will automatically get another digit if needed." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.fax}``" msgstr "" -#: ../settings/ticket.rst:102 -msgid "Examples: ``1010138``, ``1010139``" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Firstname" msgstr "" -#: ../settings/ticket.rst:110 -msgid "Date (Year.Month.Day.SystemID.Counter)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.firstname}``" msgstr "" -#: ../settings/ticket.rst:105 -msgid "" -"This version of the ticket number is fairly long. However, because it " -"contains the date of ticket creation, it also allows you to see when the " -"ticket has been created. You may feel familiar with this number format if " -"you've worked with OTRS already." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Lastname" msgstr "" -#: ../settings/ticket.rst:110 -msgid "Examples: ``201206231010138``, ``201206231010139``" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.lastname}``" msgstr "" -#: ../settings/ticket.rst:137 -msgid "OPTIONS" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Login" msgstr "" -#: ../settings/ticket.rst:113 -msgid "" -"The below options allow you to further customize your ticket number. The " -"availability of options differ depending of the chosen ticket number format " -"above." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.login}``" msgstr "" -#: ../settings/ticket.rst:122 -msgid "Checksum (default: ``no``)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Mobile" msgstr "" -#: ../settings/ticket.rst:118 -msgid "" -"If set to yes, we'll built a checksum to further \"unique\" the ticket " -"number of your system. If you're dealing with many other ticket systems this " -"might help to prevent false positive follow up detection on tickets." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.mobile}``" msgstr "" -#: ../settings/ticket.rst:122 -msgid "This will also add another digit to the ticket number." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Note" msgstr "" -#: ../settings/ticket.rst:137 -msgid "Min. size of Number (default: ``5``)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.note}``" msgstr "" -#: ../settings/ticket.rst:125 -msgid "" -"This setting defines the minimum length of your ticket number. If your " -"counter is not yet high enough, Zammad will fill the number with zeros to " -"ensure the wanted length." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Phone" msgstr "" -#: ../settings/ticket.rst:129 -msgid "" -"Please note that the minimum length is ``3`` (SystemID + at least one digit " -"if below 10). Also, if the length is no longer long enough, the number will " -"automatically get one digit longer. Ticket-Numbers **do not overflow**, thus " -"it's save to keep it at 5 or set it lower if wanted." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.phone}``" msgstr "" -#: ../settings/ticket.rst:135 -msgid "" -"This option is only available if ticket number format is set to " -"``Increment``!" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > VIP" msgstr "" -#: ../settings/ticket.rst:142 -msgid "Auto-Assignment" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.vip}``" msgstr "" -#: ../settings/ticket.rst:144 -msgid "" -"In a larger Zammad environment, it happens that several agents open the same " -"ticket at the same time. Although collision detection is then effective, the " -"efficiency of processing can be increased by means of the automatic " -"assignment of tickets when a ticket is opened." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Web" msgstr "" -#: ../settings/ticket.rst:149 -msgid "" -"The automatic assignment of tickets can be activated and configured in the " -"admin area under Settings > Ticket > Auto Assignment." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.web}``" msgstr "" -#: ../settings/ticket.rst:152 -msgid "" -"The auto assignment only works if the ticket has no owner yet. By default, " -"the agent can always reset the ticket owner to ``-`` if needed." +#: ../settings/branding.rst:10 +msgid "Product Name" msgstr "" -#: ../settings/ticket.rst:155 +#: ../settings/branding.rst:7 msgid "" -"If you want to use this function for only specific tickets, you can " -"configure the conditions accordingly to meet your requirement. By default " -"the condition affects all tickets with the state ``open``." +"Defines the name of the application, shown in the web interface, tabs and " +"title bar of the web browser." msgstr "" -#: ../settings/ticket.rst:161 -msgid "" -"If you need to exclude users (e.g. a group leader), you can search and " -"select the desired agents in the ``Exception Users`` list. The search " -"function in this area is only effective, if you have too many agents to " -"display at once to help you with the configuration." +#: ../settings/branding.rst:10 +msgid "Default value: ``Zammad Helpdesk``" msgstr "" -#: ../settings/ticket.rst:167 -#, fuzzy -msgid "Notifications" -msgstr "Verificación de correo electrónico" - -#: ../settings/ticket.rst:191 -#, fuzzy -msgid "Default Notifications" -msgstr "Verificación de correo electrónico" +#: ../settings/branding.rst:13 +msgid "Will be shown in the app and is included in email footers." +msgstr "" -#: ../settings/ticket.rst:170 -msgid "" -"This setting allows you to configure the default ticket notifications that " -"will be applied to all new agent users (incl. users who were just assigned " -"agent role). Simply change the notification matrix to desired state and " -"press **Save**." +#: ../settings/branding.rst:19 +msgid "Logo" msgstr "" -#: ../settings/ticket.rst:175 -msgid "" -"In case an agent already exists, their ticket notification preferences will " -"be preserved. Optionally, you can also **Apply current defaults to all " -"agents**." +#: ../settings/branding.rst:16 +msgid "Defines the logo of the application, shown in the login page of Zammad." msgstr "" -#: ../settings/ticket.rst:181 +#: ../settings/branding.rst:18 msgid "" -"**Potential time-consuming action:** Applying default ticket notifications " -"to all agent users may take some time to complete, be patient! The exact " -"time will depend on the size of your system and the number of agents." +"Ensure to hit the \"Submit\" button after uploading the logo. Otherwise your " +"change will not be saved." msgstr "" -#: ../settings/ticket.rst:185 +#: ../settings/branding.rst:22 msgid "" -"**Active agents only!** When current default ticket notifications are " -"applied, only active agent users are considered. In case an agent is re-" -"activated *after* this action, they will still have the old notification " -"configuration." +"Allows to set the default language of the Zammad instance. The here defined " +"locale mostly acts as a fallback for:" msgstr "" -#: ../settings/ticket.rst:190 -msgid "" -"In case you want to go back to the initial state of ticket notifications, " -"you can click on **Reset to default** button." +#: ../settings/branding.rst:25 +msgid "user preferences (if Zammad can't detect the users locale)" msgstr "" -#: ../settings/ticket.rst:194 ../settings/ticket.rst:196 -msgid "Duplicate Detection" +#: ../settings/branding.rst:26 +msgid "CSV output (reporting, time accounting)" msgstr "" -#: ../settings/ticket.rst:236 ../settings/ticket.rst:238 -msgid "Detect Duplicate Ticket Creation" +#: ../settings/branding.rst:30 +msgid "Define the timezone of your Zammad installation." msgstr "" -#: ../settings/ticket.rst:197 ../settings/ticket.rst:199 +#: ../settings/branding.rst:32 msgid "" -"This setting turns on the duplicate ticket detection mechanism during ticket " -"creation. If similar tickets are found in the system, a suitable warning " -"will be shown to the user trying to create a ticket." +"This does not have any effect on timings for your agents or how Zammad " +"stores date and time values." msgstr "" -#: ../settings/ticket.rst:204 ../settings/ticket.rst:206 -msgid "A Sample Duplicate Ticket Warning" +#: ../settings/branding.rst:35 +msgid "Changing this value has direct consequences on the following areas:" msgstr "" -#: ../settings/ticket.rst:206 ../settings/ticket.rst:208 -msgid "" -"You can choose which ticket attributes will be matched by selecting them in " -"**Attributes to compare** field. Only if the ticket attribute value provided " -"by the user in the ticket create form is *equal* with the attribute in an " -"existing ticket, the warning will be shown." +#: ../settings/branding.rst:37 +msgid ":doc:`/manage/scheduler` tasks" msgstr "" -#: ../settings/ticket.rst:211 ../settings/ticket.rst:213 -msgid "**Warning title** and **Warning message** are configurable as well." +#: ../settings/branding.rst:38 +msgid "search indexing (and thus reporting)" msgstr "" -#: ../settings/ticket.rst:213 ../settings/ticket.rst:215 -msgid "" -"You can limit the detection only to certain user roles. By default, only " -"agents will see the warning." +#: ../settings/branding.rst:40 +msgid "calendar subscriptions" msgstr "" -#: ../settings/ticket.rst:216 ../settings/ticket.rst:218 -msgid "" -"If you don't want to show the matched tickets as part of the warning, you " -"can set **Show matching ticket(s) in the warning** setting to *no*." +#: ../settings/branding.rst:41 +msgid "browser printing" msgstr "" -#: ../settings/ticket.rst:219 ../settings/ticket.rst:221 +#: ../settings/branding.rst:43 msgid "" -"By default, **Permission level for looking up ticket** is set to *User*, " -"which means user permissions will be honored during sarch. The user will " -"see the warning only if tickets they have access to are matched. " -"Alternatively, you can set this setting to *System*, in which case the " -"search will happen within *all* tickets in the system, regardless of user " -"permissions." +"Please note that some of above are fallbacks in case Zammad could not detect " +"the agents timezone correctly." msgstr "" -#: ../settings/ticket.rst:225 ../settings/ticket.rst:227 -msgid "**🦺 Safety first!**" +#: ../settings/branding.rst:77 +msgid "Pretty Date" msgstr "" -#: ../settings/ticket.rst:227 ../settings/ticket.rst:229 +#: ../settings/branding.rst:47 msgid "" -"Even if the permission level is set to *System*, the user will not be shown " -"the tickets they don't have access to in the warning, even if they match." +"This setting allows you to define how Zammad should display time stamps " +"within the interface to all users." msgstr "" -#: ../settings/ticket.rst:231 ../settings/ticket.rst:233 +#: ../settings/branding.rst:50 msgid "" -"However, just the confirmation about the existence of the tickets in the " -"system may be considered an unwanted information disclosure. Use this option " -"carefully!" +"This does not have any effect on how Zammad returns e.g. time values via " +"variables." msgstr "" -#: ../settings/ticket.rst:235 ../settings/ticket.rst:237 -msgid "" -"Finally, you can configure between matching within **All tickets** or **Open " -"tickets** only by setting **Match tickets in following states**. Depending " -"on the current ticket state, a ticket may or not be matched." +#: ../settings/branding.rst:77 +msgid "Choose in between the following options:" msgstr "" -#: ../system/core-workflows.rst:2 -msgid "Core Workflows" +#: ../settings/branding.rst:64 +msgid "relative" msgstr "" -#: ../system/core-workflows.rst:4 +#: ../settings/branding.rst:55 msgid "" -"Core Workflows allow you to adjust object attributes in many ways. For " -"example:" +"This timestamp shows a relative time span until it switches to a date. Over " +"time, it will change as follows:" msgstr "" -#: ../system/core-workflows.rst:7 -msgid "show / hide fields" +#: ../settings/branding.rst:58 +msgid "just now" msgstr "" -#: ../system/core-workflows.rst:8 -msgid "adjust mandatory setting" +#: ../settings/branding.rst:59 +msgid "5 minutes ago" msgstr "" -#: ../system/core-workflows.rst:9 -msgid "manipulate available options" +#: ../settings/branding.rst:60 +msgid "3 days 1 hour ago" msgstr "" -#: ../system/core-workflows.rst:11 -msgid "" -"With this, you can provide exactly the information your users really need!" +#: ../settings/branding.rst:61 +msgid "``03/04/2022``" msgstr "" -#: ../system/core-workflows.rst:15 -msgid "" -"If the pre-defined :doc:`/system/objects` are not enough, please add them " -"beforehand." +#: ../settings/branding.rst:63 +msgid "Hovering the timestamp helps, you'll always get a clean timestamp then." msgstr "" -#: ../system/core-workflows.rst:17 -msgid "" -"If you experience slow or unreliable field updates, please see :ref:`Core " -"Workflow Ajax Modus `" +#: ../settings/branding.rst:71 +msgid "absolute" msgstr "" -#: ../system/core-workflows.rst:22 +#: ../settings/branding.rst:67 msgid "" -"This is a very enhanced functionality and can cause unexpected UI behavior. " -"Please ensure to test your use cases after configuration to reduce surprises." +"This timestamp always includes the week day. For one week after creation, " +"the timestamp will not contain the date itself: Thursday 18:35." msgstr "" -#: ../system/core-workflows.rst:None -msgid "Dialogue for adding a new workflow" +#: ../settings/branding.rst:71 +msgid "After a week it will switch to: ``Friday 4. Mar 16:00``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:2 -msgid "Core Workflow Condition Operators" +#: ../settings/branding.rst:76 +msgid "timestamp" msgstr "" -#: ../system/core-workflows/condition-operators.rst:4 +#: ../settings/branding.rst:74 msgid "" -"You might know that there is a separate section for explaining :doc:" -"`condition operators `. Head over there to " -"see a detailed explanation of many conditions and operators." +"This will cause Zammad to show a complete timestamp according to your locale " +"defaults. For English this could be e.g. ``2022/12/03 2:40 pm`` or for " +"German e.g. ``12.03.2022 14:40``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:8 -msgid "" -"Due to differences to other places in Zammad which are also using conditions " -"(e.g. triggers), you can find a dedicated description of operators for core " -"workflows below." +#: ../settings/branding.rst:78 +msgid "Default setting: ``relative``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:12 -msgid "" -"Be aware that the availability of the operators depends on the selected " -"attribute and its field type. Some of the operators may only be available " -"for system attributes (e.g. for \"tags\", \"active\")." +#: ../settings/security.rst:2 +msgid "Security" msgstr "" -#: ../system/core-workflows/condition-operators.rst:20 -msgid "Operator" +#: ../settings/security.rst:4 +msgid "" +"For your overview we split each tab within security settings into its own " +"page:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:22 -msgid "after (absolute)" +#: ../settings/security/base.rst:2 ../settings/system/base.rst:2 +#: ../settings/ticket.rst:8 +msgid "Base" msgstr "" -#: ../system/core-workflows/condition-operators.rst:23 -msgid "Matches if a date/time is after a specific point in time." +#: ../settings/security/base.rst:5 +msgid "New User Accounts" msgstr "" -#: ../system/core-workflows/condition-operators.rst:24 -msgid "after (relative)" +#: ../settings/security/base.rst:9 +msgid "" +"Activates the `register as a new customer` function on the login page. If " +"set to ``no`` only administrators or agents can create new accounts manually." msgstr "" -#: ../system/core-workflows/condition-operators.rst:25 -msgid "Matches if a time span after a specified event has passed." +#: ../settings/security/base.rst:13 ../settings/security/base.rst:38 +#: ../settings/security/base.rst:66 +msgid "Default setting: ``yes``" msgstr "" -#: ../system/core-workflows/condition-operators.rst:26 -msgid "before (absolute)" +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"New User Accounts\" setting" msgstr "" -#: ../system/core-workflows/condition-operators.rst:27 -msgid "Matches if a date/time is before a specific point in time." +#: ../settings/security/base.rst:22 +msgid "" +"Deactivation of above function **does not** deactivate automatic account " +"creation! This means: If a user writes e.g. an email to Zammad and has no " +"account yet, Zammad will automatically create the account. User accounts are " +"a direct dependency of tickets and thus technically mandatory." msgstr "" -#: ../system/core-workflows/condition-operators.rst:28 -msgid "before (relative)" +#: ../settings/security/base.rst:29 +msgid "Lost Password" msgstr "" -#: ../system/core-workflows/condition-operators.rst:29 -msgid "Matches if a time span after a specified event has not passed." +#: ../settings/security/base.rst:33 +msgid "" +"Activates the `lost password` function on the login page. If set to ``no`` " +"only administrators may change the user's password - users may update their " +"own password if they're still logged in and they have the required :doc:" +"`permission `." msgstr "" -#: ../system/core-workflows/condition-operators.rst:30 -msgid "contains" +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"Lost Password\" setting" msgstr "" -#: ../system/core-workflows/condition-operators.rst:31 -msgid "Matches if a specified value is present." +#: ../settings/security/base.rst:49 +msgid "" +"With third party authentications - but especially LDAP - you may want to " +"disable this function. Zammad **will not** change third party login " +"passwords and instead set or change the local password!" msgstr "" -#: ../system/core-workflows/condition-operators.rst:33 -msgid "Matches if all of the specified values are present." +#: ../settings/security/base.rst:56 +msgid "Password Login" msgstr "" -#: ../system/core-workflows/condition-operators.rst:35 -msgid "Matches if none of the specified values are present." +#: ../settings/security/base.rst:60 +msgid "" +"Activates the username & password login by default and if no third-party " +"login is activated. Disabling password login on the Zammad login page only " +"takes effect if you enable any :doc:`third-party`." msgstr "" -#: ../system/core-workflows/condition-operators.rst:36 -msgid "contains not" +#: ../settings/security/base.rst:64 +msgid "See :doc:`third-party` for supported third-party logins." msgstr "" -#: ../system/core-workflows/condition-operators.rst:37 -msgid "Matches if a specified value is not present." +#: ../settings/security/base.rst:0 +msgid "Figure showing de-activated \"Password Login\" setting" msgstr "" -#: ../system/core-workflows/condition-operators.rst:39 -msgid "Matches if one specified value is present." +#: ../settings/security/base.rst:77 +msgid "" +"To help administrators to overcome \"login issues\", Zammad automatically " +"offers a password request for administrator users. This allows you to adjust " +"Third-Party applications even if the login does no longer work!" msgstr "" -#: ../system/core-workflows/condition-operators.rst:41 -msgid "Matches if one specified value is not present." +#: ../settings/security/base.rst:84 +msgid "Session Timeout" msgstr "" -#: ../system/core-workflows/condition-operators.rst:42 -msgid "does not match regex" +#: ../settings/security/base.rst:86 +msgid "" +"All settings below by default are set to ``4 weeks``. Session Timeout " +"defines the life time of a users session. As soon as it's reached, Zammad " +"will automatically log off the session in question." msgstr "" -#: ../system/core-workflows/condition-operators.rst:43 -msgid "Matches if content doesn't fit to regex rule." +#: ../settings/security/base.rst:91 +msgid "" +"Zammad takes the highest value set assigned for the user based on the " +"permissions." msgstr "" -#: ../system/core-workflows/condition-operators.rst:44 -msgid "ends with" +#: ../settings/security/base.rst:94 +msgid "``admin``" msgstr "" -#: ../system/core-workflows/condition-operators.rst:45 -msgid "Matches if content ends with specified value." +#: ../settings/security/base.rst:96 +msgid "``ticket.customer``" msgstr "" -#: ../system/core-workflows/condition-operators.rst:46 -msgid "ends with one of" +#: ../settings/security/base.rst:97 +msgid "``default`` (fallback if user doesn't have above permissions set)" msgstr "" -#: ../system/core-workflows/condition-operators.rst:47 -msgid "Matches if content ends with one of the specified values." +#: ../settings/security/base.rst:99 +msgid "" +"All settings act independently from each other allowing you to disable the " +"timeouts for e.g. admins, but not agents." msgstr "" -#: ../system/core-workflows/condition-operators.rst:48 -msgid "from (relative)" -msgstr "" +#: ../settings/security/base.rst:115 +#: ../system/integrations/checkmk/api-reference.rst:13 +msgid "Example" +msgstr "Ejemplo" -#: ../system/core-workflows/condition-operators.rst:49 -msgid "Matches if date/time is after a period of time after an event." +#: ../settings/security/base.rst:107 +msgid "Let's suppose you configured the following session timeouts" msgstr "" -#: ../system/core-workflows/condition-operators.rst:51 -msgid "Matches if content is equal to a specified value." +#: ../settings/security/base.rst:104 +msgid "default: 3 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:52 -msgid "is any of" +#: ../settings/security/base.rst:105 +msgid "admin: 2 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:53 -msgid "Matches if content is equal to any of specified values." +#: ../settings/security/base.rst:106 +msgid "ticket.agent: 4 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:54 -msgid "is modified" +#: ../settings/security/base.rst:107 +msgid "ticket.customer: 1 week" msgstr "" -#: ../system/core-workflows/condition-operators.rst:55 -msgid "Matches if content is modified." +#: ../settings/security/base.rst:115 +msgid "This results in the following situations" msgstr "" -#: ../system/core-workflows/condition-operators.rst:57 -#: ../system/core-workflows/condition-operators.rst:61 -msgid "True from the moment of changing content until form submit." +#: ../settings/security/base.rst:110 +msgid "a user with ``admin`` permission will have a timeout of 2 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:58 -msgid "is modified to" +#: ../settings/security/base.rst:111 +msgid "" +"a user with ``admin`` and ``ticket.agent`` permissions will have a timeout " +"of 2 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:59 -msgid "Matches if content is modified to a specific value." +#: ../settings/security/base.rst:113 +msgid "" +"a user with ``ticket.customer`` permission will have a timeout of 1 week" msgstr "" -#: ../system/core-workflows/condition-operators.rst:62 -msgid "is none of" +#: ../settings/security/base.rst:115 +msgid "" +"a user with neither ``admin``, ``ticket.agent`` nor ``ticket.customer`` " +"permissions will have a timeout of 3 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:63 -msgid "Matches if content is none of any specified values." +#: ../settings/security/password.rst:4 +msgid "" +"This section allows you to define password requirements for the local user " +"accounts." msgstr "" -#: ../system/core-workflows/condition-operators.rst:65 -msgid "Matches if content is not equal to a specified value." +#: ../settings/security/password.rst:9 +msgid "" +"Zammad does **not** allow you to change your LDAP password, instead, it will " +"set a password in its local database which might confuse your users. This " +"might be addressed in the future by `#1169 `_." msgstr "" -#: ../system/core-workflows/condition-operators.rst:67 -msgid "Matches if content is present." +#: ../settings/security/password.rst:14 +msgid "**Exception for admins**" msgstr "" -#: ../system/core-workflows/condition-operators.rst:68 -msgid "just changed" +#: ../settings/security/password.rst:16 +msgid "" +"Please note that below password policies *do not* affect administrators " +"setting passwords on user accounts. While this seems strange and not safe we " +"believe that an administrator knowing an user's password is insecure as well." msgstr "" -#: ../system/core-workflows/condition-operators.rst:69 -msgid "Matches if content has changed." +#: ../settings/security/password.rst:21 +msgid "The suggested workflow is either:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:71 -#: ../system/core-workflows/condition-operators.rst:75 +#: ../settings/security/password.rst:23 msgid "" -"Only true for the moment of changing content until next form field action/" -"click." +"to use third party logins to not require local passwords at all **- or -**" msgstr "" -#: ../system/core-workflows/condition-operators.rst:72 -msgid "just changed to" +#: ../settings/security/password.rst:25 +msgid "to require your *user to reset the password* upon first login." msgstr "" -#: ../system/core-workflows/condition-operators.rst:73 -msgid "Matches if content has changed to a specified value." +#: ../settings/security/password.rst:27 +msgid "" +"This way administrators are not required to set a user's password at all!" msgstr "" -#: ../system/core-workflows/condition-operators.rst:76 -msgid "matches regex" +#: ../settings/security/password.rst:31 +msgid "Maximum Failed Logins" msgstr "" -#: ../system/core-workflows/condition-operators.rst:77 -msgid "Matches if value fits to regex rule." +#: ../settings/security/password.rst:33 +msgid "" +"You can choose a value between ``4`` and ``20``. This defines how often a " +"login to a user account may fail until Zammad will lock it. Your users can " +"always use the \"forgot password\" function to change their password and " +"unlock their account." msgstr "" -#: ../system/core-workflows/condition-operators.rst:79 -msgid "Matches if no content is present." +#: ../settings/security/password.rst:38 +msgid "The default value is ``10``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:80 -msgid "starts with" +#: ../settings/security/password.rst:42 +msgid "Beside changing the user's password, you can also unlock accounts via" msgstr "" -#: ../system/core-workflows/condition-operators.rst:81 -msgid "Matches if content starts with specified value." +#: ../settings/security/password.rst:44 +msgid ":ref:`user management list `" msgstr "" -#: ../system/core-workflows/condition-operators.rst:82 -msgid "starts with one of" +#: ../settings/security/password.rst:45 +msgid ":docs:`console `" msgstr "" -#: ../system/core-workflows/condition-operators.rst:83 -msgid "Matches if content starts with one of the specified values." +#: ../settings/security/password.rst:46 +msgid ":docs:`API `" msgstr "" -#: ../system/core-workflows/condition-operators.rst:84 -msgid "till (relative)" +#: ../settings/security/password.rst:50 +msgid "Failed logins via LDAP no longer lock accounts." msgstr "" -#: ../system/core-workflows/condition-operators.rst:85 -msgid "Matches if date/time is before a period of time before an event." +#: ../settings/security/password.rst:53 +msgid "2 Lower Case And 2 Upper Case Characters" msgstr "" -#: ../system/core-workflows/condition-operators.rst:86 -msgid "today" +#: ../settings/security/password.rst:55 +msgid "" +"You can add complexity to passwords by enforcing at least 2 upper and lower " +"case characters." msgstr "" -#: ../system/core-workflows/condition-operators.rst:87 -msgid "Matches if date/time is today." +#: ../settings/security/password.rst:58 ../settings/security/password.rst:83 +msgid "The default value is ``no``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:88 -msgid "within last (relative)" +#: ../settings/security/password.rst:62 +msgid "Minimum Length" msgstr "" -#: ../system/core-workflows/condition-operators.rst:89 +#: ../settings/security/password.rst:64 msgid "" -"Matches if date/time content is within specified period of time before now." +"This defines the minimum password length required for users to provide (from " +"``4`` to ``20``)." msgstr "" -#: ../system/core-workflows/condition-operators.rst:91 -msgid "within next (relative)" +#: ../settings/security/password.rst:67 +msgid "The default value is ``6``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:92 -msgid "" -"Matches if date/time content is within specified period of time after now." +#: ../settings/security/password.rst:71 +msgid "Digit Required" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:2 -msgid "How do they work?" +#: ../settings/security/password.rst:73 +msgid "This enforces your users to use at least one digit within the password." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:4 -msgid "" -"Core Workflows are executed according to their priority. If two workflows " -"have the same priority, they are executed in alphabetical order based on " -"their **name**." +#: ../settings/security/password.rst:75 +msgid "The default value is ``yes``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:8 +#: ../settings/security/password.rst:78 +msgid "Special Character Required" +msgstr "" + +#: ../settings/security/password.rst:80 msgid "" -"Because of the way Core Workflows work, all changes to attributes are " -"checked with the application server - please see :doc:`limitations` for " -"possible issues." +"This setting allows you to improve your password quality even more by " +"enforcing the password to contain at least one special character." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:12 +#: ../settings/security/ssl-certificates.rst:2 +msgid "SSL Certificates" +msgstr "" + +#: ../settings/security/ssl-certificates.rst:7 msgid "" -"Below we're talking about settings that are important and not self-" -"explanatory." +"Zammad offers the possibility to upload custom certificates and custom " +"Certificate Authority (CA) certificates. This can be useful if you want to " +"connect Zammad the secure way to other systems which are using custom " +"certificates." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:17 +#: ../settings/security/ssl-certificates.rst:12 msgid "" -"Choose the object context you want to run the workflow in. This will decide " -"on your available attributes and actions." +"An example usecase might be: You have an internal LDAP server that is not " +"accessible from the internet, and you want a SSL-encrypted connection, using " +"a custom certificate." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:20 -msgid "Ticket objects also have access to the ticket customer." +#: ../settings/security/ssl-certificates.rst:19 +msgid "" +"You should have an existing custom certificate file and/or a custom CA " +"certificate file, which you want to add to Zammad. As filetype ``.crt`` is " +"supported and the certificate format has to be PEM (Base64 ASCII)." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:25 +#: ../settings/security/ssl-certificates.rst:25 msgid "" -"Choose in which situation the workflow is applied. Contexts can be combined " -"to avoid duplicate workflows." +"When you import a custom CA certificate, all certificates generated with " +"this are trusted. This can be useful if you have more than one system/" +"certificate you want to connect to and the certificates are issued from the " +"same custom CA." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:30 -msgid "Creation mask" +#: ../settings/security/ssl-certificates.rst:31 +msgid "Add a Certificate" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:29 +#: ../settings/security/ssl-certificates.rst:33 msgid "" -"If selected, your conditions and actions will affect all applicable creation " -"masks." +"To add a custom certificate or a custom CA certificate, head over to the " +"Admin panel > Settings > Security > SSL Certificates. Here you can find a " +"\"Add SSL Certificate\" button. In the dialog you can either select a " +"certificate file or paste the content of the certificate:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:34 -msgid "Edit mask" +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate adding dialog" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:33 +#: ../settings/security/ssl-certificates.rst:43 msgid "" -"If selected, your conditions and actions will affect all applicable edit " -"masks." +"After selecting a file or pasting the content of the certificate, click on " +"the \"Add\" button to finally upload it to Zammad. Then, the certificates " +"are immediately effective, no restart or similar required." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:39 +#: ../settings/security/ssl-certificates.rst:49 msgid "" -"Zammad differentiates between selected and saved conditions. These can be " -"combined wherever needed." +"Please note that only single certificate files are supported. That means if " +"you want to import a certificate / CA certificate, it must contain **only " +"one** certificate." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:42 -msgid "**⚠️ Restrict workflows to specific roles if needed!**" +#: ../settings/security/ssl-certificates.rst:54 +msgid "Certificate Overview" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:44 +#: ../settings/security/ssl-certificates.rst:56 msgid "" -"By default and unless configured in conditions, workflow rules are executed " -"for **all roles**. This also affects your customers!" +"After you added a certificate, you can see a table with information for each " +"added certificate:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:50 -msgid "Selected Conditions" +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing table of added certificates" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:48 +#: ../settings/security/ssl-certificates.rst:64 msgid "" -"These conditions are based on form values and match if an appropriate " -"selection is made (e.g. choosing another group in the ticket without " -"saving). This applies for drafts (active selection) and currently saved " -"values." +"Here you can download the certificate or delete it, if you don't need it " +"anymore." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:64 -msgid "Saved Conditions" -msgstr "" +#: ../settings/security/ssl-certificates.rst:68 +#, fuzzy +msgid "Deleting Certificates" +msgstr "Verificación de correo electrónico" -#: ../system/core-workflows/how-do-they-work.rst:53 +#: ../settings/security/ssl-certificates.rst:70 msgid "" -"These conditions only match if the selected values are stored in the " -"database. It ignores the current value or selection of the field, as long as " -"the changes are not saved (e.g. performing field operations for an existing " -"ticket, which is viewed/opened by an agent)." +"If you want to delete a specific certificate, you can do it by clicking on " +"the menu in the actions column and selecting delete:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:60 -msgid "" -"Keep in mind that the value has to be available in the situation where you " -"need it. Otherwise the condition won't match." +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate deletion button" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:63 -msgid "" -"Example: you can't perform any actions with *saved condition* on a ticket in " -"creation, because there are no saved values at that time." +#: ../settings/security/ssl-certificates.rst:79 +msgid "Downloading Certificates" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:66 +#: ../settings/security/ssl-certificates.rst:81 msgid "" -"You can find a description of the condition operators for core workflows :" -"doc:`here `." +"If you want to download your certificates, you can do this as well via " +"corresponding action buttons." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:72 -msgid "" -"Which actions should we run on the relevant fields? The possible actions " -"depend on the object type. However, usually you can at least change the " -"visibility and whether the field is mandatory." +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate download button" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:76 -msgid "Be aware that actions are not available for **related** context." +#: ../settings/security/third-party.rst:13 +msgid "Login Providers" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:78 -msgid "" -"**Example:** Let's assume you are working in the ticket context. While you " -"can have customer *conditions*, you *can't adjust* objects with actions in " -"that scope. That's because this wouldn't have any impact on the ticket " -"dialog. Of course all ticket attributes (state, owner, ...) are available." +#: ../settings/security/third-party.rst:2 +msgid "Third-Party Applications" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:84 +#: ../settings/security/third-party.rst:4 msgid "" -"Please also have a look at our :doc:`limitations` to be safe from surprises." -msgstr "" - -#: ../system/core-workflows/how-do-they-work.rst:88 -msgid "Available Operators" +"Third party authentication is a great way to help your users to login to " +"Zammad more easily. If the account is yet unknown, Zammad will create a new " +"user automatically, without the user needed to interact (e.g. type in his " +"name). Another big advantage of this feature is that your user doesn't need " +"to remember another password." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:90 -msgid "The availability of operators depends on the object type and scope." +#: ../settings/security/third-party.rst:10 +msgid "" +"You can deactivate logging in via :ref:`security_password_login` if any of " +"the mentioned authentication providers are enabled in your instance." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:94 +#: ../settings/security/third-party.rst:27 msgid "" -"Please note that actions may or may not restrict API based access to " -"attributes. We're displaying the following icons for your overview to " -"understand these limits better:" +"We're currently missing documentation for the following login providers:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:0 -msgid "|api| This icon indicates the action affects the API." +#: ../settings/security/third-party.rst:29 +msgid "LinkedIn" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:163 -msgid "api" +#: ../settings/security/third-party.rst:30 +msgid "Weibo" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:0 -msgid "|ui| This icon indicates the action only affects the web interface." +#: ../settings/security/third-party.rst:35 +#, fuzzy +msgid "Automatic Account Link on Initial Logon" +msgstr "Notificación automática de vinculación de cuentas" + +#: ../settings/security/third-party.rst:37 +msgid "" +"In general there's two possible options for Zammad on how to deal with " +"already known users as they try to authenticate against a third-party " +"application. By default, Zammad will not automatically link \"unknown\" " +"authentication providers to existing accounts." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:167 -msgid "ui" +#: ../settings/security/third-party.rst:42 +msgid "" +"This means that the user has to manually link authentication providers to " +"their accounts (for more about this :user-docs:`consult the user " +"documentation `)." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:102 -msgid "show |ui|" +#: ../settings/security/third-party.rst:46 +msgid "" +"Sometimes this doesn't come in handy as this also means you'll receive error " +"messages about \"email address being in use already\" for (yet) unknown " +"third-party authentication methods." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:102 -msgid "Display the chosen field. Allows setting of values." +#: ../settings/security/third-party.rst:50 +msgid "" +"If you want to allow your users to always be able to log in, no matter what, " +"you may want to enable ``Automatic account link on initial logon``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:109 -msgid "hide |ui|" +#: ../settings/security/third-party.rst:None +msgid "" +"Screenshot highlighting the \"Automatic account link on initial logon\"\n" +"setting" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:105 +#: ../settings/security/third-party.rst:60 +#, fuzzy +msgid "Automatic Account Linking Notification" +msgstr "Notificación automática de vinculación de cuentas" + +#: ../settings/security/third-party.rst:64 msgid "" -"Hide the chosen field. However, it technically still allows setting the " -"field." +"To improve security and your users awareness, you can enable Zammad to " +"notify your users when a new third-party application has been linked to " +"their account." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:108 +#: ../settings/security/third-party.rst:68 msgid "" -"Please note that the field is **not** gone and still contains an existing " -"value (if set)! Consider *remove* instead, if you want this field to be gone." +"This notification is sent out once per third-party application. Zammad does " +"also mention the method used, e.g.: ``Microsoft``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:112 -msgid "remove |ui|" +#: ../settings/security/third-party.rst:71 +msgid "By default this setting is not active (set to ``no``)." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:112 -msgid "Entirely removes the field. The field value will not be evaluated." +#: ../settings/security/third-party.rst:0 +msgid "" +"Screenshot showing sample notification mail after initial\n" +"third-party linking" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:115 -msgid "set mandatory |ui| |api|" +#: ../settings/security/third-party.rst:85 +msgid "" +"This notification is only sent if the account in question already exists. If " +"the login via the third-party also creates the missing account, the " +"notification will be skipped." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:115 -msgid "Sets the field to mandatory." +#: ../settings/security/third-party.rst:89 +msgid "This means it only affects:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:118 -msgid "set optional |ui| |api|" +#: ../settings/security/third-party.rst:91 +msgid "manual account linking within the third-party page of the users profile" +msgstr "" + +#: ../settings/security/third-party.rst:92 +msgid "" +"logging into an existing local account by utilizing the *automatic account " +"link on initial logon* functionality" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:118 -msgid "Sets the field to optional." +#: ../settings/security/third-party.rst:None +msgid "" +"Screenshot showing the \"automatic account linking notification\"\n" +"setting" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:124 -msgid "add option |ui| |api|" +#: ../settings/security/third-party.rst:100 +msgid "No User Creation on Logon" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:121 -msgid "Allows adding options to tree selects or selects." +#: ../settings/security/third-party.rst:102 +msgid "" +"By default, Zammad will create a new user account if the user logs in via a " +"third-party application and the account doesn't exist yet." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:123 +#: ../settings/security/third-party.rst:105 msgid "" -"You have to use the \"remove option\" before performing this action. It " -"allows you to use *existing* configured values." +"If you want to prevent Zammad from creating new accounts on logon, you can " +"disable this feature by setting ``No user creation on logon`` to ``yes``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:128 -msgid "remove option |ui| |api|" +#: ../settings/security/third-party.rst:None +#, fuzzy +msgid "Screenshot showing the \"no user creation on logon\" setting" msgstr "" +"Captura de pantalla que muestra la configuración básica de una cuenta de " +"correo electrónico entrante" -#: ../system/core-workflows/how-do-they-work.rst:127 +#: ../settings/security/third-party/facebook.rst:4 msgid "" -"Allows removing options from tree selects or selects. It allows you to use " -"*existing* configured values." -msgstr "" - -#: ../system/core-workflows/how-do-they-work.rst:134 -msgid "set fixed to |ui| |api|" +"It is possible to create a quick login for your helpdesk via Facebook To do " +"so, you need to follow these steps:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:131 -msgid "Reduces the available options by your selection." +#: ../settings/security/third-party/facebook.rst:9 +msgid "Register Facebook App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:133 +#: ../settings/security/third-party/facebook.rst:11 msgid "" -"This reduces your workflows in terms of *add option* and *remove option*." +"Visit [https://developers.facebook.com/apps/] and click on \"Add a new App\"" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:137 -msgid "fill in |ui|" +#: ../settings/security/third-party/facebook.rst:None +msgid "initial page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:137 -msgid "Allows filling in of string and integer fields with your values." +#: ../settings/security/third-party/facebook.rst:17 +msgid "After that enter the app settings" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:141 -msgid "fill in empty |ui|" +#: ../settings/security/third-party/facebook.rst:None +msgid "Create App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:140 -msgid "" -"Allows filling in of string and integer fields with your values **if the " -"field is empty**." +#: ../settings/security/third-party/facebook.rst:22 +msgid "Navigate to \"Settings\" and fill in this infromation" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:144 -msgid "select |ui|" +#: ../settings/security/third-party/facebook.rst:None +msgid "App Settings" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:144 -msgid "Select a specific value within a select, tree select or boolean field." +#: ../settings/security/third-party/facebook.rst:27 +msgid "Navigate to app review and Check \"Make [appname] public?\"" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:153 -msgid "auto select |ui|" +#: ../settings/security/third-party/facebook.rst:None +msgid "App Review" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:147 -msgid "Helps users with tree select and select fields:" +#: ../settings/security/third-party/facebook.rst:35 +msgid "Configure Zammad as Facebook App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:149 +#: ../settings/security/third-party/facebook.rst:37 msgid "" -"If the field has only one option available for selection and no value yet, " -"the value will be automatically set." +"Navigate to \"Admin -> Security -> Third Party Applications\" and enter the " +"App ID and the App Secret. You can find this Key in the Dashbard of your " +"Facebok app." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:152 +#: ../settings/security/third-party/facebook.rst:None +msgid "Zammad Configuration" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:44 +#: ../settings/security/third-party/github.rst:43 +#: ../settings/security/third-party/gitlab.rst:46 msgid "" -"This option only works if you have one value and doesn't work if there is " -"more than one option available." +"Now you can link accounts via \"Avatar -> Profile -> Link Accounts\" or " +"login via Zammad login page." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:157 -msgid "set readonly |ui|" +#: ../settings/security/third-party/github.rst:2 +#: ../system/integrations/github.rst:2 +msgid "GitHub" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:156 +#: ../settings/security/third-party/github.rst:4 msgid "" -"Allows you to display an attribute as read only (which means no changes are " -"possible)." +"It is possible to create a quick login for your helpdesk via GitHub. To " +"activate the quick login you need to enable OAuth for GitHub." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:161 -msgid "unset readonly |ui|" +#: ../settings/security/third-party/github.rst:8 +msgid "Register GitHub App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:160 +#: ../settings/security/third-party/github.rst:10 msgid "" -"In case a workflow set the field in question to read only, you can undo this " -"with option above." +"Visit https://www.github.com/settings/applications/new and enter the app " +"settings. As callback URL enter \"https://zammad_host/auth/github/callback\" " +"where zammad_host has to be replaced with your Zammad FQDN" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:172 -msgid "Stop after match" +#: ../settings/security/third-party/github.rst:None +msgid "Register OAuth app on www.github.com" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:174 -msgid "" -"Here you can decide if other workflows are executed after the current one." +#: ../settings/security/third-party/github.rst:19 +msgid "Configure Zammad as GitHub App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:176 +#: ../settings/security/third-party/github.rst:21 msgid "" -"If set to ``no`` (default), further workflows will be executed if they match " -"the condition. In this case, it is possible that your actions from the " -"current workflow can be overwritten by another workflow." +"Enter the \"APP ID\" and the \"APP SECRET\" from the GitHub OAUTH " +"Applications Dashboard" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:180 +#: ../settings/security/third-party/github.rst:None +msgid "GitHub config in Zammad admin interface" +msgstr "" + +#: ../settings/security/third-party/github.rst:28 msgid "" -"If set to ``yes``, no further worflows will be executed after the current " -"one." +"After you configured the GitHub credentials and activated the login method, " +"you should see a new icon on the login page." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:184 -msgid "Priority" +#: ../settings/security/third-party/github.rst:None +msgid "GitHub logo on login page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:186 +#: ../settings/security/third-party/github.rst:34 msgid "" -"You can define the sequence, in which the workflows are executed. The " -"default value is ``500``." +"If you click on the icon you will be redirected to GitHub and see something " +"similar to this:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:189 +#: ../settings/security/third-party/github.rst:None +msgid "GitHub oauth page" +msgstr "" + +#: ../settings/security/third-party/github.rst:40 +#: ../settings/security/third-party/gitlab.rst:42 msgid "" -"The workflows are executed in ascending order by their priority. That means " -"lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." +"When you grant the access you will be redirected to your Zammad instance and " +"logged in as a customer." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:2 -#, fuzzy -msgid "Learn by Example" -msgstr "Ejemplo" +#: ../settings/security/third-party/gitlab.rst:2 +msgid "Gitlab" +msgstr "" -#: ../system/core-workflows/learn-by-example.rst:4 +#: ../settings/security/third-party/gitlab.rst:4 msgid "" -"This page provides some basic examples for Core Workflows. Of course you can " -"build much more complex workflows if needed." +"It is possible to create a quick login for your helpdesk via Gitlab. To " +"activate the quick login you need to enable OAuth for Gitlab." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:7 -msgid "" -"To learn about Core Workflows in detail, first go to :doc:`how-do-they-work`." +#: ../settings/security/third-party/gitlab.rst:8 +msgid "Register Gitlab App" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:10 -#, fuzzy -msgid "Group Based Examples" -msgstr "Ejemplo" +#: ../settings/security/third-party/gitlab.rst:10 +msgid "To register an app in Gitlab open your profile and select applications." +msgstr "" -#: ../system/core-workflows/learn-by-example.rst:12 +#: ../settings/security/third-party/gitlab.rst:12 msgid "" -"All following workflows have the same base configurations. The workflow may " -"not use them all." +"As callback URL enter \"https://zammad-fqdn/auth/gitlab/callback\" where " +"zammad-fqdn has to be replaced with your Zammad FQDN" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:15 -#, fuzzy -msgid "Groups:" -msgstr "grupo" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Register OAuth app on gitlab instance" +msgstr "" -#: ../system/core-workflows/learn-by-example.rst:20 -msgid "Attributes:" +#: ../settings/security/third-party/gitlab.rst:18 +msgid "Just select *read_user* under scopes as in the screenshot and save it." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:22 -msgid "Category (Single tree selection field, not mandatory, agents only)" +#: ../settings/security/third-party/gitlab.rst:21 +msgid "Configure Zammad as Gitlab App" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:23 +#: ../settings/security/third-party/gitlab.rst:23 msgid "" -"Approved (Boolean field, not mandatory, not shown, ``false`` as default)" +"Enter the \"APP ID\" and the \"APP SECRET\" from the Gitlab OAUTH " +"Applications Dashboard and your Gitlab-URL in the \"SITE\" field." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:24 -msgid "Operating System (Text field, not mandatory, not shown)" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab config in Zammad admin interface" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:25 -msgid "Software used (Single selection field, not mandatory, not shown)" +#: ../settings/security/third-party/gitlab.rst:30 +msgid "" +"After you configured the Gitlab credentials and activated the login method, " +"you should see a new icon on the login page." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:68 -msgid "Group specific values and fields" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab logo on login page" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:28 +#: ../settings/security/third-party/gitlab.rst:36 msgid "" -"This workflow set depends on the category field. It reduces the available " -"set of values based on the group selected." +"If you click on the icon you will be redirected to Gitlab and see something " +"similar to this:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:33 -msgid "Workflow 2nd Level group" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab oauth page" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:35 +#: ../settings/security/third-party/google.rst:4 msgid "" -"This reduces the category options to ``2nd Level/*``, ``Internal/*`` and " -"``Others``. It also sets further required fields to mandatory and visible." +"With some easy and fast steps, you can enable Zammad to authenticate your " +"users via Google." +msgstr "" + +#: ../settings/security/third-party/google.rst:8 +msgid "Register a Google App" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for 2nd level" +#: ../settings/security/third-party/google.rst:10 +msgid "" +"First of all, we need to create a new project - you can skip this step if " +"you already have one." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:43 -msgid "Workflow Support group" +#: ../settings/security/third-party/google.rst:15 +msgid "" +"Use this link to create a new project: https://console.cloud.google.com/" +"projectcreate" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:45 +#: ../settings/security/third-party/google.rst:18 msgid "" -"This reduces the category options to ``Support/*``, ``Internal/*`` and " -"``Others``. It also sets further required fields to visible." +"Now expand the menu, expand \"APIs & Services\" and select \"Credentials\". " +"Go to the tab \"OAuth consent screen\" first and ensure to fill in the " +"requested information - without doing so you can't create credentials!" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for support" +#: ../settings/security/third-party/google.rst:None +msgid "Creating a consent screen" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:53 -msgid "Workflow Sales group" +#: ../settings/security/third-party/google.rst:25 +msgid "" +"After filling in and saving the consent screen information, you can go to " +"the \"Credentials\" tab and create new \"OAuth client ID\"-Credentials." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:55 +#: ../settings/security/third-party/google.rst:28 msgid "" -"This reduces the category options to ``Sales/*``, ``Internal/*`` and " -"``Others``." +"Fill in the necessary information as follows and replace ``zammad_host`` " +"with your FQDN:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for sales" +#: ../settings/security/third-party/google.rst:31 +msgid "**Application type** ``[x] Web application``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:68 -#: ../system/integrations/slack.rst:88 -msgid "The Result" +#: ../settings/security/third-party/google.rst:34 +msgid "**Authorized JavaScript origins** ``https://zammad_host/``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:63 +#: ../settings/security/third-party/google.rst:37 msgid "" -"This is what the agent would experience with the above workflows in place." +"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" +"callback``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 +#: ../settings/security/third-party/google.rst:None +msgid "Adding a new OAuth client ID" +msgstr "" + +#: ../settings/security/third-party/google.rst:43 msgid "" -"Workflow shows objects and limits options based on selections on the group" +"After creating the credentials, go to your Zammad installation and navigate " +"to \"Admin > Security > Third Party Applications\" > Google. Enter your " +"Client ID and Client secret here." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:90 -msgid "Approval process" +#: ../settings/security/third-party/google.rst:None +msgid "Zammad" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:71 -msgid "" -"In this case ``approved`` is visible to agents by default. For this " -"workflow, an additional role ``Approval person`` is required (no further " -"permissions)." +#: ../settings/security/third-party/google.rst:50 +msgid "After submitting, the login via Google can be used." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that restricts an approval attribute to specific roles" +#: ../settings/security/third-party/microsoft.rst:2 +msgid "Microsoft" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:81 +#: ../settings/security/third-party/microsoft.rst:4 msgid "" -"This workflow may work best in combination with a :doc:`trigger ` but technically, this is not required." +"Zammad's Microsoft connection allows your users with Microsoft accounts to " +"login. This works for Azure users as well and can be an alternative to :doc:" +"`/system/integrations/ldap/index`." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:84 +#: ../settings/security/third-party/microsoft.rst:10 msgid "" -"Select fields may be a better approach because they allow more values than " -"just a simple ``true`` or ``false``." +"This documentation part does not cover our :doc:`📧 Microsoft 365 email " +"channel `." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "" -"Workflow fixes possible values of \"Approved ?\" to a specific selection " -"depending on the users role" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screenshot showing Microsoft login button on Zammad login screen." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:103 -msgid "State dependent mandatory fields" +#: ../settings/security/third-party/microsoft.rst:30 +#: ../settings/security/third-party/microsoft.rst:53 +msgid "Supported account types:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:93 +#: ../settings/security/third-party/microsoft.rst:22 msgid "" -"This workflow sets ``Category`` to mandatory if the agent wants to set the " -"states ``closed`` or ``pending close`` to enforce categorization." +"Please note that Zammad only supports these account types (App dependent):" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that sets fields to mandatory on specific states" +#: ../settings/security/third-party/microsoft.rst:35 +msgid "Avatars of signing in users:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 +#: ../settings/security/third-party/microsoft.rst:33 msgid "" -"Workflow sets category field to mandatory upon choosing closed or pending " -"close as state" +"Zammad currently ignores user avatars. If the user is registered with e.g. " +"Gravatar, Zammad will fetch the avatar from there if enabled. See :doc:" +"`Zammad Image Service ` for more." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:106 -msgid "Manual Ticket Handover Process" +#: ../settings/security/third-party/microsoft.rst:38 +msgid "Step 1 - Register a Microsoft App for Zammad" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:108 -msgid "This example covers the handover of a ticket from one agent to another:" +#: ../settings/security/third-party/microsoft.rst:40 +msgid "" +"Login to the `Microsoft Azure Portal `_ and " +"navigate to App registrations to create a new app. Provide the requested " +"information as follows and register your app." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:110 -msgid "" -"When the ticket owner is modified, a new text field (\"Handover\") shows up " -"for a comment" +#: ../settings/security/third-party/microsoft.rst:46 +msgid "Name:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:112 +#: ../settings/security/third-party/microsoft.rst:45 msgid "" -"This may only be visible when the owner is changed, therefore it has to be " -"hidden in general" +"Any meaningful name fitting, this name will be displayed to users trying to " +"authenticate with this app." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:114 -msgid "The input in this handover text field is mandatory" +#: ../settings/security/third-party/microsoft.rst:49 +msgid "Choose one of the above mentioned account types (see Limitations)." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:115 +#: ../settings/security/third-party/microsoft.rst:51 msgid "" -"After submitting changes, the value of the handover field must be added as " -"an note to the ticket (via trigger)" -msgstr "" - -#: ../system/core-workflows/learn-by-example.rst:121 -msgid "Hiding handover field" +"The correct account type depends on your use case. If you want to use the " +"authentication internal only, choose the first option. If you're unsure, use " +"the \"Help me choose...\" link." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Hiding the handover field in core workflows" +#: ../settings/security/third-party/microsoft.rst:58 +msgid "Redirect URI (optional):" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:126 -msgid "Showing handover field and setting it to mandatory" +#: ../settings/security/third-party/microsoft.rst:56 +msgid "" +"Select web and provide your callback URL. The callback URL looks like this: " +"``https://zammad.domain.tld/auth/microsoft_office365/callback``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Showing the handover field and set it as mandatory" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to register a Microsoft app" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:131 -msgid "Trigger writing handover input to a new article" +#: ../settings/security/third-party/microsoft.rst:71 +msgid "Within **API permissions** add the following permissions:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Write handover content to a new article" +#: ../settings/security/third-party/microsoft.rst:69 +msgid "``User.Read``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:133 -msgid "" -"As a result, the ticket includes an article of the type note which includes " -"the predefined text and the handover comment." +#: ../settings/security/third-party/microsoft.rst:71 +msgid "Contacts" msgstr "" -#: ../system/core-workflows/limitations.rst:6 -msgid "Core Workflows do not replace Triggers" +#: ../settings/security/third-party/microsoft.rst:71 +msgid "``Contacts.Read``" msgstr "" -#: ../system/core-workflows/limitations.rst:5 +#: ../settings/security/third-party/microsoft.rst:73 msgid "" -"Workflows manipulate the behavior of fields. However, they do not set values " -"in fields because of actions." +"You can find these permissions within *Microsoft Graph → Delegated " +"permissions*." msgstr "" -#: ../system/core-workflows/limitations.rst:16 -msgid "API calls are only partly affected" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to add required API permissions" msgstr "" -#: ../system/core-workflows/limitations.rst:9 +#: ../settings/security/third-party/microsoft.rst:80 msgid "" -"Some options affect UI only and thus do not restrict responses and calls." +"Within **Certificates & secrets** create a new client secret. Note down the " +"returned secret **value** for later. **Do not** use the secret ID!" msgstr "" -#: ../system/core-workflows/limitations.rst:11 -msgid "This affects the following actions:" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to create a new app secret" msgstr "" -#: ../system/core-workflows/limitations.rst:13 -msgid "select" +#: ../settings/security/third-party/microsoft.rst:88 +msgid "" +"From **Overview** copy your apps *Application (client) ID*. If you're using " +"a single tenant app, please also copy *Directory (tenant) ID*. You now have " +"all required information for Zammad." msgstr "" -#: ../system/core-workflows/limitations.rst:14 -msgid "auto select" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to retreive application client and tenant IDs" msgstr "" -#: ../system/core-workflows/limitations.rst:15 -msgid "show" +#: ../settings/security/third-party/microsoft.rst:98 +msgid "Step 2 - Add App Credentials to Zammad" msgstr "" -#: ../system/core-workflows/limitations.rst:16 -msgid "hide" +#: ../settings/security/third-party/microsoft.rst:100 +msgid "" +"Navigate to Security > Third-party Applications (Tab) within Zammad's admin " +"settings. Scroll down to the section *Authentication via Microsoft* and fill " +"in the required information." msgstr "" -#: ../system/core-workflows/limitations.rst:25 -msgid "Some fields stay unavailable to customers" +#: ../settings/security/third-party/microsoft.rst:105 +msgid "App ID:" msgstr "" -#: ../system/core-workflows/limitations.rst:19 -msgid "" -"For technical and security reasons, some default fields (the pale ones you " -"can't edit) stay unavailable for display and usage on customer permissions." +#: ../settings/security/third-party/microsoft.rst:105 +msgid "This is your *Application (client) ID*." msgstr "" -#: ../system/core-workflows/limitations.rst:23 -msgid "" -"If you require your customers to change e.g. priorities, please consider " -"using workarounds via :doc:`/system/objects` and :doc:`/manage/trigger`." +#: ../settings/security/third-party/microsoft.rst:108 +msgid "App secret:" msgstr "" -#: ../system/core-workflows/limitations.rst:29 -msgid "Ticket title changes not supported in edit mask" +#: ../settings/security/third-party/microsoft.rst:108 +msgid "This is your *client secret* (value)." msgstr "" -#: ../system/core-workflows/limitations.rst:28 -msgid "" -"It is currently not possible to perform changes of the ticket title in the " -"edit mask (e.g. renaming, set to read-only)." +#: ../settings/security/third-party/microsoft.rst:113 +msgid "App Tenant ID:" msgstr "" -#: ../system/core-workflows/limitations.rst:37 -msgid "What is out of scope of Core Workflows?" +#: ../settings/security/third-party/microsoft.rst:111 +msgid "" +"**optional** only required for apps that use account type *Accounts in this " +"organizational directory only (Default Directory only - Single tenant).*" msgstr "" -#: ../system/core-workflows/limitations.rst:32 +#: ../settings/security/third-party/microsoft.rst:115 msgid "" -"There are some things that would count as workflow but are either done via :" -"doc:`/manage/trigger` or :doc:`/manage/scheduler`." +"Apply your settings by pressing submit and activate *Authentication via " +"Microsoft*." msgstr "" -#: ../system/core-workflows/limitations.rst:35 -msgid "Such as (but not limited to):" +#: ../settings/security/third-party/microsoft.rst:None +msgid "" +"Screencast showing how to add app credentials and activating the\n" +"authentication method" msgstr "" -#: ../system/core-workflows/limitations.rst:37 -msgid "up- or downgrade permissions of users" +#: ../settings/security/third-party/saml.rst:2 +msgid "SAML" msgstr "" -#: ../system/core-workflows/limitations.rst:38 -msgid "affecting article creation or listing" +#: ../settings/security/third-party/saml.rst:4 +msgid "" +"Connect your SAML (Security Assertion Markup Language) identity provider as " +"a single sign-on (SSO) method." msgstr "" -#: ../system/data-privacy.rst:2 -msgid "Data Privacy" +#: ../settings/security/third-party/saml.rst:7 +msgid "" +"SAML is an open standard for SSO authentication (among other things). Sign-" +"ins are shared across multiple **service providers** and managed by a " +"central **identity provider** (IdP)." msgstr "" -#: ../system/data-privacy.rst:4 +#: ../settings/security/third-party/saml.rst:11 msgid "" -"For compliance with GDPR and other data privacy laws, you may wish to " -"**permanently delete users from the system**, along with **all of their " -"associated tickets**." +"In this case, the service provider is Zammad, and the IdP is a software " +"service that you either host or subscribe to (*e.g.,* `Keycloak `_, `Redhat SSO Server `_, `ADFS `_, or `Okta `_)." msgstr "" -#: ../system/data-privacy.rst:8 +#: ../settings/security/third-party/saml.rst:18 msgid "" -"You can create manual deletion tasks or even automated deletion tasks for " -"tickets and users based on custom conditions via :doc:`scheduler `!" +"This guide assumes you are already using SAML within your organization (i." +"e., that your IdP is fully set up)." msgstr "" -#: ../system/data-privacy.rst:12 +#: ../settings/security/third-party/saml.rst:21 msgid "" -"Access to this panel requires ``admin.data_privacy`` permissions (introduced " -"in Zammad 3.5)." +"Please note: Our instructions are based on connecting Zammad with Keycloak." msgstr "" -#: ../system/data-privacy.rst:15 -msgid "" -"On older systems that have not been updated yet, customers can also be :docs:" -"`deleted via the Zammad console `." +#: ../settings/security/third-party/saml.rst:25 +msgid "Step 1: Configure Your IdP" msgstr "" -#: ../system/data-privacy.rst:22 -msgid "User deletion dialog in the Data Privacy panel" +#: ../settings/security/third-party/saml.rst:28 +msgid "Add Zammad as a Client/App" msgstr "" -#: ../system/data-privacy.rst:22 +#: ../settings/security/third-party/saml.rst:30 msgid "" -"The user deletion dialog lists some of the tickets that will be removed from " -"the system along with the user." +"Import Zammad into your IdP using the XML configuration found at ``https://" +"your.zammad.domain/auth/saml/metadata``." msgstr "" -#: ../system/data-privacy.rst:27 -#, fuzzy -msgid "Deleting Users via GUI" -msgstr "Verificación de correo electrónico" +#: ../settings/security/third-party/saml.rst:33 +msgid "" +"If your IdP doesn't support XML import, you will have to configure Zammad as " +"a new client/app manually using the above XML metadata file for reference." +msgstr "" -#: ../system/data-privacy.rst:29 -msgid "🔥 **All deletions are FINAL!**" +#: ../settings/security/third-party/saml.rst:36 +msgid "For instance, when you see this tag:" msgstr "" -#: ../system/data-privacy.rst:31 -msgid "Once you click “Delete”, the action cannot be canceled or undone." +#: ../settings/security/third-party/saml.rst:42 +msgid "" +"Set the **Assertion Consumer Service Binding URL** (sometimes also listed as " +"**Valid Redirect URIs**) to ``http://your.zammad.domain/auth/saml/callback``." msgstr "" -#: ../system/data-privacy.rst:33 +#: ../settings/security/third-party/saml.rst:47 +msgid "Set Up User Attribute Mapping" +msgstr "" + +#: ../settings/security/third-party/saml.rst:49 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." +"Zammad requests the following user attributes (or “properties”) from the IdP:" msgstr "" -#: ../system/data-privacy.rst:36 -msgid "**The following records cannot be deleted:**" +#: ../settings/security/third-party/saml.rst:51 +msgid "Email address (``email``)" msgstr "" -#: ../system/data-privacy.rst:38 -msgid "your own account" +#: ../settings/security/third-party/saml.rst:52 +msgid "Full name (``name``)" msgstr "" -#: ../system/data-privacy.rst:39 -msgid "the system's last remaining administrator account" +#: ../settings/security/third-party/saml.rst:53 +msgid "Given name (``first_name``)" msgstr "" -#: ../system/data-privacy.rst:42 -msgid "Step 1: Find a User / Confirm Deletion" +#: ../settings/security/third-party/saml.rst:54 +msgid "Family name (``last_name``)" msgstr "" -#: ../system/data-privacy.rst:44 -msgid "There are three ways to access the user deletion dialog:" +#: ../settings/security/third-party/saml.rst:56 +msgid "" +"You may need to set up “mappers” (or “mappings”) to tell your IdP how user " +"attributes in SAML correspond to those in Zammad. For a more detailed " +"breakdown, refer to the XML metadata file referenced in the previous section." msgstr "" -#: ../system/data-privacy.rst:51 -msgid "**from the user's profile**" +#: ../settings/security/third-party/saml.rst:62 +msgid "Per-IdP Instructions" msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Accessing the user deletion dialog in a user profile" +#: ../settings/security/third-party/saml.rst:102 +msgid "Keycloak" msgstr "" -#: ../system/data-privacy.rst:51 -msgid "Click **Action > Delete**." +#: ../settings/security/third-party/saml.rst:65 +msgid "" +"**To add Zammad as a client,** save the XML configuration to disk (``https://" +"your.zammad.domain/auth/saml/metadata``) and use **Clients > Clients list > " +"Import client** in the Keycloak admin panel." msgstr "" -#: ../system/data-privacy.rst:58 -msgid "**in the “Manage > Users” Admin Panel**" +#: ../settings/security/third-party/saml.rst:70 +msgid "" +"To help Zammad **match its own user accounts to Keycloak users**, create a " +"user attribute (or “property”) mapper. In **Clients list**, click on your " +"newly created Client ID, choose the tab **Client scopes** and click on the " +"link which refers to your Zammad instance. Choose **Add mapper > By " +"configuration > User Property** and create a mapper with the following " +"entries:" msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Accessing the user deletion dialog under “Users” in the Admin Panel" +#: ../settings/security/third-party/saml.rst:78 +msgid "**Name**" msgstr "" -#: ../system/data-privacy.rst:58 -msgid "Use the **⋮ Actions** menu for the target user." +#: ../settings/security/third-party/saml.rst:80 +msgid "**Mapper Type**" msgstr "" -#: ../system/data-privacy.rst:66 ../system/data-privacy.rst:104 -msgid "**in the “System > Data Privacy” Admin Panel**" +#: ../settings/security/third-party/saml.rst:81 +msgid "``User Property``" msgstr "" -#: ../system/data-privacy.rst:0 -msgid "" -"Accessing the user deletion dialog under “Data Privacy” in the Admin Panel" +#: ../settings/security/third-party/saml.rst:82 +msgid "**Property**" msgstr "" -#: ../system/data-privacy.rst:65 -msgid "" -"Use the **New Deletion Task** button. Search for users by name or email " -"address." +#: ../settings/security/third-party/saml.rst:83 +msgid "``emailAddress``" msgstr "" -#: ../system/data-privacy.rst:79 -msgid "**Delete organizations**" +#: ../settings/security/third-party/saml.rst:84 +msgid "**SAML Attribute Name**" msgstr "" -#: ../system/data-privacy.rst:69 -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:" +#: ../settings/security/third-party/saml.rst:86 +msgid "**SAML Attribute NameFormat**" msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Deleting an organization via the user deletion dialog" +#: ../settings/security/third-party/saml.rst:87 +msgid "``basic``" msgstr "" -#: ../system/data-privacy.rst:78 +#: ../settings/security/third-party/saml.rst:89 msgid "" -"If this option does not appear, make sure there are no pending deletion " -"tasks for other customers from this organization." +"In the example above, we're telling Zammad that whenever it receives a SAML " +"login request, it should take the ``email`` property from Keycloak, look for " +"a Zammad user with the same ``email`` attribute, and create a new session " +"for that user." msgstr "" -#: ../system/data-privacy.rst:82 -msgid "Step 2: Monitor Deletion Job Status" +#: ../settings/security/third-party/saml.rst:95 +msgid "" +"If your Keycloak users' email addresses are stored on another property (*e." +"g.,* ``username``), adjust accordingly." msgstr "" -#: ../system/data-privacy.rst:84 +#: ../settings/security/third-party/saml.rst:98 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:" +"Back in **Settings**, enter the Client ID (``https://your.zammad.domain/auth/" +"saml/metadata``) in the field **Master SAML Processing URL**." msgstr "" -#: ../system/data-privacy.rst:98 -msgid "**in the Activity Stream**" +#: ../settings/security/third-party/saml.rst:101 +msgid "You also need to enable **Sign assertions**." msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Activity Stream showing data privacy tasks" +#: ../settings/security/third-party/saml.rst:105 +msgid "Step 2: Configure Zammad" msgstr "" -#: ../system/data-privacy.rst:94 +#: ../settings/security/third-party/saml.rst:107 msgid "" -"For each deleted user, the Activity Stream will be updated twice—once when " -"the task is created, and once when it's complete." +"Enable SAML and enter your IdP's details in the Admin Panel under **Settings " +"> Security > Third Party Applications > Authentication via SAML**:" msgstr "" -#: ../system/data-privacy.rst:97 -msgid "" -"These notifications are only visible to users with ``admin.data_privacy`` " -"permissions." +#: ../settings/security/third-party/saml.rst:None +msgid "Example configuration of SAML part 1" msgstr "" -#: ../system/data-privacy.rst:0 -msgid "" -"The task list within Data Privacy shows removals being in progress and " -"completed." +#: ../settings/security/third-party/saml.rst:119 +msgid "Display name" msgstr "" -#: ../system/data-privacy.rst:107 -msgid "Frequently Asked Questions" +#: ../settings/security/third-party/saml.rst:116 +msgid "" +"Allows you to define a custom button name for SAML. This helps your users to " +"understand better what the button on the login page does." msgstr "" -#: ../system/data-privacy.rst:121 -msgid "What happens if I receive an email from a deleted customer?" +#: ../settings/security/third-party/saml.rst:119 +msgid "Defaults to ``SAML``." msgstr "" -#: ../system/data-privacy.rst:110 -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." +#: ../settings/security/third-party/saml.rst:123 +msgid "IDP SSO target URL" msgstr "" -#: ../system/data-privacy.rst:115 +#: ../settings/security/third-party/saml.rst:122 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**." +"This is the target URL Zammad shall redirect to when the user presses the " +"SAML button. For Keycloak, this needs to look like https://your.domain/" +"realms/your-realm/protocol/saml" msgstr "" -#: ../system/data-privacy.rst:130 -msgid "What about user information stored in internal notes or other messages?" +#: ../settings/security/third-party/saml.rst:127 +msgid "IDP single logout target URL" msgstr "" -#: ../system/data-privacy.rst:124 +#: ../settings/security/third-party/saml.rst:126 msgid "" -"The deletion process removes **user accounts and associated tickets only**." +"This is the URL to which the single logout request and response should be " +"sent." msgstr "" -#: ../system/data-privacy.rst:126 +#: ../settings/security/third-party/saml.rst:131 +#, fuzzy +msgid "IDP certificate" +msgstr "Verificación de correo electrónico" + +#: ../settings/security/third-party/saml.rst:130 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." +"The public certificate of your IDP for Zammad to verify during the callback " +"phase." msgstr "" -#: ../system/data-privacy.rst:137 -msgid "I deleted an user and can still see a message they sent!" +#: ../settings/security/third-party/saml.rst:145 +msgid "IDP certificate fingerprint" msgstr "" -#: ../system/data-privacy.rst:133 +#: ../settings/security/third-party/saml.rst:134 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." +"The fingerprint of your IDPs public certificate to verify during callback " +"phase." msgstr "" -#: ../system/data-privacy.rst:141 -msgid "I removed a customer, now my reporting is off!" +#: ../settings/security/third-party/saml.rst:137 +msgid "🔏 **For the IdP certificate / certificate fingerprint:**" msgstr "" -#: ../system/data-privacy.rst:140 +#: ../settings/security/third-party/saml.rst:139 msgid "" -"When removing users and their tickets, all references are removed. This also " -"affects e.g. Reporting - these information are lost." -msgstr "" - -#: ../system/data-privacy.rst:145 -msgid "How long does Zammad store created tasks?" +"Provide **only one or the other**—do not provide both! (Between the two, we " +"recommend the signing certificate itself: fingerprints use SHA-1, which `has " +"been broken for a while now `_.)" msgstr "" -#: ../system/data-privacy.rst:144 +#: ../settings/security/third-party/saml.rst:144 msgid "" -"Please see the on-premise data section of the :docs:`data privacy ` chapter." +"**Keycloak users:** Find your certificate in the Keycloak admin panel under " +"**Realm Settings > Keys > Algorithm: RS256 > Certificate**." msgstr "" -#: ../system/data-privacy.rst:150 -msgid "What about re-assigned tickets? I want to delete them, too." +#: ../settings/security/third-party/saml.rst:151 +msgid "Name identifier format" msgstr "" -#: ../system/data-privacy.rst:148 +#: ../settings/security/third-party/saml.rst:148 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." +"This is the unique identifiers field type. Usually it should be ``urn:oasis:" +"names:tc:SAML:1.1:nameid-format:emailAddress``." msgstr "" -#: ../system/data-privacy.rst:154 -msgid "Why are there so many deletion task entries, I didn't create them!" +#: ../settings/security/third-party/saml.rst:151 +msgid "Zammad **expects an email address as unique identifier**!" msgstr "" -#: ../system/data-privacy.rst:153 -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." +#: ../settings/security/third-party/saml.rst:155 +msgid "UID attribute name" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:2 -msgid "Admin Panel Reference" +#: ../settings/security/third-party/saml.rst:154 +msgid "" +"Here you can define an attribute that uniquely identifies the user. If " +"unset, the name identifier returned by the IDP is used." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:None -msgid "Screenshot of Checkmk settings overview" +#: ../settings/security/third-party/saml.rst:None +msgid "Example configuration of SAML part 2" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:12 +#: ../settings/security/third-party/saml.rst:163 msgid "" -"Which :doc:`group ` should Checkmk tickets be assigned " -"to as a default (*i.e.,* when none is specified)?" +"Decide if the certificate for the connection to the IdP service has to be " +"verified or not (default: ``yes``)." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:15 -msgid "(Applies to :ref:`API alerts ` only.)" +#: ../settings/security/third-party/saml.rst:169 +msgid "Signing & Encrypting" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:21 -msgid "Auto close" +#: ../settings/security/third-party/saml.rst:169 +msgid "" +"Define if you want to sign, encrypt, do both or nothing for the requests." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:18 +#: ../settings/security/third-party/saml.rst:179 +msgid "Certificate (PEM)" +msgstr "" + +#: ../settings/security/third-party/saml.rst:172 msgid "" -"Should Zammad automatically close tickets if a service has recovered on its " -"own?" +"Paste the public certificate of your Zammad SAML client, if you want to " +"encrypt the requests." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:21 -msgid "(Agents will receive notifications for such closures as appropriate.)" +#: ../settings/security/third-party/saml.rst:175 +#, fuzzy +msgid "Make sure the certificate is:" +msgstr "Verificación de correo electrónico" + +#: ../settings/security/third-party/saml.rst:177 +msgid "already valid and not yet expired" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:30 -msgid "Auto-close state" +#: ../settings/security/third-party/saml.rst:178 +#, fuzzy +msgid "no CA certificate" +msgstr "Verificación de correo electrónico" + +#: ../settings/security/third-party/saml.rst:179 +msgid "valid for signing and encrypting" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:24 -msgid "What ticket state should be applied when “auto-closing” a ticket?" +#: ../settings/security/third-party/saml.rst:185 +msgid "Private key (PEM)" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:26 +#: ../settings/security/third-party/saml.rst:182 msgid "" -"You can choose from the seven built-in ticket states. If these states aren't " -"enough for you, you can :ref:`define a new ticket state ` for this purpose as well. This can be useful for tracking " -"tickets with :doc:`reports `, for example." +"Paste the private key of your Zammad SAML client here, if you want to sign " +"the requests." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:35 -#: ../system/integrations/cti/includes/recent-logs.include.rst:2 -#: ../system/integrations/ldap/index.rst:74 -#: ../system/integrations/pgp/index.rst:106 -msgid "Recent Logs" +#: ../settings/security/third-party/saml.rst:185 +msgid "Make sure the key is an RSA key with a length of at least 2048 bits." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:None -msgid "Screenshot of Checkmk \"Recent Logs\" section" +#: ../settings/security/third-party/saml.rst:188 +msgid "Private key secret" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:41 -msgid "" -"If you're having trouble getting Zammad and Checkmk to play nicely together, " -"this section can help you troubleshoot." +#: ../settings/security/third-party/saml.rst:188 +msgid "If your private key is secured with a secret, you can provide it here." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:44 -msgid "" -"It contains a record of the fifty most recent transactions that Zammad knows " -"about, including each one's request/response details and return status." +#: ../settings/security/third-party/saml.rst:192 +msgid "Your callback URL" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:2 -msgid "API Reference" +#: ../settings/security/third-party/saml.rst:191 +msgid "" +"This URL is needed for your IdP configuration so it knows where to redirect " +"to after successful authentication." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:4 +#: ../settings/security/third-party/saml.rst:194 msgid "" -"For most users, :ref:`the sample scripts from the Setup Guide ` will do the job just fine. But if you want more fine-grained control" -"—for instance, to create high- and low-priority tickets for different types " -"of system events—then you'll have to customize the data those scripts send " -"to Zammad." +"After saving your input by clicking on the \"Submit\" button, Zammad " +"verifies the provided keys/certificates (e.g. if they are valid for signing/" +"encrypting and if they aren't expired)." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:15 +#: ../settings/security/third-party/saml.rst:199 msgid "" -"This custom script will automatically set all tickets it creates to **high " -"priority** and **assign them to charlie@chrispresso.com**." +"See :ref:`automatic account linking ` for details " +"on how to link existing Zammad accounts to IdP accounts." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:32 -msgid "How Does it Work?" +#: ../settings/security/third-party/saml.rst:205 +#, fuzzy +msgid "Automatic account linking doesn't work" +msgstr "Notificación automática de vinculación de cuentas" + +#: ../settings/security/third-party/saml.rst:206 +msgid "" +"Have you double-checked your IdP's user attribute mapping configuration?" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:34 +#: ../settings/security/third-party/twitter.rst:4 msgid "" -"There are two kinds of data you can pass to the API, both in the form of key-" -"value pairs:" +"It is possible to create a quick login for your helpdesk via Twitter. To do " +"so, you need to follow these steps:" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:44 -msgid "Checkmk parameters" +#: ../settings/security/third-party/twitter.rst:8 +msgid "Register Twitter App" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:38 -msgid "" -"are required, and make up the **contents** of the resulting tickets/" -"articles. They also determine whether an event creates a new ticket or " -"updates/closes an existing one." +#: ../settings/security/third-party/twitter.rst:10 +msgid "Go to https://dev.twitter.com/apps and login with your account." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:42 -msgid "" -"These are the only values used in the sample scripts. **Use them as-is**; " -"technically, they can be customized, but it's hard to imagine a good reason " -"for it." +#: ../settings/security/third-party/twitter.rst:15 +msgid "Click on \"Create App\"" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:52 -msgid "Ticket attributes" +#: ../settings/security/third-party/twitter.rst:None +msgid "new app page" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:47 +#: ../settings/security/third-party/twitter.rst:20 msgid "" -"are optional, and can be used to **adjust settings** on newly created " -"tickets (*e.g.,* set the owner, group, priority, or state)." +"Enter app settings. As \"Callback URL\" you need to enter ``https://" +"zammad_host/api/v1/external_credentials/twitter/callback``. You need to " +"replace ``zammad_host`` with the domain of your Zammad system." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:50 +#: ../settings/security/third-party/twitter.rst:24 msgid "" -"If you want to customize your Checkmk alert script, do it with these. Simply " -"add an extra “form” option for each one (``-F \"key=value\"``) to your " -"script's ``curl`` command line, as in the example above." +"After the app has been created, update the application icon and organization " +"attributes." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:54 -msgid "💡 **It's just an API endpoint!**" +#: ../settings/security/third-party/twitter.rst:None +msgid "set permissions to receive and send direct messages" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:56 +#: ../settings/security/third-party/twitter.rst:30 msgid "" -"When using Checkmk integration, messages need to be formatted in a certain " -"way, but that *doesn't mean the messages actually have to come from Checkmk*." +"Next we need to set ``read, write and access direct messages`` permissions " +"for the app." +msgstr "" + +#: ../settings/security/third-party/twitter.rst:None +msgid "click on Keys & Access Token, note them" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:59 +#: ../settings/security/third-party/twitter.rst:36 msgid "" -"If you use another monitoring tool that's not officially supported by " -"Zammad, there's probably a way to make it work with your Checkmk callback " -"URL." +"Go to \"Keys and Access Token\" tab and note the \"Consumer Key\" and " +"\"Consumer Secret\"." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:63 -msgid "Checkmk Parameters" +#: ../settings/security/third-party/twitter.rst:40 +msgid "Configure Zammad as Twitter App" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:65 +#: ../settings/security/third-party/twitter.rst:42 msgid "" -"When a notification is received, Zammad creates a new article containing the " -"details of the event that triggered it:" +"Go to \"Admin > Security > Twitter > Third Party Applications > Twitter\" " +"Section." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:None -msgid "Checkmk article body" +#: ../settings/security/third-party/twitter.rst:None +msgid "Admin > Security > Third Party Applications" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:72 +#: ../settings/security/third-party/twitter.rst:48 msgid "" -"These details come from the fields listed below, which correspond to " -"parameters provided by Checkmk (``$NOTIFY_*``)." +"Fill in the \"Twitter Key\" and the \"Twitter Secret\" and click the " +"\"Submit\" button." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:75 -msgid "**Required fields are marked with an asterisk (\\*).**" +#: ../settings/security/third-party/twitter.rst:51 +msgid "" +"Now you can link accounts via \"Avatar > Profile > Link Accounts\" or login " +"via Zammad login page." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:79 -msgid "event_id\\*" +#: ../settings/security/two-factor.rst:11 +msgid "Two-factor Authentication Methods" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:78 +#: ../settings/security/two-factor.rst:2 +msgid "Two-Factor Authentication" +msgstr "" + +#: ../settings/security/two-factor.rst:4 msgid "" -"A unique ID for the system event. (``$NOTIFY_SERVICEPROBLEMID`` / " -"``$NOTIFY_HOSTPROBLEMID``)" +"Two-factor authentication (2FA) enhances the security of Zammad accounts by " +"adding an extra layer of verification beyond a password. It requires users " +"to provide two different types of authentication factors, typically " +"something they know (like a password) and something they possess (like a " +"mobile device or a security token), to ensure that only authorized " +"individuals can access the account." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:86 -msgid "host\\*" +#: ../settings/security/two-factor.rst:19 +msgid "Enable Recovery Codes" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:82 +#: ../settings/security/two-factor.rst:21 msgid "" -"The hostname of the system that the event originated from. " -"(``$NOTIFY_HOSTNAME``)" +"Recovery codes are one-time use security codes that can be used by the user " +"if they lose access to their other two-factor authentication methods. They " +"cannot be used on their own, they can only be activated if at least one two-" +"factor authentication method is enabled." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:85 -msgid "" -"Used to determine if a new event belongs to an existing ticket. Also used in " -"the subject line of the resulting article (“ is ”)." +#: ../settings/security/two-factor.rst:None +msgid "Enable Recovery Codes Setting" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:96 -msgid "service" +#: ../settings/security/two-factor.rst:30 +msgid "" +"Recovery codes can only be used as a backup method. If enabled, they will be " +"automatically generated for the user once they set up their initial two-" +"factor authentication method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:89 +#: ../settings/security/two-factor.rst:34 msgid "" -"The name of the service that the event originated from. " -"(``$NOTIFY_SERVICEDESC``)" +"The user will be asked to print out or save the generated recovery codes in " +"a safe place. Once used, a recovery code cannot be reused." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:92 -msgid "Used to determine if a new event belongs to an existing ticket." +#: ../settings/security/two-factor.rst:37 +msgid "" +"Users will also have an option to regenerate their recovery codes at any " +"time, which invalidates already existing recovery codes and provides them " +"with a list of fresh codes." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:94 -#: ../system/integrations/checkmk/api-reference.rst:110 -msgid "Displayed as ``-`` when omitted." +#: ../settings/security/two-factor.rst:41 +msgid "" +"After you enable this setting, when the user completes a setup of their " +"initial two-factor authentication method, they will be presented with a list " +"of recovery codes and instructed to save them for later use." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:104 -msgid "state\\*" +#: ../settings/security/two-factor.rst:None +msgid "Recovery Codes Generation Modal Dialog" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:99 -msgid "" -"The current state of the service or host in question. " -"(``$NOTIFY_SERVICESTATE`` / ``$NOTIFY_HOSTSTATE``)" +#: ../settings/security/two-factor.rst:50 +msgid "Enforce the Set Up of the Two-Factor Authentication" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:102 +#: ../settings/security/two-factor.rst:52 msgid "" -"Used to detect when a ticket should be auto-closed (*i.e.,* on ``OK``/" -"``UP``). Also used in the subject line of the resulting article (“ is " -"”)." +"In case you wish to require your users to set up at least one two-factor " +"authentication method for their account, you can do this by selecting " +"specific user roles the requirement applies to in **Enforced for user " +"roles** setting. Of course you must have at least one two-factor " +"authentication method enabled for this setting to take effect." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:110 -msgid "text" +#: ../settings/security/two-factor.rst:None +msgid "Enforced for User Roles Setting" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:107 +#: ../settings/security/two-factor.rst:62 msgid "" -"The output of the process that triggered the event. " -"(``$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" +"After you change this setting, if the user has one of the selected roles on " +"their account, they will be forced to set up the two-factor authentication " +"upon next sign in or application reload." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:121 +#: ../settings/security/two-factor.rst:66 msgid "" -"The Object Manager attribute panel displays built-in and custom\n" -"attribute names." +"A modal dialog with instructions will be shown, and they will not be able to " +"do any work before they set up at least one two-factor method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:121 -msgid "Find a complete list of ticket attributes in the Object Manager." +#: ../settings/security/two-factor.rst:None +msgid "Modal Dialog for Enforcing Two-Factor Authentication Set Up" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:123 -msgid "" -"Ticket attributes are entirely optional, and can be used to customize the " -"tickets that Checkmk creates. (Note that these attributes will be ignored if " -"a new event belongs to an existing ticket.)" +#: ../settings/security/two-factor.rst:74 +msgid "Reset Two-Factor Authentication for a Specific User" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:128 +#: ../settings/security/two-factor.rst:76 msgid "" -"Why would you want to do this? Maybe you have only one IT guy, and all " -"system monitoring issues should be automatically assigned to him. Or, maybe " -"you're creating multiple notification rules so that database outages take " -"higher priority than disk space warnings." +"In case an user isn't able to login anymore because of an inaccessible " +"second factor, you can reset the user's 2FA method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:135 -msgid "In most cases, you'll probably want to set one of the following:" +#: ../settings/security/two-factor.rst:79 +msgid "" +"To do this, go to the user management and search for the relevant user. " +"After you found the account, click the button in the action column and " +"select \"Manage Two-Factor Authentication\":" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:137 -msgid "group" -msgstr "grupo" +#: ../settings/security/two-factor.rst:None +msgid "Context menu in action column in user management" +msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:139 -msgid "state" -msgstr "estado" +#: ../settings/security/two-factor.rst:87 +msgid "" +"After selecting this, you can see a dialog where you can either reset one " +"2FA method or reset all of the user's 2FA methods:" +msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:140 -msgid "priority" -msgstr "prioridad" +#: ../settings/security/two-factor.rst:None +msgid "Dialog for resetting user's 2FA method" +msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:142 +#: ../settings/security/two-factor.rst:94 msgid "" -"but in practice, you can set almost any attribute, including :doc:`custom " -"ones you created through the Object Manager `." +"Choose the fitting one, click on the corresponding \"Remove ...\" button and " +"confirm your action. The user now has to setup a new 2FA method, depending " +"on your 2FA configuration." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:145 -msgid "Please note that the following attributes are **not customizable**:" +#: ../settings/security/two-factor/authenticator-app.rst:2 +msgid "Authenticator App" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:147 -msgid "title" -msgstr "título" +#: ../settings/security/two-factor/authenticator-app.rst:4 +msgid "" +"The authenticator app method is a type of two-factor authentication that " +"uses a mobile application to generate one-time codes for account " +"verification. After setting up the authenticator app on their device, the " +"user links it to their Zammad account." +msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:148 -msgid "id" +#: ../settings/security/two-factor/authenticator-app.rst:12 +msgid "" +"When logging in, the user is prompted to enter a time-sensitive code " +"generated by the app, in addition to their password. This code acts as the " +"second factor of authentication, providing an extra layer of security as it " +"changes periodically and is unique to the user's device." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:149 -msgid "ticket number" +#: ../settings/security/two-factor/authenticator-app.rst:None +msgid "Security Code in Google Authenticator App" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:151 -msgid "created_by_id" +#: ../settings/security/two-factor/authenticator-app.rst:22 +msgid "" +"The app generates codes based on a shared secret key stored securely on both " +"the user's device and the server, ensuring a synchronized and secure " +"authentication process. The method of generating the codes is sometimes also " +"called TOTP (time-based one-time password)." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:152 -msgid "updated_by_id" +#: ../settings/security/two-factor/authenticator-app.rst:28 +msgid "Enabling the Authenticator App Method" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:155 -msgid "Which Values Can Be Set?" +#: ../settings/security/two-factor/authenticator-app.rst:30 +#: ../settings/security/two-factor/security-keys.rst:28 +msgid "To enable the method, just toggle the switch on in the settings." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:157 -msgid "😵 **Invalid values → unpredictable behavior**" +#: ../settings/security/two-factor/authenticator-app.rst:None +msgid "Authenticator App Switch in Settings" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:159 +#: ../settings/security/two-factor/authenticator-app.rst:36 msgid "" -"If you provide a value that Zammad doesn't understand (*e.g.,* ``-F " -"\"priority=high\"``), it's not always clear what will happen. In some cases, " -"a ticket will be created with the default values instead - but in others, it " -"may not be created at all!" +"Now the users will be able to set up this two-factor authentication method " +"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " +"Once they do, on next sign-in with password, they will be asked to provide " +"an additional security code generated by their mobile device." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:164 -msgid "So what values does Zammad understand, then? Well, it depends..." +#: ../settings/security/two-factor/security-keys.rst:2 +msgid "Security Keys" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:168 -msgid "Use an email address or username:" +#: ../settings/security/two-factor/security-keys.rst:4 +msgid "" +"The security keys method is a type of a two-factor authentication that uses " +"Web Authentication API in the browser for verifying user's identity. The " +"user can register multiple hardware or software security keys with their " +"Zammad account and then they can use it during the sign-in process." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:190 -msgid "group & priority" +#: ../settings/security/two-factor/security-keys.rst:12 +msgid "" +"When logging in, the user is prompted to provide the same security key they " +"registered with their account, in addition to their password. This key acts " +"as the second factor of authentication, providing an extra layer of security." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:175 -msgid "Refer to the dropdown menus in the ticket pane:" +#: ../settings/security/two-factor/security-keys.rst:None +msgid "Security Key dialog in Safari on macOS" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:0 -msgid "See possible values for certain attributes in the ticket pane." +#: ../settings/security/two-factor/security-keys.rst:21 +msgid "" +"The type of the key can range from hardware USB sticks to passkeys stored in " +"a device of user's choice. Which type can be used depends on the browser " +"flavor and the platform of the user." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:187 -msgid "🙅 **Ticket state CANNOT be set this way!**" +#: ../settings/security/two-factor/security-keys.rst:26 +msgid "Enabling the Security Keys Method" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:189 -msgid "" -"Why? Because ``-F \"state=...\"`` is already used :ref:`as a Checkmk " -"parameter `." +#: ../settings/security/two-factor/security-keys.rst:None +msgid "Security Keys Switch in Settings" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:222 -msgid "Everything Else" +#: ../settings/security/two-factor/security-keys.rst:34 +msgid "" +"Now the users will be able to set up this two-factor authentication method " +"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " +"Once they do, on next sign-in with password, they will be asked to provide " +"the same security key they registered during the setup." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:193 +#: ../settings/system/system-selfhosted.include.rst:3 msgid "" -"To set any other attributes, it helps to know your way around the :docs:" -"`rails console `. Valid values are those that you can " -"set with a string:" +"Below settings are only available to self hosted users. In hosted " +"environments we're handling these settings for you to ensure service " +"stability." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:218 -msgid "These values can then be passed directly to the API:" +#: ../settings/system/base.rst:11 +msgid "Fully Qualified Domain Name" msgstr "" -#: ../system/integrations/checkmk/index.rst:16 -msgid "How does it work?" +#: ../settings/system/base.rst:7 +msgid "The URL of your Zammad installation." msgstr "" -#: ../system/integrations/checkmk/index.rst:2 -msgid "Checkmk" +#: ../settings/system/base.rst:9 ../settings/system/base.rst:17 +msgid "This setting is used within :doc:`/misc/variables` and notifications." msgstr "" -#: ../system/integrations/checkmk/index.rst:4 -msgid "" -"`Checkmk `_ is a powerful IT monitoring tool that can " -"send real-time status alerts to Zammad via email or REST API. Set these " -"alerts up in Checkmk, and Zammad will automatically create, update, and " -"close tickets based on the health of your system:" +#: ../settings/system/system-base.include.rst:1 +msgid "It is automatically set by the *Getting Started wizard*." msgstr "" -#: ../system/integrations/checkmk/index.rst:14 -msgid "Screenshot of ticket created by Checkmk notifications" +#: ../settings/system/system-base.include.rst:5 +msgid "Changing this setting also changes callback URLs for your channels etc." msgstr "" -#: ../system/integrations/checkmk/index.rst:14 -msgid "Multiple alerts, same ticket." +#: ../settings/system/system-base.include.rst:6 +msgid "This setting can have negative affects on being able to login." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:2 -msgid "Setup Guide" +#: ../settings/system/base.rst:19 +msgid "HTTP type" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:4 +#: ../settings/system/base.rst:14 msgid "" -"Whenever the Checkmk integration is enabled, Zammad listens for messages on " -"its API and over email. As long as those messages follow the required " -"format, Zammad will create new tickets (or find and update existing ones) " -"based on the message contents." +"The HTTP type tells your installation how your clients connect. This is " +"relevant for authentication and cookie security." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:10 -msgid "" -"That means that “setting up Checkmk integration” is simply a matter of " -"**adding configuration to your Checkmk site**: telling it when to send these " -"messages and what to say. To do that, you'll need to create a new " -"**notification rule** (see `Checkmk's official docs `_ for help with that)." +#: ../settings/system/base.rst:31 +msgid "SystemID" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:17 +#: ../settings/system/base.rst:22 msgid "" -"As part of this new rule, you'll have to choose a **notification method** " -"(*i.e.,* a script to execute whenever the rule is triggered). This script " -"will be written by you (samples below), and contain the logic for sending " -"API/email messages to Zammad:" -msgstr "" - -#: ../system/integrations/checkmk/setup-guide.rst:26 -msgid "Checkmk \"New Rule\" dialog" +"This ID is being used within your ticket number. In case you're " +"communicating with another ticket system with similar ticket number schemes " +"this ID greatly reduces the risk of false follow ups." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:26 +#: ../settings/system/base.rst:26 msgid "" -"Find your custom scripts in the Checkmk WATO under **Notifications > New " -"Rule > Notification Method**." +"The SystemID is randomly selected upon installation of Zammad (``1-99``)." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:29 +#: ../settings/system/base.rst:30 msgid "" -"Once you're done setting up your new rule, you're all set! New tickets " -"should start coming in and auto-updating any time your rule is triggered." +"**Do not** change this setting in a productive system! Your Zammad " +"installation may no longer recognize old ticket number based follow ups upon " +"change!" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:33 -msgid "" -"(If you need help troubleshooting, be sure to check the :ref:`checkmk-recent-" -"logs`.)" +#: ../settings/system/frontend.rst:2 +msgid "Frontend" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:38 -msgid "API Alerts" +#: ../settings/system/frontend.rst:22 +msgid "Core Workflow Ajax Mode" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:40 +#: ../settings/system/frontend.rst:6 msgid "" -"To add these scripts in the Checkmk WATO, copy them into your Checkmk " -"installation directory and make them executable. (Be sure to replace the " -"``zammad.example.com`` callback URL with the one found in your admin panel.)" +"This setting allows administrators to enforce :doc:`/system/core-workflows` " +"to use Ajax-Calls instead of web sockets. You'll usually only need this if " +"you experience serious issues as noted below." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:60 -msgid "Service notification" +#: ../settings/system/frontend.rst:10 +msgid "**🤓 Possible (technical) reasons**" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:46 +#: ../settings/system/frontend.rst:12 msgid "" -"For updates on the status of the software running on your server (*e.g.,* " -"postgres)." +"In some cases, your network structure (e.g. firewalls, proxies) may " +"disconnect long web socket connections. This leads to select fields staying " +"empty (e.g. owner selection *after* selecting your group) or fields not " +"shown / hidden (e.g. when switching to or from pending states, the \"pending " +"till\" field not showing / hiding)." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:75 -msgid "Host notification" +#: ../settings/system/frontend.rst:18 +msgid "" +"Please keep in mind that the Ajax fallback may cause serious pressure on " +"your application server. If you have the choice stick to web sockets." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:63 -msgid "For updates on the status of the server itself." +#: ../settings/system/frontend.rst:22 +msgid "Default: ``no`` (inactive)" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:77 -msgid "🤔 **What's with all the env vars?**" +#: ../settings/system/frontend.rst:53 +msgid "Show calendar weeks in the picker of date/datetime fields" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:79 +#: ../settings/system/frontend.rst:25 msgid "" -"Whenever Checkmk runs these scripts, it needs to provide some information " -"about the event that triggered the notification. This information is passed " -"in the form of these ``$NOTIFY_*`` environment variables." +"With this setting you can instruct Zammad to provide week number display " +"globally for all users. Calendar with week number display are usually used " +"in business sectors and may not be relevant for everyone." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:85 +#: ../settings/system/frontend.rst:29 msgid "" -"You can specify additional parameters to pass to the script when you're " -"setting up your notification rule, but the ones you see here are all " -"provided by default." +"This setting affects *all areas* - you'll also see week numbers in the admin " +"panel for e.g. triggers and macros." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:90 -msgid "Email Alerts" +#: ../settings/system/frontend.rst:32 +msgid "Default: ``no`` (not shown)" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:94 -msgid "" -"🐞 **There are known bugs** in Zammad's processing of email from Checkmk. " -"This section will be completed once they have been resolved. (Learn more at " -"GitHub issues `#2377 `_ & " -"`#2180 `_.)" +#: ../settings/system/frontend.rst:53 +msgid "Here's the difference:" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:100 -msgid "In the meantime, we encourage you to set up API alerts instead." +#: ../settings/system/frontend.rst:0 +msgid "Screenshot showing Zammad's date picker (in the default way)" msgstr "" -#: ../system/integrations/clearbit.rst:2 -msgid "Clearbit" +#: ../settings/system/frontend.rst:41 +msgid "Set to ``no``" msgstr "" -#: ../system/integrations/clearbit.rst:4 +#: ../settings/system/frontend.rst:0 msgid "" -"With our Clearbit integration, you can easily enrich the information " -"provided by Zammad. If the customers or agents email address is known to " -"Clearbit, it will share all information it has regarding the user with " -"Zammad. Those information can include the following:" +"Screenshot showing Zammad's date picker with\n" +"week numbers enabled" msgstr "" -#: ../system/integrations/clearbit.rst:9 -msgid "Avatar" +#: ../settings/system/frontend.rst:50 +msgid "Set to ``yes``" msgstr "" -#: ../system/integrations/clearbit.rst:10 -msgid "Address information" +#: ../settings/system/index.rst:4 +msgid "" +"For your overview we split each tab within system settings into its own page:" msgstr "" -#: ../system/integrations/clearbit.rst:11 -msgid "Website information" +#: ../settings/system/index.rst:16 +msgid "Console Based Settings" msgstr "" -#: ../system/integrations/clearbit.rst:12 -msgid "A BIO (as Note by default)" +#: ../settings/system/index.rst:18 +msgid "" +"There's some console based settings we didn't put into the UI. However, you " +"may find them helpful - you can find them in our :docs:`hidden settings ` section." msgstr "" -#: ../system/integrations/clearbit.rst:14 -msgid "" -"If needed, you can add further custom objects and add mappings to them, so " -"the Clearbit information can be filled within the database. In general you " -"can get any information from Clearbit, as long as you have a mapping to an " -"Zammad object." +#: ../settings/system/network.rst:2 +msgid "Network" msgstr "" -#: ../system/integrations/clearbit.rst:21 +#: ../settings/system/network.rst:8 msgid "" -"Clearbit does have a mapping of fields like LDAP and Exchange have, but does " -"not \"win\" against Zammad information. This means that if you have e.g. the " -"last name field filled in already and Clearbit has other information on " -"that, it will not be updated." +"The proxy settings can only be saved after successfully testing the proxy " +"connection." msgstr "" -#: ../system/integrations/clearbit.rst:26 +#: ../settings/system/network.rst:15 +msgid "Proxy Address." +msgstr "" + +#: ../settings/system/network.rst:12 msgid "" -"However: If let's say the last name has been set by Clearbit and Zammad " -"notices that the last name on the Clearbit source has changed, Zammad will " -"also update this value." +"Allows you to provide a proxy server if needed. This is relevant for network " +"communication by Zammad." +msgstr "" + +#: ../settings/system/network.rst:15 +msgid "It **does not** affect the update process or Elasticsearch." msgstr "" -#: ../system/integrations/clearbit.rst:33 -msgid "" -"The configuration of Clearbit is really easy and done fast! Just login to " -"your Clearbit-Account, go to \"API\" and copy the secret-API-Key." +#: ../settings/system/network.rst:18 +msgid "Username for proxy connection." msgstr "" -#: ../system/integrations/clearbit.rst:38 +#: ../settings/system/network.rst:18 msgid "" -"Now change to your Zammad instance, go to Integrations (System) -> Clearbit " -"in the admin panel. Paste your API-Key into the API-Key-Field and decide if " -"Zammad should create unknown Organizations automatically, if the user does " -"not have one yet (and Clearbit knows it). The shared option decides if the " -"new organizations Zammad creates with Clearbit should be shared ones." +"If your proxy server requires authentication, provide the username here." msgstr "" -#: ../system/integrations/clearbit.rst:47 -msgid "" -"If you're unsure what option to choose, better stick with \"no\". You can " -"also learn more about :doc:`/manage/organizations/index`." +#: ../settings/system/network.rst:21 +msgid "Password for proxy connection." msgstr "" -#: ../system/integrations/clearbit.rst:52 +#: ../settings/system/network.rst:21 msgid "" -"The Mapping option works similar to the mapping within the Exchange and LDAP " -"sync. You can add further mappings for e.g. custom fields if you need more " -"information that Clearbit can provide." +"If your proxy server requires authentication, provide the password here." msgstr "" -#: ../system/integrations/clearbit.rst:58 -msgid "" -"If you want to add more Clearbit fields and want to learn more about " -"available fields on their API, you can take a look at their `API " -"documentation `_." +#: ../settings/system/network.rst:26 +msgid "No proxy for the following hosts." msgstr "" -#: ../system/integrations/clearbit.rst:62 +#: ../settings/system/network.rst:24 msgid "" -"If you're happy with the above chosen Settings and your mapping, just save " -"the changes and enable Clearbit integration. Zammad will now start polling " -"the Clearbit API as users contact you." +"Exception list for hosts you can't or don't want to reach via proxy server." msgstr "" -#: ../system/integrations/clearbit.rst:68 -msgid "" -"Zammad does not synchronize with Clearbit on a regular basis, but on demand " -"if needed. This saves API calls." +#: ../settings/system/network.rst:27 +msgid "Default: ``localhost,127.0.0.0,::1``" msgstr "" -#: ../system/integrations/clearbit.rst:73 -msgid "" -"Below the Settings and Mappings, you'll find our Integration log. You can " -"see what requests Zammad sent to Clearbit and also the APIs Response." +#: ../settings/system/services.rst:2 +msgid "Services" msgstr "" -#: ../system/integrations/clearbit.rst:78 -msgid "" -"By the way, you can also view the API log on the Clearbit website - the " -"information seen is basically the same." +#: ../settings/system/services.rst:10 +msgid "Image Service" msgstr "" -#: ../system/integrations/clearbit.rst:84 -msgid "Example When Adding a User" +#: ../settings/system/services.rst:5 +msgid "Defines the backend for user and organization image lookups." msgstr "" -#: ../system/integrations/clearbit.rst:86 +#: ../settings/system/services.rst:7 +msgid "Default: ``Zammad Image Service`` (active)" +msgstr "" + +#: ../settings/system/services.rst:9 msgid "" -"To show you how fast information is added, we added a small Screencast " -"below. This shows the creation of the User Alex from Clearbit. As we already " -"set the last name of Alex to \"X\", Zammad did not update it. What Zammad " -"did was to add further information it received from Clearbit." +"Make sure your on premise installation has ``HTTPS`` access to ``images." +"zammad.com``." msgstr "" -#: ../system/integrations/cti/generic.rst:2 -msgid "CTI (generic)" +#: ../settings/system/services.rst:18 +msgid "Geo Calendar Service" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:1 +#: ../settings/system/services.rst:13 msgid "" -"This integration enables Zammad to provide a caller log to your agents. With " -"this your agents can greet your customers by their name and are supported by " -"Zammad with automatically opening a new ticket dialog or the user profile." +"Defines the backend for geo calendar lookups. Used for initial calendar " +"setup." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:6 -msgid "" -"Click the toggle next to the heading to activate or deactivate this " -"integration." +#: ../settings/system/services.rst:16 +msgid "Default: ``Zammad GeoCalendar Service`` (active)" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:9 +#: ../settings/system/services.include.rst:2 msgid "" -"If you want to learn more on how your agents can use this function, please " -"refer the :user-docs:`user documentation `." +"Make sure your on premise installation has ``HTTPS`` access to ``geo.zammad." +"com``." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:14 +#: ../settings/system/services.rst:26 +msgid "Geo IP Service" +msgstr "" + +#: ../settings/system/services.rst:21 msgid "" -"Automatically opening new ticket dialogues or user profiles requires agent " -"to extension mapping - see more below." +"Defines the backend for geo IP lookups. Shows also location of an IP address " +"if an IP address is shown." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:20 -msgid "Please note the following limitations to reduce confusion later on:" +#: ../settings/system/services.rst:24 +msgid "Default: ``Zammad GeoIP Service`` (active)" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:22 -msgid "CTI integrations provide caller log functions only." +#: ../settings/system/services.rst:32 +msgid "Geo Location Service" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:23 +#: ../settings/system/services.rst:29 msgid "" -"This integration does not provide any VoIP functionalities; you can't make " -"phone calls from within Zammad." +"Defines the backend for geo location lookups to store geo locations for " +"addresses." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:25 +#: ../settings/system/services.rst:32 msgid "" -"If your browser supports ``tel``-URLs, you can click on phone numbers for " -"automatic dialing. This requires additional software / configuration on your " -"agent's computers." +"Default: ``OpenStreetMap (ODbL 1.0, http://osm.org/copyright)`` (active)" msgstr "" -#: ../system/integrations/cti/generic.rst:9 -#: ../system/integrations/cti/placetel.rst:14 -#: ../system/integrations/cti/sipgate.rst:14 -msgid "Please provide the following requirements:" +#: ../settings/system/services.rst:36 +msgid "" +"You can find a detailed privacy information on what we store for how long on " +"our :docs:`Privacy Appendix ` inside of our System " +"Documentation." msgstr "" -#: ../system/integrations/cti/generic.rst:11 -msgid "" -"A telephone system that supports webhooks (outbound) (best option are those " -"that allow customizing the calls)." +#: ../settings/system/storage.rst:2 +msgid "Storage" msgstr "" -#: ../system/integrations/cti/generic.rst:13 -msgid "A unique Call-ID during the call session." +#: ../settings/system/storage.rst:6 +msgid "" +"Here you can define where Zammad stores attachments for tickets and the " +"knowledge base. By default, we're writing to the ``Database`` - you can " +"switch to ``Filesystem`` or ``Simple Storage (S3)`` at any time. In this " +"case please have a look on the following instructions." msgstr "" -#: ../system/integrations/cti/generic.rst:14 -msgid "Call event data (both numbers and direction)." +#: ../settings/system/storage.rst:11 +msgid "" +"If you have a busy Zammad instance, we strongly encourage you to use " +"filesystem storage instead of \"Database\". This will greatly improve system " +"performance (de-crease database load and size)." msgstr "" -#: ../system/integrations/cti/generic.rst:15 -msgid "Your Zammad instance must be reachable for your telephony system." +#: ../settings/system/storage.rst:19 +msgid "Database" msgstr "" -#: ../system/integrations/cti/generic.rst:17 +#: ../settings/system/storage.rst:17 msgid "" -"If you want to learn more on what kind of requests are supported by Zammad " -"and what it expects, please consult our :docs:`CTI-API documentation `." +"This is the default storage method. The attachments are stored directly in " +"the database. If your Zammad instance grows, we recommend one of the other " +"methods to maintain performance." msgstr "" -#: ../system/integrations/cti/generic.rst:22 -#: ../system/integrations/cti/placetel.rst:27 -#: ../system/integrations/cti/sipgate.rst:30 -#, fuzzy -msgid "Available Settings" -msgstr "Verificación de correo electrónico" - -#: ../system/integrations/cti/generic.rst:29 -#: ../system/integrations/cti/placetel.rst:41 -#: ../system/integrations/cti/sipgate.rst:40 -msgid "Endpoint Settings" +#: ../settings/system/storage.rst:38 +msgid "Filesystem" msgstr "" -#: ../system/integrations/cti/generic.rst:25 +#: ../settings/system/storage.rst:22 msgid "" -"Zammad will list your generic CTI endpoint here. It contains a unique token " -"so ensure to keep this URL save." +"This storage method is recommended for all Zammad instances, especially for " +"those with a higher load. If you choose filesystem, your files are written " +"to ``/opt/zammad/storage/``." msgstr "" -#: ../system/integrations/cti/generic.rst:28 +#: ../settings/system/storage.rst:26 msgid "" -"You'll need this endpoint for your PBX to talk to Zammad, see :docs:`CTI-API " -"documentation `." +"Moving attachments from \"Database\" to \"Filesystem\" can be run during " +"production use. However, you should consider your framework conditions (e.g. " +"bandwidth, system load in production) to define the right moment." msgstr "" -#: ../system/integrations/cti/includes/important-dont-forget-saving.include.rst:3 -msgid "" -"All following options **do not save automatically**. Always use the Save " -"button on the lower end of the integration page!" +#: ../settings/system/storage.rst:32 +msgid "**You noticed slow updates of Zammad?**" msgstr "" -#: ../system/integrations/cti/generic.rst:43 -#: ../system/integrations/cti/placetel.rst:49 -#: ../system/integrations/cti/sipgate.rst:52 -msgid "Call Settings" +#: ../settings/system/storage.rst:34 +msgid "" +"While Zammad is beeing updated, it enforces a recursive \"change " +"owner\" (chown) for this directory. For instances with many files this can " +"be time consuming. To mitigate that you can move your files and create a " +"symlink in ``/opt/zammad/storage/`` to the new directory. Of course you have " +"to make sure on your own that the permissions are always correct." msgstr "" -#: ../system/integrations/cti/generic.rst:39 -#: ../system/integrations/cti/placetel.rst:49 -#: ../system/integrations/cti/sipgate.rst:37 -#: ../system/integrations/cti/sipgate.rst:50 -msgid "Inbound" +#: ../settings/system/storage.rst:95 +msgid "Simple Storage (S3)" msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:1 +#: ../settings/system/storage.rst:41 msgid "" -"This option allows you to block specific incoming caller IDs. It allows you " -"to temporarily reject e.g. spam callers without having to contact providers " -"or PBX administrators." +"To use the Simple Storage (S3), you have to provide some settings, which " +"can't be accessed in the UI (see instructions below)." msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:11 -msgid "Caller ID to block" +#: ../settings/system/storage.rst:44 +msgid "" +"⚠️ Please note that the current implementation is in its early stages and can " +"be modified in the future." msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 -msgid "Provide caller IDs to block in ``E.164`` format." +#: ../settings/system/storage.rst:47 +msgid "" +"The prerequisite is to have access to a S3-compatible storage and to have " +"all necessary parameters available (which depends on your storage provider; " +"if in doubt, please ask there for help)." msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:8 -msgid "" -"Your telephony system has to support this function. Zammad will send a " -"``reject`` response which will cause your telephony system to hang up the " -"call. To callers this usually will feel like the line is busy." +#: ../settings/system/storage.rst:51 +msgid "Steps to configure S3:" msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:14 +#: ../settings/system/storage.rst:53 msgid "" -"Provide a meaningful note for your fellow administrators to remind yourself " -"why you've chosen to block the number." +"Copy ``config/zammad/storage.yml.dist`` to ``config/zammad/storage.yml``" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 -#: ../system/integrations/cti/includes/outbound-calls.include.rst:17 -#: ../system/integrations/cti/sipgate.rst:40 -msgid "Outbound" +#: ../settings/system/storage.rst:54 +msgid "Edit the copied file in one of the following ways:" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:1 +#: ../settings/system/storage.rst:56 msgid "" -"In many cases you may want to use a different caller ID depending on the " -"destination you're calling. This may apply due to specific connection rates " -"to other countries or because you want your customer to feel you're calling " -"from the same country." +"Either provide your S3 configuration with one attribute per line like in the " +"upper area of the file" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:6 -msgid "This option expects ``E.164`` number formats." +#: ../settings/system/storage.rst:58 +msgid "" +"Or provide your S3 configuration as an URL (which you can find at the end of " +"the file). Note: you can also provide this URL as environment variable (:" +"docs:`see system documentation `) without using this yml-file." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 -msgid "Destination caller ID" +#: ../settings/system/storage.rst:62 +msgid "" +"We recommend the deletion of the not used configuration style to avoid " +"inconsistencies." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:5 -msgid "The caller ID or number you're trying to call." +#: ../settings/system/storage.rst:65 +msgid "Restart Zammad so the config file / environment variable is loaded" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:7 -msgid "You can use wildcards for e.g. country specific outbound numbers like:" +#: ../settings/system/storage.rst:66 +msgid "" +"Set the \"Storage Method\" in Zammad to ``Simple Storage (S3)`` in Settings " +"> System > Storage and click on \"Submit\". After that, Zammad checks your " +"configuration and the connection to the service and will raise an error " +"message if something is wrong." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:9 -msgid "``49*`` for Germany" +#: ../settings/system/storage.rst:72 +msgid "A very simple storage configuration could look like this:" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:10 -msgid "``4930*`` for Berlin / Germany landlines" +#: ../settings/system/storage.rst:85 +msgid "" +"Before setting the storage method to ``Simple Storage (S3)`` (step 4), " +"please make sure to have a working setup." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 -msgid "``33*`` for France" +#: ../settings/system/storage.rst:88 +msgid "" +"You can verify this by running ``rails r 'Rails.logger = Logger.new(STDOUT); " +"pp Store::Provider::S3.ping?'`` in your Zammad directory. If everything is " +"fine, you should see ``true``, else you should see ``false`` and a simple " +"error message." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:15 -msgid "Set Outbound caller ID" +#: ../settings/system/storage.rst:93 +msgid "" +"If you installed Zammad through a package manager (rather than from source), " +"replace ``rails r`` with ``zammad run rails r`` above. To learn more, see :" +"docs:`Administration via Console `." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:14 +#: ../settings/ticket.rst:4 msgid "" -"The outbound caller ID to set (the number your customer sees on his display) " -"in ``E.164`` number format." +"Here you can adjust general ticket settings. Additional ones for the ticket " +"composer interface can be found in the :doc:`/misc/composer`." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 -msgid "Provide a short description for fellow administrators." +#: ../settings/ticket.rst:11 +msgid "Ticket Hook (default: ``Ticket#``)" msgstr "" -#: ../system/integrations/cti/includes/generic-cti-support-note.includes.rst:3 -msgid "" -"This option requires your PBX to send a specific request to Zammad *before " -"dialing*. Please consult the :docs:`CTI API ` in case " -"you're not sure." +#: ../settings/ticket.rst:11 +msgid "The identifier for a ticket; *e.g.,* Ticket#, Call#, MyTicket#." msgstr "" -#: ../system/integrations/cti/generic.rst:52 -#: ../system/integrations/cti/placetel.rst:54 -#: ../system/integrations/cti/sipgate.rst:59 -msgid "Other Settings" +#: ../settings/ticket.rst:38 +msgid "Ticket Hook Position (default: ``right``)" msgstr "" -#: ../system/integrations/cti/includes/other-settings-intro.include.rst:1 +#: ../settings/ticket.rst:14 msgid "" -"Below you can find all available additional settings for this CTI " -"integration. For your overview we're sorting them by appearance and " -"reference their description first." +"With this setting you can decide (if) where to insert the ticket number." msgstr "" -#: ../system/integrations/cti/includes/default-caller-id.include.rst:2 -#: ../system/integrations/cti/includes/default-caller-id.include.rst:1 -msgid "Default caller ID for outbound calls" +#: ../settings/ticket.rst:20 +msgid "*Right*" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:16 -#: ../system/integrations/cti/includes/records-caller-log.include.rst:15 -msgid "Shown records in caller log" +#: ../settings/ticket.rst:17 +msgid "" +"This setting will add the ticket reference on the right site of the subject." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:2 -msgid "" -"Allows you to set the number of shown caller log entries for all users. You " -"can choose from the following values:" +#: ../settings/ticket.rst:20 +msgid "Example: ``Some Subject [Ticket#12345]``" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:5 -msgid "60 (default)" +#: ../settings/ticket.rst:26 +msgid "*Left*" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:6 -msgid "120" +#: ../settings/ticket.rst:23 +msgid "" +"This setting will add the ticket reference on the left site of the subject." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:7 -msgid "180" +#: ../settings/ticket.rst:26 +msgid "Example: ``[Ticket#12345] Some Subject``" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:8 -msgid "240" +#: ../settings/ticket.rst:29 +msgid "*None*" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:9 -msgid "300" +#: ../settings/ticket.rst:29 +msgid "This will completely remove ticket references from the subject." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:11 -msgid "**🥵 Potential performance issue**" +#: ../settings/ticket.rst:33 +msgid "" +"Please ensure to take a look at :doc:`/channels/email/settings` within the " +"email channel to ensure you have at least one reference that helps Zammad to " +"assign follow-ups correctly." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:13 +#: ../settings/ticket.rst:37 msgid "" -"Setting this setting higher than 60 may cause serious performance issues on " -"very busy instances. Keep in mind that this setting causes Zammad to poll " -"and send up to 300 records to *all active agent sessions* in very short time " -"periods." +"Disabling this and not setting up any further follow up search will lead to " +"unexpected results!" msgstr "" -#: ../system/integrations/cti/generic.rst:73 -msgid "Caller Log Filter" +#: ../settings/ticket.rst:65 +msgid "" +"Ticket Last Contact Behaviour (default: ``Use the start time of the last " +"customer thread (which may consist of multiple articles).``)" msgstr "" -#: ../system/integrations/cti/generic.rst:55 +#: ../settings/ticket.rst:41 msgid "" -"This function allows you to provide call information based on e.g. queues " -"only to agents that really need the information." +"This setting changes the way Zammad updates the ``Last Contact`` value of a " +"ticket. This is fairly important for overviews and what you expect upon " +"ticket updates of a customer." msgstr "" -#: ../system/integrations/cti/generic.rst:58 +#: ../settings/ticket.rst:52 msgid "" -"Why? If you have a team for several countries or departments, you don't want " -"to bug your agents from other departments. Leaving these options empty will " -"fallback to showing everything to everyone." +"Use the start time of the last customer thread (which may consist of " +"multiple articles)." msgstr "" -#: ../system/integrations/cti/generic.rst:64 -msgid "Destination caller ID or Queue" +#: ../settings/ticket.rst:46 +msgid "" +"If this option is chosen, Zammad will update the last updated value just " +"once if a customer replies. After that, Zammad will wait for an agent to " +"react." msgstr "" -#: ../system/integrations/cti/generic.rst:63 +#: ../settings/ticket.rst:50 msgid "" -"This depends on your PBX and usually is either a queue ID, phone number or " -"extension." +"This comes in handy if you want to work tickets in the order of their first " +"update. This will not change ticket orders if customers decide to \"bump\" " +"the ticket affected." msgstr "" -#: ../system/integrations/cti/generic.rst:69 -msgid "Agents" +#: ../settings/ticket.rst:57 +msgid "Use the time of the very last customer article." msgstr "" -#: ../system/integrations/cti/generic.rst:67 +#: ../settings/ticket.rst:55 msgid "" -"Select the agents that are responsible for the group. These agents will then " -"see caller log entries and call notifications fitting to said queue." +"When setting this option, Zammad will always update the last updated value. " +"This means that if ordering by ``Last Update``, ticket orders will change if " +"customers \"bump\" the ticket." msgstr "" -#: ../system/integrations/cti/generic.rst:0 -msgid "" -"Screenshot showing the caller log filter table with pre filled sample data" +#: ../settings/ticket.rst:64 +msgid "Last contact value used on :doc:`/manage/overviews`" msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:6 +#: ../settings/ticket.rst:65 +msgid "Last contact value used on :doc:`/manage/trigger`" +msgstr "" + +#: ../settings/ticket.rst:88 msgid "" -"With recent logs Zammad allows you to view the latest calls for the CTI " -"functionality. This usually comes in handy, when you're looking for errors." +"Ticket Organization Reassignment (default: ``Update the most recent tickets." +"``)" msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:0 +#: ../settings/ticket.rst:68 msgid "" -"Screenshot showing several incoming requests within Recent logs section." +"This setting changes the way Zammad updates the organization field of the " +"tickets whenever the primary organization of a user is changed." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:16 -msgid "I'm just here to clear floats up." +#: ../settings/ticket.rst:74 +msgid "Update the most recent tickets." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:20 +#: ../settings/ticket.rst:72 msgid "" -"By clicking on the entry of interest, Zammad will provide more details on " -"the call in question. You'll see the payload it received and also the " -"response that was sent." +"If this option is chosen, Zammad will update the 100 most recent tickets " +"where the user is the ticket customer. The ticket organization field will be " +"automatically set to the new primary organization of the user." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:0 -msgid "" -"Screenshot showing detailed information of a specific log entry of recent " -"logs" +#: ../settings/ticket.rst:88 +msgid "Do not update any tickets." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:31 -msgid "x" +#: ../settings/ticket.rst:77 +msgid "" +"When choosing this option, Zammad will not update any tickets when the " +"user's primary organization is changed." msgstr "" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 -#: ../system/integrations/cti/includes/troubleshooting.include.rst:9 -msgid "My Phone page stays blank, signalling does work..." +#: ../settings/ticket.rst:80 +msgid "**Use with care!**" msgstr "" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:5 +#: ../settings/ticket.rst:82 msgid "" -"If you've made sure that signalling works (check Recent logs) and your " -"Caller Log still stays empty, please ensure that you only configured one CTI " -"integration version. Specifically defining more than one agent mapping on " -"the different integration variants will be the issue." +"Using this option may lead to inconsistencies in the system as the ticket " +"organization may become decoupled from the ticket customer." msgstr "" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 -msgid "Clear the not needed agent mapping and reload your browser page." +#: ../settings/ticket.rst:85 +msgid "" +"However, you may use this option if you wish to maintain :ref:`the shared " +"access ` to the ticket for all organization " +"members of the original organization of the customer." msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:1 -msgid "" -"By mapping your agents extension to their existing Zammad users, Zammad can " -"provide a new ticket dialog or open the user profile for the agent that " -"picks up the call." +#: ../settings/ticket.rst:110 +msgid "Ticket Number Format (default: ``Increment (SystemID.Counter)``)" msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:5 +#: ../settings/ticket.rst:94 msgid "" -"This speeds up ticket aiding, no matter if it's for existing tickets or new " -"ones!" +"This setting defines the way Zammad's ticket number will look. Changing this " +"setting in production will cause follow up detection to fail." msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:8 +#: ../settings/ticket.rst:102 +msgid "Increment (SystemID.Counter)" +msgstr "" + +#: ../settings/ticket.rst:98 msgid "" -"To see it work from the agent's perspective, have a look on :user-docs:`user " -"documentation `." +"The increment value contains the SystemID (automatically generated during " +"installation) and a increment which counts up with every new Ticket. The " +"increment will automatically get another digit if needed." msgstr "" -#: ../system/integrations/cti/placetel.rst:2 -msgid "Placetel CTI" +#: ../settings/ticket.rst:102 +msgid "Examples: ``1010138``, ``1010139``" msgstr "" -#: ../system/integrations/cti/placetel.rst:16 -msgid "You need an administrative Placetel account for your organization." +#: ../settings/ticket.rst:110 +msgid "Date (Year.Month.Day.SystemID.Counter)" msgstr "" -#: ../system/integrations/cti/placetel.rst:17 -#: ../system/integrations/cti/sipgate.rst:20 +#: ../settings/ticket.rst:105 msgid "" -"Your Zammad instance must be allowed to communicate to external services." +"This version of the ticket number is fairly long. However, because it " +"contains the date of ticket creation, it also allows you to see when the " +"ticket has been created. You may feel familiar with this number format if " +"you've worked with OTRS already." msgstr "" -#: ../system/integrations/cti/placetel.rst:18 -msgid "Placetel must be able to reach your Zammad instance." +#: ../settings/ticket.rst:110 +msgid "Examples: ``201206231010138``, ``201206231010139``" msgstr "" -#: ../system/integrations/cti/placetel.rst:22 -msgid ":doc:`provider-configurations/placetel`" +#: ../settings/ticket.rst:137 +msgid "OPTIONS" msgstr "" -#: ../system/integrations/cti/placetel.rst:21 +#: ../settings/ticket.rst:113 msgid "" -"Learn how to configure Placetel to enable Zammad and Placetel to communicate " -"with each other." +"The below options allow you to further customize your ticket number. The " +"availability of options differ depending of the chosen ticket number format " +"above." msgstr "" -#: ../system/integrations/cti/placetel.rst:32 -msgid "" -"The here listed endpoint settings are relevant for the :doc:`integration " -"configuration with Placetel `." +#: ../settings/ticket.rst:122 +msgid "Checksum (default: ``no``)" msgstr "" -#: ../system/integrations/cti/placetel.rst:37 -#: ../system/integrations/i-doit.rst:53 -msgid "Endpoint" +#: ../settings/ticket.rst:118 +msgid "" +"If set to yes, we'll built a checksum to further \"unique\" the ticket " +"number of your system. If you're dealing with many other ticket systems this " +"might help to prevent false positive follow up detection on tickets." msgstr "" -#: ../system/integrations/cti/placetel.rst:36 -msgid "" -"This endpoint will be required for the Zammad integration within the " -"Placetel web interface." +#: ../settings/ticket.rst:122 +msgid "This will also add another digit to the ticket number." msgstr "" -#: ../system/integrations/cti/placetel.rst:41 -msgid "API Token" +#: ../settings/ticket.rst:137 +msgid "Min. size of Number (default: ``5``)" msgstr "" -#: ../system/integrations/cti/placetel.rst:40 +#: ../settings/ticket.rst:125 msgid "" -"You'll receive this token within the ``Web API`` menu. Make sure to copy " -"this value, it's only shown once!" +"This setting defines the minimum length of your ticket number. If your " +"counter is not yet high enough, Zammad will fill the number with zeros to " +"ensure the wanted length." msgstr "" -#: ../system/integrations/cti/placetel.rst:71 -#: ../system/integrations/cti/sipgate.rst:77 -msgid "Phone Extension to Agent Mapping" +#: ../settings/ticket.rst:129 +msgid "" +"Please note that the minimum length is ``3`` (SystemID + at least one digit " +"if below 10). Also, if the length is no longer long enough, the number will " +"automatically get one digit longer. Ticket-Numbers **do not overflow**, thus " +"it's save to keep it at 5 or set it lower if wanted." msgstr "" -#: ../system/integrations/cti/placetel.rst:0 -msgid "Screenshot showing sample user mappings in between Placetel and Zammad" +#: ../settings/ticket.rst:135 +msgid "" +"This option is only available if ticket number format is set to " +"``Increment``!" msgstr "" -#: ../system/integrations/cti/placetel.rst:64 -msgid "" -"You can find your agents Placetel username combination required within ⚙️ PBX " -"→ VoIP destinations. Within the \"Advanced settings\" section you're looking " -"for \"SIP user name\" and \"SIP server\"." +#: ../settings/ticket.rst:142 +msgid "Auto-Assignment" msgstr "" -#: ../system/integrations/cti/placetel.rst:68 -msgid "Combine these two like so: ``@``." +#: ../settings/ticket.rst:144 +msgid "" +"In a larger Zammad environment, it happens that several agents open the same " +"ticket at the same time. Although collision detection is then effective, the " +"efficiency of processing can be increased by means of the automatic " +"assignment of tickets when a ticket is opened." msgstr "" -#: ../system/integrations/cti/placetel.rst:0 -msgid "Sample VoIP credentials for a Placetel user" +#: ../settings/ticket.rst:149 +msgid "" +"The automatic assignment of tickets can be activated and configured in the " +"admin area under Settings > Ticket > Auto Assignment." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:2 -msgid "Setup Placetel connection for Zammad" +#: ../settings/ticket.rst:152 +msgid "" +"The auto assignment only works if the ticket has no owner yet. By default, " +"the agent can always reset the ticket owner to ``-`` if needed." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:6 +#: ../settings/ticket.rst:155 msgid "" -"This configuration step requires a *full* administrative Placetel account. " -"You may receive forbidden error messages with Placetel in case your " -"permissions are not high enough." +"If you want to use this function for only specific tickets, you can " +"configure the conditions accordingly to meet your requirement. By default " +"the condition affects all tickets with the state ``open``." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:10 +#: ../settings/ticket.rst:161 msgid "" -"The following actions can be configured via the `Placetel web interface " -"`_." +"If you need to exclude users (e.g. a group leader), you can search and " +"select the desired agents in the ``Exception Users`` list. The search " +"function in this area is only effective, if you have too many agents to " +"display at once to help you with the configuration." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:29 -msgid "Step 1: Activate Zammad integration" +#: ../settings/ticket.rst:167 +#, fuzzy +msgid "Notifications" +msgstr "Verificación de correo electrónico" + +#: ../settings/ticket.rst:191 +#, fuzzy +msgid "Default Notifications" +msgstr "Verificación de correo electrónico" + +#: ../settings/ticket.rst:170 +msgid "" +"This setting allows you to configure the default ticket notifications that " +"will be applied to all new agent users (incl. users who were just assigned " +"agent role). Simply change the notification matrix to desired state and " +"press **Save**." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:14 +#: ../settings/ticket.rst:175 msgid "" -"Within Integrations, scroll down to Partner integrations and select Zammad." +"In case an agent already exists, their ticket notification preferences will " +"be preserved. Optionally, you can also **Apply current defaults to all " +"agents**." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:17 +#: ../settings/ticket.rst:181 msgid "" -"You can alternatively filter by \"Ticket Systems\" to reduce the number of " -"entries on the page. You'll still want to look for Partner integrations. 🤓" +"**Potential time-consuming action:** Applying default ticket notifications " +"to all agent users may take some time to complete, be patient! The exact " +"time will depend on the size of your system and the number of agents." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:21 +#: ../settings/ticket.rst:185 msgid "" -"Within the Zammad integration now press \"Activate\". A new tab ``API`` " -"becomes available - open this tab." +"**Active agents only!** When current default ticket notifications are " +"applied, only active agent users are considered. In case an agent is re-" +"activated *after* this action, they will still have the old notification " +"configuration." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:24 +#: ../settings/ticket.rst:190 msgid "" -"Now tick \"Enable Call Control / Notify API\" and paste the Placetel " -"endpoint from your Zammad instance into the field \"URL of your API " -"endpoint\". Save to apply the settings" +"In case you want to go back to the initial state of ticket notifications, " +"you can click on **Reset to default** button." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 -msgid "Screencast showing how to activate the Zammad integration" +#: ../settings/ticket.rst:196 +msgid "Duplicate Detection" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:51 -msgid "Step 2: Generate API Token for Placetel" +#: ../settings/ticket.rst:238 +msgid "Detect Duplicate Ticket Creation" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:32 +#: ../settings/ticket.rst:199 msgid "" -"Go back to the integrations page and scroll down to \"Web API\". Generate a " -"new API token by using the \"Create a new API token\" button." +"This setting turns on the duplicate ticket detection mechanism during ticket " +"creation. If similar tickets are found in the system, a suitable warning " +"will be shown to the user trying to create a ticket." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:37 -msgid "" -"If you already generated a token either use your existing token or reset it " -"by using above mentioned button. Placetel will ask you to conform this reset." +#: ../settings/ticket.rst:206 +msgid "A Sample Duplicate Ticket Warning" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:41 +#: ../settings/ticket.rst:208 msgid "" -"Please keep in mind that existing API scripts may no longer work due to " -"token resets!" +"You can choose which ticket attributes will be matched by selecting them in " +"**Attributes to compare** field. Only if the ticket attribute value provided " +"by the user in the ticket create form is *equal* with the attribute in an " +"existing ticket, the warning will be shown." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:44 +#: ../settings/ticket.rst:213 +msgid "**Warning title** and **Warning message** are configurable as well." +msgstr "" + +#: ../settings/ticket.rst:215 msgid "" -"Copy the provided API token and insert it into the \"API Token\" field " -"within Zammad's Placetel integration." +"You can limit the detection only to certain user roles. By default, only " +"agents will see the warning." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:47 +#: ../settings/ticket.rst:218 msgid "" -"Apply your changes by using the \"Save\" button on the bottom of the " -"Placetel integration page and activate the Placetel integration." +"If you don't want to show the matched tickets as part of the warning, you " +"can set **Show matching ticket(s) in the warning** setting to *no*." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +#: ../settings/ticket.rst:221 msgid "" -"Screencast showing how to retrieve an API token from Placetel for Zammad" +"By default, **Permission level for looking up ticket** is set to *User*, " +"which means user permissions will be honored during sarch. The user will " +"see the warning only if tickets they have access to are matched. " +"Alternatively, you can set this setting to *System*, in which case the " +"search will happen within *all* tickets in the system, regardless of user " +"permissions." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:73 -#: ../system/integrations/cti/provider-configurations/sipgate.rst:77 -msgid "Step 3: Restrict the numbers to notify on" +#: ../settings/ticket.rst:227 +msgid "**🦺 Safety first!**" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:54 +#: ../settings/ticket.rst:229 msgid "" -"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " -"the the Integrations page of the Placetel web interface, go to \"Notify " -"API\"." +"Even if the permission level is set to *System*, the user will not be shown " +"the tickets they don't have access to in the warning, even if they match." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:58 +#: ../settings/ticket.rst:233 msgid "" -"Lower on the page Placetel allows you to restrict the numbers to notify on. " -"You'll find this within the \"External routing API\" part." +"However, just the confirmation about the existence of the tickets in the " +"system may be considered an unwanted information disclosure. Use this option " +"carefully!" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +#: ../settings/ticket.rst:237 msgid "" -"Screenshot showing a sample selection of phone numbers to use for the " -"Placetels notify API" +"Finally, you can configure between matching within **All tickets** or **Open " +"tickets** only by setting **Match tickets in following states**. Depending " +"on the current ticket state, a ticket may or not be matched." +msgstr "" + +#: ../system/core-workflows.rst:2 +msgid "Core Workflows" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:66 +#: ../system/core-workflows.rst:4 msgid "" -"This menu point also provides a API request log from Placetel view. Just " -"open \"Recent responses of your API endpoint\" to learn more." +"Core Workflows allow you to adjust object attributes in many ways. For " +"example:" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:69 -msgid "" -"If you want to see Zammad's perspective, use the \"Recent Logs\" part from " -"within the Placetel integration page." +#: ../system/core-workflows.rst:7 +msgid "show / hide fields" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 -msgid "Screenshot showing sample log entries for Placetels API calls to Zammad" +#: ../system/core-workflows.rst:8 +msgid "adjust mandatory setting" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:77 -msgid "Step 4 (optional): Further configurations for Placetel" +#: ../system/core-workflows.rst:9 +msgid "manipulate available options" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:76 +#: ../system/core-workflows.rst:11 msgid "" -"If needed, you can now configure Zammad's Placetel integration in more " -"detail. You can learn more about your options here: :ref:`Placetel " -"integration settings `." +"With this, you can provide exactly the information your users really need!" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:2 -msgid "Setup Sipgate connection for Zammad" +#: ../system/core-workflows.rst:15 +msgid "" +"If the pre-defined :doc:`/system/objects` are not enough, please add them " +"beforehand." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +#: ../system/core-workflows.rst:17 msgid "" -"Sipgate has no english web interface which is why this documentation page is " -"mixing up languages badly." +"If you experience slow or unreliable field updates, please see :ref:`Core " +"Workflow Ajax Modus `" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +#: ../system/core-workflows.rst:22 msgid "" -"Please also note that the availability of API addons highly depends on your " -"package trier. Usage of sipgate.io packages *is not free*, please check " -"their `pricing page `_ before!" +"This is a very enhanced functionality and can cause unexpected UI behavior. " +"Please ensure to test your use cases after configuration to reduce surprises." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:35 -msgid "Step 1: Book sipgate.io package" +#: ../system/core-workflows.rst:None +msgid "Dialogue for adding a new workflow" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:13 -msgid "Skip to step 2 if you already have the package booked!" +#: ../system/core-workflows/condition-operators.rst:2 +msgid "Core Workflow Condition Operators" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:15 +#: ../system/core-workflows/condition-operators.rst:4 msgid "" -"Login to an administrative Sipgate account and navigate to " -"``Accountverwaltung``. You'll see several different options depending on " -"your booked packages. Select ``Verträge & Produkte`` to continue." +"You might know that there is a separate section for explaining :doc:" +"`condition operators `. Head over there to " +"see a detailed explanation of many conditions and operators." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:19 +#: ../system/core-workflows/condition-operators.rst:8 msgid "" -"Scroll down to the section ``Zusätzliche Produkte buchen`` and look for " -"``sipgate.io`` - select this product by using the ``Produkte anzeigen``-" -"Button." +"Due to differences to other places in Zammad which are also using conditions " +"(e.g. triggers), you can find a dedicated description of operators for core " +"workflows below." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:23 +#: ../system/core-workflows/condition-operators.rst:12 msgid "" -"On the next page select either one of the ``sipgate.io`` packages or ``Push-" -"API Package Free``. Follow the dialogue by booking the addon. You'll be " -"returned to your contract overview and now should see the selected addon in " -"your list." +"Be aware that the availability of the operators depends on the selected " +"attribute and its field type. Some of the operators may only be available " +"for system attributes (e.g. for \"tags\", \"active\")." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:30 -msgid "" -"The availability for ``sipgate.io`` packages and their levels highly depends " -"on the overall account type and product you've booked with Sipgate." +#: ../system/core-workflows/condition-operators.rst:20 +msgid "Operator" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screencast showing the process on how to book the required sipgate.io addon" +#: ../system/core-workflows/condition-operators.rst:22 +msgid "after (absolute)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:52 -msgid "Step 2: Configure webhook for Zammad" +#: ../system/core-workflows/condition-operators.rst:23 +msgid "Matches if a date/time is after a specific point in time." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:38 -msgid "" -"Within your ``Accountverwaltung`` navicate to your product ``sipgate.io``. " -"In the newly opened tab, switch from \"Clients\" to \"Webhooks\" and paste " -"the endpoint URLs from your Zammad instance like so:" +#: ../system/core-workflows/condition-operators.rst:24 +msgid "after (relative)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:42 -msgid "Inbound endpoint to \"Incoming\"" +#: ../system/core-workflows/condition-operators.rst:25 +msgid "Matches if a time span after a specified event has passed." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:43 -msgid "Outbound endpoint to \"Outgoing\"" +#: ../system/core-workflows/condition-operators.rst:26 +msgid "before (absolute)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:47 -msgid "" -"Ensure to select at least one call group or phoneline within \"Sources\". " -"Other wise Sipgate will not indicate any incoming or outgoing calls to " -"Zammad." +#: ../system/core-workflows/condition-operators.rst:27 +msgid "Matches if a date/time is before a specific point in time." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screencast showing how to add Zammad's endpoint URLs to sipgate.ios webhook " -"configuration" +#: ../system/core-workflows/condition-operators.rst:28 +msgid "before (relative)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:55 -msgid "" -"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " -"the Webhooks → URLs section of Sipgate you can select which *sources* " -"Sipgate should notify Zammad about in- and outgoing calls." +#: ../system/core-workflows/condition-operators.rst:29 +msgid "Matches if a time span after a specified event has not passed." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:59 -msgid "" -"Use either specific phone lines or use the option \"Use for all phonelines " -"and groups\" to notify Zammad about all existing lines of your Sipgate " -"account." +#: ../system/core-workflows/condition-operators.rst:30 +msgid "contains" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screenshot showing a sample selection of phone numbers to use for the " -"Sipgates webhooks API" +#: ../system/core-workflows/condition-operators.rst:31 +msgid "Matches if a specified value is present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:68 -msgid "This section also allows you to enable a Debug log." +#: ../system/core-workflows/condition-operators.rst:33 +msgid "Matches if all of the specified values are present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "Screenshot showing an enabled Debug log option" +#: ../system/core-workflows/condition-operators.rst:35 +msgid "Matches if none of the specified values are present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:73 -msgid "" -"After enabling you can use the Debug log section to see all sent webhook " -"calls to Zammad. You'll also can see the response." +#: ../system/core-workflows/condition-operators.rst:36 +msgid "contains not" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screenshot showing sample log entries for Sipgates webhook calls to Zammad" +#: ../system/core-workflows/condition-operators.rst:37 +msgid "Matches if a specified value is not present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:81 -msgid "Step 4 (optional): Further configurations for Sipgate" +#: ../system/core-workflows/condition-operators.rst:39 +msgid "Matches if one specified value is present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:80 -msgid "" -"If needed, you can now configure Zammad's Sipgate integration in more " -"detail. You can learn more about your options here: :ref:`Sipgate " -"integration settings `." +#: ../system/core-workflows/condition-operators.rst:41 +msgid "Matches if one specified value is not present." msgstr "" -#: ../system/integrations/cti/sipgate.rst:2 -msgid "Sipgate (sipgate.io)" +#: ../system/core-workflows/condition-operators.rst:42 +msgid "does not match regex" msgstr "" -#: ../system/integrations/cti/sipgate.rst:16 -msgid "You need an administrative Sipgate account for your organization." +#: ../system/core-workflows/condition-operators.rst:43 +msgid "Matches if content doesn't fit to regex rule." msgstr "" -#: ../system/integrations/cti/sipgate.rst:17 -msgid "" -"Zammad requires a ``sipgate.io`` addon from the feature store (please note " -"that API calls are not free with Sipgate. Rates may apply and differ from " -"account to account)." +#: ../system/core-workflows/condition-operators.rst:44 +msgid "ends with" msgstr "" -#: ../system/integrations/cti/sipgate.rst:21 -msgid "Sipgate must be able to reach your Zammad instance." +#: ../system/core-workflows/condition-operators.rst:45 +msgid "Matches if content ends with specified value." msgstr "" -#: ../system/integrations/cti/sipgate.rst:25 -msgid ":doc:`provider-configurations/sipgate`" +#: ../system/core-workflows/condition-operators.rst:46 +msgid "ends with one of" msgstr "" -#: ../system/integrations/cti/sipgate.rst:24 -msgid "" -"Learn how to configure Sipgate to enable Zammad and Sipgate to communicate " -"with each other." +#: ../system/core-workflows/condition-operators.rst:47 +msgid "Matches if content ends with one of the specified values." msgstr "" -#: ../system/integrations/cti/sipgate.rst:33 -msgid "" -"Below endpoint settings affect the :doc:`sipgate.io configuration `." +#: ../system/core-workflows/condition-operators.rst:48 +msgid "from (relative)" msgstr "" -#: ../system/integrations/cti/sipgate.rst:37 -msgid "This endpoint is required for incoming call hooks." +#: ../system/core-workflows/condition-operators.rst:49 +msgid "Matches if date/time is after a period of time after an event." msgstr "" -#: ../system/integrations/cti/sipgate.rst:40 -msgid "This endpoint is required for outgoing call hooks." +#: ../system/core-workflows/condition-operators.rst:51 +msgid "Matches if content is equal to a specified value." msgstr "" -#: ../system/integrations/cti/sipgate.rst:0 -msgid "Screenshot showing sample user mappings in between Sipgate and Zammad" +#: ../system/core-workflows/condition-operators.rst:52 +msgid "is any of" msgstr "" -#: ../system/integrations/cti/sipgate.rst:69 -msgid "" -"You can find your agent's Sipgate username within ``Accountverwaltung → " -"Benutzer``. You're looking for the SIP-ID." +#: ../system/core-workflows/condition-operators.rst:53 +msgid "Matches if content is equal to any of specified values." msgstr "" -#: ../system/integrations/cti/sipgate.rst:0 -msgid "Sample VoIP credentials for a Sipgate user" +#: ../system/core-workflows/condition-operators.rst:54 +msgid "is modified" msgstr "" -#: ../system/integrations/cti/sipgate.rst:77 -msgid "Users with several devices also have several SIP-IDs." +#: ../system/core-workflows/condition-operators.rst:55 +msgid "Matches if content is modified." msgstr "" -#: ../system/integrations/elasticsearch.rst:2 -msgid "Elasticsearch (SaaS)" +#: ../system/core-workflows/condition-operators.rst:57 +#: ../system/core-workflows/condition-operators.rst:61 +msgid "True from the moment of changing content until form submit." msgstr "" -#: ../system/integrations/elasticsearch.rst:4 -msgid "" -"The Elasticsearch integration allows you to create a read-only user to use " -"with your favorite reporting tool (e.g. like Grafana)." +#: ../system/core-workflows/condition-operators.rst:58 +msgid "is modified to" msgstr "" -#: ../system/integrations/elasticsearch.rst:7 -msgid "" -"If you want to take full advantage of the Zammad reporting, have a look at " -"our :docs:`Grafana ` " -"setup page as well." +#: ../system/core-workflows/condition-operators.rst:59 +msgid "Matches if content is modified to a specific value." +msgstr "" + +#: ../system/core-workflows/condition-operators.rst:62 +msgid "is none of" +msgstr "" + +#: ../system/core-workflows/condition-operators.rst:63 +msgid "Matches if content is none of any specified values." msgstr "" -#: ../system/integrations/elasticsearch.rst:11 -#: ../system/subscription/index.rst:7 -msgid "**🚧 Hosted environment specific 🚧**" +#: ../system/core-workflows/condition-operators.rst:65 +msgid "Matches if content is not equal to a specified value." msgstr "" -#: ../system/integrations/elasticsearch.rst:13 -msgid "" -"This integration is only available for Hosted setups. In order to use " -"Elasticsearch you'll need the **Plus** subscription." +#: ../system/core-workflows/condition-operators.rst:67 +msgid "Matches if content is present." msgstr "" -#: ../system/integrations/elasticsearch.rst:16 -msgid "" -"Self hosted users have all the control over their self hosted Elasticsearch " -"instances." +#: ../system/core-workflows/condition-operators.rst:68 +msgid "just changed" msgstr "" -#: ../system/integrations/elasticsearch.rst:None -msgid "Elasticsearch integration page on SaaS environments" +#: ../system/core-workflows/condition-operators.rst:69 +msgid "Matches if content has changed." msgstr "" -#: ../system/integrations/elasticsearch.rst:27 +#: ../system/core-workflows/condition-operators.rst:71 +#: ../system/core-workflows/condition-operators.rst:75 msgid "" -"Please note the following limitations of Elasticsearch access on hosted " -"environments:" +"Only true for the moment of changing content until next form field action/" +"click." msgstr "" -#: ../system/integrations/elasticsearch.rst:30 -msgid "access to the Elasticsearch index is read-only access" +#: ../system/core-workflows/condition-operators.rst:72 +msgid "just changed to" msgstr "" -#: ../system/integrations/elasticsearch.rst:31 -msgid "currently you're limited to user only" +#: ../system/core-workflows/condition-operators.rst:73 +msgid "Matches if content has changed to a specified value." msgstr "" -#: ../system/integrations/elasticsearch.rst:32 -msgid "" -"Reporting tools that require to write into the indexes (like Kibana) are not " -"supported" +#: ../system/core-workflows/condition-operators.rst:76 +msgid "matches regex" msgstr "" -#: ../system/integrations/elasticsearch.rst:34 -msgid "IP access restriction is currently not yet supported" +#: ../system/core-workflows/condition-operators.rst:77 +msgid "Matches if value fits to regex rule." msgstr "" -#: ../system/integrations/elasticsearch.rst:37 -msgid "Activating Elasticsearch Access" +#: ../system/core-workflows/condition-operators.rst:79 +msgid "Matches if no content is present." msgstr "" -#: ../system/integrations/elasticsearch.rst:39 -msgid "" -"By default external access to your Elasticsearch index is not active. You " -"can enable the integration at any time if needed." +#: ../system/core-workflows/condition-operators.rst:80 +msgid "starts with" msgstr "" -#: ../system/integrations/elasticsearch.rst:42 -msgid "" -"Please ensure to note down the password provided - you won't have access to " -"it afterwards." +#: ../system/core-workflows/condition-operators.rst:81 +msgid "Matches if content starts with specified value." msgstr "" -#: ../system/integrations/elasticsearch.rst:None -msgid "Screencast showing activation of Elasticsearch integration" +#: ../system/core-workflows/condition-operators.rst:82 +msgid "starts with one of" msgstr "" -#: ../system/integrations/elasticsearch.rst:51 -msgid "Connection Settings" +#: ../system/core-workflows/condition-operators.rst:83 +msgid "Matches if content starts with one of the specified values." msgstr "" -#: ../system/integrations/elasticsearch.rst:53 -msgid "" -"This section holds the most important general information for accessing your " -"Elasticsearch indexes - such as:" +#: ../system/core-workflows/condition-operators.rst:84 +msgid "till (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:57 -msgid "A unique subdomain that does not tell your real instance URL." +#: ../system/core-workflows/condition-operators.rst:85 +msgid "Matches if date/time is before a period of time before an event." msgstr "" -#: ../system/integrations/elasticsearch.rst:61 -msgid "Software" +#: ../system/core-workflows/condition-operators.rst:86 +msgid "today" msgstr "" -#: ../system/integrations/elasticsearch.rst:60 -msgid "" -"The major version of the search index being used. This is required by some " -"Reporting tools like Grafana." +#: ../system/core-workflows/condition-operators.rst:87 +msgid "Matches if date/time is today." msgstr "" -#: ../system/integrations/elasticsearch.rst:64 -msgid "Authentication" +#: ../system/core-workflows/condition-operators.rst:88 +msgid "within last (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:64 -msgid "The authentication type being supported. ``Basic Authentication``" +#: ../system/core-workflows/condition-operators.rst:89 +msgid "" +"Matches if date/time content is within specified period of time before now." msgstr "" -#: ../system/integrations/elasticsearch.rst:67 -msgid "Available Indexes" +#: ../system/core-workflows/condition-operators.rst:91 +msgid "within next (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:69 +#: ../system/core-workflows/condition-operators.rst:92 msgid "" -"Within this section we're displaying the -in our opinion- most important " -"indexes for a Zammad instance." +"Matches if date/time content is within specified period of time after now." msgstr "" -#: ../system/integrations/elasticsearch.rst:72 -msgid "" -"If you require all indexes or our listing is not good enough for you, point " -"your browser to the URL we're providing and append ``/_aliases?" -"pretty=true``. The result should look like this: ``https://.zammad.com/" -"_aliases?pretty=true``." +#: ../system/core-workflows/how-do-they-work.rst:2 +msgid "How do they work?" msgstr "" -#: ../system/integrations/elasticsearch.rst:77 +#: ../system/core-workflows/how-do-they-work.rst:4 msgid "" -"Your browser will automatically ask for your credentials - you'll then see " -"something like this:" +"Core Workflows are executed according to their priority. If two workflows " +"have the same priority, they are executed in alphabetical order based on " +"their **name**." msgstr "" -#: ../system/integrations/elasticsearch.rst:125 -msgid "Credentials" +#: ../system/core-workflows/how-do-they-work.rst:8 +msgid "" +"Because of the way Core Workflows work, all changes to attributes are " +"checked with the application server - please see :doc:`limitations` for " +"possible issues." msgstr "" -#: ../system/integrations/elasticsearch.rst:127 +#: ../system/core-workflows/how-do-they-work.rst:12 msgid "" -"Within this section Zammad displays your available users. The password is " -"provided once (upon activation) and cannot be retrieved after that." +"Below we're talking about settings that are important and not self-" +"explanatory." msgstr "" -#: ../system/integrations/elasticsearch.rst:131 +#: ../system/core-workflows/how-do-they-work.rst:17 msgid "" -"If you need to change or reset your Elasticsearch user password, use the " -"\"Reset password\" button in the credentials table. Doing so creates a brand " -"new password for the account in question. This change is immediate, keep in " -"mind that this may affect third party tools connected to your instance." +"Choose the object context you want to run the workflow in. This will decide " +"on your available attributes and actions." msgstr "" -#: ../system/integrations/exchange.rst:2 -msgid "Exchange" +#: ../system/core-workflows/how-do-they-work.rst:20 +msgid "Ticket objects also have access to the ticket customer." msgstr "" -#: ../system/integrations/exchange.rst:4 +#: ../system/core-workflows/how-do-they-work.rst:25 msgid "" -"With Zammad's Exchange integration, you can easily use existing address " -"books without having to update more than one source." +"Choose in which situation the workflow is applied. Contexts can be combined " +"to avoid duplicate workflows." msgstr "" -#: ../system/integrations/exchange.rst:7 -msgid "" -"However, you should refrain from syncing all addresses, as the results may " -"not be what you expect (Exchange collects huge amounts of addresses). A " -"central address book of your company to sync makes more sense, as you can " -"ensure that Zammad gets only the data you need and want. Apart from this, it " -"is even not possible to sync the Global Address List (GAL) of your Exchange " -"system with Zammad." +#: ../system/core-workflows/how-do-they-work.rst:30 +msgid "Creation mask" msgstr "" -#: ../system/integrations/exchange.rst:16 +#: ../system/core-workflows/how-do-they-work.rst:29 msgid "" -"**Exchange and LDAP:** The exchange sync can be overruled by Zammad's LDAP " -"integration. If you have the same users in both sources, the LDAP version " -"will always be Zammad's pick." +"If selected, your conditions and actions will affect all applicable creation " +"masks." msgstr "" -#: ../system/integrations/exchange.rst:19 -msgid "" -"**One way sync:** the Exchange sync is one way. Exchange => Zammad. Changes " -"to your users inside of Zammad might be overwritten by the Exchange sync." +#: ../system/core-workflows/how-do-they-work.rst:34 +msgid "Edit mask" msgstr "" -#: ../system/integrations/exchange.rst:24 +#: ../system/core-workflows/how-do-they-work.rst:33 msgid "" -"To configure Exchange integration, simply go to the System > Integrations > " -"Exchange in the admin panel. Press \"change\" and follow the wizard for " -"adding the needed Exchange information to Zammad. On the last two steps " -"Zammad will ask you for the address book(s) and your desired attribute " -"mapping. By default, Zammad only maps email address, first- and lastname. " -"Technically, you can map any Exchange object to a Zammad user object (this " -"also works for custom objects!)." +"If selected, your conditions and actions will affect all applicable edit " +"masks." msgstr "" -#: ../system/integrations/exchange.rst:35 +#: ../system/core-workflows/how-do-they-work.rst:39 msgid "" -"If the SSL verification fails while connecting to Exchange, Zammad will ask " -"you to turn it off temporarily." +"Zammad differentiates between selected and saved conditions. These can be " +"combined wherever needed." msgstr "" -#: ../system/integrations/exchange.rst:38 -msgid "" -"Please be aware that **turning off SSL verification is a security risk**. It " -"should only be used temporarily or for testing purposes. If turned off, " -"there is no verification of the certificate, which means that every " -"presented certificate will be accepted." +#: ../system/core-workflows/how-do-they-work.rst:42 +msgid "**⚠️ Restrict workflows to specific roles if needed!**" msgstr "" -#: ../system/integrations/exchange.rst:43 +#: ../system/core-workflows/how-do-they-work.rst:44 msgid "" -"After pressing Continue, Zammad will check if the configuration is okay. You " -"can then enable Exchange and start your first sync. The sync will then run " -"hourly - if you need to change mappings or the address book(s), you can " -"change the configuration at any time." +"By default and unless configured in conditions, workflow rules are executed " +"for **all roles**. This also affects your customers!" msgstr "" -#: ../system/integrations/exchange.rst:50 -msgid "" -"After the sync has finished, you can find the new Exchange contacts under " -"\"Users\". Zammad integrates them just as normal users." +#: ../system/core-workflows/how-do-they-work.rst:50 +msgid "Selected Conditions" msgstr "" -#: ../system/integrations/exchange.rst:55 +#: ../system/core-workflows/how-do-they-work.rst:48 msgid "" -"In some cases you might see unique IDs as \"Login\" instead of the email " -"address. This is normal and doesn't affect the login or email mapping for " -"that entry." +"These conditions are based on form values and match if an appropriate " +"selection is made (e.g. choosing another group in the ticket without " +"saving). This applies for drafts (active selection) and currently saved " +"values." msgstr "" -#: ../system/integrations/github.rst:4 -msgid "" -"Use GitHub integration to track GitHub issues directly within Zammad " -"tickets. Add issue hyperlinks and get a live summary of metadata like status " -"(open/closed), assignee, labels, and more." +#: ../system/core-workflows/how-do-they-work.rst:64 +msgid "Saved Conditions" msgstr "" -#: ../system/integrations/github.rst:8 -msgid "Please note that our GitHub integration does not support pull requests." +#: ../system/core-workflows/how-do-they-work.rst:53 +msgid "" +"These conditions only match if the selected values are stored in the " +"database. It ignores the current value or selection of the field, as long as " +"the changes are not saved (e.g. performing field operations for an existing " +"ticket, which is viewed/opened by an agent)." msgstr "" -#: ../system/integrations/github.rst:None -msgid "Integration page for GitHub" +#: ../system/core-workflows/how-do-they-work.rst:60 +msgid "" +"Keep in mind that the value has to be available in the situation where you " +"need it. Otherwise the condition won't match." msgstr "" -#: ../system/integrations/github.rst:18 +#: ../system/core-workflows/how-do-they-work.rst:63 msgid "" -"In your GitHub settings, create a new API token under **Developer settings > " -"Personal access tokens > Generate new token**. Leave the **Scopes** section " -"empty." +"Example: you can't perform any actions with *saved condition* on a ticket in " +"creation, because there are no saved values at that time." msgstr "" -#: ../system/integrations/github.rst:0 ../system/integrations/gitlab.rst:0 -msgid "Screencast showing how to create a new API token" +#: ../system/core-workflows/how-do-they-work.rst:66 +msgid "" +"You can find a description of the condition operators for core workflows :" +"doc:`here `." msgstr "" -#: ../system/integrations/github.rst:27 -msgid "Create a new API key with no scopes/privileges." +#: ../system/core-workflows/how-do-they-work.rst:72 +msgid "" +"Which actions should we run on the relevant fields? The possible actions " +"depend on the object type. However, usually you can at least change the " +"visibility and whether the field is mandatory." msgstr "" -#: ../system/integrations/github.rst:29 -msgid "🔒 **Will this work for private repos?**" +#: ../system/core-workflows/how-do-they-work.rst:76 +msgid "Be aware that actions are not available for **related** context." msgstr "" -#: ../system/integrations/github.rst:31 +#: ../system/core-workflows/how-do-they-work.rst:78 msgid "" -"No. To link private repo issues, **use the** ``repo`` **scope instead**. " -"Bear in mind that the resulting token will have `lots of permissions that it " -"doesn't actually need `_, which presents a security risk if your token ever falls into " -"the wrong hands." +"**Example:** Let's assume you are working in the ticket context. While you " +"can have customer *conditions*, you *can't adjust* objects with actions in " +"that scope. That's because this wouldn't have any impact on the ticket " +"dialog. Of course all ticket attributes (state, owner, ...) are available." msgstr "" -#: ../system/integrations/github.rst:37 +#: ../system/core-workflows/how-do-they-work.rst:84 msgid "" -"Unfortunately, because of how GitHub's OAuth token scopes are set up, this " -"is the only way to link issues on private repos." +"Please also have a look at our :doc:`limitations` to be safe from surprises." msgstr "" -#: ../system/integrations/github.rst:40 -msgid "Enter your new API token in Zammad and enable GitHub integration." +#: ../system/core-workflows/how-do-they-work.rst:88 +msgid "Available Operators" msgstr "" -#: ../system/integrations/github.rst:0 -msgid "Screencast showing how to configure Zammad's GitHub integration" +#: ../system/core-workflows/how-do-they-work.rst:90 +msgid "The availability of operators depends on the object type and scope." msgstr "" -#: ../system/integrations/github.rst:47 +#: ../system/core-workflows/how-do-they-work.rst:94 msgid "" -"Use the default API endpoint (``https://api.github.com/graphql``) unless " -"you're using GitHub Enterprise Server." +"Please note that actions may or may not restrict API based access to " +"attributes. We're displaying the following icons for your overview to " +"understand these limits better:" msgstr "" -#: ../system/integrations/github.rst:50 -msgid "" -"Once completed, a new GitHub issues tab will appear in the ticket pane. 🎉" +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|api| This icon indicates the action affects the API." msgstr "" -#: ../system/integrations/github.rst:59 ../system/integrations/gitlab.rst:52 -msgid "Token verification is taking a long time" +#: ../system/core-workflows/how-do-they-work.rst:163 +msgid "api" msgstr "" -#: ../system/integrations/github.rst:56 ../system/integrations/gitlab.rst:49 -msgid "" -"Slight delays are normal (<2 min.), especially for systems under heavy load." +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|ui| This icon indicates the action only affects the web interface." msgstr "" -#: ../system/integrations/github.rst:58 -msgid "" -"Self-hosted administrators, please check your network settings to ensure " -"that your Zammad server can reach ``api.github.com``." +#: ../system/core-workflows/how-do-they-work.rst:167 +msgid "ui" msgstr "" -#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 -msgid "I reloaded the page and now the API token is gone" +#: ../system/core-workflows/how-do-they-work.rst:102 +msgid "show |ui|" msgstr "" -#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 -msgid "" -"This may indicate that Zammad is still verifying your API token. Try " -"reloading the page again in a couple minutes." +#: ../system/core-workflows/how-do-they-work.rst:102 +msgid "Display the chosen field. Allows setting of values." msgstr "" -#: ../system/integrations/gitlab.rst:2 -msgid "GitLab" +#: ../system/core-workflows/how-do-they-work.rst:109 +msgid "hide |ui|" msgstr "" -#: ../system/integrations/gitlab.rst:4 +#: ../system/core-workflows/how-do-they-work.rst:105 msgid "" -"Use GitLab integration to track GitLab issues directly within Zammad " -"tickets. Add issue hyperlinks and get a live summary of metadata like status " -"(open/closed), assignee, labels, and more." +"Hide the chosen field. However, it technically still allows setting the " +"field." msgstr "" -#: ../system/integrations/gitlab.rst:8 +#: ../system/core-workflows/how-do-they-work.rst:108 msgid "" -"Please note that our GitLab integration does not support merge requests." +"Please note that the field is **not** gone and still contains an existing " +"value (if set)! Consider *remove* instead, if you want this field to be gone." msgstr "" -#: ../system/integrations/gitlab.rst:None -msgid "Integration page for GitLab" +#: ../system/core-workflows/how-do-they-work.rst:112 +msgid "remove |ui|" msgstr "" -#: ../system/integrations/gitlab.rst:18 -msgid "" -"In your GitLab preferences, create a new API token under **Access Tokens**." +#: ../system/core-workflows/how-do-they-work.rst:112 +msgid "Entirely removes the field. The field value will not be evaluated." msgstr "" -#: ../system/integrations/gitlab.rst:20 -msgid "Under **Select scopes**, choose ``read_api`` only." +#: ../system/core-workflows/how-do-they-work.rst:115 +msgid "set mandatory |ui| |api|" msgstr "" -#: ../system/integrations/gitlab.rst:27 -msgid "🔒 **If you wish to link issues on any private repos...**" +#: ../system/core-workflows/how-do-they-work.rst:115 +msgid "Sets the field to mandatory." msgstr "" -#: ../system/integrations/gitlab.rst:29 -msgid "Your API token must belong to an account with access to those repos." +#: ../system/core-workflows/how-do-they-work.rst:118 +msgid "set optional |ui| |api|" msgstr "" -#: ../system/integrations/gitlab.rst:31 -msgid "Enter your new API token in Zammad and enable GitLab integration." +#: ../system/core-workflows/how-do-they-work.rst:118 +msgid "Sets the field to optional." msgstr "" -#: ../system/integrations/gitlab.rst:0 -msgid "Screencast showing how to configure Zammad's GitLab integration" +#: ../system/core-workflows/how-do-they-work.rst:124 +msgid "add option |ui| |api|" msgstr "" -#: ../system/integrations/gitlab.rst:40 -msgid "" -"Use the default API endpoint (``https://gitlab.com/api/graphql``) unless " -"you're a self-hosted GitLab user." +#: ../system/core-workflows/how-do-they-work.rst:121 +msgid "Allows adding options to tree selects or selects." msgstr "" -#: ../system/integrations/gitlab.rst:43 +#: ../system/core-workflows/how-do-they-work.rst:123 msgid "" -"Once completed, a new GitLab issues tab will appear in the ticket pane. 🎉" +"You have to use the \"remove option\" before performing this action. It " +"allows you to use *existing* configured values." msgstr "" -#: ../system/integrations/gitlab.rst:51 -msgid "" -"Self-hosted administrators, please check your network settings to ensure " -"that your Zammad server can reach ``gitlab.com``." +#: ../system/core-workflows/how-do-they-work.rst:128 +msgid "remove option |ui| |api|" msgstr "" -#: ../system/integrations/i-doit.rst:2 -msgid "i-doit" +#: ../system/core-workflows/how-do-they-work.rst:127 +msgid "" +"Allows removing options from tree selects or selects. It allows you to use " +"*existing* configured values." msgstr "" -#: ../system/integrations/i-doit.rst:4 -msgid "" -"`i-doit `_ is an open-source **configuration " -"management database** - in other words, a tool for keeping tabs on every " -"single piece of your physical and digital infrastructure, from network " -"equipment to virtual machines on down to the faceplates on your rack shelves " -"and more." +#: ../system/core-workflows/how-do-they-work.rst:134 +msgid "set fixed to |ui| |api|" msgstr "" -#: ../system/integrations/i-doit.rst:10 -msgid "" -"What's that got to do with Zammad? Well, if you used tickets to track issues " -"with all that hardware, you might start wishing there was a way they could " -"talk to each other." +#: ../system/core-workflows/how-do-they-work.rst:131 +msgid "Reduces the available options by your selection." msgstr "" -#: ../system/integrations/i-doit.rst:14 -msgid "Zammad gives you two:" +#: ../system/core-workflows/how-do-they-work.rst:133 +msgid "" +"This reduces your workflows in terms of *add option* and *remove option*." msgstr "" -#: ../system/integrations/i-doit.rst:17 -msgid "1. Add i-doit Links to Zammad Tickets" +#: ../system/core-workflows/how-do-they-work.rst:137 +msgid "fill in |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:20 ../system/integrations/i-doit.rst:80 -msgid "What Users See" +#: ../system/core-workflows/how-do-they-work.rst:137 +msgid "Allows filling in of string and integer fields with your values." msgstr "" -#: ../system/integrations/i-doit.rst:26 -msgid "i-doit integration in Zammad's ticket pane" +#: ../system/core-workflows/how-do-they-work.rst:141 +msgid "fill in empty |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:26 +#: ../system/core-workflows/how-do-they-work.rst:140 msgid "" -"The i-doit integration will appear under a new 🖨 tab in the ticket pane." +"Allows filling in of string and integer fields with your values **if the " +"field is empty**." msgstr "" -#: ../system/integrations/i-doit.rst:28 -msgid "" -"i-doit integration puts a new tab in Zammad's ticket pane where you can add " -"links to existing i-doit devices for easy reference. (See our :user-docs:" -"`user documentation ` to learn " -"how it works in practice)." +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "select |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:36 ../system/integrations/i-doit.rst:93 -msgid "How to Set it Up" +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "Select a specific value within a select, tree select or boolean field." msgstr "" -#: ../system/integrations/i-doit.rst:38 -msgid "" -"It requires i-doit's `API Add-on `_. Make sure to have it properly set up. Use the following setting:" +#: ../system/core-workflows/how-do-they-work.rst:153 +msgid "auto select |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:42 -msgid "Active: ``Yes``" +#: ../system/core-workflows/how-do-they-work.rst:147 +msgid "Helps users with tree select and select fields:" msgstr "" -#: ../system/integrations/i-doit.rst:43 -msgid "Enforce authentication by username and password: ``No``" +#: ../system/core-workflows/how-do-they-work.rst:149 +msgid "" +"If the field has only one option available for selection and no value yet, " +"the value will be automatically set." msgstr "" -#: ../system/integrations/i-doit.rst:45 +#: ../system/core-workflows/how-do-they-work.rst:152 msgid "" -"To set it up, enable the integration in the Zammad admin panel under " -"**System > Integrations > i-doit**:" +"This option only works if you have one value and doesn't work if there is " +"more than one option available." msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "i-doit settings within the integration pages" +#: ../system/core-workflows/how-do-they-work.rst:157 +msgid "set readonly |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:53 -msgid "The root URL of your i-doit installation." +#: ../system/core-workflows/how-do-they-work.rst:156 +msgid "" +"Allows you to display an attribute as read only (which means no changes are " +"possible)." msgstr "" -#: ../system/integrations/i-doit.rst:62 -msgid "API token" +#: ../system/core-workflows/how-do-they-work.rst:161 +msgid "unset readonly |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:56 +#: ../system/core-workflows/how-do-they-work.rst:160 msgid "" -"Found in the i-doit admin panel under **Interfaces / external data > JSON-" -"RPC API > Common Settings**." +"In case a workflow set the field in question to read only, you can undo this " +"with option above." msgstr "" -#: ../system/integrations/i-doit.rst:0 -msgid "i-doit administration interface with API configuration" +#: ../system/core-workflows/how-do-they-work.rst:172 +msgid "Stop after match" msgstr "" -#: ../system/integrations/i-doit.rst:67 -msgid "Client ID" +#: ../system/core-workflows/how-do-they-work.rst:174 +msgid "" +"Here you can decide if other workflows are executed after the current one." msgstr "" -#: ../system/integrations/i-doit.rst:65 -msgid "A unique name to identify Zammad within i-doit." +#: ../system/core-workflows/how-do-they-work.rst:176 +msgid "" +"If set to ``no`` (default), further workflows will be executed if they match " +"the condition. In this case, it is possible that your actions from the " +"current workflow can be overwritten by another workflow." +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:180 +msgid "" +"If set to ``yes``, no further worflows will be executed after the current " +"one." msgstr "" -#: ../system/integrations/i-doit.rst:67 -msgid "(Zammad does not require you to enter a value here, but i-doit might!)" +#: ../system/core-workflows/how-do-they-work.rst:184 +msgid "Priority" msgstr "" -#: ../system/integrations/i-doit.rst:70 +#: ../system/core-workflows/how-do-they-work.rst:186 msgid "" -"Here you can decide if the certificate of your i-doit system has to be " -"verified or not. In case you are using custom certificates, please have a " -"look at :doc:`how to add them to Zammad `." +"You can define the sequence, in which the workflows are executed. The " +"default value is ``500``." msgstr "" -#: ../system/integrations/i-doit.rst:77 -msgid "2. List / Create Zammad Tickets in i-doit" +#: ../system/core-workflows/how-do-they-work.rst:189 +msgid "" +"The workflows are executed in ascending order by their priority. That means " +"lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "Zammad integration in i-doit's device view" -msgstr "" +#: ../system/core-workflows/learn-by-example.rst:2 +#, fuzzy +msgid "Learn by Example" +msgstr "Ejemplo" -#: ../system/integrations/i-doit.rst:86 +#: ../system/core-workflows/learn-by-example.rst:4 msgid "" -"i-doit's ticket system integration gives you a way to see all the tickets " -"for a given device without ever leaving i-doit. (See our :user-docs:`user " -"documentation ` to learn how it " -"works in practice)." +"This page provides some basic examples for Core Workflows. Of course you can " +"build much more complex workflows if needed." msgstr "" -#: ../system/integrations/i-doit.rst:95 +#: ../system/core-workflows/learn-by-example.rst:7 msgid "" -"Enable this integration in the i-doit admin panel under **Interfaces / " -"external data > Trouble Ticket System (TTS) > Configuration**:" +"To learn about Core Workflows in detail, first go to :doc:`how-do-they-work`." msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "i-doit administration interface with TTS configuration" -msgstr "" +#: ../system/core-workflows/learn-by-example.rst:10 +#, fuzzy +msgid "Group Based Examples" +msgstr "Ejemplo" -#: ../system/integrations/i-doit.rst:104 -msgid "TTS-Type" +#: ../system/core-workflows/learn-by-example.rst:12 +msgid "" +"All following workflows have the same base configurations. The workflow may " +"not use them all." msgstr "" -#: ../system/integrations/i-doit.rst:104 -msgid "``Zammad``" -msgstr "" +#: ../system/core-workflows/learn-by-example.rst:15 +#, fuzzy +msgid "Groups:" +msgstr "grupo" -#: ../system/integrations/i-doit.rst:115 -msgid "Username / Password" +#: ../system/core-workflows/learn-by-example.rst:20 +msgid "Attributes:" msgstr "" -#: ../system/integrations/i-doit.rst:107 -msgid "Login credentials for a Zammad agent." +#: ../system/core-workflows/learn-by-example.rst:22 +msgid "Category (Single tree selection field, not mandatory, agents only)" msgstr "" -#: ../system/integrations/i-doit.rst:109 +#: ../system/core-workflows/learn-by-example.rst:23 msgid "" -"This agent must have **read permission** for all :doc:`groups ` that plan on using the i-doit integration." +"Approved (Boolean field, not mandatory, not shown, ``false`` as default)" msgstr "" -#: ../system/integrations/i-doit.rst:113 -msgid "" -"You may even wish to create a dedicated agent account just for this " -"integration (otherwise, if the agent ever changes her password, you will " -"have to remember to update it here)." +#: ../system/core-workflows/learn-by-example.rst:24 +msgid "Operating System (Text field, not mandatory, not shown)" msgstr "" -#: ../system/integrations/i-doit.rst:117 -msgid "URL incl. protocol" +#: ../system/core-workflows/learn-by-example.rst:25 +msgid "Software used (Single selection field, not mandatory, not shown)" msgstr "" -#: ../system/integrations/i-doit.rst:118 -msgid "``https://your.zammad.domain``" +#: ../system/core-workflows/learn-by-example.rst:68 +msgid "Group specific values and fields" msgstr "" -#: ../system/integrations/index.rst:2 -msgid "Integrations" +#: ../system/core-workflows/learn-by-example.rst:28 +msgid "" +"This workflow set depends on the category field. It reduces the available " +"set of values based on the group selected." msgstr "" -#: ../system/integrations/index.rst:4 -msgid "" -"Zammad offers numerous integrations that add rich features to your instance." +#: ../system/core-workflows/learn-by-example.rst:33 +msgid "Workflow 2nd Level group" msgstr "" -#: ../system/integrations/index.rst:6 -msgid "We're still working on this part of our documentation, stay tight!" +#: ../system/core-workflows/learn-by-example.rst:35 +msgid "" +"This reduces the category options to ``2nd Level/*``, ``Internal/*`` and " +"``Others``. It also sets further required fields to mandatory and visible." msgstr "" -#: ../system/integrations/index.rst:10 -msgid "Integrations for Phone Systems" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for 2nd level" msgstr "" -#: ../system/integrations/index.rst:14 -msgid "" -"Your VoIP provider or telephony system is not listed? Possibly your provider " -"supports Zammad by using the generic CTI - if you're unsure ask your " -"provider." +#: ../system/core-workflows/learn-by-example.rst:43 +msgid "Workflow Support group" msgstr "" -#: ../system/integrations/index.rst:18 +#: ../system/core-workflows/learn-by-example.rst:45 msgid "" -"Provider does not support Zammad? Consider creating a `feature request in " -"the Zammad Community `_." +"This reduces the category options to ``Support/*``, ``Internal/*`` and " +"``Others``. It also sets further required fields to visible." msgstr "" -#: ../system/integrations/index.rst:31 -msgid "Integrations for Authentication and Customers" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for support" msgstr "" -#: ../system/integrations/index.rst:44 -msgid "Integrations for Monitoring Systems" +#: ../system/core-workflows/learn-by-example.rst:53 +msgid "Workflow Sales group" msgstr "" -#: ../system/integrations/index.rst:46 -msgid "This section currently misses the following integrations:" +#: ../system/core-workflows/learn-by-example.rst:55 +msgid "" +"This reduces the category options to ``Sales/*``, ``Internal/*`` and " +"``Others``." msgstr "" -#: ../system/integrations/index.rst:48 -msgid "Icinga" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for sales" msgstr "" -#: ../system/integrations/index.rst:49 -msgid "Monit" +#: ../system/core-workflows/learn-by-example.rst:68 +#: ../system/integrations/slack.rst:88 +msgid "The Result" msgstr "" -#: ../system/integrations/index.rst:50 -msgid "Nagios" +#: ../system/core-workflows/learn-by-example.rst:63 +msgid "" +"This is what the agent would experience with the above workflows in place." msgstr "" -#: ../system/integrations/index.rst:60 -msgid "Integrations for Issue Trackers" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "" +"Workflow shows objects and limits options based on selections on the group" msgstr "" -#: ../system/integrations/index.rst:70 -msgid "Other Integrations" +#: ../system/core-workflows/learn-by-example.rst:90 +msgid "Approval process" msgstr "" -#: ../system/integrations/index.rst:72 +#: ../system/core-workflows/learn-by-example.rst:71 msgid "" -"This section will hold any other integration that can't be grouped up (yet)." +"In this case ``approved`` is visible to agents by default. For this " +"workflow, an additional role ``Approval person`` is required (no further " +"permissions)." msgstr "" -#: ../system/integrations/ldap/index.rst:2 -msgid "LDAP / Active Directory" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that restricts an approval attribute to specific roles" msgstr "" -#: ../system/integrations/ldap/index.rst:4 +#: ../system/core-workflows/learn-by-example.rst:81 msgid "" -"Zammad comes with a powerful LDAP integration that allows you to have a " -"single source of truth. By this you reduce the number of login credentials " -"your user has to remember." +"This workflow may work best in combination with a :doc:`trigger ` but technically, this is not required." msgstr "" -#: ../system/integrations/ldap/index.rst:10 +#: ../system/core-workflows/learn-by-example.rst:84 msgid "" -"The LDAP source is also a perfect candidate for Zammad's :docs:`Kerberos " -"Single Sign-On ` but also works as addition " -"to other :doc:`/settings/security/third-party`." +"Select fields may be a better approach because they allow more values than " +"just a simple ``true`` or ``false``." msgstr "" -#: ../system/integrations/ldap/index.rst:None -msgid "Zammands LDAP management page" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "" +"Workflow fixes possible values of \"Approved ?\" to a specific selection " +"depending on the users role" msgstr "" -#: ../system/integrations/ldap/index.rst:25 -msgid "📝 :doc:`manage`" +#: ../system/core-workflows/learn-by-example.rst:103 +msgid "State dependent mandatory fields" msgstr "" -#: ../system/integrations/ldap/index.rst:25 -msgid "Add, modify, remove or re-arrange your LDAP-Sources as needed." +#: ../system/core-workflows/learn-by-example.rst:93 +msgid "" +"This workflow sets ``Category`` to mandatory if the agent wants to set the " +"states ``closed`` or ``pending close`` to enforce categorization." msgstr "" -#: ../system/integrations/ldap/index.rst:30 -msgid "Before you continue, please note the following limitations." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that sets fields to mandatory on specific states" msgstr "" -#: ../system/integrations/ldap/index.rst:32 -msgid "Mapping / Synchronizing organizations is not possible" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "" +"Workflow sets category field to mandatory upon choosing closed or pending " +"close as state" msgstr "" -#: ../system/integrations/ldap/index.rst:36 -msgid "" -"You may want to consider using domain based assignments to overcome this " -"issue. Learn more on :doc:`/manage/organizations/index`." +#: ../system/core-workflows/learn-by-example.rst:106 +msgid "Manual Ticket Handover Process" msgstr "" -#: ../system/integrations/ldap/index.rst:39 -msgid "" -"Zammad's LDAP sync is one way. Editing user settings or permissions may be " -"overwritten upon the next sync depending on your configuration." +#: ../system/core-workflows/learn-by-example.rst:108 +msgid "This example covers the handover of a ticket from one agent to another:" msgstr "" -#: ../system/integrations/ldap/index.rst:41 -msgid "Nested groups are not supported." +#: ../system/core-workflows/learn-by-example.rst:110 +msgid "" +"When the ticket owner is modified, a new text field (\"Handover\") shows up " +"for a comment" msgstr "" -#: ../system/integrations/ldap/index.rst:42 -msgid "Synchronizing user avatars from LDAP is not supported." +#: ../system/core-workflows/learn-by-example.rst:112 +msgid "" +"This may only be visible when the owner is changed, therefore it has to be " +"hidden in general" msgstr "" -#: ../system/integrations/ldap/index.rst:43 -msgid "Unlike user filters, group filters cannot be changed." +#: ../system/core-workflows/learn-by-example.rst:114 +msgid "The input in this handover text field is mandatory" msgstr "" -#: ../system/integrations/ldap/index.rst:44 +#: ../system/core-workflows/learn-by-example.rst:115 msgid "" -"When a user originates from an LDAP server, Zammad will try to verify the " -"login credentials against LDAP first - if this fails Zammad will check its " -"local database." +"After submitting changes, the value of the handover field must be added as " +"an note to the ticket (via trigger)" msgstr "" -#: ../system/integrations/ldap/index.rst:50 -msgid "" -"Users can have local passwords even if they're LDAP users! You can learn " -"more about user accounts in general on :doc:`/manage/users/index`." +#: ../system/core-workflows/learn-by-example.rst:121 +msgid "Hiding handover field" msgstr "" -#: ../system/integrations/ldap/index.rst:54 -msgid "" -"When several LDAP sources contain the same user (meaning the same email " -"address), the user in question will be updated with every source configured. " -"*The last LDAP source will win.*" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Hiding the handover field in core workflows" msgstr "" -#: ../system/integrations/ldap/index.rst:58 -msgid "" -"This is subject to change with `Issue 4109 `_ in the future." +#: ../system/core-workflows/learn-by-example.rst:126 +msgid "Showing handover field and setting it to mandatory" msgstr "" -#: ../system/integrations/ldap/index.rst:60 -msgid "" -"Synchronization statistics currently affect *all* configured LDAP sources. " -"This also applies for newly added or updated sources." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Showing the handover field and set it as mandatory" msgstr "" -#: ../system/integrations/ldap/index.rst:63 -msgid "" -"This is subject to change with `Issue 4108 `_ in the future." +#: ../system/core-workflows/learn-by-example.rst:131 +msgid "Trigger writing handover input to a new article" msgstr "" -#: ../system/integrations/ldap/index.rst:65 -msgid "" -"Zammad currently has limited fallback server support. You can workaround " -"this by providing several sources - however, ensure to have the exact same " -"configuration on your fallback." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Write handover content to a new article" msgstr "" -#: ../system/integrations/ldap/index.rst:69 +#: ../system/core-workflows/learn-by-example.rst:133 msgid "" -"This is subject to improve with `Issue 4107 `_ in the future." +"As a result, the ticket includes an article of the type note which includes " +"the predefined text and the handover comment." msgstr "" -#: ../system/integrations/ldap/index.rst:76 -msgid "" -"This section holds all requests Zammad handled for all LDAP sources. These " -"entries can either contain synchronization information or logins " -"(authentication attempts via Zammad's login interface)." +#: ../system/core-workflows/limitations.rst:6 +msgid "Core Workflows do not replace Triggers" msgstr "" -#: ../system/integrations/ldap/index.rst:80 +#: ../system/core-workflows/limitations.rst:5 msgid "" -"By clicking on any request, Zammad will provide even more information. The " -"provided information can be useful when something does not work as expected." +"Workflows manipulate the behavior of fields. However, they do not set values " +"in fields because of actions." msgstr "" -#: ../system/integrations/ldap/index.rst:85 -msgid "" -"Especially a LDAP synchronization can cause many log entries. The web " -"interface will always limit the number of shown entries to the last 50 " -"entries." +#: ../system/core-workflows/limitations.rst:16 +msgid "API calls are only partly affected" msgstr "" -#: ../system/integrations/ldap/index.rst:None +#: ../system/core-workflows/limitations.rst:9 msgid "" -"Screencast showing LDAP integration log entries and a detail view on\n" -"an entry." +"Some options affect UI only and thus do not restrict responses and calls." msgstr "" -#: ../system/integrations/ldap/manage.rst:2 -msgid "Manage LDAP-Sources" +#: ../system/core-workflows/limitations.rst:11 +msgid "This affects the following actions:" msgstr "" -#: ../system/integrations/ldap/manage.rst:6 -msgid "" -"Please keep in mind all current limitations for the LDAP synchronization. " -"This will help to understand scopes of the following operations better." +#: ../system/core-workflows/limitations.rst:13 +msgid "select" msgstr "" -#: ../system/integrations/ldap/manage.rst:65 -msgid "Add new source" +#: ../system/core-workflows/limitations.rst:14 +msgid "auto select" msgstr "" -#: ../system/integrations/ldap/manage.rst:10 -msgid "" -"Using the *New Source* button allows you to add new LDAP sources to your " -"installation. You're not limited in the number of sources, however, keep in " -"mind that many sources will also take more time to synchronize." +#: ../system/core-workflows/limitations.rst:15 +msgid "show" msgstr "" -#: ../system/integrations/ldap/manage.rst:14 -msgid "" -"You can choose between different encryption types, namely *SSL* and " -"*STARTTLS* or none of them (\"*No SSL*\"). If you choose *SSL* or " -"*STARTTLS*, Zammad will display an additional *SSL verification* option that " -"allows you to disable the verification, e.g. for self-signed SSL " -"certificates. You can also tell Zammad to use a different port by appending " -"``:`` to your hostname/IP." +#: ../system/core-workflows/limitations.rst:16 +msgid "hide" msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "" -"Screenshot of configuring a new LDAP source with SSL encryption and SSL " -"verification" +#: ../system/core-workflows/limitations.rst:25 +msgid "Some fields stay unavailable to customers" msgstr "" -#: ../system/integrations/ldap/manage.rst:26 +#: ../system/core-workflows/limitations.rst:19 msgid "" -"New Source with SSL transport security enabled and certificate verification" +"For technical and security reasons, some default fields (the pale ones you " +"can't edit) stay unavailable for display and usage on customer permissions." msgstr "" -#: ../system/integrations/ldap/manage.rst:30 +#: ../system/core-workflows/limitations.rst:23 msgid "" -"Using an user filter can be a good idea if you only require a small subset " -"of your LDAP users in Zammad." +"If you require your customers to change e.g. priorities, please consider " +"using workarounds via :doc:`/system/objects` and :doc:`/manage/trigger`." msgstr "" -#: ../system/integrations/ldap/manage.rst:42 -msgid "This especially affects inactive users" +#: ../system/core-workflows/limitations.rst:29 +msgid "Ticket title changes not supported in edit mask" msgstr "" -#: ../system/integrations/ldap/manage.rst:34 +#: ../system/core-workflows/limitations.rst:28 msgid "" -"As every LDAP behaves differently on which attributes and how they are set, " -"Zammad doesn't care about any flags." +"It is currently not possible to perform changes of the ticket title in the " +"edit mask (e.g. renaming, set to read-only)." msgstr "" -#: ../system/integrations/ldap/manage.rst:37 -msgid "" -"Users that no longer are returned by your LDAP source will automatically be " -"set to inactive. Zammad assumes that the user was deactivated." +#: ../system/core-workflows/limitations.rst:37 +msgid "What is out of scope of Core Workflows?" msgstr "" -#: ../system/integrations/ldap/manage.rst:41 +#: ../system/core-workflows/limitations.rst:32 msgid "" -"Users will never be removed automatically! If you want to remove obsolete " -"users, use :doc:`/system/data-privacy`." +"There are some things that would count as workflow but are either done via :" +"doc:`/manage/trigger` or :doc:`/manage/scheduler`." msgstr "" -#: ../system/integrations/ldap/manage.rst:46 -msgid "Active Directory admins" +#: ../system/core-workflows/limitations.rst:35 +msgid "Such as (but not limited to):" msgstr "" -#: ../system/integrations/ldap/manage.rst:45 -msgid "" -"Active Directories are quite specific on how to filter for active users only " -"- please see the `Microsoft documentation `_ for more " -"information." +#: ../system/core-workflows/limitations.rst:37 +msgid "up- or downgrade permissions of users" msgstr "" -#: ../system/integrations/ldap/manage.rst:51 -msgid "" -"*Do not* manually write pathes of either LDAP attributes or groups. If " -"Zammad does not display them, it either cannot find them or you have a lot " -"of users that don't have the attributes populated." +#: ../system/core-workflows/limitations.rst:38 +msgid "affecting article creation or listing" msgstr "" -#: ../system/integrations/ldap/manage.rst:55 -msgid "" -"Zammad will always only return attributes that are filled - this reduces the " -"returned list of attributes greatly." +#: ../system/data-privacy.rst:2 +msgid "Data Privacy" msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing how to add a new LDAP source" +#: ../system/data-privacy.rst:4 +msgid "" +"For compliance with GDPR and other data privacy laws, you may wish to " +"**permanently delete users from the system**, along with **all of their " +"associated tickets**." msgstr "" -#: ../system/integrations/ldap/manage.rst:63 +#: ../system/data-privacy.rst:8 msgid "" -"If your LDAP system doesn't allow anonymous bind, Zammad detects it and " -"provides you an editable \"Base DN\" *text* field instead of a prefilled " -"*select* field." +"You can create manual deletion tasks or even automated deletion tasks for " +"tickets and users based on custom conditions via :doc:`scheduler `!" msgstr "" -#: ../system/integrations/ldap/manage.rst:81 -msgid "Review or edit existing source" +#: ../system/data-privacy.rst:12 +msgid "" +"Access to this panel requires ``admin.data_privacy`` permissions (introduced " +"in Zammad 3.5)." msgstr "" -#: ../system/integrations/ldap/manage.rst:68 +#: ../system/data-privacy.rst:15 msgid "" -"Clicking on a LDAP source will provide a configuration and mapping overview." +"On older systems that have not been updated yet, customers can also be :docs:" +"`deleted via the Zammad console `." msgstr "" -#: ../system/integrations/ldap/manage.rst:70 -msgid "" -"If needed you can then use the *Change* button to update either the name, " -"active state or the whole configuration. If you're changing the whole " -"configuration, the dialogue will be identical to the source creation." +#: ../system/data-privacy.rst:22 +msgid "User deletion dialog in the Data Privacy panel" msgstr "" -#: ../system/integrations/ldap/manage.rst:76 +#: ../system/data-privacy.rst:22 msgid "" -"Did your LDAP server change? Different LDAP servers have different " -"structures and default attributes. This causes the LDAP synchronization to " -"likely fail. Consider removing the affected source and re-add it." +"The user deletion dialog lists some of the tickets that will be removed from " +"the system along with the user." msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing the update of the source name." +#: ../system/data-privacy.rst:27 +#, fuzzy +msgid "Deleting Users via GUI" +msgstr "Verificación de correo electrónico" + +#: ../system/data-privacy.rst:29 +msgid "🔥 **All deletions are FINAL!**" msgstr "" -#: ../system/integrations/ldap/manage.rst:89 -msgid "Re-arrange LDAP source's order" +#: ../system/data-privacy.rst:31 +msgid "Once you click “Delete”, the action cannot be canceled or undone." msgstr "" -#: ../system/integrations/ldap/manage.rst:84 +#: ../system/data-privacy.rst:33 msgid "" -"You can change the synchronization order for each source at any time. Zammad " -"will synchronize the sources from top to bottom." +"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." msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "" -"Screencasting showing how to change the source order by using\n" -"drag and drop." +#: ../system/data-privacy.rst:36 +msgid "**The following records cannot be deleted:**" msgstr "" -#: ../system/integrations/ldap/manage.rst:101 -msgid "Remove a source" +#: ../system/data-privacy.rst:38 +msgid "your own account" msgstr "" -#: ../system/integrations/ldap/manage.rst:92 -msgid "" -"If you no longer need the a LDAP source or simply want to start over, you " -"can remove them at any time. This will not remove synchronized users, data " -"synchronized or permissions." +#: ../system/data-privacy.rst:39 +msgid "the system's last remaining administrator account" msgstr "" -#: ../system/integrations/ldap/manage.rst:98 -msgid "" -"Not sure if you'd need the source later on? Set the source to inactive " -"instead of removing it - see *Review or edit existing source* for more." +#: ../system/data-privacy.rst:42 +msgid "Step 1: Find a User / Confirm Deletion" msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing how to remove LDAP sources." +#: ../system/data-privacy.rst:44 +msgid "There are three ways to access the user deletion dialog:" msgstr "" -#: ../system/integrations/pgp/index.rst:2 -msgid "PGP" +#: ../system/data-privacy.rst:51 +msgid "**from the user's profile**" msgstr "" -#: ../system/integrations/pgp/index.rst:7 -msgid "" -"Pretty Good Privacy (PGP) is another method for secure email communication. " -"With PGP, you can exchange **signed** and **encrypted** messages with others." +#: ../system/data-privacy.rst:0 +msgid "Accessing the user deletion dialog in a user profile" msgstr "" -#: ../system/integrations/pgp/index.rst:13 -#: ../system/integrations/smime/index.rst:17 -msgid "Signing" +#: ../system/data-privacy.rst:51 +msgid "Click **Action > Delete**." +msgstr "" + +#: ../system/data-privacy.rst:58 +msgid "**in the “Manage > Users” Admin Panel**" msgstr "" -#: ../system/integrations/pgp/index.rst:11 -msgid "is a proof that a message hasn't been manipulated on its way." +#: ../system/data-privacy.rst:0 +msgid "Accessing the user deletion dialog under “Users” in the Admin Panel" msgstr "" -#: ../system/integrations/pgp/index.rst:13 -msgid "" -"In other words, it guarantees message **integrity** and **authenticity**." +#: ../system/data-privacy.rst:58 +msgid "Use the **⋮ Actions** menu for the target user." msgstr "" -#: ../system/integrations/pgp/index.rst:19 -#: ../system/integrations/smime/index.rst:22 -msgid "Encryption" +#: ../system/data-privacy.rst:66 ../system/data-privacy.rst:104 +msgid "**in the “System > Data Privacy” Admin Panel**" msgstr "" -#: ../system/integrations/pgp/index.rst:16 -#: ../system/integrations/smime/index.rst:20 +#: ../system/data-privacy.rst:0 msgid "" -"scrambles a message so that it can only be unscrambled by the intended " -"recipient." +"Accessing the user deletion dialog under “Data Privacy” in the Admin Panel" msgstr "" -#: ../system/integrations/pgp/index.rst:19 +#: ../system/data-privacy.rst:65 msgid "" -"In other words, it guarantees message **privacy** and **data security**." +"Use the **New Deletion Task** button. Search for users by name or email " +"address." msgstr "" -#: ../system/integrations/pgp/index.rst:25 -msgid "Screenshot of ticket creation with encrypt and sign buttons" +#: ../system/data-privacy.rst:79 +msgid "**Delete organizations**" msgstr "" -#: ../system/integrations/pgp/index.rst:25 +#: ../system/data-privacy.rst:69 msgid "" -"Once PGP has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " -"appear in the ticket composer." +"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:" msgstr "" -#: ../system/integrations/pgp/index.rst:28 -msgid "**Sign button not visible?**" +#: ../system/data-privacy.rst:0 +msgid "Deleting an organization via the user deletion dialog" msgstr "" -#: ../system/integrations/pgp/index.rst:30 +#: ../system/data-privacy.rst:78 msgid "" -"Please note that the signing of emails is based on the outgoing email " -"account. That means you have to choose a group with a sender email account, " -"which has a private key assigned." +"If this option does not appear, make sure there are no pending deletion " +"tasks for other customers from this organization." msgstr "" -#: ../system/integrations/pgp/index.rst:35 -msgid "Handling of Keys" +#: ../system/data-privacy.rst:82 +msgid "Step 2: Monitor Deletion Job Status" msgstr "" -#: ../system/integrations/pgp/index.rst:36 +#: ../system/data-privacy.rst:84 msgid "" -"To use the PGP function, you have to enable the integration (PGP) by " -"switching the toggle to *enabled*." +"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:" msgstr "" -#: ../system/integrations/pgp/index.rst:39 -msgid "" -"You can add keys by clicking the *add key* button. The keys can be imported " -"from a file or you can paste the content of the key in the text box." +#: ../system/data-privacy.rst:98 +msgid "**in the Activity Stream**" msgstr "" -#: ../system/integrations/pgp/index.rst:42 -msgid "**Which keys do I have to import?**" +#: ../system/data-privacy.rst:0 +msgid "Activity Stream showing data privacy tasks" msgstr "" -#: ../system/integrations/pgp/index.rst:44 +#: ../system/data-privacy.rst:94 msgid "" -"For **signing** *outgoing* emails, you have to import the private key of " -"your Zammad email account." +"For each deleted user, the Activity Stream will be updated twice—once when " +"the task is created, and once when it's complete." msgstr "" -#: ../system/integrations/pgp/index.rst:47 +#: ../system/data-privacy.rst:97 msgid "" -"For **encrypting** *outgoing* emails, you have to import the public key of " -"the customer's email account." +"These notifications are only visible to users with ``admin.data_privacy`` " +"permissions." msgstr "" -#: ../system/integrations/pgp/index.rst:50 +#: ../system/data-privacy.rst:0 msgid "" -"For **verifying the signature** of signed *incoming* emails, you have to " -"import the public key of the customer." +"The task list within Data Privacy shows removals being in progress and " +"completed." msgstr "" -#: ../system/integrations/pgp/index.rst:53 -msgid "" -"For **decrypting** of encrypted *incoming* emails, you have to import the " -"private key of your Zammad email account." +#: ../system/data-privacy.rst:107 +msgid "Frequently Asked Questions" msgstr "" -#: ../system/integrations/pgp/index.rst:57 -msgid "Import Keys From a File" +#: ../system/data-privacy.rst:121 +msgid "What happens if I receive an email from a deleted customer?" msgstr "" -#: ../system/integrations/pgp/index.rst:58 -msgid "You can import keys from a file in the section **Upload key**:" +#: ../system/data-privacy.rst:110 +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/integrations/pgp/index.rst:None -msgid "Screenshot of adding a key via file" +#: ../system/data-privacy.rst:115 +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**." msgstr "" -#: ../system/integrations/pgp/index.rst:64 -msgid "" -"**Supported file formats:** ASCII-armor as well as binary GPG format " -"(basically any GPG supported key format) is supported here." +#: ../system/data-privacy.rst:130 +msgid "What about user information stored in internal notes or other messages?" msgstr "" -#: ../system/integrations/pgp/index.rst:68 -msgid "Import Keys by Pasting the Content" +#: ../system/data-privacy.rst:124 +msgid "" +"The deletion process removes **user accounts and associated tickets only**." msgstr "" -#: ../system/integrations/pgp/index.rst:69 -msgid "You can also paste the key's content in the section **paste key**:" +#: ../system/data-privacy.rst:126 +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." msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of adding a key via pasting" +#: ../system/data-privacy.rst:137 +msgid "I deleted an user and can still see a message they sent!" msgstr "" -#: ../system/integrations/pgp/index.rst:75 +#: ../system/data-privacy.rst:133 msgid "" -"**Supported format:** Please note that only ASCII-armor is supported here." +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:78 -#, fuzzy -msgid "Deleting Keys" -msgstr "Verificación de correo electrónico" +#: ../system/data-privacy.rst:141 +msgid "I removed a customer, now my reporting is off!" +msgstr "" -#: ../system/integrations/pgp/index.rst:79 +#: ../system/data-privacy.rst:140 msgid "" -"If you want to delete a specific key, you can do it by clicking on the menu " -"in the *actions* column and select **delete**:" +"When removing users and their tickets, all references are removed. This also " +"affects e.g. Reporting - these information are lost." msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of deleting a key" +#: ../system/data-privacy.rst:145 +msgid "How long does Zammad store created tasks?" msgstr "" -#: ../system/integrations/pgp/index.rst:88 -msgid "Downloading Keys" +#: ../system/data-privacy.rst:144 +msgid "" +"Please see the on-premise data section of the :docs:`data privacy ` chapter." msgstr "" -#: ../system/integrations/pgp/index.rst:89 +#: ../system/data-privacy.rst:150 +msgid "What about re-assigned tickets? I want to delete them, too." +msgstr "" + +#: ../system/data-privacy.rst:148 msgid "" -"If you want to download your keys, you can do this as well via corresponding " -"action buttons. Depending on the key, you can choose wether you want to " -"download the private or the public key." +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:95 -#: ../system/integrations/smime/manage-certificates.rst:76 -msgid "Default Behavior" +#: ../system/data-privacy.rst:154 +msgid "Why are there so many deletion task entries, I didn't create them!" msgstr "" -#: ../system/integrations/pgp/index.rst:96 +#: ../system/data-privacy.rst:153 msgid "" -"Here you can adjust on per group basis, if *sign* and *encryption* is on or " -"off by default. Please be aware, that agents can always override the setting " -"for each individual article." +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Adjusting default behavior on per group basis" +#: ../system/integrations/checkmk/admin-panel-reference.rst:2 +msgid "Admin Panel Reference" msgstr "" -#: ../system/integrations/pgp/index.rst:107 +#: ../system/integrations/checkmk/admin-panel-reference.rst:None +msgid "Screenshot of Checkmk settings overview" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:12 msgid "" -"Here you can see the last actions regarding signing and encryption and if " -"they were successful." +"Which :doc:`group ` should Checkmk tickets be assigned " +"to as a default (*i.e.,* when none is specified)?" msgstr "" -#: ../system/integrations/pgp/index.rst:117 -msgid "**Sign button is not visible, but keys are imported.**" +#: ../system/integrations/checkmk/admin-panel-reference.rst:15 +msgid "(Applies to :ref:`API alerts ` only.)" msgstr "" -#: ../system/integrations/pgp/index.rst:115 -msgid "Did you choose a group in the ticket?" +#: ../system/integrations/checkmk/admin-panel-reference.rst:21 +msgid "Auto close" msgstr "" -#: ../system/integrations/pgp/index.rst:116 +#: ../system/integrations/checkmk/admin-panel-reference.rst:18 msgid "" -"Did you import a private key for the email adress, which is used for " -"outgoing emails in the group?" +"Should Zammad automatically close tickets if a service has recovered on its " +"own?" msgstr "" -#: ../system/integrations/pgp/index.rst:122 -msgid "**How to obtain keys?**" +#: ../system/integrations/checkmk/admin-panel-reference.rst:21 +msgid "(Agents will receive notifications for such closures as appropriate.)" msgstr "" -#: ../system/integrations/pgp/index.rst:120 -msgid "" -"You can create them yourself! There are some good tutorials on the web on " -"how to create them. Providing keys to Zammad is a prerequisite to use the " -"PGP feature." +#: ../system/integrations/checkmk/admin-panel-reference.rst:30 +msgid "Auto-close state" msgstr "" -#: ../system/integrations/pgp/index.rst:127 -msgid "**It says a passphrase is needed, but I haven't got one.**" +#: ../system/integrations/checkmk/admin-panel-reference.rst:24 +msgid "What ticket state should be applied when “auto-closing” a ticket?" msgstr "" -#: ../system/integrations/pgp/index.rst:125 +#: ../system/integrations/checkmk/admin-panel-reference.rst:26 msgid "" -"If the key is secured with a passphrase, you have to provide it for the " -"import in Zammad. It is possible that keys may have an empty passphrase. " -"However, this is *not* recommended." +"You can choose from the seven built-in ticket states. If these states aren't " +"enough for you, you can :ref:`define a new ticket state ` for this purpose as well. This can be useful for tracking " +"tickets with :doc:`reports `, for example." msgstr "" -#: ../system/integrations/pgp/index.rst:132 -msgid "**How do my customers get my new key?**" +#: ../system/integrations/checkmk/admin-panel-reference.rst:35 +#: ../system/integrations/cti/includes/recent-logs.include.rst:2 +#: ../system/integrations/ldap/index.rst:74 +#: ../system/integrations/pgp/index.rst:106 +msgid "Recent Logs" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:None +msgid "Screenshot of Checkmk \"Recent Logs\" section" msgstr "" -#: ../system/integrations/pgp/index.rst:130 +#: ../system/integrations/checkmk/admin-panel-reference.rst:41 msgid "" -"You have to provide your **public** key in advance. Your customer also has " -"to configure PGP in their email workflow and import your public key. The " -"other way round, you have to get the public key of your customer and have to " -"import it to Zammad." +"If you're having trouble getting Zammad and Checkmk to play nicely together, " +"this section can help you troubleshoot." msgstr "" -#: ../system/integrations/slack.rst:2 -msgid "Slack" +#: ../system/integrations/checkmk/admin-panel-reference.rst:44 +msgid "" +"It contains a record of the fifty most recent transactions that Zammad knows " +"about, including each one's request/response details and return status." msgstr "" -#: ../system/integrations/slack.rst:4 -msgid "**⚠️ Deprecation warning ⚠️**" +#: ../system/integrations/checkmk/api-reference.rst:2 +msgid "API Reference" msgstr "" -#: ../system/integrations/slack.rst:6 +#: ../system/integrations/checkmk/api-reference.rst:4 msgid "" -"Zammad 7 will no longer support this dedicated Slack integration. It is " -"recommended to switch to :doc:`pre-defined webhooks ` instead. Existing Slack integrations should " -"be migrated manually before this feature is dropped." +"For most users, :ref:`the sample scripts from the Setup Guide ` will do the job just fine. But if you want more fine-grained control" +"—for instance, to create high- and low-priority tickets for different types " +"of system events—then you'll have to customize the data those scripts send " +"to Zammad." msgstr "" -#: ../system/integrations/slack.rst:14 +#: ../system/integrations/checkmk/api-reference.rst:15 msgid "" -"In order to use this feature, please add a new Slack app to your Workspace. " -"The App you need is called ``Incoming WebHooks`` ." +"This custom script will automatically set all tickets it creates to **high " +"priority** and **assign them to charlie@chrispresso.com**." msgstr "" -#: ../system/integrations/slack.rst:18 -msgid "Why Do I Need This Feature?" +#: ../system/integrations/checkmk/api-reference.rst:32 +msgid "How Does it Work?" msgstr "" -#: ../system/integrations/slack.rst:20 +#: ../system/integrations/checkmk/api-reference.rst:34 msgid "" -"If you're already using Slack for your team communication, you'll love this " -"feature! Our Slack integration can push ticket notifications about the last " -"ticket article based on the following events:" -msgstr "" - -#: ../system/integrations/slack.rst:24 -msgid "on Ticket creation" +"There are two kinds of data you can pass to the API, both in the form of key-" +"value pairs:" msgstr "" -#: ../system/integrations/slack.rst:25 -msgid "on Ticket updates" +#: ../system/integrations/checkmk/api-reference.rst:44 +msgid "Checkmk parameters" msgstr "" -#: ../system/integrations/slack.rst:26 -msgid "on reached reminders" +#: ../system/integrations/checkmk/api-reference.rst:38 +msgid "" +"are required, and make up the **contents** of the resulting tickets/" +"articles. They also determine whether an event creates a new ticket or " +"updates/closes an existing one." msgstr "" -#: ../system/integrations/slack.rst:27 -msgid "a Ticket has escalated" +#: ../system/integrations/checkmk/api-reference.rst:42 +msgid "" +"These are the only values used in the sample scripts. **Use them as-is**; " +"technically, they can be customized, but it's hard to imagine a good reason " +"for it." msgstr "" -#: ../system/integrations/slack.rst:28 -msgid "a Ticket is going to escalate" +#: ../system/integrations/checkmk/api-reference.rst:52 +msgid "Ticket attributes" msgstr "" -#: ../system/integrations/slack.rst:30 +#: ../system/integrations/checkmk/api-reference.rst:47 msgid "" -"Zammad will provide the Ticket title, a direct link to the Ticket, the event " -"type (creation, updated, escalation), the customer, time and the last " -"article that has triggered the notification." +"are optional, and can be used to **adjust settings** on newly created " +"tickets (*e.g.,* set the owner, group, priority, or state)." msgstr "" -#: ../system/integrations/slack.rst:34 +#: ../system/integrations/checkmk/api-reference.rst:50 msgid "" -"This will give you further options, as you can see e.g. escalating tickets " -"that are assigned to an agent that's e.g. absent. You can interact faster, " -"as you might see problems earlier (or even before the problem gets one)." +"If you want to customize your Checkmk alert script, do it with these. Simply " +"add an extra “form” option for each one (``-F \"key=value\"``) to your " +"script's ``curl`` command line, as in the example above." msgstr "" -#: ../system/integrations/slack.rst:38 -msgid "" -"If needed and wanted, you can even discuss directly about the topic before " -"sending an answer to the customer. Another possible use case would be a " -"agent monitoring new agents and their answers to tickets." +#: ../system/integrations/checkmk/api-reference.rst:54 +msgid "💡 **It's just an API endpoint!**" msgstr "" -#: ../system/integrations/slack.rst:44 -#, fuzzy -msgid "Configure the Integration" -msgstr "Configuración del widget de chat" - -#: ../system/integrations/slack.rst:46 +#: ../system/integrations/checkmk/api-reference.rst:56 msgid "" -"First of all, please go to your slack workspace - go to administration => " -"Manage Apps. If you don't have an app yet, you can simply add a new one - " -"just search for ``Incoming WebHooks`` and customize the app to your needs." +"When using Checkmk integration, messages need to be formatted in a certain " +"way, but that *doesn't mean the messages actually have to come from Checkmk*." msgstr "" -#: ../system/integrations/slack.rst:50 +#: ../system/integrations/checkmk/api-reference.rst:59 msgid "" -"Choose (or create) the channel Zammad should post it's information to and " -"press on \"Add Incoming WebHooks integration\". If you're ready, copy the " -"provided WebHook URL and go to your Zammad installation." +"If you use another monitoring tool that's not officially supported by " +"Zammad, there's probably a way to make it work with your Checkmk callback " +"URL." msgstr "" -#: ../system/integrations/slack.rst:56 -msgid "" -"You need administrative rights on the Slack Workspace. The link to the app " -"directory is normally ``https://[workspace-name].slack.com/apps`` ." +#: ../system/integrations/checkmk/api-reference.rst:63 +msgid "Checkmk Parameters" msgstr "" -#: ../system/integrations/slack.rst:63 +#: ../system/integrations/checkmk/api-reference.rst:65 msgid "" -"To configure the slack integration, log in to Zammad and go to Integrations " -"(System) => Slack in the admin panel." +"When a notification is received, Zammad creates a new article containing the " +"details of the event that triggered it:" msgstr "" -#: ../system/integrations/slack.rst:66 -msgid "" -"Here you can choose on what evens Zammad should post information about a " -"ticket to your Slack channel. Next you need to device what groups shall be " -"affected by this, as anybody with access to that specific Slack channel can " -"read at least parts of the ticket this might be a privacy issue, if you " -"select the wrong groups. The username is simply the name that Zammad uses as " -"display name inside the Slack chat. The channel defines the Slack channel " -"the information is being posted in. As last option, you can set a custom " -"icon for posting to slack." +#: ../system/integrations/checkmk/api-reference.rst:None +msgid "Checkmk article body" msgstr "" -#: ../system/integrations/slack.rst:74 +#: ../system/integrations/checkmk/api-reference.rst:72 msgid "" -"When you're ready, just hit \"Submit\" and enable the integration. Zammad " -"will now post new ticket information based on the trigger you chose. Below " -"the options you have the recent log that shows the latest requests to Slack " -"for debugging if needed." +"These details come from the fields listed below, which correspond to " +"parameters provided by Checkmk (``$NOTIFY_*``)." msgstr "" -#: ../system/integrations/slack.rst:81 -msgid "" -"If you leave the Icon URL empty, Zammad will use the Zammad logo instead. " -"The icon should be a square PNG file." +#: ../system/integrations/checkmk/api-reference.rst:75 +msgid "**Required fields are marked with an asterisk (\\*).**" msgstr "" -#: ../system/integrations/slack.rst:90 -msgid "" -"The following figure shows how it will look if you choose to receive updates " -"on created and updated tickets. On every post Zammad sends to the Slack " -"channel, you can create new threads to discuss about the new article." +#: ../system/integrations/checkmk/api-reference.rst:79 +msgid "event_id\\*" msgstr "" -#: ../system/integrations/slack.rst:96 +#: ../system/integrations/checkmk/api-reference.rst:78 msgid "" -"If you just want to keep track of soon escalating or already escalated " -"tickets, it will look the the following figure. Zammad changes the color in " -"front of the post so you can easily see the state of the ticket." +"A unique ID for the system event. (``$NOTIFY_SERVICEPROBLEMID`` / " +"``$NOTIFY_HOSTPROBLEMID``)" msgstr "" -#: ../system/integrations/slack.rst:102 -msgid "" -"If you change the state, Zammad will also put information on what state the " -"ticket gets and (if pending state) the date until it pends. You'll also " -"recognize the color codes in front of posts on slack, as they are exact the " -"same the ticket state colors you'll see in Zammad!" +#: ../system/integrations/checkmk/api-reference.rst:86 +msgid "host\\*" msgstr "" -#: ../system/integrations/smime/index.rst:2 -msgid "S/MIME" +#: ../system/integrations/checkmk/api-reference.rst:82 +msgid "" +"The hostname of the system that the event originated from. " +"(``$NOTIFY_HOSTNAME``)" msgstr "" -#: ../system/integrations/smime/index.rst:11 +#: ../system/integrations/checkmk/api-reference.rst:85 msgid "" -"S/MIME is the most widely-supported method for secure email communication. " -"With S/MIME, you can exchange **signed** and **encrypted** messages with " -"others." +"Used to determine if a new event belongs to an existing ticket. Also used in " +"the subject line of the resulting article (“ is ”)." msgstr "" -#: ../system/integrations/smime/index.rst:15 -msgid "" -"is proof that a message hasn't been tampered with or sent by an impersonator." +#: ../system/integrations/checkmk/api-reference.rst:96 +msgid "service" msgstr "" -#: ../system/integrations/smime/index.rst:17 +#: ../system/integrations/checkmk/api-reference.rst:89 msgid "" -"In other words, it guarantees a message's **integrity** and **authenticity**." +"The name of the service that the event originated from. " +"(``$NOTIFY_SERVICEDESC``)" msgstr "" -#: ../system/integrations/smime/index.rst:22 -msgid "In other words, it guarantees **privacy** and **data security**." +#: ../system/integrations/checkmk/api-reference.rst:92 +msgid "Used to determine if a new event belongs to an existing ticket." msgstr "" -#: ../system/integrations/smime/index.rst:28 -msgid "Screencast demo of S/MIME features for both new tickets and replies" +#: ../system/integrations/checkmk/api-reference.rst:94 +#: ../system/integrations/checkmk/api-reference.rst:110 +msgid "Displayed as ``-`` when omitted." msgstr "" -#: ../system/integrations/smime/index.rst:28 -msgid "" -"Once S/MIME has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " -"appear in the ticket composer." +#: ../system/integrations/checkmk/api-reference.rst:104 +msgid "state\\*" msgstr "" -#: ../system/integrations/smime/index.rst:32 -msgid ":doc:`🔪 Prerequisites `" +#: ../system/integrations/checkmk/api-reference.rst:99 +msgid "" +"The current state of the service or host in question. " +"(``$NOTIFY_SERVICESTATE`` / ``$NOTIFY_HOSTSTATE``)" msgstr "" -#: ../system/integrations/smime/index.rst:31 +#: ../system/integrations/checkmk/api-reference.rst:102 msgid "" -"New to S/MIME? This section helps you to find certificate providers and " -"points out Limitations." +"Used to detect when a ticket should be auto-closed (*i.e.,* on ``OK``/" +"``UP``). Also used in the subject line of the resulting article (“ is " +"”)." msgstr "" -#: ../system/integrations/smime/index.rst:35 -msgid ":doc:`📝 Manage Certificates `" +#: ../system/integrations/checkmk/api-reference.rst:110 +msgid "text" msgstr "" -#: ../system/integrations/smime/index.rst:35 -msgid "Add and download certificates; configure group default behaviors." +#: ../system/integrations/checkmk/api-reference.rst:107 +msgid "" +"The output of the process that triggered the event. " +"(``$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" msgstr "" -#: ../system/integrations/smime/index.rst:38 -msgid ":doc:`😦 Troubleshooting `" +#: ../system/integrations/checkmk/api-reference.rst:121 +msgid "" +"The Object Manager attribute panel displays built-in and custom\n" +"attribute names." msgstr "" -#: ../system/integrations/smime/index.rst:38 -msgid "Took a wrong turn? About recent logs and common issues." +#: ../system/integrations/checkmk/api-reference.rst:121 +msgid "Find a complete list of ticket attributes in the Object Manager." msgstr "" -#: ../system/integrations/smime/index.rst:43 +#: ../system/integrations/checkmk/api-reference.rst:123 msgid "" -"For more details on how S/MIME integration works on the agent side, see the :" -"user-docs:`user docs `." -msgstr "" - -#: ../system/integrations/smime/manage-certificates.rst:2 -msgid "Manage Certificates" +"Ticket attributes are entirely optional, and can be used to customize the " +"tickets that Checkmk creates. (Note that these attributes will be ignored if " +"a new event belongs to an existing ticket.)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:4 +#: ../system/integrations/checkmk/api-reference.rst:128 msgid "" -"S/MIME is **disabled by default**. Enable it to start adding certificates." +"Why would you want to do this? Maybe you have only one IT guy, and all " +"system monitoring issues should be automatically assigned to him. Or, maybe " +"you're creating multiple notification rules so that database outages take " +"higher priority than disk space warnings." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:10 -msgid "Dialogue to add new certificates or private keys" +#: ../system/integrations/checkmk/api-reference.rst:135 +msgid "In most cases, you'll probably want to set one of the following:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:10 +#: ../system/integrations/checkmk/api-reference.rst:137 +msgid "group" +msgstr "grupo" + +#: ../system/integrations/checkmk/api-reference.rst:139 +msgid "state" +msgstr "estado" + +#: ../system/integrations/checkmk/api-reference.rst:140 +msgid "priority" +msgstr "prioridad" + +#: ../system/integrations/checkmk/api-reference.rst:142 msgid "" -"Manage certificates in the Admin Panel under **System > Integrations > S/" -"MIME**. Certificates may be pasted in as plain text or uploaded from a file." +"but in practice, you can set almost any attribute, including :doc:`custom " +"ones you created through the Object Manager `." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:14 -#, fuzzy -msgid "Add Certificate Data" -msgstr "Verificación de correo electrónico" - -#: ../system/integrations/smime/manage-certificates.rst:36 -msgid "Add Certificate" +#: ../system/integrations/checkmk/api-reference.rst:145 +msgid "Please note that the following attributes are **not customizable**:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:17 -msgid "" -"Import public-key certificates for both your own organization and your " -"contacts." +#: ../system/integrations/checkmk/api-reference.rst:147 +msgid "title" +msgstr "título" + +#: ../system/integrations/checkmk/api-reference.rst:148 +msgid "id" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:19 -msgid "" -"You can also add a bunch of certificates in one go by providing a single " -"file with all relevant certificates." +#: ../system/integrations/checkmk/api-reference.rst:149 +msgid "ticket number" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:22 -msgid "🕵️ **ALWAYS verify certificates in-person or over the phone!**" +#: ../system/integrations/checkmk/api-reference.rst:151 +msgid "created_by_id" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:24 -msgid "" -"The whole point of signatures is to alert you when someone is trying to " -"pretend to be someone they're not. Never accept a certificate from someone " -"online without verifying it first." +#: ../system/integrations/checkmk/api-reference.rst:152 +msgid "updated_by_id" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:28 -msgid "📇 **What about trusted certificate authorities?**" +#: ../system/integrations/checkmk/api-reference.rst:155 +msgid "Which Values Can Be Set?" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:30 -msgid "" -"In some cases (e.g. when dealing with large enterprises), you may be given a " -"certificate for an entire CA, rather than a single contact. Add it here to " -"trust *all* certificates issued by that CA." +#: ../system/integrations/checkmk/api-reference.rst:157 +msgid "😵 **Invalid values → unpredictable behavior**" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:35 +#: ../system/integrations/checkmk/api-reference.rst:159 msgid "" -"Commercial CAs can usually be verified online. Zammad does not include a " -"list of built-in, trusted CAs." +"If you provide a value that Zammad doesn't understand (*e.g.,* ``-F " +"\"priority=high\"``), it's not always clear what will happen. In some cases, " +"a ticket will be created with the default values instead - but in others, it " +"may not be created at all!" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:57 -msgid "Add Private Key" +#: ../system/integrations/checkmk/api-reference.rst:164 +msgid "So what values does Zammad understand, then? Well, it depends..." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:39 -msgid "" -"Once you've added a public-key certificate, you can import its matching " -"private key." +#: ../system/integrations/checkmk/api-reference.rst:168 +msgid "Use an email address or username:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:42 -msgid "" -"Private keys are for **your own organization only**; never ask your contacts " -"for their private keys." +#: ../system/integrations/checkmk/api-reference.rst:190 +msgid "group & priority" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:0 -msgid "" -"S/MIME integration showing configured certificates and possible issues with " -"Logging" +#: ../system/integrations/checkmk/api-reference.rst:175 +msgid "Refer to the dropdown menus in the ticket pane:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:50 -msgid "" -"A note is displayed on certificates with a matching private key (see line 2)." +#: ../system/integrations/checkmk/api-reference.rst:0 +msgid "See possible values for certain attributes in the ticket pane." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:52 -msgid "📤 **Certificates and private keys must be uploaded separately.**" +#: ../system/integrations/checkmk/api-reference.rst:187 +msgid "🙅 **Ticket state CANNOT be set this way!**" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:54 +#: ../system/integrations/checkmk/api-reference.rst:189 msgid "" -"If your certificate and private key are bundled together in the same file or " -"PEM block, import it twice (once using each button)." +"Why? Because ``-F \"state=...\"`` is already used :ref:`as a Checkmk " +"parameter `." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:57 -msgid "Please note that bulk imports of private keys are not possible." +#: ../system/integrations/checkmk/api-reference.rst:222 +msgid "Everything Else" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:60 -#, fuzzy -msgid "Download Certificate Data" -msgstr "Verificación de correo electrónico" - -#: ../system/integrations/smime/manage-certificates.rst:62 +#: ../system/integrations/checkmk/api-reference.rst:193 msgid "" -"You can download the earlier provided certificates and private keys at any " -"time from your Zammad instance." +"To set any other attributes, it helps to know your way around the :docs:" +"`rails console `. Valid values are those that you can " +"set with a string:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:65 -msgid "" -"Please note that passphrase-protected private keys stay protected and when " -"you download them, you have to know the passphrase to use them after " -"downloading." +#: ../system/integrations/checkmk/api-reference.rst:218 +msgid "These values can then be passed directly to the API:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:73 -msgid "Dialogue to download certificates or private keys" +#: ../system/integrations/checkmk/index.rst:16 +msgid "How does it work?" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:73 -msgid "Download stored certificates and their keys" +#: ../system/integrations/checkmk/index.rst:2 +msgid "Checkmk" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:78 +#: ../system/integrations/checkmk/index.rst:4 msgid "" -"The ticket composer will set all outgoing messages to **signed and " -"encrypted** by default (assuming the required certificates exist)." +"`Checkmk `_ is a powerful IT monitoring tool that can " +"send real-time status alerts to Zammad via email or REST API. Set these " +"alerts up in Checkmk, and Zammad will automatically create, update, and " +"close tickets based on the health of your system:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:82 -msgid "These defaults can be modified on a per-group basis:" +#: ../system/integrations/checkmk/index.rst:14 +msgid "Screenshot of ticket created by Checkmk notifications" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:None -msgid "Zammad allowing to choose the default behavior on per group basis" +#: ../system/integrations/checkmk/index.rst:14 +msgid "Multiple alerts, same ticket." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:89 -msgid "" -"Of course, agents can always manually change these settings on each email " -"they send out." +#: ../system/integrations/checkmk/setup-guide.rst:2 +msgid "Setup Guide" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:4 -msgid "A certificate *and* private key for your own organization" +#: ../system/integrations/checkmk/setup-guide.rst:4 +msgid "" +"Whenever the Checkmk integration is enabled, Zammad listens for messages on " +"its API and over email. As long as those messages follow the required " +"format, Zammad will create new tickets (or find and update existing ones) " +"based on the message contents." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:6 +#: ../system/integrations/checkmk/setup-guide.rst:10 msgid "" -"(Use this to ✒️ **sign outgoing messages** and 🔓 **decrypt incoming " -"messages**.)" +"That means that “setting up Checkmk integration” is simply a matter of " +"**adding configuration to your Checkmk site**: telling it when to send these " +"messages and what to say. To do that, you'll need to create a new " +"**notification rule** (see `Checkmk's official docs `_ for help with that)." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:9 +#: ../system/integrations/checkmk/setup-guide.rst:17 msgid "" -"Certificates belonging your contacts, or their issuing certificate authority " -"(CA)" +"As part of this new rule, you'll have to choose a **notification method** " +"(*i.e.,* a script to execute whenever the rule is triggered). This script " +"will be written by you (samples below), and contain the logic for sending " +"API/email messages to Zammad:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:11 -msgid "" -"(Use these to ✅ **verify incoming message signatures** and 🔒 **encrypt " -"outgoing messages**.)" +#: ../system/integrations/checkmk/setup-guide.rst:26 +msgid "Checkmk \"New Rule\" dialog" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:14 -msgid "🙋 **I'm new to S/MIME. Where can I get a certificate?**" +#: ../system/integrations/checkmk/setup-guide.rst:26 +msgid "" +"Find your custom scripts in the Checkmk WATO under **Notifications > New " +"Rule > Notification Method**." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:16 +#: ../system/integrations/checkmk/setup-guide.rst:29 msgid "" -"The easiest way to get certificates is to buy an annual subscription through " -"a commercial CA, such as:" +"Once you're done setting up your new rule, you're all set! New tickets " +"should start coming in and auto-updating any time your rule is triggered." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:19 +#: ../system/integrations/checkmk/setup-guide.rst:33 msgid "" -"`Sectigo (formerly Comodo) `_" +"(If you need help troubleshooting, be sure to check the :ref:`checkmk-recent-" +"logs`.)" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:20 -msgid "`Secorio `_" +#: ../system/integrations/checkmk/setup-guide.rst:38 +msgid "API Alerts" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:21 -msgid "`GlobalSign `_" +#: ../system/integrations/checkmk/setup-guide.rst:40 +msgid "" +"To add these scripts in the Checkmk WATO, copy them into your Checkmk " +"installation directory and make them executable. (Be sure to replace the " +"``zammad.example.com`` callback URL with the one found in your admin panel.)" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:23 -msgid "(Zammad is not affiliated with these CAs in any way.)" +#: ../system/integrations/checkmk/setup-guide.rst:60 +msgid "Service notification" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:25 +#: ../system/integrations/checkmk/setup-guide.rst:46 msgid "" -"You can also generate your own self-signed certificates, but the process is " -"complicated and usually 🙅 **involves extra work for your contacts**." +"For updates on the status of the software running on your server (*e.g.,* " +"postgres)." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:29 -msgid "" -"Bear in mind that 🤝 **S/MIME only works if the other party is using it, too." -"**" +#: ../system/integrations/checkmk/setup-guide.rst:75 +msgid "Host notification" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:32 -msgid "Certificate and Private Key Checks on Upload" +#: ../system/integrations/checkmk/setup-guide.rst:63 +msgid "For updates on the status of the server itself." +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:77 +msgid "🤔 **What's with all the env vars?**" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:34 +#: ../system/integrations/checkmk/setup-guide.rst:79 msgid "" -"The certificate and public key validation is based on the ``X509v3`` " -"extensions." +"Whenever Checkmk runs these scripts, it needs to provide some information " +"about the event that triggered the notification. This information is passed " +"in the form of these ``$NOTIFY_*`` environment variables." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:49 -msgid "Uploading a *client certificate*?" +#: ../system/integrations/checkmk/setup-guide.rst:85 +msgid "" +"You can specify additional parameters to pass to the script when you're " +"setting up your notification rule, but the ones you see here are all " +"provided by default." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:41 -msgid "The following attributes are required then:" +#: ../system/integrations/checkmk/setup-guide.rst:90 +msgid "Email Alerts" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:39 -msgid "Subject Alternative Name (at least one email address has to be present)" +#: ../system/integrations/checkmk/setup-guide.rst:94 +msgid "" +"🐞 **There are known bugs** in Zammad's processing of email from Checkmk. " +"This section will be completed once they have been resolved. (Learn more at " +"GitHub issues `#2377 `_ & " +"`#2180 `_.)" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:40 -msgid "Key Usage (``Digital Signature`` and/or ``Key Encipherment``)" +#: ../system/integrations/checkmk/setup-guide.rst:100 +msgid "In the meantime, we encourage you to set up API alerts instead." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:41 -msgid "Public key algorithm (either ``RSA`` or ``EC``)" +#: ../system/integrations/clearbit.rst:2 +msgid "Clearbit" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:43 +#: ../system/integrations/clearbit.rst:4 msgid "" -"The Extended Key Usage attribute is optional. If the certificate provides " -"the named attribute, than it must contain the value ``E-mail Protection``." +"With our Clearbit integration, you can easily enrich the information " +"provided by Zammad. If the customers or agents email address is known to " +"Clearbit, it will share all information it has regarding the user with " +"Zammad. Those information can include the following:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:46 -msgid "" -"Please note that any usable email adress has to be prefixed with ``email:`` " -"or ``rfc822:``." +#: ../system/integrations/clearbit.rst:9 +msgid "Avatar" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:49 -msgid "The named public key algorithms are mandatory for private keys as well." +#: ../system/integrations/clearbit.rst:10 +msgid "Address information" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:54 -msgid "Uploading a *CA certificate*?" +#: ../system/integrations/clearbit.rst:11 +msgid "Website information" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:52 -msgid "" -"In the case of an uploaded CA certificate, providing the value ``CA:TRUE`` " -"in the attribute *Basic Contstraints*, the previously mentioned attributes " -"are not verified." +#: ../system/integrations/clearbit.rst:12 +msgid "A BIO (as Note by default)" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:56 +#: ../system/integrations/clearbit.rst:14 msgid "" -"In general, the usage of any expired (``Not After``) or not yet valid (``Not " -"Before``) certificate is denied for outgoing emails." -msgstr "" - -#: ../system/integrations/smime/prerequisites.rst:59 -msgid "Example certificate:" +"If needed, you can add further custom objects and add mappings to them, so " +"the Clearbit information can be filled within the database. In general you " +"can get any information from Clearbit, as long as you have a mapping to an " +"Zammad object." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:85 +#: ../system/integrations/clearbit.rst:21 msgid "" -"Please note that Zammad will distrust senders by default. This means that " -"you're always required to provide certificate data, no matter if for signing " -"or encrypting." +"Clearbit does have a mapping of fields like LDAP and Exchange have, but does " +"not \"win\" against Zammad information. This means that if you have e.g. the " +"last name field filled in already and Clearbit has other information on " +"that, it will not be updated." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:89 -msgid "This is by design and can't be adjusted." +#: ../system/integrations/clearbit.rst:26 +msgid "" +"However: If let's say the last name has been set by Clearbit and Zammad " +"notices that the last name on the Clearbit source has changed, Zammad will " +"also update this value." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:4 +#: ../system/integrations/clearbit.rst:33 msgid "" -"All of the system's latest S/MIME activity is displayed in the **Recent " -"Logs** section." +"The configuration of Clearbit is really easy and done fast! Just login to " +"your Clearbit-Account, go to \"API\" and copy the secret-API-Key." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:11 -msgid "Sample entries of in- and outgoing S/MIME related emails." +#: ../system/integrations/clearbit.rst:38 +msgid "" +"Now change to your Zammad instance, go to Integrations (System) -> Clearbit " +"in the admin panel. Paste your API-Key into the API-Key-Field and decide if " +"Zammad should create unknown Organizations automatically, if the user does " +"not have one yet (and Clearbit knows it). The shared option decides if the " +"new organizations Zammad creates with Clearbit should be shared ones." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:11 +#: ../system/integrations/clearbit.rst:47 msgid "" -"Logs report the status and details of all mail, both incoming and outgoing, " -"that used signing/verification or encryption/decryption." +"If you're unsure what option to choose, better stick with \"no\". You can " +"also learn more about :doc:`/manage/organizations/index`." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:14 +#: ../system/integrations/clearbit.rst:52 msgid "" -"This log does **not** include email sent by :doc:`triggers ` or the :doc:`scheduler `. For those, check your " -"``production.log``." +"The Mapping option works similar to the mapping within the Exchange and LDAP " +"sync. You can add further mappings for e.g. custom fields if you need more " +"information that Clearbit can provide." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:20 -msgid "Common Issues" +#: ../system/integrations/clearbit.rst:58 +msgid "" +"If you want to add more Clearbit fields and want to learn more about " +"available fields on their API, you can take a look at their `API " +"documentation `_." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:30 -msgid "I received a signed/encrypted email before I set up S/MIME integration" +#: ../system/integrations/clearbit.rst:62 +msgid "" +"If you're happy with the above chosen Settings and your mapping, just save " +"the changes and enable Clearbit integration. Zammad will now start polling " +"the Clearbit API as users contact you." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:23 +#: ../system/integrations/clearbit.rst:68 msgid "" -"No problem. Once S/MIME has been enabled and the appropriate certificates " -"have been added, agents will be prompted to retry verification/decryption on " -"matching emails." +"Zammad does not synchronize with Clearbit on a regular basis, but on demand " +"if needed. This saves API calls." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:0 -msgid "Screenshot of user prompt to retry decryption" +#: ../system/integrations/clearbit.rst:73 +msgid "" +"Below the Settings and Mappings, you'll find our Integration log. You can " +"see what requests Zammad sent to Clearbit and also the APIs Response." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:38 -msgid "The 🔒 **Encrypt** button is disabled" +#: ../system/integrations/clearbit.rst:78 +msgid "" +"By the way, you can also view the API log on the Clearbit website - the " +"information seen is basically the same." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:33 -msgid "Have you added the recipient's certificate?" +#: ../system/integrations/clearbit.rst:84 +msgid "Example When Adding a User" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:34 -msgid "Are you sure the recipient's certificate is valid?" +#: ../system/integrations/clearbit.rst:86 +msgid "" +"To show you how fast information is added, we added a small Screencast " +"below. This shows the creation of the User Alex from Clearbit. As we already " +"set the last name of Alex to \"X\", Zammad did not update it. What Zammad " +"did was to add further information it received from Clearbit." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:35 -msgid "Have you checked your ``production.log`` for more details?" +#: ../system/integrations/cti/generic.rst:2 +msgid "CTI (generic)" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:37 +#: ../system/integrations/cti/includes/introduction.include.rst:1 msgid "" -"If encryption doesn't work in the composer, it won't work in :doc:`triggers " -"` or the :doc:`scheduler ` either!" +"This integration enables Zammad to provide a caller log to your agents. With " +"this your agents can greet your customers by their name and are supported by " +"Zammad with automatically opening a new ticket dialog or the user profile." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:42 -msgid "The ✅ **Sign** button is disabled" +#: ../system/integrations/cti/includes/introduction.include.rst:6 +msgid "" +"Click the toggle next to the heading to activate or deactivate this " +"integration." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:41 +#: ../system/integrations/cti/includes/introduction.include.rst:9 msgid "" -"Have you added **both the certificate and private key** for your " -"organization?" +"If you want to learn more on how your agents can use this function, please " +"refer the :user-docs:`user documentation `." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:42 +#: ../system/integrations/cti/includes/introduction.include.rst:14 msgid "" -"Does the email address on the certificate match the email address of the " -"agent/group composing the email?" +"Automatically opening new ticket dialogues or user profiles requires agent " +"to extension mapping - see more below." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:45 -msgid "Error: “Fingerprint already taken”" +#: ../system/integrations/cti/includes/introduction.include.rst:20 +msgid "Please note the following limitations to reduce confusion later on:" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:45 -msgid "Are you sure you haven't added this certificate already?" +#: ../system/integrations/cti/includes/introduction.include.rst:22 +msgid "CTI integrations provide caller log functions only." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:48 -msgid "Error: “❌ invalid byte sequence in UTF-8”" +#: ../system/integrations/cti/includes/introduction.include.rst:23 +msgid "" +"This integration does not provide any VoIP functionalities; you can't make " +"phone calls from within Zammad." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:48 -msgid "Please ensure to provide PEM formatted certificate and keys." +#: ../system/integrations/cti/includes/introduction.include.rst:25 +msgid "" +"If your browser supports ``tel``-URLs, you can click on phone numbers for " +"automatic dialing. This requires additional software / configuration on your " +"agent's computers." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:49 -msgid "Did you check if the provided file is a valid certificate or key?" +#: ../system/integrations/cti/generic.rst:9 +#: ../system/integrations/cti/placetel.rst:14 +#: ../system/integrations/cti/sipgate.rst:14 +msgid "Please provide the following requirements:" msgstr "" -#: ../system/integrations/zabbix.rst:2 -msgid "Zabbix Integration" +#: ../system/integrations/cti/generic.rst:11 +msgid "" +"A telephone system that supports webhooks (outbound) (best option are those " +"that allow customizing the calls)." msgstr "" -#: ../system/integrations/zabbix.rst:5 -msgid "" -"This guide describes how to integrate your Zabbix 5.4 installation with " -"Zammad using the Zabbix webhook feature. This guide will provide " -"instructions on setting up a media type, a user and an action in Zabbix." +#: ../system/integrations/cti/generic.rst:13 +msgid "A unique Call-ID during the call session." msgstr "" -#: ../system/integrations/zabbix.rst:12 -msgid "Zammad with enabled HTTP Token Authentication" +#: ../system/integrations/cti/generic.rst:14 +msgid "Call event data (both numbers and direction)." msgstr "" -#: ../system/integrations/zabbix.rst:13 -msgid "Zabbix version 5.4 or higher" +#: ../system/integrations/cti/generic.rst:15 +msgid "Your Zammad instance must be reachable for your telephony system." msgstr "" -#: ../system/integrations/zabbix.rst:16 -msgid "Setting up a Zammad" +#: ../system/integrations/cti/generic.rst:17 +msgid "" +"If you want to learn more on what kind of requests are supported by Zammad " +"and what it expects, please consult our :docs:`CTI-API documentation `." msgstr "" -#: ../system/integrations/zabbix.rst:18 -msgid "Enable **API Token Access** in Settings > System > API." +#: ../system/integrations/cti/generic.rst:22 +#: ../system/integrations/cti/placetel.rst:27 +#: ../system/integrations/cti/sipgate.rst:30 +#, fuzzy +msgid "Available Settings" +msgstr "Verificación de correo electrónico" + +#: ../system/integrations/cti/generic.rst:29 +#: ../system/integrations/cti/placetel.rst:41 +#: ../system/integrations/cti/sipgate.rst:40 +msgid "Endpoint Settings" msgstr "" -#: ../system/integrations/zabbix.rst:20 +#: ../system/integrations/cti/generic.rst:25 msgid "" -"Create a **new user** for a Zabbix alerter with an **email address** and " -"create a personal user token with **ticket.agent** permissions." -msgstr "" - -#: ../system/integrations/zabbix.rst:24 -msgid "Zabbix Webhook Configuration" +"Zammad will list your generic CTI endpoint here. It contains a unique token " +"so ensure to keep this URL save." msgstr "" -#: ../system/integrations/zabbix.rst:27 -#, fuzzy -msgid "Create a Global Macro" -msgstr "Macros" - -#: ../system/integrations/zabbix.rst:29 +#: ../system/integrations/cti/generic.rst:28 msgid "" -"Before setting up the **Webhook**, you need to setup the global macro " -"**{$ZABBIX.URL}**, which must contain the **URL** to the **Zabbix frontend**." +"You'll need this endpoint for your PBX to talk to Zammad, see :docs:`CTI-API " +"documentation `." msgstr "" -#: ../system/integrations/zabbix.rst:33 +#: ../system/integrations/cti/includes/important-dont-forget-saving.include.rst:3 msgid "" -"In the **Administration** > **Media types** section, import the `Template`_." +"All following options **do not save automatically**. Always use the Save " +"button on the lower end of the integration page!" msgstr "" -#: ../system/integrations/zabbix.rst:38 -msgid "Open the added **Zammad** media type and set:" +#: ../system/integrations/cti/generic.rst:43 +#: ../system/integrations/cti/placetel.rst:49 +#: ../system/integrations/cti/sipgate.rst:52 +msgid "Call Settings" msgstr "" -#: ../system/integrations/zabbix.rst:40 -msgid "**zammad\\_access\\_token** to the your **Personal User Token**" +#: ../system/integrations/cti/generic.rst:39 +#: ../system/integrations/cti/placetel.rst:49 +#: ../system/integrations/cti/sipgate.rst:37 +#: ../system/integrations/cti/sipgate.rst:50 +msgid "Inbound" msgstr "" -#: ../system/integrations/zabbix.rst:41 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:1 msgid "" -"**zammad\\_url** to the **frontend URL** of your **Zammad** installation" +"This option allows you to block specific incoming caller IDs. It allows you " +"to temporarily reject e.g. spam callers without having to contact providers " +"or PBX administrators." msgstr "" -#: ../system/integrations/zabbix.rst:43 -msgid "**zammad\\_customer** to your **Zammad user email**." +#: ../system/integrations/cti/includes/inbound-calls.include.rst:11 +msgid "Caller ID to block" msgstr "" -#: ../system/integrations/zabbix.rst:44 -msgid "" -"**zammad\\_enable\\_tags** to **true** or **false** to enable or disable " -"trigger tags. **Important**: if you enable tag support, each tag is set with " -"a separate request." +#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 +msgid "Provide caller IDs to block in ``E.164`` format." msgstr "" -#: ../system/integrations/zabbix.rst:48 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:8 msgid "" -"If you want to prioritize issues according to **severity** values in Zabbix, " -"you can define mapping parameters:" +"Your telephony system has to support this function. Zammad will send a " +"``reject`` response which will cause your telephony system to hang up the " +"call. To callers this usually will feel like the line is busy." msgstr "" -#: ../system/integrations/zabbix.rst:51 -msgid "**severity\\_**: Zammad priority ID" +#: ../system/integrations/cti/includes/inbound-calls.include.rst:14 +msgid "" +"Provide a meaningful note for your fellow administrators to remind yourself " +"why you've chosen to block the number." msgstr "" -#: ../system/integrations/zabbix.rst:53 -msgid "Click the **Update** button to save the **Webhook** settings." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:17 +#: ../system/integrations/cti/sipgate.rst:40 +msgid "Outbound" msgstr "" -#: ../system/integrations/zabbix.rst:55 +#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:1 msgid "" -"To receive notifications in **Zammad**, you need to create a **Zabbix user** " -"and add **Media** with the **Zammad** type." +"In many cases you may want to use a different caller ID depending on the " +"destination you're calling. This may apply due to specific connection rates " +"to other countries or because you want your customer to feel you're calling " +"from the same country." msgstr "" -#: ../system/integrations/zabbix.rst:58 -msgid "" -"For **Send to**: enter any text, as this value is not used, but is required." +#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:6 +msgid "This option expects ``E.164`` number formats." msgstr "" -#: ../system/integrations/zabbix.rst:61 -msgid "" -"For more information, use the `Zabbix documentation `_." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 +msgid "Destination caller ID" msgstr "" -#: ../system/maintenance.rst:2 -msgid "Maintenance" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:5 +msgid "The caller ID or number you're trying to call." msgstr "" -#: ../system/maintenance.rst:4 -msgid "" -"Zammad comes with a maintenance mode that you can use for e.g. updating the " -"instance or changing settings while restricting availability and functions." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:7 +msgid "You can use wildcards for e.g. country specific outbound numbers like:" msgstr "" -#: ../system/maintenance.rst:13 -msgid "Mode" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:9 +msgid "``49*`` for Germany" msgstr "" -#: ../system/maintenance.rst:8 -msgid "The mode setting allows you to enable or disable the maintenance mode." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:10 +msgid "``4930*`` for Berlin / Germany landlines" msgstr "" -#: ../system/maintenance.rst:10 -msgid "Defaults to *off*." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 +msgid "``33*`` for France" msgstr "" -#: ../system/maintenance.rst:12 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:15 +msgid "Set Outbound caller ID" +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:14 msgid "" -"The maintenance mode will restrict access to administrative roles only. This " -"means agents and customers are logged off." +"The outbound caller ID to set (the number your customer sees on his display) " +"in ``E.164`` number format." msgstr "" -#: ../system/maintenance.rst:23 -msgid "@Login" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 +msgid "Provide a short description for fellow administrators." msgstr "" -#: ../system/maintenance.rst:16 +#: ../system/integrations/cti/includes/generic-cti-support-note.includes.rst:3 msgid "" -"This setting allows you to provide a login message within a green banner " -"above the login screen. Click into the green banner in the settings page to " -"adjust your message. To activate the message, activate the *@Login* setting." +"This option requires your PBX to send a specific request to Zammad *before " +"dialing*. Please consult the :docs:`CTI API ` in case " +"you're not sure." msgstr "" -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing the default login message within the\n" -"settings page" +#: ../system/integrations/cti/generic.rst:52 +#: ../system/integrations/cti/placetel.rst:54 +#: ../system/integrations/cti/sipgate.rst:59 +msgid "Other Settings" msgstr "" -#: ../system/maintenance.rst:26 +#: ../system/integrations/cti/includes/other-settings-intro.include.rst:1 msgid "" -"Send an informative message to **all active sessions**. This comes handy to " -"inform your agents e.g. about mayor outages or to force reloads after " -"configuration changes." +"Below you can find all available additional settings for this CTI " +"integration. For your overview we're sorting them by appearance and " +"reference their description first." msgstr "" -#: ../system/maintenance.rst:31 -msgid "This is the messages title (slightly bigger than the normal message)." +#: ../system/integrations/cti/includes/default-caller-id.include.rst:2 +#: ../system/integrations/cti/includes/default-caller-id.include.rst:1 +msgid "Default caller ID for outbound calls" msgstr "" -#: ../system/maintenance.rst:34 -msgid "The text you want to provide to your logged in sessions." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:16 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:15 +msgid "Shown records in caller log" msgstr "" -#: ../system/maintenance.rst:39 -msgid "Reload application" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:2 +msgid "" +"Allows you to set the number of shown caller log entries for all users. You " +"can choose from the following values:" msgstr "" -#: ../system/maintenance.rst:37 -msgid "" -"Selecting this option will change the message acceptance button from *Close* " -"(with nothing happening) to *Continue session*, which forces the application " -"to reload." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:5 +msgid "60 (default)" msgstr "" -#: ../system/maintenance.rst:43 -msgid "" -"If you have customers that are logged in to Zammad, they'll also be notified " -"if they're active in that moment." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:6 +msgid "120" msgstr "" -#: ../system/maintenance.rst:48 -msgid "Example without reload application" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:7 +msgid "180" msgstr "" -#: ../system/maintenance.rst:52 -msgid "" -"Message setting within Zammad's admin settings without ticket reload " -"application setting." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:8 +msgid "240" msgstr "" -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing the send message settings without ticket\n" -"reload application set" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:9 +msgid "300" msgstr "" -#: ../system/maintenance.rst:61 ../system/maintenance.rst:85 -msgid "" -"The modal all other active sessions will see upon pressing *Send to clients*." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:11 +msgid "**🥵 Potential performance issue**" msgstr "" -#: ../system/maintenance.rst:0 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:13 msgid "" -"Screenshot showing modal caused by maintenance's message\n" -"without reload application ticket" +"Setting this setting higher than 60 may cause serious performance issues on " +"very busy instances. Keep in mind that this setting causes Zammad to poll " +"and send up to 300 records to *all active agent sessions* in very short time " +"periods." msgstr "" -#: ../system/maintenance.rst:72 -msgid "Example with reload application" +#: ../system/integrations/cti/generic.rst:73 +msgid "Caller Log Filter" msgstr "" -#: ../system/maintenance.rst:76 +#: ../system/integrations/cti/generic.rst:55 msgid "" -"Message setting within Zammad's admin settings with ticket reload " -"application setting." +"This function allows you to provide call information based on e.g. queues " +"only to agents that really need the information." msgstr "" -#: ../system/maintenance.rst:0 +#: ../system/integrations/cti/generic.rst:58 msgid "" -"Screenshot showing the send message settings with ticket\n" -"reload application set" +"Why? If you have a team for several countries or departments, you don't want " +"to bug your agents from other departments. Leaving these options empty will " +"fallback to showing everything to everyone." msgstr "" -#: ../system/maintenance.rst:0 +#: ../system/integrations/cti/generic.rst:64 +msgid "Destination caller ID or Queue" +msgstr "" + +#: ../system/integrations/cti/generic.rst:63 msgid "" -"Screenshot showing modal caused by maintenance's message\n" -"with reload application ticket" +"This depends on your PBX and usually is either a queue ID, phone number or " +"extension." msgstr "" -#: ../system/monitoring.rst:2 -msgid "Monitoring" +#: ../system/integrations/cti/generic.rst:69 +msgid "Agents" msgstr "" -#: ../system/monitoring.rst:4 +#: ../system/integrations/cti/generic.rst:67 msgid "" -"This function is only available in self hosted instances. If you use Zammad " -"in our cloud, we are monitoring the system on our own and take steps to fix " -"potential problems directly." +"Select the agents that are responsible for the group. These agents will then " +"see caller log entries and call notifications fitting to said queue." msgstr "" -#: ../system/monitoring.rst:11 +#: ../system/integrations/cti/generic.rst:0 msgid "" -"On the monitoring page, you can see the current health state of Zammad under " -"\"*Current Status*\" at the bottom. This can be useful if you want to have a " -"look if everything is up and running. As an example, you could have a look " -"in the monitoring when you assume that some emails aren't processed from " -"Zammad." +"Screenshot showing the caller log filter table with pre filled sample data" msgstr "" -#: ../system/monitoring.rst:17 -msgid "**Can't receive an email and the monitoring response is \"healthy\"?**" +#: ../system/integrations/cti/includes/recent-logs.include.rst:6 +msgid "" +"With recent logs Zammad allows you to view the latest calls for the CTI " +"functionality. This usually comes in handy, when you're looking for errors." msgstr "" -#: ../system/monitoring.rst:19 +#: ../system/integrations/cti/includes/recent-logs.include.rst:0 msgid "" -"Zammad will just inform you about unprocessable emails. This is not the case " -"for oversized emails. You can adjust the maximum email size in :doc:`../" -"channels/email/settings`." +"Screenshot showing several incoming requests within Recent logs section." msgstr "" -#: ../system/monitoring.rst:24 -msgid "Monitoring API" +#: ../system/integrations/cti/includes/recent-logs.include.rst:16 +msgid "I'm just here to clear floats up." msgstr "" -#: ../system/monitoring.rst:26 +#: ../system/integrations/cti/includes/recent-logs.include.rst:20 msgid "" -"Beside the indication in the monitoring page, you can also use an external " -"monitoring tool to monitor Zammad's health. To request the health of Zammad, " -"you need to provide the API key (token) to the external monitoring tool. You " -"can copy the token from the \"*Current Token*\" field as well as the whole " -"API endpoint of your system (\"*Health Check*\" field), in which the API " -"token is already included." +"By clicking on the entry of interest, Zammad will provide more details on " +"the call in question. You'll see the payload it received and also the " +"response that was sent." msgstr "" -#: ../system/monitoring.rst:37 -msgid "Screenshot showing Current Token and Health Check" +#: ../system/integrations/cti/includes/recent-logs.include.rst:0 +msgid "" +"Screenshot showing detailed information of a specific log entry of recent " +"logs" msgstr "" -#: ../system/monitoring.rst:37 -msgid "Screenshot showing Token and Health Check" +#: ../system/integrations/cti/includes/recent-logs.include.rst:31 +msgid "x" msgstr "" -#: ../system/monitoring.rst:39 -msgid "" -"In addition to that, you can reset the auto-generated token to make sure " -"that already configured monitoring systems won't work anymore. So, please " -"use this \"*Reset*\" button only if you know what you do!" +#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 +#: ../system/integrations/cti/includes/troubleshooting.include.rst:9 +msgid "My Phone page stays blank, signalling does work..." msgstr "" -#: ../system/monitoring.rst:44 -#, fuzzy -msgid "Example Output" -msgstr "Ejemplo" - -#: ../system/monitoring.rst:0 -msgid "No issues found" +#: ../system/integrations/cti/includes/troubleshooting.include.rst:5 +msgid "" +"If you've made sure that signalling works (check Recent logs) and your " +"Caller Log still stays empty, please ensure that you only configured one CTI " +"integration version. Specifically defining more than one agent mapping on " +"the different integration variants will be the issue." msgstr "" -#: ../system/monitoring.rst:48 ../system/monitoring.rst:60 -msgid "**Indicator in Zammad**:" +#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 +msgid "Clear the not needed agent mapping and reload your browser page." msgstr "" -#: ../system/monitoring.rst:0 -msgid "Screenshot showing monitoring with no issues" +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:1 +msgid "" +"By mapping your agents extension to their existing Zammad users, Zammad can " +"provide a new ticket dialog or open the user profile for the agent that " +"picks up the call." msgstr "" -#: ../system/monitoring.rst:54 ../system/monitoring.rst:66 -msgid "**API response**::" +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:5 +msgid "" +"This speeds up ticket aiding, no matter if it's for existing tickets or new " +"ones!" msgstr "" -#: ../system/monitoring.rst:0 -msgid "Issues were found" +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:8 +msgid "" +"To see it work from the agent's perspective, have a look on :user-docs:`user " +"documentation `." msgstr "" -#: ../system/monitoring.rst:0 -msgid "Screenshot showing monitoring with issues" +#: ../system/integrations/cti/placetel.rst:2 +msgid "Placetel CTI" msgstr "" -#: ../system/objects.rst:2 -msgid "Objects" +#: ../system/integrations/cti/placetel.rst:16 +msgid "You need an administrative Placetel account for your organization." msgstr "" -#: ../system/objects.rst:4 +#: ../system/integrations/cti/placetel.rst:17 +#: ../system/integrations/cti/sipgate.rst:20 msgid "" -"In Zammad you can add your own fields to tickets, users, organizations and " -"even groups (these are called \"objects\"). This can be useful if you need " -"to add further information to a ticket or any other object in Zammad and the " -"information doesn't fit in any existing field." +"Your Zammad instance must be allowed to communicate to external services." msgstr "" -#: ../system/objects.rst:11 -msgid "" -"Try to avoid deleting attributes (and disable them instead) as Zammad might " -"run into unexpected conditions if they are referenced somewhere." +#: ../system/integrations/cti/placetel.rst:18 +msgid "Placetel must be able to reach your Zammad instance." msgstr "" -#: ../system/objects.rst:16 -msgid "" -"Here's an overview of object attributes. On the upper right you can add new " -"attributes. By default, there will be no custom fields - standard attributes " -"will be grayed out, you can't delete or change those. You can edit custom " -"attributes (they are displayed in black font and have a trash bin on the " -"right side) just by clicking on them." +#: ../system/integrations/cti/placetel.rst:22 +msgid ":doc:`provider-configurations/placetel`" msgstr "" -#: ../system/objects.rst:24 +#: ../system/integrations/cti/placetel.rst:21 msgid "" -"Attributes you add to Zammad, no matter if they have default values or not, " -"will not update existing information. This means a new ticket field " -"technically will be empty unless you populate it." +"Learn how to configure Placetel to enable Zammad and Placetel to communicate " +"with each other." msgstr "" -#: ../system/objects.rst:28 +#: ../system/integrations/cti/placetel.rst:32 msgid "" -"Especially in ticket scope this also means that newly added attributes will " -"be indicated as \"changed\" to agents that view the ticket. This may " -"interfere with Zammad's tabs behavior." +"The here listed endpoint settings are relevant for the :doc:`integration " +"configuration with Placetel `." msgstr "" -#: ../system/objects.rst:40 -#, fuzzy -msgid "Ordering Attributes" -msgstr "Organización & Nombre de Departamento" +#: ../system/integrations/cti/placetel.rst:37 +#: ../system/integrations/i-doit.rst:53 +msgid "Endpoint" +msgstr "" -#: ../system/objects.rst:42 +#: ../system/integrations/cti/placetel.rst:36 msgid "" -"Since Zammad introduced :doc:`/system/core-workflows` the need to have a " -"custom positioning for attributes has become more important than ever." +"This endpoint will be required for the Zammad integration within the " +"Placetel web interface." msgstr "" -#: ../system/objects.rst:45 -msgid "" -"To adjust the position of such an attribute, simply click on the attribute " -"entry in question, scroll down and adjust the position number. Please note " -"that you cannot change the positioning of default attributes." +#: ../system/integrations/cti/placetel.rst:41 +msgid "API Token" msgstr "" -#: ../system/objects.rst:49 +#: ../system/integrations/cti/placetel.rst:40 msgid "" -"In case two attributes have the same position value, Zammad will sort " -"alphabetically by name automatically." +"You'll receive this token within the ``Web API`` menu. Make sure to copy " +"this value, it's only shown once!" msgstr "" -#: ../system/objects.rst:None -msgid "" -"Screenshot showing custom attribute entries ordered in between default ones" +#: ../system/integrations/cti/placetel.rst:71 +#: ../system/integrations/cti/sipgate.rst:77 +msgid "Phone Extension to Agent Mapping" msgstr "" -#: ../system/objects.rst:56 -msgid "Updating Database After Adding or Editing Attributes" +#: ../system/integrations/cti/placetel.rst:0 +msgid "Screenshot showing sample user mappings in between Placetel and Zammad" msgstr "" -#: ../system/objects.rst:58 +#: ../system/integrations/cti/placetel.rst:64 msgid "" -"When adding or changing attributes, Zammad will not apply the changes " -"instantly, but instead shows you the changed attributes first. If you're " -"ready to go, just click on \"Update database\" to apply the changes to " -"Zammad. If you made a mistake or just want to discard your changes, click " -"\"Discard changes\"." +"You can find your agents Placetel username combination required within ⚙️ PBX " +"→ VoIP destinations. Within the \"Advanced settings\" section you're looking " +"for \"SIP user name\" and \"SIP server\"." msgstr "" -#: ../system/objects.rst:64 -msgid "" -"After applying the changes with \"Update Database\", a restart of Zammad is " -"**mandatory**. If you don't perform it, you may experience unexpected " -"behavior or even errors. You may want to do this kind of configuration " -"during maintenance windows." +#: ../system/integrations/cti/placetel.rst:68 +msgid "Combine these two like so: ``@``." msgstr "" -#: ../system/objects.rst:72 -msgid "" -"Changes on objects require you to update the database to apply these changes." +#: ../system/integrations/cti/placetel.rst:0 +msgid "Sample VoIP credentials for a Placetel user" msgstr "" -#: ../system/objects.rst:75 -msgid "**🤓 Service restarts can be automated**" +#: ../system/integrations/cti/provider-configurations/placetel.rst:2 +msgid "Setup Placetel connection for Zammad" msgstr "" -#: ../system/objects.rst:0 -msgid "Hosted environments automatically restart for you." +#: ../system/integrations/cti/provider-configurations/placetel.rst:6 +msgid "" +"This configuration step requires a *full* administrative Placetel account. " +"You may receive forbidden error messages with Placetel in case your " +"permissions are not high enough." msgstr "" -#: ../system/objects.rst:0 +#: ../system/integrations/cti/provider-configurations/placetel.rst:10 msgid "" -"If you're using a self-hosted installation you can use :docs:`environment " -"variables `" +"The following actions can be configured via the `Placetel web interface " +"`_." msgstr "" -#: ../system/objects.rst:82 -msgid "System Attributes" +#: ../system/integrations/cti/provider-configurations/placetel.rst:29 +msgid "Step 1: Activate Zammad integration" msgstr "" -#: ../system/objects.rst:84 +#: ../system/integrations/cti/provider-configurations/placetel.rst:14 msgid "" -"Zammad comes with pre-configured attributes. Some of them can't be edited " -"via UI (or at all). This is required for proper operation of Zammad and not " -"a bug." +"Within Integrations, scroll down to Partner integrations and select Zammad." msgstr "" -#: ../system/objects.rst:90 -#, fuzzy -msgid "Ticket State" -msgstr "Ticket > Creado en" +#: ../system/integrations/cti/provider-configurations/placetel.rst:17 +msgid "" +"You can alternatively filter by \"Ticket Systems\" to reduce the number of " +"entries on the page. You'll still want to look for Partner integrations. 🤓" +msgstr "" -#: ../system/objects.rst:92 +#: ../system/integrations/cti/provider-configurations/placetel.rst:21 msgid "" -"If the pre-configured states aren't enough for you or you want to change " -"them, you can do so by clicking on the cogwheel icon in the state row in the " -"ticket tab. But you should be careful when changing pre-configured states. " -"This can lead to unwanted behavior in some cases." +"Within the Zammad integration now press \"Activate\". A new tab ``API`` " +"becomes available - open this tab." msgstr "" -#: ../system/objects.rst:None -msgid "Screenshot showing highlighted ticket state attribute" +#: ../system/integrations/cti/provider-configurations/placetel.rst:24 +msgid "" +"Now tick \"Enable Call Control / Notify API\" and paste the Placetel " +"endpoint from your Zammad instance into the field \"URL of your API " +"endpoint\". Save to apply the settings" msgstr "" -#: ../system/objects.rst:122 -msgid "Handling of states" +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "Screencast showing how to activate the Zammad integration" msgstr "" -#: ../system/objects.rst:102 -msgid "" -"In the state configuration screen, you can add new states, disable states or " -"change states." +#: ../system/integrations/cti/provider-configurations/placetel.rst:51 +msgid "Step 2: Generate API Token for Placetel" msgstr "" -#: ../system/objects.rst:0 -msgid "Screenshot showing table of default ticket states" +#: ../system/integrations/cti/provider-configurations/placetel.rst:32 +msgid "" +"Go back to the integrations page and scroll down to \"Web API\". Generate a " +"new API token by using the \"Create a new API token\" button." msgstr "" -#: ../system/objects.rst:110 +#: ../system/integrations/cti/provider-configurations/placetel.rst:37 msgid "" -"To add a new state, click on the \"New Ticket State\" button in the top " -"right corner. To change an existing state, simply click on the affected " -"state. This opens an edit dialog." +"If you already generated a token either use your existing token or reset it " +"by using above mentioned button. Placetel will ask you to conform this reset." msgstr "" -#: ../system/objects.rst:114 +#: ../system/integrations/cti/provider-configurations/placetel.rst:41 msgid "" -"You can also clone a state or set them to \"Default for new tickets\" or " -"\"Default for follow-ups\" by clicking on the ⁝ action button and select the " -"desired function." +"Please keep in mind that existing API scripts may no longer work due to " +"token resets!" msgstr "" -#: ../system/objects.rst:118 +#: ../system/integrations/cti/provider-configurations/placetel.rst:44 msgid "" -"*Default for new tickets* means that this state is used for every newly " -"created ticket." +"Copy the provided API token and insert it into the \"API Token\" field " +"within Zammad's Placetel integration." msgstr "" -#: ../system/objects.rst:121 +#: ../system/integrations/cti/provider-configurations/placetel.rst:47 msgid "" -"*Default for follow-ups* means that this state is used if the ticket is re-" -"opened after it was closed." +"Apply your changes by using the \"Save\" button on the bottom of the " +"Placetel integration page and activate the Placetel integration." msgstr "" -#: ../system/objects.rst:171 -#, fuzzy -msgid "Ticket state in detail" -msgstr "Ticket > Cliente > Correo Electrónico" - -#: ../system/objects.rst:125 +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 msgid "" -"Below you can find a description for each field and option. Please head over " -"to the :ref:`example ` to see the edit dialog." +"Screencast showing how to retrieve an API token from Placetel for Zammad" msgstr "" -#: ../system/objects.rst:129 -msgid "" -"This is the name of the state and what you and your agents are seeing when " -"choosing a state somewhere (e.g. in tickets, trigger configuration)." +#: ../system/integrations/cti/provider-configurations/placetel.rst:73 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:77 +msgid "Step 3: Restrict the numbers to notify on" msgstr "" -#: ../system/objects.rst:137 +#: ../system/integrations/cti/provider-configurations/placetel.rst:54 msgid "" -"There are different state types you can choose from. By default, Zammad " -"comes with one state per state type." +"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " +"the the Integrations page of the Placetel web interface, go to \"Notify " +"API\"." msgstr "" -#: ../system/objects.rst:140 +#: ../system/integrations/cti/provider-configurations/placetel.rst:58 msgid "" -"**new**: for states for tickets that are new and it hasn't been worked on " -"them" +"Lower on the page Placetel allows you to restrict the numbers to notify on. " +"You'll find this within the \"External routing API\" part." msgstr "" -#: ../system/objects.rst:142 +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 msgid "" -"**open**: for states for tickets that are in progress and agents are working " -"on them" +"Screenshot showing a sample selection of phone numbers to use for the " +"Placetels notify API" msgstr "" -#: ../system/objects.rst:144 -msgid "**merged**: for states for tickets that are merged with other tickets" +#: ../system/integrations/cti/provider-configurations/placetel.rst:66 +msgid "" +"This menu point also provides a API request log from Placetel view. Just " +"open \"Recent responses of your API endpoint\" to learn more." msgstr "" -#: ../system/objects.rst:145 +#: ../system/integrations/cti/provider-configurations/placetel.rst:69 msgid "" -"**pending reminder**: for states for tickets that are in progress and you " -"want to set a reminder. (default example: *pending reminder*)" +"If you want to see Zammad's perspective, use the \"Recent Logs\" part from " +"within the Placetel integration page." msgstr "" -#: ../system/objects.rst:147 -msgid "" -"**pending action**: for states for tickets that are waiting for a specified " -"time and then change their state (default example: *pending close*)" +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "Screenshot showing sample log entries for Placetels API calls to Zammad" msgstr "" -#: ../system/objects.rst:150 -msgid "" -"**closed**: for states for tickets that are finished and do not need to be " -"processed further" +#: ../system/integrations/cti/provider-configurations/placetel.rst:77 +msgid "Step 4 (optional): Further configurations for Placetel" msgstr "" -#: ../system/objects.rst:153 +#: ../system/integrations/cti/provider-configurations/placetel.rst:76 msgid "" -"⚠️ Choosing the correct state type is important! If you are in doubt, have a " -"look on the default states and their types!" +"If needed, you can now configure Zammad's Placetel integration in more " +"detail. You can learn more about your options here: :ref:`Placetel " +"integration settings `." msgstr "" -#: ../system/objects.rst:158 -msgid "Ignore escalation" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:2 +msgid "Setup Sipgate connection for Zammad" msgstr "" -#: ../system/objects.rst:157 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"Here you can define whether tickets of this state will count to escalation " -"time or not." +"Sipgate has no english web interface which is why this documentation page is " +"mixing up languages badly." msgstr "" -#: ../system/objects.rst:161 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"You can create a note for the state to inform other admins about the state. " -"This has no effect on tickets." +"Please also note that the availability of API addons highly depends on your " +"package trier. Usage of sipgate.io packages *is not free*, please check " +"their `pricing page `_ before!" msgstr "" -#: ../system/objects.rst:165 -msgid "Set the state to *active* or *inactive*." +#: ../system/integrations/cti/provider-configurations/sipgate.rst:35 +msgid "Step 1: Book sipgate.io package" msgstr "" -#: ../system/objects.rst:167 -msgid "" -"it is technically possible to set all states to inactive. To keep Zammad " -"working in such a case, the inactive flag of one of the states is ignored." +#: ../system/integrations/cti/provider-configurations/sipgate.rst:13 +msgid "Skip to step 2 if you already have the package booked!" msgstr "" -#: ../system/objects.rst:194 -#, fuzzy -msgid "Ticket state example" -msgstr "Ticket > Creado en" - -#: ../system/objects.rst:174 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:15 msgid "" -"Let's assume we want to create a new state which indicates that the ticket " -"has to wait for a response of a third party (e.g. service contractor or " -"manufacturer) and we want to to be able to set a reminder." +"Login to an administrative Sipgate account and navigate to " +"``Accountverwaltung``. You'll see several different options depending on " +"your booked packages. Select ``Verträge & Produkte`` to continue." msgstr "" -#: ../system/objects.rst:178 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:19 msgid "" -"First we give the new state a proper name. In this example we call it " -"\"waiting for manufacturer\"." +"Scroll down to the section ``Zusätzliche Produkte buchen`` and look for " +"``sipgate.io`` - select this product by using the ``Produkte anzeigen``-" +"Button." msgstr "" -#: ../system/objects.rst:181 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:23 msgid "" -"As state type we choose \"pending reminder\". This indicates that the ticket " -"is still open and we can set a reminder. This reminder can be useful if our " -"manufacturer sometimes isn't responding or we want to remind him to give us " -"an answer." +"On the next page select either one of the ``sipgate.io`` packages or ``Push-" +"API Package Free``. Follow the dialogue by booking the addon. You'll be " +"returned to your contract overview and now should see the selected addon in " +"your list." msgstr "" -#: ../system/objects.rst:186 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:30 msgid "" -"We choose \"no\" for \"ignore escalation\" because we want to escalate the " -"tickets even if we are waiting on the manufacturer's feedback." +"The availability for ``sipgate.io`` packages and their levels highly depends " +"on the overall account type and product you've booked with Sipgate." msgstr "" -#: ../system/objects.rst:189 -#, fuzzy -msgid "The **result** in the creation dialog will look like this:" -msgstr "El resultado final se parecerá a lo siguiente:" - -#: ../system/objects.rst:0 -msgid "Screenshot showing ticket state creation dialog with example" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "" +"Screencast showing the process on how to book the required sipgate.io addon" msgstr "" -#: ../system/objects.rst:197 ../system/objects.rst:199 -#, fuzzy -msgid "Ticket Priority" -msgstr "prioridad" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:52 +msgid "Step 2: Configure webhook for Zammad" +msgstr "" -#: ../system/objects.rst:199 ../system/objects.rst:201 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:38 msgid "" -"If the pre-configured priorities aren't enough for you or you want to change " -"them, you can do so by clicking on the cogwheel icon in the priority row in " -"the ticket tab:" +"Within your ``Accountverwaltung`` navicate to your product ``sipgate.io``. " +"In the newly opened tab, switch from \"Clients\" to \"Webhooks\" and paste " +"the endpoint URLs from your Zammad instance like so:" msgstr "" -#: ../system/objects.rst:None -msgid "Screenshot showing highlighted ticket priority attribute" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:42 +msgid "Inbound endpoint to \"Incoming\"" msgstr "" -#: ../system/objects.rst:224 ../system/objects.rst:226 -msgid "Handling of priorities" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:43 +msgid "Outbound endpoint to \"Outgoing\"" msgstr "" -#: ../system/objects.rst:208 ../system/objects.rst:210 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:47 msgid "" -"In the priority configuration screen, you can add new priorities, disable " -"priorities or change priorities." +"Ensure to select at least one call group or phoneline within \"Sources\". " +"Other wise Sipgate will not indicate any incoming or outgoing calls to " +"Zammad." msgstr "" -#: ../system/objects.rst:0 -msgid "Screenshot showing table of default ticket priorities" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "" +"Screencast showing how to add Zammad's endpoint URLs to sipgate.ios webhook " +"configuration" msgstr "" -#: ../system/objects.rst:216 ../system/objects.rst:218 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:55 msgid "" -"To add a new priority, click on the \"New Priority\" button in the top right " -"corner. To change an existing priority, simply click on the affected " -"priority. This opens an edit dialog." +"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " +"the Webhooks → URLs section of Sipgate you can select which *sources* " +"Sipgate should notify Zammad about in- and outgoing calls." msgstr "" -#: ../system/objects.rst:220 ../system/objects.rst:222 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:59 msgid "" -"You can also clone a priority or set them to \"Default for new tickets\" by " -"clicking on the ⁝ action button and select the desired function." +"Use either specific phone lines or use the option \"Use for all phonelines " +"and groups\" to notify Zammad about all existing lines of your Sipgate " +"account." msgstr "" -#: ../system/objects.rst:223 ../system/objects.rst:225 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"*Default for new tickets* means that this priority is used for every newly " -"created ticket." +"Screenshot showing a sample selection of phone numbers to use for the " +"Sipgates webhooks API" msgstr "" -#: ../system/objects.rst:246 ../system/objects.rst:248 -msgid "Priorities in detail" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:68 +msgid "This section also allows you to enable a Debug log." msgstr "" -#: ../system/objects.rst:227 ../system/objects.rst:229 -msgid "Below you can find a description for each field and option." +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "Screenshot showing an enabled Debug log option" msgstr "" -#: ../system/objects.rst:230 ../system/objects.rst:232 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:73 msgid "" -"This is the name of the priority and what you and your agents are seeing " -"when choosing a priority somewhere (e.g. in tickets, trigger configuration)." +"After enabling you can use the Debug log section to see all sent webhook " +"calls to Zammad. You'll also can see the response." msgstr "" -#: ../system/objects.rst:240 ../system/objects.rst:242 -msgid "Highlight color" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "" +"Screenshot showing sample log entries for Sipgates webhook calls to Zammad" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:81 +msgid "Step 4 (optional): Further configurations for Sipgate" msgstr "" -#: ../system/objects.rst:235 ../system/objects.rst:237 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:80 msgid "" -"Switch between *Low priority* (light blue), *High priority* (red) and - " -"(default). This affects the displayed color for ticket titles in overviews." +"If needed, you can now configure Zammad's Sipgate integration in more " +"detail. You can learn more about your options here: :ref:`Sipgate " +"integration settings `." msgstr "" -#: ../system/objects.rst:239 ../system/objects.rst:241 -msgid "The color options are currently limited to the mentioned options." +#: ../system/integrations/cti/sipgate.rst:2 +msgid "Sipgate (sipgate.io)" +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:16 +msgid "You need an administrative Sipgate account for your organization." msgstr "" -#: ../system/objects.rst:243 ../system/objects.rst:245 +#: ../system/integrations/cti/sipgate.rst:17 msgid "" -"You can create a note for the priority to inform other admins about the " -"priority. This has no effect on tickets." +"Zammad requires a ``sipgate.io`` addon from the feature store (please note " +"that API calls are not free with Sipgate. Rates may apply and differ from " +"account to account)." msgstr "" -#: ../system/objects.rst:247 ../system/objects.rst:249 -msgid "Set the priority to *active* or *inactive*." +#: ../system/integrations/cti/sipgate.rst:21 +msgid "Sipgate must be able to reach your Zammad instance." msgstr "" -#: ../system/objects/external-data-source-example.rst:2 -msgid "External Data Source" +#: ../system/integrations/cti/sipgate.rst:25 +msgid ":doc:`provider-configurations/sipgate`" msgstr "" -#: ../system/objects/external-data-source-example.rst:4 +#: ../system/integrations/cti/sipgate.rst:24 msgid "" -"We assume you already had a look on :doc:`types` where you can find a " -"description of the individual fields." +"Learn how to configure Sipgate to enable Zammad and Sipgate to communicate " +"with each other." msgstr "" -#: ../system/objects/external-data-source-example.rst:7 +#: ../system/integrations/cti/sipgate.rst:33 msgid "" -"To reproduce this example, choose a category you want to add a custom field, " -"click on *New Attribute* and select *External data source field* under " -"*Format*." +"Below endpoint settings affect the :doc:`sipgate.io configuration `." msgstr "" -#: ../system/objects/external-data-source-example.rst:11 -msgid "" -"Our example story is to fetch data from an external product database. We " -"want to add our products to the tickets so that the products can be searched " -"and chosen from a list and also create a link to the product website." +#: ../system/integrations/cti/sipgate.rst:37 +msgid "This endpoint is required for incoming call hooks." msgstr "" -#: ../system/objects/external-data-source-example.rst:16 -msgid "Base configuration" +#: ../system/integrations/cti/sipgate.rst:40 +msgid "This endpoint is required for outgoing call hooks." msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Initial steps to configure external data source object type" +#: ../system/integrations/cti/sipgate.rst:0 +msgid "Screenshot showing sample user mappings in between Sipgate and Zammad" msgstr "" -#: ../system/objects/external-data-source-example.rst:23 -#: ../system/variables.rst:85 -#, fuzzy -msgid "**Example:**" -msgstr "Ejemplo" +#: ../system/integrations/cti/sipgate.rst:69 +msgid "" +"You can find your agent's Sipgate username within ``Accountverwaltung → " +"Benutzer``. You're looking for the SIP-ID." +msgstr "" -#: ../system/objects/external-data-source-example.rst:25 -msgid "Name: *product*" +#: ../system/integrations/cti/sipgate.rst:0 +msgid "Sample VoIP credentials for a Sipgate user" msgstr "" -#: ../system/objects/external-data-source-example.rst:26 -msgid "Display: *Product*" +#: ../system/integrations/cti/sipgate.rst:77 +msgid "Users with several devices also have several SIP-IDs." msgstr "" -#: ../system/objects/external-data-source-example.rst:29 -msgid "External data source configuration" +#: ../system/integrations/elasticsearch.rst:2 +msgid "Elasticsearch (SaaS)" msgstr "" -#: ../system/objects/external-data-source-example.rst:31 +#: ../system/integrations/elasticsearch.rst:4 msgid "" -"First, enter the search URL making sure it contains ``#{search.term}`` as a " -"parameter:" +"The Elasticsearch integration allows you to create a read-only user to use " +"with your favorite reporting tool (e.g. like Grafana)." msgstr "" -#: ../system/objects/external-data-source-example.rst:34 -msgid "**Example:** ``https://dummyjson.com/products/search?q=#{search.term}``" +#: ../system/integrations/elasticsearch.rst:7 +msgid "" +"If you want to take full advantage of the Zammad reporting, have a look at " +"our :docs:`Grafana ` " +"setup page as well." msgstr "" -#: ../system/objects/external-data-source-example.rst:36 -msgid "" -"After that, head down to the preview section and enter a search input for " -"the external data source." +#: ../system/integrations/elasticsearch.rst:11 ../system/subscription.rst:7 +msgid "**🚧 Hosted environment specific 🚧**" msgstr "" -#: ../system/objects/external-data-source-example.rst:39 -#, fuzzy -msgid "**Example:** ``mac``" -msgstr "Ejemplo" +#: ../system/integrations/elasticsearch.rst:13 +msgid "" +"This integration is only available for Hosted setups. In order to use " +"Elasticsearch you'll need the **Plus** subscription." +msgstr "" -#: ../system/objects/external-data-source-example.rst:41 -msgid "Then you can find a preview of the response data below:" +#: ../system/integrations/elasticsearch.rst:16 +msgid "" +"Self hosted users have all the control over their self hosted Elasticsearch " +"instances." msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of JSON response based on search term" +#: ../system/integrations/elasticsearch.rst:None +msgid "Elasticsearch integration page on SaaS environments" msgstr "" -#: ../system/objects/external-data-source-example.rst:48 +#: ../system/integrations/elasticsearch.rst:27 msgid "" -"We recommend using the preview to have a look on the structure. There is a " -"top-level element called ``products``. One level below, you can find the " -"attributes ``id`` and ``title``." +"Please note the following limitations of Elasticsearch access on hosted " +"environments:" msgstr "" -#: ../system/objects/external-data-source-example.rst:52 -msgid "**Search result response based on search from example:**" +#: ../system/integrations/elasticsearch.rst:30 +msgid "access to the Elasticsearch index is read-only access" msgstr "" -#: ../system/objects/external-data-source-example.rst:119 -msgid "" -"To tell the remote system that the desired data is located below the " -"``products`` level, you have to put it in the field *Search result list key*." +#: ../system/integrations/elasticsearch.rst:31 +msgid "currently you're limited to user only" msgstr "" -#: ../system/objects/external-data-source-example.rst:122 +#: ../system/integrations/elasticsearch.rst:32 msgid "" -"After inserting ``products`` in the mentioned field, you get an extended " -"preview. You can find an additional box *Search result list* with a JSON " -"structure. This is the same response as before but stripped from the upper " -"``products`` element by the external data source." +"Reporting tools that require to write into the indexes (like Kibana) are not " +"supported" msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of JSON response search result list" +#: ../system/integrations/elasticsearch.rst:34 +msgid "IP access restriction is currently not yet supported" msgstr "" -#: ../system/objects/external-data-source-example.rst:132 -msgid "" -"Now you need to provide the keys for the search result values and labels. As " -"already mentioned, we are looking for the ``id`` and the ``title`` of our " -"products. If you haven't already, it is now a good time to look at the " -"preview of the *Search result list*." +#: ../system/integrations/elasticsearch.rst:37 +msgid "Activating Elasticsearch Access" msgstr "" -#: ../system/objects/external-data-source-example.rst:197 +#: ../system/integrations/elasticsearch.rst:39 msgid "" -"After locating our two keys, we insert them in *search result value key* " -"(``id``) and in *Search result label key* (``title``)." +"By default external access to your Elasticsearch index is not active. You " +"can enable the integration at any time if needed." msgstr "" -#: ../system/objects/external-data-source-example.rst:200 +#: ../system/integrations/elasticsearch.rst:42 msgid "" -"Basically, we configured the external data source already and we can see a " -"table in the preview section:" +"Please ensure to note down the password provided - you won't have access to " +"it afterwards." msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of product table based on search term" +#: ../system/integrations/elasticsearch.rst:None +msgid "Screencast showing activation of Elasticsearch integration" msgstr "" -#: ../system/objects/external-data-source-example.rst:208 -msgid "" -"According to our example story, now just the *Link template* is missing." +#: ../system/integrations/elasticsearch.rst:51 +msgid "Connection Settings" msgstr "" -#: ../system/objects/external-data-source-example.rst:210 +#: ../system/integrations/elasticsearch.rst:53 msgid "" -"Please note that this is an optional feature. If you don't want to use such " -"links, of course you don't have to configure it." +"This section holds the most important general information for accessing your " +"Elasticsearch indexes - such as:" msgstr "" -#: ../system/objects/external-data-source-example.rst:213 -msgid "" -"We can add now an address where additional product information can be found." +#: ../system/integrations/elasticsearch.rst:57 +msgid "A unique subdomain that does not tell your real instance URL." msgstr "" -#: ../system/objects/external-data-source-example.rst:215 -msgid "Example: ``https://your_domain.com/q=#{ticket.product}``" +#: ../system/integrations/elasticsearch.rst:61 +msgid "Software" msgstr "" -#: ../system/objects/external-data-source-example.rst:217 -msgid "In the example, the parameter means:" +#: ../system/integrations/elasticsearch.rst:60 +msgid "" +"The major version of the search index being used. This is required by some " +"Reporting tools like Grafana." msgstr "" -#: ../system/objects/external-data-source-example.rst:219 -msgid "``#{}``: \"Frame\" for the insertion of information" +#: ../system/integrations/elasticsearch.rst:64 +msgid "Authentication" msgstr "" -#: ../system/objects/external-data-source-example.rst:220 -msgid "``ticket``: object level, where you create your custom object" +#: ../system/integrations/elasticsearch.rst:64 +msgid "The authentication type being supported. ``Basic Authentication``" msgstr "" -#: ../system/objects/external-data-source-example.rst:221 -msgid "``product``: name of the (custom) object" +#: ../system/integrations/elasticsearch.rst:67 +msgid "Available Indexes" msgstr "" -#: ../system/objects/external-data-source-example.rst:223 +#: ../system/integrations/elasticsearch.rst:69 msgid "" -"After configuring your *Link template*, there will be another column in the " -"preview. Hovering on the icons in the *Link* column will show you where it " -"forwards you." +"Within this section we're displaying the -in our opinion- most important " +"indexes for a Zammad instance." msgstr "" -#: ../system/objects/external-data-source-example.rst:232 +#: ../system/integrations/elasticsearch.rst:72 msgid "" -"In our example, one of the links looks like: https://your_domain.com/q=6, " -"where the 6 is the product id." +"If you require all indexes or our listing is not good enough for you, point " +"your browser to the URL we're providing and append ``/_aliases?" +"pretty=true``. The result should look like this: ``https://.zammad.com/" +"_aliases?pretty=true``." msgstr "" -#: ../system/objects/external-data-source-example.rst:235 -#, fuzzy -msgid "You can find more information regarding the URL in :doc:`types`." +#: ../system/integrations/elasticsearch.rst:77 +msgid "" +"Your browser will automatically ask for your credentials - you'll then see " +"something like this:" msgstr "" -"También puede encontrar más información sobre la personalización del chat en " -"el área de administración." -#: ../system/objects/includes/adding-values-hint.include.rst:3 -msgid "" -"Adding values can be tricky for first timers, don't forget to press \"➕ " -"Add\" after typing your values. Otherwise you may loose a value." +#: ../system/integrations/elasticsearch.rst:125 +msgid "Credentials" msgstr "" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:1 -#: ../system/objects/includes/reposition-values.include.rst:1 -msgid "**↕️ This field type allows the positioning of its values ↔️**" +#: ../system/integrations/elasticsearch.rst:127 +msgid "" +"Within this section Zammad displays your available users. The password is " +"provided once (upon activation) and cannot be retrieved after that." msgstr "" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:3 +#: ../system/integrations/elasticsearch.rst:131 msgid "" -"In order to re-arrange the field values, first edit the field. Then you can " -"use ☰ to drag the values in question to the correct position. If you want to " -"change the layer depth, double click on ☰. With it you can cycle through the " -"available layers." +"If you need to change or reset your Elasticsearch user password, use the " +"\"Reset password\" button in the credentials table. Doing so creates a brand " +"new password for the account in question. This change is immediate, keep in " +"mind that this may affect third party tools connected to your instance." msgstr "" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:8 -msgid "When you're ready, submit your changes to save the object attribute." +#: ../system/integrations/exchange.rst:2 +msgid "Exchange" msgstr "" -#: :0 ../system/objects/types.rst:0 +#: ../system/integrations/exchange.rst:4 msgid "" -"Screencast showing how to re-position values on tree select like\n" -"fields" +"With Zammad's Exchange integration, you can easily use existing address " +"books without having to update more than one source." msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:3 +#: ../system/integrations/exchange.rst:7 msgid "" -"In order to re-arrange the field values, edit the field and scroll below the " -"values. Make sure to tick the option \"Use custom option sort\"." +"However, you should refrain from syncing all addresses, as the results may " +"not be what you expect (Exchange collects huge amounts of addresses). A " +"central address book of your company to sync makes more sense, as you can " +"ensure that Zammad gets only the data you need and want. Apart from this, it " +"is even not possible to sync the Global Address List (GAL) of your Exchange " +"system with Zammad." msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:8 +#: ../system/integrations/exchange.rst:16 msgid "" -"If you do not tick this field, all manual positioning you did above will be " -"lost upon saving! ☠️" +"**Exchange and LDAP:** The exchange sync can be overruled by Zammad's LDAP " +"integration. If you have the same users in both sources, the LDAP version " +"will always be Zammad's pick." msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:11 +#: ../system/integrations/exchange.rst:19 msgid "" -"Now use ☰ to drag the values in question to the correct position. When " -"you're ready, submit your changes to save the object attribute." -msgstr "" - -#: :0 ../system/objects/types.rst:0 -msgid "Screencast showing how to re-position values" +"**One way sync:** the Exchange sync is one way. Exchange => Zammad. Changes " +"to your users inside of Zammad might be overwritten by the Exchange sync." msgstr "" -#: ../system/objects/includes/url-template-hint.include.rst:3 +#: ../system/integrations/exchange.rst:24 msgid "" -"This field allows using :ref:`URL fields (Link Templates) `." +"To configure Exchange integration, simply go to the System > Integrations > " +"Exchange in the admin panel. Press \"change\" and follow the wizard for " +"adding the needed Exchange information to Zammad. On the last two steps " +"Zammad will ask you for the address book(s) and your desired attribute " +"mapping. By default, Zammad only maps email address, first- and lastname. " +"Technically, you can map any Exchange object to a Zammad user object (this " +"also works for custom objects!)." msgstr "" -#: ../system/objects/permissions.rst:2 -#, fuzzy -msgid "Attribute Permissions" -msgstr "Versión" - -#: ../system/objects/permissions.rst:7 +#: ../system/integrations/exchange.rst:35 msgid "" -"In the object attributes configuration you can define if a field is shown " -"and if the input in the field is mandatory, separated by different screens " -"and for different :doc:`roles/permissions `." -msgstr "" - -#: ../system/objects/permissions.rst:17 -#, fuzzy -msgid "Screenshot shows object attribute permission table" +"If the SSL verification fails while connecting to Exchange, Zammad will ask " +"you to turn it off temporarily." msgstr "" -"Captura de pantalla que muestra la configuración básica de una cuenta de " -"correo electrónico entrante" -#: ../system/objects/permissions.rst:17 +#: ../system/integrations/exchange.rst:38 msgid "" -"Some of the possible permissions and screen options for a user object " -"attribute." +"Please be aware that **turning off SSL verification is a security risk**. It " +"should only be used temporarily or for testing purposes. If turned off, " +"there is no verification of the certificate, which means that every " +"presented certificate will be accepted." msgstr "" -#: ../system/objects/permissions.rst:19 +#: ../system/integrations/exchange.rst:43 msgid "" -"Based on the object context (ticket, agent, organization, user), the " -"selectable roles (to be precise: the required permissions) and screens " -"differ. Be aware that these settings aren't affecting data creation via " -"other channels than the UI." +"After pressing Continue, Zammad will check if the configuration is okay. You " +"can then enable Exchange and start your first sync. The sync will then run " +"hourly - if you need to change mappings or the address book(s), you can " +"change the configuration at any time." msgstr "" -#: ../system/objects/permissions.rst:24 +#: ../system/integrations/exchange.rst:50 msgid "" -"If you want to have further customization possibilities, you should have a " -"look at the :doc:`core workflows `." +"After the sync has finished, you can find the new Exchange contacts under " +"\"Users\". Zammad integrates them just as normal users." msgstr "" -#: ../system/objects/permissions.rst:28 -msgid "Screens" +#: ../system/integrations/exchange.rst:55 +msgid "" +"In some cases you might see unique IDs as \"Login\" instead of the email " +"address. This is normal and doesn't affect the login or email mapping for " +"that entry." msgstr "" -#: ../system/objects/permissions.rst:30 +#: ../system/integrations/github.rst:4 msgid "" -"In the table below you can find an overview about the different permissions " -"and the available screens Zammad distinguishes between." +"Use GitHub integration to track GitHub issues directly within Zammad " +"tickets. Add issue hyperlinks and get a live summary of metadata like status " +"(open/closed), assignee, labels, and more." msgstr "" -#: ../system/objects/permissions.rst:37 -msgid "Screen" +#: ../system/integrations/github.rst:8 +msgid "Please note that our GitHub integration does not support pull requests." msgstr "" -#: ../system/objects/permissions.rst:38 -msgid "Available for" +#: ../system/integrations/github.rst:None +msgid "Integration page for GitHub" msgstr "" -#: ../system/objects/permissions.rst:40 -msgid "create" +#: ../system/integrations/github.rst:18 +msgid "" +"In your GitHub settings, create a new API token under **Developer settings > " +"Personal access tokens > Generate new token**. Leave the **Scopes** section " +"empty." msgstr "" -#: ../system/objects/permissions.rst:41 ../system/objects/permissions.rst:52 -#: ../system/objects/permissions.rst:59 ../system/objects/permissions.rst:73 -msgid "admin.user" +#: ../system/integrations/github.rst:0 ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to create a new API token" msgstr "" -#: ../system/objects/permissions.rst:42 ../system/objects/permissions.rst:53 -#: ../system/objects/permissions.rst:60 -#, fuzzy -msgid "admin.organization" -msgstr "Ticket > Organización > Nota" - -#: ../system/objects/permissions.rst:43 ../system/objects/permissions.rst:54 -#: ../system/objects/permissions.rst:61 -#, fuzzy -msgid "admin.group" -msgstr "grupo" - -#: ../system/objects/permissions.rst:44 -msgid "Creation dialog for not yet existing data" +#: ../system/integrations/github.rst:27 +msgid "Create a new API key with no scopes/privileges." msgstr "" -#: ../system/objects/permissions.rst:45 -msgid "create_middle" +#: ../system/integrations/github.rst:29 +msgid "🔒 **Will this work for private repos?**" msgstr "" -#: ../system/objects/permissions.rst:46 ../system/objects/permissions.rst:50 -#: ../system/objects/permissions.rst:57 ../system/objects/permissions.rst:66 -#: ../system/objects/permissions.rst:70 -#, fuzzy -msgid "ticket.customer" -msgstr "``#{ticket.customer.web}``" - -#: ../system/objects/permissions.rst:47 ../system/objects/permissions.rst:51 -#: ../system/objects/permissions.rst:58 ../system/objects/permissions.rst:69 -#, fuzzy -msgid "ticket.agent" -msgstr "Ticket > #" +#: ../system/integrations/github.rst:31 +msgid "" +"No. To link private repo issues, **use the** ``repo`` **scope instead**. " +"Bear in mind that the resulting token will have `lots of permissions that it " +"doesn't actually need `_, which presents a security risk if your token ever falls into " +"the wrong hands." +msgstr "" -#: ../system/objects/permissions.rst:48 -msgid "Ticket create dialog (middle section)" +#: ../system/integrations/github.rst:37 +msgid "" +"Unfortunately, because of how GitHub's OAuth token scopes are set up, this " +"is the only way to link issues on private repos." msgstr "" -#: ../system/objects/permissions.rst:49 -msgid "edit" +#: ../system/integrations/github.rst:40 +msgid "Enter your new API token in Zammad and enable GitHub integration." msgstr "" -#: ../system/objects/permissions.rst:55 -msgid "Editing dialog for already existing data" +#: ../system/integrations/github.rst:0 +msgid "Screencast showing how to configure Zammad's GitHub integration" msgstr "" -#: ../system/objects/permissions.rst:56 -msgid "view" +#: ../system/integrations/github.rst:47 +msgid "" +"Use the default API endpoint (``https://api.github.com/graphql``) unless " +"you're using GitHub Enterprise Server." msgstr "" -#: ../system/objects/permissions.rst:62 -msgid "View-only dialog for already existing data" +#: ../system/integrations/github.rst:50 +msgid "" +"Once completed, a new GitHub issues tab will appear in the ticket pane. 🎉" msgstr "" -#: ../system/objects/permissions.rst:64 -msgid "(e.g. user or organization from search)" +#: ../system/integrations/github.rst:59 ../system/integrations/gitlab.rst:52 +msgid "Token verification is taking a long time" msgstr "" -#: ../system/objects/permissions.rst:65 -msgid "signup" +#: ../system/integrations/github.rst:56 ../system/integrations/gitlab.rst:49 +msgid "" +"Slight delays are normal (<2 min.), especially for systems under heavy load." msgstr "" -#: ../system/objects/permissions.rst:67 -msgid "Sign-up screen for new customers" +#: ../system/integrations/github.rst:58 +msgid "" +"Self-hosted administrators, please check your network settings to ensure " +"that your Zammad server can reach ``api.github.com``." msgstr "" -#: ../system/objects/permissions.rst:68 -msgid "invite_customer" +#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 +msgid "I reloaded the page and now the API token is gone" msgstr "" -#: ../system/objects/permissions.rst:71 +#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 msgid "" -"Customer invitation screen (from :doc:`First Steps ` area)" +"This may indicate that Zammad is still verifying your API token. Try " +"reloading the page again in a couple minutes." msgstr "" -#: ../system/objects/permissions.rst:72 -msgid "invite_agent" +#: ../system/integrations/gitlab.rst:2 +msgid "GitLab" msgstr "" -#: ../system/objects/permissions.rst:74 +#: ../system/integrations/gitlab.rst:4 msgid "" -"Agent invitation screen (from :doc:`First Steps ` area)" -msgstr "" - -#: ../system/objects/permissions.rst:78 -msgid "Screen Options" +"Use GitLab integration to track GitLab issues directly within Zammad " +"tickets. Add issue hyperlinks and get a live summary of metadata like status " +"(open/closed), assignee, labels, and more." msgstr "" -#: ../system/objects/permissions.rst:80 +#: ../system/integrations/gitlab.rst:8 msgid "" -"For the different screens you can select \"show\" and \"required\" options." +"Please note that our GitLab integration does not support merge requests." msgstr "" -#: ../system/objects/permissions.rst:82 -msgid "**shown:** Show (check) or hide (uncheck) a field." +#: ../system/integrations/gitlab.rst:None +msgid "Integration page for GitLab" msgstr "" -#: ../system/objects/permissions.rst:83 +#: ../system/integrations/gitlab.rst:18 msgid "" -"**required:** Set a field to mandatory (check). Forces users (via UI and " -"API) to populate the field." +"In your GitLab preferences, create a new API token under **Access Tokens**." msgstr "" -#: ../system/objects/types.rst:7 -msgid "Example external data source" +#: ../system/integrations/gitlab.rst:20 +msgid "Under **Select scopes**, choose ``read_api`` only." msgstr "" -#: ../system/objects/types.rst:2 -msgid "Attribute types" +#: ../system/integrations/gitlab.rst:27 +msgid "🔒 **If you wish to link issues on any private repos...**" msgstr "" -#: ../system/objects/types.rst:4 -msgid "" -"When adding a new object attribute, you can choose between the following " -"attribute types." +#: ../system/integrations/gitlab.rst:29 +msgid "Your API token must belong to an account with access to those repos." msgstr "" -#: ../system/objects/types.rst:14 -msgid "" -"You cannot change the attribute format / type as soon as it is applied. If " -"you no longer need an object attribute, consider disabling it instead of " -"removing." +#: ../system/integrations/gitlab.rst:31 +msgid "Enter your new API token in Zammad and enable GitLab integration." msgstr "" -#: ../system/objects/types.rst:18 -msgid "**What about the translation of my attributes?**" +#: ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to configure Zammad's GitLab integration" msgstr "" -#: ../system/objects/types.rst:20 +#: ../system/integrations/gitlab.rst:40 msgid "" -"For some attribute types you can decide if they should be translatable or " -"not. To be precise, it works only for the selectable fields because the " -"possible choices are known and limited. For the following attribute types, " -"you can set the translatable flag:" +"Use the default API endpoint (``https://gitlab.com/api/graphql``) unless " +"you're a self-hosted GitLab user." +msgstr "" + +#: ../system/integrations/gitlab.rst:43 +msgid "" +"Once completed, a new GitLab issues tab will appear in the ticket pane. 🎉" msgstr "" -#: ../system/objects/types.rst:25 -msgid "*Boolean field*" +#: ../system/integrations/gitlab.rst:51 +msgid "" +"Self-hosted administrators, please check your network settings to ensure " +"that your Zammad server can reach ``gitlab.com``." msgstr "" -#: ../system/objects/types.rst:26 -msgid "*Single selection field*" +#: ../system/integrations/i-doit.rst:2 +msgid "i-doit" msgstr "" -#: ../system/objects/types.rst:27 -msgid "*Multiple selection field*" +#: ../system/integrations/i-doit.rst:4 +msgid "" +"`i-doit `_ is an open-source **configuration " +"management database** - in other words, a tool for keeping tabs on every " +"single piece of your physical and digital infrastructure, from network " +"equipment to virtual machines on down to the faceplates on your rack shelves " +"and more." msgstr "" -#: ../system/objects/types.rst:28 -msgid "*Single tree selection field*" +#: ../system/integrations/i-doit.rst:10 +msgid "" +"What's that got to do with Zammad? Well, if you used tickets to track issues " +"with all that hardware, you might start wishing there was a way they could " +"talk to each other." msgstr "" -#: ../system/objects/types.rst:29 -msgid "*Multiple tree selection field*" +#: ../system/integrations/i-doit.rst:14 +msgid "Zammad gives you two:" msgstr "" -#: ../system/objects/types.rst:31 -msgid "" -"For these types, you can find an additional field *Translate field contents*:" +#: ../system/integrations/i-doit.rst:17 +msgid "1. Add i-doit Links to Zammad Tickets" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Screenshot showing translatable attribute types" +#: ../system/integrations/i-doit.rst:20 ../system/integrations/i-doit.rst:80 +msgid "What Users See" msgstr "" -#: ../system/objects/types.rst:38 -msgid "Screenshot with example of translatable attribute type" +#: ../system/integrations/i-doit.rst:26 +msgid "i-doit integration in Zammad's ticket pane" msgstr "" -#: ../system/objects/types.rst:45 -msgid "Boolean field" +#: ../system/integrations/i-doit.rst:26 +msgid "" +"The i-doit integration will appear under a new 🖨 tab in the ticket pane." msgstr "" -#: ../system/objects/types.rst:41 +#: ../system/integrations/i-doit.rst:28 msgid "" -"Provides a drop-down field with display values for ``true`` and ``false``. " -"Setting a default is mandatory." +"i-doit integration puts a new tab in Zammad's ticket pane where you can add " +"links to existing i-doit devices for easy reference. (See our :user-docs:" +"`user documentation ` to learn " +"how it works in practice)." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Boolean fields" +#: ../system/integrations/i-doit.rst:36 ../system/integrations/i-doit.rst:93 +msgid "How to Set it Up" msgstr "" -#: ../system/objects/types.rst:55 -msgid "Date field" +#: ../system/integrations/i-doit.rst:38 +msgid "" +"It requires i-doit's `API Add-on `_. Make sure to have it properly set up. Use the following setting:" msgstr "" -#: ../system/objects/types.rst:48 -msgid "Provides a date picker field and does not allow default values." +#: ../system/integrations/i-doit.rst:42 +msgid "Active: ``Yes``" msgstr "" -#: ../system/objects/types.rst:52 -msgid "Default time diff (hours)" +#: ../system/integrations/i-doit.rst:43 +msgid "Enforce authentication by username and password: ``No``" msgstr "" -#: ../system/objects/types.rst:51 +#: ../system/integrations/i-doit.rst:45 msgid "" -"This setting helps the user by highlighting the day from now plus the " -"provided value. It *does not* pre-fill the field." +"To set it up, enable the integration in the Zammad admin panel under " +"**System > Integrations > i-doit**:" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Date fields" +#: ../system/integrations/i-doit.rst:None +msgid "i-doit settings within the integration pages" msgstr "" -#: ../system/objects/types.rst:73 -msgid "Date & time field" +#: ../system/integrations/i-doit.rst:53 +msgid "The root URL of your i-doit installation." msgstr "" -#: ../system/objects/types.rst:58 -msgid "Provides a date and time picker – does not allow default values" +#: ../system/integrations/i-doit.rst:62 +msgid "API token" msgstr "" -#: ../system/objects/types.rst:62 -msgid "Allow future" +#: ../system/integrations/i-doit.rst:56 +msgid "" +"Found in the i-doit admin panel under **Interfaces / external data > JSON-" +"RPC API > Common Settings**." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Forbid dates and times in the future." +#: ../system/integrations/i-doit.rst:0 +msgid "i-doit administration interface with API configuration" msgstr "" -#: ../system/objects/types.rst:66 -msgid "Allow past" +#: ../system/integrations/i-doit.rst:67 +msgid "Client ID" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Forbid dates and times in the past." +#: ../system/integrations/i-doit.rst:65 +msgid "A unique name to identify Zammad within i-doit." msgstr "" -#: ../system/objects/types.rst:70 -msgid "Default time diff (minutes)" +#: ../system/integrations/i-doit.rst:67 +msgid "(Zammad does not require you to enter a value here, but i-doit might!)" msgstr "" -#: ../system/objects/types.rst:69 +#: ../system/integrations/i-doit.rst:70 msgid "" -"This setting helps the user by highlighting the day from now plus the " -"provided value. It does not pre-fill the field." +"Here you can decide if the certificate of your i-doit system has to be " +"verified or not. In case you are using custom certificates, please have a " +"look at :doc:`how to add them to Zammad `." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Date & time fields" +#: ../system/integrations/i-doit.rst:77 +msgid "2. List / Create Zammad Tickets in i-doit" msgstr "" -#: ../system/objects/types.rst:86 -msgid "Integer field" +#: ../system/integrations/i-doit.rst:None +msgid "Zammad integration in i-doit's device view" msgstr "" -#: ../system/objects/types.rst:76 +#: ../system/integrations/i-doit.rst:86 msgid "" -"Provides an input field that allows integer usage only. You may define a " -"default value. You cannot enforce comma separation." +"i-doit's ticket system integration gives you a way to see all the tickets " +"for a given device without ever leaving i-doit. (See our :user-docs:`user " +"documentation ` to learn how it " +"works in practice)." msgstr "" -#: ../system/objects/types.rst:80 -msgid "Minimal" +#: ../system/integrations/i-doit.rst:95 +msgid "" +"Enable this integration in the i-doit admin panel under **Interfaces / " +"external data > Trouble Ticket System (TTS) > Configuration**:" msgstr "" -#: ../system/objects/types.rst:80 -msgid "The minimal value the field accepts." +#: ../system/integrations/i-doit.rst:None +msgid "i-doit administration interface with TTS configuration" msgstr "" -#: ../system/objects/types.rst:83 -msgid "Maximal" +#: ../system/integrations/i-doit.rst:104 +msgid "TTS-Type" msgstr "" -#: ../system/objects/types.rst:83 -msgid "The maximum value the field accepts." +#: ../system/integrations/i-doit.rst:104 +msgid "``Zammad``" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Integer fields" +#: ../system/integrations/i-doit.rst:115 +msgid "Username / Password" msgstr "" -#: ../system/objects/types.rst:99 -msgid "Multiple selection field" +#: ../system/integrations/i-doit.rst:107 +msgid "Login credentials for a Zammad agent." msgstr "" -#: ../system/objects/types.rst:89 +#: ../system/integrations/i-doit.rst:109 msgid "" -"Provides a selection field that allows the selection of one or more out of " -"several. This field does allow setting a default value." +"This agent must have **read permission** for all :doc:`groups ` that plan on using the i-doit integration." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Multiple selection fields" +#: ../system/integrations/i-doit.rst:113 +msgid "" +"You may even wish to create a dedicated agent account just for this " +"integration (otherwise, if the agent ever changes her password, you will " +"have to remember to update it here)." msgstr "" -#: ../system/objects/types.rst:112 -msgid "Single selection field" +#: ../system/integrations/i-doit.rst:117 +msgid "URL incl. protocol" msgstr "" -#: ../system/objects/types.rst:102 -msgid "" -"Provides a drop-down field that allows selection of one value out of " -"several. This field does allow setting a default value." +#: ../system/integrations/i-doit.rst:118 +msgid "``https://your.zammad.domain``" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Single selection fields" +#: ../system/integrations/index.rst:2 +msgid "Integrations" msgstr "" -#: ../system/objects/types.rst:142 -msgid "Textarea field" +#: ../system/integrations/index.rst:4 +msgid "" +"Zammad offers numerous integrations that add rich features to your instance." msgstr "" -#: ../system/objects/types.rst:115 -msgid "" -"Provides a text area input field (multiple lines) and thus allows e.g. new " -"lines. You can set a default field value." +#: ../system/integrations/index.rst:6 +msgid "We're still working on this part of our documentation, stay tight!" msgstr "" -#: ../system/objects/types.rst:120 -msgid "" -"Please note that this field *does not* support text formatting or HTML " -"content (rich text)." +#: ../system/integrations/index.rst:10 +msgid "Integrations for Phone Systems" msgstr "" -#: ../system/objects/types.rst:123 -msgid "**🥵 This field can consume a lot of visual space**" +#: ../system/integrations/index.rst:14 +msgid "" +"Your VoIP provider or telephony system is not listed? Possibly your provider " +"supports Zammad by using the generic CTI - if you're unsure ask your " +"provider." msgstr "" -#: ../system/objects/types.rst:125 +#: ../system/integrations/index.rst:18 msgid "" -"Depending on where you use this field type, it may use a lot of visual space " -"if you provide a lot of text. This may be an issue to work with." +"Provider does not support Zammad? Consider creating a `feature request in " +"the Zammad Community `_." msgstr "" -#: ../system/objects/types.rst:130 -msgid "Default" +#: ../system/integrations/index.rst:31 +msgid "Integrations for Authentication and Customers" msgstr "" -#: ../system/objects/types.rst:129 -msgid "" -"The here provided text will be shown within the text area field or new data " -"sets." +#: ../system/integrations/index.rst:44 +msgid "Integrations for Monitoring Systems" msgstr "" -#: ../system/objects/types.rst:134 ../system/objects/types.rst:160 -msgid "Maxlength" +#: ../system/integrations/index.rst:46 +msgid "This section currently misses the following integrations:" msgstr "" -#: ../system/objects/types.rst:0 ../system/objects/types.rst:160 -msgid "You can pick the maximum length of the field." +#: ../system/integrations/index.rst:48 +msgid "Icinga" msgstr "" -#: ../system/objects/types.rst:0 -msgid "The default length of this object is ``500``." +#: ../system/integrations/index.rst:49 +msgid "Monit" msgstr "" -#: ../system/objects/types.rst:139 -msgid "Rows" +#: ../system/integrations/index.rst:50 +msgid "Nagios" msgstr "" -#: ../system/objects/types.rst:0 -msgid "" -"Change the number of rows to dislay so that you can use only the space you " -"really need." +#: ../system/integrations/index.rst:60 +msgid "Integrations for Issue Trackers" msgstr "" -#: ../system/objects/types.rst:0 -msgid "The default number of rows is ``4``." +#: ../system/integrations/index.rst:70 +msgid "Other Integrations" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Textarea fields" +#: ../system/integrations/index.rst:72 +msgid "" +"This section will hold any other integration that can't be grouped up (yet)." msgstr "" -#: ../system/objects/types.rst:165 -msgid "Text field" +#: ../system/integrations/ldap/index.rst:2 +msgid "LDAP / Active Directory" msgstr "" -#: ../system/objects/types.rst:145 -msgid "Provides a text field (one line) and allows choosing a default value." +#: ../system/integrations/ldap/index.rst:4 +msgid "" +"Zammad comes with a powerful LDAP integration that allows you to have a " +"single source of truth. By this you reduce the number of login credentials " +"your user has to remember." msgstr "" -#: ../system/objects/types.rst:148 +#: ../system/integrations/ldap/index.rst:10 msgid "" -"Defines the type of the input field. This allows e.g. your browser to ensure " -"that you provide the specific type." +"The LDAP source is also a perfect candidate for Zammad's :docs:`Kerberos " +"Single Sign-On ` but also works as addition " +"to other :doc:`/settings/security/third-party`." msgstr "" -#: ../system/objects/types.rst:152 -msgid "Currently available:" +#: ../system/integrations/ldap/index.rst:None +msgid "Zammands LDAP management page" msgstr "" -#: ../system/objects/types.rst:155 -msgid "Phone" +#: ../system/integrations/ldap/index.rst:25 +msgid "📝 :doc:`manage`" msgstr "" -#: ../system/objects/types.rst:156 -msgid "Text" +#: ../system/integrations/ldap/index.rst:25 +msgid "Add, modify, remove or re-arrange your LDAP-Sources as needed." msgstr "" -#: ../system/objects/types.rst:157 -msgid "Url *(URL fields disable link-template availability)*" +#: ../system/integrations/ldap/index.rst:30 +msgid "Before you continue, please note the following limitations." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Text fields" +#: ../system/integrations/ldap/index.rst:32 +msgid "Mapping / Synchronizing organizations is not possible" msgstr "" -#: ../system/objects/types.rst:174 -msgid "Single tree selection field" +#: ../system/integrations/ldap/index.rst:36 +msgid "" +"You may want to consider using domain based assignments to overcome this " +"issue. Learn more on :doc:`/manage/organizations/index`." msgstr "" -#: ../system/objects/types.rst:168 +#: ../system/integrations/ldap/index.rst:39 msgid "" -"Provides a select-like field with up to 6 layers of options. Does not allow " -"setting a default value." +"Zammad's LDAP sync is one way. Editing user settings or permissions may be " +"overwritten upon the next sync depending on your configuration." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Tree Select fields" +#: ../system/integrations/ldap/index.rst:41 +msgid "Nested groups are not supported." msgstr "" -#: ../system/objects/types.rst:183 -msgid "Multiple tree selection field" +#: ../system/integrations/ldap/index.rst:42 +msgid "Synchronizing user avatars from LDAP is not supported." msgstr "" -#: ../system/objects/types.rst:177 -msgid "" -"Provides a select-like field with up to 6 layers of options allowing the " -"selection of multiple values. Does not allow setting a default value." +#: ../system/integrations/ldap/index.rst:43 +msgid "Unlike user filters, group filters cannot be changed." msgstr "" -#: ../system/objects/types.rst:302 -msgid "External Data Source field" +#: ../system/integrations/ldap/index.rst:44 +msgid "" +"When a user originates from an LDAP server, Zammad will try to verify the " +"login credentials against LDAP first - if this fails Zammad will check its " +"local database." msgstr "" -#: ../system/objects/types.rst:186 +#: ../system/integrations/ldap/index.rst:50 msgid "" -"Provides a searchable field which fetches data from an external system. This " -"can be useful if you have data outside of Zammad and don't want to maintain " -"both data sources." +"Users can have local passwords even if they're LDAP users! You can learn " +"more about user accounts in general on :doc:`/manage/users/index`." msgstr "" -#: ../system/objects/types.rst:190 -msgid "The feature works as follows:" +#: ../system/integrations/ldap/index.rst:54 +msgid "" +"When several LDAP sources contain the same user (meaning the same email " +"address), the user in question will be updated with every source configured. " +"*The last LDAP source will win.*" msgstr "" -#: ../system/objects/types.rst:192 +#: ../system/integrations/ldap/index.rst:58 msgid "" -"Zammad sends a query with a search string (free text from agent or based on " -"a variable) in a pre-defined format (\"Search URL\") to an external system." +"This is subject to change with `Issue 4109 `_ in the future." msgstr "" -#: ../system/objects/types.rst:195 +#: ../system/integrations/ldap/index.rst:60 msgid "" -"This external system searches for matches and provides a response as a JSON " -"structure to Zammad." +"Synchronization statistics currently affect *all* configured LDAP sources. " +"This also applies for newly added or updated sources." msgstr "" -#: ../system/objects/types.rst:197 +#: ../system/integrations/ldap/index.rst:63 msgid "" -"Zammad just looks for the defined list and value keys, reads the content and " -"displays the value to the user. There is no search on Zammad side." +"This is subject to change with `Issue 4108 `_ in the future." msgstr "" -#: ../system/objects/types.rst:201 +#: ../system/integrations/ldap/index.rst:65 msgid "" -"The usage of a PostgreSQL database for Zammad is required. In any other " -"case, Zammad will hide the external data source type and you are not able to " -"use it. If you want to use this feature, consider to :docs:`migrate your " -"database `." +"Zammad currently has limited fallback server support. You can workaround " +"this by providing several sources - however, ensure to have the exact same " +"configuration on your fallback." msgstr "" -#: ../system/objects/types.rst:205 -msgid "Currently, only ``GET`` is supported as request method." +#: ../system/integrations/ldap/index.rst:69 +msgid "" +"This is subject to improve with `Issue 4107 `_ in the future." msgstr "" -#: ../system/objects/types.rst:206 +#: ../system/integrations/ldap/index.rst:76 msgid "" -"The data structure must be in JSON format and provide the objects in an " -"array." +"This section holds all requests Zammad handled for all LDAP sources. These " +"entries can either contain synchronization information or logins " +"(authentication attempts via Zammad's login interface)." msgstr "" -#: ../system/objects/types.rst:208 +#: ../system/integrations/ldap/index.rst:80 msgid "" -"The endpoint for the external data source has to support search. On Zammad " -"side, there is no search/logic implemented; however, you can define the " -"output key and value based on the result(s) from the response (which " -"provides already filtered content based on the search)." +"By clicking on any request, Zammad will provide even more information. The " +"provided information can be useful when something does not work as expected." msgstr "" -#: ../system/objects/types.rst:212 +#: ../system/integrations/ldap/index.rst:85 msgid "" -"If you receive more results as expected, your external data source search " -"may not work properly or the structure of the URL is not correct. You should " -"get in touch with a responsible person from the external system." +"Especially a LDAP synchronization can cause many log entries. The web " +"interface will always limit the number of shown entries to the last 50 " +"entries." msgstr "" -#: ../system/objects/types.rst:217 +#: ../system/integrations/ldap/index.rst:None msgid "" -"Please have a look :doc:`at our example `, where you can find a possible configuration for a public " -"dummy endpoint." +"Screencast showing LDAP integration log entries and a detail view on\n" +"an entry." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for external data source fields" +#: ../system/integrations/ldap/manage.rst:2 +msgid "Manage LDAP-Sources" msgstr "" -#: ../system/objects/types.rst:242 -msgid "Search URL" +#: ../system/integrations/ldap/manage.rst:6 +msgid "" +"Please keep in mind all current limitations for the LDAP synchronization. " +"This will help to understand scopes of the following operations better." msgstr "" -#: ../system/objects/types.rst:227 -msgid "" -"Set your endpoint where Zammad fetches the data. Please make sure to include " -"a valid search :doc:`variable <../variables>` as an URL parameter. Example " -"for a free text search at user input: ``#{search.term}``" +#: ../system/integrations/ldap/manage.rst:65 +msgid "Add new source" msgstr "" -#: ../system/objects/types.rst:232 +#: ../system/integrations/ldap/manage.rst:10 msgid "" -"If in doubt, ask the responsible person for the external data source how " -"they expect the strucuture of the URL." +"Using the *New Source* button allows you to add new LDAP sources to your " +"installation. You're not limited in the number of sources, however, keep in " +"mind that many sources will also take more time to synchronize." msgstr "" -#: ../system/objects/types.rst:236 +#: ../system/integrations/ldap/manage.rst:14 msgid "" -"Depending on your search variable, the preview might work or not. The reason " -"is that the context might not be available and it is no bug." +"You can choose between different encryption types, namely *SSL* and " +"*STARTTLS* or none of them (\"*No SSL*\"). If you choose *SSL* or " +"*STARTTLS*, Zammad will display an additional *SSL verification* option that " +"allows you to disable the verification, e.g. for self-signed SSL " +"certificates. You can also tell Zammad to use a different port by appending " +"``:`` to your hostname/IP." msgstr "" -#: ../system/objects/types.rst:239 +#: ../system/integrations/ldap/manage.rst:0 msgid "" -"Please also make sure to use a variable which is available in your object " -"context. For example you won't be able to search for a ticket in a user " -"object context." +"Screenshot of configuring a new LDAP source with SSL encryption and SSL " +"verification" msgstr "" -#: ../system/objects/types.rst:252 -#, fuzzy -msgid "SSL Verification" -msgstr "Verificación de correo electrónico" - -#: ../system/objects/types.rst:245 -msgid "Here you can switch the SSL verification to no." +#: ../system/integrations/ldap/manage.rst:26 +msgid "" +"New Source with SSL transport security enabled and certificate verification" msgstr "" -#: ../system/objects/types.rst:249 +#: ../system/integrations/ldap/manage.rst:30 msgid "" -"If your external data source system is using self signed certificates, " -"please have a look :doc:`here ` for " -"further information about how to handle them in Zammad, so you can keep the " -"SSL verification activated." +"Using an user filter can be a good idea if you only require a small subset " +"of your LDAP users in Zammad." msgstr "" -#: ../system/objects/types.rst:258 -msgid "HTTP Authentication" +#: ../system/integrations/ldap/manage.rst:42 +msgid "This especially affects inactive users" msgstr "" -#: ../system/objects/types.rst:255 +#: ../system/integrations/ldap/manage.rst:34 msgid "" -"If your external data source requires an authentication, you can set it " -"here. You can leave it empty or choose between *Basic Authentication* or " -"*Authentication Token* (selecting one of the two methods leads to additional " -"fields where you can enter your credentials/token)." +"As every LDAP behaves differently on which attributes and how they are set, " +"Zammad doesn't care about any flags." msgstr "" -#: ../system/objects/types.rst:265 -msgid "Search result list key" +#: ../system/integrations/ldap/manage.rst:37 +msgid "" +"Users that no longer are returned by your LDAP source will automatically be " +"set to inactive. Zammad assumes that the user was deactivated." msgstr "" -#: ../system/objects/types.rst:261 +#: ../system/integrations/ldap/manage.rst:41 msgid "" -"Defines the level in the JSON structure which provides the list with search " -"results. You can leave it empty, if the data is already provided as an " -"array. If you have to go deeper in the structure, you can provide a path " -"with ``.`` as separators, e.g. ``key.subkey.sub-sub-key``." +"Users will never be removed automatically! If you want to remove obsolete " +"users, use :doc:`/system/data-privacy`." msgstr "" -#: ../system/objects/types.rst:271 -msgid "Search result value key" +#: ../system/integrations/ldap/manage.rst:46 +msgid "Active Directory admins" msgstr "" -#: ../system/objects/types.rst:268 +#: ../system/integrations/ldap/manage.rst:45 msgid "" -"Defines the attribute in the structure in which your external data source " -"provides the *value* for your data. An example would be a product *number*. " -"If you have to go deeper in the structure, you can provide a path with ``.`` " -"as separators, e.g. ``key.subkey.sub-sub-key``." -msgstr "" - -#: ../system/objects/types.rst:277 -msgid "Search result label key" +"Active Directories are quite specific on how to filter for active users only " +"- please see the `Microsoft documentation `_ for more " +"information." msgstr "" -#: ../system/objects/types.rst:274 +#: ../system/integrations/ldap/manage.rst:51 msgid "" -"Defines the attribute in the structure in which your external data source " -"provides the *label* for your data. An example would be a product *name*. If " -"you have to go deeper in the structure, you can provide a path with ``.`` as " -"separators, e.g. ``key.subkey.sub-sub-key``." +"*Do not* manually write pathes of either LDAP attributes or groups. If " +"Zammad does not display them, it either cannot find them or you have a lot " +"of users that don't have the attributes populated." msgstr "" -#: ../system/objects/types.rst:280 +#: ../system/integrations/ldap/manage.rst:55 msgid "" -"In the preview area, you can find the following items (depending on your " -"configuration above):" +"Zammad will always only return attributes that are filled - this reduces the " +"returned list of attributes greatly." msgstr "" -#: ../system/objects/types.rst:283 -msgid "" -"**Error/hint message** (only if configuration is not complete): Zammad tells " -"you, if there is a problem and what you should change in your configuration." +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing how to add a new LDAP source" msgstr "" -#: ../system/objects/types.rst:286 +#: ../system/integrations/ldap/manage.rst:63 msgid "" -"**Search field**: search for an existing attribute in the data source to get " -"a preview. This is required for the fields below to show up." +"If your LDAP system doesn't allow anonymous bind, Zammad detects it and " +"provides you an editable \"Base DN\" *text* field instead of a prefilled " +"*select* field." msgstr "" -#: ../system/objects/types.rst:288 -msgid "" -"**Search result response** (only if configuration is not complete): here you " -"can find a syntax highlighted JSON preview of the response, based on the " -"search term you entered." +#: ../system/integrations/ldap/manage.rst:81 +msgid "Review or edit existing source" msgstr "" -#: ../system/objects/types.rst:291 +#: ../system/integrations/ldap/manage.rst:68 msgid "" -"**Search result list** (only if *search result list key* is properly set): " -"output of the structure under the configured *search result list key*." +"Clicking on a LDAP source will provide a configuration and mapping overview." msgstr "" -#: ../system/objects/types.rst:294 +#: ../system/integrations/ldap/manage.rst:70 msgid "" -"**Preview table** (when fully configured): Zammad shows you a table which " -"includes the found items based on the search string (value, label and " -"optional link). You can use this preview if you don't have the complete data " -"structure of the external system in mind." +"If needed you can then use the *Change* button to update either the name, " +"active state or the whole configuration. If you're changing the whole " +"configuration, the dialogue will be identical to the source creation." msgstr "" -#: ../system/objects/types.rst:299 +#: ../system/integrations/ldap/manage.rst:76 msgid "" -"An example of a configured external data source field from agent perspective:" +"Did your LDAP server change? Different LDAP servers have different " +"structures and default attributes. This causes the LDAP synchronization to " +"likely fail. Consider removing the affected source and re-add it." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Screencast showing the search for a product in a ticket" +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing the update of the source name." msgstr "" -#: ../system/objects/types.rst:307 -msgid "URL fields (Link-Template)" +#: ../system/integrations/ldap/manage.rst:89 +msgid "Re-arrange LDAP source's order" msgstr "" -#: ../system/objects/types.rst:311 +#: ../system/integrations/ldap/manage.rst:84 msgid "" -"This function is restricted to Text, Select and External data source types " -"only." +"You can change the synchronization order for each source at any time. Zammad " +"will synchronize the sources from top to bottom." msgstr "" -#: ../system/objects/types.rst:314 +#: ../system/integrations/ldap/manage.rst:0 msgid "" -"Link-Templates are an amazing way to dynamically generate URLs. They allow " -"you to integrate other systems better without having to manually copy data " -"from Zammad if possible." +"Screencasting showing how to change the source order by using\n" +"drag and drop." msgstr "" -#: ../system/objects/types.rst:320 -msgid "" -"Another great way of communicating with another system may be Zammad's :doc:" -"`Webhooks `." +#: ../system/integrations/ldap/manage.rst:101 +msgid "Remove a source" msgstr "" -#: ../system/objects/types.rst:323 +#: ../system/integrations/ldap/manage.rst:92 msgid "" -"After filling a link-template enabled field, an URL icon will appear on its " -"right. Clicking on the icon opens a new tab." +"If you no longer need the a LDAP source or simply want to start over, you " +"can remove them at any time. This will not remove synchronized users, data " +"synchronized or permissions." msgstr "" -#: ../system/objects/types.rst:328 +#: ../system/integrations/ldap/manage.rst:98 msgid "" -"Even though Zammad displays the link template within object edit and create " -"screens, the function is optional. It's only active if you populate the " -"field." +"Not sure if you'd need the source later on? Set the source to inactive " +"instead of removing it - see *Review or edit existing source* for more." msgstr "" -#: ../system/objects/types.rst:333 -msgid "" -"What's the difference between URL and text fields with link template...?!" +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing how to remove LDAP sources." msgstr "" -#: ../system/objects/types.rst:335 -msgid "" -"Both fields have different use cases. Use ``text`` type text fields when " -"ever you have a *static* url that requires dynamic parameters. If you " -"require a drag & drop like field that you can put in any URL, use ``URL`` " -"type text fields." +#: ../system/integrations/pgp/index.rst:2 +msgid "PGP" msgstr "" -#: ../system/objects/types.rst:340 +#: ../system/integrations/pgp/index.rst:7 msgid "" -"The difference is easier to spot when comparing the fields directly, below " -"screencast shows the result - the dynamic approach uses existing values in " -"the moment of updating to built the URL - e.g. ``https://google.com/search?" -"q=cookies`` - while the URL approach uses the actual URL of the field - e.g. " -"``https://zammad.com``." +"Pretty Good Privacy (PGP) is another method for secure email communication. " +"With PGP, you can exchange **signed** and **encrypted** messages with others." msgstr "" -#: ../system/objects/types.rst:None -msgid "" -"Screencast showing the differents in between URL and text type fields with " -"actual values" +#: ../system/integrations/pgp/index.rst:13 +#: ../system/integrations/smime/index.rst:17 +msgid "Signing" msgstr "" -#: ../system/objects/types.rst:352 -msgid "How does this work...?!" +#: ../system/integrations/pgp/index.rst:11 +msgid "is a proof that a message hasn't been manipulated on its way." msgstr "" -#: ../system/objects/types.rst:354 +#: ../system/integrations/pgp/index.rst:13 msgid "" -"As an example, let's say you have an attribute called ``amazing_attribute`` " -"and you want to open a google search directly with the input from that field." +"In other words, it guarantees message **integrity** and **authenticity**." msgstr "" -#: ../system/objects/types.rst:357 -msgid "" -"Providing the link-template field below allows you to do so: ``https://www." -"google.com/search?q=#{ticket.amazing_attribute}``" +#: ../system/integrations/pgp/index.rst:19 +#: ../system/integrations/smime/index.rst:22 +msgid "Encryption" msgstr "" -#: ../system/objects/types.rst:362 +#: ../system/integrations/pgp/index.rst:16 +#: ../system/integrations/smime/index.rst:20 msgid "" -"You can use any :doc:`Zammad variable ` as long as it's " -"available in the moment you need it." +"scrambles a message so that it can only be unscrambled by the intended " +"recipient." msgstr "" -#: ../system/objects/types.rst:365 +#: ../system/integrations/pgp/index.rst:19 msgid "" -"As a result, you are redirected to Google with a search for the value of the " -"attribute, if you click on the button in the ticket (as you can see in the " -"screencast above)." +"In other words, it guarantees message **privacy** and **data security**." msgstr "" -#: ../system/packages.rst:2 -msgid "Packages" +#: ../system/integrations/pgp/index.rst:25 +msgid "Screenshot of ticket creation with encrypt and sign buttons" msgstr "" -#: ../system/packages.rst:4 -msgid "That's the package management-area." +#: ../system/integrations/pgp/index.rst:25 +msgid "" +"Once PGP has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " +"appear in the ticket composer." msgstr "" -#: ../system/packages.rst:6 -msgid "Individual add-ons for Zammad can be installed and managed here." +#: ../system/integrations/pgp/index.rst:28 +msgid "**Sign button not visible?**" msgstr "" -#: ../system/sessions.rst:2 -msgid "Sessions" +#: ../system/integrations/pgp/index.rst:30 +msgid "" +"Please note that the signing of emails is based on the outgoing email " +"account. That means you have to choose a group with a sender email account, " +"which has a private key assigned." msgstr "" -#: ../system/sessions.rst:4 +#: ../system/integrations/pgp/index.rst:35 +msgid "Handling of Keys" +msgstr "" + +#: ../system/integrations/pgp/index.rst:36 msgid "" -"Sessions management allows reviewing currently known user sessions and " -"allows to end these. The session timeout is affected by :ref:" -"`security_session_timeout` configurations from security settings." +"To use the PGP function, you have to enable the integration (PGP) by " +"switching the toggle to *enabled*." msgstr "" -#: ../system/sessions.rst:None -msgid "Screenshot showing Zammad's session management" +#: ../system/integrations/pgp/index.rst:39 +msgid "" +"You can add keys by clicking the *add key* button. The keys can be imported " +"from a file or you can paste the content of the key in the text box." msgstr "" -#: ../system/sessions.rst:13 -msgid "Zammad will provide the following information:" +#: ../system/integrations/pgp/index.rst:42 +msgid "**Which keys do I have to import?**" msgstr "" -#: ../system/sessions.rst:16 +#: ../system/integrations/pgp/index.rst:44 msgid "" -"The user account this session entry belongs to. It can be normal if a user " -"has several sessions in the list. This can be due to changed browser " -"information or if you use e.g. single sign on methods where the user does " -"not use the log off button." +"For **signing** *outgoing* emails, you have to import the private key of " +"your Zammad email account." msgstr "" -#: ../system/sessions.rst:22 -msgid "Browser" +#: ../system/integrations/pgp/index.rst:47 +msgid "" +"For **encrypting** *outgoing* emails, you have to import the public key of " +"the customer's email account." msgstr "" -#: ../system/sessions.rst:22 -msgid "The browser agent communicated to Zammad." +#: ../system/integrations/pgp/index.rst:50 +msgid "" +"For **verifying the signature** of signed *incoming* emails, you have to " +"import the public key of the customer." msgstr "" -#: ../system/sessions.rst:40 -msgid "Location" +#: ../system/integrations/pgp/index.rst:53 +msgid "" +"For **decrypting** of encrypted *incoming* emails, you have to import the " +"private key of your Zammad email account." msgstr "" -#: ../system/sessions.rst:25 -msgid "" -"The anticipated location based on the users IP address. Depending on the IP " -"address the result shown may differ. This option depends on :doc:`/settings/" -"system/services`." +#: ../system/integrations/pgp/index.rst:57 +msgid "Import Keys From a File" msgstr "" -#: ../system/sessions.rst:29 -msgid "The following information can be shown:" +#: ../system/integrations/pgp/index.rst:58 +msgid "You can import keys from a file in the section **Upload key**:" msgstr "" -#: ../system/sessions.rst:33 -msgid "IP address" +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of adding a key via file" msgstr "" -#: ../system/sessions.rst:32 +#: ../system/integrations/pgp/index.rst:64 msgid "" -"Either if you set *Geo IP services* to inactive or you're using internal IP " -"address which do not provide location information." +"**Supported file formats:** ASCII-armor as well as binary GPG format " +"(basically any GPG supported key format) is supported here." msgstr "" -#: ../system/sessions.rst:40 -msgid "Country (or Country + City)" +#: ../system/integrations/pgp/index.rst:68 +msgid "Import Keys by Pasting the Content" +msgstr "" + +#: ../system/integrations/pgp/index.rst:69 +msgid "You can also paste the key's content in the section **paste key**:" +msgstr "" + +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of adding a key via pasting" msgstr "" -#: ../system/sessions.rst:36 +#: ../system/integrations/pgp/index.rst:75 msgid "" -"If *Geo IP services* is enabled only. Depends on how detailed the available " -"IP address information are." +"**Supported format:** Please note that only ASCII-armor is supported here." msgstr "" -#: ../system/sessions.rst:39 -msgid "" -"Be aware that results can be inaccurate - this technically is not an error." -msgstr "" +#: ../system/integrations/pgp/index.rst:78 +#, fuzzy +msgid "Deleting Keys" +msgstr "Verificación de correo electrónico" -#: ../system/sessions.rst:43 -msgid "Age" +#: ../system/integrations/pgp/index.rst:79 +msgid "" +"If you want to delete a specific key, you can do it by clicking on the menu " +"in the *actions* column and select **delete**:" msgstr "" -#: ../system/sessions.rst:43 -msgid "Provides the time when the session initially has been created." +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of deleting a key" msgstr "" -#: ../system/sessions.rst:50 -msgid "Update" +#: ../system/integrations/pgp/index.rst:88 +msgid "Downloading Keys" msgstr "" -#: ../system/sessions.rst:46 +#: ../system/integrations/pgp/index.rst:89 msgid "" -"Provides the time the user used this session to open Zammad. This timestamp " -"is only updated if the user e.g. reloads, not during normal work on tickets." +"If you want to download your keys, you can do this as well via corresponding " +"action buttons. Depending on the key, you can choose wether you want to " +"download the private or the public key." msgstr "" -#: ../system/sessions.rst:50 -msgid "This timestamp is being used for the session timeout." +#: ../system/integrations/pgp/index.rst:95 +#: ../system/integrations/smime/manage-certificates.rst:76 +msgid "Default Behavior" msgstr "" -#: ../system/sessions.rst:53 +#: ../system/integrations/pgp/index.rst:96 msgid "" -"Use the delete button to remove a single session on behalf of your user." +"Here you can adjust on per group basis, if *sign* and *encryption* is on or " +"off by default. Please be aware, that agents can always override the setting " +"for each individual article." msgstr "" -#: ../system/subscription/billing.rst:2 -msgid "Billing" +#: ../system/integrations/pgp/index.rst:None +msgid "Adjusting default behavior on per group basis" msgstr "" -#: ../system/subscription/billing.rst:4 +#: ../system/integrations/pgp/index.rst:107 msgid "" -"Within the billing tab you can control all billing relevant information like " -"invoices, billing address and the option to cancel your subscription." +"Here you can see the last actions regarding signing and encryption and if " +"they were successful." +msgstr "" + +#: ../system/integrations/pgp/index.rst:117 +msgid "**Sign button is not visible, but keys are imported.**" msgstr "" -#: ../system/subscription/billing.rst:33 -msgid "Billing information" +#: ../system/integrations/pgp/index.rst:115 +msgid "Did you choose a group in the ticket?" msgstr "" -#: ../system/subscription/billing.rst:8 +#: ../system/integrations/pgp/index.rst:116 msgid "" -"All adjusted billing information below only affect future invoices. If your " -"invoice was issued wrong, please contact `our sales team `_." +"Did you import a private key for the email adress, which is used for " +"outgoing emails in the group?" msgstr "" -#: ../system/subscription/billing.rst:14 -msgid "Billing address" +#: ../system/integrations/pgp/index.rst:122 +msgid "**How to obtain keys?**" msgstr "" -#: ../system/subscription/billing.rst:13 +#: ../system/integrations/pgp/index.rst:120 msgid "" -"Provide your company address here, make sure to include the companies name " -"in case required. This address will be referenced on your invoice." +"You can create them yourself! There are some good tutorials on the web on " +"how to create them. Providing keys to Zammad is a prerequisite to use the " +"PGP feature." msgstr "" -#: ../system/subscription/billing.rst:18 -msgid "VAT ID" +#: ../system/integrations/pgp/index.rst:127 +msgid "**It says a passphrase is needed, but I haven't got one.**" msgstr "" -#: ../system/subscription/billing.rst:17 +#: ../system/integrations/pgp/index.rst:125 msgid "" -"Provide your VAT ID here. If applicable your invoice will not contain German " -"VAT. Please make sure to pay the VAT in your country as required." +"If the key is secured with a passphrase, you have to provide it for the " +"import in Zammad. It is possible that keys may have an empty passphrase. " +"However, this is *not* recommended." msgstr "" -#: ../system/subscription/billing.rst:27 -msgid "Billing Email Address" +#: ../system/integrations/pgp/index.rst:132 +msgid "**How do my customers get my new key?**" msgstr "" -#: ../system/subscription/billing.rst:21 +#: ../system/integrations/pgp/index.rst:130 msgid "" -"Usually the instance owner (the person that registered the instance) will " -"receive all emails including the invoices. In case you have your own billing " -"department, you can provide their email address here." +"You have to provide your **public** key in advance. Your customer also has " +"to configure PGP in their email workflow and import your public key. The " +"other way round, you have to get the public key of your customer and have to " +"import it to Zammad." msgstr "" -#: ../system/subscription/billing.rst:25 -msgid "" -"All billing relevant information will then be sent to this email address." +#: ../system/integrations/slack.rst:2 +msgid "Slack" msgstr "" -#: ../system/subscription/billing.rst:27 -msgid "Invoices are sent as attachment (PDF) to this email address." +#: ../system/integrations/slack.rst:4 +msgid "**⚠️ Deprecation warning ⚠️**" msgstr "" -#: ../system/subscription/billing.rst:29 +#: ../system/integrations/slack.rst:6 msgid "" -"Don't forget to press the *Submit* button after you changed above settings." +"Zammad 7 will no longer support this dedicated Slack integration. It is " +"recommended to switch to :doc:`pre-defined webhooks ` instead. Existing Slack integrations should " +"be migrated manually before this feature is dropped." msgstr "" -#: ../system/subscription/billing.rst:0 +#: ../system/integrations/slack.rst:14 msgid "" -"Screenshot showing options for billing information within the\n" -"subscription menu" +"In order to use this feature, please add a new Slack app to your Workspace. " +"The App you need is called ``Incoming WebHooks`` ." msgstr "" -#: ../system/subscription/billing.rst:70 -msgid "Payment history" +#: ../system/integrations/slack.rst:18 +msgid "Why Do I Need This Feature?" msgstr "" -#: ../system/subscription/billing.rst:36 +#: ../system/integrations/slack.rst:20 msgid "" -"The payment history will display a history of all paid invoices. At this " -"point you can also download these in case you need them again." +"If you're already using Slack for your team communication, you'll love this " +"feature! Our Slack integration can push ticket notifications about the last " +"ticket article based on the following events:" msgstr "" -#: ../system/subscription/billing.rst:41 -msgid "" -"You will only find *paid* invoices here. Invoices that are to be billed are " -"not available before the payment is completed." +#: ../system/integrations/slack.rst:24 +msgid "on Ticket creation" msgstr "" -#: ../system/subscription/billing.rst:46 -msgid "Date" +#: ../system/integrations/slack.rst:25 +msgid "on Ticket updates" msgstr "" -#: ../system/subscription/billing.rst:46 -msgid "Date of the invoice creation." +#: ../system/integrations/slack.rst:26 +msgid "on reached reminders" msgstr "" -#: ../system/subscription/billing.rst:49 -msgid "Amount" +#: ../system/integrations/slack.rst:27 +msgid "a Ticket has escalated" msgstr "" -#: ../system/subscription/billing.rst:49 -msgid "Invoice total including VAT if applicable." +#: ../system/integrations/slack.rst:28 +msgid "a Ticket is going to escalate" msgstr "" -#: ../system/subscription/billing.rst:52 +#: ../system/integrations/slack.rst:30 msgid "" -"Contains contract period (monthly or yearly) and hosted plan for the " -"subscription period in question." -msgstr "" - -#: ../system/subscription/billing.rst:63 -msgid "Payment method / Service period" +"Zammad will provide the Ticket title, a direct link to the Ticket, the event " +"type (creation, updated, escalation), the customer, time and the last " +"article that has triggered the notification." msgstr "" -#: ../system/subscription/billing.rst:56 +#: ../system/integrations/slack.rst:34 msgid "" -"Used bank account or credit card as well as the subscription period the " -"invoice is about." +"This will give you further options, as you can see e.g. escalating tickets " +"that are assigned to an agent that's e.g. absent. You can interact faster, " +"as you might see problems earlier (or even before the problem gets one)." msgstr "" -#: ../system/subscription/billing.rst:61 +#: ../system/integrations/slack.rst:38 msgid "" -"It might happen that the invoice date and subscription period differ. This " -"is nothing to worry about, the subscription periods will be accounted later " -"on." +"If needed and wanted, you can even discuss directly about the topic before " +"sending an answer to the customer. Another possible use case would be a " +"agent monitoring new agents and their answers to tickets." msgstr "" -#: ../system/subscription/billing.rst:67 -msgid "Receipt" -msgstr "" +#: ../system/integrations/slack.rst:44 +#, fuzzy +msgid "Configure the Integration" +msgstr "Configuración del widget de chat" -#: ../system/subscription/billing.rst:66 +#: ../system/integrations/slack.rst:46 msgid "" -"Use the arrow to download the invoice in question. You can download all " -"available invoices any time you need to here!" -msgstr "" - -#: ../system/subscription/billing.rst:0 -msgid "Screenshot showing payment history of a hosted instance" -msgstr "" - -#: ../system/subscription/billing.rst:94 -msgid "Do you want to cancel your subscription?" +"First of all, please go to your slack workspace - go to administration => " +"Manage Apps. If you don't have an app yet, you can simply add a new one - " +"just search for ``Incoming WebHooks`` and customize the app to your needs." msgstr "" -#: ../system/subscription/billing.rst:73 +#: ../system/integrations/slack.rst:50 msgid "" -"In case you no longer want to use Zammad's SaaS, you can cancel your " -"subscription by using the red *Yes, please cancel my subscription* button." +"Choose (or create) the channel Zammad should post it's information to and " +"press on \"Add Incoming WebHooks integration\". If you're ready, copy the " +"provided WebHook URL and go to your Zammad installation." msgstr "" -#: ../system/subscription/billing.rst:76 +#: ../system/integrations/slack.rst:56 msgid "" -"Your subscription will end the day after your trial or billing period ends." +"You need administrative rights on the Slack Workspace. The link to the app " +"directory is normally ``https://[workspace-name].slack.com/apps`` ." msgstr "" -#: ../system/subscription/billing.rst:80 +#: ../system/integrations/slack.rst:63 msgid "" -"We will remind you about your cancelled subscription several times up front. " -"After the subscription ended all instance data will be removed. A restore " -"*is not* possible after that point!" -msgstr "" - -#: ../system/subscription/billing.rst:0 -msgid "Screencast showing how to cancel a subscription" -msgstr "" - -#: ../system/subscription/billing.rst:87 -msgid "**😖 Cancelled by accident?**" +"To configure the slack integration, log in to Zammad and go to Integrations " +"(System) => Slack in the admin panel." msgstr "" -#: ../system/subscription/billing.rst:89 +#: ../system/integrations/slack.rst:66 msgid "" -"You can always undo the cancellation via the *Yes, undo the cancellation of " -"my subscription* button up to the last subscription day!" +"Here you can choose on what evens Zammad should post information about a " +"ticket to your Slack channel. Next you need to device what groups shall be " +"affected by this, as anybody with access to that specific Slack channel can " +"read at least parts of the ticket this might be a privacy issue, if you " +"select the wrong groups. The username is simply the name that Zammad uses as " +"display name inside the Slack chat. The channel defines the Slack channel " +"the information is being posted in. As last option, you can set a custom " +"icon for posting to slack." msgstr "" -#: ../system/subscription/billing.rst:0 +#: ../system/integrations/slack.rst:74 msgid "" -"Screenshot showing a red button to cancel the subscription\n" -"cancellation" +"When you're ready, just hit \"Submit\" and enable the integration. Zammad " +"will now post new ticket information based on the trigger you chose. Below " +"the options you have the recent log that shows the latest requests to Slack " +"for debugging if needed." msgstr "" -#: ../system/subscription/index.rst:2 -msgid "Subscription (SaaS)" +#: ../system/integrations/slack.rst:81 +msgid "" +"If you leave the Icon URL empty, Zammad will use the Zammad logo instead. " +"The icon should be a square PNG file." msgstr "" -#: ../system/subscription/index.rst:4 +#: ../system/integrations/slack.rst:90 msgid "" -"The subscription settings page allows you to configure your instances " -"package and number of agents required." +"The following figure shows how it will look if you choose to receive updates " +"on created and updated tickets. On every post Zammad sends to the Slack " +"channel, you can create new threads to discuss about the new article." msgstr "" -#: ../system/subscription/index.rst:9 +#: ../system/integrations/slack.rst:96 msgid "" -"This setting section is only available for Hosted setups. If you're looking " -"for on premise support contracts, please see the `Zammad pricing page " -"`_." +"If you just want to keep track of soon escalating or already escalated " +"tickets, it will look the the following figure. Zammad changes the color in " +"front of the post so you can easily see the state of the ticket." msgstr "" -#: ../system/subscription/index.rst:20 +#: ../system/integrations/slack.rst:102 msgid "" -"The subscription section currently consists of two tabs: Plan & Billing. For " -"your overview we've divided those two tabs into independent sub pages:" +"If you change the state, Zammad will also put information on what state the " +"ticket gets and (if pending state) the date until it pends. You'll also " +"recognize the color codes in front of posts on slack, as they are exact the " +"same the ticket state colors you'll see in Zammad!" msgstr "" -#: ../system/subscription/index.rst:25 -msgid ":doc:`💰 Subscription plan `" +#: ../system/integrations/smime/index.rst:2 +msgid "S/MIME" msgstr "" -#: ../system/subscription/index.rst:24 +#: ../system/integrations/smime/index.rst:11 msgid "" -"Everything affecting your instance subscription functions like number of " -"agents, package and payment method." +"S/MIME is the most widely-supported method for secure email communication. " +"With S/MIME, you can exchange **signed** and **encrypted** messages with " +"others." msgstr "" -#: ../system/subscription/index.rst:28 -msgid ":doc:`🧾 Subscription billing `" +#: ../system/integrations/smime/index.rst:15 +msgid "" +"is proof that a message hasn't been tampered with or sent by an impersonator." msgstr "" -#: ../system/subscription/index.rst:28 +#: ../system/integrations/smime/index.rst:17 msgid "" -"Everything regarding billing address, invoices and account cancellation." +"In other words, it guarantees a message's **integrity** and **authenticity**." msgstr "" -#: ../system/subscription/index.rst:33 -msgid "FAQ" +#: ../system/integrations/smime/index.rst:22 +msgid "In other words, it guarantees **privacy** and **data security**." msgstr "" -#: ../system/subscription/index.rst:37 -msgid "I set up a trial account but am missing functions to test" +#: ../system/integrations/smime/index.rst:28 +msgid "Screencast demo of S/MIME features for both new tickets and replies" msgstr "" -#: ../system/subscription/index.rst:36 +#: ../system/integrations/smime/index.rst:28 msgid "" -"The trial instance is running within the professional package allowing up to " -"three agents." -msgstr "" - -#: ../system/subscription/index.rst:40 -msgid "Can I change package within the trial?" +"Once S/MIME has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " +"appear in the ticket composer." msgstr "" -#: ../system/subscription/index.rst:40 -msgid "No. As soon as the package is changed the subscription begins." +#: ../system/integrations/smime/index.rst:32 +msgid ":doc:`🔪 Prerequisites `" msgstr "" -#: ../system/subscription/index.rst:45 -msgid "What happens to my trial instance after the trial period ended?" +#: ../system/integrations/smime/index.rst:31 +msgid "" +"New to S/MIME? This section helps you to find certificate providers and " +"points out Limitations." msgstr "" -#: ../system/subscription/index.rst:43 -msgid "" -"Your instance will automatically be canceled for you. Please see *What " -"happens to my instance after it has been canceled?* for more." +#: ../system/integrations/smime/index.rst:35 +msgid ":doc:`📝 Manage Certificates `" msgstr "" -#: ../system/subscription/index.rst:58 -msgid "What happens to my instance after it has been canceled?" +#: ../system/integrations/smime/index.rst:35 +msgid "Add and download certificates; configure group default behaviors." msgstr "" -#: ../system/subscription/index.rst:48 -msgid "That depends slightly on your instance state:" +#: ../system/integrations/smime/index.rst:38 +msgid ":doc:`😦 Troubleshooting `" msgstr "" -#: ../system/subscription/index.rst:54 -msgid "Trial instance" +#: ../system/integrations/smime/index.rst:38 +msgid "Took a wrong turn? About recent logs and common issues." msgstr "" -#: ../system/subscription/index.rst:51 +#: ../system/integrations/smime/index.rst:43 msgid "" -"If you're still on trial, we will ice your instance and remind you once " -"again about your instance. We then will wait some days and remove your " -"instance from our system. This is the last time we will inform you by Email." +"For more details on how S/MIME integration works on the agent side, see the :" +"user-docs:`user docs `." msgstr "" -#: ../system/subscription/index.rst:58 -msgid "Paid instance" +#: ../system/integrations/smime/manage-certificates.rst:2 +msgid "Manage Certificates" msgstr "" -#: ../system/subscription/index.rst:57 +#: ../system/integrations/smime/manage-certificates.rst:4 msgid "" -"If you're a paying customer and canceled your subscription, the instance " -"removal will take place the day after your last subscription day." +"S/MIME is **disabled by default**. Enable it to start adding certificates." msgstr "" -#: ../system/subscription/index.rst:60 -msgid "Can removed instances be restored?" +#: ../system/integrations/smime/manage-certificates.rst:10 +msgid "Dialogue to add new certificates or private keys" msgstr "" -#: ../system/subscription/index.rst:61 -msgid "No. Once your instance has been removed, a restoration is not possible." +#: ../system/integrations/smime/manage-certificates.rst:10 +msgid "" +"Manage certificates in the Admin Panel under **System > Integrations > S/" +"MIME**. Certificates may be pasted in as plain text or uploaded from a file." msgstr "" -#: ../system/subscription/plan.rst:2 ../system/subscription/plan.rst:38 -msgid "Plan" -msgstr "" +#: ../system/integrations/smime/manage-certificates.rst:14 +#, fuzzy +msgid "Add Certificate Data" +msgstr "Verificación de correo electrónico" -#: ../system/subscription/plan.rst:16 -msgid "Subscription" +#: ../system/integrations/smime/manage-certificates.rst:36 +msgid "Add Certificate" msgstr "" -#: ../system/subscription/plan.rst:5 +#: ../system/integrations/smime/manage-certificates.rst:17 msgid "" -"On the top of the subscription summary you'll find the number of used and " -"available (booked) agent seats. By using the *see more* link you can also " -"expand an agent list to see the currently configured active agents. This " -"list *does not* count accounts with admin permissions only." +"Import public-key certificates for both your own organization and your " +"contacts." msgstr "" -#: ../system/subscription/plan.rst:0 +#: ../system/integrations/smime/manage-certificates.rst:19 msgid "" -"Within subscription you can always see how many agents are still\n" -"available to add and who uses the seats." +"You can also add a bunch of certificates in one go by providing a single " +"file with all relevant certificates." msgstr "" -#: ../system/subscription/plan.rst:14 -msgid "" -"Learn more on how to manage your agents in general :doc:`here `." +#: ../system/integrations/smime/manage-certificates.rst:22 +msgid "🕵️ **ALWAYS verify certificates in-person or over the phone!**" msgstr "" -#: ../system/subscription/plan.rst:19 +#: ../system/integrations/smime/manage-certificates.rst:24 msgid "" -"This section gives you an overview of the available plans and their " -"functions / limits. If you require a more detailed table, check our " -"`detailed pricing table `_ for more." +"The whole point of signatures is to alert you when someone is trying to " +"pretend to be someone they're not. Never accept a certificate from someone " +"online without verifying it first." msgstr "" -#: ../system/subscription/plan.rst:23 -msgid "" -"Your selection in this step will decide on the base agent price and e.g. " -"agent limits that might apply in the summary step." +#: ../system/integrations/smime/manage-certificates.rst:28 +msgid "📇 **What about trusted certificate authorities?**" msgstr "" -#: ../system/subscription/plan.rst:26 +#: ../system/integrations/smime/manage-certificates.rst:30 msgid "" -"The green *Selected* button will also tell you what plan you're currently in." +"In some cases (e.g. when dealing with large enterprises), you may be given a " +"certificate for an entire CA, rather than a single contact. Add it here to " +"trust *all* certificates issued by that CA." msgstr "" -#: ../system/subscription/plan.rst:30 +#: ../system/integrations/smime/manage-certificates.rst:35 msgid "" -"Trial instances are running at Professional with 3 agents. The plan cannot " -"be changed during the trial for technical reasons, if you require more " -"agents for testing, please contact `our sales team `_ with a reason for the raise request." +"Commercial CAs can usually be verified online. Zammad does not include a " +"list of built-in, trusted CAs." msgstr "" -#: ../system/subscription/plan.rst:0 -msgid "" -"Screenshot showing three available packages for a hosted Zammad\n" -"instance" +#: ../system/integrations/smime/manage-certificates.rst:57 +msgid "Add Private Key" msgstr "" -#: ../system/subscription/plan.rst:83 -msgid "Summary" +#: ../system/integrations/smime/manage-certificates.rst:39 +msgid "" +"Once you've added a public-key certificate, you can import its matching " +"private key." msgstr "" -#: ../system/subscription/plan.rst:41 +#: ../system/integrations/smime/manage-certificates.rst:42 msgid "" -"In this section you can adjust the settings of the previous selected plan." +"Private keys are for **your own organization only**; never ask your contacts " +"for their private keys." msgstr "" -#: ../system/subscription/plan.rst:45 +#: ../system/integrations/smime/manage-certificates.rst:0 msgid "" -"Note that upgrading (more agents, higher package) is always possible, " -"however, downgrading will only happen when your billing period renews." +"S/MIME integration showing configured certificates and possible issues with " +"Logging" msgstr "" -#: ../system/subscription/plan.rst:49 +#: ../system/integrations/smime/manage-certificates.rst:50 msgid "" -"Upgrading resets your billing period and existing credit will be deducted " -"from the new total." +"A note is displayed on certificates with a matching private key (see line 2)." msgstr "" -#: ../system/subscription/plan.rst:58 -msgid "Billing cycle" +#: ../system/integrations/smime/manage-certificates.rst:52 +msgid "📤 **Certificates and private keys must be uploaded separately.**" msgstr "" -#: ../system/subscription/plan.rst:53 +#: ../system/integrations/smime/manage-certificates.rst:54 msgid "" -"You can choose between either monthly or yearly billing. The price per agent " -"will be cheaper if you decide for yearly billing." +"If your certificate and private key are bundled together in the same file or " +"PEM block, import it twice (once using each button)." msgstr "" -#: ../system/subscription/plan.rst:56 -msgid "" -"If you're still trying out things and are unsure of the right package for " -"your instance, you may want to choose monthly first and then upgrade to " -"yearly when you're sure." +#: ../system/integrations/smime/manage-certificates.rst:57 +msgid "Please note that bulk imports of private keys are not possible." msgstr "" -#: ../system/subscription/plan.rst:66 -msgid "Plan: (Starter|Professional|Plus) - Agents" -msgstr "" +#: ../system/integrations/smime/manage-certificates.rst:60 +#, fuzzy +msgid "Download Certificate Data" +msgstr "Verificación de correo electrónico" -#: ../system/subscription/plan.rst:61 -msgid "Choose the number of agents you require for your instance." +#: ../system/integrations/smime/manage-certificates.rst:62 +msgid "" +"You can download the earlier provided certificates and private keys at any " +"time from your Zammad instance." msgstr "" -#: ../system/subscription/plan.rst:63 +#: ../system/integrations/smime/manage-certificates.rst:65 msgid "" -"Keep in mind that some packages may have agent limits. Depending on the " -"previous chosen package, you won't be able to exceed specific agent numbers. " -"Also note that setting less agents than currently configured is not possible." +"Please note that passphrase-protected private keys stay protected and when " +"you download them, you have to know the passphrase to use them after " +"downloading." msgstr "" -#: ../system/subscription/plan.rst:69 -msgid "Total" +#: ../system/integrations/smime/manage-certificates.rst:73 +msgid "Dialogue to download certificates or private keys" msgstr "" -#: ../system/subscription/plan.rst:69 -msgid "This will be the net total you're going to be billed." +#: ../system/integrations/smime/manage-certificates.rst:73 +msgid "Download stored certificates and their keys" msgstr "" -#: ../system/subscription/plan.rst:71 +#: ../system/integrations/smime/manage-certificates.rst:78 msgid "" -"By using the *Update subscription* button, the instance package will be " -"adjusted immediately. If you didn't provide a payment method yet, Zammad " -"will request you to provide one at this point." +"The ticket composer will set all outgoing messages to **signed and " +"encrypted** by default (assuming the required certificates exist)." msgstr "" -#: ../system/subscription/plan.rst:77 -msgid "" -"In case you're still within the trial period, this means that the trial will " -"be over immediately!" +#: ../system/integrations/smime/manage-certificates.rst:82 +msgid "These defaults can be modified on a per-group basis:" msgstr "" -#: ../system/subscription/plan.rst:80 -msgid "Down- or upgrading during the trial period *is not* possible." +#: ../system/integrations/smime/manage-certificates.rst:None +msgid "Zammad allowing to choose the default behavior on per group basis" msgstr "" -#: ../system/subscription/plan.rst:0 -msgid "Screenshot showing payment options and a pricing summary" +#: ../system/integrations/smime/manage-certificates.rst:89 +msgid "" +"Of course, agents can always manually change these settings on each email " +"they send out." msgstr "" -#: ../system/subscription/plan.rst:99 -msgid "Payment method" +#: ../system/integrations/smime/prerequisites.rst:4 +msgid "A certificate *and* private key for your own organization" msgstr "" -#: ../system/subscription/plan.rst:86 -msgid "You can pay via credit card or SEPA mandate." +#: ../system/integrations/smime/prerequisites.rst:6 +msgid "" +"(Use this to ✒️ **sign outgoing messages** and 🔓 **decrypt incoming " +"messages**.)" msgstr "" -#: ../system/subscription/plan.rst:91 -msgid "Credit card" +#: ../system/integrations/smime/prerequisites.rst:9 +msgid "" +"Certificates belonging your contacts, or their issuing certificate authority " +"(CA)" msgstr "" -#: ../system/subscription/plan.rst:89 +#: ../system/integrations/smime/prerequisites.rst:11 msgid "" -"Simply follow the dialogue by clicking *authorize* and confirm -if required " -"by your bank- your consent to Zammad using your card for the payments." +"(Use these to ✅ **verify incoming message signatures** and 🔒 **encrypt " +"outgoing messages**.)" msgstr "" -#: ../system/subscription/plan.rst:95 -msgid "SEPA" +#: ../system/integrations/smime/prerequisites.rst:14 +msgid "🙋 **I'm new to S/MIME. Where can I get a certificate?**" msgstr "" -#: ../system/subscription/plan.rst:94 +#: ../system/integrations/smime/prerequisites.rst:16 msgid "" -"Provide the requested information of the bank account holder and update if " -"you're ready. You'll then receive an email with the SEPA mandate." +"The easiest way to get certificates is to buy an annual subscription through " +"a commercial CA, such as:" msgstr "" -#: ../system/subscription/plan.rst:97 +#: ../system/integrations/smime/prerequisites.rst:19 msgid "" -"Technically there's also the possibility to pay via invoice, however - this " -"method only applies to a fairly low number of instances. Please contact `our " -"sales team `_ for more information." +"`Sectigo (formerly Comodo) `_" msgstr "" -#: ../system/translations.rst:2 -msgid "Translations" +#: ../system/integrations/smime/prerequisites.rst:20 +msgid "`Secorio `_" msgstr "" -#: ../system/translations.rst:4 -msgid "" -"Translations of Zammad are processed centrally in our `Weblate instance " -"`_. This allows non-developers to review " -"and update translation texts of the language they actually speak." +#: ../system/integrations/smime/prerequisites.rst:21 +msgid "`GlobalSign `_" msgstr "" -#: ../system/translations.rst:9 -msgid "" -"Your language is in an incomplete translation state or has typos? Please " -"consider helping us in sorting this out! All you need is either a GitHub " -"account or to register directly in our instance." +#: ../system/integrations/smime/prerequisites.rst:23 +msgid "(Zammad is not affiliated with these CAs in any way.)" msgstr "" -#: ../system/translations.rst:13 +#: ../system/integrations/smime/prerequisites.rst:25 msgid "" -"Did you know? This is also where the documentation translations are handled. " -"🤓" +"You can also generate your own self-signed certificates, but the process is " +"complicated and usually 🙅 **involves extra work for your contacts**." msgstr "" -#: ../system/translations.rst:15 +#: ../system/integrations/smime/prerequisites.rst:29 msgid "" -"Have a look in our :docs:`contribution section ` in the system documentation to get started!" +"Bear in mind that 🤝 **S/MIME only works if the other party is using it, too." +"**" msgstr "" -#: ../system/translations.rst:20 -msgid "Local Translations" +#: ../system/integrations/smime/prerequisites.rst:32 +msgid "Certificate and Private Key Checks on Upload" msgstr "" -#: ../system/translations.rst:22 +#: ../system/integrations/smime/prerequisites.rst:34 msgid "" -"Apart from these system translations, there's still local translations you " -"can manage. This is relevant if you added custom objects that require " -"translations or even custom states and priorities." +"The certificate and public key validation is based on the ``X509v3`` " +"extensions." msgstr "" -#: ../system/translations.rst:None -msgid "Translation management screen within the admin menu" +#: ../system/integrations/smime/prerequisites.rst:49 +msgid "Uploading a *client certificate*?" msgstr "" -#: ../system/translations.rst:31 -msgid "Updating Translations" +#: ../system/integrations/smime/prerequisites.rst:41 +msgid "The following attributes are required then:" msgstr "" -#: ../system/translations.rst:33 -msgid "" -"Because of how Zammad ships translations, the only way to update the system " -"translations is to update your Zammad installation. The benefit of this is " -"that you no longer need internet access during a Zammad upgrade as the " -"package has everything it requires already." +#: ../system/integrations/smime/prerequisites.rst:39 +msgid "Subject Alternative Name (at least one email address has to be present)" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:40 +msgid "Key Usage (``Digital Signature`` and/or ``Key Encipherment``)" msgstr "" -#: ../system/translations.rst:39 -msgid "Translation of Custom Objects" +#: ../system/integrations/smime/prerequisites.rst:41 +msgid "Public key algorithm (either ``RSA`` or ``EC``)" msgstr "" -#: ../system/translations.rst:41 +#: ../system/integrations/smime/prerequisites.rst:43 msgid "" -"No problem at all! You can customize any translation locally, even if it is " -"not initially provided by the system." +"The Extended Key Usage attribute is optional. If the certificate provides " +"the named attribute, than it must contain the value ``E-mail Protection``." msgstr "" -#: ../system/translations.rst:44 +#: ../system/integrations/smime/prerequisites.rst:46 msgid "" -"Translation is supported for a broad number of features, including but not " -"limited to custom:" +"Please note that any usable email adress has to be prefixed with ``email:`` " +"or ``rfc822:``." msgstr "" -#: ../system/translations.rst:47 -msgid "Object Attributes" +#: ../system/integrations/smime/prerequisites.rst:49 +msgid "The named public key algorithms are mandatory for private keys as well." msgstr "" -#: ../system/translations.rst:48 -#, fuzzy -msgid "Ticket Macros" -msgstr "Macros" - -#: ../system/translations.rst:49 -#, fuzzy -msgid "Ticket Overviews" -msgstr "Ticket > Dueño > Dirección" - -#: ../system/translations.rst:50 -#, fuzzy -msgid "Ticket Priorities" -msgstr "prioridad" - -#: ../system/translations.rst:51 -#, fuzzy -msgid "Ticket States" -msgstr "Ticket > Creado en" - -#: ../system/translations.rst:54 -msgid "Customizing Translations" +#: ../system/integrations/smime/prerequisites.rst:54 +msgid "Uploading a *CA certificate*?" msgstr "" -#: ../system/translations.rst:56 +#: ../system/integrations/smime/prerequisites.rst:52 msgid "" -"Within the translation screen, simply click on the **New Translation** " -"button." +"In the case of an uploaded CA certificate, providing the value ``CA:TRUE`` " +"in the attribute *Basic Contstraints*, the previously mentioned attributes " +"are not verified." msgstr "" -#: ../system/translations.rst:None -#, fuzzy -msgid "New translation dialog" -msgstr "Diálogo: Nueva cuenta de correo electrónico" - -#: ../system/translations.rst:62 +#: ../system/integrations/smime/prerequisites.rst:56 msgid "" -"In the dialog you can immediately enter the exact translation source (if you " -"know it) and your custom translation text for it and click **Submit**." +"In general, the usage of any expired (``Not After``) or not yet valid (``Not " +"Before``) certificate is denied for outgoing emails." msgstr "" -#: ../system/translations.rst:65 -msgid "" -"Alternatively, try to search for translation suggestions in the list below. " -"Selecting an item from the list will pre-fill the translation source for you " -"and then you can just enter your custom translation." +#: ../system/integrations/smime/prerequisites.rst:59 +msgid "Example certificate:" msgstr "" -#: ../system/translations.rst:69 +#: ../system/integrations/smime/prerequisites.rst:85 msgid "" -"The target language will always default to your current language selection. " -"If you need to translate for a different language, simply change the " -"selection before submitting." +"Please note that Zammad will distrust senders by default. This means that " +"you're always required to provide certificate data, no matter if for signing " +"or encrypting." msgstr "" -#: ../system/translations.rst:73 -msgid "" -"All your custom translations will show up in the overview table when added. " -"And they will even persist across Zammad updates!" +#: ../system/integrations/smime/prerequisites.rst:89 +msgid "This is by design and can't be adjusted." msgstr "" -#: ../system/translations.rst:76 +#: ../system/integrations/smime/troubleshooting.rst:4 msgid "" -"Make sure to reload your browser if a translated string is not displayed." +"All of the system's latest S/MIME activity is displayed in the **Recent " +"Logs** section." msgstr "" -#: ../system/translations.rst:80 -msgid "Reverting to Original Translations" +#: ../system/integrations/smime/troubleshooting.rst:11 +msgid "Sample entries of in- and outgoing S/MIME related emails." msgstr "" -#: ../system/translations.rst:82 +#: ../system/integrations/smime/troubleshooting.rst:11 msgid "" -"If you want to revert a custom translation to original text, simply use the " -"appropriate action within the row of the overview table." +"Logs report the status and details of all mail, both incoming and outgoing, " +"that used signing/verification or encryption/decryption." msgstr "" -#: ../system/translations.rst:85 +#: ../system/integrations/smime/troubleshooting.rst:14 msgid "" -"Depending on the type of the translation source, the action has a slightly " -"different name:" +"This log does **not** include email sent by :doc:`triggers ` or the :doc:`scheduler `. For those, check your " +"``production.log``." msgstr "" -#: ../system/translations.rst:88 -msgid "**Reset** for customized system translations" +#: ../system/integrations/smime/troubleshooting.rst:20 +msgid "Common Issues" msgstr "" -#: ../system/translations.rst:89 -msgid "**Remove** for customized local translations" +#: ../system/integrations/smime/troubleshooting.rst:30 +msgid "I received a signed/encrypted email before I set up S/MIME integration" msgstr "" -#: ../system/translations.rst:91 +#: ../system/integrations/smime/troubleshooting.rst:23 msgid "" -"In both cases, the action will remove the customized translation after a " -"confirmation." +"No problem. Once S/MIME has been enabled and the appropriate certificates " +"have been added, agents will be prompted to retry verification/decryption on " +"matching emails." msgstr "" -#: ../system/translations.rst:None -msgid "Screenshot showing the location of the Remove action" +#: ../system/integrations/smime/troubleshooting.rst:0 +msgid "Screenshot of user prompt to retry decryption" msgstr "" -#: ../system/translations.rst:99 -msgid "Inline Translations" +#: ../system/integrations/smime/troubleshooting.rst:38 +msgid "The 🔒 **Encrypt** button is disabled" msgstr "" -#: ../system/translations.rst:101 -msgid "" -"If you prefer a more hands-on approach, you can activate the inline or on-" -"screen translation feature by pressing ``ctrl`` + ``alt`` + ``t`` at any " -"time and on any screen." +#: ../system/integrations/smime/troubleshooting.rst:33 +msgid "Have you added the recipient's certificate?" msgstr "" -#: ../system/translations.rst:105 +#: ../system/integrations/smime/troubleshooting.rst:34 +msgid "Are you sure the recipient's certificate is valid?" +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:35 +msgid "Have you checked your ``production.log`` for more details?" +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:37 msgid "" -"All customizable translation texts will be highlighted for you on the " -"screen. Just click into the highlighted area and update the text in place." +"If encryption doesn't work in the composer, it won't work in :doc:`triggers " +"` or the :doc:`scheduler ` either!" msgstr "" -#: ../system/translations.rst:None -msgid "Inline translation mode activated for the Overview screen" +#: ../system/integrations/smime/troubleshooting.rst:42 +msgid "The ✅ **Sign** button is disabled" msgstr "" -#: ../system/translations.rst:112 +#: ../system/integrations/smime/troubleshooting.rst:41 msgid "" -"When finished editing, simply press ``ctrl`` + ``alt`` + ``t`` again to " -"deactivate." +"Have you added **both the certificate and private key** for your " +"organization?" msgstr "" -#: ../system/translations.rst:117 +#: ../system/integrations/smime/troubleshooting.rst:42 msgid "" -"Even though it's available on any screen, the inline translation feature " -"requires admin permissions. It works only for the current language " -"selection. If you need to translate a different language, first change the " -"language in your :user-docs:`profile settings `." +"Does the email address on the certificate match the email address of the " +"agent/group composing the email?" msgstr "" -#: ../system/variables.rst:2 -msgid "Variables" +#: ../system/integrations/smime/troubleshooting.rst:45 +msgid "Error: “Fingerprint already taken”" msgstr "" -#: ../system/variables.rst:4 -msgid "" -"Please note that this is just an overview of available variables. It might " -"be incomplete or variables might not be available within some functions. If " -"you're missing variables or are not sure if something is not working as " -"expected, feel free to ask over at the `Community `_." +#: ../system/integrations/smime/troubleshooting.rst:45 +msgid "Are you sure you haven't added this certificate already?" msgstr "" -#: ../system/variables.rst:10 -msgid "" -"Variables can be called by typing ``::`` (just like text modules in the " -"frontend), as long as you're in a supported text field within the backend. " -"Zammad will display all variables being available within this context and " -"replace it to the variable as soon as you selected an entry." +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Error: “❌ invalid byte sequence in UTF-8”" msgstr "" -#: ../system/variables.rst:15 -msgid "" -"You have an empty field which you referenced and it appears as ``-``? That's " -"currently working as designed - you might want to ensure that these fields " -"always have a value." +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Please ensure to provide PEM formatted certificate and keys." msgstr "" -#: ../system/variables.rst:20 -msgid "Variable Categories" +#: ../system/integrations/smime/troubleshooting.rst:49 +msgid "Did you check if the provided file is a valid certificate or key?" msgstr "" -#: ../system/variables.rst:31 -msgid "Wait, What About Custom Objects?" +#: ../system/integrations/zabbix.rst:2 +msgid "Zabbix Integration" msgstr "" -#: ../system/variables.rst:33 +#: ../system/integrations/zabbix.rst:5 msgid "" -"Good point! Of course, we can't predict what objects you might create, but " -"we can give you a hint on how to put the puzzle together to get your custom " -"values." +"This guide describes how to integrate your Zabbix 5.4 installation with " +"Zammad using the Zabbix webhook feature. This guide will provide " +"instructions on setting up a media type, a user and an action in Zabbix." msgstr "" -#: ../system/variables.rst:36 -msgid "" -"For this, we'll talk about the inner part of the variable (so everything " -"within ``#{}``), please put the outer part around to have a valid variable. " -"The first part of the variable name consist of the object type. Currently " -"these are:" +#: ../system/integrations/zabbix.rst:12 +msgid "Zammad with enabled HTTP Token Authentication" msgstr "" -#: ../system/variables.rst:41 -msgid "Ticket (``ticket``)" +#: ../system/integrations/zabbix.rst:13 +msgid "Zabbix version 5.4 or higher" msgstr "" -#: ../system/variables.rst:42 -msgid "User (``user``)" +#: ../system/integrations/zabbix.rst:16 +msgid "Setting up a Zammad" msgstr "" -#: ../system/variables.rst:43 -msgid "Organization (``organization``)" +#: ../system/integrations/zabbix.rst:18 +msgid "Enable **API Token Access** in Settings > System > API." msgstr "" -#: ../system/variables.rst:44 -msgid "Group (``group``)" +#: ../system/integrations/zabbix.rst:20 +msgid "" +"Create a **new user** for a Zabbix alerter with an **email address** and " +"create a personal user token with **ticket.agent** permissions." +msgstr "" + +#: ../system/integrations/zabbix.rst:24 +msgid "Zabbix Webhook Configuration" msgstr "" -#: ../system/variables.rst:46 +#: ../system/integrations/zabbix.rst:27 +#, fuzzy +msgid "Create a Global Macro" +msgstr "Macros" + +#: ../system/integrations/zabbix.rst:29 msgid "" -"The second part is the name of the object. This is the name you define " -"during object creation and can be found within the object menu at any time. " -"The first and second part of a variable is divided by a point, e.g.: " -"``ticket.number`` which will in total be ``#{ticket.number}``." +"Before setting up the **Webhook**, you need to setup the global macro " +"**{$ZABBIX.URL}**, which must contain the **URL** to the **Zabbix frontend**." msgstr "" -#: ../system/variables.rst:51 +#: ../system/integrations/zabbix.rst:33 msgid "" -"Now, in some situations it's possible that you'll need to use a third part. " -"The best example for such a situation would be a ``select`` or ``tree-" -"select`` field which will by default return the key value, not it's display " -"name. For this, just extend your variable with ``.value``. This will result " -"in ``#{ticket.select.value}``." +"In the **Administration** > **Media types** section, import the `Template`_." msgstr "" -#: ../system/variables.rst:60 -msgid "Using Translated Variables" +#: ../system/integrations/zabbix.rst:38 +msgid "Open the added **Zammad** media type and set:" msgstr "" -#: ../system/variables.rst:62 -msgid "" -"If you want to use a translated variable in triggers or schedulers, you can " -"extend the placeholder like this: ``#{t(ticket.state.name)}``. The ``t`` " -"tells Zammad to search for fitting translated strings. The used output " -"language is based on the system language of Zammad which you can set in the " -"admin panel under :doc:`/settings/branding` or based on the selected locale " -"in the trigger/scheduler edit dialog." +#: ../system/integrations/zabbix.rst:40 +msgid "**zammad\\_access\\_token** to the your **Personal User Token**" msgstr "" -#: ../system/variables.rst:69 +#: ../system/integrations/zabbix.rst:41 msgid "" -"A possible use-case: you want to send your customers updates on tickets via " -"trigger or scheduler which should include the state of the ticket. Using the " -"default ``#{ticket.state.name}`` (without the translation flag ``t()``) " -"would lead to the output of the original (english) name of the state." +"**zammad\\_url** to the **frontend URL** of your **Zammad** installation" msgstr "" -#: ../system/variables.rst:75 -msgid "Date and Time Formatting" +#: ../system/integrations/zabbix.rst:43 +msgid "**zammad\\_customer** to your **Zammad user email**." msgstr "" -#: ../system/variables.rst:77 +#: ../system/integrations/zabbix.rst:44 msgid "" -"The system (trigger/scheduler selected) locale and timezone predefines a " -"default format of date and timestamp. This format is customizable by using " -"the ``dt()`` method." -msgstr "" - -#: ../system/variables.rst:79 -msgid "The method arguments are as follows:" +"**zammad\\_enable\\_tags** to **true** or **false** to enable or disable " +"trigger tags. **Important**: if you enable tag support, each tag is set with " +"a separate request." msgstr "" -#: ../system/variables.rst:81 -msgid "The date or timestamp variable you want to format." +#: ../system/integrations/zabbix.rst:48 +msgid "" +"If you want to prioritize issues according to **severity** values in Zabbix, " +"you can define mapping parameters:" msgstr "" -#: ../system/variables.rst:82 -msgid "The output format string." +#: ../system/integrations/zabbix.rst:51 +msgid "**severity\\_**: Zammad priority ID" msgstr "" -#: ../system/variables.rst:83 -msgid "The timezone to apply (optional)." +#: ../system/integrations/zabbix.rst:53 +msgid "Click the **Update** button to save the **Webhook** settings." msgstr "" -#: ../system/variables.rst:86 +#: ../system/integrations/zabbix.rst:55 msgid "" -"``#{dt(ticket.updated_at, \"%A %Y-%m-%d %H:%M in the office\", \"Europe/" -"Berlin\")}``" +"To receive notifications in **Zammad**, you need to create a **Zabbix user** " +"and add **Media** with the **Zammad** type." msgstr "" -#: ../system/variables.rst:87 -msgid "Monday, 2024-03-18 15:31 in the office" +#: ../system/integrations/zabbix.rst:58 +msgid "" +"For **Send to**: enter any text, as this value is not used, but is required." msgstr "" -#: ../system/variables.rst:89 +#: ../system/integrations/zabbix.rst:61 msgid "" -"If you want to use our example, make sure to paste the string above without " -"formatting (``CTRL+Shift+v``), otherwise it won't work." +"For more information, use the `Zabbix documentation `_." msgstr "" -#: ../system/variables.rst:93 -msgid "The following table lists available format directives:" +#: ../system/maintenance.rst:2 +msgid "Maintenance" msgstr "" -#: ../system/variables.rst:99 -msgid "Parameter" +#: ../system/maintenance.rst:4 +msgid "" +"Zammad comes with a maintenance mode that you can use for e.g. updating the " +"instance or changing settings while restricting availability and functions." msgstr "" -#: ../system/variables.rst:102 -msgid "``%Y``" +#: ../system/maintenance.rst:13 +msgid "Mode" msgstr "" -#: ../system/variables.rst:103 -msgid "Year with 4 digits" +#: ../system/maintenance.rst:8 +msgid "The mode setting allows you to enable or disable the maintenance mode." msgstr "" -#: ../system/variables.rst:104 -msgid "Use ``%y`` for year with 2 digits" +#: ../system/maintenance.rst:10 +msgid "Defaults to *off*." msgstr "" -#: ../system/variables.rst:105 -msgid "``%m``" +#: ../system/maintenance.rst:12 +msgid "" +"The maintenance mode will restrict access to administrative roles only. This " +"means agents and customers are logged off." msgstr "" -#: ../system/variables.rst:106 -msgid "Month of year (as number with zero-padding)" +#: ../system/maintenance.rst:23 +msgid "@Login" msgstr "" -#: ../system/variables.rst:107 -msgid "Use ``%-m`` for month without zero-padding" +#: ../system/maintenance.rst:16 +msgid "" +"This setting allows you to provide a login message within a green banner " +"above the login screen. Click into the green banner in the settings page to " +"adjust your message. To activate the message, activate the *@Login* setting." msgstr "" -#: ../system/variables.rst:108 -msgid "``%d``" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing the default login message within the\n" +"settings page" msgstr "" -#: ../system/variables.rst:109 -msgid "Day of month (as number with zero-padding)" +#: ../system/maintenance.rst:26 +msgid "" +"Send an informative message to **all active sessions**. This comes handy to " +"inform your agents e.g. about mayor outages or to force reloads after " +"configuration changes." msgstr "" -#: ../system/variables.rst:110 -msgid "Use ``%e`` for day without zero-padding" +#: ../system/maintenance.rst:31 +msgid "This is the messages title (slightly bigger than the normal message)." msgstr "" -#: ../system/variables.rst:111 -msgid "``%H``" +#: ../system/maintenance.rst:34 +msgid "The text you want to provide to your logged in sessions." msgstr "" -#: ../system/variables.rst:112 -msgid "Hour of day in 24h notation with zero-padding" +#: ../system/maintenance.rst:39 +msgid "Reload application" msgstr "" -#: ../system/variables.rst:113 -msgid "Use ``%k`` for hour without zero-padding" +#: ../system/maintenance.rst:37 +msgid "" +"Selecting this option will change the message acceptance button from *Close* " +"(with nothing happening) to *Continue session*, which forces the application " +"to reload." msgstr "" -#: ../system/variables.rst:114 -msgid "``%I``" +#: ../system/maintenance.rst:43 +msgid "" +"If you have customers that are logged in to Zammad, they'll also be notified " +"if they're active in that moment." msgstr "" -#: ../system/variables.rst:115 -msgid "Hour of day in 12h notation with zero-padding" +#: ../system/maintenance.rst:48 +msgid "Example without reload application" msgstr "" -#: ../system/variables.rst:116 +#: ../system/maintenance.rst:52 msgid "" -"Use ``%l`` for hour without zero-padding and ``%p`` / ``%P`` for meridian " -"indicator" +"Message setting within Zammad's admin settings without ticket reload " +"application setting." msgstr "" -#: ../system/variables.rst:117 -msgid "``%M``" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing the send message settings without ticket\n" +"reload application set" msgstr "" -#: ../system/variables.rst:118 -msgid "Minute of hour" +#: ../system/maintenance.rst:61 ../system/maintenance.rst:85 +msgid "" +"The modal all other active sessions will see upon pressing *Send to clients*." msgstr "" -#: ../system/variables.rst:120 -msgid "``%S``" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing modal caused by maintenance's message\n" +"without reload application ticket" msgstr "" -#: ../system/variables.rst:121 -msgid "Second of Minute" +#: ../system/maintenance.rst:72 +msgid "Example with reload application" msgstr "" -#: ../system/variables.rst:123 -msgid "``%A``" +#: ../system/maintenance.rst:76 +msgid "" +"Message setting within Zammad's admin settings with ticket reload " +"application setting." msgstr "" -#: ../system/variables.rst:124 -msgid "Weekday name" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing the send message settings with ticket\n" +"reload application set" msgstr "" -#: ../system/variables.rst:125 -msgid "Use ``%a`` for abbreviated name or ``%^A`` for uppercase name" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing modal caused by maintenance's message\n" +"with reload application ticket" msgstr "" -#: ../system/variables.rst:126 -msgid "``%B``" +#: ../system/monitoring.rst:2 +msgid "Monitoring" msgstr "" -#: ../system/variables.rst:127 -msgid "Month name" +#: ../system/monitoring.rst:4 +msgid "" +"This function is only available in self hosted instances. If you use Zammad " +"in our cloud, we are monitoring the system on our own and take steps to fix " +"potential problems directly." msgstr "" -#: ../system/variables.rst:128 -msgid "Use ``%b`` for abbreviated name" +#: ../system/monitoring.rst:11 +msgid "" +"On the monitoring page, you can see the current health state of Zammad under " +"\"*Current Status*\" at the bottom. This can be useful if you want to have a " +"look if everything is up and running. As an example, you could have a look " +"in the monitoring when you assume that some emails aren't processed from " +"Zammad." msgstr "" -#: ../system/variables.rst:129 -msgid "``%U``" +#: ../system/monitoring.rst:17 +msgid "**Can't receive an email and the monitoring response is \"healthy\"?**" msgstr "" -#: ../system/variables.rst:130 -msgid "Week number of current year" +#: ../system/monitoring.rst:19 +msgid "" +"Zammad will just inform you about unprocessable emails. This is not the case " +"for oversized emails. You can adjust the maximum email size in :doc:`../" +"channels/email/settings`." msgstr "" -#: ../system/variables.rst:131 -msgid "Use ``%W`` for a different calculation method" +#: ../system/monitoring.rst:24 +msgid "Monitoring API" msgstr "" -#: ../system/variables.rst:134 +#: ../system/monitoring.rst:26 msgid "" -"We support the known format directives for the Ruby built-in method " -"``strftime`` of the ``DateTime`` class. For more information, see `here " -"`_." +"Beside the indication in the monitoring page, you can also use an external " +"monitoring tool to monitor Zammad's health. To request the health of Zammad, " +"you need to provide the API key (token) to the external monitoring tool. You " +"can copy the token from the \"*Current Token*\" field as well as the whole " +"API endpoint of your system (\"*Health Check*\" field), in which the API " +"token is already included." msgstr "" -#: ../system/variables/article.rst:2 -msgid "Articles" +#: ../system/monitoring.rst:37 +msgid "Screenshot showing Current Token and Health Check" msgstr "" -#: ../system/variables/article.rst:4 ../system/variables/config.rst:4 -#: ../system/variables/current-user.rst:4 ../system/variables/ticket.rst:4 -msgid "" -"If you're missing variables or are not sure if something is not working as " -"expected, feel free to ask over at the `Community `_." +#: ../system/monitoring.rst:37 +msgid "Screenshot showing Token and Health Check" msgstr "" -#: ../system/variables/article.rst:6 +#: ../system/monitoring.rst:39 msgid "" -"Below you can find all available ticket article-based variables within " -"Zammad. These can be called via Triggers for example. If you're unsure if " -"Zammad does support variables at the point you're at, you can try to type " -"``::`` to check." +"In addition to that, you can reset the auto-generated token to make sure " +"that already configured monitoring systems won't work anymore. So, please " +"use this \"*Reset*\" button only if you know what you do!" msgstr "" -#: ../system/variables/article.rst:9 ../system/variables/config.rst:9 -#: ../system/variables/ticket.rst:9 -msgid "" -"The below list gives you an example what kind of data you can expect, it's " -"not intended to explain the data itself." +#: ../system/monitoring.rst:44 +#, fuzzy +msgid "Example Output" +msgstr "Ejemplo" + +#: ../system/monitoring.rst:0 +msgid "No issues found" msgstr "" -#: ../system/variables/article.rst:11 -msgid "Article Variables" +#: ../system/monitoring.rst:48 ../system/monitoring.rst:60 +msgid "**Indicator in Zammad**:" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "name" +#: ../system/monitoring.rst:0 +msgid "Screenshot showing monitoring with no issues" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "variable" +#: ../system/monitoring.rst:54 ../system/monitoring.rst:66 +msgid "**API response**::" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "example" +#: ../system/monitoring.rst:0 +msgid "Issues were found" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Web" +#: ../system/monitoring.rst:0 +msgid "Screenshot showing monitoring with issues" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.web}``" +#: ../system/objects.rst:2 +msgid "Objects" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``https://zammad.com`` or empty if not set in user object" +#: ../system/objects.rst:4 +msgid "" +"In Zammad you can add your own fields to tickets, users, organizations and " +"even groups (these are called \"objects\"). This can be useful if you need " +"to add further information to a ticket or any other object in Zammad and the " +"information doesn't fit in any existing field." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > VIP" +#: ../system/objects.rst:11 +msgid "" +"Try to avoid deleting attributes (and disable them instead) as Zammad might " +"run into unexpected conditions if they are referenced somewhere." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.vip}``" +#: ../system/objects.rst:16 +msgid "" +"Here's an overview of object attributes. On the upper right you can add new " +"attributes. By default, there will be no custom fields - standard attributes " +"will be grayed out, you can't delete or change those. You can edit custom " +"attributes (they are displayed in black font and have a trash bin on the " +"right side) just by clicking on them." msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -msgid "``true`` or ``false``" +#: ../system/objects.rst:24 +msgid "" +"Attributes you add to Zammad, no matter if they have default values or not, " +"will not update existing information. This means a new ticket field " +"technically will be empty unless you populate it." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Phone" +#: ../system/objects.rst:28 +msgid "" +"Especially in ticket scope this also means that newly added attributes will " +"be indicated as \"changed\" to agents that view the ticket. This may " +"interfere with Zammad's tabs behavior." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.phone}``" -msgstr "" +#: ../system/objects.rst:40 +#, fuzzy +msgid "Ordering Attributes" +msgstr "Organización & Nombre de Departamento" -#: ../system/variables/article.rst:1 -msgid "``+4930123456789`` or empty if not set in user object" +#: ../system/objects.rst:42 +msgid "" +"Since Zammad introduced :doc:`/system/core-workflows` the need to have a " +"custom positioning for attributes has become more important than ever." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Note" +#: ../system/objects.rst:45 +msgid "" +"To adjust the position of such an attribute, simply click on the attribute " +"entry in question, scroll down and adjust the position number. Please note " +"that you cannot change the positioning of default attributes." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.note}``" +#: ../system/objects.rst:49 +msgid "" +"In case two attributes have the same position value, Zammad will sort " +"alphabetically by name automatically." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Some note about user`` or empty if not set in user object" +#: ../system/objects.rst:None +msgid "" +"Screenshot showing custom attribute entries ordered in between default ones" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Mobile" +#: ../system/objects.rst:56 +msgid "Updating Database After Adding or Editing Attributes" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.mobile}``" +#: ../system/objects.rst:58 +msgid "" +"When adding or changing attributes, Zammad will not apply the changes " +"instantly, but instead shows you the changed attributes first. If you're " +"ready to go, just click on \"Update database\" to apply the changes to " +"Zammad. If you made a mistake or just want to discard your changes, click " +"\"Discard changes\"." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Login" +#: ../system/objects.rst:64 +msgid "" +"After applying the changes with \"Update Database\", a restart of Zammad is " +"**mandatory**. If you don't perform it, you may experience unexpected " +"behavior or even errors. You may want to do this kind of configuration " +"during maintenance windows." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.login}``" +#: ../system/objects.rst:72 +msgid "" +"Changes on objects require you to update the database to apply these changes." msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -#: ../system/variables/ticket.rst:1 -msgid "``jdoe``" +#: ../system/objects.rst:75 +msgid "**🤓 Service restarts can be automated**" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Lastname" +#: ../system/objects.rst:0 +msgid "Hosted environments automatically restart for you." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.lastname}``" +#: ../system/objects.rst:0 +msgid "" +"If you're using a self-hosted installation you can use :docs:`environment " +"variables `" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -#: ../system/variables/ticket.rst:1 -msgid "``Doe`` or empty if not set" +#: ../system/objects.rst:82 +msgid "System Attributes" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Firstname" +#: ../system/objects.rst:84 +msgid "" +"Zammad comes with pre-configured attributes. Some of them can't be edited " +"via UI (or at all). This is required for proper operation of Zammad and not " +"a bug." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.firstname}``" -msgstr "" +#: ../system/objects.rst:90 +#, fuzzy +msgid "Ticket State" +msgstr "Ticket > Creado en" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "``Joe`` or empty if not set" +#: ../system/objects.rst:92 +msgid "" +"If the pre-configured states aren't enough for you or you want to change " +"them, you can do so by clicking on the cogwheel icon in the state row in the " +"ticket tab. But you should be careful when changing pre-configured states. " +"This can lead to unwanted behavior in some cases." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Fax" +#: ../system/objects.rst:None +msgid "Screenshot showing highlighted ticket state attribute" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.fax}``" +#: ../system/objects.rst:122 +msgid "Handling of states" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Email" +#: ../system/objects.rst:102 +msgid "" +"In the state configuration screen, you can add new states, disable states or " +"change states." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.email}``" +#: ../system/objects.rst:0 +msgid "Screenshot showing table of default ticket states" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``jdoe@example.com``" +#: ../system/objects.rst:110 +msgid "" +"To add a new state, click on the \"New Ticket State\" button in the top " +"right corner. To change an existing state, simply click on the affected " +"state. This opens an edit dialog." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Department" +#: ../system/objects.rst:114 +msgid "" +"You can also clone a state or set them to \"Default for new tickets\" or " +"\"Default for follow-ups\" by clicking on the ⁝ action button and select the " +"desired function." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.department}``" +#: ../system/objects.rst:118 +msgid "" +"*Default for new tickets* means that this state is used for every newly " +"created ticket." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Sales`` or empty if not set in user object" +#: ../system/objects.rst:121 +msgid "" +"*Default for follow-ups* means that this state is used if the ticket is re-" +"opened after it was closed." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Address" -msgstr "" +#: ../system/objects.rst:171 +#, fuzzy +msgid "Ticket state in detail" +msgstr "Ticket > Cliente > Correo Electrónico" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.address}``" +#: ../system/objects.rst:125 +msgid "" +"Below you can find a description for each field and option. Please head over " +"to the :ref:`example ` to see the edit dialog." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Some street 1, 12345 Berlin`` or empty if not set in user object" +#: ../system/objects.rst:129 +msgid "" +"This is the name of the state and what you and your agents are seeing when " +"choosing a state somewhere (e.g. in tickets, trigger configuration)." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated" +#: ../system/objects.rst:137 +msgid "" +"There are different state types you can choose from. By default, Zammad " +"comes with one state per state type." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_at}``" +#: ../system/objects.rst:140 +msgid "" +"**new**: for states for tickets that are new and it hasn't been worked on " +"them" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``2019-10-08 15:24:47 UTC``" +#: ../system/objects.rst:142 +msgid "" +"**open**: for states for tickets that are in progress and agents are working " +"on them" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Type > Name" +#: ../system/objects.rst:144 +msgid "**merged**: for states for tickets that are merged with other tickets" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.type.name}``" +#: ../system/objects.rst:145 +msgid "" +"**pending reminder**: for states for tickets that are in progress and you " +"want to set a reminder. (default example: *pending reminder*)" msgstr "" -#: ../system/variables/article.rst:1 +#: ../system/objects.rst:147 msgid "" -"``email`` (`list of article types `_)" +"**pending action**: for states for tickets that are waiting for a specified " +"time and then change their state (default example: *pending close*)" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > To" +#: ../system/objects.rst:150 +msgid "" +"**closed**: for states for tickets that are finished and do not need to be " +"processed further" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.to}``" +#: ../system/objects.rst:153 +msgid "" +"⚠️ Choosing the correct state type is important! If you are in doubt, have a " +"look on the default states and their types!" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``helpdesk@example.com``" +#: ../system/objects.rst:158 +msgid "Ignore escalation" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > TicketID" +#: ../system/objects.rst:157 +msgid "" +"Here you can define whether tickets of this state will count to escalation " +"time or not." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.ticket_id}``" +#: ../system/objects.rst:161 +msgid "" +"You can create a note for the state to inform other admins about the state. " +"This has no effect on tickets." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``1`` (not ticket number)" +#: ../system/objects.rst:165 +msgid "Set the state to *active* or *inactive*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Subject" +#: ../system/objects.rst:167 +msgid "" +"it is technically possible to set all states to inactive. To keep Zammad " +"working in such a case, the inactive flag of one of the states is ignored." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.subject}``" -msgstr "" +#: ../system/objects.rst:194 +#, fuzzy +msgid "Ticket state example" +msgstr "Ticket > Creado en" -#: ../system/variables/article.rst:1 -msgid "``My amazing subject``" +#: ../system/objects.rst:174 +msgid "" +"Let's assume we want to create a new state which indicates that the ticket " +"has to wait for a response of a third party (e.g. service contractor or " +"manufacturer) and we want to to be able to set a reminder." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Sender > Name" +#: ../system/objects.rst:178 +msgid "" +"First we give the new state a proper name. In this example we call it " +"\"waiting for manufacturer\"." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.sender.name}``" +#: ../system/objects.rst:181 +msgid "" +"As state type we choose \"pending reminder\". This indicates that the ticket " +"is still open and we can set a reminder. This reminder can be useful if our " +"manufacturer sometimes isn't responding or we want to remind him to give us " +"an answer." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Customer``, ``Agent`` or ``System``" +#: ../system/objects.rst:186 +msgid "" +"We choose \"no\" for \"ignore escalation\" because we want to escalate the " +"tickets even if we are waiting on the manufacturer's feedback." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Visibility" -msgstr "" +#: ../system/objects.rst:189 +#, fuzzy +msgid "The **result** in the creation dialog will look like this:" +msgstr "El resultado final se parecerá a lo siguiente:" -#: ../system/variables/article.rst:1 -msgid "``#{article.internal}``" +#: ../system/objects.rst:0 +msgid "Screenshot showing ticket state creation dialog with example" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``false`` or ``true`` (false if not internal)" -msgstr "" +#: ../system/objects.rst:199 +#, fuzzy +msgid "Ticket Priority" +msgstr "prioridad" -#: ../system/variables/article.rst:1 -msgid "Article > From" +#: ../system/objects.rst:201 +msgid "" +"If the pre-configured priorities aren't enough for you or you want to change " +"them, you can do so by clicking on the cogwheel icon in the priority row in " +"the ticket tab:" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.from}``" +#: ../system/objects.rst:None +msgid "Screenshot showing highlighted ticket priority attribute" msgstr "" -#: ../system/variables/article.rst:1 -msgid "" -"``Joe Doe `` may differ, depends on ``FROM`` of send mail" +#: ../system/objects.rst:226 +msgid "Handling of priorities" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Web" +#: ../system/objects.rst:210 +msgid "" +"In the priority configuration screen, you can add new priorities, disable " +"priorities or change priorities." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.web}``" +#: ../system/objects.rst:0 +msgid "Screenshot showing table of default ticket priorities" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > VIP" +#: ../system/objects.rst:218 +msgid "" +"To add a new priority, click on the \"New Priority\" button in the top right " +"corner. To change an existing priority, simply click on the affected " +"priority. This opens an edit dialog." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.vip}``" +#: ../system/objects.rst:222 +msgid "" +"You can also clone a priority or set them to \"Default for new tickets\" by " +"clicking on the ⁝ action button and select the desired function." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Phone" +#: ../system/objects.rst:225 +msgid "" +"*Default for new tickets* means that this priority is used for every newly " +"created ticket." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.phone}``" +#: ../system/objects.rst:248 +msgid "Priorities in detail" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Note" +#: ../system/objects.rst:229 +msgid "Below you can find a description for each field and option." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.note}``" +#: ../system/objects.rst:232 +msgid "" +"This is the name of the priority and what you and your agents are seeing " +"when choosing a priority somewhere (e.g. in tickets, trigger configuration)." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Mobile" +#: ../system/objects.rst:242 +msgid "Highlight color" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.mobile}``" +#: ../system/objects.rst:237 +msgid "" +"Switch between *Low priority* (light blue), *High priority* (red) and - " +"(default). This affects the displayed color for ticket titles in overviews." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Login" +#: ../system/objects.rst:241 +msgid "The color options are currently limited to the mentioned options." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.login}``" +#: ../system/objects.rst:245 +msgid "" +"You can create a note for the priority to inform other admins about the " +"priority. This has no effect on tickets." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Lastname" +#: ../system/objects.rst:249 +msgid "Set the priority to *active* or *inactive*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.lastname}``" +#: ../system/objects/external-data-source-example.rst:2 +msgid "External Data Source" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Firstname" +#: ../system/objects/external-data-source-example.rst:4 +msgid "" +"We assume you already had a look on :doc:`types` where you can find a " +"description of the individual fields." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.firstname}``" +#: ../system/objects/external-data-source-example.rst:7 +msgid "" +"To reproduce this example, choose a category you want to add a custom field, " +"click on *New Attribute* and select *External data source field* under " +"*Format*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Fax" +#: ../system/objects/external-data-source-example.rst:11 +msgid "" +"Our example story is to fetch data from an external product database. We " +"want to add our products to the tickets so that the products can be searched " +"and chosen from a list and also create a link to the product website." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.fax}``" +#: ../system/objects/external-data-source-example.rst:16 +msgid "Base configuration" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Email" +#: ../system/objects/external-data-source-example.rst:None +msgid "Initial steps to configure external data source object type" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.email}``" +#: ../system/objects/external-data-source-example.rst:25 +msgid "Name: *product*" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Department" +#: ../system/objects/external-data-source-example.rst:26 +msgid "Display: *Product*" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.department}``" +#: ../system/objects/external-data-source-example.rst:29 +msgid "External data source configuration" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Address" +#: ../system/objects/external-data-source-example.rst:31 +msgid "" +"First, enter the search URL making sure it contains ``#{search.term}`` as a " +"parameter:" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.address}``" +#: ../system/objects/external-data-source-example.rst:34 +msgid "**Example:** ``https://dummyjson.com/products/search?q=#{search.term}``" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created" +#: ../system/objects/external-data-source-example.rst:36 +msgid "" +"After that, head down to the preview section and enter a search input for " +"the external data source." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_at}``" -msgstr "" +#: ../system/objects/external-data-source-example.rst:39 +#, fuzzy +msgid "**Example:** ``mac``" +msgstr "Ejemplo" -#: ../system/variables/article.rst:1 -msgid "Article > Cc" +#: ../system/objects/external-data-source-example.rst:41 +msgid "Then you can find a preview of the response data below:" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.cc}``" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of JSON response based on search term" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``jdoe@example.com, company@example.com``" +#: ../system/objects/external-data-source-example.rst:48 +msgid "" +"We recommend using the preview to have a look on the structure. There is a " +"top-level element called ``products``. One level below, you can find the " +"attributes ``id`` and ``title``." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Text" +#: ../system/objects/external-data-source-example.rst:52 +msgid "**Search result response based on search from example:**" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.body}``" +#: ../system/objects/external-data-source-example.rst:119 +msgid "" +"To tell the remote system that the desired data is located below the " +"``products`` level, you have to put it in the field *Search result list key*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Test`` without formatting (plain)" +#: ../system/objects/external-data-source-example.rst:122 +msgid "" +"After inserting ``products`` in the mentioned field, you get an extended " +"preview. You can find an additional box *Search result list* with a JSON " +"structure. This is the same response as before but stripped from the upper " +"``products`` element by the external data source." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article Text as HTML (not referenced)" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of JSON response search result list" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.body_as_html}``" +#: ../system/objects/external-data-source-example.rst:132 +msgid "" +"Now you need to provide the keys for the search result values and labels. As " +"already mentioned, we are looking for the ``id`` and the ``title`` of our " +"products. If you haven't already, it is now a good time to look at the " +"preview of the *Search result list*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Test`` with formatting" +#: ../system/objects/external-data-source-example.rst:197 +msgid "" +"After locating our two keys, we insert them in *search result value key* " +"(``id``) and in *Search result label key* (``title``)." msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "Ticket > Article#" +#: ../system/objects/external-data-source-example.rst:200 +msgid "" +"Basically, we configured the external data source already and we can see a " +"table in the preview section:" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "``#{ticket.article_count}``" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of product table based on search term" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``1`` number of ticket articles" +#: ../system/objects/external-data-source-example.rst:208 +msgid "" +"According to our example story, now just the *Link template* is missing." msgstr "" -#: ../system/variables/config.rst:2 -msgid "Config" +#: ../system/objects/external-data-source-example.rst:210 +msgid "" +"Please note that this is an optional feature. If you don't want to use such " +"links, of course you don't have to configure it." msgstr "" -#: ../system/variables/config.rst:6 +#: ../system/objects/external-data-source-example.rst:213 msgid "" -"Below you'll find config related variables. These hold useful configuration " -"information that you can use within e.g. triggers to show necessary " -"information to your customer." +"We can add now an address where additional product information can be found." msgstr "" -#: ../system/variables/config.rst:11 -msgid "Config Variables" +#: ../system/objects/external-data-source-example.rst:215 +msgid "Example: ``https://your_domain.com/q=#{ticket.product}``" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Fully Qualified Domain Name" +#: ../system/objects/external-data-source-example.rst:217 +msgid "In the example, the parameter means:" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.fqdn}``" +#: ../system/objects/external-data-source-example.rst:219 +msgid "``#{}``: \"Frame\" for the insertion of information" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``zammad.example.com``" +#: ../system/objects/external-data-source-example.rst:220 +msgid "``ticket``: object level, where you create your custom object" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Ticket Hook" +#: ../system/objects/external-data-source-example.rst:221 +msgid "``product``: name of the (custom) object" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.ticket_hook}``" +#: ../system/objects/external-data-source-example.rst:223 +msgid "" +"After configuring your *Link template*, there will be another column in the " +"preview. Hovering on the icons in the *Link* column will show you where it " +"forwards you." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``Ticket#``" +#: ../system/objects/external-data-source-example.rst:232 +msgid "" +"In our example, one of the links looks like: https://your_domain.com/q=6, " +"where the 6 is the product id." msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > HTTP type" +#: ../system/objects/external-data-source-example.rst:235 +#, fuzzy +msgid "You can find more information regarding the URL in :doc:`types`." msgstr "" +"También puede encontrar más información sobre la personalización del chat en " +"el área de administración." -#: ../system/variables/config.rst:1 -msgid "``#{config.http_type}``" +#: ../system/objects/includes/adding-values-hint.include.rst:3 +msgid "" +"Adding values can be tricky for first timers, don't forget to press \"➕ " +"Add\" after typing your values. Otherwise you may loose a value." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``https`` or ``http``" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:1 +#: ../system/objects/includes/reposition-values.include.rst:1 +msgid "**↕️ This field type allows the positioning of its values ↔️**" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > SystemID" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:3 +msgid "" +"In order to re-arrange the field values, first edit the field. Then you can " +"use ☰ to drag the values in question to the correct position. If you want to " +"change the layer depth, double click on ☰. With it you can cycle through the " +"available layers." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.system_id}``" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:8 +msgid "When you're ready, submit your changes to save the object attribute." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``31`` (value between 1 and 99)" +#: :0 ../system/objects/types.rst:0 +msgid "" +"Screencast showing how to re-position values on tree select like\n" +"fields" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Organization" +#: ../system/objects/includes/reposition-values.include.rst:3 +msgid "" +"In order to re-arrange the field values, edit the field and scroll below the " +"values. Make sure to tick the option \"Use custom option sort\"." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.organization}``" +#: ../system/objects/includes/reposition-values.include.rst:8 +msgid "" +"If you do not tick this field, all manual positioning you did above will be " +"lost upon saving! ☠️" msgstr "" -#: ../system/variables/config.rst:1 +#: ../system/objects/includes/reposition-values.include.rst:11 msgid "" -"``Zammad GmbH`` value set in `Branding `_" +"Now use ☰ to drag the values in question to the correct position. When " +"you're ready, submit your changes to save the object attribute." msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Product Name" +#: :0 ../system/objects/types.rst:0 +msgid "Screencast showing how to re-position values" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.product_name}``" +#: ../system/objects/includes/url-template-hint.include.rst:3 +msgid "" +"This field allows using :ref:`URL fields (Link Templates) `." msgstr "" -#: ../system/variables/config.rst:1 +#: ../system/objects/permissions.rst:2 +#, fuzzy +msgid "Attribute Permissions" +msgstr "Versión" + +#: ../system/objects/permissions.rst:7 msgid "" -"``Helpdesk`` value set in `Branding `_" +"In the object attributes configuration you can define if a field is shown " +"and if the input in the field is mandatory, separated by different screens " +"and for different :doc:`roles/permissions `." msgstr "" -#: ../system/variables/current-user.rst:2 -msgid "Current User" +#: ../system/objects/permissions.rst:17 +#, fuzzy +msgid "Screenshot shows object attribute permission table" msgstr "" +"Captura de pantalla que muestra la configuración básica de una cuenta de " +"correo electrónico entrante" -#: ../system/variables/current-user.rst:6 +#: ../system/objects/permissions.rst:17 msgid "" -"Current user variables always return values of the current user that caused " -"e.g. a trigger to run." +"Some of the possible permissions and screen options for a user object " +"attribute." msgstr "" -#: ../system/variables/current-user.rst:8 +#: ../system/objects/permissions.rst:19 msgid "" -"Due to the above fact, these variables are often not (yet) set or available " -"for usage." +"Based on the object context (ticket, agent, organization, user), the " +"selectable roles (to be precise: the required permissions) and screens " +"differ. Be aware that these settings aren't affecting data creation via " +"other channels than the UI." msgstr "" -#: ../system/variables/current-user.rst:10 +#: ../system/objects/permissions.rst:24 msgid "" -"In situations where e.g. schedulers or triggers run, this most likely is " -"nothing you want to use." -msgstr "" - -#: ../system/variables/current-user.rst:13 -msgid "Current User Variables" +"If you want to have further customization possibilities, you should have a " +"look at the :doc:`core workflows `." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Web" +#: ../system/objects/permissions.rst:28 +msgid "Screens" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.web}``" +#: ../system/objects/permissions.rst:30 +msgid "" +"In the table below you can find an overview about the different permissions " +"and the available screens Zammad distinguishes between." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``https://zammad.org`` or empty if not set" +#: ../system/objects/permissions.rst:37 +msgid "Screen" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > VIP" +#: ../system/objects/permissions.rst:38 +msgid "Available for" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.vip}``" +#: ../system/objects/permissions.rst:40 +msgid "create" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``false`` or ``true``" +#: ../system/objects/permissions.rst:41 ../system/objects/permissions.rst:52 +#: ../system/objects/permissions.rst:59 ../system/objects/permissions.rst:73 +msgid "admin.user" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Web" -msgstr "" +#: ../system/objects/permissions.rst:42 ../system/objects/permissions.rst:53 +#: ../system/objects/permissions.rst:60 +#, fuzzy +msgid "admin.organization" +msgstr "Ticket > Organización > Nota" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.web}``" -msgstr "" +#: ../system/objects/permissions.rst:43 ../system/objects/permissions.rst:54 +#: ../system/objects/permissions.rst:61 +#, fuzzy +msgid "admin.group" +msgstr "grupo" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > VIP" +#: ../system/objects/permissions.rst:44 +msgid "Creation dialog for not yet existing data" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.vip}``" +#: ../system/objects/permissions.rst:45 +msgid "create_middle" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Phone" -msgstr "" +#: ../system/objects/permissions.rst:46 ../system/objects/permissions.rst:50 +#: ../system/objects/permissions.rst:57 ../system/objects/permissions.rst:66 +#: ../system/objects/permissions.rst:70 +#, fuzzy +msgid "ticket.customer" +msgstr "``#{ticket.customer.web}``" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.phone}``" -msgstr "" +#: ../system/objects/permissions.rst:47 ../system/objects/permissions.rst:51 +#: ../system/objects/permissions.rst:58 ../system/objects/permissions.rst:69 +#, fuzzy +msgid "ticket.agent" +msgstr "Ticket > #" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``004930123456789`` or empty if not set" +#: ../system/objects/permissions.rst:48 +msgid "Ticket create dialog (middle section)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Note" +#: ../system/objects/permissions.rst:49 +msgid "edit" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.note}``" +#: ../system/objects/permissions.rst:55 +msgid "Editing dialog for already existing data" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Some note to this user`` or empty if not set" +#: ../system/objects/permissions.rst:56 +msgid "view" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Mobile" +#: ../system/objects/permissions.rst:62 +msgid "View-only dialog for already existing data" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.mobile}``" +#: ../system/objects/permissions.rst:64 +msgid "(e.g. user or organization from search)" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``0049176123456789`` or empty if not set" +#: ../system/objects/permissions.rst:65 +msgid "signup" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Login" +#: ../system/objects/permissions.rst:67 +msgid "Sign-up screen for new customers" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.login}``" +#: ../system/objects/permissions.rst:68 +msgid "invite_customer" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Lastname" +#: ../system/objects/permissions.rst:71 +msgid "" +"Customer invitation screen (from :doc:`First Steps ` area)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.lastname}``" +#: ../system/objects/permissions.rst:72 +msgid "invite_agent" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Firstname" +#: ../system/objects/permissions.rst:74 +msgid "" +"Agent invitation screen (from :doc:`First Steps ` area)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.firstname}``" +#: ../system/objects/permissions.rst:78 +msgid "Screen Options" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``John`` or empty if not set" +#: ../system/objects/permissions.rst:80 +msgid "" +"For the different screens you can select \"show\" and \"required\" options." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Fax" +#: ../system/objects/permissions.rst:82 +msgid "**shown:** Show (check) or hide (uncheck) a field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.fax}``" +#: ../system/objects/permissions.rst:83 +msgid "" +"**required:** Set a field to mandatory (check). Forces users (via UI and " +"API) to populate the field." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``004930123464789`` or empty if not set" +#: ../system/objects/types.rst:7 +msgid "Example external data source" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Email" +#: ../system/objects/types.rst:2 +msgid "Attribute types" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.email}``" +#: ../system/objects/types.rst:4 +msgid "" +"When adding a new object attribute, you can choose between the following " +"attribute types." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``jdoe@customer.tld``" +#: ../system/objects/types.rst:14 +msgid "" +"You cannot change the attribute format / type as soon as it is applied. If " +"you no longer need an object attribute, consider disabling it instead of " +"removing." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Department" +#: ../system/objects/types.rst:18 +msgid "**What about the translation of my attributes?**" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.department}``" +#: ../system/objects/types.rst:20 +msgid "" +"For some attribute types you can decide if they should be translatable or " +"not. To be precise, it works only for the selectable fields because the " +"possible choices are known and limited. For the following attribute types, " +"you can set the translatable flag:" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Sales`` or empty if not set" +#: ../system/objects/types.rst:25 +msgid "*Boolean field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Avatar" +#: ../system/objects/types.rst:26 +msgid "*Single selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.avatar(60,60)}``" +#: ../system/objects/types.rst:27 +msgid "*Multiple selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "avatar picture with width and height in pixel (e.g. 60,60)" +#: ../system/objects/types.rst:28 +msgid "*Single tree selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Address" +#: ../system/objects/types.rst:29 +msgid "*Multiple tree selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.address}``" +#: ../system/objects/types.rst:31 +msgid "" +"For these types, you can find an additional field *Translate field contents*:" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Some street 1, 12345 Berlin`` or empty if not set" +#: ../system/objects/types.rst:0 +msgid "Screenshot showing translatable attribute types" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated at" +#: ../system/objects/types.rst:38 +msgid "Screenshot with example of translatable attribute type" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_at}``" +#: ../system/objects/types.rst:45 +msgid "Boolean field" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC``" +#: ../system/objects/types.rst:41 +msgid "" +"Provides a drop-down field with display values for ``true`` and ``false``. " +"Setting a default is mandatory." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Phone" +#: ../system/objects/types.rst:0 +msgid "Available settings for Boolean fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.phone}``" +#: ../system/objects/types.rst:55 +msgid "Date field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Shared organization" +#: ../system/objects/types.rst:48 +msgid "Provides a date picker field and does not allow default values." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.shared}``" +#: ../system/objects/types.rst:52 +msgid "Default time diff (hours)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Note" +#: ../system/objects/types.rst:51 +msgid "" +"This setting helps the user by highlighting the day from now plus the " +"provided value. It *does not* pre-fill the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.note}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Date fields" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``A note to the organization of the user`` or empty if not set" +#: ../system/objects/types.rst:73 +msgid "Date & time field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Name" +#: ../system/objects/types.rst:58 +msgid "Provides a date and time picker – does not allow default values" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.name}``" +#: ../system/objects/types.rst:62 +msgid "Allow future" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``Zammad GmbH``" +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the future." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Domain based assignment" +#: ../system/objects/types.rst:66 +msgid "Allow past" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.domain_assignment}``" +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the past." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Domain" +#: ../system/objects/types.rst:70 +msgid "Default time diff (minutes)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.domain}``" +#: ../system/objects/types.rst:69 +msgid "" +"This setting helps the user by highlighting the day from now plus the " +"provided value. It does not pre-fill the field." msgstr "" -#: ../system/variables/current-user.rst:1 -#, fuzzy -msgid "``zammad.com`` or empty if not set" -msgstr "``Federico`` o vació si no esta configurado" - -#: ../system/variables/current-user.rst:1 -#, fuzzy -msgid "Current User > Organization > VIP" -msgstr "Ticket > Organización > Nota" - -#: ../system/variables/current-user.rst:1 -#, fuzzy -msgid "``#{user.organization.vip}``" -msgstr "``#{ticket.organization.domain}``" - -#: ../system/variables/current-user.rst:1 -msgid "Current User > Note" +#: ../system/objects/types.rst:0 +msgid "Available settings for Date & time fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.note}``" +#: ../system/objects/types.rst:86 +msgid "Integer field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Mobile" +#: ../system/objects/types.rst:76 +msgid "" +"Provides an input field that allows integer usage only. You may define a " +"default value. You cannot enforce comma separation." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.mobile}``" +#: ../system/objects/types.rst:80 +msgid "Minimal" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Login" +#: ../system/objects/types.rst:80 +msgid "The minimal value the field accepts." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.login}``" +#: ../system/objects/types.rst:83 +msgid "Maximal" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Lastname" +#: ../system/objects/types.rst:83 +msgid "The maximum value the field accepts." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.lastname}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Integer fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Firstname" +#: ../system/objects/types.rst:99 +msgid "Multiple selection field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.firstname}``" +#: ../system/objects/types.rst:89 +msgid "" +"Provides a selection field that allows the selection of one or more out of " +"several. This field does allow setting a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Fax" +#: ../system/objects/types.rst:0 +msgid "Available settings for Multiple selection fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.fax}``" +#: ../system/objects/types.rst:112 +msgid "Single selection field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Email" +#: ../system/objects/types.rst:102 +msgid "" +"Provides a drop-down field that allows selection of one value out of " +"several. This field does allow setting a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.email}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Single selection fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Department" +#: ../system/objects/types.rst:142 +msgid "Textarea field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.department}``" +#: ../system/objects/types.rst:115 +msgid "" +"Provides a text area input field (multiple lines) and thus allows e.g. new " +"lines. You can set a default field value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Web" +#: ../system/objects/types.rst:120 +msgid "" +"Please note that this field *does not* support text formatting or HTML " +"content (rich text)." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.web}``" +#: ../system/objects/types.rst:123 +msgid "**🥵 This field can consume a lot of visual space**" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > VIP" +#: ../system/objects/types.rst:125 +msgid "" +"Depending on where you use this field type, it may use a lot of visual space " +"if you provide a lot of text. This may be an issue to work with." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.vip}``" +#: ../system/objects/types.rst:130 +msgid "Default" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Phone" +#: ../system/objects/types.rst:129 +msgid "" +"The here provided text will be shown within the text area field or new data " +"sets." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.phone}``" +#: ../system/objects/types.rst:134 ../system/objects/types.rst:160 +msgid "Maxlength" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Note" +#: ../system/objects/types.rst:0 ../system/objects/types.rst:160 +msgid "You can pick the maximum length of the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.note}``" +#: ../system/objects/types.rst:0 +msgid "The default length of this object is ``500``." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Mobile" +#: ../system/objects/types.rst:139 +msgid "Rows" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.mobile}``" +#: ../system/objects/types.rst:0 +msgid "" +"Change the number of rows to dislay so that you can use only the space you " +"really need." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Login" +#: ../system/objects/types.rst:0 +msgid "The default number of rows is ``4``." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.login}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Textarea fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Lastname" +#: ../system/objects/types.rst:165 +msgid "Text field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.lastname}``" +#: ../system/objects/types.rst:145 +msgid "Provides a text field (one line) and allows choosing a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Firstname" +#: ../system/objects/types.rst:148 +msgid "" +"Defines the type of the input field. This allows e.g. your browser to ensure " +"that you provide the specific type." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.firstname}``" +#: ../system/objects/types.rst:152 +msgid "Currently available:" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Fax" +#: ../system/objects/types.rst:155 +msgid "Phone" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.fax}``" +#: ../system/objects/types.rst:156 +msgid "Text" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Email" +#: ../system/objects/types.rst:157 +msgid "Url *(URL fields disable link-template availability)*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.email}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Text fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Department" +#: ../system/objects/types.rst:174 +msgid "Single tree selection field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.department}``" +#: ../system/objects/types.rst:168 +msgid "" +"Provides a select-like field with up to 6 layers of options. Does not allow " +"setting a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -#, fuzzy -msgid "Current User > Created by > Avatar" -msgstr "Ticket > Creado por > Apellido" - -#: ../system/variables/current-user.rst:1 -#, fuzzy -msgid "``#{user.created_by.avatar(60,60)}``" -msgstr "``#{ticket.created_by.lastname}``" - -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Address" +#: ../system/objects/types.rst:0 +msgid "Available settings for Tree Select fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.address}``" +#: ../system/objects/types.rst:183 +msgid "Multiple tree selection field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created at" +#: ../system/objects/types.rst:177 +msgid "" +"Provides a select-like field with up to 6 layers of options allowing the " +"selection of multiple values. Does not allow setting a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_at}``" +#: ../system/objects/types.rst:302 +msgid "External Data Source field" msgstr "" -#: ../system/variables/current-user.rst:1 -#, fuzzy -msgid "Current User > Avatar" -msgstr "Ticket > Organización > Nota" - -#: ../system/variables/current-user.rst:1 -msgid "``#{user.avatar(60,60)}``" +#: ../system/objects/types.rst:186 +msgid "" +"Provides a searchable field which fetches data from an external system. This " +"can be useful if you have data outside of Zammad and don't want to maintain " +"both data sources." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Address" +#: ../system/objects/types.rst:190 +msgid "The feature works as follows:" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.address}``" +#: ../system/objects/types.rst:192 +msgid "" +"Zammad sends a query with a search string (free text from agent or based on " +"a variable) in a pre-defined format (\"Search URL\") to an external system." msgstr "" -#: ../system/variables/ticket.rst:6 +#: ../system/objects/types.rst:195 msgid "" -"Below you can find all available ticket-based variables within Zammad. These " -"can be called via Triggers for example. If you're unsure if Zammad does " -"support variables at the point you're at, you can try to type ``::`` to " -"check." +"This external system searches for matches and provides a response as a JSON " +"structure to Zammad." msgstr "" -#: ../system/variables/ticket.rst:12 -msgid "Ticket Variables" +#: ../system/objects/types.rst:197 +msgid "" +"Zammad just looks for the defined list and value keys, reads the content and " +"displays the value to the user. There is no search on Zammad side." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Web" +#: ../system/objects/types.rst:201 +msgid "" +"The usage of a PostgreSQL database for Zammad is required. In any other " +"case, Zammad will hide the external data source type and you are not able to " +"use it. If you want to use this feature, consider to :docs:`migrate your " +"database `." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.web}``" +#: ../system/objects/types.rst:205 +msgid "Currently, only ``GET`` is supported as request method." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > VIP" +#: ../system/objects/types.rst:206 +msgid "" +"The data structure must be in JSON format and provide the objects in an " +"array." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.vip}``" +#: ../system/objects/types.rst:208 +msgid "" +"The endpoint for the external data source has to support search. On Zammad " +"side, there is no search/logic implemented; however, you can define the " +"output key and value based on the result(s) from the response (which " +"provides already filtered content based on the search)." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Phone" +#: ../system/objects/types.rst:212 +msgid "" +"If you receive more results as expected, your external data source search " +"may not work properly or the structure of the URL is not correct. You should " +"get in touch with a responsible person from the external system." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.phone}``" +#: ../system/objects/types.rst:217 +msgid "" +"Please have a look :doc:`at our example `, where you can find a possible configuration for a public " +"dummy endpoint." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Note" +#: ../system/objects/types.rst:0 +msgid "Available settings for external data source fields" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.note}``" +#: ../system/objects/types.rst:242 +msgid "Search URL" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Mobile" +#: ../system/objects/types.rst:227 +msgid "" +"Set your endpoint where Zammad fetches the data. Please make sure to include " +"a valid search :doc:`variable ` as an URL parameter. " +"Example for a free text search at user input: ``#{search.term}``" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.mobile}``" +#: ../system/objects/types.rst:232 +msgid "" +"If in doubt, ask the responsible person for the external data source how " +"they expect the structure of the URL." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Login" +#: ../system/objects/types.rst:236 +msgid "" +"Depending on your search variable, the preview might work or not. The reason " +"is that the context might not be available and it is no bug." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.login}``" +#: ../system/objects/types.rst:239 +msgid "" +"Please also make sure to use a variable which is available in your object " +"context. For example you won't be able to search for a ticket in a user " +"object context." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Lastname" -msgstr "" +#: ../system/objects/types.rst:252 +#, fuzzy +msgid "SSL Verification" +msgstr "Verificación de correo electrónico" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.lastname}``" +#: ../system/objects/types.rst:245 +msgid "Here you can switch the SSL verification to no." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Firstname" +#: ../system/objects/types.rst:249 +msgid "" +"If your external data source system is using self signed certificates, " +"please have a look :doc:`here ` for " +"further information about how to handle them in Zammad, so you can keep the " +"SSL verification activated." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.firstname}``" +#: ../system/objects/types.rst:258 +msgid "HTTP Authentication" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Fax" +#: ../system/objects/types.rst:255 +msgid "" +"If your external data source requires an authentication, you can set it " +"here. You can leave it empty or choose between *Basic Authentication* or " +"*Authentication Token* (selecting one of the two methods leads to additional " +"fields where you can enter your credentials/token)." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.fax}``" +#: ../system/objects/types.rst:265 +msgid "Search result list key" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Email" +#: ../system/objects/types.rst:261 +msgid "" +"Defines the level in the JSON structure which provides the list with search " +"results. You can leave it empty, if the data is already provided as an " +"array. If you have to go deeper in the structure, you can provide a path " +"with ``.`` as separators, e.g. ``key.subkey.sub-sub-key``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.email}``" +#: ../system/objects/types.rst:271 +msgid "Search result value key" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Department" +#: ../system/objects/types.rst:268 +msgid "" +"Defines the attribute in the structure in which your external data source " +"provides the *value* for your data. An example would be a product *number*. " +"If you have to go deeper in the structure, you can provide a path with ``.`` " +"as separators, e.g. ``key.subkey.sub-sub-key``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.department}``" +#: ../system/objects/types.rst:277 +msgid "Search result label key" msgstr "" -#: ../system/variables/ticket.rst:1 -#, fuzzy -msgid "Ticket > Updated by > Avatar" -msgstr "Ticket > Creado por > Apellido" - -#: ../system/variables/ticket.rst:1 -#, fuzzy -msgid "``#{ticket.updated_by.avatar(60,60)}``" -msgstr "``#{ticket.created_by.lastname}``" - -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Address" +#: ../system/objects/types.rst:274 +msgid "" +"Defines the attribute in the structure in which your external data source " +"provides the *label* for your data. An example would be a product *name*. If " +"you have to go deeper in the structure, you can provide a path with ``.`` as " +"separators, e.g. ``key.subkey.sub-sub-key``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.address}``" +#: ../system/objects/types.rst:280 +msgid "" +"In the preview area, you can find the following items (depending on your " +"configuration above):" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated at" +#: ../system/objects/types.rst:283 +msgid "" +"**Error/hint message** (only if configuration is not complete): Zammad tells " +"you, if there is a problem and what you should change in your configuration." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_at}``" +#: ../system/objects/types.rst:286 +msgid "" +"**Search field**: search for an existing attribute in the data source to get " +"a preview. This is required for the fields below to show up." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Title" +#: ../system/objects/types.rst:288 +msgid "" +"**Search result response** (only if configuration is not complete): here you " +"can find a syntax highlighted JSON preview of the response, based on the " +"search term you entered." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.title}``" +#: ../system/objects/types.rst:291 +msgid "" +"**Search result list** (only if *search result list key* is properly set): " +"output of the structure under the configured *search result list key*." msgstr "" -#: ../system/variables/ticket.rst:1 +#: ../system/objects/types.rst:294 msgid "" -"``My amazing Subject`` (normally subject, can be edited within Interface and " -"thus differ)" +"**Preview table** (when fully configured): Zammad shows you a table which " +"includes the found items based on the search string (value, label and " +"optional link). You can use this preview if you don't have the complete data " +"structure of the external system in mind." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Accounted Time" +#: ../system/objects/types.rst:299 +msgid "" +"An example of a configured external data source field from agent perspective:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.time_unit}``" +#: ../system/objects/types.rst:0 +msgid "Screencast showing the search for a product in a ticket" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``1``, ``2.75`` or empty response" +#: ../system/objects/types.rst:307 +msgid "URL fields (Link-Template)" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Tags" +#: ../system/objects/types.rst:311 +msgid "" +"This function is restricted to Text, Select and External data source types " +"only." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.tags}``" +#: ../system/objects/types.rst:314 +msgid "" +"Link-Templates are an amazing way to dynamically generate URLs. They allow " +"you to integrate other systems better without having to manually copy data " +"from Zammad if possible." msgstr "" -#: ../system/variables/ticket.rst:1 +#: ../system/objects/types.rst:320 msgid "" -"Currently not available, see `Issue 2769 `_" +"Another great way of communicating with another system may be Zammad's :doc:" +"`Webhooks `." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > State > Name" +#: ../system/objects/types.rst:323 +msgid "" +"After filling a link-template enabled field, an URL icon will appear on its " +"right. Clicking on the icon opens a new tab." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.state.name}``" +#: ../system/objects/types.rst:328 +msgid "" +"Even though Zammad displays the link template within object edit and create " +"screens, the function is optional. It's only active if you populate the " +"field." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``new``, ``open``, ..." +#: ../system/objects/types.rst:333 +msgid "" +"What's the difference between URL and text fields with link template...?!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Priority > Name" +#: ../system/objects/types.rst:335 +msgid "" +"Both fields have different use cases. Use ``text`` type text fields when " +"ever you have a *static* url that requires dynamic parameters. If you " +"require a drag & drop like field that you can put in any URL, use ``URL`` " +"type text fields." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.priority.name}``" +#: ../system/objects/types.rst:340 +msgid "" +"The difference is easier to spot when comparing the fields directly, below " +"screencast shows the result - the dynamic approach uses existing values in " +"the moment of updating to built the URL - e.g. ``https://google.com/search?" +"q=cookies`` - while the URL approach uses the actual URL of the field - e.g. " +"``https://zammad.com``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2 normal``" +#: ../system/objects/types.rst:None +msgid "" +"Screencast showing the differents in between URL and text type fields with " +"actual values" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Pending till" +#: ../system/objects/types.rst:352 +msgid "How does this work...?!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.pending_time}``" +#: ../system/objects/types.rst:354 +msgid "" +"As an example, let's say you have an attribute called ``amazing_attribute`` " +"and you want to open a google search directly with the input from that field." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not set" +#: ../system/objects/types.rst:357 +msgid "" +"Providing the link-template field below allows you to do so: ``https://www." +"google.com/search?q=#{ticket.amazing_attribute}``" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Web" +#: ../system/objects/types.rst:362 +msgid "" +"You can use any :doc:`Zammad variable ` as long as it's " +"available in the moment you need it." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.web}``" +#: ../system/objects/types.rst:365 +msgid "" +"As a result, you are redirected to Google with a search for the value of the " +"attribute, if you click on the button in the ticket (as you can see in the " +"screencast above)." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``https://zammad.com`` or empty if not set" +#: ../system/packages.rst:2 +msgid "Packages" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > VIP" +#: ../system/packages.rst:4 +msgid "That's the package management-area." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.vip}``" +#: ../system/packages.rst:6 +msgid "Individual add-ons for Zammad can be installed and managed here." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Phone" +#: ../system/sessions.rst:2 +msgid "Sessions" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.phone}``" +#: ../system/sessions.rst:4 +msgid "" +"Sessions management allows reviewing currently known user sessions and " +"allows to end these. The session timeout is affected by :ref:" +"`security_session_timeout` configurations from security settings." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Note" +#: ../system/sessions.rst:None +msgid "Screenshot showing Zammad's session management" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.note}``" +#: ../system/sessions.rst:13 +msgid "Zammad will provide the following information:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Mobile" +#: ../system/sessions.rst:16 +msgid "" +"The user account this session entry belongs to. It can be normal if a user " +"has several sessions in the list. This can be due to changed browser " +"information or if you use e.g. single sign on methods where the user does " +"not use the log off button." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.mobile}``" +#: ../system/sessions.rst:22 +msgid "Browser" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Login" +#: ../system/sessions.rst:22 +msgid "The browser agent communicated to Zammad." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.login}``" +#: ../system/sessions.rst:40 +msgid "Location" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``agent``" -msgstr "``agente``" - -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Lastname" -msgstr "Ticket > Dueño > Apellido" - -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.lastname}``" -msgstr "``#{ticket.owner.lastname}``" - -#: ../system/variables/ticket.rst:1 -msgid "``Mustermann`` or empty if not set" -msgstr "``Caputo`` o vació si no esta configurado" - -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Firstname" -msgstr "Ticket > Dueño > Nombre" - -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.firstname}``" -msgstr "``#{ticket.owner.firstname}``" - -#: ../system/variables/ticket.rst:1 -msgid "``Max`` or empty if not set" -msgstr "``Federico`` o vació si no esta configurado" - -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Fax" -msgstr "Ticket > Dueño > Fax" - -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.fax}``" -msgstr "``#{ticket.owner.fax}``" - -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Email" -msgstr "Ticket > Dueño > Correo electrónico" - -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.email}``" -msgstr "``#{ticket.owner.email}``" - -#: ../system/variables/ticket.rst:1 -msgid "``agent@company.tld`` or empty if not set" -msgstr "``agent@company.tld`` o vació si no esta configurado" - -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Department" -msgstr "Ticket > Dueño > Departamento" - -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.department}``" -msgstr "``#{ticket.owner.department}``" - -#: ../system/variables/ticket.rst:1 -msgid "``Support`` or empty if not set" -msgstr "``Soporte`` o vació si no esta configurado" - -#: ../system/variables/ticket.rst:1 -#, fuzzy -msgid "Ticket > Owner > Avatar" -msgstr "Ticket > Dueño > Fax" - -#: ../system/variables/ticket.rst:1 -#, fuzzy -msgid "``#{ticket.owner.avatar(60,60)}``" -msgstr "``#{ticket.owner.lastname}``" +#: ../system/sessions.rst:25 +msgid "" +"The anticipated location based on the users IP address. Depending on the IP " +"address the result shown may differ. This option depends on :doc:`/settings/" +"system/services`." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Address" -msgstr "Ticket > Dueño > Dirección" +#: ../system/sessions.rst:29 +msgid "The following information can be shown:" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.address}``" -msgstr "``#{ticket.owner.address}``" +#: ../system/sessions.rst:33 +msgid "IP address" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Shared organization" -msgstr "Ticket > Organización > Organización compartida" +#: ../system/sessions.rst:32 +msgid "" +"Either if you set *Geo IP services* to inactive or you're using internal IP " +"address which do not provide location information." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.shared}``" -msgstr "``#{ticket.organization.shared}``" +#: ../system/sessions.rst:40 +msgid "Country (or Country + City)" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Note" -msgstr "Ticket > Organización > Nota" +#: ../system/sessions.rst:36 +msgid "" +"If *Geo IP services* is enabled only. Depends on how detailed the available " +"IP address information are." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.note}``" -msgstr "``#{ticket.organization.note}``" +#: ../system/sessions.rst:39 +msgid "" +"Be aware that results can be inaccurate - this technically is not an error." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Name" -msgstr "Ticket > Organización > Nombre" +#: ../system/sessions.rst:43 +msgid "Age" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.name}``" -msgstr "``#{ticket.organization.name}``" +#: ../system/sessions.rst:43 +msgid "Provides the time when the session initially has been created." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Zammad GmbH`` or empty if not set" +#: ../system/sessions.rst:50 +msgid "Update" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Domain based assignment" -msgstr "Ticket > Organización > Asignación basada en dominio" +#: ../system/sessions.rst:46 +msgid "" +"Provides the time the user used this session to open Zammad. This timestamp " +"is only updated if the user e.g. reloads, not during normal work on tickets." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.domain_assignment}``" -msgstr "``#{ticket.organization.domain_assignment}``" +#: ../system/sessions.rst:50 +msgid "This timestamp is being used for the session timeout." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Domain" -msgstr "Ticket > Organización > Dominio" +#: ../system/sessions.rst:53 +msgid "" +"Use the delete button to remove a single session on behalf of your user." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.domain}``" -msgstr "``#{ticket.organization.domain}``" +#: ../system/subscription.rst:2 +msgid "Subscription (SaaS)" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``domain.tld`` or empty if not set" -msgstr "``domain.tld`` o vació si no esta configurado" +#: ../system/subscription.rst:4 +msgid "" +"The subscription settings page allows you to configure your instances " +"package and number of agents required." +msgstr "" -#: ../system/variables/ticket.rst:1 -#, fuzzy -msgid "Ticket > Organization > VIP" -msgstr "Ticket > Organización > Nota" +#: ../system/subscription.rst:9 +msgid "" +"This setting section is only available for Hosted setups. If you're looking " +"for on premise support contracts, please see the `Zammad pricing page " +"`_." +msgstr "" -#: ../system/variables/ticket.rst:1 -#, fuzzy -msgid "``#{ticket.organization.vip}``" -msgstr "``#{ticket.organization.domain}``" +#: ../system/subscription.rst:14 ../system/subscription.rst:34 +msgid "Plan" +msgstr "" -#: ../system/variables/ticket.rst:1 -#, fuzzy -msgid "Ticket > Number" -msgstr "Ticket > #" +#: ../system/subscription.rst:16 +msgid "" +"Here you can set up everything affecting your instance subscription " +"functions like number of agents and package." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.number}``" -msgstr "``#{ticket.number}``" +#: ../system/subscription.rst:19 +msgid "" +"On top of the page you can find a subscription summary. You'll find the " +"number of used and available (booked) agent seats there. By using the *see " +"more* link you can also expand an agent list to see the currently configured " +"active agents. This list *does not* count accounts with admin permissions " +"only." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``31001``, ``201910731001``, ..." -msgstr "``31001``, ``201910731001``, ..." +#: ../system/subscription.rst:None +msgid "" +"Within subscription you can always see how many agents are still\n" +"available to add and who uses the seats." +msgstr "" -#: ../system/variables/ticket.rst:1 -#, fuzzy -msgid "Ticket > ID" -msgstr "Ticket > #" +#: ../system/subscription.rst:29 +msgid "" +"Learn more on how to manage your agents in general :doc:`here `." +msgstr "" -#: ../system/variables/ticket.rst:1 -#, fuzzy -msgid "``#{ticket.id}``" -msgstr "``#{ticket.number}``" +#: ../system/subscription.rst:36 +msgid "" +"This section gives you an overview of the available plans and their " +"functions / limits. If you require a more detailed table, check our " +"`detailed pricing table `_ for more." +msgstr "" -#: ../system/variables/ticket.rst:1 -#, fuzzy -msgid "``17``, ``5281``, ..." -msgstr "``31001``, ``201910731001``, ..." +#: ../system/subscription.rst:40 +msgid "" +"Your selection in this step will decide on the base agent price and e.g. " +"agent limits that might apply in the summary step." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact (customer)" -msgstr "Ticket > Ultimo contacto (cliente)" +#: ../system/subscription.rst:43 +msgid "" +"The green *Selected* button will also tell you what plan you're currently in." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_customer_at}``" -msgstr "``#{ticket.last_contact_customer_at}``" +#: ../system/subscription.rst:47 +msgid "" +"Trial instances are running at Professional with 3 agents. The plan cannot " +"be changed during the trial for technical reasons, if you require more " +"agents for testing, please contact `our sales team `_ with a reason for the raise request." +msgstr "" -#: ../system/variables/ticket.rst:1 -#, fuzzy +#: ../system/subscription.rst:None msgid "" -"``2019-10-07 16:25:00 UTC`` or empty if not applicable yet (Please note " -"`Ticket last contact behavior Settings `_ for this)" +"Screenshot showing three available packages for a hosted Zammad\n" +"instance" msgstr "" -"``2019-10-07 16:25:00 UTC`` o vació si no es aplicable todavía (Por favor " -"vea `Configuración de ultimo contacto de Ticket `_)" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact" -msgstr "Ticket > Ultimo contacto" +#: ../system/subscription.rst:57 +msgid "" +"At the bottom of this block you can find a summary where you can adjust the " +"settings of the previous selected plan." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_at}``" -msgstr "``#{ticket.last_contact_at}``" +#: ../system/subscription.rst:62 +msgid "" +"Note that upgrading (more agents, higher package) is always possible, " +"however, downgrading will only happen when your billing period renews." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact (agent)" -msgstr "Ticket > Ultimo contacto (agente)" +#: ../system/subscription.rst:66 +msgid "" +"Upgrading resets your billing period and existing credit will be deducted " +"from the new total." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_agent_at}``" -msgstr "``#{ticket.last_contact_agent_at}``" +#: ../system/subscription.rst:75 +msgid "Billing cycle" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable yet" -msgstr "``2019-10-07 16:25:00 UTC`` o vació si no aplica todavía" +#: ../system/subscription.rst:70 +msgid "" +"You can choose between either monthly or yearly billing. The price per agent " +"will be cheaper if you decide for yearly billing." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Note" -msgstr "Ticket > Grupo > Nota" +#: ../system/subscription.rst:73 +msgid "" +"If you're still trying out things and are unsure of the right package for " +"your instance, you may want to choose monthly first and then upgrade to " +"yearly when you're sure." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.note}``" -msgstr "``#{ticket.group.note}``" +#: ../system/subscription.rst:83 +msgid "Plan: (Starter|Professional|Plus) - Agents" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Note about this group``" -msgstr "``Nota sobre este grupo``" +#: ../system/subscription.rst:78 +msgid "Choose the number of agents you require for your instance." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Name" -msgstr "Ticket > Grupo > Nombre" +#: ../system/subscription.rst:80 +msgid "" +"Keep in mind that some packages may have agent limits. Depending on the " +"previous chosen package, you won't be able to exceed specific agent numbers. " +"Also note that setting less agents than currently configured is not possible." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.name}``" -msgstr "``#{ticket.group.name}``" +#: ../system/subscription.rst:86 +msgid "Total" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Sales``" -msgstr "``Ventas``" +#: ../system/subscription.rst:86 +msgid "This will be the net total you're going to be billed." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Follow-up possible" -msgstr "Ticket > Grupo > Seguimiento posible" +#: ../system/subscription.rst:88 +msgid "" +"By using the *Update subscription* button, the instance package will be " +"adjusted immediately. If you didn't provide a payment method yet, Zammad " +"will request you to provide one at this point." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.follow_up_possible}``" -msgstr "``#{ticket.group.follow_up_possible}``" +#: ../system/subscription.rst:94 +msgid "" +"In case you're still within the trial period, this means that the trial will " +"be over immediately!" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``no`` or ``yes``" -msgstr "``no`` o ``si``" +#: ../system/subscription.rst:97 +msgid "Down- or upgrading during the trial period *is not* possible." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Assign Follow-Ups" -msgstr "Ticket > Grupo > Asignar Seguimiento" +#: ../system/subscription.rst:None +msgid "Screenshot showing payment options and a pricing summary" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.follow_up_assignment}``" -msgstr "``#{ticket.group.follow_up_assignment}``" +#: ../system/subscription.rst:103 +msgid "Billing Information" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Assignment Timeout" -msgstr "Ticket > Grupo > Tiempo de espera de asignación" +#: ../system/subscription.rst:105 +msgid "" +"You can control all billing relevant information like invoices, billing " +"address and the option to cancel your subscription." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.assignment_timeout}``" -msgstr "``#{ticket.group.assignment_timeout}``" +#: ../system/subscription.rst:108 +msgid "" +"All adjusted billing information below only affect future invoices. If your " +"invoice was issued wrong, please contact `our sales team `_." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``20`` or empty if not configured" -msgstr "``20`` o vació si no esta configurado" +#: ../system/subscription.rst:114 +msgid "Billing address" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > First response" -msgstr "Ticket > Primera respuesta" +#: ../system/subscription.rst:113 +msgid "" +"Provide your company address here, make sure to include the companies name " +"in case required. This address will be referenced on your invoice." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.first_response_at}``" -msgstr "``#{ticket.first_response_at}``" +#: ../system/subscription.rst:118 +msgid "VAT ID" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Escalation at" -msgstr "Ticket > Escalación en" +#: ../system/subscription.rst:117 +msgid "" +"Provide your VAT ID here. If applicable your invoice will not contain German " +"VAT. Please make sure to pay the VAT in your country as required." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.escalation_at}``" -msgstr "``#{ticket.escalation_at}``" +#: ../system/subscription.rst:127 +msgid "Billing Email Address" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable" -msgstr "``2019-10-07 16:25:00 UTC`` o vació si no aplica" +#: ../system/subscription.rst:121 +msgid "" +"Usually the instance owner (the person that registered the instance) will " +"receive all emails including the invoices. In case you have your own billing " +"department, you can provide their email address here." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Web" -msgstr "Ticket > Cliente > Web" +#: ../system/subscription.rst:125 +msgid "" +"All billing relevant information will then be sent to this email address." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.web}``" -msgstr "``#{ticket.customer.web}``" +#: ../system/subscription.rst:127 +msgid "Invoices are sent as attachment (PDF) to this email address." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > VIP" -msgstr "Ticket > Cliente > Persona Muy Importante" +#: ../system/subscription.rst:129 +msgid "" +"Don't forget to press the *Update billing information* button after you " +"changed above settings." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.vip}``" -msgstr "``#{ticket.customer.vip}``" +#: ../system/subscription.rst:None +msgid "" +"Screenshot showing options for billing information within the\n" +"subscription menu" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Phone" -msgstr "Ticket > Cliente > Teléfono" +#: ../system/subscription.rst:137 +msgid "Payment Method" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.phone}``" -msgstr "``#{ticket.customer.phone}``" +#: ../system/subscription.rst:139 +msgid "You can pay via credit card or SEPA mandate." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Note" -msgstr "Ticket > Cliente > Nota" +#: ../system/subscription.rst:144 +msgid "Credit card" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.note}``" -msgstr "``#{ticket.customer.note}``" +#: ../system/subscription.rst:142 +msgid "" +"Simply follow the dialogue by clicking *authorize credit card* and confirm -" +"if required by your bank- your consent to Zammad using your card for the " +"payments." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Mobile" -msgstr "Ticket > Cliente > Celular" +#: ../system/subscription.rst:148 +msgid "SEPA Direct Debit" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.mobile}``" -msgstr "``#{ticket.customer.mobile}``" +#: ../system/subscription.rst:147 +msgid "" +"Provide the requested information of the bank account holder and update if " +"you're ready. You'll then receive an email with the SEPA mandate." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Login" -msgstr "Ticket > Cliente > Acceso" +#: ../system/subscription.rst:150 +msgid "" +"Technically there's also the possibility to pay via invoice, however - this " +"method only applies to a fairly low number of instances. Please contact `our " +"sales team `_ for more information." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.login}``" -msgstr "``#{ticket.customer.login}``" +#: ../system/subscription.rst:156 +#, fuzzy +#| msgid "Description" +msgid "Cancel Subscription" +msgstr "Descripción" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Lastname" -msgstr "Ticket > Cliente > Apellido" +#: ../system/subscription.rst:158 +msgid "" +"Do you want to cancel your subscription? In case you no longer want to use " +"Zammad's SaaS, you can cancel your subscription by using the red *Yes, " +"please cancel my subscription* button." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.lastname}``" -msgstr "``#{ticket.customer.lastname}``" +#: ../system/subscription.rst:162 +msgid "" +"To cancel the description, enter the FQDN of your Zammad instance and " +"provide a reason for your cancellation." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Firstname" -msgstr "Ticket > Cliente > Nombre" +#: ../system/subscription.rst:165 +msgid "" +"Your subscription will end the day after your trial or billing period ends." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.firstname}``" -msgstr "``#{ticket.customer.firstname}``" +#: ../system/subscription.rst:None +#, fuzzy +msgid "Screenshot showing subscription cancellation dialog" +msgstr "" +"Captura de pantalla que muestra la configuración básica de una cuenta de " +"correo electrónico entrante" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Fax" -msgstr "Ticket > Cliente> Fax" +#: ../system/subscription.rst:174 +msgid "" +"We will remind you about your cancelled subscription several times up front. " +"After the subscription ended all instance data will be removed. A restore " +"*is not* possible after that point!" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.fax}``" -msgstr "``#{ticket.customer.fax}``" +#: ../system/subscription.rst:178 +msgid "**😖 Cancelled by accident?**" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Email" -msgstr "Ticket > Cliente > Correo Electrónico" +#: ../system/subscription.rst:180 +msgid "" +"You can always undo the cancellation via the *Yes, undo the cancellation of " +"my subscription* button up to the last subscription day!" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.email}``" -msgstr "``#{ticket.customer.email}``" +#: ../system/subscription.rst:0 +msgid "" +"Screenshot showing a red button to cancel the subscription\n" +"cancellation" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Department" -msgstr "Ticket > Cliente > Departamento" +#: ../system/subscription.rst:189 +msgid "Payment History" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.department}``" -msgstr "``#{ticket.customer.department}``" +#: ../system/subscription.rst:191 +msgid "" +"The payment history will display a history of all paid invoices. At this " +"point you can also download these in case you need them again." +msgstr "" -#: ../system/variables/ticket.rst:1 -#, fuzzy -msgid "Ticket > Customer > Avatar" -msgstr "Ticket > Cliente> Fax" +#: ../system/subscription.rst:196 +msgid "" +"You will only find *paid* invoices here. Invoices that are to be billed are " +"not available before the payment is completed." +msgstr "" -#: ../system/variables/ticket.rst:1 -#, fuzzy -msgid "``#{ticket.customer.avatar(60,60)}``" -msgstr "``#{ticket.customer.lastname}``" +#: ../system/subscription.rst:201 +msgid "Date" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Address" -msgstr "Ticket > Cliente > Dirección" +#: ../system/subscription.rst:201 +msgid "Date of the invoice creation." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.address}``" -msgstr "``#{ticket.customer.address}``" +#: ../system/subscription.rst:204 +msgid "Amount" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Web" -msgstr "Ticket > Creado por > Web" +#: ../system/subscription.rst:204 +msgid "Invoice total including VAT if applicable." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.web}``" -msgstr "``#{ticket.created_by.web}``" +#: ../system/subscription.rst:207 +msgid "" +"Contains contract period (monthly or yearly) and hosted plan for the " +"subscription period in question." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > VIP" -msgstr "Ticket > Creado por > Persona Muy Importante" +#: ../system/subscription.rst:218 +msgid "Payment method / Service period" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.vip}``" -msgstr "``#{ticket.created_by.vip}``" +#: ../system/subscription.rst:211 +msgid "" +"Used bank account or credit card as well as the subscription period the " +"invoice is about." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Phone" -msgstr "Ticket > Creado por > Teléfono" +#: ../system/subscription.rst:216 +msgid "" +"It might happen that the invoice date and subscription period differ. This " +"is nothing to worry about, the subscription periods will be accounted later " +"on." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.phone}``" -msgstr "``#{ticket.created_by.phone}``" +#: ../system/subscription.rst:222 +msgid "Receipt" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Note" -msgstr "Ticket > Creado por > Nota" +#: ../system/subscription.rst:221 +msgid "" +"Use the arrow to download the invoice in question. You can download all " +"available invoices any time you need to here!" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.note}``" -msgstr "``#{ticket.created_by.note}``" +#: ../system/subscription.rst:None +msgid "Screenshot showing payment history of a hosted instance" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Mobile" -msgstr "Ticket > Creado por > Celular" +#: ../system/subscription.rst:229 +msgid "FAQ" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.mobile}``" -msgstr "``#{ticket.created_by.mobile}``" +#: ../system/subscription.rst:233 +msgid "I set up a trial account but am missing functions to test" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Login" -msgstr "Ticket > Creado por > Acceso" +#: ../system/subscription.rst:232 +msgid "" +"The trial instance is running within the professional package allowing up to " +"three agents." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.login}``" -msgstr "``#{ticket.created_by.login}``" +#: ../system/subscription.rst:236 +msgid "Can I change package within the trial?" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Lastname" -msgstr "Ticket > Creado por > Apellido" +#: ../system/subscription.rst:236 +msgid "No. As soon as the package is changed the subscription begins." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.lastname}``" -msgstr "``#{ticket.created_by.lastname}``" +#: ../system/subscription.rst:241 +msgid "What happens to my trial instance after the trial period ended?" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Firstname" -msgstr "Ticket > Creado por > Nombre" +#: ../system/subscription.rst:239 +msgid "" +"Your instance will automatically be canceled for you. Please see *What " +"happens to my instance after it has been canceled?* for more." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.firstname}``" -msgstr "``#{ticket.created_by.firstname}``" +#: ../system/subscription.rst:254 +msgid "What happens to my instance after it has been canceled?" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Fax" -msgstr "Ticket > Creado por > Fax" +#: ../system/subscription.rst:244 +msgid "That depends slightly on your instance state:" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.fax}``" -msgstr "``#{ticket.created_by.fax}``" +#: ../system/subscription.rst:250 +msgid "Trial instance" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Email" -msgstr "Ticket > Creado por > Correo Electrónico" +#: ../system/subscription.rst:247 +msgid "" +"If you're still on trial, we will ice your instance and remind you once " +"again about your instance. We then will wait some days and remove your " +"instance from our system. This is the last time we will inform you by Email." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.email}``" -msgstr "``#{ticket.created_by.email}``" +#: ../system/subscription.rst:254 +msgid "Paid instance" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Department" -msgstr "Ticket > Creado por > Departamento" +#: ../system/subscription.rst:253 +msgid "" +"If you're a paying customer and canceled your subscription, the instance " +"removal will take place the day after your last subscription day." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.department}``" -msgstr "``#{ticket.created_by.department}``" +#: ../system/subscription.rst:256 +msgid "Can removed instances be restored?" +msgstr "" -#: ../system/variables/ticket.rst:1 -#, fuzzy -msgid "Ticket > Created by > Avatar" -msgstr "Ticket > Creado por > Fax" +#: ../system/subscription.rst:257 +msgid "No. Once your instance has been removed, a restoration is not possible." +msgstr "" -#: ../system/variables/ticket.rst:1 -#, fuzzy -msgid "``#{ticket.created_by.avatar(60,60)}``" -msgstr "``#{ticket.created_by.lastname}``" +#: ../system/system-report.rst:2 +msgid "System Report" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Address" -msgstr "Ticket > Creado por > Dirección" +#: ../system/system-report.rst:4 +msgid "" +"In this place you can't configure Zammad. Instead you can obtain a system " +"report about Zammad and its configuration." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.address}``" -msgstr "``#{ticket.created_by.address}``" +#: ../system/system-report.rst:7 +msgid "" +"See the description in Zammad for an explanation. You can even find a " +"preview of the included data below the **Download** button." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created at" -msgstr "Ticket > Creado en" +#: ../system/system-report.rst:10 +msgid "" +"Zammad never sends this automatically to anyone. It is a manual process only " +"to provide better support based on your configuration." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_at}``" -msgstr "``#{ticket.created_at}``" +#: ../system/translations.rst:2 +msgid "Translations" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "2019-10-07 16:25:00 UTC" -msgstr "2019-10-07 16:25:00 UTC" +#: ../system/translations.rst:4 +msgid "" +"Translations of Zammad are processed centrally in our `Weblate instance " +"`_. This allows non-developers to review " +"and update translation texts of the language they actually speak." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Closing time" -msgstr "Ticket > Tiempo de cierre" +#: ../system/translations.rst:9 +msgid "" +"Your language is in an incomplete translation state or has typos? Please " +"consider helping us in sorting this out! All you need is either a GitHub " +"account or to register directly in our instance." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.close_at}``" -msgstr "``#{ticket.close_at}``" +#: ../system/translations.rst:13 +msgid "" +"Did you know? This is also where the documentation translations are handled. " +"🤓" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "2019-10-07 17:25:00 UTC" -msgstr "2019-10-07 17:25:00 UTC" +#: ../system/translations.rst:15 +msgid "" +"Have a look in our :docs:`contribution section ` in the system documentation to get started!" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``3``, any number of articles existing in the ticket right now" +#: ../system/translations.rst:20 +msgid "Local Translations" msgstr "" -"``3``, cualquier número de artículos existiendo en el ticket ahora mismo" -#: ../system/version.rst:2 -msgid "Version" -msgstr "Versión" +#: ../system/translations.rst:22 +msgid "" +"Apart from these system translations, there's still local translations you " +"can manage. This is relevant if you added custom objects that require " +"translations or even custom states and priorities." +msgstr "" -#: ../system/version.rst:4 -msgid "Shows which version is currently being used on your Zammad-instance." +#: ../system/translations.rst:None +msgid "Translation management screen within the admin menu" msgstr "" -"Muestra cual versión esta siendo actualmente usada en tu instancia de Zammad." -#: ../manage/roles/admin-permissions.rst:53 -msgid "``admin.checklist``" +#: ../system/translations.rst:31 +msgid "Updating Translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:54 -msgid ":doc:`Manage > Checklist `" +#: ../system/translations.rst:33 +msgid "" +"Because of how Zammad ships translations, the only way to update the system " +"translations is to update your Zammad installation. The benefit of this is " +"that you no longer need internet access during a Zammad upgrade as the " +"package has everything it requires already." msgstr "" -#: ../manage/roles/admin-permissions.rst:83 -msgid "``admin.channel_whatsapp``" +#: ../system/translations.rst:39 +msgid "Translation of Custom Objects" msgstr "" -#: ../manage/roles/admin-permissions.rst:84 -msgid ":doc:`Channels > Whatsapp `" +#: ../system/translations.rst:41 +msgid "" +"No problem at all! You can customize any translation locally, even if it is " +"not initially provided by the system." msgstr "" -#: ../manage/roles/admin-permissions.rst:124 -msgid "``admin.public_links``" +#: ../system/translations.rst:44 +msgid "" +"Translation is supported for a broad number of features, including but not " +"limited to custom:" msgstr "" -#: ../manage/roles/admin-permissions.rst:125 -msgid ":doc:`Manage > Public Links `" +#: ../system/translations.rst:47 +msgid "Object Attributes" msgstr "" -#: ../manage/roles/admin-permissions.rst:151 -msgid "``admin.system_report``" +#: ../system/translations.rst:48 +#, fuzzy +msgid "Ticket Macros" +msgstr "Macros" + +#: ../system/translations.rst:49 +#, fuzzy +msgid "Ticket Overviews" +msgstr "Ticket > Dueño > Dirección" + +#: ../system/translations.rst:50 +#, fuzzy +msgid "Ticket Priorities" +msgstr "prioridad" + +#: ../system/translations.rst:51 +#, fuzzy +msgid "Ticket States" +msgstr "Ticket > Creado en" + +#: ../system/translations.rst:54 +msgid "Customizing Translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:152 -msgid ":doc:`System > System Report `" +#: ../system/translations.rst:56 +msgid "" +"Within the translation screen, simply click on the **New Translation** " +"button." msgstr "" -#: ../manage/roles/admin-permissions.rst:166 +#: ../system/translations.rst:None #, fuzzy -msgid "``admin.ticket_auto_assignment``" -msgstr "``#{ticket.group.follow_up_assignment}``" +msgid "New translation dialog" +msgstr "Diálogo: Nueva cuenta de correo electrónico" -#: ../manage/roles/admin-permissions.rst:167 -msgid ":ref:`Settings > Ticket > Auto Assignment `" +#: ../system/translations.rst:62 +msgid "" +"In the dialog you can immediately enter the exact translation source (if you " +"know it) and your custom translation text for it and click **Submit**." msgstr "" -#: ../manage/roles/admin-permissions.rst:169 -msgid "``admin.ticket_duplicate_detection``" +#: ../system/translations.rst:65 +msgid "" +"Alternatively, try to search for translation suggestions in the list below. " +"Selecting an item from the list will pre-fill the translation source for you " +"and then you can just enter your custom translation." msgstr "" -#: ../manage/roles/admin-permissions.rst:170 -msgid ":ref:`Settings > Ticket > Duplicate Detection `" +#: ../system/translations.rst:69 +msgid "" +"The target language will always default to your current language selection. " +"If you need to translate for a different language, simply change the " +"selection before submitting." msgstr "" -#: ../manage/roles/admin-permissions.rst:172 -#, fuzzy -msgid "``admin.ticket_priority``" -msgstr "prioridad" +#: ../system/translations.rst:73 +msgid "" +"All your custom translations will show up in the overview table when added. " +"And they will even persist across Zammad updates!" +msgstr "" -#: ../manage/roles/admin-permissions.rst:173 -msgid ":ref:`System > Objects >Ticket Priority `" +#: ../system/translations.rst:76 +msgid "" +"Make sure to reload your browser if a translated string is not displayed." msgstr "" -#: ../manage/roles/admin-permissions.rst:175 -#, fuzzy -msgid "``admin.ticket_state``" -msgstr "Ticket > Creado en" +#: ../system/translations.rst:80 +msgid "Reverting to Original Translations" +msgstr "" -#: ../manage/roles/admin-permissions.rst:176 -msgid ":ref:`System > Objects >Ticket State `" +#: ../system/translations.rst:82 +msgid "" +"If you want to revert a custom translation to original text, simply use the " +"appropriate action within the row of the overview table." msgstr "" -#: ../manage/roles/admin-permissions.rst:193 -msgid "``admin.webhook``" +#: ../system/translations.rst:85 +msgid "" +"Depending on the type of the translation source, the action has a slightly " +"different name:" msgstr "" -#: ../manage/roles/admin-permissions.rst:194 -msgid ":doc:`Manage > Webhook `" +#: ../system/translations.rst:88 +msgid "**Reset** for customized system translations" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:43 -msgid "``user_preferences.appearance``" +#: ../system/translations.rst:89 +msgid "**Remove** for customized local translations" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:44 -msgid "Appearance configuration" +#: ../system/translations.rst:91 +msgid "" +"In both cases, the action will remove the customized translation after a " +"confirmation." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:0 -msgid "Users can switch between dark, light and" +#: ../system/translations.rst:None +msgid "Screenshot showing the location of the Remove action" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:0 -msgid "automatic mode." +#: ../system/translations.rst:99 +msgid "Inline Translations" msgstr "" -#: ../system/system-report.rst:2 -msgid "System Report" +#: ../system/translations.rst:101 +msgid "" +"If you prefer a more hands-on approach, you can activate the inline or on-" +"screen translation feature by pressing ``ctrl`` + ``alt`` + ``t`` at any " +"time and on any screen." msgstr "" -#: ../system/system-report.rst:4 +#: ../system/translations.rst:105 msgid "" -"In this place you can't configure Zammad. Instead you can obtain a system " -"report about Zammad and its configuration." +"All customizable translation texts will be highlighted for you on the " +"screen. Just click into the highlighted area and update the text in place." msgstr "" -#: ../system/system-report.rst:7 +#: ../system/translations.rst:None +msgid "Inline translation mode activated for the Overview screen" +msgstr "" + +#: ../system/translations.rst:112 msgid "" -"See the description in Zammad for an explanation. You can even find a " -"preview of the included data below the **Download** button." +"When finished editing, simply press ``ctrl`` + ``alt`` + ``t`` again to " +"deactivate." msgstr "" -#: ../system/system-report.rst:10 +#: ../system/translations.rst:117 msgid "" -"Zammad never sends this automatically to anyone. It is a manual process only " -"to provide better support based on your configuration." +"Even though it's available on any screen, the inline translation feature " +"requires admin permissions. It works only for the current language " +"selection. If you need to translate a different language, first change the " +"language in your :user-docs:`profile settings `." +msgstr "" + +#: ../system/version.rst:2 +msgid "Version" +msgstr "Versión" + +#: ../system/version.rst:4 +msgid "Shows which version is currently being used on your Zammad-instance." msgstr "" +"Muestra cual versión esta siendo actualmente usada en tu instancia de Zammad." #, fuzzy #~ msgid "" diff --git a/locale/es_CO/LC_MESSAGES/admin-docs.po b/locale/es_CO/LC_MESSAGES/admin-docs.po index 11e65ea0..3658d6d1 100644 --- a/locale/es_CO/LC_MESSAGES/admin-docs.po +++ b/locale/es_CO/LC_MESSAGES/admin-docs.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Zammad\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-11-06 10:31+0100\n" +"POT-Creation-Date: 2024-11-12 16:31+0100\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -1040,12 +1040,12 @@ msgstr "" #: ../manage/roles/agent-permissions.rst:31 #: ../manage/roles/user-preferences-permissions.rst:37 #: ../manage/scheduler.rst:108 ../manage/webhook/add.rst:116 +#: ../misc/variables.rst:101 #: ../system/integrations/cti/includes/inbound-calls.include.rst:15 #: ../system/integrations/cti/includes/outbound-calls.include.rst:18 #: ../system/integrations/cti/includes/inbound-calls.include.rst:14 #: ../system/integrations/cti/includes/outbound-calls.include.rst:17 -#: ../system/objects.rst:162 ../system/objects.rst:244 -#: ../system/variables.rst:101 ../system/objects.rst:246 +#: ../system/objects.rst:162 ../system/objects.rst:246 msgid "Note" msgstr "" @@ -2257,7 +2257,7 @@ msgstr "" #: ../channels/email/signatures.rst:22 msgid "" "To individualize the signatures, it is possible to automatically load " -"specific information into a signature via :doc:`/system/variables`. All " +"specific information into a signature via :doc:`/misc/variables`. All " "information stored on the ticket, assigned customers or agents can be " "inserted. This makes it possible to design the signature individually. To " "load a list of available variables, enter two colons (``::``) into the " @@ -2550,7 +2550,7 @@ msgstr "" #: ../channels/form.rst:19 ../manage/groups/settings.rst:14 #: ../manage/scheduler.rst:39 ../manage/slas/how-do-they-work.rst:26 #: ../manage/templates.rst:33 ../system/objects.rst:130 -#: ../system/objects.rst:232 ../system/objects.rst:234 +#: ../system/objects.rst:234 msgid "Name" msgstr "" @@ -2579,7 +2579,7 @@ msgstr "" #: ../manage/macros/how-do-they-work.rst:0 ../manage/overviews.rst:0 #: ../manage/scheduler.rst:111 ../manage/templates.rst:43 #: ../manage/webhook/add.rst:123 ../system/objects.rst:169 -#: ../system/objects.rst:246 ../system/objects.rst:248 +#: ../system/objects.rst:248 msgid "Active" msgstr "" @@ -2921,10 +2921,9 @@ msgid "Default value" msgstr "" #: ../channels/form.rst:219 ../manage/public-links.rst:47 -#: ../misc/object-conditions/basics.rst:64 +#: ../misc/object-conditions/basics.rst:64 ../misc/variables.rst:100 #: ../system/core-workflows/condition-operators.rst:21 -#: ../system/objects/permissions.rst:39 ../system/subscription/billing.rst:53 -#: ../system/variables.rst:100 +#: ../system/objects/permissions.rst:39 ../system/subscription.rst:208 msgid "Description" msgstr "" @@ -5908,7 +5907,7 @@ msgstr "" msgid "System" msgstr "" -#: ../index.rst:87 ../index.rst:88 +#: ../index.rst:87 msgid "Misc" msgstr "" @@ -7142,7 +7141,7 @@ msgstr "" #: ../manage/macros/how-do-they-work.rst:28 msgid "" "Unlike triggers, the scheduler, and text modules, macro actions do **not** " -"support the use of :doc:`/system/variables`." +"support the use of :doc:`/misc/variables`." msgstr "" #: ../manage/macros/how-do-they-work.rst:32 @@ -8370,165 +8369,149 @@ msgid "Accessing chat for agents: ``chat.agent``" msgstr "" #: ../manage/roles/admin-permissions.rst:53 +msgid "``admin.checklist``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:54 +msgid ":doc:`Manage > Checklist `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:56 msgid "``admin.channel_email``" msgstr "" -#: ../manage/roles/admin-permissions.rst:54 #: ../manage/roles/admin-permissions.rst:57 msgid ":doc:`Channels > Email `" msgstr "" -#: ../manage/roles/admin-permissions.rst:56 #: ../manage/roles/admin-permissions.rst:59 msgid "``admin.channel_facebook``" msgstr "" -#: ../manage/roles/admin-permissions.rst:57 #: ../manage/roles/admin-permissions.rst:60 msgid ":doc:`Channels > Facebook `" msgstr "" -#: ../manage/roles/admin-permissions.rst:58 #: ../manage/roles/admin-permissions.rst:61 msgid "" "Accessing Facebook tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:59 #: ../manage/roles/admin-permissions.rst:62 msgid "``admin.channel_formular``" msgstr "" -#: ../manage/roles/admin-permissions.rst:60 #: ../manage/roles/admin-permissions.rst:63 msgid ":doc:`Channels > Form `" msgstr "" -#: ../manage/roles/admin-permissions.rst:62 #: ../manage/roles/admin-permissions.rst:65 msgid "``admin.channel_google``" msgstr "" -#: ../manage/roles/admin-permissions.rst:63 #: ../manage/roles/admin-permissions.rst:66 msgid ":doc:`Channels > Google `" msgstr "" -#: ../manage/roles/admin-permissions.rst:65 #: ../manage/roles/admin-permissions.rst:68 msgid "``admin.channel_microsoft365``" msgstr "" -#: ../manage/roles/admin-permissions.rst:66 #: ../manage/roles/admin-permissions.rst:69 msgid ":doc:`Channels > Microsoft 365 `" msgstr "" -#: ../manage/roles/admin-permissions.rst:68 #: ../manage/roles/admin-permissions.rst:71 msgid "``admin.channel_sms``" msgstr "" -#: ../manage/roles/admin-permissions.rst:69 #: ../manage/roles/admin-permissions.rst:72 msgid ":doc:`Channels > SMS `" msgstr "" -#: ../manage/roles/admin-permissions.rst:71 #: ../manage/roles/admin-permissions.rst:74 msgid "``admin.channel_telegram``" msgstr "" -#: ../manage/roles/admin-permissions.rst:72 #: ../manage/roles/admin-permissions.rst:75 msgid ":doc:`Channels > Telegram `" msgstr "" -#: ../manage/roles/admin-permissions.rst:73 #: ../manage/roles/admin-permissions.rst:76 msgid "" "Accessing Telegram tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:74 #: ../manage/roles/admin-permissions.rst:77 msgid "``admin.channel_twitter``" msgstr "" -#: ../manage/roles/admin-permissions.rst:75 #: ../manage/roles/admin-permissions.rst:78 msgid ":doc:`Channels > Twitter `" msgstr "" -#: ../manage/roles/admin-permissions.rst:76 #: ../manage/roles/admin-permissions.rst:79 msgid "" "Accessing Twitter/X tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:77 #: ../manage/roles/admin-permissions.rst:80 msgid "``admin.channel_web``" msgstr "" -#: ../manage/roles/admin-permissions.rst:78 #: ../manage/roles/admin-permissions.rst:81 msgid ":doc:`Channels > Web `" msgstr "" -#: ../manage/roles/admin-permissions.rst:80 +#: ../manage/roles/admin-permissions.rst:83 +msgid "``admin.channel_whatsapp``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:84 +msgid ":doc:`Channels > Whatsapp `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:86 msgid "``admin.core_workflows``" msgstr "" -#: ../manage/roles/admin-permissions.rst:81 #: ../manage/roles/admin-permissions.rst:87 msgid ":doc:`System > Core Workflows `" msgstr "" -#: ../manage/roles/admin-permissions.rst:83 #: ../manage/roles/admin-permissions.rst:89 msgid "``admin.data_privacy``" msgstr "" -#: ../manage/roles/admin-permissions.rst:84 #: ../manage/roles/admin-permissions.rst:90 msgid ":doc:`System > Data Privacy `" msgstr "" -#: ../manage/roles/admin-permissions.rst:85 #: ../manage/roles/admin-permissions.rst:91 msgid "" "🔥 Be careful, it allows users to permanently delete data on the system." msgstr "" -#: ../manage/roles/admin-permissions.rst:86 #: ../manage/roles/admin-permissions.rst:92 msgid "``admin.group``" msgstr "" -#: ../manage/roles/admin-permissions.rst:87 #: ../manage/roles/admin-permissions.rst:93 msgid ":doc:`Manage > Groups `" msgstr "" -#: ../manage/roles/admin-permissions.rst:89 #: ../manage/roles/admin-permissions.rst:95 msgid "``admin.integration``" msgstr "" -#: ../manage/roles/admin-permissions.rst:90 #: ../manage/roles/admin-permissions.rst:96 msgid ":doc:`System > Integrations `" msgstr "" -#: ../manage/roles/admin-permissions.rst:92 #: ../manage/roles/admin-permissions.rst:98 msgid "``admin.knowledge_base``" msgstr "" -#: ../manage/roles/admin-permissions.rst:93 #: ../manage/roles/admin-permissions.rst:99 msgid ":doc:`Manage > Knowledge Base `" msgstr "" @@ -8548,57 +8531,46 @@ msgid "" "knowledge-base.html#editing-answers>`." msgstr "" -#: ../manage/roles/admin-permissions.rst:98 #: ../manage/roles/admin-permissions.rst:104 msgid "``admin.macro``" msgstr "" -#: ../manage/roles/admin-permissions.rst:99 #: ../manage/roles/admin-permissions.rst:105 msgid ":doc:`Manage > Macros `" msgstr "" -#: ../manage/roles/admin-permissions.rst:100 #: ../manage/roles/admin-permissions.rst:106 msgid "In some cases, macros may also require ``admin.tag``" msgstr "" -#: ../manage/roles/admin-permissions.rst:101 #: ../manage/roles/admin-permissions.rst:107 msgid "``admin.maintenance``" msgstr "" -#: ../manage/roles/admin-permissions.rst:102 #: ../manage/roles/admin-permissions.rst:108 msgid ":doc:`System > Maintenance `" msgstr "" -#: ../manage/roles/admin-permissions.rst:104 #: ../manage/roles/admin-permissions.rst:110 msgid "``admin.monitoring``" msgstr "" -#: ../manage/roles/admin-permissions.rst:105 #: ../manage/roles/admin-permissions.rst:111 msgid ":doc:`System > Monitoring `" msgstr "" -#: ../manage/roles/admin-permissions.rst:107 #: ../manage/roles/admin-permissions.rst:113 msgid "``admin.object``" msgstr "" -#: ../manage/roles/admin-permissions.rst:108 #: ../manage/roles/admin-permissions.rst:114 msgid ":doc:`System > Objects `" msgstr "" -#: ../manage/roles/admin-permissions.rst:110 #: ../manage/roles/admin-permissions.rst:116 msgid "``admin.organization``" msgstr "" -#: ../manage/roles/admin-permissions.rst:111 #: ../manage/roles/admin-permissions.rst:117 msgid ":doc:`Manage > Organizations `" msgstr "" @@ -8615,202 +8587,210 @@ msgstr "" msgid "They can even edit an organization's name, domain, and notes!" msgstr "" -#: ../manage/roles/admin-permissions.rst:115 #: ../manage/roles/admin-permissions.rst:121 msgid "``admin.overview``" msgstr "" -#: ../manage/roles/admin-permissions.rst:116 #: ../manage/roles/admin-permissions.rst:122 msgid ":doc:`Manage > Overviews`" msgstr "" -#: ../manage/roles/admin-permissions.rst:118 +#: ../manage/roles/admin-permissions.rst:124 +msgid "``admin.public_links``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:125 +msgid ":doc:`Manage > Public Links `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:127 msgid "``admin.package``" msgstr "" -#: ../manage/roles/admin-permissions.rst:119 #: ../manage/roles/admin-permissions.rst:128 msgid ":doc:`System > Packages `" msgstr "" -#: ../manage/roles/admin-permissions.rst:121 #: ../manage/roles/admin-permissions.rst:130 msgid "``admin.report_profile``" msgstr "" -#: ../manage/roles/admin-permissions.rst:122 #: ../manage/roles/admin-permissions.rst:131 msgid ":doc:`Manage > Report Profiles `" msgstr "" -#: ../manage/roles/admin-permissions.rst:123 #: ../manage/roles/admin-permissions.rst:132 msgid "Access to view reports: ``report``" msgstr "" -#: ../manage/roles/admin-permissions.rst:124 #: ../manage/roles/admin-permissions.rst:133 msgid "``admin.role``" msgstr "" -#: ../manage/roles/admin-permissions.rst:125 #: ../manage/roles/admin-permissions.rst:134 msgid ":doc:`Manage > Roles `" msgstr "" -#: ../manage/roles/admin-permissions.rst:127 #: ../manage/roles/admin-permissions.rst:136 msgid "``admin.scheduler``" msgstr "" -#: ../manage/roles/admin-permissions.rst:128 #: ../manage/roles/admin-permissions.rst:137 msgid ":doc:`Manage > Scheduler `" msgstr "" -#: ../manage/roles/admin-permissions.rst:129 #: ../manage/roles/admin-permissions.rst:138 msgid "For automation on tickets" msgstr "" -#: ../manage/roles/admin-permissions.rst:130 #: ../manage/roles/admin-permissions.rst:139 msgid "``admin.security``" msgstr "" -#: ../manage/roles/admin-permissions.rst:131 #: ../manage/roles/admin-permissions.rst:140 msgid ":doc:`Settings > Security `" msgstr "" -#: ../manage/roles/admin-permissions.rst:132 #: ../manage/roles/admin-permissions.rst:141 msgid "Settings of Zammad. This also covers third party authentications." msgstr "" -#: ../manage/roles/admin-permissions.rst:133 #: ../manage/roles/admin-permissions.rst:142 msgid "``admin.session``" msgstr "" -#: ../manage/roles/admin-permissions.rst:134 #: ../manage/roles/admin-permissions.rst:143 msgid ":doc:`System > Sessions `" msgstr "" -#: ../manage/roles/admin-permissions.rst:136 #: ../manage/roles/admin-permissions.rst:145 msgid "``admin.setting_system``" msgstr "" -#: ../manage/roles/admin-permissions.rst:137 #: ../manage/roles/admin-permissions.rst:146 msgid ":doc:`Settings > System `" msgstr "" -#: ../manage/roles/admin-permissions.rst:139 #: ../manage/roles/admin-permissions.rst:148 msgid "``admin.sla``" msgstr "" -#: ../manage/roles/admin-permissions.rst:140 #: ../manage/roles/admin-permissions.rst:149 msgid ":doc:`Manage > SLAs `" msgstr "" -#: ../manage/roles/admin-permissions.rst:142 +#: ../manage/roles/admin-permissions.rst:151 +msgid "``admin.system_report``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:152 +msgid ":doc:`System > System Report `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:154 msgid "``admin.tag``" msgstr "" -#: ../manage/roles/admin-permissions.rst:143 #: ../manage/roles/admin-permissions.rst:155 msgid ":doc:`Manage > Tags `" msgstr "" -#: ../manage/roles/admin-permissions.rst:145 #: ../manage/roles/admin-permissions.rst:157 msgid "``admin.template``" msgstr "" -#: ../manage/roles/admin-permissions.rst:146 #: ../manage/roles/admin-permissions.rst:158 msgid ":doc:`Manage > Templates `" msgstr "" -#: ../manage/roles/admin-permissions.rst:148 #: ../manage/roles/admin-permissions.rst:160 msgid "``admin.text_module``" msgstr "" -#: ../manage/roles/admin-permissions.rst:149 #: ../manage/roles/admin-permissions.rst:161 msgid ":doc:`Manage > Text Modules `" msgstr "" -#: ../manage/roles/admin-permissions.rst:151 #: ../manage/roles/admin-permissions.rst:163 msgid "``admin.ticket``" msgstr "" -#: ../manage/roles/admin-permissions.rst:152 #: ../manage/roles/admin-permissions.rst:164 msgid ":doc:`Settings > Tickets `" msgstr "" -#: ../manage/roles/admin-permissions.rst:153 #: ../manage/roles/admin-permissions.rst:165 msgid "Does not grant access to :doc:`/misc/composer`" msgstr "" -#: ../manage/roles/admin-permissions.rst:154 +#: ../manage/roles/admin-permissions.rst:166 +msgid "``admin.ticket_auto_assignment``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:167 +msgid ":ref:`Settings > Ticket > Auto Assignment `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:169 +msgid "``admin.ticket_duplicate_detection``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:170 +msgid ":ref:`Settings > Ticket > Duplicate Detection `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:172 +msgid "``admin.ticket_priority``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:173 +msgid ":ref:`System > Objects >Ticket Priority `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:175 +msgid "``admin.ticket_state``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:176 +msgid ":ref:`System > Objects >Ticket State `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:178 msgid "``admin.time_accounting``" msgstr "" -#: ../manage/roles/admin-permissions.rst:155 #: ../manage/roles/admin-permissions.rst:179 msgid ":doc:`Manage > Time Accounting `" msgstr "" -#: ../manage/roles/admin-permissions.rst:156 #: ../manage/roles/admin-permissions.rst:180 msgid "Also allows the export of timekeeping records." msgstr "" -#: ../manage/roles/admin-permissions.rst:157 #: ../manage/roles/admin-permissions.rst:181 msgid "``admin.translation``" msgstr "" -#: ../manage/roles/admin-permissions.rst:158 #: ../manage/roles/admin-permissions.rst:182 msgid ":doc:`System > Translations `" msgstr "" -#: ../manage/roles/admin-permissions.rst:159 #: ../manage/roles/admin-permissions.rst:183 msgid "Also enables inline translation" msgstr "" -#: ../manage/roles/admin-permissions.rst:160 #: ../manage/roles/admin-permissions.rst:184 msgid "``admin.trigger``" msgstr "" -#: ../manage/roles/admin-permissions.rst:161 #: ../manage/roles/admin-permissions.rst:185 msgid ":doc:`Manage > Triggers `" msgstr "" -#: ../manage/roles/admin-permissions.rst:163 #: ../manage/roles/admin-permissions.rst:187 msgid "``admin.user``" msgstr "" -#: ../manage/roles/admin-permissions.rst:164 #: ../manage/roles/admin-permissions.rst:188 msgid ":doc:`Manage > Users `" msgstr "" @@ -8829,6 +8809,14 @@ msgid "" "from-users-perspective>` ." msgstr "" +#: ../manage/roles/admin-permissions.rst:193 +msgid "``admin.webhook``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:194 +msgid ":doc:`Manage > Webhook `" +msgstr "" + #: ../manage/roles/agent-permissions.rst:2 msgid "Agent Permissions" msgstr "" @@ -9247,36 +9235,45 @@ msgid "than the user that generated them." msgstr "" #: ../manage/roles/user-preferences-permissions.rst:43 +msgid "``user_preferences.appearance``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:44 +msgid "Appearance configuration" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "Users can switch between dark, light and" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "automatic mode." +msgstr "" + #: ../manage/roles/user-preferences-permissions.rst:47 msgid "``user_preferences.avatar``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:44 #: ../manage/roles/user-preferences-permissions.rst:48 msgid "Avatar settings" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:45 #: ../manage/roles/user-preferences-permissions.rst:49 msgid "Override the default Gravatar with a custom avatar" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:46 #: ../manage/roles/user-preferences-permissions.rst:50 msgid "``user_preferences.calendar``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:47 #: ../manage/roles/user-preferences-permissions.rst:51 msgid "Configure the calendar feed" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:49 #: ../manage/roles/user-preferences-permissions.rst:53 msgid "``user_preferences.device``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:50 #: ../manage/roles/user-preferences-permissions.rst:54 msgid "Manage device login sessions" msgstr "" @@ -9293,22 +9290,18 @@ msgstr "" msgid "To learn more, see :doc:`/manage/trigger/system-notifications`." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:54 #: ../manage/roles/user-preferences-permissions.rst:58 msgid "``user_preferences.language``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:55 #: ../manage/roles/user-preferences-permissions.rst:59 msgid "Configure the UI locale/language" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:57 #: ../manage/roles/user-preferences-permissions.rst:61 msgid "``user_preferences.linked_accounts``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:58 #: ../manage/roles/user-preferences-permissions.rst:62 msgid "Account linking" msgstr "" @@ -9332,7 +9325,6 @@ msgstr "" msgid "is the only way users can utilize third-party logins." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:63 #: ../manage/roles/user-preferences-permissions.rst:67 msgid "``user_preferences.notifications``" msgstr "" @@ -9359,7 +9351,6 @@ msgstr "" msgid "Customers can't receive ticket notifications at all." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:69 #: ../manage/roles/user-preferences-permissions.rst:73 msgid "``user_preferences.out_of_office``" msgstr "" @@ -9384,7 +9375,6 @@ msgstr "" msgid "they're replacing." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:75 #: ../manage/roles/user-preferences-permissions.rst:79 msgid "``user_preferences.overview_sorting``" msgstr "" @@ -9413,12 +9403,10 @@ msgstr "" msgid "overviews has no effect on custom orders." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:82 #: ../manage/roles/user-preferences-permissions.rst:86 msgid "``user_preferences.password``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:83 #: ../manage/roles/user-preferences-permissions.rst:87 msgid "Change account password" msgstr "" @@ -9435,7 +9423,6 @@ msgstr "" msgid "your only allowed authentication method." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:87 #: ../manage/roles/user-preferences-permissions.rst:91 msgid "``user_preferences.two_factor_authentication``" msgstr "" @@ -9472,7 +9459,7 @@ msgstr "" #: ../manage/scheduler.rst:19 msgid "" -"Schedulers can be used to send periodic reminder emails. Use :doc:`/system/" +"Schedulers can be used to send periodic reminder emails. Use :doc:`/misc/" "variables` to build highly-customized email templates." msgstr "" @@ -10468,7 +10455,7 @@ msgstr "" #: ../manage/text-modules.rst:57 msgid "" -"The example text modules below use :doc:`/system/variables` to dynamically " +"The example text modules below use :doc:`/misc/variables` to dynamically " "insert information like the customer's or agent's names." msgstr "" @@ -10808,8 +10795,8 @@ msgstr "" #: ../misc/object-conditions/basics.rst:144 #: ../misc/object-conditions/basics.rst:160 #: ../misc/object-conditions/basics.rst:168 -#: ../misc/object-conditions/basics.rst:178 ../settings/ticket.rst:2 -#: ../system/variables/ticket.rst:2 +#: ../misc/object-conditions/basics.rst:178 ../misc/variables/ticket.rst:2 +#: ../settings/ticket.rst:2 msgid "Ticket" msgstr "" @@ -11043,7 +11030,7 @@ msgstr "" #: ../manage/trigger/how-do-they-work.rst:79 msgid "" -"Certain actions (such as *email*, *SMS* and *notes*) support :doc:`/system/" +"Certain actions (such as *email*, *SMS* and *notes*) support :doc:`/misc/" "variables`, which can be used to build highly-customized message templates." msgstr "" @@ -11072,7 +11059,7 @@ msgstr "" msgid "" "You can also combine static text with placeholders for text fields. Remember " "that the placeholders' values have to be known during trigger runtime. Learn " -"more about :doc:`/system/variables`." +"more about :doc:`/misc/variables`." msgstr "" #: ../manage/trigger/how-do-they-work.rst:105 @@ -12037,7 +12024,7 @@ msgstr "" msgid "" "When switched on, a code editor will be shown below, where you can configure " "custom payload for your webhook in JSON format. To insert supported :doc:`/" -"system/variables` use ``::`` or ``#{`` shortcuts for autocomplete." +"misc/variables` use ``::`` or ``#{`` shortcuts for autocomplete." msgstr "" #: ../manage/webhook/add.rst:103 @@ -14614,11942 +14601,11833 @@ msgid "" "powerful conditions with AND/OR relations." msgstr "" -#: ../settings/branding.rst:10 -msgid "Product Name" +#: ../misc/variables.rst:2 +msgid "Variables" msgstr "" -#: ../settings/branding.rst:7 +#: ../misc/variables.rst:4 msgid "" -"Defines the name of the application, shown in the web interface, tabs and " -"title bar of the web browser." +"Please note that this is just an overview of available variables. It might " +"be incomplete or variables might not be available within some functions. If " +"you're missing variables or are not sure if something is not working as " +"expected, feel free to ask over at the `Community `_." msgstr "" -#: ../settings/branding.rst:10 -msgid "Default value: ``Zammad Helpdesk``" +#: ../misc/variables.rst:10 +msgid "" +"Variables can be called by typing ``::`` (just like text modules in the " +"frontend), as long as you're in a supported text field within the backend. " +"Zammad will display all variables being available within this context and " +"replace it to the variable as soon as you selected an entry." msgstr "" -#: ../settings/branding.rst:13 -msgid "Will be shown in the app and is included in email footers." +#: ../misc/variables.rst:15 +msgid "" +"You have an empty field which you referenced and it appears as ``-``? That's " +"currently working as designed - you might want to ensure that these fields " +"always have a value." msgstr "" -#: ../settings/branding.rst:19 -msgid "Logo" +#: ../misc/variables.rst:20 +msgid "Variable Categories" msgstr "" -#: ../settings/branding.rst:16 -msgid "Defines the logo of the application, shown in the login page of Zammad." +#: ../misc/variables.rst:31 +msgid "Wait, What About Custom Objects?" msgstr "" -#: ../settings/branding.rst:18 +#: ../misc/variables.rst:33 msgid "" -"Ensure to hit the \"Submit\" button after uploading the logo. Otherwise your " -"change will not be saved." +"Good point! Of course, we can't predict what objects you might create, but " +"we can give you a hint on how to put the puzzle together to get your custom " +"values." msgstr "" -#: ../settings/branding.rst:22 +#: ../misc/variables.rst:36 msgid "" -"Allows to set the default language of the Zammad instance. The here defined " -"locale mostly acts as a fallback for:" -msgstr "" - -#: ../settings/branding.rst:25 -msgid "user preferences (if Zammad can't detect the users locale)" +"For this, we'll talk about the inner part of the variable (so everything " +"within ``#{}``), please put the outer part around to have a valid variable. " +"The first part of the variable name consist of the object type. Currently " +"these are:" msgstr "" -#: ../settings/branding.rst:26 -msgid "CSV output (reporting, time accounting)" +#: ../misc/variables.rst:41 +msgid "Ticket (``ticket``)" msgstr "" -#: ../settings/branding.rst:30 -msgid "Define the timezone of your Zammad installation." +#: ../misc/variables.rst:42 +msgid "User (``user``)" msgstr "" -#: ../settings/branding.rst:32 -msgid "" -"This does not have any effect on timings for your agents or how Zammad " -"stores date and time values." +#: ../misc/variables.rst:43 +msgid "Organization (``organization``)" msgstr "" -#: ../settings/branding.rst:35 -msgid "Changing this value has direct consequences on the following areas:" +#: ../misc/variables.rst:44 +msgid "Group (``group``)" msgstr "" -#: ../settings/branding.rst:37 -msgid ":doc:`/manage/scheduler` tasks" +#: ../misc/variables.rst:46 +msgid "" +"The second part is the name of the attribute. This is the name you define " +"during object creation and can be found within the object attribute menu at " +"any time. The first and second part of a variable is divided by a point, e." +"g.: ``ticket.number`` which will in total be ``#{ticket.number}``." msgstr "" -#: ../settings/branding.rst:38 -msgid "search indexing (and thus reporting)" +#: ../misc/variables.rst:51 +msgid "" +"Now, in some situations it's possible that you'll need to use a third part. " +"The best example for such a situation would be a ``select`` or ``tree-" +"select`` field which will by default return the key value, not it's display " +"name. For this, just extend your variable with ``.value``. This will result " +"in ``#{ticket.select.value}``." msgstr "" -#: ../settings/branding.rst:40 -msgid "calendar subscriptions" +#: ../misc/variables.rst:60 +msgid "Using Translated Variables" msgstr "" -#: ../settings/branding.rst:41 -msgid "browser printing" +#: ../misc/variables.rst:62 +msgid "" +"If you want to use a translated variable in triggers or schedulers, you can " +"extend the placeholder like this: ``#{t(ticket.state.name)}``. The ``t`` " +"tells Zammad to search for fitting translated strings. The used output " +"language is based on the system language of Zammad which you can set in the " +"admin panel under :doc:`/settings/branding` or based on the selected locale " +"in the trigger/scheduler edit dialog." msgstr "" -#: ../settings/branding.rst:43 +#: ../misc/variables.rst:69 msgid "" -"Please note that some of above are fallbacks in case Zammad could not detect " -"the agents timezone correctly." +"A possible use-case: you want to send your customers updates on tickets via " +"trigger or scheduler which should include the state of the ticket. Using the " +"default ``#{ticket.state.name}`` (without the translation flag ``t()``) " +"would lead to the output of the original (english) name of the state." msgstr "" -#: ../settings/branding.rst:77 -msgid "Pretty Date" +#: ../misc/variables.rst:75 +msgid "Date and Time Formatting" msgstr "" -#: ../settings/branding.rst:47 +#: ../misc/variables.rst:77 msgid "" -"This setting allows you to define how Zammad should display time stamps " -"within the interface to all users." +"The system (trigger/scheduler selected) locale and timezone predefines a " +"default format of date and timestamp. This format is customizable by using " +"the ``dt()`` method." msgstr "" -#: ../settings/branding.rst:50 -msgid "" -"This does not have any effect on how Zammad returns e.g. time values via " -"variables." +#: ../misc/variables.rst:79 +msgid "The method arguments are as follows:" msgstr "" -#: ../settings/branding.rst:77 -msgid "Choose in between the following options:" +#: ../misc/variables.rst:81 +msgid "The date or timestamp variable you want to format." msgstr "" -#: ../settings/branding.rst:64 -msgid "relative" +#: ../misc/variables.rst:82 +msgid "The output format string." msgstr "" -#: ../settings/branding.rst:55 +#: ../misc/variables.rst:83 +msgid "The timezone to apply (optional)." +msgstr "" + +#: ../misc/variables.rst:85 +#: ../system/objects/external-data-source-example.rst:23 +msgid "**Example:**" +msgstr "" + +#: ../misc/variables.rst:86 msgid "" -"This timestamp shows a relative time span until it switches to a date. Over " -"time, it will change as follows:" +"``#{dt(ticket.updated_at, \"%A %Y-%m-%d %H:%M in the office\", \"Europe/" +"Berlin\")}``" msgstr "" -#: ../settings/branding.rst:58 -msgid "just now" +#: ../misc/variables.rst:87 +msgid "Monday, 2024-03-18 15:31 in the office" msgstr "" -#: ../settings/branding.rst:59 -msgid "5 minutes ago" +#: ../misc/variables.rst:89 +msgid "" +"If you want to use our example, make sure to paste the string above without " +"formatting (``CTRL+Shift+v``), otherwise it won't work." msgstr "" -#: ../settings/branding.rst:60 -msgid "3 days 1 hour ago" +#: ../misc/variables.rst:93 +msgid "The following table lists available format directives:" msgstr "" -#: ../settings/branding.rst:61 -msgid "``03/04/2022``" +#: ../misc/variables.rst:99 +msgid "Parameter" msgstr "" -#: ../settings/branding.rst:63 -msgid "Hovering the timestamp helps, you'll always get a clean timestamp then." +#: ../misc/variables.rst:102 +msgid "``%Y``" msgstr "" -#: ../settings/branding.rst:71 -msgid "absolute" +#: ../misc/variables.rst:103 +msgid "Year with 4 digits" msgstr "" -#: ../settings/branding.rst:67 -msgid "" -"This timestamp always includes the week day. For one week after creation, " -"the timestamp will not contain the date itself: Thursday 18:35." +#: ../misc/variables.rst:104 +msgid "Use ``%y`` for year with 2 digits" msgstr "" -#: ../settings/branding.rst:71 -msgid "After a week it will switch to: ``Friday 4. Mar 16:00``." +#: ../misc/variables.rst:105 +msgid "``%m``" msgstr "" -#: ../settings/branding.rst:76 -msgid "timestamp" +#: ../misc/variables.rst:106 +msgid "Month of year (as number with zero-padding)" msgstr "" -#: ../settings/branding.rst:74 -msgid "" -"This will cause Zammad to show a complete timestamp according to your locale " -"defaults. For English this could be e.g. ``2022/12/03 2:40 pm`` or for " -"German e.g. ``12.03.2022 14:40``." +#: ../misc/variables.rst:107 +msgid "Use ``%-m`` for month without zero-padding" msgstr "" -#: ../settings/branding.rst:78 -msgid "Default setting: ``relative``." +#: ../misc/variables.rst:108 +msgid "``%d``" msgstr "" -#: ../settings/security.rst:2 -msgid "Security" +#: ../misc/variables.rst:109 +msgid "Day of month (as number with zero-padding)" msgstr "" -#: ../settings/security.rst:4 -msgid "" -"For your overview we split each tab within security settings into its own " -"page:" +#: ../misc/variables.rst:110 +msgid "Use ``%e`` for day without zero-padding" msgstr "" -#: ../settings/security/base.rst:2 ../settings/system/base.rst:2 -#: ../settings/ticket.rst:8 -msgid "Base" +#: ../misc/variables.rst:111 +msgid "``%H``" msgstr "" -#: ../settings/security/base.rst:5 -msgid "New User Accounts" +#: ../misc/variables.rst:112 +msgid "Hour of day in 24h notation with zero-padding" msgstr "" -#: ../settings/security/base.rst:9 -msgid "" -"Activates the `register as a new customer` function on the login page. If " -"set to ``no`` only administrators or agents can create new accounts manually." +#: ../misc/variables.rst:113 +msgid "Use ``%k`` for hour without zero-padding" msgstr "" -#: ../settings/security/base.rst:13 ../settings/security/base.rst:38 -#: ../settings/security/base.rst:66 -msgid "Default setting: ``yes``" +#: ../misc/variables.rst:114 +msgid "``%I``" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing activated \"New User Accounts\" setting" +#: ../misc/variables.rst:115 +msgid "Hour of day in 12h notation with zero-padding" msgstr "" -#: ../settings/security/base.rst:22 +#: ../misc/variables.rst:116 msgid "" -"Deactivation of above function **does not** deactivate automatic account " -"creation! This means: If a user writes e.g. an email to Zammad and has no " -"account yet, Zammad will automatically create the account. User accounts are " -"a direct dependency of tickets and thus technically mandatory." +"Use ``%l`` for hour without zero-padding and ``%p`` / ``%P`` for meridian " +"indicator" msgstr "" -#: ../settings/security/base.rst:29 -msgid "Lost Password" +#: ../misc/variables.rst:117 +msgid "``%M``" msgstr "" -#: ../settings/security/base.rst:33 -msgid "" -"Activates the `lost password` function on the login page. If set to ``no`` " -"only administrators may change the user's password - users may update their " -"own password if they're still logged in and they have the required :doc:" -"`permission `." +#: ../misc/variables.rst:118 +msgid "Minute of hour" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing activated \"Lost Password\" setting" +#: ../misc/variables.rst:120 +msgid "``%S``" msgstr "" -#: ../settings/security/base.rst:49 -msgid "" -"With third party authentications - but especially LDAP - you may want to " -"disable this function. Zammad **will not** change third party login " -"passwords and instead set or change the local password!" +#: ../misc/variables.rst:121 +msgid "Second of Minute" msgstr "" -#: ../settings/security/base.rst:56 -msgid "Password Login" +#: ../misc/variables.rst:123 +msgid "``%A``" msgstr "" -#: ../settings/security/base.rst:60 -msgid "" -"Activates the username & password login by default and if no third-party " -"login is activated. Disabling password login on the Zammad login page only " -"takes effect if you enable any :doc:`third-party`." +#: ../misc/variables.rst:124 +msgid "Weekday name" msgstr "" -#: ../settings/security/base.rst:64 -msgid "See :doc:`third-party` for supported third-party logins." +#: ../misc/variables.rst:125 +msgid "Use ``%a`` for abbreviated name or ``%^A`` for uppercase name" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing de-activated \"Password Login\" setting" +#: ../misc/variables.rst:126 +msgid "``%B``" msgstr "" -#: ../settings/security/base.rst:77 -msgid "" -"To help administrators to overcome \"login issues\", Zammad automatically " -"offers a password request for administrator users. This allows you to adjust " -"Third-Party applications even if the login does no longer work!" +#: ../misc/variables.rst:127 +msgid "Month name" msgstr "" -#: ../settings/security/base.rst:84 -msgid "Session Timeout" +#: ../misc/variables.rst:128 +msgid "Use ``%b`` for abbreviated name" msgstr "" -#: ../settings/security/base.rst:86 -msgid "" -"All settings below by default are set to ``4 weeks``. Session Timeout " -"defines the life time of a users session. As soon as it's reached, Zammad " -"will automatically log off the session in question." +#: ../misc/variables.rst:129 +msgid "``%U``" msgstr "" -#: ../settings/security/base.rst:91 -msgid "" -"Zammad takes the highest value set assigned for the user based on the " -"permissions." +#: ../misc/variables.rst:130 +msgid "Week number of current year" msgstr "" -#: ../settings/security/base.rst:94 -msgid "``admin``" +#: ../misc/variables.rst:131 +msgid "Use ``%W`` for a different calculation method" msgstr "" -#: ../settings/security/base.rst:96 -msgid "``ticket.customer``" +#: ../misc/variables.rst:134 +msgid "" +"We support the known format directives for the Ruby built-in method " +"``strftime`` of the ``DateTime`` class. For more information, see `here " +"`_." msgstr "" -#: ../settings/security/base.rst:97 -msgid "``default`` (fallback if user doesn't have above permissions set)" +#: ../misc/variables/article.rst:2 +msgid "Articles" msgstr "" -#: ../settings/security/base.rst:99 +#: ../misc/variables/article.rst:4 ../misc/variables/config.rst:4 +#: ../misc/variables/current-user.rst:4 ../misc/variables/ticket.rst:4 msgid "" -"All settings act independently from each other allowing you to disable the " -"timeouts for e.g. admins, but not agents." +"If you're missing variables or are not sure if something is not working as " +"expected, feel free to ask over at the `Community `_." msgstr "" -#: ../settings/security/base.rst:115 -#: ../system/integrations/checkmk/api-reference.rst:13 -msgid "Example" +#: ../misc/variables/article.rst:6 +msgid "" +"Below you can find all available ticket article-based variables within " +"Zammad. These can be called via triggers for example. If you're unsure if " +"Zammad does support variables at the point you're at, you can try to type " +"``::`` to check." msgstr "" -#: ../settings/security/base.rst:107 -msgid "Let's suppose you configured the following session timeouts" +#: ../misc/variables/article.rst:9 ../misc/variables/config.rst:9 +#: ../misc/variables/ticket.rst:9 +msgid "" +"The below list gives you an example what kind of data you can expect, it's " +"not intended to explain the data itself." msgstr "" -#: ../settings/security/base.rst:104 -msgid "default: 3 weeks" +#: ../misc/variables/article.rst:11 +msgid "Article Variables" msgstr "" -#: ../settings/security/base.rst:105 -msgid "admin: 2 weeks" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "name" msgstr "" -#: ../settings/security/base.rst:106 -msgid "ticket.agent: 4 weeks" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "variable" msgstr "" -#: ../settings/security/base.rst:107 -msgid "ticket.customer: 1 week" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "example" msgstr "" -#: ../settings/security/base.rst:115 -msgid "This results in the following situations" +#: ../misc/variables/article.rst:1 +msgid "Article > Cc" msgstr "" -#: ../settings/security/base.rst:110 -msgid "a user with ``admin`` permission will have a timeout of 2 weeks" +#: ../misc/variables/article.rst:1 +msgid "``#{article.cc}``" msgstr "" -#: ../settings/security/base.rst:111 -msgid "" -"a user with ``admin`` and ``ticket.agent`` permissions will have a timeout " -"of 2 weeks" +#: ../misc/variables/article.rst:1 +msgid "``jdoe@example.com, company@example.com``" msgstr "" -#: ../settings/security/base.rst:113 -msgid "" -"a user with ``ticket.customer`` permission will have a timeout of 1 week" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Address" msgstr "" -#: ../settings/security/base.rst:115 -msgid "" -"a user with neither ``admin``, ``ticket.agent`` nor ``ticket.customer`` " -"permissions will have a timeout of 3 weeks" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.address}``" msgstr "" -#: ../settings/security/password.rst:4 -msgid "" -"This section allows you to define password requirements for the local user " -"accounts." +#: ../misc/variables/article.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:9 -msgid "" -"Zammad does **not** allow you to change your LDAP password, instead, it will " -"set a password in its local database which might confuse your users. This " -"might be addressed in the future by `#1169 `_." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Department" msgstr "" -#: ../settings/security/password.rst:14 -msgid "**Exception for admins**" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.department}``" msgstr "" -#: ../settings/security/password.rst:16 -msgid "" -"Please note that below password policies *do not* affect administrators " -"setting passwords on user accounts. While this seems strange and not safe we " -"believe that an administrator knowing an user's password is insecure as well." +#: ../misc/variables/article.rst:1 +msgid "``Sales`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:21 -msgid "The suggested workflow is either:" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Email" msgstr "" -#: ../settings/security/password.rst:23 -msgid "" -"to use third party logins to not require local passwords at all **- or -**" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.email}``" msgstr "" -#: ../settings/security/password.rst:25 -msgid "to require your *user to reset the password* upon first login." +#: ../misc/variables/article.rst:1 +msgid "``jdoe@example.com``" msgstr "" -#: ../settings/security/password.rst:27 -msgid "" -"This way administrators are not required to set a user's password at all!" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Fax" msgstr "" -#: ../settings/security/password.rst:31 -msgid "Maximum Failed Logins" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.fax}``" msgstr "" -#: ../settings/security/password.rst:33 -msgid "" -"You can choose a value between ``4`` and ``20``. This defines how often a " -"login to a user account may fail until Zammad will lock it. Your users can " -"always use the \"forgot password\" function to change their password and " -"unlock their account." -msgstr "" - -#: ../settings/security/password.rst:38 -msgid "The default value is ``10``." +#: ../misc/variables/article.rst:1 +msgid "``+4930123456789`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:42 -msgid "Beside changing the user's password, you can also unlock accounts via" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Firstname" msgstr "" -#: ../settings/security/password.rst:44 -msgid ":ref:`user management list `" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.firstname}``" msgstr "" -#: ../settings/security/password.rst:45 -msgid ":docs:`console `" +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Joe`` or empty if not set" msgstr "" -#: ../settings/security/password.rst:46 -msgid ":docs:`API `" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Lastname" msgstr "" -#: ../settings/security/password.rst:50 -msgid "Failed logins via LDAP no longer lock accounts." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.lastname}``" msgstr "" -#: ../settings/security/password.rst:53 -msgid "2 Lower Case And 2 Upper Case Characters" +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +#: ../misc/variables/ticket.rst:1 +msgid "``Doe`` or empty if not set" msgstr "" -#: ../settings/security/password.rst:55 -msgid "" -"You can add complexity to passwords by enforcing at least 2 upper and lower " -"case characters." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Login" msgstr "" -#: ../settings/security/password.rst:58 ../settings/security/password.rst:83 -msgid "The default value is ``no``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.login}``" msgstr "" -#: ../settings/security/password.rst:62 -msgid "Minimum Length" +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +#: ../misc/variables/ticket.rst:1 +msgid "``jdoe``" msgstr "" -#: ../settings/security/password.rst:64 -msgid "" -"This defines the minimum password length required for users to provide (from " -"``4`` to ``20``)." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Mobile" msgstr "" -#: ../settings/security/password.rst:67 -msgid "The default value is ``6``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.mobile}``" msgstr "" -#: ../settings/security/password.rst:71 -msgid "Digit Required" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Note" msgstr "" -#: ../settings/security/password.rst:73 -msgid "This enforces your users to use at least one digit within the password." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.note}``" msgstr "" -#: ../settings/security/password.rst:75 -msgid "The default value is ``yes``." +#: ../misc/variables/article.rst:1 +msgid "``Some note about user`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:78 -msgid "Special Character Required" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Phone" msgstr "" -#: ../settings/security/password.rst:80 -msgid "" -"This setting allows you to improve your password quality even more by " -"enforcing the password to contain at least one special character." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.phone}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:2 -msgid "SSL Certificates" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > VIP" msgstr "" -#: ../settings/security/ssl-certificates.rst:7 -msgid "" -"Zammad offers the possibility to upload custom certificates and custom " -"Certificate Authority (CA) certificates. This can be useful if you want to " -"connect Zammad the secure way to other systems which are using custom " -"certificates." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.vip}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:12 -msgid "" -"An example usecase might be: You have an internal LDAP server that is not " -"accessible from the internet, and you want a SSL-encrypted connection, using " -"a custom certificate." +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +msgid "``true`` or ``false``" msgstr "" -#: ../settings/security/ssl-certificates.rst:19 -msgid "" -"You should have an existing custom certificate file and/or a custom CA " -"certificate file, which you want to add to Zammad. As filetype ``.crt`` is " -"supported and the certificate format has to be PEM (Base64 ASCII)." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Web" msgstr "" -#: ../settings/security/ssl-certificates.rst:25 -msgid "" -"When you import a custom CA certificate, all certificates generated with " -"this are trusted. This can be useful if you have more than one system/" -"certificate you want to connect to and the certificates are issued from the " -"same custom CA." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.web}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:31 -msgid "Add a Certificate" +#: ../misc/variables/article.rst:1 +msgid "``https://zammad.com`` or empty if not set in user object" msgstr "" -#: ../settings/security/ssl-certificates.rst:33 -msgid "" -"To add a custom certificate or a custom CA certificate, head over to the " -"Admin panel > Settings > Security > SSL Certificates. Here you can find a " -"\"Add SSL Certificate\" button. In the dialog you can either select a " -"certificate file or paste the content of the certificate:" +#: ../misc/variables/article.rst:1 +msgid "Article > Created" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate adding dialog" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_at}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:43 -msgid "" -"After selecting a file or pasting the content of the certificate, click on " -"the \"Add\" button to finally upload it to Zammad. Then, the certificates " -"are immediately effective, no restart or similar required." +#: ../misc/variables/article.rst:1 +msgid "``2019-10-08 15:24:47 UTC``" msgstr "" -#: ../settings/security/ssl-certificates.rst:49 -msgid "" -"Please note that only single certificate files are supported. That means if " -"you want to import a certificate / CA certificate, it must contain **only " -"one** certificate." +#: ../misc/variables/article.rst:1 +msgid "Article > From" msgstr "" -#: ../settings/security/ssl-certificates.rst:54 -msgid "Certificate Overview" +#: ../misc/variables/article.rst:1 +msgid "``#{article.from}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:56 +#: ../misc/variables/article.rst:1 msgid "" -"After you added a certificate, you can see a table with information for each " -"added certificate:" +"``Joe Doe `` may differ, depends on ``FROM`` of send mail" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing table of added certificates" +#: ../misc/variables/article.rst:1 +msgid "Article > Sender > Name" msgstr "" -#: ../settings/security/ssl-certificates.rst:64 -msgid "" -"Here you can download the certificate or delete it, if you don't need it " -"anymore." +#: ../misc/variables/article.rst:1 +msgid "``#{article.sender.name}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:68 -msgid "Deleting Certificates" +#: ../misc/variables/article.rst:1 +msgid "``Customer``, ``Agent`` or ``System``" msgstr "" -#: ../settings/security/ssl-certificates.rst:70 -msgid "" -"If you want to delete a specific certificate, you can do it by clicking on " -"the menu in the actions column and selecting delete:" +#: ../misc/variables/article.rst:1 +msgid "Article > Subject" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate deletion button" +#: ../misc/variables/article.rst:1 +msgid "``#{article.subject}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:79 -msgid "Downloading Certificates" +#: ../misc/variables/article.rst:1 +msgid "``My amazing subject``" msgstr "" -#: ../settings/security/ssl-certificates.rst:81 -msgid "" -"If you want to download your certificates, you can do this as well via " -"corresponding action buttons." +#: ../misc/variables/article.rst:1 +msgid "Article > Text" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate download button" +#: ../misc/variables/article.rst:1 +msgid "``#{article.body}``" msgstr "" -#: ../settings/security/third-party.rst:13 -msgid "Login Providers" +#: ../misc/variables/article.rst:1 +msgid "``Test`` without formatting (plain)" msgstr "" -#: ../settings/security/third-party.rst:2 -msgid "Third-Party Applications" +#: ../misc/variables/article.rst:1 +msgid "Article > TicketID" msgstr "" -#: ../settings/security/third-party.rst:4 -msgid "" -"Third party authentication is a great way to help your users to login to " -"Zammad more easily. If the account is yet unknown, Zammad will create a new " -"user automatically, without the user needed to interact (e.g. type in his " -"name). Another big advantage of this feature is that your user doesn't need " -"to remember another password." +#: ../misc/variables/article.rst:1 +msgid "``#{article.ticket_id}``" msgstr "" -#: ../settings/security/third-party.rst:10 -msgid "" -"You can deactivate logging in via :ref:`security_password_login` if any of " -"the mentioned authentication providers are enabled in your instance." +#: ../misc/variables/article.rst:1 +msgid "``1`` (not ticket number)" msgstr "" -#: ../settings/security/third-party.rst:27 -msgid "" -"We're currently missing documentation for the following login providers:" +#: ../misc/variables/article.rst:1 +msgid "Article > To" msgstr "" -#: ../settings/security/third-party.rst:29 -msgid "LinkedIn" +#: ../misc/variables/article.rst:1 +msgid "``#{article.to}``" msgstr "" -#: ../settings/security/third-party.rst:30 -msgid "Weibo" +#: ../misc/variables/article.rst:1 +msgid "``helpdesk@example.com``" msgstr "" -#: ../settings/security/third-party.rst:35 -msgid "Automatic Account Link on Initial Logon" +#: ../misc/variables/article.rst:1 +msgid "Article > Type > Name" msgstr "" -#: ../settings/security/third-party.rst:37 -msgid "" -"In general there's two possible options for Zammad on how to deal with " -"already known users as they try to authenticate against a third-party " -"application. By default, Zammad will not automatically link \"unknown\" " -"authentication providers to existing accounts." +#: ../misc/variables/article.rst:1 +msgid "``#{article.type.name}``" msgstr "" -#: ../settings/security/third-party.rst:42 +#: ../misc/variables/article.rst:1 msgid "" -"This means that the user has to manually link authentication providers to " -"their accounts (for more about this :user-docs:`consult the user " -"documentation `)." +"``email`` (`list of article types `_)" msgstr "" -#: ../settings/security/third-party.rst:46 -msgid "" -"Sometimes this doesn't come in handy as this also means you'll receive error " -"messages about \"email address being in use already\" for (yet) unknown " -"third-party authentication methods." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Address" msgstr "" -#: ../settings/security/third-party.rst:50 -msgid "" -"If you want to allow your users to always be able to log in, no matter what, " -"you may want to enable ``Automatic account link on initial logon``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.address}``" msgstr "" -#: ../settings/security/third-party.rst:None -msgid "" -"Screenshot highlighting the \"Automatic account link on initial logon\"\n" -"setting" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Department" msgstr "" -#: ../settings/security/third-party.rst:60 -msgid "Automatic Account Linking Notification" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.department}``" msgstr "" -#: ../settings/security/third-party.rst:64 -msgid "" -"To improve security and your users awareness, you can enable Zammad to " -"notify your users when a new third-party application has been linked to " -"their account." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Email" msgstr "" -#: ../settings/security/third-party.rst:68 -msgid "" -"This notification is sent out once per third-party application. Zammad does " -"also mention the method used, e.g.: ``Microsoft``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.email}``" msgstr "" -#: ../settings/security/third-party.rst:71 -msgid "By default this setting is not active (set to ``no``)." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Fax" msgstr "" -#: ../settings/security/third-party.rst:0 -msgid "" -"Screenshot showing sample notification mail after initial\n" -"third-party linking" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.fax}``" msgstr "" -#: ../settings/security/third-party.rst:85 -msgid "" -"This notification is only sent if the account in question already exists. If " -"the login via the third-party also creates the missing account, the " -"notification will be skipped." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Firstname" msgstr "" -#: ../settings/security/third-party.rst:89 -msgid "This means it only affects:" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.firstname}``" msgstr "" -#: ../settings/security/third-party.rst:91 -msgid "manual account linking within the third-party page of the users profile" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Lastname" msgstr "" -#: ../settings/security/third-party.rst:92 -msgid "" -"logging into an existing local account by utilizing the *automatic account " -"link on initial logon* functionality" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.lastname}``" msgstr "" -#: ../settings/security/third-party.rst:None -msgid "" -"Screenshot showing the \"automatic account linking notification\"\n" -"setting" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Login" msgstr "" -#: ../settings/security/third-party.rst:100 -msgid "No User Creation on Logon" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.login}``" msgstr "" -#: ../settings/security/third-party.rst:102 -msgid "" -"By default, Zammad will create a new user account if the user logs in via a " -"third-party application and the account doesn't exist yet." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Mobile" msgstr "" -#: ../settings/security/third-party.rst:105 -msgid "" -"If you want to prevent Zammad from creating new accounts on logon, you can " -"disable this feature by setting ``No user creation on logon`` to ``yes``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.mobile}``" msgstr "" -#: ../settings/security/third-party.rst:None -msgid "Screenshot showing the \"no user creation on logon\" setting" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Note" msgstr "" -#: ../settings/security/third-party/facebook.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via Facebook To do " -"so, you need to follow these steps:" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.note}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:9 -msgid "Register Facebook App" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Phone" msgstr "" -#: ../settings/security/third-party/facebook.rst:11 -msgid "" -"Visit [https://developers.facebook.com/apps/] and click on \"Add a new App\"" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.phone}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "initial page" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > VIP" msgstr "" -#: ../settings/security/third-party/facebook.rst:17 -msgid "After that enter the app settings" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.vip}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "Create App" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Web" msgstr "" -#: ../settings/security/third-party/facebook.rst:22 -msgid "Navigate to \"Settings\" and fill in this infromation" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.web}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "App Settings" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated" msgstr "" -#: ../settings/security/third-party/facebook.rst:27 -msgid "Navigate to app review and Check \"Make [appname] public?\"" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_at}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "App Review" +#: ../misc/variables/article.rst:1 +msgid "Article > Visibility" msgstr "" -#: ../settings/security/third-party/facebook.rst:35 -msgid "Configure Zammad as Facebook App" +#: ../misc/variables/article.rst:1 +msgid "``#{article.internal}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:37 -msgid "" -"Navigate to \"Admin -> Security -> Third Party Applications\" and enter the " -"App ID and the App Secret. You can find this Key in the Dashbard of your " -"Facebok app." +#: ../misc/variables/article.rst:1 +msgid "``false`` or ``true`` (false if not internal)" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "Zammad Configuration" +#: ../misc/variables/article.rst:1 +msgid "Article Text as HTML (not referenced)" msgstr "" -#: ../settings/security/third-party/facebook.rst:44 -#: ../settings/security/third-party/github.rst:43 -#: ../settings/security/third-party/gitlab.rst:46 -msgid "" -"Now you can link accounts via \"Avatar -> Profile -> Link Accounts\" or " -"login via Zammad login page." +#: ../misc/variables/article.rst:1 +msgid "``#{article.body_as_html}``" msgstr "" -#: ../settings/security/third-party/github.rst:2 -#: ../system/integrations/github.rst:2 -msgid "GitHub" +#: ../misc/variables/article.rst:1 +msgid "``Test`` with formatting" msgstr "" -#: ../settings/security/third-party/github.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via GitHub. To " -"activate the quick login you need to enable OAuth for GitHub." +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "Ticket > Article#" msgstr "" -#: ../settings/security/third-party/github.rst:8 -msgid "Register GitHub App" +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "``#{ticket.article_count}``" msgstr "" -#: ../settings/security/third-party/github.rst:10 -msgid "" -"Visit https://www.github.com/settings/applications/new and enter the app " -"settings. As callback URL enter \"https://zammad_host/auth/github/callback\" " -"where zammad_host has to be replaced with your Zammad FQDN" +#: ../misc/variables/article.rst:1 +msgid "``1`` number of ticket articles" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "Register OAuth app on www.github.com" +#: ../misc/variables/config.rst:2 +msgid "Config" msgstr "" -#: ../settings/security/third-party/github.rst:19 -msgid "Configure Zammad as GitHub App" +#: ../misc/variables/config.rst:6 +msgid "" +"Below you'll find config related variables. These hold useful configuration " +"information that you can use within e.g. triggers to show necessary " +"information to your customer." msgstr "" -#: ../settings/security/third-party/github.rst:21 -msgid "" -"Enter the \"APP ID\" and the \"APP SECRET\" from the GitHub OAUTH " -"Applications Dashboard" +#: ../misc/variables/config.rst:11 +msgid "Config Variables" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub config in Zammad admin interface" +#: ../misc/variables/config.rst:1 +msgid "Config > Fully Qualified Domain Name" msgstr "" -#: ../settings/security/third-party/github.rst:28 -msgid "" -"After you configured the GitHub credentials and activated the login method, " -"you should see a new icon on the login page." +#: ../misc/variables/config.rst:1 +msgid "``#{config.fqdn}``" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub logo on login page" +#: ../misc/variables/config.rst:1 +msgid "``zammad.example.com``" msgstr "" -#: ../settings/security/third-party/github.rst:34 -msgid "" -"If you click on the icon you will be redirected to GitHub and see something " -"similar to this:" +#: ../misc/variables/config.rst:1 +msgid "Config > HTTP type" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub oauth page" +#: ../misc/variables/config.rst:1 +msgid "``#{config.http_type}``" msgstr "" -#: ../settings/security/third-party/github.rst:40 -#: ../settings/security/third-party/gitlab.rst:42 -msgid "" -"When you grant the access you will be redirected to your Zammad instance and " -"logged in as a customer." +#: ../misc/variables/config.rst:1 +msgid "``https`` or ``http``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:2 -msgid "Gitlab" +#: ../misc/variables/config.rst:1 +msgid "Config > Organization" msgstr "" -#: ../settings/security/third-party/gitlab.rst:4 +#: ../misc/variables/config.rst:1 +msgid "``#{config.organization}``" +msgstr "" + +#: ../misc/variables/config.rst:1 msgid "" -"It is possible to create a quick login for your helpdesk via Gitlab. To " -"activate the quick login you need to enable OAuth for Gitlab." +"``Zammad GmbH`` value set in `Branding `_" msgstr "" -#: ../settings/security/third-party/gitlab.rst:8 -msgid "Register Gitlab App" +#: ../misc/variables/config.rst:1 +msgid "Config > Product Name" msgstr "" -#: ../settings/security/third-party/gitlab.rst:10 -msgid "To register an app in Gitlab open your profile and select applications." +#: ../misc/variables/config.rst:1 +msgid "``#{config.product_name}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:12 +#: ../misc/variables/config.rst:1 msgid "" -"As callback URL enter \"https://zammad-fqdn/auth/gitlab/callback\" where " -"zammad-fqdn has to be replaced with your Zammad FQDN" +"``Helpdesk`` value set in `Branding `_" msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Register OAuth app on gitlab instance" +#: ../misc/variables/config.rst:1 +msgid "Config > SystemID" msgstr "" -#: ../settings/security/third-party/gitlab.rst:18 -msgid "Just select *read_user* under scopes as in the screenshot and save it." +#: ../misc/variables/config.rst:1 +msgid "``#{config.system_id}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:21 -msgid "Configure Zammad as Gitlab App" +#: ../misc/variables/config.rst:1 +msgid "``31`` (value between 1 and 99)" msgstr "" -#: ../settings/security/third-party/gitlab.rst:23 -msgid "" -"Enter the \"APP ID\" and the \"APP SECRET\" from the Gitlab OAUTH " -"Applications Dashboard and your Gitlab-URL in the \"SITE\" field." +#: ../misc/variables/config.rst:1 +msgid "Config > Ticket Hook" msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab config in Zammad admin interface" +#: ../misc/variables/config.rst:1 +msgid "``#{config.ticket_hook}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:30 -msgid "" -"After you configured the Gitlab credentials and activated the login method, " -"you should see a new icon on the login page." +#: ../misc/variables/config.rst:1 +msgid "``Ticket#``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab logo on login page" +#: ../misc/variables/current-user.rst:2 +msgid "Current User" msgstr "" -#: ../settings/security/third-party/gitlab.rst:36 +#: ../misc/variables/current-user.rst:6 msgid "" -"If you click on the icon you will be redirected to Gitlab and see something " -"similar to this:" +"Current user variables always return values of the current user that caused " +"e.g. a trigger to run." msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab oauth page" +#: ../misc/variables/current-user.rst:8 +msgid "" +"Due to the above fact, these variables are often not (yet) set or available " +"for usage." msgstr "" -#: ../settings/security/third-party/google.rst:4 +#: ../misc/variables/current-user.rst:10 msgid "" -"With some easy and fast steps, you can enable Zammad to authenticate your " -"users via Google." +"In situations where e.g. schedulers or triggers run, this most likely is " +"nothing you want to use." msgstr "" -#: ../settings/security/third-party/google.rst:8 -msgid "Register a Google App" +#: ../misc/variables/current-user.rst:13 +msgid "Current User Variables" msgstr "" -#: ../settings/security/third-party/google.rst:10 -msgid "" -"First of all, we need to create a new project - you can skip this step if " -"you already have one." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Address" msgstr "" -#: ../settings/security/third-party/google.rst:15 -msgid "" -"Use this link to create a new project: https://console.cloud.google.com/" -"projectcreate" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.address}``" msgstr "" -#: ../settings/security/third-party/google.rst:18 -msgid "" -"Now expand the menu, expand \"APIs & Services\" and select \"Credentials\". " -"Go to the tab \"OAuth consent screen\" first and ensure to fill in the " -"requested information - without doing so you can't create credentials!" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set" msgstr "" -#: ../settings/security/third-party/google.rst:None -msgid "Creating a consent screen" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Avatar" msgstr "" -#: ../settings/security/third-party/google.rst:25 -msgid "" -"After filling in and saving the consent screen information, you can go to " -"the \"Credentials\" tab and create new \"OAuth client ID\"-Credentials." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/google.rst:28 -msgid "" -"Fill in the necessary information as follows and replace ``zammad_host`` " -"with your FQDN:" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "avatar picture with width and height in pixel (e.g. 60,60)" msgstr "" -#: ../settings/security/third-party/google.rst:31 -msgid "**Application type** ``[x] Web application``" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created at" msgstr "" -#: ../settings/security/third-party/google.rst:34 -msgid "**Authorized JavaScript origins** ``https://zammad_host/``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_at}``" msgstr "" -#: ../settings/security/third-party/google.rst:37 -msgid "" -"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" -"callback``" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC``" msgstr "" -#: ../settings/security/third-party/google.rst:None -msgid "Adding a new OAuth client ID" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Address" msgstr "" -#: ../settings/security/third-party/google.rst:43 -msgid "" -"After creating the credentials, go to your Zammad installation and navigate " -"to \"Admin > Security > Third Party Applications\" > Google. Enter your " -"Client ID and Client secret here." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.address}``" msgstr "" -#: ../settings/security/third-party/google.rst:None -msgid "Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Avatar" msgstr "" -#: ../settings/security/third-party/google.rst:50 -msgid "After submitting, the login via Google can be used." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:2 -msgid "Microsoft" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Department" msgstr "" -#: ../settings/security/third-party/microsoft.rst:4 -msgid "" -"Zammad's Microsoft connection allows your users with Microsoft accounts to " -"login. This works for Azure users as well and can be an alternative to :doc:" -"`/system/integrations/ldap/index`." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.department}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:10 -msgid "" -"This documentation part does not cover our :doc:`📧 Microsoft 365 email " -"channel `." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Sales`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screenshot showing Microsoft login button on Zammad login screen." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Email" msgstr "" -#: ../settings/security/third-party/microsoft.rst:30 -#: ../settings/security/third-party/microsoft.rst:53 -msgid "Supported account types:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.email}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:22 -msgid "" -"Please note that Zammad only supports these account types (App dependent):" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``jdoe@customer.tld``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:35 -msgid "Avatars of signing in users:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Fax" msgstr "" -#: ../settings/security/third-party/microsoft.rst:33 -msgid "" -"Zammad currently ignores user avatars. If the user is registered with e.g. " -"Gravatar, Zammad will fetch the avatar from there if enabled. See :doc:" -"`Zammad Image Service ` for more." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.fax}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:38 -msgid "Step 1 - Register a Microsoft App for Zammad" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``004930123464789`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:40 -msgid "" -"Login to the `Microsoft Azure Portal `_ and " -"navigate to App registrations to create a new app. Provide the requested " -"information as follows and register your app." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Firstname" msgstr "" -#: ../settings/security/third-party/microsoft.rst:46 -msgid "Name:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.firstname}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:45 -msgid "" -"Any meaningful name fitting, this name will be displayed to users trying to " -"authenticate with this app." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``John`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:49 -msgid "Choose one of the above mentioned account types (see Limitations)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Lastname" msgstr "" -#: ../settings/security/third-party/microsoft.rst:51 -msgid "" -"The correct account type depends on your use case. If you want to use the " -"authentication internal only, choose the first option. If you're unsure, use " -"the \"Help me choose...\" link." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.lastname}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:58 -msgid "Redirect URI (optional):" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Login" msgstr "" -#: ../settings/security/third-party/microsoft.rst:56 -msgid "" -"Select web and provide your callback URL. The callback URL looks like this: " -"``https://zammad.domain.tld/auth/microsoft_office365/callback``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.login}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to register a Microsoft app" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Mobile" msgstr "" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "Within **API permissions** add the following permissions:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.mobile}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:69 -msgid "``User.Read``" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``0049176123456789`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "Contacts" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Note" msgstr "" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "``Contacts.Read``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.note}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:73 -msgid "" -"You can find these permissions within *Microsoft Graph → Delegated " -"permissions*." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Some note to this user`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to add required API permissions" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Phone" msgstr "" -#: ../settings/security/third-party/microsoft.rst:80 -msgid "" -"Within **Certificates & secrets** create a new client secret. Note down the " -"returned secret **value** for later. **Do not** use the secret ID!" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.phone}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to create a new app secret" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``004930123456789`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:88 -msgid "" -"From **Overview** copy your apps *Application (client) ID*. If you're using " -"a single tenant app, please also copy *Directory (tenant) ID*. You now have " -"all required information for Zammad." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > VIP" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to retreive application client and tenant IDs" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.vip}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:98 -msgid "Step 2 - Add App Credentials to Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Web" msgstr "" -#: ../settings/security/third-party/microsoft.rst:100 -msgid "" -"Navigate to Security > Third-party Applications (Tab) within Zammad's admin " -"settings. Scroll down to the section *Authentication via Microsoft* and fill " -"in the required information." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.web}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:105 -msgid "App ID:" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``https://zammad.org`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:105 -msgid "This is your *Application (client) ID*." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Department" msgstr "" -#: ../settings/security/third-party/microsoft.rst:108 -msgid "App secret:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.department}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:108 -msgid "This is your *client secret* (value)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Email" msgstr "" -#: ../settings/security/third-party/microsoft.rst:113 -msgid "App Tenant ID:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.email}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:111 -msgid "" -"**optional** only required for apps that use account type *Accounts in this " -"organizational directory only (Default Directory only - Single tenant).*" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Fax" msgstr "" -#: ../settings/security/third-party/microsoft.rst:115 -msgid "" -"Apply your settings by pressing submit and activate *Authentication via " -"Microsoft*." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.fax}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "" -"Screencast showing how to add app credentials and activating the\n" -"authentication method" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Firstname" msgstr "" -#: ../settings/security/third-party/saml.rst:2 -msgid "SAML" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.firstname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:4 -msgid "" -"Connect your SAML (Security Assertion Markup Language) identity provider as " -"a single sign-on (SSO) method." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Lastname" msgstr "" -#: ../settings/security/third-party/saml.rst:7 -msgid "" -"SAML is an open standard for SSO authentication (among other things). Sign-" -"ins are shared across multiple **service providers** and managed by a " -"central **identity provider** (IdP)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.lastname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:11 -msgid "" -"In this case, the service provider is Zammad, and the IdP is a software " -"service that you either host or subscribe to (*e.g.,* `Keycloak `_, `Redhat SSO Server `_, `ADFS `_, or `Okta `_)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Login" msgstr "" -#: ../settings/security/third-party/saml.rst:18 -msgid "" -"This guide assumes you are already using SAML within your organization (i." -"e., that your IdP is fully set up)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.login}``" msgstr "" -#: ../settings/security/third-party/saml.rst:21 -msgid "" -"Please note: Our instructions are based on connecting Zammad with Keycloak." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Mobile" msgstr "" -#: ../settings/security/third-party/saml.rst:25 -msgid "Step 1: Configure Your IdP" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.mobile}``" msgstr "" -#: ../settings/security/third-party/saml.rst:28 -msgid "Add Zammad as a Client/App" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Note" msgstr "" -#: ../settings/security/third-party/saml.rst:30 -msgid "" -"Import Zammad into your IdP using the XML configuration found at ``https://" -"your.zammad.domain/auth/saml/metadata``." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.note}``" msgstr "" -#: ../settings/security/third-party/saml.rst:33 -msgid "" -"If your IdP doesn't support XML import, you will have to configure Zammad as " -"a new client/app manually using the above XML metadata file for reference." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Domain based assignment" msgstr "" -#: ../settings/security/third-party/saml.rst:36 -msgid "For instance, when you see this tag:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.domain_assignment}``" msgstr "" -#: ../settings/security/third-party/saml.rst:42 -msgid "" -"Set the **Assertion Consumer Service Binding URL** (sometimes also listed as " -"**Valid Redirect URIs**) to ``http://your.zammad.domain/auth/saml/callback``." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Domain" msgstr "" -#: ../settings/security/third-party/saml.rst:47 -msgid "Set Up User Attribute Mapping" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.domain}``" msgstr "" -#: ../settings/security/third-party/saml.rst:49 -msgid "" -"Zammad requests the following user attributes (or “properties”) from the IdP:" +#: ../misc/variables/current-user.rst:1 +msgid "``zammad.com`` or empty if not set" msgstr "" -#: ../settings/security/third-party/saml.rst:51 -msgid "Email address (``email``)" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Name" msgstr "" -#: ../settings/security/third-party/saml.rst:52 -msgid "Full name (``name``)" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.name}``" msgstr "" -#: ../settings/security/third-party/saml.rst:53 -msgid "Given name (``first_name``)" +#: ../misc/variables/current-user.rst:1 +msgid "``Zammad GmbH``" msgstr "" -#: ../settings/security/third-party/saml.rst:54 -msgid "Family name (``last_name``)" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Note" msgstr "" -#: ../settings/security/third-party/saml.rst:56 -msgid "" -"You may need to set up “mappers” (or “mappings”) to tell your IdP how user " -"attributes in SAML correspond to those in Zammad. For a more detailed " -"breakdown, refer to the XML metadata file referenced in the previous section." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.note}``" msgstr "" -#: ../settings/security/third-party/saml.rst:62 -msgid "Per-IdP Instructions" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``A note to the organization of the user`` or empty if not set" msgstr "" -#: ../settings/security/third-party/saml.rst:102 -msgid "Keycloak" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Shared organization" msgstr "" -#: ../settings/security/third-party/saml.rst:65 -msgid "" -"**To add Zammad as a client,** save the XML configuration to disk (``https://" -"your.zammad.domain/auth/saml/metadata``) and use **Clients > Clients list > " -"Import client** in the Keycloak admin panel." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.shared}``" msgstr "" -#: ../settings/security/third-party/saml.rst:70 -msgid "" -"To help Zammad **match its own user accounts to Keycloak users**, create a " -"user attribute (or “property”) mapper. In **Clients list**, click on your " -"newly created Client ID, choose the tab **Client scopes** and click on the " -"link which refers to your Zammad instance. Choose **Add mapper > By " -"configuration > User Property** and create a mapper with the following " -"entries:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > VIP" msgstr "" -#: ../settings/security/third-party/saml.rst:78 -msgid "**Name**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.vip}``" msgstr "" -#: ../settings/security/third-party/saml.rst:80 -msgid "**Mapper Type**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Phone" msgstr "" -#: ../settings/security/third-party/saml.rst:81 -msgid "``User Property``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.phone}``" msgstr "" -#: ../settings/security/third-party/saml.rst:82 -msgid "**Property**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated at" msgstr "" -#: ../settings/security/third-party/saml.rst:83 -msgid "``emailAddress``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_at}``" msgstr "" -#: ../settings/security/third-party/saml.rst:84 -msgid "**SAML Attribute Name**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Address" msgstr "" -#: ../settings/security/third-party/saml.rst:86 -msgid "**SAML Attribute NameFormat**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.address}``" msgstr "" -#: ../settings/security/third-party/saml.rst:87 -msgid "``basic``" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Avatar" msgstr "" -#: ../settings/security/third-party/saml.rst:89 -msgid "" -"In the example above, we're telling Zammad that whenever it receives a SAML " -"login request, it should take the ``email`` property from Keycloak, look for " -"a Zammad user with the same ``email`` attribute, and create a new session " -"for that user." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/saml.rst:95 -msgid "" -"If your Keycloak users' email addresses are stored on another property (*e." -"g.,* ``username``), adjust accordingly." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Department" msgstr "" -#: ../settings/security/third-party/saml.rst:98 -msgid "" -"Back in **Settings**, enter the Client ID (``https://your.zammad.domain/auth/" -"saml/metadata``) in the field **Master SAML Processing URL**." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.department}``" msgstr "" -#: ../settings/security/third-party/saml.rst:101 -msgid "You also need to enable **Sign assertions**." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Email" msgstr "" -#: ../settings/security/third-party/saml.rst:105 -msgid "Step 2: Configure Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.email}``" msgstr "" -#: ../settings/security/third-party/saml.rst:107 -msgid "" -"Enable SAML and enter your IdP's details in the Admin Panel under **Settings " -"> Security > Third Party Applications > Authentication via SAML**:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Fax" msgstr "" -#: ../settings/security/third-party/saml.rst:None -msgid "Example configuration of SAML part 1" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.fax}``" msgstr "" -#: ../settings/security/third-party/saml.rst:119 -msgid "Display name" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Firstname" msgstr "" -#: ../settings/security/third-party/saml.rst:116 -msgid "" -"Allows you to define a custom button name for SAML. This helps your users to " -"understand better what the button on the login page does." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.firstname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:119 -msgid "Defaults to ``SAML``." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Lastname" msgstr "" -#: ../settings/security/third-party/saml.rst:123 -msgid "IDP SSO target URL" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.lastname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:122 -msgid "" -"This is the target URL Zammad shall redirect to when the user presses the " -"SAML button. For Keycloak, this needs to look like https://your.domain/" -"realms/your-realm/protocol/saml" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Login" msgstr "" -#: ../settings/security/third-party/saml.rst:127 -msgid "IDP single logout target URL" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.login}``" msgstr "" -#: ../settings/security/third-party/saml.rst:126 -msgid "" -"This is the URL to which the single logout request and response should be " -"sent." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Mobile" msgstr "" -#: ../settings/security/third-party/saml.rst:131 -msgid "IDP certificate" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.mobile}``" msgstr "" -#: ../settings/security/third-party/saml.rst:130 -msgid "" -"The public certificate of your IDP for Zammad to verify during the callback " -"phase." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Note" msgstr "" -#: ../settings/security/third-party/saml.rst:145 -msgid "IDP certificate fingerprint" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.note}``" msgstr "" -#: ../settings/security/third-party/saml.rst:134 -msgid "" -"The fingerprint of your IDPs public certificate to verify during callback " -"phase." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Phone" msgstr "" -#: ../settings/security/third-party/saml.rst:137 -msgid "🔏 **For the IdP certificate / certificate fingerprint:**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.phone}``" msgstr "" -#: ../settings/security/third-party/saml.rst:139 -msgid "" -"Provide **only one or the other**—do not provide both! (Between the two, we " -"recommend the signing certificate itself: fingerprints use SHA-1, which `has " -"been broken for a while now `_.)" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > VIP" msgstr "" -#: ../settings/security/third-party/saml.rst:144 -msgid "" -"**Keycloak users:** Find your certificate in the Keycloak admin panel under " -"**Realm Settings > Keys > Algorithm: RS256 > Certificate**." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.vip}``" msgstr "" -#: ../settings/security/third-party/saml.rst:151 -msgid "Name identifier format" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``false`` or ``true``" msgstr "" -#: ../settings/security/third-party/saml.rst:148 -msgid "" -"This is the unique identifiers field type. Usually it should be ``urn:oasis:" -"names:tc:SAML:1.1:nameid-format:emailAddress``." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Web" msgstr "" -#: ../settings/security/third-party/saml.rst:151 -msgid "Zammad **expects an email address as unique identifier**!" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.web}``" msgstr "" -#: ../settings/security/third-party/saml.rst:155 -msgid "UID attribute name" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > VIP" msgstr "" -#: ../settings/security/third-party/saml.rst:154 -msgid "" -"Here you can define an attribute that uniquely identifies the user. If " -"unset, the name identifier returned by the IDP is used." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.vip}``" msgstr "" -#: ../settings/security/third-party/saml.rst:None -msgid "Example configuration of SAML part 2" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Web" msgstr "" -#: ../settings/security/third-party/saml.rst:163 -msgid "" -"Decide if the certificate for the connection to the IdP service has to be " -"verified or not (default: ``yes``)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.web}``" msgstr "" -#: ../settings/security/third-party/saml.rst:169 -msgid "Signing & Encrypting" +#: ../misc/variables/ticket.rst:6 +msgid "" +"Below you can find all available ticket-based variables within Zammad. These " +"can be called via triggers for example. If you're unsure if Zammad does " +"support variables at the point you're at, you can try to type ``::`` to " +"check." msgstr "" -#: ../settings/security/third-party/saml.rst:169 -msgid "" -"Define if you want to sign, encrypt, do both or nothing for the requests." +#: ../misc/variables/ticket.rst:12 +msgid "Ticket Variables" msgstr "" -#: ../settings/security/third-party/saml.rst:179 -msgid "Certificate (PEM)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Accounted Time" msgstr "" -#: ../settings/security/third-party/saml.rst:172 -msgid "" -"Paste the public certificate of your Zammad SAML client, if you want to " -"encrypt the requests." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.time_unit}``" msgstr "" -#: ../settings/security/third-party/saml.rst:175 -msgid "Make sure the certificate is:" +#: ../misc/variables/ticket.rst:1 +msgid "``1``, ``2.75`` or empty response" msgstr "" -#: ../settings/security/third-party/saml.rst:177 -msgid "already valid and not yet expired" +#: ../misc/variables/ticket.rst:1 +msgid "``3``, any number of articles existing in the ticket right now" msgstr "" -#: ../settings/security/third-party/saml.rst:178 -msgid "no CA certificate" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Closing time" msgstr "" -#: ../settings/security/third-party/saml.rst:179 -msgid "valid for signing and encrypting" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.close_at}``" msgstr "" -#: ../settings/security/third-party/saml.rst:185 -msgid "Private key (PEM)" +#: ../misc/variables/ticket.rst:1 +msgid "2019-10-07 17:25:00 UTC" msgstr "" -#: ../settings/security/third-party/saml.rst:182 -msgid "" -"Paste the private key of your Zammad SAML client here, if you want to sign " -"the requests." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created at" msgstr "" -#: ../settings/security/third-party/saml.rst:185 -msgid "Make sure the key is an RSA key with a length of at least 2048 bits." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_at}``" msgstr "" -#: ../settings/security/third-party/saml.rst:188 -msgid "Private key secret" +#: ../misc/variables/ticket.rst:1 +msgid "2019-10-07 16:25:00 UTC" msgstr "" -#: ../settings/security/third-party/saml.rst:188 -msgid "If your private key is secured with a secret, you can provide it here." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Address" msgstr "" -#: ../settings/security/third-party/saml.rst:192 -msgid "Your callback URL" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.address}``" msgstr "" -#: ../settings/security/third-party/saml.rst:191 -msgid "" -"This URL is needed for your IdP configuration so it knows where to redirect " -"to after successful authentication." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Avatar" msgstr "" -#: ../settings/security/third-party/saml.rst:194 -msgid "" -"After saving your input by clicking on the \"Submit\" button, Zammad " -"verifies the provided keys/certificates (e.g. if they are valid for signing/" -"encrypting and if they aren't expired)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/saml.rst:199 -msgid "" -"See :ref:`automatic account linking ` for details " -"on how to link existing Zammad accounts to IdP accounts." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Department" msgstr "" -#: ../settings/security/third-party/saml.rst:205 -msgid "Automatic account linking doesn't work" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.department}``" msgstr "" -#: ../settings/security/third-party/saml.rst:206 -msgid "" -"Have you double-checked your IdP's user attribute mapping configuration?" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Email" msgstr "" -#: ../settings/security/third-party/twitter.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via Twitter. To do " -"so, you need to follow these steps:" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.email}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:8 -msgid "Register Twitter App" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Fax" msgstr "" -#: ../settings/security/third-party/twitter.rst:10 -msgid "Go to https://dev.twitter.com/apps and login with your account." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.fax}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:15 -msgid "Click on \"Create App\"" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Firstname" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "new app page" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.firstname}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:20 -msgid "" -"Enter app settings. As \"Callback URL\" you need to enter ``https://" -"zammad_host/api/v1/external_credentials/twitter/callback``. You need to " -"replace ``zammad_host`` with the domain of your Zammad system." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Lastname" msgstr "" -#: ../settings/security/third-party/twitter.rst:24 -msgid "" -"After the app has been created, update the application icon and organization " -"attributes." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.lastname}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "set permissions to receive and send direct messages" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Login" msgstr "" -#: ../settings/security/third-party/twitter.rst:30 -msgid "" -"Next we need to set ``read, write and access direct messages`` permissions " -"for the app." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.login}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "click on Keys & Access Token, note them" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Mobile" msgstr "" -#: ../settings/security/third-party/twitter.rst:36 -msgid "" -"Go to \"Keys and Access Token\" tab and note the \"Consumer Key\" and " -"\"Consumer Secret\"." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.mobile}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:40 -msgid "Configure Zammad as Twitter App" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Note" msgstr "" -#: ../settings/security/third-party/twitter.rst:42 -msgid "" -"Go to \"Admin > Security > Twitter > Third Party Applications > Twitter\" " -"Section." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.note}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "Admin > Security > Third Party Applications" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Phone" msgstr "" -#: ../settings/security/third-party/twitter.rst:48 -msgid "" -"Fill in the \"Twitter Key\" and the \"Twitter Secret\" and click the " -"\"Submit\" button." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.phone}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:51 -msgid "" -"Now you can link accounts via \"Avatar > Profile > Link Accounts\" or login " -"via Zammad login page." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > VIP" msgstr "" -#: ../settings/security/two-factor.rst:11 -msgid "Two-factor Authentication Methods" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.vip}``" msgstr "" -#: ../settings/security/two-factor.rst:2 -msgid "Two-Factor Authentication" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Web" msgstr "" -#: ../settings/security/two-factor.rst:4 -msgid "" -"Two-factor authentication (2FA) enhances the security of Zammad accounts by " -"adding an extra layer of verification beyond a password. It requires users " -"to provide two different types of authentication factors, typically " -"something they know (like a password) and something they possess (like a " -"mobile device or a security token), to ensure that only authorized " -"individuals can access the account." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.web}``" msgstr "" -#: ../settings/security/two-factor.rst:19 -msgid "Enable Recovery Codes" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Address" msgstr "" -#: ../settings/security/two-factor.rst:21 -msgid "" -"Recovery codes are one-time use security codes that can be used by the user " -"if they lose access to their other two-factor authentication methods. They " -"cannot be used on their own, they can only be activated if at least one two-" -"factor authentication method is enabled." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.address}``" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Enable Recovery Codes Setting" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Avatar" msgstr "" -#: ../settings/security/two-factor.rst:30 -msgid "" -"Recovery codes can only be used as a backup method. If enabled, they will be " -"automatically generated for the user once they set up their initial two-" -"factor authentication method." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.avatar(60,60)}``" msgstr "" -#: ../settings/security/two-factor.rst:34 -msgid "" -"The user will be asked to print out or save the generated recovery codes in " -"a safe place. Once used, a recovery code cannot be reused." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Department" msgstr "" -#: ../settings/security/two-factor.rst:37 -msgid "" -"Users will also have an option to regenerate their recovery codes at any " -"time, which invalidates already existing recovery codes and provides them " -"with a list of fresh codes." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.department}``" msgstr "" -#: ../settings/security/two-factor.rst:41 -msgid "" -"After you enable this setting, when the user completes a setup of their " -"initial two-factor authentication method, they will be presented with a list " -"of recovery codes and instructed to save them for later use." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Email" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Recovery Codes Generation Modal Dialog" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.email}``" msgstr "" -#: ../settings/security/two-factor.rst:50 -msgid "Enforce the Set Up of the Two-Factor Authentication" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Fax" msgstr "" -#: ../settings/security/two-factor.rst:52 -msgid "" -"In case you wish to require your users to set up at least one two-factor " -"authentication method for their account, you can do this by selecting " -"specific user roles the requirement applies to in **Enforced for user " -"roles** setting. Of course you must have at least one two-factor " -"authentication method enabled for this setting to take effect." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.fax}``" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Enforced for User Roles Setting" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Firstname" msgstr "" -#: ../settings/security/two-factor.rst:62 -msgid "" -"After you change this setting, if the user has one of the selected roles on " -"their account, they will be forced to set up the two-factor authentication " -"upon next sign in or application reload." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.firstname}``" msgstr "" -#: ../settings/security/two-factor.rst:66 -msgid "" -"A modal dialog with instructions will be shown, and they will not be able to " -"do any work before they set up at least one two-factor method." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Lastname" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Modal Dialog for Enforcing Two-Factor Authentication Set Up" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.lastname}``" msgstr "" -#: ../settings/security/two-factor.rst:74 -msgid "Reset Two-Factor Authentication for a Specific User" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Login" msgstr "" -#: ../settings/security/two-factor.rst:76 -msgid "" -"In case an user isn't able to login anymore because of an inaccessible " -"second factor, you can reset the user's 2FA method." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.login}``" msgstr "" -#: ../settings/security/two-factor.rst:79 -msgid "" -"To do this, go to the user management and search for the relevant user. " -"After you found the account, click the button in the action column and " -"select \"Manage Two-Factor Authentication\":" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Mobile" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Context menu in action column in user management" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.mobile}``" msgstr "" -#: ../settings/security/two-factor.rst:87 -msgid "" -"After selecting this, you can see a dialog where you can either reset one " -"2FA method or reset all of the user's 2FA methods:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Note" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Dialog for resetting user's 2FA method" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.note}``" msgstr "" -#: ../settings/security/two-factor.rst:94 -msgid "" -"Choose the fitting one, click on the corresponding \"Remove ...\" button and " -"confirm your action. The user now has to setup a new 2FA method, depending " -"on your 2FA configuration." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Phone" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:2 -msgid "Authenticator App" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.phone}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:4 -msgid "" -"The authenticator app method is a type of two-factor authentication that " -"uses a mobile application to generate one-time codes for account " -"verification. After setting up the authenticator app on their device, the " -"user links it to their Zammad account." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > VIP" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:12 -msgid "" -"When logging in, the user is prompted to enter a time-sensitive code " -"generated by the app, in addition to their password. This code acts as the " -"second factor of authentication, providing an extra layer of security as it " -"changes periodically and is unique to the user's device." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.vip}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:None -msgid "Security Code in Google Authenticator App" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Web" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:22 -msgid "" -"The app generates codes based on a shared secret key stored securely on both " -"the user's device and the server, ensuring a synchronized and secure " -"authentication process. The method of generating the codes is sometimes also " -"called TOTP (time-based one-time password)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.web}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:28 -msgid "Enabling the Authenticator App Method" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Escalation at" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:30 -#: ../settings/security/two-factor/security-keys.rst:28 -msgid "To enable the method, just toggle the switch on in the settings." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.escalation_at}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:None -msgid "Authenticator App Switch in Settings" +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:36 -msgid "" -"Now the users will be able to set up this two-factor authentication method " -"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " -"Once they do, on next sign-in with password, they will be asked to provide " -"an additional security code generated by their mobile device." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > First response" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:2 -msgid "Security Keys" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.first_response_at}``" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:4 -msgid "" -"The security keys method is a type of a two-factor authentication that uses " -"Web Authentication API in the browser for verifying user's identity. The " -"user can register multiple hardware or software security keys with their " -"Zammad account and then they can use it during the sign-in process." +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable yet" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:12 -msgid "" -"When logging in, the user is prompted to provide the same security key they " -"registered with their account, in addition to their password. This key acts " -"as the second factor of authentication, providing an extra layer of security." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Assign Follow-Ups" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:None -msgid "Security Key dialog in Safari on macOS" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_assignment}``" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:21 -msgid "" -"The type of the key can range from hardware USB sticks to passkeys stored in " -"a device of user's choice. Which type can be used depends on the browser " -"flavor and the platform of the user." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Assignment Timeout" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:26 -msgid "Enabling the Security Keys Method" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.assignment_timeout}``" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:None -msgid "Security Keys Switch in Settings" +#: ../misc/variables/ticket.rst:1 +msgid "``20`` or empty if not configured" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:34 -msgid "" -"Now the users will be able to set up this two-factor authentication method " -"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " -"Once they do, on next sign-in with password, they will be asked to provide " -"the same security key they registered during the setup." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Follow-up possible" msgstr "" -#: ../settings/system/system-selfhosted.include.rst:3 -msgid "" -"Below settings are only available to self hosted users. In hosted " -"environments we're handling these settings for you to ensure service " -"stability." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_possible}``" msgstr "" -#: ../settings/system/base.rst:11 -msgid "Fully Qualified Domain Name" +#: ../misc/variables/ticket.rst:1 +msgid "``no`` or ``yes``" msgstr "" -#: ../settings/system/base.rst:7 -msgid "The URL of your Zammad installation." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Name" msgstr "" -#: ../settings/system/base.rst:9 ../settings/system/base.rst:17 -msgid "This setting is used within :doc:`/system/variables` and notifications." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.name}``" msgstr "" -#: ../settings/system/system-base.include.rst:1 -msgid "It is automatically set by the *Getting Started wizard*." +#: ../misc/variables/ticket.rst:1 +msgid "``Sales``" msgstr "" -#: ../settings/system/system-base.include.rst:5 -msgid "Changing this setting also changes callback URLs for your channels etc." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Note" msgstr "" -#: ../settings/system/system-base.include.rst:6 -msgid "This setting can have negative affects on being able to login." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.note}``" msgstr "" -#: ../settings/system/base.rst:19 -msgid "HTTP type" +#: ../misc/variables/ticket.rst:1 +msgid "``Note about this group``" msgstr "" -#: ../settings/system/base.rst:14 -msgid "" -"The HTTP type tells your installation how your clients connect. This is " -"relevant for authentication and cookie security." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > ID" msgstr "" -#: ../settings/system/base.rst:31 -msgid "SystemID" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.id}``" msgstr "" -#: ../settings/system/base.rst:22 -msgid "" -"This ID is being used within your ticket number. In case you're " -"communicating with another ticket system with similar ticket number schemes " -"this ID greatly reduces the risk of false follow ups." +#: ../misc/variables/ticket.rst:1 +msgid "``17``, ``5281``, ..." msgstr "" -#: ../settings/system/base.rst:26 -msgid "" -"The SystemID is randomly selected upon installation of Zammad (``1-99``)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact (agent)" msgstr "" -#: ../settings/system/base.rst:30 -msgid "" -"**Do not** change this setting in a productive system! Your Zammad " -"installation may no longer recognize old ticket number based follow ups upon " -"change!" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_agent_at}``" msgstr "" -#: ../settings/system/frontend.rst:2 -msgid "Frontend" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact (customer)" msgstr "" -#: ../settings/system/frontend.rst:22 -msgid "Core Workflow Ajax Mode" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_customer_at}``" msgstr "" -#: ../settings/system/frontend.rst:6 +#: ../misc/variables/ticket.rst:1 msgid "" -"This setting allows administrators to enforce :doc:`/system/core-workflows` " -"to use Ajax-Calls instead of web sockets. You'll usually only need this if " -"you experience serious issues as noted below." +"``2019-10-07 16:25:00 UTC`` or empty if not applicable yet (Please note " +"`Ticket last contact behavior Settings `_ for this)" msgstr "" -#: ../settings/system/frontend.rst:10 -msgid "**🤓 Possible (technical) reasons**" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact" msgstr "" -#: ../settings/system/frontend.rst:12 -msgid "" -"In some cases, your network structure (e.g. firewalls, proxies) may " -"disconnect long web socket connections. This leads to select fields staying " -"empty (e.g. owner selection *after* selecting your group) or fields not " -"shown / hidden (e.g. when switching to or from pending states, the \"pending " -"till\" field not showing / hiding)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_at}``" msgstr "" -#: ../settings/system/frontend.rst:18 -msgid "" -"Please keep in mind that the Ajax fallback may cause serious pressure on " -"your application server. If you have the choice stick to web sockets." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Number" msgstr "" -#: ../settings/system/frontend.rst:22 -msgid "Default: ``no`` (inactive)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.number}``" msgstr "" -#: ../settings/system/frontend.rst:53 -msgid "Show calendar weeks in the picker of date/datetime fields" +#: ../misc/variables/ticket.rst:1 +msgid "``31001``, ``201910731001``, ..." msgstr "" -#: ../settings/system/frontend.rst:25 -msgid "" -"With this setting you can instruct Zammad to provide week number display " -"globally for all users. Calendar with week number display are usually used " -"in business sectors and may not be relevant for everyone." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain based assignment" msgstr "" -#: ../settings/system/frontend.rst:29 -msgid "" -"This setting affects *all areas* - you'll also see week numbers in the admin " -"panel for e.g. triggers and macros." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain_assignment}``" msgstr "" -#: ../settings/system/frontend.rst:32 -msgid "Default: ``no`` (not shown)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain" msgstr "" -#: ../settings/system/frontend.rst:53 -msgid "Here's the difference:" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain}``" msgstr "" -#: ../settings/system/frontend.rst:0 -msgid "Screenshot showing Zammad's date picker (in the default way)" +#: ../misc/variables/ticket.rst:1 +msgid "``domain.tld`` or empty if not set" msgstr "" -#: ../settings/system/frontend.rst:41 -msgid "Set to ``no``" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Name" msgstr "" -#: ../settings/system/frontend.rst:0 -msgid "" -"Screenshot showing Zammad's date picker with\n" -"week numbers enabled" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.name}``" msgstr "" -#: ../settings/system/frontend.rst:50 -msgid "Set to ``yes``" +#: ../misc/variables/ticket.rst:1 +msgid "``Zammad GmbH`` or empty if not set" msgstr "" -#: ../settings/system/index.rst:4 -msgid "" -"For your overview we split each tab within system settings into its own page:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Note" msgstr "" -#: ../settings/system/index.rst:16 -msgid "Console Based Settings" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.note}``" msgstr "" -#: ../settings/system/index.rst:18 -msgid "" -"There's some console based settings we didn't put into the UI. However, you " -"may find them helpful - you can find them in our :docs:`hidden settings ` section." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Shared organization" msgstr "" -#: ../settings/system/network.rst:2 -msgid "Network" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.shared}``" msgstr "" -#: ../settings/system/network.rst:8 -msgid "" -"The proxy settings can only be saved after successfully testing the proxy " -"connection." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > VIP" msgstr "" -#: ../settings/system/network.rst:15 -msgid "Proxy Address." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.vip}``" msgstr "" -#: ../settings/system/network.rst:12 -msgid "" -"Allows you to provide a proxy server if needed. This is relevant for network " -"communication by Zammad." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Address" msgstr "" -#: ../settings/system/network.rst:15 -msgid "It **does not** affect the update process or Elasticsearch." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.address}``" msgstr "" -#: ../settings/system/network.rst:18 -msgid "Username for proxy connection." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Avatar" msgstr "" -#: ../settings/system/network.rst:18 -msgid "" -"If your proxy server requires authentication, provide the username here." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.avatar(60,60)}``" msgstr "" -#: ../settings/system/network.rst:21 -msgid "Password for proxy connection." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Department" msgstr "" -#: ../settings/system/network.rst:21 -msgid "" -"If your proxy server requires authentication, provide the password here." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.department}``" msgstr "" -#: ../settings/system/network.rst:26 -msgid "No proxy for the following hosts." +#: ../misc/variables/ticket.rst:1 +msgid "``Support`` or empty if not set" msgstr "" -#: ../settings/system/network.rst:24 -msgid "" -"Exception list for hosts you can't or don't want to reach via proxy server." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Email" msgstr "" -#: ../settings/system/network.rst:27 -msgid "Default: ``localhost,127.0.0.0,::1``" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.email}``" msgstr "" -#: ../settings/system/services.rst:2 -msgid "Services" +#: ../misc/variables/ticket.rst:1 +msgid "``agent@company.tld`` or empty if not set" msgstr "" -#: ../settings/system/services.rst:10 -msgid "Image Service" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Fax" msgstr "" -#: ../settings/system/services.rst:5 -msgid "Defines the backend for user and organization image lookups." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.fax}``" msgstr "" -#: ../settings/system/services.rst:7 -msgid "Default: ``Zammad Image Service`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Firstname" msgstr "" -#: ../settings/system/services.rst:9 -msgid "" -"Make sure your on premise installation has ``HTTPS`` access to ``images." -"zammad.com``." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.firstname}``" msgstr "" -#: ../settings/system/services.rst:18 -msgid "Geo Calendar Service" +#: ../misc/variables/ticket.rst:1 +msgid "``Max`` or empty if not set" msgstr "" -#: ../settings/system/services.rst:13 -msgid "" -"Defines the backend for geo calendar lookups. Used for initial calendar " -"setup." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Lastname" msgstr "" -#: ../settings/system/services.rst:16 -msgid "Default: ``Zammad GeoCalendar Service`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.lastname}``" msgstr "" -#: ../settings/system/services.include.rst:2 -msgid "" -"Make sure your on premise installation has ``HTTPS`` access to ``geo.zammad." -"com``." +#: ../misc/variables/ticket.rst:1 +msgid "``Mustermann`` or empty if not set" msgstr "" -#: ../settings/system/services.rst:26 -msgid "Geo IP Service" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Login" msgstr "" -#: ../settings/system/services.rst:21 -msgid "" -"Defines the backend for geo IP lookups. Shows also location of an IP address " -"if an IP address is shown." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.login}``" msgstr "" -#: ../settings/system/services.rst:24 -msgid "Default: ``Zammad GeoIP Service`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "``agent``" msgstr "" -#: ../settings/system/services.rst:32 -msgid "Geo Location Service" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Mobile" msgstr "" -#: ../settings/system/services.rst:29 -msgid "" -"Defines the backend for geo location lookups to store geo locations for " -"addresses." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.mobile}``" msgstr "" -#: ../settings/system/services.rst:32 -msgid "" -"Default: ``OpenStreetMap (ODbL 1.0, http://osm.org/copyright)`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Note" msgstr "" -#: ../settings/system/services.rst:36 -msgid "" -"You can find a detailed privacy information on what we store for how long on " -"our :docs:`Privacy Appendix ` inside of our System " -"Documentation." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.note}``" msgstr "" -#: ../settings/system/storage.rst:2 -msgid "Storage" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Phone" msgstr "" -#: ../settings/system/storage.rst:6 -msgid "" -"Here you can define where Zammad stores attachments for tickets and the " -"knowledge base. By default, we're writing to the ``Database`` - you can " -"switch to ``Filesystem`` or ``Simple Storage (S3)`` at any time. In this " -"case please have a look on the following instructions." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.phone}``" msgstr "" -#: ../settings/system/storage.rst:11 -msgid "" -"If you have a busy Zammad instance, we strongly encourage you to use " -"filesystem storage instead of \"Database\". This will greatly improve system " -"performance (de-crease database load and size)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > VIP" msgstr "" -#: ../settings/system/storage.rst:19 -msgid "Database" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.vip}``" msgstr "" -#: ../settings/system/storage.rst:17 -msgid "" -"This is the default storage method. The attachments are stored directly in " -"the database. If your Zammad instance grows, we recommend one of the other " -"methods to maintain performance." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Web" msgstr "" -#: ../settings/system/storage.rst:38 -msgid "Filesystem" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.web}``" msgstr "" -#: ../settings/system/storage.rst:22 -msgid "" -"This storage method is recommended for all Zammad instances, especially for " -"those with a higher load. If you choose filesystem, your files are written " -"to ``/opt/zammad/storage/``." +#: ../misc/variables/ticket.rst:1 +msgid "``https://zammad.com`` or empty if not set" msgstr "" -#: ../settings/system/storage.rst:26 -msgid "" -"Moving attachments from \"Database\" to \"Filesystem\" can be run during " -"production use. However, you should consider your framework conditions (e.g. " -"bandwidth, system load in production) to define the right moment." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Pending till" msgstr "" -#: ../settings/system/storage.rst:32 -msgid "**You noticed slow updates of Zammad?**" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.pending_time}``" msgstr "" -#: ../settings/system/storage.rst:34 -msgid "" -"While Zammad is beeing updated, it enforces a recursive \"change " -"owner\" (chown) for this directory. For instances with many files this can " -"be time consuming. To mitigate that you can move your files and create a " -"symlink in ``/opt/zammad/storage/`` to the new directory. Of course you have " -"to make sure on your own that the permissions are always correct." +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not set" msgstr "" -#: ../settings/system/storage.rst:95 -msgid "Simple Storage (S3)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Priority > Name" msgstr "" -#: ../settings/system/storage.rst:41 -msgid "" -"To use the Simple Storage (S3), you have to provide some settings, which " -"can't be accessed in the UI (see instructions below)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.priority.name}``" msgstr "" -#: ../settings/system/storage.rst:44 -msgid "" -"⚠️ Please note that the current implementation is in its early stages and can " -"be modified in the future." +#: ../misc/variables/ticket.rst:1 +msgid "``2 normal``" msgstr "" -#: ../settings/system/storage.rst:47 -msgid "" -"The prerequisite is to have access to a S3-compatible storage and to have " -"all necessary parameters available (which depends on your storage provider; " -"if in doubt, please ask there for help)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > State > Name" msgstr "" -#: ../settings/system/storage.rst:51 -msgid "Steps to configure S3:" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.state.name}``" msgstr "" -#: ../settings/system/storage.rst:53 -msgid "" -"Copy ``config/zammad/storage.yml.dist`` to ``config/zammad/storage.yml``" +#: ../misc/variables/ticket.rst:1 +msgid "``new``, ``open``, ..." msgstr "" -#: ../settings/system/storage.rst:54 -msgid "Edit the copied file in one of the following ways:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Tags" msgstr "" -#: ../settings/system/storage.rst:56 -msgid "" -"Either provide your S3 configuration with one attribute per line like in the " -"upper area of the file" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.tags}``" msgstr "" -#: ../settings/system/storage.rst:58 +#: ../misc/variables/ticket.rst:1 msgid "" -"Or provide your S3 configuration as an URL (which you can find at the end of " -"the file). Note: you can also provide this URL as environment variable (:" -"docs:`see system documentation `) without using this yml-file." +"Currently not available, see `Issue 2769 `_" msgstr "" -#: ../settings/system/storage.rst:62 -msgid "" -"We recommend the deletion of the not used configuration style to avoid " -"inconsistencies." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Title" msgstr "" -#: ../settings/system/storage.rst:65 -msgid "Restart Zammad so the config file / environment variable is loaded" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.title}``" msgstr "" -#: ../settings/system/storage.rst:66 +#: ../misc/variables/ticket.rst:1 msgid "" -"Set the \"Storage Method\" in Zammad to ``Simple Storage (S3)`` in Settings " -"> System > Storage and click on \"Submit\". After that, Zammad checks your " -"configuration and the connection to the service and will raise an error " -"message if something is wrong." +"``My amazing Subject`` (normally subject, can be edited within Interface and " +"thus differ)" msgstr "" -#: ../settings/system/storage.rst:72 -msgid "A very simple storage configuration could look like this:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated at" msgstr "" -#: ../settings/system/storage.rst:85 -msgid "" -"Before setting the storage method to ``Simple Storage (S3)`` (step 4), " -"please make sure to have a working setup." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_at}``" msgstr "" -#: ../settings/system/storage.rst:88 -msgid "" -"You can verify this by running ``rails r 'Rails.logger = Logger.new(STDOUT); " -"pp Store::Provider::S3.ping?'`` in your Zammad directory. If everything is " -"fine, you should see ``true``, else you should see ``false`` and a simple " -"error message." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Address" msgstr "" -#: ../settings/system/storage.rst:93 -msgid "" -"If you installed Zammad through a package manager (rather than from source), " -"replace ``rails r`` with ``zammad run rails r`` above. To learn more, see :" -"docs:`Administration via Console `." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.address}``" msgstr "" -#: ../settings/ticket.rst:4 -msgid "" -"Here you can adjust general ticket settings. Additional ones for the ticket " -"composer interface can be found in the :doc:`/misc/composer`." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Avatar" msgstr "" -#: ../settings/ticket.rst:11 -msgid "Ticket Hook (default: ``Ticket#``)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.avatar(60,60)}``" msgstr "" -#: ../settings/ticket.rst:11 -msgid "The identifier for a ticket; *e.g.,* Ticket#, Call#, MyTicket#." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Department" msgstr "" -#: ../settings/ticket.rst:38 -msgid "Ticket Hook Position (default: ``right``)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.department}``" msgstr "" -#: ../settings/ticket.rst:14 -msgid "" -"With this setting you can decide (if) where to insert the ticket number." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Email" msgstr "" -#: ../settings/ticket.rst:20 -msgid "*Right*" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.email}``" msgstr "" -#: ../settings/ticket.rst:17 -msgid "" -"This setting will add the ticket reference on the right site of the subject." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Fax" msgstr "" -#: ../settings/ticket.rst:20 -msgid "Example: ``Some Subject [Ticket#12345]``" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.fax}``" msgstr "" -#: ../settings/ticket.rst:26 -msgid "*Left*" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Firstname" msgstr "" -#: ../settings/ticket.rst:23 -msgid "" -"This setting will add the ticket reference on the left site of the subject." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.firstname}``" msgstr "" -#: ../settings/ticket.rst:26 -msgid "Example: ``[Ticket#12345] Some Subject``" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Lastname" msgstr "" -#: ../settings/ticket.rst:29 -msgid "*None*" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.lastname}``" msgstr "" -#: ../settings/ticket.rst:29 -msgid "This will completely remove ticket references from the subject." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Login" msgstr "" -#: ../settings/ticket.rst:33 -msgid "" -"Please ensure to take a look at :doc:`/channels/email/settings` within the " -"email channel to ensure you have at least one reference that helps Zammad to " -"assign follow-ups correctly." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.login}``" msgstr "" -#: ../settings/ticket.rst:37 -msgid "" -"Disabling this and not setting up any further follow up search will lead to " -"unexpected results!" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Mobile" msgstr "" -#: ../settings/ticket.rst:65 -msgid "" -"Ticket Last Contact Behaviour (default: ``Use the start time of the last " -"customer thread (which may consist of multiple articles).``)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.mobile}``" msgstr "" -#: ../settings/ticket.rst:41 -msgid "" -"This setting changes the way Zammad updates the ``Last Contact`` value of a " -"ticket. This is fairly important for overviews and what you expect upon " -"ticket updates of a customer." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Note" msgstr "" -#: ../settings/ticket.rst:52 -msgid "" -"Use the start time of the last customer thread (which may consist of " -"multiple articles)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.note}``" msgstr "" -#: ../settings/ticket.rst:46 -msgid "" -"If this option is chosen, Zammad will update the last updated value just " -"once if a customer replies. After that, Zammad will wait for an agent to " -"react." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Phone" msgstr "" -#: ../settings/ticket.rst:50 -msgid "" -"This comes in handy if you want to work tickets in the order of their first " -"update. This will not change ticket orders if customers decide to \"bump\" " -"the ticket affected." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.phone}``" msgstr "" -#: ../settings/ticket.rst:57 -msgid "Use the time of the very last customer article." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > VIP" msgstr "" -#: ../settings/ticket.rst:55 -msgid "" -"When setting this option, Zammad will always update the last updated value. " -"This means that if ordering by ``Last Update``, ticket orders will change if " -"customers \"bump\" the ticket." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.vip}``" msgstr "" -#: ../settings/ticket.rst:64 -msgid "Last contact value used on :doc:`/manage/overviews`" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Web" msgstr "" -#: ../settings/ticket.rst:65 -msgid "Last contact value used on :doc:`/manage/trigger`" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.web}``" msgstr "" -#: ../settings/ticket.rst:88 -msgid "" -"Ticket Organization Reassignment (default: ``Update the most recent tickets." -"``)" +#: ../settings/branding.rst:10 +msgid "Product Name" msgstr "" -#: ../settings/ticket.rst:68 +#: ../settings/branding.rst:7 msgid "" -"This setting changes the way Zammad updates the organization field of the " -"tickets whenever the primary organization of a user is changed." -msgstr "" - -#: ../settings/ticket.rst:74 -msgid "Update the most recent tickets." +"Defines the name of the application, shown in the web interface, tabs and " +"title bar of the web browser." msgstr "" -#: ../settings/ticket.rst:72 -msgid "" -"If this option is chosen, Zammad will update the 100 most recent tickets " -"where the user is the ticket customer. The ticket organization field will be " -"automatically set to the new primary organization of the user." +#: ../settings/branding.rst:10 +msgid "Default value: ``Zammad Helpdesk``" msgstr "" -#: ../settings/ticket.rst:88 -msgid "Do not update any tickets." +#: ../settings/branding.rst:13 +msgid "Will be shown in the app and is included in email footers." msgstr "" -#: ../settings/ticket.rst:77 -msgid "" -"When choosing this option, Zammad will not update any tickets when the " -"user's primary organization is changed." +#: ../settings/branding.rst:19 +msgid "Logo" msgstr "" -#: ../settings/ticket.rst:80 -msgid "**Use with care!**" +#: ../settings/branding.rst:16 +msgid "Defines the logo of the application, shown in the login page of Zammad." msgstr "" -#: ../settings/ticket.rst:82 +#: ../settings/branding.rst:18 msgid "" -"Using this option may lead to inconsistencies in the system as the ticket " -"organization may become decoupled from the ticket customer." +"Ensure to hit the \"Submit\" button after uploading the logo. Otherwise your " +"change will not be saved." msgstr "" -#: ../settings/ticket.rst:85 +#: ../settings/branding.rst:22 msgid "" -"However, you may use this option if you wish to maintain :ref:`the shared " -"access ` to the ticket for all organization " -"members of the original organization of the customer." +"Allows to set the default language of the Zammad instance. The here defined " +"locale mostly acts as a fallback for:" msgstr "" -#: ../settings/ticket.rst:110 -msgid "Ticket Number Format (default: ``Increment (SystemID.Counter)``)" +#: ../settings/branding.rst:25 +msgid "user preferences (if Zammad can't detect the users locale)" msgstr "" -#: ../settings/ticket.rst:94 -msgid "" -"This setting defines the way Zammad's ticket number will look. Changing this " -"setting in production will cause follow up detection to fail." +#: ../settings/branding.rst:26 +msgid "CSV output (reporting, time accounting)" msgstr "" -#: ../settings/ticket.rst:102 -msgid "Increment (SystemID.Counter)" +#: ../settings/branding.rst:30 +msgid "Define the timezone of your Zammad installation." msgstr "" -#: ../settings/ticket.rst:98 +#: ../settings/branding.rst:32 msgid "" -"The increment value contains the SystemID (automatically generated during " -"installation) and a increment which counts up with every new Ticket. The " -"increment will automatically get another digit if needed." +"This does not have any effect on timings for your agents or how Zammad " +"stores date and time values." msgstr "" -#: ../settings/ticket.rst:102 -msgid "Examples: ``1010138``, ``1010139``" +#: ../settings/branding.rst:35 +msgid "Changing this value has direct consequences on the following areas:" msgstr "" -#: ../settings/ticket.rst:110 -msgid "Date (Year.Month.Day.SystemID.Counter)" +#: ../settings/branding.rst:37 +msgid ":doc:`/manage/scheduler` tasks" msgstr "" -#: ../settings/ticket.rst:105 -msgid "" -"This version of the ticket number is fairly long. However, because it " -"contains the date of ticket creation, it also allows you to see when the " -"ticket has been created. You may feel familiar with this number format if " -"you've worked with OTRS already." +#: ../settings/branding.rst:38 +msgid "search indexing (and thus reporting)" msgstr "" -#: ../settings/ticket.rst:110 -msgid "Examples: ``201206231010138``, ``201206231010139``" +#: ../settings/branding.rst:40 +msgid "calendar subscriptions" msgstr "" -#: ../settings/ticket.rst:137 -msgid "OPTIONS" +#: ../settings/branding.rst:41 +msgid "browser printing" msgstr "" -#: ../settings/ticket.rst:113 +#: ../settings/branding.rst:43 msgid "" -"The below options allow you to further customize your ticket number. The " -"availability of options differ depending of the chosen ticket number format " -"above." +"Please note that some of above are fallbacks in case Zammad could not detect " +"the agents timezone correctly." msgstr "" -#: ../settings/ticket.rst:122 -msgid "Checksum (default: ``no``)" +#: ../settings/branding.rst:77 +msgid "Pretty Date" msgstr "" -#: ../settings/ticket.rst:118 +#: ../settings/branding.rst:47 msgid "" -"If set to yes, we'll built a checksum to further \"unique\" the ticket " -"number of your system. If you're dealing with many other ticket systems this " -"might help to prevent false positive follow up detection on tickets." +"This setting allows you to define how Zammad should display time stamps " +"within the interface to all users." msgstr "" -#: ../settings/ticket.rst:122 -msgid "This will also add another digit to the ticket number." +#: ../settings/branding.rst:50 +msgid "" +"This does not have any effect on how Zammad returns e.g. time values via " +"variables." msgstr "" -#: ../settings/ticket.rst:137 -msgid "Min. size of Number (default: ``5``)" +#: ../settings/branding.rst:77 +msgid "Choose in between the following options:" msgstr "" -#: ../settings/ticket.rst:125 -msgid "" -"This setting defines the minimum length of your ticket number. If your " -"counter is not yet high enough, Zammad will fill the number with zeros to " -"ensure the wanted length." +#: ../settings/branding.rst:64 +msgid "relative" msgstr "" -#: ../settings/ticket.rst:129 +#: ../settings/branding.rst:55 msgid "" -"Please note that the minimum length is ``3`` (SystemID + at least one digit " -"if below 10). Also, if the length is no longer long enough, the number will " -"automatically get one digit longer. Ticket-Numbers **do not overflow**, thus " -"it's save to keep it at 5 or set it lower if wanted." +"This timestamp shows a relative time span until it switches to a date. Over " +"time, it will change as follows:" msgstr "" -#: ../settings/ticket.rst:135 -msgid "" -"This option is only available if ticket number format is set to " -"``Increment``!" +#: ../settings/branding.rst:58 +msgid "just now" msgstr "" -#: ../settings/ticket.rst:142 -msgid "Auto-Assignment" +#: ../settings/branding.rst:59 +msgid "5 minutes ago" msgstr "" -#: ../settings/ticket.rst:144 -msgid "" -"In a larger Zammad environment, it happens that several agents open the same " -"ticket at the same time. Although collision detection is then effective, the " -"efficiency of processing can be increased by means of the automatic " -"assignment of tickets when a ticket is opened." +#: ../settings/branding.rst:60 +msgid "3 days 1 hour ago" msgstr "" -#: ../settings/ticket.rst:149 -msgid "" -"The automatic assignment of tickets can be activated and configured in the " -"admin area under Settings > Ticket > Auto Assignment." +#: ../settings/branding.rst:61 +msgid "``03/04/2022``" msgstr "" -#: ../settings/ticket.rst:152 -msgid "" -"The auto assignment only works if the ticket has no owner yet. By default, " -"the agent can always reset the ticket owner to ``-`` if needed." +#: ../settings/branding.rst:63 +msgid "Hovering the timestamp helps, you'll always get a clean timestamp then." msgstr "" -#: ../settings/ticket.rst:155 -msgid "" -"If you want to use this function for only specific tickets, you can " -"configure the conditions accordingly to meet your requirement. By default " -"the condition affects all tickets with the state ``open``." +#: ../settings/branding.rst:71 +msgid "absolute" msgstr "" -#: ../settings/ticket.rst:161 +#: ../settings/branding.rst:67 msgid "" -"If you need to exclude users (e.g. a group leader), you can search and " -"select the desired agents in the ``Exception Users`` list. The search " -"function in this area is only effective, if you have too many agents to " -"display at once to help you with the configuration." +"This timestamp always includes the week day. For one week after creation, " +"the timestamp will not contain the date itself: Thursday 18:35." msgstr "" -#: ../settings/ticket.rst:167 -msgid "Notifications" +#: ../settings/branding.rst:71 +msgid "After a week it will switch to: ``Friday 4. Mar 16:00``." msgstr "" -#: ../settings/ticket.rst:191 -msgid "Default Notifications" +#: ../settings/branding.rst:76 +msgid "timestamp" msgstr "" -#: ../settings/ticket.rst:170 +#: ../settings/branding.rst:74 msgid "" -"This setting allows you to configure the default ticket notifications that " -"will be applied to all new agent users (incl. users who were just assigned " -"agent role). Simply change the notification matrix to desired state and " -"press **Save**." +"This will cause Zammad to show a complete timestamp according to your locale " +"defaults. For English this could be e.g. ``2022/12/03 2:40 pm`` or for " +"German e.g. ``12.03.2022 14:40``." msgstr "" -#: ../settings/ticket.rst:175 -msgid "" -"In case an agent already exists, their ticket notification preferences will " -"be preserved. Optionally, you can also **Apply current defaults to all " -"agents**." +#: ../settings/branding.rst:78 +msgid "Default setting: ``relative``." msgstr "" -#: ../settings/ticket.rst:181 -msgid "" -"**Potential time-consuming action:** Applying default ticket notifications " -"to all agent users may take some time to complete, be patient! The exact " -"time will depend on the size of your system and the number of agents." +#: ../settings/security.rst:2 +msgid "Security" msgstr "" -#: ../settings/ticket.rst:185 +#: ../settings/security.rst:4 msgid "" -"**Active agents only!** When current default ticket notifications are " -"applied, only active agent users are considered. In case an agent is re-" -"activated *after* this action, they will still have the old notification " -"configuration." +"For your overview we split each tab within security settings into its own " +"page:" msgstr "" -#: ../settings/ticket.rst:190 +#: ../settings/security/base.rst:2 ../settings/system/base.rst:2 +#: ../settings/ticket.rst:8 +msgid "Base" +msgstr "" + +#: ../settings/security/base.rst:5 +msgid "New User Accounts" +msgstr "" + +#: ../settings/security/base.rst:9 msgid "" -"In case you want to go back to the initial state of ticket notifications, " -"you can click on **Reset to default** button." +"Activates the `register as a new customer` function on the login page. If " +"set to ``no`` only administrators or agents can create new accounts manually." msgstr "" -#: ../settings/ticket.rst:194 ../settings/ticket.rst:196 -msgid "Duplicate Detection" +#: ../settings/security/base.rst:13 ../settings/security/base.rst:38 +#: ../settings/security/base.rst:66 +msgid "Default setting: ``yes``" msgstr "" -#: ../settings/ticket.rst:236 ../settings/ticket.rst:238 -msgid "Detect Duplicate Ticket Creation" +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"New User Accounts\" setting" msgstr "" -#: ../settings/ticket.rst:197 ../settings/ticket.rst:199 +#: ../settings/security/base.rst:22 msgid "" -"This setting turns on the duplicate ticket detection mechanism during ticket " -"creation. If similar tickets are found in the system, a suitable warning " -"will be shown to the user trying to create a ticket." +"Deactivation of above function **does not** deactivate automatic account " +"creation! This means: If a user writes e.g. an email to Zammad and has no " +"account yet, Zammad will automatically create the account. User accounts are " +"a direct dependency of tickets and thus technically mandatory." msgstr "" -#: ../settings/ticket.rst:204 ../settings/ticket.rst:206 -msgid "A Sample Duplicate Ticket Warning" +#: ../settings/security/base.rst:29 +msgid "Lost Password" msgstr "" -#: ../settings/ticket.rst:206 ../settings/ticket.rst:208 +#: ../settings/security/base.rst:33 msgid "" -"You can choose which ticket attributes will be matched by selecting them in " -"**Attributes to compare** field. Only if the ticket attribute value provided " -"by the user in the ticket create form is *equal* with the attribute in an " -"existing ticket, the warning will be shown." +"Activates the `lost password` function on the login page. If set to ``no`` " +"only administrators may change the user's password - users may update their " +"own password if they're still logged in and they have the required :doc:" +"`permission `." msgstr "" -#: ../settings/ticket.rst:211 ../settings/ticket.rst:213 -msgid "**Warning title** and **Warning message** are configurable as well." +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"Lost Password\" setting" msgstr "" -#: ../settings/ticket.rst:213 ../settings/ticket.rst:215 +#: ../settings/security/base.rst:49 msgid "" -"You can limit the detection only to certain user roles. By default, only " -"agents will see the warning." +"With third party authentications - but especially LDAP - you may want to " +"disable this function. Zammad **will not** change third party login " +"passwords and instead set or change the local password!" msgstr "" -#: ../settings/ticket.rst:216 ../settings/ticket.rst:218 -msgid "" -"If you don't want to show the matched tickets as part of the warning, you " -"can set **Show matching ticket(s) in the warning** setting to *no*." +#: ../settings/security/base.rst:56 +msgid "Password Login" msgstr "" -#: ../settings/ticket.rst:219 ../settings/ticket.rst:221 +#: ../settings/security/base.rst:60 msgid "" -"By default, **Permission level for looking up ticket** is set to *User*, " -"which means user permissions will be honored during sarch. The user will " -"see the warning only if tickets they have access to are matched. " -"Alternatively, you can set this setting to *System*, in which case the " -"search will happen within *all* tickets in the system, regardless of user " -"permissions." +"Activates the username & password login by default and if no third-party " +"login is activated. Disabling password login on the Zammad login page only " +"takes effect if you enable any :doc:`third-party`." msgstr "" -#: ../settings/ticket.rst:225 ../settings/ticket.rst:227 -msgid "**🦺 Safety first!**" +#: ../settings/security/base.rst:64 +msgid "See :doc:`third-party` for supported third-party logins." msgstr "" -#: ../settings/ticket.rst:227 ../settings/ticket.rst:229 -msgid "" -"Even if the permission level is set to *System*, the user will not be shown " -"the tickets they don't have access to in the warning, even if they match." +#: ../settings/security/base.rst:0 +msgid "Figure showing de-activated \"Password Login\" setting" msgstr "" -#: ../settings/ticket.rst:231 ../settings/ticket.rst:233 +#: ../settings/security/base.rst:77 msgid "" -"However, just the confirmation about the existence of the tickets in the " -"system may be considered an unwanted information disclosure. Use this option " -"carefully!" +"To help administrators to overcome \"login issues\", Zammad automatically " +"offers a password request for administrator users. This allows you to adjust " +"Third-Party applications even if the login does no longer work!" msgstr "" -#: ../settings/ticket.rst:235 ../settings/ticket.rst:237 -msgid "" -"Finally, you can configure between matching within **All tickets** or **Open " -"tickets** only by setting **Match tickets in following states**. Depending " -"on the current ticket state, a ticket may or not be matched." +#: ../settings/security/base.rst:84 +msgid "Session Timeout" msgstr "" -#: ../system/core-workflows.rst:2 -msgid "Core Workflows" +#: ../settings/security/base.rst:86 +msgid "" +"All settings below by default are set to ``4 weeks``. Session Timeout " +"defines the life time of a users session. As soon as it's reached, Zammad " +"will automatically log off the session in question." msgstr "" -#: ../system/core-workflows.rst:4 +#: ../settings/security/base.rst:91 msgid "" -"Core Workflows allow you to adjust object attributes in many ways. For " -"example:" +"Zammad takes the highest value set assigned for the user based on the " +"permissions." msgstr "" -#: ../system/core-workflows.rst:7 -msgid "show / hide fields" +#: ../settings/security/base.rst:94 +msgid "``admin``" msgstr "" -#: ../system/core-workflows.rst:8 -msgid "adjust mandatory setting" +#: ../settings/security/base.rst:96 +msgid "``ticket.customer``" msgstr "" -#: ../system/core-workflows.rst:9 -msgid "manipulate available options" +#: ../settings/security/base.rst:97 +msgid "``default`` (fallback if user doesn't have above permissions set)" msgstr "" -#: ../system/core-workflows.rst:11 +#: ../settings/security/base.rst:99 msgid "" -"With this, you can provide exactly the information your users really need!" +"All settings act independently from each other allowing you to disable the " +"timeouts for e.g. admins, but not agents." msgstr "" -#: ../system/core-workflows.rst:15 -msgid "" -"If the pre-defined :doc:`/system/objects` are not enough, please add them " -"beforehand." +#: ../settings/security/base.rst:115 +#: ../system/integrations/checkmk/api-reference.rst:13 +msgid "Example" msgstr "" -#: ../system/core-workflows.rst:17 -msgid "" -"If you experience slow or unreliable field updates, please see :ref:`Core " -"Workflow Ajax Modus `" +#: ../settings/security/base.rst:107 +msgid "Let's suppose you configured the following session timeouts" msgstr "" -#: ../system/core-workflows.rst:22 -msgid "" -"This is a very enhanced functionality and can cause unexpected UI behavior. " -"Please ensure to test your use cases after configuration to reduce surprises." +#: ../settings/security/base.rst:104 +msgid "default: 3 weeks" msgstr "" -#: ../system/core-workflows.rst:None -msgid "Dialogue for adding a new workflow" +#: ../settings/security/base.rst:105 +msgid "admin: 2 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:2 -msgid "Core Workflow Condition Operators" +#: ../settings/security/base.rst:106 +msgid "ticket.agent: 4 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:4 -msgid "" -"You might know that there is a separate section for explaining :doc:" -"`condition operators `. Head over there to " -"see a detailed explanation of many conditions and operators." +#: ../settings/security/base.rst:107 +msgid "ticket.customer: 1 week" msgstr "" -#: ../system/core-workflows/condition-operators.rst:8 -msgid "" -"Due to differences to other places in Zammad which are also using conditions " -"(e.g. triggers), you can find a dedicated description of operators for core " -"workflows below." +#: ../settings/security/base.rst:115 +msgid "This results in the following situations" msgstr "" -#: ../system/core-workflows/condition-operators.rst:12 -msgid "" -"Be aware that the availability of the operators depends on the selected " -"attribute and its field type. Some of the operators may only be available " -"for system attributes (e.g. for \"tags\", \"active\")." +#: ../settings/security/base.rst:110 +msgid "a user with ``admin`` permission will have a timeout of 2 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:20 -msgid "Operator" +#: ../settings/security/base.rst:111 +msgid "" +"a user with ``admin`` and ``ticket.agent`` permissions will have a timeout " +"of 2 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:22 -msgid "after (absolute)" +#: ../settings/security/base.rst:113 +msgid "" +"a user with ``ticket.customer`` permission will have a timeout of 1 week" msgstr "" -#: ../system/core-workflows/condition-operators.rst:23 -msgid "Matches if a date/time is after a specific point in time." +#: ../settings/security/base.rst:115 +msgid "" +"a user with neither ``admin``, ``ticket.agent`` nor ``ticket.customer`` " +"permissions will have a timeout of 3 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:24 -msgid "after (relative)" +#: ../settings/security/password.rst:4 +msgid "" +"This section allows you to define password requirements for the local user " +"accounts." msgstr "" -#: ../system/core-workflows/condition-operators.rst:25 -msgid "Matches if a time span after a specified event has passed." +#: ../settings/security/password.rst:9 +msgid "" +"Zammad does **not** allow you to change your LDAP password, instead, it will " +"set a password in its local database which might confuse your users. This " +"might be addressed in the future by `#1169 `_." msgstr "" -#: ../system/core-workflows/condition-operators.rst:26 -msgid "before (absolute)" +#: ../settings/security/password.rst:14 +msgid "**Exception for admins**" msgstr "" -#: ../system/core-workflows/condition-operators.rst:27 -msgid "Matches if a date/time is before a specific point in time." +#: ../settings/security/password.rst:16 +msgid "" +"Please note that below password policies *do not* affect administrators " +"setting passwords on user accounts. While this seems strange and not safe we " +"believe that an administrator knowing an user's password is insecure as well." msgstr "" -#: ../system/core-workflows/condition-operators.rst:28 -msgid "before (relative)" +#: ../settings/security/password.rst:21 +msgid "The suggested workflow is either:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:29 -msgid "Matches if a time span after a specified event has not passed." +#: ../settings/security/password.rst:23 +msgid "" +"to use third party logins to not require local passwords at all **- or -**" msgstr "" -#: ../system/core-workflows/condition-operators.rst:30 -msgid "contains" +#: ../settings/security/password.rst:25 +msgid "to require your *user to reset the password* upon first login." msgstr "" -#: ../system/core-workflows/condition-operators.rst:31 -msgid "Matches if a specified value is present." +#: ../settings/security/password.rst:27 +msgid "" +"This way administrators are not required to set a user's password at all!" msgstr "" -#: ../system/core-workflows/condition-operators.rst:33 -msgid "Matches if all of the specified values are present." +#: ../settings/security/password.rst:31 +msgid "Maximum Failed Logins" msgstr "" -#: ../system/core-workflows/condition-operators.rst:35 -msgid "Matches if none of the specified values are present." +#: ../settings/security/password.rst:33 +msgid "" +"You can choose a value between ``4`` and ``20``. This defines how often a " +"login to a user account may fail until Zammad will lock it. Your users can " +"always use the \"forgot password\" function to change their password and " +"unlock their account." msgstr "" -#: ../system/core-workflows/condition-operators.rst:36 -msgid "contains not" +#: ../settings/security/password.rst:38 +msgid "The default value is ``10``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:37 -msgid "Matches if a specified value is not present." +#: ../settings/security/password.rst:42 +msgid "Beside changing the user's password, you can also unlock accounts via" msgstr "" -#: ../system/core-workflows/condition-operators.rst:39 -msgid "Matches if one specified value is present." +#: ../settings/security/password.rst:44 +msgid ":ref:`user management list `" msgstr "" -#: ../system/core-workflows/condition-operators.rst:41 -msgid "Matches if one specified value is not present." +#: ../settings/security/password.rst:45 +msgid ":docs:`console `" msgstr "" -#: ../system/core-workflows/condition-operators.rst:42 -msgid "does not match regex" +#: ../settings/security/password.rst:46 +msgid ":docs:`API `" msgstr "" -#: ../system/core-workflows/condition-operators.rst:43 -msgid "Matches if content doesn't fit to regex rule." +#: ../settings/security/password.rst:50 +msgid "Failed logins via LDAP no longer lock accounts." msgstr "" -#: ../system/core-workflows/condition-operators.rst:44 -msgid "ends with" +#: ../settings/security/password.rst:53 +msgid "2 Lower Case And 2 Upper Case Characters" msgstr "" -#: ../system/core-workflows/condition-operators.rst:45 -msgid "Matches if content ends with specified value." +#: ../settings/security/password.rst:55 +msgid "" +"You can add complexity to passwords by enforcing at least 2 upper and lower " +"case characters." msgstr "" -#: ../system/core-workflows/condition-operators.rst:46 -msgid "ends with one of" +#: ../settings/security/password.rst:58 ../settings/security/password.rst:83 +msgid "The default value is ``no``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:47 -msgid "Matches if content ends with one of the specified values." +#: ../settings/security/password.rst:62 +msgid "Minimum Length" msgstr "" -#: ../system/core-workflows/condition-operators.rst:48 -msgid "from (relative)" +#: ../settings/security/password.rst:64 +msgid "" +"This defines the minimum password length required for users to provide (from " +"``4`` to ``20``)." msgstr "" -#: ../system/core-workflows/condition-operators.rst:49 -msgid "Matches if date/time is after a period of time after an event." +#: ../settings/security/password.rst:67 +msgid "The default value is ``6``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:51 -msgid "Matches if content is equal to a specified value." +#: ../settings/security/password.rst:71 +msgid "Digit Required" msgstr "" -#: ../system/core-workflows/condition-operators.rst:52 -msgid "is any of" +#: ../settings/security/password.rst:73 +msgid "This enforces your users to use at least one digit within the password." msgstr "" -#: ../system/core-workflows/condition-operators.rst:53 -msgid "Matches if content is equal to any of specified values." +#: ../settings/security/password.rst:75 +msgid "The default value is ``yes``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:54 -msgid "is modified" +#: ../settings/security/password.rst:78 +msgid "Special Character Required" msgstr "" -#: ../system/core-workflows/condition-operators.rst:55 -msgid "Matches if content is modified." +#: ../settings/security/password.rst:80 +msgid "" +"This setting allows you to improve your password quality even more by " +"enforcing the password to contain at least one special character." msgstr "" -#: ../system/core-workflows/condition-operators.rst:57 -#: ../system/core-workflows/condition-operators.rst:61 -msgid "True from the moment of changing content until form submit." +#: ../settings/security/ssl-certificates.rst:2 +msgid "SSL Certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:58 -msgid "is modified to" +#: ../settings/security/ssl-certificates.rst:7 +msgid "" +"Zammad offers the possibility to upload custom certificates and custom " +"Certificate Authority (CA) certificates. This can be useful if you want to " +"connect Zammad the secure way to other systems which are using custom " +"certificates." msgstr "" -#: ../system/core-workflows/condition-operators.rst:59 -msgid "Matches if content is modified to a specific value." +#: ../settings/security/ssl-certificates.rst:12 +msgid "" +"An example usecase might be: You have an internal LDAP server that is not " +"accessible from the internet, and you want a SSL-encrypted connection, using " +"a custom certificate." msgstr "" -#: ../system/core-workflows/condition-operators.rst:62 -msgid "is none of" +#: ../settings/security/ssl-certificates.rst:19 +msgid "" +"You should have an existing custom certificate file and/or a custom CA " +"certificate file, which you want to add to Zammad. As filetype ``.crt`` is " +"supported and the certificate format has to be PEM (Base64 ASCII)." msgstr "" -#: ../system/core-workflows/condition-operators.rst:63 -msgid "Matches if content is none of any specified values." +#: ../settings/security/ssl-certificates.rst:25 +msgid "" +"When you import a custom CA certificate, all certificates generated with " +"this are trusted. This can be useful if you have more than one system/" +"certificate you want to connect to and the certificates are issued from the " +"same custom CA." msgstr "" -#: ../system/core-workflows/condition-operators.rst:65 -msgid "Matches if content is not equal to a specified value." +#: ../settings/security/ssl-certificates.rst:31 +msgid "Add a Certificate" msgstr "" -#: ../system/core-workflows/condition-operators.rst:67 -msgid "Matches if content is present." +#: ../settings/security/ssl-certificates.rst:33 +msgid "" +"To add a custom certificate or a custom CA certificate, head over to the " +"Admin panel > Settings > Security > SSL Certificates. Here you can find a " +"\"Add SSL Certificate\" button. In the dialog you can either select a " +"certificate file or paste the content of the certificate:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:68 -msgid "just changed" +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate adding dialog" msgstr "" -#: ../system/core-workflows/condition-operators.rst:69 -msgid "Matches if content has changed." +#: ../settings/security/ssl-certificates.rst:43 +msgid "" +"After selecting a file or pasting the content of the certificate, click on " +"the \"Add\" button to finally upload it to Zammad. Then, the certificates " +"are immediately effective, no restart or similar required." msgstr "" -#: ../system/core-workflows/condition-operators.rst:71 -#: ../system/core-workflows/condition-operators.rst:75 +#: ../settings/security/ssl-certificates.rst:49 msgid "" -"Only true for the moment of changing content until next form field action/" -"click." +"Please note that only single certificate files are supported. That means if " +"you want to import a certificate / CA certificate, it must contain **only " +"one** certificate." msgstr "" -#: ../system/core-workflows/condition-operators.rst:72 -msgid "just changed to" +#: ../settings/security/ssl-certificates.rst:54 +msgid "Certificate Overview" msgstr "" -#: ../system/core-workflows/condition-operators.rst:73 -msgid "Matches if content has changed to a specified value." +#: ../settings/security/ssl-certificates.rst:56 +msgid "" +"After you added a certificate, you can see a table with information for each " +"added certificate:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:76 -msgid "matches regex" +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing table of added certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:77 -msgid "Matches if value fits to regex rule." -msgstr "" - -#: ../system/core-workflows/condition-operators.rst:79 -msgid "Matches if no content is present." -msgstr "" - -#: ../system/core-workflows/condition-operators.rst:80 -msgid "starts with" +#: ../settings/security/ssl-certificates.rst:64 +msgid "" +"Here you can download the certificate or delete it, if you don't need it " +"anymore." msgstr "" -#: ../system/core-workflows/condition-operators.rst:81 -msgid "Matches if content starts with specified value." +#: ../settings/security/ssl-certificates.rst:68 +msgid "Deleting Certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:82 -msgid "starts with one of" +#: ../settings/security/ssl-certificates.rst:70 +msgid "" +"If you want to delete a specific certificate, you can do it by clicking on " +"the menu in the actions column and selecting delete:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:83 -msgid "Matches if content starts with one of the specified values." +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate deletion button" msgstr "" -#: ../system/core-workflows/condition-operators.rst:84 -msgid "till (relative)" +#: ../settings/security/ssl-certificates.rst:79 +msgid "Downloading Certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:85 -msgid "Matches if date/time is before a period of time before an event." +#: ../settings/security/ssl-certificates.rst:81 +msgid "" +"If you want to download your certificates, you can do this as well via " +"corresponding action buttons." msgstr "" -#: ../system/core-workflows/condition-operators.rst:86 -msgid "today" +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate download button" msgstr "" -#: ../system/core-workflows/condition-operators.rst:87 -msgid "Matches if date/time is today." +#: ../settings/security/third-party.rst:13 +msgid "Login Providers" msgstr "" -#: ../system/core-workflows/condition-operators.rst:88 -msgid "within last (relative)" +#: ../settings/security/third-party.rst:2 +msgid "Third-Party Applications" msgstr "" -#: ../system/core-workflows/condition-operators.rst:89 +#: ../settings/security/third-party.rst:4 msgid "" -"Matches if date/time content is within specified period of time before now." +"Third party authentication is a great way to help your users to login to " +"Zammad more easily. If the account is yet unknown, Zammad will create a new " +"user automatically, without the user needed to interact (e.g. type in his " +"name). Another big advantage of this feature is that your user doesn't need " +"to remember another password." msgstr "" -#: ../system/core-workflows/condition-operators.rst:91 -msgid "within next (relative)" +#: ../settings/security/third-party.rst:10 +msgid "" +"You can deactivate logging in via :ref:`security_password_login` if any of " +"the mentioned authentication providers are enabled in your instance." msgstr "" -#: ../system/core-workflows/condition-operators.rst:92 +#: ../settings/security/third-party.rst:27 msgid "" -"Matches if date/time content is within specified period of time after now." +"We're currently missing documentation for the following login providers:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:2 -msgid "How do they work?" +#: ../settings/security/third-party.rst:29 +msgid "LinkedIn" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:4 -msgid "" -"Core Workflows are executed according to their priority. If two workflows " -"have the same priority, they are executed in alphabetical order based on " -"their **name**." +#: ../settings/security/third-party.rst:30 +msgid "Weibo" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:8 -msgid "" -"Because of the way Core Workflows work, all changes to attributes are " -"checked with the application server - please see :doc:`limitations` for " -"possible issues." +#: ../settings/security/third-party.rst:35 +msgid "Automatic Account Link on Initial Logon" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:12 +#: ../settings/security/third-party.rst:37 msgid "" -"Below we're talking about settings that are important and not self-" -"explanatory." +"In general there's two possible options for Zammad on how to deal with " +"already known users as they try to authenticate against a third-party " +"application. By default, Zammad will not automatically link \"unknown\" " +"authentication providers to existing accounts." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:17 +#: ../settings/security/third-party.rst:42 msgid "" -"Choose the object context you want to run the workflow in. This will decide " -"on your available attributes and actions." -msgstr "" - -#: ../system/core-workflows/how-do-they-work.rst:20 -msgid "Ticket objects also have access to the ticket customer." +"This means that the user has to manually link authentication providers to " +"their accounts (for more about this :user-docs:`consult the user " +"documentation `)." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:25 +#: ../settings/security/third-party.rst:46 msgid "" -"Choose in which situation the workflow is applied. Contexts can be combined " -"to avoid duplicate workflows." +"Sometimes this doesn't come in handy as this also means you'll receive error " +"messages about \"email address being in use already\" for (yet) unknown " +"third-party authentication methods." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:30 -msgid "Creation mask" +#: ../settings/security/third-party.rst:50 +msgid "" +"If you want to allow your users to always be able to log in, no matter what, " +"you may want to enable ``Automatic account link on initial logon``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:29 +#: ../settings/security/third-party.rst:None msgid "" -"If selected, your conditions and actions will affect all applicable creation " -"masks." +"Screenshot highlighting the \"Automatic account link on initial logon\"\n" +"setting" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:34 -msgid "Edit mask" +#: ../settings/security/third-party.rst:60 +msgid "Automatic Account Linking Notification" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:33 +#: ../settings/security/third-party.rst:64 msgid "" -"If selected, your conditions and actions will affect all applicable edit " -"masks." +"To improve security and your users awareness, you can enable Zammad to " +"notify your users when a new third-party application has been linked to " +"their account." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:39 +#: ../settings/security/third-party.rst:68 msgid "" -"Zammad differentiates between selected and saved conditions. These can be " -"combined wherever needed." +"This notification is sent out once per third-party application. Zammad does " +"also mention the method used, e.g.: ``Microsoft``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:42 -msgid "**⚠️ Restrict workflows to specific roles if needed!**" +#: ../settings/security/third-party.rst:71 +msgid "By default this setting is not active (set to ``no``)." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:44 +#: ../settings/security/third-party.rst:0 msgid "" -"By default and unless configured in conditions, workflow rules are executed " -"for **all roles**. This also affects your customers!" +"Screenshot showing sample notification mail after initial\n" +"third-party linking" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:50 -msgid "Selected Conditions" +#: ../settings/security/third-party.rst:85 +msgid "" +"This notification is only sent if the account in question already exists. If " +"the login via the third-party also creates the missing account, the " +"notification will be skipped." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:48 -msgid "" -"These conditions are based on form values and match if an appropriate " -"selection is made (e.g. choosing another group in the ticket without " -"saving). This applies for drafts (active selection) and currently saved " -"values." +#: ../settings/security/third-party.rst:89 +msgid "This means it only affects:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:64 -msgid "Saved Conditions" +#: ../settings/security/third-party.rst:91 +msgid "manual account linking within the third-party page of the users profile" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:53 +#: ../settings/security/third-party.rst:92 msgid "" -"These conditions only match if the selected values are stored in the " -"database. It ignores the current value or selection of the field, as long as " -"the changes are not saved (e.g. performing field operations for an existing " -"ticket, which is viewed/opened by an agent)." +"logging into an existing local account by utilizing the *automatic account " +"link on initial logon* functionality" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:60 +#: ../settings/security/third-party.rst:None msgid "" -"Keep in mind that the value has to be available in the situation where you " -"need it. Otherwise the condition won't match." +"Screenshot showing the \"automatic account linking notification\"\n" +"setting" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:63 -msgid "" -"Example: you can't perform any actions with *saved condition* on a ticket in " -"creation, because there are no saved values at that time." +#: ../settings/security/third-party.rst:100 +msgid "No User Creation on Logon" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:66 +#: ../settings/security/third-party.rst:102 msgid "" -"You can find a description of the condition operators for core workflows :" -"doc:`here `." +"By default, Zammad will create a new user account if the user logs in via a " +"third-party application and the account doesn't exist yet." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:72 +#: ../settings/security/third-party.rst:105 msgid "" -"Which actions should we run on the relevant fields? The possible actions " -"depend on the object type. However, usually you can at least change the " -"visibility and whether the field is mandatory." +"If you want to prevent Zammad from creating new accounts on logon, you can " +"disable this feature by setting ``No user creation on logon`` to ``yes``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:76 -msgid "Be aware that actions are not available for **related** context." +#: ../settings/security/third-party.rst:None +msgid "Screenshot showing the \"no user creation on logon\" setting" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:78 +#: ../settings/security/third-party/facebook.rst:4 msgid "" -"**Example:** Let's assume you are working in the ticket context. While you " -"can have customer *conditions*, you *can't adjust* objects with actions in " -"that scope. That's because this wouldn't have any impact on the ticket " -"dialog. Of course all ticket attributes (state, owner, ...) are available." +"It is possible to create a quick login for your helpdesk via Facebook To do " +"so, you need to follow these steps:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:84 +#: ../settings/security/third-party/facebook.rst:9 +msgid "Register Facebook App" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:11 msgid "" -"Please also have a look at our :doc:`limitations` to be safe from surprises." +"Visit [https://developers.facebook.com/apps/] and click on \"Add a new App\"" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:88 -msgid "Available Operators" +#: ../settings/security/third-party/facebook.rst:None +msgid "initial page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:90 -msgid "The availability of operators depends on the object type and scope." +#: ../settings/security/third-party/facebook.rst:17 +msgid "After that enter the app settings" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:94 -msgid "" -"Please note that actions may or may not restrict API based access to " -"attributes. We're displaying the following icons for your overview to " -"understand these limits better:" +#: ../settings/security/third-party/facebook.rst:None +msgid "Create App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:0 -msgid "|api| This icon indicates the action affects the API." +#: ../settings/security/third-party/facebook.rst:22 +msgid "Navigate to \"Settings\" and fill in this infromation" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:163 -msgid "api" +#: ../settings/security/third-party/facebook.rst:None +msgid "App Settings" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:0 -msgid "|ui| This icon indicates the action only affects the web interface." +#: ../settings/security/third-party/facebook.rst:27 +msgid "Navigate to app review and Check \"Make [appname] public?\"" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:167 -msgid "ui" +#: ../settings/security/third-party/facebook.rst:None +msgid "App Review" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:102 -msgid "show |ui|" +#: ../settings/security/third-party/facebook.rst:35 +msgid "Configure Zammad as Facebook App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:102 -msgid "Display the chosen field. Allows setting of values." -msgstr "" - -#: ../system/core-workflows/how-do-they-work.rst:109 -msgid "hide |ui|" +#: ../settings/security/third-party/facebook.rst:37 +msgid "" +"Navigate to \"Admin -> Security -> Third Party Applications\" and enter the " +"App ID and the App Secret. You can find this Key in the Dashbard of your " +"Facebok app." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:105 -msgid "" -"Hide the chosen field. However, it technically still allows setting the " -"field." +#: ../settings/security/third-party/facebook.rst:None +msgid "Zammad Configuration" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:108 +#: ../settings/security/third-party/facebook.rst:44 +#: ../settings/security/third-party/github.rst:43 +#: ../settings/security/third-party/gitlab.rst:46 msgid "" -"Please note that the field is **not** gone and still contains an existing " -"value (if set)! Consider *remove* instead, if you want this field to be gone." +"Now you can link accounts via \"Avatar -> Profile -> Link Accounts\" or " +"login via Zammad login page." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:112 -msgid "remove |ui|" +#: ../settings/security/third-party/github.rst:2 +#: ../system/integrations/github.rst:2 +msgid "GitHub" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:112 -msgid "Entirely removes the field. The field value will not be evaluated." +#: ../settings/security/third-party/github.rst:4 +msgid "" +"It is possible to create a quick login for your helpdesk via GitHub. To " +"activate the quick login you need to enable OAuth for GitHub." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:115 -msgid "set mandatory |ui| |api|" +#: ../settings/security/third-party/github.rst:8 +msgid "Register GitHub App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:115 -msgid "Sets the field to mandatory." +#: ../settings/security/third-party/github.rst:10 +msgid "" +"Visit https://www.github.com/settings/applications/new and enter the app " +"settings. As callback URL enter \"https://zammad_host/auth/github/callback\" " +"where zammad_host has to be replaced with your Zammad FQDN" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:118 -msgid "set optional |ui| |api|" +#: ../settings/security/third-party/github.rst:None +msgid "Register OAuth app on www.github.com" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:118 -msgid "Sets the field to optional." +#: ../settings/security/third-party/github.rst:19 +msgid "Configure Zammad as GitHub App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:124 -msgid "add option |ui| |api|" +#: ../settings/security/third-party/github.rst:21 +msgid "" +"Enter the \"APP ID\" and the \"APP SECRET\" from the GitHub OAUTH " +"Applications Dashboard" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:121 -msgid "Allows adding options to tree selects or selects." +#: ../settings/security/third-party/github.rst:None +msgid "GitHub config in Zammad admin interface" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:123 +#: ../settings/security/third-party/github.rst:28 msgid "" -"You have to use the \"remove option\" before performing this action. It " -"allows you to use *existing* configured values." +"After you configured the GitHub credentials and activated the login method, " +"you should see a new icon on the login page." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:128 -msgid "remove option |ui| |api|" +#: ../settings/security/third-party/github.rst:None +msgid "GitHub logo on login page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:127 +#: ../settings/security/third-party/github.rst:34 msgid "" -"Allows removing options from tree selects or selects. It allows you to use " -"*existing* configured values." +"If you click on the icon you will be redirected to GitHub and see something " +"similar to this:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:134 -msgid "set fixed to |ui| |api|" +#: ../settings/security/third-party/github.rst:None +msgid "GitHub oauth page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:131 -msgid "Reduces the available options by your selection." +#: ../settings/security/third-party/github.rst:40 +#: ../settings/security/third-party/gitlab.rst:42 +msgid "" +"When you grant the access you will be redirected to your Zammad instance and " +"logged in as a customer." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:133 -msgid "" -"This reduces your workflows in terms of *add option* and *remove option*." +#: ../settings/security/third-party/gitlab.rst:2 +msgid "Gitlab" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:137 -msgid "fill in |ui|" +#: ../settings/security/third-party/gitlab.rst:4 +msgid "" +"It is possible to create a quick login for your helpdesk via Gitlab. To " +"activate the quick login you need to enable OAuth for Gitlab." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:137 -msgid "Allows filling in of string and integer fields with your values." +#: ../settings/security/third-party/gitlab.rst:8 +msgid "Register Gitlab App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:141 -msgid "fill in empty |ui|" +#: ../settings/security/third-party/gitlab.rst:10 +msgid "To register an app in Gitlab open your profile and select applications." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:140 +#: ../settings/security/third-party/gitlab.rst:12 msgid "" -"Allows filling in of string and integer fields with your values **if the " -"field is empty**." +"As callback URL enter \"https://zammad-fqdn/auth/gitlab/callback\" where " +"zammad-fqdn has to be replaced with your Zammad FQDN" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:144 -msgid "select |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Register OAuth app on gitlab instance" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:144 -msgid "Select a specific value within a select, tree select or boolean field." +#: ../settings/security/third-party/gitlab.rst:18 +msgid "Just select *read_user* under scopes as in the screenshot and save it." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:153 -msgid "auto select |ui|" +#: ../settings/security/third-party/gitlab.rst:21 +msgid "Configure Zammad as Gitlab App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:147 -msgid "Helps users with tree select and select fields:" +#: ../settings/security/third-party/gitlab.rst:23 +msgid "" +"Enter the \"APP ID\" and the \"APP SECRET\" from the Gitlab OAUTH " +"Applications Dashboard and your Gitlab-URL in the \"SITE\" field." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:149 -msgid "" -"If the field has only one option available for selection and no value yet, " -"the value will be automatically set." +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab config in Zammad admin interface" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:152 +#: ../settings/security/third-party/gitlab.rst:30 msgid "" -"This option only works if you have one value and doesn't work if there is " -"more than one option available." +"After you configured the Gitlab credentials and activated the login method, " +"you should see a new icon on the login page." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:157 -msgid "set readonly |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab logo on login page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:156 +#: ../settings/security/third-party/gitlab.rst:36 msgid "" -"Allows you to display an attribute as read only (which means no changes are " -"possible)." +"If you click on the icon you will be redirected to Gitlab and see something " +"similar to this:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:161 -msgid "unset readonly |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab oauth page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:160 +#: ../settings/security/third-party/google.rst:4 msgid "" -"In case a workflow set the field in question to read only, you can undo this " -"with option above." +"With some easy and fast steps, you can enable Zammad to authenticate your " +"users via Google." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:172 -msgid "Stop after match" +#: ../settings/security/third-party/google.rst:8 +msgid "Register a Google App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:174 +#: ../settings/security/third-party/google.rst:10 msgid "" -"Here you can decide if other workflows are executed after the current one." +"First of all, we need to create a new project - you can skip this step if " +"you already have one." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:176 +#: ../settings/security/third-party/google.rst:15 msgid "" -"If set to ``no`` (default), further workflows will be executed if they match " -"the condition. In this case, it is possible that your actions from the " -"current workflow can be overwritten by another workflow." +"Use this link to create a new project: https://console.cloud.google.com/" +"projectcreate" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:180 +#: ../settings/security/third-party/google.rst:18 msgid "" -"If set to ``yes``, no further worflows will be executed after the current " -"one." +"Now expand the menu, expand \"APIs & Services\" and select \"Credentials\". " +"Go to the tab \"OAuth consent screen\" first and ensure to fill in the " +"requested information - without doing so you can't create credentials!" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:184 -msgid "Priority" +#: ../settings/security/third-party/google.rst:None +msgid "Creating a consent screen" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:186 +#: ../settings/security/third-party/google.rst:25 msgid "" -"You can define the sequence, in which the workflows are executed. The " -"default value is ``500``." +"After filling in and saving the consent screen information, you can go to " +"the \"Credentials\" tab and create new \"OAuth client ID\"-Credentials." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:189 +#: ../settings/security/third-party/google.rst:28 msgid "" -"The workflows are executed in ascending order by their priority. That means " -"lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." +"Fill in the necessary information as follows and replace ``zammad_host`` " +"with your FQDN:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:2 -msgid "Learn by Example" +#: ../settings/security/third-party/google.rst:31 +msgid "**Application type** ``[x] Web application``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:4 -msgid "" -"This page provides some basic examples for Core Workflows. Of course you can " -"build much more complex workflows if needed." +#: ../settings/security/third-party/google.rst:34 +msgid "**Authorized JavaScript origins** ``https://zammad_host/``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:7 +#: ../settings/security/third-party/google.rst:37 msgid "" -"To learn about Core Workflows in detail, first go to :doc:`how-do-they-work`." +"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" +"callback``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:10 -msgid "Group Based Examples" +#: ../settings/security/third-party/google.rst:None +msgid "Adding a new OAuth client ID" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:12 +#: ../settings/security/third-party/google.rst:43 msgid "" -"All following workflows have the same base configurations. The workflow may " -"not use them all." +"After creating the credentials, go to your Zammad installation and navigate " +"to \"Admin > Security > Third Party Applications\" > Google. Enter your " +"Client ID and Client secret here." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:15 -msgid "Groups:" +#: ../settings/security/third-party/google.rst:None +msgid "Zammad" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:20 -msgid "Attributes:" +#: ../settings/security/third-party/google.rst:50 +msgid "After submitting, the login via Google can be used." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:22 -msgid "Category (Single tree selection field, not mandatory, agents only)" +#: ../settings/security/third-party/microsoft.rst:2 +msgid "Microsoft" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:23 +#: ../settings/security/third-party/microsoft.rst:4 msgid "" -"Approved (Boolean field, not mandatory, not shown, ``false`` as default)" +"Zammad's Microsoft connection allows your users with Microsoft accounts to " +"login. This works for Azure users as well and can be an alternative to :doc:" +"`/system/integrations/ldap/index`." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:24 -msgid "Operating System (Text field, not mandatory, not shown)" +#: ../settings/security/third-party/microsoft.rst:10 +msgid "" +"This documentation part does not cover our :doc:`📧 Microsoft 365 email " +"channel `." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:25 -msgid "Software used (Single selection field, not mandatory, not shown)" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screenshot showing Microsoft login button on Zammad login screen." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:68 -msgid "Group specific values and fields" +#: ../settings/security/third-party/microsoft.rst:30 +#: ../settings/security/third-party/microsoft.rst:53 +msgid "Supported account types:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:28 +#: ../settings/security/third-party/microsoft.rst:22 msgid "" -"This workflow set depends on the category field. It reduces the available " -"set of values based on the group selected." +"Please note that Zammad only supports these account types (App dependent):" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:33 -msgid "Workflow 2nd Level group" +#: ../settings/security/third-party/microsoft.rst:35 +msgid "Avatars of signing in users:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:35 +#: ../settings/security/third-party/microsoft.rst:33 msgid "" -"This reduces the category options to ``2nd Level/*``, ``Internal/*`` and " -"``Others``. It also sets further required fields to mandatory and visible." -msgstr "" - -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for 2nd level" +"Zammad currently ignores user avatars. If the user is registered with e.g. " +"Gravatar, Zammad will fetch the avatar from there if enabled. See :doc:" +"`Zammad Image Service ` for more." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:43 -msgid "Workflow Support group" +#: ../settings/security/third-party/microsoft.rst:38 +msgid "Step 1 - Register a Microsoft App for Zammad" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:45 +#: ../settings/security/third-party/microsoft.rst:40 msgid "" -"This reduces the category options to ``Support/*``, ``Internal/*`` and " -"``Others``. It also sets further required fields to visible." -msgstr "" - -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for support" +"Login to the `Microsoft Azure Portal `_ and " +"navigate to App registrations to create a new app. Provide the requested " +"information as follows and register your app." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:53 -msgid "Workflow Sales group" +#: ../settings/security/third-party/microsoft.rst:46 +msgid "Name:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:55 +#: ../settings/security/third-party/microsoft.rst:45 msgid "" -"This reduces the category options to ``Sales/*``, ``Internal/*`` and " -"``Others``." +"Any meaningful name fitting, this name will be displayed to users trying to " +"authenticate with this app." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for sales" +#: ../settings/security/third-party/microsoft.rst:49 +msgid "Choose one of the above mentioned account types (see Limitations)." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:68 -#: ../system/integrations/slack.rst:88 -msgid "The Result" +#: ../settings/security/third-party/microsoft.rst:51 +msgid "" +"The correct account type depends on your use case. If you want to use the " +"authentication internal only, choose the first option. If you're unsure, use " +"the \"Help me choose...\" link." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:63 -msgid "" -"This is what the agent would experience with the above workflows in place." +#: ../settings/security/third-party/microsoft.rst:58 +msgid "Redirect URI (optional):" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 +#: ../settings/security/third-party/microsoft.rst:56 msgid "" -"Workflow shows objects and limits options based on selections on the group" +"Select web and provide your callback URL. The callback URL looks like this: " +"``https://zammad.domain.tld/auth/microsoft_office365/callback``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:90 -msgid "Approval process" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to register a Microsoft app" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:71 -msgid "" -"In this case ``approved`` is visible to agents by default. For this " -"workflow, an additional role ``Approval person`` is required (no further " -"permissions)." +#: ../settings/security/third-party/microsoft.rst:71 +msgid "Within **API permissions** add the following permissions:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that restricts an approval attribute to specific roles" +#: ../settings/security/third-party/microsoft.rst:69 +msgid "``User.Read``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:81 -msgid "" -"This workflow may work best in combination with a :doc:`trigger ` but technically, this is not required." +#: ../settings/security/third-party/microsoft.rst:71 +msgid "Contacts" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:84 -msgid "" -"Select fields may be a better approach because they allow more values than " -"just a simple ``true`` or ``false``." +#: ../settings/security/third-party/microsoft.rst:71 +msgid "``Contacts.Read``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 +#: ../settings/security/third-party/microsoft.rst:73 msgid "" -"Workflow fixes possible values of \"Approved ?\" to a specific selection " -"depending on the users role" +"You can find these permissions within *Microsoft Graph → Delegated " +"permissions*." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:103 -msgid "State dependent mandatory fields" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to add required API permissions" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:93 +#: ../settings/security/third-party/microsoft.rst:80 msgid "" -"This workflow sets ``Category`` to mandatory if the agent wants to set the " -"states ``closed`` or ``pending close`` to enforce categorization." +"Within **Certificates & secrets** create a new client secret. Note down the " +"returned secret **value** for later. **Do not** use the secret ID!" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that sets fields to mandatory on specific states" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to create a new app secret" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 +#: ../settings/security/third-party/microsoft.rst:88 msgid "" -"Workflow sets category field to mandatory upon choosing closed or pending " -"close as state" +"From **Overview** copy your apps *Application (client) ID*. If you're using " +"a single tenant app, please also copy *Directory (tenant) ID*. You now have " +"all required information for Zammad." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:106 -msgid "Manual Ticket Handover Process" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to retreive application client and tenant IDs" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:108 -msgid "This example covers the handover of a ticket from one agent to another:" +#: ../settings/security/third-party/microsoft.rst:98 +msgid "Step 2 - Add App Credentials to Zammad" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:110 +#: ../settings/security/third-party/microsoft.rst:100 msgid "" -"When the ticket owner is modified, a new text field (\"Handover\") shows up " -"for a comment" +"Navigate to Security > Third-party Applications (Tab) within Zammad's admin " +"settings. Scroll down to the section *Authentication via Microsoft* and fill " +"in the required information." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:112 -msgid "" -"This may only be visible when the owner is changed, therefore it has to be " -"hidden in general" +#: ../settings/security/third-party/microsoft.rst:105 +msgid "App ID:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:114 -msgid "The input in this handover text field is mandatory" +#: ../settings/security/third-party/microsoft.rst:105 +msgid "This is your *Application (client) ID*." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:115 -msgid "" -"After submitting changes, the value of the handover field must be added as " -"an note to the ticket (via trigger)" +#: ../settings/security/third-party/microsoft.rst:108 +msgid "App secret:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:121 -msgid "Hiding handover field" +#: ../settings/security/third-party/microsoft.rst:108 +msgid "This is your *client secret* (value)." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Hiding the handover field in core workflows" +#: ../settings/security/third-party/microsoft.rst:113 +msgid "App Tenant ID:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:126 -msgid "Showing handover field and setting it to mandatory" +#: ../settings/security/third-party/microsoft.rst:111 +msgid "" +"**optional** only required for apps that use account type *Accounts in this " +"organizational directory only (Default Directory only - Single tenant).*" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Showing the handover field and set it as mandatory" +#: ../settings/security/third-party/microsoft.rst:115 +msgid "" +"Apply your settings by pressing submit and activate *Authentication via " +"Microsoft*." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:131 -msgid "Trigger writing handover input to a new article" +#: ../settings/security/third-party/microsoft.rst:None +msgid "" +"Screencast showing how to add app credentials and activating the\n" +"authentication method" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Write handover content to a new article" +#: ../settings/security/third-party/saml.rst:2 +msgid "SAML" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:133 +#: ../settings/security/third-party/saml.rst:4 msgid "" -"As a result, the ticket includes an article of the type note which includes " -"the predefined text and the handover comment." +"Connect your SAML (Security Assertion Markup Language) identity provider as " +"a single sign-on (SSO) method." msgstr "" -#: ../system/core-workflows/limitations.rst:6 -msgid "Core Workflows do not replace Triggers" +#: ../settings/security/third-party/saml.rst:7 +msgid "" +"SAML is an open standard for SSO authentication (among other things). Sign-" +"ins are shared across multiple **service providers** and managed by a " +"central **identity provider** (IdP)." msgstr "" -#: ../system/core-workflows/limitations.rst:5 +#: ../settings/security/third-party/saml.rst:11 msgid "" -"Workflows manipulate the behavior of fields. However, they do not set values " -"in fields because of actions." +"In this case, the service provider is Zammad, and the IdP is a software " +"service that you either host or subscribe to (*e.g.,* `Keycloak `_, `Redhat SSO Server `_, `ADFS `_, or `Okta `_)." msgstr "" -#: ../system/core-workflows/limitations.rst:16 -msgid "API calls are only partly affected" +#: ../settings/security/third-party/saml.rst:18 +msgid "" +"This guide assumes you are already using SAML within your organization (i." +"e., that your IdP is fully set up)." msgstr "" -#: ../system/core-workflows/limitations.rst:9 +#: ../settings/security/third-party/saml.rst:21 msgid "" -"Some options affect UI only and thus do not restrict responses and calls." +"Please note: Our instructions are based on connecting Zammad with Keycloak." msgstr "" -#: ../system/core-workflows/limitations.rst:11 -msgid "This affects the following actions:" +#: ../settings/security/third-party/saml.rst:25 +msgid "Step 1: Configure Your IdP" msgstr "" -#: ../system/core-workflows/limitations.rst:13 -msgid "select" +#: ../settings/security/third-party/saml.rst:28 +msgid "Add Zammad as a Client/App" msgstr "" -#: ../system/core-workflows/limitations.rst:14 -msgid "auto select" +#: ../settings/security/third-party/saml.rst:30 +msgid "" +"Import Zammad into your IdP using the XML configuration found at ``https://" +"your.zammad.domain/auth/saml/metadata``." msgstr "" -#: ../system/core-workflows/limitations.rst:15 -msgid "show" +#: ../settings/security/third-party/saml.rst:33 +msgid "" +"If your IdP doesn't support XML import, you will have to configure Zammad as " +"a new client/app manually using the above XML metadata file for reference." msgstr "" -#: ../system/core-workflows/limitations.rst:16 -msgid "hide" +#: ../settings/security/third-party/saml.rst:36 +msgid "For instance, when you see this tag:" msgstr "" -#: ../system/core-workflows/limitations.rst:25 -msgid "Some fields stay unavailable to customers" +#: ../settings/security/third-party/saml.rst:42 +msgid "" +"Set the **Assertion Consumer Service Binding URL** (sometimes also listed as " +"**Valid Redirect URIs**) to ``http://your.zammad.domain/auth/saml/callback``." msgstr "" -#: ../system/core-workflows/limitations.rst:19 -msgid "" -"For technical and security reasons, some default fields (the pale ones you " -"can't edit) stay unavailable for display and usage on customer permissions." +#: ../settings/security/third-party/saml.rst:47 +msgid "Set Up User Attribute Mapping" msgstr "" -#: ../system/core-workflows/limitations.rst:23 +#: ../settings/security/third-party/saml.rst:49 msgid "" -"If you require your customers to change e.g. priorities, please consider " -"using workarounds via :doc:`/system/objects` and :doc:`/manage/trigger`." +"Zammad requests the following user attributes (or “properties”) from the IdP:" msgstr "" -#: ../system/core-workflows/limitations.rst:29 -msgid "Ticket title changes not supported in edit mask" +#: ../settings/security/third-party/saml.rst:51 +msgid "Email address (``email``)" msgstr "" -#: ../system/core-workflows/limitations.rst:28 -msgid "" -"It is currently not possible to perform changes of the ticket title in the " -"edit mask (e.g. renaming, set to read-only)." +#: ../settings/security/third-party/saml.rst:52 +msgid "Full name (``name``)" msgstr "" -#: ../system/core-workflows/limitations.rst:37 -msgid "What is out of scope of Core Workflows?" +#: ../settings/security/third-party/saml.rst:53 +msgid "Given name (``first_name``)" msgstr "" -#: ../system/core-workflows/limitations.rst:32 -msgid "" -"There are some things that would count as workflow but are either done via :" -"doc:`/manage/trigger` or :doc:`/manage/scheduler`." +#: ../settings/security/third-party/saml.rst:54 +msgid "Family name (``last_name``)" msgstr "" -#: ../system/core-workflows/limitations.rst:35 -msgid "Such as (but not limited to):" +#: ../settings/security/third-party/saml.rst:56 +msgid "" +"You may need to set up “mappers” (or “mappings”) to tell your IdP how user " +"attributes in SAML correspond to those in Zammad. For a more detailed " +"breakdown, refer to the XML metadata file referenced in the previous section." msgstr "" -#: ../system/core-workflows/limitations.rst:37 -msgid "up- or downgrade permissions of users" +#: ../settings/security/third-party/saml.rst:62 +msgid "Per-IdP Instructions" msgstr "" -#: ../system/core-workflows/limitations.rst:38 -msgid "affecting article creation or listing" +#: ../settings/security/third-party/saml.rst:102 +msgid "Keycloak" msgstr "" -#: ../system/data-privacy.rst:2 -msgid "Data Privacy" +#: ../settings/security/third-party/saml.rst:65 +msgid "" +"**To add Zammad as a client,** save the XML configuration to disk (``https://" +"your.zammad.domain/auth/saml/metadata``) and use **Clients > Clients list > " +"Import client** in the Keycloak admin panel." msgstr "" -#: ../system/data-privacy.rst:4 +#: ../settings/security/third-party/saml.rst:70 msgid "" -"For compliance with GDPR and other data privacy laws, you may wish to " -"**permanently delete users from the system**, along with **all of their " -"associated tickets**." +"To help Zammad **match its own user accounts to Keycloak users**, create a " +"user attribute (or “property”) mapper. In **Clients list**, click on your " +"newly created Client ID, choose the tab **Client scopes** and click on the " +"link which refers to your Zammad instance. Choose **Add mapper > By " +"configuration > User Property** and create a mapper with the following " +"entries:" 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 `!" +#: ../settings/security/third-party/saml.rst:78 +msgid "**Name**" msgstr "" -#: ../system/data-privacy.rst:12 -msgid "" -"Access to this panel requires ``admin.data_privacy`` permissions (introduced " -"in Zammad 3.5)." +#: ../settings/security/third-party/saml.rst:80 +msgid "**Mapper Type**" msgstr "" -#: ../system/data-privacy.rst:15 -msgid "" -"On older systems that have not been updated yet, customers can also be :docs:" -"`deleted via the Zammad console `." +#: ../settings/security/third-party/saml.rst:81 +msgid "``User Property``" msgstr "" -#: ../system/data-privacy.rst:22 -msgid "User deletion dialog in the Data Privacy panel" +#: ../settings/security/third-party/saml.rst:82 +msgid "**Property**" msgstr "" -#: ../system/data-privacy.rst:22 -msgid "" -"The user deletion dialog lists some of the tickets that will be removed from " -"the system along with the user." +#: ../settings/security/third-party/saml.rst:83 +msgid "``emailAddress``" msgstr "" -#: ../system/data-privacy.rst:27 -msgid "Deleting Users via GUI" +#: ../settings/security/third-party/saml.rst:84 +msgid "**SAML Attribute Name**" msgstr "" -#: ../system/data-privacy.rst:29 -msgid "🔥 **All deletions are FINAL!**" +#: ../settings/security/third-party/saml.rst:86 +msgid "**SAML Attribute NameFormat**" msgstr "" -#: ../system/data-privacy.rst:31 -msgid "Once you click “Delete”, the action cannot be canceled or undone." +#: ../settings/security/third-party/saml.rst:87 +msgid "``basic``" msgstr "" -#: ../system/data-privacy.rst:33 +#: ../settings/security/third-party/saml.rst:89 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." +"In the example above, we're telling Zammad that whenever it receives a SAML " +"login request, it should take the ``email`` property from Keycloak, look for " +"a Zammad user with the same ``email`` attribute, and create a new session " +"for that user." msgstr "" -#: ../system/data-privacy.rst:36 -msgid "**The following records cannot be deleted:**" +#: ../settings/security/third-party/saml.rst:95 +msgid "" +"If your Keycloak users' email addresses are stored on another property (*e." +"g.,* ``username``), adjust accordingly." msgstr "" -#: ../system/data-privacy.rst:38 -msgid "your own account" +#: ../settings/security/third-party/saml.rst:98 +msgid "" +"Back in **Settings**, enter the Client ID (``https://your.zammad.domain/auth/" +"saml/metadata``) in the field **Master SAML Processing URL**." msgstr "" -#: ../system/data-privacy.rst:39 -msgid "the system's last remaining administrator account" +#: ../settings/security/third-party/saml.rst:101 +msgid "You also need to enable **Sign assertions**." msgstr "" -#: ../system/data-privacy.rst:42 -msgid "Step 1: Find a User / Confirm Deletion" +#: ../settings/security/third-party/saml.rst:105 +msgid "Step 2: Configure Zammad" msgstr "" -#: ../system/data-privacy.rst:44 -msgid "There are three ways to access the user deletion dialog:" +#: ../settings/security/third-party/saml.rst:107 +msgid "" +"Enable SAML and enter your IdP's details in the Admin Panel under **Settings " +"> Security > Third Party Applications > Authentication via SAML**:" msgstr "" -#: ../system/data-privacy.rst:51 -msgid "**from the user's profile**" +#: ../settings/security/third-party/saml.rst:None +msgid "Example configuration of SAML part 1" msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Accessing the user deletion dialog in a user profile" +#: ../settings/security/third-party/saml.rst:119 +msgid "Display name" msgstr "" -#: ../system/data-privacy.rst:51 -msgid "Click **Action > Delete**." +#: ../settings/security/third-party/saml.rst:116 +msgid "" +"Allows you to define a custom button name for SAML. This helps your users to " +"understand better what the button on the login page does." msgstr "" -#: ../system/data-privacy.rst:58 -msgid "**in the “Manage > Users” Admin Panel**" +#: ../settings/security/third-party/saml.rst:119 +msgid "Defaults to ``SAML``." msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Accessing the user deletion dialog under “Users” in the Admin Panel" +#: ../settings/security/third-party/saml.rst:123 +msgid "IDP SSO target URL" msgstr "" -#: ../system/data-privacy.rst:58 -msgid "Use the **⋮ Actions** menu for the target user." +#: ../settings/security/third-party/saml.rst:122 +msgid "" +"This is the target URL Zammad shall redirect to when the user presses the " +"SAML button. For Keycloak, this needs to look like https://your.domain/" +"realms/your-realm/protocol/saml" msgstr "" -#: ../system/data-privacy.rst:66 ../system/data-privacy.rst:104 -msgid "**in the “System > Data Privacy” Admin Panel**" +#: ../settings/security/third-party/saml.rst:127 +msgid "IDP single logout target URL" msgstr "" -#: ../system/data-privacy.rst:0 +#: ../settings/security/third-party/saml.rst:126 msgid "" -"Accessing the user deletion dialog under “Data Privacy” in the Admin Panel" +"This is the URL to which the single logout request and response should be " +"sent." msgstr "" -#: ../system/data-privacy.rst:65 +#: ../settings/security/third-party/saml.rst:131 +msgid "IDP certificate" +msgstr "" + +#: ../settings/security/third-party/saml.rst:130 msgid "" -"Use the **New Deletion Task** button. Search for users by name or email " -"address." +"The public certificate of your IDP for Zammad to verify during the callback " +"phase." msgstr "" -#: ../system/data-privacy.rst:79 -msgid "**Delete organizations**" +#: ../settings/security/third-party/saml.rst:145 +msgid "IDP certificate fingerprint" msgstr "" -#: ../system/data-privacy.rst:69 +#: ../settings/security/third-party/saml.rst:134 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:" +"The fingerprint of your IDPs public certificate to verify during callback " +"phase." msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Deleting an organization via the user deletion dialog" +#: ../settings/security/third-party/saml.rst:137 +msgid "🔏 **For the IdP certificate / certificate fingerprint:**" msgstr "" -#: ../system/data-privacy.rst:78 +#: ../settings/security/third-party/saml.rst:139 msgid "" -"If this option does not appear, make sure there are no pending deletion " -"tasks for other customers from this organization." +"Provide **only one or the other**—do not provide both! (Between the two, we " +"recommend the signing certificate itself: fingerprints use SHA-1, which `has " +"been broken for a while now `_.)" msgstr "" -#: ../system/data-privacy.rst:82 -msgid "Step 2: Monitor Deletion Job Status" +#: ../settings/security/third-party/saml.rst:144 +msgid "" +"**Keycloak users:** Find your certificate in the Keycloak admin panel under " +"**Realm Settings > Keys > Algorithm: RS256 > Certificate**." msgstr "" -#: ../system/data-privacy.rst:84 +#: ../settings/security/third-party/saml.rst:151 +msgid "Name identifier format" +msgstr "" + +#: ../settings/security/third-party/saml.rst:148 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:" +"This is the unique identifiers field type. Usually it should be ``urn:oasis:" +"names:tc:SAML:1.1:nameid-format:emailAddress``." msgstr "" -#: ../system/data-privacy.rst:98 -msgid "**in the Activity Stream**" +#: ../settings/security/third-party/saml.rst:151 +msgid "Zammad **expects an email address as unique identifier**!" msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Activity Stream showing data privacy tasks" +#: ../settings/security/third-party/saml.rst:155 +msgid "UID attribute name" msgstr "" -#: ../system/data-privacy.rst:94 +#: ../settings/security/third-party/saml.rst:154 msgid "" -"For each deleted user, the Activity Stream will be updated twice—once when " -"the task is created, and once when it's complete." +"Here you can define an attribute that uniquely identifies the user. If " +"unset, the name identifier returned by the IDP is used." msgstr "" -#: ../system/data-privacy.rst:97 -msgid "" -"These notifications are only visible to users with ``admin.data_privacy`` " -"permissions." +#: ../settings/security/third-party/saml.rst:None +msgid "Example configuration of SAML part 2" msgstr "" -#: ../system/data-privacy.rst:0 +#: ../settings/security/third-party/saml.rst:163 msgid "" -"The task list within Data Privacy shows removals being in progress and " -"completed." +"Decide if the certificate for the connection to the IdP service has to be " +"verified or not (default: ``yes``)." msgstr "" -#: ../system/data-privacy.rst:107 -msgid "Frequently Asked Questions" +#: ../settings/security/third-party/saml.rst:169 +msgid "Signing & Encrypting" msgstr "" -#: ../system/data-privacy.rst:121 -msgid "What happens if I receive an email from a deleted customer?" -msgstr "" - -#: ../system/data-privacy.rst:110 +#: ../settings/security/third-party/saml.rst:169 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." +"Define if you want to sign, encrypt, do both or nothing for the requests." msgstr "" -#: ../system/data-privacy.rst:115 -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**." +#: ../settings/security/third-party/saml.rst:179 +msgid "Certificate (PEM)" msgstr "" -#: ../system/data-privacy.rst:130 -msgid "What about user information stored in internal notes or other messages?" +#: ../settings/security/third-party/saml.rst:172 +msgid "" +"Paste the public certificate of your Zammad SAML client, if you want to " +"encrypt the requests." msgstr "" -#: ../system/data-privacy.rst:124 -msgid "" -"The deletion process removes **user accounts and associated tickets only**." +#: ../settings/security/third-party/saml.rst:175 +msgid "Make sure the certificate is:" msgstr "" -#: ../system/data-privacy.rst:126 -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." +#: ../settings/security/third-party/saml.rst:177 +msgid "already valid and not yet expired" msgstr "" -#: ../system/data-privacy.rst:137 -msgid "I deleted an user and can still see a message they sent!" +#: ../settings/security/third-party/saml.rst:178 +msgid "no CA certificate" msgstr "" -#: ../system/data-privacy.rst:133 -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." +#: ../settings/security/third-party/saml.rst:179 +msgid "valid for signing and encrypting" msgstr "" -#: ../system/data-privacy.rst:141 -msgid "I removed a customer, now my reporting is off!" +#: ../settings/security/third-party/saml.rst:185 +msgid "Private key (PEM)" msgstr "" -#: ../system/data-privacy.rst:140 +#: ../settings/security/third-party/saml.rst:182 msgid "" -"When removing users and their tickets, all references are removed. This also " -"affects e.g. Reporting - these information are lost." +"Paste the private key of your Zammad SAML client here, if you want to sign " +"the requests." msgstr "" -#: ../system/data-privacy.rst:145 -msgid "How long does Zammad store created tasks?" +#: ../settings/security/third-party/saml.rst:185 +msgid "Make sure the key is an RSA key with a length of at least 2048 bits." msgstr "" -#: ../system/data-privacy.rst:144 -msgid "" -"Please see the on-premise data section of the :docs:`data privacy ` chapter." +#: ../settings/security/third-party/saml.rst:188 +msgid "Private key secret" msgstr "" -#: ../system/data-privacy.rst:150 -msgid "What about re-assigned tickets? I want to delete them, too." +#: ../settings/security/third-party/saml.rst:188 +msgid "If your private key is secured with a secret, you can provide it here." msgstr "" -#: ../system/data-privacy.rst:148 -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." +#: ../settings/security/third-party/saml.rst:192 +msgid "Your callback URL" msgstr "" -#: ../system/data-privacy.rst:154 -msgid "Why are there so many deletion task entries, I didn't create them!" +#: ../settings/security/third-party/saml.rst:191 +msgid "" +"This URL is needed for your IdP configuration so it knows where to redirect " +"to after successful authentication." msgstr "" -#: ../system/data-privacy.rst:153 +#: ../settings/security/third-party/saml.rst:194 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." +"After saving your input by clicking on the \"Submit\" button, Zammad " +"verifies the provided keys/certificates (e.g. if they are valid for signing/" +"encrypting and if they aren't expired)." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:2 -msgid "Admin Panel Reference" +#: ../settings/security/third-party/saml.rst:199 +msgid "" +"See :ref:`automatic account linking ` for details " +"on how to link existing Zammad accounts to IdP accounts." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:None -msgid "Screenshot of Checkmk settings overview" +#: ../settings/security/third-party/saml.rst:205 +msgid "Automatic account linking doesn't work" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:12 +#: ../settings/security/third-party/saml.rst:206 msgid "" -"Which :doc:`group ` should Checkmk tickets be assigned " -"to as a default (*i.e.,* when none is specified)?" +"Have you double-checked your IdP's user attribute mapping configuration?" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:15 -msgid "(Applies to :ref:`API alerts ` only.)" +#: ../settings/security/third-party/twitter.rst:4 +msgid "" +"It is possible to create a quick login for your helpdesk via Twitter. To do " +"so, you need to follow these steps:" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:21 -msgid "Auto close" +#: ../settings/security/third-party/twitter.rst:8 +msgid "Register Twitter App" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:18 -msgid "" -"Should Zammad automatically close tickets if a service has recovered on its " -"own?" +#: ../settings/security/third-party/twitter.rst:10 +msgid "Go to https://dev.twitter.com/apps and login with your account." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:21 -msgid "(Agents will receive notifications for such closures as appropriate.)" +#: ../settings/security/third-party/twitter.rst:15 +msgid "Click on \"Create App\"" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:30 -msgid "Auto-close state" +#: ../settings/security/third-party/twitter.rst:None +msgid "new app page" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:24 -msgid "What ticket state should be applied when “auto-closing” a ticket?" +#: ../settings/security/third-party/twitter.rst:20 +msgid "" +"Enter app settings. As \"Callback URL\" you need to enter ``https://" +"zammad_host/api/v1/external_credentials/twitter/callback``. You need to " +"replace ``zammad_host`` with the domain of your Zammad system." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:26 +#: ../settings/security/third-party/twitter.rst:24 msgid "" -"You can choose from the seven built-in ticket states. If these states aren't " -"enough for you, you can :ref:`define a new ticket state ` for this purpose as well. This can be useful for tracking " -"tickets with :doc:`reports `, for example." +"After the app has been created, update the application icon and organization " +"attributes." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:35 -#: ../system/integrations/cti/includes/recent-logs.include.rst:2 -#: ../system/integrations/ldap/index.rst:74 -#: ../system/integrations/pgp/index.rst:106 -msgid "Recent Logs" +#: ../settings/security/third-party/twitter.rst:None +msgid "set permissions to receive and send direct messages" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:None -msgid "Screenshot of Checkmk \"Recent Logs\" section" +#: ../settings/security/third-party/twitter.rst:30 +msgid "" +"Next we need to set ``read, write and access direct messages`` permissions " +"for the app." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:41 -msgid "" -"If you're having trouble getting Zammad and Checkmk to play nicely together, " -"this section can help you troubleshoot." +#: ../settings/security/third-party/twitter.rst:None +msgid "click on Keys & Access Token, note them" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:44 +#: ../settings/security/third-party/twitter.rst:36 msgid "" -"It contains a record of the fifty most recent transactions that Zammad knows " -"about, including each one's request/response details and return status." +"Go to \"Keys and Access Token\" tab and note the \"Consumer Key\" and " +"\"Consumer Secret\"." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:2 -msgid "API Reference" +#: ../settings/security/third-party/twitter.rst:40 +msgid "Configure Zammad as Twitter App" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:4 +#: ../settings/security/third-party/twitter.rst:42 msgid "" -"For most users, :ref:`the sample scripts from the Setup Guide ` will do the job just fine. But if you want more fine-grained control" -"—for instance, to create high- and low-priority tickets for different types " -"of system events—then you'll have to customize the data those scripts send " -"to Zammad." +"Go to \"Admin > Security > Twitter > Third Party Applications > Twitter\" " +"Section." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:15 -msgid "" -"This custom script will automatically set all tickets it creates to **high " -"priority** and **assign them to charlie@chrispresso.com**." +#: ../settings/security/third-party/twitter.rst:None +msgid "Admin > Security > Third Party Applications" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:32 -msgid "How Does it Work?" +#: ../settings/security/third-party/twitter.rst:48 +msgid "" +"Fill in the \"Twitter Key\" and the \"Twitter Secret\" and click the " +"\"Submit\" button." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:34 +#: ../settings/security/third-party/twitter.rst:51 msgid "" -"There are two kinds of data you can pass to the API, both in the form of key-" -"value pairs:" +"Now you can link accounts via \"Avatar > Profile > Link Accounts\" or login " +"via Zammad login page." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:44 -msgid "Checkmk parameters" +#: ../settings/security/two-factor.rst:11 +msgid "Two-factor Authentication Methods" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:38 -msgid "" -"are required, and make up the **contents** of the resulting tickets/" -"articles. They also determine whether an event creates a new ticket or " -"updates/closes an existing one." +#: ../settings/security/two-factor.rst:2 +msgid "Two-Factor Authentication" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:42 +#: ../settings/security/two-factor.rst:4 msgid "" -"These are the only values used in the sample scripts. **Use them as-is**; " -"technically, they can be customized, but it's hard to imagine a good reason " -"for it." +"Two-factor authentication (2FA) enhances the security of Zammad accounts by " +"adding an extra layer of verification beyond a password. It requires users " +"to provide two different types of authentication factors, typically " +"something they know (like a password) and something they possess (like a " +"mobile device or a security token), to ensure that only authorized " +"individuals can access the account." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:52 -msgid "Ticket attributes" +#: ../settings/security/two-factor.rst:19 +msgid "Enable Recovery Codes" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:47 +#: ../settings/security/two-factor.rst:21 msgid "" -"are optional, and can be used to **adjust settings** on newly created " -"tickets (*e.g.,* set the owner, group, priority, or state)." +"Recovery codes are one-time use security codes that can be used by the user " +"if they lose access to their other two-factor authentication methods. They " +"cannot be used on their own, they can only be activated if at least one two-" +"factor authentication method is enabled." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:50 -msgid "" -"If you want to customize your Checkmk alert script, do it with these. Simply " -"add an extra “form” option for each one (``-F \"key=value\"``) to your " -"script's ``curl`` command line, as in the example above." +#: ../settings/security/two-factor.rst:None +msgid "Enable Recovery Codes Setting" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:54 -msgid "💡 **It's just an API endpoint!**" +#: ../settings/security/two-factor.rst:30 +msgid "" +"Recovery codes can only be used as a backup method. If enabled, they will be " +"automatically generated for the user once they set up their initial two-" +"factor authentication method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:56 +#: ../settings/security/two-factor.rst:34 msgid "" -"When using Checkmk integration, messages need to be formatted in a certain " -"way, but that *doesn't mean the messages actually have to come from Checkmk*." +"The user will be asked to print out or save the generated recovery codes in " +"a safe place. Once used, a recovery code cannot be reused." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:59 +#: ../settings/security/two-factor.rst:37 msgid "" -"If you use another monitoring tool that's not officially supported by " -"Zammad, there's probably a way to make it work with your Checkmk callback " -"URL." +"Users will also have an option to regenerate their recovery codes at any " +"time, which invalidates already existing recovery codes and provides them " +"with a list of fresh codes." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:63 -msgid "Checkmk Parameters" +#: ../settings/security/two-factor.rst:41 +msgid "" +"After you enable this setting, when the user completes a setup of their " +"initial two-factor authentication method, they will be presented with a list " +"of recovery codes and instructed to save them for later use." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:65 -msgid "" -"When a notification is received, Zammad creates a new article containing the " -"details of the event that triggered it:" +#: ../settings/security/two-factor.rst:None +msgid "Recovery Codes Generation Modal Dialog" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:None -msgid "Checkmk article body" +#: ../settings/security/two-factor.rst:50 +msgid "Enforce the Set Up of the Two-Factor Authentication" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:72 +#: ../settings/security/two-factor.rst:52 msgid "" -"These details come from the fields listed below, which correspond to " -"parameters provided by Checkmk (``$NOTIFY_*``)." +"In case you wish to require your users to set up at least one two-factor " +"authentication method for their account, you can do this by selecting " +"specific user roles the requirement applies to in **Enforced for user " +"roles** setting. Of course you must have at least one two-factor " +"authentication method enabled for this setting to take effect." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:75 -msgid "**Required fields are marked with an asterisk (\\*).**" +#: ../settings/security/two-factor.rst:None +msgid "Enforced for User Roles Setting" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:79 -msgid "event_id\\*" +#: ../settings/security/two-factor.rst:62 +msgid "" +"After you change this setting, if the user has one of the selected roles on " +"their account, they will be forced to set up the two-factor authentication " +"upon next sign in or application reload." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:78 +#: ../settings/security/two-factor.rst:66 msgid "" -"A unique ID for the system event. (``$NOTIFY_SERVICEPROBLEMID`` / " -"``$NOTIFY_HOSTPROBLEMID``)" +"A modal dialog with instructions will be shown, and they will not be able to " +"do any work before they set up at least one two-factor method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:86 -msgid "host\\*" +#: ../settings/security/two-factor.rst:None +msgid "Modal Dialog for Enforcing Two-Factor Authentication Set Up" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:82 +#: ../settings/security/two-factor.rst:74 +msgid "Reset Two-Factor Authentication for a Specific User" +msgstr "" + +#: ../settings/security/two-factor.rst:76 msgid "" -"The hostname of the system that the event originated from. " -"(``$NOTIFY_HOSTNAME``)" +"In case an user isn't able to login anymore because of an inaccessible " +"second factor, you can reset the user's 2FA method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:85 +#: ../settings/security/two-factor.rst:79 msgid "" -"Used to determine if a new event belongs to an existing ticket. Also used in " -"the subject line of the resulting article (“ is ”)." +"To do this, go to the user management and search for the relevant user. " +"After you found the account, click the button in the action column and " +"select \"Manage Two-Factor Authentication\":" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:96 -msgid "service" +#: ../settings/security/two-factor.rst:None +msgid "Context menu in action column in user management" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:89 +#: ../settings/security/two-factor.rst:87 msgid "" -"The name of the service that the event originated from. " -"(``$NOTIFY_SERVICEDESC``)" +"After selecting this, you can see a dialog where you can either reset one " +"2FA method or reset all of the user's 2FA methods:" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:92 -msgid "Used to determine if a new event belongs to an existing ticket." +#: ../settings/security/two-factor.rst:None +msgid "Dialog for resetting user's 2FA method" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:94 -#: ../system/integrations/checkmk/api-reference.rst:110 -msgid "Displayed as ``-`` when omitted." +#: ../settings/security/two-factor.rst:94 +msgid "" +"Choose the fitting one, click on the corresponding \"Remove ...\" button and " +"confirm your action. The user now has to setup a new 2FA method, depending " +"on your 2FA configuration." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:104 -msgid "state\\*" +#: ../settings/security/two-factor/authenticator-app.rst:2 +msgid "Authenticator App" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:99 +#: ../settings/security/two-factor/authenticator-app.rst:4 msgid "" -"The current state of the service or host in question. " -"(``$NOTIFY_SERVICESTATE`` / ``$NOTIFY_HOSTSTATE``)" +"The authenticator app method is a type of two-factor authentication that " +"uses a mobile application to generate one-time codes for account " +"verification. After setting up the authenticator app on their device, the " +"user links it to their Zammad account." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:102 +#: ../settings/security/two-factor/authenticator-app.rst:12 msgid "" -"Used to detect when a ticket should be auto-closed (*i.e.,* on ``OK``/" -"``UP``). Also used in the subject line of the resulting article (“ is " -"”)." +"When logging in, the user is prompted to enter a time-sensitive code " +"generated by the app, in addition to their password. This code acts as the " +"second factor of authentication, providing an extra layer of security as it " +"changes periodically and is unique to the user's device." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:110 -msgid "text" +#: ../settings/security/two-factor/authenticator-app.rst:None +msgid "Security Code in Google Authenticator App" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:107 +#: ../settings/security/two-factor/authenticator-app.rst:22 msgid "" -"The output of the process that triggered the event. " -"(``$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" +"The app generates codes based on a shared secret key stored securely on both " +"the user's device and the server, ensuring a synchronized and secure " +"authentication process. The method of generating the codes is sometimes also " +"called TOTP (time-based one-time password)." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:121 -msgid "" -"The Object Manager attribute panel displays built-in and custom\n" -"attribute names." +#: ../settings/security/two-factor/authenticator-app.rst:28 +msgid "Enabling the Authenticator App Method" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:121 -msgid "Find a complete list of ticket attributes in the Object Manager." +#: ../settings/security/two-factor/authenticator-app.rst:30 +#: ../settings/security/two-factor/security-keys.rst:28 +msgid "To enable the method, just toggle the switch on in the settings." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:123 -msgid "" -"Ticket attributes are entirely optional, and can be used to customize the " -"tickets that Checkmk creates. (Note that these attributes will be ignored if " -"a new event belongs to an existing ticket.)" +#: ../settings/security/two-factor/authenticator-app.rst:None +msgid "Authenticator App Switch in Settings" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:128 +#: ../settings/security/two-factor/authenticator-app.rst:36 msgid "" -"Why would you want to do this? Maybe you have only one IT guy, and all " -"system monitoring issues should be automatically assigned to him. Or, maybe " -"you're creating multiple notification rules so that database outages take " -"higher priority than disk space warnings." +"Now the users will be able to set up this two-factor authentication method " +"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " +"Once they do, on next sign-in with password, they will be asked to provide " +"an additional security code generated by their mobile device." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:135 -msgid "In most cases, you'll probably want to set one of the following:" +#: ../settings/security/two-factor/security-keys.rst:2 +msgid "Security Keys" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:137 -msgid "group" +#: ../settings/security/two-factor/security-keys.rst:4 +msgid "" +"The security keys method is a type of a two-factor authentication that uses " +"Web Authentication API in the browser for verifying user's identity. The " +"user can register multiple hardware or software security keys with their " +"Zammad account and then they can use it during the sign-in process." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:139 -msgid "state" +#: ../settings/security/two-factor/security-keys.rst:12 +msgid "" +"When logging in, the user is prompted to provide the same security key they " +"registered with their account, in addition to their password. This key acts " +"as the second factor of authentication, providing an extra layer of security." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:140 -msgid "priority" +#: ../settings/security/two-factor/security-keys.rst:None +msgid "Security Key dialog in Safari on macOS" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:142 +#: ../settings/security/two-factor/security-keys.rst:21 msgid "" -"but in practice, you can set almost any attribute, including :doc:`custom " -"ones you created through the Object Manager `." -msgstr "" - -#: ../system/integrations/checkmk/api-reference.rst:145 -msgid "Please note that the following attributes are **not customizable**:" +"The type of the key can range from hardware USB sticks to passkeys stored in " +"a device of user's choice. Which type can be used depends on the browser " +"flavor and the platform of the user." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:147 -msgid "title" +#: ../settings/security/two-factor/security-keys.rst:26 +msgid "Enabling the Security Keys Method" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:148 -msgid "id" +#: ../settings/security/two-factor/security-keys.rst:None +msgid "Security Keys Switch in Settings" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:149 -msgid "ticket number" +#: ../settings/security/two-factor/security-keys.rst:34 +msgid "" +"Now the users will be able to set up this two-factor authentication method " +"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " +"Once they do, on next sign-in with password, they will be asked to provide " +"the same security key they registered during the setup." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:151 -msgid "created_by_id" +#: ../settings/system/system-selfhosted.include.rst:3 +msgid "" +"Below settings are only available to self hosted users. In hosted " +"environments we're handling these settings for you to ensure service " +"stability." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:152 -msgid "updated_by_id" +#: ../settings/system/base.rst:11 +msgid "Fully Qualified Domain Name" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:155 -msgid "Which Values Can Be Set?" +#: ../settings/system/base.rst:7 +msgid "The URL of your Zammad installation." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:157 -msgid "😵 **Invalid values → unpredictable behavior**" +#: ../settings/system/base.rst:9 ../settings/system/base.rst:17 +msgid "This setting is used within :doc:`/misc/variables` and notifications." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:159 -msgid "" -"If you provide a value that Zammad doesn't understand (*e.g.,* ``-F " -"\"priority=high\"``), it's not always clear what will happen. In some cases, " -"a ticket will be created with the default values instead - but in others, it " -"may not be created at all!" +#: ../settings/system/system-base.include.rst:1 +msgid "It is automatically set by the *Getting Started wizard*." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:164 -msgid "So what values does Zammad understand, then? Well, it depends..." +#: ../settings/system/system-base.include.rst:5 +msgid "Changing this setting also changes callback URLs for your channels etc." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:168 -msgid "Use an email address or username:" +#: ../settings/system/system-base.include.rst:6 +msgid "This setting can have negative affects on being able to login." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:190 -msgid "group & priority" +#: ../settings/system/base.rst:19 +msgid "HTTP type" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:175 -msgid "Refer to the dropdown menus in the ticket pane:" +#: ../settings/system/base.rst:14 +msgid "" +"The HTTP type tells your installation how your clients connect. This is " +"relevant for authentication and cookie security." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:0 -msgid "See possible values for certain attributes in the ticket pane." +#: ../settings/system/base.rst:31 +msgid "SystemID" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:187 -msgid "🙅 **Ticket state CANNOT be set this way!**" +#: ../settings/system/base.rst:22 +msgid "" +"This ID is being used within your ticket number. In case you're " +"communicating with another ticket system with similar ticket number schemes " +"this ID greatly reduces the risk of false follow ups." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:189 +#: ../settings/system/base.rst:26 msgid "" -"Why? Because ``-F \"state=...\"`` is already used :ref:`as a Checkmk " -"parameter `." +"The SystemID is randomly selected upon installation of Zammad (``1-99``)." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:222 -msgid "Everything Else" +#: ../settings/system/base.rst:30 +msgid "" +"**Do not** change this setting in a productive system! Your Zammad " +"installation may no longer recognize old ticket number based follow ups upon " +"change!" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:193 -msgid "" -"To set any other attributes, it helps to know your way around the :docs:" -"`rails console `. Valid values are those that you can " -"set with a string:" +#: ../settings/system/frontend.rst:2 +msgid "Frontend" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:218 -msgid "These values can then be passed directly to the API:" +#: ../settings/system/frontend.rst:22 +msgid "Core Workflow Ajax Mode" msgstr "" -#: ../system/integrations/checkmk/index.rst:16 -msgid "How does it work?" +#: ../settings/system/frontend.rst:6 +msgid "" +"This setting allows administrators to enforce :doc:`/system/core-workflows` " +"to use Ajax-Calls instead of web sockets. You'll usually only need this if " +"you experience serious issues as noted below." msgstr "" -#: ../system/integrations/checkmk/index.rst:2 -msgid "Checkmk" +#: ../settings/system/frontend.rst:10 +msgid "**🤓 Possible (technical) reasons**" msgstr "" -#: ../system/integrations/checkmk/index.rst:4 +#: ../settings/system/frontend.rst:12 msgid "" -"`Checkmk `_ is a powerful IT monitoring tool that can " -"send real-time status alerts to Zammad via email or REST API. Set these " -"alerts up in Checkmk, and Zammad will automatically create, update, and " -"close tickets based on the health of your system:" +"In some cases, your network structure (e.g. firewalls, proxies) may " +"disconnect long web socket connections. This leads to select fields staying " +"empty (e.g. owner selection *after* selecting your group) or fields not " +"shown / hidden (e.g. when switching to or from pending states, the \"pending " +"till\" field not showing / hiding)." msgstr "" -#: ../system/integrations/checkmk/index.rst:14 -msgid "Screenshot of ticket created by Checkmk notifications" +#: ../settings/system/frontend.rst:18 +msgid "" +"Please keep in mind that the Ajax fallback may cause serious pressure on " +"your application server. If you have the choice stick to web sockets." msgstr "" -#: ../system/integrations/checkmk/index.rst:14 -msgid "Multiple alerts, same ticket." +#: ../settings/system/frontend.rst:22 +msgid "Default: ``no`` (inactive)" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:2 -msgid "Setup Guide" +#: ../settings/system/frontend.rst:53 +msgid "Show calendar weeks in the picker of date/datetime fields" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:4 +#: ../settings/system/frontend.rst:25 msgid "" -"Whenever the Checkmk integration is enabled, Zammad listens for messages on " -"its API and over email. As long as those messages follow the required " -"format, Zammad will create new tickets (or find and update existing ones) " -"based on the message contents." +"With this setting you can instruct Zammad to provide week number display " +"globally for all users. Calendar with week number display are usually used " +"in business sectors and may not be relevant for everyone." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:10 +#: ../settings/system/frontend.rst:29 msgid "" -"That means that “setting up Checkmk integration” is simply a matter of " -"**adding configuration to your Checkmk site**: telling it when to send these " -"messages and what to say. To do that, you'll need to create a new " -"**notification rule** (see `Checkmk's official docs `_ for help with that)." +"This setting affects *all areas* - you'll also see week numbers in the admin " +"panel for e.g. triggers and macros." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:17 -msgid "" -"As part of this new rule, you'll have to choose a **notification method** " -"(*i.e.,* a script to execute whenever the rule is triggered). This script " -"will be written by you (samples below), and contain the logic for sending " -"API/email messages to Zammad:" +#: ../settings/system/frontend.rst:32 +msgid "Default: ``no`` (not shown)" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:26 -msgid "Checkmk \"New Rule\" dialog" +#: ../settings/system/frontend.rst:53 +msgid "Here's the difference:" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:26 -msgid "" -"Find your custom scripts in the Checkmk WATO under **Notifications > New " -"Rule > Notification Method**." +#: ../settings/system/frontend.rst:0 +msgid "Screenshot showing Zammad's date picker (in the default way)" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:29 -msgid "" -"Once you're done setting up your new rule, you're all set! New tickets " -"should start coming in and auto-updating any time your rule is triggered." +#: ../settings/system/frontend.rst:41 +msgid "Set to ``no``" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:33 +#: ../settings/system/frontend.rst:0 msgid "" -"(If you need help troubleshooting, be sure to check the :ref:`checkmk-recent-" -"logs`.)" +"Screenshot showing Zammad's date picker with\n" +"week numbers enabled" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:38 -msgid "API Alerts" +#: ../settings/system/frontend.rst:50 +msgid "Set to ``yes``" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:40 +#: ../settings/system/index.rst:4 msgid "" -"To add these scripts in the Checkmk WATO, copy them into your Checkmk " -"installation directory and make them executable. (Be sure to replace the " -"``zammad.example.com`` callback URL with the one found in your admin panel.)" +"For your overview we split each tab within system settings into its own page:" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:60 -msgid "Service notification" +#: ../settings/system/index.rst:16 +msgid "Console Based Settings" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:46 +#: ../settings/system/index.rst:18 msgid "" -"For updates on the status of the software running on your server (*e.g.,* " -"postgres)." +"There's some console based settings we didn't put into the UI. However, you " +"may find them helpful - you can find them in our :docs:`hidden settings ` section." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:75 -msgid "Host notification" +#: ../settings/system/network.rst:2 +msgid "Network" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:63 -msgid "For updates on the status of the server itself." +#: ../settings/system/network.rst:8 +msgid "" +"The proxy settings can only be saved after successfully testing the proxy " +"connection." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:77 -msgid "🤔 **What's with all the env vars?**" +#: ../settings/system/network.rst:15 +msgid "Proxy Address." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:79 +#: ../settings/system/network.rst:12 msgid "" -"Whenever Checkmk runs these scripts, it needs to provide some information " -"about the event that triggered the notification. This information is passed " -"in the form of these ``$NOTIFY_*`` environment variables." +"Allows you to provide a proxy server if needed. This is relevant for network " +"communication by Zammad." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:85 -msgid "" -"You can specify additional parameters to pass to the script when you're " -"setting up your notification rule, but the ones you see here are all " -"provided by default." +#: ../settings/system/network.rst:15 +msgid "It **does not** affect the update process or Elasticsearch." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:90 -msgid "Email Alerts" +#: ../settings/system/network.rst:18 +msgid "Username for proxy connection." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:94 +#: ../settings/system/network.rst:18 msgid "" -"🐞 **There are known bugs** in Zammad's processing of email from Checkmk. " -"This section will be completed once they have been resolved. (Learn more at " -"GitHub issues `#2377 `_ & " -"`#2180 `_.)" +"If your proxy server requires authentication, provide the username here." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:100 -msgid "In the meantime, we encourage you to set up API alerts instead." +#: ../settings/system/network.rst:21 +msgid "Password for proxy connection." msgstr "" -#: ../system/integrations/clearbit.rst:2 -msgid "Clearbit" +#: ../settings/system/network.rst:21 +msgid "" +"If your proxy server requires authentication, provide the password here." msgstr "" -#: ../system/integrations/clearbit.rst:4 +#: ../settings/system/network.rst:26 +msgid "No proxy for the following hosts." +msgstr "" + +#: ../settings/system/network.rst:24 msgid "" -"With our Clearbit integration, you can easily enrich the information " -"provided by Zammad. If the customers or agents email address is known to " -"Clearbit, it will share all information it has regarding the user with " -"Zammad. Those information can include the following:" +"Exception list for hosts you can't or don't want to reach via proxy server." msgstr "" -#: ../system/integrations/clearbit.rst:9 -msgid "Avatar" +#: ../settings/system/network.rst:27 +msgid "Default: ``localhost,127.0.0.0,::1``" msgstr "" -#: ../system/integrations/clearbit.rst:10 -msgid "Address information" +#: ../settings/system/services.rst:2 +msgid "Services" msgstr "" -#: ../system/integrations/clearbit.rst:11 -msgid "Website information" +#: ../settings/system/services.rst:10 +msgid "Image Service" msgstr "" -#: ../system/integrations/clearbit.rst:12 -msgid "A BIO (as Note by default)" +#: ../settings/system/services.rst:5 +msgid "Defines the backend for user and organization image lookups." msgstr "" -#: ../system/integrations/clearbit.rst:14 -msgid "" -"If needed, you can add further custom objects and add mappings to them, so " -"the Clearbit information can be filled within the database. In general you " -"can get any information from Clearbit, as long as you have a mapping to an " -"Zammad object." +#: ../settings/system/services.rst:7 +msgid "Default: ``Zammad Image Service`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:21 +#: ../settings/system/services.rst:9 msgid "" -"Clearbit does have a mapping of fields like LDAP and Exchange have, but does " -"not \"win\" against Zammad information. This means that if you have e.g. the " -"last name field filled in already and Clearbit has other information on " -"that, it will not be updated." +"Make sure your on premise installation has ``HTTPS`` access to ``images." +"zammad.com``." msgstr "" -#: ../system/integrations/clearbit.rst:26 -msgid "" -"However: If let's say the last name has been set by Clearbit and Zammad " -"notices that the last name on the Clearbit source has changed, Zammad will " -"also update this value." +#: ../settings/system/services.rst:18 +msgid "Geo Calendar Service" msgstr "" -#: ../system/integrations/clearbit.rst:33 +#: ../settings/system/services.rst:13 msgid "" -"The configuration of Clearbit is really easy and done fast! Just login to " -"your Clearbit-Account, go to \"API\" and copy the secret-API-Key." +"Defines the backend for geo calendar lookups. Used for initial calendar " +"setup." msgstr "" -#: ../system/integrations/clearbit.rst:38 -msgid "" -"Now change to your Zammad instance, go to Integrations (System) -> Clearbit " -"in the admin panel. Paste your API-Key into the API-Key-Field and decide if " -"Zammad should create unknown Organizations automatically, if the user does " -"not have one yet (and Clearbit knows it). The shared option decides if the " -"new organizations Zammad creates with Clearbit should be shared ones." +#: ../settings/system/services.rst:16 +msgid "Default: ``Zammad GeoCalendar Service`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:47 +#: ../settings/system/services.include.rst:2 msgid "" -"If you're unsure what option to choose, better stick with \"no\". You can " -"also learn more about :doc:`/manage/organizations/index`." +"Make sure your on premise installation has ``HTTPS`` access to ``geo.zammad." +"com``." msgstr "" -#: ../system/integrations/clearbit.rst:52 -msgid "" -"The Mapping option works similar to the mapping within the Exchange and LDAP " -"sync. You can add further mappings for e.g. custom fields if you need more " -"information that Clearbit can provide." +#: ../settings/system/services.rst:26 +msgid "Geo IP Service" msgstr "" -#: ../system/integrations/clearbit.rst:58 +#: ../settings/system/services.rst:21 msgid "" -"If you want to add more Clearbit fields and want to learn more about " -"available fields on their API, you can take a look at their `API " -"documentation `_." +"Defines the backend for geo IP lookups. Shows also location of an IP address " +"if an IP address is shown." msgstr "" -#: ../system/integrations/clearbit.rst:62 -msgid "" -"If you're happy with the above chosen Settings and your mapping, just save " -"the changes and enable Clearbit integration. Zammad will now start polling " -"the Clearbit API as users contact you." +#: ../settings/system/services.rst:24 +msgid "Default: ``Zammad GeoIP Service`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:68 -msgid "" -"Zammad does not synchronize with Clearbit on a regular basis, but on demand " -"if needed. This saves API calls." +#: ../settings/system/services.rst:32 +msgid "Geo Location Service" msgstr "" -#: ../system/integrations/clearbit.rst:73 +#: ../settings/system/services.rst:29 msgid "" -"Below the Settings and Mappings, you'll find our Integration log. You can " -"see what requests Zammad sent to Clearbit and also the APIs Response." +"Defines the backend for geo location lookups to store geo locations for " +"addresses." msgstr "" -#: ../system/integrations/clearbit.rst:78 +#: ../settings/system/services.rst:32 msgid "" -"By the way, you can also view the API log on the Clearbit website - the " -"information seen is basically the same." -msgstr "" - -#: ../system/integrations/clearbit.rst:84 -msgid "Example When Adding a User" +"Default: ``OpenStreetMap (ODbL 1.0, http://osm.org/copyright)`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:86 +#: ../settings/system/services.rst:36 msgid "" -"To show you how fast information is added, we added a small Screencast " -"below. This shows the creation of the User Alex from Clearbit. As we already " -"set the last name of Alex to \"X\", Zammad did not update it. What Zammad " -"did was to add further information it received from Clearbit." +"You can find a detailed privacy information on what we store for how long on " +"our :docs:`Privacy Appendix ` inside of our System " +"Documentation." msgstr "" -#: ../system/integrations/cti/generic.rst:2 -msgid "CTI (generic)" +#: ../settings/system/storage.rst:2 +msgid "Storage" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:1 +#: ../settings/system/storage.rst:6 msgid "" -"This integration enables Zammad to provide a caller log to your agents. With " -"this your agents can greet your customers by their name and are supported by " -"Zammad with automatically opening a new ticket dialog or the user profile." +"Here you can define where Zammad stores attachments for tickets and the " +"knowledge base. By default, we're writing to the ``Database`` - you can " +"switch to ``Filesystem`` or ``Simple Storage (S3)`` at any time. In this " +"case please have a look on the following instructions." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:6 +#: ../settings/system/storage.rst:11 msgid "" -"Click the toggle next to the heading to activate or deactivate this " -"integration." +"If you have a busy Zammad instance, we strongly encourage you to use " +"filesystem storage instead of \"Database\". This will greatly improve system " +"performance (de-crease database load and size)." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:9 -msgid "" -"If you want to learn more on how your agents can use this function, please " -"refer the :user-docs:`user documentation `." +#: ../settings/system/storage.rst:19 +msgid "Database" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:14 +#: ../settings/system/storage.rst:17 msgid "" -"Automatically opening new ticket dialogues or user profiles requires agent " -"to extension mapping - see more below." -msgstr "" - -#: ../system/integrations/cti/includes/introduction.include.rst:20 -msgid "Please note the following limitations to reduce confusion later on:" +"This is the default storage method. The attachments are stored directly in " +"the database. If your Zammad instance grows, we recommend one of the other " +"methods to maintain performance." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:22 -msgid "CTI integrations provide caller log functions only." +#: ../settings/system/storage.rst:38 +msgid "Filesystem" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:23 +#: ../settings/system/storage.rst:22 msgid "" -"This integration does not provide any VoIP functionalities; you can't make " -"phone calls from within Zammad." +"This storage method is recommended for all Zammad instances, especially for " +"those with a higher load. If you choose filesystem, your files are written " +"to ``/opt/zammad/storage/``." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:25 +#: ../settings/system/storage.rst:26 msgid "" -"If your browser supports ``tel``-URLs, you can click on phone numbers for " -"automatic dialing. This requires additional software / configuration on your " -"agent's computers." +"Moving attachments from \"Database\" to \"Filesystem\" can be run during " +"production use. However, you should consider your framework conditions (e.g. " +"bandwidth, system load in production) to define the right moment." msgstr "" -#: ../system/integrations/cti/generic.rst:9 -#: ../system/integrations/cti/placetel.rst:14 -#: ../system/integrations/cti/sipgate.rst:14 -msgid "Please provide the following requirements:" +#: ../settings/system/storage.rst:32 +msgid "**You noticed slow updates of Zammad?**" msgstr "" -#: ../system/integrations/cti/generic.rst:11 +#: ../settings/system/storage.rst:34 msgid "" -"A telephone system that supports webhooks (outbound) (best option are those " -"that allow customizing the calls)." +"While Zammad is beeing updated, it enforces a recursive \"change " +"owner\" (chown) for this directory. For instances with many files this can " +"be time consuming. To mitigate that you can move your files and create a " +"symlink in ``/opt/zammad/storage/`` to the new directory. Of course you have " +"to make sure on your own that the permissions are always correct." msgstr "" -#: ../system/integrations/cti/generic.rst:13 -msgid "A unique Call-ID during the call session." +#: ../settings/system/storage.rst:95 +msgid "Simple Storage (S3)" msgstr "" -#: ../system/integrations/cti/generic.rst:14 -msgid "Call event data (both numbers and direction)." +#: ../settings/system/storage.rst:41 +msgid "" +"To use the Simple Storage (S3), you have to provide some settings, which " +"can't be accessed in the UI (see instructions below)." msgstr "" -#: ../system/integrations/cti/generic.rst:15 -msgid "Your Zammad instance must be reachable for your telephony system." +#: ../settings/system/storage.rst:44 +msgid "" +"⚠️ Please note that the current implementation is in its early stages and can " +"be modified in the future." msgstr "" -#: ../system/integrations/cti/generic.rst:17 +#: ../settings/system/storage.rst:47 msgid "" -"If you want to learn more on what kind of requests are supported by Zammad " -"and what it expects, please consult our :docs:`CTI-API documentation `." +"The prerequisite is to have access to a S3-compatible storage and to have " +"all necessary parameters available (which depends on your storage provider; " +"if in doubt, please ask there for help)." msgstr "" -#: ../system/integrations/cti/generic.rst:22 -#: ../system/integrations/cti/placetel.rst:27 -#: ../system/integrations/cti/sipgate.rst:30 -msgid "Available Settings" +#: ../settings/system/storage.rst:51 +msgid "Steps to configure S3:" msgstr "" -#: ../system/integrations/cti/generic.rst:29 -#: ../system/integrations/cti/placetel.rst:41 -#: ../system/integrations/cti/sipgate.rst:40 -msgid "Endpoint Settings" +#: ../settings/system/storage.rst:53 +msgid "" +"Copy ``config/zammad/storage.yml.dist`` to ``config/zammad/storage.yml``" msgstr "" -#: ../system/integrations/cti/generic.rst:25 -msgid "" -"Zammad will list your generic CTI endpoint here. It contains a unique token " -"so ensure to keep this URL save." +#: ../settings/system/storage.rst:54 +msgid "Edit the copied file in one of the following ways:" msgstr "" -#: ../system/integrations/cti/generic.rst:28 +#: ../settings/system/storage.rst:56 msgid "" -"You'll need this endpoint for your PBX to talk to Zammad, see :docs:`CTI-API " -"documentation `." +"Either provide your S3 configuration with one attribute per line like in the " +"upper area of the file" msgstr "" -#: ../system/integrations/cti/includes/important-dont-forget-saving.include.rst:3 +#: ../settings/system/storage.rst:58 msgid "" -"All following options **do not save automatically**. Always use the Save " -"button on the lower end of the integration page!" +"Or provide your S3 configuration as an URL (which you can find at the end of " +"the file). Note: you can also provide this URL as environment variable (:" +"docs:`see system documentation `) without using this yml-file." msgstr "" -#: ../system/integrations/cti/generic.rst:43 -#: ../system/integrations/cti/placetel.rst:49 -#: ../system/integrations/cti/sipgate.rst:52 -msgid "Call Settings" +#: ../settings/system/storage.rst:62 +msgid "" +"We recommend the deletion of the not used configuration style to avoid " +"inconsistencies." msgstr "" -#: ../system/integrations/cti/generic.rst:39 -#: ../system/integrations/cti/placetel.rst:49 -#: ../system/integrations/cti/sipgate.rst:37 -#: ../system/integrations/cti/sipgate.rst:50 -msgid "Inbound" +#: ../settings/system/storage.rst:65 +msgid "Restart Zammad so the config file / environment variable is loaded" msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:1 +#: ../settings/system/storage.rst:66 msgid "" -"This option allows you to block specific incoming caller IDs. It allows you " -"to temporarily reject e.g. spam callers without having to contact providers " -"or PBX administrators." +"Set the \"Storage Method\" in Zammad to ``Simple Storage (S3)`` in Settings " +"> System > Storage and click on \"Submit\". After that, Zammad checks your " +"configuration and the connection to the service and will raise an error " +"message if something is wrong." msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:11 -msgid "Caller ID to block" +#: ../settings/system/storage.rst:72 +msgid "A very simple storage configuration could look like this:" msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 -msgid "Provide caller IDs to block in ``E.164`` format." +#: ../settings/system/storage.rst:85 +msgid "" +"Before setting the storage method to ``Simple Storage (S3)`` (step 4), " +"please make sure to have a working setup." msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:8 +#: ../settings/system/storage.rst:88 msgid "" -"Your telephony system has to support this function. Zammad will send a " -"``reject`` response which will cause your telephony system to hang up the " -"call. To callers this usually will feel like the line is busy." +"You can verify this by running ``rails r 'Rails.logger = Logger.new(STDOUT); " +"pp Store::Provider::S3.ping?'`` in your Zammad directory. If everything is " +"fine, you should see ``true``, else you should see ``false`` and a simple " +"error message." msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:14 +#: ../settings/system/storage.rst:93 msgid "" -"Provide a meaningful note for your fellow administrators to remind yourself " -"why you've chosen to block the number." +"If you installed Zammad through a package manager (rather than from source), " +"replace ``rails r`` with ``zammad run rails r`` above. To learn more, see :" +"docs:`Administration via Console `." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 -#: ../system/integrations/cti/includes/outbound-calls.include.rst:17 -#: ../system/integrations/cti/sipgate.rst:40 -msgid "Outbound" +#: ../settings/ticket.rst:4 +msgid "" +"Here you can adjust general ticket settings. Additional ones for the ticket " +"composer interface can be found in the :doc:`/misc/composer`." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:1 -msgid "" -"In many cases you may want to use a different caller ID depending on the " -"destination you're calling. This may apply due to specific connection rates " -"to other countries or because you want your customer to feel you're calling " -"from the same country." +#: ../settings/ticket.rst:11 +msgid "Ticket Hook (default: ``Ticket#``)" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:6 -msgid "This option expects ``E.164`` number formats." +#: ../settings/ticket.rst:11 +msgid "The identifier for a ticket; *e.g.,* Ticket#, Call#, MyTicket#." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 -msgid "Destination caller ID" +#: ../settings/ticket.rst:38 +msgid "Ticket Hook Position (default: ``right``)" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:5 -msgid "The caller ID or number you're trying to call." +#: ../settings/ticket.rst:14 +msgid "" +"With this setting you can decide (if) where to insert the ticket number." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:7 -msgid "You can use wildcards for e.g. country specific outbound numbers like:" +#: ../settings/ticket.rst:20 +msgid "*Right*" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:9 -msgid "``49*`` for Germany" +#: ../settings/ticket.rst:17 +msgid "" +"This setting will add the ticket reference on the right site of the subject." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:10 -msgid "``4930*`` for Berlin / Germany landlines" +#: ../settings/ticket.rst:20 +msgid "Example: ``Some Subject [Ticket#12345]``" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 -msgid "``33*`` for France" +#: ../settings/ticket.rst:26 +msgid "*Left*" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:15 -msgid "Set Outbound caller ID" +#: ../settings/ticket.rst:23 +msgid "" +"This setting will add the ticket reference on the left site of the subject." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:14 -msgid "" -"The outbound caller ID to set (the number your customer sees on his display) " -"in ``E.164`` number format." +#: ../settings/ticket.rst:26 +msgid "Example: ``[Ticket#12345] Some Subject``" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 -msgid "Provide a short description for fellow administrators." +#: ../settings/ticket.rst:29 +msgid "*None*" msgstr "" -#: ../system/integrations/cti/includes/generic-cti-support-note.includes.rst:3 -msgid "" -"This option requires your PBX to send a specific request to Zammad *before " -"dialing*. Please consult the :docs:`CTI API ` in case " -"you're not sure." +#: ../settings/ticket.rst:29 +msgid "This will completely remove ticket references from the subject." msgstr "" -#: ../system/integrations/cti/generic.rst:52 -#: ../system/integrations/cti/placetel.rst:54 -#: ../system/integrations/cti/sipgate.rst:59 -msgid "Other Settings" +#: ../settings/ticket.rst:33 +msgid "" +"Please ensure to take a look at :doc:`/channels/email/settings` within the " +"email channel to ensure you have at least one reference that helps Zammad to " +"assign follow-ups correctly." msgstr "" -#: ../system/integrations/cti/includes/other-settings-intro.include.rst:1 +#: ../settings/ticket.rst:37 msgid "" -"Below you can find all available additional settings for this CTI " -"integration. For your overview we're sorting them by appearance and " -"reference their description first." +"Disabling this and not setting up any further follow up search will lead to " +"unexpected results!" msgstr "" -#: ../system/integrations/cti/includes/default-caller-id.include.rst:2 -#: ../system/integrations/cti/includes/default-caller-id.include.rst:1 -msgid "Default caller ID for outbound calls" +#: ../settings/ticket.rst:65 +msgid "" +"Ticket Last Contact Behaviour (default: ``Use the start time of the last " +"customer thread (which may consist of multiple articles).``)" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:16 -#: ../system/integrations/cti/includes/records-caller-log.include.rst:15 -msgid "Shown records in caller log" +#: ../settings/ticket.rst:41 +msgid "" +"This setting changes the way Zammad updates the ``Last Contact`` value of a " +"ticket. This is fairly important for overviews and what you expect upon " +"ticket updates of a customer." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:2 +#: ../settings/ticket.rst:52 msgid "" -"Allows you to set the number of shown caller log entries for all users. You " -"can choose from the following values:" +"Use the start time of the last customer thread (which may consist of " +"multiple articles)." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:5 -msgid "60 (default)" +#: ../settings/ticket.rst:46 +msgid "" +"If this option is chosen, Zammad will update the last updated value just " +"once if a customer replies. After that, Zammad will wait for an agent to " +"react." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:6 -msgid "120" +#: ../settings/ticket.rst:50 +msgid "" +"This comes in handy if you want to work tickets in the order of their first " +"update. This will not change ticket orders if customers decide to \"bump\" " +"the ticket affected." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:7 -msgid "180" +#: ../settings/ticket.rst:57 +msgid "Use the time of the very last customer article." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:8 -msgid "240" +#: ../settings/ticket.rst:55 +msgid "" +"When setting this option, Zammad will always update the last updated value. " +"This means that if ordering by ``Last Update``, ticket orders will change if " +"customers \"bump\" the ticket." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:9 -msgid "300" +#: ../settings/ticket.rst:64 +msgid "Last contact value used on :doc:`/manage/overviews`" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:11 -msgid "**🥵 Potential performance issue**" +#: ../settings/ticket.rst:65 +msgid "Last contact value used on :doc:`/manage/trigger`" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:13 +#: ../settings/ticket.rst:88 msgid "" -"Setting this setting higher than 60 may cause serious performance issues on " -"very busy instances. Keep in mind that this setting causes Zammad to poll " -"and send up to 300 records to *all active agent sessions* in very short time " -"periods." +"Ticket Organization Reassignment (default: ``Update the most recent tickets." +"``)" msgstr "" -#: ../system/integrations/cti/generic.rst:73 -msgid "Caller Log Filter" +#: ../settings/ticket.rst:68 +msgid "" +"This setting changes the way Zammad updates the organization field of the " +"tickets whenever the primary organization of a user is changed." msgstr "" -#: ../system/integrations/cti/generic.rst:55 -msgid "" -"This function allows you to provide call information based on e.g. queues " -"only to agents that really need the information." +#: ../settings/ticket.rst:74 +msgid "Update the most recent tickets." msgstr "" -#: ../system/integrations/cti/generic.rst:58 +#: ../settings/ticket.rst:72 msgid "" -"Why? If you have a team for several countries or departments, you don't want " -"to bug your agents from other departments. Leaving these options empty will " -"fallback to showing everything to everyone." +"If this option is chosen, Zammad will update the 100 most recent tickets " +"where the user is the ticket customer. The ticket organization field will be " +"automatically set to the new primary organization of the user." msgstr "" -#: ../system/integrations/cti/generic.rst:64 -msgid "Destination caller ID or Queue" +#: ../settings/ticket.rst:88 +msgid "Do not update any tickets." msgstr "" -#: ../system/integrations/cti/generic.rst:63 +#: ../settings/ticket.rst:77 msgid "" -"This depends on your PBX and usually is either a queue ID, phone number or " -"extension." +"When choosing this option, Zammad will not update any tickets when the " +"user's primary organization is changed." msgstr "" -#: ../system/integrations/cti/generic.rst:69 -msgid "Agents" +#: ../settings/ticket.rst:80 +msgid "**Use with care!**" msgstr "" -#: ../system/integrations/cti/generic.rst:67 +#: ../settings/ticket.rst:82 msgid "" -"Select the agents that are responsible for the group. These agents will then " -"see caller log entries and call notifications fitting to said queue." +"Using this option may lead to inconsistencies in the system as the ticket " +"organization may become decoupled from the ticket customer." msgstr "" -#: ../system/integrations/cti/generic.rst:0 +#: ../settings/ticket.rst:85 msgid "" -"Screenshot showing the caller log filter table with pre filled sample data" +"However, you may use this option if you wish to maintain :ref:`the shared " +"access ` to the ticket for all organization " +"members of the original organization of the customer." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:6 -msgid "" -"With recent logs Zammad allows you to view the latest calls for the CTI " -"functionality. This usually comes in handy, when you're looking for errors." +#: ../settings/ticket.rst:110 +msgid "Ticket Number Format (default: ``Increment (SystemID.Counter)``)" msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:0 +#: ../settings/ticket.rst:94 msgid "" -"Screenshot showing several incoming requests within Recent logs section." +"This setting defines the way Zammad's ticket number will look. Changing this " +"setting in production will cause follow up detection to fail." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:16 -msgid "I'm just here to clear floats up." +#: ../settings/ticket.rst:102 +msgid "Increment (SystemID.Counter)" msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:20 +#: ../settings/ticket.rst:98 msgid "" -"By clicking on the entry of interest, Zammad will provide more details on " -"the call in question. You'll see the payload it received and also the " -"response that was sent." +"The increment value contains the SystemID (automatically generated during " +"installation) and a increment which counts up with every new Ticket. The " +"increment will automatically get another digit if needed." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:0 -msgid "" -"Screenshot showing detailed information of a specific log entry of recent " -"logs" +#: ../settings/ticket.rst:102 +msgid "Examples: ``1010138``, ``1010139``" msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:31 -msgid "x" +#: ../settings/ticket.rst:110 +msgid "Date (Year.Month.Day.SystemID.Counter)" msgstr "" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 -#: ../system/integrations/cti/includes/troubleshooting.include.rst:9 -msgid "My Phone page stays blank, signalling does work..." +#: ../settings/ticket.rst:105 +msgid "" +"This version of the ticket number is fairly long. However, because it " +"contains the date of ticket creation, it also allows you to see when the " +"ticket has been created. You may feel familiar with this number format if " +"you've worked with OTRS already." msgstr "" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:5 -msgid "" -"If you've made sure that signalling works (check Recent logs) and your " -"Caller Log still stays empty, please ensure that you only configured one CTI " -"integration version. Specifically defining more than one agent mapping on " -"the different integration variants will be the issue." +#: ../settings/ticket.rst:110 +msgid "Examples: ``201206231010138``, ``201206231010139``" msgstr "" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 -msgid "Clear the not needed agent mapping and reload your browser page." +#: ../settings/ticket.rst:137 +msgid "OPTIONS" msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:1 +#: ../settings/ticket.rst:113 msgid "" -"By mapping your agents extension to their existing Zammad users, Zammad can " -"provide a new ticket dialog or open the user profile for the agent that " -"picks up the call." +"The below options allow you to further customize your ticket number. The " +"availability of options differ depending of the chosen ticket number format " +"above." msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:5 -msgid "" -"This speeds up ticket aiding, no matter if it's for existing tickets or new " -"ones!" +#: ../settings/ticket.rst:122 +msgid "Checksum (default: ``no``)" msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:8 +#: ../settings/ticket.rst:118 msgid "" -"To see it work from the agent's perspective, have a look on :user-docs:`user " -"documentation `." +"If set to yes, we'll built a checksum to further \"unique\" the ticket " +"number of your system. If you're dealing with many other ticket systems this " +"might help to prevent false positive follow up detection on tickets." msgstr "" -#: ../system/integrations/cti/placetel.rst:2 -msgid "Placetel CTI" +#: ../settings/ticket.rst:122 +msgid "This will also add another digit to the ticket number." msgstr "" -#: ../system/integrations/cti/placetel.rst:16 -msgid "You need an administrative Placetel account for your organization." +#: ../settings/ticket.rst:137 +msgid "Min. size of Number (default: ``5``)" msgstr "" -#: ../system/integrations/cti/placetel.rst:17 -#: ../system/integrations/cti/sipgate.rst:20 +#: ../settings/ticket.rst:125 msgid "" -"Your Zammad instance must be allowed to communicate to external services." +"This setting defines the minimum length of your ticket number. If your " +"counter is not yet high enough, Zammad will fill the number with zeros to " +"ensure the wanted length." msgstr "" -#: ../system/integrations/cti/placetel.rst:18 -msgid "Placetel must be able to reach your Zammad instance." -msgstr "" - -#: ../system/integrations/cti/placetel.rst:22 -msgid ":doc:`provider-configurations/placetel`" -msgstr "" - -#: ../system/integrations/cti/placetel.rst:21 +#: ../settings/ticket.rst:129 msgid "" -"Learn how to configure Placetel to enable Zammad and Placetel to communicate " -"with each other." +"Please note that the minimum length is ``3`` (SystemID + at least one digit " +"if below 10). Also, if the length is no longer long enough, the number will " +"automatically get one digit longer. Ticket-Numbers **do not overflow**, thus " +"it's save to keep it at 5 or set it lower if wanted." msgstr "" -#: ../system/integrations/cti/placetel.rst:32 +#: ../settings/ticket.rst:135 msgid "" -"The here listed endpoint settings are relevant for the :doc:`integration " -"configuration with Placetel `." +"This option is only available if ticket number format is set to " +"``Increment``!" msgstr "" -#: ../system/integrations/cti/placetel.rst:37 -#: ../system/integrations/i-doit.rst:53 -msgid "Endpoint" +#: ../settings/ticket.rst:142 +msgid "Auto-Assignment" msgstr "" -#: ../system/integrations/cti/placetel.rst:36 +#: ../settings/ticket.rst:144 msgid "" -"This endpoint will be required for the Zammad integration within the " -"Placetel web interface." -msgstr "" - -#: ../system/integrations/cti/placetel.rst:41 -msgid "API Token" +"In a larger Zammad environment, it happens that several agents open the same " +"ticket at the same time. Although collision detection is then effective, the " +"efficiency of processing can be increased by means of the automatic " +"assignment of tickets when a ticket is opened." msgstr "" -#: ../system/integrations/cti/placetel.rst:40 +#: ../settings/ticket.rst:149 msgid "" -"You'll receive this token within the ``Web API`` menu. Make sure to copy " -"this value, it's only shown once!" -msgstr "" - -#: ../system/integrations/cti/placetel.rst:71 -#: ../system/integrations/cti/sipgate.rst:77 -msgid "Phone Extension to Agent Mapping" +"The automatic assignment of tickets can be activated and configured in the " +"admin area under Settings > Ticket > Auto Assignment." msgstr "" -#: ../system/integrations/cti/placetel.rst:0 -msgid "Screenshot showing sample user mappings in between Placetel and Zammad" +#: ../settings/ticket.rst:152 +msgid "" +"The auto assignment only works if the ticket has no owner yet. By default, " +"the agent can always reset the ticket owner to ``-`` if needed." msgstr "" -#: ../system/integrations/cti/placetel.rst:64 +#: ../settings/ticket.rst:155 msgid "" -"You can find your agents Placetel username combination required within ⚙️ PBX " -"→ VoIP destinations. Within the \"Advanced settings\" section you're looking " -"for \"SIP user name\" and \"SIP server\"." +"If you want to use this function for only specific tickets, you can " +"configure the conditions accordingly to meet your requirement. By default " +"the condition affects all tickets with the state ``open``." msgstr "" -#: ../system/integrations/cti/placetel.rst:68 -msgid "Combine these two like so: ``@``." +#: ../settings/ticket.rst:161 +msgid "" +"If you need to exclude users (e.g. a group leader), you can search and " +"select the desired agents in the ``Exception Users`` list. The search " +"function in this area is only effective, if you have too many agents to " +"display at once to help you with the configuration." msgstr "" -#: ../system/integrations/cti/placetel.rst:0 -msgid "Sample VoIP credentials for a Placetel user" +#: ../settings/ticket.rst:167 +msgid "Notifications" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:2 -msgid "Setup Placetel connection for Zammad" +#: ../settings/ticket.rst:191 +msgid "Default Notifications" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:6 +#: ../settings/ticket.rst:170 msgid "" -"This configuration step requires a *full* administrative Placetel account. " -"You may receive forbidden error messages with Placetel in case your " -"permissions are not high enough." +"This setting allows you to configure the default ticket notifications that " +"will be applied to all new agent users (incl. users who were just assigned " +"agent role). Simply change the notification matrix to desired state and " +"press **Save**." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:10 +#: ../settings/ticket.rst:175 msgid "" -"The following actions can be configured via the `Placetel web interface " -"`_." -msgstr "" - -#: ../system/integrations/cti/provider-configurations/placetel.rst:29 -msgid "Step 1: Activate Zammad integration" +"In case an agent already exists, their ticket notification preferences will " +"be preserved. Optionally, you can also **Apply current defaults to all " +"agents**." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:14 +#: ../settings/ticket.rst:181 msgid "" -"Within Integrations, scroll down to Partner integrations and select Zammad." +"**Potential time-consuming action:** Applying default ticket notifications " +"to all agent users may take some time to complete, be patient! The exact " +"time will depend on the size of your system and the number of agents." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:17 +#: ../settings/ticket.rst:185 msgid "" -"You can alternatively filter by \"Ticket Systems\" to reduce the number of " -"entries on the page. You'll still want to look for Partner integrations. 🤓" +"**Active agents only!** When current default ticket notifications are " +"applied, only active agent users are considered. In case an agent is re-" +"activated *after* this action, they will still have the old notification " +"configuration." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:21 +#: ../settings/ticket.rst:190 msgid "" -"Within the Zammad integration now press \"Activate\". A new tab ``API`` " -"becomes available - open this tab." +"In case you want to go back to the initial state of ticket notifications, " +"you can click on **Reset to default** button." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:24 -msgid "" -"Now tick \"Enable Call Control / Notify API\" and paste the Placetel " -"endpoint from your Zammad instance into the field \"URL of your API " -"endpoint\". Save to apply the settings" +#: ../settings/ticket.rst:196 +msgid "Duplicate Detection" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 -msgid "Screencast showing how to activate the Zammad integration" +#: ../settings/ticket.rst:238 +msgid "Detect Duplicate Ticket Creation" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:51 -msgid "Step 2: Generate API Token for Placetel" +#: ../settings/ticket.rst:199 +msgid "" +"This setting turns on the duplicate ticket detection mechanism during ticket " +"creation. If similar tickets are found in the system, a suitable warning " +"will be shown to the user trying to create a ticket." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:32 -msgid "" -"Go back to the integrations page and scroll down to \"Web API\". Generate a " -"new API token by using the \"Create a new API token\" button." +#: ../settings/ticket.rst:206 +msgid "A Sample Duplicate Ticket Warning" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:37 +#: ../settings/ticket.rst:208 msgid "" -"If you already generated a token either use your existing token or reset it " -"by using above mentioned button. Placetel will ask you to conform this reset." +"You can choose which ticket attributes will be matched by selecting them in " +"**Attributes to compare** field. Only if the ticket attribute value provided " +"by the user in the ticket create form is *equal* with the attribute in an " +"existing ticket, the warning will be shown." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:41 -msgid "" -"Please keep in mind that existing API scripts may no longer work due to " -"token resets!" +#: ../settings/ticket.rst:213 +msgid "**Warning title** and **Warning message** are configurable as well." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:44 +#: ../settings/ticket.rst:215 msgid "" -"Copy the provided API token and insert it into the \"API Token\" field " -"within Zammad's Placetel integration." +"You can limit the detection only to certain user roles. By default, only " +"agents will see the warning." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:47 +#: ../settings/ticket.rst:218 msgid "" -"Apply your changes by using the \"Save\" button on the bottom of the " -"Placetel integration page and activate the Placetel integration." +"If you don't want to show the matched tickets as part of the warning, you " +"can set **Show matching ticket(s) in the warning** setting to *no*." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +#: ../settings/ticket.rst:221 msgid "" -"Screencast showing how to retrieve an API token from Placetel for Zammad" +"By default, **Permission level for looking up ticket** is set to *User*, " +"which means user permissions will be honored during sarch. The user will " +"see the warning only if tickets they have access to are matched. " +"Alternatively, you can set this setting to *System*, in which case the " +"search will happen within *all* tickets in the system, regardless of user " +"permissions." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:73 -#: ../system/integrations/cti/provider-configurations/sipgate.rst:77 -msgid "Step 3: Restrict the numbers to notify on" +#: ../settings/ticket.rst:227 +msgid "**🦺 Safety first!**" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:54 +#: ../settings/ticket.rst:229 msgid "" -"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " -"the the Integrations page of the Placetel web interface, go to \"Notify " -"API\"." +"Even if the permission level is set to *System*, the user will not be shown " +"the tickets they don't have access to in the warning, even if they match." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:58 +#: ../settings/ticket.rst:233 msgid "" -"Lower on the page Placetel allows you to restrict the numbers to notify on. " -"You'll find this within the \"External routing API\" part." +"However, just the confirmation about the existence of the tickets in the " +"system may be considered an unwanted information disclosure. Use this option " +"carefully!" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +#: ../settings/ticket.rst:237 msgid "" -"Screenshot showing a sample selection of phone numbers to use for the " -"Placetels notify API" +"Finally, you can configure between matching within **All tickets** or **Open " +"tickets** only by setting **Match tickets in following states**. Depending " +"on the current ticket state, a ticket may or not be matched." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:66 -msgid "" -"This menu point also provides a API request log from Placetel view. Just " -"open \"Recent responses of your API endpoint\" to learn more." +#: ../system/core-workflows.rst:2 +msgid "Core Workflows" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:69 +#: ../system/core-workflows.rst:4 msgid "" -"If you want to see Zammad's perspective, use the \"Recent Logs\" part from " -"within the Placetel integration page." +"Core Workflows allow you to adjust object attributes in many ways. For " +"example:" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 -msgid "Screenshot showing sample log entries for Placetels API calls to Zammad" +#: ../system/core-workflows.rst:7 +msgid "show / hide fields" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:77 -msgid "Step 4 (optional): Further configurations for Placetel" +#: ../system/core-workflows.rst:8 +msgid "adjust mandatory setting" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:76 +#: ../system/core-workflows.rst:9 +msgid "manipulate available options" +msgstr "" + +#: ../system/core-workflows.rst:11 msgid "" -"If needed, you can now configure Zammad's Placetel integration in more " -"detail. You can learn more about your options here: :ref:`Placetel " -"integration settings `." +"With this, you can provide exactly the information your users really need!" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:2 -msgid "Setup Sipgate connection for Zammad" +#: ../system/core-workflows.rst:15 +msgid "" +"If the pre-defined :doc:`/system/objects` are not enough, please add them " +"beforehand." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +#: ../system/core-workflows.rst:17 msgid "" -"Sipgate has no english web interface which is why this documentation page is " -"mixing up languages badly." +"If you experience slow or unreliable field updates, please see :ref:`Core " +"Workflow Ajax Modus `" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +#: ../system/core-workflows.rst:22 msgid "" -"Please also note that the availability of API addons highly depends on your " -"package trier. Usage of sipgate.io packages *is not free*, please check " -"their `pricing page `_ before!" +"This is a very enhanced functionality and can cause unexpected UI behavior. " +"Please ensure to test your use cases after configuration to reduce surprises." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:35 -msgid "Step 1: Book sipgate.io package" +#: ../system/core-workflows.rst:None +msgid "Dialogue for adding a new workflow" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:13 -msgid "Skip to step 2 if you already have the package booked!" +#: ../system/core-workflows/condition-operators.rst:2 +msgid "Core Workflow Condition Operators" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:15 +#: ../system/core-workflows/condition-operators.rst:4 msgid "" -"Login to an administrative Sipgate account and navigate to " -"``Accountverwaltung``. You'll see several different options depending on " -"your booked packages. Select ``Verträge & Produkte`` to continue." +"You might know that there is a separate section for explaining :doc:" +"`condition operators `. Head over there to " +"see a detailed explanation of many conditions and operators." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:19 +#: ../system/core-workflows/condition-operators.rst:8 msgid "" -"Scroll down to the section ``Zusätzliche Produkte buchen`` and look for " -"``sipgate.io`` - select this product by using the ``Produkte anzeigen``-" -"Button." -msgstr "" - -#: ../system/integrations/cti/provider-configurations/sipgate.rst:23 -msgid "" -"On the next page select either one of the ``sipgate.io`` packages or ``Push-" -"API Package Free``. Follow the dialogue by booking the addon. You'll be " -"returned to your contract overview and now should see the selected addon in " -"your list." +"Due to differences to other places in Zammad which are also using conditions " +"(e.g. triggers), you can find a dedicated description of operators for core " +"workflows below." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:30 +#: ../system/core-workflows/condition-operators.rst:12 msgid "" -"The availability for ``sipgate.io`` packages and their levels highly depends " -"on the overall account type and product you've booked with Sipgate." +"Be aware that the availability of the operators depends on the selected " +"attribute and its field type. Some of the operators may only be available " +"for system attributes (e.g. for \"tags\", \"active\")." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screencast showing the process on how to book the required sipgate.io addon" +#: ../system/core-workflows/condition-operators.rst:20 +msgid "Operator" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:52 -msgid "Step 2: Configure webhook for Zammad" +#: ../system/core-workflows/condition-operators.rst:22 +msgid "after (absolute)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:38 -msgid "" -"Within your ``Accountverwaltung`` navicate to your product ``sipgate.io``. " -"In the newly opened tab, switch from \"Clients\" to \"Webhooks\" and paste " -"the endpoint URLs from your Zammad instance like so:" +#: ../system/core-workflows/condition-operators.rst:23 +msgid "Matches if a date/time is after a specific point in time." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:42 -msgid "Inbound endpoint to \"Incoming\"" +#: ../system/core-workflows/condition-operators.rst:24 +msgid "after (relative)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:43 -msgid "Outbound endpoint to \"Outgoing\"" +#: ../system/core-workflows/condition-operators.rst:25 +msgid "Matches if a time span after a specified event has passed." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:47 -msgid "" -"Ensure to select at least one call group or phoneline within \"Sources\". " -"Other wise Sipgate will not indicate any incoming or outgoing calls to " -"Zammad." +#: ../system/core-workflows/condition-operators.rst:26 +msgid "before (absolute)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screencast showing how to add Zammad's endpoint URLs to sipgate.ios webhook " -"configuration" +#: ../system/core-workflows/condition-operators.rst:27 +msgid "Matches if a date/time is before a specific point in time." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:55 -msgid "" -"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " -"the Webhooks → URLs section of Sipgate you can select which *sources* " -"Sipgate should notify Zammad about in- and outgoing calls." +#: ../system/core-workflows/condition-operators.rst:28 +msgid "before (relative)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:59 -msgid "" -"Use either specific phone lines or use the option \"Use for all phonelines " -"and groups\" to notify Zammad about all existing lines of your Sipgate " -"account." +#: ../system/core-workflows/condition-operators.rst:29 +msgid "Matches if a time span after a specified event has not passed." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screenshot showing a sample selection of phone numbers to use for the " -"Sipgates webhooks API" +#: ../system/core-workflows/condition-operators.rst:30 +msgid "contains" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:68 -msgid "This section also allows you to enable a Debug log." +#: ../system/core-workflows/condition-operators.rst:31 +msgid "Matches if a specified value is present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "Screenshot showing an enabled Debug log option" +#: ../system/core-workflows/condition-operators.rst:33 +msgid "Matches if all of the specified values are present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:73 -msgid "" -"After enabling you can use the Debug log section to see all sent webhook " -"calls to Zammad. You'll also can see the response." +#: ../system/core-workflows/condition-operators.rst:35 +msgid "Matches if none of the specified values are present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screenshot showing sample log entries for Sipgates webhook calls to Zammad" +#: ../system/core-workflows/condition-operators.rst:36 +msgid "contains not" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:81 -msgid "Step 4 (optional): Further configurations for Sipgate" +#: ../system/core-workflows/condition-operators.rst:37 +msgid "Matches if a specified value is not present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:80 -msgid "" -"If needed, you can now configure Zammad's Sipgate integration in more " -"detail. You can learn more about your options here: :ref:`Sipgate " -"integration settings `." +#: ../system/core-workflows/condition-operators.rst:39 +msgid "Matches if one specified value is present." msgstr "" -#: ../system/integrations/cti/sipgate.rst:2 -msgid "Sipgate (sipgate.io)" +#: ../system/core-workflows/condition-operators.rst:41 +msgid "Matches if one specified value is not present." msgstr "" -#: ../system/integrations/cti/sipgate.rst:16 -msgid "You need an administrative Sipgate account for your organization." +#: ../system/core-workflows/condition-operators.rst:42 +msgid "does not match regex" msgstr "" -#: ../system/integrations/cti/sipgate.rst:17 -msgid "" -"Zammad requires a ``sipgate.io`` addon from the feature store (please note " -"that API calls are not free with Sipgate. Rates may apply and differ from " -"account to account)." +#: ../system/core-workflows/condition-operators.rst:43 +msgid "Matches if content doesn't fit to regex rule." msgstr "" -#: ../system/integrations/cti/sipgate.rst:21 -msgid "Sipgate must be able to reach your Zammad instance." +#: ../system/core-workflows/condition-operators.rst:44 +msgid "ends with" msgstr "" -#: ../system/integrations/cti/sipgate.rst:25 -msgid ":doc:`provider-configurations/sipgate`" +#: ../system/core-workflows/condition-operators.rst:45 +msgid "Matches if content ends with specified value." msgstr "" -#: ../system/integrations/cti/sipgate.rst:24 -msgid "" -"Learn how to configure Sipgate to enable Zammad and Sipgate to communicate " -"with each other." +#: ../system/core-workflows/condition-operators.rst:46 +msgid "ends with one of" msgstr "" -#: ../system/integrations/cti/sipgate.rst:33 -msgid "" -"Below endpoint settings affect the :doc:`sipgate.io configuration `." +#: ../system/core-workflows/condition-operators.rst:47 +msgid "Matches if content ends with one of the specified values." msgstr "" -#: ../system/integrations/cti/sipgate.rst:37 -msgid "This endpoint is required for incoming call hooks." +#: ../system/core-workflows/condition-operators.rst:48 +msgid "from (relative)" msgstr "" -#: ../system/integrations/cti/sipgate.rst:40 -msgid "This endpoint is required for outgoing call hooks." +#: ../system/core-workflows/condition-operators.rst:49 +msgid "Matches if date/time is after a period of time after an event." msgstr "" -#: ../system/integrations/cti/sipgate.rst:0 -msgid "Screenshot showing sample user mappings in between Sipgate and Zammad" +#: ../system/core-workflows/condition-operators.rst:51 +msgid "Matches if content is equal to a specified value." msgstr "" -#: ../system/integrations/cti/sipgate.rst:69 -msgid "" -"You can find your agent's Sipgate username within ``Accountverwaltung → " -"Benutzer``. You're looking for the SIP-ID." +#: ../system/core-workflows/condition-operators.rst:52 +msgid "is any of" msgstr "" -#: ../system/integrations/cti/sipgate.rst:0 -msgid "Sample VoIP credentials for a Sipgate user" +#: ../system/core-workflows/condition-operators.rst:53 +msgid "Matches if content is equal to any of specified values." msgstr "" -#: ../system/integrations/cti/sipgate.rst:77 -msgid "Users with several devices also have several SIP-IDs." +#: ../system/core-workflows/condition-operators.rst:54 +msgid "is modified" msgstr "" -#: ../system/integrations/elasticsearch.rst:2 -msgid "Elasticsearch (SaaS)" +#: ../system/core-workflows/condition-operators.rst:55 +msgid "Matches if content is modified." msgstr "" -#: ../system/integrations/elasticsearch.rst:4 -msgid "" -"The Elasticsearch integration allows you to create a read-only user to use " -"with your favorite reporting tool (e.g. like Grafana)." +#: ../system/core-workflows/condition-operators.rst:57 +#: ../system/core-workflows/condition-operators.rst:61 +msgid "True from the moment of changing content until form submit." msgstr "" -#: ../system/integrations/elasticsearch.rst:7 -msgid "" -"If you want to take full advantage of the Zammad reporting, have a look at " -"our :docs:`Grafana ` " -"setup page as well." +#: ../system/core-workflows/condition-operators.rst:58 +msgid "is modified to" msgstr "" -#: ../system/integrations/elasticsearch.rst:11 -#: ../system/subscription/index.rst:7 -msgid "**🚧 Hosted environment specific 🚧**" +#: ../system/core-workflows/condition-operators.rst:59 +msgid "Matches if content is modified to a specific value." msgstr "" -#: ../system/integrations/elasticsearch.rst:13 -msgid "" -"This integration is only available for Hosted setups. In order to use " -"Elasticsearch you'll need the **Plus** subscription." +#: ../system/core-workflows/condition-operators.rst:62 +msgid "is none of" msgstr "" -#: ../system/integrations/elasticsearch.rst:16 -msgid "" -"Self hosted users have all the control over their self hosted Elasticsearch " -"instances." +#: ../system/core-workflows/condition-operators.rst:63 +msgid "Matches if content is none of any specified values." msgstr "" -#: ../system/integrations/elasticsearch.rst:None -msgid "Elasticsearch integration page on SaaS environments" +#: ../system/core-workflows/condition-operators.rst:65 +msgid "Matches if content is not equal to a specified value." msgstr "" -#: ../system/integrations/elasticsearch.rst:27 -msgid "" -"Please note the following limitations of Elasticsearch access on hosted " -"environments:" +#: ../system/core-workflows/condition-operators.rst:67 +msgid "Matches if content is present." msgstr "" -#: ../system/integrations/elasticsearch.rst:30 -msgid "access to the Elasticsearch index is read-only access" +#: ../system/core-workflows/condition-operators.rst:68 +msgid "just changed" msgstr "" -#: ../system/integrations/elasticsearch.rst:31 -msgid "currently you're limited to user only" +#: ../system/core-workflows/condition-operators.rst:69 +msgid "Matches if content has changed." msgstr "" -#: ../system/integrations/elasticsearch.rst:32 +#: ../system/core-workflows/condition-operators.rst:71 +#: ../system/core-workflows/condition-operators.rst:75 msgid "" -"Reporting tools that require to write into the indexes (like Kibana) are not " -"supported" +"Only true for the moment of changing content until next form field action/" +"click." msgstr "" -#: ../system/integrations/elasticsearch.rst:34 -msgid "IP access restriction is currently not yet supported" +#: ../system/core-workflows/condition-operators.rst:72 +msgid "just changed to" msgstr "" -#: ../system/integrations/elasticsearch.rst:37 -msgid "Activating Elasticsearch Access" +#: ../system/core-workflows/condition-operators.rst:73 +msgid "Matches if content has changed to a specified value." msgstr "" -#: ../system/integrations/elasticsearch.rst:39 -msgid "" -"By default external access to your Elasticsearch index is not active. You " -"can enable the integration at any time if needed." +#: ../system/core-workflows/condition-operators.rst:76 +msgid "matches regex" msgstr "" -#: ../system/integrations/elasticsearch.rst:42 -msgid "" -"Please ensure to note down the password provided - you won't have access to " -"it afterwards." +#: ../system/core-workflows/condition-operators.rst:77 +msgid "Matches if value fits to regex rule." msgstr "" -#: ../system/integrations/elasticsearch.rst:None -msgid "Screencast showing activation of Elasticsearch integration" +#: ../system/core-workflows/condition-operators.rst:79 +msgid "Matches if no content is present." msgstr "" -#: ../system/integrations/elasticsearch.rst:51 -msgid "Connection Settings" +#: ../system/core-workflows/condition-operators.rst:80 +msgid "starts with" msgstr "" -#: ../system/integrations/elasticsearch.rst:53 -msgid "" -"This section holds the most important general information for accessing your " -"Elasticsearch indexes - such as:" -msgstr "" - -#: ../system/integrations/elasticsearch.rst:57 -msgid "A unique subdomain that does not tell your real instance URL." +#: ../system/core-workflows/condition-operators.rst:81 +msgid "Matches if content starts with specified value." msgstr "" -#: ../system/integrations/elasticsearch.rst:61 -msgid "Software" +#: ../system/core-workflows/condition-operators.rst:82 +msgid "starts with one of" msgstr "" -#: ../system/integrations/elasticsearch.rst:60 -msgid "" -"The major version of the search index being used. This is required by some " -"Reporting tools like Grafana." +#: ../system/core-workflows/condition-operators.rst:83 +msgid "Matches if content starts with one of the specified values." msgstr "" -#: ../system/integrations/elasticsearch.rst:64 -msgid "Authentication" +#: ../system/core-workflows/condition-operators.rst:84 +msgid "till (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:64 -msgid "The authentication type being supported. ``Basic Authentication``" +#: ../system/core-workflows/condition-operators.rst:85 +msgid "Matches if date/time is before a period of time before an event." msgstr "" -#: ../system/integrations/elasticsearch.rst:67 -msgid "Available Indexes" +#: ../system/core-workflows/condition-operators.rst:86 +msgid "today" msgstr "" -#: ../system/integrations/elasticsearch.rst:69 -msgid "" -"Within this section we're displaying the -in our opinion- most important " -"indexes for a Zammad instance." +#: ../system/core-workflows/condition-operators.rst:87 +msgid "Matches if date/time is today." msgstr "" -#: ../system/integrations/elasticsearch.rst:72 -msgid "" -"If you require all indexes or our listing is not good enough for you, point " -"your browser to the URL we're providing and append ``/_aliases?" -"pretty=true``. The result should look like this: ``https://.zammad.com/" -"_aliases?pretty=true``." +#: ../system/core-workflows/condition-operators.rst:88 +msgid "within last (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:77 +#: ../system/core-workflows/condition-operators.rst:89 msgid "" -"Your browser will automatically ask for your credentials - you'll then see " -"something like this:" +"Matches if date/time content is within specified period of time before now." msgstr "" -#: ../system/integrations/elasticsearch.rst:125 -msgid "Credentials" +#: ../system/core-workflows/condition-operators.rst:91 +msgid "within next (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:127 +#: ../system/core-workflows/condition-operators.rst:92 msgid "" -"Within this section Zammad displays your available users. The password is " -"provided once (upon activation) and cannot be retrieved after that." +"Matches if date/time content is within specified period of time after now." msgstr "" -#: ../system/integrations/elasticsearch.rst:131 -msgid "" -"If you need to change or reset your Elasticsearch user password, use the " -"\"Reset password\" button in the credentials table. Doing so creates a brand " -"new password for the account in question. This change is immediate, keep in " -"mind that this may affect third party tools connected to your instance." +#: ../system/core-workflows/how-do-they-work.rst:2 +msgid "How do they work?" msgstr "" -#: ../system/integrations/exchange.rst:2 -msgid "Exchange" +#: ../system/core-workflows/how-do-they-work.rst:4 +msgid "" +"Core Workflows are executed according to their priority. If two workflows " +"have the same priority, they are executed in alphabetical order based on " +"their **name**." msgstr "" -#: ../system/integrations/exchange.rst:4 +#: ../system/core-workflows/how-do-they-work.rst:8 msgid "" -"With Zammad's Exchange integration, you can easily use existing address " -"books without having to update more than one source." +"Because of the way Core Workflows work, all changes to attributes are " +"checked with the application server - please see :doc:`limitations` for " +"possible issues." msgstr "" -#: ../system/integrations/exchange.rst:7 +#: ../system/core-workflows/how-do-they-work.rst:12 msgid "" -"However, you should refrain from syncing all addresses, as the results may " -"not be what you expect (Exchange collects huge amounts of addresses). A " -"central address book of your company to sync makes more sense, as you can " -"ensure that Zammad gets only the data you need and want. Apart from this, it " -"is even not possible to sync the Global Address List (GAL) of your Exchange " -"system with Zammad." +"Below we're talking about settings that are important and not self-" +"explanatory." msgstr "" -#: ../system/integrations/exchange.rst:16 +#: ../system/core-workflows/how-do-they-work.rst:17 msgid "" -"**Exchange and LDAP:** The exchange sync can be overruled by Zammad's LDAP " -"integration. If you have the same users in both sources, the LDAP version " -"will always be Zammad's pick." +"Choose the object context you want to run the workflow in. This will decide " +"on your available attributes and actions." msgstr "" -#: ../system/integrations/exchange.rst:19 -msgid "" -"**One way sync:** the Exchange sync is one way. Exchange => Zammad. Changes " -"to your users inside of Zammad might be overwritten by the Exchange sync." +#: ../system/core-workflows/how-do-they-work.rst:20 +msgid "Ticket objects also have access to the ticket customer." msgstr "" -#: ../system/integrations/exchange.rst:24 +#: ../system/core-workflows/how-do-they-work.rst:25 msgid "" -"To configure Exchange integration, simply go to the System > Integrations > " -"Exchange in the admin panel. Press \"change\" and follow the wizard for " -"adding the needed Exchange information to Zammad. On the last two steps " -"Zammad will ask you for the address book(s) and your desired attribute " -"mapping. By default, Zammad only maps email address, first- and lastname. " -"Technically, you can map any Exchange object to a Zammad user object (this " -"also works for custom objects!)." +"Choose in which situation the workflow is applied. Contexts can be combined " +"to avoid duplicate workflows." msgstr "" -#: ../system/integrations/exchange.rst:35 -msgid "" -"If the SSL verification fails while connecting to Exchange, Zammad will ask " -"you to turn it off temporarily." +#: ../system/core-workflows/how-do-they-work.rst:30 +msgid "Creation mask" msgstr "" -#: ../system/integrations/exchange.rst:38 +#: ../system/core-workflows/how-do-they-work.rst:29 msgid "" -"Please be aware that **turning off SSL verification is a security risk**. It " -"should only be used temporarily or for testing purposes. If turned off, " -"there is no verification of the certificate, which means that every " -"presented certificate will be accepted." +"If selected, your conditions and actions will affect all applicable creation " +"masks." msgstr "" -#: ../system/integrations/exchange.rst:43 -msgid "" -"After pressing Continue, Zammad will check if the configuration is okay. You " -"can then enable Exchange and start your first sync. The sync will then run " -"hourly - if you need to change mappings or the address book(s), you can " -"change the configuration at any time." +#: ../system/core-workflows/how-do-they-work.rst:34 +msgid "Edit mask" msgstr "" -#: ../system/integrations/exchange.rst:50 +#: ../system/core-workflows/how-do-they-work.rst:33 msgid "" -"After the sync has finished, you can find the new Exchange contacts under " -"\"Users\". Zammad integrates them just as normal users." +"If selected, your conditions and actions will affect all applicable edit " +"masks." msgstr "" -#: ../system/integrations/exchange.rst:55 +#: ../system/core-workflows/how-do-they-work.rst:39 msgid "" -"In some cases you might see unique IDs as \"Login\" instead of the email " -"address. This is normal and doesn't affect the login or email mapping for " -"that entry." +"Zammad differentiates between selected and saved conditions. These can be " +"combined wherever needed." msgstr "" -#: ../system/integrations/github.rst:4 -msgid "" -"Use GitHub integration to track GitHub issues directly within Zammad " -"tickets. Add issue hyperlinks and get a live summary of metadata like status " -"(open/closed), assignee, labels, and more." +#: ../system/core-workflows/how-do-they-work.rst:42 +msgid "**⚠️ Restrict workflows to specific roles if needed!**" msgstr "" -#: ../system/integrations/github.rst:8 -msgid "Please note that our GitHub integration does not support pull requests." +#: ../system/core-workflows/how-do-they-work.rst:44 +msgid "" +"By default and unless configured in conditions, workflow rules are executed " +"for **all roles**. This also affects your customers!" msgstr "" -#: ../system/integrations/github.rst:None -msgid "Integration page for GitHub" +#: ../system/core-workflows/how-do-they-work.rst:50 +msgid "Selected Conditions" msgstr "" -#: ../system/integrations/github.rst:18 +#: ../system/core-workflows/how-do-they-work.rst:48 msgid "" -"In your GitHub settings, create a new API token under **Developer settings > " -"Personal access tokens > Generate new token**. Leave the **Scopes** section " -"empty." +"These conditions are based on form values and match if an appropriate " +"selection is made (e.g. choosing another group in the ticket without " +"saving). This applies for drafts (active selection) and currently saved " +"values." msgstr "" -#: ../system/integrations/github.rst:0 ../system/integrations/gitlab.rst:0 -msgid "Screencast showing how to create a new API token" +#: ../system/core-workflows/how-do-they-work.rst:64 +msgid "Saved Conditions" msgstr "" -#: ../system/integrations/github.rst:27 -msgid "Create a new API key with no scopes/privileges." +#: ../system/core-workflows/how-do-they-work.rst:53 +msgid "" +"These conditions only match if the selected values are stored in the " +"database. It ignores the current value or selection of the field, as long as " +"the changes are not saved (e.g. performing field operations for an existing " +"ticket, which is viewed/opened by an agent)." msgstr "" -#: ../system/integrations/github.rst:29 -msgid "🔒 **Will this work for private repos?**" +#: ../system/core-workflows/how-do-they-work.rst:60 +msgid "" +"Keep in mind that the value has to be available in the situation where you " +"need it. Otherwise the condition won't match." msgstr "" -#: ../system/integrations/github.rst:31 +#: ../system/core-workflows/how-do-they-work.rst:63 msgid "" -"No. To link private repo issues, **use the** ``repo`` **scope instead**. " -"Bear in mind that the resulting token will have `lots of permissions that it " -"doesn't actually need `_, which presents a security risk if your token ever falls into " -"the wrong hands." +"Example: you can't perform any actions with *saved condition* on a ticket in " +"creation, because there are no saved values at that time." msgstr "" -#: ../system/integrations/github.rst:37 +#: ../system/core-workflows/how-do-they-work.rst:66 msgid "" -"Unfortunately, because of how GitHub's OAuth token scopes are set up, this " -"is the only way to link issues on private repos." +"You can find a description of the condition operators for core workflows :" +"doc:`here `." msgstr "" -#: ../system/integrations/github.rst:40 -msgid "Enter your new API token in Zammad and enable GitHub integration." +#: ../system/core-workflows/how-do-they-work.rst:72 +msgid "" +"Which actions should we run on the relevant fields? The possible actions " +"depend on the object type. However, usually you can at least change the " +"visibility and whether the field is mandatory." msgstr "" -#: ../system/integrations/github.rst:0 -msgid "Screencast showing how to configure Zammad's GitHub integration" +#: ../system/core-workflows/how-do-they-work.rst:76 +msgid "Be aware that actions are not available for **related** context." msgstr "" -#: ../system/integrations/github.rst:47 +#: ../system/core-workflows/how-do-they-work.rst:78 msgid "" -"Use the default API endpoint (``https://api.github.com/graphql``) unless " -"you're using GitHub Enterprise Server." +"**Example:** Let's assume you are working in the ticket context. While you " +"can have customer *conditions*, you *can't adjust* objects with actions in " +"that scope. That's because this wouldn't have any impact on the ticket " +"dialog. Of course all ticket attributes (state, owner, ...) are available." msgstr "" -#: ../system/integrations/github.rst:50 +#: ../system/core-workflows/how-do-they-work.rst:84 msgid "" -"Once completed, a new GitHub issues tab will appear in the ticket pane. 🎉" +"Please also have a look at our :doc:`limitations` to be safe from surprises." msgstr "" -#: ../system/integrations/github.rst:59 ../system/integrations/gitlab.rst:52 -msgid "Token verification is taking a long time" +#: ../system/core-workflows/how-do-they-work.rst:88 +msgid "Available Operators" msgstr "" -#: ../system/integrations/github.rst:56 ../system/integrations/gitlab.rst:49 -msgid "" -"Slight delays are normal (<2 min.), especially for systems under heavy load." +#: ../system/core-workflows/how-do-they-work.rst:90 +msgid "The availability of operators depends on the object type and scope." msgstr "" -#: ../system/integrations/github.rst:58 +#: ../system/core-workflows/how-do-they-work.rst:94 msgid "" -"Self-hosted administrators, please check your network settings to ensure " -"that your Zammad server can reach ``api.github.com``." +"Please note that actions may or may not restrict API based access to " +"attributes. We're displaying the following icons for your overview to " +"understand these limits better:" msgstr "" -#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 -msgid "I reloaded the page and now the API token is gone" +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|api| This icon indicates the action affects the API." msgstr "" -#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 -msgid "" -"This may indicate that Zammad is still verifying your API token. Try " -"reloading the page again in a couple minutes." +#: ../system/core-workflows/how-do-they-work.rst:163 +msgid "api" msgstr "" -#: ../system/integrations/gitlab.rst:2 -msgid "GitLab" +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|ui| This icon indicates the action only affects the web interface." msgstr "" -#: ../system/integrations/gitlab.rst:4 -msgid "" -"Use GitLab integration to track GitLab issues directly within Zammad " -"tickets. Add issue hyperlinks and get a live summary of metadata like status " -"(open/closed), assignee, labels, and more." +#: ../system/core-workflows/how-do-they-work.rst:167 +msgid "ui" msgstr "" -#: ../system/integrations/gitlab.rst:8 -msgid "" -"Please note that our GitLab integration does not support merge requests." +#: ../system/core-workflows/how-do-they-work.rst:102 +msgid "show |ui|" msgstr "" -#: ../system/integrations/gitlab.rst:None -msgid "Integration page for GitLab" +#: ../system/core-workflows/how-do-they-work.rst:102 +msgid "Display the chosen field. Allows setting of values." msgstr "" -#: ../system/integrations/gitlab.rst:18 -msgid "" -"In your GitLab preferences, create a new API token under **Access Tokens**." +#: ../system/core-workflows/how-do-they-work.rst:109 +msgid "hide |ui|" msgstr "" -#: ../system/integrations/gitlab.rst:20 -msgid "Under **Select scopes**, choose ``read_api`` only." +#: ../system/core-workflows/how-do-they-work.rst:105 +msgid "" +"Hide the chosen field. However, it technically still allows setting the " +"field." msgstr "" -#: ../system/integrations/gitlab.rst:27 -msgid "🔒 **If you wish to link issues on any private repos...**" +#: ../system/core-workflows/how-do-they-work.rst:108 +msgid "" +"Please note that the field is **not** gone and still contains an existing " +"value (if set)! Consider *remove* instead, if you want this field to be gone." msgstr "" -#: ../system/integrations/gitlab.rst:29 -msgid "Your API token must belong to an account with access to those repos." +#: ../system/core-workflows/how-do-they-work.rst:112 +msgid "remove |ui|" msgstr "" -#: ../system/integrations/gitlab.rst:31 -msgid "Enter your new API token in Zammad and enable GitLab integration." +#: ../system/core-workflows/how-do-they-work.rst:112 +msgid "Entirely removes the field. The field value will not be evaluated." msgstr "" -#: ../system/integrations/gitlab.rst:0 -msgid "Screencast showing how to configure Zammad's GitLab integration" +#: ../system/core-workflows/how-do-they-work.rst:115 +msgid "set mandatory |ui| |api|" msgstr "" -#: ../system/integrations/gitlab.rst:40 -msgid "" -"Use the default API endpoint (``https://gitlab.com/api/graphql``) unless " -"you're a self-hosted GitLab user." +#: ../system/core-workflows/how-do-they-work.rst:115 +msgid "Sets the field to mandatory." msgstr "" -#: ../system/integrations/gitlab.rst:43 -msgid "" -"Once completed, a new GitLab issues tab will appear in the ticket pane. 🎉" +#: ../system/core-workflows/how-do-they-work.rst:118 +msgid "set optional |ui| |api|" msgstr "" -#: ../system/integrations/gitlab.rst:51 -msgid "" -"Self-hosted administrators, please check your network settings to ensure " -"that your Zammad server can reach ``gitlab.com``." +#: ../system/core-workflows/how-do-they-work.rst:118 +msgid "Sets the field to optional." msgstr "" -#: ../system/integrations/i-doit.rst:2 -msgid "i-doit" +#: ../system/core-workflows/how-do-they-work.rst:124 +msgid "add option |ui| |api|" msgstr "" -#: ../system/integrations/i-doit.rst:4 -msgid "" -"`i-doit `_ is an open-source **configuration " -"management database** - in other words, a tool for keeping tabs on every " -"single piece of your physical and digital infrastructure, from network " -"equipment to virtual machines on down to the faceplates on your rack shelves " -"and more." +#: ../system/core-workflows/how-do-they-work.rst:121 +msgid "Allows adding options to tree selects or selects." msgstr "" -#: ../system/integrations/i-doit.rst:10 +#: ../system/core-workflows/how-do-they-work.rst:123 msgid "" -"What's that got to do with Zammad? Well, if you used tickets to track issues " -"with all that hardware, you might start wishing there was a way they could " -"talk to each other." -msgstr "" - -#: ../system/integrations/i-doit.rst:14 -msgid "Zammad gives you two:" +"You have to use the \"remove option\" before performing this action. It " +"allows you to use *existing* configured values." msgstr "" -#: ../system/integrations/i-doit.rst:17 -msgid "1. Add i-doit Links to Zammad Tickets" +#: ../system/core-workflows/how-do-they-work.rst:128 +msgid "remove option |ui| |api|" msgstr "" -#: ../system/integrations/i-doit.rst:20 ../system/integrations/i-doit.rst:80 -msgid "What Users See" +#: ../system/core-workflows/how-do-they-work.rst:127 +msgid "" +"Allows removing options from tree selects or selects. It allows you to use " +"*existing* configured values." msgstr "" -#: ../system/integrations/i-doit.rst:26 -msgid "i-doit integration in Zammad's ticket pane" +#: ../system/core-workflows/how-do-they-work.rst:134 +msgid "set fixed to |ui| |api|" msgstr "" -#: ../system/integrations/i-doit.rst:26 -msgid "" -"The i-doit integration will appear under a new 🖨 tab in the ticket pane." +#: ../system/core-workflows/how-do-they-work.rst:131 +msgid "Reduces the available options by your selection." msgstr "" -#: ../system/integrations/i-doit.rst:28 +#: ../system/core-workflows/how-do-they-work.rst:133 msgid "" -"i-doit integration puts a new tab in Zammad's ticket pane where you can add " -"links to existing i-doit devices for easy reference. (See our :user-docs:" -"`user documentation ` to learn " -"how it works in practice)." +"This reduces your workflows in terms of *add option* and *remove option*." msgstr "" -#: ../system/integrations/i-doit.rst:36 ../system/integrations/i-doit.rst:93 -msgid "How to Set it Up" +#: ../system/core-workflows/how-do-they-work.rst:137 +msgid "fill in |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:38 -msgid "" -"It requires i-doit's `API Add-on `_. Make sure to have it properly set up. Use the following setting:" +#: ../system/core-workflows/how-do-they-work.rst:137 +msgid "Allows filling in of string and integer fields with your values." msgstr "" -#: ../system/integrations/i-doit.rst:42 -msgid "Active: ``Yes``" +#: ../system/core-workflows/how-do-they-work.rst:141 +msgid "fill in empty |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:43 -msgid "Enforce authentication by username and password: ``No``" +#: ../system/core-workflows/how-do-they-work.rst:140 +msgid "" +"Allows filling in of string and integer fields with your values **if the " +"field is empty**." msgstr "" -#: ../system/integrations/i-doit.rst:45 -msgid "" -"To set it up, enable the integration in the Zammad admin panel under " -"**System > Integrations > i-doit**:" +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "select |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "i-doit settings within the integration pages" +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "Select a specific value within a select, tree select or boolean field." msgstr "" -#: ../system/integrations/i-doit.rst:53 -msgid "The root URL of your i-doit installation." +#: ../system/core-workflows/how-do-they-work.rst:153 +msgid "auto select |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:62 -msgid "API token" +#: ../system/core-workflows/how-do-they-work.rst:147 +msgid "Helps users with tree select and select fields:" msgstr "" -#: ../system/integrations/i-doit.rst:56 +#: ../system/core-workflows/how-do-they-work.rst:149 msgid "" -"Found in the i-doit admin panel under **Interfaces / external data > JSON-" -"RPC API > Common Settings**." +"If the field has only one option available for selection and no value yet, " +"the value will be automatically set." msgstr "" -#: ../system/integrations/i-doit.rst:0 -msgid "i-doit administration interface with API configuration" +#: ../system/core-workflows/how-do-they-work.rst:152 +msgid "" +"This option only works if you have one value and doesn't work if there is " +"more than one option available." msgstr "" -#: ../system/integrations/i-doit.rst:67 -msgid "Client ID" +#: ../system/core-workflows/how-do-they-work.rst:157 +msgid "set readonly |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:65 -msgid "A unique name to identify Zammad within i-doit." +#: ../system/core-workflows/how-do-they-work.rst:156 +msgid "" +"Allows you to display an attribute as read only (which means no changes are " +"possible)." msgstr "" -#: ../system/integrations/i-doit.rst:67 -msgid "(Zammad does not require you to enter a value here, but i-doit might!)" +#: ../system/core-workflows/how-do-they-work.rst:161 +msgid "unset readonly |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:70 +#: ../system/core-workflows/how-do-they-work.rst:160 msgid "" -"Here you can decide if the certificate of your i-doit system has to be " -"verified or not. In case you are using custom certificates, please have a " -"look at :doc:`how to add them to Zammad `." -msgstr "" - -#: ../system/integrations/i-doit.rst:77 -msgid "2. List / Create Zammad Tickets in i-doit" +"In case a workflow set the field in question to read only, you can undo this " +"with option above." msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "Zammad integration in i-doit's device view" +#: ../system/core-workflows/how-do-they-work.rst:172 +msgid "Stop after match" msgstr "" -#: ../system/integrations/i-doit.rst:86 +#: ../system/core-workflows/how-do-they-work.rst:174 msgid "" -"i-doit's ticket system integration gives you a way to see all the tickets " -"for a given device without ever leaving i-doit. (See our :user-docs:`user " -"documentation ` to learn how it " -"works in practice)." +"Here you can decide if other workflows are executed after the current one." msgstr "" -#: ../system/integrations/i-doit.rst:95 +#: ../system/core-workflows/how-do-they-work.rst:176 msgid "" -"Enable this integration in the i-doit admin panel under **Interfaces / " -"external data > Trouble Ticket System (TTS) > Configuration**:" +"If set to ``no`` (default), further workflows will be executed if they match " +"the condition. In this case, it is possible that your actions from the " +"current workflow can be overwritten by another workflow." msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "i-doit administration interface with TTS configuration" +#: ../system/core-workflows/how-do-they-work.rst:180 +msgid "" +"If set to ``yes``, no further worflows will be executed after the current " +"one." msgstr "" -#: ../system/integrations/i-doit.rst:104 -msgid "TTS-Type" +#: ../system/core-workflows/how-do-they-work.rst:184 +msgid "Priority" msgstr "" -#: ../system/integrations/i-doit.rst:104 -msgid "``Zammad``" +#: ../system/core-workflows/how-do-they-work.rst:186 +msgid "" +"You can define the sequence, in which the workflows are executed. The " +"default value is ``500``." msgstr "" -#: ../system/integrations/i-doit.rst:115 -msgid "Username / Password" +#: ../system/core-workflows/how-do-they-work.rst:189 +msgid "" +"The workflows are executed in ascending order by their priority. That means " +"lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." msgstr "" -#: ../system/integrations/i-doit.rst:107 -msgid "Login credentials for a Zammad agent." +#: ../system/core-workflows/learn-by-example.rst:2 +msgid "Learn by Example" msgstr "" -#: ../system/integrations/i-doit.rst:109 +#: ../system/core-workflows/learn-by-example.rst:4 msgid "" -"This agent must have **read permission** for all :doc:`groups ` that plan on using the i-doit integration." +"This page provides some basic examples for Core Workflows. Of course you can " +"build much more complex workflows if needed." msgstr "" -#: ../system/integrations/i-doit.rst:113 +#: ../system/core-workflows/learn-by-example.rst:7 msgid "" -"You may even wish to create a dedicated agent account just for this " -"integration (otherwise, if the agent ever changes her password, you will " -"have to remember to update it here)." +"To learn about Core Workflows in detail, first go to :doc:`how-do-they-work`." msgstr "" -#: ../system/integrations/i-doit.rst:117 -msgid "URL incl. protocol" +#: ../system/core-workflows/learn-by-example.rst:10 +msgid "Group Based Examples" msgstr "" -#: ../system/integrations/i-doit.rst:118 -msgid "``https://your.zammad.domain``" +#: ../system/core-workflows/learn-by-example.rst:12 +msgid "" +"All following workflows have the same base configurations. The workflow may " +"not use them all." msgstr "" -#: ../system/integrations/index.rst:2 -msgid "Integrations" +#: ../system/core-workflows/learn-by-example.rst:15 +msgid "Groups:" msgstr "" -#: ../system/integrations/index.rst:4 +#: ../system/core-workflows/learn-by-example.rst:20 +msgid "Attributes:" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:22 +msgid "Category (Single tree selection field, not mandatory, agents only)" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:23 msgid "" -"Zammad offers numerous integrations that add rich features to your instance." +"Approved (Boolean field, not mandatory, not shown, ``false`` as default)" msgstr "" -#: ../system/integrations/index.rst:6 -msgid "We're still working on this part of our documentation, stay tight!" +#: ../system/core-workflows/learn-by-example.rst:24 +msgid "Operating System (Text field, not mandatory, not shown)" msgstr "" -#: ../system/integrations/index.rst:10 -msgid "Integrations for Phone Systems" +#: ../system/core-workflows/learn-by-example.rst:25 +msgid "Software used (Single selection field, not mandatory, not shown)" msgstr "" -#: ../system/integrations/index.rst:14 -msgid "" -"Your VoIP provider or telephony system is not listed? Possibly your provider " -"supports Zammad by using the generic CTI - if you're unsure ask your " -"provider." +#: ../system/core-workflows/learn-by-example.rst:68 +msgid "Group specific values and fields" msgstr "" -#: ../system/integrations/index.rst:18 +#: ../system/core-workflows/learn-by-example.rst:28 msgid "" -"Provider does not support Zammad? Consider creating a `feature request in " -"the Zammad Community `_." +"This workflow set depends on the category field. It reduces the available " +"set of values based on the group selected." msgstr "" -#: ../system/integrations/index.rst:31 -msgid "Integrations for Authentication and Customers" +#: ../system/core-workflows/learn-by-example.rst:33 +msgid "Workflow 2nd Level group" msgstr "" -#: ../system/integrations/index.rst:44 -msgid "Integrations for Monitoring Systems" +#: ../system/core-workflows/learn-by-example.rst:35 +msgid "" +"This reduces the category options to ``2nd Level/*``, ``Internal/*`` and " +"``Others``. It also sets further required fields to mandatory and visible." msgstr "" -#: ../system/integrations/index.rst:46 -msgid "This section currently misses the following integrations:" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for 2nd level" msgstr "" -#: ../system/integrations/index.rst:48 -msgid "Icinga" +#: ../system/core-workflows/learn-by-example.rst:43 +msgid "Workflow Support group" msgstr "" -#: ../system/integrations/index.rst:49 -msgid "Monit" +#: ../system/core-workflows/learn-by-example.rst:45 +msgid "" +"This reduces the category options to ``Support/*``, ``Internal/*`` and " +"``Others``. It also sets further required fields to visible." msgstr "" -#: ../system/integrations/index.rst:50 -msgid "Nagios" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for support" msgstr "" -#: ../system/integrations/index.rst:60 -msgid "Integrations for Issue Trackers" +#: ../system/core-workflows/learn-by-example.rst:53 +msgid "Workflow Sales group" msgstr "" -#: ../system/integrations/index.rst:70 -msgid "Other Integrations" +#: ../system/core-workflows/learn-by-example.rst:55 +msgid "" +"This reduces the category options to ``Sales/*``, ``Internal/*`` and " +"``Others``." msgstr "" -#: ../system/integrations/index.rst:72 -msgid "" -"This section will hold any other integration that can't be grouped up (yet)." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for sales" msgstr "" -#: ../system/integrations/ldap/index.rst:2 -msgid "LDAP / Active Directory" +#: ../system/core-workflows/learn-by-example.rst:68 +#: ../system/integrations/slack.rst:88 +msgid "The Result" msgstr "" -#: ../system/integrations/ldap/index.rst:4 +#: ../system/core-workflows/learn-by-example.rst:63 msgid "" -"Zammad comes with a powerful LDAP integration that allows you to have a " -"single source of truth. By this you reduce the number of login credentials " -"your user has to remember." +"This is what the agent would experience with the above workflows in place." msgstr "" -#: ../system/integrations/ldap/index.rst:10 +#: ../system/core-workflows/learn-by-example.rst:0 msgid "" -"The LDAP source is also a perfect candidate for Zammad's :docs:`Kerberos " -"Single Sign-On ` but also works as addition " -"to other :doc:`/settings/security/third-party`." +"Workflow shows objects and limits options based on selections on the group" msgstr "" -#: ../system/integrations/ldap/index.rst:None -msgid "Zammands LDAP management page" +#: ../system/core-workflows/learn-by-example.rst:90 +msgid "Approval process" msgstr "" -#: ../system/integrations/ldap/index.rst:25 -msgid "📝 :doc:`manage`" +#: ../system/core-workflows/learn-by-example.rst:71 +msgid "" +"In this case ``approved`` is visible to agents by default. For this " +"workflow, an additional role ``Approval person`` is required (no further " +"permissions)." msgstr "" -#: ../system/integrations/ldap/index.rst:25 -msgid "Add, modify, remove or re-arrange your LDAP-Sources as needed." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that restricts an approval attribute to specific roles" msgstr "" -#: ../system/integrations/ldap/index.rst:30 -msgid "Before you continue, please note the following limitations." +#: ../system/core-workflows/learn-by-example.rst:81 +msgid "" +"This workflow may work best in combination with a :doc:`trigger ` but technically, this is not required." msgstr "" -#: ../system/integrations/ldap/index.rst:32 -msgid "Mapping / Synchronizing organizations is not possible" +#: ../system/core-workflows/learn-by-example.rst:84 +msgid "" +"Select fields may be a better approach because they allow more values than " +"just a simple ``true`` or ``false``." msgstr "" -#: ../system/integrations/ldap/index.rst:36 +#: ../system/core-workflows/learn-by-example.rst:0 msgid "" -"You may want to consider using domain based assignments to overcome this " -"issue. Learn more on :doc:`/manage/organizations/index`." +"Workflow fixes possible values of \"Approved ?\" to a specific selection " +"depending on the users role" msgstr "" -#: ../system/integrations/ldap/index.rst:39 +#: ../system/core-workflows/learn-by-example.rst:103 +msgid "State dependent mandatory fields" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:93 msgid "" -"Zammad's LDAP sync is one way. Editing user settings or permissions may be " -"overwritten upon the next sync depending on your configuration." +"This workflow sets ``Category`` to mandatory if the agent wants to set the " +"states ``closed`` or ``pending close`` to enforce categorization." msgstr "" -#: ../system/integrations/ldap/index.rst:41 -msgid "Nested groups are not supported." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that sets fields to mandatory on specific states" msgstr "" -#: ../system/integrations/ldap/index.rst:42 -msgid "Synchronizing user avatars from LDAP is not supported." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "" +"Workflow sets category field to mandatory upon choosing closed or pending " +"close as state" msgstr "" -#: ../system/integrations/ldap/index.rst:43 -msgid "Unlike user filters, group filters cannot be changed." +#: ../system/core-workflows/learn-by-example.rst:106 +msgid "Manual Ticket Handover Process" msgstr "" -#: ../system/integrations/ldap/index.rst:44 -msgid "" -"When a user originates from an LDAP server, Zammad will try to verify the " -"login credentials against LDAP first - if this fails Zammad will check its " -"local database." +#: ../system/core-workflows/learn-by-example.rst:108 +msgid "This example covers the handover of a ticket from one agent to another:" msgstr "" -#: ../system/integrations/ldap/index.rst:50 +#: ../system/core-workflows/learn-by-example.rst:110 msgid "" -"Users can have local passwords even if they're LDAP users! You can learn " -"more about user accounts in general on :doc:`/manage/users/index`." +"When the ticket owner is modified, a new text field (\"Handover\") shows up " +"for a comment" msgstr "" -#: ../system/integrations/ldap/index.rst:54 +#: ../system/core-workflows/learn-by-example.rst:112 msgid "" -"When several LDAP sources contain the same user (meaning the same email " -"address), the user in question will be updated with every source configured. " -"*The last LDAP source will win.*" +"This may only be visible when the owner is changed, therefore it has to be " +"hidden in general" msgstr "" -#: ../system/integrations/ldap/index.rst:58 -msgid "" -"This is subject to change with `Issue 4109 `_ in the future." +#: ../system/core-workflows/learn-by-example.rst:114 +msgid "The input in this handover text field is mandatory" msgstr "" -#: ../system/integrations/ldap/index.rst:60 +#: ../system/core-workflows/learn-by-example.rst:115 msgid "" -"Synchronization statistics currently affect *all* configured LDAP sources. " -"This also applies for newly added or updated sources." +"After submitting changes, the value of the handover field must be added as " +"an note to the ticket (via trigger)" msgstr "" -#: ../system/integrations/ldap/index.rst:63 -msgid "" -"This is subject to change with `Issue 4108 `_ in the future." +#: ../system/core-workflows/learn-by-example.rst:121 +msgid "Hiding handover field" msgstr "" -#: ../system/integrations/ldap/index.rst:65 -msgid "" -"Zammad currently has limited fallback server support. You can workaround " -"this by providing several sources - however, ensure to have the exact same " -"configuration on your fallback." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Hiding the handover field in core workflows" msgstr "" -#: ../system/integrations/ldap/index.rst:69 -msgid "" -"This is subject to improve with `Issue 4107 `_ in the future." +#: ../system/core-workflows/learn-by-example.rst:126 +msgid "Showing handover field and setting it to mandatory" msgstr "" -#: ../system/integrations/ldap/index.rst:76 -msgid "" -"This section holds all requests Zammad handled for all LDAP sources. These " -"entries can either contain synchronization information or logins " -"(authentication attempts via Zammad's login interface)." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Showing the handover field and set it as mandatory" msgstr "" -#: ../system/integrations/ldap/index.rst:80 -msgid "" -"By clicking on any request, Zammad will provide even more information. The " -"provided information can be useful when something does not work as expected." +#: ../system/core-workflows/learn-by-example.rst:131 +msgid "Trigger writing handover input to a new article" msgstr "" -#: ../system/integrations/ldap/index.rst:85 -msgid "" -"Especially a LDAP synchronization can cause many log entries. The web " -"interface will always limit the number of shown entries to the last 50 " -"entries." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Write handover content to a new article" msgstr "" -#: ../system/integrations/ldap/index.rst:None +#: ../system/core-workflows/learn-by-example.rst:133 msgid "" -"Screencast showing LDAP integration log entries and a detail view on\n" -"an entry." +"As a result, the ticket includes an article of the type note which includes " +"the predefined text and the handover comment." msgstr "" -#: ../system/integrations/ldap/manage.rst:2 -msgid "Manage LDAP-Sources" +#: ../system/core-workflows/limitations.rst:6 +msgid "Core Workflows do not replace Triggers" msgstr "" -#: ../system/integrations/ldap/manage.rst:6 +#: ../system/core-workflows/limitations.rst:5 msgid "" -"Please keep in mind all current limitations for the LDAP synchronization. " -"This will help to understand scopes of the following operations better." +"Workflows manipulate the behavior of fields. However, they do not set values " +"in fields because of actions." msgstr "" -#: ../system/integrations/ldap/manage.rst:65 -msgid "Add new source" +#: ../system/core-workflows/limitations.rst:16 +msgid "API calls are only partly affected" msgstr "" -#: ../system/integrations/ldap/manage.rst:10 +#: ../system/core-workflows/limitations.rst:9 msgid "" -"Using the *New Source* button allows you to add new LDAP sources to your " -"installation. You're not limited in the number of sources, however, keep in " -"mind that many sources will also take more time to synchronize." +"Some options affect UI only and thus do not restrict responses and calls." msgstr "" -#: ../system/integrations/ldap/manage.rst:14 -msgid "" -"You can choose between different encryption types, namely *SSL* and " -"*STARTTLS* or none of them (\"*No SSL*\"). If you choose *SSL* or " -"*STARTTLS*, Zammad will display an additional *SSL verification* option that " -"allows you to disable the verification, e.g. for self-signed SSL " -"certificates. You can also tell Zammad to use a different port by appending " -"``:`` to your hostname/IP." +#: ../system/core-workflows/limitations.rst:11 +msgid "This affects the following actions:" msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "" -"Screenshot of configuring a new LDAP source with SSL encryption and SSL " -"verification" +#: ../system/core-workflows/limitations.rst:13 +msgid "select" msgstr "" -#: ../system/integrations/ldap/manage.rst:26 -msgid "" -"New Source with SSL transport security enabled and certificate verification" +#: ../system/core-workflows/limitations.rst:14 +msgid "auto select" msgstr "" -#: ../system/integrations/ldap/manage.rst:30 -msgid "" -"Using an user filter can be a good idea if you only require a small subset " -"of your LDAP users in Zammad." +#: ../system/core-workflows/limitations.rst:15 +msgid "show" msgstr "" -#: ../system/integrations/ldap/manage.rst:42 -msgid "This especially affects inactive users" +#: ../system/core-workflows/limitations.rst:16 +msgid "hide" msgstr "" -#: ../system/integrations/ldap/manage.rst:34 -msgid "" -"As every LDAP behaves differently on which attributes and how they are set, " -"Zammad doesn't care about any flags." +#: ../system/core-workflows/limitations.rst:25 +msgid "Some fields stay unavailable to customers" msgstr "" -#: ../system/integrations/ldap/manage.rst:37 +#: ../system/core-workflows/limitations.rst:19 msgid "" -"Users that no longer are returned by your LDAP source will automatically be " -"set to inactive. Zammad assumes that the user was deactivated." +"For technical and security reasons, some default fields (the pale ones you " +"can't edit) stay unavailable for display and usage on customer permissions." msgstr "" -#: ../system/integrations/ldap/manage.rst:41 +#: ../system/core-workflows/limitations.rst:23 msgid "" -"Users will never be removed automatically! If you want to remove obsolete " -"users, use :doc:`/system/data-privacy`." +"If you require your customers to change e.g. priorities, please consider " +"using workarounds via :doc:`/system/objects` and :doc:`/manage/trigger`." msgstr "" -#: ../system/integrations/ldap/manage.rst:46 -msgid "Active Directory admins" +#: ../system/core-workflows/limitations.rst:29 +msgid "Ticket title changes not supported in edit mask" msgstr "" -#: ../system/integrations/ldap/manage.rst:45 +#: ../system/core-workflows/limitations.rst:28 msgid "" -"Active Directories are quite specific on how to filter for active users only " -"- please see the `Microsoft documentation `_ for more " -"information." +"It is currently not possible to perform changes of the ticket title in the " +"edit mask (e.g. renaming, set to read-only)." msgstr "" -#: ../system/integrations/ldap/manage.rst:51 -msgid "" -"*Do not* manually write pathes of either LDAP attributes or groups. If " -"Zammad does not display them, it either cannot find them or you have a lot " -"of users that don't have the attributes populated." +#: ../system/core-workflows/limitations.rst:37 +msgid "What is out of scope of Core Workflows?" msgstr "" -#: ../system/integrations/ldap/manage.rst:55 +#: ../system/core-workflows/limitations.rst:32 msgid "" -"Zammad will always only return attributes that are filled - this reduces the " -"returned list of attributes greatly." +"There are some things that would count as workflow but are either done via :" +"doc:`/manage/trigger` or :doc:`/manage/scheduler`." msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing how to add a new LDAP source" +#: ../system/core-workflows/limitations.rst:35 +msgid "Such as (but not limited to):" msgstr "" -#: ../system/integrations/ldap/manage.rst:63 -msgid "" -"If your LDAP system doesn't allow anonymous bind, Zammad detects it and " -"provides you an editable \"Base DN\" *text* field instead of a prefilled " -"*select* field." +#: ../system/core-workflows/limitations.rst:37 +msgid "up- or downgrade permissions of users" msgstr "" -#: ../system/integrations/ldap/manage.rst:81 -msgid "Review or edit existing source" +#: ../system/core-workflows/limitations.rst:38 +msgid "affecting article creation or listing" msgstr "" -#: ../system/integrations/ldap/manage.rst:68 +#: ../system/data-privacy.rst:2 +msgid "Data Privacy" +msgstr "" + +#: ../system/data-privacy.rst:4 msgid "" -"Clicking on a LDAP source will provide a configuration and mapping overview." +"For compliance with GDPR and other data privacy laws, you may wish to " +"**permanently delete users from the system**, along with **all of their " +"associated tickets**." msgstr "" -#: ../system/integrations/ldap/manage.rst:70 +#: ../system/data-privacy.rst:8 msgid "" -"If needed you can then use the *Change* button to update either the name, " -"active state or the whole configuration. If you're changing the whole " -"configuration, the dialogue will be identical to the source creation." +"You can create manual deletion tasks or even automated deletion tasks for " +"tickets and users based on custom conditions via :doc:`scheduler `!" msgstr "" -#: ../system/integrations/ldap/manage.rst:76 +#: ../system/data-privacy.rst:12 msgid "" -"Did your LDAP server change? Different LDAP servers have different " -"structures and default attributes. This causes the LDAP synchronization to " -"likely fail. Consider removing the affected source and re-add it." +"Access to this panel requires ``admin.data_privacy`` permissions (introduced " +"in Zammad 3.5)." msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing the update of the source name." +#: ../system/data-privacy.rst:15 +msgid "" +"On older systems that have not been updated yet, customers can also be :docs:" +"`deleted via the Zammad console `." msgstr "" -#: ../system/integrations/ldap/manage.rst:89 -msgid "Re-arrange LDAP source's order" +#: ../system/data-privacy.rst:22 +msgid "User deletion dialog in the Data Privacy panel" msgstr "" -#: ../system/integrations/ldap/manage.rst:84 +#: ../system/data-privacy.rst:22 msgid "" -"You can change the synchronization order for each source at any time. Zammad " -"will synchronize the sources from top to bottom." +"The user deletion dialog lists some of the tickets that will be removed from " +"the system along with the user." msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "" -"Screencasting showing how to change the source order by using\n" -"drag and drop." +#: ../system/data-privacy.rst:27 +msgid "Deleting Users via GUI" msgstr "" -#: ../system/integrations/ldap/manage.rst:101 -msgid "Remove a source" +#: ../system/data-privacy.rst:29 +msgid "🔥 **All deletions are FINAL!**" msgstr "" -#: ../system/integrations/ldap/manage.rst:92 -msgid "" -"If you no longer need the a LDAP source or simply want to start over, you " -"can remove them at any time. This will not remove synchronized users, data " -"synchronized or permissions." +#: ../system/data-privacy.rst:31 +msgid "Once you click “Delete”, the action cannot be canceled or undone." msgstr "" -#: ../system/integrations/ldap/manage.rst:98 +#: ../system/data-privacy.rst:33 msgid "" -"Not sure if you'd need the source later on? Set the source to inactive " -"instead of removing it - see *Review or edit existing source* for more." +"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." msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing how to remove LDAP sources." +#: ../system/data-privacy.rst:36 +msgid "**The following records cannot be deleted:**" msgstr "" -#: ../system/integrations/pgp/index.rst:2 -msgid "PGP" +#: ../system/data-privacy.rst:38 +msgid "your own account" msgstr "" -#: ../system/integrations/pgp/index.rst:7 -msgid "" -"Pretty Good Privacy (PGP) is another method for secure email communication. " -"With PGP, you can exchange **signed** and **encrypted** messages with others." +#: ../system/data-privacy.rst:39 +msgid "the system's last remaining administrator account" msgstr "" -#: ../system/integrations/pgp/index.rst:13 -#: ../system/integrations/smime/index.rst:17 -msgid "Signing" +#: ../system/data-privacy.rst:42 +msgid "Step 1: Find a User / Confirm Deletion" msgstr "" -#: ../system/integrations/pgp/index.rst:11 -msgid "is a proof that a message hasn't been manipulated on its way." +#: ../system/data-privacy.rst:44 +msgid "There are three ways to access the user deletion dialog:" msgstr "" -#: ../system/integrations/pgp/index.rst:13 -msgid "" -"In other words, it guarantees message **integrity** and **authenticity**." +#: ../system/data-privacy.rst:51 +msgid "**from the user's profile**" msgstr "" -#: ../system/integrations/pgp/index.rst:19 -#: ../system/integrations/smime/index.rst:22 -msgid "Encryption" +#: ../system/data-privacy.rst:0 +msgid "Accessing the user deletion dialog in a user profile" msgstr "" -#: ../system/integrations/pgp/index.rst:16 -#: ../system/integrations/smime/index.rst:20 -msgid "" -"scrambles a message so that it can only be unscrambled by the intended " -"recipient." +#: ../system/data-privacy.rst:51 +msgid "Click **Action > Delete**." msgstr "" -#: ../system/integrations/pgp/index.rst:19 -msgid "" -"In other words, it guarantees message **privacy** and **data security**." +#: ../system/data-privacy.rst:58 +msgid "**in the “Manage > Users” Admin Panel**" msgstr "" -#: ../system/integrations/pgp/index.rst:25 -msgid "Screenshot of ticket creation with encrypt and sign buttons" +#: ../system/data-privacy.rst:0 +msgid "Accessing the user deletion dialog under “Users” in the Admin Panel" msgstr "" -#: ../system/integrations/pgp/index.rst:25 -msgid "" -"Once PGP has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " -"appear in the ticket composer." +#: ../system/data-privacy.rst:58 +msgid "Use the **⋮ Actions** menu for the target user." msgstr "" -#: ../system/integrations/pgp/index.rst:28 -msgid "**Sign button not visible?**" +#: ../system/data-privacy.rst:66 ../system/data-privacy.rst:104 +msgid "**in the “System > Data Privacy” Admin Panel**" msgstr "" -#: ../system/integrations/pgp/index.rst:30 +#: ../system/data-privacy.rst:0 msgid "" -"Please note that the signing of emails is based on the outgoing email " -"account. That means you have to choose a group with a sender email account, " -"which has a private key assigned." +"Accessing the user deletion dialog under “Data Privacy” in the Admin Panel" msgstr "" -#: ../system/integrations/pgp/index.rst:35 -msgid "Handling of Keys" +#: ../system/data-privacy.rst:65 +msgid "" +"Use the **New Deletion Task** button. Search for users by name or email " +"address." msgstr "" -#: ../system/integrations/pgp/index.rst:36 -msgid "" -"To use the PGP function, you have to enable the integration (PGP) by " -"switching the toggle to *enabled*." +#: ../system/data-privacy.rst:79 +msgid "**Delete organizations**" msgstr "" -#: ../system/integrations/pgp/index.rst:39 +#: ../system/data-privacy.rst:69 msgid "" -"You can add keys by clicking the *add key* button. The keys can be imported " -"from a file or you can paste the content of the key in the text box." +"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:" msgstr "" -#: ../system/integrations/pgp/index.rst:42 -msgid "**Which keys do I have to import?**" +#: ../system/data-privacy.rst:0 +msgid "Deleting an organization via the user deletion dialog" msgstr "" -#: ../system/integrations/pgp/index.rst:44 +#: ../system/data-privacy.rst:78 msgid "" -"For **signing** *outgoing* emails, you have to import the private key of " -"your Zammad email account." +"If this option does not appear, make sure there are no pending deletion " +"tasks for other customers from this organization." msgstr "" -#: ../system/integrations/pgp/index.rst:47 -msgid "" -"For **encrypting** *outgoing* emails, you have to import the public key of " -"the customer's email account." +#: ../system/data-privacy.rst:82 +msgid "Step 2: Monitor Deletion Job Status" msgstr "" -#: ../system/integrations/pgp/index.rst:50 +#: ../system/data-privacy.rst:84 msgid "" -"For **verifying the signature** of signed *incoming* emails, you have to " -"import the public key of the customer." +"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:" msgstr "" -#: ../system/integrations/pgp/index.rst:53 -msgid "" -"For **decrypting** of encrypted *incoming* emails, you have to import the " -"private key of your Zammad email account." +#: ../system/data-privacy.rst:98 +msgid "**in the Activity Stream**" msgstr "" -#: ../system/integrations/pgp/index.rst:57 -msgid "Import Keys From a File" +#: ../system/data-privacy.rst:0 +msgid "Activity Stream showing data privacy tasks" msgstr "" -#: ../system/integrations/pgp/index.rst:58 -msgid "You can import keys from a file in the section **Upload key**:" +#: ../system/data-privacy.rst:94 +msgid "" +"For each deleted user, the Activity Stream will be updated twice—once when " +"the task is created, and once when it's complete." msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of adding a key via file" +#: ../system/data-privacy.rst:97 +msgid "" +"These notifications are only visible to users with ``admin.data_privacy`` " +"permissions." msgstr "" -#: ../system/integrations/pgp/index.rst:64 +#: ../system/data-privacy.rst:0 msgid "" -"**Supported file formats:** ASCII-armor as well as binary GPG format " -"(basically any GPG supported key format) is supported here." +"The task list within Data Privacy shows removals being in progress and " +"completed." msgstr "" -#: ../system/integrations/pgp/index.rst:68 -msgid "Import Keys by Pasting the Content" +#: ../system/data-privacy.rst:107 +msgid "Frequently Asked Questions" msgstr "" -#: ../system/integrations/pgp/index.rst:69 -msgid "You can also paste the key's content in the section **paste key**:" +#: ../system/data-privacy.rst:121 +msgid "What happens if I receive an email from a deleted customer?" msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of adding a key via pasting" +#: ../system/data-privacy.rst:110 +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/integrations/pgp/index.rst:75 +#: ../system/data-privacy.rst:115 msgid "" -"**Supported format:** Please note that only ASCII-armor is supported here." +"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**." msgstr "" -#: ../system/integrations/pgp/index.rst:78 -msgid "Deleting Keys" +#: ../system/data-privacy.rst:130 +msgid "What about user information stored in internal notes or other messages?" msgstr "" -#: ../system/integrations/pgp/index.rst:79 +#: ../system/data-privacy.rst:124 msgid "" -"If you want to delete a specific key, you can do it by clicking on the menu " -"in the *actions* column and select **delete**:" +"The deletion process removes **user accounts and associated tickets only**." msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of deleting a key" +#: ../system/data-privacy.rst:126 +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." msgstr "" -#: ../system/integrations/pgp/index.rst:88 -msgid "Downloading Keys" +#: ../system/data-privacy.rst:137 +msgid "I deleted an user and can still see a message they sent!" msgstr "" -#: ../system/integrations/pgp/index.rst:89 +#: ../system/data-privacy.rst:133 msgid "" -"If you want to download your keys, you can do this as well via corresponding " -"action buttons. Depending on the key, you can choose wether you want to " -"download the private or the public key." +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:95 -#: ../system/integrations/smime/manage-certificates.rst:76 -msgid "Default Behavior" +#: ../system/data-privacy.rst:141 +msgid "I removed a customer, now my reporting is off!" msgstr "" -#: ../system/integrations/pgp/index.rst:96 +#: ../system/data-privacy.rst:140 msgid "" -"Here you can adjust on per group basis, if *sign* and *encryption* is on or " -"off by default. Please be aware, that agents can always override the setting " -"for each individual article." +"When removing users and their tickets, all references are removed. This also " +"affects e.g. Reporting - these information are lost." msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Adjusting default behavior on per group basis" +#: ../system/data-privacy.rst:145 +msgid "How long does Zammad store created tasks?" msgstr "" -#: ../system/integrations/pgp/index.rst:107 +#: ../system/data-privacy.rst:144 msgid "" -"Here you can see the last actions regarding signing and encryption and if " -"they were successful." -msgstr "" - -#: ../system/integrations/pgp/index.rst:117 -msgid "**Sign button is not visible, but keys are imported.**" +"Please see the on-premise data section of the :docs:`data privacy ` chapter." msgstr "" -#: ../system/integrations/pgp/index.rst:115 -msgid "Did you choose a group in the ticket?" +#: ../system/data-privacy.rst:150 +msgid "What about re-assigned tickets? I want to delete them, too." msgstr "" -#: ../system/integrations/pgp/index.rst:116 +#: ../system/data-privacy.rst:148 msgid "" -"Did you import a private key for the email adress, which is used for " -"outgoing emails in the group?" +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:122 -msgid "**How to obtain keys?**" +#: ../system/data-privacy.rst:154 +msgid "Why are there so many deletion task entries, I didn't create them!" msgstr "" -#: ../system/integrations/pgp/index.rst:120 +#: ../system/data-privacy.rst:153 msgid "" -"You can create them yourself! There are some good tutorials on the web on " -"how to create them. Providing keys to Zammad is a prerequisite to use the " -"PGP feature." -msgstr "" - -#: ../system/integrations/pgp/index.rst:127 -msgid "**It says a passphrase is needed, but I haven't got one.**" +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:125 -msgid "" -"If the key is secured with a passphrase, you have to provide it for the " -"import in Zammad. It is possible that keys may have an empty passphrase. " -"However, this is *not* recommended." +#: ../system/integrations/checkmk/admin-panel-reference.rst:2 +msgid "Admin Panel Reference" msgstr "" -#: ../system/integrations/pgp/index.rst:132 -msgid "**How do my customers get my new key?**" +#: ../system/integrations/checkmk/admin-panel-reference.rst:None +msgid "Screenshot of Checkmk settings overview" msgstr "" -#: ../system/integrations/pgp/index.rst:130 +#: ../system/integrations/checkmk/admin-panel-reference.rst:12 msgid "" -"You have to provide your **public** key in advance. Your customer also has " -"to configure PGP in their email workflow and import your public key. The " -"other way round, you have to get the public key of your customer and have to " -"import it to Zammad." +"Which :doc:`group ` should Checkmk tickets be assigned " +"to as a default (*i.e.,* when none is specified)?" msgstr "" -#: ../system/integrations/slack.rst:2 -msgid "Slack" +#: ../system/integrations/checkmk/admin-panel-reference.rst:15 +msgid "(Applies to :ref:`API alerts ` only.)" msgstr "" -#: ../system/integrations/slack.rst:4 -msgid "**⚠️ Deprecation warning ⚠️**" +#: ../system/integrations/checkmk/admin-panel-reference.rst:21 +msgid "Auto close" msgstr "" -#: ../system/integrations/slack.rst:6 +#: ../system/integrations/checkmk/admin-panel-reference.rst:18 msgid "" -"Zammad 7 will no longer support this dedicated Slack integration. It is " -"recommended to switch to :doc:`pre-defined webhooks ` instead. Existing Slack integrations should " -"be migrated manually before this feature is dropped." +"Should Zammad automatically close tickets if a service has recovered on its " +"own?" msgstr "" -#: ../system/integrations/slack.rst:14 -msgid "" -"In order to use this feature, please add a new Slack app to your Workspace. " -"The App you need is called ``Incoming WebHooks`` ." +#: ../system/integrations/checkmk/admin-panel-reference.rst:21 +msgid "(Agents will receive notifications for such closures as appropriate.)" msgstr "" -#: ../system/integrations/slack.rst:18 -msgid "Why Do I Need This Feature?" +#: ../system/integrations/checkmk/admin-panel-reference.rst:30 +msgid "Auto-close state" msgstr "" -#: ../system/integrations/slack.rst:20 -msgid "" -"If you're already using Slack for your team communication, you'll love this " -"feature! Our Slack integration can push ticket notifications about the last " -"ticket article based on the following events:" +#: ../system/integrations/checkmk/admin-panel-reference.rst:24 +msgid "What ticket state should be applied when “auto-closing” a ticket?" msgstr "" -#: ../system/integrations/slack.rst:24 -msgid "on Ticket creation" +#: ../system/integrations/checkmk/admin-panel-reference.rst:26 +msgid "" +"You can choose from the seven built-in ticket states. If these states aren't " +"enough for you, you can :ref:`define a new ticket state ` for this purpose as well. This can be useful for tracking " +"tickets with :doc:`reports `, for example." msgstr "" -#: ../system/integrations/slack.rst:25 -msgid "on Ticket updates" +#: ../system/integrations/checkmk/admin-panel-reference.rst:35 +#: ../system/integrations/cti/includes/recent-logs.include.rst:2 +#: ../system/integrations/ldap/index.rst:74 +#: ../system/integrations/pgp/index.rst:106 +msgid "Recent Logs" msgstr "" -#: ../system/integrations/slack.rst:26 -msgid "on reached reminders" +#: ../system/integrations/checkmk/admin-panel-reference.rst:None +msgid "Screenshot of Checkmk \"Recent Logs\" section" msgstr "" -#: ../system/integrations/slack.rst:27 -msgid "a Ticket has escalated" +#: ../system/integrations/checkmk/admin-panel-reference.rst:41 +msgid "" +"If you're having trouble getting Zammad and Checkmk to play nicely together, " +"this section can help you troubleshoot." msgstr "" -#: ../system/integrations/slack.rst:28 -msgid "a Ticket is going to escalate" +#: ../system/integrations/checkmk/admin-panel-reference.rst:44 +msgid "" +"It contains a record of the fifty most recent transactions that Zammad knows " +"about, including each one's request/response details and return status." msgstr "" -#: ../system/integrations/slack.rst:30 -msgid "" -"Zammad will provide the Ticket title, a direct link to the Ticket, the event " -"type (creation, updated, escalation), the customer, time and the last " -"article that has triggered the notification." +#: ../system/integrations/checkmk/api-reference.rst:2 +msgid "API Reference" msgstr "" -#: ../system/integrations/slack.rst:34 +#: ../system/integrations/checkmk/api-reference.rst:4 msgid "" -"This will give you further options, as you can see e.g. escalating tickets " -"that are assigned to an agent that's e.g. absent. You can interact faster, " -"as you might see problems earlier (or even before the problem gets one)." +"For most users, :ref:`the sample scripts from the Setup Guide ` will do the job just fine. But if you want more fine-grained control" +"—for instance, to create high- and low-priority tickets for different types " +"of system events—then you'll have to customize the data those scripts send " +"to Zammad." msgstr "" -#: ../system/integrations/slack.rst:38 +#: ../system/integrations/checkmk/api-reference.rst:15 msgid "" -"If needed and wanted, you can even discuss directly about the topic before " -"sending an answer to the customer. Another possible use case would be a " -"agent monitoring new agents and their answers to tickets." +"This custom script will automatically set all tickets it creates to **high " +"priority** and **assign them to charlie@chrispresso.com**." msgstr "" -#: ../system/integrations/slack.rst:44 -msgid "Configure the Integration" +#: ../system/integrations/checkmk/api-reference.rst:32 +msgid "How Does it Work?" msgstr "" -#: ../system/integrations/slack.rst:46 +#: ../system/integrations/checkmk/api-reference.rst:34 msgid "" -"First of all, please go to your slack workspace - go to administration => " -"Manage Apps. If you don't have an app yet, you can simply add a new one - " -"just search for ``Incoming WebHooks`` and customize the app to your needs." +"There are two kinds of data you can pass to the API, both in the form of key-" +"value pairs:" msgstr "" -#: ../system/integrations/slack.rst:50 -msgid "" -"Choose (or create) the channel Zammad should post it's information to and " -"press on \"Add Incoming WebHooks integration\". If you're ready, copy the " -"provided WebHook URL and go to your Zammad installation." +#: ../system/integrations/checkmk/api-reference.rst:44 +msgid "Checkmk parameters" msgstr "" -#: ../system/integrations/slack.rst:56 +#: ../system/integrations/checkmk/api-reference.rst:38 msgid "" -"You need administrative rights on the Slack Workspace. The link to the app " -"directory is normally ``https://[workspace-name].slack.com/apps`` ." +"are required, and make up the **contents** of the resulting tickets/" +"articles. They also determine whether an event creates a new ticket or " +"updates/closes an existing one." msgstr "" -#: ../system/integrations/slack.rst:63 +#: ../system/integrations/checkmk/api-reference.rst:42 msgid "" -"To configure the slack integration, log in to Zammad and go to Integrations " -"(System) => Slack in the admin panel." +"These are the only values used in the sample scripts. **Use them as-is**; " +"technically, they can be customized, but it's hard to imagine a good reason " +"for it." msgstr "" -#: ../system/integrations/slack.rst:66 -msgid "" -"Here you can choose on what evens Zammad should post information about a " -"ticket to your Slack channel. Next you need to device what groups shall be " -"affected by this, as anybody with access to that specific Slack channel can " -"read at least parts of the ticket this might be a privacy issue, if you " -"select the wrong groups. The username is simply the name that Zammad uses as " -"display name inside the Slack chat. The channel defines the Slack channel " -"the information is being posted in. As last option, you can set a custom " -"icon for posting to slack." +#: ../system/integrations/checkmk/api-reference.rst:52 +msgid "Ticket attributes" msgstr "" -#: ../system/integrations/slack.rst:74 +#: ../system/integrations/checkmk/api-reference.rst:47 msgid "" -"When you're ready, just hit \"Submit\" and enable the integration. Zammad " -"will now post new ticket information based on the trigger you chose. Below " -"the options you have the recent log that shows the latest requests to Slack " -"for debugging if needed." +"are optional, and can be used to **adjust settings** on newly created " +"tickets (*e.g.,* set the owner, group, priority, or state)." msgstr "" -#: ../system/integrations/slack.rst:81 +#: ../system/integrations/checkmk/api-reference.rst:50 msgid "" -"If you leave the Icon URL empty, Zammad will use the Zammad logo instead. " -"The icon should be a square PNG file." +"If you want to customize your Checkmk alert script, do it with these. Simply " +"add an extra “form” option for each one (``-F \"key=value\"``) to your " +"script's ``curl`` command line, as in the example above." msgstr "" -#: ../system/integrations/slack.rst:90 -msgid "" -"The following figure shows how it will look if you choose to receive updates " -"on created and updated tickets. On every post Zammad sends to the Slack " -"channel, you can create new threads to discuss about the new article." +#: ../system/integrations/checkmk/api-reference.rst:54 +msgid "💡 **It's just an API endpoint!**" msgstr "" -#: ../system/integrations/slack.rst:96 +#: ../system/integrations/checkmk/api-reference.rst:56 msgid "" -"If you just want to keep track of soon escalating or already escalated " -"tickets, it will look the the following figure. Zammad changes the color in " -"front of the post so you can easily see the state of the ticket." +"When using Checkmk integration, messages need to be formatted in a certain " +"way, but that *doesn't mean the messages actually have to come from Checkmk*." msgstr "" -#: ../system/integrations/slack.rst:102 +#: ../system/integrations/checkmk/api-reference.rst:59 msgid "" -"If you change the state, Zammad will also put information on what state the " -"ticket gets and (if pending state) the date until it pends. You'll also " -"recognize the color codes in front of posts on slack, as they are exact the " -"same the ticket state colors you'll see in Zammad!" +"If you use another monitoring tool that's not officially supported by " +"Zammad, there's probably a way to make it work with your Checkmk callback " +"URL." msgstr "" -#: ../system/integrations/smime/index.rst:2 -msgid "S/MIME" +#: ../system/integrations/checkmk/api-reference.rst:63 +msgid "Checkmk Parameters" msgstr "" -#: ../system/integrations/smime/index.rst:11 +#: ../system/integrations/checkmk/api-reference.rst:65 msgid "" -"S/MIME is the most widely-supported method for secure email communication. " -"With S/MIME, you can exchange **signed** and **encrypted** messages with " -"others." +"When a notification is received, Zammad creates a new article containing the " +"details of the event that triggered it:" msgstr "" -#: ../system/integrations/smime/index.rst:15 -msgid "" -"is proof that a message hasn't been tampered with or sent by an impersonator." +#: ../system/integrations/checkmk/api-reference.rst:None +msgid "Checkmk article body" msgstr "" -#: ../system/integrations/smime/index.rst:17 +#: ../system/integrations/checkmk/api-reference.rst:72 msgid "" -"In other words, it guarantees a message's **integrity** and **authenticity**." +"These details come from the fields listed below, which correspond to " +"parameters provided by Checkmk (``$NOTIFY_*``)." msgstr "" -#: ../system/integrations/smime/index.rst:22 -msgid "In other words, it guarantees **privacy** and **data security**." +#: ../system/integrations/checkmk/api-reference.rst:75 +msgid "**Required fields are marked with an asterisk (\\*).**" msgstr "" -#: ../system/integrations/smime/index.rst:28 -msgid "Screencast demo of S/MIME features for both new tickets and replies" +#: ../system/integrations/checkmk/api-reference.rst:79 +msgid "event_id\\*" msgstr "" -#: ../system/integrations/smime/index.rst:28 +#: ../system/integrations/checkmk/api-reference.rst:78 msgid "" -"Once S/MIME has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " -"appear in the ticket composer." +"A unique ID for the system event. (``$NOTIFY_SERVICEPROBLEMID`` / " +"``$NOTIFY_HOSTPROBLEMID``)" msgstr "" -#: ../system/integrations/smime/index.rst:32 -msgid ":doc:`🔪 Prerequisites `" +#: ../system/integrations/checkmk/api-reference.rst:86 +msgid "host\\*" msgstr "" -#: ../system/integrations/smime/index.rst:31 +#: ../system/integrations/checkmk/api-reference.rst:82 msgid "" -"New to S/MIME? This section helps you to find certificate providers and " -"points out Limitations." +"The hostname of the system that the event originated from. " +"(``$NOTIFY_HOSTNAME``)" msgstr "" -#: ../system/integrations/smime/index.rst:35 -msgid ":doc:`📝 Manage Certificates `" +#: ../system/integrations/checkmk/api-reference.rst:85 +msgid "" +"Used to determine if a new event belongs to an existing ticket. Also used in " +"the subject line of the resulting article (“ is ”)." msgstr "" -#: ../system/integrations/smime/index.rst:35 -msgid "Add and download certificates; configure group default behaviors." +#: ../system/integrations/checkmk/api-reference.rst:96 +msgid "service" msgstr "" -#: ../system/integrations/smime/index.rst:38 -msgid ":doc:`😦 Troubleshooting `" +#: ../system/integrations/checkmk/api-reference.rst:89 +msgid "" +"The name of the service that the event originated from. " +"(``$NOTIFY_SERVICEDESC``)" msgstr "" -#: ../system/integrations/smime/index.rst:38 -msgid "Took a wrong turn? About recent logs and common issues." +#: ../system/integrations/checkmk/api-reference.rst:92 +msgid "Used to determine if a new event belongs to an existing ticket." msgstr "" -#: ../system/integrations/smime/index.rst:43 -msgid "" -"For more details on how S/MIME integration works on the agent side, see the :" -"user-docs:`user docs `." +#: ../system/integrations/checkmk/api-reference.rst:94 +#: ../system/integrations/checkmk/api-reference.rst:110 +msgid "Displayed as ``-`` when omitted." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:2 -msgid "Manage Certificates" +#: ../system/integrations/checkmk/api-reference.rst:104 +msgid "state\\*" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:4 +#: ../system/integrations/checkmk/api-reference.rst:99 msgid "" -"S/MIME is **disabled by default**. Enable it to start adding certificates." +"The current state of the service or host in question. " +"(``$NOTIFY_SERVICESTATE`` / ``$NOTIFY_HOSTSTATE``)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:10 -msgid "Dialogue to add new certificates or private keys" +#: ../system/integrations/checkmk/api-reference.rst:102 +msgid "" +"Used to detect when a ticket should be auto-closed (*i.e.,* on ``OK``/" +"``UP``). Also used in the subject line of the resulting article (“ is " +"”)." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:10 +#: ../system/integrations/checkmk/api-reference.rst:110 +msgid "text" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:107 msgid "" -"Manage certificates in the Admin Panel under **System > Integrations > S/" -"MIME**. Certificates may be pasted in as plain text or uploaded from a file." +"The output of the process that triggered the event. " +"(``$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:14 -msgid "Add Certificate Data" +#: ../system/integrations/checkmk/api-reference.rst:121 +msgid "" +"The Object Manager attribute panel displays built-in and custom\n" +"attribute names." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:36 -msgid "Add Certificate" +#: ../system/integrations/checkmk/api-reference.rst:121 +msgid "Find a complete list of ticket attributes in the Object Manager." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:17 +#: ../system/integrations/checkmk/api-reference.rst:123 msgid "" -"Import public-key certificates for both your own organization and your " -"contacts." +"Ticket attributes are entirely optional, and can be used to customize the " +"tickets that Checkmk creates. (Note that these attributes will be ignored if " +"a new event belongs to an existing ticket.)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:19 +#: ../system/integrations/checkmk/api-reference.rst:128 msgid "" -"You can also add a bunch of certificates in one go by providing a single " -"file with all relevant certificates." +"Why would you want to do this? Maybe you have only one IT guy, and all " +"system monitoring issues should be automatically assigned to him. Or, maybe " +"you're creating multiple notification rules so that database outages take " +"higher priority than disk space warnings." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:22 -msgid "🕵️ **ALWAYS verify certificates in-person or over the phone!**" +#: ../system/integrations/checkmk/api-reference.rst:135 +msgid "In most cases, you'll probably want to set one of the following:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:24 -msgid "" -"The whole point of signatures is to alert you when someone is trying to " -"pretend to be someone they're not. Never accept a certificate from someone " -"online without verifying it first." +#: ../system/integrations/checkmk/api-reference.rst:137 +msgid "group" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:28 -msgid "📇 **What about trusted certificate authorities?**" +#: ../system/integrations/checkmk/api-reference.rst:139 +msgid "state" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:30 -msgid "" -"In some cases (e.g. when dealing with large enterprises), you may be given a " -"certificate for an entire CA, rather than a single contact. Add it here to " -"trust *all* certificates issued by that CA." +#: ../system/integrations/checkmk/api-reference.rst:140 +msgid "priority" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:35 +#: ../system/integrations/checkmk/api-reference.rst:142 msgid "" -"Commercial CAs can usually be verified online. Zammad does not include a " -"list of built-in, trusted CAs." +"but in practice, you can set almost any attribute, including :doc:`custom " +"ones you created through the Object Manager `." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:57 -msgid "Add Private Key" +#: ../system/integrations/checkmk/api-reference.rst:145 +msgid "Please note that the following attributes are **not customizable**:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:39 -msgid "" -"Once you've added a public-key certificate, you can import its matching " -"private key." +#: ../system/integrations/checkmk/api-reference.rst:147 +msgid "title" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:42 -msgid "" -"Private keys are for **your own organization only**; never ask your contacts " -"for their private keys." +#: ../system/integrations/checkmk/api-reference.rst:148 +msgid "id" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:0 -msgid "" -"S/MIME integration showing configured certificates and possible issues with " -"Logging" +#: ../system/integrations/checkmk/api-reference.rst:149 +msgid "ticket number" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:50 -msgid "" -"A note is displayed on certificates with a matching private key (see line 2)." +#: ../system/integrations/checkmk/api-reference.rst:151 +msgid "created_by_id" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:52 -msgid "📤 **Certificates and private keys must be uploaded separately.**" +#: ../system/integrations/checkmk/api-reference.rst:152 +msgid "updated_by_id" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:54 -msgid "" -"If your certificate and private key are bundled together in the same file or " -"PEM block, import it twice (once using each button)." -msgstr "" - -#: ../system/integrations/smime/manage-certificates.rst:57 -msgid "Please note that bulk imports of private keys are not possible." +#: ../system/integrations/checkmk/api-reference.rst:155 +msgid "Which Values Can Be Set?" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:60 -msgid "Download Certificate Data" +#: ../system/integrations/checkmk/api-reference.rst:157 +msgid "😵 **Invalid values → unpredictable behavior**" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:62 +#: ../system/integrations/checkmk/api-reference.rst:159 msgid "" -"You can download the earlier provided certificates and private keys at any " -"time from your Zammad instance." +"If you provide a value that Zammad doesn't understand (*e.g.,* ``-F " +"\"priority=high\"``), it's not always clear what will happen. In some cases, " +"a ticket will be created with the default values instead - but in others, it " +"may not be created at all!" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:65 -msgid "" -"Please note that passphrase-protected private keys stay protected and when " -"you download them, you have to know the passphrase to use them after " -"downloading." +#: ../system/integrations/checkmk/api-reference.rst:164 +msgid "So what values does Zammad understand, then? Well, it depends..." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:73 -msgid "Dialogue to download certificates or private keys" +#: ../system/integrations/checkmk/api-reference.rst:168 +msgid "Use an email address or username:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:73 -msgid "Download stored certificates and their keys" +#: ../system/integrations/checkmk/api-reference.rst:190 +msgid "group & priority" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:78 -msgid "" -"The ticket composer will set all outgoing messages to **signed and " -"encrypted** by default (assuming the required certificates exist)." +#: ../system/integrations/checkmk/api-reference.rst:175 +msgid "Refer to the dropdown menus in the ticket pane:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:82 -msgid "These defaults can be modified on a per-group basis:" +#: ../system/integrations/checkmk/api-reference.rst:0 +msgid "See possible values for certain attributes in the ticket pane." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:None -msgid "Zammad allowing to choose the default behavior on per group basis" +#: ../system/integrations/checkmk/api-reference.rst:187 +msgid "🙅 **Ticket state CANNOT be set this way!**" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:89 +#: ../system/integrations/checkmk/api-reference.rst:189 msgid "" -"Of course, agents can always manually change these settings on each email " -"they send out." +"Why? Because ``-F \"state=...\"`` is already used :ref:`as a Checkmk " +"parameter `." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:4 -msgid "A certificate *and* private key for your own organization" +#: ../system/integrations/checkmk/api-reference.rst:222 +msgid "Everything Else" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:6 +#: ../system/integrations/checkmk/api-reference.rst:193 msgid "" -"(Use this to ✒️ **sign outgoing messages** and 🔓 **decrypt incoming " -"messages**.)" +"To set any other attributes, it helps to know your way around the :docs:" +"`rails console `. Valid values are those that you can " +"set with a string:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:9 -msgid "" -"Certificates belonging your contacts, or their issuing certificate authority " -"(CA)" +#: ../system/integrations/checkmk/api-reference.rst:218 +msgid "These values can then be passed directly to the API:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:11 -msgid "" -"(Use these to ✅ **verify incoming message signatures** and 🔒 **encrypt " -"outgoing messages**.)" +#: ../system/integrations/checkmk/index.rst:16 +msgid "How does it work?" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:14 -msgid "🙋 **I'm new to S/MIME. Where can I get a certificate?**" +#: ../system/integrations/checkmk/index.rst:2 +msgid "Checkmk" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:16 +#: ../system/integrations/checkmk/index.rst:4 msgid "" -"The easiest way to get certificates is to buy an annual subscription through " -"a commercial CA, such as:" +"`Checkmk `_ is a powerful IT monitoring tool that can " +"send real-time status alerts to Zammad via email or REST API. Set these " +"alerts up in Checkmk, and Zammad will automatically create, update, and " +"close tickets based on the health of your system:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:19 -msgid "" -"`Sectigo (formerly Comodo) `_" +#: ../system/integrations/checkmk/index.rst:14 +msgid "Screenshot of ticket created by Checkmk notifications" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:20 -msgid "`Secorio `_" +#: ../system/integrations/checkmk/index.rst:14 +msgid "Multiple alerts, same ticket." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:21 -msgid "`GlobalSign `_" +#: ../system/integrations/checkmk/setup-guide.rst:2 +msgid "Setup Guide" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:23 -msgid "(Zammad is not affiliated with these CAs in any way.)" +#: ../system/integrations/checkmk/setup-guide.rst:4 +msgid "" +"Whenever the Checkmk integration is enabled, Zammad listens for messages on " +"its API and over email. As long as those messages follow the required " +"format, Zammad will create new tickets (or find and update existing ones) " +"based on the message contents." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:25 +#: ../system/integrations/checkmk/setup-guide.rst:10 msgid "" -"You can also generate your own self-signed certificates, but the process is " -"complicated and usually 🙅 **involves extra work for your contacts**." +"That means that “setting up Checkmk integration” is simply a matter of " +"**adding configuration to your Checkmk site**: telling it when to send these " +"messages and what to say. To do that, you'll need to create a new " +"**notification rule** (see `Checkmk's official docs `_ for help with that)." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:29 +#: ../system/integrations/checkmk/setup-guide.rst:17 msgid "" -"Bear in mind that 🤝 **S/MIME only works if the other party is using it, too." -"**" +"As part of this new rule, you'll have to choose a **notification method** " +"(*i.e.,* a script to execute whenever the rule is triggered). This script " +"will be written by you (samples below), and contain the logic for sending " +"API/email messages to Zammad:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:32 -msgid "Certificate and Private Key Checks on Upload" +#: ../system/integrations/checkmk/setup-guide.rst:26 +msgid "Checkmk \"New Rule\" dialog" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:34 +#: ../system/integrations/checkmk/setup-guide.rst:26 msgid "" -"The certificate and public key validation is based on the ``X509v3`` " -"extensions." +"Find your custom scripts in the Checkmk WATO under **Notifications > New " +"Rule > Notification Method**." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:49 -msgid "Uploading a *client certificate*?" +#: ../system/integrations/checkmk/setup-guide.rst:29 +msgid "" +"Once you're done setting up your new rule, you're all set! New tickets " +"should start coming in and auto-updating any time your rule is triggered." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:41 -msgid "The following attributes are required then:" +#: ../system/integrations/checkmk/setup-guide.rst:33 +msgid "" +"(If you need help troubleshooting, be sure to check the :ref:`checkmk-recent-" +"logs`.)" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:39 -msgid "Subject Alternative Name (at least one email address has to be present)" +#: ../system/integrations/checkmk/setup-guide.rst:38 +msgid "API Alerts" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:40 -msgid "Key Usage (``Digital Signature`` and/or ``Key Encipherment``)" +#: ../system/integrations/checkmk/setup-guide.rst:40 +msgid "" +"To add these scripts in the Checkmk WATO, copy them into your Checkmk " +"installation directory and make them executable. (Be sure to replace the " +"``zammad.example.com`` callback URL with the one found in your admin panel.)" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:41 -msgid "Public key algorithm (either ``RSA`` or ``EC``)" +#: ../system/integrations/checkmk/setup-guide.rst:60 +msgid "Service notification" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:43 +#: ../system/integrations/checkmk/setup-guide.rst:46 msgid "" -"The Extended Key Usage attribute is optional. If the certificate provides " -"the named attribute, than it must contain the value ``E-mail Protection``." +"For updates on the status of the software running on your server (*e.g.,* " +"postgres)." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:46 -msgid "" -"Please note that any usable email adress has to be prefixed with ``email:`` " -"or ``rfc822:``." +#: ../system/integrations/checkmk/setup-guide.rst:75 +msgid "Host notification" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:49 -msgid "The named public key algorithms are mandatory for private keys as well." +#: ../system/integrations/checkmk/setup-guide.rst:63 +msgid "For updates on the status of the server itself." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:54 -msgid "Uploading a *CA certificate*?" +#: ../system/integrations/checkmk/setup-guide.rst:77 +msgid "🤔 **What's with all the env vars?**" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:52 +#: ../system/integrations/checkmk/setup-guide.rst:79 msgid "" -"In the case of an uploaded CA certificate, providing the value ``CA:TRUE`` " -"in the attribute *Basic Contstraints*, the previously mentioned attributes " -"are not verified." +"Whenever Checkmk runs these scripts, it needs to provide some information " +"about the event that triggered the notification. This information is passed " +"in the form of these ``$NOTIFY_*`` environment variables." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:56 +#: ../system/integrations/checkmk/setup-guide.rst:85 msgid "" -"In general, the usage of any expired (``Not After``) or not yet valid (``Not " -"Before``) certificate is denied for outgoing emails." +"You can specify additional parameters to pass to the script when you're " +"setting up your notification rule, but the ones you see here are all " +"provided by default." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:59 -msgid "Example certificate:" +#: ../system/integrations/checkmk/setup-guide.rst:90 +msgid "Email Alerts" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:85 +#: ../system/integrations/checkmk/setup-guide.rst:94 msgid "" -"Please note that Zammad will distrust senders by default. This means that " -"you're always required to provide certificate data, no matter if for signing " -"or encrypting." +"🐞 **There are known bugs** in Zammad's processing of email from Checkmk. " +"This section will be completed once they have been resolved. (Learn more at " +"GitHub issues `#2377 `_ & " +"`#2180 `_.)" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:89 -msgid "This is by design and can't be adjusted." +#: ../system/integrations/checkmk/setup-guide.rst:100 +msgid "In the meantime, we encourage you to set up API alerts instead." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:4 -msgid "" -"All of the system's latest S/MIME activity is displayed in the **Recent " -"Logs** section." +#: ../system/integrations/clearbit.rst:2 +msgid "Clearbit" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:11 -msgid "Sample entries of in- and outgoing S/MIME related emails." +#: ../system/integrations/clearbit.rst:4 +msgid "" +"With our Clearbit integration, you can easily enrich the information " +"provided by Zammad. If the customers or agents email address is known to " +"Clearbit, it will share all information it has regarding the user with " +"Zammad. Those information can include the following:" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:11 -msgid "" -"Logs report the status and details of all mail, both incoming and outgoing, " -"that used signing/verification or encryption/decryption." +#: ../system/integrations/clearbit.rst:9 +msgid "Avatar" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:14 -msgid "" -"This log does **not** include email sent by :doc:`triggers ` or the :doc:`scheduler `. For those, check your " -"``production.log``." +#: ../system/integrations/clearbit.rst:10 +msgid "Address information" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:20 -msgid "Common Issues" +#: ../system/integrations/clearbit.rst:11 +msgid "Website information" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:30 -msgid "I received a signed/encrypted email before I set up S/MIME integration" +#: ../system/integrations/clearbit.rst:12 +msgid "A BIO (as Note by default)" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:23 +#: ../system/integrations/clearbit.rst:14 msgid "" -"No problem. Once S/MIME has been enabled and the appropriate certificates " -"have been added, agents will be prompted to retry verification/decryption on " -"matching emails." +"If needed, you can add further custom objects and add mappings to them, so " +"the Clearbit information can be filled within the database. In general you " +"can get any information from Clearbit, as long as you have a mapping to an " +"Zammad object." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:0 -msgid "Screenshot of user prompt to retry decryption" +#: ../system/integrations/clearbit.rst:21 +msgid "" +"Clearbit does have a mapping of fields like LDAP and Exchange have, but does " +"not \"win\" against Zammad information. This means that if you have e.g. the " +"last name field filled in already and Clearbit has other information on " +"that, it will not be updated." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:38 -msgid "The 🔒 **Encrypt** button is disabled" +#: ../system/integrations/clearbit.rst:26 +msgid "" +"However: If let's say the last name has been set by Clearbit and Zammad " +"notices that the last name on the Clearbit source has changed, Zammad will " +"also update this value." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:33 -msgid "Have you added the recipient's certificate?" +#: ../system/integrations/clearbit.rst:33 +msgid "" +"The configuration of Clearbit is really easy and done fast! Just login to " +"your Clearbit-Account, go to \"API\" and copy the secret-API-Key." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:34 -msgid "Are you sure the recipient's certificate is valid?" +#: ../system/integrations/clearbit.rst:38 +msgid "" +"Now change to your Zammad instance, go to Integrations (System) -> Clearbit " +"in the admin panel. Paste your API-Key into the API-Key-Field and decide if " +"Zammad should create unknown Organizations automatically, if the user does " +"not have one yet (and Clearbit knows it). The shared option decides if the " +"new organizations Zammad creates with Clearbit should be shared ones." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:35 -msgid "Have you checked your ``production.log`` for more details?" +#: ../system/integrations/clearbit.rst:47 +msgid "" +"If you're unsure what option to choose, better stick with \"no\". You can " +"also learn more about :doc:`/manage/organizations/index`." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:37 +#: ../system/integrations/clearbit.rst:52 msgid "" -"If encryption doesn't work in the composer, it won't work in :doc:`triggers " -"` or the :doc:`scheduler ` either!" +"The Mapping option works similar to the mapping within the Exchange and LDAP " +"sync. You can add further mappings for e.g. custom fields if you need more " +"information that Clearbit can provide." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:42 -msgid "The ✅ **Sign** button is disabled" +#: ../system/integrations/clearbit.rst:58 +msgid "" +"If you want to add more Clearbit fields and want to learn more about " +"available fields on their API, you can take a look at their `API " +"documentation `_." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:41 +#: ../system/integrations/clearbit.rst:62 msgid "" -"Have you added **both the certificate and private key** for your " -"organization?" +"If you're happy with the above chosen Settings and your mapping, just save " +"the changes and enable Clearbit integration. Zammad will now start polling " +"the Clearbit API as users contact you." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:42 +#: ../system/integrations/clearbit.rst:68 msgid "" -"Does the email address on the certificate match the email address of the " -"agent/group composing the email?" +"Zammad does not synchronize with Clearbit on a regular basis, but on demand " +"if needed. This saves API calls." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:45 -msgid "Error: “Fingerprint already taken”" +#: ../system/integrations/clearbit.rst:73 +msgid "" +"Below the Settings and Mappings, you'll find our Integration log. You can " +"see what requests Zammad sent to Clearbit and also the APIs Response." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:45 -msgid "Are you sure you haven't added this certificate already?" +#: ../system/integrations/clearbit.rst:78 +msgid "" +"By the way, you can also view the API log on the Clearbit website - the " +"information seen is basically the same." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:48 -msgid "Error: “❌ invalid byte sequence in UTF-8”" +#: ../system/integrations/clearbit.rst:84 +msgid "Example When Adding a User" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:48 -msgid "Please ensure to provide PEM formatted certificate and keys." +#: ../system/integrations/clearbit.rst:86 +msgid "" +"To show you how fast information is added, we added a small Screencast " +"below. This shows the creation of the User Alex from Clearbit. As we already " +"set the last name of Alex to \"X\", Zammad did not update it. What Zammad " +"did was to add further information it received from Clearbit." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:49 -msgid "Did you check if the provided file is a valid certificate or key?" +#: ../system/integrations/cti/generic.rst:2 +msgid "CTI (generic)" msgstr "" -#: ../system/integrations/zabbix.rst:2 -msgid "Zabbix Integration" +#: ../system/integrations/cti/includes/introduction.include.rst:1 +msgid "" +"This integration enables Zammad to provide a caller log to your agents. With " +"this your agents can greet your customers by their name and are supported by " +"Zammad with automatically opening a new ticket dialog or the user profile." msgstr "" -#: ../system/integrations/zabbix.rst:5 +#: ../system/integrations/cti/includes/introduction.include.rst:6 msgid "" -"This guide describes how to integrate your Zabbix 5.4 installation with " -"Zammad using the Zabbix webhook feature. This guide will provide " -"instructions on setting up a media type, a user and an action in Zabbix." +"Click the toggle next to the heading to activate or deactivate this " +"integration." msgstr "" -#: ../system/integrations/zabbix.rst:12 -msgid "Zammad with enabled HTTP Token Authentication" +#: ../system/integrations/cti/includes/introduction.include.rst:9 +msgid "" +"If you want to learn more on how your agents can use this function, please " +"refer the :user-docs:`user documentation `." msgstr "" -#: ../system/integrations/zabbix.rst:13 -msgid "Zabbix version 5.4 or higher" +#: ../system/integrations/cti/includes/introduction.include.rst:14 +msgid "" +"Automatically opening new ticket dialogues or user profiles requires agent " +"to extension mapping - see more below." msgstr "" -#: ../system/integrations/zabbix.rst:16 -msgid "Setting up a Zammad" +#: ../system/integrations/cti/includes/introduction.include.rst:20 +msgid "Please note the following limitations to reduce confusion later on:" msgstr "" -#: ../system/integrations/zabbix.rst:18 -msgid "Enable **API Token Access** in Settings > System > API." +#: ../system/integrations/cti/includes/introduction.include.rst:22 +msgid "CTI integrations provide caller log functions only." msgstr "" -#: ../system/integrations/zabbix.rst:20 +#: ../system/integrations/cti/includes/introduction.include.rst:23 msgid "" -"Create a **new user** for a Zabbix alerter with an **email address** and " -"create a personal user token with **ticket.agent** permissions." +"This integration does not provide any VoIP functionalities; you can't make " +"phone calls from within Zammad." msgstr "" -#: ../system/integrations/zabbix.rst:24 -msgid "Zabbix Webhook Configuration" +#: ../system/integrations/cti/includes/introduction.include.rst:25 +msgid "" +"If your browser supports ``tel``-URLs, you can click on phone numbers for " +"automatic dialing. This requires additional software / configuration on your " +"agent's computers." msgstr "" -#: ../system/integrations/zabbix.rst:27 -msgid "Create a Global Macro" +#: ../system/integrations/cti/generic.rst:9 +#: ../system/integrations/cti/placetel.rst:14 +#: ../system/integrations/cti/sipgate.rst:14 +msgid "Please provide the following requirements:" msgstr "" -#: ../system/integrations/zabbix.rst:29 +#: ../system/integrations/cti/generic.rst:11 msgid "" -"Before setting up the **Webhook**, you need to setup the global macro " -"**{$ZABBIX.URL}**, which must contain the **URL** to the **Zabbix frontend**." +"A telephone system that supports webhooks (outbound) (best option are those " +"that allow customizing the calls)." msgstr "" -#: ../system/integrations/zabbix.rst:33 -msgid "" -"In the **Administration** > **Media types** section, import the `Template`_." +#: ../system/integrations/cti/generic.rst:13 +msgid "A unique Call-ID during the call session." msgstr "" -#: ../system/integrations/zabbix.rst:38 -msgid "Open the added **Zammad** media type and set:" +#: ../system/integrations/cti/generic.rst:14 +msgid "Call event data (both numbers and direction)." msgstr "" -#: ../system/integrations/zabbix.rst:40 -msgid "**zammad\\_access\\_token** to the your **Personal User Token**" +#: ../system/integrations/cti/generic.rst:15 +msgid "Your Zammad instance must be reachable for your telephony system." msgstr "" -#: ../system/integrations/zabbix.rst:41 +#: ../system/integrations/cti/generic.rst:17 msgid "" -"**zammad\\_url** to the **frontend URL** of your **Zammad** installation" +"If you want to learn more on what kind of requests are supported by Zammad " +"and what it expects, please consult our :docs:`CTI-API documentation `." msgstr "" -#: ../system/integrations/zabbix.rst:43 -msgid "**zammad\\_customer** to your **Zammad user email**." +#: ../system/integrations/cti/generic.rst:22 +#: ../system/integrations/cti/placetel.rst:27 +#: ../system/integrations/cti/sipgate.rst:30 +msgid "Available Settings" msgstr "" -#: ../system/integrations/zabbix.rst:44 -msgid "" -"**zammad\\_enable\\_tags** to **true** or **false** to enable or disable " -"trigger tags. **Important**: if you enable tag support, each tag is set with " -"a separate request." +#: ../system/integrations/cti/generic.rst:29 +#: ../system/integrations/cti/placetel.rst:41 +#: ../system/integrations/cti/sipgate.rst:40 +msgid "Endpoint Settings" msgstr "" -#: ../system/integrations/zabbix.rst:48 +#: ../system/integrations/cti/generic.rst:25 msgid "" -"If you want to prioritize issues according to **severity** values in Zabbix, " -"you can define mapping parameters:" -msgstr "" - -#: ../system/integrations/zabbix.rst:51 -msgid "**severity\\_**: Zammad priority ID" -msgstr "" - -#: ../system/integrations/zabbix.rst:53 -msgid "Click the **Update** button to save the **Webhook** settings." +"Zammad will list your generic CTI endpoint here. It contains a unique token " +"so ensure to keep this URL save." msgstr "" -#: ../system/integrations/zabbix.rst:55 +#: ../system/integrations/cti/generic.rst:28 msgid "" -"To receive notifications in **Zammad**, you need to create a **Zabbix user** " -"and add **Media** with the **Zammad** type." +"You'll need this endpoint for your PBX to talk to Zammad, see :docs:`CTI-API " +"documentation `." msgstr "" -#: ../system/integrations/zabbix.rst:58 +#: ../system/integrations/cti/includes/important-dont-forget-saving.include.rst:3 msgid "" -"For **Send to**: enter any text, as this value is not used, but is required." +"All following options **do not save automatically**. Always use the Save " +"button on the lower end of the integration page!" msgstr "" -#: ../system/integrations/zabbix.rst:61 -msgid "" -"For more information, use the `Zabbix documentation `_." +#: ../system/integrations/cti/generic.rst:43 +#: ../system/integrations/cti/placetel.rst:49 +#: ../system/integrations/cti/sipgate.rst:52 +msgid "Call Settings" msgstr "" -#: ../system/maintenance.rst:2 -msgid "Maintenance" +#: ../system/integrations/cti/generic.rst:39 +#: ../system/integrations/cti/placetel.rst:49 +#: ../system/integrations/cti/sipgate.rst:37 +#: ../system/integrations/cti/sipgate.rst:50 +msgid "Inbound" msgstr "" -#: ../system/maintenance.rst:4 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:1 msgid "" -"Zammad comes with a maintenance mode that you can use for e.g. updating the " -"instance or changing settings while restricting availability and functions." +"This option allows you to block specific incoming caller IDs. It allows you " +"to temporarily reject e.g. spam callers without having to contact providers " +"or PBX administrators." msgstr "" -#: ../system/maintenance.rst:13 -msgid "Mode" +#: ../system/integrations/cti/includes/inbound-calls.include.rst:11 +msgid "Caller ID to block" msgstr "" -#: ../system/maintenance.rst:8 -msgid "The mode setting allows you to enable or disable the maintenance mode." +#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 +msgid "Provide caller IDs to block in ``E.164`` format." msgstr "" -#: ../system/maintenance.rst:10 -msgid "Defaults to *off*." +#: ../system/integrations/cti/includes/inbound-calls.include.rst:8 +msgid "" +"Your telephony system has to support this function. Zammad will send a " +"``reject`` response which will cause your telephony system to hang up the " +"call. To callers this usually will feel like the line is busy." msgstr "" -#: ../system/maintenance.rst:12 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:14 msgid "" -"The maintenance mode will restrict access to administrative roles only. This " -"means agents and customers are logged off." -msgstr "" - -#: ../system/maintenance.rst:23 -msgid "@Login" -msgstr "" - -#: ../system/maintenance.rst:16 -msgid "" -"This setting allows you to provide a login message within a green banner " -"above the login screen. Click into the green banner in the settings page to " -"adjust your message. To activate the message, activate the *@Login* setting." -msgstr "" - -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing the default login message within the\n" -"settings page" -msgstr "" - -#: ../system/maintenance.rst:26 -msgid "" -"Send an informative message to **all active sessions**. This comes handy to " -"inform your agents e.g. about mayor outages or to force reloads after " -"configuration changes." -msgstr "" - -#: ../system/maintenance.rst:31 -msgid "This is the messages title (slightly bigger than the normal message)." -msgstr "" - -#: ../system/maintenance.rst:34 -msgid "The text you want to provide to your logged in sessions." -msgstr "" - -#: ../system/maintenance.rst:39 -msgid "Reload application" -msgstr "" - -#: ../system/maintenance.rst:37 -msgid "" -"Selecting this option will change the message acceptance button from *Close* " -"(with nothing happening) to *Continue session*, which forces the application " -"to reload." -msgstr "" - -#: ../system/maintenance.rst:43 -msgid "" -"If you have customers that are logged in to Zammad, they'll also be notified " -"if they're active in that moment." -msgstr "" - -#: ../system/maintenance.rst:48 -msgid "Example without reload application" +"Provide a meaningful note for your fellow administrators to remind yourself " +"why you've chosen to block the number." msgstr "" -#: ../system/maintenance.rst:52 -msgid "" -"Message setting within Zammad's admin settings without ticket reload " -"application setting." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:17 +#: ../system/integrations/cti/sipgate.rst:40 +msgid "Outbound" msgstr "" -#: ../system/maintenance.rst:0 +#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:1 msgid "" -"Screenshot showing the send message settings without ticket\n" -"reload application set" +"In many cases you may want to use a different caller ID depending on the " +"destination you're calling. This may apply due to specific connection rates " +"to other countries or because you want your customer to feel you're calling " +"from the same country." msgstr "" -#: ../system/maintenance.rst:61 ../system/maintenance.rst:85 -msgid "" -"The modal all other active sessions will see upon pressing *Send to clients*." +#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:6 +msgid "This option expects ``E.164`` number formats." msgstr "" -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing modal caused by maintenance's message\n" -"without reload application ticket" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 +msgid "Destination caller ID" msgstr "" -#: ../system/maintenance.rst:72 -msgid "Example with reload application" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:5 +msgid "The caller ID or number you're trying to call." msgstr "" -#: ../system/maintenance.rst:76 -msgid "" -"Message setting within Zammad's admin settings with ticket reload " -"application setting." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:7 +msgid "You can use wildcards for e.g. country specific outbound numbers like:" msgstr "" -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing the send message settings with ticket\n" -"reload application set" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:9 +msgid "``49*`` for Germany" msgstr "" -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing modal caused by maintenance's message\n" -"with reload application ticket" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:10 +msgid "``4930*`` for Berlin / Germany landlines" msgstr "" -#: ../system/monitoring.rst:2 -msgid "Monitoring" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 +msgid "``33*`` for France" msgstr "" -#: ../system/monitoring.rst:4 -msgid "" -"This function is only available in self hosted instances. If you use Zammad " -"in our cloud, we are monitoring the system on our own and take steps to fix " -"potential problems directly." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:15 +msgid "Set Outbound caller ID" msgstr "" -#: ../system/monitoring.rst:11 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:14 msgid "" -"On the monitoring page, you can see the current health state of Zammad under " -"\"*Current Status*\" at the bottom. This can be useful if you want to have a " -"look if everything is up and running. As an example, you could have a look " -"in the monitoring when you assume that some emails aren't processed from " -"Zammad." +"The outbound caller ID to set (the number your customer sees on his display) " +"in ``E.164`` number format." msgstr "" -#: ../system/monitoring.rst:17 -msgid "**Can't receive an email and the monitoring response is \"healthy\"?**" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 +msgid "Provide a short description for fellow administrators." msgstr "" -#: ../system/monitoring.rst:19 +#: ../system/integrations/cti/includes/generic-cti-support-note.includes.rst:3 msgid "" -"Zammad will just inform you about unprocessable emails. This is not the case " -"for oversized emails. You can adjust the maximum email size in :doc:`../" -"channels/email/settings`." +"This option requires your PBX to send a specific request to Zammad *before " +"dialing*. Please consult the :docs:`CTI API ` in case " +"you're not sure." msgstr "" -#: ../system/monitoring.rst:24 -msgid "Monitoring API" +#: ../system/integrations/cti/generic.rst:52 +#: ../system/integrations/cti/placetel.rst:54 +#: ../system/integrations/cti/sipgate.rst:59 +msgid "Other Settings" msgstr "" -#: ../system/monitoring.rst:26 +#: ../system/integrations/cti/includes/other-settings-intro.include.rst:1 msgid "" -"Beside the indication in the monitoring page, you can also use an external " -"monitoring tool to monitor Zammad's health. To request the health of Zammad, " -"you need to provide the API key (token) to the external monitoring tool. You " -"can copy the token from the \"*Current Token*\" field as well as the whole " -"API endpoint of your system (\"*Health Check*\" field), in which the API " -"token is already included." +"Below you can find all available additional settings for this CTI " +"integration. For your overview we're sorting them by appearance and " +"reference their description first." msgstr "" -#: ../system/monitoring.rst:37 -msgid "Screenshot showing Current Token and Health Check" +#: ../system/integrations/cti/includes/default-caller-id.include.rst:2 +#: ../system/integrations/cti/includes/default-caller-id.include.rst:1 +msgid "Default caller ID for outbound calls" msgstr "" -#: ../system/monitoring.rst:37 -msgid "Screenshot showing Token and Health Check" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:16 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:15 +msgid "Shown records in caller log" msgstr "" -#: ../system/monitoring.rst:39 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:2 msgid "" -"In addition to that, you can reset the auto-generated token to make sure " -"that already configured monitoring systems won't work anymore. So, please " -"use this \"*Reset*\" button only if you know what you do!" -msgstr "" - -#: ../system/monitoring.rst:44 -msgid "Example Output" -msgstr "" - -#: ../system/monitoring.rst:0 -msgid "No issues found" -msgstr "" - -#: ../system/monitoring.rst:48 ../system/monitoring.rst:60 -msgid "**Indicator in Zammad**:" -msgstr "" - -#: ../system/monitoring.rst:0 -msgid "Screenshot showing monitoring with no issues" -msgstr "" - -#: ../system/monitoring.rst:54 ../system/monitoring.rst:66 -msgid "**API response**::" -msgstr "" - -#: ../system/monitoring.rst:0 -msgid "Issues were found" -msgstr "" - -#: ../system/monitoring.rst:0 -msgid "Screenshot showing monitoring with issues" -msgstr "" - -#: ../system/objects.rst:2 -msgid "Objects" +"Allows you to set the number of shown caller log entries for all users. You " +"can choose from the following values:" msgstr "" -#: ../system/objects.rst:4 -msgid "" -"In Zammad you can add your own fields to tickets, users, organizations and " -"even groups (these are called \"objects\"). This can be useful if you need " -"to add further information to a ticket or any other object in Zammad and the " -"information doesn't fit in any existing field." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:5 +msgid "60 (default)" msgstr "" -#: ../system/objects.rst:11 -msgid "" -"Try to avoid deleting attributes (and disable them instead) as Zammad might " -"run into unexpected conditions if they are referenced somewhere." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:6 +msgid "120" msgstr "" -#: ../system/objects.rst:16 -msgid "" -"Here's an overview of object attributes. On the upper right you can add new " -"attributes. By default, there will be no custom fields - standard attributes " -"will be grayed out, you can't delete or change those. You can edit custom " -"attributes (they are displayed in black font and have a trash bin on the " -"right side) just by clicking on them." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:7 +msgid "180" msgstr "" -#: ../system/objects.rst:24 -msgid "" -"Attributes you add to Zammad, no matter if they have default values or not, " -"will not update existing information. This means a new ticket field " -"technically will be empty unless you populate it." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:8 +msgid "240" msgstr "" -#: ../system/objects.rst:28 -msgid "" -"Especially in ticket scope this also means that newly added attributes will " -"be indicated as \"changed\" to agents that view the ticket. This may " -"interfere with Zammad's tabs behavior." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:9 +msgid "300" msgstr "" -#: ../system/objects.rst:40 -msgid "Ordering Attributes" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:11 +msgid "**🥵 Potential performance issue**" msgstr "" -#: ../system/objects.rst:42 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:13 msgid "" -"Since Zammad introduced :doc:`/system/core-workflows` the need to have a " -"custom positioning for attributes has become more important than ever." +"Setting this setting higher than 60 may cause serious performance issues on " +"very busy instances. Keep in mind that this setting causes Zammad to poll " +"and send up to 300 records to *all active agent sessions* in very short time " +"periods." msgstr "" -#: ../system/objects.rst:45 -msgid "" -"To adjust the position of such an attribute, simply click on the attribute " -"entry in question, scroll down and adjust the position number. Please note " -"that you cannot change the positioning of default attributes." +#: ../system/integrations/cti/generic.rst:73 +msgid "Caller Log Filter" msgstr "" -#: ../system/objects.rst:49 +#: ../system/integrations/cti/generic.rst:55 msgid "" -"In case two attributes have the same position value, Zammad will sort " -"alphabetically by name automatically." +"This function allows you to provide call information based on e.g. queues " +"only to agents that really need the information." msgstr "" -#: ../system/objects.rst:None +#: ../system/integrations/cti/generic.rst:58 msgid "" -"Screenshot showing custom attribute entries ordered in between default ones" +"Why? If you have a team for several countries or departments, you don't want " +"to bug your agents from other departments. Leaving these options empty will " +"fallback to showing everything to everyone." msgstr "" -#: ../system/objects.rst:56 -msgid "Updating Database After Adding or Editing Attributes" +#: ../system/integrations/cti/generic.rst:64 +msgid "Destination caller ID or Queue" msgstr "" -#: ../system/objects.rst:58 +#: ../system/integrations/cti/generic.rst:63 msgid "" -"When adding or changing attributes, Zammad will not apply the changes " -"instantly, but instead shows you the changed attributes first. If you're " -"ready to go, just click on \"Update database\" to apply the changes to " -"Zammad. If you made a mistake or just want to discard your changes, click " -"\"Discard changes\"." +"This depends on your PBX and usually is either a queue ID, phone number or " +"extension." msgstr "" -#: ../system/objects.rst:64 -msgid "" -"After applying the changes with \"Update Database\", a restart of Zammad is " -"**mandatory**. If you don't perform it, you may experience unexpected " -"behavior or even errors. You may want to do this kind of configuration " -"during maintenance windows." +#: ../system/integrations/cti/generic.rst:69 +msgid "Agents" msgstr "" -#: ../system/objects.rst:72 +#: ../system/integrations/cti/generic.rst:67 msgid "" -"Changes on objects require you to update the database to apply these changes." +"Select the agents that are responsible for the group. These agents will then " +"see caller log entries and call notifications fitting to said queue." msgstr "" -#: ../system/objects.rst:75 -msgid "**🤓 Service restarts can be automated**" +#: ../system/integrations/cti/generic.rst:0 +msgid "" +"Screenshot showing the caller log filter table with pre filled sample data" msgstr "" -#: ../system/objects.rst:0 -msgid "Hosted environments automatically restart for you." +#: ../system/integrations/cti/includes/recent-logs.include.rst:6 +msgid "" +"With recent logs Zammad allows you to view the latest calls for the CTI " +"functionality. This usually comes in handy, when you're looking for errors." msgstr "" -#: ../system/objects.rst:0 +#: ../system/integrations/cti/includes/recent-logs.include.rst:0 msgid "" -"If you're using a self-hosted installation you can use :docs:`environment " -"variables `" +"Screenshot showing several incoming requests within Recent logs section." msgstr "" -#: ../system/objects.rst:82 -msgid "System Attributes" +#: ../system/integrations/cti/includes/recent-logs.include.rst:16 +msgid "I'm just here to clear floats up." msgstr "" -#: ../system/objects.rst:84 +#: ../system/integrations/cti/includes/recent-logs.include.rst:20 msgid "" -"Zammad comes with pre-configured attributes. Some of them can't be edited " -"via UI (or at all). This is required for proper operation of Zammad and not " -"a bug." -msgstr "" - -#: ../system/objects.rst:90 -msgid "Ticket State" +"By clicking on the entry of interest, Zammad will provide more details on " +"the call in question. You'll see the payload it received and also the " +"response that was sent." msgstr "" -#: ../system/objects.rst:92 +#: ../system/integrations/cti/includes/recent-logs.include.rst:0 msgid "" -"If the pre-configured states aren't enough for you or you want to change " -"them, you can do so by clicking on the cogwheel icon in the state row in the " -"ticket tab. But you should be careful when changing pre-configured states. " -"This can lead to unwanted behavior in some cases." +"Screenshot showing detailed information of a specific log entry of recent " +"logs" msgstr "" -#: ../system/objects.rst:None -msgid "Screenshot showing highlighted ticket state attribute" +#: ../system/integrations/cti/includes/recent-logs.include.rst:31 +msgid "x" msgstr "" -#: ../system/objects.rst:122 -msgid "Handling of states" +#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 +#: ../system/integrations/cti/includes/troubleshooting.include.rst:9 +msgid "My Phone page stays blank, signalling does work..." msgstr "" -#: ../system/objects.rst:102 +#: ../system/integrations/cti/includes/troubleshooting.include.rst:5 msgid "" -"In the state configuration screen, you can add new states, disable states or " -"change states." +"If you've made sure that signalling works (check Recent logs) and your " +"Caller Log still stays empty, please ensure that you only configured one CTI " +"integration version. Specifically defining more than one agent mapping on " +"the different integration variants will be the issue." msgstr "" -#: ../system/objects.rst:0 -msgid "Screenshot showing table of default ticket states" +#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 +msgid "Clear the not needed agent mapping and reload your browser page." msgstr "" -#: ../system/objects.rst:110 +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:1 msgid "" -"To add a new state, click on the \"New Ticket State\" button in the top " -"right corner. To change an existing state, simply click on the affected " -"state. This opens an edit dialog." +"By mapping your agents extension to their existing Zammad users, Zammad can " +"provide a new ticket dialog or open the user profile for the agent that " +"picks up the call." msgstr "" -#: ../system/objects.rst:114 +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:5 msgid "" -"You can also clone a state or set them to \"Default for new tickets\" or " -"\"Default for follow-ups\" by clicking on the ⁝ action button and select the " -"desired function." +"This speeds up ticket aiding, no matter if it's for existing tickets or new " +"ones!" msgstr "" -#: ../system/objects.rst:118 +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:8 msgid "" -"*Default for new tickets* means that this state is used for every newly " -"created ticket." +"To see it work from the agent's perspective, have a look on :user-docs:`user " +"documentation `." msgstr "" -#: ../system/objects.rst:121 -msgid "" -"*Default for follow-ups* means that this state is used if the ticket is re-" -"opened after it was closed." +#: ../system/integrations/cti/placetel.rst:2 +msgid "Placetel CTI" msgstr "" -#: ../system/objects.rst:171 -msgid "Ticket state in detail" +#: ../system/integrations/cti/placetel.rst:16 +msgid "You need an administrative Placetel account for your organization." msgstr "" -#: ../system/objects.rst:125 +#: ../system/integrations/cti/placetel.rst:17 +#: ../system/integrations/cti/sipgate.rst:20 msgid "" -"Below you can find a description for each field and option. Please head over " -"to the :ref:`example ` to see the edit dialog." +"Your Zammad instance must be allowed to communicate to external services." msgstr "" -#: ../system/objects.rst:129 -msgid "" -"This is the name of the state and what you and your agents are seeing when " -"choosing a state somewhere (e.g. in tickets, trigger configuration)." +#: ../system/integrations/cti/placetel.rst:18 +msgid "Placetel must be able to reach your Zammad instance." msgstr "" -#: ../system/objects.rst:137 -msgid "" -"There are different state types you can choose from. By default, Zammad " -"comes with one state per state type." +#: ../system/integrations/cti/placetel.rst:22 +msgid ":doc:`provider-configurations/placetel`" msgstr "" -#: ../system/objects.rst:140 +#: ../system/integrations/cti/placetel.rst:21 msgid "" -"**new**: for states for tickets that are new and it hasn't been worked on " -"them" +"Learn how to configure Placetel to enable Zammad and Placetel to communicate " +"with each other." msgstr "" -#: ../system/objects.rst:142 +#: ../system/integrations/cti/placetel.rst:32 msgid "" -"**open**: for states for tickets that are in progress and agents are working " -"on them" -msgstr "" - -#: ../system/objects.rst:144 -msgid "**merged**: for states for tickets that are merged with other tickets" +"The here listed endpoint settings are relevant for the :doc:`integration " +"configuration with Placetel `." msgstr "" -#: ../system/objects.rst:145 -msgid "" -"**pending reminder**: for states for tickets that are in progress and you " -"want to set a reminder. (default example: *pending reminder*)" +#: ../system/integrations/cti/placetel.rst:37 +#: ../system/integrations/i-doit.rst:53 +msgid "Endpoint" msgstr "" -#: ../system/objects.rst:147 +#: ../system/integrations/cti/placetel.rst:36 msgid "" -"**pending action**: for states for tickets that are waiting for a specified " -"time and then change their state (default example: *pending close*)" +"This endpoint will be required for the Zammad integration within the " +"Placetel web interface." msgstr "" -#: ../system/objects.rst:150 -msgid "" -"**closed**: for states for tickets that are finished and do not need to be " -"processed further" +#: ../system/integrations/cti/placetel.rst:41 +msgid "API Token" msgstr "" -#: ../system/objects.rst:153 +#: ../system/integrations/cti/placetel.rst:40 msgid "" -"⚠️ Choosing the correct state type is important! If you are in doubt, have a " -"look on the default states and their types!" +"You'll receive this token within the ``Web API`` menu. Make sure to copy " +"this value, it's only shown once!" msgstr "" -#: ../system/objects.rst:158 -msgid "Ignore escalation" +#: ../system/integrations/cti/placetel.rst:71 +#: ../system/integrations/cti/sipgate.rst:77 +msgid "Phone Extension to Agent Mapping" msgstr "" -#: ../system/objects.rst:157 -msgid "" -"Here you can define whether tickets of this state will count to escalation " -"time or not." +#: ../system/integrations/cti/placetel.rst:0 +msgid "Screenshot showing sample user mappings in between Placetel and Zammad" msgstr "" -#: ../system/objects.rst:161 +#: ../system/integrations/cti/placetel.rst:64 msgid "" -"You can create a note for the state to inform other admins about the state. " -"This has no effect on tickets." +"You can find your agents Placetel username combination required within ⚙️ PBX " +"→ VoIP destinations. Within the \"Advanced settings\" section you're looking " +"for \"SIP user name\" and \"SIP server\"." msgstr "" -#: ../system/objects.rst:165 -msgid "Set the state to *active* or *inactive*." +#: ../system/integrations/cti/placetel.rst:68 +msgid "Combine these two like so: ``@``." msgstr "" -#: ../system/objects.rst:167 -msgid "" -"it is technically possible to set all states to inactive. To keep Zammad " -"working in such a case, the inactive flag of one of the states is ignored." +#: ../system/integrations/cti/placetel.rst:0 +msgid "Sample VoIP credentials for a Placetel user" msgstr "" -#: ../system/objects.rst:194 -msgid "Ticket state example" +#: ../system/integrations/cti/provider-configurations/placetel.rst:2 +msgid "Setup Placetel connection for Zammad" msgstr "" -#: ../system/objects.rst:174 +#: ../system/integrations/cti/provider-configurations/placetel.rst:6 msgid "" -"Let's assume we want to create a new state which indicates that the ticket " -"has to wait for a response of a third party (e.g. service contractor or " -"manufacturer) and we want to to be able to set a reminder." +"This configuration step requires a *full* administrative Placetel account. " +"You may receive forbidden error messages with Placetel in case your " +"permissions are not high enough." msgstr "" -#: ../system/objects.rst:178 +#: ../system/integrations/cti/provider-configurations/placetel.rst:10 msgid "" -"First we give the new state a proper name. In this example we call it " -"\"waiting for manufacturer\"." +"The following actions can be configured via the `Placetel web interface " +"`_." msgstr "" -#: ../system/objects.rst:181 -msgid "" -"As state type we choose \"pending reminder\". This indicates that the ticket " -"is still open and we can set a reminder. This reminder can be useful if our " -"manufacturer sometimes isn't responding or we want to remind him to give us " -"an answer." +#: ../system/integrations/cti/provider-configurations/placetel.rst:29 +msgid "Step 1: Activate Zammad integration" msgstr "" -#: ../system/objects.rst:186 +#: ../system/integrations/cti/provider-configurations/placetel.rst:14 msgid "" -"We choose \"no\" for \"ignore escalation\" because we want to escalate the " -"tickets even if we are waiting on the manufacturer's feedback." -msgstr "" - -#: ../system/objects.rst:189 -msgid "The **result** in the creation dialog will look like this:" +"Within Integrations, scroll down to Partner integrations and select Zammad." msgstr "" -#: ../system/objects.rst:0 -msgid "Screenshot showing ticket state creation dialog with example" +#: ../system/integrations/cti/provider-configurations/placetel.rst:17 +msgid "" +"You can alternatively filter by \"Ticket Systems\" to reduce the number of " +"entries on the page. You'll still want to look for Partner integrations. 🤓" msgstr "" -#: ../system/objects.rst:197 ../system/objects.rst:199 -msgid "Ticket Priority" +#: ../system/integrations/cti/provider-configurations/placetel.rst:21 +msgid "" +"Within the Zammad integration now press \"Activate\". A new tab ``API`` " +"becomes available - open this tab." msgstr "" -#: ../system/objects.rst:199 ../system/objects.rst:201 +#: ../system/integrations/cti/provider-configurations/placetel.rst:24 msgid "" -"If the pre-configured priorities aren't enough for you or you want to change " -"them, you can do so by clicking on the cogwheel icon in the priority row in " -"the ticket tab:" +"Now tick \"Enable Call Control / Notify API\" and paste the Placetel " +"endpoint from your Zammad instance into the field \"URL of your API " +"endpoint\". Save to apply the settings" msgstr "" -#: ../system/objects.rst:None -msgid "Screenshot showing highlighted ticket priority attribute" +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "Screencast showing how to activate the Zammad integration" msgstr "" -#: ../system/objects.rst:224 ../system/objects.rst:226 -msgid "Handling of priorities" +#: ../system/integrations/cti/provider-configurations/placetel.rst:51 +msgid "Step 2: Generate API Token for Placetel" msgstr "" -#: ../system/objects.rst:208 ../system/objects.rst:210 +#: ../system/integrations/cti/provider-configurations/placetel.rst:32 msgid "" -"In the priority configuration screen, you can add new priorities, disable " -"priorities or change priorities." +"Go back to the integrations page and scroll down to \"Web API\". Generate a " +"new API token by using the \"Create a new API token\" button." msgstr "" -#: ../system/objects.rst:0 -msgid "Screenshot showing table of default ticket priorities" +#: ../system/integrations/cti/provider-configurations/placetel.rst:37 +msgid "" +"If you already generated a token either use your existing token or reset it " +"by using above mentioned button. Placetel will ask you to conform this reset." msgstr "" -#: ../system/objects.rst:216 ../system/objects.rst:218 +#: ../system/integrations/cti/provider-configurations/placetel.rst:41 msgid "" -"To add a new priority, click on the \"New Priority\" button in the top right " -"corner. To change an existing priority, simply click on the affected " -"priority. This opens an edit dialog." +"Please keep in mind that existing API scripts may no longer work due to " +"token resets!" msgstr "" -#: ../system/objects.rst:220 ../system/objects.rst:222 +#: ../system/integrations/cti/provider-configurations/placetel.rst:44 msgid "" -"You can also clone a priority or set them to \"Default for new tickets\" by " -"clicking on the ⁝ action button and select the desired function." +"Copy the provided API token and insert it into the \"API Token\" field " +"within Zammad's Placetel integration." msgstr "" -#: ../system/objects.rst:223 ../system/objects.rst:225 +#: ../system/integrations/cti/provider-configurations/placetel.rst:47 msgid "" -"*Default for new tickets* means that this priority is used for every newly " -"created ticket." +"Apply your changes by using the \"Save\" button on the bottom of the " +"Placetel integration page and activate the Placetel integration." msgstr "" -#: ../system/objects.rst:246 ../system/objects.rst:248 -msgid "Priorities in detail" +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "" +"Screencast showing how to retrieve an API token from Placetel for Zammad" msgstr "" -#: ../system/objects.rst:227 ../system/objects.rst:229 -msgid "Below you can find a description for each field and option." +#: ../system/integrations/cti/provider-configurations/placetel.rst:73 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:77 +msgid "Step 3: Restrict the numbers to notify on" msgstr "" -#: ../system/objects.rst:230 ../system/objects.rst:232 +#: ../system/integrations/cti/provider-configurations/placetel.rst:54 msgid "" -"This is the name of the priority and what you and your agents are seeing " -"when choosing a priority somewhere (e.g. in tickets, trigger configuration)." +"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " +"the the Integrations page of the Placetel web interface, go to \"Notify " +"API\"." msgstr "" -#: ../system/objects.rst:240 ../system/objects.rst:242 -msgid "Highlight color" +#: ../system/integrations/cti/provider-configurations/placetel.rst:58 +msgid "" +"Lower on the page Placetel allows you to restrict the numbers to notify on. " +"You'll find this within the \"External routing API\" part." msgstr "" -#: ../system/objects.rst:235 ../system/objects.rst:237 +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 msgid "" -"Switch between *Low priority* (light blue), *High priority* (red) and - " -"(default). This affects the displayed color for ticket titles in overviews." +"Screenshot showing a sample selection of phone numbers to use for the " +"Placetels notify API" msgstr "" -#: ../system/objects.rst:239 ../system/objects.rst:241 -msgid "The color options are currently limited to the mentioned options." +#: ../system/integrations/cti/provider-configurations/placetel.rst:66 +msgid "" +"This menu point also provides a API request log from Placetel view. Just " +"open \"Recent responses of your API endpoint\" to learn more." msgstr "" -#: ../system/objects.rst:243 ../system/objects.rst:245 +#: ../system/integrations/cti/provider-configurations/placetel.rst:69 msgid "" -"You can create a note for the priority to inform other admins about the " -"priority. This has no effect on tickets." +"If you want to see Zammad's perspective, use the \"Recent Logs\" part from " +"within the Placetel integration page." msgstr "" -#: ../system/objects.rst:247 ../system/objects.rst:249 -msgid "Set the priority to *active* or *inactive*." +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "Screenshot showing sample log entries for Placetels API calls to Zammad" msgstr "" -#: ../system/objects/external-data-source-example.rst:2 -msgid "External Data Source" +#: ../system/integrations/cti/provider-configurations/placetel.rst:77 +msgid "Step 4 (optional): Further configurations for Placetel" msgstr "" -#: ../system/objects/external-data-source-example.rst:4 +#: ../system/integrations/cti/provider-configurations/placetel.rst:76 msgid "" -"We assume you already had a look on :doc:`types` where you can find a " -"description of the individual fields." +"If needed, you can now configure Zammad's Placetel integration in more " +"detail. You can learn more about your options here: :ref:`Placetel " +"integration settings `." msgstr "" -#: ../system/objects/external-data-source-example.rst:7 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:2 +msgid "Setup Sipgate connection for Zammad" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"To reproduce this example, choose a category you want to add a custom field, " -"click on *New Attribute* and select *External data source field* under " -"*Format*." +"Sipgate has no english web interface which is why this documentation page is " +"mixing up languages badly." msgstr "" -#: ../system/objects/external-data-source-example.rst:11 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"Our example story is to fetch data from an external product database. We " -"want to add our products to the tickets so that the products can be searched " -"and chosen from a list and also create a link to the product website." +"Please also note that the availability of API addons highly depends on your " +"package trier. Usage of sipgate.io packages *is not free*, please check " +"their `pricing page `_ before!" msgstr "" -#: ../system/objects/external-data-source-example.rst:16 -msgid "Base configuration" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:35 +msgid "Step 1: Book sipgate.io package" msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Initial steps to configure external data source object type" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:13 +msgid "Skip to step 2 if you already have the package booked!" msgstr "" -#: ../system/objects/external-data-source-example.rst:23 -#: ../system/variables.rst:85 -msgid "**Example:**" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:15 +msgid "" +"Login to an administrative Sipgate account and navigate to " +"``Accountverwaltung``. You'll see several different options depending on " +"your booked packages. Select ``Verträge & Produkte`` to continue." msgstr "" -#: ../system/objects/external-data-source-example.rst:25 -msgid "Name: *product*" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:19 +msgid "" +"Scroll down to the section ``Zusätzliche Produkte buchen`` and look for " +"``sipgate.io`` - select this product by using the ``Produkte anzeigen``-" +"Button." msgstr "" -#: ../system/objects/external-data-source-example.rst:26 -msgid "Display: *Product*" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:23 +msgid "" +"On the next page select either one of the ``sipgate.io`` packages or ``Push-" +"API Package Free``. Follow the dialogue by booking the addon. You'll be " +"returned to your contract overview and now should see the selected addon in " +"your list." msgstr "" -#: ../system/objects/external-data-source-example.rst:29 -msgid "External data source configuration" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:30 +msgid "" +"The availability for ``sipgate.io`` packages and their levels highly depends " +"on the overall account type and product you've booked with Sipgate." msgstr "" -#: ../system/objects/external-data-source-example.rst:31 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"First, enter the search URL making sure it contains ``#{search.term}`` as a " -"parameter:" +"Screencast showing the process on how to book the required sipgate.io addon" msgstr "" -#: ../system/objects/external-data-source-example.rst:34 -msgid "**Example:** ``https://dummyjson.com/products/search?q=#{search.term}``" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:52 +msgid "Step 2: Configure webhook for Zammad" msgstr "" -#: ../system/objects/external-data-source-example.rst:36 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:38 msgid "" -"After that, head down to the preview section and enter a search input for " -"the external data source." +"Within your ``Accountverwaltung`` navicate to your product ``sipgate.io``. " +"In the newly opened tab, switch from \"Clients\" to \"Webhooks\" and paste " +"the endpoint URLs from your Zammad instance like so:" msgstr "" -#: ../system/objects/external-data-source-example.rst:39 -msgid "**Example:** ``mac``" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:42 +msgid "Inbound endpoint to \"Incoming\"" msgstr "" -#: ../system/objects/external-data-source-example.rst:41 -msgid "Then you can find a preview of the response data below:" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:43 +msgid "Outbound endpoint to \"Outgoing\"" msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of JSON response based on search term" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:47 +msgid "" +"Ensure to select at least one call group or phoneline within \"Sources\". " +"Other wise Sipgate will not indicate any incoming or outgoing calls to " +"Zammad." msgstr "" -#: ../system/objects/external-data-source-example.rst:48 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"We recommend using the preview to have a look on the structure. There is a " -"top-level element called ``products``. One level below, you can find the " -"attributes ``id`` and ``title``." +"Screencast showing how to add Zammad's endpoint URLs to sipgate.ios webhook " +"configuration" msgstr "" -#: ../system/objects/external-data-source-example.rst:52 -msgid "**Search result response based on search from example:**" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:55 +msgid "" +"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " +"the Webhooks → URLs section of Sipgate you can select which *sources* " +"Sipgate should notify Zammad about in- and outgoing calls." msgstr "" -#: ../system/objects/external-data-source-example.rst:119 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:59 msgid "" -"To tell the remote system that the desired data is located below the " -"``products`` level, you have to put it in the field *Search result list key*." +"Use either specific phone lines or use the option \"Use for all phonelines " +"and groups\" to notify Zammad about all existing lines of your Sipgate " +"account." msgstr "" -#: ../system/objects/external-data-source-example.rst:122 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"After inserting ``products`` in the mentioned field, you get an extended " -"preview. You can find an additional box *Search result list* with a JSON " -"structure. This is the same response as before but stripped from the upper " -"``products`` element by the external data source." +"Screenshot showing a sample selection of phone numbers to use for the " +"Sipgates webhooks API" msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of JSON response search result list" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:68 +msgid "This section also allows you to enable a Debug log." msgstr "" -#: ../system/objects/external-data-source-example.rst:132 -msgid "" -"Now you need to provide the keys for the search result values and labels. As " -"already mentioned, we are looking for the ``id`` and the ``title`` of our " -"products. If you haven't already, it is now a good time to look at the " -"preview of the *Search result list*." +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "Screenshot showing an enabled Debug log option" msgstr "" -#: ../system/objects/external-data-source-example.rst:197 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:73 msgid "" -"After locating our two keys, we insert them in *search result value key* " -"(``id``) and in *Search result label key* (``title``)." +"After enabling you can use the Debug log section to see all sent webhook " +"calls to Zammad. You'll also can see the response." msgstr "" -#: ../system/objects/external-data-source-example.rst:200 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"Basically, we configured the external data source already and we can see a " -"table in the preview section:" -msgstr "" - -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of product table based on search term" +"Screenshot showing sample log entries for Sipgates webhook calls to Zammad" msgstr "" -#: ../system/objects/external-data-source-example.rst:208 -msgid "" -"According to our example story, now just the *Link template* is missing." +#: ../system/integrations/cti/provider-configurations/sipgate.rst:81 +msgid "Step 4 (optional): Further configurations for Sipgate" msgstr "" -#: ../system/objects/external-data-source-example.rst:210 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:80 msgid "" -"Please note that this is an optional feature. If you don't want to use such " -"links, of course you don't have to configure it." +"If needed, you can now configure Zammad's Sipgate integration in more " +"detail. You can learn more about your options here: :ref:`Sipgate " +"integration settings `." msgstr "" -#: ../system/objects/external-data-source-example.rst:213 -msgid "" -"We can add now an address where additional product information can be found." +#: ../system/integrations/cti/sipgate.rst:2 +msgid "Sipgate (sipgate.io)" msgstr "" -#: ../system/objects/external-data-source-example.rst:215 -msgid "Example: ``https://your_domain.com/q=#{ticket.product}``" +#: ../system/integrations/cti/sipgate.rst:16 +msgid "You need an administrative Sipgate account for your organization." msgstr "" -#: ../system/objects/external-data-source-example.rst:217 -msgid "In the example, the parameter means:" +#: ../system/integrations/cti/sipgate.rst:17 +msgid "" +"Zammad requires a ``sipgate.io`` addon from the feature store (please note " +"that API calls are not free with Sipgate. Rates may apply and differ from " +"account to account)." msgstr "" -#: ../system/objects/external-data-source-example.rst:219 -msgid "``#{}``: \"Frame\" for the insertion of information" +#: ../system/integrations/cti/sipgate.rst:21 +msgid "Sipgate must be able to reach your Zammad instance." msgstr "" -#: ../system/objects/external-data-source-example.rst:220 -msgid "``ticket``: object level, where you create your custom object" +#: ../system/integrations/cti/sipgate.rst:25 +msgid ":doc:`provider-configurations/sipgate`" msgstr "" -#: ../system/objects/external-data-source-example.rst:221 -msgid "``product``: name of the (custom) object" +#: ../system/integrations/cti/sipgate.rst:24 +msgid "" +"Learn how to configure Sipgate to enable Zammad and Sipgate to communicate " +"with each other." msgstr "" -#: ../system/objects/external-data-source-example.rst:223 +#: ../system/integrations/cti/sipgate.rst:33 msgid "" -"After configuring your *Link template*, there will be another column in the " -"preview. Hovering on the icons in the *Link* column will show you where it " -"forwards you." +"Below endpoint settings affect the :doc:`sipgate.io configuration `." msgstr "" -#: ../system/objects/external-data-source-example.rst:232 -msgid "" -"In our example, one of the links looks like: https://your_domain.com/q=6, " -"where the 6 is the product id." +#: ../system/integrations/cti/sipgate.rst:37 +msgid "This endpoint is required for incoming call hooks." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:40 +msgid "This endpoint is required for outgoing call hooks." msgstr "" -#: ../system/objects/external-data-source-example.rst:235 -msgid "You can find more information regarding the URL in :doc:`types`." +#: ../system/integrations/cti/sipgate.rst:0 +msgid "Screenshot showing sample user mappings in between Sipgate and Zammad" msgstr "" -#: ../system/objects/includes/adding-values-hint.include.rst:3 +#: ../system/integrations/cti/sipgate.rst:69 msgid "" -"Adding values can be tricky for first timers, don't forget to press \"➕ " -"Add\" after typing your values. Otherwise you may loose a value." +"You can find your agent's Sipgate username within ``Accountverwaltung → " +"Benutzer``. You're looking for the SIP-ID." msgstr "" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:1 -#: ../system/objects/includes/reposition-values.include.rst:1 -msgid "**↕️ This field type allows the positioning of its values ↔️**" +#: ../system/integrations/cti/sipgate.rst:0 +msgid "Sample VoIP credentials for a Sipgate user" msgstr "" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:3 -msgid "" -"In order to re-arrange the field values, first edit the field. Then you can " -"use ☰ to drag the values in question to the correct position. If you want to " -"change the layer depth, double click on ☰. With it you can cycle through the " -"available layers." +#: ../system/integrations/cti/sipgate.rst:77 +msgid "Users with several devices also have several SIP-IDs." msgstr "" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:8 -msgid "When you're ready, submit your changes to save the object attribute." +#: ../system/integrations/elasticsearch.rst:2 +msgid "Elasticsearch (SaaS)" msgstr "" -#: :0 ../system/objects/types.rst:0 +#: ../system/integrations/elasticsearch.rst:4 msgid "" -"Screencast showing how to re-position values on tree select like\n" -"fields" +"The Elasticsearch integration allows you to create a read-only user to use " +"with your favorite reporting tool (e.g. like Grafana)." msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:3 +#: ../system/integrations/elasticsearch.rst:7 msgid "" -"In order to re-arrange the field values, edit the field and scroll below the " -"values. Make sure to tick the option \"Use custom option sort\"." +"If you want to take full advantage of the Zammad reporting, have a look at " +"our :docs:`Grafana ` " +"setup page as well." msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:8 -msgid "" -"If you do not tick this field, all manual positioning you did above will be " -"lost upon saving! ☠️" +#: ../system/integrations/elasticsearch.rst:11 ../system/subscription.rst:7 +msgid "**🚧 Hosted environment specific 🚧**" msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:11 +#: ../system/integrations/elasticsearch.rst:13 msgid "" -"Now use ☰ to drag the values in question to the correct position. When " -"you're ready, submit your changes to save the object attribute." -msgstr "" - -#: :0 ../system/objects/types.rst:0 -msgid "Screencast showing how to re-position values" +"This integration is only available for Hosted setups. In order to use " +"Elasticsearch you'll need the **Plus** subscription." msgstr "" -#: ../system/objects/includes/url-template-hint.include.rst:3 +#: ../system/integrations/elasticsearch.rst:16 msgid "" -"This field allows using :ref:`URL fields (Link Templates) `." +"Self hosted users have all the control over their self hosted Elasticsearch " +"instances." msgstr "" -#: ../system/objects/permissions.rst:2 -msgid "Attribute Permissions" +#: ../system/integrations/elasticsearch.rst:None +msgid "Elasticsearch integration page on SaaS environments" msgstr "" -#: ../system/objects/permissions.rst:7 +#: ../system/integrations/elasticsearch.rst:27 msgid "" -"In the object attributes configuration you can define if a field is shown " -"and if the input in the field is mandatory, separated by different screens " -"and for different :doc:`roles/permissions `." +"Please note the following limitations of Elasticsearch access on hosted " +"environments:" msgstr "" -#: ../system/objects/permissions.rst:17 -msgid "Screenshot shows object attribute permission table" +#: ../system/integrations/elasticsearch.rst:30 +msgid "access to the Elasticsearch index is read-only access" msgstr "" -#: ../system/objects/permissions.rst:17 -msgid "" -"Some of the possible permissions and screen options for a user object " -"attribute." +#: ../system/integrations/elasticsearch.rst:31 +msgid "currently you're limited to user only" msgstr "" -#: ../system/objects/permissions.rst:19 +#: ../system/integrations/elasticsearch.rst:32 msgid "" -"Based on the object context (ticket, agent, organization, user), the " -"selectable roles (to be precise: the required permissions) and screens " -"differ. Be aware that these settings aren't affecting data creation via " -"other channels than the UI." +"Reporting tools that require to write into the indexes (like Kibana) are not " +"supported" msgstr "" -#: ../system/objects/permissions.rst:24 -msgid "" -"If you want to have further customization possibilities, you should have a " -"look at the :doc:`core workflows `." +#: ../system/integrations/elasticsearch.rst:34 +msgid "IP access restriction is currently not yet supported" msgstr "" -#: ../system/objects/permissions.rst:28 -msgid "Screens" +#: ../system/integrations/elasticsearch.rst:37 +msgid "Activating Elasticsearch Access" msgstr "" -#: ../system/objects/permissions.rst:30 +#: ../system/integrations/elasticsearch.rst:39 msgid "" -"In the table below you can find an overview about the different permissions " -"and the available screens Zammad distinguishes between." -msgstr "" - -#: ../system/objects/permissions.rst:37 -msgid "Screen" +"By default external access to your Elasticsearch index is not active. You " +"can enable the integration at any time if needed." msgstr "" -#: ../system/objects/permissions.rst:38 -msgid "Available for" +#: ../system/integrations/elasticsearch.rst:42 +msgid "" +"Please ensure to note down the password provided - you won't have access to " +"it afterwards." msgstr "" -#: ../system/objects/permissions.rst:40 -msgid "create" +#: ../system/integrations/elasticsearch.rst:None +msgid "Screencast showing activation of Elasticsearch integration" msgstr "" -#: ../system/objects/permissions.rst:41 ../system/objects/permissions.rst:52 -#: ../system/objects/permissions.rst:59 ../system/objects/permissions.rst:73 -msgid "admin.user" +#: ../system/integrations/elasticsearch.rst:51 +msgid "Connection Settings" msgstr "" -#: ../system/objects/permissions.rst:42 ../system/objects/permissions.rst:53 -#: ../system/objects/permissions.rst:60 -msgid "admin.organization" +#: ../system/integrations/elasticsearch.rst:53 +msgid "" +"This section holds the most important general information for accessing your " +"Elasticsearch indexes - such as:" msgstr "" -#: ../system/objects/permissions.rst:43 ../system/objects/permissions.rst:54 -#: ../system/objects/permissions.rst:61 -msgid "admin.group" +#: ../system/integrations/elasticsearch.rst:57 +msgid "A unique subdomain that does not tell your real instance URL." msgstr "" -#: ../system/objects/permissions.rst:44 -msgid "Creation dialog for not yet existing data" +#: ../system/integrations/elasticsearch.rst:61 +msgid "Software" msgstr "" -#: ../system/objects/permissions.rst:45 -msgid "create_middle" +#: ../system/integrations/elasticsearch.rst:60 +msgid "" +"The major version of the search index being used. This is required by some " +"Reporting tools like Grafana." msgstr "" -#: ../system/objects/permissions.rst:46 ../system/objects/permissions.rst:50 -#: ../system/objects/permissions.rst:57 ../system/objects/permissions.rst:66 -#: ../system/objects/permissions.rst:70 -msgid "ticket.customer" +#: ../system/integrations/elasticsearch.rst:64 +msgid "Authentication" msgstr "" -#: ../system/objects/permissions.rst:47 ../system/objects/permissions.rst:51 -#: ../system/objects/permissions.rst:58 ../system/objects/permissions.rst:69 -msgid "ticket.agent" +#: ../system/integrations/elasticsearch.rst:64 +msgid "The authentication type being supported. ``Basic Authentication``" msgstr "" -#: ../system/objects/permissions.rst:48 -msgid "Ticket create dialog (middle section)" +#: ../system/integrations/elasticsearch.rst:67 +msgid "Available Indexes" msgstr "" -#: ../system/objects/permissions.rst:49 -msgid "edit" +#: ../system/integrations/elasticsearch.rst:69 +msgid "" +"Within this section we're displaying the -in our opinion- most important " +"indexes for a Zammad instance." msgstr "" -#: ../system/objects/permissions.rst:55 -msgid "Editing dialog for already existing data" +#: ../system/integrations/elasticsearch.rst:72 +msgid "" +"If you require all indexes or our listing is not good enough for you, point " +"your browser to the URL we're providing and append ``/_aliases?" +"pretty=true``. The result should look like this: ``https://.zammad.com/" +"_aliases?pretty=true``." msgstr "" -#: ../system/objects/permissions.rst:56 -msgid "view" +#: ../system/integrations/elasticsearch.rst:77 +msgid "" +"Your browser will automatically ask for your credentials - you'll then see " +"something like this:" msgstr "" -#: ../system/objects/permissions.rst:62 -msgid "View-only dialog for already existing data" +#: ../system/integrations/elasticsearch.rst:125 +msgid "Credentials" msgstr "" -#: ../system/objects/permissions.rst:64 -msgid "(e.g. user or organization from search)" +#: ../system/integrations/elasticsearch.rst:127 +msgid "" +"Within this section Zammad displays your available users. The password is " +"provided once (upon activation) and cannot be retrieved after that." msgstr "" -#: ../system/objects/permissions.rst:65 -msgid "signup" +#: ../system/integrations/elasticsearch.rst:131 +msgid "" +"If you need to change or reset your Elasticsearch user password, use the " +"\"Reset password\" button in the credentials table. Doing so creates a brand " +"new password for the account in question. This change is immediate, keep in " +"mind that this may affect third party tools connected to your instance." msgstr "" -#: ../system/objects/permissions.rst:67 -msgid "Sign-up screen for new customers" +#: ../system/integrations/exchange.rst:2 +msgid "Exchange" msgstr "" -#: ../system/objects/permissions.rst:68 -msgid "invite_customer" +#: ../system/integrations/exchange.rst:4 +msgid "" +"With Zammad's Exchange integration, you can easily use existing address " +"books without having to update more than one source." msgstr "" -#: ../system/objects/permissions.rst:71 +#: ../system/integrations/exchange.rst:7 msgid "" -"Customer invitation screen (from :doc:`First Steps ` area)" +"However, you should refrain from syncing all addresses, as the results may " +"not be what you expect (Exchange collects huge amounts of addresses). A " +"central address book of your company to sync makes more sense, as you can " +"ensure that Zammad gets only the data you need and want. Apart from this, it " +"is even not possible to sync the Global Address List (GAL) of your Exchange " +"system with Zammad." msgstr "" -#: ../system/objects/permissions.rst:72 -msgid "invite_agent" +#: ../system/integrations/exchange.rst:16 +msgid "" +"**Exchange and LDAP:** The exchange sync can be overruled by Zammad's LDAP " +"integration. If you have the same users in both sources, the LDAP version " +"will always be Zammad's pick." msgstr "" -#: ../system/objects/permissions.rst:74 +#: ../system/integrations/exchange.rst:19 msgid "" -"Agent invitation screen (from :doc:`First Steps ` area)" +"**One way sync:** the Exchange sync is one way. Exchange => Zammad. Changes " +"to your users inside of Zammad might be overwritten by the Exchange sync." msgstr "" -#: ../system/objects/permissions.rst:78 -msgid "Screen Options" +#: ../system/integrations/exchange.rst:24 +msgid "" +"To configure Exchange integration, simply go to the System > Integrations > " +"Exchange in the admin panel. Press \"change\" and follow the wizard for " +"adding the needed Exchange information to Zammad. On the last two steps " +"Zammad will ask you for the address book(s) and your desired attribute " +"mapping. By default, Zammad only maps email address, first- and lastname. " +"Technically, you can map any Exchange object to a Zammad user object (this " +"also works for custom objects!)." msgstr "" -#: ../system/objects/permissions.rst:80 +#: ../system/integrations/exchange.rst:35 msgid "" -"For the different screens you can select \"show\" and \"required\" options." +"If the SSL verification fails while connecting to Exchange, Zammad will ask " +"you to turn it off temporarily." msgstr "" -#: ../system/objects/permissions.rst:82 -msgid "**shown:** Show (check) or hide (uncheck) a field." +#: ../system/integrations/exchange.rst:38 +msgid "" +"Please be aware that **turning off SSL verification is a security risk**. It " +"should only be used temporarily or for testing purposes. If turned off, " +"there is no verification of the certificate, which means that every " +"presented certificate will be accepted." msgstr "" -#: ../system/objects/permissions.rst:83 +#: ../system/integrations/exchange.rst:43 msgid "" -"**required:** Set a field to mandatory (check). Forces users (via UI and " -"API) to populate the field." -msgstr "" - -#: ../system/objects/types.rst:7 -msgid "Example external data source" +"After pressing Continue, Zammad will check if the configuration is okay. You " +"can then enable Exchange and start your first sync. The sync will then run " +"hourly - if you need to change mappings or the address book(s), you can " +"change the configuration at any time." msgstr "" -#: ../system/objects/types.rst:2 -msgid "Attribute types" +#: ../system/integrations/exchange.rst:50 +msgid "" +"After the sync has finished, you can find the new Exchange contacts under " +"\"Users\". Zammad integrates them just as normal users." msgstr "" -#: ../system/objects/types.rst:4 +#: ../system/integrations/exchange.rst:55 msgid "" -"When adding a new object attribute, you can choose between the following " -"attribute types." +"In some cases you might see unique IDs as \"Login\" instead of the email " +"address. This is normal and doesn't affect the login or email mapping for " +"that entry." msgstr "" -#: ../system/objects/types.rst:14 +#: ../system/integrations/github.rst:4 msgid "" -"You cannot change the attribute format / type as soon as it is applied. If " -"you no longer need an object attribute, consider disabling it instead of " -"removing." +"Use GitHub integration to track GitHub issues directly within Zammad " +"tickets. Add issue hyperlinks and get a live summary of metadata like status " +"(open/closed), assignee, labels, and more." msgstr "" -#: ../system/objects/types.rst:18 -msgid "**What about the translation of my attributes?**" +#: ../system/integrations/github.rst:8 +msgid "Please note that our GitHub integration does not support pull requests." msgstr "" -#: ../system/objects/types.rst:20 -msgid "" -"For some attribute types you can decide if they should be translatable or " -"not. To be precise, it works only for the selectable fields because the " -"possible choices are known and limited. For the following attribute types, " -"you can set the translatable flag:" +#: ../system/integrations/github.rst:None +msgid "Integration page for GitHub" msgstr "" -#: ../system/objects/types.rst:25 -msgid "*Boolean field*" +#: ../system/integrations/github.rst:18 +msgid "" +"In your GitHub settings, create a new API token under **Developer settings > " +"Personal access tokens > Generate new token**. Leave the **Scopes** section " +"empty." msgstr "" -#: ../system/objects/types.rst:26 -msgid "*Single selection field*" +#: ../system/integrations/github.rst:0 ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to create a new API token" msgstr "" -#: ../system/objects/types.rst:27 -msgid "*Multiple selection field*" +#: ../system/integrations/github.rst:27 +msgid "Create a new API key with no scopes/privileges." msgstr "" -#: ../system/objects/types.rst:28 -msgid "*Single tree selection field*" +#: ../system/integrations/github.rst:29 +msgid "🔒 **Will this work for private repos?**" msgstr "" -#: ../system/objects/types.rst:29 -msgid "*Multiple tree selection field*" +#: ../system/integrations/github.rst:31 +msgid "" +"No. To link private repo issues, **use the** ``repo`` **scope instead**. " +"Bear in mind that the resulting token will have `lots of permissions that it " +"doesn't actually need `_, which presents a security risk if your token ever falls into " +"the wrong hands." msgstr "" -#: ../system/objects/types.rst:31 +#: ../system/integrations/github.rst:37 msgid "" -"For these types, you can find an additional field *Translate field contents*:" +"Unfortunately, because of how GitHub's OAuth token scopes are set up, this " +"is the only way to link issues on private repos." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Screenshot showing translatable attribute types" +#: ../system/integrations/github.rst:40 +msgid "Enter your new API token in Zammad and enable GitHub integration." msgstr "" -#: ../system/objects/types.rst:38 -msgid "Screenshot with example of translatable attribute type" +#: ../system/integrations/github.rst:0 +msgid "Screencast showing how to configure Zammad's GitHub integration" msgstr "" -#: ../system/objects/types.rst:45 -msgid "Boolean field" +#: ../system/integrations/github.rst:47 +msgid "" +"Use the default API endpoint (``https://api.github.com/graphql``) unless " +"you're using GitHub Enterprise Server." msgstr "" -#: ../system/objects/types.rst:41 +#: ../system/integrations/github.rst:50 msgid "" -"Provides a drop-down field with display values for ``true`` and ``false``. " -"Setting a default is mandatory." +"Once completed, a new GitHub issues tab will appear in the ticket pane. 🎉" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Boolean fields" +#: ../system/integrations/github.rst:59 ../system/integrations/gitlab.rst:52 +msgid "Token verification is taking a long time" msgstr "" -#: ../system/objects/types.rst:55 -msgid "Date field" +#: ../system/integrations/github.rst:56 ../system/integrations/gitlab.rst:49 +msgid "" +"Slight delays are normal (<2 min.), especially for systems under heavy load." msgstr "" -#: ../system/objects/types.rst:48 -msgid "Provides a date picker field and does not allow default values." +#: ../system/integrations/github.rst:58 +msgid "" +"Self-hosted administrators, please check your network settings to ensure " +"that your Zammad server can reach ``api.github.com``." msgstr "" -#: ../system/objects/types.rst:52 -msgid "Default time diff (hours)" +#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 +msgid "I reloaded the page and now the API token is gone" msgstr "" -#: ../system/objects/types.rst:51 +#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 msgid "" -"This setting helps the user by highlighting the day from now plus the " -"provided value. It *does not* pre-fill the field." -msgstr "" - -#: ../system/objects/types.rst:0 -msgid "Available settings for Date fields" +"This may indicate that Zammad is still verifying your API token. Try " +"reloading the page again in a couple minutes." msgstr "" -#: ../system/objects/types.rst:73 -msgid "Date & time field" +#: ../system/integrations/gitlab.rst:2 +msgid "GitLab" msgstr "" -#: ../system/objects/types.rst:58 -msgid "Provides a date and time picker – does not allow default values" +#: ../system/integrations/gitlab.rst:4 +msgid "" +"Use GitLab integration to track GitLab issues directly within Zammad " +"tickets. Add issue hyperlinks and get a live summary of metadata like status " +"(open/closed), assignee, labels, and more." msgstr "" -#: ../system/objects/types.rst:62 -msgid "Allow future" +#: ../system/integrations/gitlab.rst:8 +msgid "" +"Please note that our GitLab integration does not support merge requests." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Forbid dates and times in the future." +#: ../system/integrations/gitlab.rst:None +msgid "Integration page for GitLab" msgstr "" -#: ../system/objects/types.rst:66 -msgid "Allow past" +#: ../system/integrations/gitlab.rst:18 +msgid "" +"In your GitLab preferences, create a new API token under **Access Tokens**." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Forbid dates and times in the past." +#: ../system/integrations/gitlab.rst:20 +msgid "Under **Select scopes**, choose ``read_api`` only." msgstr "" -#: ../system/objects/types.rst:70 -msgid "Default time diff (minutes)" +#: ../system/integrations/gitlab.rst:27 +msgid "🔒 **If you wish to link issues on any private repos...**" msgstr "" -#: ../system/objects/types.rst:69 -msgid "" -"This setting helps the user by highlighting the day from now plus the " -"provided value. It does not pre-fill the field." +#: ../system/integrations/gitlab.rst:29 +msgid "Your API token must belong to an account with access to those repos." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Date & time fields" +#: ../system/integrations/gitlab.rst:31 +msgid "Enter your new API token in Zammad and enable GitLab integration." msgstr "" -#: ../system/objects/types.rst:86 -msgid "Integer field" +#: ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to configure Zammad's GitLab integration" msgstr "" -#: ../system/objects/types.rst:76 +#: ../system/integrations/gitlab.rst:40 msgid "" -"Provides an input field that allows integer usage only. You may define a " -"default value. You cannot enforce comma separation." +"Use the default API endpoint (``https://gitlab.com/api/graphql``) unless " +"you're a self-hosted GitLab user." msgstr "" -#: ../system/objects/types.rst:80 -msgid "Minimal" +#: ../system/integrations/gitlab.rst:43 +msgid "" +"Once completed, a new GitLab issues tab will appear in the ticket pane. 🎉" msgstr "" -#: ../system/objects/types.rst:80 -msgid "The minimal value the field accepts." +#: ../system/integrations/gitlab.rst:51 +msgid "" +"Self-hosted administrators, please check your network settings to ensure " +"that your Zammad server can reach ``gitlab.com``." msgstr "" -#: ../system/objects/types.rst:83 -msgid "Maximal" +#: ../system/integrations/i-doit.rst:2 +msgid "i-doit" msgstr "" -#: ../system/objects/types.rst:83 -msgid "The maximum value the field accepts." +#: ../system/integrations/i-doit.rst:4 +msgid "" +"`i-doit `_ is an open-source **configuration " +"management database** - in other words, a tool for keeping tabs on every " +"single piece of your physical and digital infrastructure, from network " +"equipment to virtual machines on down to the faceplates on your rack shelves " +"and more." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Integer fields" +#: ../system/integrations/i-doit.rst:10 +msgid "" +"What's that got to do with Zammad? Well, if you used tickets to track issues " +"with all that hardware, you might start wishing there was a way they could " +"talk to each other." msgstr "" -#: ../system/objects/types.rst:99 -msgid "Multiple selection field" +#: ../system/integrations/i-doit.rst:14 +msgid "Zammad gives you two:" msgstr "" -#: ../system/objects/types.rst:89 -msgid "" -"Provides a selection field that allows the selection of one or more out of " -"several. This field does allow setting a default value." +#: ../system/integrations/i-doit.rst:17 +msgid "1. Add i-doit Links to Zammad Tickets" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Multiple selection fields" +#: ../system/integrations/i-doit.rst:20 ../system/integrations/i-doit.rst:80 +msgid "What Users See" msgstr "" -#: ../system/objects/types.rst:112 -msgid "Single selection field" +#: ../system/integrations/i-doit.rst:26 +msgid "i-doit integration in Zammad's ticket pane" msgstr "" -#: ../system/objects/types.rst:102 +#: ../system/integrations/i-doit.rst:26 msgid "" -"Provides a drop-down field that allows selection of one value out of " -"several. This field does allow setting a default value." +"The i-doit integration will appear under a new 🖨 tab in the ticket pane." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Single selection fields" +#: ../system/integrations/i-doit.rst:28 +msgid "" +"i-doit integration puts a new tab in Zammad's ticket pane where you can add " +"links to existing i-doit devices for easy reference. (See our :user-docs:" +"`user documentation ` to learn " +"how it works in practice)." msgstr "" -#: ../system/objects/types.rst:142 -msgid "Textarea field" +#: ../system/integrations/i-doit.rst:36 ../system/integrations/i-doit.rst:93 +msgid "How to Set it Up" msgstr "" -#: ../system/objects/types.rst:115 +#: ../system/integrations/i-doit.rst:38 msgid "" -"Provides a text area input field (multiple lines) and thus allows e.g. new " -"lines. You can set a default field value." +"It requires i-doit's `API Add-on `_. Make sure to have it properly set up. Use the following setting:" msgstr "" -#: ../system/objects/types.rst:120 -msgid "" -"Please note that this field *does not* support text formatting or HTML " -"content (rich text)." +#: ../system/integrations/i-doit.rst:42 +msgid "Active: ``Yes``" msgstr "" -#: ../system/objects/types.rst:123 -msgid "**🥵 This field can consume a lot of visual space**" +#: ../system/integrations/i-doit.rst:43 +msgid "Enforce authentication by username and password: ``No``" msgstr "" -#: ../system/objects/types.rst:125 +#: ../system/integrations/i-doit.rst:45 msgid "" -"Depending on where you use this field type, it may use a lot of visual space " -"if you provide a lot of text. This may be an issue to work with." +"To set it up, enable the integration in the Zammad admin panel under " +"**System > Integrations > i-doit**:" msgstr "" -#: ../system/objects/types.rst:130 -msgid "Default" +#: ../system/integrations/i-doit.rst:None +msgid "i-doit settings within the integration pages" msgstr "" -#: ../system/objects/types.rst:129 -msgid "" -"The here provided text will be shown within the text area field or new data " -"sets." +#: ../system/integrations/i-doit.rst:53 +msgid "The root URL of your i-doit installation." msgstr "" -#: ../system/objects/types.rst:134 ../system/objects/types.rst:160 -msgid "Maxlength" +#: ../system/integrations/i-doit.rst:62 +msgid "API token" msgstr "" -#: ../system/objects/types.rst:0 ../system/objects/types.rst:160 -msgid "You can pick the maximum length of the field." +#: ../system/integrations/i-doit.rst:56 +msgid "" +"Found in the i-doit admin panel under **Interfaces / external data > JSON-" +"RPC API > Common Settings**." msgstr "" -#: ../system/objects/types.rst:0 -msgid "The default length of this object is ``500``." +#: ../system/integrations/i-doit.rst:0 +msgid "i-doit administration interface with API configuration" msgstr "" -#: ../system/objects/types.rst:139 -msgid "Rows" +#: ../system/integrations/i-doit.rst:67 +msgid "Client ID" msgstr "" -#: ../system/objects/types.rst:0 -msgid "" -"Change the number of rows to dislay so that you can use only the space you " -"really need." +#: ../system/integrations/i-doit.rst:65 +msgid "A unique name to identify Zammad within i-doit." msgstr "" -#: ../system/objects/types.rst:0 -msgid "The default number of rows is ``4``." +#: ../system/integrations/i-doit.rst:67 +msgid "(Zammad does not require you to enter a value here, but i-doit might!)" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Textarea fields" +#: ../system/integrations/i-doit.rst:70 +msgid "" +"Here you can decide if the certificate of your i-doit system has to be " +"verified or not. In case you are using custom certificates, please have a " +"look at :doc:`how to add them to Zammad `." msgstr "" -#: ../system/objects/types.rst:165 -msgid "Text field" +#: ../system/integrations/i-doit.rst:77 +msgid "2. List / Create Zammad Tickets in i-doit" msgstr "" -#: ../system/objects/types.rst:145 -msgid "Provides a text field (one line) and allows choosing a default value." +#: ../system/integrations/i-doit.rst:None +msgid "Zammad integration in i-doit's device view" msgstr "" -#: ../system/objects/types.rst:148 +#: ../system/integrations/i-doit.rst:86 msgid "" -"Defines the type of the input field. This allows e.g. your browser to ensure " -"that you provide the specific type." +"i-doit's ticket system integration gives you a way to see all the tickets " +"for a given device without ever leaving i-doit. (See our :user-docs:`user " +"documentation ` to learn how it " +"works in practice)." msgstr "" -#: ../system/objects/types.rst:152 -msgid "Currently available:" +#: ../system/integrations/i-doit.rst:95 +msgid "" +"Enable this integration in the i-doit admin panel under **Interfaces / " +"external data > Trouble Ticket System (TTS) > Configuration**:" msgstr "" -#: ../system/objects/types.rst:155 -msgid "Phone" +#: ../system/integrations/i-doit.rst:None +msgid "i-doit administration interface with TTS configuration" msgstr "" -#: ../system/objects/types.rst:156 -msgid "Text" +#: ../system/integrations/i-doit.rst:104 +msgid "TTS-Type" msgstr "" -#: ../system/objects/types.rst:157 -msgid "Url *(URL fields disable link-template availability)*" +#: ../system/integrations/i-doit.rst:104 +msgid "``Zammad``" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Text fields" +#: ../system/integrations/i-doit.rst:115 +msgid "Username / Password" msgstr "" -#: ../system/objects/types.rst:174 -msgid "Single tree selection field" +#: ../system/integrations/i-doit.rst:107 +msgid "Login credentials for a Zammad agent." msgstr "" -#: ../system/objects/types.rst:168 +#: ../system/integrations/i-doit.rst:109 msgid "" -"Provides a select-like field with up to 6 layers of options. Does not allow " -"setting a default value." +"This agent must have **read permission** for all :doc:`groups ` that plan on using the i-doit integration." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Tree Select fields" +#: ../system/integrations/i-doit.rst:113 +msgid "" +"You may even wish to create a dedicated agent account just for this " +"integration (otherwise, if the agent ever changes her password, you will " +"have to remember to update it here)." msgstr "" -#: ../system/objects/types.rst:183 -msgid "Multiple tree selection field" +#: ../system/integrations/i-doit.rst:117 +msgid "URL incl. protocol" msgstr "" -#: ../system/objects/types.rst:177 -msgid "" -"Provides a select-like field with up to 6 layers of options allowing the " -"selection of multiple values. Does not allow setting a default value." +#: ../system/integrations/i-doit.rst:118 +msgid "``https://your.zammad.domain``" msgstr "" -#: ../system/objects/types.rst:302 -msgid "External Data Source field" +#: ../system/integrations/index.rst:2 +msgid "Integrations" msgstr "" -#: ../system/objects/types.rst:186 +#: ../system/integrations/index.rst:4 msgid "" -"Provides a searchable field which fetches data from an external system. This " -"can be useful if you have data outside of Zammad and don't want to maintain " -"both data sources." +"Zammad offers numerous integrations that add rich features to your instance." msgstr "" -#: ../system/objects/types.rst:190 -msgid "The feature works as follows:" +#: ../system/integrations/index.rst:6 +msgid "We're still working on this part of our documentation, stay tight!" msgstr "" -#: ../system/objects/types.rst:192 -msgid "" -"Zammad sends a query with a search string (free text from agent or based on " -"a variable) in a pre-defined format (\"Search URL\") to an external system." +#: ../system/integrations/index.rst:10 +msgid "Integrations for Phone Systems" msgstr "" -#: ../system/objects/types.rst:195 +#: ../system/integrations/index.rst:14 msgid "" -"This external system searches for matches and provides a response as a JSON " -"structure to Zammad." +"Your VoIP provider or telephony system is not listed? Possibly your provider " +"supports Zammad by using the generic CTI - if you're unsure ask your " +"provider." msgstr "" -#: ../system/objects/types.rst:197 +#: ../system/integrations/index.rst:18 msgid "" -"Zammad just looks for the defined list and value keys, reads the content and " -"displays the value to the user. There is no search on Zammad side." +"Provider does not support Zammad? Consider creating a `feature request in " +"the Zammad Community `_." msgstr "" -#: ../system/objects/types.rst:201 -msgid "" -"The usage of a PostgreSQL database for Zammad is required. In any other " -"case, Zammad will hide the external data source type and you are not able to " -"use it. If you want to use this feature, consider to :docs:`migrate your " -"database `." +#: ../system/integrations/index.rst:31 +msgid "Integrations for Authentication and Customers" msgstr "" -#: ../system/objects/types.rst:205 -msgid "Currently, only ``GET`` is supported as request method." +#: ../system/integrations/index.rst:44 +msgid "Integrations for Monitoring Systems" msgstr "" -#: ../system/objects/types.rst:206 -msgid "" -"The data structure must be in JSON format and provide the objects in an " -"array." +#: ../system/integrations/index.rst:46 +msgid "This section currently misses the following integrations:" msgstr "" -#: ../system/objects/types.rst:208 -msgid "" -"The endpoint for the external data source has to support search. On Zammad " -"side, there is no search/logic implemented; however, you can define the " -"output key and value based on the result(s) from the response (which " -"provides already filtered content based on the search)." +#: ../system/integrations/index.rst:48 +msgid "Icinga" msgstr "" -#: ../system/objects/types.rst:212 -msgid "" -"If you receive more results as expected, your external data source search " -"may not work properly or the structure of the URL is not correct. You should " -"get in touch with a responsible person from the external system." +#: ../system/integrations/index.rst:49 +msgid "Monit" msgstr "" -#: ../system/objects/types.rst:217 -msgid "" -"Please have a look :doc:`at our example `, where you can find a possible configuration for a public " -"dummy endpoint." +#: ../system/integrations/index.rst:50 +msgid "Nagios" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for external data source fields" +#: ../system/integrations/index.rst:60 +msgid "Integrations for Issue Trackers" msgstr "" -#: ../system/objects/types.rst:242 -msgid "Search URL" +#: ../system/integrations/index.rst:70 +msgid "Other Integrations" msgstr "" -#: ../system/objects/types.rst:227 +#: ../system/integrations/index.rst:72 msgid "" -"Set your endpoint where Zammad fetches the data. Please make sure to include " -"a valid search :doc:`variable <../variables>` as an URL parameter. Example " -"for a free text search at user input: ``#{search.term}``" +"This section will hold any other integration that can't be grouped up (yet)." msgstr "" -#: ../system/objects/types.rst:232 -msgid "" -"If in doubt, ask the responsible person for the external data source how " -"they expect the strucuture of the URL." +#: ../system/integrations/ldap/index.rst:2 +msgid "LDAP / Active Directory" msgstr "" -#: ../system/objects/types.rst:236 +#: ../system/integrations/ldap/index.rst:4 msgid "" -"Depending on your search variable, the preview might work or not. The reason " -"is that the context might not be available and it is no bug." +"Zammad comes with a powerful LDAP integration that allows you to have a " +"single source of truth. By this you reduce the number of login credentials " +"your user has to remember." msgstr "" -#: ../system/objects/types.rst:239 +#: ../system/integrations/ldap/index.rst:10 msgid "" -"Please also make sure to use a variable which is available in your object " -"context. For example you won't be able to search for a ticket in a user " -"object context." -msgstr "" - -#: ../system/objects/types.rst:252 -msgid "SSL Verification" +"The LDAP source is also a perfect candidate for Zammad's :docs:`Kerberos " +"Single Sign-On ` but also works as addition " +"to other :doc:`/settings/security/third-party`." msgstr "" -#: ../system/objects/types.rst:245 -msgid "Here you can switch the SSL verification to no." +#: ../system/integrations/ldap/index.rst:None +msgid "Zammands LDAP management page" msgstr "" -#: ../system/objects/types.rst:249 -msgid "" -"If your external data source system is using self signed certificates, " -"please have a look :doc:`here ` for " -"further information about how to handle them in Zammad, so you can keep the " -"SSL verification activated." +#: ../system/integrations/ldap/index.rst:25 +msgid "📝 :doc:`manage`" msgstr "" -#: ../system/objects/types.rst:258 -msgid "HTTP Authentication" +#: ../system/integrations/ldap/index.rst:25 +msgid "Add, modify, remove or re-arrange your LDAP-Sources as needed." msgstr "" -#: ../system/objects/types.rst:255 -msgid "" -"If your external data source requires an authentication, you can set it " -"here. You can leave it empty or choose between *Basic Authentication* or " -"*Authentication Token* (selecting one of the two methods leads to additional " -"fields where you can enter your credentials/token)." +#: ../system/integrations/ldap/index.rst:30 +msgid "Before you continue, please note the following limitations." msgstr "" -#: ../system/objects/types.rst:265 -msgid "Search result list key" +#: ../system/integrations/ldap/index.rst:32 +msgid "Mapping / Synchronizing organizations is not possible" msgstr "" -#: ../system/objects/types.rst:261 +#: ../system/integrations/ldap/index.rst:36 msgid "" -"Defines the level in the JSON structure which provides the list with search " -"results. You can leave it empty, if the data is already provided as an " -"array. If you have to go deeper in the structure, you can provide a path " -"with ``.`` as separators, e.g. ``key.subkey.sub-sub-key``." +"You may want to consider using domain based assignments to overcome this " +"issue. Learn more on :doc:`/manage/organizations/index`." msgstr "" -#: ../system/objects/types.rst:271 -msgid "Search result value key" +#: ../system/integrations/ldap/index.rst:39 +msgid "" +"Zammad's LDAP sync is one way. Editing user settings or permissions may be " +"overwritten upon the next sync depending on your configuration." msgstr "" -#: ../system/objects/types.rst:268 -msgid "" -"Defines the attribute in the structure in which your external data source " -"provides the *value* for your data. An example would be a product *number*. " -"If you have to go deeper in the structure, you can provide a path with ``.`` " -"as separators, e.g. ``key.subkey.sub-sub-key``." +#: ../system/integrations/ldap/index.rst:41 +msgid "Nested groups are not supported." msgstr "" -#: ../system/objects/types.rst:277 -msgid "Search result label key" +#: ../system/integrations/ldap/index.rst:42 +msgid "Synchronizing user avatars from LDAP is not supported." msgstr "" -#: ../system/objects/types.rst:274 -msgid "" -"Defines the attribute in the structure in which your external data source " -"provides the *label* for your data. An example would be a product *name*. If " -"you have to go deeper in the structure, you can provide a path with ``.`` as " -"separators, e.g. ``key.subkey.sub-sub-key``." +#: ../system/integrations/ldap/index.rst:43 +msgid "Unlike user filters, group filters cannot be changed." msgstr "" -#: ../system/objects/types.rst:280 +#: ../system/integrations/ldap/index.rst:44 msgid "" -"In the preview area, you can find the following items (depending on your " -"configuration above):" +"When a user originates from an LDAP server, Zammad will try to verify the " +"login credentials against LDAP first - if this fails Zammad will check its " +"local database." msgstr "" -#: ../system/objects/types.rst:283 +#: ../system/integrations/ldap/index.rst:50 msgid "" -"**Error/hint message** (only if configuration is not complete): Zammad tells " -"you, if there is a problem and what you should change in your configuration." +"Users can have local passwords even if they're LDAP users! You can learn " +"more about user accounts in general on :doc:`/manage/users/index`." msgstr "" -#: ../system/objects/types.rst:286 +#: ../system/integrations/ldap/index.rst:54 msgid "" -"**Search field**: search for an existing attribute in the data source to get " -"a preview. This is required for the fields below to show up." +"When several LDAP sources contain the same user (meaning the same email " +"address), the user in question will be updated with every source configured. " +"*The last LDAP source will win.*" msgstr "" -#: ../system/objects/types.rst:288 +#: ../system/integrations/ldap/index.rst:58 msgid "" -"**Search result response** (only if configuration is not complete): here you " -"can find a syntax highlighted JSON preview of the response, based on the " -"search term you entered." +"This is subject to change with `Issue 4109 `_ in the future." msgstr "" -#: ../system/objects/types.rst:291 +#: ../system/integrations/ldap/index.rst:60 msgid "" -"**Search result list** (only if *search result list key* is properly set): " -"output of the structure under the configured *search result list key*." +"Synchronization statistics currently affect *all* configured LDAP sources. " +"This also applies for newly added or updated sources." msgstr "" -#: ../system/objects/types.rst:294 +#: ../system/integrations/ldap/index.rst:63 msgid "" -"**Preview table** (when fully configured): Zammad shows you a table which " -"includes the found items based on the search string (value, label and " -"optional link). You can use this preview if you don't have the complete data " -"structure of the external system in mind." +"This is subject to change with `Issue 4108 `_ in the future." msgstr "" -#: ../system/objects/types.rst:299 +#: ../system/integrations/ldap/index.rst:65 msgid "" -"An example of a configured external data source field from agent perspective:" +"Zammad currently has limited fallback server support. You can workaround " +"this by providing several sources - however, ensure to have the exact same " +"configuration on your fallback." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Screencast showing the search for a product in a ticket" +#: ../system/integrations/ldap/index.rst:69 +msgid "" +"This is subject to improve with `Issue 4107 `_ in the future." msgstr "" -#: ../system/objects/types.rst:307 -msgid "URL fields (Link-Template)" +#: ../system/integrations/ldap/index.rst:76 +msgid "" +"This section holds all requests Zammad handled for all LDAP sources. These " +"entries can either contain synchronization information or logins " +"(authentication attempts via Zammad's login interface)." msgstr "" -#: ../system/objects/types.rst:311 +#: ../system/integrations/ldap/index.rst:80 msgid "" -"This function is restricted to Text, Select and External data source types " -"only." +"By clicking on any request, Zammad will provide even more information. The " +"provided information can be useful when something does not work as expected." msgstr "" -#: ../system/objects/types.rst:314 +#: ../system/integrations/ldap/index.rst:85 msgid "" -"Link-Templates are an amazing way to dynamically generate URLs. They allow " -"you to integrate other systems better without having to manually copy data " -"from Zammad if possible." +"Especially a LDAP synchronization can cause many log entries. The web " +"interface will always limit the number of shown entries to the last 50 " +"entries." msgstr "" -#: ../system/objects/types.rst:320 +#: ../system/integrations/ldap/index.rst:None msgid "" -"Another great way of communicating with another system may be Zammad's :doc:" -"`Webhooks `." +"Screencast showing LDAP integration log entries and a detail view on\n" +"an entry." msgstr "" -#: ../system/objects/types.rst:323 -msgid "" -"After filling a link-template enabled field, an URL icon will appear on its " -"right. Clicking on the icon opens a new tab." +#: ../system/integrations/ldap/manage.rst:2 +msgid "Manage LDAP-Sources" msgstr "" -#: ../system/objects/types.rst:328 +#: ../system/integrations/ldap/manage.rst:6 msgid "" -"Even though Zammad displays the link template within object edit and create " -"screens, the function is optional. It's only active if you populate the " -"field." +"Please keep in mind all current limitations for the LDAP synchronization. " +"This will help to understand scopes of the following operations better." msgstr "" -#: ../system/objects/types.rst:333 -msgid "" -"What's the difference between URL and text fields with link template...?!" +#: ../system/integrations/ldap/manage.rst:65 +msgid "Add new source" msgstr "" -#: ../system/objects/types.rst:335 +#: ../system/integrations/ldap/manage.rst:10 msgid "" -"Both fields have different use cases. Use ``text`` type text fields when " -"ever you have a *static* url that requires dynamic parameters. If you " -"require a drag & drop like field that you can put in any URL, use ``URL`` " -"type text fields." +"Using the *New Source* button allows you to add new LDAP sources to your " +"installation. You're not limited in the number of sources, however, keep in " +"mind that many sources will also take more time to synchronize." msgstr "" -#: ../system/objects/types.rst:340 +#: ../system/integrations/ldap/manage.rst:14 msgid "" -"The difference is easier to spot when comparing the fields directly, below " -"screencast shows the result - the dynamic approach uses existing values in " -"the moment of updating to built the URL - e.g. ``https://google.com/search?" -"q=cookies`` - while the URL approach uses the actual URL of the field - e.g. " -"``https://zammad.com``." +"You can choose between different encryption types, namely *SSL* and " +"*STARTTLS* or none of them (\"*No SSL*\"). If you choose *SSL* or " +"*STARTTLS*, Zammad will display an additional *SSL verification* option that " +"allows you to disable the verification, e.g. for self-signed SSL " +"certificates. You can also tell Zammad to use a different port by appending " +"``:`` to your hostname/IP." msgstr "" -#: ../system/objects/types.rst:None +#: ../system/integrations/ldap/manage.rst:0 msgid "" -"Screencast showing the differents in between URL and text type fields with " -"actual values" +"Screenshot of configuring a new LDAP source with SSL encryption and SSL " +"verification" msgstr "" -#: ../system/objects/types.rst:352 -msgid "How does this work...?!" +#: ../system/integrations/ldap/manage.rst:26 +msgid "" +"New Source with SSL transport security enabled and certificate verification" msgstr "" -#: ../system/objects/types.rst:354 +#: ../system/integrations/ldap/manage.rst:30 msgid "" -"As an example, let's say you have an attribute called ``amazing_attribute`` " -"and you want to open a google search directly with the input from that field." +"Using an user filter can be a good idea if you only require a small subset " +"of your LDAP users in Zammad." msgstr "" -#: ../system/objects/types.rst:357 -msgid "" -"Providing the link-template field below allows you to do so: ``https://www." -"google.com/search?q=#{ticket.amazing_attribute}``" +#: ../system/integrations/ldap/manage.rst:42 +msgid "This especially affects inactive users" msgstr "" -#: ../system/objects/types.rst:362 +#: ../system/integrations/ldap/manage.rst:34 msgid "" -"You can use any :doc:`Zammad variable ` as long as it's " -"available in the moment you need it." +"As every LDAP behaves differently on which attributes and how they are set, " +"Zammad doesn't care about any flags." msgstr "" -#: ../system/objects/types.rst:365 +#: ../system/integrations/ldap/manage.rst:37 msgid "" -"As a result, you are redirected to Google with a search for the value of the " -"attribute, if you click on the button in the ticket (as you can see in the " -"screencast above)." +"Users that no longer are returned by your LDAP source will automatically be " +"set to inactive. Zammad assumes that the user was deactivated." msgstr "" -#: ../system/packages.rst:2 -msgid "Packages" +#: ../system/integrations/ldap/manage.rst:41 +msgid "" +"Users will never be removed automatically! If you want to remove obsolete " +"users, use :doc:`/system/data-privacy`." msgstr "" -#: ../system/packages.rst:4 -msgid "That's the package management-area." +#: ../system/integrations/ldap/manage.rst:46 +msgid "Active Directory admins" msgstr "" -#: ../system/packages.rst:6 -msgid "Individual add-ons for Zammad can be installed and managed here." +#: ../system/integrations/ldap/manage.rst:45 +msgid "" +"Active Directories are quite specific on how to filter for active users only " +"- please see the `Microsoft documentation `_ for more " +"information." msgstr "" -#: ../system/sessions.rst:2 -msgid "Sessions" +#: ../system/integrations/ldap/manage.rst:51 +msgid "" +"*Do not* manually write pathes of either LDAP attributes or groups. If " +"Zammad does not display them, it either cannot find them or you have a lot " +"of users that don't have the attributes populated." msgstr "" -#: ../system/sessions.rst:4 +#: ../system/integrations/ldap/manage.rst:55 msgid "" -"Sessions management allows reviewing currently known user sessions and " -"allows to end these. The session timeout is affected by :ref:" -"`security_session_timeout` configurations from security settings." +"Zammad will always only return attributes that are filled - this reduces the " +"returned list of attributes greatly." msgstr "" -#: ../system/sessions.rst:None -msgid "Screenshot showing Zammad's session management" +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing how to add a new LDAP source" msgstr "" -#: ../system/sessions.rst:13 -msgid "Zammad will provide the following information:" +#: ../system/integrations/ldap/manage.rst:63 +msgid "" +"If your LDAP system doesn't allow anonymous bind, Zammad detects it and " +"provides you an editable \"Base DN\" *text* field instead of a prefilled " +"*select* field." msgstr "" -#: ../system/sessions.rst:16 -msgid "" -"The user account this session entry belongs to. It can be normal if a user " -"has several sessions in the list. This can be due to changed browser " -"information or if you use e.g. single sign on methods where the user does " -"not use the log off button." +#: ../system/integrations/ldap/manage.rst:81 +msgid "Review or edit existing source" msgstr "" -#: ../system/sessions.rst:22 -msgid "Browser" +#: ../system/integrations/ldap/manage.rst:68 +msgid "" +"Clicking on a LDAP source will provide a configuration and mapping overview." msgstr "" -#: ../system/sessions.rst:22 -msgid "The browser agent communicated to Zammad." +#: ../system/integrations/ldap/manage.rst:70 +msgid "" +"If needed you can then use the *Change* button to update either the name, " +"active state or the whole configuration. If you're changing the whole " +"configuration, the dialogue will be identical to the source creation." msgstr "" -#: ../system/sessions.rst:40 -msgid "Location" +#: ../system/integrations/ldap/manage.rst:76 +msgid "" +"Did your LDAP server change? Different LDAP servers have different " +"structures and default attributes. This causes the LDAP synchronization to " +"likely fail. Consider removing the affected source and re-add it." msgstr "" -#: ../system/sessions.rst:25 -msgid "" -"The anticipated location based on the users IP address. Depending on the IP " -"address the result shown may differ. This option depends on :doc:`/settings/" -"system/services`." +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing the update of the source name." msgstr "" -#: ../system/sessions.rst:29 -msgid "The following information can be shown:" +#: ../system/integrations/ldap/manage.rst:89 +msgid "Re-arrange LDAP source's order" msgstr "" -#: ../system/sessions.rst:33 -msgid "IP address" +#: ../system/integrations/ldap/manage.rst:84 +msgid "" +"You can change the synchronization order for each source at any time. Zammad " +"will synchronize the sources from top to bottom." msgstr "" -#: ../system/sessions.rst:32 +#: ../system/integrations/ldap/manage.rst:0 msgid "" -"Either if you set *Geo IP services* to inactive or you're using internal IP " -"address which do not provide location information." +"Screencasting showing how to change the source order by using\n" +"drag and drop." msgstr "" -#: ../system/sessions.rst:40 -msgid "Country (or Country + City)" +#: ../system/integrations/ldap/manage.rst:101 +msgid "Remove a source" msgstr "" -#: ../system/sessions.rst:36 +#: ../system/integrations/ldap/manage.rst:92 msgid "" -"If *Geo IP services* is enabled only. Depends on how detailed the available " -"IP address information are." +"If you no longer need the a LDAP source or simply want to start over, you " +"can remove them at any time. This will not remove synchronized users, data " +"synchronized or permissions." msgstr "" -#: ../system/sessions.rst:39 +#: ../system/integrations/ldap/manage.rst:98 msgid "" -"Be aware that results can be inaccurate - this technically is not an error." +"Not sure if you'd need the source later on? Set the source to inactive " +"instead of removing it - see *Review or edit existing source* for more." msgstr "" -#: ../system/sessions.rst:43 -msgid "Age" +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing how to remove LDAP sources." msgstr "" -#: ../system/sessions.rst:43 -msgid "Provides the time when the session initially has been created." +#: ../system/integrations/pgp/index.rst:2 +msgid "PGP" msgstr "" -#: ../system/sessions.rst:50 -msgid "Update" +#: ../system/integrations/pgp/index.rst:7 +msgid "" +"Pretty Good Privacy (PGP) is another method for secure email communication. " +"With PGP, you can exchange **signed** and **encrypted** messages with others." msgstr "" -#: ../system/sessions.rst:46 -msgid "" -"Provides the time the user used this session to open Zammad. This timestamp " -"is only updated if the user e.g. reloads, not during normal work on tickets." +#: ../system/integrations/pgp/index.rst:13 +#: ../system/integrations/smime/index.rst:17 +msgid "Signing" msgstr "" -#: ../system/sessions.rst:50 -msgid "This timestamp is being used for the session timeout." +#: ../system/integrations/pgp/index.rst:11 +msgid "is a proof that a message hasn't been manipulated on its way." msgstr "" -#: ../system/sessions.rst:53 +#: ../system/integrations/pgp/index.rst:13 msgid "" -"Use the delete button to remove a single session on behalf of your user." +"In other words, it guarantees message **integrity** and **authenticity**." msgstr "" -#: ../system/subscription/billing.rst:2 -msgid "Billing" +#: ../system/integrations/pgp/index.rst:19 +#: ../system/integrations/smime/index.rst:22 +msgid "Encryption" msgstr "" -#: ../system/subscription/billing.rst:4 +#: ../system/integrations/pgp/index.rst:16 +#: ../system/integrations/smime/index.rst:20 msgid "" -"Within the billing tab you can control all billing relevant information like " -"invoices, billing address and the option to cancel your subscription." -msgstr "" - -#: ../system/subscription/billing.rst:33 -msgid "Billing information" +"scrambles a message so that it can only be unscrambled by the intended " +"recipient." msgstr "" -#: ../system/subscription/billing.rst:8 +#: ../system/integrations/pgp/index.rst:19 msgid "" -"All adjusted billing information below only affect future invoices. If your " -"invoice was issued wrong, please contact `our sales team `_." +"In other words, it guarantees message **privacy** and **data security**." msgstr "" -#: ../system/subscription/billing.rst:14 -msgid "Billing address" +#: ../system/integrations/pgp/index.rst:25 +msgid "Screenshot of ticket creation with encrypt and sign buttons" msgstr "" -#: ../system/subscription/billing.rst:13 +#: ../system/integrations/pgp/index.rst:25 msgid "" -"Provide your company address here, make sure to include the companies name " -"in case required. This address will be referenced on your invoice." +"Once PGP has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " +"appear in the ticket composer." msgstr "" -#: ../system/subscription/billing.rst:18 -msgid "VAT ID" +#: ../system/integrations/pgp/index.rst:28 +msgid "**Sign button not visible?**" msgstr "" -#: ../system/subscription/billing.rst:17 +#: ../system/integrations/pgp/index.rst:30 msgid "" -"Provide your VAT ID here. If applicable your invoice will not contain German " -"VAT. Please make sure to pay the VAT in your country as required." +"Please note that the signing of emails is based on the outgoing email " +"account. That means you have to choose a group with a sender email account, " +"which has a private key assigned." msgstr "" -#: ../system/subscription/billing.rst:27 -msgid "Billing Email Address" +#: ../system/integrations/pgp/index.rst:35 +msgid "Handling of Keys" msgstr "" -#: ../system/subscription/billing.rst:21 +#: ../system/integrations/pgp/index.rst:36 msgid "" -"Usually the instance owner (the person that registered the instance) will " -"receive all emails including the invoices. In case you have your own billing " -"department, you can provide their email address here." +"To use the PGP function, you have to enable the integration (PGP) by " +"switching the toggle to *enabled*." msgstr "" -#: ../system/subscription/billing.rst:25 +#: ../system/integrations/pgp/index.rst:39 msgid "" -"All billing relevant information will then be sent to this email address." +"You can add keys by clicking the *add key* button. The keys can be imported " +"from a file or you can paste the content of the key in the text box." msgstr "" -#: ../system/subscription/billing.rst:27 -msgid "Invoices are sent as attachment (PDF) to this email address." +#: ../system/integrations/pgp/index.rst:42 +msgid "**Which keys do I have to import?**" msgstr "" -#: ../system/subscription/billing.rst:29 +#: ../system/integrations/pgp/index.rst:44 msgid "" -"Don't forget to press the *Submit* button after you changed above settings." +"For **signing** *outgoing* emails, you have to import the private key of " +"your Zammad email account." msgstr "" -#: ../system/subscription/billing.rst:0 +#: ../system/integrations/pgp/index.rst:47 msgid "" -"Screenshot showing options for billing information within the\n" -"subscription menu" -msgstr "" - -#: ../system/subscription/billing.rst:70 -msgid "Payment history" +"For **encrypting** *outgoing* emails, you have to import the public key of " +"the customer's email account." msgstr "" -#: ../system/subscription/billing.rst:36 +#: ../system/integrations/pgp/index.rst:50 msgid "" -"The payment history will display a history of all paid invoices. At this " -"point you can also download these in case you need them again." +"For **verifying the signature** of signed *incoming* emails, you have to " +"import the public key of the customer." msgstr "" -#: ../system/subscription/billing.rst:41 +#: ../system/integrations/pgp/index.rst:53 msgid "" -"You will only find *paid* invoices here. Invoices that are to be billed are " -"not available before the payment is completed." +"For **decrypting** of encrypted *incoming* emails, you have to import the " +"private key of your Zammad email account." msgstr "" -#: ../system/subscription/billing.rst:46 -msgid "Date" +#: ../system/integrations/pgp/index.rst:57 +msgid "Import Keys From a File" msgstr "" -#: ../system/subscription/billing.rst:46 -msgid "Date of the invoice creation." +#: ../system/integrations/pgp/index.rst:58 +msgid "You can import keys from a file in the section **Upload key**:" msgstr "" -#: ../system/subscription/billing.rst:49 -msgid "Amount" +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of adding a key via file" msgstr "" -#: ../system/subscription/billing.rst:49 -msgid "Invoice total including VAT if applicable." +#: ../system/integrations/pgp/index.rst:64 +msgid "" +"**Supported file formats:** ASCII-armor as well as binary GPG format " +"(basically any GPG supported key format) is supported here." msgstr "" -#: ../system/subscription/billing.rst:52 -msgid "" -"Contains contract period (monthly or yearly) and hosted plan for the " -"subscription period in question." +#: ../system/integrations/pgp/index.rst:68 +msgid "Import Keys by Pasting the Content" msgstr "" -#: ../system/subscription/billing.rst:63 -msgid "Payment method / Service period" +#: ../system/integrations/pgp/index.rst:69 +msgid "You can also paste the key's content in the section **paste key**:" msgstr "" -#: ../system/subscription/billing.rst:56 -msgid "" -"Used bank account or credit card as well as the subscription period the " -"invoice is about." +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of adding a key via pasting" msgstr "" -#: ../system/subscription/billing.rst:61 +#: ../system/integrations/pgp/index.rst:75 msgid "" -"It might happen that the invoice date and subscription period differ. This " -"is nothing to worry about, the subscription periods will be accounted later " -"on." +"**Supported format:** Please note that only ASCII-armor is supported here." msgstr "" -#: ../system/subscription/billing.rst:67 -msgid "Receipt" +#: ../system/integrations/pgp/index.rst:78 +msgid "Deleting Keys" msgstr "" -#: ../system/subscription/billing.rst:66 +#: ../system/integrations/pgp/index.rst:79 msgid "" -"Use the arrow to download the invoice in question. You can download all " -"available invoices any time you need to here!" +"If you want to delete a specific key, you can do it by clicking on the menu " +"in the *actions* column and select **delete**:" msgstr "" -#: ../system/subscription/billing.rst:0 -msgid "Screenshot showing payment history of a hosted instance" +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of deleting a key" msgstr "" -#: ../system/subscription/billing.rst:94 -msgid "Do you want to cancel your subscription?" +#: ../system/integrations/pgp/index.rst:88 +msgid "Downloading Keys" msgstr "" -#: ../system/subscription/billing.rst:73 +#: ../system/integrations/pgp/index.rst:89 msgid "" -"In case you no longer want to use Zammad's SaaS, you can cancel your " -"subscription by using the red *Yes, please cancel my subscription* button." +"If you want to download your keys, you can do this as well via corresponding " +"action buttons. Depending on the key, you can choose wether you want to " +"download the private or the public key." msgstr "" -#: ../system/subscription/billing.rst:76 -msgid "" -"Your subscription will end the day after your trial or billing period ends." +#: ../system/integrations/pgp/index.rst:95 +#: ../system/integrations/smime/manage-certificates.rst:76 +msgid "Default Behavior" msgstr "" -#: ../system/subscription/billing.rst:80 +#: ../system/integrations/pgp/index.rst:96 msgid "" -"We will remind you about your cancelled subscription several times up front. " -"After the subscription ended all instance data will be removed. A restore " -"*is not* possible after that point!" +"Here you can adjust on per group basis, if *sign* and *encryption* is on or " +"off by default. Please be aware, that agents can always override the setting " +"for each individual article." msgstr "" -#: ../system/subscription/billing.rst:0 -msgid "Screencast showing how to cancel a subscription" +#: ../system/integrations/pgp/index.rst:None +msgid "Adjusting default behavior on per group basis" msgstr "" -#: ../system/subscription/billing.rst:87 -msgid "**😖 Cancelled by accident?**" +#: ../system/integrations/pgp/index.rst:107 +msgid "" +"Here you can see the last actions regarding signing and encryption and if " +"they were successful." msgstr "" -#: ../system/subscription/billing.rst:89 -msgid "" -"You can always undo the cancellation via the *Yes, undo the cancellation of " -"my subscription* button up to the last subscription day!" +#: ../system/integrations/pgp/index.rst:117 +msgid "**Sign button is not visible, but keys are imported.**" +msgstr "" + +#: ../system/integrations/pgp/index.rst:115 +msgid "Did you choose a group in the ticket?" msgstr "" -#: ../system/subscription/billing.rst:0 +#: ../system/integrations/pgp/index.rst:116 msgid "" -"Screenshot showing a red button to cancel the subscription\n" -"cancellation" +"Did you import a private key for the email adress, which is used for " +"outgoing emails in the group?" msgstr "" -#: ../system/subscription/index.rst:2 -msgid "Subscription (SaaS)" +#: ../system/integrations/pgp/index.rst:122 +msgid "**How to obtain keys?**" msgstr "" -#: ../system/subscription/index.rst:4 +#: ../system/integrations/pgp/index.rst:120 msgid "" -"The subscription settings page allows you to configure your instances " -"package and number of agents required." +"You can create them yourself! There are some good tutorials on the web on " +"how to create them. Providing keys to Zammad is a prerequisite to use the " +"PGP feature." msgstr "" -#: ../system/subscription/index.rst:9 -msgid "" -"This setting section is only available for Hosted setups. If you're looking " -"for on premise support contracts, please see the `Zammad pricing page " -"`_." +#: ../system/integrations/pgp/index.rst:127 +msgid "**It says a passphrase is needed, but I haven't got one.**" msgstr "" -#: ../system/subscription/index.rst:20 +#: ../system/integrations/pgp/index.rst:125 msgid "" -"The subscription section currently consists of two tabs: Plan & Billing. For " -"your overview we've divided those two tabs into independent sub pages:" +"If the key is secured with a passphrase, you have to provide it for the " +"import in Zammad. It is possible that keys may have an empty passphrase. " +"However, this is *not* recommended." msgstr "" -#: ../system/subscription/index.rst:25 -msgid ":doc:`💰 Subscription plan `" +#: ../system/integrations/pgp/index.rst:132 +msgid "**How do my customers get my new key?**" msgstr "" -#: ../system/subscription/index.rst:24 +#: ../system/integrations/pgp/index.rst:130 msgid "" -"Everything affecting your instance subscription functions like number of " -"agents, package and payment method." +"You have to provide your **public** key in advance. Your customer also has " +"to configure PGP in their email workflow and import your public key. The " +"other way round, you have to get the public key of your customer and have to " +"import it to Zammad." +msgstr "" + +#: ../system/integrations/slack.rst:2 +msgid "Slack" msgstr "" -#: ../system/subscription/index.rst:28 -msgid ":doc:`🧾 Subscription billing `" +#: ../system/integrations/slack.rst:4 +msgid "**⚠️ Deprecation warning ⚠️**" msgstr "" -#: ../system/subscription/index.rst:28 +#: ../system/integrations/slack.rst:6 msgid "" -"Everything regarding billing address, invoices and account cancellation." +"Zammad 7 will no longer support this dedicated Slack integration. It is " +"recommended to switch to :doc:`pre-defined webhooks ` instead. Existing Slack integrations should " +"be migrated manually before this feature is dropped." msgstr "" -#: ../system/subscription/index.rst:33 -msgid "FAQ" +#: ../system/integrations/slack.rst:14 +msgid "" +"In order to use this feature, please add a new Slack app to your Workspace. " +"The App you need is called ``Incoming WebHooks`` ." msgstr "" -#: ../system/subscription/index.rst:37 -msgid "I set up a trial account but am missing functions to test" +#: ../system/integrations/slack.rst:18 +msgid "Why Do I Need This Feature?" msgstr "" -#: ../system/subscription/index.rst:36 +#: ../system/integrations/slack.rst:20 msgid "" -"The trial instance is running within the professional package allowing up to " -"three agents." +"If you're already using Slack for your team communication, you'll love this " +"feature! Our Slack integration can push ticket notifications about the last " +"ticket article based on the following events:" msgstr "" -#: ../system/subscription/index.rst:40 -msgid "Can I change package within the trial?" +#: ../system/integrations/slack.rst:24 +msgid "on Ticket creation" msgstr "" -#: ../system/subscription/index.rst:40 -msgid "No. As soon as the package is changed the subscription begins." +#: ../system/integrations/slack.rst:25 +msgid "on Ticket updates" msgstr "" -#: ../system/subscription/index.rst:45 -msgid "What happens to my trial instance after the trial period ended?" +#: ../system/integrations/slack.rst:26 +msgid "on reached reminders" msgstr "" -#: ../system/subscription/index.rst:43 -msgid "" -"Your instance will automatically be canceled for you. Please see *What " -"happens to my instance after it has been canceled?* for more." +#: ../system/integrations/slack.rst:27 +msgid "a Ticket has escalated" msgstr "" -#: ../system/subscription/index.rst:58 -msgid "What happens to my instance after it has been canceled?" +#: ../system/integrations/slack.rst:28 +msgid "a Ticket is going to escalate" msgstr "" -#: ../system/subscription/index.rst:48 -msgid "That depends slightly on your instance state:" +#: ../system/integrations/slack.rst:30 +msgid "" +"Zammad will provide the Ticket title, a direct link to the Ticket, the event " +"type (creation, updated, escalation), the customer, time and the last " +"article that has triggered the notification." msgstr "" -#: ../system/subscription/index.rst:54 -msgid "Trial instance" +#: ../system/integrations/slack.rst:34 +msgid "" +"This will give you further options, as you can see e.g. escalating tickets " +"that are assigned to an agent that's e.g. absent. You can interact faster, " +"as you might see problems earlier (or even before the problem gets one)." msgstr "" -#: ../system/subscription/index.rst:51 +#: ../system/integrations/slack.rst:38 msgid "" -"If you're still on trial, we will ice your instance and remind you once " -"again about your instance. We then will wait some days and remove your " -"instance from our system. This is the last time we will inform you by Email." +"If needed and wanted, you can even discuss directly about the topic before " +"sending an answer to the customer. Another possible use case would be a " +"agent monitoring new agents and their answers to tickets." msgstr "" -#: ../system/subscription/index.rst:58 -msgid "Paid instance" +#: ../system/integrations/slack.rst:44 +msgid "Configure the Integration" msgstr "" -#: ../system/subscription/index.rst:57 +#: ../system/integrations/slack.rst:46 msgid "" -"If you're a paying customer and canceled your subscription, the instance " -"removal will take place the day after your last subscription day." +"First of all, please go to your slack workspace - go to administration => " +"Manage Apps. If you don't have an app yet, you can simply add a new one - " +"just search for ``Incoming WebHooks`` and customize the app to your needs." msgstr "" -#: ../system/subscription/index.rst:60 -msgid "Can removed instances be restored?" +#: ../system/integrations/slack.rst:50 +msgid "" +"Choose (or create) the channel Zammad should post it's information to and " +"press on \"Add Incoming WebHooks integration\". If you're ready, copy the " +"provided WebHook URL and go to your Zammad installation." msgstr "" -#: ../system/subscription/index.rst:61 -msgid "No. Once your instance has been removed, a restoration is not possible." +#: ../system/integrations/slack.rst:56 +msgid "" +"You need administrative rights on the Slack Workspace. The link to the app " +"directory is normally ``https://[workspace-name].slack.com/apps`` ." msgstr "" -#: ../system/subscription/plan.rst:2 ../system/subscription/plan.rst:38 -msgid "Plan" +#: ../system/integrations/slack.rst:63 +msgid "" +"To configure the slack integration, log in to Zammad and go to Integrations " +"(System) => Slack in the admin panel." msgstr "" -#: ../system/subscription/plan.rst:16 -msgid "Subscription" +#: ../system/integrations/slack.rst:66 +msgid "" +"Here you can choose on what evens Zammad should post information about a " +"ticket to your Slack channel. Next you need to device what groups shall be " +"affected by this, as anybody with access to that specific Slack channel can " +"read at least parts of the ticket this might be a privacy issue, if you " +"select the wrong groups. The username is simply the name that Zammad uses as " +"display name inside the Slack chat. The channel defines the Slack channel " +"the information is being posted in. As last option, you can set a custom " +"icon for posting to slack." msgstr "" -#: ../system/subscription/plan.rst:5 +#: ../system/integrations/slack.rst:74 msgid "" -"On the top of the subscription summary you'll find the number of used and " -"available (booked) agent seats. By using the *see more* link you can also " -"expand an agent list to see the currently configured active agents. This " -"list *does not* count accounts with admin permissions only." +"When you're ready, just hit \"Submit\" and enable the integration. Zammad " +"will now post new ticket information based on the trigger you chose. Below " +"the options you have the recent log that shows the latest requests to Slack " +"for debugging if needed." msgstr "" -#: ../system/subscription/plan.rst:0 +#: ../system/integrations/slack.rst:81 msgid "" -"Within subscription you can always see how many agents are still\n" -"available to add and who uses the seats." +"If you leave the Icon URL empty, Zammad will use the Zammad logo instead. " +"The icon should be a square PNG file." msgstr "" -#: ../system/subscription/plan.rst:14 +#: ../system/integrations/slack.rst:90 msgid "" -"Learn more on how to manage your agents in general :doc:`here `." +"The following figure shows how it will look if you choose to receive updates " +"on created and updated tickets. On every post Zammad sends to the Slack " +"channel, you can create new threads to discuss about the new article." msgstr "" -#: ../system/subscription/plan.rst:19 +#: ../system/integrations/slack.rst:96 msgid "" -"This section gives you an overview of the available plans and their " -"functions / limits. If you require a more detailed table, check our " -"`detailed pricing table `_ for more." +"If you just want to keep track of soon escalating or already escalated " +"tickets, it will look the the following figure. Zammad changes the color in " +"front of the post so you can easily see the state of the ticket." msgstr "" -#: ../system/subscription/plan.rst:23 +#: ../system/integrations/slack.rst:102 msgid "" -"Your selection in this step will decide on the base agent price and e.g. " -"agent limits that might apply in the summary step." +"If you change the state, Zammad will also put information on what state the " +"ticket gets and (if pending state) the date until it pends. You'll also " +"recognize the color codes in front of posts on slack, as they are exact the " +"same the ticket state colors you'll see in Zammad!" msgstr "" -#: ../system/subscription/plan.rst:26 -msgid "" -"The green *Selected* button will also tell you what plan you're currently in." +#: ../system/integrations/smime/index.rst:2 +msgid "S/MIME" msgstr "" -#: ../system/subscription/plan.rst:30 +#: ../system/integrations/smime/index.rst:11 msgid "" -"Trial instances are running at Professional with 3 agents. The plan cannot " -"be changed during the trial for technical reasons, if you require more " -"agents for testing, please contact `our sales team `_ with a reason for the raise request." +"S/MIME is the most widely-supported method for secure email communication. " +"With S/MIME, you can exchange **signed** and **encrypted** messages with " +"others." msgstr "" -#: ../system/subscription/plan.rst:0 +#: ../system/integrations/smime/index.rst:15 msgid "" -"Screenshot showing three available packages for a hosted Zammad\n" -"instance" +"is proof that a message hasn't been tampered with or sent by an impersonator." msgstr "" -#: ../system/subscription/plan.rst:83 -msgid "Summary" +#: ../system/integrations/smime/index.rst:17 +msgid "" +"In other words, it guarantees a message's **integrity** and **authenticity**." msgstr "" -#: ../system/subscription/plan.rst:41 -msgid "" -"In this section you can adjust the settings of the previous selected plan." +#: ../system/integrations/smime/index.rst:22 +msgid "In other words, it guarantees **privacy** and **data security**." msgstr "" -#: ../system/subscription/plan.rst:45 -msgid "" -"Note that upgrading (more agents, higher package) is always possible, " -"however, downgrading will only happen when your billing period renews." +#: ../system/integrations/smime/index.rst:28 +msgid "Screencast demo of S/MIME features for both new tickets and replies" msgstr "" -#: ../system/subscription/plan.rst:49 +#: ../system/integrations/smime/index.rst:28 msgid "" -"Upgrading resets your billing period and existing credit will be deducted " -"from the new total." +"Once S/MIME has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " +"appear in the ticket composer." msgstr "" -#: ../system/subscription/plan.rst:58 -msgid "Billing cycle" +#: ../system/integrations/smime/index.rst:32 +msgid ":doc:`🔪 Prerequisites `" msgstr "" -#: ../system/subscription/plan.rst:53 +#: ../system/integrations/smime/index.rst:31 msgid "" -"You can choose between either monthly or yearly billing. The price per agent " -"will be cheaper if you decide for yearly billing." +"New to S/MIME? This section helps you to find certificate providers and " +"points out Limitations." msgstr "" -#: ../system/subscription/plan.rst:56 -msgid "" -"If you're still trying out things and are unsure of the right package for " -"your instance, you may want to choose monthly first and then upgrade to " -"yearly when you're sure." +#: ../system/integrations/smime/index.rst:35 +msgid ":doc:`📝 Manage Certificates `" msgstr "" -#: ../system/subscription/plan.rst:66 -msgid "Plan: (Starter|Professional|Plus) - Agents" +#: ../system/integrations/smime/index.rst:35 +msgid "Add and download certificates; configure group default behaviors." msgstr "" -#: ../system/subscription/plan.rst:61 -msgid "Choose the number of agents you require for your instance." +#: ../system/integrations/smime/index.rst:38 +msgid ":doc:`😦 Troubleshooting `" msgstr "" -#: ../system/subscription/plan.rst:63 -msgid "" -"Keep in mind that some packages may have agent limits. Depending on the " -"previous chosen package, you won't be able to exceed specific agent numbers. " -"Also note that setting less agents than currently configured is not possible." +#: ../system/integrations/smime/index.rst:38 +msgid "Took a wrong turn? About recent logs and common issues." msgstr "" -#: ../system/subscription/plan.rst:69 -msgid "Total" +#: ../system/integrations/smime/index.rst:43 +msgid "" +"For more details on how S/MIME integration works on the agent side, see the :" +"user-docs:`user docs `." msgstr "" -#: ../system/subscription/plan.rst:69 -msgid "This will be the net total you're going to be billed." +#: ../system/integrations/smime/manage-certificates.rst:2 +msgid "Manage Certificates" msgstr "" -#: ../system/subscription/plan.rst:71 +#: ../system/integrations/smime/manage-certificates.rst:4 msgid "" -"By using the *Update subscription* button, the instance package will be " -"adjusted immediately. If you didn't provide a payment method yet, Zammad " -"will request you to provide one at this point." +"S/MIME is **disabled by default**. Enable it to start adding certificates." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:10 +msgid "Dialogue to add new certificates or private keys" msgstr "" -#: ../system/subscription/plan.rst:77 +#: ../system/integrations/smime/manage-certificates.rst:10 msgid "" -"In case you're still within the trial period, this means that the trial will " -"be over immediately!" +"Manage certificates in the Admin Panel under **System > Integrations > S/" +"MIME**. Certificates may be pasted in as plain text or uploaded from a file." msgstr "" -#: ../system/subscription/plan.rst:80 -msgid "Down- or upgrading during the trial period *is not* possible." +#: ../system/integrations/smime/manage-certificates.rst:14 +msgid "Add Certificate Data" msgstr "" -#: ../system/subscription/plan.rst:0 -msgid "Screenshot showing payment options and a pricing summary" +#: ../system/integrations/smime/manage-certificates.rst:36 +msgid "Add Certificate" msgstr "" -#: ../system/subscription/plan.rst:99 -msgid "Payment method" +#: ../system/integrations/smime/manage-certificates.rst:17 +msgid "" +"Import public-key certificates for both your own organization and your " +"contacts." msgstr "" -#: ../system/subscription/plan.rst:86 -msgid "You can pay via credit card or SEPA mandate." +#: ../system/integrations/smime/manage-certificates.rst:19 +msgid "" +"You can also add a bunch of certificates in one go by providing a single " +"file with all relevant certificates." msgstr "" -#: ../system/subscription/plan.rst:91 -msgid "Credit card" +#: ../system/integrations/smime/manage-certificates.rst:22 +msgid "🕵️ **ALWAYS verify certificates in-person or over the phone!**" msgstr "" -#: ../system/subscription/plan.rst:89 +#: ../system/integrations/smime/manage-certificates.rst:24 msgid "" -"Simply follow the dialogue by clicking *authorize* and confirm -if required " -"by your bank- your consent to Zammad using your card for the payments." +"The whole point of signatures is to alert you when someone is trying to " +"pretend to be someone they're not. Never accept a certificate from someone " +"online without verifying it first." msgstr "" -#: ../system/subscription/plan.rst:95 -msgid "SEPA" +#: ../system/integrations/smime/manage-certificates.rst:28 +msgid "📇 **What about trusted certificate authorities?**" msgstr "" -#: ../system/subscription/plan.rst:94 +#: ../system/integrations/smime/manage-certificates.rst:30 msgid "" -"Provide the requested information of the bank account holder and update if " -"you're ready. You'll then receive an email with the SEPA mandate." +"In some cases (e.g. when dealing with large enterprises), you may be given a " +"certificate for an entire CA, rather than a single contact. Add it here to " +"trust *all* certificates issued by that CA." msgstr "" -#: ../system/subscription/plan.rst:97 +#: ../system/integrations/smime/manage-certificates.rst:35 msgid "" -"Technically there's also the possibility to pay via invoice, however - this " -"method only applies to a fairly low number of instances. Please contact `our " -"sales team `_ for more information." +"Commercial CAs can usually be verified online. Zammad does not include a " +"list of built-in, trusted CAs." msgstr "" -#: ../system/translations.rst:2 -msgid "Translations" +#: ../system/integrations/smime/manage-certificates.rst:57 +msgid "Add Private Key" msgstr "" -#: ../system/translations.rst:4 +#: ../system/integrations/smime/manage-certificates.rst:39 msgid "" -"Translations of Zammad are processed centrally in our `Weblate instance " -"`_. This allows non-developers to review " -"and update translation texts of the language they actually speak." +"Once you've added a public-key certificate, you can import its matching " +"private key." msgstr "" -#: ../system/translations.rst:9 +#: ../system/integrations/smime/manage-certificates.rst:42 msgid "" -"Your language is in an incomplete translation state or has typos? Please " -"consider helping us in sorting this out! All you need is either a GitHub " -"account or to register directly in our instance." +"Private keys are for **your own organization only**; never ask your contacts " +"for their private keys." msgstr "" -#: ../system/translations.rst:13 +#: ../system/integrations/smime/manage-certificates.rst:0 msgid "" -"Did you know? This is also where the documentation translations are handled. " -"🤓" +"S/MIME integration showing configured certificates and possible issues with " +"Logging" msgstr "" -#: ../system/translations.rst:15 +#: ../system/integrations/smime/manage-certificates.rst:50 msgid "" -"Have a look in our :docs:`contribution section ` in the system documentation to get started!" +"A note is displayed on certificates with a matching private key (see line 2)." msgstr "" -#: ../system/translations.rst:20 -msgid "Local Translations" +#: ../system/integrations/smime/manage-certificates.rst:52 +msgid "📤 **Certificates and private keys must be uploaded separately.**" msgstr "" -#: ../system/translations.rst:22 +#: ../system/integrations/smime/manage-certificates.rst:54 msgid "" -"Apart from these system translations, there's still local translations you " -"can manage. This is relevant if you added custom objects that require " -"translations or even custom states and priorities." +"If your certificate and private key are bundled together in the same file or " +"PEM block, import it twice (once using each button)." msgstr "" -#: ../system/translations.rst:None -msgid "Translation management screen within the admin menu" +#: ../system/integrations/smime/manage-certificates.rst:57 +msgid "Please note that bulk imports of private keys are not possible." msgstr "" -#: ../system/translations.rst:31 -msgid "Updating Translations" +#: ../system/integrations/smime/manage-certificates.rst:60 +msgid "Download Certificate Data" msgstr "" -#: ../system/translations.rst:33 +#: ../system/integrations/smime/manage-certificates.rst:62 msgid "" -"Because of how Zammad ships translations, the only way to update the system " -"translations is to update your Zammad installation. The benefit of this is " -"that you no longer need internet access during a Zammad upgrade as the " -"package has everything it requires already." +"You can download the earlier provided certificates and private keys at any " +"time from your Zammad instance." msgstr "" -#: ../system/translations.rst:39 -msgid "Translation of Custom Objects" +#: ../system/integrations/smime/manage-certificates.rst:65 +msgid "" +"Please note that passphrase-protected private keys stay protected and when " +"you download them, you have to know the passphrase to use them after " +"downloading." msgstr "" -#: ../system/translations.rst:41 -msgid "" -"No problem at all! You can customize any translation locally, even if it is " -"not initially provided by the system." +#: ../system/integrations/smime/manage-certificates.rst:73 +msgid "Dialogue to download certificates or private keys" msgstr "" -#: ../system/translations.rst:44 +#: ../system/integrations/smime/manage-certificates.rst:73 +msgid "Download stored certificates and their keys" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:78 msgid "" -"Translation is supported for a broad number of features, including but not " -"limited to custom:" +"The ticket composer will set all outgoing messages to **signed and " +"encrypted** by default (assuming the required certificates exist)." msgstr "" -#: ../system/translations.rst:47 -msgid "Object Attributes" +#: ../system/integrations/smime/manage-certificates.rst:82 +msgid "These defaults can be modified on a per-group basis:" msgstr "" -#: ../system/translations.rst:48 -msgid "Ticket Macros" +#: ../system/integrations/smime/manage-certificates.rst:None +msgid "Zammad allowing to choose the default behavior on per group basis" msgstr "" -#: ../system/translations.rst:49 -msgid "Ticket Overviews" +#: ../system/integrations/smime/manage-certificates.rst:89 +msgid "" +"Of course, agents can always manually change these settings on each email " +"they send out." msgstr "" -#: ../system/translations.rst:50 -msgid "Ticket Priorities" +#: ../system/integrations/smime/prerequisites.rst:4 +msgid "A certificate *and* private key for your own organization" msgstr "" -#: ../system/translations.rst:51 -msgid "Ticket States" +#: ../system/integrations/smime/prerequisites.rst:6 +msgid "" +"(Use this to ✒️ **sign outgoing messages** and 🔓 **decrypt incoming " +"messages**.)" msgstr "" -#: ../system/translations.rst:54 -msgid "Customizing Translations" +#: ../system/integrations/smime/prerequisites.rst:9 +msgid "" +"Certificates belonging your contacts, or their issuing certificate authority " +"(CA)" msgstr "" -#: ../system/translations.rst:56 +#: ../system/integrations/smime/prerequisites.rst:11 msgid "" -"Within the translation screen, simply click on the **New Translation** " -"button." +"(Use these to ✅ **verify incoming message signatures** and 🔒 **encrypt " +"outgoing messages**.)" msgstr "" -#: ../system/translations.rst:None -msgid "New translation dialog" +#: ../system/integrations/smime/prerequisites.rst:14 +msgid "🙋 **I'm new to S/MIME. Where can I get a certificate?**" msgstr "" -#: ../system/translations.rst:62 +#: ../system/integrations/smime/prerequisites.rst:16 msgid "" -"In the dialog you can immediately enter the exact translation source (if you " -"know it) and your custom translation text for it and click **Submit**." +"The easiest way to get certificates is to buy an annual subscription through " +"a commercial CA, such as:" msgstr "" -#: ../system/translations.rst:65 +#: ../system/integrations/smime/prerequisites.rst:19 msgid "" -"Alternatively, try to search for translation suggestions in the list below. " -"Selecting an item from the list will pre-fill the translation source for you " -"and then you can just enter your custom translation." +"`Sectigo (formerly Comodo) `_" msgstr "" -#: ../system/translations.rst:69 -msgid "" -"The target language will always default to your current language selection. " -"If you need to translate for a different language, simply change the " -"selection before submitting." +#: ../system/integrations/smime/prerequisites.rst:20 +msgid "`Secorio `_" msgstr "" -#: ../system/translations.rst:73 -msgid "" -"All your custom translations will show up in the overview table when added. " -"And they will even persist across Zammad updates!" +#: ../system/integrations/smime/prerequisites.rst:21 +msgid "`GlobalSign `_" msgstr "" -#: ../system/translations.rst:76 -msgid "" -"Make sure to reload your browser if a translated string is not displayed." +#: ../system/integrations/smime/prerequisites.rst:23 +msgid "(Zammad is not affiliated with these CAs in any way.)" msgstr "" -#: ../system/translations.rst:80 -msgid "Reverting to Original Translations" +#: ../system/integrations/smime/prerequisites.rst:25 +msgid "" +"You can also generate your own self-signed certificates, but the process is " +"complicated and usually 🙅 **involves extra work for your contacts**." msgstr "" -#: ../system/translations.rst:82 +#: ../system/integrations/smime/prerequisites.rst:29 msgid "" -"If you want to revert a custom translation to original text, simply use the " -"appropriate action within the row of the overview table." +"Bear in mind that 🤝 **S/MIME only works if the other party is using it, too." +"**" msgstr "" -#: ../system/translations.rst:85 +#: ../system/integrations/smime/prerequisites.rst:32 +msgid "Certificate and Private Key Checks on Upload" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:34 msgid "" -"Depending on the type of the translation source, the action has a slightly " -"different name:" +"The certificate and public key validation is based on the ``X509v3`` " +"extensions." msgstr "" -#: ../system/translations.rst:88 -msgid "**Reset** for customized system translations" +#: ../system/integrations/smime/prerequisites.rst:49 +msgid "Uploading a *client certificate*?" msgstr "" -#: ../system/translations.rst:89 -msgid "**Remove** for customized local translations" +#: ../system/integrations/smime/prerequisites.rst:41 +msgid "The following attributes are required then:" msgstr "" -#: ../system/translations.rst:91 -msgid "" -"In both cases, the action will remove the customized translation after a " -"confirmation." +#: ../system/integrations/smime/prerequisites.rst:39 +msgid "Subject Alternative Name (at least one email address has to be present)" msgstr "" -#: ../system/translations.rst:None -msgid "Screenshot showing the location of the Remove action" +#: ../system/integrations/smime/prerequisites.rst:40 +msgid "Key Usage (``Digital Signature`` and/or ``Key Encipherment``)" msgstr "" -#: ../system/translations.rst:99 -msgid "Inline Translations" +#: ../system/integrations/smime/prerequisites.rst:41 +msgid "Public key algorithm (either ``RSA`` or ``EC``)" msgstr "" -#: ../system/translations.rst:101 +#: ../system/integrations/smime/prerequisites.rst:43 msgid "" -"If you prefer a more hands-on approach, you can activate the inline or on-" -"screen translation feature by pressing ``ctrl`` + ``alt`` + ``t`` at any " -"time and on any screen." +"The Extended Key Usage attribute is optional. If the certificate provides " +"the named attribute, than it must contain the value ``E-mail Protection``." msgstr "" -#: ../system/translations.rst:105 +#: ../system/integrations/smime/prerequisites.rst:46 msgid "" -"All customizable translation texts will be highlighted for you on the " -"screen. Just click into the highlighted area and update the text in place." +"Please note that any usable email adress has to be prefixed with ``email:`` " +"or ``rfc822:``." msgstr "" -#: ../system/translations.rst:None -msgid "Inline translation mode activated for the Overview screen" +#: ../system/integrations/smime/prerequisites.rst:49 +msgid "The named public key algorithms are mandatory for private keys as well." msgstr "" -#: ../system/translations.rst:112 +#: ../system/integrations/smime/prerequisites.rst:54 +msgid "Uploading a *CA certificate*?" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:52 msgid "" -"When finished editing, simply press ``ctrl`` + ``alt`` + ``t`` again to " -"deactivate." +"In the case of an uploaded CA certificate, providing the value ``CA:TRUE`` " +"in the attribute *Basic Contstraints*, the previously mentioned attributes " +"are not verified." msgstr "" -#: ../system/translations.rst:117 +#: ../system/integrations/smime/prerequisites.rst:56 msgid "" -"Even though it's available on any screen, the inline translation feature " -"requires admin permissions. It works only for the current language " -"selection. If you need to translate a different language, first change the " -"language in your :user-docs:`profile settings `." +"In general, the usage of any expired (``Not After``) or not yet valid (``Not " +"Before``) certificate is denied for outgoing emails." msgstr "" -#: ../system/variables.rst:2 -msgid "Variables" +#: ../system/integrations/smime/prerequisites.rst:59 +msgid "Example certificate:" msgstr "" -#: ../system/variables.rst:4 +#: ../system/integrations/smime/prerequisites.rst:85 msgid "" -"Please note that this is just an overview of available variables. It might " -"be incomplete or variables might not be available within some functions. If " -"you're missing variables or are not sure if something is not working as " -"expected, feel free to ask over at the `Community `_." +"Please note that Zammad will distrust senders by default. This means that " +"you're always required to provide certificate data, no matter if for signing " +"or encrypting." msgstr "" -#: ../system/variables.rst:10 -msgid "" -"Variables can be called by typing ``::`` (just like text modules in the " -"frontend), as long as you're in a supported text field within the backend. " -"Zammad will display all variables being available within this context and " -"replace it to the variable as soon as you selected an entry." +#: ../system/integrations/smime/prerequisites.rst:89 +msgid "This is by design and can't be adjusted." msgstr "" -#: ../system/variables.rst:15 +#: ../system/integrations/smime/troubleshooting.rst:4 msgid "" -"You have an empty field which you referenced and it appears as ``-``? That's " -"currently working as designed - you might want to ensure that these fields " -"always have a value." +"All of the system's latest S/MIME activity is displayed in the **Recent " +"Logs** section." msgstr "" -#: ../system/variables.rst:20 -msgid "Variable Categories" +#: ../system/integrations/smime/troubleshooting.rst:11 +msgid "Sample entries of in- and outgoing S/MIME related emails." msgstr "" -#: ../system/variables.rst:31 -msgid "Wait, What About Custom Objects?" +#: ../system/integrations/smime/troubleshooting.rst:11 +msgid "" +"Logs report the status and details of all mail, both incoming and outgoing, " +"that used signing/verification or encryption/decryption." msgstr "" -#: ../system/variables.rst:33 +#: ../system/integrations/smime/troubleshooting.rst:14 msgid "" -"Good point! Of course, we can't predict what objects you might create, but " -"we can give you a hint on how to put the puzzle together to get your custom " -"values." +"This log does **not** include email sent by :doc:`triggers ` or the :doc:`scheduler `. For those, check your " +"``production.log``." +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:20 +msgid "Common Issues" +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:30 +msgid "I received a signed/encrypted email before I set up S/MIME integration" msgstr "" -#: ../system/variables.rst:36 +#: ../system/integrations/smime/troubleshooting.rst:23 msgid "" -"For this, we'll talk about the inner part of the variable (so everything " -"within ``#{}``), please put the outer part around to have a valid variable. " -"The first part of the variable name consist of the object type. Currently " -"these are:" +"No problem. Once S/MIME has been enabled and the appropriate certificates " +"have been added, agents will be prompted to retry verification/decryption on " +"matching emails." msgstr "" -#: ../system/variables.rst:41 -msgid "Ticket (``ticket``)" +#: ../system/integrations/smime/troubleshooting.rst:0 +msgid "Screenshot of user prompt to retry decryption" msgstr "" -#: ../system/variables.rst:42 -msgid "User (``user``)" +#: ../system/integrations/smime/troubleshooting.rst:38 +msgid "The 🔒 **Encrypt** button is disabled" msgstr "" -#: ../system/variables.rst:43 -msgid "Organization (``organization``)" +#: ../system/integrations/smime/troubleshooting.rst:33 +msgid "Have you added the recipient's certificate?" msgstr "" -#: ../system/variables.rst:44 -msgid "Group (``group``)" +#: ../system/integrations/smime/troubleshooting.rst:34 +msgid "Are you sure the recipient's certificate is valid?" msgstr "" -#: ../system/variables.rst:46 -msgid "" -"The second part is the name of the object. This is the name you define " -"during object creation and can be found within the object menu at any time. " -"The first and second part of a variable is divided by a point, e.g.: " -"``ticket.number`` which will in total be ``#{ticket.number}``." +#: ../system/integrations/smime/troubleshooting.rst:35 +msgid "Have you checked your ``production.log`` for more details?" msgstr "" -#: ../system/variables.rst:51 +#: ../system/integrations/smime/troubleshooting.rst:37 msgid "" -"Now, in some situations it's possible that you'll need to use a third part. " -"The best example for such a situation would be a ``select`` or ``tree-" -"select`` field which will by default return the key value, not it's display " -"name. For this, just extend your variable with ``.value``. This will result " -"in ``#{ticket.select.value}``." +"If encryption doesn't work in the composer, it won't work in :doc:`triggers " +"` or the :doc:`scheduler ` either!" msgstr "" -#: ../system/variables.rst:60 -msgid "Using Translated Variables" +#: ../system/integrations/smime/troubleshooting.rst:42 +msgid "The ✅ **Sign** button is disabled" msgstr "" -#: ../system/variables.rst:62 +#: ../system/integrations/smime/troubleshooting.rst:41 msgid "" -"If you want to use a translated variable in triggers or schedulers, you can " -"extend the placeholder like this: ``#{t(ticket.state.name)}``. The ``t`` " -"tells Zammad to search for fitting translated strings. The used output " -"language is based on the system language of Zammad which you can set in the " -"admin panel under :doc:`/settings/branding` or based on the selected locale " -"in the trigger/scheduler edit dialog." +"Have you added **both the certificate and private key** for your " +"organization?" msgstr "" -#: ../system/variables.rst:69 +#: ../system/integrations/smime/troubleshooting.rst:42 msgid "" -"A possible use-case: you want to send your customers updates on tickets via " -"trigger or scheduler which should include the state of the ticket. Using the " -"default ``#{ticket.state.name}`` (without the translation flag ``t()``) " -"would lead to the output of the original (english) name of the state." +"Does the email address on the certificate match the email address of the " +"agent/group composing the email?" msgstr "" -#: ../system/variables.rst:75 -msgid "Date and Time Formatting" +#: ../system/integrations/smime/troubleshooting.rst:45 +msgid "Error: “Fingerprint already taken”" msgstr "" -#: ../system/variables.rst:77 -msgid "" -"The system (trigger/scheduler selected) locale and timezone predefines a " -"default format of date and timestamp. This format is customizable by using " -"the ``dt()`` method." +#: ../system/integrations/smime/troubleshooting.rst:45 +msgid "Are you sure you haven't added this certificate already?" msgstr "" -#: ../system/variables.rst:79 -msgid "The method arguments are as follows:" +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Error: “❌ invalid byte sequence in UTF-8”" msgstr "" -#: ../system/variables.rst:81 -msgid "The date or timestamp variable you want to format." +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Please ensure to provide PEM formatted certificate and keys." msgstr "" -#: ../system/variables.rst:82 -msgid "The output format string." +#: ../system/integrations/smime/troubleshooting.rst:49 +msgid "Did you check if the provided file is a valid certificate or key?" msgstr "" -#: ../system/variables.rst:83 -msgid "The timezone to apply (optional)." +#: ../system/integrations/zabbix.rst:2 +msgid "Zabbix Integration" msgstr "" -#: ../system/variables.rst:86 +#: ../system/integrations/zabbix.rst:5 msgid "" -"``#{dt(ticket.updated_at, \"%A %Y-%m-%d %H:%M in the office\", \"Europe/" -"Berlin\")}``" +"This guide describes how to integrate your Zabbix 5.4 installation with " +"Zammad using the Zabbix webhook feature. This guide will provide " +"instructions on setting up a media type, a user and an action in Zabbix." msgstr "" -#: ../system/variables.rst:87 -msgid "Monday, 2024-03-18 15:31 in the office" +#: ../system/integrations/zabbix.rst:12 +msgid "Zammad with enabled HTTP Token Authentication" msgstr "" -#: ../system/variables.rst:89 -msgid "" -"If you want to use our example, make sure to paste the string above without " -"formatting (``CTRL+Shift+v``), otherwise it won't work." +#: ../system/integrations/zabbix.rst:13 +msgid "Zabbix version 5.4 or higher" msgstr "" -#: ../system/variables.rst:93 -msgid "The following table lists available format directives:" +#: ../system/integrations/zabbix.rst:16 +msgid "Setting up a Zammad" msgstr "" -#: ../system/variables.rst:99 -msgid "Parameter" +#: ../system/integrations/zabbix.rst:18 +msgid "Enable **API Token Access** in Settings > System > API." msgstr "" -#: ../system/variables.rst:102 -msgid "``%Y``" +#: ../system/integrations/zabbix.rst:20 +msgid "" +"Create a **new user** for a Zabbix alerter with an **email address** and " +"create a personal user token with **ticket.agent** permissions." msgstr "" -#: ../system/variables.rst:103 -msgid "Year with 4 digits" +#: ../system/integrations/zabbix.rst:24 +msgid "Zabbix Webhook Configuration" msgstr "" -#: ../system/variables.rst:104 -msgid "Use ``%y`` for year with 2 digits" +#: ../system/integrations/zabbix.rst:27 +msgid "Create a Global Macro" msgstr "" -#: ../system/variables.rst:105 -msgid "``%m``" +#: ../system/integrations/zabbix.rst:29 +msgid "" +"Before setting up the **Webhook**, you need to setup the global macro " +"**{$ZABBIX.URL}**, which must contain the **URL** to the **Zabbix frontend**." msgstr "" -#: ../system/variables.rst:106 -msgid "Month of year (as number with zero-padding)" +#: ../system/integrations/zabbix.rst:33 +msgid "" +"In the **Administration** > **Media types** section, import the `Template`_." msgstr "" -#: ../system/variables.rst:107 -msgid "Use ``%-m`` for month without zero-padding" +#: ../system/integrations/zabbix.rst:38 +msgid "Open the added **Zammad** media type and set:" msgstr "" -#: ../system/variables.rst:108 -msgid "``%d``" +#: ../system/integrations/zabbix.rst:40 +msgid "**zammad\\_access\\_token** to the your **Personal User Token**" msgstr "" -#: ../system/variables.rst:109 -msgid "Day of month (as number with zero-padding)" +#: ../system/integrations/zabbix.rst:41 +msgid "" +"**zammad\\_url** to the **frontend URL** of your **Zammad** installation" msgstr "" -#: ../system/variables.rst:110 -msgid "Use ``%e`` for day without zero-padding" +#: ../system/integrations/zabbix.rst:43 +msgid "**zammad\\_customer** to your **Zammad user email**." msgstr "" -#: ../system/variables.rst:111 -msgid "``%H``" +#: ../system/integrations/zabbix.rst:44 +msgid "" +"**zammad\\_enable\\_tags** to **true** or **false** to enable or disable " +"trigger tags. **Important**: if you enable tag support, each tag is set with " +"a separate request." msgstr "" -#: ../system/variables.rst:112 -msgid "Hour of day in 24h notation with zero-padding" +#: ../system/integrations/zabbix.rst:48 +msgid "" +"If you want to prioritize issues according to **severity** values in Zabbix, " +"you can define mapping parameters:" msgstr "" -#: ../system/variables.rst:113 -msgid "Use ``%k`` for hour without zero-padding" +#: ../system/integrations/zabbix.rst:51 +msgid "**severity\\_**: Zammad priority ID" msgstr "" -#: ../system/variables.rst:114 -msgid "``%I``" +#: ../system/integrations/zabbix.rst:53 +msgid "Click the **Update** button to save the **Webhook** settings." msgstr "" -#: ../system/variables.rst:115 -msgid "Hour of day in 12h notation with zero-padding" +#: ../system/integrations/zabbix.rst:55 +msgid "" +"To receive notifications in **Zammad**, you need to create a **Zabbix user** " +"and add **Media** with the **Zammad** type." msgstr "" -#: ../system/variables.rst:116 +#: ../system/integrations/zabbix.rst:58 msgid "" -"Use ``%l`` for hour without zero-padding and ``%p`` / ``%P`` for meridian " -"indicator" +"For **Send to**: enter any text, as this value is not used, but is required." msgstr "" -#: ../system/variables.rst:117 -msgid "``%M``" +#: ../system/integrations/zabbix.rst:61 +msgid "" +"For more information, use the `Zabbix documentation `_." msgstr "" -#: ../system/variables.rst:118 -msgid "Minute of hour" +#: ../system/maintenance.rst:2 +msgid "Maintenance" msgstr "" -#: ../system/variables.rst:120 -msgid "``%S``" +#: ../system/maintenance.rst:4 +msgid "" +"Zammad comes with a maintenance mode that you can use for e.g. updating the " +"instance or changing settings while restricting availability and functions." msgstr "" -#: ../system/variables.rst:121 -msgid "Second of Minute" +#: ../system/maintenance.rst:13 +msgid "Mode" msgstr "" -#: ../system/variables.rst:123 -msgid "``%A``" +#: ../system/maintenance.rst:8 +msgid "The mode setting allows you to enable or disable the maintenance mode." msgstr "" -#: ../system/variables.rst:124 -msgid "Weekday name" +#: ../system/maintenance.rst:10 +msgid "Defaults to *off*." msgstr "" -#: ../system/variables.rst:125 -msgid "Use ``%a`` for abbreviated name or ``%^A`` for uppercase name" +#: ../system/maintenance.rst:12 +msgid "" +"The maintenance mode will restrict access to administrative roles only. This " +"means agents and customers are logged off." msgstr "" -#: ../system/variables.rst:126 -msgid "``%B``" +#: ../system/maintenance.rst:23 +msgid "@Login" msgstr "" -#: ../system/variables.rst:127 -msgid "Month name" +#: ../system/maintenance.rst:16 +msgid "" +"This setting allows you to provide a login message within a green banner " +"above the login screen. Click into the green banner in the settings page to " +"adjust your message. To activate the message, activate the *@Login* setting." msgstr "" -#: ../system/variables.rst:128 -msgid "Use ``%b`` for abbreviated name" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing the default login message within the\n" +"settings page" msgstr "" -#: ../system/variables.rst:129 -msgid "``%U``" +#: ../system/maintenance.rst:26 +msgid "" +"Send an informative message to **all active sessions**. This comes handy to " +"inform your agents e.g. about mayor outages or to force reloads after " +"configuration changes." msgstr "" -#: ../system/variables.rst:130 -msgid "Week number of current year" +#: ../system/maintenance.rst:31 +msgid "This is the messages title (slightly bigger than the normal message)." msgstr "" -#: ../system/variables.rst:131 -msgid "Use ``%W`` for a different calculation method" +#: ../system/maintenance.rst:34 +msgid "The text you want to provide to your logged in sessions." msgstr "" -#: ../system/variables.rst:134 +#: ../system/maintenance.rst:39 +msgid "Reload application" +msgstr "" + +#: ../system/maintenance.rst:37 msgid "" -"We support the known format directives for the Ruby built-in method " -"``strftime`` of the ``DateTime`` class. For more information, see `here " -"`_." +"Selecting this option will change the message acceptance button from *Close* " +"(with nothing happening) to *Continue session*, which forces the application " +"to reload." msgstr "" -#: ../system/variables/article.rst:2 -msgid "Articles" +#: ../system/maintenance.rst:43 +msgid "" +"If you have customers that are logged in to Zammad, they'll also be notified " +"if they're active in that moment." msgstr "" -#: ../system/variables/article.rst:4 ../system/variables/config.rst:4 -#: ../system/variables/current-user.rst:4 ../system/variables/ticket.rst:4 +#: ../system/maintenance.rst:48 +msgid "Example without reload application" +msgstr "" + +#: ../system/maintenance.rst:52 msgid "" -"If you're missing variables or are not sure if something is not working as " -"expected, feel free to ask over at the `Community `_." +"Message setting within Zammad's admin settings without ticket reload " +"application setting." msgstr "" -#: ../system/variables/article.rst:6 +#: ../system/maintenance.rst:0 msgid "" -"Below you can find all available ticket article-based variables within " -"Zammad. These can be called via Triggers for example. If you're unsure if " -"Zammad does support variables at the point you're at, you can try to type " -"``::`` to check." +"Screenshot showing the send message settings without ticket\n" +"reload application set" msgstr "" -#: ../system/variables/article.rst:9 ../system/variables/config.rst:9 -#: ../system/variables/ticket.rst:9 +#: ../system/maintenance.rst:61 ../system/maintenance.rst:85 msgid "" -"The below list gives you an example what kind of data you can expect, it's " -"not intended to explain the data itself." +"The modal all other active sessions will see upon pressing *Send to clients*." msgstr "" -#: ../system/variables/article.rst:11 -msgid "Article Variables" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing modal caused by maintenance's message\n" +"without reload application ticket" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "name" +#: ../system/maintenance.rst:72 +msgid "Example with reload application" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "variable" +#: ../system/maintenance.rst:76 +msgid "" +"Message setting within Zammad's admin settings with ticket reload " +"application setting." msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "example" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing the send message settings with ticket\n" +"reload application set" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Web" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing modal caused by maintenance's message\n" +"with reload application ticket" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.web}``" +#: ../system/monitoring.rst:2 +msgid "Monitoring" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``https://zammad.com`` or empty if not set in user object" +#: ../system/monitoring.rst:4 +msgid "" +"This function is only available in self hosted instances. If you use Zammad " +"in our cloud, we are monitoring the system on our own and take steps to fix " +"potential problems directly." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > VIP" +#: ../system/monitoring.rst:11 +msgid "" +"On the monitoring page, you can see the current health state of Zammad under " +"\"*Current Status*\" at the bottom. This can be useful if you want to have a " +"look if everything is up and running. As an example, you could have a look " +"in the monitoring when you assume that some emails aren't processed from " +"Zammad." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.vip}``" +#: ../system/monitoring.rst:17 +msgid "**Can't receive an email and the monitoring response is \"healthy\"?**" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -msgid "``true`` or ``false``" +#: ../system/monitoring.rst:19 +msgid "" +"Zammad will just inform you about unprocessable emails. This is not the case " +"for oversized emails. You can adjust the maximum email size in :doc:`../" +"channels/email/settings`." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Phone" +#: ../system/monitoring.rst:24 +msgid "Monitoring API" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.phone}``" +#: ../system/monitoring.rst:26 +msgid "" +"Beside the indication in the monitoring page, you can also use an external " +"monitoring tool to monitor Zammad's health. To request the health of Zammad, " +"you need to provide the API key (token) to the external monitoring tool. You " +"can copy the token from the \"*Current Token*\" field as well as the whole " +"API endpoint of your system (\"*Health Check*\" field), in which the API " +"token is already included." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``+4930123456789`` or empty if not set in user object" +#: ../system/monitoring.rst:37 +msgid "Screenshot showing Current Token and Health Check" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Note" +#: ../system/monitoring.rst:37 +msgid "Screenshot showing Token and Health Check" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.note}``" +#: ../system/monitoring.rst:39 +msgid "" +"In addition to that, you can reset the auto-generated token to make sure " +"that already configured monitoring systems won't work anymore. So, please " +"use this \"*Reset*\" button only if you know what you do!" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Some note about user`` or empty if not set in user object" +#: ../system/monitoring.rst:44 +msgid "Example Output" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Mobile" +#: ../system/monitoring.rst:0 +msgid "No issues found" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.mobile}``" +#: ../system/monitoring.rst:48 ../system/monitoring.rst:60 +msgid "**Indicator in Zammad**:" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Login" +#: ../system/monitoring.rst:0 +msgid "Screenshot showing monitoring with no issues" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.login}``" +#: ../system/monitoring.rst:54 ../system/monitoring.rst:66 +msgid "**API response**::" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -#: ../system/variables/ticket.rst:1 -msgid "``jdoe``" +#: ../system/monitoring.rst:0 +msgid "Issues were found" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Lastname" +#: ../system/monitoring.rst:0 +msgid "Screenshot showing monitoring with issues" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.lastname}``" +#: ../system/objects.rst:2 +msgid "Objects" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -#: ../system/variables/ticket.rst:1 -msgid "``Doe`` or empty if not set" +#: ../system/objects.rst:4 +msgid "" +"In Zammad you can add your own fields to tickets, users, organizations and " +"even groups (these are called \"objects\"). This can be useful if you need " +"to add further information to a ticket or any other object in Zammad and the " +"information doesn't fit in any existing field." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Firstname" +#: ../system/objects.rst:11 +msgid "" +"Try to avoid deleting attributes (and disable them instead) as Zammad might " +"run into unexpected conditions if they are referenced somewhere." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.firstname}``" +#: ../system/objects.rst:16 +msgid "" +"Here's an overview of object attributes. On the upper right you can add new " +"attributes. By default, there will be no custom fields - standard attributes " +"will be grayed out, you can't delete or change those. You can edit custom " +"attributes (they are displayed in black font and have a trash bin on the " +"right side) just by clicking on them." msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "``Joe`` or empty if not set" +#: ../system/objects.rst:24 +msgid "" +"Attributes you add to Zammad, no matter if they have default values or not, " +"will not update existing information. This means a new ticket field " +"technically will be empty unless you populate it." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Fax" +#: ../system/objects.rst:28 +msgid "" +"Especially in ticket scope this also means that newly added attributes will " +"be indicated as \"changed\" to agents that view the ticket. This may " +"interfere with Zammad's tabs behavior." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.fax}``" +#: ../system/objects.rst:40 +msgid "Ordering Attributes" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Email" +#: ../system/objects.rst:42 +msgid "" +"Since Zammad introduced :doc:`/system/core-workflows` the need to have a " +"custom positioning for attributes has become more important than ever." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.email}``" +#: ../system/objects.rst:45 +msgid "" +"To adjust the position of such an attribute, simply click on the attribute " +"entry in question, scroll down and adjust the position number. Please note " +"that you cannot change the positioning of default attributes." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``jdoe@example.com``" +#: ../system/objects.rst:49 +msgid "" +"In case two attributes have the same position value, Zammad will sort " +"alphabetically by name automatically." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Department" +#: ../system/objects.rst:None +msgid "" +"Screenshot showing custom attribute entries ordered in between default ones" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.department}``" +#: ../system/objects.rst:56 +msgid "Updating Database After Adding or Editing Attributes" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Sales`` or empty if not set in user object" +#: ../system/objects.rst:58 +msgid "" +"When adding or changing attributes, Zammad will not apply the changes " +"instantly, but instead shows you the changed attributes first. If you're " +"ready to go, just click on \"Update database\" to apply the changes to " +"Zammad. If you made a mistake or just want to discard your changes, click " +"\"Discard changes\"." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Address" +#: ../system/objects.rst:64 +msgid "" +"After applying the changes with \"Update Database\", a restart of Zammad is " +"**mandatory**. If you don't perform it, you may experience unexpected " +"behavior or even errors. You may want to do this kind of configuration " +"during maintenance windows." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.address}``" +#: ../system/objects.rst:72 +msgid "" +"Changes on objects require you to update the database to apply these changes." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Some street 1, 12345 Berlin`` or empty if not set in user object" +#: ../system/objects.rst:75 +msgid "**🤓 Service restarts can be automated**" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated" +#: ../system/objects.rst:0 +msgid "Hosted environments automatically restart for you." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_at}``" +#: ../system/objects.rst:0 +msgid "" +"If you're using a self-hosted installation you can use :docs:`environment " +"variables `" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``2019-10-08 15:24:47 UTC``" +#: ../system/objects.rst:82 +msgid "System Attributes" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Type > Name" +#: ../system/objects.rst:84 +msgid "" +"Zammad comes with pre-configured attributes. Some of them can't be edited " +"via UI (or at all). This is required for proper operation of Zammad and not " +"a bug." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.type.name}``" +#: ../system/objects.rst:90 +msgid "Ticket State" msgstr "" -#: ../system/variables/article.rst:1 +#: ../system/objects.rst:92 msgid "" -"``email`` (`list of article types `_)" +"If the pre-configured states aren't enough for you or you want to change " +"them, you can do so by clicking on the cogwheel icon in the state row in the " +"ticket tab. But you should be careful when changing pre-configured states. " +"This can lead to unwanted behavior in some cases." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > To" +#: ../system/objects.rst:None +msgid "Screenshot showing highlighted ticket state attribute" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.to}``" +#: ../system/objects.rst:122 +msgid "Handling of states" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``helpdesk@example.com``" +#: ../system/objects.rst:102 +msgid "" +"In the state configuration screen, you can add new states, disable states or " +"change states." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > TicketID" +#: ../system/objects.rst:0 +msgid "Screenshot showing table of default ticket states" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.ticket_id}``" +#: ../system/objects.rst:110 +msgid "" +"To add a new state, click on the \"New Ticket State\" button in the top " +"right corner. To change an existing state, simply click on the affected " +"state. This opens an edit dialog." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``1`` (not ticket number)" +#: ../system/objects.rst:114 +msgid "" +"You can also clone a state or set them to \"Default for new tickets\" or " +"\"Default for follow-ups\" by clicking on the ⁝ action button and select the " +"desired function." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Subject" +#: ../system/objects.rst:118 +msgid "" +"*Default for new tickets* means that this state is used for every newly " +"created ticket." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.subject}``" +#: ../system/objects.rst:121 +msgid "" +"*Default for follow-ups* means that this state is used if the ticket is re-" +"opened after it was closed." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``My amazing subject``" +#: ../system/objects.rst:171 +msgid "Ticket state in detail" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Sender > Name" +#: ../system/objects.rst:125 +msgid "" +"Below you can find a description for each field and option. Please head over " +"to the :ref:`example ` to see the edit dialog." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.sender.name}``" +#: ../system/objects.rst:129 +msgid "" +"This is the name of the state and what you and your agents are seeing when " +"choosing a state somewhere (e.g. in tickets, trigger configuration)." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Customer``, ``Agent`` or ``System``" +#: ../system/objects.rst:137 +msgid "" +"There are different state types you can choose from. By default, Zammad " +"comes with one state per state type." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Visibility" +#: ../system/objects.rst:140 +msgid "" +"**new**: for states for tickets that are new and it hasn't been worked on " +"them" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.internal}``" +#: ../system/objects.rst:142 +msgid "" +"**open**: for states for tickets that are in progress and agents are working " +"on them" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``false`` or ``true`` (false if not internal)" +#: ../system/objects.rst:144 +msgid "**merged**: for states for tickets that are merged with other tickets" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > From" +#: ../system/objects.rst:145 +msgid "" +"**pending reminder**: for states for tickets that are in progress and you " +"want to set a reminder. (default example: *pending reminder*)" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.from}``" +#: ../system/objects.rst:147 +msgid "" +"**pending action**: for states for tickets that are waiting for a specified " +"time and then change their state (default example: *pending close*)" msgstr "" -#: ../system/variables/article.rst:1 +#: ../system/objects.rst:150 msgid "" -"``Joe Doe `` may differ, depends on ``FROM`` of send mail" +"**closed**: for states for tickets that are finished and do not need to be " +"processed further" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Web" +#: ../system/objects.rst:153 +msgid "" +"⚠️ Choosing the correct state type is important! If you are in doubt, have a " +"look on the default states and their types!" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.web}``" +#: ../system/objects.rst:158 +msgid "Ignore escalation" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > VIP" +#: ../system/objects.rst:157 +msgid "" +"Here you can define whether tickets of this state will count to escalation " +"time or not." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.vip}``" +#: ../system/objects.rst:161 +msgid "" +"You can create a note for the state to inform other admins about the state. " +"This has no effect on tickets." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Phone" +#: ../system/objects.rst:165 +msgid "Set the state to *active* or *inactive*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.phone}``" +#: ../system/objects.rst:167 +msgid "" +"it is technically possible to set all states to inactive. To keep Zammad " +"working in such a case, the inactive flag of one of the states is ignored." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Note" +#: ../system/objects.rst:194 +msgid "Ticket state example" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.note}``" +#: ../system/objects.rst:174 +msgid "" +"Let's assume we want to create a new state which indicates that the ticket " +"has to wait for a response of a third party (e.g. service contractor or " +"manufacturer) and we want to to be able to set a reminder." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Mobile" +#: ../system/objects.rst:178 +msgid "" +"First we give the new state a proper name. In this example we call it " +"\"waiting for manufacturer\"." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.mobile}``" +#: ../system/objects.rst:181 +msgid "" +"As state type we choose \"pending reminder\". This indicates that the ticket " +"is still open and we can set a reminder. This reminder can be useful if our " +"manufacturer sometimes isn't responding or we want to remind him to give us " +"an answer." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Login" +#: ../system/objects.rst:186 +msgid "" +"We choose \"no\" for \"ignore escalation\" because we want to escalate the " +"tickets even if we are waiting on the manufacturer's feedback." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.login}``" +#: ../system/objects.rst:189 +msgid "The **result** in the creation dialog will look like this:" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Lastname" +#: ../system/objects.rst:0 +msgid "Screenshot showing ticket state creation dialog with example" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.lastname}``" +#: ../system/objects.rst:199 +msgid "Ticket Priority" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Firstname" +#: ../system/objects.rst:201 +msgid "" +"If the pre-configured priorities aren't enough for you or you want to change " +"them, you can do so by clicking on the cogwheel icon in the priority row in " +"the ticket tab:" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.firstname}``" +#: ../system/objects.rst:None +msgid "Screenshot showing highlighted ticket priority attribute" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Fax" +#: ../system/objects.rst:226 +msgid "Handling of priorities" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.fax}``" +#: ../system/objects.rst:210 +msgid "" +"In the priority configuration screen, you can add new priorities, disable " +"priorities or change priorities." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Email" +#: ../system/objects.rst:0 +msgid "Screenshot showing table of default ticket priorities" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.email}``" +#: ../system/objects.rst:218 +msgid "" +"To add a new priority, click on the \"New Priority\" button in the top right " +"corner. To change an existing priority, simply click on the affected " +"priority. This opens an edit dialog." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Department" +#: ../system/objects.rst:222 +msgid "" +"You can also clone a priority or set them to \"Default for new tickets\" by " +"clicking on the ⁝ action button and select the desired function." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.department}``" +#: ../system/objects.rst:225 +msgid "" +"*Default for new tickets* means that this priority is used for every newly " +"created ticket." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Address" +#: ../system/objects.rst:248 +msgid "Priorities in detail" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.address}``" +#: ../system/objects.rst:229 +msgid "Below you can find a description for each field and option." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created" +#: ../system/objects.rst:232 +msgid "" +"This is the name of the priority and what you and your agents are seeing " +"when choosing a priority somewhere (e.g. in tickets, trigger configuration)." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_at}``" +#: ../system/objects.rst:242 +msgid "Highlight color" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Cc" +#: ../system/objects.rst:237 +msgid "" +"Switch between *Low priority* (light blue), *High priority* (red) and - " +"(default). This affects the displayed color for ticket titles in overviews." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.cc}``" +#: ../system/objects.rst:241 +msgid "The color options are currently limited to the mentioned options." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``jdoe@example.com, company@example.com``" +#: ../system/objects.rst:245 +msgid "" +"You can create a note for the priority to inform other admins about the " +"priority. This has no effect on tickets." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Text" +#: ../system/objects.rst:249 +msgid "Set the priority to *active* or *inactive*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.body}``" +#: ../system/objects/external-data-source-example.rst:2 +msgid "External Data Source" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Test`` without formatting (plain)" +#: ../system/objects/external-data-source-example.rst:4 +msgid "" +"We assume you already had a look on :doc:`types` where you can find a " +"description of the individual fields." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article Text as HTML (not referenced)" +#: ../system/objects/external-data-source-example.rst:7 +msgid "" +"To reproduce this example, choose a category you want to add a custom field, " +"click on *New Attribute* and select *External data source field* under " +"*Format*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.body_as_html}``" +#: ../system/objects/external-data-source-example.rst:11 +msgid "" +"Our example story is to fetch data from an external product database. We " +"want to add our products to the tickets so that the products can be searched " +"and chosen from a list and also create a link to the product website." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Test`` with formatting" +#: ../system/objects/external-data-source-example.rst:16 +msgid "Base configuration" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "Ticket > Article#" +#: ../system/objects/external-data-source-example.rst:None +msgid "Initial steps to configure external data source object type" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "``#{ticket.article_count}``" +#: ../system/objects/external-data-source-example.rst:25 +msgid "Name: *product*" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``1`` number of ticket articles" +#: ../system/objects/external-data-source-example.rst:26 +msgid "Display: *Product*" msgstr "" -#: ../system/variables/config.rst:2 -msgid "Config" +#: ../system/objects/external-data-source-example.rst:29 +msgid "External data source configuration" msgstr "" -#: ../system/variables/config.rst:6 +#: ../system/objects/external-data-source-example.rst:31 msgid "" -"Below you'll find config related variables. These hold useful configuration " -"information that you can use within e.g. triggers to show necessary " -"information to your customer." +"First, enter the search URL making sure it contains ``#{search.term}`` as a " +"parameter:" msgstr "" -#: ../system/variables/config.rst:11 -msgid "Config Variables" +#: ../system/objects/external-data-source-example.rst:34 +msgid "**Example:** ``https://dummyjson.com/products/search?q=#{search.term}``" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Fully Qualified Domain Name" +#: ../system/objects/external-data-source-example.rst:36 +msgid "" +"After that, head down to the preview section and enter a search input for " +"the external data source." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.fqdn}``" +#: ../system/objects/external-data-source-example.rst:39 +msgid "**Example:** ``mac``" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``zammad.example.com``" +#: ../system/objects/external-data-source-example.rst:41 +msgid "Then you can find a preview of the response data below:" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Ticket Hook" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of JSON response based on search term" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.ticket_hook}``" +#: ../system/objects/external-data-source-example.rst:48 +msgid "" +"We recommend using the preview to have a look on the structure. There is a " +"top-level element called ``products``. One level below, you can find the " +"attributes ``id`` and ``title``." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``Ticket#``" +#: ../system/objects/external-data-source-example.rst:52 +msgid "**Search result response based on search from example:**" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > HTTP type" +#: ../system/objects/external-data-source-example.rst:119 +msgid "" +"To tell the remote system that the desired data is located below the " +"``products`` level, you have to put it in the field *Search result list key*." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.http_type}``" +#: ../system/objects/external-data-source-example.rst:122 +msgid "" +"After inserting ``products`` in the mentioned field, you get an extended " +"preview. You can find an additional box *Search result list* with a JSON " +"structure. This is the same response as before but stripped from the upper " +"``products`` element by the external data source." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``https`` or ``http``" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of JSON response search result list" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > SystemID" +#: ../system/objects/external-data-source-example.rst:132 +msgid "" +"Now you need to provide the keys for the search result values and labels. As " +"already mentioned, we are looking for the ``id`` and the ``title`` of our " +"products. If you haven't already, it is now a good time to look at the " +"preview of the *Search result list*." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.system_id}``" +#: ../system/objects/external-data-source-example.rst:197 +msgid "" +"After locating our two keys, we insert them in *search result value key* " +"(``id``) and in *Search result label key* (``title``)." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``31`` (value between 1 and 99)" +#: ../system/objects/external-data-source-example.rst:200 +msgid "" +"Basically, we configured the external data source already and we can see a " +"table in the preview section:" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Organization" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of product table based on search term" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.organization}``" +#: ../system/objects/external-data-source-example.rst:208 +msgid "" +"According to our example story, now just the *Link template* is missing." msgstr "" -#: ../system/variables/config.rst:1 +#: ../system/objects/external-data-source-example.rst:210 msgid "" -"``Zammad GmbH`` value set in `Branding `_" +"Please note that this is an optional feature. If you don't want to use such " +"links, of course you don't have to configure it." msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Product Name" +#: ../system/objects/external-data-source-example.rst:213 +msgid "" +"We can add now an address where additional product information can be found." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.product_name}``" +#: ../system/objects/external-data-source-example.rst:215 +msgid "Example: ``https://your_domain.com/q=#{ticket.product}``" msgstr "" -#: ../system/variables/config.rst:1 -msgid "" -"``Helpdesk`` value set in `Branding `_" +#: ../system/objects/external-data-source-example.rst:217 +msgid "In the example, the parameter means:" +msgstr "" + +#: ../system/objects/external-data-source-example.rst:219 +msgid "``#{}``: \"Frame\" for the insertion of information" msgstr "" -#: ../system/variables/current-user.rst:2 -msgid "Current User" +#: ../system/objects/external-data-source-example.rst:220 +msgid "``ticket``: object level, where you create your custom object" msgstr "" -#: ../system/variables/current-user.rst:6 -msgid "" -"Current user variables always return values of the current user that caused " -"e.g. a trigger to run." +#: ../system/objects/external-data-source-example.rst:221 +msgid "``product``: name of the (custom) object" msgstr "" -#: ../system/variables/current-user.rst:8 +#: ../system/objects/external-data-source-example.rst:223 msgid "" -"Due to the above fact, these variables are often not (yet) set or available " -"for usage." +"After configuring your *Link template*, there will be another column in the " +"preview. Hovering on the icons in the *Link* column will show you where it " +"forwards you." msgstr "" -#: ../system/variables/current-user.rst:10 +#: ../system/objects/external-data-source-example.rst:232 msgid "" -"In situations where e.g. schedulers or triggers run, this most likely is " -"nothing you want to use." -msgstr "" - -#: ../system/variables/current-user.rst:13 -msgid "Current User Variables" +"In our example, one of the links looks like: https://your_domain.com/q=6, " +"where the 6 is the product id." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Web" +#: ../system/objects/external-data-source-example.rst:235 +msgid "You can find more information regarding the URL in :doc:`types`." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.web}``" +#: ../system/objects/includes/adding-values-hint.include.rst:3 +msgid "" +"Adding values can be tricky for first timers, don't forget to press \"➕ " +"Add\" after typing your values. Otherwise you may loose a value." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``https://zammad.org`` or empty if not set" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:1 +#: ../system/objects/includes/reposition-values.include.rst:1 +msgid "**↕️ This field type allows the positioning of its values ↔️**" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > VIP" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:3 +msgid "" +"In order to re-arrange the field values, first edit the field. Then you can " +"use ☰ to drag the values in question to the correct position. If you want to " +"change the layer depth, double click on ☰. With it you can cycle through the " +"available layers." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.vip}``" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:8 +msgid "When you're ready, submit your changes to save the object attribute." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``false`` or ``true``" +#: :0 ../system/objects/types.rst:0 +msgid "" +"Screencast showing how to re-position values on tree select like\n" +"fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Web" +#: ../system/objects/includes/reposition-values.include.rst:3 +msgid "" +"In order to re-arrange the field values, edit the field and scroll below the " +"values. Make sure to tick the option \"Use custom option sort\"." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.web}``" +#: ../system/objects/includes/reposition-values.include.rst:8 +msgid "" +"If you do not tick this field, all manual positioning you did above will be " +"lost upon saving! ☠️" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > VIP" +#: ../system/objects/includes/reposition-values.include.rst:11 +msgid "" +"Now use ☰ to drag the values in question to the correct position. When " +"you're ready, submit your changes to save the object attribute." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.vip}``" +#: :0 ../system/objects/types.rst:0 +msgid "Screencast showing how to re-position values" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Phone" +#: ../system/objects/includes/url-template-hint.include.rst:3 +msgid "" +"This field allows using :ref:`URL fields (Link Templates) `." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.phone}``" +#: ../system/objects/permissions.rst:2 +msgid "Attribute Permissions" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``004930123456789`` or empty if not set" +#: ../system/objects/permissions.rst:7 +msgid "" +"In the object attributes configuration you can define if a field is shown " +"and if the input in the field is mandatory, separated by different screens " +"and for different :doc:`roles/permissions `." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Note" +#: ../system/objects/permissions.rst:17 +msgid "Screenshot shows object attribute permission table" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.note}``" +#: ../system/objects/permissions.rst:17 +msgid "" +"Some of the possible permissions and screen options for a user object " +"attribute." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Some note to this user`` or empty if not set" +#: ../system/objects/permissions.rst:19 +msgid "" +"Based on the object context (ticket, agent, organization, user), the " +"selectable roles (to be precise: the required permissions) and screens " +"differ. Be aware that these settings aren't affecting data creation via " +"other channels than the UI." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Mobile" +#: ../system/objects/permissions.rst:24 +msgid "" +"If you want to have further customization possibilities, you should have a " +"look at the :doc:`core workflows `." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.mobile}``" +#: ../system/objects/permissions.rst:28 +msgid "Screens" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``0049176123456789`` or empty if not set" +#: ../system/objects/permissions.rst:30 +msgid "" +"In the table below you can find an overview about the different permissions " +"and the available screens Zammad distinguishes between." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Login" +#: ../system/objects/permissions.rst:37 +msgid "Screen" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.login}``" +#: ../system/objects/permissions.rst:38 +msgid "Available for" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Lastname" +#: ../system/objects/permissions.rst:40 +msgid "create" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.lastname}``" +#: ../system/objects/permissions.rst:41 ../system/objects/permissions.rst:52 +#: ../system/objects/permissions.rst:59 ../system/objects/permissions.rst:73 +msgid "admin.user" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Firstname" +#: ../system/objects/permissions.rst:42 ../system/objects/permissions.rst:53 +#: ../system/objects/permissions.rst:60 +msgid "admin.organization" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.firstname}``" +#: ../system/objects/permissions.rst:43 ../system/objects/permissions.rst:54 +#: ../system/objects/permissions.rst:61 +msgid "admin.group" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``John`` or empty if not set" +#: ../system/objects/permissions.rst:44 +msgid "Creation dialog for not yet existing data" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Fax" +#: ../system/objects/permissions.rst:45 +msgid "create_middle" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.fax}``" +#: ../system/objects/permissions.rst:46 ../system/objects/permissions.rst:50 +#: ../system/objects/permissions.rst:57 ../system/objects/permissions.rst:66 +#: ../system/objects/permissions.rst:70 +msgid "ticket.customer" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``004930123464789`` or empty if not set" +#: ../system/objects/permissions.rst:47 ../system/objects/permissions.rst:51 +#: ../system/objects/permissions.rst:58 ../system/objects/permissions.rst:69 +msgid "ticket.agent" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Email" +#: ../system/objects/permissions.rst:48 +msgid "Ticket create dialog (middle section)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.email}``" +#: ../system/objects/permissions.rst:49 +msgid "edit" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``jdoe@customer.tld``" +#: ../system/objects/permissions.rst:55 +msgid "Editing dialog for already existing data" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Department" +#: ../system/objects/permissions.rst:56 +msgid "view" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.department}``" +#: ../system/objects/permissions.rst:62 +msgid "View-only dialog for already existing data" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Sales`` or empty if not set" +#: ../system/objects/permissions.rst:64 +msgid "(e.g. user or organization from search)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Avatar" +#: ../system/objects/permissions.rst:65 +msgid "signup" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.avatar(60,60)}``" +#: ../system/objects/permissions.rst:67 +msgid "Sign-up screen for new customers" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "avatar picture with width and height in pixel (e.g. 60,60)" +#: ../system/objects/permissions.rst:68 +msgid "invite_customer" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Address" +#: ../system/objects/permissions.rst:71 +msgid "" +"Customer invitation screen (from :doc:`First Steps ` area)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.address}``" +#: ../system/objects/permissions.rst:72 +msgid "invite_agent" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Some street 1, 12345 Berlin`` or empty if not set" +#: ../system/objects/permissions.rst:74 +msgid "" +"Agent invitation screen (from :doc:`First Steps ` area)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated at" +#: ../system/objects/permissions.rst:78 +msgid "Screen Options" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_at}``" +#: ../system/objects/permissions.rst:80 +msgid "" +"For the different screens you can select \"show\" and \"required\" options." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC``" +#: ../system/objects/permissions.rst:82 +msgid "**shown:** Show (check) or hide (uncheck) a field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Phone" +#: ../system/objects/permissions.rst:83 +msgid "" +"**required:** Set a field to mandatory (check). Forces users (via UI and " +"API) to populate the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.phone}``" +#: ../system/objects/types.rst:7 +msgid "Example external data source" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Shared organization" +#: ../system/objects/types.rst:2 +msgid "Attribute types" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.shared}``" +#: ../system/objects/types.rst:4 +msgid "" +"When adding a new object attribute, you can choose between the following " +"attribute types." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Note" +#: ../system/objects/types.rst:14 +msgid "" +"You cannot change the attribute format / type as soon as it is applied. If " +"you no longer need an object attribute, consider disabling it instead of " +"removing." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.note}``" +#: ../system/objects/types.rst:18 +msgid "**What about the translation of my attributes?**" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``A note to the organization of the user`` or empty if not set" +#: ../system/objects/types.rst:20 +msgid "" +"For some attribute types you can decide if they should be translatable or " +"not. To be precise, it works only for the selectable fields because the " +"possible choices are known and limited. For the following attribute types, " +"you can set the translatable flag:" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Name" +#: ../system/objects/types.rst:25 +msgid "*Boolean field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.name}``" +#: ../system/objects/types.rst:26 +msgid "*Single selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``Zammad GmbH``" +#: ../system/objects/types.rst:27 +msgid "*Multiple selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Domain based assignment" +#: ../system/objects/types.rst:28 +msgid "*Single tree selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.domain_assignment}``" +#: ../system/objects/types.rst:29 +msgid "*Multiple tree selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Domain" +#: ../system/objects/types.rst:31 +msgid "" +"For these types, you can find an additional field *Translate field contents*:" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.domain}``" +#: ../system/objects/types.rst:0 +msgid "Screenshot showing translatable attribute types" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``zammad.com`` or empty if not set" +#: ../system/objects/types.rst:38 +msgid "Screenshot with example of translatable attribute type" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > VIP" +#: ../system/objects/types.rst:45 +msgid "Boolean field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.vip}``" +#: ../system/objects/types.rst:41 +msgid "" +"Provides a drop-down field with display values for ``true`` and ``false``. " +"Setting a default is mandatory." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Note" +#: ../system/objects/types.rst:0 +msgid "Available settings for Boolean fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.note}``" +#: ../system/objects/types.rst:55 +msgid "Date field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Mobile" +#: ../system/objects/types.rst:48 +msgid "Provides a date picker field and does not allow default values." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.mobile}``" +#: ../system/objects/types.rst:52 +msgid "Default time diff (hours)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Login" +#: ../system/objects/types.rst:51 +msgid "" +"This setting helps the user by highlighting the day from now plus the " +"provided value. It *does not* pre-fill the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.login}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Date fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Lastname" +#: ../system/objects/types.rst:73 +msgid "Date & time field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.lastname}``" +#: ../system/objects/types.rst:58 +msgid "Provides a date and time picker – does not allow default values" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Firstname" +#: ../system/objects/types.rst:62 +msgid "Allow future" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.firstname}``" +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the future." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Fax" +#: ../system/objects/types.rst:66 +msgid "Allow past" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.fax}``" +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the past." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Email" +#: ../system/objects/types.rst:70 +msgid "Default time diff (minutes)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.email}``" +#: ../system/objects/types.rst:69 +msgid "" +"This setting helps the user by highlighting the day from now plus the " +"provided value. It does not pre-fill the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Department" +#: ../system/objects/types.rst:0 +msgid "Available settings for Date & time fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.department}``" +#: ../system/objects/types.rst:86 +msgid "Integer field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Web" +#: ../system/objects/types.rst:76 +msgid "" +"Provides an input field that allows integer usage only. You may define a " +"default value. You cannot enforce comma separation." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.web}``" +#: ../system/objects/types.rst:80 +msgid "Minimal" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > VIP" +#: ../system/objects/types.rst:80 +msgid "The minimal value the field accepts." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.vip}``" +#: ../system/objects/types.rst:83 +msgid "Maximal" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Phone" +#: ../system/objects/types.rst:83 +msgid "The maximum value the field accepts." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.phone}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Integer fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Note" +#: ../system/objects/types.rst:99 +msgid "Multiple selection field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.note}``" +#: ../system/objects/types.rst:89 +msgid "" +"Provides a selection field that allows the selection of one or more out of " +"several. This field does allow setting a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Mobile" +#: ../system/objects/types.rst:0 +msgid "Available settings for Multiple selection fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.mobile}``" +#: ../system/objects/types.rst:112 +msgid "Single selection field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Login" +#: ../system/objects/types.rst:102 +msgid "" +"Provides a drop-down field that allows selection of one value out of " +"several. This field does allow setting a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.login}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Single selection fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Lastname" +#: ../system/objects/types.rst:142 +msgid "Textarea field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.lastname}``" +#: ../system/objects/types.rst:115 +msgid "" +"Provides a text area input field (multiple lines) and thus allows e.g. new " +"lines. You can set a default field value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Firstname" +#: ../system/objects/types.rst:120 +msgid "" +"Please note that this field *does not* support text formatting or HTML " +"content (rich text)." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.firstname}``" +#: ../system/objects/types.rst:123 +msgid "**🥵 This field can consume a lot of visual space**" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Fax" +#: ../system/objects/types.rst:125 +msgid "" +"Depending on where you use this field type, it may use a lot of visual space " +"if you provide a lot of text. This may be an issue to work with." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.fax}``" +#: ../system/objects/types.rst:130 +msgid "Default" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Email" +#: ../system/objects/types.rst:129 +msgid "" +"The here provided text will be shown within the text area field or new data " +"sets." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.email}``" +#: ../system/objects/types.rst:134 ../system/objects/types.rst:160 +msgid "Maxlength" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Department" +#: ../system/objects/types.rst:0 ../system/objects/types.rst:160 +msgid "You can pick the maximum length of the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.department}``" +#: ../system/objects/types.rst:0 +msgid "The default length of this object is ``500``." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Avatar" +#: ../system/objects/types.rst:139 +msgid "Rows" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.avatar(60,60)}``" +#: ../system/objects/types.rst:0 +msgid "" +"Change the number of rows to dislay so that you can use only the space you " +"really need." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Address" +#: ../system/objects/types.rst:0 +msgid "The default number of rows is ``4``." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.address}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Textarea fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created at" +#: ../system/objects/types.rst:165 +msgid "Text field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_at}``" +#: ../system/objects/types.rst:145 +msgid "Provides a text field (one line) and allows choosing a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Avatar" +#: ../system/objects/types.rst:148 +msgid "" +"Defines the type of the input field. This allows e.g. your browser to ensure " +"that you provide the specific type." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.avatar(60,60)}``" +#: ../system/objects/types.rst:152 +msgid "Currently available:" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Address" +#: ../system/objects/types.rst:155 +msgid "Phone" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.address}``" +#: ../system/objects/types.rst:156 +msgid "Text" msgstr "" -#: ../system/variables/ticket.rst:6 -msgid "" -"Below you can find all available ticket-based variables within Zammad. These " -"can be called via Triggers for example. If you're unsure if Zammad does " -"support variables at the point you're at, you can try to type ``::`` to " -"check." +#: ../system/objects/types.rst:157 +msgid "Url *(URL fields disable link-template availability)*" msgstr "" -#: ../system/variables/ticket.rst:12 -msgid "Ticket Variables" +#: ../system/objects/types.rst:0 +msgid "Available settings for Text fields" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Web" +#: ../system/objects/types.rst:174 +msgid "Single tree selection field" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.web}``" +#: ../system/objects/types.rst:168 +msgid "" +"Provides a select-like field with up to 6 layers of options. Does not allow " +"setting a default value." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > VIP" +#: ../system/objects/types.rst:0 +msgid "Available settings for Tree Select fields" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.vip}``" +#: ../system/objects/types.rst:183 +msgid "Multiple tree selection field" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Phone" +#: ../system/objects/types.rst:177 +msgid "" +"Provides a select-like field with up to 6 layers of options allowing the " +"selection of multiple values. Does not allow setting a default value." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.phone}``" +#: ../system/objects/types.rst:302 +msgid "External Data Source field" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Note" +#: ../system/objects/types.rst:186 +msgid "" +"Provides a searchable field which fetches data from an external system. This " +"can be useful if you have data outside of Zammad and don't want to maintain " +"both data sources." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.note}``" +#: ../system/objects/types.rst:190 +msgid "The feature works as follows:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Mobile" +#: ../system/objects/types.rst:192 +msgid "" +"Zammad sends a query with a search string (free text from agent or based on " +"a variable) in a pre-defined format (\"Search URL\") to an external system." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.mobile}``" +#: ../system/objects/types.rst:195 +msgid "" +"This external system searches for matches and provides a response as a JSON " +"structure to Zammad." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Login" +#: ../system/objects/types.rst:197 +msgid "" +"Zammad just looks for the defined list and value keys, reads the content and " +"displays the value to the user. There is no search on Zammad side." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.login}``" +#: ../system/objects/types.rst:201 +msgid "" +"The usage of a PostgreSQL database for Zammad is required. In any other " +"case, Zammad will hide the external data source type and you are not able to " +"use it. If you want to use this feature, consider to :docs:`migrate your " +"database `." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Lastname" +#: ../system/objects/types.rst:205 +msgid "Currently, only ``GET`` is supported as request method." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.lastname}``" +#: ../system/objects/types.rst:206 +msgid "" +"The data structure must be in JSON format and provide the objects in an " +"array." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Firstname" +#: ../system/objects/types.rst:208 +msgid "" +"The endpoint for the external data source has to support search. On Zammad " +"side, there is no search/logic implemented; however, you can define the " +"output key and value based on the result(s) from the response (which " +"provides already filtered content based on the search)." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.firstname}``" +#: ../system/objects/types.rst:212 +msgid "" +"If you receive more results as expected, your external data source search " +"may not work properly or the structure of the URL is not correct. You should " +"get in touch with a responsible person from the external system." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Fax" +#: ../system/objects/types.rst:217 +msgid "" +"Please have a look :doc:`at our example `, where you can find a possible configuration for a public " +"dummy endpoint." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.fax}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for external data source fields" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Email" +#: ../system/objects/types.rst:242 +msgid "Search URL" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.email}``" +#: ../system/objects/types.rst:227 +msgid "" +"Set your endpoint where Zammad fetches the data. Please make sure to include " +"a valid search :doc:`variable ` as an URL parameter. " +"Example for a free text search at user input: ``#{search.term}``" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Department" +#: ../system/objects/types.rst:232 +msgid "" +"If in doubt, ask the responsible person for the external data source how " +"they expect the structure of the URL." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.department}``" +#: ../system/objects/types.rst:236 +msgid "" +"Depending on your search variable, the preview might work or not. The reason " +"is that the context might not be available and it is no bug." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Avatar" +#: ../system/objects/types.rst:239 +msgid "" +"Please also make sure to use a variable which is available in your object " +"context. For example you won't be able to search for a ticket in a user " +"object context." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.avatar(60,60)}``" +#: ../system/objects/types.rst:252 +msgid "SSL Verification" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Address" +#: ../system/objects/types.rst:245 +msgid "Here you can switch the SSL verification to no." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.address}``" +#: ../system/objects/types.rst:249 +msgid "" +"If your external data source system is using self signed certificates, " +"please have a look :doc:`here ` for " +"further information about how to handle them in Zammad, so you can keep the " +"SSL verification activated." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated at" +#: ../system/objects/types.rst:258 +msgid "HTTP Authentication" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_at}``" +#: ../system/objects/types.rst:255 +msgid "" +"If your external data source requires an authentication, you can set it " +"here. You can leave it empty or choose between *Basic Authentication* or " +"*Authentication Token* (selecting one of the two methods leads to additional " +"fields where you can enter your credentials/token)." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Title" +#: ../system/objects/types.rst:265 +msgid "Search result list key" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.title}``" +#: ../system/objects/types.rst:261 +msgid "" +"Defines the level in the JSON structure which provides the list with search " +"results. You can leave it empty, if the data is already provided as an " +"array. If you have to go deeper in the structure, you can provide a path " +"with ``.`` as separators, e.g. ``key.subkey.sub-sub-key``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "" -"``My amazing Subject`` (normally subject, can be edited within Interface and " -"thus differ)" +#: ../system/objects/types.rst:271 +msgid "Search result value key" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Accounted Time" +#: ../system/objects/types.rst:268 +msgid "" +"Defines the attribute in the structure in which your external data source " +"provides the *value* for your data. An example would be a product *number*. " +"If you have to go deeper in the structure, you can provide a path with ``.`` " +"as separators, e.g. ``key.subkey.sub-sub-key``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.time_unit}``" +#: ../system/objects/types.rst:277 +msgid "Search result label key" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``1``, ``2.75`` or empty response" +#: ../system/objects/types.rst:274 +msgid "" +"Defines the attribute in the structure in which your external data source " +"provides the *label* for your data. An example would be a product *name*. If " +"you have to go deeper in the structure, you can provide a path with ``.`` as " +"separators, e.g. ``key.subkey.sub-sub-key``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Tags" +#: ../system/objects/types.rst:280 +msgid "" +"In the preview area, you can find the following items (depending on your " +"configuration above):" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.tags}``" +#: ../system/objects/types.rst:283 +msgid "" +"**Error/hint message** (only if configuration is not complete): Zammad tells " +"you, if there is a problem and what you should change in your configuration." msgstr "" -#: ../system/variables/ticket.rst:1 +#: ../system/objects/types.rst:286 msgid "" -"Currently not available, see `Issue 2769 `_" +"**Search field**: search for an existing attribute in the data source to get " +"a preview. This is required for the fields below to show up." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > State > Name" +#: ../system/objects/types.rst:288 +msgid "" +"**Search result response** (only if configuration is not complete): here you " +"can find a syntax highlighted JSON preview of the response, based on the " +"search term you entered." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.state.name}``" +#: ../system/objects/types.rst:291 +msgid "" +"**Search result list** (only if *search result list key* is properly set): " +"output of the structure under the configured *search result list key*." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``new``, ``open``, ..." +#: ../system/objects/types.rst:294 +msgid "" +"**Preview table** (when fully configured): Zammad shows you a table which " +"includes the found items based on the search string (value, label and " +"optional link). You can use this preview if you don't have the complete data " +"structure of the external system in mind." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Priority > Name" +#: ../system/objects/types.rst:299 +msgid "" +"An example of a configured external data source field from agent perspective:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.priority.name}``" +#: ../system/objects/types.rst:0 +msgid "Screencast showing the search for a product in a ticket" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2 normal``" +#: ../system/objects/types.rst:307 +msgid "URL fields (Link-Template)" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Pending till" +#: ../system/objects/types.rst:311 +msgid "" +"This function is restricted to Text, Select and External data source types " +"only." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.pending_time}``" +#: ../system/objects/types.rst:314 +msgid "" +"Link-Templates are an amazing way to dynamically generate URLs. They allow " +"you to integrate other systems better without having to manually copy data " +"from Zammad if possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not set" +#: ../system/objects/types.rst:320 +msgid "" +"Another great way of communicating with another system may be Zammad's :doc:" +"`Webhooks `." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Web" +#: ../system/objects/types.rst:323 +msgid "" +"After filling a link-template enabled field, an URL icon will appear on its " +"right. Clicking on the icon opens a new tab." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.web}``" +#: ../system/objects/types.rst:328 +msgid "" +"Even though Zammad displays the link template within object edit and create " +"screens, the function is optional. It's only active if you populate the " +"field." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``https://zammad.com`` or empty if not set" +#: ../system/objects/types.rst:333 +msgid "" +"What's the difference between URL and text fields with link template...?!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > VIP" +#: ../system/objects/types.rst:335 +msgid "" +"Both fields have different use cases. Use ``text`` type text fields when " +"ever you have a *static* url that requires dynamic parameters. If you " +"require a drag & drop like field that you can put in any URL, use ``URL`` " +"type text fields." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.vip}``" +#: ../system/objects/types.rst:340 +msgid "" +"The difference is easier to spot when comparing the fields directly, below " +"screencast shows the result - the dynamic approach uses existing values in " +"the moment of updating to built the URL - e.g. ``https://google.com/search?" +"q=cookies`` - while the URL approach uses the actual URL of the field - e.g. " +"``https://zammad.com``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Phone" +#: ../system/objects/types.rst:None +msgid "" +"Screencast showing the differents in between URL and text type fields with " +"actual values" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.phone}``" +#: ../system/objects/types.rst:352 +msgid "How does this work...?!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Note" +#: ../system/objects/types.rst:354 +msgid "" +"As an example, let's say you have an attribute called ``amazing_attribute`` " +"and you want to open a google search directly with the input from that field." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.note}``" +#: ../system/objects/types.rst:357 +msgid "" +"Providing the link-template field below allows you to do so: ``https://www." +"google.com/search?q=#{ticket.amazing_attribute}``" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Mobile" +#: ../system/objects/types.rst:362 +msgid "" +"You can use any :doc:`Zammad variable ` as long as it's " +"available in the moment you need it." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.mobile}``" +#: ../system/objects/types.rst:365 +msgid "" +"As a result, you are redirected to Google with a search for the value of the " +"attribute, if you click on the button in the ticket (as you can see in the " +"screencast above)." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Login" +#: ../system/packages.rst:2 +msgid "Packages" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.login}``" +#: ../system/packages.rst:4 +msgid "That's the package management-area." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``agent``" +#: ../system/packages.rst:6 +msgid "Individual add-ons for Zammad can be installed and managed here." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Lastname" +#: ../system/sessions.rst:2 +msgid "Sessions" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.lastname}``" +#: ../system/sessions.rst:4 +msgid "" +"Sessions management allows reviewing currently known user sessions and " +"allows to end these. The session timeout is affected by :ref:" +"`security_session_timeout` configurations from security settings." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Mustermann`` or empty if not set" +#: ../system/sessions.rst:None +msgid "Screenshot showing Zammad's session management" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Firstname" +#: ../system/sessions.rst:13 +msgid "Zammad will provide the following information:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.firstname}``" +#: ../system/sessions.rst:16 +msgid "" +"The user account this session entry belongs to. It can be normal if a user " +"has several sessions in the list. This can be due to changed browser " +"information or if you use e.g. single sign on methods where the user does " +"not use the log off button." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Max`` or empty if not set" +#: ../system/sessions.rst:22 +msgid "Browser" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Fax" +#: ../system/sessions.rst:22 +msgid "The browser agent communicated to Zammad." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.fax}``" +#: ../system/sessions.rst:40 +msgid "Location" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Email" +#: ../system/sessions.rst:25 +msgid "" +"The anticipated location based on the users IP address. Depending on the IP " +"address the result shown may differ. This option depends on :doc:`/settings/" +"system/services`." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.email}``" +#: ../system/sessions.rst:29 +msgid "The following information can be shown:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``agent@company.tld`` or empty if not set" +#: ../system/sessions.rst:33 +msgid "IP address" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Department" +#: ../system/sessions.rst:32 +msgid "" +"Either if you set *Geo IP services* to inactive or you're using internal IP " +"address which do not provide location information." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.department}``" +#: ../system/sessions.rst:40 +msgid "Country (or Country + City)" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Support`` or empty if not set" +#: ../system/sessions.rst:36 +msgid "" +"If *Geo IP services* is enabled only. Depends on how detailed the available " +"IP address information are." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Avatar" +#: ../system/sessions.rst:39 +msgid "" +"Be aware that results can be inaccurate - this technically is not an error." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.avatar(60,60)}``" +#: ../system/sessions.rst:43 +msgid "Age" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Address" +#: ../system/sessions.rst:43 +msgid "Provides the time when the session initially has been created." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.address}``" +#: ../system/sessions.rst:50 +msgid "Update" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Shared organization" +#: ../system/sessions.rst:46 +msgid "" +"Provides the time the user used this session to open Zammad. This timestamp " +"is only updated if the user e.g. reloads, not during normal work on tickets." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.shared}``" +#: ../system/sessions.rst:50 +msgid "This timestamp is being used for the session timeout." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Note" +#: ../system/sessions.rst:53 +msgid "" +"Use the delete button to remove a single session on behalf of your user." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.note}``" +#: ../system/subscription.rst:2 +msgid "Subscription (SaaS)" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Name" +#: ../system/subscription.rst:4 +msgid "" +"The subscription settings page allows you to configure your instances " +"package and number of agents required." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.name}``" +#: ../system/subscription.rst:9 +msgid "" +"This setting section is only available for Hosted setups. If you're looking " +"for on premise support contracts, please see the `Zammad pricing page " +"`_." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Zammad GmbH`` or empty if not set" +#: ../system/subscription.rst:14 ../system/subscription.rst:34 +msgid "Plan" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Domain based assignment" +#: ../system/subscription.rst:16 +msgid "" +"Here you can set up everything affecting your instance subscription " +"functions like number of agents and package." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.domain_assignment}``" +#: ../system/subscription.rst:19 +msgid "" +"On top of the page you can find a subscription summary. You'll find the " +"number of used and available (booked) agent seats there. By using the *see " +"more* link you can also expand an agent list to see the currently configured " +"active agents. This list *does not* count accounts with admin permissions " +"only." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Domain" +#: ../system/subscription.rst:None +msgid "" +"Within subscription you can always see how many agents are still\n" +"available to add and who uses the seats." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.domain}``" +#: ../system/subscription.rst:29 +msgid "" +"Learn more on how to manage your agents in general :doc:`here `." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``domain.tld`` or empty if not set" +#: ../system/subscription.rst:36 +msgid "" +"This section gives you an overview of the available plans and their " +"functions / limits. If you require a more detailed table, check our " +"`detailed pricing table `_ for more." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > VIP" +#: ../system/subscription.rst:40 +msgid "" +"Your selection in this step will decide on the base agent price and e.g. " +"agent limits that might apply in the summary step." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.vip}``" +#: ../system/subscription.rst:43 +msgid "" +"The green *Selected* button will also tell you what plan you're currently in." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Number" +#: ../system/subscription.rst:47 +msgid "" +"Trial instances are running at Professional with 3 agents. The plan cannot " +"be changed during the trial for technical reasons, if you require more " +"agents for testing, please contact `our sales team `_ with a reason for the raise request." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.number}``" +#: ../system/subscription.rst:None +msgid "" +"Screenshot showing three available packages for a hosted Zammad\n" +"instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``31001``, ``201910731001``, ..." +#: ../system/subscription.rst:57 +msgid "" +"At the bottom of this block you can find a summary where you can adjust the " +"settings of the previous selected plan." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > ID" +#: ../system/subscription.rst:62 +msgid "" +"Note that upgrading (more agents, higher package) is always possible, " +"however, downgrading will only happen when your billing period renews." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.id}``" +#: ../system/subscription.rst:66 +msgid "" +"Upgrading resets your billing period and existing credit will be deducted " +"from the new total." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``17``, ``5281``, ..." +#: ../system/subscription.rst:75 +msgid "Billing cycle" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact (customer)" +#: ../system/subscription.rst:70 +msgid "" +"You can choose between either monthly or yearly billing. The price per agent " +"will be cheaper if you decide for yearly billing." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_customer_at}``" +#: ../system/subscription.rst:73 +msgid "" +"If you're still trying out things and are unsure of the right package for " +"your instance, you may want to choose monthly first and then upgrade to " +"yearly when you're sure." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "" -"``2019-10-07 16:25:00 UTC`` or empty if not applicable yet (Please note " -"`Ticket last contact behavior Settings `_ for this)" +#: ../system/subscription.rst:83 +msgid "Plan: (Starter|Professional|Plus) - Agents" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact" +#: ../system/subscription.rst:78 +msgid "Choose the number of agents you require for your instance." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_at}``" +#: ../system/subscription.rst:80 +msgid "" +"Keep in mind that some packages may have agent limits. Depending on the " +"previous chosen package, you won't be able to exceed specific agent numbers. " +"Also note that setting less agents than currently configured is not possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact (agent)" +#: ../system/subscription.rst:86 +msgid "Total" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_agent_at}``" +#: ../system/subscription.rst:86 +msgid "This will be the net total you're going to be billed." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable yet" +#: ../system/subscription.rst:88 +msgid "" +"By using the *Update subscription* button, the instance package will be " +"adjusted immediately. If you didn't provide a payment method yet, Zammad " +"will request you to provide one at this point." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Note" +#: ../system/subscription.rst:94 +msgid "" +"In case you're still within the trial period, this means that the trial will " +"be over immediately!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.note}``" +#: ../system/subscription.rst:97 +msgid "Down- or upgrading during the trial period *is not* possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Note about this group``" +#: ../system/subscription.rst:None +msgid "Screenshot showing payment options and a pricing summary" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Name" +#: ../system/subscription.rst:103 +msgid "Billing Information" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.name}``" +#: ../system/subscription.rst:105 +msgid "" +"You can control all billing relevant information like invoices, billing " +"address and the option to cancel your subscription." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Sales``" +#: ../system/subscription.rst:108 +msgid "" +"All adjusted billing information below only affect future invoices. If your " +"invoice was issued wrong, please contact `our sales team `_." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Follow-up possible" +#: ../system/subscription.rst:114 +msgid "Billing address" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.follow_up_possible}``" +#: ../system/subscription.rst:113 +msgid "" +"Provide your company address here, make sure to include the companies name " +"in case required. This address will be referenced on your invoice." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``no`` or ``yes``" +#: ../system/subscription.rst:118 +msgid "VAT ID" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Assign Follow-Ups" +#: ../system/subscription.rst:117 +msgid "" +"Provide your VAT ID here. If applicable your invoice will not contain German " +"VAT. Please make sure to pay the VAT in your country as required." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.follow_up_assignment}``" +#: ../system/subscription.rst:127 +msgid "Billing Email Address" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Assignment Timeout" +#: ../system/subscription.rst:121 +msgid "" +"Usually the instance owner (the person that registered the instance) will " +"receive all emails including the invoices. In case you have your own billing " +"department, you can provide their email address here." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.assignment_timeout}``" +#: ../system/subscription.rst:125 +msgid "" +"All billing relevant information will then be sent to this email address." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``20`` or empty if not configured" +#: ../system/subscription.rst:127 +msgid "Invoices are sent as attachment (PDF) to this email address." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > First response" +#: ../system/subscription.rst:129 +msgid "" +"Don't forget to press the *Update billing information* button after you " +"changed above settings." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.first_response_at}``" +#: ../system/subscription.rst:None +msgid "" +"Screenshot showing options for billing information within the\n" +"subscription menu" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Escalation at" +#: ../system/subscription.rst:137 +msgid "Payment Method" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.escalation_at}``" +#: ../system/subscription.rst:139 +msgid "You can pay via credit card or SEPA mandate." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable" +#: ../system/subscription.rst:144 +msgid "Credit card" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Web" +#: ../system/subscription.rst:142 +msgid "" +"Simply follow the dialogue by clicking *authorize credit card* and confirm -" +"if required by your bank- your consent to Zammad using your card for the " +"payments." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.web}``" +#: ../system/subscription.rst:148 +msgid "SEPA Direct Debit" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > VIP" +#: ../system/subscription.rst:147 +msgid "" +"Provide the requested information of the bank account holder and update if " +"you're ready. You'll then receive an email with the SEPA mandate." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.vip}``" +#: ../system/subscription.rst:150 +msgid "" +"Technically there's also the possibility to pay via invoice, however - this " +"method only applies to a fairly low number of instances. Please contact `our " +"sales team `_ for more information." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Phone" +#: ../system/subscription.rst:156 +msgid "Cancel Subscription" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.phone}``" +#: ../system/subscription.rst:158 +msgid "" +"Do you want to cancel your subscription? In case you no longer want to use " +"Zammad's SaaS, you can cancel your subscription by using the red *Yes, " +"please cancel my subscription* button." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Note" +#: ../system/subscription.rst:162 +msgid "" +"To cancel the description, enter the FQDN of your Zammad instance and " +"provide a reason for your cancellation." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.note}``" +#: ../system/subscription.rst:165 +msgid "" +"Your subscription will end the day after your trial or billing period ends." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Mobile" +#: ../system/subscription.rst:None +msgid "Screenshot showing subscription cancellation dialog" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.mobile}``" +#: ../system/subscription.rst:174 +msgid "" +"We will remind you about your cancelled subscription several times up front. " +"After the subscription ended all instance data will be removed. A restore " +"*is not* possible after that point!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Login" +#: ../system/subscription.rst:178 +msgid "**😖 Cancelled by accident?**" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.login}``" +#: ../system/subscription.rst:180 +msgid "" +"You can always undo the cancellation via the *Yes, undo the cancellation of " +"my subscription* button up to the last subscription day!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Lastname" +#: ../system/subscription.rst:0 +msgid "" +"Screenshot showing a red button to cancel the subscription\n" +"cancellation" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.lastname}``" +#: ../system/subscription.rst:189 +msgid "Payment History" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Firstname" +#: ../system/subscription.rst:191 +msgid "" +"The payment history will display a history of all paid invoices. At this " +"point you can also download these in case you need them again." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.firstname}``" +#: ../system/subscription.rst:196 +msgid "" +"You will only find *paid* invoices here. Invoices that are to be billed are " +"not available before the payment is completed." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Fax" +#: ../system/subscription.rst:201 +msgid "Date" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.fax}``" +#: ../system/subscription.rst:201 +msgid "Date of the invoice creation." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Email" +#: ../system/subscription.rst:204 +msgid "Amount" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.email}``" +#: ../system/subscription.rst:204 +msgid "Invoice total including VAT if applicable." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Department" +#: ../system/subscription.rst:207 +msgid "" +"Contains contract period (monthly or yearly) and hosted plan for the " +"subscription period in question." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.department}``" +#: ../system/subscription.rst:218 +msgid "Payment method / Service period" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Avatar" +#: ../system/subscription.rst:211 +msgid "" +"Used bank account or credit card as well as the subscription period the " +"invoice is about." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.avatar(60,60)}``" +#: ../system/subscription.rst:216 +msgid "" +"It might happen that the invoice date and subscription period differ. This " +"is nothing to worry about, the subscription periods will be accounted later " +"on." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Address" +#: ../system/subscription.rst:222 +msgid "Receipt" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.address}``" +#: ../system/subscription.rst:221 +msgid "" +"Use the arrow to download the invoice in question. You can download all " +"available invoices any time you need to here!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Web" +#: ../system/subscription.rst:None +msgid "Screenshot showing payment history of a hosted instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.web}``" +#: ../system/subscription.rst:229 +msgid "FAQ" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > VIP" +#: ../system/subscription.rst:233 +msgid "I set up a trial account but am missing functions to test" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.vip}``" +#: ../system/subscription.rst:232 +msgid "" +"The trial instance is running within the professional package allowing up to " +"three agents." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Phone" +#: ../system/subscription.rst:236 +msgid "Can I change package within the trial?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.phone}``" +#: ../system/subscription.rst:236 +msgid "No. As soon as the package is changed the subscription begins." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Note" +#: ../system/subscription.rst:241 +msgid "What happens to my trial instance after the trial period ended?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.note}``" +#: ../system/subscription.rst:239 +msgid "" +"Your instance will automatically be canceled for you. Please see *What " +"happens to my instance after it has been canceled?* for more." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Mobile" +#: ../system/subscription.rst:254 +msgid "What happens to my instance after it has been canceled?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.mobile}``" +#: ../system/subscription.rst:244 +msgid "That depends slightly on your instance state:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Login" +#: ../system/subscription.rst:250 +msgid "Trial instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.login}``" +#: ../system/subscription.rst:247 +msgid "" +"If you're still on trial, we will ice your instance and remind you once " +"again about your instance. We then will wait some days and remove your " +"instance from our system. This is the last time we will inform you by Email." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Lastname" +#: ../system/subscription.rst:254 +msgid "Paid instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.lastname}``" +#: ../system/subscription.rst:253 +msgid "" +"If you're a paying customer and canceled your subscription, the instance " +"removal will take place the day after your last subscription day." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Firstname" +#: ../system/subscription.rst:256 +msgid "Can removed instances be restored?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.firstname}``" +#: ../system/subscription.rst:257 +msgid "No. Once your instance has been removed, a restoration is not possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Fax" +#: ../system/system-report.rst:2 +msgid "System Report" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.fax}``" +#: ../system/system-report.rst:4 +msgid "" +"In this place you can't configure Zammad. Instead you can obtain a system " +"report about Zammad and its configuration." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Email" +#: ../system/system-report.rst:7 +msgid "" +"See the description in Zammad for an explanation. You can even find a " +"preview of the included data below the **Download** button." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.email}``" +#: ../system/system-report.rst:10 +msgid "" +"Zammad never sends this automatically to anyone. It is a manual process only " +"to provide better support based on your configuration." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Department" +#: ../system/translations.rst:2 +msgid "Translations" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.department}``" +#: ../system/translations.rst:4 +msgid "" +"Translations of Zammad are processed centrally in our `Weblate instance " +"`_. This allows non-developers to review " +"and update translation texts of the language they actually speak." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Avatar" +#: ../system/translations.rst:9 +msgid "" +"Your language is in an incomplete translation state or has typos? Please " +"consider helping us in sorting this out! All you need is either a GitHub " +"account or to register directly in our instance." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.avatar(60,60)}``" +#: ../system/translations.rst:13 +msgid "" +"Did you know? This is also where the documentation translations are handled. " +"🤓" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Address" +#: ../system/translations.rst:15 +msgid "" +"Have a look in our :docs:`contribution section ` in the system documentation to get started!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.address}``" +#: ../system/translations.rst:20 +msgid "Local Translations" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created at" +#: ../system/translations.rst:22 +msgid "" +"Apart from these system translations, there's still local translations you " +"can manage. This is relevant if you added custom objects that require " +"translations or even custom states and priorities." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_at}``" +#: ../system/translations.rst:None +msgid "Translation management screen within the admin menu" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "2019-10-07 16:25:00 UTC" +#: ../system/translations.rst:31 +msgid "Updating Translations" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Closing time" +#: ../system/translations.rst:33 +msgid "" +"Because of how Zammad ships translations, the only way to update the system " +"translations is to update your Zammad installation. The benefit of this is " +"that you no longer need internet access during a Zammad upgrade as the " +"package has everything it requires already." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.close_at}``" +#: ../system/translations.rst:39 +msgid "Translation of Custom Objects" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "2019-10-07 17:25:00 UTC" +#: ../system/translations.rst:41 +msgid "" +"No problem at all! You can customize any translation locally, even if it is " +"not initially provided by the system." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``3``, any number of articles existing in the ticket right now" +#: ../system/translations.rst:44 +msgid "" +"Translation is supported for a broad number of features, including but not " +"limited to custom:" msgstr "" -#: ../system/version.rst:2 -msgid "Version" +#: ../system/translations.rst:47 +msgid "Object Attributes" msgstr "" -#: ../system/version.rst:4 -msgid "Shows which version is currently being used on your Zammad-instance." +#: ../system/translations.rst:48 +msgid "Ticket Macros" msgstr "" -#: ../manage/roles/admin-permissions.rst:53 -msgid "``admin.checklist``" +#: ../system/translations.rst:49 +msgid "Ticket Overviews" msgstr "" -#: ../manage/roles/admin-permissions.rst:54 -msgid ":doc:`Manage > Checklist `" +#: ../system/translations.rst:50 +msgid "Ticket Priorities" msgstr "" -#: ../manage/roles/admin-permissions.rst:83 -msgid "``admin.channel_whatsapp``" +#: ../system/translations.rst:51 +msgid "Ticket States" msgstr "" -#: ../manage/roles/admin-permissions.rst:84 -msgid ":doc:`Channels > Whatsapp `" +#: ../system/translations.rst:54 +msgid "Customizing Translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:124 -msgid "``admin.public_links``" +#: ../system/translations.rst:56 +msgid "" +"Within the translation screen, simply click on the **New Translation** " +"button." msgstr "" -#: ../manage/roles/admin-permissions.rst:125 -msgid ":doc:`Manage > Public Links `" +#: ../system/translations.rst:None +msgid "New translation dialog" msgstr "" -#: ../manage/roles/admin-permissions.rst:151 -msgid "``admin.system_report``" +#: ../system/translations.rst:62 +msgid "" +"In the dialog you can immediately enter the exact translation source (if you " +"know it) and your custom translation text for it and click **Submit**." msgstr "" -#: ../manage/roles/admin-permissions.rst:152 -msgid ":doc:`System > System Report `" +#: ../system/translations.rst:65 +msgid "" +"Alternatively, try to search for translation suggestions in the list below. " +"Selecting an item from the list will pre-fill the translation source for you " +"and then you can just enter your custom translation." msgstr "" -#: ../manage/roles/admin-permissions.rst:166 -msgid "``admin.ticket_auto_assignment``" +#: ../system/translations.rst:69 +msgid "" +"The target language will always default to your current language selection. " +"If you need to translate for a different language, simply change the " +"selection before submitting." msgstr "" -#: ../manage/roles/admin-permissions.rst:167 -msgid ":ref:`Settings > Ticket > Auto Assignment `" +#: ../system/translations.rst:73 +msgid "" +"All your custom translations will show up in the overview table when added. " +"And they will even persist across Zammad updates!" msgstr "" -#: ../manage/roles/admin-permissions.rst:169 -msgid "``admin.ticket_duplicate_detection``" +#: ../system/translations.rst:76 +msgid "" +"Make sure to reload your browser if a translated string is not displayed." msgstr "" -#: ../manage/roles/admin-permissions.rst:170 -msgid ":ref:`Settings > Ticket > Duplicate Detection `" +#: ../system/translations.rst:80 +msgid "Reverting to Original Translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:172 -msgid "``admin.ticket_priority``" +#: ../system/translations.rst:82 +msgid "" +"If you want to revert a custom translation to original text, simply use the " +"appropriate action within the row of the overview table." msgstr "" -#: ../manage/roles/admin-permissions.rst:173 -msgid ":ref:`System > Objects >Ticket Priority `" +#: ../system/translations.rst:85 +msgid "" +"Depending on the type of the translation source, the action has a slightly " +"different name:" msgstr "" -#: ../manage/roles/admin-permissions.rst:175 -msgid "``admin.ticket_state``" +#: ../system/translations.rst:88 +msgid "**Reset** for customized system translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:176 -msgid ":ref:`System > Objects >Ticket State `" +#: ../system/translations.rst:89 +msgid "**Remove** for customized local translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:193 -msgid "``admin.webhook``" +#: ../system/translations.rst:91 +msgid "" +"In both cases, the action will remove the customized translation after a " +"confirmation." msgstr "" -#: ../manage/roles/admin-permissions.rst:194 -msgid ":doc:`Manage > Webhook `" +#: ../system/translations.rst:None +msgid "Screenshot showing the location of the Remove action" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:43 -msgid "``user_preferences.appearance``" +#: ../system/translations.rst:99 +msgid "Inline Translations" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:44 -msgid "Appearance configuration" +#: ../system/translations.rst:101 +msgid "" +"If you prefer a more hands-on approach, you can activate the inline or on-" +"screen translation feature by pressing ``ctrl`` + ``alt`` + ``t`` at any " +"time and on any screen." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:0 -msgid "Users can switch between dark, light and" +#: ../system/translations.rst:105 +msgid "" +"All customizable translation texts will be highlighted for you on the " +"screen. Just click into the highlighted area and update the text in place." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:0 -msgid "automatic mode." +#: ../system/translations.rst:None +msgid "Inline translation mode activated for the Overview screen" msgstr "" -#: ../system/system-report.rst:2 -msgid "System Report" +#: ../system/translations.rst:112 +msgid "" +"When finished editing, simply press ``ctrl`` + ``alt`` + ``t`` again to " +"deactivate." msgstr "" -#: ../system/system-report.rst:4 +#: ../system/translations.rst:117 msgid "" -"In this place you can't configure Zammad. Instead you can obtain a system " -"report about Zammad and its configuration." +"Even though it's available on any screen, the inline translation feature " +"requires admin permissions. It works only for the current language " +"selection. If you need to translate a different language, first change the " +"language in your :user-docs:`profile settings `." msgstr "" -#: ../system/system-report.rst:7 -msgid "" -"See the description in Zammad for an explanation. You can even find a " -"preview of the included data below the **Download** button." +#: ../system/version.rst:2 +msgid "Version" msgstr "" -#: ../system/system-report.rst:10 -msgid "" -"Zammad never sends this automatically to anyone. It is a manual process only " -"to provide better support based on your configuration." +#: ../system/version.rst:4 +msgid "Shows which version is currently being used on your Zammad-instance." msgstr "" diff --git a/locale/es_MX/LC_MESSAGES/admin-docs.po b/locale/es_MX/LC_MESSAGES/admin-docs.po index 260de3df..6a36694a 100644 --- a/locale/es_MX/LC_MESSAGES/admin-docs.po +++ b/locale/es_MX/LC_MESSAGES/admin-docs.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Zammad\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-11-06 10:31+0100\n" +"POT-Creation-Date: 2024-11-12 16:31+0100\n" "PO-Revision-Date: 2023-10-11 14:18+0000\n" "Last-Translator: morealedgar \n" "Language-Team: Spanish (Mexico) Checklist `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:56 msgid "``admin.channel_email``" msgstr "" -#: ../manage/roles/admin-permissions.rst:54 #: ../manage/roles/admin-permissions.rst:57 msgid ":doc:`Channels > Email `" msgstr "" -#: ../manage/roles/admin-permissions.rst:56 #: ../manage/roles/admin-permissions.rst:59 msgid "``admin.channel_facebook``" msgstr "" -#: ../manage/roles/admin-permissions.rst:57 #: ../manage/roles/admin-permissions.rst:60 msgid ":doc:`Channels > Facebook `" msgstr "" -#: ../manage/roles/admin-permissions.rst:58 #: ../manage/roles/admin-permissions.rst:61 msgid "" "Accessing Facebook tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:59 #: ../manage/roles/admin-permissions.rst:62 msgid "``admin.channel_formular``" msgstr "" -#: ../manage/roles/admin-permissions.rst:60 #: ../manage/roles/admin-permissions.rst:63 msgid ":doc:`Channels > Form `" msgstr "" -#: ../manage/roles/admin-permissions.rst:62 #: ../manage/roles/admin-permissions.rst:65 msgid "``admin.channel_google``" msgstr "" -#: ../manage/roles/admin-permissions.rst:63 #: ../manage/roles/admin-permissions.rst:66 msgid ":doc:`Channels > Google `" msgstr "" -#: ../manage/roles/admin-permissions.rst:65 #: ../manage/roles/admin-permissions.rst:68 msgid "``admin.channel_microsoft365``" msgstr "" -#: ../manage/roles/admin-permissions.rst:66 #: ../manage/roles/admin-permissions.rst:69 msgid ":doc:`Channels > Microsoft 365 `" msgstr "" -#: ../manage/roles/admin-permissions.rst:68 #: ../manage/roles/admin-permissions.rst:71 msgid "``admin.channel_sms``" msgstr "" -#: ../manage/roles/admin-permissions.rst:69 #: ../manage/roles/admin-permissions.rst:72 msgid ":doc:`Channels > SMS `" msgstr "" -#: ../manage/roles/admin-permissions.rst:71 #: ../manage/roles/admin-permissions.rst:74 msgid "``admin.channel_telegram``" msgstr "" -#: ../manage/roles/admin-permissions.rst:72 #: ../manage/roles/admin-permissions.rst:75 msgid ":doc:`Channels > Telegram `" msgstr "" -#: ../manage/roles/admin-permissions.rst:73 #: ../manage/roles/admin-permissions.rst:76 msgid "" "Accessing Telegram tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:74 #: ../manage/roles/admin-permissions.rst:77 msgid "``admin.channel_twitter``" msgstr "" -#: ../manage/roles/admin-permissions.rst:75 #: ../manage/roles/admin-permissions.rst:78 msgid ":doc:`Channels > Twitter `" msgstr "" -#: ../manage/roles/admin-permissions.rst:76 #: ../manage/roles/admin-permissions.rst:79 msgid "" "Accessing Twitter/X tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:77 #: ../manage/roles/admin-permissions.rst:80 msgid "``admin.channel_web``" msgstr "" -#: ../manage/roles/admin-permissions.rst:78 #: ../manage/roles/admin-permissions.rst:81 msgid ":doc:`Channels > Web `" msgstr "" -#: ../manage/roles/admin-permissions.rst:80 +#: ../manage/roles/admin-permissions.rst:83 +msgid "``admin.channel_whatsapp``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:84 +msgid ":doc:`Channels > Whatsapp `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:86 msgid "``admin.core_workflows``" msgstr "" -#: ../manage/roles/admin-permissions.rst:81 #: ../manage/roles/admin-permissions.rst:87 msgid ":doc:`System > Core Workflows `" msgstr "" -#: ../manage/roles/admin-permissions.rst:83 #: ../manage/roles/admin-permissions.rst:89 msgid "``admin.data_privacy``" msgstr "" -#: ../manage/roles/admin-permissions.rst:84 #: ../manage/roles/admin-permissions.rst:90 msgid ":doc:`System > Data Privacy `" msgstr "" -#: ../manage/roles/admin-permissions.rst:85 #: ../manage/roles/admin-permissions.rst:91 msgid "" "🔥 Be careful, it allows users to permanently delete data on the system." msgstr "" -#: ../manage/roles/admin-permissions.rst:86 #: ../manage/roles/admin-permissions.rst:92 msgid "``admin.group``" msgstr "" -#: ../manage/roles/admin-permissions.rst:87 #: ../manage/roles/admin-permissions.rst:93 msgid ":doc:`Manage > Groups `" msgstr "" -#: ../manage/roles/admin-permissions.rst:89 #: ../manage/roles/admin-permissions.rst:95 msgid "``admin.integration``" msgstr "" -#: ../manage/roles/admin-permissions.rst:90 #: ../manage/roles/admin-permissions.rst:96 msgid ":doc:`System > Integrations `" msgstr "" -#: ../manage/roles/admin-permissions.rst:92 #: ../manage/roles/admin-permissions.rst:98 msgid "``admin.knowledge_base``" msgstr "" -#: ../manage/roles/admin-permissions.rst:93 #: ../manage/roles/admin-permissions.rst:99 msgid ":doc:`Manage > Knowledge Base `" msgstr "" @@ -8552,57 +8535,46 @@ msgid "" "knowledge-base.html#editing-answers>`." msgstr "" -#: ../manage/roles/admin-permissions.rst:98 #: ../manage/roles/admin-permissions.rst:104 msgid "``admin.macro``" msgstr "" -#: ../manage/roles/admin-permissions.rst:99 #: ../manage/roles/admin-permissions.rst:105 msgid ":doc:`Manage > Macros `" msgstr "" -#: ../manage/roles/admin-permissions.rst:100 #: ../manage/roles/admin-permissions.rst:106 msgid "In some cases, macros may also require ``admin.tag``" msgstr "" -#: ../manage/roles/admin-permissions.rst:101 #: ../manage/roles/admin-permissions.rst:107 msgid "``admin.maintenance``" msgstr "" -#: ../manage/roles/admin-permissions.rst:102 #: ../manage/roles/admin-permissions.rst:108 msgid ":doc:`System > Maintenance `" msgstr "" -#: ../manage/roles/admin-permissions.rst:104 #: ../manage/roles/admin-permissions.rst:110 msgid "``admin.monitoring``" msgstr "" -#: ../manage/roles/admin-permissions.rst:105 #: ../manage/roles/admin-permissions.rst:111 msgid ":doc:`System > Monitoring `" msgstr "" -#: ../manage/roles/admin-permissions.rst:107 #: ../manage/roles/admin-permissions.rst:113 msgid "``admin.object``" msgstr "" -#: ../manage/roles/admin-permissions.rst:108 #: ../manage/roles/admin-permissions.rst:114 msgid ":doc:`System > Objects `" msgstr "" -#: ../manage/roles/admin-permissions.rst:110 #: ../manage/roles/admin-permissions.rst:116 msgid "``admin.organization``" msgstr "" -#: ../manage/roles/admin-permissions.rst:111 #: ../manage/roles/admin-permissions.rst:117 msgid ":doc:`Manage > Organizations `" msgstr "" @@ -8619,202 +8591,210 @@ msgstr "" msgid "They can even edit an organization's name, domain, and notes!" msgstr "" -#: ../manage/roles/admin-permissions.rst:115 #: ../manage/roles/admin-permissions.rst:121 msgid "``admin.overview``" msgstr "" -#: ../manage/roles/admin-permissions.rst:116 #: ../manage/roles/admin-permissions.rst:122 msgid ":doc:`Manage > Overviews`" msgstr "" -#: ../manage/roles/admin-permissions.rst:118 +#: ../manage/roles/admin-permissions.rst:124 +msgid "``admin.public_links``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:125 +msgid ":doc:`Manage > Public Links `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:127 msgid "``admin.package``" msgstr "" -#: ../manage/roles/admin-permissions.rst:119 #: ../manage/roles/admin-permissions.rst:128 msgid ":doc:`System > Packages `" msgstr "" -#: ../manage/roles/admin-permissions.rst:121 #: ../manage/roles/admin-permissions.rst:130 msgid "``admin.report_profile``" msgstr "" -#: ../manage/roles/admin-permissions.rst:122 #: ../manage/roles/admin-permissions.rst:131 msgid ":doc:`Manage > Report Profiles `" msgstr "" -#: ../manage/roles/admin-permissions.rst:123 #: ../manage/roles/admin-permissions.rst:132 msgid "Access to view reports: ``report``" msgstr "" -#: ../manage/roles/admin-permissions.rst:124 #: ../manage/roles/admin-permissions.rst:133 msgid "``admin.role``" msgstr "" -#: ../manage/roles/admin-permissions.rst:125 #: ../manage/roles/admin-permissions.rst:134 msgid ":doc:`Manage > Roles `" msgstr "" -#: ../manage/roles/admin-permissions.rst:127 #: ../manage/roles/admin-permissions.rst:136 msgid "``admin.scheduler``" msgstr "" -#: ../manage/roles/admin-permissions.rst:128 #: ../manage/roles/admin-permissions.rst:137 msgid ":doc:`Manage > Scheduler `" msgstr "" -#: ../manage/roles/admin-permissions.rst:129 #: ../manage/roles/admin-permissions.rst:138 msgid "For automation on tickets" msgstr "" -#: ../manage/roles/admin-permissions.rst:130 #: ../manage/roles/admin-permissions.rst:139 msgid "``admin.security``" msgstr "" -#: ../manage/roles/admin-permissions.rst:131 #: ../manage/roles/admin-permissions.rst:140 msgid ":doc:`Settings > Security `" msgstr "" -#: ../manage/roles/admin-permissions.rst:132 #: ../manage/roles/admin-permissions.rst:141 msgid "Settings of Zammad. This also covers third party authentications." msgstr "" -#: ../manage/roles/admin-permissions.rst:133 #: ../manage/roles/admin-permissions.rst:142 msgid "``admin.session``" msgstr "" -#: ../manage/roles/admin-permissions.rst:134 #: ../manage/roles/admin-permissions.rst:143 msgid ":doc:`System > Sessions `" msgstr "" -#: ../manage/roles/admin-permissions.rst:136 #: ../manage/roles/admin-permissions.rst:145 msgid "``admin.setting_system``" msgstr "" -#: ../manage/roles/admin-permissions.rst:137 #: ../manage/roles/admin-permissions.rst:146 msgid ":doc:`Settings > System `" msgstr "" -#: ../manage/roles/admin-permissions.rst:139 #: ../manage/roles/admin-permissions.rst:148 msgid "``admin.sla``" msgstr "" -#: ../manage/roles/admin-permissions.rst:140 #: ../manage/roles/admin-permissions.rst:149 msgid ":doc:`Manage > SLAs `" msgstr "" -#: ../manage/roles/admin-permissions.rst:142 +#: ../manage/roles/admin-permissions.rst:151 +msgid "``admin.system_report``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:152 +msgid ":doc:`System > System Report `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:154 msgid "``admin.tag``" msgstr "" -#: ../manage/roles/admin-permissions.rst:143 #: ../manage/roles/admin-permissions.rst:155 msgid ":doc:`Manage > Tags `" msgstr "" -#: ../manage/roles/admin-permissions.rst:145 #: ../manage/roles/admin-permissions.rst:157 msgid "``admin.template``" msgstr "" -#: ../manage/roles/admin-permissions.rst:146 #: ../manage/roles/admin-permissions.rst:158 msgid ":doc:`Manage > Templates `" msgstr "" -#: ../manage/roles/admin-permissions.rst:148 #: ../manage/roles/admin-permissions.rst:160 msgid "``admin.text_module``" msgstr "" -#: ../manage/roles/admin-permissions.rst:149 #: ../manage/roles/admin-permissions.rst:161 msgid ":doc:`Manage > Text Modules `" msgstr "" -#: ../manage/roles/admin-permissions.rst:151 #: ../manage/roles/admin-permissions.rst:163 msgid "``admin.ticket``" msgstr "" -#: ../manage/roles/admin-permissions.rst:152 #: ../manage/roles/admin-permissions.rst:164 msgid ":doc:`Settings > Tickets `" msgstr "" -#: ../manage/roles/admin-permissions.rst:153 #: ../manage/roles/admin-permissions.rst:165 msgid "Does not grant access to :doc:`/misc/composer`" msgstr "" -#: ../manage/roles/admin-permissions.rst:154 +#: ../manage/roles/admin-permissions.rst:166 +msgid "``admin.ticket_auto_assignment``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:167 +msgid ":ref:`Settings > Ticket > Auto Assignment `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:169 +msgid "``admin.ticket_duplicate_detection``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:170 +msgid ":ref:`Settings > Ticket > Duplicate Detection `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:172 +msgid "``admin.ticket_priority``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:173 +msgid ":ref:`System > Objects >Ticket Priority `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:175 +msgid "``admin.ticket_state``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:176 +msgid ":ref:`System > Objects >Ticket State `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:178 msgid "``admin.time_accounting``" msgstr "" -#: ../manage/roles/admin-permissions.rst:155 #: ../manage/roles/admin-permissions.rst:179 msgid ":doc:`Manage > Time Accounting `" msgstr "" -#: ../manage/roles/admin-permissions.rst:156 #: ../manage/roles/admin-permissions.rst:180 msgid "Also allows the export of timekeeping records." msgstr "" -#: ../manage/roles/admin-permissions.rst:157 #: ../manage/roles/admin-permissions.rst:181 msgid "``admin.translation``" msgstr "" -#: ../manage/roles/admin-permissions.rst:158 #: ../manage/roles/admin-permissions.rst:182 msgid ":doc:`System > Translations `" msgstr "" -#: ../manage/roles/admin-permissions.rst:159 #: ../manage/roles/admin-permissions.rst:183 msgid "Also enables inline translation" msgstr "" -#: ../manage/roles/admin-permissions.rst:160 #: ../manage/roles/admin-permissions.rst:184 msgid "``admin.trigger``" msgstr "" -#: ../manage/roles/admin-permissions.rst:161 #: ../manage/roles/admin-permissions.rst:185 msgid ":doc:`Manage > Triggers `" msgstr "" -#: ../manage/roles/admin-permissions.rst:163 #: ../manage/roles/admin-permissions.rst:187 msgid "``admin.user``" msgstr "" -#: ../manage/roles/admin-permissions.rst:164 #: ../manage/roles/admin-permissions.rst:188 msgid ":doc:`Manage > Users `" msgstr "" @@ -8833,6 +8813,14 @@ msgid "" "from-users-perspective>` ." msgstr "" +#: ../manage/roles/admin-permissions.rst:193 +msgid "``admin.webhook``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:194 +msgid ":doc:`Manage > Webhook `" +msgstr "" + #: ../manage/roles/agent-permissions.rst:2 msgid "Agent Permissions" msgstr "" @@ -9251,36 +9239,45 @@ msgid "than the user that generated them." msgstr "" #: ../manage/roles/user-preferences-permissions.rst:43 +msgid "``user_preferences.appearance``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:44 +msgid "Appearance configuration" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "Users can switch between dark, light and" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "automatic mode." +msgstr "" + #: ../manage/roles/user-preferences-permissions.rst:47 msgid "``user_preferences.avatar``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:44 #: ../manage/roles/user-preferences-permissions.rst:48 msgid "Avatar settings" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:45 #: ../manage/roles/user-preferences-permissions.rst:49 msgid "Override the default Gravatar with a custom avatar" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:46 #: ../manage/roles/user-preferences-permissions.rst:50 msgid "``user_preferences.calendar``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:47 #: ../manage/roles/user-preferences-permissions.rst:51 msgid "Configure the calendar feed" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:49 #: ../manage/roles/user-preferences-permissions.rst:53 msgid "``user_preferences.device``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:50 #: ../manage/roles/user-preferences-permissions.rst:54 msgid "Manage device login sessions" msgstr "" @@ -9297,22 +9294,18 @@ msgstr "" msgid "To learn more, see :doc:`/manage/trigger/system-notifications`." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:54 #: ../manage/roles/user-preferences-permissions.rst:58 msgid "``user_preferences.language``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:55 #: ../manage/roles/user-preferences-permissions.rst:59 msgid "Configure the UI locale/language" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:57 #: ../manage/roles/user-preferences-permissions.rst:61 msgid "``user_preferences.linked_accounts``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:58 #: ../manage/roles/user-preferences-permissions.rst:62 msgid "Account linking" msgstr "" @@ -9336,7 +9329,6 @@ msgstr "" msgid "is the only way users can utilize third-party logins." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:63 #: ../manage/roles/user-preferences-permissions.rst:67 msgid "``user_preferences.notifications``" msgstr "" @@ -9363,7 +9355,6 @@ msgstr "" msgid "Customers can't receive ticket notifications at all." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:69 #: ../manage/roles/user-preferences-permissions.rst:73 msgid "``user_preferences.out_of_office``" msgstr "" @@ -9388,7 +9379,6 @@ msgstr "" msgid "they're replacing." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:75 #: ../manage/roles/user-preferences-permissions.rst:79 msgid "``user_preferences.overview_sorting``" msgstr "" @@ -9417,12 +9407,10 @@ msgstr "" msgid "overviews has no effect on custom orders." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:82 #: ../manage/roles/user-preferences-permissions.rst:86 msgid "``user_preferences.password``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:83 #: ../manage/roles/user-preferences-permissions.rst:87 msgid "Change account password" msgstr "" @@ -9439,7 +9427,6 @@ msgstr "" msgid "your only allowed authentication method." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:87 #: ../manage/roles/user-preferences-permissions.rst:91 msgid "``user_preferences.two_factor_authentication``" msgstr "" @@ -9476,7 +9463,7 @@ msgstr "" #: ../manage/scheduler.rst:19 msgid "" -"Schedulers can be used to send periodic reminder emails. Use :doc:`/system/" +"Schedulers can be used to send periodic reminder emails. Use :doc:`/misc/" "variables` to build highly-customized email templates." msgstr "" @@ -10472,7 +10459,7 @@ msgstr "" #: ../manage/text-modules.rst:57 msgid "" -"The example text modules below use :doc:`/system/variables` to dynamically " +"The example text modules below use :doc:`/misc/variables` to dynamically " "insert information like the customer's or agent's names." msgstr "" @@ -10812,8 +10799,8 @@ msgstr "" #: ../misc/object-conditions/basics.rst:144 #: ../misc/object-conditions/basics.rst:160 #: ../misc/object-conditions/basics.rst:168 -#: ../misc/object-conditions/basics.rst:178 ../settings/ticket.rst:2 -#: ../system/variables/ticket.rst:2 +#: ../misc/object-conditions/basics.rst:178 ../misc/variables/ticket.rst:2 +#: ../settings/ticket.rst:2 msgid "Ticket" msgstr "" @@ -11047,7 +11034,7 @@ msgstr "" #: ../manage/trigger/how-do-they-work.rst:79 msgid "" -"Certain actions (such as *email*, *SMS* and *notes*) support :doc:`/system/" +"Certain actions (such as *email*, *SMS* and *notes*) support :doc:`/misc/" "variables`, which can be used to build highly-customized message templates." msgstr "" @@ -11076,7 +11063,7 @@ msgstr "" msgid "" "You can also combine static text with placeholders for text fields. Remember " "that the placeholders' values have to be known during trigger runtime. Learn " -"more about :doc:`/system/variables`." +"more about :doc:`/misc/variables`." msgstr "" #: ../manage/trigger/how-do-they-work.rst:105 @@ -12041,7 +12028,7 @@ msgstr "" msgid "" "When switched on, a code editor will be shown below, where you can configure " "custom payload for your webhook in JSON format. To insert supported :doc:`/" -"system/variables` use ``::`` or ``#{`` shortcuts for autocomplete." +"misc/variables` use ``::`` or ``#{`` shortcuts for autocomplete." msgstr "" #: ../manage/webhook/add.rst:103 @@ -14618,11944 +14605,11835 @@ msgid "" "powerful conditions with AND/OR relations." msgstr "" -#: ../settings/branding.rst:10 -msgid "Product Name" +#: ../misc/variables.rst:2 +msgid "Variables" msgstr "" -#: ../settings/branding.rst:7 +#: ../misc/variables.rst:4 msgid "" -"Defines the name of the application, shown in the web interface, tabs and " -"title bar of the web browser." +"Please note that this is just an overview of available variables. It might " +"be incomplete or variables might not be available within some functions. If " +"you're missing variables or are not sure if something is not working as " +"expected, feel free to ask over at the `Community `_." msgstr "" -#: ../settings/branding.rst:10 -msgid "Default value: ``Zammad Helpdesk``" +#: ../misc/variables.rst:10 +msgid "" +"Variables can be called by typing ``::`` (just like text modules in the " +"frontend), as long as you're in a supported text field within the backend. " +"Zammad will display all variables being available within this context and " +"replace it to the variable as soon as you selected an entry." msgstr "" -#: ../settings/branding.rst:13 -msgid "Will be shown in the app and is included in email footers." +#: ../misc/variables.rst:15 +msgid "" +"You have an empty field which you referenced and it appears as ``-``? That's " +"currently working as designed - you might want to ensure that these fields " +"always have a value." msgstr "" -#: ../settings/branding.rst:19 -msgid "Logo" +#: ../misc/variables.rst:20 +msgid "Variable Categories" msgstr "" -#: ../settings/branding.rst:16 -msgid "Defines the logo of the application, shown in the login page of Zammad." +#: ../misc/variables.rst:31 +msgid "Wait, What About Custom Objects?" msgstr "" -#: ../settings/branding.rst:18 +#: ../misc/variables.rst:33 msgid "" -"Ensure to hit the \"Submit\" button after uploading the logo. Otherwise your " -"change will not be saved." +"Good point! Of course, we can't predict what objects you might create, but " +"we can give you a hint on how to put the puzzle together to get your custom " +"values." msgstr "" -#: ../settings/branding.rst:22 +#: ../misc/variables.rst:36 msgid "" -"Allows to set the default language of the Zammad instance. The here defined " -"locale mostly acts as a fallback for:" -msgstr "" - -#: ../settings/branding.rst:25 -msgid "user preferences (if Zammad can't detect the users locale)" +"For this, we'll talk about the inner part of the variable (so everything " +"within ``#{}``), please put the outer part around to have a valid variable. " +"The first part of the variable name consist of the object type. Currently " +"these are:" msgstr "" -#: ../settings/branding.rst:26 -msgid "CSV output (reporting, time accounting)" +#: ../misc/variables.rst:41 +msgid "Ticket (``ticket``)" msgstr "" -#: ../settings/branding.rst:30 -msgid "Define the timezone of your Zammad installation." +#: ../misc/variables.rst:42 +msgid "User (``user``)" msgstr "" -#: ../settings/branding.rst:32 -msgid "" -"This does not have any effect on timings for your agents or how Zammad " -"stores date and time values." +#: ../misc/variables.rst:43 +msgid "Organization (``organization``)" msgstr "" -#: ../settings/branding.rst:35 -msgid "Changing this value has direct consequences on the following areas:" +#: ../misc/variables.rst:44 +msgid "Group (``group``)" msgstr "" -#: ../settings/branding.rst:37 -msgid ":doc:`/manage/scheduler` tasks" +#: ../misc/variables.rst:46 +msgid "" +"The second part is the name of the attribute. This is the name you define " +"during object creation and can be found within the object attribute menu at " +"any time. The first and second part of a variable is divided by a point, e." +"g.: ``ticket.number`` which will in total be ``#{ticket.number}``." msgstr "" -#: ../settings/branding.rst:38 -msgid "search indexing (and thus reporting)" +#: ../misc/variables.rst:51 +msgid "" +"Now, in some situations it's possible that you'll need to use a third part. " +"The best example for such a situation would be a ``select`` or ``tree-" +"select`` field which will by default return the key value, not it's display " +"name. For this, just extend your variable with ``.value``. This will result " +"in ``#{ticket.select.value}``." msgstr "" -#: ../settings/branding.rst:40 -msgid "calendar subscriptions" +#: ../misc/variables.rst:60 +msgid "Using Translated Variables" msgstr "" -#: ../settings/branding.rst:41 -msgid "browser printing" +#: ../misc/variables.rst:62 +msgid "" +"If you want to use a translated variable in triggers or schedulers, you can " +"extend the placeholder like this: ``#{t(ticket.state.name)}``. The ``t`` " +"tells Zammad to search for fitting translated strings. The used output " +"language is based on the system language of Zammad which you can set in the " +"admin panel under :doc:`/settings/branding` or based on the selected locale " +"in the trigger/scheduler edit dialog." msgstr "" -#: ../settings/branding.rst:43 +#: ../misc/variables.rst:69 msgid "" -"Please note that some of above are fallbacks in case Zammad could not detect " -"the agents timezone correctly." +"A possible use-case: you want to send your customers updates on tickets via " +"trigger or scheduler which should include the state of the ticket. Using the " +"default ``#{ticket.state.name}`` (without the translation flag ``t()``) " +"would lead to the output of the original (english) name of the state." msgstr "" -#: ../settings/branding.rst:77 -msgid "Pretty Date" +#: ../misc/variables.rst:75 +msgid "Date and Time Formatting" msgstr "" -#: ../settings/branding.rst:47 +#: ../misc/variables.rst:77 msgid "" -"This setting allows you to define how Zammad should display time stamps " -"within the interface to all users." +"The system (trigger/scheduler selected) locale and timezone predefines a " +"default format of date and timestamp. This format is customizable by using " +"the ``dt()`` method." msgstr "" -#: ../settings/branding.rst:50 -msgid "" -"This does not have any effect on how Zammad returns e.g. time values via " -"variables." +#: ../misc/variables.rst:79 +msgid "The method arguments are as follows:" msgstr "" -#: ../settings/branding.rst:77 -msgid "Choose in between the following options:" +#: ../misc/variables.rst:81 +msgid "The date or timestamp variable you want to format." msgstr "" -#: ../settings/branding.rst:64 -msgid "relative" +#: ../misc/variables.rst:82 +msgid "The output format string." msgstr "" -#: ../settings/branding.rst:55 +#: ../misc/variables.rst:83 +msgid "The timezone to apply (optional)." +msgstr "" + +#: ../misc/variables.rst:85 +#: ../system/objects/external-data-source-example.rst:23 +msgid "**Example:**" +msgstr "" + +#: ../misc/variables.rst:86 msgid "" -"This timestamp shows a relative time span until it switches to a date. Over " -"time, it will change as follows:" +"``#{dt(ticket.updated_at, \"%A %Y-%m-%d %H:%M in the office\", \"Europe/" +"Berlin\")}``" msgstr "" -#: ../settings/branding.rst:58 -msgid "just now" +#: ../misc/variables.rst:87 +msgid "Monday, 2024-03-18 15:31 in the office" msgstr "" -#: ../settings/branding.rst:59 -msgid "5 minutes ago" +#: ../misc/variables.rst:89 +msgid "" +"If you want to use our example, make sure to paste the string above without " +"formatting (``CTRL+Shift+v``), otherwise it won't work." msgstr "" -#: ../settings/branding.rst:60 -msgid "3 days 1 hour ago" +#: ../misc/variables.rst:93 +msgid "The following table lists available format directives:" msgstr "" -#: ../settings/branding.rst:61 -msgid "``03/04/2022``" +#: ../misc/variables.rst:99 +msgid "Parameter" msgstr "" -#: ../settings/branding.rst:63 -msgid "Hovering the timestamp helps, you'll always get a clean timestamp then." +#: ../misc/variables.rst:102 +msgid "``%Y``" msgstr "" -#: ../settings/branding.rst:71 -msgid "absolute" +#: ../misc/variables.rst:103 +msgid "Year with 4 digits" msgstr "" -#: ../settings/branding.rst:67 -msgid "" -"This timestamp always includes the week day. For one week after creation, " -"the timestamp will not contain the date itself: Thursday 18:35." +#: ../misc/variables.rst:104 +msgid "Use ``%y`` for year with 2 digits" msgstr "" -#: ../settings/branding.rst:71 -msgid "After a week it will switch to: ``Friday 4. Mar 16:00``." +#: ../misc/variables.rst:105 +msgid "``%m``" msgstr "" -#: ../settings/branding.rst:76 -msgid "timestamp" +#: ../misc/variables.rst:106 +msgid "Month of year (as number with zero-padding)" msgstr "" -#: ../settings/branding.rst:74 -msgid "" -"This will cause Zammad to show a complete timestamp according to your locale " -"defaults. For English this could be e.g. ``2022/12/03 2:40 pm`` or for " -"German e.g. ``12.03.2022 14:40``." +#: ../misc/variables.rst:107 +msgid "Use ``%-m`` for month without zero-padding" msgstr "" -#: ../settings/branding.rst:78 -msgid "Default setting: ``relative``." +#: ../misc/variables.rst:108 +msgid "``%d``" msgstr "" -#: ../settings/security.rst:2 -msgid "Security" +#: ../misc/variables.rst:109 +msgid "Day of month (as number with zero-padding)" msgstr "" -#: ../settings/security.rst:4 -msgid "" -"For your overview we split each tab within security settings into its own " -"page:" +#: ../misc/variables.rst:110 +msgid "Use ``%e`` for day without zero-padding" msgstr "" -#: ../settings/security/base.rst:2 ../settings/system/base.rst:2 -#: ../settings/ticket.rst:8 -msgid "Base" +#: ../misc/variables.rst:111 +msgid "``%H``" msgstr "" -#: ../settings/security/base.rst:5 -msgid "New User Accounts" +#: ../misc/variables.rst:112 +msgid "Hour of day in 24h notation with zero-padding" msgstr "" -#: ../settings/security/base.rst:9 -msgid "" -"Activates the `register as a new customer` function on the login page. If " -"set to ``no`` only administrators or agents can create new accounts manually." +#: ../misc/variables.rst:113 +msgid "Use ``%k`` for hour without zero-padding" msgstr "" -#: ../settings/security/base.rst:13 ../settings/security/base.rst:38 -#: ../settings/security/base.rst:66 -msgid "Default setting: ``yes``" +#: ../misc/variables.rst:114 +msgid "``%I``" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing activated \"New User Accounts\" setting" +#: ../misc/variables.rst:115 +msgid "Hour of day in 12h notation with zero-padding" msgstr "" -#: ../settings/security/base.rst:22 +#: ../misc/variables.rst:116 msgid "" -"Deactivation of above function **does not** deactivate automatic account " -"creation! This means: If a user writes e.g. an email to Zammad and has no " -"account yet, Zammad will automatically create the account. User accounts are " -"a direct dependency of tickets and thus technically mandatory." +"Use ``%l`` for hour without zero-padding and ``%p`` / ``%P`` for meridian " +"indicator" msgstr "" -#: ../settings/security/base.rst:29 -msgid "Lost Password" +#: ../misc/variables.rst:117 +msgid "``%M``" msgstr "" -#: ../settings/security/base.rst:33 -msgid "" -"Activates the `lost password` function on the login page. If set to ``no`` " -"only administrators may change the user's password - users may update their " -"own password if they're still logged in and they have the required :doc:" -"`permission `." +#: ../misc/variables.rst:118 +msgid "Minute of hour" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing activated \"Lost Password\" setting" +#: ../misc/variables.rst:120 +msgid "``%S``" msgstr "" -#: ../settings/security/base.rst:49 -msgid "" -"With third party authentications - but especially LDAP - you may want to " -"disable this function. Zammad **will not** change third party login " -"passwords and instead set or change the local password!" +#: ../misc/variables.rst:121 +msgid "Second of Minute" msgstr "" -#: ../settings/security/base.rst:56 -msgid "Password Login" +#: ../misc/variables.rst:123 +msgid "``%A``" msgstr "" -#: ../settings/security/base.rst:60 -msgid "" -"Activates the username & password login by default and if no third-party " -"login is activated. Disabling password login on the Zammad login page only " -"takes effect if you enable any :doc:`third-party`." +#: ../misc/variables.rst:124 +msgid "Weekday name" msgstr "" -#: ../settings/security/base.rst:64 -msgid "See :doc:`third-party` for supported third-party logins." +#: ../misc/variables.rst:125 +msgid "Use ``%a`` for abbreviated name or ``%^A`` for uppercase name" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing de-activated \"Password Login\" setting" +#: ../misc/variables.rst:126 +msgid "``%B``" msgstr "" -#: ../settings/security/base.rst:77 -msgid "" -"To help administrators to overcome \"login issues\", Zammad automatically " -"offers a password request for administrator users. This allows you to adjust " -"Third-Party applications even if the login does no longer work!" +#: ../misc/variables.rst:127 +msgid "Month name" msgstr "" -#: ../settings/security/base.rst:84 -msgid "Session Timeout" +#: ../misc/variables.rst:128 +msgid "Use ``%b`` for abbreviated name" msgstr "" -#: ../settings/security/base.rst:86 -msgid "" -"All settings below by default are set to ``4 weeks``. Session Timeout " -"defines the life time of a users session. As soon as it's reached, Zammad " -"will automatically log off the session in question." +#: ../misc/variables.rst:129 +msgid "``%U``" msgstr "" -#: ../settings/security/base.rst:91 -msgid "" -"Zammad takes the highest value set assigned for the user based on the " -"permissions." +#: ../misc/variables.rst:130 +msgid "Week number of current year" msgstr "" -#: ../settings/security/base.rst:94 -msgid "``admin``" +#: ../misc/variables.rst:131 +msgid "Use ``%W`` for a different calculation method" msgstr "" -#: ../settings/security/base.rst:96 -msgid "``ticket.customer``" +#: ../misc/variables.rst:134 +msgid "" +"We support the known format directives for the Ruby built-in method " +"``strftime`` of the ``DateTime`` class. For more information, see `here " +"`_." msgstr "" -#: ../settings/security/base.rst:97 -msgid "``default`` (fallback if user doesn't have above permissions set)" +#: ../misc/variables/article.rst:2 +msgid "Articles" msgstr "" -#: ../settings/security/base.rst:99 +#: ../misc/variables/article.rst:4 ../misc/variables/config.rst:4 +#: ../misc/variables/current-user.rst:4 ../misc/variables/ticket.rst:4 msgid "" -"All settings act independently from each other allowing you to disable the " -"timeouts for e.g. admins, but not agents." +"If you're missing variables or are not sure if something is not working as " +"expected, feel free to ask over at the `Community `_." msgstr "" -#: ../settings/security/base.rst:115 -#: ../system/integrations/checkmk/api-reference.rst:13 -msgid "Example" +#: ../misc/variables/article.rst:6 +msgid "" +"Below you can find all available ticket article-based variables within " +"Zammad. These can be called via triggers for example. If you're unsure if " +"Zammad does support variables at the point you're at, you can try to type " +"``::`` to check." msgstr "" -#: ../settings/security/base.rst:107 -msgid "Let's suppose you configured the following session timeouts" +#: ../misc/variables/article.rst:9 ../misc/variables/config.rst:9 +#: ../misc/variables/ticket.rst:9 +msgid "" +"The below list gives you an example what kind of data you can expect, it's " +"not intended to explain the data itself." msgstr "" -#: ../settings/security/base.rst:104 -msgid "default: 3 weeks" +#: ../misc/variables/article.rst:11 +msgid "Article Variables" msgstr "" -#: ../settings/security/base.rst:105 -msgid "admin: 2 weeks" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "name" msgstr "" -#: ../settings/security/base.rst:106 -msgid "ticket.agent: 4 weeks" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "variable" msgstr "" -#: ../settings/security/base.rst:107 -msgid "ticket.customer: 1 week" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "example" msgstr "" -#: ../settings/security/base.rst:115 -msgid "This results in the following situations" +#: ../misc/variables/article.rst:1 +msgid "Article > Cc" msgstr "" -#: ../settings/security/base.rst:110 -msgid "a user with ``admin`` permission will have a timeout of 2 weeks" +#: ../misc/variables/article.rst:1 +msgid "``#{article.cc}``" msgstr "" -#: ../settings/security/base.rst:111 -msgid "" -"a user with ``admin`` and ``ticket.agent`` permissions will have a timeout " -"of 2 weeks" +#: ../misc/variables/article.rst:1 +msgid "``jdoe@example.com, company@example.com``" msgstr "" -#: ../settings/security/base.rst:113 -msgid "" -"a user with ``ticket.customer`` permission will have a timeout of 1 week" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Address" msgstr "" -#: ../settings/security/base.rst:115 -msgid "" -"a user with neither ``admin``, ``ticket.agent`` nor ``ticket.customer`` " -"permissions will have a timeout of 3 weeks" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.address}``" msgstr "" -#: ../settings/security/password.rst:4 -msgid "" -"This section allows you to define password requirements for the local user " -"accounts." +#: ../misc/variables/article.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:9 -msgid "" -"Zammad does **not** allow you to change your LDAP password, instead, it will " -"set a password in its local database which might confuse your users. This " -"might be addressed in the future by `#1169 `_." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Department" msgstr "" -#: ../settings/security/password.rst:14 -msgid "**Exception for admins**" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.department}``" msgstr "" -#: ../settings/security/password.rst:16 -msgid "" -"Please note that below password policies *do not* affect administrators " -"setting passwords on user accounts. While this seems strange and not safe we " -"believe that an administrator knowing an user's password is insecure as well." +#: ../misc/variables/article.rst:1 +msgid "``Sales`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:21 -msgid "The suggested workflow is either:" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Email" msgstr "" -#: ../settings/security/password.rst:23 -msgid "" -"to use third party logins to not require local passwords at all **- or -**" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.email}``" msgstr "" -#: ../settings/security/password.rst:25 -msgid "to require your *user to reset the password* upon first login." +#: ../misc/variables/article.rst:1 +msgid "``jdoe@example.com``" msgstr "" -#: ../settings/security/password.rst:27 -msgid "" -"This way administrators are not required to set a user's password at all!" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Fax" msgstr "" -#: ../settings/security/password.rst:31 -msgid "Maximum Failed Logins" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.fax}``" msgstr "" -#: ../settings/security/password.rst:33 -msgid "" -"You can choose a value between ``4`` and ``20``. This defines how often a " -"login to a user account may fail until Zammad will lock it. Your users can " -"always use the \"forgot password\" function to change their password and " -"unlock their account." -msgstr "" - -#: ../settings/security/password.rst:38 -msgid "The default value is ``10``." +#: ../misc/variables/article.rst:1 +msgid "``+4930123456789`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:42 -msgid "Beside changing the user's password, you can also unlock accounts via" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Firstname" msgstr "" -#: ../settings/security/password.rst:44 -msgid ":ref:`user management list `" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.firstname}``" msgstr "" -#: ../settings/security/password.rst:45 -msgid ":docs:`console `" +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Joe`` or empty if not set" msgstr "" -#: ../settings/security/password.rst:46 -msgid ":docs:`API `" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Lastname" msgstr "" -#: ../settings/security/password.rst:50 -msgid "Failed logins via LDAP no longer lock accounts." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.lastname}``" msgstr "" -#: ../settings/security/password.rst:53 -msgid "2 Lower Case And 2 Upper Case Characters" +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +#: ../misc/variables/ticket.rst:1 +msgid "``Doe`` or empty if not set" msgstr "" -#: ../settings/security/password.rst:55 -msgid "" -"You can add complexity to passwords by enforcing at least 2 upper and lower " -"case characters." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Login" msgstr "" -#: ../settings/security/password.rst:58 ../settings/security/password.rst:83 -msgid "The default value is ``no``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.login}``" msgstr "" -#: ../settings/security/password.rst:62 -msgid "Minimum Length" +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +#: ../misc/variables/ticket.rst:1 +msgid "``jdoe``" msgstr "" -#: ../settings/security/password.rst:64 -msgid "" -"This defines the minimum password length required for users to provide (from " -"``4`` to ``20``)." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Mobile" msgstr "" -#: ../settings/security/password.rst:67 -msgid "The default value is ``6``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.mobile}``" msgstr "" -#: ../settings/security/password.rst:71 -msgid "Digit Required" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Note" msgstr "" -#: ../settings/security/password.rst:73 -msgid "This enforces your users to use at least one digit within the password." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.note}``" msgstr "" -#: ../settings/security/password.rst:75 -msgid "The default value is ``yes``." +#: ../misc/variables/article.rst:1 +msgid "``Some note about user`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:78 -msgid "Special Character Required" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Phone" msgstr "" -#: ../settings/security/password.rst:80 -msgid "" -"This setting allows you to improve your password quality even more by " -"enforcing the password to contain at least one special character." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.phone}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:2 -msgid "SSL Certificates" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > VIP" msgstr "" -#: ../settings/security/ssl-certificates.rst:7 -msgid "" -"Zammad offers the possibility to upload custom certificates and custom " -"Certificate Authority (CA) certificates. This can be useful if you want to " -"connect Zammad the secure way to other systems which are using custom " -"certificates." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.vip}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:12 -msgid "" -"An example usecase might be: You have an internal LDAP server that is not " -"accessible from the internet, and you want a SSL-encrypted connection, using " -"a custom certificate." +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +msgid "``true`` or ``false``" msgstr "" -#: ../settings/security/ssl-certificates.rst:19 -msgid "" -"You should have an existing custom certificate file and/or a custom CA " -"certificate file, which you want to add to Zammad. As filetype ``.crt`` is " -"supported and the certificate format has to be PEM (Base64 ASCII)." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Web" msgstr "" -#: ../settings/security/ssl-certificates.rst:25 -msgid "" -"When you import a custom CA certificate, all certificates generated with " -"this are trusted. This can be useful if you have more than one system/" -"certificate you want to connect to and the certificates are issued from the " -"same custom CA." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.web}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:31 -msgid "Add a Certificate" +#: ../misc/variables/article.rst:1 +msgid "``https://zammad.com`` or empty if not set in user object" msgstr "" -#: ../settings/security/ssl-certificates.rst:33 -msgid "" -"To add a custom certificate or a custom CA certificate, head over to the " -"Admin panel > Settings > Security > SSL Certificates. Here you can find a " -"\"Add SSL Certificate\" button. In the dialog you can either select a " -"certificate file or paste the content of the certificate:" +#: ../misc/variables/article.rst:1 +msgid "Article > Created" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate adding dialog" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_at}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:43 -msgid "" -"After selecting a file or pasting the content of the certificate, click on " -"the \"Add\" button to finally upload it to Zammad. Then, the certificates " -"are immediately effective, no restart or similar required." +#: ../misc/variables/article.rst:1 +msgid "``2019-10-08 15:24:47 UTC``" msgstr "" -#: ../settings/security/ssl-certificates.rst:49 -msgid "" -"Please note that only single certificate files are supported. That means if " -"you want to import a certificate / CA certificate, it must contain **only " -"one** certificate." +#: ../misc/variables/article.rst:1 +msgid "Article > From" msgstr "" -#: ../settings/security/ssl-certificates.rst:54 -msgid "Certificate Overview" +#: ../misc/variables/article.rst:1 +msgid "``#{article.from}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:56 +#: ../misc/variables/article.rst:1 msgid "" -"After you added a certificate, you can see a table with information for each " -"added certificate:" +"``Joe Doe `` may differ, depends on ``FROM`` of send mail" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing table of added certificates" +#: ../misc/variables/article.rst:1 +msgid "Article > Sender > Name" msgstr "" -#: ../settings/security/ssl-certificates.rst:64 -msgid "" -"Here you can download the certificate or delete it, if you don't need it " -"anymore." +#: ../misc/variables/article.rst:1 +msgid "``#{article.sender.name}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:68 -msgid "Deleting Certificates" +#: ../misc/variables/article.rst:1 +msgid "``Customer``, ``Agent`` or ``System``" msgstr "" -#: ../settings/security/ssl-certificates.rst:70 -msgid "" -"If you want to delete a specific certificate, you can do it by clicking on " -"the menu in the actions column and selecting delete:" +#: ../misc/variables/article.rst:1 +msgid "Article > Subject" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate deletion button" +#: ../misc/variables/article.rst:1 +msgid "``#{article.subject}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:79 -msgid "Downloading Certificates" +#: ../misc/variables/article.rst:1 +msgid "``My amazing subject``" msgstr "" -#: ../settings/security/ssl-certificates.rst:81 -msgid "" -"If you want to download your certificates, you can do this as well via " -"corresponding action buttons." +#: ../misc/variables/article.rst:1 +msgid "Article > Text" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate download button" +#: ../misc/variables/article.rst:1 +msgid "``#{article.body}``" msgstr "" -#: ../settings/security/third-party.rst:13 -msgid "Login Providers" +#: ../misc/variables/article.rst:1 +msgid "``Test`` without formatting (plain)" msgstr "" -#: ../settings/security/third-party.rst:2 -msgid "Third-Party Applications" +#: ../misc/variables/article.rst:1 +msgid "Article > TicketID" msgstr "" -#: ../settings/security/third-party.rst:4 -msgid "" -"Third party authentication is a great way to help your users to login to " -"Zammad more easily. If the account is yet unknown, Zammad will create a new " -"user automatically, without the user needed to interact (e.g. type in his " -"name). Another big advantage of this feature is that your user doesn't need " -"to remember another password." +#: ../misc/variables/article.rst:1 +msgid "``#{article.ticket_id}``" msgstr "" -#: ../settings/security/third-party.rst:10 -msgid "" -"You can deactivate logging in via :ref:`security_password_login` if any of " -"the mentioned authentication providers are enabled in your instance." +#: ../misc/variables/article.rst:1 +msgid "``1`` (not ticket number)" msgstr "" -#: ../settings/security/third-party.rst:27 -msgid "" -"We're currently missing documentation for the following login providers:" +#: ../misc/variables/article.rst:1 +msgid "Article > To" msgstr "" -#: ../settings/security/third-party.rst:29 -msgid "LinkedIn" +#: ../misc/variables/article.rst:1 +msgid "``#{article.to}``" msgstr "" -#: ../settings/security/third-party.rst:30 -msgid "Weibo" +#: ../misc/variables/article.rst:1 +msgid "``helpdesk@example.com``" msgstr "" -#: ../settings/security/third-party.rst:35 -msgid "Automatic Account Link on Initial Logon" +#: ../misc/variables/article.rst:1 +msgid "Article > Type > Name" msgstr "" -#: ../settings/security/third-party.rst:37 -msgid "" -"In general there's two possible options for Zammad on how to deal with " -"already known users as they try to authenticate against a third-party " -"application. By default, Zammad will not automatically link \"unknown\" " -"authentication providers to existing accounts." +#: ../misc/variables/article.rst:1 +msgid "``#{article.type.name}``" msgstr "" -#: ../settings/security/third-party.rst:42 +#: ../misc/variables/article.rst:1 msgid "" -"This means that the user has to manually link authentication providers to " -"their accounts (for more about this :user-docs:`consult the user " -"documentation `)." +"``email`` (`list of article types `_)" msgstr "" -#: ../settings/security/third-party.rst:46 -msgid "" -"Sometimes this doesn't come in handy as this also means you'll receive error " -"messages about \"email address being in use already\" for (yet) unknown " -"third-party authentication methods." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Address" msgstr "" -#: ../settings/security/third-party.rst:50 -msgid "" -"If you want to allow your users to always be able to log in, no matter what, " -"you may want to enable ``Automatic account link on initial logon``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.address}``" msgstr "" -#: ../settings/security/third-party.rst:None -msgid "" -"Screenshot highlighting the \"Automatic account link on initial logon\"\n" -"setting" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Department" msgstr "" -#: ../settings/security/third-party.rst:60 -msgid "Automatic Account Linking Notification" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.department}``" msgstr "" -#: ../settings/security/third-party.rst:64 -msgid "" -"To improve security and your users awareness, you can enable Zammad to " -"notify your users when a new third-party application has been linked to " -"their account." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Email" msgstr "" -#: ../settings/security/third-party.rst:68 -msgid "" -"This notification is sent out once per third-party application. Zammad does " -"also mention the method used, e.g.: ``Microsoft``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.email}``" msgstr "" -#: ../settings/security/third-party.rst:71 -msgid "By default this setting is not active (set to ``no``)." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Fax" msgstr "" -#: ../settings/security/third-party.rst:0 -msgid "" -"Screenshot showing sample notification mail after initial\n" -"third-party linking" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.fax}``" msgstr "" -#: ../settings/security/third-party.rst:85 -msgid "" -"This notification is only sent if the account in question already exists. If " -"the login via the third-party also creates the missing account, the " -"notification will be skipped." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Firstname" msgstr "" -#: ../settings/security/third-party.rst:89 -msgid "This means it only affects:" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.firstname}``" msgstr "" -#: ../settings/security/third-party.rst:91 -msgid "manual account linking within the third-party page of the users profile" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Lastname" msgstr "" -#: ../settings/security/third-party.rst:92 -msgid "" -"logging into an existing local account by utilizing the *automatic account " -"link on initial logon* functionality" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.lastname}``" msgstr "" -#: ../settings/security/third-party.rst:None -msgid "" -"Screenshot showing the \"automatic account linking notification\"\n" -"setting" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Login" msgstr "" -#: ../settings/security/third-party.rst:100 -msgid "No User Creation on Logon" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.login}``" msgstr "" -#: ../settings/security/third-party.rst:102 -msgid "" -"By default, Zammad will create a new user account if the user logs in via a " -"third-party application and the account doesn't exist yet." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Mobile" msgstr "" -#: ../settings/security/third-party.rst:105 -msgid "" -"If you want to prevent Zammad from creating new accounts on logon, you can " -"disable this feature by setting ``No user creation on logon`` to ``yes``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.mobile}``" msgstr "" -#: ../settings/security/third-party.rst:None -msgid "Screenshot showing the \"no user creation on logon\" setting" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Note" msgstr "" -#: ../settings/security/third-party/facebook.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via Facebook To do " -"so, you need to follow these steps:" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.note}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:9 -msgid "Register Facebook App" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Phone" msgstr "" -#: ../settings/security/third-party/facebook.rst:11 -msgid "" -"Visit [https://developers.facebook.com/apps/] and click on \"Add a new App\"" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.phone}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "initial page" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > VIP" msgstr "" -#: ../settings/security/third-party/facebook.rst:17 -msgid "After that enter the app settings" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.vip}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "Create App" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Web" msgstr "" -#: ../settings/security/third-party/facebook.rst:22 -msgid "Navigate to \"Settings\" and fill in this infromation" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.web}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "App Settings" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated" msgstr "" -#: ../settings/security/third-party/facebook.rst:27 -msgid "Navigate to app review and Check \"Make [appname] public?\"" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_at}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "App Review" +#: ../misc/variables/article.rst:1 +msgid "Article > Visibility" msgstr "" -#: ../settings/security/third-party/facebook.rst:35 -msgid "Configure Zammad as Facebook App" +#: ../misc/variables/article.rst:1 +msgid "``#{article.internal}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:37 -msgid "" -"Navigate to \"Admin -> Security -> Third Party Applications\" and enter the " -"App ID and the App Secret. You can find this Key in the Dashbard of your " -"Facebok app." +#: ../misc/variables/article.rst:1 +msgid "``false`` or ``true`` (false if not internal)" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "Zammad Configuration" +#: ../misc/variables/article.rst:1 +msgid "Article Text as HTML (not referenced)" msgstr "" -#: ../settings/security/third-party/facebook.rst:44 -#: ../settings/security/third-party/github.rst:43 -#: ../settings/security/third-party/gitlab.rst:46 -msgid "" -"Now you can link accounts via \"Avatar -> Profile -> Link Accounts\" or " -"login via Zammad login page." +#: ../misc/variables/article.rst:1 +msgid "``#{article.body_as_html}``" msgstr "" -#: ../settings/security/third-party/github.rst:2 -#: ../system/integrations/github.rst:2 -msgid "GitHub" +#: ../misc/variables/article.rst:1 +msgid "``Test`` with formatting" msgstr "" -#: ../settings/security/third-party/github.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via GitHub. To " -"activate the quick login you need to enable OAuth for GitHub." +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "Ticket > Article#" msgstr "" -#: ../settings/security/third-party/github.rst:8 -msgid "Register GitHub App" +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "``#{ticket.article_count}``" msgstr "" -#: ../settings/security/third-party/github.rst:10 -msgid "" -"Visit https://www.github.com/settings/applications/new and enter the app " -"settings. As callback URL enter \"https://zammad_host/auth/github/callback\" " -"where zammad_host has to be replaced with your Zammad FQDN" +#: ../misc/variables/article.rst:1 +msgid "``1`` number of ticket articles" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "Register OAuth app on www.github.com" +#: ../misc/variables/config.rst:2 +msgid "Config" msgstr "" -#: ../settings/security/third-party/github.rst:19 -msgid "Configure Zammad as GitHub App" +#: ../misc/variables/config.rst:6 +msgid "" +"Below you'll find config related variables. These hold useful configuration " +"information that you can use within e.g. triggers to show necessary " +"information to your customer." msgstr "" -#: ../settings/security/third-party/github.rst:21 -msgid "" -"Enter the \"APP ID\" and the \"APP SECRET\" from the GitHub OAUTH " -"Applications Dashboard" +#: ../misc/variables/config.rst:11 +msgid "Config Variables" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub config in Zammad admin interface" +#: ../misc/variables/config.rst:1 +msgid "Config > Fully Qualified Domain Name" msgstr "" -#: ../settings/security/third-party/github.rst:28 -msgid "" -"After you configured the GitHub credentials and activated the login method, " -"you should see a new icon on the login page." +#: ../misc/variables/config.rst:1 +msgid "``#{config.fqdn}``" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub logo on login page" +#: ../misc/variables/config.rst:1 +msgid "``zammad.example.com``" msgstr "" -#: ../settings/security/third-party/github.rst:34 -msgid "" -"If you click on the icon you will be redirected to GitHub and see something " -"similar to this:" +#: ../misc/variables/config.rst:1 +msgid "Config > HTTP type" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub oauth page" +#: ../misc/variables/config.rst:1 +msgid "``#{config.http_type}``" msgstr "" -#: ../settings/security/third-party/github.rst:40 -#: ../settings/security/third-party/gitlab.rst:42 -msgid "" -"When you grant the access you will be redirected to your Zammad instance and " -"logged in as a customer." +#: ../misc/variables/config.rst:1 +msgid "``https`` or ``http``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:2 -msgid "Gitlab" +#: ../misc/variables/config.rst:1 +msgid "Config > Organization" msgstr "" -#: ../settings/security/third-party/gitlab.rst:4 +#: ../misc/variables/config.rst:1 +msgid "``#{config.organization}``" +msgstr "" + +#: ../misc/variables/config.rst:1 msgid "" -"It is possible to create a quick login for your helpdesk via Gitlab. To " -"activate the quick login you need to enable OAuth for Gitlab." +"``Zammad GmbH`` value set in `Branding `_" msgstr "" -#: ../settings/security/third-party/gitlab.rst:8 -msgid "Register Gitlab App" +#: ../misc/variables/config.rst:1 +msgid "Config > Product Name" msgstr "" -#: ../settings/security/third-party/gitlab.rst:10 -msgid "To register an app in Gitlab open your profile and select applications." +#: ../misc/variables/config.rst:1 +msgid "``#{config.product_name}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:12 +#: ../misc/variables/config.rst:1 msgid "" -"As callback URL enter \"https://zammad-fqdn/auth/gitlab/callback\" where " -"zammad-fqdn has to be replaced with your Zammad FQDN" +"``Helpdesk`` value set in `Branding `_" msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Register OAuth app on gitlab instance" +#: ../misc/variables/config.rst:1 +msgid "Config > SystemID" msgstr "" -#: ../settings/security/third-party/gitlab.rst:18 -msgid "Just select *read_user* under scopes as in the screenshot and save it." +#: ../misc/variables/config.rst:1 +msgid "``#{config.system_id}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:21 -msgid "Configure Zammad as Gitlab App" +#: ../misc/variables/config.rst:1 +msgid "``31`` (value between 1 and 99)" msgstr "" -#: ../settings/security/third-party/gitlab.rst:23 -msgid "" -"Enter the \"APP ID\" and the \"APP SECRET\" from the Gitlab OAUTH " -"Applications Dashboard and your Gitlab-URL in the \"SITE\" field." +#: ../misc/variables/config.rst:1 +msgid "Config > Ticket Hook" msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab config in Zammad admin interface" +#: ../misc/variables/config.rst:1 +msgid "``#{config.ticket_hook}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:30 -msgid "" -"After you configured the Gitlab credentials and activated the login method, " -"you should see a new icon on the login page." +#: ../misc/variables/config.rst:1 +msgid "``Ticket#``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab logo on login page" +#: ../misc/variables/current-user.rst:2 +msgid "Current User" msgstr "" -#: ../settings/security/third-party/gitlab.rst:36 +#: ../misc/variables/current-user.rst:6 msgid "" -"If you click on the icon you will be redirected to Gitlab and see something " -"similar to this:" +"Current user variables always return values of the current user that caused " +"e.g. a trigger to run." msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab oauth page" +#: ../misc/variables/current-user.rst:8 +msgid "" +"Due to the above fact, these variables are often not (yet) set or available " +"for usage." msgstr "" -#: ../settings/security/third-party/google.rst:4 +#: ../misc/variables/current-user.rst:10 msgid "" -"With some easy and fast steps, you can enable Zammad to authenticate your " -"users via Google." +"In situations where e.g. schedulers or triggers run, this most likely is " +"nothing you want to use." msgstr "" -#: ../settings/security/third-party/google.rst:8 -msgid "Register a Google App" +#: ../misc/variables/current-user.rst:13 +msgid "Current User Variables" msgstr "" -#: ../settings/security/third-party/google.rst:10 -msgid "" -"First of all, we need to create a new project - you can skip this step if " -"you already have one." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Address" msgstr "" -#: ../settings/security/third-party/google.rst:15 -msgid "" -"Use this link to create a new project: https://console.cloud.google.com/" -"projectcreate" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.address}``" msgstr "" -#: ../settings/security/third-party/google.rst:18 -msgid "" -"Now expand the menu, expand \"APIs & Services\" and select \"Credentials\". " -"Go to the tab \"OAuth consent screen\" first and ensure to fill in the " -"requested information - without doing so you can't create credentials!" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set" msgstr "" -#: ../settings/security/third-party/google.rst:None -msgid "Creating a consent screen" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Avatar" msgstr "" -#: ../settings/security/third-party/google.rst:25 -msgid "" -"After filling in and saving the consent screen information, you can go to " -"the \"Credentials\" tab and create new \"OAuth client ID\"-Credentials." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/google.rst:28 -msgid "" -"Fill in the necessary information as follows and replace ``zammad_host`` " -"with your FQDN:" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "avatar picture with width and height in pixel (e.g. 60,60)" msgstr "" -#: ../settings/security/third-party/google.rst:31 -msgid "**Application type** ``[x] Web application``" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created at" msgstr "" -#: ../settings/security/third-party/google.rst:34 -msgid "**Authorized JavaScript origins** ``https://zammad_host/``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_at}``" msgstr "" -#: ../settings/security/third-party/google.rst:37 -msgid "" -"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" -"callback``" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC``" msgstr "" -#: ../settings/security/third-party/google.rst:None -msgid "Adding a new OAuth client ID" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Address" msgstr "" -#: ../settings/security/third-party/google.rst:43 -msgid "" -"After creating the credentials, go to your Zammad installation and navigate " -"to \"Admin > Security > Third Party Applications\" > Google. Enter your " -"Client ID and Client secret here." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.address}``" msgstr "" -#: ../settings/security/third-party/google.rst:None -msgid "Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Avatar" msgstr "" -#: ../settings/security/third-party/google.rst:50 -msgid "After submitting, the login via Google can be used." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:2 -msgid "Microsoft" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Department" msgstr "" -#: ../settings/security/third-party/microsoft.rst:4 -msgid "" -"Zammad's Microsoft connection allows your users with Microsoft accounts to " -"login. This works for Azure users as well and can be an alternative to :doc:" -"`/system/integrations/ldap/index`." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.department}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:10 -msgid "" -"This documentation part does not cover our :doc:`📧 Microsoft 365 email " -"channel `." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Sales`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screenshot showing Microsoft login button on Zammad login screen." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Email" msgstr "" -#: ../settings/security/third-party/microsoft.rst:30 -#: ../settings/security/third-party/microsoft.rst:53 -msgid "Supported account types:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.email}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:22 -msgid "" -"Please note that Zammad only supports these account types (App dependent):" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``jdoe@customer.tld``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:35 -msgid "Avatars of signing in users:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Fax" msgstr "" -#: ../settings/security/third-party/microsoft.rst:33 -msgid "" -"Zammad currently ignores user avatars. If the user is registered with e.g. " -"Gravatar, Zammad will fetch the avatar from there if enabled. See :doc:" -"`Zammad Image Service ` for more." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.fax}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:38 -msgid "Step 1 - Register a Microsoft App for Zammad" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``004930123464789`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:40 -msgid "" -"Login to the `Microsoft Azure Portal `_ and " -"navigate to App registrations to create a new app. Provide the requested " -"information as follows and register your app." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Firstname" msgstr "" -#: ../settings/security/third-party/microsoft.rst:46 -msgid "Name:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.firstname}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:45 -msgid "" -"Any meaningful name fitting, this name will be displayed to users trying to " -"authenticate with this app." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``John`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:49 -msgid "Choose one of the above mentioned account types (see Limitations)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Lastname" msgstr "" -#: ../settings/security/third-party/microsoft.rst:51 -msgid "" -"The correct account type depends on your use case. If you want to use the " -"authentication internal only, choose the first option. If you're unsure, use " -"the \"Help me choose...\" link." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.lastname}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:58 -msgid "Redirect URI (optional):" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Login" msgstr "" -#: ../settings/security/third-party/microsoft.rst:56 -msgid "" -"Select web and provide your callback URL. The callback URL looks like this: " -"``https://zammad.domain.tld/auth/microsoft_office365/callback``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.login}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to register a Microsoft app" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Mobile" msgstr "" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "Within **API permissions** add the following permissions:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.mobile}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:69 -msgid "``User.Read``" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``0049176123456789`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "Contacts" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Note" msgstr "" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "``Contacts.Read``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.note}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:73 -msgid "" -"You can find these permissions within *Microsoft Graph → Delegated " -"permissions*." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Some note to this user`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to add required API permissions" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Phone" msgstr "" -#: ../settings/security/third-party/microsoft.rst:80 -msgid "" -"Within **Certificates & secrets** create a new client secret. Note down the " -"returned secret **value** for later. **Do not** use the secret ID!" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.phone}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to create a new app secret" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``004930123456789`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:88 -msgid "" -"From **Overview** copy your apps *Application (client) ID*. If you're using " -"a single tenant app, please also copy *Directory (tenant) ID*. You now have " -"all required information for Zammad." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > VIP" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to retreive application client and tenant IDs" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.vip}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:98 -msgid "Step 2 - Add App Credentials to Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Web" msgstr "" -#: ../settings/security/third-party/microsoft.rst:100 -msgid "" -"Navigate to Security > Third-party Applications (Tab) within Zammad's admin " -"settings. Scroll down to the section *Authentication via Microsoft* and fill " -"in the required information." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.web}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:105 -msgid "App ID:" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``https://zammad.org`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:105 -msgid "This is your *Application (client) ID*." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Department" msgstr "" -#: ../settings/security/third-party/microsoft.rst:108 -msgid "App secret:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.department}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:108 -msgid "This is your *client secret* (value)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Email" msgstr "" -#: ../settings/security/third-party/microsoft.rst:113 -msgid "App Tenant ID:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.email}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:111 -msgid "" -"**optional** only required for apps that use account type *Accounts in this " -"organizational directory only (Default Directory only - Single tenant).*" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Fax" msgstr "" -#: ../settings/security/third-party/microsoft.rst:115 -msgid "" -"Apply your settings by pressing submit and activate *Authentication via " -"Microsoft*." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.fax}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "" -"Screencast showing how to add app credentials and activating the\n" -"authentication method" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Firstname" msgstr "" -#: ../settings/security/third-party/saml.rst:2 -msgid "SAML" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.firstname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:4 -msgid "" -"Connect your SAML (Security Assertion Markup Language) identity provider as " -"a single sign-on (SSO) method." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Lastname" msgstr "" -#: ../settings/security/third-party/saml.rst:7 -msgid "" -"SAML is an open standard for SSO authentication (among other things). Sign-" -"ins are shared across multiple **service providers** and managed by a " -"central **identity provider** (IdP)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.lastname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:11 -msgid "" -"In this case, the service provider is Zammad, and the IdP is a software " -"service that you either host or subscribe to (*e.g.,* `Keycloak `_, `Redhat SSO Server `_, `ADFS `_, or `Okta `_)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Login" msgstr "" -#: ../settings/security/third-party/saml.rst:18 -msgid "" -"This guide assumes you are already using SAML within your organization (i." -"e., that your IdP is fully set up)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.login}``" msgstr "" -#: ../settings/security/third-party/saml.rst:21 -msgid "" -"Please note: Our instructions are based on connecting Zammad with Keycloak." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Mobile" msgstr "" -#: ../settings/security/third-party/saml.rst:25 -msgid "Step 1: Configure Your IdP" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.mobile}``" msgstr "" -#: ../settings/security/third-party/saml.rst:28 -msgid "Add Zammad as a Client/App" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Note" msgstr "" -#: ../settings/security/third-party/saml.rst:30 -msgid "" -"Import Zammad into your IdP using the XML configuration found at ``https://" -"your.zammad.domain/auth/saml/metadata``." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.note}``" msgstr "" -#: ../settings/security/third-party/saml.rst:33 -msgid "" -"If your IdP doesn't support XML import, you will have to configure Zammad as " -"a new client/app manually using the above XML metadata file for reference." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Domain based assignment" msgstr "" -#: ../settings/security/third-party/saml.rst:36 -msgid "For instance, when you see this tag:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.domain_assignment}``" msgstr "" -#: ../settings/security/third-party/saml.rst:42 -msgid "" -"Set the **Assertion Consumer Service Binding URL** (sometimes also listed as " -"**Valid Redirect URIs**) to ``http://your.zammad.domain/auth/saml/callback``." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Domain" msgstr "" -#: ../settings/security/third-party/saml.rst:47 -msgid "Set Up User Attribute Mapping" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.domain}``" msgstr "" -#: ../settings/security/third-party/saml.rst:49 -msgid "" -"Zammad requests the following user attributes (or “properties”) from the IdP:" +#: ../misc/variables/current-user.rst:1 +msgid "``zammad.com`` or empty if not set" msgstr "" -#: ../settings/security/third-party/saml.rst:51 -msgid "Email address (``email``)" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Name" msgstr "" -#: ../settings/security/third-party/saml.rst:52 -msgid "Full name (``name``)" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.name}``" msgstr "" -#: ../settings/security/third-party/saml.rst:53 -msgid "Given name (``first_name``)" +#: ../misc/variables/current-user.rst:1 +msgid "``Zammad GmbH``" msgstr "" -#: ../settings/security/third-party/saml.rst:54 -msgid "Family name (``last_name``)" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Note" msgstr "" -#: ../settings/security/third-party/saml.rst:56 -msgid "" -"You may need to set up “mappers” (or “mappings”) to tell your IdP how user " -"attributes in SAML correspond to those in Zammad. For a more detailed " -"breakdown, refer to the XML metadata file referenced in the previous section." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.note}``" msgstr "" -#: ../settings/security/third-party/saml.rst:62 -msgid "Per-IdP Instructions" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``A note to the organization of the user`` or empty if not set" msgstr "" -#: ../settings/security/third-party/saml.rst:102 -msgid "Keycloak" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Shared organization" msgstr "" -#: ../settings/security/third-party/saml.rst:65 -msgid "" -"**To add Zammad as a client,** save the XML configuration to disk (``https://" -"your.zammad.domain/auth/saml/metadata``) and use **Clients > Clients list > " -"Import client** in the Keycloak admin panel." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.shared}``" msgstr "" -#: ../settings/security/third-party/saml.rst:70 -msgid "" -"To help Zammad **match its own user accounts to Keycloak users**, create a " -"user attribute (or “property”) mapper. In **Clients list**, click on your " -"newly created Client ID, choose the tab **Client scopes** and click on the " -"link which refers to your Zammad instance. Choose **Add mapper > By " -"configuration > User Property** and create a mapper with the following " -"entries:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > VIP" msgstr "" -#: ../settings/security/third-party/saml.rst:78 -msgid "**Name**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.vip}``" msgstr "" -#: ../settings/security/third-party/saml.rst:80 -msgid "**Mapper Type**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Phone" msgstr "" -#: ../settings/security/third-party/saml.rst:81 -msgid "``User Property``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.phone}``" msgstr "" -#: ../settings/security/third-party/saml.rst:82 -msgid "**Property**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated at" msgstr "" -#: ../settings/security/third-party/saml.rst:83 -msgid "``emailAddress``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_at}``" msgstr "" -#: ../settings/security/third-party/saml.rst:84 -msgid "**SAML Attribute Name**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Address" msgstr "" -#: ../settings/security/third-party/saml.rst:86 -msgid "**SAML Attribute NameFormat**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.address}``" msgstr "" -#: ../settings/security/third-party/saml.rst:87 -msgid "``basic``" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Avatar" msgstr "" -#: ../settings/security/third-party/saml.rst:89 -msgid "" -"In the example above, we're telling Zammad that whenever it receives a SAML " -"login request, it should take the ``email`` property from Keycloak, look for " -"a Zammad user with the same ``email`` attribute, and create a new session " -"for that user." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/saml.rst:95 -msgid "" -"If your Keycloak users' email addresses are stored on another property (*e." -"g.,* ``username``), adjust accordingly." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Department" msgstr "" -#: ../settings/security/third-party/saml.rst:98 -msgid "" -"Back in **Settings**, enter the Client ID (``https://your.zammad.domain/auth/" -"saml/metadata``) in the field **Master SAML Processing URL**." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.department}``" msgstr "" -#: ../settings/security/third-party/saml.rst:101 -msgid "You also need to enable **Sign assertions**." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Email" msgstr "" -#: ../settings/security/third-party/saml.rst:105 -msgid "Step 2: Configure Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.email}``" msgstr "" -#: ../settings/security/third-party/saml.rst:107 -msgid "" -"Enable SAML and enter your IdP's details in the Admin Panel under **Settings " -"> Security > Third Party Applications > Authentication via SAML**:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Fax" msgstr "" -#: ../settings/security/third-party/saml.rst:None -msgid "Example configuration of SAML part 1" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.fax}``" msgstr "" -#: ../settings/security/third-party/saml.rst:119 -msgid "Display name" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Firstname" msgstr "" -#: ../settings/security/third-party/saml.rst:116 -msgid "" -"Allows you to define a custom button name for SAML. This helps your users to " -"understand better what the button on the login page does." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.firstname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:119 -msgid "Defaults to ``SAML``." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Lastname" msgstr "" -#: ../settings/security/third-party/saml.rst:123 -msgid "IDP SSO target URL" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.lastname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:122 -msgid "" -"This is the target URL Zammad shall redirect to when the user presses the " -"SAML button. For Keycloak, this needs to look like https://your.domain/" -"realms/your-realm/protocol/saml" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Login" msgstr "" -#: ../settings/security/third-party/saml.rst:127 -msgid "IDP single logout target URL" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.login}``" msgstr "" -#: ../settings/security/third-party/saml.rst:126 -msgid "" -"This is the URL to which the single logout request and response should be " -"sent." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Mobile" msgstr "" -#: ../settings/security/third-party/saml.rst:131 -msgid "IDP certificate" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.mobile}``" msgstr "" -#: ../settings/security/third-party/saml.rst:130 -msgid "" -"The public certificate of your IDP for Zammad to verify during the callback " -"phase." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Note" msgstr "" -#: ../settings/security/third-party/saml.rst:145 -msgid "IDP certificate fingerprint" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.note}``" msgstr "" -#: ../settings/security/third-party/saml.rst:134 -msgid "" -"The fingerprint of your IDPs public certificate to verify during callback " -"phase." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Phone" msgstr "" -#: ../settings/security/third-party/saml.rst:137 -msgid "🔏 **For the IdP certificate / certificate fingerprint:**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.phone}``" msgstr "" -#: ../settings/security/third-party/saml.rst:139 -msgid "" -"Provide **only one or the other**—do not provide both! (Between the two, we " -"recommend the signing certificate itself: fingerprints use SHA-1, which `has " -"been broken for a while now `_.)" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > VIP" msgstr "" -#: ../settings/security/third-party/saml.rst:144 -msgid "" -"**Keycloak users:** Find your certificate in the Keycloak admin panel under " -"**Realm Settings > Keys > Algorithm: RS256 > Certificate**." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.vip}``" msgstr "" -#: ../settings/security/third-party/saml.rst:151 -msgid "Name identifier format" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``false`` or ``true``" msgstr "" -#: ../settings/security/third-party/saml.rst:148 -msgid "" -"This is the unique identifiers field type. Usually it should be ``urn:oasis:" -"names:tc:SAML:1.1:nameid-format:emailAddress``." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Web" msgstr "" -#: ../settings/security/third-party/saml.rst:151 -msgid "Zammad **expects an email address as unique identifier**!" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.web}``" msgstr "" -#: ../settings/security/third-party/saml.rst:155 -msgid "UID attribute name" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > VIP" msgstr "" -#: ../settings/security/third-party/saml.rst:154 -msgid "" -"Here you can define an attribute that uniquely identifies the user. If " -"unset, the name identifier returned by the IDP is used." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.vip}``" msgstr "" -#: ../settings/security/third-party/saml.rst:None -msgid "Example configuration of SAML part 2" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Web" msgstr "" -#: ../settings/security/third-party/saml.rst:163 -msgid "" -"Decide if the certificate for the connection to the IdP service has to be " -"verified or not (default: ``yes``)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.web}``" msgstr "" -#: ../settings/security/third-party/saml.rst:169 -msgid "Signing & Encrypting" +#: ../misc/variables/ticket.rst:6 +msgid "" +"Below you can find all available ticket-based variables within Zammad. These " +"can be called via triggers for example. If you're unsure if Zammad does " +"support variables at the point you're at, you can try to type ``::`` to " +"check." msgstr "" -#: ../settings/security/third-party/saml.rst:169 -msgid "" -"Define if you want to sign, encrypt, do both or nothing for the requests." +#: ../misc/variables/ticket.rst:12 +msgid "Ticket Variables" msgstr "" -#: ../settings/security/third-party/saml.rst:179 -msgid "Certificate (PEM)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Accounted Time" msgstr "" -#: ../settings/security/third-party/saml.rst:172 -msgid "" -"Paste the public certificate of your Zammad SAML client, if you want to " -"encrypt the requests." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.time_unit}``" msgstr "" -#: ../settings/security/third-party/saml.rst:175 -msgid "Make sure the certificate is:" +#: ../misc/variables/ticket.rst:1 +msgid "``1``, ``2.75`` or empty response" msgstr "" -#: ../settings/security/third-party/saml.rst:177 -msgid "already valid and not yet expired" +#: ../misc/variables/ticket.rst:1 +msgid "``3``, any number of articles existing in the ticket right now" msgstr "" -#: ../settings/security/third-party/saml.rst:178 -msgid "no CA certificate" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Closing time" msgstr "" -#: ../settings/security/third-party/saml.rst:179 -msgid "valid for signing and encrypting" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.close_at}``" msgstr "" -#: ../settings/security/third-party/saml.rst:185 -msgid "Private key (PEM)" +#: ../misc/variables/ticket.rst:1 +msgid "2019-10-07 17:25:00 UTC" msgstr "" -#: ../settings/security/third-party/saml.rst:182 -msgid "" -"Paste the private key of your Zammad SAML client here, if you want to sign " -"the requests." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created at" msgstr "" -#: ../settings/security/third-party/saml.rst:185 -msgid "Make sure the key is an RSA key with a length of at least 2048 bits." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_at}``" msgstr "" -#: ../settings/security/third-party/saml.rst:188 -msgid "Private key secret" +#: ../misc/variables/ticket.rst:1 +msgid "2019-10-07 16:25:00 UTC" msgstr "" -#: ../settings/security/third-party/saml.rst:188 -msgid "If your private key is secured with a secret, you can provide it here." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Address" msgstr "" -#: ../settings/security/third-party/saml.rst:192 -msgid "Your callback URL" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.address}``" msgstr "" -#: ../settings/security/third-party/saml.rst:191 -msgid "" -"This URL is needed for your IdP configuration so it knows where to redirect " -"to after successful authentication." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Avatar" msgstr "" -#: ../settings/security/third-party/saml.rst:194 -msgid "" -"After saving your input by clicking on the \"Submit\" button, Zammad " -"verifies the provided keys/certificates (e.g. if they are valid for signing/" -"encrypting and if they aren't expired)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/saml.rst:199 -msgid "" -"See :ref:`automatic account linking ` for details " -"on how to link existing Zammad accounts to IdP accounts." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Department" msgstr "" -#: ../settings/security/third-party/saml.rst:205 -msgid "Automatic account linking doesn't work" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.department}``" msgstr "" -#: ../settings/security/third-party/saml.rst:206 -msgid "" -"Have you double-checked your IdP's user attribute mapping configuration?" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Email" msgstr "" -#: ../settings/security/third-party/twitter.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via Twitter. To do " -"so, you need to follow these steps:" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.email}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:8 -msgid "Register Twitter App" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Fax" msgstr "" -#: ../settings/security/third-party/twitter.rst:10 -msgid "Go to https://dev.twitter.com/apps and login with your account." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.fax}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:15 -msgid "Click on \"Create App\"" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Firstname" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "new app page" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.firstname}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:20 -msgid "" -"Enter app settings. As \"Callback URL\" you need to enter ``https://" -"zammad_host/api/v1/external_credentials/twitter/callback``. You need to " -"replace ``zammad_host`` with the domain of your Zammad system." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Lastname" msgstr "" -#: ../settings/security/third-party/twitter.rst:24 -msgid "" -"After the app has been created, update the application icon and organization " -"attributes." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.lastname}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "set permissions to receive and send direct messages" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Login" msgstr "" -#: ../settings/security/third-party/twitter.rst:30 -msgid "" -"Next we need to set ``read, write and access direct messages`` permissions " -"for the app." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.login}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "click on Keys & Access Token, note them" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Mobile" msgstr "" -#: ../settings/security/third-party/twitter.rst:36 -msgid "" -"Go to \"Keys and Access Token\" tab and note the \"Consumer Key\" and " -"\"Consumer Secret\"." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.mobile}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:40 -msgid "Configure Zammad as Twitter App" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Note" msgstr "" -#: ../settings/security/third-party/twitter.rst:42 -msgid "" -"Go to \"Admin > Security > Twitter > Third Party Applications > Twitter\" " -"Section." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.note}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "Admin > Security > Third Party Applications" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Phone" msgstr "" -#: ../settings/security/third-party/twitter.rst:48 -msgid "" -"Fill in the \"Twitter Key\" and the \"Twitter Secret\" and click the " -"\"Submit\" button." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.phone}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:51 -msgid "" -"Now you can link accounts via \"Avatar > Profile > Link Accounts\" or login " -"via Zammad login page." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > VIP" msgstr "" -#: ../settings/security/two-factor.rst:11 -msgid "Two-factor Authentication Methods" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.vip}``" msgstr "" -#: ../settings/security/two-factor.rst:2 -msgid "Two-Factor Authentication" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Web" msgstr "" -#: ../settings/security/two-factor.rst:4 -msgid "" -"Two-factor authentication (2FA) enhances the security of Zammad accounts by " -"adding an extra layer of verification beyond a password. It requires users " -"to provide two different types of authentication factors, typically " -"something they know (like a password) and something they possess (like a " -"mobile device or a security token), to ensure that only authorized " -"individuals can access the account." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.web}``" msgstr "" -#: ../settings/security/two-factor.rst:19 -msgid "Enable Recovery Codes" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Address" msgstr "" -#: ../settings/security/two-factor.rst:21 -msgid "" -"Recovery codes are one-time use security codes that can be used by the user " -"if they lose access to their other two-factor authentication methods. They " -"cannot be used on their own, they can only be activated if at least one two-" -"factor authentication method is enabled." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.address}``" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Enable Recovery Codes Setting" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Avatar" msgstr "" -#: ../settings/security/two-factor.rst:30 -msgid "" -"Recovery codes can only be used as a backup method. If enabled, they will be " -"automatically generated for the user once they set up their initial two-" -"factor authentication method." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.avatar(60,60)}``" msgstr "" -#: ../settings/security/two-factor.rst:34 -msgid "" -"The user will be asked to print out or save the generated recovery codes in " -"a safe place. Once used, a recovery code cannot be reused." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Department" msgstr "" -#: ../settings/security/two-factor.rst:37 -msgid "" -"Users will also have an option to regenerate their recovery codes at any " -"time, which invalidates already existing recovery codes and provides them " -"with a list of fresh codes." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.department}``" msgstr "" -#: ../settings/security/two-factor.rst:41 -msgid "" -"After you enable this setting, when the user completes a setup of their " -"initial two-factor authentication method, they will be presented with a list " -"of recovery codes and instructed to save them for later use." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Email" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Recovery Codes Generation Modal Dialog" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.email}``" msgstr "" -#: ../settings/security/two-factor.rst:50 -msgid "Enforce the Set Up of the Two-Factor Authentication" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Fax" msgstr "" -#: ../settings/security/two-factor.rst:52 -msgid "" -"In case you wish to require your users to set up at least one two-factor " -"authentication method for their account, you can do this by selecting " -"specific user roles the requirement applies to in **Enforced for user " -"roles** setting. Of course you must have at least one two-factor " -"authentication method enabled for this setting to take effect." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.fax}``" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Enforced for User Roles Setting" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Firstname" msgstr "" -#: ../settings/security/two-factor.rst:62 -msgid "" -"After you change this setting, if the user has one of the selected roles on " -"their account, they will be forced to set up the two-factor authentication " -"upon next sign in or application reload." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.firstname}``" msgstr "" -#: ../settings/security/two-factor.rst:66 -msgid "" -"A modal dialog with instructions will be shown, and they will not be able to " -"do any work before they set up at least one two-factor method." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Lastname" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Modal Dialog for Enforcing Two-Factor Authentication Set Up" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.lastname}``" msgstr "" -#: ../settings/security/two-factor.rst:74 -msgid "Reset Two-Factor Authentication for a Specific User" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Login" msgstr "" -#: ../settings/security/two-factor.rst:76 -msgid "" -"In case an user isn't able to login anymore because of an inaccessible " -"second factor, you can reset the user's 2FA method." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.login}``" msgstr "" -#: ../settings/security/two-factor.rst:79 -msgid "" -"To do this, go to the user management and search for the relevant user. " -"After you found the account, click the button in the action column and " -"select \"Manage Two-Factor Authentication\":" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Mobile" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Context menu in action column in user management" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.mobile}``" msgstr "" -#: ../settings/security/two-factor.rst:87 -msgid "" -"After selecting this, you can see a dialog where you can either reset one " -"2FA method or reset all of the user's 2FA methods:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Note" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Dialog for resetting user's 2FA method" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.note}``" msgstr "" -#: ../settings/security/two-factor.rst:94 -msgid "" -"Choose the fitting one, click on the corresponding \"Remove ...\" button and " -"confirm your action. The user now has to setup a new 2FA method, depending " -"on your 2FA configuration." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Phone" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:2 -msgid "Authenticator App" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.phone}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:4 -msgid "" -"The authenticator app method is a type of two-factor authentication that " -"uses a mobile application to generate one-time codes for account " -"verification. After setting up the authenticator app on their device, the " -"user links it to their Zammad account." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > VIP" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:12 -msgid "" -"When logging in, the user is prompted to enter a time-sensitive code " -"generated by the app, in addition to their password. This code acts as the " -"second factor of authentication, providing an extra layer of security as it " -"changes periodically and is unique to the user's device." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.vip}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:None -msgid "Security Code in Google Authenticator App" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Web" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:22 -msgid "" -"The app generates codes based on a shared secret key stored securely on both " -"the user's device and the server, ensuring a synchronized and secure " -"authentication process. The method of generating the codes is sometimes also " -"called TOTP (time-based one-time password)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.web}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:28 -msgid "Enabling the Authenticator App Method" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Escalation at" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:30 -#: ../settings/security/two-factor/security-keys.rst:28 -msgid "To enable the method, just toggle the switch on in the settings." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.escalation_at}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:None -msgid "Authenticator App Switch in Settings" +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:36 -msgid "" -"Now the users will be able to set up this two-factor authentication method " -"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " -"Once they do, on next sign-in with password, they will be asked to provide " -"an additional security code generated by their mobile device." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > First response" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:2 -msgid "Security Keys" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.first_response_at}``" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:4 -msgid "" -"The security keys method is a type of a two-factor authentication that uses " -"Web Authentication API in the browser for verifying user's identity. The " -"user can register multiple hardware or software security keys with their " -"Zammad account and then they can use it during the sign-in process." +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable yet" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:12 -msgid "" -"When logging in, the user is prompted to provide the same security key they " -"registered with their account, in addition to their password. This key acts " -"as the second factor of authentication, providing an extra layer of security." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Assign Follow-Ups" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:None -msgid "Security Key dialog in Safari on macOS" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_assignment}``" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:21 -msgid "" -"The type of the key can range from hardware USB sticks to passkeys stored in " -"a device of user's choice. Which type can be used depends on the browser " -"flavor and the platform of the user." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Assignment Timeout" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:26 -msgid "Enabling the Security Keys Method" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.assignment_timeout}``" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:None -msgid "Security Keys Switch in Settings" +#: ../misc/variables/ticket.rst:1 +msgid "``20`` or empty if not configured" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:34 -msgid "" -"Now the users will be able to set up this two-factor authentication method " -"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " -"Once they do, on next sign-in with password, they will be asked to provide " -"the same security key they registered during the setup." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Follow-up possible" msgstr "" -#: ../settings/system/system-selfhosted.include.rst:3 -msgid "" -"Below settings are only available to self hosted users. In hosted " -"environments we're handling these settings for you to ensure service " -"stability." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_possible}``" msgstr "" -#: ../settings/system/base.rst:11 -msgid "Fully Qualified Domain Name" +#: ../misc/variables/ticket.rst:1 +msgid "``no`` or ``yes``" msgstr "" -#: ../settings/system/base.rst:7 -msgid "The URL of your Zammad installation." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Name" msgstr "" -#: ../settings/system/base.rst:9 ../settings/system/base.rst:17 -msgid "This setting is used within :doc:`/system/variables` and notifications." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.name}``" msgstr "" -#: ../settings/system/system-base.include.rst:1 -msgid "It is automatically set by the *Getting Started wizard*." +#: ../misc/variables/ticket.rst:1 +msgid "``Sales``" msgstr "" -#: ../settings/system/system-base.include.rst:5 -msgid "Changing this setting also changes callback URLs for your channels etc." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Note" msgstr "" -#: ../settings/system/system-base.include.rst:6 -msgid "This setting can have negative affects on being able to login." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.note}``" msgstr "" -#: ../settings/system/base.rst:19 -msgid "HTTP type" +#: ../misc/variables/ticket.rst:1 +msgid "``Note about this group``" msgstr "" -#: ../settings/system/base.rst:14 -msgid "" -"The HTTP type tells your installation how your clients connect. This is " -"relevant for authentication and cookie security." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > ID" msgstr "" -#: ../settings/system/base.rst:31 -msgid "SystemID" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.id}``" msgstr "" -#: ../settings/system/base.rst:22 -msgid "" -"This ID is being used within your ticket number. In case you're " -"communicating with another ticket system with similar ticket number schemes " -"this ID greatly reduces the risk of false follow ups." +#: ../misc/variables/ticket.rst:1 +msgid "``17``, ``5281``, ..." msgstr "" -#: ../settings/system/base.rst:26 -msgid "" -"The SystemID is randomly selected upon installation of Zammad (``1-99``)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact (agent)" msgstr "" -#: ../settings/system/base.rst:30 -msgid "" -"**Do not** change this setting in a productive system! Your Zammad " -"installation may no longer recognize old ticket number based follow ups upon " -"change!" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_agent_at}``" msgstr "" -#: ../settings/system/frontend.rst:2 -msgid "Frontend" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact (customer)" msgstr "" -#: ../settings/system/frontend.rst:22 -msgid "Core Workflow Ajax Mode" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_customer_at}``" msgstr "" -#: ../settings/system/frontend.rst:6 +#: ../misc/variables/ticket.rst:1 msgid "" -"This setting allows administrators to enforce :doc:`/system/core-workflows` " -"to use Ajax-Calls instead of web sockets. You'll usually only need this if " -"you experience serious issues as noted below." +"``2019-10-07 16:25:00 UTC`` or empty if not applicable yet (Please note " +"`Ticket last contact behavior Settings `_ for this)" msgstr "" -#: ../settings/system/frontend.rst:10 -msgid "**🤓 Possible (technical) reasons**" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact" msgstr "" -#: ../settings/system/frontend.rst:12 -msgid "" -"In some cases, your network structure (e.g. firewalls, proxies) may " -"disconnect long web socket connections. This leads to select fields staying " -"empty (e.g. owner selection *after* selecting your group) or fields not " -"shown / hidden (e.g. when switching to or from pending states, the \"pending " -"till\" field not showing / hiding)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_at}``" msgstr "" -#: ../settings/system/frontend.rst:18 -msgid "" -"Please keep in mind that the Ajax fallback may cause serious pressure on " -"your application server. If you have the choice stick to web sockets." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Number" msgstr "" -#: ../settings/system/frontend.rst:22 -msgid "Default: ``no`` (inactive)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.number}``" msgstr "" -#: ../settings/system/frontend.rst:53 -msgid "Show calendar weeks in the picker of date/datetime fields" +#: ../misc/variables/ticket.rst:1 +msgid "``31001``, ``201910731001``, ..." msgstr "" -#: ../settings/system/frontend.rst:25 -msgid "" -"With this setting you can instruct Zammad to provide week number display " -"globally for all users. Calendar with week number display are usually used " -"in business sectors and may not be relevant for everyone." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain based assignment" msgstr "" -#: ../settings/system/frontend.rst:29 -msgid "" -"This setting affects *all areas* - you'll also see week numbers in the admin " -"panel for e.g. triggers and macros." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain_assignment}``" msgstr "" -#: ../settings/system/frontend.rst:32 -msgid "Default: ``no`` (not shown)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain" msgstr "" -#: ../settings/system/frontend.rst:53 -msgid "Here's the difference:" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain}``" msgstr "" -#: ../settings/system/frontend.rst:0 -msgid "Screenshot showing Zammad's date picker (in the default way)" +#: ../misc/variables/ticket.rst:1 +msgid "``domain.tld`` or empty if not set" msgstr "" -#: ../settings/system/frontend.rst:41 -msgid "Set to ``no``" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Name" msgstr "" -#: ../settings/system/frontend.rst:0 -msgid "" -"Screenshot showing Zammad's date picker with\n" -"week numbers enabled" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.name}``" msgstr "" -#: ../settings/system/frontend.rst:50 -msgid "Set to ``yes``" +#: ../misc/variables/ticket.rst:1 +msgid "``Zammad GmbH`` or empty if not set" msgstr "" -#: ../settings/system/index.rst:4 -msgid "" -"For your overview we split each tab within system settings into its own page:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Note" msgstr "" -#: ../settings/system/index.rst:16 -msgid "Console Based Settings" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.note}``" msgstr "" -#: ../settings/system/index.rst:18 -msgid "" -"There's some console based settings we didn't put into the UI. However, you " -"may find them helpful - you can find them in our :docs:`hidden settings ` section." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Shared organization" msgstr "" -#: ../settings/system/network.rst:2 -msgid "Network" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.shared}``" msgstr "" -#: ../settings/system/network.rst:8 -msgid "" -"The proxy settings can only be saved after successfully testing the proxy " -"connection." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > VIP" msgstr "" -#: ../settings/system/network.rst:15 -msgid "Proxy Address." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.vip}``" msgstr "" -#: ../settings/system/network.rst:12 -msgid "" -"Allows you to provide a proxy server if needed. This is relevant for network " -"communication by Zammad." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Address" msgstr "" -#: ../settings/system/network.rst:15 -msgid "It **does not** affect the update process or Elasticsearch." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.address}``" msgstr "" -#: ../settings/system/network.rst:18 -msgid "Username for proxy connection." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Avatar" msgstr "" -#: ../settings/system/network.rst:18 -msgid "" -"If your proxy server requires authentication, provide the username here." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.avatar(60,60)}``" msgstr "" -#: ../settings/system/network.rst:21 -msgid "Password for proxy connection." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Department" msgstr "" -#: ../settings/system/network.rst:21 -msgid "" -"If your proxy server requires authentication, provide the password here." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.department}``" msgstr "" -#: ../settings/system/network.rst:26 -msgid "No proxy for the following hosts." +#: ../misc/variables/ticket.rst:1 +msgid "``Support`` or empty if not set" msgstr "" -#: ../settings/system/network.rst:24 -msgid "" -"Exception list for hosts you can't or don't want to reach via proxy server." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Email" msgstr "" -#: ../settings/system/network.rst:27 -msgid "Default: ``localhost,127.0.0.0,::1``" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.email}``" msgstr "" -#: ../settings/system/services.rst:2 -msgid "Services" +#: ../misc/variables/ticket.rst:1 +msgid "``agent@company.tld`` or empty if not set" msgstr "" -#: ../settings/system/services.rst:10 -msgid "Image Service" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Fax" msgstr "" -#: ../settings/system/services.rst:5 -msgid "Defines the backend for user and organization image lookups." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.fax}``" msgstr "" -#: ../settings/system/services.rst:7 -msgid "Default: ``Zammad Image Service`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Firstname" msgstr "" -#: ../settings/system/services.rst:9 -msgid "" -"Make sure your on premise installation has ``HTTPS`` access to ``images." -"zammad.com``." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.firstname}``" msgstr "" -#: ../settings/system/services.rst:18 -msgid "Geo Calendar Service" +#: ../misc/variables/ticket.rst:1 +msgid "``Max`` or empty if not set" msgstr "" -#: ../settings/system/services.rst:13 -msgid "" -"Defines the backend for geo calendar lookups. Used for initial calendar " -"setup." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Lastname" msgstr "" -#: ../settings/system/services.rst:16 -msgid "Default: ``Zammad GeoCalendar Service`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.lastname}``" msgstr "" -#: ../settings/system/services.include.rst:2 -msgid "" -"Make sure your on premise installation has ``HTTPS`` access to ``geo.zammad." -"com``." +#: ../misc/variables/ticket.rst:1 +msgid "``Mustermann`` or empty if not set" msgstr "" -#: ../settings/system/services.rst:26 -msgid "Geo IP Service" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Login" msgstr "" -#: ../settings/system/services.rst:21 -msgid "" -"Defines the backend for geo IP lookups. Shows also location of an IP address " -"if an IP address is shown." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.login}``" msgstr "" -#: ../settings/system/services.rst:24 -msgid "Default: ``Zammad GeoIP Service`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "``agent``" msgstr "" -#: ../settings/system/services.rst:32 -msgid "Geo Location Service" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Mobile" msgstr "" -#: ../settings/system/services.rst:29 -msgid "" -"Defines the backend for geo location lookups to store geo locations for " -"addresses." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.mobile}``" msgstr "" -#: ../settings/system/services.rst:32 -msgid "" -"Default: ``OpenStreetMap (ODbL 1.0, http://osm.org/copyright)`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Note" msgstr "" -#: ../settings/system/services.rst:36 -msgid "" -"You can find a detailed privacy information on what we store for how long on " -"our :docs:`Privacy Appendix ` inside of our System " -"Documentation." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.note}``" msgstr "" -#: ../settings/system/storage.rst:2 -msgid "Storage" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Phone" msgstr "" -#: ../settings/system/storage.rst:6 -msgid "" -"Here you can define where Zammad stores attachments for tickets and the " -"knowledge base. By default, we're writing to the ``Database`` - you can " -"switch to ``Filesystem`` or ``Simple Storage (S3)`` at any time. In this " -"case please have a look on the following instructions." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.phone}``" msgstr "" -#: ../settings/system/storage.rst:11 -msgid "" -"If you have a busy Zammad instance, we strongly encourage you to use " -"filesystem storage instead of \"Database\". This will greatly improve system " -"performance (de-crease database load and size)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > VIP" msgstr "" -#: ../settings/system/storage.rst:19 -msgid "Database" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.vip}``" msgstr "" -#: ../settings/system/storage.rst:17 -msgid "" -"This is the default storage method. The attachments are stored directly in " -"the database. If your Zammad instance grows, we recommend one of the other " -"methods to maintain performance." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Web" msgstr "" -#: ../settings/system/storage.rst:38 -msgid "Filesystem" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.web}``" msgstr "" -#: ../settings/system/storage.rst:22 -msgid "" -"This storage method is recommended for all Zammad instances, especially for " -"those with a higher load. If you choose filesystem, your files are written " -"to ``/opt/zammad/storage/``." +#: ../misc/variables/ticket.rst:1 +msgid "``https://zammad.com`` or empty if not set" msgstr "" -#: ../settings/system/storage.rst:26 -msgid "" -"Moving attachments from \"Database\" to \"Filesystem\" can be run during " -"production use. However, you should consider your framework conditions (e.g. " -"bandwidth, system load in production) to define the right moment." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Pending till" msgstr "" -#: ../settings/system/storage.rst:32 -msgid "**You noticed slow updates of Zammad?**" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.pending_time}``" msgstr "" -#: ../settings/system/storage.rst:34 -msgid "" -"While Zammad is beeing updated, it enforces a recursive \"change " -"owner\" (chown) for this directory. For instances with many files this can " -"be time consuming. To mitigate that you can move your files and create a " -"symlink in ``/opt/zammad/storage/`` to the new directory. Of course you have " -"to make sure on your own that the permissions are always correct." +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not set" msgstr "" -#: ../settings/system/storage.rst:95 -msgid "Simple Storage (S3)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Priority > Name" msgstr "" -#: ../settings/system/storage.rst:41 -msgid "" -"To use the Simple Storage (S3), you have to provide some settings, which " -"can't be accessed in the UI (see instructions below)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.priority.name}``" msgstr "" -#: ../settings/system/storage.rst:44 -msgid "" -"⚠️ Please note that the current implementation is in its early stages and can " -"be modified in the future." +#: ../misc/variables/ticket.rst:1 +msgid "``2 normal``" msgstr "" -#: ../settings/system/storage.rst:47 -msgid "" -"The prerequisite is to have access to a S3-compatible storage and to have " -"all necessary parameters available (which depends on your storage provider; " -"if in doubt, please ask there for help)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > State > Name" msgstr "" -#: ../settings/system/storage.rst:51 -msgid "Steps to configure S3:" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.state.name}``" msgstr "" -#: ../settings/system/storage.rst:53 -msgid "" -"Copy ``config/zammad/storage.yml.dist`` to ``config/zammad/storage.yml``" +#: ../misc/variables/ticket.rst:1 +msgid "``new``, ``open``, ..." msgstr "" -#: ../settings/system/storage.rst:54 -msgid "Edit the copied file in one of the following ways:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Tags" msgstr "" -#: ../settings/system/storage.rst:56 -msgid "" -"Either provide your S3 configuration with one attribute per line like in the " -"upper area of the file" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.tags}``" msgstr "" -#: ../settings/system/storage.rst:58 +#: ../misc/variables/ticket.rst:1 msgid "" -"Or provide your S3 configuration as an URL (which you can find at the end of " -"the file). Note: you can also provide this URL as environment variable (:" -"docs:`see system documentation `) without using this yml-file." +"Currently not available, see `Issue 2769 `_" msgstr "" -#: ../settings/system/storage.rst:62 -msgid "" -"We recommend the deletion of the not used configuration style to avoid " -"inconsistencies." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Title" msgstr "" -#: ../settings/system/storage.rst:65 -msgid "Restart Zammad so the config file / environment variable is loaded" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.title}``" msgstr "" -#: ../settings/system/storage.rst:66 +#: ../misc/variables/ticket.rst:1 msgid "" -"Set the \"Storage Method\" in Zammad to ``Simple Storage (S3)`` in Settings " -"> System > Storage and click on \"Submit\". After that, Zammad checks your " -"configuration and the connection to the service and will raise an error " -"message if something is wrong." +"``My amazing Subject`` (normally subject, can be edited within Interface and " +"thus differ)" msgstr "" -#: ../settings/system/storage.rst:72 -msgid "A very simple storage configuration could look like this:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated at" msgstr "" -#: ../settings/system/storage.rst:85 -msgid "" -"Before setting the storage method to ``Simple Storage (S3)`` (step 4), " -"please make sure to have a working setup." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_at}``" msgstr "" -#: ../settings/system/storage.rst:88 -msgid "" -"You can verify this by running ``rails r 'Rails.logger = Logger.new(STDOUT); " -"pp Store::Provider::S3.ping?'`` in your Zammad directory. If everything is " -"fine, you should see ``true``, else you should see ``false`` and a simple " -"error message." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Address" msgstr "" -#: ../settings/system/storage.rst:93 -msgid "" -"If you installed Zammad through a package manager (rather than from source), " -"replace ``rails r`` with ``zammad run rails r`` above. To learn more, see :" -"docs:`Administration via Console `." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.address}``" msgstr "" -#: ../settings/ticket.rst:4 -msgid "" -"Here you can adjust general ticket settings. Additional ones for the ticket " -"composer interface can be found in the :doc:`/misc/composer`." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Avatar" msgstr "" -#: ../settings/ticket.rst:11 -msgid "Ticket Hook (default: ``Ticket#``)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.avatar(60,60)}``" msgstr "" -#: ../settings/ticket.rst:11 -msgid "The identifier for a ticket; *e.g.,* Ticket#, Call#, MyTicket#." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Department" msgstr "" -#: ../settings/ticket.rst:38 -msgid "Ticket Hook Position (default: ``right``)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.department}``" msgstr "" -#: ../settings/ticket.rst:14 -msgid "" -"With this setting you can decide (if) where to insert the ticket number." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Email" msgstr "" -#: ../settings/ticket.rst:20 -msgid "*Right*" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.email}``" msgstr "" -#: ../settings/ticket.rst:17 -msgid "" -"This setting will add the ticket reference on the right site of the subject." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Fax" msgstr "" -#: ../settings/ticket.rst:20 -msgid "Example: ``Some Subject [Ticket#12345]``" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.fax}``" msgstr "" -#: ../settings/ticket.rst:26 -msgid "*Left*" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Firstname" msgstr "" -#: ../settings/ticket.rst:23 -msgid "" -"This setting will add the ticket reference on the left site of the subject." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.firstname}``" msgstr "" -#: ../settings/ticket.rst:26 -msgid "Example: ``[Ticket#12345] Some Subject``" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Lastname" msgstr "" -#: ../settings/ticket.rst:29 -msgid "*None*" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.lastname}``" msgstr "" -#: ../settings/ticket.rst:29 -msgid "This will completely remove ticket references from the subject." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Login" msgstr "" -#: ../settings/ticket.rst:33 -msgid "" -"Please ensure to take a look at :doc:`/channels/email/settings` within the " -"email channel to ensure you have at least one reference that helps Zammad to " -"assign follow-ups correctly." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.login}``" msgstr "" -#: ../settings/ticket.rst:37 -msgid "" -"Disabling this and not setting up any further follow up search will lead to " -"unexpected results!" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Mobile" msgstr "" -#: ../settings/ticket.rst:65 -msgid "" -"Ticket Last Contact Behaviour (default: ``Use the start time of the last " -"customer thread (which may consist of multiple articles).``)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.mobile}``" msgstr "" -#: ../settings/ticket.rst:41 -msgid "" -"This setting changes the way Zammad updates the ``Last Contact`` value of a " -"ticket. This is fairly important for overviews and what you expect upon " -"ticket updates of a customer." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Note" msgstr "" -#: ../settings/ticket.rst:52 -msgid "" -"Use the start time of the last customer thread (which may consist of " -"multiple articles)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.note}``" msgstr "" -#: ../settings/ticket.rst:46 -msgid "" -"If this option is chosen, Zammad will update the last updated value just " -"once if a customer replies. After that, Zammad will wait for an agent to " -"react." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Phone" msgstr "" -#: ../settings/ticket.rst:50 -msgid "" -"This comes in handy if you want to work tickets in the order of their first " -"update. This will not change ticket orders if customers decide to \"bump\" " -"the ticket affected." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.phone}``" msgstr "" -#: ../settings/ticket.rst:57 -msgid "Use the time of the very last customer article." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > VIP" msgstr "" -#: ../settings/ticket.rst:55 -msgid "" -"When setting this option, Zammad will always update the last updated value. " -"This means that if ordering by ``Last Update``, ticket orders will change if " -"customers \"bump\" the ticket." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.vip}``" msgstr "" -#: ../settings/ticket.rst:64 -msgid "Last contact value used on :doc:`/manage/overviews`" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Web" msgstr "" -#: ../settings/ticket.rst:65 -msgid "Last contact value used on :doc:`/manage/trigger`" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.web}``" msgstr "" -#: ../settings/ticket.rst:88 -msgid "" -"Ticket Organization Reassignment (default: ``Update the most recent tickets." -"``)" +#: ../settings/branding.rst:10 +msgid "Product Name" msgstr "" -#: ../settings/ticket.rst:68 +#: ../settings/branding.rst:7 msgid "" -"This setting changes the way Zammad updates the organization field of the " -"tickets whenever the primary organization of a user is changed." -msgstr "" - -#: ../settings/ticket.rst:74 -msgid "Update the most recent tickets." +"Defines the name of the application, shown in the web interface, tabs and " +"title bar of the web browser." msgstr "" -#: ../settings/ticket.rst:72 -msgid "" -"If this option is chosen, Zammad will update the 100 most recent tickets " -"where the user is the ticket customer. The ticket organization field will be " -"automatically set to the new primary organization of the user." +#: ../settings/branding.rst:10 +msgid "Default value: ``Zammad Helpdesk``" msgstr "" -#: ../settings/ticket.rst:88 -msgid "Do not update any tickets." +#: ../settings/branding.rst:13 +msgid "Will be shown in the app and is included in email footers." msgstr "" -#: ../settings/ticket.rst:77 -msgid "" -"When choosing this option, Zammad will not update any tickets when the " -"user's primary organization is changed." +#: ../settings/branding.rst:19 +msgid "Logo" msgstr "" -#: ../settings/ticket.rst:80 -msgid "**Use with care!**" +#: ../settings/branding.rst:16 +msgid "Defines the logo of the application, shown in the login page of Zammad." msgstr "" -#: ../settings/ticket.rst:82 +#: ../settings/branding.rst:18 msgid "" -"Using this option may lead to inconsistencies in the system as the ticket " -"organization may become decoupled from the ticket customer." +"Ensure to hit the \"Submit\" button after uploading the logo. Otherwise your " +"change will not be saved." msgstr "" -#: ../settings/ticket.rst:85 +#: ../settings/branding.rst:22 msgid "" -"However, you may use this option if you wish to maintain :ref:`the shared " -"access ` to the ticket for all organization " -"members of the original organization of the customer." +"Allows to set the default language of the Zammad instance. The here defined " +"locale mostly acts as a fallback for:" msgstr "" -#: ../settings/ticket.rst:110 -msgid "Ticket Number Format (default: ``Increment (SystemID.Counter)``)" +#: ../settings/branding.rst:25 +msgid "user preferences (if Zammad can't detect the users locale)" msgstr "" -#: ../settings/ticket.rst:94 -msgid "" -"This setting defines the way Zammad's ticket number will look. Changing this " -"setting in production will cause follow up detection to fail." +#: ../settings/branding.rst:26 +msgid "CSV output (reporting, time accounting)" msgstr "" -#: ../settings/ticket.rst:102 -msgid "Increment (SystemID.Counter)" +#: ../settings/branding.rst:30 +msgid "Define the timezone of your Zammad installation." msgstr "" -#: ../settings/ticket.rst:98 +#: ../settings/branding.rst:32 msgid "" -"The increment value contains the SystemID (automatically generated during " -"installation) and a increment which counts up with every new Ticket. The " -"increment will automatically get another digit if needed." +"This does not have any effect on timings for your agents or how Zammad " +"stores date and time values." msgstr "" -#: ../settings/ticket.rst:102 -msgid "Examples: ``1010138``, ``1010139``" +#: ../settings/branding.rst:35 +msgid "Changing this value has direct consequences on the following areas:" msgstr "" -#: ../settings/ticket.rst:110 -msgid "Date (Year.Month.Day.SystemID.Counter)" +#: ../settings/branding.rst:37 +msgid ":doc:`/manage/scheduler` tasks" msgstr "" -#: ../settings/ticket.rst:105 -msgid "" -"This version of the ticket number is fairly long. However, because it " -"contains the date of ticket creation, it also allows you to see when the " -"ticket has been created. You may feel familiar with this number format if " -"you've worked with OTRS already." +#: ../settings/branding.rst:38 +msgid "search indexing (and thus reporting)" msgstr "" -#: ../settings/ticket.rst:110 -msgid "Examples: ``201206231010138``, ``201206231010139``" +#: ../settings/branding.rst:40 +msgid "calendar subscriptions" msgstr "" -#: ../settings/ticket.rst:137 -msgid "OPTIONS" +#: ../settings/branding.rst:41 +msgid "browser printing" msgstr "" -#: ../settings/ticket.rst:113 +#: ../settings/branding.rst:43 msgid "" -"The below options allow you to further customize your ticket number. The " -"availability of options differ depending of the chosen ticket number format " -"above." +"Please note that some of above are fallbacks in case Zammad could not detect " +"the agents timezone correctly." msgstr "" -#: ../settings/ticket.rst:122 -msgid "Checksum (default: ``no``)" +#: ../settings/branding.rst:77 +msgid "Pretty Date" msgstr "" -#: ../settings/ticket.rst:118 +#: ../settings/branding.rst:47 msgid "" -"If set to yes, we'll built a checksum to further \"unique\" the ticket " -"number of your system. If you're dealing with many other ticket systems this " -"might help to prevent false positive follow up detection on tickets." +"This setting allows you to define how Zammad should display time stamps " +"within the interface to all users." msgstr "" -#: ../settings/ticket.rst:122 -msgid "This will also add another digit to the ticket number." +#: ../settings/branding.rst:50 +msgid "" +"This does not have any effect on how Zammad returns e.g. time values via " +"variables." msgstr "" -#: ../settings/ticket.rst:137 -msgid "Min. size of Number (default: ``5``)" +#: ../settings/branding.rst:77 +msgid "Choose in between the following options:" msgstr "" -#: ../settings/ticket.rst:125 -msgid "" -"This setting defines the minimum length of your ticket number. If your " -"counter is not yet high enough, Zammad will fill the number with zeros to " -"ensure the wanted length." +#: ../settings/branding.rst:64 +msgid "relative" msgstr "" -#: ../settings/ticket.rst:129 +#: ../settings/branding.rst:55 msgid "" -"Please note that the minimum length is ``3`` (SystemID + at least one digit " -"if below 10). Also, if the length is no longer long enough, the number will " -"automatically get one digit longer. Ticket-Numbers **do not overflow**, thus " -"it's save to keep it at 5 or set it lower if wanted." +"This timestamp shows a relative time span until it switches to a date. Over " +"time, it will change as follows:" msgstr "" -#: ../settings/ticket.rst:135 -msgid "" -"This option is only available if ticket number format is set to " -"``Increment``!" +#: ../settings/branding.rst:58 +msgid "just now" msgstr "" -#: ../settings/ticket.rst:142 -msgid "Auto-Assignment" +#: ../settings/branding.rst:59 +msgid "5 minutes ago" msgstr "" -#: ../settings/ticket.rst:144 -msgid "" -"In a larger Zammad environment, it happens that several agents open the same " -"ticket at the same time. Although collision detection is then effective, the " -"efficiency of processing can be increased by means of the automatic " -"assignment of tickets when a ticket is opened." +#: ../settings/branding.rst:60 +msgid "3 days 1 hour ago" msgstr "" -#: ../settings/ticket.rst:149 -msgid "" -"The automatic assignment of tickets can be activated and configured in the " -"admin area under Settings > Ticket > Auto Assignment." +#: ../settings/branding.rst:61 +msgid "``03/04/2022``" msgstr "" -#: ../settings/ticket.rst:152 -msgid "" -"The auto assignment only works if the ticket has no owner yet. By default, " -"the agent can always reset the ticket owner to ``-`` if needed." +#: ../settings/branding.rst:63 +msgid "Hovering the timestamp helps, you'll always get a clean timestamp then." msgstr "" -#: ../settings/ticket.rst:155 -msgid "" -"If you want to use this function for only specific tickets, you can " -"configure the conditions accordingly to meet your requirement. By default " -"the condition affects all tickets with the state ``open``." +#: ../settings/branding.rst:71 +msgid "absolute" msgstr "" -#: ../settings/ticket.rst:161 +#: ../settings/branding.rst:67 msgid "" -"If you need to exclude users (e.g. a group leader), you can search and " -"select the desired agents in the ``Exception Users`` list. The search " -"function in this area is only effective, if you have too many agents to " -"display at once to help you with the configuration." +"This timestamp always includes the week day. For one week after creation, " +"the timestamp will not contain the date itself: Thursday 18:35." msgstr "" -#: ../settings/ticket.rst:167 -msgid "Notifications" +#: ../settings/branding.rst:71 +msgid "After a week it will switch to: ``Friday 4. Mar 16:00``." msgstr "" -#: ../settings/ticket.rst:191 -msgid "Default Notifications" +#: ../settings/branding.rst:76 +msgid "timestamp" msgstr "" -#: ../settings/ticket.rst:170 +#: ../settings/branding.rst:74 msgid "" -"This setting allows you to configure the default ticket notifications that " -"will be applied to all new agent users (incl. users who were just assigned " -"agent role). Simply change the notification matrix to desired state and " -"press **Save**." +"This will cause Zammad to show a complete timestamp according to your locale " +"defaults. For English this could be e.g. ``2022/12/03 2:40 pm`` or for " +"German e.g. ``12.03.2022 14:40``." msgstr "" -#: ../settings/ticket.rst:175 -msgid "" -"In case an agent already exists, their ticket notification preferences will " -"be preserved. Optionally, you can also **Apply current defaults to all " -"agents**." +#: ../settings/branding.rst:78 +msgid "Default setting: ``relative``." msgstr "" -#: ../settings/ticket.rst:181 -msgid "" -"**Potential time-consuming action:** Applying default ticket notifications " -"to all agent users may take some time to complete, be patient! The exact " -"time will depend on the size of your system and the number of agents." +#: ../settings/security.rst:2 +msgid "Security" msgstr "" -#: ../settings/ticket.rst:185 +#: ../settings/security.rst:4 msgid "" -"**Active agents only!** When current default ticket notifications are " -"applied, only active agent users are considered. In case an agent is re-" -"activated *after* this action, they will still have the old notification " -"configuration." +"For your overview we split each tab within security settings into its own " +"page:" msgstr "" -#: ../settings/ticket.rst:190 +#: ../settings/security/base.rst:2 ../settings/system/base.rst:2 +#: ../settings/ticket.rst:8 +msgid "Base" +msgstr "" + +#: ../settings/security/base.rst:5 +msgid "New User Accounts" +msgstr "" + +#: ../settings/security/base.rst:9 msgid "" -"In case you want to go back to the initial state of ticket notifications, " -"you can click on **Reset to default** button." +"Activates the `register as a new customer` function on the login page. If " +"set to ``no`` only administrators or agents can create new accounts manually." msgstr "" -#: ../settings/ticket.rst:194 ../settings/ticket.rst:196 -msgid "Duplicate Detection" +#: ../settings/security/base.rst:13 ../settings/security/base.rst:38 +#: ../settings/security/base.rst:66 +msgid "Default setting: ``yes``" msgstr "" -#: ../settings/ticket.rst:236 ../settings/ticket.rst:238 -msgid "Detect Duplicate Ticket Creation" +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"New User Accounts\" setting" msgstr "" -#: ../settings/ticket.rst:197 ../settings/ticket.rst:199 +#: ../settings/security/base.rst:22 msgid "" -"This setting turns on the duplicate ticket detection mechanism during ticket " -"creation. If similar tickets are found in the system, a suitable warning " -"will be shown to the user trying to create a ticket." +"Deactivation of above function **does not** deactivate automatic account " +"creation! This means: If a user writes e.g. an email to Zammad and has no " +"account yet, Zammad will automatically create the account. User accounts are " +"a direct dependency of tickets and thus technically mandatory." msgstr "" -#: ../settings/ticket.rst:204 ../settings/ticket.rst:206 -msgid "A Sample Duplicate Ticket Warning" +#: ../settings/security/base.rst:29 +msgid "Lost Password" msgstr "" -#: ../settings/ticket.rst:206 ../settings/ticket.rst:208 +#: ../settings/security/base.rst:33 msgid "" -"You can choose which ticket attributes will be matched by selecting them in " -"**Attributes to compare** field. Only if the ticket attribute value provided " -"by the user in the ticket create form is *equal* with the attribute in an " -"existing ticket, the warning will be shown." +"Activates the `lost password` function on the login page. If set to ``no`` " +"only administrators may change the user's password - users may update their " +"own password if they're still logged in and they have the required :doc:" +"`permission `." msgstr "" -#: ../settings/ticket.rst:211 ../settings/ticket.rst:213 -msgid "**Warning title** and **Warning message** are configurable as well." +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"Lost Password\" setting" msgstr "" -#: ../settings/ticket.rst:213 ../settings/ticket.rst:215 +#: ../settings/security/base.rst:49 msgid "" -"You can limit the detection only to certain user roles. By default, only " -"agents will see the warning." +"With third party authentications - but especially LDAP - you may want to " +"disable this function. Zammad **will not** change third party login " +"passwords and instead set or change the local password!" msgstr "" -#: ../settings/ticket.rst:216 ../settings/ticket.rst:218 -msgid "" -"If you don't want to show the matched tickets as part of the warning, you " -"can set **Show matching ticket(s) in the warning** setting to *no*." +#: ../settings/security/base.rst:56 +msgid "Password Login" msgstr "" -#: ../settings/ticket.rst:219 ../settings/ticket.rst:221 +#: ../settings/security/base.rst:60 msgid "" -"By default, **Permission level for looking up ticket** is set to *User*, " -"which means user permissions will be honored during sarch. The user will " -"see the warning only if tickets they have access to are matched. " -"Alternatively, you can set this setting to *System*, in which case the " -"search will happen within *all* tickets in the system, regardless of user " -"permissions." +"Activates the username & password login by default and if no third-party " +"login is activated. Disabling password login on the Zammad login page only " +"takes effect if you enable any :doc:`third-party`." msgstr "" -#: ../settings/ticket.rst:225 ../settings/ticket.rst:227 -msgid "**🦺 Safety first!**" +#: ../settings/security/base.rst:64 +msgid "See :doc:`third-party` for supported third-party logins." msgstr "" -#: ../settings/ticket.rst:227 ../settings/ticket.rst:229 -msgid "" -"Even if the permission level is set to *System*, the user will not be shown " -"the tickets they don't have access to in the warning, even if they match." +#: ../settings/security/base.rst:0 +msgid "Figure showing de-activated \"Password Login\" setting" msgstr "" -#: ../settings/ticket.rst:231 ../settings/ticket.rst:233 +#: ../settings/security/base.rst:77 msgid "" -"However, just the confirmation about the existence of the tickets in the " -"system may be considered an unwanted information disclosure. Use this option " -"carefully!" +"To help administrators to overcome \"login issues\", Zammad automatically " +"offers a password request for administrator users. This allows you to adjust " +"Third-Party applications even if the login does no longer work!" msgstr "" -#: ../settings/ticket.rst:235 ../settings/ticket.rst:237 -msgid "" -"Finally, you can configure between matching within **All tickets** or **Open " -"tickets** only by setting **Match tickets in following states**. Depending " -"on the current ticket state, a ticket may or not be matched." +#: ../settings/security/base.rst:84 +msgid "Session Timeout" msgstr "" -#: ../system/core-workflows.rst:2 -msgid "Core Workflows" +#: ../settings/security/base.rst:86 +msgid "" +"All settings below by default are set to ``4 weeks``. Session Timeout " +"defines the life time of a users session. As soon as it's reached, Zammad " +"will automatically log off the session in question." msgstr "" -#: ../system/core-workflows.rst:4 +#: ../settings/security/base.rst:91 msgid "" -"Core Workflows allow you to adjust object attributes in many ways. For " -"example:" +"Zammad takes the highest value set assigned for the user based on the " +"permissions." msgstr "" -#: ../system/core-workflows.rst:7 -msgid "show / hide fields" +#: ../settings/security/base.rst:94 +msgid "``admin``" msgstr "" -#: ../system/core-workflows.rst:8 -msgid "adjust mandatory setting" +#: ../settings/security/base.rst:96 +msgid "``ticket.customer``" msgstr "" -#: ../system/core-workflows.rst:9 -msgid "manipulate available options" +#: ../settings/security/base.rst:97 +msgid "``default`` (fallback if user doesn't have above permissions set)" msgstr "" -#: ../system/core-workflows.rst:11 +#: ../settings/security/base.rst:99 msgid "" -"With this, you can provide exactly the information your users really need!" +"All settings act independently from each other allowing you to disable the " +"timeouts for e.g. admins, but not agents." msgstr "" -#: ../system/core-workflows.rst:15 -msgid "" -"If the pre-defined :doc:`/system/objects` are not enough, please add them " -"beforehand." +#: ../settings/security/base.rst:115 +#: ../system/integrations/checkmk/api-reference.rst:13 +msgid "Example" msgstr "" -#: ../system/core-workflows.rst:17 -msgid "" -"If you experience slow or unreliable field updates, please see :ref:`Core " -"Workflow Ajax Modus `" +#: ../settings/security/base.rst:107 +msgid "Let's suppose you configured the following session timeouts" msgstr "" -#: ../system/core-workflows.rst:22 -msgid "" -"This is a very enhanced functionality and can cause unexpected UI behavior. " -"Please ensure to test your use cases after configuration to reduce surprises." +#: ../settings/security/base.rst:104 +msgid "default: 3 weeks" msgstr "" -#: ../system/core-workflows.rst:None -msgid "Dialogue for adding a new workflow" +#: ../settings/security/base.rst:105 +msgid "admin: 2 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:2 -msgid "Core Workflow Condition Operators" +#: ../settings/security/base.rst:106 +msgid "ticket.agent: 4 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:4 -msgid "" -"You might know that there is a separate section for explaining :doc:" -"`condition operators `. Head over there to " -"see a detailed explanation of many conditions and operators." +#: ../settings/security/base.rst:107 +msgid "ticket.customer: 1 week" msgstr "" -#: ../system/core-workflows/condition-operators.rst:8 -msgid "" -"Due to differences to other places in Zammad which are also using conditions " -"(e.g. triggers), you can find a dedicated description of operators for core " -"workflows below." +#: ../settings/security/base.rst:115 +msgid "This results in the following situations" msgstr "" -#: ../system/core-workflows/condition-operators.rst:12 -msgid "" -"Be aware that the availability of the operators depends on the selected " -"attribute and its field type. Some of the operators may only be available " -"for system attributes (e.g. for \"tags\", \"active\")." +#: ../settings/security/base.rst:110 +msgid "a user with ``admin`` permission will have a timeout of 2 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:20 -msgid "Operator" +#: ../settings/security/base.rst:111 +msgid "" +"a user with ``admin`` and ``ticket.agent`` permissions will have a timeout " +"of 2 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:22 -msgid "after (absolute)" +#: ../settings/security/base.rst:113 +msgid "" +"a user with ``ticket.customer`` permission will have a timeout of 1 week" msgstr "" -#: ../system/core-workflows/condition-operators.rst:23 -msgid "Matches if a date/time is after a specific point in time." +#: ../settings/security/base.rst:115 +msgid "" +"a user with neither ``admin``, ``ticket.agent`` nor ``ticket.customer`` " +"permissions will have a timeout of 3 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:24 -msgid "after (relative)" +#: ../settings/security/password.rst:4 +msgid "" +"This section allows you to define password requirements for the local user " +"accounts." msgstr "" -#: ../system/core-workflows/condition-operators.rst:25 -msgid "Matches if a time span after a specified event has passed." +#: ../settings/security/password.rst:9 +msgid "" +"Zammad does **not** allow you to change your LDAP password, instead, it will " +"set a password in its local database which might confuse your users. This " +"might be addressed in the future by `#1169 `_." msgstr "" -#: ../system/core-workflows/condition-operators.rst:26 -msgid "before (absolute)" +#: ../settings/security/password.rst:14 +msgid "**Exception for admins**" msgstr "" -#: ../system/core-workflows/condition-operators.rst:27 -msgid "Matches if a date/time is before a specific point in time." +#: ../settings/security/password.rst:16 +msgid "" +"Please note that below password policies *do not* affect administrators " +"setting passwords on user accounts. While this seems strange and not safe we " +"believe that an administrator knowing an user's password is insecure as well." msgstr "" -#: ../system/core-workflows/condition-operators.rst:28 -msgid "before (relative)" +#: ../settings/security/password.rst:21 +msgid "The suggested workflow is either:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:29 -msgid "Matches if a time span after a specified event has not passed." +#: ../settings/security/password.rst:23 +msgid "" +"to use third party logins to not require local passwords at all **- or -**" msgstr "" -#: ../system/core-workflows/condition-operators.rst:30 -msgid "contains" +#: ../settings/security/password.rst:25 +msgid "to require your *user to reset the password* upon first login." msgstr "" -#: ../system/core-workflows/condition-operators.rst:31 -msgid "Matches if a specified value is present." +#: ../settings/security/password.rst:27 +msgid "" +"This way administrators are not required to set a user's password at all!" msgstr "" -#: ../system/core-workflows/condition-operators.rst:33 -msgid "Matches if all of the specified values are present." +#: ../settings/security/password.rst:31 +msgid "Maximum Failed Logins" msgstr "" -#: ../system/core-workflows/condition-operators.rst:35 -msgid "Matches if none of the specified values are present." +#: ../settings/security/password.rst:33 +msgid "" +"You can choose a value between ``4`` and ``20``. This defines how often a " +"login to a user account may fail until Zammad will lock it. Your users can " +"always use the \"forgot password\" function to change their password and " +"unlock their account." msgstr "" -#: ../system/core-workflows/condition-operators.rst:36 -msgid "contains not" +#: ../settings/security/password.rst:38 +msgid "The default value is ``10``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:37 -msgid "Matches if a specified value is not present." +#: ../settings/security/password.rst:42 +msgid "Beside changing the user's password, you can also unlock accounts via" msgstr "" -#: ../system/core-workflows/condition-operators.rst:39 -msgid "Matches if one specified value is present." +#: ../settings/security/password.rst:44 +msgid ":ref:`user management list `" msgstr "" -#: ../system/core-workflows/condition-operators.rst:41 -msgid "Matches if one specified value is not present." +#: ../settings/security/password.rst:45 +msgid ":docs:`console `" msgstr "" -#: ../system/core-workflows/condition-operators.rst:42 -msgid "does not match regex" +#: ../settings/security/password.rst:46 +msgid ":docs:`API `" msgstr "" -#: ../system/core-workflows/condition-operators.rst:43 -msgid "Matches if content doesn't fit to regex rule." +#: ../settings/security/password.rst:50 +msgid "Failed logins via LDAP no longer lock accounts." msgstr "" -#: ../system/core-workflows/condition-operators.rst:44 -msgid "ends with" +#: ../settings/security/password.rst:53 +msgid "2 Lower Case And 2 Upper Case Characters" msgstr "" -#: ../system/core-workflows/condition-operators.rst:45 -msgid "Matches if content ends with specified value." +#: ../settings/security/password.rst:55 +msgid "" +"You can add complexity to passwords by enforcing at least 2 upper and lower " +"case characters." msgstr "" -#: ../system/core-workflows/condition-operators.rst:46 -msgid "ends with one of" +#: ../settings/security/password.rst:58 ../settings/security/password.rst:83 +msgid "The default value is ``no``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:47 -msgid "Matches if content ends with one of the specified values." +#: ../settings/security/password.rst:62 +msgid "Minimum Length" msgstr "" -#: ../system/core-workflows/condition-operators.rst:48 -msgid "from (relative)" +#: ../settings/security/password.rst:64 +msgid "" +"This defines the minimum password length required for users to provide (from " +"``4`` to ``20``)." msgstr "" -#: ../system/core-workflows/condition-operators.rst:49 -msgid "Matches if date/time is after a period of time after an event." +#: ../settings/security/password.rst:67 +msgid "The default value is ``6``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:51 -msgid "Matches if content is equal to a specified value." +#: ../settings/security/password.rst:71 +msgid "Digit Required" msgstr "" -#: ../system/core-workflows/condition-operators.rst:52 -msgid "is any of" +#: ../settings/security/password.rst:73 +msgid "This enforces your users to use at least one digit within the password." msgstr "" -#: ../system/core-workflows/condition-operators.rst:53 -msgid "Matches if content is equal to any of specified values." +#: ../settings/security/password.rst:75 +msgid "The default value is ``yes``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:54 -msgid "is modified" +#: ../settings/security/password.rst:78 +msgid "Special Character Required" msgstr "" -#: ../system/core-workflows/condition-operators.rst:55 -msgid "Matches if content is modified." +#: ../settings/security/password.rst:80 +msgid "" +"This setting allows you to improve your password quality even more by " +"enforcing the password to contain at least one special character." msgstr "" -#: ../system/core-workflows/condition-operators.rst:57 -#: ../system/core-workflows/condition-operators.rst:61 -msgid "True from the moment of changing content until form submit." +#: ../settings/security/ssl-certificates.rst:2 +msgid "SSL Certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:58 -msgid "is modified to" +#: ../settings/security/ssl-certificates.rst:7 +msgid "" +"Zammad offers the possibility to upload custom certificates and custom " +"Certificate Authority (CA) certificates. This can be useful if you want to " +"connect Zammad the secure way to other systems which are using custom " +"certificates." msgstr "" -#: ../system/core-workflows/condition-operators.rst:59 -msgid "Matches if content is modified to a specific value." +#: ../settings/security/ssl-certificates.rst:12 +msgid "" +"An example usecase might be: You have an internal LDAP server that is not " +"accessible from the internet, and you want a SSL-encrypted connection, using " +"a custom certificate." msgstr "" -#: ../system/core-workflows/condition-operators.rst:62 -msgid "is none of" +#: ../settings/security/ssl-certificates.rst:19 +msgid "" +"You should have an existing custom certificate file and/or a custom CA " +"certificate file, which you want to add to Zammad. As filetype ``.crt`` is " +"supported and the certificate format has to be PEM (Base64 ASCII)." msgstr "" -#: ../system/core-workflows/condition-operators.rst:63 -msgid "Matches if content is none of any specified values." +#: ../settings/security/ssl-certificates.rst:25 +msgid "" +"When you import a custom CA certificate, all certificates generated with " +"this are trusted. This can be useful if you have more than one system/" +"certificate you want to connect to and the certificates are issued from the " +"same custom CA." msgstr "" -#: ../system/core-workflows/condition-operators.rst:65 -msgid "Matches if content is not equal to a specified value." +#: ../settings/security/ssl-certificates.rst:31 +msgid "Add a Certificate" msgstr "" -#: ../system/core-workflows/condition-operators.rst:67 -msgid "Matches if content is present." +#: ../settings/security/ssl-certificates.rst:33 +msgid "" +"To add a custom certificate or a custom CA certificate, head over to the " +"Admin panel > Settings > Security > SSL Certificates. Here you can find a " +"\"Add SSL Certificate\" button. In the dialog you can either select a " +"certificate file or paste the content of the certificate:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:68 -msgid "just changed" +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate adding dialog" msgstr "" -#: ../system/core-workflows/condition-operators.rst:69 -msgid "Matches if content has changed." +#: ../settings/security/ssl-certificates.rst:43 +msgid "" +"After selecting a file or pasting the content of the certificate, click on " +"the \"Add\" button to finally upload it to Zammad. Then, the certificates " +"are immediately effective, no restart or similar required." msgstr "" -#: ../system/core-workflows/condition-operators.rst:71 -#: ../system/core-workflows/condition-operators.rst:75 +#: ../settings/security/ssl-certificates.rst:49 msgid "" -"Only true for the moment of changing content until next form field action/" -"click." +"Please note that only single certificate files are supported. That means if " +"you want to import a certificate / CA certificate, it must contain **only " +"one** certificate." msgstr "" -#: ../system/core-workflows/condition-operators.rst:72 -msgid "just changed to" +#: ../settings/security/ssl-certificates.rst:54 +msgid "Certificate Overview" msgstr "" -#: ../system/core-workflows/condition-operators.rst:73 -msgid "Matches if content has changed to a specified value." +#: ../settings/security/ssl-certificates.rst:56 +msgid "" +"After you added a certificate, you can see a table with information for each " +"added certificate:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:76 -msgid "matches regex" +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing table of added certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:77 -msgid "Matches if value fits to regex rule." -msgstr "" - -#: ../system/core-workflows/condition-operators.rst:79 -msgid "Matches if no content is present." -msgstr "" - -#: ../system/core-workflows/condition-operators.rst:80 -msgid "starts with" +#: ../settings/security/ssl-certificates.rst:64 +msgid "" +"Here you can download the certificate or delete it, if you don't need it " +"anymore." msgstr "" -#: ../system/core-workflows/condition-operators.rst:81 -msgid "Matches if content starts with specified value." +#: ../settings/security/ssl-certificates.rst:68 +msgid "Deleting Certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:82 -msgid "starts with one of" +#: ../settings/security/ssl-certificates.rst:70 +msgid "" +"If you want to delete a specific certificate, you can do it by clicking on " +"the menu in the actions column and selecting delete:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:83 -msgid "Matches if content starts with one of the specified values." +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate deletion button" msgstr "" -#: ../system/core-workflows/condition-operators.rst:84 -msgid "till (relative)" +#: ../settings/security/ssl-certificates.rst:79 +msgid "Downloading Certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:85 -msgid "Matches if date/time is before a period of time before an event." +#: ../settings/security/ssl-certificates.rst:81 +msgid "" +"If you want to download your certificates, you can do this as well via " +"corresponding action buttons." msgstr "" -#: ../system/core-workflows/condition-operators.rst:86 -msgid "today" +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate download button" msgstr "" -#: ../system/core-workflows/condition-operators.rst:87 -msgid "Matches if date/time is today." +#: ../settings/security/third-party.rst:13 +msgid "Login Providers" msgstr "" -#: ../system/core-workflows/condition-operators.rst:88 -msgid "within last (relative)" +#: ../settings/security/third-party.rst:2 +msgid "Third-Party Applications" msgstr "" -#: ../system/core-workflows/condition-operators.rst:89 +#: ../settings/security/third-party.rst:4 msgid "" -"Matches if date/time content is within specified period of time before now." +"Third party authentication is a great way to help your users to login to " +"Zammad more easily. If the account is yet unknown, Zammad will create a new " +"user automatically, without the user needed to interact (e.g. type in his " +"name). Another big advantage of this feature is that your user doesn't need " +"to remember another password." msgstr "" -#: ../system/core-workflows/condition-operators.rst:91 -msgid "within next (relative)" +#: ../settings/security/third-party.rst:10 +msgid "" +"You can deactivate logging in via :ref:`security_password_login` if any of " +"the mentioned authentication providers are enabled in your instance." msgstr "" -#: ../system/core-workflows/condition-operators.rst:92 +#: ../settings/security/third-party.rst:27 msgid "" -"Matches if date/time content is within specified period of time after now." +"We're currently missing documentation for the following login providers:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:2 -msgid "How do they work?" +#: ../settings/security/third-party.rst:29 +msgid "LinkedIn" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:4 -msgid "" -"Core Workflows are executed according to their priority. If two workflows " -"have the same priority, they are executed in alphabetical order based on " -"their **name**." +#: ../settings/security/third-party.rst:30 +msgid "Weibo" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:8 -msgid "" -"Because of the way Core Workflows work, all changes to attributes are " -"checked with the application server - please see :doc:`limitations` for " -"possible issues." +#: ../settings/security/third-party.rst:35 +msgid "Automatic Account Link on Initial Logon" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:12 +#: ../settings/security/third-party.rst:37 msgid "" -"Below we're talking about settings that are important and not self-" -"explanatory." +"In general there's two possible options for Zammad on how to deal with " +"already known users as they try to authenticate against a third-party " +"application. By default, Zammad will not automatically link \"unknown\" " +"authentication providers to existing accounts." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:17 +#: ../settings/security/third-party.rst:42 msgid "" -"Choose the object context you want to run the workflow in. This will decide " -"on your available attributes and actions." -msgstr "" - -#: ../system/core-workflows/how-do-they-work.rst:20 -msgid "Ticket objects also have access to the ticket customer." +"This means that the user has to manually link authentication providers to " +"their accounts (for more about this :user-docs:`consult the user " +"documentation `)." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:25 +#: ../settings/security/third-party.rst:46 msgid "" -"Choose in which situation the workflow is applied. Contexts can be combined " -"to avoid duplicate workflows." +"Sometimes this doesn't come in handy as this also means you'll receive error " +"messages about \"email address being in use already\" for (yet) unknown " +"third-party authentication methods." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:30 -msgid "Creation mask" +#: ../settings/security/third-party.rst:50 +msgid "" +"If you want to allow your users to always be able to log in, no matter what, " +"you may want to enable ``Automatic account link on initial logon``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:29 +#: ../settings/security/third-party.rst:None msgid "" -"If selected, your conditions and actions will affect all applicable creation " -"masks." +"Screenshot highlighting the \"Automatic account link on initial logon\"\n" +"setting" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:34 -msgid "Edit mask" +#: ../settings/security/third-party.rst:60 +msgid "Automatic Account Linking Notification" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:33 +#: ../settings/security/third-party.rst:64 msgid "" -"If selected, your conditions and actions will affect all applicable edit " -"masks." +"To improve security and your users awareness, you can enable Zammad to " +"notify your users when a new third-party application has been linked to " +"their account." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:39 +#: ../settings/security/third-party.rst:68 msgid "" -"Zammad differentiates between selected and saved conditions. These can be " -"combined wherever needed." +"This notification is sent out once per third-party application. Zammad does " +"also mention the method used, e.g.: ``Microsoft``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:42 -msgid "**⚠️ Restrict workflows to specific roles if needed!**" +#: ../settings/security/third-party.rst:71 +msgid "By default this setting is not active (set to ``no``)." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:44 +#: ../settings/security/third-party.rst:0 msgid "" -"By default and unless configured in conditions, workflow rules are executed " -"for **all roles**. This also affects your customers!" +"Screenshot showing sample notification mail after initial\n" +"third-party linking" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:50 -msgid "Selected Conditions" +#: ../settings/security/third-party.rst:85 +msgid "" +"This notification is only sent if the account in question already exists. If " +"the login via the third-party also creates the missing account, the " +"notification will be skipped." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:48 -msgid "" -"These conditions are based on form values and match if an appropriate " -"selection is made (e.g. choosing another group in the ticket without " -"saving). This applies for drafts (active selection) and currently saved " -"values." +#: ../settings/security/third-party.rst:89 +msgid "This means it only affects:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:64 -msgid "Saved Conditions" +#: ../settings/security/third-party.rst:91 +msgid "manual account linking within the third-party page of the users profile" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:53 +#: ../settings/security/third-party.rst:92 msgid "" -"These conditions only match if the selected values are stored in the " -"database. It ignores the current value or selection of the field, as long as " -"the changes are not saved (e.g. performing field operations for an existing " -"ticket, which is viewed/opened by an agent)." +"logging into an existing local account by utilizing the *automatic account " +"link on initial logon* functionality" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:60 +#: ../settings/security/third-party.rst:None msgid "" -"Keep in mind that the value has to be available in the situation where you " -"need it. Otherwise the condition won't match." +"Screenshot showing the \"automatic account linking notification\"\n" +"setting" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:63 -msgid "" -"Example: you can't perform any actions with *saved condition* on a ticket in " -"creation, because there are no saved values at that time." +#: ../settings/security/third-party.rst:100 +msgid "No User Creation on Logon" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:66 +#: ../settings/security/third-party.rst:102 msgid "" -"You can find a description of the condition operators for core workflows :" -"doc:`here `." +"By default, Zammad will create a new user account if the user logs in via a " +"third-party application and the account doesn't exist yet." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:72 +#: ../settings/security/third-party.rst:105 msgid "" -"Which actions should we run on the relevant fields? The possible actions " -"depend on the object type. However, usually you can at least change the " -"visibility and whether the field is mandatory." +"If you want to prevent Zammad from creating new accounts on logon, you can " +"disable this feature by setting ``No user creation on logon`` to ``yes``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:76 -msgid "Be aware that actions are not available for **related** context." +#: ../settings/security/third-party.rst:None +msgid "Screenshot showing the \"no user creation on logon\" setting" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:78 +#: ../settings/security/third-party/facebook.rst:4 msgid "" -"**Example:** Let's assume you are working in the ticket context. While you " -"can have customer *conditions*, you *can't adjust* objects with actions in " -"that scope. That's because this wouldn't have any impact on the ticket " -"dialog. Of course all ticket attributes (state, owner, ...) are available." +"It is possible to create a quick login for your helpdesk via Facebook To do " +"so, you need to follow these steps:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:84 +#: ../settings/security/third-party/facebook.rst:9 +msgid "Register Facebook App" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:11 msgid "" -"Please also have a look at our :doc:`limitations` to be safe from surprises." +"Visit [https://developers.facebook.com/apps/] and click on \"Add a new App\"" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:88 -msgid "Available Operators" +#: ../settings/security/third-party/facebook.rst:None +msgid "initial page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:90 -msgid "The availability of operators depends on the object type and scope." +#: ../settings/security/third-party/facebook.rst:17 +msgid "After that enter the app settings" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:94 -msgid "" -"Please note that actions may or may not restrict API based access to " -"attributes. We're displaying the following icons for your overview to " -"understand these limits better:" +#: ../settings/security/third-party/facebook.rst:None +msgid "Create App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:0 -msgid "|api| This icon indicates the action affects the API." +#: ../settings/security/third-party/facebook.rst:22 +msgid "Navigate to \"Settings\" and fill in this infromation" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:163 -msgid "api" +#: ../settings/security/third-party/facebook.rst:None +msgid "App Settings" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:0 -msgid "|ui| This icon indicates the action only affects the web interface." +#: ../settings/security/third-party/facebook.rst:27 +msgid "Navigate to app review and Check \"Make [appname] public?\"" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:167 -msgid "ui" +#: ../settings/security/third-party/facebook.rst:None +msgid "App Review" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:102 -msgid "show |ui|" +#: ../settings/security/third-party/facebook.rst:35 +msgid "Configure Zammad as Facebook App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:102 -msgid "Display the chosen field. Allows setting of values." -msgstr "" - -#: ../system/core-workflows/how-do-they-work.rst:109 -msgid "hide |ui|" +#: ../settings/security/third-party/facebook.rst:37 +msgid "" +"Navigate to \"Admin -> Security -> Third Party Applications\" and enter the " +"App ID and the App Secret. You can find this Key in the Dashbard of your " +"Facebok app." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:105 -msgid "" -"Hide the chosen field. However, it technically still allows setting the " -"field." +#: ../settings/security/third-party/facebook.rst:None +msgid "Zammad Configuration" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:108 +#: ../settings/security/third-party/facebook.rst:44 +#: ../settings/security/third-party/github.rst:43 +#: ../settings/security/third-party/gitlab.rst:46 msgid "" -"Please note that the field is **not** gone and still contains an existing " -"value (if set)! Consider *remove* instead, if you want this field to be gone." +"Now you can link accounts via \"Avatar -> Profile -> Link Accounts\" or " +"login via Zammad login page." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:112 -msgid "remove |ui|" +#: ../settings/security/third-party/github.rst:2 +#: ../system/integrations/github.rst:2 +msgid "GitHub" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:112 -msgid "Entirely removes the field. The field value will not be evaluated." +#: ../settings/security/third-party/github.rst:4 +msgid "" +"It is possible to create a quick login for your helpdesk via GitHub. To " +"activate the quick login you need to enable OAuth for GitHub." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:115 -msgid "set mandatory |ui| |api|" +#: ../settings/security/third-party/github.rst:8 +msgid "Register GitHub App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:115 -msgid "Sets the field to mandatory." +#: ../settings/security/third-party/github.rst:10 +msgid "" +"Visit https://www.github.com/settings/applications/new and enter the app " +"settings. As callback URL enter \"https://zammad_host/auth/github/callback\" " +"where zammad_host has to be replaced with your Zammad FQDN" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:118 -msgid "set optional |ui| |api|" +#: ../settings/security/third-party/github.rst:None +msgid "Register OAuth app on www.github.com" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:118 -msgid "Sets the field to optional." +#: ../settings/security/third-party/github.rst:19 +msgid "Configure Zammad as GitHub App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:124 -msgid "add option |ui| |api|" +#: ../settings/security/third-party/github.rst:21 +msgid "" +"Enter the \"APP ID\" and the \"APP SECRET\" from the GitHub OAUTH " +"Applications Dashboard" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:121 -msgid "Allows adding options to tree selects or selects." +#: ../settings/security/third-party/github.rst:None +msgid "GitHub config in Zammad admin interface" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:123 +#: ../settings/security/third-party/github.rst:28 msgid "" -"You have to use the \"remove option\" before performing this action. It " -"allows you to use *existing* configured values." +"After you configured the GitHub credentials and activated the login method, " +"you should see a new icon on the login page." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:128 -msgid "remove option |ui| |api|" +#: ../settings/security/third-party/github.rst:None +msgid "GitHub logo on login page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:127 +#: ../settings/security/third-party/github.rst:34 msgid "" -"Allows removing options from tree selects or selects. It allows you to use " -"*existing* configured values." +"If you click on the icon you will be redirected to GitHub and see something " +"similar to this:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:134 -msgid "set fixed to |ui| |api|" +#: ../settings/security/third-party/github.rst:None +msgid "GitHub oauth page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:131 -msgid "Reduces the available options by your selection." +#: ../settings/security/third-party/github.rst:40 +#: ../settings/security/third-party/gitlab.rst:42 +msgid "" +"When you grant the access you will be redirected to your Zammad instance and " +"logged in as a customer." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:133 -msgid "" -"This reduces your workflows in terms of *add option* and *remove option*." +#: ../settings/security/third-party/gitlab.rst:2 +msgid "Gitlab" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:137 -msgid "fill in |ui|" +#: ../settings/security/third-party/gitlab.rst:4 +msgid "" +"It is possible to create a quick login for your helpdesk via Gitlab. To " +"activate the quick login you need to enable OAuth for Gitlab." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:137 -msgid "Allows filling in of string and integer fields with your values." +#: ../settings/security/third-party/gitlab.rst:8 +msgid "Register Gitlab App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:141 -msgid "fill in empty |ui|" +#: ../settings/security/third-party/gitlab.rst:10 +msgid "To register an app in Gitlab open your profile and select applications." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:140 +#: ../settings/security/third-party/gitlab.rst:12 msgid "" -"Allows filling in of string and integer fields with your values **if the " -"field is empty**." +"As callback URL enter \"https://zammad-fqdn/auth/gitlab/callback\" where " +"zammad-fqdn has to be replaced with your Zammad FQDN" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:144 -msgid "select |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Register OAuth app on gitlab instance" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:144 -msgid "Select a specific value within a select, tree select or boolean field." +#: ../settings/security/third-party/gitlab.rst:18 +msgid "Just select *read_user* under scopes as in the screenshot and save it." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:153 -msgid "auto select |ui|" +#: ../settings/security/third-party/gitlab.rst:21 +msgid "Configure Zammad as Gitlab App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:147 -msgid "Helps users with tree select and select fields:" +#: ../settings/security/third-party/gitlab.rst:23 +msgid "" +"Enter the \"APP ID\" and the \"APP SECRET\" from the Gitlab OAUTH " +"Applications Dashboard and your Gitlab-URL in the \"SITE\" field." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:149 -msgid "" -"If the field has only one option available for selection and no value yet, " -"the value will be automatically set." +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab config in Zammad admin interface" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:152 +#: ../settings/security/third-party/gitlab.rst:30 msgid "" -"This option only works if you have one value and doesn't work if there is " -"more than one option available." +"After you configured the Gitlab credentials and activated the login method, " +"you should see a new icon on the login page." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:157 -msgid "set readonly |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab logo on login page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:156 +#: ../settings/security/third-party/gitlab.rst:36 msgid "" -"Allows you to display an attribute as read only (which means no changes are " -"possible)." +"If you click on the icon you will be redirected to Gitlab and see something " +"similar to this:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:161 -msgid "unset readonly |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab oauth page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:160 +#: ../settings/security/third-party/google.rst:4 msgid "" -"In case a workflow set the field in question to read only, you can undo this " -"with option above." +"With some easy and fast steps, you can enable Zammad to authenticate your " +"users via Google." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:172 -msgid "Stop after match" +#: ../settings/security/third-party/google.rst:8 +msgid "Register a Google App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:174 +#: ../settings/security/third-party/google.rst:10 msgid "" -"Here you can decide if other workflows are executed after the current one." +"First of all, we need to create a new project - you can skip this step if " +"you already have one." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:176 +#: ../settings/security/third-party/google.rst:15 msgid "" -"If set to ``no`` (default), further workflows will be executed if they match " -"the condition. In this case, it is possible that your actions from the " -"current workflow can be overwritten by another workflow." +"Use this link to create a new project: https://console.cloud.google.com/" +"projectcreate" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:180 +#: ../settings/security/third-party/google.rst:18 msgid "" -"If set to ``yes``, no further worflows will be executed after the current " -"one." +"Now expand the menu, expand \"APIs & Services\" and select \"Credentials\". " +"Go to the tab \"OAuth consent screen\" first and ensure to fill in the " +"requested information - without doing so you can't create credentials!" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:184 -msgid "Priority" +#: ../settings/security/third-party/google.rst:None +msgid "Creating a consent screen" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:186 +#: ../settings/security/third-party/google.rst:25 msgid "" -"You can define the sequence, in which the workflows are executed. The " -"default value is ``500``." +"After filling in and saving the consent screen information, you can go to " +"the \"Credentials\" tab and create new \"OAuth client ID\"-Credentials." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:189 +#: ../settings/security/third-party/google.rst:28 msgid "" -"The workflows are executed in ascending order by their priority. That means " -"lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." +"Fill in the necessary information as follows and replace ``zammad_host`` " +"with your FQDN:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:2 -msgid "Learn by Example" +#: ../settings/security/third-party/google.rst:31 +msgid "**Application type** ``[x] Web application``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:4 -msgid "" -"This page provides some basic examples for Core Workflows. Of course you can " -"build much more complex workflows if needed." +#: ../settings/security/third-party/google.rst:34 +msgid "**Authorized JavaScript origins** ``https://zammad_host/``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:7 +#: ../settings/security/third-party/google.rst:37 msgid "" -"To learn about Core Workflows in detail, first go to :doc:`how-do-they-work`." +"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" +"callback``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:10 -msgid "Group Based Examples" +#: ../settings/security/third-party/google.rst:None +msgid "Adding a new OAuth client ID" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:12 +#: ../settings/security/third-party/google.rst:43 msgid "" -"All following workflows have the same base configurations. The workflow may " -"not use them all." +"After creating the credentials, go to your Zammad installation and navigate " +"to \"Admin > Security > Third Party Applications\" > Google. Enter your " +"Client ID and Client secret here." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:15 -msgid "Groups:" +#: ../settings/security/third-party/google.rst:None +msgid "Zammad" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:20 -msgid "Attributes:" +#: ../settings/security/third-party/google.rst:50 +msgid "After submitting, the login via Google can be used." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:22 -msgid "Category (Single tree selection field, not mandatory, agents only)" +#: ../settings/security/third-party/microsoft.rst:2 +msgid "Microsoft" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:23 +#: ../settings/security/third-party/microsoft.rst:4 msgid "" -"Approved (Boolean field, not mandatory, not shown, ``false`` as default)" +"Zammad's Microsoft connection allows your users with Microsoft accounts to " +"login. This works for Azure users as well and can be an alternative to :doc:" +"`/system/integrations/ldap/index`." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:24 -msgid "Operating System (Text field, not mandatory, not shown)" +#: ../settings/security/third-party/microsoft.rst:10 +msgid "" +"This documentation part does not cover our :doc:`📧 Microsoft 365 email " +"channel `." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:25 -msgid "Software used (Single selection field, not mandatory, not shown)" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screenshot showing Microsoft login button on Zammad login screen." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:68 -msgid "Group specific values and fields" +#: ../settings/security/third-party/microsoft.rst:30 +#: ../settings/security/third-party/microsoft.rst:53 +msgid "Supported account types:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:28 +#: ../settings/security/third-party/microsoft.rst:22 msgid "" -"This workflow set depends on the category field. It reduces the available " -"set of values based on the group selected." +"Please note that Zammad only supports these account types (App dependent):" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:33 -msgid "Workflow 2nd Level group" +#: ../settings/security/third-party/microsoft.rst:35 +msgid "Avatars of signing in users:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:35 +#: ../settings/security/third-party/microsoft.rst:33 msgid "" -"This reduces the category options to ``2nd Level/*``, ``Internal/*`` and " -"``Others``. It also sets further required fields to mandatory and visible." -msgstr "" - -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for 2nd level" +"Zammad currently ignores user avatars. If the user is registered with e.g. " +"Gravatar, Zammad will fetch the avatar from there if enabled. See :doc:" +"`Zammad Image Service ` for more." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:43 -msgid "Workflow Support group" +#: ../settings/security/third-party/microsoft.rst:38 +msgid "Step 1 - Register a Microsoft App for Zammad" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:45 +#: ../settings/security/third-party/microsoft.rst:40 msgid "" -"This reduces the category options to ``Support/*``, ``Internal/*`` and " -"``Others``. It also sets further required fields to visible." -msgstr "" - -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for support" +"Login to the `Microsoft Azure Portal `_ and " +"navigate to App registrations to create a new app. Provide the requested " +"information as follows and register your app." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:53 -msgid "Workflow Sales group" +#: ../settings/security/third-party/microsoft.rst:46 +msgid "Name:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:55 +#: ../settings/security/third-party/microsoft.rst:45 msgid "" -"This reduces the category options to ``Sales/*``, ``Internal/*`` and " -"``Others``." +"Any meaningful name fitting, this name will be displayed to users trying to " +"authenticate with this app." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for sales" +#: ../settings/security/third-party/microsoft.rst:49 +msgid "Choose one of the above mentioned account types (see Limitations)." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:68 -#: ../system/integrations/slack.rst:88 -msgid "The Result" +#: ../settings/security/third-party/microsoft.rst:51 +msgid "" +"The correct account type depends on your use case. If you want to use the " +"authentication internal only, choose the first option. If you're unsure, use " +"the \"Help me choose...\" link." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:63 -msgid "" -"This is what the agent would experience with the above workflows in place." +#: ../settings/security/third-party/microsoft.rst:58 +msgid "Redirect URI (optional):" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 +#: ../settings/security/third-party/microsoft.rst:56 msgid "" -"Workflow shows objects and limits options based on selections on the group" +"Select web and provide your callback URL. The callback URL looks like this: " +"``https://zammad.domain.tld/auth/microsoft_office365/callback``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:90 -msgid "Approval process" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to register a Microsoft app" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:71 -msgid "" -"In this case ``approved`` is visible to agents by default. For this " -"workflow, an additional role ``Approval person`` is required (no further " -"permissions)." +#: ../settings/security/third-party/microsoft.rst:71 +msgid "Within **API permissions** add the following permissions:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that restricts an approval attribute to specific roles" +#: ../settings/security/third-party/microsoft.rst:69 +msgid "``User.Read``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:81 -msgid "" -"This workflow may work best in combination with a :doc:`trigger ` but technically, this is not required." +#: ../settings/security/third-party/microsoft.rst:71 +msgid "Contacts" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:84 -msgid "" -"Select fields may be a better approach because they allow more values than " -"just a simple ``true`` or ``false``." +#: ../settings/security/third-party/microsoft.rst:71 +msgid "``Contacts.Read``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 +#: ../settings/security/third-party/microsoft.rst:73 msgid "" -"Workflow fixes possible values of \"Approved ?\" to a specific selection " -"depending on the users role" +"You can find these permissions within *Microsoft Graph → Delegated " +"permissions*." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:103 -msgid "State dependent mandatory fields" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to add required API permissions" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:93 +#: ../settings/security/third-party/microsoft.rst:80 msgid "" -"This workflow sets ``Category`` to mandatory if the agent wants to set the " -"states ``closed`` or ``pending close`` to enforce categorization." +"Within **Certificates & secrets** create a new client secret. Note down the " +"returned secret **value** for later. **Do not** use the secret ID!" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that sets fields to mandatory on specific states" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to create a new app secret" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 +#: ../settings/security/third-party/microsoft.rst:88 msgid "" -"Workflow sets category field to mandatory upon choosing closed or pending " -"close as state" +"From **Overview** copy your apps *Application (client) ID*. If you're using " +"a single tenant app, please also copy *Directory (tenant) ID*. You now have " +"all required information for Zammad." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:106 -msgid "Manual Ticket Handover Process" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to retreive application client and tenant IDs" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:108 -msgid "This example covers the handover of a ticket from one agent to another:" +#: ../settings/security/third-party/microsoft.rst:98 +msgid "Step 2 - Add App Credentials to Zammad" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:110 +#: ../settings/security/third-party/microsoft.rst:100 msgid "" -"When the ticket owner is modified, a new text field (\"Handover\") shows up " -"for a comment" +"Navigate to Security > Third-party Applications (Tab) within Zammad's admin " +"settings. Scroll down to the section *Authentication via Microsoft* and fill " +"in the required information." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:112 -msgid "" -"This may only be visible when the owner is changed, therefore it has to be " -"hidden in general" +#: ../settings/security/third-party/microsoft.rst:105 +msgid "App ID:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:114 -msgid "The input in this handover text field is mandatory" +#: ../settings/security/third-party/microsoft.rst:105 +msgid "This is your *Application (client) ID*." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:115 -msgid "" -"After submitting changes, the value of the handover field must be added as " -"an note to the ticket (via trigger)" +#: ../settings/security/third-party/microsoft.rst:108 +msgid "App secret:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:121 -msgid "Hiding handover field" +#: ../settings/security/third-party/microsoft.rst:108 +msgid "This is your *client secret* (value)." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Hiding the handover field in core workflows" +#: ../settings/security/third-party/microsoft.rst:113 +msgid "App Tenant ID:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:126 -msgid "Showing handover field and setting it to mandatory" +#: ../settings/security/third-party/microsoft.rst:111 +msgid "" +"**optional** only required for apps that use account type *Accounts in this " +"organizational directory only (Default Directory only - Single tenant).*" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Showing the handover field and set it as mandatory" +#: ../settings/security/third-party/microsoft.rst:115 +msgid "" +"Apply your settings by pressing submit and activate *Authentication via " +"Microsoft*." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:131 -msgid "Trigger writing handover input to a new article" +#: ../settings/security/third-party/microsoft.rst:None +msgid "" +"Screencast showing how to add app credentials and activating the\n" +"authentication method" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Write handover content to a new article" +#: ../settings/security/third-party/saml.rst:2 +msgid "SAML" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:133 +#: ../settings/security/third-party/saml.rst:4 msgid "" -"As a result, the ticket includes an article of the type note which includes " -"the predefined text and the handover comment." +"Connect your SAML (Security Assertion Markup Language) identity provider as " +"a single sign-on (SSO) method." msgstr "" -#: ../system/core-workflows/limitations.rst:6 -msgid "Core Workflows do not replace Triggers" +#: ../settings/security/third-party/saml.rst:7 +msgid "" +"SAML is an open standard for SSO authentication (among other things). Sign-" +"ins are shared across multiple **service providers** and managed by a " +"central **identity provider** (IdP)." msgstr "" -#: ../system/core-workflows/limitations.rst:5 +#: ../settings/security/third-party/saml.rst:11 msgid "" -"Workflows manipulate the behavior of fields. However, they do not set values " -"in fields because of actions." +"In this case, the service provider is Zammad, and the IdP is a software " +"service that you either host or subscribe to (*e.g.,* `Keycloak `_, `Redhat SSO Server `_, `ADFS `_, or `Okta `_)." msgstr "" -#: ../system/core-workflows/limitations.rst:16 -msgid "API calls are only partly affected" +#: ../settings/security/third-party/saml.rst:18 +msgid "" +"This guide assumes you are already using SAML within your organization (i." +"e., that your IdP is fully set up)." msgstr "" -#: ../system/core-workflows/limitations.rst:9 +#: ../settings/security/third-party/saml.rst:21 msgid "" -"Some options affect UI only and thus do not restrict responses and calls." +"Please note: Our instructions are based on connecting Zammad with Keycloak." msgstr "" -#: ../system/core-workflows/limitations.rst:11 -msgid "This affects the following actions:" +#: ../settings/security/third-party/saml.rst:25 +msgid "Step 1: Configure Your IdP" msgstr "" -#: ../system/core-workflows/limitations.rst:13 -msgid "select" +#: ../settings/security/third-party/saml.rst:28 +msgid "Add Zammad as a Client/App" msgstr "" -#: ../system/core-workflows/limitations.rst:14 -msgid "auto select" +#: ../settings/security/third-party/saml.rst:30 +msgid "" +"Import Zammad into your IdP using the XML configuration found at ``https://" +"your.zammad.domain/auth/saml/metadata``." msgstr "" -#: ../system/core-workflows/limitations.rst:15 -msgid "show" +#: ../settings/security/third-party/saml.rst:33 +msgid "" +"If your IdP doesn't support XML import, you will have to configure Zammad as " +"a new client/app manually using the above XML metadata file for reference." msgstr "" -#: ../system/core-workflows/limitations.rst:16 -msgid "hide" +#: ../settings/security/third-party/saml.rst:36 +msgid "For instance, when you see this tag:" msgstr "" -#: ../system/core-workflows/limitations.rst:25 -msgid "Some fields stay unavailable to customers" +#: ../settings/security/third-party/saml.rst:42 +msgid "" +"Set the **Assertion Consumer Service Binding URL** (sometimes also listed as " +"**Valid Redirect URIs**) to ``http://your.zammad.domain/auth/saml/callback``." msgstr "" -#: ../system/core-workflows/limitations.rst:19 -msgid "" -"For technical and security reasons, some default fields (the pale ones you " -"can't edit) stay unavailable for display and usage on customer permissions." +#: ../settings/security/third-party/saml.rst:47 +msgid "Set Up User Attribute Mapping" msgstr "" -#: ../system/core-workflows/limitations.rst:23 +#: ../settings/security/third-party/saml.rst:49 msgid "" -"If you require your customers to change e.g. priorities, please consider " -"using workarounds via :doc:`/system/objects` and :doc:`/manage/trigger`." +"Zammad requests the following user attributes (or “properties”) from the IdP:" msgstr "" -#: ../system/core-workflows/limitations.rst:29 -msgid "Ticket title changes not supported in edit mask" +#: ../settings/security/third-party/saml.rst:51 +msgid "Email address (``email``)" msgstr "" -#: ../system/core-workflows/limitations.rst:28 -msgid "" -"It is currently not possible to perform changes of the ticket title in the " -"edit mask (e.g. renaming, set to read-only)." +#: ../settings/security/third-party/saml.rst:52 +msgid "Full name (``name``)" msgstr "" -#: ../system/core-workflows/limitations.rst:37 -msgid "What is out of scope of Core Workflows?" +#: ../settings/security/third-party/saml.rst:53 +msgid "Given name (``first_name``)" msgstr "" -#: ../system/core-workflows/limitations.rst:32 -msgid "" -"There are some things that would count as workflow but are either done via :" -"doc:`/manage/trigger` or :doc:`/manage/scheduler`." +#: ../settings/security/third-party/saml.rst:54 +msgid "Family name (``last_name``)" msgstr "" -#: ../system/core-workflows/limitations.rst:35 -msgid "Such as (but not limited to):" +#: ../settings/security/third-party/saml.rst:56 +msgid "" +"You may need to set up “mappers” (or “mappings”) to tell your IdP how user " +"attributes in SAML correspond to those in Zammad. For a more detailed " +"breakdown, refer to the XML metadata file referenced in the previous section." msgstr "" -#: ../system/core-workflows/limitations.rst:37 -msgid "up- or downgrade permissions of users" +#: ../settings/security/third-party/saml.rst:62 +msgid "Per-IdP Instructions" msgstr "" -#: ../system/core-workflows/limitations.rst:38 -msgid "affecting article creation or listing" +#: ../settings/security/third-party/saml.rst:102 +msgid "Keycloak" msgstr "" -#: ../system/data-privacy.rst:2 -msgid "Data Privacy" +#: ../settings/security/third-party/saml.rst:65 +msgid "" +"**To add Zammad as a client,** save the XML configuration to disk (``https://" +"your.zammad.domain/auth/saml/metadata``) and use **Clients > Clients list > " +"Import client** in the Keycloak admin panel." msgstr "" -#: ../system/data-privacy.rst:4 +#: ../settings/security/third-party/saml.rst:70 msgid "" -"For compliance with GDPR and other data privacy laws, you may wish to " -"**permanently delete users from the system**, along with **all of their " -"associated tickets**." +"To help Zammad **match its own user accounts to Keycloak users**, create a " +"user attribute (or “property”) mapper. In **Clients list**, click on your " +"newly created Client ID, choose the tab **Client scopes** and click on the " +"link which refers to your Zammad instance. Choose **Add mapper > By " +"configuration > User Property** and create a mapper with the following " +"entries:" 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 `!" +#: ../settings/security/third-party/saml.rst:78 +msgid "**Name**" msgstr "" -#: ../system/data-privacy.rst:12 -msgid "" -"Access to this panel requires ``admin.data_privacy`` permissions (introduced " -"in Zammad 3.5)." +#: ../settings/security/third-party/saml.rst:80 +msgid "**Mapper Type**" msgstr "" -#: ../system/data-privacy.rst:15 -msgid "" -"On older systems that have not been updated yet, customers can also be :docs:" -"`deleted via the Zammad console `." +#: ../settings/security/third-party/saml.rst:81 +msgid "``User Property``" msgstr "" -#: ../system/data-privacy.rst:22 -msgid "User deletion dialog in the Data Privacy panel" +#: ../settings/security/third-party/saml.rst:82 +msgid "**Property**" msgstr "" -#: ../system/data-privacy.rst:22 -msgid "" -"The user deletion dialog lists some of the tickets that will be removed from " -"the system along with the user." +#: ../settings/security/third-party/saml.rst:83 +msgid "``emailAddress``" msgstr "" -#: ../system/data-privacy.rst:27 -msgid "Deleting Users via GUI" +#: ../settings/security/third-party/saml.rst:84 +msgid "**SAML Attribute Name**" msgstr "" -#: ../system/data-privacy.rst:29 -msgid "🔥 **All deletions are FINAL!**" +#: ../settings/security/third-party/saml.rst:86 +msgid "**SAML Attribute NameFormat**" msgstr "" -#: ../system/data-privacy.rst:31 -msgid "Once you click “Delete”, the action cannot be canceled or undone." +#: ../settings/security/third-party/saml.rst:87 +msgid "``basic``" msgstr "" -#: ../system/data-privacy.rst:33 +#: ../settings/security/third-party/saml.rst:89 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." +"In the example above, we're telling Zammad that whenever it receives a SAML " +"login request, it should take the ``email`` property from Keycloak, look for " +"a Zammad user with the same ``email`` attribute, and create a new session " +"for that user." msgstr "" -#: ../system/data-privacy.rst:36 -msgid "**The following records cannot be deleted:**" +#: ../settings/security/third-party/saml.rst:95 +msgid "" +"If your Keycloak users' email addresses are stored on another property (*e." +"g.,* ``username``), adjust accordingly." msgstr "" -#: ../system/data-privacy.rst:38 -msgid "your own account" +#: ../settings/security/third-party/saml.rst:98 +msgid "" +"Back in **Settings**, enter the Client ID (``https://your.zammad.domain/auth/" +"saml/metadata``) in the field **Master SAML Processing URL**." msgstr "" -#: ../system/data-privacy.rst:39 -msgid "the system's last remaining administrator account" +#: ../settings/security/third-party/saml.rst:101 +msgid "You also need to enable **Sign assertions**." msgstr "" -#: ../system/data-privacy.rst:42 -msgid "Step 1: Find a User / Confirm Deletion" +#: ../settings/security/third-party/saml.rst:105 +msgid "Step 2: Configure Zammad" msgstr "" -#: ../system/data-privacy.rst:44 -msgid "There are three ways to access the user deletion dialog:" +#: ../settings/security/third-party/saml.rst:107 +msgid "" +"Enable SAML and enter your IdP's details in the Admin Panel under **Settings " +"> Security > Third Party Applications > Authentication via SAML**:" msgstr "" -#: ../system/data-privacy.rst:51 -msgid "**from the user's profile**" +#: ../settings/security/third-party/saml.rst:None +msgid "Example configuration of SAML part 1" msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Accessing the user deletion dialog in a user profile" +#: ../settings/security/third-party/saml.rst:119 +msgid "Display name" msgstr "" -#: ../system/data-privacy.rst:51 -msgid "Click **Action > Delete**." +#: ../settings/security/third-party/saml.rst:116 +msgid "" +"Allows you to define a custom button name for SAML. This helps your users to " +"understand better what the button on the login page does." msgstr "" -#: ../system/data-privacy.rst:58 -msgid "**in the “Manage > Users” Admin Panel**" +#: ../settings/security/third-party/saml.rst:119 +msgid "Defaults to ``SAML``." msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Accessing the user deletion dialog under “Users” in the Admin Panel" +#: ../settings/security/third-party/saml.rst:123 +msgid "IDP SSO target URL" msgstr "" -#: ../system/data-privacy.rst:58 -msgid "Use the **⋮ Actions** menu for the target user." +#: ../settings/security/third-party/saml.rst:122 +msgid "" +"This is the target URL Zammad shall redirect to when the user presses the " +"SAML button. For Keycloak, this needs to look like https://your.domain/" +"realms/your-realm/protocol/saml" msgstr "" -#: ../system/data-privacy.rst:66 ../system/data-privacy.rst:104 -msgid "**in the “System > Data Privacy” Admin Panel**" +#: ../settings/security/third-party/saml.rst:127 +msgid "IDP single logout target URL" msgstr "" -#: ../system/data-privacy.rst:0 +#: ../settings/security/third-party/saml.rst:126 msgid "" -"Accessing the user deletion dialog under “Data Privacy” in the Admin Panel" +"This is the URL to which the single logout request and response should be " +"sent." msgstr "" -#: ../system/data-privacy.rst:65 +#: ../settings/security/third-party/saml.rst:131 +msgid "IDP certificate" +msgstr "" + +#: ../settings/security/third-party/saml.rst:130 msgid "" -"Use the **New Deletion Task** button. Search for users by name or email " -"address." +"The public certificate of your IDP for Zammad to verify during the callback " +"phase." msgstr "" -#: ../system/data-privacy.rst:79 -msgid "**Delete organizations**" +#: ../settings/security/third-party/saml.rst:145 +msgid "IDP certificate fingerprint" msgstr "" -#: ../system/data-privacy.rst:69 +#: ../settings/security/third-party/saml.rst:134 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:" +"The fingerprint of your IDPs public certificate to verify during callback " +"phase." msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Deleting an organization via the user deletion dialog" +#: ../settings/security/third-party/saml.rst:137 +msgid "🔏 **For the IdP certificate / certificate fingerprint:**" msgstr "" -#: ../system/data-privacy.rst:78 +#: ../settings/security/third-party/saml.rst:139 msgid "" -"If this option does not appear, make sure there are no pending deletion " -"tasks for other customers from this organization." +"Provide **only one or the other**—do not provide both! (Between the two, we " +"recommend the signing certificate itself: fingerprints use SHA-1, which `has " +"been broken for a while now `_.)" msgstr "" -#: ../system/data-privacy.rst:82 -msgid "Step 2: Monitor Deletion Job Status" +#: ../settings/security/third-party/saml.rst:144 +msgid "" +"**Keycloak users:** Find your certificate in the Keycloak admin panel under " +"**Realm Settings > Keys > Algorithm: RS256 > Certificate**." msgstr "" -#: ../system/data-privacy.rst:84 +#: ../settings/security/third-party/saml.rst:151 +msgid "Name identifier format" +msgstr "" + +#: ../settings/security/third-party/saml.rst:148 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:" +"This is the unique identifiers field type. Usually it should be ``urn:oasis:" +"names:tc:SAML:1.1:nameid-format:emailAddress``." msgstr "" -#: ../system/data-privacy.rst:98 -msgid "**in the Activity Stream**" +#: ../settings/security/third-party/saml.rst:151 +msgid "Zammad **expects an email address as unique identifier**!" msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Activity Stream showing data privacy tasks" +#: ../settings/security/third-party/saml.rst:155 +msgid "UID attribute name" msgstr "" -#: ../system/data-privacy.rst:94 +#: ../settings/security/third-party/saml.rst:154 msgid "" -"For each deleted user, the Activity Stream will be updated twice—once when " -"the task is created, and once when it's complete." +"Here you can define an attribute that uniquely identifies the user. If " +"unset, the name identifier returned by the IDP is used." msgstr "" -#: ../system/data-privacy.rst:97 -msgid "" -"These notifications are only visible to users with ``admin.data_privacy`` " -"permissions." +#: ../settings/security/third-party/saml.rst:None +msgid "Example configuration of SAML part 2" msgstr "" -#: ../system/data-privacy.rst:0 +#: ../settings/security/third-party/saml.rst:163 msgid "" -"The task list within Data Privacy shows removals being in progress and " -"completed." +"Decide if the certificate for the connection to the IdP service has to be " +"verified or not (default: ``yes``)." msgstr "" -#: ../system/data-privacy.rst:107 -msgid "Frequently Asked Questions" +#: ../settings/security/third-party/saml.rst:169 +msgid "Signing & Encrypting" msgstr "" -#: ../system/data-privacy.rst:121 -msgid "What happens if I receive an email from a deleted customer?" -msgstr "" - -#: ../system/data-privacy.rst:110 +#: ../settings/security/third-party/saml.rst:169 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." +"Define if you want to sign, encrypt, do both or nothing for the requests." msgstr "" -#: ../system/data-privacy.rst:115 -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**." +#: ../settings/security/third-party/saml.rst:179 +msgid "Certificate (PEM)" msgstr "" -#: ../system/data-privacy.rst:130 -msgid "What about user information stored in internal notes or other messages?" +#: ../settings/security/third-party/saml.rst:172 +msgid "" +"Paste the public certificate of your Zammad SAML client, if you want to " +"encrypt the requests." msgstr "" -#: ../system/data-privacy.rst:124 -msgid "" -"The deletion process removes **user accounts and associated tickets only**." +#: ../settings/security/third-party/saml.rst:175 +msgid "Make sure the certificate is:" msgstr "" -#: ../system/data-privacy.rst:126 -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." +#: ../settings/security/third-party/saml.rst:177 +msgid "already valid and not yet expired" msgstr "" -#: ../system/data-privacy.rst:137 -msgid "I deleted an user and can still see a message they sent!" +#: ../settings/security/third-party/saml.rst:178 +msgid "no CA certificate" msgstr "" -#: ../system/data-privacy.rst:133 -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." +#: ../settings/security/third-party/saml.rst:179 +msgid "valid for signing and encrypting" msgstr "" -#: ../system/data-privacy.rst:141 -msgid "I removed a customer, now my reporting is off!" +#: ../settings/security/third-party/saml.rst:185 +msgid "Private key (PEM)" msgstr "" -#: ../system/data-privacy.rst:140 +#: ../settings/security/third-party/saml.rst:182 msgid "" -"When removing users and their tickets, all references are removed. This also " -"affects e.g. Reporting - these information are lost." +"Paste the private key of your Zammad SAML client here, if you want to sign " +"the requests." msgstr "" -#: ../system/data-privacy.rst:145 -msgid "How long does Zammad store created tasks?" +#: ../settings/security/third-party/saml.rst:185 +msgid "Make sure the key is an RSA key with a length of at least 2048 bits." msgstr "" -#: ../system/data-privacy.rst:144 -msgid "" -"Please see the on-premise data section of the :docs:`data privacy ` chapter." +#: ../settings/security/third-party/saml.rst:188 +msgid "Private key secret" msgstr "" -#: ../system/data-privacy.rst:150 -msgid "What about re-assigned tickets? I want to delete them, too." +#: ../settings/security/third-party/saml.rst:188 +msgid "If your private key is secured with a secret, you can provide it here." msgstr "" -#: ../system/data-privacy.rst:148 -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." +#: ../settings/security/third-party/saml.rst:192 +msgid "Your callback URL" msgstr "" -#: ../system/data-privacy.rst:154 -msgid "Why are there so many deletion task entries, I didn't create them!" +#: ../settings/security/third-party/saml.rst:191 +msgid "" +"This URL is needed for your IdP configuration so it knows where to redirect " +"to after successful authentication." msgstr "" -#: ../system/data-privacy.rst:153 +#: ../settings/security/third-party/saml.rst:194 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." +"After saving your input by clicking on the \"Submit\" button, Zammad " +"verifies the provided keys/certificates (e.g. if they are valid for signing/" +"encrypting and if they aren't expired)." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:2 -msgid "Admin Panel Reference" +#: ../settings/security/third-party/saml.rst:199 +msgid "" +"See :ref:`automatic account linking ` for details " +"on how to link existing Zammad accounts to IdP accounts." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:None -msgid "Screenshot of Checkmk settings overview" +#: ../settings/security/third-party/saml.rst:205 +msgid "Automatic account linking doesn't work" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:12 +#: ../settings/security/third-party/saml.rst:206 msgid "" -"Which :doc:`group ` should Checkmk tickets be assigned " -"to as a default (*i.e.,* when none is specified)?" +"Have you double-checked your IdP's user attribute mapping configuration?" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:15 -msgid "(Applies to :ref:`API alerts ` only.)" +#: ../settings/security/third-party/twitter.rst:4 +msgid "" +"It is possible to create a quick login for your helpdesk via Twitter. To do " +"so, you need to follow these steps:" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:21 -msgid "Auto close" +#: ../settings/security/third-party/twitter.rst:8 +msgid "Register Twitter App" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:18 -msgid "" -"Should Zammad automatically close tickets if a service has recovered on its " -"own?" +#: ../settings/security/third-party/twitter.rst:10 +msgid "Go to https://dev.twitter.com/apps and login with your account." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:21 -msgid "(Agents will receive notifications for such closures as appropriate.)" +#: ../settings/security/third-party/twitter.rst:15 +msgid "Click on \"Create App\"" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:30 -msgid "Auto-close state" +#: ../settings/security/third-party/twitter.rst:None +msgid "new app page" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:24 -msgid "What ticket state should be applied when “auto-closing” a ticket?" +#: ../settings/security/third-party/twitter.rst:20 +msgid "" +"Enter app settings. As \"Callback URL\" you need to enter ``https://" +"zammad_host/api/v1/external_credentials/twitter/callback``. You need to " +"replace ``zammad_host`` with the domain of your Zammad system." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:26 +#: ../settings/security/third-party/twitter.rst:24 msgid "" -"You can choose from the seven built-in ticket states. If these states aren't " -"enough for you, you can :ref:`define a new ticket state ` for this purpose as well. This can be useful for tracking " -"tickets with :doc:`reports `, for example." +"After the app has been created, update the application icon and organization " +"attributes." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:35 -#: ../system/integrations/cti/includes/recent-logs.include.rst:2 -#: ../system/integrations/ldap/index.rst:74 -#: ../system/integrations/pgp/index.rst:106 -msgid "Recent Logs" +#: ../settings/security/third-party/twitter.rst:None +msgid "set permissions to receive and send direct messages" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:None -msgid "Screenshot of Checkmk \"Recent Logs\" section" +#: ../settings/security/third-party/twitter.rst:30 +msgid "" +"Next we need to set ``read, write and access direct messages`` permissions " +"for the app." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:41 -msgid "" -"If you're having trouble getting Zammad and Checkmk to play nicely together, " -"this section can help you troubleshoot." +#: ../settings/security/third-party/twitter.rst:None +msgid "click on Keys & Access Token, note them" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:44 +#: ../settings/security/third-party/twitter.rst:36 msgid "" -"It contains a record of the fifty most recent transactions that Zammad knows " -"about, including each one's request/response details and return status." +"Go to \"Keys and Access Token\" tab and note the \"Consumer Key\" and " +"\"Consumer Secret\"." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:2 -msgid "API Reference" +#: ../settings/security/third-party/twitter.rst:40 +msgid "Configure Zammad as Twitter App" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:4 +#: ../settings/security/third-party/twitter.rst:42 msgid "" -"For most users, :ref:`the sample scripts from the Setup Guide ` will do the job just fine. But if you want more fine-grained control" -"—for instance, to create high- and low-priority tickets for different types " -"of system events—then you'll have to customize the data those scripts send " -"to Zammad." +"Go to \"Admin > Security > Twitter > Third Party Applications > Twitter\" " +"Section." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:15 -msgid "" -"This custom script will automatically set all tickets it creates to **high " -"priority** and **assign them to charlie@chrispresso.com**." +#: ../settings/security/third-party/twitter.rst:None +msgid "Admin > Security > Third Party Applications" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:32 -msgid "How Does it Work?" +#: ../settings/security/third-party/twitter.rst:48 +msgid "" +"Fill in the \"Twitter Key\" and the \"Twitter Secret\" and click the " +"\"Submit\" button." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:34 +#: ../settings/security/third-party/twitter.rst:51 msgid "" -"There are two kinds of data you can pass to the API, both in the form of key-" -"value pairs:" +"Now you can link accounts via \"Avatar > Profile > Link Accounts\" or login " +"via Zammad login page." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:44 -msgid "Checkmk parameters" +#: ../settings/security/two-factor.rst:11 +msgid "Two-factor Authentication Methods" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:38 -msgid "" -"are required, and make up the **contents** of the resulting tickets/" -"articles. They also determine whether an event creates a new ticket or " -"updates/closes an existing one." +#: ../settings/security/two-factor.rst:2 +msgid "Two-Factor Authentication" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:42 +#: ../settings/security/two-factor.rst:4 msgid "" -"These are the only values used in the sample scripts. **Use them as-is**; " -"technically, they can be customized, but it's hard to imagine a good reason " -"for it." +"Two-factor authentication (2FA) enhances the security of Zammad accounts by " +"adding an extra layer of verification beyond a password. It requires users " +"to provide two different types of authentication factors, typically " +"something they know (like a password) and something they possess (like a " +"mobile device or a security token), to ensure that only authorized " +"individuals can access the account." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:52 -msgid "Ticket attributes" +#: ../settings/security/two-factor.rst:19 +msgid "Enable Recovery Codes" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:47 +#: ../settings/security/two-factor.rst:21 msgid "" -"are optional, and can be used to **adjust settings** on newly created " -"tickets (*e.g.,* set the owner, group, priority, or state)." +"Recovery codes are one-time use security codes that can be used by the user " +"if they lose access to their other two-factor authentication methods. They " +"cannot be used on their own, they can only be activated if at least one two-" +"factor authentication method is enabled." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:50 -msgid "" -"If you want to customize your Checkmk alert script, do it with these. Simply " -"add an extra “form” option for each one (``-F \"key=value\"``) to your " -"script's ``curl`` command line, as in the example above." +#: ../settings/security/two-factor.rst:None +msgid "Enable Recovery Codes Setting" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:54 -msgid "💡 **It's just an API endpoint!**" +#: ../settings/security/two-factor.rst:30 +msgid "" +"Recovery codes can only be used as a backup method. If enabled, they will be " +"automatically generated for the user once they set up their initial two-" +"factor authentication method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:56 +#: ../settings/security/two-factor.rst:34 msgid "" -"When using Checkmk integration, messages need to be formatted in a certain " -"way, but that *doesn't mean the messages actually have to come from Checkmk*." +"The user will be asked to print out or save the generated recovery codes in " +"a safe place. Once used, a recovery code cannot be reused." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:59 +#: ../settings/security/two-factor.rst:37 msgid "" -"If you use another monitoring tool that's not officially supported by " -"Zammad, there's probably a way to make it work with your Checkmk callback " -"URL." +"Users will also have an option to regenerate their recovery codes at any " +"time, which invalidates already existing recovery codes and provides them " +"with a list of fresh codes." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:63 -msgid "Checkmk Parameters" +#: ../settings/security/two-factor.rst:41 +msgid "" +"After you enable this setting, when the user completes a setup of their " +"initial two-factor authentication method, they will be presented with a list " +"of recovery codes and instructed to save them for later use." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:65 -msgid "" -"When a notification is received, Zammad creates a new article containing the " -"details of the event that triggered it:" +#: ../settings/security/two-factor.rst:None +msgid "Recovery Codes Generation Modal Dialog" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:None -msgid "Checkmk article body" +#: ../settings/security/two-factor.rst:50 +msgid "Enforce the Set Up of the Two-Factor Authentication" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:72 +#: ../settings/security/two-factor.rst:52 msgid "" -"These details come from the fields listed below, which correspond to " -"parameters provided by Checkmk (``$NOTIFY_*``)." +"In case you wish to require your users to set up at least one two-factor " +"authentication method for their account, you can do this by selecting " +"specific user roles the requirement applies to in **Enforced for user " +"roles** setting. Of course you must have at least one two-factor " +"authentication method enabled for this setting to take effect." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:75 -msgid "**Required fields are marked with an asterisk (\\*).**" +#: ../settings/security/two-factor.rst:None +msgid "Enforced for User Roles Setting" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:79 -msgid "event_id\\*" +#: ../settings/security/two-factor.rst:62 +msgid "" +"After you change this setting, if the user has one of the selected roles on " +"their account, they will be forced to set up the two-factor authentication " +"upon next sign in or application reload." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:78 +#: ../settings/security/two-factor.rst:66 msgid "" -"A unique ID for the system event. (``$NOTIFY_SERVICEPROBLEMID`` / " -"``$NOTIFY_HOSTPROBLEMID``)" +"A modal dialog with instructions will be shown, and they will not be able to " +"do any work before they set up at least one two-factor method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:86 -msgid "host\\*" +#: ../settings/security/two-factor.rst:None +msgid "Modal Dialog for Enforcing Two-Factor Authentication Set Up" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:82 +#: ../settings/security/two-factor.rst:74 +msgid "Reset Two-Factor Authentication for a Specific User" +msgstr "" + +#: ../settings/security/two-factor.rst:76 msgid "" -"The hostname of the system that the event originated from. " -"(``$NOTIFY_HOSTNAME``)" +"In case an user isn't able to login anymore because of an inaccessible " +"second factor, you can reset the user's 2FA method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:85 +#: ../settings/security/two-factor.rst:79 msgid "" -"Used to determine if a new event belongs to an existing ticket. Also used in " -"the subject line of the resulting article (“ is ”)." +"To do this, go to the user management and search for the relevant user. " +"After you found the account, click the button in the action column and " +"select \"Manage Two-Factor Authentication\":" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:96 -msgid "service" +#: ../settings/security/two-factor.rst:None +msgid "Context menu in action column in user management" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:89 +#: ../settings/security/two-factor.rst:87 msgid "" -"The name of the service that the event originated from. " -"(``$NOTIFY_SERVICEDESC``)" +"After selecting this, you can see a dialog where you can either reset one " +"2FA method or reset all of the user's 2FA methods:" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:92 -msgid "Used to determine if a new event belongs to an existing ticket." +#: ../settings/security/two-factor.rst:None +msgid "Dialog for resetting user's 2FA method" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:94 -#: ../system/integrations/checkmk/api-reference.rst:110 -msgid "Displayed as ``-`` when omitted." +#: ../settings/security/two-factor.rst:94 +msgid "" +"Choose the fitting one, click on the corresponding \"Remove ...\" button and " +"confirm your action. The user now has to setup a new 2FA method, depending " +"on your 2FA configuration." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:104 -msgid "state\\*" +#: ../settings/security/two-factor/authenticator-app.rst:2 +msgid "Authenticator App" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:99 +#: ../settings/security/two-factor/authenticator-app.rst:4 msgid "" -"The current state of the service or host in question. " -"(``$NOTIFY_SERVICESTATE`` / ``$NOTIFY_HOSTSTATE``)" +"The authenticator app method is a type of two-factor authentication that " +"uses a mobile application to generate one-time codes for account " +"verification. After setting up the authenticator app on their device, the " +"user links it to their Zammad account." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:102 +#: ../settings/security/two-factor/authenticator-app.rst:12 msgid "" -"Used to detect when a ticket should be auto-closed (*i.e.,* on ``OK``/" -"``UP``). Also used in the subject line of the resulting article (“ is " -"”)." +"When logging in, the user is prompted to enter a time-sensitive code " +"generated by the app, in addition to their password. This code acts as the " +"second factor of authentication, providing an extra layer of security as it " +"changes periodically and is unique to the user's device." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:110 -msgid "text" +#: ../settings/security/two-factor/authenticator-app.rst:None +msgid "Security Code in Google Authenticator App" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:107 +#: ../settings/security/two-factor/authenticator-app.rst:22 msgid "" -"The output of the process that triggered the event. " -"(``$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" +"The app generates codes based on a shared secret key stored securely on both " +"the user's device and the server, ensuring a synchronized and secure " +"authentication process. The method of generating the codes is sometimes also " +"called TOTP (time-based one-time password)." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:121 -msgid "" -"The Object Manager attribute panel displays built-in and custom\n" -"attribute names." +#: ../settings/security/two-factor/authenticator-app.rst:28 +msgid "Enabling the Authenticator App Method" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:121 -msgid "Find a complete list of ticket attributes in the Object Manager." +#: ../settings/security/two-factor/authenticator-app.rst:30 +#: ../settings/security/two-factor/security-keys.rst:28 +msgid "To enable the method, just toggle the switch on in the settings." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:123 -msgid "" -"Ticket attributes are entirely optional, and can be used to customize the " -"tickets that Checkmk creates. (Note that these attributes will be ignored if " -"a new event belongs to an existing ticket.)" +#: ../settings/security/two-factor/authenticator-app.rst:None +msgid "Authenticator App Switch in Settings" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:128 +#: ../settings/security/two-factor/authenticator-app.rst:36 msgid "" -"Why would you want to do this? Maybe you have only one IT guy, and all " -"system monitoring issues should be automatically assigned to him. Or, maybe " -"you're creating multiple notification rules so that database outages take " -"higher priority than disk space warnings." +"Now the users will be able to set up this two-factor authentication method " +"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " +"Once they do, on next sign-in with password, they will be asked to provide " +"an additional security code generated by their mobile device." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:135 -msgid "In most cases, you'll probably want to set one of the following:" +#: ../settings/security/two-factor/security-keys.rst:2 +msgid "Security Keys" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:137 -msgid "group" +#: ../settings/security/two-factor/security-keys.rst:4 +msgid "" +"The security keys method is a type of a two-factor authentication that uses " +"Web Authentication API in the browser for verifying user's identity. The " +"user can register multiple hardware or software security keys with their " +"Zammad account and then they can use it during the sign-in process." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:139 -msgid "state" +#: ../settings/security/two-factor/security-keys.rst:12 +msgid "" +"When logging in, the user is prompted to provide the same security key they " +"registered with their account, in addition to their password. This key acts " +"as the second factor of authentication, providing an extra layer of security." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:140 -msgid "priority" +#: ../settings/security/two-factor/security-keys.rst:None +msgid "Security Key dialog in Safari on macOS" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:142 +#: ../settings/security/two-factor/security-keys.rst:21 msgid "" -"but in practice, you can set almost any attribute, including :doc:`custom " -"ones you created through the Object Manager `." -msgstr "" - -#: ../system/integrations/checkmk/api-reference.rst:145 -msgid "Please note that the following attributes are **not customizable**:" +"The type of the key can range from hardware USB sticks to passkeys stored in " +"a device of user's choice. Which type can be used depends on the browser " +"flavor and the platform of the user." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:147 -msgid "title" +#: ../settings/security/two-factor/security-keys.rst:26 +msgid "Enabling the Security Keys Method" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:148 -msgid "id" +#: ../settings/security/two-factor/security-keys.rst:None +msgid "Security Keys Switch in Settings" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:149 -msgid "ticket number" +#: ../settings/security/two-factor/security-keys.rst:34 +msgid "" +"Now the users will be able to set up this two-factor authentication method " +"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " +"Once they do, on next sign-in with password, they will be asked to provide " +"the same security key they registered during the setup." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:151 -msgid "created_by_id" +#: ../settings/system/system-selfhosted.include.rst:3 +msgid "" +"Below settings are only available to self hosted users. In hosted " +"environments we're handling these settings for you to ensure service " +"stability." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:152 -msgid "updated_by_id" +#: ../settings/system/base.rst:11 +msgid "Fully Qualified Domain Name" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:155 -msgid "Which Values Can Be Set?" +#: ../settings/system/base.rst:7 +msgid "The URL of your Zammad installation." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:157 -msgid "😵 **Invalid values → unpredictable behavior**" +#: ../settings/system/base.rst:9 ../settings/system/base.rst:17 +msgid "This setting is used within :doc:`/misc/variables` and notifications." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:159 -msgid "" -"If you provide a value that Zammad doesn't understand (*e.g.,* ``-F " -"\"priority=high\"``), it's not always clear what will happen. In some cases, " -"a ticket will be created with the default values instead - but in others, it " -"may not be created at all!" +#: ../settings/system/system-base.include.rst:1 +msgid "It is automatically set by the *Getting Started wizard*." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:164 -msgid "So what values does Zammad understand, then? Well, it depends..." +#: ../settings/system/system-base.include.rst:5 +msgid "Changing this setting also changes callback URLs for your channels etc." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:168 -msgid "Use an email address or username:" +#: ../settings/system/system-base.include.rst:6 +msgid "This setting can have negative affects on being able to login." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:190 -msgid "group & priority" +#: ../settings/system/base.rst:19 +msgid "HTTP type" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:175 -msgid "Refer to the dropdown menus in the ticket pane:" +#: ../settings/system/base.rst:14 +msgid "" +"The HTTP type tells your installation how your clients connect. This is " +"relevant for authentication and cookie security." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:0 -msgid "See possible values for certain attributes in the ticket pane." +#: ../settings/system/base.rst:31 +msgid "SystemID" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:187 -msgid "🙅 **Ticket state CANNOT be set this way!**" +#: ../settings/system/base.rst:22 +msgid "" +"This ID is being used within your ticket number. In case you're " +"communicating with another ticket system with similar ticket number schemes " +"this ID greatly reduces the risk of false follow ups." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:189 +#: ../settings/system/base.rst:26 msgid "" -"Why? Because ``-F \"state=...\"`` is already used :ref:`as a Checkmk " -"parameter `." +"The SystemID is randomly selected upon installation of Zammad (``1-99``)." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:222 -msgid "Everything Else" +#: ../settings/system/base.rst:30 +msgid "" +"**Do not** change this setting in a productive system! Your Zammad " +"installation may no longer recognize old ticket number based follow ups upon " +"change!" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:193 -msgid "" -"To set any other attributes, it helps to know your way around the :docs:" -"`rails console `. Valid values are those that you can " -"set with a string:" +#: ../settings/system/frontend.rst:2 +msgid "Frontend" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:218 -msgid "These values can then be passed directly to the API:" +#: ../settings/system/frontend.rst:22 +msgid "Core Workflow Ajax Mode" msgstr "" -#: ../system/integrations/checkmk/index.rst:16 -msgid "How does it work?" +#: ../settings/system/frontend.rst:6 +msgid "" +"This setting allows administrators to enforce :doc:`/system/core-workflows` " +"to use Ajax-Calls instead of web sockets. You'll usually only need this if " +"you experience serious issues as noted below." msgstr "" -#: ../system/integrations/checkmk/index.rst:2 -msgid "Checkmk" +#: ../settings/system/frontend.rst:10 +msgid "**🤓 Possible (technical) reasons**" msgstr "" -#: ../system/integrations/checkmk/index.rst:4 +#: ../settings/system/frontend.rst:12 msgid "" -"`Checkmk `_ is a powerful IT monitoring tool that can " -"send real-time status alerts to Zammad via email or REST API. Set these " -"alerts up in Checkmk, and Zammad will automatically create, update, and " -"close tickets based on the health of your system:" +"In some cases, your network structure (e.g. firewalls, proxies) may " +"disconnect long web socket connections. This leads to select fields staying " +"empty (e.g. owner selection *after* selecting your group) or fields not " +"shown / hidden (e.g. when switching to or from pending states, the \"pending " +"till\" field not showing / hiding)." msgstr "" -#: ../system/integrations/checkmk/index.rst:14 -msgid "Screenshot of ticket created by Checkmk notifications" +#: ../settings/system/frontend.rst:18 +msgid "" +"Please keep in mind that the Ajax fallback may cause serious pressure on " +"your application server. If you have the choice stick to web sockets." msgstr "" -#: ../system/integrations/checkmk/index.rst:14 -msgid "Multiple alerts, same ticket." +#: ../settings/system/frontend.rst:22 +msgid "Default: ``no`` (inactive)" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:2 -msgid "Setup Guide" +#: ../settings/system/frontend.rst:53 +msgid "Show calendar weeks in the picker of date/datetime fields" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:4 +#: ../settings/system/frontend.rst:25 msgid "" -"Whenever the Checkmk integration is enabled, Zammad listens for messages on " -"its API and over email. As long as those messages follow the required " -"format, Zammad will create new tickets (or find and update existing ones) " -"based on the message contents." +"With this setting you can instruct Zammad to provide week number display " +"globally for all users. Calendar with week number display are usually used " +"in business sectors and may not be relevant for everyone." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:10 +#: ../settings/system/frontend.rst:29 msgid "" -"That means that “setting up Checkmk integration” is simply a matter of " -"**adding configuration to your Checkmk site**: telling it when to send these " -"messages and what to say. To do that, you'll need to create a new " -"**notification rule** (see `Checkmk's official docs `_ for help with that)." +"This setting affects *all areas* - you'll also see week numbers in the admin " +"panel for e.g. triggers and macros." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:17 -msgid "" -"As part of this new rule, you'll have to choose a **notification method** " -"(*i.e.,* a script to execute whenever the rule is triggered). This script " -"will be written by you (samples below), and contain the logic for sending " -"API/email messages to Zammad:" +#: ../settings/system/frontend.rst:32 +msgid "Default: ``no`` (not shown)" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:26 -msgid "Checkmk \"New Rule\" dialog" +#: ../settings/system/frontend.rst:53 +msgid "Here's the difference:" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:26 -msgid "" -"Find your custom scripts in the Checkmk WATO under **Notifications > New " -"Rule > Notification Method**." +#: ../settings/system/frontend.rst:0 +msgid "Screenshot showing Zammad's date picker (in the default way)" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:29 -msgid "" -"Once you're done setting up your new rule, you're all set! New tickets " -"should start coming in and auto-updating any time your rule is triggered." +#: ../settings/system/frontend.rst:41 +msgid "Set to ``no``" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:33 +#: ../settings/system/frontend.rst:0 msgid "" -"(If you need help troubleshooting, be sure to check the :ref:`checkmk-recent-" -"logs`.)" +"Screenshot showing Zammad's date picker with\n" +"week numbers enabled" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:38 -msgid "API Alerts" +#: ../settings/system/frontend.rst:50 +msgid "Set to ``yes``" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:40 +#: ../settings/system/index.rst:4 msgid "" -"To add these scripts in the Checkmk WATO, copy them into your Checkmk " -"installation directory and make them executable. (Be sure to replace the " -"``zammad.example.com`` callback URL with the one found in your admin panel.)" +"For your overview we split each tab within system settings into its own page:" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:60 -msgid "Service notification" +#: ../settings/system/index.rst:16 +msgid "Console Based Settings" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:46 +#: ../settings/system/index.rst:18 msgid "" -"For updates on the status of the software running on your server (*e.g.,* " -"postgres)." +"There's some console based settings we didn't put into the UI. However, you " +"may find them helpful - you can find them in our :docs:`hidden settings ` section." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:75 -msgid "Host notification" +#: ../settings/system/network.rst:2 +msgid "Network" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:63 -msgid "For updates on the status of the server itself." +#: ../settings/system/network.rst:8 +msgid "" +"The proxy settings can only be saved after successfully testing the proxy " +"connection." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:77 -msgid "🤔 **What's with all the env vars?**" +#: ../settings/system/network.rst:15 +msgid "Proxy Address." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:79 +#: ../settings/system/network.rst:12 msgid "" -"Whenever Checkmk runs these scripts, it needs to provide some information " -"about the event that triggered the notification. This information is passed " -"in the form of these ``$NOTIFY_*`` environment variables." +"Allows you to provide a proxy server if needed. This is relevant for network " +"communication by Zammad." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:85 -msgid "" -"You can specify additional parameters to pass to the script when you're " -"setting up your notification rule, but the ones you see here are all " -"provided by default." +#: ../settings/system/network.rst:15 +msgid "It **does not** affect the update process or Elasticsearch." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:90 -msgid "Email Alerts" +#: ../settings/system/network.rst:18 +msgid "Username for proxy connection." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:94 +#: ../settings/system/network.rst:18 msgid "" -"🐞 **There are known bugs** in Zammad's processing of email from Checkmk. " -"This section will be completed once they have been resolved. (Learn more at " -"GitHub issues `#2377 `_ & " -"`#2180 `_.)" +"If your proxy server requires authentication, provide the username here." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:100 -msgid "In the meantime, we encourage you to set up API alerts instead." +#: ../settings/system/network.rst:21 +msgid "Password for proxy connection." msgstr "" -#: ../system/integrations/clearbit.rst:2 -msgid "Clearbit" +#: ../settings/system/network.rst:21 +msgid "" +"If your proxy server requires authentication, provide the password here." msgstr "" -#: ../system/integrations/clearbit.rst:4 +#: ../settings/system/network.rst:26 +msgid "No proxy for the following hosts." +msgstr "" + +#: ../settings/system/network.rst:24 msgid "" -"With our Clearbit integration, you can easily enrich the information " -"provided by Zammad. If the customers or agents email address is known to " -"Clearbit, it will share all information it has regarding the user with " -"Zammad. Those information can include the following:" +"Exception list for hosts you can't or don't want to reach via proxy server." msgstr "" -#: ../system/integrations/clearbit.rst:9 -msgid "Avatar" +#: ../settings/system/network.rst:27 +msgid "Default: ``localhost,127.0.0.0,::1``" msgstr "" -#: ../system/integrations/clearbit.rst:10 -msgid "Address information" +#: ../settings/system/services.rst:2 +msgid "Services" msgstr "" -#: ../system/integrations/clearbit.rst:11 -msgid "Website information" +#: ../settings/system/services.rst:10 +msgid "Image Service" msgstr "" -#: ../system/integrations/clearbit.rst:12 -msgid "A BIO (as Note by default)" +#: ../settings/system/services.rst:5 +msgid "Defines the backend for user and organization image lookups." msgstr "" -#: ../system/integrations/clearbit.rst:14 -msgid "" -"If needed, you can add further custom objects and add mappings to them, so " -"the Clearbit information can be filled within the database. In general you " -"can get any information from Clearbit, as long as you have a mapping to an " -"Zammad object." +#: ../settings/system/services.rst:7 +msgid "Default: ``Zammad Image Service`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:21 +#: ../settings/system/services.rst:9 msgid "" -"Clearbit does have a mapping of fields like LDAP and Exchange have, but does " -"not \"win\" against Zammad information. This means that if you have e.g. the " -"last name field filled in already and Clearbit has other information on " -"that, it will not be updated." +"Make sure your on premise installation has ``HTTPS`` access to ``images." +"zammad.com``." msgstr "" -#: ../system/integrations/clearbit.rst:26 -msgid "" -"However: If let's say the last name has been set by Clearbit and Zammad " -"notices that the last name on the Clearbit source has changed, Zammad will " -"also update this value." +#: ../settings/system/services.rst:18 +msgid "Geo Calendar Service" msgstr "" -#: ../system/integrations/clearbit.rst:33 +#: ../settings/system/services.rst:13 msgid "" -"The configuration of Clearbit is really easy and done fast! Just login to " -"your Clearbit-Account, go to \"API\" and copy the secret-API-Key." +"Defines the backend for geo calendar lookups. Used for initial calendar " +"setup." msgstr "" -#: ../system/integrations/clearbit.rst:38 -msgid "" -"Now change to your Zammad instance, go to Integrations (System) -> Clearbit " -"in the admin panel. Paste your API-Key into the API-Key-Field and decide if " -"Zammad should create unknown Organizations automatically, if the user does " -"not have one yet (and Clearbit knows it). The shared option decides if the " -"new organizations Zammad creates with Clearbit should be shared ones." +#: ../settings/system/services.rst:16 +msgid "Default: ``Zammad GeoCalendar Service`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:47 +#: ../settings/system/services.include.rst:2 msgid "" -"If you're unsure what option to choose, better stick with \"no\". You can " -"also learn more about :doc:`/manage/organizations/index`." +"Make sure your on premise installation has ``HTTPS`` access to ``geo.zammad." +"com``." msgstr "" -#: ../system/integrations/clearbit.rst:52 -msgid "" -"The Mapping option works similar to the mapping within the Exchange and LDAP " -"sync. You can add further mappings for e.g. custom fields if you need more " -"information that Clearbit can provide." +#: ../settings/system/services.rst:26 +msgid "Geo IP Service" msgstr "" -#: ../system/integrations/clearbit.rst:58 +#: ../settings/system/services.rst:21 msgid "" -"If you want to add more Clearbit fields and want to learn more about " -"available fields on their API, you can take a look at their `API " -"documentation `_." +"Defines the backend for geo IP lookups. Shows also location of an IP address " +"if an IP address is shown." msgstr "" -#: ../system/integrations/clearbit.rst:62 -msgid "" -"If you're happy with the above chosen Settings and your mapping, just save " -"the changes and enable Clearbit integration. Zammad will now start polling " -"the Clearbit API as users contact you." +#: ../settings/system/services.rst:24 +msgid "Default: ``Zammad GeoIP Service`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:68 -msgid "" -"Zammad does not synchronize with Clearbit on a regular basis, but on demand " -"if needed. This saves API calls." +#: ../settings/system/services.rst:32 +msgid "Geo Location Service" msgstr "" -#: ../system/integrations/clearbit.rst:73 +#: ../settings/system/services.rst:29 msgid "" -"Below the Settings and Mappings, you'll find our Integration log. You can " -"see what requests Zammad sent to Clearbit and also the APIs Response." +"Defines the backend for geo location lookups to store geo locations for " +"addresses." msgstr "" -#: ../system/integrations/clearbit.rst:78 +#: ../settings/system/services.rst:32 msgid "" -"By the way, you can also view the API log on the Clearbit website - the " -"information seen is basically the same." -msgstr "" - -#: ../system/integrations/clearbit.rst:84 -msgid "Example When Adding a User" +"Default: ``OpenStreetMap (ODbL 1.0, http://osm.org/copyright)`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:86 +#: ../settings/system/services.rst:36 msgid "" -"To show you how fast information is added, we added a small Screencast " -"below. This shows the creation of the User Alex from Clearbit. As we already " -"set the last name of Alex to \"X\", Zammad did not update it. What Zammad " -"did was to add further information it received from Clearbit." +"You can find a detailed privacy information on what we store for how long on " +"our :docs:`Privacy Appendix ` inside of our System " +"Documentation." msgstr "" -#: ../system/integrations/cti/generic.rst:2 -msgid "CTI (generic)" +#: ../settings/system/storage.rst:2 +msgid "Storage" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:1 +#: ../settings/system/storage.rst:6 msgid "" -"This integration enables Zammad to provide a caller log to your agents. With " -"this your agents can greet your customers by their name and are supported by " -"Zammad with automatically opening a new ticket dialog or the user profile." +"Here you can define where Zammad stores attachments for tickets and the " +"knowledge base. By default, we're writing to the ``Database`` - you can " +"switch to ``Filesystem`` or ``Simple Storage (S3)`` at any time. In this " +"case please have a look on the following instructions." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:6 +#: ../settings/system/storage.rst:11 msgid "" -"Click the toggle next to the heading to activate or deactivate this " -"integration." +"If you have a busy Zammad instance, we strongly encourage you to use " +"filesystem storage instead of \"Database\". This will greatly improve system " +"performance (de-crease database load and size)." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:9 -msgid "" -"If you want to learn more on how your agents can use this function, please " -"refer the :user-docs:`user documentation `." +#: ../settings/system/storage.rst:19 +msgid "Database" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:14 +#: ../settings/system/storage.rst:17 msgid "" -"Automatically opening new ticket dialogues or user profiles requires agent " -"to extension mapping - see more below." -msgstr "" - -#: ../system/integrations/cti/includes/introduction.include.rst:20 -msgid "Please note the following limitations to reduce confusion later on:" +"This is the default storage method. The attachments are stored directly in " +"the database. If your Zammad instance grows, we recommend one of the other " +"methods to maintain performance." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:22 -msgid "CTI integrations provide caller log functions only." +#: ../settings/system/storage.rst:38 +msgid "Filesystem" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:23 +#: ../settings/system/storage.rst:22 msgid "" -"This integration does not provide any VoIP functionalities; you can't make " -"phone calls from within Zammad." +"This storage method is recommended for all Zammad instances, especially for " +"those with a higher load. If you choose filesystem, your files are written " +"to ``/opt/zammad/storage/``." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:25 +#: ../settings/system/storage.rst:26 msgid "" -"If your browser supports ``tel``-URLs, you can click on phone numbers for " -"automatic dialing. This requires additional software / configuration on your " -"agent's computers." +"Moving attachments from \"Database\" to \"Filesystem\" can be run during " +"production use. However, you should consider your framework conditions (e.g. " +"bandwidth, system load in production) to define the right moment." msgstr "" -#: ../system/integrations/cti/generic.rst:9 -#: ../system/integrations/cti/placetel.rst:14 -#: ../system/integrations/cti/sipgate.rst:14 -msgid "Please provide the following requirements:" +#: ../settings/system/storage.rst:32 +msgid "**You noticed slow updates of Zammad?**" msgstr "" -#: ../system/integrations/cti/generic.rst:11 +#: ../settings/system/storage.rst:34 msgid "" -"A telephone system that supports webhooks (outbound) (best option are those " -"that allow customizing the calls)." +"While Zammad is beeing updated, it enforces a recursive \"change " +"owner\" (chown) for this directory. For instances with many files this can " +"be time consuming. To mitigate that you can move your files and create a " +"symlink in ``/opt/zammad/storage/`` to the new directory. Of course you have " +"to make sure on your own that the permissions are always correct." msgstr "" -#: ../system/integrations/cti/generic.rst:13 -msgid "A unique Call-ID during the call session." +#: ../settings/system/storage.rst:95 +msgid "Simple Storage (S3)" msgstr "" -#: ../system/integrations/cti/generic.rst:14 -msgid "Call event data (both numbers and direction)." +#: ../settings/system/storage.rst:41 +msgid "" +"To use the Simple Storage (S3), you have to provide some settings, which " +"can't be accessed in the UI (see instructions below)." msgstr "" -#: ../system/integrations/cti/generic.rst:15 -msgid "Your Zammad instance must be reachable for your telephony system." +#: ../settings/system/storage.rst:44 +msgid "" +"⚠️ Please note that the current implementation is in its early stages and can " +"be modified in the future." msgstr "" -#: ../system/integrations/cti/generic.rst:17 +#: ../settings/system/storage.rst:47 msgid "" -"If you want to learn more on what kind of requests are supported by Zammad " -"and what it expects, please consult our :docs:`CTI-API documentation `." +"The prerequisite is to have access to a S3-compatible storage and to have " +"all necessary parameters available (which depends on your storage provider; " +"if in doubt, please ask there for help)." msgstr "" -#: ../system/integrations/cti/generic.rst:22 -#: ../system/integrations/cti/placetel.rst:27 -#: ../system/integrations/cti/sipgate.rst:30 -msgid "Available Settings" +#: ../settings/system/storage.rst:51 +msgid "Steps to configure S3:" msgstr "" -#: ../system/integrations/cti/generic.rst:29 -#: ../system/integrations/cti/placetel.rst:41 -#: ../system/integrations/cti/sipgate.rst:40 -msgid "Endpoint Settings" +#: ../settings/system/storage.rst:53 +msgid "" +"Copy ``config/zammad/storage.yml.dist`` to ``config/zammad/storage.yml``" msgstr "" -#: ../system/integrations/cti/generic.rst:25 -msgid "" -"Zammad will list your generic CTI endpoint here. It contains a unique token " -"so ensure to keep this URL save." +#: ../settings/system/storage.rst:54 +msgid "Edit the copied file in one of the following ways:" msgstr "" -#: ../system/integrations/cti/generic.rst:28 +#: ../settings/system/storage.rst:56 msgid "" -"You'll need this endpoint for your PBX to talk to Zammad, see :docs:`CTI-API " -"documentation `." +"Either provide your S3 configuration with one attribute per line like in the " +"upper area of the file" msgstr "" -#: ../system/integrations/cti/includes/important-dont-forget-saving.include.rst:3 +#: ../settings/system/storage.rst:58 msgid "" -"All following options **do not save automatically**. Always use the Save " -"button on the lower end of the integration page!" +"Or provide your S3 configuration as an URL (which you can find at the end of " +"the file). Note: you can also provide this URL as environment variable (:" +"docs:`see system documentation `) without using this yml-file." msgstr "" -#: ../system/integrations/cti/generic.rst:43 -#: ../system/integrations/cti/placetel.rst:49 -#: ../system/integrations/cti/sipgate.rst:52 -msgid "Call Settings" +#: ../settings/system/storage.rst:62 +msgid "" +"We recommend the deletion of the not used configuration style to avoid " +"inconsistencies." msgstr "" -#: ../system/integrations/cti/generic.rst:39 -#: ../system/integrations/cti/placetel.rst:49 -#: ../system/integrations/cti/sipgate.rst:37 -#: ../system/integrations/cti/sipgate.rst:50 -msgid "Inbound" +#: ../settings/system/storage.rst:65 +msgid "Restart Zammad so the config file / environment variable is loaded" msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:1 +#: ../settings/system/storage.rst:66 msgid "" -"This option allows you to block specific incoming caller IDs. It allows you " -"to temporarily reject e.g. spam callers without having to contact providers " -"or PBX administrators." +"Set the \"Storage Method\" in Zammad to ``Simple Storage (S3)`` in Settings " +"> System > Storage and click on \"Submit\". After that, Zammad checks your " +"configuration and the connection to the service and will raise an error " +"message if something is wrong." msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:11 -msgid "Caller ID to block" +#: ../settings/system/storage.rst:72 +msgid "A very simple storage configuration could look like this:" msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 -msgid "Provide caller IDs to block in ``E.164`` format." +#: ../settings/system/storage.rst:85 +msgid "" +"Before setting the storage method to ``Simple Storage (S3)`` (step 4), " +"please make sure to have a working setup." msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:8 +#: ../settings/system/storage.rst:88 msgid "" -"Your telephony system has to support this function. Zammad will send a " -"``reject`` response which will cause your telephony system to hang up the " -"call. To callers this usually will feel like the line is busy." +"You can verify this by running ``rails r 'Rails.logger = Logger.new(STDOUT); " +"pp Store::Provider::S3.ping?'`` in your Zammad directory. If everything is " +"fine, you should see ``true``, else you should see ``false`` and a simple " +"error message." msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:14 +#: ../settings/system/storage.rst:93 msgid "" -"Provide a meaningful note for your fellow administrators to remind yourself " -"why you've chosen to block the number." +"If you installed Zammad through a package manager (rather than from source), " +"replace ``rails r`` with ``zammad run rails r`` above. To learn more, see :" +"docs:`Administration via Console `." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 -#: ../system/integrations/cti/includes/outbound-calls.include.rst:17 -#: ../system/integrations/cti/sipgate.rst:40 -msgid "Outbound" +#: ../settings/ticket.rst:4 +msgid "" +"Here you can adjust general ticket settings. Additional ones for the ticket " +"composer interface can be found in the :doc:`/misc/composer`." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:1 -msgid "" -"In many cases you may want to use a different caller ID depending on the " -"destination you're calling. This may apply due to specific connection rates " -"to other countries or because you want your customer to feel you're calling " -"from the same country." +#: ../settings/ticket.rst:11 +msgid "Ticket Hook (default: ``Ticket#``)" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:6 -msgid "This option expects ``E.164`` number formats." +#: ../settings/ticket.rst:11 +msgid "The identifier for a ticket; *e.g.,* Ticket#, Call#, MyTicket#." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 -msgid "Destination caller ID" +#: ../settings/ticket.rst:38 +msgid "Ticket Hook Position (default: ``right``)" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:5 -msgid "The caller ID or number you're trying to call." +#: ../settings/ticket.rst:14 +msgid "" +"With this setting you can decide (if) where to insert the ticket number." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:7 -msgid "You can use wildcards for e.g. country specific outbound numbers like:" +#: ../settings/ticket.rst:20 +msgid "*Right*" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:9 -msgid "``49*`` for Germany" +#: ../settings/ticket.rst:17 +msgid "" +"This setting will add the ticket reference on the right site of the subject." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:10 -msgid "``4930*`` for Berlin / Germany landlines" +#: ../settings/ticket.rst:20 +msgid "Example: ``Some Subject [Ticket#12345]``" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 -msgid "``33*`` for France" +#: ../settings/ticket.rst:26 +msgid "*Left*" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:15 -msgid "Set Outbound caller ID" +#: ../settings/ticket.rst:23 +msgid "" +"This setting will add the ticket reference on the left site of the subject." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:14 -msgid "" -"The outbound caller ID to set (the number your customer sees on his display) " -"in ``E.164`` number format." +#: ../settings/ticket.rst:26 +msgid "Example: ``[Ticket#12345] Some Subject``" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 -msgid "Provide a short description for fellow administrators." +#: ../settings/ticket.rst:29 +msgid "*None*" msgstr "" -#: ../system/integrations/cti/includes/generic-cti-support-note.includes.rst:3 -msgid "" -"This option requires your PBX to send a specific request to Zammad *before " -"dialing*. Please consult the :docs:`CTI API ` in case " -"you're not sure." +#: ../settings/ticket.rst:29 +msgid "This will completely remove ticket references from the subject." msgstr "" -#: ../system/integrations/cti/generic.rst:52 -#: ../system/integrations/cti/placetel.rst:54 -#: ../system/integrations/cti/sipgate.rst:59 -msgid "Other Settings" +#: ../settings/ticket.rst:33 +msgid "" +"Please ensure to take a look at :doc:`/channels/email/settings` within the " +"email channel to ensure you have at least one reference that helps Zammad to " +"assign follow-ups correctly." msgstr "" -#: ../system/integrations/cti/includes/other-settings-intro.include.rst:1 +#: ../settings/ticket.rst:37 msgid "" -"Below you can find all available additional settings for this CTI " -"integration. For your overview we're sorting them by appearance and " -"reference their description first." +"Disabling this and not setting up any further follow up search will lead to " +"unexpected results!" msgstr "" -#: ../system/integrations/cti/includes/default-caller-id.include.rst:2 -#: ../system/integrations/cti/includes/default-caller-id.include.rst:1 -msgid "Default caller ID for outbound calls" +#: ../settings/ticket.rst:65 +msgid "" +"Ticket Last Contact Behaviour (default: ``Use the start time of the last " +"customer thread (which may consist of multiple articles).``)" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:16 -#: ../system/integrations/cti/includes/records-caller-log.include.rst:15 -msgid "Shown records in caller log" +#: ../settings/ticket.rst:41 +msgid "" +"This setting changes the way Zammad updates the ``Last Contact`` value of a " +"ticket. This is fairly important for overviews and what you expect upon " +"ticket updates of a customer." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:2 +#: ../settings/ticket.rst:52 msgid "" -"Allows you to set the number of shown caller log entries for all users. You " -"can choose from the following values:" +"Use the start time of the last customer thread (which may consist of " +"multiple articles)." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:5 -msgid "60 (default)" +#: ../settings/ticket.rst:46 +msgid "" +"If this option is chosen, Zammad will update the last updated value just " +"once if a customer replies. After that, Zammad will wait for an agent to " +"react." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:6 -msgid "120" +#: ../settings/ticket.rst:50 +msgid "" +"This comes in handy if you want to work tickets in the order of their first " +"update. This will not change ticket orders if customers decide to \"bump\" " +"the ticket affected." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:7 -msgid "180" +#: ../settings/ticket.rst:57 +msgid "Use the time of the very last customer article." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:8 -msgid "240" +#: ../settings/ticket.rst:55 +msgid "" +"When setting this option, Zammad will always update the last updated value. " +"This means that if ordering by ``Last Update``, ticket orders will change if " +"customers \"bump\" the ticket." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:9 -msgid "300" +#: ../settings/ticket.rst:64 +msgid "Last contact value used on :doc:`/manage/overviews`" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:11 -msgid "**🥵 Potential performance issue**" +#: ../settings/ticket.rst:65 +msgid "Last contact value used on :doc:`/manage/trigger`" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:13 +#: ../settings/ticket.rst:88 msgid "" -"Setting this setting higher than 60 may cause serious performance issues on " -"very busy instances. Keep in mind that this setting causes Zammad to poll " -"and send up to 300 records to *all active agent sessions* in very short time " -"periods." +"Ticket Organization Reassignment (default: ``Update the most recent tickets." +"``)" msgstr "" -#: ../system/integrations/cti/generic.rst:73 -msgid "Caller Log Filter" +#: ../settings/ticket.rst:68 +msgid "" +"This setting changes the way Zammad updates the organization field of the " +"tickets whenever the primary organization of a user is changed." msgstr "" -#: ../system/integrations/cti/generic.rst:55 -msgid "" -"This function allows you to provide call information based on e.g. queues " -"only to agents that really need the information." +#: ../settings/ticket.rst:74 +msgid "Update the most recent tickets." msgstr "" -#: ../system/integrations/cti/generic.rst:58 +#: ../settings/ticket.rst:72 msgid "" -"Why? If you have a team for several countries or departments, you don't want " -"to bug your agents from other departments. Leaving these options empty will " -"fallback to showing everything to everyone." +"If this option is chosen, Zammad will update the 100 most recent tickets " +"where the user is the ticket customer. The ticket organization field will be " +"automatically set to the new primary organization of the user." msgstr "" -#: ../system/integrations/cti/generic.rst:64 -msgid "Destination caller ID or Queue" +#: ../settings/ticket.rst:88 +msgid "Do not update any tickets." msgstr "" -#: ../system/integrations/cti/generic.rst:63 +#: ../settings/ticket.rst:77 msgid "" -"This depends on your PBX and usually is either a queue ID, phone number or " -"extension." +"When choosing this option, Zammad will not update any tickets when the " +"user's primary organization is changed." msgstr "" -#: ../system/integrations/cti/generic.rst:69 -msgid "Agents" +#: ../settings/ticket.rst:80 +msgid "**Use with care!**" msgstr "" -#: ../system/integrations/cti/generic.rst:67 +#: ../settings/ticket.rst:82 msgid "" -"Select the agents that are responsible for the group. These agents will then " -"see caller log entries and call notifications fitting to said queue." +"Using this option may lead to inconsistencies in the system as the ticket " +"organization may become decoupled from the ticket customer." msgstr "" -#: ../system/integrations/cti/generic.rst:0 +#: ../settings/ticket.rst:85 msgid "" -"Screenshot showing the caller log filter table with pre filled sample data" +"However, you may use this option if you wish to maintain :ref:`the shared " +"access ` to the ticket for all organization " +"members of the original organization of the customer." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:6 -msgid "" -"With recent logs Zammad allows you to view the latest calls for the CTI " -"functionality. This usually comes in handy, when you're looking for errors." +#: ../settings/ticket.rst:110 +msgid "Ticket Number Format (default: ``Increment (SystemID.Counter)``)" msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:0 +#: ../settings/ticket.rst:94 msgid "" -"Screenshot showing several incoming requests within Recent logs section." +"This setting defines the way Zammad's ticket number will look. Changing this " +"setting in production will cause follow up detection to fail." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:16 -msgid "I'm just here to clear floats up." +#: ../settings/ticket.rst:102 +msgid "Increment (SystemID.Counter)" msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:20 +#: ../settings/ticket.rst:98 msgid "" -"By clicking on the entry of interest, Zammad will provide more details on " -"the call in question. You'll see the payload it received and also the " -"response that was sent." +"The increment value contains the SystemID (automatically generated during " +"installation) and a increment which counts up with every new Ticket. The " +"increment will automatically get another digit if needed." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:0 -msgid "" -"Screenshot showing detailed information of a specific log entry of recent " -"logs" +#: ../settings/ticket.rst:102 +msgid "Examples: ``1010138``, ``1010139``" msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:31 -msgid "x" +#: ../settings/ticket.rst:110 +msgid "Date (Year.Month.Day.SystemID.Counter)" msgstr "" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 -#: ../system/integrations/cti/includes/troubleshooting.include.rst:9 -msgid "My Phone page stays blank, signalling does work..." +#: ../settings/ticket.rst:105 +msgid "" +"This version of the ticket number is fairly long. However, because it " +"contains the date of ticket creation, it also allows you to see when the " +"ticket has been created. You may feel familiar with this number format if " +"you've worked with OTRS already." msgstr "" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:5 -msgid "" -"If you've made sure that signalling works (check Recent logs) and your " -"Caller Log still stays empty, please ensure that you only configured one CTI " -"integration version. Specifically defining more than one agent mapping on " -"the different integration variants will be the issue." +#: ../settings/ticket.rst:110 +msgid "Examples: ``201206231010138``, ``201206231010139``" msgstr "" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 -msgid "Clear the not needed agent mapping and reload your browser page." +#: ../settings/ticket.rst:137 +msgid "OPTIONS" msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:1 +#: ../settings/ticket.rst:113 msgid "" -"By mapping your agents extension to their existing Zammad users, Zammad can " -"provide a new ticket dialog or open the user profile for the agent that " -"picks up the call." +"The below options allow you to further customize your ticket number. The " +"availability of options differ depending of the chosen ticket number format " +"above." msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:5 -msgid "" -"This speeds up ticket aiding, no matter if it's for existing tickets or new " -"ones!" +#: ../settings/ticket.rst:122 +msgid "Checksum (default: ``no``)" msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:8 +#: ../settings/ticket.rst:118 msgid "" -"To see it work from the agent's perspective, have a look on :user-docs:`user " -"documentation `." +"If set to yes, we'll built a checksum to further \"unique\" the ticket " +"number of your system. If you're dealing with many other ticket systems this " +"might help to prevent false positive follow up detection on tickets." msgstr "" -#: ../system/integrations/cti/placetel.rst:2 -msgid "Placetel CTI" +#: ../settings/ticket.rst:122 +msgid "This will also add another digit to the ticket number." msgstr "" -#: ../system/integrations/cti/placetel.rst:16 -msgid "You need an administrative Placetel account for your organization." +#: ../settings/ticket.rst:137 +msgid "Min. size of Number (default: ``5``)" msgstr "" -#: ../system/integrations/cti/placetel.rst:17 -#: ../system/integrations/cti/sipgate.rst:20 +#: ../settings/ticket.rst:125 msgid "" -"Your Zammad instance must be allowed to communicate to external services." +"This setting defines the minimum length of your ticket number. If your " +"counter is not yet high enough, Zammad will fill the number with zeros to " +"ensure the wanted length." msgstr "" -#: ../system/integrations/cti/placetel.rst:18 -msgid "Placetel must be able to reach your Zammad instance." -msgstr "" - -#: ../system/integrations/cti/placetel.rst:22 -msgid ":doc:`provider-configurations/placetel`" -msgstr "" - -#: ../system/integrations/cti/placetel.rst:21 +#: ../settings/ticket.rst:129 msgid "" -"Learn how to configure Placetel to enable Zammad and Placetel to communicate " -"with each other." +"Please note that the minimum length is ``3`` (SystemID + at least one digit " +"if below 10). Also, if the length is no longer long enough, the number will " +"automatically get one digit longer. Ticket-Numbers **do not overflow**, thus " +"it's save to keep it at 5 or set it lower if wanted." msgstr "" -#: ../system/integrations/cti/placetel.rst:32 +#: ../settings/ticket.rst:135 msgid "" -"The here listed endpoint settings are relevant for the :doc:`integration " -"configuration with Placetel `." +"This option is only available if ticket number format is set to " +"``Increment``!" msgstr "" -#: ../system/integrations/cti/placetel.rst:37 -#: ../system/integrations/i-doit.rst:53 -msgid "Endpoint" +#: ../settings/ticket.rst:142 +msgid "Auto-Assignment" msgstr "" -#: ../system/integrations/cti/placetel.rst:36 +#: ../settings/ticket.rst:144 msgid "" -"This endpoint will be required for the Zammad integration within the " -"Placetel web interface." -msgstr "" - -#: ../system/integrations/cti/placetel.rst:41 -msgid "API Token" +"In a larger Zammad environment, it happens that several agents open the same " +"ticket at the same time. Although collision detection is then effective, the " +"efficiency of processing can be increased by means of the automatic " +"assignment of tickets when a ticket is opened." msgstr "" -#: ../system/integrations/cti/placetel.rst:40 +#: ../settings/ticket.rst:149 msgid "" -"You'll receive this token within the ``Web API`` menu. Make sure to copy " -"this value, it's only shown once!" -msgstr "" - -#: ../system/integrations/cti/placetel.rst:71 -#: ../system/integrations/cti/sipgate.rst:77 -msgid "Phone Extension to Agent Mapping" +"The automatic assignment of tickets can be activated and configured in the " +"admin area under Settings > Ticket > Auto Assignment." msgstr "" -#: ../system/integrations/cti/placetel.rst:0 -msgid "Screenshot showing sample user mappings in between Placetel and Zammad" +#: ../settings/ticket.rst:152 +msgid "" +"The auto assignment only works if the ticket has no owner yet. By default, " +"the agent can always reset the ticket owner to ``-`` if needed." msgstr "" -#: ../system/integrations/cti/placetel.rst:64 +#: ../settings/ticket.rst:155 msgid "" -"You can find your agents Placetel username combination required within ⚙️ PBX " -"→ VoIP destinations. Within the \"Advanced settings\" section you're looking " -"for \"SIP user name\" and \"SIP server\"." +"If you want to use this function for only specific tickets, you can " +"configure the conditions accordingly to meet your requirement. By default " +"the condition affects all tickets with the state ``open``." msgstr "" -#: ../system/integrations/cti/placetel.rst:68 -msgid "Combine these two like so: ``@``." +#: ../settings/ticket.rst:161 +msgid "" +"If you need to exclude users (e.g. a group leader), you can search and " +"select the desired agents in the ``Exception Users`` list. The search " +"function in this area is only effective, if you have too many agents to " +"display at once to help you with the configuration." msgstr "" -#: ../system/integrations/cti/placetel.rst:0 -msgid "Sample VoIP credentials for a Placetel user" +#: ../settings/ticket.rst:167 +msgid "Notifications" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:2 -msgid "Setup Placetel connection for Zammad" +#: ../settings/ticket.rst:191 +msgid "Default Notifications" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:6 +#: ../settings/ticket.rst:170 msgid "" -"This configuration step requires a *full* administrative Placetel account. " -"You may receive forbidden error messages with Placetel in case your " -"permissions are not high enough." +"This setting allows you to configure the default ticket notifications that " +"will be applied to all new agent users (incl. users who were just assigned " +"agent role). Simply change the notification matrix to desired state and " +"press **Save**." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:10 +#: ../settings/ticket.rst:175 msgid "" -"The following actions can be configured via the `Placetel web interface " -"`_." -msgstr "" - -#: ../system/integrations/cti/provider-configurations/placetel.rst:29 -msgid "Step 1: Activate Zammad integration" +"In case an agent already exists, their ticket notification preferences will " +"be preserved. Optionally, you can also **Apply current defaults to all " +"agents**." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:14 +#: ../settings/ticket.rst:181 msgid "" -"Within Integrations, scroll down to Partner integrations and select Zammad." +"**Potential time-consuming action:** Applying default ticket notifications " +"to all agent users may take some time to complete, be patient! The exact " +"time will depend on the size of your system and the number of agents." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:17 +#: ../settings/ticket.rst:185 msgid "" -"You can alternatively filter by \"Ticket Systems\" to reduce the number of " -"entries on the page. You'll still want to look for Partner integrations. 🤓" +"**Active agents only!** When current default ticket notifications are " +"applied, only active agent users are considered. In case an agent is re-" +"activated *after* this action, they will still have the old notification " +"configuration." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:21 +#: ../settings/ticket.rst:190 msgid "" -"Within the Zammad integration now press \"Activate\". A new tab ``API`` " -"becomes available - open this tab." +"In case you want to go back to the initial state of ticket notifications, " +"you can click on **Reset to default** button." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:24 -msgid "" -"Now tick \"Enable Call Control / Notify API\" and paste the Placetel " -"endpoint from your Zammad instance into the field \"URL of your API " -"endpoint\". Save to apply the settings" +#: ../settings/ticket.rst:196 +msgid "Duplicate Detection" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 -msgid "Screencast showing how to activate the Zammad integration" +#: ../settings/ticket.rst:238 +msgid "Detect Duplicate Ticket Creation" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:51 -msgid "Step 2: Generate API Token for Placetel" +#: ../settings/ticket.rst:199 +msgid "" +"This setting turns on the duplicate ticket detection mechanism during ticket " +"creation. If similar tickets are found in the system, a suitable warning " +"will be shown to the user trying to create a ticket." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:32 -msgid "" -"Go back to the integrations page and scroll down to \"Web API\". Generate a " -"new API token by using the \"Create a new API token\" button." +#: ../settings/ticket.rst:206 +msgid "A Sample Duplicate Ticket Warning" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:37 +#: ../settings/ticket.rst:208 msgid "" -"If you already generated a token either use your existing token or reset it " -"by using above mentioned button. Placetel will ask you to conform this reset." +"You can choose which ticket attributes will be matched by selecting them in " +"**Attributes to compare** field. Only if the ticket attribute value provided " +"by the user in the ticket create form is *equal* with the attribute in an " +"existing ticket, the warning will be shown." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:41 -msgid "" -"Please keep in mind that existing API scripts may no longer work due to " -"token resets!" +#: ../settings/ticket.rst:213 +msgid "**Warning title** and **Warning message** are configurable as well." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:44 +#: ../settings/ticket.rst:215 msgid "" -"Copy the provided API token and insert it into the \"API Token\" field " -"within Zammad's Placetel integration." +"You can limit the detection only to certain user roles. By default, only " +"agents will see the warning." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:47 +#: ../settings/ticket.rst:218 msgid "" -"Apply your changes by using the \"Save\" button on the bottom of the " -"Placetel integration page and activate the Placetel integration." +"If you don't want to show the matched tickets as part of the warning, you " +"can set **Show matching ticket(s) in the warning** setting to *no*." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +#: ../settings/ticket.rst:221 msgid "" -"Screencast showing how to retrieve an API token from Placetel for Zammad" +"By default, **Permission level for looking up ticket** is set to *User*, " +"which means user permissions will be honored during sarch. The user will " +"see the warning only if tickets they have access to are matched. " +"Alternatively, you can set this setting to *System*, in which case the " +"search will happen within *all* tickets in the system, regardless of user " +"permissions." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:73 -#: ../system/integrations/cti/provider-configurations/sipgate.rst:77 -msgid "Step 3: Restrict the numbers to notify on" +#: ../settings/ticket.rst:227 +msgid "**🦺 Safety first!**" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:54 +#: ../settings/ticket.rst:229 msgid "" -"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " -"the the Integrations page of the Placetel web interface, go to \"Notify " -"API\"." +"Even if the permission level is set to *System*, the user will not be shown " +"the tickets they don't have access to in the warning, even if they match." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:58 +#: ../settings/ticket.rst:233 msgid "" -"Lower on the page Placetel allows you to restrict the numbers to notify on. " -"You'll find this within the \"External routing API\" part." +"However, just the confirmation about the existence of the tickets in the " +"system may be considered an unwanted information disclosure. Use this option " +"carefully!" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +#: ../settings/ticket.rst:237 msgid "" -"Screenshot showing a sample selection of phone numbers to use for the " -"Placetels notify API" +"Finally, you can configure between matching within **All tickets** or **Open " +"tickets** only by setting **Match tickets in following states**. Depending " +"on the current ticket state, a ticket may or not be matched." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:66 -msgid "" -"This menu point also provides a API request log from Placetel view. Just " -"open \"Recent responses of your API endpoint\" to learn more." +#: ../system/core-workflows.rst:2 +msgid "Core Workflows" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:69 +#: ../system/core-workflows.rst:4 msgid "" -"If you want to see Zammad's perspective, use the \"Recent Logs\" part from " -"within the Placetel integration page." +"Core Workflows allow you to adjust object attributes in many ways. For " +"example:" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 -msgid "Screenshot showing sample log entries for Placetels API calls to Zammad" +#: ../system/core-workflows.rst:7 +msgid "show / hide fields" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:77 -msgid "Step 4 (optional): Further configurations for Placetel" +#: ../system/core-workflows.rst:8 +msgid "adjust mandatory setting" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:76 +#: ../system/core-workflows.rst:9 +msgid "manipulate available options" +msgstr "" + +#: ../system/core-workflows.rst:11 msgid "" -"If needed, you can now configure Zammad's Placetel integration in more " -"detail. You can learn more about your options here: :ref:`Placetel " -"integration settings `." +"With this, you can provide exactly the information your users really need!" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:2 -msgid "Setup Sipgate connection for Zammad" +#: ../system/core-workflows.rst:15 +msgid "" +"If the pre-defined :doc:`/system/objects` are not enough, please add them " +"beforehand." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +#: ../system/core-workflows.rst:17 msgid "" -"Sipgate has no english web interface which is why this documentation page is " -"mixing up languages badly." +"If you experience slow or unreliable field updates, please see :ref:`Core " +"Workflow Ajax Modus `" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +#: ../system/core-workflows.rst:22 msgid "" -"Please also note that the availability of API addons highly depends on your " -"package trier. Usage of sipgate.io packages *is not free*, please check " -"their `pricing page `_ before!" +"This is a very enhanced functionality and can cause unexpected UI behavior. " +"Please ensure to test your use cases after configuration to reduce surprises." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:35 -msgid "Step 1: Book sipgate.io package" +#: ../system/core-workflows.rst:None +msgid "Dialogue for adding a new workflow" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:13 -msgid "Skip to step 2 if you already have the package booked!" +#: ../system/core-workflows/condition-operators.rst:2 +msgid "Core Workflow Condition Operators" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:15 +#: ../system/core-workflows/condition-operators.rst:4 msgid "" -"Login to an administrative Sipgate account and navigate to " -"``Accountverwaltung``. You'll see several different options depending on " -"your booked packages. Select ``Verträge & Produkte`` to continue." +"You might know that there is a separate section for explaining :doc:" +"`condition operators `. Head over there to " +"see a detailed explanation of many conditions and operators." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:19 +#: ../system/core-workflows/condition-operators.rst:8 msgid "" -"Scroll down to the section ``Zusätzliche Produkte buchen`` and look for " -"``sipgate.io`` - select this product by using the ``Produkte anzeigen``-" -"Button." -msgstr "" - -#: ../system/integrations/cti/provider-configurations/sipgate.rst:23 -msgid "" -"On the next page select either one of the ``sipgate.io`` packages or ``Push-" -"API Package Free``. Follow the dialogue by booking the addon. You'll be " -"returned to your contract overview and now should see the selected addon in " -"your list." +"Due to differences to other places in Zammad which are also using conditions " +"(e.g. triggers), you can find a dedicated description of operators for core " +"workflows below." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:30 +#: ../system/core-workflows/condition-operators.rst:12 msgid "" -"The availability for ``sipgate.io`` packages and their levels highly depends " -"on the overall account type and product you've booked with Sipgate." +"Be aware that the availability of the operators depends on the selected " +"attribute and its field type. Some of the operators may only be available " +"for system attributes (e.g. for \"tags\", \"active\")." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screencast showing the process on how to book the required sipgate.io addon" +#: ../system/core-workflows/condition-operators.rst:20 +msgid "Operator" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:52 -msgid "Step 2: Configure webhook for Zammad" +#: ../system/core-workflows/condition-operators.rst:22 +msgid "after (absolute)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:38 -msgid "" -"Within your ``Accountverwaltung`` navicate to your product ``sipgate.io``. " -"In the newly opened tab, switch from \"Clients\" to \"Webhooks\" and paste " -"the endpoint URLs from your Zammad instance like so:" +#: ../system/core-workflows/condition-operators.rst:23 +msgid "Matches if a date/time is after a specific point in time." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:42 -msgid "Inbound endpoint to \"Incoming\"" +#: ../system/core-workflows/condition-operators.rst:24 +msgid "after (relative)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:43 -msgid "Outbound endpoint to \"Outgoing\"" +#: ../system/core-workflows/condition-operators.rst:25 +msgid "Matches if a time span after a specified event has passed." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:47 -msgid "" -"Ensure to select at least one call group or phoneline within \"Sources\". " -"Other wise Sipgate will not indicate any incoming or outgoing calls to " -"Zammad." +#: ../system/core-workflows/condition-operators.rst:26 +msgid "before (absolute)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screencast showing how to add Zammad's endpoint URLs to sipgate.ios webhook " -"configuration" +#: ../system/core-workflows/condition-operators.rst:27 +msgid "Matches if a date/time is before a specific point in time." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:55 -msgid "" -"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " -"the Webhooks → URLs section of Sipgate you can select which *sources* " -"Sipgate should notify Zammad about in- and outgoing calls." +#: ../system/core-workflows/condition-operators.rst:28 +msgid "before (relative)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:59 -msgid "" -"Use either specific phone lines or use the option \"Use for all phonelines " -"and groups\" to notify Zammad about all existing lines of your Sipgate " -"account." +#: ../system/core-workflows/condition-operators.rst:29 +msgid "Matches if a time span after a specified event has not passed." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screenshot showing a sample selection of phone numbers to use for the " -"Sipgates webhooks API" +#: ../system/core-workflows/condition-operators.rst:30 +msgid "contains" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:68 -msgid "This section also allows you to enable a Debug log." +#: ../system/core-workflows/condition-operators.rst:31 +msgid "Matches if a specified value is present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "Screenshot showing an enabled Debug log option" +#: ../system/core-workflows/condition-operators.rst:33 +msgid "Matches if all of the specified values are present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:73 -msgid "" -"After enabling you can use the Debug log section to see all sent webhook " -"calls to Zammad. You'll also can see the response." +#: ../system/core-workflows/condition-operators.rst:35 +msgid "Matches if none of the specified values are present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screenshot showing sample log entries for Sipgates webhook calls to Zammad" +#: ../system/core-workflows/condition-operators.rst:36 +msgid "contains not" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:81 -msgid "Step 4 (optional): Further configurations for Sipgate" +#: ../system/core-workflows/condition-operators.rst:37 +msgid "Matches if a specified value is not present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:80 -msgid "" -"If needed, you can now configure Zammad's Sipgate integration in more " -"detail. You can learn more about your options here: :ref:`Sipgate " -"integration settings `." +#: ../system/core-workflows/condition-operators.rst:39 +msgid "Matches if one specified value is present." msgstr "" -#: ../system/integrations/cti/sipgate.rst:2 -msgid "Sipgate (sipgate.io)" +#: ../system/core-workflows/condition-operators.rst:41 +msgid "Matches if one specified value is not present." msgstr "" -#: ../system/integrations/cti/sipgate.rst:16 -msgid "You need an administrative Sipgate account for your organization." +#: ../system/core-workflows/condition-operators.rst:42 +msgid "does not match regex" msgstr "" -#: ../system/integrations/cti/sipgate.rst:17 -msgid "" -"Zammad requires a ``sipgate.io`` addon from the feature store (please note " -"that API calls are not free with Sipgate. Rates may apply and differ from " -"account to account)." +#: ../system/core-workflows/condition-operators.rst:43 +msgid "Matches if content doesn't fit to regex rule." msgstr "" -#: ../system/integrations/cti/sipgate.rst:21 -msgid "Sipgate must be able to reach your Zammad instance." +#: ../system/core-workflows/condition-operators.rst:44 +msgid "ends with" msgstr "" -#: ../system/integrations/cti/sipgate.rst:25 -msgid ":doc:`provider-configurations/sipgate`" +#: ../system/core-workflows/condition-operators.rst:45 +msgid "Matches if content ends with specified value." msgstr "" -#: ../system/integrations/cti/sipgate.rst:24 -msgid "" -"Learn how to configure Sipgate to enable Zammad and Sipgate to communicate " -"with each other." +#: ../system/core-workflows/condition-operators.rst:46 +msgid "ends with one of" msgstr "" -#: ../system/integrations/cti/sipgate.rst:33 -msgid "" -"Below endpoint settings affect the :doc:`sipgate.io configuration `." +#: ../system/core-workflows/condition-operators.rst:47 +msgid "Matches if content ends with one of the specified values." msgstr "" -#: ../system/integrations/cti/sipgate.rst:37 -msgid "This endpoint is required for incoming call hooks." +#: ../system/core-workflows/condition-operators.rst:48 +msgid "from (relative)" msgstr "" -#: ../system/integrations/cti/sipgate.rst:40 -msgid "This endpoint is required for outgoing call hooks." +#: ../system/core-workflows/condition-operators.rst:49 +msgid "Matches if date/time is after a period of time after an event." msgstr "" -#: ../system/integrations/cti/sipgate.rst:0 -msgid "Screenshot showing sample user mappings in between Sipgate and Zammad" +#: ../system/core-workflows/condition-operators.rst:51 +msgid "Matches if content is equal to a specified value." msgstr "" -#: ../system/integrations/cti/sipgate.rst:69 -msgid "" -"You can find your agent's Sipgate username within ``Accountverwaltung → " -"Benutzer``. You're looking for the SIP-ID." +#: ../system/core-workflows/condition-operators.rst:52 +msgid "is any of" msgstr "" -#: ../system/integrations/cti/sipgate.rst:0 -msgid "Sample VoIP credentials for a Sipgate user" +#: ../system/core-workflows/condition-operators.rst:53 +msgid "Matches if content is equal to any of specified values." msgstr "" -#: ../system/integrations/cti/sipgate.rst:77 -msgid "Users with several devices also have several SIP-IDs." +#: ../system/core-workflows/condition-operators.rst:54 +msgid "is modified" msgstr "" -#: ../system/integrations/elasticsearch.rst:2 -msgid "Elasticsearch (SaaS)" +#: ../system/core-workflows/condition-operators.rst:55 +msgid "Matches if content is modified." msgstr "" -#: ../system/integrations/elasticsearch.rst:4 -msgid "" -"The Elasticsearch integration allows you to create a read-only user to use " -"with your favorite reporting tool (e.g. like Grafana)." +#: ../system/core-workflows/condition-operators.rst:57 +#: ../system/core-workflows/condition-operators.rst:61 +msgid "True from the moment of changing content until form submit." msgstr "" -#: ../system/integrations/elasticsearch.rst:7 -msgid "" -"If you want to take full advantage of the Zammad reporting, have a look at " -"our :docs:`Grafana ` " -"setup page as well." +#: ../system/core-workflows/condition-operators.rst:58 +msgid "is modified to" msgstr "" -#: ../system/integrations/elasticsearch.rst:11 -#: ../system/subscription/index.rst:7 -msgid "**🚧 Hosted environment specific 🚧**" +#: ../system/core-workflows/condition-operators.rst:59 +msgid "Matches if content is modified to a specific value." msgstr "" -#: ../system/integrations/elasticsearch.rst:13 -msgid "" -"This integration is only available for Hosted setups. In order to use " -"Elasticsearch you'll need the **Plus** subscription." +#: ../system/core-workflows/condition-operators.rst:62 +msgid "is none of" msgstr "" -#: ../system/integrations/elasticsearch.rst:16 -msgid "" -"Self hosted users have all the control over their self hosted Elasticsearch " -"instances." +#: ../system/core-workflows/condition-operators.rst:63 +msgid "Matches if content is none of any specified values." msgstr "" -#: ../system/integrations/elasticsearch.rst:None -msgid "Elasticsearch integration page on SaaS environments" +#: ../system/core-workflows/condition-operators.rst:65 +msgid "Matches if content is not equal to a specified value." msgstr "" -#: ../system/integrations/elasticsearch.rst:27 -msgid "" -"Please note the following limitations of Elasticsearch access on hosted " -"environments:" +#: ../system/core-workflows/condition-operators.rst:67 +msgid "Matches if content is present." msgstr "" -#: ../system/integrations/elasticsearch.rst:30 -msgid "access to the Elasticsearch index is read-only access" +#: ../system/core-workflows/condition-operators.rst:68 +msgid "just changed" msgstr "" -#: ../system/integrations/elasticsearch.rst:31 -msgid "currently you're limited to user only" +#: ../system/core-workflows/condition-operators.rst:69 +msgid "Matches if content has changed." msgstr "" -#: ../system/integrations/elasticsearch.rst:32 +#: ../system/core-workflows/condition-operators.rst:71 +#: ../system/core-workflows/condition-operators.rst:75 msgid "" -"Reporting tools that require to write into the indexes (like Kibana) are not " -"supported" +"Only true for the moment of changing content until next form field action/" +"click." msgstr "" -#: ../system/integrations/elasticsearch.rst:34 -msgid "IP access restriction is currently not yet supported" +#: ../system/core-workflows/condition-operators.rst:72 +msgid "just changed to" msgstr "" -#: ../system/integrations/elasticsearch.rst:37 -msgid "Activating Elasticsearch Access" +#: ../system/core-workflows/condition-operators.rst:73 +msgid "Matches if content has changed to a specified value." msgstr "" -#: ../system/integrations/elasticsearch.rst:39 -msgid "" -"By default external access to your Elasticsearch index is not active. You " -"can enable the integration at any time if needed." +#: ../system/core-workflows/condition-operators.rst:76 +msgid "matches regex" msgstr "" -#: ../system/integrations/elasticsearch.rst:42 -msgid "" -"Please ensure to note down the password provided - you won't have access to " -"it afterwards." +#: ../system/core-workflows/condition-operators.rst:77 +msgid "Matches if value fits to regex rule." msgstr "" -#: ../system/integrations/elasticsearch.rst:None -msgid "Screencast showing activation of Elasticsearch integration" +#: ../system/core-workflows/condition-operators.rst:79 +msgid "Matches if no content is present." msgstr "" -#: ../system/integrations/elasticsearch.rst:51 -msgid "Connection Settings" +#: ../system/core-workflows/condition-operators.rst:80 +msgid "starts with" msgstr "" -#: ../system/integrations/elasticsearch.rst:53 -msgid "" -"This section holds the most important general information for accessing your " -"Elasticsearch indexes - such as:" -msgstr "" - -#: ../system/integrations/elasticsearch.rst:57 -msgid "A unique subdomain that does not tell your real instance URL." +#: ../system/core-workflows/condition-operators.rst:81 +msgid "Matches if content starts with specified value." msgstr "" -#: ../system/integrations/elasticsearch.rst:61 -msgid "Software" +#: ../system/core-workflows/condition-operators.rst:82 +msgid "starts with one of" msgstr "" -#: ../system/integrations/elasticsearch.rst:60 -msgid "" -"The major version of the search index being used. This is required by some " -"Reporting tools like Grafana." +#: ../system/core-workflows/condition-operators.rst:83 +msgid "Matches if content starts with one of the specified values." msgstr "" -#: ../system/integrations/elasticsearch.rst:64 -msgid "Authentication" +#: ../system/core-workflows/condition-operators.rst:84 +msgid "till (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:64 -msgid "The authentication type being supported. ``Basic Authentication``" +#: ../system/core-workflows/condition-operators.rst:85 +msgid "Matches if date/time is before a period of time before an event." msgstr "" -#: ../system/integrations/elasticsearch.rst:67 -msgid "Available Indexes" +#: ../system/core-workflows/condition-operators.rst:86 +msgid "today" msgstr "" -#: ../system/integrations/elasticsearch.rst:69 -msgid "" -"Within this section we're displaying the -in our opinion- most important " -"indexes for a Zammad instance." +#: ../system/core-workflows/condition-operators.rst:87 +msgid "Matches if date/time is today." msgstr "" -#: ../system/integrations/elasticsearch.rst:72 -msgid "" -"If you require all indexes or our listing is not good enough for you, point " -"your browser to the URL we're providing and append ``/_aliases?" -"pretty=true``. The result should look like this: ``https://.zammad.com/" -"_aliases?pretty=true``." +#: ../system/core-workflows/condition-operators.rst:88 +msgid "within last (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:77 +#: ../system/core-workflows/condition-operators.rst:89 msgid "" -"Your browser will automatically ask for your credentials - you'll then see " -"something like this:" +"Matches if date/time content is within specified period of time before now." msgstr "" -#: ../system/integrations/elasticsearch.rst:125 -msgid "Credentials" +#: ../system/core-workflows/condition-operators.rst:91 +msgid "within next (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:127 +#: ../system/core-workflows/condition-operators.rst:92 msgid "" -"Within this section Zammad displays your available users. The password is " -"provided once (upon activation) and cannot be retrieved after that." +"Matches if date/time content is within specified period of time after now." msgstr "" -#: ../system/integrations/elasticsearch.rst:131 -msgid "" -"If you need to change or reset your Elasticsearch user password, use the " -"\"Reset password\" button in the credentials table. Doing so creates a brand " -"new password for the account in question. This change is immediate, keep in " -"mind that this may affect third party tools connected to your instance." +#: ../system/core-workflows/how-do-they-work.rst:2 +msgid "How do they work?" msgstr "" -#: ../system/integrations/exchange.rst:2 -msgid "Exchange" +#: ../system/core-workflows/how-do-they-work.rst:4 +msgid "" +"Core Workflows are executed according to their priority. If two workflows " +"have the same priority, they are executed in alphabetical order based on " +"their **name**." msgstr "" -#: ../system/integrations/exchange.rst:4 +#: ../system/core-workflows/how-do-they-work.rst:8 msgid "" -"With Zammad's Exchange integration, you can easily use existing address " -"books without having to update more than one source." +"Because of the way Core Workflows work, all changes to attributes are " +"checked with the application server - please see :doc:`limitations` for " +"possible issues." msgstr "" -#: ../system/integrations/exchange.rst:7 +#: ../system/core-workflows/how-do-they-work.rst:12 msgid "" -"However, you should refrain from syncing all addresses, as the results may " -"not be what you expect (Exchange collects huge amounts of addresses). A " -"central address book of your company to sync makes more sense, as you can " -"ensure that Zammad gets only the data you need and want. Apart from this, it " -"is even not possible to sync the Global Address List (GAL) of your Exchange " -"system with Zammad." +"Below we're talking about settings that are important and not self-" +"explanatory." msgstr "" -#: ../system/integrations/exchange.rst:16 +#: ../system/core-workflows/how-do-they-work.rst:17 msgid "" -"**Exchange and LDAP:** The exchange sync can be overruled by Zammad's LDAP " -"integration. If you have the same users in both sources, the LDAP version " -"will always be Zammad's pick." +"Choose the object context you want to run the workflow in. This will decide " +"on your available attributes and actions." msgstr "" -#: ../system/integrations/exchange.rst:19 -msgid "" -"**One way sync:** the Exchange sync is one way. Exchange => Zammad. Changes " -"to your users inside of Zammad might be overwritten by the Exchange sync." +#: ../system/core-workflows/how-do-they-work.rst:20 +msgid "Ticket objects also have access to the ticket customer." msgstr "" -#: ../system/integrations/exchange.rst:24 +#: ../system/core-workflows/how-do-they-work.rst:25 msgid "" -"To configure Exchange integration, simply go to the System > Integrations > " -"Exchange in the admin panel. Press \"change\" and follow the wizard for " -"adding the needed Exchange information to Zammad. On the last two steps " -"Zammad will ask you for the address book(s) and your desired attribute " -"mapping. By default, Zammad only maps email address, first- and lastname. " -"Technically, you can map any Exchange object to a Zammad user object (this " -"also works for custom objects!)." +"Choose in which situation the workflow is applied. Contexts can be combined " +"to avoid duplicate workflows." msgstr "" -#: ../system/integrations/exchange.rst:35 -msgid "" -"If the SSL verification fails while connecting to Exchange, Zammad will ask " -"you to turn it off temporarily." +#: ../system/core-workflows/how-do-they-work.rst:30 +msgid "Creation mask" msgstr "" -#: ../system/integrations/exchange.rst:38 +#: ../system/core-workflows/how-do-they-work.rst:29 msgid "" -"Please be aware that **turning off SSL verification is a security risk**. It " -"should only be used temporarily or for testing purposes. If turned off, " -"there is no verification of the certificate, which means that every " -"presented certificate will be accepted." +"If selected, your conditions and actions will affect all applicable creation " +"masks." msgstr "" -#: ../system/integrations/exchange.rst:43 -msgid "" -"After pressing Continue, Zammad will check if the configuration is okay. You " -"can then enable Exchange and start your first sync. The sync will then run " -"hourly - if you need to change mappings or the address book(s), you can " -"change the configuration at any time." +#: ../system/core-workflows/how-do-they-work.rst:34 +msgid "Edit mask" msgstr "" -#: ../system/integrations/exchange.rst:50 +#: ../system/core-workflows/how-do-they-work.rst:33 msgid "" -"After the sync has finished, you can find the new Exchange contacts under " -"\"Users\". Zammad integrates them just as normal users." +"If selected, your conditions and actions will affect all applicable edit " +"masks." msgstr "" -#: ../system/integrations/exchange.rst:55 +#: ../system/core-workflows/how-do-they-work.rst:39 msgid "" -"In some cases you might see unique IDs as \"Login\" instead of the email " -"address. This is normal and doesn't affect the login or email mapping for " -"that entry." +"Zammad differentiates between selected and saved conditions. These can be " +"combined wherever needed." msgstr "" -#: ../system/integrations/github.rst:4 -msgid "" -"Use GitHub integration to track GitHub issues directly within Zammad " -"tickets. Add issue hyperlinks and get a live summary of metadata like status " -"(open/closed), assignee, labels, and more." +#: ../system/core-workflows/how-do-they-work.rst:42 +msgid "**⚠️ Restrict workflows to specific roles if needed!**" msgstr "" -#: ../system/integrations/github.rst:8 -msgid "Please note that our GitHub integration does not support pull requests." +#: ../system/core-workflows/how-do-they-work.rst:44 +msgid "" +"By default and unless configured in conditions, workflow rules are executed " +"for **all roles**. This also affects your customers!" msgstr "" -#: ../system/integrations/github.rst:None -msgid "Integration page for GitHub" +#: ../system/core-workflows/how-do-they-work.rst:50 +msgid "Selected Conditions" msgstr "" -#: ../system/integrations/github.rst:18 +#: ../system/core-workflows/how-do-they-work.rst:48 msgid "" -"In your GitHub settings, create a new API token under **Developer settings > " -"Personal access tokens > Generate new token**. Leave the **Scopes** section " -"empty." +"These conditions are based on form values and match if an appropriate " +"selection is made (e.g. choosing another group in the ticket without " +"saving). This applies for drafts (active selection) and currently saved " +"values." msgstr "" -#: ../system/integrations/github.rst:0 ../system/integrations/gitlab.rst:0 -msgid "Screencast showing how to create a new API token" +#: ../system/core-workflows/how-do-they-work.rst:64 +msgid "Saved Conditions" msgstr "" -#: ../system/integrations/github.rst:27 -msgid "Create a new API key with no scopes/privileges." +#: ../system/core-workflows/how-do-they-work.rst:53 +msgid "" +"These conditions only match if the selected values are stored in the " +"database. It ignores the current value or selection of the field, as long as " +"the changes are not saved (e.g. performing field operations for an existing " +"ticket, which is viewed/opened by an agent)." msgstr "" -#: ../system/integrations/github.rst:29 -msgid "🔒 **Will this work for private repos?**" +#: ../system/core-workflows/how-do-they-work.rst:60 +msgid "" +"Keep in mind that the value has to be available in the situation where you " +"need it. Otherwise the condition won't match." msgstr "" -#: ../system/integrations/github.rst:31 +#: ../system/core-workflows/how-do-they-work.rst:63 msgid "" -"No. To link private repo issues, **use the** ``repo`` **scope instead**. " -"Bear in mind that the resulting token will have `lots of permissions that it " -"doesn't actually need `_, which presents a security risk if your token ever falls into " -"the wrong hands." +"Example: you can't perform any actions with *saved condition* on a ticket in " +"creation, because there are no saved values at that time." msgstr "" -#: ../system/integrations/github.rst:37 +#: ../system/core-workflows/how-do-they-work.rst:66 msgid "" -"Unfortunately, because of how GitHub's OAuth token scopes are set up, this " -"is the only way to link issues on private repos." +"You can find a description of the condition operators for core workflows :" +"doc:`here `." msgstr "" -#: ../system/integrations/github.rst:40 -msgid "Enter your new API token in Zammad and enable GitHub integration." +#: ../system/core-workflows/how-do-they-work.rst:72 +msgid "" +"Which actions should we run on the relevant fields? The possible actions " +"depend on the object type. However, usually you can at least change the " +"visibility and whether the field is mandatory." msgstr "" -#: ../system/integrations/github.rst:0 -msgid "Screencast showing how to configure Zammad's GitHub integration" +#: ../system/core-workflows/how-do-they-work.rst:76 +msgid "Be aware that actions are not available for **related** context." msgstr "" -#: ../system/integrations/github.rst:47 +#: ../system/core-workflows/how-do-they-work.rst:78 msgid "" -"Use the default API endpoint (``https://api.github.com/graphql``) unless " -"you're using GitHub Enterprise Server." +"**Example:** Let's assume you are working in the ticket context. While you " +"can have customer *conditions*, you *can't adjust* objects with actions in " +"that scope. That's because this wouldn't have any impact on the ticket " +"dialog. Of course all ticket attributes (state, owner, ...) are available." msgstr "" -#: ../system/integrations/github.rst:50 +#: ../system/core-workflows/how-do-they-work.rst:84 msgid "" -"Once completed, a new GitHub issues tab will appear in the ticket pane. 🎉" +"Please also have a look at our :doc:`limitations` to be safe from surprises." msgstr "" -#: ../system/integrations/github.rst:59 ../system/integrations/gitlab.rst:52 -msgid "Token verification is taking a long time" +#: ../system/core-workflows/how-do-they-work.rst:88 +msgid "Available Operators" msgstr "" -#: ../system/integrations/github.rst:56 ../system/integrations/gitlab.rst:49 -msgid "" -"Slight delays are normal (<2 min.), especially for systems under heavy load." +#: ../system/core-workflows/how-do-they-work.rst:90 +msgid "The availability of operators depends on the object type and scope." msgstr "" -#: ../system/integrations/github.rst:58 +#: ../system/core-workflows/how-do-they-work.rst:94 msgid "" -"Self-hosted administrators, please check your network settings to ensure " -"that your Zammad server can reach ``api.github.com``." +"Please note that actions may or may not restrict API based access to " +"attributes. We're displaying the following icons for your overview to " +"understand these limits better:" msgstr "" -#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 -msgid "I reloaded the page and now the API token is gone" +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|api| This icon indicates the action affects the API." msgstr "" -#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 -msgid "" -"This may indicate that Zammad is still verifying your API token. Try " -"reloading the page again in a couple minutes." +#: ../system/core-workflows/how-do-they-work.rst:163 +msgid "api" msgstr "" -#: ../system/integrations/gitlab.rst:2 -msgid "GitLab" +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|ui| This icon indicates the action only affects the web interface." msgstr "" -#: ../system/integrations/gitlab.rst:4 -msgid "" -"Use GitLab integration to track GitLab issues directly within Zammad " -"tickets. Add issue hyperlinks and get a live summary of metadata like status " -"(open/closed), assignee, labels, and more." +#: ../system/core-workflows/how-do-they-work.rst:167 +msgid "ui" msgstr "" -#: ../system/integrations/gitlab.rst:8 -msgid "" -"Please note that our GitLab integration does not support merge requests." +#: ../system/core-workflows/how-do-they-work.rst:102 +msgid "show |ui|" msgstr "" -#: ../system/integrations/gitlab.rst:None -msgid "Integration page for GitLab" +#: ../system/core-workflows/how-do-they-work.rst:102 +msgid "Display the chosen field. Allows setting of values." msgstr "" -#: ../system/integrations/gitlab.rst:18 -msgid "" -"In your GitLab preferences, create a new API token under **Access Tokens**." +#: ../system/core-workflows/how-do-they-work.rst:109 +msgid "hide |ui|" msgstr "" -#: ../system/integrations/gitlab.rst:20 -msgid "Under **Select scopes**, choose ``read_api`` only." +#: ../system/core-workflows/how-do-they-work.rst:105 +msgid "" +"Hide the chosen field. However, it technically still allows setting the " +"field." msgstr "" -#: ../system/integrations/gitlab.rst:27 -msgid "🔒 **If you wish to link issues on any private repos...**" +#: ../system/core-workflows/how-do-they-work.rst:108 +msgid "" +"Please note that the field is **not** gone and still contains an existing " +"value (if set)! Consider *remove* instead, if you want this field to be gone." msgstr "" -#: ../system/integrations/gitlab.rst:29 -msgid "Your API token must belong to an account with access to those repos." +#: ../system/core-workflows/how-do-they-work.rst:112 +msgid "remove |ui|" msgstr "" -#: ../system/integrations/gitlab.rst:31 -msgid "Enter your new API token in Zammad and enable GitLab integration." +#: ../system/core-workflows/how-do-they-work.rst:112 +msgid "Entirely removes the field. The field value will not be evaluated." msgstr "" -#: ../system/integrations/gitlab.rst:0 -msgid "Screencast showing how to configure Zammad's GitLab integration" +#: ../system/core-workflows/how-do-they-work.rst:115 +msgid "set mandatory |ui| |api|" msgstr "" -#: ../system/integrations/gitlab.rst:40 -msgid "" -"Use the default API endpoint (``https://gitlab.com/api/graphql``) unless " -"you're a self-hosted GitLab user." +#: ../system/core-workflows/how-do-they-work.rst:115 +msgid "Sets the field to mandatory." msgstr "" -#: ../system/integrations/gitlab.rst:43 -msgid "" -"Once completed, a new GitLab issues tab will appear in the ticket pane. 🎉" +#: ../system/core-workflows/how-do-they-work.rst:118 +msgid "set optional |ui| |api|" msgstr "" -#: ../system/integrations/gitlab.rst:51 -msgid "" -"Self-hosted administrators, please check your network settings to ensure " -"that your Zammad server can reach ``gitlab.com``." +#: ../system/core-workflows/how-do-they-work.rst:118 +msgid "Sets the field to optional." msgstr "" -#: ../system/integrations/i-doit.rst:2 -msgid "i-doit" +#: ../system/core-workflows/how-do-they-work.rst:124 +msgid "add option |ui| |api|" msgstr "" -#: ../system/integrations/i-doit.rst:4 -msgid "" -"`i-doit `_ is an open-source **configuration " -"management database** - in other words, a tool for keeping tabs on every " -"single piece of your physical and digital infrastructure, from network " -"equipment to virtual machines on down to the faceplates on your rack shelves " -"and more." +#: ../system/core-workflows/how-do-they-work.rst:121 +msgid "Allows adding options to tree selects or selects." msgstr "" -#: ../system/integrations/i-doit.rst:10 +#: ../system/core-workflows/how-do-they-work.rst:123 msgid "" -"What's that got to do with Zammad? Well, if you used tickets to track issues " -"with all that hardware, you might start wishing there was a way they could " -"talk to each other." -msgstr "" - -#: ../system/integrations/i-doit.rst:14 -msgid "Zammad gives you two:" +"You have to use the \"remove option\" before performing this action. It " +"allows you to use *existing* configured values." msgstr "" -#: ../system/integrations/i-doit.rst:17 -msgid "1. Add i-doit Links to Zammad Tickets" +#: ../system/core-workflows/how-do-they-work.rst:128 +msgid "remove option |ui| |api|" msgstr "" -#: ../system/integrations/i-doit.rst:20 ../system/integrations/i-doit.rst:80 -msgid "What Users See" +#: ../system/core-workflows/how-do-they-work.rst:127 +msgid "" +"Allows removing options from tree selects or selects. It allows you to use " +"*existing* configured values." msgstr "" -#: ../system/integrations/i-doit.rst:26 -msgid "i-doit integration in Zammad's ticket pane" +#: ../system/core-workflows/how-do-they-work.rst:134 +msgid "set fixed to |ui| |api|" msgstr "" -#: ../system/integrations/i-doit.rst:26 -msgid "" -"The i-doit integration will appear under a new 🖨 tab in the ticket pane." +#: ../system/core-workflows/how-do-they-work.rst:131 +msgid "Reduces the available options by your selection." msgstr "" -#: ../system/integrations/i-doit.rst:28 +#: ../system/core-workflows/how-do-they-work.rst:133 msgid "" -"i-doit integration puts a new tab in Zammad's ticket pane where you can add " -"links to existing i-doit devices for easy reference. (See our :user-docs:" -"`user documentation ` to learn " -"how it works in practice)." +"This reduces your workflows in terms of *add option* and *remove option*." msgstr "" -#: ../system/integrations/i-doit.rst:36 ../system/integrations/i-doit.rst:93 -msgid "How to Set it Up" +#: ../system/core-workflows/how-do-they-work.rst:137 +msgid "fill in |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:38 -msgid "" -"It requires i-doit's `API Add-on `_. Make sure to have it properly set up. Use the following setting:" +#: ../system/core-workflows/how-do-they-work.rst:137 +msgid "Allows filling in of string and integer fields with your values." msgstr "" -#: ../system/integrations/i-doit.rst:42 -msgid "Active: ``Yes``" +#: ../system/core-workflows/how-do-they-work.rst:141 +msgid "fill in empty |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:43 -msgid "Enforce authentication by username and password: ``No``" +#: ../system/core-workflows/how-do-they-work.rst:140 +msgid "" +"Allows filling in of string and integer fields with your values **if the " +"field is empty**." msgstr "" -#: ../system/integrations/i-doit.rst:45 -msgid "" -"To set it up, enable the integration in the Zammad admin panel under " -"**System > Integrations > i-doit**:" +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "select |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "i-doit settings within the integration pages" +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "Select a specific value within a select, tree select or boolean field." msgstr "" -#: ../system/integrations/i-doit.rst:53 -msgid "The root URL of your i-doit installation." +#: ../system/core-workflows/how-do-they-work.rst:153 +msgid "auto select |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:62 -msgid "API token" +#: ../system/core-workflows/how-do-they-work.rst:147 +msgid "Helps users with tree select and select fields:" msgstr "" -#: ../system/integrations/i-doit.rst:56 +#: ../system/core-workflows/how-do-they-work.rst:149 msgid "" -"Found in the i-doit admin panel under **Interfaces / external data > JSON-" -"RPC API > Common Settings**." +"If the field has only one option available for selection and no value yet, " +"the value will be automatically set." msgstr "" -#: ../system/integrations/i-doit.rst:0 -msgid "i-doit administration interface with API configuration" +#: ../system/core-workflows/how-do-they-work.rst:152 +msgid "" +"This option only works if you have one value and doesn't work if there is " +"more than one option available." msgstr "" -#: ../system/integrations/i-doit.rst:67 -msgid "Client ID" +#: ../system/core-workflows/how-do-they-work.rst:157 +msgid "set readonly |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:65 -msgid "A unique name to identify Zammad within i-doit." +#: ../system/core-workflows/how-do-they-work.rst:156 +msgid "" +"Allows you to display an attribute as read only (which means no changes are " +"possible)." msgstr "" -#: ../system/integrations/i-doit.rst:67 -msgid "(Zammad does not require you to enter a value here, but i-doit might!)" +#: ../system/core-workflows/how-do-they-work.rst:161 +msgid "unset readonly |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:70 +#: ../system/core-workflows/how-do-they-work.rst:160 msgid "" -"Here you can decide if the certificate of your i-doit system has to be " -"verified or not. In case you are using custom certificates, please have a " -"look at :doc:`how to add them to Zammad `." -msgstr "" - -#: ../system/integrations/i-doit.rst:77 -msgid "2. List / Create Zammad Tickets in i-doit" +"In case a workflow set the field in question to read only, you can undo this " +"with option above." msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "Zammad integration in i-doit's device view" +#: ../system/core-workflows/how-do-they-work.rst:172 +msgid "Stop after match" msgstr "" -#: ../system/integrations/i-doit.rst:86 +#: ../system/core-workflows/how-do-they-work.rst:174 msgid "" -"i-doit's ticket system integration gives you a way to see all the tickets " -"for a given device without ever leaving i-doit. (See our :user-docs:`user " -"documentation ` to learn how it " -"works in practice)." +"Here you can decide if other workflows are executed after the current one." msgstr "" -#: ../system/integrations/i-doit.rst:95 +#: ../system/core-workflows/how-do-they-work.rst:176 msgid "" -"Enable this integration in the i-doit admin panel under **Interfaces / " -"external data > Trouble Ticket System (TTS) > Configuration**:" +"If set to ``no`` (default), further workflows will be executed if they match " +"the condition. In this case, it is possible that your actions from the " +"current workflow can be overwritten by another workflow." msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "i-doit administration interface with TTS configuration" +#: ../system/core-workflows/how-do-they-work.rst:180 +msgid "" +"If set to ``yes``, no further worflows will be executed after the current " +"one." msgstr "" -#: ../system/integrations/i-doit.rst:104 -msgid "TTS-Type" +#: ../system/core-workflows/how-do-they-work.rst:184 +msgid "Priority" msgstr "" -#: ../system/integrations/i-doit.rst:104 -msgid "``Zammad``" +#: ../system/core-workflows/how-do-they-work.rst:186 +msgid "" +"You can define the sequence, in which the workflows are executed. The " +"default value is ``500``." msgstr "" -#: ../system/integrations/i-doit.rst:115 -msgid "Username / Password" +#: ../system/core-workflows/how-do-they-work.rst:189 +msgid "" +"The workflows are executed in ascending order by their priority. That means " +"lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." msgstr "" -#: ../system/integrations/i-doit.rst:107 -msgid "Login credentials for a Zammad agent." +#: ../system/core-workflows/learn-by-example.rst:2 +msgid "Learn by Example" msgstr "" -#: ../system/integrations/i-doit.rst:109 +#: ../system/core-workflows/learn-by-example.rst:4 msgid "" -"This agent must have **read permission** for all :doc:`groups ` that plan on using the i-doit integration." +"This page provides some basic examples for Core Workflows. Of course you can " +"build much more complex workflows if needed." msgstr "" -#: ../system/integrations/i-doit.rst:113 +#: ../system/core-workflows/learn-by-example.rst:7 msgid "" -"You may even wish to create a dedicated agent account just for this " -"integration (otherwise, if the agent ever changes her password, you will " -"have to remember to update it here)." +"To learn about Core Workflows in detail, first go to :doc:`how-do-they-work`." msgstr "" -#: ../system/integrations/i-doit.rst:117 -msgid "URL incl. protocol" +#: ../system/core-workflows/learn-by-example.rst:10 +msgid "Group Based Examples" msgstr "" -#: ../system/integrations/i-doit.rst:118 -msgid "``https://your.zammad.domain``" +#: ../system/core-workflows/learn-by-example.rst:12 +msgid "" +"All following workflows have the same base configurations. The workflow may " +"not use them all." msgstr "" -#: ../system/integrations/index.rst:2 -msgid "Integrations" +#: ../system/core-workflows/learn-by-example.rst:15 +msgid "Groups:" msgstr "" -#: ../system/integrations/index.rst:4 +#: ../system/core-workflows/learn-by-example.rst:20 +msgid "Attributes:" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:22 +msgid "Category (Single tree selection field, not mandatory, agents only)" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:23 msgid "" -"Zammad offers numerous integrations that add rich features to your instance." +"Approved (Boolean field, not mandatory, not shown, ``false`` as default)" msgstr "" -#: ../system/integrations/index.rst:6 -msgid "We're still working on this part of our documentation, stay tight!" +#: ../system/core-workflows/learn-by-example.rst:24 +msgid "Operating System (Text field, not mandatory, not shown)" msgstr "" -#: ../system/integrations/index.rst:10 -msgid "Integrations for Phone Systems" +#: ../system/core-workflows/learn-by-example.rst:25 +msgid "Software used (Single selection field, not mandatory, not shown)" msgstr "" -#: ../system/integrations/index.rst:14 -msgid "" -"Your VoIP provider or telephony system is not listed? Possibly your provider " -"supports Zammad by using the generic CTI - if you're unsure ask your " -"provider." +#: ../system/core-workflows/learn-by-example.rst:68 +msgid "Group specific values and fields" msgstr "" -#: ../system/integrations/index.rst:18 +#: ../system/core-workflows/learn-by-example.rst:28 msgid "" -"Provider does not support Zammad? Consider creating a `feature request in " -"the Zammad Community `_." +"This workflow set depends on the category field. It reduces the available " +"set of values based on the group selected." msgstr "" -#: ../system/integrations/index.rst:31 -msgid "Integrations for Authentication and Customers" +#: ../system/core-workflows/learn-by-example.rst:33 +msgid "Workflow 2nd Level group" msgstr "" -#: ../system/integrations/index.rst:44 -msgid "Integrations for Monitoring Systems" +#: ../system/core-workflows/learn-by-example.rst:35 +msgid "" +"This reduces the category options to ``2nd Level/*``, ``Internal/*`` and " +"``Others``. It also sets further required fields to mandatory and visible." msgstr "" -#: ../system/integrations/index.rst:46 -msgid "This section currently misses the following integrations:" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for 2nd level" msgstr "" -#: ../system/integrations/index.rst:48 -msgid "Icinga" +#: ../system/core-workflows/learn-by-example.rst:43 +msgid "Workflow Support group" msgstr "" -#: ../system/integrations/index.rst:49 -msgid "Monit" +#: ../system/core-workflows/learn-by-example.rst:45 +msgid "" +"This reduces the category options to ``Support/*``, ``Internal/*`` and " +"``Others``. It also sets further required fields to visible." msgstr "" -#: ../system/integrations/index.rst:50 -msgid "Nagios" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for support" msgstr "" -#: ../system/integrations/index.rst:60 -msgid "Integrations for Issue Trackers" +#: ../system/core-workflows/learn-by-example.rst:53 +msgid "Workflow Sales group" msgstr "" -#: ../system/integrations/index.rst:70 -msgid "Other Integrations" +#: ../system/core-workflows/learn-by-example.rst:55 +msgid "" +"This reduces the category options to ``Sales/*``, ``Internal/*`` and " +"``Others``." msgstr "" -#: ../system/integrations/index.rst:72 -msgid "" -"This section will hold any other integration that can't be grouped up (yet)." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for sales" msgstr "" -#: ../system/integrations/ldap/index.rst:2 -msgid "LDAP / Active Directory" +#: ../system/core-workflows/learn-by-example.rst:68 +#: ../system/integrations/slack.rst:88 +msgid "The Result" msgstr "" -#: ../system/integrations/ldap/index.rst:4 +#: ../system/core-workflows/learn-by-example.rst:63 msgid "" -"Zammad comes with a powerful LDAP integration that allows you to have a " -"single source of truth. By this you reduce the number of login credentials " -"your user has to remember." +"This is what the agent would experience with the above workflows in place." msgstr "" -#: ../system/integrations/ldap/index.rst:10 +#: ../system/core-workflows/learn-by-example.rst:0 msgid "" -"The LDAP source is also a perfect candidate for Zammad's :docs:`Kerberos " -"Single Sign-On ` but also works as addition " -"to other :doc:`/settings/security/third-party`." +"Workflow shows objects and limits options based on selections on the group" msgstr "" -#: ../system/integrations/ldap/index.rst:None -msgid "Zammands LDAP management page" +#: ../system/core-workflows/learn-by-example.rst:90 +msgid "Approval process" msgstr "" -#: ../system/integrations/ldap/index.rst:25 -msgid "📝 :doc:`manage`" +#: ../system/core-workflows/learn-by-example.rst:71 +msgid "" +"In this case ``approved`` is visible to agents by default. For this " +"workflow, an additional role ``Approval person`` is required (no further " +"permissions)." msgstr "" -#: ../system/integrations/ldap/index.rst:25 -msgid "Add, modify, remove or re-arrange your LDAP-Sources as needed." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that restricts an approval attribute to specific roles" msgstr "" -#: ../system/integrations/ldap/index.rst:30 -msgid "Before you continue, please note the following limitations." +#: ../system/core-workflows/learn-by-example.rst:81 +msgid "" +"This workflow may work best in combination with a :doc:`trigger ` but technically, this is not required." msgstr "" -#: ../system/integrations/ldap/index.rst:32 -msgid "Mapping / Synchronizing organizations is not possible" +#: ../system/core-workflows/learn-by-example.rst:84 +msgid "" +"Select fields may be a better approach because they allow more values than " +"just a simple ``true`` or ``false``." msgstr "" -#: ../system/integrations/ldap/index.rst:36 +#: ../system/core-workflows/learn-by-example.rst:0 msgid "" -"You may want to consider using domain based assignments to overcome this " -"issue. Learn more on :doc:`/manage/organizations/index`." +"Workflow fixes possible values of \"Approved ?\" to a specific selection " +"depending on the users role" msgstr "" -#: ../system/integrations/ldap/index.rst:39 +#: ../system/core-workflows/learn-by-example.rst:103 +msgid "State dependent mandatory fields" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:93 msgid "" -"Zammad's LDAP sync is one way. Editing user settings or permissions may be " -"overwritten upon the next sync depending on your configuration." +"This workflow sets ``Category`` to mandatory if the agent wants to set the " +"states ``closed`` or ``pending close`` to enforce categorization." msgstr "" -#: ../system/integrations/ldap/index.rst:41 -msgid "Nested groups are not supported." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that sets fields to mandatory on specific states" msgstr "" -#: ../system/integrations/ldap/index.rst:42 -msgid "Synchronizing user avatars from LDAP is not supported." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "" +"Workflow sets category field to mandatory upon choosing closed or pending " +"close as state" msgstr "" -#: ../system/integrations/ldap/index.rst:43 -msgid "Unlike user filters, group filters cannot be changed." +#: ../system/core-workflows/learn-by-example.rst:106 +msgid "Manual Ticket Handover Process" msgstr "" -#: ../system/integrations/ldap/index.rst:44 -msgid "" -"When a user originates from an LDAP server, Zammad will try to verify the " -"login credentials against LDAP first - if this fails Zammad will check its " -"local database." +#: ../system/core-workflows/learn-by-example.rst:108 +msgid "This example covers the handover of a ticket from one agent to another:" msgstr "" -#: ../system/integrations/ldap/index.rst:50 +#: ../system/core-workflows/learn-by-example.rst:110 msgid "" -"Users can have local passwords even if they're LDAP users! You can learn " -"more about user accounts in general on :doc:`/manage/users/index`." +"When the ticket owner is modified, a new text field (\"Handover\") shows up " +"for a comment" msgstr "" -#: ../system/integrations/ldap/index.rst:54 +#: ../system/core-workflows/learn-by-example.rst:112 msgid "" -"When several LDAP sources contain the same user (meaning the same email " -"address), the user in question will be updated with every source configured. " -"*The last LDAP source will win.*" +"This may only be visible when the owner is changed, therefore it has to be " +"hidden in general" msgstr "" -#: ../system/integrations/ldap/index.rst:58 -msgid "" -"This is subject to change with `Issue 4109 `_ in the future." +#: ../system/core-workflows/learn-by-example.rst:114 +msgid "The input in this handover text field is mandatory" msgstr "" -#: ../system/integrations/ldap/index.rst:60 +#: ../system/core-workflows/learn-by-example.rst:115 msgid "" -"Synchronization statistics currently affect *all* configured LDAP sources. " -"This also applies for newly added or updated sources." +"After submitting changes, the value of the handover field must be added as " +"an note to the ticket (via trigger)" msgstr "" -#: ../system/integrations/ldap/index.rst:63 -msgid "" -"This is subject to change with `Issue 4108 `_ in the future." +#: ../system/core-workflows/learn-by-example.rst:121 +msgid "Hiding handover field" msgstr "" -#: ../system/integrations/ldap/index.rst:65 -msgid "" -"Zammad currently has limited fallback server support. You can workaround " -"this by providing several sources - however, ensure to have the exact same " -"configuration on your fallback." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Hiding the handover field in core workflows" msgstr "" -#: ../system/integrations/ldap/index.rst:69 -msgid "" -"This is subject to improve with `Issue 4107 `_ in the future." +#: ../system/core-workflows/learn-by-example.rst:126 +msgid "Showing handover field and setting it to mandatory" msgstr "" -#: ../system/integrations/ldap/index.rst:76 -msgid "" -"This section holds all requests Zammad handled for all LDAP sources. These " -"entries can either contain synchronization information or logins " -"(authentication attempts via Zammad's login interface)." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Showing the handover field and set it as mandatory" msgstr "" -#: ../system/integrations/ldap/index.rst:80 -msgid "" -"By clicking on any request, Zammad will provide even more information. The " -"provided information can be useful when something does not work as expected." +#: ../system/core-workflows/learn-by-example.rst:131 +msgid "Trigger writing handover input to a new article" msgstr "" -#: ../system/integrations/ldap/index.rst:85 -msgid "" -"Especially a LDAP synchronization can cause many log entries. The web " -"interface will always limit the number of shown entries to the last 50 " -"entries." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Write handover content to a new article" msgstr "" -#: ../system/integrations/ldap/index.rst:None +#: ../system/core-workflows/learn-by-example.rst:133 msgid "" -"Screencast showing LDAP integration log entries and a detail view on\n" -"an entry." +"As a result, the ticket includes an article of the type note which includes " +"the predefined text and the handover comment." msgstr "" -#: ../system/integrations/ldap/manage.rst:2 -msgid "Manage LDAP-Sources" +#: ../system/core-workflows/limitations.rst:6 +msgid "Core Workflows do not replace Triggers" msgstr "" -#: ../system/integrations/ldap/manage.rst:6 +#: ../system/core-workflows/limitations.rst:5 msgid "" -"Please keep in mind all current limitations for the LDAP synchronization. " -"This will help to understand scopes of the following operations better." +"Workflows manipulate the behavior of fields. However, they do not set values " +"in fields because of actions." msgstr "" -#: ../system/integrations/ldap/manage.rst:65 -msgid "Add new source" +#: ../system/core-workflows/limitations.rst:16 +msgid "API calls are only partly affected" msgstr "" -#: ../system/integrations/ldap/manage.rst:10 +#: ../system/core-workflows/limitations.rst:9 msgid "" -"Using the *New Source* button allows you to add new LDAP sources to your " -"installation. You're not limited in the number of sources, however, keep in " -"mind that many sources will also take more time to synchronize." +"Some options affect UI only and thus do not restrict responses and calls." msgstr "" -#: ../system/integrations/ldap/manage.rst:14 -msgid "" -"You can choose between different encryption types, namely *SSL* and " -"*STARTTLS* or none of them (\"*No SSL*\"). If you choose *SSL* or " -"*STARTTLS*, Zammad will display an additional *SSL verification* option that " -"allows you to disable the verification, e.g. for self-signed SSL " -"certificates. You can also tell Zammad to use a different port by appending " -"``:`` to your hostname/IP." +#: ../system/core-workflows/limitations.rst:11 +msgid "This affects the following actions:" msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "" -"Screenshot of configuring a new LDAP source with SSL encryption and SSL " -"verification" +#: ../system/core-workflows/limitations.rst:13 +msgid "select" msgstr "" -#: ../system/integrations/ldap/manage.rst:26 -msgid "" -"New Source with SSL transport security enabled and certificate verification" +#: ../system/core-workflows/limitations.rst:14 +msgid "auto select" msgstr "" -#: ../system/integrations/ldap/manage.rst:30 -msgid "" -"Using an user filter can be a good idea if you only require a small subset " -"of your LDAP users in Zammad." +#: ../system/core-workflows/limitations.rst:15 +msgid "show" msgstr "" -#: ../system/integrations/ldap/manage.rst:42 -msgid "This especially affects inactive users" +#: ../system/core-workflows/limitations.rst:16 +msgid "hide" msgstr "" -#: ../system/integrations/ldap/manage.rst:34 -msgid "" -"As every LDAP behaves differently on which attributes and how they are set, " -"Zammad doesn't care about any flags." +#: ../system/core-workflows/limitations.rst:25 +msgid "Some fields stay unavailable to customers" msgstr "" -#: ../system/integrations/ldap/manage.rst:37 +#: ../system/core-workflows/limitations.rst:19 msgid "" -"Users that no longer are returned by your LDAP source will automatically be " -"set to inactive. Zammad assumes that the user was deactivated." +"For technical and security reasons, some default fields (the pale ones you " +"can't edit) stay unavailable for display and usage on customer permissions." msgstr "" -#: ../system/integrations/ldap/manage.rst:41 +#: ../system/core-workflows/limitations.rst:23 msgid "" -"Users will never be removed automatically! If you want to remove obsolete " -"users, use :doc:`/system/data-privacy`." +"If you require your customers to change e.g. priorities, please consider " +"using workarounds via :doc:`/system/objects` and :doc:`/manage/trigger`." msgstr "" -#: ../system/integrations/ldap/manage.rst:46 -msgid "Active Directory admins" +#: ../system/core-workflows/limitations.rst:29 +msgid "Ticket title changes not supported in edit mask" msgstr "" -#: ../system/integrations/ldap/manage.rst:45 +#: ../system/core-workflows/limitations.rst:28 msgid "" -"Active Directories are quite specific on how to filter for active users only " -"- please see the `Microsoft documentation `_ for more " -"information." +"It is currently not possible to perform changes of the ticket title in the " +"edit mask (e.g. renaming, set to read-only)." msgstr "" -#: ../system/integrations/ldap/manage.rst:51 -msgid "" -"*Do not* manually write pathes of either LDAP attributes or groups. If " -"Zammad does not display them, it either cannot find them or you have a lot " -"of users that don't have the attributes populated." +#: ../system/core-workflows/limitations.rst:37 +msgid "What is out of scope of Core Workflows?" msgstr "" -#: ../system/integrations/ldap/manage.rst:55 +#: ../system/core-workflows/limitations.rst:32 msgid "" -"Zammad will always only return attributes that are filled - this reduces the " -"returned list of attributes greatly." +"There are some things that would count as workflow but are either done via :" +"doc:`/manage/trigger` or :doc:`/manage/scheduler`." msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing how to add a new LDAP source" +#: ../system/core-workflows/limitations.rst:35 +msgid "Such as (but not limited to):" msgstr "" -#: ../system/integrations/ldap/manage.rst:63 -msgid "" -"If your LDAP system doesn't allow anonymous bind, Zammad detects it and " -"provides you an editable \"Base DN\" *text* field instead of a prefilled " -"*select* field." +#: ../system/core-workflows/limitations.rst:37 +msgid "up- or downgrade permissions of users" msgstr "" -#: ../system/integrations/ldap/manage.rst:81 -msgid "Review or edit existing source" +#: ../system/core-workflows/limitations.rst:38 +msgid "affecting article creation or listing" msgstr "" -#: ../system/integrations/ldap/manage.rst:68 +#: ../system/data-privacy.rst:2 +msgid "Data Privacy" +msgstr "" + +#: ../system/data-privacy.rst:4 msgid "" -"Clicking on a LDAP source will provide a configuration and mapping overview." +"For compliance with GDPR and other data privacy laws, you may wish to " +"**permanently delete users from the system**, along with **all of their " +"associated tickets**." msgstr "" -#: ../system/integrations/ldap/manage.rst:70 +#: ../system/data-privacy.rst:8 msgid "" -"If needed you can then use the *Change* button to update either the name, " -"active state or the whole configuration. If you're changing the whole " -"configuration, the dialogue will be identical to the source creation." +"You can create manual deletion tasks or even automated deletion tasks for " +"tickets and users based on custom conditions via :doc:`scheduler `!" msgstr "" -#: ../system/integrations/ldap/manage.rst:76 +#: ../system/data-privacy.rst:12 msgid "" -"Did your LDAP server change? Different LDAP servers have different " -"structures and default attributes. This causes the LDAP synchronization to " -"likely fail. Consider removing the affected source and re-add it." +"Access to this panel requires ``admin.data_privacy`` permissions (introduced " +"in Zammad 3.5)." msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing the update of the source name." +#: ../system/data-privacy.rst:15 +msgid "" +"On older systems that have not been updated yet, customers can also be :docs:" +"`deleted via the Zammad console `." msgstr "" -#: ../system/integrations/ldap/manage.rst:89 -msgid "Re-arrange LDAP source's order" +#: ../system/data-privacy.rst:22 +msgid "User deletion dialog in the Data Privacy panel" msgstr "" -#: ../system/integrations/ldap/manage.rst:84 +#: ../system/data-privacy.rst:22 msgid "" -"You can change the synchronization order for each source at any time. Zammad " -"will synchronize the sources from top to bottom." +"The user deletion dialog lists some of the tickets that will be removed from " +"the system along with the user." msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "" -"Screencasting showing how to change the source order by using\n" -"drag and drop." +#: ../system/data-privacy.rst:27 +msgid "Deleting Users via GUI" msgstr "" -#: ../system/integrations/ldap/manage.rst:101 -msgid "Remove a source" +#: ../system/data-privacy.rst:29 +msgid "🔥 **All deletions are FINAL!**" msgstr "" -#: ../system/integrations/ldap/manage.rst:92 -msgid "" -"If you no longer need the a LDAP source or simply want to start over, you " -"can remove them at any time. This will not remove synchronized users, data " -"synchronized or permissions." +#: ../system/data-privacy.rst:31 +msgid "Once you click “Delete”, the action cannot be canceled or undone." msgstr "" -#: ../system/integrations/ldap/manage.rst:98 +#: ../system/data-privacy.rst:33 msgid "" -"Not sure if you'd need the source later on? Set the source to inactive " -"instead of removing it - see *Review or edit existing source* for more." +"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." msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing how to remove LDAP sources." +#: ../system/data-privacy.rst:36 +msgid "**The following records cannot be deleted:**" msgstr "" -#: ../system/integrations/pgp/index.rst:2 -msgid "PGP" +#: ../system/data-privacy.rst:38 +msgid "your own account" msgstr "" -#: ../system/integrations/pgp/index.rst:7 -msgid "" -"Pretty Good Privacy (PGP) is another method for secure email communication. " -"With PGP, you can exchange **signed** and **encrypted** messages with others." +#: ../system/data-privacy.rst:39 +msgid "the system's last remaining administrator account" msgstr "" -#: ../system/integrations/pgp/index.rst:13 -#: ../system/integrations/smime/index.rst:17 -msgid "Signing" +#: ../system/data-privacy.rst:42 +msgid "Step 1: Find a User / Confirm Deletion" msgstr "" -#: ../system/integrations/pgp/index.rst:11 -msgid "is a proof that a message hasn't been manipulated on its way." +#: ../system/data-privacy.rst:44 +msgid "There are three ways to access the user deletion dialog:" msgstr "" -#: ../system/integrations/pgp/index.rst:13 -msgid "" -"In other words, it guarantees message **integrity** and **authenticity**." +#: ../system/data-privacy.rst:51 +msgid "**from the user's profile**" msgstr "" -#: ../system/integrations/pgp/index.rst:19 -#: ../system/integrations/smime/index.rst:22 -msgid "Encryption" +#: ../system/data-privacy.rst:0 +msgid "Accessing the user deletion dialog in a user profile" msgstr "" -#: ../system/integrations/pgp/index.rst:16 -#: ../system/integrations/smime/index.rst:20 -msgid "" -"scrambles a message so that it can only be unscrambled by the intended " -"recipient." +#: ../system/data-privacy.rst:51 +msgid "Click **Action > Delete**." msgstr "" -#: ../system/integrations/pgp/index.rst:19 -msgid "" -"In other words, it guarantees message **privacy** and **data security**." +#: ../system/data-privacy.rst:58 +msgid "**in the “Manage > Users” Admin Panel**" msgstr "" -#: ../system/integrations/pgp/index.rst:25 -msgid "Screenshot of ticket creation with encrypt and sign buttons" +#: ../system/data-privacy.rst:0 +msgid "Accessing the user deletion dialog under “Users” in the Admin Panel" msgstr "" -#: ../system/integrations/pgp/index.rst:25 -msgid "" -"Once PGP has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " -"appear in the ticket composer." +#: ../system/data-privacy.rst:58 +msgid "Use the **⋮ Actions** menu for the target user." msgstr "" -#: ../system/integrations/pgp/index.rst:28 -msgid "**Sign button not visible?**" +#: ../system/data-privacy.rst:66 ../system/data-privacy.rst:104 +msgid "**in the “System > Data Privacy” Admin Panel**" msgstr "" -#: ../system/integrations/pgp/index.rst:30 +#: ../system/data-privacy.rst:0 msgid "" -"Please note that the signing of emails is based on the outgoing email " -"account. That means you have to choose a group with a sender email account, " -"which has a private key assigned." +"Accessing the user deletion dialog under “Data Privacy” in the Admin Panel" msgstr "" -#: ../system/integrations/pgp/index.rst:35 -msgid "Handling of Keys" +#: ../system/data-privacy.rst:65 +msgid "" +"Use the **New Deletion Task** button. Search for users by name or email " +"address." msgstr "" -#: ../system/integrations/pgp/index.rst:36 -msgid "" -"To use the PGP function, you have to enable the integration (PGP) by " -"switching the toggle to *enabled*." +#: ../system/data-privacy.rst:79 +msgid "**Delete organizations**" msgstr "" -#: ../system/integrations/pgp/index.rst:39 +#: ../system/data-privacy.rst:69 msgid "" -"You can add keys by clicking the *add key* button. The keys can be imported " -"from a file or you can paste the content of the key in the text box." +"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:" msgstr "" -#: ../system/integrations/pgp/index.rst:42 -msgid "**Which keys do I have to import?**" +#: ../system/data-privacy.rst:0 +msgid "Deleting an organization via the user deletion dialog" msgstr "" -#: ../system/integrations/pgp/index.rst:44 +#: ../system/data-privacy.rst:78 msgid "" -"For **signing** *outgoing* emails, you have to import the private key of " -"your Zammad email account." +"If this option does not appear, make sure there are no pending deletion " +"tasks for other customers from this organization." msgstr "" -#: ../system/integrations/pgp/index.rst:47 -msgid "" -"For **encrypting** *outgoing* emails, you have to import the public key of " -"the customer's email account." +#: ../system/data-privacy.rst:82 +msgid "Step 2: Monitor Deletion Job Status" msgstr "" -#: ../system/integrations/pgp/index.rst:50 +#: ../system/data-privacy.rst:84 msgid "" -"For **verifying the signature** of signed *incoming* emails, you have to " -"import the public key of the customer." +"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:" msgstr "" -#: ../system/integrations/pgp/index.rst:53 -msgid "" -"For **decrypting** of encrypted *incoming* emails, you have to import the " -"private key of your Zammad email account." +#: ../system/data-privacy.rst:98 +msgid "**in the Activity Stream**" msgstr "" -#: ../system/integrations/pgp/index.rst:57 -msgid "Import Keys From a File" +#: ../system/data-privacy.rst:0 +msgid "Activity Stream showing data privacy tasks" msgstr "" -#: ../system/integrations/pgp/index.rst:58 -msgid "You can import keys from a file in the section **Upload key**:" +#: ../system/data-privacy.rst:94 +msgid "" +"For each deleted user, the Activity Stream will be updated twice—once when " +"the task is created, and once when it's complete." msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of adding a key via file" +#: ../system/data-privacy.rst:97 +msgid "" +"These notifications are only visible to users with ``admin.data_privacy`` " +"permissions." msgstr "" -#: ../system/integrations/pgp/index.rst:64 +#: ../system/data-privacy.rst:0 msgid "" -"**Supported file formats:** ASCII-armor as well as binary GPG format " -"(basically any GPG supported key format) is supported here." +"The task list within Data Privacy shows removals being in progress and " +"completed." msgstr "" -#: ../system/integrations/pgp/index.rst:68 -msgid "Import Keys by Pasting the Content" +#: ../system/data-privacy.rst:107 +msgid "Frequently Asked Questions" msgstr "" -#: ../system/integrations/pgp/index.rst:69 -msgid "You can also paste the key's content in the section **paste key**:" +#: ../system/data-privacy.rst:121 +msgid "What happens if I receive an email from a deleted customer?" msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of adding a key via pasting" +#: ../system/data-privacy.rst:110 +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/integrations/pgp/index.rst:75 +#: ../system/data-privacy.rst:115 msgid "" -"**Supported format:** Please note that only ASCII-armor is supported here." +"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**." msgstr "" -#: ../system/integrations/pgp/index.rst:78 -msgid "Deleting Keys" +#: ../system/data-privacy.rst:130 +msgid "What about user information stored in internal notes or other messages?" msgstr "" -#: ../system/integrations/pgp/index.rst:79 +#: ../system/data-privacy.rst:124 msgid "" -"If you want to delete a specific key, you can do it by clicking on the menu " -"in the *actions* column and select **delete**:" +"The deletion process removes **user accounts and associated tickets only**." msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of deleting a key" +#: ../system/data-privacy.rst:126 +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." msgstr "" -#: ../system/integrations/pgp/index.rst:88 -msgid "Downloading Keys" +#: ../system/data-privacy.rst:137 +msgid "I deleted an user and can still see a message they sent!" msgstr "" -#: ../system/integrations/pgp/index.rst:89 +#: ../system/data-privacy.rst:133 msgid "" -"If you want to download your keys, you can do this as well via corresponding " -"action buttons. Depending on the key, you can choose wether you want to " -"download the private or the public key." +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:95 -#: ../system/integrations/smime/manage-certificates.rst:76 -msgid "Default Behavior" +#: ../system/data-privacy.rst:141 +msgid "I removed a customer, now my reporting is off!" msgstr "" -#: ../system/integrations/pgp/index.rst:96 +#: ../system/data-privacy.rst:140 msgid "" -"Here you can adjust on per group basis, if *sign* and *encryption* is on or " -"off by default. Please be aware, that agents can always override the setting " -"for each individual article." +"When removing users and their tickets, all references are removed. This also " +"affects e.g. Reporting - these information are lost." msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Adjusting default behavior on per group basis" +#: ../system/data-privacy.rst:145 +msgid "How long does Zammad store created tasks?" msgstr "" -#: ../system/integrations/pgp/index.rst:107 +#: ../system/data-privacy.rst:144 msgid "" -"Here you can see the last actions regarding signing and encryption and if " -"they were successful." -msgstr "" - -#: ../system/integrations/pgp/index.rst:117 -msgid "**Sign button is not visible, but keys are imported.**" +"Please see the on-premise data section of the :docs:`data privacy ` chapter." msgstr "" -#: ../system/integrations/pgp/index.rst:115 -msgid "Did you choose a group in the ticket?" +#: ../system/data-privacy.rst:150 +msgid "What about re-assigned tickets? I want to delete them, too." msgstr "" -#: ../system/integrations/pgp/index.rst:116 +#: ../system/data-privacy.rst:148 msgid "" -"Did you import a private key for the email adress, which is used for " -"outgoing emails in the group?" +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:122 -msgid "**How to obtain keys?**" +#: ../system/data-privacy.rst:154 +msgid "Why are there so many deletion task entries, I didn't create them!" msgstr "" -#: ../system/integrations/pgp/index.rst:120 +#: ../system/data-privacy.rst:153 msgid "" -"You can create them yourself! There are some good tutorials on the web on " -"how to create them. Providing keys to Zammad is a prerequisite to use the " -"PGP feature." -msgstr "" - -#: ../system/integrations/pgp/index.rst:127 -msgid "**It says a passphrase is needed, but I haven't got one.**" +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:125 -msgid "" -"If the key is secured with a passphrase, you have to provide it for the " -"import in Zammad. It is possible that keys may have an empty passphrase. " -"However, this is *not* recommended." +#: ../system/integrations/checkmk/admin-panel-reference.rst:2 +msgid "Admin Panel Reference" msgstr "" -#: ../system/integrations/pgp/index.rst:132 -msgid "**How do my customers get my new key?**" +#: ../system/integrations/checkmk/admin-panel-reference.rst:None +msgid "Screenshot of Checkmk settings overview" msgstr "" -#: ../system/integrations/pgp/index.rst:130 +#: ../system/integrations/checkmk/admin-panel-reference.rst:12 msgid "" -"You have to provide your **public** key in advance. Your customer also has " -"to configure PGP in their email workflow and import your public key. The " -"other way round, you have to get the public key of your customer and have to " -"import it to Zammad." +"Which :doc:`group ` should Checkmk tickets be assigned " +"to as a default (*i.e.,* when none is specified)?" msgstr "" -#: ../system/integrations/slack.rst:2 -msgid "Slack" +#: ../system/integrations/checkmk/admin-panel-reference.rst:15 +msgid "(Applies to :ref:`API alerts ` only.)" msgstr "" -#: ../system/integrations/slack.rst:4 -msgid "**⚠️ Deprecation warning ⚠️**" +#: ../system/integrations/checkmk/admin-panel-reference.rst:21 +msgid "Auto close" msgstr "" -#: ../system/integrations/slack.rst:6 +#: ../system/integrations/checkmk/admin-panel-reference.rst:18 msgid "" -"Zammad 7 will no longer support this dedicated Slack integration. It is " -"recommended to switch to :doc:`pre-defined webhooks ` instead. Existing Slack integrations should " -"be migrated manually before this feature is dropped." +"Should Zammad automatically close tickets if a service has recovered on its " +"own?" msgstr "" -#: ../system/integrations/slack.rst:14 -msgid "" -"In order to use this feature, please add a new Slack app to your Workspace. " -"The App you need is called ``Incoming WebHooks`` ." +#: ../system/integrations/checkmk/admin-panel-reference.rst:21 +msgid "(Agents will receive notifications for such closures as appropriate.)" msgstr "" -#: ../system/integrations/slack.rst:18 -msgid "Why Do I Need This Feature?" +#: ../system/integrations/checkmk/admin-panel-reference.rst:30 +msgid "Auto-close state" msgstr "" -#: ../system/integrations/slack.rst:20 -msgid "" -"If you're already using Slack for your team communication, you'll love this " -"feature! Our Slack integration can push ticket notifications about the last " -"ticket article based on the following events:" +#: ../system/integrations/checkmk/admin-panel-reference.rst:24 +msgid "What ticket state should be applied when “auto-closing” a ticket?" msgstr "" -#: ../system/integrations/slack.rst:24 -msgid "on Ticket creation" +#: ../system/integrations/checkmk/admin-panel-reference.rst:26 +msgid "" +"You can choose from the seven built-in ticket states. If these states aren't " +"enough for you, you can :ref:`define a new ticket state ` for this purpose as well. This can be useful for tracking " +"tickets with :doc:`reports `, for example." msgstr "" -#: ../system/integrations/slack.rst:25 -msgid "on Ticket updates" +#: ../system/integrations/checkmk/admin-panel-reference.rst:35 +#: ../system/integrations/cti/includes/recent-logs.include.rst:2 +#: ../system/integrations/ldap/index.rst:74 +#: ../system/integrations/pgp/index.rst:106 +msgid "Recent Logs" msgstr "" -#: ../system/integrations/slack.rst:26 -msgid "on reached reminders" +#: ../system/integrations/checkmk/admin-panel-reference.rst:None +msgid "Screenshot of Checkmk \"Recent Logs\" section" msgstr "" -#: ../system/integrations/slack.rst:27 -msgid "a Ticket has escalated" +#: ../system/integrations/checkmk/admin-panel-reference.rst:41 +msgid "" +"If you're having trouble getting Zammad and Checkmk to play nicely together, " +"this section can help you troubleshoot." msgstr "" -#: ../system/integrations/slack.rst:28 -msgid "a Ticket is going to escalate" +#: ../system/integrations/checkmk/admin-panel-reference.rst:44 +msgid "" +"It contains a record of the fifty most recent transactions that Zammad knows " +"about, including each one's request/response details and return status." msgstr "" -#: ../system/integrations/slack.rst:30 -msgid "" -"Zammad will provide the Ticket title, a direct link to the Ticket, the event " -"type (creation, updated, escalation), the customer, time and the last " -"article that has triggered the notification." +#: ../system/integrations/checkmk/api-reference.rst:2 +msgid "API Reference" msgstr "" -#: ../system/integrations/slack.rst:34 +#: ../system/integrations/checkmk/api-reference.rst:4 msgid "" -"This will give you further options, as you can see e.g. escalating tickets " -"that are assigned to an agent that's e.g. absent. You can interact faster, " -"as you might see problems earlier (or even before the problem gets one)." +"For most users, :ref:`the sample scripts from the Setup Guide ` will do the job just fine. But if you want more fine-grained control" +"—for instance, to create high- and low-priority tickets for different types " +"of system events—then you'll have to customize the data those scripts send " +"to Zammad." msgstr "" -#: ../system/integrations/slack.rst:38 +#: ../system/integrations/checkmk/api-reference.rst:15 msgid "" -"If needed and wanted, you can even discuss directly about the topic before " -"sending an answer to the customer. Another possible use case would be a " -"agent monitoring new agents and their answers to tickets." +"This custom script will automatically set all tickets it creates to **high " +"priority** and **assign them to charlie@chrispresso.com**." msgstr "" -#: ../system/integrations/slack.rst:44 -msgid "Configure the Integration" +#: ../system/integrations/checkmk/api-reference.rst:32 +msgid "How Does it Work?" msgstr "" -#: ../system/integrations/slack.rst:46 +#: ../system/integrations/checkmk/api-reference.rst:34 msgid "" -"First of all, please go to your slack workspace - go to administration => " -"Manage Apps. If you don't have an app yet, you can simply add a new one - " -"just search for ``Incoming WebHooks`` and customize the app to your needs." +"There are two kinds of data you can pass to the API, both in the form of key-" +"value pairs:" msgstr "" -#: ../system/integrations/slack.rst:50 -msgid "" -"Choose (or create) the channel Zammad should post it's information to and " -"press on \"Add Incoming WebHooks integration\". If you're ready, copy the " -"provided WebHook URL and go to your Zammad installation." +#: ../system/integrations/checkmk/api-reference.rst:44 +msgid "Checkmk parameters" msgstr "" -#: ../system/integrations/slack.rst:56 +#: ../system/integrations/checkmk/api-reference.rst:38 msgid "" -"You need administrative rights on the Slack Workspace. The link to the app " -"directory is normally ``https://[workspace-name].slack.com/apps`` ." +"are required, and make up the **contents** of the resulting tickets/" +"articles. They also determine whether an event creates a new ticket or " +"updates/closes an existing one." msgstr "" -#: ../system/integrations/slack.rst:63 +#: ../system/integrations/checkmk/api-reference.rst:42 msgid "" -"To configure the slack integration, log in to Zammad and go to Integrations " -"(System) => Slack in the admin panel." +"These are the only values used in the sample scripts. **Use them as-is**; " +"technically, they can be customized, but it's hard to imagine a good reason " +"for it." msgstr "" -#: ../system/integrations/slack.rst:66 -msgid "" -"Here you can choose on what evens Zammad should post information about a " -"ticket to your Slack channel. Next you need to device what groups shall be " -"affected by this, as anybody with access to that specific Slack channel can " -"read at least parts of the ticket this might be a privacy issue, if you " -"select the wrong groups. The username is simply the name that Zammad uses as " -"display name inside the Slack chat. The channel defines the Slack channel " -"the information is being posted in. As last option, you can set a custom " -"icon for posting to slack." +#: ../system/integrations/checkmk/api-reference.rst:52 +msgid "Ticket attributes" msgstr "" -#: ../system/integrations/slack.rst:74 +#: ../system/integrations/checkmk/api-reference.rst:47 msgid "" -"When you're ready, just hit \"Submit\" and enable the integration. Zammad " -"will now post new ticket information based on the trigger you chose. Below " -"the options you have the recent log that shows the latest requests to Slack " -"for debugging if needed." +"are optional, and can be used to **adjust settings** on newly created " +"tickets (*e.g.,* set the owner, group, priority, or state)." msgstr "" -#: ../system/integrations/slack.rst:81 +#: ../system/integrations/checkmk/api-reference.rst:50 msgid "" -"If you leave the Icon URL empty, Zammad will use the Zammad logo instead. " -"The icon should be a square PNG file." +"If you want to customize your Checkmk alert script, do it with these. Simply " +"add an extra “form” option for each one (``-F \"key=value\"``) to your " +"script's ``curl`` command line, as in the example above." msgstr "" -#: ../system/integrations/slack.rst:90 -msgid "" -"The following figure shows how it will look if you choose to receive updates " -"on created and updated tickets. On every post Zammad sends to the Slack " -"channel, you can create new threads to discuss about the new article." +#: ../system/integrations/checkmk/api-reference.rst:54 +msgid "💡 **It's just an API endpoint!**" msgstr "" -#: ../system/integrations/slack.rst:96 +#: ../system/integrations/checkmk/api-reference.rst:56 msgid "" -"If you just want to keep track of soon escalating or already escalated " -"tickets, it will look the the following figure. Zammad changes the color in " -"front of the post so you can easily see the state of the ticket." +"When using Checkmk integration, messages need to be formatted in a certain " +"way, but that *doesn't mean the messages actually have to come from Checkmk*." msgstr "" -#: ../system/integrations/slack.rst:102 +#: ../system/integrations/checkmk/api-reference.rst:59 msgid "" -"If you change the state, Zammad will also put information on what state the " -"ticket gets and (if pending state) the date until it pends. You'll also " -"recognize the color codes in front of posts on slack, as they are exact the " -"same the ticket state colors you'll see in Zammad!" +"If you use another monitoring tool that's not officially supported by " +"Zammad, there's probably a way to make it work with your Checkmk callback " +"URL." msgstr "" -#: ../system/integrations/smime/index.rst:2 -msgid "S/MIME" +#: ../system/integrations/checkmk/api-reference.rst:63 +msgid "Checkmk Parameters" msgstr "" -#: ../system/integrations/smime/index.rst:11 +#: ../system/integrations/checkmk/api-reference.rst:65 msgid "" -"S/MIME is the most widely-supported method for secure email communication. " -"With S/MIME, you can exchange **signed** and **encrypted** messages with " -"others." +"When a notification is received, Zammad creates a new article containing the " +"details of the event that triggered it:" msgstr "" -#: ../system/integrations/smime/index.rst:15 -msgid "" -"is proof that a message hasn't been tampered with or sent by an impersonator." +#: ../system/integrations/checkmk/api-reference.rst:None +msgid "Checkmk article body" msgstr "" -#: ../system/integrations/smime/index.rst:17 +#: ../system/integrations/checkmk/api-reference.rst:72 msgid "" -"In other words, it guarantees a message's **integrity** and **authenticity**." +"These details come from the fields listed below, which correspond to " +"parameters provided by Checkmk (``$NOTIFY_*``)." msgstr "" -#: ../system/integrations/smime/index.rst:22 -msgid "In other words, it guarantees **privacy** and **data security**." +#: ../system/integrations/checkmk/api-reference.rst:75 +msgid "**Required fields are marked with an asterisk (\\*).**" msgstr "" -#: ../system/integrations/smime/index.rst:28 -msgid "Screencast demo of S/MIME features for both new tickets and replies" +#: ../system/integrations/checkmk/api-reference.rst:79 +msgid "event_id\\*" msgstr "" -#: ../system/integrations/smime/index.rst:28 +#: ../system/integrations/checkmk/api-reference.rst:78 msgid "" -"Once S/MIME has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " -"appear in the ticket composer." +"A unique ID for the system event. (``$NOTIFY_SERVICEPROBLEMID`` / " +"``$NOTIFY_HOSTPROBLEMID``)" msgstr "" -#: ../system/integrations/smime/index.rst:32 -msgid ":doc:`🔪 Prerequisites `" +#: ../system/integrations/checkmk/api-reference.rst:86 +msgid "host\\*" msgstr "" -#: ../system/integrations/smime/index.rst:31 +#: ../system/integrations/checkmk/api-reference.rst:82 msgid "" -"New to S/MIME? This section helps you to find certificate providers and " -"points out Limitations." +"The hostname of the system that the event originated from. " +"(``$NOTIFY_HOSTNAME``)" msgstr "" -#: ../system/integrations/smime/index.rst:35 -msgid ":doc:`📝 Manage Certificates `" +#: ../system/integrations/checkmk/api-reference.rst:85 +msgid "" +"Used to determine if a new event belongs to an existing ticket. Also used in " +"the subject line of the resulting article (“ is ”)." msgstr "" -#: ../system/integrations/smime/index.rst:35 -msgid "Add and download certificates; configure group default behaviors." +#: ../system/integrations/checkmk/api-reference.rst:96 +msgid "service" msgstr "" -#: ../system/integrations/smime/index.rst:38 -msgid ":doc:`😦 Troubleshooting `" +#: ../system/integrations/checkmk/api-reference.rst:89 +msgid "" +"The name of the service that the event originated from. " +"(``$NOTIFY_SERVICEDESC``)" msgstr "" -#: ../system/integrations/smime/index.rst:38 -msgid "Took a wrong turn? About recent logs and common issues." +#: ../system/integrations/checkmk/api-reference.rst:92 +msgid "Used to determine if a new event belongs to an existing ticket." msgstr "" -#: ../system/integrations/smime/index.rst:43 -msgid "" -"For more details on how S/MIME integration works on the agent side, see the :" -"user-docs:`user docs `." +#: ../system/integrations/checkmk/api-reference.rst:94 +#: ../system/integrations/checkmk/api-reference.rst:110 +msgid "Displayed as ``-`` when omitted." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:2 -msgid "Manage Certificates" +#: ../system/integrations/checkmk/api-reference.rst:104 +msgid "state\\*" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:4 +#: ../system/integrations/checkmk/api-reference.rst:99 msgid "" -"S/MIME is **disabled by default**. Enable it to start adding certificates." +"The current state of the service or host in question. " +"(``$NOTIFY_SERVICESTATE`` / ``$NOTIFY_HOSTSTATE``)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:10 -msgid "Dialogue to add new certificates or private keys" +#: ../system/integrations/checkmk/api-reference.rst:102 +msgid "" +"Used to detect when a ticket should be auto-closed (*i.e.,* on ``OK``/" +"``UP``). Also used in the subject line of the resulting article (“ is " +"”)." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:10 +#: ../system/integrations/checkmk/api-reference.rst:110 +msgid "text" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:107 msgid "" -"Manage certificates in the Admin Panel under **System > Integrations > S/" -"MIME**. Certificates may be pasted in as plain text or uploaded from a file." +"The output of the process that triggered the event. " +"(``$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:14 -msgid "Add Certificate Data" +#: ../system/integrations/checkmk/api-reference.rst:121 +msgid "" +"The Object Manager attribute panel displays built-in and custom\n" +"attribute names." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:36 -msgid "Add Certificate" +#: ../system/integrations/checkmk/api-reference.rst:121 +msgid "Find a complete list of ticket attributes in the Object Manager." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:17 +#: ../system/integrations/checkmk/api-reference.rst:123 msgid "" -"Import public-key certificates for both your own organization and your " -"contacts." +"Ticket attributes are entirely optional, and can be used to customize the " +"tickets that Checkmk creates. (Note that these attributes will be ignored if " +"a new event belongs to an existing ticket.)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:19 +#: ../system/integrations/checkmk/api-reference.rst:128 msgid "" -"You can also add a bunch of certificates in one go by providing a single " -"file with all relevant certificates." +"Why would you want to do this? Maybe you have only one IT guy, and all " +"system monitoring issues should be automatically assigned to him. Or, maybe " +"you're creating multiple notification rules so that database outages take " +"higher priority than disk space warnings." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:22 -msgid "🕵️ **ALWAYS verify certificates in-person or over the phone!**" +#: ../system/integrations/checkmk/api-reference.rst:135 +msgid "In most cases, you'll probably want to set one of the following:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:24 -msgid "" -"The whole point of signatures is to alert you when someone is trying to " -"pretend to be someone they're not. Never accept a certificate from someone " -"online without verifying it first." +#: ../system/integrations/checkmk/api-reference.rst:137 +msgid "group" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:28 -msgid "📇 **What about trusted certificate authorities?**" +#: ../system/integrations/checkmk/api-reference.rst:139 +msgid "state" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:30 -msgid "" -"In some cases (e.g. when dealing with large enterprises), you may be given a " -"certificate for an entire CA, rather than a single contact. Add it here to " -"trust *all* certificates issued by that CA." +#: ../system/integrations/checkmk/api-reference.rst:140 +msgid "priority" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:35 +#: ../system/integrations/checkmk/api-reference.rst:142 msgid "" -"Commercial CAs can usually be verified online. Zammad does not include a " -"list of built-in, trusted CAs." +"but in practice, you can set almost any attribute, including :doc:`custom " +"ones you created through the Object Manager `." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:57 -msgid "Add Private Key" +#: ../system/integrations/checkmk/api-reference.rst:145 +msgid "Please note that the following attributes are **not customizable**:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:39 -msgid "" -"Once you've added a public-key certificate, you can import its matching " -"private key." +#: ../system/integrations/checkmk/api-reference.rst:147 +msgid "title" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:42 -msgid "" -"Private keys are for **your own organization only**; never ask your contacts " -"for their private keys." +#: ../system/integrations/checkmk/api-reference.rst:148 +msgid "id" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:0 -msgid "" -"S/MIME integration showing configured certificates and possible issues with " -"Logging" +#: ../system/integrations/checkmk/api-reference.rst:149 +msgid "ticket number" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:50 -msgid "" -"A note is displayed on certificates with a matching private key (see line 2)." +#: ../system/integrations/checkmk/api-reference.rst:151 +msgid "created_by_id" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:52 -msgid "📤 **Certificates and private keys must be uploaded separately.**" +#: ../system/integrations/checkmk/api-reference.rst:152 +msgid "updated_by_id" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:54 -msgid "" -"If your certificate and private key are bundled together in the same file or " -"PEM block, import it twice (once using each button)." -msgstr "" - -#: ../system/integrations/smime/manage-certificates.rst:57 -msgid "Please note that bulk imports of private keys are not possible." +#: ../system/integrations/checkmk/api-reference.rst:155 +msgid "Which Values Can Be Set?" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:60 -msgid "Download Certificate Data" +#: ../system/integrations/checkmk/api-reference.rst:157 +msgid "😵 **Invalid values → unpredictable behavior**" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:62 +#: ../system/integrations/checkmk/api-reference.rst:159 msgid "" -"You can download the earlier provided certificates and private keys at any " -"time from your Zammad instance." +"If you provide a value that Zammad doesn't understand (*e.g.,* ``-F " +"\"priority=high\"``), it's not always clear what will happen. In some cases, " +"a ticket will be created with the default values instead - but in others, it " +"may not be created at all!" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:65 -msgid "" -"Please note that passphrase-protected private keys stay protected and when " -"you download them, you have to know the passphrase to use them after " -"downloading." +#: ../system/integrations/checkmk/api-reference.rst:164 +msgid "So what values does Zammad understand, then? Well, it depends..." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:73 -msgid "Dialogue to download certificates or private keys" +#: ../system/integrations/checkmk/api-reference.rst:168 +msgid "Use an email address or username:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:73 -msgid "Download stored certificates and their keys" +#: ../system/integrations/checkmk/api-reference.rst:190 +msgid "group & priority" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:78 -msgid "" -"The ticket composer will set all outgoing messages to **signed and " -"encrypted** by default (assuming the required certificates exist)." +#: ../system/integrations/checkmk/api-reference.rst:175 +msgid "Refer to the dropdown menus in the ticket pane:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:82 -msgid "These defaults can be modified on a per-group basis:" +#: ../system/integrations/checkmk/api-reference.rst:0 +msgid "See possible values for certain attributes in the ticket pane." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:None -msgid "Zammad allowing to choose the default behavior on per group basis" +#: ../system/integrations/checkmk/api-reference.rst:187 +msgid "🙅 **Ticket state CANNOT be set this way!**" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:89 +#: ../system/integrations/checkmk/api-reference.rst:189 msgid "" -"Of course, agents can always manually change these settings on each email " -"they send out." +"Why? Because ``-F \"state=...\"`` is already used :ref:`as a Checkmk " +"parameter `." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:4 -msgid "A certificate *and* private key for your own organization" +#: ../system/integrations/checkmk/api-reference.rst:222 +msgid "Everything Else" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:6 +#: ../system/integrations/checkmk/api-reference.rst:193 msgid "" -"(Use this to ✒️ **sign outgoing messages** and 🔓 **decrypt incoming " -"messages**.)" +"To set any other attributes, it helps to know your way around the :docs:" +"`rails console `. Valid values are those that you can " +"set with a string:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:9 -msgid "" -"Certificates belonging your contacts, or their issuing certificate authority " -"(CA)" +#: ../system/integrations/checkmk/api-reference.rst:218 +msgid "These values can then be passed directly to the API:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:11 -msgid "" -"(Use these to ✅ **verify incoming message signatures** and 🔒 **encrypt " -"outgoing messages**.)" +#: ../system/integrations/checkmk/index.rst:16 +msgid "How does it work?" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:14 -msgid "🙋 **I'm new to S/MIME. Where can I get a certificate?**" +#: ../system/integrations/checkmk/index.rst:2 +msgid "Checkmk" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:16 +#: ../system/integrations/checkmk/index.rst:4 msgid "" -"The easiest way to get certificates is to buy an annual subscription through " -"a commercial CA, such as:" +"`Checkmk `_ is a powerful IT monitoring tool that can " +"send real-time status alerts to Zammad via email or REST API. Set these " +"alerts up in Checkmk, and Zammad will automatically create, update, and " +"close tickets based on the health of your system:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:19 -msgid "" -"`Sectigo (formerly Comodo) `_" +#: ../system/integrations/checkmk/index.rst:14 +msgid "Screenshot of ticket created by Checkmk notifications" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:20 -msgid "`Secorio `_" +#: ../system/integrations/checkmk/index.rst:14 +msgid "Multiple alerts, same ticket." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:21 -msgid "`GlobalSign `_" +#: ../system/integrations/checkmk/setup-guide.rst:2 +msgid "Setup Guide" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:23 -msgid "(Zammad is not affiliated with these CAs in any way.)" +#: ../system/integrations/checkmk/setup-guide.rst:4 +msgid "" +"Whenever the Checkmk integration is enabled, Zammad listens for messages on " +"its API and over email. As long as those messages follow the required " +"format, Zammad will create new tickets (or find and update existing ones) " +"based on the message contents." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:25 +#: ../system/integrations/checkmk/setup-guide.rst:10 msgid "" -"You can also generate your own self-signed certificates, but the process is " -"complicated and usually 🙅 **involves extra work for your contacts**." +"That means that “setting up Checkmk integration” is simply a matter of " +"**adding configuration to your Checkmk site**: telling it when to send these " +"messages and what to say. To do that, you'll need to create a new " +"**notification rule** (see `Checkmk's official docs `_ for help with that)." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:29 +#: ../system/integrations/checkmk/setup-guide.rst:17 msgid "" -"Bear in mind that 🤝 **S/MIME only works if the other party is using it, too." -"**" +"As part of this new rule, you'll have to choose a **notification method** " +"(*i.e.,* a script to execute whenever the rule is triggered). This script " +"will be written by you (samples below), and contain the logic for sending " +"API/email messages to Zammad:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:32 -msgid "Certificate and Private Key Checks on Upload" +#: ../system/integrations/checkmk/setup-guide.rst:26 +msgid "Checkmk \"New Rule\" dialog" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:34 +#: ../system/integrations/checkmk/setup-guide.rst:26 msgid "" -"The certificate and public key validation is based on the ``X509v3`` " -"extensions." +"Find your custom scripts in the Checkmk WATO under **Notifications > New " +"Rule > Notification Method**." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:49 -msgid "Uploading a *client certificate*?" +#: ../system/integrations/checkmk/setup-guide.rst:29 +msgid "" +"Once you're done setting up your new rule, you're all set! New tickets " +"should start coming in and auto-updating any time your rule is triggered." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:41 -msgid "The following attributes are required then:" +#: ../system/integrations/checkmk/setup-guide.rst:33 +msgid "" +"(If you need help troubleshooting, be sure to check the :ref:`checkmk-recent-" +"logs`.)" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:39 -msgid "Subject Alternative Name (at least one email address has to be present)" +#: ../system/integrations/checkmk/setup-guide.rst:38 +msgid "API Alerts" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:40 -msgid "Key Usage (``Digital Signature`` and/or ``Key Encipherment``)" +#: ../system/integrations/checkmk/setup-guide.rst:40 +msgid "" +"To add these scripts in the Checkmk WATO, copy them into your Checkmk " +"installation directory and make them executable. (Be sure to replace the " +"``zammad.example.com`` callback URL with the one found in your admin panel.)" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:41 -msgid "Public key algorithm (either ``RSA`` or ``EC``)" +#: ../system/integrations/checkmk/setup-guide.rst:60 +msgid "Service notification" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:43 +#: ../system/integrations/checkmk/setup-guide.rst:46 msgid "" -"The Extended Key Usage attribute is optional. If the certificate provides " -"the named attribute, than it must contain the value ``E-mail Protection``." +"For updates on the status of the software running on your server (*e.g.,* " +"postgres)." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:46 -msgid "" -"Please note that any usable email adress has to be prefixed with ``email:`` " -"or ``rfc822:``." +#: ../system/integrations/checkmk/setup-guide.rst:75 +msgid "Host notification" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:49 -msgid "The named public key algorithms are mandatory for private keys as well." +#: ../system/integrations/checkmk/setup-guide.rst:63 +msgid "For updates on the status of the server itself." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:54 -msgid "Uploading a *CA certificate*?" +#: ../system/integrations/checkmk/setup-guide.rst:77 +msgid "🤔 **What's with all the env vars?**" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:52 +#: ../system/integrations/checkmk/setup-guide.rst:79 msgid "" -"In the case of an uploaded CA certificate, providing the value ``CA:TRUE`` " -"in the attribute *Basic Contstraints*, the previously mentioned attributes " -"are not verified." +"Whenever Checkmk runs these scripts, it needs to provide some information " +"about the event that triggered the notification. This information is passed " +"in the form of these ``$NOTIFY_*`` environment variables." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:56 +#: ../system/integrations/checkmk/setup-guide.rst:85 msgid "" -"In general, the usage of any expired (``Not After``) or not yet valid (``Not " -"Before``) certificate is denied for outgoing emails." +"You can specify additional parameters to pass to the script when you're " +"setting up your notification rule, but the ones you see here are all " +"provided by default." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:59 -msgid "Example certificate:" +#: ../system/integrations/checkmk/setup-guide.rst:90 +msgid "Email Alerts" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:85 +#: ../system/integrations/checkmk/setup-guide.rst:94 msgid "" -"Please note that Zammad will distrust senders by default. This means that " -"you're always required to provide certificate data, no matter if for signing " -"or encrypting." +"🐞 **There are known bugs** in Zammad's processing of email from Checkmk. " +"This section will be completed once they have been resolved. (Learn more at " +"GitHub issues `#2377 `_ & " +"`#2180 `_.)" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:89 -msgid "This is by design and can't be adjusted." +#: ../system/integrations/checkmk/setup-guide.rst:100 +msgid "In the meantime, we encourage you to set up API alerts instead." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:4 -msgid "" -"All of the system's latest S/MIME activity is displayed in the **Recent " -"Logs** section." +#: ../system/integrations/clearbit.rst:2 +msgid "Clearbit" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:11 -msgid "Sample entries of in- and outgoing S/MIME related emails." +#: ../system/integrations/clearbit.rst:4 +msgid "" +"With our Clearbit integration, you can easily enrich the information " +"provided by Zammad. If the customers or agents email address is known to " +"Clearbit, it will share all information it has regarding the user with " +"Zammad. Those information can include the following:" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:11 -msgid "" -"Logs report the status and details of all mail, both incoming and outgoing, " -"that used signing/verification or encryption/decryption." +#: ../system/integrations/clearbit.rst:9 +msgid "Avatar" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:14 -msgid "" -"This log does **not** include email sent by :doc:`triggers ` or the :doc:`scheduler `. For those, check your " -"``production.log``." +#: ../system/integrations/clearbit.rst:10 +msgid "Address information" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:20 -msgid "Common Issues" +#: ../system/integrations/clearbit.rst:11 +msgid "Website information" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:30 -msgid "I received a signed/encrypted email before I set up S/MIME integration" +#: ../system/integrations/clearbit.rst:12 +msgid "A BIO (as Note by default)" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:23 +#: ../system/integrations/clearbit.rst:14 msgid "" -"No problem. Once S/MIME has been enabled and the appropriate certificates " -"have been added, agents will be prompted to retry verification/decryption on " -"matching emails." +"If needed, you can add further custom objects and add mappings to them, so " +"the Clearbit information can be filled within the database. In general you " +"can get any information from Clearbit, as long as you have a mapping to an " +"Zammad object." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:0 -msgid "Screenshot of user prompt to retry decryption" +#: ../system/integrations/clearbit.rst:21 +msgid "" +"Clearbit does have a mapping of fields like LDAP and Exchange have, but does " +"not \"win\" against Zammad information. This means that if you have e.g. the " +"last name field filled in already and Clearbit has other information on " +"that, it will not be updated." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:38 -msgid "The 🔒 **Encrypt** button is disabled" +#: ../system/integrations/clearbit.rst:26 +msgid "" +"However: If let's say the last name has been set by Clearbit and Zammad " +"notices that the last name on the Clearbit source has changed, Zammad will " +"also update this value." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:33 -msgid "Have you added the recipient's certificate?" +#: ../system/integrations/clearbit.rst:33 +msgid "" +"The configuration of Clearbit is really easy and done fast! Just login to " +"your Clearbit-Account, go to \"API\" and copy the secret-API-Key." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:34 -msgid "Are you sure the recipient's certificate is valid?" +#: ../system/integrations/clearbit.rst:38 +msgid "" +"Now change to your Zammad instance, go to Integrations (System) -> Clearbit " +"in the admin panel. Paste your API-Key into the API-Key-Field and decide if " +"Zammad should create unknown Organizations automatically, if the user does " +"not have one yet (and Clearbit knows it). The shared option decides if the " +"new organizations Zammad creates with Clearbit should be shared ones." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:35 -msgid "Have you checked your ``production.log`` for more details?" +#: ../system/integrations/clearbit.rst:47 +msgid "" +"If you're unsure what option to choose, better stick with \"no\". You can " +"also learn more about :doc:`/manage/organizations/index`." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:37 +#: ../system/integrations/clearbit.rst:52 msgid "" -"If encryption doesn't work in the composer, it won't work in :doc:`triggers " -"` or the :doc:`scheduler ` either!" +"The Mapping option works similar to the mapping within the Exchange and LDAP " +"sync. You can add further mappings for e.g. custom fields if you need more " +"information that Clearbit can provide." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:42 -msgid "The ✅ **Sign** button is disabled" +#: ../system/integrations/clearbit.rst:58 +msgid "" +"If you want to add more Clearbit fields and want to learn more about " +"available fields on their API, you can take a look at their `API " +"documentation `_." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:41 +#: ../system/integrations/clearbit.rst:62 msgid "" -"Have you added **both the certificate and private key** for your " -"organization?" +"If you're happy with the above chosen Settings and your mapping, just save " +"the changes and enable Clearbit integration. Zammad will now start polling " +"the Clearbit API as users contact you." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:42 +#: ../system/integrations/clearbit.rst:68 msgid "" -"Does the email address on the certificate match the email address of the " -"agent/group composing the email?" +"Zammad does not synchronize with Clearbit on a regular basis, but on demand " +"if needed. This saves API calls." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:45 -msgid "Error: “Fingerprint already taken”" +#: ../system/integrations/clearbit.rst:73 +msgid "" +"Below the Settings and Mappings, you'll find our Integration log. You can " +"see what requests Zammad sent to Clearbit and also the APIs Response." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:45 -msgid "Are you sure you haven't added this certificate already?" +#: ../system/integrations/clearbit.rst:78 +msgid "" +"By the way, you can also view the API log on the Clearbit website - the " +"information seen is basically the same." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:48 -msgid "Error: “❌ invalid byte sequence in UTF-8”" +#: ../system/integrations/clearbit.rst:84 +msgid "Example When Adding a User" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:48 -msgid "Please ensure to provide PEM formatted certificate and keys." +#: ../system/integrations/clearbit.rst:86 +msgid "" +"To show you how fast information is added, we added a small Screencast " +"below. This shows the creation of the User Alex from Clearbit. As we already " +"set the last name of Alex to \"X\", Zammad did not update it. What Zammad " +"did was to add further information it received from Clearbit." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:49 -msgid "Did you check if the provided file is a valid certificate or key?" +#: ../system/integrations/cti/generic.rst:2 +msgid "CTI (generic)" msgstr "" -#: ../system/integrations/zabbix.rst:2 -msgid "Zabbix Integration" +#: ../system/integrations/cti/includes/introduction.include.rst:1 +msgid "" +"This integration enables Zammad to provide a caller log to your agents. With " +"this your agents can greet your customers by their name and are supported by " +"Zammad with automatically opening a new ticket dialog or the user profile." msgstr "" -#: ../system/integrations/zabbix.rst:5 +#: ../system/integrations/cti/includes/introduction.include.rst:6 msgid "" -"This guide describes how to integrate your Zabbix 5.4 installation with " -"Zammad using the Zabbix webhook feature. This guide will provide " -"instructions on setting up a media type, a user and an action in Zabbix." +"Click the toggle next to the heading to activate or deactivate this " +"integration." msgstr "" -#: ../system/integrations/zabbix.rst:12 -msgid "Zammad with enabled HTTP Token Authentication" +#: ../system/integrations/cti/includes/introduction.include.rst:9 +msgid "" +"If you want to learn more on how your agents can use this function, please " +"refer the :user-docs:`user documentation `." msgstr "" -#: ../system/integrations/zabbix.rst:13 -msgid "Zabbix version 5.4 or higher" +#: ../system/integrations/cti/includes/introduction.include.rst:14 +msgid "" +"Automatically opening new ticket dialogues or user profiles requires agent " +"to extension mapping - see more below." msgstr "" -#: ../system/integrations/zabbix.rst:16 -msgid "Setting up a Zammad" +#: ../system/integrations/cti/includes/introduction.include.rst:20 +msgid "Please note the following limitations to reduce confusion later on:" msgstr "" -#: ../system/integrations/zabbix.rst:18 -msgid "Enable **API Token Access** in Settings > System > API." +#: ../system/integrations/cti/includes/introduction.include.rst:22 +msgid "CTI integrations provide caller log functions only." msgstr "" -#: ../system/integrations/zabbix.rst:20 +#: ../system/integrations/cti/includes/introduction.include.rst:23 msgid "" -"Create a **new user** for a Zabbix alerter with an **email address** and " -"create a personal user token with **ticket.agent** permissions." +"This integration does not provide any VoIP functionalities; you can't make " +"phone calls from within Zammad." msgstr "" -#: ../system/integrations/zabbix.rst:24 -msgid "Zabbix Webhook Configuration" +#: ../system/integrations/cti/includes/introduction.include.rst:25 +msgid "" +"If your browser supports ``tel``-URLs, you can click on phone numbers for " +"automatic dialing. This requires additional software / configuration on your " +"agent's computers." msgstr "" -#: ../system/integrations/zabbix.rst:27 -msgid "Create a Global Macro" +#: ../system/integrations/cti/generic.rst:9 +#: ../system/integrations/cti/placetel.rst:14 +#: ../system/integrations/cti/sipgate.rst:14 +msgid "Please provide the following requirements:" msgstr "" -#: ../system/integrations/zabbix.rst:29 +#: ../system/integrations/cti/generic.rst:11 msgid "" -"Before setting up the **Webhook**, you need to setup the global macro " -"**{$ZABBIX.URL}**, which must contain the **URL** to the **Zabbix frontend**." +"A telephone system that supports webhooks (outbound) (best option are those " +"that allow customizing the calls)." msgstr "" -#: ../system/integrations/zabbix.rst:33 -msgid "" -"In the **Administration** > **Media types** section, import the `Template`_." +#: ../system/integrations/cti/generic.rst:13 +msgid "A unique Call-ID during the call session." msgstr "" -#: ../system/integrations/zabbix.rst:38 -msgid "Open the added **Zammad** media type and set:" +#: ../system/integrations/cti/generic.rst:14 +msgid "Call event data (both numbers and direction)." msgstr "" -#: ../system/integrations/zabbix.rst:40 -msgid "**zammad\\_access\\_token** to the your **Personal User Token**" +#: ../system/integrations/cti/generic.rst:15 +msgid "Your Zammad instance must be reachable for your telephony system." msgstr "" -#: ../system/integrations/zabbix.rst:41 +#: ../system/integrations/cti/generic.rst:17 msgid "" -"**zammad\\_url** to the **frontend URL** of your **Zammad** installation" +"If you want to learn more on what kind of requests are supported by Zammad " +"and what it expects, please consult our :docs:`CTI-API documentation `." msgstr "" -#: ../system/integrations/zabbix.rst:43 -msgid "**zammad\\_customer** to your **Zammad user email**." +#: ../system/integrations/cti/generic.rst:22 +#: ../system/integrations/cti/placetel.rst:27 +#: ../system/integrations/cti/sipgate.rst:30 +msgid "Available Settings" msgstr "" -#: ../system/integrations/zabbix.rst:44 -msgid "" -"**zammad\\_enable\\_tags** to **true** or **false** to enable or disable " -"trigger tags. **Important**: if you enable tag support, each tag is set with " -"a separate request." +#: ../system/integrations/cti/generic.rst:29 +#: ../system/integrations/cti/placetel.rst:41 +#: ../system/integrations/cti/sipgate.rst:40 +msgid "Endpoint Settings" msgstr "" -#: ../system/integrations/zabbix.rst:48 +#: ../system/integrations/cti/generic.rst:25 msgid "" -"If you want to prioritize issues according to **severity** values in Zabbix, " -"you can define mapping parameters:" -msgstr "" - -#: ../system/integrations/zabbix.rst:51 -msgid "**severity\\_**: Zammad priority ID" -msgstr "" - -#: ../system/integrations/zabbix.rst:53 -msgid "Click the **Update** button to save the **Webhook** settings." +"Zammad will list your generic CTI endpoint here. It contains a unique token " +"so ensure to keep this URL save." msgstr "" -#: ../system/integrations/zabbix.rst:55 +#: ../system/integrations/cti/generic.rst:28 msgid "" -"To receive notifications in **Zammad**, you need to create a **Zabbix user** " -"and add **Media** with the **Zammad** type." +"You'll need this endpoint for your PBX to talk to Zammad, see :docs:`CTI-API " +"documentation `." msgstr "" -#: ../system/integrations/zabbix.rst:58 +#: ../system/integrations/cti/includes/important-dont-forget-saving.include.rst:3 msgid "" -"For **Send to**: enter any text, as this value is not used, but is required." +"All following options **do not save automatically**. Always use the Save " +"button on the lower end of the integration page!" msgstr "" -#: ../system/integrations/zabbix.rst:61 -msgid "" -"For more information, use the `Zabbix documentation `_." +#: ../system/integrations/cti/generic.rst:43 +#: ../system/integrations/cti/placetel.rst:49 +#: ../system/integrations/cti/sipgate.rst:52 +msgid "Call Settings" msgstr "" -#: ../system/maintenance.rst:2 -msgid "Maintenance" +#: ../system/integrations/cti/generic.rst:39 +#: ../system/integrations/cti/placetel.rst:49 +#: ../system/integrations/cti/sipgate.rst:37 +#: ../system/integrations/cti/sipgate.rst:50 +msgid "Inbound" msgstr "" -#: ../system/maintenance.rst:4 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:1 msgid "" -"Zammad comes with a maintenance mode that you can use for e.g. updating the " -"instance or changing settings while restricting availability and functions." +"This option allows you to block specific incoming caller IDs. It allows you " +"to temporarily reject e.g. spam callers without having to contact providers " +"or PBX administrators." msgstr "" -#: ../system/maintenance.rst:13 -msgid "Mode" +#: ../system/integrations/cti/includes/inbound-calls.include.rst:11 +msgid "Caller ID to block" msgstr "" -#: ../system/maintenance.rst:8 -msgid "The mode setting allows you to enable or disable the maintenance mode." +#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 +msgid "Provide caller IDs to block in ``E.164`` format." msgstr "" -#: ../system/maintenance.rst:10 -msgid "Defaults to *off*." +#: ../system/integrations/cti/includes/inbound-calls.include.rst:8 +msgid "" +"Your telephony system has to support this function. Zammad will send a " +"``reject`` response which will cause your telephony system to hang up the " +"call. To callers this usually will feel like the line is busy." msgstr "" -#: ../system/maintenance.rst:12 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:14 msgid "" -"The maintenance mode will restrict access to administrative roles only. This " -"means agents and customers are logged off." -msgstr "" - -#: ../system/maintenance.rst:23 -msgid "@Login" -msgstr "" - -#: ../system/maintenance.rst:16 -msgid "" -"This setting allows you to provide a login message within a green banner " -"above the login screen. Click into the green banner in the settings page to " -"adjust your message. To activate the message, activate the *@Login* setting." -msgstr "" - -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing the default login message within the\n" -"settings page" -msgstr "" - -#: ../system/maintenance.rst:26 -msgid "" -"Send an informative message to **all active sessions**. This comes handy to " -"inform your agents e.g. about mayor outages or to force reloads after " -"configuration changes." -msgstr "" - -#: ../system/maintenance.rst:31 -msgid "This is the messages title (slightly bigger than the normal message)." -msgstr "" - -#: ../system/maintenance.rst:34 -msgid "The text you want to provide to your logged in sessions." -msgstr "" - -#: ../system/maintenance.rst:39 -msgid "Reload application" -msgstr "" - -#: ../system/maintenance.rst:37 -msgid "" -"Selecting this option will change the message acceptance button from *Close* " -"(with nothing happening) to *Continue session*, which forces the application " -"to reload." -msgstr "" - -#: ../system/maintenance.rst:43 -msgid "" -"If you have customers that are logged in to Zammad, they'll also be notified " -"if they're active in that moment." -msgstr "" - -#: ../system/maintenance.rst:48 -msgid "Example without reload application" +"Provide a meaningful note for your fellow administrators to remind yourself " +"why you've chosen to block the number." msgstr "" -#: ../system/maintenance.rst:52 -msgid "" -"Message setting within Zammad's admin settings without ticket reload " -"application setting." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:17 +#: ../system/integrations/cti/sipgate.rst:40 +msgid "Outbound" msgstr "" -#: ../system/maintenance.rst:0 +#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:1 msgid "" -"Screenshot showing the send message settings without ticket\n" -"reload application set" +"In many cases you may want to use a different caller ID depending on the " +"destination you're calling. This may apply due to specific connection rates " +"to other countries or because you want your customer to feel you're calling " +"from the same country." msgstr "" -#: ../system/maintenance.rst:61 ../system/maintenance.rst:85 -msgid "" -"The modal all other active sessions will see upon pressing *Send to clients*." +#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:6 +msgid "This option expects ``E.164`` number formats." msgstr "" -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing modal caused by maintenance's message\n" -"without reload application ticket" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 +msgid "Destination caller ID" msgstr "" -#: ../system/maintenance.rst:72 -msgid "Example with reload application" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:5 +msgid "The caller ID or number you're trying to call." msgstr "" -#: ../system/maintenance.rst:76 -msgid "" -"Message setting within Zammad's admin settings with ticket reload " -"application setting." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:7 +msgid "You can use wildcards for e.g. country specific outbound numbers like:" msgstr "" -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing the send message settings with ticket\n" -"reload application set" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:9 +msgid "``49*`` for Germany" msgstr "" -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing modal caused by maintenance's message\n" -"with reload application ticket" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:10 +msgid "``4930*`` for Berlin / Germany landlines" msgstr "" -#: ../system/monitoring.rst:2 -msgid "Monitoring" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 +msgid "``33*`` for France" msgstr "" -#: ../system/monitoring.rst:4 -msgid "" -"This function is only available in self hosted instances. If you use Zammad " -"in our cloud, we are monitoring the system on our own and take steps to fix " -"potential problems directly." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:15 +msgid "Set Outbound caller ID" msgstr "" -#: ../system/monitoring.rst:11 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:14 msgid "" -"On the monitoring page, you can see the current health state of Zammad under " -"\"*Current Status*\" at the bottom. This can be useful if you want to have a " -"look if everything is up and running. As an example, you could have a look " -"in the monitoring when you assume that some emails aren't processed from " -"Zammad." +"The outbound caller ID to set (the number your customer sees on his display) " +"in ``E.164`` number format." msgstr "" -#: ../system/monitoring.rst:17 -msgid "**Can't receive an email and the monitoring response is \"healthy\"?**" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 +msgid "Provide a short description for fellow administrators." msgstr "" -#: ../system/monitoring.rst:19 +#: ../system/integrations/cti/includes/generic-cti-support-note.includes.rst:3 msgid "" -"Zammad will just inform you about unprocessable emails. This is not the case " -"for oversized emails. You can adjust the maximum email size in :doc:`../" -"channels/email/settings`." +"This option requires your PBX to send a specific request to Zammad *before " +"dialing*. Please consult the :docs:`CTI API ` in case " +"you're not sure." msgstr "" -#: ../system/monitoring.rst:24 -msgid "Monitoring API" +#: ../system/integrations/cti/generic.rst:52 +#: ../system/integrations/cti/placetel.rst:54 +#: ../system/integrations/cti/sipgate.rst:59 +msgid "Other Settings" msgstr "" -#: ../system/monitoring.rst:26 +#: ../system/integrations/cti/includes/other-settings-intro.include.rst:1 msgid "" -"Beside the indication in the monitoring page, you can also use an external " -"monitoring tool to monitor Zammad's health. To request the health of Zammad, " -"you need to provide the API key (token) to the external monitoring tool. You " -"can copy the token from the \"*Current Token*\" field as well as the whole " -"API endpoint of your system (\"*Health Check*\" field), in which the API " -"token is already included." +"Below you can find all available additional settings for this CTI " +"integration. For your overview we're sorting them by appearance and " +"reference their description first." msgstr "" -#: ../system/monitoring.rst:37 -msgid "Screenshot showing Current Token and Health Check" +#: ../system/integrations/cti/includes/default-caller-id.include.rst:2 +#: ../system/integrations/cti/includes/default-caller-id.include.rst:1 +msgid "Default caller ID for outbound calls" msgstr "" -#: ../system/monitoring.rst:37 -msgid "Screenshot showing Token and Health Check" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:16 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:15 +msgid "Shown records in caller log" msgstr "" -#: ../system/monitoring.rst:39 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:2 msgid "" -"In addition to that, you can reset the auto-generated token to make sure " -"that already configured monitoring systems won't work anymore. So, please " -"use this \"*Reset*\" button only if you know what you do!" -msgstr "" - -#: ../system/monitoring.rst:44 -msgid "Example Output" -msgstr "" - -#: ../system/monitoring.rst:0 -msgid "No issues found" -msgstr "" - -#: ../system/monitoring.rst:48 ../system/monitoring.rst:60 -msgid "**Indicator in Zammad**:" -msgstr "" - -#: ../system/monitoring.rst:0 -msgid "Screenshot showing monitoring with no issues" -msgstr "" - -#: ../system/monitoring.rst:54 ../system/monitoring.rst:66 -msgid "**API response**::" -msgstr "" - -#: ../system/monitoring.rst:0 -msgid "Issues were found" -msgstr "" - -#: ../system/monitoring.rst:0 -msgid "Screenshot showing monitoring with issues" -msgstr "" - -#: ../system/objects.rst:2 -msgid "Objects" +"Allows you to set the number of shown caller log entries for all users. You " +"can choose from the following values:" msgstr "" -#: ../system/objects.rst:4 -msgid "" -"In Zammad you can add your own fields to tickets, users, organizations and " -"even groups (these are called \"objects\"). This can be useful if you need " -"to add further information to a ticket or any other object in Zammad and the " -"information doesn't fit in any existing field." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:5 +msgid "60 (default)" msgstr "" -#: ../system/objects.rst:11 -msgid "" -"Try to avoid deleting attributes (and disable them instead) as Zammad might " -"run into unexpected conditions if they are referenced somewhere." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:6 +msgid "120" msgstr "" -#: ../system/objects.rst:16 -msgid "" -"Here's an overview of object attributes. On the upper right you can add new " -"attributes. By default, there will be no custom fields - standard attributes " -"will be grayed out, you can't delete or change those. You can edit custom " -"attributes (they are displayed in black font and have a trash bin on the " -"right side) just by clicking on them." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:7 +msgid "180" msgstr "" -#: ../system/objects.rst:24 -msgid "" -"Attributes you add to Zammad, no matter if they have default values or not, " -"will not update existing information. This means a new ticket field " -"technically will be empty unless you populate it." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:8 +msgid "240" msgstr "" -#: ../system/objects.rst:28 -msgid "" -"Especially in ticket scope this also means that newly added attributes will " -"be indicated as \"changed\" to agents that view the ticket. This may " -"interfere with Zammad's tabs behavior." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:9 +msgid "300" msgstr "" -#: ../system/objects.rst:40 -msgid "Ordering Attributes" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:11 +msgid "**🥵 Potential performance issue**" msgstr "" -#: ../system/objects.rst:42 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:13 msgid "" -"Since Zammad introduced :doc:`/system/core-workflows` the need to have a " -"custom positioning for attributes has become more important than ever." +"Setting this setting higher than 60 may cause serious performance issues on " +"very busy instances. Keep in mind that this setting causes Zammad to poll " +"and send up to 300 records to *all active agent sessions* in very short time " +"periods." msgstr "" -#: ../system/objects.rst:45 -msgid "" -"To adjust the position of such an attribute, simply click on the attribute " -"entry in question, scroll down and adjust the position number. Please note " -"that you cannot change the positioning of default attributes." +#: ../system/integrations/cti/generic.rst:73 +msgid "Caller Log Filter" msgstr "" -#: ../system/objects.rst:49 +#: ../system/integrations/cti/generic.rst:55 msgid "" -"In case two attributes have the same position value, Zammad will sort " -"alphabetically by name automatically." +"This function allows you to provide call information based on e.g. queues " +"only to agents that really need the information." msgstr "" -#: ../system/objects.rst:None +#: ../system/integrations/cti/generic.rst:58 msgid "" -"Screenshot showing custom attribute entries ordered in between default ones" +"Why? If you have a team for several countries or departments, you don't want " +"to bug your agents from other departments. Leaving these options empty will " +"fallback to showing everything to everyone." msgstr "" -#: ../system/objects.rst:56 -msgid "Updating Database After Adding or Editing Attributes" +#: ../system/integrations/cti/generic.rst:64 +msgid "Destination caller ID or Queue" msgstr "" -#: ../system/objects.rst:58 +#: ../system/integrations/cti/generic.rst:63 msgid "" -"When adding or changing attributes, Zammad will not apply the changes " -"instantly, but instead shows you the changed attributes first. If you're " -"ready to go, just click on \"Update database\" to apply the changes to " -"Zammad. If you made a mistake or just want to discard your changes, click " -"\"Discard changes\"." +"This depends on your PBX and usually is either a queue ID, phone number or " +"extension." msgstr "" -#: ../system/objects.rst:64 -msgid "" -"After applying the changes with \"Update Database\", a restart of Zammad is " -"**mandatory**. If you don't perform it, you may experience unexpected " -"behavior or even errors. You may want to do this kind of configuration " -"during maintenance windows." +#: ../system/integrations/cti/generic.rst:69 +msgid "Agents" msgstr "" -#: ../system/objects.rst:72 +#: ../system/integrations/cti/generic.rst:67 msgid "" -"Changes on objects require you to update the database to apply these changes." +"Select the agents that are responsible for the group. These agents will then " +"see caller log entries and call notifications fitting to said queue." msgstr "" -#: ../system/objects.rst:75 -msgid "**🤓 Service restarts can be automated**" +#: ../system/integrations/cti/generic.rst:0 +msgid "" +"Screenshot showing the caller log filter table with pre filled sample data" msgstr "" -#: ../system/objects.rst:0 -msgid "Hosted environments automatically restart for you." +#: ../system/integrations/cti/includes/recent-logs.include.rst:6 +msgid "" +"With recent logs Zammad allows you to view the latest calls for the CTI " +"functionality. This usually comes in handy, when you're looking for errors." msgstr "" -#: ../system/objects.rst:0 +#: ../system/integrations/cti/includes/recent-logs.include.rst:0 msgid "" -"If you're using a self-hosted installation you can use :docs:`environment " -"variables `" +"Screenshot showing several incoming requests within Recent logs section." msgstr "" -#: ../system/objects.rst:82 -msgid "System Attributes" +#: ../system/integrations/cti/includes/recent-logs.include.rst:16 +msgid "I'm just here to clear floats up." msgstr "" -#: ../system/objects.rst:84 +#: ../system/integrations/cti/includes/recent-logs.include.rst:20 msgid "" -"Zammad comes with pre-configured attributes. Some of them can't be edited " -"via UI (or at all). This is required for proper operation of Zammad and not " -"a bug." -msgstr "" - -#: ../system/objects.rst:90 -msgid "Ticket State" +"By clicking on the entry of interest, Zammad will provide more details on " +"the call in question. You'll see the payload it received and also the " +"response that was sent." msgstr "" -#: ../system/objects.rst:92 +#: ../system/integrations/cti/includes/recent-logs.include.rst:0 msgid "" -"If the pre-configured states aren't enough for you or you want to change " -"them, you can do so by clicking on the cogwheel icon in the state row in the " -"ticket tab. But you should be careful when changing pre-configured states. " -"This can lead to unwanted behavior in some cases." +"Screenshot showing detailed information of a specific log entry of recent " +"logs" msgstr "" -#: ../system/objects.rst:None -msgid "Screenshot showing highlighted ticket state attribute" +#: ../system/integrations/cti/includes/recent-logs.include.rst:31 +msgid "x" msgstr "" -#: ../system/objects.rst:122 -msgid "Handling of states" +#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 +#: ../system/integrations/cti/includes/troubleshooting.include.rst:9 +msgid "My Phone page stays blank, signalling does work..." msgstr "" -#: ../system/objects.rst:102 +#: ../system/integrations/cti/includes/troubleshooting.include.rst:5 msgid "" -"In the state configuration screen, you can add new states, disable states or " -"change states." +"If you've made sure that signalling works (check Recent logs) and your " +"Caller Log still stays empty, please ensure that you only configured one CTI " +"integration version. Specifically defining more than one agent mapping on " +"the different integration variants will be the issue." msgstr "" -#: ../system/objects.rst:0 -msgid "Screenshot showing table of default ticket states" +#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 +msgid "Clear the not needed agent mapping and reload your browser page." msgstr "" -#: ../system/objects.rst:110 +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:1 msgid "" -"To add a new state, click on the \"New Ticket State\" button in the top " -"right corner. To change an existing state, simply click on the affected " -"state. This opens an edit dialog." +"By mapping your agents extension to their existing Zammad users, Zammad can " +"provide a new ticket dialog or open the user profile for the agent that " +"picks up the call." msgstr "" -#: ../system/objects.rst:114 +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:5 msgid "" -"You can also clone a state or set them to \"Default for new tickets\" or " -"\"Default for follow-ups\" by clicking on the ⁝ action button and select the " -"desired function." +"This speeds up ticket aiding, no matter if it's for existing tickets or new " +"ones!" msgstr "" -#: ../system/objects.rst:118 +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:8 msgid "" -"*Default for new tickets* means that this state is used for every newly " -"created ticket." +"To see it work from the agent's perspective, have a look on :user-docs:`user " +"documentation `." msgstr "" -#: ../system/objects.rst:121 -msgid "" -"*Default for follow-ups* means that this state is used if the ticket is re-" -"opened after it was closed." +#: ../system/integrations/cti/placetel.rst:2 +msgid "Placetel CTI" msgstr "" -#: ../system/objects.rst:171 -msgid "Ticket state in detail" +#: ../system/integrations/cti/placetel.rst:16 +msgid "You need an administrative Placetel account for your organization." msgstr "" -#: ../system/objects.rst:125 +#: ../system/integrations/cti/placetel.rst:17 +#: ../system/integrations/cti/sipgate.rst:20 msgid "" -"Below you can find a description for each field and option. Please head over " -"to the :ref:`example ` to see the edit dialog." +"Your Zammad instance must be allowed to communicate to external services." msgstr "" -#: ../system/objects.rst:129 -msgid "" -"This is the name of the state and what you and your agents are seeing when " -"choosing a state somewhere (e.g. in tickets, trigger configuration)." +#: ../system/integrations/cti/placetel.rst:18 +msgid "Placetel must be able to reach your Zammad instance." msgstr "" -#: ../system/objects.rst:137 -msgid "" -"There are different state types you can choose from. By default, Zammad " -"comes with one state per state type." +#: ../system/integrations/cti/placetel.rst:22 +msgid ":doc:`provider-configurations/placetel`" msgstr "" -#: ../system/objects.rst:140 +#: ../system/integrations/cti/placetel.rst:21 msgid "" -"**new**: for states for tickets that are new and it hasn't been worked on " -"them" +"Learn how to configure Placetel to enable Zammad and Placetel to communicate " +"with each other." msgstr "" -#: ../system/objects.rst:142 +#: ../system/integrations/cti/placetel.rst:32 msgid "" -"**open**: for states for tickets that are in progress and agents are working " -"on them" -msgstr "" - -#: ../system/objects.rst:144 -msgid "**merged**: for states for tickets that are merged with other tickets" +"The here listed endpoint settings are relevant for the :doc:`integration " +"configuration with Placetel `." msgstr "" -#: ../system/objects.rst:145 -msgid "" -"**pending reminder**: for states for tickets that are in progress and you " -"want to set a reminder. (default example: *pending reminder*)" +#: ../system/integrations/cti/placetel.rst:37 +#: ../system/integrations/i-doit.rst:53 +msgid "Endpoint" msgstr "" -#: ../system/objects.rst:147 +#: ../system/integrations/cti/placetel.rst:36 msgid "" -"**pending action**: for states for tickets that are waiting for a specified " -"time and then change their state (default example: *pending close*)" +"This endpoint will be required for the Zammad integration within the " +"Placetel web interface." msgstr "" -#: ../system/objects.rst:150 -msgid "" -"**closed**: for states for tickets that are finished and do not need to be " -"processed further" +#: ../system/integrations/cti/placetel.rst:41 +msgid "API Token" msgstr "" -#: ../system/objects.rst:153 +#: ../system/integrations/cti/placetel.rst:40 msgid "" -"⚠️ Choosing the correct state type is important! If you are in doubt, have a " -"look on the default states and their types!" +"You'll receive this token within the ``Web API`` menu. Make sure to copy " +"this value, it's only shown once!" msgstr "" -#: ../system/objects.rst:158 -msgid "Ignore escalation" +#: ../system/integrations/cti/placetel.rst:71 +#: ../system/integrations/cti/sipgate.rst:77 +msgid "Phone Extension to Agent Mapping" msgstr "" -#: ../system/objects.rst:157 -msgid "" -"Here you can define whether tickets of this state will count to escalation " -"time or not." +#: ../system/integrations/cti/placetel.rst:0 +msgid "Screenshot showing sample user mappings in between Placetel and Zammad" msgstr "" -#: ../system/objects.rst:161 +#: ../system/integrations/cti/placetel.rst:64 msgid "" -"You can create a note for the state to inform other admins about the state. " -"This has no effect on tickets." +"You can find your agents Placetel username combination required within ⚙️ PBX " +"→ VoIP destinations. Within the \"Advanced settings\" section you're looking " +"for \"SIP user name\" and \"SIP server\"." msgstr "" -#: ../system/objects.rst:165 -msgid "Set the state to *active* or *inactive*." +#: ../system/integrations/cti/placetel.rst:68 +msgid "Combine these two like so: ``@``." msgstr "" -#: ../system/objects.rst:167 -msgid "" -"it is technically possible to set all states to inactive. To keep Zammad " -"working in such a case, the inactive flag of one of the states is ignored." +#: ../system/integrations/cti/placetel.rst:0 +msgid "Sample VoIP credentials for a Placetel user" msgstr "" -#: ../system/objects.rst:194 -msgid "Ticket state example" +#: ../system/integrations/cti/provider-configurations/placetel.rst:2 +msgid "Setup Placetel connection for Zammad" msgstr "" -#: ../system/objects.rst:174 +#: ../system/integrations/cti/provider-configurations/placetel.rst:6 msgid "" -"Let's assume we want to create a new state which indicates that the ticket " -"has to wait for a response of a third party (e.g. service contractor or " -"manufacturer) and we want to to be able to set a reminder." +"This configuration step requires a *full* administrative Placetel account. " +"You may receive forbidden error messages with Placetel in case your " +"permissions are not high enough." msgstr "" -#: ../system/objects.rst:178 +#: ../system/integrations/cti/provider-configurations/placetel.rst:10 msgid "" -"First we give the new state a proper name. In this example we call it " -"\"waiting for manufacturer\"." +"The following actions can be configured via the `Placetel web interface " +"`_." msgstr "" -#: ../system/objects.rst:181 -msgid "" -"As state type we choose \"pending reminder\". This indicates that the ticket " -"is still open and we can set a reminder. This reminder can be useful if our " -"manufacturer sometimes isn't responding or we want to remind him to give us " -"an answer." +#: ../system/integrations/cti/provider-configurations/placetel.rst:29 +msgid "Step 1: Activate Zammad integration" msgstr "" -#: ../system/objects.rst:186 +#: ../system/integrations/cti/provider-configurations/placetel.rst:14 msgid "" -"We choose \"no\" for \"ignore escalation\" because we want to escalate the " -"tickets even if we are waiting on the manufacturer's feedback." -msgstr "" - -#: ../system/objects.rst:189 -msgid "The **result** in the creation dialog will look like this:" +"Within Integrations, scroll down to Partner integrations and select Zammad." msgstr "" -#: ../system/objects.rst:0 -msgid "Screenshot showing ticket state creation dialog with example" +#: ../system/integrations/cti/provider-configurations/placetel.rst:17 +msgid "" +"You can alternatively filter by \"Ticket Systems\" to reduce the number of " +"entries on the page. You'll still want to look for Partner integrations. 🤓" msgstr "" -#: ../system/objects.rst:197 ../system/objects.rst:199 -msgid "Ticket Priority" +#: ../system/integrations/cti/provider-configurations/placetel.rst:21 +msgid "" +"Within the Zammad integration now press \"Activate\". A new tab ``API`` " +"becomes available - open this tab." msgstr "" -#: ../system/objects.rst:199 ../system/objects.rst:201 +#: ../system/integrations/cti/provider-configurations/placetel.rst:24 msgid "" -"If the pre-configured priorities aren't enough for you or you want to change " -"them, you can do so by clicking on the cogwheel icon in the priority row in " -"the ticket tab:" +"Now tick \"Enable Call Control / Notify API\" and paste the Placetel " +"endpoint from your Zammad instance into the field \"URL of your API " +"endpoint\". Save to apply the settings" msgstr "" -#: ../system/objects.rst:None -msgid "Screenshot showing highlighted ticket priority attribute" +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "Screencast showing how to activate the Zammad integration" msgstr "" -#: ../system/objects.rst:224 ../system/objects.rst:226 -msgid "Handling of priorities" +#: ../system/integrations/cti/provider-configurations/placetel.rst:51 +msgid "Step 2: Generate API Token for Placetel" msgstr "" -#: ../system/objects.rst:208 ../system/objects.rst:210 +#: ../system/integrations/cti/provider-configurations/placetel.rst:32 msgid "" -"In the priority configuration screen, you can add new priorities, disable " -"priorities or change priorities." +"Go back to the integrations page and scroll down to \"Web API\". Generate a " +"new API token by using the \"Create a new API token\" button." msgstr "" -#: ../system/objects.rst:0 -msgid "Screenshot showing table of default ticket priorities" +#: ../system/integrations/cti/provider-configurations/placetel.rst:37 +msgid "" +"If you already generated a token either use your existing token or reset it " +"by using above mentioned button. Placetel will ask you to conform this reset." msgstr "" -#: ../system/objects.rst:216 ../system/objects.rst:218 +#: ../system/integrations/cti/provider-configurations/placetel.rst:41 msgid "" -"To add a new priority, click on the \"New Priority\" button in the top right " -"corner. To change an existing priority, simply click on the affected " -"priority. This opens an edit dialog." +"Please keep in mind that existing API scripts may no longer work due to " +"token resets!" msgstr "" -#: ../system/objects.rst:220 ../system/objects.rst:222 +#: ../system/integrations/cti/provider-configurations/placetel.rst:44 msgid "" -"You can also clone a priority or set them to \"Default for new tickets\" by " -"clicking on the ⁝ action button and select the desired function." +"Copy the provided API token and insert it into the \"API Token\" field " +"within Zammad's Placetel integration." msgstr "" -#: ../system/objects.rst:223 ../system/objects.rst:225 +#: ../system/integrations/cti/provider-configurations/placetel.rst:47 msgid "" -"*Default for new tickets* means that this priority is used for every newly " -"created ticket." +"Apply your changes by using the \"Save\" button on the bottom of the " +"Placetel integration page and activate the Placetel integration." msgstr "" -#: ../system/objects.rst:246 ../system/objects.rst:248 -msgid "Priorities in detail" +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "" +"Screencast showing how to retrieve an API token from Placetel for Zammad" msgstr "" -#: ../system/objects.rst:227 ../system/objects.rst:229 -msgid "Below you can find a description for each field and option." +#: ../system/integrations/cti/provider-configurations/placetel.rst:73 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:77 +msgid "Step 3: Restrict the numbers to notify on" msgstr "" -#: ../system/objects.rst:230 ../system/objects.rst:232 +#: ../system/integrations/cti/provider-configurations/placetel.rst:54 msgid "" -"This is the name of the priority and what you and your agents are seeing " -"when choosing a priority somewhere (e.g. in tickets, trigger configuration)." +"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " +"the the Integrations page of the Placetel web interface, go to \"Notify " +"API\"." msgstr "" -#: ../system/objects.rst:240 ../system/objects.rst:242 -msgid "Highlight color" +#: ../system/integrations/cti/provider-configurations/placetel.rst:58 +msgid "" +"Lower on the page Placetel allows you to restrict the numbers to notify on. " +"You'll find this within the \"External routing API\" part." msgstr "" -#: ../system/objects.rst:235 ../system/objects.rst:237 +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 msgid "" -"Switch between *Low priority* (light blue), *High priority* (red) and - " -"(default). This affects the displayed color for ticket titles in overviews." +"Screenshot showing a sample selection of phone numbers to use for the " +"Placetels notify API" msgstr "" -#: ../system/objects.rst:239 ../system/objects.rst:241 -msgid "The color options are currently limited to the mentioned options." +#: ../system/integrations/cti/provider-configurations/placetel.rst:66 +msgid "" +"This menu point also provides a API request log from Placetel view. Just " +"open \"Recent responses of your API endpoint\" to learn more." msgstr "" -#: ../system/objects.rst:243 ../system/objects.rst:245 +#: ../system/integrations/cti/provider-configurations/placetel.rst:69 msgid "" -"You can create a note for the priority to inform other admins about the " -"priority. This has no effect on tickets." +"If you want to see Zammad's perspective, use the \"Recent Logs\" part from " +"within the Placetel integration page." msgstr "" -#: ../system/objects.rst:247 ../system/objects.rst:249 -msgid "Set the priority to *active* or *inactive*." +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "Screenshot showing sample log entries for Placetels API calls to Zammad" msgstr "" -#: ../system/objects/external-data-source-example.rst:2 -msgid "External Data Source" +#: ../system/integrations/cti/provider-configurations/placetel.rst:77 +msgid "Step 4 (optional): Further configurations for Placetel" msgstr "" -#: ../system/objects/external-data-source-example.rst:4 +#: ../system/integrations/cti/provider-configurations/placetel.rst:76 msgid "" -"We assume you already had a look on :doc:`types` where you can find a " -"description of the individual fields." +"If needed, you can now configure Zammad's Placetel integration in more " +"detail. You can learn more about your options here: :ref:`Placetel " +"integration settings `." msgstr "" -#: ../system/objects/external-data-source-example.rst:7 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:2 +msgid "Setup Sipgate connection for Zammad" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"To reproduce this example, choose a category you want to add a custom field, " -"click on *New Attribute* and select *External data source field* under " -"*Format*." +"Sipgate has no english web interface which is why this documentation page is " +"mixing up languages badly." msgstr "" -#: ../system/objects/external-data-source-example.rst:11 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"Our example story is to fetch data from an external product database. We " -"want to add our products to the tickets so that the products can be searched " -"and chosen from a list and also create a link to the product website." +"Please also note that the availability of API addons highly depends on your " +"package trier. Usage of sipgate.io packages *is not free*, please check " +"their `pricing page `_ before!" msgstr "" -#: ../system/objects/external-data-source-example.rst:16 -msgid "Base configuration" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:35 +msgid "Step 1: Book sipgate.io package" msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Initial steps to configure external data source object type" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:13 +msgid "Skip to step 2 if you already have the package booked!" msgstr "" -#: ../system/objects/external-data-source-example.rst:23 -#: ../system/variables.rst:85 -msgid "**Example:**" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:15 +msgid "" +"Login to an administrative Sipgate account and navigate to " +"``Accountverwaltung``. You'll see several different options depending on " +"your booked packages. Select ``Verträge & Produkte`` to continue." msgstr "" -#: ../system/objects/external-data-source-example.rst:25 -msgid "Name: *product*" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:19 +msgid "" +"Scroll down to the section ``Zusätzliche Produkte buchen`` and look for " +"``sipgate.io`` - select this product by using the ``Produkte anzeigen``-" +"Button." msgstr "" -#: ../system/objects/external-data-source-example.rst:26 -msgid "Display: *Product*" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:23 +msgid "" +"On the next page select either one of the ``sipgate.io`` packages or ``Push-" +"API Package Free``. Follow the dialogue by booking the addon. You'll be " +"returned to your contract overview and now should see the selected addon in " +"your list." msgstr "" -#: ../system/objects/external-data-source-example.rst:29 -msgid "External data source configuration" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:30 +msgid "" +"The availability for ``sipgate.io`` packages and their levels highly depends " +"on the overall account type and product you've booked with Sipgate." msgstr "" -#: ../system/objects/external-data-source-example.rst:31 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"First, enter the search URL making sure it contains ``#{search.term}`` as a " -"parameter:" +"Screencast showing the process on how to book the required sipgate.io addon" msgstr "" -#: ../system/objects/external-data-source-example.rst:34 -msgid "**Example:** ``https://dummyjson.com/products/search?q=#{search.term}``" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:52 +msgid "Step 2: Configure webhook for Zammad" msgstr "" -#: ../system/objects/external-data-source-example.rst:36 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:38 msgid "" -"After that, head down to the preview section and enter a search input for " -"the external data source." +"Within your ``Accountverwaltung`` navicate to your product ``sipgate.io``. " +"In the newly opened tab, switch from \"Clients\" to \"Webhooks\" and paste " +"the endpoint URLs from your Zammad instance like so:" msgstr "" -#: ../system/objects/external-data-source-example.rst:39 -msgid "**Example:** ``mac``" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:42 +msgid "Inbound endpoint to \"Incoming\"" msgstr "" -#: ../system/objects/external-data-source-example.rst:41 -msgid "Then you can find a preview of the response data below:" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:43 +msgid "Outbound endpoint to \"Outgoing\"" msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of JSON response based on search term" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:47 +msgid "" +"Ensure to select at least one call group or phoneline within \"Sources\". " +"Other wise Sipgate will not indicate any incoming or outgoing calls to " +"Zammad." msgstr "" -#: ../system/objects/external-data-source-example.rst:48 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"We recommend using the preview to have a look on the structure. There is a " -"top-level element called ``products``. One level below, you can find the " -"attributes ``id`` and ``title``." +"Screencast showing how to add Zammad's endpoint URLs to sipgate.ios webhook " +"configuration" msgstr "" -#: ../system/objects/external-data-source-example.rst:52 -msgid "**Search result response based on search from example:**" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:55 +msgid "" +"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " +"the Webhooks → URLs section of Sipgate you can select which *sources* " +"Sipgate should notify Zammad about in- and outgoing calls." msgstr "" -#: ../system/objects/external-data-source-example.rst:119 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:59 msgid "" -"To tell the remote system that the desired data is located below the " -"``products`` level, you have to put it in the field *Search result list key*." +"Use either specific phone lines or use the option \"Use for all phonelines " +"and groups\" to notify Zammad about all existing lines of your Sipgate " +"account." msgstr "" -#: ../system/objects/external-data-source-example.rst:122 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"After inserting ``products`` in the mentioned field, you get an extended " -"preview. You can find an additional box *Search result list* with a JSON " -"structure. This is the same response as before but stripped from the upper " -"``products`` element by the external data source." +"Screenshot showing a sample selection of phone numbers to use for the " +"Sipgates webhooks API" msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of JSON response search result list" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:68 +msgid "This section also allows you to enable a Debug log." msgstr "" -#: ../system/objects/external-data-source-example.rst:132 -msgid "" -"Now you need to provide the keys for the search result values and labels. As " -"already mentioned, we are looking for the ``id`` and the ``title`` of our " -"products. If you haven't already, it is now a good time to look at the " -"preview of the *Search result list*." +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "Screenshot showing an enabled Debug log option" msgstr "" -#: ../system/objects/external-data-source-example.rst:197 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:73 msgid "" -"After locating our two keys, we insert them in *search result value key* " -"(``id``) and in *Search result label key* (``title``)." +"After enabling you can use the Debug log section to see all sent webhook " +"calls to Zammad. You'll also can see the response." msgstr "" -#: ../system/objects/external-data-source-example.rst:200 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"Basically, we configured the external data source already and we can see a " -"table in the preview section:" -msgstr "" - -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of product table based on search term" +"Screenshot showing sample log entries for Sipgates webhook calls to Zammad" msgstr "" -#: ../system/objects/external-data-source-example.rst:208 -msgid "" -"According to our example story, now just the *Link template* is missing." +#: ../system/integrations/cti/provider-configurations/sipgate.rst:81 +msgid "Step 4 (optional): Further configurations for Sipgate" msgstr "" -#: ../system/objects/external-data-source-example.rst:210 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:80 msgid "" -"Please note that this is an optional feature. If you don't want to use such " -"links, of course you don't have to configure it." +"If needed, you can now configure Zammad's Sipgate integration in more " +"detail. You can learn more about your options here: :ref:`Sipgate " +"integration settings `." msgstr "" -#: ../system/objects/external-data-source-example.rst:213 -msgid "" -"We can add now an address where additional product information can be found." +#: ../system/integrations/cti/sipgate.rst:2 +msgid "Sipgate (sipgate.io)" msgstr "" -#: ../system/objects/external-data-source-example.rst:215 -msgid "Example: ``https://your_domain.com/q=#{ticket.product}``" +#: ../system/integrations/cti/sipgate.rst:16 +msgid "You need an administrative Sipgate account for your organization." msgstr "" -#: ../system/objects/external-data-source-example.rst:217 -msgid "In the example, the parameter means:" +#: ../system/integrations/cti/sipgate.rst:17 +msgid "" +"Zammad requires a ``sipgate.io`` addon from the feature store (please note " +"that API calls are not free with Sipgate. Rates may apply and differ from " +"account to account)." msgstr "" -#: ../system/objects/external-data-source-example.rst:219 -msgid "``#{}``: \"Frame\" for the insertion of information" +#: ../system/integrations/cti/sipgate.rst:21 +msgid "Sipgate must be able to reach your Zammad instance." msgstr "" -#: ../system/objects/external-data-source-example.rst:220 -msgid "``ticket``: object level, where you create your custom object" +#: ../system/integrations/cti/sipgate.rst:25 +msgid ":doc:`provider-configurations/sipgate`" msgstr "" -#: ../system/objects/external-data-source-example.rst:221 -msgid "``product``: name of the (custom) object" +#: ../system/integrations/cti/sipgate.rst:24 +msgid "" +"Learn how to configure Sipgate to enable Zammad and Sipgate to communicate " +"with each other." msgstr "" -#: ../system/objects/external-data-source-example.rst:223 +#: ../system/integrations/cti/sipgate.rst:33 msgid "" -"After configuring your *Link template*, there will be another column in the " -"preview. Hovering on the icons in the *Link* column will show you where it " -"forwards you." +"Below endpoint settings affect the :doc:`sipgate.io configuration `." msgstr "" -#: ../system/objects/external-data-source-example.rst:232 -msgid "" -"In our example, one of the links looks like: https://your_domain.com/q=6, " -"where the 6 is the product id." +#: ../system/integrations/cti/sipgate.rst:37 +msgid "This endpoint is required for incoming call hooks." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:40 +msgid "This endpoint is required for outgoing call hooks." msgstr "" -#: ../system/objects/external-data-source-example.rst:235 -msgid "You can find more information regarding the URL in :doc:`types`." +#: ../system/integrations/cti/sipgate.rst:0 +msgid "Screenshot showing sample user mappings in between Sipgate and Zammad" msgstr "" -#: ../system/objects/includes/adding-values-hint.include.rst:3 +#: ../system/integrations/cti/sipgate.rst:69 msgid "" -"Adding values can be tricky for first timers, don't forget to press \"➕ " -"Add\" after typing your values. Otherwise you may loose a value." +"You can find your agent's Sipgate username within ``Accountverwaltung → " +"Benutzer``. You're looking for the SIP-ID." msgstr "" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:1 -#: ../system/objects/includes/reposition-values.include.rst:1 -msgid "**↕️ This field type allows the positioning of its values ↔️**" +#: ../system/integrations/cti/sipgate.rst:0 +msgid "Sample VoIP credentials for a Sipgate user" msgstr "" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:3 -msgid "" -"In order to re-arrange the field values, first edit the field. Then you can " -"use ☰ to drag the values in question to the correct position. If you want to " -"change the layer depth, double click on ☰. With it you can cycle through the " -"available layers." +#: ../system/integrations/cti/sipgate.rst:77 +msgid "Users with several devices also have several SIP-IDs." msgstr "" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:8 -msgid "When you're ready, submit your changes to save the object attribute." +#: ../system/integrations/elasticsearch.rst:2 +msgid "Elasticsearch (SaaS)" msgstr "" -#: :0 ../system/objects/types.rst:0 +#: ../system/integrations/elasticsearch.rst:4 msgid "" -"Screencast showing how to re-position values on tree select like\n" -"fields" +"The Elasticsearch integration allows you to create a read-only user to use " +"with your favorite reporting tool (e.g. like Grafana)." msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:3 +#: ../system/integrations/elasticsearch.rst:7 msgid "" -"In order to re-arrange the field values, edit the field and scroll below the " -"values. Make sure to tick the option \"Use custom option sort\"." +"If you want to take full advantage of the Zammad reporting, have a look at " +"our :docs:`Grafana ` " +"setup page as well." msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:8 -msgid "" -"If you do not tick this field, all manual positioning you did above will be " -"lost upon saving! ☠️" +#: ../system/integrations/elasticsearch.rst:11 ../system/subscription.rst:7 +msgid "**🚧 Hosted environment specific 🚧**" msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:11 +#: ../system/integrations/elasticsearch.rst:13 msgid "" -"Now use ☰ to drag the values in question to the correct position. When " -"you're ready, submit your changes to save the object attribute." -msgstr "" - -#: :0 ../system/objects/types.rst:0 -msgid "Screencast showing how to re-position values" +"This integration is only available for Hosted setups. In order to use " +"Elasticsearch you'll need the **Plus** subscription." msgstr "" -#: ../system/objects/includes/url-template-hint.include.rst:3 +#: ../system/integrations/elasticsearch.rst:16 msgid "" -"This field allows using :ref:`URL fields (Link Templates) `." +"Self hosted users have all the control over their self hosted Elasticsearch " +"instances." msgstr "" -#: ../system/objects/permissions.rst:2 -msgid "Attribute Permissions" +#: ../system/integrations/elasticsearch.rst:None +msgid "Elasticsearch integration page on SaaS environments" msgstr "" -#: ../system/objects/permissions.rst:7 +#: ../system/integrations/elasticsearch.rst:27 msgid "" -"In the object attributes configuration you can define if a field is shown " -"and if the input in the field is mandatory, separated by different screens " -"and for different :doc:`roles/permissions `." +"Please note the following limitations of Elasticsearch access on hosted " +"environments:" msgstr "" -#: ../system/objects/permissions.rst:17 -msgid "Screenshot shows object attribute permission table" +#: ../system/integrations/elasticsearch.rst:30 +msgid "access to the Elasticsearch index is read-only access" msgstr "" -#: ../system/objects/permissions.rst:17 -msgid "" -"Some of the possible permissions and screen options for a user object " -"attribute." +#: ../system/integrations/elasticsearch.rst:31 +msgid "currently you're limited to user only" msgstr "" -#: ../system/objects/permissions.rst:19 +#: ../system/integrations/elasticsearch.rst:32 msgid "" -"Based on the object context (ticket, agent, organization, user), the " -"selectable roles (to be precise: the required permissions) and screens " -"differ. Be aware that these settings aren't affecting data creation via " -"other channels than the UI." +"Reporting tools that require to write into the indexes (like Kibana) are not " +"supported" msgstr "" -#: ../system/objects/permissions.rst:24 -msgid "" -"If you want to have further customization possibilities, you should have a " -"look at the :doc:`core workflows `." +#: ../system/integrations/elasticsearch.rst:34 +msgid "IP access restriction is currently not yet supported" msgstr "" -#: ../system/objects/permissions.rst:28 -msgid "Screens" +#: ../system/integrations/elasticsearch.rst:37 +msgid "Activating Elasticsearch Access" msgstr "" -#: ../system/objects/permissions.rst:30 +#: ../system/integrations/elasticsearch.rst:39 msgid "" -"In the table below you can find an overview about the different permissions " -"and the available screens Zammad distinguishes between." -msgstr "" - -#: ../system/objects/permissions.rst:37 -msgid "Screen" +"By default external access to your Elasticsearch index is not active. You " +"can enable the integration at any time if needed." msgstr "" -#: ../system/objects/permissions.rst:38 -msgid "Available for" +#: ../system/integrations/elasticsearch.rst:42 +msgid "" +"Please ensure to note down the password provided - you won't have access to " +"it afterwards." msgstr "" -#: ../system/objects/permissions.rst:40 -msgid "create" +#: ../system/integrations/elasticsearch.rst:None +msgid "Screencast showing activation of Elasticsearch integration" msgstr "" -#: ../system/objects/permissions.rst:41 ../system/objects/permissions.rst:52 -#: ../system/objects/permissions.rst:59 ../system/objects/permissions.rst:73 -msgid "admin.user" +#: ../system/integrations/elasticsearch.rst:51 +msgid "Connection Settings" msgstr "" -#: ../system/objects/permissions.rst:42 ../system/objects/permissions.rst:53 -#: ../system/objects/permissions.rst:60 -msgid "admin.organization" +#: ../system/integrations/elasticsearch.rst:53 +msgid "" +"This section holds the most important general information for accessing your " +"Elasticsearch indexes - such as:" msgstr "" -#: ../system/objects/permissions.rst:43 ../system/objects/permissions.rst:54 -#: ../system/objects/permissions.rst:61 -msgid "admin.group" +#: ../system/integrations/elasticsearch.rst:57 +msgid "A unique subdomain that does not tell your real instance URL." msgstr "" -#: ../system/objects/permissions.rst:44 -msgid "Creation dialog for not yet existing data" +#: ../system/integrations/elasticsearch.rst:61 +msgid "Software" msgstr "" -#: ../system/objects/permissions.rst:45 -msgid "create_middle" +#: ../system/integrations/elasticsearch.rst:60 +msgid "" +"The major version of the search index being used. This is required by some " +"Reporting tools like Grafana." msgstr "" -#: ../system/objects/permissions.rst:46 ../system/objects/permissions.rst:50 -#: ../system/objects/permissions.rst:57 ../system/objects/permissions.rst:66 -#: ../system/objects/permissions.rst:70 -msgid "ticket.customer" +#: ../system/integrations/elasticsearch.rst:64 +msgid "Authentication" msgstr "" -#: ../system/objects/permissions.rst:47 ../system/objects/permissions.rst:51 -#: ../system/objects/permissions.rst:58 ../system/objects/permissions.rst:69 -msgid "ticket.agent" +#: ../system/integrations/elasticsearch.rst:64 +msgid "The authentication type being supported. ``Basic Authentication``" msgstr "" -#: ../system/objects/permissions.rst:48 -msgid "Ticket create dialog (middle section)" +#: ../system/integrations/elasticsearch.rst:67 +msgid "Available Indexes" msgstr "" -#: ../system/objects/permissions.rst:49 -msgid "edit" +#: ../system/integrations/elasticsearch.rst:69 +msgid "" +"Within this section we're displaying the -in our opinion- most important " +"indexes for a Zammad instance." msgstr "" -#: ../system/objects/permissions.rst:55 -msgid "Editing dialog for already existing data" +#: ../system/integrations/elasticsearch.rst:72 +msgid "" +"If you require all indexes or our listing is not good enough for you, point " +"your browser to the URL we're providing and append ``/_aliases?" +"pretty=true``. The result should look like this: ``https://.zammad.com/" +"_aliases?pretty=true``." msgstr "" -#: ../system/objects/permissions.rst:56 -msgid "view" +#: ../system/integrations/elasticsearch.rst:77 +msgid "" +"Your browser will automatically ask for your credentials - you'll then see " +"something like this:" msgstr "" -#: ../system/objects/permissions.rst:62 -msgid "View-only dialog for already existing data" +#: ../system/integrations/elasticsearch.rst:125 +msgid "Credentials" msgstr "" -#: ../system/objects/permissions.rst:64 -msgid "(e.g. user or organization from search)" +#: ../system/integrations/elasticsearch.rst:127 +msgid "" +"Within this section Zammad displays your available users. The password is " +"provided once (upon activation) and cannot be retrieved after that." msgstr "" -#: ../system/objects/permissions.rst:65 -msgid "signup" +#: ../system/integrations/elasticsearch.rst:131 +msgid "" +"If you need to change or reset your Elasticsearch user password, use the " +"\"Reset password\" button in the credentials table. Doing so creates a brand " +"new password for the account in question. This change is immediate, keep in " +"mind that this may affect third party tools connected to your instance." msgstr "" -#: ../system/objects/permissions.rst:67 -msgid "Sign-up screen for new customers" +#: ../system/integrations/exchange.rst:2 +msgid "Exchange" msgstr "" -#: ../system/objects/permissions.rst:68 -msgid "invite_customer" +#: ../system/integrations/exchange.rst:4 +msgid "" +"With Zammad's Exchange integration, you can easily use existing address " +"books without having to update more than one source." msgstr "" -#: ../system/objects/permissions.rst:71 +#: ../system/integrations/exchange.rst:7 msgid "" -"Customer invitation screen (from :doc:`First Steps ` area)" +"However, you should refrain from syncing all addresses, as the results may " +"not be what you expect (Exchange collects huge amounts of addresses). A " +"central address book of your company to sync makes more sense, as you can " +"ensure that Zammad gets only the data you need and want. Apart from this, it " +"is even not possible to sync the Global Address List (GAL) of your Exchange " +"system with Zammad." msgstr "" -#: ../system/objects/permissions.rst:72 -msgid "invite_agent" +#: ../system/integrations/exchange.rst:16 +msgid "" +"**Exchange and LDAP:** The exchange sync can be overruled by Zammad's LDAP " +"integration. If you have the same users in both sources, the LDAP version " +"will always be Zammad's pick." msgstr "" -#: ../system/objects/permissions.rst:74 +#: ../system/integrations/exchange.rst:19 msgid "" -"Agent invitation screen (from :doc:`First Steps ` area)" +"**One way sync:** the Exchange sync is one way. Exchange => Zammad. Changes " +"to your users inside of Zammad might be overwritten by the Exchange sync." msgstr "" -#: ../system/objects/permissions.rst:78 -msgid "Screen Options" +#: ../system/integrations/exchange.rst:24 +msgid "" +"To configure Exchange integration, simply go to the System > Integrations > " +"Exchange in the admin panel. Press \"change\" and follow the wizard for " +"adding the needed Exchange information to Zammad. On the last two steps " +"Zammad will ask you for the address book(s) and your desired attribute " +"mapping. By default, Zammad only maps email address, first- and lastname. " +"Technically, you can map any Exchange object to a Zammad user object (this " +"also works for custom objects!)." msgstr "" -#: ../system/objects/permissions.rst:80 +#: ../system/integrations/exchange.rst:35 msgid "" -"For the different screens you can select \"show\" and \"required\" options." +"If the SSL verification fails while connecting to Exchange, Zammad will ask " +"you to turn it off temporarily." msgstr "" -#: ../system/objects/permissions.rst:82 -msgid "**shown:** Show (check) or hide (uncheck) a field." +#: ../system/integrations/exchange.rst:38 +msgid "" +"Please be aware that **turning off SSL verification is a security risk**. It " +"should only be used temporarily or for testing purposes. If turned off, " +"there is no verification of the certificate, which means that every " +"presented certificate will be accepted." msgstr "" -#: ../system/objects/permissions.rst:83 +#: ../system/integrations/exchange.rst:43 msgid "" -"**required:** Set a field to mandatory (check). Forces users (via UI and " -"API) to populate the field." -msgstr "" - -#: ../system/objects/types.rst:7 -msgid "Example external data source" +"After pressing Continue, Zammad will check if the configuration is okay. You " +"can then enable Exchange and start your first sync. The sync will then run " +"hourly - if you need to change mappings or the address book(s), you can " +"change the configuration at any time." msgstr "" -#: ../system/objects/types.rst:2 -msgid "Attribute types" +#: ../system/integrations/exchange.rst:50 +msgid "" +"After the sync has finished, you can find the new Exchange contacts under " +"\"Users\". Zammad integrates them just as normal users." msgstr "" -#: ../system/objects/types.rst:4 +#: ../system/integrations/exchange.rst:55 msgid "" -"When adding a new object attribute, you can choose between the following " -"attribute types." +"In some cases you might see unique IDs as \"Login\" instead of the email " +"address. This is normal and doesn't affect the login or email mapping for " +"that entry." msgstr "" -#: ../system/objects/types.rst:14 +#: ../system/integrations/github.rst:4 msgid "" -"You cannot change the attribute format / type as soon as it is applied. If " -"you no longer need an object attribute, consider disabling it instead of " -"removing." +"Use GitHub integration to track GitHub issues directly within Zammad " +"tickets. Add issue hyperlinks and get a live summary of metadata like status " +"(open/closed), assignee, labels, and more." msgstr "" -#: ../system/objects/types.rst:18 -msgid "**What about the translation of my attributes?**" +#: ../system/integrations/github.rst:8 +msgid "Please note that our GitHub integration does not support pull requests." msgstr "" -#: ../system/objects/types.rst:20 -msgid "" -"For some attribute types you can decide if they should be translatable or " -"not. To be precise, it works only for the selectable fields because the " -"possible choices are known and limited. For the following attribute types, " -"you can set the translatable flag:" +#: ../system/integrations/github.rst:None +msgid "Integration page for GitHub" msgstr "" -#: ../system/objects/types.rst:25 -msgid "*Boolean field*" +#: ../system/integrations/github.rst:18 +msgid "" +"In your GitHub settings, create a new API token under **Developer settings > " +"Personal access tokens > Generate new token**. Leave the **Scopes** section " +"empty." msgstr "" -#: ../system/objects/types.rst:26 -msgid "*Single selection field*" +#: ../system/integrations/github.rst:0 ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to create a new API token" msgstr "" -#: ../system/objects/types.rst:27 -msgid "*Multiple selection field*" +#: ../system/integrations/github.rst:27 +msgid "Create a new API key with no scopes/privileges." msgstr "" -#: ../system/objects/types.rst:28 -msgid "*Single tree selection field*" +#: ../system/integrations/github.rst:29 +msgid "🔒 **Will this work for private repos?**" msgstr "" -#: ../system/objects/types.rst:29 -msgid "*Multiple tree selection field*" +#: ../system/integrations/github.rst:31 +msgid "" +"No. To link private repo issues, **use the** ``repo`` **scope instead**. " +"Bear in mind that the resulting token will have `lots of permissions that it " +"doesn't actually need `_, which presents a security risk if your token ever falls into " +"the wrong hands." msgstr "" -#: ../system/objects/types.rst:31 +#: ../system/integrations/github.rst:37 msgid "" -"For these types, you can find an additional field *Translate field contents*:" +"Unfortunately, because of how GitHub's OAuth token scopes are set up, this " +"is the only way to link issues on private repos." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Screenshot showing translatable attribute types" +#: ../system/integrations/github.rst:40 +msgid "Enter your new API token in Zammad and enable GitHub integration." msgstr "" -#: ../system/objects/types.rst:38 -msgid "Screenshot with example of translatable attribute type" +#: ../system/integrations/github.rst:0 +msgid "Screencast showing how to configure Zammad's GitHub integration" msgstr "" -#: ../system/objects/types.rst:45 -msgid "Boolean field" +#: ../system/integrations/github.rst:47 +msgid "" +"Use the default API endpoint (``https://api.github.com/graphql``) unless " +"you're using GitHub Enterprise Server." msgstr "" -#: ../system/objects/types.rst:41 +#: ../system/integrations/github.rst:50 msgid "" -"Provides a drop-down field with display values for ``true`` and ``false``. " -"Setting a default is mandatory." +"Once completed, a new GitHub issues tab will appear in the ticket pane. 🎉" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Boolean fields" +#: ../system/integrations/github.rst:59 ../system/integrations/gitlab.rst:52 +msgid "Token verification is taking a long time" msgstr "" -#: ../system/objects/types.rst:55 -msgid "Date field" +#: ../system/integrations/github.rst:56 ../system/integrations/gitlab.rst:49 +msgid "" +"Slight delays are normal (<2 min.), especially for systems under heavy load." msgstr "" -#: ../system/objects/types.rst:48 -msgid "Provides a date picker field and does not allow default values." +#: ../system/integrations/github.rst:58 +msgid "" +"Self-hosted administrators, please check your network settings to ensure " +"that your Zammad server can reach ``api.github.com``." msgstr "" -#: ../system/objects/types.rst:52 -msgid "Default time diff (hours)" +#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 +msgid "I reloaded the page and now the API token is gone" msgstr "" -#: ../system/objects/types.rst:51 +#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 msgid "" -"This setting helps the user by highlighting the day from now plus the " -"provided value. It *does not* pre-fill the field." -msgstr "" - -#: ../system/objects/types.rst:0 -msgid "Available settings for Date fields" +"This may indicate that Zammad is still verifying your API token. Try " +"reloading the page again in a couple minutes." msgstr "" -#: ../system/objects/types.rst:73 -msgid "Date & time field" +#: ../system/integrations/gitlab.rst:2 +msgid "GitLab" msgstr "" -#: ../system/objects/types.rst:58 -msgid "Provides a date and time picker – does not allow default values" +#: ../system/integrations/gitlab.rst:4 +msgid "" +"Use GitLab integration to track GitLab issues directly within Zammad " +"tickets. Add issue hyperlinks and get a live summary of metadata like status " +"(open/closed), assignee, labels, and more." msgstr "" -#: ../system/objects/types.rst:62 -msgid "Allow future" +#: ../system/integrations/gitlab.rst:8 +msgid "" +"Please note that our GitLab integration does not support merge requests." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Forbid dates and times in the future." +#: ../system/integrations/gitlab.rst:None +msgid "Integration page for GitLab" msgstr "" -#: ../system/objects/types.rst:66 -msgid "Allow past" +#: ../system/integrations/gitlab.rst:18 +msgid "" +"In your GitLab preferences, create a new API token under **Access Tokens**." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Forbid dates and times in the past." +#: ../system/integrations/gitlab.rst:20 +msgid "Under **Select scopes**, choose ``read_api`` only." msgstr "" -#: ../system/objects/types.rst:70 -msgid "Default time diff (minutes)" +#: ../system/integrations/gitlab.rst:27 +msgid "🔒 **If you wish to link issues on any private repos...**" msgstr "" -#: ../system/objects/types.rst:69 -msgid "" -"This setting helps the user by highlighting the day from now plus the " -"provided value. It does not pre-fill the field." +#: ../system/integrations/gitlab.rst:29 +msgid "Your API token must belong to an account with access to those repos." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Date & time fields" +#: ../system/integrations/gitlab.rst:31 +msgid "Enter your new API token in Zammad and enable GitLab integration." msgstr "" -#: ../system/objects/types.rst:86 -msgid "Integer field" +#: ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to configure Zammad's GitLab integration" msgstr "" -#: ../system/objects/types.rst:76 +#: ../system/integrations/gitlab.rst:40 msgid "" -"Provides an input field that allows integer usage only. You may define a " -"default value. You cannot enforce comma separation." +"Use the default API endpoint (``https://gitlab.com/api/graphql``) unless " +"you're a self-hosted GitLab user." msgstr "" -#: ../system/objects/types.rst:80 -msgid "Minimal" +#: ../system/integrations/gitlab.rst:43 +msgid "" +"Once completed, a new GitLab issues tab will appear in the ticket pane. 🎉" msgstr "" -#: ../system/objects/types.rst:80 -msgid "The minimal value the field accepts." +#: ../system/integrations/gitlab.rst:51 +msgid "" +"Self-hosted administrators, please check your network settings to ensure " +"that your Zammad server can reach ``gitlab.com``." msgstr "" -#: ../system/objects/types.rst:83 -msgid "Maximal" +#: ../system/integrations/i-doit.rst:2 +msgid "i-doit" msgstr "" -#: ../system/objects/types.rst:83 -msgid "The maximum value the field accepts." +#: ../system/integrations/i-doit.rst:4 +msgid "" +"`i-doit `_ is an open-source **configuration " +"management database** - in other words, a tool for keeping tabs on every " +"single piece of your physical and digital infrastructure, from network " +"equipment to virtual machines on down to the faceplates on your rack shelves " +"and more." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Integer fields" +#: ../system/integrations/i-doit.rst:10 +msgid "" +"What's that got to do with Zammad? Well, if you used tickets to track issues " +"with all that hardware, you might start wishing there was a way they could " +"talk to each other." msgstr "" -#: ../system/objects/types.rst:99 -msgid "Multiple selection field" +#: ../system/integrations/i-doit.rst:14 +msgid "Zammad gives you two:" msgstr "" -#: ../system/objects/types.rst:89 -msgid "" -"Provides a selection field that allows the selection of one or more out of " -"several. This field does allow setting a default value." +#: ../system/integrations/i-doit.rst:17 +msgid "1. Add i-doit Links to Zammad Tickets" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Multiple selection fields" +#: ../system/integrations/i-doit.rst:20 ../system/integrations/i-doit.rst:80 +msgid "What Users See" msgstr "" -#: ../system/objects/types.rst:112 -msgid "Single selection field" +#: ../system/integrations/i-doit.rst:26 +msgid "i-doit integration in Zammad's ticket pane" msgstr "" -#: ../system/objects/types.rst:102 +#: ../system/integrations/i-doit.rst:26 msgid "" -"Provides a drop-down field that allows selection of one value out of " -"several. This field does allow setting a default value." +"The i-doit integration will appear under a new 🖨 tab in the ticket pane." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Single selection fields" +#: ../system/integrations/i-doit.rst:28 +msgid "" +"i-doit integration puts a new tab in Zammad's ticket pane where you can add " +"links to existing i-doit devices for easy reference. (See our :user-docs:" +"`user documentation ` to learn " +"how it works in practice)." msgstr "" -#: ../system/objects/types.rst:142 -msgid "Textarea field" +#: ../system/integrations/i-doit.rst:36 ../system/integrations/i-doit.rst:93 +msgid "How to Set it Up" msgstr "" -#: ../system/objects/types.rst:115 +#: ../system/integrations/i-doit.rst:38 msgid "" -"Provides a text area input field (multiple lines) and thus allows e.g. new " -"lines. You can set a default field value." +"It requires i-doit's `API Add-on `_. Make sure to have it properly set up. Use the following setting:" msgstr "" -#: ../system/objects/types.rst:120 -msgid "" -"Please note that this field *does not* support text formatting or HTML " -"content (rich text)." +#: ../system/integrations/i-doit.rst:42 +msgid "Active: ``Yes``" msgstr "" -#: ../system/objects/types.rst:123 -msgid "**🥵 This field can consume a lot of visual space**" +#: ../system/integrations/i-doit.rst:43 +msgid "Enforce authentication by username and password: ``No``" msgstr "" -#: ../system/objects/types.rst:125 +#: ../system/integrations/i-doit.rst:45 msgid "" -"Depending on where you use this field type, it may use a lot of visual space " -"if you provide a lot of text. This may be an issue to work with." +"To set it up, enable the integration in the Zammad admin panel under " +"**System > Integrations > i-doit**:" msgstr "" -#: ../system/objects/types.rst:130 -msgid "Default" +#: ../system/integrations/i-doit.rst:None +msgid "i-doit settings within the integration pages" msgstr "" -#: ../system/objects/types.rst:129 -msgid "" -"The here provided text will be shown within the text area field or new data " -"sets." +#: ../system/integrations/i-doit.rst:53 +msgid "The root URL of your i-doit installation." msgstr "" -#: ../system/objects/types.rst:134 ../system/objects/types.rst:160 -msgid "Maxlength" +#: ../system/integrations/i-doit.rst:62 +msgid "API token" msgstr "" -#: ../system/objects/types.rst:0 ../system/objects/types.rst:160 -msgid "You can pick the maximum length of the field." +#: ../system/integrations/i-doit.rst:56 +msgid "" +"Found in the i-doit admin panel under **Interfaces / external data > JSON-" +"RPC API > Common Settings**." msgstr "" -#: ../system/objects/types.rst:0 -msgid "The default length of this object is ``500``." +#: ../system/integrations/i-doit.rst:0 +msgid "i-doit administration interface with API configuration" msgstr "" -#: ../system/objects/types.rst:139 -msgid "Rows" +#: ../system/integrations/i-doit.rst:67 +msgid "Client ID" msgstr "" -#: ../system/objects/types.rst:0 -msgid "" -"Change the number of rows to dislay so that you can use only the space you " -"really need." +#: ../system/integrations/i-doit.rst:65 +msgid "A unique name to identify Zammad within i-doit." msgstr "" -#: ../system/objects/types.rst:0 -msgid "The default number of rows is ``4``." +#: ../system/integrations/i-doit.rst:67 +msgid "(Zammad does not require you to enter a value here, but i-doit might!)" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Textarea fields" +#: ../system/integrations/i-doit.rst:70 +msgid "" +"Here you can decide if the certificate of your i-doit system has to be " +"verified or not. In case you are using custom certificates, please have a " +"look at :doc:`how to add them to Zammad `." msgstr "" -#: ../system/objects/types.rst:165 -msgid "Text field" +#: ../system/integrations/i-doit.rst:77 +msgid "2. List / Create Zammad Tickets in i-doit" msgstr "" -#: ../system/objects/types.rst:145 -msgid "Provides a text field (one line) and allows choosing a default value." +#: ../system/integrations/i-doit.rst:None +msgid "Zammad integration in i-doit's device view" msgstr "" -#: ../system/objects/types.rst:148 +#: ../system/integrations/i-doit.rst:86 msgid "" -"Defines the type of the input field. This allows e.g. your browser to ensure " -"that you provide the specific type." +"i-doit's ticket system integration gives you a way to see all the tickets " +"for a given device without ever leaving i-doit. (See our :user-docs:`user " +"documentation ` to learn how it " +"works in practice)." msgstr "" -#: ../system/objects/types.rst:152 -msgid "Currently available:" +#: ../system/integrations/i-doit.rst:95 +msgid "" +"Enable this integration in the i-doit admin panel under **Interfaces / " +"external data > Trouble Ticket System (TTS) > Configuration**:" msgstr "" -#: ../system/objects/types.rst:155 -msgid "Phone" +#: ../system/integrations/i-doit.rst:None +msgid "i-doit administration interface with TTS configuration" msgstr "" -#: ../system/objects/types.rst:156 -msgid "Text" +#: ../system/integrations/i-doit.rst:104 +msgid "TTS-Type" msgstr "" -#: ../system/objects/types.rst:157 -msgid "Url *(URL fields disable link-template availability)*" +#: ../system/integrations/i-doit.rst:104 +msgid "``Zammad``" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Text fields" +#: ../system/integrations/i-doit.rst:115 +msgid "Username / Password" msgstr "" -#: ../system/objects/types.rst:174 -msgid "Single tree selection field" +#: ../system/integrations/i-doit.rst:107 +msgid "Login credentials for a Zammad agent." msgstr "" -#: ../system/objects/types.rst:168 +#: ../system/integrations/i-doit.rst:109 msgid "" -"Provides a select-like field with up to 6 layers of options. Does not allow " -"setting a default value." +"This agent must have **read permission** for all :doc:`groups ` that plan on using the i-doit integration." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Tree Select fields" +#: ../system/integrations/i-doit.rst:113 +msgid "" +"You may even wish to create a dedicated agent account just for this " +"integration (otherwise, if the agent ever changes her password, you will " +"have to remember to update it here)." msgstr "" -#: ../system/objects/types.rst:183 -msgid "Multiple tree selection field" +#: ../system/integrations/i-doit.rst:117 +msgid "URL incl. protocol" msgstr "" -#: ../system/objects/types.rst:177 -msgid "" -"Provides a select-like field with up to 6 layers of options allowing the " -"selection of multiple values. Does not allow setting a default value." +#: ../system/integrations/i-doit.rst:118 +msgid "``https://your.zammad.domain``" msgstr "" -#: ../system/objects/types.rst:302 -msgid "External Data Source field" +#: ../system/integrations/index.rst:2 +msgid "Integrations" msgstr "" -#: ../system/objects/types.rst:186 +#: ../system/integrations/index.rst:4 msgid "" -"Provides a searchable field which fetches data from an external system. This " -"can be useful if you have data outside of Zammad and don't want to maintain " -"both data sources." +"Zammad offers numerous integrations that add rich features to your instance." msgstr "" -#: ../system/objects/types.rst:190 -msgid "The feature works as follows:" +#: ../system/integrations/index.rst:6 +msgid "We're still working on this part of our documentation, stay tight!" msgstr "" -#: ../system/objects/types.rst:192 -msgid "" -"Zammad sends a query with a search string (free text from agent or based on " -"a variable) in a pre-defined format (\"Search URL\") to an external system." +#: ../system/integrations/index.rst:10 +msgid "Integrations for Phone Systems" msgstr "" -#: ../system/objects/types.rst:195 +#: ../system/integrations/index.rst:14 msgid "" -"This external system searches for matches and provides a response as a JSON " -"structure to Zammad." +"Your VoIP provider or telephony system is not listed? Possibly your provider " +"supports Zammad by using the generic CTI - if you're unsure ask your " +"provider." msgstr "" -#: ../system/objects/types.rst:197 +#: ../system/integrations/index.rst:18 msgid "" -"Zammad just looks for the defined list and value keys, reads the content and " -"displays the value to the user. There is no search on Zammad side." +"Provider does not support Zammad? Consider creating a `feature request in " +"the Zammad Community `_." msgstr "" -#: ../system/objects/types.rst:201 -msgid "" -"The usage of a PostgreSQL database for Zammad is required. In any other " -"case, Zammad will hide the external data source type and you are not able to " -"use it. If you want to use this feature, consider to :docs:`migrate your " -"database `." +#: ../system/integrations/index.rst:31 +msgid "Integrations for Authentication and Customers" msgstr "" -#: ../system/objects/types.rst:205 -msgid "Currently, only ``GET`` is supported as request method." +#: ../system/integrations/index.rst:44 +msgid "Integrations for Monitoring Systems" msgstr "" -#: ../system/objects/types.rst:206 -msgid "" -"The data structure must be in JSON format and provide the objects in an " -"array." +#: ../system/integrations/index.rst:46 +msgid "This section currently misses the following integrations:" msgstr "" -#: ../system/objects/types.rst:208 -msgid "" -"The endpoint for the external data source has to support search. On Zammad " -"side, there is no search/logic implemented; however, you can define the " -"output key and value based on the result(s) from the response (which " -"provides already filtered content based on the search)." +#: ../system/integrations/index.rst:48 +msgid "Icinga" msgstr "" -#: ../system/objects/types.rst:212 -msgid "" -"If you receive more results as expected, your external data source search " -"may not work properly or the structure of the URL is not correct. You should " -"get in touch with a responsible person from the external system." +#: ../system/integrations/index.rst:49 +msgid "Monit" msgstr "" -#: ../system/objects/types.rst:217 -msgid "" -"Please have a look :doc:`at our example `, where you can find a possible configuration for a public " -"dummy endpoint." +#: ../system/integrations/index.rst:50 +msgid "Nagios" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for external data source fields" +#: ../system/integrations/index.rst:60 +msgid "Integrations for Issue Trackers" msgstr "" -#: ../system/objects/types.rst:242 -msgid "Search URL" +#: ../system/integrations/index.rst:70 +msgid "Other Integrations" msgstr "" -#: ../system/objects/types.rst:227 +#: ../system/integrations/index.rst:72 msgid "" -"Set your endpoint where Zammad fetches the data. Please make sure to include " -"a valid search :doc:`variable <../variables>` as an URL parameter. Example " -"for a free text search at user input: ``#{search.term}``" +"This section will hold any other integration that can't be grouped up (yet)." msgstr "" -#: ../system/objects/types.rst:232 -msgid "" -"If in doubt, ask the responsible person for the external data source how " -"they expect the strucuture of the URL." +#: ../system/integrations/ldap/index.rst:2 +msgid "LDAP / Active Directory" msgstr "" -#: ../system/objects/types.rst:236 +#: ../system/integrations/ldap/index.rst:4 msgid "" -"Depending on your search variable, the preview might work or not. The reason " -"is that the context might not be available and it is no bug." +"Zammad comes with a powerful LDAP integration that allows you to have a " +"single source of truth. By this you reduce the number of login credentials " +"your user has to remember." msgstr "" -#: ../system/objects/types.rst:239 +#: ../system/integrations/ldap/index.rst:10 msgid "" -"Please also make sure to use a variable which is available in your object " -"context. For example you won't be able to search for a ticket in a user " -"object context." -msgstr "" - -#: ../system/objects/types.rst:252 -msgid "SSL Verification" +"The LDAP source is also a perfect candidate for Zammad's :docs:`Kerberos " +"Single Sign-On ` but also works as addition " +"to other :doc:`/settings/security/third-party`." msgstr "" -#: ../system/objects/types.rst:245 -msgid "Here you can switch the SSL verification to no." +#: ../system/integrations/ldap/index.rst:None +msgid "Zammands LDAP management page" msgstr "" -#: ../system/objects/types.rst:249 -msgid "" -"If your external data source system is using self signed certificates, " -"please have a look :doc:`here ` for " -"further information about how to handle them in Zammad, so you can keep the " -"SSL verification activated." +#: ../system/integrations/ldap/index.rst:25 +msgid "📝 :doc:`manage`" msgstr "" -#: ../system/objects/types.rst:258 -msgid "HTTP Authentication" +#: ../system/integrations/ldap/index.rst:25 +msgid "Add, modify, remove or re-arrange your LDAP-Sources as needed." msgstr "" -#: ../system/objects/types.rst:255 -msgid "" -"If your external data source requires an authentication, you can set it " -"here. You can leave it empty or choose between *Basic Authentication* or " -"*Authentication Token* (selecting one of the two methods leads to additional " -"fields where you can enter your credentials/token)." +#: ../system/integrations/ldap/index.rst:30 +msgid "Before you continue, please note the following limitations." msgstr "" -#: ../system/objects/types.rst:265 -msgid "Search result list key" +#: ../system/integrations/ldap/index.rst:32 +msgid "Mapping / Synchronizing organizations is not possible" msgstr "" -#: ../system/objects/types.rst:261 +#: ../system/integrations/ldap/index.rst:36 msgid "" -"Defines the level in the JSON structure which provides the list with search " -"results. You can leave it empty, if the data is already provided as an " -"array. If you have to go deeper in the structure, you can provide a path " -"with ``.`` as separators, e.g. ``key.subkey.sub-sub-key``." +"You may want to consider using domain based assignments to overcome this " +"issue. Learn more on :doc:`/manage/organizations/index`." msgstr "" -#: ../system/objects/types.rst:271 -msgid "Search result value key" +#: ../system/integrations/ldap/index.rst:39 +msgid "" +"Zammad's LDAP sync is one way. Editing user settings or permissions may be " +"overwritten upon the next sync depending on your configuration." msgstr "" -#: ../system/objects/types.rst:268 -msgid "" -"Defines the attribute in the structure in which your external data source " -"provides the *value* for your data. An example would be a product *number*. " -"If you have to go deeper in the structure, you can provide a path with ``.`` " -"as separators, e.g. ``key.subkey.sub-sub-key``." +#: ../system/integrations/ldap/index.rst:41 +msgid "Nested groups are not supported." msgstr "" -#: ../system/objects/types.rst:277 -msgid "Search result label key" +#: ../system/integrations/ldap/index.rst:42 +msgid "Synchronizing user avatars from LDAP is not supported." msgstr "" -#: ../system/objects/types.rst:274 -msgid "" -"Defines the attribute in the structure in which your external data source " -"provides the *label* for your data. An example would be a product *name*. If " -"you have to go deeper in the structure, you can provide a path with ``.`` as " -"separators, e.g. ``key.subkey.sub-sub-key``." +#: ../system/integrations/ldap/index.rst:43 +msgid "Unlike user filters, group filters cannot be changed." msgstr "" -#: ../system/objects/types.rst:280 +#: ../system/integrations/ldap/index.rst:44 msgid "" -"In the preview area, you can find the following items (depending on your " -"configuration above):" +"When a user originates from an LDAP server, Zammad will try to verify the " +"login credentials against LDAP first - if this fails Zammad will check its " +"local database." msgstr "" -#: ../system/objects/types.rst:283 +#: ../system/integrations/ldap/index.rst:50 msgid "" -"**Error/hint message** (only if configuration is not complete): Zammad tells " -"you, if there is a problem and what you should change in your configuration." +"Users can have local passwords even if they're LDAP users! You can learn " +"more about user accounts in general on :doc:`/manage/users/index`." msgstr "" -#: ../system/objects/types.rst:286 +#: ../system/integrations/ldap/index.rst:54 msgid "" -"**Search field**: search for an existing attribute in the data source to get " -"a preview. This is required for the fields below to show up." +"When several LDAP sources contain the same user (meaning the same email " +"address), the user in question will be updated with every source configured. " +"*The last LDAP source will win.*" msgstr "" -#: ../system/objects/types.rst:288 +#: ../system/integrations/ldap/index.rst:58 msgid "" -"**Search result response** (only if configuration is not complete): here you " -"can find a syntax highlighted JSON preview of the response, based on the " -"search term you entered." +"This is subject to change with `Issue 4109 `_ in the future." msgstr "" -#: ../system/objects/types.rst:291 +#: ../system/integrations/ldap/index.rst:60 msgid "" -"**Search result list** (only if *search result list key* is properly set): " -"output of the structure under the configured *search result list key*." +"Synchronization statistics currently affect *all* configured LDAP sources. " +"This also applies for newly added or updated sources." msgstr "" -#: ../system/objects/types.rst:294 +#: ../system/integrations/ldap/index.rst:63 msgid "" -"**Preview table** (when fully configured): Zammad shows you a table which " -"includes the found items based on the search string (value, label and " -"optional link). You can use this preview if you don't have the complete data " -"structure of the external system in mind." +"This is subject to change with `Issue 4108 `_ in the future." msgstr "" -#: ../system/objects/types.rst:299 +#: ../system/integrations/ldap/index.rst:65 msgid "" -"An example of a configured external data source field from agent perspective:" +"Zammad currently has limited fallback server support. You can workaround " +"this by providing several sources - however, ensure to have the exact same " +"configuration on your fallback." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Screencast showing the search for a product in a ticket" +#: ../system/integrations/ldap/index.rst:69 +msgid "" +"This is subject to improve with `Issue 4107 `_ in the future." msgstr "" -#: ../system/objects/types.rst:307 -msgid "URL fields (Link-Template)" +#: ../system/integrations/ldap/index.rst:76 +msgid "" +"This section holds all requests Zammad handled for all LDAP sources. These " +"entries can either contain synchronization information or logins " +"(authentication attempts via Zammad's login interface)." msgstr "" -#: ../system/objects/types.rst:311 +#: ../system/integrations/ldap/index.rst:80 msgid "" -"This function is restricted to Text, Select and External data source types " -"only." +"By clicking on any request, Zammad will provide even more information. The " +"provided information can be useful when something does not work as expected." msgstr "" -#: ../system/objects/types.rst:314 +#: ../system/integrations/ldap/index.rst:85 msgid "" -"Link-Templates are an amazing way to dynamically generate URLs. They allow " -"you to integrate other systems better without having to manually copy data " -"from Zammad if possible." +"Especially a LDAP synchronization can cause many log entries. The web " +"interface will always limit the number of shown entries to the last 50 " +"entries." msgstr "" -#: ../system/objects/types.rst:320 +#: ../system/integrations/ldap/index.rst:None msgid "" -"Another great way of communicating with another system may be Zammad's :doc:" -"`Webhooks `." +"Screencast showing LDAP integration log entries and a detail view on\n" +"an entry." msgstr "" -#: ../system/objects/types.rst:323 -msgid "" -"After filling a link-template enabled field, an URL icon will appear on its " -"right. Clicking on the icon opens a new tab." +#: ../system/integrations/ldap/manage.rst:2 +msgid "Manage LDAP-Sources" msgstr "" -#: ../system/objects/types.rst:328 +#: ../system/integrations/ldap/manage.rst:6 msgid "" -"Even though Zammad displays the link template within object edit and create " -"screens, the function is optional. It's only active if you populate the " -"field." +"Please keep in mind all current limitations for the LDAP synchronization. " +"This will help to understand scopes of the following operations better." msgstr "" -#: ../system/objects/types.rst:333 -msgid "" -"What's the difference between URL and text fields with link template...?!" +#: ../system/integrations/ldap/manage.rst:65 +msgid "Add new source" msgstr "" -#: ../system/objects/types.rst:335 +#: ../system/integrations/ldap/manage.rst:10 msgid "" -"Both fields have different use cases. Use ``text`` type text fields when " -"ever you have a *static* url that requires dynamic parameters. If you " -"require a drag & drop like field that you can put in any URL, use ``URL`` " -"type text fields." +"Using the *New Source* button allows you to add new LDAP sources to your " +"installation. You're not limited in the number of sources, however, keep in " +"mind that many sources will also take more time to synchronize." msgstr "" -#: ../system/objects/types.rst:340 +#: ../system/integrations/ldap/manage.rst:14 msgid "" -"The difference is easier to spot when comparing the fields directly, below " -"screencast shows the result - the dynamic approach uses existing values in " -"the moment of updating to built the URL - e.g. ``https://google.com/search?" -"q=cookies`` - while the URL approach uses the actual URL of the field - e.g. " -"``https://zammad.com``." +"You can choose between different encryption types, namely *SSL* and " +"*STARTTLS* or none of them (\"*No SSL*\"). If you choose *SSL* or " +"*STARTTLS*, Zammad will display an additional *SSL verification* option that " +"allows you to disable the verification, e.g. for self-signed SSL " +"certificates. You can also tell Zammad to use a different port by appending " +"``:`` to your hostname/IP." msgstr "" -#: ../system/objects/types.rst:None +#: ../system/integrations/ldap/manage.rst:0 msgid "" -"Screencast showing the differents in between URL and text type fields with " -"actual values" +"Screenshot of configuring a new LDAP source with SSL encryption and SSL " +"verification" msgstr "" -#: ../system/objects/types.rst:352 -msgid "How does this work...?!" +#: ../system/integrations/ldap/manage.rst:26 +msgid "" +"New Source with SSL transport security enabled and certificate verification" msgstr "" -#: ../system/objects/types.rst:354 +#: ../system/integrations/ldap/manage.rst:30 msgid "" -"As an example, let's say you have an attribute called ``amazing_attribute`` " -"and you want to open a google search directly with the input from that field." +"Using an user filter can be a good idea if you only require a small subset " +"of your LDAP users in Zammad." msgstr "" -#: ../system/objects/types.rst:357 -msgid "" -"Providing the link-template field below allows you to do so: ``https://www." -"google.com/search?q=#{ticket.amazing_attribute}``" +#: ../system/integrations/ldap/manage.rst:42 +msgid "This especially affects inactive users" msgstr "" -#: ../system/objects/types.rst:362 +#: ../system/integrations/ldap/manage.rst:34 msgid "" -"You can use any :doc:`Zammad variable ` as long as it's " -"available in the moment you need it." +"As every LDAP behaves differently on which attributes and how they are set, " +"Zammad doesn't care about any flags." msgstr "" -#: ../system/objects/types.rst:365 +#: ../system/integrations/ldap/manage.rst:37 msgid "" -"As a result, you are redirected to Google with a search for the value of the " -"attribute, if you click on the button in the ticket (as you can see in the " -"screencast above)." +"Users that no longer are returned by your LDAP source will automatically be " +"set to inactive. Zammad assumes that the user was deactivated." msgstr "" -#: ../system/packages.rst:2 -msgid "Packages" +#: ../system/integrations/ldap/manage.rst:41 +msgid "" +"Users will never be removed automatically! If you want to remove obsolete " +"users, use :doc:`/system/data-privacy`." msgstr "" -#: ../system/packages.rst:4 -msgid "That's the package management-area." +#: ../system/integrations/ldap/manage.rst:46 +msgid "Active Directory admins" msgstr "" -#: ../system/packages.rst:6 -msgid "Individual add-ons for Zammad can be installed and managed here." +#: ../system/integrations/ldap/manage.rst:45 +msgid "" +"Active Directories are quite specific on how to filter for active users only " +"- please see the `Microsoft documentation `_ for more " +"information." msgstr "" -#: ../system/sessions.rst:2 -msgid "Sessions" +#: ../system/integrations/ldap/manage.rst:51 +msgid "" +"*Do not* manually write pathes of either LDAP attributes or groups. If " +"Zammad does not display them, it either cannot find them or you have a lot " +"of users that don't have the attributes populated." msgstr "" -#: ../system/sessions.rst:4 +#: ../system/integrations/ldap/manage.rst:55 msgid "" -"Sessions management allows reviewing currently known user sessions and " -"allows to end these. The session timeout is affected by :ref:" -"`security_session_timeout` configurations from security settings." +"Zammad will always only return attributes that are filled - this reduces the " +"returned list of attributes greatly." msgstr "" -#: ../system/sessions.rst:None -msgid "Screenshot showing Zammad's session management" +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing how to add a new LDAP source" msgstr "" -#: ../system/sessions.rst:13 -msgid "Zammad will provide the following information:" +#: ../system/integrations/ldap/manage.rst:63 +msgid "" +"If your LDAP system doesn't allow anonymous bind, Zammad detects it and " +"provides you an editable \"Base DN\" *text* field instead of a prefilled " +"*select* field." msgstr "" -#: ../system/sessions.rst:16 -msgid "" -"The user account this session entry belongs to. It can be normal if a user " -"has several sessions in the list. This can be due to changed browser " -"information or if you use e.g. single sign on methods where the user does " -"not use the log off button." +#: ../system/integrations/ldap/manage.rst:81 +msgid "Review or edit existing source" msgstr "" -#: ../system/sessions.rst:22 -msgid "Browser" +#: ../system/integrations/ldap/manage.rst:68 +msgid "" +"Clicking on a LDAP source will provide a configuration and mapping overview." msgstr "" -#: ../system/sessions.rst:22 -msgid "The browser agent communicated to Zammad." +#: ../system/integrations/ldap/manage.rst:70 +msgid "" +"If needed you can then use the *Change* button to update either the name, " +"active state or the whole configuration. If you're changing the whole " +"configuration, the dialogue will be identical to the source creation." msgstr "" -#: ../system/sessions.rst:40 -msgid "Location" +#: ../system/integrations/ldap/manage.rst:76 +msgid "" +"Did your LDAP server change? Different LDAP servers have different " +"structures and default attributes. This causes the LDAP synchronization to " +"likely fail. Consider removing the affected source and re-add it." msgstr "" -#: ../system/sessions.rst:25 -msgid "" -"The anticipated location based on the users IP address. Depending on the IP " -"address the result shown may differ. This option depends on :doc:`/settings/" -"system/services`." +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing the update of the source name." msgstr "" -#: ../system/sessions.rst:29 -msgid "The following information can be shown:" +#: ../system/integrations/ldap/manage.rst:89 +msgid "Re-arrange LDAP source's order" msgstr "" -#: ../system/sessions.rst:33 -msgid "IP address" +#: ../system/integrations/ldap/manage.rst:84 +msgid "" +"You can change the synchronization order for each source at any time. Zammad " +"will synchronize the sources from top to bottom." msgstr "" -#: ../system/sessions.rst:32 +#: ../system/integrations/ldap/manage.rst:0 msgid "" -"Either if you set *Geo IP services* to inactive or you're using internal IP " -"address which do not provide location information." +"Screencasting showing how to change the source order by using\n" +"drag and drop." msgstr "" -#: ../system/sessions.rst:40 -msgid "Country (or Country + City)" +#: ../system/integrations/ldap/manage.rst:101 +msgid "Remove a source" msgstr "" -#: ../system/sessions.rst:36 +#: ../system/integrations/ldap/manage.rst:92 msgid "" -"If *Geo IP services* is enabled only. Depends on how detailed the available " -"IP address information are." +"If you no longer need the a LDAP source or simply want to start over, you " +"can remove them at any time. This will not remove synchronized users, data " +"synchronized or permissions." msgstr "" -#: ../system/sessions.rst:39 +#: ../system/integrations/ldap/manage.rst:98 msgid "" -"Be aware that results can be inaccurate - this technically is not an error." +"Not sure if you'd need the source later on? Set the source to inactive " +"instead of removing it - see *Review or edit existing source* for more." msgstr "" -#: ../system/sessions.rst:43 -msgid "Age" +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing how to remove LDAP sources." msgstr "" -#: ../system/sessions.rst:43 -msgid "Provides the time when the session initially has been created." +#: ../system/integrations/pgp/index.rst:2 +msgid "PGP" msgstr "" -#: ../system/sessions.rst:50 -msgid "Update" +#: ../system/integrations/pgp/index.rst:7 +msgid "" +"Pretty Good Privacy (PGP) is another method for secure email communication. " +"With PGP, you can exchange **signed** and **encrypted** messages with others." msgstr "" -#: ../system/sessions.rst:46 -msgid "" -"Provides the time the user used this session to open Zammad. This timestamp " -"is only updated if the user e.g. reloads, not during normal work on tickets." +#: ../system/integrations/pgp/index.rst:13 +#: ../system/integrations/smime/index.rst:17 +msgid "Signing" msgstr "" -#: ../system/sessions.rst:50 -msgid "This timestamp is being used for the session timeout." +#: ../system/integrations/pgp/index.rst:11 +msgid "is a proof that a message hasn't been manipulated on its way." msgstr "" -#: ../system/sessions.rst:53 +#: ../system/integrations/pgp/index.rst:13 msgid "" -"Use the delete button to remove a single session on behalf of your user." +"In other words, it guarantees message **integrity** and **authenticity**." msgstr "" -#: ../system/subscription/billing.rst:2 -msgid "Billing" +#: ../system/integrations/pgp/index.rst:19 +#: ../system/integrations/smime/index.rst:22 +msgid "Encryption" msgstr "" -#: ../system/subscription/billing.rst:4 +#: ../system/integrations/pgp/index.rst:16 +#: ../system/integrations/smime/index.rst:20 msgid "" -"Within the billing tab you can control all billing relevant information like " -"invoices, billing address and the option to cancel your subscription." -msgstr "" - -#: ../system/subscription/billing.rst:33 -msgid "Billing information" +"scrambles a message so that it can only be unscrambled by the intended " +"recipient." msgstr "" -#: ../system/subscription/billing.rst:8 +#: ../system/integrations/pgp/index.rst:19 msgid "" -"All adjusted billing information below only affect future invoices. If your " -"invoice was issued wrong, please contact `our sales team `_." +"In other words, it guarantees message **privacy** and **data security**." msgstr "" -#: ../system/subscription/billing.rst:14 -msgid "Billing address" +#: ../system/integrations/pgp/index.rst:25 +msgid "Screenshot of ticket creation with encrypt and sign buttons" msgstr "" -#: ../system/subscription/billing.rst:13 +#: ../system/integrations/pgp/index.rst:25 msgid "" -"Provide your company address here, make sure to include the companies name " -"in case required. This address will be referenced on your invoice." +"Once PGP has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " +"appear in the ticket composer." msgstr "" -#: ../system/subscription/billing.rst:18 -msgid "VAT ID" +#: ../system/integrations/pgp/index.rst:28 +msgid "**Sign button not visible?**" msgstr "" -#: ../system/subscription/billing.rst:17 +#: ../system/integrations/pgp/index.rst:30 msgid "" -"Provide your VAT ID here. If applicable your invoice will not contain German " -"VAT. Please make sure to pay the VAT in your country as required." +"Please note that the signing of emails is based on the outgoing email " +"account. That means you have to choose a group with a sender email account, " +"which has a private key assigned." msgstr "" -#: ../system/subscription/billing.rst:27 -msgid "Billing Email Address" +#: ../system/integrations/pgp/index.rst:35 +msgid "Handling of Keys" msgstr "" -#: ../system/subscription/billing.rst:21 +#: ../system/integrations/pgp/index.rst:36 msgid "" -"Usually the instance owner (the person that registered the instance) will " -"receive all emails including the invoices. In case you have your own billing " -"department, you can provide their email address here." +"To use the PGP function, you have to enable the integration (PGP) by " +"switching the toggle to *enabled*." msgstr "" -#: ../system/subscription/billing.rst:25 +#: ../system/integrations/pgp/index.rst:39 msgid "" -"All billing relevant information will then be sent to this email address." +"You can add keys by clicking the *add key* button. The keys can be imported " +"from a file or you can paste the content of the key in the text box." msgstr "" -#: ../system/subscription/billing.rst:27 -msgid "Invoices are sent as attachment (PDF) to this email address." +#: ../system/integrations/pgp/index.rst:42 +msgid "**Which keys do I have to import?**" msgstr "" -#: ../system/subscription/billing.rst:29 +#: ../system/integrations/pgp/index.rst:44 msgid "" -"Don't forget to press the *Submit* button after you changed above settings." +"For **signing** *outgoing* emails, you have to import the private key of " +"your Zammad email account." msgstr "" -#: ../system/subscription/billing.rst:0 +#: ../system/integrations/pgp/index.rst:47 msgid "" -"Screenshot showing options for billing information within the\n" -"subscription menu" -msgstr "" - -#: ../system/subscription/billing.rst:70 -msgid "Payment history" +"For **encrypting** *outgoing* emails, you have to import the public key of " +"the customer's email account." msgstr "" -#: ../system/subscription/billing.rst:36 +#: ../system/integrations/pgp/index.rst:50 msgid "" -"The payment history will display a history of all paid invoices. At this " -"point you can also download these in case you need them again." +"For **verifying the signature** of signed *incoming* emails, you have to " +"import the public key of the customer." msgstr "" -#: ../system/subscription/billing.rst:41 +#: ../system/integrations/pgp/index.rst:53 msgid "" -"You will only find *paid* invoices here. Invoices that are to be billed are " -"not available before the payment is completed." +"For **decrypting** of encrypted *incoming* emails, you have to import the " +"private key of your Zammad email account." msgstr "" -#: ../system/subscription/billing.rst:46 -msgid "Date" +#: ../system/integrations/pgp/index.rst:57 +msgid "Import Keys From a File" msgstr "" -#: ../system/subscription/billing.rst:46 -msgid "Date of the invoice creation." +#: ../system/integrations/pgp/index.rst:58 +msgid "You can import keys from a file in the section **Upload key**:" msgstr "" -#: ../system/subscription/billing.rst:49 -msgid "Amount" +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of adding a key via file" msgstr "" -#: ../system/subscription/billing.rst:49 -msgid "Invoice total including VAT if applicable." +#: ../system/integrations/pgp/index.rst:64 +msgid "" +"**Supported file formats:** ASCII-armor as well as binary GPG format " +"(basically any GPG supported key format) is supported here." msgstr "" -#: ../system/subscription/billing.rst:52 -msgid "" -"Contains contract period (monthly or yearly) and hosted plan for the " -"subscription period in question." +#: ../system/integrations/pgp/index.rst:68 +msgid "Import Keys by Pasting the Content" msgstr "" -#: ../system/subscription/billing.rst:63 -msgid "Payment method / Service period" +#: ../system/integrations/pgp/index.rst:69 +msgid "You can also paste the key's content in the section **paste key**:" msgstr "" -#: ../system/subscription/billing.rst:56 -msgid "" -"Used bank account or credit card as well as the subscription period the " -"invoice is about." +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of adding a key via pasting" msgstr "" -#: ../system/subscription/billing.rst:61 +#: ../system/integrations/pgp/index.rst:75 msgid "" -"It might happen that the invoice date and subscription period differ. This " -"is nothing to worry about, the subscription periods will be accounted later " -"on." +"**Supported format:** Please note that only ASCII-armor is supported here." msgstr "" -#: ../system/subscription/billing.rst:67 -msgid "Receipt" +#: ../system/integrations/pgp/index.rst:78 +msgid "Deleting Keys" msgstr "" -#: ../system/subscription/billing.rst:66 +#: ../system/integrations/pgp/index.rst:79 msgid "" -"Use the arrow to download the invoice in question. You can download all " -"available invoices any time you need to here!" +"If you want to delete a specific key, you can do it by clicking on the menu " +"in the *actions* column and select **delete**:" msgstr "" -#: ../system/subscription/billing.rst:0 -msgid "Screenshot showing payment history of a hosted instance" +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of deleting a key" msgstr "" -#: ../system/subscription/billing.rst:94 -msgid "Do you want to cancel your subscription?" +#: ../system/integrations/pgp/index.rst:88 +msgid "Downloading Keys" msgstr "" -#: ../system/subscription/billing.rst:73 +#: ../system/integrations/pgp/index.rst:89 msgid "" -"In case you no longer want to use Zammad's SaaS, you can cancel your " -"subscription by using the red *Yes, please cancel my subscription* button." +"If you want to download your keys, you can do this as well via corresponding " +"action buttons. Depending on the key, you can choose wether you want to " +"download the private or the public key." msgstr "" -#: ../system/subscription/billing.rst:76 -msgid "" -"Your subscription will end the day after your trial or billing period ends." +#: ../system/integrations/pgp/index.rst:95 +#: ../system/integrations/smime/manage-certificates.rst:76 +msgid "Default Behavior" msgstr "" -#: ../system/subscription/billing.rst:80 +#: ../system/integrations/pgp/index.rst:96 msgid "" -"We will remind you about your cancelled subscription several times up front. " -"After the subscription ended all instance data will be removed. A restore " -"*is not* possible after that point!" +"Here you can adjust on per group basis, if *sign* and *encryption* is on or " +"off by default. Please be aware, that agents can always override the setting " +"for each individual article." msgstr "" -#: ../system/subscription/billing.rst:0 -msgid "Screencast showing how to cancel a subscription" +#: ../system/integrations/pgp/index.rst:None +msgid "Adjusting default behavior on per group basis" msgstr "" -#: ../system/subscription/billing.rst:87 -msgid "**😖 Cancelled by accident?**" +#: ../system/integrations/pgp/index.rst:107 +msgid "" +"Here you can see the last actions regarding signing and encryption and if " +"they were successful." msgstr "" -#: ../system/subscription/billing.rst:89 -msgid "" -"You can always undo the cancellation via the *Yes, undo the cancellation of " -"my subscription* button up to the last subscription day!" +#: ../system/integrations/pgp/index.rst:117 +msgid "**Sign button is not visible, but keys are imported.**" +msgstr "" + +#: ../system/integrations/pgp/index.rst:115 +msgid "Did you choose a group in the ticket?" msgstr "" -#: ../system/subscription/billing.rst:0 +#: ../system/integrations/pgp/index.rst:116 msgid "" -"Screenshot showing a red button to cancel the subscription\n" -"cancellation" +"Did you import a private key for the email adress, which is used for " +"outgoing emails in the group?" msgstr "" -#: ../system/subscription/index.rst:2 -msgid "Subscription (SaaS)" +#: ../system/integrations/pgp/index.rst:122 +msgid "**How to obtain keys?**" msgstr "" -#: ../system/subscription/index.rst:4 +#: ../system/integrations/pgp/index.rst:120 msgid "" -"The subscription settings page allows you to configure your instances " -"package and number of agents required." +"You can create them yourself! There are some good tutorials on the web on " +"how to create them. Providing keys to Zammad is a prerequisite to use the " +"PGP feature." msgstr "" -#: ../system/subscription/index.rst:9 -msgid "" -"This setting section is only available for Hosted setups. If you're looking " -"for on premise support contracts, please see the `Zammad pricing page " -"`_." +#: ../system/integrations/pgp/index.rst:127 +msgid "**It says a passphrase is needed, but I haven't got one.**" msgstr "" -#: ../system/subscription/index.rst:20 +#: ../system/integrations/pgp/index.rst:125 msgid "" -"The subscription section currently consists of two tabs: Plan & Billing. For " -"your overview we've divided those two tabs into independent sub pages:" +"If the key is secured with a passphrase, you have to provide it for the " +"import in Zammad. It is possible that keys may have an empty passphrase. " +"However, this is *not* recommended." msgstr "" -#: ../system/subscription/index.rst:25 -msgid ":doc:`💰 Subscription plan `" +#: ../system/integrations/pgp/index.rst:132 +msgid "**How do my customers get my new key?**" msgstr "" -#: ../system/subscription/index.rst:24 +#: ../system/integrations/pgp/index.rst:130 msgid "" -"Everything affecting your instance subscription functions like number of " -"agents, package and payment method." +"You have to provide your **public** key in advance. Your customer also has " +"to configure PGP in their email workflow and import your public key. The " +"other way round, you have to get the public key of your customer and have to " +"import it to Zammad." +msgstr "" + +#: ../system/integrations/slack.rst:2 +msgid "Slack" msgstr "" -#: ../system/subscription/index.rst:28 -msgid ":doc:`🧾 Subscription billing `" +#: ../system/integrations/slack.rst:4 +msgid "**⚠️ Deprecation warning ⚠️**" msgstr "" -#: ../system/subscription/index.rst:28 +#: ../system/integrations/slack.rst:6 msgid "" -"Everything regarding billing address, invoices and account cancellation." +"Zammad 7 will no longer support this dedicated Slack integration. It is " +"recommended to switch to :doc:`pre-defined webhooks ` instead. Existing Slack integrations should " +"be migrated manually before this feature is dropped." msgstr "" -#: ../system/subscription/index.rst:33 -msgid "FAQ" +#: ../system/integrations/slack.rst:14 +msgid "" +"In order to use this feature, please add a new Slack app to your Workspace. " +"The App you need is called ``Incoming WebHooks`` ." msgstr "" -#: ../system/subscription/index.rst:37 -msgid "I set up a trial account but am missing functions to test" +#: ../system/integrations/slack.rst:18 +msgid "Why Do I Need This Feature?" msgstr "" -#: ../system/subscription/index.rst:36 +#: ../system/integrations/slack.rst:20 msgid "" -"The trial instance is running within the professional package allowing up to " -"three agents." +"If you're already using Slack for your team communication, you'll love this " +"feature! Our Slack integration can push ticket notifications about the last " +"ticket article based on the following events:" msgstr "" -#: ../system/subscription/index.rst:40 -msgid "Can I change package within the trial?" +#: ../system/integrations/slack.rst:24 +msgid "on Ticket creation" msgstr "" -#: ../system/subscription/index.rst:40 -msgid "No. As soon as the package is changed the subscription begins." +#: ../system/integrations/slack.rst:25 +msgid "on Ticket updates" msgstr "" -#: ../system/subscription/index.rst:45 -msgid "What happens to my trial instance after the trial period ended?" +#: ../system/integrations/slack.rst:26 +msgid "on reached reminders" msgstr "" -#: ../system/subscription/index.rst:43 -msgid "" -"Your instance will automatically be canceled for you. Please see *What " -"happens to my instance after it has been canceled?* for more." +#: ../system/integrations/slack.rst:27 +msgid "a Ticket has escalated" msgstr "" -#: ../system/subscription/index.rst:58 -msgid "What happens to my instance after it has been canceled?" +#: ../system/integrations/slack.rst:28 +msgid "a Ticket is going to escalate" msgstr "" -#: ../system/subscription/index.rst:48 -msgid "That depends slightly on your instance state:" +#: ../system/integrations/slack.rst:30 +msgid "" +"Zammad will provide the Ticket title, a direct link to the Ticket, the event " +"type (creation, updated, escalation), the customer, time and the last " +"article that has triggered the notification." msgstr "" -#: ../system/subscription/index.rst:54 -msgid "Trial instance" +#: ../system/integrations/slack.rst:34 +msgid "" +"This will give you further options, as you can see e.g. escalating tickets " +"that are assigned to an agent that's e.g. absent. You can interact faster, " +"as you might see problems earlier (or even before the problem gets one)." msgstr "" -#: ../system/subscription/index.rst:51 +#: ../system/integrations/slack.rst:38 msgid "" -"If you're still on trial, we will ice your instance and remind you once " -"again about your instance. We then will wait some days and remove your " -"instance from our system. This is the last time we will inform you by Email." +"If needed and wanted, you can even discuss directly about the topic before " +"sending an answer to the customer. Another possible use case would be a " +"agent monitoring new agents and their answers to tickets." msgstr "" -#: ../system/subscription/index.rst:58 -msgid "Paid instance" +#: ../system/integrations/slack.rst:44 +msgid "Configure the Integration" msgstr "" -#: ../system/subscription/index.rst:57 +#: ../system/integrations/slack.rst:46 msgid "" -"If you're a paying customer and canceled your subscription, the instance " -"removal will take place the day after your last subscription day." +"First of all, please go to your slack workspace - go to administration => " +"Manage Apps. If you don't have an app yet, you can simply add a new one - " +"just search for ``Incoming WebHooks`` and customize the app to your needs." msgstr "" -#: ../system/subscription/index.rst:60 -msgid "Can removed instances be restored?" +#: ../system/integrations/slack.rst:50 +msgid "" +"Choose (or create) the channel Zammad should post it's information to and " +"press on \"Add Incoming WebHooks integration\". If you're ready, copy the " +"provided WebHook URL and go to your Zammad installation." msgstr "" -#: ../system/subscription/index.rst:61 -msgid "No. Once your instance has been removed, a restoration is not possible." +#: ../system/integrations/slack.rst:56 +msgid "" +"You need administrative rights on the Slack Workspace. The link to the app " +"directory is normally ``https://[workspace-name].slack.com/apps`` ." msgstr "" -#: ../system/subscription/plan.rst:2 ../system/subscription/plan.rst:38 -msgid "Plan" +#: ../system/integrations/slack.rst:63 +msgid "" +"To configure the slack integration, log in to Zammad and go to Integrations " +"(System) => Slack in the admin panel." msgstr "" -#: ../system/subscription/plan.rst:16 -msgid "Subscription" +#: ../system/integrations/slack.rst:66 +msgid "" +"Here you can choose on what evens Zammad should post information about a " +"ticket to your Slack channel. Next you need to device what groups shall be " +"affected by this, as anybody with access to that specific Slack channel can " +"read at least parts of the ticket this might be a privacy issue, if you " +"select the wrong groups. The username is simply the name that Zammad uses as " +"display name inside the Slack chat. The channel defines the Slack channel " +"the information is being posted in. As last option, you can set a custom " +"icon for posting to slack." msgstr "" -#: ../system/subscription/plan.rst:5 +#: ../system/integrations/slack.rst:74 msgid "" -"On the top of the subscription summary you'll find the number of used and " -"available (booked) agent seats. By using the *see more* link you can also " -"expand an agent list to see the currently configured active agents. This " -"list *does not* count accounts with admin permissions only." +"When you're ready, just hit \"Submit\" and enable the integration. Zammad " +"will now post new ticket information based on the trigger you chose. Below " +"the options you have the recent log that shows the latest requests to Slack " +"for debugging if needed." msgstr "" -#: ../system/subscription/plan.rst:0 +#: ../system/integrations/slack.rst:81 msgid "" -"Within subscription you can always see how many agents are still\n" -"available to add and who uses the seats." +"If you leave the Icon URL empty, Zammad will use the Zammad logo instead. " +"The icon should be a square PNG file." msgstr "" -#: ../system/subscription/plan.rst:14 +#: ../system/integrations/slack.rst:90 msgid "" -"Learn more on how to manage your agents in general :doc:`here `." +"The following figure shows how it will look if you choose to receive updates " +"on created and updated tickets. On every post Zammad sends to the Slack " +"channel, you can create new threads to discuss about the new article." msgstr "" -#: ../system/subscription/plan.rst:19 +#: ../system/integrations/slack.rst:96 msgid "" -"This section gives you an overview of the available plans and their " -"functions / limits. If you require a more detailed table, check our " -"`detailed pricing table `_ for more." +"If you just want to keep track of soon escalating or already escalated " +"tickets, it will look the the following figure. Zammad changes the color in " +"front of the post so you can easily see the state of the ticket." msgstr "" -#: ../system/subscription/plan.rst:23 +#: ../system/integrations/slack.rst:102 msgid "" -"Your selection in this step will decide on the base agent price and e.g. " -"agent limits that might apply in the summary step." +"If you change the state, Zammad will also put information on what state the " +"ticket gets and (if pending state) the date until it pends. You'll also " +"recognize the color codes in front of posts on slack, as they are exact the " +"same the ticket state colors you'll see in Zammad!" msgstr "" -#: ../system/subscription/plan.rst:26 -msgid "" -"The green *Selected* button will also tell you what plan you're currently in." +#: ../system/integrations/smime/index.rst:2 +msgid "S/MIME" msgstr "" -#: ../system/subscription/plan.rst:30 +#: ../system/integrations/smime/index.rst:11 msgid "" -"Trial instances are running at Professional with 3 agents. The plan cannot " -"be changed during the trial for technical reasons, if you require more " -"agents for testing, please contact `our sales team `_ with a reason for the raise request." +"S/MIME is the most widely-supported method for secure email communication. " +"With S/MIME, you can exchange **signed** and **encrypted** messages with " +"others." msgstr "" -#: ../system/subscription/plan.rst:0 +#: ../system/integrations/smime/index.rst:15 msgid "" -"Screenshot showing three available packages for a hosted Zammad\n" -"instance" +"is proof that a message hasn't been tampered with or sent by an impersonator." msgstr "" -#: ../system/subscription/plan.rst:83 -msgid "Summary" +#: ../system/integrations/smime/index.rst:17 +msgid "" +"In other words, it guarantees a message's **integrity** and **authenticity**." msgstr "" -#: ../system/subscription/plan.rst:41 -msgid "" -"In this section you can adjust the settings of the previous selected plan." +#: ../system/integrations/smime/index.rst:22 +msgid "In other words, it guarantees **privacy** and **data security**." msgstr "" -#: ../system/subscription/plan.rst:45 -msgid "" -"Note that upgrading (more agents, higher package) is always possible, " -"however, downgrading will only happen when your billing period renews." +#: ../system/integrations/smime/index.rst:28 +msgid "Screencast demo of S/MIME features for both new tickets and replies" msgstr "" -#: ../system/subscription/plan.rst:49 +#: ../system/integrations/smime/index.rst:28 msgid "" -"Upgrading resets your billing period and existing credit will be deducted " -"from the new total." +"Once S/MIME has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " +"appear in the ticket composer." msgstr "" -#: ../system/subscription/plan.rst:58 -msgid "Billing cycle" +#: ../system/integrations/smime/index.rst:32 +msgid ":doc:`🔪 Prerequisites `" msgstr "" -#: ../system/subscription/plan.rst:53 +#: ../system/integrations/smime/index.rst:31 msgid "" -"You can choose between either monthly or yearly billing. The price per agent " -"will be cheaper if you decide for yearly billing." +"New to S/MIME? This section helps you to find certificate providers and " +"points out Limitations." msgstr "" -#: ../system/subscription/plan.rst:56 -msgid "" -"If you're still trying out things and are unsure of the right package for " -"your instance, you may want to choose monthly first and then upgrade to " -"yearly when you're sure." +#: ../system/integrations/smime/index.rst:35 +msgid ":doc:`📝 Manage Certificates `" msgstr "" -#: ../system/subscription/plan.rst:66 -msgid "Plan: (Starter|Professional|Plus) - Agents" +#: ../system/integrations/smime/index.rst:35 +msgid "Add and download certificates; configure group default behaviors." msgstr "" -#: ../system/subscription/plan.rst:61 -msgid "Choose the number of agents you require for your instance." +#: ../system/integrations/smime/index.rst:38 +msgid ":doc:`😦 Troubleshooting `" msgstr "" -#: ../system/subscription/plan.rst:63 -msgid "" -"Keep in mind that some packages may have agent limits. Depending on the " -"previous chosen package, you won't be able to exceed specific agent numbers. " -"Also note that setting less agents than currently configured is not possible." +#: ../system/integrations/smime/index.rst:38 +msgid "Took a wrong turn? About recent logs and common issues." msgstr "" -#: ../system/subscription/plan.rst:69 -msgid "Total" +#: ../system/integrations/smime/index.rst:43 +msgid "" +"For more details on how S/MIME integration works on the agent side, see the :" +"user-docs:`user docs `." msgstr "" -#: ../system/subscription/plan.rst:69 -msgid "This will be the net total you're going to be billed." +#: ../system/integrations/smime/manage-certificates.rst:2 +msgid "Manage Certificates" msgstr "" -#: ../system/subscription/plan.rst:71 +#: ../system/integrations/smime/manage-certificates.rst:4 msgid "" -"By using the *Update subscription* button, the instance package will be " -"adjusted immediately. If you didn't provide a payment method yet, Zammad " -"will request you to provide one at this point." +"S/MIME is **disabled by default**. Enable it to start adding certificates." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:10 +msgid "Dialogue to add new certificates or private keys" msgstr "" -#: ../system/subscription/plan.rst:77 +#: ../system/integrations/smime/manage-certificates.rst:10 msgid "" -"In case you're still within the trial period, this means that the trial will " -"be over immediately!" +"Manage certificates in the Admin Panel under **System > Integrations > S/" +"MIME**. Certificates may be pasted in as plain text or uploaded from a file." msgstr "" -#: ../system/subscription/plan.rst:80 -msgid "Down- or upgrading during the trial period *is not* possible." +#: ../system/integrations/smime/manage-certificates.rst:14 +msgid "Add Certificate Data" msgstr "" -#: ../system/subscription/plan.rst:0 -msgid "Screenshot showing payment options and a pricing summary" +#: ../system/integrations/smime/manage-certificates.rst:36 +msgid "Add Certificate" msgstr "" -#: ../system/subscription/plan.rst:99 -msgid "Payment method" +#: ../system/integrations/smime/manage-certificates.rst:17 +msgid "" +"Import public-key certificates for both your own organization and your " +"contacts." msgstr "" -#: ../system/subscription/plan.rst:86 -msgid "You can pay via credit card or SEPA mandate." +#: ../system/integrations/smime/manage-certificates.rst:19 +msgid "" +"You can also add a bunch of certificates in one go by providing a single " +"file with all relevant certificates." msgstr "" -#: ../system/subscription/plan.rst:91 -msgid "Credit card" +#: ../system/integrations/smime/manage-certificates.rst:22 +msgid "🕵️ **ALWAYS verify certificates in-person or over the phone!**" msgstr "" -#: ../system/subscription/plan.rst:89 +#: ../system/integrations/smime/manage-certificates.rst:24 msgid "" -"Simply follow the dialogue by clicking *authorize* and confirm -if required " -"by your bank- your consent to Zammad using your card for the payments." +"The whole point of signatures is to alert you when someone is trying to " +"pretend to be someone they're not. Never accept a certificate from someone " +"online without verifying it first." msgstr "" -#: ../system/subscription/plan.rst:95 -msgid "SEPA" +#: ../system/integrations/smime/manage-certificates.rst:28 +msgid "📇 **What about trusted certificate authorities?**" msgstr "" -#: ../system/subscription/plan.rst:94 +#: ../system/integrations/smime/manage-certificates.rst:30 msgid "" -"Provide the requested information of the bank account holder and update if " -"you're ready. You'll then receive an email with the SEPA mandate." +"In some cases (e.g. when dealing with large enterprises), you may be given a " +"certificate for an entire CA, rather than a single contact. Add it here to " +"trust *all* certificates issued by that CA." msgstr "" -#: ../system/subscription/plan.rst:97 +#: ../system/integrations/smime/manage-certificates.rst:35 msgid "" -"Technically there's also the possibility to pay via invoice, however - this " -"method only applies to a fairly low number of instances. Please contact `our " -"sales team `_ for more information." +"Commercial CAs can usually be verified online. Zammad does not include a " +"list of built-in, trusted CAs." msgstr "" -#: ../system/translations.rst:2 -msgid "Translations" +#: ../system/integrations/smime/manage-certificates.rst:57 +msgid "Add Private Key" msgstr "" -#: ../system/translations.rst:4 +#: ../system/integrations/smime/manage-certificates.rst:39 msgid "" -"Translations of Zammad are processed centrally in our `Weblate instance " -"`_. This allows non-developers to review " -"and update translation texts of the language they actually speak." +"Once you've added a public-key certificate, you can import its matching " +"private key." msgstr "" -#: ../system/translations.rst:9 +#: ../system/integrations/smime/manage-certificates.rst:42 msgid "" -"Your language is in an incomplete translation state or has typos? Please " -"consider helping us in sorting this out! All you need is either a GitHub " -"account or to register directly in our instance." +"Private keys are for **your own organization only**; never ask your contacts " +"for their private keys." msgstr "" -#: ../system/translations.rst:13 +#: ../system/integrations/smime/manage-certificates.rst:0 msgid "" -"Did you know? This is also where the documentation translations are handled. " -"🤓" +"S/MIME integration showing configured certificates and possible issues with " +"Logging" msgstr "" -#: ../system/translations.rst:15 +#: ../system/integrations/smime/manage-certificates.rst:50 msgid "" -"Have a look in our :docs:`contribution section ` in the system documentation to get started!" +"A note is displayed on certificates with a matching private key (see line 2)." msgstr "" -#: ../system/translations.rst:20 -msgid "Local Translations" +#: ../system/integrations/smime/manage-certificates.rst:52 +msgid "📤 **Certificates and private keys must be uploaded separately.**" msgstr "" -#: ../system/translations.rst:22 +#: ../system/integrations/smime/manage-certificates.rst:54 msgid "" -"Apart from these system translations, there's still local translations you " -"can manage. This is relevant if you added custom objects that require " -"translations or even custom states and priorities." +"If your certificate and private key are bundled together in the same file or " +"PEM block, import it twice (once using each button)." msgstr "" -#: ../system/translations.rst:None -msgid "Translation management screen within the admin menu" +#: ../system/integrations/smime/manage-certificates.rst:57 +msgid "Please note that bulk imports of private keys are not possible." msgstr "" -#: ../system/translations.rst:31 -msgid "Updating Translations" +#: ../system/integrations/smime/manage-certificates.rst:60 +msgid "Download Certificate Data" msgstr "" -#: ../system/translations.rst:33 +#: ../system/integrations/smime/manage-certificates.rst:62 msgid "" -"Because of how Zammad ships translations, the only way to update the system " -"translations is to update your Zammad installation. The benefit of this is " -"that you no longer need internet access during a Zammad upgrade as the " -"package has everything it requires already." +"You can download the earlier provided certificates and private keys at any " +"time from your Zammad instance." msgstr "" -#: ../system/translations.rst:39 -msgid "Translation of Custom Objects" +#: ../system/integrations/smime/manage-certificates.rst:65 +msgid "" +"Please note that passphrase-protected private keys stay protected and when " +"you download them, you have to know the passphrase to use them after " +"downloading." msgstr "" -#: ../system/translations.rst:41 -msgid "" -"No problem at all! You can customize any translation locally, even if it is " -"not initially provided by the system." +#: ../system/integrations/smime/manage-certificates.rst:73 +msgid "Dialogue to download certificates or private keys" msgstr "" -#: ../system/translations.rst:44 +#: ../system/integrations/smime/manage-certificates.rst:73 +msgid "Download stored certificates and their keys" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:78 msgid "" -"Translation is supported for a broad number of features, including but not " -"limited to custom:" +"The ticket composer will set all outgoing messages to **signed and " +"encrypted** by default (assuming the required certificates exist)." msgstr "" -#: ../system/translations.rst:47 -msgid "Object Attributes" +#: ../system/integrations/smime/manage-certificates.rst:82 +msgid "These defaults can be modified on a per-group basis:" msgstr "" -#: ../system/translations.rst:48 -msgid "Ticket Macros" +#: ../system/integrations/smime/manage-certificates.rst:None +msgid "Zammad allowing to choose the default behavior on per group basis" msgstr "" -#: ../system/translations.rst:49 -msgid "Ticket Overviews" +#: ../system/integrations/smime/manage-certificates.rst:89 +msgid "" +"Of course, agents can always manually change these settings on each email " +"they send out." msgstr "" -#: ../system/translations.rst:50 -msgid "Ticket Priorities" +#: ../system/integrations/smime/prerequisites.rst:4 +msgid "A certificate *and* private key for your own organization" msgstr "" -#: ../system/translations.rst:51 -msgid "Ticket States" +#: ../system/integrations/smime/prerequisites.rst:6 +msgid "" +"(Use this to ✒️ **sign outgoing messages** and 🔓 **decrypt incoming " +"messages**.)" msgstr "" -#: ../system/translations.rst:54 -msgid "Customizing Translations" +#: ../system/integrations/smime/prerequisites.rst:9 +msgid "" +"Certificates belonging your contacts, or their issuing certificate authority " +"(CA)" msgstr "" -#: ../system/translations.rst:56 +#: ../system/integrations/smime/prerequisites.rst:11 msgid "" -"Within the translation screen, simply click on the **New Translation** " -"button." +"(Use these to ✅ **verify incoming message signatures** and 🔒 **encrypt " +"outgoing messages**.)" msgstr "" -#: ../system/translations.rst:None -msgid "New translation dialog" +#: ../system/integrations/smime/prerequisites.rst:14 +msgid "🙋 **I'm new to S/MIME. Where can I get a certificate?**" msgstr "" -#: ../system/translations.rst:62 +#: ../system/integrations/smime/prerequisites.rst:16 msgid "" -"In the dialog you can immediately enter the exact translation source (if you " -"know it) and your custom translation text for it and click **Submit**." +"The easiest way to get certificates is to buy an annual subscription through " +"a commercial CA, such as:" msgstr "" -#: ../system/translations.rst:65 +#: ../system/integrations/smime/prerequisites.rst:19 msgid "" -"Alternatively, try to search for translation suggestions in the list below. " -"Selecting an item from the list will pre-fill the translation source for you " -"and then you can just enter your custom translation." +"`Sectigo (formerly Comodo) `_" msgstr "" -#: ../system/translations.rst:69 -msgid "" -"The target language will always default to your current language selection. " -"If you need to translate for a different language, simply change the " -"selection before submitting." +#: ../system/integrations/smime/prerequisites.rst:20 +msgid "`Secorio `_" msgstr "" -#: ../system/translations.rst:73 -msgid "" -"All your custom translations will show up in the overview table when added. " -"And they will even persist across Zammad updates!" +#: ../system/integrations/smime/prerequisites.rst:21 +msgid "`GlobalSign `_" msgstr "" -#: ../system/translations.rst:76 -msgid "" -"Make sure to reload your browser if a translated string is not displayed." +#: ../system/integrations/smime/prerequisites.rst:23 +msgid "(Zammad is not affiliated with these CAs in any way.)" msgstr "" -#: ../system/translations.rst:80 -msgid "Reverting to Original Translations" +#: ../system/integrations/smime/prerequisites.rst:25 +msgid "" +"You can also generate your own self-signed certificates, but the process is " +"complicated and usually 🙅 **involves extra work for your contacts**." msgstr "" -#: ../system/translations.rst:82 +#: ../system/integrations/smime/prerequisites.rst:29 msgid "" -"If you want to revert a custom translation to original text, simply use the " -"appropriate action within the row of the overview table." +"Bear in mind that 🤝 **S/MIME only works if the other party is using it, too." +"**" msgstr "" -#: ../system/translations.rst:85 +#: ../system/integrations/smime/prerequisites.rst:32 +msgid "Certificate and Private Key Checks on Upload" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:34 msgid "" -"Depending on the type of the translation source, the action has a slightly " -"different name:" +"The certificate and public key validation is based on the ``X509v3`` " +"extensions." msgstr "" -#: ../system/translations.rst:88 -msgid "**Reset** for customized system translations" +#: ../system/integrations/smime/prerequisites.rst:49 +msgid "Uploading a *client certificate*?" msgstr "" -#: ../system/translations.rst:89 -msgid "**Remove** for customized local translations" +#: ../system/integrations/smime/prerequisites.rst:41 +msgid "The following attributes are required then:" msgstr "" -#: ../system/translations.rst:91 -msgid "" -"In both cases, the action will remove the customized translation after a " -"confirmation." +#: ../system/integrations/smime/prerequisites.rst:39 +msgid "Subject Alternative Name (at least one email address has to be present)" msgstr "" -#: ../system/translations.rst:None -msgid "Screenshot showing the location of the Remove action" +#: ../system/integrations/smime/prerequisites.rst:40 +msgid "Key Usage (``Digital Signature`` and/or ``Key Encipherment``)" msgstr "" -#: ../system/translations.rst:99 -msgid "Inline Translations" +#: ../system/integrations/smime/prerequisites.rst:41 +msgid "Public key algorithm (either ``RSA`` or ``EC``)" msgstr "" -#: ../system/translations.rst:101 +#: ../system/integrations/smime/prerequisites.rst:43 msgid "" -"If you prefer a more hands-on approach, you can activate the inline or on-" -"screen translation feature by pressing ``ctrl`` + ``alt`` + ``t`` at any " -"time and on any screen." +"The Extended Key Usage attribute is optional. If the certificate provides " +"the named attribute, than it must contain the value ``E-mail Protection``." msgstr "" -#: ../system/translations.rst:105 +#: ../system/integrations/smime/prerequisites.rst:46 msgid "" -"All customizable translation texts will be highlighted for you on the " -"screen. Just click into the highlighted area and update the text in place." +"Please note that any usable email adress has to be prefixed with ``email:`` " +"or ``rfc822:``." msgstr "" -#: ../system/translations.rst:None -msgid "Inline translation mode activated for the Overview screen" +#: ../system/integrations/smime/prerequisites.rst:49 +msgid "The named public key algorithms are mandatory for private keys as well." msgstr "" -#: ../system/translations.rst:112 +#: ../system/integrations/smime/prerequisites.rst:54 +msgid "Uploading a *CA certificate*?" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:52 msgid "" -"When finished editing, simply press ``ctrl`` + ``alt`` + ``t`` again to " -"deactivate." +"In the case of an uploaded CA certificate, providing the value ``CA:TRUE`` " +"in the attribute *Basic Contstraints*, the previously mentioned attributes " +"are not verified." msgstr "" -#: ../system/translations.rst:117 +#: ../system/integrations/smime/prerequisites.rst:56 msgid "" -"Even though it's available on any screen, the inline translation feature " -"requires admin permissions. It works only for the current language " -"selection. If you need to translate a different language, first change the " -"language in your :user-docs:`profile settings `." +"In general, the usage of any expired (``Not After``) or not yet valid (``Not " +"Before``) certificate is denied for outgoing emails." msgstr "" -#: ../system/variables.rst:2 -msgid "Variables" +#: ../system/integrations/smime/prerequisites.rst:59 +msgid "Example certificate:" msgstr "" -#: ../system/variables.rst:4 +#: ../system/integrations/smime/prerequisites.rst:85 msgid "" -"Please note that this is just an overview of available variables. It might " -"be incomplete or variables might not be available within some functions. If " -"you're missing variables or are not sure if something is not working as " -"expected, feel free to ask over at the `Community `_." +"Please note that Zammad will distrust senders by default. This means that " +"you're always required to provide certificate data, no matter if for signing " +"or encrypting." msgstr "" -#: ../system/variables.rst:10 -msgid "" -"Variables can be called by typing ``::`` (just like text modules in the " -"frontend), as long as you're in a supported text field within the backend. " -"Zammad will display all variables being available within this context and " -"replace it to the variable as soon as you selected an entry." +#: ../system/integrations/smime/prerequisites.rst:89 +msgid "This is by design and can't be adjusted." msgstr "" -#: ../system/variables.rst:15 +#: ../system/integrations/smime/troubleshooting.rst:4 msgid "" -"You have an empty field which you referenced and it appears as ``-``? That's " -"currently working as designed - you might want to ensure that these fields " -"always have a value." +"All of the system's latest S/MIME activity is displayed in the **Recent " +"Logs** section." msgstr "" -#: ../system/variables.rst:20 -msgid "Variable Categories" +#: ../system/integrations/smime/troubleshooting.rst:11 +msgid "Sample entries of in- and outgoing S/MIME related emails." msgstr "" -#: ../system/variables.rst:31 -msgid "Wait, What About Custom Objects?" +#: ../system/integrations/smime/troubleshooting.rst:11 +msgid "" +"Logs report the status and details of all mail, both incoming and outgoing, " +"that used signing/verification or encryption/decryption." msgstr "" -#: ../system/variables.rst:33 +#: ../system/integrations/smime/troubleshooting.rst:14 msgid "" -"Good point! Of course, we can't predict what objects you might create, but " -"we can give you a hint on how to put the puzzle together to get your custom " -"values." +"This log does **not** include email sent by :doc:`triggers ` or the :doc:`scheduler `. For those, check your " +"``production.log``." +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:20 +msgid "Common Issues" +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:30 +msgid "I received a signed/encrypted email before I set up S/MIME integration" msgstr "" -#: ../system/variables.rst:36 +#: ../system/integrations/smime/troubleshooting.rst:23 msgid "" -"For this, we'll talk about the inner part of the variable (so everything " -"within ``#{}``), please put the outer part around to have a valid variable. " -"The first part of the variable name consist of the object type. Currently " -"these are:" +"No problem. Once S/MIME has been enabled and the appropriate certificates " +"have been added, agents will be prompted to retry verification/decryption on " +"matching emails." msgstr "" -#: ../system/variables.rst:41 -msgid "Ticket (``ticket``)" +#: ../system/integrations/smime/troubleshooting.rst:0 +msgid "Screenshot of user prompt to retry decryption" msgstr "" -#: ../system/variables.rst:42 -msgid "User (``user``)" +#: ../system/integrations/smime/troubleshooting.rst:38 +msgid "The 🔒 **Encrypt** button is disabled" msgstr "" -#: ../system/variables.rst:43 -msgid "Organization (``organization``)" +#: ../system/integrations/smime/troubleshooting.rst:33 +msgid "Have you added the recipient's certificate?" msgstr "" -#: ../system/variables.rst:44 -msgid "Group (``group``)" +#: ../system/integrations/smime/troubleshooting.rst:34 +msgid "Are you sure the recipient's certificate is valid?" msgstr "" -#: ../system/variables.rst:46 -msgid "" -"The second part is the name of the object. This is the name you define " -"during object creation and can be found within the object menu at any time. " -"The first and second part of a variable is divided by a point, e.g.: " -"``ticket.number`` which will in total be ``#{ticket.number}``." +#: ../system/integrations/smime/troubleshooting.rst:35 +msgid "Have you checked your ``production.log`` for more details?" msgstr "" -#: ../system/variables.rst:51 +#: ../system/integrations/smime/troubleshooting.rst:37 msgid "" -"Now, in some situations it's possible that you'll need to use a third part. " -"The best example for such a situation would be a ``select`` or ``tree-" -"select`` field which will by default return the key value, not it's display " -"name. For this, just extend your variable with ``.value``. This will result " -"in ``#{ticket.select.value}``." +"If encryption doesn't work in the composer, it won't work in :doc:`triggers " +"` or the :doc:`scheduler ` either!" msgstr "" -#: ../system/variables.rst:60 -msgid "Using Translated Variables" +#: ../system/integrations/smime/troubleshooting.rst:42 +msgid "The ✅ **Sign** button is disabled" msgstr "" -#: ../system/variables.rst:62 +#: ../system/integrations/smime/troubleshooting.rst:41 msgid "" -"If you want to use a translated variable in triggers or schedulers, you can " -"extend the placeholder like this: ``#{t(ticket.state.name)}``. The ``t`` " -"tells Zammad to search for fitting translated strings. The used output " -"language is based on the system language of Zammad which you can set in the " -"admin panel under :doc:`/settings/branding` or based on the selected locale " -"in the trigger/scheduler edit dialog." +"Have you added **both the certificate and private key** for your " +"organization?" msgstr "" -#: ../system/variables.rst:69 +#: ../system/integrations/smime/troubleshooting.rst:42 msgid "" -"A possible use-case: you want to send your customers updates on tickets via " -"trigger or scheduler which should include the state of the ticket. Using the " -"default ``#{ticket.state.name}`` (without the translation flag ``t()``) " -"would lead to the output of the original (english) name of the state." +"Does the email address on the certificate match the email address of the " +"agent/group composing the email?" msgstr "" -#: ../system/variables.rst:75 -msgid "Date and Time Formatting" +#: ../system/integrations/smime/troubleshooting.rst:45 +msgid "Error: “Fingerprint already taken”" msgstr "" -#: ../system/variables.rst:77 -msgid "" -"The system (trigger/scheduler selected) locale and timezone predefines a " -"default format of date and timestamp. This format is customizable by using " -"the ``dt()`` method." +#: ../system/integrations/smime/troubleshooting.rst:45 +msgid "Are you sure you haven't added this certificate already?" msgstr "" -#: ../system/variables.rst:79 -msgid "The method arguments are as follows:" +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Error: “❌ invalid byte sequence in UTF-8”" msgstr "" -#: ../system/variables.rst:81 -msgid "The date or timestamp variable you want to format." +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Please ensure to provide PEM formatted certificate and keys." msgstr "" -#: ../system/variables.rst:82 -msgid "The output format string." +#: ../system/integrations/smime/troubleshooting.rst:49 +msgid "Did you check if the provided file is a valid certificate or key?" msgstr "" -#: ../system/variables.rst:83 -msgid "The timezone to apply (optional)." +#: ../system/integrations/zabbix.rst:2 +msgid "Zabbix Integration" msgstr "" -#: ../system/variables.rst:86 +#: ../system/integrations/zabbix.rst:5 msgid "" -"``#{dt(ticket.updated_at, \"%A %Y-%m-%d %H:%M in the office\", \"Europe/" -"Berlin\")}``" +"This guide describes how to integrate your Zabbix 5.4 installation with " +"Zammad using the Zabbix webhook feature. This guide will provide " +"instructions on setting up a media type, a user and an action in Zabbix." msgstr "" -#: ../system/variables.rst:87 -msgid "Monday, 2024-03-18 15:31 in the office" +#: ../system/integrations/zabbix.rst:12 +msgid "Zammad with enabled HTTP Token Authentication" msgstr "" -#: ../system/variables.rst:89 -msgid "" -"If you want to use our example, make sure to paste the string above without " -"formatting (``CTRL+Shift+v``), otherwise it won't work." +#: ../system/integrations/zabbix.rst:13 +msgid "Zabbix version 5.4 or higher" msgstr "" -#: ../system/variables.rst:93 -msgid "The following table lists available format directives:" +#: ../system/integrations/zabbix.rst:16 +msgid "Setting up a Zammad" msgstr "" -#: ../system/variables.rst:99 -msgid "Parameter" +#: ../system/integrations/zabbix.rst:18 +msgid "Enable **API Token Access** in Settings > System > API." msgstr "" -#: ../system/variables.rst:102 -msgid "``%Y``" +#: ../system/integrations/zabbix.rst:20 +msgid "" +"Create a **new user** for a Zabbix alerter with an **email address** and " +"create a personal user token with **ticket.agent** permissions." msgstr "" -#: ../system/variables.rst:103 -msgid "Year with 4 digits" +#: ../system/integrations/zabbix.rst:24 +msgid "Zabbix Webhook Configuration" msgstr "" -#: ../system/variables.rst:104 -msgid "Use ``%y`` for year with 2 digits" +#: ../system/integrations/zabbix.rst:27 +msgid "Create a Global Macro" msgstr "" -#: ../system/variables.rst:105 -msgid "``%m``" +#: ../system/integrations/zabbix.rst:29 +msgid "" +"Before setting up the **Webhook**, you need to setup the global macro " +"**{$ZABBIX.URL}**, which must contain the **URL** to the **Zabbix frontend**." msgstr "" -#: ../system/variables.rst:106 -msgid "Month of year (as number with zero-padding)" +#: ../system/integrations/zabbix.rst:33 +msgid "" +"In the **Administration** > **Media types** section, import the `Template`_." msgstr "" -#: ../system/variables.rst:107 -msgid "Use ``%-m`` for month without zero-padding" +#: ../system/integrations/zabbix.rst:38 +msgid "Open the added **Zammad** media type and set:" msgstr "" -#: ../system/variables.rst:108 -msgid "``%d``" +#: ../system/integrations/zabbix.rst:40 +msgid "**zammad\\_access\\_token** to the your **Personal User Token**" msgstr "" -#: ../system/variables.rst:109 -msgid "Day of month (as number with zero-padding)" +#: ../system/integrations/zabbix.rst:41 +msgid "" +"**zammad\\_url** to the **frontend URL** of your **Zammad** installation" msgstr "" -#: ../system/variables.rst:110 -msgid "Use ``%e`` for day without zero-padding" +#: ../system/integrations/zabbix.rst:43 +msgid "**zammad\\_customer** to your **Zammad user email**." msgstr "" -#: ../system/variables.rst:111 -msgid "``%H``" +#: ../system/integrations/zabbix.rst:44 +msgid "" +"**zammad\\_enable\\_tags** to **true** or **false** to enable or disable " +"trigger tags. **Important**: if you enable tag support, each tag is set with " +"a separate request." msgstr "" -#: ../system/variables.rst:112 -msgid "Hour of day in 24h notation with zero-padding" +#: ../system/integrations/zabbix.rst:48 +msgid "" +"If you want to prioritize issues according to **severity** values in Zabbix, " +"you can define mapping parameters:" msgstr "" -#: ../system/variables.rst:113 -msgid "Use ``%k`` for hour without zero-padding" +#: ../system/integrations/zabbix.rst:51 +msgid "**severity\\_**: Zammad priority ID" msgstr "" -#: ../system/variables.rst:114 -msgid "``%I``" +#: ../system/integrations/zabbix.rst:53 +msgid "Click the **Update** button to save the **Webhook** settings." msgstr "" -#: ../system/variables.rst:115 -msgid "Hour of day in 12h notation with zero-padding" +#: ../system/integrations/zabbix.rst:55 +msgid "" +"To receive notifications in **Zammad**, you need to create a **Zabbix user** " +"and add **Media** with the **Zammad** type." msgstr "" -#: ../system/variables.rst:116 +#: ../system/integrations/zabbix.rst:58 msgid "" -"Use ``%l`` for hour without zero-padding and ``%p`` / ``%P`` for meridian " -"indicator" +"For **Send to**: enter any text, as this value is not used, but is required." msgstr "" -#: ../system/variables.rst:117 -msgid "``%M``" +#: ../system/integrations/zabbix.rst:61 +msgid "" +"For more information, use the `Zabbix documentation `_." msgstr "" -#: ../system/variables.rst:118 -msgid "Minute of hour" +#: ../system/maintenance.rst:2 +msgid "Maintenance" msgstr "" -#: ../system/variables.rst:120 -msgid "``%S``" +#: ../system/maintenance.rst:4 +msgid "" +"Zammad comes with a maintenance mode that you can use for e.g. updating the " +"instance or changing settings while restricting availability and functions." msgstr "" -#: ../system/variables.rst:121 -msgid "Second of Minute" +#: ../system/maintenance.rst:13 +msgid "Mode" msgstr "" -#: ../system/variables.rst:123 -msgid "``%A``" +#: ../system/maintenance.rst:8 +msgid "The mode setting allows you to enable or disable the maintenance mode." msgstr "" -#: ../system/variables.rst:124 -msgid "Weekday name" +#: ../system/maintenance.rst:10 +msgid "Defaults to *off*." msgstr "" -#: ../system/variables.rst:125 -msgid "Use ``%a`` for abbreviated name or ``%^A`` for uppercase name" +#: ../system/maintenance.rst:12 +msgid "" +"The maintenance mode will restrict access to administrative roles only. This " +"means agents and customers are logged off." msgstr "" -#: ../system/variables.rst:126 -msgid "``%B``" +#: ../system/maintenance.rst:23 +msgid "@Login" msgstr "" -#: ../system/variables.rst:127 -msgid "Month name" +#: ../system/maintenance.rst:16 +msgid "" +"This setting allows you to provide a login message within a green banner " +"above the login screen. Click into the green banner in the settings page to " +"adjust your message. To activate the message, activate the *@Login* setting." msgstr "" -#: ../system/variables.rst:128 -msgid "Use ``%b`` for abbreviated name" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing the default login message within the\n" +"settings page" msgstr "" -#: ../system/variables.rst:129 -msgid "``%U``" +#: ../system/maintenance.rst:26 +msgid "" +"Send an informative message to **all active sessions**. This comes handy to " +"inform your agents e.g. about mayor outages or to force reloads after " +"configuration changes." msgstr "" -#: ../system/variables.rst:130 -msgid "Week number of current year" +#: ../system/maintenance.rst:31 +msgid "This is the messages title (slightly bigger than the normal message)." msgstr "" -#: ../system/variables.rst:131 -msgid "Use ``%W`` for a different calculation method" +#: ../system/maintenance.rst:34 +msgid "The text you want to provide to your logged in sessions." msgstr "" -#: ../system/variables.rst:134 +#: ../system/maintenance.rst:39 +msgid "Reload application" +msgstr "" + +#: ../system/maintenance.rst:37 msgid "" -"We support the known format directives for the Ruby built-in method " -"``strftime`` of the ``DateTime`` class. For more information, see `here " -"`_." +"Selecting this option will change the message acceptance button from *Close* " +"(with nothing happening) to *Continue session*, which forces the application " +"to reload." msgstr "" -#: ../system/variables/article.rst:2 -msgid "Articles" +#: ../system/maintenance.rst:43 +msgid "" +"If you have customers that are logged in to Zammad, they'll also be notified " +"if they're active in that moment." msgstr "" -#: ../system/variables/article.rst:4 ../system/variables/config.rst:4 -#: ../system/variables/current-user.rst:4 ../system/variables/ticket.rst:4 +#: ../system/maintenance.rst:48 +msgid "Example without reload application" +msgstr "" + +#: ../system/maintenance.rst:52 msgid "" -"If you're missing variables or are not sure if something is not working as " -"expected, feel free to ask over at the `Community `_." +"Message setting within Zammad's admin settings without ticket reload " +"application setting." msgstr "" -#: ../system/variables/article.rst:6 +#: ../system/maintenance.rst:0 msgid "" -"Below you can find all available ticket article-based variables within " -"Zammad. These can be called via Triggers for example. If you're unsure if " -"Zammad does support variables at the point you're at, you can try to type " -"``::`` to check." +"Screenshot showing the send message settings without ticket\n" +"reload application set" msgstr "" -#: ../system/variables/article.rst:9 ../system/variables/config.rst:9 -#: ../system/variables/ticket.rst:9 +#: ../system/maintenance.rst:61 ../system/maintenance.rst:85 msgid "" -"The below list gives you an example what kind of data you can expect, it's " -"not intended to explain the data itself." +"The modal all other active sessions will see upon pressing *Send to clients*." msgstr "" -#: ../system/variables/article.rst:11 -msgid "Article Variables" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing modal caused by maintenance's message\n" +"without reload application ticket" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "name" +#: ../system/maintenance.rst:72 +msgid "Example with reload application" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "variable" +#: ../system/maintenance.rst:76 +msgid "" +"Message setting within Zammad's admin settings with ticket reload " +"application setting." msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "example" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing the send message settings with ticket\n" +"reload application set" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Web" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing modal caused by maintenance's message\n" +"with reload application ticket" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.web}``" +#: ../system/monitoring.rst:2 +msgid "Monitoring" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``https://zammad.com`` or empty if not set in user object" +#: ../system/monitoring.rst:4 +msgid "" +"This function is only available in self hosted instances. If you use Zammad " +"in our cloud, we are monitoring the system on our own and take steps to fix " +"potential problems directly." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > VIP" +#: ../system/monitoring.rst:11 +msgid "" +"On the monitoring page, you can see the current health state of Zammad under " +"\"*Current Status*\" at the bottom. This can be useful if you want to have a " +"look if everything is up and running. As an example, you could have a look " +"in the monitoring when you assume that some emails aren't processed from " +"Zammad." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.vip}``" +#: ../system/monitoring.rst:17 +msgid "**Can't receive an email and the monitoring response is \"healthy\"?**" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -msgid "``true`` or ``false``" +#: ../system/monitoring.rst:19 +msgid "" +"Zammad will just inform you about unprocessable emails. This is not the case " +"for oversized emails. You can adjust the maximum email size in :doc:`../" +"channels/email/settings`." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Phone" +#: ../system/monitoring.rst:24 +msgid "Monitoring API" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.phone}``" +#: ../system/monitoring.rst:26 +msgid "" +"Beside the indication in the monitoring page, you can also use an external " +"monitoring tool to monitor Zammad's health. To request the health of Zammad, " +"you need to provide the API key (token) to the external monitoring tool. You " +"can copy the token from the \"*Current Token*\" field as well as the whole " +"API endpoint of your system (\"*Health Check*\" field), in which the API " +"token is already included." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``+4930123456789`` or empty if not set in user object" +#: ../system/monitoring.rst:37 +msgid "Screenshot showing Current Token and Health Check" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Note" +#: ../system/monitoring.rst:37 +msgid "Screenshot showing Token and Health Check" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.note}``" +#: ../system/monitoring.rst:39 +msgid "" +"In addition to that, you can reset the auto-generated token to make sure " +"that already configured monitoring systems won't work anymore. So, please " +"use this \"*Reset*\" button only if you know what you do!" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Some note about user`` or empty if not set in user object" +#: ../system/monitoring.rst:44 +msgid "Example Output" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Mobile" +#: ../system/monitoring.rst:0 +msgid "No issues found" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.mobile}``" +#: ../system/monitoring.rst:48 ../system/monitoring.rst:60 +msgid "**Indicator in Zammad**:" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Login" +#: ../system/monitoring.rst:0 +msgid "Screenshot showing monitoring with no issues" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.login}``" +#: ../system/monitoring.rst:54 ../system/monitoring.rst:66 +msgid "**API response**::" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -#: ../system/variables/ticket.rst:1 -msgid "``jdoe``" +#: ../system/monitoring.rst:0 +msgid "Issues were found" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Lastname" +#: ../system/monitoring.rst:0 +msgid "Screenshot showing monitoring with issues" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.lastname}``" +#: ../system/objects.rst:2 +msgid "Objects" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -#: ../system/variables/ticket.rst:1 -msgid "``Doe`` or empty if not set" +#: ../system/objects.rst:4 +msgid "" +"In Zammad you can add your own fields to tickets, users, organizations and " +"even groups (these are called \"objects\"). This can be useful if you need " +"to add further information to a ticket or any other object in Zammad and the " +"information doesn't fit in any existing field." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Firstname" +#: ../system/objects.rst:11 +msgid "" +"Try to avoid deleting attributes (and disable them instead) as Zammad might " +"run into unexpected conditions if they are referenced somewhere." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.firstname}``" +#: ../system/objects.rst:16 +msgid "" +"Here's an overview of object attributes. On the upper right you can add new " +"attributes. By default, there will be no custom fields - standard attributes " +"will be grayed out, you can't delete or change those. You can edit custom " +"attributes (they are displayed in black font and have a trash bin on the " +"right side) just by clicking on them." msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "``Joe`` or empty if not set" +#: ../system/objects.rst:24 +msgid "" +"Attributes you add to Zammad, no matter if they have default values or not, " +"will not update existing information. This means a new ticket field " +"technically will be empty unless you populate it." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Fax" +#: ../system/objects.rst:28 +msgid "" +"Especially in ticket scope this also means that newly added attributes will " +"be indicated as \"changed\" to agents that view the ticket. This may " +"interfere with Zammad's tabs behavior." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.fax}``" +#: ../system/objects.rst:40 +msgid "Ordering Attributes" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Email" +#: ../system/objects.rst:42 +msgid "" +"Since Zammad introduced :doc:`/system/core-workflows` the need to have a " +"custom positioning for attributes has become more important than ever." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.email}``" +#: ../system/objects.rst:45 +msgid "" +"To adjust the position of such an attribute, simply click on the attribute " +"entry in question, scroll down and adjust the position number. Please note " +"that you cannot change the positioning of default attributes." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``jdoe@example.com``" +#: ../system/objects.rst:49 +msgid "" +"In case two attributes have the same position value, Zammad will sort " +"alphabetically by name automatically." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Department" +#: ../system/objects.rst:None +msgid "" +"Screenshot showing custom attribute entries ordered in between default ones" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.department}``" +#: ../system/objects.rst:56 +msgid "Updating Database After Adding or Editing Attributes" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Sales`` or empty if not set in user object" +#: ../system/objects.rst:58 +msgid "" +"When adding or changing attributes, Zammad will not apply the changes " +"instantly, but instead shows you the changed attributes first. If you're " +"ready to go, just click on \"Update database\" to apply the changes to " +"Zammad. If you made a mistake or just want to discard your changes, click " +"\"Discard changes\"." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Address" +#: ../system/objects.rst:64 +msgid "" +"After applying the changes with \"Update Database\", a restart of Zammad is " +"**mandatory**. If you don't perform it, you may experience unexpected " +"behavior or even errors. You may want to do this kind of configuration " +"during maintenance windows." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.address}``" +#: ../system/objects.rst:72 +msgid "" +"Changes on objects require you to update the database to apply these changes." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Some street 1, 12345 Berlin`` or empty if not set in user object" +#: ../system/objects.rst:75 +msgid "**🤓 Service restarts can be automated**" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated" +#: ../system/objects.rst:0 +msgid "Hosted environments automatically restart for you." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_at}``" +#: ../system/objects.rst:0 +msgid "" +"If you're using a self-hosted installation you can use :docs:`environment " +"variables `" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``2019-10-08 15:24:47 UTC``" +#: ../system/objects.rst:82 +msgid "System Attributes" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Type > Name" +#: ../system/objects.rst:84 +msgid "" +"Zammad comes with pre-configured attributes. Some of them can't be edited " +"via UI (or at all). This is required for proper operation of Zammad and not " +"a bug." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.type.name}``" +#: ../system/objects.rst:90 +msgid "Ticket State" msgstr "" -#: ../system/variables/article.rst:1 +#: ../system/objects.rst:92 msgid "" -"``email`` (`list of article types `_)" +"If the pre-configured states aren't enough for you or you want to change " +"them, you can do so by clicking on the cogwheel icon in the state row in the " +"ticket tab. But you should be careful when changing pre-configured states. " +"This can lead to unwanted behavior in some cases." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > To" +#: ../system/objects.rst:None +msgid "Screenshot showing highlighted ticket state attribute" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.to}``" +#: ../system/objects.rst:122 +msgid "Handling of states" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``helpdesk@example.com``" +#: ../system/objects.rst:102 +msgid "" +"In the state configuration screen, you can add new states, disable states or " +"change states." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > TicketID" +#: ../system/objects.rst:0 +msgid "Screenshot showing table of default ticket states" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.ticket_id}``" +#: ../system/objects.rst:110 +msgid "" +"To add a new state, click on the \"New Ticket State\" button in the top " +"right corner. To change an existing state, simply click on the affected " +"state. This opens an edit dialog." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``1`` (not ticket number)" +#: ../system/objects.rst:114 +msgid "" +"You can also clone a state or set them to \"Default for new tickets\" or " +"\"Default for follow-ups\" by clicking on the ⁝ action button and select the " +"desired function." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Subject" +#: ../system/objects.rst:118 +msgid "" +"*Default for new tickets* means that this state is used for every newly " +"created ticket." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.subject}``" +#: ../system/objects.rst:121 +msgid "" +"*Default for follow-ups* means that this state is used if the ticket is re-" +"opened after it was closed." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``My amazing subject``" +#: ../system/objects.rst:171 +msgid "Ticket state in detail" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Sender > Name" +#: ../system/objects.rst:125 +msgid "" +"Below you can find a description for each field and option. Please head over " +"to the :ref:`example ` to see the edit dialog." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.sender.name}``" +#: ../system/objects.rst:129 +msgid "" +"This is the name of the state and what you and your agents are seeing when " +"choosing a state somewhere (e.g. in tickets, trigger configuration)." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Customer``, ``Agent`` or ``System``" +#: ../system/objects.rst:137 +msgid "" +"There are different state types you can choose from. By default, Zammad " +"comes with one state per state type." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Visibility" +#: ../system/objects.rst:140 +msgid "" +"**new**: for states for tickets that are new and it hasn't been worked on " +"them" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.internal}``" +#: ../system/objects.rst:142 +msgid "" +"**open**: for states for tickets that are in progress and agents are working " +"on them" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``false`` or ``true`` (false if not internal)" +#: ../system/objects.rst:144 +msgid "**merged**: for states for tickets that are merged with other tickets" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > From" +#: ../system/objects.rst:145 +msgid "" +"**pending reminder**: for states for tickets that are in progress and you " +"want to set a reminder. (default example: *pending reminder*)" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.from}``" +#: ../system/objects.rst:147 +msgid "" +"**pending action**: for states for tickets that are waiting for a specified " +"time and then change their state (default example: *pending close*)" msgstr "" -#: ../system/variables/article.rst:1 +#: ../system/objects.rst:150 msgid "" -"``Joe Doe `` may differ, depends on ``FROM`` of send mail" +"**closed**: for states for tickets that are finished and do not need to be " +"processed further" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Web" +#: ../system/objects.rst:153 +msgid "" +"⚠️ Choosing the correct state type is important! If you are in doubt, have a " +"look on the default states and their types!" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.web}``" +#: ../system/objects.rst:158 +msgid "Ignore escalation" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > VIP" +#: ../system/objects.rst:157 +msgid "" +"Here you can define whether tickets of this state will count to escalation " +"time or not." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.vip}``" +#: ../system/objects.rst:161 +msgid "" +"You can create a note for the state to inform other admins about the state. " +"This has no effect on tickets." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Phone" +#: ../system/objects.rst:165 +msgid "Set the state to *active* or *inactive*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.phone}``" +#: ../system/objects.rst:167 +msgid "" +"it is technically possible to set all states to inactive. To keep Zammad " +"working in such a case, the inactive flag of one of the states is ignored." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Note" +#: ../system/objects.rst:194 +msgid "Ticket state example" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.note}``" +#: ../system/objects.rst:174 +msgid "" +"Let's assume we want to create a new state which indicates that the ticket " +"has to wait for a response of a third party (e.g. service contractor or " +"manufacturer) and we want to to be able to set a reminder." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Mobile" +#: ../system/objects.rst:178 +msgid "" +"First we give the new state a proper name. In this example we call it " +"\"waiting for manufacturer\"." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.mobile}``" +#: ../system/objects.rst:181 +msgid "" +"As state type we choose \"pending reminder\". This indicates that the ticket " +"is still open and we can set a reminder. This reminder can be useful if our " +"manufacturer sometimes isn't responding or we want to remind him to give us " +"an answer." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Login" +#: ../system/objects.rst:186 +msgid "" +"We choose \"no\" for \"ignore escalation\" because we want to escalate the " +"tickets even if we are waiting on the manufacturer's feedback." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.login}``" +#: ../system/objects.rst:189 +msgid "The **result** in the creation dialog will look like this:" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Lastname" +#: ../system/objects.rst:0 +msgid "Screenshot showing ticket state creation dialog with example" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.lastname}``" +#: ../system/objects.rst:199 +msgid "Ticket Priority" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Firstname" +#: ../system/objects.rst:201 +msgid "" +"If the pre-configured priorities aren't enough for you or you want to change " +"them, you can do so by clicking on the cogwheel icon in the priority row in " +"the ticket tab:" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.firstname}``" +#: ../system/objects.rst:None +msgid "Screenshot showing highlighted ticket priority attribute" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Fax" +#: ../system/objects.rst:226 +msgid "Handling of priorities" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.fax}``" +#: ../system/objects.rst:210 +msgid "" +"In the priority configuration screen, you can add new priorities, disable " +"priorities or change priorities." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Email" +#: ../system/objects.rst:0 +msgid "Screenshot showing table of default ticket priorities" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.email}``" +#: ../system/objects.rst:218 +msgid "" +"To add a new priority, click on the \"New Priority\" button in the top right " +"corner. To change an existing priority, simply click on the affected " +"priority. This opens an edit dialog." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Department" +#: ../system/objects.rst:222 +msgid "" +"You can also clone a priority or set them to \"Default for new tickets\" by " +"clicking on the ⁝ action button and select the desired function." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.department}``" +#: ../system/objects.rst:225 +msgid "" +"*Default for new tickets* means that this priority is used for every newly " +"created ticket." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Address" +#: ../system/objects.rst:248 +msgid "Priorities in detail" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.address}``" +#: ../system/objects.rst:229 +msgid "Below you can find a description for each field and option." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created" +#: ../system/objects.rst:232 +msgid "" +"This is the name of the priority and what you and your agents are seeing " +"when choosing a priority somewhere (e.g. in tickets, trigger configuration)." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_at}``" +#: ../system/objects.rst:242 +msgid "Highlight color" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Cc" +#: ../system/objects.rst:237 +msgid "" +"Switch between *Low priority* (light blue), *High priority* (red) and - " +"(default). This affects the displayed color for ticket titles in overviews." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.cc}``" +#: ../system/objects.rst:241 +msgid "The color options are currently limited to the mentioned options." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``jdoe@example.com, company@example.com``" +#: ../system/objects.rst:245 +msgid "" +"You can create a note for the priority to inform other admins about the " +"priority. This has no effect on tickets." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Text" +#: ../system/objects.rst:249 +msgid "Set the priority to *active* or *inactive*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.body}``" +#: ../system/objects/external-data-source-example.rst:2 +msgid "External Data Source" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Test`` without formatting (plain)" +#: ../system/objects/external-data-source-example.rst:4 +msgid "" +"We assume you already had a look on :doc:`types` where you can find a " +"description of the individual fields." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article Text as HTML (not referenced)" +#: ../system/objects/external-data-source-example.rst:7 +msgid "" +"To reproduce this example, choose a category you want to add a custom field, " +"click on *New Attribute* and select *External data source field* under " +"*Format*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.body_as_html}``" +#: ../system/objects/external-data-source-example.rst:11 +msgid "" +"Our example story is to fetch data from an external product database. We " +"want to add our products to the tickets so that the products can be searched " +"and chosen from a list and also create a link to the product website." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Test`` with formatting" +#: ../system/objects/external-data-source-example.rst:16 +msgid "Base configuration" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "Ticket > Article#" +#: ../system/objects/external-data-source-example.rst:None +msgid "Initial steps to configure external data source object type" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "``#{ticket.article_count}``" +#: ../system/objects/external-data-source-example.rst:25 +msgid "Name: *product*" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``1`` number of ticket articles" +#: ../system/objects/external-data-source-example.rst:26 +msgid "Display: *Product*" msgstr "" -#: ../system/variables/config.rst:2 -msgid "Config" +#: ../system/objects/external-data-source-example.rst:29 +msgid "External data source configuration" msgstr "" -#: ../system/variables/config.rst:6 +#: ../system/objects/external-data-source-example.rst:31 msgid "" -"Below you'll find config related variables. These hold useful configuration " -"information that you can use within e.g. triggers to show necessary " -"information to your customer." +"First, enter the search URL making sure it contains ``#{search.term}`` as a " +"parameter:" msgstr "" -#: ../system/variables/config.rst:11 -msgid "Config Variables" +#: ../system/objects/external-data-source-example.rst:34 +msgid "**Example:** ``https://dummyjson.com/products/search?q=#{search.term}``" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Fully Qualified Domain Name" +#: ../system/objects/external-data-source-example.rst:36 +msgid "" +"After that, head down to the preview section and enter a search input for " +"the external data source." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.fqdn}``" +#: ../system/objects/external-data-source-example.rst:39 +msgid "**Example:** ``mac``" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``zammad.example.com``" +#: ../system/objects/external-data-source-example.rst:41 +msgid "Then you can find a preview of the response data below:" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Ticket Hook" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of JSON response based on search term" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.ticket_hook}``" +#: ../system/objects/external-data-source-example.rst:48 +msgid "" +"We recommend using the preview to have a look on the structure. There is a " +"top-level element called ``products``. One level below, you can find the " +"attributes ``id`` and ``title``." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``Ticket#``" +#: ../system/objects/external-data-source-example.rst:52 +msgid "**Search result response based on search from example:**" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > HTTP type" +#: ../system/objects/external-data-source-example.rst:119 +msgid "" +"To tell the remote system that the desired data is located below the " +"``products`` level, you have to put it in the field *Search result list key*." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.http_type}``" +#: ../system/objects/external-data-source-example.rst:122 +msgid "" +"After inserting ``products`` in the mentioned field, you get an extended " +"preview. You can find an additional box *Search result list* with a JSON " +"structure. This is the same response as before but stripped from the upper " +"``products`` element by the external data source." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``https`` or ``http``" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of JSON response search result list" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > SystemID" +#: ../system/objects/external-data-source-example.rst:132 +msgid "" +"Now you need to provide the keys for the search result values and labels. As " +"already mentioned, we are looking for the ``id`` and the ``title`` of our " +"products. If you haven't already, it is now a good time to look at the " +"preview of the *Search result list*." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.system_id}``" +#: ../system/objects/external-data-source-example.rst:197 +msgid "" +"After locating our two keys, we insert them in *search result value key* " +"(``id``) and in *Search result label key* (``title``)." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``31`` (value between 1 and 99)" +#: ../system/objects/external-data-source-example.rst:200 +msgid "" +"Basically, we configured the external data source already and we can see a " +"table in the preview section:" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Organization" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of product table based on search term" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.organization}``" +#: ../system/objects/external-data-source-example.rst:208 +msgid "" +"According to our example story, now just the *Link template* is missing." msgstr "" -#: ../system/variables/config.rst:1 +#: ../system/objects/external-data-source-example.rst:210 msgid "" -"``Zammad GmbH`` value set in `Branding `_" +"Please note that this is an optional feature. If you don't want to use such " +"links, of course you don't have to configure it." msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Product Name" +#: ../system/objects/external-data-source-example.rst:213 +msgid "" +"We can add now an address where additional product information can be found." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.product_name}``" +#: ../system/objects/external-data-source-example.rst:215 +msgid "Example: ``https://your_domain.com/q=#{ticket.product}``" msgstr "" -#: ../system/variables/config.rst:1 -msgid "" -"``Helpdesk`` value set in `Branding `_" +#: ../system/objects/external-data-source-example.rst:217 +msgid "In the example, the parameter means:" +msgstr "" + +#: ../system/objects/external-data-source-example.rst:219 +msgid "``#{}``: \"Frame\" for the insertion of information" msgstr "" -#: ../system/variables/current-user.rst:2 -msgid "Current User" +#: ../system/objects/external-data-source-example.rst:220 +msgid "``ticket``: object level, where you create your custom object" msgstr "" -#: ../system/variables/current-user.rst:6 -msgid "" -"Current user variables always return values of the current user that caused " -"e.g. a trigger to run." +#: ../system/objects/external-data-source-example.rst:221 +msgid "``product``: name of the (custom) object" msgstr "" -#: ../system/variables/current-user.rst:8 +#: ../system/objects/external-data-source-example.rst:223 msgid "" -"Due to the above fact, these variables are often not (yet) set or available " -"for usage." +"After configuring your *Link template*, there will be another column in the " +"preview. Hovering on the icons in the *Link* column will show you where it " +"forwards you." msgstr "" -#: ../system/variables/current-user.rst:10 +#: ../system/objects/external-data-source-example.rst:232 msgid "" -"In situations where e.g. schedulers or triggers run, this most likely is " -"nothing you want to use." -msgstr "" - -#: ../system/variables/current-user.rst:13 -msgid "Current User Variables" +"In our example, one of the links looks like: https://your_domain.com/q=6, " +"where the 6 is the product id." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Web" +#: ../system/objects/external-data-source-example.rst:235 +msgid "You can find more information regarding the URL in :doc:`types`." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.web}``" +#: ../system/objects/includes/adding-values-hint.include.rst:3 +msgid "" +"Adding values can be tricky for first timers, don't forget to press \"➕ " +"Add\" after typing your values. Otherwise you may loose a value." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``https://zammad.org`` or empty if not set" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:1 +#: ../system/objects/includes/reposition-values.include.rst:1 +msgid "**↕️ This field type allows the positioning of its values ↔️**" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > VIP" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:3 +msgid "" +"In order to re-arrange the field values, first edit the field. Then you can " +"use ☰ to drag the values in question to the correct position. If you want to " +"change the layer depth, double click on ☰. With it you can cycle through the " +"available layers." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.vip}``" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:8 +msgid "When you're ready, submit your changes to save the object attribute." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``false`` or ``true``" +#: :0 ../system/objects/types.rst:0 +msgid "" +"Screencast showing how to re-position values on tree select like\n" +"fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Web" +#: ../system/objects/includes/reposition-values.include.rst:3 +msgid "" +"In order to re-arrange the field values, edit the field and scroll below the " +"values. Make sure to tick the option \"Use custom option sort\"." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.web}``" +#: ../system/objects/includes/reposition-values.include.rst:8 +msgid "" +"If you do not tick this field, all manual positioning you did above will be " +"lost upon saving! ☠️" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > VIP" +#: ../system/objects/includes/reposition-values.include.rst:11 +msgid "" +"Now use ☰ to drag the values in question to the correct position. When " +"you're ready, submit your changes to save the object attribute." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.vip}``" +#: :0 ../system/objects/types.rst:0 +msgid "Screencast showing how to re-position values" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Phone" +#: ../system/objects/includes/url-template-hint.include.rst:3 +msgid "" +"This field allows using :ref:`URL fields (Link Templates) `." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.phone}``" +#: ../system/objects/permissions.rst:2 +msgid "Attribute Permissions" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``004930123456789`` or empty if not set" +#: ../system/objects/permissions.rst:7 +msgid "" +"In the object attributes configuration you can define if a field is shown " +"and if the input in the field is mandatory, separated by different screens " +"and for different :doc:`roles/permissions `." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Note" +#: ../system/objects/permissions.rst:17 +msgid "Screenshot shows object attribute permission table" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.note}``" +#: ../system/objects/permissions.rst:17 +msgid "" +"Some of the possible permissions and screen options for a user object " +"attribute." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Some note to this user`` or empty if not set" +#: ../system/objects/permissions.rst:19 +msgid "" +"Based on the object context (ticket, agent, organization, user), the " +"selectable roles (to be precise: the required permissions) and screens " +"differ. Be aware that these settings aren't affecting data creation via " +"other channels than the UI." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Mobile" +#: ../system/objects/permissions.rst:24 +msgid "" +"If you want to have further customization possibilities, you should have a " +"look at the :doc:`core workflows `." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.mobile}``" +#: ../system/objects/permissions.rst:28 +msgid "Screens" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``0049176123456789`` or empty if not set" +#: ../system/objects/permissions.rst:30 +msgid "" +"In the table below you can find an overview about the different permissions " +"and the available screens Zammad distinguishes between." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Login" +#: ../system/objects/permissions.rst:37 +msgid "Screen" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.login}``" +#: ../system/objects/permissions.rst:38 +msgid "Available for" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Lastname" +#: ../system/objects/permissions.rst:40 +msgid "create" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.lastname}``" +#: ../system/objects/permissions.rst:41 ../system/objects/permissions.rst:52 +#: ../system/objects/permissions.rst:59 ../system/objects/permissions.rst:73 +msgid "admin.user" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Firstname" +#: ../system/objects/permissions.rst:42 ../system/objects/permissions.rst:53 +#: ../system/objects/permissions.rst:60 +msgid "admin.organization" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.firstname}``" +#: ../system/objects/permissions.rst:43 ../system/objects/permissions.rst:54 +#: ../system/objects/permissions.rst:61 +msgid "admin.group" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``John`` or empty if not set" +#: ../system/objects/permissions.rst:44 +msgid "Creation dialog for not yet existing data" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Fax" +#: ../system/objects/permissions.rst:45 +msgid "create_middle" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.fax}``" +#: ../system/objects/permissions.rst:46 ../system/objects/permissions.rst:50 +#: ../system/objects/permissions.rst:57 ../system/objects/permissions.rst:66 +#: ../system/objects/permissions.rst:70 +msgid "ticket.customer" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``004930123464789`` or empty if not set" +#: ../system/objects/permissions.rst:47 ../system/objects/permissions.rst:51 +#: ../system/objects/permissions.rst:58 ../system/objects/permissions.rst:69 +msgid "ticket.agent" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Email" +#: ../system/objects/permissions.rst:48 +msgid "Ticket create dialog (middle section)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.email}``" +#: ../system/objects/permissions.rst:49 +msgid "edit" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``jdoe@customer.tld``" +#: ../system/objects/permissions.rst:55 +msgid "Editing dialog for already existing data" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Department" +#: ../system/objects/permissions.rst:56 +msgid "view" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.department}``" +#: ../system/objects/permissions.rst:62 +msgid "View-only dialog for already existing data" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Sales`` or empty if not set" +#: ../system/objects/permissions.rst:64 +msgid "(e.g. user or organization from search)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Avatar" +#: ../system/objects/permissions.rst:65 +msgid "signup" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.avatar(60,60)}``" +#: ../system/objects/permissions.rst:67 +msgid "Sign-up screen for new customers" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "avatar picture with width and height in pixel (e.g. 60,60)" +#: ../system/objects/permissions.rst:68 +msgid "invite_customer" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Address" +#: ../system/objects/permissions.rst:71 +msgid "" +"Customer invitation screen (from :doc:`First Steps ` area)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.address}``" +#: ../system/objects/permissions.rst:72 +msgid "invite_agent" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Some street 1, 12345 Berlin`` or empty if not set" +#: ../system/objects/permissions.rst:74 +msgid "" +"Agent invitation screen (from :doc:`First Steps ` area)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated at" +#: ../system/objects/permissions.rst:78 +msgid "Screen Options" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_at}``" +#: ../system/objects/permissions.rst:80 +msgid "" +"For the different screens you can select \"show\" and \"required\" options." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC``" +#: ../system/objects/permissions.rst:82 +msgid "**shown:** Show (check) or hide (uncheck) a field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Phone" +#: ../system/objects/permissions.rst:83 +msgid "" +"**required:** Set a field to mandatory (check). Forces users (via UI and " +"API) to populate the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.phone}``" +#: ../system/objects/types.rst:7 +msgid "Example external data source" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Shared organization" +#: ../system/objects/types.rst:2 +msgid "Attribute types" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.shared}``" +#: ../system/objects/types.rst:4 +msgid "" +"When adding a new object attribute, you can choose between the following " +"attribute types." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Note" +#: ../system/objects/types.rst:14 +msgid "" +"You cannot change the attribute format / type as soon as it is applied. If " +"you no longer need an object attribute, consider disabling it instead of " +"removing." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.note}``" +#: ../system/objects/types.rst:18 +msgid "**What about the translation of my attributes?**" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``A note to the organization of the user`` or empty if not set" +#: ../system/objects/types.rst:20 +msgid "" +"For some attribute types you can decide if they should be translatable or " +"not. To be precise, it works only for the selectable fields because the " +"possible choices are known and limited. For the following attribute types, " +"you can set the translatable flag:" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Name" +#: ../system/objects/types.rst:25 +msgid "*Boolean field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.name}``" +#: ../system/objects/types.rst:26 +msgid "*Single selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``Zammad GmbH``" +#: ../system/objects/types.rst:27 +msgid "*Multiple selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Domain based assignment" +#: ../system/objects/types.rst:28 +msgid "*Single tree selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.domain_assignment}``" +#: ../system/objects/types.rst:29 +msgid "*Multiple tree selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Domain" +#: ../system/objects/types.rst:31 +msgid "" +"For these types, you can find an additional field *Translate field contents*:" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.domain}``" +#: ../system/objects/types.rst:0 +msgid "Screenshot showing translatable attribute types" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``zammad.com`` or empty if not set" +#: ../system/objects/types.rst:38 +msgid "Screenshot with example of translatable attribute type" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > VIP" +#: ../system/objects/types.rst:45 +msgid "Boolean field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.vip}``" +#: ../system/objects/types.rst:41 +msgid "" +"Provides a drop-down field with display values for ``true`` and ``false``. " +"Setting a default is mandatory." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Note" +#: ../system/objects/types.rst:0 +msgid "Available settings for Boolean fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.note}``" +#: ../system/objects/types.rst:55 +msgid "Date field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Mobile" +#: ../system/objects/types.rst:48 +msgid "Provides a date picker field and does not allow default values." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.mobile}``" +#: ../system/objects/types.rst:52 +msgid "Default time diff (hours)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Login" +#: ../system/objects/types.rst:51 +msgid "" +"This setting helps the user by highlighting the day from now plus the " +"provided value. It *does not* pre-fill the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.login}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Date fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Lastname" +#: ../system/objects/types.rst:73 +msgid "Date & time field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.lastname}``" +#: ../system/objects/types.rst:58 +msgid "Provides a date and time picker – does not allow default values" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Firstname" +#: ../system/objects/types.rst:62 +msgid "Allow future" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.firstname}``" +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the future." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Fax" +#: ../system/objects/types.rst:66 +msgid "Allow past" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.fax}``" +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the past." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Email" +#: ../system/objects/types.rst:70 +msgid "Default time diff (minutes)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.email}``" +#: ../system/objects/types.rst:69 +msgid "" +"This setting helps the user by highlighting the day from now plus the " +"provided value. It does not pre-fill the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Department" +#: ../system/objects/types.rst:0 +msgid "Available settings for Date & time fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.department}``" +#: ../system/objects/types.rst:86 +msgid "Integer field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Web" +#: ../system/objects/types.rst:76 +msgid "" +"Provides an input field that allows integer usage only. You may define a " +"default value. You cannot enforce comma separation." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.web}``" +#: ../system/objects/types.rst:80 +msgid "Minimal" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > VIP" +#: ../system/objects/types.rst:80 +msgid "The minimal value the field accepts." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.vip}``" +#: ../system/objects/types.rst:83 +msgid "Maximal" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Phone" +#: ../system/objects/types.rst:83 +msgid "The maximum value the field accepts." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.phone}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Integer fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Note" +#: ../system/objects/types.rst:99 +msgid "Multiple selection field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.note}``" +#: ../system/objects/types.rst:89 +msgid "" +"Provides a selection field that allows the selection of one or more out of " +"several. This field does allow setting a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Mobile" +#: ../system/objects/types.rst:0 +msgid "Available settings for Multiple selection fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.mobile}``" +#: ../system/objects/types.rst:112 +msgid "Single selection field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Login" +#: ../system/objects/types.rst:102 +msgid "" +"Provides a drop-down field that allows selection of one value out of " +"several. This field does allow setting a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.login}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Single selection fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Lastname" +#: ../system/objects/types.rst:142 +msgid "Textarea field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.lastname}``" +#: ../system/objects/types.rst:115 +msgid "" +"Provides a text area input field (multiple lines) and thus allows e.g. new " +"lines. You can set a default field value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Firstname" +#: ../system/objects/types.rst:120 +msgid "" +"Please note that this field *does not* support text formatting or HTML " +"content (rich text)." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.firstname}``" +#: ../system/objects/types.rst:123 +msgid "**🥵 This field can consume a lot of visual space**" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Fax" +#: ../system/objects/types.rst:125 +msgid "" +"Depending on where you use this field type, it may use a lot of visual space " +"if you provide a lot of text. This may be an issue to work with." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.fax}``" +#: ../system/objects/types.rst:130 +msgid "Default" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Email" +#: ../system/objects/types.rst:129 +msgid "" +"The here provided text will be shown within the text area field or new data " +"sets." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.email}``" +#: ../system/objects/types.rst:134 ../system/objects/types.rst:160 +msgid "Maxlength" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Department" +#: ../system/objects/types.rst:0 ../system/objects/types.rst:160 +msgid "You can pick the maximum length of the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.department}``" +#: ../system/objects/types.rst:0 +msgid "The default length of this object is ``500``." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Avatar" +#: ../system/objects/types.rst:139 +msgid "Rows" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.avatar(60,60)}``" +#: ../system/objects/types.rst:0 +msgid "" +"Change the number of rows to dislay so that you can use only the space you " +"really need." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Address" +#: ../system/objects/types.rst:0 +msgid "The default number of rows is ``4``." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.address}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Textarea fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created at" +#: ../system/objects/types.rst:165 +msgid "Text field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_at}``" +#: ../system/objects/types.rst:145 +msgid "Provides a text field (one line) and allows choosing a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Avatar" +#: ../system/objects/types.rst:148 +msgid "" +"Defines the type of the input field. This allows e.g. your browser to ensure " +"that you provide the specific type." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.avatar(60,60)}``" +#: ../system/objects/types.rst:152 +msgid "Currently available:" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Address" +#: ../system/objects/types.rst:155 +msgid "Phone" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.address}``" +#: ../system/objects/types.rst:156 +msgid "Text" msgstr "" -#: ../system/variables/ticket.rst:6 -msgid "" -"Below you can find all available ticket-based variables within Zammad. These " -"can be called via Triggers for example. If you're unsure if Zammad does " -"support variables at the point you're at, you can try to type ``::`` to " -"check." +#: ../system/objects/types.rst:157 +msgid "Url *(URL fields disable link-template availability)*" msgstr "" -#: ../system/variables/ticket.rst:12 -msgid "Ticket Variables" +#: ../system/objects/types.rst:0 +msgid "Available settings for Text fields" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Web" +#: ../system/objects/types.rst:174 +msgid "Single tree selection field" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.web}``" +#: ../system/objects/types.rst:168 +msgid "" +"Provides a select-like field with up to 6 layers of options. Does not allow " +"setting a default value." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > VIP" +#: ../system/objects/types.rst:0 +msgid "Available settings for Tree Select fields" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.vip}``" +#: ../system/objects/types.rst:183 +msgid "Multiple tree selection field" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Phone" +#: ../system/objects/types.rst:177 +msgid "" +"Provides a select-like field with up to 6 layers of options allowing the " +"selection of multiple values. Does not allow setting a default value." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.phone}``" +#: ../system/objects/types.rst:302 +msgid "External Data Source field" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Note" +#: ../system/objects/types.rst:186 +msgid "" +"Provides a searchable field which fetches data from an external system. This " +"can be useful if you have data outside of Zammad and don't want to maintain " +"both data sources." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.note}``" +#: ../system/objects/types.rst:190 +msgid "The feature works as follows:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Mobile" +#: ../system/objects/types.rst:192 +msgid "" +"Zammad sends a query with a search string (free text from agent or based on " +"a variable) in a pre-defined format (\"Search URL\") to an external system." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.mobile}``" +#: ../system/objects/types.rst:195 +msgid "" +"This external system searches for matches and provides a response as a JSON " +"structure to Zammad." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Login" +#: ../system/objects/types.rst:197 +msgid "" +"Zammad just looks for the defined list and value keys, reads the content and " +"displays the value to the user. There is no search on Zammad side." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.login}``" +#: ../system/objects/types.rst:201 +msgid "" +"The usage of a PostgreSQL database for Zammad is required. In any other " +"case, Zammad will hide the external data source type and you are not able to " +"use it. If you want to use this feature, consider to :docs:`migrate your " +"database `." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Lastname" +#: ../system/objects/types.rst:205 +msgid "Currently, only ``GET`` is supported as request method." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.lastname}``" +#: ../system/objects/types.rst:206 +msgid "" +"The data structure must be in JSON format and provide the objects in an " +"array." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Firstname" +#: ../system/objects/types.rst:208 +msgid "" +"The endpoint for the external data source has to support search. On Zammad " +"side, there is no search/logic implemented; however, you can define the " +"output key and value based on the result(s) from the response (which " +"provides already filtered content based on the search)." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.firstname}``" +#: ../system/objects/types.rst:212 +msgid "" +"If you receive more results as expected, your external data source search " +"may not work properly or the structure of the URL is not correct. You should " +"get in touch with a responsible person from the external system." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Fax" +#: ../system/objects/types.rst:217 +msgid "" +"Please have a look :doc:`at our example `, where you can find a possible configuration for a public " +"dummy endpoint." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.fax}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for external data source fields" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Email" +#: ../system/objects/types.rst:242 +msgid "Search URL" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.email}``" +#: ../system/objects/types.rst:227 +msgid "" +"Set your endpoint where Zammad fetches the data. Please make sure to include " +"a valid search :doc:`variable ` as an URL parameter. " +"Example for a free text search at user input: ``#{search.term}``" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Department" +#: ../system/objects/types.rst:232 +msgid "" +"If in doubt, ask the responsible person for the external data source how " +"they expect the structure of the URL." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.department}``" +#: ../system/objects/types.rst:236 +msgid "" +"Depending on your search variable, the preview might work or not. The reason " +"is that the context might not be available and it is no bug." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Avatar" +#: ../system/objects/types.rst:239 +msgid "" +"Please also make sure to use a variable which is available in your object " +"context. For example you won't be able to search for a ticket in a user " +"object context." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.avatar(60,60)}``" +#: ../system/objects/types.rst:252 +msgid "SSL Verification" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Address" +#: ../system/objects/types.rst:245 +msgid "Here you can switch the SSL verification to no." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.address}``" +#: ../system/objects/types.rst:249 +msgid "" +"If your external data source system is using self signed certificates, " +"please have a look :doc:`here ` for " +"further information about how to handle them in Zammad, so you can keep the " +"SSL verification activated." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated at" +#: ../system/objects/types.rst:258 +msgid "HTTP Authentication" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_at}``" +#: ../system/objects/types.rst:255 +msgid "" +"If your external data source requires an authentication, you can set it " +"here. You can leave it empty or choose between *Basic Authentication* or " +"*Authentication Token* (selecting one of the two methods leads to additional " +"fields where you can enter your credentials/token)." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Title" +#: ../system/objects/types.rst:265 +msgid "Search result list key" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.title}``" +#: ../system/objects/types.rst:261 +msgid "" +"Defines the level in the JSON structure which provides the list with search " +"results. You can leave it empty, if the data is already provided as an " +"array. If you have to go deeper in the structure, you can provide a path " +"with ``.`` as separators, e.g. ``key.subkey.sub-sub-key``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "" -"``My amazing Subject`` (normally subject, can be edited within Interface and " -"thus differ)" +#: ../system/objects/types.rst:271 +msgid "Search result value key" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Accounted Time" +#: ../system/objects/types.rst:268 +msgid "" +"Defines the attribute in the structure in which your external data source " +"provides the *value* for your data. An example would be a product *number*. " +"If you have to go deeper in the structure, you can provide a path with ``.`` " +"as separators, e.g. ``key.subkey.sub-sub-key``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.time_unit}``" +#: ../system/objects/types.rst:277 +msgid "Search result label key" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``1``, ``2.75`` or empty response" +#: ../system/objects/types.rst:274 +msgid "" +"Defines the attribute in the structure in which your external data source " +"provides the *label* for your data. An example would be a product *name*. If " +"you have to go deeper in the structure, you can provide a path with ``.`` as " +"separators, e.g. ``key.subkey.sub-sub-key``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Tags" +#: ../system/objects/types.rst:280 +msgid "" +"In the preview area, you can find the following items (depending on your " +"configuration above):" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.tags}``" +#: ../system/objects/types.rst:283 +msgid "" +"**Error/hint message** (only if configuration is not complete): Zammad tells " +"you, if there is a problem and what you should change in your configuration." msgstr "" -#: ../system/variables/ticket.rst:1 +#: ../system/objects/types.rst:286 msgid "" -"Currently not available, see `Issue 2769 `_" +"**Search field**: search for an existing attribute in the data source to get " +"a preview. This is required for the fields below to show up." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > State > Name" +#: ../system/objects/types.rst:288 +msgid "" +"**Search result response** (only if configuration is not complete): here you " +"can find a syntax highlighted JSON preview of the response, based on the " +"search term you entered." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.state.name}``" +#: ../system/objects/types.rst:291 +msgid "" +"**Search result list** (only if *search result list key* is properly set): " +"output of the structure under the configured *search result list key*." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``new``, ``open``, ..." +#: ../system/objects/types.rst:294 +msgid "" +"**Preview table** (when fully configured): Zammad shows you a table which " +"includes the found items based on the search string (value, label and " +"optional link). You can use this preview if you don't have the complete data " +"structure of the external system in mind." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Priority > Name" +#: ../system/objects/types.rst:299 +msgid "" +"An example of a configured external data source field from agent perspective:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.priority.name}``" +#: ../system/objects/types.rst:0 +msgid "Screencast showing the search for a product in a ticket" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2 normal``" +#: ../system/objects/types.rst:307 +msgid "URL fields (Link-Template)" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Pending till" +#: ../system/objects/types.rst:311 +msgid "" +"This function is restricted to Text, Select and External data source types " +"only." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.pending_time}``" +#: ../system/objects/types.rst:314 +msgid "" +"Link-Templates are an amazing way to dynamically generate URLs. They allow " +"you to integrate other systems better without having to manually copy data " +"from Zammad if possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not set" +#: ../system/objects/types.rst:320 +msgid "" +"Another great way of communicating with another system may be Zammad's :doc:" +"`Webhooks `." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Web" +#: ../system/objects/types.rst:323 +msgid "" +"After filling a link-template enabled field, an URL icon will appear on its " +"right. Clicking on the icon opens a new tab." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.web}``" +#: ../system/objects/types.rst:328 +msgid "" +"Even though Zammad displays the link template within object edit and create " +"screens, the function is optional. It's only active if you populate the " +"field." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``https://zammad.com`` or empty if not set" +#: ../system/objects/types.rst:333 +msgid "" +"What's the difference between URL and text fields with link template...?!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > VIP" +#: ../system/objects/types.rst:335 +msgid "" +"Both fields have different use cases. Use ``text`` type text fields when " +"ever you have a *static* url that requires dynamic parameters. If you " +"require a drag & drop like field that you can put in any URL, use ``URL`` " +"type text fields." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.vip}``" +#: ../system/objects/types.rst:340 +msgid "" +"The difference is easier to spot when comparing the fields directly, below " +"screencast shows the result - the dynamic approach uses existing values in " +"the moment of updating to built the URL - e.g. ``https://google.com/search?" +"q=cookies`` - while the URL approach uses the actual URL of the field - e.g. " +"``https://zammad.com``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Phone" +#: ../system/objects/types.rst:None +msgid "" +"Screencast showing the differents in between URL and text type fields with " +"actual values" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.phone}``" +#: ../system/objects/types.rst:352 +msgid "How does this work...?!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Note" +#: ../system/objects/types.rst:354 +msgid "" +"As an example, let's say you have an attribute called ``amazing_attribute`` " +"and you want to open a google search directly with the input from that field." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.note}``" +#: ../system/objects/types.rst:357 +msgid "" +"Providing the link-template field below allows you to do so: ``https://www." +"google.com/search?q=#{ticket.amazing_attribute}``" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Mobile" +#: ../system/objects/types.rst:362 +msgid "" +"You can use any :doc:`Zammad variable ` as long as it's " +"available in the moment you need it." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.mobile}``" +#: ../system/objects/types.rst:365 +msgid "" +"As a result, you are redirected to Google with a search for the value of the " +"attribute, if you click on the button in the ticket (as you can see in the " +"screencast above)." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Login" +#: ../system/packages.rst:2 +msgid "Packages" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.login}``" +#: ../system/packages.rst:4 +msgid "That's the package management-area." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``agent``" +#: ../system/packages.rst:6 +msgid "Individual add-ons for Zammad can be installed and managed here." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Lastname" +#: ../system/sessions.rst:2 +msgid "Sessions" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.lastname}``" +#: ../system/sessions.rst:4 +msgid "" +"Sessions management allows reviewing currently known user sessions and " +"allows to end these. The session timeout is affected by :ref:" +"`security_session_timeout` configurations from security settings." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Mustermann`` or empty if not set" +#: ../system/sessions.rst:None +msgid "Screenshot showing Zammad's session management" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Firstname" +#: ../system/sessions.rst:13 +msgid "Zammad will provide the following information:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.firstname}``" +#: ../system/sessions.rst:16 +msgid "" +"The user account this session entry belongs to. It can be normal if a user " +"has several sessions in the list. This can be due to changed browser " +"information or if you use e.g. single sign on methods where the user does " +"not use the log off button." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Max`` or empty if not set" +#: ../system/sessions.rst:22 +msgid "Browser" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Fax" +#: ../system/sessions.rst:22 +msgid "The browser agent communicated to Zammad." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.fax}``" +#: ../system/sessions.rst:40 +msgid "Location" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Email" +#: ../system/sessions.rst:25 +msgid "" +"The anticipated location based on the users IP address. Depending on the IP " +"address the result shown may differ. This option depends on :doc:`/settings/" +"system/services`." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.email}``" +#: ../system/sessions.rst:29 +msgid "The following information can be shown:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``agent@company.tld`` or empty if not set" +#: ../system/sessions.rst:33 +msgid "IP address" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Department" +#: ../system/sessions.rst:32 +msgid "" +"Either if you set *Geo IP services* to inactive or you're using internal IP " +"address which do not provide location information." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.department}``" +#: ../system/sessions.rst:40 +msgid "Country (or Country + City)" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Support`` or empty if not set" +#: ../system/sessions.rst:36 +msgid "" +"If *Geo IP services* is enabled only. Depends on how detailed the available " +"IP address information are." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Avatar" +#: ../system/sessions.rst:39 +msgid "" +"Be aware that results can be inaccurate - this technically is not an error." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.avatar(60,60)}``" +#: ../system/sessions.rst:43 +msgid "Age" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Address" +#: ../system/sessions.rst:43 +msgid "Provides the time when the session initially has been created." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.address}``" +#: ../system/sessions.rst:50 +msgid "Update" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Shared organization" +#: ../system/sessions.rst:46 +msgid "" +"Provides the time the user used this session to open Zammad. This timestamp " +"is only updated if the user e.g. reloads, not during normal work on tickets." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.shared}``" +#: ../system/sessions.rst:50 +msgid "This timestamp is being used for the session timeout." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Note" +#: ../system/sessions.rst:53 +msgid "" +"Use the delete button to remove a single session on behalf of your user." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.note}``" +#: ../system/subscription.rst:2 +msgid "Subscription (SaaS)" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Name" +#: ../system/subscription.rst:4 +msgid "" +"The subscription settings page allows you to configure your instances " +"package and number of agents required." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.name}``" +#: ../system/subscription.rst:9 +msgid "" +"This setting section is only available for Hosted setups. If you're looking " +"for on premise support contracts, please see the `Zammad pricing page " +"`_." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Zammad GmbH`` or empty if not set" +#: ../system/subscription.rst:14 ../system/subscription.rst:34 +msgid "Plan" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Domain based assignment" +#: ../system/subscription.rst:16 +msgid "" +"Here you can set up everything affecting your instance subscription " +"functions like number of agents and package." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.domain_assignment}``" +#: ../system/subscription.rst:19 +msgid "" +"On top of the page you can find a subscription summary. You'll find the " +"number of used and available (booked) agent seats there. By using the *see " +"more* link you can also expand an agent list to see the currently configured " +"active agents. This list *does not* count accounts with admin permissions " +"only." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Domain" +#: ../system/subscription.rst:None +msgid "" +"Within subscription you can always see how many agents are still\n" +"available to add and who uses the seats." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.domain}``" +#: ../system/subscription.rst:29 +msgid "" +"Learn more on how to manage your agents in general :doc:`here `." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``domain.tld`` or empty if not set" +#: ../system/subscription.rst:36 +msgid "" +"This section gives you an overview of the available plans and their " +"functions / limits. If you require a more detailed table, check our " +"`detailed pricing table `_ for more." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > VIP" +#: ../system/subscription.rst:40 +msgid "" +"Your selection in this step will decide on the base agent price and e.g. " +"agent limits that might apply in the summary step." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.vip}``" +#: ../system/subscription.rst:43 +msgid "" +"The green *Selected* button will also tell you what plan you're currently in." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Number" +#: ../system/subscription.rst:47 +msgid "" +"Trial instances are running at Professional with 3 agents. The plan cannot " +"be changed during the trial for technical reasons, if you require more " +"agents for testing, please contact `our sales team `_ with a reason for the raise request." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.number}``" +#: ../system/subscription.rst:None +msgid "" +"Screenshot showing three available packages for a hosted Zammad\n" +"instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``31001``, ``201910731001``, ..." +#: ../system/subscription.rst:57 +msgid "" +"At the bottom of this block you can find a summary where you can adjust the " +"settings of the previous selected plan." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > ID" +#: ../system/subscription.rst:62 +msgid "" +"Note that upgrading (more agents, higher package) is always possible, " +"however, downgrading will only happen when your billing period renews." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.id}``" +#: ../system/subscription.rst:66 +msgid "" +"Upgrading resets your billing period and existing credit will be deducted " +"from the new total." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``17``, ``5281``, ..." +#: ../system/subscription.rst:75 +msgid "Billing cycle" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact (customer)" +#: ../system/subscription.rst:70 +msgid "" +"You can choose between either monthly or yearly billing. The price per agent " +"will be cheaper if you decide for yearly billing." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_customer_at}``" +#: ../system/subscription.rst:73 +msgid "" +"If you're still trying out things and are unsure of the right package for " +"your instance, you may want to choose monthly first and then upgrade to " +"yearly when you're sure." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "" -"``2019-10-07 16:25:00 UTC`` or empty if not applicable yet (Please note " -"`Ticket last contact behavior Settings `_ for this)" +#: ../system/subscription.rst:83 +msgid "Plan: (Starter|Professional|Plus) - Agents" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact" +#: ../system/subscription.rst:78 +msgid "Choose the number of agents you require for your instance." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_at}``" +#: ../system/subscription.rst:80 +msgid "" +"Keep in mind that some packages may have agent limits. Depending on the " +"previous chosen package, you won't be able to exceed specific agent numbers. " +"Also note that setting less agents than currently configured is not possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact (agent)" +#: ../system/subscription.rst:86 +msgid "Total" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_agent_at}``" +#: ../system/subscription.rst:86 +msgid "This will be the net total you're going to be billed." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable yet" +#: ../system/subscription.rst:88 +msgid "" +"By using the *Update subscription* button, the instance package will be " +"adjusted immediately. If you didn't provide a payment method yet, Zammad " +"will request you to provide one at this point." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Note" +#: ../system/subscription.rst:94 +msgid "" +"In case you're still within the trial period, this means that the trial will " +"be over immediately!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.note}``" +#: ../system/subscription.rst:97 +msgid "Down- or upgrading during the trial period *is not* possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Note about this group``" +#: ../system/subscription.rst:None +msgid "Screenshot showing payment options and a pricing summary" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Name" +#: ../system/subscription.rst:103 +msgid "Billing Information" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.name}``" +#: ../system/subscription.rst:105 +msgid "" +"You can control all billing relevant information like invoices, billing " +"address and the option to cancel your subscription." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Sales``" +#: ../system/subscription.rst:108 +msgid "" +"All adjusted billing information below only affect future invoices. If your " +"invoice was issued wrong, please contact `our sales team `_." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Follow-up possible" +#: ../system/subscription.rst:114 +msgid "Billing address" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.follow_up_possible}``" +#: ../system/subscription.rst:113 +msgid "" +"Provide your company address here, make sure to include the companies name " +"in case required. This address will be referenced on your invoice." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``no`` or ``yes``" +#: ../system/subscription.rst:118 +msgid "VAT ID" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Assign Follow-Ups" +#: ../system/subscription.rst:117 +msgid "" +"Provide your VAT ID here. If applicable your invoice will not contain German " +"VAT. Please make sure to pay the VAT in your country as required." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.follow_up_assignment}``" +#: ../system/subscription.rst:127 +msgid "Billing Email Address" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Assignment Timeout" +#: ../system/subscription.rst:121 +msgid "" +"Usually the instance owner (the person that registered the instance) will " +"receive all emails including the invoices. In case you have your own billing " +"department, you can provide their email address here." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.assignment_timeout}``" +#: ../system/subscription.rst:125 +msgid "" +"All billing relevant information will then be sent to this email address." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``20`` or empty if not configured" +#: ../system/subscription.rst:127 +msgid "Invoices are sent as attachment (PDF) to this email address." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > First response" +#: ../system/subscription.rst:129 +msgid "" +"Don't forget to press the *Update billing information* button after you " +"changed above settings." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.first_response_at}``" +#: ../system/subscription.rst:None +msgid "" +"Screenshot showing options for billing information within the\n" +"subscription menu" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Escalation at" +#: ../system/subscription.rst:137 +msgid "Payment Method" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.escalation_at}``" +#: ../system/subscription.rst:139 +msgid "You can pay via credit card or SEPA mandate." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable" +#: ../system/subscription.rst:144 +msgid "Credit card" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Web" +#: ../system/subscription.rst:142 +msgid "" +"Simply follow the dialogue by clicking *authorize credit card* and confirm -" +"if required by your bank- your consent to Zammad using your card for the " +"payments." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.web}``" +#: ../system/subscription.rst:148 +msgid "SEPA Direct Debit" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > VIP" +#: ../system/subscription.rst:147 +msgid "" +"Provide the requested information of the bank account holder and update if " +"you're ready. You'll then receive an email with the SEPA mandate." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.vip}``" +#: ../system/subscription.rst:150 +msgid "" +"Technically there's also the possibility to pay via invoice, however - this " +"method only applies to a fairly low number of instances. Please contact `our " +"sales team `_ for more information." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Phone" +#: ../system/subscription.rst:156 +msgid "Cancel Subscription" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.phone}``" +#: ../system/subscription.rst:158 +msgid "" +"Do you want to cancel your subscription? In case you no longer want to use " +"Zammad's SaaS, you can cancel your subscription by using the red *Yes, " +"please cancel my subscription* button." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Note" +#: ../system/subscription.rst:162 +msgid "" +"To cancel the description, enter the FQDN of your Zammad instance and " +"provide a reason for your cancellation." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.note}``" +#: ../system/subscription.rst:165 +msgid "" +"Your subscription will end the day after your trial or billing period ends." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Mobile" +#: ../system/subscription.rst:None +msgid "Screenshot showing subscription cancellation dialog" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.mobile}``" +#: ../system/subscription.rst:174 +msgid "" +"We will remind you about your cancelled subscription several times up front. " +"After the subscription ended all instance data will be removed. A restore " +"*is not* possible after that point!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Login" +#: ../system/subscription.rst:178 +msgid "**😖 Cancelled by accident?**" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.login}``" +#: ../system/subscription.rst:180 +msgid "" +"You can always undo the cancellation via the *Yes, undo the cancellation of " +"my subscription* button up to the last subscription day!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Lastname" +#: ../system/subscription.rst:0 +msgid "" +"Screenshot showing a red button to cancel the subscription\n" +"cancellation" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.lastname}``" +#: ../system/subscription.rst:189 +msgid "Payment History" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Firstname" +#: ../system/subscription.rst:191 +msgid "" +"The payment history will display a history of all paid invoices. At this " +"point you can also download these in case you need them again." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.firstname}``" +#: ../system/subscription.rst:196 +msgid "" +"You will only find *paid* invoices here. Invoices that are to be billed are " +"not available before the payment is completed." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Fax" +#: ../system/subscription.rst:201 +msgid "Date" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.fax}``" +#: ../system/subscription.rst:201 +msgid "Date of the invoice creation." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Email" +#: ../system/subscription.rst:204 +msgid "Amount" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.email}``" +#: ../system/subscription.rst:204 +msgid "Invoice total including VAT if applicable." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Department" +#: ../system/subscription.rst:207 +msgid "" +"Contains contract period (monthly or yearly) and hosted plan for the " +"subscription period in question." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.department}``" +#: ../system/subscription.rst:218 +msgid "Payment method / Service period" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Avatar" +#: ../system/subscription.rst:211 +msgid "" +"Used bank account or credit card as well as the subscription period the " +"invoice is about." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.avatar(60,60)}``" +#: ../system/subscription.rst:216 +msgid "" +"It might happen that the invoice date and subscription period differ. This " +"is nothing to worry about, the subscription periods will be accounted later " +"on." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Address" +#: ../system/subscription.rst:222 +msgid "Receipt" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.address}``" +#: ../system/subscription.rst:221 +msgid "" +"Use the arrow to download the invoice in question. You can download all " +"available invoices any time you need to here!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Web" +#: ../system/subscription.rst:None +msgid "Screenshot showing payment history of a hosted instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.web}``" +#: ../system/subscription.rst:229 +msgid "FAQ" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > VIP" +#: ../system/subscription.rst:233 +msgid "I set up a trial account but am missing functions to test" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.vip}``" +#: ../system/subscription.rst:232 +msgid "" +"The trial instance is running within the professional package allowing up to " +"three agents." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Phone" +#: ../system/subscription.rst:236 +msgid "Can I change package within the trial?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.phone}``" +#: ../system/subscription.rst:236 +msgid "No. As soon as the package is changed the subscription begins." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Note" +#: ../system/subscription.rst:241 +msgid "What happens to my trial instance after the trial period ended?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.note}``" +#: ../system/subscription.rst:239 +msgid "" +"Your instance will automatically be canceled for you. Please see *What " +"happens to my instance after it has been canceled?* for more." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Mobile" +#: ../system/subscription.rst:254 +msgid "What happens to my instance after it has been canceled?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.mobile}``" +#: ../system/subscription.rst:244 +msgid "That depends slightly on your instance state:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Login" +#: ../system/subscription.rst:250 +msgid "Trial instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.login}``" +#: ../system/subscription.rst:247 +msgid "" +"If you're still on trial, we will ice your instance and remind you once " +"again about your instance. We then will wait some days and remove your " +"instance from our system. This is the last time we will inform you by Email." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Lastname" +#: ../system/subscription.rst:254 +msgid "Paid instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.lastname}``" +#: ../system/subscription.rst:253 +msgid "" +"If you're a paying customer and canceled your subscription, the instance " +"removal will take place the day after your last subscription day." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Firstname" +#: ../system/subscription.rst:256 +msgid "Can removed instances be restored?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.firstname}``" +#: ../system/subscription.rst:257 +msgid "No. Once your instance has been removed, a restoration is not possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Fax" +#: ../system/system-report.rst:2 +msgid "System Report" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.fax}``" +#: ../system/system-report.rst:4 +msgid "" +"In this place you can't configure Zammad. Instead you can obtain a system " +"report about Zammad and its configuration." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Email" +#: ../system/system-report.rst:7 +msgid "" +"See the description in Zammad for an explanation. You can even find a " +"preview of the included data below the **Download** button." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.email}``" +#: ../system/system-report.rst:10 +msgid "" +"Zammad never sends this automatically to anyone. It is a manual process only " +"to provide better support based on your configuration." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Department" +#: ../system/translations.rst:2 +msgid "Translations" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.department}``" +#: ../system/translations.rst:4 +msgid "" +"Translations of Zammad are processed centrally in our `Weblate instance " +"`_. This allows non-developers to review " +"and update translation texts of the language they actually speak." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Avatar" +#: ../system/translations.rst:9 +msgid "" +"Your language is in an incomplete translation state or has typos? Please " +"consider helping us in sorting this out! All you need is either a GitHub " +"account or to register directly in our instance." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.avatar(60,60)}``" +#: ../system/translations.rst:13 +msgid "" +"Did you know? This is also where the documentation translations are handled. " +"🤓" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Address" +#: ../system/translations.rst:15 +msgid "" +"Have a look in our :docs:`contribution section ` in the system documentation to get started!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.address}``" +#: ../system/translations.rst:20 +msgid "Local Translations" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created at" +#: ../system/translations.rst:22 +msgid "" +"Apart from these system translations, there's still local translations you " +"can manage. This is relevant if you added custom objects that require " +"translations or even custom states and priorities." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_at}``" +#: ../system/translations.rst:None +msgid "Translation management screen within the admin menu" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "2019-10-07 16:25:00 UTC" +#: ../system/translations.rst:31 +msgid "Updating Translations" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Closing time" +#: ../system/translations.rst:33 +msgid "" +"Because of how Zammad ships translations, the only way to update the system " +"translations is to update your Zammad installation. The benefit of this is " +"that you no longer need internet access during a Zammad upgrade as the " +"package has everything it requires already." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.close_at}``" +#: ../system/translations.rst:39 +msgid "Translation of Custom Objects" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "2019-10-07 17:25:00 UTC" +#: ../system/translations.rst:41 +msgid "" +"No problem at all! You can customize any translation locally, even if it is " +"not initially provided by the system." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``3``, any number of articles existing in the ticket right now" +#: ../system/translations.rst:44 +msgid "" +"Translation is supported for a broad number of features, including but not " +"limited to custom:" msgstr "" -#: ../system/version.rst:2 -msgid "Version" +#: ../system/translations.rst:47 +msgid "Object Attributes" msgstr "" -#: ../system/version.rst:4 -msgid "Shows which version is currently being used on your Zammad-instance." +#: ../system/translations.rst:48 +msgid "Ticket Macros" msgstr "" -#: ../manage/roles/admin-permissions.rst:53 -msgid "``admin.checklist``" +#: ../system/translations.rst:49 +msgid "Ticket Overviews" msgstr "" -#: ../manage/roles/admin-permissions.rst:54 -msgid ":doc:`Manage > Checklist `" +#: ../system/translations.rst:50 +msgid "Ticket Priorities" msgstr "" -#: ../manage/roles/admin-permissions.rst:83 -msgid "``admin.channel_whatsapp``" +#: ../system/translations.rst:51 +msgid "Ticket States" msgstr "" -#: ../manage/roles/admin-permissions.rst:84 -msgid ":doc:`Channels > Whatsapp `" +#: ../system/translations.rst:54 +msgid "Customizing Translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:124 -msgid "``admin.public_links``" +#: ../system/translations.rst:56 +msgid "" +"Within the translation screen, simply click on the **New Translation** " +"button." msgstr "" -#: ../manage/roles/admin-permissions.rst:125 -msgid ":doc:`Manage > Public Links `" +#: ../system/translations.rst:None +msgid "New translation dialog" msgstr "" -#: ../manage/roles/admin-permissions.rst:151 -msgid "``admin.system_report``" +#: ../system/translations.rst:62 +msgid "" +"In the dialog you can immediately enter the exact translation source (if you " +"know it) and your custom translation text for it and click **Submit**." msgstr "" -#: ../manage/roles/admin-permissions.rst:152 -msgid ":doc:`System > System Report `" +#: ../system/translations.rst:65 +msgid "" +"Alternatively, try to search for translation suggestions in the list below. " +"Selecting an item from the list will pre-fill the translation source for you " +"and then you can just enter your custom translation." msgstr "" -#: ../manage/roles/admin-permissions.rst:166 -msgid "``admin.ticket_auto_assignment``" +#: ../system/translations.rst:69 +msgid "" +"The target language will always default to your current language selection. " +"If you need to translate for a different language, simply change the " +"selection before submitting." msgstr "" -#: ../manage/roles/admin-permissions.rst:167 -msgid ":ref:`Settings > Ticket > Auto Assignment `" +#: ../system/translations.rst:73 +msgid "" +"All your custom translations will show up in the overview table when added. " +"And they will even persist across Zammad updates!" msgstr "" -#: ../manage/roles/admin-permissions.rst:169 -msgid "``admin.ticket_duplicate_detection``" +#: ../system/translations.rst:76 +msgid "" +"Make sure to reload your browser if a translated string is not displayed." msgstr "" -#: ../manage/roles/admin-permissions.rst:170 -msgid ":ref:`Settings > Ticket > Duplicate Detection `" +#: ../system/translations.rst:80 +msgid "Reverting to Original Translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:172 -msgid "``admin.ticket_priority``" +#: ../system/translations.rst:82 +msgid "" +"If you want to revert a custom translation to original text, simply use the " +"appropriate action within the row of the overview table." msgstr "" -#: ../manage/roles/admin-permissions.rst:173 -msgid ":ref:`System > Objects >Ticket Priority `" +#: ../system/translations.rst:85 +msgid "" +"Depending on the type of the translation source, the action has a slightly " +"different name:" msgstr "" -#: ../manage/roles/admin-permissions.rst:175 -msgid "``admin.ticket_state``" +#: ../system/translations.rst:88 +msgid "**Reset** for customized system translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:176 -msgid ":ref:`System > Objects >Ticket State `" +#: ../system/translations.rst:89 +msgid "**Remove** for customized local translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:193 -msgid "``admin.webhook``" +#: ../system/translations.rst:91 +msgid "" +"In both cases, the action will remove the customized translation after a " +"confirmation." msgstr "" -#: ../manage/roles/admin-permissions.rst:194 -msgid ":doc:`Manage > Webhook `" +#: ../system/translations.rst:None +msgid "Screenshot showing the location of the Remove action" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:43 -msgid "``user_preferences.appearance``" +#: ../system/translations.rst:99 +msgid "Inline Translations" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:44 -msgid "Appearance configuration" +#: ../system/translations.rst:101 +msgid "" +"If you prefer a more hands-on approach, you can activate the inline or on-" +"screen translation feature by pressing ``ctrl`` + ``alt`` + ``t`` at any " +"time and on any screen." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:0 -msgid "Users can switch between dark, light and" +#: ../system/translations.rst:105 +msgid "" +"All customizable translation texts will be highlighted for you on the " +"screen. Just click into the highlighted area and update the text in place." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:0 -msgid "automatic mode." +#: ../system/translations.rst:None +msgid "Inline translation mode activated for the Overview screen" msgstr "" -#: ../system/system-report.rst:2 -msgid "System Report" +#: ../system/translations.rst:112 +msgid "" +"When finished editing, simply press ``ctrl`` + ``alt`` + ``t`` again to " +"deactivate." msgstr "" -#: ../system/system-report.rst:4 +#: ../system/translations.rst:117 msgid "" -"In this place you can't configure Zammad. Instead you can obtain a system " -"report about Zammad and its configuration." +"Even though it's available on any screen, the inline translation feature " +"requires admin permissions. It works only for the current language " +"selection. If you need to translate a different language, first change the " +"language in your :user-docs:`profile settings `." msgstr "" -#: ../system/system-report.rst:7 -msgid "" -"See the description in Zammad for an explanation. You can even find a " -"preview of the included data below the **Download** button." +#: ../system/version.rst:2 +msgid "Version" msgstr "" -#: ../system/system-report.rst:10 -msgid "" -"Zammad never sends this automatically to anyone. It is a manual process only " -"to provide better support based on your configuration." +#: ../system/version.rst:4 +msgid "Shows which version is currently being used on your Zammad-instance." msgstr "" #, fuzzy diff --git a/locale/fa/LC_MESSAGES/admin-docs.po b/locale/fa/LC_MESSAGES/admin-docs.po index ed6b70e8..32fec1ec 100644 --- a/locale/fa/LC_MESSAGES/admin-docs.po +++ b/locale/fa/LC_MESSAGES/admin-docs.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Zammad\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-11-06 10:31+0100\n" +"POT-Creation-Date: 2024-11-12 16:31+0100\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -1040,12 +1040,12 @@ msgstr "" #: ../manage/roles/agent-permissions.rst:31 #: ../manage/roles/user-preferences-permissions.rst:37 #: ../manage/scheduler.rst:108 ../manage/webhook/add.rst:116 +#: ../misc/variables.rst:101 #: ../system/integrations/cti/includes/inbound-calls.include.rst:15 #: ../system/integrations/cti/includes/outbound-calls.include.rst:18 #: ../system/integrations/cti/includes/inbound-calls.include.rst:14 #: ../system/integrations/cti/includes/outbound-calls.include.rst:17 -#: ../system/objects.rst:162 ../system/objects.rst:244 -#: ../system/variables.rst:101 ../system/objects.rst:246 +#: ../system/objects.rst:162 ../system/objects.rst:246 msgid "Note" msgstr "" @@ -2257,7 +2257,7 @@ msgstr "" #: ../channels/email/signatures.rst:22 msgid "" "To individualize the signatures, it is possible to automatically load " -"specific information into a signature via :doc:`/system/variables`. All " +"specific information into a signature via :doc:`/misc/variables`. All " "information stored on the ticket, assigned customers or agents can be " "inserted. This makes it possible to design the signature individually. To " "load a list of available variables, enter two colons (``::``) into the " @@ -2550,7 +2550,7 @@ msgstr "" #: ../channels/form.rst:19 ../manage/groups/settings.rst:14 #: ../manage/scheduler.rst:39 ../manage/slas/how-do-they-work.rst:26 #: ../manage/templates.rst:33 ../system/objects.rst:130 -#: ../system/objects.rst:232 ../system/objects.rst:234 +#: ../system/objects.rst:234 msgid "Name" msgstr "" @@ -2579,7 +2579,7 @@ msgstr "" #: ../manage/macros/how-do-they-work.rst:0 ../manage/overviews.rst:0 #: ../manage/scheduler.rst:111 ../manage/templates.rst:43 #: ../manage/webhook/add.rst:123 ../system/objects.rst:169 -#: ../system/objects.rst:246 ../system/objects.rst:248 +#: ../system/objects.rst:248 msgid "Active" msgstr "" @@ -2921,10 +2921,9 @@ msgid "Default value" msgstr "" #: ../channels/form.rst:219 ../manage/public-links.rst:47 -#: ../misc/object-conditions/basics.rst:64 +#: ../misc/object-conditions/basics.rst:64 ../misc/variables.rst:100 #: ../system/core-workflows/condition-operators.rst:21 -#: ../system/objects/permissions.rst:39 ../system/subscription/billing.rst:53 -#: ../system/variables.rst:100 +#: ../system/objects/permissions.rst:39 ../system/subscription.rst:208 msgid "Description" msgstr "" @@ -5908,7 +5907,7 @@ msgstr "" msgid "System" msgstr "" -#: ../index.rst:87 ../index.rst:88 +#: ../index.rst:87 msgid "Misc" msgstr "" @@ -7142,7 +7141,7 @@ msgstr "" #: ../manage/macros/how-do-they-work.rst:28 msgid "" "Unlike triggers, the scheduler, and text modules, macro actions do **not** " -"support the use of :doc:`/system/variables`." +"support the use of :doc:`/misc/variables`." msgstr "" #: ../manage/macros/how-do-they-work.rst:32 @@ -8370,165 +8369,149 @@ msgid "Accessing chat for agents: ``chat.agent``" msgstr "" #: ../manage/roles/admin-permissions.rst:53 +msgid "``admin.checklist``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:54 +msgid ":doc:`Manage > Checklist `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:56 msgid "``admin.channel_email``" msgstr "" -#: ../manage/roles/admin-permissions.rst:54 #: ../manage/roles/admin-permissions.rst:57 msgid ":doc:`Channels > Email `" msgstr "" -#: ../manage/roles/admin-permissions.rst:56 #: ../manage/roles/admin-permissions.rst:59 msgid "``admin.channel_facebook``" msgstr "" -#: ../manage/roles/admin-permissions.rst:57 #: ../manage/roles/admin-permissions.rst:60 msgid ":doc:`Channels > Facebook `" msgstr "" -#: ../manage/roles/admin-permissions.rst:58 #: ../manage/roles/admin-permissions.rst:61 msgid "" "Accessing Facebook tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:59 #: ../manage/roles/admin-permissions.rst:62 msgid "``admin.channel_formular``" msgstr "" -#: ../manage/roles/admin-permissions.rst:60 #: ../manage/roles/admin-permissions.rst:63 msgid ":doc:`Channels > Form `" msgstr "" -#: ../manage/roles/admin-permissions.rst:62 #: ../manage/roles/admin-permissions.rst:65 msgid "``admin.channel_google``" msgstr "" -#: ../manage/roles/admin-permissions.rst:63 #: ../manage/roles/admin-permissions.rst:66 msgid ":doc:`Channels > Google `" msgstr "" -#: ../manage/roles/admin-permissions.rst:65 #: ../manage/roles/admin-permissions.rst:68 msgid "``admin.channel_microsoft365``" msgstr "" -#: ../manage/roles/admin-permissions.rst:66 #: ../manage/roles/admin-permissions.rst:69 msgid ":doc:`Channels > Microsoft 365 `" msgstr "" -#: ../manage/roles/admin-permissions.rst:68 #: ../manage/roles/admin-permissions.rst:71 msgid "``admin.channel_sms``" msgstr "" -#: ../manage/roles/admin-permissions.rst:69 #: ../manage/roles/admin-permissions.rst:72 msgid ":doc:`Channels > SMS `" msgstr "" -#: ../manage/roles/admin-permissions.rst:71 #: ../manage/roles/admin-permissions.rst:74 msgid "``admin.channel_telegram``" msgstr "" -#: ../manage/roles/admin-permissions.rst:72 #: ../manage/roles/admin-permissions.rst:75 msgid ":doc:`Channels > Telegram `" msgstr "" -#: ../manage/roles/admin-permissions.rst:73 #: ../manage/roles/admin-permissions.rst:76 msgid "" "Accessing Telegram tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:74 #: ../manage/roles/admin-permissions.rst:77 msgid "``admin.channel_twitter``" msgstr "" -#: ../manage/roles/admin-permissions.rst:75 #: ../manage/roles/admin-permissions.rst:78 msgid ":doc:`Channels > Twitter `" msgstr "" -#: ../manage/roles/admin-permissions.rst:76 #: ../manage/roles/admin-permissions.rst:79 msgid "" "Accessing Twitter/X tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:77 #: ../manage/roles/admin-permissions.rst:80 msgid "``admin.channel_web``" msgstr "" -#: ../manage/roles/admin-permissions.rst:78 #: ../manage/roles/admin-permissions.rst:81 msgid ":doc:`Channels > Web `" msgstr "" -#: ../manage/roles/admin-permissions.rst:80 +#: ../manage/roles/admin-permissions.rst:83 +msgid "``admin.channel_whatsapp``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:84 +msgid ":doc:`Channels > Whatsapp `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:86 msgid "``admin.core_workflows``" msgstr "" -#: ../manage/roles/admin-permissions.rst:81 #: ../manage/roles/admin-permissions.rst:87 msgid ":doc:`System > Core Workflows `" msgstr "" -#: ../manage/roles/admin-permissions.rst:83 #: ../manage/roles/admin-permissions.rst:89 msgid "``admin.data_privacy``" msgstr "" -#: ../manage/roles/admin-permissions.rst:84 #: ../manage/roles/admin-permissions.rst:90 msgid ":doc:`System > Data Privacy `" msgstr "" -#: ../manage/roles/admin-permissions.rst:85 #: ../manage/roles/admin-permissions.rst:91 msgid "" "🔥 Be careful, it allows users to permanently delete data on the system." msgstr "" -#: ../manage/roles/admin-permissions.rst:86 #: ../manage/roles/admin-permissions.rst:92 msgid "``admin.group``" msgstr "" -#: ../manage/roles/admin-permissions.rst:87 #: ../manage/roles/admin-permissions.rst:93 msgid ":doc:`Manage > Groups `" msgstr "" -#: ../manage/roles/admin-permissions.rst:89 #: ../manage/roles/admin-permissions.rst:95 msgid "``admin.integration``" msgstr "" -#: ../manage/roles/admin-permissions.rst:90 #: ../manage/roles/admin-permissions.rst:96 msgid ":doc:`System > Integrations `" msgstr "" -#: ../manage/roles/admin-permissions.rst:92 #: ../manage/roles/admin-permissions.rst:98 msgid "``admin.knowledge_base``" msgstr "" -#: ../manage/roles/admin-permissions.rst:93 #: ../manage/roles/admin-permissions.rst:99 msgid ":doc:`Manage > Knowledge Base `" msgstr "" @@ -8548,57 +8531,46 @@ msgid "" "knowledge-base.html#editing-answers>`." msgstr "" -#: ../manage/roles/admin-permissions.rst:98 #: ../manage/roles/admin-permissions.rst:104 msgid "``admin.macro``" msgstr "" -#: ../manage/roles/admin-permissions.rst:99 #: ../manage/roles/admin-permissions.rst:105 msgid ":doc:`Manage > Macros `" msgstr "" -#: ../manage/roles/admin-permissions.rst:100 #: ../manage/roles/admin-permissions.rst:106 msgid "In some cases, macros may also require ``admin.tag``" msgstr "" -#: ../manage/roles/admin-permissions.rst:101 #: ../manage/roles/admin-permissions.rst:107 msgid "``admin.maintenance``" msgstr "" -#: ../manage/roles/admin-permissions.rst:102 #: ../manage/roles/admin-permissions.rst:108 msgid ":doc:`System > Maintenance `" msgstr "" -#: ../manage/roles/admin-permissions.rst:104 #: ../manage/roles/admin-permissions.rst:110 msgid "``admin.monitoring``" msgstr "" -#: ../manage/roles/admin-permissions.rst:105 #: ../manage/roles/admin-permissions.rst:111 msgid ":doc:`System > Monitoring `" msgstr "" -#: ../manage/roles/admin-permissions.rst:107 #: ../manage/roles/admin-permissions.rst:113 msgid "``admin.object``" msgstr "" -#: ../manage/roles/admin-permissions.rst:108 #: ../manage/roles/admin-permissions.rst:114 msgid ":doc:`System > Objects `" msgstr "" -#: ../manage/roles/admin-permissions.rst:110 #: ../manage/roles/admin-permissions.rst:116 msgid "``admin.organization``" msgstr "" -#: ../manage/roles/admin-permissions.rst:111 #: ../manage/roles/admin-permissions.rst:117 msgid ":doc:`Manage > Organizations `" msgstr "" @@ -8615,202 +8587,210 @@ msgstr "" msgid "They can even edit an organization's name, domain, and notes!" msgstr "" -#: ../manage/roles/admin-permissions.rst:115 #: ../manage/roles/admin-permissions.rst:121 msgid "``admin.overview``" msgstr "" -#: ../manage/roles/admin-permissions.rst:116 #: ../manage/roles/admin-permissions.rst:122 msgid ":doc:`Manage > Overviews`" msgstr "" -#: ../manage/roles/admin-permissions.rst:118 +#: ../manage/roles/admin-permissions.rst:124 +msgid "``admin.public_links``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:125 +msgid ":doc:`Manage > Public Links `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:127 msgid "``admin.package``" msgstr "" -#: ../manage/roles/admin-permissions.rst:119 #: ../manage/roles/admin-permissions.rst:128 msgid ":doc:`System > Packages `" msgstr "" -#: ../manage/roles/admin-permissions.rst:121 #: ../manage/roles/admin-permissions.rst:130 msgid "``admin.report_profile``" msgstr "" -#: ../manage/roles/admin-permissions.rst:122 #: ../manage/roles/admin-permissions.rst:131 msgid ":doc:`Manage > Report Profiles `" msgstr "" -#: ../manage/roles/admin-permissions.rst:123 #: ../manage/roles/admin-permissions.rst:132 msgid "Access to view reports: ``report``" msgstr "" -#: ../manage/roles/admin-permissions.rst:124 #: ../manage/roles/admin-permissions.rst:133 msgid "``admin.role``" msgstr "" -#: ../manage/roles/admin-permissions.rst:125 #: ../manage/roles/admin-permissions.rst:134 msgid ":doc:`Manage > Roles `" msgstr "" -#: ../manage/roles/admin-permissions.rst:127 #: ../manage/roles/admin-permissions.rst:136 msgid "``admin.scheduler``" msgstr "" -#: ../manage/roles/admin-permissions.rst:128 #: ../manage/roles/admin-permissions.rst:137 msgid ":doc:`Manage > Scheduler `" msgstr "" -#: ../manage/roles/admin-permissions.rst:129 #: ../manage/roles/admin-permissions.rst:138 msgid "For automation on tickets" msgstr "" -#: ../manage/roles/admin-permissions.rst:130 #: ../manage/roles/admin-permissions.rst:139 msgid "``admin.security``" msgstr "" -#: ../manage/roles/admin-permissions.rst:131 #: ../manage/roles/admin-permissions.rst:140 msgid ":doc:`Settings > Security `" msgstr "" -#: ../manage/roles/admin-permissions.rst:132 #: ../manage/roles/admin-permissions.rst:141 msgid "Settings of Zammad. This also covers third party authentications." msgstr "" -#: ../manage/roles/admin-permissions.rst:133 #: ../manage/roles/admin-permissions.rst:142 msgid "``admin.session``" msgstr "" -#: ../manage/roles/admin-permissions.rst:134 #: ../manage/roles/admin-permissions.rst:143 msgid ":doc:`System > Sessions `" msgstr "" -#: ../manage/roles/admin-permissions.rst:136 #: ../manage/roles/admin-permissions.rst:145 msgid "``admin.setting_system``" msgstr "" -#: ../manage/roles/admin-permissions.rst:137 #: ../manage/roles/admin-permissions.rst:146 msgid ":doc:`Settings > System `" msgstr "" -#: ../manage/roles/admin-permissions.rst:139 #: ../manage/roles/admin-permissions.rst:148 msgid "``admin.sla``" msgstr "" -#: ../manage/roles/admin-permissions.rst:140 #: ../manage/roles/admin-permissions.rst:149 msgid ":doc:`Manage > SLAs `" msgstr "" -#: ../manage/roles/admin-permissions.rst:142 +#: ../manage/roles/admin-permissions.rst:151 +msgid "``admin.system_report``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:152 +msgid ":doc:`System > System Report `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:154 msgid "``admin.tag``" msgstr "" -#: ../manage/roles/admin-permissions.rst:143 #: ../manage/roles/admin-permissions.rst:155 msgid ":doc:`Manage > Tags `" msgstr "" -#: ../manage/roles/admin-permissions.rst:145 #: ../manage/roles/admin-permissions.rst:157 msgid "``admin.template``" msgstr "" -#: ../manage/roles/admin-permissions.rst:146 #: ../manage/roles/admin-permissions.rst:158 msgid ":doc:`Manage > Templates `" msgstr "" -#: ../manage/roles/admin-permissions.rst:148 #: ../manage/roles/admin-permissions.rst:160 msgid "``admin.text_module``" msgstr "" -#: ../manage/roles/admin-permissions.rst:149 #: ../manage/roles/admin-permissions.rst:161 msgid ":doc:`Manage > Text Modules `" msgstr "" -#: ../manage/roles/admin-permissions.rst:151 #: ../manage/roles/admin-permissions.rst:163 msgid "``admin.ticket``" msgstr "" -#: ../manage/roles/admin-permissions.rst:152 #: ../manage/roles/admin-permissions.rst:164 msgid ":doc:`Settings > Tickets `" msgstr "" -#: ../manage/roles/admin-permissions.rst:153 #: ../manage/roles/admin-permissions.rst:165 msgid "Does not grant access to :doc:`/misc/composer`" msgstr "" -#: ../manage/roles/admin-permissions.rst:154 +#: ../manage/roles/admin-permissions.rst:166 +msgid "``admin.ticket_auto_assignment``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:167 +msgid ":ref:`Settings > Ticket > Auto Assignment `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:169 +msgid "``admin.ticket_duplicate_detection``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:170 +msgid ":ref:`Settings > Ticket > Duplicate Detection `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:172 +msgid "``admin.ticket_priority``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:173 +msgid ":ref:`System > Objects >Ticket Priority `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:175 +msgid "``admin.ticket_state``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:176 +msgid ":ref:`System > Objects >Ticket State `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:178 msgid "``admin.time_accounting``" msgstr "" -#: ../manage/roles/admin-permissions.rst:155 #: ../manage/roles/admin-permissions.rst:179 msgid ":doc:`Manage > Time Accounting `" msgstr "" -#: ../manage/roles/admin-permissions.rst:156 #: ../manage/roles/admin-permissions.rst:180 msgid "Also allows the export of timekeeping records." msgstr "" -#: ../manage/roles/admin-permissions.rst:157 #: ../manage/roles/admin-permissions.rst:181 msgid "``admin.translation``" msgstr "" -#: ../manage/roles/admin-permissions.rst:158 #: ../manage/roles/admin-permissions.rst:182 msgid ":doc:`System > Translations `" msgstr "" -#: ../manage/roles/admin-permissions.rst:159 #: ../manage/roles/admin-permissions.rst:183 msgid "Also enables inline translation" msgstr "" -#: ../manage/roles/admin-permissions.rst:160 #: ../manage/roles/admin-permissions.rst:184 msgid "``admin.trigger``" msgstr "" -#: ../manage/roles/admin-permissions.rst:161 #: ../manage/roles/admin-permissions.rst:185 msgid ":doc:`Manage > Triggers `" msgstr "" -#: ../manage/roles/admin-permissions.rst:163 #: ../manage/roles/admin-permissions.rst:187 msgid "``admin.user``" msgstr "" -#: ../manage/roles/admin-permissions.rst:164 #: ../manage/roles/admin-permissions.rst:188 msgid ":doc:`Manage > Users `" msgstr "" @@ -8829,6 +8809,14 @@ msgid "" "from-users-perspective>` ." msgstr "" +#: ../manage/roles/admin-permissions.rst:193 +msgid "``admin.webhook``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:194 +msgid ":doc:`Manage > Webhook `" +msgstr "" + #: ../manage/roles/agent-permissions.rst:2 msgid "Agent Permissions" msgstr "" @@ -9247,36 +9235,45 @@ msgid "than the user that generated them." msgstr "" #: ../manage/roles/user-preferences-permissions.rst:43 +msgid "``user_preferences.appearance``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:44 +msgid "Appearance configuration" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "Users can switch between dark, light and" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "automatic mode." +msgstr "" + #: ../manage/roles/user-preferences-permissions.rst:47 msgid "``user_preferences.avatar``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:44 #: ../manage/roles/user-preferences-permissions.rst:48 msgid "Avatar settings" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:45 #: ../manage/roles/user-preferences-permissions.rst:49 msgid "Override the default Gravatar with a custom avatar" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:46 #: ../manage/roles/user-preferences-permissions.rst:50 msgid "``user_preferences.calendar``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:47 #: ../manage/roles/user-preferences-permissions.rst:51 msgid "Configure the calendar feed" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:49 #: ../manage/roles/user-preferences-permissions.rst:53 msgid "``user_preferences.device``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:50 #: ../manage/roles/user-preferences-permissions.rst:54 msgid "Manage device login sessions" msgstr "" @@ -9293,22 +9290,18 @@ msgstr "" msgid "To learn more, see :doc:`/manage/trigger/system-notifications`." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:54 #: ../manage/roles/user-preferences-permissions.rst:58 msgid "``user_preferences.language``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:55 #: ../manage/roles/user-preferences-permissions.rst:59 msgid "Configure the UI locale/language" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:57 #: ../manage/roles/user-preferences-permissions.rst:61 msgid "``user_preferences.linked_accounts``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:58 #: ../manage/roles/user-preferences-permissions.rst:62 msgid "Account linking" msgstr "" @@ -9332,7 +9325,6 @@ msgstr "" msgid "is the only way users can utilize third-party logins." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:63 #: ../manage/roles/user-preferences-permissions.rst:67 msgid "``user_preferences.notifications``" msgstr "" @@ -9359,7 +9351,6 @@ msgstr "" msgid "Customers can't receive ticket notifications at all." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:69 #: ../manage/roles/user-preferences-permissions.rst:73 msgid "``user_preferences.out_of_office``" msgstr "" @@ -9384,7 +9375,6 @@ msgstr "" msgid "they're replacing." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:75 #: ../manage/roles/user-preferences-permissions.rst:79 msgid "``user_preferences.overview_sorting``" msgstr "" @@ -9413,12 +9403,10 @@ msgstr "" msgid "overviews has no effect on custom orders." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:82 #: ../manage/roles/user-preferences-permissions.rst:86 msgid "``user_preferences.password``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:83 #: ../manage/roles/user-preferences-permissions.rst:87 msgid "Change account password" msgstr "" @@ -9435,7 +9423,6 @@ msgstr "" msgid "your only allowed authentication method." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:87 #: ../manage/roles/user-preferences-permissions.rst:91 msgid "``user_preferences.two_factor_authentication``" msgstr "" @@ -9472,7 +9459,7 @@ msgstr "" #: ../manage/scheduler.rst:19 msgid "" -"Schedulers can be used to send periodic reminder emails. Use :doc:`/system/" +"Schedulers can be used to send periodic reminder emails. Use :doc:`/misc/" "variables` to build highly-customized email templates." msgstr "" @@ -10468,7 +10455,7 @@ msgstr "" #: ../manage/text-modules.rst:57 msgid "" -"The example text modules below use :doc:`/system/variables` to dynamically " +"The example text modules below use :doc:`/misc/variables` to dynamically " "insert information like the customer's or agent's names." msgstr "" @@ -10808,8 +10795,8 @@ msgstr "" #: ../misc/object-conditions/basics.rst:144 #: ../misc/object-conditions/basics.rst:160 #: ../misc/object-conditions/basics.rst:168 -#: ../misc/object-conditions/basics.rst:178 ../settings/ticket.rst:2 -#: ../system/variables/ticket.rst:2 +#: ../misc/object-conditions/basics.rst:178 ../misc/variables/ticket.rst:2 +#: ../settings/ticket.rst:2 msgid "Ticket" msgstr "" @@ -11043,7 +11030,7 @@ msgstr "" #: ../manage/trigger/how-do-they-work.rst:79 msgid "" -"Certain actions (such as *email*, *SMS* and *notes*) support :doc:`/system/" +"Certain actions (such as *email*, *SMS* and *notes*) support :doc:`/misc/" "variables`, which can be used to build highly-customized message templates." msgstr "" @@ -11072,7 +11059,7 @@ msgstr "" msgid "" "You can also combine static text with placeholders for text fields. Remember " "that the placeholders' values have to be known during trigger runtime. Learn " -"more about :doc:`/system/variables`." +"more about :doc:`/misc/variables`." msgstr "" #: ../manage/trigger/how-do-they-work.rst:105 @@ -12037,7 +12024,7 @@ msgstr "" msgid "" "When switched on, a code editor will be shown below, where you can configure " "custom payload for your webhook in JSON format. To insert supported :doc:`/" -"system/variables` use ``::`` or ``#{`` shortcuts for autocomplete." +"misc/variables` use ``::`` or ``#{`` shortcuts for autocomplete." msgstr "" #: ../manage/webhook/add.rst:103 @@ -14614,11942 +14601,11833 @@ msgid "" "powerful conditions with AND/OR relations." msgstr "" -#: ../settings/branding.rst:10 -msgid "Product Name" +#: ../misc/variables.rst:2 +msgid "Variables" msgstr "" -#: ../settings/branding.rst:7 +#: ../misc/variables.rst:4 msgid "" -"Defines the name of the application, shown in the web interface, tabs and " -"title bar of the web browser." +"Please note that this is just an overview of available variables. It might " +"be incomplete or variables might not be available within some functions. If " +"you're missing variables or are not sure if something is not working as " +"expected, feel free to ask over at the `Community `_." msgstr "" -#: ../settings/branding.rst:10 -msgid "Default value: ``Zammad Helpdesk``" +#: ../misc/variables.rst:10 +msgid "" +"Variables can be called by typing ``::`` (just like text modules in the " +"frontend), as long as you're in a supported text field within the backend. " +"Zammad will display all variables being available within this context and " +"replace it to the variable as soon as you selected an entry." msgstr "" -#: ../settings/branding.rst:13 -msgid "Will be shown in the app and is included in email footers." +#: ../misc/variables.rst:15 +msgid "" +"You have an empty field which you referenced and it appears as ``-``? That's " +"currently working as designed - you might want to ensure that these fields " +"always have a value." msgstr "" -#: ../settings/branding.rst:19 -msgid "Logo" +#: ../misc/variables.rst:20 +msgid "Variable Categories" msgstr "" -#: ../settings/branding.rst:16 -msgid "Defines the logo of the application, shown in the login page of Zammad." +#: ../misc/variables.rst:31 +msgid "Wait, What About Custom Objects?" msgstr "" -#: ../settings/branding.rst:18 +#: ../misc/variables.rst:33 msgid "" -"Ensure to hit the \"Submit\" button after uploading the logo. Otherwise your " -"change will not be saved." +"Good point! Of course, we can't predict what objects you might create, but " +"we can give you a hint on how to put the puzzle together to get your custom " +"values." msgstr "" -#: ../settings/branding.rst:22 +#: ../misc/variables.rst:36 msgid "" -"Allows to set the default language of the Zammad instance. The here defined " -"locale mostly acts as a fallback for:" -msgstr "" - -#: ../settings/branding.rst:25 -msgid "user preferences (if Zammad can't detect the users locale)" +"For this, we'll talk about the inner part of the variable (so everything " +"within ``#{}``), please put the outer part around to have a valid variable. " +"The first part of the variable name consist of the object type. Currently " +"these are:" msgstr "" -#: ../settings/branding.rst:26 -msgid "CSV output (reporting, time accounting)" +#: ../misc/variables.rst:41 +msgid "Ticket (``ticket``)" msgstr "" -#: ../settings/branding.rst:30 -msgid "Define the timezone of your Zammad installation." +#: ../misc/variables.rst:42 +msgid "User (``user``)" msgstr "" -#: ../settings/branding.rst:32 -msgid "" -"This does not have any effect on timings for your agents or how Zammad " -"stores date and time values." +#: ../misc/variables.rst:43 +msgid "Organization (``organization``)" msgstr "" -#: ../settings/branding.rst:35 -msgid "Changing this value has direct consequences on the following areas:" +#: ../misc/variables.rst:44 +msgid "Group (``group``)" msgstr "" -#: ../settings/branding.rst:37 -msgid ":doc:`/manage/scheduler` tasks" +#: ../misc/variables.rst:46 +msgid "" +"The second part is the name of the attribute. This is the name you define " +"during object creation and can be found within the object attribute menu at " +"any time. The first and second part of a variable is divided by a point, e." +"g.: ``ticket.number`` which will in total be ``#{ticket.number}``." msgstr "" -#: ../settings/branding.rst:38 -msgid "search indexing (and thus reporting)" +#: ../misc/variables.rst:51 +msgid "" +"Now, in some situations it's possible that you'll need to use a third part. " +"The best example for such a situation would be a ``select`` or ``tree-" +"select`` field which will by default return the key value, not it's display " +"name. For this, just extend your variable with ``.value``. This will result " +"in ``#{ticket.select.value}``." msgstr "" -#: ../settings/branding.rst:40 -msgid "calendar subscriptions" +#: ../misc/variables.rst:60 +msgid "Using Translated Variables" msgstr "" -#: ../settings/branding.rst:41 -msgid "browser printing" +#: ../misc/variables.rst:62 +msgid "" +"If you want to use a translated variable in triggers or schedulers, you can " +"extend the placeholder like this: ``#{t(ticket.state.name)}``. The ``t`` " +"tells Zammad to search for fitting translated strings. The used output " +"language is based on the system language of Zammad which you can set in the " +"admin panel under :doc:`/settings/branding` or based on the selected locale " +"in the trigger/scheduler edit dialog." msgstr "" -#: ../settings/branding.rst:43 +#: ../misc/variables.rst:69 msgid "" -"Please note that some of above are fallbacks in case Zammad could not detect " -"the agents timezone correctly." +"A possible use-case: you want to send your customers updates on tickets via " +"trigger or scheduler which should include the state of the ticket. Using the " +"default ``#{ticket.state.name}`` (without the translation flag ``t()``) " +"would lead to the output of the original (english) name of the state." msgstr "" -#: ../settings/branding.rst:77 -msgid "Pretty Date" +#: ../misc/variables.rst:75 +msgid "Date and Time Formatting" msgstr "" -#: ../settings/branding.rst:47 +#: ../misc/variables.rst:77 msgid "" -"This setting allows you to define how Zammad should display time stamps " -"within the interface to all users." +"The system (trigger/scheduler selected) locale and timezone predefines a " +"default format of date and timestamp. This format is customizable by using " +"the ``dt()`` method." msgstr "" -#: ../settings/branding.rst:50 -msgid "" -"This does not have any effect on how Zammad returns e.g. time values via " -"variables." +#: ../misc/variables.rst:79 +msgid "The method arguments are as follows:" msgstr "" -#: ../settings/branding.rst:77 -msgid "Choose in between the following options:" +#: ../misc/variables.rst:81 +msgid "The date or timestamp variable you want to format." msgstr "" -#: ../settings/branding.rst:64 -msgid "relative" +#: ../misc/variables.rst:82 +msgid "The output format string." msgstr "" -#: ../settings/branding.rst:55 +#: ../misc/variables.rst:83 +msgid "The timezone to apply (optional)." +msgstr "" + +#: ../misc/variables.rst:85 +#: ../system/objects/external-data-source-example.rst:23 +msgid "**Example:**" +msgstr "" + +#: ../misc/variables.rst:86 msgid "" -"This timestamp shows a relative time span until it switches to a date. Over " -"time, it will change as follows:" +"``#{dt(ticket.updated_at, \"%A %Y-%m-%d %H:%M in the office\", \"Europe/" +"Berlin\")}``" msgstr "" -#: ../settings/branding.rst:58 -msgid "just now" +#: ../misc/variables.rst:87 +msgid "Monday, 2024-03-18 15:31 in the office" msgstr "" -#: ../settings/branding.rst:59 -msgid "5 minutes ago" +#: ../misc/variables.rst:89 +msgid "" +"If you want to use our example, make sure to paste the string above without " +"formatting (``CTRL+Shift+v``), otherwise it won't work." msgstr "" -#: ../settings/branding.rst:60 -msgid "3 days 1 hour ago" +#: ../misc/variables.rst:93 +msgid "The following table lists available format directives:" msgstr "" -#: ../settings/branding.rst:61 -msgid "``03/04/2022``" +#: ../misc/variables.rst:99 +msgid "Parameter" msgstr "" -#: ../settings/branding.rst:63 -msgid "Hovering the timestamp helps, you'll always get a clean timestamp then." +#: ../misc/variables.rst:102 +msgid "``%Y``" msgstr "" -#: ../settings/branding.rst:71 -msgid "absolute" +#: ../misc/variables.rst:103 +msgid "Year with 4 digits" msgstr "" -#: ../settings/branding.rst:67 -msgid "" -"This timestamp always includes the week day. For one week after creation, " -"the timestamp will not contain the date itself: Thursday 18:35." +#: ../misc/variables.rst:104 +msgid "Use ``%y`` for year with 2 digits" msgstr "" -#: ../settings/branding.rst:71 -msgid "After a week it will switch to: ``Friday 4. Mar 16:00``." +#: ../misc/variables.rst:105 +msgid "``%m``" msgstr "" -#: ../settings/branding.rst:76 -msgid "timestamp" +#: ../misc/variables.rst:106 +msgid "Month of year (as number with zero-padding)" msgstr "" -#: ../settings/branding.rst:74 -msgid "" -"This will cause Zammad to show a complete timestamp according to your locale " -"defaults. For English this could be e.g. ``2022/12/03 2:40 pm`` or for " -"German e.g. ``12.03.2022 14:40``." +#: ../misc/variables.rst:107 +msgid "Use ``%-m`` for month without zero-padding" msgstr "" -#: ../settings/branding.rst:78 -msgid "Default setting: ``relative``." +#: ../misc/variables.rst:108 +msgid "``%d``" msgstr "" -#: ../settings/security.rst:2 -msgid "Security" +#: ../misc/variables.rst:109 +msgid "Day of month (as number with zero-padding)" msgstr "" -#: ../settings/security.rst:4 -msgid "" -"For your overview we split each tab within security settings into its own " -"page:" +#: ../misc/variables.rst:110 +msgid "Use ``%e`` for day without zero-padding" msgstr "" -#: ../settings/security/base.rst:2 ../settings/system/base.rst:2 -#: ../settings/ticket.rst:8 -msgid "Base" +#: ../misc/variables.rst:111 +msgid "``%H``" msgstr "" -#: ../settings/security/base.rst:5 -msgid "New User Accounts" +#: ../misc/variables.rst:112 +msgid "Hour of day in 24h notation with zero-padding" msgstr "" -#: ../settings/security/base.rst:9 -msgid "" -"Activates the `register as a new customer` function on the login page. If " -"set to ``no`` only administrators or agents can create new accounts manually." +#: ../misc/variables.rst:113 +msgid "Use ``%k`` for hour without zero-padding" msgstr "" -#: ../settings/security/base.rst:13 ../settings/security/base.rst:38 -#: ../settings/security/base.rst:66 -msgid "Default setting: ``yes``" +#: ../misc/variables.rst:114 +msgid "``%I``" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing activated \"New User Accounts\" setting" +#: ../misc/variables.rst:115 +msgid "Hour of day in 12h notation with zero-padding" msgstr "" -#: ../settings/security/base.rst:22 +#: ../misc/variables.rst:116 msgid "" -"Deactivation of above function **does not** deactivate automatic account " -"creation! This means: If a user writes e.g. an email to Zammad and has no " -"account yet, Zammad will automatically create the account. User accounts are " -"a direct dependency of tickets and thus technically mandatory." +"Use ``%l`` for hour without zero-padding and ``%p`` / ``%P`` for meridian " +"indicator" msgstr "" -#: ../settings/security/base.rst:29 -msgid "Lost Password" +#: ../misc/variables.rst:117 +msgid "``%M``" msgstr "" -#: ../settings/security/base.rst:33 -msgid "" -"Activates the `lost password` function on the login page. If set to ``no`` " -"only administrators may change the user's password - users may update their " -"own password if they're still logged in and they have the required :doc:" -"`permission `." +#: ../misc/variables.rst:118 +msgid "Minute of hour" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing activated \"Lost Password\" setting" +#: ../misc/variables.rst:120 +msgid "``%S``" msgstr "" -#: ../settings/security/base.rst:49 -msgid "" -"With third party authentications - but especially LDAP - you may want to " -"disable this function. Zammad **will not** change third party login " -"passwords and instead set or change the local password!" +#: ../misc/variables.rst:121 +msgid "Second of Minute" msgstr "" -#: ../settings/security/base.rst:56 -msgid "Password Login" +#: ../misc/variables.rst:123 +msgid "``%A``" msgstr "" -#: ../settings/security/base.rst:60 -msgid "" -"Activates the username & password login by default and if no third-party " -"login is activated. Disabling password login on the Zammad login page only " -"takes effect if you enable any :doc:`third-party`." +#: ../misc/variables.rst:124 +msgid "Weekday name" msgstr "" -#: ../settings/security/base.rst:64 -msgid "See :doc:`third-party` for supported third-party logins." +#: ../misc/variables.rst:125 +msgid "Use ``%a`` for abbreviated name or ``%^A`` for uppercase name" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing de-activated \"Password Login\" setting" +#: ../misc/variables.rst:126 +msgid "``%B``" msgstr "" -#: ../settings/security/base.rst:77 -msgid "" -"To help administrators to overcome \"login issues\", Zammad automatically " -"offers a password request for administrator users. This allows you to adjust " -"Third-Party applications even if the login does no longer work!" +#: ../misc/variables.rst:127 +msgid "Month name" msgstr "" -#: ../settings/security/base.rst:84 -msgid "Session Timeout" +#: ../misc/variables.rst:128 +msgid "Use ``%b`` for abbreviated name" msgstr "" -#: ../settings/security/base.rst:86 -msgid "" -"All settings below by default are set to ``4 weeks``. Session Timeout " -"defines the life time of a users session. As soon as it's reached, Zammad " -"will automatically log off the session in question." +#: ../misc/variables.rst:129 +msgid "``%U``" msgstr "" -#: ../settings/security/base.rst:91 -msgid "" -"Zammad takes the highest value set assigned for the user based on the " -"permissions." +#: ../misc/variables.rst:130 +msgid "Week number of current year" msgstr "" -#: ../settings/security/base.rst:94 -msgid "``admin``" +#: ../misc/variables.rst:131 +msgid "Use ``%W`` for a different calculation method" msgstr "" -#: ../settings/security/base.rst:96 -msgid "``ticket.customer``" +#: ../misc/variables.rst:134 +msgid "" +"We support the known format directives for the Ruby built-in method " +"``strftime`` of the ``DateTime`` class. For more information, see `here " +"`_." msgstr "" -#: ../settings/security/base.rst:97 -msgid "``default`` (fallback if user doesn't have above permissions set)" +#: ../misc/variables/article.rst:2 +msgid "Articles" msgstr "" -#: ../settings/security/base.rst:99 +#: ../misc/variables/article.rst:4 ../misc/variables/config.rst:4 +#: ../misc/variables/current-user.rst:4 ../misc/variables/ticket.rst:4 msgid "" -"All settings act independently from each other allowing you to disable the " -"timeouts for e.g. admins, but not agents." +"If you're missing variables or are not sure if something is not working as " +"expected, feel free to ask over at the `Community `_." msgstr "" -#: ../settings/security/base.rst:115 -#: ../system/integrations/checkmk/api-reference.rst:13 -msgid "Example" +#: ../misc/variables/article.rst:6 +msgid "" +"Below you can find all available ticket article-based variables within " +"Zammad. These can be called via triggers for example. If you're unsure if " +"Zammad does support variables at the point you're at, you can try to type " +"``::`` to check." msgstr "" -#: ../settings/security/base.rst:107 -msgid "Let's suppose you configured the following session timeouts" +#: ../misc/variables/article.rst:9 ../misc/variables/config.rst:9 +#: ../misc/variables/ticket.rst:9 +msgid "" +"The below list gives you an example what kind of data you can expect, it's " +"not intended to explain the data itself." msgstr "" -#: ../settings/security/base.rst:104 -msgid "default: 3 weeks" +#: ../misc/variables/article.rst:11 +msgid "Article Variables" msgstr "" -#: ../settings/security/base.rst:105 -msgid "admin: 2 weeks" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "name" msgstr "" -#: ../settings/security/base.rst:106 -msgid "ticket.agent: 4 weeks" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "variable" msgstr "" -#: ../settings/security/base.rst:107 -msgid "ticket.customer: 1 week" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "example" msgstr "" -#: ../settings/security/base.rst:115 -msgid "This results in the following situations" +#: ../misc/variables/article.rst:1 +msgid "Article > Cc" msgstr "" -#: ../settings/security/base.rst:110 -msgid "a user with ``admin`` permission will have a timeout of 2 weeks" +#: ../misc/variables/article.rst:1 +msgid "``#{article.cc}``" msgstr "" -#: ../settings/security/base.rst:111 -msgid "" -"a user with ``admin`` and ``ticket.agent`` permissions will have a timeout " -"of 2 weeks" +#: ../misc/variables/article.rst:1 +msgid "``jdoe@example.com, company@example.com``" msgstr "" -#: ../settings/security/base.rst:113 -msgid "" -"a user with ``ticket.customer`` permission will have a timeout of 1 week" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Address" msgstr "" -#: ../settings/security/base.rst:115 -msgid "" -"a user with neither ``admin``, ``ticket.agent`` nor ``ticket.customer`` " -"permissions will have a timeout of 3 weeks" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.address}``" msgstr "" -#: ../settings/security/password.rst:4 -msgid "" -"This section allows you to define password requirements for the local user " -"accounts." +#: ../misc/variables/article.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:9 -msgid "" -"Zammad does **not** allow you to change your LDAP password, instead, it will " -"set a password in its local database which might confuse your users. This " -"might be addressed in the future by `#1169 `_." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Department" msgstr "" -#: ../settings/security/password.rst:14 -msgid "**Exception for admins**" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.department}``" msgstr "" -#: ../settings/security/password.rst:16 -msgid "" -"Please note that below password policies *do not* affect administrators " -"setting passwords on user accounts. While this seems strange and not safe we " -"believe that an administrator knowing an user's password is insecure as well." +#: ../misc/variables/article.rst:1 +msgid "``Sales`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:21 -msgid "The suggested workflow is either:" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Email" msgstr "" -#: ../settings/security/password.rst:23 -msgid "" -"to use third party logins to not require local passwords at all **- or -**" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.email}``" msgstr "" -#: ../settings/security/password.rst:25 -msgid "to require your *user to reset the password* upon first login." +#: ../misc/variables/article.rst:1 +msgid "``jdoe@example.com``" msgstr "" -#: ../settings/security/password.rst:27 -msgid "" -"This way administrators are not required to set a user's password at all!" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Fax" msgstr "" -#: ../settings/security/password.rst:31 -msgid "Maximum Failed Logins" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.fax}``" msgstr "" -#: ../settings/security/password.rst:33 -msgid "" -"You can choose a value between ``4`` and ``20``. This defines how often a " -"login to a user account may fail until Zammad will lock it. Your users can " -"always use the \"forgot password\" function to change their password and " -"unlock their account." -msgstr "" - -#: ../settings/security/password.rst:38 -msgid "The default value is ``10``." +#: ../misc/variables/article.rst:1 +msgid "``+4930123456789`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:42 -msgid "Beside changing the user's password, you can also unlock accounts via" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Firstname" msgstr "" -#: ../settings/security/password.rst:44 -msgid ":ref:`user management list `" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.firstname}``" msgstr "" -#: ../settings/security/password.rst:45 -msgid ":docs:`console `" +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Joe`` or empty if not set" msgstr "" -#: ../settings/security/password.rst:46 -msgid ":docs:`API `" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Lastname" msgstr "" -#: ../settings/security/password.rst:50 -msgid "Failed logins via LDAP no longer lock accounts." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.lastname}``" msgstr "" -#: ../settings/security/password.rst:53 -msgid "2 Lower Case And 2 Upper Case Characters" +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +#: ../misc/variables/ticket.rst:1 +msgid "``Doe`` or empty if not set" msgstr "" -#: ../settings/security/password.rst:55 -msgid "" -"You can add complexity to passwords by enforcing at least 2 upper and lower " -"case characters." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Login" msgstr "" -#: ../settings/security/password.rst:58 ../settings/security/password.rst:83 -msgid "The default value is ``no``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.login}``" msgstr "" -#: ../settings/security/password.rst:62 -msgid "Minimum Length" +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +#: ../misc/variables/ticket.rst:1 +msgid "``jdoe``" msgstr "" -#: ../settings/security/password.rst:64 -msgid "" -"This defines the minimum password length required for users to provide (from " -"``4`` to ``20``)." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Mobile" msgstr "" -#: ../settings/security/password.rst:67 -msgid "The default value is ``6``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.mobile}``" msgstr "" -#: ../settings/security/password.rst:71 -msgid "Digit Required" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Note" msgstr "" -#: ../settings/security/password.rst:73 -msgid "This enforces your users to use at least one digit within the password." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.note}``" msgstr "" -#: ../settings/security/password.rst:75 -msgid "The default value is ``yes``." +#: ../misc/variables/article.rst:1 +msgid "``Some note about user`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:78 -msgid "Special Character Required" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Phone" msgstr "" -#: ../settings/security/password.rst:80 -msgid "" -"This setting allows you to improve your password quality even more by " -"enforcing the password to contain at least one special character." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.phone}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:2 -msgid "SSL Certificates" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > VIP" msgstr "" -#: ../settings/security/ssl-certificates.rst:7 -msgid "" -"Zammad offers the possibility to upload custom certificates and custom " -"Certificate Authority (CA) certificates. This can be useful if you want to " -"connect Zammad the secure way to other systems which are using custom " -"certificates." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.vip}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:12 -msgid "" -"An example usecase might be: You have an internal LDAP server that is not " -"accessible from the internet, and you want a SSL-encrypted connection, using " -"a custom certificate." +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +msgid "``true`` or ``false``" msgstr "" -#: ../settings/security/ssl-certificates.rst:19 -msgid "" -"You should have an existing custom certificate file and/or a custom CA " -"certificate file, which you want to add to Zammad. As filetype ``.crt`` is " -"supported and the certificate format has to be PEM (Base64 ASCII)." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Web" msgstr "" -#: ../settings/security/ssl-certificates.rst:25 -msgid "" -"When you import a custom CA certificate, all certificates generated with " -"this are trusted. This can be useful if you have more than one system/" -"certificate you want to connect to and the certificates are issued from the " -"same custom CA." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.web}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:31 -msgid "Add a Certificate" +#: ../misc/variables/article.rst:1 +msgid "``https://zammad.com`` or empty if not set in user object" msgstr "" -#: ../settings/security/ssl-certificates.rst:33 -msgid "" -"To add a custom certificate or a custom CA certificate, head over to the " -"Admin panel > Settings > Security > SSL Certificates. Here you can find a " -"\"Add SSL Certificate\" button. In the dialog you can either select a " -"certificate file or paste the content of the certificate:" +#: ../misc/variables/article.rst:1 +msgid "Article > Created" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate adding dialog" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_at}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:43 -msgid "" -"After selecting a file or pasting the content of the certificate, click on " -"the \"Add\" button to finally upload it to Zammad. Then, the certificates " -"are immediately effective, no restart or similar required." +#: ../misc/variables/article.rst:1 +msgid "``2019-10-08 15:24:47 UTC``" msgstr "" -#: ../settings/security/ssl-certificates.rst:49 -msgid "" -"Please note that only single certificate files are supported. That means if " -"you want to import a certificate / CA certificate, it must contain **only " -"one** certificate." +#: ../misc/variables/article.rst:1 +msgid "Article > From" msgstr "" -#: ../settings/security/ssl-certificates.rst:54 -msgid "Certificate Overview" +#: ../misc/variables/article.rst:1 +msgid "``#{article.from}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:56 +#: ../misc/variables/article.rst:1 msgid "" -"After you added a certificate, you can see a table with information for each " -"added certificate:" +"``Joe Doe `` may differ, depends on ``FROM`` of send mail" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing table of added certificates" +#: ../misc/variables/article.rst:1 +msgid "Article > Sender > Name" msgstr "" -#: ../settings/security/ssl-certificates.rst:64 -msgid "" -"Here you can download the certificate or delete it, if you don't need it " -"anymore." +#: ../misc/variables/article.rst:1 +msgid "``#{article.sender.name}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:68 -msgid "Deleting Certificates" +#: ../misc/variables/article.rst:1 +msgid "``Customer``, ``Agent`` or ``System``" msgstr "" -#: ../settings/security/ssl-certificates.rst:70 -msgid "" -"If you want to delete a specific certificate, you can do it by clicking on " -"the menu in the actions column and selecting delete:" +#: ../misc/variables/article.rst:1 +msgid "Article > Subject" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate deletion button" +#: ../misc/variables/article.rst:1 +msgid "``#{article.subject}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:79 -msgid "Downloading Certificates" +#: ../misc/variables/article.rst:1 +msgid "``My amazing subject``" msgstr "" -#: ../settings/security/ssl-certificates.rst:81 -msgid "" -"If you want to download your certificates, you can do this as well via " -"corresponding action buttons." +#: ../misc/variables/article.rst:1 +msgid "Article > Text" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate download button" +#: ../misc/variables/article.rst:1 +msgid "``#{article.body}``" msgstr "" -#: ../settings/security/third-party.rst:13 -msgid "Login Providers" +#: ../misc/variables/article.rst:1 +msgid "``Test`` without formatting (plain)" msgstr "" -#: ../settings/security/third-party.rst:2 -msgid "Third-Party Applications" +#: ../misc/variables/article.rst:1 +msgid "Article > TicketID" msgstr "" -#: ../settings/security/third-party.rst:4 -msgid "" -"Third party authentication is a great way to help your users to login to " -"Zammad more easily. If the account is yet unknown, Zammad will create a new " -"user automatically, without the user needed to interact (e.g. type in his " -"name). Another big advantage of this feature is that your user doesn't need " -"to remember another password." +#: ../misc/variables/article.rst:1 +msgid "``#{article.ticket_id}``" msgstr "" -#: ../settings/security/third-party.rst:10 -msgid "" -"You can deactivate logging in via :ref:`security_password_login` if any of " -"the mentioned authentication providers are enabled in your instance." +#: ../misc/variables/article.rst:1 +msgid "``1`` (not ticket number)" msgstr "" -#: ../settings/security/third-party.rst:27 -msgid "" -"We're currently missing documentation for the following login providers:" +#: ../misc/variables/article.rst:1 +msgid "Article > To" msgstr "" -#: ../settings/security/third-party.rst:29 -msgid "LinkedIn" +#: ../misc/variables/article.rst:1 +msgid "``#{article.to}``" msgstr "" -#: ../settings/security/third-party.rst:30 -msgid "Weibo" +#: ../misc/variables/article.rst:1 +msgid "``helpdesk@example.com``" msgstr "" -#: ../settings/security/third-party.rst:35 -msgid "Automatic Account Link on Initial Logon" +#: ../misc/variables/article.rst:1 +msgid "Article > Type > Name" msgstr "" -#: ../settings/security/third-party.rst:37 -msgid "" -"In general there's two possible options for Zammad on how to deal with " -"already known users as they try to authenticate against a third-party " -"application. By default, Zammad will not automatically link \"unknown\" " -"authentication providers to existing accounts." +#: ../misc/variables/article.rst:1 +msgid "``#{article.type.name}``" msgstr "" -#: ../settings/security/third-party.rst:42 +#: ../misc/variables/article.rst:1 msgid "" -"This means that the user has to manually link authentication providers to " -"their accounts (for more about this :user-docs:`consult the user " -"documentation `)." +"``email`` (`list of article types `_)" msgstr "" -#: ../settings/security/third-party.rst:46 -msgid "" -"Sometimes this doesn't come in handy as this also means you'll receive error " -"messages about \"email address being in use already\" for (yet) unknown " -"third-party authentication methods." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Address" msgstr "" -#: ../settings/security/third-party.rst:50 -msgid "" -"If you want to allow your users to always be able to log in, no matter what, " -"you may want to enable ``Automatic account link on initial logon``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.address}``" msgstr "" -#: ../settings/security/third-party.rst:None -msgid "" -"Screenshot highlighting the \"Automatic account link on initial logon\"\n" -"setting" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Department" msgstr "" -#: ../settings/security/third-party.rst:60 -msgid "Automatic Account Linking Notification" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.department}``" msgstr "" -#: ../settings/security/third-party.rst:64 -msgid "" -"To improve security and your users awareness, you can enable Zammad to " -"notify your users when a new third-party application has been linked to " -"their account." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Email" msgstr "" -#: ../settings/security/third-party.rst:68 -msgid "" -"This notification is sent out once per third-party application. Zammad does " -"also mention the method used, e.g.: ``Microsoft``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.email}``" msgstr "" -#: ../settings/security/third-party.rst:71 -msgid "By default this setting is not active (set to ``no``)." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Fax" msgstr "" -#: ../settings/security/third-party.rst:0 -msgid "" -"Screenshot showing sample notification mail after initial\n" -"third-party linking" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.fax}``" msgstr "" -#: ../settings/security/third-party.rst:85 -msgid "" -"This notification is only sent if the account in question already exists. If " -"the login via the third-party also creates the missing account, the " -"notification will be skipped." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Firstname" msgstr "" -#: ../settings/security/third-party.rst:89 -msgid "This means it only affects:" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.firstname}``" msgstr "" -#: ../settings/security/third-party.rst:91 -msgid "manual account linking within the third-party page of the users profile" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Lastname" msgstr "" -#: ../settings/security/third-party.rst:92 -msgid "" -"logging into an existing local account by utilizing the *automatic account " -"link on initial logon* functionality" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.lastname}``" msgstr "" -#: ../settings/security/third-party.rst:None -msgid "" -"Screenshot showing the \"automatic account linking notification\"\n" -"setting" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Login" msgstr "" -#: ../settings/security/third-party.rst:100 -msgid "No User Creation on Logon" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.login}``" msgstr "" -#: ../settings/security/third-party.rst:102 -msgid "" -"By default, Zammad will create a new user account if the user logs in via a " -"third-party application and the account doesn't exist yet." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Mobile" msgstr "" -#: ../settings/security/third-party.rst:105 -msgid "" -"If you want to prevent Zammad from creating new accounts on logon, you can " -"disable this feature by setting ``No user creation on logon`` to ``yes``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.mobile}``" msgstr "" -#: ../settings/security/third-party.rst:None -msgid "Screenshot showing the \"no user creation on logon\" setting" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Note" msgstr "" -#: ../settings/security/third-party/facebook.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via Facebook To do " -"so, you need to follow these steps:" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.note}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:9 -msgid "Register Facebook App" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Phone" msgstr "" -#: ../settings/security/third-party/facebook.rst:11 -msgid "" -"Visit [https://developers.facebook.com/apps/] and click on \"Add a new App\"" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.phone}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "initial page" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > VIP" msgstr "" -#: ../settings/security/third-party/facebook.rst:17 -msgid "After that enter the app settings" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.vip}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "Create App" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Web" msgstr "" -#: ../settings/security/third-party/facebook.rst:22 -msgid "Navigate to \"Settings\" and fill in this infromation" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.web}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "App Settings" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated" msgstr "" -#: ../settings/security/third-party/facebook.rst:27 -msgid "Navigate to app review and Check \"Make [appname] public?\"" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_at}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "App Review" +#: ../misc/variables/article.rst:1 +msgid "Article > Visibility" msgstr "" -#: ../settings/security/third-party/facebook.rst:35 -msgid "Configure Zammad as Facebook App" +#: ../misc/variables/article.rst:1 +msgid "``#{article.internal}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:37 -msgid "" -"Navigate to \"Admin -> Security -> Third Party Applications\" and enter the " -"App ID and the App Secret. You can find this Key in the Dashbard of your " -"Facebok app." +#: ../misc/variables/article.rst:1 +msgid "``false`` or ``true`` (false if not internal)" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "Zammad Configuration" +#: ../misc/variables/article.rst:1 +msgid "Article Text as HTML (not referenced)" msgstr "" -#: ../settings/security/third-party/facebook.rst:44 -#: ../settings/security/third-party/github.rst:43 -#: ../settings/security/third-party/gitlab.rst:46 -msgid "" -"Now you can link accounts via \"Avatar -> Profile -> Link Accounts\" or " -"login via Zammad login page." +#: ../misc/variables/article.rst:1 +msgid "``#{article.body_as_html}``" msgstr "" -#: ../settings/security/third-party/github.rst:2 -#: ../system/integrations/github.rst:2 -msgid "GitHub" +#: ../misc/variables/article.rst:1 +msgid "``Test`` with formatting" msgstr "" -#: ../settings/security/third-party/github.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via GitHub. To " -"activate the quick login you need to enable OAuth for GitHub." +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "Ticket > Article#" msgstr "" -#: ../settings/security/third-party/github.rst:8 -msgid "Register GitHub App" +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "``#{ticket.article_count}``" msgstr "" -#: ../settings/security/third-party/github.rst:10 -msgid "" -"Visit https://www.github.com/settings/applications/new and enter the app " -"settings. As callback URL enter \"https://zammad_host/auth/github/callback\" " -"where zammad_host has to be replaced with your Zammad FQDN" +#: ../misc/variables/article.rst:1 +msgid "``1`` number of ticket articles" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "Register OAuth app on www.github.com" +#: ../misc/variables/config.rst:2 +msgid "Config" msgstr "" -#: ../settings/security/third-party/github.rst:19 -msgid "Configure Zammad as GitHub App" +#: ../misc/variables/config.rst:6 +msgid "" +"Below you'll find config related variables. These hold useful configuration " +"information that you can use within e.g. triggers to show necessary " +"information to your customer." msgstr "" -#: ../settings/security/third-party/github.rst:21 -msgid "" -"Enter the \"APP ID\" and the \"APP SECRET\" from the GitHub OAUTH " -"Applications Dashboard" +#: ../misc/variables/config.rst:11 +msgid "Config Variables" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub config in Zammad admin interface" +#: ../misc/variables/config.rst:1 +msgid "Config > Fully Qualified Domain Name" msgstr "" -#: ../settings/security/third-party/github.rst:28 -msgid "" -"After you configured the GitHub credentials and activated the login method, " -"you should see a new icon on the login page." +#: ../misc/variables/config.rst:1 +msgid "``#{config.fqdn}``" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub logo on login page" +#: ../misc/variables/config.rst:1 +msgid "``zammad.example.com``" msgstr "" -#: ../settings/security/third-party/github.rst:34 -msgid "" -"If you click on the icon you will be redirected to GitHub and see something " -"similar to this:" +#: ../misc/variables/config.rst:1 +msgid "Config > HTTP type" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub oauth page" +#: ../misc/variables/config.rst:1 +msgid "``#{config.http_type}``" msgstr "" -#: ../settings/security/third-party/github.rst:40 -#: ../settings/security/third-party/gitlab.rst:42 -msgid "" -"When you grant the access you will be redirected to your Zammad instance and " -"logged in as a customer." +#: ../misc/variables/config.rst:1 +msgid "``https`` or ``http``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:2 -msgid "Gitlab" +#: ../misc/variables/config.rst:1 +msgid "Config > Organization" msgstr "" -#: ../settings/security/third-party/gitlab.rst:4 +#: ../misc/variables/config.rst:1 +msgid "``#{config.organization}``" +msgstr "" + +#: ../misc/variables/config.rst:1 msgid "" -"It is possible to create a quick login for your helpdesk via Gitlab. To " -"activate the quick login you need to enable OAuth for Gitlab." +"``Zammad GmbH`` value set in `Branding `_" msgstr "" -#: ../settings/security/third-party/gitlab.rst:8 -msgid "Register Gitlab App" +#: ../misc/variables/config.rst:1 +msgid "Config > Product Name" msgstr "" -#: ../settings/security/third-party/gitlab.rst:10 -msgid "To register an app in Gitlab open your profile and select applications." +#: ../misc/variables/config.rst:1 +msgid "``#{config.product_name}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:12 +#: ../misc/variables/config.rst:1 msgid "" -"As callback URL enter \"https://zammad-fqdn/auth/gitlab/callback\" where " -"zammad-fqdn has to be replaced with your Zammad FQDN" +"``Helpdesk`` value set in `Branding `_" msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Register OAuth app on gitlab instance" +#: ../misc/variables/config.rst:1 +msgid "Config > SystemID" msgstr "" -#: ../settings/security/third-party/gitlab.rst:18 -msgid "Just select *read_user* under scopes as in the screenshot and save it." +#: ../misc/variables/config.rst:1 +msgid "``#{config.system_id}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:21 -msgid "Configure Zammad as Gitlab App" +#: ../misc/variables/config.rst:1 +msgid "``31`` (value between 1 and 99)" msgstr "" -#: ../settings/security/third-party/gitlab.rst:23 -msgid "" -"Enter the \"APP ID\" and the \"APP SECRET\" from the Gitlab OAUTH " -"Applications Dashboard and your Gitlab-URL in the \"SITE\" field." +#: ../misc/variables/config.rst:1 +msgid "Config > Ticket Hook" msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab config in Zammad admin interface" +#: ../misc/variables/config.rst:1 +msgid "``#{config.ticket_hook}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:30 -msgid "" -"After you configured the Gitlab credentials and activated the login method, " -"you should see a new icon on the login page." +#: ../misc/variables/config.rst:1 +msgid "``Ticket#``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab logo on login page" +#: ../misc/variables/current-user.rst:2 +msgid "Current User" msgstr "" -#: ../settings/security/third-party/gitlab.rst:36 +#: ../misc/variables/current-user.rst:6 msgid "" -"If you click on the icon you will be redirected to Gitlab and see something " -"similar to this:" +"Current user variables always return values of the current user that caused " +"e.g. a trigger to run." msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab oauth page" +#: ../misc/variables/current-user.rst:8 +msgid "" +"Due to the above fact, these variables are often not (yet) set or available " +"for usage." msgstr "" -#: ../settings/security/third-party/google.rst:4 +#: ../misc/variables/current-user.rst:10 msgid "" -"With some easy and fast steps, you can enable Zammad to authenticate your " -"users via Google." +"In situations where e.g. schedulers or triggers run, this most likely is " +"nothing you want to use." msgstr "" -#: ../settings/security/third-party/google.rst:8 -msgid "Register a Google App" +#: ../misc/variables/current-user.rst:13 +msgid "Current User Variables" msgstr "" -#: ../settings/security/third-party/google.rst:10 -msgid "" -"First of all, we need to create a new project - you can skip this step if " -"you already have one." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Address" msgstr "" -#: ../settings/security/third-party/google.rst:15 -msgid "" -"Use this link to create a new project: https://console.cloud.google.com/" -"projectcreate" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.address}``" msgstr "" -#: ../settings/security/third-party/google.rst:18 -msgid "" -"Now expand the menu, expand \"APIs & Services\" and select \"Credentials\". " -"Go to the tab \"OAuth consent screen\" first and ensure to fill in the " -"requested information - without doing so you can't create credentials!" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set" msgstr "" -#: ../settings/security/third-party/google.rst:None -msgid "Creating a consent screen" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Avatar" msgstr "" -#: ../settings/security/third-party/google.rst:25 -msgid "" -"After filling in and saving the consent screen information, you can go to " -"the \"Credentials\" tab and create new \"OAuth client ID\"-Credentials." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/google.rst:28 -msgid "" -"Fill in the necessary information as follows and replace ``zammad_host`` " -"with your FQDN:" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "avatar picture with width and height in pixel (e.g. 60,60)" msgstr "" -#: ../settings/security/third-party/google.rst:31 -msgid "**Application type** ``[x] Web application``" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created at" msgstr "" -#: ../settings/security/third-party/google.rst:34 -msgid "**Authorized JavaScript origins** ``https://zammad_host/``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_at}``" msgstr "" -#: ../settings/security/third-party/google.rst:37 -msgid "" -"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" -"callback``" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC``" msgstr "" -#: ../settings/security/third-party/google.rst:None -msgid "Adding a new OAuth client ID" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Address" msgstr "" -#: ../settings/security/third-party/google.rst:43 -msgid "" -"After creating the credentials, go to your Zammad installation and navigate " -"to \"Admin > Security > Third Party Applications\" > Google. Enter your " -"Client ID and Client secret here." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.address}``" msgstr "" -#: ../settings/security/third-party/google.rst:None -msgid "Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Avatar" msgstr "" -#: ../settings/security/third-party/google.rst:50 -msgid "After submitting, the login via Google can be used." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:2 -msgid "Microsoft" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Department" msgstr "" -#: ../settings/security/third-party/microsoft.rst:4 -msgid "" -"Zammad's Microsoft connection allows your users with Microsoft accounts to " -"login. This works for Azure users as well and can be an alternative to :doc:" -"`/system/integrations/ldap/index`." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.department}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:10 -msgid "" -"This documentation part does not cover our :doc:`📧 Microsoft 365 email " -"channel `." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Sales`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screenshot showing Microsoft login button on Zammad login screen." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Email" msgstr "" -#: ../settings/security/third-party/microsoft.rst:30 -#: ../settings/security/third-party/microsoft.rst:53 -msgid "Supported account types:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.email}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:22 -msgid "" -"Please note that Zammad only supports these account types (App dependent):" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``jdoe@customer.tld``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:35 -msgid "Avatars of signing in users:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Fax" msgstr "" -#: ../settings/security/third-party/microsoft.rst:33 -msgid "" -"Zammad currently ignores user avatars. If the user is registered with e.g. " -"Gravatar, Zammad will fetch the avatar from there if enabled. See :doc:" -"`Zammad Image Service ` for more." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.fax}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:38 -msgid "Step 1 - Register a Microsoft App for Zammad" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``004930123464789`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:40 -msgid "" -"Login to the `Microsoft Azure Portal `_ and " -"navigate to App registrations to create a new app. Provide the requested " -"information as follows and register your app." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Firstname" msgstr "" -#: ../settings/security/third-party/microsoft.rst:46 -msgid "Name:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.firstname}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:45 -msgid "" -"Any meaningful name fitting, this name will be displayed to users trying to " -"authenticate with this app." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``John`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:49 -msgid "Choose one of the above mentioned account types (see Limitations)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Lastname" msgstr "" -#: ../settings/security/third-party/microsoft.rst:51 -msgid "" -"The correct account type depends on your use case. If you want to use the " -"authentication internal only, choose the first option. If you're unsure, use " -"the \"Help me choose...\" link." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.lastname}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:58 -msgid "Redirect URI (optional):" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Login" msgstr "" -#: ../settings/security/third-party/microsoft.rst:56 -msgid "" -"Select web and provide your callback URL. The callback URL looks like this: " -"``https://zammad.domain.tld/auth/microsoft_office365/callback``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.login}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to register a Microsoft app" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Mobile" msgstr "" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "Within **API permissions** add the following permissions:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.mobile}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:69 -msgid "``User.Read``" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``0049176123456789`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "Contacts" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Note" msgstr "" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "``Contacts.Read``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.note}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:73 -msgid "" -"You can find these permissions within *Microsoft Graph → Delegated " -"permissions*." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Some note to this user`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to add required API permissions" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Phone" msgstr "" -#: ../settings/security/third-party/microsoft.rst:80 -msgid "" -"Within **Certificates & secrets** create a new client secret. Note down the " -"returned secret **value** for later. **Do not** use the secret ID!" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.phone}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to create a new app secret" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``004930123456789`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:88 -msgid "" -"From **Overview** copy your apps *Application (client) ID*. If you're using " -"a single tenant app, please also copy *Directory (tenant) ID*. You now have " -"all required information for Zammad." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > VIP" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to retreive application client and tenant IDs" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.vip}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:98 -msgid "Step 2 - Add App Credentials to Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Web" msgstr "" -#: ../settings/security/third-party/microsoft.rst:100 -msgid "" -"Navigate to Security > Third-party Applications (Tab) within Zammad's admin " -"settings. Scroll down to the section *Authentication via Microsoft* and fill " -"in the required information." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.web}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:105 -msgid "App ID:" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``https://zammad.org`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:105 -msgid "This is your *Application (client) ID*." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Department" msgstr "" -#: ../settings/security/third-party/microsoft.rst:108 -msgid "App secret:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.department}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:108 -msgid "This is your *client secret* (value)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Email" msgstr "" -#: ../settings/security/third-party/microsoft.rst:113 -msgid "App Tenant ID:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.email}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:111 -msgid "" -"**optional** only required for apps that use account type *Accounts in this " -"organizational directory only (Default Directory only - Single tenant).*" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Fax" msgstr "" -#: ../settings/security/third-party/microsoft.rst:115 -msgid "" -"Apply your settings by pressing submit and activate *Authentication via " -"Microsoft*." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.fax}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "" -"Screencast showing how to add app credentials and activating the\n" -"authentication method" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Firstname" msgstr "" -#: ../settings/security/third-party/saml.rst:2 -msgid "SAML" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.firstname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:4 -msgid "" -"Connect your SAML (Security Assertion Markup Language) identity provider as " -"a single sign-on (SSO) method." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Lastname" msgstr "" -#: ../settings/security/third-party/saml.rst:7 -msgid "" -"SAML is an open standard for SSO authentication (among other things). Sign-" -"ins are shared across multiple **service providers** and managed by a " -"central **identity provider** (IdP)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.lastname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:11 -msgid "" -"In this case, the service provider is Zammad, and the IdP is a software " -"service that you either host or subscribe to (*e.g.,* `Keycloak `_, `Redhat SSO Server `_, `ADFS `_, or `Okta `_)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Login" msgstr "" -#: ../settings/security/third-party/saml.rst:18 -msgid "" -"This guide assumes you are already using SAML within your organization (i." -"e., that your IdP is fully set up)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.login}``" msgstr "" -#: ../settings/security/third-party/saml.rst:21 -msgid "" -"Please note: Our instructions are based on connecting Zammad with Keycloak." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Mobile" msgstr "" -#: ../settings/security/third-party/saml.rst:25 -msgid "Step 1: Configure Your IdP" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.mobile}``" msgstr "" -#: ../settings/security/third-party/saml.rst:28 -msgid "Add Zammad as a Client/App" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Note" msgstr "" -#: ../settings/security/third-party/saml.rst:30 -msgid "" -"Import Zammad into your IdP using the XML configuration found at ``https://" -"your.zammad.domain/auth/saml/metadata``." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.note}``" msgstr "" -#: ../settings/security/third-party/saml.rst:33 -msgid "" -"If your IdP doesn't support XML import, you will have to configure Zammad as " -"a new client/app manually using the above XML metadata file for reference." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Domain based assignment" msgstr "" -#: ../settings/security/third-party/saml.rst:36 -msgid "For instance, when you see this tag:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.domain_assignment}``" msgstr "" -#: ../settings/security/third-party/saml.rst:42 -msgid "" -"Set the **Assertion Consumer Service Binding URL** (sometimes also listed as " -"**Valid Redirect URIs**) to ``http://your.zammad.domain/auth/saml/callback``." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Domain" msgstr "" -#: ../settings/security/third-party/saml.rst:47 -msgid "Set Up User Attribute Mapping" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.domain}``" msgstr "" -#: ../settings/security/third-party/saml.rst:49 -msgid "" -"Zammad requests the following user attributes (or “properties”) from the IdP:" +#: ../misc/variables/current-user.rst:1 +msgid "``zammad.com`` or empty if not set" msgstr "" -#: ../settings/security/third-party/saml.rst:51 -msgid "Email address (``email``)" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Name" msgstr "" -#: ../settings/security/third-party/saml.rst:52 -msgid "Full name (``name``)" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.name}``" msgstr "" -#: ../settings/security/third-party/saml.rst:53 -msgid "Given name (``first_name``)" +#: ../misc/variables/current-user.rst:1 +msgid "``Zammad GmbH``" msgstr "" -#: ../settings/security/third-party/saml.rst:54 -msgid "Family name (``last_name``)" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Note" msgstr "" -#: ../settings/security/third-party/saml.rst:56 -msgid "" -"You may need to set up “mappers” (or “mappings”) to tell your IdP how user " -"attributes in SAML correspond to those in Zammad. For a more detailed " -"breakdown, refer to the XML metadata file referenced in the previous section." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.note}``" msgstr "" -#: ../settings/security/third-party/saml.rst:62 -msgid "Per-IdP Instructions" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``A note to the organization of the user`` or empty if not set" msgstr "" -#: ../settings/security/third-party/saml.rst:102 -msgid "Keycloak" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Shared organization" msgstr "" -#: ../settings/security/third-party/saml.rst:65 -msgid "" -"**To add Zammad as a client,** save the XML configuration to disk (``https://" -"your.zammad.domain/auth/saml/metadata``) and use **Clients > Clients list > " -"Import client** in the Keycloak admin panel." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.shared}``" msgstr "" -#: ../settings/security/third-party/saml.rst:70 -msgid "" -"To help Zammad **match its own user accounts to Keycloak users**, create a " -"user attribute (or “property”) mapper. In **Clients list**, click on your " -"newly created Client ID, choose the tab **Client scopes** and click on the " -"link which refers to your Zammad instance. Choose **Add mapper > By " -"configuration > User Property** and create a mapper with the following " -"entries:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > VIP" msgstr "" -#: ../settings/security/third-party/saml.rst:78 -msgid "**Name**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.vip}``" msgstr "" -#: ../settings/security/third-party/saml.rst:80 -msgid "**Mapper Type**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Phone" msgstr "" -#: ../settings/security/third-party/saml.rst:81 -msgid "``User Property``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.phone}``" msgstr "" -#: ../settings/security/third-party/saml.rst:82 -msgid "**Property**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated at" msgstr "" -#: ../settings/security/third-party/saml.rst:83 -msgid "``emailAddress``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_at}``" msgstr "" -#: ../settings/security/third-party/saml.rst:84 -msgid "**SAML Attribute Name**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Address" msgstr "" -#: ../settings/security/third-party/saml.rst:86 -msgid "**SAML Attribute NameFormat**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.address}``" msgstr "" -#: ../settings/security/third-party/saml.rst:87 -msgid "``basic``" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Avatar" msgstr "" -#: ../settings/security/third-party/saml.rst:89 -msgid "" -"In the example above, we're telling Zammad that whenever it receives a SAML " -"login request, it should take the ``email`` property from Keycloak, look for " -"a Zammad user with the same ``email`` attribute, and create a new session " -"for that user." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/saml.rst:95 -msgid "" -"If your Keycloak users' email addresses are stored on another property (*e." -"g.,* ``username``), adjust accordingly." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Department" msgstr "" -#: ../settings/security/third-party/saml.rst:98 -msgid "" -"Back in **Settings**, enter the Client ID (``https://your.zammad.domain/auth/" -"saml/metadata``) in the field **Master SAML Processing URL**." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.department}``" msgstr "" -#: ../settings/security/third-party/saml.rst:101 -msgid "You also need to enable **Sign assertions**." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Email" msgstr "" -#: ../settings/security/third-party/saml.rst:105 -msgid "Step 2: Configure Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.email}``" msgstr "" -#: ../settings/security/third-party/saml.rst:107 -msgid "" -"Enable SAML and enter your IdP's details in the Admin Panel under **Settings " -"> Security > Third Party Applications > Authentication via SAML**:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Fax" msgstr "" -#: ../settings/security/third-party/saml.rst:None -msgid "Example configuration of SAML part 1" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.fax}``" msgstr "" -#: ../settings/security/third-party/saml.rst:119 -msgid "Display name" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Firstname" msgstr "" -#: ../settings/security/third-party/saml.rst:116 -msgid "" -"Allows you to define a custom button name for SAML. This helps your users to " -"understand better what the button on the login page does." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.firstname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:119 -msgid "Defaults to ``SAML``." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Lastname" msgstr "" -#: ../settings/security/third-party/saml.rst:123 -msgid "IDP SSO target URL" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.lastname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:122 -msgid "" -"This is the target URL Zammad shall redirect to when the user presses the " -"SAML button. For Keycloak, this needs to look like https://your.domain/" -"realms/your-realm/protocol/saml" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Login" msgstr "" -#: ../settings/security/third-party/saml.rst:127 -msgid "IDP single logout target URL" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.login}``" msgstr "" -#: ../settings/security/third-party/saml.rst:126 -msgid "" -"This is the URL to which the single logout request and response should be " -"sent." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Mobile" msgstr "" -#: ../settings/security/third-party/saml.rst:131 -msgid "IDP certificate" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.mobile}``" msgstr "" -#: ../settings/security/third-party/saml.rst:130 -msgid "" -"The public certificate of your IDP for Zammad to verify during the callback " -"phase." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Note" msgstr "" -#: ../settings/security/third-party/saml.rst:145 -msgid "IDP certificate fingerprint" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.note}``" msgstr "" -#: ../settings/security/third-party/saml.rst:134 -msgid "" -"The fingerprint of your IDPs public certificate to verify during callback " -"phase." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Phone" msgstr "" -#: ../settings/security/third-party/saml.rst:137 -msgid "🔏 **For the IdP certificate / certificate fingerprint:**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.phone}``" msgstr "" -#: ../settings/security/third-party/saml.rst:139 -msgid "" -"Provide **only one or the other**—do not provide both! (Between the two, we " -"recommend the signing certificate itself: fingerprints use SHA-1, which `has " -"been broken for a while now `_.)" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > VIP" msgstr "" -#: ../settings/security/third-party/saml.rst:144 -msgid "" -"**Keycloak users:** Find your certificate in the Keycloak admin panel under " -"**Realm Settings > Keys > Algorithm: RS256 > Certificate**." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.vip}``" msgstr "" -#: ../settings/security/third-party/saml.rst:151 -msgid "Name identifier format" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``false`` or ``true``" msgstr "" -#: ../settings/security/third-party/saml.rst:148 -msgid "" -"This is the unique identifiers field type. Usually it should be ``urn:oasis:" -"names:tc:SAML:1.1:nameid-format:emailAddress``." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Web" msgstr "" -#: ../settings/security/third-party/saml.rst:151 -msgid "Zammad **expects an email address as unique identifier**!" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.web}``" msgstr "" -#: ../settings/security/third-party/saml.rst:155 -msgid "UID attribute name" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > VIP" msgstr "" -#: ../settings/security/third-party/saml.rst:154 -msgid "" -"Here you can define an attribute that uniquely identifies the user. If " -"unset, the name identifier returned by the IDP is used." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.vip}``" msgstr "" -#: ../settings/security/third-party/saml.rst:None -msgid "Example configuration of SAML part 2" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Web" msgstr "" -#: ../settings/security/third-party/saml.rst:163 -msgid "" -"Decide if the certificate for the connection to the IdP service has to be " -"verified or not (default: ``yes``)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.web}``" msgstr "" -#: ../settings/security/third-party/saml.rst:169 -msgid "Signing & Encrypting" +#: ../misc/variables/ticket.rst:6 +msgid "" +"Below you can find all available ticket-based variables within Zammad. These " +"can be called via triggers for example. If you're unsure if Zammad does " +"support variables at the point you're at, you can try to type ``::`` to " +"check." msgstr "" -#: ../settings/security/third-party/saml.rst:169 -msgid "" -"Define if you want to sign, encrypt, do both or nothing for the requests." +#: ../misc/variables/ticket.rst:12 +msgid "Ticket Variables" msgstr "" -#: ../settings/security/third-party/saml.rst:179 -msgid "Certificate (PEM)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Accounted Time" msgstr "" -#: ../settings/security/third-party/saml.rst:172 -msgid "" -"Paste the public certificate of your Zammad SAML client, if you want to " -"encrypt the requests." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.time_unit}``" msgstr "" -#: ../settings/security/third-party/saml.rst:175 -msgid "Make sure the certificate is:" +#: ../misc/variables/ticket.rst:1 +msgid "``1``, ``2.75`` or empty response" msgstr "" -#: ../settings/security/third-party/saml.rst:177 -msgid "already valid and not yet expired" +#: ../misc/variables/ticket.rst:1 +msgid "``3``, any number of articles existing in the ticket right now" msgstr "" -#: ../settings/security/third-party/saml.rst:178 -msgid "no CA certificate" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Closing time" msgstr "" -#: ../settings/security/third-party/saml.rst:179 -msgid "valid for signing and encrypting" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.close_at}``" msgstr "" -#: ../settings/security/third-party/saml.rst:185 -msgid "Private key (PEM)" +#: ../misc/variables/ticket.rst:1 +msgid "2019-10-07 17:25:00 UTC" msgstr "" -#: ../settings/security/third-party/saml.rst:182 -msgid "" -"Paste the private key of your Zammad SAML client here, if you want to sign " -"the requests." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created at" msgstr "" -#: ../settings/security/third-party/saml.rst:185 -msgid "Make sure the key is an RSA key with a length of at least 2048 bits." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_at}``" msgstr "" -#: ../settings/security/third-party/saml.rst:188 -msgid "Private key secret" +#: ../misc/variables/ticket.rst:1 +msgid "2019-10-07 16:25:00 UTC" msgstr "" -#: ../settings/security/third-party/saml.rst:188 -msgid "If your private key is secured with a secret, you can provide it here." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Address" msgstr "" -#: ../settings/security/third-party/saml.rst:192 -msgid "Your callback URL" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.address}``" msgstr "" -#: ../settings/security/third-party/saml.rst:191 -msgid "" -"This URL is needed for your IdP configuration so it knows where to redirect " -"to after successful authentication." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Avatar" msgstr "" -#: ../settings/security/third-party/saml.rst:194 -msgid "" -"After saving your input by clicking on the \"Submit\" button, Zammad " -"verifies the provided keys/certificates (e.g. if they are valid for signing/" -"encrypting and if they aren't expired)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/saml.rst:199 -msgid "" -"See :ref:`automatic account linking ` for details " -"on how to link existing Zammad accounts to IdP accounts." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Department" msgstr "" -#: ../settings/security/third-party/saml.rst:205 -msgid "Automatic account linking doesn't work" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.department}``" msgstr "" -#: ../settings/security/third-party/saml.rst:206 -msgid "" -"Have you double-checked your IdP's user attribute mapping configuration?" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Email" msgstr "" -#: ../settings/security/third-party/twitter.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via Twitter. To do " -"so, you need to follow these steps:" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.email}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:8 -msgid "Register Twitter App" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Fax" msgstr "" -#: ../settings/security/third-party/twitter.rst:10 -msgid "Go to https://dev.twitter.com/apps and login with your account." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.fax}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:15 -msgid "Click on \"Create App\"" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Firstname" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "new app page" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.firstname}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:20 -msgid "" -"Enter app settings. As \"Callback URL\" you need to enter ``https://" -"zammad_host/api/v1/external_credentials/twitter/callback``. You need to " -"replace ``zammad_host`` with the domain of your Zammad system." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Lastname" msgstr "" -#: ../settings/security/third-party/twitter.rst:24 -msgid "" -"After the app has been created, update the application icon and organization " -"attributes." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.lastname}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "set permissions to receive and send direct messages" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Login" msgstr "" -#: ../settings/security/third-party/twitter.rst:30 -msgid "" -"Next we need to set ``read, write and access direct messages`` permissions " -"for the app." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.login}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "click on Keys & Access Token, note them" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Mobile" msgstr "" -#: ../settings/security/third-party/twitter.rst:36 -msgid "" -"Go to \"Keys and Access Token\" tab and note the \"Consumer Key\" and " -"\"Consumer Secret\"." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.mobile}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:40 -msgid "Configure Zammad as Twitter App" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Note" msgstr "" -#: ../settings/security/third-party/twitter.rst:42 -msgid "" -"Go to \"Admin > Security > Twitter > Third Party Applications > Twitter\" " -"Section." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.note}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "Admin > Security > Third Party Applications" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Phone" msgstr "" -#: ../settings/security/third-party/twitter.rst:48 -msgid "" -"Fill in the \"Twitter Key\" and the \"Twitter Secret\" and click the " -"\"Submit\" button." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.phone}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:51 -msgid "" -"Now you can link accounts via \"Avatar > Profile > Link Accounts\" or login " -"via Zammad login page." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > VIP" msgstr "" -#: ../settings/security/two-factor.rst:11 -msgid "Two-factor Authentication Methods" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.vip}``" msgstr "" -#: ../settings/security/two-factor.rst:2 -msgid "Two-Factor Authentication" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Web" msgstr "" -#: ../settings/security/two-factor.rst:4 -msgid "" -"Two-factor authentication (2FA) enhances the security of Zammad accounts by " -"adding an extra layer of verification beyond a password. It requires users " -"to provide two different types of authentication factors, typically " -"something they know (like a password) and something they possess (like a " -"mobile device or a security token), to ensure that only authorized " -"individuals can access the account." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.web}``" msgstr "" -#: ../settings/security/two-factor.rst:19 -msgid "Enable Recovery Codes" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Address" msgstr "" -#: ../settings/security/two-factor.rst:21 -msgid "" -"Recovery codes are one-time use security codes that can be used by the user " -"if they lose access to their other two-factor authentication methods. They " -"cannot be used on their own, they can only be activated if at least one two-" -"factor authentication method is enabled." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.address}``" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Enable Recovery Codes Setting" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Avatar" msgstr "" -#: ../settings/security/two-factor.rst:30 -msgid "" -"Recovery codes can only be used as a backup method. If enabled, they will be " -"automatically generated for the user once they set up their initial two-" -"factor authentication method." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.avatar(60,60)}``" msgstr "" -#: ../settings/security/two-factor.rst:34 -msgid "" -"The user will be asked to print out or save the generated recovery codes in " -"a safe place. Once used, a recovery code cannot be reused." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Department" msgstr "" -#: ../settings/security/two-factor.rst:37 -msgid "" -"Users will also have an option to regenerate their recovery codes at any " -"time, which invalidates already existing recovery codes and provides them " -"with a list of fresh codes." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.department}``" msgstr "" -#: ../settings/security/two-factor.rst:41 -msgid "" -"After you enable this setting, when the user completes a setup of their " -"initial two-factor authentication method, they will be presented with a list " -"of recovery codes and instructed to save them for later use." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Email" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Recovery Codes Generation Modal Dialog" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.email}``" msgstr "" -#: ../settings/security/two-factor.rst:50 -msgid "Enforce the Set Up of the Two-Factor Authentication" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Fax" msgstr "" -#: ../settings/security/two-factor.rst:52 -msgid "" -"In case you wish to require your users to set up at least one two-factor " -"authentication method for their account, you can do this by selecting " -"specific user roles the requirement applies to in **Enforced for user " -"roles** setting. Of course you must have at least one two-factor " -"authentication method enabled for this setting to take effect." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.fax}``" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Enforced for User Roles Setting" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Firstname" msgstr "" -#: ../settings/security/two-factor.rst:62 -msgid "" -"After you change this setting, if the user has one of the selected roles on " -"their account, they will be forced to set up the two-factor authentication " -"upon next sign in or application reload." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.firstname}``" msgstr "" -#: ../settings/security/two-factor.rst:66 -msgid "" -"A modal dialog with instructions will be shown, and they will not be able to " -"do any work before they set up at least one two-factor method." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Lastname" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Modal Dialog for Enforcing Two-Factor Authentication Set Up" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.lastname}``" msgstr "" -#: ../settings/security/two-factor.rst:74 -msgid "Reset Two-Factor Authentication for a Specific User" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Login" msgstr "" -#: ../settings/security/two-factor.rst:76 -msgid "" -"In case an user isn't able to login anymore because of an inaccessible " -"second factor, you can reset the user's 2FA method." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.login}``" msgstr "" -#: ../settings/security/two-factor.rst:79 -msgid "" -"To do this, go to the user management and search for the relevant user. " -"After you found the account, click the button in the action column and " -"select \"Manage Two-Factor Authentication\":" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Mobile" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Context menu in action column in user management" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.mobile}``" msgstr "" -#: ../settings/security/two-factor.rst:87 -msgid "" -"After selecting this, you can see a dialog where you can either reset one " -"2FA method or reset all of the user's 2FA methods:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Note" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Dialog for resetting user's 2FA method" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.note}``" msgstr "" -#: ../settings/security/two-factor.rst:94 -msgid "" -"Choose the fitting one, click on the corresponding \"Remove ...\" button and " -"confirm your action. The user now has to setup a new 2FA method, depending " -"on your 2FA configuration." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Phone" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:2 -msgid "Authenticator App" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.phone}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:4 -msgid "" -"The authenticator app method is a type of two-factor authentication that " -"uses a mobile application to generate one-time codes for account " -"verification. After setting up the authenticator app on their device, the " -"user links it to their Zammad account." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > VIP" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:12 -msgid "" -"When logging in, the user is prompted to enter a time-sensitive code " -"generated by the app, in addition to their password. This code acts as the " -"second factor of authentication, providing an extra layer of security as it " -"changes periodically and is unique to the user's device." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.vip}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:None -msgid "Security Code in Google Authenticator App" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Web" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:22 -msgid "" -"The app generates codes based on a shared secret key stored securely on both " -"the user's device and the server, ensuring a synchronized and secure " -"authentication process. The method of generating the codes is sometimes also " -"called TOTP (time-based one-time password)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.web}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:28 -msgid "Enabling the Authenticator App Method" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Escalation at" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:30 -#: ../settings/security/two-factor/security-keys.rst:28 -msgid "To enable the method, just toggle the switch on in the settings." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.escalation_at}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:None -msgid "Authenticator App Switch in Settings" +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:36 -msgid "" -"Now the users will be able to set up this two-factor authentication method " -"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " -"Once they do, on next sign-in with password, they will be asked to provide " -"an additional security code generated by their mobile device." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > First response" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:2 -msgid "Security Keys" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.first_response_at}``" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:4 -msgid "" -"The security keys method is a type of a two-factor authentication that uses " -"Web Authentication API in the browser for verifying user's identity. The " -"user can register multiple hardware or software security keys with their " -"Zammad account and then they can use it during the sign-in process." +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable yet" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:12 -msgid "" -"When logging in, the user is prompted to provide the same security key they " -"registered with their account, in addition to their password. This key acts " -"as the second factor of authentication, providing an extra layer of security." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Assign Follow-Ups" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:None -msgid "Security Key dialog in Safari on macOS" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_assignment}``" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:21 -msgid "" -"The type of the key can range from hardware USB sticks to passkeys stored in " -"a device of user's choice. Which type can be used depends on the browser " -"flavor and the platform of the user." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Assignment Timeout" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:26 -msgid "Enabling the Security Keys Method" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.assignment_timeout}``" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:None -msgid "Security Keys Switch in Settings" +#: ../misc/variables/ticket.rst:1 +msgid "``20`` or empty if not configured" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:34 -msgid "" -"Now the users will be able to set up this two-factor authentication method " -"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " -"Once they do, on next sign-in with password, they will be asked to provide " -"the same security key they registered during the setup." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Follow-up possible" msgstr "" -#: ../settings/system/system-selfhosted.include.rst:3 -msgid "" -"Below settings are only available to self hosted users. In hosted " -"environments we're handling these settings for you to ensure service " -"stability." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_possible}``" msgstr "" -#: ../settings/system/base.rst:11 -msgid "Fully Qualified Domain Name" +#: ../misc/variables/ticket.rst:1 +msgid "``no`` or ``yes``" msgstr "" -#: ../settings/system/base.rst:7 -msgid "The URL of your Zammad installation." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Name" msgstr "" -#: ../settings/system/base.rst:9 ../settings/system/base.rst:17 -msgid "This setting is used within :doc:`/system/variables` and notifications." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.name}``" msgstr "" -#: ../settings/system/system-base.include.rst:1 -msgid "It is automatically set by the *Getting Started wizard*." +#: ../misc/variables/ticket.rst:1 +msgid "``Sales``" msgstr "" -#: ../settings/system/system-base.include.rst:5 -msgid "Changing this setting also changes callback URLs for your channels etc." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Note" msgstr "" -#: ../settings/system/system-base.include.rst:6 -msgid "This setting can have negative affects on being able to login." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.note}``" msgstr "" -#: ../settings/system/base.rst:19 -msgid "HTTP type" +#: ../misc/variables/ticket.rst:1 +msgid "``Note about this group``" msgstr "" -#: ../settings/system/base.rst:14 -msgid "" -"The HTTP type tells your installation how your clients connect. This is " -"relevant for authentication and cookie security." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > ID" msgstr "" -#: ../settings/system/base.rst:31 -msgid "SystemID" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.id}``" msgstr "" -#: ../settings/system/base.rst:22 -msgid "" -"This ID is being used within your ticket number. In case you're " -"communicating with another ticket system with similar ticket number schemes " -"this ID greatly reduces the risk of false follow ups." +#: ../misc/variables/ticket.rst:1 +msgid "``17``, ``5281``, ..." msgstr "" -#: ../settings/system/base.rst:26 -msgid "" -"The SystemID is randomly selected upon installation of Zammad (``1-99``)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact (agent)" msgstr "" -#: ../settings/system/base.rst:30 -msgid "" -"**Do not** change this setting in a productive system! Your Zammad " -"installation may no longer recognize old ticket number based follow ups upon " -"change!" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_agent_at}``" msgstr "" -#: ../settings/system/frontend.rst:2 -msgid "Frontend" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact (customer)" msgstr "" -#: ../settings/system/frontend.rst:22 -msgid "Core Workflow Ajax Mode" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_customer_at}``" msgstr "" -#: ../settings/system/frontend.rst:6 +#: ../misc/variables/ticket.rst:1 msgid "" -"This setting allows administrators to enforce :doc:`/system/core-workflows` " -"to use Ajax-Calls instead of web sockets. You'll usually only need this if " -"you experience serious issues as noted below." +"``2019-10-07 16:25:00 UTC`` or empty if not applicable yet (Please note " +"`Ticket last contact behavior Settings `_ for this)" msgstr "" -#: ../settings/system/frontend.rst:10 -msgid "**🤓 Possible (technical) reasons**" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact" msgstr "" -#: ../settings/system/frontend.rst:12 -msgid "" -"In some cases, your network structure (e.g. firewalls, proxies) may " -"disconnect long web socket connections. This leads to select fields staying " -"empty (e.g. owner selection *after* selecting your group) or fields not " -"shown / hidden (e.g. when switching to or from pending states, the \"pending " -"till\" field not showing / hiding)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_at}``" msgstr "" -#: ../settings/system/frontend.rst:18 -msgid "" -"Please keep in mind that the Ajax fallback may cause serious pressure on " -"your application server. If you have the choice stick to web sockets." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Number" msgstr "" -#: ../settings/system/frontend.rst:22 -msgid "Default: ``no`` (inactive)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.number}``" msgstr "" -#: ../settings/system/frontend.rst:53 -msgid "Show calendar weeks in the picker of date/datetime fields" +#: ../misc/variables/ticket.rst:1 +msgid "``31001``, ``201910731001``, ..." msgstr "" -#: ../settings/system/frontend.rst:25 -msgid "" -"With this setting you can instruct Zammad to provide week number display " -"globally for all users. Calendar with week number display are usually used " -"in business sectors and may not be relevant for everyone." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain based assignment" msgstr "" -#: ../settings/system/frontend.rst:29 -msgid "" -"This setting affects *all areas* - you'll also see week numbers in the admin " -"panel for e.g. triggers and macros." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain_assignment}``" msgstr "" -#: ../settings/system/frontend.rst:32 -msgid "Default: ``no`` (not shown)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain" msgstr "" -#: ../settings/system/frontend.rst:53 -msgid "Here's the difference:" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain}``" msgstr "" -#: ../settings/system/frontend.rst:0 -msgid "Screenshot showing Zammad's date picker (in the default way)" +#: ../misc/variables/ticket.rst:1 +msgid "``domain.tld`` or empty if not set" msgstr "" -#: ../settings/system/frontend.rst:41 -msgid "Set to ``no``" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Name" msgstr "" -#: ../settings/system/frontend.rst:0 -msgid "" -"Screenshot showing Zammad's date picker with\n" -"week numbers enabled" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.name}``" msgstr "" -#: ../settings/system/frontend.rst:50 -msgid "Set to ``yes``" +#: ../misc/variables/ticket.rst:1 +msgid "``Zammad GmbH`` or empty if not set" msgstr "" -#: ../settings/system/index.rst:4 -msgid "" -"For your overview we split each tab within system settings into its own page:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Note" msgstr "" -#: ../settings/system/index.rst:16 -msgid "Console Based Settings" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.note}``" msgstr "" -#: ../settings/system/index.rst:18 -msgid "" -"There's some console based settings we didn't put into the UI. However, you " -"may find them helpful - you can find them in our :docs:`hidden settings ` section." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Shared organization" msgstr "" -#: ../settings/system/network.rst:2 -msgid "Network" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.shared}``" msgstr "" -#: ../settings/system/network.rst:8 -msgid "" -"The proxy settings can only be saved after successfully testing the proxy " -"connection." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > VIP" msgstr "" -#: ../settings/system/network.rst:15 -msgid "Proxy Address." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.vip}``" msgstr "" -#: ../settings/system/network.rst:12 -msgid "" -"Allows you to provide a proxy server if needed. This is relevant for network " -"communication by Zammad." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Address" msgstr "" -#: ../settings/system/network.rst:15 -msgid "It **does not** affect the update process or Elasticsearch." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.address}``" msgstr "" -#: ../settings/system/network.rst:18 -msgid "Username for proxy connection." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Avatar" msgstr "" -#: ../settings/system/network.rst:18 -msgid "" -"If your proxy server requires authentication, provide the username here." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.avatar(60,60)}``" msgstr "" -#: ../settings/system/network.rst:21 -msgid "Password for proxy connection." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Department" msgstr "" -#: ../settings/system/network.rst:21 -msgid "" -"If your proxy server requires authentication, provide the password here." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.department}``" msgstr "" -#: ../settings/system/network.rst:26 -msgid "No proxy for the following hosts." +#: ../misc/variables/ticket.rst:1 +msgid "``Support`` or empty if not set" msgstr "" -#: ../settings/system/network.rst:24 -msgid "" -"Exception list for hosts you can't or don't want to reach via proxy server." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Email" msgstr "" -#: ../settings/system/network.rst:27 -msgid "Default: ``localhost,127.0.0.0,::1``" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.email}``" msgstr "" -#: ../settings/system/services.rst:2 -msgid "Services" +#: ../misc/variables/ticket.rst:1 +msgid "``agent@company.tld`` or empty if not set" msgstr "" -#: ../settings/system/services.rst:10 -msgid "Image Service" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Fax" msgstr "" -#: ../settings/system/services.rst:5 -msgid "Defines the backend for user and organization image lookups." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.fax}``" msgstr "" -#: ../settings/system/services.rst:7 -msgid "Default: ``Zammad Image Service`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Firstname" msgstr "" -#: ../settings/system/services.rst:9 -msgid "" -"Make sure your on premise installation has ``HTTPS`` access to ``images." -"zammad.com``." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.firstname}``" msgstr "" -#: ../settings/system/services.rst:18 -msgid "Geo Calendar Service" +#: ../misc/variables/ticket.rst:1 +msgid "``Max`` or empty if not set" msgstr "" -#: ../settings/system/services.rst:13 -msgid "" -"Defines the backend for geo calendar lookups. Used for initial calendar " -"setup." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Lastname" msgstr "" -#: ../settings/system/services.rst:16 -msgid "Default: ``Zammad GeoCalendar Service`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.lastname}``" msgstr "" -#: ../settings/system/services.include.rst:2 -msgid "" -"Make sure your on premise installation has ``HTTPS`` access to ``geo.zammad." -"com``." +#: ../misc/variables/ticket.rst:1 +msgid "``Mustermann`` or empty if not set" msgstr "" -#: ../settings/system/services.rst:26 -msgid "Geo IP Service" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Login" msgstr "" -#: ../settings/system/services.rst:21 -msgid "" -"Defines the backend for geo IP lookups. Shows also location of an IP address " -"if an IP address is shown." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.login}``" msgstr "" -#: ../settings/system/services.rst:24 -msgid "Default: ``Zammad GeoIP Service`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "``agent``" msgstr "" -#: ../settings/system/services.rst:32 -msgid "Geo Location Service" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Mobile" msgstr "" -#: ../settings/system/services.rst:29 -msgid "" -"Defines the backend for geo location lookups to store geo locations for " -"addresses." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.mobile}``" msgstr "" -#: ../settings/system/services.rst:32 -msgid "" -"Default: ``OpenStreetMap (ODbL 1.0, http://osm.org/copyright)`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Note" msgstr "" -#: ../settings/system/services.rst:36 -msgid "" -"You can find a detailed privacy information on what we store for how long on " -"our :docs:`Privacy Appendix ` inside of our System " -"Documentation." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.note}``" msgstr "" -#: ../settings/system/storage.rst:2 -msgid "Storage" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Phone" msgstr "" -#: ../settings/system/storage.rst:6 -msgid "" -"Here you can define where Zammad stores attachments for tickets and the " -"knowledge base. By default, we're writing to the ``Database`` - you can " -"switch to ``Filesystem`` or ``Simple Storage (S3)`` at any time. In this " -"case please have a look on the following instructions." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.phone}``" msgstr "" -#: ../settings/system/storage.rst:11 -msgid "" -"If you have a busy Zammad instance, we strongly encourage you to use " -"filesystem storage instead of \"Database\". This will greatly improve system " -"performance (de-crease database load and size)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > VIP" msgstr "" -#: ../settings/system/storage.rst:19 -msgid "Database" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.vip}``" msgstr "" -#: ../settings/system/storage.rst:17 -msgid "" -"This is the default storage method. The attachments are stored directly in " -"the database. If your Zammad instance grows, we recommend one of the other " -"methods to maintain performance." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Web" msgstr "" -#: ../settings/system/storage.rst:38 -msgid "Filesystem" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.web}``" msgstr "" -#: ../settings/system/storage.rst:22 -msgid "" -"This storage method is recommended for all Zammad instances, especially for " -"those with a higher load. If you choose filesystem, your files are written " -"to ``/opt/zammad/storage/``." +#: ../misc/variables/ticket.rst:1 +msgid "``https://zammad.com`` or empty if not set" msgstr "" -#: ../settings/system/storage.rst:26 -msgid "" -"Moving attachments from \"Database\" to \"Filesystem\" can be run during " -"production use. However, you should consider your framework conditions (e.g. " -"bandwidth, system load in production) to define the right moment." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Pending till" msgstr "" -#: ../settings/system/storage.rst:32 -msgid "**You noticed slow updates of Zammad?**" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.pending_time}``" msgstr "" -#: ../settings/system/storage.rst:34 -msgid "" -"While Zammad is beeing updated, it enforces a recursive \"change " -"owner\" (chown) for this directory. For instances with many files this can " -"be time consuming. To mitigate that you can move your files and create a " -"symlink in ``/opt/zammad/storage/`` to the new directory. Of course you have " -"to make sure on your own that the permissions are always correct." +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not set" msgstr "" -#: ../settings/system/storage.rst:95 -msgid "Simple Storage (S3)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Priority > Name" msgstr "" -#: ../settings/system/storage.rst:41 -msgid "" -"To use the Simple Storage (S3), you have to provide some settings, which " -"can't be accessed in the UI (see instructions below)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.priority.name}``" msgstr "" -#: ../settings/system/storage.rst:44 -msgid "" -"⚠️ Please note that the current implementation is in its early stages and can " -"be modified in the future." +#: ../misc/variables/ticket.rst:1 +msgid "``2 normal``" msgstr "" -#: ../settings/system/storage.rst:47 -msgid "" -"The prerequisite is to have access to a S3-compatible storage and to have " -"all necessary parameters available (which depends on your storage provider; " -"if in doubt, please ask there for help)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > State > Name" msgstr "" -#: ../settings/system/storage.rst:51 -msgid "Steps to configure S3:" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.state.name}``" msgstr "" -#: ../settings/system/storage.rst:53 -msgid "" -"Copy ``config/zammad/storage.yml.dist`` to ``config/zammad/storage.yml``" +#: ../misc/variables/ticket.rst:1 +msgid "``new``, ``open``, ..." msgstr "" -#: ../settings/system/storage.rst:54 -msgid "Edit the copied file in one of the following ways:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Tags" msgstr "" -#: ../settings/system/storage.rst:56 -msgid "" -"Either provide your S3 configuration with one attribute per line like in the " -"upper area of the file" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.tags}``" msgstr "" -#: ../settings/system/storage.rst:58 +#: ../misc/variables/ticket.rst:1 msgid "" -"Or provide your S3 configuration as an URL (which you can find at the end of " -"the file). Note: you can also provide this URL as environment variable (:" -"docs:`see system documentation `) without using this yml-file." +"Currently not available, see `Issue 2769 `_" msgstr "" -#: ../settings/system/storage.rst:62 -msgid "" -"We recommend the deletion of the not used configuration style to avoid " -"inconsistencies." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Title" msgstr "" -#: ../settings/system/storage.rst:65 -msgid "Restart Zammad so the config file / environment variable is loaded" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.title}``" msgstr "" -#: ../settings/system/storage.rst:66 +#: ../misc/variables/ticket.rst:1 msgid "" -"Set the \"Storage Method\" in Zammad to ``Simple Storage (S3)`` in Settings " -"> System > Storage and click on \"Submit\". After that, Zammad checks your " -"configuration and the connection to the service and will raise an error " -"message if something is wrong." +"``My amazing Subject`` (normally subject, can be edited within Interface and " +"thus differ)" msgstr "" -#: ../settings/system/storage.rst:72 -msgid "A very simple storage configuration could look like this:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated at" msgstr "" -#: ../settings/system/storage.rst:85 -msgid "" -"Before setting the storage method to ``Simple Storage (S3)`` (step 4), " -"please make sure to have a working setup." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_at}``" msgstr "" -#: ../settings/system/storage.rst:88 -msgid "" -"You can verify this by running ``rails r 'Rails.logger = Logger.new(STDOUT); " -"pp Store::Provider::S3.ping?'`` in your Zammad directory. If everything is " -"fine, you should see ``true``, else you should see ``false`` and a simple " -"error message." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Address" msgstr "" -#: ../settings/system/storage.rst:93 -msgid "" -"If you installed Zammad through a package manager (rather than from source), " -"replace ``rails r`` with ``zammad run rails r`` above. To learn more, see :" -"docs:`Administration via Console `." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.address}``" msgstr "" -#: ../settings/ticket.rst:4 -msgid "" -"Here you can adjust general ticket settings. Additional ones for the ticket " -"composer interface can be found in the :doc:`/misc/composer`." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Avatar" msgstr "" -#: ../settings/ticket.rst:11 -msgid "Ticket Hook (default: ``Ticket#``)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.avatar(60,60)}``" msgstr "" -#: ../settings/ticket.rst:11 -msgid "The identifier for a ticket; *e.g.,* Ticket#, Call#, MyTicket#." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Department" msgstr "" -#: ../settings/ticket.rst:38 -msgid "Ticket Hook Position (default: ``right``)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.department}``" msgstr "" -#: ../settings/ticket.rst:14 -msgid "" -"With this setting you can decide (if) where to insert the ticket number." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Email" msgstr "" -#: ../settings/ticket.rst:20 -msgid "*Right*" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.email}``" msgstr "" -#: ../settings/ticket.rst:17 -msgid "" -"This setting will add the ticket reference on the right site of the subject." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Fax" msgstr "" -#: ../settings/ticket.rst:20 -msgid "Example: ``Some Subject [Ticket#12345]``" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.fax}``" msgstr "" -#: ../settings/ticket.rst:26 -msgid "*Left*" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Firstname" msgstr "" -#: ../settings/ticket.rst:23 -msgid "" -"This setting will add the ticket reference on the left site of the subject." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.firstname}``" msgstr "" -#: ../settings/ticket.rst:26 -msgid "Example: ``[Ticket#12345] Some Subject``" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Lastname" msgstr "" -#: ../settings/ticket.rst:29 -msgid "*None*" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.lastname}``" msgstr "" -#: ../settings/ticket.rst:29 -msgid "This will completely remove ticket references from the subject." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Login" msgstr "" -#: ../settings/ticket.rst:33 -msgid "" -"Please ensure to take a look at :doc:`/channels/email/settings` within the " -"email channel to ensure you have at least one reference that helps Zammad to " -"assign follow-ups correctly." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.login}``" msgstr "" -#: ../settings/ticket.rst:37 -msgid "" -"Disabling this and not setting up any further follow up search will lead to " -"unexpected results!" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Mobile" msgstr "" -#: ../settings/ticket.rst:65 -msgid "" -"Ticket Last Contact Behaviour (default: ``Use the start time of the last " -"customer thread (which may consist of multiple articles).``)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.mobile}``" msgstr "" -#: ../settings/ticket.rst:41 -msgid "" -"This setting changes the way Zammad updates the ``Last Contact`` value of a " -"ticket. This is fairly important for overviews and what you expect upon " -"ticket updates of a customer." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Note" msgstr "" -#: ../settings/ticket.rst:52 -msgid "" -"Use the start time of the last customer thread (which may consist of " -"multiple articles)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.note}``" msgstr "" -#: ../settings/ticket.rst:46 -msgid "" -"If this option is chosen, Zammad will update the last updated value just " -"once if a customer replies. After that, Zammad will wait for an agent to " -"react." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Phone" msgstr "" -#: ../settings/ticket.rst:50 -msgid "" -"This comes in handy if you want to work tickets in the order of their first " -"update. This will not change ticket orders if customers decide to \"bump\" " -"the ticket affected." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.phone}``" msgstr "" -#: ../settings/ticket.rst:57 -msgid "Use the time of the very last customer article." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > VIP" msgstr "" -#: ../settings/ticket.rst:55 -msgid "" -"When setting this option, Zammad will always update the last updated value. " -"This means that if ordering by ``Last Update``, ticket orders will change if " -"customers \"bump\" the ticket." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.vip}``" msgstr "" -#: ../settings/ticket.rst:64 -msgid "Last contact value used on :doc:`/manage/overviews`" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Web" msgstr "" -#: ../settings/ticket.rst:65 -msgid "Last contact value used on :doc:`/manage/trigger`" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.web}``" msgstr "" -#: ../settings/ticket.rst:88 -msgid "" -"Ticket Organization Reassignment (default: ``Update the most recent tickets." -"``)" +#: ../settings/branding.rst:10 +msgid "Product Name" msgstr "" -#: ../settings/ticket.rst:68 +#: ../settings/branding.rst:7 msgid "" -"This setting changes the way Zammad updates the organization field of the " -"tickets whenever the primary organization of a user is changed." -msgstr "" - -#: ../settings/ticket.rst:74 -msgid "Update the most recent tickets." +"Defines the name of the application, shown in the web interface, tabs and " +"title bar of the web browser." msgstr "" -#: ../settings/ticket.rst:72 -msgid "" -"If this option is chosen, Zammad will update the 100 most recent tickets " -"where the user is the ticket customer. The ticket organization field will be " -"automatically set to the new primary organization of the user." +#: ../settings/branding.rst:10 +msgid "Default value: ``Zammad Helpdesk``" msgstr "" -#: ../settings/ticket.rst:88 -msgid "Do not update any tickets." +#: ../settings/branding.rst:13 +msgid "Will be shown in the app and is included in email footers." msgstr "" -#: ../settings/ticket.rst:77 -msgid "" -"When choosing this option, Zammad will not update any tickets when the " -"user's primary organization is changed." +#: ../settings/branding.rst:19 +msgid "Logo" msgstr "" -#: ../settings/ticket.rst:80 -msgid "**Use with care!**" +#: ../settings/branding.rst:16 +msgid "Defines the logo of the application, shown in the login page of Zammad." msgstr "" -#: ../settings/ticket.rst:82 +#: ../settings/branding.rst:18 msgid "" -"Using this option may lead to inconsistencies in the system as the ticket " -"organization may become decoupled from the ticket customer." +"Ensure to hit the \"Submit\" button after uploading the logo. Otherwise your " +"change will not be saved." msgstr "" -#: ../settings/ticket.rst:85 +#: ../settings/branding.rst:22 msgid "" -"However, you may use this option if you wish to maintain :ref:`the shared " -"access ` to the ticket for all organization " -"members of the original organization of the customer." +"Allows to set the default language of the Zammad instance. The here defined " +"locale mostly acts as a fallback for:" msgstr "" -#: ../settings/ticket.rst:110 -msgid "Ticket Number Format (default: ``Increment (SystemID.Counter)``)" +#: ../settings/branding.rst:25 +msgid "user preferences (if Zammad can't detect the users locale)" msgstr "" -#: ../settings/ticket.rst:94 -msgid "" -"This setting defines the way Zammad's ticket number will look. Changing this " -"setting in production will cause follow up detection to fail." +#: ../settings/branding.rst:26 +msgid "CSV output (reporting, time accounting)" msgstr "" -#: ../settings/ticket.rst:102 -msgid "Increment (SystemID.Counter)" +#: ../settings/branding.rst:30 +msgid "Define the timezone of your Zammad installation." msgstr "" -#: ../settings/ticket.rst:98 +#: ../settings/branding.rst:32 msgid "" -"The increment value contains the SystemID (automatically generated during " -"installation) and a increment which counts up with every new Ticket. The " -"increment will automatically get another digit if needed." +"This does not have any effect on timings for your agents or how Zammad " +"stores date and time values." msgstr "" -#: ../settings/ticket.rst:102 -msgid "Examples: ``1010138``, ``1010139``" +#: ../settings/branding.rst:35 +msgid "Changing this value has direct consequences on the following areas:" msgstr "" -#: ../settings/ticket.rst:110 -msgid "Date (Year.Month.Day.SystemID.Counter)" +#: ../settings/branding.rst:37 +msgid ":doc:`/manage/scheduler` tasks" msgstr "" -#: ../settings/ticket.rst:105 -msgid "" -"This version of the ticket number is fairly long. However, because it " -"contains the date of ticket creation, it also allows you to see when the " -"ticket has been created. You may feel familiar with this number format if " -"you've worked with OTRS already." +#: ../settings/branding.rst:38 +msgid "search indexing (and thus reporting)" msgstr "" -#: ../settings/ticket.rst:110 -msgid "Examples: ``201206231010138``, ``201206231010139``" +#: ../settings/branding.rst:40 +msgid "calendar subscriptions" msgstr "" -#: ../settings/ticket.rst:137 -msgid "OPTIONS" +#: ../settings/branding.rst:41 +msgid "browser printing" msgstr "" -#: ../settings/ticket.rst:113 +#: ../settings/branding.rst:43 msgid "" -"The below options allow you to further customize your ticket number. The " -"availability of options differ depending of the chosen ticket number format " -"above." +"Please note that some of above are fallbacks in case Zammad could not detect " +"the agents timezone correctly." msgstr "" -#: ../settings/ticket.rst:122 -msgid "Checksum (default: ``no``)" +#: ../settings/branding.rst:77 +msgid "Pretty Date" msgstr "" -#: ../settings/ticket.rst:118 +#: ../settings/branding.rst:47 msgid "" -"If set to yes, we'll built a checksum to further \"unique\" the ticket " -"number of your system. If you're dealing with many other ticket systems this " -"might help to prevent false positive follow up detection on tickets." +"This setting allows you to define how Zammad should display time stamps " +"within the interface to all users." msgstr "" -#: ../settings/ticket.rst:122 -msgid "This will also add another digit to the ticket number." +#: ../settings/branding.rst:50 +msgid "" +"This does not have any effect on how Zammad returns e.g. time values via " +"variables." msgstr "" -#: ../settings/ticket.rst:137 -msgid "Min. size of Number (default: ``5``)" +#: ../settings/branding.rst:77 +msgid "Choose in between the following options:" msgstr "" -#: ../settings/ticket.rst:125 -msgid "" -"This setting defines the minimum length of your ticket number. If your " -"counter is not yet high enough, Zammad will fill the number with zeros to " -"ensure the wanted length." +#: ../settings/branding.rst:64 +msgid "relative" msgstr "" -#: ../settings/ticket.rst:129 +#: ../settings/branding.rst:55 msgid "" -"Please note that the minimum length is ``3`` (SystemID + at least one digit " -"if below 10). Also, if the length is no longer long enough, the number will " -"automatically get one digit longer. Ticket-Numbers **do not overflow**, thus " -"it's save to keep it at 5 or set it lower if wanted." +"This timestamp shows a relative time span until it switches to a date. Over " +"time, it will change as follows:" msgstr "" -#: ../settings/ticket.rst:135 -msgid "" -"This option is only available if ticket number format is set to " -"``Increment``!" +#: ../settings/branding.rst:58 +msgid "just now" msgstr "" -#: ../settings/ticket.rst:142 -msgid "Auto-Assignment" +#: ../settings/branding.rst:59 +msgid "5 minutes ago" msgstr "" -#: ../settings/ticket.rst:144 -msgid "" -"In a larger Zammad environment, it happens that several agents open the same " -"ticket at the same time. Although collision detection is then effective, the " -"efficiency of processing can be increased by means of the automatic " -"assignment of tickets when a ticket is opened." +#: ../settings/branding.rst:60 +msgid "3 days 1 hour ago" msgstr "" -#: ../settings/ticket.rst:149 -msgid "" -"The automatic assignment of tickets can be activated and configured in the " -"admin area under Settings > Ticket > Auto Assignment." +#: ../settings/branding.rst:61 +msgid "``03/04/2022``" msgstr "" -#: ../settings/ticket.rst:152 -msgid "" -"The auto assignment only works if the ticket has no owner yet. By default, " -"the agent can always reset the ticket owner to ``-`` if needed." +#: ../settings/branding.rst:63 +msgid "Hovering the timestamp helps, you'll always get a clean timestamp then." msgstr "" -#: ../settings/ticket.rst:155 -msgid "" -"If you want to use this function for only specific tickets, you can " -"configure the conditions accordingly to meet your requirement. By default " -"the condition affects all tickets with the state ``open``." +#: ../settings/branding.rst:71 +msgid "absolute" msgstr "" -#: ../settings/ticket.rst:161 +#: ../settings/branding.rst:67 msgid "" -"If you need to exclude users (e.g. a group leader), you can search and " -"select the desired agents in the ``Exception Users`` list. The search " -"function in this area is only effective, if you have too many agents to " -"display at once to help you with the configuration." +"This timestamp always includes the week day. For one week after creation, " +"the timestamp will not contain the date itself: Thursday 18:35." msgstr "" -#: ../settings/ticket.rst:167 -msgid "Notifications" +#: ../settings/branding.rst:71 +msgid "After a week it will switch to: ``Friday 4. Mar 16:00``." msgstr "" -#: ../settings/ticket.rst:191 -msgid "Default Notifications" +#: ../settings/branding.rst:76 +msgid "timestamp" msgstr "" -#: ../settings/ticket.rst:170 +#: ../settings/branding.rst:74 msgid "" -"This setting allows you to configure the default ticket notifications that " -"will be applied to all new agent users (incl. users who were just assigned " -"agent role). Simply change the notification matrix to desired state and " -"press **Save**." +"This will cause Zammad to show a complete timestamp according to your locale " +"defaults. For English this could be e.g. ``2022/12/03 2:40 pm`` or for " +"German e.g. ``12.03.2022 14:40``." msgstr "" -#: ../settings/ticket.rst:175 -msgid "" -"In case an agent already exists, their ticket notification preferences will " -"be preserved. Optionally, you can also **Apply current defaults to all " -"agents**." +#: ../settings/branding.rst:78 +msgid "Default setting: ``relative``." msgstr "" -#: ../settings/ticket.rst:181 -msgid "" -"**Potential time-consuming action:** Applying default ticket notifications " -"to all agent users may take some time to complete, be patient! The exact " -"time will depend on the size of your system and the number of agents." +#: ../settings/security.rst:2 +msgid "Security" msgstr "" -#: ../settings/ticket.rst:185 +#: ../settings/security.rst:4 msgid "" -"**Active agents only!** When current default ticket notifications are " -"applied, only active agent users are considered. In case an agent is re-" -"activated *after* this action, they will still have the old notification " -"configuration." +"For your overview we split each tab within security settings into its own " +"page:" msgstr "" -#: ../settings/ticket.rst:190 +#: ../settings/security/base.rst:2 ../settings/system/base.rst:2 +#: ../settings/ticket.rst:8 +msgid "Base" +msgstr "" + +#: ../settings/security/base.rst:5 +msgid "New User Accounts" +msgstr "" + +#: ../settings/security/base.rst:9 msgid "" -"In case you want to go back to the initial state of ticket notifications, " -"you can click on **Reset to default** button." +"Activates the `register as a new customer` function on the login page. If " +"set to ``no`` only administrators or agents can create new accounts manually." msgstr "" -#: ../settings/ticket.rst:194 ../settings/ticket.rst:196 -msgid "Duplicate Detection" +#: ../settings/security/base.rst:13 ../settings/security/base.rst:38 +#: ../settings/security/base.rst:66 +msgid "Default setting: ``yes``" msgstr "" -#: ../settings/ticket.rst:236 ../settings/ticket.rst:238 -msgid "Detect Duplicate Ticket Creation" +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"New User Accounts\" setting" msgstr "" -#: ../settings/ticket.rst:197 ../settings/ticket.rst:199 +#: ../settings/security/base.rst:22 msgid "" -"This setting turns on the duplicate ticket detection mechanism during ticket " -"creation. If similar tickets are found in the system, a suitable warning " -"will be shown to the user trying to create a ticket." +"Deactivation of above function **does not** deactivate automatic account " +"creation! This means: If a user writes e.g. an email to Zammad and has no " +"account yet, Zammad will automatically create the account. User accounts are " +"a direct dependency of tickets and thus technically mandatory." msgstr "" -#: ../settings/ticket.rst:204 ../settings/ticket.rst:206 -msgid "A Sample Duplicate Ticket Warning" +#: ../settings/security/base.rst:29 +msgid "Lost Password" msgstr "" -#: ../settings/ticket.rst:206 ../settings/ticket.rst:208 +#: ../settings/security/base.rst:33 msgid "" -"You can choose which ticket attributes will be matched by selecting them in " -"**Attributes to compare** field. Only if the ticket attribute value provided " -"by the user in the ticket create form is *equal* with the attribute in an " -"existing ticket, the warning will be shown." +"Activates the `lost password` function on the login page. If set to ``no`` " +"only administrators may change the user's password - users may update their " +"own password if they're still logged in and they have the required :doc:" +"`permission `." msgstr "" -#: ../settings/ticket.rst:211 ../settings/ticket.rst:213 -msgid "**Warning title** and **Warning message** are configurable as well." +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"Lost Password\" setting" msgstr "" -#: ../settings/ticket.rst:213 ../settings/ticket.rst:215 +#: ../settings/security/base.rst:49 msgid "" -"You can limit the detection only to certain user roles. By default, only " -"agents will see the warning." +"With third party authentications - but especially LDAP - you may want to " +"disable this function. Zammad **will not** change third party login " +"passwords and instead set or change the local password!" msgstr "" -#: ../settings/ticket.rst:216 ../settings/ticket.rst:218 -msgid "" -"If you don't want to show the matched tickets as part of the warning, you " -"can set **Show matching ticket(s) in the warning** setting to *no*." +#: ../settings/security/base.rst:56 +msgid "Password Login" msgstr "" -#: ../settings/ticket.rst:219 ../settings/ticket.rst:221 +#: ../settings/security/base.rst:60 msgid "" -"By default, **Permission level for looking up ticket** is set to *User*, " -"which means user permissions will be honored during sarch. The user will " -"see the warning only if tickets they have access to are matched. " -"Alternatively, you can set this setting to *System*, in which case the " -"search will happen within *all* tickets in the system, regardless of user " -"permissions." +"Activates the username & password login by default and if no third-party " +"login is activated. Disabling password login on the Zammad login page only " +"takes effect if you enable any :doc:`third-party`." msgstr "" -#: ../settings/ticket.rst:225 ../settings/ticket.rst:227 -msgid "**🦺 Safety first!**" +#: ../settings/security/base.rst:64 +msgid "See :doc:`third-party` for supported third-party logins." msgstr "" -#: ../settings/ticket.rst:227 ../settings/ticket.rst:229 -msgid "" -"Even if the permission level is set to *System*, the user will not be shown " -"the tickets they don't have access to in the warning, even if they match." +#: ../settings/security/base.rst:0 +msgid "Figure showing de-activated \"Password Login\" setting" msgstr "" -#: ../settings/ticket.rst:231 ../settings/ticket.rst:233 +#: ../settings/security/base.rst:77 msgid "" -"However, just the confirmation about the existence of the tickets in the " -"system may be considered an unwanted information disclosure. Use this option " -"carefully!" +"To help administrators to overcome \"login issues\", Zammad automatically " +"offers a password request for administrator users. This allows you to adjust " +"Third-Party applications even if the login does no longer work!" msgstr "" -#: ../settings/ticket.rst:235 ../settings/ticket.rst:237 -msgid "" -"Finally, you can configure between matching within **All tickets** or **Open " -"tickets** only by setting **Match tickets in following states**. Depending " -"on the current ticket state, a ticket may or not be matched." +#: ../settings/security/base.rst:84 +msgid "Session Timeout" msgstr "" -#: ../system/core-workflows.rst:2 -msgid "Core Workflows" +#: ../settings/security/base.rst:86 +msgid "" +"All settings below by default are set to ``4 weeks``. Session Timeout " +"defines the life time of a users session. As soon as it's reached, Zammad " +"will automatically log off the session in question." msgstr "" -#: ../system/core-workflows.rst:4 +#: ../settings/security/base.rst:91 msgid "" -"Core Workflows allow you to adjust object attributes in many ways. For " -"example:" +"Zammad takes the highest value set assigned for the user based on the " +"permissions." msgstr "" -#: ../system/core-workflows.rst:7 -msgid "show / hide fields" +#: ../settings/security/base.rst:94 +msgid "``admin``" msgstr "" -#: ../system/core-workflows.rst:8 -msgid "adjust mandatory setting" +#: ../settings/security/base.rst:96 +msgid "``ticket.customer``" msgstr "" -#: ../system/core-workflows.rst:9 -msgid "manipulate available options" +#: ../settings/security/base.rst:97 +msgid "``default`` (fallback if user doesn't have above permissions set)" msgstr "" -#: ../system/core-workflows.rst:11 +#: ../settings/security/base.rst:99 msgid "" -"With this, you can provide exactly the information your users really need!" +"All settings act independently from each other allowing you to disable the " +"timeouts for e.g. admins, but not agents." msgstr "" -#: ../system/core-workflows.rst:15 -msgid "" -"If the pre-defined :doc:`/system/objects` are not enough, please add them " -"beforehand." +#: ../settings/security/base.rst:115 +#: ../system/integrations/checkmk/api-reference.rst:13 +msgid "Example" msgstr "" -#: ../system/core-workflows.rst:17 -msgid "" -"If you experience slow or unreliable field updates, please see :ref:`Core " -"Workflow Ajax Modus `" +#: ../settings/security/base.rst:107 +msgid "Let's suppose you configured the following session timeouts" msgstr "" -#: ../system/core-workflows.rst:22 -msgid "" -"This is a very enhanced functionality and can cause unexpected UI behavior. " -"Please ensure to test your use cases after configuration to reduce surprises." +#: ../settings/security/base.rst:104 +msgid "default: 3 weeks" msgstr "" -#: ../system/core-workflows.rst:None -msgid "Dialogue for adding a new workflow" +#: ../settings/security/base.rst:105 +msgid "admin: 2 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:2 -msgid "Core Workflow Condition Operators" +#: ../settings/security/base.rst:106 +msgid "ticket.agent: 4 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:4 -msgid "" -"You might know that there is a separate section for explaining :doc:" -"`condition operators `. Head over there to " -"see a detailed explanation of many conditions and operators." +#: ../settings/security/base.rst:107 +msgid "ticket.customer: 1 week" msgstr "" -#: ../system/core-workflows/condition-operators.rst:8 -msgid "" -"Due to differences to other places in Zammad which are also using conditions " -"(e.g. triggers), you can find a dedicated description of operators for core " -"workflows below." +#: ../settings/security/base.rst:115 +msgid "This results in the following situations" msgstr "" -#: ../system/core-workflows/condition-operators.rst:12 -msgid "" -"Be aware that the availability of the operators depends on the selected " -"attribute and its field type. Some of the operators may only be available " -"for system attributes (e.g. for \"tags\", \"active\")." +#: ../settings/security/base.rst:110 +msgid "a user with ``admin`` permission will have a timeout of 2 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:20 -msgid "Operator" +#: ../settings/security/base.rst:111 +msgid "" +"a user with ``admin`` and ``ticket.agent`` permissions will have a timeout " +"of 2 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:22 -msgid "after (absolute)" +#: ../settings/security/base.rst:113 +msgid "" +"a user with ``ticket.customer`` permission will have a timeout of 1 week" msgstr "" -#: ../system/core-workflows/condition-operators.rst:23 -msgid "Matches if a date/time is after a specific point in time." +#: ../settings/security/base.rst:115 +msgid "" +"a user with neither ``admin``, ``ticket.agent`` nor ``ticket.customer`` " +"permissions will have a timeout of 3 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:24 -msgid "after (relative)" +#: ../settings/security/password.rst:4 +msgid "" +"This section allows you to define password requirements for the local user " +"accounts." msgstr "" -#: ../system/core-workflows/condition-operators.rst:25 -msgid "Matches if a time span after a specified event has passed." +#: ../settings/security/password.rst:9 +msgid "" +"Zammad does **not** allow you to change your LDAP password, instead, it will " +"set a password in its local database which might confuse your users. This " +"might be addressed in the future by `#1169 `_." msgstr "" -#: ../system/core-workflows/condition-operators.rst:26 -msgid "before (absolute)" +#: ../settings/security/password.rst:14 +msgid "**Exception for admins**" msgstr "" -#: ../system/core-workflows/condition-operators.rst:27 -msgid "Matches if a date/time is before a specific point in time." +#: ../settings/security/password.rst:16 +msgid "" +"Please note that below password policies *do not* affect administrators " +"setting passwords on user accounts. While this seems strange and not safe we " +"believe that an administrator knowing an user's password is insecure as well." msgstr "" -#: ../system/core-workflows/condition-operators.rst:28 -msgid "before (relative)" +#: ../settings/security/password.rst:21 +msgid "The suggested workflow is either:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:29 -msgid "Matches if a time span after a specified event has not passed." +#: ../settings/security/password.rst:23 +msgid "" +"to use third party logins to not require local passwords at all **- or -**" msgstr "" -#: ../system/core-workflows/condition-operators.rst:30 -msgid "contains" +#: ../settings/security/password.rst:25 +msgid "to require your *user to reset the password* upon first login." msgstr "" -#: ../system/core-workflows/condition-operators.rst:31 -msgid "Matches if a specified value is present." +#: ../settings/security/password.rst:27 +msgid "" +"This way administrators are not required to set a user's password at all!" msgstr "" -#: ../system/core-workflows/condition-operators.rst:33 -msgid "Matches if all of the specified values are present." +#: ../settings/security/password.rst:31 +msgid "Maximum Failed Logins" msgstr "" -#: ../system/core-workflows/condition-operators.rst:35 -msgid "Matches if none of the specified values are present." +#: ../settings/security/password.rst:33 +msgid "" +"You can choose a value between ``4`` and ``20``. This defines how often a " +"login to a user account may fail until Zammad will lock it. Your users can " +"always use the \"forgot password\" function to change their password and " +"unlock their account." msgstr "" -#: ../system/core-workflows/condition-operators.rst:36 -msgid "contains not" +#: ../settings/security/password.rst:38 +msgid "The default value is ``10``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:37 -msgid "Matches if a specified value is not present." +#: ../settings/security/password.rst:42 +msgid "Beside changing the user's password, you can also unlock accounts via" msgstr "" -#: ../system/core-workflows/condition-operators.rst:39 -msgid "Matches if one specified value is present." +#: ../settings/security/password.rst:44 +msgid ":ref:`user management list `" msgstr "" -#: ../system/core-workflows/condition-operators.rst:41 -msgid "Matches if one specified value is not present." +#: ../settings/security/password.rst:45 +msgid ":docs:`console `" msgstr "" -#: ../system/core-workflows/condition-operators.rst:42 -msgid "does not match regex" +#: ../settings/security/password.rst:46 +msgid ":docs:`API `" msgstr "" -#: ../system/core-workflows/condition-operators.rst:43 -msgid "Matches if content doesn't fit to regex rule." +#: ../settings/security/password.rst:50 +msgid "Failed logins via LDAP no longer lock accounts." msgstr "" -#: ../system/core-workflows/condition-operators.rst:44 -msgid "ends with" +#: ../settings/security/password.rst:53 +msgid "2 Lower Case And 2 Upper Case Characters" msgstr "" -#: ../system/core-workflows/condition-operators.rst:45 -msgid "Matches if content ends with specified value." +#: ../settings/security/password.rst:55 +msgid "" +"You can add complexity to passwords by enforcing at least 2 upper and lower " +"case characters." msgstr "" -#: ../system/core-workflows/condition-operators.rst:46 -msgid "ends with one of" +#: ../settings/security/password.rst:58 ../settings/security/password.rst:83 +msgid "The default value is ``no``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:47 -msgid "Matches if content ends with one of the specified values." +#: ../settings/security/password.rst:62 +msgid "Minimum Length" msgstr "" -#: ../system/core-workflows/condition-operators.rst:48 -msgid "from (relative)" +#: ../settings/security/password.rst:64 +msgid "" +"This defines the minimum password length required for users to provide (from " +"``4`` to ``20``)." msgstr "" -#: ../system/core-workflows/condition-operators.rst:49 -msgid "Matches if date/time is after a period of time after an event." +#: ../settings/security/password.rst:67 +msgid "The default value is ``6``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:51 -msgid "Matches if content is equal to a specified value." +#: ../settings/security/password.rst:71 +msgid "Digit Required" msgstr "" -#: ../system/core-workflows/condition-operators.rst:52 -msgid "is any of" +#: ../settings/security/password.rst:73 +msgid "This enforces your users to use at least one digit within the password." msgstr "" -#: ../system/core-workflows/condition-operators.rst:53 -msgid "Matches if content is equal to any of specified values." +#: ../settings/security/password.rst:75 +msgid "The default value is ``yes``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:54 -msgid "is modified" +#: ../settings/security/password.rst:78 +msgid "Special Character Required" msgstr "" -#: ../system/core-workflows/condition-operators.rst:55 -msgid "Matches if content is modified." +#: ../settings/security/password.rst:80 +msgid "" +"This setting allows you to improve your password quality even more by " +"enforcing the password to contain at least one special character." msgstr "" -#: ../system/core-workflows/condition-operators.rst:57 -#: ../system/core-workflows/condition-operators.rst:61 -msgid "True from the moment of changing content until form submit." +#: ../settings/security/ssl-certificates.rst:2 +msgid "SSL Certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:58 -msgid "is modified to" +#: ../settings/security/ssl-certificates.rst:7 +msgid "" +"Zammad offers the possibility to upload custom certificates and custom " +"Certificate Authority (CA) certificates. This can be useful if you want to " +"connect Zammad the secure way to other systems which are using custom " +"certificates." msgstr "" -#: ../system/core-workflows/condition-operators.rst:59 -msgid "Matches if content is modified to a specific value." +#: ../settings/security/ssl-certificates.rst:12 +msgid "" +"An example usecase might be: You have an internal LDAP server that is not " +"accessible from the internet, and you want a SSL-encrypted connection, using " +"a custom certificate." msgstr "" -#: ../system/core-workflows/condition-operators.rst:62 -msgid "is none of" +#: ../settings/security/ssl-certificates.rst:19 +msgid "" +"You should have an existing custom certificate file and/or a custom CA " +"certificate file, which you want to add to Zammad. As filetype ``.crt`` is " +"supported and the certificate format has to be PEM (Base64 ASCII)." msgstr "" -#: ../system/core-workflows/condition-operators.rst:63 -msgid "Matches if content is none of any specified values." +#: ../settings/security/ssl-certificates.rst:25 +msgid "" +"When you import a custom CA certificate, all certificates generated with " +"this are trusted. This can be useful if you have more than one system/" +"certificate you want to connect to and the certificates are issued from the " +"same custom CA." msgstr "" -#: ../system/core-workflows/condition-operators.rst:65 -msgid "Matches if content is not equal to a specified value." +#: ../settings/security/ssl-certificates.rst:31 +msgid "Add a Certificate" msgstr "" -#: ../system/core-workflows/condition-operators.rst:67 -msgid "Matches if content is present." +#: ../settings/security/ssl-certificates.rst:33 +msgid "" +"To add a custom certificate or a custom CA certificate, head over to the " +"Admin panel > Settings > Security > SSL Certificates. Here you can find a " +"\"Add SSL Certificate\" button. In the dialog you can either select a " +"certificate file or paste the content of the certificate:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:68 -msgid "just changed" +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate adding dialog" msgstr "" -#: ../system/core-workflows/condition-operators.rst:69 -msgid "Matches if content has changed." +#: ../settings/security/ssl-certificates.rst:43 +msgid "" +"After selecting a file or pasting the content of the certificate, click on " +"the \"Add\" button to finally upload it to Zammad. Then, the certificates " +"are immediately effective, no restart or similar required." msgstr "" -#: ../system/core-workflows/condition-operators.rst:71 -#: ../system/core-workflows/condition-operators.rst:75 +#: ../settings/security/ssl-certificates.rst:49 msgid "" -"Only true for the moment of changing content until next form field action/" -"click." +"Please note that only single certificate files are supported. That means if " +"you want to import a certificate / CA certificate, it must contain **only " +"one** certificate." msgstr "" -#: ../system/core-workflows/condition-operators.rst:72 -msgid "just changed to" +#: ../settings/security/ssl-certificates.rst:54 +msgid "Certificate Overview" msgstr "" -#: ../system/core-workflows/condition-operators.rst:73 -msgid "Matches if content has changed to a specified value." +#: ../settings/security/ssl-certificates.rst:56 +msgid "" +"After you added a certificate, you can see a table with information for each " +"added certificate:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:76 -msgid "matches regex" +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing table of added certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:77 -msgid "Matches if value fits to regex rule." -msgstr "" - -#: ../system/core-workflows/condition-operators.rst:79 -msgid "Matches if no content is present." -msgstr "" - -#: ../system/core-workflows/condition-operators.rst:80 -msgid "starts with" +#: ../settings/security/ssl-certificates.rst:64 +msgid "" +"Here you can download the certificate or delete it, if you don't need it " +"anymore." msgstr "" -#: ../system/core-workflows/condition-operators.rst:81 -msgid "Matches if content starts with specified value." +#: ../settings/security/ssl-certificates.rst:68 +msgid "Deleting Certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:82 -msgid "starts with one of" +#: ../settings/security/ssl-certificates.rst:70 +msgid "" +"If you want to delete a specific certificate, you can do it by clicking on " +"the menu in the actions column and selecting delete:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:83 -msgid "Matches if content starts with one of the specified values." +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate deletion button" msgstr "" -#: ../system/core-workflows/condition-operators.rst:84 -msgid "till (relative)" +#: ../settings/security/ssl-certificates.rst:79 +msgid "Downloading Certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:85 -msgid "Matches if date/time is before a period of time before an event." +#: ../settings/security/ssl-certificates.rst:81 +msgid "" +"If you want to download your certificates, you can do this as well via " +"corresponding action buttons." msgstr "" -#: ../system/core-workflows/condition-operators.rst:86 -msgid "today" +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate download button" msgstr "" -#: ../system/core-workflows/condition-operators.rst:87 -msgid "Matches if date/time is today." +#: ../settings/security/third-party.rst:13 +msgid "Login Providers" msgstr "" -#: ../system/core-workflows/condition-operators.rst:88 -msgid "within last (relative)" +#: ../settings/security/third-party.rst:2 +msgid "Third-Party Applications" msgstr "" -#: ../system/core-workflows/condition-operators.rst:89 +#: ../settings/security/third-party.rst:4 msgid "" -"Matches if date/time content is within specified period of time before now." +"Third party authentication is a great way to help your users to login to " +"Zammad more easily. If the account is yet unknown, Zammad will create a new " +"user automatically, without the user needed to interact (e.g. type in his " +"name). Another big advantage of this feature is that your user doesn't need " +"to remember another password." msgstr "" -#: ../system/core-workflows/condition-operators.rst:91 -msgid "within next (relative)" +#: ../settings/security/third-party.rst:10 +msgid "" +"You can deactivate logging in via :ref:`security_password_login` if any of " +"the mentioned authentication providers are enabled in your instance." msgstr "" -#: ../system/core-workflows/condition-operators.rst:92 +#: ../settings/security/third-party.rst:27 msgid "" -"Matches if date/time content is within specified period of time after now." +"We're currently missing documentation for the following login providers:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:2 -msgid "How do they work?" +#: ../settings/security/third-party.rst:29 +msgid "LinkedIn" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:4 -msgid "" -"Core Workflows are executed according to their priority. If two workflows " -"have the same priority, they are executed in alphabetical order based on " -"their **name**." +#: ../settings/security/third-party.rst:30 +msgid "Weibo" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:8 -msgid "" -"Because of the way Core Workflows work, all changes to attributes are " -"checked with the application server - please see :doc:`limitations` for " -"possible issues." +#: ../settings/security/third-party.rst:35 +msgid "Automatic Account Link on Initial Logon" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:12 +#: ../settings/security/third-party.rst:37 msgid "" -"Below we're talking about settings that are important and not self-" -"explanatory." +"In general there's two possible options for Zammad on how to deal with " +"already known users as they try to authenticate against a third-party " +"application. By default, Zammad will not automatically link \"unknown\" " +"authentication providers to existing accounts." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:17 +#: ../settings/security/third-party.rst:42 msgid "" -"Choose the object context you want to run the workflow in. This will decide " -"on your available attributes and actions." -msgstr "" - -#: ../system/core-workflows/how-do-they-work.rst:20 -msgid "Ticket objects also have access to the ticket customer." +"This means that the user has to manually link authentication providers to " +"their accounts (for more about this :user-docs:`consult the user " +"documentation `)." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:25 +#: ../settings/security/third-party.rst:46 msgid "" -"Choose in which situation the workflow is applied. Contexts can be combined " -"to avoid duplicate workflows." +"Sometimes this doesn't come in handy as this also means you'll receive error " +"messages about \"email address being in use already\" for (yet) unknown " +"third-party authentication methods." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:30 -msgid "Creation mask" +#: ../settings/security/third-party.rst:50 +msgid "" +"If you want to allow your users to always be able to log in, no matter what, " +"you may want to enable ``Automatic account link on initial logon``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:29 +#: ../settings/security/third-party.rst:None msgid "" -"If selected, your conditions and actions will affect all applicable creation " -"masks." +"Screenshot highlighting the \"Automatic account link on initial logon\"\n" +"setting" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:34 -msgid "Edit mask" +#: ../settings/security/third-party.rst:60 +msgid "Automatic Account Linking Notification" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:33 +#: ../settings/security/third-party.rst:64 msgid "" -"If selected, your conditions and actions will affect all applicable edit " -"masks." +"To improve security and your users awareness, you can enable Zammad to " +"notify your users when a new third-party application has been linked to " +"their account." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:39 +#: ../settings/security/third-party.rst:68 msgid "" -"Zammad differentiates between selected and saved conditions. These can be " -"combined wherever needed." +"This notification is sent out once per third-party application. Zammad does " +"also mention the method used, e.g.: ``Microsoft``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:42 -msgid "**⚠️ Restrict workflows to specific roles if needed!**" +#: ../settings/security/third-party.rst:71 +msgid "By default this setting is not active (set to ``no``)." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:44 +#: ../settings/security/third-party.rst:0 msgid "" -"By default and unless configured in conditions, workflow rules are executed " -"for **all roles**. This also affects your customers!" +"Screenshot showing sample notification mail after initial\n" +"third-party linking" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:50 -msgid "Selected Conditions" +#: ../settings/security/third-party.rst:85 +msgid "" +"This notification is only sent if the account in question already exists. If " +"the login via the third-party also creates the missing account, the " +"notification will be skipped." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:48 -msgid "" -"These conditions are based on form values and match if an appropriate " -"selection is made (e.g. choosing another group in the ticket without " -"saving). This applies for drafts (active selection) and currently saved " -"values." +#: ../settings/security/third-party.rst:89 +msgid "This means it only affects:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:64 -msgid "Saved Conditions" +#: ../settings/security/third-party.rst:91 +msgid "manual account linking within the third-party page of the users profile" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:53 +#: ../settings/security/third-party.rst:92 msgid "" -"These conditions only match if the selected values are stored in the " -"database. It ignores the current value or selection of the field, as long as " -"the changes are not saved (e.g. performing field operations for an existing " -"ticket, which is viewed/opened by an agent)." +"logging into an existing local account by utilizing the *automatic account " +"link on initial logon* functionality" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:60 +#: ../settings/security/third-party.rst:None msgid "" -"Keep in mind that the value has to be available in the situation where you " -"need it. Otherwise the condition won't match." +"Screenshot showing the \"automatic account linking notification\"\n" +"setting" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:63 -msgid "" -"Example: you can't perform any actions with *saved condition* on a ticket in " -"creation, because there are no saved values at that time." +#: ../settings/security/third-party.rst:100 +msgid "No User Creation on Logon" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:66 +#: ../settings/security/third-party.rst:102 msgid "" -"You can find a description of the condition operators for core workflows :" -"doc:`here `." +"By default, Zammad will create a new user account if the user logs in via a " +"third-party application and the account doesn't exist yet." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:72 +#: ../settings/security/third-party.rst:105 msgid "" -"Which actions should we run on the relevant fields? The possible actions " -"depend on the object type. However, usually you can at least change the " -"visibility and whether the field is mandatory." +"If you want to prevent Zammad from creating new accounts on logon, you can " +"disable this feature by setting ``No user creation on logon`` to ``yes``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:76 -msgid "Be aware that actions are not available for **related** context." +#: ../settings/security/third-party.rst:None +msgid "Screenshot showing the \"no user creation on logon\" setting" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:78 +#: ../settings/security/third-party/facebook.rst:4 msgid "" -"**Example:** Let's assume you are working in the ticket context. While you " -"can have customer *conditions*, you *can't adjust* objects with actions in " -"that scope. That's because this wouldn't have any impact on the ticket " -"dialog. Of course all ticket attributes (state, owner, ...) are available." +"It is possible to create a quick login for your helpdesk via Facebook To do " +"so, you need to follow these steps:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:84 +#: ../settings/security/third-party/facebook.rst:9 +msgid "Register Facebook App" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:11 msgid "" -"Please also have a look at our :doc:`limitations` to be safe from surprises." +"Visit [https://developers.facebook.com/apps/] and click on \"Add a new App\"" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:88 -msgid "Available Operators" +#: ../settings/security/third-party/facebook.rst:None +msgid "initial page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:90 -msgid "The availability of operators depends on the object type and scope." +#: ../settings/security/third-party/facebook.rst:17 +msgid "After that enter the app settings" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:94 -msgid "" -"Please note that actions may or may not restrict API based access to " -"attributes. We're displaying the following icons for your overview to " -"understand these limits better:" +#: ../settings/security/third-party/facebook.rst:None +msgid "Create App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:0 -msgid "|api| This icon indicates the action affects the API." +#: ../settings/security/third-party/facebook.rst:22 +msgid "Navigate to \"Settings\" and fill in this infromation" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:163 -msgid "api" +#: ../settings/security/third-party/facebook.rst:None +msgid "App Settings" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:0 -msgid "|ui| This icon indicates the action only affects the web interface." +#: ../settings/security/third-party/facebook.rst:27 +msgid "Navigate to app review and Check \"Make [appname] public?\"" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:167 -msgid "ui" +#: ../settings/security/third-party/facebook.rst:None +msgid "App Review" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:102 -msgid "show |ui|" +#: ../settings/security/third-party/facebook.rst:35 +msgid "Configure Zammad as Facebook App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:102 -msgid "Display the chosen field. Allows setting of values." -msgstr "" - -#: ../system/core-workflows/how-do-they-work.rst:109 -msgid "hide |ui|" +#: ../settings/security/third-party/facebook.rst:37 +msgid "" +"Navigate to \"Admin -> Security -> Third Party Applications\" and enter the " +"App ID and the App Secret. You can find this Key in the Dashbard of your " +"Facebok app." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:105 -msgid "" -"Hide the chosen field. However, it technically still allows setting the " -"field." +#: ../settings/security/third-party/facebook.rst:None +msgid "Zammad Configuration" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:108 +#: ../settings/security/third-party/facebook.rst:44 +#: ../settings/security/third-party/github.rst:43 +#: ../settings/security/third-party/gitlab.rst:46 msgid "" -"Please note that the field is **not** gone and still contains an existing " -"value (if set)! Consider *remove* instead, if you want this field to be gone." +"Now you can link accounts via \"Avatar -> Profile -> Link Accounts\" or " +"login via Zammad login page." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:112 -msgid "remove |ui|" +#: ../settings/security/third-party/github.rst:2 +#: ../system/integrations/github.rst:2 +msgid "GitHub" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:112 -msgid "Entirely removes the field. The field value will not be evaluated." +#: ../settings/security/third-party/github.rst:4 +msgid "" +"It is possible to create a quick login for your helpdesk via GitHub. To " +"activate the quick login you need to enable OAuth for GitHub." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:115 -msgid "set mandatory |ui| |api|" +#: ../settings/security/third-party/github.rst:8 +msgid "Register GitHub App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:115 -msgid "Sets the field to mandatory." +#: ../settings/security/third-party/github.rst:10 +msgid "" +"Visit https://www.github.com/settings/applications/new and enter the app " +"settings. As callback URL enter \"https://zammad_host/auth/github/callback\" " +"where zammad_host has to be replaced with your Zammad FQDN" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:118 -msgid "set optional |ui| |api|" +#: ../settings/security/third-party/github.rst:None +msgid "Register OAuth app on www.github.com" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:118 -msgid "Sets the field to optional." +#: ../settings/security/third-party/github.rst:19 +msgid "Configure Zammad as GitHub App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:124 -msgid "add option |ui| |api|" +#: ../settings/security/third-party/github.rst:21 +msgid "" +"Enter the \"APP ID\" and the \"APP SECRET\" from the GitHub OAUTH " +"Applications Dashboard" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:121 -msgid "Allows adding options to tree selects or selects." +#: ../settings/security/third-party/github.rst:None +msgid "GitHub config in Zammad admin interface" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:123 +#: ../settings/security/third-party/github.rst:28 msgid "" -"You have to use the \"remove option\" before performing this action. It " -"allows you to use *existing* configured values." +"After you configured the GitHub credentials and activated the login method, " +"you should see a new icon on the login page." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:128 -msgid "remove option |ui| |api|" +#: ../settings/security/third-party/github.rst:None +msgid "GitHub logo on login page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:127 +#: ../settings/security/third-party/github.rst:34 msgid "" -"Allows removing options from tree selects or selects. It allows you to use " -"*existing* configured values." +"If you click on the icon you will be redirected to GitHub and see something " +"similar to this:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:134 -msgid "set fixed to |ui| |api|" +#: ../settings/security/third-party/github.rst:None +msgid "GitHub oauth page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:131 -msgid "Reduces the available options by your selection." +#: ../settings/security/third-party/github.rst:40 +#: ../settings/security/third-party/gitlab.rst:42 +msgid "" +"When you grant the access you will be redirected to your Zammad instance and " +"logged in as a customer." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:133 -msgid "" -"This reduces your workflows in terms of *add option* and *remove option*." +#: ../settings/security/third-party/gitlab.rst:2 +msgid "Gitlab" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:137 -msgid "fill in |ui|" +#: ../settings/security/third-party/gitlab.rst:4 +msgid "" +"It is possible to create a quick login for your helpdesk via Gitlab. To " +"activate the quick login you need to enable OAuth for Gitlab." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:137 -msgid "Allows filling in of string and integer fields with your values." +#: ../settings/security/third-party/gitlab.rst:8 +msgid "Register Gitlab App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:141 -msgid "fill in empty |ui|" +#: ../settings/security/third-party/gitlab.rst:10 +msgid "To register an app in Gitlab open your profile and select applications." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:140 +#: ../settings/security/third-party/gitlab.rst:12 msgid "" -"Allows filling in of string and integer fields with your values **if the " -"field is empty**." +"As callback URL enter \"https://zammad-fqdn/auth/gitlab/callback\" where " +"zammad-fqdn has to be replaced with your Zammad FQDN" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:144 -msgid "select |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Register OAuth app on gitlab instance" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:144 -msgid "Select a specific value within a select, tree select or boolean field." +#: ../settings/security/third-party/gitlab.rst:18 +msgid "Just select *read_user* under scopes as in the screenshot and save it." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:153 -msgid "auto select |ui|" +#: ../settings/security/third-party/gitlab.rst:21 +msgid "Configure Zammad as Gitlab App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:147 -msgid "Helps users with tree select and select fields:" +#: ../settings/security/third-party/gitlab.rst:23 +msgid "" +"Enter the \"APP ID\" and the \"APP SECRET\" from the Gitlab OAUTH " +"Applications Dashboard and your Gitlab-URL in the \"SITE\" field." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:149 -msgid "" -"If the field has only one option available for selection and no value yet, " -"the value will be automatically set." +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab config in Zammad admin interface" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:152 +#: ../settings/security/third-party/gitlab.rst:30 msgid "" -"This option only works if you have one value and doesn't work if there is " -"more than one option available." +"After you configured the Gitlab credentials and activated the login method, " +"you should see a new icon on the login page." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:157 -msgid "set readonly |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab logo on login page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:156 +#: ../settings/security/third-party/gitlab.rst:36 msgid "" -"Allows you to display an attribute as read only (which means no changes are " -"possible)." +"If you click on the icon you will be redirected to Gitlab and see something " +"similar to this:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:161 -msgid "unset readonly |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab oauth page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:160 +#: ../settings/security/third-party/google.rst:4 msgid "" -"In case a workflow set the field in question to read only, you can undo this " -"with option above." +"With some easy and fast steps, you can enable Zammad to authenticate your " +"users via Google." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:172 -msgid "Stop after match" +#: ../settings/security/third-party/google.rst:8 +msgid "Register a Google App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:174 +#: ../settings/security/third-party/google.rst:10 msgid "" -"Here you can decide if other workflows are executed after the current one." +"First of all, we need to create a new project - you can skip this step if " +"you already have one." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:176 +#: ../settings/security/third-party/google.rst:15 msgid "" -"If set to ``no`` (default), further workflows will be executed if they match " -"the condition. In this case, it is possible that your actions from the " -"current workflow can be overwritten by another workflow." +"Use this link to create a new project: https://console.cloud.google.com/" +"projectcreate" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:180 +#: ../settings/security/third-party/google.rst:18 msgid "" -"If set to ``yes``, no further worflows will be executed after the current " -"one." +"Now expand the menu, expand \"APIs & Services\" and select \"Credentials\". " +"Go to the tab \"OAuth consent screen\" first and ensure to fill in the " +"requested information - without doing so you can't create credentials!" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:184 -msgid "Priority" +#: ../settings/security/third-party/google.rst:None +msgid "Creating a consent screen" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:186 +#: ../settings/security/third-party/google.rst:25 msgid "" -"You can define the sequence, in which the workflows are executed. The " -"default value is ``500``." +"After filling in and saving the consent screen information, you can go to " +"the \"Credentials\" tab and create new \"OAuth client ID\"-Credentials." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:189 +#: ../settings/security/third-party/google.rst:28 msgid "" -"The workflows are executed in ascending order by their priority. That means " -"lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." +"Fill in the necessary information as follows and replace ``zammad_host`` " +"with your FQDN:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:2 -msgid "Learn by Example" +#: ../settings/security/third-party/google.rst:31 +msgid "**Application type** ``[x] Web application``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:4 -msgid "" -"This page provides some basic examples for Core Workflows. Of course you can " -"build much more complex workflows if needed." +#: ../settings/security/third-party/google.rst:34 +msgid "**Authorized JavaScript origins** ``https://zammad_host/``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:7 +#: ../settings/security/third-party/google.rst:37 msgid "" -"To learn about Core Workflows in detail, first go to :doc:`how-do-they-work`." +"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" +"callback``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:10 -msgid "Group Based Examples" +#: ../settings/security/third-party/google.rst:None +msgid "Adding a new OAuth client ID" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:12 +#: ../settings/security/third-party/google.rst:43 msgid "" -"All following workflows have the same base configurations. The workflow may " -"not use them all." +"After creating the credentials, go to your Zammad installation and navigate " +"to \"Admin > Security > Third Party Applications\" > Google. Enter your " +"Client ID and Client secret here." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:15 -msgid "Groups:" +#: ../settings/security/third-party/google.rst:None +msgid "Zammad" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:20 -msgid "Attributes:" +#: ../settings/security/third-party/google.rst:50 +msgid "After submitting, the login via Google can be used." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:22 -msgid "Category (Single tree selection field, not mandatory, agents only)" +#: ../settings/security/third-party/microsoft.rst:2 +msgid "Microsoft" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:23 +#: ../settings/security/third-party/microsoft.rst:4 msgid "" -"Approved (Boolean field, not mandatory, not shown, ``false`` as default)" +"Zammad's Microsoft connection allows your users with Microsoft accounts to " +"login. This works for Azure users as well and can be an alternative to :doc:" +"`/system/integrations/ldap/index`." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:24 -msgid "Operating System (Text field, not mandatory, not shown)" +#: ../settings/security/third-party/microsoft.rst:10 +msgid "" +"This documentation part does not cover our :doc:`📧 Microsoft 365 email " +"channel `." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:25 -msgid "Software used (Single selection field, not mandatory, not shown)" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screenshot showing Microsoft login button on Zammad login screen." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:68 -msgid "Group specific values and fields" +#: ../settings/security/third-party/microsoft.rst:30 +#: ../settings/security/third-party/microsoft.rst:53 +msgid "Supported account types:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:28 +#: ../settings/security/third-party/microsoft.rst:22 msgid "" -"This workflow set depends on the category field. It reduces the available " -"set of values based on the group selected." +"Please note that Zammad only supports these account types (App dependent):" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:33 -msgid "Workflow 2nd Level group" +#: ../settings/security/third-party/microsoft.rst:35 +msgid "Avatars of signing in users:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:35 +#: ../settings/security/third-party/microsoft.rst:33 msgid "" -"This reduces the category options to ``2nd Level/*``, ``Internal/*`` and " -"``Others``. It also sets further required fields to mandatory and visible." -msgstr "" - -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for 2nd level" +"Zammad currently ignores user avatars. If the user is registered with e.g. " +"Gravatar, Zammad will fetch the avatar from there if enabled. See :doc:" +"`Zammad Image Service ` for more." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:43 -msgid "Workflow Support group" +#: ../settings/security/third-party/microsoft.rst:38 +msgid "Step 1 - Register a Microsoft App for Zammad" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:45 +#: ../settings/security/third-party/microsoft.rst:40 msgid "" -"This reduces the category options to ``Support/*``, ``Internal/*`` and " -"``Others``. It also sets further required fields to visible." -msgstr "" - -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for support" +"Login to the `Microsoft Azure Portal `_ and " +"navigate to App registrations to create a new app. Provide the requested " +"information as follows and register your app." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:53 -msgid "Workflow Sales group" +#: ../settings/security/third-party/microsoft.rst:46 +msgid "Name:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:55 +#: ../settings/security/third-party/microsoft.rst:45 msgid "" -"This reduces the category options to ``Sales/*``, ``Internal/*`` and " -"``Others``." +"Any meaningful name fitting, this name will be displayed to users trying to " +"authenticate with this app." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for sales" +#: ../settings/security/third-party/microsoft.rst:49 +msgid "Choose one of the above mentioned account types (see Limitations)." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:68 -#: ../system/integrations/slack.rst:88 -msgid "The Result" +#: ../settings/security/third-party/microsoft.rst:51 +msgid "" +"The correct account type depends on your use case. If you want to use the " +"authentication internal only, choose the first option. If you're unsure, use " +"the \"Help me choose...\" link." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:63 -msgid "" -"This is what the agent would experience with the above workflows in place." +#: ../settings/security/third-party/microsoft.rst:58 +msgid "Redirect URI (optional):" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 +#: ../settings/security/third-party/microsoft.rst:56 msgid "" -"Workflow shows objects and limits options based on selections on the group" +"Select web and provide your callback URL. The callback URL looks like this: " +"``https://zammad.domain.tld/auth/microsoft_office365/callback``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:90 -msgid "Approval process" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to register a Microsoft app" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:71 -msgid "" -"In this case ``approved`` is visible to agents by default. For this " -"workflow, an additional role ``Approval person`` is required (no further " -"permissions)." +#: ../settings/security/third-party/microsoft.rst:71 +msgid "Within **API permissions** add the following permissions:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that restricts an approval attribute to specific roles" +#: ../settings/security/third-party/microsoft.rst:69 +msgid "``User.Read``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:81 -msgid "" -"This workflow may work best in combination with a :doc:`trigger ` but technically, this is not required." +#: ../settings/security/third-party/microsoft.rst:71 +msgid "Contacts" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:84 -msgid "" -"Select fields may be a better approach because they allow more values than " -"just a simple ``true`` or ``false``." +#: ../settings/security/third-party/microsoft.rst:71 +msgid "``Contacts.Read``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 +#: ../settings/security/third-party/microsoft.rst:73 msgid "" -"Workflow fixes possible values of \"Approved ?\" to a specific selection " -"depending on the users role" +"You can find these permissions within *Microsoft Graph → Delegated " +"permissions*." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:103 -msgid "State dependent mandatory fields" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to add required API permissions" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:93 +#: ../settings/security/third-party/microsoft.rst:80 msgid "" -"This workflow sets ``Category`` to mandatory if the agent wants to set the " -"states ``closed`` or ``pending close`` to enforce categorization." +"Within **Certificates & secrets** create a new client secret. Note down the " +"returned secret **value** for later. **Do not** use the secret ID!" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that sets fields to mandatory on specific states" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to create a new app secret" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 +#: ../settings/security/third-party/microsoft.rst:88 msgid "" -"Workflow sets category field to mandatory upon choosing closed or pending " -"close as state" +"From **Overview** copy your apps *Application (client) ID*. If you're using " +"a single tenant app, please also copy *Directory (tenant) ID*. You now have " +"all required information for Zammad." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:106 -msgid "Manual Ticket Handover Process" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to retreive application client and tenant IDs" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:108 -msgid "This example covers the handover of a ticket from one agent to another:" +#: ../settings/security/third-party/microsoft.rst:98 +msgid "Step 2 - Add App Credentials to Zammad" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:110 +#: ../settings/security/third-party/microsoft.rst:100 msgid "" -"When the ticket owner is modified, a new text field (\"Handover\") shows up " -"for a comment" +"Navigate to Security > Third-party Applications (Tab) within Zammad's admin " +"settings. Scroll down to the section *Authentication via Microsoft* and fill " +"in the required information." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:112 -msgid "" -"This may only be visible when the owner is changed, therefore it has to be " -"hidden in general" +#: ../settings/security/third-party/microsoft.rst:105 +msgid "App ID:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:114 -msgid "The input in this handover text field is mandatory" +#: ../settings/security/third-party/microsoft.rst:105 +msgid "This is your *Application (client) ID*." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:115 -msgid "" -"After submitting changes, the value of the handover field must be added as " -"an note to the ticket (via trigger)" +#: ../settings/security/third-party/microsoft.rst:108 +msgid "App secret:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:121 -msgid "Hiding handover field" +#: ../settings/security/third-party/microsoft.rst:108 +msgid "This is your *client secret* (value)." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Hiding the handover field in core workflows" +#: ../settings/security/third-party/microsoft.rst:113 +msgid "App Tenant ID:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:126 -msgid "Showing handover field and setting it to mandatory" +#: ../settings/security/third-party/microsoft.rst:111 +msgid "" +"**optional** only required for apps that use account type *Accounts in this " +"organizational directory only (Default Directory only - Single tenant).*" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Showing the handover field and set it as mandatory" +#: ../settings/security/third-party/microsoft.rst:115 +msgid "" +"Apply your settings by pressing submit and activate *Authentication via " +"Microsoft*." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:131 -msgid "Trigger writing handover input to a new article" +#: ../settings/security/third-party/microsoft.rst:None +msgid "" +"Screencast showing how to add app credentials and activating the\n" +"authentication method" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Write handover content to a new article" +#: ../settings/security/third-party/saml.rst:2 +msgid "SAML" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:133 +#: ../settings/security/third-party/saml.rst:4 msgid "" -"As a result, the ticket includes an article of the type note which includes " -"the predefined text and the handover comment." +"Connect your SAML (Security Assertion Markup Language) identity provider as " +"a single sign-on (SSO) method." msgstr "" -#: ../system/core-workflows/limitations.rst:6 -msgid "Core Workflows do not replace Triggers" +#: ../settings/security/third-party/saml.rst:7 +msgid "" +"SAML is an open standard for SSO authentication (among other things). Sign-" +"ins are shared across multiple **service providers** and managed by a " +"central **identity provider** (IdP)." msgstr "" -#: ../system/core-workflows/limitations.rst:5 +#: ../settings/security/third-party/saml.rst:11 msgid "" -"Workflows manipulate the behavior of fields. However, they do not set values " -"in fields because of actions." +"In this case, the service provider is Zammad, and the IdP is a software " +"service that you either host or subscribe to (*e.g.,* `Keycloak `_, `Redhat SSO Server `_, `ADFS `_, or `Okta `_)." msgstr "" -#: ../system/core-workflows/limitations.rst:16 -msgid "API calls are only partly affected" +#: ../settings/security/third-party/saml.rst:18 +msgid "" +"This guide assumes you are already using SAML within your organization (i." +"e., that your IdP is fully set up)." msgstr "" -#: ../system/core-workflows/limitations.rst:9 +#: ../settings/security/third-party/saml.rst:21 msgid "" -"Some options affect UI only and thus do not restrict responses and calls." +"Please note: Our instructions are based on connecting Zammad with Keycloak." msgstr "" -#: ../system/core-workflows/limitations.rst:11 -msgid "This affects the following actions:" +#: ../settings/security/third-party/saml.rst:25 +msgid "Step 1: Configure Your IdP" msgstr "" -#: ../system/core-workflows/limitations.rst:13 -msgid "select" +#: ../settings/security/third-party/saml.rst:28 +msgid "Add Zammad as a Client/App" msgstr "" -#: ../system/core-workflows/limitations.rst:14 -msgid "auto select" +#: ../settings/security/third-party/saml.rst:30 +msgid "" +"Import Zammad into your IdP using the XML configuration found at ``https://" +"your.zammad.domain/auth/saml/metadata``." msgstr "" -#: ../system/core-workflows/limitations.rst:15 -msgid "show" +#: ../settings/security/third-party/saml.rst:33 +msgid "" +"If your IdP doesn't support XML import, you will have to configure Zammad as " +"a new client/app manually using the above XML metadata file for reference." msgstr "" -#: ../system/core-workflows/limitations.rst:16 -msgid "hide" +#: ../settings/security/third-party/saml.rst:36 +msgid "For instance, when you see this tag:" msgstr "" -#: ../system/core-workflows/limitations.rst:25 -msgid "Some fields stay unavailable to customers" +#: ../settings/security/third-party/saml.rst:42 +msgid "" +"Set the **Assertion Consumer Service Binding URL** (sometimes also listed as " +"**Valid Redirect URIs**) to ``http://your.zammad.domain/auth/saml/callback``." msgstr "" -#: ../system/core-workflows/limitations.rst:19 -msgid "" -"For technical and security reasons, some default fields (the pale ones you " -"can't edit) stay unavailable for display and usage on customer permissions." +#: ../settings/security/third-party/saml.rst:47 +msgid "Set Up User Attribute Mapping" msgstr "" -#: ../system/core-workflows/limitations.rst:23 +#: ../settings/security/third-party/saml.rst:49 msgid "" -"If you require your customers to change e.g. priorities, please consider " -"using workarounds via :doc:`/system/objects` and :doc:`/manage/trigger`." +"Zammad requests the following user attributes (or “properties”) from the IdP:" msgstr "" -#: ../system/core-workflows/limitations.rst:29 -msgid "Ticket title changes not supported in edit mask" +#: ../settings/security/third-party/saml.rst:51 +msgid "Email address (``email``)" msgstr "" -#: ../system/core-workflows/limitations.rst:28 -msgid "" -"It is currently not possible to perform changes of the ticket title in the " -"edit mask (e.g. renaming, set to read-only)." +#: ../settings/security/third-party/saml.rst:52 +msgid "Full name (``name``)" msgstr "" -#: ../system/core-workflows/limitations.rst:37 -msgid "What is out of scope of Core Workflows?" +#: ../settings/security/third-party/saml.rst:53 +msgid "Given name (``first_name``)" msgstr "" -#: ../system/core-workflows/limitations.rst:32 -msgid "" -"There are some things that would count as workflow but are either done via :" -"doc:`/manage/trigger` or :doc:`/manage/scheduler`." +#: ../settings/security/third-party/saml.rst:54 +msgid "Family name (``last_name``)" msgstr "" -#: ../system/core-workflows/limitations.rst:35 -msgid "Such as (but not limited to):" +#: ../settings/security/third-party/saml.rst:56 +msgid "" +"You may need to set up “mappers” (or “mappings”) to tell your IdP how user " +"attributes in SAML correspond to those in Zammad. For a more detailed " +"breakdown, refer to the XML metadata file referenced in the previous section." msgstr "" -#: ../system/core-workflows/limitations.rst:37 -msgid "up- or downgrade permissions of users" +#: ../settings/security/third-party/saml.rst:62 +msgid "Per-IdP Instructions" msgstr "" -#: ../system/core-workflows/limitations.rst:38 -msgid "affecting article creation or listing" +#: ../settings/security/third-party/saml.rst:102 +msgid "Keycloak" msgstr "" -#: ../system/data-privacy.rst:2 -msgid "Data Privacy" +#: ../settings/security/third-party/saml.rst:65 +msgid "" +"**To add Zammad as a client,** save the XML configuration to disk (``https://" +"your.zammad.domain/auth/saml/metadata``) and use **Clients > Clients list > " +"Import client** in the Keycloak admin panel." msgstr "" -#: ../system/data-privacy.rst:4 +#: ../settings/security/third-party/saml.rst:70 msgid "" -"For compliance with GDPR and other data privacy laws, you may wish to " -"**permanently delete users from the system**, along with **all of their " -"associated tickets**." +"To help Zammad **match its own user accounts to Keycloak users**, create a " +"user attribute (or “property”) mapper. In **Clients list**, click on your " +"newly created Client ID, choose the tab **Client scopes** and click on the " +"link which refers to your Zammad instance. Choose **Add mapper > By " +"configuration > User Property** and create a mapper with the following " +"entries:" 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 `!" +#: ../settings/security/third-party/saml.rst:78 +msgid "**Name**" msgstr "" -#: ../system/data-privacy.rst:12 -msgid "" -"Access to this panel requires ``admin.data_privacy`` permissions (introduced " -"in Zammad 3.5)." +#: ../settings/security/third-party/saml.rst:80 +msgid "**Mapper Type**" msgstr "" -#: ../system/data-privacy.rst:15 -msgid "" -"On older systems that have not been updated yet, customers can also be :docs:" -"`deleted via the Zammad console `." +#: ../settings/security/third-party/saml.rst:81 +msgid "``User Property``" msgstr "" -#: ../system/data-privacy.rst:22 -msgid "User deletion dialog in the Data Privacy panel" +#: ../settings/security/third-party/saml.rst:82 +msgid "**Property**" msgstr "" -#: ../system/data-privacy.rst:22 -msgid "" -"The user deletion dialog lists some of the tickets that will be removed from " -"the system along with the user." +#: ../settings/security/third-party/saml.rst:83 +msgid "``emailAddress``" msgstr "" -#: ../system/data-privacy.rst:27 -msgid "Deleting Users via GUI" +#: ../settings/security/third-party/saml.rst:84 +msgid "**SAML Attribute Name**" msgstr "" -#: ../system/data-privacy.rst:29 -msgid "🔥 **All deletions are FINAL!**" +#: ../settings/security/third-party/saml.rst:86 +msgid "**SAML Attribute NameFormat**" msgstr "" -#: ../system/data-privacy.rst:31 -msgid "Once you click “Delete”, the action cannot be canceled or undone." +#: ../settings/security/third-party/saml.rst:87 +msgid "``basic``" msgstr "" -#: ../system/data-privacy.rst:33 +#: ../settings/security/third-party/saml.rst:89 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." +"In the example above, we're telling Zammad that whenever it receives a SAML " +"login request, it should take the ``email`` property from Keycloak, look for " +"a Zammad user with the same ``email`` attribute, and create a new session " +"for that user." msgstr "" -#: ../system/data-privacy.rst:36 -msgid "**The following records cannot be deleted:**" +#: ../settings/security/third-party/saml.rst:95 +msgid "" +"If your Keycloak users' email addresses are stored on another property (*e." +"g.,* ``username``), adjust accordingly." msgstr "" -#: ../system/data-privacy.rst:38 -msgid "your own account" +#: ../settings/security/third-party/saml.rst:98 +msgid "" +"Back in **Settings**, enter the Client ID (``https://your.zammad.domain/auth/" +"saml/metadata``) in the field **Master SAML Processing URL**." msgstr "" -#: ../system/data-privacy.rst:39 -msgid "the system's last remaining administrator account" +#: ../settings/security/third-party/saml.rst:101 +msgid "You also need to enable **Sign assertions**." msgstr "" -#: ../system/data-privacy.rst:42 -msgid "Step 1: Find a User / Confirm Deletion" +#: ../settings/security/third-party/saml.rst:105 +msgid "Step 2: Configure Zammad" msgstr "" -#: ../system/data-privacy.rst:44 -msgid "There are three ways to access the user deletion dialog:" +#: ../settings/security/third-party/saml.rst:107 +msgid "" +"Enable SAML and enter your IdP's details in the Admin Panel under **Settings " +"> Security > Third Party Applications > Authentication via SAML**:" msgstr "" -#: ../system/data-privacy.rst:51 -msgid "**from the user's profile**" +#: ../settings/security/third-party/saml.rst:None +msgid "Example configuration of SAML part 1" msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Accessing the user deletion dialog in a user profile" +#: ../settings/security/third-party/saml.rst:119 +msgid "Display name" msgstr "" -#: ../system/data-privacy.rst:51 -msgid "Click **Action > Delete**." +#: ../settings/security/third-party/saml.rst:116 +msgid "" +"Allows you to define a custom button name for SAML. This helps your users to " +"understand better what the button on the login page does." msgstr "" -#: ../system/data-privacy.rst:58 -msgid "**in the “Manage > Users” Admin Panel**" +#: ../settings/security/third-party/saml.rst:119 +msgid "Defaults to ``SAML``." msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Accessing the user deletion dialog under “Users” in the Admin Panel" +#: ../settings/security/third-party/saml.rst:123 +msgid "IDP SSO target URL" msgstr "" -#: ../system/data-privacy.rst:58 -msgid "Use the **⋮ Actions** menu for the target user." +#: ../settings/security/third-party/saml.rst:122 +msgid "" +"This is the target URL Zammad shall redirect to when the user presses the " +"SAML button. For Keycloak, this needs to look like https://your.domain/" +"realms/your-realm/protocol/saml" msgstr "" -#: ../system/data-privacy.rst:66 ../system/data-privacy.rst:104 -msgid "**in the “System > Data Privacy” Admin Panel**" +#: ../settings/security/third-party/saml.rst:127 +msgid "IDP single logout target URL" msgstr "" -#: ../system/data-privacy.rst:0 +#: ../settings/security/third-party/saml.rst:126 msgid "" -"Accessing the user deletion dialog under “Data Privacy” in the Admin Panel" +"This is the URL to which the single logout request and response should be " +"sent." msgstr "" -#: ../system/data-privacy.rst:65 +#: ../settings/security/third-party/saml.rst:131 +msgid "IDP certificate" +msgstr "" + +#: ../settings/security/third-party/saml.rst:130 msgid "" -"Use the **New Deletion Task** button. Search for users by name or email " -"address." +"The public certificate of your IDP for Zammad to verify during the callback " +"phase." msgstr "" -#: ../system/data-privacy.rst:79 -msgid "**Delete organizations**" +#: ../settings/security/third-party/saml.rst:145 +msgid "IDP certificate fingerprint" msgstr "" -#: ../system/data-privacy.rst:69 +#: ../settings/security/third-party/saml.rst:134 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:" +"The fingerprint of your IDPs public certificate to verify during callback " +"phase." msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Deleting an organization via the user deletion dialog" +#: ../settings/security/third-party/saml.rst:137 +msgid "🔏 **For the IdP certificate / certificate fingerprint:**" msgstr "" -#: ../system/data-privacy.rst:78 +#: ../settings/security/third-party/saml.rst:139 msgid "" -"If this option does not appear, make sure there are no pending deletion " -"tasks for other customers from this organization." +"Provide **only one or the other**—do not provide both! (Between the two, we " +"recommend the signing certificate itself: fingerprints use SHA-1, which `has " +"been broken for a while now `_.)" msgstr "" -#: ../system/data-privacy.rst:82 -msgid "Step 2: Monitor Deletion Job Status" +#: ../settings/security/third-party/saml.rst:144 +msgid "" +"**Keycloak users:** Find your certificate in the Keycloak admin panel under " +"**Realm Settings > Keys > Algorithm: RS256 > Certificate**." msgstr "" -#: ../system/data-privacy.rst:84 +#: ../settings/security/third-party/saml.rst:151 +msgid "Name identifier format" +msgstr "" + +#: ../settings/security/third-party/saml.rst:148 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:" +"This is the unique identifiers field type. Usually it should be ``urn:oasis:" +"names:tc:SAML:1.1:nameid-format:emailAddress``." msgstr "" -#: ../system/data-privacy.rst:98 -msgid "**in the Activity Stream**" +#: ../settings/security/third-party/saml.rst:151 +msgid "Zammad **expects an email address as unique identifier**!" msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Activity Stream showing data privacy tasks" +#: ../settings/security/third-party/saml.rst:155 +msgid "UID attribute name" msgstr "" -#: ../system/data-privacy.rst:94 +#: ../settings/security/third-party/saml.rst:154 msgid "" -"For each deleted user, the Activity Stream will be updated twice—once when " -"the task is created, and once when it's complete." +"Here you can define an attribute that uniquely identifies the user. If " +"unset, the name identifier returned by the IDP is used." msgstr "" -#: ../system/data-privacy.rst:97 -msgid "" -"These notifications are only visible to users with ``admin.data_privacy`` " -"permissions." +#: ../settings/security/third-party/saml.rst:None +msgid "Example configuration of SAML part 2" msgstr "" -#: ../system/data-privacy.rst:0 +#: ../settings/security/third-party/saml.rst:163 msgid "" -"The task list within Data Privacy shows removals being in progress and " -"completed." +"Decide if the certificate for the connection to the IdP service has to be " +"verified or not (default: ``yes``)." msgstr "" -#: ../system/data-privacy.rst:107 -msgid "Frequently Asked Questions" +#: ../settings/security/third-party/saml.rst:169 +msgid "Signing & Encrypting" msgstr "" -#: ../system/data-privacy.rst:121 -msgid "What happens if I receive an email from a deleted customer?" -msgstr "" - -#: ../system/data-privacy.rst:110 +#: ../settings/security/third-party/saml.rst:169 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." +"Define if you want to sign, encrypt, do both or nothing for the requests." msgstr "" -#: ../system/data-privacy.rst:115 -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**." +#: ../settings/security/third-party/saml.rst:179 +msgid "Certificate (PEM)" msgstr "" -#: ../system/data-privacy.rst:130 -msgid "What about user information stored in internal notes or other messages?" +#: ../settings/security/third-party/saml.rst:172 +msgid "" +"Paste the public certificate of your Zammad SAML client, if you want to " +"encrypt the requests." msgstr "" -#: ../system/data-privacy.rst:124 -msgid "" -"The deletion process removes **user accounts and associated tickets only**." +#: ../settings/security/third-party/saml.rst:175 +msgid "Make sure the certificate is:" msgstr "" -#: ../system/data-privacy.rst:126 -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." +#: ../settings/security/third-party/saml.rst:177 +msgid "already valid and not yet expired" msgstr "" -#: ../system/data-privacy.rst:137 -msgid "I deleted an user and can still see a message they sent!" +#: ../settings/security/third-party/saml.rst:178 +msgid "no CA certificate" msgstr "" -#: ../system/data-privacy.rst:133 -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." +#: ../settings/security/third-party/saml.rst:179 +msgid "valid for signing and encrypting" msgstr "" -#: ../system/data-privacy.rst:141 -msgid "I removed a customer, now my reporting is off!" +#: ../settings/security/third-party/saml.rst:185 +msgid "Private key (PEM)" msgstr "" -#: ../system/data-privacy.rst:140 +#: ../settings/security/third-party/saml.rst:182 msgid "" -"When removing users and their tickets, all references are removed. This also " -"affects e.g. Reporting - these information are lost." +"Paste the private key of your Zammad SAML client here, if you want to sign " +"the requests." msgstr "" -#: ../system/data-privacy.rst:145 -msgid "How long does Zammad store created tasks?" +#: ../settings/security/third-party/saml.rst:185 +msgid "Make sure the key is an RSA key with a length of at least 2048 bits." msgstr "" -#: ../system/data-privacy.rst:144 -msgid "" -"Please see the on-premise data section of the :docs:`data privacy ` chapter." +#: ../settings/security/third-party/saml.rst:188 +msgid "Private key secret" msgstr "" -#: ../system/data-privacy.rst:150 -msgid "What about re-assigned tickets? I want to delete them, too." +#: ../settings/security/third-party/saml.rst:188 +msgid "If your private key is secured with a secret, you can provide it here." msgstr "" -#: ../system/data-privacy.rst:148 -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." +#: ../settings/security/third-party/saml.rst:192 +msgid "Your callback URL" msgstr "" -#: ../system/data-privacy.rst:154 -msgid "Why are there so many deletion task entries, I didn't create them!" +#: ../settings/security/third-party/saml.rst:191 +msgid "" +"This URL is needed for your IdP configuration so it knows where to redirect " +"to after successful authentication." msgstr "" -#: ../system/data-privacy.rst:153 +#: ../settings/security/third-party/saml.rst:194 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." +"After saving your input by clicking on the \"Submit\" button, Zammad " +"verifies the provided keys/certificates (e.g. if they are valid for signing/" +"encrypting and if they aren't expired)." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:2 -msgid "Admin Panel Reference" +#: ../settings/security/third-party/saml.rst:199 +msgid "" +"See :ref:`automatic account linking ` for details " +"on how to link existing Zammad accounts to IdP accounts." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:None -msgid "Screenshot of Checkmk settings overview" +#: ../settings/security/third-party/saml.rst:205 +msgid "Automatic account linking doesn't work" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:12 +#: ../settings/security/third-party/saml.rst:206 msgid "" -"Which :doc:`group ` should Checkmk tickets be assigned " -"to as a default (*i.e.,* when none is specified)?" +"Have you double-checked your IdP's user attribute mapping configuration?" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:15 -msgid "(Applies to :ref:`API alerts ` only.)" +#: ../settings/security/third-party/twitter.rst:4 +msgid "" +"It is possible to create a quick login for your helpdesk via Twitter. To do " +"so, you need to follow these steps:" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:21 -msgid "Auto close" +#: ../settings/security/third-party/twitter.rst:8 +msgid "Register Twitter App" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:18 -msgid "" -"Should Zammad automatically close tickets if a service has recovered on its " -"own?" +#: ../settings/security/third-party/twitter.rst:10 +msgid "Go to https://dev.twitter.com/apps and login with your account." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:21 -msgid "(Agents will receive notifications for such closures as appropriate.)" +#: ../settings/security/third-party/twitter.rst:15 +msgid "Click on \"Create App\"" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:30 -msgid "Auto-close state" +#: ../settings/security/third-party/twitter.rst:None +msgid "new app page" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:24 -msgid "What ticket state should be applied when “auto-closing” a ticket?" +#: ../settings/security/third-party/twitter.rst:20 +msgid "" +"Enter app settings. As \"Callback URL\" you need to enter ``https://" +"zammad_host/api/v1/external_credentials/twitter/callback``. You need to " +"replace ``zammad_host`` with the domain of your Zammad system." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:26 +#: ../settings/security/third-party/twitter.rst:24 msgid "" -"You can choose from the seven built-in ticket states. If these states aren't " -"enough for you, you can :ref:`define a new ticket state ` for this purpose as well. This can be useful for tracking " -"tickets with :doc:`reports `, for example." +"After the app has been created, update the application icon and organization " +"attributes." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:35 -#: ../system/integrations/cti/includes/recent-logs.include.rst:2 -#: ../system/integrations/ldap/index.rst:74 -#: ../system/integrations/pgp/index.rst:106 -msgid "Recent Logs" +#: ../settings/security/third-party/twitter.rst:None +msgid "set permissions to receive and send direct messages" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:None -msgid "Screenshot of Checkmk \"Recent Logs\" section" +#: ../settings/security/third-party/twitter.rst:30 +msgid "" +"Next we need to set ``read, write and access direct messages`` permissions " +"for the app." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:41 -msgid "" -"If you're having trouble getting Zammad and Checkmk to play nicely together, " -"this section can help you troubleshoot." +#: ../settings/security/third-party/twitter.rst:None +msgid "click on Keys & Access Token, note them" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:44 +#: ../settings/security/third-party/twitter.rst:36 msgid "" -"It contains a record of the fifty most recent transactions that Zammad knows " -"about, including each one's request/response details and return status." +"Go to \"Keys and Access Token\" tab and note the \"Consumer Key\" and " +"\"Consumer Secret\"." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:2 -msgid "API Reference" +#: ../settings/security/third-party/twitter.rst:40 +msgid "Configure Zammad as Twitter App" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:4 +#: ../settings/security/third-party/twitter.rst:42 msgid "" -"For most users, :ref:`the sample scripts from the Setup Guide ` will do the job just fine. But if you want more fine-grained control" -"—for instance, to create high- and low-priority tickets for different types " -"of system events—then you'll have to customize the data those scripts send " -"to Zammad." +"Go to \"Admin > Security > Twitter > Third Party Applications > Twitter\" " +"Section." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:15 -msgid "" -"This custom script will automatically set all tickets it creates to **high " -"priority** and **assign them to charlie@chrispresso.com**." +#: ../settings/security/third-party/twitter.rst:None +msgid "Admin > Security > Third Party Applications" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:32 -msgid "How Does it Work?" +#: ../settings/security/third-party/twitter.rst:48 +msgid "" +"Fill in the \"Twitter Key\" and the \"Twitter Secret\" and click the " +"\"Submit\" button." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:34 +#: ../settings/security/third-party/twitter.rst:51 msgid "" -"There are two kinds of data you can pass to the API, both in the form of key-" -"value pairs:" +"Now you can link accounts via \"Avatar > Profile > Link Accounts\" or login " +"via Zammad login page." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:44 -msgid "Checkmk parameters" +#: ../settings/security/two-factor.rst:11 +msgid "Two-factor Authentication Methods" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:38 -msgid "" -"are required, and make up the **contents** of the resulting tickets/" -"articles. They also determine whether an event creates a new ticket or " -"updates/closes an existing one." +#: ../settings/security/two-factor.rst:2 +msgid "Two-Factor Authentication" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:42 +#: ../settings/security/two-factor.rst:4 msgid "" -"These are the only values used in the sample scripts. **Use them as-is**; " -"technically, they can be customized, but it's hard to imagine a good reason " -"for it." +"Two-factor authentication (2FA) enhances the security of Zammad accounts by " +"adding an extra layer of verification beyond a password. It requires users " +"to provide two different types of authentication factors, typically " +"something they know (like a password) and something they possess (like a " +"mobile device or a security token), to ensure that only authorized " +"individuals can access the account." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:52 -msgid "Ticket attributes" +#: ../settings/security/two-factor.rst:19 +msgid "Enable Recovery Codes" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:47 +#: ../settings/security/two-factor.rst:21 msgid "" -"are optional, and can be used to **adjust settings** on newly created " -"tickets (*e.g.,* set the owner, group, priority, or state)." +"Recovery codes are one-time use security codes that can be used by the user " +"if they lose access to their other two-factor authentication methods. They " +"cannot be used on their own, they can only be activated if at least one two-" +"factor authentication method is enabled." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:50 -msgid "" -"If you want to customize your Checkmk alert script, do it with these. Simply " -"add an extra “form” option for each one (``-F \"key=value\"``) to your " -"script's ``curl`` command line, as in the example above." +#: ../settings/security/two-factor.rst:None +msgid "Enable Recovery Codes Setting" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:54 -msgid "💡 **It's just an API endpoint!**" +#: ../settings/security/two-factor.rst:30 +msgid "" +"Recovery codes can only be used as a backup method. If enabled, they will be " +"automatically generated for the user once they set up their initial two-" +"factor authentication method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:56 +#: ../settings/security/two-factor.rst:34 msgid "" -"When using Checkmk integration, messages need to be formatted in a certain " -"way, but that *doesn't mean the messages actually have to come from Checkmk*." +"The user will be asked to print out or save the generated recovery codes in " +"a safe place. Once used, a recovery code cannot be reused." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:59 +#: ../settings/security/two-factor.rst:37 msgid "" -"If you use another monitoring tool that's not officially supported by " -"Zammad, there's probably a way to make it work with your Checkmk callback " -"URL." +"Users will also have an option to regenerate their recovery codes at any " +"time, which invalidates already existing recovery codes and provides them " +"with a list of fresh codes." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:63 -msgid "Checkmk Parameters" +#: ../settings/security/two-factor.rst:41 +msgid "" +"After you enable this setting, when the user completes a setup of their " +"initial two-factor authentication method, they will be presented with a list " +"of recovery codes and instructed to save them for later use." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:65 -msgid "" -"When a notification is received, Zammad creates a new article containing the " -"details of the event that triggered it:" +#: ../settings/security/two-factor.rst:None +msgid "Recovery Codes Generation Modal Dialog" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:None -msgid "Checkmk article body" +#: ../settings/security/two-factor.rst:50 +msgid "Enforce the Set Up of the Two-Factor Authentication" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:72 +#: ../settings/security/two-factor.rst:52 msgid "" -"These details come from the fields listed below, which correspond to " -"parameters provided by Checkmk (``$NOTIFY_*``)." +"In case you wish to require your users to set up at least one two-factor " +"authentication method for their account, you can do this by selecting " +"specific user roles the requirement applies to in **Enforced for user " +"roles** setting. Of course you must have at least one two-factor " +"authentication method enabled for this setting to take effect." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:75 -msgid "**Required fields are marked with an asterisk (\\*).**" +#: ../settings/security/two-factor.rst:None +msgid "Enforced for User Roles Setting" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:79 -msgid "event_id\\*" +#: ../settings/security/two-factor.rst:62 +msgid "" +"After you change this setting, if the user has one of the selected roles on " +"their account, they will be forced to set up the two-factor authentication " +"upon next sign in or application reload." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:78 +#: ../settings/security/two-factor.rst:66 msgid "" -"A unique ID for the system event. (``$NOTIFY_SERVICEPROBLEMID`` / " -"``$NOTIFY_HOSTPROBLEMID``)" +"A modal dialog with instructions will be shown, and they will not be able to " +"do any work before they set up at least one two-factor method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:86 -msgid "host\\*" +#: ../settings/security/two-factor.rst:None +msgid "Modal Dialog for Enforcing Two-Factor Authentication Set Up" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:82 +#: ../settings/security/two-factor.rst:74 +msgid "Reset Two-Factor Authentication for a Specific User" +msgstr "" + +#: ../settings/security/two-factor.rst:76 msgid "" -"The hostname of the system that the event originated from. " -"(``$NOTIFY_HOSTNAME``)" +"In case an user isn't able to login anymore because of an inaccessible " +"second factor, you can reset the user's 2FA method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:85 +#: ../settings/security/two-factor.rst:79 msgid "" -"Used to determine if a new event belongs to an existing ticket. Also used in " -"the subject line of the resulting article (“ is ”)." +"To do this, go to the user management and search for the relevant user. " +"After you found the account, click the button in the action column and " +"select \"Manage Two-Factor Authentication\":" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:96 -msgid "service" +#: ../settings/security/two-factor.rst:None +msgid "Context menu in action column in user management" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:89 +#: ../settings/security/two-factor.rst:87 msgid "" -"The name of the service that the event originated from. " -"(``$NOTIFY_SERVICEDESC``)" +"After selecting this, you can see a dialog where you can either reset one " +"2FA method or reset all of the user's 2FA methods:" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:92 -msgid "Used to determine if a new event belongs to an existing ticket." +#: ../settings/security/two-factor.rst:None +msgid "Dialog for resetting user's 2FA method" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:94 -#: ../system/integrations/checkmk/api-reference.rst:110 -msgid "Displayed as ``-`` when omitted." +#: ../settings/security/two-factor.rst:94 +msgid "" +"Choose the fitting one, click on the corresponding \"Remove ...\" button and " +"confirm your action. The user now has to setup a new 2FA method, depending " +"on your 2FA configuration." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:104 -msgid "state\\*" +#: ../settings/security/two-factor/authenticator-app.rst:2 +msgid "Authenticator App" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:99 +#: ../settings/security/two-factor/authenticator-app.rst:4 msgid "" -"The current state of the service or host in question. " -"(``$NOTIFY_SERVICESTATE`` / ``$NOTIFY_HOSTSTATE``)" +"The authenticator app method is a type of two-factor authentication that " +"uses a mobile application to generate one-time codes for account " +"verification. After setting up the authenticator app on their device, the " +"user links it to their Zammad account." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:102 +#: ../settings/security/two-factor/authenticator-app.rst:12 msgid "" -"Used to detect when a ticket should be auto-closed (*i.e.,* on ``OK``/" -"``UP``). Also used in the subject line of the resulting article (“ is " -"”)." +"When logging in, the user is prompted to enter a time-sensitive code " +"generated by the app, in addition to their password. This code acts as the " +"second factor of authentication, providing an extra layer of security as it " +"changes periodically and is unique to the user's device." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:110 -msgid "text" +#: ../settings/security/two-factor/authenticator-app.rst:None +msgid "Security Code in Google Authenticator App" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:107 +#: ../settings/security/two-factor/authenticator-app.rst:22 msgid "" -"The output of the process that triggered the event. " -"(``$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" +"The app generates codes based on a shared secret key stored securely on both " +"the user's device and the server, ensuring a synchronized and secure " +"authentication process. The method of generating the codes is sometimes also " +"called TOTP (time-based one-time password)." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:121 -msgid "" -"The Object Manager attribute panel displays built-in and custom\n" -"attribute names." +#: ../settings/security/two-factor/authenticator-app.rst:28 +msgid "Enabling the Authenticator App Method" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:121 -msgid "Find a complete list of ticket attributes in the Object Manager." +#: ../settings/security/two-factor/authenticator-app.rst:30 +#: ../settings/security/two-factor/security-keys.rst:28 +msgid "To enable the method, just toggle the switch on in the settings." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:123 -msgid "" -"Ticket attributes are entirely optional, and can be used to customize the " -"tickets that Checkmk creates. (Note that these attributes will be ignored if " -"a new event belongs to an existing ticket.)" +#: ../settings/security/two-factor/authenticator-app.rst:None +msgid "Authenticator App Switch in Settings" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:128 +#: ../settings/security/two-factor/authenticator-app.rst:36 msgid "" -"Why would you want to do this? Maybe you have only one IT guy, and all " -"system monitoring issues should be automatically assigned to him. Or, maybe " -"you're creating multiple notification rules so that database outages take " -"higher priority than disk space warnings." +"Now the users will be able to set up this two-factor authentication method " +"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " +"Once they do, on next sign-in with password, they will be asked to provide " +"an additional security code generated by their mobile device." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:135 -msgid "In most cases, you'll probably want to set one of the following:" +#: ../settings/security/two-factor/security-keys.rst:2 +msgid "Security Keys" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:137 -msgid "group" +#: ../settings/security/two-factor/security-keys.rst:4 +msgid "" +"The security keys method is a type of a two-factor authentication that uses " +"Web Authentication API in the browser for verifying user's identity. The " +"user can register multiple hardware or software security keys with their " +"Zammad account and then they can use it during the sign-in process." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:139 -msgid "state" +#: ../settings/security/two-factor/security-keys.rst:12 +msgid "" +"When logging in, the user is prompted to provide the same security key they " +"registered with their account, in addition to their password. This key acts " +"as the second factor of authentication, providing an extra layer of security." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:140 -msgid "priority" +#: ../settings/security/two-factor/security-keys.rst:None +msgid "Security Key dialog in Safari on macOS" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:142 +#: ../settings/security/two-factor/security-keys.rst:21 msgid "" -"but in practice, you can set almost any attribute, including :doc:`custom " -"ones you created through the Object Manager `." -msgstr "" - -#: ../system/integrations/checkmk/api-reference.rst:145 -msgid "Please note that the following attributes are **not customizable**:" +"The type of the key can range from hardware USB sticks to passkeys stored in " +"a device of user's choice. Which type can be used depends on the browser " +"flavor and the platform of the user." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:147 -msgid "title" +#: ../settings/security/two-factor/security-keys.rst:26 +msgid "Enabling the Security Keys Method" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:148 -msgid "id" +#: ../settings/security/two-factor/security-keys.rst:None +msgid "Security Keys Switch in Settings" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:149 -msgid "ticket number" +#: ../settings/security/two-factor/security-keys.rst:34 +msgid "" +"Now the users will be able to set up this two-factor authentication method " +"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " +"Once they do, on next sign-in with password, they will be asked to provide " +"the same security key they registered during the setup." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:151 -msgid "created_by_id" +#: ../settings/system/system-selfhosted.include.rst:3 +msgid "" +"Below settings are only available to self hosted users. In hosted " +"environments we're handling these settings for you to ensure service " +"stability." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:152 -msgid "updated_by_id" +#: ../settings/system/base.rst:11 +msgid "Fully Qualified Domain Name" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:155 -msgid "Which Values Can Be Set?" +#: ../settings/system/base.rst:7 +msgid "The URL of your Zammad installation." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:157 -msgid "😵 **Invalid values → unpredictable behavior**" +#: ../settings/system/base.rst:9 ../settings/system/base.rst:17 +msgid "This setting is used within :doc:`/misc/variables` and notifications." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:159 -msgid "" -"If you provide a value that Zammad doesn't understand (*e.g.,* ``-F " -"\"priority=high\"``), it's not always clear what will happen. In some cases, " -"a ticket will be created with the default values instead - but in others, it " -"may not be created at all!" +#: ../settings/system/system-base.include.rst:1 +msgid "It is automatically set by the *Getting Started wizard*." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:164 -msgid "So what values does Zammad understand, then? Well, it depends..." +#: ../settings/system/system-base.include.rst:5 +msgid "Changing this setting also changes callback URLs for your channels etc." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:168 -msgid "Use an email address or username:" +#: ../settings/system/system-base.include.rst:6 +msgid "This setting can have negative affects on being able to login." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:190 -msgid "group & priority" +#: ../settings/system/base.rst:19 +msgid "HTTP type" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:175 -msgid "Refer to the dropdown menus in the ticket pane:" +#: ../settings/system/base.rst:14 +msgid "" +"The HTTP type tells your installation how your clients connect. This is " +"relevant for authentication and cookie security." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:0 -msgid "See possible values for certain attributes in the ticket pane." +#: ../settings/system/base.rst:31 +msgid "SystemID" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:187 -msgid "🙅 **Ticket state CANNOT be set this way!**" +#: ../settings/system/base.rst:22 +msgid "" +"This ID is being used within your ticket number. In case you're " +"communicating with another ticket system with similar ticket number schemes " +"this ID greatly reduces the risk of false follow ups." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:189 +#: ../settings/system/base.rst:26 msgid "" -"Why? Because ``-F \"state=...\"`` is already used :ref:`as a Checkmk " -"parameter `." +"The SystemID is randomly selected upon installation of Zammad (``1-99``)." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:222 -msgid "Everything Else" +#: ../settings/system/base.rst:30 +msgid "" +"**Do not** change this setting in a productive system! Your Zammad " +"installation may no longer recognize old ticket number based follow ups upon " +"change!" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:193 -msgid "" -"To set any other attributes, it helps to know your way around the :docs:" -"`rails console `. Valid values are those that you can " -"set with a string:" +#: ../settings/system/frontend.rst:2 +msgid "Frontend" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:218 -msgid "These values can then be passed directly to the API:" +#: ../settings/system/frontend.rst:22 +msgid "Core Workflow Ajax Mode" msgstr "" -#: ../system/integrations/checkmk/index.rst:16 -msgid "How does it work?" +#: ../settings/system/frontend.rst:6 +msgid "" +"This setting allows administrators to enforce :doc:`/system/core-workflows` " +"to use Ajax-Calls instead of web sockets. You'll usually only need this if " +"you experience serious issues as noted below." msgstr "" -#: ../system/integrations/checkmk/index.rst:2 -msgid "Checkmk" +#: ../settings/system/frontend.rst:10 +msgid "**🤓 Possible (technical) reasons**" msgstr "" -#: ../system/integrations/checkmk/index.rst:4 +#: ../settings/system/frontend.rst:12 msgid "" -"`Checkmk `_ is a powerful IT monitoring tool that can " -"send real-time status alerts to Zammad via email or REST API. Set these " -"alerts up in Checkmk, and Zammad will automatically create, update, and " -"close tickets based on the health of your system:" +"In some cases, your network structure (e.g. firewalls, proxies) may " +"disconnect long web socket connections. This leads to select fields staying " +"empty (e.g. owner selection *after* selecting your group) or fields not " +"shown / hidden (e.g. when switching to or from pending states, the \"pending " +"till\" field not showing / hiding)." msgstr "" -#: ../system/integrations/checkmk/index.rst:14 -msgid "Screenshot of ticket created by Checkmk notifications" +#: ../settings/system/frontend.rst:18 +msgid "" +"Please keep in mind that the Ajax fallback may cause serious pressure on " +"your application server. If you have the choice stick to web sockets." msgstr "" -#: ../system/integrations/checkmk/index.rst:14 -msgid "Multiple alerts, same ticket." +#: ../settings/system/frontend.rst:22 +msgid "Default: ``no`` (inactive)" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:2 -msgid "Setup Guide" +#: ../settings/system/frontend.rst:53 +msgid "Show calendar weeks in the picker of date/datetime fields" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:4 +#: ../settings/system/frontend.rst:25 msgid "" -"Whenever the Checkmk integration is enabled, Zammad listens for messages on " -"its API and over email. As long as those messages follow the required " -"format, Zammad will create new tickets (or find and update existing ones) " -"based on the message contents." +"With this setting you can instruct Zammad to provide week number display " +"globally for all users. Calendar with week number display are usually used " +"in business sectors and may not be relevant for everyone." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:10 +#: ../settings/system/frontend.rst:29 msgid "" -"That means that “setting up Checkmk integration” is simply a matter of " -"**adding configuration to your Checkmk site**: telling it when to send these " -"messages and what to say. To do that, you'll need to create a new " -"**notification rule** (see `Checkmk's official docs `_ for help with that)." +"This setting affects *all areas* - you'll also see week numbers in the admin " +"panel for e.g. triggers and macros." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:17 -msgid "" -"As part of this new rule, you'll have to choose a **notification method** " -"(*i.e.,* a script to execute whenever the rule is triggered). This script " -"will be written by you (samples below), and contain the logic for sending " -"API/email messages to Zammad:" +#: ../settings/system/frontend.rst:32 +msgid "Default: ``no`` (not shown)" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:26 -msgid "Checkmk \"New Rule\" dialog" +#: ../settings/system/frontend.rst:53 +msgid "Here's the difference:" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:26 -msgid "" -"Find your custom scripts in the Checkmk WATO under **Notifications > New " -"Rule > Notification Method**." +#: ../settings/system/frontend.rst:0 +msgid "Screenshot showing Zammad's date picker (in the default way)" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:29 -msgid "" -"Once you're done setting up your new rule, you're all set! New tickets " -"should start coming in and auto-updating any time your rule is triggered." +#: ../settings/system/frontend.rst:41 +msgid "Set to ``no``" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:33 +#: ../settings/system/frontend.rst:0 msgid "" -"(If you need help troubleshooting, be sure to check the :ref:`checkmk-recent-" -"logs`.)" +"Screenshot showing Zammad's date picker with\n" +"week numbers enabled" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:38 -msgid "API Alerts" +#: ../settings/system/frontend.rst:50 +msgid "Set to ``yes``" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:40 +#: ../settings/system/index.rst:4 msgid "" -"To add these scripts in the Checkmk WATO, copy them into your Checkmk " -"installation directory and make them executable. (Be sure to replace the " -"``zammad.example.com`` callback URL with the one found in your admin panel.)" +"For your overview we split each tab within system settings into its own page:" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:60 -msgid "Service notification" +#: ../settings/system/index.rst:16 +msgid "Console Based Settings" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:46 +#: ../settings/system/index.rst:18 msgid "" -"For updates on the status of the software running on your server (*e.g.,* " -"postgres)." +"There's some console based settings we didn't put into the UI. However, you " +"may find them helpful - you can find them in our :docs:`hidden settings ` section." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:75 -msgid "Host notification" +#: ../settings/system/network.rst:2 +msgid "Network" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:63 -msgid "For updates on the status of the server itself." +#: ../settings/system/network.rst:8 +msgid "" +"The proxy settings can only be saved after successfully testing the proxy " +"connection." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:77 -msgid "🤔 **What's with all the env vars?**" +#: ../settings/system/network.rst:15 +msgid "Proxy Address." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:79 +#: ../settings/system/network.rst:12 msgid "" -"Whenever Checkmk runs these scripts, it needs to provide some information " -"about the event that triggered the notification. This information is passed " -"in the form of these ``$NOTIFY_*`` environment variables." +"Allows you to provide a proxy server if needed. This is relevant for network " +"communication by Zammad." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:85 -msgid "" -"You can specify additional parameters to pass to the script when you're " -"setting up your notification rule, but the ones you see here are all " -"provided by default." +#: ../settings/system/network.rst:15 +msgid "It **does not** affect the update process or Elasticsearch." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:90 -msgid "Email Alerts" +#: ../settings/system/network.rst:18 +msgid "Username for proxy connection." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:94 +#: ../settings/system/network.rst:18 msgid "" -"🐞 **There are known bugs** in Zammad's processing of email from Checkmk. " -"This section will be completed once they have been resolved. (Learn more at " -"GitHub issues `#2377 `_ & " -"`#2180 `_.)" +"If your proxy server requires authentication, provide the username here." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:100 -msgid "In the meantime, we encourage you to set up API alerts instead." +#: ../settings/system/network.rst:21 +msgid "Password for proxy connection." msgstr "" -#: ../system/integrations/clearbit.rst:2 -msgid "Clearbit" +#: ../settings/system/network.rst:21 +msgid "" +"If your proxy server requires authentication, provide the password here." msgstr "" -#: ../system/integrations/clearbit.rst:4 +#: ../settings/system/network.rst:26 +msgid "No proxy for the following hosts." +msgstr "" + +#: ../settings/system/network.rst:24 msgid "" -"With our Clearbit integration, you can easily enrich the information " -"provided by Zammad. If the customers or agents email address is known to " -"Clearbit, it will share all information it has regarding the user with " -"Zammad. Those information can include the following:" +"Exception list for hosts you can't or don't want to reach via proxy server." msgstr "" -#: ../system/integrations/clearbit.rst:9 -msgid "Avatar" +#: ../settings/system/network.rst:27 +msgid "Default: ``localhost,127.0.0.0,::1``" msgstr "" -#: ../system/integrations/clearbit.rst:10 -msgid "Address information" +#: ../settings/system/services.rst:2 +msgid "Services" msgstr "" -#: ../system/integrations/clearbit.rst:11 -msgid "Website information" +#: ../settings/system/services.rst:10 +msgid "Image Service" msgstr "" -#: ../system/integrations/clearbit.rst:12 -msgid "A BIO (as Note by default)" +#: ../settings/system/services.rst:5 +msgid "Defines the backend for user and organization image lookups." msgstr "" -#: ../system/integrations/clearbit.rst:14 -msgid "" -"If needed, you can add further custom objects and add mappings to them, so " -"the Clearbit information can be filled within the database. In general you " -"can get any information from Clearbit, as long as you have a mapping to an " -"Zammad object." +#: ../settings/system/services.rst:7 +msgid "Default: ``Zammad Image Service`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:21 +#: ../settings/system/services.rst:9 msgid "" -"Clearbit does have a mapping of fields like LDAP and Exchange have, but does " -"not \"win\" against Zammad information. This means that if you have e.g. the " -"last name field filled in already and Clearbit has other information on " -"that, it will not be updated." +"Make sure your on premise installation has ``HTTPS`` access to ``images." +"zammad.com``." msgstr "" -#: ../system/integrations/clearbit.rst:26 -msgid "" -"However: If let's say the last name has been set by Clearbit and Zammad " -"notices that the last name on the Clearbit source has changed, Zammad will " -"also update this value." +#: ../settings/system/services.rst:18 +msgid "Geo Calendar Service" msgstr "" -#: ../system/integrations/clearbit.rst:33 +#: ../settings/system/services.rst:13 msgid "" -"The configuration of Clearbit is really easy and done fast! Just login to " -"your Clearbit-Account, go to \"API\" and copy the secret-API-Key." +"Defines the backend for geo calendar lookups. Used for initial calendar " +"setup." msgstr "" -#: ../system/integrations/clearbit.rst:38 -msgid "" -"Now change to your Zammad instance, go to Integrations (System) -> Clearbit " -"in the admin panel. Paste your API-Key into the API-Key-Field and decide if " -"Zammad should create unknown Organizations automatically, if the user does " -"not have one yet (and Clearbit knows it). The shared option decides if the " -"new organizations Zammad creates with Clearbit should be shared ones." +#: ../settings/system/services.rst:16 +msgid "Default: ``Zammad GeoCalendar Service`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:47 +#: ../settings/system/services.include.rst:2 msgid "" -"If you're unsure what option to choose, better stick with \"no\". You can " -"also learn more about :doc:`/manage/organizations/index`." +"Make sure your on premise installation has ``HTTPS`` access to ``geo.zammad." +"com``." msgstr "" -#: ../system/integrations/clearbit.rst:52 -msgid "" -"The Mapping option works similar to the mapping within the Exchange and LDAP " -"sync. You can add further mappings for e.g. custom fields if you need more " -"information that Clearbit can provide." +#: ../settings/system/services.rst:26 +msgid "Geo IP Service" msgstr "" -#: ../system/integrations/clearbit.rst:58 +#: ../settings/system/services.rst:21 msgid "" -"If you want to add more Clearbit fields and want to learn more about " -"available fields on their API, you can take a look at their `API " -"documentation `_." +"Defines the backend for geo IP lookups. Shows also location of an IP address " +"if an IP address is shown." msgstr "" -#: ../system/integrations/clearbit.rst:62 -msgid "" -"If you're happy with the above chosen Settings and your mapping, just save " -"the changes and enable Clearbit integration. Zammad will now start polling " -"the Clearbit API as users contact you." +#: ../settings/system/services.rst:24 +msgid "Default: ``Zammad GeoIP Service`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:68 -msgid "" -"Zammad does not synchronize with Clearbit on a regular basis, but on demand " -"if needed. This saves API calls." +#: ../settings/system/services.rst:32 +msgid "Geo Location Service" msgstr "" -#: ../system/integrations/clearbit.rst:73 +#: ../settings/system/services.rst:29 msgid "" -"Below the Settings and Mappings, you'll find our Integration log. You can " -"see what requests Zammad sent to Clearbit and also the APIs Response." +"Defines the backend for geo location lookups to store geo locations for " +"addresses." msgstr "" -#: ../system/integrations/clearbit.rst:78 +#: ../settings/system/services.rst:32 msgid "" -"By the way, you can also view the API log on the Clearbit website - the " -"information seen is basically the same." -msgstr "" - -#: ../system/integrations/clearbit.rst:84 -msgid "Example When Adding a User" +"Default: ``OpenStreetMap (ODbL 1.0, http://osm.org/copyright)`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:86 +#: ../settings/system/services.rst:36 msgid "" -"To show you how fast information is added, we added a small Screencast " -"below. This shows the creation of the User Alex from Clearbit. As we already " -"set the last name of Alex to \"X\", Zammad did not update it. What Zammad " -"did was to add further information it received from Clearbit." +"You can find a detailed privacy information on what we store for how long on " +"our :docs:`Privacy Appendix ` inside of our System " +"Documentation." msgstr "" -#: ../system/integrations/cti/generic.rst:2 -msgid "CTI (generic)" +#: ../settings/system/storage.rst:2 +msgid "Storage" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:1 +#: ../settings/system/storage.rst:6 msgid "" -"This integration enables Zammad to provide a caller log to your agents. With " -"this your agents can greet your customers by their name and are supported by " -"Zammad with automatically opening a new ticket dialog or the user profile." +"Here you can define where Zammad stores attachments for tickets and the " +"knowledge base. By default, we're writing to the ``Database`` - you can " +"switch to ``Filesystem`` or ``Simple Storage (S3)`` at any time. In this " +"case please have a look on the following instructions." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:6 +#: ../settings/system/storage.rst:11 msgid "" -"Click the toggle next to the heading to activate or deactivate this " -"integration." +"If you have a busy Zammad instance, we strongly encourage you to use " +"filesystem storage instead of \"Database\". This will greatly improve system " +"performance (de-crease database load and size)." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:9 -msgid "" -"If you want to learn more on how your agents can use this function, please " -"refer the :user-docs:`user documentation `." +#: ../settings/system/storage.rst:19 +msgid "Database" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:14 +#: ../settings/system/storage.rst:17 msgid "" -"Automatically opening new ticket dialogues or user profiles requires agent " -"to extension mapping - see more below." -msgstr "" - -#: ../system/integrations/cti/includes/introduction.include.rst:20 -msgid "Please note the following limitations to reduce confusion later on:" +"This is the default storage method. The attachments are stored directly in " +"the database. If your Zammad instance grows, we recommend one of the other " +"methods to maintain performance." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:22 -msgid "CTI integrations provide caller log functions only." +#: ../settings/system/storage.rst:38 +msgid "Filesystem" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:23 +#: ../settings/system/storage.rst:22 msgid "" -"This integration does not provide any VoIP functionalities; you can't make " -"phone calls from within Zammad." +"This storage method is recommended for all Zammad instances, especially for " +"those with a higher load. If you choose filesystem, your files are written " +"to ``/opt/zammad/storage/``." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:25 +#: ../settings/system/storage.rst:26 msgid "" -"If your browser supports ``tel``-URLs, you can click on phone numbers for " -"automatic dialing. This requires additional software / configuration on your " -"agent's computers." +"Moving attachments from \"Database\" to \"Filesystem\" can be run during " +"production use. However, you should consider your framework conditions (e.g. " +"bandwidth, system load in production) to define the right moment." msgstr "" -#: ../system/integrations/cti/generic.rst:9 -#: ../system/integrations/cti/placetel.rst:14 -#: ../system/integrations/cti/sipgate.rst:14 -msgid "Please provide the following requirements:" +#: ../settings/system/storage.rst:32 +msgid "**You noticed slow updates of Zammad?**" msgstr "" -#: ../system/integrations/cti/generic.rst:11 +#: ../settings/system/storage.rst:34 msgid "" -"A telephone system that supports webhooks (outbound) (best option are those " -"that allow customizing the calls)." +"While Zammad is beeing updated, it enforces a recursive \"change " +"owner\" (chown) for this directory. For instances with many files this can " +"be time consuming. To mitigate that you can move your files and create a " +"symlink in ``/opt/zammad/storage/`` to the new directory. Of course you have " +"to make sure on your own that the permissions are always correct." msgstr "" -#: ../system/integrations/cti/generic.rst:13 -msgid "A unique Call-ID during the call session." +#: ../settings/system/storage.rst:95 +msgid "Simple Storage (S3)" msgstr "" -#: ../system/integrations/cti/generic.rst:14 -msgid "Call event data (both numbers and direction)." +#: ../settings/system/storage.rst:41 +msgid "" +"To use the Simple Storage (S3), you have to provide some settings, which " +"can't be accessed in the UI (see instructions below)." msgstr "" -#: ../system/integrations/cti/generic.rst:15 -msgid "Your Zammad instance must be reachable for your telephony system." +#: ../settings/system/storage.rst:44 +msgid "" +"⚠️ Please note that the current implementation is in its early stages and can " +"be modified in the future." msgstr "" -#: ../system/integrations/cti/generic.rst:17 +#: ../settings/system/storage.rst:47 msgid "" -"If you want to learn more on what kind of requests are supported by Zammad " -"and what it expects, please consult our :docs:`CTI-API documentation `." +"The prerequisite is to have access to a S3-compatible storage and to have " +"all necessary parameters available (which depends on your storage provider; " +"if in doubt, please ask there for help)." msgstr "" -#: ../system/integrations/cti/generic.rst:22 -#: ../system/integrations/cti/placetel.rst:27 -#: ../system/integrations/cti/sipgate.rst:30 -msgid "Available Settings" +#: ../settings/system/storage.rst:51 +msgid "Steps to configure S3:" msgstr "" -#: ../system/integrations/cti/generic.rst:29 -#: ../system/integrations/cti/placetel.rst:41 -#: ../system/integrations/cti/sipgate.rst:40 -msgid "Endpoint Settings" +#: ../settings/system/storage.rst:53 +msgid "" +"Copy ``config/zammad/storage.yml.dist`` to ``config/zammad/storage.yml``" msgstr "" -#: ../system/integrations/cti/generic.rst:25 -msgid "" -"Zammad will list your generic CTI endpoint here. It contains a unique token " -"so ensure to keep this URL save." +#: ../settings/system/storage.rst:54 +msgid "Edit the copied file in one of the following ways:" msgstr "" -#: ../system/integrations/cti/generic.rst:28 +#: ../settings/system/storage.rst:56 msgid "" -"You'll need this endpoint for your PBX to talk to Zammad, see :docs:`CTI-API " -"documentation `." +"Either provide your S3 configuration with one attribute per line like in the " +"upper area of the file" msgstr "" -#: ../system/integrations/cti/includes/important-dont-forget-saving.include.rst:3 +#: ../settings/system/storage.rst:58 msgid "" -"All following options **do not save automatically**. Always use the Save " -"button on the lower end of the integration page!" +"Or provide your S3 configuration as an URL (which you can find at the end of " +"the file). Note: you can also provide this URL as environment variable (:" +"docs:`see system documentation `) without using this yml-file." msgstr "" -#: ../system/integrations/cti/generic.rst:43 -#: ../system/integrations/cti/placetel.rst:49 -#: ../system/integrations/cti/sipgate.rst:52 -msgid "Call Settings" +#: ../settings/system/storage.rst:62 +msgid "" +"We recommend the deletion of the not used configuration style to avoid " +"inconsistencies." msgstr "" -#: ../system/integrations/cti/generic.rst:39 -#: ../system/integrations/cti/placetel.rst:49 -#: ../system/integrations/cti/sipgate.rst:37 -#: ../system/integrations/cti/sipgate.rst:50 -msgid "Inbound" +#: ../settings/system/storage.rst:65 +msgid "Restart Zammad so the config file / environment variable is loaded" msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:1 +#: ../settings/system/storage.rst:66 msgid "" -"This option allows you to block specific incoming caller IDs. It allows you " -"to temporarily reject e.g. spam callers without having to contact providers " -"or PBX administrators." +"Set the \"Storage Method\" in Zammad to ``Simple Storage (S3)`` in Settings " +"> System > Storage and click on \"Submit\". After that, Zammad checks your " +"configuration and the connection to the service and will raise an error " +"message if something is wrong." msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:11 -msgid "Caller ID to block" +#: ../settings/system/storage.rst:72 +msgid "A very simple storage configuration could look like this:" msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 -msgid "Provide caller IDs to block in ``E.164`` format." +#: ../settings/system/storage.rst:85 +msgid "" +"Before setting the storage method to ``Simple Storage (S3)`` (step 4), " +"please make sure to have a working setup." msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:8 +#: ../settings/system/storage.rst:88 msgid "" -"Your telephony system has to support this function. Zammad will send a " -"``reject`` response which will cause your telephony system to hang up the " -"call. To callers this usually will feel like the line is busy." +"You can verify this by running ``rails r 'Rails.logger = Logger.new(STDOUT); " +"pp Store::Provider::S3.ping?'`` in your Zammad directory. If everything is " +"fine, you should see ``true``, else you should see ``false`` and a simple " +"error message." msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:14 +#: ../settings/system/storage.rst:93 msgid "" -"Provide a meaningful note for your fellow administrators to remind yourself " -"why you've chosen to block the number." +"If you installed Zammad through a package manager (rather than from source), " +"replace ``rails r`` with ``zammad run rails r`` above. To learn more, see :" +"docs:`Administration via Console `." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 -#: ../system/integrations/cti/includes/outbound-calls.include.rst:17 -#: ../system/integrations/cti/sipgate.rst:40 -msgid "Outbound" +#: ../settings/ticket.rst:4 +msgid "" +"Here you can adjust general ticket settings. Additional ones for the ticket " +"composer interface can be found in the :doc:`/misc/composer`." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:1 -msgid "" -"In many cases you may want to use a different caller ID depending on the " -"destination you're calling. This may apply due to specific connection rates " -"to other countries or because you want your customer to feel you're calling " -"from the same country." +#: ../settings/ticket.rst:11 +msgid "Ticket Hook (default: ``Ticket#``)" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:6 -msgid "This option expects ``E.164`` number formats." +#: ../settings/ticket.rst:11 +msgid "The identifier for a ticket; *e.g.,* Ticket#, Call#, MyTicket#." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 -msgid "Destination caller ID" +#: ../settings/ticket.rst:38 +msgid "Ticket Hook Position (default: ``right``)" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:5 -msgid "The caller ID or number you're trying to call." +#: ../settings/ticket.rst:14 +msgid "" +"With this setting you can decide (if) where to insert the ticket number." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:7 -msgid "You can use wildcards for e.g. country specific outbound numbers like:" +#: ../settings/ticket.rst:20 +msgid "*Right*" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:9 -msgid "``49*`` for Germany" +#: ../settings/ticket.rst:17 +msgid "" +"This setting will add the ticket reference on the right site of the subject." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:10 -msgid "``4930*`` for Berlin / Germany landlines" +#: ../settings/ticket.rst:20 +msgid "Example: ``Some Subject [Ticket#12345]``" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 -msgid "``33*`` for France" +#: ../settings/ticket.rst:26 +msgid "*Left*" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:15 -msgid "Set Outbound caller ID" +#: ../settings/ticket.rst:23 +msgid "" +"This setting will add the ticket reference on the left site of the subject." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:14 -msgid "" -"The outbound caller ID to set (the number your customer sees on his display) " -"in ``E.164`` number format." +#: ../settings/ticket.rst:26 +msgid "Example: ``[Ticket#12345] Some Subject``" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 -msgid "Provide a short description for fellow administrators." +#: ../settings/ticket.rst:29 +msgid "*None*" msgstr "" -#: ../system/integrations/cti/includes/generic-cti-support-note.includes.rst:3 -msgid "" -"This option requires your PBX to send a specific request to Zammad *before " -"dialing*. Please consult the :docs:`CTI API ` in case " -"you're not sure." +#: ../settings/ticket.rst:29 +msgid "This will completely remove ticket references from the subject." msgstr "" -#: ../system/integrations/cti/generic.rst:52 -#: ../system/integrations/cti/placetel.rst:54 -#: ../system/integrations/cti/sipgate.rst:59 -msgid "Other Settings" +#: ../settings/ticket.rst:33 +msgid "" +"Please ensure to take a look at :doc:`/channels/email/settings` within the " +"email channel to ensure you have at least one reference that helps Zammad to " +"assign follow-ups correctly." msgstr "" -#: ../system/integrations/cti/includes/other-settings-intro.include.rst:1 +#: ../settings/ticket.rst:37 msgid "" -"Below you can find all available additional settings for this CTI " -"integration. For your overview we're sorting them by appearance and " -"reference their description first." +"Disabling this and not setting up any further follow up search will lead to " +"unexpected results!" msgstr "" -#: ../system/integrations/cti/includes/default-caller-id.include.rst:2 -#: ../system/integrations/cti/includes/default-caller-id.include.rst:1 -msgid "Default caller ID for outbound calls" +#: ../settings/ticket.rst:65 +msgid "" +"Ticket Last Contact Behaviour (default: ``Use the start time of the last " +"customer thread (which may consist of multiple articles).``)" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:16 -#: ../system/integrations/cti/includes/records-caller-log.include.rst:15 -msgid "Shown records in caller log" +#: ../settings/ticket.rst:41 +msgid "" +"This setting changes the way Zammad updates the ``Last Contact`` value of a " +"ticket. This is fairly important for overviews and what you expect upon " +"ticket updates of a customer." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:2 +#: ../settings/ticket.rst:52 msgid "" -"Allows you to set the number of shown caller log entries for all users. You " -"can choose from the following values:" +"Use the start time of the last customer thread (which may consist of " +"multiple articles)." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:5 -msgid "60 (default)" +#: ../settings/ticket.rst:46 +msgid "" +"If this option is chosen, Zammad will update the last updated value just " +"once if a customer replies. After that, Zammad will wait for an agent to " +"react." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:6 -msgid "120" +#: ../settings/ticket.rst:50 +msgid "" +"This comes in handy if you want to work tickets in the order of their first " +"update. This will not change ticket orders if customers decide to \"bump\" " +"the ticket affected." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:7 -msgid "180" +#: ../settings/ticket.rst:57 +msgid "Use the time of the very last customer article." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:8 -msgid "240" +#: ../settings/ticket.rst:55 +msgid "" +"When setting this option, Zammad will always update the last updated value. " +"This means that if ordering by ``Last Update``, ticket orders will change if " +"customers \"bump\" the ticket." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:9 -msgid "300" +#: ../settings/ticket.rst:64 +msgid "Last contact value used on :doc:`/manage/overviews`" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:11 -msgid "**🥵 Potential performance issue**" +#: ../settings/ticket.rst:65 +msgid "Last contact value used on :doc:`/manage/trigger`" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:13 +#: ../settings/ticket.rst:88 msgid "" -"Setting this setting higher than 60 may cause serious performance issues on " -"very busy instances. Keep in mind that this setting causes Zammad to poll " -"and send up to 300 records to *all active agent sessions* in very short time " -"periods." +"Ticket Organization Reassignment (default: ``Update the most recent tickets." +"``)" msgstr "" -#: ../system/integrations/cti/generic.rst:73 -msgid "Caller Log Filter" +#: ../settings/ticket.rst:68 +msgid "" +"This setting changes the way Zammad updates the organization field of the " +"tickets whenever the primary organization of a user is changed." msgstr "" -#: ../system/integrations/cti/generic.rst:55 -msgid "" -"This function allows you to provide call information based on e.g. queues " -"only to agents that really need the information." +#: ../settings/ticket.rst:74 +msgid "Update the most recent tickets." msgstr "" -#: ../system/integrations/cti/generic.rst:58 +#: ../settings/ticket.rst:72 msgid "" -"Why? If you have a team for several countries or departments, you don't want " -"to bug your agents from other departments. Leaving these options empty will " -"fallback to showing everything to everyone." +"If this option is chosen, Zammad will update the 100 most recent tickets " +"where the user is the ticket customer. The ticket organization field will be " +"automatically set to the new primary organization of the user." msgstr "" -#: ../system/integrations/cti/generic.rst:64 -msgid "Destination caller ID or Queue" +#: ../settings/ticket.rst:88 +msgid "Do not update any tickets." msgstr "" -#: ../system/integrations/cti/generic.rst:63 +#: ../settings/ticket.rst:77 msgid "" -"This depends on your PBX and usually is either a queue ID, phone number or " -"extension." +"When choosing this option, Zammad will not update any tickets when the " +"user's primary organization is changed." msgstr "" -#: ../system/integrations/cti/generic.rst:69 -msgid "Agents" +#: ../settings/ticket.rst:80 +msgid "**Use with care!**" msgstr "" -#: ../system/integrations/cti/generic.rst:67 +#: ../settings/ticket.rst:82 msgid "" -"Select the agents that are responsible for the group. These agents will then " -"see caller log entries and call notifications fitting to said queue." +"Using this option may lead to inconsistencies in the system as the ticket " +"organization may become decoupled from the ticket customer." msgstr "" -#: ../system/integrations/cti/generic.rst:0 +#: ../settings/ticket.rst:85 msgid "" -"Screenshot showing the caller log filter table with pre filled sample data" +"However, you may use this option if you wish to maintain :ref:`the shared " +"access ` to the ticket for all organization " +"members of the original organization of the customer." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:6 -msgid "" -"With recent logs Zammad allows you to view the latest calls for the CTI " -"functionality. This usually comes in handy, when you're looking for errors." +#: ../settings/ticket.rst:110 +msgid "Ticket Number Format (default: ``Increment (SystemID.Counter)``)" msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:0 +#: ../settings/ticket.rst:94 msgid "" -"Screenshot showing several incoming requests within Recent logs section." +"This setting defines the way Zammad's ticket number will look. Changing this " +"setting in production will cause follow up detection to fail." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:16 -msgid "I'm just here to clear floats up." +#: ../settings/ticket.rst:102 +msgid "Increment (SystemID.Counter)" msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:20 +#: ../settings/ticket.rst:98 msgid "" -"By clicking on the entry of interest, Zammad will provide more details on " -"the call in question. You'll see the payload it received and also the " -"response that was sent." +"The increment value contains the SystemID (automatically generated during " +"installation) and a increment which counts up with every new Ticket. The " +"increment will automatically get another digit if needed." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:0 -msgid "" -"Screenshot showing detailed information of a specific log entry of recent " -"logs" +#: ../settings/ticket.rst:102 +msgid "Examples: ``1010138``, ``1010139``" msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:31 -msgid "x" +#: ../settings/ticket.rst:110 +msgid "Date (Year.Month.Day.SystemID.Counter)" msgstr "" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 -#: ../system/integrations/cti/includes/troubleshooting.include.rst:9 -msgid "My Phone page stays blank, signalling does work..." +#: ../settings/ticket.rst:105 +msgid "" +"This version of the ticket number is fairly long. However, because it " +"contains the date of ticket creation, it also allows you to see when the " +"ticket has been created. You may feel familiar with this number format if " +"you've worked with OTRS already." msgstr "" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:5 -msgid "" -"If you've made sure that signalling works (check Recent logs) and your " -"Caller Log still stays empty, please ensure that you only configured one CTI " -"integration version. Specifically defining more than one agent mapping on " -"the different integration variants will be the issue." +#: ../settings/ticket.rst:110 +msgid "Examples: ``201206231010138``, ``201206231010139``" msgstr "" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 -msgid "Clear the not needed agent mapping and reload your browser page." +#: ../settings/ticket.rst:137 +msgid "OPTIONS" msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:1 +#: ../settings/ticket.rst:113 msgid "" -"By mapping your agents extension to their existing Zammad users, Zammad can " -"provide a new ticket dialog or open the user profile for the agent that " -"picks up the call." +"The below options allow you to further customize your ticket number. The " +"availability of options differ depending of the chosen ticket number format " +"above." msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:5 -msgid "" -"This speeds up ticket aiding, no matter if it's for existing tickets or new " -"ones!" +#: ../settings/ticket.rst:122 +msgid "Checksum (default: ``no``)" msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:8 +#: ../settings/ticket.rst:118 msgid "" -"To see it work from the agent's perspective, have a look on :user-docs:`user " -"documentation `." +"If set to yes, we'll built a checksum to further \"unique\" the ticket " +"number of your system. If you're dealing with many other ticket systems this " +"might help to prevent false positive follow up detection on tickets." msgstr "" -#: ../system/integrations/cti/placetel.rst:2 -msgid "Placetel CTI" +#: ../settings/ticket.rst:122 +msgid "This will also add another digit to the ticket number." msgstr "" -#: ../system/integrations/cti/placetel.rst:16 -msgid "You need an administrative Placetel account for your organization." +#: ../settings/ticket.rst:137 +msgid "Min. size of Number (default: ``5``)" msgstr "" -#: ../system/integrations/cti/placetel.rst:17 -#: ../system/integrations/cti/sipgate.rst:20 +#: ../settings/ticket.rst:125 msgid "" -"Your Zammad instance must be allowed to communicate to external services." +"This setting defines the minimum length of your ticket number. If your " +"counter is not yet high enough, Zammad will fill the number with zeros to " +"ensure the wanted length." msgstr "" -#: ../system/integrations/cti/placetel.rst:18 -msgid "Placetel must be able to reach your Zammad instance." -msgstr "" - -#: ../system/integrations/cti/placetel.rst:22 -msgid ":doc:`provider-configurations/placetel`" -msgstr "" - -#: ../system/integrations/cti/placetel.rst:21 +#: ../settings/ticket.rst:129 msgid "" -"Learn how to configure Placetel to enable Zammad and Placetel to communicate " -"with each other." +"Please note that the minimum length is ``3`` (SystemID + at least one digit " +"if below 10). Also, if the length is no longer long enough, the number will " +"automatically get one digit longer. Ticket-Numbers **do not overflow**, thus " +"it's save to keep it at 5 or set it lower if wanted." msgstr "" -#: ../system/integrations/cti/placetel.rst:32 +#: ../settings/ticket.rst:135 msgid "" -"The here listed endpoint settings are relevant for the :doc:`integration " -"configuration with Placetel `." +"This option is only available if ticket number format is set to " +"``Increment``!" msgstr "" -#: ../system/integrations/cti/placetel.rst:37 -#: ../system/integrations/i-doit.rst:53 -msgid "Endpoint" +#: ../settings/ticket.rst:142 +msgid "Auto-Assignment" msgstr "" -#: ../system/integrations/cti/placetel.rst:36 +#: ../settings/ticket.rst:144 msgid "" -"This endpoint will be required for the Zammad integration within the " -"Placetel web interface." -msgstr "" - -#: ../system/integrations/cti/placetel.rst:41 -msgid "API Token" +"In a larger Zammad environment, it happens that several agents open the same " +"ticket at the same time. Although collision detection is then effective, the " +"efficiency of processing can be increased by means of the automatic " +"assignment of tickets when a ticket is opened." msgstr "" -#: ../system/integrations/cti/placetel.rst:40 +#: ../settings/ticket.rst:149 msgid "" -"You'll receive this token within the ``Web API`` menu. Make sure to copy " -"this value, it's only shown once!" -msgstr "" - -#: ../system/integrations/cti/placetel.rst:71 -#: ../system/integrations/cti/sipgate.rst:77 -msgid "Phone Extension to Agent Mapping" +"The automatic assignment of tickets can be activated and configured in the " +"admin area under Settings > Ticket > Auto Assignment." msgstr "" -#: ../system/integrations/cti/placetel.rst:0 -msgid "Screenshot showing sample user mappings in between Placetel and Zammad" +#: ../settings/ticket.rst:152 +msgid "" +"The auto assignment only works if the ticket has no owner yet. By default, " +"the agent can always reset the ticket owner to ``-`` if needed." msgstr "" -#: ../system/integrations/cti/placetel.rst:64 +#: ../settings/ticket.rst:155 msgid "" -"You can find your agents Placetel username combination required within ⚙️ PBX " -"→ VoIP destinations. Within the \"Advanced settings\" section you're looking " -"for \"SIP user name\" and \"SIP server\"." +"If you want to use this function for only specific tickets, you can " +"configure the conditions accordingly to meet your requirement. By default " +"the condition affects all tickets with the state ``open``." msgstr "" -#: ../system/integrations/cti/placetel.rst:68 -msgid "Combine these two like so: ``@``." +#: ../settings/ticket.rst:161 +msgid "" +"If you need to exclude users (e.g. a group leader), you can search and " +"select the desired agents in the ``Exception Users`` list. The search " +"function in this area is only effective, if you have too many agents to " +"display at once to help you with the configuration." msgstr "" -#: ../system/integrations/cti/placetel.rst:0 -msgid "Sample VoIP credentials for a Placetel user" +#: ../settings/ticket.rst:167 +msgid "Notifications" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:2 -msgid "Setup Placetel connection for Zammad" +#: ../settings/ticket.rst:191 +msgid "Default Notifications" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:6 +#: ../settings/ticket.rst:170 msgid "" -"This configuration step requires a *full* administrative Placetel account. " -"You may receive forbidden error messages with Placetel in case your " -"permissions are not high enough." +"This setting allows you to configure the default ticket notifications that " +"will be applied to all new agent users (incl. users who were just assigned " +"agent role). Simply change the notification matrix to desired state and " +"press **Save**." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:10 +#: ../settings/ticket.rst:175 msgid "" -"The following actions can be configured via the `Placetel web interface " -"`_." -msgstr "" - -#: ../system/integrations/cti/provider-configurations/placetel.rst:29 -msgid "Step 1: Activate Zammad integration" +"In case an agent already exists, their ticket notification preferences will " +"be preserved. Optionally, you can also **Apply current defaults to all " +"agents**." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:14 +#: ../settings/ticket.rst:181 msgid "" -"Within Integrations, scroll down to Partner integrations and select Zammad." +"**Potential time-consuming action:** Applying default ticket notifications " +"to all agent users may take some time to complete, be patient! The exact " +"time will depend on the size of your system and the number of agents." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:17 +#: ../settings/ticket.rst:185 msgid "" -"You can alternatively filter by \"Ticket Systems\" to reduce the number of " -"entries on the page. You'll still want to look for Partner integrations. 🤓" +"**Active agents only!** When current default ticket notifications are " +"applied, only active agent users are considered. In case an agent is re-" +"activated *after* this action, they will still have the old notification " +"configuration." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:21 +#: ../settings/ticket.rst:190 msgid "" -"Within the Zammad integration now press \"Activate\". A new tab ``API`` " -"becomes available - open this tab." +"In case you want to go back to the initial state of ticket notifications, " +"you can click on **Reset to default** button." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:24 -msgid "" -"Now tick \"Enable Call Control / Notify API\" and paste the Placetel " -"endpoint from your Zammad instance into the field \"URL of your API " -"endpoint\". Save to apply the settings" +#: ../settings/ticket.rst:196 +msgid "Duplicate Detection" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 -msgid "Screencast showing how to activate the Zammad integration" +#: ../settings/ticket.rst:238 +msgid "Detect Duplicate Ticket Creation" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:51 -msgid "Step 2: Generate API Token for Placetel" +#: ../settings/ticket.rst:199 +msgid "" +"This setting turns on the duplicate ticket detection mechanism during ticket " +"creation. If similar tickets are found in the system, a suitable warning " +"will be shown to the user trying to create a ticket." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:32 -msgid "" -"Go back to the integrations page and scroll down to \"Web API\". Generate a " -"new API token by using the \"Create a new API token\" button." +#: ../settings/ticket.rst:206 +msgid "A Sample Duplicate Ticket Warning" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:37 +#: ../settings/ticket.rst:208 msgid "" -"If you already generated a token either use your existing token or reset it " -"by using above mentioned button. Placetel will ask you to conform this reset." +"You can choose which ticket attributes will be matched by selecting them in " +"**Attributes to compare** field. Only if the ticket attribute value provided " +"by the user in the ticket create form is *equal* with the attribute in an " +"existing ticket, the warning will be shown." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:41 -msgid "" -"Please keep in mind that existing API scripts may no longer work due to " -"token resets!" +#: ../settings/ticket.rst:213 +msgid "**Warning title** and **Warning message** are configurable as well." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:44 +#: ../settings/ticket.rst:215 msgid "" -"Copy the provided API token and insert it into the \"API Token\" field " -"within Zammad's Placetel integration." +"You can limit the detection only to certain user roles. By default, only " +"agents will see the warning." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:47 +#: ../settings/ticket.rst:218 msgid "" -"Apply your changes by using the \"Save\" button on the bottom of the " -"Placetel integration page and activate the Placetel integration." +"If you don't want to show the matched tickets as part of the warning, you " +"can set **Show matching ticket(s) in the warning** setting to *no*." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +#: ../settings/ticket.rst:221 msgid "" -"Screencast showing how to retrieve an API token from Placetel for Zammad" +"By default, **Permission level for looking up ticket** is set to *User*, " +"which means user permissions will be honored during sarch. The user will " +"see the warning only if tickets they have access to are matched. " +"Alternatively, you can set this setting to *System*, in which case the " +"search will happen within *all* tickets in the system, regardless of user " +"permissions." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:73 -#: ../system/integrations/cti/provider-configurations/sipgate.rst:77 -msgid "Step 3: Restrict the numbers to notify on" +#: ../settings/ticket.rst:227 +msgid "**🦺 Safety first!**" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:54 +#: ../settings/ticket.rst:229 msgid "" -"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " -"the the Integrations page of the Placetel web interface, go to \"Notify " -"API\"." +"Even if the permission level is set to *System*, the user will not be shown " +"the tickets they don't have access to in the warning, even if they match." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:58 +#: ../settings/ticket.rst:233 msgid "" -"Lower on the page Placetel allows you to restrict the numbers to notify on. " -"You'll find this within the \"External routing API\" part." +"However, just the confirmation about the existence of the tickets in the " +"system may be considered an unwanted information disclosure. Use this option " +"carefully!" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +#: ../settings/ticket.rst:237 msgid "" -"Screenshot showing a sample selection of phone numbers to use for the " -"Placetels notify API" +"Finally, you can configure between matching within **All tickets** or **Open " +"tickets** only by setting **Match tickets in following states**. Depending " +"on the current ticket state, a ticket may or not be matched." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:66 -msgid "" -"This menu point also provides a API request log from Placetel view. Just " -"open \"Recent responses of your API endpoint\" to learn more." +#: ../system/core-workflows.rst:2 +msgid "Core Workflows" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:69 +#: ../system/core-workflows.rst:4 msgid "" -"If you want to see Zammad's perspective, use the \"Recent Logs\" part from " -"within the Placetel integration page." +"Core Workflows allow you to adjust object attributes in many ways. For " +"example:" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 -msgid "Screenshot showing sample log entries for Placetels API calls to Zammad" +#: ../system/core-workflows.rst:7 +msgid "show / hide fields" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:77 -msgid "Step 4 (optional): Further configurations for Placetel" +#: ../system/core-workflows.rst:8 +msgid "adjust mandatory setting" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:76 +#: ../system/core-workflows.rst:9 +msgid "manipulate available options" +msgstr "" + +#: ../system/core-workflows.rst:11 msgid "" -"If needed, you can now configure Zammad's Placetel integration in more " -"detail. You can learn more about your options here: :ref:`Placetel " -"integration settings `." +"With this, you can provide exactly the information your users really need!" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:2 -msgid "Setup Sipgate connection for Zammad" +#: ../system/core-workflows.rst:15 +msgid "" +"If the pre-defined :doc:`/system/objects` are not enough, please add them " +"beforehand." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +#: ../system/core-workflows.rst:17 msgid "" -"Sipgate has no english web interface which is why this documentation page is " -"mixing up languages badly." +"If you experience slow or unreliable field updates, please see :ref:`Core " +"Workflow Ajax Modus `" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +#: ../system/core-workflows.rst:22 msgid "" -"Please also note that the availability of API addons highly depends on your " -"package trier. Usage of sipgate.io packages *is not free*, please check " -"their `pricing page `_ before!" +"This is a very enhanced functionality and can cause unexpected UI behavior. " +"Please ensure to test your use cases after configuration to reduce surprises." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:35 -msgid "Step 1: Book sipgate.io package" +#: ../system/core-workflows.rst:None +msgid "Dialogue for adding a new workflow" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:13 -msgid "Skip to step 2 if you already have the package booked!" +#: ../system/core-workflows/condition-operators.rst:2 +msgid "Core Workflow Condition Operators" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:15 +#: ../system/core-workflows/condition-operators.rst:4 msgid "" -"Login to an administrative Sipgate account and navigate to " -"``Accountverwaltung``. You'll see several different options depending on " -"your booked packages. Select ``Verträge & Produkte`` to continue." +"You might know that there is a separate section for explaining :doc:" +"`condition operators `. Head over there to " +"see a detailed explanation of many conditions and operators." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:19 +#: ../system/core-workflows/condition-operators.rst:8 msgid "" -"Scroll down to the section ``Zusätzliche Produkte buchen`` and look for " -"``sipgate.io`` - select this product by using the ``Produkte anzeigen``-" -"Button." -msgstr "" - -#: ../system/integrations/cti/provider-configurations/sipgate.rst:23 -msgid "" -"On the next page select either one of the ``sipgate.io`` packages or ``Push-" -"API Package Free``. Follow the dialogue by booking the addon. You'll be " -"returned to your contract overview and now should see the selected addon in " -"your list." +"Due to differences to other places in Zammad which are also using conditions " +"(e.g. triggers), you can find a dedicated description of operators for core " +"workflows below." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:30 +#: ../system/core-workflows/condition-operators.rst:12 msgid "" -"The availability for ``sipgate.io`` packages and their levels highly depends " -"on the overall account type and product you've booked with Sipgate." +"Be aware that the availability of the operators depends on the selected " +"attribute and its field type. Some of the operators may only be available " +"for system attributes (e.g. for \"tags\", \"active\")." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screencast showing the process on how to book the required sipgate.io addon" +#: ../system/core-workflows/condition-operators.rst:20 +msgid "Operator" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:52 -msgid "Step 2: Configure webhook for Zammad" +#: ../system/core-workflows/condition-operators.rst:22 +msgid "after (absolute)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:38 -msgid "" -"Within your ``Accountverwaltung`` navicate to your product ``sipgate.io``. " -"In the newly opened tab, switch from \"Clients\" to \"Webhooks\" and paste " -"the endpoint URLs from your Zammad instance like so:" +#: ../system/core-workflows/condition-operators.rst:23 +msgid "Matches if a date/time is after a specific point in time." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:42 -msgid "Inbound endpoint to \"Incoming\"" +#: ../system/core-workflows/condition-operators.rst:24 +msgid "after (relative)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:43 -msgid "Outbound endpoint to \"Outgoing\"" +#: ../system/core-workflows/condition-operators.rst:25 +msgid "Matches if a time span after a specified event has passed." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:47 -msgid "" -"Ensure to select at least one call group or phoneline within \"Sources\". " -"Other wise Sipgate will not indicate any incoming or outgoing calls to " -"Zammad." +#: ../system/core-workflows/condition-operators.rst:26 +msgid "before (absolute)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screencast showing how to add Zammad's endpoint URLs to sipgate.ios webhook " -"configuration" +#: ../system/core-workflows/condition-operators.rst:27 +msgid "Matches if a date/time is before a specific point in time." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:55 -msgid "" -"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " -"the Webhooks → URLs section of Sipgate you can select which *sources* " -"Sipgate should notify Zammad about in- and outgoing calls." +#: ../system/core-workflows/condition-operators.rst:28 +msgid "before (relative)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:59 -msgid "" -"Use either specific phone lines or use the option \"Use for all phonelines " -"and groups\" to notify Zammad about all existing lines of your Sipgate " -"account." +#: ../system/core-workflows/condition-operators.rst:29 +msgid "Matches if a time span after a specified event has not passed." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screenshot showing a sample selection of phone numbers to use for the " -"Sipgates webhooks API" +#: ../system/core-workflows/condition-operators.rst:30 +msgid "contains" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:68 -msgid "This section also allows you to enable a Debug log." +#: ../system/core-workflows/condition-operators.rst:31 +msgid "Matches if a specified value is present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "Screenshot showing an enabled Debug log option" +#: ../system/core-workflows/condition-operators.rst:33 +msgid "Matches if all of the specified values are present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:73 -msgid "" -"After enabling you can use the Debug log section to see all sent webhook " -"calls to Zammad. You'll also can see the response." +#: ../system/core-workflows/condition-operators.rst:35 +msgid "Matches if none of the specified values are present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screenshot showing sample log entries for Sipgates webhook calls to Zammad" +#: ../system/core-workflows/condition-operators.rst:36 +msgid "contains not" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:81 -msgid "Step 4 (optional): Further configurations for Sipgate" +#: ../system/core-workflows/condition-operators.rst:37 +msgid "Matches if a specified value is not present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:80 -msgid "" -"If needed, you can now configure Zammad's Sipgate integration in more " -"detail. You can learn more about your options here: :ref:`Sipgate " -"integration settings `." +#: ../system/core-workflows/condition-operators.rst:39 +msgid "Matches if one specified value is present." msgstr "" -#: ../system/integrations/cti/sipgate.rst:2 -msgid "Sipgate (sipgate.io)" +#: ../system/core-workflows/condition-operators.rst:41 +msgid "Matches if one specified value is not present." msgstr "" -#: ../system/integrations/cti/sipgate.rst:16 -msgid "You need an administrative Sipgate account for your organization." +#: ../system/core-workflows/condition-operators.rst:42 +msgid "does not match regex" msgstr "" -#: ../system/integrations/cti/sipgate.rst:17 -msgid "" -"Zammad requires a ``sipgate.io`` addon from the feature store (please note " -"that API calls are not free with Sipgate. Rates may apply and differ from " -"account to account)." +#: ../system/core-workflows/condition-operators.rst:43 +msgid "Matches if content doesn't fit to regex rule." msgstr "" -#: ../system/integrations/cti/sipgate.rst:21 -msgid "Sipgate must be able to reach your Zammad instance." +#: ../system/core-workflows/condition-operators.rst:44 +msgid "ends with" msgstr "" -#: ../system/integrations/cti/sipgate.rst:25 -msgid ":doc:`provider-configurations/sipgate`" +#: ../system/core-workflows/condition-operators.rst:45 +msgid "Matches if content ends with specified value." msgstr "" -#: ../system/integrations/cti/sipgate.rst:24 -msgid "" -"Learn how to configure Sipgate to enable Zammad and Sipgate to communicate " -"with each other." +#: ../system/core-workflows/condition-operators.rst:46 +msgid "ends with one of" msgstr "" -#: ../system/integrations/cti/sipgate.rst:33 -msgid "" -"Below endpoint settings affect the :doc:`sipgate.io configuration `." +#: ../system/core-workflows/condition-operators.rst:47 +msgid "Matches if content ends with one of the specified values." msgstr "" -#: ../system/integrations/cti/sipgate.rst:37 -msgid "This endpoint is required for incoming call hooks." +#: ../system/core-workflows/condition-operators.rst:48 +msgid "from (relative)" msgstr "" -#: ../system/integrations/cti/sipgate.rst:40 -msgid "This endpoint is required for outgoing call hooks." +#: ../system/core-workflows/condition-operators.rst:49 +msgid "Matches if date/time is after a period of time after an event." msgstr "" -#: ../system/integrations/cti/sipgate.rst:0 -msgid "Screenshot showing sample user mappings in between Sipgate and Zammad" +#: ../system/core-workflows/condition-operators.rst:51 +msgid "Matches if content is equal to a specified value." msgstr "" -#: ../system/integrations/cti/sipgate.rst:69 -msgid "" -"You can find your agent's Sipgate username within ``Accountverwaltung → " -"Benutzer``. You're looking for the SIP-ID." +#: ../system/core-workflows/condition-operators.rst:52 +msgid "is any of" msgstr "" -#: ../system/integrations/cti/sipgate.rst:0 -msgid "Sample VoIP credentials for a Sipgate user" +#: ../system/core-workflows/condition-operators.rst:53 +msgid "Matches if content is equal to any of specified values." msgstr "" -#: ../system/integrations/cti/sipgate.rst:77 -msgid "Users with several devices also have several SIP-IDs." +#: ../system/core-workflows/condition-operators.rst:54 +msgid "is modified" msgstr "" -#: ../system/integrations/elasticsearch.rst:2 -msgid "Elasticsearch (SaaS)" +#: ../system/core-workflows/condition-operators.rst:55 +msgid "Matches if content is modified." msgstr "" -#: ../system/integrations/elasticsearch.rst:4 -msgid "" -"The Elasticsearch integration allows you to create a read-only user to use " -"with your favorite reporting tool (e.g. like Grafana)." +#: ../system/core-workflows/condition-operators.rst:57 +#: ../system/core-workflows/condition-operators.rst:61 +msgid "True from the moment of changing content until form submit." msgstr "" -#: ../system/integrations/elasticsearch.rst:7 -msgid "" -"If you want to take full advantage of the Zammad reporting, have a look at " -"our :docs:`Grafana ` " -"setup page as well." +#: ../system/core-workflows/condition-operators.rst:58 +msgid "is modified to" msgstr "" -#: ../system/integrations/elasticsearch.rst:11 -#: ../system/subscription/index.rst:7 -msgid "**🚧 Hosted environment specific 🚧**" +#: ../system/core-workflows/condition-operators.rst:59 +msgid "Matches if content is modified to a specific value." msgstr "" -#: ../system/integrations/elasticsearch.rst:13 -msgid "" -"This integration is only available for Hosted setups. In order to use " -"Elasticsearch you'll need the **Plus** subscription." +#: ../system/core-workflows/condition-operators.rst:62 +msgid "is none of" msgstr "" -#: ../system/integrations/elasticsearch.rst:16 -msgid "" -"Self hosted users have all the control over their self hosted Elasticsearch " -"instances." +#: ../system/core-workflows/condition-operators.rst:63 +msgid "Matches if content is none of any specified values." msgstr "" -#: ../system/integrations/elasticsearch.rst:None -msgid "Elasticsearch integration page on SaaS environments" +#: ../system/core-workflows/condition-operators.rst:65 +msgid "Matches if content is not equal to a specified value." msgstr "" -#: ../system/integrations/elasticsearch.rst:27 -msgid "" -"Please note the following limitations of Elasticsearch access on hosted " -"environments:" +#: ../system/core-workflows/condition-operators.rst:67 +msgid "Matches if content is present." msgstr "" -#: ../system/integrations/elasticsearch.rst:30 -msgid "access to the Elasticsearch index is read-only access" +#: ../system/core-workflows/condition-operators.rst:68 +msgid "just changed" msgstr "" -#: ../system/integrations/elasticsearch.rst:31 -msgid "currently you're limited to user only" +#: ../system/core-workflows/condition-operators.rst:69 +msgid "Matches if content has changed." msgstr "" -#: ../system/integrations/elasticsearch.rst:32 +#: ../system/core-workflows/condition-operators.rst:71 +#: ../system/core-workflows/condition-operators.rst:75 msgid "" -"Reporting tools that require to write into the indexes (like Kibana) are not " -"supported" +"Only true for the moment of changing content until next form field action/" +"click." msgstr "" -#: ../system/integrations/elasticsearch.rst:34 -msgid "IP access restriction is currently not yet supported" +#: ../system/core-workflows/condition-operators.rst:72 +msgid "just changed to" msgstr "" -#: ../system/integrations/elasticsearch.rst:37 -msgid "Activating Elasticsearch Access" +#: ../system/core-workflows/condition-operators.rst:73 +msgid "Matches if content has changed to a specified value." msgstr "" -#: ../system/integrations/elasticsearch.rst:39 -msgid "" -"By default external access to your Elasticsearch index is not active. You " -"can enable the integration at any time if needed." +#: ../system/core-workflows/condition-operators.rst:76 +msgid "matches regex" msgstr "" -#: ../system/integrations/elasticsearch.rst:42 -msgid "" -"Please ensure to note down the password provided - you won't have access to " -"it afterwards." +#: ../system/core-workflows/condition-operators.rst:77 +msgid "Matches if value fits to regex rule." msgstr "" -#: ../system/integrations/elasticsearch.rst:None -msgid "Screencast showing activation of Elasticsearch integration" +#: ../system/core-workflows/condition-operators.rst:79 +msgid "Matches if no content is present." msgstr "" -#: ../system/integrations/elasticsearch.rst:51 -msgid "Connection Settings" +#: ../system/core-workflows/condition-operators.rst:80 +msgid "starts with" msgstr "" -#: ../system/integrations/elasticsearch.rst:53 -msgid "" -"This section holds the most important general information for accessing your " -"Elasticsearch indexes - such as:" -msgstr "" - -#: ../system/integrations/elasticsearch.rst:57 -msgid "A unique subdomain that does not tell your real instance URL." +#: ../system/core-workflows/condition-operators.rst:81 +msgid "Matches if content starts with specified value." msgstr "" -#: ../system/integrations/elasticsearch.rst:61 -msgid "Software" +#: ../system/core-workflows/condition-operators.rst:82 +msgid "starts with one of" msgstr "" -#: ../system/integrations/elasticsearch.rst:60 -msgid "" -"The major version of the search index being used. This is required by some " -"Reporting tools like Grafana." +#: ../system/core-workflows/condition-operators.rst:83 +msgid "Matches if content starts with one of the specified values." msgstr "" -#: ../system/integrations/elasticsearch.rst:64 -msgid "Authentication" +#: ../system/core-workflows/condition-operators.rst:84 +msgid "till (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:64 -msgid "The authentication type being supported. ``Basic Authentication``" +#: ../system/core-workflows/condition-operators.rst:85 +msgid "Matches if date/time is before a period of time before an event." msgstr "" -#: ../system/integrations/elasticsearch.rst:67 -msgid "Available Indexes" +#: ../system/core-workflows/condition-operators.rst:86 +msgid "today" msgstr "" -#: ../system/integrations/elasticsearch.rst:69 -msgid "" -"Within this section we're displaying the -in our opinion- most important " -"indexes for a Zammad instance." +#: ../system/core-workflows/condition-operators.rst:87 +msgid "Matches if date/time is today." msgstr "" -#: ../system/integrations/elasticsearch.rst:72 -msgid "" -"If you require all indexes or our listing is not good enough for you, point " -"your browser to the URL we're providing and append ``/_aliases?" -"pretty=true``. The result should look like this: ``https://.zammad.com/" -"_aliases?pretty=true``." +#: ../system/core-workflows/condition-operators.rst:88 +msgid "within last (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:77 +#: ../system/core-workflows/condition-operators.rst:89 msgid "" -"Your browser will automatically ask for your credentials - you'll then see " -"something like this:" +"Matches if date/time content is within specified period of time before now." msgstr "" -#: ../system/integrations/elasticsearch.rst:125 -msgid "Credentials" +#: ../system/core-workflows/condition-operators.rst:91 +msgid "within next (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:127 +#: ../system/core-workflows/condition-operators.rst:92 msgid "" -"Within this section Zammad displays your available users. The password is " -"provided once (upon activation) and cannot be retrieved after that." +"Matches if date/time content is within specified period of time after now." msgstr "" -#: ../system/integrations/elasticsearch.rst:131 -msgid "" -"If you need to change or reset your Elasticsearch user password, use the " -"\"Reset password\" button in the credentials table. Doing so creates a brand " -"new password for the account in question. This change is immediate, keep in " -"mind that this may affect third party tools connected to your instance." +#: ../system/core-workflows/how-do-they-work.rst:2 +msgid "How do they work?" msgstr "" -#: ../system/integrations/exchange.rst:2 -msgid "Exchange" +#: ../system/core-workflows/how-do-they-work.rst:4 +msgid "" +"Core Workflows are executed according to their priority. If two workflows " +"have the same priority, they are executed in alphabetical order based on " +"their **name**." msgstr "" -#: ../system/integrations/exchange.rst:4 +#: ../system/core-workflows/how-do-they-work.rst:8 msgid "" -"With Zammad's Exchange integration, you can easily use existing address " -"books without having to update more than one source." +"Because of the way Core Workflows work, all changes to attributes are " +"checked with the application server - please see :doc:`limitations` for " +"possible issues." msgstr "" -#: ../system/integrations/exchange.rst:7 +#: ../system/core-workflows/how-do-they-work.rst:12 msgid "" -"However, you should refrain from syncing all addresses, as the results may " -"not be what you expect (Exchange collects huge amounts of addresses). A " -"central address book of your company to sync makes more sense, as you can " -"ensure that Zammad gets only the data you need and want. Apart from this, it " -"is even not possible to sync the Global Address List (GAL) of your Exchange " -"system with Zammad." +"Below we're talking about settings that are important and not self-" +"explanatory." msgstr "" -#: ../system/integrations/exchange.rst:16 +#: ../system/core-workflows/how-do-they-work.rst:17 msgid "" -"**Exchange and LDAP:** The exchange sync can be overruled by Zammad's LDAP " -"integration. If you have the same users in both sources, the LDAP version " -"will always be Zammad's pick." +"Choose the object context you want to run the workflow in. This will decide " +"on your available attributes and actions." msgstr "" -#: ../system/integrations/exchange.rst:19 -msgid "" -"**One way sync:** the Exchange sync is one way. Exchange => Zammad. Changes " -"to your users inside of Zammad might be overwritten by the Exchange sync." +#: ../system/core-workflows/how-do-they-work.rst:20 +msgid "Ticket objects also have access to the ticket customer." msgstr "" -#: ../system/integrations/exchange.rst:24 +#: ../system/core-workflows/how-do-they-work.rst:25 msgid "" -"To configure Exchange integration, simply go to the System > Integrations > " -"Exchange in the admin panel. Press \"change\" and follow the wizard for " -"adding the needed Exchange information to Zammad. On the last two steps " -"Zammad will ask you for the address book(s) and your desired attribute " -"mapping. By default, Zammad only maps email address, first- and lastname. " -"Technically, you can map any Exchange object to a Zammad user object (this " -"also works for custom objects!)." +"Choose in which situation the workflow is applied. Contexts can be combined " +"to avoid duplicate workflows." msgstr "" -#: ../system/integrations/exchange.rst:35 -msgid "" -"If the SSL verification fails while connecting to Exchange, Zammad will ask " -"you to turn it off temporarily." +#: ../system/core-workflows/how-do-they-work.rst:30 +msgid "Creation mask" msgstr "" -#: ../system/integrations/exchange.rst:38 +#: ../system/core-workflows/how-do-they-work.rst:29 msgid "" -"Please be aware that **turning off SSL verification is a security risk**. It " -"should only be used temporarily or for testing purposes. If turned off, " -"there is no verification of the certificate, which means that every " -"presented certificate will be accepted." +"If selected, your conditions and actions will affect all applicable creation " +"masks." msgstr "" -#: ../system/integrations/exchange.rst:43 -msgid "" -"After pressing Continue, Zammad will check if the configuration is okay. You " -"can then enable Exchange and start your first sync. The sync will then run " -"hourly - if you need to change mappings or the address book(s), you can " -"change the configuration at any time." +#: ../system/core-workflows/how-do-they-work.rst:34 +msgid "Edit mask" msgstr "" -#: ../system/integrations/exchange.rst:50 +#: ../system/core-workflows/how-do-they-work.rst:33 msgid "" -"After the sync has finished, you can find the new Exchange contacts under " -"\"Users\". Zammad integrates them just as normal users." +"If selected, your conditions and actions will affect all applicable edit " +"masks." msgstr "" -#: ../system/integrations/exchange.rst:55 +#: ../system/core-workflows/how-do-they-work.rst:39 msgid "" -"In some cases you might see unique IDs as \"Login\" instead of the email " -"address. This is normal and doesn't affect the login or email mapping for " -"that entry." +"Zammad differentiates between selected and saved conditions. These can be " +"combined wherever needed." msgstr "" -#: ../system/integrations/github.rst:4 -msgid "" -"Use GitHub integration to track GitHub issues directly within Zammad " -"tickets. Add issue hyperlinks and get a live summary of metadata like status " -"(open/closed), assignee, labels, and more." +#: ../system/core-workflows/how-do-they-work.rst:42 +msgid "**⚠️ Restrict workflows to specific roles if needed!**" msgstr "" -#: ../system/integrations/github.rst:8 -msgid "Please note that our GitHub integration does not support pull requests." +#: ../system/core-workflows/how-do-they-work.rst:44 +msgid "" +"By default and unless configured in conditions, workflow rules are executed " +"for **all roles**. This also affects your customers!" msgstr "" -#: ../system/integrations/github.rst:None -msgid "Integration page for GitHub" +#: ../system/core-workflows/how-do-they-work.rst:50 +msgid "Selected Conditions" msgstr "" -#: ../system/integrations/github.rst:18 +#: ../system/core-workflows/how-do-they-work.rst:48 msgid "" -"In your GitHub settings, create a new API token under **Developer settings > " -"Personal access tokens > Generate new token**. Leave the **Scopes** section " -"empty." +"These conditions are based on form values and match if an appropriate " +"selection is made (e.g. choosing another group in the ticket without " +"saving). This applies for drafts (active selection) and currently saved " +"values." msgstr "" -#: ../system/integrations/github.rst:0 ../system/integrations/gitlab.rst:0 -msgid "Screencast showing how to create a new API token" +#: ../system/core-workflows/how-do-they-work.rst:64 +msgid "Saved Conditions" msgstr "" -#: ../system/integrations/github.rst:27 -msgid "Create a new API key with no scopes/privileges." +#: ../system/core-workflows/how-do-they-work.rst:53 +msgid "" +"These conditions only match if the selected values are stored in the " +"database. It ignores the current value or selection of the field, as long as " +"the changes are not saved (e.g. performing field operations for an existing " +"ticket, which is viewed/opened by an agent)." msgstr "" -#: ../system/integrations/github.rst:29 -msgid "🔒 **Will this work for private repos?**" +#: ../system/core-workflows/how-do-they-work.rst:60 +msgid "" +"Keep in mind that the value has to be available in the situation where you " +"need it. Otherwise the condition won't match." msgstr "" -#: ../system/integrations/github.rst:31 +#: ../system/core-workflows/how-do-they-work.rst:63 msgid "" -"No. To link private repo issues, **use the** ``repo`` **scope instead**. " -"Bear in mind that the resulting token will have `lots of permissions that it " -"doesn't actually need `_, which presents a security risk if your token ever falls into " -"the wrong hands." +"Example: you can't perform any actions with *saved condition* on a ticket in " +"creation, because there are no saved values at that time." msgstr "" -#: ../system/integrations/github.rst:37 +#: ../system/core-workflows/how-do-they-work.rst:66 msgid "" -"Unfortunately, because of how GitHub's OAuth token scopes are set up, this " -"is the only way to link issues on private repos." +"You can find a description of the condition operators for core workflows :" +"doc:`here `." msgstr "" -#: ../system/integrations/github.rst:40 -msgid "Enter your new API token in Zammad and enable GitHub integration." +#: ../system/core-workflows/how-do-they-work.rst:72 +msgid "" +"Which actions should we run on the relevant fields? The possible actions " +"depend on the object type. However, usually you can at least change the " +"visibility and whether the field is mandatory." msgstr "" -#: ../system/integrations/github.rst:0 -msgid "Screencast showing how to configure Zammad's GitHub integration" +#: ../system/core-workflows/how-do-they-work.rst:76 +msgid "Be aware that actions are not available for **related** context." msgstr "" -#: ../system/integrations/github.rst:47 +#: ../system/core-workflows/how-do-they-work.rst:78 msgid "" -"Use the default API endpoint (``https://api.github.com/graphql``) unless " -"you're using GitHub Enterprise Server." +"**Example:** Let's assume you are working in the ticket context. While you " +"can have customer *conditions*, you *can't adjust* objects with actions in " +"that scope. That's because this wouldn't have any impact on the ticket " +"dialog. Of course all ticket attributes (state, owner, ...) are available." msgstr "" -#: ../system/integrations/github.rst:50 +#: ../system/core-workflows/how-do-they-work.rst:84 msgid "" -"Once completed, a new GitHub issues tab will appear in the ticket pane. 🎉" +"Please also have a look at our :doc:`limitations` to be safe from surprises." msgstr "" -#: ../system/integrations/github.rst:59 ../system/integrations/gitlab.rst:52 -msgid "Token verification is taking a long time" +#: ../system/core-workflows/how-do-they-work.rst:88 +msgid "Available Operators" msgstr "" -#: ../system/integrations/github.rst:56 ../system/integrations/gitlab.rst:49 -msgid "" -"Slight delays are normal (<2 min.), especially for systems under heavy load." +#: ../system/core-workflows/how-do-they-work.rst:90 +msgid "The availability of operators depends on the object type and scope." msgstr "" -#: ../system/integrations/github.rst:58 +#: ../system/core-workflows/how-do-they-work.rst:94 msgid "" -"Self-hosted administrators, please check your network settings to ensure " -"that your Zammad server can reach ``api.github.com``." +"Please note that actions may or may not restrict API based access to " +"attributes. We're displaying the following icons for your overview to " +"understand these limits better:" msgstr "" -#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 -msgid "I reloaded the page and now the API token is gone" +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|api| This icon indicates the action affects the API." msgstr "" -#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 -msgid "" -"This may indicate that Zammad is still verifying your API token. Try " -"reloading the page again in a couple minutes." +#: ../system/core-workflows/how-do-they-work.rst:163 +msgid "api" msgstr "" -#: ../system/integrations/gitlab.rst:2 -msgid "GitLab" +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|ui| This icon indicates the action only affects the web interface." msgstr "" -#: ../system/integrations/gitlab.rst:4 -msgid "" -"Use GitLab integration to track GitLab issues directly within Zammad " -"tickets. Add issue hyperlinks and get a live summary of metadata like status " -"(open/closed), assignee, labels, and more." +#: ../system/core-workflows/how-do-they-work.rst:167 +msgid "ui" msgstr "" -#: ../system/integrations/gitlab.rst:8 -msgid "" -"Please note that our GitLab integration does not support merge requests." +#: ../system/core-workflows/how-do-they-work.rst:102 +msgid "show |ui|" msgstr "" -#: ../system/integrations/gitlab.rst:None -msgid "Integration page for GitLab" +#: ../system/core-workflows/how-do-they-work.rst:102 +msgid "Display the chosen field. Allows setting of values." msgstr "" -#: ../system/integrations/gitlab.rst:18 -msgid "" -"In your GitLab preferences, create a new API token under **Access Tokens**." +#: ../system/core-workflows/how-do-they-work.rst:109 +msgid "hide |ui|" msgstr "" -#: ../system/integrations/gitlab.rst:20 -msgid "Under **Select scopes**, choose ``read_api`` only." +#: ../system/core-workflows/how-do-they-work.rst:105 +msgid "" +"Hide the chosen field. However, it technically still allows setting the " +"field." msgstr "" -#: ../system/integrations/gitlab.rst:27 -msgid "🔒 **If you wish to link issues on any private repos...**" +#: ../system/core-workflows/how-do-they-work.rst:108 +msgid "" +"Please note that the field is **not** gone and still contains an existing " +"value (if set)! Consider *remove* instead, if you want this field to be gone." msgstr "" -#: ../system/integrations/gitlab.rst:29 -msgid "Your API token must belong to an account with access to those repos." +#: ../system/core-workflows/how-do-they-work.rst:112 +msgid "remove |ui|" msgstr "" -#: ../system/integrations/gitlab.rst:31 -msgid "Enter your new API token in Zammad and enable GitLab integration." +#: ../system/core-workflows/how-do-they-work.rst:112 +msgid "Entirely removes the field. The field value will not be evaluated." msgstr "" -#: ../system/integrations/gitlab.rst:0 -msgid "Screencast showing how to configure Zammad's GitLab integration" +#: ../system/core-workflows/how-do-they-work.rst:115 +msgid "set mandatory |ui| |api|" msgstr "" -#: ../system/integrations/gitlab.rst:40 -msgid "" -"Use the default API endpoint (``https://gitlab.com/api/graphql``) unless " -"you're a self-hosted GitLab user." +#: ../system/core-workflows/how-do-they-work.rst:115 +msgid "Sets the field to mandatory." msgstr "" -#: ../system/integrations/gitlab.rst:43 -msgid "" -"Once completed, a new GitLab issues tab will appear in the ticket pane. 🎉" +#: ../system/core-workflows/how-do-they-work.rst:118 +msgid "set optional |ui| |api|" msgstr "" -#: ../system/integrations/gitlab.rst:51 -msgid "" -"Self-hosted administrators, please check your network settings to ensure " -"that your Zammad server can reach ``gitlab.com``." +#: ../system/core-workflows/how-do-they-work.rst:118 +msgid "Sets the field to optional." msgstr "" -#: ../system/integrations/i-doit.rst:2 -msgid "i-doit" +#: ../system/core-workflows/how-do-they-work.rst:124 +msgid "add option |ui| |api|" msgstr "" -#: ../system/integrations/i-doit.rst:4 -msgid "" -"`i-doit `_ is an open-source **configuration " -"management database** - in other words, a tool for keeping tabs on every " -"single piece of your physical and digital infrastructure, from network " -"equipment to virtual machines on down to the faceplates on your rack shelves " -"and more." +#: ../system/core-workflows/how-do-they-work.rst:121 +msgid "Allows adding options to tree selects or selects." msgstr "" -#: ../system/integrations/i-doit.rst:10 +#: ../system/core-workflows/how-do-they-work.rst:123 msgid "" -"What's that got to do with Zammad? Well, if you used tickets to track issues " -"with all that hardware, you might start wishing there was a way they could " -"talk to each other." -msgstr "" - -#: ../system/integrations/i-doit.rst:14 -msgid "Zammad gives you two:" +"You have to use the \"remove option\" before performing this action. It " +"allows you to use *existing* configured values." msgstr "" -#: ../system/integrations/i-doit.rst:17 -msgid "1. Add i-doit Links to Zammad Tickets" +#: ../system/core-workflows/how-do-they-work.rst:128 +msgid "remove option |ui| |api|" msgstr "" -#: ../system/integrations/i-doit.rst:20 ../system/integrations/i-doit.rst:80 -msgid "What Users See" +#: ../system/core-workflows/how-do-they-work.rst:127 +msgid "" +"Allows removing options from tree selects or selects. It allows you to use " +"*existing* configured values." msgstr "" -#: ../system/integrations/i-doit.rst:26 -msgid "i-doit integration in Zammad's ticket pane" +#: ../system/core-workflows/how-do-they-work.rst:134 +msgid "set fixed to |ui| |api|" msgstr "" -#: ../system/integrations/i-doit.rst:26 -msgid "" -"The i-doit integration will appear under a new 🖨 tab in the ticket pane." +#: ../system/core-workflows/how-do-they-work.rst:131 +msgid "Reduces the available options by your selection." msgstr "" -#: ../system/integrations/i-doit.rst:28 +#: ../system/core-workflows/how-do-they-work.rst:133 msgid "" -"i-doit integration puts a new tab in Zammad's ticket pane where you can add " -"links to existing i-doit devices for easy reference. (See our :user-docs:" -"`user documentation ` to learn " -"how it works in practice)." +"This reduces your workflows in terms of *add option* and *remove option*." msgstr "" -#: ../system/integrations/i-doit.rst:36 ../system/integrations/i-doit.rst:93 -msgid "How to Set it Up" +#: ../system/core-workflows/how-do-they-work.rst:137 +msgid "fill in |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:38 -msgid "" -"It requires i-doit's `API Add-on `_. Make sure to have it properly set up. Use the following setting:" +#: ../system/core-workflows/how-do-they-work.rst:137 +msgid "Allows filling in of string and integer fields with your values." msgstr "" -#: ../system/integrations/i-doit.rst:42 -msgid "Active: ``Yes``" +#: ../system/core-workflows/how-do-they-work.rst:141 +msgid "fill in empty |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:43 -msgid "Enforce authentication by username and password: ``No``" +#: ../system/core-workflows/how-do-they-work.rst:140 +msgid "" +"Allows filling in of string and integer fields with your values **if the " +"field is empty**." msgstr "" -#: ../system/integrations/i-doit.rst:45 -msgid "" -"To set it up, enable the integration in the Zammad admin panel under " -"**System > Integrations > i-doit**:" +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "select |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "i-doit settings within the integration pages" +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "Select a specific value within a select, tree select or boolean field." msgstr "" -#: ../system/integrations/i-doit.rst:53 -msgid "The root URL of your i-doit installation." +#: ../system/core-workflows/how-do-they-work.rst:153 +msgid "auto select |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:62 -msgid "API token" +#: ../system/core-workflows/how-do-they-work.rst:147 +msgid "Helps users with tree select and select fields:" msgstr "" -#: ../system/integrations/i-doit.rst:56 +#: ../system/core-workflows/how-do-they-work.rst:149 msgid "" -"Found in the i-doit admin panel under **Interfaces / external data > JSON-" -"RPC API > Common Settings**." +"If the field has only one option available for selection and no value yet, " +"the value will be automatically set." msgstr "" -#: ../system/integrations/i-doit.rst:0 -msgid "i-doit administration interface with API configuration" +#: ../system/core-workflows/how-do-they-work.rst:152 +msgid "" +"This option only works if you have one value and doesn't work if there is " +"more than one option available." msgstr "" -#: ../system/integrations/i-doit.rst:67 -msgid "Client ID" +#: ../system/core-workflows/how-do-they-work.rst:157 +msgid "set readonly |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:65 -msgid "A unique name to identify Zammad within i-doit." +#: ../system/core-workflows/how-do-they-work.rst:156 +msgid "" +"Allows you to display an attribute as read only (which means no changes are " +"possible)." msgstr "" -#: ../system/integrations/i-doit.rst:67 -msgid "(Zammad does not require you to enter a value here, but i-doit might!)" +#: ../system/core-workflows/how-do-they-work.rst:161 +msgid "unset readonly |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:70 +#: ../system/core-workflows/how-do-they-work.rst:160 msgid "" -"Here you can decide if the certificate of your i-doit system has to be " -"verified or not. In case you are using custom certificates, please have a " -"look at :doc:`how to add them to Zammad `." -msgstr "" - -#: ../system/integrations/i-doit.rst:77 -msgid "2. List / Create Zammad Tickets in i-doit" +"In case a workflow set the field in question to read only, you can undo this " +"with option above." msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "Zammad integration in i-doit's device view" +#: ../system/core-workflows/how-do-they-work.rst:172 +msgid "Stop after match" msgstr "" -#: ../system/integrations/i-doit.rst:86 +#: ../system/core-workflows/how-do-they-work.rst:174 msgid "" -"i-doit's ticket system integration gives you a way to see all the tickets " -"for a given device without ever leaving i-doit. (See our :user-docs:`user " -"documentation ` to learn how it " -"works in practice)." +"Here you can decide if other workflows are executed after the current one." msgstr "" -#: ../system/integrations/i-doit.rst:95 +#: ../system/core-workflows/how-do-they-work.rst:176 msgid "" -"Enable this integration in the i-doit admin panel under **Interfaces / " -"external data > Trouble Ticket System (TTS) > Configuration**:" +"If set to ``no`` (default), further workflows will be executed if they match " +"the condition. In this case, it is possible that your actions from the " +"current workflow can be overwritten by another workflow." msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "i-doit administration interface with TTS configuration" +#: ../system/core-workflows/how-do-they-work.rst:180 +msgid "" +"If set to ``yes``, no further worflows will be executed after the current " +"one." msgstr "" -#: ../system/integrations/i-doit.rst:104 -msgid "TTS-Type" +#: ../system/core-workflows/how-do-they-work.rst:184 +msgid "Priority" msgstr "" -#: ../system/integrations/i-doit.rst:104 -msgid "``Zammad``" +#: ../system/core-workflows/how-do-they-work.rst:186 +msgid "" +"You can define the sequence, in which the workflows are executed. The " +"default value is ``500``." msgstr "" -#: ../system/integrations/i-doit.rst:115 -msgid "Username / Password" +#: ../system/core-workflows/how-do-they-work.rst:189 +msgid "" +"The workflows are executed in ascending order by their priority. That means " +"lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." msgstr "" -#: ../system/integrations/i-doit.rst:107 -msgid "Login credentials for a Zammad agent." +#: ../system/core-workflows/learn-by-example.rst:2 +msgid "Learn by Example" msgstr "" -#: ../system/integrations/i-doit.rst:109 +#: ../system/core-workflows/learn-by-example.rst:4 msgid "" -"This agent must have **read permission** for all :doc:`groups ` that plan on using the i-doit integration." +"This page provides some basic examples for Core Workflows. Of course you can " +"build much more complex workflows if needed." msgstr "" -#: ../system/integrations/i-doit.rst:113 +#: ../system/core-workflows/learn-by-example.rst:7 msgid "" -"You may even wish to create a dedicated agent account just for this " -"integration (otherwise, if the agent ever changes her password, you will " -"have to remember to update it here)." +"To learn about Core Workflows in detail, first go to :doc:`how-do-they-work`." msgstr "" -#: ../system/integrations/i-doit.rst:117 -msgid "URL incl. protocol" +#: ../system/core-workflows/learn-by-example.rst:10 +msgid "Group Based Examples" msgstr "" -#: ../system/integrations/i-doit.rst:118 -msgid "``https://your.zammad.domain``" +#: ../system/core-workflows/learn-by-example.rst:12 +msgid "" +"All following workflows have the same base configurations. The workflow may " +"not use them all." msgstr "" -#: ../system/integrations/index.rst:2 -msgid "Integrations" +#: ../system/core-workflows/learn-by-example.rst:15 +msgid "Groups:" msgstr "" -#: ../system/integrations/index.rst:4 +#: ../system/core-workflows/learn-by-example.rst:20 +msgid "Attributes:" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:22 +msgid "Category (Single tree selection field, not mandatory, agents only)" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:23 msgid "" -"Zammad offers numerous integrations that add rich features to your instance." +"Approved (Boolean field, not mandatory, not shown, ``false`` as default)" msgstr "" -#: ../system/integrations/index.rst:6 -msgid "We're still working on this part of our documentation, stay tight!" +#: ../system/core-workflows/learn-by-example.rst:24 +msgid "Operating System (Text field, not mandatory, not shown)" msgstr "" -#: ../system/integrations/index.rst:10 -msgid "Integrations for Phone Systems" +#: ../system/core-workflows/learn-by-example.rst:25 +msgid "Software used (Single selection field, not mandatory, not shown)" msgstr "" -#: ../system/integrations/index.rst:14 -msgid "" -"Your VoIP provider or telephony system is not listed? Possibly your provider " -"supports Zammad by using the generic CTI - if you're unsure ask your " -"provider." +#: ../system/core-workflows/learn-by-example.rst:68 +msgid "Group specific values and fields" msgstr "" -#: ../system/integrations/index.rst:18 +#: ../system/core-workflows/learn-by-example.rst:28 msgid "" -"Provider does not support Zammad? Consider creating a `feature request in " -"the Zammad Community `_." +"This workflow set depends on the category field. It reduces the available " +"set of values based on the group selected." msgstr "" -#: ../system/integrations/index.rst:31 -msgid "Integrations for Authentication and Customers" +#: ../system/core-workflows/learn-by-example.rst:33 +msgid "Workflow 2nd Level group" msgstr "" -#: ../system/integrations/index.rst:44 -msgid "Integrations for Monitoring Systems" +#: ../system/core-workflows/learn-by-example.rst:35 +msgid "" +"This reduces the category options to ``2nd Level/*``, ``Internal/*`` and " +"``Others``. It also sets further required fields to mandatory and visible." msgstr "" -#: ../system/integrations/index.rst:46 -msgid "This section currently misses the following integrations:" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for 2nd level" msgstr "" -#: ../system/integrations/index.rst:48 -msgid "Icinga" +#: ../system/core-workflows/learn-by-example.rst:43 +msgid "Workflow Support group" msgstr "" -#: ../system/integrations/index.rst:49 -msgid "Monit" +#: ../system/core-workflows/learn-by-example.rst:45 +msgid "" +"This reduces the category options to ``Support/*``, ``Internal/*`` and " +"``Others``. It also sets further required fields to visible." msgstr "" -#: ../system/integrations/index.rst:50 -msgid "Nagios" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for support" msgstr "" -#: ../system/integrations/index.rst:60 -msgid "Integrations for Issue Trackers" +#: ../system/core-workflows/learn-by-example.rst:53 +msgid "Workflow Sales group" msgstr "" -#: ../system/integrations/index.rst:70 -msgid "Other Integrations" +#: ../system/core-workflows/learn-by-example.rst:55 +msgid "" +"This reduces the category options to ``Sales/*``, ``Internal/*`` and " +"``Others``." msgstr "" -#: ../system/integrations/index.rst:72 -msgid "" -"This section will hold any other integration that can't be grouped up (yet)." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for sales" msgstr "" -#: ../system/integrations/ldap/index.rst:2 -msgid "LDAP / Active Directory" +#: ../system/core-workflows/learn-by-example.rst:68 +#: ../system/integrations/slack.rst:88 +msgid "The Result" msgstr "" -#: ../system/integrations/ldap/index.rst:4 +#: ../system/core-workflows/learn-by-example.rst:63 msgid "" -"Zammad comes with a powerful LDAP integration that allows you to have a " -"single source of truth. By this you reduce the number of login credentials " -"your user has to remember." +"This is what the agent would experience with the above workflows in place." msgstr "" -#: ../system/integrations/ldap/index.rst:10 +#: ../system/core-workflows/learn-by-example.rst:0 msgid "" -"The LDAP source is also a perfect candidate for Zammad's :docs:`Kerberos " -"Single Sign-On ` but also works as addition " -"to other :doc:`/settings/security/third-party`." +"Workflow shows objects and limits options based on selections on the group" msgstr "" -#: ../system/integrations/ldap/index.rst:None -msgid "Zammands LDAP management page" +#: ../system/core-workflows/learn-by-example.rst:90 +msgid "Approval process" msgstr "" -#: ../system/integrations/ldap/index.rst:25 -msgid "📝 :doc:`manage`" +#: ../system/core-workflows/learn-by-example.rst:71 +msgid "" +"In this case ``approved`` is visible to agents by default. For this " +"workflow, an additional role ``Approval person`` is required (no further " +"permissions)." msgstr "" -#: ../system/integrations/ldap/index.rst:25 -msgid "Add, modify, remove or re-arrange your LDAP-Sources as needed." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that restricts an approval attribute to specific roles" msgstr "" -#: ../system/integrations/ldap/index.rst:30 -msgid "Before you continue, please note the following limitations." +#: ../system/core-workflows/learn-by-example.rst:81 +msgid "" +"This workflow may work best in combination with a :doc:`trigger ` but technically, this is not required." msgstr "" -#: ../system/integrations/ldap/index.rst:32 -msgid "Mapping / Synchronizing organizations is not possible" +#: ../system/core-workflows/learn-by-example.rst:84 +msgid "" +"Select fields may be a better approach because they allow more values than " +"just a simple ``true`` or ``false``." msgstr "" -#: ../system/integrations/ldap/index.rst:36 +#: ../system/core-workflows/learn-by-example.rst:0 msgid "" -"You may want to consider using domain based assignments to overcome this " -"issue. Learn more on :doc:`/manage/organizations/index`." +"Workflow fixes possible values of \"Approved ?\" to a specific selection " +"depending on the users role" msgstr "" -#: ../system/integrations/ldap/index.rst:39 +#: ../system/core-workflows/learn-by-example.rst:103 +msgid "State dependent mandatory fields" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:93 msgid "" -"Zammad's LDAP sync is one way. Editing user settings or permissions may be " -"overwritten upon the next sync depending on your configuration." +"This workflow sets ``Category`` to mandatory if the agent wants to set the " +"states ``closed`` or ``pending close`` to enforce categorization." msgstr "" -#: ../system/integrations/ldap/index.rst:41 -msgid "Nested groups are not supported." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that sets fields to mandatory on specific states" msgstr "" -#: ../system/integrations/ldap/index.rst:42 -msgid "Synchronizing user avatars from LDAP is not supported." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "" +"Workflow sets category field to mandatory upon choosing closed or pending " +"close as state" msgstr "" -#: ../system/integrations/ldap/index.rst:43 -msgid "Unlike user filters, group filters cannot be changed." +#: ../system/core-workflows/learn-by-example.rst:106 +msgid "Manual Ticket Handover Process" msgstr "" -#: ../system/integrations/ldap/index.rst:44 -msgid "" -"When a user originates from an LDAP server, Zammad will try to verify the " -"login credentials against LDAP first - if this fails Zammad will check its " -"local database." +#: ../system/core-workflows/learn-by-example.rst:108 +msgid "This example covers the handover of a ticket from one agent to another:" msgstr "" -#: ../system/integrations/ldap/index.rst:50 +#: ../system/core-workflows/learn-by-example.rst:110 msgid "" -"Users can have local passwords even if they're LDAP users! You can learn " -"more about user accounts in general on :doc:`/manage/users/index`." +"When the ticket owner is modified, a new text field (\"Handover\") shows up " +"for a comment" msgstr "" -#: ../system/integrations/ldap/index.rst:54 +#: ../system/core-workflows/learn-by-example.rst:112 msgid "" -"When several LDAP sources contain the same user (meaning the same email " -"address), the user in question will be updated with every source configured. " -"*The last LDAP source will win.*" +"This may only be visible when the owner is changed, therefore it has to be " +"hidden in general" msgstr "" -#: ../system/integrations/ldap/index.rst:58 -msgid "" -"This is subject to change with `Issue 4109 `_ in the future." +#: ../system/core-workflows/learn-by-example.rst:114 +msgid "The input in this handover text field is mandatory" msgstr "" -#: ../system/integrations/ldap/index.rst:60 +#: ../system/core-workflows/learn-by-example.rst:115 msgid "" -"Synchronization statistics currently affect *all* configured LDAP sources. " -"This also applies for newly added or updated sources." +"After submitting changes, the value of the handover field must be added as " +"an note to the ticket (via trigger)" msgstr "" -#: ../system/integrations/ldap/index.rst:63 -msgid "" -"This is subject to change with `Issue 4108 `_ in the future." +#: ../system/core-workflows/learn-by-example.rst:121 +msgid "Hiding handover field" msgstr "" -#: ../system/integrations/ldap/index.rst:65 -msgid "" -"Zammad currently has limited fallback server support. You can workaround " -"this by providing several sources - however, ensure to have the exact same " -"configuration on your fallback." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Hiding the handover field in core workflows" msgstr "" -#: ../system/integrations/ldap/index.rst:69 -msgid "" -"This is subject to improve with `Issue 4107 `_ in the future." +#: ../system/core-workflows/learn-by-example.rst:126 +msgid "Showing handover field and setting it to mandatory" msgstr "" -#: ../system/integrations/ldap/index.rst:76 -msgid "" -"This section holds all requests Zammad handled for all LDAP sources. These " -"entries can either contain synchronization information or logins " -"(authentication attempts via Zammad's login interface)." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Showing the handover field and set it as mandatory" msgstr "" -#: ../system/integrations/ldap/index.rst:80 -msgid "" -"By clicking on any request, Zammad will provide even more information. The " -"provided information can be useful when something does not work as expected." +#: ../system/core-workflows/learn-by-example.rst:131 +msgid "Trigger writing handover input to a new article" msgstr "" -#: ../system/integrations/ldap/index.rst:85 -msgid "" -"Especially a LDAP synchronization can cause many log entries. The web " -"interface will always limit the number of shown entries to the last 50 " -"entries." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Write handover content to a new article" msgstr "" -#: ../system/integrations/ldap/index.rst:None +#: ../system/core-workflows/learn-by-example.rst:133 msgid "" -"Screencast showing LDAP integration log entries and a detail view on\n" -"an entry." +"As a result, the ticket includes an article of the type note which includes " +"the predefined text and the handover comment." msgstr "" -#: ../system/integrations/ldap/manage.rst:2 -msgid "Manage LDAP-Sources" +#: ../system/core-workflows/limitations.rst:6 +msgid "Core Workflows do not replace Triggers" msgstr "" -#: ../system/integrations/ldap/manage.rst:6 +#: ../system/core-workflows/limitations.rst:5 msgid "" -"Please keep in mind all current limitations for the LDAP synchronization. " -"This will help to understand scopes of the following operations better." +"Workflows manipulate the behavior of fields. However, they do not set values " +"in fields because of actions." msgstr "" -#: ../system/integrations/ldap/manage.rst:65 -msgid "Add new source" +#: ../system/core-workflows/limitations.rst:16 +msgid "API calls are only partly affected" msgstr "" -#: ../system/integrations/ldap/manage.rst:10 +#: ../system/core-workflows/limitations.rst:9 msgid "" -"Using the *New Source* button allows you to add new LDAP sources to your " -"installation. You're not limited in the number of sources, however, keep in " -"mind that many sources will also take more time to synchronize." +"Some options affect UI only and thus do not restrict responses and calls." msgstr "" -#: ../system/integrations/ldap/manage.rst:14 -msgid "" -"You can choose between different encryption types, namely *SSL* and " -"*STARTTLS* or none of them (\"*No SSL*\"). If you choose *SSL* or " -"*STARTTLS*, Zammad will display an additional *SSL verification* option that " -"allows you to disable the verification, e.g. for self-signed SSL " -"certificates. You can also tell Zammad to use a different port by appending " -"``:`` to your hostname/IP." +#: ../system/core-workflows/limitations.rst:11 +msgid "This affects the following actions:" msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "" -"Screenshot of configuring a new LDAP source with SSL encryption and SSL " -"verification" +#: ../system/core-workflows/limitations.rst:13 +msgid "select" msgstr "" -#: ../system/integrations/ldap/manage.rst:26 -msgid "" -"New Source with SSL transport security enabled and certificate verification" +#: ../system/core-workflows/limitations.rst:14 +msgid "auto select" msgstr "" -#: ../system/integrations/ldap/manage.rst:30 -msgid "" -"Using an user filter can be a good idea if you only require a small subset " -"of your LDAP users in Zammad." +#: ../system/core-workflows/limitations.rst:15 +msgid "show" msgstr "" -#: ../system/integrations/ldap/manage.rst:42 -msgid "This especially affects inactive users" +#: ../system/core-workflows/limitations.rst:16 +msgid "hide" msgstr "" -#: ../system/integrations/ldap/manage.rst:34 -msgid "" -"As every LDAP behaves differently on which attributes and how they are set, " -"Zammad doesn't care about any flags." +#: ../system/core-workflows/limitations.rst:25 +msgid "Some fields stay unavailable to customers" msgstr "" -#: ../system/integrations/ldap/manage.rst:37 +#: ../system/core-workflows/limitations.rst:19 msgid "" -"Users that no longer are returned by your LDAP source will automatically be " -"set to inactive. Zammad assumes that the user was deactivated." +"For technical and security reasons, some default fields (the pale ones you " +"can't edit) stay unavailable for display and usage on customer permissions." msgstr "" -#: ../system/integrations/ldap/manage.rst:41 +#: ../system/core-workflows/limitations.rst:23 msgid "" -"Users will never be removed automatically! If you want to remove obsolete " -"users, use :doc:`/system/data-privacy`." +"If you require your customers to change e.g. priorities, please consider " +"using workarounds via :doc:`/system/objects` and :doc:`/manage/trigger`." msgstr "" -#: ../system/integrations/ldap/manage.rst:46 -msgid "Active Directory admins" +#: ../system/core-workflows/limitations.rst:29 +msgid "Ticket title changes not supported in edit mask" msgstr "" -#: ../system/integrations/ldap/manage.rst:45 +#: ../system/core-workflows/limitations.rst:28 msgid "" -"Active Directories are quite specific on how to filter for active users only " -"- please see the `Microsoft documentation `_ for more " -"information." +"It is currently not possible to perform changes of the ticket title in the " +"edit mask (e.g. renaming, set to read-only)." msgstr "" -#: ../system/integrations/ldap/manage.rst:51 -msgid "" -"*Do not* manually write pathes of either LDAP attributes or groups. If " -"Zammad does not display them, it either cannot find them or you have a lot " -"of users that don't have the attributes populated." +#: ../system/core-workflows/limitations.rst:37 +msgid "What is out of scope of Core Workflows?" msgstr "" -#: ../system/integrations/ldap/manage.rst:55 +#: ../system/core-workflows/limitations.rst:32 msgid "" -"Zammad will always only return attributes that are filled - this reduces the " -"returned list of attributes greatly." +"There are some things that would count as workflow but are either done via :" +"doc:`/manage/trigger` or :doc:`/manage/scheduler`." msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing how to add a new LDAP source" +#: ../system/core-workflows/limitations.rst:35 +msgid "Such as (but not limited to):" msgstr "" -#: ../system/integrations/ldap/manage.rst:63 -msgid "" -"If your LDAP system doesn't allow anonymous bind, Zammad detects it and " -"provides you an editable \"Base DN\" *text* field instead of a prefilled " -"*select* field." +#: ../system/core-workflows/limitations.rst:37 +msgid "up- or downgrade permissions of users" msgstr "" -#: ../system/integrations/ldap/manage.rst:81 -msgid "Review or edit existing source" +#: ../system/core-workflows/limitations.rst:38 +msgid "affecting article creation or listing" msgstr "" -#: ../system/integrations/ldap/manage.rst:68 +#: ../system/data-privacy.rst:2 +msgid "Data Privacy" +msgstr "" + +#: ../system/data-privacy.rst:4 msgid "" -"Clicking on a LDAP source will provide a configuration and mapping overview." +"For compliance with GDPR and other data privacy laws, you may wish to " +"**permanently delete users from the system**, along with **all of their " +"associated tickets**." msgstr "" -#: ../system/integrations/ldap/manage.rst:70 +#: ../system/data-privacy.rst:8 msgid "" -"If needed you can then use the *Change* button to update either the name, " -"active state or the whole configuration. If you're changing the whole " -"configuration, the dialogue will be identical to the source creation." +"You can create manual deletion tasks or even automated deletion tasks for " +"tickets and users based on custom conditions via :doc:`scheduler `!" msgstr "" -#: ../system/integrations/ldap/manage.rst:76 +#: ../system/data-privacy.rst:12 msgid "" -"Did your LDAP server change? Different LDAP servers have different " -"structures and default attributes. This causes the LDAP synchronization to " -"likely fail. Consider removing the affected source and re-add it." +"Access to this panel requires ``admin.data_privacy`` permissions (introduced " +"in Zammad 3.5)." msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing the update of the source name." +#: ../system/data-privacy.rst:15 +msgid "" +"On older systems that have not been updated yet, customers can also be :docs:" +"`deleted via the Zammad console `." msgstr "" -#: ../system/integrations/ldap/manage.rst:89 -msgid "Re-arrange LDAP source's order" +#: ../system/data-privacy.rst:22 +msgid "User deletion dialog in the Data Privacy panel" msgstr "" -#: ../system/integrations/ldap/manage.rst:84 +#: ../system/data-privacy.rst:22 msgid "" -"You can change the synchronization order for each source at any time. Zammad " -"will synchronize the sources from top to bottom." +"The user deletion dialog lists some of the tickets that will be removed from " +"the system along with the user." msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "" -"Screencasting showing how to change the source order by using\n" -"drag and drop." +#: ../system/data-privacy.rst:27 +msgid "Deleting Users via GUI" msgstr "" -#: ../system/integrations/ldap/manage.rst:101 -msgid "Remove a source" +#: ../system/data-privacy.rst:29 +msgid "🔥 **All deletions are FINAL!**" msgstr "" -#: ../system/integrations/ldap/manage.rst:92 -msgid "" -"If you no longer need the a LDAP source or simply want to start over, you " -"can remove them at any time. This will not remove synchronized users, data " -"synchronized or permissions." +#: ../system/data-privacy.rst:31 +msgid "Once you click “Delete”, the action cannot be canceled or undone." msgstr "" -#: ../system/integrations/ldap/manage.rst:98 +#: ../system/data-privacy.rst:33 msgid "" -"Not sure if you'd need the source later on? Set the source to inactive " -"instead of removing it - see *Review or edit existing source* for more." +"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." msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing how to remove LDAP sources." +#: ../system/data-privacy.rst:36 +msgid "**The following records cannot be deleted:**" msgstr "" -#: ../system/integrations/pgp/index.rst:2 -msgid "PGP" +#: ../system/data-privacy.rst:38 +msgid "your own account" msgstr "" -#: ../system/integrations/pgp/index.rst:7 -msgid "" -"Pretty Good Privacy (PGP) is another method for secure email communication. " -"With PGP, you can exchange **signed** and **encrypted** messages with others." +#: ../system/data-privacy.rst:39 +msgid "the system's last remaining administrator account" msgstr "" -#: ../system/integrations/pgp/index.rst:13 -#: ../system/integrations/smime/index.rst:17 -msgid "Signing" +#: ../system/data-privacy.rst:42 +msgid "Step 1: Find a User / Confirm Deletion" msgstr "" -#: ../system/integrations/pgp/index.rst:11 -msgid "is a proof that a message hasn't been manipulated on its way." +#: ../system/data-privacy.rst:44 +msgid "There are three ways to access the user deletion dialog:" msgstr "" -#: ../system/integrations/pgp/index.rst:13 -msgid "" -"In other words, it guarantees message **integrity** and **authenticity**." +#: ../system/data-privacy.rst:51 +msgid "**from the user's profile**" msgstr "" -#: ../system/integrations/pgp/index.rst:19 -#: ../system/integrations/smime/index.rst:22 -msgid "Encryption" +#: ../system/data-privacy.rst:0 +msgid "Accessing the user deletion dialog in a user profile" msgstr "" -#: ../system/integrations/pgp/index.rst:16 -#: ../system/integrations/smime/index.rst:20 -msgid "" -"scrambles a message so that it can only be unscrambled by the intended " -"recipient." +#: ../system/data-privacy.rst:51 +msgid "Click **Action > Delete**." msgstr "" -#: ../system/integrations/pgp/index.rst:19 -msgid "" -"In other words, it guarantees message **privacy** and **data security**." +#: ../system/data-privacy.rst:58 +msgid "**in the “Manage > Users” Admin Panel**" msgstr "" -#: ../system/integrations/pgp/index.rst:25 -msgid "Screenshot of ticket creation with encrypt and sign buttons" +#: ../system/data-privacy.rst:0 +msgid "Accessing the user deletion dialog under “Users” in the Admin Panel" msgstr "" -#: ../system/integrations/pgp/index.rst:25 -msgid "" -"Once PGP has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " -"appear in the ticket composer." +#: ../system/data-privacy.rst:58 +msgid "Use the **⋮ Actions** menu for the target user." msgstr "" -#: ../system/integrations/pgp/index.rst:28 -msgid "**Sign button not visible?**" +#: ../system/data-privacy.rst:66 ../system/data-privacy.rst:104 +msgid "**in the “System > Data Privacy” Admin Panel**" msgstr "" -#: ../system/integrations/pgp/index.rst:30 +#: ../system/data-privacy.rst:0 msgid "" -"Please note that the signing of emails is based on the outgoing email " -"account. That means you have to choose a group with a sender email account, " -"which has a private key assigned." +"Accessing the user deletion dialog under “Data Privacy” in the Admin Panel" msgstr "" -#: ../system/integrations/pgp/index.rst:35 -msgid "Handling of Keys" +#: ../system/data-privacy.rst:65 +msgid "" +"Use the **New Deletion Task** button. Search for users by name or email " +"address." msgstr "" -#: ../system/integrations/pgp/index.rst:36 -msgid "" -"To use the PGP function, you have to enable the integration (PGP) by " -"switching the toggle to *enabled*." +#: ../system/data-privacy.rst:79 +msgid "**Delete organizations**" msgstr "" -#: ../system/integrations/pgp/index.rst:39 +#: ../system/data-privacy.rst:69 msgid "" -"You can add keys by clicking the *add key* button. The keys can be imported " -"from a file or you can paste the content of the key in the text box." +"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:" msgstr "" -#: ../system/integrations/pgp/index.rst:42 -msgid "**Which keys do I have to import?**" +#: ../system/data-privacy.rst:0 +msgid "Deleting an organization via the user deletion dialog" msgstr "" -#: ../system/integrations/pgp/index.rst:44 +#: ../system/data-privacy.rst:78 msgid "" -"For **signing** *outgoing* emails, you have to import the private key of " -"your Zammad email account." +"If this option does not appear, make sure there are no pending deletion " +"tasks for other customers from this organization." msgstr "" -#: ../system/integrations/pgp/index.rst:47 -msgid "" -"For **encrypting** *outgoing* emails, you have to import the public key of " -"the customer's email account." +#: ../system/data-privacy.rst:82 +msgid "Step 2: Monitor Deletion Job Status" msgstr "" -#: ../system/integrations/pgp/index.rst:50 +#: ../system/data-privacy.rst:84 msgid "" -"For **verifying the signature** of signed *incoming* emails, you have to " -"import the public key of the customer." +"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:" msgstr "" -#: ../system/integrations/pgp/index.rst:53 -msgid "" -"For **decrypting** of encrypted *incoming* emails, you have to import the " -"private key of your Zammad email account." +#: ../system/data-privacy.rst:98 +msgid "**in the Activity Stream**" msgstr "" -#: ../system/integrations/pgp/index.rst:57 -msgid "Import Keys From a File" +#: ../system/data-privacy.rst:0 +msgid "Activity Stream showing data privacy tasks" msgstr "" -#: ../system/integrations/pgp/index.rst:58 -msgid "You can import keys from a file in the section **Upload key**:" +#: ../system/data-privacy.rst:94 +msgid "" +"For each deleted user, the Activity Stream will be updated twice—once when " +"the task is created, and once when it's complete." msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of adding a key via file" +#: ../system/data-privacy.rst:97 +msgid "" +"These notifications are only visible to users with ``admin.data_privacy`` " +"permissions." msgstr "" -#: ../system/integrations/pgp/index.rst:64 +#: ../system/data-privacy.rst:0 msgid "" -"**Supported file formats:** ASCII-armor as well as binary GPG format " -"(basically any GPG supported key format) is supported here." +"The task list within Data Privacy shows removals being in progress and " +"completed." msgstr "" -#: ../system/integrations/pgp/index.rst:68 -msgid "Import Keys by Pasting the Content" +#: ../system/data-privacy.rst:107 +msgid "Frequently Asked Questions" msgstr "" -#: ../system/integrations/pgp/index.rst:69 -msgid "You can also paste the key's content in the section **paste key**:" +#: ../system/data-privacy.rst:121 +msgid "What happens if I receive an email from a deleted customer?" msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of adding a key via pasting" +#: ../system/data-privacy.rst:110 +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/integrations/pgp/index.rst:75 +#: ../system/data-privacy.rst:115 msgid "" -"**Supported format:** Please note that only ASCII-armor is supported here." +"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**." msgstr "" -#: ../system/integrations/pgp/index.rst:78 -msgid "Deleting Keys" +#: ../system/data-privacy.rst:130 +msgid "What about user information stored in internal notes or other messages?" msgstr "" -#: ../system/integrations/pgp/index.rst:79 +#: ../system/data-privacy.rst:124 msgid "" -"If you want to delete a specific key, you can do it by clicking on the menu " -"in the *actions* column and select **delete**:" +"The deletion process removes **user accounts and associated tickets only**." msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of deleting a key" +#: ../system/data-privacy.rst:126 +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." msgstr "" -#: ../system/integrations/pgp/index.rst:88 -msgid "Downloading Keys" +#: ../system/data-privacy.rst:137 +msgid "I deleted an user and can still see a message they sent!" msgstr "" -#: ../system/integrations/pgp/index.rst:89 +#: ../system/data-privacy.rst:133 msgid "" -"If you want to download your keys, you can do this as well via corresponding " -"action buttons. Depending on the key, you can choose wether you want to " -"download the private or the public key." +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:95 -#: ../system/integrations/smime/manage-certificates.rst:76 -msgid "Default Behavior" +#: ../system/data-privacy.rst:141 +msgid "I removed a customer, now my reporting is off!" msgstr "" -#: ../system/integrations/pgp/index.rst:96 +#: ../system/data-privacy.rst:140 msgid "" -"Here you can adjust on per group basis, if *sign* and *encryption* is on or " -"off by default. Please be aware, that agents can always override the setting " -"for each individual article." +"When removing users and their tickets, all references are removed. This also " +"affects e.g. Reporting - these information are lost." msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Adjusting default behavior on per group basis" +#: ../system/data-privacy.rst:145 +msgid "How long does Zammad store created tasks?" msgstr "" -#: ../system/integrations/pgp/index.rst:107 +#: ../system/data-privacy.rst:144 msgid "" -"Here you can see the last actions regarding signing and encryption and if " -"they were successful." -msgstr "" - -#: ../system/integrations/pgp/index.rst:117 -msgid "**Sign button is not visible, but keys are imported.**" +"Please see the on-premise data section of the :docs:`data privacy ` chapter." msgstr "" -#: ../system/integrations/pgp/index.rst:115 -msgid "Did you choose a group in the ticket?" +#: ../system/data-privacy.rst:150 +msgid "What about re-assigned tickets? I want to delete them, too." msgstr "" -#: ../system/integrations/pgp/index.rst:116 +#: ../system/data-privacy.rst:148 msgid "" -"Did you import a private key for the email adress, which is used for " -"outgoing emails in the group?" +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:122 -msgid "**How to obtain keys?**" +#: ../system/data-privacy.rst:154 +msgid "Why are there so many deletion task entries, I didn't create them!" msgstr "" -#: ../system/integrations/pgp/index.rst:120 +#: ../system/data-privacy.rst:153 msgid "" -"You can create them yourself! There are some good tutorials on the web on " -"how to create them. Providing keys to Zammad is a prerequisite to use the " -"PGP feature." -msgstr "" - -#: ../system/integrations/pgp/index.rst:127 -msgid "**It says a passphrase is needed, but I haven't got one.**" +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:125 -msgid "" -"If the key is secured with a passphrase, you have to provide it for the " -"import in Zammad. It is possible that keys may have an empty passphrase. " -"However, this is *not* recommended." +#: ../system/integrations/checkmk/admin-panel-reference.rst:2 +msgid "Admin Panel Reference" msgstr "" -#: ../system/integrations/pgp/index.rst:132 -msgid "**How do my customers get my new key?**" +#: ../system/integrations/checkmk/admin-panel-reference.rst:None +msgid "Screenshot of Checkmk settings overview" msgstr "" -#: ../system/integrations/pgp/index.rst:130 +#: ../system/integrations/checkmk/admin-panel-reference.rst:12 msgid "" -"You have to provide your **public** key in advance. Your customer also has " -"to configure PGP in their email workflow and import your public key. The " -"other way round, you have to get the public key of your customer and have to " -"import it to Zammad." +"Which :doc:`group ` should Checkmk tickets be assigned " +"to as a default (*i.e.,* when none is specified)?" msgstr "" -#: ../system/integrations/slack.rst:2 -msgid "Slack" +#: ../system/integrations/checkmk/admin-panel-reference.rst:15 +msgid "(Applies to :ref:`API alerts ` only.)" msgstr "" -#: ../system/integrations/slack.rst:4 -msgid "**⚠️ Deprecation warning ⚠️**" +#: ../system/integrations/checkmk/admin-panel-reference.rst:21 +msgid "Auto close" msgstr "" -#: ../system/integrations/slack.rst:6 +#: ../system/integrations/checkmk/admin-panel-reference.rst:18 msgid "" -"Zammad 7 will no longer support this dedicated Slack integration. It is " -"recommended to switch to :doc:`pre-defined webhooks ` instead. Existing Slack integrations should " -"be migrated manually before this feature is dropped." +"Should Zammad automatically close tickets if a service has recovered on its " +"own?" msgstr "" -#: ../system/integrations/slack.rst:14 -msgid "" -"In order to use this feature, please add a new Slack app to your Workspace. " -"The App you need is called ``Incoming WebHooks`` ." +#: ../system/integrations/checkmk/admin-panel-reference.rst:21 +msgid "(Agents will receive notifications for such closures as appropriate.)" msgstr "" -#: ../system/integrations/slack.rst:18 -msgid "Why Do I Need This Feature?" +#: ../system/integrations/checkmk/admin-panel-reference.rst:30 +msgid "Auto-close state" msgstr "" -#: ../system/integrations/slack.rst:20 -msgid "" -"If you're already using Slack for your team communication, you'll love this " -"feature! Our Slack integration can push ticket notifications about the last " -"ticket article based on the following events:" +#: ../system/integrations/checkmk/admin-panel-reference.rst:24 +msgid "What ticket state should be applied when “auto-closing” a ticket?" msgstr "" -#: ../system/integrations/slack.rst:24 -msgid "on Ticket creation" +#: ../system/integrations/checkmk/admin-panel-reference.rst:26 +msgid "" +"You can choose from the seven built-in ticket states. If these states aren't " +"enough for you, you can :ref:`define a new ticket state ` for this purpose as well. This can be useful for tracking " +"tickets with :doc:`reports `, for example." msgstr "" -#: ../system/integrations/slack.rst:25 -msgid "on Ticket updates" +#: ../system/integrations/checkmk/admin-panel-reference.rst:35 +#: ../system/integrations/cti/includes/recent-logs.include.rst:2 +#: ../system/integrations/ldap/index.rst:74 +#: ../system/integrations/pgp/index.rst:106 +msgid "Recent Logs" msgstr "" -#: ../system/integrations/slack.rst:26 -msgid "on reached reminders" +#: ../system/integrations/checkmk/admin-panel-reference.rst:None +msgid "Screenshot of Checkmk \"Recent Logs\" section" msgstr "" -#: ../system/integrations/slack.rst:27 -msgid "a Ticket has escalated" +#: ../system/integrations/checkmk/admin-panel-reference.rst:41 +msgid "" +"If you're having trouble getting Zammad and Checkmk to play nicely together, " +"this section can help you troubleshoot." msgstr "" -#: ../system/integrations/slack.rst:28 -msgid "a Ticket is going to escalate" +#: ../system/integrations/checkmk/admin-panel-reference.rst:44 +msgid "" +"It contains a record of the fifty most recent transactions that Zammad knows " +"about, including each one's request/response details and return status." msgstr "" -#: ../system/integrations/slack.rst:30 -msgid "" -"Zammad will provide the Ticket title, a direct link to the Ticket, the event " -"type (creation, updated, escalation), the customer, time and the last " -"article that has triggered the notification." +#: ../system/integrations/checkmk/api-reference.rst:2 +msgid "API Reference" msgstr "" -#: ../system/integrations/slack.rst:34 +#: ../system/integrations/checkmk/api-reference.rst:4 msgid "" -"This will give you further options, as you can see e.g. escalating tickets " -"that are assigned to an agent that's e.g. absent. You can interact faster, " -"as you might see problems earlier (or even before the problem gets one)." +"For most users, :ref:`the sample scripts from the Setup Guide ` will do the job just fine. But if you want more fine-grained control" +"—for instance, to create high- and low-priority tickets for different types " +"of system events—then you'll have to customize the data those scripts send " +"to Zammad." msgstr "" -#: ../system/integrations/slack.rst:38 +#: ../system/integrations/checkmk/api-reference.rst:15 msgid "" -"If needed and wanted, you can even discuss directly about the topic before " -"sending an answer to the customer. Another possible use case would be a " -"agent monitoring new agents and their answers to tickets." +"This custom script will automatically set all tickets it creates to **high " +"priority** and **assign them to charlie@chrispresso.com**." msgstr "" -#: ../system/integrations/slack.rst:44 -msgid "Configure the Integration" +#: ../system/integrations/checkmk/api-reference.rst:32 +msgid "How Does it Work?" msgstr "" -#: ../system/integrations/slack.rst:46 +#: ../system/integrations/checkmk/api-reference.rst:34 msgid "" -"First of all, please go to your slack workspace - go to administration => " -"Manage Apps. If you don't have an app yet, you can simply add a new one - " -"just search for ``Incoming WebHooks`` and customize the app to your needs." +"There are two kinds of data you can pass to the API, both in the form of key-" +"value pairs:" msgstr "" -#: ../system/integrations/slack.rst:50 -msgid "" -"Choose (or create) the channel Zammad should post it's information to and " -"press on \"Add Incoming WebHooks integration\". If you're ready, copy the " -"provided WebHook URL and go to your Zammad installation." +#: ../system/integrations/checkmk/api-reference.rst:44 +msgid "Checkmk parameters" msgstr "" -#: ../system/integrations/slack.rst:56 +#: ../system/integrations/checkmk/api-reference.rst:38 msgid "" -"You need administrative rights on the Slack Workspace. The link to the app " -"directory is normally ``https://[workspace-name].slack.com/apps`` ." +"are required, and make up the **contents** of the resulting tickets/" +"articles. They also determine whether an event creates a new ticket or " +"updates/closes an existing one." msgstr "" -#: ../system/integrations/slack.rst:63 +#: ../system/integrations/checkmk/api-reference.rst:42 msgid "" -"To configure the slack integration, log in to Zammad and go to Integrations " -"(System) => Slack in the admin panel." +"These are the only values used in the sample scripts. **Use them as-is**; " +"technically, they can be customized, but it's hard to imagine a good reason " +"for it." msgstr "" -#: ../system/integrations/slack.rst:66 -msgid "" -"Here you can choose on what evens Zammad should post information about a " -"ticket to your Slack channel. Next you need to device what groups shall be " -"affected by this, as anybody with access to that specific Slack channel can " -"read at least parts of the ticket this might be a privacy issue, if you " -"select the wrong groups. The username is simply the name that Zammad uses as " -"display name inside the Slack chat. The channel defines the Slack channel " -"the information is being posted in. As last option, you can set a custom " -"icon for posting to slack." +#: ../system/integrations/checkmk/api-reference.rst:52 +msgid "Ticket attributes" msgstr "" -#: ../system/integrations/slack.rst:74 +#: ../system/integrations/checkmk/api-reference.rst:47 msgid "" -"When you're ready, just hit \"Submit\" and enable the integration. Zammad " -"will now post new ticket information based on the trigger you chose. Below " -"the options you have the recent log that shows the latest requests to Slack " -"for debugging if needed." +"are optional, and can be used to **adjust settings** on newly created " +"tickets (*e.g.,* set the owner, group, priority, or state)." msgstr "" -#: ../system/integrations/slack.rst:81 +#: ../system/integrations/checkmk/api-reference.rst:50 msgid "" -"If you leave the Icon URL empty, Zammad will use the Zammad logo instead. " -"The icon should be a square PNG file." +"If you want to customize your Checkmk alert script, do it with these. Simply " +"add an extra “form” option for each one (``-F \"key=value\"``) to your " +"script's ``curl`` command line, as in the example above." msgstr "" -#: ../system/integrations/slack.rst:90 -msgid "" -"The following figure shows how it will look if you choose to receive updates " -"on created and updated tickets. On every post Zammad sends to the Slack " -"channel, you can create new threads to discuss about the new article." +#: ../system/integrations/checkmk/api-reference.rst:54 +msgid "💡 **It's just an API endpoint!**" msgstr "" -#: ../system/integrations/slack.rst:96 +#: ../system/integrations/checkmk/api-reference.rst:56 msgid "" -"If you just want to keep track of soon escalating or already escalated " -"tickets, it will look the the following figure. Zammad changes the color in " -"front of the post so you can easily see the state of the ticket." +"When using Checkmk integration, messages need to be formatted in a certain " +"way, but that *doesn't mean the messages actually have to come from Checkmk*." msgstr "" -#: ../system/integrations/slack.rst:102 +#: ../system/integrations/checkmk/api-reference.rst:59 msgid "" -"If you change the state, Zammad will also put information on what state the " -"ticket gets and (if pending state) the date until it pends. You'll also " -"recognize the color codes in front of posts on slack, as they are exact the " -"same the ticket state colors you'll see in Zammad!" +"If you use another monitoring tool that's not officially supported by " +"Zammad, there's probably a way to make it work with your Checkmk callback " +"URL." msgstr "" -#: ../system/integrations/smime/index.rst:2 -msgid "S/MIME" +#: ../system/integrations/checkmk/api-reference.rst:63 +msgid "Checkmk Parameters" msgstr "" -#: ../system/integrations/smime/index.rst:11 +#: ../system/integrations/checkmk/api-reference.rst:65 msgid "" -"S/MIME is the most widely-supported method for secure email communication. " -"With S/MIME, you can exchange **signed** and **encrypted** messages with " -"others." +"When a notification is received, Zammad creates a new article containing the " +"details of the event that triggered it:" msgstr "" -#: ../system/integrations/smime/index.rst:15 -msgid "" -"is proof that a message hasn't been tampered with or sent by an impersonator." +#: ../system/integrations/checkmk/api-reference.rst:None +msgid "Checkmk article body" msgstr "" -#: ../system/integrations/smime/index.rst:17 +#: ../system/integrations/checkmk/api-reference.rst:72 msgid "" -"In other words, it guarantees a message's **integrity** and **authenticity**." +"These details come from the fields listed below, which correspond to " +"parameters provided by Checkmk (``$NOTIFY_*``)." msgstr "" -#: ../system/integrations/smime/index.rst:22 -msgid "In other words, it guarantees **privacy** and **data security**." +#: ../system/integrations/checkmk/api-reference.rst:75 +msgid "**Required fields are marked with an asterisk (\\*).**" msgstr "" -#: ../system/integrations/smime/index.rst:28 -msgid "Screencast demo of S/MIME features for both new tickets and replies" +#: ../system/integrations/checkmk/api-reference.rst:79 +msgid "event_id\\*" msgstr "" -#: ../system/integrations/smime/index.rst:28 +#: ../system/integrations/checkmk/api-reference.rst:78 msgid "" -"Once S/MIME has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " -"appear in the ticket composer." +"A unique ID for the system event. (``$NOTIFY_SERVICEPROBLEMID`` / " +"``$NOTIFY_HOSTPROBLEMID``)" msgstr "" -#: ../system/integrations/smime/index.rst:32 -msgid ":doc:`🔪 Prerequisites `" +#: ../system/integrations/checkmk/api-reference.rst:86 +msgid "host\\*" msgstr "" -#: ../system/integrations/smime/index.rst:31 +#: ../system/integrations/checkmk/api-reference.rst:82 msgid "" -"New to S/MIME? This section helps you to find certificate providers and " -"points out Limitations." +"The hostname of the system that the event originated from. " +"(``$NOTIFY_HOSTNAME``)" msgstr "" -#: ../system/integrations/smime/index.rst:35 -msgid ":doc:`📝 Manage Certificates `" +#: ../system/integrations/checkmk/api-reference.rst:85 +msgid "" +"Used to determine if a new event belongs to an existing ticket. Also used in " +"the subject line of the resulting article (“ is ”)." msgstr "" -#: ../system/integrations/smime/index.rst:35 -msgid "Add and download certificates; configure group default behaviors." +#: ../system/integrations/checkmk/api-reference.rst:96 +msgid "service" msgstr "" -#: ../system/integrations/smime/index.rst:38 -msgid ":doc:`😦 Troubleshooting `" +#: ../system/integrations/checkmk/api-reference.rst:89 +msgid "" +"The name of the service that the event originated from. " +"(``$NOTIFY_SERVICEDESC``)" msgstr "" -#: ../system/integrations/smime/index.rst:38 -msgid "Took a wrong turn? About recent logs and common issues." +#: ../system/integrations/checkmk/api-reference.rst:92 +msgid "Used to determine if a new event belongs to an existing ticket." msgstr "" -#: ../system/integrations/smime/index.rst:43 -msgid "" -"For more details on how S/MIME integration works on the agent side, see the :" -"user-docs:`user docs `." +#: ../system/integrations/checkmk/api-reference.rst:94 +#: ../system/integrations/checkmk/api-reference.rst:110 +msgid "Displayed as ``-`` when omitted." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:2 -msgid "Manage Certificates" +#: ../system/integrations/checkmk/api-reference.rst:104 +msgid "state\\*" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:4 +#: ../system/integrations/checkmk/api-reference.rst:99 msgid "" -"S/MIME is **disabled by default**. Enable it to start adding certificates." +"The current state of the service or host in question. " +"(``$NOTIFY_SERVICESTATE`` / ``$NOTIFY_HOSTSTATE``)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:10 -msgid "Dialogue to add new certificates or private keys" +#: ../system/integrations/checkmk/api-reference.rst:102 +msgid "" +"Used to detect when a ticket should be auto-closed (*i.e.,* on ``OK``/" +"``UP``). Also used in the subject line of the resulting article (“ is " +"”)." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:10 +#: ../system/integrations/checkmk/api-reference.rst:110 +msgid "text" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:107 msgid "" -"Manage certificates in the Admin Panel under **System > Integrations > S/" -"MIME**. Certificates may be pasted in as plain text or uploaded from a file." +"The output of the process that triggered the event. " +"(``$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:14 -msgid "Add Certificate Data" +#: ../system/integrations/checkmk/api-reference.rst:121 +msgid "" +"The Object Manager attribute panel displays built-in and custom\n" +"attribute names." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:36 -msgid "Add Certificate" +#: ../system/integrations/checkmk/api-reference.rst:121 +msgid "Find a complete list of ticket attributes in the Object Manager." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:17 +#: ../system/integrations/checkmk/api-reference.rst:123 msgid "" -"Import public-key certificates for both your own organization and your " -"contacts." +"Ticket attributes are entirely optional, and can be used to customize the " +"tickets that Checkmk creates. (Note that these attributes will be ignored if " +"a new event belongs to an existing ticket.)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:19 +#: ../system/integrations/checkmk/api-reference.rst:128 msgid "" -"You can also add a bunch of certificates in one go by providing a single " -"file with all relevant certificates." +"Why would you want to do this? Maybe you have only one IT guy, and all " +"system monitoring issues should be automatically assigned to him. Or, maybe " +"you're creating multiple notification rules so that database outages take " +"higher priority than disk space warnings." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:22 -msgid "🕵️ **ALWAYS verify certificates in-person or over the phone!**" +#: ../system/integrations/checkmk/api-reference.rst:135 +msgid "In most cases, you'll probably want to set one of the following:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:24 -msgid "" -"The whole point of signatures is to alert you when someone is trying to " -"pretend to be someone they're not. Never accept a certificate from someone " -"online without verifying it first." +#: ../system/integrations/checkmk/api-reference.rst:137 +msgid "group" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:28 -msgid "📇 **What about trusted certificate authorities?**" +#: ../system/integrations/checkmk/api-reference.rst:139 +msgid "state" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:30 -msgid "" -"In some cases (e.g. when dealing with large enterprises), you may be given a " -"certificate for an entire CA, rather than a single contact. Add it here to " -"trust *all* certificates issued by that CA." +#: ../system/integrations/checkmk/api-reference.rst:140 +msgid "priority" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:35 +#: ../system/integrations/checkmk/api-reference.rst:142 msgid "" -"Commercial CAs can usually be verified online. Zammad does not include a " -"list of built-in, trusted CAs." +"but in practice, you can set almost any attribute, including :doc:`custom " +"ones you created through the Object Manager `." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:57 -msgid "Add Private Key" +#: ../system/integrations/checkmk/api-reference.rst:145 +msgid "Please note that the following attributes are **not customizable**:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:39 -msgid "" -"Once you've added a public-key certificate, you can import its matching " -"private key." +#: ../system/integrations/checkmk/api-reference.rst:147 +msgid "title" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:42 -msgid "" -"Private keys are for **your own organization only**; never ask your contacts " -"for their private keys." +#: ../system/integrations/checkmk/api-reference.rst:148 +msgid "id" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:0 -msgid "" -"S/MIME integration showing configured certificates and possible issues with " -"Logging" +#: ../system/integrations/checkmk/api-reference.rst:149 +msgid "ticket number" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:50 -msgid "" -"A note is displayed on certificates with a matching private key (see line 2)." +#: ../system/integrations/checkmk/api-reference.rst:151 +msgid "created_by_id" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:52 -msgid "📤 **Certificates and private keys must be uploaded separately.**" +#: ../system/integrations/checkmk/api-reference.rst:152 +msgid "updated_by_id" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:54 -msgid "" -"If your certificate and private key are bundled together in the same file or " -"PEM block, import it twice (once using each button)." -msgstr "" - -#: ../system/integrations/smime/manage-certificates.rst:57 -msgid "Please note that bulk imports of private keys are not possible." +#: ../system/integrations/checkmk/api-reference.rst:155 +msgid "Which Values Can Be Set?" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:60 -msgid "Download Certificate Data" +#: ../system/integrations/checkmk/api-reference.rst:157 +msgid "😵 **Invalid values → unpredictable behavior**" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:62 +#: ../system/integrations/checkmk/api-reference.rst:159 msgid "" -"You can download the earlier provided certificates and private keys at any " -"time from your Zammad instance." +"If you provide a value that Zammad doesn't understand (*e.g.,* ``-F " +"\"priority=high\"``), it's not always clear what will happen. In some cases, " +"a ticket will be created with the default values instead - but in others, it " +"may not be created at all!" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:65 -msgid "" -"Please note that passphrase-protected private keys stay protected and when " -"you download them, you have to know the passphrase to use them after " -"downloading." +#: ../system/integrations/checkmk/api-reference.rst:164 +msgid "So what values does Zammad understand, then? Well, it depends..." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:73 -msgid "Dialogue to download certificates or private keys" +#: ../system/integrations/checkmk/api-reference.rst:168 +msgid "Use an email address or username:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:73 -msgid "Download stored certificates and their keys" +#: ../system/integrations/checkmk/api-reference.rst:190 +msgid "group & priority" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:78 -msgid "" -"The ticket composer will set all outgoing messages to **signed and " -"encrypted** by default (assuming the required certificates exist)." +#: ../system/integrations/checkmk/api-reference.rst:175 +msgid "Refer to the dropdown menus in the ticket pane:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:82 -msgid "These defaults can be modified on a per-group basis:" +#: ../system/integrations/checkmk/api-reference.rst:0 +msgid "See possible values for certain attributes in the ticket pane." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:None -msgid "Zammad allowing to choose the default behavior on per group basis" +#: ../system/integrations/checkmk/api-reference.rst:187 +msgid "🙅 **Ticket state CANNOT be set this way!**" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:89 +#: ../system/integrations/checkmk/api-reference.rst:189 msgid "" -"Of course, agents can always manually change these settings on each email " -"they send out." +"Why? Because ``-F \"state=...\"`` is already used :ref:`as a Checkmk " +"parameter `." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:4 -msgid "A certificate *and* private key for your own organization" +#: ../system/integrations/checkmk/api-reference.rst:222 +msgid "Everything Else" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:6 +#: ../system/integrations/checkmk/api-reference.rst:193 msgid "" -"(Use this to ✒️ **sign outgoing messages** and 🔓 **decrypt incoming " -"messages**.)" +"To set any other attributes, it helps to know your way around the :docs:" +"`rails console `. Valid values are those that you can " +"set with a string:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:9 -msgid "" -"Certificates belonging your contacts, or their issuing certificate authority " -"(CA)" +#: ../system/integrations/checkmk/api-reference.rst:218 +msgid "These values can then be passed directly to the API:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:11 -msgid "" -"(Use these to ✅ **verify incoming message signatures** and 🔒 **encrypt " -"outgoing messages**.)" +#: ../system/integrations/checkmk/index.rst:16 +msgid "How does it work?" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:14 -msgid "🙋 **I'm new to S/MIME. Where can I get a certificate?**" +#: ../system/integrations/checkmk/index.rst:2 +msgid "Checkmk" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:16 +#: ../system/integrations/checkmk/index.rst:4 msgid "" -"The easiest way to get certificates is to buy an annual subscription through " -"a commercial CA, such as:" +"`Checkmk `_ is a powerful IT monitoring tool that can " +"send real-time status alerts to Zammad via email or REST API. Set these " +"alerts up in Checkmk, and Zammad will automatically create, update, and " +"close tickets based on the health of your system:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:19 -msgid "" -"`Sectigo (formerly Comodo) `_" +#: ../system/integrations/checkmk/index.rst:14 +msgid "Screenshot of ticket created by Checkmk notifications" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:20 -msgid "`Secorio `_" +#: ../system/integrations/checkmk/index.rst:14 +msgid "Multiple alerts, same ticket." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:21 -msgid "`GlobalSign `_" +#: ../system/integrations/checkmk/setup-guide.rst:2 +msgid "Setup Guide" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:23 -msgid "(Zammad is not affiliated with these CAs in any way.)" +#: ../system/integrations/checkmk/setup-guide.rst:4 +msgid "" +"Whenever the Checkmk integration is enabled, Zammad listens for messages on " +"its API and over email. As long as those messages follow the required " +"format, Zammad will create new tickets (or find and update existing ones) " +"based on the message contents." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:25 +#: ../system/integrations/checkmk/setup-guide.rst:10 msgid "" -"You can also generate your own self-signed certificates, but the process is " -"complicated and usually 🙅 **involves extra work for your contacts**." +"That means that “setting up Checkmk integration” is simply a matter of " +"**adding configuration to your Checkmk site**: telling it when to send these " +"messages and what to say. To do that, you'll need to create a new " +"**notification rule** (see `Checkmk's official docs `_ for help with that)." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:29 +#: ../system/integrations/checkmk/setup-guide.rst:17 msgid "" -"Bear in mind that 🤝 **S/MIME only works if the other party is using it, too." -"**" +"As part of this new rule, you'll have to choose a **notification method** " +"(*i.e.,* a script to execute whenever the rule is triggered). This script " +"will be written by you (samples below), and contain the logic for sending " +"API/email messages to Zammad:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:32 -msgid "Certificate and Private Key Checks on Upload" +#: ../system/integrations/checkmk/setup-guide.rst:26 +msgid "Checkmk \"New Rule\" dialog" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:34 +#: ../system/integrations/checkmk/setup-guide.rst:26 msgid "" -"The certificate and public key validation is based on the ``X509v3`` " -"extensions." +"Find your custom scripts in the Checkmk WATO under **Notifications > New " +"Rule > Notification Method**." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:49 -msgid "Uploading a *client certificate*?" +#: ../system/integrations/checkmk/setup-guide.rst:29 +msgid "" +"Once you're done setting up your new rule, you're all set! New tickets " +"should start coming in and auto-updating any time your rule is triggered." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:41 -msgid "The following attributes are required then:" +#: ../system/integrations/checkmk/setup-guide.rst:33 +msgid "" +"(If you need help troubleshooting, be sure to check the :ref:`checkmk-recent-" +"logs`.)" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:39 -msgid "Subject Alternative Name (at least one email address has to be present)" +#: ../system/integrations/checkmk/setup-guide.rst:38 +msgid "API Alerts" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:40 -msgid "Key Usage (``Digital Signature`` and/or ``Key Encipherment``)" +#: ../system/integrations/checkmk/setup-guide.rst:40 +msgid "" +"To add these scripts in the Checkmk WATO, copy them into your Checkmk " +"installation directory and make them executable. (Be sure to replace the " +"``zammad.example.com`` callback URL with the one found in your admin panel.)" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:41 -msgid "Public key algorithm (either ``RSA`` or ``EC``)" +#: ../system/integrations/checkmk/setup-guide.rst:60 +msgid "Service notification" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:43 +#: ../system/integrations/checkmk/setup-guide.rst:46 msgid "" -"The Extended Key Usage attribute is optional. If the certificate provides " -"the named attribute, than it must contain the value ``E-mail Protection``." +"For updates on the status of the software running on your server (*e.g.,* " +"postgres)." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:46 -msgid "" -"Please note that any usable email adress has to be prefixed with ``email:`` " -"or ``rfc822:``." +#: ../system/integrations/checkmk/setup-guide.rst:75 +msgid "Host notification" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:49 -msgid "The named public key algorithms are mandatory for private keys as well." +#: ../system/integrations/checkmk/setup-guide.rst:63 +msgid "For updates on the status of the server itself." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:54 -msgid "Uploading a *CA certificate*?" +#: ../system/integrations/checkmk/setup-guide.rst:77 +msgid "🤔 **What's with all the env vars?**" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:52 +#: ../system/integrations/checkmk/setup-guide.rst:79 msgid "" -"In the case of an uploaded CA certificate, providing the value ``CA:TRUE`` " -"in the attribute *Basic Contstraints*, the previously mentioned attributes " -"are not verified." +"Whenever Checkmk runs these scripts, it needs to provide some information " +"about the event that triggered the notification. This information is passed " +"in the form of these ``$NOTIFY_*`` environment variables." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:56 +#: ../system/integrations/checkmk/setup-guide.rst:85 msgid "" -"In general, the usage of any expired (``Not After``) or not yet valid (``Not " -"Before``) certificate is denied for outgoing emails." +"You can specify additional parameters to pass to the script when you're " +"setting up your notification rule, but the ones you see here are all " +"provided by default." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:59 -msgid "Example certificate:" +#: ../system/integrations/checkmk/setup-guide.rst:90 +msgid "Email Alerts" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:85 +#: ../system/integrations/checkmk/setup-guide.rst:94 msgid "" -"Please note that Zammad will distrust senders by default. This means that " -"you're always required to provide certificate data, no matter if for signing " -"or encrypting." +"🐞 **There are known bugs** in Zammad's processing of email from Checkmk. " +"This section will be completed once they have been resolved. (Learn more at " +"GitHub issues `#2377 `_ & " +"`#2180 `_.)" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:89 -msgid "This is by design and can't be adjusted." +#: ../system/integrations/checkmk/setup-guide.rst:100 +msgid "In the meantime, we encourage you to set up API alerts instead." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:4 -msgid "" -"All of the system's latest S/MIME activity is displayed in the **Recent " -"Logs** section." +#: ../system/integrations/clearbit.rst:2 +msgid "Clearbit" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:11 -msgid "Sample entries of in- and outgoing S/MIME related emails." +#: ../system/integrations/clearbit.rst:4 +msgid "" +"With our Clearbit integration, you can easily enrich the information " +"provided by Zammad. If the customers or agents email address is known to " +"Clearbit, it will share all information it has regarding the user with " +"Zammad. Those information can include the following:" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:11 -msgid "" -"Logs report the status and details of all mail, both incoming and outgoing, " -"that used signing/verification or encryption/decryption." +#: ../system/integrations/clearbit.rst:9 +msgid "Avatar" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:14 -msgid "" -"This log does **not** include email sent by :doc:`triggers ` or the :doc:`scheduler `. For those, check your " -"``production.log``." +#: ../system/integrations/clearbit.rst:10 +msgid "Address information" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:20 -msgid "Common Issues" +#: ../system/integrations/clearbit.rst:11 +msgid "Website information" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:30 -msgid "I received a signed/encrypted email before I set up S/MIME integration" +#: ../system/integrations/clearbit.rst:12 +msgid "A BIO (as Note by default)" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:23 +#: ../system/integrations/clearbit.rst:14 msgid "" -"No problem. Once S/MIME has been enabled and the appropriate certificates " -"have been added, agents will be prompted to retry verification/decryption on " -"matching emails." +"If needed, you can add further custom objects and add mappings to them, so " +"the Clearbit information can be filled within the database. In general you " +"can get any information from Clearbit, as long as you have a mapping to an " +"Zammad object." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:0 -msgid "Screenshot of user prompt to retry decryption" +#: ../system/integrations/clearbit.rst:21 +msgid "" +"Clearbit does have a mapping of fields like LDAP and Exchange have, but does " +"not \"win\" against Zammad information. This means that if you have e.g. the " +"last name field filled in already and Clearbit has other information on " +"that, it will not be updated." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:38 -msgid "The 🔒 **Encrypt** button is disabled" +#: ../system/integrations/clearbit.rst:26 +msgid "" +"However: If let's say the last name has been set by Clearbit and Zammad " +"notices that the last name on the Clearbit source has changed, Zammad will " +"also update this value." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:33 -msgid "Have you added the recipient's certificate?" +#: ../system/integrations/clearbit.rst:33 +msgid "" +"The configuration of Clearbit is really easy and done fast! Just login to " +"your Clearbit-Account, go to \"API\" and copy the secret-API-Key." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:34 -msgid "Are you sure the recipient's certificate is valid?" +#: ../system/integrations/clearbit.rst:38 +msgid "" +"Now change to your Zammad instance, go to Integrations (System) -> Clearbit " +"in the admin panel. Paste your API-Key into the API-Key-Field and decide if " +"Zammad should create unknown Organizations automatically, if the user does " +"not have one yet (and Clearbit knows it). The shared option decides if the " +"new organizations Zammad creates with Clearbit should be shared ones." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:35 -msgid "Have you checked your ``production.log`` for more details?" +#: ../system/integrations/clearbit.rst:47 +msgid "" +"If you're unsure what option to choose, better stick with \"no\". You can " +"also learn more about :doc:`/manage/organizations/index`." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:37 +#: ../system/integrations/clearbit.rst:52 msgid "" -"If encryption doesn't work in the composer, it won't work in :doc:`triggers " -"` or the :doc:`scheduler ` either!" +"The Mapping option works similar to the mapping within the Exchange and LDAP " +"sync. You can add further mappings for e.g. custom fields if you need more " +"information that Clearbit can provide." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:42 -msgid "The ✅ **Sign** button is disabled" +#: ../system/integrations/clearbit.rst:58 +msgid "" +"If you want to add more Clearbit fields and want to learn more about " +"available fields on their API, you can take a look at their `API " +"documentation `_." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:41 +#: ../system/integrations/clearbit.rst:62 msgid "" -"Have you added **both the certificate and private key** for your " -"organization?" +"If you're happy with the above chosen Settings and your mapping, just save " +"the changes and enable Clearbit integration. Zammad will now start polling " +"the Clearbit API as users contact you." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:42 +#: ../system/integrations/clearbit.rst:68 msgid "" -"Does the email address on the certificate match the email address of the " -"agent/group composing the email?" +"Zammad does not synchronize with Clearbit on a regular basis, but on demand " +"if needed. This saves API calls." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:45 -msgid "Error: “Fingerprint already taken”" +#: ../system/integrations/clearbit.rst:73 +msgid "" +"Below the Settings and Mappings, you'll find our Integration log. You can " +"see what requests Zammad sent to Clearbit and also the APIs Response." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:45 -msgid "Are you sure you haven't added this certificate already?" +#: ../system/integrations/clearbit.rst:78 +msgid "" +"By the way, you can also view the API log on the Clearbit website - the " +"information seen is basically the same." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:48 -msgid "Error: “❌ invalid byte sequence in UTF-8”" +#: ../system/integrations/clearbit.rst:84 +msgid "Example When Adding a User" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:48 -msgid "Please ensure to provide PEM formatted certificate and keys." +#: ../system/integrations/clearbit.rst:86 +msgid "" +"To show you how fast information is added, we added a small Screencast " +"below. This shows the creation of the User Alex from Clearbit. As we already " +"set the last name of Alex to \"X\", Zammad did not update it. What Zammad " +"did was to add further information it received from Clearbit." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:49 -msgid "Did you check if the provided file is a valid certificate or key?" +#: ../system/integrations/cti/generic.rst:2 +msgid "CTI (generic)" msgstr "" -#: ../system/integrations/zabbix.rst:2 -msgid "Zabbix Integration" +#: ../system/integrations/cti/includes/introduction.include.rst:1 +msgid "" +"This integration enables Zammad to provide a caller log to your agents. With " +"this your agents can greet your customers by their name and are supported by " +"Zammad with automatically opening a new ticket dialog or the user profile." msgstr "" -#: ../system/integrations/zabbix.rst:5 +#: ../system/integrations/cti/includes/introduction.include.rst:6 msgid "" -"This guide describes how to integrate your Zabbix 5.4 installation with " -"Zammad using the Zabbix webhook feature. This guide will provide " -"instructions on setting up a media type, a user and an action in Zabbix." +"Click the toggle next to the heading to activate or deactivate this " +"integration." msgstr "" -#: ../system/integrations/zabbix.rst:12 -msgid "Zammad with enabled HTTP Token Authentication" +#: ../system/integrations/cti/includes/introduction.include.rst:9 +msgid "" +"If you want to learn more on how your agents can use this function, please " +"refer the :user-docs:`user documentation `." msgstr "" -#: ../system/integrations/zabbix.rst:13 -msgid "Zabbix version 5.4 or higher" +#: ../system/integrations/cti/includes/introduction.include.rst:14 +msgid "" +"Automatically opening new ticket dialogues or user profiles requires agent " +"to extension mapping - see more below." msgstr "" -#: ../system/integrations/zabbix.rst:16 -msgid "Setting up a Zammad" +#: ../system/integrations/cti/includes/introduction.include.rst:20 +msgid "Please note the following limitations to reduce confusion later on:" msgstr "" -#: ../system/integrations/zabbix.rst:18 -msgid "Enable **API Token Access** in Settings > System > API." +#: ../system/integrations/cti/includes/introduction.include.rst:22 +msgid "CTI integrations provide caller log functions only." msgstr "" -#: ../system/integrations/zabbix.rst:20 +#: ../system/integrations/cti/includes/introduction.include.rst:23 msgid "" -"Create a **new user** for a Zabbix alerter with an **email address** and " -"create a personal user token with **ticket.agent** permissions." +"This integration does not provide any VoIP functionalities; you can't make " +"phone calls from within Zammad." msgstr "" -#: ../system/integrations/zabbix.rst:24 -msgid "Zabbix Webhook Configuration" +#: ../system/integrations/cti/includes/introduction.include.rst:25 +msgid "" +"If your browser supports ``tel``-URLs, you can click on phone numbers for " +"automatic dialing. This requires additional software / configuration on your " +"agent's computers." msgstr "" -#: ../system/integrations/zabbix.rst:27 -msgid "Create a Global Macro" +#: ../system/integrations/cti/generic.rst:9 +#: ../system/integrations/cti/placetel.rst:14 +#: ../system/integrations/cti/sipgate.rst:14 +msgid "Please provide the following requirements:" msgstr "" -#: ../system/integrations/zabbix.rst:29 +#: ../system/integrations/cti/generic.rst:11 msgid "" -"Before setting up the **Webhook**, you need to setup the global macro " -"**{$ZABBIX.URL}**, which must contain the **URL** to the **Zabbix frontend**." +"A telephone system that supports webhooks (outbound) (best option are those " +"that allow customizing the calls)." msgstr "" -#: ../system/integrations/zabbix.rst:33 -msgid "" -"In the **Administration** > **Media types** section, import the `Template`_." +#: ../system/integrations/cti/generic.rst:13 +msgid "A unique Call-ID during the call session." msgstr "" -#: ../system/integrations/zabbix.rst:38 -msgid "Open the added **Zammad** media type and set:" +#: ../system/integrations/cti/generic.rst:14 +msgid "Call event data (both numbers and direction)." msgstr "" -#: ../system/integrations/zabbix.rst:40 -msgid "**zammad\\_access\\_token** to the your **Personal User Token**" +#: ../system/integrations/cti/generic.rst:15 +msgid "Your Zammad instance must be reachable for your telephony system." msgstr "" -#: ../system/integrations/zabbix.rst:41 +#: ../system/integrations/cti/generic.rst:17 msgid "" -"**zammad\\_url** to the **frontend URL** of your **Zammad** installation" +"If you want to learn more on what kind of requests are supported by Zammad " +"and what it expects, please consult our :docs:`CTI-API documentation `." msgstr "" -#: ../system/integrations/zabbix.rst:43 -msgid "**zammad\\_customer** to your **Zammad user email**." +#: ../system/integrations/cti/generic.rst:22 +#: ../system/integrations/cti/placetel.rst:27 +#: ../system/integrations/cti/sipgate.rst:30 +msgid "Available Settings" msgstr "" -#: ../system/integrations/zabbix.rst:44 -msgid "" -"**zammad\\_enable\\_tags** to **true** or **false** to enable or disable " -"trigger tags. **Important**: if you enable tag support, each tag is set with " -"a separate request." +#: ../system/integrations/cti/generic.rst:29 +#: ../system/integrations/cti/placetel.rst:41 +#: ../system/integrations/cti/sipgate.rst:40 +msgid "Endpoint Settings" msgstr "" -#: ../system/integrations/zabbix.rst:48 +#: ../system/integrations/cti/generic.rst:25 msgid "" -"If you want to prioritize issues according to **severity** values in Zabbix, " -"you can define mapping parameters:" -msgstr "" - -#: ../system/integrations/zabbix.rst:51 -msgid "**severity\\_**: Zammad priority ID" -msgstr "" - -#: ../system/integrations/zabbix.rst:53 -msgid "Click the **Update** button to save the **Webhook** settings." +"Zammad will list your generic CTI endpoint here. It contains a unique token " +"so ensure to keep this URL save." msgstr "" -#: ../system/integrations/zabbix.rst:55 +#: ../system/integrations/cti/generic.rst:28 msgid "" -"To receive notifications in **Zammad**, you need to create a **Zabbix user** " -"and add **Media** with the **Zammad** type." +"You'll need this endpoint for your PBX to talk to Zammad, see :docs:`CTI-API " +"documentation `." msgstr "" -#: ../system/integrations/zabbix.rst:58 +#: ../system/integrations/cti/includes/important-dont-forget-saving.include.rst:3 msgid "" -"For **Send to**: enter any text, as this value is not used, but is required." +"All following options **do not save automatically**. Always use the Save " +"button on the lower end of the integration page!" msgstr "" -#: ../system/integrations/zabbix.rst:61 -msgid "" -"For more information, use the `Zabbix documentation `_." +#: ../system/integrations/cti/generic.rst:43 +#: ../system/integrations/cti/placetel.rst:49 +#: ../system/integrations/cti/sipgate.rst:52 +msgid "Call Settings" msgstr "" -#: ../system/maintenance.rst:2 -msgid "Maintenance" +#: ../system/integrations/cti/generic.rst:39 +#: ../system/integrations/cti/placetel.rst:49 +#: ../system/integrations/cti/sipgate.rst:37 +#: ../system/integrations/cti/sipgate.rst:50 +msgid "Inbound" msgstr "" -#: ../system/maintenance.rst:4 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:1 msgid "" -"Zammad comes with a maintenance mode that you can use for e.g. updating the " -"instance or changing settings while restricting availability and functions." +"This option allows you to block specific incoming caller IDs. It allows you " +"to temporarily reject e.g. spam callers without having to contact providers " +"or PBX administrators." msgstr "" -#: ../system/maintenance.rst:13 -msgid "Mode" +#: ../system/integrations/cti/includes/inbound-calls.include.rst:11 +msgid "Caller ID to block" msgstr "" -#: ../system/maintenance.rst:8 -msgid "The mode setting allows you to enable or disable the maintenance mode." +#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 +msgid "Provide caller IDs to block in ``E.164`` format." msgstr "" -#: ../system/maintenance.rst:10 -msgid "Defaults to *off*." +#: ../system/integrations/cti/includes/inbound-calls.include.rst:8 +msgid "" +"Your telephony system has to support this function. Zammad will send a " +"``reject`` response which will cause your telephony system to hang up the " +"call. To callers this usually will feel like the line is busy." msgstr "" -#: ../system/maintenance.rst:12 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:14 msgid "" -"The maintenance mode will restrict access to administrative roles only. This " -"means agents and customers are logged off." -msgstr "" - -#: ../system/maintenance.rst:23 -msgid "@Login" -msgstr "" - -#: ../system/maintenance.rst:16 -msgid "" -"This setting allows you to provide a login message within a green banner " -"above the login screen. Click into the green banner in the settings page to " -"adjust your message. To activate the message, activate the *@Login* setting." -msgstr "" - -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing the default login message within the\n" -"settings page" -msgstr "" - -#: ../system/maintenance.rst:26 -msgid "" -"Send an informative message to **all active sessions**. This comes handy to " -"inform your agents e.g. about mayor outages or to force reloads after " -"configuration changes." -msgstr "" - -#: ../system/maintenance.rst:31 -msgid "This is the messages title (slightly bigger than the normal message)." -msgstr "" - -#: ../system/maintenance.rst:34 -msgid "The text you want to provide to your logged in sessions." -msgstr "" - -#: ../system/maintenance.rst:39 -msgid "Reload application" -msgstr "" - -#: ../system/maintenance.rst:37 -msgid "" -"Selecting this option will change the message acceptance button from *Close* " -"(with nothing happening) to *Continue session*, which forces the application " -"to reload." -msgstr "" - -#: ../system/maintenance.rst:43 -msgid "" -"If you have customers that are logged in to Zammad, they'll also be notified " -"if they're active in that moment." -msgstr "" - -#: ../system/maintenance.rst:48 -msgid "Example without reload application" +"Provide a meaningful note for your fellow administrators to remind yourself " +"why you've chosen to block the number." msgstr "" -#: ../system/maintenance.rst:52 -msgid "" -"Message setting within Zammad's admin settings without ticket reload " -"application setting." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:17 +#: ../system/integrations/cti/sipgate.rst:40 +msgid "Outbound" msgstr "" -#: ../system/maintenance.rst:0 +#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:1 msgid "" -"Screenshot showing the send message settings without ticket\n" -"reload application set" +"In many cases you may want to use a different caller ID depending on the " +"destination you're calling. This may apply due to specific connection rates " +"to other countries or because you want your customer to feel you're calling " +"from the same country." msgstr "" -#: ../system/maintenance.rst:61 ../system/maintenance.rst:85 -msgid "" -"The modal all other active sessions will see upon pressing *Send to clients*." +#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:6 +msgid "This option expects ``E.164`` number formats." msgstr "" -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing modal caused by maintenance's message\n" -"without reload application ticket" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 +msgid "Destination caller ID" msgstr "" -#: ../system/maintenance.rst:72 -msgid "Example with reload application" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:5 +msgid "The caller ID or number you're trying to call." msgstr "" -#: ../system/maintenance.rst:76 -msgid "" -"Message setting within Zammad's admin settings with ticket reload " -"application setting." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:7 +msgid "You can use wildcards for e.g. country specific outbound numbers like:" msgstr "" -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing the send message settings with ticket\n" -"reload application set" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:9 +msgid "``49*`` for Germany" msgstr "" -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing modal caused by maintenance's message\n" -"with reload application ticket" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:10 +msgid "``4930*`` for Berlin / Germany landlines" msgstr "" -#: ../system/monitoring.rst:2 -msgid "Monitoring" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 +msgid "``33*`` for France" msgstr "" -#: ../system/monitoring.rst:4 -msgid "" -"This function is only available in self hosted instances. If you use Zammad " -"in our cloud, we are monitoring the system on our own and take steps to fix " -"potential problems directly." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:15 +msgid "Set Outbound caller ID" msgstr "" -#: ../system/monitoring.rst:11 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:14 msgid "" -"On the monitoring page, you can see the current health state of Zammad under " -"\"*Current Status*\" at the bottom. This can be useful if you want to have a " -"look if everything is up and running. As an example, you could have a look " -"in the monitoring when you assume that some emails aren't processed from " -"Zammad." +"The outbound caller ID to set (the number your customer sees on his display) " +"in ``E.164`` number format." msgstr "" -#: ../system/monitoring.rst:17 -msgid "**Can't receive an email and the monitoring response is \"healthy\"?**" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 +msgid "Provide a short description for fellow administrators." msgstr "" -#: ../system/monitoring.rst:19 +#: ../system/integrations/cti/includes/generic-cti-support-note.includes.rst:3 msgid "" -"Zammad will just inform you about unprocessable emails. This is not the case " -"for oversized emails. You can adjust the maximum email size in :doc:`../" -"channels/email/settings`." +"This option requires your PBX to send a specific request to Zammad *before " +"dialing*. Please consult the :docs:`CTI API ` in case " +"you're not sure." msgstr "" -#: ../system/monitoring.rst:24 -msgid "Monitoring API" +#: ../system/integrations/cti/generic.rst:52 +#: ../system/integrations/cti/placetel.rst:54 +#: ../system/integrations/cti/sipgate.rst:59 +msgid "Other Settings" msgstr "" -#: ../system/monitoring.rst:26 +#: ../system/integrations/cti/includes/other-settings-intro.include.rst:1 msgid "" -"Beside the indication in the monitoring page, you can also use an external " -"monitoring tool to monitor Zammad's health. To request the health of Zammad, " -"you need to provide the API key (token) to the external monitoring tool. You " -"can copy the token from the \"*Current Token*\" field as well as the whole " -"API endpoint of your system (\"*Health Check*\" field), in which the API " -"token is already included." +"Below you can find all available additional settings for this CTI " +"integration. For your overview we're sorting them by appearance and " +"reference their description first." msgstr "" -#: ../system/monitoring.rst:37 -msgid "Screenshot showing Current Token and Health Check" +#: ../system/integrations/cti/includes/default-caller-id.include.rst:2 +#: ../system/integrations/cti/includes/default-caller-id.include.rst:1 +msgid "Default caller ID for outbound calls" msgstr "" -#: ../system/monitoring.rst:37 -msgid "Screenshot showing Token and Health Check" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:16 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:15 +msgid "Shown records in caller log" msgstr "" -#: ../system/monitoring.rst:39 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:2 msgid "" -"In addition to that, you can reset the auto-generated token to make sure " -"that already configured monitoring systems won't work anymore. So, please " -"use this \"*Reset*\" button only if you know what you do!" -msgstr "" - -#: ../system/monitoring.rst:44 -msgid "Example Output" -msgstr "" - -#: ../system/monitoring.rst:0 -msgid "No issues found" -msgstr "" - -#: ../system/monitoring.rst:48 ../system/monitoring.rst:60 -msgid "**Indicator in Zammad**:" -msgstr "" - -#: ../system/monitoring.rst:0 -msgid "Screenshot showing monitoring with no issues" -msgstr "" - -#: ../system/monitoring.rst:54 ../system/monitoring.rst:66 -msgid "**API response**::" -msgstr "" - -#: ../system/monitoring.rst:0 -msgid "Issues were found" -msgstr "" - -#: ../system/monitoring.rst:0 -msgid "Screenshot showing monitoring with issues" -msgstr "" - -#: ../system/objects.rst:2 -msgid "Objects" +"Allows you to set the number of shown caller log entries for all users. You " +"can choose from the following values:" msgstr "" -#: ../system/objects.rst:4 -msgid "" -"In Zammad you can add your own fields to tickets, users, organizations and " -"even groups (these are called \"objects\"). This can be useful if you need " -"to add further information to a ticket or any other object in Zammad and the " -"information doesn't fit in any existing field." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:5 +msgid "60 (default)" msgstr "" -#: ../system/objects.rst:11 -msgid "" -"Try to avoid deleting attributes (and disable them instead) as Zammad might " -"run into unexpected conditions if they are referenced somewhere." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:6 +msgid "120" msgstr "" -#: ../system/objects.rst:16 -msgid "" -"Here's an overview of object attributes. On the upper right you can add new " -"attributes. By default, there will be no custom fields - standard attributes " -"will be grayed out, you can't delete or change those. You can edit custom " -"attributes (they are displayed in black font and have a trash bin on the " -"right side) just by clicking on them." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:7 +msgid "180" msgstr "" -#: ../system/objects.rst:24 -msgid "" -"Attributes you add to Zammad, no matter if they have default values or not, " -"will not update existing information. This means a new ticket field " -"technically will be empty unless you populate it." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:8 +msgid "240" msgstr "" -#: ../system/objects.rst:28 -msgid "" -"Especially in ticket scope this also means that newly added attributes will " -"be indicated as \"changed\" to agents that view the ticket. This may " -"interfere with Zammad's tabs behavior." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:9 +msgid "300" msgstr "" -#: ../system/objects.rst:40 -msgid "Ordering Attributes" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:11 +msgid "**🥵 Potential performance issue**" msgstr "" -#: ../system/objects.rst:42 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:13 msgid "" -"Since Zammad introduced :doc:`/system/core-workflows` the need to have a " -"custom positioning for attributes has become more important than ever." +"Setting this setting higher than 60 may cause serious performance issues on " +"very busy instances. Keep in mind that this setting causes Zammad to poll " +"and send up to 300 records to *all active agent sessions* in very short time " +"periods." msgstr "" -#: ../system/objects.rst:45 -msgid "" -"To adjust the position of such an attribute, simply click on the attribute " -"entry in question, scroll down and adjust the position number. Please note " -"that you cannot change the positioning of default attributes." +#: ../system/integrations/cti/generic.rst:73 +msgid "Caller Log Filter" msgstr "" -#: ../system/objects.rst:49 +#: ../system/integrations/cti/generic.rst:55 msgid "" -"In case two attributes have the same position value, Zammad will sort " -"alphabetically by name automatically." +"This function allows you to provide call information based on e.g. queues " +"only to agents that really need the information." msgstr "" -#: ../system/objects.rst:None +#: ../system/integrations/cti/generic.rst:58 msgid "" -"Screenshot showing custom attribute entries ordered in between default ones" +"Why? If you have a team for several countries or departments, you don't want " +"to bug your agents from other departments. Leaving these options empty will " +"fallback to showing everything to everyone." msgstr "" -#: ../system/objects.rst:56 -msgid "Updating Database After Adding or Editing Attributes" +#: ../system/integrations/cti/generic.rst:64 +msgid "Destination caller ID or Queue" msgstr "" -#: ../system/objects.rst:58 +#: ../system/integrations/cti/generic.rst:63 msgid "" -"When adding or changing attributes, Zammad will not apply the changes " -"instantly, but instead shows you the changed attributes first. If you're " -"ready to go, just click on \"Update database\" to apply the changes to " -"Zammad. If you made a mistake or just want to discard your changes, click " -"\"Discard changes\"." +"This depends on your PBX and usually is either a queue ID, phone number or " +"extension." msgstr "" -#: ../system/objects.rst:64 -msgid "" -"After applying the changes with \"Update Database\", a restart of Zammad is " -"**mandatory**. If you don't perform it, you may experience unexpected " -"behavior or even errors. You may want to do this kind of configuration " -"during maintenance windows." +#: ../system/integrations/cti/generic.rst:69 +msgid "Agents" msgstr "" -#: ../system/objects.rst:72 +#: ../system/integrations/cti/generic.rst:67 msgid "" -"Changes on objects require you to update the database to apply these changes." +"Select the agents that are responsible for the group. These agents will then " +"see caller log entries and call notifications fitting to said queue." msgstr "" -#: ../system/objects.rst:75 -msgid "**🤓 Service restarts can be automated**" +#: ../system/integrations/cti/generic.rst:0 +msgid "" +"Screenshot showing the caller log filter table with pre filled sample data" msgstr "" -#: ../system/objects.rst:0 -msgid "Hosted environments automatically restart for you." +#: ../system/integrations/cti/includes/recent-logs.include.rst:6 +msgid "" +"With recent logs Zammad allows you to view the latest calls for the CTI " +"functionality. This usually comes in handy, when you're looking for errors." msgstr "" -#: ../system/objects.rst:0 +#: ../system/integrations/cti/includes/recent-logs.include.rst:0 msgid "" -"If you're using a self-hosted installation you can use :docs:`environment " -"variables `" +"Screenshot showing several incoming requests within Recent logs section." msgstr "" -#: ../system/objects.rst:82 -msgid "System Attributes" +#: ../system/integrations/cti/includes/recent-logs.include.rst:16 +msgid "I'm just here to clear floats up." msgstr "" -#: ../system/objects.rst:84 +#: ../system/integrations/cti/includes/recent-logs.include.rst:20 msgid "" -"Zammad comes with pre-configured attributes. Some of them can't be edited " -"via UI (or at all). This is required for proper operation of Zammad and not " -"a bug." -msgstr "" - -#: ../system/objects.rst:90 -msgid "Ticket State" +"By clicking on the entry of interest, Zammad will provide more details on " +"the call in question. You'll see the payload it received and also the " +"response that was sent." msgstr "" -#: ../system/objects.rst:92 +#: ../system/integrations/cti/includes/recent-logs.include.rst:0 msgid "" -"If the pre-configured states aren't enough for you or you want to change " -"them, you can do so by clicking on the cogwheel icon in the state row in the " -"ticket tab. But you should be careful when changing pre-configured states. " -"This can lead to unwanted behavior in some cases." +"Screenshot showing detailed information of a specific log entry of recent " +"logs" msgstr "" -#: ../system/objects.rst:None -msgid "Screenshot showing highlighted ticket state attribute" +#: ../system/integrations/cti/includes/recent-logs.include.rst:31 +msgid "x" msgstr "" -#: ../system/objects.rst:122 -msgid "Handling of states" +#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 +#: ../system/integrations/cti/includes/troubleshooting.include.rst:9 +msgid "My Phone page stays blank, signalling does work..." msgstr "" -#: ../system/objects.rst:102 +#: ../system/integrations/cti/includes/troubleshooting.include.rst:5 msgid "" -"In the state configuration screen, you can add new states, disable states or " -"change states." +"If you've made sure that signalling works (check Recent logs) and your " +"Caller Log still stays empty, please ensure that you only configured one CTI " +"integration version. Specifically defining more than one agent mapping on " +"the different integration variants will be the issue." msgstr "" -#: ../system/objects.rst:0 -msgid "Screenshot showing table of default ticket states" +#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 +msgid "Clear the not needed agent mapping and reload your browser page." msgstr "" -#: ../system/objects.rst:110 +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:1 msgid "" -"To add a new state, click on the \"New Ticket State\" button in the top " -"right corner. To change an existing state, simply click on the affected " -"state. This opens an edit dialog." +"By mapping your agents extension to their existing Zammad users, Zammad can " +"provide a new ticket dialog or open the user profile for the agent that " +"picks up the call." msgstr "" -#: ../system/objects.rst:114 +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:5 msgid "" -"You can also clone a state or set them to \"Default for new tickets\" or " -"\"Default for follow-ups\" by clicking on the ⁝ action button and select the " -"desired function." +"This speeds up ticket aiding, no matter if it's for existing tickets or new " +"ones!" msgstr "" -#: ../system/objects.rst:118 +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:8 msgid "" -"*Default for new tickets* means that this state is used for every newly " -"created ticket." +"To see it work from the agent's perspective, have a look on :user-docs:`user " +"documentation `." msgstr "" -#: ../system/objects.rst:121 -msgid "" -"*Default for follow-ups* means that this state is used if the ticket is re-" -"opened after it was closed." +#: ../system/integrations/cti/placetel.rst:2 +msgid "Placetel CTI" msgstr "" -#: ../system/objects.rst:171 -msgid "Ticket state in detail" +#: ../system/integrations/cti/placetel.rst:16 +msgid "You need an administrative Placetel account for your organization." msgstr "" -#: ../system/objects.rst:125 +#: ../system/integrations/cti/placetel.rst:17 +#: ../system/integrations/cti/sipgate.rst:20 msgid "" -"Below you can find a description for each field and option. Please head over " -"to the :ref:`example ` to see the edit dialog." +"Your Zammad instance must be allowed to communicate to external services." msgstr "" -#: ../system/objects.rst:129 -msgid "" -"This is the name of the state and what you and your agents are seeing when " -"choosing a state somewhere (e.g. in tickets, trigger configuration)." +#: ../system/integrations/cti/placetel.rst:18 +msgid "Placetel must be able to reach your Zammad instance." msgstr "" -#: ../system/objects.rst:137 -msgid "" -"There are different state types you can choose from. By default, Zammad " -"comes with one state per state type." +#: ../system/integrations/cti/placetel.rst:22 +msgid ":doc:`provider-configurations/placetel`" msgstr "" -#: ../system/objects.rst:140 +#: ../system/integrations/cti/placetel.rst:21 msgid "" -"**new**: for states for tickets that are new and it hasn't been worked on " -"them" +"Learn how to configure Placetel to enable Zammad and Placetel to communicate " +"with each other." msgstr "" -#: ../system/objects.rst:142 +#: ../system/integrations/cti/placetel.rst:32 msgid "" -"**open**: for states for tickets that are in progress and agents are working " -"on them" -msgstr "" - -#: ../system/objects.rst:144 -msgid "**merged**: for states for tickets that are merged with other tickets" +"The here listed endpoint settings are relevant for the :doc:`integration " +"configuration with Placetel `." msgstr "" -#: ../system/objects.rst:145 -msgid "" -"**pending reminder**: for states for tickets that are in progress and you " -"want to set a reminder. (default example: *pending reminder*)" +#: ../system/integrations/cti/placetel.rst:37 +#: ../system/integrations/i-doit.rst:53 +msgid "Endpoint" msgstr "" -#: ../system/objects.rst:147 +#: ../system/integrations/cti/placetel.rst:36 msgid "" -"**pending action**: for states for tickets that are waiting for a specified " -"time and then change their state (default example: *pending close*)" +"This endpoint will be required for the Zammad integration within the " +"Placetel web interface." msgstr "" -#: ../system/objects.rst:150 -msgid "" -"**closed**: for states for tickets that are finished and do not need to be " -"processed further" +#: ../system/integrations/cti/placetel.rst:41 +msgid "API Token" msgstr "" -#: ../system/objects.rst:153 +#: ../system/integrations/cti/placetel.rst:40 msgid "" -"⚠️ Choosing the correct state type is important! If you are in doubt, have a " -"look on the default states and their types!" +"You'll receive this token within the ``Web API`` menu. Make sure to copy " +"this value, it's only shown once!" msgstr "" -#: ../system/objects.rst:158 -msgid "Ignore escalation" +#: ../system/integrations/cti/placetel.rst:71 +#: ../system/integrations/cti/sipgate.rst:77 +msgid "Phone Extension to Agent Mapping" msgstr "" -#: ../system/objects.rst:157 -msgid "" -"Here you can define whether tickets of this state will count to escalation " -"time or not." +#: ../system/integrations/cti/placetel.rst:0 +msgid "Screenshot showing sample user mappings in between Placetel and Zammad" msgstr "" -#: ../system/objects.rst:161 +#: ../system/integrations/cti/placetel.rst:64 msgid "" -"You can create a note for the state to inform other admins about the state. " -"This has no effect on tickets." +"You can find your agents Placetel username combination required within ⚙️ PBX " +"→ VoIP destinations. Within the \"Advanced settings\" section you're looking " +"for \"SIP user name\" and \"SIP server\"." msgstr "" -#: ../system/objects.rst:165 -msgid "Set the state to *active* or *inactive*." +#: ../system/integrations/cti/placetel.rst:68 +msgid "Combine these two like so: ``@``." msgstr "" -#: ../system/objects.rst:167 -msgid "" -"it is technically possible to set all states to inactive. To keep Zammad " -"working in such a case, the inactive flag of one of the states is ignored." +#: ../system/integrations/cti/placetel.rst:0 +msgid "Sample VoIP credentials for a Placetel user" msgstr "" -#: ../system/objects.rst:194 -msgid "Ticket state example" +#: ../system/integrations/cti/provider-configurations/placetel.rst:2 +msgid "Setup Placetel connection for Zammad" msgstr "" -#: ../system/objects.rst:174 +#: ../system/integrations/cti/provider-configurations/placetel.rst:6 msgid "" -"Let's assume we want to create a new state which indicates that the ticket " -"has to wait for a response of a third party (e.g. service contractor or " -"manufacturer) and we want to to be able to set a reminder." +"This configuration step requires a *full* administrative Placetel account. " +"You may receive forbidden error messages with Placetel in case your " +"permissions are not high enough." msgstr "" -#: ../system/objects.rst:178 +#: ../system/integrations/cti/provider-configurations/placetel.rst:10 msgid "" -"First we give the new state a proper name. In this example we call it " -"\"waiting for manufacturer\"." +"The following actions can be configured via the `Placetel web interface " +"`_." msgstr "" -#: ../system/objects.rst:181 -msgid "" -"As state type we choose \"pending reminder\". This indicates that the ticket " -"is still open and we can set a reminder. This reminder can be useful if our " -"manufacturer sometimes isn't responding or we want to remind him to give us " -"an answer." +#: ../system/integrations/cti/provider-configurations/placetel.rst:29 +msgid "Step 1: Activate Zammad integration" msgstr "" -#: ../system/objects.rst:186 +#: ../system/integrations/cti/provider-configurations/placetel.rst:14 msgid "" -"We choose \"no\" for \"ignore escalation\" because we want to escalate the " -"tickets even if we are waiting on the manufacturer's feedback." -msgstr "" - -#: ../system/objects.rst:189 -msgid "The **result** in the creation dialog will look like this:" +"Within Integrations, scroll down to Partner integrations and select Zammad." msgstr "" -#: ../system/objects.rst:0 -msgid "Screenshot showing ticket state creation dialog with example" +#: ../system/integrations/cti/provider-configurations/placetel.rst:17 +msgid "" +"You can alternatively filter by \"Ticket Systems\" to reduce the number of " +"entries on the page. You'll still want to look for Partner integrations. 🤓" msgstr "" -#: ../system/objects.rst:197 ../system/objects.rst:199 -msgid "Ticket Priority" +#: ../system/integrations/cti/provider-configurations/placetel.rst:21 +msgid "" +"Within the Zammad integration now press \"Activate\". A new tab ``API`` " +"becomes available - open this tab." msgstr "" -#: ../system/objects.rst:199 ../system/objects.rst:201 +#: ../system/integrations/cti/provider-configurations/placetel.rst:24 msgid "" -"If the pre-configured priorities aren't enough for you or you want to change " -"them, you can do so by clicking on the cogwheel icon in the priority row in " -"the ticket tab:" +"Now tick \"Enable Call Control / Notify API\" and paste the Placetel " +"endpoint from your Zammad instance into the field \"URL of your API " +"endpoint\". Save to apply the settings" msgstr "" -#: ../system/objects.rst:None -msgid "Screenshot showing highlighted ticket priority attribute" +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "Screencast showing how to activate the Zammad integration" msgstr "" -#: ../system/objects.rst:224 ../system/objects.rst:226 -msgid "Handling of priorities" +#: ../system/integrations/cti/provider-configurations/placetel.rst:51 +msgid "Step 2: Generate API Token for Placetel" msgstr "" -#: ../system/objects.rst:208 ../system/objects.rst:210 +#: ../system/integrations/cti/provider-configurations/placetel.rst:32 msgid "" -"In the priority configuration screen, you can add new priorities, disable " -"priorities or change priorities." +"Go back to the integrations page and scroll down to \"Web API\". Generate a " +"new API token by using the \"Create a new API token\" button." msgstr "" -#: ../system/objects.rst:0 -msgid "Screenshot showing table of default ticket priorities" +#: ../system/integrations/cti/provider-configurations/placetel.rst:37 +msgid "" +"If you already generated a token either use your existing token or reset it " +"by using above mentioned button. Placetel will ask you to conform this reset." msgstr "" -#: ../system/objects.rst:216 ../system/objects.rst:218 +#: ../system/integrations/cti/provider-configurations/placetel.rst:41 msgid "" -"To add a new priority, click on the \"New Priority\" button in the top right " -"corner. To change an existing priority, simply click on the affected " -"priority. This opens an edit dialog." +"Please keep in mind that existing API scripts may no longer work due to " +"token resets!" msgstr "" -#: ../system/objects.rst:220 ../system/objects.rst:222 +#: ../system/integrations/cti/provider-configurations/placetel.rst:44 msgid "" -"You can also clone a priority or set them to \"Default for new tickets\" by " -"clicking on the ⁝ action button and select the desired function." +"Copy the provided API token and insert it into the \"API Token\" field " +"within Zammad's Placetel integration." msgstr "" -#: ../system/objects.rst:223 ../system/objects.rst:225 +#: ../system/integrations/cti/provider-configurations/placetel.rst:47 msgid "" -"*Default for new tickets* means that this priority is used for every newly " -"created ticket." +"Apply your changes by using the \"Save\" button on the bottom of the " +"Placetel integration page and activate the Placetel integration." msgstr "" -#: ../system/objects.rst:246 ../system/objects.rst:248 -msgid "Priorities in detail" +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "" +"Screencast showing how to retrieve an API token from Placetel for Zammad" msgstr "" -#: ../system/objects.rst:227 ../system/objects.rst:229 -msgid "Below you can find a description for each field and option." +#: ../system/integrations/cti/provider-configurations/placetel.rst:73 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:77 +msgid "Step 3: Restrict the numbers to notify on" msgstr "" -#: ../system/objects.rst:230 ../system/objects.rst:232 +#: ../system/integrations/cti/provider-configurations/placetel.rst:54 msgid "" -"This is the name of the priority and what you and your agents are seeing " -"when choosing a priority somewhere (e.g. in tickets, trigger configuration)." +"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " +"the the Integrations page of the Placetel web interface, go to \"Notify " +"API\"." msgstr "" -#: ../system/objects.rst:240 ../system/objects.rst:242 -msgid "Highlight color" +#: ../system/integrations/cti/provider-configurations/placetel.rst:58 +msgid "" +"Lower on the page Placetel allows you to restrict the numbers to notify on. " +"You'll find this within the \"External routing API\" part." msgstr "" -#: ../system/objects.rst:235 ../system/objects.rst:237 +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 msgid "" -"Switch between *Low priority* (light blue), *High priority* (red) and - " -"(default). This affects the displayed color for ticket titles in overviews." +"Screenshot showing a sample selection of phone numbers to use for the " +"Placetels notify API" msgstr "" -#: ../system/objects.rst:239 ../system/objects.rst:241 -msgid "The color options are currently limited to the mentioned options." +#: ../system/integrations/cti/provider-configurations/placetel.rst:66 +msgid "" +"This menu point also provides a API request log from Placetel view. Just " +"open \"Recent responses of your API endpoint\" to learn more." msgstr "" -#: ../system/objects.rst:243 ../system/objects.rst:245 +#: ../system/integrations/cti/provider-configurations/placetel.rst:69 msgid "" -"You can create a note for the priority to inform other admins about the " -"priority. This has no effect on tickets." +"If you want to see Zammad's perspective, use the \"Recent Logs\" part from " +"within the Placetel integration page." msgstr "" -#: ../system/objects.rst:247 ../system/objects.rst:249 -msgid "Set the priority to *active* or *inactive*." +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "Screenshot showing sample log entries for Placetels API calls to Zammad" msgstr "" -#: ../system/objects/external-data-source-example.rst:2 -msgid "External Data Source" +#: ../system/integrations/cti/provider-configurations/placetel.rst:77 +msgid "Step 4 (optional): Further configurations for Placetel" msgstr "" -#: ../system/objects/external-data-source-example.rst:4 +#: ../system/integrations/cti/provider-configurations/placetel.rst:76 msgid "" -"We assume you already had a look on :doc:`types` where you can find a " -"description of the individual fields." +"If needed, you can now configure Zammad's Placetel integration in more " +"detail. You can learn more about your options here: :ref:`Placetel " +"integration settings `." msgstr "" -#: ../system/objects/external-data-source-example.rst:7 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:2 +msgid "Setup Sipgate connection for Zammad" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"To reproduce this example, choose a category you want to add a custom field, " -"click on *New Attribute* and select *External data source field* under " -"*Format*." +"Sipgate has no english web interface which is why this documentation page is " +"mixing up languages badly." msgstr "" -#: ../system/objects/external-data-source-example.rst:11 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"Our example story is to fetch data from an external product database. We " -"want to add our products to the tickets so that the products can be searched " -"and chosen from a list and also create a link to the product website." +"Please also note that the availability of API addons highly depends on your " +"package trier. Usage of sipgate.io packages *is not free*, please check " +"their `pricing page `_ before!" msgstr "" -#: ../system/objects/external-data-source-example.rst:16 -msgid "Base configuration" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:35 +msgid "Step 1: Book sipgate.io package" msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Initial steps to configure external data source object type" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:13 +msgid "Skip to step 2 if you already have the package booked!" msgstr "" -#: ../system/objects/external-data-source-example.rst:23 -#: ../system/variables.rst:85 -msgid "**Example:**" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:15 +msgid "" +"Login to an administrative Sipgate account and navigate to " +"``Accountverwaltung``. You'll see several different options depending on " +"your booked packages. Select ``Verträge & Produkte`` to continue." msgstr "" -#: ../system/objects/external-data-source-example.rst:25 -msgid "Name: *product*" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:19 +msgid "" +"Scroll down to the section ``Zusätzliche Produkte buchen`` and look for " +"``sipgate.io`` - select this product by using the ``Produkte anzeigen``-" +"Button." msgstr "" -#: ../system/objects/external-data-source-example.rst:26 -msgid "Display: *Product*" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:23 +msgid "" +"On the next page select either one of the ``sipgate.io`` packages or ``Push-" +"API Package Free``. Follow the dialogue by booking the addon. You'll be " +"returned to your contract overview and now should see the selected addon in " +"your list." msgstr "" -#: ../system/objects/external-data-source-example.rst:29 -msgid "External data source configuration" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:30 +msgid "" +"The availability for ``sipgate.io`` packages and their levels highly depends " +"on the overall account type and product you've booked with Sipgate." msgstr "" -#: ../system/objects/external-data-source-example.rst:31 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"First, enter the search URL making sure it contains ``#{search.term}`` as a " -"parameter:" +"Screencast showing the process on how to book the required sipgate.io addon" msgstr "" -#: ../system/objects/external-data-source-example.rst:34 -msgid "**Example:** ``https://dummyjson.com/products/search?q=#{search.term}``" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:52 +msgid "Step 2: Configure webhook for Zammad" msgstr "" -#: ../system/objects/external-data-source-example.rst:36 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:38 msgid "" -"After that, head down to the preview section and enter a search input for " -"the external data source." +"Within your ``Accountverwaltung`` navicate to your product ``sipgate.io``. " +"In the newly opened tab, switch from \"Clients\" to \"Webhooks\" and paste " +"the endpoint URLs from your Zammad instance like so:" msgstr "" -#: ../system/objects/external-data-source-example.rst:39 -msgid "**Example:** ``mac``" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:42 +msgid "Inbound endpoint to \"Incoming\"" msgstr "" -#: ../system/objects/external-data-source-example.rst:41 -msgid "Then you can find a preview of the response data below:" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:43 +msgid "Outbound endpoint to \"Outgoing\"" msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of JSON response based on search term" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:47 +msgid "" +"Ensure to select at least one call group or phoneline within \"Sources\". " +"Other wise Sipgate will not indicate any incoming or outgoing calls to " +"Zammad." msgstr "" -#: ../system/objects/external-data-source-example.rst:48 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"We recommend using the preview to have a look on the structure. There is a " -"top-level element called ``products``. One level below, you can find the " -"attributes ``id`` and ``title``." +"Screencast showing how to add Zammad's endpoint URLs to sipgate.ios webhook " +"configuration" msgstr "" -#: ../system/objects/external-data-source-example.rst:52 -msgid "**Search result response based on search from example:**" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:55 +msgid "" +"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " +"the Webhooks → URLs section of Sipgate you can select which *sources* " +"Sipgate should notify Zammad about in- and outgoing calls." msgstr "" -#: ../system/objects/external-data-source-example.rst:119 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:59 msgid "" -"To tell the remote system that the desired data is located below the " -"``products`` level, you have to put it in the field *Search result list key*." +"Use either specific phone lines or use the option \"Use for all phonelines " +"and groups\" to notify Zammad about all existing lines of your Sipgate " +"account." msgstr "" -#: ../system/objects/external-data-source-example.rst:122 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"After inserting ``products`` in the mentioned field, you get an extended " -"preview. You can find an additional box *Search result list* with a JSON " -"structure. This is the same response as before but stripped from the upper " -"``products`` element by the external data source." +"Screenshot showing a sample selection of phone numbers to use for the " +"Sipgates webhooks API" msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of JSON response search result list" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:68 +msgid "This section also allows you to enable a Debug log." msgstr "" -#: ../system/objects/external-data-source-example.rst:132 -msgid "" -"Now you need to provide the keys for the search result values and labels. As " -"already mentioned, we are looking for the ``id`` and the ``title`` of our " -"products. If you haven't already, it is now a good time to look at the " -"preview of the *Search result list*." +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "Screenshot showing an enabled Debug log option" msgstr "" -#: ../system/objects/external-data-source-example.rst:197 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:73 msgid "" -"After locating our two keys, we insert them in *search result value key* " -"(``id``) and in *Search result label key* (``title``)." +"After enabling you can use the Debug log section to see all sent webhook " +"calls to Zammad. You'll also can see the response." msgstr "" -#: ../system/objects/external-data-source-example.rst:200 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"Basically, we configured the external data source already and we can see a " -"table in the preview section:" -msgstr "" - -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of product table based on search term" +"Screenshot showing sample log entries for Sipgates webhook calls to Zammad" msgstr "" -#: ../system/objects/external-data-source-example.rst:208 -msgid "" -"According to our example story, now just the *Link template* is missing." +#: ../system/integrations/cti/provider-configurations/sipgate.rst:81 +msgid "Step 4 (optional): Further configurations for Sipgate" msgstr "" -#: ../system/objects/external-data-source-example.rst:210 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:80 msgid "" -"Please note that this is an optional feature. If you don't want to use such " -"links, of course you don't have to configure it." +"If needed, you can now configure Zammad's Sipgate integration in more " +"detail. You can learn more about your options here: :ref:`Sipgate " +"integration settings `." msgstr "" -#: ../system/objects/external-data-source-example.rst:213 -msgid "" -"We can add now an address where additional product information can be found." +#: ../system/integrations/cti/sipgate.rst:2 +msgid "Sipgate (sipgate.io)" msgstr "" -#: ../system/objects/external-data-source-example.rst:215 -msgid "Example: ``https://your_domain.com/q=#{ticket.product}``" +#: ../system/integrations/cti/sipgate.rst:16 +msgid "You need an administrative Sipgate account for your organization." msgstr "" -#: ../system/objects/external-data-source-example.rst:217 -msgid "In the example, the parameter means:" +#: ../system/integrations/cti/sipgate.rst:17 +msgid "" +"Zammad requires a ``sipgate.io`` addon from the feature store (please note " +"that API calls are not free with Sipgate. Rates may apply and differ from " +"account to account)." msgstr "" -#: ../system/objects/external-data-source-example.rst:219 -msgid "``#{}``: \"Frame\" for the insertion of information" +#: ../system/integrations/cti/sipgate.rst:21 +msgid "Sipgate must be able to reach your Zammad instance." msgstr "" -#: ../system/objects/external-data-source-example.rst:220 -msgid "``ticket``: object level, where you create your custom object" +#: ../system/integrations/cti/sipgate.rst:25 +msgid ":doc:`provider-configurations/sipgate`" msgstr "" -#: ../system/objects/external-data-source-example.rst:221 -msgid "``product``: name of the (custom) object" +#: ../system/integrations/cti/sipgate.rst:24 +msgid "" +"Learn how to configure Sipgate to enable Zammad and Sipgate to communicate " +"with each other." msgstr "" -#: ../system/objects/external-data-source-example.rst:223 +#: ../system/integrations/cti/sipgate.rst:33 msgid "" -"After configuring your *Link template*, there will be another column in the " -"preview. Hovering on the icons in the *Link* column will show you where it " -"forwards you." +"Below endpoint settings affect the :doc:`sipgate.io configuration `." msgstr "" -#: ../system/objects/external-data-source-example.rst:232 -msgid "" -"In our example, one of the links looks like: https://your_domain.com/q=6, " -"where the 6 is the product id." +#: ../system/integrations/cti/sipgate.rst:37 +msgid "This endpoint is required for incoming call hooks." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:40 +msgid "This endpoint is required for outgoing call hooks." msgstr "" -#: ../system/objects/external-data-source-example.rst:235 -msgid "You can find more information regarding the URL in :doc:`types`." +#: ../system/integrations/cti/sipgate.rst:0 +msgid "Screenshot showing sample user mappings in between Sipgate and Zammad" msgstr "" -#: ../system/objects/includes/adding-values-hint.include.rst:3 +#: ../system/integrations/cti/sipgate.rst:69 msgid "" -"Adding values can be tricky for first timers, don't forget to press \"➕ " -"Add\" after typing your values. Otherwise you may loose a value." +"You can find your agent's Sipgate username within ``Accountverwaltung → " +"Benutzer``. You're looking for the SIP-ID." msgstr "" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:1 -#: ../system/objects/includes/reposition-values.include.rst:1 -msgid "**↕️ This field type allows the positioning of its values ↔️**" +#: ../system/integrations/cti/sipgate.rst:0 +msgid "Sample VoIP credentials for a Sipgate user" msgstr "" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:3 -msgid "" -"In order to re-arrange the field values, first edit the field. Then you can " -"use ☰ to drag the values in question to the correct position. If you want to " -"change the layer depth, double click on ☰. With it you can cycle through the " -"available layers." +#: ../system/integrations/cti/sipgate.rst:77 +msgid "Users with several devices also have several SIP-IDs." msgstr "" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:8 -msgid "When you're ready, submit your changes to save the object attribute." +#: ../system/integrations/elasticsearch.rst:2 +msgid "Elasticsearch (SaaS)" msgstr "" -#: :0 ../system/objects/types.rst:0 +#: ../system/integrations/elasticsearch.rst:4 msgid "" -"Screencast showing how to re-position values on tree select like\n" -"fields" +"The Elasticsearch integration allows you to create a read-only user to use " +"with your favorite reporting tool (e.g. like Grafana)." msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:3 +#: ../system/integrations/elasticsearch.rst:7 msgid "" -"In order to re-arrange the field values, edit the field and scroll below the " -"values. Make sure to tick the option \"Use custom option sort\"." +"If you want to take full advantage of the Zammad reporting, have a look at " +"our :docs:`Grafana ` " +"setup page as well." msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:8 -msgid "" -"If you do not tick this field, all manual positioning you did above will be " -"lost upon saving! ☠️" +#: ../system/integrations/elasticsearch.rst:11 ../system/subscription.rst:7 +msgid "**🚧 Hosted environment specific 🚧**" msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:11 +#: ../system/integrations/elasticsearch.rst:13 msgid "" -"Now use ☰ to drag the values in question to the correct position. When " -"you're ready, submit your changes to save the object attribute." -msgstr "" - -#: :0 ../system/objects/types.rst:0 -msgid "Screencast showing how to re-position values" +"This integration is only available for Hosted setups. In order to use " +"Elasticsearch you'll need the **Plus** subscription." msgstr "" -#: ../system/objects/includes/url-template-hint.include.rst:3 +#: ../system/integrations/elasticsearch.rst:16 msgid "" -"This field allows using :ref:`URL fields (Link Templates) `." +"Self hosted users have all the control over their self hosted Elasticsearch " +"instances." msgstr "" -#: ../system/objects/permissions.rst:2 -msgid "Attribute Permissions" +#: ../system/integrations/elasticsearch.rst:None +msgid "Elasticsearch integration page on SaaS environments" msgstr "" -#: ../system/objects/permissions.rst:7 +#: ../system/integrations/elasticsearch.rst:27 msgid "" -"In the object attributes configuration you can define if a field is shown " -"and if the input in the field is mandatory, separated by different screens " -"and for different :doc:`roles/permissions `." +"Please note the following limitations of Elasticsearch access on hosted " +"environments:" msgstr "" -#: ../system/objects/permissions.rst:17 -msgid "Screenshot shows object attribute permission table" +#: ../system/integrations/elasticsearch.rst:30 +msgid "access to the Elasticsearch index is read-only access" msgstr "" -#: ../system/objects/permissions.rst:17 -msgid "" -"Some of the possible permissions and screen options for a user object " -"attribute." +#: ../system/integrations/elasticsearch.rst:31 +msgid "currently you're limited to user only" msgstr "" -#: ../system/objects/permissions.rst:19 +#: ../system/integrations/elasticsearch.rst:32 msgid "" -"Based on the object context (ticket, agent, organization, user), the " -"selectable roles (to be precise: the required permissions) and screens " -"differ. Be aware that these settings aren't affecting data creation via " -"other channels than the UI." +"Reporting tools that require to write into the indexes (like Kibana) are not " +"supported" msgstr "" -#: ../system/objects/permissions.rst:24 -msgid "" -"If you want to have further customization possibilities, you should have a " -"look at the :doc:`core workflows `." +#: ../system/integrations/elasticsearch.rst:34 +msgid "IP access restriction is currently not yet supported" msgstr "" -#: ../system/objects/permissions.rst:28 -msgid "Screens" +#: ../system/integrations/elasticsearch.rst:37 +msgid "Activating Elasticsearch Access" msgstr "" -#: ../system/objects/permissions.rst:30 +#: ../system/integrations/elasticsearch.rst:39 msgid "" -"In the table below you can find an overview about the different permissions " -"and the available screens Zammad distinguishes between." -msgstr "" - -#: ../system/objects/permissions.rst:37 -msgid "Screen" +"By default external access to your Elasticsearch index is not active. You " +"can enable the integration at any time if needed." msgstr "" -#: ../system/objects/permissions.rst:38 -msgid "Available for" +#: ../system/integrations/elasticsearch.rst:42 +msgid "" +"Please ensure to note down the password provided - you won't have access to " +"it afterwards." msgstr "" -#: ../system/objects/permissions.rst:40 -msgid "create" +#: ../system/integrations/elasticsearch.rst:None +msgid "Screencast showing activation of Elasticsearch integration" msgstr "" -#: ../system/objects/permissions.rst:41 ../system/objects/permissions.rst:52 -#: ../system/objects/permissions.rst:59 ../system/objects/permissions.rst:73 -msgid "admin.user" +#: ../system/integrations/elasticsearch.rst:51 +msgid "Connection Settings" msgstr "" -#: ../system/objects/permissions.rst:42 ../system/objects/permissions.rst:53 -#: ../system/objects/permissions.rst:60 -msgid "admin.organization" +#: ../system/integrations/elasticsearch.rst:53 +msgid "" +"This section holds the most important general information for accessing your " +"Elasticsearch indexes - such as:" msgstr "" -#: ../system/objects/permissions.rst:43 ../system/objects/permissions.rst:54 -#: ../system/objects/permissions.rst:61 -msgid "admin.group" +#: ../system/integrations/elasticsearch.rst:57 +msgid "A unique subdomain that does not tell your real instance URL." msgstr "" -#: ../system/objects/permissions.rst:44 -msgid "Creation dialog for not yet existing data" +#: ../system/integrations/elasticsearch.rst:61 +msgid "Software" msgstr "" -#: ../system/objects/permissions.rst:45 -msgid "create_middle" +#: ../system/integrations/elasticsearch.rst:60 +msgid "" +"The major version of the search index being used. This is required by some " +"Reporting tools like Grafana." msgstr "" -#: ../system/objects/permissions.rst:46 ../system/objects/permissions.rst:50 -#: ../system/objects/permissions.rst:57 ../system/objects/permissions.rst:66 -#: ../system/objects/permissions.rst:70 -msgid "ticket.customer" +#: ../system/integrations/elasticsearch.rst:64 +msgid "Authentication" msgstr "" -#: ../system/objects/permissions.rst:47 ../system/objects/permissions.rst:51 -#: ../system/objects/permissions.rst:58 ../system/objects/permissions.rst:69 -msgid "ticket.agent" +#: ../system/integrations/elasticsearch.rst:64 +msgid "The authentication type being supported. ``Basic Authentication``" msgstr "" -#: ../system/objects/permissions.rst:48 -msgid "Ticket create dialog (middle section)" +#: ../system/integrations/elasticsearch.rst:67 +msgid "Available Indexes" msgstr "" -#: ../system/objects/permissions.rst:49 -msgid "edit" +#: ../system/integrations/elasticsearch.rst:69 +msgid "" +"Within this section we're displaying the -in our opinion- most important " +"indexes for a Zammad instance." msgstr "" -#: ../system/objects/permissions.rst:55 -msgid "Editing dialog for already existing data" +#: ../system/integrations/elasticsearch.rst:72 +msgid "" +"If you require all indexes or our listing is not good enough for you, point " +"your browser to the URL we're providing and append ``/_aliases?" +"pretty=true``. The result should look like this: ``https://.zammad.com/" +"_aliases?pretty=true``." msgstr "" -#: ../system/objects/permissions.rst:56 -msgid "view" +#: ../system/integrations/elasticsearch.rst:77 +msgid "" +"Your browser will automatically ask for your credentials - you'll then see " +"something like this:" msgstr "" -#: ../system/objects/permissions.rst:62 -msgid "View-only dialog for already existing data" +#: ../system/integrations/elasticsearch.rst:125 +msgid "Credentials" msgstr "" -#: ../system/objects/permissions.rst:64 -msgid "(e.g. user or organization from search)" +#: ../system/integrations/elasticsearch.rst:127 +msgid "" +"Within this section Zammad displays your available users. The password is " +"provided once (upon activation) and cannot be retrieved after that." msgstr "" -#: ../system/objects/permissions.rst:65 -msgid "signup" +#: ../system/integrations/elasticsearch.rst:131 +msgid "" +"If you need to change or reset your Elasticsearch user password, use the " +"\"Reset password\" button in the credentials table. Doing so creates a brand " +"new password for the account in question. This change is immediate, keep in " +"mind that this may affect third party tools connected to your instance." msgstr "" -#: ../system/objects/permissions.rst:67 -msgid "Sign-up screen for new customers" +#: ../system/integrations/exchange.rst:2 +msgid "Exchange" msgstr "" -#: ../system/objects/permissions.rst:68 -msgid "invite_customer" +#: ../system/integrations/exchange.rst:4 +msgid "" +"With Zammad's Exchange integration, you can easily use existing address " +"books without having to update more than one source." msgstr "" -#: ../system/objects/permissions.rst:71 +#: ../system/integrations/exchange.rst:7 msgid "" -"Customer invitation screen (from :doc:`First Steps ` area)" +"However, you should refrain from syncing all addresses, as the results may " +"not be what you expect (Exchange collects huge amounts of addresses). A " +"central address book of your company to sync makes more sense, as you can " +"ensure that Zammad gets only the data you need and want. Apart from this, it " +"is even not possible to sync the Global Address List (GAL) of your Exchange " +"system with Zammad." msgstr "" -#: ../system/objects/permissions.rst:72 -msgid "invite_agent" +#: ../system/integrations/exchange.rst:16 +msgid "" +"**Exchange and LDAP:** The exchange sync can be overruled by Zammad's LDAP " +"integration. If you have the same users in both sources, the LDAP version " +"will always be Zammad's pick." msgstr "" -#: ../system/objects/permissions.rst:74 +#: ../system/integrations/exchange.rst:19 msgid "" -"Agent invitation screen (from :doc:`First Steps ` area)" +"**One way sync:** the Exchange sync is one way. Exchange => Zammad. Changes " +"to your users inside of Zammad might be overwritten by the Exchange sync." msgstr "" -#: ../system/objects/permissions.rst:78 -msgid "Screen Options" +#: ../system/integrations/exchange.rst:24 +msgid "" +"To configure Exchange integration, simply go to the System > Integrations > " +"Exchange in the admin panel. Press \"change\" and follow the wizard for " +"adding the needed Exchange information to Zammad. On the last two steps " +"Zammad will ask you for the address book(s) and your desired attribute " +"mapping. By default, Zammad only maps email address, first- and lastname. " +"Technically, you can map any Exchange object to a Zammad user object (this " +"also works for custom objects!)." msgstr "" -#: ../system/objects/permissions.rst:80 +#: ../system/integrations/exchange.rst:35 msgid "" -"For the different screens you can select \"show\" and \"required\" options." +"If the SSL verification fails while connecting to Exchange, Zammad will ask " +"you to turn it off temporarily." msgstr "" -#: ../system/objects/permissions.rst:82 -msgid "**shown:** Show (check) or hide (uncheck) a field." +#: ../system/integrations/exchange.rst:38 +msgid "" +"Please be aware that **turning off SSL verification is a security risk**. It " +"should only be used temporarily or for testing purposes. If turned off, " +"there is no verification of the certificate, which means that every " +"presented certificate will be accepted." msgstr "" -#: ../system/objects/permissions.rst:83 +#: ../system/integrations/exchange.rst:43 msgid "" -"**required:** Set a field to mandatory (check). Forces users (via UI and " -"API) to populate the field." -msgstr "" - -#: ../system/objects/types.rst:7 -msgid "Example external data source" +"After pressing Continue, Zammad will check if the configuration is okay. You " +"can then enable Exchange and start your first sync. The sync will then run " +"hourly - if you need to change mappings or the address book(s), you can " +"change the configuration at any time." msgstr "" -#: ../system/objects/types.rst:2 -msgid "Attribute types" +#: ../system/integrations/exchange.rst:50 +msgid "" +"After the sync has finished, you can find the new Exchange contacts under " +"\"Users\". Zammad integrates them just as normal users." msgstr "" -#: ../system/objects/types.rst:4 +#: ../system/integrations/exchange.rst:55 msgid "" -"When adding a new object attribute, you can choose between the following " -"attribute types." +"In some cases you might see unique IDs as \"Login\" instead of the email " +"address. This is normal and doesn't affect the login or email mapping for " +"that entry." msgstr "" -#: ../system/objects/types.rst:14 +#: ../system/integrations/github.rst:4 msgid "" -"You cannot change the attribute format / type as soon as it is applied. If " -"you no longer need an object attribute, consider disabling it instead of " -"removing." +"Use GitHub integration to track GitHub issues directly within Zammad " +"tickets. Add issue hyperlinks and get a live summary of metadata like status " +"(open/closed), assignee, labels, and more." msgstr "" -#: ../system/objects/types.rst:18 -msgid "**What about the translation of my attributes?**" +#: ../system/integrations/github.rst:8 +msgid "Please note that our GitHub integration does not support pull requests." msgstr "" -#: ../system/objects/types.rst:20 -msgid "" -"For some attribute types you can decide if they should be translatable or " -"not. To be precise, it works only for the selectable fields because the " -"possible choices are known and limited. For the following attribute types, " -"you can set the translatable flag:" +#: ../system/integrations/github.rst:None +msgid "Integration page for GitHub" msgstr "" -#: ../system/objects/types.rst:25 -msgid "*Boolean field*" +#: ../system/integrations/github.rst:18 +msgid "" +"In your GitHub settings, create a new API token under **Developer settings > " +"Personal access tokens > Generate new token**. Leave the **Scopes** section " +"empty." msgstr "" -#: ../system/objects/types.rst:26 -msgid "*Single selection field*" +#: ../system/integrations/github.rst:0 ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to create a new API token" msgstr "" -#: ../system/objects/types.rst:27 -msgid "*Multiple selection field*" +#: ../system/integrations/github.rst:27 +msgid "Create a new API key with no scopes/privileges." msgstr "" -#: ../system/objects/types.rst:28 -msgid "*Single tree selection field*" +#: ../system/integrations/github.rst:29 +msgid "🔒 **Will this work for private repos?**" msgstr "" -#: ../system/objects/types.rst:29 -msgid "*Multiple tree selection field*" +#: ../system/integrations/github.rst:31 +msgid "" +"No. To link private repo issues, **use the** ``repo`` **scope instead**. " +"Bear in mind that the resulting token will have `lots of permissions that it " +"doesn't actually need `_, which presents a security risk if your token ever falls into " +"the wrong hands." msgstr "" -#: ../system/objects/types.rst:31 +#: ../system/integrations/github.rst:37 msgid "" -"For these types, you can find an additional field *Translate field contents*:" +"Unfortunately, because of how GitHub's OAuth token scopes are set up, this " +"is the only way to link issues on private repos." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Screenshot showing translatable attribute types" +#: ../system/integrations/github.rst:40 +msgid "Enter your new API token in Zammad and enable GitHub integration." msgstr "" -#: ../system/objects/types.rst:38 -msgid "Screenshot with example of translatable attribute type" +#: ../system/integrations/github.rst:0 +msgid "Screencast showing how to configure Zammad's GitHub integration" msgstr "" -#: ../system/objects/types.rst:45 -msgid "Boolean field" +#: ../system/integrations/github.rst:47 +msgid "" +"Use the default API endpoint (``https://api.github.com/graphql``) unless " +"you're using GitHub Enterprise Server." msgstr "" -#: ../system/objects/types.rst:41 +#: ../system/integrations/github.rst:50 msgid "" -"Provides a drop-down field with display values for ``true`` and ``false``. " -"Setting a default is mandatory." +"Once completed, a new GitHub issues tab will appear in the ticket pane. 🎉" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Boolean fields" +#: ../system/integrations/github.rst:59 ../system/integrations/gitlab.rst:52 +msgid "Token verification is taking a long time" msgstr "" -#: ../system/objects/types.rst:55 -msgid "Date field" +#: ../system/integrations/github.rst:56 ../system/integrations/gitlab.rst:49 +msgid "" +"Slight delays are normal (<2 min.), especially for systems under heavy load." msgstr "" -#: ../system/objects/types.rst:48 -msgid "Provides a date picker field and does not allow default values." +#: ../system/integrations/github.rst:58 +msgid "" +"Self-hosted administrators, please check your network settings to ensure " +"that your Zammad server can reach ``api.github.com``." msgstr "" -#: ../system/objects/types.rst:52 -msgid "Default time diff (hours)" +#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 +msgid "I reloaded the page and now the API token is gone" msgstr "" -#: ../system/objects/types.rst:51 +#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 msgid "" -"This setting helps the user by highlighting the day from now plus the " -"provided value. It *does not* pre-fill the field." -msgstr "" - -#: ../system/objects/types.rst:0 -msgid "Available settings for Date fields" +"This may indicate that Zammad is still verifying your API token. Try " +"reloading the page again in a couple minutes." msgstr "" -#: ../system/objects/types.rst:73 -msgid "Date & time field" +#: ../system/integrations/gitlab.rst:2 +msgid "GitLab" msgstr "" -#: ../system/objects/types.rst:58 -msgid "Provides a date and time picker – does not allow default values" +#: ../system/integrations/gitlab.rst:4 +msgid "" +"Use GitLab integration to track GitLab issues directly within Zammad " +"tickets. Add issue hyperlinks and get a live summary of metadata like status " +"(open/closed), assignee, labels, and more." msgstr "" -#: ../system/objects/types.rst:62 -msgid "Allow future" +#: ../system/integrations/gitlab.rst:8 +msgid "" +"Please note that our GitLab integration does not support merge requests." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Forbid dates and times in the future." +#: ../system/integrations/gitlab.rst:None +msgid "Integration page for GitLab" msgstr "" -#: ../system/objects/types.rst:66 -msgid "Allow past" +#: ../system/integrations/gitlab.rst:18 +msgid "" +"In your GitLab preferences, create a new API token under **Access Tokens**." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Forbid dates and times in the past." +#: ../system/integrations/gitlab.rst:20 +msgid "Under **Select scopes**, choose ``read_api`` only." msgstr "" -#: ../system/objects/types.rst:70 -msgid "Default time diff (minutes)" +#: ../system/integrations/gitlab.rst:27 +msgid "🔒 **If you wish to link issues on any private repos...**" msgstr "" -#: ../system/objects/types.rst:69 -msgid "" -"This setting helps the user by highlighting the day from now plus the " -"provided value. It does not pre-fill the field." +#: ../system/integrations/gitlab.rst:29 +msgid "Your API token must belong to an account with access to those repos." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Date & time fields" +#: ../system/integrations/gitlab.rst:31 +msgid "Enter your new API token in Zammad and enable GitLab integration." msgstr "" -#: ../system/objects/types.rst:86 -msgid "Integer field" +#: ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to configure Zammad's GitLab integration" msgstr "" -#: ../system/objects/types.rst:76 +#: ../system/integrations/gitlab.rst:40 msgid "" -"Provides an input field that allows integer usage only. You may define a " -"default value. You cannot enforce comma separation." +"Use the default API endpoint (``https://gitlab.com/api/graphql``) unless " +"you're a self-hosted GitLab user." msgstr "" -#: ../system/objects/types.rst:80 -msgid "Minimal" +#: ../system/integrations/gitlab.rst:43 +msgid "" +"Once completed, a new GitLab issues tab will appear in the ticket pane. 🎉" msgstr "" -#: ../system/objects/types.rst:80 -msgid "The minimal value the field accepts." +#: ../system/integrations/gitlab.rst:51 +msgid "" +"Self-hosted administrators, please check your network settings to ensure " +"that your Zammad server can reach ``gitlab.com``." msgstr "" -#: ../system/objects/types.rst:83 -msgid "Maximal" +#: ../system/integrations/i-doit.rst:2 +msgid "i-doit" msgstr "" -#: ../system/objects/types.rst:83 -msgid "The maximum value the field accepts." +#: ../system/integrations/i-doit.rst:4 +msgid "" +"`i-doit `_ is an open-source **configuration " +"management database** - in other words, a tool for keeping tabs on every " +"single piece of your physical and digital infrastructure, from network " +"equipment to virtual machines on down to the faceplates on your rack shelves " +"and more." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Integer fields" +#: ../system/integrations/i-doit.rst:10 +msgid "" +"What's that got to do with Zammad? Well, if you used tickets to track issues " +"with all that hardware, you might start wishing there was a way they could " +"talk to each other." msgstr "" -#: ../system/objects/types.rst:99 -msgid "Multiple selection field" +#: ../system/integrations/i-doit.rst:14 +msgid "Zammad gives you two:" msgstr "" -#: ../system/objects/types.rst:89 -msgid "" -"Provides a selection field that allows the selection of one or more out of " -"several. This field does allow setting a default value." +#: ../system/integrations/i-doit.rst:17 +msgid "1. Add i-doit Links to Zammad Tickets" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Multiple selection fields" +#: ../system/integrations/i-doit.rst:20 ../system/integrations/i-doit.rst:80 +msgid "What Users See" msgstr "" -#: ../system/objects/types.rst:112 -msgid "Single selection field" +#: ../system/integrations/i-doit.rst:26 +msgid "i-doit integration in Zammad's ticket pane" msgstr "" -#: ../system/objects/types.rst:102 +#: ../system/integrations/i-doit.rst:26 msgid "" -"Provides a drop-down field that allows selection of one value out of " -"several. This field does allow setting a default value." +"The i-doit integration will appear under a new 🖨 tab in the ticket pane." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Single selection fields" +#: ../system/integrations/i-doit.rst:28 +msgid "" +"i-doit integration puts a new tab in Zammad's ticket pane where you can add " +"links to existing i-doit devices for easy reference. (See our :user-docs:" +"`user documentation ` to learn " +"how it works in practice)." msgstr "" -#: ../system/objects/types.rst:142 -msgid "Textarea field" +#: ../system/integrations/i-doit.rst:36 ../system/integrations/i-doit.rst:93 +msgid "How to Set it Up" msgstr "" -#: ../system/objects/types.rst:115 +#: ../system/integrations/i-doit.rst:38 msgid "" -"Provides a text area input field (multiple lines) and thus allows e.g. new " -"lines. You can set a default field value." +"It requires i-doit's `API Add-on `_. Make sure to have it properly set up. Use the following setting:" msgstr "" -#: ../system/objects/types.rst:120 -msgid "" -"Please note that this field *does not* support text formatting or HTML " -"content (rich text)." +#: ../system/integrations/i-doit.rst:42 +msgid "Active: ``Yes``" msgstr "" -#: ../system/objects/types.rst:123 -msgid "**🥵 This field can consume a lot of visual space**" +#: ../system/integrations/i-doit.rst:43 +msgid "Enforce authentication by username and password: ``No``" msgstr "" -#: ../system/objects/types.rst:125 +#: ../system/integrations/i-doit.rst:45 msgid "" -"Depending on where you use this field type, it may use a lot of visual space " -"if you provide a lot of text. This may be an issue to work with." +"To set it up, enable the integration in the Zammad admin panel under " +"**System > Integrations > i-doit**:" msgstr "" -#: ../system/objects/types.rst:130 -msgid "Default" +#: ../system/integrations/i-doit.rst:None +msgid "i-doit settings within the integration pages" msgstr "" -#: ../system/objects/types.rst:129 -msgid "" -"The here provided text will be shown within the text area field or new data " -"sets." +#: ../system/integrations/i-doit.rst:53 +msgid "The root URL of your i-doit installation." msgstr "" -#: ../system/objects/types.rst:134 ../system/objects/types.rst:160 -msgid "Maxlength" +#: ../system/integrations/i-doit.rst:62 +msgid "API token" msgstr "" -#: ../system/objects/types.rst:0 ../system/objects/types.rst:160 -msgid "You can pick the maximum length of the field." +#: ../system/integrations/i-doit.rst:56 +msgid "" +"Found in the i-doit admin panel under **Interfaces / external data > JSON-" +"RPC API > Common Settings**." msgstr "" -#: ../system/objects/types.rst:0 -msgid "The default length of this object is ``500``." +#: ../system/integrations/i-doit.rst:0 +msgid "i-doit administration interface with API configuration" msgstr "" -#: ../system/objects/types.rst:139 -msgid "Rows" +#: ../system/integrations/i-doit.rst:67 +msgid "Client ID" msgstr "" -#: ../system/objects/types.rst:0 -msgid "" -"Change the number of rows to dislay so that you can use only the space you " -"really need." +#: ../system/integrations/i-doit.rst:65 +msgid "A unique name to identify Zammad within i-doit." msgstr "" -#: ../system/objects/types.rst:0 -msgid "The default number of rows is ``4``." +#: ../system/integrations/i-doit.rst:67 +msgid "(Zammad does not require you to enter a value here, but i-doit might!)" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Textarea fields" +#: ../system/integrations/i-doit.rst:70 +msgid "" +"Here you can decide if the certificate of your i-doit system has to be " +"verified or not. In case you are using custom certificates, please have a " +"look at :doc:`how to add them to Zammad `." msgstr "" -#: ../system/objects/types.rst:165 -msgid "Text field" +#: ../system/integrations/i-doit.rst:77 +msgid "2. List / Create Zammad Tickets in i-doit" msgstr "" -#: ../system/objects/types.rst:145 -msgid "Provides a text field (one line) and allows choosing a default value." +#: ../system/integrations/i-doit.rst:None +msgid "Zammad integration in i-doit's device view" msgstr "" -#: ../system/objects/types.rst:148 +#: ../system/integrations/i-doit.rst:86 msgid "" -"Defines the type of the input field. This allows e.g. your browser to ensure " -"that you provide the specific type." +"i-doit's ticket system integration gives you a way to see all the tickets " +"for a given device without ever leaving i-doit. (See our :user-docs:`user " +"documentation ` to learn how it " +"works in practice)." msgstr "" -#: ../system/objects/types.rst:152 -msgid "Currently available:" +#: ../system/integrations/i-doit.rst:95 +msgid "" +"Enable this integration in the i-doit admin panel under **Interfaces / " +"external data > Trouble Ticket System (TTS) > Configuration**:" msgstr "" -#: ../system/objects/types.rst:155 -msgid "Phone" +#: ../system/integrations/i-doit.rst:None +msgid "i-doit administration interface with TTS configuration" msgstr "" -#: ../system/objects/types.rst:156 -msgid "Text" +#: ../system/integrations/i-doit.rst:104 +msgid "TTS-Type" msgstr "" -#: ../system/objects/types.rst:157 -msgid "Url *(URL fields disable link-template availability)*" +#: ../system/integrations/i-doit.rst:104 +msgid "``Zammad``" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Text fields" +#: ../system/integrations/i-doit.rst:115 +msgid "Username / Password" msgstr "" -#: ../system/objects/types.rst:174 -msgid "Single tree selection field" +#: ../system/integrations/i-doit.rst:107 +msgid "Login credentials for a Zammad agent." msgstr "" -#: ../system/objects/types.rst:168 +#: ../system/integrations/i-doit.rst:109 msgid "" -"Provides a select-like field with up to 6 layers of options. Does not allow " -"setting a default value." +"This agent must have **read permission** for all :doc:`groups ` that plan on using the i-doit integration." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Tree Select fields" +#: ../system/integrations/i-doit.rst:113 +msgid "" +"You may even wish to create a dedicated agent account just for this " +"integration (otherwise, if the agent ever changes her password, you will " +"have to remember to update it here)." msgstr "" -#: ../system/objects/types.rst:183 -msgid "Multiple tree selection field" +#: ../system/integrations/i-doit.rst:117 +msgid "URL incl. protocol" msgstr "" -#: ../system/objects/types.rst:177 -msgid "" -"Provides a select-like field with up to 6 layers of options allowing the " -"selection of multiple values. Does not allow setting a default value." +#: ../system/integrations/i-doit.rst:118 +msgid "``https://your.zammad.domain``" msgstr "" -#: ../system/objects/types.rst:302 -msgid "External Data Source field" +#: ../system/integrations/index.rst:2 +msgid "Integrations" msgstr "" -#: ../system/objects/types.rst:186 +#: ../system/integrations/index.rst:4 msgid "" -"Provides a searchable field which fetches data from an external system. This " -"can be useful if you have data outside of Zammad and don't want to maintain " -"both data sources." +"Zammad offers numerous integrations that add rich features to your instance." msgstr "" -#: ../system/objects/types.rst:190 -msgid "The feature works as follows:" +#: ../system/integrations/index.rst:6 +msgid "We're still working on this part of our documentation, stay tight!" msgstr "" -#: ../system/objects/types.rst:192 -msgid "" -"Zammad sends a query with a search string (free text from agent or based on " -"a variable) in a pre-defined format (\"Search URL\") to an external system." +#: ../system/integrations/index.rst:10 +msgid "Integrations for Phone Systems" msgstr "" -#: ../system/objects/types.rst:195 +#: ../system/integrations/index.rst:14 msgid "" -"This external system searches for matches and provides a response as a JSON " -"structure to Zammad." +"Your VoIP provider or telephony system is not listed? Possibly your provider " +"supports Zammad by using the generic CTI - if you're unsure ask your " +"provider." msgstr "" -#: ../system/objects/types.rst:197 +#: ../system/integrations/index.rst:18 msgid "" -"Zammad just looks for the defined list and value keys, reads the content and " -"displays the value to the user. There is no search on Zammad side." +"Provider does not support Zammad? Consider creating a `feature request in " +"the Zammad Community `_." msgstr "" -#: ../system/objects/types.rst:201 -msgid "" -"The usage of a PostgreSQL database for Zammad is required. In any other " -"case, Zammad will hide the external data source type and you are not able to " -"use it. If you want to use this feature, consider to :docs:`migrate your " -"database `." +#: ../system/integrations/index.rst:31 +msgid "Integrations for Authentication and Customers" msgstr "" -#: ../system/objects/types.rst:205 -msgid "Currently, only ``GET`` is supported as request method." +#: ../system/integrations/index.rst:44 +msgid "Integrations for Monitoring Systems" msgstr "" -#: ../system/objects/types.rst:206 -msgid "" -"The data structure must be in JSON format and provide the objects in an " -"array." +#: ../system/integrations/index.rst:46 +msgid "This section currently misses the following integrations:" msgstr "" -#: ../system/objects/types.rst:208 -msgid "" -"The endpoint for the external data source has to support search. On Zammad " -"side, there is no search/logic implemented; however, you can define the " -"output key and value based on the result(s) from the response (which " -"provides already filtered content based on the search)." +#: ../system/integrations/index.rst:48 +msgid "Icinga" msgstr "" -#: ../system/objects/types.rst:212 -msgid "" -"If you receive more results as expected, your external data source search " -"may not work properly or the structure of the URL is not correct. You should " -"get in touch with a responsible person from the external system." +#: ../system/integrations/index.rst:49 +msgid "Monit" msgstr "" -#: ../system/objects/types.rst:217 -msgid "" -"Please have a look :doc:`at our example `, where you can find a possible configuration for a public " -"dummy endpoint." +#: ../system/integrations/index.rst:50 +msgid "Nagios" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for external data source fields" +#: ../system/integrations/index.rst:60 +msgid "Integrations for Issue Trackers" msgstr "" -#: ../system/objects/types.rst:242 -msgid "Search URL" +#: ../system/integrations/index.rst:70 +msgid "Other Integrations" msgstr "" -#: ../system/objects/types.rst:227 +#: ../system/integrations/index.rst:72 msgid "" -"Set your endpoint where Zammad fetches the data. Please make sure to include " -"a valid search :doc:`variable <../variables>` as an URL parameter. Example " -"for a free text search at user input: ``#{search.term}``" +"This section will hold any other integration that can't be grouped up (yet)." msgstr "" -#: ../system/objects/types.rst:232 -msgid "" -"If in doubt, ask the responsible person for the external data source how " -"they expect the strucuture of the URL." +#: ../system/integrations/ldap/index.rst:2 +msgid "LDAP / Active Directory" msgstr "" -#: ../system/objects/types.rst:236 +#: ../system/integrations/ldap/index.rst:4 msgid "" -"Depending on your search variable, the preview might work or not. The reason " -"is that the context might not be available and it is no bug." +"Zammad comes with a powerful LDAP integration that allows you to have a " +"single source of truth. By this you reduce the number of login credentials " +"your user has to remember." msgstr "" -#: ../system/objects/types.rst:239 +#: ../system/integrations/ldap/index.rst:10 msgid "" -"Please also make sure to use a variable which is available in your object " -"context. For example you won't be able to search for a ticket in a user " -"object context." -msgstr "" - -#: ../system/objects/types.rst:252 -msgid "SSL Verification" +"The LDAP source is also a perfect candidate for Zammad's :docs:`Kerberos " +"Single Sign-On ` but also works as addition " +"to other :doc:`/settings/security/third-party`." msgstr "" -#: ../system/objects/types.rst:245 -msgid "Here you can switch the SSL verification to no." +#: ../system/integrations/ldap/index.rst:None +msgid "Zammands LDAP management page" msgstr "" -#: ../system/objects/types.rst:249 -msgid "" -"If your external data source system is using self signed certificates, " -"please have a look :doc:`here ` for " -"further information about how to handle them in Zammad, so you can keep the " -"SSL verification activated." +#: ../system/integrations/ldap/index.rst:25 +msgid "📝 :doc:`manage`" msgstr "" -#: ../system/objects/types.rst:258 -msgid "HTTP Authentication" +#: ../system/integrations/ldap/index.rst:25 +msgid "Add, modify, remove or re-arrange your LDAP-Sources as needed." msgstr "" -#: ../system/objects/types.rst:255 -msgid "" -"If your external data source requires an authentication, you can set it " -"here. You can leave it empty or choose between *Basic Authentication* or " -"*Authentication Token* (selecting one of the two methods leads to additional " -"fields where you can enter your credentials/token)." +#: ../system/integrations/ldap/index.rst:30 +msgid "Before you continue, please note the following limitations." msgstr "" -#: ../system/objects/types.rst:265 -msgid "Search result list key" +#: ../system/integrations/ldap/index.rst:32 +msgid "Mapping / Synchronizing organizations is not possible" msgstr "" -#: ../system/objects/types.rst:261 +#: ../system/integrations/ldap/index.rst:36 msgid "" -"Defines the level in the JSON structure which provides the list with search " -"results. You can leave it empty, if the data is already provided as an " -"array. If you have to go deeper in the structure, you can provide a path " -"with ``.`` as separators, e.g. ``key.subkey.sub-sub-key``." +"You may want to consider using domain based assignments to overcome this " +"issue. Learn more on :doc:`/manage/organizations/index`." msgstr "" -#: ../system/objects/types.rst:271 -msgid "Search result value key" +#: ../system/integrations/ldap/index.rst:39 +msgid "" +"Zammad's LDAP sync is one way. Editing user settings or permissions may be " +"overwritten upon the next sync depending on your configuration." msgstr "" -#: ../system/objects/types.rst:268 -msgid "" -"Defines the attribute in the structure in which your external data source " -"provides the *value* for your data. An example would be a product *number*. " -"If you have to go deeper in the structure, you can provide a path with ``.`` " -"as separators, e.g. ``key.subkey.sub-sub-key``." +#: ../system/integrations/ldap/index.rst:41 +msgid "Nested groups are not supported." msgstr "" -#: ../system/objects/types.rst:277 -msgid "Search result label key" +#: ../system/integrations/ldap/index.rst:42 +msgid "Synchronizing user avatars from LDAP is not supported." msgstr "" -#: ../system/objects/types.rst:274 -msgid "" -"Defines the attribute in the structure in which your external data source " -"provides the *label* for your data. An example would be a product *name*. If " -"you have to go deeper in the structure, you can provide a path with ``.`` as " -"separators, e.g. ``key.subkey.sub-sub-key``." +#: ../system/integrations/ldap/index.rst:43 +msgid "Unlike user filters, group filters cannot be changed." msgstr "" -#: ../system/objects/types.rst:280 +#: ../system/integrations/ldap/index.rst:44 msgid "" -"In the preview area, you can find the following items (depending on your " -"configuration above):" +"When a user originates from an LDAP server, Zammad will try to verify the " +"login credentials against LDAP first - if this fails Zammad will check its " +"local database." msgstr "" -#: ../system/objects/types.rst:283 +#: ../system/integrations/ldap/index.rst:50 msgid "" -"**Error/hint message** (only if configuration is not complete): Zammad tells " -"you, if there is a problem and what you should change in your configuration." +"Users can have local passwords even if they're LDAP users! You can learn " +"more about user accounts in general on :doc:`/manage/users/index`." msgstr "" -#: ../system/objects/types.rst:286 +#: ../system/integrations/ldap/index.rst:54 msgid "" -"**Search field**: search for an existing attribute in the data source to get " -"a preview. This is required for the fields below to show up." +"When several LDAP sources contain the same user (meaning the same email " +"address), the user in question will be updated with every source configured. " +"*The last LDAP source will win.*" msgstr "" -#: ../system/objects/types.rst:288 +#: ../system/integrations/ldap/index.rst:58 msgid "" -"**Search result response** (only if configuration is not complete): here you " -"can find a syntax highlighted JSON preview of the response, based on the " -"search term you entered." +"This is subject to change with `Issue 4109 `_ in the future." msgstr "" -#: ../system/objects/types.rst:291 +#: ../system/integrations/ldap/index.rst:60 msgid "" -"**Search result list** (only if *search result list key* is properly set): " -"output of the structure under the configured *search result list key*." +"Synchronization statistics currently affect *all* configured LDAP sources. " +"This also applies for newly added or updated sources." msgstr "" -#: ../system/objects/types.rst:294 +#: ../system/integrations/ldap/index.rst:63 msgid "" -"**Preview table** (when fully configured): Zammad shows you a table which " -"includes the found items based on the search string (value, label and " -"optional link). You can use this preview if you don't have the complete data " -"structure of the external system in mind." +"This is subject to change with `Issue 4108 `_ in the future." msgstr "" -#: ../system/objects/types.rst:299 +#: ../system/integrations/ldap/index.rst:65 msgid "" -"An example of a configured external data source field from agent perspective:" +"Zammad currently has limited fallback server support. You can workaround " +"this by providing several sources - however, ensure to have the exact same " +"configuration on your fallback." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Screencast showing the search for a product in a ticket" +#: ../system/integrations/ldap/index.rst:69 +msgid "" +"This is subject to improve with `Issue 4107 `_ in the future." msgstr "" -#: ../system/objects/types.rst:307 -msgid "URL fields (Link-Template)" +#: ../system/integrations/ldap/index.rst:76 +msgid "" +"This section holds all requests Zammad handled for all LDAP sources. These " +"entries can either contain synchronization information or logins " +"(authentication attempts via Zammad's login interface)." msgstr "" -#: ../system/objects/types.rst:311 +#: ../system/integrations/ldap/index.rst:80 msgid "" -"This function is restricted to Text, Select and External data source types " -"only." +"By clicking on any request, Zammad will provide even more information. The " +"provided information can be useful when something does not work as expected." msgstr "" -#: ../system/objects/types.rst:314 +#: ../system/integrations/ldap/index.rst:85 msgid "" -"Link-Templates are an amazing way to dynamically generate URLs. They allow " -"you to integrate other systems better without having to manually copy data " -"from Zammad if possible." +"Especially a LDAP synchronization can cause many log entries. The web " +"interface will always limit the number of shown entries to the last 50 " +"entries." msgstr "" -#: ../system/objects/types.rst:320 +#: ../system/integrations/ldap/index.rst:None msgid "" -"Another great way of communicating with another system may be Zammad's :doc:" -"`Webhooks `." +"Screencast showing LDAP integration log entries and a detail view on\n" +"an entry." msgstr "" -#: ../system/objects/types.rst:323 -msgid "" -"After filling a link-template enabled field, an URL icon will appear on its " -"right. Clicking on the icon opens a new tab." +#: ../system/integrations/ldap/manage.rst:2 +msgid "Manage LDAP-Sources" msgstr "" -#: ../system/objects/types.rst:328 +#: ../system/integrations/ldap/manage.rst:6 msgid "" -"Even though Zammad displays the link template within object edit and create " -"screens, the function is optional. It's only active if you populate the " -"field." +"Please keep in mind all current limitations for the LDAP synchronization. " +"This will help to understand scopes of the following operations better." msgstr "" -#: ../system/objects/types.rst:333 -msgid "" -"What's the difference between URL and text fields with link template...?!" +#: ../system/integrations/ldap/manage.rst:65 +msgid "Add new source" msgstr "" -#: ../system/objects/types.rst:335 +#: ../system/integrations/ldap/manage.rst:10 msgid "" -"Both fields have different use cases. Use ``text`` type text fields when " -"ever you have a *static* url that requires dynamic parameters. If you " -"require a drag & drop like field that you can put in any URL, use ``URL`` " -"type text fields." +"Using the *New Source* button allows you to add new LDAP sources to your " +"installation. You're not limited in the number of sources, however, keep in " +"mind that many sources will also take more time to synchronize." msgstr "" -#: ../system/objects/types.rst:340 +#: ../system/integrations/ldap/manage.rst:14 msgid "" -"The difference is easier to spot when comparing the fields directly, below " -"screencast shows the result - the dynamic approach uses existing values in " -"the moment of updating to built the URL - e.g. ``https://google.com/search?" -"q=cookies`` - while the URL approach uses the actual URL of the field - e.g. " -"``https://zammad.com``." +"You can choose between different encryption types, namely *SSL* and " +"*STARTTLS* or none of them (\"*No SSL*\"). If you choose *SSL* or " +"*STARTTLS*, Zammad will display an additional *SSL verification* option that " +"allows you to disable the verification, e.g. for self-signed SSL " +"certificates. You can also tell Zammad to use a different port by appending " +"``:`` to your hostname/IP." msgstr "" -#: ../system/objects/types.rst:None +#: ../system/integrations/ldap/manage.rst:0 msgid "" -"Screencast showing the differents in between URL and text type fields with " -"actual values" +"Screenshot of configuring a new LDAP source with SSL encryption and SSL " +"verification" msgstr "" -#: ../system/objects/types.rst:352 -msgid "How does this work...?!" +#: ../system/integrations/ldap/manage.rst:26 +msgid "" +"New Source with SSL transport security enabled and certificate verification" msgstr "" -#: ../system/objects/types.rst:354 +#: ../system/integrations/ldap/manage.rst:30 msgid "" -"As an example, let's say you have an attribute called ``amazing_attribute`` " -"and you want to open a google search directly with the input from that field." +"Using an user filter can be a good idea if you only require a small subset " +"of your LDAP users in Zammad." msgstr "" -#: ../system/objects/types.rst:357 -msgid "" -"Providing the link-template field below allows you to do so: ``https://www." -"google.com/search?q=#{ticket.amazing_attribute}``" +#: ../system/integrations/ldap/manage.rst:42 +msgid "This especially affects inactive users" msgstr "" -#: ../system/objects/types.rst:362 +#: ../system/integrations/ldap/manage.rst:34 msgid "" -"You can use any :doc:`Zammad variable ` as long as it's " -"available in the moment you need it." +"As every LDAP behaves differently on which attributes and how they are set, " +"Zammad doesn't care about any flags." msgstr "" -#: ../system/objects/types.rst:365 +#: ../system/integrations/ldap/manage.rst:37 msgid "" -"As a result, you are redirected to Google with a search for the value of the " -"attribute, if you click on the button in the ticket (as you can see in the " -"screencast above)." +"Users that no longer are returned by your LDAP source will automatically be " +"set to inactive. Zammad assumes that the user was deactivated." msgstr "" -#: ../system/packages.rst:2 -msgid "Packages" +#: ../system/integrations/ldap/manage.rst:41 +msgid "" +"Users will never be removed automatically! If you want to remove obsolete " +"users, use :doc:`/system/data-privacy`." msgstr "" -#: ../system/packages.rst:4 -msgid "That's the package management-area." +#: ../system/integrations/ldap/manage.rst:46 +msgid "Active Directory admins" msgstr "" -#: ../system/packages.rst:6 -msgid "Individual add-ons for Zammad can be installed and managed here." +#: ../system/integrations/ldap/manage.rst:45 +msgid "" +"Active Directories are quite specific on how to filter for active users only " +"- please see the `Microsoft documentation `_ for more " +"information." msgstr "" -#: ../system/sessions.rst:2 -msgid "Sessions" +#: ../system/integrations/ldap/manage.rst:51 +msgid "" +"*Do not* manually write pathes of either LDAP attributes or groups. If " +"Zammad does not display them, it either cannot find them or you have a lot " +"of users that don't have the attributes populated." msgstr "" -#: ../system/sessions.rst:4 +#: ../system/integrations/ldap/manage.rst:55 msgid "" -"Sessions management allows reviewing currently known user sessions and " -"allows to end these. The session timeout is affected by :ref:" -"`security_session_timeout` configurations from security settings." +"Zammad will always only return attributes that are filled - this reduces the " +"returned list of attributes greatly." msgstr "" -#: ../system/sessions.rst:None -msgid "Screenshot showing Zammad's session management" +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing how to add a new LDAP source" msgstr "" -#: ../system/sessions.rst:13 -msgid "Zammad will provide the following information:" +#: ../system/integrations/ldap/manage.rst:63 +msgid "" +"If your LDAP system doesn't allow anonymous bind, Zammad detects it and " +"provides you an editable \"Base DN\" *text* field instead of a prefilled " +"*select* field." msgstr "" -#: ../system/sessions.rst:16 -msgid "" -"The user account this session entry belongs to. It can be normal if a user " -"has several sessions in the list. This can be due to changed browser " -"information or if you use e.g. single sign on methods where the user does " -"not use the log off button." +#: ../system/integrations/ldap/manage.rst:81 +msgid "Review or edit existing source" msgstr "" -#: ../system/sessions.rst:22 -msgid "Browser" +#: ../system/integrations/ldap/manage.rst:68 +msgid "" +"Clicking on a LDAP source will provide a configuration and mapping overview." msgstr "" -#: ../system/sessions.rst:22 -msgid "The browser agent communicated to Zammad." +#: ../system/integrations/ldap/manage.rst:70 +msgid "" +"If needed you can then use the *Change* button to update either the name, " +"active state or the whole configuration. If you're changing the whole " +"configuration, the dialogue will be identical to the source creation." msgstr "" -#: ../system/sessions.rst:40 -msgid "Location" +#: ../system/integrations/ldap/manage.rst:76 +msgid "" +"Did your LDAP server change? Different LDAP servers have different " +"structures and default attributes. This causes the LDAP synchronization to " +"likely fail. Consider removing the affected source and re-add it." msgstr "" -#: ../system/sessions.rst:25 -msgid "" -"The anticipated location based on the users IP address. Depending on the IP " -"address the result shown may differ. This option depends on :doc:`/settings/" -"system/services`." +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing the update of the source name." msgstr "" -#: ../system/sessions.rst:29 -msgid "The following information can be shown:" +#: ../system/integrations/ldap/manage.rst:89 +msgid "Re-arrange LDAP source's order" msgstr "" -#: ../system/sessions.rst:33 -msgid "IP address" +#: ../system/integrations/ldap/manage.rst:84 +msgid "" +"You can change the synchronization order for each source at any time. Zammad " +"will synchronize the sources from top to bottom." msgstr "" -#: ../system/sessions.rst:32 +#: ../system/integrations/ldap/manage.rst:0 msgid "" -"Either if you set *Geo IP services* to inactive or you're using internal IP " -"address which do not provide location information." +"Screencasting showing how to change the source order by using\n" +"drag and drop." msgstr "" -#: ../system/sessions.rst:40 -msgid "Country (or Country + City)" +#: ../system/integrations/ldap/manage.rst:101 +msgid "Remove a source" msgstr "" -#: ../system/sessions.rst:36 +#: ../system/integrations/ldap/manage.rst:92 msgid "" -"If *Geo IP services* is enabled only. Depends on how detailed the available " -"IP address information are." +"If you no longer need the a LDAP source or simply want to start over, you " +"can remove them at any time. This will not remove synchronized users, data " +"synchronized or permissions." msgstr "" -#: ../system/sessions.rst:39 +#: ../system/integrations/ldap/manage.rst:98 msgid "" -"Be aware that results can be inaccurate - this technically is not an error." +"Not sure if you'd need the source later on? Set the source to inactive " +"instead of removing it - see *Review or edit existing source* for more." msgstr "" -#: ../system/sessions.rst:43 -msgid "Age" +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing how to remove LDAP sources." msgstr "" -#: ../system/sessions.rst:43 -msgid "Provides the time when the session initially has been created." +#: ../system/integrations/pgp/index.rst:2 +msgid "PGP" msgstr "" -#: ../system/sessions.rst:50 -msgid "Update" +#: ../system/integrations/pgp/index.rst:7 +msgid "" +"Pretty Good Privacy (PGP) is another method for secure email communication. " +"With PGP, you can exchange **signed** and **encrypted** messages with others." msgstr "" -#: ../system/sessions.rst:46 -msgid "" -"Provides the time the user used this session to open Zammad. This timestamp " -"is only updated if the user e.g. reloads, not during normal work on tickets." +#: ../system/integrations/pgp/index.rst:13 +#: ../system/integrations/smime/index.rst:17 +msgid "Signing" msgstr "" -#: ../system/sessions.rst:50 -msgid "This timestamp is being used for the session timeout." +#: ../system/integrations/pgp/index.rst:11 +msgid "is a proof that a message hasn't been manipulated on its way." msgstr "" -#: ../system/sessions.rst:53 +#: ../system/integrations/pgp/index.rst:13 msgid "" -"Use the delete button to remove a single session on behalf of your user." +"In other words, it guarantees message **integrity** and **authenticity**." msgstr "" -#: ../system/subscription/billing.rst:2 -msgid "Billing" +#: ../system/integrations/pgp/index.rst:19 +#: ../system/integrations/smime/index.rst:22 +msgid "Encryption" msgstr "" -#: ../system/subscription/billing.rst:4 +#: ../system/integrations/pgp/index.rst:16 +#: ../system/integrations/smime/index.rst:20 msgid "" -"Within the billing tab you can control all billing relevant information like " -"invoices, billing address and the option to cancel your subscription." -msgstr "" - -#: ../system/subscription/billing.rst:33 -msgid "Billing information" +"scrambles a message so that it can only be unscrambled by the intended " +"recipient." msgstr "" -#: ../system/subscription/billing.rst:8 +#: ../system/integrations/pgp/index.rst:19 msgid "" -"All adjusted billing information below only affect future invoices. If your " -"invoice was issued wrong, please contact `our sales team `_." +"In other words, it guarantees message **privacy** and **data security**." msgstr "" -#: ../system/subscription/billing.rst:14 -msgid "Billing address" +#: ../system/integrations/pgp/index.rst:25 +msgid "Screenshot of ticket creation with encrypt and sign buttons" msgstr "" -#: ../system/subscription/billing.rst:13 +#: ../system/integrations/pgp/index.rst:25 msgid "" -"Provide your company address here, make sure to include the companies name " -"in case required. This address will be referenced on your invoice." +"Once PGP has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " +"appear in the ticket composer." msgstr "" -#: ../system/subscription/billing.rst:18 -msgid "VAT ID" +#: ../system/integrations/pgp/index.rst:28 +msgid "**Sign button not visible?**" msgstr "" -#: ../system/subscription/billing.rst:17 +#: ../system/integrations/pgp/index.rst:30 msgid "" -"Provide your VAT ID here. If applicable your invoice will not contain German " -"VAT. Please make sure to pay the VAT in your country as required." +"Please note that the signing of emails is based on the outgoing email " +"account. That means you have to choose a group with a sender email account, " +"which has a private key assigned." msgstr "" -#: ../system/subscription/billing.rst:27 -msgid "Billing Email Address" +#: ../system/integrations/pgp/index.rst:35 +msgid "Handling of Keys" msgstr "" -#: ../system/subscription/billing.rst:21 +#: ../system/integrations/pgp/index.rst:36 msgid "" -"Usually the instance owner (the person that registered the instance) will " -"receive all emails including the invoices. In case you have your own billing " -"department, you can provide their email address here." +"To use the PGP function, you have to enable the integration (PGP) by " +"switching the toggle to *enabled*." msgstr "" -#: ../system/subscription/billing.rst:25 +#: ../system/integrations/pgp/index.rst:39 msgid "" -"All billing relevant information will then be sent to this email address." +"You can add keys by clicking the *add key* button. The keys can be imported " +"from a file or you can paste the content of the key in the text box." msgstr "" -#: ../system/subscription/billing.rst:27 -msgid "Invoices are sent as attachment (PDF) to this email address." +#: ../system/integrations/pgp/index.rst:42 +msgid "**Which keys do I have to import?**" msgstr "" -#: ../system/subscription/billing.rst:29 +#: ../system/integrations/pgp/index.rst:44 msgid "" -"Don't forget to press the *Submit* button after you changed above settings." +"For **signing** *outgoing* emails, you have to import the private key of " +"your Zammad email account." msgstr "" -#: ../system/subscription/billing.rst:0 +#: ../system/integrations/pgp/index.rst:47 msgid "" -"Screenshot showing options for billing information within the\n" -"subscription menu" -msgstr "" - -#: ../system/subscription/billing.rst:70 -msgid "Payment history" +"For **encrypting** *outgoing* emails, you have to import the public key of " +"the customer's email account." msgstr "" -#: ../system/subscription/billing.rst:36 +#: ../system/integrations/pgp/index.rst:50 msgid "" -"The payment history will display a history of all paid invoices. At this " -"point you can also download these in case you need them again." +"For **verifying the signature** of signed *incoming* emails, you have to " +"import the public key of the customer." msgstr "" -#: ../system/subscription/billing.rst:41 +#: ../system/integrations/pgp/index.rst:53 msgid "" -"You will only find *paid* invoices here. Invoices that are to be billed are " -"not available before the payment is completed." +"For **decrypting** of encrypted *incoming* emails, you have to import the " +"private key of your Zammad email account." msgstr "" -#: ../system/subscription/billing.rst:46 -msgid "Date" +#: ../system/integrations/pgp/index.rst:57 +msgid "Import Keys From a File" msgstr "" -#: ../system/subscription/billing.rst:46 -msgid "Date of the invoice creation." +#: ../system/integrations/pgp/index.rst:58 +msgid "You can import keys from a file in the section **Upload key**:" msgstr "" -#: ../system/subscription/billing.rst:49 -msgid "Amount" +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of adding a key via file" msgstr "" -#: ../system/subscription/billing.rst:49 -msgid "Invoice total including VAT if applicable." +#: ../system/integrations/pgp/index.rst:64 +msgid "" +"**Supported file formats:** ASCII-armor as well as binary GPG format " +"(basically any GPG supported key format) is supported here." msgstr "" -#: ../system/subscription/billing.rst:52 -msgid "" -"Contains contract period (monthly or yearly) and hosted plan for the " -"subscription period in question." +#: ../system/integrations/pgp/index.rst:68 +msgid "Import Keys by Pasting the Content" msgstr "" -#: ../system/subscription/billing.rst:63 -msgid "Payment method / Service period" +#: ../system/integrations/pgp/index.rst:69 +msgid "You can also paste the key's content in the section **paste key**:" msgstr "" -#: ../system/subscription/billing.rst:56 -msgid "" -"Used bank account or credit card as well as the subscription period the " -"invoice is about." +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of adding a key via pasting" msgstr "" -#: ../system/subscription/billing.rst:61 +#: ../system/integrations/pgp/index.rst:75 msgid "" -"It might happen that the invoice date and subscription period differ. This " -"is nothing to worry about, the subscription periods will be accounted later " -"on." +"**Supported format:** Please note that only ASCII-armor is supported here." msgstr "" -#: ../system/subscription/billing.rst:67 -msgid "Receipt" +#: ../system/integrations/pgp/index.rst:78 +msgid "Deleting Keys" msgstr "" -#: ../system/subscription/billing.rst:66 +#: ../system/integrations/pgp/index.rst:79 msgid "" -"Use the arrow to download the invoice in question. You can download all " -"available invoices any time you need to here!" +"If you want to delete a specific key, you can do it by clicking on the menu " +"in the *actions* column and select **delete**:" msgstr "" -#: ../system/subscription/billing.rst:0 -msgid "Screenshot showing payment history of a hosted instance" +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of deleting a key" msgstr "" -#: ../system/subscription/billing.rst:94 -msgid "Do you want to cancel your subscription?" +#: ../system/integrations/pgp/index.rst:88 +msgid "Downloading Keys" msgstr "" -#: ../system/subscription/billing.rst:73 +#: ../system/integrations/pgp/index.rst:89 msgid "" -"In case you no longer want to use Zammad's SaaS, you can cancel your " -"subscription by using the red *Yes, please cancel my subscription* button." +"If you want to download your keys, you can do this as well via corresponding " +"action buttons. Depending on the key, you can choose wether you want to " +"download the private or the public key." msgstr "" -#: ../system/subscription/billing.rst:76 -msgid "" -"Your subscription will end the day after your trial or billing period ends." +#: ../system/integrations/pgp/index.rst:95 +#: ../system/integrations/smime/manage-certificates.rst:76 +msgid "Default Behavior" msgstr "" -#: ../system/subscription/billing.rst:80 +#: ../system/integrations/pgp/index.rst:96 msgid "" -"We will remind you about your cancelled subscription several times up front. " -"After the subscription ended all instance data will be removed. A restore " -"*is not* possible after that point!" +"Here you can adjust on per group basis, if *sign* and *encryption* is on or " +"off by default. Please be aware, that agents can always override the setting " +"for each individual article." msgstr "" -#: ../system/subscription/billing.rst:0 -msgid "Screencast showing how to cancel a subscription" +#: ../system/integrations/pgp/index.rst:None +msgid "Adjusting default behavior on per group basis" msgstr "" -#: ../system/subscription/billing.rst:87 -msgid "**😖 Cancelled by accident?**" +#: ../system/integrations/pgp/index.rst:107 +msgid "" +"Here you can see the last actions regarding signing and encryption and if " +"they were successful." msgstr "" -#: ../system/subscription/billing.rst:89 -msgid "" -"You can always undo the cancellation via the *Yes, undo the cancellation of " -"my subscription* button up to the last subscription day!" +#: ../system/integrations/pgp/index.rst:117 +msgid "**Sign button is not visible, but keys are imported.**" +msgstr "" + +#: ../system/integrations/pgp/index.rst:115 +msgid "Did you choose a group in the ticket?" msgstr "" -#: ../system/subscription/billing.rst:0 +#: ../system/integrations/pgp/index.rst:116 msgid "" -"Screenshot showing a red button to cancel the subscription\n" -"cancellation" +"Did you import a private key for the email adress, which is used for " +"outgoing emails in the group?" msgstr "" -#: ../system/subscription/index.rst:2 -msgid "Subscription (SaaS)" +#: ../system/integrations/pgp/index.rst:122 +msgid "**How to obtain keys?**" msgstr "" -#: ../system/subscription/index.rst:4 +#: ../system/integrations/pgp/index.rst:120 msgid "" -"The subscription settings page allows you to configure your instances " -"package and number of agents required." +"You can create them yourself! There are some good tutorials on the web on " +"how to create them. Providing keys to Zammad is a prerequisite to use the " +"PGP feature." msgstr "" -#: ../system/subscription/index.rst:9 -msgid "" -"This setting section is only available for Hosted setups. If you're looking " -"for on premise support contracts, please see the `Zammad pricing page " -"`_." +#: ../system/integrations/pgp/index.rst:127 +msgid "**It says a passphrase is needed, but I haven't got one.**" msgstr "" -#: ../system/subscription/index.rst:20 +#: ../system/integrations/pgp/index.rst:125 msgid "" -"The subscription section currently consists of two tabs: Plan & Billing. For " -"your overview we've divided those two tabs into independent sub pages:" +"If the key is secured with a passphrase, you have to provide it for the " +"import in Zammad. It is possible that keys may have an empty passphrase. " +"However, this is *not* recommended." msgstr "" -#: ../system/subscription/index.rst:25 -msgid ":doc:`💰 Subscription plan `" +#: ../system/integrations/pgp/index.rst:132 +msgid "**How do my customers get my new key?**" msgstr "" -#: ../system/subscription/index.rst:24 +#: ../system/integrations/pgp/index.rst:130 msgid "" -"Everything affecting your instance subscription functions like number of " -"agents, package and payment method." +"You have to provide your **public** key in advance. Your customer also has " +"to configure PGP in their email workflow and import your public key. The " +"other way round, you have to get the public key of your customer and have to " +"import it to Zammad." +msgstr "" + +#: ../system/integrations/slack.rst:2 +msgid "Slack" msgstr "" -#: ../system/subscription/index.rst:28 -msgid ":doc:`🧾 Subscription billing `" +#: ../system/integrations/slack.rst:4 +msgid "**⚠️ Deprecation warning ⚠️**" msgstr "" -#: ../system/subscription/index.rst:28 +#: ../system/integrations/slack.rst:6 msgid "" -"Everything regarding billing address, invoices and account cancellation." +"Zammad 7 will no longer support this dedicated Slack integration. It is " +"recommended to switch to :doc:`pre-defined webhooks ` instead. Existing Slack integrations should " +"be migrated manually before this feature is dropped." msgstr "" -#: ../system/subscription/index.rst:33 -msgid "FAQ" +#: ../system/integrations/slack.rst:14 +msgid "" +"In order to use this feature, please add a new Slack app to your Workspace. " +"The App you need is called ``Incoming WebHooks`` ." msgstr "" -#: ../system/subscription/index.rst:37 -msgid "I set up a trial account but am missing functions to test" +#: ../system/integrations/slack.rst:18 +msgid "Why Do I Need This Feature?" msgstr "" -#: ../system/subscription/index.rst:36 +#: ../system/integrations/slack.rst:20 msgid "" -"The trial instance is running within the professional package allowing up to " -"three agents." +"If you're already using Slack for your team communication, you'll love this " +"feature! Our Slack integration can push ticket notifications about the last " +"ticket article based on the following events:" msgstr "" -#: ../system/subscription/index.rst:40 -msgid "Can I change package within the trial?" +#: ../system/integrations/slack.rst:24 +msgid "on Ticket creation" msgstr "" -#: ../system/subscription/index.rst:40 -msgid "No. As soon as the package is changed the subscription begins." +#: ../system/integrations/slack.rst:25 +msgid "on Ticket updates" msgstr "" -#: ../system/subscription/index.rst:45 -msgid "What happens to my trial instance after the trial period ended?" +#: ../system/integrations/slack.rst:26 +msgid "on reached reminders" msgstr "" -#: ../system/subscription/index.rst:43 -msgid "" -"Your instance will automatically be canceled for you. Please see *What " -"happens to my instance after it has been canceled?* for more." +#: ../system/integrations/slack.rst:27 +msgid "a Ticket has escalated" msgstr "" -#: ../system/subscription/index.rst:58 -msgid "What happens to my instance after it has been canceled?" +#: ../system/integrations/slack.rst:28 +msgid "a Ticket is going to escalate" msgstr "" -#: ../system/subscription/index.rst:48 -msgid "That depends slightly on your instance state:" +#: ../system/integrations/slack.rst:30 +msgid "" +"Zammad will provide the Ticket title, a direct link to the Ticket, the event " +"type (creation, updated, escalation), the customer, time and the last " +"article that has triggered the notification." msgstr "" -#: ../system/subscription/index.rst:54 -msgid "Trial instance" +#: ../system/integrations/slack.rst:34 +msgid "" +"This will give you further options, as you can see e.g. escalating tickets " +"that are assigned to an agent that's e.g. absent. You can interact faster, " +"as you might see problems earlier (or even before the problem gets one)." msgstr "" -#: ../system/subscription/index.rst:51 +#: ../system/integrations/slack.rst:38 msgid "" -"If you're still on trial, we will ice your instance and remind you once " -"again about your instance. We then will wait some days and remove your " -"instance from our system. This is the last time we will inform you by Email." +"If needed and wanted, you can even discuss directly about the topic before " +"sending an answer to the customer. Another possible use case would be a " +"agent monitoring new agents and their answers to tickets." msgstr "" -#: ../system/subscription/index.rst:58 -msgid "Paid instance" +#: ../system/integrations/slack.rst:44 +msgid "Configure the Integration" msgstr "" -#: ../system/subscription/index.rst:57 +#: ../system/integrations/slack.rst:46 msgid "" -"If you're a paying customer and canceled your subscription, the instance " -"removal will take place the day after your last subscription day." +"First of all, please go to your slack workspace - go to administration => " +"Manage Apps. If you don't have an app yet, you can simply add a new one - " +"just search for ``Incoming WebHooks`` and customize the app to your needs." msgstr "" -#: ../system/subscription/index.rst:60 -msgid "Can removed instances be restored?" +#: ../system/integrations/slack.rst:50 +msgid "" +"Choose (or create) the channel Zammad should post it's information to and " +"press on \"Add Incoming WebHooks integration\". If you're ready, copy the " +"provided WebHook URL and go to your Zammad installation." msgstr "" -#: ../system/subscription/index.rst:61 -msgid "No. Once your instance has been removed, a restoration is not possible." +#: ../system/integrations/slack.rst:56 +msgid "" +"You need administrative rights on the Slack Workspace. The link to the app " +"directory is normally ``https://[workspace-name].slack.com/apps`` ." msgstr "" -#: ../system/subscription/plan.rst:2 ../system/subscription/plan.rst:38 -msgid "Plan" +#: ../system/integrations/slack.rst:63 +msgid "" +"To configure the slack integration, log in to Zammad and go to Integrations " +"(System) => Slack in the admin panel." msgstr "" -#: ../system/subscription/plan.rst:16 -msgid "Subscription" +#: ../system/integrations/slack.rst:66 +msgid "" +"Here you can choose on what evens Zammad should post information about a " +"ticket to your Slack channel. Next you need to device what groups shall be " +"affected by this, as anybody with access to that specific Slack channel can " +"read at least parts of the ticket this might be a privacy issue, if you " +"select the wrong groups. The username is simply the name that Zammad uses as " +"display name inside the Slack chat. The channel defines the Slack channel " +"the information is being posted in. As last option, you can set a custom " +"icon for posting to slack." msgstr "" -#: ../system/subscription/plan.rst:5 +#: ../system/integrations/slack.rst:74 msgid "" -"On the top of the subscription summary you'll find the number of used and " -"available (booked) agent seats. By using the *see more* link you can also " -"expand an agent list to see the currently configured active agents. This " -"list *does not* count accounts with admin permissions only." +"When you're ready, just hit \"Submit\" and enable the integration. Zammad " +"will now post new ticket information based on the trigger you chose. Below " +"the options you have the recent log that shows the latest requests to Slack " +"for debugging if needed." msgstr "" -#: ../system/subscription/plan.rst:0 +#: ../system/integrations/slack.rst:81 msgid "" -"Within subscription you can always see how many agents are still\n" -"available to add and who uses the seats." +"If you leave the Icon URL empty, Zammad will use the Zammad logo instead. " +"The icon should be a square PNG file." msgstr "" -#: ../system/subscription/plan.rst:14 +#: ../system/integrations/slack.rst:90 msgid "" -"Learn more on how to manage your agents in general :doc:`here `." +"The following figure shows how it will look if you choose to receive updates " +"on created and updated tickets. On every post Zammad sends to the Slack " +"channel, you can create new threads to discuss about the new article." msgstr "" -#: ../system/subscription/plan.rst:19 +#: ../system/integrations/slack.rst:96 msgid "" -"This section gives you an overview of the available plans and their " -"functions / limits. If you require a more detailed table, check our " -"`detailed pricing table `_ for more." +"If you just want to keep track of soon escalating or already escalated " +"tickets, it will look the the following figure. Zammad changes the color in " +"front of the post so you can easily see the state of the ticket." msgstr "" -#: ../system/subscription/plan.rst:23 +#: ../system/integrations/slack.rst:102 msgid "" -"Your selection in this step will decide on the base agent price and e.g. " -"agent limits that might apply in the summary step." +"If you change the state, Zammad will also put information on what state the " +"ticket gets and (if pending state) the date until it pends. You'll also " +"recognize the color codes in front of posts on slack, as they are exact the " +"same the ticket state colors you'll see in Zammad!" msgstr "" -#: ../system/subscription/plan.rst:26 -msgid "" -"The green *Selected* button will also tell you what plan you're currently in." +#: ../system/integrations/smime/index.rst:2 +msgid "S/MIME" msgstr "" -#: ../system/subscription/plan.rst:30 +#: ../system/integrations/smime/index.rst:11 msgid "" -"Trial instances are running at Professional with 3 agents. The plan cannot " -"be changed during the trial for technical reasons, if you require more " -"agents for testing, please contact `our sales team `_ with a reason for the raise request." +"S/MIME is the most widely-supported method for secure email communication. " +"With S/MIME, you can exchange **signed** and **encrypted** messages with " +"others." msgstr "" -#: ../system/subscription/plan.rst:0 +#: ../system/integrations/smime/index.rst:15 msgid "" -"Screenshot showing three available packages for a hosted Zammad\n" -"instance" +"is proof that a message hasn't been tampered with or sent by an impersonator." msgstr "" -#: ../system/subscription/plan.rst:83 -msgid "Summary" +#: ../system/integrations/smime/index.rst:17 +msgid "" +"In other words, it guarantees a message's **integrity** and **authenticity**." msgstr "" -#: ../system/subscription/plan.rst:41 -msgid "" -"In this section you can adjust the settings of the previous selected plan." +#: ../system/integrations/smime/index.rst:22 +msgid "In other words, it guarantees **privacy** and **data security**." msgstr "" -#: ../system/subscription/plan.rst:45 -msgid "" -"Note that upgrading (more agents, higher package) is always possible, " -"however, downgrading will only happen when your billing period renews." +#: ../system/integrations/smime/index.rst:28 +msgid "Screencast demo of S/MIME features for both new tickets and replies" msgstr "" -#: ../system/subscription/plan.rst:49 +#: ../system/integrations/smime/index.rst:28 msgid "" -"Upgrading resets your billing period and existing credit will be deducted " -"from the new total." +"Once S/MIME has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " +"appear in the ticket composer." msgstr "" -#: ../system/subscription/plan.rst:58 -msgid "Billing cycle" +#: ../system/integrations/smime/index.rst:32 +msgid ":doc:`🔪 Prerequisites `" msgstr "" -#: ../system/subscription/plan.rst:53 +#: ../system/integrations/smime/index.rst:31 msgid "" -"You can choose between either monthly or yearly billing. The price per agent " -"will be cheaper if you decide for yearly billing." +"New to S/MIME? This section helps you to find certificate providers and " +"points out Limitations." msgstr "" -#: ../system/subscription/plan.rst:56 -msgid "" -"If you're still trying out things and are unsure of the right package for " -"your instance, you may want to choose monthly first and then upgrade to " -"yearly when you're sure." +#: ../system/integrations/smime/index.rst:35 +msgid ":doc:`📝 Manage Certificates `" msgstr "" -#: ../system/subscription/plan.rst:66 -msgid "Plan: (Starter|Professional|Plus) - Agents" +#: ../system/integrations/smime/index.rst:35 +msgid "Add and download certificates; configure group default behaviors." msgstr "" -#: ../system/subscription/plan.rst:61 -msgid "Choose the number of agents you require for your instance." +#: ../system/integrations/smime/index.rst:38 +msgid ":doc:`😦 Troubleshooting `" msgstr "" -#: ../system/subscription/plan.rst:63 -msgid "" -"Keep in mind that some packages may have agent limits. Depending on the " -"previous chosen package, you won't be able to exceed specific agent numbers. " -"Also note that setting less agents than currently configured is not possible." +#: ../system/integrations/smime/index.rst:38 +msgid "Took a wrong turn? About recent logs and common issues." msgstr "" -#: ../system/subscription/plan.rst:69 -msgid "Total" +#: ../system/integrations/smime/index.rst:43 +msgid "" +"For more details on how S/MIME integration works on the agent side, see the :" +"user-docs:`user docs `." msgstr "" -#: ../system/subscription/plan.rst:69 -msgid "This will be the net total you're going to be billed." +#: ../system/integrations/smime/manage-certificates.rst:2 +msgid "Manage Certificates" msgstr "" -#: ../system/subscription/plan.rst:71 +#: ../system/integrations/smime/manage-certificates.rst:4 msgid "" -"By using the *Update subscription* button, the instance package will be " -"adjusted immediately. If you didn't provide a payment method yet, Zammad " -"will request you to provide one at this point." +"S/MIME is **disabled by default**. Enable it to start adding certificates." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:10 +msgid "Dialogue to add new certificates or private keys" msgstr "" -#: ../system/subscription/plan.rst:77 +#: ../system/integrations/smime/manage-certificates.rst:10 msgid "" -"In case you're still within the trial period, this means that the trial will " -"be over immediately!" +"Manage certificates in the Admin Panel under **System > Integrations > S/" +"MIME**. Certificates may be pasted in as plain text or uploaded from a file." msgstr "" -#: ../system/subscription/plan.rst:80 -msgid "Down- or upgrading during the trial period *is not* possible." +#: ../system/integrations/smime/manage-certificates.rst:14 +msgid "Add Certificate Data" msgstr "" -#: ../system/subscription/plan.rst:0 -msgid "Screenshot showing payment options and a pricing summary" +#: ../system/integrations/smime/manage-certificates.rst:36 +msgid "Add Certificate" msgstr "" -#: ../system/subscription/plan.rst:99 -msgid "Payment method" +#: ../system/integrations/smime/manage-certificates.rst:17 +msgid "" +"Import public-key certificates for both your own organization and your " +"contacts." msgstr "" -#: ../system/subscription/plan.rst:86 -msgid "You can pay via credit card or SEPA mandate." +#: ../system/integrations/smime/manage-certificates.rst:19 +msgid "" +"You can also add a bunch of certificates in one go by providing a single " +"file with all relevant certificates." msgstr "" -#: ../system/subscription/plan.rst:91 -msgid "Credit card" +#: ../system/integrations/smime/manage-certificates.rst:22 +msgid "🕵️ **ALWAYS verify certificates in-person or over the phone!**" msgstr "" -#: ../system/subscription/plan.rst:89 +#: ../system/integrations/smime/manage-certificates.rst:24 msgid "" -"Simply follow the dialogue by clicking *authorize* and confirm -if required " -"by your bank- your consent to Zammad using your card for the payments." +"The whole point of signatures is to alert you when someone is trying to " +"pretend to be someone they're not. Never accept a certificate from someone " +"online without verifying it first." msgstr "" -#: ../system/subscription/plan.rst:95 -msgid "SEPA" +#: ../system/integrations/smime/manage-certificates.rst:28 +msgid "📇 **What about trusted certificate authorities?**" msgstr "" -#: ../system/subscription/plan.rst:94 +#: ../system/integrations/smime/manage-certificates.rst:30 msgid "" -"Provide the requested information of the bank account holder and update if " -"you're ready. You'll then receive an email with the SEPA mandate." +"In some cases (e.g. when dealing with large enterprises), you may be given a " +"certificate for an entire CA, rather than a single contact. Add it here to " +"trust *all* certificates issued by that CA." msgstr "" -#: ../system/subscription/plan.rst:97 +#: ../system/integrations/smime/manage-certificates.rst:35 msgid "" -"Technically there's also the possibility to pay via invoice, however - this " -"method only applies to a fairly low number of instances. Please contact `our " -"sales team `_ for more information." +"Commercial CAs can usually be verified online. Zammad does not include a " +"list of built-in, trusted CAs." msgstr "" -#: ../system/translations.rst:2 -msgid "Translations" +#: ../system/integrations/smime/manage-certificates.rst:57 +msgid "Add Private Key" msgstr "" -#: ../system/translations.rst:4 +#: ../system/integrations/smime/manage-certificates.rst:39 msgid "" -"Translations of Zammad are processed centrally in our `Weblate instance " -"`_. This allows non-developers to review " -"and update translation texts of the language they actually speak." +"Once you've added a public-key certificate, you can import its matching " +"private key." msgstr "" -#: ../system/translations.rst:9 +#: ../system/integrations/smime/manage-certificates.rst:42 msgid "" -"Your language is in an incomplete translation state or has typos? Please " -"consider helping us in sorting this out! All you need is either a GitHub " -"account or to register directly in our instance." +"Private keys are for **your own organization only**; never ask your contacts " +"for their private keys." msgstr "" -#: ../system/translations.rst:13 +#: ../system/integrations/smime/manage-certificates.rst:0 msgid "" -"Did you know? This is also where the documentation translations are handled. " -"🤓" +"S/MIME integration showing configured certificates and possible issues with " +"Logging" msgstr "" -#: ../system/translations.rst:15 +#: ../system/integrations/smime/manage-certificates.rst:50 msgid "" -"Have a look in our :docs:`contribution section ` in the system documentation to get started!" +"A note is displayed on certificates with a matching private key (see line 2)." msgstr "" -#: ../system/translations.rst:20 -msgid "Local Translations" +#: ../system/integrations/smime/manage-certificates.rst:52 +msgid "📤 **Certificates and private keys must be uploaded separately.**" msgstr "" -#: ../system/translations.rst:22 +#: ../system/integrations/smime/manage-certificates.rst:54 msgid "" -"Apart from these system translations, there's still local translations you " -"can manage. This is relevant if you added custom objects that require " -"translations or even custom states and priorities." +"If your certificate and private key are bundled together in the same file or " +"PEM block, import it twice (once using each button)." msgstr "" -#: ../system/translations.rst:None -msgid "Translation management screen within the admin menu" +#: ../system/integrations/smime/manage-certificates.rst:57 +msgid "Please note that bulk imports of private keys are not possible." msgstr "" -#: ../system/translations.rst:31 -msgid "Updating Translations" +#: ../system/integrations/smime/manage-certificates.rst:60 +msgid "Download Certificate Data" msgstr "" -#: ../system/translations.rst:33 +#: ../system/integrations/smime/manage-certificates.rst:62 msgid "" -"Because of how Zammad ships translations, the only way to update the system " -"translations is to update your Zammad installation. The benefit of this is " -"that you no longer need internet access during a Zammad upgrade as the " -"package has everything it requires already." +"You can download the earlier provided certificates and private keys at any " +"time from your Zammad instance." msgstr "" -#: ../system/translations.rst:39 -msgid "Translation of Custom Objects" +#: ../system/integrations/smime/manage-certificates.rst:65 +msgid "" +"Please note that passphrase-protected private keys stay protected and when " +"you download them, you have to know the passphrase to use them after " +"downloading." msgstr "" -#: ../system/translations.rst:41 -msgid "" -"No problem at all! You can customize any translation locally, even if it is " -"not initially provided by the system." +#: ../system/integrations/smime/manage-certificates.rst:73 +msgid "Dialogue to download certificates or private keys" msgstr "" -#: ../system/translations.rst:44 +#: ../system/integrations/smime/manage-certificates.rst:73 +msgid "Download stored certificates and their keys" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:78 msgid "" -"Translation is supported for a broad number of features, including but not " -"limited to custom:" +"The ticket composer will set all outgoing messages to **signed and " +"encrypted** by default (assuming the required certificates exist)." msgstr "" -#: ../system/translations.rst:47 -msgid "Object Attributes" +#: ../system/integrations/smime/manage-certificates.rst:82 +msgid "These defaults can be modified on a per-group basis:" msgstr "" -#: ../system/translations.rst:48 -msgid "Ticket Macros" +#: ../system/integrations/smime/manage-certificates.rst:None +msgid "Zammad allowing to choose the default behavior on per group basis" msgstr "" -#: ../system/translations.rst:49 -msgid "Ticket Overviews" +#: ../system/integrations/smime/manage-certificates.rst:89 +msgid "" +"Of course, agents can always manually change these settings on each email " +"they send out." msgstr "" -#: ../system/translations.rst:50 -msgid "Ticket Priorities" +#: ../system/integrations/smime/prerequisites.rst:4 +msgid "A certificate *and* private key for your own organization" msgstr "" -#: ../system/translations.rst:51 -msgid "Ticket States" +#: ../system/integrations/smime/prerequisites.rst:6 +msgid "" +"(Use this to ✒️ **sign outgoing messages** and 🔓 **decrypt incoming " +"messages**.)" msgstr "" -#: ../system/translations.rst:54 -msgid "Customizing Translations" +#: ../system/integrations/smime/prerequisites.rst:9 +msgid "" +"Certificates belonging your contacts, or their issuing certificate authority " +"(CA)" msgstr "" -#: ../system/translations.rst:56 +#: ../system/integrations/smime/prerequisites.rst:11 msgid "" -"Within the translation screen, simply click on the **New Translation** " -"button." +"(Use these to ✅ **verify incoming message signatures** and 🔒 **encrypt " +"outgoing messages**.)" msgstr "" -#: ../system/translations.rst:None -msgid "New translation dialog" +#: ../system/integrations/smime/prerequisites.rst:14 +msgid "🙋 **I'm new to S/MIME. Where can I get a certificate?**" msgstr "" -#: ../system/translations.rst:62 +#: ../system/integrations/smime/prerequisites.rst:16 msgid "" -"In the dialog you can immediately enter the exact translation source (if you " -"know it) and your custom translation text for it and click **Submit**." +"The easiest way to get certificates is to buy an annual subscription through " +"a commercial CA, such as:" msgstr "" -#: ../system/translations.rst:65 +#: ../system/integrations/smime/prerequisites.rst:19 msgid "" -"Alternatively, try to search for translation suggestions in the list below. " -"Selecting an item from the list will pre-fill the translation source for you " -"and then you can just enter your custom translation." +"`Sectigo (formerly Comodo) `_" msgstr "" -#: ../system/translations.rst:69 -msgid "" -"The target language will always default to your current language selection. " -"If you need to translate for a different language, simply change the " -"selection before submitting." +#: ../system/integrations/smime/prerequisites.rst:20 +msgid "`Secorio `_" msgstr "" -#: ../system/translations.rst:73 -msgid "" -"All your custom translations will show up in the overview table when added. " -"And they will even persist across Zammad updates!" +#: ../system/integrations/smime/prerequisites.rst:21 +msgid "`GlobalSign `_" msgstr "" -#: ../system/translations.rst:76 -msgid "" -"Make sure to reload your browser if a translated string is not displayed." +#: ../system/integrations/smime/prerequisites.rst:23 +msgid "(Zammad is not affiliated with these CAs in any way.)" msgstr "" -#: ../system/translations.rst:80 -msgid "Reverting to Original Translations" +#: ../system/integrations/smime/prerequisites.rst:25 +msgid "" +"You can also generate your own self-signed certificates, but the process is " +"complicated and usually 🙅 **involves extra work for your contacts**." msgstr "" -#: ../system/translations.rst:82 +#: ../system/integrations/smime/prerequisites.rst:29 msgid "" -"If you want to revert a custom translation to original text, simply use the " -"appropriate action within the row of the overview table." +"Bear in mind that 🤝 **S/MIME only works if the other party is using it, too." +"**" msgstr "" -#: ../system/translations.rst:85 +#: ../system/integrations/smime/prerequisites.rst:32 +msgid "Certificate and Private Key Checks on Upload" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:34 msgid "" -"Depending on the type of the translation source, the action has a slightly " -"different name:" +"The certificate and public key validation is based on the ``X509v3`` " +"extensions." msgstr "" -#: ../system/translations.rst:88 -msgid "**Reset** for customized system translations" +#: ../system/integrations/smime/prerequisites.rst:49 +msgid "Uploading a *client certificate*?" msgstr "" -#: ../system/translations.rst:89 -msgid "**Remove** for customized local translations" +#: ../system/integrations/smime/prerequisites.rst:41 +msgid "The following attributes are required then:" msgstr "" -#: ../system/translations.rst:91 -msgid "" -"In both cases, the action will remove the customized translation after a " -"confirmation." +#: ../system/integrations/smime/prerequisites.rst:39 +msgid "Subject Alternative Name (at least one email address has to be present)" msgstr "" -#: ../system/translations.rst:None -msgid "Screenshot showing the location of the Remove action" +#: ../system/integrations/smime/prerequisites.rst:40 +msgid "Key Usage (``Digital Signature`` and/or ``Key Encipherment``)" msgstr "" -#: ../system/translations.rst:99 -msgid "Inline Translations" +#: ../system/integrations/smime/prerequisites.rst:41 +msgid "Public key algorithm (either ``RSA`` or ``EC``)" msgstr "" -#: ../system/translations.rst:101 +#: ../system/integrations/smime/prerequisites.rst:43 msgid "" -"If you prefer a more hands-on approach, you can activate the inline or on-" -"screen translation feature by pressing ``ctrl`` + ``alt`` + ``t`` at any " -"time and on any screen." +"The Extended Key Usage attribute is optional. If the certificate provides " +"the named attribute, than it must contain the value ``E-mail Protection``." msgstr "" -#: ../system/translations.rst:105 +#: ../system/integrations/smime/prerequisites.rst:46 msgid "" -"All customizable translation texts will be highlighted for you on the " -"screen. Just click into the highlighted area and update the text in place." +"Please note that any usable email adress has to be prefixed with ``email:`` " +"or ``rfc822:``." msgstr "" -#: ../system/translations.rst:None -msgid "Inline translation mode activated for the Overview screen" +#: ../system/integrations/smime/prerequisites.rst:49 +msgid "The named public key algorithms are mandatory for private keys as well." msgstr "" -#: ../system/translations.rst:112 +#: ../system/integrations/smime/prerequisites.rst:54 +msgid "Uploading a *CA certificate*?" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:52 msgid "" -"When finished editing, simply press ``ctrl`` + ``alt`` + ``t`` again to " -"deactivate." +"In the case of an uploaded CA certificate, providing the value ``CA:TRUE`` " +"in the attribute *Basic Contstraints*, the previously mentioned attributes " +"are not verified." msgstr "" -#: ../system/translations.rst:117 +#: ../system/integrations/smime/prerequisites.rst:56 msgid "" -"Even though it's available on any screen, the inline translation feature " -"requires admin permissions. It works only for the current language " -"selection. If you need to translate a different language, first change the " -"language in your :user-docs:`profile settings `." +"In general, the usage of any expired (``Not After``) or not yet valid (``Not " +"Before``) certificate is denied for outgoing emails." msgstr "" -#: ../system/variables.rst:2 -msgid "Variables" +#: ../system/integrations/smime/prerequisites.rst:59 +msgid "Example certificate:" msgstr "" -#: ../system/variables.rst:4 +#: ../system/integrations/smime/prerequisites.rst:85 msgid "" -"Please note that this is just an overview of available variables. It might " -"be incomplete or variables might not be available within some functions. If " -"you're missing variables or are not sure if something is not working as " -"expected, feel free to ask over at the `Community `_." +"Please note that Zammad will distrust senders by default. This means that " +"you're always required to provide certificate data, no matter if for signing " +"or encrypting." msgstr "" -#: ../system/variables.rst:10 -msgid "" -"Variables can be called by typing ``::`` (just like text modules in the " -"frontend), as long as you're in a supported text field within the backend. " -"Zammad will display all variables being available within this context and " -"replace it to the variable as soon as you selected an entry." +#: ../system/integrations/smime/prerequisites.rst:89 +msgid "This is by design and can't be adjusted." msgstr "" -#: ../system/variables.rst:15 +#: ../system/integrations/smime/troubleshooting.rst:4 msgid "" -"You have an empty field which you referenced and it appears as ``-``? That's " -"currently working as designed - you might want to ensure that these fields " -"always have a value." +"All of the system's latest S/MIME activity is displayed in the **Recent " +"Logs** section." msgstr "" -#: ../system/variables.rst:20 -msgid "Variable Categories" +#: ../system/integrations/smime/troubleshooting.rst:11 +msgid "Sample entries of in- and outgoing S/MIME related emails." msgstr "" -#: ../system/variables.rst:31 -msgid "Wait, What About Custom Objects?" +#: ../system/integrations/smime/troubleshooting.rst:11 +msgid "" +"Logs report the status and details of all mail, both incoming and outgoing, " +"that used signing/verification or encryption/decryption." msgstr "" -#: ../system/variables.rst:33 +#: ../system/integrations/smime/troubleshooting.rst:14 msgid "" -"Good point! Of course, we can't predict what objects you might create, but " -"we can give you a hint on how to put the puzzle together to get your custom " -"values." +"This log does **not** include email sent by :doc:`triggers ` or the :doc:`scheduler `. For those, check your " +"``production.log``." +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:20 +msgid "Common Issues" +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:30 +msgid "I received a signed/encrypted email before I set up S/MIME integration" msgstr "" -#: ../system/variables.rst:36 +#: ../system/integrations/smime/troubleshooting.rst:23 msgid "" -"For this, we'll talk about the inner part of the variable (so everything " -"within ``#{}``), please put the outer part around to have a valid variable. " -"The first part of the variable name consist of the object type. Currently " -"these are:" +"No problem. Once S/MIME has been enabled and the appropriate certificates " +"have been added, agents will be prompted to retry verification/decryption on " +"matching emails." msgstr "" -#: ../system/variables.rst:41 -msgid "Ticket (``ticket``)" +#: ../system/integrations/smime/troubleshooting.rst:0 +msgid "Screenshot of user prompt to retry decryption" msgstr "" -#: ../system/variables.rst:42 -msgid "User (``user``)" +#: ../system/integrations/smime/troubleshooting.rst:38 +msgid "The 🔒 **Encrypt** button is disabled" msgstr "" -#: ../system/variables.rst:43 -msgid "Organization (``organization``)" +#: ../system/integrations/smime/troubleshooting.rst:33 +msgid "Have you added the recipient's certificate?" msgstr "" -#: ../system/variables.rst:44 -msgid "Group (``group``)" +#: ../system/integrations/smime/troubleshooting.rst:34 +msgid "Are you sure the recipient's certificate is valid?" msgstr "" -#: ../system/variables.rst:46 -msgid "" -"The second part is the name of the object. This is the name you define " -"during object creation and can be found within the object menu at any time. " -"The first and second part of a variable is divided by a point, e.g.: " -"``ticket.number`` which will in total be ``#{ticket.number}``." +#: ../system/integrations/smime/troubleshooting.rst:35 +msgid "Have you checked your ``production.log`` for more details?" msgstr "" -#: ../system/variables.rst:51 +#: ../system/integrations/smime/troubleshooting.rst:37 msgid "" -"Now, in some situations it's possible that you'll need to use a third part. " -"The best example for such a situation would be a ``select`` or ``tree-" -"select`` field which will by default return the key value, not it's display " -"name. For this, just extend your variable with ``.value``. This will result " -"in ``#{ticket.select.value}``." +"If encryption doesn't work in the composer, it won't work in :doc:`triggers " +"` or the :doc:`scheduler ` either!" msgstr "" -#: ../system/variables.rst:60 -msgid "Using Translated Variables" +#: ../system/integrations/smime/troubleshooting.rst:42 +msgid "The ✅ **Sign** button is disabled" msgstr "" -#: ../system/variables.rst:62 +#: ../system/integrations/smime/troubleshooting.rst:41 msgid "" -"If you want to use a translated variable in triggers or schedulers, you can " -"extend the placeholder like this: ``#{t(ticket.state.name)}``. The ``t`` " -"tells Zammad to search for fitting translated strings. The used output " -"language is based on the system language of Zammad which you can set in the " -"admin panel under :doc:`/settings/branding` or based on the selected locale " -"in the trigger/scheduler edit dialog." +"Have you added **both the certificate and private key** for your " +"organization?" msgstr "" -#: ../system/variables.rst:69 +#: ../system/integrations/smime/troubleshooting.rst:42 msgid "" -"A possible use-case: you want to send your customers updates on tickets via " -"trigger or scheduler which should include the state of the ticket. Using the " -"default ``#{ticket.state.name}`` (without the translation flag ``t()``) " -"would lead to the output of the original (english) name of the state." +"Does the email address on the certificate match the email address of the " +"agent/group composing the email?" msgstr "" -#: ../system/variables.rst:75 -msgid "Date and Time Formatting" +#: ../system/integrations/smime/troubleshooting.rst:45 +msgid "Error: “Fingerprint already taken”" msgstr "" -#: ../system/variables.rst:77 -msgid "" -"The system (trigger/scheduler selected) locale and timezone predefines a " -"default format of date and timestamp. This format is customizable by using " -"the ``dt()`` method." +#: ../system/integrations/smime/troubleshooting.rst:45 +msgid "Are you sure you haven't added this certificate already?" msgstr "" -#: ../system/variables.rst:79 -msgid "The method arguments are as follows:" +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Error: “❌ invalid byte sequence in UTF-8”" msgstr "" -#: ../system/variables.rst:81 -msgid "The date or timestamp variable you want to format." +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Please ensure to provide PEM formatted certificate and keys." msgstr "" -#: ../system/variables.rst:82 -msgid "The output format string." +#: ../system/integrations/smime/troubleshooting.rst:49 +msgid "Did you check if the provided file is a valid certificate or key?" msgstr "" -#: ../system/variables.rst:83 -msgid "The timezone to apply (optional)." +#: ../system/integrations/zabbix.rst:2 +msgid "Zabbix Integration" msgstr "" -#: ../system/variables.rst:86 +#: ../system/integrations/zabbix.rst:5 msgid "" -"``#{dt(ticket.updated_at, \"%A %Y-%m-%d %H:%M in the office\", \"Europe/" -"Berlin\")}``" +"This guide describes how to integrate your Zabbix 5.4 installation with " +"Zammad using the Zabbix webhook feature. This guide will provide " +"instructions on setting up a media type, a user and an action in Zabbix." msgstr "" -#: ../system/variables.rst:87 -msgid "Monday, 2024-03-18 15:31 in the office" +#: ../system/integrations/zabbix.rst:12 +msgid "Zammad with enabled HTTP Token Authentication" msgstr "" -#: ../system/variables.rst:89 -msgid "" -"If you want to use our example, make sure to paste the string above without " -"formatting (``CTRL+Shift+v``), otherwise it won't work." +#: ../system/integrations/zabbix.rst:13 +msgid "Zabbix version 5.4 or higher" msgstr "" -#: ../system/variables.rst:93 -msgid "The following table lists available format directives:" +#: ../system/integrations/zabbix.rst:16 +msgid "Setting up a Zammad" msgstr "" -#: ../system/variables.rst:99 -msgid "Parameter" +#: ../system/integrations/zabbix.rst:18 +msgid "Enable **API Token Access** in Settings > System > API." msgstr "" -#: ../system/variables.rst:102 -msgid "``%Y``" +#: ../system/integrations/zabbix.rst:20 +msgid "" +"Create a **new user** for a Zabbix alerter with an **email address** and " +"create a personal user token with **ticket.agent** permissions." msgstr "" -#: ../system/variables.rst:103 -msgid "Year with 4 digits" +#: ../system/integrations/zabbix.rst:24 +msgid "Zabbix Webhook Configuration" msgstr "" -#: ../system/variables.rst:104 -msgid "Use ``%y`` for year with 2 digits" +#: ../system/integrations/zabbix.rst:27 +msgid "Create a Global Macro" msgstr "" -#: ../system/variables.rst:105 -msgid "``%m``" +#: ../system/integrations/zabbix.rst:29 +msgid "" +"Before setting up the **Webhook**, you need to setup the global macro " +"**{$ZABBIX.URL}**, which must contain the **URL** to the **Zabbix frontend**." msgstr "" -#: ../system/variables.rst:106 -msgid "Month of year (as number with zero-padding)" +#: ../system/integrations/zabbix.rst:33 +msgid "" +"In the **Administration** > **Media types** section, import the `Template`_." msgstr "" -#: ../system/variables.rst:107 -msgid "Use ``%-m`` for month without zero-padding" +#: ../system/integrations/zabbix.rst:38 +msgid "Open the added **Zammad** media type and set:" msgstr "" -#: ../system/variables.rst:108 -msgid "``%d``" +#: ../system/integrations/zabbix.rst:40 +msgid "**zammad\\_access\\_token** to the your **Personal User Token**" msgstr "" -#: ../system/variables.rst:109 -msgid "Day of month (as number with zero-padding)" +#: ../system/integrations/zabbix.rst:41 +msgid "" +"**zammad\\_url** to the **frontend URL** of your **Zammad** installation" msgstr "" -#: ../system/variables.rst:110 -msgid "Use ``%e`` for day without zero-padding" +#: ../system/integrations/zabbix.rst:43 +msgid "**zammad\\_customer** to your **Zammad user email**." msgstr "" -#: ../system/variables.rst:111 -msgid "``%H``" +#: ../system/integrations/zabbix.rst:44 +msgid "" +"**zammad\\_enable\\_tags** to **true** or **false** to enable or disable " +"trigger tags. **Important**: if you enable tag support, each tag is set with " +"a separate request." msgstr "" -#: ../system/variables.rst:112 -msgid "Hour of day in 24h notation with zero-padding" +#: ../system/integrations/zabbix.rst:48 +msgid "" +"If you want to prioritize issues according to **severity** values in Zabbix, " +"you can define mapping parameters:" msgstr "" -#: ../system/variables.rst:113 -msgid "Use ``%k`` for hour without zero-padding" +#: ../system/integrations/zabbix.rst:51 +msgid "**severity\\_**: Zammad priority ID" msgstr "" -#: ../system/variables.rst:114 -msgid "``%I``" +#: ../system/integrations/zabbix.rst:53 +msgid "Click the **Update** button to save the **Webhook** settings." msgstr "" -#: ../system/variables.rst:115 -msgid "Hour of day in 12h notation with zero-padding" +#: ../system/integrations/zabbix.rst:55 +msgid "" +"To receive notifications in **Zammad**, you need to create a **Zabbix user** " +"and add **Media** with the **Zammad** type." msgstr "" -#: ../system/variables.rst:116 +#: ../system/integrations/zabbix.rst:58 msgid "" -"Use ``%l`` for hour without zero-padding and ``%p`` / ``%P`` for meridian " -"indicator" +"For **Send to**: enter any text, as this value is not used, but is required." msgstr "" -#: ../system/variables.rst:117 -msgid "``%M``" +#: ../system/integrations/zabbix.rst:61 +msgid "" +"For more information, use the `Zabbix documentation `_." msgstr "" -#: ../system/variables.rst:118 -msgid "Minute of hour" +#: ../system/maintenance.rst:2 +msgid "Maintenance" msgstr "" -#: ../system/variables.rst:120 -msgid "``%S``" +#: ../system/maintenance.rst:4 +msgid "" +"Zammad comes with a maintenance mode that you can use for e.g. updating the " +"instance or changing settings while restricting availability and functions." msgstr "" -#: ../system/variables.rst:121 -msgid "Second of Minute" +#: ../system/maintenance.rst:13 +msgid "Mode" msgstr "" -#: ../system/variables.rst:123 -msgid "``%A``" +#: ../system/maintenance.rst:8 +msgid "The mode setting allows you to enable or disable the maintenance mode." msgstr "" -#: ../system/variables.rst:124 -msgid "Weekday name" +#: ../system/maintenance.rst:10 +msgid "Defaults to *off*." msgstr "" -#: ../system/variables.rst:125 -msgid "Use ``%a`` for abbreviated name or ``%^A`` for uppercase name" +#: ../system/maintenance.rst:12 +msgid "" +"The maintenance mode will restrict access to administrative roles only. This " +"means agents and customers are logged off." msgstr "" -#: ../system/variables.rst:126 -msgid "``%B``" +#: ../system/maintenance.rst:23 +msgid "@Login" msgstr "" -#: ../system/variables.rst:127 -msgid "Month name" +#: ../system/maintenance.rst:16 +msgid "" +"This setting allows you to provide a login message within a green banner " +"above the login screen. Click into the green banner in the settings page to " +"adjust your message. To activate the message, activate the *@Login* setting." msgstr "" -#: ../system/variables.rst:128 -msgid "Use ``%b`` for abbreviated name" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing the default login message within the\n" +"settings page" msgstr "" -#: ../system/variables.rst:129 -msgid "``%U``" +#: ../system/maintenance.rst:26 +msgid "" +"Send an informative message to **all active sessions**. This comes handy to " +"inform your agents e.g. about mayor outages or to force reloads after " +"configuration changes." msgstr "" -#: ../system/variables.rst:130 -msgid "Week number of current year" +#: ../system/maintenance.rst:31 +msgid "This is the messages title (slightly bigger than the normal message)." msgstr "" -#: ../system/variables.rst:131 -msgid "Use ``%W`` for a different calculation method" +#: ../system/maintenance.rst:34 +msgid "The text you want to provide to your logged in sessions." msgstr "" -#: ../system/variables.rst:134 +#: ../system/maintenance.rst:39 +msgid "Reload application" +msgstr "" + +#: ../system/maintenance.rst:37 msgid "" -"We support the known format directives for the Ruby built-in method " -"``strftime`` of the ``DateTime`` class. For more information, see `here " -"`_." +"Selecting this option will change the message acceptance button from *Close* " +"(with nothing happening) to *Continue session*, which forces the application " +"to reload." msgstr "" -#: ../system/variables/article.rst:2 -msgid "Articles" +#: ../system/maintenance.rst:43 +msgid "" +"If you have customers that are logged in to Zammad, they'll also be notified " +"if they're active in that moment." msgstr "" -#: ../system/variables/article.rst:4 ../system/variables/config.rst:4 -#: ../system/variables/current-user.rst:4 ../system/variables/ticket.rst:4 +#: ../system/maintenance.rst:48 +msgid "Example without reload application" +msgstr "" + +#: ../system/maintenance.rst:52 msgid "" -"If you're missing variables or are not sure if something is not working as " -"expected, feel free to ask over at the `Community `_." +"Message setting within Zammad's admin settings without ticket reload " +"application setting." msgstr "" -#: ../system/variables/article.rst:6 +#: ../system/maintenance.rst:0 msgid "" -"Below you can find all available ticket article-based variables within " -"Zammad. These can be called via Triggers for example. If you're unsure if " -"Zammad does support variables at the point you're at, you can try to type " -"``::`` to check." +"Screenshot showing the send message settings without ticket\n" +"reload application set" msgstr "" -#: ../system/variables/article.rst:9 ../system/variables/config.rst:9 -#: ../system/variables/ticket.rst:9 +#: ../system/maintenance.rst:61 ../system/maintenance.rst:85 msgid "" -"The below list gives you an example what kind of data you can expect, it's " -"not intended to explain the data itself." +"The modal all other active sessions will see upon pressing *Send to clients*." msgstr "" -#: ../system/variables/article.rst:11 -msgid "Article Variables" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing modal caused by maintenance's message\n" +"without reload application ticket" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "name" +#: ../system/maintenance.rst:72 +msgid "Example with reload application" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "variable" +#: ../system/maintenance.rst:76 +msgid "" +"Message setting within Zammad's admin settings with ticket reload " +"application setting." msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "example" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing the send message settings with ticket\n" +"reload application set" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Web" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing modal caused by maintenance's message\n" +"with reload application ticket" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.web}``" +#: ../system/monitoring.rst:2 +msgid "Monitoring" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``https://zammad.com`` or empty if not set in user object" +#: ../system/monitoring.rst:4 +msgid "" +"This function is only available in self hosted instances. If you use Zammad " +"in our cloud, we are monitoring the system on our own and take steps to fix " +"potential problems directly." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > VIP" +#: ../system/monitoring.rst:11 +msgid "" +"On the monitoring page, you can see the current health state of Zammad under " +"\"*Current Status*\" at the bottom. This can be useful if you want to have a " +"look if everything is up and running. As an example, you could have a look " +"in the monitoring when you assume that some emails aren't processed from " +"Zammad." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.vip}``" +#: ../system/monitoring.rst:17 +msgid "**Can't receive an email and the monitoring response is \"healthy\"?**" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -msgid "``true`` or ``false``" +#: ../system/monitoring.rst:19 +msgid "" +"Zammad will just inform you about unprocessable emails. This is not the case " +"for oversized emails. You can adjust the maximum email size in :doc:`../" +"channels/email/settings`." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Phone" +#: ../system/monitoring.rst:24 +msgid "Monitoring API" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.phone}``" +#: ../system/monitoring.rst:26 +msgid "" +"Beside the indication in the monitoring page, you can also use an external " +"monitoring tool to monitor Zammad's health. To request the health of Zammad, " +"you need to provide the API key (token) to the external monitoring tool. You " +"can copy the token from the \"*Current Token*\" field as well as the whole " +"API endpoint of your system (\"*Health Check*\" field), in which the API " +"token is already included." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``+4930123456789`` or empty if not set in user object" +#: ../system/monitoring.rst:37 +msgid "Screenshot showing Current Token and Health Check" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Note" +#: ../system/monitoring.rst:37 +msgid "Screenshot showing Token and Health Check" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.note}``" +#: ../system/monitoring.rst:39 +msgid "" +"In addition to that, you can reset the auto-generated token to make sure " +"that already configured monitoring systems won't work anymore. So, please " +"use this \"*Reset*\" button only if you know what you do!" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Some note about user`` or empty if not set in user object" +#: ../system/monitoring.rst:44 +msgid "Example Output" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Mobile" +#: ../system/monitoring.rst:0 +msgid "No issues found" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.mobile}``" +#: ../system/monitoring.rst:48 ../system/monitoring.rst:60 +msgid "**Indicator in Zammad**:" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Login" +#: ../system/monitoring.rst:0 +msgid "Screenshot showing monitoring with no issues" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.login}``" +#: ../system/monitoring.rst:54 ../system/monitoring.rst:66 +msgid "**API response**::" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -#: ../system/variables/ticket.rst:1 -msgid "``jdoe``" +#: ../system/monitoring.rst:0 +msgid "Issues were found" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Lastname" +#: ../system/monitoring.rst:0 +msgid "Screenshot showing monitoring with issues" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.lastname}``" +#: ../system/objects.rst:2 +msgid "Objects" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -#: ../system/variables/ticket.rst:1 -msgid "``Doe`` or empty if not set" +#: ../system/objects.rst:4 +msgid "" +"In Zammad you can add your own fields to tickets, users, organizations and " +"even groups (these are called \"objects\"). This can be useful if you need " +"to add further information to a ticket or any other object in Zammad and the " +"information doesn't fit in any existing field." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Firstname" +#: ../system/objects.rst:11 +msgid "" +"Try to avoid deleting attributes (and disable them instead) as Zammad might " +"run into unexpected conditions if they are referenced somewhere." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.firstname}``" +#: ../system/objects.rst:16 +msgid "" +"Here's an overview of object attributes. On the upper right you can add new " +"attributes. By default, there will be no custom fields - standard attributes " +"will be grayed out, you can't delete or change those. You can edit custom " +"attributes (they are displayed in black font and have a trash bin on the " +"right side) just by clicking on them." msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "``Joe`` or empty if not set" +#: ../system/objects.rst:24 +msgid "" +"Attributes you add to Zammad, no matter if they have default values or not, " +"will not update existing information. This means a new ticket field " +"technically will be empty unless you populate it." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Fax" +#: ../system/objects.rst:28 +msgid "" +"Especially in ticket scope this also means that newly added attributes will " +"be indicated as \"changed\" to agents that view the ticket. This may " +"interfere with Zammad's tabs behavior." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.fax}``" +#: ../system/objects.rst:40 +msgid "Ordering Attributes" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Email" +#: ../system/objects.rst:42 +msgid "" +"Since Zammad introduced :doc:`/system/core-workflows` the need to have a " +"custom positioning for attributes has become more important than ever." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.email}``" +#: ../system/objects.rst:45 +msgid "" +"To adjust the position of such an attribute, simply click on the attribute " +"entry in question, scroll down and adjust the position number. Please note " +"that you cannot change the positioning of default attributes." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``jdoe@example.com``" +#: ../system/objects.rst:49 +msgid "" +"In case two attributes have the same position value, Zammad will sort " +"alphabetically by name automatically." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Department" +#: ../system/objects.rst:None +msgid "" +"Screenshot showing custom attribute entries ordered in between default ones" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.department}``" +#: ../system/objects.rst:56 +msgid "Updating Database After Adding or Editing Attributes" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Sales`` or empty if not set in user object" +#: ../system/objects.rst:58 +msgid "" +"When adding or changing attributes, Zammad will not apply the changes " +"instantly, but instead shows you the changed attributes first. If you're " +"ready to go, just click on \"Update database\" to apply the changes to " +"Zammad. If you made a mistake or just want to discard your changes, click " +"\"Discard changes\"." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Address" +#: ../system/objects.rst:64 +msgid "" +"After applying the changes with \"Update Database\", a restart of Zammad is " +"**mandatory**. If you don't perform it, you may experience unexpected " +"behavior or even errors. You may want to do this kind of configuration " +"during maintenance windows." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.address}``" +#: ../system/objects.rst:72 +msgid "" +"Changes on objects require you to update the database to apply these changes." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Some street 1, 12345 Berlin`` or empty if not set in user object" +#: ../system/objects.rst:75 +msgid "**🤓 Service restarts can be automated**" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated" +#: ../system/objects.rst:0 +msgid "Hosted environments automatically restart for you." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_at}``" +#: ../system/objects.rst:0 +msgid "" +"If you're using a self-hosted installation you can use :docs:`environment " +"variables `" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``2019-10-08 15:24:47 UTC``" +#: ../system/objects.rst:82 +msgid "System Attributes" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Type > Name" +#: ../system/objects.rst:84 +msgid "" +"Zammad comes with pre-configured attributes. Some of them can't be edited " +"via UI (or at all). This is required for proper operation of Zammad and not " +"a bug." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.type.name}``" +#: ../system/objects.rst:90 +msgid "Ticket State" msgstr "" -#: ../system/variables/article.rst:1 +#: ../system/objects.rst:92 msgid "" -"``email`` (`list of article types `_)" +"If the pre-configured states aren't enough for you or you want to change " +"them, you can do so by clicking on the cogwheel icon in the state row in the " +"ticket tab. But you should be careful when changing pre-configured states. " +"This can lead to unwanted behavior in some cases." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > To" +#: ../system/objects.rst:None +msgid "Screenshot showing highlighted ticket state attribute" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.to}``" +#: ../system/objects.rst:122 +msgid "Handling of states" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``helpdesk@example.com``" +#: ../system/objects.rst:102 +msgid "" +"In the state configuration screen, you can add new states, disable states or " +"change states." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > TicketID" +#: ../system/objects.rst:0 +msgid "Screenshot showing table of default ticket states" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.ticket_id}``" +#: ../system/objects.rst:110 +msgid "" +"To add a new state, click on the \"New Ticket State\" button in the top " +"right corner. To change an existing state, simply click on the affected " +"state. This opens an edit dialog." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``1`` (not ticket number)" +#: ../system/objects.rst:114 +msgid "" +"You can also clone a state or set them to \"Default for new tickets\" or " +"\"Default for follow-ups\" by clicking on the ⁝ action button and select the " +"desired function." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Subject" +#: ../system/objects.rst:118 +msgid "" +"*Default for new tickets* means that this state is used for every newly " +"created ticket." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.subject}``" +#: ../system/objects.rst:121 +msgid "" +"*Default for follow-ups* means that this state is used if the ticket is re-" +"opened after it was closed." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``My amazing subject``" +#: ../system/objects.rst:171 +msgid "Ticket state in detail" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Sender > Name" +#: ../system/objects.rst:125 +msgid "" +"Below you can find a description for each field and option. Please head over " +"to the :ref:`example ` to see the edit dialog." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.sender.name}``" +#: ../system/objects.rst:129 +msgid "" +"This is the name of the state and what you and your agents are seeing when " +"choosing a state somewhere (e.g. in tickets, trigger configuration)." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Customer``, ``Agent`` or ``System``" +#: ../system/objects.rst:137 +msgid "" +"There are different state types you can choose from. By default, Zammad " +"comes with one state per state type." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Visibility" +#: ../system/objects.rst:140 +msgid "" +"**new**: for states for tickets that are new and it hasn't been worked on " +"them" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.internal}``" +#: ../system/objects.rst:142 +msgid "" +"**open**: for states for tickets that are in progress and agents are working " +"on them" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``false`` or ``true`` (false if not internal)" +#: ../system/objects.rst:144 +msgid "**merged**: for states for tickets that are merged with other tickets" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > From" +#: ../system/objects.rst:145 +msgid "" +"**pending reminder**: for states for tickets that are in progress and you " +"want to set a reminder. (default example: *pending reminder*)" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.from}``" +#: ../system/objects.rst:147 +msgid "" +"**pending action**: for states for tickets that are waiting for a specified " +"time and then change their state (default example: *pending close*)" msgstr "" -#: ../system/variables/article.rst:1 +#: ../system/objects.rst:150 msgid "" -"``Joe Doe `` may differ, depends on ``FROM`` of send mail" +"**closed**: for states for tickets that are finished and do not need to be " +"processed further" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Web" +#: ../system/objects.rst:153 +msgid "" +"⚠️ Choosing the correct state type is important! If you are in doubt, have a " +"look on the default states and their types!" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.web}``" +#: ../system/objects.rst:158 +msgid "Ignore escalation" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > VIP" +#: ../system/objects.rst:157 +msgid "" +"Here you can define whether tickets of this state will count to escalation " +"time or not." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.vip}``" +#: ../system/objects.rst:161 +msgid "" +"You can create a note for the state to inform other admins about the state. " +"This has no effect on tickets." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Phone" +#: ../system/objects.rst:165 +msgid "Set the state to *active* or *inactive*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.phone}``" +#: ../system/objects.rst:167 +msgid "" +"it is technically possible to set all states to inactive. To keep Zammad " +"working in such a case, the inactive flag of one of the states is ignored." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Note" +#: ../system/objects.rst:194 +msgid "Ticket state example" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.note}``" +#: ../system/objects.rst:174 +msgid "" +"Let's assume we want to create a new state which indicates that the ticket " +"has to wait for a response of a third party (e.g. service contractor or " +"manufacturer) and we want to to be able to set a reminder." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Mobile" +#: ../system/objects.rst:178 +msgid "" +"First we give the new state a proper name. In this example we call it " +"\"waiting for manufacturer\"." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.mobile}``" +#: ../system/objects.rst:181 +msgid "" +"As state type we choose \"pending reminder\". This indicates that the ticket " +"is still open and we can set a reminder. This reminder can be useful if our " +"manufacturer sometimes isn't responding or we want to remind him to give us " +"an answer." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Login" +#: ../system/objects.rst:186 +msgid "" +"We choose \"no\" for \"ignore escalation\" because we want to escalate the " +"tickets even if we are waiting on the manufacturer's feedback." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.login}``" +#: ../system/objects.rst:189 +msgid "The **result** in the creation dialog will look like this:" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Lastname" +#: ../system/objects.rst:0 +msgid "Screenshot showing ticket state creation dialog with example" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.lastname}``" +#: ../system/objects.rst:199 +msgid "Ticket Priority" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Firstname" +#: ../system/objects.rst:201 +msgid "" +"If the pre-configured priorities aren't enough for you or you want to change " +"them, you can do so by clicking on the cogwheel icon in the priority row in " +"the ticket tab:" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.firstname}``" +#: ../system/objects.rst:None +msgid "Screenshot showing highlighted ticket priority attribute" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Fax" +#: ../system/objects.rst:226 +msgid "Handling of priorities" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.fax}``" +#: ../system/objects.rst:210 +msgid "" +"In the priority configuration screen, you can add new priorities, disable " +"priorities or change priorities." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Email" +#: ../system/objects.rst:0 +msgid "Screenshot showing table of default ticket priorities" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.email}``" +#: ../system/objects.rst:218 +msgid "" +"To add a new priority, click on the \"New Priority\" button in the top right " +"corner. To change an existing priority, simply click on the affected " +"priority. This opens an edit dialog." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Department" +#: ../system/objects.rst:222 +msgid "" +"You can also clone a priority or set them to \"Default for new tickets\" by " +"clicking on the ⁝ action button and select the desired function." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.department}``" +#: ../system/objects.rst:225 +msgid "" +"*Default for new tickets* means that this priority is used for every newly " +"created ticket." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Address" +#: ../system/objects.rst:248 +msgid "Priorities in detail" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.address}``" +#: ../system/objects.rst:229 +msgid "Below you can find a description for each field and option." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created" +#: ../system/objects.rst:232 +msgid "" +"This is the name of the priority and what you and your agents are seeing " +"when choosing a priority somewhere (e.g. in tickets, trigger configuration)." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_at}``" +#: ../system/objects.rst:242 +msgid "Highlight color" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Cc" +#: ../system/objects.rst:237 +msgid "" +"Switch between *Low priority* (light blue), *High priority* (red) and - " +"(default). This affects the displayed color for ticket titles in overviews." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.cc}``" +#: ../system/objects.rst:241 +msgid "The color options are currently limited to the mentioned options." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``jdoe@example.com, company@example.com``" +#: ../system/objects.rst:245 +msgid "" +"You can create a note for the priority to inform other admins about the " +"priority. This has no effect on tickets." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Text" +#: ../system/objects.rst:249 +msgid "Set the priority to *active* or *inactive*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.body}``" +#: ../system/objects/external-data-source-example.rst:2 +msgid "External Data Source" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Test`` without formatting (plain)" +#: ../system/objects/external-data-source-example.rst:4 +msgid "" +"We assume you already had a look on :doc:`types` where you can find a " +"description of the individual fields." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article Text as HTML (not referenced)" +#: ../system/objects/external-data-source-example.rst:7 +msgid "" +"To reproduce this example, choose a category you want to add a custom field, " +"click on *New Attribute* and select *External data source field* under " +"*Format*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.body_as_html}``" +#: ../system/objects/external-data-source-example.rst:11 +msgid "" +"Our example story is to fetch data from an external product database. We " +"want to add our products to the tickets so that the products can be searched " +"and chosen from a list and also create a link to the product website." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Test`` with formatting" +#: ../system/objects/external-data-source-example.rst:16 +msgid "Base configuration" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "Ticket > Article#" +#: ../system/objects/external-data-source-example.rst:None +msgid "Initial steps to configure external data source object type" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "``#{ticket.article_count}``" +#: ../system/objects/external-data-source-example.rst:25 +msgid "Name: *product*" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``1`` number of ticket articles" +#: ../system/objects/external-data-source-example.rst:26 +msgid "Display: *Product*" msgstr "" -#: ../system/variables/config.rst:2 -msgid "Config" +#: ../system/objects/external-data-source-example.rst:29 +msgid "External data source configuration" msgstr "" -#: ../system/variables/config.rst:6 +#: ../system/objects/external-data-source-example.rst:31 msgid "" -"Below you'll find config related variables. These hold useful configuration " -"information that you can use within e.g. triggers to show necessary " -"information to your customer." +"First, enter the search URL making sure it contains ``#{search.term}`` as a " +"parameter:" msgstr "" -#: ../system/variables/config.rst:11 -msgid "Config Variables" +#: ../system/objects/external-data-source-example.rst:34 +msgid "**Example:** ``https://dummyjson.com/products/search?q=#{search.term}``" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Fully Qualified Domain Name" +#: ../system/objects/external-data-source-example.rst:36 +msgid "" +"After that, head down to the preview section and enter a search input for " +"the external data source." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.fqdn}``" +#: ../system/objects/external-data-source-example.rst:39 +msgid "**Example:** ``mac``" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``zammad.example.com``" +#: ../system/objects/external-data-source-example.rst:41 +msgid "Then you can find a preview of the response data below:" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Ticket Hook" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of JSON response based on search term" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.ticket_hook}``" +#: ../system/objects/external-data-source-example.rst:48 +msgid "" +"We recommend using the preview to have a look on the structure. There is a " +"top-level element called ``products``. One level below, you can find the " +"attributes ``id`` and ``title``." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``Ticket#``" +#: ../system/objects/external-data-source-example.rst:52 +msgid "**Search result response based on search from example:**" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > HTTP type" +#: ../system/objects/external-data-source-example.rst:119 +msgid "" +"To tell the remote system that the desired data is located below the " +"``products`` level, you have to put it in the field *Search result list key*." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.http_type}``" +#: ../system/objects/external-data-source-example.rst:122 +msgid "" +"After inserting ``products`` in the mentioned field, you get an extended " +"preview. You can find an additional box *Search result list* with a JSON " +"structure. This is the same response as before but stripped from the upper " +"``products`` element by the external data source." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``https`` or ``http``" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of JSON response search result list" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > SystemID" +#: ../system/objects/external-data-source-example.rst:132 +msgid "" +"Now you need to provide the keys for the search result values and labels. As " +"already mentioned, we are looking for the ``id`` and the ``title`` of our " +"products. If you haven't already, it is now a good time to look at the " +"preview of the *Search result list*." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.system_id}``" +#: ../system/objects/external-data-source-example.rst:197 +msgid "" +"After locating our two keys, we insert them in *search result value key* " +"(``id``) and in *Search result label key* (``title``)." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``31`` (value between 1 and 99)" +#: ../system/objects/external-data-source-example.rst:200 +msgid "" +"Basically, we configured the external data source already and we can see a " +"table in the preview section:" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Organization" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of product table based on search term" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.organization}``" +#: ../system/objects/external-data-source-example.rst:208 +msgid "" +"According to our example story, now just the *Link template* is missing." msgstr "" -#: ../system/variables/config.rst:1 +#: ../system/objects/external-data-source-example.rst:210 msgid "" -"``Zammad GmbH`` value set in `Branding `_" +"Please note that this is an optional feature. If you don't want to use such " +"links, of course you don't have to configure it." msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Product Name" +#: ../system/objects/external-data-source-example.rst:213 +msgid "" +"We can add now an address where additional product information can be found." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.product_name}``" +#: ../system/objects/external-data-source-example.rst:215 +msgid "Example: ``https://your_domain.com/q=#{ticket.product}``" msgstr "" -#: ../system/variables/config.rst:1 -msgid "" -"``Helpdesk`` value set in `Branding `_" +#: ../system/objects/external-data-source-example.rst:217 +msgid "In the example, the parameter means:" +msgstr "" + +#: ../system/objects/external-data-source-example.rst:219 +msgid "``#{}``: \"Frame\" for the insertion of information" msgstr "" -#: ../system/variables/current-user.rst:2 -msgid "Current User" +#: ../system/objects/external-data-source-example.rst:220 +msgid "``ticket``: object level, where you create your custom object" msgstr "" -#: ../system/variables/current-user.rst:6 -msgid "" -"Current user variables always return values of the current user that caused " -"e.g. a trigger to run." +#: ../system/objects/external-data-source-example.rst:221 +msgid "``product``: name of the (custom) object" msgstr "" -#: ../system/variables/current-user.rst:8 +#: ../system/objects/external-data-source-example.rst:223 msgid "" -"Due to the above fact, these variables are often not (yet) set or available " -"for usage." +"After configuring your *Link template*, there will be another column in the " +"preview. Hovering on the icons in the *Link* column will show you where it " +"forwards you." msgstr "" -#: ../system/variables/current-user.rst:10 +#: ../system/objects/external-data-source-example.rst:232 msgid "" -"In situations where e.g. schedulers or triggers run, this most likely is " -"nothing you want to use." -msgstr "" - -#: ../system/variables/current-user.rst:13 -msgid "Current User Variables" +"In our example, one of the links looks like: https://your_domain.com/q=6, " +"where the 6 is the product id." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Web" +#: ../system/objects/external-data-source-example.rst:235 +msgid "You can find more information regarding the URL in :doc:`types`." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.web}``" +#: ../system/objects/includes/adding-values-hint.include.rst:3 +msgid "" +"Adding values can be tricky for first timers, don't forget to press \"➕ " +"Add\" after typing your values. Otherwise you may loose a value." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``https://zammad.org`` or empty if not set" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:1 +#: ../system/objects/includes/reposition-values.include.rst:1 +msgid "**↕️ This field type allows the positioning of its values ↔️**" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > VIP" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:3 +msgid "" +"In order to re-arrange the field values, first edit the field. Then you can " +"use ☰ to drag the values in question to the correct position. If you want to " +"change the layer depth, double click on ☰. With it you can cycle through the " +"available layers." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.vip}``" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:8 +msgid "When you're ready, submit your changes to save the object attribute." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``false`` or ``true``" +#: :0 ../system/objects/types.rst:0 +msgid "" +"Screencast showing how to re-position values on tree select like\n" +"fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Web" +#: ../system/objects/includes/reposition-values.include.rst:3 +msgid "" +"In order to re-arrange the field values, edit the field and scroll below the " +"values. Make sure to tick the option \"Use custom option sort\"." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.web}``" +#: ../system/objects/includes/reposition-values.include.rst:8 +msgid "" +"If you do not tick this field, all manual positioning you did above will be " +"lost upon saving! ☠️" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > VIP" +#: ../system/objects/includes/reposition-values.include.rst:11 +msgid "" +"Now use ☰ to drag the values in question to the correct position. When " +"you're ready, submit your changes to save the object attribute." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.vip}``" +#: :0 ../system/objects/types.rst:0 +msgid "Screencast showing how to re-position values" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Phone" +#: ../system/objects/includes/url-template-hint.include.rst:3 +msgid "" +"This field allows using :ref:`URL fields (Link Templates) `." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.phone}``" +#: ../system/objects/permissions.rst:2 +msgid "Attribute Permissions" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``004930123456789`` or empty if not set" +#: ../system/objects/permissions.rst:7 +msgid "" +"In the object attributes configuration you can define if a field is shown " +"and if the input in the field is mandatory, separated by different screens " +"and for different :doc:`roles/permissions `." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Note" +#: ../system/objects/permissions.rst:17 +msgid "Screenshot shows object attribute permission table" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.note}``" +#: ../system/objects/permissions.rst:17 +msgid "" +"Some of the possible permissions and screen options for a user object " +"attribute." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Some note to this user`` or empty if not set" +#: ../system/objects/permissions.rst:19 +msgid "" +"Based on the object context (ticket, agent, organization, user), the " +"selectable roles (to be precise: the required permissions) and screens " +"differ. Be aware that these settings aren't affecting data creation via " +"other channels than the UI." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Mobile" +#: ../system/objects/permissions.rst:24 +msgid "" +"If you want to have further customization possibilities, you should have a " +"look at the :doc:`core workflows `." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.mobile}``" +#: ../system/objects/permissions.rst:28 +msgid "Screens" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``0049176123456789`` or empty if not set" +#: ../system/objects/permissions.rst:30 +msgid "" +"In the table below you can find an overview about the different permissions " +"and the available screens Zammad distinguishes between." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Login" +#: ../system/objects/permissions.rst:37 +msgid "Screen" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.login}``" +#: ../system/objects/permissions.rst:38 +msgid "Available for" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Lastname" +#: ../system/objects/permissions.rst:40 +msgid "create" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.lastname}``" +#: ../system/objects/permissions.rst:41 ../system/objects/permissions.rst:52 +#: ../system/objects/permissions.rst:59 ../system/objects/permissions.rst:73 +msgid "admin.user" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Firstname" +#: ../system/objects/permissions.rst:42 ../system/objects/permissions.rst:53 +#: ../system/objects/permissions.rst:60 +msgid "admin.organization" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.firstname}``" +#: ../system/objects/permissions.rst:43 ../system/objects/permissions.rst:54 +#: ../system/objects/permissions.rst:61 +msgid "admin.group" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``John`` or empty if not set" +#: ../system/objects/permissions.rst:44 +msgid "Creation dialog for not yet existing data" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Fax" +#: ../system/objects/permissions.rst:45 +msgid "create_middle" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.fax}``" +#: ../system/objects/permissions.rst:46 ../system/objects/permissions.rst:50 +#: ../system/objects/permissions.rst:57 ../system/objects/permissions.rst:66 +#: ../system/objects/permissions.rst:70 +msgid "ticket.customer" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``004930123464789`` or empty if not set" +#: ../system/objects/permissions.rst:47 ../system/objects/permissions.rst:51 +#: ../system/objects/permissions.rst:58 ../system/objects/permissions.rst:69 +msgid "ticket.agent" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Email" +#: ../system/objects/permissions.rst:48 +msgid "Ticket create dialog (middle section)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.email}``" +#: ../system/objects/permissions.rst:49 +msgid "edit" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``jdoe@customer.tld``" +#: ../system/objects/permissions.rst:55 +msgid "Editing dialog for already existing data" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Department" +#: ../system/objects/permissions.rst:56 +msgid "view" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.department}``" +#: ../system/objects/permissions.rst:62 +msgid "View-only dialog for already existing data" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Sales`` or empty if not set" +#: ../system/objects/permissions.rst:64 +msgid "(e.g. user or organization from search)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Avatar" +#: ../system/objects/permissions.rst:65 +msgid "signup" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.avatar(60,60)}``" +#: ../system/objects/permissions.rst:67 +msgid "Sign-up screen for new customers" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "avatar picture with width and height in pixel (e.g. 60,60)" +#: ../system/objects/permissions.rst:68 +msgid "invite_customer" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Address" +#: ../system/objects/permissions.rst:71 +msgid "" +"Customer invitation screen (from :doc:`First Steps ` area)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.address}``" +#: ../system/objects/permissions.rst:72 +msgid "invite_agent" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Some street 1, 12345 Berlin`` or empty if not set" +#: ../system/objects/permissions.rst:74 +msgid "" +"Agent invitation screen (from :doc:`First Steps ` area)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated at" +#: ../system/objects/permissions.rst:78 +msgid "Screen Options" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_at}``" +#: ../system/objects/permissions.rst:80 +msgid "" +"For the different screens you can select \"show\" and \"required\" options." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC``" +#: ../system/objects/permissions.rst:82 +msgid "**shown:** Show (check) or hide (uncheck) a field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Phone" +#: ../system/objects/permissions.rst:83 +msgid "" +"**required:** Set a field to mandatory (check). Forces users (via UI and " +"API) to populate the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.phone}``" +#: ../system/objects/types.rst:7 +msgid "Example external data source" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Shared organization" +#: ../system/objects/types.rst:2 +msgid "Attribute types" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.shared}``" +#: ../system/objects/types.rst:4 +msgid "" +"When adding a new object attribute, you can choose between the following " +"attribute types." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Note" +#: ../system/objects/types.rst:14 +msgid "" +"You cannot change the attribute format / type as soon as it is applied. If " +"you no longer need an object attribute, consider disabling it instead of " +"removing." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.note}``" +#: ../system/objects/types.rst:18 +msgid "**What about the translation of my attributes?**" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``A note to the organization of the user`` or empty if not set" +#: ../system/objects/types.rst:20 +msgid "" +"For some attribute types you can decide if they should be translatable or " +"not. To be precise, it works only for the selectable fields because the " +"possible choices are known and limited. For the following attribute types, " +"you can set the translatable flag:" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Name" +#: ../system/objects/types.rst:25 +msgid "*Boolean field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.name}``" +#: ../system/objects/types.rst:26 +msgid "*Single selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``Zammad GmbH``" +#: ../system/objects/types.rst:27 +msgid "*Multiple selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Domain based assignment" +#: ../system/objects/types.rst:28 +msgid "*Single tree selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.domain_assignment}``" +#: ../system/objects/types.rst:29 +msgid "*Multiple tree selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Domain" +#: ../system/objects/types.rst:31 +msgid "" +"For these types, you can find an additional field *Translate field contents*:" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.domain}``" +#: ../system/objects/types.rst:0 +msgid "Screenshot showing translatable attribute types" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``zammad.com`` or empty if not set" +#: ../system/objects/types.rst:38 +msgid "Screenshot with example of translatable attribute type" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > VIP" +#: ../system/objects/types.rst:45 +msgid "Boolean field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.vip}``" +#: ../system/objects/types.rst:41 +msgid "" +"Provides a drop-down field with display values for ``true`` and ``false``. " +"Setting a default is mandatory." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Note" +#: ../system/objects/types.rst:0 +msgid "Available settings for Boolean fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.note}``" +#: ../system/objects/types.rst:55 +msgid "Date field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Mobile" +#: ../system/objects/types.rst:48 +msgid "Provides a date picker field and does not allow default values." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.mobile}``" +#: ../system/objects/types.rst:52 +msgid "Default time diff (hours)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Login" +#: ../system/objects/types.rst:51 +msgid "" +"This setting helps the user by highlighting the day from now plus the " +"provided value. It *does not* pre-fill the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.login}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Date fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Lastname" +#: ../system/objects/types.rst:73 +msgid "Date & time field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.lastname}``" +#: ../system/objects/types.rst:58 +msgid "Provides a date and time picker – does not allow default values" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Firstname" +#: ../system/objects/types.rst:62 +msgid "Allow future" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.firstname}``" +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the future." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Fax" +#: ../system/objects/types.rst:66 +msgid "Allow past" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.fax}``" +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the past." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Email" +#: ../system/objects/types.rst:70 +msgid "Default time diff (minutes)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.email}``" +#: ../system/objects/types.rst:69 +msgid "" +"This setting helps the user by highlighting the day from now plus the " +"provided value. It does not pre-fill the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Department" +#: ../system/objects/types.rst:0 +msgid "Available settings for Date & time fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.department}``" +#: ../system/objects/types.rst:86 +msgid "Integer field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Web" +#: ../system/objects/types.rst:76 +msgid "" +"Provides an input field that allows integer usage only. You may define a " +"default value. You cannot enforce comma separation." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.web}``" +#: ../system/objects/types.rst:80 +msgid "Minimal" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > VIP" +#: ../system/objects/types.rst:80 +msgid "The minimal value the field accepts." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.vip}``" +#: ../system/objects/types.rst:83 +msgid "Maximal" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Phone" +#: ../system/objects/types.rst:83 +msgid "The maximum value the field accepts." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.phone}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Integer fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Note" +#: ../system/objects/types.rst:99 +msgid "Multiple selection field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.note}``" +#: ../system/objects/types.rst:89 +msgid "" +"Provides a selection field that allows the selection of one or more out of " +"several. This field does allow setting a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Mobile" +#: ../system/objects/types.rst:0 +msgid "Available settings for Multiple selection fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.mobile}``" +#: ../system/objects/types.rst:112 +msgid "Single selection field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Login" +#: ../system/objects/types.rst:102 +msgid "" +"Provides a drop-down field that allows selection of one value out of " +"several. This field does allow setting a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.login}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Single selection fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Lastname" +#: ../system/objects/types.rst:142 +msgid "Textarea field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.lastname}``" +#: ../system/objects/types.rst:115 +msgid "" +"Provides a text area input field (multiple lines) and thus allows e.g. new " +"lines. You can set a default field value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Firstname" +#: ../system/objects/types.rst:120 +msgid "" +"Please note that this field *does not* support text formatting or HTML " +"content (rich text)." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.firstname}``" +#: ../system/objects/types.rst:123 +msgid "**🥵 This field can consume a lot of visual space**" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Fax" +#: ../system/objects/types.rst:125 +msgid "" +"Depending on where you use this field type, it may use a lot of visual space " +"if you provide a lot of text. This may be an issue to work with." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.fax}``" +#: ../system/objects/types.rst:130 +msgid "Default" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Email" +#: ../system/objects/types.rst:129 +msgid "" +"The here provided text will be shown within the text area field or new data " +"sets." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.email}``" +#: ../system/objects/types.rst:134 ../system/objects/types.rst:160 +msgid "Maxlength" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Department" +#: ../system/objects/types.rst:0 ../system/objects/types.rst:160 +msgid "You can pick the maximum length of the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.department}``" +#: ../system/objects/types.rst:0 +msgid "The default length of this object is ``500``." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Avatar" +#: ../system/objects/types.rst:139 +msgid "Rows" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.avatar(60,60)}``" +#: ../system/objects/types.rst:0 +msgid "" +"Change the number of rows to dislay so that you can use only the space you " +"really need." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Address" +#: ../system/objects/types.rst:0 +msgid "The default number of rows is ``4``." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.address}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Textarea fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created at" +#: ../system/objects/types.rst:165 +msgid "Text field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_at}``" +#: ../system/objects/types.rst:145 +msgid "Provides a text field (one line) and allows choosing a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Avatar" +#: ../system/objects/types.rst:148 +msgid "" +"Defines the type of the input field. This allows e.g. your browser to ensure " +"that you provide the specific type." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.avatar(60,60)}``" +#: ../system/objects/types.rst:152 +msgid "Currently available:" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Address" +#: ../system/objects/types.rst:155 +msgid "Phone" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.address}``" +#: ../system/objects/types.rst:156 +msgid "Text" msgstr "" -#: ../system/variables/ticket.rst:6 -msgid "" -"Below you can find all available ticket-based variables within Zammad. These " -"can be called via Triggers for example. If you're unsure if Zammad does " -"support variables at the point you're at, you can try to type ``::`` to " -"check." +#: ../system/objects/types.rst:157 +msgid "Url *(URL fields disable link-template availability)*" msgstr "" -#: ../system/variables/ticket.rst:12 -msgid "Ticket Variables" +#: ../system/objects/types.rst:0 +msgid "Available settings for Text fields" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Web" +#: ../system/objects/types.rst:174 +msgid "Single tree selection field" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.web}``" +#: ../system/objects/types.rst:168 +msgid "" +"Provides a select-like field with up to 6 layers of options. Does not allow " +"setting a default value." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > VIP" +#: ../system/objects/types.rst:0 +msgid "Available settings for Tree Select fields" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.vip}``" +#: ../system/objects/types.rst:183 +msgid "Multiple tree selection field" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Phone" +#: ../system/objects/types.rst:177 +msgid "" +"Provides a select-like field with up to 6 layers of options allowing the " +"selection of multiple values. Does not allow setting a default value." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.phone}``" +#: ../system/objects/types.rst:302 +msgid "External Data Source field" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Note" +#: ../system/objects/types.rst:186 +msgid "" +"Provides a searchable field which fetches data from an external system. This " +"can be useful if you have data outside of Zammad and don't want to maintain " +"both data sources." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.note}``" +#: ../system/objects/types.rst:190 +msgid "The feature works as follows:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Mobile" +#: ../system/objects/types.rst:192 +msgid "" +"Zammad sends a query with a search string (free text from agent or based on " +"a variable) in a pre-defined format (\"Search URL\") to an external system." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.mobile}``" +#: ../system/objects/types.rst:195 +msgid "" +"This external system searches for matches and provides a response as a JSON " +"structure to Zammad." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Login" +#: ../system/objects/types.rst:197 +msgid "" +"Zammad just looks for the defined list and value keys, reads the content and " +"displays the value to the user. There is no search on Zammad side." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.login}``" +#: ../system/objects/types.rst:201 +msgid "" +"The usage of a PostgreSQL database for Zammad is required. In any other " +"case, Zammad will hide the external data source type and you are not able to " +"use it. If you want to use this feature, consider to :docs:`migrate your " +"database `." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Lastname" +#: ../system/objects/types.rst:205 +msgid "Currently, only ``GET`` is supported as request method." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.lastname}``" +#: ../system/objects/types.rst:206 +msgid "" +"The data structure must be in JSON format and provide the objects in an " +"array." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Firstname" +#: ../system/objects/types.rst:208 +msgid "" +"The endpoint for the external data source has to support search. On Zammad " +"side, there is no search/logic implemented; however, you can define the " +"output key and value based on the result(s) from the response (which " +"provides already filtered content based on the search)." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.firstname}``" +#: ../system/objects/types.rst:212 +msgid "" +"If you receive more results as expected, your external data source search " +"may not work properly or the structure of the URL is not correct. You should " +"get in touch with a responsible person from the external system." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Fax" +#: ../system/objects/types.rst:217 +msgid "" +"Please have a look :doc:`at our example `, where you can find a possible configuration for a public " +"dummy endpoint." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.fax}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for external data source fields" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Email" +#: ../system/objects/types.rst:242 +msgid "Search URL" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.email}``" +#: ../system/objects/types.rst:227 +msgid "" +"Set your endpoint where Zammad fetches the data. Please make sure to include " +"a valid search :doc:`variable ` as an URL parameter. " +"Example for a free text search at user input: ``#{search.term}``" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Department" +#: ../system/objects/types.rst:232 +msgid "" +"If in doubt, ask the responsible person for the external data source how " +"they expect the structure of the URL." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.department}``" +#: ../system/objects/types.rst:236 +msgid "" +"Depending on your search variable, the preview might work or not. The reason " +"is that the context might not be available and it is no bug." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Avatar" +#: ../system/objects/types.rst:239 +msgid "" +"Please also make sure to use a variable which is available in your object " +"context. For example you won't be able to search for a ticket in a user " +"object context." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.avatar(60,60)}``" +#: ../system/objects/types.rst:252 +msgid "SSL Verification" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Address" +#: ../system/objects/types.rst:245 +msgid "Here you can switch the SSL verification to no." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.address}``" +#: ../system/objects/types.rst:249 +msgid "" +"If your external data source system is using self signed certificates, " +"please have a look :doc:`here ` for " +"further information about how to handle them in Zammad, so you can keep the " +"SSL verification activated." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated at" +#: ../system/objects/types.rst:258 +msgid "HTTP Authentication" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_at}``" +#: ../system/objects/types.rst:255 +msgid "" +"If your external data source requires an authentication, you can set it " +"here. You can leave it empty or choose between *Basic Authentication* or " +"*Authentication Token* (selecting one of the two methods leads to additional " +"fields where you can enter your credentials/token)." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Title" +#: ../system/objects/types.rst:265 +msgid "Search result list key" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.title}``" +#: ../system/objects/types.rst:261 +msgid "" +"Defines the level in the JSON structure which provides the list with search " +"results. You can leave it empty, if the data is already provided as an " +"array. If you have to go deeper in the structure, you can provide a path " +"with ``.`` as separators, e.g. ``key.subkey.sub-sub-key``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "" -"``My amazing Subject`` (normally subject, can be edited within Interface and " -"thus differ)" +#: ../system/objects/types.rst:271 +msgid "Search result value key" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Accounted Time" +#: ../system/objects/types.rst:268 +msgid "" +"Defines the attribute in the structure in which your external data source " +"provides the *value* for your data. An example would be a product *number*. " +"If you have to go deeper in the structure, you can provide a path with ``.`` " +"as separators, e.g. ``key.subkey.sub-sub-key``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.time_unit}``" +#: ../system/objects/types.rst:277 +msgid "Search result label key" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``1``, ``2.75`` or empty response" +#: ../system/objects/types.rst:274 +msgid "" +"Defines the attribute in the structure in which your external data source " +"provides the *label* for your data. An example would be a product *name*. If " +"you have to go deeper in the structure, you can provide a path with ``.`` as " +"separators, e.g. ``key.subkey.sub-sub-key``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Tags" +#: ../system/objects/types.rst:280 +msgid "" +"In the preview area, you can find the following items (depending on your " +"configuration above):" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.tags}``" +#: ../system/objects/types.rst:283 +msgid "" +"**Error/hint message** (only if configuration is not complete): Zammad tells " +"you, if there is a problem and what you should change in your configuration." msgstr "" -#: ../system/variables/ticket.rst:1 +#: ../system/objects/types.rst:286 msgid "" -"Currently not available, see `Issue 2769 `_" +"**Search field**: search for an existing attribute in the data source to get " +"a preview. This is required for the fields below to show up." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > State > Name" +#: ../system/objects/types.rst:288 +msgid "" +"**Search result response** (only if configuration is not complete): here you " +"can find a syntax highlighted JSON preview of the response, based on the " +"search term you entered." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.state.name}``" +#: ../system/objects/types.rst:291 +msgid "" +"**Search result list** (only if *search result list key* is properly set): " +"output of the structure under the configured *search result list key*." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``new``, ``open``, ..." +#: ../system/objects/types.rst:294 +msgid "" +"**Preview table** (when fully configured): Zammad shows you a table which " +"includes the found items based on the search string (value, label and " +"optional link). You can use this preview if you don't have the complete data " +"structure of the external system in mind." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Priority > Name" +#: ../system/objects/types.rst:299 +msgid "" +"An example of a configured external data source field from agent perspective:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.priority.name}``" +#: ../system/objects/types.rst:0 +msgid "Screencast showing the search for a product in a ticket" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2 normal``" +#: ../system/objects/types.rst:307 +msgid "URL fields (Link-Template)" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Pending till" +#: ../system/objects/types.rst:311 +msgid "" +"This function is restricted to Text, Select and External data source types " +"only." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.pending_time}``" +#: ../system/objects/types.rst:314 +msgid "" +"Link-Templates are an amazing way to dynamically generate URLs. They allow " +"you to integrate other systems better without having to manually copy data " +"from Zammad if possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not set" +#: ../system/objects/types.rst:320 +msgid "" +"Another great way of communicating with another system may be Zammad's :doc:" +"`Webhooks `." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Web" +#: ../system/objects/types.rst:323 +msgid "" +"After filling a link-template enabled field, an URL icon will appear on its " +"right. Clicking on the icon opens a new tab." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.web}``" +#: ../system/objects/types.rst:328 +msgid "" +"Even though Zammad displays the link template within object edit and create " +"screens, the function is optional. It's only active if you populate the " +"field." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``https://zammad.com`` or empty if not set" +#: ../system/objects/types.rst:333 +msgid "" +"What's the difference between URL and text fields with link template...?!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > VIP" +#: ../system/objects/types.rst:335 +msgid "" +"Both fields have different use cases. Use ``text`` type text fields when " +"ever you have a *static* url that requires dynamic parameters. If you " +"require a drag & drop like field that you can put in any URL, use ``URL`` " +"type text fields." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.vip}``" +#: ../system/objects/types.rst:340 +msgid "" +"The difference is easier to spot when comparing the fields directly, below " +"screencast shows the result - the dynamic approach uses existing values in " +"the moment of updating to built the URL - e.g. ``https://google.com/search?" +"q=cookies`` - while the URL approach uses the actual URL of the field - e.g. " +"``https://zammad.com``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Phone" +#: ../system/objects/types.rst:None +msgid "" +"Screencast showing the differents in between URL and text type fields with " +"actual values" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.phone}``" +#: ../system/objects/types.rst:352 +msgid "How does this work...?!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Note" +#: ../system/objects/types.rst:354 +msgid "" +"As an example, let's say you have an attribute called ``amazing_attribute`` " +"and you want to open a google search directly with the input from that field." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.note}``" +#: ../system/objects/types.rst:357 +msgid "" +"Providing the link-template field below allows you to do so: ``https://www." +"google.com/search?q=#{ticket.amazing_attribute}``" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Mobile" +#: ../system/objects/types.rst:362 +msgid "" +"You can use any :doc:`Zammad variable ` as long as it's " +"available in the moment you need it." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.mobile}``" +#: ../system/objects/types.rst:365 +msgid "" +"As a result, you are redirected to Google with a search for the value of the " +"attribute, if you click on the button in the ticket (as you can see in the " +"screencast above)." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Login" +#: ../system/packages.rst:2 +msgid "Packages" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.login}``" +#: ../system/packages.rst:4 +msgid "That's the package management-area." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``agent``" +#: ../system/packages.rst:6 +msgid "Individual add-ons for Zammad can be installed and managed here." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Lastname" +#: ../system/sessions.rst:2 +msgid "Sessions" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.lastname}``" +#: ../system/sessions.rst:4 +msgid "" +"Sessions management allows reviewing currently known user sessions and " +"allows to end these. The session timeout is affected by :ref:" +"`security_session_timeout` configurations from security settings." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Mustermann`` or empty if not set" +#: ../system/sessions.rst:None +msgid "Screenshot showing Zammad's session management" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Firstname" +#: ../system/sessions.rst:13 +msgid "Zammad will provide the following information:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.firstname}``" +#: ../system/sessions.rst:16 +msgid "" +"The user account this session entry belongs to. It can be normal if a user " +"has several sessions in the list. This can be due to changed browser " +"information or if you use e.g. single sign on methods where the user does " +"not use the log off button." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Max`` or empty if not set" +#: ../system/sessions.rst:22 +msgid "Browser" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Fax" +#: ../system/sessions.rst:22 +msgid "The browser agent communicated to Zammad." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.fax}``" +#: ../system/sessions.rst:40 +msgid "Location" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Email" +#: ../system/sessions.rst:25 +msgid "" +"The anticipated location based on the users IP address. Depending on the IP " +"address the result shown may differ. This option depends on :doc:`/settings/" +"system/services`." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.email}``" +#: ../system/sessions.rst:29 +msgid "The following information can be shown:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``agent@company.tld`` or empty if not set" +#: ../system/sessions.rst:33 +msgid "IP address" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Department" +#: ../system/sessions.rst:32 +msgid "" +"Either if you set *Geo IP services* to inactive or you're using internal IP " +"address which do not provide location information." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.department}``" +#: ../system/sessions.rst:40 +msgid "Country (or Country + City)" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Support`` or empty if not set" +#: ../system/sessions.rst:36 +msgid "" +"If *Geo IP services* is enabled only. Depends on how detailed the available " +"IP address information are." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Avatar" +#: ../system/sessions.rst:39 +msgid "" +"Be aware that results can be inaccurate - this technically is not an error." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.avatar(60,60)}``" +#: ../system/sessions.rst:43 +msgid "Age" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Address" +#: ../system/sessions.rst:43 +msgid "Provides the time when the session initially has been created." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.address}``" +#: ../system/sessions.rst:50 +msgid "Update" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Shared organization" +#: ../system/sessions.rst:46 +msgid "" +"Provides the time the user used this session to open Zammad. This timestamp " +"is only updated if the user e.g. reloads, not during normal work on tickets." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.shared}``" +#: ../system/sessions.rst:50 +msgid "This timestamp is being used for the session timeout." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Note" +#: ../system/sessions.rst:53 +msgid "" +"Use the delete button to remove a single session on behalf of your user." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.note}``" +#: ../system/subscription.rst:2 +msgid "Subscription (SaaS)" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Name" +#: ../system/subscription.rst:4 +msgid "" +"The subscription settings page allows you to configure your instances " +"package and number of agents required." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.name}``" +#: ../system/subscription.rst:9 +msgid "" +"This setting section is only available for Hosted setups. If you're looking " +"for on premise support contracts, please see the `Zammad pricing page " +"`_." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Zammad GmbH`` or empty if not set" +#: ../system/subscription.rst:14 ../system/subscription.rst:34 +msgid "Plan" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Domain based assignment" +#: ../system/subscription.rst:16 +msgid "" +"Here you can set up everything affecting your instance subscription " +"functions like number of agents and package." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.domain_assignment}``" +#: ../system/subscription.rst:19 +msgid "" +"On top of the page you can find a subscription summary. You'll find the " +"number of used and available (booked) agent seats there. By using the *see " +"more* link you can also expand an agent list to see the currently configured " +"active agents. This list *does not* count accounts with admin permissions " +"only." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Domain" +#: ../system/subscription.rst:None +msgid "" +"Within subscription you can always see how many agents are still\n" +"available to add and who uses the seats." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.domain}``" +#: ../system/subscription.rst:29 +msgid "" +"Learn more on how to manage your agents in general :doc:`here `." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``domain.tld`` or empty if not set" +#: ../system/subscription.rst:36 +msgid "" +"This section gives you an overview of the available plans and their " +"functions / limits. If you require a more detailed table, check our " +"`detailed pricing table `_ for more." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > VIP" +#: ../system/subscription.rst:40 +msgid "" +"Your selection in this step will decide on the base agent price and e.g. " +"agent limits that might apply in the summary step." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.vip}``" +#: ../system/subscription.rst:43 +msgid "" +"The green *Selected* button will also tell you what plan you're currently in." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Number" +#: ../system/subscription.rst:47 +msgid "" +"Trial instances are running at Professional with 3 agents. The plan cannot " +"be changed during the trial for technical reasons, if you require more " +"agents for testing, please contact `our sales team `_ with a reason for the raise request." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.number}``" +#: ../system/subscription.rst:None +msgid "" +"Screenshot showing three available packages for a hosted Zammad\n" +"instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``31001``, ``201910731001``, ..." +#: ../system/subscription.rst:57 +msgid "" +"At the bottom of this block you can find a summary where you can adjust the " +"settings of the previous selected plan." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > ID" +#: ../system/subscription.rst:62 +msgid "" +"Note that upgrading (more agents, higher package) is always possible, " +"however, downgrading will only happen when your billing period renews." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.id}``" +#: ../system/subscription.rst:66 +msgid "" +"Upgrading resets your billing period and existing credit will be deducted " +"from the new total." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``17``, ``5281``, ..." +#: ../system/subscription.rst:75 +msgid "Billing cycle" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact (customer)" +#: ../system/subscription.rst:70 +msgid "" +"You can choose between either monthly or yearly billing. The price per agent " +"will be cheaper if you decide for yearly billing." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_customer_at}``" +#: ../system/subscription.rst:73 +msgid "" +"If you're still trying out things and are unsure of the right package for " +"your instance, you may want to choose monthly first and then upgrade to " +"yearly when you're sure." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "" -"``2019-10-07 16:25:00 UTC`` or empty if not applicable yet (Please note " -"`Ticket last contact behavior Settings `_ for this)" +#: ../system/subscription.rst:83 +msgid "Plan: (Starter|Professional|Plus) - Agents" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact" +#: ../system/subscription.rst:78 +msgid "Choose the number of agents you require for your instance." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_at}``" +#: ../system/subscription.rst:80 +msgid "" +"Keep in mind that some packages may have agent limits. Depending on the " +"previous chosen package, you won't be able to exceed specific agent numbers. " +"Also note that setting less agents than currently configured is not possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact (agent)" +#: ../system/subscription.rst:86 +msgid "Total" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_agent_at}``" +#: ../system/subscription.rst:86 +msgid "This will be the net total you're going to be billed." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable yet" +#: ../system/subscription.rst:88 +msgid "" +"By using the *Update subscription* button, the instance package will be " +"adjusted immediately. If you didn't provide a payment method yet, Zammad " +"will request you to provide one at this point." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Note" +#: ../system/subscription.rst:94 +msgid "" +"In case you're still within the trial period, this means that the trial will " +"be over immediately!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.note}``" +#: ../system/subscription.rst:97 +msgid "Down- or upgrading during the trial period *is not* possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Note about this group``" +#: ../system/subscription.rst:None +msgid "Screenshot showing payment options and a pricing summary" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Name" +#: ../system/subscription.rst:103 +msgid "Billing Information" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.name}``" +#: ../system/subscription.rst:105 +msgid "" +"You can control all billing relevant information like invoices, billing " +"address and the option to cancel your subscription." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Sales``" +#: ../system/subscription.rst:108 +msgid "" +"All adjusted billing information below only affect future invoices. If your " +"invoice was issued wrong, please contact `our sales team `_." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Follow-up possible" +#: ../system/subscription.rst:114 +msgid "Billing address" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.follow_up_possible}``" +#: ../system/subscription.rst:113 +msgid "" +"Provide your company address here, make sure to include the companies name " +"in case required. This address will be referenced on your invoice." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``no`` or ``yes``" +#: ../system/subscription.rst:118 +msgid "VAT ID" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Assign Follow-Ups" +#: ../system/subscription.rst:117 +msgid "" +"Provide your VAT ID here. If applicable your invoice will not contain German " +"VAT. Please make sure to pay the VAT in your country as required." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.follow_up_assignment}``" +#: ../system/subscription.rst:127 +msgid "Billing Email Address" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Assignment Timeout" +#: ../system/subscription.rst:121 +msgid "" +"Usually the instance owner (the person that registered the instance) will " +"receive all emails including the invoices. In case you have your own billing " +"department, you can provide their email address here." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.assignment_timeout}``" +#: ../system/subscription.rst:125 +msgid "" +"All billing relevant information will then be sent to this email address." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``20`` or empty if not configured" +#: ../system/subscription.rst:127 +msgid "Invoices are sent as attachment (PDF) to this email address." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > First response" +#: ../system/subscription.rst:129 +msgid "" +"Don't forget to press the *Update billing information* button after you " +"changed above settings." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.first_response_at}``" +#: ../system/subscription.rst:None +msgid "" +"Screenshot showing options for billing information within the\n" +"subscription menu" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Escalation at" +#: ../system/subscription.rst:137 +msgid "Payment Method" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.escalation_at}``" +#: ../system/subscription.rst:139 +msgid "You can pay via credit card or SEPA mandate." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable" +#: ../system/subscription.rst:144 +msgid "Credit card" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Web" +#: ../system/subscription.rst:142 +msgid "" +"Simply follow the dialogue by clicking *authorize credit card* and confirm -" +"if required by your bank- your consent to Zammad using your card for the " +"payments." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.web}``" +#: ../system/subscription.rst:148 +msgid "SEPA Direct Debit" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > VIP" +#: ../system/subscription.rst:147 +msgid "" +"Provide the requested information of the bank account holder and update if " +"you're ready. You'll then receive an email with the SEPA mandate." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.vip}``" +#: ../system/subscription.rst:150 +msgid "" +"Technically there's also the possibility to pay via invoice, however - this " +"method only applies to a fairly low number of instances. Please contact `our " +"sales team `_ for more information." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Phone" +#: ../system/subscription.rst:156 +msgid "Cancel Subscription" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.phone}``" +#: ../system/subscription.rst:158 +msgid "" +"Do you want to cancel your subscription? In case you no longer want to use " +"Zammad's SaaS, you can cancel your subscription by using the red *Yes, " +"please cancel my subscription* button." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Note" +#: ../system/subscription.rst:162 +msgid "" +"To cancel the description, enter the FQDN of your Zammad instance and " +"provide a reason for your cancellation." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.note}``" +#: ../system/subscription.rst:165 +msgid "" +"Your subscription will end the day after your trial or billing period ends." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Mobile" +#: ../system/subscription.rst:None +msgid "Screenshot showing subscription cancellation dialog" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.mobile}``" +#: ../system/subscription.rst:174 +msgid "" +"We will remind you about your cancelled subscription several times up front. " +"After the subscription ended all instance data will be removed. A restore " +"*is not* possible after that point!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Login" +#: ../system/subscription.rst:178 +msgid "**😖 Cancelled by accident?**" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.login}``" +#: ../system/subscription.rst:180 +msgid "" +"You can always undo the cancellation via the *Yes, undo the cancellation of " +"my subscription* button up to the last subscription day!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Lastname" +#: ../system/subscription.rst:0 +msgid "" +"Screenshot showing a red button to cancel the subscription\n" +"cancellation" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.lastname}``" +#: ../system/subscription.rst:189 +msgid "Payment History" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Firstname" +#: ../system/subscription.rst:191 +msgid "" +"The payment history will display a history of all paid invoices. At this " +"point you can also download these in case you need them again." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.firstname}``" +#: ../system/subscription.rst:196 +msgid "" +"You will only find *paid* invoices here. Invoices that are to be billed are " +"not available before the payment is completed." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Fax" +#: ../system/subscription.rst:201 +msgid "Date" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.fax}``" +#: ../system/subscription.rst:201 +msgid "Date of the invoice creation." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Email" +#: ../system/subscription.rst:204 +msgid "Amount" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.email}``" +#: ../system/subscription.rst:204 +msgid "Invoice total including VAT if applicable." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Department" +#: ../system/subscription.rst:207 +msgid "" +"Contains contract period (monthly or yearly) and hosted plan for the " +"subscription period in question." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.department}``" +#: ../system/subscription.rst:218 +msgid "Payment method / Service period" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Avatar" +#: ../system/subscription.rst:211 +msgid "" +"Used bank account or credit card as well as the subscription period the " +"invoice is about." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.avatar(60,60)}``" +#: ../system/subscription.rst:216 +msgid "" +"It might happen that the invoice date and subscription period differ. This " +"is nothing to worry about, the subscription periods will be accounted later " +"on." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Address" +#: ../system/subscription.rst:222 +msgid "Receipt" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.address}``" +#: ../system/subscription.rst:221 +msgid "" +"Use the arrow to download the invoice in question. You can download all " +"available invoices any time you need to here!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Web" +#: ../system/subscription.rst:None +msgid "Screenshot showing payment history of a hosted instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.web}``" +#: ../system/subscription.rst:229 +msgid "FAQ" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > VIP" +#: ../system/subscription.rst:233 +msgid "I set up a trial account but am missing functions to test" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.vip}``" +#: ../system/subscription.rst:232 +msgid "" +"The trial instance is running within the professional package allowing up to " +"three agents." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Phone" +#: ../system/subscription.rst:236 +msgid "Can I change package within the trial?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.phone}``" +#: ../system/subscription.rst:236 +msgid "No. As soon as the package is changed the subscription begins." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Note" +#: ../system/subscription.rst:241 +msgid "What happens to my trial instance after the trial period ended?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.note}``" +#: ../system/subscription.rst:239 +msgid "" +"Your instance will automatically be canceled for you. Please see *What " +"happens to my instance after it has been canceled?* for more." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Mobile" +#: ../system/subscription.rst:254 +msgid "What happens to my instance after it has been canceled?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.mobile}``" +#: ../system/subscription.rst:244 +msgid "That depends slightly on your instance state:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Login" +#: ../system/subscription.rst:250 +msgid "Trial instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.login}``" +#: ../system/subscription.rst:247 +msgid "" +"If you're still on trial, we will ice your instance and remind you once " +"again about your instance. We then will wait some days and remove your " +"instance from our system. This is the last time we will inform you by Email." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Lastname" +#: ../system/subscription.rst:254 +msgid "Paid instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.lastname}``" +#: ../system/subscription.rst:253 +msgid "" +"If you're a paying customer and canceled your subscription, the instance " +"removal will take place the day after your last subscription day." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Firstname" +#: ../system/subscription.rst:256 +msgid "Can removed instances be restored?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.firstname}``" +#: ../system/subscription.rst:257 +msgid "No. Once your instance has been removed, a restoration is not possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Fax" +#: ../system/system-report.rst:2 +msgid "System Report" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.fax}``" +#: ../system/system-report.rst:4 +msgid "" +"In this place you can't configure Zammad. Instead you can obtain a system " +"report about Zammad and its configuration." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Email" +#: ../system/system-report.rst:7 +msgid "" +"See the description in Zammad for an explanation. You can even find a " +"preview of the included data below the **Download** button." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.email}``" +#: ../system/system-report.rst:10 +msgid "" +"Zammad never sends this automatically to anyone. It is a manual process only " +"to provide better support based on your configuration." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Department" +#: ../system/translations.rst:2 +msgid "Translations" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.department}``" +#: ../system/translations.rst:4 +msgid "" +"Translations of Zammad are processed centrally in our `Weblate instance " +"`_. This allows non-developers to review " +"and update translation texts of the language they actually speak." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Avatar" +#: ../system/translations.rst:9 +msgid "" +"Your language is in an incomplete translation state or has typos? Please " +"consider helping us in sorting this out! All you need is either a GitHub " +"account or to register directly in our instance." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.avatar(60,60)}``" +#: ../system/translations.rst:13 +msgid "" +"Did you know? This is also where the documentation translations are handled. " +"🤓" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Address" +#: ../system/translations.rst:15 +msgid "" +"Have a look in our :docs:`contribution section ` in the system documentation to get started!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.address}``" +#: ../system/translations.rst:20 +msgid "Local Translations" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created at" +#: ../system/translations.rst:22 +msgid "" +"Apart from these system translations, there's still local translations you " +"can manage. This is relevant if you added custom objects that require " +"translations or even custom states and priorities." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_at}``" +#: ../system/translations.rst:None +msgid "Translation management screen within the admin menu" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "2019-10-07 16:25:00 UTC" +#: ../system/translations.rst:31 +msgid "Updating Translations" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Closing time" +#: ../system/translations.rst:33 +msgid "" +"Because of how Zammad ships translations, the only way to update the system " +"translations is to update your Zammad installation. The benefit of this is " +"that you no longer need internet access during a Zammad upgrade as the " +"package has everything it requires already." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.close_at}``" +#: ../system/translations.rst:39 +msgid "Translation of Custom Objects" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "2019-10-07 17:25:00 UTC" +#: ../system/translations.rst:41 +msgid "" +"No problem at all! You can customize any translation locally, even if it is " +"not initially provided by the system." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``3``, any number of articles existing in the ticket right now" +#: ../system/translations.rst:44 +msgid "" +"Translation is supported for a broad number of features, including but not " +"limited to custom:" msgstr "" -#: ../system/version.rst:2 -msgid "Version" +#: ../system/translations.rst:47 +msgid "Object Attributes" msgstr "" -#: ../system/version.rst:4 -msgid "Shows which version is currently being used on your Zammad-instance." +#: ../system/translations.rst:48 +msgid "Ticket Macros" msgstr "" -#: ../manage/roles/admin-permissions.rst:53 -msgid "``admin.checklist``" +#: ../system/translations.rst:49 +msgid "Ticket Overviews" msgstr "" -#: ../manage/roles/admin-permissions.rst:54 -msgid ":doc:`Manage > Checklist `" +#: ../system/translations.rst:50 +msgid "Ticket Priorities" msgstr "" -#: ../manage/roles/admin-permissions.rst:83 -msgid "``admin.channel_whatsapp``" +#: ../system/translations.rst:51 +msgid "Ticket States" msgstr "" -#: ../manage/roles/admin-permissions.rst:84 -msgid ":doc:`Channels > Whatsapp `" +#: ../system/translations.rst:54 +msgid "Customizing Translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:124 -msgid "``admin.public_links``" +#: ../system/translations.rst:56 +msgid "" +"Within the translation screen, simply click on the **New Translation** " +"button." msgstr "" -#: ../manage/roles/admin-permissions.rst:125 -msgid ":doc:`Manage > Public Links `" +#: ../system/translations.rst:None +msgid "New translation dialog" msgstr "" -#: ../manage/roles/admin-permissions.rst:151 -msgid "``admin.system_report``" +#: ../system/translations.rst:62 +msgid "" +"In the dialog you can immediately enter the exact translation source (if you " +"know it) and your custom translation text for it and click **Submit**." msgstr "" -#: ../manage/roles/admin-permissions.rst:152 -msgid ":doc:`System > System Report `" +#: ../system/translations.rst:65 +msgid "" +"Alternatively, try to search for translation suggestions in the list below. " +"Selecting an item from the list will pre-fill the translation source for you " +"and then you can just enter your custom translation." msgstr "" -#: ../manage/roles/admin-permissions.rst:166 -msgid "``admin.ticket_auto_assignment``" +#: ../system/translations.rst:69 +msgid "" +"The target language will always default to your current language selection. " +"If you need to translate for a different language, simply change the " +"selection before submitting." msgstr "" -#: ../manage/roles/admin-permissions.rst:167 -msgid ":ref:`Settings > Ticket > Auto Assignment `" +#: ../system/translations.rst:73 +msgid "" +"All your custom translations will show up in the overview table when added. " +"And they will even persist across Zammad updates!" msgstr "" -#: ../manage/roles/admin-permissions.rst:169 -msgid "``admin.ticket_duplicate_detection``" +#: ../system/translations.rst:76 +msgid "" +"Make sure to reload your browser if a translated string is not displayed." msgstr "" -#: ../manage/roles/admin-permissions.rst:170 -msgid ":ref:`Settings > Ticket > Duplicate Detection `" +#: ../system/translations.rst:80 +msgid "Reverting to Original Translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:172 -msgid "``admin.ticket_priority``" +#: ../system/translations.rst:82 +msgid "" +"If you want to revert a custom translation to original text, simply use the " +"appropriate action within the row of the overview table." msgstr "" -#: ../manage/roles/admin-permissions.rst:173 -msgid ":ref:`System > Objects >Ticket Priority `" +#: ../system/translations.rst:85 +msgid "" +"Depending on the type of the translation source, the action has a slightly " +"different name:" msgstr "" -#: ../manage/roles/admin-permissions.rst:175 -msgid "``admin.ticket_state``" +#: ../system/translations.rst:88 +msgid "**Reset** for customized system translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:176 -msgid ":ref:`System > Objects >Ticket State `" +#: ../system/translations.rst:89 +msgid "**Remove** for customized local translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:193 -msgid "``admin.webhook``" +#: ../system/translations.rst:91 +msgid "" +"In both cases, the action will remove the customized translation after a " +"confirmation." msgstr "" -#: ../manage/roles/admin-permissions.rst:194 -msgid ":doc:`Manage > Webhook `" +#: ../system/translations.rst:None +msgid "Screenshot showing the location of the Remove action" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:43 -msgid "``user_preferences.appearance``" +#: ../system/translations.rst:99 +msgid "Inline Translations" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:44 -msgid "Appearance configuration" +#: ../system/translations.rst:101 +msgid "" +"If you prefer a more hands-on approach, you can activate the inline or on-" +"screen translation feature by pressing ``ctrl`` + ``alt`` + ``t`` at any " +"time and on any screen." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:0 -msgid "Users can switch between dark, light and" +#: ../system/translations.rst:105 +msgid "" +"All customizable translation texts will be highlighted for you on the " +"screen. Just click into the highlighted area and update the text in place." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:0 -msgid "automatic mode." +#: ../system/translations.rst:None +msgid "Inline translation mode activated for the Overview screen" msgstr "" -#: ../system/system-report.rst:2 -msgid "System Report" +#: ../system/translations.rst:112 +msgid "" +"When finished editing, simply press ``ctrl`` + ``alt`` + ``t`` again to " +"deactivate." msgstr "" -#: ../system/system-report.rst:4 +#: ../system/translations.rst:117 msgid "" -"In this place you can't configure Zammad. Instead you can obtain a system " -"report about Zammad and its configuration." +"Even though it's available on any screen, the inline translation feature " +"requires admin permissions. It works only for the current language " +"selection. If you need to translate a different language, first change the " +"language in your :user-docs:`profile settings `." msgstr "" -#: ../system/system-report.rst:7 -msgid "" -"See the description in Zammad for an explanation. You can even find a " -"preview of the included data below the **Download** button." +#: ../system/version.rst:2 +msgid "Version" msgstr "" -#: ../system/system-report.rst:10 -msgid "" -"Zammad never sends this automatically to anyone. It is a manual process only " -"to provide better support based on your configuration." +#: ../system/version.rst:4 +msgid "Shows which version is currently being used on your Zammad-instance." msgstr "" diff --git a/locale/fr/LC_MESSAGES/admin-docs.po b/locale/fr/LC_MESSAGES/admin-docs.po index e75d1f7c..d7fb9147 100644 --- a/locale/fr/LC_MESSAGES/admin-docs.po +++ b/locale/fr/LC_MESSAGES/admin-docs.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Zammad\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-11-06 10:31+0100\n" +"POT-Creation-Date: 2024-11-12 16:31+0100\n" "PO-Revision-Date: 2024-10-08 00:00+0000\n" "Last-Translator: Misha \n" "Language-Team: French Checklist `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:56 msgid "``admin.channel_email``" msgstr "" -#: ../manage/roles/admin-permissions.rst:54 #: ../manage/roles/admin-permissions.rst:57 msgid ":doc:`Channels > Email `" msgstr "" -#: ../manage/roles/admin-permissions.rst:56 #: ../manage/roles/admin-permissions.rst:59 msgid "``admin.channel_facebook``" msgstr "" -#: ../manage/roles/admin-permissions.rst:57 #: ../manage/roles/admin-permissions.rst:60 msgid ":doc:`Channels > Facebook `" msgstr "" -#: ../manage/roles/admin-permissions.rst:58 #: ../manage/roles/admin-permissions.rst:61 msgid "" "Accessing Facebook tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:59 #: ../manage/roles/admin-permissions.rst:62 msgid "``admin.channel_formular``" msgstr "" -#: ../manage/roles/admin-permissions.rst:60 #: ../manage/roles/admin-permissions.rst:63 msgid ":doc:`Channels > Form `" msgstr "" -#: ../manage/roles/admin-permissions.rst:62 #: ../manage/roles/admin-permissions.rst:65 msgid "``admin.channel_google``" msgstr "" -#: ../manage/roles/admin-permissions.rst:63 #: ../manage/roles/admin-permissions.rst:66 msgid ":doc:`Channels > Google `" msgstr "" -#: ../manage/roles/admin-permissions.rst:65 #: ../manage/roles/admin-permissions.rst:68 msgid "``admin.channel_microsoft365``" msgstr "" -#: ../manage/roles/admin-permissions.rst:66 #: ../manage/roles/admin-permissions.rst:69 msgid ":doc:`Channels > Microsoft 365 `" msgstr "" -#: ../manage/roles/admin-permissions.rst:68 #: ../manage/roles/admin-permissions.rst:71 msgid "``admin.channel_sms``" msgstr "" -#: ../manage/roles/admin-permissions.rst:69 #: ../manage/roles/admin-permissions.rst:72 msgid ":doc:`Channels > SMS `" msgstr "" -#: ../manage/roles/admin-permissions.rst:71 #: ../manage/roles/admin-permissions.rst:74 msgid "``admin.channel_telegram``" msgstr "" -#: ../manage/roles/admin-permissions.rst:72 #: ../manage/roles/admin-permissions.rst:75 msgid ":doc:`Channels > Telegram `" msgstr "" -#: ../manage/roles/admin-permissions.rst:73 #: ../manage/roles/admin-permissions.rst:76 msgid "" "Accessing Telegram tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:74 #: ../manage/roles/admin-permissions.rst:77 msgid "``admin.channel_twitter``" msgstr "" -#: ../manage/roles/admin-permissions.rst:75 #: ../manage/roles/admin-permissions.rst:78 msgid ":doc:`Channels > Twitter `" msgstr "" -#: ../manage/roles/admin-permissions.rst:76 #: ../manage/roles/admin-permissions.rst:79 msgid "" "Accessing Twitter/X tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:77 #: ../manage/roles/admin-permissions.rst:80 msgid "``admin.channel_web``" msgstr "" -#: ../manage/roles/admin-permissions.rst:78 #: ../manage/roles/admin-permissions.rst:81 msgid ":doc:`Channels > Web `" msgstr "" -#: ../manage/roles/admin-permissions.rst:80 +#: ../manage/roles/admin-permissions.rst:83 +msgid "``admin.channel_whatsapp``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:84 +msgid ":doc:`Channels > Whatsapp `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:86 msgid "``admin.core_workflows``" msgstr "" -#: ../manage/roles/admin-permissions.rst:81 #: ../manage/roles/admin-permissions.rst:87 msgid ":doc:`System > Core Workflows `" msgstr "" -#: ../manage/roles/admin-permissions.rst:83 #: ../manage/roles/admin-permissions.rst:89 msgid "``admin.data_privacy``" msgstr "" -#: ../manage/roles/admin-permissions.rst:84 #: ../manage/roles/admin-permissions.rst:90 msgid ":doc:`System > Data Privacy `" msgstr "" -#: ../manage/roles/admin-permissions.rst:85 #: ../manage/roles/admin-permissions.rst:91 msgid "" "🔥 Be careful, it allows users to permanently delete data on the system." msgstr "" -#: ../manage/roles/admin-permissions.rst:86 #: ../manage/roles/admin-permissions.rst:92 msgid "``admin.group``" msgstr "" -#: ../manage/roles/admin-permissions.rst:87 #: ../manage/roles/admin-permissions.rst:93 msgid ":doc:`Manage > Groups `" msgstr "" -#: ../manage/roles/admin-permissions.rst:89 #: ../manage/roles/admin-permissions.rst:95 msgid "``admin.integration``" msgstr "" -#: ../manage/roles/admin-permissions.rst:90 #: ../manage/roles/admin-permissions.rst:96 msgid ":doc:`System > Integrations `" msgstr "" -#: ../manage/roles/admin-permissions.rst:92 #: ../manage/roles/admin-permissions.rst:98 msgid "``admin.knowledge_base``" msgstr "" -#: ../manage/roles/admin-permissions.rst:93 #: ../manage/roles/admin-permissions.rst:99 msgid ":doc:`Manage > Knowledge Base `" msgstr "" @@ -8740,57 +8723,46 @@ msgid "" "knowledge-base.html#editing-answers>`." msgstr "" -#: ../manage/roles/admin-permissions.rst:98 #: ../manage/roles/admin-permissions.rst:104 msgid "``admin.macro``" msgstr "" -#: ../manage/roles/admin-permissions.rst:99 #: ../manage/roles/admin-permissions.rst:105 msgid ":doc:`Manage > Macros `" msgstr "" -#: ../manage/roles/admin-permissions.rst:100 #: ../manage/roles/admin-permissions.rst:106 msgid "In some cases, macros may also require ``admin.tag``" msgstr "" -#: ../manage/roles/admin-permissions.rst:101 #: ../manage/roles/admin-permissions.rst:107 msgid "``admin.maintenance``" msgstr "" -#: ../manage/roles/admin-permissions.rst:102 #: ../manage/roles/admin-permissions.rst:108 msgid ":doc:`System > Maintenance `" msgstr "" -#: ../manage/roles/admin-permissions.rst:104 #: ../manage/roles/admin-permissions.rst:110 msgid "``admin.monitoring``" msgstr "" -#: ../manage/roles/admin-permissions.rst:105 #: ../manage/roles/admin-permissions.rst:111 msgid ":doc:`System > Monitoring `" msgstr "" -#: ../manage/roles/admin-permissions.rst:107 #: ../manage/roles/admin-permissions.rst:113 msgid "``admin.object``" msgstr "" -#: ../manage/roles/admin-permissions.rst:108 #: ../manage/roles/admin-permissions.rst:114 msgid ":doc:`System > Objects `" msgstr "" -#: ../manage/roles/admin-permissions.rst:110 #: ../manage/roles/admin-permissions.rst:116 msgid "``admin.organization``" msgstr "" -#: ../manage/roles/admin-permissions.rst:111 #: ../manage/roles/admin-permissions.rst:117 msgid ":doc:`Manage > Organizations `" msgstr "" @@ -8807,202 +8779,212 @@ msgstr "" msgid "They can even edit an organization's name, domain, and notes!" msgstr "" -#: ../manage/roles/admin-permissions.rst:115 #: ../manage/roles/admin-permissions.rst:121 msgid "``admin.overview``" msgstr "" -#: ../manage/roles/admin-permissions.rst:116 #: ../manage/roles/admin-permissions.rst:122 msgid ":doc:`Manage > Overviews`" msgstr "" -#: ../manage/roles/admin-permissions.rst:118 +#: ../manage/roles/admin-permissions.rst:124 +msgid "``admin.public_links``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:125 +msgid ":doc:`Manage > Public Links `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:127 msgid "``admin.package``" msgstr "" -#: ../manage/roles/admin-permissions.rst:119 #: ../manage/roles/admin-permissions.rst:128 msgid ":doc:`System > Packages `" msgstr "" -#: ../manage/roles/admin-permissions.rst:121 #: ../manage/roles/admin-permissions.rst:130 msgid "``admin.report_profile``" msgstr "" -#: ../manage/roles/admin-permissions.rst:122 #: ../manage/roles/admin-permissions.rst:131 msgid ":doc:`Manage > Report Profiles `" msgstr "" -#: ../manage/roles/admin-permissions.rst:123 #: ../manage/roles/admin-permissions.rst:132 msgid "Access to view reports: ``report``" msgstr "" -#: ../manage/roles/admin-permissions.rst:124 #: ../manage/roles/admin-permissions.rst:133 msgid "``admin.role``" msgstr "" -#: ../manage/roles/admin-permissions.rst:125 #: ../manage/roles/admin-permissions.rst:134 msgid ":doc:`Manage > Roles `" msgstr "" -#: ../manage/roles/admin-permissions.rst:127 #: ../manage/roles/admin-permissions.rst:136 msgid "``admin.scheduler``" msgstr "" -#: ../manage/roles/admin-permissions.rst:128 #: ../manage/roles/admin-permissions.rst:137 msgid ":doc:`Manage > Scheduler `" msgstr "" -#: ../manage/roles/admin-permissions.rst:129 #: ../manage/roles/admin-permissions.rst:138 msgid "For automation on tickets" msgstr "" -#: ../manage/roles/admin-permissions.rst:130 #: ../manage/roles/admin-permissions.rst:139 msgid "``admin.security``" msgstr "" -#: ../manage/roles/admin-permissions.rst:131 #: ../manage/roles/admin-permissions.rst:140 msgid ":doc:`Settings > Security `" msgstr "" -#: ../manage/roles/admin-permissions.rst:132 #: ../manage/roles/admin-permissions.rst:141 msgid "Settings of Zammad. This also covers third party authentications." msgstr "" -#: ../manage/roles/admin-permissions.rst:133 #: ../manage/roles/admin-permissions.rst:142 msgid "``admin.session``" msgstr "" -#: ../manage/roles/admin-permissions.rst:134 #: ../manage/roles/admin-permissions.rst:143 msgid ":doc:`System > Sessions `" msgstr "" -#: ../manage/roles/admin-permissions.rst:136 #: ../manage/roles/admin-permissions.rst:145 msgid "``admin.setting_system``" msgstr "" -#: ../manage/roles/admin-permissions.rst:137 #: ../manage/roles/admin-permissions.rst:146 msgid ":doc:`Settings > System `" msgstr "" -#: ../manage/roles/admin-permissions.rst:139 #: ../manage/roles/admin-permissions.rst:148 msgid "``admin.sla``" msgstr "" -#: ../manage/roles/admin-permissions.rst:140 #: ../manage/roles/admin-permissions.rst:149 msgid ":doc:`Manage > SLAs `" msgstr "" -#: ../manage/roles/admin-permissions.rst:142 +#: ../manage/roles/admin-permissions.rst:151 +msgid "``admin.system_report``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:152 +msgid ":doc:`System > System Report `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:154 msgid "``admin.tag``" msgstr "" -#: ../manage/roles/admin-permissions.rst:143 #: ../manage/roles/admin-permissions.rst:155 msgid ":doc:`Manage > Tags `" msgstr "" -#: ../manage/roles/admin-permissions.rst:145 #: ../manage/roles/admin-permissions.rst:157 msgid "``admin.template``" msgstr "" -#: ../manage/roles/admin-permissions.rst:146 #: ../manage/roles/admin-permissions.rst:158 msgid ":doc:`Manage > Templates `" msgstr "" -#: ../manage/roles/admin-permissions.rst:148 #: ../manage/roles/admin-permissions.rst:160 msgid "``admin.text_module``" msgstr "" -#: ../manage/roles/admin-permissions.rst:149 #: ../manage/roles/admin-permissions.rst:161 msgid ":doc:`Manage > Text Modules `" msgstr "" -#: ../manage/roles/admin-permissions.rst:151 #: ../manage/roles/admin-permissions.rst:163 msgid "``admin.ticket``" msgstr "" -#: ../manage/roles/admin-permissions.rst:152 #: ../manage/roles/admin-permissions.rst:164 msgid ":doc:`Settings > Tickets `" msgstr "" -#: ../manage/roles/admin-permissions.rst:153 #: ../manage/roles/admin-permissions.rst:165 msgid "Does not grant access to :doc:`/misc/composer`" msgstr "" -#: ../manage/roles/admin-permissions.rst:154 +#: ../manage/roles/admin-permissions.rst:166 +msgid "``admin.ticket_auto_assignment``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:167 +msgid ":ref:`Settings > Ticket > Auto Assignment `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:169 +msgid "``admin.ticket_duplicate_detection``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:170 +msgid ":ref:`Settings > Ticket > Duplicate Detection `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:172 +#, fuzzy +msgid "``admin.ticket_priority``" +msgstr "priorité" + +#: ../manage/roles/admin-permissions.rst:173 +msgid ":ref:`System > Objects >Ticket Priority `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:175 +#, fuzzy +msgid "``admin.ticket_state``" +msgstr "exemple" + +#: ../manage/roles/admin-permissions.rst:176 +msgid ":ref:`System > Objects >Ticket State `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:178 msgid "``admin.time_accounting``" msgstr "" -#: ../manage/roles/admin-permissions.rst:155 #: ../manage/roles/admin-permissions.rst:179 msgid ":doc:`Manage > Time Accounting `" msgstr "" -#: ../manage/roles/admin-permissions.rst:156 #: ../manage/roles/admin-permissions.rst:180 msgid "Also allows the export of timekeeping records." msgstr "" -#: ../manage/roles/admin-permissions.rst:157 #: ../manage/roles/admin-permissions.rst:181 msgid "``admin.translation``" msgstr "" -#: ../manage/roles/admin-permissions.rst:158 #: ../manage/roles/admin-permissions.rst:182 msgid ":doc:`System > Translations `" msgstr "" -#: ../manage/roles/admin-permissions.rst:159 #: ../manage/roles/admin-permissions.rst:183 msgid "Also enables inline translation" msgstr "" -#: ../manage/roles/admin-permissions.rst:160 #: ../manage/roles/admin-permissions.rst:184 msgid "``admin.trigger``" msgstr "" -#: ../manage/roles/admin-permissions.rst:161 #: ../manage/roles/admin-permissions.rst:185 msgid ":doc:`Manage > Triggers `" msgstr "" -#: ../manage/roles/admin-permissions.rst:163 #: ../manage/roles/admin-permissions.rst:187 msgid "``admin.user``" msgstr "" -#: ../manage/roles/admin-permissions.rst:164 #: ../manage/roles/admin-permissions.rst:188 msgid ":doc:`Manage > Users `" msgstr "" @@ -9021,6 +9003,14 @@ msgid "" "from-users-perspective>` ." msgstr "" +#: ../manage/roles/admin-permissions.rst:193 +msgid "``admin.webhook``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:194 +msgid ":doc:`Manage > Webhook `" +msgstr "" + #: ../manage/roles/agent-permissions.rst:2 msgid "Agent Permissions" msgstr "" @@ -9441,37 +9431,47 @@ msgid "than the user that generated them." msgstr "" #: ../manage/roles/user-preferences-permissions.rst:43 +msgid "``user_preferences.appearance``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:44 +#, fuzzy +msgid "Appearance configuration" +msgstr "Boîte de dialogue de configuration avancée" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "Users can switch between dark, light and" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "automatic mode." +msgstr "" + #: ../manage/roles/user-preferences-permissions.rst:47 msgid "``user_preferences.avatar``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:44 #: ../manage/roles/user-preferences-permissions.rst:48 #, fuzzy msgid "Avatar settings" msgstr "Paramètres" -#: ../manage/roles/user-preferences-permissions.rst:45 #: ../manage/roles/user-preferences-permissions.rst:49 msgid "Override the default Gravatar with a custom avatar" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:46 #: ../manage/roles/user-preferences-permissions.rst:50 msgid "``user_preferences.calendar``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:47 #: ../manage/roles/user-preferences-permissions.rst:51 msgid "Configure the calendar feed" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:49 #: ../manage/roles/user-preferences-permissions.rst:53 msgid "``user_preferences.device``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:50 #: ../manage/roles/user-preferences-permissions.rst:54 msgid "Manage device login sessions" msgstr "" @@ -9488,22 +9488,18 @@ msgstr "" msgid "To learn more, see :doc:`/manage/trigger/system-notifications`." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:54 #: ../manage/roles/user-preferences-permissions.rst:58 msgid "``user_preferences.language``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:55 #: ../manage/roles/user-preferences-permissions.rst:59 msgid "Configure the UI locale/language" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:57 #: ../manage/roles/user-preferences-permissions.rst:61 msgid "``user_preferences.linked_accounts``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:58 #: ../manage/roles/user-preferences-permissions.rst:62 #, fuzzy msgid "Account linking" @@ -9528,7 +9524,6 @@ msgstr "" msgid "is the only way users can utilize third-party logins." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:63 #: ../manage/roles/user-preferences-permissions.rst:67 msgid "``user_preferences.notifications``" msgstr "" @@ -9557,7 +9552,6 @@ msgstr "" msgid "Customers can't receive ticket notifications at all." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:69 #: ../manage/roles/user-preferences-permissions.rst:73 msgid "``user_preferences.out_of_office``" msgstr "" @@ -9582,7 +9576,6 @@ msgstr "" msgid "they're replacing." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:75 #: ../manage/roles/user-preferences-permissions.rst:79 msgid "``user_preferences.overview_sorting``" msgstr "" @@ -9611,12 +9604,10 @@ msgstr "" msgid "overviews has no effect on custom orders." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:82 #: ../manage/roles/user-preferences-permissions.rst:86 msgid "``user_preferences.password``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:83 #: ../manage/roles/user-preferences-permissions.rst:87 msgid "Change account password" msgstr "" @@ -9633,7 +9624,6 @@ msgstr "" msgid "your only allowed authentication method." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:87 #: ../manage/roles/user-preferences-permissions.rst:91 msgid "``user_preferences.two_factor_authentication``" msgstr "" @@ -9670,7 +9660,7 @@ msgstr "" #: ../manage/scheduler.rst:19 msgid "" -"Schedulers can be used to send periodic reminder emails. Use :doc:`/system/" +"Schedulers can be used to send periodic reminder emails. Use :doc:`/misc/" "variables` to build highly-customized email templates." msgstr "" @@ -10672,7 +10662,7 @@ msgstr "" #: ../manage/text-modules.rst:57 msgid "" -"The example text modules below use :doc:`/system/variables` to dynamically " +"The example text modules below use :doc:`/misc/variables` to dynamically " "insert information like the customer's or agent's names." msgstr "" @@ -11014,8 +11004,8 @@ msgstr "" #: ../misc/object-conditions/basics.rst:144 #: ../misc/object-conditions/basics.rst:160 #: ../misc/object-conditions/basics.rst:168 -#: ../misc/object-conditions/basics.rst:178 ../settings/ticket.rst:2 -#: ../system/variables/ticket.rst:2 +#: ../misc/object-conditions/basics.rst:178 ../misc/variables/ticket.rst:2 +#: ../settings/ticket.rst:2 msgid "Ticket" msgstr "" @@ -11249,7 +11239,7 @@ msgstr "" #: ../manage/trigger/how-do-they-work.rst:79 msgid "" -"Certain actions (such as *email*, *SMS* and *notes*) support :doc:`/system/" +"Certain actions (such as *email*, *SMS* and *notes*) support :doc:`/misc/" "variables`, which can be used to build highly-customized message templates." msgstr "" @@ -11278,7 +11268,7 @@ msgstr "" msgid "" "You can also combine static text with placeholders for text fields. Remember " "that the placeholders' values have to be known during trigger runtime. Learn " -"more about :doc:`/system/variables`." +"more about :doc:`/misc/variables`." msgstr "" #: ../manage/trigger/how-do-they-work.rst:105 @@ -12246,7 +12236,7 @@ msgstr "" msgid "" "When switched on, a code editor will be shown below, where you can configure " "custom payload for your webhook in JSON format. To insert supported :doc:`/" -"system/variables` use ``::`` or ``#{`` shortcuts for autocomplete." +"misc/variables` use ``::`` or ``#{`` shortcuts for autocomplete." msgstr "" #: ../manage/webhook/add.rst:103 @@ -14857,12035 +14847,11942 @@ msgid "" "powerful conditions with AND/OR relations." msgstr "" -#: ../settings/branding.rst:10 -msgid "Product Name" -msgstr "" +#: ../misc/variables.rst:2 +msgid "Variables" +msgstr "Variables" -#: ../settings/branding.rst:7 +#: ../misc/variables.rst:4 msgid "" -"Defines the name of the application, shown in the web interface, tabs and " -"title bar of the web browser." +"Please note that this is just an overview of available variables. It might " +"be incomplete or variables might not be available within some functions. If " +"you're missing variables or are not sure if something is not working as " +"expected, feel free to ask over at the `Community `_." msgstr "" -#: ../settings/branding.rst:10 -msgid "Default value: ``Zammad Helpdesk``" +#: ../misc/variables.rst:10 +msgid "" +"Variables can be called by typing ``::`` (just like text modules in the " +"frontend), as long as you're in a supported text field within the backend. " +"Zammad will display all variables being available within this context and " +"replace it to the variable as soon as you selected an entry." msgstr "" -#: ../settings/branding.rst:13 -msgid "Will be shown in the app and is included in email footers." +#: ../misc/variables.rst:15 +msgid "" +"You have an empty field which you referenced and it appears as ``-``? That's " +"currently working as designed - you might want to ensure that these fields " +"always have a value." msgstr "" -#: ../settings/branding.rst:19 -msgid "Logo" +#: ../misc/variables.rst:20 +msgid "Variable Categories" msgstr "" -#: ../settings/branding.rst:16 -msgid "Defines the logo of the application, shown in the login page of Zammad." +#: ../misc/variables.rst:31 +msgid "Wait, What About Custom Objects?" msgstr "" -#: ../settings/branding.rst:18 +#: ../misc/variables.rst:33 msgid "" -"Ensure to hit the \"Submit\" button after uploading the logo. Otherwise your " -"change will not be saved." +"Good point! Of course, we can't predict what objects you might create, but " +"we can give you a hint on how to put the puzzle together to get your custom " +"values." msgstr "" -#: ../settings/branding.rst:22 +#: ../misc/variables.rst:36 msgid "" -"Allows to set the default language of the Zammad instance. The here defined " -"locale mostly acts as a fallback for:" +"For this, we'll talk about the inner part of the variable (so everything " +"within ``#{}``), please put the outer part around to have a valid variable. " +"The first part of the variable name consist of the object type. Currently " +"these are:" msgstr "" -#: ../settings/branding.rst:25 -msgid "user preferences (if Zammad can't detect the users locale)" +#: ../misc/variables.rst:41 +msgid "Ticket (``ticket``)" msgstr "" -#: ../settings/branding.rst:26 -msgid "CSV output (reporting, time accounting)" +#: ../misc/variables.rst:42 +msgid "User (``user``)" msgstr "" -#: ../settings/branding.rst:30 -msgid "Define the timezone of your Zammad installation." +#: ../misc/variables.rst:43 +msgid "Organization (``organization``)" msgstr "" -#: ../settings/branding.rst:32 -msgid "" -"This does not have any effect on timings for your agents or how Zammad " -"stores date and time values." +#: ../misc/variables.rst:44 +msgid "Group (``group``)" msgstr "" -#: ../settings/branding.rst:35 -msgid "Changing this value has direct consequences on the following areas:" +#: ../misc/variables.rst:46 +msgid "" +"The second part is the name of the attribute. This is the name you define " +"during object creation and can be found within the object attribute menu at " +"any time. The first and second part of a variable is divided by a point, e." +"g.: ``ticket.number`` which will in total be ``#{ticket.number}``." msgstr "" -#: ../settings/branding.rst:37 -msgid ":doc:`/manage/scheduler` tasks" +#: ../misc/variables.rst:51 +msgid "" +"Now, in some situations it's possible that you'll need to use a third part. " +"The best example for such a situation would be a ``select`` or ``tree-" +"select`` field which will by default return the key value, not it's display " +"name. For this, just extend your variable with ``.value``. This will result " +"in ``#{ticket.select.value}``." msgstr "" -#: ../settings/branding.rst:38 -msgid "search indexing (and thus reporting)" -msgstr "" +#: ../misc/variables.rst:60 +#, fuzzy +msgid "Using Translated Variables" +msgstr "Traductions" -#: ../settings/branding.rst:40 -msgid "calendar subscriptions" +#: ../misc/variables.rst:62 +msgid "" +"If you want to use a translated variable in triggers or schedulers, you can " +"extend the placeholder like this: ``#{t(ticket.state.name)}``. The ``t`` " +"tells Zammad to search for fitting translated strings. The used output " +"language is based on the system language of Zammad which you can set in the " +"admin panel under :doc:`/settings/branding` or based on the selected locale " +"in the trigger/scheduler edit dialog." msgstr "" -#: ../settings/branding.rst:41 -msgid "browser printing" +#: ../misc/variables.rst:69 +msgid "" +"A possible use-case: you want to send your customers updates on tickets via " +"trigger or scheduler which should include the state of the ticket. Using the " +"default ``#{ticket.state.name}`` (without the translation flag ``t()``) " +"would lead to the output of the original (english) name of the state." msgstr "" -#: ../settings/branding.rst:43 -msgid "" -"Please note that some of above are fallbacks in case Zammad could not detect " -"the agents timezone correctly." +#: ../misc/variables.rst:75 +msgid "Date and Time Formatting" msgstr "" -#: ../settings/branding.rst:77 -msgid "Pretty Date" +#: ../misc/variables.rst:77 +msgid "" +"The system (trigger/scheduler selected) locale and timezone predefines a " +"default format of date and timestamp. This format is customizable by using " +"the ``dt()`` method." msgstr "" -#: ../settings/branding.rst:47 -msgid "" -"This setting allows you to define how Zammad should display time stamps " -"within the interface to all users." +#: ../misc/variables.rst:79 +msgid "The method arguments are as follows:" msgstr "" -#: ../settings/branding.rst:50 -msgid "" -"This does not have any effect on how Zammad returns e.g. time values via " -"variables." +#: ../misc/variables.rst:81 +msgid "The date or timestamp variable you want to format." msgstr "" -#: ../settings/branding.rst:77 -msgid "Choose in between the following options:" +#: ../misc/variables.rst:82 +msgid "The output format string." msgstr "" -#: ../settings/branding.rst:64 -msgid "relative" +#: ../misc/variables.rst:83 +msgid "The timezone to apply (optional)." msgstr "" -#: ../settings/branding.rst:55 +#: ../misc/variables.rst:85 +#: ../system/objects/external-data-source-example.rst:23 +#, fuzzy +msgid "**Example:**" +msgstr "exemple" + +#: ../misc/variables.rst:86 msgid "" -"This timestamp shows a relative time span until it switches to a date. Over " -"time, it will change as follows:" +"``#{dt(ticket.updated_at, \"%A %Y-%m-%d %H:%M in the office\", \"Europe/" +"Berlin\")}``" msgstr "" -#: ../settings/branding.rst:58 -msgid "just now" +#: ../misc/variables.rst:87 +msgid "Monday, 2024-03-18 15:31 in the office" msgstr "" -#: ../settings/branding.rst:59 -msgid "5 minutes ago" +#: ../misc/variables.rst:89 +msgid "" +"If you want to use our example, make sure to paste the string above without " +"formatting (``CTRL+Shift+v``), otherwise it won't work." msgstr "" -#: ../settings/branding.rst:60 -msgid "3 days 1 hour ago" +#: ../misc/variables.rst:93 +msgid "The following table lists available format directives:" msgstr "" -#: ../settings/branding.rst:61 -msgid "``03/04/2022``" +#: ../misc/variables.rst:99 +msgid "Parameter" msgstr "" -#: ../settings/branding.rst:63 -msgid "Hovering the timestamp helps, you'll always get a clean timestamp then." +#: ../misc/variables.rst:102 +msgid "``%Y``" msgstr "" -#: ../settings/branding.rst:71 -msgid "absolute" +#: ../misc/variables.rst:103 +msgid "Year with 4 digits" msgstr "" -#: ../settings/branding.rst:67 -msgid "" -"This timestamp always includes the week day. For one week after creation, " -"the timestamp will not contain the date itself: Thursday 18:35." +#: ../misc/variables.rst:104 +msgid "Use ``%y`` for year with 2 digits" msgstr "" -#: ../settings/branding.rst:71 -msgid "After a week it will switch to: ``Friday 4. Mar 16:00``." +#: ../misc/variables.rst:105 +msgid "``%m``" msgstr "" -#: ../settings/branding.rst:76 -msgid "timestamp" +#: ../misc/variables.rst:106 +msgid "Month of year (as number with zero-padding)" msgstr "" -#: ../settings/branding.rst:74 -msgid "" -"This will cause Zammad to show a complete timestamp according to your locale " -"defaults. For English this could be e.g. ``2022/12/03 2:40 pm`` or for " -"German e.g. ``12.03.2022 14:40``." +#: ../misc/variables.rst:107 +msgid "Use ``%-m`` for month without zero-padding" msgstr "" -#: ../settings/branding.rst:78 -msgid "Default setting: ``relative``." +#: ../misc/variables.rst:108 +msgid "``%d``" msgstr "" -#: ../settings/security.rst:2 -msgid "Security" +#: ../misc/variables.rst:109 +msgid "Day of month (as number with zero-padding)" msgstr "" -#: ../settings/security.rst:4 -msgid "" -"For your overview we split each tab within security settings into its own " -"page:" +#: ../misc/variables.rst:110 +msgid "Use ``%e`` for day without zero-padding" msgstr "" -#: ../settings/security/base.rst:2 ../settings/system/base.rst:2 -#: ../settings/ticket.rst:8 -msgid "Base" +#: ../misc/variables.rst:111 +msgid "``%H``" msgstr "" -#: ../settings/security/base.rst:5 -msgid "New User Accounts" +#: ../misc/variables.rst:112 +msgid "Hour of day in 24h notation with zero-padding" msgstr "" -#: ../settings/security/base.rst:9 -msgid "" -"Activates the `register as a new customer` function on the login page. If " -"set to ``no`` only administrators or agents can create new accounts manually." +#: ../misc/variables.rst:113 +msgid "Use ``%k`` for hour without zero-padding" msgstr "" -#: ../settings/security/base.rst:13 ../settings/security/base.rst:38 -#: ../settings/security/base.rst:66 -msgid "Default setting: ``yes``" +#: ../misc/variables.rst:114 +msgid "``%I``" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing activated \"New User Accounts\" setting" +#: ../misc/variables.rst:115 +msgid "Hour of day in 12h notation with zero-padding" msgstr "" -#: ../settings/security/base.rst:22 +#: ../misc/variables.rst:116 msgid "" -"Deactivation of above function **does not** deactivate automatic account " -"creation! This means: If a user writes e.g. an email to Zammad and has no " -"account yet, Zammad will automatically create the account. User accounts are " -"a direct dependency of tickets and thus technically mandatory." +"Use ``%l`` for hour without zero-padding and ``%p`` / ``%P`` for meridian " +"indicator" msgstr "" -#: ../settings/security/base.rst:29 -msgid "Lost Password" +#: ../misc/variables.rst:117 +msgid "``%M``" msgstr "" -#: ../settings/security/base.rst:33 -msgid "" -"Activates the `lost password` function on the login page. If set to ``no`` " -"only administrators may change the user's password - users may update their " -"own password if they're still logged in and they have the required :doc:" -"`permission `." +#: ../misc/variables.rst:118 +msgid "Minute of hour" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing activated \"Lost Password\" setting" +#: ../misc/variables.rst:120 +msgid "``%S``" msgstr "" -#: ../settings/security/base.rst:49 -msgid "" -"With third party authentications - but especially LDAP - you may want to " -"disable this function. Zammad **will not** change third party login " -"passwords and instead set or change the local password!" +#: ../misc/variables.rst:121 +msgid "Second of Minute" msgstr "" -#: ../settings/security/base.rst:56 -msgid "Password Login" +#: ../misc/variables.rst:123 +msgid "``%A``" msgstr "" -#: ../settings/security/base.rst:60 -msgid "" -"Activates the username & password login by default and if no third-party " -"login is activated. Disabling password login on the Zammad login page only " -"takes effect if you enable any :doc:`third-party`." +#: ../misc/variables.rst:124 +msgid "Weekday name" msgstr "" -#: ../settings/security/base.rst:64 -msgid "See :doc:`third-party` for supported third-party logins." +#: ../misc/variables.rst:125 +msgid "Use ``%a`` for abbreviated name or ``%^A`` for uppercase name" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing de-activated \"Password Login\" setting" +#: ../misc/variables.rst:126 +msgid "``%B``" msgstr "" -#: ../settings/security/base.rst:77 -msgid "" -"To help administrators to overcome \"login issues\", Zammad automatically " -"offers a password request for administrator users. This allows you to adjust " -"Third-Party applications even if the login does no longer work!" +#: ../misc/variables.rst:127 +msgid "Month name" msgstr "" -#: ../settings/security/base.rst:84 -msgid "Session Timeout" +#: ../misc/variables.rst:128 +msgid "Use ``%b`` for abbreviated name" msgstr "" -#: ../settings/security/base.rst:86 -msgid "" -"All settings below by default are set to ``4 weeks``. Session Timeout " -"defines the life time of a users session. As soon as it's reached, Zammad " -"will automatically log off the session in question." +#: ../misc/variables.rst:129 +msgid "``%U``" msgstr "" -#: ../settings/security/base.rst:91 -msgid "" -"Zammad takes the highest value set assigned for the user based on the " -"permissions." +#: ../misc/variables.rst:130 +msgid "Week number of current year" msgstr "" -#: ../settings/security/base.rst:94 -msgid "``admin``" +#: ../misc/variables.rst:131 +msgid "Use ``%W`` for a different calculation method" msgstr "" -#: ../settings/security/base.rst:96 -msgid "``ticket.customer``" +#: ../misc/variables.rst:134 +msgid "" +"We support the known format directives for the Ruby built-in method " +"``strftime`` of the ``DateTime`` class. For more information, see `here " +"`_." msgstr "" -#: ../settings/security/base.rst:97 -msgid "``default`` (fallback if user doesn't have above permissions set)" +#: ../misc/variables/article.rst:2 +msgid "Articles" +msgstr "Articles" + +#: ../misc/variables/article.rst:4 ../misc/variables/config.rst:4 +#: ../misc/variables/current-user.rst:4 ../misc/variables/ticket.rst:4 +msgid "" +"If you're missing variables or are not sure if something is not working as " +"expected, feel free to ask over at the `Community `_." msgstr "" +"Si il vous manque des variables ou si vous pensez que quelque chose ne " +"fonctionne pas comme prévu, n'hésitez pas à demander à la `Communauté " +"`_." -#: ../settings/security/base.rst:99 +#: ../misc/variables/article.rst:6 +#, fuzzy +#| msgid "" +#| "Below you can find all available ticket article-based variables within " +#| "Zammad. These can be called via Triggers for example. If you're unsure if " +#| "Zammad does support variables at the point you're at, you can try to type " +#| "``::`` to check." msgid "" -"All settings act independently from each other allowing you to disable the " -"timeouts for e.g. admins, but not agents." +"Below you can find all available ticket article-based variables within " +"Zammad. These can be called via triggers for example. If you're unsure if " +"Zammad does support variables at the point you're at, you can try to type " +"``::`` to check." msgstr "" +"Ci dessous, vous pourrez trouver l'ensemble des variables des articles de " +"ticket disponibles dans Zammad. Elles peuvent être utilisées via les " +"Déclencheurs par exemple. Pour vous assurer que Zammad supporte les " +"variables à l'endroit où vous vous trouvez, vous pouvez taper ``::`` pour " +"vérifier." -#: ../settings/security/base.rst:115 -#: ../system/integrations/checkmk/api-reference.rst:13 -msgid "Example" +#: ../misc/variables/article.rst:9 ../misc/variables/config.rst:9 +#: ../misc/variables/ticket.rst:9 +msgid "" +"The below list gives you an example what kind of data you can expect, it's " +"not intended to explain the data itself." msgstr "" +"La liste ci-dessous vous donne un exemple du type de données auxquelles vous " +"pouvez vous attendre, elle n'est pas destiné à expliquer les données elles-" +"mêmes." -#: ../settings/security/base.rst:107 -msgid "Let's suppose you configured the following session timeouts" +#: ../misc/variables/article.rst:11 +msgid "Article Variables" +msgstr "Variables Article" + +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "name" +msgstr "nom" + +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "variable" +msgstr "variable" + +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "example" +msgstr "exemple" + +#: ../misc/variables/article.rst:1 +msgid "Article > Cc" msgstr "" -#: ../settings/security/base.rst:104 -msgid "default: 3 weeks" +#: ../misc/variables/article.rst:1 +msgid "``#{article.cc}``" msgstr "" -#: ../settings/security/base.rst:105 -msgid "admin: 2 weeks" +#: ../misc/variables/article.rst:1 +msgid "``jdoe@example.com, company@example.com``" msgstr "" -#: ../settings/security/base.rst:106 -msgid "ticket.agent: 4 weeks" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Address" msgstr "" -#: ../settings/security/base.rst:107 -msgid "ticket.customer: 1 week" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.address}``" msgstr "" -#: ../settings/security/base.rst:115 -msgid "This results in the following situations" +#: ../misc/variables/article.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set in user object" msgstr "" -#: ../settings/security/base.rst:110 -msgid "a user with ``admin`` permission will have a timeout of 2 weeks" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Department" msgstr "" -#: ../settings/security/base.rst:111 -msgid "" -"a user with ``admin`` and ``ticket.agent`` permissions will have a timeout " -"of 2 weeks" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.department}``" msgstr "" -#: ../settings/security/base.rst:113 -msgid "" -"a user with ``ticket.customer`` permission will have a timeout of 1 week" +#: ../misc/variables/article.rst:1 +msgid "``Sales`` or empty if not set in user object" msgstr "" -#: ../settings/security/base.rst:115 -msgid "" -"a user with neither ``admin``, ``ticket.agent`` nor ``ticket.customer`` " -"permissions will have a timeout of 3 weeks" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Email" msgstr "" -#: ../settings/security/password.rst:4 -msgid "" -"This section allows you to define password requirements for the local user " -"accounts." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.email}``" msgstr "" -#: ../settings/security/password.rst:9 -msgid "" -"Zammad does **not** allow you to change your LDAP password, instead, it will " -"set a password in its local database which might confuse your users. This " -"might be addressed in the future by `#1169 `_." +#: ../misc/variables/article.rst:1 +msgid "``jdoe@example.com``" msgstr "" -#: ../settings/security/password.rst:14 -msgid "**Exception for admins**" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Fax" msgstr "" -#: ../settings/security/password.rst:16 -msgid "" -"Please note that below password policies *do not* affect administrators " -"setting passwords on user accounts. While this seems strange and not safe we " -"believe that an administrator knowing an user's password is insecure as well." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.fax}``" msgstr "" -#: ../settings/security/password.rst:21 -msgid "The suggested workflow is either:" +#: ../misc/variables/article.rst:1 +msgid "``+4930123456789`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:23 -msgid "" -"to use third party logins to not require local passwords at all **- or -**" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Firstname" msgstr "" -#: ../settings/security/password.rst:25 -msgid "to require your *user to reset the password* upon first login." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.firstname}``" msgstr "" -#: ../settings/security/password.rst:27 -msgid "" -"This way administrators are not required to set a user's password at all!" +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Joe`` or empty if not set" msgstr "" -#: ../settings/security/password.rst:31 -msgid "Maximum Failed Logins" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Lastname" msgstr "" -#: ../settings/security/password.rst:33 -msgid "" -"You can choose a value between ``4`` and ``20``. This defines how often a " -"login to a user account may fail until Zammad will lock it. Your users can " -"always use the \"forgot password\" function to change their password and " -"unlock their account." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.lastname}``" msgstr "" -#: ../settings/security/password.rst:38 -msgid "The default value is ``10``." +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +#: ../misc/variables/ticket.rst:1 +msgid "``Doe`` or empty if not set" msgstr "" -#: ../settings/security/password.rst:42 -msgid "Beside changing the user's password, you can also unlock accounts via" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Login" msgstr "" -#: ../settings/security/password.rst:44 -msgid ":ref:`user management list `" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.login}``" msgstr "" -#: ../settings/security/password.rst:45 -msgid ":docs:`console `" +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +#: ../misc/variables/ticket.rst:1 +msgid "``jdoe``" msgstr "" -#: ../settings/security/password.rst:46 -msgid ":docs:`API `" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Mobile" msgstr "" -#: ../settings/security/password.rst:50 -msgid "Failed logins via LDAP no longer lock accounts." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.mobile}``" msgstr "" -#: ../settings/security/password.rst:53 -msgid "2 Lower Case And 2 Upper Case Characters" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Note" msgstr "" -#: ../settings/security/password.rst:55 -msgid "" -"You can add complexity to passwords by enforcing at least 2 upper and lower " -"case characters." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.note}``" msgstr "" -#: ../settings/security/password.rst:58 ../settings/security/password.rst:83 -msgid "The default value is ``no``." +#: ../misc/variables/article.rst:1 +msgid "``Some note about user`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:62 -msgid "Minimum Length" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Phone" msgstr "" -#: ../settings/security/password.rst:64 -msgid "" -"This defines the minimum password length required for users to provide (from " -"``4`` to ``20``)." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.phone}``" msgstr "" -#: ../settings/security/password.rst:67 -msgid "The default value is ``6``." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > VIP" msgstr "" -#: ../settings/security/password.rst:71 -msgid "Digit Required" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.vip}``" msgstr "" -#: ../settings/security/password.rst:73 -msgid "This enforces your users to use at least one digit within the password." +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +msgid "``true`` or ``false``" msgstr "" -#: ../settings/security/password.rst:75 -msgid "The default value is ``yes``." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Web" msgstr "" -#: ../settings/security/password.rst:78 -msgid "Special Character Required" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.web}``" msgstr "" -#: ../settings/security/password.rst:80 -msgid "" -"This setting allows you to improve your password quality even more by " -"enforcing the password to contain at least one special character." +#: ../misc/variables/article.rst:1 +msgid "``https://zammad.com`` or empty if not set in user object" msgstr "" -#: ../settings/security/ssl-certificates.rst:2 -msgid "SSL Certificates" +#: ../misc/variables/article.rst:1 +msgid "Article > Created" msgstr "" -#: ../settings/security/ssl-certificates.rst:7 -msgid "" -"Zammad offers the possibility to upload custom certificates and custom " -"Certificate Authority (CA) certificates. This can be useful if you want to " -"connect Zammad the secure way to other systems which are using custom " -"certificates." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_at}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:12 -msgid "" -"An example usecase might be: You have an internal LDAP server that is not " -"accessible from the internet, and you want a SSL-encrypted connection, using " -"a custom certificate." +#: ../misc/variables/article.rst:1 +msgid "``2019-10-08 15:24:47 UTC``" msgstr "" -#: ../settings/security/ssl-certificates.rst:19 -msgid "" -"You should have an existing custom certificate file and/or a custom CA " -"certificate file, which you want to add to Zammad. As filetype ``.crt`` is " -"supported and the certificate format has to be PEM (Base64 ASCII)." +#: ../misc/variables/article.rst:1 +msgid "Article > From" msgstr "" -#: ../settings/security/ssl-certificates.rst:25 +#: ../misc/variables/article.rst:1 +msgid "``#{article.from}``" +msgstr "" + +#: ../misc/variables/article.rst:1 msgid "" -"When you import a custom CA certificate, all certificates generated with " -"this are trusted. This can be useful if you have more than one system/" -"certificate you want to connect to and the certificates are issued from the " -"same custom CA." +"``Joe Doe `` may differ, depends on ``FROM`` of send mail" msgstr "" -#: ../settings/security/ssl-certificates.rst:31 -msgid "Add a Certificate" +#: ../misc/variables/article.rst:1 +msgid "Article > Sender > Name" msgstr "" -#: ../settings/security/ssl-certificates.rst:33 -msgid "" -"To add a custom certificate or a custom CA certificate, head over to the " -"Admin panel > Settings > Security > SSL Certificates. Here you can find a " -"\"Add SSL Certificate\" button. In the dialog you can either select a " -"certificate file or paste the content of the certificate:" +#: ../misc/variables/article.rst:1 +msgid "``#{article.sender.name}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate adding dialog" +#: ../misc/variables/article.rst:1 +msgid "``Customer``, ``Agent`` or ``System``" msgstr "" -#: ../settings/security/ssl-certificates.rst:43 -msgid "" -"After selecting a file or pasting the content of the certificate, click on " -"the \"Add\" button to finally upload it to Zammad. Then, the certificates " -"are immediately effective, no restart or similar required." +#: ../misc/variables/article.rst:1 +msgid "Article > Subject" msgstr "" -#: ../settings/security/ssl-certificates.rst:49 -msgid "" -"Please note that only single certificate files are supported. That means if " -"you want to import a certificate / CA certificate, it must contain **only " -"one** certificate." +#: ../misc/variables/article.rst:1 +msgid "``#{article.subject}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:54 -msgid "Certificate Overview" +#: ../misc/variables/article.rst:1 +msgid "``My amazing subject``" msgstr "" -#: ../settings/security/ssl-certificates.rst:56 -msgid "" -"After you added a certificate, you can see a table with information for each " -"added certificate:" +#: ../misc/variables/article.rst:1 +msgid "Article > Text" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing table of added certificates" +#: ../misc/variables/article.rst:1 +msgid "``#{article.body}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:64 -msgid "" -"Here you can download the certificate or delete it, if you don't need it " -"anymore." +#: ../misc/variables/article.rst:1 +msgid "``Test`` without formatting (plain)" msgstr "" -#: ../settings/security/ssl-certificates.rst:68 -#, fuzzy -msgid "Deleting Certificates" -msgstr "Intégrations" +#: ../misc/variables/article.rst:1 +msgid "Article > TicketID" +msgstr "" -#: ../settings/security/ssl-certificates.rst:70 -msgid "" -"If you want to delete a specific certificate, you can do it by clicking on " -"the menu in the actions column and selecting delete:" +#: ../misc/variables/article.rst:1 +msgid "``#{article.ticket_id}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate deletion button" +#: ../misc/variables/article.rst:1 +msgid "``1`` (not ticket number)" msgstr "" -#: ../settings/security/ssl-certificates.rst:79 -msgid "Downloading Certificates" +#: ../misc/variables/article.rst:1 +msgid "Article > To" msgstr "" -#: ../settings/security/ssl-certificates.rst:81 -msgid "" -"If you want to download your certificates, you can do this as well via " -"corresponding action buttons." +#: ../misc/variables/article.rst:1 +msgid "``#{article.to}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate download button" +#: ../misc/variables/article.rst:1 +msgid "``helpdesk@example.com``" msgstr "" -#: ../settings/security/third-party.rst:13 -msgid "Login Providers" +#: ../misc/variables/article.rst:1 +msgid "Article > Type > Name" msgstr "" -#: ../settings/security/third-party.rst:2 -msgid "Third-Party Applications" +#: ../misc/variables/article.rst:1 +msgid "``#{article.type.name}``" msgstr "" -#: ../settings/security/third-party.rst:4 +#: ../misc/variables/article.rst:1 msgid "" -"Third party authentication is a great way to help your users to login to " -"Zammad more easily. If the account is yet unknown, Zammad will create a new " -"user automatically, without the user needed to interact (e.g. type in his " -"name). Another big advantage of this feature is that your user doesn't need " -"to remember another password." +"``email`` (`list of article types `_)" msgstr "" -#: ../settings/security/third-party.rst:10 -msgid "" -"You can deactivate logging in via :ref:`security_password_login` if any of " -"the mentioned authentication providers are enabled in your instance." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Address" msgstr "" -#: ../settings/security/third-party.rst:27 -msgid "" -"We're currently missing documentation for the following login providers:" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.address}``" msgstr "" -#: ../settings/security/third-party.rst:29 -msgid "LinkedIn" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Department" msgstr "" -#: ../settings/security/third-party.rst:30 -msgid "Weibo" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.department}``" msgstr "" -#: ../settings/security/third-party.rst:35 -#, fuzzy -msgid "Automatic Account Link on Initial Logon" -msgstr "Notification de liaison automatique de compte" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Email" +msgstr "" -#: ../settings/security/third-party.rst:37 -msgid "" -"In general there's two possible options for Zammad on how to deal with " -"already known users as they try to authenticate against a third-party " -"application. By default, Zammad will not automatically link \"unknown\" " -"authentication providers to existing accounts." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.email}``" msgstr "" -#: ../settings/security/third-party.rst:42 -msgid "" -"This means that the user has to manually link authentication providers to " -"their accounts (for more about this :user-docs:`consult the user " -"documentation `)." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Fax" msgstr "" -#: ../settings/security/third-party.rst:46 -msgid "" -"Sometimes this doesn't come in handy as this also means you'll receive error " -"messages about \"email address being in use already\" for (yet) unknown " -"third-party authentication methods." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.fax}``" msgstr "" -#: ../settings/security/third-party.rst:50 -msgid "" -"If you want to allow your users to always be able to log in, no matter what, " -"you may want to enable ``Automatic account link on initial logon``." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Firstname" msgstr "" -#: ../settings/security/third-party.rst:None -msgid "" -"Screenshot highlighting the \"Automatic account link on initial logon\"\n" -"setting" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.firstname}``" msgstr "" -#: ../settings/security/third-party.rst:60 -#, fuzzy -msgid "Automatic Account Linking Notification" -msgstr "Notification de liaison automatique de compte" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Lastname" +msgstr "" -#: ../settings/security/third-party.rst:64 -msgid "" -"To improve security and your users awareness, you can enable Zammad to " -"notify your users when a new third-party application has been linked to " -"their account." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.lastname}``" msgstr "" -#: ../settings/security/third-party.rst:68 -msgid "" -"This notification is sent out once per third-party application. Zammad does " -"also mention the method used, e.g.: ``Microsoft``." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Login" msgstr "" -#: ../settings/security/third-party.rst:71 -msgid "By default this setting is not active (set to ``no``)." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.login}``" msgstr "" -#: ../settings/security/third-party.rst:0 -msgid "" -"Screenshot showing sample notification mail after initial\n" -"third-party linking" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Mobile" msgstr "" -#: ../settings/security/third-party.rst:85 -msgid "" -"This notification is only sent if the account in question already exists. If " -"the login via the third-party also creates the missing account, the " -"notification will be skipped." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.mobile}``" msgstr "" -#: ../settings/security/third-party.rst:89 -msgid "This means it only affects:" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Note" msgstr "" -#: ../settings/security/third-party.rst:91 -msgid "manual account linking within the third-party page of the users profile" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.note}``" msgstr "" -#: ../settings/security/third-party.rst:92 -msgid "" -"logging into an existing local account by utilizing the *automatic account " -"link on initial logon* functionality" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Phone" msgstr "" -#: ../settings/security/third-party.rst:None -msgid "" -"Screenshot showing the \"automatic account linking notification\"\n" -"setting" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.phone}``" msgstr "" -#: ../settings/security/third-party.rst:100 -msgid "No User Creation on Logon" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > VIP" msgstr "" -#: ../settings/security/third-party.rst:102 -msgid "" -"By default, Zammad will create a new user account if the user logs in via a " -"third-party application and the account doesn't exist yet." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.vip}``" msgstr "" -#: ../settings/security/third-party.rst:105 -msgid "" -"If you want to prevent Zammad from creating new accounts on logon, you can " -"disable this feature by setting ``No user creation on logon`` to ``yes``." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Web" msgstr "" -#: ../settings/security/third-party.rst:None -#, fuzzy -msgid "Screenshot showing the \"no user creation on logon\" setting" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.web}``" msgstr "" -"Capture d'écran montrant la configuration de base d'une boîte de réception" -#: ../settings/security/third-party/facebook.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via Facebook To do " -"so, you need to follow these steps:" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated" msgstr "" -#: ../settings/security/third-party/facebook.rst:9 -msgid "Register Facebook App" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_at}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:11 -msgid "" -"Visit [https://developers.facebook.com/apps/] and click on \"Add a new App\"" +#: ../misc/variables/article.rst:1 +msgid "Article > Visibility" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "initial page" +#: ../misc/variables/article.rst:1 +msgid "``#{article.internal}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:17 -msgid "After that enter the app settings" +#: ../misc/variables/article.rst:1 +msgid "``false`` or ``true`` (false if not internal)" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "Create App" +#: ../misc/variables/article.rst:1 +msgid "Article Text as HTML (not referenced)" msgstr "" -#: ../settings/security/third-party/facebook.rst:22 -msgid "Navigate to \"Settings\" and fill in this infromation" +#: ../misc/variables/article.rst:1 +msgid "``#{article.body_as_html}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "App Settings" +#: ../misc/variables/article.rst:1 +msgid "``Test`` with formatting" msgstr "" -#: ../settings/security/third-party/facebook.rst:27 -msgid "Navigate to app review and Check \"Make [appname] public?\"" +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "Ticket > Article#" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "App Review" +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "``#{ticket.article_count}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:35 -msgid "Configure Zammad as Facebook App" +#: ../misc/variables/article.rst:1 +msgid "``1`` number of ticket articles" msgstr "" -#: ../settings/security/third-party/facebook.rst:37 +#: ../misc/variables/config.rst:2 +msgid "Config" +msgstr "Configuration" + +#: ../misc/variables/config.rst:6 msgid "" -"Navigate to \"Admin -> Security -> Third Party Applications\" and enter the " -"App ID and the App Secret. You can find this Key in the Dashbard of your " -"Facebok app." +"Below you'll find config related variables. These hold useful configuration " +"information that you can use within e.g. triggers to show necessary " +"information to your customer." msgstr "" +"Ci-dessous, vous trouverez les variables liées à la configuration. Celles " +"contiennent des informations utiles que vous pouvez utiliser, par exemple, " +"dans un déclencheur pour afficher des informations nécessaires au client." -#: ../settings/security/third-party/facebook.rst:None -msgid "Zammad Configuration" +#: ../misc/variables/config.rst:11 +msgid "Config Variables" +msgstr "Variables Configuration" + +#: ../misc/variables/config.rst:1 +msgid "Config > Fully Qualified Domain Name" msgstr "" -#: ../settings/security/third-party/facebook.rst:44 -#: ../settings/security/third-party/github.rst:43 -#: ../settings/security/third-party/gitlab.rst:46 -msgid "" -"Now you can link accounts via \"Avatar -> Profile -> Link Accounts\" or " -"login via Zammad login page." +#: ../misc/variables/config.rst:1 +msgid "``#{config.fqdn}``" msgstr "" -#: ../settings/security/third-party/github.rst:2 -#: ../system/integrations/github.rst:2 -msgid "GitHub" +#: ../misc/variables/config.rst:1 +msgid "``zammad.example.com``" msgstr "" -#: ../settings/security/third-party/github.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via GitHub. To " -"activate the quick login you need to enable OAuth for GitHub." +#: ../misc/variables/config.rst:1 +msgid "Config > HTTP type" msgstr "" -#: ../settings/security/third-party/github.rst:8 -msgid "Register GitHub App" +#: ../misc/variables/config.rst:1 +msgid "``#{config.http_type}``" msgstr "" -#: ../settings/security/third-party/github.rst:10 -msgid "" -"Visit https://www.github.com/settings/applications/new and enter the app " -"settings. As callback URL enter \"https://zammad_host/auth/github/callback\" " -"where zammad_host has to be replaced with your Zammad FQDN" +#: ../misc/variables/config.rst:1 +msgid "``https`` or ``http``" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "Register OAuth app on www.github.com" +#: ../misc/variables/config.rst:1 +msgid "Config > Organization" msgstr "" -#: ../settings/security/third-party/github.rst:19 -msgid "Configure Zammad as GitHub App" +#: ../misc/variables/config.rst:1 +msgid "``#{config.organization}``" msgstr "" -#: ../settings/security/third-party/github.rst:21 +#: ../misc/variables/config.rst:1 msgid "" -"Enter the \"APP ID\" and the \"APP SECRET\" from the GitHub OAUTH " -"Applications Dashboard" +"``Zammad GmbH`` value set in `Branding `_" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub config in Zammad admin interface" +#: ../misc/variables/config.rst:1 +msgid "Config > Product Name" msgstr "" -#: ../settings/security/third-party/github.rst:28 +#: ../misc/variables/config.rst:1 +msgid "``#{config.product_name}``" +msgstr "" + +#: ../misc/variables/config.rst:1 msgid "" -"After you configured the GitHub credentials and activated the login method, " -"you should see a new icon on the login page." +"``Helpdesk`` value set in `Branding `_" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub logo on login page" +#: ../misc/variables/config.rst:1 +msgid "Config > SystemID" msgstr "" -#: ../settings/security/third-party/github.rst:34 -msgid "" -"If you click on the icon you will be redirected to GitHub and see something " -"similar to this:" +#: ../misc/variables/config.rst:1 +msgid "``#{config.system_id}``" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub oauth page" +#: ../misc/variables/config.rst:1 +msgid "``31`` (value between 1 and 99)" msgstr "" -#: ../settings/security/third-party/github.rst:40 -#: ../settings/security/third-party/gitlab.rst:42 -msgid "" -"When you grant the access you will be redirected to your Zammad instance and " -"logged in as a customer." +#: ../misc/variables/config.rst:1 +msgid "Config > Ticket Hook" msgstr "" -#: ../settings/security/third-party/gitlab.rst:2 -msgid "Gitlab" +#: ../misc/variables/config.rst:1 +msgid "``#{config.ticket_hook}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via Gitlab. To " -"activate the quick login you need to enable OAuth for Gitlab." +#: ../misc/variables/config.rst:1 +msgid "``Ticket#``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:8 -msgid "Register Gitlab App" +#: ../misc/variables/current-user.rst:2 +msgid "Current User" +msgstr "Utilisateur courant" + +#: ../misc/variables/current-user.rst:6 +msgid "" +"Current user variables always return values of the current user that caused " +"e.g. a trigger to run." msgstr "" +"Les variables Utilisateur courant retournent toujours les valeurs de " +"l'utilisateur qui a initié l'action, par exemple, lancer un déclencheur." -#: ../settings/security/third-party/gitlab.rst:10 -msgid "To register an app in Gitlab open your profile and select applications." +#: ../misc/variables/current-user.rst:8 +#, fuzzy +msgid "" +"Due to the above fact, these variables are often not (yet) set or available " +"for usage." msgstr "" +"En raison du fait ci-dessus, ces variables ne sont souvent pas ( encore ) " +"définies ou disponibles." -#: ../settings/security/third-party/gitlab.rst:12 +#: ../misc/variables/current-user.rst:10 msgid "" -"As callback URL enter \"https://zammad-fqdn/auth/gitlab/callback\" where " -"zammad-fqdn has to be replaced with your Zammad FQDN" +"In situations where e.g. schedulers or triggers run, this most likely is " +"nothing you want to use." msgstr "" +"Dans des situations où, par exemple, des planificateurs ou des déclencheurs " +"s’exécutent, l'utilisation de ces variables sera à éviter." -#: ../settings/security/third-party/gitlab.rst:None -msgid "Register OAuth app on gitlab instance" +#: ../misc/variables/current-user.rst:13 +msgid "Current User Variables" +msgstr "Variables Utilisateur courant" + +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Address" msgstr "" -#: ../settings/security/third-party/gitlab.rst:18 -msgid "Just select *read_user* under scopes as in the screenshot and save it." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.address}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:21 -msgid "Configure Zammad as Gitlab App" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set" msgstr "" -#: ../settings/security/third-party/gitlab.rst:23 -msgid "" -"Enter the \"APP ID\" and the \"APP SECRET\" from the Gitlab OAUTH " -"Applications Dashboard and your Gitlab-URL in the \"SITE\" field." +#: ../misc/variables/current-user.rst:1 +#, fuzzy +msgid "Current User > Avatar" +msgstr "Utilisateur courant" + +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab config in Zammad admin interface" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "avatar picture with width and height in pixel (e.g. 60,60)" msgstr "" -#: ../settings/security/third-party/gitlab.rst:30 -msgid "" -"After you configured the Gitlab credentials and activated the login method, " -"you should see a new icon on the login page." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created at" msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab logo on login page" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_at}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:36 -msgid "" -"If you click on the icon you will be redirected to Gitlab and see something " -"similar to this:" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab oauth page" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Address" msgstr "" -#: ../settings/security/third-party/google.rst:4 -msgid "" -"With some easy and fast steps, you can enable Zammad to authenticate your " -"users via Google." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.address}``" msgstr "" -#: ../settings/security/third-party/google.rst:8 -msgid "Register a Google App" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Avatar" msgstr "" -#: ../settings/security/third-party/google.rst:10 -msgid "" -"First of all, we need to create a new project - you can skip this step if " -"you already have one." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/google.rst:15 -msgid "" -"Use this link to create a new project: https://console.cloud.google.com/" -"projectcreate" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Department" msgstr "" -#: ../settings/security/third-party/google.rst:18 -msgid "" -"Now expand the menu, expand \"APIs & Services\" and select \"Credentials\". " -"Go to the tab \"OAuth consent screen\" first and ensure to fill in the " -"requested information - without doing so you can't create credentials!" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.department}``" msgstr "" -#: ../settings/security/third-party/google.rst:None -msgid "Creating a consent screen" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Sales`` or empty if not set" msgstr "" -#: ../settings/security/third-party/google.rst:25 -msgid "" -"After filling in and saving the consent screen information, you can go to " -"the \"Credentials\" tab and create new \"OAuth client ID\"-Credentials." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Email" msgstr "" -#: ../settings/security/third-party/google.rst:28 -msgid "" -"Fill in the necessary information as follows and replace ``zammad_host`` " -"with your FQDN:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.email}``" msgstr "" -#: ../settings/security/third-party/google.rst:31 -msgid "**Application type** ``[x] Web application``" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``jdoe@customer.tld``" msgstr "" -#: ../settings/security/third-party/google.rst:34 -msgid "**Authorized JavaScript origins** ``https://zammad_host/``" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Fax" msgstr "" -#: ../settings/security/third-party/google.rst:37 -msgid "" -"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" -"callback``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.fax}``" msgstr "" -#: ../settings/security/third-party/google.rst:None -msgid "Adding a new OAuth client ID" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``004930123464789`` or empty if not set" msgstr "" -#: ../settings/security/third-party/google.rst:43 -msgid "" -"After creating the credentials, go to your Zammad installation and navigate " -"to \"Admin > Security > Third Party Applications\" > Google. Enter your " -"Client ID and Client secret here." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Firstname" msgstr "" -#: ../settings/security/third-party/google.rst:None -msgid "Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.firstname}``" msgstr "" -#: ../settings/security/third-party/google.rst:50 -msgid "After submitting, the login via Google can be used." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``John`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:2 -msgid "Microsoft" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Lastname" msgstr "" -#: ../settings/security/third-party/microsoft.rst:4 -msgid "" -"Zammad's Microsoft connection allows your users with Microsoft accounts to " -"login. This works for Azure users as well and can be an alternative to :doc:" -"`/system/integrations/ldap/index`." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.lastname}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:10 -msgid "" -"This documentation part does not cover our :doc:`📧 Microsoft 365 email " -"channel `." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Login" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screenshot showing Microsoft login button on Zammad login screen." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.login}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:30 -#: ../settings/security/third-party/microsoft.rst:53 -msgid "Supported account types:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Mobile" msgstr "" -#: ../settings/security/third-party/microsoft.rst:22 -msgid "" -"Please note that Zammad only supports these account types (App dependent):" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.mobile}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:35 -msgid "Avatars of signing in users:" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``0049176123456789`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:33 -msgid "" -"Zammad currently ignores user avatars. If the user is registered with e.g. " -"Gravatar, Zammad will fetch the avatar from there if enabled. See :doc:" -"`Zammad Image Service ` for more." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Note" msgstr "" -#: ../settings/security/third-party/microsoft.rst:38 -msgid "Step 1 - Register a Microsoft App for Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.note}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:40 -msgid "" -"Login to the `Microsoft Azure Portal `_ and " -"navigate to App registrations to create a new app. Provide the requested " -"information as follows and register your app." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Some note to this user`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:46 -msgid "Name:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Phone" msgstr "" -#: ../settings/security/third-party/microsoft.rst:45 -msgid "" -"Any meaningful name fitting, this name will be displayed to users trying to " -"authenticate with this app." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.phone}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:49 -msgid "Choose one of the above mentioned account types (see Limitations)." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``004930123456789`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:51 -msgid "" -"The correct account type depends on your use case. If you want to use the " -"authentication internal only, choose the first option. If you're unsure, use " -"the \"Help me choose...\" link." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > VIP" msgstr "" -#: ../settings/security/third-party/microsoft.rst:58 -msgid "Redirect URI (optional):" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.vip}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:56 -msgid "" -"Select web and provide your callback URL. The callback URL looks like this: " -"``https://zammad.domain.tld/auth/microsoft_office365/callback``" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Web" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to register a Microsoft app" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.web}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "Within **API permissions** add the following permissions:" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``https://zammad.org`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:69 -msgid "``User.Read``" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Department" msgstr "" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "Contacts" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.department}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "``Contacts.Read``" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Email" msgstr "" -#: ../settings/security/third-party/microsoft.rst:73 -msgid "" -"You can find these permissions within *Microsoft Graph → Delegated " -"permissions*." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.email}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to add required API permissions" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Fax" msgstr "" -#: ../settings/security/third-party/microsoft.rst:80 -msgid "" -"Within **Certificates & secrets** create a new client secret. Note down the " -"returned secret **value** for later. **Do not** use the secret ID!" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.fax}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to create a new app secret" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Firstname" msgstr "" -#: ../settings/security/third-party/microsoft.rst:88 -msgid "" -"From **Overview** copy your apps *Application (client) ID*. If you're using " -"a single tenant app, please also copy *Directory (tenant) ID*. You now have " -"all required information for Zammad." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.firstname}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to retreive application client and tenant IDs" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Lastname" msgstr "" -#: ../settings/security/third-party/microsoft.rst:98 -msgid "Step 2 - Add App Credentials to Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.lastname}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:100 -msgid "" -"Navigate to Security > Third-party Applications (Tab) within Zammad's admin " -"settings. Scroll down to the section *Authentication via Microsoft* and fill " -"in the required information." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Login" msgstr "" -#: ../settings/security/third-party/microsoft.rst:105 -msgid "App ID:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.login}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:105 -msgid "This is your *Application (client) ID*." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Mobile" msgstr "" -#: ../settings/security/third-party/microsoft.rst:108 -msgid "App secret:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.mobile}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:108 -msgid "This is your *client secret* (value)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Note" msgstr "" -#: ../settings/security/third-party/microsoft.rst:113 -msgid "App Tenant ID:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.note}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:111 -msgid "" -"**optional** only required for apps that use account type *Accounts in this " -"organizational directory only (Default Directory only - Single tenant).*" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Domain based assignment" msgstr "" -#: ../settings/security/third-party/microsoft.rst:115 -msgid "" -"Apply your settings by pressing submit and activate *Authentication via " -"Microsoft*." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.domain_assignment}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "" -"Screencast showing how to add app credentials and activating the\n" -"authentication method" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Domain" msgstr "" -#: ../settings/security/third-party/saml.rst:2 -msgid "SAML" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.domain}``" msgstr "" -#: ../settings/security/third-party/saml.rst:4 -msgid "" -"Connect your SAML (Security Assertion Markup Language) identity provider as " -"a single sign-on (SSO) method." +#: ../misc/variables/current-user.rst:1 +msgid "``zammad.com`` or empty if not set" msgstr "" -#: ../settings/security/third-party/saml.rst:7 -msgid "" -"SAML is an open standard for SSO authentication (among other things). Sign-" -"ins are shared across multiple **service providers** and managed by a " -"central **identity provider** (IdP)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Name" msgstr "" -#: ../settings/security/third-party/saml.rst:11 -msgid "" -"In this case, the service provider is Zammad, and the IdP is a software " -"service that you either host or subscribe to (*e.g.,* `Keycloak `_, `Redhat SSO Server `_, `ADFS `_, or `Okta `_)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.name}``" msgstr "" -#: ../settings/security/third-party/saml.rst:18 -msgid "" -"This guide assumes you are already using SAML within your organization (i." -"e., that your IdP is fully set up)." +#: ../misc/variables/current-user.rst:1 +msgid "``Zammad GmbH``" msgstr "" -#: ../settings/security/third-party/saml.rst:21 -msgid "" -"Please note: Our instructions are based on connecting Zammad with Keycloak." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Note" msgstr "" -#: ../settings/security/third-party/saml.rst:25 -msgid "Step 1: Configure Your IdP" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.note}``" msgstr "" -#: ../settings/security/third-party/saml.rst:28 -msgid "Add Zammad as a Client/App" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``A note to the organization of the user`` or empty if not set" msgstr "" -#: ../settings/security/third-party/saml.rst:30 -msgid "" -"Import Zammad into your IdP using the XML configuration found at ``https://" -"your.zammad.domain/auth/saml/metadata``." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Shared organization" msgstr "" -#: ../settings/security/third-party/saml.rst:33 -msgid "" -"If your IdP doesn't support XML import, you will have to configure Zammad as " -"a new client/app manually using the above XML metadata file for reference." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.shared}``" msgstr "" -#: ../settings/security/third-party/saml.rst:36 -msgid "For instance, when you see this tag:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > VIP" msgstr "" -#: ../settings/security/third-party/saml.rst:42 -msgid "" -"Set the **Assertion Consumer Service Binding URL** (sometimes also listed as " -"**Valid Redirect URIs**) to ``http://your.zammad.domain/auth/saml/callback``." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.vip}``" msgstr "" -#: ../settings/security/third-party/saml.rst:47 -msgid "Set Up User Attribute Mapping" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Phone" msgstr "" -#: ../settings/security/third-party/saml.rst:49 -msgid "" -"Zammad requests the following user attributes (or “properties”) from the IdP:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.phone}``" msgstr "" -#: ../settings/security/third-party/saml.rst:51 -msgid "Email address (``email``)" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated at" msgstr "" -#: ../settings/security/third-party/saml.rst:52 -msgid "Full name (``name``)" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_at}``" msgstr "" -#: ../settings/security/third-party/saml.rst:53 -msgid "Given name (``first_name``)" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Address" msgstr "" -#: ../settings/security/third-party/saml.rst:54 -msgid "Family name (``last_name``)" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.address}``" msgstr "" -#: ../settings/security/third-party/saml.rst:56 -msgid "" -"You may need to set up “mappers” (or “mappings”) to tell your IdP how user " -"attributes in SAML correspond to those in Zammad. For a more detailed " -"breakdown, refer to the XML metadata file referenced in the previous section." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Avatar" msgstr "" -#: ../settings/security/third-party/saml.rst:62 -msgid "Per-IdP Instructions" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/saml.rst:102 -msgid "Keycloak" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Department" msgstr "" -#: ../settings/security/third-party/saml.rst:65 -msgid "" -"**To add Zammad as a client,** save the XML configuration to disk (``https://" -"your.zammad.domain/auth/saml/metadata``) and use **Clients > Clients list > " -"Import client** in the Keycloak admin panel." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.department}``" msgstr "" -#: ../settings/security/third-party/saml.rst:70 -msgid "" -"To help Zammad **match its own user accounts to Keycloak users**, create a " -"user attribute (or “property”) mapper. In **Clients list**, click on your " -"newly created Client ID, choose the tab **Client scopes** and click on the " -"link which refers to your Zammad instance. Choose **Add mapper > By " -"configuration > User Property** and create a mapper with the following " -"entries:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Email" msgstr "" -#: ../settings/security/third-party/saml.rst:78 -msgid "**Name**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.email}``" msgstr "" -#: ../settings/security/third-party/saml.rst:80 -msgid "**Mapper Type**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Fax" msgstr "" -#: ../settings/security/third-party/saml.rst:81 -msgid "``User Property``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.fax}``" msgstr "" -#: ../settings/security/third-party/saml.rst:82 -msgid "**Property**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Firstname" msgstr "" -#: ../settings/security/third-party/saml.rst:83 -msgid "``emailAddress``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.firstname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:84 -msgid "**SAML Attribute Name**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Lastname" msgstr "" -#: ../settings/security/third-party/saml.rst:86 -msgid "**SAML Attribute NameFormat**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.lastname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:87 -msgid "``basic``" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Login" msgstr "" -#: ../settings/security/third-party/saml.rst:89 -msgid "" -"In the example above, we're telling Zammad that whenever it receives a SAML " -"login request, it should take the ``email`` property from Keycloak, look for " -"a Zammad user with the same ``email`` attribute, and create a new session " -"for that user." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.login}``" msgstr "" -#: ../settings/security/third-party/saml.rst:95 -msgid "" -"If your Keycloak users' email addresses are stored on another property (*e." -"g.,* ``username``), adjust accordingly." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Mobile" msgstr "" -#: ../settings/security/third-party/saml.rst:98 -msgid "" -"Back in **Settings**, enter the Client ID (``https://your.zammad.domain/auth/" -"saml/metadata``) in the field **Master SAML Processing URL**." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.mobile}``" msgstr "" -#: ../settings/security/third-party/saml.rst:101 -msgid "You also need to enable **Sign assertions**." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Note" msgstr "" -#: ../settings/security/third-party/saml.rst:105 -msgid "Step 2: Configure Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.note}``" msgstr "" -#: ../settings/security/third-party/saml.rst:107 -msgid "" -"Enable SAML and enter your IdP's details in the Admin Panel under **Settings " -"> Security > Third Party Applications > Authentication via SAML**:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Phone" msgstr "" -#: ../settings/security/third-party/saml.rst:None -msgid "Example configuration of SAML part 1" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.phone}``" msgstr "" -#: ../settings/security/third-party/saml.rst:119 -msgid "Display name" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > VIP" msgstr "" -#: ../settings/security/third-party/saml.rst:116 -msgid "" -"Allows you to define a custom button name for SAML. This helps your users to " -"understand better what the button on the login page does." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.vip}``" msgstr "" -#: ../settings/security/third-party/saml.rst:119 -msgid "Defaults to ``SAML``." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``false`` or ``true``" msgstr "" -#: ../settings/security/third-party/saml.rst:123 -msgid "IDP SSO target URL" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Web" msgstr "" -#: ../settings/security/third-party/saml.rst:122 -msgid "" -"This is the target URL Zammad shall redirect to when the user presses the " -"SAML button. For Keycloak, this needs to look like https://your.domain/" -"realms/your-realm/protocol/saml" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.web}``" msgstr "" -#: ../settings/security/third-party/saml.rst:127 -msgid "IDP single logout target URL" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > VIP" msgstr "" -#: ../settings/security/third-party/saml.rst:126 -msgid "" -"This is the URL to which the single logout request and response should be " -"sent." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.vip}``" msgstr "" -#: ../settings/security/third-party/saml.rst:131 -#, fuzzy -msgid "IDP certificate" -msgstr "Intégrations" - -#: ../settings/security/third-party/saml.rst:130 -msgid "" -"The public certificate of your IDP for Zammad to verify during the callback " -"phase." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Web" msgstr "" -#: ../settings/security/third-party/saml.rst:145 -msgid "IDP certificate fingerprint" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.web}``" msgstr "" -#: ../settings/security/third-party/saml.rst:134 +#: ../misc/variables/ticket.rst:6 +#, fuzzy +#| msgid "" +#| "Below you can find all available ticket article-based variables within " +#| "Zammad. These can be called via Triggers for example. If you're unsure if " +#| "Zammad does support variables at the point you're at, you can try to type " +#| "``::`` to check." msgid "" -"The fingerprint of your IDPs public certificate to verify during callback " -"phase." +"Below you can find all available ticket-based variables within Zammad. These " +"can be called via triggers for example. If you're unsure if Zammad does " +"support variables at the point you're at, you can try to type ``::`` to " +"check." msgstr "" +"Ci dessous, vous pourrez trouver l'ensemble des variables des articles de " +"ticket disponibles dans Zammad. Elles peuvent être utilisées via les " +"Déclencheurs par exemple. Pour vous assurer que Zammad supporte les " +"variables à l'endroit où vous vous trouvez, vous pouvez taper ``::`` pour " +"vérifier." -#: ../settings/security/third-party/saml.rst:137 -msgid "🔏 **For the IdP certificate / certificate fingerprint:**" +#: ../misc/variables/ticket.rst:12 +msgid "Ticket Variables" msgstr "" -#: ../settings/security/third-party/saml.rst:139 -msgid "" -"Provide **only one or the other**—do not provide both! (Between the two, we " -"recommend the signing certificate itself: fingerprints use SHA-1, which `has " -"been broken for a while now `_.)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Accounted Time" msgstr "" -#: ../settings/security/third-party/saml.rst:144 -msgid "" -"**Keycloak users:** Find your certificate in the Keycloak admin panel under " -"**Realm Settings > Keys > Algorithm: RS256 > Certificate**." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.time_unit}``" msgstr "" -#: ../settings/security/third-party/saml.rst:151 -msgid "Name identifier format" +#: ../misc/variables/ticket.rst:1 +msgid "``1``, ``2.75`` or empty response" msgstr "" -#: ../settings/security/third-party/saml.rst:148 -msgid "" -"This is the unique identifiers field type. Usually it should be ``urn:oasis:" -"names:tc:SAML:1.1:nameid-format:emailAddress``." +#: ../misc/variables/ticket.rst:1 +msgid "``3``, any number of articles existing in the ticket right now" msgstr "" -#: ../settings/security/third-party/saml.rst:151 -msgid "Zammad **expects an email address as unique identifier**!" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Closing time" msgstr "" -#: ../settings/security/third-party/saml.rst:155 -msgid "UID attribute name" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.close_at}``" msgstr "" -#: ../settings/security/third-party/saml.rst:154 -msgid "" -"Here you can define an attribute that uniquely identifies the user. If " -"unset, the name identifier returned by the IDP is used." +#: ../misc/variables/ticket.rst:1 +msgid "2019-10-07 17:25:00 UTC" msgstr "" -#: ../settings/security/third-party/saml.rst:None -msgid "Example configuration of SAML part 2" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created at" msgstr "" -#: ../settings/security/third-party/saml.rst:163 -msgid "" -"Decide if the certificate for the connection to the IdP service has to be " -"verified or not (default: ``yes``)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_at}``" msgstr "" -#: ../settings/security/third-party/saml.rst:169 -msgid "Signing & Encrypting" +#: ../misc/variables/ticket.rst:1 +msgid "2019-10-07 16:25:00 UTC" msgstr "" -#: ../settings/security/third-party/saml.rst:169 -msgid "" -"Define if you want to sign, encrypt, do both or nothing for the requests." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Address" msgstr "" -#: ../settings/security/third-party/saml.rst:179 -msgid "Certificate (PEM)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.address}``" msgstr "" -#: ../settings/security/third-party/saml.rst:172 -msgid "" -"Paste the public certificate of your Zammad SAML client, if you want to " -"encrypt the requests." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Avatar" msgstr "" -#: ../settings/security/third-party/saml.rst:175 -#, fuzzy -msgid "Make sure the certificate is:" -msgstr "Intégrations" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.avatar(60,60)}``" +msgstr "" -#: ../settings/security/third-party/saml.rst:177 -msgid "already valid and not yet expired" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Department" msgstr "" -#: ../settings/security/third-party/saml.rst:178 -#, fuzzy -msgid "no CA certificate" -msgstr "Intégrations" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.department}``" +msgstr "" -#: ../settings/security/third-party/saml.rst:179 -msgid "valid for signing and encrypting" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Email" msgstr "" -#: ../settings/security/third-party/saml.rst:185 -msgid "Private key (PEM)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.email}``" msgstr "" -#: ../settings/security/third-party/saml.rst:182 -msgid "" -"Paste the private key of your Zammad SAML client here, if you want to sign " -"the requests." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Fax" msgstr "" -#: ../settings/security/third-party/saml.rst:185 -msgid "Make sure the key is an RSA key with a length of at least 2048 bits." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.fax}``" msgstr "" -#: ../settings/security/third-party/saml.rst:188 -msgid "Private key secret" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Firstname" msgstr "" -#: ../settings/security/third-party/saml.rst:188 -msgid "If your private key is secured with a secret, you can provide it here." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.firstname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:192 -msgid "Your callback URL" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Lastname" msgstr "" -#: ../settings/security/third-party/saml.rst:191 -msgid "" -"This URL is needed for your IdP configuration so it knows where to redirect " -"to after successful authentication." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.lastname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:194 -msgid "" -"After saving your input by clicking on the \"Submit\" button, Zammad " -"verifies the provided keys/certificates (e.g. if they are valid for signing/" -"encrypting and if they aren't expired)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Login" msgstr "" -#: ../settings/security/third-party/saml.rst:199 -msgid "" -"See :ref:`automatic account linking ` for details " -"on how to link existing Zammad accounts to IdP accounts." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.login}``" msgstr "" -#: ../settings/security/third-party/saml.rst:205 -msgid "Automatic account linking doesn't work" -msgstr "La liaison automatique de compte ne fonctionne pas" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Mobile" +msgstr "" -#: ../settings/security/third-party/saml.rst:206 -msgid "" -"Have you double-checked your IdP's user attribute mapping configuration?" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.mobile}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via Twitter. To do " -"so, you need to follow these steps:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Note" msgstr "" -#: ../settings/security/third-party/twitter.rst:8 -msgid "Register Twitter App" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.note}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:10 -msgid "Go to https://dev.twitter.com/apps and login with your account." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Phone" msgstr "" -#: ../settings/security/third-party/twitter.rst:15 -msgid "Click on \"Create App\"" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.phone}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "new app page" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > VIP" msgstr "" -#: ../settings/security/third-party/twitter.rst:20 -msgid "" -"Enter app settings. As \"Callback URL\" you need to enter ``https://" -"zammad_host/api/v1/external_credentials/twitter/callback``. You need to " -"replace ``zammad_host`` with the domain of your Zammad system." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.vip}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:24 -msgid "" -"After the app has been created, update the application icon and organization " -"attributes." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Web" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "set permissions to receive and send direct messages" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.web}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:30 -msgid "" -"Next we need to set ``read, write and access direct messages`` permissions " -"for the app." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Address" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "click on Keys & Access Token, note them" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.address}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:36 -msgid "" -"Go to \"Keys and Access Token\" tab and note the \"Consumer Key\" and " -"\"Consumer Secret\"." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Avatar" msgstr "" -#: ../settings/security/third-party/twitter.rst:40 -msgid "Configure Zammad as Twitter App" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:42 -msgid "" -"Go to \"Admin > Security > Twitter > Third Party Applications > Twitter\" " -"Section." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Department" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "Admin > Security > Third Party Applications" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.department}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:48 -msgid "" -"Fill in the \"Twitter Key\" and the \"Twitter Secret\" and click the " -"\"Submit\" button." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Email" msgstr "" -#: ../settings/security/third-party/twitter.rst:51 -msgid "" -"Now you can link accounts via \"Avatar > Profile > Link Accounts\" or login " -"via Zammad login page." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.email}``" msgstr "" -#: ../settings/security/two-factor.rst:11 -msgid "Two-factor Authentication Methods" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Fax" msgstr "" -#: ../settings/security/two-factor.rst:2 -msgid "Two-Factor Authentication" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.fax}``" msgstr "" -#: ../settings/security/two-factor.rst:4 -msgid "" -"Two-factor authentication (2FA) enhances the security of Zammad accounts by " -"adding an extra layer of verification beyond a password. It requires users " -"to provide two different types of authentication factors, typically " -"something they know (like a password) and something they possess (like a " -"mobile device or a security token), to ensure that only authorized " -"individuals can access the account." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Firstname" msgstr "" -#: ../settings/security/two-factor.rst:19 -msgid "Enable Recovery Codes" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.firstname}``" msgstr "" -#: ../settings/security/two-factor.rst:21 -msgid "" -"Recovery codes are one-time use security codes that can be used by the user " -"if they lose access to their other two-factor authentication methods. They " -"cannot be used on their own, they can only be activated if at least one two-" -"factor authentication method is enabled." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Lastname" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Enable Recovery Codes Setting" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.lastname}``" msgstr "" -#: ../settings/security/two-factor.rst:30 -msgid "" -"Recovery codes can only be used as a backup method. If enabled, they will be " -"automatically generated for the user once they set up their initial two-" -"factor authentication method." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Login" msgstr "" -#: ../settings/security/two-factor.rst:34 -msgid "" -"The user will be asked to print out or save the generated recovery codes in " -"a safe place. Once used, a recovery code cannot be reused." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.login}``" msgstr "" -#: ../settings/security/two-factor.rst:37 -msgid "" -"Users will also have an option to regenerate their recovery codes at any " -"time, which invalidates already existing recovery codes and provides them " -"with a list of fresh codes." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Mobile" msgstr "" -#: ../settings/security/two-factor.rst:41 -msgid "" -"After you enable this setting, when the user completes a setup of their " -"initial two-factor authentication method, they will be presented with a list " -"of recovery codes and instructed to save them for later use." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.mobile}``" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Recovery Codes Generation Modal Dialog" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Note" msgstr "" -#: ../settings/security/two-factor.rst:50 -msgid "Enforce the Set Up of the Two-Factor Authentication" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.note}``" msgstr "" -#: ../settings/security/two-factor.rst:52 -msgid "" -"In case you wish to require your users to set up at least one two-factor " -"authentication method for their account, you can do this by selecting " -"specific user roles the requirement applies to in **Enforced for user " -"roles** setting. Of course you must have at least one two-factor " -"authentication method enabled for this setting to take effect." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Phone" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Enforced for User Roles Setting" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.phone}``" msgstr "" -#: ../settings/security/two-factor.rst:62 -msgid "" -"After you change this setting, if the user has one of the selected roles on " -"their account, they will be forced to set up the two-factor authentication " -"upon next sign in or application reload." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > VIP" msgstr "" -#: ../settings/security/two-factor.rst:66 -msgid "" -"A modal dialog with instructions will be shown, and they will not be able to " -"do any work before they set up at least one two-factor method." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.vip}``" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Modal Dialog for Enforcing Two-Factor Authentication Set Up" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Web" msgstr "" -#: ../settings/security/two-factor.rst:74 -msgid "Reset Two-Factor Authentication for a Specific User" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.web}``" msgstr "" -#: ../settings/security/two-factor.rst:76 -msgid "" -"In case an user isn't able to login anymore because of an inaccessible " -"second factor, you can reset the user's 2FA method." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Escalation at" msgstr "" -#: ../settings/security/two-factor.rst:79 -msgid "" -"To do this, go to the user management and search for the relevant user. " -"After you found the account, click the button in the action column and " -"select \"Manage Two-Factor Authentication\":" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.escalation_at}``" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Context menu in action column in user management" +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable" msgstr "" -#: ../settings/security/two-factor.rst:87 -msgid "" -"After selecting this, you can see a dialog where you can either reset one " -"2FA method or reset all of the user's 2FA methods:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > First response" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Dialog for resetting user's 2FA method" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.first_response_at}``" msgstr "" -#: ../settings/security/two-factor.rst:94 -msgid "" -"Choose the fitting one, click on the corresponding \"Remove ...\" button and " -"confirm your action. The user now has to setup a new 2FA method, depending " -"on your 2FA configuration." +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable yet" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:2 -msgid "Authenticator App" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Assign Follow-Ups" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:4 -msgid "" -"The authenticator app method is a type of two-factor authentication that " -"uses a mobile application to generate one-time codes for account " -"verification. After setting up the authenticator app on their device, the " -"user links it to their Zammad account." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_assignment}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:12 -msgid "" -"When logging in, the user is prompted to enter a time-sensitive code " -"generated by the app, in addition to their password. This code acts as the " -"second factor of authentication, providing an extra layer of security as it " -"changes periodically and is unique to the user's device." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Assignment Timeout" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:None -msgid "Security Code in Google Authenticator App" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.assignment_timeout}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:22 -msgid "" -"The app generates codes based on a shared secret key stored securely on both " -"the user's device and the server, ensuring a synchronized and secure " -"authentication process. The method of generating the codes is sometimes also " -"called TOTP (time-based one-time password)." +#: ../misc/variables/ticket.rst:1 +msgid "``20`` or empty if not configured" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:28 -msgid "Enabling the Authenticator App Method" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Follow-up possible" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:30 -#: ../settings/security/two-factor/security-keys.rst:28 -msgid "To enable the method, just toggle the switch on in the settings." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_possible}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:None -msgid "Authenticator App Switch in Settings" +#: ../misc/variables/ticket.rst:1 +msgid "``no`` or ``yes``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:36 -msgid "" -"Now the users will be able to set up this two-factor authentication method " -"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " -"Once they do, on next sign-in with password, they will be asked to provide " -"an additional security code generated by their mobile device." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Name" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:2 -msgid "Security Keys" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.name}``" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:4 -msgid "" -"The security keys method is a type of a two-factor authentication that uses " -"Web Authentication API in the browser for verifying user's identity. The " -"user can register multiple hardware or software security keys with their " -"Zammad account and then they can use it during the sign-in process." +#: ../misc/variables/ticket.rst:1 +msgid "``Sales``" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:12 -msgid "" -"When logging in, the user is prompted to provide the same security key they " -"registered with their account, in addition to their password. This key acts " -"as the second factor of authentication, providing an extra layer of security." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Note" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:None -msgid "Security Key dialog in Safari on macOS" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.note}``" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:21 -msgid "" -"The type of the key can range from hardware USB sticks to passkeys stored in " -"a device of user's choice. Which type can be used depends on the browser " -"flavor and the platform of the user." +#: ../misc/variables/ticket.rst:1 +msgid "``Note about this group``" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:26 -msgid "Enabling the Security Keys Method" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > ID" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:None -msgid "Security Keys Switch in Settings" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.id}``" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:34 -msgid "" -"Now the users will be able to set up this two-factor authentication method " -"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " -"Once they do, on next sign-in with password, they will be asked to provide " -"the same security key they registered during the setup." +#: ../misc/variables/ticket.rst:1 +msgid "``17``, ``5281``, ..." msgstr "" -#: ../settings/system/system-selfhosted.include.rst:3 -msgid "" -"Below settings are only available to self hosted users. In hosted " -"environments we're handling these settings for you to ensure service " -"stability." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact (agent)" msgstr "" -#: ../settings/system/base.rst:11 -msgid "Fully Qualified Domain Name" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_agent_at}``" msgstr "" -#: ../settings/system/base.rst:7 -msgid "The URL of your Zammad installation." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact (customer)" msgstr "" -#: ../settings/system/base.rst:9 ../settings/system/base.rst:17 -msgid "This setting is used within :doc:`/system/variables` and notifications." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_customer_at}``" msgstr "" -#: ../settings/system/system-base.include.rst:1 -msgid "It is automatically set by the *Getting Started wizard*." +#: ../misc/variables/ticket.rst:1 +msgid "" +"``2019-10-07 16:25:00 UTC`` or empty if not applicable yet (Please note " +"`Ticket last contact behavior Settings `_ for this)" msgstr "" -#: ../settings/system/system-base.include.rst:5 -msgid "Changing this setting also changes callback URLs for your channels etc." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact" msgstr "" -#: ../settings/system/system-base.include.rst:6 -msgid "This setting can have negative affects on being able to login." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_at}``" msgstr "" -#: ../settings/system/base.rst:19 -msgid "HTTP type" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Number" msgstr "" -#: ../settings/system/base.rst:14 -msgid "" -"The HTTP type tells your installation how your clients connect. This is " -"relevant for authentication and cookie security." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.number}``" msgstr "" -#: ../settings/system/base.rst:31 -msgid "SystemID" +#: ../misc/variables/ticket.rst:1 +msgid "``31001``, ``201910731001``, ..." msgstr "" -#: ../settings/system/base.rst:22 -msgid "" -"This ID is being used within your ticket number. In case you're " -"communicating with another ticket system with similar ticket number schemes " -"this ID greatly reduces the risk of false follow ups." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain based assignment" msgstr "" -#: ../settings/system/base.rst:26 -msgid "" -"The SystemID is randomly selected upon installation of Zammad (``1-99``)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain_assignment}``" msgstr "" -#: ../settings/system/base.rst:30 -msgid "" -"**Do not** change this setting in a productive system! Your Zammad " -"installation may no longer recognize old ticket number based follow ups upon " -"change!" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain" msgstr "" -#: ../settings/system/frontend.rst:2 -msgid "Frontend" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain}``" msgstr "" -#: ../settings/system/frontend.rst:22 -msgid "Core Workflow Ajax Mode" +#: ../misc/variables/ticket.rst:1 +msgid "``domain.tld`` or empty if not set" msgstr "" -#: ../settings/system/frontend.rst:6 -msgid "" -"This setting allows administrators to enforce :doc:`/system/core-workflows` " -"to use Ajax-Calls instead of web sockets. You'll usually only need this if " -"you experience serious issues as noted below." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Name" msgstr "" -#: ../settings/system/frontend.rst:10 -msgid "**🤓 Possible (technical) reasons**" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.name}``" msgstr "" -#: ../settings/system/frontend.rst:12 -msgid "" -"In some cases, your network structure (e.g. firewalls, proxies) may " -"disconnect long web socket connections. This leads to select fields staying " -"empty (e.g. owner selection *after* selecting your group) or fields not " -"shown / hidden (e.g. when switching to or from pending states, the \"pending " -"till\" field not showing / hiding)." +#: ../misc/variables/ticket.rst:1 +msgid "``Zammad GmbH`` or empty if not set" msgstr "" -#: ../settings/system/frontend.rst:18 -msgid "" -"Please keep in mind that the Ajax fallback may cause serious pressure on " -"your application server. If you have the choice stick to web sockets." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Note" msgstr "" -#: ../settings/system/frontend.rst:22 -msgid "Default: ``no`` (inactive)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.note}``" msgstr "" -#: ../settings/system/frontend.rst:53 -msgid "Show calendar weeks in the picker of date/datetime fields" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Shared organization" msgstr "" -#: ../settings/system/frontend.rst:25 -msgid "" -"With this setting you can instruct Zammad to provide week number display " -"globally for all users. Calendar with week number display are usually used " -"in business sectors and may not be relevant for everyone." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.shared}``" msgstr "" -#: ../settings/system/frontend.rst:29 -msgid "" -"This setting affects *all areas* - you'll also see week numbers in the admin " -"panel for e.g. triggers and macros." +#: ../misc/variables/ticket.rst:1 +#, fuzzy +msgid "Ticket > Organization > VIP" +msgstr "Sociétés" + +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.vip}``" msgstr "" -#: ../settings/system/frontend.rst:32 -msgid "Default: ``no`` (not shown)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Address" msgstr "" -#: ../settings/system/frontend.rst:53 -msgid "Here's the difference:" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.address}``" msgstr "" -#: ../settings/system/frontend.rst:0 -msgid "Screenshot showing Zammad's date picker (in the default way)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Avatar" msgstr "" -#: ../settings/system/frontend.rst:41 -msgid "Set to ``no``" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.avatar(60,60)}``" msgstr "" -#: ../settings/system/frontend.rst:0 -msgid "" -"Screenshot showing Zammad's date picker with\n" -"week numbers enabled" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Department" msgstr "" -#: ../settings/system/frontend.rst:50 -msgid "Set to ``yes``" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.department}``" msgstr "" -#: ../settings/system/index.rst:4 -msgid "" -"For your overview we split each tab within system settings into its own page:" +#: ../misc/variables/ticket.rst:1 +msgid "``Support`` or empty if not set" msgstr "" -#: ../settings/system/index.rst:16 -#, fuzzy -msgid "Console Based Settings" -msgstr "Paramètres" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Email" +msgstr "" -#: ../settings/system/index.rst:18 -msgid "" -"There's some console based settings we didn't put into the UI. However, you " -"may find them helpful - you can find them in our :docs:`hidden settings ` section." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.email}``" msgstr "" -#: ../settings/system/network.rst:2 -msgid "Network" +#: ../misc/variables/ticket.rst:1 +msgid "``agent@company.tld`` or empty if not set" msgstr "" -#: ../settings/system/network.rst:8 -msgid "" -"The proxy settings can only be saved after successfully testing the proxy " -"connection." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Fax" msgstr "" -#: ../settings/system/network.rst:15 -msgid "Proxy Address." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.fax}``" msgstr "" -#: ../settings/system/network.rst:12 -msgid "" -"Allows you to provide a proxy server if needed. This is relevant for network " -"communication by Zammad." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Firstname" msgstr "" -#: ../settings/system/network.rst:15 -msgid "It **does not** affect the update process or Elasticsearch." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.firstname}``" msgstr "" -#: ../settings/system/network.rst:18 -msgid "Username for proxy connection." +#: ../misc/variables/ticket.rst:1 +msgid "``Max`` or empty if not set" msgstr "" -#: ../settings/system/network.rst:18 -msgid "" -"If your proxy server requires authentication, provide the username here." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Lastname" msgstr "" -#: ../settings/system/network.rst:21 -msgid "Password for proxy connection." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.lastname}``" msgstr "" -#: ../settings/system/network.rst:21 -msgid "" -"If your proxy server requires authentication, provide the password here." +#: ../misc/variables/ticket.rst:1 +msgid "``Mustermann`` or empty if not set" msgstr "" -#: ../settings/system/network.rst:26 -msgid "No proxy for the following hosts." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Login" msgstr "" -#: ../settings/system/network.rst:24 -msgid "" -"Exception list for hosts you can't or don't want to reach via proxy server." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.login}``" msgstr "" -#: ../settings/system/network.rst:27 -msgid "Default: ``localhost,127.0.0.0,::1``" +#: ../misc/variables/ticket.rst:1 +msgid "``agent``" msgstr "" -#: ../settings/system/services.rst:2 -msgid "Services" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Mobile" msgstr "" -#: ../settings/system/services.rst:10 -msgid "Image Service" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.mobile}``" msgstr "" -#: ../settings/system/services.rst:5 -msgid "Defines the backend for user and organization image lookups." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Note" msgstr "" -#: ../settings/system/services.rst:7 -msgid "Default: ``Zammad Image Service`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.note}``" msgstr "" -#: ../settings/system/services.rst:9 -msgid "" -"Make sure your on premise installation has ``HTTPS`` access to ``images." -"zammad.com``." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Phone" msgstr "" -#: ../settings/system/services.rst:18 -msgid "Geo Calendar Service" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.phone}``" msgstr "" -#: ../settings/system/services.rst:13 -msgid "" -"Defines the backend for geo calendar lookups. Used for initial calendar " -"setup." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > VIP" msgstr "" -#: ../settings/system/services.rst:16 -msgid "Default: ``Zammad GeoCalendar Service`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.vip}``" msgstr "" -#: ../settings/system/services.include.rst:2 -msgid "" -"Make sure your on premise installation has ``HTTPS`` access to ``geo.zammad." -"com``." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Web" msgstr "" -#: ../settings/system/services.rst:26 -msgid "Geo IP Service" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.web}``" msgstr "" -#: ../settings/system/services.rst:21 -msgid "" -"Defines the backend for geo IP lookups. Shows also location of an IP address " -"if an IP address is shown." +#: ../misc/variables/ticket.rst:1 +msgid "``https://zammad.com`` or empty if not set" msgstr "" -#: ../settings/system/services.rst:24 -msgid "Default: ``Zammad GeoIP Service`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Pending till" msgstr "" -#: ../settings/system/services.rst:32 -msgid "Geo Location Service" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.pending_time}``" msgstr "" -#: ../settings/system/services.rst:29 -msgid "" -"Defines the backend for geo location lookups to store geo locations for " -"addresses." +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not set" msgstr "" -#: ../settings/system/services.rst:32 -msgid "" -"Default: ``OpenStreetMap (ODbL 1.0, http://osm.org/copyright)`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Priority > Name" msgstr "" -#: ../settings/system/services.rst:36 -msgid "" -"You can find a detailed privacy information on what we store for how long on " -"our :docs:`Privacy Appendix ` inside of our System " -"Documentation." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.priority.name}``" msgstr "" -#: ../settings/system/storage.rst:2 -msgid "Storage" +#: ../misc/variables/ticket.rst:1 +msgid "``2 normal``" msgstr "" -#: ../settings/system/storage.rst:6 -msgid "" -"Here you can define where Zammad stores attachments for tickets and the " -"knowledge base. By default, we're writing to the ``Database`` - you can " -"switch to ``Filesystem`` or ``Simple Storage (S3)`` at any time. In this " -"case please have a look on the following instructions." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > State > Name" msgstr "" -#: ../settings/system/storage.rst:11 -msgid "" -"If you have a busy Zammad instance, we strongly encourage you to use " -"filesystem storage instead of \"Database\". This will greatly improve system " -"performance (de-crease database load and size)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.state.name}``" msgstr "" -#: ../settings/system/storage.rst:19 -msgid "Database" +#: ../misc/variables/ticket.rst:1 +msgid "``new``, ``open``, ..." msgstr "" -#: ../settings/system/storage.rst:17 -msgid "" -"This is the default storage method. The attachments are stored directly in " -"the database. If your Zammad instance grows, we recommend one of the other " -"methods to maintain performance." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Tags" msgstr "" -#: ../settings/system/storage.rst:38 -msgid "Filesystem" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.tags}``" msgstr "" -#: ../settings/system/storage.rst:22 +#: ../misc/variables/ticket.rst:1 msgid "" -"This storage method is recommended for all Zammad instances, especially for " -"those with a higher load. If you choose filesystem, your files are written " -"to ``/opt/zammad/storage/``." +"Currently not available, see `Issue 2769 `_" msgstr "" -#: ../settings/system/storage.rst:26 -msgid "" -"Moving attachments from \"Database\" to \"Filesystem\" can be run during " -"production use. However, you should consider your framework conditions (e.g. " -"bandwidth, system load in production) to define the right moment." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Title" msgstr "" -#: ../settings/system/storage.rst:32 -msgid "**You noticed slow updates of Zammad?**" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.title}``" msgstr "" -#: ../settings/system/storage.rst:34 +#: ../misc/variables/ticket.rst:1 msgid "" -"While Zammad is beeing updated, it enforces a recursive \"change " -"owner\" (chown) for this directory. For instances with many files this can " -"be time consuming. To mitigate that you can move your files and create a " -"symlink in ``/opt/zammad/storage/`` to the new directory. Of course you have " -"to make sure on your own that the permissions are always correct." +"``My amazing Subject`` (normally subject, can be edited within Interface and " +"thus differ)" msgstr "" -#: ../settings/system/storage.rst:95 -msgid "Simple Storage (S3)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated at" msgstr "" -#: ../settings/system/storage.rst:41 -msgid "" -"To use the Simple Storage (S3), you have to provide some settings, which " -"can't be accessed in the UI (see instructions below)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_at}``" msgstr "" -#: ../settings/system/storage.rst:44 -msgid "" -"⚠️ Please note that the current implementation is in its early stages and can " -"be modified in the future." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Address" msgstr "" -#: ../settings/system/storage.rst:47 -msgid "" -"The prerequisite is to have access to a S3-compatible storage and to have " -"all necessary parameters available (which depends on your storage provider; " -"if in doubt, please ask there for help)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.address}``" msgstr "" -#: ../settings/system/storage.rst:51 -msgid "Steps to configure S3:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Avatar" msgstr "" -#: ../settings/system/storage.rst:53 -msgid "" -"Copy ``config/zammad/storage.yml.dist`` to ``config/zammad/storage.yml``" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.avatar(60,60)}``" msgstr "" -#: ../settings/system/storage.rst:54 -msgid "Edit the copied file in one of the following ways:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Department" msgstr "" -#: ../settings/system/storage.rst:56 -msgid "" -"Either provide your S3 configuration with one attribute per line like in the " -"upper area of the file" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.department}``" msgstr "" -#: ../settings/system/storage.rst:58 -msgid "" -"Or provide your S3 configuration as an URL (which you can find at the end of " -"the file). Note: you can also provide this URL as environment variable (:" -"docs:`see system documentation `) without using this yml-file." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Email" msgstr "" -#: ../settings/system/storage.rst:62 -msgid "" -"We recommend the deletion of the not used configuration style to avoid " -"inconsistencies." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.email}``" msgstr "" -#: ../settings/system/storage.rst:65 -msgid "Restart Zammad so the config file / environment variable is loaded" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Fax" msgstr "" -#: ../settings/system/storage.rst:66 -msgid "" -"Set the \"Storage Method\" in Zammad to ``Simple Storage (S3)`` in Settings " -"> System > Storage and click on \"Submit\". After that, Zammad checks your " -"configuration and the connection to the service and will raise an error " -"message if something is wrong." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.fax}``" msgstr "" -#: ../settings/system/storage.rst:72 -msgid "A very simple storage configuration could look like this:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Firstname" msgstr "" -#: ../settings/system/storage.rst:85 -msgid "" -"Before setting the storage method to ``Simple Storage (S3)`` (step 4), " -"please make sure to have a working setup." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.firstname}``" msgstr "" -#: ../settings/system/storage.rst:88 -msgid "" -"You can verify this by running ``rails r 'Rails.logger = Logger.new(STDOUT); " -"pp Store::Provider::S3.ping?'`` in your Zammad directory. If everything is " -"fine, you should see ``true``, else you should see ``false`` and a simple " -"error message." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Lastname" msgstr "" -#: ../settings/system/storage.rst:93 -msgid "" -"If you installed Zammad through a package manager (rather than from source), " -"replace ``rails r`` with ``zammad run rails r`` above. To learn more, see :" -"docs:`Administration via Console `." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.lastname}``" msgstr "" -#: ../settings/ticket.rst:4 -msgid "" -"Here you can adjust general ticket settings. Additional ones for the ticket " -"composer interface can be found in the :doc:`/misc/composer`." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Login" msgstr "" -#: ../settings/ticket.rst:11 -msgid "Ticket Hook (default: ``Ticket#``)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.login}``" msgstr "" -#: ../settings/ticket.rst:11 -msgid "The identifier for a ticket; *e.g.,* Ticket#, Call#, MyTicket#." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Mobile" msgstr "" -#: ../settings/ticket.rst:38 -msgid "Ticket Hook Position (default: ``right``)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.mobile}``" msgstr "" -#: ../settings/ticket.rst:14 -msgid "" -"With this setting you can decide (if) where to insert the ticket number." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Note" msgstr "" -#: ../settings/ticket.rst:20 -msgid "*Right*" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.note}``" msgstr "" -#: ../settings/ticket.rst:17 -msgid "" -"This setting will add the ticket reference on the right site of the subject." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Phone" msgstr "" -#: ../settings/ticket.rst:20 -msgid "Example: ``Some Subject [Ticket#12345]``" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.phone}``" msgstr "" -#: ../settings/ticket.rst:26 -msgid "*Left*" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > VIP" msgstr "" -#: ../settings/ticket.rst:23 -msgid "" -"This setting will add the ticket reference on the left site of the subject." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.vip}``" msgstr "" -#: ../settings/ticket.rst:26 -msgid "Example: ``[Ticket#12345] Some Subject``" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Web" msgstr "" -#: ../settings/ticket.rst:29 -msgid "*None*" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.web}``" msgstr "" -#: ../settings/ticket.rst:29 -msgid "This will completely remove ticket references from the subject." +#: ../settings/branding.rst:10 +msgid "Product Name" msgstr "" -#: ../settings/ticket.rst:33 +#: ../settings/branding.rst:7 msgid "" -"Please ensure to take a look at :doc:`/channels/email/settings` within the " -"email channel to ensure you have at least one reference that helps Zammad to " -"assign follow-ups correctly." +"Defines the name of the application, shown in the web interface, tabs and " +"title bar of the web browser." msgstr "" -#: ../settings/ticket.rst:37 -msgid "" -"Disabling this and not setting up any further follow up search will lead to " -"unexpected results!" +#: ../settings/branding.rst:10 +msgid "Default value: ``Zammad Helpdesk``" msgstr "" -#: ../settings/ticket.rst:65 -msgid "" -"Ticket Last Contact Behaviour (default: ``Use the start time of the last " -"customer thread (which may consist of multiple articles).``)" +#: ../settings/branding.rst:13 +msgid "Will be shown in the app and is included in email footers." msgstr "" -#: ../settings/ticket.rst:41 -msgid "" -"This setting changes the way Zammad updates the ``Last Contact`` value of a " -"ticket. This is fairly important for overviews and what you expect upon " -"ticket updates of a customer." +#: ../settings/branding.rst:19 +msgid "Logo" msgstr "" -#: ../settings/ticket.rst:52 -msgid "" -"Use the start time of the last customer thread (which may consist of " -"multiple articles)." +#: ../settings/branding.rst:16 +msgid "Defines the logo of the application, shown in the login page of Zammad." msgstr "" -#: ../settings/ticket.rst:46 +#: ../settings/branding.rst:18 msgid "" -"If this option is chosen, Zammad will update the last updated value just " -"once if a customer replies. After that, Zammad will wait for an agent to " -"react." +"Ensure to hit the \"Submit\" button after uploading the logo. Otherwise your " +"change will not be saved." msgstr "" -#: ../settings/ticket.rst:50 +#: ../settings/branding.rst:22 msgid "" -"This comes in handy if you want to work tickets in the order of their first " -"update. This will not change ticket orders if customers decide to \"bump\" " -"the ticket affected." +"Allows to set the default language of the Zammad instance. The here defined " +"locale mostly acts as a fallback for:" msgstr "" -#: ../settings/ticket.rst:57 -msgid "Use the time of the very last customer article." +#: ../settings/branding.rst:25 +msgid "user preferences (if Zammad can't detect the users locale)" msgstr "" -#: ../settings/ticket.rst:55 -msgid "" -"When setting this option, Zammad will always update the last updated value. " -"This means that if ordering by ``Last Update``, ticket orders will change if " -"customers \"bump\" the ticket." +#: ../settings/branding.rst:26 +msgid "CSV output (reporting, time accounting)" msgstr "" -#: ../settings/ticket.rst:64 -msgid "Last contact value used on :doc:`/manage/overviews`" +#: ../settings/branding.rst:30 +msgid "Define the timezone of your Zammad installation." msgstr "" -#: ../settings/ticket.rst:65 -msgid "Last contact value used on :doc:`/manage/trigger`" +#: ../settings/branding.rst:32 +msgid "" +"This does not have any effect on timings for your agents or how Zammad " +"stores date and time values." msgstr "" -#: ../settings/ticket.rst:88 -msgid "" -"Ticket Organization Reassignment (default: ``Update the most recent tickets." -"``)" +#: ../settings/branding.rst:35 +msgid "Changing this value has direct consequences on the following areas:" msgstr "" -#: ../settings/ticket.rst:68 -msgid "" -"This setting changes the way Zammad updates the organization field of the " -"tickets whenever the primary organization of a user is changed." +#: ../settings/branding.rst:37 +msgid ":doc:`/manage/scheduler` tasks" msgstr "" -#: ../settings/ticket.rst:74 -msgid "Update the most recent tickets." +#: ../settings/branding.rst:38 +msgid "search indexing (and thus reporting)" msgstr "" -#: ../settings/ticket.rst:72 -msgid "" -"If this option is chosen, Zammad will update the 100 most recent tickets " -"where the user is the ticket customer. The ticket organization field will be " -"automatically set to the new primary organization of the user." +#: ../settings/branding.rst:40 +msgid "calendar subscriptions" msgstr "" -#: ../settings/ticket.rst:88 -msgid "Do not update any tickets." +#: ../settings/branding.rst:41 +msgid "browser printing" msgstr "" -#: ../settings/ticket.rst:77 +#: ../settings/branding.rst:43 msgid "" -"When choosing this option, Zammad will not update any tickets when the " -"user's primary organization is changed." +"Please note that some of above are fallbacks in case Zammad could not detect " +"the agents timezone correctly." msgstr "" -#: ../settings/ticket.rst:80 -msgid "**Use with care!**" +#: ../settings/branding.rst:77 +msgid "Pretty Date" msgstr "" -#: ../settings/ticket.rst:82 +#: ../settings/branding.rst:47 msgid "" -"Using this option may lead to inconsistencies in the system as the ticket " -"organization may become decoupled from the ticket customer." +"This setting allows you to define how Zammad should display time stamps " +"within the interface to all users." msgstr "" -#: ../settings/ticket.rst:85 +#: ../settings/branding.rst:50 msgid "" -"However, you may use this option if you wish to maintain :ref:`the shared " -"access ` to the ticket for all organization " -"members of the original organization of the customer." +"This does not have any effect on how Zammad returns e.g. time values via " +"variables." msgstr "" -#: ../settings/ticket.rst:110 -msgid "Ticket Number Format (default: ``Increment (SystemID.Counter)``)" +#: ../settings/branding.rst:77 +msgid "Choose in between the following options:" msgstr "" -#: ../settings/ticket.rst:94 -msgid "" -"This setting defines the way Zammad's ticket number will look. Changing this " -"setting in production will cause follow up detection to fail." +#: ../settings/branding.rst:64 +msgid "relative" msgstr "" -#: ../settings/ticket.rst:102 -msgid "Increment (SystemID.Counter)" +#: ../settings/branding.rst:55 +msgid "" +"This timestamp shows a relative time span until it switches to a date. Over " +"time, it will change as follows:" msgstr "" -#: ../settings/ticket.rst:98 -msgid "" -"The increment value contains the SystemID (automatically generated during " -"installation) and a increment which counts up with every new Ticket. The " -"increment will automatically get another digit if needed." +#: ../settings/branding.rst:58 +msgid "just now" msgstr "" -#: ../settings/ticket.rst:102 -msgid "Examples: ``1010138``, ``1010139``" +#: ../settings/branding.rst:59 +msgid "5 minutes ago" msgstr "" -#: ../settings/ticket.rst:110 -msgid "Date (Year.Month.Day.SystemID.Counter)" +#: ../settings/branding.rst:60 +msgid "3 days 1 hour ago" msgstr "" -#: ../settings/ticket.rst:105 -msgid "" -"This version of the ticket number is fairly long. However, because it " -"contains the date of ticket creation, it also allows you to see when the " -"ticket has been created. You may feel familiar with this number format if " -"you've worked with OTRS already." +#: ../settings/branding.rst:61 +msgid "``03/04/2022``" msgstr "" -#: ../settings/ticket.rst:110 -msgid "Examples: ``201206231010138``, ``201206231010139``" +#: ../settings/branding.rst:63 +msgid "Hovering the timestamp helps, you'll always get a clean timestamp then." msgstr "" -#: ../settings/ticket.rst:137 -msgid "OPTIONS" +#: ../settings/branding.rst:71 +msgid "absolute" msgstr "" -#: ../settings/ticket.rst:113 +#: ../settings/branding.rst:67 msgid "" -"The below options allow you to further customize your ticket number. The " -"availability of options differ depending of the chosen ticket number format " -"above." +"This timestamp always includes the week day. For one week after creation, " +"the timestamp will not contain the date itself: Thursday 18:35." msgstr "" -#: ../settings/ticket.rst:122 -msgid "Checksum (default: ``no``)" +#: ../settings/branding.rst:71 +msgid "After a week it will switch to: ``Friday 4. Mar 16:00``." msgstr "" -#: ../settings/ticket.rst:118 -msgid "" -"If set to yes, we'll built a checksum to further \"unique\" the ticket " -"number of your system. If you're dealing with many other ticket systems this " -"might help to prevent false positive follow up detection on tickets." +#: ../settings/branding.rst:76 +msgid "timestamp" msgstr "" -#: ../settings/ticket.rst:122 -msgid "This will also add another digit to the ticket number." +#: ../settings/branding.rst:74 +msgid "" +"This will cause Zammad to show a complete timestamp according to your locale " +"defaults. For English this could be e.g. ``2022/12/03 2:40 pm`` or for " +"German e.g. ``12.03.2022 14:40``." msgstr "" -#: ../settings/ticket.rst:137 -msgid "Min. size of Number (default: ``5``)" +#: ../settings/branding.rst:78 +msgid "Default setting: ``relative``." msgstr "" -#: ../settings/ticket.rst:125 -msgid "" -"This setting defines the minimum length of your ticket number. If your " -"counter is not yet high enough, Zammad will fill the number with zeros to " -"ensure the wanted length." +#: ../settings/security.rst:2 +msgid "Security" msgstr "" -#: ../settings/ticket.rst:129 +#: ../settings/security.rst:4 msgid "" -"Please note that the minimum length is ``3`` (SystemID + at least one digit " -"if below 10). Also, if the length is no longer long enough, the number will " -"automatically get one digit longer. Ticket-Numbers **do not overflow**, thus " -"it's save to keep it at 5 or set it lower if wanted." +"For your overview we split each tab within security settings into its own " +"page:" msgstr "" -#: ../settings/ticket.rst:135 -msgid "" -"This option is only available if ticket number format is set to " -"``Increment``!" +#: ../settings/security/base.rst:2 ../settings/system/base.rst:2 +#: ../settings/ticket.rst:8 +msgid "Base" msgstr "" -#: ../settings/ticket.rst:142 -msgid "Auto-Assignment" +#: ../settings/security/base.rst:5 +msgid "New User Accounts" msgstr "" -#: ../settings/ticket.rst:144 +#: ../settings/security/base.rst:9 msgid "" -"In a larger Zammad environment, it happens that several agents open the same " -"ticket at the same time. Although collision detection is then effective, the " -"efficiency of processing can be increased by means of the automatic " -"assignment of tickets when a ticket is opened." +"Activates the `register as a new customer` function on the login page. If " +"set to ``no`` only administrators or agents can create new accounts manually." msgstr "" -#: ../settings/ticket.rst:149 -msgid "" -"The automatic assignment of tickets can be activated and configured in the " -"admin area under Settings > Ticket > Auto Assignment." +#: ../settings/security/base.rst:13 ../settings/security/base.rst:38 +#: ../settings/security/base.rst:66 +msgid "Default setting: ``yes``" msgstr "" -#: ../settings/ticket.rst:152 -msgid "" -"The auto assignment only works if the ticket has no owner yet. By default, " -"the agent can always reset the ticket owner to ``-`` if needed." +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"New User Accounts\" setting" msgstr "" -#: ../settings/ticket.rst:155 +#: ../settings/security/base.rst:22 msgid "" -"If you want to use this function for only specific tickets, you can " -"configure the conditions accordingly to meet your requirement. By default " -"the condition affects all tickets with the state ``open``." +"Deactivation of above function **does not** deactivate automatic account " +"creation! This means: If a user writes e.g. an email to Zammad and has no " +"account yet, Zammad will automatically create the account. User accounts are " +"a direct dependency of tickets and thus technically mandatory." msgstr "" -#: ../settings/ticket.rst:161 -msgid "" -"If you need to exclude users (e.g. a group leader), you can search and " -"select the desired agents in the ``Exception Users`` list. The search " -"function in this area is only effective, if you have too many agents to " -"display at once to help you with the configuration." +#: ../settings/security/base.rst:29 +msgid "Lost Password" msgstr "" -#: ../settings/ticket.rst:167 -#, fuzzy -msgid "Notifications" -msgstr "Intégrations" - -#: ../settings/ticket.rst:191 -#, fuzzy -msgid "Default Notifications" -msgstr "Intégrations" - -#: ../settings/ticket.rst:170 +#: ../settings/security/base.rst:33 msgid "" -"This setting allows you to configure the default ticket notifications that " -"will be applied to all new agent users (incl. users who were just assigned " -"agent role). Simply change the notification matrix to desired state and " -"press **Save**." +"Activates the `lost password` function on the login page. If set to ``no`` " +"only administrators may change the user's password - users may update their " +"own password if they're still logged in and they have the required :doc:" +"`permission `." msgstr "" -#: ../settings/ticket.rst:175 -msgid "" -"In case an agent already exists, their ticket notification preferences will " -"be preserved. Optionally, you can also **Apply current defaults to all " -"agents**." +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"Lost Password\" setting" msgstr "" -#: ../settings/ticket.rst:181 +#: ../settings/security/base.rst:49 msgid "" -"**Potential time-consuming action:** Applying default ticket notifications " -"to all agent users may take some time to complete, be patient! The exact " -"time will depend on the size of your system and the number of agents." +"With third party authentications - but especially LDAP - you may want to " +"disable this function. Zammad **will not** change third party login " +"passwords and instead set or change the local password!" msgstr "" -#: ../settings/ticket.rst:185 -msgid "" -"**Active agents only!** When current default ticket notifications are " -"applied, only active agent users are considered. In case an agent is re-" -"activated *after* this action, they will still have the old notification " -"configuration." +#: ../settings/security/base.rst:56 +msgid "Password Login" msgstr "" -#: ../settings/ticket.rst:190 +#: ../settings/security/base.rst:60 msgid "" -"In case you want to go back to the initial state of ticket notifications, " -"you can click on **Reset to default** button." +"Activates the username & password login by default and if no third-party " +"login is activated. Disabling password login on the Zammad login page only " +"takes effect if you enable any :doc:`third-party`." msgstr "" -#: ../settings/ticket.rst:194 ../settings/ticket.rst:196 -msgid "Duplicate Detection" +#: ../settings/security/base.rst:64 +msgid "See :doc:`third-party` for supported third-party logins." msgstr "" -#: ../settings/ticket.rst:236 ../settings/ticket.rst:238 -msgid "Detect Duplicate Ticket Creation" +#: ../settings/security/base.rst:0 +msgid "Figure showing de-activated \"Password Login\" setting" msgstr "" -#: ../settings/ticket.rst:197 ../settings/ticket.rst:199 +#: ../settings/security/base.rst:77 msgid "" -"This setting turns on the duplicate ticket detection mechanism during ticket " -"creation. If similar tickets are found in the system, a suitable warning " -"will be shown to the user trying to create a ticket." +"To help administrators to overcome \"login issues\", Zammad automatically " +"offers a password request for administrator users. This allows you to adjust " +"Third-Party applications even if the login does no longer work!" msgstr "" -#: ../settings/ticket.rst:204 ../settings/ticket.rst:206 -msgid "A Sample Duplicate Ticket Warning" +#: ../settings/security/base.rst:84 +msgid "Session Timeout" msgstr "" -#: ../settings/ticket.rst:206 ../settings/ticket.rst:208 +#: ../settings/security/base.rst:86 msgid "" -"You can choose which ticket attributes will be matched by selecting them in " -"**Attributes to compare** field. Only if the ticket attribute value provided " -"by the user in the ticket create form is *equal* with the attribute in an " -"existing ticket, the warning will be shown." -msgstr "" - -#: ../settings/ticket.rst:211 ../settings/ticket.rst:213 -msgid "**Warning title** and **Warning message** are configurable as well." +"All settings below by default are set to ``4 weeks``. Session Timeout " +"defines the life time of a users session. As soon as it's reached, Zammad " +"will automatically log off the session in question." msgstr "" -#: ../settings/ticket.rst:213 ../settings/ticket.rst:215 +#: ../settings/security/base.rst:91 msgid "" -"You can limit the detection only to certain user roles. By default, only " -"agents will see the warning." +"Zammad takes the highest value set assigned for the user based on the " +"permissions." msgstr "" -#: ../settings/ticket.rst:216 ../settings/ticket.rst:218 -msgid "" -"If you don't want to show the matched tickets as part of the warning, you " -"can set **Show matching ticket(s) in the warning** setting to *no*." +#: ../settings/security/base.rst:94 +msgid "``admin``" msgstr "" -#: ../settings/ticket.rst:219 ../settings/ticket.rst:221 -msgid "" -"By default, **Permission level for looking up ticket** is set to *User*, " -"which means user permissions will be honored during sarch. The user will " -"see the warning only if tickets they have access to are matched. " -"Alternatively, you can set this setting to *System*, in which case the " -"search will happen within *all* tickets in the system, regardless of user " -"permissions." +#: ../settings/security/base.rst:96 +msgid "``ticket.customer``" msgstr "" -#: ../settings/ticket.rst:225 ../settings/ticket.rst:227 -msgid "**🦺 Safety first!**" +#: ../settings/security/base.rst:97 +msgid "``default`` (fallback if user doesn't have above permissions set)" msgstr "" -#: ../settings/ticket.rst:227 ../settings/ticket.rst:229 +#: ../settings/security/base.rst:99 msgid "" -"Even if the permission level is set to *System*, the user will not be shown " -"the tickets they don't have access to in the warning, even if they match." +"All settings act independently from each other allowing you to disable the " +"timeouts for e.g. admins, but not agents." msgstr "" -#: ../settings/ticket.rst:231 ../settings/ticket.rst:233 -msgid "" -"However, just the confirmation about the existence of the tickets in the " -"system may be considered an unwanted information disclosure. Use this option " -"carefully!" +#: ../settings/security/base.rst:115 +#: ../system/integrations/checkmk/api-reference.rst:13 +msgid "Example" msgstr "" -#: ../settings/ticket.rst:235 ../settings/ticket.rst:237 -msgid "" -"Finally, you can configure between matching within **All tickets** or **Open " -"tickets** only by setting **Match tickets in following states**. Depending " -"on the current ticket state, a ticket may or not be matched." +#: ../settings/security/base.rst:107 +msgid "Let's suppose you configured the following session timeouts" msgstr "" -#: ../system/core-workflows.rst:2 -msgid "Core Workflows" -msgstr "Flux de travail principaux" - -#: ../system/core-workflows.rst:4 -msgid "" -"Core Workflows allow you to adjust object attributes in many ways. For " -"example:" +#: ../settings/security/base.rst:104 +msgid "default: 3 weeks" msgstr "" -#: ../system/core-workflows.rst:7 -msgid "show / hide fields" +#: ../settings/security/base.rst:105 +msgid "admin: 2 weeks" msgstr "" -#: ../system/core-workflows.rst:8 -msgid "adjust mandatory setting" +#: ../settings/security/base.rst:106 +msgid "ticket.agent: 4 weeks" msgstr "" -#: ../system/core-workflows.rst:9 -msgid "manipulate available options" +#: ../settings/security/base.rst:107 +msgid "ticket.customer: 1 week" msgstr "" -#: ../system/core-workflows.rst:11 -msgid "" -"With this, you can provide exactly the information your users really need!" +#: ../settings/security/base.rst:115 +msgid "This results in the following situations" msgstr "" -#: ../system/core-workflows.rst:15 -msgid "" -"If the pre-defined :doc:`/system/objects` are not enough, please add them " -"beforehand." +#: ../settings/security/base.rst:110 +msgid "a user with ``admin`` permission will have a timeout of 2 weeks" msgstr "" -#: ../system/core-workflows.rst:17 +#: ../settings/security/base.rst:111 msgid "" -"If you experience slow or unreliable field updates, please see :ref:`Core " -"Workflow Ajax Modus `" +"a user with ``admin`` and ``ticket.agent`` permissions will have a timeout " +"of 2 weeks" msgstr "" -#: ../system/core-workflows.rst:22 +#: ../settings/security/base.rst:113 msgid "" -"This is a very enhanced functionality and can cause unexpected UI behavior. " -"Please ensure to test your use cases after configuration to reduce surprises." +"a user with ``ticket.customer`` permission will have a timeout of 1 week" msgstr "" -#: ../system/core-workflows.rst:None -msgid "Dialogue for adding a new workflow" +#: ../settings/security/base.rst:115 +msgid "" +"a user with neither ``admin``, ``ticket.agent`` nor ``ticket.customer`` " +"permissions will have a timeout of 3 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:2 -msgid "Core Workflow Condition Operators" +#: ../settings/security/password.rst:4 +msgid "" +"This section allows you to define password requirements for the local user " +"accounts." msgstr "" -#: ../system/core-workflows/condition-operators.rst:4 +#: ../settings/security/password.rst:9 msgid "" -"You might know that there is a separate section for explaining :doc:" -"`condition operators `. Head over there to " -"see a detailed explanation of many conditions and operators." +"Zammad does **not** allow you to change your LDAP password, instead, it will " +"set a password in its local database which might confuse your users. This " +"might be addressed in the future by `#1169 `_." msgstr "" -#: ../system/core-workflows/condition-operators.rst:8 -msgid "" -"Due to differences to other places in Zammad which are also using conditions " -"(e.g. triggers), you can find a dedicated description of operators for core " -"workflows below." +#: ../settings/security/password.rst:14 +msgid "**Exception for admins**" msgstr "" -#: ../system/core-workflows/condition-operators.rst:12 +#: ../settings/security/password.rst:16 msgid "" -"Be aware that the availability of the operators depends on the selected " -"attribute and its field type. Some of the operators may only be available " -"for system attributes (e.g. for \"tags\", \"active\")." +"Please note that below password policies *do not* affect administrators " +"setting passwords on user accounts. While this seems strange and not safe we " +"believe that an administrator knowing an user's password is insecure as well." msgstr "" -#: ../system/core-workflows/condition-operators.rst:20 -msgid "Operator" +#: ../settings/security/password.rst:21 +msgid "The suggested workflow is either:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:22 -msgid "after (absolute)" +#: ../settings/security/password.rst:23 +msgid "" +"to use third party logins to not require local passwords at all **- or -**" msgstr "" -#: ../system/core-workflows/condition-operators.rst:23 -msgid "Matches if a date/time is after a specific point in time." +#: ../settings/security/password.rst:25 +msgid "to require your *user to reset the password* upon first login." msgstr "" -#: ../system/core-workflows/condition-operators.rst:24 -msgid "after (relative)" +#: ../settings/security/password.rst:27 +msgid "" +"This way administrators are not required to set a user's password at all!" msgstr "" -#: ../system/core-workflows/condition-operators.rst:25 -msgid "Matches if a time span after a specified event has passed." +#: ../settings/security/password.rst:31 +msgid "Maximum Failed Logins" msgstr "" -#: ../system/core-workflows/condition-operators.rst:26 -msgid "before (absolute)" +#: ../settings/security/password.rst:33 +msgid "" +"You can choose a value between ``4`` and ``20``. This defines how often a " +"login to a user account may fail until Zammad will lock it. Your users can " +"always use the \"forgot password\" function to change their password and " +"unlock their account." msgstr "" -#: ../system/core-workflows/condition-operators.rst:27 -msgid "Matches if a date/time is before a specific point in time." +#: ../settings/security/password.rst:38 +msgid "The default value is ``10``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:28 -msgid "before (relative)" +#: ../settings/security/password.rst:42 +msgid "Beside changing the user's password, you can also unlock accounts via" msgstr "" -#: ../system/core-workflows/condition-operators.rst:29 -msgid "Matches if a time span after a specified event has not passed." +#: ../settings/security/password.rst:44 +msgid ":ref:`user management list `" msgstr "" -#: ../system/core-workflows/condition-operators.rst:30 -msgid "contains" +#: ../settings/security/password.rst:45 +msgid ":docs:`console `" msgstr "" -#: ../system/core-workflows/condition-operators.rst:31 -msgid "Matches if a specified value is present." +#: ../settings/security/password.rst:46 +msgid ":docs:`API `" msgstr "" -#: ../system/core-workflows/condition-operators.rst:33 -msgid "Matches if all of the specified values are present." +#: ../settings/security/password.rst:50 +msgid "Failed logins via LDAP no longer lock accounts." msgstr "" -#: ../system/core-workflows/condition-operators.rst:35 -msgid "Matches if none of the specified values are present." +#: ../settings/security/password.rst:53 +msgid "2 Lower Case And 2 Upper Case Characters" msgstr "" -#: ../system/core-workflows/condition-operators.rst:36 -msgid "contains not" +#: ../settings/security/password.rst:55 +msgid "" +"You can add complexity to passwords by enforcing at least 2 upper and lower " +"case characters." msgstr "" -#: ../system/core-workflows/condition-operators.rst:37 -msgid "Matches if a specified value is not present." +#: ../settings/security/password.rst:58 ../settings/security/password.rst:83 +msgid "The default value is ``no``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:39 -msgid "Matches if one specified value is present." +#: ../settings/security/password.rst:62 +msgid "Minimum Length" msgstr "" -#: ../system/core-workflows/condition-operators.rst:41 -msgid "Matches if one specified value is not present." +#: ../settings/security/password.rst:64 +msgid "" +"This defines the minimum password length required for users to provide (from " +"``4`` to ``20``)." msgstr "" -#: ../system/core-workflows/condition-operators.rst:42 -msgid "does not match regex" +#: ../settings/security/password.rst:67 +msgid "The default value is ``6``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:43 -msgid "Matches if content doesn't fit to regex rule." +#: ../settings/security/password.rst:71 +msgid "Digit Required" msgstr "" -#: ../system/core-workflows/condition-operators.rst:44 -msgid "ends with" +#: ../settings/security/password.rst:73 +msgid "This enforces your users to use at least one digit within the password." msgstr "" -#: ../system/core-workflows/condition-operators.rst:45 -msgid "Matches if content ends with specified value." +#: ../settings/security/password.rst:75 +msgid "The default value is ``yes``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:46 -msgid "ends with one of" +#: ../settings/security/password.rst:78 +msgid "Special Character Required" msgstr "" -#: ../system/core-workflows/condition-operators.rst:47 -msgid "Matches if content ends with one of the specified values." +#: ../settings/security/password.rst:80 +msgid "" +"This setting allows you to improve your password quality even more by " +"enforcing the password to contain at least one special character." msgstr "" -#: ../system/core-workflows/condition-operators.rst:48 -msgid "from (relative)" +#: ../settings/security/ssl-certificates.rst:2 +msgid "SSL Certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:49 -msgid "Matches if date/time is after a period of time after an event." +#: ../settings/security/ssl-certificates.rst:7 +msgid "" +"Zammad offers the possibility to upload custom certificates and custom " +"Certificate Authority (CA) certificates. This can be useful if you want to " +"connect Zammad the secure way to other systems which are using custom " +"certificates." msgstr "" -#: ../system/core-workflows/condition-operators.rst:51 -msgid "Matches if content is equal to a specified value." -msgstr "" - -#: ../system/core-workflows/condition-operators.rst:52 -msgid "is any of" +#: ../settings/security/ssl-certificates.rst:12 +msgid "" +"An example usecase might be: You have an internal LDAP server that is not " +"accessible from the internet, and you want a SSL-encrypted connection, using " +"a custom certificate." msgstr "" -#: ../system/core-workflows/condition-operators.rst:53 -msgid "Matches if content is equal to any of specified values." +#: ../settings/security/ssl-certificates.rst:19 +msgid "" +"You should have an existing custom certificate file and/or a custom CA " +"certificate file, which you want to add to Zammad. As filetype ``.crt`` is " +"supported and the certificate format has to be PEM (Base64 ASCII)." msgstr "" -#: ../system/core-workflows/condition-operators.rst:54 -msgid "is modified" +#: ../settings/security/ssl-certificates.rst:25 +msgid "" +"When you import a custom CA certificate, all certificates generated with " +"this are trusted. This can be useful if you have more than one system/" +"certificate you want to connect to and the certificates are issued from the " +"same custom CA." msgstr "" -#: ../system/core-workflows/condition-operators.rst:55 -msgid "Matches if content is modified." +#: ../settings/security/ssl-certificates.rst:31 +msgid "Add a Certificate" msgstr "" -#: ../system/core-workflows/condition-operators.rst:57 -#: ../system/core-workflows/condition-operators.rst:61 -msgid "True from the moment of changing content until form submit." +#: ../settings/security/ssl-certificates.rst:33 +msgid "" +"To add a custom certificate or a custom CA certificate, head over to the " +"Admin panel > Settings > Security > SSL Certificates. Here you can find a " +"\"Add SSL Certificate\" button. In the dialog you can either select a " +"certificate file or paste the content of the certificate:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:58 -msgid "is modified to" +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate adding dialog" msgstr "" -#: ../system/core-workflows/condition-operators.rst:59 -msgid "Matches if content is modified to a specific value." +#: ../settings/security/ssl-certificates.rst:43 +msgid "" +"After selecting a file or pasting the content of the certificate, click on " +"the \"Add\" button to finally upload it to Zammad. Then, the certificates " +"are immediately effective, no restart or similar required." msgstr "" -#: ../system/core-workflows/condition-operators.rst:62 -msgid "is none of" +#: ../settings/security/ssl-certificates.rst:49 +msgid "" +"Please note that only single certificate files are supported. That means if " +"you want to import a certificate / CA certificate, it must contain **only " +"one** certificate." msgstr "" -#: ../system/core-workflows/condition-operators.rst:63 -msgid "Matches if content is none of any specified values." +#: ../settings/security/ssl-certificates.rst:54 +msgid "Certificate Overview" msgstr "" -#: ../system/core-workflows/condition-operators.rst:65 -msgid "Matches if content is not equal to a specified value." +#: ../settings/security/ssl-certificates.rst:56 +msgid "" +"After you added a certificate, you can see a table with information for each " +"added certificate:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:67 -msgid "Matches if content is present." +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing table of added certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:68 -msgid "just changed" +#: ../settings/security/ssl-certificates.rst:64 +msgid "" +"Here you can download the certificate or delete it, if you don't need it " +"anymore." msgstr "" -#: ../system/core-workflows/condition-operators.rst:69 -msgid "Matches if content has changed." -msgstr "" +#: ../settings/security/ssl-certificates.rst:68 +#, fuzzy +msgid "Deleting Certificates" +msgstr "Intégrations" -#: ../system/core-workflows/condition-operators.rst:71 -#: ../system/core-workflows/condition-operators.rst:75 +#: ../settings/security/ssl-certificates.rst:70 msgid "" -"Only true for the moment of changing content until next form field action/" -"click." +"If you want to delete a specific certificate, you can do it by clicking on " +"the menu in the actions column and selecting delete:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:72 -msgid "just changed to" +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate deletion button" msgstr "" -#: ../system/core-workflows/condition-operators.rst:73 -msgid "Matches if content has changed to a specified value." +#: ../settings/security/ssl-certificates.rst:79 +msgid "Downloading Certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:76 -msgid "matches regex" +#: ../settings/security/ssl-certificates.rst:81 +msgid "" +"If you want to download your certificates, you can do this as well via " +"corresponding action buttons." msgstr "" -#: ../system/core-workflows/condition-operators.rst:77 -msgid "Matches if value fits to regex rule." +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate download button" msgstr "" -#: ../system/core-workflows/condition-operators.rst:79 -msgid "Matches if no content is present." +#: ../settings/security/third-party.rst:13 +msgid "Login Providers" msgstr "" -#: ../system/core-workflows/condition-operators.rst:80 -msgid "starts with" +#: ../settings/security/third-party.rst:2 +msgid "Third-Party Applications" msgstr "" -#: ../system/core-workflows/condition-operators.rst:81 -msgid "Matches if content starts with specified value." +#: ../settings/security/third-party.rst:4 +msgid "" +"Third party authentication is a great way to help your users to login to " +"Zammad more easily. If the account is yet unknown, Zammad will create a new " +"user automatically, without the user needed to interact (e.g. type in his " +"name). Another big advantage of this feature is that your user doesn't need " +"to remember another password." msgstr "" -#: ../system/core-workflows/condition-operators.rst:82 -msgid "starts with one of" +#: ../settings/security/third-party.rst:10 +msgid "" +"You can deactivate logging in via :ref:`security_password_login` if any of " +"the mentioned authentication providers are enabled in your instance." msgstr "" -#: ../system/core-workflows/condition-operators.rst:83 -msgid "Matches if content starts with one of the specified values." +#: ../settings/security/third-party.rst:27 +msgid "" +"We're currently missing documentation for the following login providers:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:84 -msgid "till (relative)" +#: ../settings/security/third-party.rst:29 +msgid "LinkedIn" msgstr "" -#: ../system/core-workflows/condition-operators.rst:85 -msgid "Matches if date/time is before a period of time before an event." +#: ../settings/security/third-party.rst:30 +msgid "Weibo" msgstr "" -#: ../system/core-workflows/condition-operators.rst:86 -msgid "today" -msgstr "" +#: ../settings/security/third-party.rst:35 +#, fuzzy +msgid "Automatic Account Link on Initial Logon" +msgstr "Notification de liaison automatique de compte" -#: ../system/core-workflows/condition-operators.rst:87 -msgid "Matches if date/time is today." +#: ../settings/security/third-party.rst:37 +msgid "" +"In general there's two possible options for Zammad on how to deal with " +"already known users as they try to authenticate against a third-party " +"application. By default, Zammad will not automatically link \"unknown\" " +"authentication providers to existing accounts." msgstr "" -#: ../system/core-workflows/condition-operators.rst:88 -msgid "within last (relative)" +#: ../settings/security/third-party.rst:42 +msgid "" +"This means that the user has to manually link authentication providers to " +"their accounts (for more about this :user-docs:`consult the user " +"documentation `)." msgstr "" -#: ../system/core-workflows/condition-operators.rst:89 +#: ../settings/security/third-party.rst:46 msgid "" -"Matches if date/time content is within specified period of time before now." +"Sometimes this doesn't come in handy as this also means you'll receive error " +"messages about \"email address being in use already\" for (yet) unknown " +"third-party authentication methods." msgstr "" -#: ../system/core-workflows/condition-operators.rst:91 -msgid "within next (relative)" +#: ../settings/security/third-party.rst:50 +msgid "" +"If you want to allow your users to always be able to log in, no matter what, " +"you may want to enable ``Automatic account link on initial logon``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:92 +#: ../settings/security/third-party.rst:None msgid "" -"Matches if date/time content is within specified period of time after now." +"Screenshot highlighting the \"Automatic account link on initial logon\"\n" +"setting" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:2 -msgid "How do they work?" -msgstr "" +#: ../settings/security/third-party.rst:60 +#, fuzzy +msgid "Automatic Account Linking Notification" +msgstr "Notification de liaison automatique de compte" -#: ../system/core-workflows/how-do-they-work.rst:4 +#: ../settings/security/third-party.rst:64 msgid "" -"Core Workflows are executed according to their priority. If two workflows " -"have the same priority, they are executed in alphabetical order based on " -"their **name**." +"To improve security and your users awareness, you can enable Zammad to " +"notify your users when a new third-party application has been linked to " +"their account." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:8 +#: ../settings/security/third-party.rst:68 msgid "" -"Because of the way Core Workflows work, all changes to attributes are " -"checked with the application server - please see :doc:`limitations` for " -"possible issues." +"This notification is sent out once per third-party application. Zammad does " +"also mention the method used, e.g.: ``Microsoft``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:12 +#: ../settings/security/third-party.rst:71 +msgid "By default this setting is not active (set to ``no``)." +msgstr "" + +#: ../settings/security/third-party.rst:0 msgid "" -"Below we're talking about settings that are important and not self-" -"explanatory." +"Screenshot showing sample notification mail after initial\n" +"third-party linking" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:17 +#: ../settings/security/third-party.rst:85 msgid "" -"Choose the object context you want to run the workflow in. This will decide " -"on your available attributes and actions." +"This notification is only sent if the account in question already exists. If " +"the login via the third-party also creates the missing account, the " +"notification will be skipped." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:20 -msgid "Ticket objects also have access to the ticket customer." +#: ../settings/security/third-party.rst:89 +msgid "This means it only affects:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:25 -msgid "" -"Choose in which situation the workflow is applied. Contexts can be combined " -"to avoid duplicate workflows." +#: ../settings/security/third-party.rst:91 +msgid "manual account linking within the third-party page of the users profile" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:30 -msgid "Creation mask" +#: ../settings/security/third-party.rst:92 +msgid "" +"logging into an existing local account by utilizing the *automatic account " +"link on initial logon* functionality" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:29 +#: ../settings/security/third-party.rst:None msgid "" -"If selected, your conditions and actions will affect all applicable creation " -"masks." +"Screenshot showing the \"automatic account linking notification\"\n" +"setting" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:34 -msgid "Edit mask" +#: ../settings/security/third-party.rst:100 +msgid "No User Creation on Logon" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:33 +#: ../settings/security/third-party.rst:102 msgid "" -"If selected, your conditions and actions will affect all applicable edit " -"masks." +"By default, Zammad will create a new user account if the user logs in via a " +"third-party application and the account doesn't exist yet." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:39 +#: ../settings/security/third-party.rst:105 msgid "" -"Zammad differentiates between selected and saved conditions. These can be " -"combined wherever needed." +"If you want to prevent Zammad from creating new accounts on logon, you can " +"disable this feature by setting ``No user creation on logon`` to ``yes``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:42 -msgid "**⚠️ Restrict workflows to specific roles if needed!**" +#: ../settings/security/third-party.rst:None +#, fuzzy +msgid "Screenshot showing the \"no user creation on logon\" setting" msgstr "" +"Capture d'écran montrant la configuration de base d'une boîte de réception" -#: ../system/core-workflows/how-do-they-work.rst:44 +#: ../settings/security/third-party/facebook.rst:4 msgid "" -"By default and unless configured in conditions, workflow rules are executed " -"for **all roles**. This also affects your customers!" +"It is possible to create a quick login for your helpdesk via Facebook To do " +"so, you need to follow these steps:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:50 -msgid "Selected Conditions" +#: ../settings/security/third-party/facebook.rst:9 +msgid "Register Facebook App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:48 +#: ../settings/security/third-party/facebook.rst:11 msgid "" -"These conditions are based on form values and match if an appropriate " -"selection is made (e.g. choosing another group in the ticket without " -"saving). This applies for drafts (active selection) and currently saved " -"values." +"Visit [https://developers.facebook.com/apps/] and click on \"Add a new App\"" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:64 -msgid "Saved Conditions" +#: ../settings/security/third-party/facebook.rst:None +msgid "initial page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:53 -msgid "" -"These conditions only match if the selected values are stored in the " -"database. It ignores the current value or selection of the field, as long as " -"the changes are not saved (e.g. performing field operations for an existing " -"ticket, which is viewed/opened by an agent)." +#: ../settings/security/third-party/facebook.rst:17 +msgid "After that enter the app settings" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:60 -msgid "" -"Keep in mind that the value has to be available in the situation where you " -"need it. Otherwise the condition won't match." +#: ../settings/security/third-party/facebook.rst:None +msgid "Create App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:63 -msgid "" -"Example: you can't perform any actions with *saved condition* on a ticket in " -"creation, because there are no saved values at that time." +#: ../settings/security/third-party/facebook.rst:22 +msgid "Navigate to \"Settings\" and fill in this infromation" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:66 -msgid "" -"You can find a description of the condition operators for core workflows :" -"doc:`here `." +#: ../settings/security/third-party/facebook.rst:None +msgid "App Settings" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:72 -msgid "" -"Which actions should we run on the relevant fields? The possible actions " -"depend on the object type. However, usually you can at least change the " -"visibility and whether the field is mandatory." +#: ../settings/security/third-party/facebook.rst:27 +msgid "Navigate to app review and Check \"Make [appname] public?\"" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:76 -msgid "Be aware that actions are not available for **related** context." +#: ../settings/security/third-party/facebook.rst:None +msgid "App Review" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:78 -msgid "" -"**Example:** Let's assume you are working in the ticket context. While you " -"can have customer *conditions*, you *can't adjust* objects with actions in " -"that scope. That's because this wouldn't have any impact on the ticket " -"dialog. Of course all ticket attributes (state, owner, ...) are available." +#: ../settings/security/third-party/facebook.rst:35 +msgid "Configure Zammad as Facebook App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:84 +#: ../settings/security/third-party/facebook.rst:37 msgid "" -"Please also have a look at our :doc:`limitations` to be safe from surprises." -msgstr "" - -#: ../system/core-workflows/how-do-they-work.rst:88 -msgid "Available Operators" +"Navigate to \"Admin -> Security -> Third Party Applications\" and enter the " +"App ID and the App Secret. You can find this Key in the Dashbard of your " +"Facebok app." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:90 -msgid "The availability of operators depends on the object type and scope." +#: ../settings/security/third-party/facebook.rst:None +msgid "Zammad Configuration" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:94 +#: ../settings/security/third-party/facebook.rst:44 +#: ../settings/security/third-party/github.rst:43 +#: ../settings/security/third-party/gitlab.rst:46 msgid "" -"Please note that actions may or may not restrict API based access to " -"attributes. We're displaying the following icons for your overview to " -"understand these limits better:" +"Now you can link accounts via \"Avatar -> Profile -> Link Accounts\" or " +"login via Zammad login page." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:0 -msgid "|api| This icon indicates the action affects the API." +#: ../settings/security/third-party/github.rst:2 +#: ../system/integrations/github.rst:2 +msgid "GitHub" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:163 -msgid "api" +#: ../settings/security/third-party/github.rst:4 +msgid "" +"It is possible to create a quick login for your helpdesk via GitHub. To " +"activate the quick login you need to enable OAuth for GitHub." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:0 -msgid "|ui| This icon indicates the action only affects the web interface." +#: ../settings/security/third-party/github.rst:8 +msgid "Register GitHub App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:167 -msgid "ui" +#: ../settings/security/third-party/github.rst:10 +msgid "" +"Visit https://www.github.com/settings/applications/new and enter the app " +"settings. As callback URL enter \"https://zammad_host/auth/github/callback\" " +"where zammad_host has to be replaced with your Zammad FQDN" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:102 -msgid "show |ui|" +#: ../settings/security/third-party/github.rst:None +msgid "Register OAuth app on www.github.com" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:102 -msgid "Display the chosen field. Allows setting of values." +#: ../settings/security/third-party/github.rst:19 +msgid "Configure Zammad as GitHub App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:109 -msgid "hide |ui|" +#: ../settings/security/third-party/github.rst:21 +msgid "" +"Enter the \"APP ID\" and the \"APP SECRET\" from the GitHub OAUTH " +"Applications Dashboard" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:105 -msgid "" -"Hide the chosen field. However, it technically still allows setting the " -"field." +#: ../settings/security/third-party/github.rst:None +msgid "GitHub config in Zammad admin interface" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:108 +#: ../settings/security/third-party/github.rst:28 msgid "" -"Please note that the field is **not** gone and still contains an existing " -"value (if set)! Consider *remove* instead, if you want this field to be gone." +"After you configured the GitHub credentials and activated the login method, " +"you should see a new icon on the login page." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:112 -msgid "remove |ui|" +#: ../settings/security/third-party/github.rst:None +msgid "GitHub logo on login page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:112 -msgid "Entirely removes the field. The field value will not be evaluated." +#: ../settings/security/third-party/github.rst:34 +msgid "" +"If you click on the icon you will be redirected to GitHub and see something " +"similar to this:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:115 -msgid "set mandatory |ui| |api|" +#: ../settings/security/third-party/github.rst:None +msgid "GitHub oauth page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:115 -msgid "Sets the field to mandatory." +#: ../settings/security/third-party/github.rst:40 +#: ../settings/security/third-party/gitlab.rst:42 +msgid "" +"When you grant the access you will be redirected to your Zammad instance and " +"logged in as a customer." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:118 -msgid "set optional |ui| |api|" +#: ../settings/security/third-party/gitlab.rst:2 +msgid "Gitlab" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:118 -msgid "Sets the field to optional." +#: ../settings/security/third-party/gitlab.rst:4 +msgid "" +"It is possible to create a quick login for your helpdesk via Gitlab. To " +"activate the quick login you need to enable OAuth for Gitlab." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:124 -msgid "add option |ui| |api|" +#: ../settings/security/third-party/gitlab.rst:8 +msgid "Register Gitlab App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:121 -msgid "Allows adding options to tree selects or selects." +#: ../settings/security/third-party/gitlab.rst:10 +msgid "To register an app in Gitlab open your profile and select applications." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:123 +#: ../settings/security/third-party/gitlab.rst:12 msgid "" -"You have to use the \"remove option\" before performing this action. It " -"allows you to use *existing* configured values." -msgstr "" - -#: ../system/core-workflows/how-do-they-work.rst:128 -msgid "remove option |ui| |api|" +"As callback URL enter \"https://zammad-fqdn/auth/gitlab/callback\" where " +"zammad-fqdn has to be replaced with your Zammad FQDN" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:127 -msgid "" -"Allows removing options from tree selects or selects. It allows you to use " -"*existing* configured values." +#: ../settings/security/third-party/gitlab.rst:None +msgid "Register OAuth app on gitlab instance" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:134 -msgid "set fixed to |ui| |api|" +#: ../settings/security/third-party/gitlab.rst:18 +msgid "Just select *read_user* under scopes as in the screenshot and save it." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:131 -msgid "Reduces the available options by your selection." +#: ../settings/security/third-party/gitlab.rst:21 +msgid "Configure Zammad as Gitlab App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:133 +#: ../settings/security/third-party/gitlab.rst:23 msgid "" -"This reduces your workflows in terms of *add option* and *remove option*." +"Enter the \"APP ID\" and the \"APP SECRET\" from the Gitlab OAUTH " +"Applications Dashboard and your Gitlab-URL in the \"SITE\" field." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:137 -msgid "fill in |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab config in Zammad admin interface" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:137 -msgid "Allows filling in of string and integer fields with your values." +#: ../settings/security/third-party/gitlab.rst:30 +msgid "" +"After you configured the Gitlab credentials and activated the login method, " +"you should see a new icon on the login page." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:141 -msgid "fill in empty |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab logo on login page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:140 +#: ../settings/security/third-party/gitlab.rst:36 msgid "" -"Allows filling in of string and integer fields with your values **if the " -"field is empty**." +"If you click on the icon you will be redirected to Gitlab and see something " +"similar to this:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:144 -msgid "select |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab oauth page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:144 -msgid "Select a specific value within a select, tree select or boolean field." +#: ../settings/security/third-party/google.rst:4 +msgid "" +"With some easy and fast steps, you can enable Zammad to authenticate your " +"users via Google." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:153 -msgid "auto select |ui|" +#: ../settings/security/third-party/google.rst:8 +msgid "Register a Google App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:147 -msgid "Helps users with tree select and select fields:" +#: ../settings/security/third-party/google.rst:10 +msgid "" +"First of all, we need to create a new project - you can skip this step if " +"you already have one." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:149 +#: ../settings/security/third-party/google.rst:15 msgid "" -"If the field has only one option available for selection and no value yet, " -"the value will be automatically set." +"Use this link to create a new project: https://console.cloud.google.com/" +"projectcreate" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:152 +#: ../settings/security/third-party/google.rst:18 msgid "" -"This option only works if you have one value and doesn't work if there is " -"more than one option available." +"Now expand the menu, expand \"APIs & Services\" and select \"Credentials\". " +"Go to the tab \"OAuth consent screen\" first and ensure to fill in the " +"requested information - without doing so you can't create credentials!" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:157 -msgid "set readonly |ui|" +#: ../settings/security/third-party/google.rst:None +msgid "Creating a consent screen" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:156 +#: ../settings/security/third-party/google.rst:25 msgid "" -"Allows you to display an attribute as read only (which means no changes are " -"possible)." -msgstr "" - -#: ../system/core-workflows/how-do-they-work.rst:161 -msgid "unset readonly |ui|" +"After filling in and saving the consent screen information, you can go to " +"the \"Credentials\" tab and create new \"OAuth client ID\"-Credentials." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:160 +#: ../settings/security/third-party/google.rst:28 msgid "" -"In case a workflow set the field in question to read only, you can undo this " -"with option above." +"Fill in the necessary information as follows and replace ``zammad_host`` " +"with your FQDN:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:172 -msgid "Stop after match" +#: ../settings/security/third-party/google.rst:31 +msgid "**Application type** ``[x] Web application``" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:174 -msgid "" -"Here you can decide if other workflows are executed after the current one." +#: ../settings/security/third-party/google.rst:34 +msgid "**Authorized JavaScript origins** ``https://zammad_host/``" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:176 +#: ../settings/security/third-party/google.rst:37 msgid "" -"If set to ``no`` (default), further workflows will be executed if they match " -"the condition. In this case, it is possible that your actions from the " -"current workflow can be overwritten by another workflow." +"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" +"callback``" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:180 -msgid "" -"If set to ``yes``, no further worflows will be executed after the current " -"one." +#: ../settings/security/third-party/google.rst:None +msgid "Adding a new OAuth client ID" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:184 -msgid "Priority" -msgstr "Priorité" - -#: ../system/core-workflows/how-do-they-work.rst:186 +#: ../settings/security/third-party/google.rst:43 msgid "" -"You can define the sequence, in which the workflows are executed. The " -"default value is ``500``." +"After creating the credentials, go to your Zammad installation and navigate " +"to \"Admin > Security > Third Party Applications\" > Google. Enter your " +"Client ID and Client secret here." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:189 -msgid "" -"The workflows are executed in ascending order by their priority. That means " -"lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." +#: ../settings/security/third-party/google.rst:None +msgid "Zammad" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:2 -#, fuzzy -msgid "Learn by Example" -msgstr "exemple" +#: ../settings/security/third-party/google.rst:50 +msgid "After submitting, the login via Google can be used." +msgstr "" -#: ../system/core-workflows/learn-by-example.rst:4 -msgid "" -"This page provides some basic examples for Core Workflows. Of course you can " -"build much more complex workflows if needed." +#: ../settings/security/third-party/microsoft.rst:2 +msgid "Microsoft" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:7 +#: ../settings/security/third-party/microsoft.rst:4 msgid "" -"To learn about Core Workflows in detail, first go to :doc:`how-do-they-work`." +"Zammad's Microsoft connection allows your users with Microsoft accounts to " +"login. This works for Azure users as well and can be an alternative to :doc:" +"`/system/integrations/ldap/index`." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:10 -#, fuzzy -msgid "Group Based Examples" -msgstr "exemple" - -#: ../system/core-workflows/learn-by-example.rst:12 +#: ../settings/security/third-party/microsoft.rst:10 msgid "" -"All following workflows have the same base configurations. The workflow may " -"not use them all." +"This documentation part does not cover our :doc:`📧 Microsoft 365 email " +"channel `." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:15 -#, fuzzy -msgid "Groups:" -msgstr "Groupes" - -#: ../system/core-workflows/learn-by-example.rst:20 -#, fuzzy -msgid "Attributes:" -msgstr "Variables Article" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screenshot showing Microsoft login button on Zammad login screen." +msgstr "" -#: ../system/core-workflows/learn-by-example.rst:22 -msgid "Category (Single tree selection field, not mandatory, agents only)" +#: ../settings/security/third-party/microsoft.rst:30 +#: ../settings/security/third-party/microsoft.rst:53 +msgid "Supported account types:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:23 +#: ../settings/security/third-party/microsoft.rst:22 msgid "" -"Approved (Boolean field, not mandatory, not shown, ``false`` as default)" +"Please note that Zammad only supports these account types (App dependent):" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:24 -msgid "Operating System (Text field, not mandatory, not shown)" +#: ../settings/security/third-party/microsoft.rst:35 +msgid "Avatars of signing in users:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:25 -msgid "Software used (Single selection field, not mandatory, not shown)" +#: ../settings/security/third-party/microsoft.rst:33 +msgid "" +"Zammad currently ignores user avatars. If the user is registered with e.g. " +"Gravatar, Zammad will fetch the avatar from there if enabled. See :doc:" +"`Zammad Image Service ` for more." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:68 -msgid "Group specific values and fields" +#: ../settings/security/third-party/microsoft.rst:38 +msgid "Step 1 - Register a Microsoft App for Zammad" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:28 +#: ../settings/security/third-party/microsoft.rst:40 msgid "" -"This workflow set depends on the category field. It reduces the available " -"set of values based on the group selected." +"Login to the `Microsoft Azure Portal `_ and " +"navigate to App registrations to create a new app. Provide the requested " +"information as follows and register your app." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:33 -msgid "Workflow 2nd Level group" +#: ../settings/security/third-party/microsoft.rst:46 +msgid "Name:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:35 +#: ../settings/security/third-party/microsoft.rst:45 msgid "" -"This reduces the category options to ``2nd Level/*``, ``Internal/*`` and " -"``Others``. It also sets further required fields to mandatory and visible." -msgstr "" - -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for 2nd level" +"Any meaningful name fitting, this name will be displayed to users trying to " +"authenticate with this app." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:43 -msgid "Workflow Support group" +#: ../settings/security/third-party/microsoft.rst:49 +msgid "Choose one of the above mentioned account types (see Limitations)." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:45 +#: ../settings/security/third-party/microsoft.rst:51 msgid "" -"This reduces the category options to ``Support/*``, ``Internal/*`` and " -"``Others``. It also sets further required fields to visible." -msgstr "" - -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for support" +"The correct account type depends on your use case. If you want to use the " +"authentication internal only, choose the first option. If you're unsure, use " +"the \"Help me choose...\" link." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:53 -msgid "Workflow Sales group" +#: ../settings/security/third-party/microsoft.rst:58 +msgid "Redirect URI (optional):" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:55 +#: ../settings/security/third-party/microsoft.rst:56 msgid "" -"This reduces the category options to ``Sales/*``, ``Internal/*`` and " -"``Others``." +"Select web and provide your callback URL. The callback URL looks like this: " +"``https://zammad.domain.tld/auth/microsoft_office365/callback``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for sales" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to register a Microsoft app" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:68 -#: ../system/integrations/slack.rst:88 -msgid "The Result" +#: ../settings/security/third-party/microsoft.rst:71 +msgid "Within **API permissions** add the following permissions:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:63 -msgid "" -"This is what the agent would experience with the above workflows in place." +#: ../settings/security/third-party/microsoft.rst:69 +msgid "``User.Read``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "" -"Workflow shows objects and limits options based on selections on the group" +#: ../settings/security/third-party/microsoft.rst:71 +msgid "Contacts" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:90 -msgid "Approval process" +#: ../settings/security/third-party/microsoft.rst:71 +msgid "``Contacts.Read``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:71 +#: ../settings/security/third-party/microsoft.rst:73 msgid "" -"In this case ``approved`` is visible to agents by default. For this " -"workflow, an additional role ``Approval person`` is required (no further " -"permissions)." +"You can find these permissions within *Microsoft Graph → Delegated " +"permissions*." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that restricts an approval attribute to specific roles" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to add required API permissions" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:81 +#: ../settings/security/third-party/microsoft.rst:80 msgid "" -"This workflow may work best in combination with a :doc:`trigger ` but technically, this is not required." +"Within **Certificates & secrets** create a new client secret. Note down the " +"returned secret **value** for later. **Do not** use the secret ID!" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:84 -msgid "" -"Select fields may be a better approach because they allow more values than " -"just a simple ``true`` or ``false``." +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to create a new app secret" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 +#: ../settings/security/third-party/microsoft.rst:88 msgid "" -"Workflow fixes possible values of \"Approved ?\" to a specific selection " -"depending on the users role" +"From **Overview** copy your apps *Application (client) ID*. If you're using " +"a single tenant app, please also copy *Directory (tenant) ID*. You now have " +"all required information for Zammad." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:103 -msgid "State dependent mandatory fields" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to retreive application client and tenant IDs" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:93 +#: ../settings/security/third-party/microsoft.rst:98 +msgid "Step 2 - Add App Credentials to Zammad" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:100 msgid "" -"This workflow sets ``Category`` to mandatory if the agent wants to set the " -"states ``closed`` or ``pending close`` to enforce categorization." +"Navigate to Security > Third-party Applications (Tab) within Zammad's admin " +"settings. Scroll down to the section *Authentication via Microsoft* and fill " +"in the required information." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that sets fields to mandatory on specific states" +#: ../settings/security/third-party/microsoft.rst:105 +msgid "App ID:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "" -"Workflow sets category field to mandatory upon choosing closed or pending " -"close as state" +#: ../settings/security/third-party/microsoft.rst:105 +msgid "This is your *Application (client) ID*." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:106 -msgid "Manual Ticket Handover Process" +#: ../settings/security/third-party/microsoft.rst:108 +msgid "App secret:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:108 -msgid "This example covers the handover of a ticket from one agent to another:" +#: ../settings/security/third-party/microsoft.rst:108 +msgid "This is your *client secret* (value)." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:110 -msgid "" -"When the ticket owner is modified, a new text field (\"Handover\") shows up " -"for a comment" +#: ../settings/security/third-party/microsoft.rst:113 +msgid "App Tenant ID:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:112 +#: ../settings/security/third-party/microsoft.rst:111 msgid "" -"This may only be visible when the owner is changed, therefore it has to be " -"hidden in general" +"**optional** only required for apps that use account type *Accounts in this " +"organizational directory only (Default Directory only - Single tenant).*" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:114 -msgid "The input in this handover text field is mandatory" +#: ../settings/security/third-party/microsoft.rst:115 +msgid "" +"Apply your settings by pressing submit and activate *Authentication via " +"Microsoft*." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:115 +#: ../settings/security/third-party/microsoft.rst:None msgid "" -"After submitting changes, the value of the handover field must be added as " -"an note to the ticket (via trigger)" +"Screencast showing how to add app credentials and activating the\n" +"authentication method" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:121 -msgid "Hiding handover field" +#: ../settings/security/third-party/saml.rst:2 +msgid "SAML" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Hiding the handover field in core workflows" +#: ../settings/security/third-party/saml.rst:4 +msgid "" +"Connect your SAML (Security Assertion Markup Language) identity provider as " +"a single sign-on (SSO) method." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:126 -msgid "Showing handover field and setting it to mandatory" +#: ../settings/security/third-party/saml.rst:7 +msgid "" +"SAML is an open standard for SSO authentication (among other things). Sign-" +"ins are shared across multiple **service providers** and managed by a " +"central **identity provider** (IdP)." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Showing the handover field and set it as mandatory" +#: ../settings/security/third-party/saml.rst:11 +msgid "" +"In this case, the service provider is Zammad, and the IdP is a software " +"service that you either host or subscribe to (*e.g.,* `Keycloak `_, `Redhat SSO Server `_, `ADFS `_, or `Okta `_)." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:131 -msgid "Trigger writing handover input to a new article" +#: ../settings/security/third-party/saml.rst:18 +msgid "" +"This guide assumes you are already using SAML within your organization (i." +"e., that your IdP is fully set up)." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Write handover content to a new article" +#: ../settings/security/third-party/saml.rst:21 +msgid "" +"Please note: Our instructions are based on connecting Zammad with Keycloak." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:133 -msgid "" -"As a result, the ticket includes an article of the type note which includes " -"the predefined text and the handover comment." +#: ../settings/security/third-party/saml.rst:25 +msgid "Step 1: Configure Your IdP" msgstr "" -#: ../system/core-workflows/limitations.rst:6 -msgid "Core Workflows do not replace Triggers" +#: ../settings/security/third-party/saml.rst:28 +msgid "Add Zammad as a Client/App" msgstr "" -#: ../system/core-workflows/limitations.rst:5 +#: ../settings/security/third-party/saml.rst:30 msgid "" -"Workflows manipulate the behavior of fields. However, they do not set values " -"in fields because of actions." +"Import Zammad into your IdP using the XML configuration found at ``https://" +"your.zammad.domain/auth/saml/metadata``." msgstr "" -#: ../system/core-workflows/limitations.rst:16 -msgid "API calls are only partly affected" +#: ../settings/security/third-party/saml.rst:33 +msgid "" +"If your IdP doesn't support XML import, you will have to configure Zammad as " +"a new client/app manually using the above XML metadata file for reference." msgstr "" -#: ../system/core-workflows/limitations.rst:9 +#: ../settings/security/third-party/saml.rst:36 +msgid "For instance, when you see this tag:" +msgstr "" + +#: ../settings/security/third-party/saml.rst:42 msgid "" -"Some options affect UI only and thus do not restrict responses and calls." +"Set the **Assertion Consumer Service Binding URL** (sometimes also listed as " +"**Valid Redirect URIs**) to ``http://your.zammad.domain/auth/saml/callback``." msgstr "" -#: ../system/core-workflows/limitations.rst:11 -msgid "This affects the following actions:" +#: ../settings/security/third-party/saml.rst:47 +msgid "Set Up User Attribute Mapping" msgstr "" -#: ../system/core-workflows/limitations.rst:13 -msgid "select" +#: ../settings/security/third-party/saml.rst:49 +msgid "" +"Zammad requests the following user attributes (or “properties”) from the IdP:" msgstr "" -#: ../system/core-workflows/limitations.rst:14 -msgid "auto select" +#: ../settings/security/third-party/saml.rst:51 +msgid "Email address (``email``)" msgstr "" -#: ../system/core-workflows/limitations.rst:15 -msgid "show" +#: ../settings/security/third-party/saml.rst:52 +msgid "Full name (``name``)" msgstr "" -#: ../system/core-workflows/limitations.rst:16 -msgid "hide" +#: ../settings/security/third-party/saml.rst:53 +msgid "Given name (``first_name``)" msgstr "" -#: ../system/core-workflows/limitations.rst:25 -msgid "Some fields stay unavailable to customers" +#: ../settings/security/third-party/saml.rst:54 +msgid "Family name (``last_name``)" msgstr "" -#: ../system/core-workflows/limitations.rst:19 +#: ../settings/security/third-party/saml.rst:56 msgid "" -"For technical and security reasons, some default fields (the pale ones you " -"can't edit) stay unavailable for display and usage on customer permissions." +"You may need to set up “mappers” (or “mappings”) to tell your IdP how user " +"attributes in SAML correspond to those in Zammad. For a more detailed " +"breakdown, refer to the XML metadata file referenced in the previous section." msgstr "" -#: ../system/core-workflows/limitations.rst:23 -msgid "" -"If you require your customers to change e.g. priorities, please consider " -"using workarounds via :doc:`/system/objects` and :doc:`/manage/trigger`." +#: ../settings/security/third-party/saml.rst:62 +msgid "Per-IdP Instructions" msgstr "" -#: ../system/core-workflows/limitations.rst:29 -msgid "Ticket title changes not supported in edit mask" +#: ../settings/security/third-party/saml.rst:102 +msgid "Keycloak" msgstr "" -#: ../system/core-workflows/limitations.rst:28 +#: ../settings/security/third-party/saml.rst:65 msgid "" -"It is currently not possible to perform changes of the ticket title in the " -"edit mask (e.g. renaming, set to read-only)." +"**To add Zammad as a client,** save the XML configuration to disk (``https://" +"your.zammad.domain/auth/saml/metadata``) and use **Clients > Clients list > " +"Import client** in the Keycloak admin panel." msgstr "" -#: ../system/core-workflows/limitations.rst:37 -msgid "What is out of scope of Core Workflows?" +#: ../settings/security/third-party/saml.rst:70 +msgid "" +"To help Zammad **match its own user accounts to Keycloak users**, create a " +"user attribute (or “property”) mapper. In **Clients list**, click on your " +"newly created Client ID, choose the tab **Client scopes** and click on the " +"link which refers to your Zammad instance. Choose **Add mapper > By " +"configuration > User Property** and create a mapper with the following " +"entries:" msgstr "" -#: ../system/core-workflows/limitations.rst:32 -msgid "" -"There are some things that would count as workflow but are either done via :" -"doc:`/manage/trigger` or :doc:`/manage/scheduler`." +#: ../settings/security/third-party/saml.rst:78 +msgid "**Name**" msgstr "" -#: ../system/core-workflows/limitations.rst:35 -msgid "Such as (but not limited to):" +#: ../settings/security/third-party/saml.rst:80 +msgid "**Mapper Type**" msgstr "" -#: ../system/core-workflows/limitations.rst:37 -msgid "up- or downgrade permissions of users" +#: ../settings/security/third-party/saml.rst:81 +msgid "``User Property``" msgstr "" -#: ../system/core-workflows/limitations.rst:38 -msgid "affecting article creation or listing" +#: ../settings/security/third-party/saml.rst:82 +msgid "**Property**" msgstr "" -#: ../system/data-privacy.rst:2 -msgid "Data Privacy" +#: ../settings/security/third-party/saml.rst:83 +msgid "``emailAddress``" msgstr "" -#: ../system/data-privacy.rst:4 -msgid "" -"For compliance with GDPR and other data privacy laws, you may wish to " -"**permanently delete users from the system**, along with **all of their " -"associated tickets**." +#: ../settings/security/third-party/saml.rst:84 +msgid "**SAML Attribute Name**" 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 `!" +#: ../settings/security/third-party/saml.rst:86 +msgid "**SAML Attribute NameFormat**" msgstr "" -#: ../system/data-privacy.rst:12 -msgid "" -"Access to this panel requires ``admin.data_privacy`` permissions (introduced " -"in Zammad 3.5)." +#: ../settings/security/third-party/saml.rst:87 +msgid "``basic``" msgstr "" -#: ../system/data-privacy.rst:15 +#: ../settings/security/third-party/saml.rst:89 msgid "" -"On older systems that have not been updated yet, customers can also be :docs:" -"`deleted via the Zammad console `." +"In the example above, we're telling Zammad that whenever it receives a SAML " +"login request, it should take the ``email`` property from Keycloak, look for " +"a Zammad user with the same ``email`` attribute, and create a new session " +"for that user." msgstr "" -#: ../system/data-privacy.rst:22 -msgid "User deletion dialog in the Data Privacy panel" +#: ../settings/security/third-party/saml.rst:95 +msgid "" +"If your Keycloak users' email addresses are stored on another property (*e." +"g.,* ``username``), adjust accordingly." msgstr "" -#: ../system/data-privacy.rst:22 +#: ../settings/security/third-party/saml.rst:98 msgid "" -"The user deletion dialog lists some of the tickets that will be removed from " -"the system along with the user." +"Back in **Settings**, enter the Client ID (``https://your.zammad.domain/auth/" +"saml/metadata``) in the field **Master SAML Processing URL**." msgstr "" -#: ../system/data-privacy.rst:27 -#, fuzzy -msgid "Deleting Users via GUI" -msgstr "Intégrations" - -#: ../system/data-privacy.rst:29 -msgid "🔥 **All deletions are FINAL!**" +#: ../settings/security/third-party/saml.rst:101 +msgid "You also need to enable **Sign assertions**." msgstr "" -#: ../system/data-privacy.rst:31 -msgid "Once you click “Delete”, the action cannot be canceled or undone." +#: ../settings/security/third-party/saml.rst:105 +msgid "Step 2: Configure Zammad" msgstr "" -#: ../system/data-privacy.rst:33 +#: ../settings/security/third-party/saml.rst:107 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." +"Enable SAML and enter your IdP's details in the Admin Panel under **Settings " +"> Security > Third Party Applications > Authentication via SAML**:" msgstr "" -#: ../system/data-privacy.rst:36 -msgid "**The following records cannot be deleted:**" +#: ../settings/security/third-party/saml.rst:None +msgid "Example configuration of SAML part 1" msgstr "" -#: ../system/data-privacy.rst:38 -msgid "your own account" +#: ../settings/security/third-party/saml.rst:119 +msgid "Display name" msgstr "" -#: ../system/data-privacy.rst:39 -msgid "the system's last remaining administrator account" +#: ../settings/security/third-party/saml.rst:116 +msgid "" +"Allows you to define a custom button name for SAML. This helps your users to " +"understand better what the button on the login page does." msgstr "" -#: ../system/data-privacy.rst:42 -msgid "Step 1: Find a User / Confirm Deletion" +#: ../settings/security/third-party/saml.rst:119 +msgid "Defaults to ``SAML``." msgstr "" -#: ../system/data-privacy.rst:44 -msgid "There are three ways to access the user deletion dialog:" +#: ../settings/security/third-party/saml.rst:123 +msgid "IDP SSO target URL" msgstr "" -#: ../system/data-privacy.rst:51 -msgid "**from the user's profile**" +#: ../settings/security/third-party/saml.rst:122 +msgid "" +"This is the target URL Zammad shall redirect to when the user presses the " +"SAML button. For Keycloak, this needs to look like https://your.domain/" +"realms/your-realm/protocol/saml" msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Accessing the user deletion dialog in a user profile" +#: ../settings/security/third-party/saml.rst:127 +msgid "IDP single logout target URL" msgstr "" -#: ../system/data-privacy.rst:51 -msgid "Click **Action > Delete**." +#: ../settings/security/third-party/saml.rst:126 +msgid "" +"This is the URL to which the single logout request and response should be " +"sent." msgstr "" -#: ../system/data-privacy.rst:58 -msgid "**in the “Manage > Users” Admin Panel**" -msgstr "" +#: ../settings/security/third-party/saml.rst:131 +#, fuzzy +msgid "IDP certificate" +msgstr "Intégrations" -#: ../system/data-privacy.rst:0 -msgid "Accessing the user deletion dialog under “Users” in the Admin Panel" +#: ../settings/security/third-party/saml.rst:130 +msgid "" +"The public certificate of your IDP for Zammad to verify during the callback " +"phase." msgstr "" -#: ../system/data-privacy.rst:58 -msgid "Use the **⋮ Actions** menu for the target user." +#: ../settings/security/third-party/saml.rst:145 +msgid "IDP certificate fingerprint" msgstr "" -#: ../system/data-privacy.rst:66 ../system/data-privacy.rst:104 -msgid "**in the “System > Data Privacy” Admin Panel**" +#: ../settings/security/third-party/saml.rst:134 +msgid "" +"The fingerprint of your IDPs public certificate to verify during callback " +"phase." msgstr "" -#: ../system/data-privacy.rst:0 -msgid "" -"Accessing the user deletion dialog under “Data Privacy” in the Admin Panel" +#: ../settings/security/third-party/saml.rst:137 +msgid "🔏 **For the IdP certificate / certificate fingerprint:**" msgstr "" -#: ../system/data-privacy.rst:65 +#: ../settings/security/third-party/saml.rst:139 msgid "" -"Use the **New Deletion Task** button. Search for users by name or email " -"address." +"Provide **only one or the other**—do not provide both! (Between the two, we " +"recommend the signing certificate itself: fingerprints use SHA-1, which `has " +"been broken for a while now `_.)" msgstr "" -#: ../system/data-privacy.rst:79 -#, fuzzy -msgid "**Delete organizations**" -msgstr "Sociétés" - -#: ../system/data-privacy.rst:69 +#: ../settings/security/third-party/saml.rst:144 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:" +"**Keycloak users:** Find your certificate in the Keycloak admin panel under " +"**Realm Settings > Keys > Algorithm: RS256 > Certificate**." msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Deleting an organization via the user deletion dialog" +#: ../settings/security/third-party/saml.rst:151 +msgid "Name identifier format" msgstr "" -#: ../system/data-privacy.rst:78 +#: ../settings/security/third-party/saml.rst:148 msgid "" -"If this option does not appear, make sure there are no pending deletion " -"tasks for other customers from this organization." +"This is the unique identifiers field type. Usually it should be ``urn:oasis:" +"names:tc:SAML:1.1:nameid-format:emailAddress``." msgstr "" -#: ../system/data-privacy.rst:82 -msgid "Step 2: Monitor Deletion Job Status" +#: ../settings/security/third-party/saml.rst:151 +msgid "Zammad **expects an email address as unique identifier**!" msgstr "" -#: ../system/data-privacy.rst:84 -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:" +#: ../settings/security/third-party/saml.rst:155 +msgid "UID attribute name" msgstr "" -#: ../system/data-privacy.rst:98 -msgid "**in the Activity Stream**" +#: ../settings/security/third-party/saml.rst:154 +msgid "" +"Here you can define an attribute that uniquely identifies the user. If " +"unset, the name identifier returned by the IDP is used." msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Activity Stream showing data privacy tasks" +#: ../settings/security/third-party/saml.rst:None +msgid "Example configuration of SAML part 2" msgstr "" -#: ../system/data-privacy.rst:94 +#: ../settings/security/third-party/saml.rst:163 msgid "" -"For each deleted user, the Activity Stream will be updated twice—once when " -"the task is created, and once when it's complete." +"Decide if the certificate for the connection to the IdP service has to be " +"verified or not (default: ``yes``)." msgstr "" -#: ../system/data-privacy.rst:97 -msgid "" -"These notifications are only visible to users with ``admin.data_privacy`` " -"permissions." +#: ../settings/security/third-party/saml.rst:169 +msgid "Signing & Encrypting" msgstr "" -#: ../system/data-privacy.rst:0 +#: ../settings/security/third-party/saml.rst:169 msgid "" -"The task list within Data Privacy shows removals being in progress and " -"completed." +"Define if you want to sign, encrypt, do both or nothing for the requests." msgstr "" -#: ../system/data-privacy.rst:107 -msgid "Frequently Asked Questions" +#: ../settings/security/third-party/saml.rst:179 +msgid "Certificate (PEM)" msgstr "" -#: ../system/data-privacy.rst:121 -msgid "What happens if I receive an email from a deleted customer?" +#: ../settings/security/third-party/saml.rst:172 +msgid "" +"Paste the public certificate of your Zammad SAML client, if you want to " +"encrypt the requests." msgstr "" -#: ../system/data-privacy.rst:110 -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." +#: ../settings/security/third-party/saml.rst:175 +#, fuzzy +msgid "Make sure the certificate is:" +msgstr "Intégrations" + +#: ../settings/security/third-party/saml.rst:177 +msgid "already valid and not yet expired" msgstr "" -#: ../system/data-privacy.rst:115 -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**." +#: ../settings/security/third-party/saml.rst:178 +#, fuzzy +msgid "no CA certificate" +msgstr "Intégrations" + +#: ../settings/security/third-party/saml.rst:179 +msgid "valid for signing and encrypting" msgstr "" -#: ../system/data-privacy.rst:130 -msgid "What about user information stored in internal notes or other messages?" +#: ../settings/security/third-party/saml.rst:185 +msgid "Private key (PEM)" msgstr "" -#: ../system/data-privacy.rst:124 +#: ../settings/security/third-party/saml.rst:182 msgid "" -"The deletion process removes **user accounts and associated tickets only**." +"Paste the private key of your Zammad SAML client here, if you want to sign " +"the requests." msgstr "" -#: ../system/data-privacy.rst:126 -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." +#: ../settings/security/third-party/saml.rst:185 +msgid "Make sure the key is an RSA key with a length of at least 2048 bits." msgstr "" -#: ../system/data-privacy.rst:137 -msgid "I deleted an user and can still see a message they sent!" +#: ../settings/security/third-party/saml.rst:188 +msgid "Private key secret" msgstr "" -#: ../system/data-privacy.rst:133 -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." +#: ../settings/security/third-party/saml.rst:188 +msgid "If your private key is secured with a secret, you can provide it here." msgstr "" -#: ../system/data-privacy.rst:141 -msgid "I removed a customer, now my reporting is off!" +#: ../settings/security/third-party/saml.rst:192 +msgid "Your callback URL" msgstr "" -#: ../system/data-privacy.rst:140 +#: ../settings/security/third-party/saml.rst:191 msgid "" -"When removing users and their tickets, all references are removed. This also " -"affects e.g. Reporting - these information are lost." +"This URL is needed for your IdP configuration so it knows where to redirect " +"to after successful authentication." msgstr "" -#: ../system/data-privacy.rst:145 -msgid "How long does Zammad store created tasks?" +#: ../settings/security/third-party/saml.rst:194 +msgid "" +"After saving your input by clicking on the \"Submit\" button, Zammad " +"verifies the provided keys/certificates (e.g. if they are valid for signing/" +"encrypting and if they aren't expired)." msgstr "" -#: ../system/data-privacy.rst:144 +#: ../settings/security/third-party/saml.rst:199 msgid "" -"Please see the on-premise data section of the :docs:`data privacy ` chapter." +"See :ref:`automatic account linking ` for details " +"on how to link existing Zammad accounts to IdP accounts." msgstr "" -#: ../system/data-privacy.rst:150 -msgid "What about re-assigned tickets? I want to delete them, too." -msgstr "" +#: ../settings/security/third-party/saml.rst:205 +msgid "Automatic account linking doesn't work" +msgstr "La liaison automatique de compte ne fonctionne pas" -#: ../system/data-privacy.rst:148 +#: ../settings/security/third-party/saml.rst:206 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." -msgstr "" - -#: ../system/data-privacy.rst:154 -msgid "Why are there so many deletion task entries, I didn't create them!" +"Have you double-checked your IdP's user attribute mapping configuration?" msgstr "" -#: ../system/data-privacy.rst:153 +#: ../settings/security/third-party/twitter.rst:4 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." +"It is possible to create a quick login for your helpdesk via Twitter. To do " +"so, you need to follow these steps:" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:2 -msgid "Admin Panel Reference" +#: ../settings/security/third-party/twitter.rst:8 +msgid "Register Twitter App" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:None -msgid "Screenshot of Checkmk settings overview" +#: ../settings/security/third-party/twitter.rst:10 +msgid "Go to https://dev.twitter.com/apps and login with your account." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:12 -msgid "" -"Which :doc:`group ` should Checkmk tickets be assigned " -"to as a default (*i.e.,* when none is specified)?" +#: ../settings/security/third-party/twitter.rst:15 +msgid "Click on \"Create App\"" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:15 -msgid "(Applies to :ref:`API alerts ` only.)" +#: ../settings/security/third-party/twitter.rst:None +msgid "new app page" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:21 -msgid "Auto close" +#: ../settings/security/third-party/twitter.rst:20 +msgid "" +"Enter app settings. As \"Callback URL\" you need to enter ``https://" +"zammad_host/api/v1/external_credentials/twitter/callback``. You need to " +"replace ``zammad_host`` with the domain of your Zammad system." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:18 +#: ../settings/security/third-party/twitter.rst:24 msgid "" -"Should Zammad automatically close tickets if a service has recovered on its " -"own?" +"After the app has been created, update the application icon and organization " +"attributes." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:21 -msgid "(Agents will receive notifications for such closures as appropriate.)" +#: ../settings/security/third-party/twitter.rst:None +msgid "set permissions to receive and send direct messages" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:30 -msgid "Auto-close state" +#: ../settings/security/third-party/twitter.rst:30 +msgid "" +"Next we need to set ``read, write and access direct messages`` permissions " +"for the app." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:24 -msgid "What ticket state should be applied when “auto-closing” a ticket?" +#: ../settings/security/third-party/twitter.rst:None +msgid "click on Keys & Access Token, note them" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:26 +#: ../settings/security/third-party/twitter.rst:36 msgid "" -"You can choose from the seven built-in ticket states. If these states aren't " -"enough for you, you can :ref:`define a new ticket state ` for this purpose as well. This can be useful for tracking " -"tickets with :doc:`reports `, for example." -msgstr "" - -#: ../system/integrations/checkmk/admin-panel-reference.rst:35 -#: ../system/integrations/cti/includes/recent-logs.include.rst:2 -#: ../system/integrations/ldap/index.rst:74 -#: ../system/integrations/pgp/index.rst:106 -msgid "Recent Logs" +"Go to \"Keys and Access Token\" tab and note the \"Consumer Key\" and " +"\"Consumer Secret\"." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:None -msgid "Screenshot of Checkmk \"Recent Logs\" section" +#: ../settings/security/third-party/twitter.rst:40 +msgid "Configure Zammad as Twitter App" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:41 +#: ../settings/security/third-party/twitter.rst:42 msgid "" -"If you're having trouble getting Zammad and Checkmk to play nicely together, " -"this section can help you troubleshoot." +"Go to \"Admin > Security > Twitter > Third Party Applications > Twitter\" " +"Section." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:44 -msgid "" -"It contains a record of the fifty most recent transactions that Zammad knows " -"about, including each one's request/response details and return status." +#: ../settings/security/third-party/twitter.rst:None +msgid "Admin > Security > Third Party Applications" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:2 -msgid "API Reference" +#: ../settings/security/third-party/twitter.rst:48 +msgid "" +"Fill in the \"Twitter Key\" and the \"Twitter Secret\" and click the " +"\"Submit\" button." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:4 +#: ../settings/security/third-party/twitter.rst:51 msgid "" -"For most users, :ref:`the sample scripts from the Setup Guide ` will do the job just fine. But if you want more fine-grained control" -"—for instance, to create high- and low-priority tickets for different types " -"of system events—then you'll have to customize the data those scripts send " -"to Zammad." +"Now you can link accounts via \"Avatar > Profile > Link Accounts\" or login " +"via Zammad login page." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:15 -msgid "" -"This custom script will automatically set all tickets it creates to **high " -"priority** and **assign them to charlie@chrispresso.com**." +#: ../settings/security/two-factor.rst:11 +msgid "Two-factor Authentication Methods" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:32 -msgid "How Does it Work?" +#: ../settings/security/two-factor.rst:2 +msgid "Two-Factor Authentication" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:34 +#: ../settings/security/two-factor.rst:4 msgid "" -"There are two kinds of data you can pass to the API, both in the form of key-" -"value pairs:" +"Two-factor authentication (2FA) enhances the security of Zammad accounts by " +"adding an extra layer of verification beyond a password. It requires users " +"to provide two different types of authentication factors, typically " +"something they know (like a password) and something they possess (like a " +"mobile device or a security token), to ensure that only authorized " +"individuals can access the account." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:44 -msgid "Checkmk parameters" +#: ../settings/security/two-factor.rst:19 +msgid "Enable Recovery Codes" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:38 +#: ../settings/security/two-factor.rst:21 msgid "" -"are required, and make up the **contents** of the resulting tickets/" -"articles. They also determine whether an event creates a new ticket or " -"updates/closes an existing one." +"Recovery codes are one-time use security codes that can be used by the user " +"if they lose access to their other two-factor authentication methods. They " +"cannot be used on their own, they can only be activated if at least one two-" +"factor authentication method is enabled." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:42 -msgid "" -"These are the only values used in the sample scripts. **Use them as-is**; " -"technically, they can be customized, but it's hard to imagine a good reason " -"for it." +#: ../settings/security/two-factor.rst:None +msgid "Enable Recovery Codes Setting" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:52 -msgid "Ticket attributes" -msgstr "Attributs du ticket" - -#: ../system/integrations/checkmk/api-reference.rst:47 +#: ../settings/security/two-factor.rst:30 msgid "" -"are optional, and can be used to **adjust settings** on newly created " -"tickets (*e.g.,* set the owner, group, priority, or state)." +"Recovery codes can only be used as a backup method. If enabled, they will be " +"automatically generated for the user once they set up their initial two-" +"factor authentication method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:50 +#: ../settings/security/two-factor.rst:34 msgid "" -"If you want to customize your Checkmk alert script, do it with these. Simply " -"add an extra “form” option for each one (``-F \"key=value\"``) to your " -"script's ``curl`` command line, as in the example above." +"The user will be asked to print out or save the generated recovery codes in " +"a safe place. Once used, a recovery code cannot be reused." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:54 -msgid "💡 **It's just an API endpoint!**" +#: ../settings/security/two-factor.rst:37 +msgid "" +"Users will also have an option to regenerate their recovery codes at any " +"time, which invalidates already existing recovery codes and provides them " +"with a list of fresh codes." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:56 +#: ../settings/security/two-factor.rst:41 msgid "" -"When using Checkmk integration, messages need to be formatted in a certain " -"way, but that *doesn't mean the messages actually have to come from Checkmk*." +"After you enable this setting, when the user completes a setup of their " +"initial two-factor authentication method, they will be presented with a list " +"of recovery codes and instructed to save them for later use." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:59 -msgid "" -"If you use another monitoring tool that's not officially supported by " -"Zammad, there's probably a way to make it work with your Checkmk callback " -"URL." +#: ../settings/security/two-factor.rst:None +msgid "Recovery Codes Generation Modal Dialog" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:63 -msgid "Checkmk Parameters" +#: ../settings/security/two-factor.rst:50 +msgid "Enforce the Set Up of the Two-Factor Authentication" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:65 +#: ../settings/security/two-factor.rst:52 msgid "" -"When a notification is received, Zammad creates a new article containing the " -"details of the event that triggered it:" +"In case you wish to require your users to set up at least one two-factor " +"authentication method for their account, you can do this by selecting " +"specific user roles the requirement applies to in **Enforced for user " +"roles** setting. Of course you must have at least one two-factor " +"authentication method enabled for this setting to take effect." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:None -msgid "Checkmk article body" +#: ../settings/security/two-factor.rst:None +msgid "Enforced for User Roles Setting" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:72 +#: ../settings/security/two-factor.rst:62 msgid "" -"These details come from the fields listed below, which correspond to " -"parameters provided by Checkmk (``$NOTIFY_*``)." -msgstr "" - -#: ../system/integrations/checkmk/api-reference.rst:75 -msgid "**Required fields are marked with an asterisk (\\*).**" +"After you change this setting, if the user has one of the selected roles on " +"their account, they will be forced to set up the two-factor authentication " +"upon next sign in or application reload." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:79 -msgid "event_id\\*" +#: ../settings/security/two-factor.rst:66 +msgid "" +"A modal dialog with instructions will be shown, and they will not be able to " +"do any work before they set up at least one two-factor method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:78 -msgid "" -"A unique ID for the system event. (``$NOTIFY_SERVICEPROBLEMID`` / " -"``$NOTIFY_HOSTPROBLEMID``)" +#: ../settings/security/two-factor.rst:None +msgid "Modal Dialog for Enforcing Two-Factor Authentication Set Up" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:86 -msgid "host\\*" +#: ../settings/security/two-factor.rst:74 +msgid "Reset Two-Factor Authentication for a Specific User" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:82 +#: ../settings/security/two-factor.rst:76 msgid "" -"The hostname of the system that the event originated from. " -"(``$NOTIFY_HOSTNAME``)" +"In case an user isn't able to login anymore because of an inaccessible " +"second factor, you can reset the user's 2FA method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:85 +#: ../settings/security/two-factor.rst:79 msgid "" -"Used to determine if a new event belongs to an existing ticket. Also used in " -"the subject line of the resulting article (“ is ”)." +"To do this, go to the user management and search for the relevant user. " +"After you found the account, click the button in the action column and " +"select \"Manage Two-Factor Authentication\":" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:96 -msgid "service" +#: ../settings/security/two-factor.rst:None +msgid "Context menu in action column in user management" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:89 +#: ../settings/security/two-factor.rst:87 msgid "" -"The name of the service that the event originated from. " -"(``$NOTIFY_SERVICEDESC``)" +"After selecting this, you can see a dialog where you can either reset one " +"2FA method or reset all of the user's 2FA methods:" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:92 -msgid "Used to determine if a new event belongs to an existing ticket." +#: ../settings/security/two-factor.rst:None +msgid "Dialog for resetting user's 2FA method" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:94 -#: ../system/integrations/checkmk/api-reference.rst:110 -msgid "Displayed as ``-`` when omitted." +#: ../settings/security/two-factor.rst:94 +msgid "" +"Choose the fitting one, click on the corresponding \"Remove ...\" button and " +"confirm your action. The user now has to setup a new 2FA method, depending " +"on your 2FA configuration." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:104 -msgid "state\\*" +#: ../settings/security/two-factor/authenticator-app.rst:2 +msgid "Authenticator App" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:99 +#: ../settings/security/two-factor/authenticator-app.rst:4 msgid "" -"The current state of the service or host in question. " -"(``$NOTIFY_SERVICESTATE`` / ``$NOTIFY_HOSTSTATE``)" +"The authenticator app method is a type of two-factor authentication that " +"uses a mobile application to generate one-time codes for account " +"verification. After setting up the authenticator app on their device, the " +"user links it to their Zammad account." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:102 +#: ../settings/security/two-factor/authenticator-app.rst:12 msgid "" -"Used to detect when a ticket should be auto-closed (*i.e.,* on ``OK``/" -"``UP``). Also used in the subject line of the resulting article (“ is " -"”)." +"When logging in, the user is prompted to enter a time-sensitive code " +"generated by the app, in addition to their password. This code acts as the " +"second factor of authentication, providing an extra layer of security as it " +"changes periodically and is unique to the user's device." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:110 -msgid "text" +#: ../settings/security/two-factor/authenticator-app.rst:None +msgid "Security Code in Google Authenticator App" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:107 +#: ../settings/security/two-factor/authenticator-app.rst:22 msgid "" -"The output of the process that triggered the event. " -"(``$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" +"The app generates codes based on a shared secret key stored securely on both " +"the user's device and the server, ensuring a synchronized and secure " +"authentication process. The method of generating the codes is sometimes also " +"called TOTP (time-based one-time password)." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:121 -msgid "" -"The Object Manager attribute panel displays built-in and custom\n" -"attribute names." +#: ../settings/security/two-factor/authenticator-app.rst:28 +msgid "Enabling the Authenticator App Method" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:121 -msgid "Find a complete list of ticket attributes in the Object Manager." +#: ../settings/security/two-factor/authenticator-app.rst:30 +#: ../settings/security/two-factor/security-keys.rst:28 +msgid "To enable the method, just toggle the switch on in the settings." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:123 -msgid "" -"Ticket attributes are entirely optional, and can be used to customize the " -"tickets that Checkmk creates. (Note that these attributes will be ignored if " -"a new event belongs to an existing ticket.)" +#: ../settings/security/two-factor/authenticator-app.rst:None +msgid "Authenticator App Switch in Settings" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:128 +#: ../settings/security/two-factor/authenticator-app.rst:36 msgid "" -"Why would you want to do this? Maybe you have only one IT guy, and all " -"system monitoring issues should be automatically assigned to him. Or, maybe " -"you're creating multiple notification rules so that database outages take " -"higher priority than disk space warnings." +"Now the users will be able to set up this two-factor authentication method " +"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " +"Once they do, on next sign-in with password, they will be asked to provide " +"an additional security code generated by their mobile device." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:135 -msgid "In most cases, you'll probably want to set one of the following:" +#: ../settings/security/two-factor/security-keys.rst:2 +msgid "Security Keys" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:137 -msgid "group" -msgstr "groupe" - -#: ../system/integrations/checkmk/api-reference.rst:139 -msgid "state" +#: ../settings/security/two-factor/security-keys.rst:4 +msgid "" +"The security keys method is a type of a two-factor authentication that uses " +"Web Authentication API in the browser for verifying user's identity. The " +"user can register multiple hardware or software security keys with their " +"Zammad account and then they can use it during the sign-in process." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:140 -msgid "priority" -msgstr "priorité" - -#: ../system/integrations/checkmk/api-reference.rst:142 +#: ../settings/security/two-factor/security-keys.rst:12 msgid "" -"but in practice, you can set almost any attribute, including :doc:`custom " -"ones you created through the Object Manager `." +"When logging in, the user is prompted to provide the same security key they " +"registered with their account, in addition to their password. This key acts " +"as the second factor of authentication, providing an extra layer of security." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:145 -msgid "Please note that the following attributes are **not customizable**:" +#: ../settings/security/two-factor/security-keys.rst:None +msgid "Security Key dialog in Safari on macOS" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:147 -msgid "title" -msgstr "titre" +#: ../settings/security/two-factor/security-keys.rst:21 +msgid "" +"The type of the key can range from hardware USB sticks to passkeys stored in " +"a device of user's choice. Which type can be used depends on the browser " +"flavor and the platform of the user." +msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:148 -msgid "id" +#: ../settings/security/two-factor/security-keys.rst:26 +msgid "Enabling the Security Keys Method" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:149 -msgid "ticket number" +#: ../settings/security/two-factor/security-keys.rst:None +msgid "Security Keys Switch in Settings" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:151 -msgid "created_by_id" +#: ../settings/security/two-factor/security-keys.rst:34 +msgid "" +"Now the users will be able to set up this two-factor authentication method " +"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " +"Once they do, on next sign-in with password, they will be asked to provide " +"the same security key they registered during the setup." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:152 -msgid "updated_by_id" +#: ../settings/system/system-selfhosted.include.rst:3 +msgid "" +"Below settings are only available to self hosted users. In hosted " +"environments we're handling these settings for you to ensure service " +"stability." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:155 -msgid "Which Values Can Be Set?" +#: ../settings/system/base.rst:11 +msgid "Fully Qualified Domain Name" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:157 -msgid "😵 **Invalid values → unpredictable behavior**" +#: ../settings/system/base.rst:7 +msgid "The URL of your Zammad installation." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:159 -msgid "" -"If you provide a value that Zammad doesn't understand (*e.g.,* ``-F " -"\"priority=high\"``), it's not always clear what will happen. In some cases, " -"a ticket will be created with the default values instead - but in others, it " -"may not be created at all!" +#: ../settings/system/base.rst:9 ../settings/system/base.rst:17 +msgid "This setting is used within :doc:`/misc/variables` and notifications." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:164 -msgid "So what values does Zammad understand, then? Well, it depends..." +#: ../settings/system/system-base.include.rst:1 +msgid "It is automatically set by the *Getting Started wizard*." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:168 -msgid "Use an email address or username:" +#: ../settings/system/system-base.include.rst:5 +msgid "Changing this setting also changes callback URLs for your channels etc." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:190 -msgid "group & priority" +#: ../settings/system/system-base.include.rst:6 +msgid "This setting can have negative affects on being able to login." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:175 -msgid "Refer to the dropdown menus in the ticket pane:" +#: ../settings/system/base.rst:19 +msgid "HTTP type" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:0 -msgid "See possible values for certain attributes in the ticket pane." +#: ../settings/system/base.rst:14 +msgid "" +"The HTTP type tells your installation how your clients connect. This is " +"relevant for authentication and cookie security." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:187 -msgid "🙅 **Ticket state CANNOT be set this way!**" +#: ../settings/system/base.rst:31 +msgid "SystemID" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:189 +#: ../settings/system/base.rst:22 msgid "" -"Why? Because ``-F \"state=...\"`` is already used :ref:`as a Checkmk " -"parameter `." +"This ID is being used within your ticket number. In case you're " +"communicating with another ticket system with similar ticket number schemes " +"this ID greatly reduces the risk of false follow ups." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:222 -msgid "Everything Else" +#: ../settings/system/base.rst:26 +msgid "" +"The SystemID is randomly selected upon installation of Zammad (``1-99``)." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:193 +#: ../settings/system/base.rst:30 msgid "" -"To set any other attributes, it helps to know your way around the :docs:" -"`rails console `. Valid values are those that you can " -"set with a string:" +"**Do not** change this setting in a productive system! Your Zammad " +"installation may no longer recognize old ticket number based follow ups upon " +"change!" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:218 -msgid "These values can then be passed directly to the API:" +#: ../settings/system/frontend.rst:2 +msgid "Frontend" msgstr "" -#: ../system/integrations/checkmk/index.rst:16 -msgid "How does it work?" +#: ../settings/system/frontend.rst:22 +msgid "Core Workflow Ajax Mode" msgstr "" -#: ../system/integrations/checkmk/index.rst:2 -msgid "Checkmk" +#: ../settings/system/frontend.rst:6 +msgid "" +"This setting allows administrators to enforce :doc:`/system/core-workflows` " +"to use Ajax-Calls instead of web sockets. You'll usually only need this if " +"you experience serious issues as noted below." msgstr "" -#: ../system/integrations/checkmk/index.rst:4 +#: ../settings/system/frontend.rst:10 +msgid "**🤓 Possible (technical) reasons**" +msgstr "" + +#: ../settings/system/frontend.rst:12 msgid "" -"`Checkmk `_ is a powerful IT monitoring tool that can " -"send real-time status alerts to Zammad via email or REST API. Set these " -"alerts up in Checkmk, and Zammad will automatically create, update, and " -"close tickets based on the health of your system:" +"In some cases, your network structure (e.g. firewalls, proxies) may " +"disconnect long web socket connections. This leads to select fields staying " +"empty (e.g. owner selection *after* selecting your group) or fields not " +"shown / hidden (e.g. when switching to or from pending states, the \"pending " +"till\" field not showing / hiding)." msgstr "" -#: ../system/integrations/checkmk/index.rst:14 -msgid "Screenshot of ticket created by Checkmk notifications" +#: ../settings/system/frontend.rst:18 +msgid "" +"Please keep in mind that the Ajax fallback may cause serious pressure on " +"your application server. If you have the choice stick to web sockets." msgstr "" -#: ../system/integrations/checkmk/index.rst:14 -msgid "Multiple alerts, same ticket." +#: ../settings/system/frontend.rst:22 +msgid "Default: ``no`` (inactive)" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:2 -msgid "Setup Guide" +#: ../settings/system/frontend.rst:53 +msgid "Show calendar weeks in the picker of date/datetime fields" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:4 +#: ../settings/system/frontend.rst:25 msgid "" -"Whenever the Checkmk integration is enabled, Zammad listens for messages on " -"its API and over email. As long as those messages follow the required " -"format, Zammad will create new tickets (or find and update existing ones) " -"based on the message contents." +"With this setting you can instruct Zammad to provide week number display " +"globally for all users. Calendar with week number display are usually used " +"in business sectors and may not be relevant for everyone." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:10 +#: ../settings/system/frontend.rst:29 msgid "" -"That means that “setting up Checkmk integration” is simply a matter of " -"**adding configuration to your Checkmk site**: telling it when to send these " -"messages and what to say. To do that, you'll need to create a new " -"**notification rule** (see `Checkmk's official docs `_ for help with that)." +"This setting affects *all areas* - you'll also see week numbers in the admin " +"panel for e.g. triggers and macros." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:17 -msgid "" -"As part of this new rule, you'll have to choose a **notification method** " -"(*i.e.,* a script to execute whenever the rule is triggered). This script " -"will be written by you (samples below), and contain the logic for sending " -"API/email messages to Zammad:" +#: ../settings/system/frontend.rst:32 +msgid "Default: ``no`` (not shown)" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:26 -msgid "Checkmk \"New Rule\" dialog" +#: ../settings/system/frontend.rst:53 +msgid "Here's the difference:" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:26 -msgid "" -"Find your custom scripts in the Checkmk WATO under **Notifications > New " -"Rule > Notification Method**." +#: ../settings/system/frontend.rst:0 +msgid "Screenshot showing Zammad's date picker (in the default way)" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:29 -msgid "" -"Once you're done setting up your new rule, you're all set! New tickets " -"should start coming in and auto-updating any time your rule is triggered." +#: ../settings/system/frontend.rst:41 +msgid "Set to ``no``" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:33 +#: ../settings/system/frontend.rst:0 msgid "" -"(If you need help troubleshooting, be sure to check the :ref:`checkmk-recent-" -"logs`.)" +"Screenshot showing Zammad's date picker with\n" +"week numbers enabled" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:38 -msgid "API Alerts" +#: ../settings/system/frontend.rst:50 +msgid "Set to ``yes``" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:40 +#: ../settings/system/index.rst:4 msgid "" -"To add these scripts in the Checkmk WATO, copy them into your Checkmk " -"installation directory and make them executable. (Be sure to replace the " -"``zammad.example.com`` callback URL with the one found in your admin panel.)" +"For your overview we split each tab within system settings into its own page:" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:60 -msgid "Service notification" -msgstr "" +#: ../settings/system/index.rst:16 +#, fuzzy +msgid "Console Based Settings" +msgstr "Paramètres" -#: ../system/integrations/checkmk/setup-guide.rst:46 +#: ../settings/system/index.rst:18 msgid "" -"For updates on the status of the software running on your server (*e.g.,* " -"postgres)." +"There's some console based settings we didn't put into the UI. However, you " +"may find them helpful - you can find them in our :docs:`hidden settings ` section." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:75 -msgid "Host notification" +#: ../settings/system/network.rst:2 +msgid "Network" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:63 -msgid "For updates on the status of the server itself." +#: ../settings/system/network.rst:8 +msgid "" +"The proxy settings can only be saved after successfully testing the proxy " +"connection." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:77 -msgid "🤔 **What's with all the env vars?**" +#: ../settings/system/network.rst:15 +msgid "Proxy Address." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:79 +#: ../settings/system/network.rst:12 msgid "" -"Whenever Checkmk runs these scripts, it needs to provide some information " -"about the event that triggered the notification. This information is passed " -"in the form of these ``$NOTIFY_*`` environment variables." +"Allows you to provide a proxy server if needed. This is relevant for network " +"communication by Zammad." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:85 -msgid "" -"You can specify additional parameters to pass to the script when you're " -"setting up your notification rule, but the ones you see here are all " -"provided by default." +#: ../settings/system/network.rst:15 +msgid "It **does not** affect the update process or Elasticsearch." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:90 -msgid "Email Alerts" +#: ../settings/system/network.rst:18 +msgid "Username for proxy connection." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:94 +#: ../settings/system/network.rst:18 msgid "" -"🐞 **There are known bugs** in Zammad's processing of email from Checkmk. " -"This section will be completed once they have been resolved. (Learn more at " -"GitHub issues `#2377 `_ & " -"`#2180 `_.)" +"If your proxy server requires authentication, provide the username here." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:100 -msgid "In the meantime, we encourage you to set up API alerts instead." +#: ../settings/system/network.rst:21 +msgid "Password for proxy connection." msgstr "" -#: ../system/integrations/clearbit.rst:2 -msgid "Clearbit" +#: ../settings/system/network.rst:21 +msgid "" +"If your proxy server requires authentication, provide the password here." msgstr "" -#: ../system/integrations/clearbit.rst:4 -msgid "" -"With our Clearbit integration, you can easily enrich the information " -"provided by Zammad. If the customers or agents email address is known to " -"Clearbit, it will share all information it has regarding the user with " -"Zammad. Those information can include the following:" +#: ../settings/system/network.rst:26 +msgid "No proxy for the following hosts." msgstr "" -#: ../system/integrations/clearbit.rst:9 -msgid "Avatar" -msgstr "Avatar" +#: ../settings/system/network.rst:24 +msgid "" +"Exception list for hosts you can't or don't want to reach via proxy server." +msgstr "" -#: ../system/integrations/clearbit.rst:10 -msgid "Address information" +#: ../settings/system/network.rst:27 +msgid "Default: ``localhost,127.0.0.0,::1``" msgstr "" -#: ../system/integrations/clearbit.rst:11 -msgid "Website information" +#: ../settings/system/services.rst:2 +msgid "Services" msgstr "" -#: ../system/integrations/clearbit.rst:12 -msgid "A BIO (as Note by default)" +#: ../settings/system/services.rst:10 +msgid "Image Service" msgstr "" -#: ../system/integrations/clearbit.rst:14 -msgid "" -"If needed, you can add further custom objects and add mappings to them, so " -"the Clearbit information can be filled within the database. In general you " -"can get any information from Clearbit, as long as you have a mapping to an " -"Zammad object." +#: ../settings/system/services.rst:5 +msgid "Defines the backend for user and organization image lookups." msgstr "" -#: ../system/integrations/clearbit.rst:21 -msgid "" -"Clearbit does have a mapping of fields like LDAP and Exchange have, but does " -"not \"win\" against Zammad information. This means that if you have e.g. the " -"last name field filled in already and Clearbit has other information on " -"that, it will not be updated." +#: ../settings/system/services.rst:7 +msgid "Default: ``Zammad Image Service`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:26 +#: ../settings/system/services.rst:9 msgid "" -"However: If let's say the last name has been set by Clearbit and Zammad " -"notices that the last name on the Clearbit source has changed, Zammad will " -"also update this value." +"Make sure your on premise installation has ``HTTPS`` access to ``images." +"zammad.com``." msgstr "" -#: ../system/integrations/clearbit.rst:33 -msgid "" -"The configuration of Clearbit is really easy and done fast! Just login to " -"your Clearbit-Account, go to \"API\" and copy the secret-API-Key." +#: ../settings/system/services.rst:18 +msgid "Geo Calendar Service" msgstr "" -#: ../system/integrations/clearbit.rst:38 +#: ../settings/system/services.rst:13 msgid "" -"Now change to your Zammad instance, go to Integrations (System) -> Clearbit " -"in the admin panel. Paste your API-Key into the API-Key-Field and decide if " -"Zammad should create unknown Organizations automatically, if the user does " -"not have one yet (and Clearbit knows it). The shared option decides if the " -"new organizations Zammad creates with Clearbit should be shared ones." +"Defines the backend for geo calendar lookups. Used for initial calendar " +"setup." msgstr "" -#: ../system/integrations/clearbit.rst:47 -msgid "" -"If you're unsure what option to choose, better stick with \"no\". You can " -"also learn more about :doc:`/manage/organizations/index`." +#: ../settings/system/services.rst:16 +msgid "Default: ``Zammad GeoCalendar Service`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:52 +#: ../settings/system/services.include.rst:2 msgid "" -"The Mapping option works similar to the mapping within the Exchange and LDAP " -"sync. You can add further mappings for e.g. custom fields if you need more " -"information that Clearbit can provide." +"Make sure your on premise installation has ``HTTPS`` access to ``geo.zammad." +"com``." msgstr "" -#: ../system/integrations/clearbit.rst:58 -msgid "" -"If you want to add more Clearbit fields and want to learn more about " -"available fields on their API, you can take a look at their `API " -"documentation `_." +#: ../settings/system/services.rst:26 +msgid "Geo IP Service" msgstr "" -#: ../system/integrations/clearbit.rst:62 +#: ../settings/system/services.rst:21 msgid "" -"If you're happy with the above chosen Settings and your mapping, just save " -"the changes and enable Clearbit integration. Zammad will now start polling " -"the Clearbit API as users contact you." +"Defines the backend for geo IP lookups. Shows also location of an IP address " +"if an IP address is shown." msgstr "" -#: ../system/integrations/clearbit.rst:68 -msgid "" -"Zammad does not synchronize with Clearbit on a regular basis, but on demand " -"if needed. This saves API calls." +#: ../settings/system/services.rst:24 +msgid "Default: ``Zammad GeoIP Service`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:73 -msgid "" -"Below the Settings and Mappings, you'll find our Integration log. You can " -"see what requests Zammad sent to Clearbit and also the APIs Response." +#: ../settings/system/services.rst:32 +msgid "Geo Location Service" msgstr "" -#: ../system/integrations/clearbit.rst:78 +#: ../settings/system/services.rst:29 msgid "" -"By the way, you can also view the API log on the Clearbit website - the " -"information seen is basically the same." +"Defines the backend for geo location lookups to store geo locations for " +"addresses." msgstr "" -#: ../system/integrations/clearbit.rst:84 -msgid "Example When Adding a User" +#: ../settings/system/services.rst:32 +msgid "" +"Default: ``OpenStreetMap (ODbL 1.0, http://osm.org/copyright)`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:86 +#: ../settings/system/services.rst:36 msgid "" -"To show you how fast information is added, we added a small Screencast " -"below. This shows the creation of the User Alex from Clearbit. As we already " -"set the last name of Alex to \"X\", Zammad did not update it. What Zammad " -"did was to add further information it received from Clearbit." +"You can find a detailed privacy information on what we store for how long on " +"our :docs:`Privacy Appendix ` inside of our System " +"Documentation." msgstr "" -#: ../system/integrations/cti/generic.rst:2 -msgid "CTI (generic)" +#: ../settings/system/storage.rst:2 +msgid "Storage" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:1 +#: ../settings/system/storage.rst:6 msgid "" -"This integration enables Zammad to provide a caller log to your agents. With " -"this your agents can greet your customers by their name and are supported by " -"Zammad with automatically opening a new ticket dialog or the user profile." +"Here you can define where Zammad stores attachments for tickets and the " +"knowledge base. By default, we're writing to the ``Database`` - you can " +"switch to ``Filesystem`` or ``Simple Storage (S3)`` at any time. In this " +"case please have a look on the following instructions." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:6 +#: ../settings/system/storage.rst:11 msgid "" -"Click the toggle next to the heading to activate or deactivate this " -"integration." +"If you have a busy Zammad instance, we strongly encourage you to use " +"filesystem storage instead of \"Database\". This will greatly improve system " +"performance (de-crease database load and size)." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:9 -msgid "" -"If you want to learn more on how your agents can use this function, please " -"refer the :user-docs:`user documentation `." +#: ../settings/system/storage.rst:19 +msgid "Database" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:14 +#: ../settings/system/storage.rst:17 msgid "" -"Automatically opening new ticket dialogues or user profiles requires agent " -"to extension mapping - see more below." -msgstr "" - -#: ../system/integrations/cti/includes/introduction.include.rst:20 -msgid "Please note the following limitations to reduce confusion later on:" +"This is the default storage method. The attachments are stored directly in " +"the database. If your Zammad instance grows, we recommend one of the other " +"methods to maintain performance." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:22 -msgid "CTI integrations provide caller log functions only." +#: ../settings/system/storage.rst:38 +msgid "Filesystem" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:23 +#: ../settings/system/storage.rst:22 msgid "" -"This integration does not provide any VoIP functionalities; you can't make " -"phone calls from within Zammad." +"This storage method is recommended for all Zammad instances, especially for " +"those with a higher load. If you choose filesystem, your files are written " +"to ``/opt/zammad/storage/``." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:25 +#: ../settings/system/storage.rst:26 msgid "" -"If your browser supports ``tel``-URLs, you can click on phone numbers for " -"automatic dialing. This requires additional software / configuration on your " -"agent's computers." +"Moving attachments from \"Database\" to \"Filesystem\" can be run during " +"production use. However, you should consider your framework conditions (e.g. " +"bandwidth, system load in production) to define the right moment." msgstr "" -#: ../system/integrations/cti/generic.rst:9 -#: ../system/integrations/cti/placetel.rst:14 -#: ../system/integrations/cti/sipgate.rst:14 -msgid "Please provide the following requirements:" +#: ../settings/system/storage.rst:32 +msgid "**You noticed slow updates of Zammad?**" msgstr "" -#: ../system/integrations/cti/generic.rst:11 +#: ../settings/system/storage.rst:34 msgid "" -"A telephone system that supports webhooks (outbound) (best option are those " -"that allow customizing the calls)." +"While Zammad is beeing updated, it enforces a recursive \"change " +"owner\" (chown) for this directory. For instances with many files this can " +"be time consuming. To mitigate that you can move your files and create a " +"symlink in ``/opt/zammad/storage/`` to the new directory. Of course you have " +"to make sure on your own that the permissions are always correct." msgstr "" -#: ../system/integrations/cti/generic.rst:13 -msgid "A unique Call-ID during the call session." +#: ../settings/system/storage.rst:95 +msgid "Simple Storage (S3)" msgstr "" -#: ../system/integrations/cti/generic.rst:14 -msgid "Call event data (both numbers and direction)." +#: ../settings/system/storage.rst:41 +msgid "" +"To use the Simple Storage (S3), you have to provide some settings, which " +"can't be accessed in the UI (see instructions below)." msgstr "" -#: ../system/integrations/cti/generic.rst:15 -msgid "Your Zammad instance must be reachable for your telephony system." +#: ../settings/system/storage.rst:44 +msgid "" +"⚠️ Please note that the current implementation is in its early stages and can " +"be modified in the future." msgstr "" -#: ../system/integrations/cti/generic.rst:17 +#: ../settings/system/storage.rst:47 msgid "" -"If you want to learn more on what kind of requests are supported by Zammad " -"and what it expects, please consult our :docs:`CTI-API documentation `." +"The prerequisite is to have access to a S3-compatible storage and to have " +"all necessary parameters available (which depends on your storage provider; " +"if in doubt, please ask there for help)." msgstr "" -#: ../system/integrations/cti/generic.rst:22 -#: ../system/integrations/cti/placetel.rst:27 -#: ../system/integrations/cti/sipgate.rst:30 -#, fuzzy -msgid "Available Settings" -msgstr "Paramètres" - -#: ../system/integrations/cti/generic.rst:29 -#: ../system/integrations/cti/placetel.rst:41 -#: ../system/integrations/cti/sipgate.rst:40 -#, fuzzy -msgid "Endpoint Settings" -msgstr "Paramètres" +#: ../settings/system/storage.rst:51 +msgid "Steps to configure S3:" +msgstr "" -#: ../system/integrations/cti/generic.rst:25 +#: ../settings/system/storage.rst:53 msgid "" -"Zammad will list your generic CTI endpoint here. It contains a unique token " -"so ensure to keep this URL save." +"Copy ``config/zammad/storage.yml.dist`` to ``config/zammad/storage.yml``" msgstr "" -#: ../system/integrations/cti/generic.rst:28 -msgid "" -"You'll need this endpoint for your PBX to talk to Zammad, see :docs:`CTI-API " -"documentation `." +#: ../settings/system/storage.rst:54 +msgid "Edit the copied file in one of the following ways:" msgstr "" -#: ../system/integrations/cti/includes/important-dont-forget-saving.include.rst:3 +#: ../settings/system/storage.rst:56 msgid "" -"All following options **do not save automatically**. Always use the Save " -"button on the lower end of the integration page!" +"Either provide your S3 configuration with one attribute per line like in the " +"upper area of the file" msgstr "" -#: ../system/integrations/cti/generic.rst:43 -#: ../system/integrations/cti/placetel.rst:49 -#: ../system/integrations/cti/sipgate.rst:52 -#, fuzzy -msgid "Call Settings" -msgstr "Paramètres" - -#: ../system/integrations/cti/generic.rst:39 -#: ../system/integrations/cti/placetel.rst:49 -#: ../system/integrations/cti/sipgate.rst:37 -#: ../system/integrations/cti/sipgate.rst:50 -msgid "Inbound" +#: ../settings/system/storage.rst:58 +msgid "" +"Or provide your S3 configuration as an URL (which you can find at the end of " +"the file). Note: you can also provide this URL as environment variable (:" +"docs:`see system documentation `) without using this yml-file." msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:1 +#: ../settings/system/storage.rst:62 msgid "" -"This option allows you to block specific incoming caller IDs. It allows you " -"to temporarily reject e.g. spam callers without having to contact providers " -"or PBX administrators." +"We recommend the deletion of the not used configuration style to avoid " +"inconsistencies." msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:11 -msgid "Caller ID to block" +#: ../settings/system/storage.rst:65 +msgid "Restart Zammad so the config file / environment variable is loaded" msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 -msgid "Provide caller IDs to block in ``E.164`` format." +#: ../settings/system/storage.rst:66 +msgid "" +"Set the \"Storage Method\" in Zammad to ``Simple Storage (S3)`` in Settings " +"> System > Storage and click on \"Submit\". After that, Zammad checks your " +"configuration and the connection to the service and will raise an error " +"message if something is wrong." msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:8 +#: ../settings/system/storage.rst:72 +msgid "A very simple storage configuration could look like this:" +msgstr "" + +#: ../settings/system/storage.rst:85 msgid "" -"Your telephony system has to support this function. Zammad will send a " -"``reject`` response which will cause your telephony system to hang up the " -"call. To callers this usually will feel like the line is busy." +"Before setting the storage method to ``Simple Storage (S3)`` (step 4), " +"please make sure to have a working setup." msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:14 +#: ../settings/system/storage.rst:88 msgid "" -"Provide a meaningful note for your fellow administrators to remind yourself " -"why you've chosen to block the number." +"You can verify this by running ``rails r 'Rails.logger = Logger.new(STDOUT); " +"pp Store::Provider::S3.ping?'`` in your Zammad directory. If everything is " +"fine, you should see ``true``, else you should see ``false`` and a simple " +"error message." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 -#: ../system/integrations/cti/includes/outbound-calls.include.rst:17 -#: ../system/integrations/cti/sipgate.rst:40 -msgid "Outbound" +#: ../settings/system/storage.rst:93 +msgid "" +"If you installed Zammad through a package manager (rather than from source), " +"replace ``rails r`` with ``zammad run rails r`` above. To learn more, see :" +"docs:`Administration via Console `." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:1 +#: ../settings/ticket.rst:4 msgid "" -"In many cases you may want to use a different caller ID depending on the " -"destination you're calling. This may apply due to specific connection rates " -"to other countries or because you want your customer to feel you're calling " -"from the same country." +"Here you can adjust general ticket settings. Additional ones for the ticket " +"composer interface can be found in the :doc:`/misc/composer`." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:6 -msgid "This option expects ``E.164`` number formats." +#: ../settings/ticket.rst:11 +msgid "Ticket Hook (default: ``Ticket#``)" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 -msgid "Destination caller ID" +#: ../settings/ticket.rst:11 +msgid "The identifier for a ticket; *e.g.,* Ticket#, Call#, MyTicket#." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:5 -msgid "The caller ID or number you're trying to call." +#: ../settings/ticket.rst:38 +msgid "Ticket Hook Position (default: ``right``)" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:7 -msgid "You can use wildcards for e.g. country specific outbound numbers like:" +#: ../settings/ticket.rst:14 +msgid "" +"With this setting you can decide (if) where to insert the ticket number." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:9 -msgid "``49*`` for Germany" +#: ../settings/ticket.rst:20 +msgid "*Right*" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:10 -msgid "``4930*`` for Berlin / Germany landlines" +#: ../settings/ticket.rst:17 +msgid "" +"This setting will add the ticket reference on the right site of the subject." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 -msgid "``33*`` for France" +#: ../settings/ticket.rst:20 +msgid "Example: ``Some Subject [Ticket#12345]``" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:15 -msgid "Set Outbound caller ID" +#: ../settings/ticket.rst:26 +msgid "*Left*" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:14 +#: ../settings/ticket.rst:23 msgid "" -"The outbound caller ID to set (the number your customer sees on his display) " -"in ``E.164`` number format." +"This setting will add the ticket reference on the left site of the subject." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 -msgid "Provide a short description for fellow administrators." +#: ../settings/ticket.rst:26 +msgid "Example: ``[Ticket#12345] Some Subject``" msgstr "" -#: ../system/integrations/cti/includes/generic-cti-support-note.includes.rst:3 -msgid "" -"This option requires your PBX to send a specific request to Zammad *before " -"dialing*. Please consult the :docs:`CTI API ` in case " -"you're not sure." +#: ../settings/ticket.rst:29 +msgid "*None*" msgstr "" -#: ../system/integrations/cti/generic.rst:52 -#: ../system/integrations/cti/placetel.rst:54 -#: ../system/integrations/cti/sipgate.rst:59 -#, fuzzy -msgid "Other Settings" -msgstr "Paramètres" +#: ../settings/ticket.rst:29 +msgid "This will completely remove ticket references from the subject." +msgstr "" -#: ../system/integrations/cti/includes/other-settings-intro.include.rst:1 +#: ../settings/ticket.rst:33 msgid "" -"Below you can find all available additional settings for this CTI " -"integration. For your overview we're sorting them by appearance and " -"reference their description first." +"Please ensure to take a look at :doc:`/channels/email/settings` within the " +"email channel to ensure you have at least one reference that helps Zammad to " +"assign follow-ups correctly." msgstr "" -#: ../system/integrations/cti/includes/default-caller-id.include.rst:2 -#: ../system/integrations/cti/includes/default-caller-id.include.rst:1 -msgid "Default caller ID for outbound calls" +#: ../settings/ticket.rst:37 +msgid "" +"Disabling this and not setting up any further follow up search will lead to " +"unexpected results!" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:16 -#: ../system/integrations/cti/includes/records-caller-log.include.rst:15 -msgid "Shown records in caller log" +#: ../settings/ticket.rst:65 +msgid "" +"Ticket Last Contact Behaviour (default: ``Use the start time of the last " +"customer thread (which may consist of multiple articles).``)" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:2 +#: ../settings/ticket.rst:41 msgid "" -"Allows you to set the number of shown caller log entries for all users. You " -"can choose from the following values:" +"This setting changes the way Zammad updates the ``Last Contact`` value of a " +"ticket. This is fairly important for overviews and what you expect upon " +"ticket updates of a customer." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:5 -msgid "60 (default)" +#: ../settings/ticket.rst:52 +msgid "" +"Use the start time of the last customer thread (which may consist of " +"multiple articles)." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:6 -msgid "120" +#: ../settings/ticket.rst:46 +msgid "" +"If this option is chosen, Zammad will update the last updated value just " +"once if a customer replies. After that, Zammad will wait for an agent to " +"react." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:7 -msgid "180" +#: ../settings/ticket.rst:50 +msgid "" +"This comes in handy if you want to work tickets in the order of their first " +"update. This will not change ticket orders if customers decide to \"bump\" " +"the ticket affected." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:8 -msgid "240" +#: ../settings/ticket.rst:57 +msgid "Use the time of the very last customer article." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:9 -msgid "300" +#: ../settings/ticket.rst:55 +msgid "" +"When setting this option, Zammad will always update the last updated value. " +"This means that if ordering by ``Last Update``, ticket orders will change if " +"customers \"bump\" the ticket." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:11 -msgid "**🥵 Potential performance issue**" -msgstr "" - -#: ../system/integrations/cti/includes/records-caller-log.include.rst:13 -msgid "" -"Setting this setting higher than 60 may cause serious performance issues on " -"very busy instances. Keep in mind that this setting causes Zammad to poll " -"and send up to 300 records to *all active agent sessions* in very short time " -"periods." +#: ../settings/ticket.rst:64 +msgid "Last contact value used on :doc:`/manage/overviews`" msgstr "" -#: ../system/integrations/cti/generic.rst:73 -msgid "Caller Log Filter" +#: ../settings/ticket.rst:65 +msgid "Last contact value used on :doc:`/manage/trigger`" msgstr "" -#: ../system/integrations/cti/generic.rst:55 +#: ../settings/ticket.rst:88 msgid "" -"This function allows you to provide call information based on e.g. queues " -"only to agents that really need the information." +"Ticket Organization Reassignment (default: ``Update the most recent tickets." +"``)" msgstr "" -#: ../system/integrations/cti/generic.rst:58 +#: ../settings/ticket.rst:68 msgid "" -"Why? If you have a team for several countries or departments, you don't want " -"to bug your agents from other departments. Leaving these options empty will " -"fallback to showing everything to everyone." +"This setting changes the way Zammad updates the organization field of the " +"tickets whenever the primary organization of a user is changed." msgstr "" -#: ../system/integrations/cti/generic.rst:64 -msgid "Destination caller ID or Queue" +#: ../settings/ticket.rst:74 +msgid "Update the most recent tickets." msgstr "" -#: ../system/integrations/cti/generic.rst:63 +#: ../settings/ticket.rst:72 msgid "" -"This depends on your PBX and usually is either a queue ID, phone number or " -"extension." +"If this option is chosen, Zammad will update the 100 most recent tickets " +"where the user is the ticket customer. The ticket organization field will be " +"automatically set to the new primary organization of the user." msgstr "" -#: ../system/integrations/cti/generic.rst:69 -msgid "Agents" +#: ../settings/ticket.rst:88 +msgid "Do not update any tickets." msgstr "" -#: ../system/integrations/cti/generic.rst:67 +#: ../settings/ticket.rst:77 msgid "" -"Select the agents that are responsible for the group. These agents will then " -"see caller log entries and call notifications fitting to said queue." +"When choosing this option, Zammad will not update any tickets when the " +"user's primary organization is changed." msgstr "" -#: ../system/integrations/cti/generic.rst:0 -msgid "" -"Screenshot showing the caller log filter table with pre filled sample data" +#: ../settings/ticket.rst:80 +msgid "**Use with care!**" msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:6 +#: ../settings/ticket.rst:82 msgid "" -"With recent logs Zammad allows you to view the latest calls for the CTI " -"functionality. This usually comes in handy, when you're looking for errors." +"Using this option may lead to inconsistencies in the system as the ticket " +"organization may become decoupled from the ticket customer." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:0 +#: ../settings/ticket.rst:85 msgid "" -"Screenshot showing several incoming requests within Recent logs section." +"However, you may use this option if you wish to maintain :ref:`the shared " +"access ` to the ticket for all organization " +"members of the original organization of the customer." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:16 -msgid "I'm just here to clear floats up." +#: ../settings/ticket.rst:110 +msgid "Ticket Number Format (default: ``Increment (SystemID.Counter)``)" msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:20 +#: ../settings/ticket.rst:94 msgid "" -"By clicking on the entry of interest, Zammad will provide more details on " -"the call in question. You'll see the payload it received and also the " -"response that was sent." +"This setting defines the way Zammad's ticket number will look. Changing this " +"setting in production will cause follow up detection to fail." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:0 +#: ../settings/ticket.rst:102 +msgid "Increment (SystemID.Counter)" +msgstr "" + +#: ../settings/ticket.rst:98 msgid "" -"Screenshot showing detailed information of a specific log entry of recent " -"logs" +"The increment value contains the SystemID (automatically generated during " +"installation) and a increment which counts up with every new Ticket. The " +"increment will automatically get another digit if needed." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:31 -msgid "x" +#: ../settings/ticket.rst:102 +msgid "Examples: ``1010138``, ``1010139``" msgstr "" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 -#: ../system/integrations/cti/includes/troubleshooting.include.rst:9 -msgid "My Phone page stays blank, signalling does work..." +#: ../settings/ticket.rst:110 +msgid "Date (Year.Month.Day.SystemID.Counter)" msgstr "" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:5 +#: ../settings/ticket.rst:105 msgid "" -"If you've made sure that signalling works (check Recent logs) and your " -"Caller Log still stays empty, please ensure that you only configured one CTI " -"integration version. Specifically defining more than one agent mapping on " -"the different integration variants will be the issue." +"This version of the ticket number is fairly long. However, because it " +"contains the date of ticket creation, it also allows you to see when the " +"ticket has been created. You may feel familiar with this number format if " +"you've worked with OTRS already." msgstr "" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 -msgid "Clear the not needed agent mapping and reload your browser page." +#: ../settings/ticket.rst:110 +msgid "Examples: ``201206231010138``, ``201206231010139``" msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:1 -msgid "" -"By mapping your agents extension to their existing Zammad users, Zammad can " -"provide a new ticket dialog or open the user profile for the agent that " -"picks up the call." +#: ../settings/ticket.rst:137 +msgid "OPTIONS" msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:5 +#: ../settings/ticket.rst:113 msgid "" -"This speeds up ticket aiding, no matter if it's for existing tickets or new " -"ones!" +"The below options allow you to further customize your ticket number. The " +"availability of options differ depending of the chosen ticket number format " +"above." msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:8 +#: ../settings/ticket.rst:122 +msgid "Checksum (default: ``no``)" +msgstr "" + +#: ../settings/ticket.rst:118 msgid "" -"To see it work from the agent's perspective, have a look on :user-docs:`user " -"documentation `." +"If set to yes, we'll built a checksum to further \"unique\" the ticket " +"number of your system. If you're dealing with many other ticket systems this " +"might help to prevent false positive follow up detection on tickets." msgstr "" -#: ../system/integrations/cti/placetel.rst:2 -msgid "Placetel CTI" +#: ../settings/ticket.rst:122 +msgid "This will also add another digit to the ticket number." msgstr "" -#: ../system/integrations/cti/placetel.rst:16 -msgid "You need an administrative Placetel account for your organization." +#: ../settings/ticket.rst:137 +msgid "Min. size of Number (default: ``5``)" msgstr "" -#: ../system/integrations/cti/placetel.rst:17 -#: ../system/integrations/cti/sipgate.rst:20 +#: ../settings/ticket.rst:125 msgid "" -"Your Zammad instance must be allowed to communicate to external services." +"This setting defines the minimum length of your ticket number. If your " +"counter is not yet high enough, Zammad will fill the number with zeros to " +"ensure the wanted length." msgstr "" -#: ../system/integrations/cti/placetel.rst:18 -msgid "Placetel must be able to reach your Zammad instance." +#: ../settings/ticket.rst:129 +msgid "" +"Please note that the minimum length is ``3`` (SystemID + at least one digit " +"if below 10). Also, if the length is no longer long enough, the number will " +"automatically get one digit longer. Ticket-Numbers **do not overflow**, thus " +"it's save to keep it at 5 or set it lower if wanted." msgstr "" -#: ../system/integrations/cti/placetel.rst:22 -msgid ":doc:`provider-configurations/placetel`" +#: ../settings/ticket.rst:135 +msgid "" +"This option is only available if ticket number format is set to " +"``Increment``!" msgstr "" -#: ../system/integrations/cti/placetel.rst:21 -msgid "" -"Learn how to configure Placetel to enable Zammad and Placetel to communicate " -"with each other." +#: ../settings/ticket.rst:142 +msgid "Auto-Assignment" msgstr "" -#: ../system/integrations/cti/placetel.rst:32 +#: ../settings/ticket.rst:144 msgid "" -"The here listed endpoint settings are relevant for the :doc:`integration " -"configuration with Placetel `." +"In a larger Zammad environment, it happens that several agents open the same " +"ticket at the same time. Although collision detection is then effective, the " +"efficiency of processing can be increased by means of the automatic " +"assignment of tickets when a ticket is opened." msgstr "" -#: ../system/integrations/cti/placetel.rst:37 -#: ../system/integrations/i-doit.rst:53 -msgid "Endpoint" +#: ../settings/ticket.rst:149 +msgid "" +"The automatic assignment of tickets can be activated and configured in the " +"admin area under Settings > Ticket > Auto Assignment." msgstr "" -#: ../system/integrations/cti/placetel.rst:36 +#: ../settings/ticket.rst:152 msgid "" -"This endpoint will be required for the Zammad integration within the " -"Placetel web interface." +"The auto assignment only works if the ticket has no owner yet. By default, " +"the agent can always reset the ticket owner to ``-`` if needed." msgstr "" -#: ../system/integrations/cti/placetel.rst:41 -msgid "API Token" +#: ../settings/ticket.rst:155 +msgid "" +"If you want to use this function for only specific tickets, you can " +"configure the conditions accordingly to meet your requirement. By default " +"the condition affects all tickets with the state ``open``." msgstr "" -#: ../system/integrations/cti/placetel.rst:40 +#: ../settings/ticket.rst:161 msgid "" -"You'll receive this token within the ``Web API`` menu. Make sure to copy " -"this value, it's only shown once!" +"If you need to exclude users (e.g. a group leader), you can search and " +"select the desired agents in the ``Exception Users`` list. The search " +"function in this area is only effective, if you have too many agents to " +"display at once to help you with the configuration." msgstr "" -#: ../system/integrations/cti/placetel.rst:71 -#: ../system/integrations/cti/sipgate.rst:77 -msgid "Phone Extension to Agent Mapping" -msgstr "" +#: ../settings/ticket.rst:167 +#, fuzzy +msgid "Notifications" +msgstr "Intégrations" -#: ../system/integrations/cti/placetel.rst:0 -msgid "Screenshot showing sample user mappings in between Placetel and Zammad" -msgstr "" +#: ../settings/ticket.rst:191 +#, fuzzy +msgid "Default Notifications" +msgstr "Intégrations" -#: ../system/integrations/cti/placetel.rst:64 +#: ../settings/ticket.rst:170 msgid "" -"You can find your agents Placetel username combination required within ⚙️ PBX " -"→ VoIP destinations. Within the \"Advanced settings\" section you're looking " -"for \"SIP user name\" and \"SIP server\"." +"This setting allows you to configure the default ticket notifications that " +"will be applied to all new agent users (incl. users who were just assigned " +"agent role). Simply change the notification matrix to desired state and " +"press **Save**." msgstr "" -#: ../system/integrations/cti/placetel.rst:68 -msgid "Combine these two like so: ``@``." +#: ../settings/ticket.rst:175 +msgid "" +"In case an agent already exists, their ticket notification preferences will " +"be preserved. Optionally, you can also **Apply current defaults to all " +"agents**." msgstr "" -#: ../system/integrations/cti/placetel.rst:0 -msgid "Sample VoIP credentials for a Placetel user" +#: ../settings/ticket.rst:181 +msgid "" +"**Potential time-consuming action:** Applying default ticket notifications " +"to all agent users may take some time to complete, be patient! The exact " +"time will depend on the size of your system and the number of agents." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:2 -msgid "Setup Placetel connection for Zammad" +#: ../settings/ticket.rst:185 +msgid "" +"**Active agents only!** When current default ticket notifications are " +"applied, only active agent users are considered. In case an agent is re-" +"activated *after* this action, they will still have the old notification " +"configuration." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:6 +#: ../settings/ticket.rst:190 msgid "" -"This configuration step requires a *full* administrative Placetel account. " -"You may receive forbidden error messages with Placetel in case your " -"permissions are not high enough." +"In case you want to go back to the initial state of ticket notifications, " +"you can click on **Reset to default** button." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:10 -msgid "" -"The following actions can be configured via the `Placetel web interface " -"`_." +#: ../settings/ticket.rst:196 +msgid "Duplicate Detection" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:29 -msgid "Step 1: Activate Zammad integration" +#: ../settings/ticket.rst:238 +msgid "Detect Duplicate Ticket Creation" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:14 +#: ../settings/ticket.rst:199 msgid "" -"Within Integrations, scroll down to Partner integrations and select Zammad." +"This setting turns on the duplicate ticket detection mechanism during ticket " +"creation. If similar tickets are found in the system, a suitable warning " +"will be shown to the user trying to create a ticket." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:17 -msgid "" -"You can alternatively filter by \"Ticket Systems\" to reduce the number of " -"entries on the page. You'll still want to look for Partner integrations. 🤓" +#: ../settings/ticket.rst:206 +msgid "A Sample Duplicate Ticket Warning" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:21 +#: ../settings/ticket.rst:208 msgid "" -"Within the Zammad integration now press \"Activate\". A new tab ``API`` " -"becomes available - open this tab." +"You can choose which ticket attributes will be matched by selecting them in " +"**Attributes to compare** field. Only if the ticket attribute value provided " +"by the user in the ticket create form is *equal* with the attribute in an " +"existing ticket, the warning will be shown." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:24 -msgid "" -"Now tick \"Enable Call Control / Notify API\" and paste the Placetel " -"endpoint from your Zammad instance into the field \"URL of your API " -"endpoint\". Save to apply the settings" +#: ../settings/ticket.rst:213 +msgid "**Warning title** and **Warning message** are configurable as well." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 -msgid "Screencast showing how to activate the Zammad integration" +#: ../settings/ticket.rst:215 +msgid "" +"You can limit the detection only to certain user roles. By default, only " +"agents will see the warning." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:51 -msgid "Step 2: Generate API Token for Placetel" +#: ../settings/ticket.rst:218 +msgid "" +"If you don't want to show the matched tickets as part of the warning, you " +"can set **Show matching ticket(s) in the warning** setting to *no*." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:32 +#: ../settings/ticket.rst:221 msgid "" -"Go back to the integrations page and scroll down to \"Web API\". Generate a " -"new API token by using the \"Create a new API token\" button." +"By default, **Permission level for looking up ticket** is set to *User*, " +"which means user permissions will be honored during sarch. The user will " +"see the warning only if tickets they have access to are matched. " +"Alternatively, you can set this setting to *System*, in which case the " +"search will happen within *all* tickets in the system, regardless of user " +"permissions." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:37 -msgid "" -"If you already generated a token either use your existing token or reset it " -"by using above mentioned button. Placetel will ask you to conform this reset." +#: ../settings/ticket.rst:227 +msgid "**🦺 Safety first!**" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:41 +#: ../settings/ticket.rst:229 msgid "" -"Please keep in mind that existing API scripts may no longer work due to " -"token resets!" +"Even if the permission level is set to *System*, the user will not be shown " +"the tickets they don't have access to in the warning, even if they match." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:44 +#: ../settings/ticket.rst:233 msgid "" -"Copy the provided API token and insert it into the \"API Token\" field " -"within Zammad's Placetel integration." +"However, just the confirmation about the existence of the tickets in the " +"system may be considered an unwanted information disclosure. Use this option " +"carefully!" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:47 +#: ../settings/ticket.rst:237 msgid "" -"Apply your changes by using the \"Save\" button on the bottom of the " -"Placetel integration page and activate the Placetel integration." +"Finally, you can configure between matching within **All tickets** or **Open " +"tickets** only by setting **Match tickets in following states**. Depending " +"on the current ticket state, a ticket may or not be matched." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +#: ../system/core-workflows.rst:2 +msgid "Core Workflows" +msgstr "Flux de travail principaux" + +#: ../system/core-workflows.rst:4 msgid "" -"Screencast showing how to retrieve an API token from Placetel for Zammad" +"Core Workflows allow you to adjust object attributes in many ways. For " +"example:" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:73 -#: ../system/integrations/cti/provider-configurations/sipgate.rst:77 -msgid "Step 3: Restrict the numbers to notify on" +#: ../system/core-workflows.rst:7 +msgid "show / hide fields" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:54 -msgid "" -"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " -"the the Integrations page of the Placetel web interface, go to \"Notify " -"API\"." +#: ../system/core-workflows.rst:8 +msgid "adjust mandatory setting" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:58 +#: ../system/core-workflows.rst:9 +msgid "manipulate available options" +msgstr "" + +#: ../system/core-workflows.rst:11 msgid "" -"Lower on the page Placetel allows you to restrict the numbers to notify on. " -"You'll find this within the \"External routing API\" part." +"With this, you can provide exactly the information your users really need!" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +#: ../system/core-workflows.rst:15 msgid "" -"Screenshot showing a sample selection of phone numbers to use for the " -"Placetels notify API" +"If the pre-defined :doc:`/system/objects` are not enough, please add them " +"beforehand." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:66 +#: ../system/core-workflows.rst:17 msgid "" -"This menu point also provides a API request log from Placetel view. Just " -"open \"Recent responses of your API endpoint\" to learn more." +"If you experience slow or unreliable field updates, please see :ref:`Core " +"Workflow Ajax Modus `" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:69 +#: ../system/core-workflows.rst:22 msgid "" -"If you want to see Zammad's perspective, use the \"Recent Logs\" part from " -"within the Placetel integration page." +"This is a very enhanced functionality and can cause unexpected UI behavior. " +"Please ensure to test your use cases after configuration to reduce surprises." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 -msgid "Screenshot showing sample log entries for Placetels API calls to Zammad" +#: ../system/core-workflows.rst:None +msgid "Dialogue for adding a new workflow" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:77 -msgid "Step 4 (optional): Further configurations for Placetel" +#: ../system/core-workflows/condition-operators.rst:2 +msgid "Core Workflow Condition Operators" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:76 +#: ../system/core-workflows/condition-operators.rst:4 msgid "" -"If needed, you can now configure Zammad's Placetel integration in more " -"detail. You can learn more about your options here: :ref:`Placetel " -"integration settings `." +"You might know that there is a separate section for explaining :doc:" +"`condition operators `. Head over there to " +"see a detailed explanation of many conditions and operators." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:2 -msgid "Setup Sipgate connection for Zammad" +#: ../system/core-workflows/condition-operators.rst:8 +msgid "" +"Due to differences to other places in Zammad which are also using conditions " +"(e.g. triggers), you can find a dedicated description of operators for core " +"workflows below." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +#: ../system/core-workflows/condition-operators.rst:12 msgid "" -"Sipgate has no english web interface which is why this documentation page is " -"mixing up languages badly." +"Be aware that the availability of the operators depends on the selected " +"attribute and its field type. Some of the operators may only be available " +"for system attributes (e.g. for \"tags\", \"active\")." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Please also note that the availability of API addons highly depends on your " -"package trier. Usage of sipgate.io packages *is not free*, please check " -"their `pricing page `_ before!" +#: ../system/core-workflows/condition-operators.rst:20 +msgid "Operator" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:35 -msgid "Step 1: Book sipgate.io package" +#: ../system/core-workflows/condition-operators.rst:22 +msgid "after (absolute)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:13 -msgid "Skip to step 2 if you already have the package booked!" +#: ../system/core-workflows/condition-operators.rst:23 +msgid "Matches if a date/time is after a specific point in time." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:15 -msgid "" -"Login to an administrative Sipgate account and navigate to " -"``Accountverwaltung``. You'll see several different options depending on " -"your booked packages. Select ``Verträge & Produkte`` to continue." +#: ../system/core-workflows/condition-operators.rst:24 +msgid "after (relative)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:19 -msgid "" -"Scroll down to the section ``Zusätzliche Produkte buchen`` and look for " -"``sipgate.io`` - select this product by using the ``Produkte anzeigen``-" -"Button." +#: ../system/core-workflows/condition-operators.rst:25 +msgid "Matches if a time span after a specified event has passed." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:23 -msgid "" -"On the next page select either one of the ``sipgate.io`` packages or ``Push-" -"API Package Free``. Follow the dialogue by booking the addon. You'll be " -"returned to your contract overview and now should see the selected addon in " -"your list." +#: ../system/core-workflows/condition-operators.rst:26 +msgid "before (absolute)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:30 -msgid "" -"The availability for ``sipgate.io`` packages and their levels highly depends " -"on the overall account type and product you've booked with Sipgate." +#: ../system/core-workflows/condition-operators.rst:27 +msgid "Matches if a date/time is before a specific point in time." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screencast showing the process on how to book the required sipgate.io addon" +#: ../system/core-workflows/condition-operators.rst:28 +msgid "before (relative)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:52 -msgid "Step 2: Configure webhook for Zammad" +#: ../system/core-workflows/condition-operators.rst:29 +msgid "Matches if a time span after a specified event has not passed." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:38 -msgid "" -"Within your ``Accountverwaltung`` navicate to your product ``sipgate.io``. " -"In the newly opened tab, switch from \"Clients\" to \"Webhooks\" and paste " -"the endpoint URLs from your Zammad instance like so:" +#: ../system/core-workflows/condition-operators.rst:30 +msgid "contains" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:42 -msgid "Inbound endpoint to \"Incoming\"" +#: ../system/core-workflows/condition-operators.rst:31 +msgid "Matches if a specified value is present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:43 -msgid "Outbound endpoint to \"Outgoing\"" +#: ../system/core-workflows/condition-operators.rst:33 +msgid "Matches if all of the specified values are present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:47 -msgid "" -"Ensure to select at least one call group or phoneline within \"Sources\". " -"Other wise Sipgate will not indicate any incoming or outgoing calls to " -"Zammad." +#: ../system/core-workflows/condition-operators.rst:35 +msgid "Matches if none of the specified values are present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screencast showing how to add Zammad's endpoint URLs to sipgate.ios webhook " -"configuration" +#: ../system/core-workflows/condition-operators.rst:36 +msgid "contains not" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:55 -msgid "" -"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " -"the Webhooks → URLs section of Sipgate you can select which *sources* " -"Sipgate should notify Zammad about in- and outgoing calls." +#: ../system/core-workflows/condition-operators.rst:37 +msgid "Matches if a specified value is not present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:59 -msgid "" -"Use either specific phone lines or use the option \"Use for all phonelines " -"and groups\" to notify Zammad about all existing lines of your Sipgate " -"account." +#: ../system/core-workflows/condition-operators.rst:39 +msgid "Matches if one specified value is present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screenshot showing a sample selection of phone numbers to use for the " -"Sipgates webhooks API" +#: ../system/core-workflows/condition-operators.rst:41 +msgid "Matches if one specified value is not present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:68 -msgid "This section also allows you to enable a Debug log." -msgstr "" - -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "Screenshot showing an enabled Debug log option" -msgstr "" - -#: ../system/integrations/cti/provider-configurations/sipgate.rst:73 -msgid "" -"After enabling you can use the Debug log section to see all sent webhook " -"calls to Zammad. You'll also can see the response." +#: ../system/core-workflows/condition-operators.rst:42 +msgid "does not match regex" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screenshot showing sample log entries for Sipgates webhook calls to Zammad" +#: ../system/core-workflows/condition-operators.rst:43 +msgid "Matches if content doesn't fit to regex rule." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:81 -msgid "Step 4 (optional): Further configurations for Sipgate" +#: ../system/core-workflows/condition-operators.rst:44 +msgid "ends with" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:80 -msgid "" -"If needed, you can now configure Zammad's Sipgate integration in more " -"detail. You can learn more about your options here: :ref:`Sipgate " -"integration settings `." +#: ../system/core-workflows/condition-operators.rst:45 +msgid "Matches if content ends with specified value." msgstr "" -#: ../system/integrations/cti/sipgate.rst:2 -msgid "Sipgate (sipgate.io)" +#: ../system/core-workflows/condition-operators.rst:46 +msgid "ends with one of" msgstr "" -#: ../system/integrations/cti/sipgate.rst:16 -msgid "You need an administrative Sipgate account for your organization." +#: ../system/core-workflows/condition-operators.rst:47 +msgid "Matches if content ends with one of the specified values." msgstr "" -#: ../system/integrations/cti/sipgate.rst:17 -msgid "" -"Zammad requires a ``sipgate.io`` addon from the feature store (please note " -"that API calls are not free with Sipgate. Rates may apply and differ from " -"account to account)." +#: ../system/core-workflows/condition-operators.rst:48 +msgid "from (relative)" msgstr "" -#: ../system/integrations/cti/sipgate.rst:21 -msgid "Sipgate must be able to reach your Zammad instance." +#: ../system/core-workflows/condition-operators.rst:49 +msgid "Matches if date/time is after a period of time after an event." msgstr "" -#: ../system/integrations/cti/sipgate.rst:25 -msgid ":doc:`provider-configurations/sipgate`" +#: ../system/core-workflows/condition-operators.rst:51 +msgid "Matches if content is equal to a specified value." msgstr "" -#: ../system/integrations/cti/sipgate.rst:24 -msgid "" -"Learn how to configure Sipgate to enable Zammad and Sipgate to communicate " -"with each other." +#: ../system/core-workflows/condition-operators.rst:52 +msgid "is any of" msgstr "" -#: ../system/integrations/cti/sipgate.rst:33 -msgid "" -"Below endpoint settings affect the :doc:`sipgate.io configuration `." +#: ../system/core-workflows/condition-operators.rst:53 +msgid "Matches if content is equal to any of specified values." msgstr "" -#: ../system/integrations/cti/sipgate.rst:37 -msgid "This endpoint is required for incoming call hooks." +#: ../system/core-workflows/condition-operators.rst:54 +msgid "is modified" msgstr "" -#: ../system/integrations/cti/sipgate.rst:40 -msgid "This endpoint is required for outgoing call hooks." +#: ../system/core-workflows/condition-operators.rst:55 +msgid "Matches if content is modified." msgstr "" -#: ../system/integrations/cti/sipgate.rst:0 -msgid "Screenshot showing sample user mappings in between Sipgate and Zammad" +#: ../system/core-workflows/condition-operators.rst:57 +#: ../system/core-workflows/condition-operators.rst:61 +msgid "True from the moment of changing content until form submit." msgstr "" -#: ../system/integrations/cti/sipgate.rst:69 -msgid "" -"You can find your agent's Sipgate username within ``Accountverwaltung → " -"Benutzer``. You're looking for the SIP-ID." +#: ../system/core-workflows/condition-operators.rst:58 +msgid "is modified to" msgstr "" -#: ../system/integrations/cti/sipgate.rst:0 -msgid "Sample VoIP credentials for a Sipgate user" +#: ../system/core-workflows/condition-operators.rst:59 +msgid "Matches if content is modified to a specific value." msgstr "" -#: ../system/integrations/cti/sipgate.rst:77 -msgid "Users with several devices also have several SIP-IDs." +#: ../system/core-workflows/condition-operators.rst:62 +msgid "is none of" msgstr "" -#: ../system/integrations/elasticsearch.rst:2 -msgid "Elasticsearch (SaaS)" +#: ../system/core-workflows/condition-operators.rst:63 +msgid "Matches if content is none of any specified values." msgstr "" -#: ../system/integrations/elasticsearch.rst:4 -msgid "" -"The Elasticsearch integration allows you to create a read-only user to use " -"with your favorite reporting tool (e.g. like Grafana)." +#: ../system/core-workflows/condition-operators.rst:65 +msgid "Matches if content is not equal to a specified value." msgstr "" -#: ../system/integrations/elasticsearch.rst:7 -msgid "" -"If you want to take full advantage of the Zammad reporting, have a look at " -"our :docs:`Grafana ` " -"setup page as well." +#: ../system/core-workflows/condition-operators.rst:67 +msgid "Matches if content is present." msgstr "" -#: ../system/integrations/elasticsearch.rst:11 -#: ../system/subscription/index.rst:7 -msgid "**🚧 Hosted environment specific 🚧**" +#: ../system/core-workflows/condition-operators.rst:68 +msgid "just changed" msgstr "" -#: ../system/integrations/elasticsearch.rst:13 -msgid "" -"This integration is only available for Hosted setups. In order to use " -"Elasticsearch you'll need the **Plus** subscription." +#: ../system/core-workflows/condition-operators.rst:69 +msgid "Matches if content has changed." msgstr "" -#: ../system/integrations/elasticsearch.rst:16 +#: ../system/core-workflows/condition-operators.rst:71 +#: ../system/core-workflows/condition-operators.rst:75 msgid "" -"Self hosted users have all the control over their self hosted Elasticsearch " -"instances." +"Only true for the moment of changing content until next form field action/" +"click." msgstr "" -#: ../system/integrations/elasticsearch.rst:None -msgid "Elasticsearch integration page on SaaS environments" +#: ../system/core-workflows/condition-operators.rst:72 +msgid "just changed to" msgstr "" -#: ../system/integrations/elasticsearch.rst:27 -msgid "" -"Please note the following limitations of Elasticsearch access on hosted " -"environments:" +#: ../system/core-workflows/condition-operators.rst:73 +msgid "Matches if content has changed to a specified value." msgstr "" -#: ../system/integrations/elasticsearch.rst:30 -msgid "access to the Elasticsearch index is read-only access" +#: ../system/core-workflows/condition-operators.rst:76 +msgid "matches regex" msgstr "" -#: ../system/integrations/elasticsearch.rst:31 -msgid "currently you're limited to user only" +#: ../system/core-workflows/condition-operators.rst:77 +msgid "Matches if value fits to regex rule." msgstr "" -#: ../system/integrations/elasticsearch.rst:32 -msgid "" -"Reporting tools that require to write into the indexes (like Kibana) are not " -"supported" +#: ../system/core-workflows/condition-operators.rst:79 +msgid "Matches if no content is present." msgstr "" -#: ../system/integrations/elasticsearch.rst:34 -msgid "IP access restriction is currently not yet supported" +#: ../system/core-workflows/condition-operators.rst:80 +msgid "starts with" msgstr "" -#: ../system/integrations/elasticsearch.rst:37 -msgid "Activating Elasticsearch Access" +#: ../system/core-workflows/condition-operators.rst:81 +msgid "Matches if content starts with specified value." msgstr "" -#: ../system/integrations/elasticsearch.rst:39 -msgid "" -"By default external access to your Elasticsearch index is not active. You " -"can enable the integration at any time if needed." +#: ../system/core-workflows/condition-operators.rst:82 +msgid "starts with one of" msgstr "" -#: ../system/integrations/elasticsearch.rst:42 -msgid "" -"Please ensure to note down the password provided - you won't have access to " -"it afterwards." +#: ../system/core-workflows/condition-operators.rst:83 +msgid "Matches if content starts with one of the specified values." msgstr "" -#: ../system/integrations/elasticsearch.rst:None -msgid "Screencast showing activation of Elasticsearch integration" +#: ../system/core-workflows/condition-operators.rst:84 +msgid "till (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:51 -msgid "Connection Settings" +#: ../system/core-workflows/condition-operators.rst:85 +msgid "Matches if date/time is before a period of time before an event." msgstr "" -#: ../system/integrations/elasticsearch.rst:53 -msgid "" -"This section holds the most important general information for accessing your " -"Elasticsearch indexes - such as:" +#: ../system/core-workflows/condition-operators.rst:86 +msgid "today" msgstr "" -#: ../system/integrations/elasticsearch.rst:57 -msgid "A unique subdomain that does not tell your real instance URL." +#: ../system/core-workflows/condition-operators.rst:87 +msgid "Matches if date/time is today." msgstr "" -#: ../system/integrations/elasticsearch.rst:61 -msgid "Software" +#: ../system/core-workflows/condition-operators.rst:88 +msgid "within last (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:60 +#: ../system/core-workflows/condition-operators.rst:89 msgid "" -"The major version of the search index being used. This is required by some " -"Reporting tools like Grafana." +"Matches if date/time content is within specified period of time before now." msgstr "" -#: ../system/integrations/elasticsearch.rst:64 -msgid "Authentication" +#: ../system/core-workflows/condition-operators.rst:91 +msgid "within next (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:64 -msgid "The authentication type being supported. ``Basic Authentication``" +#: ../system/core-workflows/condition-operators.rst:92 +msgid "" +"Matches if date/time content is within specified period of time after now." msgstr "" -#: ../system/integrations/elasticsearch.rst:67 -msgid "Available Indexes" +#: ../system/core-workflows/how-do-they-work.rst:2 +msgid "How do they work?" msgstr "" -#: ../system/integrations/elasticsearch.rst:69 +#: ../system/core-workflows/how-do-they-work.rst:4 msgid "" -"Within this section we're displaying the -in our opinion- most important " -"indexes for a Zammad instance." +"Core Workflows are executed according to their priority. If two workflows " +"have the same priority, they are executed in alphabetical order based on " +"their **name**." msgstr "" -#: ../system/integrations/elasticsearch.rst:72 +#: ../system/core-workflows/how-do-they-work.rst:8 msgid "" -"If you require all indexes or our listing is not good enough for you, point " -"your browser to the URL we're providing and append ``/_aliases?" -"pretty=true``. The result should look like this: ``https://.zammad.com/" -"_aliases?pretty=true``." +"Because of the way Core Workflows work, all changes to attributes are " +"checked with the application server - please see :doc:`limitations` for " +"possible issues." msgstr "" -#: ../system/integrations/elasticsearch.rst:77 +#: ../system/core-workflows/how-do-they-work.rst:12 msgid "" -"Your browser will automatically ask for your credentials - you'll then see " -"something like this:" +"Below we're talking about settings that are important and not self-" +"explanatory." msgstr "" -#: ../system/integrations/elasticsearch.rst:125 -msgid "Credentials" +#: ../system/core-workflows/how-do-they-work.rst:17 +msgid "" +"Choose the object context you want to run the workflow in. This will decide " +"on your available attributes and actions." msgstr "" -#: ../system/integrations/elasticsearch.rst:127 -msgid "" -"Within this section Zammad displays your available users. The password is " -"provided once (upon activation) and cannot be retrieved after that." +#: ../system/core-workflows/how-do-they-work.rst:20 +msgid "Ticket objects also have access to the ticket customer." msgstr "" -#: ../system/integrations/elasticsearch.rst:131 +#: ../system/core-workflows/how-do-they-work.rst:25 msgid "" -"If you need to change or reset your Elasticsearch user password, use the " -"\"Reset password\" button in the credentials table. Doing so creates a brand " -"new password for the account in question. This change is immediate, keep in " -"mind that this may affect third party tools connected to your instance." +"Choose in which situation the workflow is applied. Contexts can be combined " +"to avoid duplicate workflows." msgstr "" -#: ../system/integrations/exchange.rst:2 -msgid "Exchange" +#: ../system/core-workflows/how-do-they-work.rst:30 +msgid "Creation mask" msgstr "" -#: ../system/integrations/exchange.rst:4 +#: ../system/core-workflows/how-do-they-work.rst:29 msgid "" -"With Zammad's Exchange integration, you can easily use existing address " -"books without having to update more than one source." +"If selected, your conditions and actions will affect all applicable creation " +"masks." msgstr "" -#: ../system/integrations/exchange.rst:7 -msgid "" -"However, you should refrain from syncing all addresses, as the results may " -"not be what you expect (Exchange collects huge amounts of addresses). A " -"central address book of your company to sync makes more sense, as you can " -"ensure that Zammad gets only the data you need and want. Apart from this, it " -"is even not possible to sync the Global Address List (GAL) of your Exchange " -"system with Zammad." +#: ../system/core-workflows/how-do-they-work.rst:34 +msgid "Edit mask" msgstr "" -#: ../system/integrations/exchange.rst:16 +#: ../system/core-workflows/how-do-they-work.rst:33 msgid "" -"**Exchange and LDAP:** The exchange sync can be overruled by Zammad's LDAP " -"integration. If you have the same users in both sources, the LDAP version " -"will always be Zammad's pick." +"If selected, your conditions and actions will affect all applicable edit " +"masks." msgstr "" -#: ../system/integrations/exchange.rst:19 +#: ../system/core-workflows/how-do-they-work.rst:39 msgid "" -"**One way sync:** the Exchange sync is one way. Exchange => Zammad. Changes " -"to your users inside of Zammad might be overwritten by the Exchange sync." +"Zammad differentiates between selected and saved conditions. These can be " +"combined wherever needed." msgstr "" -#: ../system/integrations/exchange.rst:24 -msgid "" -"To configure Exchange integration, simply go to the System > Integrations > " -"Exchange in the admin panel. Press \"change\" and follow the wizard for " -"adding the needed Exchange information to Zammad. On the last two steps " -"Zammad will ask you for the address book(s) and your desired attribute " -"mapping. By default, Zammad only maps email address, first- and lastname. " -"Technically, you can map any Exchange object to a Zammad user object (this " -"also works for custom objects!)." +#: ../system/core-workflows/how-do-they-work.rst:42 +msgid "**⚠️ Restrict workflows to specific roles if needed!**" msgstr "" -#: ../system/integrations/exchange.rst:35 +#: ../system/core-workflows/how-do-they-work.rst:44 msgid "" -"If the SSL verification fails while connecting to Exchange, Zammad will ask " -"you to turn it off temporarily." +"By default and unless configured in conditions, workflow rules are executed " +"for **all roles**. This also affects your customers!" msgstr "" -#: ../system/integrations/exchange.rst:38 -msgid "" -"Please be aware that **turning off SSL verification is a security risk**. It " -"should only be used temporarily or for testing purposes. If turned off, " -"there is no verification of the certificate, which means that every " -"presented certificate will be accepted." +#: ../system/core-workflows/how-do-they-work.rst:50 +msgid "Selected Conditions" msgstr "" -#: ../system/integrations/exchange.rst:43 +#: ../system/core-workflows/how-do-they-work.rst:48 msgid "" -"After pressing Continue, Zammad will check if the configuration is okay. You " -"can then enable Exchange and start your first sync. The sync will then run " -"hourly - if you need to change mappings or the address book(s), you can " -"change the configuration at any time." +"These conditions are based on form values and match if an appropriate " +"selection is made (e.g. choosing another group in the ticket without " +"saving). This applies for drafts (active selection) and currently saved " +"values." msgstr "" -#: ../system/integrations/exchange.rst:50 -msgid "" -"After the sync has finished, you can find the new Exchange contacts under " -"\"Users\". Zammad integrates them just as normal users." +#: ../system/core-workflows/how-do-they-work.rst:64 +msgid "Saved Conditions" msgstr "" -#: ../system/integrations/exchange.rst:55 +#: ../system/core-workflows/how-do-they-work.rst:53 msgid "" -"In some cases you might see unique IDs as \"Login\" instead of the email " -"address. This is normal and doesn't affect the login or email mapping for " -"that entry." +"These conditions only match if the selected values are stored in the " +"database. It ignores the current value or selection of the field, as long as " +"the changes are not saved (e.g. performing field operations for an existing " +"ticket, which is viewed/opened by an agent)." msgstr "" -#: ../system/integrations/github.rst:4 +#: ../system/core-workflows/how-do-they-work.rst:60 msgid "" -"Use GitHub integration to track GitHub issues directly within Zammad " -"tickets. Add issue hyperlinks and get a live summary of metadata like status " -"(open/closed), assignee, labels, and more." -msgstr "" - -#: ../system/integrations/github.rst:8 -msgid "Please note that our GitHub integration does not support pull requests." -msgstr "" - -#: ../system/integrations/github.rst:None -msgid "Integration page for GitHub" +"Keep in mind that the value has to be available in the situation where you " +"need it. Otherwise the condition won't match." msgstr "" -#: ../system/integrations/github.rst:18 +#: ../system/core-workflows/how-do-they-work.rst:63 msgid "" -"In your GitHub settings, create a new API token under **Developer settings > " -"Personal access tokens > Generate new token**. Leave the **Scopes** section " -"empty." +"Example: you can't perform any actions with *saved condition* on a ticket in " +"creation, because there are no saved values at that time." msgstr "" -#: ../system/integrations/github.rst:0 ../system/integrations/gitlab.rst:0 -msgid "Screencast showing how to create a new API token" +#: ../system/core-workflows/how-do-they-work.rst:66 +msgid "" +"You can find a description of the condition operators for core workflows :" +"doc:`here `." msgstr "" -#: ../system/integrations/github.rst:27 -msgid "Create a new API key with no scopes/privileges." +#: ../system/core-workflows/how-do-they-work.rst:72 +msgid "" +"Which actions should we run on the relevant fields? The possible actions " +"depend on the object type. However, usually you can at least change the " +"visibility and whether the field is mandatory." msgstr "" -#: ../system/integrations/github.rst:29 -msgid "🔒 **Will this work for private repos?**" +#: ../system/core-workflows/how-do-they-work.rst:76 +msgid "Be aware that actions are not available for **related** context." msgstr "" -#: ../system/integrations/github.rst:31 +#: ../system/core-workflows/how-do-they-work.rst:78 msgid "" -"No. To link private repo issues, **use the** ``repo`` **scope instead**. " -"Bear in mind that the resulting token will have `lots of permissions that it " -"doesn't actually need `_, which presents a security risk if your token ever falls into " -"the wrong hands." +"**Example:** Let's assume you are working in the ticket context. While you " +"can have customer *conditions*, you *can't adjust* objects with actions in " +"that scope. That's because this wouldn't have any impact on the ticket " +"dialog. Of course all ticket attributes (state, owner, ...) are available." msgstr "" -#: ../system/integrations/github.rst:37 +#: ../system/core-workflows/how-do-they-work.rst:84 msgid "" -"Unfortunately, because of how GitHub's OAuth token scopes are set up, this " -"is the only way to link issues on private repos." +"Please also have a look at our :doc:`limitations` to be safe from surprises." msgstr "" -#: ../system/integrations/github.rst:40 -msgid "Enter your new API token in Zammad and enable GitHub integration." +#: ../system/core-workflows/how-do-they-work.rst:88 +msgid "Available Operators" msgstr "" -#: ../system/integrations/github.rst:0 -msgid "Screencast showing how to configure Zammad's GitHub integration" +#: ../system/core-workflows/how-do-they-work.rst:90 +msgid "The availability of operators depends on the object type and scope." msgstr "" -#: ../system/integrations/github.rst:47 +#: ../system/core-workflows/how-do-they-work.rst:94 msgid "" -"Use the default API endpoint (``https://api.github.com/graphql``) unless " -"you're using GitHub Enterprise Server." +"Please note that actions may or may not restrict API based access to " +"attributes. We're displaying the following icons for your overview to " +"understand these limits better:" msgstr "" -#: ../system/integrations/github.rst:50 -msgid "" -"Once completed, a new GitHub issues tab will appear in the ticket pane. 🎉" +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|api| This icon indicates the action affects the API." msgstr "" -#: ../system/integrations/github.rst:59 ../system/integrations/gitlab.rst:52 -msgid "Token verification is taking a long time" +#: ../system/core-workflows/how-do-they-work.rst:163 +msgid "api" msgstr "" -#: ../system/integrations/github.rst:56 ../system/integrations/gitlab.rst:49 -msgid "" -"Slight delays are normal (<2 min.), especially for systems under heavy load." +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|ui| This icon indicates the action only affects the web interface." msgstr "" -#: ../system/integrations/github.rst:58 -msgid "" -"Self-hosted administrators, please check your network settings to ensure " -"that your Zammad server can reach ``api.github.com``." +#: ../system/core-workflows/how-do-they-work.rst:167 +msgid "ui" msgstr "" -#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 -msgid "I reloaded the page and now the API token is gone" +#: ../system/core-workflows/how-do-they-work.rst:102 +msgid "show |ui|" msgstr "" -#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 -msgid "" -"This may indicate that Zammad is still verifying your API token. Try " -"reloading the page again in a couple minutes." +#: ../system/core-workflows/how-do-they-work.rst:102 +msgid "Display the chosen field. Allows setting of values." msgstr "" -#: ../system/integrations/gitlab.rst:2 -msgid "GitLab" +#: ../system/core-workflows/how-do-they-work.rst:109 +msgid "hide |ui|" msgstr "" -#: ../system/integrations/gitlab.rst:4 +#: ../system/core-workflows/how-do-they-work.rst:105 msgid "" -"Use GitLab integration to track GitLab issues directly within Zammad " -"tickets. Add issue hyperlinks and get a live summary of metadata like status " -"(open/closed), assignee, labels, and more." +"Hide the chosen field. However, it technically still allows setting the " +"field." msgstr "" -#: ../system/integrations/gitlab.rst:8 +#: ../system/core-workflows/how-do-they-work.rst:108 msgid "" -"Please note that our GitLab integration does not support merge requests." +"Please note that the field is **not** gone and still contains an existing " +"value (if set)! Consider *remove* instead, if you want this field to be gone." msgstr "" -#: ../system/integrations/gitlab.rst:None -msgid "Integration page for GitLab" +#: ../system/core-workflows/how-do-they-work.rst:112 +msgid "remove |ui|" msgstr "" -#: ../system/integrations/gitlab.rst:18 -msgid "" -"In your GitLab preferences, create a new API token under **Access Tokens**." +#: ../system/core-workflows/how-do-they-work.rst:112 +msgid "Entirely removes the field. The field value will not be evaluated." msgstr "" -#: ../system/integrations/gitlab.rst:20 -msgid "Under **Select scopes**, choose ``read_api`` only." +#: ../system/core-workflows/how-do-they-work.rst:115 +msgid "set mandatory |ui| |api|" msgstr "" -#: ../system/integrations/gitlab.rst:27 -msgid "🔒 **If you wish to link issues on any private repos...**" +#: ../system/core-workflows/how-do-they-work.rst:115 +msgid "Sets the field to mandatory." msgstr "" -#: ../system/integrations/gitlab.rst:29 -msgid "Your API token must belong to an account with access to those repos." +#: ../system/core-workflows/how-do-they-work.rst:118 +msgid "set optional |ui| |api|" msgstr "" -#: ../system/integrations/gitlab.rst:31 -msgid "Enter your new API token in Zammad and enable GitLab integration." +#: ../system/core-workflows/how-do-they-work.rst:118 +msgid "Sets the field to optional." msgstr "" -#: ../system/integrations/gitlab.rst:0 -msgid "Screencast showing how to configure Zammad's GitLab integration" +#: ../system/core-workflows/how-do-they-work.rst:124 +msgid "add option |ui| |api|" msgstr "" -#: ../system/integrations/gitlab.rst:40 -msgid "" -"Use the default API endpoint (``https://gitlab.com/api/graphql``) unless " -"you're a self-hosted GitLab user." +#: ../system/core-workflows/how-do-they-work.rst:121 +msgid "Allows adding options to tree selects or selects." msgstr "" -#: ../system/integrations/gitlab.rst:43 +#: ../system/core-workflows/how-do-they-work.rst:123 msgid "" -"Once completed, a new GitLab issues tab will appear in the ticket pane. 🎉" +"You have to use the \"remove option\" before performing this action. It " +"allows you to use *existing* configured values." msgstr "" -#: ../system/integrations/gitlab.rst:51 +#: ../system/core-workflows/how-do-they-work.rst:128 +msgid "remove option |ui| |api|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:127 msgid "" -"Self-hosted administrators, please check your network settings to ensure " -"that your Zammad server can reach ``gitlab.com``." +"Allows removing options from tree selects or selects. It allows you to use " +"*existing* configured values." msgstr "" -#: ../system/integrations/i-doit.rst:2 -msgid "i-doit" +#: ../system/core-workflows/how-do-they-work.rst:134 +msgid "set fixed to |ui| |api|" msgstr "" -#: ../system/integrations/i-doit.rst:4 -msgid "" -"`i-doit `_ is an open-source **configuration " -"management database** - in other words, a tool for keeping tabs on every " -"single piece of your physical and digital infrastructure, from network " -"equipment to virtual machines on down to the faceplates on your rack shelves " -"and more." +#: ../system/core-workflows/how-do-they-work.rst:131 +msgid "Reduces the available options by your selection." msgstr "" -#: ../system/integrations/i-doit.rst:10 +#: ../system/core-workflows/how-do-they-work.rst:133 msgid "" -"What's that got to do with Zammad? Well, if you used tickets to track issues " -"with all that hardware, you might start wishing there was a way they could " -"talk to each other." -msgstr "" - -#: ../system/integrations/i-doit.rst:14 -msgid "Zammad gives you two:" +"This reduces your workflows in terms of *add option* and *remove option*." msgstr "" -#: ../system/integrations/i-doit.rst:17 -msgid "1. Add i-doit Links to Zammad Tickets" +#: ../system/core-workflows/how-do-they-work.rst:137 +msgid "fill in |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:20 ../system/integrations/i-doit.rst:80 -msgid "What Users See" +#: ../system/core-workflows/how-do-they-work.rst:137 +msgid "Allows filling in of string and integer fields with your values." msgstr "" -#: ../system/integrations/i-doit.rst:26 -msgid "i-doit integration in Zammad's ticket pane" +#: ../system/core-workflows/how-do-they-work.rst:141 +msgid "fill in empty |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:26 +#: ../system/core-workflows/how-do-they-work.rst:140 msgid "" -"The i-doit integration will appear under a new 🖨 tab in the ticket pane." +"Allows filling in of string and integer fields with your values **if the " +"field is empty**." msgstr "" -#: ../system/integrations/i-doit.rst:28 -msgid "" -"i-doit integration puts a new tab in Zammad's ticket pane where you can add " -"links to existing i-doit devices for easy reference. (See our :user-docs:" -"`user documentation ` to learn " -"how it works in practice)." +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "select |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:36 ../system/integrations/i-doit.rst:93 -msgid "How to Set it Up" +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "Select a specific value within a select, tree select or boolean field." msgstr "" -#: ../system/integrations/i-doit.rst:38 -msgid "" -"It requires i-doit's `API Add-on `_. Make sure to have it properly set up. Use the following setting:" +#: ../system/core-workflows/how-do-they-work.rst:153 +msgid "auto select |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:42 -msgid "Active: ``Yes``" +#: ../system/core-workflows/how-do-they-work.rst:147 +msgid "Helps users with tree select and select fields:" msgstr "" -#: ../system/integrations/i-doit.rst:43 -msgid "Enforce authentication by username and password: ``No``" +#: ../system/core-workflows/how-do-they-work.rst:149 +msgid "" +"If the field has only one option available for selection and no value yet, " +"the value will be automatically set." msgstr "" -#: ../system/integrations/i-doit.rst:45 +#: ../system/core-workflows/how-do-they-work.rst:152 msgid "" -"To set it up, enable the integration in the Zammad admin panel under " -"**System > Integrations > i-doit**:" +"This option only works if you have one value and doesn't work if there is " +"more than one option available." msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "i-doit settings within the integration pages" +#: ../system/core-workflows/how-do-they-work.rst:157 +msgid "set readonly |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:53 -msgid "The root URL of your i-doit installation." +#: ../system/core-workflows/how-do-they-work.rst:156 +msgid "" +"Allows you to display an attribute as read only (which means no changes are " +"possible)." msgstr "" -#: ../system/integrations/i-doit.rst:62 -msgid "API token" +#: ../system/core-workflows/how-do-they-work.rst:161 +msgid "unset readonly |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:56 +#: ../system/core-workflows/how-do-they-work.rst:160 msgid "" -"Found in the i-doit admin panel under **Interfaces / external data > JSON-" -"RPC API > Common Settings**." +"In case a workflow set the field in question to read only, you can undo this " +"with option above." msgstr "" -#: ../system/integrations/i-doit.rst:0 -msgid "i-doit administration interface with API configuration" +#: ../system/core-workflows/how-do-they-work.rst:172 +msgid "Stop after match" msgstr "" -#: ../system/integrations/i-doit.rst:67 -msgid "Client ID" +#: ../system/core-workflows/how-do-they-work.rst:174 +msgid "" +"Here you can decide if other workflows are executed after the current one." msgstr "" -#: ../system/integrations/i-doit.rst:65 -msgid "A unique name to identify Zammad within i-doit." +#: ../system/core-workflows/how-do-they-work.rst:176 +msgid "" +"If set to ``no`` (default), further workflows will be executed if they match " +"the condition. In this case, it is possible that your actions from the " +"current workflow can be overwritten by another workflow." msgstr "" -#: ../system/integrations/i-doit.rst:67 -msgid "(Zammad does not require you to enter a value here, but i-doit might!)" +#: ../system/core-workflows/how-do-they-work.rst:180 +msgid "" +"If set to ``yes``, no further worflows will be executed after the current " +"one." msgstr "" -#: ../system/integrations/i-doit.rst:70 +#: ../system/core-workflows/how-do-they-work.rst:184 +msgid "Priority" +msgstr "Priorité" + +#: ../system/core-workflows/how-do-they-work.rst:186 msgid "" -"Here you can decide if the certificate of your i-doit system has to be " -"verified or not. In case you are using custom certificates, please have a " -"look at :doc:`how to add them to Zammad `." +"You can define the sequence, in which the workflows are executed. The " +"default value is ``500``." msgstr "" -#: ../system/integrations/i-doit.rst:77 -msgid "2. List / Create Zammad Tickets in i-doit" +#: ../system/core-workflows/how-do-they-work.rst:189 +msgid "" +"The workflows are executed in ascending order by their priority. That means " +"lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "Zammad integration in i-doit's device view" +#: ../system/core-workflows/learn-by-example.rst:2 +#, fuzzy +msgid "Learn by Example" +msgstr "exemple" + +#: ../system/core-workflows/learn-by-example.rst:4 +msgid "" +"This page provides some basic examples for Core Workflows. Of course you can " +"build much more complex workflows if needed." msgstr "" -#: ../system/integrations/i-doit.rst:86 +#: ../system/core-workflows/learn-by-example.rst:7 msgid "" -"i-doit's ticket system integration gives you a way to see all the tickets " -"for a given device without ever leaving i-doit. (See our :user-docs:`user " -"documentation ` to learn how it " -"works in practice)." +"To learn about Core Workflows in detail, first go to :doc:`how-do-they-work`." msgstr "" -#: ../system/integrations/i-doit.rst:95 +#: ../system/core-workflows/learn-by-example.rst:10 +#, fuzzy +msgid "Group Based Examples" +msgstr "exemple" + +#: ../system/core-workflows/learn-by-example.rst:12 msgid "" -"Enable this integration in the i-doit admin panel under **Interfaces / " -"external data > Trouble Ticket System (TTS) > Configuration**:" +"All following workflows have the same base configurations. The workflow may " +"not use them all." msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "i-doit administration interface with TTS configuration" +#: ../system/core-workflows/learn-by-example.rst:15 +#, fuzzy +msgid "Groups:" +msgstr "Groupes" + +#: ../system/core-workflows/learn-by-example.rst:20 +#, fuzzy +msgid "Attributes:" +msgstr "Variables Article" + +#: ../system/core-workflows/learn-by-example.rst:22 +msgid "Category (Single tree selection field, not mandatory, agents only)" msgstr "" -#: ../system/integrations/i-doit.rst:104 -msgid "TTS-Type" +#: ../system/core-workflows/learn-by-example.rst:23 +msgid "" +"Approved (Boolean field, not mandatory, not shown, ``false`` as default)" msgstr "" -#: ../system/integrations/i-doit.rst:104 -msgid "``Zammad``" +#: ../system/core-workflows/learn-by-example.rst:24 +msgid "Operating System (Text field, not mandatory, not shown)" msgstr "" -#: ../system/integrations/i-doit.rst:115 -msgid "Username / Password" +#: ../system/core-workflows/learn-by-example.rst:25 +msgid "Software used (Single selection field, not mandatory, not shown)" msgstr "" -#: ../system/integrations/i-doit.rst:107 -msgid "Login credentials for a Zammad agent." +#: ../system/core-workflows/learn-by-example.rst:68 +msgid "Group specific values and fields" msgstr "" -#: ../system/integrations/i-doit.rst:109 +#: ../system/core-workflows/learn-by-example.rst:28 msgid "" -"This agent must have **read permission** for all :doc:`groups ` that plan on using the i-doit integration." +"This workflow set depends on the category field. It reduces the available " +"set of values based on the group selected." msgstr "" -#: ../system/integrations/i-doit.rst:113 -msgid "" -"You may even wish to create a dedicated agent account just for this " -"integration (otherwise, if the agent ever changes her password, you will " -"have to remember to update it here)." +#: ../system/core-workflows/learn-by-example.rst:33 +msgid "Workflow 2nd Level group" msgstr "" -#: ../system/integrations/i-doit.rst:117 -msgid "URL incl. protocol" +#: ../system/core-workflows/learn-by-example.rst:35 +msgid "" +"This reduces the category options to ``2nd Level/*``, ``Internal/*`` and " +"``Others``. It also sets further required fields to mandatory and visible." msgstr "" -#: ../system/integrations/i-doit.rst:118 -msgid "``https://your.zammad.domain``" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for 2nd level" msgstr "" -#: ../system/integrations/index.rst:2 -msgid "Integrations" -msgstr "Intégrations" +#: ../system/core-workflows/learn-by-example.rst:43 +msgid "Workflow Support group" +msgstr "" -#: ../system/integrations/index.rst:4 +#: ../system/core-workflows/learn-by-example.rst:45 msgid "" -"Zammad offers numerous integrations that add rich features to your instance." +"This reduces the category options to ``Support/*``, ``Internal/*`` and " +"``Others``. It also sets further required fields to visible." msgstr "" -#: ../system/integrations/index.rst:6 -msgid "We're still working on this part of our documentation, stay tight!" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for support" msgstr "" -#: ../system/integrations/index.rst:10 -msgid "Integrations for Phone Systems" +#: ../system/core-workflows/learn-by-example.rst:53 +msgid "Workflow Sales group" msgstr "" -#: ../system/integrations/index.rst:14 +#: ../system/core-workflows/learn-by-example.rst:55 msgid "" -"Your VoIP provider or telephony system is not listed? Possibly your provider " -"supports Zammad by using the generic CTI - if you're unsure ask your " -"provider." +"This reduces the category options to ``Sales/*``, ``Internal/*`` and " +"``Others``." msgstr "" -#: ../system/integrations/index.rst:18 -msgid "" -"Provider does not support Zammad? Consider creating a `feature request in " -"the Zammad Community `_." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for sales" msgstr "" -#: ../system/integrations/index.rst:31 -msgid "Integrations for Authentication and Customers" +#: ../system/core-workflows/learn-by-example.rst:68 +#: ../system/integrations/slack.rst:88 +msgid "The Result" msgstr "" -#: ../system/integrations/index.rst:44 -msgid "Integrations for Monitoring Systems" +#: ../system/core-workflows/learn-by-example.rst:63 +msgid "" +"This is what the agent would experience with the above workflows in place." msgstr "" -#: ../system/integrations/index.rst:46 -msgid "This section currently misses the following integrations:" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "" +"Workflow shows objects and limits options based on selections on the group" msgstr "" -#: ../system/integrations/index.rst:48 -msgid "Icinga" +#: ../system/core-workflows/learn-by-example.rst:90 +msgid "Approval process" msgstr "" -#: ../system/integrations/index.rst:49 -msgid "Monit" +#: ../system/core-workflows/learn-by-example.rst:71 +msgid "" +"In this case ``approved`` is visible to agents by default. For this " +"workflow, an additional role ``Approval person`` is required (no further " +"permissions)." msgstr "" -#: ../system/integrations/index.rst:50 -msgid "Nagios" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that restricts an approval attribute to specific roles" msgstr "" -#: ../system/integrations/index.rst:60 -msgid "Integrations for Issue Trackers" +#: ../system/core-workflows/learn-by-example.rst:81 +msgid "" +"This workflow may work best in combination with a :doc:`trigger ` but technically, this is not required." msgstr "" -#: ../system/integrations/index.rst:70 -msgid "Other Integrations" +#: ../system/core-workflows/learn-by-example.rst:84 +msgid "" +"Select fields may be a better approach because they allow more values than " +"just a simple ``true`` or ``false``." msgstr "" -#: ../system/integrations/index.rst:72 +#: ../system/core-workflows/learn-by-example.rst:0 msgid "" -"This section will hold any other integration that can't be grouped up (yet)." +"Workflow fixes possible values of \"Approved ?\" to a specific selection " +"depending on the users role" msgstr "" -#: ../system/integrations/ldap/index.rst:2 -msgid "LDAP / Active Directory" +#: ../system/core-workflows/learn-by-example.rst:103 +msgid "State dependent mandatory fields" msgstr "" -#: ../system/integrations/ldap/index.rst:4 +#: ../system/core-workflows/learn-by-example.rst:93 msgid "" -"Zammad comes with a powerful LDAP integration that allows you to have a " -"single source of truth. By this you reduce the number of login credentials " -"your user has to remember." +"This workflow sets ``Category`` to mandatory if the agent wants to set the " +"states ``closed`` or ``pending close`` to enforce categorization." msgstr "" -#: ../system/integrations/ldap/index.rst:10 +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that sets fields to mandatory on specific states" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:0 msgid "" -"The LDAP source is also a perfect candidate for Zammad's :docs:`Kerberos " -"Single Sign-On ` but also works as addition " -"to other :doc:`/settings/security/third-party`." +"Workflow sets category field to mandatory upon choosing closed or pending " +"close as state" msgstr "" -#: ../system/integrations/ldap/index.rst:None -msgid "Zammands LDAP management page" +#: ../system/core-workflows/learn-by-example.rst:106 +msgid "Manual Ticket Handover Process" msgstr "" -#: ../system/integrations/ldap/index.rst:25 -msgid "📝 :doc:`manage`" +#: ../system/core-workflows/learn-by-example.rst:108 +msgid "This example covers the handover of a ticket from one agent to another:" msgstr "" -#: ../system/integrations/ldap/index.rst:25 -msgid "Add, modify, remove or re-arrange your LDAP-Sources as needed." +#: ../system/core-workflows/learn-by-example.rst:110 +msgid "" +"When the ticket owner is modified, a new text field (\"Handover\") shows up " +"for a comment" msgstr "" -#: ../system/integrations/ldap/index.rst:30 -msgid "Before you continue, please note the following limitations." +#: ../system/core-workflows/learn-by-example.rst:112 +msgid "" +"This may only be visible when the owner is changed, therefore it has to be " +"hidden in general" msgstr "" -#: ../system/integrations/ldap/index.rst:32 -msgid "Mapping / Synchronizing organizations is not possible" +#: ../system/core-workflows/learn-by-example.rst:114 +msgid "The input in this handover text field is mandatory" msgstr "" -#: ../system/integrations/ldap/index.rst:36 +#: ../system/core-workflows/learn-by-example.rst:115 msgid "" -"You may want to consider using domain based assignments to overcome this " -"issue. Learn more on :doc:`/manage/organizations/index`." +"After submitting changes, the value of the handover field must be added as " +"an note to the ticket (via trigger)" msgstr "" -#: ../system/integrations/ldap/index.rst:39 -msgid "" -"Zammad's LDAP sync is one way. Editing user settings or permissions may be " -"overwritten upon the next sync depending on your configuration." +#: ../system/core-workflows/learn-by-example.rst:121 +msgid "Hiding handover field" msgstr "" -#: ../system/integrations/ldap/index.rst:41 -msgid "Nested groups are not supported." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Hiding the handover field in core workflows" msgstr "" -#: ../system/integrations/ldap/index.rst:42 -msgid "Synchronizing user avatars from LDAP is not supported." +#: ../system/core-workflows/learn-by-example.rst:126 +msgid "Showing handover field and setting it to mandatory" msgstr "" -#: ../system/integrations/ldap/index.rst:43 -msgid "Unlike user filters, group filters cannot be changed." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Showing the handover field and set it as mandatory" msgstr "" -#: ../system/integrations/ldap/index.rst:44 -msgid "" -"When a user originates from an LDAP server, Zammad will try to verify the " -"login credentials against LDAP first - if this fails Zammad will check its " -"local database." +#: ../system/core-workflows/learn-by-example.rst:131 +msgid "Trigger writing handover input to a new article" msgstr "" -#: ../system/integrations/ldap/index.rst:50 -msgid "" -"Users can have local passwords even if they're LDAP users! You can learn " -"more about user accounts in general on :doc:`/manage/users/index`." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Write handover content to a new article" msgstr "" -#: ../system/integrations/ldap/index.rst:54 +#: ../system/core-workflows/learn-by-example.rst:133 msgid "" -"When several LDAP sources contain the same user (meaning the same email " -"address), the user in question will be updated with every source configured. " -"*The last LDAP source will win.*" +"As a result, the ticket includes an article of the type note which includes " +"the predefined text and the handover comment." msgstr "" -#: ../system/integrations/ldap/index.rst:58 -msgid "" -"This is subject to change with `Issue 4109 `_ in the future." +#: ../system/core-workflows/limitations.rst:6 +msgid "Core Workflows do not replace Triggers" msgstr "" -#: ../system/integrations/ldap/index.rst:60 +#: ../system/core-workflows/limitations.rst:5 msgid "" -"Synchronization statistics currently affect *all* configured LDAP sources. " -"This also applies for newly added or updated sources." +"Workflows manipulate the behavior of fields. However, they do not set values " +"in fields because of actions." msgstr "" -#: ../system/integrations/ldap/index.rst:63 -msgid "" -"This is subject to change with `Issue 4108 `_ in the future." +#: ../system/core-workflows/limitations.rst:16 +msgid "API calls are only partly affected" msgstr "" -#: ../system/integrations/ldap/index.rst:65 +#: ../system/core-workflows/limitations.rst:9 msgid "" -"Zammad currently has limited fallback server support. You can workaround " -"this by providing several sources - however, ensure to have the exact same " -"configuration on your fallback." +"Some options affect UI only and thus do not restrict responses and calls." msgstr "" -#: ../system/integrations/ldap/index.rst:69 -msgid "" -"This is subject to improve with `Issue 4107 `_ in the future." +#: ../system/core-workflows/limitations.rst:11 +msgid "This affects the following actions:" msgstr "" -#: ../system/integrations/ldap/index.rst:76 -msgid "" -"This section holds all requests Zammad handled for all LDAP sources. These " -"entries can either contain synchronization information or logins " -"(authentication attempts via Zammad's login interface)." +#: ../system/core-workflows/limitations.rst:13 +msgid "select" msgstr "" -#: ../system/integrations/ldap/index.rst:80 -msgid "" -"By clicking on any request, Zammad will provide even more information. The " -"provided information can be useful when something does not work as expected." +#: ../system/core-workflows/limitations.rst:14 +msgid "auto select" msgstr "" -#: ../system/integrations/ldap/index.rst:85 -msgid "" -"Especially a LDAP synchronization can cause many log entries. The web " -"interface will always limit the number of shown entries to the last 50 " -"entries." +#: ../system/core-workflows/limitations.rst:15 +msgid "show" msgstr "" -#: ../system/integrations/ldap/index.rst:None -msgid "" -"Screencast showing LDAP integration log entries and a detail view on\n" -"an entry." +#: ../system/core-workflows/limitations.rst:16 +msgid "hide" msgstr "" -#: ../system/integrations/ldap/manage.rst:2 -msgid "Manage LDAP-Sources" +#: ../system/core-workflows/limitations.rst:25 +msgid "Some fields stay unavailable to customers" msgstr "" -#: ../system/integrations/ldap/manage.rst:6 +#: ../system/core-workflows/limitations.rst:19 msgid "" -"Please keep in mind all current limitations for the LDAP synchronization. " -"This will help to understand scopes of the following operations better." +"For technical and security reasons, some default fields (the pale ones you " +"can't edit) stay unavailable for display and usage on customer permissions." msgstr "" -#: ../system/integrations/ldap/manage.rst:65 -msgid "Add new source" +#: ../system/core-workflows/limitations.rst:23 +msgid "" +"If you require your customers to change e.g. priorities, please consider " +"using workarounds via :doc:`/system/objects` and :doc:`/manage/trigger`." msgstr "" -#: ../system/integrations/ldap/manage.rst:10 -msgid "" -"Using the *New Source* button allows you to add new LDAP sources to your " -"installation. You're not limited in the number of sources, however, keep in " -"mind that many sources will also take more time to synchronize." +#: ../system/core-workflows/limitations.rst:29 +msgid "Ticket title changes not supported in edit mask" msgstr "" -#: ../system/integrations/ldap/manage.rst:14 +#: ../system/core-workflows/limitations.rst:28 msgid "" -"You can choose between different encryption types, namely *SSL* and " -"*STARTTLS* or none of them (\"*No SSL*\"). If you choose *SSL* or " -"*STARTTLS*, Zammad will display an additional *SSL verification* option that " -"allows you to disable the verification, e.g. for self-signed SSL " -"certificates. You can also tell Zammad to use a different port by appending " -"``:`` to your hostname/IP." +"It is currently not possible to perform changes of the ticket title in the " +"edit mask (e.g. renaming, set to read-only)." msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "" -"Screenshot of configuring a new LDAP source with SSL encryption and SSL " -"verification" +#: ../system/core-workflows/limitations.rst:37 +msgid "What is out of scope of Core Workflows?" msgstr "" -#: ../system/integrations/ldap/manage.rst:26 +#: ../system/core-workflows/limitations.rst:32 msgid "" -"New Source with SSL transport security enabled and certificate verification" +"There are some things that would count as workflow but are either done via :" +"doc:`/manage/trigger` or :doc:`/manage/scheduler`." msgstr "" -#: ../system/integrations/ldap/manage.rst:30 -msgid "" -"Using an user filter can be a good idea if you only require a small subset " -"of your LDAP users in Zammad." +#: ../system/core-workflows/limitations.rst:35 +msgid "Such as (but not limited to):" msgstr "" -#: ../system/integrations/ldap/manage.rst:42 -msgid "This especially affects inactive users" +#: ../system/core-workflows/limitations.rst:37 +msgid "up- or downgrade permissions of users" msgstr "" -#: ../system/integrations/ldap/manage.rst:34 -msgid "" -"As every LDAP behaves differently on which attributes and how they are set, " -"Zammad doesn't care about any flags." +#: ../system/core-workflows/limitations.rst:38 +msgid "affecting article creation or listing" msgstr "" -#: ../system/integrations/ldap/manage.rst:37 -msgid "" -"Users that no longer are returned by your LDAP source will automatically be " -"set to inactive. Zammad assumes that the user was deactivated." +#: ../system/data-privacy.rst:2 +msgid "Data Privacy" msgstr "" -#: ../system/integrations/ldap/manage.rst:41 +#: ../system/data-privacy.rst:4 msgid "" -"Users will never be removed automatically! If you want to remove obsolete " -"users, use :doc:`/system/data-privacy`." +"For compliance with GDPR and other data privacy laws, you may wish to " +"**permanently delete users from the system**, along with **all of their " +"associated tickets**." msgstr "" -#: ../system/integrations/ldap/manage.rst:46 -msgid "Active Directory admins" +#: ../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 `!" msgstr "" -#: ../system/integrations/ldap/manage.rst:45 +#: ../system/data-privacy.rst:12 msgid "" -"Active Directories are quite specific on how to filter for active users only " -"- please see the `Microsoft documentation `_ for more " -"information." -msgstr "" - -#: ../system/integrations/ldap/manage.rst:51 -msgid "" -"*Do not* manually write pathes of either LDAP attributes or groups. If " -"Zammad does not display them, it either cannot find them or you have a lot " -"of users that don't have the attributes populated." +"Access to this panel requires ``admin.data_privacy`` permissions (introduced " +"in Zammad 3.5)." msgstr "" -#: ../system/integrations/ldap/manage.rst:55 +#: ../system/data-privacy.rst:15 msgid "" -"Zammad will always only return attributes that are filled - this reduces the " -"returned list of attributes greatly." +"On older systems that have not been updated yet, customers can also be :docs:" +"`deleted via the Zammad console `." msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing how to add a new LDAP source" +#: ../system/data-privacy.rst:22 +msgid "User deletion dialog in the Data Privacy panel" msgstr "" -#: ../system/integrations/ldap/manage.rst:63 +#: ../system/data-privacy.rst:22 msgid "" -"If your LDAP system doesn't allow anonymous bind, Zammad detects it and " -"provides you an editable \"Base DN\" *text* field instead of a prefilled " -"*select* field." +"The user deletion dialog lists some of the tickets that will be removed from " +"the system along with the user." msgstr "" -#: ../system/integrations/ldap/manage.rst:81 -msgid "Review or edit existing source" -msgstr "" +#: ../system/data-privacy.rst:27 +#, fuzzy +msgid "Deleting Users via GUI" +msgstr "Intégrations" -#: ../system/integrations/ldap/manage.rst:68 -msgid "" -"Clicking on a LDAP source will provide a configuration and mapping overview." +#: ../system/data-privacy.rst:29 +msgid "🔥 **All deletions are FINAL!**" msgstr "" -#: ../system/integrations/ldap/manage.rst:70 -msgid "" -"If needed you can then use the *Change* button to update either the name, " -"active state or the whole configuration. If you're changing the whole " -"configuration, the dialogue will be identical to the source creation." +#: ../system/data-privacy.rst:31 +msgid "Once you click “Delete”, the action cannot be canceled or undone." msgstr "" -#: ../system/integrations/ldap/manage.rst:76 +#: ../system/data-privacy.rst:33 msgid "" -"Did your LDAP server change? Different LDAP servers have different " -"structures and default attributes. This causes the LDAP synchronization to " -"likely fail. Consider removing the affected source and re-add it." +"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." msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing the update of the source name." +#: ../system/data-privacy.rst:36 +msgid "**The following records cannot be deleted:**" msgstr "" -#: ../system/integrations/ldap/manage.rst:89 -msgid "Re-arrange LDAP source's order" +#: ../system/data-privacy.rst:38 +msgid "your own account" msgstr "" -#: ../system/integrations/ldap/manage.rst:84 -msgid "" -"You can change the synchronization order for each source at any time. Zammad " -"will synchronize the sources from top to bottom." +#: ../system/data-privacy.rst:39 +msgid "the system's last remaining administrator account" msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "" -"Screencasting showing how to change the source order by using\n" -"drag and drop." +#: ../system/data-privacy.rst:42 +msgid "Step 1: Find a User / Confirm Deletion" msgstr "" -#: ../system/integrations/ldap/manage.rst:101 -msgid "Remove a source" +#: ../system/data-privacy.rst:44 +msgid "There are three ways to access the user deletion dialog:" msgstr "" -#: ../system/integrations/ldap/manage.rst:92 -msgid "" -"If you no longer need the a LDAP source or simply want to start over, you " -"can remove them at any time. This will not remove synchronized users, data " -"synchronized or permissions." +#: ../system/data-privacy.rst:51 +msgid "**from the user's profile**" msgstr "" -#: ../system/integrations/ldap/manage.rst:98 -msgid "" -"Not sure if you'd need the source later on? Set the source to inactive " -"instead of removing it - see *Review or edit existing source* for more." +#: ../system/data-privacy.rst:0 +msgid "Accessing the user deletion dialog in a user profile" msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing how to remove LDAP sources." +#: ../system/data-privacy.rst:51 +msgid "Click **Action > Delete**." msgstr "" -#: ../system/integrations/pgp/index.rst:2 -msgid "PGP" +#: ../system/data-privacy.rst:58 +msgid "**in the “Manage > Users” Admin Panel**" msgstr "" -#: ../system/integrations/pgp/index.rst:7 -msgid "" -"Pretty Good Privacy (PGP) is another method for secure email communication. " -"With PGP, you can exchange **signed** and **encrypted** messages with others." +#: ../system/data-privacy.rst:0 +msgid "Accessing the user deletion dialog under “Users” in the Admin Panel" msgstr "" -#: ../system/integrations/pgp/index.rst:13 -#: ../system/integrations/smime/index.rst:17 -msgid "Signing" +#: ../system/data-privacy.rst:58 +msgid "Use the **⋮ Actions** menu for the target user." msgstr "" -#: ../system/integrations/pgp/index.rst:11 -msgid "is a proof that a message hasn't been manipulated on its way." +#: ../system/data-privacy.rst:66 ../system/data-privacy.rst:104 +msgid "**in the “System > Data Privacy” Admin Panel**" msgstr "" -#: ../system/integrations/pgp/index.rst:13 +#: ../system/data-privacy.rst:0 msgid "" -"In other words, it guarantees message **integrity** and **authenticity**." -msgstr "" - -#: ../system/integrations/pgp/index.rst:19 -#: ../system/integrations/smime/index.rst:22 -msgid "Encryption" +"Accessing the user deletion dialog under “Data Privacy” in the Admin Panel" msgstr "" -#: ../system/integrations/pgp/index.rst:16 -#: ../system/integrations/smime/index.rst:20 +#: ../system/data-privacy.rst:65 msgid "" -"scrambles a message so that it can only be unscrambled by the intended " -"recipient." +"Use the **New Deletion Task** button. Search for users by name or email " +"address." msgstr "" -#: ../system/integrations/pgp/index.rst:19 +#: ../system/data-privacy.rst:79 +#, fuzzy +msgid "**Delete organizations**" +msgstr "Sociétés" + +#: ../system/data-privacy.rst:69 msgid "" -"In other words, it guarantees message **privacy** and **data security**." +"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:" msgstr "" -#: ../system/integrations/pgp/index.rst:25 -msgid "Screenshot of ticket creation with encrypt and sign buttons" +#: ../system/data-privacy.rst:0 +msgid "Deleting an organization via the user deletion dialog" msgstr "" -#: ../system/integrations/pgp/index.rst:25 +#: ../system/data-privacy.rst:78 msgid "" -"Once PGP has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " -"appear in the ticket composer." +"If this option does not appear, make sure there are no pending deletion " +"tasks for other customers from this organization." msgstr "" -#: ../system/integrations/pgp/index.rst:28 -msgid "**Sign button not visible?**" +#: ../system/data-privacy.rst:82 +msgid "Step 2: Monitor Deletion Job Status" msgstr "" -#: ../system/integrations/pgp/index.rst:30 +#: ../system/data-privacy.rst:84 msgid "" -"Please note that the signing of emails is based on the outgoing email " -"account. That means you have to choose a group with a sender email account, " -"which has a private key assigned." +"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:" msgstr "" -#: ../system/integrations/pgp/index.rst:35 -msgid "Handling of Keys" +#: ../system/data-privacy.rst:98 +msgid "**in the Activity Stream**" msgstr "" -#: ../system/integrations/pgp/index.rst:36 -msgid "" -"To use the PGP function, you have to enable the integration (PGP) by " -"switching the toggle to *enabled*." +#: ../system/data-privacy.rst:0 +msgid "Activity Stream showing data privacy tasks" msgstr "" -#: ../system/integrations/pgp/index.rst:39 +#: ../system/data-privacy.rst:94 msgid "" -"You can add keys by clicking the *add key* button. The keys can be imported " -"from a file or you can paste the content of the key in the text box." +"For each deleted user, the Activity Stream will be updated twice—once when " +"the task is created, and once when it's complete." msgstr "" -#: ../system/integrations/pgp/index.rst:42 -msgid "**Which keys do I have to import?**" +#: ../system/data-privacy.rst:97 +msgid "" +"These notifications are only visible to users with ``admin.data_privacy`` " +"permissions." msgstr "" -#: ../system/integrations/pgp/index.rst:44 +#: ../system/data-privacy.rst:0 msgid "" -"For **signing** *outgoing* emails, you have to import the private key of " -"your Zammad email account." +"The task list within Data Privacy shows removals being in progress and " +"completed." msgstr "" -#: ../system/integrations/pgp/index.rst:47 -msgid "" -"For **encrypting** *outgoing* emails, you have to import the public key of " -"the customer's email account." +#: ../system/data-privacy.rst:107 +msgid "Frequently Asked Questions" msgstr "" -#: ../system/integrations/pgp/index.rst:50 -msgid "" -"For **verifying the signature** of signed *incoming* emails, you have to " -"import the public key of the customer." +#: ../system/data-privacy.rst:121 +msgid "What happens if I receive an email from a deleted customer?" msgstr "" -#: ../system/integrations/pgp/index.rst:53 +#: ../system/data-privacy.rst:110 msgid "" -"For **decrypting** of encrypted *incoming* emails, you have to import the " -"private key of your Zammad email account." +"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/integrations/pgp/index.rst:57 -msgid "Import Keys From a File" +#: ../system/data-privacy.rst:115 +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**." msgstr "" -#: ../system/integrations/pgp/index.rst:58 -msgid "You can import keys from a file in the section **Upload key**:" +#: ../system/data-privacy.rst:130 +msgid "What about user information stored in internal notes or other messages?" msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of adding a key via file" +#: ../system/data-privacy.rst:124 +msgid "" +"The deletion process removes **user accounts and associated tickets only**." msgstr "" -#: ../system/integrations/pgp/index.rst:64 +#: ../system/data-privacy.rst:126 msgid "" -"**Supported file formats:** ASCII-armor as well as binary GPG format " -"(basically any GPG supported key format) is supported here." +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:68 -msgid "Import Keys by Pasting the Content" +#: ../system/data-privacy.rst:137 +msgid "I deleted an user and can still see a message they sent!" msgstr "" -#: ../system/integrations/pgp/index.rst:69 -msgid "You can also paste the key's content in the section **paste key**:" +#: ../system/data-privacy.rst:133 +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." msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of adding a key via pasting" +#: ../system/data-privacy.rst:141 +msgid "I removed a customer, now my reporting is off!" msgstr "" -#: ../system/integrations/pgp/index.rst:75 -msgid "" -"**Supported format:** Please note that only ASCII-armor is supported here." -msgstr "" - -#: ../system/integrations/pgp/index.rst:78 -#, fuzzy -msgid "Deleting Keys" -msgstr "Intégrations" - -#: ../system/integrations/pgp/index.rst:79 +#: ../system/data-privacy.rst:140 msgid "" -"If you want to delete a specific key, you can do it by clicking on the menu " -"in the *actions* column and select **delete**:" -msgstr "" - -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of deleting a key" +"When removing users and their tickets, all references are removed. This also " +"affects e.g. Reporting - these information are lost." msgstr "" -#: ../system/integrations/pgp/index.rst:88 -msgid "Downloading Keys" +#: ../system/data-privacy.rst:145 +msgid "How long does Zammad store created tasks?" msgstr "" -#: ../system/integrations/pgp/index.rst:89 +#: ../system/data-privacy.rst:144 msgid "" -"If you want to download your keys, you can do this as well via corresponding " -"action buttons. Depending on the key, you can choose wether you want to " -"download the private or the public key." +"Please see the on-premise data section of the :docs:`data privacy ` chapter." msgstr "" -#: ../system/integrations/pgp/index.rst:95 -#: ../system/integrations/smime/manage-certificates.rst:76 -msgid "Default Behavior" +#: ../system/data-privacy.rst:150 +msgid "What about re-assigned tickets? I want to delete them, too." msgstr "" -#: ../system/integrations/pgp/index.rst:96 +#: ../system/data-privacy.rst:148 msgid "" -"Here you can adjust on per group basis, if *sign* and *encryption* is on or " -"off by default. Please be aware, that agents can always override the setting " -"for each individual article." +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Adjusting default behavior on per group basis" +#: ../system/data-privacy.rst:154 +msgid "Why are there so many deletion task entries, I didn't create them!" msgstr "" -#: ../system/integrations/pgp/index.rst:107 +#: ../system/data-privacy.rst:153 msgid "" -"Here you can see the last actions regarding signing and encryption and if " -"they were successful." +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:117 -msgid "**Sign button is not visible, but keys are imported.**" +#: ../system/integrations/checkmk/admin-panel-reference.rst:2 +msgid "Admin Panel Reference" msgstr "" -#: ../system/integrations/pgp/index.rst:115 -msgid "Did you choose a group in the ticket?" +#: ../system/integrations/checkmk/admin-panel-reference.rst:None +msgid "Screenshot of Checkmk settings overview" msgstr "" -#: ../system/integrations/pgp/index.rst:116 +#: ../system/integrations/checkmk/admin-panel-reference.rst:12 msgid "" -"Did you import a private key for the email adress, which is used for " -"outgoing emails in the group?" +"Which :doc:`group ` should Checkmk tickets be assigned " +"to as a default (*i.e.,* when none is specified)?" msgstr "" -#: ../system/integrations/pgp/index.rst:122 -msgid "**How to obtain keys?**" +#: ../system/integrations/checkmk/admin-panel-reference.rst:15 +msgid "(Applies to :ref:`API alerts ` only.)" msgstr "" -#: ../system/integrations/pgp/index.rst:120 +#: ../system/integrations/checkmk/admin-panel-reference.rst:21 +msgid "Auto close" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:18 msgid "" -"You can create them yourself! There are some good tutorials on the web on " -"how to create them. Providing keys to Zammad is a prerequisite to use the " -"PGP feature." +"Should Zammad automatically close tickets if a service has recovered on its " +"own?" msgstr "" -#: ../system/integrations/pgp/index.rst:127 -msgid "**It says a passphrase is needed, but I haven't got one.**" +#: ../system/integrations/checkmk/admin-panel-reference.rst:21 +msgid "(Agents will receive notifications for such closures as appropriate.)" msgstr "" -#: ../system/integrations/pgp/index.rst:125 -msgid "" -"If the key is secured with a passphrase, you have to provide it for the " -"import in Zammad. It is possible that keys may have an empty passphrase. " -"However, this is *not* recommended." +#: ../system/integrations/checkmk/admin-panel-reference.rst:30 +msgid "Auto-close state" msgstr "" -#: ../system/integrations/pgp/index.rst:132 -msgid "**How do my customers get my new key?**" +#: ../system/integrations/checkmk/admin-panel-reference.rst:24 +msgid "What ticket state should be applied when “auto-closing” a ticket?" msgstr "" -#: ../system/integrations/pgp/index.rst:130 +#: ../system/integrations/checkmk/admin-panel-reference.rst:26 msgid "" -"You have to provide your **public** key in advance. Your customer also has " -"to configure PGP in their email workflow and import your public key. The " -"other way round, you have to get the public key of your customer and have to " -"import it to Zammad." +"You can choose from the seven built-in ticket states. If these states aren't " +"enough for you, you can :ref:`define a new ticket state ` for this purpose as well. This can be useful for tracking " +"tickets with :doc:`reports `, for example." msgstr "" -#: ../system/integrations/slack.rst:2 -msgid "Slack" +#: ../system/integrations/checkmk/admin-panel-reference.rst:35 +#: ../system/integrations/cti/includes/recent-logs.include.rst:2 +#: ../system/integrations/ldap/index.rst:74 +#: ../system/integrations/pgp/index.rst:106 +msgid "Recent Logs" msgstr "" -#: ../system/integrations/slack.rst:4 -msgid "**⚠️ Deprecation warning ⚠️**" +#: ../system/integrations/checkmk/admin-panel-reference.rst:None +msgid "Screenshot of Checkmk \"Recent Logs\" section" msgstr "" -#: ../system/integrations/slack.rst:6 +#: ../system/integrations/checkmk/admin-panel-reference.rst:41 msgid "" -"Zammad 7 will no longer support this dedicated Slack integration. It is " -"recommended to switch to :doc:`pre-defined webhooks ` instead. Existing Slack integrations should " -"be migrated manually before this feature is dropped." +"If you're having trouble getting Zammad and Checkmk to play nicely together, " +"this section can help you troubleshoot." msgstr "" -#: ../system/integrations/slack.rst:14 +#: ../system/integrations/checkmk/admin-panel-reference.rst:44 msgid "" -"In order to use this feature, please add a new Slack app to your Workspace. " -"The App you need is called ``Incoming WebHooks`` ." +"It contains a record of the fifty most recent transactions that Zammad knows " +"about, including each one's request/response details and return status." msgstr "" -#: ../system/integrations/slack.rst:18 -msgid "Why Do I Need This Feature?" +#: ../system/integrations/checkmk/api-reference.rst:2 +msgid "API Reference" msgstr "" -#: ../system/integrations/slack.rst:20 +#: ../system/integrations/checkmk/api-reference.rst:4 msgid "" -"If you're already using Slack for your team communication, you'll love this " -"feature! Our Slack integration can push ticket notifications about the last " -"ticket article based on the following events:" +"For most users, :ref:`the sample scripts from the Setup Guide ` will do the job just fine. But if you want more fine-grained control" +"—for instance, to create high- and low-priority tickets for different types " +"of system events—then you'll have to customize the data those scripts send " +"to Zammad." msgstr "" -#: ../system/integrations/slack.rst:24 -msgid "on Ticket creation" +#: ../system/integrations/checkmk/api-reference.rst:15 +msgid "" +"This custom script will automatically set all tickets it creates to **high " +"priority** and **assign them to charlie@chrispresso.com**." msgstr "" -#: ../system/integrations/slack.rst:25 -msgid "on Ticket updates" +#: ../system/integrations/checkmk/api-reference.rst:32 +msgid "How Does it Work?" msgstr "" -#: ../system/integrations/slack.rst:26 -msgid "on reached reminders" +#: ../system/integrations/checkmk/api-reference.rst:34 +msgid "" +"There are two kinds of data you can pass to the API, both in the form of key-" +"value pairs:" msgstr "" -#: ../system/integrations/slack.rst:27 -msgid "a Ticket has escalated" +#: ../system/integrations/checkmk/api-reference.rst:44 +msgid "Checkmk parameters" msgstr "" -#: ../system/integrations/slack.rst:28 -msgid "a Ticket is going to escalate" +#: ../system/integrations/checkmk/api-reference.rst:38 +msgid "" +"are required, and make up the **contents** of the resulting tickets/" +"articles. They also determine whether an event creates a new ticket or " +"updates/closes an existing one." msgstr "" -#: ../system/integrations/slack.rst:30 +#: ../system/integrations/checkmk/api-reference.rst:42 msgid "" -"Zammad will provide the Ticket title, a direct link to the Ticket, the event " -"type (creation, updated, escalation), the customer, time and the last " -"article that has triggered the notification." +"These are the only values used in the sample scripts. **Use them as-is**; " +"technically, they can be customized, but it's hard to imagine a good reason " +"for it." msgstr "" -#: ../system/integrations/slack.rst:34 +#: ../system/integrations/checkmk/api-reference.rst:52 +msgid "Ticket attributes" +msgstr "Attributs du ticket" + +#: ../system/integrations/checkmk/api-reference.rst:47 msgid "" -"This will give you further options, as you can see e.g. escalating tickets " -"that are assigned to an agent that's e.g. absent. You can interact faster, " -"as you might see problems earlier (or even before the problem gets one)." +"are optional, and can be used to **adjust settings** on newly created " +"tickets (*e.g.,* set the owner, group, priority, or state)." msgstr "" -#: ../system/integrations/slack.rst:38 +#: ../system/integrations/checkmk/api-reference.rst:50 msgid "" -"If needed and wanted, you can even discuss directly about the topic before " -"sending an answer to the customer. Another possible use case would be a " -"agent monitoring new agents and their answers to tickets." +"If you want to customize your Checkmk alert script, do it with these. Simply " +"add an extra “form” option for each one (``-F \"key=value\"``) to your " +"script's ``curl`` command line, as in the example above." msgstr "" -#: ../system/integrations/slack.rst:44 -#, fuzzy -msgid "Configure the Integration" -msgstr "Configuration du widget de discussion" +#: ../system/integrations/checkmk/api-reference.rst:54 +msgid "💡 **It's just an API endpoint!**" +msgstr "" -#: ../system/integrations/slack.rst:46 +#: ../system/integrations/checkmk/api-reference.rst:56 msgid "" -"First of all, please go to your slack workspace - go to administration => " -"Manage Apps. If you don't have an app yet, you can simply add a new one - " -"just search for ``Incoming WebHooks`` and customize the app to your needs." +"When using Checkmk integration, messages need to be formatted in a certain " +"way, but that *doesn't mean the messages actually have to come from Checkmk*." msgstr "" -#: ../system/integrations/slack.rst:50 +#: ../system/integrations/checkmk/api-reference.rst:59 msgid "" -"Choose (or create) the channel Zammad should post it's information to and " -"press on \"Add Incoming WebHooks integration\". If you're ready, copy the " -"provided WebHook URL and go to your Zammad installation." +"If you use another monitoring tool that's not officially supported by " +"Zammad, there's probably a way to make it work with your Checkmk callback " +"URL." msgstr "" -#: ../system/integrations/slack.rst:56 -msgid "" -"You need administrative rights on the Slack Workspace. The link to the app " -"directory is normally ``https://[workspace-name].slack.com/apps`` ." +#: ../system/integrations/checkmk/api-reference.rst:63 +msgid "Checkmk Parameters" msgstr "" -#: ../system/integrations/slack.rst:63 +#: ../system/integrations/checkmk/api-reference.rst:65 msgid "" -"To configure the slack integration, log in to Zammad and go to Integrations " -"(System) => Slack in the admin panel." +"When a notification is received, Zammad creates a new article containing the " +"details of the event that triggered it:" msgstr "" -#: ../system/integrations/slack.rst:66 -msgid "" -"Here you can choose on what evens Zammad should post information about a " -"ticket to your Slack channel. Next you need to device what groups shall be " -"affected by this, as anybody with access to that specific Slack channel can " -"read at least parts of the ticket this might be a privacy issue, if you " -"select the wrong groups. The username is simply the name that Zammad uses as " -"display name inside the Slack chat. The channel defines the Slack channel " -"the information is being posted in. As last option, you can set a custom " -"icon for posting to slack." +#: ../system/integrations/checkmk/api-reference.rst:None +msgid "Checkmk article body" msgstr "" -#: ../system/integrations/slack.rst:74 +#: ../system/integrations/checkmk/api-reference.rst:72 msgid "" -"When you're ready, just hit \"Submit\" and enable the integration. Zammad " -"will now post new ticket information based on the trigger you chose. Below " -"the options you have the recent log that shows the latest requests to Slack " -"for debugging if needed." +"These details come from the fields listed below, which correspond to " +"parameters provided by Checkmk (``$NOTIFY_*``)." msgstr "" -#: ../system/integrations/slack.rst:81 -msgid "" -"If you leave the Icon URL empty, Zammad will use the Zammad logo instead. " -"The icon should be a square PNG file." +#: ../system/integrations/checkmk/api-reference.rst:75 +msgid "**Required fields are marked with an asterisk (\\*).**" msgstr "" -#: ../system/integrations/slack.rst:90 -msgid "" -"The following figure shows how it will look if you choose to receive updates " -"on created and updated tickets. On every post Zammad sends to the Slack " -"channel, you can create new threads to discuss about the new article." +#: ../system/integrations/checkmk/api-reference.rst:79 +msgid "event_id\\*" msgstr "" -#: ../system/integrations/slack.rst:96 +#: ../system/integrations/checkmk/api-reference.rst:78 msgid "" -"If you just want to keep track of soon escalating or already escalated " -"tickets, it will look the the following figure. Zammad changes the color in " -"front of the post so you can easily see the state of the ticket." +"A unique ID for the system event. (``$NOTIFY_SERVICEPROBLEMID`` / " +"``$NOTIFY_HOSTPROBLEMID``)" msgstr "" -#: ../system/integrations/slack.rst:102 -msgid "" -"If you change the state, Zammad will also put information on what state the " -"ticket gets and (if pending state) the date until it pends. You'll also " -"recognize the color codes in front of posts on slack, as they are exact the " -"same the ticket state colors you'll see in Zammad!" +#: ../system/integrations/checkmk/api-reference.rst:86 +msgid "host\\*" msgstr "" -#: ../system/integrations/smime/index.rst:2 -msgid "S/MIME" +#: ../system/integrations/checkmk/api-reference.rst:82 +msgid "" +"The hostname of the system that the event originated from. " +"(``$NOTIFY_HOSTNAME``)" msgstr "" -#: ../system/integrations/smime/index.rst:11 +#: ../system/integrations/checkmk/api-reference.rst:85 msgid "" -"S/MIME is the most widely-supported method for secure email communication. " -"With S/MIME, you can exchange **signed** and **encrypted** messages with " -"others." +"Used to determine if a new event belongs to an existing ticket. Also used in " +"the subject line of the resulting article (“ is ”)." msgstr "" -#: ../system/integrations/smime/index.rst:15 -msgid "" -"is proof that a message hasn't been tampered with or sent by an impersonator." +#: ../system/integrations/checkmk/api-reference.rst:96 +msgid "service" msgstr "" -#: ../system/integrations/smime/index.rst:17 +#: ../system/integrations/checkmk/api-reference.rst:89 msgid "" -"In other words, it guarantees a message's **integrity** and **authenticity**." +"The name of the service that the event originated from. " +"(``$NOTIFY_SERVICEDESC``)" msgstr "" -#: ../system/integrations/smime/index.rst:22 -msgid "In other words, it guarantees **privacy** and **data security**." +#: ../system/integrations/checkmk/api-reference.rst:92 +msgid "Used to determine if a new event belongs to an existing ticket." msgstr "" -#: ../system/integrations/smime/index.rst:28 -msgid "Screencast demo of S/MIME features for both new tickets and replies" +#: ../system/integrations/checkmk/api-reference.rst:94 +#: ../system/integrations/checkmk/api-reference.rst:110 +msgid "Displayed as ``-`` when omitted." msgstr "" -#: ../system/integrations/smime/index.rst:28 -msgid "" -"Once S/MIME has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " -"appear in the ticket composer." +#: ../system/integrations/checkmk/api-reference.rst:104 +msgid "state\\*" msgstr "" -#: ../system/integrations/smime/index.rst:32 -msgid ":doc:`🔪 Prerequisites `" +#: ../system/integrations/checkmk/api-reference.rst:99 +msgid "" +"The current state of the service or host in question. " +"(``$NOTIFY_SERVICESTATE`` / ``$NOTIFY_HOSTSTATE``)" msgstr "" -#: ../system/integrations/smime/index.rst:31 +#: ../system/integrations/checkmk/api-reference.rst:102 msgid "" -"New to S/MIME? This section helps you to find certificate providers and " -"points out Limitations." +"Used to detect when a ticket should be auto-closed (*i.e.,* on ``OK``/" +"``UP``). Also used in the subject line of the resulting article (“ is " +"”)." msgstr "" -#: ../system/integrations/smime/index.rst:35 -msgid ":doc:`📝 Manage Certificates `" +#: ../system/integrations/checkmk/api-reference.rst:110 +msgid "text" msgstr "" -#: ../system/integrations/smime/index.rst:35 -msgid "Add and download certificates; configure group default behaviors." +#: ../system/integrations/checkmk/api-reference.rst:107 +msgid "" +"The output of the process that triggered the event. " +"(``$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" msgstr "" -#: ../system/integrations/smime/index.rst:38 -msgid ":doc:`😦 Troubleshooting `" +#: ../system/integrations/checkmk/api-reference.rst:121 +msgid "" +"The Object Manager attribute panel displays built-in and custom\n" +"attribute names." msgstr "" -#: ../system/integrations/smime/index.rst:38 -msgid "Took a wrong turn? About recent logs and common issues." +#: ../system/integrations/checkmk/api-reference.rst:121 +msgid "Find a complete list of ticket attributes in the Object Manager." msgstr "" -#: ../system/integrations/smime/index.rst:43 +#: ../system/integrations/checkmk/api-reference.rst:123 msgid "" -"For more details on how S/MIME integration works on the agent side, see the :" -"user-docs:`user docs `." +"Ticket attributes are entirely optional, and can be used to customize the " +"tickets that Checkmk creates. (Note that these attributes will be ignored if " +"a new event belongs to an existing ticket.)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:2 -msgid "Manage Certificates" +#: ../system/integrations/checkmk/api-reference.rst:128 +msgid "" +"Why would you want to do this? Maybe you have only one IT guy, and all " +"system monitoring issues should be automatically assigned to him. Or, maybe " +"you're creating multiple notification rules so that database outages take " +"higher priority than disk space warnings." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:4 -msgid "" -"S/MIME is **disabled by default**. Enable it to start adding certificates." +#: ../system/integrations/checkmk/api-reference.rst:135 +msgid "In most cases, you'll probably want to set one of the following:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:10 -msgid "Dialogue to add new certificates or private keys" +#: ../system/integrations/checkmk/api-reference.rst:137 +msgid "group" +msgstr "groupe" + +#: ../system/integrations/checkmk/api-reference.rst:139 +msgid "state" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:10 +#: ../system/integrations/checkmk/api-reference.rst:140 +msgid "priority" +msgstr "priorité" + +#: ../system/integrations/checkmk/api-reference.rst:142 msgid "" -"Manage certificates in the Admin Panel under **System > Integrations > S/" -"MIME**. Certificates may be pasted in as plain text or uploaded from a file." +"but in practice, you can set almost any attribute, including :doc:`custom " +"ones you created through the Object Manager `." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:14 -#, fuzzy -msgid "Add Certificate Data" -msgstr "Intégrations" - -#: ../system/integrations/smime/manage-certificates.rst:36 -msgid "Add Certificate" +#: ../system/integrations/checkmk/api-reference.rst:145 +msgid "Please note that the following attributes are **not customizable**:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:17 -msgid "" -"Import public-key certificates for both your own organization and your " -"contacts." +#: ../system/integrations/checkmk/api-reference.rst:147 +msgid "title" +msgstr "titre" + +#: ../system/integrations/checkmk/api-reference.rst:148 +msgid "id" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:19 -msgid "" -"You can also add a bunch of certificates in one go by providing a single " -"file with all relevant certificates." +#: ../system/integrations/checkmk/api-reference.rst:149 +msgid "ticket number" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:22 -msgid "🕵️ **ALWAYS verify certificates in-person or over the phone!**" +#: ../system/integrations/checkmk/api-reference.rst:151 +msgid "created_by_id" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:24 -msgid "" -"The whole point of signatures is to alert you when someone is trying to " -"pretend to be someone they're not. Never accept a certificate from someone " -"online without verifying it first." +#: ../system/integrations/checkmk/api-reference.rst:152 +msgid "updated_by_id" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:28 -msgid "📇 **What about trusted certificate authorities?**" +#: ../system/integrations/checkmk/api-reference.rst:155 +msgid "Which Values Can Be Set?" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:30 -msgid "" -"In some cases (e.g. when dealing with large enterprises), you may be given a " -"certificate for an entire CA, rather than a single contact. Add it here to " -"trust *all* certificates issued by that CA." +#: ../system/integrations/checkmk/api-reference.rst:157 +msgid "😵 **Invalid values → unpredictable behavior**" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:35 +#: ../system/integrations/checkmk/api-reference.rst:159 msgid "" -"Commercial CAs can usually be verified online. Zammad does not include a " -"list of built-in, trusted CAs." +"If you provide a value that Zammad doesn't understand (*e.g.,* ``-F " +"\"priority=high\"``), it's not always clear what will happen. In some cases, " +"a ticket will be created with the default values instead - but in others, it " +"may not be created at all!" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:57 -msgid "Add Private Key" +#: ../system/integrations/checkmk/api-reference.rst:164 +msgid "So what values does Zammad understand, then? Well, it depends..." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:39 -msgid "" -"Once you've added a public-key certificate, you can import its matching " -"private key." +#: ../system/integrations/checkmk/api-reference.rst:168 +msgid "Use an email address or username:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:42 -msgid "" -"Private keys are for **your own organization only**; never ask your contacts " -"for their private keys." +#: ../system/integrations/checkmk/api-reference.rst:190 +msgid "group & priority" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:0 -msgid "" -"S/MIME integration showing configured certificates and possible issues with " -"Logging" +#: ../system/integrations/checkmk/api-reference.rst:175 +msgid "Refer to the dropdown menus in the ticket pane:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:50 -msgid "" -"A note is displayed on certificates with a matching private key (see line 2)." +#: ../system/integrations/checkmk/api-reference.rst:0 +msgid "See possible values for certain attributes in the ticket pane." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:52 -msgid "📤 **Certificates and private keys must be uploaded separately.**" +#: ../system/integrations/checkmk/api-reference.rst:187 +msgid "🙅 **Ticket state CANNOT be set this way!**" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:54 +#: ../system/integrations/checkmk/api-reference.rst:189 msgid "" -"If your certificate and private key are bundled together in the same file or " -"PEM block, import it twice (once using each button)." +"Why? Because ``-F \"state=...\"`` is already used :ref:`as a Checkmk " +"parameter `." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:57 -msgid "Please note that bulk imports of private keys are not possible." +#: ../system/integrations/checkmk/api-reference.rst:222 +msgid "Everything Else" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:60 -#, fuzzy -msgid "Download Certificate Data" -msgstr "Intégrations" - -#: ../system/integrations/smime/manage-certificates.rst:62 +#: ../system/integrations/checkmk/api-reference.rst:193 msgid "" -"You can download the earlier provided certificates and private keys at any " -"time from your Zammad instance." +"To set any other attributes, it helps to know your way around the :docs:" +"`rails console `. Valid values are those that you can " +"set with a string:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:65 -msgid "" -"Please note that passphrase-protected private keys stay protected and when " -"you download them, you have to know the passphrase to use them after " -"downloading." +#: ../system/integrations/checkmk/api-reference.rst:218 +msgid "These values can then be passed directly to the API:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:73 -msgid "Dialogue to download certificates or private keys" +#: ../system/integrations/checkmk/index.rst:16 +msgid "How does it work?" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:73 -msgid "Download stored certificates and their keys" +#: ../system/integrations/checkmk/index.rst:2 +msgid "Checkmk" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:78 +#: ../system/integrations/checkmk/index.rst:4 msgid "" -"The ticket composer will set all outgoing messages to **signed and " -"encrypted** by default (assuming the required certificates exist)." +"`Checkmk `_ is a powerful IT monitoring tool that can " +"send real-time status alerts to Zammad via email or REST API. Set these " +"alerts up in Checkmk, and Zammad will automatically create, update, and " +"close tickets based on the health of your system:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:82 -msgid "These defaults can be modified on a per-group basis:" +#: ../system/integrations/checkmk/index.rst:14 +msgid "Screenshot of ticket created by Checkmk notifications" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:None -msgid "Zammad allowing to choose the default behavior on per group basis" +#: ../system/integrations/checkmk/index.rst:14 +msgid "Multiple alerts, same ticket." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:89 -msgid "" -"Of course, agents can always manually change these settings on each email " -"they send out." +#: ../system/integrations/checkmk/setup-guide.rst:2 +msgid "Setup Guide" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:4 -msgid "A certificate *and* private key for your own organization" +#: ../system/integrations/checkmk/setup-guide.rst:4 +msgid "" +"Whenever the Checkmk integration is enabled, Zammad listens for messages on " +"its API and over email. As long as those messages follow the required " +"format, Zammad will create new tickets (or find and update existing ones) " +"based on the message contents." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:6 +#: ../system/integrations/checkmk/setup-guide.rst:10 msgid "" -"(Use this to ✒️ **sign outgoing messages** and 🔓 **decrypt incoming " -"messages**.)" +"That means that “setting up Checkmk integration” is simply a matter of " +"**adding configuration to your Checkmk site**: telling it when to send these " +"messages and what to say. To do that, you'll need to create a new " +"**notification rule** (see `Checkmk's official docs `_ for help with that)." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:9 +#: ../system/integrations/checkmk/setup-guide.rst:17 msgid "" -"Certificates belonging your contacts, or their issuing certificate authority " -"(CA)" +"As part of this new rule, you'll have to choose a **notification method** " +"(*i.e.,* a script to execute whenever the rule is triggered). This script " +"will be written by you (samples below), and contain the logic for sending " +"API/email messages to Zammad:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:11 -msgid "" -"(Use these to ✅ **verify incoming message signatures** and 🔒 **encrypt " -"outgoing messages**.)" +#: ../system/integrations/checkmk/setup-guide.rst:26 +msgid "Checkmk \"New Rule\" dialog" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:14 -msgid "🙋 **I'm new to S/MIME. Where can I get a certificate?**" +#: ../system/integrations/checkmk/setup-guide.rst:26 +msgid "" +"Find your custom scripts in the Checkmk WATO under **Notifications > New " +"Rule > Notification Method**." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:16 +#: ../system/integrations/checkmk/setup-guide.rst:29 msgid "" -"The easiest way to get certificates is to buy an annual subscription through " -"a commercial CA, such as:" +"Once you're done setting up your new rule, you're all set! New tickets " +"should start coming in and auto-updating any time your rule is triggered." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:19 +#: ../system/integrations/checkmk/setup-guide.rst:33 msgid "" -"`Sectigo (formerly Comodo) `_" +"(If you need help troubleshooting, be sure to check the :ref:`checkmk-recent-" +"logs`.)" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:20 -msgid "`Secorio `_" +#: ../system/integrations/checkmk/setup-guide.rst:38 +msgid "API Alerts" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:21 -msgid "`GlobalSign `_" +#: ../system/integrations/checkmk/setup-guide.rst:40 +msgid "" +"To add these scripts in the Checkmk WATO, copy them into your Checkmk " +"installation directory and make them executable. (Be sure to replace the " +"``zammad.example.com`` callback URL with the one found in your admin panel.)" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:23 -msgid "(Zammad is not affiliated with these CAs in any way.)" +#: ../system/integrations/checkmk/setup-guide.rst:60 +msgid "Service notification" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:25 +#: ../system/integrations/checkmk/setup-guide.rst:46 msgid "" -"You can also generate your own self-signed certificates, but the process is " -"complicated and usually 🙅 **involves extra work for your contacts**." +"For updates on the status of the software running on your server (*e.g.,* " +"postgres)." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:29 -msgid "" -"Bear in mind that 🤝 **S/MIME only works if the other party is using it, too." -"**" +#: ../system/integrations/checkmk/setup-guide.rst:75 +msgid "Host notification" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:32 -msgid "Certificate and Private Key Checks on Upload" +#: ../system/integrations/checkmk/setup-guide.rst:63 +msgid "For updates on the status of the server itself." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:34 -msgid "" -"The certificate and public key validation is based on the ``X509v3`` " -"extensions." +#: ../system/integrations/checkmk/setup-guide.rst:77 +msgid "🤔 **What's with all the env vars?**" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:49 -msgid "Uploading a *client certificate*?" +#: ../system/integrations/checkmk/setup-guide.rst:79 +msgid "" +"Whenever Checkmk runs these scripts, it needs to provide some information " +"about the event that triggered the notification. This information is passed " +"in the form of these ``$NOTIFY_*`` environment variables." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:41 -msgid "The following attributes are required then:" +#: ../system/integrations/checkmk/setup-guide.rst:85 +msgid "" +"You can specify additional parameters to pass to the script when you're " +"setting up your notification rule, but the ones you see here are all " +"provided by default." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:39 -msgid "Subject Alternative Name (at least one email address has to be present)" +#: ../system/integrations/checkmk/setup-guide.rst:90 +msgid "Email Alerts" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:40 -msgid "Key Usage (``Digital Signature`` and/or ``Key Encipherment``)" +#: ../system/integrations/checkmk/setup-guide.rst:94 +msgid "" +"🐞 **There are known bugs** in Zammad's processing of email from Checkmk. " +"This section will be completed once they have been resolved. (Learn more at " +"GitHub issues `#2377 `_ & " +"`#2180 `_.)" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:41 -msgid "Public key algorithm (either ``RSA`` or ``EC``)" +#: ../system/integrations/checkmk/setup-guide.rst:100 +msgid "In the meantime, we encourage you to set up API alerts instead." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:43 -msgid "" -"The Extended Key Usage attribute is optional. If the certificate provides " -"the named attribute, than it must contain the value ``E-mail Protection``." +#: ../system/integrations/clearbit.rst:2 +msgid "Clearbit" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:46 +#: ../system/integrations/clearbit.rst:4 msgid "" -"Please note that any usable email adress has to be prefixed with ``email:`` " -"or ``rfc822:``." +"With our Clearbit integration, you can easily enrich the information " +"provided by Zammad. If the customers or agents email address is known to " +"Clearbit, it will share all information it has regarding the user with " +"Zammad. Those information can include the following:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:49 -msgid "The named public key algorithms are mandatory for private keys as well." +#: ../system/integrations/clearbit.rst:9 +msgid "Avatar" +msgstr "Avatar" + +#: ../system/integrations/clearbit.rst:10 +msgid "Address information" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:54 -msgid "Uploading a *CA certificate*?" +#: ../system/integrations/clearbit.rst:11 +msgid "Website information" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:52 -msgid "" -"In the case of an uploaded CA certificate, providing the value ``CA:TRUE`` " -"in the attribute *Basic Contstraints*, the previously mentioned attributes " -"are not verified." +#: ../system/integrations/clearbit.rst:12 +msgid "A BIO (as Note by default)" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:56 +#: ../system/integrations/clearbit.rst:14 msgid "" -"In general, the usage of any expired (``Not After``) or not yet valid (``Not " -"Before``) certificate is denied for outgoing emails." +"If needed, you can add further custom objects and add mappings to them, so " +"the Clearbit information can be filled within the database. In general you " +"can get any information from Clearbit, as long as you have a mapping to an " +"Zammad object." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:59 -msgid "Example certificate:" +#: ../system/integrations/clearbit.rst:21 +msgid "" +"Clearbit does have a mapping of fields like LDAP and Exchange have, but does " +"not \"win\" against Zammad information. This means that if you have e.g. the " +"last name field filled in already and Clearbit has other information on " +"that, it will not be updated." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:85 +#: ../system/integrations/clearbit.rst:26 msgid "" -"Please note that Zammad will distrust senders by default. This means that " -"you're always required to provide certificate data, no matter if for signing " -"or encrypting." +"However: If let's say the last name has been set by Clearbit and Zammad " +"notices that the last name on the Clearbit source has changed, Zammad will " +"also update this value." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:89 -msgid "This is by design and can't be adjusted." +#: ../system/integrations/clearbit.rst:33 +msgid "" +"The configuration of Clearbit is really easy and done fast! Just login to " +"your Clearbit-Account, go to \"API\" and copy the secret-API-Key." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:4 +#: ../system/integrations/clearbit.rst:38 msgid "" -"All of the system's latest S/MIME activity is displayed in the **Recent " -"Logs** section." +"Now change to your Zammad instance, go to Integrations (System) -> Clearbit " +"in the admin panel. Paste your API-Key into the API-Key-Field and decide if " +"Zammad should create unknown Organizations automatically, if the user does " +"not have one yet (and Clearbit knows it). The shared option decides if the " +"new organizations Zammad creates with Clearbit should be shared ones." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:11 -msgid "Sample entries of in- and outgoing S/MIME related emails." +#: ../system/integrations/clearbit.rst:47 +msgid "" +"If you're unsure what option to choose, better stick with \"no\". You can " +"also learn more about :doc:`/manage/organizations/index`." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:11 +#: ../system/integrations/clearbit.rst:52 msgid "" -"Logs report the status and details of all mail, both incoming and outgoing, " -"that used signing/verification or encryption/decryption." +"The Mapping option works similar to the mapping within the Exchange and LDAP " +"sync. You can add further mappings for e.g. custom fields if you need more " +"information that Clearbit can provide." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:14 +#: ../system/integrations/clearbit.rst:58 msgid "" -"This log does **not** include email sent by :doc:`triggers ` or the :doc:`scheduler `. For those, check your " -"``production.log``." +"If you want to add more Clearbit fields and want to learn more about " +"available fields on their API, you can take a look at their `API " +"documentation `_." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:20 -msgid "Common Issues" +#: ../system/integrations/clearbit.rst:62 +msgid "" +"If you're happy with the above chosen Settings and your mapping, just save " +"the changes and enable Clearbit integration. Zammad will now start polling " +"the Clearbit API as users contact you." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:30 -msgid "I received a signed/encrypted email before I set up S/MIME integration" +#: ../system/integrations/clearbit.rst:68 +msgid "" +"Zammad does not synchronize with Clearbit on a regular basis, but on demand " +"if needed. This saves API calls." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:23 +#: ../system/integrations/clearbit.rst:73 msgid "" -"No problem. Once S/MIME has been enabled and the appropriate certificates " -"have been added, agents will be prompted to retry verification/decryption on " -"matching emails." +"Below the Settings and Mappings, you'll find our Integration log. You can " +"see what requests Zammad sent to Clearbit and also the APIs Response." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:0 -msgid "Screenshot of user prompt to retry decryption" -msgstr "" - -#: ../system/integrations/smime/troubleshooting.rst:38 -msgid "The 🔒 **Encrypt** button is disabled" +#: ../system/integrations/clearbit.rst:78 +msgid "" +"By the way, you can also view the API log on the Clearbit website - the " +"information seen is basically the same." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:33 -msgid "Have you added the recipient's certificate?" +#: ../system/integrations/clearbit.rst:84 +msgid "Example When Adding a User" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:34 -msgid "Are you sure the recipient's certificate is valid?" +#: ../system/integrations/clearbit.rst:86 +msgid "" +"To show you how fast information is added, we added a small Screencast " +"below. This shows the creation of the User Alex from Clearbit. As we already " +"set the last name of Alex to \"X\", Zammad did not update it. What Zammad " +"did was to add further information it received from Clearbit." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:35 -msgid "Have you checked your ``production.log`` for more details?" +#: ../system/integrations/cti/generic.rst:2 +msgid "CTI (generic)" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:37 +#: ../system/integrations/cti/includes/introduction.include.rst:1 msgid "" -"If encryption doesn't work in the composer, it won't work in :doc:`triggers " -"` or the :doc:`scheduler ` either!" -msgstr "" - -#: ../system/integrations/smime/troubleshooting.rst:42 -msgid "The ✅ **Sign** button is disabled" +"This integration enables Zammad to provide a caller log to your agents. With " +"this your agents can greet your customers by their name and are supported by " +"Zammad with automatically opening a new ticket dialog or the user profile." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:41 +#: ../system/integrations/cti/includes/introduction.include.rst:6 msgid "" -"Have you added **both the certificate and private key** for your " -"organization?" +"Click the toggle next to the heading to activate or deactivate this " +"integration." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:42 +#: ../system/integrations/cti/includes/introduction.include.rst:9 msgid "" -"Does the email address on the certificate match the email address of the " -"agent/group composing the email?" +"If you want to learn more on how your agents can use this function, please " +"refer the :user-docs:`user documentation `." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:45 -msgid "Error: “Fingerprint already taken”" +#: ../system/integrations/cti/includes/introduction.include.rst:14 +msgid "" +"Automatically opening new ticket dialogues or user profiles requires agent " +"to extension mapping - see more below." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:45 -msgid "Are you sure you haven't added this certificate already?" +#: ../system/integrations/cti/includes/introduction.include.rst:20 +msgid "Please note the following limitations to reduce confusion later on:" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:48 -msgid "Error: “❌ invalid byte sequence in UTF-8”" +#: ../system/integrations/cti/includes/introduction.include.rst:22 +msgid "CTI integrations provide caller log functions only." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:48 -msgid "Please ensure to provide PEM formatted certificate and keys." +#: ../system/integrations/cti/includes/introduction.include.rst:23 +msgid "" +"This integration does not provide any VoIP functionalities; you can't make " +"phone calls from within Zammad." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:49 -msgid "Did you check if the provided file is a valid certificate or key?" +#: ../system/integrations/cti/includes/introduction.include.rst:25 +msgid "" +"If your browser supports ``tel``-URLs, you can click on phone numbers for " +"automatic dialing. This requires additional software / configuration on your " +"agent's computers." msgstr "" -#: ../system/integrations/zabbix.rst:2 -msgid "Zabbix Integration" +#: ../system/integrations/cti/generic.rst:9 +#: ../system/integrations/cti/placetel.rst:14 +#: ../system/integrations/cti/sipgate.rst:14 +msgid "Please provide the following requirements:" msgstr "" -#: ../system/integrations/zabbix.rst:5 +#: ../system/integrations/cti/generic.rst:11 msgid "" -"This guide describes how to integrate your Zabbix 5.4 installation with " -"Zammad using the Zabbix webhook feature. This guide will provide " -"instructions on setting up a media type, a user and an action in Zabbix." -msgstr "" - -#: ../system/integrations/zabbix.rst:12 -msgid "Zammad with enabled HTTP Token Authentication" +"A telephone system that supports webhooks (outbound) (best option are those " +"that allow customizing the calls)." msgstr "" -#: ../system/integrations/zabbix.rst:13 -msgid "Zabbix version 5.4 or higher" +#: ../system/integrations/cti/generic.rst:13 +msgid "A unique Call-ID during the call session." msgstr "" -#: ../system/integrations/zabbix.rst:16 -msgid "Setting up a Zammad" +#: ../system/integrations/cti/generic.rst:14 +msgid "Call event data (both numbers and direction)." msgstr "" -#: ../system/integrations/zabbix.rst:18 -msgid "Enable **API Token Access** in Settings > System > API." +#: ../system/integrations/cti/generic.rst:15 +msgid "Your Zammad instance must be reachable for your telephony system." msgstr "" -#: ../system/integrations/zabbix.rst:20 +#: ../system/integrations/cti/generic.rst:17 msgid "" -"Create a **new user** for a Zabbix alerter with an **email address** and " -"create a personal user token with **ticket.agent** permissions." +"If you want to learn more on what kind of requests are supported by Zammad " +"and what it expects, please consult our :docs:`CTI-API documentation `." msgstr "" -#: ../system/integrations/zabbix.rst:24 +#: ../system/integrations/cti/generic.rst:22 +#: ../system/integrations/cti/placetel.rst:27 +#: ../system/integrations/cti/sipgate.rst:30 #, fuzzy -msgid "Zabbix Webhook Configuration" -msgstr "Intégrations" +msgid "Available Settings" +msgstr "Paramètres" -#: ../system/integrations/zabbix.rst:27 -msgid "Create a Global Macro" -msgstr "" +#: ../system/integrations/cti/generic.rst:29 +#: ../system/integrations/cti/placetel.rst:41 +#: ../system/integrations/cti/sipgate.rst:40 +#, fuzzy +msgid "Endpoint Settings" +msgstr "Paramètres" -#: ../system/integrations/zabbix.rst:29 +#: ../system/integrations/cti/generic.rst:25 msgid "" -"Before setting up the **Webhook**, you need to setup the global macro " -"**{$ZABBIX.URL}**, which must contain the **URL** to the **Zabbix frontend**." +"Zammad will list your generic CTI endpoint here. It contains a unique token " +"so ensure to keep this URL save." msgstr "" -#: ../system/integrations/zabbix.rst:33 +#: ../system/integrations/cti/generic.rst:28 msgid "" -"In the **Administration** > **Media types** section, import the `Template`_." +"You'll need this endpoint for your PBX to talk to Zammad, see :docs:`CTI-API " +"documentation `." msgstr "" -#: ../system/integrations/zabbix.rst:38 -msgid "Open the added **Zammad** media type and set:" +#: ../system/integrations/cti/includes/important-dont-forget-saving.include.rst:3 +msgid "" +"All following options **do not save automatically**. Always use the Save " +"button on the lower end of the integration page!" msgstr "" -#: ../system/integrations/zabbix.rst:40 -msgid "**zammad\\_access\\_token** to the your **Personal User Token**" +#: ../system/integrations/cti/generic.rst:43 +#: ../system/integrations/cti/placetel.rst:49 +#: ../system/integrations/cti/sipgate.rst:52 +#, fuzzy +msgid "Call Settings" +msgstr "Paramètres" + +#: ../system/integrations/cti/generic.rst:39 +#: ../system/integrations/cti/placetel.rst:49 +#: ../system/integrations/cti/sipgate.rst:37 +#: ../system/integrations/cti/sipgate.rst:50 +msgid "Inbound" msgstr "" -#: ../system/integrations/zabbix.rst:41 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:1 msgid "" -"**zammad\\_url** to the **frontend URL** of your **Zammad** installation" +"This option allows you to block specific incoming caller IDs. It allows you " +"to temporarily reject e.g. spam callers without having to contact providers " +"or PBX administrators." msgstr "" -#: ../system/integrations/zabbix.rst:43 -msgid "**zammad\\_customer** to your **Zammad user email**." +#: ../system/integrations/cti/includes/inbound-calls.include.rst:11 +msgid "Caller ID to block" msgstr "" -#: ../system/integrations/zabbix.rst:44 -msgid "" -"**zammad\\_enable\\_tags** to **true** or **false** to enable or disable " -"trigger tags. **Important**: if you enable tag support, each tag is set with " -"a separate request." +#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 +msgid "Provide caller IDs to block in ``E.164`` format." msgstr "" -#: ../system/integrations/zabbix.rst:48 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:8 msgid "" -"If you want to prioritize issues according to **severity** values in Zabbix, " -"you can define mapping parameters:" +"Your telephony system has to support this function. Zammad will send a " +"``reject`` response which will cause your telephony system to hang up the " +"call. To callers this usually will feel like the line is busy." msgstr "" -#: ../system/integrations/zabbix.rst:51 -msgid "**severity\\_**: Zammad priority ID" +#: ../system/integrations/cti/includes/inbound-calls.include.rst:14 +msgid "" +"Provide a meaningful note for your fellow administrators to remind yourself " +"why you've chosen to block the number." msgstr "" -#: ../system/integrations/zabbix.rst:53 -msgid "Click the **Update** button to save the **Webhook** settings." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:17 +#: ../system/integrations/cti/sipgate.rst:40 +msgid "Outbound" msgstr "" -#: ../system/integrations/zabbix.rst:55 +#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:1 msgid "" -"To receive notifications in **Zammad**, you need to create a **Zabbix user** " -"and add **Media** with the **Zammad** type." +"In many cases you may want to use a different caller ID depending on the " +"destination you're calling. This may apply due to specific connection rates " +"to other countries or because you want your customer to feel you're calling " +"from the same country." msgstr "" -#: ../system/integrations/zabbix.rst:58 -msgid "" -"For **Send to**: enter any text, as this value is not used, but is required." +#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:6 +msgid "This option expects ``E.164`` number formats." msgstr "" -#: ../system/integrations/zabbix.rst:61 -msgid "" -"For more information, use the `Zabbix documentation `_." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 +msgid "Destination caller ID" msgstr "" -#: ../system/maintenance.rst:2 -msgid "Maintenance" -msgstr "Maintenance" - -#: ../system/maintenance.rst:4 -msgid "" -"Zammad comes with a maintenance mode that you can use for e.g. updating the " -"instance or changing settings while restricting availability and functions." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:5 +msgid "The caller ID or number you're trying to call." msgstr "" -#: ../system/maintenance.rst:13 -msgid "Mode" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:7 +msgid "You can use wildcards for e.g. country specific outbound numbers like:" msgstr "" -#: ../system/maintenance.rst:8 -msgid "The mode setting allows you to enable or disable the maintenance mode." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:9 +msgid "``49*`` for Germany" msgstr "" -#: ../system/maintenance.rst:10 -msgid "Defaults to *off*." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:10 +msgid "``4930*`` for Berlin / Germany landlines" msgstr "" -#: ../system/maintenance.rst:12 -msgid "" -"The maintenance mode will restrict access to administrative roles only. This " -"means agents and customers are logged off." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 +msgid "``33*`` for France" msgstr "" -#: ../system/maintenance.rst:23 -msgid "@Login" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:15 +msgid "Set Outbound caller ID" msgstr "" -#: ../system/maintenance.rst:16 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:14 msgid "" -"This setting allows you to provide a login message within a green banner " -"above the login screen. Click into the green banner in the settings page to " -"adjust your message. To activate the message, activate the *@Login* setting." +"The outbound caller ID to set (the number your customer sees on his display) " +"in ``E.164`` number format." msgstr "" -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing the default login message within the\n" -"settings page" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 +msgid "Provide a short description for fellow administrators." msgstr "" -#: ../system/maintenance.rst:26 +#: ../system/integrations/cti/includes/generic-cti-support-note.includes.rst:3 msgid "" -"Send an informative message to **all active sessions**. This comes handy to " -"inform your agents e.g. about mayor outages or to force reloads after " -"configuration changes." +"This option requires your PBX to send a specific request to Zammad *before " +"dialing*. Please consult the :docs:`CTI API ` in case " +"you're not sure." msgstr "" -#: ../system/maintenance.rst:31 -msgid "This is the messages title (slightly bigger than the normal message)." +#: ../system/integrations/cti/generic.rst:52 +#: ../system/integrations/cti/placetel.rst:54 +#: ../system/integrations/cti/sipgate.rst:59 +#, fuzzy +msgid "Other Settings" +msgstr "Paramètres" + +#: ../system/integrations/cti/includes/other-settings-intro.include.rst:1 +msgid "" +"Below you can find all available additional settings for this CTI " +"integration. For your overview we're sorting them by appearance and " +"reference their description first." msgstr "" -#: ../system/maintenance.rst:34 -msgid "The text you want to provide to your logged in sessions." +#: ../system/integrations/cti/includes/default-caller-id.include.rst:2 +#: ../system/integrations/cti/includes/default-caller-id.include.rst:1 +msgid "Default caller ID for outbound calls" msgstr "" -#: ../system/maintenance.rst:39 -msgid "Reload application" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:16 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:15 +msgid "Shown records in caller log" msgstr "" -#: ../system/maintenance.rst:37 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:2 msgid "" -"Selecting this option will change the message acceptance button from *Close* " -"(with nothing happening) to *Continue session*, which forces the application " -"to reload." +"Allows you to set the number of shown caller log entries for all users. You " +"can choose from the following values:" msgstr "" -#: ../system/maintenance.rst:43 -msgid "" -"If you have customers that are logged in to Zammad, they'll also be notified " -"if they're active in that moment." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:5 +msgid "60 (default)" msgstr "" -#: ../system/maintenance.rst:48 -msgid "Example without reload application" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:6 +msgid "120" msgstr "" -#: ../system/maintenance.rst:52 -msgid "" -"Message setting within Zammad's admin settings without ticket reload " -"application setting." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:7 +msgid "180" msgstr "" -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing the send message settings without ticket\n" -"reload application set" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:8 +msgid "240" msgstr "" -#: ../system/maintenance.rst:61 ../system/maintenance.rst:85 -msgid "" -"The modal all other active sessions will see upon pressing *Send to clients*." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:9 +msgid "300" msgstr "" -#: ../system/maintenance.rst:0 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:11 +msgid "**🥵 Potential performance issue**" +msgstr "" + +#: ../system/integrations/cti/includes/records-caller-log.include.rst:13 msgid "" -"Screenshot showing modal caused by maintenance's message\n" -"without reload application ticket" +"Setting this setting higher than 60 may cause serious performance issues on " +"very busy instances. Keep in mind that this setting causes Zammad to poll " +"and send up to 300 records to *all active agent sessions* in very short time " +"periods." msgstr "" -#: ../system/maintenance.rst:72 -msgid "Example with reload application" +#: ../system/integrations/cti/generic.rst:73 +msgid "Caller Log Filter" msgstr "" -#: ../system/maintenance.rst:76 +#: ../system/integrations/cti/generic.rst:55 msgid "" -"Message setting within Zammad's admin settings with ticket reload " -"application setting." +"This function allows you to provide call information based on e.g. queues " +"only to agents that really need the information." msgstr "" -#: ../system/maintenance.rst:0 +#: ../system/integrations/cti/generic.rst:58 msgid "" -"Screenshot showing the send message settings with ticket\n" -"reload application set" +"Why? If you have a team for several countries or departments, you don't want " +"to bug your agents from other departments. Leaving these options empty will " +"fallback to showing everything to everyone." msgstr "" -#: ../system/maintenance.rst:0 +#: ../system/integrations/cti/generic.rst:64 +msgid "Destination caller ID or Queue" +msgstr "" + +#: ../system/integrations/cti/generic.rst:63 msgid "" -"Screenshot showing modal caused by maintenance's message\n" -"with reload application ticket" +"This depends on your PBX and usually is either a queue ID, phone number or " +"extension." msgstr "" -#: ../system/monitoring.rst:2 -msgid "Monitoring" -msgstr "Supervision" +#: ../system/integrations/cti/generic.rst:69 +msgid "Agents" +msgstr "" -#: ../system/monitoring.rst:4 +#: ../system/integrations/cti/generic.rst:67 msgid "" -"This function is only available in self hosted instances. If you use Zammad " -"in our cloud, we are monitoring the system on our own and take steps to fix " -"potential problems directly." +"Select the agents that are responsible for the group. These agents will then " +"see caller log entries and call notifications fitting to said queue." msgstr "" -#: ../system/monitoring.rst:11 +#: ../system/integrations/cti/generic.rst:0 msgid "" -"On the monitoring page, you can see the current health state of Zammad under " -"\"*Current Status*\" at the bottom. This can be useful if you want to have a " -"look if everything is up and running. As an example, you could have a look " -"in the monitoring when you assume that some emails aren't processed from " -"Zammad." +"Screenshot showing the caller log filter table with pre filled sample data" msgstr "" -#: ../system/monitoring.rst:17 -msgid "**Can't receive an email and the monitoring response is \"healthy\"?**" +#: ../system/integrations/cti/includes/recent-logs.include.rst:6 +msgid "" +"With recent logs Zammad allows you to view the latest calls for the CTI " +"functionality. This usually comes in handy, when you're looking for errors." msgstr "" -#: ../system/monitoring.rst:19 +#: ../system/integrations/cti/includes/recent-logs.include.rst:0 msgid "" -"Zammad will just inform you about unprocessable emails. This is not the case " -"for oversized emails. You can adjust the maximum email size in :doc:`../" -"channels/email/settings`." +"Screenshot showing several incoming requests within Recent logs section." msgstr "" -#: ../system/monitoring.rst:24 -#, fuzzy -msgid "Monitoring API" -msgstr "Supervision" +#: ../system/integrations/cti/includes/recent-logs.include.rst:16 +msgid "I'm just here to clear floats up." +msgstr "" -#: ../system/monitoring.rst:26 +#: ../system/integrations/cti/includes/recent-logs.include.rst:20 msgid "" -"Beside the indication in the monitoring page, you can also use an external " -"monitoring tool to monitor Zammad's health. To request the health of Zammad, " -"you need to provide the API key (token) to the external monitoring tool. You " -"can copy the token from the \"*Current Token*\" field as well as the whole " -"API endpoint of your system (\"*Health Check*\" field), in which the API " -"token is already included." +"By clicking on the entry of interest, Zammad will provide more details on " +"the call in question. You'll see the payload it received and also the " +"response that was sent." msgstr "" -#: ../system/monitoring.rst:37 -msgid "Screenshot showing Current Token and Health Check" +#: ../system/integrations/cti/includes/recent-logs.include.rst:0 +msgid "" +"Screenshot showing detailed information of a specific log entry of recent " +"logs" msgstr "" -#: ../system/monitoring.rst:37 -msgid "Screenshot showing Token and Health Check" +#: ../system/integrations/cti/includes/recent-logs.include.rst:31 +msgid "x" msgstr "" -#: ../system/monitoring.rst:39 -msgid "" -"In addition to that, you can reset the auto-generated token to make sure " -"that already configured monitoring systems won't work anymore. So, please " -"use this \"*Reset*\" button only if you know what you do!" +#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 +#: ../system/integrations/cti/includes/troubleshooting.include.rst:9 +msgid "My Phone page stays blank, signalling does work..." msgstr "" -#: ../system/monitoring.rst:44 -#, fuzzy -msgid "Example Output" -msgstr "exemple" - -#: ../system/monitoring.rst:0 -msgid "No issues found" +#: ../system/integrations/cti/includes/troubleshooting.include.rst:5 +msgid "" +"If you've made sure that signalling works (check Recent logs) and your " +"Caller Log still stays empty, please ensure that you only configured one CTI " +"integration version. Specifically defining more than one agent mapping on " +"the different integration variants will be the issue." msgstr "" -#: ../system/monitoring.rst:48 ../system/monitoring.rst:60 -msgid "**Indicator in Zammad**:" +#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 +msgid "Clear the not needed agent mapping and reload your browser page." msgstr "" -#: ../system/monitoring.rst:0 -msgid "Screenshot showing monitoring with no issues" +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:1 +msgid "" +"By mapping your agents extension to their existing Zammad users, Zammad can " +"provide a new ticket dialog or open the user profile for the agent that " +"picks up the call." msgstr "" -#: ../system/monitoring.rst:54 ../system/monitoring.rst:66 -msgid "**API response**::" +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:5 +msgid "" +"This speeds up ticket aiding, no matter if it's for existing tickets or new " +"ones!" msgstr "" -#: ../system/monitoring.rst:0 -msgid "Issues were found" +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:8 +msgid "" +"To see it work from the agent's perspective, have a look on :user-docs:`user " +"documentation `." msgstr "" -#: ../system/monitoring.rst:0 -msgid "Screenshot showing monitoring with issues" +#: ../system/integrations/cti/placetel.rst:2 +msgid "Placetel CTI" msgstr "" -#: ../system/objects.rst:2 -msgid "Objects" -msgstr "Objets" +#: ../system/integrations/cti/placetel.rst:16 +msgid "You need an administrative Placetel account for your organization." +msgstr "" -#: ../system/objects.rst:4 +#: ../system/integrations/cti/placetel.rst:17 +#: ../system/integrations/cti/sipgate.rst:20 msgid "" -"In Zammad you can add your own fields to tickets, users, organizations and " -"even groups (these are called \"objects\"). This can be useful if you need " -"to add further information to a ticket or any other object in Zammad and the " -"information doesn't fit in any existing field." +"Your Zammad instance must be allowed to communicate to external services." msgstr "" -#: ../system/objects.rst:11 -msgid "" -"Try to avoid deleting attributes (and disable them instead) as Zammad might " -"run into unexpected conditions if they are referenced somewhere." +#: ../system/integrations/cti/placetel.rst:18 +msgid "Placetel must be able to reach your Zammad instance." msgstr "" -#: ../system/objects.rst:16 -msgid "" -"Here's an overview of object attributes. On the upper right you can add new " -"attributes. By default, there will be no custom fields - standard attributes " -"will be grayed out, you can't delete or change those. You can edit custom " -"attributes (they are displayed in black font and have a trash bin on the " -"right side) just by clicking on them." +#: ../system/integrations/cti/placetel.rst:22 +msgid ":doc:`provider-configurations/placetel`" msgstr "" -#: ../system/objects.rst:24 +#: ../system/integrations/cti/placetel.rst:21 msgid "" -"Attributes you add to Zammad, no matter if they have default values or not, " -"will not update existing information. This means a new ticket field " -"technically will be empty unless you populate it." +"Learn how to configure Placetel to enable Zammad and Placetel to communicate " +"with each other." msgstr "" -#: ../system/objects.rst:28 +#: ../system/integrations/cti/placetel.rst:32 msgid "" -"Especially in ticket scope this also means that newly added attributes will " -"be indicated as \"changed\" to agents that view the ticket. This may " -"interfere with Zammad's tabs behavior." +"The here listed endpoint settings are relevant for the :doc:`integration " +"configuration with Placetel `." msgstr "" -#: ../system/objects.rst:40 -#, fuzzy -msgid "Ordering Attributes" -msgstr "Objets" +#: ../system/integrations/cti/placetel.rst:37 +#: ../system/integrations/i-doit.rst:53 +msgid "Endpoint" +msgstr "" -#: ../system/objects.rst:42 +#: ../system/integrations/cti/placetel.rst:36 msgid "" -"Since Zammad introduced :doc:`/system/core-workflows` the need to have a " -"custom positioning for attributes has become more important than ever." +"This endpoint will be required for the Zammad integration within the " +"Placetel web interface." msgstr "" -#: ../system/objects.rst:45 -msgid "" -"To adjust the position of such an attribute, simply click on the attribute " -"entry in question, scroll down and adjust the position number. Please note " -"that you cannot change the positioning of default attributes." +#: ../system/integrations/cti/placetel.rst:41 +msgid "API Token" msgstr "" -#: ../system/objects.rst:49 +#: ../system/integrations/cti/placetel.rst:40 msgid "" -"In case two attributes have the same position value, Zammad will sort " -"alphabetically by name automatically." +"You'll receive this token within the ``Web API`` menu. Make sure to copy " +"this value, it's only shown once!" msgstr "" -#: ../system/objects.rst:None -msgid "" -"Screenshot showing custom attribute entries ordered in between default ones" +#: ../system/integrations/cti/placetel.rst:71 +#: ../system/integrations/cti/sipgate.rst:77 +msgid "Phone Extension to Agent Mapping" msgstr "" -#: ../system/objects.rst:56 -msgid "Updating Database After Adding or Editing Attributes" +#: ../system/integrations/cti/placetel.rst:0 +msgid "Screenshot showing sample user mappings in between Placetel and Zammad" msgstr "" -#: ../system/objects.rst:58 +#: ../system/integrations/cti/placetel.rst:64 msgid "" -"When adding or changing attributes, Zammad will not apply the changes " -"instantly, but instead shows you the changed attributes first. If you're " -"ready to go, just click on \"Update database\" to apply the changes to " -"Zammad. If you made a mistake or just want to discard your changes, click " -"\"Discard changes\"." +"You can find your agents Placetel username combination required within ⚙️ PBX " +"→ VoIP destinations. Within the \"Advanced settings\" section you're looking " +"for \"SIP user name\" and \"SIP server\"." msgstr "" -#: ../system/objects.rst:64 -msgid "" -"After applying the changes with \"Update Database\", a restart of Zammad is " -"**mandatory**. If you don't perform it, you may experience unexpected " -"behavior or even errors. You may want to do this kind of configuration " -"during maintenance windows." +#: ../system/integrations/cti/placetel.rst:68 +msgid "Combine these two like so: ``@``." msgstr "" -#: ../system/objects.rst:72 -msgid "" -"Changes on objects require you to update the database to apply these changes." +#: ../system/integrations/cti/placetel.rst:0 +msgid "Sample VoIP credentials for a Placetel user" msgstr "" -#: ../system/objects.rst:75 -msgid "**🤓 Service restarts can be automated**" +#: ../system/integrations/cti/provider-configurations/placetel.rst:2 +msgid "Setup Placetel connection for Zammad" msgstr "" -#: ../system/objects.rst:0 -msgid "Hosted environments automatically restart for you." +#: ../system/integrations/cti/provider-configurations/placetel.rst:6 +msgid "" +"This configuration step requires a *full* administrative Placetel account. " +"You may receive forbidden error messages with Placetel in case your " +"permissions are not high enough." msgstr "" -#: ../system/objects.rst:0 +#: ../system/integrations/cti/provider-configurations/placetel.rst:10 msgid "" -"If you're using a self-hosted installation you can use :docs:`environment " -"variables `" +"The following actions can be configured via the `Placetel web interface " +"`_." msgstr "" -#: ../system/objects.rst:82 -#, fuzzy -msgid "System Attributes" -msgstr "Variables Article" +#: ../system/integrations/cti/provider-configurations/placetel.rst:29 +msgid "Step 1: Activate Zammad integration" +msgstr "" -#: ../system/objects.rst:84 +#: ../system/integrations/cti/provider-configurations/placetel.rst:14 msgid "" -"Zammad comes with pre-configured attributes. Some of them can't be edited " -"via UI (or at all). This is required for proper operation of Zammad and not " -"a bug." +"Within Integrations, scroll down to Partner integrations and select Zammad." msgstr "" -#: ../system/objects.rst:90 -msgid "Ticket State" +#: ../system/integrations/cti/provider-configurations/placetel.rst:17 +msgid "" +"You can alternatively filter by \"Ticket Systems\" to reduce the number of " +"entries on the page. You'll still want to look for Partner integrations. 🤓" msgstr "" -#: ../system/objects.rst:92 +#: ../system/integrations/cti/provider-configurations/placetel.rst:21 msgid "" -"If the pre-configured states aren't enough for you or you want to change " -"them, you can do so by clicking on the cogwheel icon in the state row in the " -"ticket tab. But you should be careful when changing pre-configured states. " -"This can lead to unwanted behavior in some cases." +"Within the Zammad integration now press \"Activate\". A new tab ``API`` " +"becomes available - open this tab." msgstr "" -#: ../system/objects.rst:None -msgid "Screenshot showing highlighted ticket state attribute" +#: ../system/integrations/cti/provider-configurations/placetel.rst:24 +msgid "" +"Now tick \"Enable Call Control / Notify API\" and paste the Placetel " +"endpoint from your Zammad instance into the field \"URL of your API " +"endpoint\". Save to apply the settings" msgstr "" -#: ../system/objects.rst:122 -msgid "Handling of states" +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "Screencast showing how to activate the Zammad integration" msgstr "" -#: ../system/objects.rst:102 +#: ../system/integrations/cti/provider-configurations/placetel.rst:51 +msgid "Step 2: Generate API Token for Placetel" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:32 msgid "" -"In the state configuration screen, you can add new states, disable states or " -"change states." +"Go back to the integrations page and scroll down to \"Web API\". Generate a " +"new API token by using the \"Create a new API token\" button." msgstr "" -#: ../system/objects.rst:0 -msgid "Screenshot showing table of default ticket states" +#: ../system/integrations/cti/provider-configurations/placetel.rst:37 +msgid "" +"If you already generated a token either use your existing token or reset it " +"by using above mentioned button. Placetel will ask you to conform this reset." msgstr "" -#: ../system/objects.rst:110 +#: ../system/integrations/cti/provider-configurations/placetel.rst:41 msgid "" -"To add a new state, click on the \"New Ticket State\" button in the top " -"right corner. To change an existing state, simply click on the affected " -"state. This opens an edit dialog." +"Please keep in mind that existing API scripts may no longer work due to " +"token resets!" msgstr "" -#: ../system/objects.rst:114 +#: ../system/integrations/cti/provider-configurations/placetel.rst:44 msgid "" -"You can also clone a state or set them to \"Default for new tickets\" or " -"\"Default for follow-ups\" by clicking on the ⁝ action button and select the " -"desired function." +"Copy the provided API token and insert it into the \"API Token\" field " +"within Zammad's Placetel integration." msgstr "" -#: ../system/objects.rst:118 +#: ../system/integrations/cti/provider-configurations/placetel.rst:47 msgid "" -"*Default for new tickets* means that this state is used for every newly " -"created ticket." +"Apply your changes by using the \"Save\" button on the bottom of the " +"Placetel integration page and activate the Placetel integration." msgstr "" -#: ../system/objects.rst:121 +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 msgid "" -"*Default for follow-ups* means that this state is used if the ticket is re-" -"opened after it was closed." +"Screencast showing how to retrieve an API token from Placetel for Zammad" msgstr "" -#: ../system/objects.rst:171 -msgid "Ticket state in detail" +#: ../system/integrations/cti/provider-configurations/placetel.rst:73 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:77 +msgid "Step 3: Restrict the numbers to notify on" msgstr "" -#: ../system/objects.rst:125 +#: ../system/integrations/cti/provider-configurations/placetel.rst:54 msgid "" -"Below you can find a description for each field and option. Please head over " -"to the :ref:`example ` to see the edit dialog." +"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " +"the the Integrations page of the Placetel web interface, go to \"Notify " +"API\"." msgstr "" -#: ../system/objects.rst:129 +#: ../system/integrations/cti/provider-configurations/placetel.rst:58 msgid "" -"This is the name of the state and what you and your agents are seeing when " -"choosing a state somewhere (e.g. in tickets, trigger configuration)." +"Lower on the page Placetel allows you to restrict the numbers to notify on. " +"You'll find this within the \"External routing API\" part." msgstr "" -#: ../system/objects.rst:137 +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 msgid "" -"There are different state types you can choose from. By default, Zammad " -"comes with one state per state type." +"Screenshot showing a sample selection of phone numbers to use for the " +"Placetels notify API" msgstr "" -#: ../system/objects.rst:140 +#: ../system/integrations/cti/provider-configurations/placetel.rst:66 msgid "" -"**new**: for states for tickets that are new and it hasn't been worked on " -"them" +"This menu point also provides a API request log from Placetel view. Just " +"open \"Recent responses of your API endpoint\" to learn more." msgstr "" -#: ../system/objects.rst:142 +#: ../system/integrations/cti/provider-configurations/placetel.rst:69 msgid "" -"**open**: for states for tickets that are in progress and agents are working " -"on them" +"If you want to see Zammad's perspective, use the \"Recent Logs\" part from " +"within the Placetel integration page." msgstr "" -#: ../system/objects.rst:144 -msgid "**merged**: for states for tickets that are merged with other tickets" +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "Screenshot showing sample log entries for Placetels API calls to Zammad" msgstr "" -#: ../system/objects.rst:145 -msgid "" -"**pending reminder**: for states for tickets that are in progress and you " -"want to set a reminder. (default example: *pending reminder*)" +#: ../system/integrations/cti/provider-configurations/placetel.rst:77 +msgid "Step 4 (optional): Further configurations for Placetel" msgstr "" -#: ../system/objects.rst:147 +#: ../system/integrations/cti/provider-configurations/placetel.rst:76 msgid "" -"**pending action**: for states for tickets that are waiting for a specified " -"time and then change their state (default example: *pending close*)" +"If needed, you can now configure Zammad's Placetel integration in more " +"detail. You can learn more about your options here: :ref:`Placetel " +"integration settings `." msgstr "" -#: ../system/objects.rst:150 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:2 +msgid "Setup Sipgate connection for Zammad" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"**closed**: for states for tickets that are finished and do not need to be " -"processed further" +"Sipgate has no english web interface which is why this documentation page is " +"mixing up languages badly." msgstr "" -#: ../system/objects.rst:153 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"⚠️ Choosing the correct state type is important! If you are in doubt, have a " -"look on the default states and their types!" +"Please also note that the availability of API addons highly depends on your " +"package trier. Usage of sipgate.io packages *is not free*, please check " +"their `pricing page `_ before!" msgstr "" -#: ../system/objects.rst:158 -msgid "Ignore escalation" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:35 +msgid "Step 1: Book sipgate.io package" msgstr "" -#: ../system/objects.rst:157 -msgid "" -"Here you can define whether tickets of this state will count to escalation " -"time or not." +#: ../system/integrations/cti/provider-configurations/sipgate.rst:13 +msgid "Skip to step 2 if you already have the package booked!" msgstr "" -#: ../system/objects.rst:161 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:15 msgid "" -"You can create a note for the state to inform other admins about the state. " -"This has no effect on tickets." +"Login to an administrative Sipgate account and navigate to " +"``Accountverwaltung``. You'll see several different options depending on " +"your booked packages. Select ``Verträge & Produkte`` to continue." msgstr "" -#: ../system/objects.rst:165 -msgid "Set the state to *active* or *inactive*." +#: ../system/integrations/cti/provider-configurations/sipgate.rst:19 +msgid "" +"Scroll down to the section ``Zusätzliche Produkte buchen`` and look for " +"``sipgate.io`` - select this product by using the ``Produkte anzeigen``-" +"Button." msgstr "" -#: ../system/objects.rst:167 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:23 msgid "" -"it is technically possible to set all states to inactive. To keep Zammad " -"working in such a case, the inactive flag of one of the states is ignored." +"On the next page select either one of the ``sipgate.io`` packages or ``Push-" +"API Package Free``. Follow the dialogue by booking the addon. You'll be " +"returned to your contract overview and now should see the selected addon in " +"your list." msgstr "" -#: ../system/objects.rst:194 -#, fuzzy -msgid "Ticket state example" -msgstr "exemple" - -#: ../system/objects.rst:174 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:30 msgid "" -"Let's assume we want to create a new state which indicates that the ticket " -"has to wait for a response of a third party (e.g. service contractor or " -"manufacturer) and we want to to be able to set a reminder." +"The availability for ``sipgate.io`` packages and their levels highly depends " +"on the overall account type and product you've booked with Sipgate." msgstr "" -#: ../system/objects.rst:178 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"First we give the new state a proper name. In this example we call it " -"\"waiting for manufacturer\"." +"Screencast showing the process on how to book the required sipgate.io addon" msgstr "" -#: ../system/objects.rst:181 -msgid "" -"As state type we choose \"pending reminder\". This indicates that the ticket " -"is still open and we can set a reminder. This reminder can be useful if our " -"manufacturer sometimes isn't responding or we want to remind him to give us " -"an answer." +#: ../system/integrations/cti/provider-configurations/sipgate.rst:52 +msgid "Step 2: Configure webhook for Zammad" msgstr "" -#: ../system/objects.rst:186 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:38 msgid "" -"We choose \"no\" for \"ignore escalation\" because we want to escalate the " -"tickets even if we are waiting on the manufacturer's feedback." +"Within your ``Accountverwaltung`` navicate to your product ``sipgate.io``. " +"In the newly opened tab, switch from \"Clients\" to \"Webhooks\" and paste " +"the endpoint URLs from your Zammad instance like so:" msgstr "" -#: ../system/objects.rst:189 -msgid "The **result** in the creation dialog will look like this:" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:42 +msgid "Inbound endpoint to \"Incoming\"" msgstr "" -"Le **résultat** final du dialogue de création ressemblera à ce qui suit :" -#: ../system/objects.rst:0 -msgid "Screenshot showing ticket state creation dialog with example" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:43 +msgid "Outbound endpoint to \"Outgoing\"" msgstr "" -#: ../system/objects.rst:197 ../system/objects.rst:199 -#, fuzzy -msgid "Ticket Priority" -msgstr "priorité" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:47 +msgid "" +"Ensure to select at least one call group or phoneline within \"Sources\". " +"Other wise Sipgate will not indicate any incoming or outgoing calls to " +"Zammad." +msgstr "" -#: ../system/objects.rst:199 ../system/objects.rst:201 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"If the pre-configured priorities aren't enough for you or you want to change " -"them, you can do so by clicking on the cogwheel icon in the priority row in " -"the ticket tab:" +"Screencast showing how to add Zammad's endpoint URLs to sipgate.ios webhook " +"configuration" msgstr "" -#: ../system/objects.rst:None -msgid "Screenshot showing highlighted ticket priority attribute" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:55 +msgid "" +"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " +"the Webhooks → URLs section of Sipgate you can select which *sources* " +"Sipgate should notify Zammad about in- and outgoing calls." msgstr "" -#: ../system/objects.rst:224 ../system/objects.rst:226 -msgid "Handling of priorities" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:59 +msgid "" +"Use either specific phone lines or use the option \"Use for all phonelines " +"and groups\" to notify Zammad about all existing lines of your Sipgate " +"account." msgstr "" -#: ../system/objects.rst:208 ../system/objects.rst:210 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"In the priority configuration screen, you can add new priorities, disable " -"priorities or change priorities." +"Screenshot showing a sample selection of phone numbers to use for the " +"Sipgates webhooks API" msgstr "" -#: ../system/objects.rst:0 -msgid "Screenshot showing table of default ticket priorities" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:68 +msgid "This section also allows you to enable a Debug log." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "Screenshot showing an enabled Debug log option" msgstr "" -#: ../system/objects.rst:216 ../system/objects.rst:218 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:73 msgid "" -"To add a new priority, click on the \"New Priority\" button in the top right " -"corner. To change an existing priority, simply click on the affected " -"priority. This opens an edit dialog." +"After enabling you can use the Debug log section to see all sent webhook " +"calls to Zammad. You'll also can see the response." msgstr "" -#: ../system/objects.rst:220 ../system/objects.rst:222 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"You can also clone a priority or set them to \"Default for new tickets\" by " -"clicking on the ⁝ action button and select the desired function." +"Screenshot showing sample log entries for Sipgates webhook calls to Zammad" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:81 +msgid "Step 4 (optional): Further configurations for Sipgate" msgstr "" -#: ../system/objects.rst:223 ../system/objects.rst:225 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:80 msgid "" -"*Default for new tickets* means that this priority is used for every newly " -"created ticket." +"If needed, you can now configure Zammad's Sipgate integration in more " +"detail. You can learn more about your options here: :ref:`Sipgate " +"integration settings `." msgstr "" -#: ../system/objects.rst:246 ../system/objects.rst:248 -msgid "Priorities in detail" +#: ../system/integrations/cti/sipgate.rst:2 +msgid "Sipgate (sipgate.io)" msgstr "" -#: ../system/objects.rst:227 ../system/objects.rst:229 -msgid "Below you can find a description for each field and option." +#: ../system/integrations/cti/sipgate.rst:16 +msgid "You need an administrative Sipgate account for your organization." msgstr "" -#: ../system/objects.rst:230 ../system/objects.rst:232 +#: ../system/integrations/cti/sipgate.rst:17 msgid "" -"This is the name of the priority and what you and your agents are seeing " -"when choosing a priority somewhere (e.g. in tickets, trigger configuration)." +"Zammad requires a ``sipgate.io`` addon from the feature store (please note " +"that API calls are not free with Sipgate. Rates may apply and differ from " +"account to account)." msgstr "" -#: ../system/objects.rst:240 ../system/objects.rst:242 -msgid "Highlight color" +#: ../system/integrations/cti/sipgate.rst:21 +msgid "Sipgate must be able to reach your Zammad instance." msgstr "" -#: ../system/objects.rst:235 ../system/objects.rst:237 -msgid "" -"Switch between *Low priority* (light blue), *High priority* (red) and - " -"(default). This affects the displayed color for ticket titles in overviews." +#: ../system/integrations/cti/sipgate.rst:25 +msgid ":doc:`provider-configurations/sipgate`" msgstr "" -#: ../system/objects.rst:239 ../system/objects.rst:241 -msgid "The color options are currently limited to the mentioned options." +#: ../system/integrations/cti/sipgate.rst:24 +msgid "" +"Learn how to configure Sipgate to enable Zammad and Sipgate to communicate " +"with each other." msgstr "" -#: ../system/objects.rst:243 ../system/objects.rst:245 +#: ../system/integrations/cti/sipgate.rst:33 msgid "" -"You can create a note for the priority to inform other admins about the " -"priority. This has no effect on tickets." +"Below endpoint settings affect the :doc:`sipgate.io configuration `." msgstr "" -#: ../system/objects.rst:247 ../system/objects.rst:249 -msgid "Set the priority to *active* or *inactive*." +#: ../system/integrations/cti/sipgate.rst:37 +msgid "This endpoint is required for incoming call hooks." msgstr "" -#: ../system/objects/external-data-source-example.rst:2 -msgid "External Data Source" +#: ../system/integrations/cti/sipgate.rst:40 +msgid "This endpoint is required for outgoing call hooks." msgstr "" -#: ../system/objects/external-data-source-example.rst:4 -msgid "" -"We assume you already had a look on :doc:`types` where you can find a " -"description of the individual fields." +#: ../system/integrations/cti/sipgate.rst:0 +msgid "Screenshot showing sample user mappings in between Sipgate and Zammad" msgstr "" -#: ../system/objects/external-data-source-example.rst:7 +#: ../system/integrations/cti/sipgate.rst:69 msgid "" -"To reproduce this example, choose a category you want to add a custom field, " -"click on *New Attribute* and select *External data source field* under " -"*Format*." +"You can find your agent's Sipgate username within ``Accountverwaltung → " +"Benutzer``. You're looking for the SIP-ID." msgstr "" -#: ../system/objects/external-data-source-example.rst:11 -msgid "" -"Our example story is to fetch data from an external product database. We " -"want to add our products to the tickets so that the products can be searched " -"and chosen from a list and also create a link to the product website." +#: ../system/integrations/cti/sipgate.rst:0 +msgid "Sample VoIP credentials for a Sipgate user" msgstr "" -#: ../system/objects/external-data-source-example.rst:16 -msgid "Base configuration" +#: ../system/integrations/cti/sipgate.rst:77 +msgid "Users with several devices also have several SIP-IDs." msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Initial steps to configure external data source object type" +#: ../system/integrations/elasticsearch.rst:2 +msgid "Elasticsearch (SaaS)" msgstr "" -#: ../system/objects/external-data-source-example.rst:23 -#: ../system/variables.rst:85 -#, fuzzy -msgid "**Example:**" -msgstr "exemple" +#: ../system/integrations/elasticsearch.rst:4 +msgid "" +"The Elasticsearch integration allows you to create a read-only user to use " +"with your favorite reporting tool (e.g. like Grafana)." +msgstr "" -#: ../system/objects/external-data-source-example.rst:25 -msgid "Name: *product*" +#: ../system/integrations/elasticsearch.rst:7 +msgid "" +"If you want to take full advantage of the Zammad reporting, have a look at " +"our :docs:`Grafana ` " +"setup page as well." msgstr "" -#: ../system/objects/external-data-source-example.rst:26 -msgid "Display: *Product*" +#: ../system/integrations/elasticsearch.rst:11 ../system/subscription.rst:7 +msgid "**🚧 Hosted environment specific 🚧**" msgstr "" -#: ../system/objects/external-data-source-example.rst:29 -msgid "External data source configuration" +#: ../system/integrations/elasticsearch.rst:13 +msgid "" +"This integration is only available for Hosted setups. In order to use " +"Elasticsearch you'll need the **Plus** subscription." msgstr "" -#: ../system/objects/external-data-source-example.rst:31 +#: ../system/integrations/elasticsearch.rst:16 msgid "" -"First, enter the search URL making sure it contains ``#{search.term}`` as a " -"parameter:" +"Self hosted users have all the control over their self hosted Elasticsearch " +"instances." msgstr "" -#: ../system/objects/external-data-source-example.rst:34 -msgid "**Example:** ``https://dummyjson.com/products/search?q=#{search.term}``" +#: ../system/integrations/elasticsearch.rst:None +msgid "Elasticsearch integration page on SaaS environments" msgstr "" -#: ../system/objects/external-data-source-example.rst:36 +#: ../system/integrations/elasticsearch.rst:27 msgid "" -"After that, head down to the preview section and enter a search input for " -"the external data source." +"Please note the following limitations of Elasticsearch access on hosted " +"environments:" msgstr "" -#: ../system/objects/external-data-source-example.rst:39 -#, fuzzy -msgid "**Example:** ``mac``" -msgstr "exemple" - -#: ../system/objects/external-data-source-example.rst:41 -msgid "Then you can find a preview of the response data below:" +#: ../system/integrations/elasticsearch.rst:30 +msgid "access to the Elasticsearch index is read-only access" msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of JSON response based on search term" +#: ../system/integrations/elasticsearch.rst:31 +msgid "currently you're limited to user only" msgstr "" -#: ../system/objects/external-data-source-example.rst:48 +#: ../system/integrations/elasticsearch.rst:32 msgid "" -"We recommend using the preview to have a look on the structure. There is a " -"top-level element called ``products``. One level below, you can find the " -"attributes ``id`` and ``title``." +"Reporting tools that require to write into the indexes (like Kibana) are not " +"supported" msgstr "" -#: ../system/objects/external-data-source-example.rst:52 -msgid "**Search result response based on search from example:**" +#: ../system/integrations/elasticsearch.rst:34 +msgid "IP access restriction is currently not yet supported" msgstr "" -#: ../system/objects/external-data-source-example.rst:119 +#: ../system/integrations/elasticsearch.rst:37 +msgid "Activating Elasticsearch Access" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:39 msgid "" -"To tell the remote system that the desired data is located below the " -"``products`` level, you have to put it in the field *Search result list key*." +"By default external access to your Elasticsearch index is not active. You " +"can enable the integration at any time if needed." msgstr "" -#: ../system/objects/external-data-source-example.rst:122 +#: ../system/integrations/elasticsearch.rst:42 msgid "" -"After inserting ``products`` in the mentioned field, you get an extended " -"preview. You can find an additional box *Search result list* with a JSON " -"structure. This is the same response as before but stripped from the upper " -"``products`` element by the external data source." +"Please ensure to note down the password provided - you won't have access to " +"it afterwards." msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of JSON response search result list" +#: ../system/integrations/elasticsearch.rst:None +msgid "Screencast showing activation of Elasticsearch integration" msgstr "" -#: ../system/objects/external-data-source-example.rst:132 -msgid "" -"Now you need to provide the keys for the search result values and labels. As " -"already mentioned, we are looking for the ``id`` and the ``title`` of our " -"products. If you haven't already, it is now a good time to look at the " -"preview of the *Search result list*." +#: ../system/integrations/elasticsearch.rst:51 +msgid "Connection Settings" msgstr "" -#: ../system/objects/external-data-source-example.rst:197 +#: ../system/integrations/elasticsearch.rst:53 msgid "" -"After locating our two keys, we insert them in *search result value key* " -"(``id``) and in *Search result label key* (``title``)." +"This section holds the most important general information for accessing your " +"Elasticsearch indexes - such as:" msgstr "" -#: ../system/objects/external-data-source-example.rst:200 -msgid "" -"Basically, we configured the external data source already and we can see a " -"table in the preview section:" +#: ../system/integrations/elasticsearch.rst:57 +msgid "A unique subdomain that does not tell your real instance URL." msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of product table based on search term" +#: ../system/integrations/elasticsearch.rst:61 +msgid "Software" msgstr "" -#: ../system/objects/external-data-source-example.rst:208 +#: ../system/integrations/elasticsearch.rst:60 msgid "" -"According to our example story, now just the *Link template* is missing." +"The major version of the search index being used. This is required by some " +"Reporting tools like Grafana." msgstr "" -#: ../system/objects/external-data-source-example.rst:210 -msgid "" -"Please note that this is an optional feature. If you don't want to use such " -"links, of course you don't have to configure it." +#: ../system/integrations/elasticsearch.rst:64 +msgid "Authentication" msgstr "" -#: ../system/objects/external-data-source-example.rst:213 -msgid "" -"We can add now an address where additional product information can be found." +#: ../system/integrations/elasticsearch.rst:64 +msgid "The authentication type being supported. ``Basic Authentication``" msgstr "" -#: ../system/objects/external-data-source-example.rst:215 -msgid "Example: ``https://your_domain.com/q=#{ticket.product}``" +#: ../system/integrations/elasticsearch.rst:67 +msgid "Available Indexes" msgstr "" -#: ../system/objects/external-data-source-example.rst:217 -msgid "In the example, the parameter means:" +#: ../system/integrations/elasticsearch.rst:69 +msgid "" +"Within this section we're displaying the -in our opinion- most important " +"indexes for a Zammad instance." msgstr "" -#: ../system/objects/external-data-source-example.rst:219 -msgid "``#{}``: \"Frame\" for the insertion of information" +#: ../system/integrations/elasticsearch.rst:72 +msgid "" +"If you require all indexes or our listing is not good enough for you, point " +"your browser to the URL we're providing and append ``/_aliases?" +"pretty=true``. The result should look like this: ``https://.zammad.com/" +"_aliases?pretty=true``." msgstr "" -#: ../system/objects/external-data-source-example.rst:220 -msgid "``ticket``: object level, where you create your custom object" +#: ../system/integrations/elasticsearch.rst:77 +msgid "" +"Your browser will automatically ask for your credentials - you'll then see " +"something like this:" msgstr "" -#: ../system/objects/external-data-source-example.rst:221 -msgid "``product``: name of the (custom) object" +#: ../system/integrations/elasticsearch.rst:125 +msgid "Credentials" msgstr "" -#: ../system/objects/external-data-source-example.rst:223 +#: ../system/integrations/elasticsearch.rst:127 msgid "" -"After configuring your *Link template*, there will be another column in the " -"preview. Hovering on the icons in the *Link* column will show you where it " -"forwards you." +"Within this section Zammad displays your available users. The password is " +"provided once (upon activation) and cannot be retrieved after that." msgstr "" -#: ../system/objects/external-data-source-example.rst:232 +#: ../system/integrations/elasticsearch.rst:131 msgid "" -"In our example, one of the links looks like: https://your_domain.com/q=6, " -"where the 6 is the product id." +"If you need to change or reset your Elasticsearch user password, use the " +"\"Reset password\" button in the credentials table. Doing so creates a brand " +"new password for the account in question. This change is immediate, keep in " +"mind that this may affect third party tools connected to your instance." msgstr "" -#: ../system/objects/external-data-source-example.rst:235 -#, fuzzy -msgid "You can find more information regarding the URL in :doc:`types`." +#: ../system/integrations/exchange.rst:2 +msgid "Exchange" msgstr "" -"Vous pouvez également trouver plus d'informations sur la personnalisation du " -"chat dans la zone d'administration." -#: ../system/objects/includes/adding-values-hint.include.rst:3 +#: ../system/integrations/exchange.rst:4 msgid "" -"Adding values can be tricky for first timers, don't forget to press \"➕ " -"Add\" after typing your values. Otherwise you may loose a value." +"With Zammad's Exchange integration, you can easily use existing address " +"books without having to update more than one source." msgstr "" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:1 -#: ../system/objects/includes/reposition-values.include.rst:1 -msgid "**↕️ This field type allows the positioning of its values ↔️**" +#: ../system/integrations/exchange.rst:7 +msgid "" +"However, you should refrain from syncing all addresses, as the results may " +"not be what you expect (Exchange collects huge amounts of addresses). A " +"central address book of your company to sync makes more sense, as you can " +"ensure that Zammad gets only the data you need and want. Apart from this, it " +"is even not possible to sync the Global Address List (GAL) of your Exchange " +"system with Zammad." msgstr "" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:3 +#: ../system/integrations/exchange.rst:16 msgid "" -"In order to re-arrange the field values, first edit the field. Then you can " -"use ☰ to drag the values in question to the correct position. If you want to " -"change the layer depth, double click on ☰. With it you can cycle through the " -"available layers." +"**Exchange and LDAP:** The exchange sync can be overruled by Zammad's LDAP " +"integration. If you have the same users in both sources, the LDAP version " +"will always be Zammad's pick." msgstr "" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:8 -msgid "When you're ready, submit your changes to save the object attribute." +#: ../system/integrations/exchange.rst:19 +msgid "" +"**One way sync:** the Exchange sync is one way. Exchange => Zammad. Changes " +"to your users inside of Zammad might be overwritten by the Exchange sync." msgstr "" -#: :0 ../system/objects/types.rst:0 +#: ../system/integrations/exchange.rst:24 msgid "" -"Screencast showing how to re-position values on tree select like\n" -"fields" +"To configure Exchange integration, simply go to the System > Integrations > " +"Exchange in the admin panel. Press \"change\" and follow the wizard for " +"adding the needed Exchange information to Zammad. On the last two steps " +"Zammad will ask you for the address book(s) and your desired attribute " +"mapping. By default, Zammad only maps email address, first- and lastname. " +"Technically, you can map any Exchange object to a Zammad user object (this " +"also works for custom objects!)." msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:3 +#: ../system/integrations/exchange.rst:35 msgid "" -"In order to re-arrange the field values, edit the field and scroll below the " -"values. Make sure to tick the option \"Use custom option sort\"." +"If the SSL verification fails while connecting to Exchange, Zammad will ask " +"you to turn it off temporarily." msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:8 +#: ../system/integrations/exchange.rst:38 msgid "" -"If you do not tick this field, all manual positioning you did above will be " -"lost upon saving! ☠️" +"Please be aware that **turning off SSL verification is a security risk**. It " +"should only be used temporarily or for testing purposes. If turned off, " +"there is no verification of the certificate, which means that every " +"presented certificate will be accepted." msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:11 +#: ../system/integrations/exchange.rst:43 msgid "" -"Now use ☰ to drag the values in question to the correct position. When " -"you're ready, submit your changes to save the object attribute." +"After pressing Continue, Zammad will check if the configuration is okay. You " +"can then enable Exchange and start your first sync. The sync will then run " +"hourly - if you need to change mappings or the address book(s), you can " +"change the configuration at any time." msgstr "" -#: :0 ../system/objects/types.rst:0 -msgid "Screencast showing how to re-position values" +#: ../system/integrations/exchange.rst:50 +msgid "" +"After the sync has finished, you can find the new Exchange contacts under " +"\"Users\". Zammad integrates them just as normal users." msgstr "" -#: ../system/objects/includes/url-template-hint.include.rst:3 +#: ../system/integrations/exchange.rst:55 msgid "" -"This field allows using :ref:`URL fields (Link Templates) `." +"In some cases you might see unique IDs as \"Login\" instead of the email " +"address. This is normal and doesn't affect the login or email mapping for " +"that entry." msgstr "" -#: ../system/objects/permissions.rst:2 -#, fuzzy -msgid "Attribute Permissions" -msgstr "Sessions" - -#: ../system/objects/permissions.rst:7 +#: ../system/integrations/github.rst:4 msgid "" -"In the object attributes configuration you can define if a field is shown " -"and if the input in the field is mandatory, separated by different screens " -"and for different :doc:`roles/permissions `." +"Use GitHub integration to track GitHub issues directly within Zammad " +"tickets. Add issue hyperlinks and get a live summary of metadata like status " +"(open/closed), assignee, labels, and more." msgstr "" -#: ../system/objects/permissions.rst:17 -msgid "Screenshot shows object attribute permission table" +#: ../system/integrations/github.rst:8 +msgid "Please note that our GitHub integration does not support pull requests." msgstr "" -"Capture d'écran montrant le tableau d'autorisations des attributs d'objets" -#: ../system/objects/permissions.rst:17 -msgid "" -"Some of the possible permissions and screen options for a user object " -"attribute." +#: ../system/integrations/github.rst:None +msgid "Integration page for GitHub" msgstr "" -#: ../system/objects/permissions.rst:19 +#: ../system/integrations/github.rst:18 msgid "" -"Based on the object context (ticket, agent, organization, user), the " -"selectable roles (to be precise: the required permissions) and screens " -"differ. Be aware that these settings aren't affecting data creation via " -"other channels than the UI." +"In your GitHub settings, create a new API token under **Developer settings > " +"Personal access tokens > Generate new token**. Leave the **Scopes** section " +"empty." msgstr "" -#: ../system/objects/permissions.rst:24 -msgid "" -"If you want to have further customization possibilities, you should have a " -"look at the :doc:`core workflows `." +#: ../system/integrations/github.rst:0 ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to create a new API token" msgstr "" -#: ../system/objects/permissions.rst:28 -msgid "Screens" +#: ../system/integrations/github.rst:27 +msgid "Create a new API key with no scopes/privileges." msgstr "" -#: ../system/objects/permissions.rst:30 +#: ../system/integrations/github.rst:29 +msgid "🔒 **Will this work for private repos?**" +msgstr "" + +#: ../system/integrations/github.rst:31 msgid "" -"In the table below you can find an overview about the different permissions " -"and the available screens Zammad distinguishes between." +"No. To link private repo issues, **use the** ``repo`` **scope instead**. " +"Bear in mind that the resulting token will have `lots of permissions that it " +"doesn't actually need `_, which presents a security risk if your token ever falls into " +"the wrong hands." msgstr "" -#: ../system/objects/permissions.rst:37 -msgid "Screen" +#: ../system/integrations/github.rst:37 +msgid "" +"Unfortunately, because of how GitHub's OAuth token scopes are set up, this " +"is the only way to link issues on private repos." msgstr "" -#: ../system/objects/permissions.rst:38 -#, fuzzy -msgid "Available for" -msgstr "variable" +#: ../system/integrations/github.rst:40 +msgid "Enter your new API token in Zammad and enable GitHub integration." +msgstr "" -#: ../system/objects/permissions.rst:40 -msgid "create" +#: ../system/integrations/github.rst:0 +msgid "Screencast showing how to configure Zammad's GitHub integration" msgstr "" -#: ../system/objects/permissions.rst:41 ../system/objects/permissions.rst:52 -#: ../system/objects/permissions.rst:59 ../system/objects/permissions.rst:73 -msgid "admin.user" +#: ../system/integrations/github.rst:47 +msgid "" +"Use the default API endpoint (``https://api.github.com/graphql``) unless " +"you're using GitHub Enterprise Server." msgstr "" -#: ../system/objects/permissions.rst:42 ../system/objects/permissions.rst:53 -#: ../system/objects/permissions.rst:60 -#, fuzzy -msgid "admin.organization" -msgstr "Organisation" - -#: ../system/objects/permissions.rst:43 ../system/objects/permissions.rst:54 -#: ../system/objects/permissions.rst:61 -#, fuzzy -msgid "admin.group" -msgstr "groupe" +#: ../system/integrations/github.rst:50 +msgid "" +"Once completed, a new GitHub issues tab will appear in the ticket pane. 🎉" +msgstr "" -#: ../system/objects/permissions.rst:44 -msgid "Creation dialog for not yet existing data" +#: ../system/integrations/github.rst:59 ../system/integrations/gitlab.rst:52 +msgid "Token verification is taking a long time" msgstr "" -#: ../system/objects/permissions.rst:45 -msgid "create_middle" +#: ../system/integrations/github.rst:56 ../system/integrations/gitlab.rst:49 +msgid "" +"Slight delays are normal (<2 min.), especially for systems under heavy load." msgstr "" -#: ../system/objects/permissions.rst:46 ../system/objects/permissions.rst:50 -#: ../system/objects/permissions.rst:57 ../system/objects/permissions.rst:66 -#: ../system/objects/permissions.rst:70 -#, fuzzy -msgid "ticket.customer" -msgstr "Client" +#: ../system/integrations/github.rst:58 +msgid "" +"Self-hosted administrators, please check your network settings to ensure " +"that your Zammad server can reach ``api.github.com``." +msgstr "" -#: ../system/objects/permissions.rst:47 ../system/objects/permissions.rst:51 -#: ../system/objects/permissions.rst:58 ../system/objects/permissions.rst:69 -#, fuzzy -msgid "ticket.agent" -msgstr "priorité" +#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 +msgid "I reloaded the page and now the API token is gone" +msgstr "" -#: ../system/objects/permissions.rst:48 -msgid "Ticket create dialog (middle section)" +#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 +msgid "" +"This may indicate that Zammad is still verifying your API token. Try " +"reloading the page again in a couple minutes." msgstr "" -#: ../system/objects/permissions.rst:49 -msgid "edit" +#: ../system/integrations/gitlab.rst:2 +msgid "GitLab" msgstr "" -#: ../system/objects/permissions.rst:55 -msgid "Editing dialog for already existing data" +#: ../system/integrations/gitlab.rst:4 +msgid "" +"Use GitLab integration to track GitLab issues directly within Zammad " +"tickets. Add issue hyperlinks and get a live summary of metadata like status " +"(open/closed), assignee, labels, and more." msgstr "" -#: ../system/objects/permissions.rst:56 -msgid "view" +#: ../system/integrations/gitlab.rst:8 +msgid "" +"Please note that our GitLab integration does not support merge requests." msgstr "" -#: ../system/objects/permissions.rst:62 -msgid "View-only dialog for already existing data" +#: ../system/integrations/gitlab.rst:None +msgid "Integration page for GitLab" msgstr "" -#: ../system/objects/permissions.rst:64 -msgid "(e.g. user or organization from search)" +#: ../system/integrations/gitlab.rst:18 +msgid "" +"In your GitLab preferences, create a new API token under **Access Tokens**." msgstr "" -#: ../system/objects/permissions.rst:65 -msgid "signup" +#: ../system/integrations/gitlab.rst:20 +msgid "Under **Select scopes**, choose ``read_api`` only." msgstr "" -#: ../system/objects/permissions.rst:67 -msgid "Sign-up screen for new customers" +#: ../system/integrations/gitlab.rst:27 +msgid "🔒 **If you wish to link issues on any private repos...**" msgstr "" -#: ../system/objects/permissions.rst:68 -#, fuzzy -msgid "invite_customer" -msgstr "Client" +#: ../system/integrations/gitlab.rst:29 +msgid "Your API token must belong to an account with access to those repos." +msgstr "" -#: ../system/objects/permissions.rst:71 -msgid "" -"Customer invitation screen (from :doc:`First Steps ` area)" +#: ../system/integrations/gitlab.rst:31 +msgid "Enter your new API token in Zammad and enable GitLab integration." msgstr "" -#: ../system/objects/permissions.rst:72 -msgid "invite_agent" +#: ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to configure Zammad's GitLab integration" msgstr "" -#: ../system/objects/permissions.rst:74 +#: ../system/integrations/gitlab.rst:40 msgid "" -"Agent invitation screen (from :doc:`First Steps ` area)" +"Use the default API endpoint (``https://gitlab.com/api/graphql``) unless " +"you're a self-hosted GitLab user." msgstr "" -#: ../system/objects/permissions.rst:78 -#, fuzzy -msgid "Screen Options" -msgstr "Sociétés" +#: ../system/integrations/gitlab.rst:43 +msgid "" +"Once completed, a new GitLab issues tab will appear in the ticket pane. 🎉" +msgstr "" -#: ../system/objects/permissions.rst:80 +#: ../system/integrations/gitlab.rst:51 msgid "" -"For the different screens you can select \"show\" and \"required\" options." +"Self-hosted administrators, please check your network settings to ensure " +"that your Zammad server can reach ``gitlab.com``." msgstr "" -#: ../system/objects/permissions.rst:82 -msgid "**shown:** Show (check) or hide (uncheck) a field." +#: ../system/integrations/i-doit.rst:2 +msgid "i-doit" msgstr "" -#: ../system/objects/permissions.rst:83 +#: ../system/integrations/i-doit.rst:4 msgid "" -"**required:** Set a field to mandatory (check). Forces users (via UI and " -"API) to populate the field." +"`i-doit `_ is an open-source **configuration " +"management database** - in other words, a tool for keeping tabs on every " +"single piece of your physical and digital infrastructure, from network " +"equipment to virtual machines on down to the faceplates on your rack shelves " +"and more." msgstr "" -#: ../system/objects/types.rst:7 -msgid "Example external data source" +#: ../system/integrations/i-doit.rst:10 +msgid "" +"What's that got to do with Zammad? Well, if you used tickets to track issues " +"with all that hardware, you might start wishing there was a way they could " +"talk to each other." msgstr "" -#: ../system/objects/types.rst:2 -msgid "Attribute types" +#: ../system/integrations/i-doit.rst:14 +msgid "Zammad gives you two:" msgstr "" -#: ../system/objects/types.rst:4 -msgid "" -"When adding a new object attribute, you can choose between the following " -"attribute types." +#: ../system/integrations/i-doit.rst:17 +msgid "1. Add i-doit Links to Zammad Tickets" msgstr "" -#: ../system/objects/types.rst:14 -msgid "" -"You cannot change the attribute format / type as soon as it is applied. If " -"you no longer need an object attribute, consider disabling it instead of " -"removing." +#: ../system/integrations/i-doit.rst:20 ../system/integrations/i-doit.rst:80 +msgid "What Users See" msgstr "" -#: ../system/objects/types.rst:18 -msgid "**What about the translation of my attributes?**" +#: ../system/integrations/i-doit.rst:26 +msgid "i-doit integration in Zammad's ticket pane" msgstr "" -#: ../system/objects/types.rst:20 +#: ../system/integrations/i-doit.rst:26 msgid "" -"For some attribute types you can decide if they should be translatable or " -"not. To be precise, it works only for the selectable fields because the " -"possible choices are known and limited. For the following attribute types, " -"you can set the translatable flag:" +"The i-doit integration will appear under a new 🖨 tab in the ticket pane." msgstr "" -#: ../system/objects/types.rst:25 -msgid "*Boolean field*" +#: ../system/integrations/i-doit.rst:28 +msgid "" +"i-doit integration puts a new tab in Zammad's ticket pane where you can add " +"links to existing i-doit devices for easy reference. (See our :user-docs:" +"`user documentation ` to learn " +"how it works in practice)." msgstr "" -#: ../system/objects/types.rst:26 -msgid "*Single selection field*" +#: ../system/integrations/i-doit.rst:36 ../system/integrations/i-doit.rst:93 +msgid "How to Set it Up" msgstr "" -#: ../system/objects/types.rst:27 -msgid "*Multiple selection field*" +#: ../system/integrations/i-doit.rst:38 +msgid "" +"It requires i-doit's `API Add-on `_. Make sure to have it properly set up. Use the following setting:" msgstr "" -#: ../system/objects/types.rst:28 -msgid "*Single tree selection field*" +#: ../system/integrations/i-doit.rst:42 +msgid "Active: ``Yes``" msgstr "" -#: ../system/objects/types.rst:29 -msgid "*Multiple tree selection field*" +#: ../system/integrations/i-doit.rst:43 +msgid "Enforce authentication by username and password: ``No``" msgstr "" -#: ../system/objects/types.rst:31 +#: ../system/integrations/i-doit.rst:45 msgid "" -"For these types, you can find an additional field *Translate field contents*:" +"To set it up, enable the integration in the Zammad admin panel under " +"**System > Integrations > i-doit**:" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Screenshot showing translatable attribute types" +#: ../system/integrations/i-doit.rst:None +msgid "i-doit settings within the integration pages" msgstr "" -#: ../system/objects/types.rst:38 -msgid "Screenshot with example of translatable attribute type" +#: ../system/integrations/i-doit.rst:53 +msgid "The root URL of your i-doit installation." msgstr "" -#: ../system/objects/types.rst:45 -msgid "Boolean field" +#: ../system/integrations/i-doit.rst:62 +msgid "API token" msgstr "" -#: ../system/objects/types.rst:41 +#: ../system/integrations/i-doit.rst:56 msgid "" -"Provides a drop-down field with display values for ``true`` and ``false``. " -"Setting a default is mandatory." +"Found in the i-doit admin panel under **Interfaces / external data > JSON-" +"RPC API > Common Settings**." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Boolean fields" +#: ../system/integrations/i-doit.rst:0 +msgid "i-doit administration interface with API configuration" msgstr "" -#: ../system/objects/types.rst:55 -msgid "Date field" +#: ../system/integrations/i-doit.rst:67 +msgid "Client ID" msgstr "" -#: ../system/objects/types.rst:48 -msgid "Provides a date picker field and does not allow default values." +#: ../system/integrations/i-doit.rst:65 +msgid "A unique name to identify Zammad within i-doit." msgstr "" -#: ../system/objects/types.rst:52 -msgid "Default time diff (hours)" +#: ../system/integrations/i-doit.rst:67 +msgid "(Zammad does not require you to enter a value here, but i-doit might!)" msgstr "" -#: ../system/objects/types.rst:51 +#: ../system/integrations/i-doit.rst:70 msgid "" -"This setting helps the user by highlighting the day from now plus the " -"provided value. It *does not* pre-fill the field." +"Here you can decide if the certificate of your i-doit system has to be " +"verified or not. In case you are using custom certificates, please have a " +"look at :doc:`how to add them to Zammad `." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Date fields" +#: ../system/integrations/i-doit.rst:77 +msgid "2. List / Create Zammad Tickets in i-doit" msgstr "" -#: ../system/objects/types.rst:73 -msgid "Date & time field" +#: ../system/integrations/i-doit.rst:None +msgid "Zammad integration in i-doit's device view" msgstr "" -#: ../system/objects/types.rst:58 -msgid "Provides a date and time picker – does not allow default values" +#: ../system/integrations/i-doit.rst:86 +msgid "" +"i-doit's ticket system integration gives you a way to see all the tickets " +"for a given device without ever leaving i-doit. (See our :user-docs:`user " +"documentation ` to learn how it " +"works in practice)." msgstr "" -#: ../system/objects/types.rst:62 -msgid "Allow future" +#: ../system/integrations/i-doit.rst:95 +msgid "" +"Enable this integration in the i-doit admin panel under **Interfaces / " +"external data > Trouble Ticket System (TTS) > Configuration**:" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Forbid dates and times in the future." +#: ../system/integrations/i-doit.rst:None +msgid "i-doit administration interface with TTS configuration" msgstr "" -#: ../system/objects/types.rst:66 -msgid "Allow past" +#: ../system/integrations/i-doit.rst:104 +msgid "TTS-Type" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Forbid dates and times in the past." +#: ../system/integrations/i-doit.rst:104 +msgid "``Zammad``" msgstr "" -#: ../system/objects/types.rst:70 -msgid "Default time diff (minutes)" +#: ../system/integrations/i-doit.rst:115 +msgid "Username / Password" msgstr "" -#: ../system/objects/types.rst:69 +#: ../system/integrations/i-doit.rst:107 +msgid "Login credentials for a Zammad agent." +msgstr "" + +#: ../system/integrations/i-doit.rst:109 msgid "" -"This setting helps the user by highlighting the day from now plus the " -"provided value. It does not pre-fill the field." +"This agent must have **read permission** for all :doc:`groups ` that plan on using the i-doit integration." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Date & time fields" +#: ../system/integrations/i-doit.rst:113 +msgid "" +"You may even wish to create a dedicated agent account just for this " +"integration (otherwise, if the agent ever changes her password, you will " +"have to remember to update it here)." msgstr "" -#: ../system/objects/types.rst:86 -msgid "Integer field" +#: ../system/integrations/i-doit.rst:117 +msgid "URL incl. protocol" msgstr "" -#: ../system/objects/types.rst:76 -msgid "" -"Provides an input field that allows integer usage only. You may define a " -"default value. You cannot enforce comma separation." +#: ../system/integrations/i-doit.rst:118 +msgid "``https://your.zammad.domain``" msgstr "" -#: ../system/objects/types.rst:80 -msgid "Minimal" +#: ../system/integrations/index.rst:2 +msgid "Integrations" +msgstr "Intégrations" + +#: ../system/integrations/index.rst:4 +msgid "" +"Zammad offers numerous integrations that add rich features to your instance." msgstr "" -#: ../system/objects/types.rst:80 -msgid "The minimal value the field accepts." +#: ../system/integrations/index.rst:6 +msgid "We're still working on this part of our documentation, stay tight!" msgstr "" -#: ../system/objects/types.rst:83 -msgid "Maximal" +#: ../system/integrations/index.rst:10 +msgid "Integrations for Phone Systems" msgstr "" -#: ../system/objects/types.rst:83 -msgid "The maximum value the field accepts." +#: ../system/integrations/index.rst:14 +msgid "" +"Your VoIP provider or telephony system is not listed? Possibly your provider " +"supports Zammad by using the generic CTI - if you're unsure ask your " +"provider." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Integer fields" +#: ../system/integrations/index.rst:18 +msgid "" +"Provider does not support Zammad? Consider creating a `feature request in " +"the Zammad Community `_." msgstr "" -#: ../system/objects/types.rst:99 -msgid "Multiple selection field" +#: ../system/integrations/index.rst:31 +msgid "Integrations for Authentication and Customers" msgstr "" -#: ../system/objects/types.rst:89 -msgid "" -"Provides a selection field that allows the selection of one or more out of " -"several. This field does allow setting a default value." +#: ../system/integrations/index.rst:44 +msgid "Integrations for Monitoring Systems" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Multiple selection fields" +#: ../system/integrations/index.rst:46 +msgid "This section currently misses the following integrations:" msgstr "" -#: ../system/objects/types.rst:112 -msgid "Single selection field" +#: ../system/integrations/index.rst:48 +msgid "Icinga" msgstr "" -#: ../system/objects/types.rst:102 -msgid "" -"Provides a drop-down field that allows selection of one value out of " -"several. This field does allow setting a default value." +#: ../system/integrations/index.rst:49 +msgid "Monit" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Single selection fields" +#: ../system/integrations/index.rst:50 +msgid "Nagios" msgstr "" -#: ../system/objects/types.rst:142 -msgid "Textarea field" +#: ../system/integrations/index.rst:60 +msgid "Integrations for Issue Trackers" msgstr "" -#: ../system/objects/types.rst:115 -msgid "" -"Provides a text area input field (multiple lines) and thus allows e.g. new " -"lines. You can set a default field value." +#: ../system/integrations/index.rst:70 +msgid "Other Integrations" msgstr "" -#: ../system/objects/types.rst:120 +#: ../system/integrations/index.rst:72 msgid "" -"Please note that this field *does not* support text formatting or HTML " -"content (rich text)." +"This section will hold any other integration that can't be grouped up (yet)." msgstr "" -#: ../system/objects/types.rst:123 -msgid "**🥵 This field can consume a lot of visual space**" +#: ../system/integrations/ldap/index.rst:2 +msgid "LDAP / Active Directory" msgstr "" -#: ../system/objects/types.rst:125 +#: ../system/integrations/ldap/index.rst:4 msgid "" -"Depending on where you use this field type, it may use a lot of visual space " -"if you provide a lot of text. This may be an issue to work with." +"Zammad comes with a powerful LDAP integration that allows you to have a " +"single source of truth. By this you reduce the number of login credentials " +"your user has to remember." msgstr "" -#: ../system/objects/types.rst:130 -msgid "Default" +#: ../system/integrations/ldap/index.rst:10 +msgid "" +"The LDAP source is also a perfect candidate for Zammad's :docs:`Kerberos " +"Single Sign-On ` but also works as addition " +"to other :doc:`/settings/security/third-party`." msgstr "" -#: ../system/objects/types.rst:129 -msgid "" -"The here provided text will be shown within the text area field or new data " -"sets." +#: ../system/integrations/ldap/index.rst:None +msgid "Zammands LDAP management page" msgstr "" -#: ../system/objects/types.rst:134 ../system/objects/types.rst:160 -msgid "Maxlength" +#: ../system/integrations/ldap/index.rst:25 +msgid "📝 :doc:`manage`" msgstr "" -#: ../system/objects/types.rst:0 ../system/objects/types.rst:160 -msgid "You can pick the maximum length of the field." +#: ../system/integrations/ldap/index.rst:25 +msgid "Add, modify, remove or re-arrange your LDAP-Sources as needed." msgstr "" -#: ../system/objects/types.rst:0 -msgid "The default length of this object is ``500``." +#: ../system/integrations/ldap/index.rst:30 +msgid "Before you continue, please note the following limitations." msgstr "" -#: ../system/objects/types.rst:139 -msgid "Rows" +#: ../system/integrations/ldap/index.rst:32 +msgid "Mapping / Synchronizing organizations is not possible" msgstr "" -#: ../system/objects/types.rst:0 +#: ../system/integrations/ldap/index.rst:36 msgid "" -"Change the number of rows to dislay so that you can use only the space you " -"really need." +"You may want to consider using domain based assignments to overcome this " +"issue. Learn more on :doc:`/manage/organizations/index`." msgstr "" -#: ../system/objects/types.rst:0 -msgid "The default number of rows is ``4``." +#: ../system/integrations/ldap/index.rst:39 +msgid "" +"Zammad's LDAP sync is one way. Editing user settings or permissions may be " +"overwritten upon the next sync depending on your configuration." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Textarea fields" +#: ../system/integrations/ldap/index.rst:41 +msgid "Nested groups are not supported." msgstr "" -#: ../system/objects/types.rst:165 -msgid "Text field" +#: ../system/integrations/ldap/index.rst:42 +msgid "Synchronizing user avatars from LDAP is not supported." msgstr "" -#: ../system/objects/types.rst:145 -msgid "Provides a text field (one line) and allows choosing a default value." +#: ../system/integrations/ldap/index.rst:43 +msgid "Unlike user filters, group filters cannot be changed." msgstr "" -#: ../system/objects/types.rst:148 +#: ../system/integrations/ldap/index.rst:44 msgid "" -"Defines the type of the input field. This allows e.g. your browser to ensure " -"that you provide the specific type." +"When a user originates from an LDAP server, Zammad will try to verify the " +"login credentials against LDAP first - if this fails Zammad will check its " +"local database." msgstr "" -#: ../system/objects/types.rst:152 -msgid "Currently available:" +#: ../system/integrations/ldap/index.rst:50 +msgid "" +"Users can have local passwords even if they're LDAP users! You can learn " +"more about user accounts in general on :doc:`/manage/users/index`." msgstr "" -#: ../system/objects/types.rst:155 -msgid "Phone" +#: ../system/integrations/ldap/index.rst:54 +msgid "" +"When several LDAP sources contain the same user (meaning the same email " +"address), the user in question will be updated with every source configured. " +"*The last LDAP source will win.*" msgstr "" -#: ../system/objects/types.rst:156 -msgid "Text" -msgstr "Texte" - -#: ../system/objects/types.rst:157 -msgid "Url *(URL fields disable link-template availability)*" +#: ../system/integrations/ldap/index.rst:58 +msgid "" +"This is subject to change with `Issue 4109 `_ in the future." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Text fields" +#: ../system/integrations/ldap/index.rst:60 +msgid "" +"Synchronization statistics currently affect *all* configured LDAP sources. " +"This also applies for newly added or updated sources." msgstr "" -#: ../system/objects/types.rst:174 -msgid "Single tree selection field" +#: ../system/integrations/ldap/index.rst:63 +msgid "" +"This is subject to change with `Issue 4108 `_ in the future." msgstr "" -#: ../system/objects/types.rst:168 +#: ../system/integrations/ldap/index.rst:65 msgid "" -"Provides a select-like field with up to 6 layers of options. Does not allow " -"setting a default value." +"Zammad currently has limited fallback server support. You can workaround " +"this by providing several sources - however, ensure to have the exact same " +"configuration on your fallback." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Tree Select fields" +#: ../system/integrations/ldap/index.rst:69 +msgid "" +"This is subject to improve with `Issue 4107 `_ in the future." msgstr "" -#: ../system/objects/types.rst:183 -msgid "Multiple tree selection field" +#: ../system/integrations/ldap/index.rst:76 +msgid "" +"This section holds all requests Zammad handled for all LDAP sources. These " +"entries can either contain synchronization information or logins " +"(authentication attempts via Zammad's login interface)." msgstr "" -#: ../system/objects/types.rst:177 +#: ../system/integrations/ldap/index.rst:80 msgid "" -"Provides a select-like field with up to 6 layers of options allowing the " -"selection of multiple values. Does not allow setting a default value." +"By clicking on any request, Zammad will provide even more information. The " +"provided information can be useful when something does not work as expected." msgstr "" -#: ../system/objects/types.rst:302 -msgid "External Data Source field" +#: ../system/integrations/ldap/index.rst:85 +msgid "" +"Especially a LDAP synchronization can cause many log entries. The web " +"interface will always limit the number of shown entries to the last 50 " +"entries." msgstr "" -#: ../system/objects/types.rst:186 +#: ../system/integrations/ldap/index.rst:None msgid "" -"Provides a searchable field which fetches data from an external system. This " -"can be useful if you have data outside of Zammad and don't want to maintain " -"both data sources." +"Screencast showing LDAP integration log entries and a detail view on\n" +"an entry." msgstr "" -#: ../system/objects/types.rst:190 -msgid "The feature works as follows:" +#: ../system/integrations/ldap/manage.rst:2 +msgid "Manage LDAP-Sources" msgstr "" -#: ../system/objects/types.rst:192 +#: ../system/integrations/ldap/manage.rst:6 msgid "" -"Zammad sends a query with a search string (free text from agent or based on " -"a variable) in a pre-defined format (\"Search URL\") to an external system." +"Please keep in mind all current limitations for the LDAP synchronization. " +"This will help to understand scopes of the following operations better." msgstr "" -#: ../system/objects/types.rst:195 -msgid "" -"This external system searches for matches and provides a response as a JSON " -"structure to Zammad." +#: ../system/integrations/ldap/manage.rst:65 +msgid "Add new source" msgstr "" -#: ../system/objects/types.rst:197 +#: ../system/integrations/ldap/manage.rst:10 msgid "" -"Zammad just looks for the defined list and value keys, reads the content and " -"displays the value to the user. There is no search on Zammad side." +"Using the *New Source* button allows you to add new LDAP sources to your " +"installation. You're not limited in the number of sources, however, keep in " +"mind that many sources will also take more time to synchronize." msgstr "" -#: ../system/objects/types.rst:201 +#: ../system/integrations/ldap/manage.rst:14 msgid "" -"The usage of a PostgreSQL database for Zammad is required. In any other " -"case, Zammad will hide the external data source type and you are not able to " -"use it. If you want to use this feature, consider to :docs:`migrate your " -"database `." +"You can choose between different encryption types, namely *SSL* and " +"*STARTTLS* or none of them (\"*No SSL*\"). If you choose *SSL* or " +"*STARTTLS*, Zammad will display an additional *SSL verification* option that " +"allows you to disable the verification, e.g. for self-signed SSL " +"certificates. You can also tell Zammad to use a different port by appending " +"``:`` to your hostname/IP." msgstr "" -#: ../system/objects/types.rst:205 -msgid "Currently, only ``GET`` is supported as request method." +#: ../system/integrations/ldap/manage.rst:0 +msgid "" +"Screenshot of configuring a new LDAP source with SSL encryption and SSL " +"verification" msgstr "" -#: ../system/objects/types.rst:206 +#: ../system/integrations/ldap/manage.rst:26 msgid "" -"The data structure must be in JSON format and provide the objects in an " -"array." +"New Source with SSL transport security enabled and certificate verification" msgstr "" -#: ../system/objects/types.rst:208 +#: ../system/integrations/ldap/manage.rst:30 msgid "" -"The endpoint for the external data source has to support search. On Zammad " -"side, there is no search/logic implemented; however, you can define the " -"output key and value based on the result(s) from the response (which " -"provides already filtered content based on the search)." +"Using an user filter can be a good idea if you only require a small subset " +"of your LDAP users in Zammad." msgstr "" -#: ../system/objects/types.rst:212 -msgid "" -"If you receive more results as expected, your external data source search " -"may not work properly or the structure of the URL is not correct. You should " -"get in touch with a responsible person from the external system." +#: ../system/integrations/ldap/manage.rst:42 +msgid "This especially affects inactive users" msgstr "" -#: ../system/objects/types.rst:217 +#: ../system/integrations/ldap/manage.rst:34 msgid "" -"Please have a look :doc:`at our example `, where you can find a possible configuration for a public " -"dummy endpoint." +"As every LDAP behaves differently on which attributes and how they are set, " +"Zammad doesn't care about any flags." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for external data source fields" +#: ../system/integrations/ldap/manage.rst:37 +msgid "" +"Users that no longer are returned by your LDAP source will automatically be " +"set to inactive. Zammad assumes that the user was deactivated." msgstr "" -#: ../system/objects/types.rst:242 -msgid "Search URL" +#: ../system/integrations/ldap/manage.rst:41 +msgid "" +"Users will never be removed automatically! If you want to remove obsolete " +"users, use :doc:`/system/data-privacy`." msgstr "" -#: ../system/objects/types.rst:227 -msgid "" -"Set your endpoint where Zammad fetches the data. Please make sure to include " -"a valid search :doc:`variable <../variables>` as an URL parameter. Example " -"for a free text search at user input: ``#{search.term}``" +#: ../system/integrations/ldap/manage.rst:46 +msgid "Active Directory admins" msgstr "" -#: ../system/objects/types.rst:232 +#: ../system/integrations/ldap/manage.rst:45 msgid "" -"If in doubt, ask the responsible person for the external data source how " -"they expect the strucuture of the URL." +"Active Directories are quite specific on how to filter for active users only " +"- please see the `Microsoft documentation `_ for more " +"information." msgstr "" -#: ../system/objects/types.rst:236 +#: ../system/integrations/ldap/manage.rst:51 msgid "" -"Depending on your search variable, the preview might work or not. The reason " -"is that the context might not be available and it is no bug." +"*Do not* manually write pathes of either LDAP attributes or groups. If " +"Zammad does not display them, it either cannot find them or you have a lot " +"of users that don't have the attributes populated." msgstr "" -#: ../system/objects/types.rst:239 +#: ../system/integrations/ldap/manage.rst:55 msgid "" -"Please also make sure to use a variable which is available in your object " -"context. For example you won't be able to search for a ticket in a user " -"object context." +"Zammad will always only return attributes that are filled - this reduces the " +"returned list of attributes greatly." msgstr "" -#: ../system/objects/types.rst:252 -#, fuzzy -msgid "SSL Verification" -msgstr "Intégrations" - -#: ../system/objects/types.rst:245 -msgid "Here you can switch the SSL verification to no." +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing how to add a new LDAP source" msgstr "" -#: ../system/objects/types.rst:249 +#: ../system/integrations/ldap/manage.rst:63 msgid "" -"If your external data source system is using self signed certificates, " -"please have a look :doc:`here ` for " -"further information about how to handle them in Zammad, so you can keep the " -"SSL verification activated." +"If your LDAP system doesn't allow anonymous bind, Zammad detects it and " +"provides you an editable \"Base DN\" *text* field instead of a prefilled " +"*select* field." msgstr "" -#: ../system/objects/types.rst:258 -msgid "HTTP Authentication" +#: ../system/integrations/ldap/manage.rst:81 +msgid "Review or edit existing source" msgstr "" -#: ../system/objects/types.rst:255 +#: ../system/integrations/ldap/manage.rst:68 msgid "" -"If your external data source requires an authentication, you can set it " -"here. You can leave it empty or choose between *Basic Authentication* or " -"*Authentication Token* (selecting one of the two methods leads to additional " -"fields where you can enter your credentials/token)." -msgstr "" - -#: ../system/objects/types.rst:265 -msgid "Search result list key" +"Clicking on a LDAP source will provide a configuration and mapping overview." msgstr "" -#: ../system/objects/types.rst:261 +#: ../system/integrations/ldap/manage.rst:70 msgid "" -"Defines the level in the JSON structure which provides the list with search " -"results. You can leave it empty, if the data is already provided as an " -"array. If you have to go deeper in the structure, you can provide a path " -"with ``.`` as separators, e.g. ``key.subkey.sub-sub-key``." +"If needed you can then use the *Change* button to update either the name, " +"active state or the whole configuration. If you're changing the whole " +"configuration, the dialogue will be identical to the source creation." msgstr "" -#: ../system/objects/types.rst:271 -msgid "Search result value key" +#: ../system/integrations/ldap/manage.rst:76 +msgid "" +"Did your LDAP server change? Different LDAP servers have different " +"structures and default attributes. This causes the LDAP synchronization to " +"likely fail. Consider removing the affected source and re-add it." msgstr "" -#: ../system/objects/types.rst:268 -msgid "" -"Defines the attribute in the structure in which your external data source " -"provides the *value* for your data. An example would be a product *number*. " -"If you have to go deeper in the structure, you can provide a path with ``.`` " -"as separators, e.g. ``key.subkey.sub-sub-key``." +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing the update of the source name." msgstr "" -#: ../system/objects/types.rst:277 -msgid "Search result label key" +#: ../system/integrations/ldap/manage.rst:89 +msgid "Re-arrange LDAP source's order" msgstr "" -#: ../system/objects/types.rst:274 +#: ../system/integrations/ldap/manage.rst:84 msgid "" -"Defines the attribute in the structure in which your external data source " -"provides the *label* for your data. An example would be a product *name*. If " -"you have to go deeper in the structure, you can provide a path with ``.`` as " -"separators, e.g. ``key.subkey.sub-sub-key``." +"You can change the synchronization order for each source at any time. Zammad " +"will synchronize the sources from top to bottom." msgstr "" -#: ../system/objects/types.rst:280 +#: ../system/integrations/ldap/manage.rst:0 msgid "" -"In the preview area, you can find the following items (depending on your " -"configuration above):" +"Screencasting showing how to change the source order by using\n" +"drag and drop." msgstr "" -#: ../system/objects/types.rst:283 -msgid "" -"**Error/hint message** (only if configuration is not complete): Zammad tells " -"you, if there is a problem and what you should change in your configuration." +#: ../system/integrations/ldap/manage.rst:101 +msgid "Remove a source" msgstr "" -#: ../system/objects/types.rst:286 +#: ../system/integrations/ldap/manage.rst:92 msgid "" -"**Search field**: search for an existing attribute in the data source to get " -"a preview. This is required for the fields below to show up." +"If you no longer need the a LDAP source or simply want to start over, you " +"can remove them at any time. This will not remove synchronized users, data " +"synchronized or permissions." msgstr "" -#: ../system/objects/types.rst:288 +#: ../system/integrations/ldap/manage.rst:98 msgid "" -"**Search result response** (only if configuration is not complete): here you " -"can find a syntax highlighted JSON preview of the response, based on the " -"search term you entered." +"Not sure if you'd need the source later on? Set the source to inactive " +"instead of removing it - see *Review or edit existing source* for more." msgstr "" -#: ../system/objects/types.rst:291 -msgid "" -"**Search result list** (only if *search result list key* is properly set): " -"output of the structure under the configured *search result list key*." +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing how to remove LDAP sources." msgstr "" -#: ../system/objects/types.rst:294 -msgid "" -"**Preview table** (when fully configured): Zammad shows you a table which " -"includes the found items based on the search string (value, label and " -"optional link). You can use this preview if you don't have the complete data " -"structure of the external system in mind." +#: ../system/integrations/pgp/index.rst:2 +msgid "PGP" msgstr "" -#: ../system/objects/types.rst:299 +#: ../system/integrations/pgp/index.rst:7 msgid "" -"An example of a configured external data source field from agent perspective:" +"Pretty Good Privacy (PGP) is another method for secure email communication. " +"With PGP, you can exchange **signed** and **encrypted** messages with others." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Screencast showing the search for a product in a ticket" +#: ../system/integrations/pgp/index.rst:13 +#: ../system/integrations/smime/index.rst:17 +msgid "Signing" msgstr "" -#: ../system/objects/types.rst:307 -msgid "URL fields (Link-Template)" +#: ../system/integrations/pgp/index.rst:11 +msgid "is a proof that a message hasn't been manipulated on its way." msgstr "" -#: ../system/objects/types.rst:311 +#: ../system/integrations/pgp/index.rst:13 msgid "" -"This function is restricted to Text, Select and External data source types " -"only." +"In other words, it guarantees message **integrity** and **authenticity**." msgstr "" -#: ../system/objects/types.rst:314 -msgid "" -"Link-Templates are an amazing way to dynamically generate URLs. They allow " -"you to integrate other systems better without having to manually copy data " -"from Zammad if possible." +#: ../system/integrations/pgp/index.rst:19 +#: ../system/integrations/smime/index.rst:22 +msgid "Encryption" msgstr "" -#: ../system/objects/types.rst:320 +#: ../system/integrations/pgp/index.rst:16 +#: ../system/integrations/smime/index.rst:20 msgid "" -"Another great way of communicating with another system may be Zammad's :doc:" -"`Webhooks `." +"scrambles a message so that it can only be unscrambled by the intended " +"recipient." msgstr "" -#: ../system/objects/types.rst:323 +#: ../system/integrations/pgp/index.rst:19 msgid "" -"After filling a link-template enabled field, an URL icon will appear on its " -"right. Clicking on the icon opens a new tab." +"In other words, it guarantees message **privacy** and **data security**." msgstr "" -#: ../system/objects/types.rst:328 -msgid "" -"Even though Zammad displays the link template within object edit and create " -"screens, the function is optional. It's only active if you populate the " -"field." +#: ../system/integrations/pgp/index.rst:25 +msgid "Screenshot of ticket creation with encrypt and sign buttons" msgstr "" -#: ../system/objects/types.rst:333 +#: ../system/integrations/pgp/index.rst:25 msgid "" -"What's the difference between URL and text fields with link template...?!" +"Once PGP has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " +"appear in the ticket composer." msgstr "" -#: ../system/objects/types.rst:335 +#: ../system/integrations/pgp/index.rst:28 +msgid "**Sign button not visible?**" +msgstr "" + +#: ../system/integrations/pgp/index.rst:30 msgid "" -"Both fields have different use cases. Use ``text`` type text fields when " -"ever you have a *static* url that requires dynamic parameters. If you " -"require a drag & drop like field that you can put in any URL, use ``URL`` " -"type text fields." +"Please note that the signing of emails is based on the outgoing email " +"account. That means you have to choose a group with a sender email account, " +"which has a private key assigned." msgstr "" -#: ../system/objects/types.rst:340 +#: ../system/integrations/pgp/index.rst:35 +msgid "Handling of Keys" +msgstr "" + +#: ../system/integrations/pgp/index.rst:36 msgid "" -"The difference is easier to spot when comparing the fields directly, below " -"screencast shows the result - the dynamic approach uses existing values in " -"the moment of updating to built the URL - e.g. ``https://google.com/search?" -"q=cookies`` - while the URL approach uses the actual URL of the field - e.g. " -"``https://zammad.com``." +"To use the PGP function, you have to enable the integration (PGP) by " +"switching the toggle to *enabled*." msgstr "" -#: ../system/objects/types.rst:None +#: ../system/integrations/pgp/index.rst:39 msgid "" -"Screencast showing the differents in between URL and text type fields with " -"actual values" +"You can add keys by clicking the *add key* button. The keys can be imported " +"from a file or you can paste the content of the key in the text box." msgstr "" -#: ../system/objects/types.rst:352 -msgid "How does this work...?!" +#: ../system/integrations/pgp/index.rst:42 +msgid "**Which keys do I have to import?**" msgstr "" -#: ../system/objects/types.rst:354 +#: ../system/integrations/pgp/index.rst:44 msgid "" -"As an example, let's say you have an attribute called ``amazing_attribute`` " -"and you want to open a google search directly with the input from that field." +"For **signing** *outgoing* emails, you have to import the private key of " +"your Zammad email account." msgstr "" -#: ../system/objects/types.rst:357 +#: ../system/integrations/pgp/index.rst:47 msgid "" -"Providing the link-template field below allows you to do so: ``https://www." -"google.com/search?q=#{ticket.amazing_attribute}``" +"For **encrypting** *outgoing* emails, you have to import the public key of " +"the customer's email account." msgstr "" -#: ../system/objects/types.rst:362 +#: ../system/integrations/pgp/index.rst:50 msgid "" -"You can use any :doc:`Zammad variable ` as long as it's " -"available in the moment you need it." +"For **verifying the signature** of signed *incoming* emails, you have to " +"import the public key of the customer." msgstr "" -#: ../system/objects/types.rst:365 +#: ../system/integrations/pgp/index.rst:53 msgid "" -"As a result, you are redirected to Google with a search for the value of the " -"attribute, if you click on the button in the ticket (as you can see in the " -"screencast above)." +"For **decrypting** of encrypted *incoming* emails, you have to import the " +"private key of your Zammad email account." msgstr "" -#: ../system/packages.rst:2 -msgid "Packages" -msgstr "Paquets" - -#: ../system/packages.rst:4 -msgid "That's the package management-area." +#: ../system/integrations/pgp/index.rst:57 +msgid "Import Keys From a File" msgstr "" -#: ../system/packages.rst:6 -msgid "Individual add-ons for Zammad can be installed and managed here." +#: ../system/integrations/pgp/index.rst:58 +msgid "You can import keys from a file in the section **Upload key**:" msgstr "" -#: ../system/sessions.rst:2 -msgid "Sessions" -msgstr "Sessions" - -#: ../system/sessions.rst:4 -msgid "" -"Sessions management allows reviewing currently known user sessions and " -"allows to end these. The session timeout is affected by :ref:" -"`security_session_timeout` configurations from security settings." +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of adding a key via file" msgstr "" -#: ../system/sessions.rst:None -msgid "Screenshot showing Zammad's session management" +#: ../system/integrations/pgp/index.rst:64 +msgid "" +"**Supported file formats:** ASCII-armor as well as binary GPG format " +"(basically any GPG supported key format) is supported here." msgstr "" -#: ../system/sessions.rst:13 -msgid "Zammad will provide the following information:" +#: ../system/integrations/pgp/index.rst:68 +msgid "Import Keys by Pasting the Content" msgstr "" -#: ../system/sessions.rst:16 -msgid "" -"The user account this session entry belongs to. It can be normal if a user " -"has several sessions in the list. This can be due to changed browser " -"information or if you use e.g. single sign on methods where the user does " -"not use the log off button." +#: ../system/integrations/pgp/index.rst:69 +msgid "You can also paste the key's content in the section **paste key**:" msgstr "" -#: ../system/sessions.rst:22 -msgid "Browser" +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of adding a key via pasting" msgstr "" -#: ../system/sessions.rst:22 -msgid "The browser agent communicated to Zammad." +#: ../system/integrations/pgp/index.rst:75 +msgid "" +"**Supported format:** Please note that only ASCII-armor is supported here." msgstr "" -#: ../system/sessions.rst:40 +#: ../system/integrations/pgp/index.rst:78 #, fuzzy -msgid "Location" +msgid "Deleting Keys" msgstr "Intégrations" -#: ../system/sessions.rst:25 +#: ../system/integrations/pgp/index.rst:79 msgid "" -"The anticipated location based on the users IP address. Depending on the IP " -"address the result shown may differ. This option depends on :doc:`/settings/" -"system/services`." +"If you want to delete a specific key, you can do it by clicking on the menu " +"in the *actions* column and select **delete**:" msgstr "" -#: ../system/sessions.rst:29 -msgid "The following information can be shown:" +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of deleting a key" msgstr "" -#: ../system/sessions.rst:33 -msgid "IP address" +#: ../system/integrations/pgp/index.rst:88 +msgid "Downloading Keys" msgstr "" -#: ../system/sessions.rst:32 +#: ../system/integrations/pgp/index.rst:89 msgid "" -"Either if you set *Geo IP services* to inactive or you're using internal IP " -"address which do not provide location information." +"If you want to download your keys, you can do this as well via corresponding " +"action buttons. Depending on the key, you can choose wether you want to " +"download the private or the public key." msgstr "" -#: ../system/sessions.rst:40 -msgid "Country (or Country + City)" +#: ../system/integrations/pgp/index.rst:95 +#: ../system/integrations/smime/manage-certificates.rst:76 +msgid "Default Behavior" msgstr "" -#: ../system/sessions.rst:36 +#: ../system/integrations/pgp/index.rst:96 msgid "" -"If *Geo IP services* is enabled only. Depends on how detailed the available " -"IP address information are." +"Here you can adjust on per group basis, if *sign* and *encryption* is on or " +"off by default. Please be aware, that agents can always override the setting " +"for each individual article." msgstr "" -#: ../system/sessions.rst:39 -msgid "" -"Be aware that results can be inaccurate - this technically is not an error." +#: ../system/integrations/pgp/index.rst:None +msgid "Adjusting default behavior on per group basis" msgstr "" -#: ../system/sessions.rst:43 -msgid "Age" +#: ../system/integrations/pgp/index.rst:107 +msgid "" +"Here you can see the last actions regarding signing and encryption and if " +"they were successful." msgstr "" -#: ../system/sessions.rst:43 -msgid "Provides the time when the session initially has been created." +#: ../system/integrations/pgp/index.rst:117 +msgid "**Sign button is not visible, but keys are imported.**" msgstr "" -#: ../system/sessions.rst:50 -msgid "Update" +#: ../system/integrations/pgp/index.rst:115 +msgid "Did you choose a group in the ticket?" msgstr "" -#: ../system/sessions.rst:46 +#: ../system/integrations/pgp/index.rst:116 msgid "" -"Provides the time the user used this session to open Zammad. This timestamp " -"is only updated if the user e.g. reloads, not during normal work on tickets." +"Did you import a private key for the email adress, which is used for " +"outgoing emails in the group?" msgstr "" -#: ../system/sessions.rst:50 -msgid "This timestamp is being used for the session timeout." +#: ../system/integrations/pgp/index.rst:122 +msgid "**How to obtain keys?**" msgstr "" -#: ../system/sessions.rst:53 +#: ../system/integrations/pgp/index.rst:120 msgid "" -"Use the delete button to remove a single session on behalf of your user." +"You can create them yourself! There are some good tutorials on the web on " +"how to create them. Providing keys to Zammad is a prerequisite to use the " +"PGP feature." msgstr "" -#: ../system/subscription/billing.rst:2 -msgid "Billing" +#: ../system/integrations/pgp/index.rst:127 +msgid "**It says a passphrase is needed, but I haven't got one.**" msgstr "" -#: ../system/subscription/billing.rst:4 +#: ../system/integrations/pgp/index.rst:125 msgid "" -"Within the billing tab you can control all billing relevant information like " -"invoices, billing address and the option to cancel your subscription." +"If the key is secured with a passphrase, you have to provide it for the " +"import in Zammad. It is possible that keys may have an empty passphrase. " +"However, this is *not* recommended." msgstr "" -#: ../system/subscription/billing.rst:33 -msgid "Billing information" +#: ../system/integrations/pgp/index.rst:132 +msgid "**How do my customers get my new key?**" msgstr "" -#: ../system/subscription/billing.rst:8 +#: ../system/integrations/pgp/index.rst:130 msgid "" -"All adjusted billing information below only affect future invoices. If your " -"invoice was issued wrong, please contact `our sales team `_." +"You have to provide your **public** key in advance. Your customer also has " +"to configure PGP in their email workflow and import your public key. The " +"other way round, you have to get the public key of your customer and have to " +"import it to Zammad." msgstr "" -#: ../system/subscription/billing.rst:14 -msgid "Billing address" +#: ../system/integrations/slack.rst:2 +msgid "Slack" msgstr "" -#: ../system/subscription/billing.rst:13 -msgid "" -"Provide your company address here, make sure to include the companies name " -"in case required. This address will be referenced on your invoice." +#: ../system/integrations/slack.rst:4 +msgid "**⚠️ Deprecation warning ⚠️**" msgstr "" -#: ../system/subscription/billing.rst:18 -msgid "VAT ID" +#: ../system/integrations/slack.rst:6 +msgid "" +"Zammad 7 will no longer support this dedicated Slack integration. It is " +"recommended to switch to :doc:`pre-defined webhooks ` instead. Existing Slack integrations should " +"be migrated manually before this feature is dropped." msgstr "" -#: ../system/subscription/billing.rst:17 +#: ../system/integrations/slack.rst:14 msgid "" -"Provide your VAT ID here. If applicable your invoice will not contain German " -"VAT. Please make sure to pay the VAT in your country as required." +"In order to use this feature, please add a new Slack app to your Workspace. " +"The App you need is called ``Incoming WebHooks`` ." msgstr "" -#: ../system/subscription/billing.rst:27 -msgid "Billing Email Address" +#: ../system/integrations/slack.rst:18 +msgid "Why Do I Need This Feature?" msgstr "" -#: ../system/subscription/billing.rst:21 +#: ../system/integrations/slack.rst:20 msgid "" -"Usually the instance owner (the person that registered the instance) will " -"receive all emails including the invoices. In case you have your own billing " -"department, you can provide their email address here." +"If you're already using Slack for your team communication, you'll love this " +"feature! Our Slack integration can push ticket notifications about the last " +"ticket article based on the following events:" msgstr "" -#: ../system/subscription/billing.rst:25 -msgid "" -"All billing relevant information will then be sent to this email address." +#: ../system/integrations/slack.rst:24 +msgid "on Ticket creation" msgstr "" -#: ../system/subscription/billing.rst:27 -msgid "Invoices are sent as attachment (PDF) to this email address." +#: ../system/integrations/slack.rst:25 +msgid "on Ticket updates" msgstr "" -#: ../system/subscription/billing.rst:29 -msgid "" -"Don't forget to press the *Submit* button after you changed above settings." +#: ../system/integrations/slack.rst:26 +msgid "on reached reminders" msgstr "" -#: ../system/subscription/billing.rst:0 -msgid "" -"Screenshot showing options for billing information within the\n" -"subscription menu" +#: ../system/integrations/slack.rst:27 +msgid "a Ticket has escalated" msgstr "" -#: ../system/subscription/billing.rst:70 -msgid "Payment history" +#: ../system/integrations/slack.rst:28 +msgid "a Ticket is going to escalate" msgstr "" -#: ../system/subscription/billing.rst:36 +#: ../system/integrations/slack.rst:30 msgid "" -"The payment history will display a history of all paid invoices. At this " -"point you can also download these in case you need them again." +"Zammad will provide the Ticket title, a direct link to the Ticket, the event " +"type (creation, updated, escalation), the customer, time and the last " +"article that has triggered the notification." msgstr "" -#: ../system/subscription/billing.rst:41 +#: ../system/integrations/slack.rst:34 msgid "" -"You will only find *paid* invoices here. Invoices that are to be billed are " -"not available before the payment is completed." -msgstr "" - -#: ../system/subscription/billing.rst:46 -msgid "Date" +"This will give you further options, as you can see e.g. escalating tickets " +"that are assigned to an agent that's e.g. absent. You can interact faster, " +"as you might see problems earlier (or even before the problem gets one)." msgstr "" -#: ../system/subscription/billing.rst:46 -msgid "Date of the invoice creation." +#: ../system/integrations/slack.rst:38 +msgid "" +"If needed and wanted, you can even discuss directly about the topic before " +"sending an answer to the customer. Another possible use case would be a " +"agent monitoring new agents and their answers to tickets." msgstr "" -#: ../system/subscription/billing.rst:49 +#: ../system/integrations/slack.rst:44 #, fuzzy -msgid "Amount" -msgstr "Les comptes" - -#: ../system/subscription/billing.rst:49 -msgid "Invoice total including VAT if applicable." -msgstr "" +msgid "Configure the Integration" +msgstr "Configuration du widget de discussion" -#: ../system/subscription/billing.rst:52 +#: ../system/integrations/slack.rst:46 msgid "" -"Contains contract period (monthly or yearly) and hosted plan for the " -"subscription period in question." -msgstr "" - -#: ../system/subscription/billing.rst:63 -msgid "Payment method / Service period" +"First of all, please go to your slack workspace - go to administration => " +"Manage Apps. If you don't have an app yet, you can simply add a new one - " +"just search for ``Incoming WebHooks`` and customize the app to your needs." msgstr "" -#: ../system/subscription/billing.rst:56 +#: ../system/integrations/slack.rst:50 msgid "" -"Used bank account or credit card as well as the subscription period the " -"invoice is about." +"Choose (or create) the channel Zammad should post it's information to and " +"press on \"Add Incoming WebHooks integration\". If you're ready, copy the " +"provided WebHook URL and go to your Zammad installation." msgstr "" -#: ../system/subscription/billing.rst:61 +#: ../system/integrations/slack.rst:56 msgid "" -"It might happen that the invoice date and subscription period differ. This " -"is nothing to worry about, the subscription periods will be accounted later " -"on." -msgstr "" - -#: ../system/subscription/billing.rst:67 -msgid "Receipt" +"You need administrative rights on the Slack Workspace. The link to the app " +"directory is normally ``https://[workspace-name].slack.com/apps`` ." msgstr "" -#: ../system/subscription/billing.rst:66 +#: ../system/integrations/slack.rst:63 msgid "" -"Use the arrow to download the invoice in question. You can download all " -"available invoices any time you need to here!" +"To configure the slack integration, log in to Zammad and go to Integrations " +"(System) => Slack in the admin panel." msgstr "" -#: ../system/subscription/billing.rst:0 -msgid "Screenshot showing payment history of a hosted instance" +#: ../system/integrations/slack.rst:66 +msgid "" +"Here you can choose on what evens Zammad should post information about a " +"ticket to your Slack channel. Next you need to device what groups shall be " +"affected by this, as anybody with access to that specific Slack channel can " +"read at least parts of the ticket this might be a privacy issue, if you " +"select the wrong groups. The username is simply the name that Zammad uses as " +"display name inside the Slack chat. The channel defines the Slack channel " +"the information is being posted in. As last option, you can set a custom " +"icon for posting to slack." msgstr "" -#: ../system/subscription/billing.rst:94 -msgid "Do you want to cancel your subscription?" +#: ../system/integrations/slack.rst:74 +msgid "" +"When you're ready, just hit \"Submit\" and enable the integration. Zammad " +"will now post new ticket information based on the trigger you chose. Below " +"the options you have the recent log that shows the latest requests to Slack " +"for debugging if needed." msgstr "" -#: ../system/subscription/billing.rst:73 +#: ../system/integrations/slack.rst:81 msgid "" -"In case you no longer want to use Zammad's SaaS, you can cancel your " -"subscription by using the red *Yes, please cancel my subscription* button." +"If you leave the Icon URL empty, Zammad will use the Zammad logo instead. " +"The icon should be a square PNG file." msgstr "" -#: ../system/subscription/billing.rst:76 +#: ../system/integrations/slack.rst:90 msgid "" -"Your subscription will end the day after your trial or billing period ends." +"The following figure shows how it will look if you choose to receive updates " +"on created and updated tickets. On every post Zammad sends to the Slack " +"channel, you can create new threads to discuss about the new article." msgstr "" -#: ../system/subscription/billing.rst:80 +#: ../system/integrations/slack.rst:96 msgid "" -"We will remind you about your cancelled subscription several times up front. " -"After the subscription ended all instance data will be removed. A restore " -"*is not* possible after that point!" +"If you just want to keep track of soon escalating or already escalated " +"tickets, it will look the the following figure. Zammad changes the color in " +"front of the post so you can easily see the state of the ticket." msgstr "" -#: ../system/subscription/billing.rst:0 -msgid "Screencast showing how to cancel a subscription" +#: ../system/integrations/slack.rst:102 +msgid "" +"If you change the state, Zammad will also put information on what state the " +"ticket gets and (if pending state) the date until it pends. You'll also " +"recognize the color codes in front of posts on slack, as they are exact the " +"same the ticket state colors you'll see in Zammad!" msgstr "" -#: ../system/subscription/billing.rst:87 -msgid "**😖 Cancelled by accident?**" +#: ../system/integrations/smime/index.rst:2 +msgid "S/MIME" msgstr "" -#: ../system/subscription/billing.rst:89 +#: ../system/integrations/smime/index.rst:11 msgid "" -"You can always undo the cancellation via the *Yes, undo the cancellation of " -"my subscription* button up to the last subscription day!" +"S/MIME is the most widely-supported method for secure email communication. " +"With S/MIME, you can exchange **signed** and **encrypted** messages with " +"others." msgstr "" -#: ../system/subscription/billing.rst:0 +#: ../system/integrations/smime/index.rst:15 msgid "" -"Screenshot showing a red button to cancel the subscription\n" -"cancellation" +"is proof that a message hasn't been tampered with or sent by an impersonator." msgstr "" -#: ../system/subscription/index.rst:2 -msgid "Subscription (SaaS)" +#: ../system/integrations/smime/index.rst:17 +msgid "" +"In other words, it guarantees a message's **integrity** and **authenticity**." msgstr "" -#: ../system/subscription/index.rst:4 -msgid "" -"The subscription settings page allows you to configure your instances " -"package and number of agents required." +#: ../system/integrations/smime/index.rst:22 +msgid "In other words, it guarantees **privacy** and **data security**." msgstr "" -#: ../system/subscription/index.rst:9 -msgid "" -"This setting section is only available for Hosted setups. If you're looking " -"for on premise support contracts, please see the `Zammad pricing page " -"`_." +#: ../system/integrations/smime/index.rst:28 +msgid "Screencast demo of S/MIME features for both new tickets and replies" msgstr "" -#: ../system/subscription/index.rst:20 +#: ../system/integrations/smime/index.rst:28 msgid "" -"The subscription section currently consists of two tabs: Plan & Billing. For " -"your overview we've divided those two tabs into independent sub pages:" +"Once S/MIME has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " +"appear in the ticket composer." msgstr "" -#: ../system/subscription/index.rst:25 -msgid ":doc:`💰 Subscription plan `" +#: ../system/integrations/smime/index.rst:32 +msgid ":doc:`🔪 Prerequisites `" msgstr "" -#: ../system/subscription/index.rst:24 +#: ../system/integrations/smime/index.rst:31 msgid "" -"Everything affecting your instance subscription functions like number of " -"agents, package and payment method." +"New to S/MIME? This section helps you to find certificate providers and " +"points out Limitations." msgstr "" -#: ../system/subscription/index.rst:28 -msgid ":doc:`🧾 Subscription billing `" +#: ../system/integrations/smime/index.rst:35 +msgid ":doc:`📝 Manage Certificates `" msgstr "" -#: ../system/subscription/index.rst:28 -msgid "" -"Everything regarding billing address, invoices and account cancellation." +#: ../system/integrations/smime/index.rst:35 +msgid "Add and download certificates; configure group default behaviors." msgstr "" -#: ../system/subscription/index.rst:33 -msgid "FAQ" +#: ../system/integrations/smime/index.rst:38 +msgid ":doc:`😦 Troubleshooting `" msgstr "" -#: ../system/subscription/index.rst:37 -msgid "I set up a trial account but am missing functions to test" +#: ../system/integrations/smime/index.rst:38 +msgid "Took a wrong turn? About recent logs and common issues." msgstr "" -#: ../system/subscription/index.rst:36 +#: ../system/integrations/smime/index.rst:43 msgid "" -"The trial instance is running within the professional package allowing up to " -"three agents." +"For more details on how S/MIME integration works on the agent side, see the :" +"user-docs:`user docs `." msgstr "" -#: ../system/subscription/index.rst:40 -msgid "Can I change package within the trial?" +#: ../system/integrations/smime/manage-certificates.rst:2 +msgid "Manage Certificates" msgstr "" -#: ../system/subscription/index.rst:40 -msgid "No. As soon as the package is changed the subscription begins." +#: ../system/integrations/smime/manage-certificates.rst:4 +msgid "" +"S/MIME is **disabled by default**. Enable it to start adding certificates." msgstr "" -#: ../system/subscription/index.rst:45 -msgid "What happens to my trial instance after the trial period ended?" +#: ../system/integrations/smime/manage-certificates.rst:10 +msgid "Dialogue to add new certificates or private keys" msgstr "" -#: ../system/subscription/index.rst:43 +#: ../system/integrations/smime/manage-certificates.rst:10 msgid "" -"Your instance will automatically be canceled for you. Please see *What " -"happens to my instance after it has been canceled?* for more." +"Manage certificates in the Admin Panel under **System > Integrations > S/" +"MIME**. Certificates may be pasted in as plain text or uploaded from a file." msgstr "" -#: ../system/subscription/index.rst:58 -msgid "What happens to my instance after it has been canceled?" -msgstr "" +#: ../system/integrations/smime/manage-certificates.rst:14 +#, fuzzy +msgid "Add Certificate Data" +msgstr "Intégrations" -#: ../system/subscription/index.rst:48 -msgid "That depends slightly on your instance state:" +#: ../system/integrations/smime/manage-certificates.rst:36 +msgid "Add Certificate" msgstr "" -#: ../system/subscription/index.rst:54 -#, fuzzy -msgid "Trial instance" -msgstr "Maintenance" - -#: ../system/subscription/index.rst:51 +#: ../system/integrations/smime/manage-certificates.rst:17 msgid "" -"If you're still on trial, we will ice your instance and remind you once " -"again about your instance. We then will wait some days and remove your " -"instance from our system. This is the last time we will inform you by Email." +"Import public-key certificates for both your own organization and your " +"contacts." msgstr "" -#: ../system/subscription/index.rst:58 -#, fuzzy -msgid "Paid instance" -msgstr "Maintenance" - -#: ../system/subscription/index.rst:57 +#: ../system/integrations/smime/manage-certificates.rst:19 msgid "" -"If you're a paying customer and canceled your subscription, the instance " -"removal will take place the day after your last subscription day." +"You can also add a bunch of certificates in one go by providing a single " +"file with all relevant certificates." msgstr "" -#: ../system/subscription/index.rst:60 -msgid "Can removed instances be restored?" +#: ../system/integrations/smime/manage-certificates.rst:22 +msgid "🕵️ **ALWAYS verify certificates in-person or over the phone!**" msgstr "" -#: ../system/subscription/index.rst:61 -msgid "No. Once your instance has been removed, a restoration is not possible." +#: ../system/integrations/smime/manage-certificates.rst:24 +msgid "" +"The whole point of signatures is to alert you when someone is trying to " +"pretend to be someone they're not. Never accept a certificate from someone " +"online without verifying it first." msgstr "" -#: ../system/subscription/plan.rst:2 ../system/subscription/plan.rst:38 -msgid "Plan" +#: ../system/integrations/smime/manage-certificates.rst:28 +msgid "📇 **What about trusted certificate authorities?**" msgstr "" -#: ../system/subscription/plan.rst:16 -msgid "Subscription" +#: ../system/integrations/smime/manage-certificates.rst:30 +msgid "" +"In some cases (e.g. when dealing with large enterprises), you may be given a " +"certificate for an entire CA, rather than a single contact. Add it here to " +"trust *all* certificates issued by that CA." msgstr "" -#: ../system/subscription/plan.rst:5 +#: ../system/integrations/smime/manage-certificates.rst:35 msgid "" -"On the top of the subscription summary you'll find the number of used and " -"available (booked) agent seats. By using the *see more* link you can also " -"expand an agent list to see the currently configured active agents. This " -"list *does not* count accounts with admin permissions only." +"Commercial CAs can usually be verified online. Zammad does not include a " +"list of built-in, trusted CAs." msgstr "" -#: ../system/subscription/plan.rst:0 -msgid "" -"Within subscription you can always see how many agents are still\n" -"available to add and who uses the seats." +#: ../system/integrations/smime/manage-certificates.rst:57 +msgid "Add Private Key" msgstr "" -#: ../system/subscription/plan.rst:14 +#: ../system/integrations/smime/manage-certificates.rst:39 msgid "" -"Learn more on how to manage your agents in general :doc:`here `." +"Once you've added a public-key certificate, you can import its matching " +"private key." msgstr "" -#: ../system/subscription/plan.rst:19 +#: ../system/integrations/smime/manage-certificates.rst:42 msgid "" -"This section gives you an overview of the available plans and their " -"functions / limits. If you require a more detailed table, check our " -"`detailed pricing table `_ for more." +"Private keys are for **your own organization only**; never ask your contacts " +"for their private keys." msgstr "" -#: ../system/subscription/plan.rst:23 +#: ../system/integrations/smime/manage-certificates.rst:0 msgid "" -"Your selection in this step will decide on the base agent price and e.g. " -"agent limits that might apply in the summary step." +"S/MIME integration showing configured certificates and possible issues with " +"Logging" msgstr "" -#: ../system/subscription/plan.rst:26 +#: ../system/integrations/smime/manage-certificates.rst:50 msgid "" -"The green *Selected* button will also tell you what plan you're currently in." +"A note is displayed on certificates with a matching private key (see line 2)." msgstr "" -#: ../system/subscription/plan.rst:30 -msgid "" -"Trial instances are running at Professional with 3 agents. The plan cannot " -"be changed during the trial for technical reasons, if you require more " -"agents for testing, please contact `our sales team `_ with a reason for the raise request." +#: ../system/integrations/smime/manage-certificates.rst:52 +msgid "📤 **Certificates and private keys must be uploaded separately.**" msgstr "" -#: ../system/subscription/plan.rst:0 +#: ../system/integrations/smime/manage-certificates.rst:54 msgid "" -"Screenshot showing three available packages for a hosted Zammad\n" -"instance" +"If your certificate and private key are bundled together in the same file or " +"PEM block, import it twice (once using each button)." msgstr "" -#: ../system/subscription/plan.rst:83 -msgid "Summary" +#: ../system/integrations/smime/manage-certificates.rst:57 +msgid "Please note that bulk imports of private keys are not possible." msgstr "" -#: ../system/subscription/plan.rst:41 -msgid "" -"In this section you can adjust the settings of the previous selected plan." -msgstr "" +#: ../system/integrations/smime/manage-certificates.rst:60 +#, fuzzy +msgid "Download Certificate Data" +msgstr "Intégrations" -#: ../system/subscription/plan.rst:45 +#: ../system/integrations/smime/manage-certificates.rst:62 msgid "" -"Note that upgrading (more agents, higher package) is always possible, " -"however, downgrading will only happen when your billing period renews." +"You can download the earlier provided certificates and private keys at any " +"time from your Zammad instance." msgstr "" -#: ../system/subscription/plan.rst:49 +#: ../system/integrations/smime/manage-certificates.rst:65 msgid "" -"Upgrading resets your billing period and existing credit will be deducted " -"from the new total." +"Please note that passphrase-protected private keys stay protected and when " +"you download them, you have to know the passphrase to use them after " +"downloading." msgstr "" -#: ../system/subscription/plan.rst:58 -msgid "Billing cycle" +#: ../system/integrations/smime/manage-certificates.rst:73 +msgid "Dialogue to download certificates or private keys" msgstr "" -#: ../system/subscription/plan.rst:53 -msgid "" -"You can choose between either monthly or yearly billing. The price per agent " -"will be cheaper if you decide for yearly billing." +#: ../system/integrations/smime/manage-certificates.rst:73 +msgid "Download stored certificates and their keys" msgstr "" -#: ../system/subscription/plan.rst:56 +#: ../system/integrations/smime/manage-certificates.rst:78 msgid "" -"If you're still trying out things and are unsure of the right package for " -"your instance, you may want to choose monthly first and then upgrade to " -"yearly when you're sure." +"The ticket composer will set all outgoing messages to **signed and " +"encrypted** by default (assuming the required certificates exist)." msgstr "" -#: ../system/subscription/plan.rst:66 -msgid "Plan: (Starter|Professional|Plus) - Agents" +#: ../system/integrations/smime/manage-certificates.rst:82 +msgid "These defaults can be modified on a per-group basis:" msgstr "" -#: ../system/subscription/plan.rst:61 -msgid "Choose the number of agents you require for your instance." +#: ../system/integrations/smime/manage-certificates.rst:None +msgid "Zammad allowing to choose the default behavior on per group basis" msgstr "" -#: ../system/subscription/plan.rst:63 +#: ../system/integrations/smime/manage-certificates.rst:89 msgid "" -"Keep in mind that some packages may have agent limits. Depending on the " -"previous chosen package, you won't be able to exceed specific agent numbers. " -"Also note that setting less agents than currently configured is not possible." -msgstr "" - -#: ../system/subscription/plan.rst:69 -msgid "Total" +"Of course, agents can always manually change these settings on each email " +"they send out." msgstr "" -#: ../system/subscription/plan.rst:69 -msgid "This will be the net total you're going to be billed." +#: ../system/integrations/smime/prerequisites.rst:4 +msgid "A certificate *and* private key for your own organization" msgstr "" -#: ../system/subscription/plan.rst:71 +#: ../system/integrations/smime/prerequisites.rst:6 msgid "" -"By using the *Update subscription* button, the instance package will be " -"adjusted immediately. If you didn't provide a payment method yet, Zammad " -"will request you to provide one at this point." +"(Use this to ✒️ **sign outgoing messages** and 🔓 **decrypt incoming " +"messages**.)" msgstr "" -#: ../system/subscription/plan.rst:77 +#: ../system/integrations/smime/prerequisites.rst:9 msgid "" -"In case you're still within the trial period, this means that the trial will " -"be over immediately!" +"Certificates belonging your contacts, or their issuing certificate authority " +"(CA)" msgstr "" -#: ../system/subscription/plan.rst:80 -msgid "Down- or upgrading during the trial period *is not* possible." +#: ../system/integrations/smime/prerequisites.rst:11 +msgid "" +"(Use these to ✅ **verify incoming message signatures** and 🔒 **encrypt " +"outgoing messages**.)" msgstr "" -#: ../system/subscription/plan.rst:0 -msgid "Screenshot showing payment options and a pricing summary" +#: ../system/integrations/smime/prerequisites.rst:14 +msgid "🙋 **I'm new to S/MIME. Where can I get a certificate?**" msgstr "" -#: ../system/subscription/plan.rst:99 -msgid "Payment method" +#: ../system/integrations/smime/prerequisites.rst:16 +msgid "" +"The easiest way to get certificates is to buy an annual subscription through " +"a commercial CA, such as:" msgstr "" -#: ../system/subscription/plan.rst:86 -msgid "You can pay via credit card or SEPA mandate." +#: ../system/integrations/smime/prerequisites.rst:19 +msgid "" +"`Sectigo (formerly Comodo) `_" msgstr "" -#: ../system/subscription/plan.rst:91 -msgid "Credit card" +#: ../system/integrations/smime/prerequisites.rst:20 +msgid "`Secorio `_" msgstr "" -#: ../system/subscription/plan.rst:89 -msgid "" -"Simply follow the dialogue by clicking *authorize* and confirm -if required " -"by your bank- your consent to Zammad using your card for the payments." +#: ../system/integrations/smime/prerequisites.rst:21 +msgid "`GlobalSign `_" msgstr "" -#: ../system/subscription/plan.rst:95 -msgid "SEPA" +#: ../system/integrations/smime/prerequisites.rst:23 +msgid "(Zammad is not affiliated with these CAs in any way.)" msgstr "" -#: ../system/subscription/plan.rst:94 +#: ../system/integrations/smime/prerequisites.rst:25 msgid "" -"Provide the requested information of the bank account holder and update if " -"you're ready. You'll then receive an email with the SEPA mandate." +"You can also generate your own self-signed certificates, but the process is " +"complicated and usually 🙅 **involves extra work for your contacts**." msgstr "" -#: ../system/subscription/plan.rst:97 +#: ../system/integrations/smime/prerequisites.rst:29 msgid "" -"Technically there's also the possibility to pay via invoice, however - this " -"method only applies to a fairly low number of instances. Please contact `our " -"sales team `_ for more information." +"Bear in mind that 🤝 **S/MIME only works if the other party is using it, too." +"**" msgstr "" -#: ../system/translations.rst:2 -msgid "Translations" -msgstr "Traductions" - -#: ../system/translations.rst:4 -msgid "" -"Translations of Zammad are processed centrally in our `Weblate instance " -"`_. This allows non-developers to review " -"and update translation texts of the language they actually speak." +#: ../system/integrations/smime/prerequisites.rst:32 +msgid "Certificate and Private Key Checks on Upload" msgstr "" -#: ../system/translations.rst:9 +#: ../system/integrations/smime/prerequisites.rst:34 msgid "" -"Your language is in an incomplete translation state or has typos? Please " -"consider helping us in sorting this out! All you need is either a GitHub " -"account or to register directly in our instance." +"The certificate and public key validation is based on the ``X509v3`` " +"extensions." msgstr "" -#: ../system/translations.rst:13 -msgid "" -"Did you know? This is also where the documentation translations are handled. " -"🤓" +#: ../system/integrations/smime/prerequisites.rst:49 +msgid "Uploading a *client certificate*?" msgstr "" -#: ../system/translations.rst:15 -msgid "" -"Have a look in our :docs:`contribution section ` in the system documentation to get started!" +#: ../system/integrations/smime/prerequisites.rst:41 +msgid "The following attributes are required then:" msgstr "" -#: ../system/translations.rst:20 -#, fuzzy -msgid "Local Translations" -msgstr "Traductions" +#: ../system/integrations/smime/prerequisites.rst:39 +msgid "Subject Alternative Name (at least one email address has to be present)" +msgstr "" -#: ../system/translations.rst:22 -msgid "" -"Apart from these system translations, there's still local translations you " -"can manage. This is relevant if you added custom objects that require " -"translations or even custom states and priorities." +#: ../system/integrations/smime/prerequisites.rst:40 +msgid "Key Usage (``Digital Signature`` and/or ``Key Encipherment``)" msgstr "" -#: ../system/translations.rst:None -msgid "Translation management screen within the admin menu" +#: ../system/integrations/smime/prerequisites.rst:41 +msgid "Public key algorithm (either ``RSA`` or ``EC``)" msgstr "" -#: ../system/translations.rst:31 -#, fuzzy -msgid "Updating Translations" -msgstr "Traductions" +#: ../system/integrations/smime/prerequisites.rst:43 +msgid "" +"The Extended Key Usage attribute is optional. If the certificate provides " +"the named attribute, than it must contain the value ``E-mail Protection``." +msgstr "" -#: ../system/translations.rst:33 +#: ../system/integrations/smime/prerequisites.rst:46 msgid "" -"Because of how Zammad ships translations, the only way to update the system " -"translations is to update your Zammad installation. The benefit of this is " -"that you no longer need internet access during a Zammad upgrade as the " -"package has everything it requires already." +"Please note that any usable email adress has to be prefixed with ``email:`` " +"or ``rfc822:``." msgstr "" -#: ../system/translations.rst:39 -msgid "Translation of Custom Objects" +#: ../system/integrations/smime/prerequisites.rst:49 +msgid "The named public key algorithms are mandatory for private keys as well." msgstr "" -#: ../system/translations.rst:41 -msgid "" -"No problem at all! You can customize any translation locally, even if it is " -"not initially provided by the system." +#: ../system/integrations/smime/prerequisites.rst:54 +msgid "Uploading a *CA certificate*?" msgstr "" -#: ../system/translations.rst:44 +#: ../system/integrations/smime/prerequisites.rst:52 msgid "" -"Translation is supported for a broad number of features, including but not " -"limited to custom:" +"In the case of an uploaded CA certificate, providing the value ``CA:TRUE`` " +"in the attribute *Basic Contstraints*, the previously mentioned attributes " +"are not verified." msgstr "" -#: ../system/translations.rst:47 -#, fuzzy -msgid "Object Attributes" -msgstr "Variables Article" - -#: ../system/translations.rst:48 -msgid "Ticket Macros" -msgstr "Automation sur les tickets" - -#: ../system/translations.rst:49 -#, fuzzy -msgid "Ticket Overviews" -msgstr "Aperçus" - -#: ../system/translations.rst:50 -#, fuzzy -msgid "Ticket Priorities" -msgstr "priorité" - -#: ../system/translations.rst:51 -#, fuzzy -msgid "Ticket States" -msgstr "exemple" - -#: ../system/translations.rst:54 -#, fuzzy -msgid "Customizing Translations" -msgstr "Traductions" - -#: ../system/translations.rst:56 +#: ../system/integrations/smime/prerequisites.rst:56 msgid "" -"Within the translation screen, simply click on the **New Translation** " -"button." +"In general, the usage of any expired (``Not After``) or not yet valid (``Not " +"Before``) certificate is denied for outgoing emails." msgstr "" -#: ../system/translations.rst:None -#, fuzzy -msgid "New translation dialog" -msgstr "Boîte de dialogue Nouveau compte de messagerie" +#: ../system/integrations/smime/prerequisites.rst:59 +msgid "Example certificate:" +msgstr "" -#: ../system/translations.rst:62 +#: ../system/integrations/smime/prerequisites.rst:85 msgid "" -"In the dialog you can immediately enter the exact translation source (if you " -"know it) and your custom translation text for it and click **Submit**." +"Please note that Zammad will distrust senders by default. This means that " +"you're always required to provide certificate data, no matter if for signing " +"or encrypting." msgstr "" -#: ../system/translations.rst:65 -msgid "" -"Alternatively, try to search for translation suggestions in the list below. " -"Selecting an item from the list will pre-fill the translation source for you " -"and then you can just enter your custom translation." +#: ../system/integrations/smime/prerequisites.rst:89 +msgid "This is by design and can't be adjusted." msgstr "" -#: ../system/translations.rst:69 +#: ../system/integrations/smime/troubleshooting.rst:4 msgid "" -"The target language will always default to your current language selection. " -"If you need to translate for a different language, simply change the " -"selection before submitting." +"All of the system's latest S/MIME activity is displayed in the **Recent " +"Logs** section." msgstr "" -#: ../system/translations.rst:73 +#: ../system/integrations/smime/troubleshooting.rst:11 +msgid "Sample entries of in- and outgoing S/MIME related emails." +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:11 msgid "" -"All your custom translations will show up in the overview table when added. " -"And they will even persist across Zammad updates!" +"Logs report the status and details of all mail, both incoming and outgoing, " +"that used signing/verification or encryption/decryption." msgstr "" -#: ../system/translations.rst:76 +#: ../system/integrations/smime/troubleshooting.rst:14 msgid "" -"Make sure to reload your browser if a translated string is not displayed." +"This log does **not** include email sent by :doc:`triggers ` or the :doc:`scheduler `. For those, check your " +"``production.log``." msgstr "" -#: ../system/translations.rst:80 -msgid "Reverting to Original Translations" +#: ../system/integrations/smime/troubleshooting.rst:20 +msgid "Common Issues" msgstr "" -#: ../system/translations.rst:82 -msgid "" -"If you want to revert a custom translation to original text, simply use the " -"appropriate action within the row of the overview table." +#: ../system/integrations/smime/troubleshooting.rst:30 +msgid "I received a signed/encrypted email before I set up S/MIME integration" msgstr "" -#: ../system/translations.rst:85 +#: ../system/integrations/smime/troubleshooting.rst:23 msgid "" -"Depending on the type of the translation source, the action has a slightly " -"different name:" +"No problem. Once S/MIME has been enabled and the appropriate certificates " +"have been added, agents will be prompted to retry verification/decryption on " +"matching emails." msgstr "" -#: ../system/translations.rst:88 -msgid "**Reset** for customized system translations" +#: ../system/integrations/smime/troubleshooting.rst:0 +msgid "Screenshot of user prompt to retry decryption" msgstr "" -#: ../system/translations.rst:89 -msgid "**Remove** for customized local translations" +#: ../system/integrations/smime/troubleshooting.rst:38 +msgid "The 🔒 **Encrypt** button is disabled" msgstr "" -#: ../system/translations.rst:91 -msgid "" -"In both cases, the action will remove the customized translation after a " -"confirmation." +#: ../system/integrations/smime/troubleshooting.rst:33 +msgid "Have you added the recipient's certificate?" msgstr "" -#: ../system/translations.rst:None -msgid "Screenshot showing the location of the Remove action" +#: ../system/integrations/smime/troubleshooting.rst:34 +msgid "Are you sure the recipient's certificate is valid?" msgstr "" -#: ../system/translations.rst:99 -#, fuzzy -msgid "Inline Translations" -msgstr "Traductions" - -#: ../system/translations.rst:101 -msgid "" -"If you prefer a more hands-on approach, you can activate the inline or on-" -"screen translation feature by pressing ``ctrl`` + ``alt`` + ``t`` at any " -"time and on any screen." +#: ../system/integrations/smime/troubleshooting.rst:35 +msgid "Have you checked your ``production.log`` for more details?" msgstr "" -#: ../system/translations.rst:105 +#: ../system/integrations/smime/troubleshooting.rst:37 msgid "" -"All customizable translation texts will be highlighted for you on the " -"screen. Just click into the highlighted area and update the text in place." +"If encryption doesn't work in the composer, it won't work in :doc:`triggers " +"` or the :doc:`scheduler ` either!" msgstr "" -#: ../system/translations.rst:None -msgid "Inline translation mode activated for the Overview screen" +#: ../system/integrations/smime/troubleshooting.rst:42 +msgid "The ✅ **Sign** button is disabled" msgstr "" -#: ../system/translations.rst:112 +#: ../system/integrations/smime/troubleshooting.rst:41 msgid "" -"When finished editing, simply press ``ctrl`` + ``alt`` + ``t`` again to " -"deactivate." +"Have you added **both the certificate and private key** for your " +"organization?" msgstr "" -#: ../system/translations.rst:117 +#: ../system/integrations/smime/troubleshooting.rst:42 msgid "" -"Even though it's available on any screen, the inline translation feature " -"requires admin permissions. It works only for the current language " -"selection. If you need to translate a different language, first change the " -"language in your :user-docs:`profile settings `." +"Does the email address on the certificate match the email address of the " +"agent/group composing the email?" msgstr "" -#: ../system/variables.rst:2 -msgid "Variables" -msgstr "Variables" - -#: ../system/variables.rst:4 -msgid "" -"Please note that this is just an overview of available variables. It might " -"be incomplete or variables might not be available within some functions. If " -"you're missing variables or are not sure if something is not working as " -"expected, feel free to ask over at the `Community `_." +#: ../system/integrations/smime/troubleshooting.rst:45 +msgid "Error: “Fingerprint already taken”" msgstr "" -#: ../system/variables.rst:10 -msgid "" -"Variables can be called by typing ``::`` (just like text modules in the " -"frontend), as long as you're in a supported text field within the backend. " -"Zammad will display all variables being available within this context and " -"replace it to the variable as soon as you selected an entry." +#: ../system/integrations/smime/troubleshooting.rst:45 +msgid "Are you sure you haven't added this certificate already?" msgstr "" -#: ../system/variables.rst:15 -msgid "" -"You have an empty field which you referenced and it appears as ``-``? That's " -"currently working as designed - you might want to ensure that these fields " -"always have a value." +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Error: “❌ invalid byte sequence in UTF-8”" msgstr "" -#: ../system/variables.rst:20 -msgid "Variable Categories" +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Please ensure to provide PEM formatted certificate and keys." msgstr "" -#: ../system/variables.rst:31 -msgid "Wait, What About Custom Objects?" +#: ../system/integrations/smime/troubleshooting.rst:49 +msgid "Did you check if the provided file is a valid certificate or key?" msgstr "" -#: ../system/variables.rst:33 -msgid "" -"Good point! Of course, we can't predict what objects you might create, but " -"we can give you a hint on how to put the puzzle together to get your custom " -"values." +#: ../system/integrations/zabbix.rst:2 +msgid "Zabbix Integration" msgstr "" -#: ../system/variables.rst:36 +#: ../system/integrations/zabbix.rst:5 msgid "" -"For this, we'll talk about the inner part of the variable (so everything " -"within ``#{}``), please put the outer part around to have a valid variable. " -"The first part of the variable name consist of the object type. Currently " -"these are:" -msgstr "" - -#: ../system/variables.rst:41 -msgid "Ticket (``ticket``)" +"This guide describes how to integrate your Zabbix 5.4 installation with " +"Zammad using the Zabbix webhook feature. This guide will provide " +"instructions on setting up a media type, a user and an action in Zabbix." msgstr "" -#: ../system/variables.rst:42 -msgid "User (``user``)" +#: ../system/integrations/zabbix.rst:12 +msgid "Zammad with enabled HTTP Token Authentication" msgstr "" -#: ../system/variables.rst:43 -msgid "Organization (``organization``)" +#: ../system/integrations/zabbix.rst:13 +msgid "Zabbix version 5.4 or higher" msgstr "" -#: ../system/variables.rst:44 -msgid "Group (``group``)" +#: ../system/integrations/zabbix.rst:16 +msgid "Setting up a Zammad" msgstr "" -#: ../system/variables.rst:46 -msgid "" -"The second part is the name of the object. This is the name you define " -"during object creation and can be found within the object menu at any time. " -"The first and second part of a variable is divided by a point, e.g.: " -"``ticket.number`` which will in total be ``#{ticket.number}``." +#: ../system/integrations/zabbix.rst:18 +msgid "Enable **API Token Access** in Settings > System > API." msgstr "" -#: ../system/variables.rst:51 +#: ../system/integrations/zabbix.rst:20 msgid "" -"Now, in some situations it's possible that you'll need to use a third part. " -"The best example for such a situation would be a ``select`` or ``tree-" -"select`` field which will by default return the key value, not it's display " -"name. For this, just extend your variable with ``.value``. This will result " -"in ``#{ticket.select.value}``." +"Create a **new user** for a Zabbix alerter with an **email address** and " +"create a personal user token with **ticket.agent** permissions." msgstr "" -#: ../system/variables.rst:60 +#: ../system/integrations/zabbix.rst:24 #, fuzzy -msgid "Using Translated Variables" -msgstr "Traductions" +msgid "Zabbix Webhook Configuration" +msgstr "Intégrations" -#: ../system/variables.rst:62 -msgid "" -"If you want to use a translated variable in triggers or schedulers, you can " -"extend the placeholder like this: ``#{t(ticket.state.name)}``. The ``t`` " -"tells Zammad to search for fitting translated strings. The used output " -"language is based on the system language of Zammad which you can set in the " -"admin panel under :doc:`/settings/branding` or based on the selected locale " -"in the trigger/scheduler edit dialog." +#: ../system/integrations/zabbix.rst:27 +msgid "Create a Global Macro" msgstr "" -#: ../system/variables.rst:69 +#: ../system/integrations/zabbix.rst:29 msgid "" -"A possible use-case: you want to send your customers updates on tickets via " -"trigger or scheduler which should include the state of the ticket. Using the " -"default ``#{ticket.state.name}`` (without the translation flag ``t()``) " -"would lead to the output of the original (english) name of the state." -msgstr "" - -#: ../system/variables.rst:75 -msgid "Date and Time Formatting" +"Before setting up the **Webhook**, you need to setup the global macro " +"**{$ZABBIX.URL}**, which must contain the **URL** to the **Zabbix frontend**." msgstr "" -#: ../system/variables.rst:77 +#: ../system/integrations/zabbix.rst:33 msgid "" -"The system (trigger/scheduler selected) locale and timezone predefines a " -"default format of date and timestamp. This format is customizable by using " -"the ``dt()`` method." -msgstr "" - -#: ../system/variables.rst:79 -msgid "The method arguments are as follows:" -msgstr "" - -#: ../system/variables.rst:81 -msgid "The date or timestamp variable you want to format." +"In the **Administration** > **Media types** section, import the `Template`_." msgstr "" -#: ../system/variables.rst:82 -msgid "The output format string." +#: ../system/integrations/zabbix.rst:38 +msgid "Open the added **Zammad** media type and set:" msgstr "" -#: ../system/variables.rst:83 -msgid "The timezone to apply (optional)." +#: ../system/integrations/zabbix.rst:40 +msgid "**zammad\\_access\\_token** to the your **Personal User Token**" msgstr "" -#: ../system/variables.rst:86 +#: ../system/integrations/zabbix.rst:41 msgid "" -"``#{dt(ticket.updated_at, \"%A %Y-%m-%d %H:%M in the office\", \"Europe/" -"Berlin\")}``" +"**zammad\\_url** to the **frontend URL** of your **Zammad** installation" msgstr "" -#: ../system/variables.rst:87 -msgid "Monday, 2024-03-18 15:31 in the office" +#: ../system/integrations/zabbix.rst:43 +msgid "**zammad\\_customer** to your **Zammad user email**." msgstr "" -#: ../system/variables.rst:89 +#: ../system/integrations/zabbix.rst:44 msgid "" -"If you want to use our example, make sure to paste the string above without " -"formatting (``CTRL+Shift+v``), otherwise it won't work." +"**zammad\\_enable\\_tags** to **true** or **false** to enable or disable " +"trigger tags. **Important**: if you enable tag support, each tag is set with " +"a separate request." msgstr "" -#: ../system/variables.rst:93 -msgid "The following table lists available format directives:" +#: ../system/integrations/zabbix.rst:48 +msgid "" +"If you want to prioritize issues according to **severity** values in Zabbix, " +"you can define mapping parameters:" msgstr "" -#: ../system/variables.rst:99 -msgid "Parameter" +#: ../system/integrations/zabbix.rst:51 +msgid "**severity\\_**: Zammad priority ID" msgstr "" -#: ../system/variables.rst:102 -msgid "``%Y``" +#: ../system/integrations/zabbix.rst:53 +msgid "Click the **Update** button to save the **Webhook** settings." msgstr "" -#: ../system/variables.rst:103 -msgid "Year with 4 digits" +#: ../system/integrations/zabbix.rst:55 +msgid "" +"To receive notifications in **Zammad**, you need to create a **Zabbix user** " +"and add **Media** with the **Zammad** type." msgstr "" -#: ../system/variables.rst:104 -msgid "Use ``%y`` for year with 2 digits" +#: ../system/integrations/zabbix.rst:58 +msgid "" +"For **Send to**: enter any text, as this value is not used, but is required." msgstr "" -#: ../system/variables.rst:105 -msgid "``%m``" +#: ../system/integrations/zabbix.rst:61 +msgid "" +"For more information, use the `Zabbix documentation `_." msgstr "" -#: ../system/variables.rst:106 -msgid "Month of year (as number with zero-padding)" -msgstr "" +#: ../system/maintenance.rst:2 +msgid "Maintenance" +msgstr "Maintenance" -#: ../system/variables.rst:107 -msgid "Use ``%-m`` for month without zero-padding" +#: ../system/maintenance.rst:4 +msgid "" +"Zammad comes with a maintenance mode that you can use for e.g. updating the " +"instance or changing settings while restricting availability and functions." msgstr "" -#: ../system/variables.rst:108 -msgid "``%d``" +#: ../system/maintenance.rst:13 +msgid "Mode" msgstr "" -#: ../system/variables.rst:109 -msgid "Day of month (as number with zero-padding)" +#: ../system/maintenance.rst:8 +msgid "The mode setting allows you to enable or disable the maintenance mode." msgstr "" -#: ../system/variables.rst:110 -msgid "Use ``%e`` for day without zero-padding" +#: ../system/maintenance.rst:10 +msgid "Defaults to *off*." msgstr "" -#: ../system/variables.rst:111 -msgid "``%H``" +#: ../system/maintenance.rst:12 +msgid "" +"The maintenance mode will restrict access to administrative roles only. This " +"means agents and customers are logged off." msgstr "" -#: ../system/variables.rst:112 -msgid "Hour of day in 24h notation with zero-padding" +#: ../system/maintenance.rst:23 +msgid "@Login" msgstr "" -#: ../system/variables.rst:113 -msgid "Use ``%k`` for hour without zero-padding" +#: ../system/maintenance.rst:16 +msgid "" +"This setting allows you to provide a login message within a green banner " +"above the login screen. Click into the green banner in the settings page to " +"adjust your message. To activate the message, activate the *@Login* setting." msgstr "" -#: ../system/variables.rst:114 -msgid "``%I``" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing the default login message within the\n" +"settings page" msgstr "" -#: ../system/variables.rst:115 -msgid "Hour of day in 12h notation with zero-padding" -msgstr "" - -#: ../system/variables.rst:116 +#: ../system/maintenance.rst:26 msgid "" -"Use ``%l`` for hour without zero-padding and ``%p`` / ``%P`` for meridian " -"indicator" +"Send an informative message to **all active sessions**. This comes handy to " +"inform your agents e.g. about mayor outages or to force reloads after " +"configuration changes." msgstr "" -#: ../system/variables.rst:117 -msgid "``%M``" +#: ../system/maintenance.rst:31 +msgid "This is the messages title (slightly bigger than the normal message)." msgstr "" -#: ../system/variables.rst:118 -msgid "Minute of hour" +#: ../system/maintenance.rst:34 +msgid "The text you want to provide to your logged in sessions." msgstr "" -#: ../system/variables.rst:120 -msgid "``%S``" +#: ../system/maintenance.rst:39 +msgid "Reload application" msgstr "" -#: ../system/variables.rst:121 -msgid "Second of Minute" +#: ../system/maintenance.rst:37 +msgid "" +"Selecting this option will change the message acceptance button from *Close* " +"(with nothing happening) to *Continue session*, which forces the application " +"to reload." msgstr "" -#: ../system/variables.rst:123 -msgid "``%A``" +#: ../system/maintenance.rst:43 +msgid "" +"If you have customers that are logged in to Zammad, they'll also be notified " +"if they're active in that moment." msgstr "" -#: ../system/variables.rst:124 -msgid "Weekday name" +#: ../system/maintenance.rst:48 +msgid "Example without reload application" msgstr "" -#: ../system/variables.rst:125 -msgid "Use ``%a`` for abbreviated name or ``%^A`` for uppercase name" +#: ../system/maintenance.rst:52 +msgid "" +"Message setting within Zammad's admin settings without ticket reload " +"application setting." msgstr "" -#: ../system/variables.rst:126 -msgid "``%B``" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing the send message settings without ticket\n" +"reload application set" msgstr "" -#: ../system/variables.rst:127 -msgid "Month name" +#: ../system/maintenance.rst:61 ../system/maintenance.rst:85 +msgid "" +"The modal all other active sessions will see upon pressing *Send to clients*." msgstr "" -#: ../system/variables.rst:128 -msgid "Use ``%b`` for abbreviated name" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing modal caused by maintenance's message\n" +"without reload application ticket" msgstr "" -#: ../system/variables.rst:129 -msgid "``%U``" +#: ../system/maintenance.rst:72 +msgid "Example with reload application" msgstr "" -#: ../system/variables.rst:130 -msgid "Week number of current year" +#: ../system/maintenance.rst:76 +msgid "" +"Message setting within Zammad's admin settings with ticket reload " +"application setting." msgstr "" -#: ../system/variables.rst:131 -msgid "Use ``%W`` for a different calculation method" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing the send message settings with ticket\n" +"reload application set" msgstr "" -#: ../system/variables.rst:134 +#: ../system/maintenance.rst:0 msgid "" -"We support the known format directives for the Ruby built-in method " -"``strftime`` of the ``DateTime`` class. For more information, see `here " -"`_." +"Screenshot showing modal caused by maintenance's message\n" +"with reload application ticket" msgstr "" -#: ../system/variables/article.rst:2 -msgid "Articles" -msgstr "Articles" +#: ../system/monitoring.rst:2 +msgid "Monitoring" +msgstr "Supervision" -#: ../system/variables/article.rst:4 ../system/variables/config.rst:4 -#: ../system/variables/current-user.rst:4 ../system/variables/ticket.rst:4 +#: ../system/monitoring.rst:4 msgid "" -"If you're missing variables or are not sure if something is not working as " -"expected, feel free to ask over at the `Community `_." +"This function is only available in self hosted instances. If you use Zammad " +"in our cloud, we are monitoring the system on our own and take steps to fix " +"potential problems directly." msgstr "" -"Si il vous manque des variables ou si vous pensez que quelque chose ne " -"fonctionne pas comme prévu, n'hésitez pas à demander à la `Communauté " -"`_." -#: ../system/variables/article.rst:6 +#: ../system/monitoring.rst:11 msgid "" -"Below you can find all available ticket article-based variables within " -"Zammad. These can be called via Triggers for example. If you're unsure if " -"Zammad does support variables at the point you're at, you can try to type " -"``::`` to check." +"On the monitoring page, you can see the current health state of Zammad under " +"\"*Current Status*\" at the bottom. This can be useful if you want to have a " +"look if everything is up and running. As an example, you could have a look " +"in the monitoring when you assume that some emails aren't processed from " +"Zammad." msgstr "" -"Ci dessous, vous pourrez trouver l'ensemble des variables des articles de " -"ticket disponibles dans Zammad. Elles peuvent être utilisées via les " -"Déclencheurs par exemple. Pour vous assurer que Zammad supporte les " -"variables à l'endroit où vous vous trouvez, vous pouvez taper ``::`` pour " -"vérifier." -#: ../system/variables/article.rst:9 ../system/variables/config.rst:9 -#: ../system/variables/ticket.rst:9 -msgid "" -"The below list gives you an example what kind of data you can expect, it's " -"not intended to explain the data itself." +#: ../system/monitoring.rst:17 +msgid "**Can't receive an email and the monitoring response is \"healthy\"?**" msgstr "" -"La liste ci-dessous vous donne un exemple du type de données auxquelles vous " -"pouvez vous attendre, elle n'est pas destiné à expliquer les données elles-" -"mêmes." - -#: ../system/variables/article.rst:11 -msgid "Article Variables" -msgstr "Variables Article" - -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "name" -msgstr "nom" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "variable" -msgstr "variable" +#: ../system/monitoring.rst:19 +msgid "" +"Zammad will just inform you about unprocessable emails. This is not the case " +"for oversized emails. You can adjust the maximum email size in :doc:`../" +"channels/email/settings`." +msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "example" -msgstr "exemple" +#: ../system/monitoring.rst:24 +#, fuzzy +msgid "Monitoring API" +msgstr "Supervision" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Web" +#: ../system/monitoring.rst:26 +msgid "" +"Beside the indication in the monitoring page, you can also use an external " +"monitoring tool to monitor Zammad's health. To request the health of Zammad, " +"you need to provide the API key (token) to the external monitoring tool. You " +"can copy the token from the \"*Current Token*\" field as well as the whole " +"API endpoint of your system (\"*Health Check*\" field), in which the API " +"token is already included." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.web}``" +#: ../system/monitoring.rst:37 +msgid "Screenshot showing Current Token and Health Check" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``https://zammad.com`` or empty if not set in user object" +#: ../system/monitoring.rst:37 +msgid "Screenshot showing Token and Health Check" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > VIP" +#: ../system/monitoring.rst:39 +msgid "" +"In addition to that, you can reset the auto-generated token to make sure " +"that already configured monitoring systems won't work anymore. So, please " +"use this \"*Reset*\" button only if you know what you do!" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.vip}``" -msgstr "" +#: ../system/monitoring.rst:44 +#, fuzzy +msgid "Example Output" +msgstr "exemple" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -msgid "``true`` or ``false``" +#: ../system/monitoring.rst:0 +msgid "No issues found" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Phone" +#: ../system/monitoring.rst:48 ../system/monitoring.rst:60 +msgid "**Indicator in Zammad**:" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.phone}``" +#: ../system/monitoring.rst:0 +msgid "Screenshot showing monitoring with no issues" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``+4930123456789`` or empty if not set in user object" +#: ../system/monitoring.rst:54 ../system/monitoring.rst:66 +msgid "**API response**::" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Note" +#: ../system/monitoring.rst:0 +msgid "Issues were found" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.note}``" +#: ../system/monitoring.rst:0 +msgid "Screenshot showing monitoring with issues" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Some note about user`` or empty if not set in user object" -msgstr "" +#: ../system/objects.rst:2 +msgid "Objects" +msgstr "Objets" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Mobile" +#: ../system/objects.rst:4 +msgid "" +"In Zammad you can add your own fields to tickets, users, organizations and " +"even groups (these are called \"objects\"). This can be useful if you need " +"to add further information to a ticket or any other object in Zammad and the " +"information doesn't fit in any existing field." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.mobile}``" +#: ../system/objects.rst:11 +msgid "" +"Try to avoid deleting attributes (and disable them instead) as Zammad might " +"run into unexpected conditions if they are referenced somewhere." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Login" +#: ../system/objects.rst:16 +msgid "" +"Here's an overview of object attributes. On the upper right you can add new " +"attributes. By default, there will be no custom fields - standard attributes " +"will be grayed out, you can't delete or change those. You can edit custom " +"attributes (they are displayed in black font and have a trash bin on the " +"right side) just by clicking on them." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.login}``" +#: ../system/objects.rst:24 +msgid "" +"Attributes you add to Zammad, no matter if they have default values or not, " +"will not update existing information. This means a new ticket field " +"technically will be empty unless you populate it." msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -#: ../system/variables/ticket.rst:1 -msgid "``jdoe``" +#: ../system/objects.rst:28 +msgid "" +"Especially in ticket scope this also means that newly added attributes will " +"be indicated as \"changed\" to agents that view the ticket. This may " +"interfere with Zammad's tabs behavior." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Lastname" +#: ../system/objects.rst:40 +#, fuzzy +msgid "Ordering Attributes" +msgstr "Objets" + +#: ../system/objects.rst:42 +msgid "" +"Since Zammad introduced :doc:`/system/core-workflows` the need to have a " +"custom positioning for attributes has become more important than ever." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.lastname}``" +#: ../system/objects.rst:45 +msgid "" +"To adjust the position of such an attribute, simply click on the attribute " +"entry in question, scroll down and adjust the position number. Please note " +"that you cannot change the positioning of default attributes." msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -#: ../system/variables/ticket.rst:1 -msgid "``Doe`` or empty if not set" +#: ../system/objects.rst:49 +msgid "" +"In case two attributes have the same position value, Zammad will sort " +"alphabetically by name automatically." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Firstname" +#: ../system/objects.rst:None +msgid "" +"Screenshot showing custom attribute entries ordered in between default ones" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.firstname}``" +#: ../system/objects.rst:56 +msgid "Updating Database After Adding or Editing Attributes" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "``Joe`` or empty if not set" +#: ../system/objects.rst:58 +msgid "" +"When adding or changing attributes, Zammad will not apply the changes " +"instantly, but instead shows you the changed attributes first. If you're " +"ready to go, just click on \"Update database\" to apply the changes to " +"Zammad. If you made a mistake or just want to discard your changes, click " +"\"Discard changes\"." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Fax" +#: ../system/objects.rst:64 +msgid "" +"After applying the changes with \"Update Database\", a restart of Zammad is " +"**mandatory**. If you don't perform it, you may experience unexpected " +"behavior or even errors. You may want to do this kind of configuration " +"during maintenance windows." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.fax}``" +#: ../system/objects.rst:72 +msgid "" +"Changes on objects require you to update the database to apply these changes." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Email" +#: ../system/objects.rst:75 +msgid "**🤓 Service restarts can be automated**" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.email}``" +#: ../system/objects.rst:0 +msgid "Hosted environments automatically restart for you." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``jdoe@example.com``" +#: ../system/objects.rst:0 +msgid "" +"If you're using a self-hosted installation you can use :docs:`environment " +"variables `" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Department" -msgstr "" +#: ../system/objects.rst:82 +#, fuzzy +msgid "System Attributes" +msgstr "Variables Article" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.department}``" +#: ../system/objects.rst:84 +msgid "" +"Zammad comes with pre-configured attributes. Some of them can't be edited " +"via UI (or at all). This is required for proper operation of Zammad and not " +"a bug." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Sales`` or empty if not set in user object" +#: ../system/objects.rst:90 +msgid "Ticket State" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Address" +#: ../system/objects.rst:92 +msgid "" +"If the pre-configured states aren't enough for you or you want to change " +"them, you can do so by clicking on the cogwheel icon in the state row in the " +"ticket tab. But you should be careful when changing pre-configured states. " +"This can lead to unwanted behavior in some cases." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.address}``" +#: ../system/objects.rst:None +msgid "Screenshot showing highlighted ticket state attribute" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Some street 1, 12345 Berlin`` or empty if not set in user object" +#: ../system/objects.rst:122 +msgid "Handling of states" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated" +#: ../system/objects.rst:102 +msgid "" +"In the state configuration screen, you can add new states, disable states or " +"change states." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_at}``" +#: ../system/objects.rst:0 +msgid "Screenshot showing table of default ticket states" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``2019-10-08 15:24:47 UTC``" +#: ../system/objects.rst:110 +msgid "" +"To add a new state, click on the \"New Ticket State\" button in the top " +"right corner. To change an existing state, simply click on the affected " +"state. This opens an edit dialog." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Type > Name" +#: ../system/objects.rst:114 +msgid "" +"You can also clone a state or set them to \"Default for new tickets\" or " +"\"Default for follow-ups\" by clicking on the ⁝ action button and select the " +"desired function." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.type.name}``" +#: ../system/objects.rst:118 +msgid "" +"*Default for new tickets* means that this state is used for every newly " +"created ticket." msgstr "" -#: ../system/variables/article.rst:1 +#: ../system/objects.rst:121 msgid "" -"``email`` (`list of article types `_)" +"*Default for follow-ups* means that this state is used if the ticket is re-" +"opened after it was closed." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > To" +#: ../system/objects.rst:171 +msgid "Ticket state in detail" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.to}``" +#: ../system/objects.rst:125 +msgid "" +"Below you can find a description for each field and option. Please head over " +"to the :ref:`example ` to see the edit dialog." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``helpdesk@example.com``" +#: ../system/objects.rst:129 +msgid "" +"This is the name of the state and what you and your agents are seeing when " +"choosing a state somewhere (e.g. in tickets, trigger configuration)." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > TicketID" +#: ../system/objects.rst:137 +msgid "" +"There are different state types you can choose from. By default, Zammad " +"comes with one state per state type." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.ticket_id}``" +#: ../system/objects.rst:140 +msgid "" +"**new**: for states for tickets that are new and it hasn't been worked on " +"them" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``1`` (not ticket number)" +#: ../system/objects.rst:142 +msgid "" +"**open**: for states for tickets that are in progress and agents are working " +"on them" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Subject" +#: ../system/objects.rst:144 +msgid "**merged**: for states for tickets that are merged with other tickets" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.subject}``" +#: ../system/objects.rst:145 +msgid "" +"**pending reminder**: for states for tickets that are in progress and you " +"want to set a reminder. (default example: *pending reminder*)" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``My amazing subject``" +#: ../system/objects.rst:147 +msgid "" +"**pending action**: for states for tickets that are waiting for a specified " +"time and then change their state (default example: *pending close*)" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Sender > Name" +#: ../system/objects.rst:150 +msgid "" +"**closed**: for states for tickets that are finished and do not need to be " +"processed further" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.sender.name}``" +#: ../system/objects.rst:153 +msgid "" +"⚠️ Choosing the correct state type is important! If you are in doubt, have a " +"look on the default states and their types!" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Customer``, ``Agent`` or ``System``" +#: ../system/objects.rst:158 +msgid "Ignore escalation" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Visibility" +#: ../system/objects.rst:157 +msgid "" +"Here you can define whether tickets of this state will count to escalation " +"time or not." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.internal}``" +#: ../system/objects.rst:161 +msgid "" +"You can create a note for the state to inform other admins about the state. " +"This has no effect on tickets." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``false`` or ``true`` (false if not internal)" +#: ../system/objects.rst:165 +msgid "Set the state to *active* or *inactive*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > From" +#: ../system/objects.rst:167 +msgid "" +"it is technically possible to set all states to inactive. To keep Zammad " +"working in such a case, the inactive flag of one of the states is ignored." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.from}``" -msgstr "" +#: ../system/objects.rst:194 +#, fuzzy +msgid "Ticket state example" +msgstr "exemple" -#: ../system/variables/article.rst:1 +#: ../system/objects.rst:174 msgid "" -"``Joe Doe `` may differ, depends on ``FROM`` of send mail" +"Let's assume we want to create a new state which indicates that the ticket " +"has to wait for a response of a third party (e.g. service contractor or " +"manufacturer) and we want to to be able to set a reminder." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Web" +#: ../system/objects.rst:178 +msgid "" +"First we give the new state a proper name. In this example we call it " +"\"waiting for manufacturer\"." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.web}``" +#: ../system/objects.rst:181 +msgid "" +"As state type we choose \"pending reminder\". This indicates that the ticket " +"is still open and we can set a reminder. This reminder can be useful if our " +"manufacturer sometimes isn't responding or we want to remind him to give us " +"an answer." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > VIP" +#: ../system/objects.rst:186 +msgid "" +"We choose \"no\" for \"ignore escalation\" because we want to escalate the " +"tickets even if we are waiting on the manufacturer's feedback." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.vip}``" +#: ../system/objects.rst:189 +msgid "The **result** in the creation dialog will look like this:" msgstr "" +"Le **résultat** final du dialogue de création ressemblera à ce qui suit :" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Phone" +#: ../system/objects.rst:0 +msgid "Screenshot showing ticket state creation dialog with example" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.phone}``" -msgstr "" +#: ../system/objects.rst:199 +#, fuzzy +msgid "Ticket Priority" +msgstr "priorité" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Note" +#: ../system/objects.rst:201 +msgid "" +"If the pre-configured priorities aren't enough for you or you want to change " +"them, you can do so by clicking on the cogwheel icon in the priority row in " +"the ticket tab:" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.note}``" +#: ../system/objects.rst:None +msgid "Screenshot showing highlighted ticket priority attribute" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Mobile" +#: ../system/objects.rst:226 +msgid "Handling of priorities" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.mobile}``" +#: ../system/objects.rst:210 +msgid "" +"In the priority configuration screen, you can add new priorities, disable " +"priorities or change priorities." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Login" +#: ../system/objects.rst:0 +msgid "Screenshot showing table of default ticket priorities" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.login}``" +#: ../system/objects.rst:218 +msgid "" +"To add a new priority, click on the \"New Priority\" button in the top right " +"corner. To change an existing priority, simply click on the affected " +"priority. This opens an edit dialog." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Lastname" +#: ../system/objects.rst:222 +msgid "" +"You can also clone a priority or set them to \"Default for new tickets\" by " +"clicking on the ⁝ action button and select the desired function." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.lastname}``" +#: ../system/objects.rst:225 +msgid "" +"*Default for new tickets* means that this priority is used for every newly " +"created ticket." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Firstname" +#: ../system/objects.rst:248 +msgid "Priorities in detail" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.firstname}``" +#: ../system/objects.rst:229 +msgid "Below you can find a description for each field and option." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Fax" +#: ../system/objects.rst:232 +msgid "" +"This is the name of the priority and what you and your agents are seeing " +"when choosing a priority somewhere (e.g. in tickets, trigger configuration)." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.fax}``" +#: ../system/objects.rst:242 +msgid "Highlight color" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Email" +#: ../system/objects.rst:237 +msgid "" +"Switch between *Low priority* (light blue), *High priority* (red) and - " +"(default). This affects the displayed color for ticket titles in overviews." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.email}``" +#: ../system/objects.rst:241 +msgid "The color options are currently limited to the mentioned options." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Department" +#: ../system/objects.rst:245 +msgid "" +"You can create a note for the priority to inform other admins about the " +"priority. This has no effect on tickets." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.department}``" +#: ../system/objects.rst:249 +msgid "Set the priority to *active* or *inactive*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Address" +#: ../system/objects/external-data-source-example.rst:2 +msgid "External Data Source" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.address}``" +#: ../system/objects/external-data-source-example.rst:4 +msgid "" +"We assume you already had a look on :doc:`types` where you can find a " +"description of the individual fields." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created" +#: ../system/objects/external-data-source-example.rst:7 +msgid "" +"To reproduce this example, choose a category you want to add a custom field, " +"click on *New Attribute* and select *External data source field* under " +"*Format*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_at}``" +#: ../system/objects/external-data-source-example.rst:11 +msgid "" +"Our example story is to fetch data from an external product database. We " +"want to add our products to the tickets so that the products can be searched " +"and chosen from a list and also create a link to the product website." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Cc" +#: ../system/objects/external-data-source-example.rst:16 +msgid "Base configuration" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.cc}``" -msgstr "" - -#: ../system/variables/article.rst:1 -msgid "``jdoe@example.com, company@example.com``" +#: ../system/objects/external-data-source-example.rst:None +msgid "Initial steps to configure external data source object type" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Text" +#: ../system/objects/external-data-source-example.rst:25 +msgid "Name: *product*" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.body}``" +#: ../system/objects/external-data-source-example.rst:26 +msgid "Display: *Product*" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Test`` without formatting (plain)" +#: ../system/objects/external-data-source-example.rst:29 +msgid "External data source configuration" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article Text as HTML (not referenced)" +#: ../system/objects/external-data-source-example.rst:31 +msgid "" +"First, enter the search URL making sure it contains ``#{search.term}`` as a " +"parameter:" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.body_as_html}``" +#: ../system/objects/external-data-source-example.rst:34 +msgid "**Example:** ``https://dummyjson.com/products/search?q=#{search.term}``" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Test`` with formatting" +#: ../system/objects/external-data-source-example.rst:36 +msgid "" +"After that, head down to the preview section and enter a search input for " +"the external data source." msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "Ticket > Article#" -msgstr "" +#: ../system/objects/external-data-source-example.rst:39 +#, fuzzy +msgid "**Example:** ``mac``" +msgstr "exemple" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "``#{ticket.article_count}``" +#: ../system/objects/external-data-source-example.rst:41 +msgid "Then you can find a preview of the response data below:" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``1`` number of ticket articles" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of JSON response based on search term" msgstr "" -#: ../system/variables/config.rst:2 -msgid "Config" -msgstr "Configuration" - -#: ../system/variables/config.rst:6 +#: ../system/objects/external-data-source-example.rst:48 msgid "" -"Below you'll find config related variables. These hold useful configuration " -"information that you can use within e.g. triggers to show necessary " -"information to your customer." -msgstr "" -"Ci-dessous, vous trouverez les variables liées à la configuration. Celles " -"contiennent des informations utiles que vous pouvez utiliser, par exemple, " -"dans un déclencheur pour afficher des informations nécessaires au client." - -#: ../system/variables/config.rst:11 -msgid "Config Variables" -msgstr "Variables Configuration" - -#: ../system/variables/config.rst:1 -msgid "Config > Fully Qualified Domain Name" +"We recommend using the preview to have a look on the structure. There is a " +"top-level element called ``products``. One level below, you can find the " +"attributes ``id`` and ``title``." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.fqdn}``" +#: ../system/objects/external-data-source-example.rst:52 +msgid "**Search result response based on search from example:**" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``zammad.example.com``" +#: ../system/objects/external-data-source-example.rst:119 +msgid "" +"To tell the remote system that the desired data is located below the " +"``products`` level, you have to put it in the field *Search result list key*." msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Ticket Hook" +#: ../system/objects/external-data-source-example.rst:122 +msgid "" +"After inserting ``products`` in the mentioned field, you get an extended " +"preview. You can find an additional box *Search result list* with a JSON " +"structure. This is the same response as before but stripped from the upper " +"``products`` element by the external data source." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.ticket_hook}``" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of JSON response search result list" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``Ticket#``" +#: ../system/objects/external-data-source-example.rst:132 +msgid "" +"Now you need to provide the keys for the search result values and labels. As " +"already mentioned, we are looking for the ``id`` and the ``title`` of our " +"products. If you haven't already, it is now a good time to look at the " +"preview of the *Search result list*." msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > HTTP type" +#: ../system/objects/external-data-source-example.rst:197 +msgid "" +"After locating our two keys, we insert them in *search result value key* " +"(``id``) and in *Search result label key* (``title``)." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.http_type}``" +#: ../system/objects/external-data-source-example.rst:200 +msgid "" +"Basically, we configured the external data source already and we can see a " +"table in the preview section:" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``https`` or ``http``" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of product table based on search term" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > SystemID" +#: ../system/objects/external-data-source-example.rst:208 +msgid "" +"According to our example story, now just the *Link template* is missing." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.system_id}``" +#: ../system/objects/external-data-source-example.rst:210 +msgid "" +"Please note that this is an optional feature. If you don't want to use such " +"links, of course you don't have to configure it." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``31`` (value between 1 and 99)" +#: ../system/objects/external-data-source-example.rst:213 +msgid "" +"We can add now an address where additional product information can be found." msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Organization" +#: ../system/objects/external-data-source-example.rst:215 +msgid "Example: ``https://your_domain.com/q=#{ticket.product}``" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.organization}``" +#: ../system/objects/external-data-source-example.rst:217 +msgid "In the example, the parameter means:" msgstr "" -#: ../system/variables/config.rst:1 -msgid "" -"``Zammad GmbH`` value set in `Branding `_" +#: ../system/objects/external-data-source-example.rst:219 +msgid "``#{}``: \"Frame\" for the insertion of information" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Product Name" +#: ../system/objects/external-data-source-example.rst:220 +msgid "``ticket``: object level, where you create your custom object" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.product_name}``" +#: ../system/objects/external-data-source-example.rst:221 +msgid "``product``: name of the (custom) object" msgstr "" -#: ../system/variables/config.rst:1 +#: ../system/objects/external-data-source-example.rst:223 msgid "" -"``Helpdesk`` value set in `Branding `_" +"After configuring your *Link template*, there will be another column in the " +"preview. Hovering on the icons in the *Link* column will show you where it " +"forwards you." msgstr "" -#: ../system/variables/current-user.rst:2 -msgid "Current User" -msgstr "Utilisateur courant" - -#: ../system/variables/current-user.rst:6 +#: ../system/objects/external-data-source-example.rst:232 msgid "" -"Current user variables always return values of the current user that caused " -"e.g. a trigger to run." +"In our example, one of the links looks like: https://your_domain.com/q=6, " +"where the 6 is the product id." msgstr "" -"Les variables Utilisateur courant retournent toujours les valeurs de " -"l'utilisateur qui a initié l'action, par exemple, lancer un déclencheur." -#: ../system/variables/current-user.rst:8 +#: ../system/objects/external-data-source-example.rst:235 #, fuzzy -msgid "" -"Due to the above fact, these variables are often not (yet) set or available " -"for usage." +msgid "You can find more information regarding the URL in :doc:`types`." msgstr "" -"En raison du fait ci-dessus, ces variables ne sont souvent pas ( encore ) " -"définies ou disponibles." +"Vous pouvez également trouver plus d'informations sur la personnalisation du " +"chat dans la zone d'administration." -#: ../system/variables/current-user.rst:10 +#: ../system/objects/includes/adding-values-hint.include.rst:3 msgid "" -"In situations where e.g. schedulers or triggers run, this most likely is " -"nothing you want to use." +"Adding values can be tricky for first timers, don't forget to press \"➕ " +"Add\" after typing your values. Otherwise you may loose a value." msgstr "" -"Dans des situations où, par exemple, des planificateurs ou des déclencheurs " -"s’exécutent, l'utilisation de ces variables sera à éviter." - -#: ../system/variables/current-user.rst:13 -msgid "Current User Variables" -msgstr "Variables Utilisateur courant" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Web" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:1 +#: ../system/objects/includes/reposition-values.include.rst:1 +msgid "**↕️ This field type allows the positioning of its values ↔️**" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.web}``" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:3 +msgid "" +"In order to re-arrange the field values, first edit the field. Then you can " +"use ☰ to drag the values in question to the correct position. If you want to " +"change the layer depth, double click on ☰. With it you can cycle through the " +"available layers." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``https://zammad.org`` or empty if not set" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:8 +msgid "When you're ready, submit your changes to save the object attribute." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > VIP" +#: :0 ../system/objects/types.rst:0 +msgid "" +"Screencast showing how to re-position values on tree select like\n" +"fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.vip}``" +#: ../system/objects/includes/reposition-values.include.rst:3 +msgid "" +"In order to re-arrange the field values, edit the field and scroll below the " +"values. Make sure to tick the option \"Use custom option sort\"." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``false`` or ``true``" +#: ../system/objects/includes/reposition-values.include.rst:8 +msgid "" +"If you do not tick this field, all manual positioning you did above will be " +"lost upon saving! ☠️" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Web" +#: ../system/objects/includes/reposition-values.include.rst:11 +msgid "" +"Now use ☰ to drag the values in question to the correct position. When " +"you're ready, submit your changes to save the object attribute." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.web}``" +#: :0 ../system/objects/types.rst:0 +msgid "Screencast showing how to re-position values" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > VIP" +#: ../system/objects/includes/url-template-hint.include.rst:3 +msgid "" +"This field allows using :ref:`URL fields (Link Templates) `." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.vip}``" -msgstr "" +#: ../system/objects/permissions.rst:2 +#, fuzzy +msgid "Attribute Permissions" +msgstr "Sessions" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Phone" +#: ../system/objects/permissions.rst:7 +msgid "" +"In the object attributes configuration you can define if a field is shown " +"and if the input in the field is mandatory, separated by different screens " +"and for different :doc:`roles/permissions `." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.phone}``" +#: ../system/objects/permissions.rst:17 +msgid "Screenshot shows object attribute permission table" msgstr "" +"Capture d'écran montrant le tableau d'autorisations des attributs d'objets" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``004930123456789`` or empty if not set" +#: ../system/objects/permissions.rst:17 +msgid "" +"Some of the possible permissions and screen options for a user object " +"attribute." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Note" +#: ../system/objects/permissions.rst:19 +msgid "" +"Based on the object context (ticket, agent, organization, user), the " +"selectable roles (to be precise: the required permissions) and screens " +"differ. Be aware that these settings aren't affecting data creation via " +"other channels than the UI." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.note}``" +#: ../system/objects/permissions.rst:24 +msgid "" +"If you want to have further customization possibilities, you should have a " +"look at the :doc:`core workflows `." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Some note to this user`` or empty if not set" +#: ../system/objects/permissions.rst:28 +msgid "Screens" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Mobile" +#: ../system/objects/permissions.rst:30 +msgid "" +"In the table below you can find an overview about the different permissions " +"and the available screens Zammad distinguishes between." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.mobile}``" +#: ../system/objects/permissions.rst:37 +msgid "Screen" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``0049176123456789`` or empty if not set" -msgstr "" +#: ../system/objects/permissions.rst:38 +#, fuzzy +msgid "Available for" +msgstr "variable" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Login" +#: ../system/objects/permissions.rst:40 +msgid "create" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.login}``" +#: ../system/objects/permissions.rst:41 ../system/objects/permissions.rst:52 +#: ../system/objects/permissions.rst:59 ../system/objects/permissions.rst:73 +msgid "admin.user" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Lastname" -msgstr "" +#: ../system/objects/permissions.rst:42 ../system/objects/permissions.rst:53 +#: ../system/objects/permissions.rst:60 +#, fuzzy +msgid "admin.organization" +msgstr "Organisation" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.lastname}``" -msgstr "" +#: ../system/objects/permissions.rst:43 ../system/objects/permissions.rst:54 +#: ../system/objects/permissions.rst:61 +#, fuzzy +msgid "admin.group" +msgstr "groupe" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Firstname" +#: ../system/objects/permissions.rst:44 +msgid "Creation dialog for not yet existing data" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.firstname}``" +#: ../system/objects/permissions.rst:45 +msgid "create_middle" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``John`` or empty if not set" -msgstr "" +#: ../system/objects/permissions.rst:46 ../system/objects/permissions.rst:50 +#: ../system/objects/permissions.rst:57 ../system/objects/permissions.rst:66 +#: ../system/objects/permissions.rst:70 +#, fuzzy +msgid "ticket.customer" +msgstr "Client" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Fax" -msgstr "" +#: ../system/objects/permissions.rst:47 ../system/objects/permissions.rst:51 +#: ../system/objects/permissions.rst:58 ../system/objects/permissions.rst:69 +#, fuzzy +msgid "ticket.agent" +msgstr "priorité" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.fax}``" +#: ../system/objects/permissions.rst:48 +msgid "Ticket create dialog (middle section)" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``004930123464789`` or empty if not set" +#: ../system/objects/permissions.rst:49 +msgid "edit" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Email" +#: ../system/objects/permissions.rst:55 +msgid "Editing dialog for already existing data" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.email}``" +#: ../system/objects/permissions.rst:56 +msgid "view" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``jdoe@customer.tld``" +#: ../system/objects/permissions.rst:62 +msgid "View-only dialog for already existing data" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Department" +#: ../system/objects/permissions.rst:64 +msgid "(e.g. user or organization from search)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.department}``" +#: ../system/objects/permissions.rst:65 +msgid "signup" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Sales`` or empty if not set" +#: ../system/objects/permissions.rst:67 +msgid "Sign-up screen for new customers" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Avatar" -msgstr "" +#: ../system/objects/permissions.rst:68 +#, fuzzy +msgid "invite_customer" +msgstr "Client" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.avatar(60,60)}``" +#: ../system/objects/permissions.rst:71 +msgid "" +"Customer invitation screen (from :doc:`First Steps ` area)" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "avatar picture with width and height in pixel (e.g. 60,60)" +#: ../system/objects/permissions.rst:72 +msgid "invite_agent" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Address" +#: ../system/objects/permissions.rst:74 +msgid "" +"Agent invitation screen (from :doc:`First Steps ` area)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.address}``" -msgstr "" +#: ../system/objects/permissions.rst:78 +#, fuzzy +msgid "Screen Options" +msgstr "Sociétés" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Some street 1, 12345 Berlin`` or empty if not set" +#: ../system/objects/permissions.rst:80 +msgid "" +"For the different screens you can select \"show\" and \"required\" options." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated at" +#: ../system/objects/permissions.rst:82 +msgid "**shown:** Show (check) or hide (uncheck) a field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_at}``" +#: ../system/objects/permissions.rst:83 +msgid "" +"**required:** Set a field to mandatory (check). Forces users (via UI and " +"API) to populate the field." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC``" +#: ../system/objects/types.rst:7 +msgid "Example external data source" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Phone" +#: ../system/objects/types.rst:2 +msgid "Attribute types" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.phone}``" +#: ../system/objects/types.rst:4 +msgid "" +"When adding a new object attribute, you can choose between the following " +"attribute types." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Shared organization" +#: ../system/objects/types.rst:14 +msgid "" +"You cannot change the attribute format / type as soon as it is applied. If " +"you no longer need an object attribute, consider disabling it instead of " +"removing." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.shared}``" +#: ../system/objects/types.rst:18 +msgid "**What about the translation of my attributes?**" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Note" +#: ../system/objects/types.rst:20 +msgid "" +"For some attribute types you can decide if they should be translatable or " +"not. To be precise, it works only for the selectable fields because the " +"possible choices are known and limited. For the following attribute types, " +"you can set the translatable flag:" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.note}``" +#: ../system/objects/types.rst:25 +msgid "*Boolean field*" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``A note to the organization of the user`` or empty if not set" +#: ../system/objects/types.rst:26 +msgid "*Single selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Name" +#: ../system/objects/types.rst:27 +msgid "*Multiple selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.name}``" +#: ../system/objects/types.rst:28 +msgid "*Single tree selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``Zammad GmbH``" +#: ../system/objects/types.rst:29 +msgid "*Multiple tree selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Domain based assignment" +#: ../system/objects/types.rst:31 +msgid "" +"For these types, you can find an additional field *Translate field contents*:" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.domain_assignment}``" +#: ../system/objects/types.rst:0 +msgid "Screenshot showing translatable attribute types" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Domain" +#: ../system/objects/types.rst:38 +msgid "Screenshot with example of translatable attribute type" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.domain}``" +#: ../system/objects/types.rst:45 +msgid "Boolean field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``zammad.com`` or empty if not set" +#: ../system/objects/types.rst:41 +msgid "" +"Provides a drop-down field with display values for ``true`` and ``false``. " +"Setting a default is mandatory." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > VIP" +#: ../system/objects/types.rst:0 +msgid "Available settings for Boolean fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.vip}``" +#: ../system/objects/types.rst:55 +msgid "Date field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Note" +#: ../system/objects/types.rst:48 +msgid "Provides a date picker field and does not allow default values." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.note}``" +#: ../system/objects/types.rst:52 +msgid "Default time diff (hours)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Mobile" +#: ../system/objects/types.rst:51 +msgid "" +"This setting helps the user by highlighting the day from now plus the " +"provided value. It *does not* pre-fill the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.mobile}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Date fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Login" +#: ../system/objects/types.rst:73 +msgid "Date & time field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.login}``" +#: ../system/objects/types.rst:58 +msgid "Provides a date and time picker – does not allow default values" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Lastname" +#: ../system/objects/types.rst:62 +msgid "Allow future" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.lastname}``" +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the future." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Firstname" +#: ../system/objects/types.rst:66 +msgid "Allow past" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.firstname}``" +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the past." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Fax" +#: ../system/objects/types.rst:70 +msgid "Default time diff (minutes)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.fax}``" +#: ../system/objects/types.rst:69 +msgid "" +"This setting helps the user by highlighting the day from now plus the " +"provided value. It does not pre-fill the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Email" +#: ../system/objects/types.rst:0 +msgid "Available settings for Date & time fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.email}``" +#: ../system/objects/types.rst:86 +msgid "Integer field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Department" +#: ../system/objects/types.rst:76 +msgid "" +"Provides an input field that allows integer usage only. You may define a " +"default value. You cannot enforce comma separation." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.department}``" +#: ../system/objects/types.rst:80 +msgid "Minimal" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Web" +#: ../system/objects/types.rst:80 +msgid "The minimal value the field accepts." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.web}``" +#: ../system/objects/types.rst:83 +msgid "Maximal" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > VIP" +#: ../system/objects/types.rst:83 +msgid "The maximum value the field accepts." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.vip}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Integer fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Phone" +#: ../system/objects/types.rst:99 +msgid "Multiple selection field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.phone}``" +#: ../system/objects/types.rst:89 +msgid "" +"Provides a selection field that allows the selection of one or more out of " +"several. This field does allow setting a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Note" +#: ../system/objects/types.rst:0 +msgid "Available settings for Multiple selection fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.note}``" +#: ../system/objects/types.rst:112 +msgid "Single selection field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Mobile" +#: ../system/objects/types.rst:102 +msgid "" +"Provides a drop-down field that allows selection of one value out of " +"several. This field does allow setting a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.mobile}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Single selection fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Login" +#: ../system/objects/types.rst:142 +msgid "Textarea field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.login}``" +#: ../system/objects/types.rst:115 +msgid "" +"Provides a text area input field (multiple lines) and thus allows e.g. new " +"lines. You can set a default field value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Lastname" +#: ../system/objects/types.rst:120 +msgid "" +"Please note that this field *does not* support text formatting or HTML " +"content (rich text)." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.lastname}``" +#: ../system/objects/types.rst:123 +msgid "**🥵 This field can consume a lot of visual space**" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Firstname" +#: ../system/objects/types.rst:125 +msgid "" +"Depending on where you use this field type, it may use a lot of visual space " +"if you provide a lot of text. This may be an issue to work with." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.firstname}``" +#: ../system/objects/types.rst:130 +msgid "Default" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Fax" +#: ../system/objects/types.rst:129 +msgid "" +"The here provided text will be shown within the text area field or new data " +"sets." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.fax}``" +#: ../system/objects/types.rst:134 ../system/objects/types.rst:160 +msgid "Maxlength" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Email" +#: ../system/objects/types.rst:0 ../system/objects/types.rst:160 +msgid "You can pick the maximum length of the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.email}``" +#: ../system/objects/types.rst:0 +msgid "The default length of this object is ``500``." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Department" +#: ../system/objects/types.rst:139 +msgid "Rows" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.department}``" +#: ../system/objects/types.rst:0 +msgid "" +"Change the number of rows to dislay so that you can use only the space you " +"really need." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Avatar" +#: ../system/objects/types.rst:0 +msgid "The default number of rows is ``4``." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.avatar(60,60)}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Textarea fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Address" +#: ../system/objects/types.rst:165 +msgid "Text field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.address}``" +#: ../system/objects/types.rst:145 +msgid "Provides a text field (one line) and allows choosing a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created at" +#: ../system/objects/types.rst:148 +msgid "" +"Defines the type of the input field. This allows e.g. your browser to ensure " +"that you provide the specific type." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_at}``" +#: ../system/objects/types.rst:152 +msgid "Currently available:" msgstr "" -#: ../system/variables/current-user.rst:1 -#, fuzzy -msgid "Current User > Avatar" -msgstr "Utilisateur courant" +#: ../system/objects/types.rst:155 +msgid "Phone" +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.avatar(60,60)}``" +#: ../system/objects/types.rst:156 +msgid "Text" +msgstr "Texte" + +#: ../system/objects/types.rst:157 +msgid "Url *(URL fields disable link-template availability)*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Address" +#: ../system/objects/types.rst:0 +msgid "Available settings for Text fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.address}``" +#: ../system/objects/types.rst:174 +msgid "Single tree selection field" msgstr "" -#: ../system/variables/ticket.rst:6 +#: ../system/objects/types.rst:168 msgid "" -"Below you can find all available ticket-based variables within Zammad. These " -"can be called via Triggers for example. If you're unsure if Zammad does " -"support variables at the point you're at, you can try to type ``::`` to " -"check." +"Provides a select-like field with up to 6 layers of options. Does not allow " +"setting a default value." msgstr "" -#: ../system/variables/ticket.rst:12 -msgid "Ticket Variables" +#: ../system/objects/types.rst:0 +msgid "Available settings for Tree Select fields" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Web" +#: ../system/objects/types.rst:183 +msgid "Multiple tree selection field" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.web}``" +#: ../system/objects/types.rst:177 +msgid "" +"Provides a select-like field with up to 6 layers of options allowing the " +"selection of multiple values. Does not allow setting a default value." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > VIP" +#: ../system/objects/types.rst:302 +msgid "External Data Source field" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.vip}``" +#: ../system/objects/types.rst:186 +msgid "" +"Provides a searchable field which fetches data from an external system. This " +"can be useful if you have data outside of Zammad and don't want to maintain " +"both data sources." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Phone" +#: ../system/objects/types.rst:190 +msgid "The feature works as follows:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.phone}``" +#: ../system/objects/types.rst:192 +msgid "" +"Zammad sends a query with a search string (free text from agent or based on " +"a variable) in a pre-defined format (\"Search URL\") to an external system." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Note" +#: ../system/objects/types.rst:195 +msgid "" +"This external system searches for matches and provides a response as a JSON " +"structure to Zammad." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.note}``" +#: ../system/objects/types.rst:197 +msgid "" +"Zammad just looks for the defined list and value keys, reads the content and " +"displays the value to the user. There is no search on Zammad side." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Mobile" +#: ../system/objects/types.rst:201 +msgid "" +"The usage of a PostgreSQL database for Zammad is required. In any other " +"case, Zammad will hide the external data source type and you are not able to " +"use it. If you want to use this feature, consider to :docs:`migrate your " +"database `." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.mobile}``" +#: ../system/objects/types.rst:205 +msgid "Currently, only ``GET`` is supported as request method." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Login" +#: ../system/objects/types.rst:206 +msgid "" +"The data structure must be in JSON format and provide the objects in an " +"array." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.login}``" +#: ../system/objects/types.rst:208 +msgid "" +"The endpoint for the external data source has to support search. On Zammad " +"side, there is no search/logic implemented; however, you can define the " +"output key and value based on the result(s) from the response (which " +"provides already filtered content based on the search)." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Lastname" +#: ../system/objects/types.rst:212 +msgid "" +"If you receive more results as expected, your external data source search " +"may not work properly or the structure of the URL is not correct. You should " +"get in touch with a responsible person from the external system." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.lastname}``" +#: ../system/objects/types.rst:217 +msgid "" +"Please have a look :doc:`at our example `, where you can find a possible configuration for a public " +"dummy endpoint." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Firstname" +#: ../system/objects/types.rst:0 +msgid "Available settings for external data source fields" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.firstname}``" +#: ../system/objects/types.rst:242 +msgid "Search URL" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Fax" +#: ../system/objects/types.rst:227 +msgid "" +"Set your endpoint where Zammad fetches the data. Please make sure to include " +"a valid search :doc:`variable ` as an URL parameter. " +"Example for a free text search at user input: ``#{search.term}``" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.fax}``" +#: ../system/objects/types.rst:232 +msgid "" +"If in doubt, ask the responsible person for the external data source how " +"they expect the structure of the URL." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Email" +#: ../system/objects/types.rst:236 +msgid "" +"Depending on your search variable, the preview might work or not. The reason " +"is that the context might not be available and it is no bug." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.email}``" +#: ../system/objects/types.rst:239 +msgid "" +"Please also make sure to use a variable which is available in your object " +"context. For example you won't be able to search for a ticket in a user " +"object context." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Department" -msgstr "" +#: ../system/objects/types.rst:252 +#, fuzzy +msgid "SSL Verification" +msgstr "Intégrations" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.department}``" +#: ../system/objects/types.rst:245 +msgid "Here you can switch the SSL verification to no." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Avatar" +#: ../system/objects/types.rst:249 +msgid "" +"If your external data source system is using self signed certificates, " +"please have a look :doc:`here ` for " +"further information about how to handle them in Zammad, so you can keep the " +"SSL verification activated." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.avatar(60,60)}``" +#: ../system/objects/types.rst:258 +msgid "HTTP Authentication" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Address" +#: ../system/objects/types.rst:255 +msgid "" +"If your external data source requires an authentication, you can set it " +"here. You can leave it empty or choose between *Basic Authentication* or " +"*Authentication Token* (selecting one of the two methods leads to additional " +"fields where you can enter your credentials/token)." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.address}``" +#: ../system/objects/types.rst:265 +msgid "Search result list key" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated at" +#: ../system/objects/types.rst:261 +msgid "" +"Defines the level in the JSON structure which provides the list with search " +"results. You can leave it empty, if the data is already provided as an " +"array. If you have to go deeper in the structure, you can provide a path " +"with ``.`` as separators, e.g. ``key.subkey.sub-sub-key``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_at}``" +#: ../system/objects/types.rst:271 +msgid "Search result value key" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Title" +#: ../system/objects/types.rst:268 +msgid "" +"Defines the attribute in the structure in which your external data source " +"provides the *value* for your data. An example would be a product *number*. " +"If you have to go deeper in the structure, you can provide a path with ``.`` " +"as separators, e.g. ``key.subkey.sub-sub-key``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.title}``" +#: ../system/objects/types.rst:277 +msgid "Search result label key" msgstr "" -#: ../system/variables/ticket.rst:1 +#: ../system/objects/types.rst:274 msgid "" -"``My amazing Subject`` (normally subject, can be edited within Interface and " -"thus differ)" +"Defines the attribute in the structure in which your external data source " +"provides the *label* for your data. An example would be a product *name*. If " +"you have to go deeper in the structure, you can provide a path with ``.`` as " +"separators, e.g. ``key.subkey.sub-sub-key``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Accounted Time" +#: ../system/objects/types.rst:280 +msgid "" +"In the preview area, you can find the following items (depending on your " +"configuration above):" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.time_unit}``" +#: ../system/objects/types.rst:283 +msgid "" +"**Error/hint message** (only if configuration is not complete): Zammad tells " +"you, if there is a problem and what you should change in your configuration." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``1``, ``2.75`` or empty response" +#: ../system/objects/types.rst:286 +msgid "" +"**Search field**: search for an existing attribute in the data source to get " +"a preview. This is required for the fields below to show up." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Tags" +#: ../system/objects/types.rst:288 +msgid "" +"**Search result response** (only if configuration is not complete): here you " +"can find a syntax highlighted JSON preview of the response, based on the " +"search term you entered." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.tags}``" +#: ../system/objects/types.rst:291 +msgid "" +"**Search result list** (only if *search result list key* is properly set): " +"output of the structure under the configured *search result list key*." msgstr "" -#: ../system/variables/ticket.rst:1 +#: ../system/objects/types.rst:294 msgid "" -"Currently not available, see `Issue 2769 `_" +"**Preview table** (when fully configured): Zammad shows you a table which " +"includes the found items based on the search string (value, label and " +"optional link). You can use this preview if you don't have the complete data " +"structure of the external system in mind." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > State > Name" +#: ../system/objects/types.rst:299 +msgid "" +"An example of a configured external data source field from agent perspective:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.state.name}``" +#: ../system/objects/types.rst:0 +msgid "Screencast showing the search for a product in a ticket" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``new``, ``open``, ..." +#: ../system/objects/types.rst:307 +msgid "URL fields (Link-Template)" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Priority > Name" +#: ../system/objects/types.rst:311 +msgid "" +"This function is restricted to Text, Select and External data source types " +"only." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.priority.name}``" +#: ../system/objects/types.rst:314 +msgid "" +"Link-Templates are an amazing way to dynamically generate URLs. They allow " +"you to integrate other systems better without having to manually copy data " +"from Zammad if possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2 normal``" +#: ../system/objects/types.rst:320 +msgid "" +"Another great way of communicating with another system may be Zammad's :doc:" +"`Webhooks `." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Pending till" +#: ../system/objects/types.rst:323 +msgid "" +"After filling a link-template enabled field, an URL icon will appear on its " +"right. Clicking on the icon opens a new tab." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.pending_time}``" +#: ../system/objects/types.rst:328 +msgid "" +"Even though Zammad displays the link template within object edit and create " +"screens, the function is optional. It's only active if you populate the " +"field." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not set" +#: ../system/objects/types.rst:333 +msgid "" +"What's the difference between URL and text fields with link template...?!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Web" +#: ../system/objects/types.rst:335 +msgid "" +"Both fields have different use cases. Use ``text`` type text fields when " +"ever you have a *static* url that requires dynamic parameters. If you " +"require a drag & drop like field that you can put in any URL, use ``URL`` " +"type text fields." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.web}``" +#: ../system/objects/types.rst:340 +msgid "" +"The difference is easier to spot when comparing the fields directly, below " +"screencast shows the result - the dynamic approach uses existing values in " +"the moment of updating to built the URL - e.g. ``https://google.com/search?" +"q=cookies`` - while the URL approach uses the actual URL of the field - e.g. " +"``https://zammad.com``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``https://zammad.com`` or empty if not set" +#: ../system/objects/types.rst:None +msgid "" +"Screencast showing the differents in between URL and text type fields with " +"actual values" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > VIP" +#: ../system/objects/types.rst:352 +msgid "How does this work...?!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.vip}``" +#: ../system/objects/types.rst:354 +msgid "" +"As an example, let's say you have an attribute called ``amazing_attribute`` " +"and you want to open a google search directly with the input from that field." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Phone" +#: ../system/objects/types.rst:357 +msgid "" +"Providing the link-template field below allows you to do so: ``https://www." +"google.com/search?q=#{ticket.amazing_attribute}``" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.phone}``" +#: ../system/objects/types.rst:362 +msgid "" +"You can use any :doc:`Zammad variable ` as long as it's " +"available in the moment you need it." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Note" +#: ../system/objects/types.rst:365 +msgid "" +"As a result, you are redirected to Google with a search for the value of the " +"attribute, if you click on the button in the ticket (as you can see in the " +"screencast above)." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.note}``" -msgstr "" +#: ../system/packages.rst:2 +msgid "Packages" +msgstr "Paquets" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Mobile" +#: ../system/packages.rst:4 +msgid "That's the package management-area." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.mobile}``" +#: ../system/packages.rst:6 +msgid "Individual add-ons for Zammad can be installed and managed here." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Login" -msgstr "" +#: ../system/sessions.rst:2 +msgid "Sessions" +msgstr "Sessions" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.login}``" +#: ../system/sessions.rst:4 +msgid "" +"Sessions management allows reviewing currently known user sessions and " +"allows to end these. The session timeout is affected by :ref:" +"`security_session_timeout` configurations from security settings." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``agent``" +#: ../system/sessions.rst:None +msgid "Screenshot showing Zammad's session management" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Lastname" +#: ../system/sessions.rst:13 +msgid "Zammad will provide the following information:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.lastname}``" +#: ../system/sessions.rst:16 +msgid "" +"The user account this session entry belongs to. It can be normal if a user " +"has several sessions in the list. This can be due to changed browser " +"information or if you use e.g. single sign on methods where the user does " +"not use the log off button." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Mustermann`` or empty if not set" +#: ../system/sessions.rst:22 +msgid "Browser" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Firstname" +#: ../system/sessions.rst:22 +msgid "The browser agent communicated to Zammad." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.firstname}``" -msgstr "" +#: ../system/sessions.rst:40 +#, fuzzy +msgid "Location" +msgstr "Intégrations" -#: ../system/variables/ticket.rst:1 -msgid "``Max`` or empty if not set" +#: ../system/sessions.rst:25 +msgid "" +"The anticipated location based on the users IP address. Depending on the IP " +"address the result shown may differ. This option depends on :doc:`/settings/" +"system/services`." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Fax" +#: ../system/sessions.rst:29 +msgid "The following information can be shown:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.fax}``" +#: ../system/sessions.rst:33 +msgid "IP address" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Email" +#: ../system/sessions.rst:32 +msgid "" +"Either if you set *Geo IP services* to inactive or you're using internal IP " +"address which do not provide location information." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.email}``" +#: ../system/sessions.rst:40 +msgid "Country (or Country + City)" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``agent@company.tld`` or empty if not set" +#: ../system/sessions.rst:36 +msgid "" +"If *Geo IP services* is enabled only. Depends on how detailed the available " +"IP address information are." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Department" +#: ../system/sessions.rst:39 +msgid "" +"Be aware that results can be inaccurate - this technically is not an error." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.department}``" +#: ../system/sessions.rst:43 +msgid "Age" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Support`` or empty if not set" +#: ../system/sessions.rst:43 +msgid "Provides the time when the session initially has been created." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Avatar" +#: ../system/sessions.rst:50 +msgid "Update" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.avatar(60,60)}``" +#: ../system/sessions.rst:46 +msgid "" +"Provides the time the user used this session to open Zammad. This timestamp " +"is only updated if the user e.g. reloads, not during normal work on tickets." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Address" +#: ../system/sessions.rst:50 +msgid "This timestamp is being used for the session timeout." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.address}``" +#: ../system/sessions.rst:53 +msgid "" +"Use the delete button to remove a single session on behalf of your user." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Shared organization" +#: ../system/subscription.rst:2 +msgid "Subscription (SaaS)" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.shared}``" +#: ../system/subscription.rst:4 +msgid "" +"The subscription settings page allows you to configure your instances " +"package and number of agents required." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Note" +#: ../system/subscription.rst:9 +msgid "" +"This setting section is only available for Hosted setups. If you're looking " +"for on premise support contracts, please see the `Zammad pricing page " +"`_." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.note}``" +#: ../system/subscription.rst:14 ../system/subscription.rst:34 +msgid "Plan" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Name" +#: ../system/subscription.rst:16 +msgid "" +"Here you can set up everything affecting your instance subscription " +"functions like number of agents and package." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.name}``" +#: ../system/subscription.rst:19 +msgid "" +"On top of the page you can find a subscription summary. You'll find the " +"number of used and available (booked) agent seats there. By using the *see " +"more* link you can also expand an agent list to see the currently configured " +"active agents. This list *does not* count accounts with admin permissions " +"only." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Zammad GmbH`` or empty if not set" +#: ../system/subscription.rst:None +msgid "" +"Within subscription you can always see how many agents are still\n" +"available to add and who uses the seats." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Domain based assignment" +#: ../system/subscription.rst:29 +msgid "" +"Learn more on how to manage your agents in general :doc:`here `." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.domain_assignment}``" +#: ../system/subscription.rst:36 +msgid "" +"This section gives you an overview of the available plans and their " +"functions / limits. If you require a more detailed table, check our " +"`detailed pricing table `_ for more." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Domain" +#: ../system/subscription.rst:40 +msgid "" +"Your selection in this step will decide on the base agent price and e.g. " +"agent limits that might apply in the summary step." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.domain}``" +#: ../system/subscription.rst:43 +msgid "" +"The green *Selected* button will also tell you what plan you're currently in." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``domain.tld`` or empty if not set" +#: ../system/subscription.rst:47 +msgid "" +"Trial instances are running at Professional with 3 agents. The plan cannot " +"be changed during the trial for technical reasons, if you require more " +"agents for testing, please contact `our sales team `_ with a reason for the raise request." msgstr "" -#: ../system/variables/ticket.rst:1 -#, fuzzy -msgid "Ticket > Organization > VIP" -msgstr "Sociétés" - -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.vip}``" +#: ../system/subscription.rst:None +msgid "" +"Screenshot showing three available packages for a hosted Zammad\n" +"instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Number" +#: ../system/subscription.rst:57 +msgid "" +"At the bottom of this block you can find a summary where you can adjust the " +"settings of the previous selected plan." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.number}``" +#: ../system/subscription.rst:62 +msgid "" +"Note that upgrading (more agents, higher package) is always possible, " +"however, downgrading will only happen when your billing period renews." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``31001``, ``201910731001``, ..." +#: ../system/subscription.rst:66 +msgid "" +"Upgrading resets your billing period and existing credit will be deducted " +"from the new total." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > ID" +#: ../system/subscription.rst:75 +msgid "Billing cycle" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.id}``" +#: ../system/subscription.rst:70 +msgid "" +"You can choose between either monthly or yearly billing. The price per agent " +"will be cheaper if you decide for yearly billing." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``17``, ``5281``, ..." +#: ../system/subscription.rst:73 +msgid "" +"If you're still trying out things and are unsure of the right package for " +"your instance, you may want to choose monthly first and then upgrade to " +"yearly when you're sure." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact (customer)" +#: ../system/subscription.rst:83 +msgid "Plan: (Starter|Professional|Plus) - Agents" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_customer_at}``" +#: ../system/subscription.rst:78 +msgid "Choose the number of agents you require for your instance." msgstr "" -#: ../system/variables/ticket.rst:1 +#: ../system/subscription.rst:80 msgid "" -"``2019-10-07 16:25:00 UTC`` or empty if not applicable yet (Please note " -"`Ticket last contact behavior Settings `_ for this)" -msgstr "" - -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact" +"Keep in mind that some packages may have agent limits. Depending on the " +"previous chosen package, you won't be able to exceed specific agent numbers. " +"Also note that setting less agents than currently configured is not possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_at}``" +#: ../system/subscription.rst:86 +msgid "Total" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact (agent)" +#: ../system/subscription.rst:86 +msgid "This will be the net total you're going to be billed." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_agent_at}``" +#: ../system/subscription.rst:88 +msgid "" +"By using the *Update subscription* button, the instance package will be " +"adjusted immediately. If you didn't provide a payment method yet, Zammad " +"will request you to provide one at this point." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable yet" +#: ../system/subscription.rst:94 +msgid "" +"In case you're still within the trial period, this means that the trial will " +"be over immediately!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Note" +#: ../system/subscription.rst:97 +msgid "Down- or upgrading during the trial period *is not* possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.note}``" +#: ../system/subscription.rst:None +msgid "Screenshot showing payment options and a pricing summary" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Note about this group``" +#: ../system/subscription.rst:103 +msgid "Billing Information" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Name" +#: ../system/subscription.rst:105 +msgid "" +"You can control all billing relevant information like invoices, billing " +"address and the option to cancel your subscription." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.name}``" +#: ../system/subscription.rst:108 +msgid "" +"All adjusted billing information below only affect future invoices. If your " +"invoice was issued wrong, please contact `our sales team `_." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Sales``" +#: ../system/subscription.rst:114 +msgid "Billing address" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Follow-up possible" +#: ../system/subscription.rst:113 +msgid "" +"Provide your company address here, make sure to include the companies name " +"in case required. This address will be referenced on your invoice." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.follow_up_possible}``" +#: ../system/subscription.rst:118 +msgid "VAT ID" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``no`` or ``yes``" +#: ../system/subscription.rst:117 +msgid "" +"Provide your VAT ID here. If applicable your invoice will not contain German " +"VAT. Please make sure to pay the VAT in your country as required." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Assign Follow-Ups" +#: ../system/subscription.rst:127 +msgid "Billing Email Address" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.follow_up_assignment}``" +#: ../system/subscription.rst:121 +msgid "" +"Usually the instance owner (the person that registered the instance) will " +"receive all emails including the invoices. In case you have your own billing " +"department, you can provide their email address here." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Assignment Timeout" +#: ../system/subscription.rst:125 +msgid "" +"All billing relevant information will then be sent to this email address." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.assignment_timeout}``" +#: ../system/subscription.rst:127 +msgid "Invoices are sent as attachment (PDF) to this email address." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``20`` or empty if not configured" +#: ../system/subscription.rst:129 +msgid "" +"Don't forget to press the *Update billing information* button after you " +"changed above settings." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > First response" +#: ../system/subscription.rst:None +msgid "" +"Screenshot showing options for billing information within the\n" +"subscription menu" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.first_response_at}``" +#: ../system/subscription.rst:137 +msgid "Payment Method" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Escalation at" +#: ../system/subscription.rst:139 +msgid "You can pay via credit card or SEPA mandate." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.escalation_at}``" +#: ../system/subscription.rst:144 +msgid "Credit card" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable" +#: ../system/subscription.rst:142 +msgid "" +"Simply follow the dialogue by clicking *authorize credit card* and confirm -" +"if required by your bank- your consent to Zammad using your card for the " +"payments." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Web" +#: ../system/subscription.rst:148 +msgid "SEPA Direct Debit" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.web}``" +#: ../system/subscription.rst:147 +msgid "" +"Provide the requested information of the bank account holder and update if " +"you're ready. You'll then receive an email with the SEPA mandate." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > VIP" +#: ../system/subscription.rst:150 +msgid "" +"Technically there's also the possibility to pay via invoice, however - this " +"method only applies to a fairly low number of instances. Please contact `our " +"sales team `_ for more information." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.vip}``" +#: ../system/subscription.rst:156 +msgid "Cancel Subscription" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Phone" +#: ../system/subscription.rst:158 +msgid "" +"Do you want to cancel your subscription? In case you no longer want to use " +"Zammad's SaaS, you can cancel your subscription by using the red *Yes, " +"please cancel my subscription* button." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.phone}``" +#: ../system/subscription.rst:162 +msgid "" +"To cancel the description, enter the FQDN of your Zammad instance and " +"provide a reason for your cancellation." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Note" +#: ../system/subscription.rst:165 +msgid "" +"Your subscription will end the day after your trial or billing period ends." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.note}``" +#: ../system/subscription.rst:None +#, fuzzy +msgid "Screenshot showing subscription cancellation dialog" msgstr "" +"Capture d'écran montrant la configuration de base d'une boîte de réception" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Mobile" +#: ../system/subscription.rst:174 +msgid "" +"We will remind you about your cancelled subscription several times up front. " +"After the subscription ended all instance data will be removed. A restore " +"*is not* possible after that point!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.mobile}``" +#: ../system/subscription.rst:178 +msgid "**😖 Cancelled by accident?**" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Login" +#: ../system/subscription.rst:180 +msgid "" +"You can always undo the cancellation via the *Yes, undo the cancellation of " +"my subscription* button up to the last subscription day!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.login}``" +#: ../system/subscription.rst:0 +msgid "" +"Screenshot showing a red button to cancel the subscription\n" +"cancellation" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Lastname" +#: ../system/subscription.rst:189 +msgid "Payment History" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.lastname}``" +#: ../system/subscription.rst:191 +msgid "" +"The payment history will display a history of all paid invoices. At this " +"point you can also download these in case you need them again." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Firstname" +#: ../system/subscription.rst:196 +msgid "" +"You will only find *paid* invoices here. Invoices that are to be billed are " +"not available before the payment is completed." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.firstname}``" +#: ../system/subscription.rst:201 +msgid "Date" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Fax" +#: ../system/subscription.rst:201 +msgid "Date of the invoice creation." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.fax}``" -msgstr "" +#: ../system/subscription.rst:204 +#, fuzzy +msgid "Amount" +msgstr "Les comptes" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Email" +#: ../system/subscription.rst:204 +msgid "Invoice total including VAT if applicable." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.email}``" +#: ../system/subscription.rst:207 +msgid "" +"Contains contract period (monthly or yearly) and hosted plan for the " +"subscription period in question." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Department" +#: ../system/subscription.rst:218 +msgid "Payment method / Service period" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.department}``" +#: ../system/subscription.rst:211 +msgid "" +"Used bank account or credit card as well as the subscription period the " +"invoice is about." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Avatar" +#: ../system/subscription.rst:216 +msgid "" +"It might happen that the invoice date and subscription period differ. This " +"is nothing to worry about, the subscription periods will be accounted later " +"on." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.avatar(60,60)}``" +#: ../system/subscription.rst:222 +msgid "Receipt" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Address" +#: ../system/subscription.rst:221 +msgid "" +"Use the arrow to download the invoice in question. You can download all " +"available invoices any time you need to here!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.address}``" +#: ../system/subscription.rst:None +msgid "Screenshot showing payment history of a hosted instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Web" +#: ../system/subscription.rst:229 +msgid "FAQ" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.web}``" +#: ../system/subscription.rst:233 +msgid "I set up a trial account but am missing functions to test" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > VIP" +#: ../system/subscription.rst:232 +msgid "" +"The trial instance is running within the professional package allowing up to " +"three agents." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.vip}``" +#: ../system/subscription.rst:236 +msgid "Can I change package within the trial?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Phone" +#: ../system/subscription.rst:236 +msgid "No. As soon as the package is changed the subscription begins." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.phone}``" +#: ../system/subscription.rst:241 +msgid "What happens to my trial instance after the trial period ended?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Note" +#: ../system/subscription.rst:239 +msgid "" +"Your instance will automatically be canceled for you. Please see *What " +"happens to my instance after it has been canceled?* for more." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.note}``" +#: ../system/subscription.rst:254 +msgid "What happens to my instance after it has been canceled?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Mobile" +#: ../system/subscription.rst:244 +msgid "That depends slightly on your instance state:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.mobile}``" -msgstr "" +#: ../system/subscription.rst:250 +#, fuzzy +msgid "Trial instance" +msgstr "Maintenance" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Login" +#: ../system/subscription.rst:247 +msgid "" +"If you're still on trial, we will ice your instance and remind you once " +"again about your instance. We then will wait some days and remove your " +"instance from our system. This is the last time we will inform you by Email." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.login}``" -msgstr "" +#: ../system/subscription.rst:254 +#, fuzzy +msgid "Paid instance" +msgstr "Maintenance" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Lastname" +#: ../system/subscription.rst:253 +msgid "" +"If you're a paying customer and canceled your subscription, the instance " +"removal will take place the day after your last subscription day." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.lastname}``" +#: ../system/subscription.rst:256 +msgid "Can removed instances be restored?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Firstname" +#: ../system/subscription.rst:257 +msgid "No. Once your instance has been removed, a restoration is not possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.firstname}``" -msgstr "" +#: ../system/system-report.rst:2 +#, fuzzy +msgid "System Report" +msgstr "Variables Article" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Fax" +#: ../system/system-report.rst:4 +msgid "" +"In this place you can't configure Zammad. Instead you can obtain a system " +"report about Zammad and its configuration." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.fax}``" +#: ../system/system-report.rst:7 +msgid "" +"See the description in Zammad for an explanation. You can even find a " +"preview of the included data below the **Download** button." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Email" +#: ../system/system-report.rst:10 +msgid "" +"Zammad never sends this automatically to anyone. It is a manual process only " +"to provide better support based on your configuration." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.email}``" -msgstr "" +#: ../system/translations.rst:2 +msgid "Translations" +msgstr "Traductions" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Department" +#: ../system/translations.rst:4 +msgid "" +"Translations of Zammad are processed centrally in our `Weblate instance " +"`_. This allows non-developers to review " +"and update translation texts of the language they actually speak." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.department}``" +#: ../system/translations.rst:9 +msgid "" +"Your language is in an incomplete translation state or has typos? Please " +"consider helping us in sorting this out! All you need is either a GitHub " +"account or to register directly in our instance." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Avatar" +#: ../system/translations.rst:13 +msgid "" +"Did you know? This is also where the documentation translations are handled. " +"🤓" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.avatar(60,60)}``" +#: ../system/translations.rst:15 +msgid "" +"Have a look in our :docs:`contribution section ` in the system documentation to get started!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Address" -msgstr "" +#: ../system/translations.rst:20 +#, fuzzy +msgid "Local Translations" +msgstr "Traductions" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.address}``" +#: ../system/translations.rst:22 +msgid "" +"Apart from these system translations, there's still local translations you " +"can manage. This is relevant if you added custom objects that require " +"translations or even custom states and priorities." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created at" +#: ../system/translations.rst:None +msgid "Translation management screen within the admin menu" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_at}``" -msgstr "" +#: ../system/translations.rst:31 +#, fuzzy +msgid "Updating Translations" +msgstr "Traductions" -#: ../system/variables/ticket.rst:1 -msgid "2019-10-07 16:25:00 UTC" +#: ../system/translations.rst:33 +msgid "" +"Because of how Zammad ships translations, the only way to update the system " +"translations is to update your Zammad installation. The benefit of this is " +"that you no longer need internet access during a Zammad upgrade as the " +"package has everything it requires already." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Closing time" +#: ../system/translations.rst:39 +msgid "Translation of Custom Objects" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.close_at}``" +#: ../system/translations.rst:41 +msgid "" +"No problem at all! You can customize any translation locally, even if it is " +"not initially provided by the system." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "2019-10-07 17:25:00 UTC" +#: ../system/translations.rst:44 +msgid "" +"Translation is supported for a broad number of features, including but not " +"limited to custom:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``3``, any number of articles existing in the ticket right now" -msgstr "" +#: ../system/translations.rst:47 +#, fuzzy +msgid "Object Attributes" +msgstr "Variables Article" -#: ../system/version.rst:2 -msgid "Version" -msgstr "Version" +#: ../system/translations.rst:48 +msgid "Ticket Macros" +msgstr "Automation sur les tickets" -#: ../system/version.rst:4 -msgid "Shows which version is currently being used on your Zammad-instance." -msgstr "" -"Voir quelle version est actuellement utilisée pour votre instance Zammad." +#: ../system/translations.rst:49 +#, fuzzy +msgid "Ticket Overviews" +msgstr "Aperçus" -#: ../manage/roles/admin-permissions.rst:53 -msgid "``admin.checklist``" -msgstr "" +#: ../system/translations.rst:50 +#, fuzzy +msgid "Ticket Priorities" +msgstr "priorité" -#: ../manage/roles/admin-permissions.rst:54 -msgid ":doc:`Manage > Checklist `" -msgstr "" +#: ../system/translations.rst:51 +#, fuzzy +msgid "Ticket States" +msgstr "exemple" -#: ../manage/roles/admin-permissions.rst:83 -msgid "``admin.channel_whatsapp``" -msgstr "" +#: ../system/translations.rst:54 +#, fuzzy +msgid "Customizing Translations" +msgstr "Traductions" -#: ../manage/roles/admin-permissions.rst:84 -msgid ":doc:`Channels > Whatsapp `" +#: ../system/translations.rst:56 +msgid "" +"Within the translation screen, simply click on the **New Translation** " +"button." msgstr "" -#: ../manage/roles/admin-permissions.rst:124 -msgid "``admin.public_links``" -msgstr "" +#: ../system/translations.rst:None +#, fuzzy +msgid "New translation dialog" +msgstr "Boîte de dialogue Nouveau compte de messagerie" -#: ../manage/roles/admin-permissions.rst:125 -msgid ":doc:`Manage > Public Links `" +#: ../system/translations.rst:62 +msgid "" +"In the dialog you can immediately enter the exact translation source (if you " +"know it) and your custom translation text for it and click **Submit**." msgstr "" -#: ../manage/roles/admin-permissions.rst:151 -msgid "``admin.system_report``" +#: ../system/translations.rst:65 +msgid "" +"Alternatively, try to search for translation suggestions in the list below. " +"Selecting an item from the list will pre-fill the translation source for you " +"and then you can just enter your custom translation." msgstr "" -#: ../manage/roles/admin-permissions.rst:152 -msgid ":doc:`System > System Report `" +#: ../system/translations.rst:69 +msgid "" +"The target language will always default to your current language selection. " +"If you need to translate for a different language, simply change the " +"selection before submitting." msgstr "" -#: ../manage/roles/admin-permissions.rst:166 -msgid "``admin.ticket_auto_assignment``" +#: ../system/translations.rst:73 +msgid "" +"All your custom translations will show up in the overview table when added. " +"And they will even persist across Zammad updates!" msgstr "" -#: ../manage/roles/admin-permissions.rst:167 -msgid ":ref:`Settings > Ticket > Auto Assignment `" +#: ../system/translations.rst:76 +msgid "" +"Make sure to reload your browser if a translated string is not displayed." msgstr "" -#: ../manage/roles/admin-permissions.rst:169 -msgid "``admin.ticket_duplicate_detection``" +#: ../system/translations.rst:80 +msgid "Reverting to Original Translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:170 -msgid ":ref:`Settings > Ticket > Duplicate Detection `" +#: ../system/translations.rst:82 +msgid "" +"If you want to revert a custom translation to original text, simply use the " +"appropriate action within the row of the overview table." msgstr "" -#: ../manage/roles/admin-permissions.rst:172 -#, fuzzy -msgid "``admin.ticket_priority``" -msgstr "priorité" - -#: ../manage/roles/admin-permissions.rst:173 -msgid ":ref:`System > Objects >Ticket Priority `" +#: ../system/translations.rst:85 +msgid "" +"Depending on the type of the translation source, the action has a slightly " +"different name:" msgstr "" -#: ../manage/roles/admin-permissions.rst:175 -#, fuzzy -msgid "``admin.ticket_state``" -msgstr "exemple" - -#: ../manage/roles/admin-permissions.rst:176 -msgid ":ref:`System > Objects >Ticket State `" +#: ../system/translations.rst:88 +msgid "**Reset** for customized system translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:193 -msgid "``admin.webhook``" +#: ../system/translations.rst:89 +msgid "**Remove** for customized local translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:194 -msgid ":doc:`Manage > Webhook `" +#: ../system/translations.rst:91 +msgid "" +"In both cases, the action will remove the customized translation after a " +"confirmation." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:43 -msgid "``user_preferences.appearance``" +#: ../system/translations.rst:None +msgid "Screenshot showing the location of the Remove action" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:44 +#: ../system/translations.rst:99 #, fuzzy -msgid "Appearance configuration" -msgstr "Boîte de dialogue de configuration avancée" +msgid "Inline Translations" +msgstr "Traductions" -#: ../manage/roles/user-preferences-permissions.rst:0 -msgid "Users can switch between dark, light and" +#: ../system/translations.rst:101 +msgid "" +"If you prefer a more hands-on approach, you can activate the inline or on-" +"screen translation feature by pressing ``ctrl`` + ``alt`` + ``t`` at any " +"time and on any screen." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:0 -msgid "automatic mode." +#: ../system/translations.rst:105 +msgid "" +"All customizable translation texts will be highlighted for you on the " +"screen. Just click into the highlighted area and update the text in place." msgstr "" -#: ../system/system-report.rst:2 -#, fuzzy -msgid "System Report" -msgstr "Variables Article" +#: ../system/translations.rst:None +msgid "Inline translation mode activated for the Overview screen" +msgstr "" -#: ../system/system-report.rst:4 +#: ../system/translations.rst:112 msgid "" -"In this place you can't configure Zammad. Instead you can obtain a system " -"report about Zammad and its configuration." +"When finished editing, simply press ``ctrl`` + ``alt`` + ``t`` again to " +"deactivate." msgstr "" -#: ../system/system-report.rst:7 +#: ../system/translations.rst:117 msgid "" -"See the description in Zammad for an explanation. You can even find a " -"preview of the included data below the **Download** button." +"Even though it's available on any screen, the inline translation feature " +"requires admin permissions. It works only for the current language " +"selection. If you need to translate a different language, first change the " +"language in your :user-docs:`profile settings `." msgstr "" -#: ../system/system-report.rst:10 -msgid "" -"Zammad never sends this automatically to anyone. It is a manual process only " -"to provide better support based on your configuration." +#: ../system/version.rst:2 +msgid "Version" +msgstr "Version" + +#: ../system/version.rst:4 +msgid "Shows which version is currently being used on your Zammad-instance." msgstr "" +"Voir quelle version est actuellement utilisée pour votre instance Zammad." #, fuzzy #~ msgid "" diff --git a/locale/fr_CA/LC_MESSAGES/admin-docs.po b/locale/fr_CA/LC_MESSAGES/admin-docs.po index 9cfdbe16..610995f0 100644 --- a/locale/fr_CA/LC_MESSAGES/admin-docs.po +++ b/locale/fr_CA/LC_MESSAGES/admin-docs.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Zammad\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-11-06 10:31+0100\n" +"POT-Creation-Date: 2024-11-12 16:31+0100\n" "PO-Revision-Date: 2021-12-03 14:33+0000\n" "Last-Translator: TRANSFER FROM TRANSIFEX \n" "Language-Team: French (Canada) Checklist `" +msgstr "Billet > Prganisation > Organisation partagée" + #: ../manage/roles/admin-permissions.rst:56 msgid "``admin.channel_email``" msgstr "" -#: ../manage/roles/admin-permissions.rst:54 #: ../manage/roles/admin-permissions.rst:57 msgid ":doc:`Channels > Email `" msgstr "" -#: ../manage/roles/admin-permissions.rst:56 #: ../manage/roles/admin-permissions.rst:59 msgid "``admin.channel_facebook``" msgstr "" -#: ../manage/roles/admin-permissions.rst:57 #: ../manage/roles/admin-permissions.rst:60 msgid ":doc:`Channels > Facebook `" msgstr "" -#: ../manage/roles/admin-permissions.rst:58 #: ../manage/roles/admin-permissions.rst:61 msgid "" "Accessing Facebook tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:59 #: ../manage/roles/admin-permissions.rst:62 msgid "``admin.channel_formular``" msgstr "" -#: ../manage/roles/admin-permissions.rst:60 #: ../manage/roles/admin-permissions.rst:63 msgid ":doc:`Channels > Form `" msgstr "" -#: ../manage/roles/admin-permissions.rst:62 #: ../manage/roles/admin-permissions.rst:65 msgid "``admin.channel_google``" msgstr "" -#: ../manage/roles/admin-permissions.rst:63 #: ../manage/roles/admin-permissions.rst:66 msgid ":doc:`Channels > Google `" msgstr "" -#: ../manage/roles/admin-permissions.rst:65 #: ../manage/roles/admin-permissions.rst:68 msgid "``admin.channel_microsoft365``" msgstr "" -#: ../manage/roles/admin-permissions.rst:66 #: ../manage/roles/admin-permissions.rst:69 msgid ":doc:`Channels > Microsoft 365 `" msgstr "" -#: ../manage/roles/admin-permissions.rst:68 #: ../manage/roles/admin-permissions.rst:71 msgid "``admin.channel_sms``" msgstr "" -#: ../manage/roles/admin-permissions.rst:69 #: ../manage/roles/admin-permissions.rst:72 msgid ":doc:`Channels > SMS `" msgstr "" -#: ../manage/roles/admin-permissions.rst:71 #: ../manage/roles/admin-permissions.rst:74 msgid "``admin.channel_telegram``" msgstr "" -#: ../manage/roles/admin-permissions.rst:72 #: ../manage/roles/admin-permissions.rst:75 msgid ":doc:`Channels > Telegram `" msgstr "" -#: ../manage/roles/admin-permissions.rst:73 #: ../manage/roles/admin-permissions.rst:76 msgid "" "Accessing Telegram tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:74 #: ../manage/roles/admin-permissions.rst:77 msgid "``admin.channel_twitter``" msgstr "" -#: ../manage/roles/admin-permissions.rst:75 #: ../manage/roles/admin-permissions.rst:78 msgid ":doc:`Channels > Twitter `" msgstr "" -#: ../manage/roles/admin-permissions.rst:76 #: ../manage/roles/admin-permissions.rst:79 msgid "" "Accessing Twitter/X tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:77 #: ../manage/roles/admin-permissions.rst:80 msgid "``admin.channel_web``" msgstr "" -#: ../manage/roles/admin-permissions.rst:78 #: ../manage/roles/admin-permissions.rst:81 msgid ":doc:`Channels > Web `" msgstr "" -#: ../manage/roles/admin-permissions.rst:80 +#: ../manage/roles/admin-permissions.rst:83 +msgid "``admin.channel_whatsapp``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:84 +#, fuzzy +msgid ":doc:`Channels > Whatsapp `" +msgstr "Billet > Prganisation > Organisation partagée" + #: ../manage/roles/admin-permissions.rst:86 msgid "``admin.core_workflows``" msgstr "" -#: ../manage/roles/admin-permissions.rst:81 #: ../manage/roles/admin-permissions.rst:87 msgid ":doc:`System > Core Workflows `" msgstr "" -#: ../manage/roles/admin-permissions.rst:83 #: ../manage/roles/admin-permissions.rst:89 msgid "``admin.data_privacy``" msgstr "" -#: ../manage/roles/admin-permissions.rst:84 #: ../manage/roles/admin-permissions.rst:90 msgid ":doc:`System > Data Privacy `" msgstr "" -#: ../manage/roles/admin-permissions.rst:85 #: ../manage/roles/admin-permissions.rst:91 msgid "" "🔥 Be careful, it allows users to permanently delete data on the system." msgstr "" -#: ../manage/roles/admin-permissions.rst:86 #: ../manage/roles/admin-permissions.rst:92 msgid "``admin.group``" msgstr "" -#: ../manage/roles/admin-permissions.rst:87 #: ../manage/roles/admin-permissions.rst:93 msgid ":doc:`Manage > Groups `" msgstr "" -#: ../manage/roles/admin-permissions.rst:89 #: ../manage/roles/admin-permissions.rst:95 msgid "``admin.integration``" msgstr "" -#: ../manage/roles/admin-permissions.rst:90 #: ../manage/roles/admin-permissions.rst:96 msgid ":doc:`System > Integrations `" msgstr "" -#: ../manage/roles/admin-permissions.rst:92 #: ../manage/roles/admin-permissions.rst:98 msgid "``admin.knowledge_base``" msgstr "" -#: ../manage/roles/admin-permissions.rst:93 #: ../manage/roles/admin-permissions.rst:99 msgid ":doc:`Manage > Knowledge Base `" msgstr "" @@ -8718,57 +8703,46 @@ msgid "" "knowledge-base.html#editing-answers>`." msgstr "" -#: ../manage/roles/admin-permissions.rst:98 #: ../manage/roles/admin-permissions.rst:104 msgid "``admin.macro``" msgstr "" -#: ../manage/roles/admin-permissions.rst:99 #: ../manage/roles/admin-permissions.rst:105 msgid ":doc:`Manage > Macros `" msgstr "" -#: ../manage/roles/admin-permissions.rst:100 #: ../manage/roles/admin-permissions.rst:106 msgid "In some cases, macros may also require ``admin.tag``" msgstr "" -#: ../manage/roles/admin-permissions.rst:101 #: ../manage/roles/admin-permissions.rst:107 msgid "``admin.maintenance``" msgstr "" -#: ../manage/roles/admin-permissions.rst:102 #: ../manage/roles/admin-permissions.rst:108 msgid ":doc:`System > Maintenance `" msgstr "" -#: ../manage/roles/admin-permissions.rst:104 #: ../manage/roles/admin-permissions.rst:110 msgid "``admin.monitoring``" msgstr "" -#: ../manage/roles/admin-permissions.rst:105 #: ../manage/roles/admin-permissions.rst:111 msgid ":doc:`System > Monitoring `" msgstr "" -#: ../manage/roles/admin-permissions.rst:107 #: ../manage/roles/admin-permissions.rst:113 msgid "``admin.object``" msgstr "" -#: ../manage/roles/admin-permissions.rst:108 #: ../manage/roles/admin-permissions.rst:114 msgid ":doc:`System > Objects `" msgstr "" -#: ../manage/roles/admin-permissions.rst:110 #: ../manage/roles/admin-permissions.rst:116 msgid "``admin.organization``" msgstr "" -#: ../manage/roles/admin-permissions.rst:111 #: ../manage/roles/admin-permissions.rst:117 #, fuzzy msgid ":doc:`Manage > Organizations `" @@ -8786,206 +8760,219 @@ msgstr "" msgid "They can even edit an organization's name, domain, and notes!" msgstr "" -#: ../manage/roles/admin-permissions.rst:115 #: ../manage/roles/admin-permissions.rst:121 msgid "``admin.overview``" msgstr "" -#: ../manage/roles/admin-permissions.rst:116 #: ../manage/roles/admin-permissions.rst:122 msgid ":doc:`Manage > Overviews`" msgstr "" -#: ../manage/roles/admin-permissions.rst:118 +#: ../manage/roles/admin-permissions.rst:124 +msgid "``admin.public_links``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:125 +#, fuzzy +msgid ":doc:`Manage > Public Links `" +msgstr "Billet > Prganisation > Organisation partagée" + #: ../manage/roles/admin-permissions.rst:127 msgid "``admin.package``" msgstr "" -#: ../manage/roles/admin-permissions.rst:119 #: ../manage/roles/admin-permissions.rst:128 msgid ":doc:`System > Packages `" msgstr "" -#: ../manage/roles/admin-permissions.rst:121 #: ../manage/roles/admin-permissions.rst:130 msgid "``admin.report_profile``" msgstr "" -#: ../manage/roles/admin-permissions.rst:122 #: ../manage/roles/admin-permissions.rst:131 msgid ":doc:`Manage > Report Profiles `" msgstr "" -#: ../manage/roles/admin-permissions.rst:123 #: ../manage/roles/admin-permissions.rst:132 msgid "Access to view reports: ``report``" msgstr "" -#: ../manage/roles/admin-permissions.rst:124 #: ../manage/roles/admin-permissions.rst:133 msgid "``admin.role``" msgstr "" -#: ../manage/roles/admin-permissions.rst:125 #: ../manage/roles/admin-permissions.rst:134 #, fuzzy msgid ":doc:`Manage > Roles `" msgstr "Billet > Prganisation > Organisation partagée" -#: ../manage/roles/admin-permissions.rst:127 #: ../manage/roles/admin-permissions.rst:136 msgid "``admin.scheduler``" msgstr "" -#: ../manage/roles/admin-permissions.rst:128 #: ../manage/roles/admin-permissions.rst:137 #, fuzzy msgid ":doc:`Manage > Scheduler `" msgstr "Billet > Prganisation > Organisation partagée" -#: ../manage/roles/admin-permissions.rst:129 #: ../manage/roles/admin-permissions.rst:138 msgid "For automation on tickets" msgstr "" -#: ../manage/roles/admin-permissions.rst:130 #: ../manage/roles/admin-permissions.rst:139 msgid "``admin.security``" msgstr "" -#: ../manage/roles/admin-permissions.rst:131 #: ../manage/roles/admin-permissions.rst:140 msgid ":doc:`Settings > Security `" msgstr "" -#: ../manage/roles/admin-permissions.rst:132 #: ../manage/roles/admin-permissions.rst:141 msgid "Settings of Zammad. This also covers third party authentications." msgstr "" -#: ../manage/roles/admin-permissions.rst:133 #: ../manage/roles/admin-permissions.rst:142 msgid "``admin.session``" msgstr "" -#: ../manage/roles/admin-permissions.rst:134 #: ../manage/roles/admin-permissions.rst:143 msgid ":doc:`System > Sessions `" msgstr "" -#: ../manage/roles/admin-permissions.rst:136 #: ../manage/roles/admin-permissions.rst:145 msgid "``admin.setting_system``" msgstr "" -#: ../manage/roles/admin-permissions.rst:137 #: ../manage/roles/admin-permissions.rst:146 msgid ":doc:`Settings > System `" msgstr "" -#: ../manage/roles/admin-permissions.rst:139 #: ../manage/roles/admin-permissions.rst:148 msgid "``admin.sla``" msgstr "" -#: ../manage/roles/admin-permissions.rst:140 #: ../manage/roles/admin-permissions.rst:149 msgid ":doc:`Manage > SLAs `" msgstr "" -#: ../manage/roles/admin-permissions.rst:142 +#: ../manage/roles/admin-permissions.rst:151 +msgid "``admin.system_report``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:152 +#, fuzzy +msgid ":doc:`System > System Report `" +msgstr "Billet > Prganisation > Organisation partagée" + #: ../manage/roles/admin-permissions.rst:154 msgid "``admin.tag``" msgstr "" -#: ../manage/roles/admin-permissions.rst:143 #: ../manage/roles/admin-permissions.rst:155 msgid ":doc:`Manage > Tags `" msgstr "" -#: ../manage/roles/admin-permissions.rst:145 #: ../manage/roles/admin-permissions.rst:157 msgid "``admin.template``" msgstr "" -#: ../manage/roles/admin-permissions.rst:146 #: ../manage/roles/admin-permissions.rst:158 #, fuzzy msgid ":doc:`Manage > Templates `" msgstr "Billet > Prganisation > Organisation partagée" -#: ../manage/roles/admin-permissions.rst:148 #: ../manage/roles/admin-permissions.rst:160 msgid "``admin.text_module``" msgstr "" -#: ../manage/roles/admin-permissions.rst:149 #: ../manage/roles/admin-permissions.rst:161 msgid ":doc:`Manage > Text Modules `" msgstr "" -#: ../manage/roles/admin-permissions.rst:151 #: ../manage/roles/admin-permissions.rst:163 msgid "``admin.ticket``" msgstr "" -#: ../manage/roles/admin-permissions.rst:152 #: ../manage/roles/admin-permissions.rst:164 msgid ":doc:`Settings > Tickets `" msgstr "" -#: ../manage/roles/admin-permissions.rst:153 #: ../manage/roles/admin-permissions.rst:165 msgid "Does not grant access to :doc:`/misc/composer`" msgstr "" -#: ../manage/roles/admin-permissions.rst:154 +#: ../manage/roles/admin-permissions.rst:166 +#, fuzzy +msgid "``admin.ticket_auto_assignment``" +msgstr "``#{ticket.group.follow_up_assignment}``" + +#: ../manage/roles/admin-permissions.rst:167 +msgid ":ref:`Settings > Ticket > Auto Assignment `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:169 +msgid "``admin.ticket_duplicate_detection``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:170 +msgid ":ref:`Settings > Ticket > Duplicate Detection `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:172 +#, fuzzy +msgid "``admin.ticket_priority``" +msgstr "``#{ticket.priority.name}``" + +#: ../manage/roles/admin-permissions.rst:173 +msgid ":ref:`System > Objects >Ticket Priority `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:175 +#, fuzzy +msgid "``admin.ticket_state``" +msgstr "``#{ticket.state.name}``" + +#: ../manage/roles/admin-permissions.rst:176 +msgid ":ref:`System > Objects >Ticket State `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:178 msgid "``admin.time_accounting``" msgstr "" -#: ../manage/roles/admin-permissions.rst:155 #: ../manage/roles/admin-permissions.rst:179 msgid ":doc:`Manage > Time Accounting `" msgstr "" -#: ../manage/roles/admin-permissions.rst:156 #: ../manage/roles/admin-permissions.rst:180 msgid "Also allows the export of timekeeping records." msgstr "" -#: ../manage/roles/admin-permissions.rst:157 #: ../manage/roles/admin-permissions.rst:181 msgid "``admin.translation``" msgstr "" -#: ../manage/roles/admin-permissions.rst:158 #: ../manage/roles/admin-permissions.rst:182 #, fuzzy msgid ":doc:`System > Translations `" msgstr "Billet > Prganisation > Organisation partagée" -#: ../manage/roles/admin-permissions.rst:159 #: ../manage/roles/admin-permissions.rst:183 msgid "Also enables inline translation" msgstr "" -#: ../manage/roles/admin-permissions.rst:160 #: ../manage/roles/admin-permissions.rst:184 msgid "``admin.trigger``" msgstr "" -#: ../manage/roles/admin-permissions.rst:161 #: ../manage/roles/admin-permissions.rst:185 msgid ":doc:`Manage > Triggers `" msgstr "" -#: ../manage/roles/admin-permissions.rst:163 #: ../manage/roles/admin-permissions.rst:187 msgid "``admin.user``" msgstr "" -#: ../manage/roles/admin-permissions.rst:164 #: ../manage/roles/admin-permissions.rst:188 msgid ":doc:`Manage > Users `" msgstr "" @@ -9004,6 +8991,15 @@ msgid "" "from-users-perspective>` ." msgstr "" +#: ../manage/roles/admin-permissions.rst:193 +msgid "``admin.webhook``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:194 +#, fuzzy +msgid ":doc:`Manage > Webhook `" +msgstr "Billet > Prganisation > Organisation partagée" + #: ../manage/roles/agent-permissions.rst:2 msgid "Agent Permissions" msgstr "" @@ -9425,37 +9421,47 @@ msgid "than the user that generated them." msgstr "" #: ../manage/roles/user-preferences-permissions.rst:43 +msgid "``user_preferences.appearance``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:44 +#, fuzzy +msgid "Appearance configuration" +msgstr "Bloquer les notifications" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "Users can switch between dark, light and" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "automatic mode." +msgstr "" + #: ../manage/roles/user-preferences-permissions.rst:47 msgid "``user_preferences.avatar``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:44 #: ../manage/roles/user-preferences-permissions.rst:48 #, fuzzy msgid "Avatar settings" msgstr "Réglages avancés" -#: ../manage/roles/user-preferences-permissions.rst:45 #: ../manage/roles/user-preferences-permissions.rst:49 msgid "Override the default Gravatar with a custom avatar" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:46 #: ../manage/roles/user-preferences-permissions.rst:50 msgid "``user_preferences.calendar``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:47 #: ../manage/roles/user-preferences-permissions.rst:51 msgid "Configure the calendar feed" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:49 #: ../manage/roles/user-preferences-permissions.rst:53 msgid "``user_preferences.device``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:50 #: ../manage/roles/user-preferences-permissions.rst:54 msgid "Manage device login sessions" msgstr "" @@ -9472,22 +9478,18 @@ msgstr "" msgid "To learn more, see :doc:`/manage/trigger/system-notifications`." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:54 #: ../manage/roles/user-preferences-permissions.rst:58 msgid "``user_preferences.language``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:55 #: ../manage/roles/user-preferences-permissions.rst:59 msgid "Configure the UI locale/language" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:57 #: ../manage/roles/user-preferences-permissions.rst:61 msgid "``user_preferences.linked_accounts``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:58 #: ../manage/roles/user-preferences-permissions.rst:62 #, fuzzy msgid "Account linking" @@ -9512,7 +9514,6 @@ msgstr "" msgid "is the only way users can utilize third-party logins." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:63 #: ../manage/roles/user-preferences-permissions.rst:67 msgid "``user_preferences.notifications``" msgstr "" @@ -9541,7 +9542,6 @@ msgstr "" msgid "Customers can't receive ticket notifications at all." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:69 #: ../manage/roles/user-preferences-permissions.rst:73 msgid "``user_preferences.out_of_office``" msgstr "" @@ -9566,7 +9566,6 @@ msgstr "" msgid "they're replacing." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:75 #: ../manage/roles/user-preferences-permissions.rst:79 msgid "``user_preferences.overview_sorting``" msgstr "" @@ -9595,12 +9594,10 @@ msgstr "" msgid "overviews has no effect on custom orders." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:82 #: ../manage/roles/user-preferences-permissions.rst:86 msgid "``user_preferences.password``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:83 #: ../manage/roles/user-preferences-permissions.rst:87 msgid "Change account password" msgstr "" @@ -9617,7 +9614,6 @@ msgstr "" msgid "your only allowed authentication method." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:87 #: ../manage/roles/user-preferences-permissions.rst:91 msgid "``user_preferences.two_factor_authentication``" msgstr "" @@ -9654,7 +9650,7 @@ msgstr "" #: ../manage/scheduler.rst:19 msgid "" -"Schedulers can be used to send periodic reminder emails. Use :doc:`/system/" +"Schedulers can be used to send periodic reminder emails. Use :doc:`/misc/" "variables` to build highly-customized email templates." msgstr "" @@ -10663,7 +10659,7 @@ msgstr "" #: ../manage/text-modules.rst:57 msgid "" -"The example text modules below use :doc:`/system/variables` to dynamically " +"The example text modules below use :doc:`/misc/variables` to dynamically " "insert information like the customer's or agent's names." msgstr "" @@ -11012,8 +11008,8 @@ msgstr "" #: ../misc/object-conditions/basics.rst:144 #: ../misc/object-conditions/basics.rst:160 #: ../misc/object-conditions/basics.rst:168 -#: ../misc/object-conditions/basics.rst:178 ../settings/ticket.rst:2 -#: ../system/variables/ticket.rst:2 +#: ../misc/object-conditions/basics.rst:178 ../misc/variables/ticket.rst:2 +#: ../settings/ticket.rst:2 msgid "Ticket" msgstr "Billet" @@ -11248,7 +11244,7 @@ msgstr "" #: ../manage/trigger/how-do-they-work.rst:79 msgid "" -"Certain actions (such as *email*, *SMS* and *notes*) support :doc:`/system/" +"Certain actions (such as *email*, *SMS* and *notes*) support :doc:`/misc/" "variables`, which can be used to build highly-customized message templates." msgstr "" @@ -11277,7 +11273,7 @@ msgstr "" msgid "" "You can also combine static text with placeholders for text fields. Remember " "that the placeholders' values have to be known during trigger runtime. Learn " -"more about :doc:`/system/variables`." +"more about :doc:`/misc/variables`." msgstr "" #: ../manage/trigger/how-do-they-work.rst:105 @@ -12246,7 +12242,7 @@ msgstr "" msgid "" "When switched on, a code editor will be shown below, where you can configure " "custom payload for your webhook in JSON format. To insert supported :doc:`/" -"system/variables` use ``::`` or ``#{`` shortcuts for autocomplete." +"misc/variables` use ``::`` or ``#{`` shortcuts for autocomplete." msgstr "" #: ../manage/webhook/add.rst:103 @@ -14877,12144 +14873,12042 @@ msgid "" "powerful conditions with AND/OR relations." msgstr "" -#: ../settings/branding.rst:10 -msgid "Product Name" +#: ../misc/variables.rst:2 +msgid "Variables" msgstr "" -#: ../settings/branding.rst:7 +#: ../misc/variables.rst:4 msgid "" -"Defines the name of the application, shown in the web interface, tabs and " -"title bar of the web browser." -msgstr "" - -#: ../settings/branding.rst:10 -msgid "Default value: ``Zammad Helpdesk``" -msgstr "" - -#: ../settings/branding.rst:13 -msgid "Will be shown in the app and is included in email footers." -msgstr "" - -#: ../settings/branding.rst:19 -msgid "Logo" -msgstr "" - -#: ../settings/branding.rst:16 -msgid "Defines the logo of the application, shown in the login page of Zammad." +"Please note that this is just an overview of available variables. It might " +"be incomplete or variables might not be available within some functions. If " +"you're missing variables or are not sure if something is not working as " +"expected, feel free to ask over at the `Community `_." msgstr "" -#: ../settings/branding.rst:18 +#: ../misc/variables.rst:10 msgid "" -"Ensure to hit the \"Submit\" button after uploading the logo. Otherwise your " -"change will not be saved." +"Variables can be called by typing ``::`` (just like text modules in the " +"frontend), as long as you're in a supported text field within the backend. " +"Zammad will display all variables being available within this context and " +"replace it to the variable as soon as you selected an entry." msgstr "" -#: ../settings/branding.rst:22 +#: ../misc/variables.rst:15 msgid "" -"Allows to set the default language of the Zammad instance. The here defined " -"locale mostly acts as a fallback for:" +"You have an empty field which you referenced and it appears as ``-``? That's " +"currently working as designed - you might want to ensure that these fields " +"always have a value." msgstr "" -#: ../settings/branding.rst:25 -msgid "user preferences (if Zammad can't detect the users locale)" +#: ../misc/variables.rst:20 +msgid "Variable Categories" msgstr "" -#: ../settings/branding.rst:26 -msgid "CSV output (reporting, time accounting)" +#: ../misc/variables.rst:31 +msgid "Wait, What About Custom Objects?" msgstr "" -#: ../settings/branding.rst:30 -msgid "Define the timezone of your Zammad installation." +#: ../misc/variables.rst:33 +msgid "" +"Good point! Of course, we can't predict what objects you might create, but " +"we can give you a hint on how to put the puzzle together to get your custom " +"values." msgstr "" -#: ../settings/branding.rst:32 +#: ../misc/variables.rst:36 msgid "" -"This does not have any effect on timings for your agents or how Zammad " -"stores date and time values." +"For this, we'll talk about the inner part of the variable (so everything " +"within ``#{}``), please put the outer part around to have a valid variable. " +"The first part of the variable name consist of the object type. Currently " +"these are:" msgstr "" -#: ../settings/branding.rst:35 -msgid "Changing this value has direct consequences on the following areas:" +#: ../misc/variables.rst:41 +msgid "Ticket (``ticket``)" msgstr "" -#: ../settings/branding.rst:37 -msgid ":doc:`/manage/scheduler` tasks" +#: ../misc/variables.rst:42 +msgid "User (``user``)" msgstr "" -#: ../settings/branding.rst:38 -msgid "search indexing (and thus reporting)" +#: ../misc/variables.rst:43 +msgid "Organization (``organization``)" msgstr "" -#: ../settings/branding.rst:40 -msgid "calendar subscriptions" +#: ../misc/variables.rst:44 +msgid "Group (``group``)" msgstr "" -#: ../settings/branding.rst:41 -msgid "browser printing" +#: ../misc/variables.rst:46 +msgid "" +"The second part is the name of the attribute. This is the name you define " +"during object creation and can be found within the object attribute menu at " +"any time. The first and second part of a variable is divided by a point, e." +"g.: ``ticket.number`` which will in total be ``#{ticket.number}``." msgstr "" -#: ../settings/branding.rst:43 +#: ../misc/variables.rst:51 msgid "" -"Please note that some of above are fallbacks in case Zammad could not detect " -"the agents timezone correctly." +"Now, in some situations it's possible that you'll need to use a third part. " +"The best example for such a situation would be a ``select`` or ``tree-" +"select`` field which will by default return the key value, not it's display " +"name. For this, just extend your variable with ``.value``. This will result " +"in ``#{ticket.select.value}``." msgstr "" -#: ../settings/branding.rst:77 -msgid "Pretty Date" +#: ../misc/variables.rst:60 +msgid "Using Translated Variables" msgstr "" -#: ../settings/branding.rst:47 +#: ../misc/variables.rst:62 msgid "" -"This setting allows you to define how Zammad should display time stamps " -"within the interface to all users." +"If you want to use a translated variable in triggers or schedulers, you can " +"extend the placeholder like this: ``#{t(ticket.state.name)}``. The ``t`` " +"tells Zammad to search for fitting translated strings. The used output " +"language is based on the system language of Zammad which you can set in the " +"admin panel under :doc:`/settings/branding` or based on the selected locale " +"in the trigger/scheduler edit dialog." msgstr "" -#: ../settings/branding.rst:50 +#: ../misc/variables.rst:69 msgid "" -"This does not have any effect on how Zammad returns e.g. time values via " -"variables." -msgstr "" - -#: ../settings/branding.rst:77 -msgid "Choose in between the following options:" +"A possible use-case: you want to send your customers updates on tickets via " +"trigger or scheduler which should include the state of the ticket. Using the " +"default ``#{ticket.state.name}`` (without the translation flag ``t()``) " +"would lead to the output of the original (english) name of the state." msgstr "" -#: ../settings/branding.rst:64 -msgid "relative" +#: ../misc/variables.rst:75 +msgid "Date and Time Formatting" msgstr "" -#: ../settings/branding.rst:55 +#: ../misc/variables.rst:77 msgid "" -"This timestamp shows a relative time span until it switches to a date. Over " -"time, it will change as follows:" -msgstr "" - -#: ../settings/branding.rst:58 -msgid "just now" +"The system (trigger/scheduler selected) locale and timezone predefines a " +"default format of date and timestamp. This format is customizable by using " +"the ``dt()`` method." msgstr "" -#: ../settings/branding.rst:59 -msgid "5 minutes ago" +#: ../misc/variables.rst:79 +msgid "The method arguments are as follows:" msgstr "" -#: ../settings/branding.rst:60 -msgid "3 days 1 hour ago" +#: ../misc/variables.rst:81 +msgid "The date or timestamp variable you want to format." msgstr "" -#: ../settings/branding.rst:61 -msgid "``03/04/2022``" +#: ../misc/variables.rst:82 +msgid "The output format string." msgstr "" -#: ../settings/branding.rst:63 -msgid "Hovering the timestamp helps, you'll always get a clean timestamp then." +#: ../misc/variables.rst:83 +msgid "The timezone to apply (optional)." msgstr "" -#: ../settings/branding.rst:71 -msgid "absolute" -msgstr "" +#: ../misc/variables.rst:85 +#: ../system/objects/external-data-source-example.rst:23 +#, fuzzy +msgid "**Example:**" +msgstr "Exemple" -#: ../settings/branding.rst:67 +#: ../misc/variables.rst:86 msgid "" -"This timestamp always includes the week day. For one week after creation, " -"the timestamp will not contain the date itself: Thursday 18:35." -msgstr "" - -#: ../settings/branding.rst:71 -msgid "After a week it will switch to: ``Friday 4. Mar 16:00``." +"``#{dt(ticket.updated_at, \"%A %Y-%m-%d %H:%M in the office\", \"Europe/" +"Berlin\")}``" msgstr "" -#: ../settings/branding.rst:76 -msgid "timestamp" +#: ../misc/variables.rst:87 +msgid "Monday, 2024-03-18 15:31 in the office" msgstr "" -#: ../settings/branding.rst:74 +#: ../misc/variables.rst:89 msgid "" -"This will cause Zammad to show a complete timestamp according to your locale " -"defaults. For English this could be e.g. ``2022/12/03 2:40 pm`` or for " -"German e.g. ``12.03.2022 14:40``." +"If you want to use our example, make sure to paste the string above without " +"formatting (``CTRL+Shift+v``), otherwise it won't work." msgstr "" -#: ../settings/branding.rst:78 -msgid "Default setting: ``relative``." +#: ../misc/variables.rst:93 +msgid "The following table lists available format directives:" msgstr "" -#: ../settings/security.rst:2 -msgid "Security" +#: ../misc/variables.rst:99 +msgid "Parameter" msgstr "" -#: ../settings/security.rst:4 -msgid "" -"For your overview we split each tab within security settings into its own " -"page:" +#: ../misc/variables.rst:102 +msgid "``%Y``" msgstr "" -#: ../settings/security/base.rst:2 ../settings/system/base.rst:2 -#: ../settings/ticket.rst:8 -msgid "Base" -msgstr "Base" - -#: ../settings/security/base.rst:5 -msgid "New User Accounts" +#: ../misc/variables.rst:103 +msgid "Year with 4 digits" msgstr "" -#: ../settings/security/base.rst:9 -msgid "" -"Activates the `register as a new customer` function on the login page. If " -"set to ``no`` only administrators or agents can create new accounts manually." +#: ../misc/variables.rst:104 +msgid "Use ``%y`` for year with 2 digits" msgstr "" -#: ../settings/security/base.rst:13 ../settings/security/base.rst:38 -#: ../settings/security/base.rst:66 -msgid "Default setting: ``yes``" +#: ../misc/variables.rst:105 +msgid "``%m``" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing activated \"New User Accounts\" setting" +#: ../misc/variables.rst:106 +msgid "Month of year (as number with zero-padding)" msgstr "" -#: ../settings/security/base.rst:22 -msgid "" -"Deactivation of above function **does not** deactivate automatic account " -"creation! This means: If a user writes e.g. an email to Zammad and has no " -"account yet, Zammad will automatically create the account. User accounts are " -"a direct dependency of tickets and thus technically mandatory." +#: ../misc/variables.rst:107 +msgid "Use ``%-m`` for month without zero-padding" msgstr "" -#: ../settings/security/base.rst:29 -msgid "Lost Password" +#: ../misc/variables.rst:108 +msgid "``%d``" msgstr "" -#: ../settings/security/base.rst:33 -msgid "" -"Activates the `lost password` function on the login page. If set to ``no`` " -"only administrators may change the user's password - users may update their " -"own password if they're still logged in and they have the required :doc:" -"`permission `." +#: ../misc/variables.rst:109 +msgid "Day of month (as number with zero-padding)" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing activated \"Lost Password\" setting" +#: ../misc/variables.rst:110 +msgid "Use ``%e`` for day without zero-padding" msgstr "" -#: ../settings/security/base.rst:49 -msgid "" -"With third party authentications - but especially LDAP - you may want to " -"disable this function. Zammad **will not** change third party login " -"passwords and instead set or change the local password!" +#: ../misc/variables.rst:111 +msgid "``%H``" msgstr "" -#: ../settings/security/base.rst:56 -msgid "Password Login" +#: ../misc/variables.rst:112 +msgid "Hour of day in 24h notation with zero-padding" msgstr "" -#: ../settings/security/base.rst:60 -msgid "" -"Activates the username & password login by default and if no third-party " -"login is activated. Disabling password login on the Zammad login page only " -"takes effect if you enable any :doc:`third-party`." +#: ../misc/variables.rst:113 +msgid "Use ``%k`` for hour without zero-padding" msgstr "" -#: ../settings/security/base.rst:64 -msgid "See :doc:`third-party` for supported third-party logins." +#: ../misc/variables.rst:114 +msgid "``%I``" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing de-activated \"Password Login\" setting" +#: ../misc/variables.rst:115 +msgid "Hour of day in 12h notation with zero-padding" msgstr "" -#: ../settings/security/base.rst:77 +#: ../misc/variables.rst:116 msgid "" -"To help administrators to overcome \"login issues\", Zammad automatically " -"offers a password request for administrator users. This allows you to adjust " -"Third-Party applications even if the login does no longer work!" +"Use ``%l`` for hour without zero-padding and ``%p`` / ``%P`` for meridian " +"indicator" msgstr "" -#: ../settings/security/base.rst:84 -msgid "Session Timeout" +#: ../misc/variables.rst:117 +msgid "``%M``" msgstr "" -#: ../settings/security/base.rst:86 -msgid "" -"All settings below by default are set to ``4 weeks``. Session Timeout " -"defines the life time of a users session. As soon as it's reached, Zammad " -"will automatically log off the session in question." +#: ../misc/variables.rst:118 +msgid "Minute of hour" msgstr "" -#: ../settings/security/base.rst:91 -msgid "" -"Zammad takes the highest value set assigned for the user based on the " -"permissions." +#: ../misc/variables.rst:120 +msgid "``%S``" msgstr "" -#: ../settings/security/base.rst:94 -msgid "``admin``" +#: ../misc/variables.rst:121 +msgid "Second of Minute" msgstr "" -#: ../settings/security/base.rst:96 -msgid "``ticket.customer``" +#: ../misc/variables.rst:123 +msgid "``%A``" msgstr "" -#: ../settings/security/base.rst:97 -msgid "``default`` (fallback if user doesn't have above permissions set)" +#: ../misc/variables.rst:124 +msgid "Weekday name" msgstr "" -#: ../settings/security/base.rst:99 -msgid "" -"All settings act independently from each other allowing you to disable the " -"timeouts for e.g. admins, but not agents." +#: ../misc/variables.rst:125 +msgid "Use ``%a`` for abbreviated name or ``%^A`` for uppercase name" msgstr "" -#: ../settings/security/base.rst:115 -#: ../system/integrations/checkmk/api-reference.rst:13 -msgid "Example" +#: ../misc/variables.rst:126 +msgid "``%B``" msgstr "" -#: ../settings/security/base.rst:107 -msgid "Let's suppose you configured the following session timeouts" +#: ../misc/variables.rst:127 +msgid "Month name" msgstr "" -#: ../settings/security/base.rst:104 -msgid "default: 3 weeks" +#: ../misc/variables.rst:128 +msgid "Use ``%b`` for abbreviated name" msgstr "" -#: ../settings/security/base.rst:105 -msgid "admin: 2 weeks" +#: ../misc/variables.rst:129 +msgid "``%U``" msgstr "" -#: ../settings/security/base.rst:106 -msgid "ticket.agent: 4 weeks" +#: ../misc/variables.rst:130 +msgid "Week number of current year" msgstr "" -#: ../settings/security/base.rst:107 -msgid "ticket.customer: 1 week" +#: ../misc/variables.rst:131 +msgid "Use ``%W`` for a different calculation method" msgstr "" -#: ../settings/security/base.rst:115 -msgid "This results in the following situations" +#: ../misc/variables.rst:134 +msgid "" +"We support the known format directives for the Ruby built-in method " +"``strftime`` of the ``DateTime`` class. For more information, see `here " +"`_." msgstr "" -#: ../settings/security/base.rst:110 -msgid "a user with ``admin`` permission will have a timeout of 2 weeks" +#: ../misc/variables/article.rst:2 +msgid "Articles" msgstr "" -#: ../settings/security/base.rst:111 +#: ../misc/variables/article.rst:4 ../misc/variables/config.rst:4 +#: ../misc/variables/current-user.rst:4 ../misc/variables/ticket.rst:4 msgid "" -"a user with ``admin`` and ``ticket.agent`` permissions will have a timeout " -"of 2 weeks" +"If you're missing variables or are not sure if something is not working as " +"expected, feel free to ask over at the `Community `_." msgstr "" +"Si vous manquez de variables ou n'êtes pas certain que quelque chose ne " +"fonctionne pas tel que prévu, n'hésitez pas à demander à la `Communauté " +"` _." -#: ../settings/security/base.rst:113 +#: ../misc/variables/article.rst:6 +#, fuzzy +#| msgid "" +#| "Below you can find all available ticket-based variables within Zammad. " +#| "These can be called via Triggers for example. If you're unsure if Zammad " +#| "does support variables at the point you're at, you can try to type ``::`` " +#| "to check." msgid "" -"a user with ``ticket.customer`` permission will have a timeout of 1 week" +"Below you can find all available ticket article-based variables within " +"Zammad. These can be called via triggers for example. If you're unsure if " +"Zammad does support variables at the point you're at, you can try to type " +"``::`` to check." msgstr "" +"Vous trouverez ci-dessous toutes les variables, disponibles dans Zammad, " +"basées sur les billets. Par exemple, celles-ci peuvent être appelées via des " +"déclencheurs. Si vous ne savez pas si Zammad prend en charge une certaine " +"variable, vous pouvez essayer de taper ``::`` pour vérifier." -#: ../settings/security/base.rst:115 +#: ../misc/variables/article.rst:9 ../misc/variables/config.rst:9 +#: ../misc/variables/ticket.rst:9 msgid "" -"a user with neither ``admin``, ``ticket.agent`` nor ``ticket.customer`` " -"permissions will have a timeout of 3 weeks" +"The below list gives you an example what kind of data you can expect, it's " +"not intended to explain the data itself." msgstr "" +"La liste ci-dessous vous donne un exemple du type de données auquel vous " +"pouvez vous attendre; cependant, elle n'est pas destinée à expliquer les " +"données elles-mêmes." -#: ../settings/security/password.rst:4 -msgid "" -"This section allows you to define password requirements for the local user " -"accounts." +#: ../misc/variables/article.rst:11 +msgid "Article Variables" msgstr "" -#: ../settings/security/password.rst:9 -msgid "" -"Zammad does **not** allow you to change your LDAP password, instead, it will " -"set a password in its local database which might confuse your users. This " -"might be addressed in the future by `#1169 `_." +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "name" +msgstr "Nom" + +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "variable" +msgstr "Variable" + +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "example" +msgstr "Exemple" + +#: ../misc/variables/article.rst:1 +msgid "Article > Cc" msgstr "" -#: ../settings/security/password.rst:14 -msgid "**Exception for admins**" +#: ../misc/variables/article.rst:1 +msgid "``#{article.cc}``" msgstr "" -#: ../settings/security/password.rst:16 -msgid "" -"Please note that below password policies *do not* affect administrators " -"setting passwords on user accounts. While this seems strange and not safe we " -"believe that an administrator knowing an user's password is insecure as well." +#: ../misc/variables/article.rst:1 +msgid "``jdoe@example.com, company@example.com``" msgstr "" -#: ../settings/security/password.rst:21 -msgid "The suggested workflow is either:" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Address" msgstr "" -#: ../settings/security/password.rst:23 -msgid "" -"to use third party logins to not require local passwords at all **- or -**" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.address}``" msgstr "" -#: ../settings/security/password.rst:25 -msgid "to require your *user to reset the password* upon first login." +#: ../misc/variables/article.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:27 -msgid "" -"This way administrators are not required to set a user's password at all!" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Department" msgstr "" -#: ../settings/security/password.rst:31 -msgid "Maximum Failed Logins" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.department}``" msgstr "" -#: ../settings/security/password.rst:33 -msgid "" -"You can choose a value between ``4`` and ``20``. This defines how often a " -"login to a user account may fail until Zammad will lock it. Your users can " -"always use the \"forgot password\" function to change their password and " -"unlock their account." +#: ../misc/variables/article.rst:1 +msgid "``Sales`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:38 -msgid "The default value is ``10``." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Email" msgstr "" -#: ../settings/security/password.rst:42 -msgid "Beside changing the user's password, you can also unlock accounts via" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.email}``" msgstr "" -#: ../settings/security/password.rst:44 -msgid ":ref:`user management list `" +#: ../misc/variables/article.rst:1 +msgid "``jdoe@example.com``" msgstr "" -#: ../settings/security/password.rst:45 -msgid ":docs:`console `" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Fax" msgstr "" -#: ../settings/security/password.rst:46 -msgid ":docs:`API `" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.fax}``" msgstr "" -#: ../settings/security/password.rst:50 -msgid "Failed logins via LDAP no longer lock accounts." +#: ../misc/variables/article.rst:1 +msgid "``+4930123456789`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:53 -msgid "2 Lower Case And 2 Upper Case Characters" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Firstname" msgstr "" -#: ../settings/security/password.rst:55 -msgid "" -"You can add complexity to passwords by enforcing at least 2 upper and lower " -"case characters." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.firstname}``" msgstr "" -#: ../settings/security/password.rst:58 ../settings/security/password.rst:83 -msgid "The default value is ``no``." +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Joe`` or empty if not set" +msgstr "``Joe`` ou vide si non défini" + +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Lastname" msgstr "" -#: ../settings/security/password.rst:62 -msgid "Minimum Length" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.lastname}``" msgstr "" -#: ../settings/security/password.rst:64 -msgid "" -"This defines the minimum password length required for users to provide (from " -"``4`` to ``20``)." +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +#: ../misc/variables/ticket.rst:1 +msgid "``Doe`` or empty if not set" +msgstr "``Doe`` ou vide si non défini" + +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Login" msgstr "" -#: ../settings/security/password.rst:67 -msgid "The default value is ``6``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.login}``" msgstr "" -#: ../settings/security/password.rst:71 -msgid "Digit Required" +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +#: ../misc/variables/ticket.rst:1 +msgid "``jdoe``" +msgstr "``jdoe``" + +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Mobile" msgstr "" -#: ../settings/security/password.rst:73 -msgid "This enforces your users to use at least one digit within the password." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.mobile}``" msgstr "" -#: ../settings/security/password.rst:75 -msgid "The default value is ``yes``." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Note" msgstr "" -#: ../settings/security/password.rst:78 -msgid "Special Character Required" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.note}``" msgstr "" -#: ../settings/security/password.rst:80 -msgid "" -"This setting allows you to improve your password quality even more by " -"enforcing the password to contain at least one special character." +#: ../misc/variables/article.rst:1 +msgid "``Some note about user`` or empty if not set in user object" msgstr "" -#: ../settings/security/ssl-certificates.rst:2 -msgid "SSL Certificates" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Phone" msgstr "" -#: ../settings/security/ssl-certificates.rst:7 -msgid "" -"Zammad offers the possibility to upload custom certificates and custom " -"Certificate Authority (CA) certificates. This can be useful if you want to " -"connect Zammad the secure way to other systems which are using custom " -"certificates." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.phone}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:12 -msgid "" -"An example usecase might be: You have an internal LDAP server that is not " -"accessible from the internet, and you want a SSL-encrypted connection, using " -"a custom certificate." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > VIP" msgstr "" -#: ../settings/security/ssl-certificates.rst:19 -msgid "" -"You should have an existing custom certificate file and/or a custom CA " -"certificate file, which you want to add to Zammad. As filetype ``.crt`` is " -"supported and the certificate format has to be PEM (Base64 ASCII)." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.vip}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:25 -msgid "" -"When you import a custom CA certificate, all certificates generated with " -"this are trusted. This can be useful if you have more than one system/" -"certificate you want to connect to and the certificates are issued from the " -"same custom CA." +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +msgid "``true`` or ``false``" msgstr "" -#: ../settings/security/ssl-certificates.rst:31 -msgid "Add a Certificate" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Web" msgstr "" -#: ../settings/security/ssl-certificates.rst:33 -msgid "" -"To add a custom certificate or a custom CA certificate, head over to the " -"Admin panel > Settings > Security > SSL Certificates. Here you can find a " -"\"Add SSL Certificate\" button. In the dialog you can either select a " -"certificate file or paste the content of the certificate:" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.web}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate adding dialog" +#: ../misc/variables/article.rst:1 +msgid "``https://zammad.com`` or empty if not set in user object" msgstr "" -#: ../settings/security/ssl-certificates.rst:43 -msgid "" -"After selecting a file or pasting the content of the certificate, click on " -"the \"Add\" button to finally upload it to Zammad. Then, the certificates " -"are immediately effective, no restart or similar required." +#: ../misc/variables/article.rst:1 +msgid "Article > Created" msgstr "" -#: ../settings/security/ssl-certificates.rst:49 -msgid "" -"Please note that only single certificate files are supported. That means if " -"you want to import a certificate / CA certificate, it must contain **only " -"one** certificate." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_at}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:54 -msgid "Certificate Overview" +#: ../misc/variables/article.rst:1 +msgid "``2019-10-08 15:24:47 UTC``" msgstr "" -#: ../settings/security/ssl-certificates.rst:56 -msgid "" -"After you added a certificate, you can see a table with information for each " -"added certificate:" +#: ../misc/variables/article.rst:1 +msgid "Article > From" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing table of added certificates" +#: ../misc/variables/article.rst:1 +msgid "``#{article.from}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:64 +#: ../misc/variables/article.rst:1 msgid "" -"Here you can download the certificate or delete it, if you don't need it " -"anymore." +"``Joe Doe `` may differ, depends on ``FROM`` of send mail" msgstr "" -#: ../settings/security/ssl-certificates.rst:68 -#, fuzzy -msgid "Deleting Certificates" -msgstr "Bloquer les notifications" +#: ../misc/variables/article.rst:1 +msgid "Article > Sender > Name" +msgstr "" -#: ../settings/security/ssl-certificates.rst:70 -msgid "" -"If you want to delete a specific certificate, you can do it by clicking on " -"the menu in the actions column and selecting delete:" +#: ../misc/variables/article.rst:1 +msgid "``#{article.sender.name}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate deletion button" +#: ../misc/variables/article.rst:1 +msgid "``Customer``, ``Agent`` or ``System``" msgstr "" -#: ../settings/security/ssl-certificates.rst:79 -msgid "Downloading Certificates" +#: ../misc/variables/article.rst:1 +msgid "Article > Subject" msgstr "" -#: ../settings/security/ssl-certificates.rst:81 -msgid "" -"If you want to download your certificates, you can do this as well via " -"corresponding action buttons." +#: ../misc/variables/article.rst:1 +msgid "``#{article.subject}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate download button" +#: ../misc/variables/article.rst:1 +msgid "``My amazing subject``" msgstr "" -#: ../settings/security/third-party.rst:13 -msgid "Login Providers" +#: ../misc/variables/article.rst:1 +msgid "Article > Text" msgstr "" -#: ../settings/security/third-party.rst:2 -msgid "Third-Party Applications" +#: ../misc/variables/article.rst:1 +msgid "``#{article.body}``" msgstr "" -#: ../settings/security/third-party.rst:4 -msgid "" -"Third party authentication is a great way to help your users to login to " -"Zammad more easily. If the account is yet unknown, Zammad will create a new " -"user automatically, without the user needed to interact (e.g. type in his " -"name). Another big advantage of this feature is that your user doesn't need " -"to remember another password." +#: ../misc/variables/article.rst:1 +msgid "``Test`` without formatting (plain)" msgstr "" -#: ../settings/security/third-party.rst:10 -msgid "" -"You can deactivate logging in via :ref:`security_password_login` if any of " -"the mentioned authentication providers are enabled in your instance." +#: ../misc/variables/article.rst:1 +msgid "Article > TicketID" msgstr "" -#: ../settings/security/third-party.rst:27 -msgid "" -"We're currently missing documentation for the following login providers:" +#: ../misc/variables/article.rst:1 +msgid "``#{article.ticket_id}``" msgstr "" -#: ../settings/security/third-party.rst:29 -msgid "LinkedIn" +#: ../misc/variables/article.rst:1 +msgid "``1`` (not ticket number)" msgstr "" -#: ../settings/security/third-party.rst:30 -msgid "Weibo" +#: ../misc/variables/article.rst:1 +msgid "Article > To" msgstr "" -#: ../settings/security/third-party.rst:35 -msgid "Automatic Account Link on Initial Logon" +#: ../misc/variables/article.rst:1 +msgid "``#{article.to}``" msgstr "" -#: ../settings/security/third-party.rst:37 -msgid "" -"In general there's two possible options for Zammad on how to deal with " -"already known users as they try to authenticate against a third-party " -"application. By default, Zammad will not automatically link \"unknown\" " -"authentication providers to existing accounts." +#: ../misc/variables/article.rst:1 +msgid "``helpdesk@example.com``" msgstr "" -#: ../settings/security/third-party.rst:42 -msgid "" -"This means that the user has to manually link authentication providers to " -"their accounts (for more about this :user-docs:`consult the user " -"documentation `)." +#: ../misc/variables/article.rst:1 +msgid "Article > Type > Name" msgstr "" -#: ../settings/security/third-party.rst:46 -msgid "" -"Sometimes this doesn't come in handy as this also means you'll receive error " -"messages about \"email address being in use already\" for (yet) unknown " -"third-party authentication methods." +#: ../misc/variables/article.rst:1 +msgid "``#{article.type.name}``" msgstr "" -#: ../settings/security/third-party.rst:50 +#: ../misc/variables/article.rst:1 msgid "" -"If you want to allow your users to always be able to log in, no matter what, " -"you may want to enable ``Automatic account link on initial logon``." +"``email`` (`list of article types `_)" msgstr "" -#: ../settings/security/third-party.rst:None -msgid "" -"Screenshot highlighting the \"Automatic account link on initial logon\"\n" -"setting" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Address" msgstr "" -#: ../settings/security/third-party.rst:60 -msgid "Automatic Account Linking Notification" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.address}``" msgstr "" -#: ../settings/security/third-party.rst:64 -msgid "" -"To improve security and your users awareness, you can enable Zammad to " -"notify your users when a new third-party application has been linked to " -"their account." -msgstr "" - -#: ../settings/security/third-party.rst:68 -msgid "" -"This notification is sent out once per third-party application. Zammad does " -"also mention the method used, e.g.: ``Microsoft``." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Department" msgstr "" -#: ../settings/security/third-party.rst:71 -msgid "By default this setting is not active (set to ``no``)." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.department}``" msgstr "" -#: ../settings/security/third-party.rst:0 -msgid "" -"Screenshot showing sample notification mail after initial\n" -"third-party linking" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Email" msgstr "" -#: ../settings/security/third-party.rst:85 -msgid "" -"This notification is only sent if the account in question already exists. If " -"the login via the third-party also creates the missing account, the " -"notification will be skipped." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.email}``" msgstr "" -#: ../settings/security/third-party.rst:89 -msgid "This means it only affects:" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Fax" msgstr "" -#: ../settings/security/third-party.rst:91 -msgid "manual account linking within the third-party page of the users profile" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.fax}``" msgstr "" -#: ../settings/security/third-party.rst:92 -msgid "" -"logging into an existing local account by utilizing the *automatic account " -"link on initial logon* functionality" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Firstname" msgstr "" -#: ../settings/security/third-party.rst:None -msgid "" -"Screenshot showing the \"automatic account linking notification\"\n" -"setting" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.firstname}``" msgstr "" -#: ../settings/security/third-party.rst:100 -msgid "No User Creation on Logon" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Lastname" msgstr "" -#: ../settings/security/third-party.rst:102 -msgid "" -"By default, Zammad will create a new user account if the user logs in via a " -"third-party application and the account doesn't exist yet." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.lastname}``" msgstr "" -#: ../settings/security/third-party.rst:105 -msgid "" -"If you want to prevent Zammad from creating new accounts on logon, you can " -"disable this feature by setting ``No user creation on logon`` to ``yes``." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Login" msgstr "" -#: ../settings/security/third-party.rst:None -msgid "Screenshot showing the \"no user creation on logon\" setting" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.login}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via Facebook To do " -"so, you need to follow these steps:" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Mobile" msgstr "" -#: ../settings/security/third-party/facebook.rst:9 -msgid "Register Facebook App" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.mobile}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:11 -msgid "" -"Visit [https://developers.facebook.com/apps/] and click on \"Add a new App\"" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Note" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "initial page" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.note}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:17 -msgid "After that enter the app settings" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Phone" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "Create App" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.phone}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:22 -msgid "Navigate to \"Settings\" and fill in this infromation" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > VIP" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "App Settings" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.vip}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:27 -msgid "Navigate to app review and Check \"Make [appname] public?\"" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Web" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "App Review" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.web}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:35 -msgid "Configure Zammad as Facebook App" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated" msgstr "" -#: ../settings/security/third-party/facebook.rst:37 -msgid "" -"Navigate to \"Admin -> Security -> Third Party Applications\" and enter the " -"App ID and the App Secret. You can find this Key in the Dashbard of your " -"Facebok app." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_at}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "Zammad Configuration" +#: ../misc/variables/article.rst:1 +msgid "Article > Visibility" msgstr "" -#: ../settings/security/third-party/facebook.rst:44 -#: ../settings/security/third-party/github.rst:43 -#: ../settings/security/third-party/gitlab.rst:46 -msgid "" -"Now you can link accounts via \"Avatar -> Profile -> Link Accounts\" or " -"login via Zammad login page." +#: ../misc/variables/article.rst:1 +msgid "``#{article.internal}``" msgstr "" -#: ../settings/security/third-party/github.rst:2 -#: ../system/integrations/github.rst:2 -msgid "GitHub" +#: ../misc/variables/article.rst:1 +msgid "``false`` or ``true`` (false if not internal)" msgstr "" -#: ../settings/security/third-party/github.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via GitHub. To " -"activate the quick login you need to enable OAuth for GitHub." +#: ../misc/variables/article.rst:1 +msgid "Article Text as HTML (not referenced)" msgstr "" -#: ../settings/security/third-party/github.rst:8 -msgid "Register GitHub App" +#: ../misc/variables/article.rst:1 +msgid "``#{article.body_as_html}``" msgstr "" -#: ../settings/security/third-party/github.rst:10 -msgid "" -"Visit https://www.github.com/settings/applications/new and enter the app " -"settings. As callback URL enter \"https://zammad_host/auth/github/callback\" " -"where zammad_host has to be replaced with your Zammad FQDN" +#: ../misc/variables/article.rst:1 +msgid "``Test`` with formatting" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "Register OAuth app on www.github.com" -msgstr "" +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "Ticket > Article#" +msgstr "Billet > Article #:" -#: ../settings/security/third-party/github.rst:19 -msgid "Configure Zammad as GitHub App" -msgstr "" +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "``#{ticket.article_count}``" +msgstr "``#{ticket.article_count}``" -#: ../settings/security/third-party/github.rst:21 -msgid "" -"Enter the \"APP ID\" and the \"APP SECRET\" from the GitHub OAUTH " -"Applications Dashboard" +#: ../misc/variables/article.rst:1 +msgid "``1`` number of ticket articles" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub config in Zammad admin interface" +#: ../misc/variables/config.rst:2 +msgid "Config" msgstr "" -#: ../settings/security/third-party/github.rst:28 +#: ../misc/variables/config.rst:6 msgid "" -"After you configured the GitHub credentials and activated the login method, " -"you should see a new icon on the login page." +"Below you'll find config related variables. These hold useful configuration " +"information that you can use within e.g. triggers to show necessary " +"information to your customer." msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub logo on login page" +#: ../misc/variables/config.rst:11 +msgid "Config Variables" msgstr "" -#: ../settings/security/third-party/github.rst:34 -msgid "" -"If you click on the icon you will be redirected to GitHub and see something " -"similar to this:" +#: ../misc/variables/config.rst:1 +msgid "Config > Fully Qualified Domain Name" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub oauth page" +#: ../misc/variables/config.rst:1 +msgid "``#{config.fqdn}``" msgstr "" -#: ../settings/security/third-party/github.rst:40 -#: ../settings/security/third-party/gitlab.rst:42 -msgid "" -"When you grant the access you will be redirected to your Zammad instance and " -"logged in as a customer." +#: ../misc/variables/config.rst:1 +msgid "``zammad.example.com``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:2 -msgid "Gitlab" +#: ../misc/variables/config.rst:1 +msgid "Config > HTTP type" msgstr "" -#: ../settings/security/third-party/gitlab.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via Gitlab. To " -"activate the quick login you need to enable OAuth for Gitlab." +#: ../misc/variables/config.rst:1 +msgid "``#{config.http_type}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:8 -msgid "Register Gitlab App" +#: ../misc/variables/config.rst:1 +msgid "``https`` or ``http``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:10 -msgid "To register an app in Gitlab open your profile and select applications." +#: ../misc/variables/config.rst:1 +msgid "Config > Organization" msgstr "" -#: ../settings/security/third-party/gitlab.rst:12 -msgid "" -"As callback URL enter \"https://zammad-fqdn/auth/gitlab/callback\" where " -"zammad-fqdn has to be replaced with your Zammad FQDN" +#: ../misc/variables/config.rst:1 +msgid "``#{config.organization}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Register OAuth app on gitlab instance" +#: ../misc/variables/config.rst:1 +msgid "" +"``Zammad GmbH`` value set in `Branding `_" msgstr "" -#: ../settings/security/third-party/gitlab.rst:18 -msgid "Just select *read_user* under scopes as in the screenshot and save it." +#: ../misc/variables/config.rst:1 +msgid "Config > Product Name" msgstr "" -#: ../settings/security/third-party/gitlab.rst:21 -msgid "Configure Zammad as Gitlab App" +#: ../misc/variables/config.rst:1 +msgid "``#{config.product_name}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:23 +#: ../misc/variables/config.rst:1 msgid "" -"Enter the \"APP ID\" and the \"APP SECRET\" from the Gitlab OAUTH " -"Applications Dashboard and your Gitlab-URL in the \"SITE\" field." +"``Helpdesk`` value set in `Branding `_" msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab config in Zammad admin interface" +#: ../misc/variables/config.rst:1 +msgid "Config > SystemID" msgstr "" -#: ../settings/security/third-party/gitlab.rst:30 -msgid "" -"After you configured the Gitlab credentials and activated the login method, " -"you should see a new icon on the login page." +#: ../misc/variables/config.rst:1 +msgid "``#{config.system_id}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab logo on login page" +#: ../misc/variables/config.rst:1 +msgid "``31`` (value between 1 and 99)" msgstr "" -#: ../settings/security/third-party/gitlab.rst:36 -msgid "" -"If you click on the icon you will be redirected to Gitlab and see something " -"similar to this:" +#: ../misc/variables/config.rst:1 +msgid "Config > Ticket Hook" msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab oauth page" +#: ../misc/variables/config.rst:1 +msgid "``#{config.ticket_hook}``" msgstr "" -#: ../settings/security/third-party/google.rst:4 -msgid "" -"With some easy and fast steps, you can enable Zammad to authenticate your " -"users via Google." +#: ../misc/variables/config.rst:1 +msgid "``Ticket#``" msgstr "" -#: ../settings/security/third-party/google.rst:8 -msgid "Register a Google App" +#: ../misc/variables/current-user.rst:2 +msgid "Current User" msgstr "" -#: ../settings/security/third-party/google.rst:10 +#: ../misc/variables/current-user.rst:6 msgid "" -"First of all, we need to create a new project - you can skip this step if " -"you already have one." +"Current user variables always return values of the current user that caused " +"e.g. a trigger to run." msgstr "" -#: ../settings/security/third-party/google.rst:15 +#: ../misc/variables/current-user.rst:8 msgid "" -"Use this link to create a new project: https://console.cloud.google.com/" -"projectcreate" +"Due to the above fact, these variables are often not (yet) set or available " +"for usage." msgstr "" -#: ../settings/security/third-party/google.rst:18 +#: ../misc/variables/current-user.rst:10 msgid "" -"Now expand the menu, expand \"APIs & Services\" and select \"Credentials\". " -"Go to the tab \"OAuth consent screen\" first and ensure to fill in the " -"requested information - without doing so you can't create credentials!" +"In situations where e.g. schedulers or triggers run, this most likely is " +"nothing you want to use." msgstr "" -#: ../settings/security/third-party/google.rst:None -msgid "Creating a consent screen" +#: ../misc/variables/current-user.rst:13 +msgid "Current User Variables" msgstr "" -#: ../settings/security/third-party/google.rst:25 -msgid "" -"After filling in and saving the consent screen information, you can go to " -"the \"Credentials\" tab and create new \"OAuth client ID\"-Credentials." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Address" msgstr "" -#: ../settings/security/third-party/google.rst:28 -msgid "" -"Fill in the necessary information as follows and replace ``zammad_host`` " -"with your FQDN:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.address}``" msgstr "" -#: ../settings/security/third-party/google.rst:31 -msgid "**Application type** ``[x] Web application``" -msgstr "" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set" +msgstr "``12345, rue des Cadeaux, Pôle Nord HoH oHo`` ou vide si non défini" -#: ../settings/security/third-party/google.rst:34 -msgid "**Authorized JavaScript origins** ``https://zammad_host/``" -msgstr "" +#: ../misc/variables/current-user.rst:1 +#, fuzzy +msgid "Current User > Avatar" +msgstr "Billet > Organisation > Note" -#: ../settings/security/third-party/google.rst:37 -msgid "" -"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" -"callback``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/google.rst:None -msgid "Adding a new OAuth client ID" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "avatar picture with width and height in pixel (e.g. 60,60)" msgstr "" -#: ../settings/security/third-party/google.rst:43 -msgid "" -"After creating the credentials, go to your Zammad installation and navigate " -"to \"Admin > Security > Third Party Applications\" > Google. Enter your " -"Client ID and Client secret here." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created at" msgstr "" -#: ../settings/security/third-party/google.rst:None -msgid "Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_at}``" msgstr "" -#: ../settings/security/third-party/google.rst:50 -msgid "After submitting, the login via Google can be used." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC``" +msgstr "``2019-10-07 16:25:00 UTC``" + +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Address" msgstr "" -#: ../settings/security/third-party/microsoft.rst:2 -msgid "Microsoft" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.address}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:4 -msgid "" -"Zammad's Microsoft connection allows your users with Microsoft accounts to " -"login. This works for Azure users as well and can be an alternative to :doc:" -"`/system/integrations/ldap/index`." +#: ../misc/variables/current-user.rst:1 +#, fuzzy +msgid "Current User > Created by > Avatar" +msgstr "Billet > Créé par > Nom de famille" + +#: ../misc/variables/current-user.rst:1 +#, fuzzy +msgid "``#{user.created_by.avatar(60,60)}``" +msgstr "``#{ticket.created_by.lastname}``" + +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Department" msgstr "" -#: ../settings/security/third-party/microsoft.rst:10 -msgid "" -"This documentation part does not cover our :doc:`📧 Microsoft 365 email " -"channel `." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.department}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screenshot showing Microsoft login button on Zammad login screen." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Sales`` or empty if not set" +msgstr "``Ventes`` ou vide si non défini" + +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Email" msgstr "" -#: ../settings/security/third-party/microsoft.rst:30 -#: ../settings/security/third-party/microsoft.rst:53 -msgid "Supported account types:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.email}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:22 -msgid "" -"Please note that Zammad only supports these account types (App dependent):" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``jdoe@customer.tld``" +msgstr "``jdoe@customer.tld``" + +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Fax" msgstr "" -#: ../settings/security/third-party/microsoft.rst:35 -msgid "Avatars of signing in users:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.fax}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:33 -msgid "" -"Zammad currently ignores user avatars. If the user is registered with e.g. " -"Gravatar, Zammad will fetch the avatar from there if enabled. See :doc:" -"`Zammad Image Service ` for more." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``004930123464789`` or empty if not set" +msgstr "``004930123464789`` ou vide si non défini" + +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Firstname" msgstr "" -#: ../settings/security/third-party/microsoft.rst:38 -msgid "Step 1 - Register a Microsoft App for Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.firstname}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:40 -msgid "" -"Login to the `Microsoft Azure Portal `_ and " -"navigate to App registrations to create a new app. Provide the requested " -"information as follows and register your app." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``John`` or empty if not set" +msgstr "``John`` ou vide si non défini" + +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Lastname" msgstr "" -#: ../settings/security/third-party/microsoft.rst:46 -msgid "Name:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.lastname}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:45 -msgid "" -"Any meaningful name fitting, this name will be displayed to users trying to " -"authenticate with this app." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Login" msgstr "" -#: ../settings/security/third-party/microsoft.rst:49 -msgid "Choose one of the above mentioned account types (see Limitations)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.login}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:51 -msgid "" -"The correct account type depends on your use case. If you want to use the " -"authentication internal only, choose the first option. If you're unsure, use " -"the \"Help me choose...\" link." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Mobile" msgstr "" -#: ../settings/security/third-party/microsoft.rst:58 -msgid "Redirect URI (optional):" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.mobile}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:56 -msgid "" -"Select web and provide your callback URL. The callback URL looks like this: " -"``https://zammad.domain.tld/auth/microsoft_office365/callback``" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``0049176123456789`` or empty if not set" +msgstr "``0049176123456789`` ou vide si non défini" + +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Note" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to register a Microsoft app" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.note}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "Within **API permissions** add the following permissions:" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Some note to this user`` or empty if not set" +msgstr "``Quelques notes à cet utilisateur` ou vide si non défini" + +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Phone" msgstr "" -#: ../settings/security/third-party/microsoft.rst:69 -msgid "``User.Read``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.phone}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "Contacts" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``004930123456789`` or empty if not set" +msgstr "``004930123456789`` ou vide si non défini" + +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > VIP" msgstr "" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "``Contacts.Read``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.vip}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:73 -msgid "" -"You can find these permissions within *Microsoft Graph → Delegated " -"permissions*." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Web" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to add required API permissions" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.web}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:80 -msgid "" -"Within **Certificates & secrets** create a new client secret. Note down the " -"returned secret **value** for later. **Do not** use the secret ID!" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``https://zammad.org`` or empty if not set" +msgstr "``https://zammad.org`` ou vide si non défini" + +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Department" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to create a new app secret" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.department}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:88 -msgid "" -"From **Overview** copy your apps *Application (client) ID*. If you're using " -"a single tenant app, please also copy *Directory (tenant) ID*. You now have " -"all required information for Zammad." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Email" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to retreive application client and tenant IDs" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.email}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:98 -msgid "Step 2 - Add App Credentials to Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Fax" msgstr "" -#: ../settings/security/third-party/microsoft.rst:100 -msgid "" -"Navigate to Security > Third-party Applications (Tab) within Zammad's admin " -"settings. Scroll down to the section *Authentication via Microsoft* and fill " -"in the required information." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.fax}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:105 -msgid "App ID:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Firstname" msgstr "" -#: ../settings/security/third-party/microsoft.rst:105 -msgid "This is your *Application (client) ID*." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.firstname}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:108 -msgid "App secret:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Lastname" msgstr "" -#: ../settings/security/third-party/microsoft.rst:108 -msgid "This is your *client secret* (value)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.lastname}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:113 -msgid "App Tenant ID:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Login" msgstr "" -#: ../settings/security/third-party/microsoft.rst:111 -msgid "" -"**optional** only required for apps that use account type *Accounts in this " -"organizational directory only (Default Directory only - Single tenant).*" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.login}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:115 -msgid "" -"Apply your settings by pressing submit and activate *Authentication via " -"Microsoft*." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Mobile" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "" -"Screencast showing how to add app credentials and activating the\n" -"authentication method" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.mobile}``" msgstr "" -#: ../settings/security/third-party/saml.rst:2 -msgid "SAML" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Note" msgstr "" -#: ../settings/security/third-party/saml.rst:4 -msgid "" -"Connect your SAML (Security Assertion Markup Language) identity provider as " -"a single sign-on (SSO) method." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.note}``" msgstr "" -#: ../settings/security/third-party/saml.rst:7 -msgid "" -"SAML is an open standard for SSO authentication (among other things). Sign-" -"ins are shared across multiple **service providers** and managed by a " -"central **identity provider** (IdP)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Domain based assignment" msgstr "" -#: ../settings/security/third-party/saml.rst:11 -msgid "" -"In this case, the service provider is Zammad, and the IdP is a software " -"service that you either host or subscribe to (*e.g.,* `Keycloak `_, `Redhat SSO Server `_, `ADFS `_, or `Okta `_)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.domain_assignment}``" msgstr "" -#: ../settings/security/third-party/saml.rst:18 -msgid "" -"This guide assumes you are already using SAML within your organization (i." -"e., that your IdP is fully set up)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Domain" msgstr "" -#: ../settings/security/third-party/saml.rst:21 -msgid "" -"Please note: Our instructions are based on connecting Zammad with Keycloak." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.domain}``" msgstr "" -#: ../settings/security/third-party/saml.rst:25 -msgid "Step 1: Configure Your IdP" +#: ../misc/variables/current-user.rst:1 +#, fuzzy +msgid "``zammad.com`` or empty if not set" +msgstr "``https://zammad.com`` ou vide si non défini" + +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Name" msgstr "" -#: ../settings/security/third-party/saml.rst:28 -msgid "Add Zammad as a Client/App" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.name}``" msgstr "" -#: ../settings/security/third-party/saml.rst:30 -msgid "" -"Import Zammad into your IdP using the XML configuration found at ``https://" -"your.zammad.domain/auth/saml/metadata``." -msgstr "" - -#: ../settings/security/third-party/saml.rst:33 -msgid "" -"If your IdP doesn't support XML import, you will have to configure Zammad as " -"a new client/app manually using the above XML metadata file for reference." -msgstr "" +#: ../misc/variables/current-user.rst:1 +#, fuzzy +msgid "``Zammad GmbH``" +msgstr "``Zammad GmbH`` ou vide si non défini" -#: ../settings/security/third-party/saml.rst:36 -msgid "For instance, when you see this tag:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Note" msgstr "" -#: ../settings/security/third-party/saml.rst:42 -msgid "" -"Set the **Assertion Consumer Service Binding URL** (sometimes also listed as " -"**Valid Redirect URIs**) to ``http://your.zammad.domain/auth/saml/callback``." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.note}``" msgstr "" -#: ../settings/security/third-party/saml.rst:47 -msgid "Set Up User Attribute Mapping" -msgstr "" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``A note to the organization of the user`` or empty if not set" +msgstr "``Une note à l'organisation de l'utilisateur` ou vide si non défini" -#: ../settings/security/third-party/saml.rst:49 -msgid "" -"Zammad requests the following user attributes (or “properties”) from the IdP:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Shared organization" msgstr "" -#: ../settings/security/third-party/saml.rst:51 -msgid "Email address (``email``)" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.shared}``" msgstr "" -#: ../settings/security/third-party/saml.rst:52 -msgid "Full name (``name``)" -msgstr "" +#: ../misc/variables/current-user.rst:1 +#, fuzzy +msgid "Current User > Organization > VIP" +msgstr "Billet > Organisation > Note" -#: ../settings/security/third-party/saml.rst:53 -msgid "Given name (``first_name``)" -msgstr "" +#: ../misc/variables/current-user.rst:1 +#, fuzzy +msgid "``#{user.organization.vip}``" +msgstr "``#{ticket.organization.domain}``" -#: ../settings/security/third-party/saml.rst:54 -msgid "Family name (``last_name``)" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Phone" msgstr "" -#: ../settings/security/third-party/saml.rst:56 -msgid "" -"You may need to set up “mappers” (or “mappings”) to tell your IdP how user " -"attributes in SAML correspond to those in Zammad. For a more detailed " -"breakdown, refer to the XML metadata file referenced in the previous section." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.phone}``" msgstr "" -#: ../settings/security/third-party/saml.rst:62 -msgid "Per-IdP Instructions" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated at" msgstr "" -#: ../settings/security/third-party/saml.rst:102 -msgid "Keycloak" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_at}``" msgstr "" -#: ../settings/security/third-party/saml.rst:65 -msgid "" -"**To add Zammad as a client,** save the XML configuration to disk (``https://" -"your.zammad.domain/auth/saml/metadata``) and use **Clients > Clients list > " -"Import client** in the Keycloak admin panel." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Address" msgstr "" -#: ../settings/security/third-party/saml.rst:70 -msgid "" -"To help Zammad **match its own user accounts to Keycloak users**, create a " -"user attribute (or “property”) mapper. In **Clients list**, click on your " -"newly created Client ID, choose the tab **Client scopes** and click on the " -"link which refers to your Zammad instance. Choose **Add mapper > By " -"configuration > User Property** and create a mapper with the following " -"entries:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.address}``" msgstr "" -#: ../settings/security/third-party/saml.rst:78 -msgid "**Name**" -msgstr "" +#: ../misc/variables/current-user.rst:1 +#, fuzzy +msgid "Current User > Updated by > Avatar" +msgstr "Billet > mis à jour par > Nom de famille" -#: ../settings/security/third-party/saml.rst:80 -msgid "**Mapper Type**" -msgstr "" +#: ../misc/variables/current-user.rst:1 +#, fuzzy +msgid "``#{user.updated_by.avatar(60,60)}``" +msgstr "``#{ticket.updated_by.lastname}``" -#: ../settings/security/third-party/saml.rst:81 -msgid "``User Property``" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Department" msgstr "" -#: ../settings/security/third-party/saml.rst:82 -msgid "**Property**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.department}``" msgstr "" -#: ../settings/security/third-party/saml.rst:83 -msgid "``emailAddress``" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Email" msgstr "" -#: ../settings/security/third-party/saml.rst:84 -msgid "**SAML Attribute Name**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.email}``" msgstr "" -#: ../settings/security/third-party/saml.rst:86 -msgid "**SAML Attribute NameFormat**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Fax" msgstr "" -#: ../settings/security/third-party/saml.rst:87 -msgid "``basic``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.fax}``" msgstr "" -#: ../settings/security/third-party/saml.rst:89 -msgid "" -"In the example above, we're telling Zammad that whenever it receives a SAML " -"login request, it should take the ``email`` property from Keycloak, look for " -"a Zammad user with the same ``email`` attribute, and create a new session " -"for that user." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Firstname" msgstr "" -#: ../settings/security/third-party/saml.rst:95 -msgid "" -"If your Keycloak users' email addresses are stored on another property (*e." -"g.,* ``username``), adjust accordingly." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.firstname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:98 -msgid "" -"Back in **Settings**, enter the Client ID (``https://your.zammad.domain/auth/" -"saml/metadata``) in the field **Master SAML Processing URL**." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Lastname" msgstr "" -#: ../settings/security/third-party/saml.rst:101 -msgid "You also need to enable **Sign assertions**." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.lastname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:105 -msgid "Step 2: Configure Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Login" msgstr "" -#: ../settings/security/third-party/saml.rst:107 -msgid "" -"Enable SAML and enter your IdP's details in the Admin Panel under **Settings " -"> Security > Third Party Applications > Authentication via SAML**:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.login}``" msgstr "" -#: ../settings/security/third-party/saml.rst:None -msgid "Example configuration of SAML part 1" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Mobile" msgstr "" -#: ../settings/security/third-party/saml.rst:119 -msgid "Display name" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.mobile}``" msgstr "" -#: ../settings/security/third-party/saml.rst:116 -msgid "" -"Allows you to define a custom button name for SAML. This helps your users to " -"understand better what the button on the login page does." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Note" msgstr "" -#: ../settings/security/third-party/saml.rst:119 -msgid "Defaults to ``SAML``." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.note}``" msgstr "" -#: ../settings/security/third-party/saml.rst:123 -msgid "IDP SSO target URL" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Phone" msgstr "" -#: ../settings/security/third-party/saml.rst:122 -msgid "" -"This is the target URL Zammad shall redirect to when the user presses the " -"SAML button. For Keycloak, this needs to look like https://your.domain/" -"realms/your-realm/protocol/saml" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.phone}``" msgstr "" -#: ../settings/security/third-party/saml.rst:127 -msgid "IDP single logout target URL" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > VIP" msgstr "" -#: ../settings/security/third-party/saml.rst:126 -msgid "" -"This is the URL to which the single logout request and response should be " -"sent." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.vip}``" msgstr "" -#: ../settings/security/third-party/saml.rst:131 -#, fuzzy -msgid "IDP certificate" -msgstr "Bloquer les notifications" - -#: ../settings/security/third-party/saml.rst:130 -msgid "" -"The public certificate of your IDP for Zammad to verify during the callback " -"phase." -msgstr "" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``false`` or ``true``" +msgstr "``false`` ou ``true``" -#: ../settings/security/third-party/saml.rst:145 -msgid "IDP certificate fingerprint" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Web" msgstr "" -#: ../settings/security/third-party/saml.rst:134 -msgid "" -"The fingerprint of your IDPs public certificate to verify during callback " -"phase." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.web}``" msgstr "" -#: ../settings/security/third-party/saml.rst:137 -msgid "🔏 **For the IdP certificate / certificate fingerprint:**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > VIP" msgstr "" -#: ../settings/security/third-party/saml.rst:139 -msgid "" -"Provide **only one or the other**—do not provide both! (Between the two, we " -"recommend the signing certificate itself: fingerprints use SHA-1, which `has " -"been broken for a while now `_.)" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.vip}``" msgstr "" -#: ../settings/security/third-party/saml.rst:144 -msgid "" -"**Keycloak users:** Find your certificate in the Keycloak admin panel under " -"**Realm Settings > Keys > Algorithm: RS256 > Certificate**." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Web" msgstr "" -#: ../settings/security/third-party/saml.rst:151 -msgid "Name identifier format" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.web}``" msgstr "" -#: ../settings/security/third-party/saml.rst:148 +#: ../misc/variables/ticket.rst:6 +#, fuzzy +#| msgid "" +#| "Below you can find all available ticket-based variables within Zammad. " +#| "These can be called via Triggers for example. If you're unsure if Zammad " +#| "does support variables at the point you're at, you can try to type ``::`` " +#| "to check." msgid "" -"This is the unique identifiers field type. Usually it should be ``urn:oasis:" -"names:tc:SAML:1.1:nameid-format:emailAddress``." +"Below you can find all available ticket-based variables within Zammad. These " +"can be called via triggers for example. If you're unsure if Zammad does " +"support variables at the point you're at, you can try to type ``::`` to " +"check." msgstr "" +"Vous trouverez ci-dessous toutes les variables, disponibles dans Zammad, " +"basées sur les billets. Par exemple, celles-ci peuvent être appelées via des " +"déclencheurs. Si vous ne savez pas si Zammad prend en charge une certaine " +"variable, vous pouvez essayer de taper ``::`` pour vérifier." -#: ../settings/security/third-party/saml.rst:151 -msgid "Zammad **expects an email address as unique identifier**!" -msgstr "" +#: ../misc/variables/ticket.rst:12 +msgid "Ticket Variables" +msgstr "Variables de billet" -#: ../settings/security/third-party/saml.rst:155 -#, fuzzy -msgid "UID attribute name" -msgstr "Attributs d'article" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Accounted Time" +msgstr "Billet > Temps comptabilisé" -#: ../settings/security/third-party/saml.rst:154 -msgid "" -"Here you can define an attribute that uniquely identifies the user. If " -"unset, the name identifier returned by the IDP is used." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.time_unit}``" +msgstr "``#{ticket.time_unit}``" -#: ../settings/security/third-party/saml.rst:None -msgid "Example configuration of SAML part 2" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``1``, ``2.75`` or empty response" +msgstr "``1``, ``2.75`` ou vide si non défini" -#: ../settings/security/third-party/saml.rst:163 -msgid "" -"Decide if the certificate for the connection to the IdP service has to be " -"verified or not (default: ``yes``)." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``3``, any number of articles existing in the ticket right now" +msgstr "``3``, nombre d'articles existant pour le billet en ce moment" -#: ../settings/security/third-party/saml.rst:169 -msgid "Signing & Encrypting" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Closing time" +msgstr "Ticket > Heure de fermeture à" -#: ../settings/security/third-party/saml.rst:169 -msgid "" -"Define if you want to sign, encrypt, do both or nothing for the requests." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.close_at}``" +msgstr "``#{ticket.close_at}``" -#: ../settings/security/third-party/saml.rst:179 -msgid "Certificate (PEM)" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "2019-10-07 17:25:00 UTC" +msgstr "2019-10-07 17:25:00 UTC" -#: ../settings/security/third-party/saml.rst:172 -msgid "" -"Paste the public certificate of your Zammad SAML client, if you want to " -"encrypt the requests." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created at" +msgstr "Billet créé à" -#: ../settings/security/third-party/saml.rst:175 -#, fuzzy -msgid "Make sure the certificate is:" -msgstr "Bloquer les notifications" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_at}``" +msgstr "``#{ticket.created_at}``" -#: ../settings/security/third-party/saml.rst:177 -msgid "already valid and not yet expired" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "2019-10-07 16:25:00 UTC" +msgstr "2019-10-07 16:25:00 UTC" -#: ../settings/security/third-party/saml.rst:178 -#, fuzzy -msgid "no CA certificate" -msgstr "Bloquer les notifications" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Address" +msgstr "Billet > Créé par > Adresse" -#: ../settings/security/third-party/saml.rst:179 -msgid "valid for signing and encrypting" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.address}``" +msgstr "``#{ticket.created_by.address}``" -#: ../settings/security/third-party/saml.rst:185 -msgid "Private key (PEM)" -msgstr "" +#: ../misc/variables/ticket.rst:1 +#, fuzzy +msgid "Ticket > Created by > Avatar" +msgstr "Billet > Créé par > Télécopieur" -#: ../settings/security/third-party/saml.rst:182 -msgid "" -"Paste the private key of your Zammad SAML client here, if you want to sign " -"the requests." -msgstr "" +#: ../misc/variables/ticket.rst:1 +#, fuzzy +msgid "``#{ticket.created_by.avatar(60,60)}``" +msgstr "``#{ticket.created_by.lastname}``" -#: ../settings/security/third-party/saml.rst:185 -msgid "Make sure the key is an RSA key with a length of at least 2048 bits." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Department" +msgstr "Billet > Créé par > Département" -#: ../settings/security/third-party/saml.rst:188 -msgid "Private key secret" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.department}``" +msgstr "``#{ticket.created_by.department}``" -#: ../settings/security/third-party/saml.rst:188 -msgid "If your private key is secured with a secret, you can provide it here." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Email" +msgstr "Billet > Créé par > Courriel" -#: ../settings/security/third-party/saml.rst:192 -msgid "Your callback URL" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.email}``" +msgstr "``#{ticket.created_by.email}``" -#: ../settings/security/third-party/saml.rst:191 -msgid "" -"This URL is needed for your IdP configuration so it knows where to redirect " -"to after successful authentication." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Fax" +msgstr "Billet > Créé par > Télécopieur" -#: ../settings/security/third-party/saml.rst:194 -msgid "" -"After saving your input by clicking on the \"Submit\" button, Zammad " -"verifies the provided keys/certificates (e.g. if they are valid for signing/" -"encrypting and if they aren't expired)." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.fax}``" +msgstr "``#{ticket.created_by.fax}``" -#: ../settings/security/third-party/saml.rst:199 -msgid "" -"See :ref:`automatic account linking ` for details " -"on how to link existing Zammad accounts to IdP accounts." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Firstname" +msgstr "Billet > Créé par > Prénom" -#: ../settings/security/third-party/saml.rst:205 -msgid "Automatic account linking doesn't work" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.firstname}``" +msgstr "``#{ticket.created_by.firstname}``" -#: ../settings/security/third-party/saml.rst:206 -msgid "" -"Have you double-checked your IdP's user attribute mapping configuration?" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Lastname" +msgstr "Billet > Créé par > Nom de famille" -#: ../settings/security/third-party/twitter.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via Twitter. To do " -"so, you need to follow these steps:" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.lastname}``" +msgstr "``#{ticket.created_by.lastname}``" -#: ../settings/security/third-party/twitter.rst:8 -msgid "Register Twitter App" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Login" +msgstr "Billet > Créé par > Login" -#: ../settings/security/third-party/twitter.rst:10 -msgid "Go to https://dev.twitter.com/apps and login with your account." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.login}``" +msgstr "``#{ticket.created_by.login}``" -#: ../settings/security/third-party/twitter.rst:15 -msgid "Click on \"Create App\"" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Mobile" +msgstr "Billet > Créé par > Mobile" -#: ../settings/security/third-party/twitter.rst:None -msgid "new app page" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.mobile}``" +msgstr "``#{ticket.created_by.mobile}``" -#: ../settings/security/third-party/twitter.rst:20 -msgid "" -"Enter app settings. As \"Callback URL\" you need to enter ``https://" -"zammad_host/api/v1/external_credentials/twitter/callback``. You need to " -"replace ``zammad_host`` with the domain of your Zammad system." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Note" +msgstr "Billet > Créé par > Note" -#: ../settings/security/third-party/twitter.rst:24 -msgid "" -"After the app has been created, update the application icon and organization " -"attributes." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.note}``" +msgstr "``#{ticket.created_by.note}``" -#: ../settings/security/third-party/twitter.rst:None -msgid "set permissions to receive and send direct messages" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Phone" +msgstr "Billet > Créé par > Téléphone" -#: ../settings/security/third-party/twitter.rst:30 -msgid "" -"Next we need to set ``read, write and access direct messages`` permissions " -"for the app." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.phone}``" +msgstr "``#{ticket.created_by.phone}``" -#: ../settings/security/third-party/twitter.rst:None -msgid "click on Keys & Access Token, note them" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > VIP" +msgstr "Billet > Créé par > VIP" -#: ../settings/security/third-party/twitter.rst:36 -msgid "" -"Go to \"Keys and Access Token\" tab and note the \"Consumer Key\" and " -"\"Consumer Secret\"." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.vip}``" +msgstr "``#{ticket.created_by.vip}``" -#: ../settings/security/third-party/twitter.rst:40 -msgid "Configure Zammad as Twitter App" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Web" +msgstr "Billet > Créé par le > Web" -#: ../settings/security/third-party/twitter.rst:42 -msgid "" -"Go to \"Admin > Security > Twitter > Third Party Applications > Twitter\" " -"Section." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.web}``" +msgstr "``#{ticket.created_by.web}``" -#: ../settings/security/third-party/twitter.rst:None -msgid "Admin > Security > Third Party Applications" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Address" +msgstr "Billet > Client > Adresse" -#: ../settings/security/third-party/twitter.rst:48 -msgid "" -"Fill in the \"Twitter Key\" and the \"Twitter Secret\" and click the " -"\"Submit\" button." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.address}``" +msgstr "``#{ticket.customer.address}``" -#: ../settings/security/third-party/twitter.rst:51 -msgid "" -"Now you can link accounts via \"Avatar > Profile > Link Accounts\" or login " -"via Zammad login page." -msgstr "" +#: ../misc/variables/ticket.rst:1 +#, fuzzy +msgid "Ticket > Customer > Avatar" +msgstr "Billet > Client > Télécopieur" -#: ../settings/security/two-factor.rst:11 -msgid "Two-factor Authentication Methods" -msgstr "" +#: ../misc/variables/ticket.rst:1 +#, fuzzy +msgid "``#{ticket.customer.avatar(60,60)}``" +msgstr "``#{ticket.customer.lastname}``" -#: ../settings/security/two-factor.rst:2 -msgid "Two-Factor Authentication" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Department" +msgstr "Billet > Client > Département" -#: ../settings/security/two-factor.rst:4 -msgid "" -"Two-factor authentication (2FA) enhances the security of Zammad accounts by " -"adding an extra layer of verification beyond a password. It requires users " -"to provide two different types of authentication factors, typically " -"something they know (like a password) and something they possess (like a " -"mobile device or a security token), to ensure that only authorized " -"individuals can access the account." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.department}``" +msgstr "``#{ticket.customer.department}``" -#: ../settings/security/two-factor.rst:19 -msgid "Enable Recovery Codes" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Email" +msgstr "Billet > Client > Courriel" -#: ../settings/security/two-factor.rst:21 -msgid "" -"Recovery codes are one-time use security codes that can be used by the user " -"if they lose access to their other two-factor authentication methods. They " -"cannot be used on their own, they can only be activated if at least one two-" -"factor authentication method is enabled." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.email}``" +msgstr "``#{ticket.customer.email}``" -#: ../settings/security/two-factor.rst:None -msgid "Enable Recovery Codes Setting" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Fax" +msgstr "Billet > Client > Télécopieur" -#: ../settings/security/two-factor.rst:30 -msgid "" -"Recovery codes can only be used as a backup method. If enabled, they will be " -"automatically generated for the user once they set up their initial two-" -"factor authentication method." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.fax}``" +msgstr "``#{ticket.customer.fax}``" -#: ../settings/security/two-factor.rst:34 -msgid "" -"The user will be asked to print out or save the generated recovery codes in " -"a safe place. Once used, a recovery code cannot be reused." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Firstname" +msgstr "Billet > Client > Prénom" -#: ../settings/security/two-factor.rst:37 -msgid "" -"Users will also have an option to regenerate their recovery codes at any " -"time, which invalidates already existing recovery codes and provides them " -"with a list of fresh codes." -msgstr "" - -#: ../settings/security/two-factor.rst:41 -msgid "" -"After you enable this setting, when the user completes a setup of their " -"initial two-factor authentication method, they will be presented with a list " -"of recovery codes and instructed to save them for later use." -msgstr "" - -#: ../settings/security/two-factor.rst:None -msgid "Recovery Codes Generation Modal Dialog" -msgstr "" - -#: ../settings/security/two-factor.rst:50 -msgid "Enforce the Set Up of the Two-Factor Authentication" -msgstr "" - -#: ../settings/security/two-factor.rst:52 -msgid "" -"In case you wish to require your users to set up at least one two-factor " -"authentication method for their account, you can do this by selecting " -"specific user roles the requirement applies to in **Enforced for user " -"roles** setting. Of course you must have at least one two-factor " -"authentication method enabled for this setting to take effect." -msgstr "" - -#: ../settings/security/two-factor.rst:None -msgid "Enforced for User Roles Setting" -msgstr "" - -#: ../settings/security/two-factor.rst:62 -msgid "" -"After you change this setting, if the user has one of the selected roles on " -"their account, they will be forced to set up the two-factor authentication " -"upon next sign in or application reload." -msgstr "" - -#: ../settings/security/two-factor.rst:66 -msgid "" -"A modal dialog with instructions will be shown, and they will not be able to " -"do any work before they set up at least one two-factor method." -msgstr "" - -#: ../settings/security/two-factor.rst:None -msgid "Modal Dialog for Enforcing Two-Factor Authentication Set Up" -msgstr "" - -#: ../settings/security/two-factor.rst:74 -msgid "Reset Two-Factor Authentication for a Specific User" -msgstr "" - -#: ../settings/security/two-factor.rst:76 -msgid "" -"In case an user isn't able to login anymore because of an inaccessible " -"second factor, you can reset the user's 2FA method." -msgstr "" - -#: ../settings/security/two-factor.rst:79 -msgid "" -"To do this, go to the user management and search for the relevant user. " -"After you found the account, click the button in the action column and " -"select \"Manage Two-Factor Authentication\":" -msgstr "" - -#: ../settings/security/two-factor.rst:None -msgid "Context menu in action column in user management" -msgstr "" - -#: ../settings/security/two-factor.rst:87 -msgid "" -"After selecting this, you can see a dialog where you can either reset one " -"2FA method or reset all of the user's 2FA methods:" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.firstname}``" +msgstr "``#{ticket.customer.firstname}``" -#: ../settings/security/two-factor.rst:None -msgid "Dialog for resetting user's 2FA method" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Lastname" +msgstr "Billet > Client > Nom de famille" -#: ../settings/security/two-factor.rst:94 -msgid "" -"Choose the fitting one, click on the corresponding \"Remove ...\" button and " -"confirm your action. The user now has to setup a new 2FA method, depending " -"on your 2FA configuration." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.lastname}``" +msgstr "``#{ticket.customer.lastname}``" -#: ../settings/security/two-factor/authenticator-app.rst:2 -msgid "Authenticator App" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Login" +msgstr "Billet > Client > Login" -#: ../settings/security/two-factor/authenticator-app.rst:4 -msgid "" -"The authenticator app method is a type of two-factor authentication that " -"uses a mobile application to generate one-time codes for account " -"verification. After setting up the authenticator app on their device, the " -"user links it to their Zammad account." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.login}``" +msgstr "``#{ticket.customer.login}``" -#: ../settings/security/two-factor/authenticator-app.rst:12 -msgid "" -"When logging in, the user is prompted to enter a time-sensitive code " -"generated by the app, in addition to their password. This code acts as the " -"second factor of authentication, providing an extra layer of security as it " -"changes periodically and is unique to the user's device." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Mobile" +msgstr "Billet > Client > Mobile" -#: ../settings/security/two-factor/authenticator-app.rst:None -msgid "Security Code in Google Authenticator App" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.mobile}``" +msgstr "``#{ticket.customer.mobile}``" -#: ../settings/security/two-factor/authenticator-app.rst:22 -msgid "" -"The app generates codes based on a shared secret key stored securely on both " -"the user's device and the server, ensuring a synchronized and secure " -"authentication process. The method of generating the codes is sometimes also " -"called TOTP (time-based one-time password)." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Note" +msgstr "Billet > Client > Note" -#: ../settings/security/two-factor/authenticator-app.rst:28 -msgid "Enabling the Authenticator App Method" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.note}``" +msgstr "``#{ticket.customer.note}``" -#: ../settings/security/two-factor/authenticator-app.rst:30 -#: ../settings/security/two-factor/security-keys.rst:28 -msgid "To enable the method, just toggle the switch on in the settings." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Phone" +msgstr "Billet > Client > Téléphone" -#: ../settings/security/two-factor/authenticator-app.rst:None -msgid "Authenticator App Switch in Settings" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.phone}``" +msgstr "``#{ticket.customer.phone}``" -#: ../settings/security/two-factor/authenticator-app.rst:36 -msgid "" -"Now the users will be able to set up this two-factor authentication method " -"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " -"Once they do, on next sign-in with password, they will be asked to provide " -"an additional security code generated by their mobile device." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > VIP" +msgstr "Billet > Client > VIP" -#: ../settings/security/two-factor/security-keys.rst:2 -msgid "Security Keys" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.vip}``" +msgstr "``#{ticket.customer.vip}``" -#: ../settings/security/two-factor/security-keys.rst:4 -msgid "" -"The security keys method is a type of a two-factor authentication that uses " -"Web Authentication API in the browser for verifying user's identity. The " -"user can register multiple hardware or software security keys with their " -"Zammad account and then they can use it during the sign-in process." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Web" +msgstr "Billet > Client > Web" -#: ../settings/security/two-factor/security-keys.rst:12 -msgid "" -"When logging in, the user is prompted to provide the same security key they " -"registered with their account, in addition to their password. This key acts " -"as the second factor of authentication, providing an extra layer of security." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.web}``" +msgstr "``#{ticket.customer.web}``" -#: ../settings/security/two-factor/security-keys.rst:None -msgid "Security Key dialog in Safari on macOS" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Escalation at" +msgstr "Billet > Escalade à" -#: ../settings/security/two-factor/security-keys.rst:21 -msgid "" -"The type of the key can range from hardware USB sticks to passkeys stored in " -"a device of user's choice. Which type can be used depends on the browser " -"flavor and the platform of the user." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.escalation_at}``" +msgstr "``#{ticket.escalation_at}``" -#: ../settings/security/two-factor/security-keys.rst:26 -msgid "Enabling the Security Keys Method" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable" +msgstr "``2019-10-07 16:25:00 UTC`` ou vide si non défini" -#: ../settings/security/two-factor/security-keys.rst:None -msgid "Security Keys Switch in Settings" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > First response" +msgstr "Billet > Première réponse" -#: ../settings/security/two-factor/security-keys.rst:34 -msgid "" -"Now the users will be able to set up this two-factor authentication method " -"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " -"Once they do, on next sign-in with password, they will be asked to provide " -"the same security key they registered during the setup." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.first_response_at}``" +msgstr "``#{ticket.first_response_at}``" -#: ../settings/system/system-selfhosted.include.rst:3 -msgid "" -"Below settings are only available to self hosted users. In hosted " -"environments we're handling these settings for you to ensure service " -"stability." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable yet" +msgstr "``2019-10-07 16:25:00 UTC`` ou vide si non encore applicable" -#: ../settings/system/base.rst:11 -msgid "Fully Qualified Domain Name" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Assign Follow-Ups" +msgstr "Ticket > Groupe > Attribuer des suivis" -#: ../settings/system/base.rst:7 -msgid "The URL of your Zammad installation." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_assignment}``" +msgstr "``#{ticket.group.follow_up_assignment}``" -#: ../settings/system/base.rst:9 ../settings/system/base.rst:17 -msgid "This setting is used within :doc:`/system/variables` and notifications." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Assignment Timeout" +msgstr "Ticket > Groupe > Délai d'attente d'affectation" -#: ../settings/system/system-base.include.rst:1 -msgid "It is automatically set by the *Getting Started wizard*." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.assignment_timeout}``" +msgstr "``#{ticket.group.assignment_timeout}``" -#: ../settings/system/system-base.include.rst:5 -msgid "Changing this setting also changes callback URLs for your channels etc." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``20`` or empty if not configured" +msgstr "``20`` ou vide si non défini" -#: ../settings/system/system-base.include.rst:6 -msgid "This setting can have negative affects on being able to login." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Follow-up possible" +msgstr "Billet > Groupe > Suivi possible" -#: ../settings/system/base.rst:19 -msgid "HTTP type" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_possible}``" +msgstr "``#{ticket.group.follow_up_possible}``" -#: ../settings/system/base.rst:14 -msgid "" -"The HTTP type tells your installation how your clients connect. This is " -"relevant for authentication and cookie security." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``no`` or ``yes``" +msgstr "``no`` ou ``yes``" -#: ../settings/system/base.rst:31 -msgid "SystemID" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Name" +msgstr "Billet > Groupe > Name" -#: ../settings/system/base.rst:22 -msgid "" -"This ID is being used within your ticket number. In case you're " -"communicating with another ticket system with similar ticket number schemes " -"this ID greatly reduces the risk of false follow ups." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.name}``" +msgstr "``#{ticket.group.name}``" -#: ../settings/system/base.rst:26 -msgid "" -"The SystemID is randomly selected upon installation of Zammad (``1-99``)." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``Sales``" +msgstr "``Ventes``" -#: ../settings/system/base.rst:30 -msgid "" -"**Do not** change this setting in a productive system! Your Zammad " -"installation may no longer recognize old ticket number based follow ups upon " -"change!" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Note" +msgstr "Billet > Groupe > Note" -#: ../settings/system/frontend.rst:2 -msgid "Frontend" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.note}``" +msgstr "``#{ticket.group.note}``" -#: ../settings/system/frontend.rst:22 -msgid "Core Workflow Ajax Mode" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``Note about this group``" +msgstr "``Note à propos de ce groupe``" -#: ../settings/system/frontend.rst:6 -msgid "" -"This setting allows administrators to enforce :doc:`/system/core-workflows` " -"to use Ajax-Calls instead of web sockets. You'll usually only need this if " -"you experience serious issues as noted below." -msgstr "" +#: ../misc/variables/ticket.rst:1 +#, fuzzy +msgid "Ticket > ID" +msgstr "Billet > #:" -#: ../settings/system/frontend.rst:10 -msgid "**🤓 Possible (technical) reasons**" -msgstr "" +#: ../misc/variables/ticket.rst:1 +#, fuzzy +msgid "``#{ticket.id}``" +msgstr "``#{ticket.title}``" -#: ../settings/system/frontend.rst:12 -msgid "" -"In some cases, your network structure (e.g. firewalls, proxies) may " -"disconnect long web socket connections. This leads to select fields staying " -"empty (e.g. owner selection *after* selecting your group) or fields not " -"shown / hidden (e.g. when switching to or from pending states, the \"pending " -"till\" field not showing / hiding)." -msgstr "" +#: ../misc/variables/ticket.rst:1 +#, fuzzy +msgid "``17``, ``5281``, ..." +msgstr "``new``, ``open``, ..." -#: ../settings/system/frontend.rst:18 -msgid "" -"Please keep in mind that the Ajax fallback may cause serious pressure on " -"your application server. If you have the choice stick to web sockets." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact (agent)" +msgstr "Billet > Dernier contact (Agent)" -#: ../settings/system/frontend.rst:22 -msgid "Default: ``no`` (inactive)" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_agent_at}``" +msgstr "``#{ticket.last_contact_agent_at}``" -#: ../settings/system/frontend.rst:53 -msgid "Show calendar weeks in the picker of date/datetime fields" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact (customer)" +msgstr "Billet > Dernier contact (client)" -#: ../settings/system/frontend.rst:25 -msgid "" -"With this setting you can instruct Zammad to provide week number display " -"globally for all users. Calendar with week number display are usually used " -"in business sectors and may not be relevant for everyone." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_customer_at}``" +msgstr "``#{ticket.last_contact_customer_at}``" -#: ../settings/system/frontend.rst:29 +#: ../misc/variables/ticket.rst:1 +#, fuzzy msgid "" -"This setting affects *all areas* - you'll also see week numbers in the admin " -"panel for e.g. triggers and macros." -msgstr "" - -#: ../settings/system/frontend.rst:32 -msgid "Default: ``no`` (not shown)" +"``2019-10-07 16:25:00 UTC`` or empty if not applicable yet (Please note " +"`Ticket last contact behavior Settings `_ for this)" msgstr "" +"``2019-10-07 16:25:00 UTC`` ou vide si ne s'applique pas encore (veuillez " +"noter ``Paramètres: comportement du dernier contact du billet ``_ pour cela)" -#: ../settings/system/frontend.rst:53 -msgid "Here's the difference:" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact" +msgstr "Billet > Dernier contact" -#: ../settings/system/frontend.rst:0 -msgid "Screenshot showing Zammad's date picker (in the default way)" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_at}``" +msgstr "``#{ticket.last_contact_at}``" -#: ../settings/system/frontend.rst:41 +#: ../misc/variables/ticket.rst:1 #, fuzzy -msgid "Set to ``no``" -msgstr "Option réglée sur ``no``" +msgid "Ticket > Number" +msgstr "Billet > #:" -#: ../settings/system/frontend.rst:0 -msgid "" -"Screenshot showing Zammad's date picker with\n" -"week numbers enabled" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.number}``" +msgstr "``#{ticket.number}``" -#: ../settings/system/frontend.rst:50 -#, fuzzy -msgid "Set to ``yes``" -msgstr "Option réglée sur ``yes``" +#: ../misc/variables/ticket.rst:1 +msgid "``31001``, ``201910731001``, ..." +msgstr "``31001``, ``201910731001``, ..." -#: ../settings/system/index.rst:4 -msgid "" -"For your overview we split each tab within system settings into its own page:" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain based assignment" +msgstr "Billet > Organisation > Affectation basée sur un domaine" -#: ../settings/system/index.rst:16 -#, fuzzy -msgid "Console Based Settings" -msgstr "Réglages avancés" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain_assignment}``" +msgstr "``#{ticket.organization.domain_assignment}``" -#: ../settings/system/index.rst:18 -msgid "" -"There's some console based settings we didn't put into the UI. However, you " -"may find them helpful - you can find them in our :docs:`hidden settings ` section." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain" +msgstr "Billet > Organisation > Domaine" -#: ../settings/system/network.rst:2 -msgid "Network" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain}``" +msgstr "``#{ticket.organization.domain}``" -#: ../settings/system/network.rst:8 -msgid "" -"The proxy settings can only be saved after successfully testing the proxy " -"connection." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``domain.tld`` or empty if not set" +msgstr "``domaine.tld`` ou vide si non défini" -#: ../settings/system/network.rst:15 -msgid "Proxy Address." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Name" +msgstr "Billet > Organisation > Nom" -#: ../settings/system/network.rst:12 -msgid "" -"Allows you to provide a proxy server if needed. This is relevant for network " -"communication by Zammad." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.name}``" +msgstr "``#{ticket.organization.name}``" -#: ../settings/system/network.rst:15 -msgid "It **does not** affect the update process or Elasticsearch." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``Zammad GmbH`` or empty if not set" +msgstr "``Zammad GmbH`` ou vide si non défini" -#: ../settings/system/network.rst:18 -msgid "Username for proxy connection." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Note" +msgstr "Billet > Organisation > Note" -#: ../settings/system/network.rst:18 -msgid "" -"If your proxy server requires authentication, provide the username here." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.note}``" +msgstr "``#{ticket.organization.note}``" + +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Shared organization" +msgstr "Billet > Prganisation > Organisation partagée" -#: ../settings/system/network.rst:21 -msgid "Password for proxy connection." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.shared}``" +msgstr "``#{ticket.organization.shared}``" -#: ../settings/system/network.rst:21 -msgid "" -"If your proxy server requires authentication, provide the password here." -msgstr "" +#: ../misc/variables/ticket.rst:1 +#, fuzzy +msgid "Ticket > Organization > VIP" +msgstr "Billet > Organisation > Note" -#: ../settings/system/network.rst:26 -msgid "No proxy for the following hosts." -msgstr "" +#: ../misc/variables/ticket.rst:1 +#, fuzzy +msgid "``#{ticket.organization.vip}``" +msgstr "``#{ticket.organization.domain}``" -#: ../settings/system/network.rst:24 -msgid "" -"Exception list for hosts you can't or don't want to reach via proxy server." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Address" +msgstr "Billet > Propriétaire > Adresse" -#: ../settings/system/network.rst:27 -msgid "Default: ``localhost,127.0.0.0,::1``" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.address}``" +msgstr "``#{ticket.owner.address}``" -#: ../settings/system/services.rst:2 -msgid "Services" -msgstr "" +#: ../misc/variables/ticket.rst:1 +#, fuzzy +msgid "Ticket > Owner > Avatar" +msgstr "Billet > Propriétaire > Télécopieur" -#: ../settings/system/services.rst:10 -msgid "Image Service" -msgstr "" +#: ../misc/variables/ticket.rst:1 +#, fuzzy +msgid "``#{ticket.owner.avatar(60,60)}``" +msgstr "``#{ticket.owner.lastname}``" -#: ../settings/system/services.rst:5 -msgid "Defines the backend for user and organization image lookups." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Department" +msgstr "Billet > Propriétaire > Département" -#: ../settings/system/services.rst:7 -msgid "Default: ``Zammad Image Service`` (active)" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.department}``" +msgstr "``#{ticket.owner.department}``" -#: ../settings/system/services.rst:9 -msgid "" -"Make sure your on premise installation has ``HTTPS`` access to ``images." -"zammad.com``." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``Support`` or empty if not set" +msgstr "``Assistance`` ou vide si non défini" -#: ../settings/system/services.rst:18 -msgid "Geo Calendar Service" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Email" +msgstr "Billet > Propriétaire > Courriel" -#: ../settings/system/services.rst:13 -msgid "" -"Defines the backend for geo calendar lookups. Used for initial calendar " -"setup." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.email}``" +msgstr "``#{ticket.owner.email}``" -#: ../settings/system/services.rst:16 -msgid "Default: ``Zammad GeoCalendar Service`` (active)" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``agent@company.tld`` or empty if not set" +msgstr "``agent@company.tld`` ou vide si non défini" -#: ../settings/system/services.include.rst:2 -msgid "" -"Make sure your on premise installation has ``HTTPS`` access to ``geo.zammad." -"com``." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Fax" +msgstr "Billet > Propriétaire > Télécopieur" -#: ../settings/system/services.rst:26 -msgid "Geo IP Service" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.fax}``" +msgstr "``#{ticket.owner.fax}``" -#: ../settings/system/services.rst:21 -msgid "" -"Defines the backend for geo IP lookups. Shows also location of an IP address " -"if an IP address is shown." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Firstname" +msgstr "Billet > Propriétaire > Prénom" -#: ../settings/system/services.rst:24 -msgid "Default: ``Zammad GeoIP Service`` (active)" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.firstname}``" +msgstr "``#{ticket.owner.firstname}``" -#: ../settings/system/services.rst:32 -msgid "Geo Location Service" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``Max`` or empty if not set" +msgstr "``Max`` ou vide si non défini" -#: ../settings/system/services.rst:29 -msgid "" -"Defines the backend for geo location lookups to store geo locations for " -"addresses." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Lastname" +msgstr "Billet > Propriétaire > Nom de famille" -#: ../settings/system/services.rst:32 -msgid "" -"Default: ``OpenStreetMap (ODbL 1.0, http://osm.org/copyright)`` (active)" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.lastname}``" +msgstr "``#{ticket.owner.lastname}``" -#: ../settings/system/services.rst:36 -msgid "" -"You can find a detailed privacy information on what we store for how long on " -"our :docs:`Privacy Appendix ` inside of our System " -"Documentation." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``Mustermann`` or empty if not set" +msgstr "``Mustermann`` ou vide si non défini" -#: ../settings/system/storage.rst:2 -msgid "Storage" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Login" +msgstr "Billet > Propriétaire > Login" -#: ../settings/system/storage.rst:6 -msgid "" -"Here you can define where Zammad stores attachments for tickets and the " -"knowledge base. By default, we're writing to the ``Database`` - you can " -"switch to ``Filesystem`` or ``Simple Storage (S3)`` at any time. In this " -"case please have a look on the following instructions." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.login}``" +msgstr "``#{ticket.owner.login}``" -#: ../settings/system/storage.rst:11 -msgid "" -"If you have a busy Zammad instance, we strongly encourage you to use " -"filesystem storage instead of \"Database\". This will greatly improve system " -"performance (de-crease database load and size)." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``agent``" +msgstr "``Agent``" -#: ../settings/system/storage.rst:19 -msgid "Database" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Mobile" +msgstr "Billet > Propriétaire > Mobile" -#: ../settings/system/storage.rst:17 -msgid "" -"This is the default storage method. The attachments are stored directly in " -"the database. If your Zammad instance grows, we recommend one of the other " -"methods to maintain performance." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.mobile}``" +msgstr "``#{ticket.owner.mobile}``" -#: ../settings/system/storage.rst:38 -msgid "Filesystem" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Note" +msgstr "Billet > Propriétaire > Note" -#: ../settings/system/storage.rst:22 -msgid "" -"This storage method is recommended for all Zammad instances, especially for " -"those with a higher load. If you choose filesystem, your files are written " -"to ``/opt/zammad/storage/``." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.note}``" +msgstr "``#{ticket.owner.note}``" -#: ../settings/system/storage.rst:26 -msgid "" -"Moving attachments from \"Database\" to \"Filesystem\" can be run during " -"production use. However, you should consider your framework conditions (e.g. " -"bandwidth, system load in production) to define the right moment." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Phone" +msgstr "Billet > Propriétaire > Téléphone" -#: ../settings/system/storage.rst:32 -msgid "**You noticed slow updates of Zammad?**" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.phone}``" +msgstr "``#{ticket.owner.phone}``" -#: ../settings/system/storage.rst:34 -msgid "" -"While Zammad is beeing updated, it enforces a recursive \"change " -"owner\" (chown) for this directory. For instances with many files this can " -"be time consuming. To mitigate that you can move your files and create a " -"symlink in ``/opt/zammad/storage/`` to the new directory. Of course you have " -"to make sure on your own that the permissions are always correct." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > VIP" +msgstr "Billet > Propriétaire > VIP" -#: ../settings/system/storage.rst:95 -msgid "Simple Storage (S3)" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.vip}``" +msgstr "``#{ticket.owner.vip}``" -#: ../settings/system/storage.rst:41 -msgid "" -"To use the Simple Storage (S3), you have to provide some settings, which " -"can't be accessed in the UI (see instructions below)." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Web" +msgstr "Billet > Propriétaire > Web" -#: ../settings/system/storage.rst:44 -msgid "" -"⚠️ Please note that the current implementation is in its early stages and can " -"be modified in the future." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.web}``" +msgstr "``#{ticket.owner.web}``" -#: ../settings/system/storage.rst:47 -msgid "" -"The prerequisite is to have access to a S3-compatible storage and to have " -"all necessary parameters available (which depends on your storage provider; " -"if in doubt, please ask there for help)." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``https://zammad.com`` or empty if not set" +msgstr "``https://zammad.com`` ou vide si non défini" -#: ../settings/system/storage.rst:51 -msgid "Steps to configure S3:" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Pending till" +msgstr "Billet > En attente jusqu'à" -#: ../settings/system/storage.rst:53 -msgid "" -"Copy ``config/zammad/storage.yml.dist`` to ``config/zammad/storage.yml``" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.pending_time}``" +msgstr "``#{ticket.pending_time}``" -#: ../settings/system/storage.rst:54 -msgid "Edit the copied file in one of the following ways:" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not set" +msgstr "``2019-10-07 16:25:00 UTC`` ou vide si non défini" -#: ../settings/system/storage.rst:56 -msgid "" -"Either provide your S3 configuration with one attribute per line like in the " -"upper area of the file" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Priority > Name" +msgstr "Billet > Priorité > Nom" -#: ../settings/system/storage.rst:58 -msgid "" -"Or provide your S3 configuration as an URL (which you can find at the end of " -"the file). Note: you can also provide this URL as environment variable (:" -"docs:`see system documentation `) without using this yml-file." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.priority.name}``" +msgstr "``#{ticket.priority.name}``" -#: ../settings/system/storage.rst:62 -msgid "" -"We recommend the deletion of the not used configuration style to avoid " -"inconsistencies." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``2 normal``" +msgstr "``2 normal``" -#: ../settings/system/storage.rst:65 -msgid "Restart Zammad so the config file / environment variable is loaded" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > State > Name" +msgstr "Billet > État > Nom" -#: ../settings/system/storage.rst:66 -msgid "" -"Set the \"Storage Method\" in Zammad to ``Simple Storage (S3)`` in Settings " -"> System > Storage and click on \"Submit\". After that, Zammad checks your " -"configuration and the connection to the service and will raise an error " -"message if something is wrong." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.state.name}``" +msgstr "``#{ticket.state.name}``" -#: ../settings/system/storage.rst:72 -msgid "A very simple storage configuration could look like this:" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``new``, ``open``, ..." +msgstr "``new``, ``open``, ..." -#: ../settings/system/storage.rst:85 -msgid "" -"Before setting the storage method to ``Simple Storage (S3)`` (step 4), " -"please make sure to have a working setup." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Tags" +msgstr "Billet > Étiquettes" -#: ../settings/system/storage.rst:88 -msgid "" -"You can verify this by running ``rails r 'Rails.logger = Logger.new(STDOUT); " -"pp Store::Provider::S3.ping?'`` in your Zammad directory. If everything is " -"fine, you should see ``true``, else you should see ``false`` and a simple " -"error message." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.tags}``" +msgstr "``#{ticket.tags}``" -#: ../settings/system/storage.rst:93 +#: ../misc/variables/ticket.rst:1 msgid "" -"If you installed Zammad through a package manager (rather than from source), " -"replace ``rails r`` with ``zammad run rails r`` above. To learn more, see :" -"docs:`Administration via Console `." +"Currently not available, see `Issue 2769 `_" msgstr "" +"Actuellement non disponible, voir `Issue 2769 `_" -#: ../settings/ticket.rst:4 -#, fuzzy +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Title" +msgstr "Billet > Titre" + +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.title}``" +msgstr "``#{ticket.title}``" + +#: ../misc/variables/ticket.rst:1 msgid "" -"Here you can adjust general ticket settings. Additional ones for the ticket " -"composer interface can be found in the :doc:`/misc/composer`." +"``My amazing Subject`` (normally subject, can be edited within Interface and " +"thus differ)" msgstr "" -"Des paramètres supplémentaires pour l'interface du compositeur de billets " -"peuvent être trouvés dans :doc:`/misc/composer`." +"``Mon incroyable sujet`` (normalement le sujet peut être modifié dans " +"l'interface et donc être différent)" -#: ../settings/ticket.rst:11 -msgid "Ticket Hook (default: ``Ticket#``)" -msgstr "Crochet d'intégration du billet (default: ``Ticket#``)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated at" +msgstr "Billet > mis à jour à:" -#: ../settings/ticket.rst:11 -msgid "The identifier for a ticket; *e.g.,* Ticket#, Call#, MyTicket#." -msgstr "L'identifiant d'un billet; *par exemple:* Ticket#, Call#, MyTicket#." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_at}``" +msgstr "``#{ticket.updated_at}``" -#: ../settings/ticket.rst:38 -msgid "Ticket Hook Position (default: ``right``)" -msgstr "Position du crochet d'intégration du billet (default: ``right``)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Address" +msgstr "Billet > mis à jour par > Adresse" -#: ../settings/ticket.rst:14 -msgid "" -"With this setting you can decide (if) where to insert the ticket number." -msgstr "" -"Avec ce paramètre, vous pouvez décider (si) où insérer le numéro de billet." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.address}``" +msgstr "``#{ticket.updated_by.address}``" -#: ../settings/ticket.rst:20 -msgid "*Right*" -msgstr "*Droit*" +#: ../misc/variables/ticket.rst:1 +#, fuzzy +msgid "Ticket > Updated by > Avatar" +msgstr "Billet > mis à jour par > Télécopieur" -#: ../settings/ticket.rst:17 -msgid "" -"This setting will add the ticket reference on the right site of the subject." -msgstr "Ce paramètre ajoutera la référence du billet à la droite du sujet." +#: ../misc/variables/ticket.rst:1 +#, fuzzy +msgid "``#{ticket.updated_by.avatar(60,60)}``" +msgstr "``#{ticket.updated_by.lastname}``" -#: ../settings/ticket.rst:20 -msgid "Example: ``Some Subject [Ticket#12345]``" -msgstr "Exemple: ``Votre billet [Ticket #: 12345]``" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Department" +msgstr "Billet > mis à jour par > Département" -#: ../settings/ticket.rst:26 -msgid "*Left*" -msgstr "*Gauche*" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.department}``" +msgstr "``#{ticket.updated_by.department}``" -#: ../settings/ticket.rst:23 -msgid "" -"This setting will add the ticket reference on the left site of the subject." -msgstr "Ce paramètre ajoutera la référence du billet à la gauche du sujet." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Email" +msgstr "Billet > mis à jour par > Courriel" -#: ../settings/ticket.rst:26 -msgid "Example: ``[Ticket#12345] Some Subject``" -msgstr "Exemple: ``[Ticket #: 12345] Votre billet``" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.email}``" +msgstr "``#{ticket.updated_by.email}``" -#: ../settings/ticket.rst:29 -msgid "*None*" -msgstr "*Aucun*" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Fax" +msgstr "Billet > mis à jour par > Télécopieur" -#: ../settings/ticket.rst:29 -msgid "This will completely remove ticket references from the subject." -msgstr "Ceci supprimera complètement les références du billet du sujet." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.fax}``" +msgstr "``#{ticket.updated_by.fax}``" -#: ../settings/ticket.rst:33 -msgid "" -"Please ensure to take a look at :doc:`/channels/email/settings` within the " -"email channel to ensure you have at least one reference that helps Zammad to " -"assign follow-ups correctly." -msgstr "" -"Veuillez vous assurer de consulter :doc:`/channels/email/settings` dans le " -"canal de messagerie pour vous assurer d'avoir au moins une référence qui " -"aide Zammad à affecter correctement les suivis." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Firstname" +msgstr "Billet > mis à jour par > Prénom" -#: ../settings/ticket.rst:37 -msgid "" -"Disabling this and not setting up any further follow up search will lead to " -"unexpected results!" -msgstr "" -"Désactiver ceci et ne pas configurer de recherche de suivi supplémentaire " -"entraînera des résultats inattendus!" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.firstname}``" +msgstr "``#{ticket.updated_by.firstname}``" -#: ../settings/ticket.rst:65 -#, fuzzy -msgid "" -"Ticket Last Contact Behaviour (default: ``Use the start time of the last " -"customer thread (which may consist of multiple articles).``)" -msgstr "" -"Comportement du dernier contact du billet (par défaut: ``Dernier contact " -"client (avec la considération qu'un agent y ait répondu)``)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Lastname" +msgstr "Billet > mis à jour par > Nom de famille" -#: ../settings/ticket.rst:41 -msgid "" -"This setting changes the way Zammad updates the ``Last Contact`` value of a " -"ticket. This is fairly important for overviews and what you expect upon " -"ticket updates of a customer." -msgstr "" -"Ce paramètre modifie la façon dont Zammad met à jour la valeur ``Dernier " -"contact`` d'un billet. Ceci est assez important pour les aperçus et ce que " -"vous attendez des mises à jour des billets d'un client." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.lastname}``" +msgstr "``#{ticket.updated_by.lastname}``" -#: ../settings/ticket.rst:52 -msgid "" -"Use the start time of the last customer thread (which may consist of " -"multiple articles)." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Login" +msgstr "Billet > mis à jour par > Login" -#: ../settings/ticket.rst:46 -msgid "" -"If this option is chosen, Zammad will update the last updated value just " -"once if a customer replies. After that, Zammad will wait for an agent to " -"react." -msgstr "" -"Si cette option est choisie, Zammad mettra à jour la dernière valeur mise à " -"jour une seule fois, si un client répond. Ensuite, Zammad attendra qu'un " -"agent réagisse." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.login}``" +msgstr "``#{ticket.updated_by.login}``" -#: ../settings/ticket.rst:50 -#, fuzzy -msgid "" -"This comes in handy if you want to work tickets in the order of their first " -"update. This will not change ticket orders if customers decide to \"bump\" " -"the ticket affected." -msgstr "" -"Ceci est pratique si vous souhaitez travailler sur les billets dans l'ordre " -"de leur première mise à jour. Cela ne changera pas l'ordre des billets si " -"les clients décident de \"bumper\" le billet concerné." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Mobile" +msgstr "Billet > mis à jour par > Mobile" -#: ../settings/ticket.rst:57 -msgid "Use the time of the very last customer article." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.mobile}``" +msgstr "``#{ticket.updated_by.mobile}``" -#: ../settings/ticket.rst:55 -msgid "" -"When setting this option, Zammad will always update the last updated value. " -"This means that if ordering by ``Last Update``, ticket orders will change if " -"customers \"bump\" the ticket." -msgstr "" -"Lors de la définition de cette option, Zammad mettra toujours à jour la " -"dernière valeur mise à jour. Cela signifie que si vous ordonnancez par " -"``Dernière mise à jour``, l'ordre des billets changera si les clients " -"\"bumpent\" le billet." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Note" +msgstr "Billet > mis à jour par > Note" -#: ../settings/ticket.rst:64 -msgid "Last contact value used on :doc:`/manage/overviews`" -msgstr "Dernière valeur de contact utilisée à :doc:`/manage/overviews`" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.note}``" +msgstr "``#{ticket.updated_by.note}``" -#: ../settings/ticket.rst:65 -msgid "Last contact value used on :doc:`/manage/trigger`" -msgstr "Dernière valeur de contact utilisée à :doc:`/manage/trigger`" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Phone" +msgstr "Billet > mis à jour par > Téléphone" -#: ../settings/ticket.rst:88 -msgid "" -"Ticket Organization Reassignment (default: ``Update the most recent tickets." -"``)" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.phone}``" +msgstr "``#{ticket.updated_by.phone}``" -#: ../settings/ticket.rst:68 -msgid "" -"This setting changes the way Zammad updates the organization field of the " -"tickets whenever the primary organization of a user is changed." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > VIP" +msgstr "Billet > mis à jour par > VIP" -#: ../settings/ticket.rst:74 -msgid "Update the most recent tickets." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.vip}``" +msgstr "``#{ticket.updated_by.vip}``" -#: ../settings/ticket.rst:72 -msgid "" -"If this option is chosen, Zammad will update the 100 most recent tickets " -"where the user is the ticket customer. The ticket organization field will be " -"automatically set to the new primary organization of the user." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Web" +msgstr "Billet > mis à jour par > Web" -#: ../settings/ticket.rst:88 -msgid "Do not update any tickets." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.web}``" +msgstr "``#{ticket.updated_by.web}``" + +#: ../settings/branding.rst:10 +msgid "Product Name" msgstr "" -#: ../settings/ticket.rst:77 +#: ../settings/branding.rst:7 msgid "" -"When choosing this option, Zammad will not update any tickets when the " -"user's primary organization is changed." +"Defines the name of the application, shown in the web interface, tabs and " +"title bar of the web browser." msgstr "" -#: ../settings/ticket.rst:80 -msgid "**Use with care!**" +#: ../settings/branding.rst:10 +msgid "Default value: ``Zammad Helpdesk``" msgstr "" -#: ../settings/ticket.rst:82 -msgid "" -"Using this option may lead to inconsistencies in the system as the ticket " -"organization may become decoupled from the ticket customer." +#: ../settings/branding.rst:13 +msgid "Will be shown in the app and is included in email footers." msgstr "" -#: ../settings/ticket.rst:85 -msgid "" -"However, you may use this option if you wish to maintain :ref:`the shared " -"access ` to the ticket for all organization " -"members of the original organization of the customer." +#: ../settings/branding.rst:19 +msgid "Logo" msgstr "" -#: ../settings/ticket.rst:110 -msgid "Ticket Number Format (default: ``Increment (SystemID.Counter)``)" +#: ../settings/branding.rst:16 +msgid "Defines the logo of the application, shown in the login page of Zammad." msgstr "" -"Format du numéro de billet (par défaut: ``Increment (SystemID.Counter)``)" -#: ../settings/ticket.rst:94 -#, fuzzy +#: ../settings/branding.rst:18 msgid "" -"This setting defines the way Zammad's ticket number will look. Changing this " -"setting in production will cause follow up detection to fail." +"Ensure to hit the \"Submit\" button after uploading the logo. Otherwise your " +"change will not be saved." msgstr "" -"Ce paramètre définit l'apparence du numéro de billet de Zammad. La " -"modification de ce paramètre en production entraînera l'échec de la " -"détection de suivi." - -#: ../settings/ticket.rst:102 -msgid "Increment (SystemID.Counter)" -msgstr "Incrémentation (SystemID.Counter)" -#: ../settings/ticket.rst:98 +#: ../settings/branding.rst:22 msgid "" -"The increment value contains the SystemID (automatically generated during " -"installation) and a increment which counts up with every new Ticket. The " -"increment will automatically get another digit if needed." +"Allows to set the default language of the Zammad instance. The here defined " +"locale mostly acts as a fallback for:" msgstr "" -"La valeur d'incrémentation contient le \"SystemID\" (généré automatiquement " -"lors de l'installation) et un incrément qui est ajouté à chaque nouveau " -"billet. Le résultat obtiendra automatiquement un chiffre significateur " -"suppémentaire si nécessaire." - -#: ../settings/ticket.rst:102 -msgid "Examples: ``1010138``, ``1010139``" -msgstr "Exemples: ``1010138``, ``1010139``" - -#: ../settings/ticket.rst:110 -msgid "Date (Year.Month.Day.SystemID.Counter)" -msgstr "Date (Année.Mois.Jour.SystemID.Counter)" -#: ../settings/ticket.rst:105 -msgid "" -"This version of the ticket number is fairly long. However, because it " -"contains the date of ticket creation, it also allows you to see when the " -"ticket has been created. You may feel familiar with this number format if " -"you've worked with OTRS already." +#: ../settings/branding.rst:25 +msgid "user preferences (if Zammad can't detect the users locale)" msgstr "" -"Cette version du numéro de billet est assez longue. Cependant, parce qu'il " -"contient la date de création du billet, il vous permet également de voir " -"quand le billet a été créé. Vous pouvez vous sentir familier avec ce format " -"de nombre si vous avez déjà travaillé avec OTRS." -#: ../settings/ticket.rst:110 -msgid "Examples: ``201206231010138``, ``201206231010139``" -msgstr "Exemples: ``201206231010138``, ``201206231010139``" +#: ../settings/branding.rst:26 +msgid "CSV output (reporting, time accounting)" +msgstr "" -#: ../settings/ticket.rst:137 -msgid "OPTIONS" -msgstr "OPTIONS" +#: ../settings/branding.rst:30 +msgid "Define the timezone of your Zammad installation." +msgstr "" -#: ../settings/ticket.rst:113 +#: ../settings/branding.rst:32 msgid "" -"The below options allow you to further customize your ticket number. The " -"availability of options differ depending of the chosen ticket number format " -"above." +"This does not have any effect on timings for your agents or how Zammad " +"stores date and time values." msgstr "" -"Les options ci-dessous vous permettent de personnaliser davantage votre " -"numéro de billet. La disponibilité des options varie en fonction du format " -"de numéro de billet choisi ci-dessus." - -#: ../settings/ticket.rst:122 -msgid "Checksum (default: ``no``)" -msgstr "Somme de contrôle (default: ``no``)" -#: ../settings/ticket.rst:118 -#, fuzzy -msgid "" -"If set to yes, we'll built a checksum to further \"unique\" the ticket " -"number of your system. If you're dealing with many other ticket systems this " -"might help to prevent false positive follow up detection on tickets." +#: ../settings/branding.rst:35 +msgid "Changing this value has direct consequences on the following areas:" msgstr "" -"Si la valeur est définie sur \"yes\", nous créerons une somme de contrôle " -"pour \"rendre unique\" le numéro de billet de votre système. Si vous avez " -"affaire à de nombreux autres systèmes de billets, ceci pourrait aider à " -"empêcher les détections de faux positifs de suivi sur les billets." -#: ../settings/ticket.rst:122 -msgid "This will also add another digit to the ticket number." +#: ../settings/branding.rst:37 +msgid ":doc:`/manage/scheduler` tasks" msgstr "" -"Cela ajoutera également un autre chiffre significatif au numéro de billet." -#: ../settings/ticket.rst:137 -msgid "Min. size of Number (default: ``5``)" -msgstr "Taille minimale du nombre (par défaut: ``5``)" +#: ../settings/branding.rst:38 +msgid "search indexing (and thus reporting)" +msgstr "" -#: ../settings/ticket.rst:125 -msgid "" -"This setting defines the minimum length of your ticket number. If your " -"counter is not yet high enough, Zammad will fill the number with zeros to " -"ensure the wanted length." +#: ../settings/branding.rst:40 +msgid "calendar subscriptions" msgstr "" -"This setting defines the minimum length of your ticket number. If your " -"counter is not yet high enough, Zammad will fill the number with zeros to " -"ensure the wanted length." -#: ../settings/ticket.rst:129 -msgid "" -"Please note that the minimum length is ``3`` (SystemID + at least one digit " -"if below 10). Also, if the length is no longer long enough, the number will " -"automatically get one digit longer. Ticket-Numbers **do not overflow**, thus " -"it's save to keep it at 5 or set it lower if wanted." +#: ../settings/branding.rst:41 +msgid "browser printing" msgstr "" -"Veuillez noter que la longueur minimale est de ``3`` (SystemID + au moins un " -"chiffre si inférieur à 10). De plus, si la largeur n'est plus assez longue, " -"le numéro obtiendra automatiquement un chiffre significatif de plus. Les " -"numéros de billet **ne débordent pas**, il est donc préférable de le " -"conserver à 5 ou de l'abaisser si vous le souhaitez." -#: ../settings/ticket.rst:135 +#: ../settings/branding.rst:43 msgid "" -"This option is only available if ticket number format is set to " -"``Increment``!" +"Please note that some of above are fallbacks in case Zammad could not detect " +"the agents timezone correctly." msgstr "" -"Cette option n'est disponible que si le format du numéro de billet est réglé " -"sur ``Increment``!" -#: ../settings/ticket.rst:142 -msgid "Auto-Assignment" -msgstr "Affectation automatique" +#: ../settings/branding.rst:77 +msgid "Pretty Date" +msgstr "" -#: ../settings/ticket.rst:144 +#: ../settings/branding.rst:47 msgid "" -"In a larger Zammad environment, it happens that several agents open the same " -"ticket at the same time. Although collision detection is then effective, the " -"efficiency of processing can be increased by means of the automatic " -"assignment of tickets when a ticket is opened." +"This setting allows you to define how Zammad should display time stamps " +"within the interface to all users." msgstr "" -"Dans un environnement Zammad plus grand, il arrive que plusieurs agents " -"ouvrent le même billet en même temps. Bien que la détection de collision " -"soit efficace, l'efficacité du traitement peut être augmentée au moyen de " -"l'attribution automatique de billet à leur ouverture." -#: ../settings/ticket.rst:149 -#, fuzzy +#: ../settings/branding.rst:50 msgid "" -"The automatic assignment of tickets can be activated and configured in the " -"admin area under Settings > Ticket > Auto Assignment." +"This does not have any effect on how Zammad returns e.g. time values via " +"variables." msgstr "" -"L'affectation automatique des billets peut être activée et configurée sur la " -"page d'administration sous Paramètres -> Billet -> Affectation automatique." -#: ../settings/ticket.rst:152 -#, fuzzy -msgid "" -"The auto assignment only works if the ticket has no owner yet. By default, " -"the agent can always reset the ticket owner to ``-`` if needed." +#: ../settings/branding.rst:77 +msgid "Choose in between the following options:" msgstr "" -"L'affectation automatique ne démarre que si le billet n'a pas encore de " -"propriétaire. Par défaut, l'agent peut toujours réinitialiser le " -"propriétaire du billet sur ``-`` si nécessaire." -#: ../settings/ticket.rst:155 -#, fuzzy -msgid "" -"If you want to use this function for only specific tickets, you can " -"configure the conditions accordingly to meet your requirement. By default " -"the condition affects all tickets with the state ``open``." +#: ../settings/branding.rst:64 +msgid "relative" msgstr "" -"Si vous souhaitez utiliser cette fonction uniquement pour des billets " -"spécifiques, vous pouvez configurer les conditions en conséquence pour " -"répondre à vos besoins. Par défaut, la condition affecte tous les billets " -"avec l'état ``Ouvert``." -#: ../settings/ticket.rst:161 -#, fuzzy +#: ../settings/branding.rst:55 msgid "" -"If you need to exclude users (e.g. a group leader), you can search and " -"select the desired agents in the ``Exception Users`` list. The search " -"function in this area is only effective, if you have too many agents to " -"display at once to help you with the configuration." +"This timestamp shows a relative time span until it switches to a date. Over " +"time, it will change as follows:" msgstr "" -"La fonction de recherche dans cette zone n'est efficace, pour vous aider " -"dans la configuration, que si vous avez trop d'agents à afficher à la fois." - -#: ../settings/ticket.rst:167 -#, fuzzy -msgid "Notifications" -msgstr "Bloquer les notifications" -#: ../settings/ticket.rst:191 -#, fuzzy -msgid "Default Notifications" -msgstr "Bloquer les notifications" +#: ../settings/branding.rst:58 +msgid "just now" +msgstr "" -#: ../settings/ticket.rst:170 -msgid "" -"This setting allows you to configure the default ticket notifications that " -"will be applied to all new agent users (incl. users who were just assigned " -"agent role). Simply change the notification matrix to desired state and " -"press **Save**." +#: ../settings/branding.rst:59 +msgid "5 minutes ago" msgstr "" -#: ../settings/ticket.rst:175 -msgid "" -"In case an agent already exists, their ticket notification preferences will " -"be preserved. Optionally, you can also **Apply current defaults to all " -"agents**." +#: ../settings/branding.rst:60 +msgid "3 days 1 hour ago" msgstr "" -#: ../settings/ticket.rst:181 -msgid "" -"**Potential time-consuming action:** Applying default ticket notifications " -"to all agent users may take some time to complete, be patient! The exact " -"time will depend on the size of your system and the number of agents." +#: ../settings/branding.rst:61 +msgid "``03/04/2022``" +msgstr "" + +#: ../settings/branding.rst:63 +msgid "Hovering the timestamp helps, you'll always get a clean timestamp then." msgstr "" -#: ../settings/ticket.rst:185 -msgid "" -"**Active agents only!** When current default ticket notifications are " -"applied, only active agent users are considered. In case an agent is re-" -"activated *after* this action, they will still have the old notification " -"configuration." +#: ../settings/branding.rst:71 +msgid "absolute" msgstr "" -#: ../settings/ticket.rst:190 +#: ../settings/branding.rst:67 msgid "" -"In case you want to go back to the initial state of ticket notifications, " -"you can click on **Reset to default** button." +"This timestamp always includes the week day. For one week after creation, " +"the timestamp will not contain the date itself: Thursday 18:35." msgstr "" -#: ../settings/ticket.rst:194 ../settings/ticket.rst:196 -msgid "Duplicate Detection" +#: ../settings/branding.rst:71 +msgid "After a week it will switch to: ``Friday 4. Mar 16:00``." msgstr "" -#: ../settings/ticket.rst:236 ../settings/ticket.rst:238 -msgid "Detect Duplicate Ticket Creation" +#: ../settings/branding.rst:76 +msgid "timestamp" msgstr "" -#: ../settings/ticket.rst:197 ../settings/ticket.rst:199 +#: ../settings/branding.rst:74 msgid "" -"This setting turns on the duplicate ticket detection mechanism during ticket " -"creation. If similar tickets are found in the system, a suitable warning " -"will be shown to the user trying to create a ticket." +"This will cause Zammad to show a complete timestamp according to your locale " +"defaults. For English this could be e.g. ``2022/12/03 2:40 pm`` or for " +"German e.g. ``12.03.2022 14:40``." msgstr "" -#: ../settings/ticket.rst:204 ../settings/ticket.rst:206 -msgid "A Sample Duplicate Ticket Warning" +#: ../settings/branding.rst:78 +msgid "Default setting: ``relative``." +msgstr "" + +#: ../settings/security.rst:2 +msgid "Security" msgstr "" -#: ../settings/ticket.rst:206 ../settings/ticket.rst:208 +#: ../settings/security.rst:4 msgid "" -"You can choose which ticket attributes will be matched by selecting them in " -"**Attributes to compare** field. Only if the ticket attribute value provided " -"by the user in the ticket create form is *equal* with the attribute in an " -"existing ticket, the warning will be shown." +"For your overview we split each tab within security settings into its own " +"page:" msgstr "" -#: ../settings/ticket.rst:211 ../settings/ticket.rst:213 -msgid "**Warning title** and **Warning message** are configurable as well." +#: ../settings/security/base.rst:2 ../settings/system/base.rst:2 +#: ../settings/ticket.rst:8 +msgid "Base" +msgstr "Base" + +#: ../settings/security/base.rst:5 +msgid "New User Accounts" msgstr "" -#: ../settings/ticket.rst:213 ../settings/ticket.rst:215 +#: ../settings/security/base.rst:9 msgid "" -"You can limit the detection only to certain user roles. By default, only " -"agents will see the warning." +"Activates the `register as a new customer` function on the login page. If " +"set to ``no`` only administrators or agents can create new accounts manually." msgstr "" -#: ../settings/ticket.rst:216 ../settings/ticket.rst:218 -msgid "" -"If you don't want to show the matched tickets as part of the warning, you " -"can set **Show matching ticket(s) in the warning** setting to *no*." +#: ../settings/security/base.rst:13 ../settings/security/base.rst:38 +#: ../settings/security/base.rst:66 +msgid "Default setting: ``yes``" +msgstr "" + +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"New User Accounts\" setting" msgstr "" -#: ../settings/ticket.rst:219 ../settings/ticket.rst:221 +#: ../settings/security/base.rst:22 msgid "" -"By default, **Permission level for looking up ticket** is set to *User*, " -"which means user permissions will be honored during sarch. The user will " -"see the warning only if tickets they have access to are matched. " -"Alternatively, you can set this setting to *System*, in which case the " -"search will happen within *all* tickets in the system, regardless of user " -"permissions." +"Deactivation of above function **does not** deactivate automatic account " +"creation! This means: If a user writes e.g. an email to Zammad and has no " +"account yet, Zammad will automatically create the account. User accounts are " +"a direct dependency of tickets and thus technically mandatory." msgstr "" -#: ../settings/ticket.rst:225 ../settings/ticket.rst:227 -msgid "**🦺 Safety first!**" +#: ../settings/security/base.rst:29 +msgid "Lost Password" msgstr "" -#: ../settings/ticket.rst:227 ../settings/ticket.rst:229 +#: ../settings/security/base.rst:33 msgid "" -"Even if the permission level is set to *System*, the user will not be shown " -"the tickets they don't have access to in the warning, even if they match." +"Activates the `lost password` function on the login page. If set to ``no`` " +"only administrators may change the user's password - users may update their " +"own password if they're still logged in and they have the required :doc:" +"`permission `." msgstr "" -#: ../settings/ticket.rst:231 ../settings/ticket.rst:233 -msgid "" -"However, just the confirmation about the existence of the tickets in the " -"system may be considered an unwanted information disclosure. Use this option " -"carefully!" +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"Lost Password\" setting" msgstr "" -#: ../settings/ticket.rst:235 ../settings/ticket.rst:237 +#: ../settings/security/base.rst:49 msgid "" -"Finally, you can configure between matching within **All tickets** or **Open " -"tickets** only by setting **Match tickets in following states**. Depending " -"on the current ticket state, a ticket may or not be matched." +"With third party authentications - but especially LDAP - you may want to " +"disable this function. Zammad **will not** change third party login " +"passwords and instead set or change the local password!" msgstr "" -#: ../system/core-workflows.rst:2 -msgid "Core Workflows" +#: ../settings/security/base.rst:56 +msgid "Password Login" msgstr "" -#: ../system/core-workflows.rst:4 +#: ../settings/security/base.rst:60 msgid "" -"Core Workflows allow you to adjust object attributes in many ways. For " -"example:" +"Activates the username & password login by default and if no third-party " +"login is activated. Disabling password login on the Zammad login page only " +"takes effect if you enable any :doc:`third-party`." msgstr "" -#: ../system/core-workflows.rst:7 -msgid "show / hide fields" +#: ../settings/security/base.rst:64 +msgid "See :doc:`third-party` for supported third-party logins." msgstr "" -#: ../system/core-workflows.rst:8 -msgid "adjust mandatory setting" +#: ../settings/security/base.rst:0 +msgid "Figure showing de-activated \"Password Login\" setting" msgstr "" -#: ../system/core-workflows.rst:9 -msgid "manipulate available options" +#: ../settings/security/base.rst:77 +msgid "" +"To help administrators to overcome \"login issues\", Zammad automatically " +"offers a password request for administrator users. This allows you to adjust " +"Third-Party applications even if the login does no longer work!" msgstr "" -#: ../system/core-workflows.rst:11 -msgid "" -"With this, you can provide exactly the information your users really need!" +#: ../settings/security/base.rst:84 +msgid "Session Timeout" msgstr "" -#: ../system/core-workflows.rst:15 +#: ../settings/security/base.rst:86 msgid "" -"If the pre-defined :doc:`/system/objects` are not enough, please add them " -"beforehand." +"All settings below by default are set to ``4 weeks``. Session Timeout " +"defines the life time of a users session. As soon as it's reached, Zammad " +"will automatically log off the session in question." msgstr "" -#: ../system/core-workflows.rst:17 +#: ../settings/security/base.rst:91 msgid "" -"If you experience slow or unreliable field updates, please see :ref:`Core " -"Workflow Ajax Modus `" +"Zammad takes the highest value set assigned for the user based on the " +"permissions." msgstr "" -#: ../system/core-workflows.rst:22 -msgid "" -"This is a very enhanced functionality and can cause unexpected UI behavior. " -"Please ensure to test your use cases after configuration to reduce surprises." +#: ../settings/security/base.rst:94 +msgid "``admin``" msgstr "" -#: ../system/core-workflows.rst:None -msgid "Dialogue for adding a new workflow" +#: ../settings/security/base.rst:96 +msgid "``ticket.customer``" msgstr "" -#: ../system/core-workflows/condition-operators.rst:2 -msgid "Core Workflow Condition Operators" +#: ../settings/security/base.rst:97 +msgid "``default`` (fallback if user doesn't have above permissions set)" msgstr "" -#: ../system/core-workflows/condition-operators.rst:4 +#: ../settings/security/base.rst:99 msgid "" -"You might know that there is a separate section for explaining :doc:" -"`condition operators `. Head over there to " -"see a detailed explanation of many conditions and operators." +"All settings act independently from each other allowing you to disable the " +"timeouts for e.g. admins, but not agents." msgstr "" -#: ../system/core-workflows/condition-operators.rst:8 -msgid "" -"Due to differences to other places in Zammad which are also using conditions " -"(e.g. triggers), you can find a dedicated description of operators for core " -"workflows below." +#: ../settings/security/base.rst:115 +#: ../system/integrations/checkmk/api-reference.rst:13 +msgid "Example" msgstr "" -#: ../system/core-workflows/condition-operators.rst:12 -msgid "" -"Be aware that the availability of the operators depends on the selected " -"attribute and its field type. Some of the operators may only be available " -"for system attributes (e.g. for \"tags\", \"active\")." +#: ../settings/security/base.rst:107 +msgid "Let's suppose you configured the following session timeouts" msgstr "" -#: ../system/core-workflows/condition-operators.rst:20 -msgid "Operator" +#: ../settings/security/base.rst:104 +msgid "default: 3 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:22 -msgid "after (absolute)" +#: ../settings/security/base.rst:105 +msgid "admin: 2 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:23 -msgid "Matches if a date/time is after a specific point in time." +#: ../settings/security/base.rst:106 +msgid "ticket.agent: 4 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:24 -msgid "after (relative)" +#: ../settings/security/base.rst:107 +msgid "ticket.customer: 1 week" msgstr "" -#: ../system/core-workflows/condition-operators.rst:25 -msgid "Matches if a time span after a specified event has passed." +#: ../settings/security/base.rst:115 +msgid "This results in the following situations" msgstr "" -#: ../system/core-workflows/condition-operators.rst:26 -msgid "before (absolute)" +#: ../settings/security/base.rst:110 +msgid "a user with ``admin`` permission will have a timeout of 2 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:27 -msgid "Matches if a date/time is before a specific point in time." +#: ../settings/security/base.rst:111 +msgid "" +"a user with ``admin`` and ``ticket.agent`` permissions will have a timeout " +"of 2 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:28 -msgid "before (relative)" +#: ../settings/security/base.rst:113 +msgid "" +"a user with ``ticket.customer`` permission will have a timeout of 1 week" msgstr "" -#: ../system/core-workflows/condition-operators.rst:29 -msgid "Matches if a time span after a specified event has not passed." +#: ../settings/security/base.rst:115 +msgid "" +"a user with neither ``admin``, ``ticket.agent`` nor ``ticket.customer`` " +"permissions will have a timeout of 3 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:30 -msgid "contains" +#: ../settings/security/password.rst:4 +msgid "" +"This section allows you to define password requirements for the local user " +"accounts." msgstr "" -#: ../system/core-workflows/condition-operators.rst:31 -msgid "Matches if a specified value is present." +#: ../settings/security/password.rst:9 +msgid "" +"Zammad does **not** allow you to change your LDAP password, instead, it will " +"set a password in its local database which might confuse your users. This " +"might be addressed in the future by `#1169 `_." msgstr "" -#: ../system/core-workflows/condition-operators.rst:33 -msgid "Matches if all of the specified values are present." +#: ../settings/security/password.rst:14 +msgid "**Exception for admins**" msgstr "" -#: ../system/core-workflows/condition-operators.rst:35 -msgid "Matches if none of the specified values are present." +#: ../settings/security/password.rst:16 +msgid "" +"Please note that below password policies *do not* affect administrators " +"setting passwords on user accounts. While this seems strange and not safe we " +"believe that an administrator knowing an user's password is insecure as well." msgstr "" -#: ../system/core-workflows/condition-operators.rst:36 -msgid "contains not" +#: ../settings/security/password.rst:21 +msgid "The suggested workflow is either:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:37 -msgid "Matches if a specified value is not present." +#: ../settings/security/password.rst:23 +msgid "" +"to use third party logins to not require local passwords at all **- or -**" msgstr "" -#: ../system/core-workflows/condition-operators.rst:39 -msgid "Matches if one specified value is present." +#: ../settings/security/password.rst:25 +msgid "to require your *user to reset the password* upon first login." msgstr "" -#: ../system/core-workflows/condition-operators.rst:41 -msgid "Matches if one specified value is not present." +#: ../settings/security/password.rst:27 +msgid "" +"This way administrators are not required to set a user's password at all!" msgstr "" -#: ../system/core-workflows/condition-operators.rst:42 -msgid "does not match regex" +#: ../settings/security/password.rst:31 +msgid "Maximum Failed Logins" msgstr "" -#: ../system/core-workflows/condition-operators.rst:43 -msgid "Matches if content doesn't fit to regex rule." +#: ../settings/security/password.rst:33 +msgid "" +"You can choose a value between ``4`` and ``20``. This defines how often a " +"login to a user account may fail until Zammad will lock it. Your users can " +"always use the \"forgot password\" function to change their password and " +"unlock their account." msgstr "" -#: ../system/core-workflows/condition-operators.rst:44 -msgid "ends with" +#: ../settings/security/password.rst:38 +msgid "The default value is ``10``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:45 -msgid "Matches if content ends with specified value." +#: ../settings/security/password.rst:42 +msgid "Beside changing the user's password, you can also unlock accounts via" msgstr "" -#: ../system/core-workflows/condition-operators.rst:46 -msgid "ends with one of" +#: ../settings/security/password.rst:44 +msgid ":ref:`user management list `" msgstr "" -#: ../system/core-workflows/condition-operators.rst:47 -msgid "Matches if content ends with one of the specified values." +#: ../settings/security/password.rst:45 +msgid ":docs:`console `" msgstr "" -#: ../system/core-workflows/condition-operators.rst:48 -msgid "from (relative)" +#: ../settings/security/password.rst:46 +msgid ":docs:`API `" msgstr "" -#: ../system/core-workflows/condition-operators.rst:49 -msgid "Matches if date/time is after a period of time after an event." +#: ../settings/security/password.rst:50 +msgid "Failed logins via LDAP no longer lock accounts." msgstr "" -#: ../system/core-workflows/condition-operators.rst:51 -msgid "Matches if content is equal to a specified value." +#: ../settings/security/password.rst:53 +msgid "2 Lower Case And 2 Upper Case Characters" msgstr "" -#: ../system/core-workflows/condition-operators.rst:52 -msgid "is any of" +#: ../settings/security/password.rst:55 +msgid "" +"You can add complexity to passwords by enforcing at least 2 upper and lower " +"case characters." msgstr "" -#: ../system/core-workflows/condition-operators.rst:53 -msgid "Matches if content is equal to any of specified values." +#: ../settings/security/password.rst:58 ../settings/security/password.rst:83 +msgid "The default value is ``no``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:54 -msgid "is modified" +#: ../settings/security/password.rst:62 +msgid "Minimum Length" msgstr "" -#: ../system/core-workflows/condition-operators.rst:55 -msgid "Matches if content is modified." +#: ../settings/security/password.rst:64 +msgid "" +"This defines the minimum password length required for users to provide (from " +"``4`` to ``20``)." msgstr "" -#: ../system/core-workflows/condition-operators.rst:57 -#: ../system/core-workflows/condition-operators.rst:61 -msgid "True from the moment of changing content until form submit." +#: ../settings/security/password.rst:67 +msgid "The default value is ``6``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:58 -msgid "is modified to" +#: ../settings/security/password.rst:71 +msgid "Digit Required" msgstr "" -#: ../system/core-workflows/condition-operators.rst:59 -msgid "Matches if content is modified to a specific value." +#: ../settings/security/password.rst:73 +msgid "This enforces your users to use at least one digit within the password." msgstr "" -#: ../system/core-workflows/condition-operators.rst:62 -msgid "is none of" +#: ../settings/security/password.rst:75 +msgid "The default value is ``yes``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:63 -msgid "Matches if content is none of any specified values." +#: ../settings/security/password.rst:78 +msgid "Special Character Required" msgstr "" -#: ../system/core-workflows/condition-operators.rst:65 -msgid "Matches if content is not equal to a specified value." +#: ../settings/security/password.rst:80 +msgid "" +"This setting allows you to improve your password quality even more by " +"enforcing the password to contain at least one special character." msgstr "" -#: ../system/core-workflows/condition-operators.rst:67 -msgid "Matches if content is present." +#: ../settings/security/ssl-certificates.rst:2 +msgid "SSL Certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:68 -msgid "just changed" +#: ../settings/security/ssl-certificates.rst:7 +msgid "" +"Zammad offers the possibility to upload custom certificates and custom " +"Certificate Authority (CA) certificates. This can be useful if you want to " +"connect Zammad the secure way to other systems which are using custom " +"certificates." msgstr "" -#: ../system/core-workflows/condition-operators.rst:69 -msgid "Matches if content has changed." +#: ../settings/security/ssl-certificates.rst:12 +msgid "" +"An example usecase might be: You have an internal LDAP server that is not " +"accessible from the internet, and you want a SSL-encrypted connection, using " +"a custom certificate." msgstr "" -#: ../system/core-workflows/condition-operators.rst:71 -#: ../system/core-workflows/condition-operators.rst:75 +#: ../settings/security/ssl-certificates.rst:19 msgid "" -"Only true for the moment of changing content until next form field action/" -"click." +"You should have an existing custom certificate file and/or a custom CA " +"certificate file, which you want to add to Zammad. As filetype ``.crt`` is " +"supported and the certificate format has to be PEM (Base64 ASCII)." msgstr "" -#: ../system/core-workflows/condition-operators.rst:72 -msgid "just changed to" +#: ../settings/security/ssl-certificates.rst:25 +msgid "" +"When you import a custom CA certificate, all certificates generated with " +"this are trusted. This can be useful if you have more than one system/" +"certificate you want to connect to and the certificates are issued from the " +"same custom CA." msgstr "" -#: ../system/core-workflows/condition-operators.rst:73 -msgid "Matches if content has changed to a specified value." +#: ../settings/security/ssl-certificates.rst:31 +msgid "Add a Certificate" msgstr "" -#: ../system/core-workflows/condition-operators.rst:76 -msgid "matches regex" +#: ../settings/security/ssl-certificates.rst:33 +msgid "" +"To add a custom certificate or a custom CA certificate, head over to the " +"Admin panel > Settings > Security > SSL Certificates. Here you can find a " +"\"Add SSL Certificate\" button. In the dialog you can either select a " +"certificate file or paste the content of the certificate:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:77 -msgid "Matches if value fits to regex rule." +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate adding dialog" msgstr "" -#: ../system/core-workflows/condition-operators.rst:79 -msgid "Matches if no content is present." +#: ../settings/security/ssl-certificates.rst:43 +msgid "" +"After selecting a file or pasting the content of the certificate, click on " +"the \"Add\" button to finally upload it to Zammad. Then, the certificates " +"are immediately effective, no restart or similar required." msgstr "" -#: ../system/core-workflows/condition-operators.rst:80 -msgid "starts with" +#: ../settings/security/ssl-certificates.rst:49 +msgid "" +"Please note that only single certificate files are supported. That means if " +"you want to import a certificate / CA certificate, it must contain **only " +"one** certificate." msgstr "" -#: ../system/core-workflows/condition-operators.rst:81 -msgid "Matches if content starts with specified value." +#: ../settings/security/ssl-certificates.rst:54 +msgid "Certificate Overview" msgstr "" -#: ../system/core-workflows/condition-operators.rst:82 -msgid "starts with one of" +#: ../settings/security/ssl-certificates.rst:56 +msgid "" +"After you added a certificate, you can see a table with information for each " +"added certificate:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:83 -msgid "Matches if content starts with one of the specified values." +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing table of added certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:84 -msgid "till (relative)" +#: ../settings/security/ssl-certificates.rst:64 +msgid "" +"Here you can download the certificate or delete it, if you don't need it " +"anymore." msgstr "" -#: ../system/core-workflows/condition-operators.rst:85 -msgid "Matches if date/time is before a period of time before an event." -msgstr "" +#: ../settings/security/ssl-certificates.rst:68 +#, fuzzy +msgid "Deleting Certificates" +msgstr "Bloquer les notifications" -#: ../system/core-workflows/condition-operators.rst:86 -msgid "today" +#: ../settings/security/ssl-certificates.rst:70 +msgid "" +"If you want to delete a specific certificate, you can do it by clicking on " +"the menu in the actions column and selecting delete:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:87 -msgid "Matches if date/time is today." +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate deletion button" msgstr "" -#: ../system/core-workflows/condition-operators.rst:88 -msgid "within last (relative)" +#: ../settings/security/ssl-certificates.rst:79 +msgid "Downloading Certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:89 +#: ../settings/security/ssl-certificates.rst:81 msgid "" -"Matches if date/time content is within specified period of time before now." +"If you want to download your certificates, you can do this as well via " +"corresponding action buttons." msgstr "" -#: ../system/core-workflows/condition-operators.rst:91 -msgid "within next (relative)" +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate download button" msgstr "" -#: ../system/core-workflows/condition-operators.rst:92 -msgid "" -"Matches if date/time content is within specified period of time after now." +#: ../settings/security/third-party.rst:13 +msgid "Login Providers" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:2 -msgid "How do they work?" +#: ../settings/security/third-party.rst:2 +msgid "Third-Party Applications" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:4 +#: ../settings/security/third-party.rst:4 msgid "" -"Core Workflows are executed according to their priority. If two workflows " -"have the same priority, they are executed in alphabetical order based on " -"their **name**." +"Third party authentication is a great way to help your users to login to " +"Zammad more easily. If the account is yet unknown, Zammad will create a new " +"user automatically, without the user needed to interact (e.g. type in his " +"name). Another big advantage of this feature is that your user doesn't need " +"to remember another password." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:8 +#: ../settings/security/third-party.rst:10 msgid "" -"Because of the way Core Workflows work, all changes to attributes are " -"checked with the application server - please see :doc:`limitations` for " -"possible issues." +"You can deactivate logging in via :ref:`security_password_login` if any of " +"the mentioned authentication providers are enabled in your instance." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:12 +#: ../settings/security/third-party.rst:27 msgid "" -"Below we're talking about settings that are important and not self-" -"explanatory." +"We're currently missing documentation for the following login providers:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:17 +#: ../settings/security/third-party.rst:29 +msgid "LinkedIn" +msgstr "" + +#: ../settings/security/third-party.rst:30 +msgid "Weibo" +msgstr "" + +#: ../settings/security/third-party.rst:35 +msgid "Automatic Account Link on Initial Logon" +msgstr "" + +#: ../settings/security/third-party.rst:37 msgid "" -"Choose the object context you want to run the workflow in. This will decide " -"on your available attributes and actions." +"In general there's two possible options for Zammad on how to deal with " +"already known users as they try to authenticate against a third-party " +"application. By default, Zammad will not automatically link \"unknown\" " +"authentication providers to existing accounts." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:20 -msgid "Ticket objects also have access to the ticket customer." +#: ../settings/security/third-party.rst:42 +msgid "" +"This means that the user has to manually link authentication providers to " +"their accounts (for more about this :user-docs:`consult the user " +"documentation `)." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:25 +#: ../settings/security/third-party.rst:46 msgid "" -"Choose in which situation the workflow is applied. Contexts can be combined " -"to avoid duplicate workflows." +"Sometimes this doesn't come in handy as this also means you'll receive error " +"messages about \"email address being in use already\" for (yet) unknown " +"third-party authentication methods." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:30 -msgid "Creation mask" +#: ../settings/security/third-party.rst:50 +msgid "" +"If you want to allow your users to always be able to log in, no matter what, " +"you may want to enable ``Automatic account link on initial logon``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:29 +#: ../settings/security/third-party.rst:None msgid "" -"If selected, your conditions and actions will affect all applicable creation " -"masks." +"Screenshot highlighting the \"Automatic account link on initial logon\"\n" +"setting" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:34 -msgid "Edit mask" +#: ../settings/security/third-party.rst:60 +msgid "Automatic Account Linking Notification" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:33 +#: ../settings/security/third-party.rst:64 msgid "" -"If selected, your conditions and actions will affect all applicable edit " -"masks." +"To improve security and your users awareness, you can enable Zammad to " +"notify your users when a new third-party application has been linked to " +"their account." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:39 +#: ../settings/security/third-party.rst:68 msgid "" -"Zammad differentiates between selected and saved conditions. These can be " -"combined wherever needed." +"This notification is sent out once per third-party application. Zammad does " +"also mention the method used, e.g.: ``Microsoft``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:42 -msgid "**⚠️ Restrict workflows to specific roles if needed!**" +#: ../settings/security/third-party.rst:71 +msgid "By default this setting is not active (set to ``no``)." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:44 +#: ../settings/security/third-party.rst:0 msgid "" -"By default and unless configured in conditions, workflow rules are executed " -"for **all roles**. This also affects your customers!" +"Screenshot showing sample notification mail after initial\n" +"third-party linking" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:50 -msgid "Selected Conditions" +#: ../settings/security/third-party.rst:85 +msgid "" +"This notification is only sent if the account in question already exists. If " +"the login via the third-party also creates the missing account, the " +"notification will be skipped." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:48 -msgid "" -"These conditions are based on form values and match if an appropriate " -"selection is made (e.g. choosing another group in the ticket without " -"saving). This applies for drafts (active selection) and currently saved " -"values." +#: ../settings/security/third-party.rst:89 +msgid "This means it only affects:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:64 -msgid "Saved Conditions" +#: ../settings/security/third-party.rst:91 +msgid "manual account linking within the third-party page of the users profile" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:53 +#: ../settings/security/third-party.rst:92 msgid "" -"These conditions only match if the selected values are stored in the " -"database. It ignores the current value or selection of the field, as long as " -"the changes are not saved (e.g. performing field operations for an existing " -"ticket, which is viewed/opened by an agent)." +"logging into an existing local account by utilizing the *automatic account " +"link on initial logon* functionality" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:60 +#: ../settings/security/third-party.rst:None msgid "" -"Keep in mind that the value has to be available in the situation where you " -"need it. Otherwise the condition won't match." +"Screenshot showing the \"automatic account linking notification\"\n" +"setting" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:63 -msgid "" -"Example: you can't perform any actions with *saved condition* on a ticket in " -"creation, because there are no saved values at that time." +#: ../settings/security/third-party.rst:100 +msgid "No User Creation on Logon" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:66 +#: ../settings/security/third-party.rst:102 msgid "" -"You can find a description of the condition operators for core workflows :" -"doc:`here `." +"By default, Zammad will create a new user account if the user logs in via a " +"third-party application and the account doesn't exist yet." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:72 +#: ../settings/security/third-party.rst:105 msgid "" -"Which actions should we run on the relevant fields? The possible actions " -"depend on the object type. However, usually you can at least change the " -"visibility and whether the field is mandatory." +"If you want to prevent Zammad from creating new accounts on logon, you can " +"disable this feature by setting ``No user creation on logon`` to ``yes``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:76 -msgid "Be aware that actions are not available for **related** context." +#: ../settings/security/third-party.rst:None +msgid "Screenshot showing the \"no user creation on logon\" setting" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:78 +#: ../settings/security/third-party/facebook.rst:4 msgid "" -"**Example:** Let's assume you are working in the ticket context. While you " -"can have customer *conditions*, you *can't adjust* objects with actions in " -"that scope. That's because this wouldn't have any impact on the ticket " -"dialog. Of course all ticket attributes (state, owner, ...) are available." +"It is possible to create a quick login for your helpdesk via Facebook To do " +"so, you need to follow these steps:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:84 -msgid "" -"Please also have a look at our :doc:`limitations` to be safe from surprises." +#: ../settings/security/third-party/facebook.rst:9 +msgid "Register Facebook App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:88 -msgid "Available Operators" +#: ../settings/security/third-party/facebook.rst:11 +msgid "" +"Visit [https://developers.facebook.com/apps/] and click on \"Add a new App\"" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:90 -msgid "The availability of operators depends on the object type and scope." +#: ../settings/security/third-party/facebook.rst:None +msgid "initial page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:94 -msgid "" -"Please note that actions may or may not restrict API based access to " -"attributes. We're displaying the following icons for your overview to " -"understand these limits better:" +#: ../settings/security/third-party/facebook.rst:17 +msgid "After that enter the app settings" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:0 -msgid "|api| This icon indicates the action affects the API." +#: ../settings/security/third-party/facebook.rst:None +msgid "Create App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:163 -msgid "api" +#: ../settings/security/third-party/facebook.rst:22 +msgid "Navigate to \"Settings\" and fill in this infromation" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:0 -msgid "|ui| This icon indicates the action only affects the web interface." +#: ../settings/security/third-party/facebook.rst:None +msgid "App Settings" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:167 -msgid "ui" +#: ../settings/security/third-party/facebook.rst:27 +msgid "Navigate to app review and Check \"Make [appname] public?\"" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:102 -msgid "show |ui|" +#: ../settings/security/third-party/facebook.rst:None +msgid "App Review" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:102 -msgid "Display the chosen field. Allows setting of values." +#: ../settings/security/third-party/facebook.rst:35 +msgid "Configure Zammad as Facebook App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:109 -msgid "hide |ui|" +#: ../settings/security/third-party/facebook.rst:37 +msgid "" +"Navigate to \"Admin -> Security -> Third Party Applications\" and enter the " +"App ID and the App Secret. You can find this Key in the Dashbard of your " +"Facebok app." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:105 -msgid "" -"Hide the chosen field. However, it technically still allows setting the " -"field." +#: ../settings/security/third-party/facebook.rst:None +msgid "Zammad Configuration" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:108 +#: ../settings/security/third-party/facebook.rst:44 +#: ../settings/security/third-party/github.rst:43 +#: ../settings/security/third-party/gitlab.rst:46 msgid "" -"Please note that the field is **not** gone and still contains an existing " -"value (if set)! Consider *remove* instead, if you want this field to be gone." +"Now you can link accounts via \"Avatar -> Profile -> Link Accounts\" or " +"login via Zammad login page." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:112 -msgid "remove |ui|" +#: ../settings/security/third-party/github.rst:2 +#: ../system/integrations/github.rst:2 +msgid "GitHub" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:112 -msgid "Entirely removes the field. The field value will not be evaluated." +#: ../settings/security/third-party/github.rst:4 +msgid "" +"It is possible to create a quick login for your helpdesk via GitHub. To " +"activate the quick login you need to enable OAuth for GitHub." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:115 -msgid "set mandatory |ui| |api|" +#: ../settings/security/third-party/github.rst:8 +msgid "Register GitHub App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:115 -msgid "Sets the field to mandatory." +#: ../settings/security/third-party/github.rst:10 +msgid "" +"Visit https://www.github.com/settings/applications/new and enter the app " +"settings. As callback URL enter \"https://zammad_host/auth/github/callback\" " +"where zammad_host has to be replaced with your Zammad FQDN" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:118 -msgid "set optional |ui| |api|" +#: ../settings/security/third-party/github.rst:None +msgid "Register OAuth app on www.github.com" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:118 -msgid "Sets the field to optional." +#: ../settings/security/third-party/github.rst:19 +msgid "Configure Zammad as GitHub App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:124 -msgid "add option |ui| |api|" +#: ../settings/security/third-party/github.rst:21 +msgid "" +"Enter the \"APP ID\" and the \"APP SECRET\" from the GitHub OAUTH " +"Applications Dashboard" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:121 -msgid "Allows adding options to tree selects or selects." +#: ../settings/security/third-party/github.rst:None +msgid "GitHub config in Zammad admin interface" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:123 +#: ../settings/security/third-party/github.rst:28 msgid "" -"You have to use the \"remove option\" before performing this action. It " -"allows you to use *existing* configured values." +"After you configured the GitHub credentials and activated the login method, " +"you should see a new icon on the login page." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:128 -msgid "remove option |ui| |api|" +#: ../settings/security/third-party/github.rst:None +msgid "GitHub logo on login page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:127 +#: ../settings/security/third-party/github.rst:34 msgid "" -"Allows removing options from tree selects or selects. It allows you to use " -"*existing* configured values." +"If you click on the icon you will be redirected to GitHub and see something " +"similar to this:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:134 -msgid "set fixed to |ui| |api|" +#: ../settings/security/third-party/github.rst:None +msgid "GitHub oauth page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:131 -msgid "Reduces the available options by your selection." +#: ../settings/security/third-party/github.rst:40 +#: ../settings/security/third-party/gitlab.rst:42 +msgid "" +"When you grant the access you will be redirected to your Zammad instance and " +"logged in as a customer." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:133 -msgid "" -"This reduces your workflows in terms of *add option* and *remove option*." +#: ../settings/security/third-party/gitlab.rst:2 +msgid "Gitlab" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:137 -msgid "fill in |ui|" +#: ../settings/security/third-party/gitlab.rst:4 +msgid "" +"It is possible to create a quick login for your helpdesk via Gitlab. To " +"activate the quick login you need to enable OAuth for Gitlab." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:137 -msgid "Allows filling in of string and integer fields with your values." +#: ../settings/security/third-party/gitlab.rst:8 +msgid "Register Gitlab App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:141 -msgid "fill in empty |ui|" +#: ../settings/security/third-party/gitlab.rst:10 +msgid "To register an app in Gitlab open your profile and select applications." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:140 +#: ../settings/security/third-party/gitlab.rst:12 msgid "" -"Allows filling in of string and integer fields with your values **if the " -"field is empty**." +"As callback URL enter \"https://zammad-fqdn/auth/gitlab/callback\" where " +"zammad-fqdn has to be replaced with your Zammad FQDN" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:144 -msgid "select |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Register OAuth app on gitlab instance" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:144 -msgid "Select a specific value within a select, tree select or boolean field." +#: ../settings/security/third-party/gitlab.rst:18 +msgid "Just select *read_user* under scopes as in the screenshot and save it." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:153 -msgid "auto select |ui|" +#: ../settings/security/third-party/gitlab.rst:21 +msgid "Configure Zammad as Gitlab App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:147 -msgid "Helps users with tree select and select fields:" +#: ../settings/security/third-party/gitlab.rst:23 +msgid "" +"Enter the \"APP ID\" and the \"APP SECRET\" from the Gitlab OAUTH " +"Applications Dashboard and your Gitlab-URL in the \"SITE\" field." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:149 -msgid "" -"If the field has only one option available for selection and no value yet, " -"the value will be automatically set." +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab config in Zammad admin interface" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:152 +#: ../settings/security/third-party/gitlab.rst:30 msgid "" -"This option only works if you have one value and doesn't work if there is " -"more than one option available." +"After you configured the Gitlab credentials and activated the login method, " +"you should see a new icon on the login page." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:157 -msgid "set readonly |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab logo on login page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:156 +#: ../settings/security/third-party/gitlab.rst:36 msgid "" -"Allows you to display an attribute as read only (which means no changes are " -"possible)." +"If you click on the icon you will be redirected to Gitlab and see something " +"similar to this:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:161 -msgid "unset readonly |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab oauth page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:160 +#: ../settings/security/third-party/google.rst:4 msgid "" -"In case a workflow set the field in question to read only, you can undo this " -"with option above." +"With some easy and fast steps, you can enable Zammad to authenticate your " +"users via Google." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:172 -msgid "Stop after match" +#: ../settings/security/third-party/google.rst:8 +msgid "Register a Google App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:174 +#: ../settings/security/third-party/google.rst:10 msgid "" -"Here you can decide if other workflows are executed after the current one." +"First of all, we need to create a new project - you can skip this step if " +"you already have one." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:176 +#: ../settings/security/third-party/google.rst:15 msgid "" -"If set to ``no`` (default), further workflows will be executed if they match " -"the condition. In this case, it is possible that your actions from the " -"current workflow can be overwritten by another workflow." +"Use this link to create a new project: https://console.cloud.google.com/" +"projectcreate" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:180 +#: ../settings/security/third-party/google.rst:18 msgid "" -"If set to ``yes``, no further worflows will be executed after the current " -"one." +"Now expand the menu, expand \"APIs & Services\" and select \"Credentials\". " +"Go to the tab \"OAuth consent screen\" first and ensure to fill in the " +"requested information - without doing so you can't create credentials!" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:184 -msgid "Priority" +#: ../settings/security/third-party/google.rst:None +msgid "Creating a consent screen" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:186 +#: ../settings/security/third-party/google.rst:25 msgid "" -"You can define the sequence, in which the workflows are executed. The " -"default value is ``500``." +"After filling in and saving the consent screen information, you can go to " +"the \"Credentials\" tab and create new \"OAuth client ID\"-Credentials." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:189 +#: ../settings/security/third-party/google.rst:28 msgid "" -"The workflows are executed in ascending order by their priority. That means " -"lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." +"Fill in the necessary information as follows and replace ``zammad_host`` " +"with your FQDN:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:2 -#, fuzzy -msgid "Learn by Example" -msgstr "Exemple" +#: ../settings/security/third-party/google.rst:31 +msgid "**Application type** ``[x] Web application``" +msgstr "" -#: ../system/core-workflows/learn-by-example.rst:4 -msgid "" -"This page provides some basic examples for Core Workflows. Of course you can " -"build much more complex workflows if needed." +#: ../settings/security/third-party/google.rst:34 +msgid "**Authorized JavaScript origins** ``https://zammad_host/``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:7 +#: ../settings/security/third-party/google.rst:37 msgid "" -"To learn about Core Workflows in detail, first go to :doc:`how-do-they-work`." +"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" +"callback``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:10 -#, fuzzy -msgid "Group Based Examples" -msgstr "Exemple" +#: ../settings/security/third-party/google.rst:None +msgid "Adding a new OAuth client ID" +msgstr "" -#: ../system/core-workflows/learn-by-example.rst:12 +#: ../settings/security/third-party/google.rst:43 msgid "" -"All following workflows have the same base configurations. The workflow may " -"not use them all." +"After creating the credentials, go to your Zammad installation and navigate " +"to \"Admin > Security > Third Party Applications\" > Google. Enter your " +"Client ID and Client secret here." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:15 -msgid "Groups:" +#: ../settings/security/third-party/google.rst:None +msgid "Zammad" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:20 -#, fuzzy -msgid "Attributes:" -msgstr "Attributs d'article" +#: ../settings/security/third-party/google.rst:50 +msgid "After submitting, the login via Google can be used." +msgstr "" -#: ../system/core-workflows/learn-by-example.rst:22 -msgid "Category (Single tree selection field, not mandatory, agents only)" +#: ../settings/security/third-party/microsoft.rst:2 +msgid "Microsoft" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:23 +#: ../settings/security/third-party/microsoft.rst:4 msgid "" -"Approved (Boolean field, not mandatory, not shown, ``false`` as default)" +"Zammad's Microsoft connection allows your users with Microsoft accounts to " +"login. This works for Azure users as well and can be an alternative to :doc:" +"`/system/integrations/ldap/index`." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:24 -msgid "Operating System (Text field, not mandatory, not shown)" +#: ../settings/security/third-party/microsoft.rst:10 +msgid "" +"This documentation part does not cover our :doc:`📧 Microsoft 365 email " +"channel `." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:25 -msgid "Software used (Single selection field, not mandatory, not shown)" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screenshot showing Microsoft login button on Zammad login screen." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:68 -msgid "Group specific values and fields" +#: ../settings/security/third-party/microsoft.rst:30 +#: ../settings/security/third-party/microsoft.rst:53 +msgid "Supported account types:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:28 +#: ../settings/security/third-party/microsoft.rst:22 msgid "" -"This workflow set depends on the category field. It reduces the available " -"set of values based on the group selected." +"Please note that Zammad only supports these account types (App dependent):" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:33 -msgid "Workflow 2nd Level group" +#: ../settings/security/third-party/microsoft.rst:35 +msgid "Avatars of signing in users:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:35 +#: ../settings/security/third-party/microsoft.rst:33 msgid "" -"This reduces the category options to ``2nd Level/*``, ``Internal/*`` and " -"``Others``. It also sets further required fields to mandatory and visible." +"Zammad currently ignores user avatars. If the user is registered with e.g. " +"Gravatar, Zammad will fetch the avatar from there if enabled. See :doc:" +"`Zammad Image Service ` for more." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for 2nd level" +#: ../settings/security/third-party/microsoft.rst:38 +msgid "Step 1 - Register a Microsoft App for Zammad" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:43 -msgid "Workflow Support group" +#: ../settings/security/third-party/microsoft.rst:40 +msgid "" +"Login to the `Microsoft Azure Portal `_ and " +"navigate to App registrations to create a new app. Provide the requested " +"information as follows and register your app." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:45 +#: ../settings/security/third-party/microsoft.rst:46 +msgid "Name:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:45 msgid "" -"This reduces the category options to ``Support/*``, ``Internal/*`` and " -"``Others``. It also sets further required fields to visible." +"Any meaningful name fitting, this name will be displayed to users trying to " +"authenticate with this app." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for support" +#: ../settings/security/third-party/microsoft.rst:49 +msgid "Choose one of the above mentioned account types (see Limitations)." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:53 -msgid "Workflow Sales group" +#: ../settings/security/third-party/microsoft.rst:51 +msgid "" +"The correct account type depends on your use case. If you want to use the " +"authentication internal only, choose the first option. If you're unsure, use " +"the \"Help me choose...\" link." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:55 +#: ../settings/security/third-party/microsoft.rst:58 +msgid "Redirect URI (optional):" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:56 msgid "" -"This reduces the category options to ``Sales/*``, ``Internal/*`` and " -"``Others``." +"Select web and provide your callback URL. The callback URL looks like this: " +"``https://zammad.domain.tld/auth/microsoft_office365/callback``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for sales" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to register a Microsoft app" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:68 -#: ../system/integrations/slack.rst:88 -msgid "The Result" +#: ../settings/security/third-party/microsoft.rst:71 +msgid "Within **API permissions** add the following permissions:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:69 +msgid "``User.Read``" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:71 +msgid "Contacts" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:63 -msgid "" -"This is what the agent would experience with the above workflows in place." +#: ../settings/security/third-party/microsoft.rst:71 +msgid "``Contacts.Read``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 +#: ../settings/security/third-party/microsoft.rst:73 msgid "" -"Workflow shows objects and limits options based on selections on the group" +"You can find these permissions within *Microsoft Graph → Delegated " +"permissions*." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:90 -msgid "Approval process" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to add required API permissions" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:71 +#: ../settings/security/third-party/microsoft.rst:80 msgid "" -"In this case ``approved`` is visible to agents by default. For this " -"workflow, an additional role ``Approval person`` is required (no further " -"permissions)." +"Within **Certificates & secrets** create a new client secret. Note down the " +"returned secret **value** for later. **Do not** use the secret ID!" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that restricts an approval attribute to specific roles" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to create a new app secret" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:81 +#: ../settings/security/third-party/microsoft.rst:88 msgid "" -"This workflow may work best in combination with a :doc:`trigger ` but technically, this is not required." +"From **Overview** copy your apps *Application (client) ID*. If you're using " +"a single tenant app, please also copy *Directory (tenant) ID*. You now have " +"all required information for Zammad." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:84 -msgid "" -"Select fields may be a better approach because they allow more values than " -"just a simple ``true`` or ``false``." +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to retreive application client and tenant IDs" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 +#: ../settings/security/third-party/microsoft.rst:98 +msgid "Step 2 - Add App Credentials to Zammad" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:100 msgid "" -"Workflow fixes possible values of \"Approved ?\" to a specific selection " -"depending on the users role" +"Navigate to Security > Third-party Applications (Tab) within Zammad's admin " +"settings. Scroll down to the section *Authentication via Microsoft* and fill " +"in the required information." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:103 -msgid "State dependent mandatory fields" +#: ../settings/security/third-party/microsoft.rst:105 +msgid "App ID:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:93 -msgid "" -"This workflow sets ``Category`` to mandatory if the agent wants to set the " -"states ``closed`` or ``pending close`` to enforce categorization." +#: ../settings/security/third-party/microsoft.rst:105 +msgid "This is your *Application (client) ID*." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that sets fields to mandatory on specific states" +#: ../settings/security/third-party/microsoft.rst:108 +msgid "App secret:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "" -"Workflow sets category field to mandatory upon choosing closed or pending " -"close as state" +#: ../settings/security/third-party/microsoft.rst:108 +msgid "This is your *client secret* (value)." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:106 -msgid "Manual Ticket Handover Process" +#: ../settings/security/third-party/microsoft.rst:113 +msgid "App Tenant ID:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:108 -msgid "This example covers the handover of a ticket from one agent to another:" +#: ../settings/security/third-party/microsoft.rst:111 +msgid "" +"**optional** only required for apps that use account type *Accounts in this " +"organizational directory only (Default Directory only - Single tenant).*" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:110 +#: ../settings/security/third-party/microsoft.rst:115 msgid "" -"When the ticket owner is modified, a new text field (\"Handover\") shows up " -"for a comment" +"Apply your settings by pressing submit and activate *Authentication via " +"Microsoft*." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:112 +#: ../settings/security/third-party/microsoft.rst:None msgid "" -"This may only be visible when the owner is changed, therefore it has to be " -"hidden in general" +"Screencast showing how to add app credentials and activating the\n" +"authentication method" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:114 -msgid "The input in this handover text field is mandatory" +#: ../settings/security/third-party/saml.rst:2 +msgid "SAML" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:115 +#: ../settings/security/third-party/saml.rst:4 msgid "" -"After submitting changes, the value of the handover field must be added as " -"an note to the ticket (via trigger)" +"Connect your SAML (Security Assertion Markup Language) identity provider as " +"a single sign-on (SSO) method." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:121 -msgid "Hiding handover field" +#: ../settings/security/third-party/saml.rst:7 +msgid "" +"SAML is an open standard for SSO authentication (among other things). Sign-" +"ins are shared across multiple **service providers** and managed by a " +"central **identity provider** (IdP)." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Hiding the handover field in core workflows" +#: ../settings/security/third-party/saml.rst:11 +msgid "" +"In this case, the service provider is Zammad, and the IdP is a software " +"service that you either host or subscribe to (*e.g.,* `Keycloak `_, `Redhat SSO Server `_, `ADFS `_, or `Okta `_)." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:126 -msgid "Showing handover field and setting it to mandatory" +#: ../settings/security/third-party/saml.rst:18 +msgid "" +"This guide assumes you are already using SAML within your organization (i." +"e., that your IdP is fully set up)." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Showing the handover field and set it as mandatory" +#: ../settings/security/third-party/saml.rst:21 +msgid "" +"Please note: Our instructions are based on connecting Zammad with Keycloak." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:131 -msgid "Trigger writing handover input to a new article" +#: ../settings/security/third-party/saml.rst:25 +msgid "Step 1: Configure Your IdP" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Write handover content to a new article" +#: ../settings/security/third-party/saml.rst:28 +msgid "Add Zammad as a Client/App" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:133 +#: ../settings/security/third-party/saml.rst:30 msgid "" -"As a result, the ticket includes an article of the type note which includes " -"the predefined text and the handover comment." +"Import Zammad into your IdP using the XML configuration found at ``https://" +"your.zammad.domain/auth/saml/metadata``." msgstr "" -#: ../system/core-workflows/limitations.rst:6 -msgid "Core Workflows do not replace Triggers" +#: ../settings/security/third-party/saml.rst:33 +msgid "" +"If your IdP doesn't support XML import, you will have to configure Zammad as " +"a new client/app manually using the above XML metadata file for reference." msgstr "" -#: ../system/core-workflows/limitations.rst:5 +#: ../settings/security/third-party/saml.rst:36 +msgid "For instance, when you see this tag:" +msgstr "" + +#: ../settings/security/third-party/saml.rst:42 msgid "" -"Workflows manipulate the behavior of fields. However, they do not set values " -"in fields because of actions." +"Set the **Assertion Consumer Service Binding URL** (sometimes also listed as " +"**Valid Redirect URIs**) to ``http://your.zammad.domain/auth/saml/callback``." msgstr "" -#: ../system/core-workflows/limitations.rst:16 -msgid "API calls are only partly affected" +#: ../settings/security/third-party/saml.rst:47 +msgid "Set Up User Attribute Mapping" msgstr "" -#: ../system/core-workflows/limitations.rst:9 +#: ../settings/security/third-party/saml.rst:49 msgid "" -"Some options affect UI only and thus do not restrict responses and calls." +"Zammad requests the following user attributes (or “properties”) from the IdP:" msgstr "" -#: ../system/core-workflows/limitations.rst:11 -msgid "This affects the following actions:" +#: ../settings/security/third-party/saml.rst:51 +msgid "Email address (``email``)" msgstr "" -#: ../system/core-workflows/limitations.rst:13 -msgid "select" +#: ../settings/security/third-party/saml.rst:52 +msgid "Full name (``name``)" msgstr "" -#: ../system/core-workflows/limitations.rst:14 -msgid "auto select" +#: ../settings/security/third-party/saml.rst:53 +msgid "Given name (``first_name``)" msgstr "" -#: ../system/core-workflows/limitations.rst:15 -msgid "show" +#: ../settings/security/third-party/saml.rst:54 +msgid "Family name (``last_name``)" msgstr "" -#: ../system/core-workflows/limitations.rst:16 -msgid "hide" +#: ../settings/security/third-party/saml.rst:56 +msgid "" +"You may need to set up “mappers” (or “mappings”) to tell your IdP how user " +"attributes in SAML correspond to those in Zammad. For a more detailed " +"breakdown, refer to the XML metadata file referenced in the previous section." msgstr "" -#: ../system/core-workflows/limitations.rst:25 -msgid "Some fields stay unavailable to customers" +#: ../settings/security/third-party/saml.rst:62 +msgid "Per-IdP Instructions" msgstr "" -#: ../system/core-workflows/limitations.rst:19 -msgid "" -"For technical and security reasons, some default fields (the pale ones you " -"can't edit) stay unavailable for display and usage on customer permissions." +#: ../settings/security/third-party/saml.rst:102 +msgid "Keycloak" msgstr "" -#: ../system/core-workflows/limitations.rst:23 +#: ../settings/security/third-party/saml.rst:65 msgid "" -"If you require your customers to change e.g. priorities, please consider " -"using workarounds via :doc:`/system/objects` and :doc:`/manage/trigger`." +"**To add Zammad as a client,** save the XML configuration to disk (``https://" +"your.zammad.domain/auth/saml/metadata``) and use **Clients > Clients list > " +"Import client** in the Keycloak admin panel." msgstr "" -#: ../system/core-workflows/limitations.rst:29 -msgid "Ticket title changes not supported in edit mask" +#: ../settings/security/third-party/saml.rst:70 +msgid "" +"To help Zammad **match its own user accounts to Keycloak users**, create a " +"user attribute (or “property”) mapper. In **Clients list**, click on your " +"newly created Client ID, choose the tab **Client scopes** and click on the " +"link which refers to your Zammad instance. Choose **Add mapper > By " +"configuration > User Property** and create a mapper with the following " +"entries:" msgstr "" -#: ../system/core-workflows/limitations.rst:28 -msgid "" -"It is currently not possible to perform changes of the ticket title in the " -"edit mask (e.g. renaming, set to read-only)." +#: ../settings/security/third-party/saml.rst:78 +msgid "**Name**" msgstr "" -#: ../system/core-workflows/limitations.rst:37 -msgid "What is out of scope of Core Workflows?" +#: ../settings/security/third-party/saml.rst:80 +msgid "**Mapper Type**" msgstr "" -#: ../system/core-workflows/limitations.rst:32 -msgid "" -"There are some things that would count as workflow but are either done via :" -"doc:`/manage/trigger` or :doc:`/manage/scheduler`." +#: ../settings/security/third-party/saml.rst:81 +msgid "``User Property``" msgstr "" -#: ../system/core-workflows/limitations.rst:35 -msgid "Such as (but not limited to):" +#: ../settings/security/third-party/saml.rst:82 +msgid "**Property**" msgstr "" -#: ../system/core-workflows/limitations.rst:37 -msgid "up- or downgrade permissions of users" +#: ../settings/security/third-party/saml.rst:83 +msgid "``emailAddress``" msgstr "" -#: ../system/core-workflows/limitations.rst:38 -msgid "affecting article creation or listing" +#: ../settings/security/third-party/saml.rst:84 +msgid "**SAML Attribute Name**" msgstr "" -#: ../system/data-privacy.rst:2 -msgid "Data Privacy" +#: ../settings/security/third-party/saml.rst:86 +msgid "**SAML Attribute NameFormat**" msgstr "" -#: ../system/data-privacy.rst:4 -msgid "" -"For compliance with GDPR and other data privacy laws, you may wish to " -"**permanently delete users from the system**, along with **all of their " -"associated tickets**." +#: ../settings/security/third-party/saml.rst:87 +msgid "``basic``" msgstr "" -#: ../system/data-privacy.rst:8 +#: ../settings/security/third-party/saml.rst:89 msgid "" -"You can create manual deletion tasks or even automated deletion tasks for " -"tickets and users based on custom conditions via :doc:`scheduler `!" +"In the example above, we're telling Zammad that whenever it receives a SAML " +"login request, it should take the ``email`` property from Keycloak, look for " +"a Zammad user with the same ``email`` attribute, and create a new session " +"for that user." msgstr "" -#: ../system/data-privacy.rst:12 +#: ../settings/security/third-party/saml.rst:95 msgid "" -"Access to this panel requires ``admin.data_privacy`` permissions (introduced " -"in Zammad 3.5)." +"If your Keycloak users' email addresses are stored on another property (*e." +"g.,* ``username``), adjust accordingly." msgstr "" -#: ../system/data-privacy.rst:15 +#: ../settings/security/third-party/saml.rst:98 msgid "" -"On older systems that have not been updated yet, customers can also be :docs:" -"`deleted via the Zammad console `." +"Back in **Settings**, enter the Client ID (``https://your.zammad.domain/auth/" +"saml/metadata``) in the field **Master SAML Processing URL**." msgstr "" -#: ../system/data-privacy.rst:22 -msgid "User deletion dialog in the Data Privacy panel" +#: ../settings/security/third-party/saml.rst:101 +msgid "You also need to enable **Sign assertions**." msgstr "" -#: ../system/data-privacy.rst:22 -msgid "" -"The user deletion dialog lists some of the tickets that will be removed from " -"the system along with the user." +#: ../settings/security/third-party/saml.rst:105 +msgid "Step 2: Configure Zammad" msgstr "" -#: ../system/data-privacy.rst:27 -#, fuzzy -msgid "Deleting Users via GUI" -msgstr "Bloquer les notifications" +#: ../settings/security/third-party/saml.rst:107 +msgid "" +"Enable SAML and enter your IdP's details in the Admin Panel under **Settings " +"> Security > Third Party Applications > Authentication via SAML**:" +msgstr "" -#: ../system/data-privacy.rst:29 -msgid "🔥 **All deletions are FINAL!**" +#: ../settings/security/third-party/saml.rst:None +msgid "Example configuration of SAML part 1" msgstr "" -#: ../system/data-privacy.rst:31 -msgid "Once you click “Delete”, the action cannot be canceled or undone." +#: ../settings/security/third-party/saml.rst:119 +msgid "Display name" msgstr "" -#: ../system/data-privacy.rst:33 +#: ../settings/security/third-party/saml.rst:116 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." +"Allows you to define a custom button name for SAML. This helps your users to " +"understand better what the button on the login page does." msgstr "" -#: ../system/data-privacy.rst:36 -msgid "**The following records cannot be deleted:**" +#: ../settings/security/third-party/saml.rst:119 +msgid "Defaults to ``SAML``." msgstr "" -#: ../system/data-privacy.rst:38 -msgid "your own account" +#: ../settings/security/third-party/saml.rst:123 +msgid "IDP SSO target URL" msgstr "" -#: ../system/data-privacy.rst:39 -msgid "the system's last remaining administrator account" +#: ../settings/security/third-party/saml.rst:122 +msgid "" +"This is the target URL Zammad shall redirect to when the user presses the " +"SAML button. For Keycloak, this needs to look like https://your.domain/" +"realms/your-realm/protocol/saml" msgstr "" -#: ../system/data-privacy.rst:42 -msgid "Step 1: Find a User / Confirm Deletion" +#: ../settings/security/third-party/saml.rst:127 +msgid "IDP single logout target URL" msgstr "" -#: ../system/data-privacy.rst:44 -msgid "There are three ways to access the user deletion dialog:" +#: ../settings/security/third-party/saml.rst:126 +msgid "" +"This is the URL to which the single logout request and response should be " +"sent." msgstr "" -#: ../system/data-privacy.rst:51 -msgid "**from the user's profile**" +#: ../settings/security/third-party/saml.rst:131 +#, fuzzy +msgid "IDP certificate" +msgstr "Bloquer les notifications" + +#: ../settings/security/third-party/saml.rst:130 +msgid "" +"The public certificate of your IDP for Zammad to verify during the callback " +"phase." msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Accessing the user deletion dialog in a user profile" +#: ../settings/security/third-party/saml.rst:145 +msgid "IDP certificate fingerprint" msgstr "" -#: ../system/data-privacy.rst:51 -msgid "Click **Action > Delete**." +#: ../settings/security/third-party/saml.rst:134 +msgid "" +"The fingerprint of your IDPs public certificate to verify during callback " +"phase." msgstr "" -#: ../system/data-privacy.rst:58 -msgid "**in the “Manage > Users” Admin Panel**" +#: ../settings/security/third-party/saml.rst:137 +msgid "🔏 **For the IdP certificate / certificate fingerprint:**" msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Accessing the user deletion dialog under “Users” in the Admin Panel" +#: ../settings/security/third-party/saml.rst:139 +msgid "" +"Provide **only one or the other**—do not provide both! (Between the two, we " +"recommend the signing certificate itself: fingerprints use SHA-1, which `has " +"been broken for a while now `_.)" msgstr "" -#: ../system/data-privacy.rst:58 -msgid "Use the **⋮ Actions** menu for the target user." +#: ../settings/security/third-party/saml.rst:144 +msgid "" +"**Keycloak users:** Find your certificate in the Keycloak admin panel under " +"**Realm Settings > Keys > Algorithm: RS256 > Certificate**." msgstr "" -#: ../system/data-privacy.rst:66 ../system/data-privacy.rst:104 -msgid "**in the “System > Data Privacy” Admin Panel**" +#: ../settings/security/third-party/saml.rst:151 +msgid "Name identifier format" msgstr "" -#: ../system/data-privacy.rst:0 +#: ../settings/security/third-party/saml.rst:148 msgid "" -"Accessing the user deletion dialog under “Data Privacy” in the Admin Panel" +"This is the unique identifiers field type. Usually it should be ``urn:oasis:" +"names:tc:SAML:1.1:nameid-format:emailAddress``." msgstr "" -#: ../system/data-privacy.rst:65 -msgid "" -"Use the **New Deletion Task** button. Search for users by name or email " -"address." +#: ../settings/security/third-party/saml.rst:151 +msgid "Zammad **expects an email address as unique identifier**!" msgstr "" -#: ../system/data-privacy.rst:79 +#: ../settings/security/third-party/saml.rst:155 #, fuzzy -msgid "**Delete organizations**" -msgstr "Billet > Organisation > Note" +msgid "UID attribute name" +msgstr "Attributs d'article" -#: ../system/data-privacy.rst:69 +#: ../settings/security/third-party/saml.rst:154 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:" +"Here you can define an attribute that uniquely identifies the user. If " +"unset, the name identifier returned by the IDP is used." msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Deleting an organization via the user deletion dialog" +#: ../settings/security/third-party/saml.rst:None +msgid "Example configuration of SAML part 2" msgstr "" -#: ../system/data-privacy.rst:78 +#: ../settings/security/third-party/saml.rst:163 msgid "" -"If this option does not appear, make sure there are no pending deletion " -"tasks for other customers from this organization." +"Decide if the certificate for the connection to the IdP service has to be " +"verified or not (default: ``yes``)." msgstr "" -#: ../system/data-privacy.rst:82 -msgid "Step 2: Monitor Deletion Job Status" +#: ../settings/security/third-party/saml.rst:169 +msgid "Signing & Encrypting" msgstr "" -#: ../system/data-privacy.rst:84 +#: ../settings/security/third-party/saml.rst:169 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:" -msgstr "" - -#: ../system/data-privacy.rst:98 -msgid "**in the Activity Stream**" +"Define if you want to sign, encrypt, do both or nothing for the requests." msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Activity Stream showing data privacy tasks" +#: ../settings/security/third-party/saml.rst:179 +msgid "Certificate (PEM)" msgstr "" -#: ../system/data-privacy.rst:94 +#: ../settings/security/third-party/saml.rst:172 msgid "" -"For each deleted user, the Activity Stream will be updated twice—once when " -"the task is created, and once when it's complete." +"Paste the public certificate of your Zammad SAML client, if you want to " +"encrypt the requests." msgstr "" -#: ../system/data-privacy.rst:97 -msgid "" -"These notifications are only visible to users with ``admin.data_privacy`` " -"permissions." -msgstr "" +#: ../settings/security/third-party/saml.rst:175 +#, fuzzy +msgid "Make sure the certificate is:" +msgstr "Bloquer les notifications" -#: ../system/data-privacy.rst:0 -msgid "" -"The task list within Data Privacy shows removals being in progress and " -"completed." +#: ../settings/security/third-party/saml.rst:177 +msgid "already valid and not yet expired" msgstr "" -#: ../system/data-privacy.rst:107 -msgid "Frequently Asked Questions" -msgstr "" +#: ../settings/security/third-party/saml.rst:178 +#, fuzzy +msgid "no CA certificate" +msgstr "Bloquer les notifications" -#: ../system/data-privacy.rst:121 -msgid "What happens if I receive an email from a deleted customer?" +#: ../settings/security/third-party/saml.rst:179 +msgid "valid for signing and encrypting" msgstr "" -#: ../system/data-privacy.rst:110 -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." +#: ../settings/security/third-party/saml.rst:185 +msgid "Private key (PEM)" msgstr "" -#: ../system/data-privacy.rst:115 +#: ../settings/security/third-party/saml.rst:182 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**." +"Paste the private key of your Zammad SAML client here, if you want to sign " +"the requests." msgstr "" -#: ../system/data-privacy.rst:130 -msgid "What about user information stored in internal notes or other messages?" +#: ../settings/security/third-party/saml.rst:185 +msgid "Make sure the key is an RSA key with a length of at least 2048 bits." msgstr "" -#: ../system/data-privacy.rst:124 -msgid "" -"The deletion process removes **user accounts and associated tickets only**." +#: ../settings/security/third-party/saml.rst:188 +msgid "Private key secret" msgstr "" -#: ../system/data-privacy.rst:126 -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." +#: ../settings/security/third-party/saml.rst:188 +msgid "If your private key is secured with a secret, you can provide it here." msgstr "" -#: ../system/data-privacy.rst:137 -msgid "I deleted an user and can still see a message they sent!" +#: ../settings/security/third-party/saml.rst:192 +msgid "Your callback URL" msgstr "" -#: ../system/data-privacy.rst:133 +#: ../settings/security/third-party/saml.rst:191 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." -msgstr "" - -#: ../system/data-privacy.rst:141 -msgid "I removed a customer, now my reporting is off!" +"This URL is needed for your IdP configuration so it knows where to redirect " +"to after successful authentication." msgstr "" -#: ../system/data-privacy.rst:140 +#: ../settings/security/third-party/saml.rst:194 msgid "" -"When removing users and their tickets, all references are removed. This also " -"affects e.g. Reporting - these information are lost." +"After saving your input by clicking on the \"Submit\" button, Zammad " +"verifies the provided keys/certificates (e.g. if they are valid for signing/" +"encrypting and if they aren't expired)." msgstr "" -#: ../system/data-privacy.rst:145 -msgid "How long does Zammad store created tasks?" +#: ../settings/security/third-party/saml.rst:199 +msgid "" +"See :ref:`automatic account linking ` for details " +"on how to link existing Zammad accounts to IdP accounts." msgstr "" -#: ../system/data-privacy.rst:144 -msgid "" -"Please see the on-premise data section of the :docs:`data privacy ` chapter." +#: ../settings/security/third-party/saml.rst:205 +msgid "Automatic account linking doesn't work" msgstr "" -#: ../system/data-privacy.rst:150 -msgid "What about re-assigned tickets? I want to delete them, too." +#: ../settings/security/third-party/saml.rst:206 +msgid "" +"Have you double-checked your IdP's user attribute mapping configuration?" msgstr "" -#: ../system/data-privacy.rst:148 +#: ../settings/security/third-party/twitter.rst:4 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." +"It is possible to create a quick login for your helpdesk via Twitter. To do " +"so, you need to follow these steps:" msgstr "" -#: ../system/data-privacy.rst:154 -msgid "Why are there so many deletion task entries, I didn't create them!" +#: ../settings/security/third-party/twitter.rst:8 +msgid "Register Twitter App" msgstr "" -#: ../system/data-privacy.rst:153 -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." +#: ../settings/security/third-party/twitter.rst:10 +msgid "Go to https://dev.twitter.com/apps and login with your account." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:2 -msgid "Admin Panel Reference" +#: ../settings/security/third-party/twitter.rst:15 +msgid "Click on \"Create App\"" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:None -msgid "Screenshot of Checkmk settings overview" +#: ../settings/security/third-party/twitter.rst:None +msgid "new app page" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:12 +#: ../settings/security/third-party/twitter.rst:20 msgid "" -"Which :doc:`group ` should Checkmk tickets be assigned " -"to as a default (*i.e.,* when none is specified)?" +"Enter app settings. As \"Callback URL\" you need to enter ``https://" +"zammad_host/api/v1/external_credentials/twitter/callback``. You need to " +"replace ``zammad_host`` with the domain of your Zammad system." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:15 -msgid "(Applies to :ref:`API alerts ` only.)" +#: ../settings/security/third-party/twitter.rst:24 +msgid "" +"After the app has been created, update the application icon and organization " +"attributes." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:21 -msgid "Auto close" +#: ../settings/security/third-party/twitter.rst:None +msgid "set permissions to receive and send direct messages" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:18 +#: ../settings/security/third-party/twitter.rst:30 msgid "" -"Should Zammad automatically close tickets if a service has recovered on its " -"own?" +"Next we need to set ``read, write and access direct messages`` permissions " +"for the app." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:21 -msgid "(Agents will receive notifications for such closures as appropriate.)" +#: ../settings/security/third-party/twitter.rst:None +msgid "click on Keys & Access Token, note them" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:30 -msgid "Auto-close state" +#: ../settings/security/third-party/twitter.rst:36 +msgid "" +"Go to \"Keys and Access Token\" tab and note the \"Consumer Key\" and " +"\"Consumer Secret\"." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:24 -msgid "What ticket state should be applied when “auto-closing” a ticket?" +#: ../settings/security/third-party/twitter.rst:40 +msgid "Configure Zammad as Twitter App" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:26 +#: ../settings/security/third-party/twitter.rst:42 msgid "" -"You can choose from the seven built-in ticket states. If these states aren't " -"enough for you, you can :ref:`define a new ticket state ` for this purpose as well. This can be useful for tracking " -"tickets with :doc:`reports `, for example." -msgstr "" - -#: ../system/integrations/checkmk/admin-panel-reference.rst:35 -#: ../system/integrations/cti/includes/recent-logs.include.rst:2 -#: ../system/integrations/ldap/index.rst:74 -#: ../system/integrations/pgp/index.rst:106 -msgid "Recent Logs" +"Go to \"Admin > Security > Twitter > Third Party Applications > Twitter\" " +"Section." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:None -msgid "Screenshot of Checkmk \"Recent Logs\" section" +#: ../settings/security/third-party/twitter.rst:None +msgid "Admin > Security > Third Party Applications" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:41 +#: ../settings/security/third-party/twitter.rst:48 msgid "" -"If you're having trouble getting Zammad and Checkmk to play nicely together, " -"this section can help you troubleshoot." +"Fill in the \"Twitter Key\" and the \"Twitter Secret\" and click the " +"\"Submit\" button." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:44 +#: ../settings/security/third-party/twitter.rst:51 msgid "" -"It contains a record of the fifty most recent transactions that Zammad knows " -"about, including each one's request/response details and return status." +"Now you can link accounts via \"Avatar > Profile > Link Accounts\" or login " +"via Zammad login page." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:2 -msgid "API Reference" +#: ../settings/security/two-factor.rst:11 +msgid "Two-factor Authentication Methods" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:4 -msgid "" -"For most users, :ref:`the sample scripts from the Setup Guide ` will do the job just fine. But if you want more fine-grained control" -"—for instance, to create high- and low-priority tickets for different types " -"of system events—then you'll have to customize the data those scripts send " -"to Zammad." +#: ../settings/security/two-factor.rst:2 +msgid "Two-Factor Authentication" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:15 +#: ../settings/security/two-factor.rst:4 msgid "" -"This custom script will automatically set all tickets it creates to **high " -"priority** and **assign them to charlie@chrispresso.com**." +"Two-factor authentication (2FA) enhances the security of Zammad accounts by " +"adding an extra layer of verification beyond a password. It requires users " +"to provide two different types of authentication factors, typically " +"something they know (like a password) and something they possess (like a " +"mobile device or a security token), to ensure that only authorized " +"individuals can access the account." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:32 -msgid "How Does it Work?" +#: ../settings/security/two-factor.rst:19 +msgid "Enable Recovery Codes" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:34 +#: ../settings/security/two-factor.rst:21 msgid "" -"There are two kinds of data you can pass to the API, both in the form of key-" -"value pairs:" +"Recovery codes are one-time use security codes that can be used by the user " +"if they lose access to their other two-factor authentication methods. They " +"cannot be used on their own, they can only be activated if at least one two-" +"factor authentication method is enabled." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:44 -msgid "Checkmk parameters" +#: ../settings/security/two-factor.rst:None +msgid "Enable Recovery Codes Setting" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:38 +#: ../settings/security/two-factor.rst:30 msgid "" -"are required, and make up the **contents** of the resulting tickets/" -"articles. They also determine whether an event creates a new ticket or " -"updates/closes an existing one." +"Recovery codes can only be used as a backup method. If enabled, they will be " +"automatically generated for the user once they set up their initial two-" +"factor authentication method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:42 +#: ../settings/security/two-factor.rst:34 msgid "" -"These are the only values used in the sample scripts. **Use them as-is**; " -"technically, they can be customized, but it's hard to imagine a good reason " -"for it." +"The user will be asked to print out or save the generated recovery codes in " +"a safe place. Once used, a recovery code cannot be reused." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:52 -msgid "Ticket attributes" -msgstr "Attributs d'un billet" - -#: ../system/integrations/checkmk/api-reference.rst:47 +#: ../settings/security/two-factor.rst:37 msgid "" -"are optional, and can be used to **adjust settings** on newly created " -"tickets (*e.g.,* set the owner, group, priority, or state)." +"Users will also have an option to regenerate their recovery codes at any " +"time, which invalidates already existing recovery codes and provides them " +"with a list of fresh codes." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:50 +#: ../settings/security/two-factor.rst:41 msgid "" -"If you want to customize your Checkmk alert script, do it with these. Simply " -"add an extra “form” option for each one (``-F \"key=value\"``) to your " -"script's ``curl`` command line, as in the example above." +"After you enable this setting, when the user completes a setup of their " +"initial two-factor authentication method, they will be presented with a list " +"of recovery codes and instructed to save them for later use." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:54 -msgid "💡 **It's just an API endpoint!**" +#: ../settings/security/two-factor.rst:None +msgid "Recovery Codes Generation Modal Dialog" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:56 -msgid "" -"When using Checkmk integration, messages need to be formatted in a certain " -"way, but that *doesn't mean the messages actually have to come from Checkmk*." +#: ../settings/security/two-factor.rst:50 +msgid "Enforce the Set Up of the Two-Factor Authentication" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:59 +#: ../settings/security/two-factor.rst:52 msgid "" -"If you use another monitoring tool that's not officially supported by " -"Zammad, there's probably a way to make it work with your Checkmk callback " -"URL." +"In case you wish to require your users to set up at least one two-factor " +"authentication method for their account, you can do this by selecting " +"specific user roles the requirement applies to in **Enforced for user " +"roles** setting. Of course you must have at least one two-factor " +"authentication method enabled for this setting to take effect." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:63 -msgid "Checkmk Parameters" +#: ../settings/security/two-factor.rst:None +msgid "Enforced for User Roles Setting" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:65 +#: ../settings/security/two-factor.rst:62 msgid "" -"When a notification is received, Zammad creates a new article containing the " -"details of the event that triggered it:" +"After you change this setting, if the user has one of the selected roles on " +"their account, they will be forced to set up the two-factor authentication " +"upon next sign in or application reload." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:None -msgid "Checkmk article body" +#: ../settings/security/two-factor.rst:66 +msgid "" +"A modal dialog with instructions will be shown, and they will not be able to " +"do any work before they set up at least one two-factor method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:72 -msgid "" -"These details come from the fields listed below, which correspond to " -"parameters provided by Checkmk (``$NOTIFY_*``)." +#: ../settings/security/two-factor.rst:None +msgid "Modal Dialog for Enforcing Two-Factor Authentication Set Up" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:75 -msgid "**Required fields are marked with an asterisk (\\*).**" +#: ../settings/security/two-factor.rst:74 +msgid "Reset Two-Factor Authentication for a Specific User" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:79 -msgid "event_id\\*" +#: ../settings/security/two-factor.rst:76 +msgid "" +"In case an user isn't able to login anymore because of an inaccessible " +"second factor, you can reset the user's 2FA method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:78 +#: ../settings/security/two-factor.rst:79 msgid "" -"A unique ID for the system event. (``$NOTIFY_SERVICEPROBLEMID`` / " -"``$NOTIFY_HOSTPROBLEMID``)" +"To do this, go to the user management and search for the relevant user. " +"After you found the account, click the button in the action column and " +"select \"Manage Two-Factor Authentication\":" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:86 -msgid "host\\*" +#: ../settings/security/two-factor.rst:None +msgid "Context menu in action column in user management" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:82 +#: ../settings/security/two-factor.rst:87 msgid "" -"The hostname of the system that the event originated from. " -"(``$NOTIFY_HOSTNAME``)" +"After selecting this, you can see a dialog where you can either reset one " +"2FA method or reset all of the user's 2FA methods:" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:85 -msgid "" -"Used to determine if a new event belongs to an existing ticket. Also used in " -"the subject line of the resulting article (“ is ”)." +#: ../settings/security/two-factor.rst:None +msgid "Dialog for resetting user's 2FA method" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:96 -msgid "service" +#: ../settings/security/two-factor.rst:94 +msgid "" +"Choose the fitting one, click on the corresponding \"Remove ...\" button and " +"confirm your action. The user now has to setup a new 2FA method, depending " +"on your 2FA configuration." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:89 -msgid "" -"The name of the service that the event originated from. " -"(``$NOTIFY_SERVICEDESC``)" +#: ../settings/security/two-factor/authenticator-app.rst:2 +msgid "Authenticator App" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:92 -msgid "Used to determine if a new event belongs to an existing ticket." +#: ../settings/security/two-factor/authenticator-app.rst:4 +msgid "" +"The authenticator app method is a type of two-factor authentication that " +"uses a mobile application to generate one-time codes for account " +"verification. After setting up the authenticator app on their device, the " +"user links it to their Zammad account." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:94 -#: ../system/integrations/checkmk/api-reference.rst:110 -msgid "Displayed as ``-`` when omitted." +#: ../settings/security/two-factor/authenticator-app.rst:12 +msgid "" +"When logging in, the user is prompted to enter a time-sensitive code " +"generated by the app, in addition to their password. This code acts as the " +"second factor of authentication, providing an extra layer of security as it " +"changes periodically and is unique to the user's device." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:104 -msgid "state\\*" +#: ../settings/security/two-factor/authenticator-app.rst:None +msgid "Security Code in Google Authenticator App" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:99 +#: ../settings/security/two-factor/authenticator-app.rst:22 msgid "" -"The current state of the service or host in question. " -"(``$NOTIFY_SERVICESTATE`` / ``$NOTIFY_HOSTSTATE``)" +"The app generates codes based on a shared secret key stored securely on both " +"the user's device and the server, ensuring a synchronized and secure " +"authentication process. The method of generating the codes is sometimes also " +"called TOTP (time-based one-time password)." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:102 -msgid "" -"Used to detect when a ticket should be auto-closed (*i.e.,* on ``OK``/" -"``UP``). Also used in the subject line of the resulting article (“ is " -"”)." +#: ../settings/security/two-factor/authenticator-app.rst:28 +msgid "Enabling the Authenticator App Method" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:110 -msgid "text" +#: ../settings/security/two-factor/authenticator-app.rst:30 +#: ../settings/security/two-factor/security-keys.rst:28 +msgid "To enable the method, just toggle the switch on in the settings." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:107 -msgid "" -"The output of the process that triggered the event. " -"(``$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" +#: ../settings/security/two-factor/authenticator-app.rst:None +msgid "Authenticator App Switch in Settings" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:121 +#: ../settings/security/two-factor/authenticator-app.rst:36 msgid "" -"The Object Manager attribute panel displays built-in and custom\n" -"attribute names." +"Now the users will be able to set up this two-factor authentication method " +"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " +"Once they do, on next sign-in with password, they will be asked to provide " +"an additional security code generated by their mobile device." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:121 -msgid "Find a complete list of ticket attributes in the Object Manager." +#: ../settings/security/two-factor/security-keys.rst:2 +msgid "Security Keys" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:123 +#: ../settings/security/two-factor/security-keys.rst:4 msgid "" -"Ticket attributes are entirely optional, and can be used to customize the " -"tickets that Checkmk creates. (Note that these attributes will be ignored if " -"a new event belongs to an existing ticket.)" +"The security keys method is a type of a two-factor authentication that uses " +"Web Authentication API in the browser for verifying user's identity. The " +"user can register multiple hardware or software security keys with their " +"Zammad account and then they can use it during the sign-in process." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:128 +#: ../settings/security/two-factor/security-keys.rst:12 msgid "" -"Why would you want to do this? Maybe you have only one IT guy, and all " -"system monitoring issues should be automatically assigned to him. Or, maybe " -"you're creating multiple notification rules so that database outages take " -"higher priority than disk space warnings." +"When logging in, the user is prompted to provide the same security key they " +"registered with their account, in addition to their password. This key acts " +"as the second factor of authentication, providing an extra layer of security." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:135 -msgid "In most cases, you'll probably want to set one of the following:" +#: ../settings/security/two-factor/security-keys.rst:None +msgid "Security Key dialog in Safari on macOS" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:137 -msgid "group" +#: ../settings/security/two-factor/security-keys.rst:21 +msgid "" +"The type of the key can range from hardware USB sticks to passkeys stored in " +"a device of user's choice. Which type can be used depends on the browser " +"flavor and the platform of the user." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:139 -msgid "state" +#: ../settings/security/two-factor/security-keys.rst:26 +msgid "Enabling the Security Keys Method" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:140 -msgid "priority" +#: ../settings/security/two-factor/security-keys.rst:None +msgid "Security Keys Switch in Settings" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:142 +#: ../settings/security/two-factor/security-keys.rst:34 msgid "" -"but in practice, you can set almost any attribute, including :doc:`custom " -"ones you created through the Object Manager `." +"Now the users will be able to set up this two-factor authentication method " +"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " +"Once they do, on next sign-in with password, they will be asked to provide " +"the same security key they registered during the setup." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:145 -msgid "Please note that the following attributes are **not customizable**:" +#: ../settings/system/system-selfhosted.include.rst:3 +msgid "" +"Below settings are only available to self hosted users. In hosted " +"environments we're handling these settings for you to ensure service " +"stability." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:147 -msgid "title" +#: ../settings/system/base.rst:11 +msgid "Fully Qualified Domain Name" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:148 -msgid "id" +#: ../settings/system/base.rst:7 +msgid "The URL of your Zammad installation." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:149 -msgid "ticket number" +#: ../settings/system/base.rst:9 ../settings/system/base.rst:17 +msgid "This setting is used within :doc:`/misc/variables` and notifications." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:151 -msgid "created_by_id" +#: ../settings/system/system-base.include.rst:1 +msgid "It is automatically set by the *Getting Started wizard*." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:152 -msgid "updated_by_id" +#: ../settings/system/system-base.include.rst:5 +msgid "Changing this setting also changes callback URLs for your channels etc." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:155 -msgid "Which Values Can Be Set?" +#: ../settings/system/system-base.include.rst:6 +msgid "This setting can have negative affects on being able to login." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:157 -msgid "😵 **Invalid values → unpredictable behavior**" +#: ../settings/system/base.rst:19 +msgid "HTTP type" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:159 +#: ../settings/system/base.rst:14 msgid "" -"If you provide a value that Zammad doesn't understand (*e.g.,* ``-F " -"\"priority=high\"``), it's not always clear what will happen. In some cases, " -"a ticket will be created with the default values instead - but in others, it " -"may not be created at all!" +"The HTTP type tells your installation how your clients connect. This is " +"relevant for authentication and cookie security." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:164 -msgid "So what values does Zammad understand, then? Well, it depends..." +#: ../settings/system/base.rst:31 +msgid "SystemID" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:168 -msgid "Use an email address or username:" +#: ../settings/system/base.rst:22 +msgid "" +"This ID is being used within your ticket number. In case you're " +"communicating with another ticket system with similar ticket number schemes " +"this ID greatly reduces the risk of false follow ups." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:190 -msgid "group & priority" +#: ../settings/system/base.rst:26 +msgid "" +"The SystemID is randomly selected upon installation of Zammad (``1-99``)." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:175 -msgid "Refer to the dropdown menus in the ticket pane:" +#: ../settings/system/base.rst:30 +msgid "" +"**Do not** change this setting in a productive system! Your Zammad " +"installation may no longer recognize old ticket number based follow ups upon " +"change!" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:0 -msgid "See possible values for certain attributes in the ticket pane." +#: ../settings/system/frontend.rst:2 +msgid "Frontend" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:187 -msgid "🙅 **Ticket state CANNOT be set this way!**" +#: ../settings/system/frontend.rst:22 +msgid "Core Workflow Ajax Mode" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:189 +#: ../settings/system/frontend.rst:6 msgid "" -"Why? Because ``-F \"state=...\"`` is already used :ref:`as a Checkmk " -"parameter `." +"This setting allows administrators to enforce :doc:`/system/core-workflows` " +"to use Ajax-Calls instead of web sockets. You'll usually only need this if " +"you experience serious issues as noted below." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:222 -msgid "Everything Else" +#: ../settings/system/frontend.rst:10 +msgid "**🤓 Possible (technical) reasons**" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:193 +#: ../settings/system/frontend.rst:12 msgid "" -"To set any other attributes, it helps to know your way around the :docs:" -"`rails console `. Valid values are those that you can " -"set with a string:" +"In some cases, your network structure (e.g. firewalls, proxies) may " +"disconnect long web socket connections. This leads to select fields staying " +"empty (e.g. owner selection *after* selecting your group) or fields not " +"shown / hidden (e.g. when switching to or from pending states, the \"pending " +"till\" field not showing / hiding)." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:218 -msgid "These values can then be passed directly to the API:" +#: ../settings/system/frontend.rst:18 +msgid "" +"Please keep in mind that the Ajax fallback may cause serious pressure on " +"your application server. If you have the choice stick to web sockets." msgstr "" -#: ../system/integrations/checkmk/index.rst:16 -msgid "How does it work?" +#: ../settings/system/frontend.rst:22 +msgid "Default: ``no`` (inactive)" msgstr "" -#: ../system/integrations/checkmk/index.rst:2 -msgid "Checkmk" +#: ../settings/system/frontend.rst:53 +msgid "Show calendar weeks in the picker of date/datetime fields" msgstr "" -#: ../system/integrations/checkmk/index.rst:4 +#: ../settings/system/frontend.rst:25 msgid "" -"`Checkmk `_ is a powerful IT monitoring tool that can " -"send real-time status alerts to Zammad via email or REST API. Set these " -"alerts up in Checkmk, and Zammad will automatically create, update, and " -"close tickets based on the health of your system:" +"With this setting you can instruct Zammad to provide week number display " +"globally for all users. Calendar with week number display are usually used " +"in business sectors and may not be relevant for everyone." +msgstr "" + +#: ../settings/system/frontend.rst:29 +msgid "" +"This setting affects *all areas* - you'll also see week numbers in the admin " +"panel for e.g. triggers and macros." +msgstr "" + +#: ../settings/system/frontend.rst:32 +msgid "Default: ``no`` (not shown)" msgstr "" -#: ../system/integrations/checkmk/index.rst:14 -msgid "Screenshot of ticket created by Checkmk notifications" +#: ../settings/system/frontend.rst:53 +msgid "Here's the difference:" msgstr "" -#: ../system/integrations/checkmk/index.rst:14 -msgid "Multiple alerts, same ticket." +#: ../settings/system/frontend.rst:0 +msgid "Screenshot showing Zammad's date picker (in the default way)" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:2 -msgid "Setup Guide" -msgstr "" +#: ../settings/system/frontend.rst:41 +#, fuzzy +msgid "Set to ``no``" +msgstr "Option réglée sur ``no``" -#: ../system/integrations/checkmk/setup-guide.rst:4 +#: ../settings/system/frontend.rst:0 msgid "" -"Whenever the Checkmk integration is enabled, Zammad listens for messages on " -"its API and over email. As long as those messages follow the required " -"format, Zammad will create new tickets (or find and update existing ones) " -"based on the message contents." +"Screenshot showing Zammad's date picker with\n" +"week numbers enabled" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:10 +#: ../settings/system/frontend.rst:50 +#, fuzzy +msgid "Set to ``yes``" +msgstr "Option réglée sur ``yes``" + +#: ../settings/system/index.rst:4 msgid "" -"That means that “setting up Checkmk integration” is simply a matter of " -"**adding configuration to your Checkmk site**: telling it when to send these " -"messages and what to say. To do that, you'll need to create a new " -"**notification rule** (see `Checkmk's official docs `_ for help with that)." +"For your overview we split each tab within system settings into its own page:" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:17 +#: ../settings/system/index.rst:16 +#, fuzzy +msgid "Console Based Settings" +msgstr "Réglages avancés" + +#: ../settings/system/index.rst:18 msgid "" -"As part of this new rule, you'll have to choose a **notification method** " -"(*i.e.,* a script to execute whenever the rule is triggered). This script " -"will be written by you (samples below), and contain the logic for sending " -"API/email messages to Zammad:" +"There's some console based settings we didn't put into the UI. However, you " +"may find them helpful - you can find them in our :docs:`hidden settings ` section." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:26 -msgid "Checkmk \"New Rule\" dialog" +#: ../settings/system/network.rst:2 +msgid "Network" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:26 +#: ../settings/system/network.rst:8 msgid "" -"Find your custom scripts in the Checkmk WATO under **Notifications > New " -"Rule > Notification Method**." +"The proxy settings can only be saved after successfully testing the proxy " +"connection." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:29 -msgid "" -"Once you're done setting up your new rule, you're all set! New tickets " -"should start coming in and auto-updating any time your rule is triggered." +#: ../settings/system/network.rst:15 +msgid "Proxy Address." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:33 +#: ../settings/system/network.rst:12 msgid "" -"(If you need help troubleshooting, be sure to check the :ref:`checkmk-recent-" -"logs`.)" +"Allows you to provide a proxy server if needed. This is relevant for network " +"communication by Zammad." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:38 -msgid "API Alerts" +#: ../settings/system/network.rst:15 +msgid "It **does not** affect the update process or Elasticsearch." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:40 +#: ../settings/system/network.rst:18 +msgid "Username for proxy connection." +msgstr "" + +#: ../settings/system/network.rst:18 msgid "" -"To add these scripts in the Checkmk WATO, copy them into your Checkmk " -"installation directory and make them executable. (Be sure to replace the " -"``zammad.example.com`` callback URL with the one found in your admin panel.)" +"If your proxy server requires authentication, provide the username here." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:60 -msgid "Service notification" +#: ../settings/system/network.rst:21 +msgid "Password for proxy connection." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:46 +#: ../settings/system/network.rst:21 msgid "" -"For updates on the status of the software running on your server (*e.g.,* " -"postgres)." +"If your proxy server requires authentication, provide the password here." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:75 -msgid "Host notification" +#: ../settings/system/network.rst:26 +msgid "No proxy for the following hosts." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:63 -msgid "For updates on the status of the server itself." +#: ../settings/system/network.rst:24 +msgid "" +"Exception list for hosts you can't or don't want to reach via proxy server." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:77 -msgid "🤔 **What's with all the env vars?**" +#: ../settings/system/network.rst:27 +msgid "Default: ``localhost,127.0.0.0,::1``" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:79 -msgid "" -"Whenever Checkmk runs these scripts, it needs to provide some information " -"about the event that triggered the notification. This information is passed " -"in the form of these ``$NOTIFY_*`` environment variables." +#: ../settings/system/services.rst:2 +msgid "Services" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:85 -msgid "" -"You can specify additional parameters to pass to the script when you're " -"setting up your notification rule, but the ones you see here are all " -"provided by default." +#: ../settings/system/services.rst:10 +msgid "Image Service" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:90 -msgid "Email Alerts" +#: ../settings/system/services.rst:5 +msgid "Defines the backend for user and organization image lookups." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:94 -msgid "" -"🐞 **There are known bugs** in Zammad's processing of email from Checkmk. " -"This section will be completed once they have been resolved. (Learn more at " -"GitHub issues `#2377 `_ & " -"`#2180 `_.)" +#: ../settings/system/services.rst:7 +msgid "Default: ``Zammad Image Service`` (active)" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:100 -msgid "In the meantime, we encourage you to set up API alerts instead." +#: ../settings/system/services.rst:9 +msgid "" +"Make sure your on premise installation has ``HTTPS`` access to ``images." +"zammad.com``." msgstr "" -#: ../system/integrations/clearbit.rst:2 -msgid "Clearbit" +#: ../settings/system/services.rst:18 +msgid "Geo Calendar Service" msgstr "" -#: ../system/integrations/clearbit.rst:4 +#: ../settings/system/services.rst:13 msgid "" -"With our Clearbit integration, you can easily enrich the information " -"provided by Zammad. If the customers or agents email address is known to " -"Clearbit, it will share all information it has regarding the user with " -"Zammad. Those information can include the following:" +"Defines the backend for geo calendar lookups. Used for initial calendar " +"setup." msgstr "" -#: ../system/integrations/clearbit.rst:9 -msgid "Avatar" +#: ../settings/system/services.rst:16 +msgid "Default: ``Zammad GeoCalendar Service`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:10 -msgid "Address information" +#: ../settings/system/services.include.rst:2 +msgid "" +"Make sure your on premise installation has ``HTTPS`` access to ``geo.zammad." +"com``." msgstr "" -#: ../system/integrations/clearbit.rst:11 -msgid "Website information" +#: ../settings/system/services.rst:26 +msgid "Geo IP Service" msgstr "" -#: ../system/integrations/clearbit.rst:12 -msgid "A BIO (as Note by default)" +#: ../settings/system/services.rst:21 +msgid "" +"Defines the backend for geo IP lookups. Shows also location of an IP address " +"if an IP address is shown." msgstr "" -#: ../system/integrations/clearbit.rst:14 -msgid "" -"If needed, you can add further custom objects and add mappings to them, so " -"the Clearbit information can be filled within the database. In general you " -"can get any information from Clearbit, as long as you have a mapping to an " -"Zammad object." +#: ../settings/system/services.rst:24 +msgid "Default: ``Zammad GeoIP Service`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:21 -msgid "" -"Clearbit does have a mapping of fields like LDAP and Exchange have, but does " -"not \"win\" against Zammad information. This means that if you have e.g. the " -"last name field filled in already and Clearbit has other information on " -"that, it will not be updated." +#: ../settings/system/services.rst:32 +msgid "Geo Location Service" msgstr "" -#: ../system/integrations/clearbit.rst:26 +#: ../settings/system/services.rst:29 msgid "" -"However: If let's say the last name has been set by Clearbit and Zammad " -"notices that the last name on the Clearbit source has changed, Zammad will " -"also update this value." +"Defines the backend for geo location lookups to store geo locations for " +"addresses." msgstr "" -#: ../system/integrations/clearbit.rst:33 +#: ../settings/system/services.rst:32 msgid "" -"The configuration of Clearbit is really easy and done fast! Just login to " -"your Clearbit-Account, go to \"API\" and copy the secret-API-Key." +"Default: ``OpenStreetMap (ODbL 1.0, http://osm.org/copyright)`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:38 +#: ../settings/system/services.rst:36 msgid "" -"Now change to your Zammad instance, go to Integrations (System) -> Clearbit " -"in the admin panel. Paste your API-Key into the API-Key-Field and decide if " -"Zammad should create unknown Organizations automatically, if the user does " -"not have one yet (and Clearbit knows it). The shared option decides if the " -"new organizations Zammad creates with Clearbit should be shared ones." +"You can find a detailed privacy information on what we store for how long on " +"our :docs:`Privacy Appendix ` inside of our System " +"Documentation." msgstr "" -#: ../system/integrations/clearbit.rst:47 -msgid "" -"If you're unsure what option to choose, better stick with \"no\". You can " -"also learn more about :doc:`/manage/organizations/index`." +#: ../settings/system/storage.rst:2 +msgid "Storage" msgstr "" -#: ../system/integrations/clearbit.rst:52 +#: ../settings/system/storage.rst:6 msgid "" -"The Mapping option works similar to the mapping within the Exchange and LDAP " -"sync. You can add further mappings for e.g. custom fields if you need more " -"information that Clearbit can provide." +"Here you can define where Zammad stores attachments for tickets and the " +"knowledge base. By default, we're writing to the ``Database`` - you can " +"switch to ``Filesystem`` or ``Simple Storage (S3)`` at any time. In this " +"case please have a look on the following instructions." msgstr "" -#: ../system/integrations/clearbit.rst:58 +#: ../settings/system/storage.rst:11 msgid "" -"If you want to add more Clearbit fields and want to learn more about " -"available fields on their API, you can take a look at their `API " -"documentation `_." +"If you have a busy Zammad instance, we strongly encourage you to use " +"filesystem storage instead of \"Database\". This will greatly improve system " +"performance (de-crease database load and size)." msgstr "" -#: ../system/integrations/clearbit.rst:62 -msgid "" -"If you're happy with the above chosen Settings and your mapping, just save " -"the changes and enable Clearbit integration. Zammad will now start polling " -"the Clearbit API as users contact you." +#: ../settings/system/storage.rst:19 +msgid "Database" msgstr "" -#: ../system/integrations/clearbit.rst:68 +#: ../settings/system/storage.rst:17 msgid "" -"Zammad does not synchronize with Clearbit on a regular basis, but on demand " -"if needed. This saves API calls." +"This is the default storage method. The attachments are stored directly in " +"the database. If your Zammad instance grows, we recommend one of the other " +"methods to maintain performance." msgstr "" -#: ../system/integrations/clearbit.rst:73 +#: ../settings/system/storage.rst:38 +msgid "Filesystem" +msgstr "" + +#: ../settings/system/storage.rst:22 msgid "" -"Below the Settings and Mappings, you'll find our Integration log. You can " -"see what requests Zammad sent to Clearbit and also the APIs Response." +"This storage method is recommended for all Zammad instances, especially for " +"those with a higher load. If you choose filesystem, your files are written " +"to ``/opt/zammad/storage/``." msgstr "" -#: ../system/integrations/clearbit.rst:78 +#: ../settings/system/storage.rst:26 msgid "" -"By the way, you can also view the API log on the Clearbit website - the " -"information seen is basically the same." +"Moving attachments from \"Database\" to \"Filesystem\" can be run during " +"production use. However, you should consider your framework conditions (e.g. " +"bandwidth, system load in production) to define the right moment." msgstr "" -#: ../system/integrations/clearbit.rst:84 -msgid "Example When Adding a User" +#: ../settings/system/storage.rst:32 +msgid "**You noticed slow updates of Zammad?**" msgstr "" -#: ../system/integrations/clearbit.rst:86 +#: ../settings/system/storage.rst:34 msgid "" -"To show you how fast information is added, we added a small Screencast " -"below. This shows the creation of the User Alex from Clearbit. As we already " -"set the last name of Alex to \"X\", Zammad did not update it. What Zammad " -"did was to add further information it received from Clearbit." +"While Zammad is beeing updated, it enforces a recursive \"change " +"owner\" (chown) for this directory. For instances with many files this can " +"be time consuming. To mitigate that you can move your files and create a " +"symlink in ``/opt/zammad/storage/`` to the new directory. Of course you have " +"to make sure on your own that the permissions are always correct." msgstr "" -#: ../system/integrations/cti/generic.rst:2 -msgid "CTI (generic)" +#: ../settings/system/storage.rst:95 +msgid "Simple Storage (S3)" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:1 +#: ../settings/system/storage.rst:41 msgid "" -"This integration enables Zammad to provide a caller log to your agents. With " -"this your agents can greet your customers by their name and are supported by " -"Zammad with automatically opening a new ticket dialog or the user profile." +"To use the Simple Storage (S3), you have to provide some settings, which " +"can't be accessed in the UI (see instructions below)." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:6 +#: ../settings/system/storage.rst:44 msgid "" -"Click the toggle next to the heading to activate or deactivate this " -"integration." +"⚠️ Please note that the current implementation is in its early stages and can " +"be modified in the future." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:9 +#: ../settings/system/storage.rst:47 msgid "" -"If you want to learn more on how your agents can use this function, please " -"refer the :user-docs:`user documentation `." +"The prerequisite is to have access to a S3-compatible storage and to have " +"all necessary parameters available (which depends on your storage provider; " +"if in doubt, please ask there for help)." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:14 +#: ../settings/system/storage.rst:51 +msgid "Steps to configure S3:" +msgstr "" + +#: ../settings/system/storage.rst:53 msgid "" -"Automatically opening new ticket dialogues or user profiles requires agent " -"to extension mapping - see more below." +"Copy ``config/zammad/storage.yml.dist`` to ``config/zammad/storage.yml``" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:20 -msgid "Please note the following limitations to reduce confusion later on:" +#: ../settings/system/storage.rst:54 +msgid "Edit the copied file in one of the following ways:" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:22 -msgid "CTI integrations provide caller log functions only." +#: ../settings/system/storage.rst:56 +msgid "" +"Either provide your S3 configuration with one attribute per line like in the " +"upper area of the file" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:23 +#: ../settings/system/storage.rst:58 msgid "" -"This integration does not provide any VoIP functionalities; you can't make " -"phone calls from within Zammad." +"Or provide your S3 configuration as an URL (which you can find at the end of " +"the file). Note: you can also provide this URL as environment variable (:" +"docs:`see system documentation `) without using this yml-file." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:25 +#: ../settings/system/storage.rst:62 msgid "" -"If your browser supports ``tel``-URLs, you can click on phone numbers for " -"automatic dialing. This requires additional software / configuration on your " -"agent's computers." +"We recommend the deletion of the not used configuration style to avoid " +"inconsistencies." msgstr "" -#: ../system/integrations/cti/generic.rst:9 -#: ../system/integrations/cti/placetel.rst:14 -#: ../system/integrations/cti/sipgate.rst:14 -msgid "Please provide the following requirements:" +#: ../settings/system/storage.rst:65 +msgid "Restart Zammad so the config file / environment variable is loaded" msgstr "" -#: ../system/integrations/cti/generic.rst:11 +#: ../settings/system/storage.rst:66 msgid "" -"A telephone system that supports webhooks (outbound) (best option are those " -"that allow customizing the calls)." +"Set the \"Storage Method\" in Zammad to ``Simple Storage (S3)`` in Settings " +"> System > Storage and click on \"Submit\". After that, Zammad checks your " +"configuration and the connection to the service and will raise an error " +"message if something is wrong." msgstr "" -#: ../system/integrations/cti/generic.rst:13 -msgid "A unique Call-ID during the call session." +#: ../settings/system/storage.rst:72 +msgid "A very simple storage configuration could look like this:" msgstr "" -#: ../system/integrations/cti/generic.rst:14 -msgid "Call event data (both numbers and direction)." +#: ../settings/system/storage.rst:85 +msgid "" +"Before setting the storage method to ``Simple Storage (S3)`` (step 4), " +"please make sure to have a working setup." msgstr "" -#: ../system/integrations/cti/generic.rst:15 -msgid "Your Zammad instance must be reachable for your telephony system." +#: ../settings/system/storage.rst:88 +msgid "" +"You can verify this by running ``rails r 'Rails.logger = Logger.new(STDOUT); " +"pp Store::Provider::S3.ping?'`` in your Zammad directory. If everything is " +"fine, you should see ``true``, else you should see ``false`` and a simple " +"error message." msgstr "" -#: ../system/integrations/cti/generic.rst:17 +#: ../settings/system/storage.rst:93 msgid "" -"If you want to learn more on what kind of requests are supported by Zammad " -"and what it expects, please consult our :docs:`CTI-API documentation `." +"If you installed Zammad through a package manager (rather than from source), " +"replace ``rails r`` with ``zammad run rails r`` above. To learn more, see :" +"docs:`Administration via Console `." msgstr "" -#: ../system/integrations/cti/generic.rst:22 -#: ../system/integrations/cti/placetel.rst:27 -#: ../system/integrations/cti/sipgate.rst:30 -#, fuzzy -msgid "Available Settings" -msgstr "Réglages avancés" - -#: ../system/integrations/cti/generic.rst:29 -#: ../system/integrations/cti/placetel.rst:41 -#: ../system/integrations/cti/sipgate.rst:40 +#: ../settings/ticket.rst:4 #, fuzzy -msgid "Endpoint Settings" -msgstr "Liste des réglages" - -#: ../system/integrations/cti/generic.rst:25 msgid "" -"Zammad will list your generic CTI endpoint here. It contains a unique token " -"so ensure to keep this URL save." +"Here you can adjust general ticket settings. Additional ones for the ticket " +"composer interface can be found in the :doc:`/misc/composer`." msgstr "" +"Des paramètres supplémentaires pour l'interface du compositeur de billets " +"peuvent être trouvés dans :doc:`/misc/composer`." -#: ../system/integrations/cti/generic.rst:28 +#: ../settings/ticket.rst:11 +msgid "Ticket Hook (default: ``Ticket#``)" +msgstr "Crochet d'intégration du billet (default: ``Ticket#``)" + +#: ../settings/ticket.rst:11 +msgid "The identifier for a ticket; *e.g.,* Ticket#, Call#, MyTicket#." +msgstr "L'identifiant d'un billet; *par exemple:* Ticket#, Call#, MyTicket#." + +#: ../settings/ticket.rst:38 +msgid "Ticket Hook Position (default: ``right``)" +msgstr "Position du crochet d'intégration du billet (default: ``right``)" + +#: ../settings/ticket.rst:14 msgid "" -"You'll need this endpoint for your PBX to talk to Zammad, see :docs:`CTI-API " -"documentation `." +"With this setting you can decide (if) where to insert the ticket number." msgstr "" +"Avec ce paramètre, vous pouvez décider (si) où insérer le numéro de billet." -#: ../system/integrations/cti/includes/important-dont-forget-saving.include.rst:3 +#: ../settings/ticket.rst:20 +msgid "*Right*" +msgstr "*Droit*" + +#: ../settings/ticket.rst:17 msgid "" -"All following options **do not save automatically**. Always use the Save " -"button on the lower end of the integration page!" -msgstr "" +"This setting will add the ticket reference on the right site of the subject." +msgstr "Ce paramètre ajoutera la référence du billet à la droite du sujet." -#: ../system/integrations/cti/generic.rst:43 -#: ../system/integrations/cti/placetel.rst:49 -#: ../system/integrations/cti/sipgate.rst:52 -#, fuzzy -msgid "Call Settings" -msgstr "Réglages" +#: ../settings/ticket.rst:20 +msgid "Example: ``Some Subject [Ticket#12345]``" +msgstr "Exemple: ``Votre billet [Ticket #: 12345]``" -#: ../system/integrations/cti/generic.rst:39 -#: ../system/integrations/cti/placetel.rst:49 -#: ../system/integrations/cti/sipgate.rst:37 -#: ../system/integrations/cti/sipgate.rst:50 -msgid "Inbound" -msgstr "" +#: ../settings/ticket.rst:26 +msgid "*Left*" +msgstr "*Gauche*" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:1 +#: ../settings/ticket.rst:23 msgid "" -"This option allows you to block specific incoming caller IDs. It allows you " -"to temporarily reject e.g. spam callers without having to contact providers " -"or PBX administrators." -msgstr "" +"This setting will add the ticket reference on the left site of the subject." +msgstr "Ce paramètre ajoutera la référence du billet à la gauche du sujet." -#: ../system/integrations/cti/includes/inbound-calls.include.rst:11 -msgid "Caller ID to block" -msgstr "" +#: ../settings/ticket.rst:26 +msgid "Example: ``[Ticket#12345] Some Subject``" +msgstr "Exemple: ``[Ticket #: 12345] Votre billet``" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 -msgid "Provide caller IDs to block in ``E.164`` format." -msgstr "" +#: ../settings/ticket.rst:29 +msgid "*None*" +msgstr "*Aucun*" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:8 +#: ../settings/ticket.rst:29 +msgid "This will completely remove ticket references from the subject." +msgstr "Ceci supprimera complètement les références du billet du sujet." + +#: ../settings/ticket.rst:33 msgid "" -"Your telephony system has to support this function. Zammad will send a " -"``reject`` response which will cause your telephony system to hang up the " -"call. To callers this usually will feel like the line is busy." +"Please ensure to take a look at :doc:`/channels/email/settings` within the " +"email channel to ensure you have at least one reference that helps Zammad to " +"assign follow-ups correctly." msgstr "" +"Veuillez vous assurer de consulter :doc:`/channels/email/settings` dans le " +"canal de messagerie pour vous assurer d'avoir au moins une référence qui " +"aide Zammad à affecter correctement les suivis." -#: ../system/integrations/cti/includes/inbound-calls.include.rst:14 +#: ../settings/ticket.rst:37 msgid "" -"Provide a meaningful note for your fellow administrators to remind yourself " -"why you've chosen to block the number." +"Disabling this and not setting up any further follow up search will lead to " +"unexpected results!" msgstr "" +"Désactiver ceci et ne pas configurer de recherche de suivi supplémentaire " +"entraînera des résultats inattendus!" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 -#: ../system/integrations/cti/includes/outbound-calls.include.rst:17 -#: ../system/integrations/cti/sipgate.rst:40 -msgid "Outbound" +#: ../settings/ticket.rst:65 +#, fuzzy +msgid "" +"Ticket Last Contact Behaviour (default: ``Use the start time of the last " +"customer thread (which may consist of multiple articles).``)" msgstr "" +"Comportement du dernier contact du billet (par défaut: ``Dernier contact " +"client (avec la considération qu'un agent y ait répondu)``)" -#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:1 +#: ../settings/ticket.rst:41 msgid "" -"In many cases you may want to use a different caller ID depending on the " -"destination you're calling. This may apply due to specific connection rates " -"to other countries or because you want your customer to feel you're calling " -"from the same country." +"This setting changes the way Zammad updates the ``Last Contact`` value of a " +"ticket. This is fairly important for overviews and what you expect upon " +"ticket updates of a customer." msgstr "" +"Ce paramètre modifie la façon dont Zammad met à jour la valeur ``Dernier " +"contact`` d'un billet. Ceci est assez important pour les aperçus et ce que " +"vous attendez des mises à jour des billets d'un client." -#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:6 -msgid "This option expects ``E.164`` number formats." +#: ../settings/ticket.rst:52 +msgid "" +"Use the start time of the last customer thread (which may consist of " +"multiple articles)." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 -msgid "Destination caller ID" +#: ../settings/ticket.rst:46 +msgid "" +"If this option is chosen, Zammad will update the last updated value just " +"once if a customer replies. After that, Zammad will wait for an agent to " +"react." msgstr "" +"Si cette option est choisie, Zammad mettra à jour la dernière valeur mise à " +"jour une seule fois, si un client répond. Ensuite, Zammad attendra qu'un " +"agent réagisse." -#: ../system/integrations/cti/includes/outbound-calls.include.rst:5 -msgid "The caller ID or number you're trying to call." +#: ../settings/ticket.rst:50 +#, fuzzy +msgid "" +"This comes in handy if you want to work tickets in the order of their first " +"update. This will not change ticket orders if customers decide to \"bump\" " +"the ticket affected." msgstr "" +"Ceci est pratique si vous souhaitez travailler sur les billets dans l'ordre " +"de leur première mise à jour. Cela ne changera pas l'ordre des billets si " +"les clients décident de \"bumper\" le billet concerné." -#: ../system/integrations/cti/includes/outbound-calls.include.rst:7 -msgid "You can use wildcards for e.g. country specific outbound numbers like:" +#: ../settings/ticket.rst:57 +msgid "Use the time of the very last customer article." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:9 -msgid "``49*`` for Germany" +#: ../settings/ticket.rst:55 +msgid "" +"When setting this option, Zammad will always update the last updated value. " +"This means that if ordering by ``Last Update``, ticket orders will change if " +"customers \"bump\" the ticket." msgstr "" +"Lors de la définition de cette option, Zammad mettra toujours à jour la " +"dernière valeur mise à jour. Cela signifie que si vous ordonnancez par " +"``Dernière mise à jour``, l'ordre des billets changera si les clients " +"\"bumpent\" le billet." -#: ../system/integrations/cti/includes/outbound-calls.include.rst:10 -msgid "``4930*`` for Berlin / Germany landlines" -msgstr "" +#: ../settings/ticket.rst:64 +msgid "Last contact value used on :doc:`/manage/overviews`" +msgstr "Dernière valeur de contact utilisée à :doc:`/manage/overviews`" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 -msgid "``33*`` for France" -msgstr "" +#: ../settings/ticket.rst:65 +msgid "Last contact value used on :doc:`/manage/trigger`" +msgstr "Dernière valeur de contact utilisée à :doc:`/manage/trigger`" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:15 -msgid "Set Outbound caller ID" +#: ../settings/ticket.rst:88 +msgid "" +"Ticket Organization Reassignment (default: ``Update the most recent tickets." +"``)" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:14 +#: ../settings/ticket.rst:68 msgid "" -"The outbound caller ID to set (the number your customer sees on his display) " -"in ``E.164`` number format." +"This setting changes the way Zammad updates the organization field of the " +"tickets whenever the primary organization of a user is changed." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 -msgid "Provide a short description for fellow administrators." +#: ../settings/ticket.rst:74 +msgid "Update the most recent tickets." msgstr "" -#: ../system/integrations/cti/includes/generic-cti-support-note.includes.rst:3 +#: ../settings/ticket.rst:72 msgid "" -"This option requires your PBX to send a specific request to Zammad *before " -"dialing*. Please consult the :docs:`CTI API ` in case " -"you're not sure." +"If this option is chosen, Zammad will update the 100 most recent tickets " +"where the user is the ticket customer. The ticket organization field will be " +"automatically set to the new primary organization of the user." msgstr "" -#: ../system/integrations/cti/generic.rst:52 -#: ../system/integrations/cti/placetel.rst:54 -#: ../system/integrations/cti/sipgate.rst:59 -#, fuzzy -msgid "Other Settings" -msgstr "Réglages" +#: ../settings/ticket.rst:88 +msgid "Do not update any tickets." +msgstr "" -#: ../system/integrations/cti/includes/other-settings-intro.include.rst:1 +#: ../settings/ticket.rst:77 msgid "" -"Below you can find all available additional settings for this CTI " -"integration. For your overview we're sorting them by appearance and " -"reference their description first." +"When choosing this option, Zammad will not update any tickets when the " +"user's primary organization is changed." msgstr "" -#: ../system/integrations/cti/includes/default-caller-id.include.rst:2 -#: ../system/integrations/cti/includes/default-caller-id.include.rst:1 -msgid "Default caller ID for outbound calls" +#: ../settings/ticket.rst:80 +msgid "**Use with care!**" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:16 -#: ../system/integrations/cti/includes/records-caller-log.include.rst:15 -msgid "Shown records in caller log" +#: ../settings/ticket.rst:82 +msgid "" +"Using this option may lead to inconsistencies in the system as the ticket " +"organization may become decoupled from the ticket customer." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:2 +#: ../settings/ticket.rst:85 msgid "" -"Allows you to set the number of shown caller log entries for all users. You " -"can choose from the following values:" +"However, you may use this option if you wish to maintain :ref:`the shared " +"access ` to the ticket for all organization " +"members of the original organization of the customer." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:5 -msgid "60 (default)" +#: ../settings/ticket.rst:110 +msgid "Ticket Number Format (default: ``Increment (SystemID.Counter)``)" msgstr "" +"Format du numéro de billet (par défaut: ``Increment (SystemID.Counter)``)" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:6 -msgid "120" +#: ../settings/ticket.rst:94 +#, fuzzy +msgid "" +"This setting defines the way Zammad's ticket number will look. Changing this " +"setting in production will cause follow up detection to fail." msgstr "" +"Ce paramètre définit l'apparence du numéro de billet de Zammad. La " +"modification de ce paramètre en production entraînera l'échec de la " +"détection de suivi." -#: ../system/integrations/cti/includes/records-caller-log.include.rst:7 -msgid "180" -msgstr "" +#: ../settings/ticket.rst:102 +msgid "Increment (SystemID.Counter)" +msgstr "Incrémentation (SystemID.Counter)" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:8 -msgid "240" +#: ../settings/ticket.rst:98 +msgid "" +"The increment value contains the SystemID (automatically generated during " +"installation) and a increment which counts up with every new Ticket. The " +"increment will automatically get another digit if needed." msgstr "" +"La valeur d'incrémentation contient le \"SystemID\" (généré automatiquement " +"lors de l'installation) et un incrément qui est ajouté à chaque nouveau " +"billet. Le résultat obtiendra automatiquement un chiffre significateur " +"suppémentaire si nécessaire." -#: ../system/integrations/cti/includes/records-caller-log.include.rst:9 -msgid "300" -msgstr "" +#: ../settings/ticket.rst:102 +msgid "Examples: ``1010138``, ``1010139``" +msgstr "Exemples: ``1010138``, ``1010139``" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:11 -msgid "**🥵 Potential performance issue**" -msgstr "" +#: ../settings/ticket.rst:110 +msgid "Date (Year.Month.Day.SystemID.Counter)" +msgstr "Date (Année.Mois.Jour.SystemID.Counter)" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:13 +#: ../settings/ticket.rst:105 msgid "" -"Setting this setting higher than 60 may cause serious performance issues on " -"very busy instances. Keep in mind that this setting causes Zammad to poll " -"and send up to 300 records to *all active agent sessions* in very short time " -"periods." +"This version of the ticket number is fairly long. However, because it " +"contains the date of ticket creation, it also allows you to see when the " +"ticket has been created. You may feel familiar with this number format if " +"you've worked with OTRS already." msgstr "" +"Cette version du numéro de billet est assez longue. Cependant, parce qu'il " +"contient la date de création du billet, il vous permet également de voir " +"quand le billet a été créé. Vous pouvez vous sentir familier avec ce format " +"de nombre si vous avez déjà travaillé avec OTRS." -#: ../system/integrations/cti/generic.rst:73 -msgid "Caller Log Filter" -msgstr "" +#: ../settings/ticket.rst:110 +msgid "Examples: ``201206231010138``, ``201206231010139``" +msgstr "Exemples: ``201206231010138``, ``201206231010139``" -#: ../system/integrations/cti/generic.rst:55 +#: ../settings/ticket.rst:137 +msgid "OPTIONS" +msgstr "OPTIONS" + +#: ../settings/ticket.rst:113 msgid "" -"This function allows you to provide call information based on e.g. queues " -"only to agents that really need the information." +"The below options allow you to further customize your ticket number. The " +"availability of options differ depending of the chosen ticket number format " +"above." msgstr "" +"Les options ci-dessous vous permettent de personnaliser davantage votre " +"numéro de billet. La disponibilité des options varie en fonction du format " +"de numéro de billet choisi ci-dessus." -#: ../system/integrations/cti/generic.rst:58 +#: ../settings/ticket.rst:122 +msgid "Checksum (default: ``no``)" +msgstr "Somme de contrôle (default: ``no``)" + +#: ../settings/ticket.rst:118 +#, fuzzy msgid "" -"Why? If you have a team for several countries or departments, you don't want " -"to bug your agents from other departments. Leaving these options empty will " -"fallback to showing everything to everyone." +"If set to yes, we'll built a checksum to further \"unique\" the ticket " +"number of your system. If you're dealing with many other ticket systems this " +"might help to prevent false positive follow up detection on tickets." msgstr "" +"Si la valeur est définie sur \"yes\", nous créerons une somme de contrôle " +"pour \"rendre unique\" le numéro de billet de votre système. Si vous avez " +"affaire à de nombreux autres systèmes de billets, ceci pourrait aider à " +"empêcher les détections de faux positifs de suivi sur les billets." -#: ../system/integrations/cti/generic.rst:64 -msgid "Destination caller ID or Queue" +#: ../settings/ticket.rst:122 +msgid "This will also add another digit to the ticket number." msgstr "" +"Cela ajoutera également un autre chiffre significatif au numéro de billet." -#: ../system/integrations/cti/generic.rst:63 -msgid "" -"This depends on your PBX and usually is either a queue ID, phone number or " -"extension." -msgstr "" +#: ../settings/ticket.rst:137 +msgid "Min. size of Number (default: ``5``)" +msgstr "Taille minimale du nombre (par défaut: ``5``)" -#: ../system/integrations/cti/generic.rst:69 -msgid "Agents" +#: ../settings/ticket.rst:125 +msgid "" +"This setting defines the minimum length of your ticket number. If your " +"counter is not yet high enough, Zammad will fill the number with zeros to " +"ensure the wanted length." msgstr "" +"This setting defines the minimum length of your ticket number. If your " +"counter is not yet high enough, Zammad will fill the number with zeros to " +"ensure the wanted length." -#: ../system/integrations/cti/generic.rst:67 +#: ../settings/ticket.rst:129 msgid "" -"Select the agents that are responsible for the group. These agents will then " -"see caller log entries and call notifications fitting to said queue." +"Please note that the minimum length is ``3`` (SystemID + at least one digit " +"if below 10). Also, if the length is no longer long enough, the number will " +"automatically get one digit longer. Ticket-Numbers **do not overflow**, thus " +"it's save to keep it at 5 or set it lower if wanted." msgstr "" +"Veuillez noter que la longueur minimale est de ``3`` (SystemID + au moins un " +"chiffre si inférieur à 10). De plus, si la largeur n'est plus assez longue, " +"le numéro obtiendra automatiquement un chiffre significatif de plus. Les " +"numéros de billet **ne débordent pas**, il est donc préférable de le " +"conserver à 5 ou de l'abaisser si vous le souhaitez." -#: ../system/integrations/cti/generic.rst:0 +#: ../settings/ticket.rst:135 msgid "" -"Screenshot showing the caller log filter table with pre filled sample data" +"This option is only available if ticket number format is set to " +"``Increment``!" msgstr "" +"Cette option n'est disponible que si le format du numéro de billet est réglé " +"sur ``Increment``!" -#: ../system/integrations/cti/includes/recent-logs.include.rst:6 +#: ../settings/ticket.rst:142 +msgid "Auto-Assignment" +msgstr "Affectation automatique" + +#: ../settings/ticket.rst:144 msgid "" -"With recent logs Zammad allows you to view the latest calls for the CTI " -"functionality. This usually comes in handy, when you're looking for errors." +"In a larger Zammad environment, it happens that several agents open the same " +"ticket at the same time. Although collision detection is then effective, the " +"efficiency of processing can be increased by means of the automatic " +"assignment of tickets when a ticket is opened." msgstr "" +"Dans un environnement Zammad plus grand, il arrive que plusieurs agents " +"ouvrent le même billet en même temps. Bien que la détection de collision " +"soit efficace, l'efficacité du traitement peut être augmentée au moyen de " +"l'attribution automatique de billet à leur ouverture." -#: ../system/integrations/cti/includes/recent-logs.include.rst:0 +#: ../settings/ticket.rst:149 +#, fuzzy msgid "" -"Screenshot showing several incoming requests within Recent logs section." +"The automatic assignment of tickets can be activated and configured in the " +"admin area under Settings > Ticket > Auto Assignment." msgstr "" +"L'affectation automatique des billets peut être activée et configurée sur la " +"page d'administration sous Paramètres -> Billet -> Affectation automatique." -#: ../system/integrations/cti/includes/recent-logs.include.rst:16 -msgid "I'm just here to clear floats up." +#: ../settings/ticket.rst:152 +#, fuzzy +msgid "" +"The auto assignment only works if the ticket has no owner yet. By default, " +"the agent can always reset the ticket owner to ``-`` if needed." msgstr "" +"L'affectation automatique ne démarre que si le billet n'a pas encore de " +"propriétaire. Par défaut, l'agent peut toujours réinitialiser le " +"propriétaire du billet sur ``-`` si nécessaire." -#: ../system/integrations/cti/includes/recent-logs.include.rst:20 +#: ../settings/ticket.rst:155 +#, fuzzy msgid "" -"By clicking on the entry of interest, Zammad will provide more details on " -"the call in question. You'll see the payload it received and also the " -"response that was sent." +"If you want to use this function for only specific tickets, you can " +"configure the conditions accordingly to meet your requirement. By default " +"the condition affects all tickets with the state ``open``." msgstr "" +"Si vous souhaitez utiliser cette fonction uniquement pour des billets " +"spécifiques, vous pouvez configurer les conditions en conséquence pour " +"répondre à vos besoins. Par défaut, la condition affecte tous les billets " +"avec l'état ``Ouvert``." -#: ../system/integrations/cti/includes/recent-logs.include.rst:0 +#: ../settings/ticket.rst:161 +#, fuzzy msgid "" -"Screenshot showing detailed information of a specific log entry of recent " -"logs" +"If you need to exclude users (e.g. a group leader), you can search and " +"select the desired agents in the ``Exception Users`` list. The search " +"function in this area is only effective, if you have too many agents to " +"display at once to help you with the configuration." msgstr "" +"La fonction de recherche dans cette zone n'est efficace, pour vous aider " +"dans la configuration, que si vous avez trop d'agents à afficher à la fois." -#: ../system/integrations/cti/includes/recent-logs.include.rst:31 -msgid "x" -msgstr "" +#: ../settings/ticket.rst:167 +#, fuzzy +msgid "Notifications" +msgstr "Bloquer les notifications" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 -#: ../system/integrations/cti/includes/troubleshooting.include.rst:9 -msgid "My Phone page stays blank, signalling does work..." -msgstr "" +#: ../settings/ticket.rst:191 +#, fuzzy +msgid "Default Notifications" +msgstr "Bloquer les notifications" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:5 +#: ../settings/ticket.rst:170 msgid "" -"If you've made sure that signalling works (check Recent logs) and your " -"Caller Log still stays empty, please ensure that you only configured one CTI " -"integration version. Specifically defining more than one agent mapping on " -"the different integration variants will be the issue." +"This setting allows you to configure the default ticket notifications that " +"will be applied to all new agent users (incl. users who were just assigned " +"agent role). Simply change the notification matrix to desired state and " +"press **Save**." msgstr "" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 -msgid "Clear the not needed agent mapping and reload your browser page." +#: ../settings/ticket.rst:175 +msgid "" +"In case an agent already exists, their ticket notification preferences will " +"be preserved. Optionally, you can also **Apply current defaults to all " +"agents**." msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:1 +#: ../settings/ticket.rst:181 msgid "" -"By mapping your agents extension to their existing Zammad users, Zammad can " -"provide a new ticket dialog or open the user profile for the agent that " -"picks up the call." +"**Potential time-consuming action:** Applying default ticket notifications " +"to all agent users may take some time to complete, be patient! The exact " +"time will depend on the size of your system and the number of agents." msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:5 +#: ../settings/ticket.rst:185 msgid "" -"This speeds up ticket aiding, no matter if it's for existing tickets or new " -"ones!" +"**Active agents only!** When current default ticket notifications are " +"applied, only active agent users are considered. In case an agent is re-" +"activated *after* this action, they will still have the old notification " +"configuration." msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:8 +#: ../settings/ticket.rst:190 msgid "" -"To see it work from the agent's perspective, have a look on :user-docs:`user " -"documentation `." +"In case you want to go back to the initial state of ticket notifications, " +"you can click on **Reset to default** button." msgstr "" -#: ../system/integrations/cti/placetel.rst:2 -msgid "Placetel CTI" +#: ../settings/ticket.rst:196 +msgid "Duplicate Detection" msgstr "" -#: ../system/integrations/cti/placetel.rst:16 -msgid "You need an administrative Placetel account for your organization." +#: ../settings/ticket.rst:238 +msgid "Detect Duplicate Ticket Creation" msgstr "" -#: ../system/integrations/cti/placetel.rst:17 -#: ../system/integrations/cti/sipgate.rst:20 +#: ../settings/ticket.rst:199 msgid "" -"Your Zammad instance must be allowed to communicate to external services." -msgstr "" - -#: ../system/integrations/cti/placetel.rst:18 -msgid "Placetel must be able to reach your Zammad instance." -msgstr "" - -#: ../system/integrations/cti/placetel.rst:22 -msgid ":doc:`provider-configurations/placetel`" +"This setting turns on the duplicate ticket detection mechanism during ticket " +"creation. If similar tickets are found in the system, a suitable warning " +"will be shown to the user trying to create a ticket." msgstr "" -#: ../system/integrations/cti/placetel.rst:21 -msgid "" -"Learn how to configure Placetel to enable Zammad and Placetel to communicate " -"with each other." +#: ../settings/ticket.rst:206 +msgid "A Sample Duplicate Ticket Warning" msgstr "" -#: ../system/integrations/cti/placetel.rst:32 +#: ../settings/ticket.rst:208 msgid "" -"The here listed endpoint settings are relevant for the :doc:`integration " -"configuration with Placetel `." +"You can choose which ticket attributes will be matched by selecting them in " +"**Attributes to compare** field. Only if the ticket attribute value provided " +"by the user in the ticket create form is *equal* with the attribute in an " +"existing ticket, the warning will be shown." msgstr "" -#: ../system/integrations/cti/placetel.rst:37 -#: ../system/integrations/i-doit.rst:53 -msgid "Endpoint" +#: ../settings/ticket.rst:213 +msgid "**Warning title** and **Warning message** are configurable as well." msgstr "" -#: ../system/integrations/cti/placetel.rst:36 +#: ../settings/ticket.rst:215 msgid "" -"This endpoint will be required for the Zammad integration within the " -"Placetel web interface." +"You can limit the detection only to certain user roles. By default, only " +"agents will see the warning." msgstr "" -#: ../system/integrations/cti/placetel.rst:41 -msgid "API Token" +#: ../settings/ticket.rst:218 +msgid "" +"If you don't want to show the matched tickets as part of the warning, you " +"can set **Show matching ticket(s) in the warning** setting to *no*." msgstr "" -#: ../system/integrations/cti/placetel.rst:40 +#: ../settings/ticket.rst:221 msgid "" -"You'll receive this token within the ``Web API`` menu. Make sure to copy " -"this value, it's only shown once!" +"By default, **Permission level for looking up ticket** is set to *User*, " +"which means user permissions will be honored during sarch. The user will " +"see the warning only if tickets they have access to are matched. " +"Alternatively, you can set this setting to *System*, in which case the " +"search will happen within *all* tickets in the system, regardless of user " +"permissions." msgstr "" -#: ../system/integrations/cti/placetel.rst:71 -#: ../system/integrations/cti/sipgate.rst:77 -msgid "Phone Extension to Agent Mapping" +#: ../settings/ticket.rst:227 +msgid "**🦺 Safety first!**" msgstr "" -#: ../system/integrations/cti/placetel.rst:0 -msgid "Screenshot showing sample user mappings in between Placetel and Zammad" +#: ../settings/ticket.rst:229 +msgid "" +"Even if the permission level is set to *System*, the user will not be shown " +"the tickets they don't have access to in the warning, even if they match." msgstr "" -#: ../system/integrations/cti/placetel.rst:64 +#: ../settings/ticket.rst:233 msgid "" -"You can find your agents Placetel username combination required within ⚙️ PBX " -"→ VoIP destinations. Within the \"Advanced settings\" section you're looking " -"for \"SIP user name\" and \"SIP server\"." +"However, just the confirmation about the existence of the tickets in the " +"system may be considered an unwanted information disclosure. Use this option " +"carefully!" msgstr "" -#: ../system/integrations/cti/placetel.rst:68 -msgid "Combine these two like so: ``@``." +#: ../settings/ticket.rst:237 +msgid "" +"Finally, you can configure between matching within **All tickets** or **Open " +"tickets** only by setting **Match tickets in following states**. Depending " +"on the current ticket state, a ticket may or not be matched." msgstr "" -#: ../system/integrations/cti/placetel.rst:0 -msgid "Sample VoIP credentials for a Placetel user" +#: ../system/core-workflows.rst:2 +msgid "Core Workflows" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:2 -msgid "Setup Placetel connection for Zammad" +#: ../system/core-workflows.rst:4 +msgid "" +"Core Workflows allow you to adjust object attributes in many ways. For " +"example:" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:6 -msgid "" -"This configuration step requires a *full* administrative Placetel account. " -"You may receive forbidden error messages with Placetel in case your " -"permissions are not high enough." +#: ../system/core-workflows.rst:7 +msgid "show / hide fields" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:10 -msgid "" -"The following actions can be configured via the `Placetel web interface " -"`_." +#: ../system/core-workflows.rst:8 +msgid "adjust mandatory setting" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:29 -msgid "Step 1: Activate Zammad integration" +#: ../system/core-workflows.rst:9 +msgid "manipulate available options" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:14 +#: ../system/core-workflows.rst:11 msgid "" -"Within Integrations, scroll down to Partner integrations and select Zammad." +"With this, you can provide exactly the information your users really need!" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:17 +#: ../system/core-workflows.rst:15 msgid "" -"You can alternatively filter by \"Ticket Systems\" to reduce the number of " -"entries on the page. You'll still want to look for Partner integrations. 🤓" +"If the pre-defined :doc:`/system/objects` are not enough, please add them " +"beforehand." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:21 +#: ../system/core-workflows.rst:17 msgid "" -"Within the Zammad integration now press \"Activate\". A new tab ``API`` " -"becomes available - open this tab." +"If you experience slow or unreliable field updates, please see :ref:`Core " +"Workflow Ajax Modus `" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:24 +#: ../system/core-workflows.rst:22 msgid "" -"Now tick \"Enable Call Control / Notify API\" and paste the Placetel " -"endpoint from your Zammad instance into the field \"URL of your API " -"endpoint\". Save to apply the settings" +"This is a very enhanced functionality and can cause unexpected UI behavior. " +"Please ensure to test your use cases after configuration to reduce surprises." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 -msgid "Screencast showing how to activate the Zammad integration" +#: ../system/core-workflows.rst:None +msgid "Dialogue for adding a new workflow" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:51 -msgid "Step 2: Generate API Token for Placetel" +#: ../system/core-workflows/condition-operators.rst:2 +msgid "Core Workflow Condition Operators" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:32 +#: ../system/core-workflows/condition-operators.rst:4 msgid "" -"Go back to the integrations page and scroll down to \"Web API\". Generate a " -"new API token by using the \"Create a new API token\" button." +"You might know that there is a separate section for explaining :doc:" +"`condition operators `. Head over there to " +"see a detailed explanation of many conditions and operators." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:37 +#: ../system/core-workflows/condition-operators.rst:8 msgid "" -"If you already generated a token either use your existing token or reset it " -"by using above mentioned button. Placetel will ask you to conform this reset." +"Due to differences to other places in Zammad which are also using conditions " +"(e.g. triggers), you can find a dedicated description of operators for core " +"workflows below." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:41 +#: ../system/core-workflows/condition-operators.rst:12 msgid "" -"Please keep in mind that existing API scripts may no longer work due to " -"token resets!" +"Be aware that the availability of the operators depends on the selected " +"attribute and its field type. Some of the operators may only be available " +"for system attributes (e.g. for \"tags\", \"active\")." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:44 -msgid "" -"Copy the provided API token and insert it into the \"API Token\" field " -"within Zammad's Placetel integration." +#: ../system/core-workflows/condition-operators.rst:20 +msgid "Operator" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:47 -msgid "" -"Apply your changes by using the \"Save\" button on the bottom of the " -"Placetel integration page and activate the Placetel integration." +#: ../system/core-workflows/condition-operators.rst:22 +msgid "after (absolute)" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 -msgid "" -"Screencast showing how to retrieve an API token from Placetel for Zammad" +#: ../system/core-workflows/condition-operators.rst:23 +msgid "Matches if a date/time is after a specific point in time." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:73 -#: ../system/integrations/cti/provider-configurations/sipgate.rst:77 -msgid "Step 3: Restrict the numbers to notify on" +#: ../system/core-workflows/condition-operators.rst:24 +msgid "after (relative)" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:54 -msgid "" -"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " -"the the Integrations page of the Placetel web interface, go to \"Notify " -"API\"." +#: ../system/core-workflows/condition-operators.rst:25 +msgid "Matches if a time span after a specified event has passed." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:58 -msgid "" -"Lower on the page Placetel allows you to restrict the numbers to notify on. " -"You'll find this within the \"External routing API\" part." +#: ../system/core-workflows/condition-operators.rst:26 +msgid "before (absolute)" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 -msgid "" -"Screenshot showing a sample selection of phone numbers to use for the " -"Placetels notify API" +#: ../system/core-workflows/condition-operators.rst:27 +msgid "Matches if a date/time is before a specific point in time." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:66 -msgid "" -"This menu point also provides a API request log from Placetel view. Just " -"open \"Recent responses of your API endpoint\" to learn more." +#: ../system/core-workflows/condition-operators.rst:28 +msgid "before (relative)" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:69 -msgid "" -"If you want to see Zammad's perspective, use the \"Recent Logs\" part from " -"within the Placetel integration page." +#: ../system/core-workflows/condition-operators.rst:29 +msgid "Matches if a time span after a specified event has not passed." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 -msgid "Screenshot showing sample log entries for Placetels API calls to Zammad" +#: ../system/core-workflows/condition-operators.rst:30 +msgid "contains" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:77 -msgid "Step 4 (optional): Further configurations for Placetel" +#: ../system/core-workflows/condition-operators.rst:31 +msgid "Matches if a specified value is present." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:76 -msgid "" -"If needed, you can now configure Zammad's Placetel integration in more " -"detail. You can learn more about your options here: :ref:`Placetel " -"integration settings `." +#: ../system/core-workflows/condition-operators.rst:33 +msgid "Matches if all of the specified values are present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:2 -msgid "Setup Sipgate connection for Zammad" +#: ../system/core-workflows/condition-operators.rst:35 +msgid "Matches if none of the specified values are present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Sipgate has no english web interface which is why this documentation page is " -"mixing up languages badly." +#: ../system/core-workflows/condition-operators.rst:36 +msgid "contains not" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Please also note that the availability of API addons highly depends on your " -"package trier. Usage of sipgate.io packages *is not free*, please check " -"their `pricing page `_ before!" +#: ../system/core-workflows/condition-operators.rst:37 +msgid "Matches if a specified value is not present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:35 -msgid "Step 1: Book sipgate.io package" +#: ../system/core-workflows/condition-operators.rst:39 +msgid "Matches if one specified value is present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:13 -msgid "Skip to step 2 if you already have the package booked!" +#: ../system/core-workflows/condition-operators.rst:41 +msgid "Matches if one specified value is not present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:15 -msgid "" -"Login to an administrative Sipgate account and navigate to " -"``Accountverwaltung``. You'll see several different options depending on " -"your booked packages. Select ``Verträge & Produkte`` to continue." +#: ../system/core-workflows/condition-operators.rst:42 +msgid "does not match regex" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:19 -msgid "" -"Scroll down to the section ``Zusätzliche Produkte buchen`` and look for " -"``sipgate.io`` - select this product by using the ``Produkte anzeigen``-" -"Button." +#: ../system/core-workflows/condition-operators.rst:43 +msgid "Matches if content doesn't fit to regex rule." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:23 -msgid "" -"On the next page select either one of the ``sipgate.io`` packages or ``Push-" -"API Package Free``. Follow the dialogue by booking the addon. You'll be " -"returned to your contract overview and now should see the selected addon in " -"your list." +#: ../system/core-workflows/condition-operators.rst:44 +msgid "ends with" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:30 -msgid "" -"The availability for ``sipgate.io`` packages and their levels highly depends " -"on the overall account type and product you've booked with Sipgate." +#: ../system/core-workflows/condition-operators.rst:45 +msgid "Matches if content ends with specified value." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screencast showing the process on how to book the required sipgate.io addon" +#: ../system/core-workflows/condition-operators.rst:46 +msgid "ends with one of" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:52 -msgid "Step 2: Configure webhook for Zammad" +#: ../system/core-workflows/condition-operators.rst:47 +msgid "Matches if content ends with one of the specified values." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:38 -msgid "" -"Within your ``Accountverwaltung`` navicate to your product ``sipgate.io``. " -"In the newly opened tab, switch from \"Clients\" to \"Webhooks\" and paste " -"the endpoint URLs from your Zammad instance like so:" +#: ../system/core-workflows/condition-operators.rst:48 +msgid "from (relative)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:42 -msgid "Inbound endpoint to \"Incoming\"" +#: ../system/core-workflows/condition-operators.rst:49 +msgid "Matches if date/time is after a period of time after an event." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:43 -msgid "Outbound endpoint to \"Outgoing\"" +#: ../system/core-workflows/condition-operators.rst:51 +msgid "Matches if content is equal to a specified value." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:47 -msgid "" -"Ensure to select at least one call group or phoneline within \"Sources\". " -"Other wise Sipgate will not indicate any incoming or outgoing calls to " -"Zammad." +#: ../system/core-workflows/condition-operators.rst:52 +msgid "is any of" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screencast showing how to add Zammad's endpoint URLs to sipgate.ios webhook " -"configuration" +#: ../system/core-workflows/condition-operators.rst:53 +msgid "Matches if content is equal to any of specified values." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:55 -msgid "" -"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " -"the Webhooks → URLs section of Sipgate you can select which *sources* " -"Sipgate should notify Zammad about in- and outgoing calls." +#: ../system/core-workflows/condition-operators.rst:54 +msgid "is modified" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:59 -msgid "" -"Use either specific phone lines or use the option \"Use for all phonelines " -"and groups\" to notify Zammad about all existing lines of your Sipgate " -"account." +#: ../system/core-workflows/condition-operators.rst:55 +msgid "Matches if content is modified." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screenshot showing a sample selection of phone numbers to use for the " -"Sipgates webhooks API" +#: ../system/core-workflows/condition-operators.rst:57 +#: ../system/core-workflows/condition-operators.rst:61 +msgid "True from the moment of changing content until form submit." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:68 -msgid "This section also allows you to enable a Debug log." +#: ../system/core-workflows/condition-operators.rst:58 +msgid "is modified to" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "Screenshot showing an enabled Debug log option" +#: ../system/core-workflows/condition-operators.rst:59 +msgid "Matches if content is modified to a specific value." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:73 -msgid "" -"After enabling you can use the Debug log section to see all sent webhook " -"calls to Zammad. You'll also can see the response." +#: ../system/core-workflows/condition-operators.rst:62 +msgid "is none of" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screenshot showing sample log entries for Sipgates webhook calls to Zammad" +#: ../system/core-workflows/condition-operators.rst:63 +msgid "Matches if content is none of any specified values." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:81 -msgid "Step 4 (optional): Further configurations for Sipgate" +#: ../system/core-workflows/condition-operators.rst:65 +msgid "Matches if content is not equal to a specified value." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:80 -msgid "" -"If needed, you can now configure Zammad's Sipgate integration in more " -"detail. You can learn more about your options here: :ref:`Sipgate " -"integration settings `." +#: ../system/core-workflows/condition-operators.rst:67 +msgid "Matches if content is present." msgstr "" -#: ../system/integrations/cti/sipgate.rst:2 -msgid "Sipgate (sipgate.io)" +#: ../system/core-workflows/condition-operators.rst:68 +msgid "just changed" msgstr "" -#: ../system/integrations/cti/sipgate.rst:16 -msgid "You need an administrative Sipgate account for your organization." +#: ../system/core-workflows/condition-operators.rst:69 +msgid "Matches if content has changed." msgstr "" -#: ../system/integrations/cti/sipgate.rst:17 +#: ../system/core-workflows/condition-operators.rst:71 +#: ../system/core-workflows/condition-operators.rst:75 msgid "" -"Zammad requires a ``sipgate.io`` addon from the feature store (please note " -"that API calls are not free with Sipgate. Rates may apply and differ from " -"account to account)." -msgstr "" - -#: ../system/integrations/cti/sipgate.rst:21 -msgid "Sipgate must be able to reach your Zammad instance." +"Only true for the moment of changing content until next form field action/" +"click." msgstr "" -#: ../system/integrations/cti/sipgate.rst:25 -msgid ":doc:`provider-configurations/sipgate`" +#: ../system/core-workflows/condition-operators.rst:72 +msgid "just changed to" msgstr "" -#: ../system/integrations/cti/sipgate.rst:24 -msgid "" -"Learn how to configure Sipgate to enable Zammad and Sipgate to communicate " -"with each other." +#: ../system/core-workflows/condition-operators.rst:73 +msgid "Matches if content has changed to a specified value." msgstr "" -#: ../system/integrations/cti/sipgate.rst:33 -msgid "" -"Below endpoint settings affect the :doc:`sipgate.io configuration `." +#: ../system/core-workflows/condition-operators.rst:76 +msgid "matches regex" msgstr "" -#: ../system/integrations/cti/sipgate.rst:37 -msgid "This endpoint is required for incoming call hooks." +#: ../system/core-workflows/condition-operators.rst:77 +msgid "Matches if value fits to regex rule." msgstr "" -#: ../system/integrations/cti/sipgate.rst:40 -msgid "This endpoint is required for outgoing call hooks." +#: ../system/core-workflows/condition-operators.rst:79 +msgid "Matches if no content is present." msgstr "" -#: ../system/integrations/cti/sipgate.rst:0 -msgid "Screenshot showing sample user mappings in between Sipgate and Zammad" +#: ../system/core-workflows/condition-operators.rst:80 +msgid "starts with" msgstr "" -#: ../system/integrations/cti/sipgate.rst:69 -msgid "" -"You can find your agent's Sipgate username within ``Accountverwaltung → " -"Benutzer``. You're looking for the SIP-ID." +#: ../system/core-workflows/condition-operators.rst:81 +msgid "Matches if content starts with specified value." msgstr "" -#: ../system/integrations/cti/sipgate.rst:0 -msgid "Sample VoIP credentials for a Sipgate user" +#: ../system/core-workflows/condition-operators.rst:82 +msgid "starts with one of" msgstr "" -#: ../system/integrations/cti/sipgate.rst:77 -msgid "Users with several devices also have several SIP-IDs." +#: ../system/core-workflows/condition-operators.rst:83 +msgid "Matches if content starts with one of the specified values." msgstr "" -#: ../system/integrations/elasticsearch.rst:2 -msgid "Elasticsearch (SaaS)" +#: ../system/core-workflows/condition-operators.rst:84 +msgid "till (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:4 -msgid "" -"The Elasticsearch integration allows you to create a read-only user to use " -"with your favorite reporting tool (e.g. like Grafana)." +#: ../system/core-workflows/condition-operators.rst:85 +msgid "Matches if date/time is before a period of time before an event." msgstr "" -#: ../system/integrations/elasticsearch.rst:7 -msgid "" -"If you want to take full advantage of the Zammad reporting, have a look at " -"our :docs:`Grafana ` " -"setup page as well." +#: ../system/core-workflows/condition-operators.rst:86 +msgid "today" msgstr "" -#: ../system/integrations/elasticsearch.rst:11 -#: ../system/subscription/index.rst:7 -msgid "**🚧 Hosted environment specific 🚧**" +#: ../system/core-workflows/condition-operators.rst:87 +msgid "Matches if date/time is today." msgstr "" -#: ../system/integrations/elasticsearch.rst:13 -msgid "" -"This integration is only available for Hosted setups. In order to use " -"Elasticsearch you'll need the **Plus** subscription." +#: ../system/core-workflows/condition-operators.rst:88 +msgid "within last (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:16 +#: ../system/core-workflows/condition-operators.rst:89 msgid "" -"Self hosted users have all the control over their self hosted Elasticsearch " -"instances." +"Matches if date/time content is within specified period of time before now." msgstr "" -#: ../system/integrations/elasticsearch.rst:None -msgid "Elasticsearch integration page on SaaS environments" +#: ../system/core-workflows/condition-operators.rst:91 +msgid "within next (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:27 +#: ../system/core-workflows/condition-operators.rst:92 msgid "" -"Please note the following limitations of Elasticsearch access on hosted " -"environments:" -msgstr "" - -#: ../system/integrations/elasticsearch.rst:30 -msgid "access to the Elasticsearch index is read-only access" +"Matches if date/time content is within specified period of time after now." msgstr "" -#: ../system/integrations/elasticsearch.rst:31 -msgid "currently you're limited to user only" +#: ../system/core-workflows/how-do-they-work.rst:2 +msgid "How do they work?" msgstr "" -#: ../system/integrations/elasticsearch.rst:32 +#: ../system/core-workflows/how-do-they-work.rst:4 msgid "" -"Reporting tools that require to write into the indexes (like Kibana) are not " -"supported" +"Core Workflows are executed according to their priority. If two workflows " +"have the same priority, they are executed in alphabetical order based on " +"their **name**." msgstr "" -#: ../system/integrations/elasticsearch.rst:34 -msgid "IP access restriction is currently not yet supported" +#: ../system/core-workflows/how-do-they-work.rst:8 +msgid "" +"Because of the way Core Workflows work, all changes to attributes are " +"checked with the application server - please see :doc:`limitations` for " +"possible issues." msgstr "" -#: ../system/integrations/elasticsearch.rst:37 -msgid "Activating Elasticsearch Access" +#: ../system/core-workflows/how-do-they-work.rst:12 +msgid "" +"Below we're talking about settings that are important and not self-" +"explanatory." msgstr "" -#: ../system/integrations/elasticsearch.rst:39 +#: ../system/core-workflows/how-do-they-work.rst:17 msgid "" -"By default external access to your Elasticsearch index is not active. You " -"can enable the integration at any time if needed." +"Choose the object context you want to run the workflow in. This will decide " +"on your available attributes and actions." msgstr "" -#: ../system/integrations/elasticsearch.rst:42 -msgid "" -"Please ensure to note down the password provided - you won't have access to " -"it afterwards." +#: ../system/core-workflows/how-do-they-work.rst:20 +msgid "Ticket objects also have access to the ticket customer." msgstr "" -#: ../system/integrations/elasticsearch.rst:None -msgid "Screencast showing activation of Elasticsearch integration" +#: ../system/core-workflows/how-do-they-work.rst:25 +msgid "" +"Choose in which situation the workflow is applied. Contexts can be combined " +"to avoid duplicate workflows." msgstr "" -#: ../system/integrations/elasticsearch.rst:51 -msgid "Connection Settings" +#: ../system/core-workflows/how-do-they-work.rst:30 +msgid "Creation mask" msgstr "" -#: ../system/integrations/elasticsearch.rst:53 +#: ../system/core-workflows/how-do-they-work.rst:29 msgid "" -"This section holds the most important general information for accessing your " -"Elasticsearch indexes - such as:" +"If selected, your conditions and actions will affect all applicable creation " +"masks." msgstr "" -#: ../system/integrations/elasticsearch.rst:57 -msgid "A unique subdomain that does not tell your real instance URL." +#: ../system/core-workflows/how-do-they-work.rst:34 +msgid "Edit mask" msgstr "" -#: ../system/integrations/elasticsearch.rst:61 -msgid "Software" +#: ../system/core-workflows/how-do-they-work.rst:33 +msgid "" +"If selected, your conditions and actions will affect all applicable edit " +"masks." msgstr "" -#: ../system/integrations/elasticsearch.rst:60 +#: ../system/core-workflows/how-do-they-work.rst:39 msgid "" -"The major version of the search index being used. This is required by some " -"Reporting tools like Grafana." +"Zammad differentiates between selected and saved conditions. These can be " +"combined wherever needed." msgstr "" -#: ../system/integrations/elasticsearch.rst:64 -msgid "Authentication" +#: ../system/core-workflows/how-do-they-work.rst:42 +msgid "**⚠️ Restrict workflows to specific roles if needed!**" msgstr "" -#: ../system/integrations/elasticsearch.rst:64 -msgid "The authentication type being supported. ``Basic Authentication``" +#: ../system/core-workflows/how-do-they-work.rst:44 +msgid "" +"By default and unless configured in conditions, workflow rules are executed " +"for **all roles**. This also affects your customers!" msgstr "" -#: ../system/integrations/elasticsearch.rst:67 -msgid "Available Indexes" +#: ../system/core-workflows/how-do-they-work.rst:50 +msgid "Selected Conditions" msgstr "" -#: ../system/integrations/elasticsearch.rst:69 +#: ../system/core-workflows/how-do-they-work.rst:48 msgid "" -"Within this section we're displaying the -in our opinion- most important " -"indexes for a Zammad instance." +"These conditions are based on form values and match if an appropriate " +"selection is made (e.g. choosing another group in the ticket without " +"saving). This applies for drafts (active selection) and currently saved " +"values." msgstr "" -#: ../system/integrations/elasticsearch.rst:72 +#: ../system/core-workflows/how-do-they-work.rst:64 +msgid "Saved Conditions" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:53 msgid "" -"If you require all indexes or our listing is not good enough for you, point " -"your browser to the URL we're providing and append ``/_aliases?" -"pretty=true``. The result should look like this: ``https://.zammad.com/" -"_aliases?pretty=true``." +"These conditions only match if the selected values are stored in the " +"database. It ignores the current value or selection of the field, as long as " +"the changes are not saved (e.g. performing field operations for an existing " +"ticket, which is viewed/opened by an agent)." msgstr "" -#: ../system/integrations/elasticsearch.rst:77 +#: ../system/core-workflows/how-do-they-work.rst:60 msgid "" -"Your browser will automatically ask for your credentials - you'll then see " -"something like this:" +"Keep in mind that the value has to be available in the situation where you " +"need it. Otherwise the condition won't match." msgstr "" -#: ../system/integrations/elasticsearch.rst:125 -msgid "Credentials" +#: ../system/core-workflows/how-do-they-work.rst:63 +msgid "" +"Example: you can't perform any actions with *saved condition* on a ticket in " +"creation, because there are no saved values at that time." msgstr "" -#: ../system/integrations/elasticsearch.rst:127 +#: ../system/core-workflows/how-do-they-work.rst:66 msgid "" -"Within this section Zammad displays your available users. The password is " -"provided once (upon activation) and cannot be retrieved after that." +"You can find a description of the condition operators for core workflows :" +"doc:`here `." msgstr "" -#: ../system/integrations/elasticsearch.rst:131 +#: ../system/core-workflows/how-do-they-work.rst:72 msgid "" -"If you need to change or reset your Elasticsearch user password, use the " -"\"Reset password\" button in the credentials table. Doing so creates a brand " -"new password for the account in question. This change is immediate, keep in " -"mind that this may affect third party tools connected to your instance." +"Which actions should we run on the relevant fields? The possible actions " +"depend on the object type. However, usually you can at least change the " +"visibility and whether the field is mandatory." msgstr "" -#: ../system/integrations/exchange.rst:2 -msgid "Exchange" +#: ../system/core-workflows/how-do-they-work.rst:76 +msgid "Be aware that actions are not available for **related** context." msgstr "" -#: ../system/integrations/exchange.rst:4 +#: ../system/core-workflows/how-do-they-work.rst:78 msgid "" -"With Zammad's Exchange integration, you can easily use existing address " -"books without having to update more than one source." +"**Example:** Let's assume you are working in the ticket context. While you " +"can have customer *conditions*, you *can't adjust* objects with actions in " +"that scope. That's because this wouldn't have any impact on the ticket " +"dialog. Of course all ticket attributes (state, owner, ...) are available." msgstr "" -#: ../system/integrations/exchange.rst:7 +#: ../system/core-workflows/how-do-they-work.rst:84 msgid "" -"However, you should refrain from syncing all addresses, as the results may " -"not be what you expect (Exchange collects huge amounts of addresses). A " -"central address book of your company to sync makes more sense, as you can " -"ensure that Zammad gets only the data you need and want. Apart from this, it " -"is even not possible to sync the Global Address List (GAL) of your Exchange " -"system with Zammad." +"Please also have a look at our :doc:`limitations` to be safe from surprises." msgstr "" -#: ../system/integrations/exchange.rst:16 -msgid "" -"**Exchange and LDAP:** The exchange sync can be overruled by Zammad's LDAP " -"integration. If you have the same users in both sources, the LDAP version " -"will always be Zammad's pick." +#: ../system/core-workflows/how-do-they-work.rst:88 +msgid "Available Operators" msgstr "" -#: ../system/integrations/exchange.rst:19 -msgid "" -"**One way sync:** the Exchange sync is one way. Exchange => Zammad. Changes " -"to your users inside of Zammad might be overwritten by the Exchange sync." +#: ../system/core-workflows/how-do-they-work.rst:90 +msgid "The availability of operators depends on the object type and scope." msgstr "" -#: ../system/integrations/exchange.rst:24 +#: ../system/core-workflows/how-do-they-work.rst:94 msgid "" -"To configure Exchange integration, simply go to the System > Integrations > " -"Exchange in the admin panel. Press \"change\" and follow the wizard for " -"adding the needed Exchange information to Zammad. On the last two steps " -"Zammad will ask you for the address book(s) and your desired attribute " -"mapping. By default, Zammad only maps email address, first- and lastname. " -"Technically, you can map any Exchange object to a Zammad user object (this " -"also works for custom objects!)." +"Please note that actions may or may not restrict API based access to " +"attributes. We're displaying the following icons for your overview to " +"understand these limits better:" msgstr "" -#: ../system/integrations/exchange.rst:35 -msgid "" -"If the SSL verification fails while connecting to Exchange, Zammad will ask " -"you to turn it off temporarily." +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|api| This icon indicates the action affects the API." msgstr "" -#: ../system/integrations/exchange.rst:38 -msgid "" -"Please be aware that **turning off SSL verification is a security risk**. It " -"should only be used temporarily or for testing purposes. If turned off, " -"there is no verification of the certificate, which means that every " -"presented certificate will be accepted." +#: ../system/core-workflows/how-do-they-work.rst:163 +msgid "api" msgstr "" -#: ../system/integrations/exchange.rst:43 -msgid "" -"After pressing Continue, Zammad will check if the configuration is okay. You " -"can then enable Exchange and start your first sync. The sync will then run " -"hourly - if you need to change mappings or the address book(s), you can " -"change the configuration at any time." +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|ui| This icon indicates the action only affects the web interface." msgstr "" -#: ../system/integrations/exchange.rst:50 -msgid "" -"After the sync has finished, you can find the new Exchange contacts under " -"\"Users\". Zammad integrates them just as normal users." +#: ../system/core-workflows/how-do-they-work.rst:167 +msgid "ui" msgstr "" -#: ../system/integrations/exchange.rst:55 -msgid "" -"In some cases you might see unique IDs as \"Login\" instead of the email " -"address. This is normal and doesn't affect the login or email mapping for " -"that entry." +#: ../system/core-workflows/how-do-they-work.rst:102 +msgid "show |ui|" msgstr "" -#: ../system/integrations/github.rst:4 -msgid "" -"Use GitHub integration to track GitHub issues directly within Zammad " -"tickets. Add issue hyperlinks and get a live summary of metadata like status " -"(open/closed), assignee, labels, and more." +#: ../system/core-workflows/how-do-they-work.rst:102 +msgid "Display the chosen field. Allows setting of values." msgstr "" -#: ../system/integrations/github.rst:8 -msgid "Please note that our GitHub integration does not support pull requests." +#: ../system/core-workflows/how-do-they-work.rst:109 +msgid "hide |ui|" msgstr "" -#: ../system/integrations/github.rst:None -msgid "Integration page for GitHub" +#: ../system/core-workflows/how-do-they-work.rst:105 +msgid "" +"Hide the chosen field. However, it technically still allows setting the " +"field." msgstr "" -#: ../system/integrations/github.rst:18 +#: ../system/core-workflows/how-do-they-work.rst:108 msgid "" -"In your GitHub settings, create a new API token under **Developer settings > " -"Personal access tokens > Generate new token**. Leave the **Scopes** section " -"empty." +"Please note that the field is **not** gone and still contains an existing " +"value (if set)! Consider *remove* instead, if you want this field to be gone." msgstr "" -#: ../system/integrations/github.rst:0 ../system/integrations/gitlab.rst:0 -msgid "Screencast showing how to create a new API token" +#: ../system/core-workflows/how-do-they-work.rst:112 +msgid "remove |ui|" msgstr "" -#: ../system/integrations/github.rst:27 -msgid "Create a new API key with no scopes/privileges." +#: ../system/core-workflows/how-do-they-work.rst:112 +msgid "Entirely removes the field. The field value will not be evaluated." msgstr "" -#: ../system/integrations/github.rst:29 -msgid "🔒 **Will this work for private repos?**" +#: ../system/core-workflows/how-do-they-work.rst:115 +msgid "set mandatory |ui| |api|" msgstr "" -#: ../system/integrations/github.rst:31 -msgid "" -"No. To link private repo issues, **use the** ``repo`` **scope instead**. " -"Bear in mind that the resulting token will have `lots of permissions that it " -"doesn't actually need `_, which presents a security risk if your token ever falls into " -"the wrong hands." +#: ../system/core-workflows/how-do-they-work.rst:115 +msgid "Sets the field to mandatory." msgstr "" -#: ../system/integrations/github.rst:37 -msgid "" -"Unfortunately, because of how GitHub's OAuth token scopes are set up, this " -"is the only way to link issues on private repos." +#: ../system/core-workflows/how-do-they-work.rst:118 +msgid "set optional |ui| |api|" msgstr "" -#: ../system/integrations/github.rst:40 -msgid "Enter your new API token in Zammad and enable GitHub integration." +#: ../system/core-workflows/how-do-they-work.rst:118 +msgid "Sets the field to optional." msgstr "" -#: ../system/integrations/github.rst:0 -msgid "Screencast showing how to configure Zammad's GitHub integration" +#: ../system/core-workflows/how-do-they-work.rst:124 +msgid "add option |ui| |api|" msgstr "" -#: ../system/integrations/github.rst:47 -msgid "" -"Use the default API endpoint (``https://api.github.com/graphql``) unless " -"you're using GitHub Enterprise Server." +#: ../system/core-workflows/how-do-they-work.rst:121 +msgid "Allows adding options to tree selects or selects." msgstr "" -#: ../system/integrations/github.rst:50 +#: ../system/core-workflows/how-do-they-work.rst:123 msgid "" -"Once completed, a new GitHub issues tab will appear in the ticket pane. 🎉" +"You have to use the \"remove option\" before performing this action. It " +"allows you to use *existing* configured values." msgstr "" -#: ../system/integrations/github.rst:59 ../system/integrations/gitlab.rst:52 -msgid "Token verification is taking a long time" +#: ../system/core-workflows/how-do-they-work.rst:128 +msgid "remove option |ui| |api|" msgstr "" -#: ../system/integrations/github.rst:56 ../system/integrations/gitlab.rst:49 +#: ../system/core-workflows/how-do-they-work.rst:127 msgid "" -"Slight delays are normal (<2 min.), especially for systems under heavy load." +"Allows removing options from tree selects or selects. It allows you to use " +"*existing* configured values." msgstr "" -#: ../system/integrations/github.rst:58 -msgid "" -"Self-hosted administrators, please check your network settings to ensure " -"that your Zammad server can reach ``api.github.com``." +#: ../system/core-workflows/how-do-they-work.rst:134 +msgid "set fixed to |ui| |api|" msgstr "" -#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 -msgid "I reloaded the page and now the API token is gone" +#: ../system/core-workflows/how-do-they-work.rst:131 +msgid "Reduces the available options by your selection." msgstr "" -#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 +#: ../system/core-workflows/how-do-they-work.rst:133 msgid "" -"This may indicate that Zammad is still verifying your API token. Try " -"reloading the page again in a couple minutes." +"This reduces your workflows in terms of *add option* and *remove option*." msgstr "" -#: ../system/integrations/gitlab.rst:2 -msgid "GitLab" +#: ../system/core-workflows/how-do-they-work.rst:137 +msgid "fill in |ui|" msgstr "" -#: ../system/integrations/gitlab.rst:4 -msgid "" -"Use GitLab integration to track GitLab issues directly within Zammad " -"tickets. Add issue hyperlinks and get a live summary of metadata like status " -"(open/closed), assignee, labels, and more." +#: ../system/core-workflows/how-do-they-work.rst:137 +msgid "Allows filling in of string and integer fields with your values." msgstr "" -#: ../system/integrations/gitlab.rst:8 +#: ../system/core-workflows/how-do-they-work.rst:141 +msgid "fill in empty |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:140 msgid "" -"Please note that our GitLab integration does not support merge requests." +"Allows filling in of string and integer fields with your values **if the " +"field is empty**." msgstr "" -#: ../system/integrations/gitlab.rst:None -msgid "Integration page for GitLab" +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "select |ui|" msgstr "" -#: ../system/integrations/gitlab.rst:18 -msgid "" -"In your GitLab preferences, create a new API token under **Access Tokens**." +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "Select a specific value within a select, tree select or boolean field." msgstr "" -#: ../system/integrations/gitlab.rst:20 -msgid "Under **Select scopes**, choose ``read_api`` only." +#: ../system/core-workflows/how-do-they-work.rst:153 +msgid "auto select |ui|" msgstr "" -#: ../system/integrations/gitlab.rst:27 -msgid "🔒 **If you wish to link issues on any private repos...**" +#: ../system/core-workflows/how-do-they-work.rst:147 +msgid "Helps users with tree select and select fields:" msgstr "" -#: ../system/integrations/gitlab.rst:29 -msgid "Your API token must belong to an account with access to those repos." +#: ../system/core-workflows/how-do-they-work.rst:149 +msgid "" +"If the field has only one option available for selection and no value yet, " +"the value will be automatically set." msgstr "" -#: ../system/integrations/gitlab.rst:31 -msgid "Enter your new API token in Zammad and enable GitLab integration." +#: ../system/core-workflows/how-do-they-work.rst:152 +msgid "" +"This option only works if you have one value and doesn't work if there is " +"more than one option available." msgstr "" -#: ../system/integrations/gitlab.rst:0 -msgid "Screencast showing how to configure Zammad's GitLab integration" +#: ../system/core-workflows/how-do-they-work.rst:157 +msgid "set readonly |ui|" msgstr "" -#: ../system/integrations/gitlab.rst:40 +#: ../system/core-workflows/how-do-they-work.rst:156 msgid "" -"Use the default API endpoint (``https://gitlab.com/api/graphql``) unless " -"you're a self-hosted GitLab user." +"Allows you to display an attribute as read only (which means no changes are " +"possible)." msgstr "" -#: ../system/integrations/gitlab.rst:43 -msgid "" -"Once completed, a new GitLab issues tab will appear in the ticket pane. 🎉" +#: ../system/core-workflows/how-do-they-work.rst:161 +msgid "unset readonly |ui|" msgstr "" -#: ../system/integrations/gitlab.rst:51 +#: ../system/core-workflows/how-do-they-work.rst:160 msgid "" -"Self-hosted administrators, please check your network settings to ensure " -"that your Zammad server can reach ``gitlab.com``." +"In case a workflow set the field in question to read only, you can undo this " +"with option above." msgstr "" -#: ../system/integrations/i-doit.rst:2 -msgid "i-doit" +#: ../system/core-workflows/how-do-they-work.rst:172 +msgid "Stop after match" msgstr "" -#: ../system/integrations/i-doit.rst:4 +#: ../system/core-workflows/how-do-they-work.rst:174 msgid "" -"`i-doit `_ is an open-source **configuration " -"management database** - in other words, a tool for keeping tabs on every " -"single piece of your physical and digital infrastructure, from network " -"equipment to virtual machines on down to the faceplates on your rack shelves " -"and more." +"Here you can decide if other workflows are executed after the current one." msgstr "" -#: ../system/integrations/i-doit.rst:10 +#: ../system/core-workflows/how-do-they-work.rst:176 msgid "" -"What's that got to do with Zammad? Well, if you used tickets to track issues " -"with all that hardware, you might start wishing there was a way they could " -"talk to each other." +"If set to ``no`` (default), further workflows will be executed if they match " +"the condition. In this case, it is possible that your actions from the " +"current workflow can be overwritten by another workflow." msgstr "" -#: ../system/integrations/i-doit.rst:14 -msgid "Zammad gives you two:" +#: ../system/core-workflows/how-do-they-work.rst:180 +msgid "" +"If set to ``yes``, no further worflows will be executed after the current " +"one." msgstr "" -#: ../system/integrations/i-doit.rst:17 -msgid "1. Add i-doit Links to Zammad Tickets" +#: ../system/core-workflows/how-do-they-work.rst:184 +msgid "Priority" msgstr "" -#: ../system/integrations/i-doit.rst:20 ../system/integrations/i-doit.rst:80 -msgid "What Users See" +#: ../system/core-workflows/how-do-they-work.rst:186 +msgid "" +"You can define the sequence, in which the workflows are executed. The " +"default value is ``500``." msgstr "" -#: ../system/integrations/i-doit.rst:26 -msgid "i-doit integration in Zammad's ticket pane" +#: ../system/core-workflows/how-do-they-work.rst:189 +msgid "" +"The workflows are executed in ascending order by their priority. That means " +"lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." msgstr "" -#: ../system/integrations/i-doit.rst:26 +#: ../system/core-workflows/learn-by-example.rst:2 +#, fuzzy +msgid "Learn by Example" +msgstr "Exemple" + +#: ../system/core-workflows/learn-by-example.rst:4 msgid "" -"The i-doit integration will appear under a new 🖨 tab in the ticket pane." +"This page provides some basic examples for Core Workflows. Of course you can " +"build much more complex workflows if needed." msgstr "" -#: ../system/integrations/i-doit.rst:28 +#: ../system/core-workflows/learn-by-example.rst:7 msgid "" -"i-doit integration puts a new tab in Zammad's ticket pane where you can add " -"links to existing i-doit devices for easy reference. (See our :user-docs:" -"`user documentation ` to learn " -"how it works in practice)." +"To learn about Core Workflows in detail, first go to :doc:`how-do-they-work`." msgstr "" -#: ../system/integrations/i-doit.rst:36 ../system/integrations/i-doit.rst:93 -msgid "How to Set it Up" -msgstr "" +#: ../system/core-workflows/learn-by-example.rst:10 +#, fuzzy +msgid "Group Based Examples" +msgstr "Exemple" -#: ../system/integrations/i-doit.rst:38 +#: ../system/core-workflows/learn-by-example.rst:12 msgid "" -"It requires i-doit's `API Add-on `_. Make sure to have it properly set up. Use the following setting:" +"All following workflows have the same base configurations. The workflow may " +"not use them all." msgstr "" -#: ../system/integrations/i-doit.rst:42 -msgid "Active: ``Yes``" +#: ../system/core-workflows/learn-by-example.rst:15 +msgid "Groups:" msgstr "" -#: ../system/integrations/i-doit.rst:43 -msgid "Enforce authentication by username and password: ``No``" +#: ../system/core-workflows/learn-by-example.rst:20 +#, fuzzy +msgid "Attributes:" +msgstr "Attributs d'article" + +#: ../system/core-workflows/learn-by-example.rst:22 +msgid "Category (Single tree selection field, not mandatory, agents only)" msgstr "" -#: ../system/integrations/i-doit.rst:45 +#: ../system/core-workflows/learn-by-example.rst:23 msgid "" -"To set it up, enable the integration in the Zammad admin panel under " -"**System > Integrations > i-doit**:" +"Approved (Boolean field, not mandatory, not shown, ``false`` as default)" msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "i-doit settings within the integration pages" +#: ../system/core-workflows/learn-by-example.rst:24 +msgid "Operating System (Text field, not mandatory, not shown)" msgstr "" -#: ../system/integrations/i-doit.rst:53 -msgid "The root URL of your i-doit installation." +#: ../system/core-workflows/learn-by-example.rst:25 +msgid "Software used (Single selection field, not mandatory, not shown)" msgstr "" -#: ../system/integrations/i-doit.rst:62 -msgid "API token" +#: ../system/core-workflows/learn-by-example.rst:68 +msgid "Group specific values and fields" msgstr "" -#: ../system/integrations/i-doit.rst:56 +#: ../system/core-workflows/learn-by-example.rst:28 msgid "" -"Found in the i-doit admin panel under **Interfaces / external data > JSON-" -"RPC API > Common Settings**." +"This workflow set depends on the category field. It reduces the available " +"set of values based on the group selected." msgstr "" -#: ../system/integrations/i-doit.rst:0 -msgid "i-doit administration interface with API configuration" +#: ../system/core-workflows/learn-by-example.rst:33 +msgid "Workflow 2nd Level group" msgstr "" -#: ../system/integrations/i-doit.rst:67 -msgid "Client ID" +#: ../system/core-workflows/learn-by-example.rst:35 +msgid "" +"This reduces the category options to ``2nd Level/*``, ``Internal/*`` and " +"``Others``. It also sets further required fields to mandatory and visible." msgstr "" -#: ../system/integrations/i-doit.rst:65 -msgid "A unique name to identify Zammad within i-doit." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for 2nd level" msgstr "" -#: ../system/integrations/i-doit.rst:67 -msgid "(Zammad does not require you to enter a value here, but i-doit might!)" +#: ../system/core-workflows/learn-by-example.rst:43 +msgid "Workflow Support group" msgstr "" -#: ../system/integrations/i-doit.rst:70 +#: ../system/core-workflows/learn-by-example.rst:45 msgid "" -"Here you can decide if the certificate of your i-doit system has to be " -"verified or not. In case you are using custom certificates, please have a " -"look at :doc:`how to add them to Zammad `." +"This reduces the category options to ``Support/*``, ``Internal/*`` and " +"``Others``. It also sets further required fields to visible." msgstr "" -#: ../system/integrations/i-doit.rst:77 -msgid "2. List / Create Zammad Tickets in i-doit" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for support" msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "Zammad integration in i-doit's device view" +#: ../system/core-workflows/learn-by-example.rst:53 +msgid "Workflow Sales group" msgstr "" -#: ../system/integrations/i-doit.rst:86 +#: ../system/core-workflows/learn-by-example.rst:55 msgid "" -"i-doit's ticket system integration gives you a way to see all the tickets " -"for a given device without ever leaving i-doit. (See our :user-docs:`user " -"documentation ` to learn how it " -"works in practice)." +"This reduces the category options to ``Sales/*``, ``Internal/*`` and " +"``Others``." msgstr "" -#: ../system/integrations/i-doit.rst:95 +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for sales" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:68 +#: ../system/integrations/slack.rst:88 +msgid "The Result" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:63 msgid "" -"Enable this integration in the i-doit admin panel under **Interfaces / " -"external data > Trouble Ticket System (TTS) > Configuration**:" +"This is what the agent would experience with the above workflows in place." msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "i-doit administration interface with TTS configuration" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "" +"Workflow shows objects and limits options based on selections on the group" msgstr "" -#: ../system/integrations/i-doit.rst:104 -msgid "TTS-Type" +#: ../system/core-workflows/learn-by-example.rst:90 +msgid "Approval process" msgstr "" -#: ../system/integrations/i-doit.rst:104 -msgid "``Zammad``" +#: ../system/core-workflows/learn-by-example.rst:71 +msgid "" +"In this case ``approved`` is visible to agents by default. For this " +"workflow, an additional role ``Approval person`` is required (no further " +"permissions)." msgstr "" -#: ../system/integrations/i-doit.rst:115 -msgid "Username / Password" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that restricts an approval attribute to specific roles" msgstr "" -#: ../system/integrations/i-doit.rst:107 -msgid "Login credentials for a Zammad agent." +#: ../system/core-workflows/learn-by-example.rst:81 +msgid "" +"This workflow may work best in combination with a :doc:`trigger ` but technically, this is not required." msgstr "" -#: ../system/integrations/i-doit.rst:109 +#: ../system/core-workflows/learn-by-example.rst:84 msgid "" -"This agent must have **read permission** for all :doc:`groups ` that plan on using the i-doit integration." +"Select fields may be a better approach because they allow more values than " +"just a simple ``true`` or ``false``." msgstr "" -#: ../system/integrations/i-doit.rst:113 +#: ../system/core-workflows/learn-by-example.rst:0 msgid "" -"You may even wish to create a dedicated agent account just for this " -"integration (otherwise, if the agent ever changes her password, you will " -"have to remember to update it here)." +"Workflow fixes possible values of \"Approved ?\" to a specific selection " +"depending on the users role" msgstr "" -#: ../system/integrations/i-doit.rst:117 -msgid "URL incl. protocol" +#: ../system/core-workflows/learn-by-example.rst:103 +msgid "State dependent mandatory fields" msgstr "" -#: ../system/integrations/i-doit.rst:118 -msgid "``https://your.zammad.domain``" +#: ../system/core-workflows/learn-by-example.rst:93 +msgid "" +"This workflow sets ``Category`` to mandatory if the agent wants to set the " +"states ``closed`` or ``pending close`` to enforce categorization." msgstr "" -#: ../system/integrations/index.rst:2 -msgid "Integrations" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that sets fields to mandatory on specific states" msgstr "" -#: ../system/integrations/index.rst:4 +#: ../system/core-workflows/learn-by-example.rst:0 msgid "" -"Zammad offers numerous integrations that add rich features to your instance." +"Workflow sets category field to mandatory upon choosing closed or pending " +"close as state" msgstr "" -#: ../system/integrations/index.rst:6 -msgid "We're still working on this part of our documentation, stay tight!" +#: ../system/core-workflows/learn-by-example.rst:106 +msgid "Manual Ticket Handover Process" msgstr "" -#: ../system/integrations/index.rst:10 -msgid "Integrations for Phone Systems" +#: ../system/core-workflows/learn-by-example.rst:108 +msgid "This example covers the handover of a ticket from one agent to another:" msgstr "" -#: ../system/integrations/index.rst:14 +#: ../system/core-workflows/learn-by-example.rst:110 msgid "" -"Your VoIP provider or telephony system is not listed? Possibly your provider " -"supports Zammad by using the generic CTI - if you're unsure ask your " -"provider." +"When the ticket owner is modified, a new text field (\"Handover\") shows up " +"for a comment" msgstr "" -#: ../system/integrations/index.rst:18 +#: ../system/core-workflows/learn-by-example.rst:112 msgid "" -"Provider does not support Zammad? Consider creating a `feature request in " -"the Zammad Community `_." +"This may only be visible when the owner is changed, therefore it has to be " +"hidden in general" msgstr "" -#: ../system/integrations/index.rst:31 -msgid "Integrations for Authentication and Customers" +#: ../system/core-workflows/learn-by-example.rst:114 +msgid "The input in this handover text field is mandatory" msgstr "" -#: ../system/integrations/index.rst:44 -msgid "Integrations for Monitoring Systems" +#: ../system/core-workflows/learn-by-example.rst:115 +msgid "" +"After submitting changes, the value of the handover field must be added as " +"an note to the ticket (via trigger)" msgstr "" -#: ../system/integrations/index.rst:46 -msgid "This section currently misses the following integrations:" +#: ../system/core-workflows/learn-by-example.rst:121 +msgid "Hiding handover field" msgstr "" -#: ../system/integrations/index.rst:48 -msgid "Icinga" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Hiding the handover field in core workflows" msgstr "" -#: ../system/integrations/index.rst:49 -msgid "Monit" +#: ../system/core-workflows/learn-by-example.rst:126 +msgid "Showing handover field and setting it to mandatory" msgstr "" -#: ../system/integrations/index.rst:50 -msgid "Nagios" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Showing the handover field and set it as mandatory" msgstr "" -#: ../system/integrations/index.rst:60 -msgid "Integrations for Issue Trackers" +#: ../system/core-workflows/learn-by-example.rst:131 +msgid "Trigger writing handover input to a new article" msgstr "" -#: ../system/integrations/index.rst:70 -msgid "Other Integrations" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Write handover content to a new article" msgstr "" -#: ../system/integrations/index.rst:72 +#: ../system/core-workflows/learn-by-example.rst:133 msgid "" -"This section will hold any other integration that can't be grouped up (yet)." +"As a result, the ticket includes an article of the type note which includes " +"the predefined text and the handover comment." msgstr "" -#: ../system/integrations/ldap/index.rst:2 -msgid "LDAP / Active Directory" +#: ../system/core-workflows/limitations.rst:6 +msgid "Core Workflows do not replace Triggers" msgstr "" -#: ../system/integrations/ldap/index.rst:4 +#: ../system/core-workflows/limitations.rst:5 msgid "" -"Zammad comes with a powerful LDAP integration that allows you to have a " -"single source of truth. By this you reduce the number of login credentials " -"your user has to remember." +"Workflows manipulate the behavior of fields. However, they do not set values " +"in fields because of actions." msgstr "" -#: ../system/integrations/ldap/index.rst:10 +#: ../system/core-workflows/limitations.rst:16 +msgid "API calls are only partly affected" +msgstr "" + +#: ../system/core-workflows/limitations.rst:9 msgid "" -"The LDAP source is also a perfect candidate for Zammad's :docs:`Kerberos " -"Single Sign-On ` but also works as addition " -"to other :doc:`/settings/security/third-party`." +"Some options affect UI only and thus do not restrict responses and calls." msgstr "" -#: ../system/integrations/ldap/index.rst:None -msgid "Zammands LDAP management page" +#: ../system/core-workflows/limitations.rst:11 +msgid "This affects the following actions:" msgstr "" -#: ../system/integrations/ldap/index.rst:25 -#, fuzzy -msgid "📝 :doc:`manage`" -msgstr "Dernière valeur de contact utilisée à :doc:`/manage/trigger`" +#: ../system/core-workflows/limitations.rst:13 +msgid "select" +msgstr "" -#: ../system/integrations/ldap/index.rst:25 -msgid "Add, modify, remove or re-arrange your LDAP-Sources as needed." +#: ../system/core-workflows/limitations.rst:14 +msgid "auto select" msgstr "" -#: ../system/integrations/ldap/index.rst:30 -msgid "Before you continue, please note the following limitations." +#: ../system/core-workflows/limitations.rst:15 +msgid "show" +msgstr "" + +#: ../system/core-workflows/limitations.rst:16 +msgid "hide" msgstr "" -#: ../system/integrations/ldap/index.rst:32 -msgid "Mapping / Synchronizing organizations is not possible" +#: ../system/core-workflows/limitations.rst:25 +msgid "Some fields stay unavailable to customers" msgstr "" -#: ../system/integrations/ldap/index.rst:36 +#: ../system/core-workflows/limitations.rst:19 msgid "" -"You may want to consider using domain based assignments to overcome this " -"issue. Learn more on :doc:`/manage/organizations/index`." +"For technical and security reasons, some default fields (the pale ones you " +"can't edit) stay unavailable for display and usage on customer permissions." msgstr "" -#: ../system/integrations/ldap/index.rst:39 +#: ../system/core-workflows/limitations.rst:23 msgid "" -"Zammad's LDAP sync is one way. Editing user settings or permissions may be " -"overwritten upon the next sync depending on your configuration." +"If you require your customers to change e.g. priorities, please consider " +"using workarounds via :doc:`/system/objects` and :doc:`/manage/trigger`." msgstr "" -#: ../system/integrations/ldap/index.rst:41 -msgid "Nested groups are not supported." +#: ../system/core-workflows/limitations.rst:29 +msgid "Ticket title changes not supported in edit mask" msgstr "" -#: ../system/integrations/ldap/index.rst:42 -msgid "Synchronizing user avatars from LDAP is not supported." +#: ../system/core-workflows/limitations.rst:28 +msgid "" +"It is currently not possible to perform changes of the ticket title in the " +"edit mask (e.g. renaming, set to read-only)." msgstr "" -#: ../system/integrations/ldap/index.rst:43 -msgid "Unlike user filters, group filters cannot be changed." +#: ../system/core-workflows/limitations.rst:37 +msgid "What is out of scope of Core Workflows?" msgstr "" -#: ../system/integrations/ldap/index.rst:44 +#: ../system/core-workflows/limitations.rst:32 msgid "" -"When a user originates from an LDAP server, Zammad will try to verify the " -"login credentials against LDAP first - if this fails Zammad will check its " -"local database." +"There are some things that would count as workflow but are either done via :" +"doc:`/manage/trigger` or :doc:`/manage/scheduler`." msgstr "" -#: ../system/integrations/ldap/index.rst:50 -msgid "" -"Users can have local passwords even if they're LDAP users! You can learn " -"more about user accounts in general on :doc:`/manage/users/index`." +#: ../system/core-workflows/limitations.rst:35 +msgid "Such as (but not limited to):" msgstr "" -#: ../system/integrations/ldap/index.rst:54 -msgid "" -"When several LDAP sources contain the same user (meaning the same email " -"address), the user in question will be updated with every source configured. " -"*The last LDAP source will win.*" +#: ../system/core-workflows/limitations.rst:37 +msgid "up- or downgrade permissions of users" msgstr "" -#: ../system/integrations/ldap/index.rst:58 -#, fuzzy -msgid "" -"This is subject to change with `Issue 4109 `_ in the future." +#: ../system/core-workflows/limitations.rst:38 +msgid "affecting article creation or listing" msgstr "" -"Actuellement non disponible, voir `Issue 2769 `_" -#: ../system/integrations/ldap/index.rst:60 -msgid "" -"Synchronization statistics currently affect *all* configured LDAP sources. " -"This also applies for newly added or updated sources." +#: ../system/data-privacy.rst:2 +msgid "Data Privacy" msgstr "" -#: ../system/integrations/ldap/index.rst:63 -#, fuzzy +#: ../system/data-privacy.rst:4 msgid "" -"This is subject to change with `Issue 4108 `_ in the future." +"For compliance with GDPR and other data privacy laws, you may wish to " +"**permanently delete users from the system**, along with **all of their " +"associated tickets**." msgstr "" -"Actuellement non disponible, voir `Issue 2769 `_" -#: ../system/integrations/ldap/index.rst:65 +#: ../system/data-privacy.rst:8 msgid "" -"Zammad currently has limited fallback server support. You can workaround " -"this by providing several sources - however, ensure to have the exact same " -"configuration on your fallback." +"You can create manual deletion tasks or even automated deletion tasks for " +"tickets and users based on custom conditions via :doc:`scheduler `!" msgstr "" -#: ../system/integrations/ldap/index.rst:69 -#, fuzzy +#: ../system/data-privacy.rst:12 msgid "" -"This is subject to improve with `Issue 4107 `_ in the future." +"Access to this panel requires ``admin.data_privacy`` permissions (introduced " +"in Zammad 3.5)." msgstr "" -"Actuellement non disponible, voir `Issue 2769 `_" -#: ../system/integrations/ldap/index.rst:76 +#: ../system/data-privacy.rst:15 msgid "" -"This section holds all requests Zammad handled for all LDAP sources. These " -"entries can either contain synchronization information or logins " -"(authentication attempts via Zammad's login interface)." +"On older systems that have not been updated yet, customers can also be :docs:" +"`deleted via the Zammad console `." msgstr "" -#: ../system/integrations/ldap/index.rst:80 -msgid "" -"By clicking on any request, Zammad will provide even more information. The " -"provided information can be useful when something does not work as expected." +#: ../system/data-privacy.rst:22 +msgid "User deletion dialog in the Data Privacy panel" msgstr "" -#: ../system/integrations/ldap/index.rst:85 +#: ../system/data-privacy.rst:22 msgid "" -"Especially a LDAP synchronization can cause many log entries. The web " -"interface will always limit the number of shown entries to the last 50 " -"entries." +"The user deletion dialog lists some of the tickets that will be removed from " +"the system along with the user." msgstr "" -#: ../system/integrations/ldap/index.rst:None -msgid "" -"Screencast showing LDAP integration log entries and a detail view on\n" -"an entry." +#: ../system/data-privacy.rst:27 +#, fuzzy +msgid "Deleting Users via GUI" +msgstr "Bloquer les notifications" + +#: ../system/data-privacy.rst:29 +msgid "🔥 **All deletions are FINAL!**" msgstr "" -#: ../system/integrations/ldap/manage.rst:2 -msgid "Manage LDAP-Sources" +#: ../system/data-privacy.rst:31 +msgid "Once you click “Delete”, the action cannot be canceled or undone." msgstr "" -#: ../system/integrations/ldap/manage.rst:6 +#: ../system/data-privacy.rst:33 msgid "" -"Please keep in mind all current limitations for the LDAP synchronization. " -"This will help to understand scopes of the following operations better." +"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." msgstr "" -#: ../system/integrations/ldap/manage.rst:65 -msgid "Add new source" +#: ../system/data-privacy.rst:36 +msgid "**The following records cannot be deleted:**" msgstr "" -#: ../system/integrations/ldap/manage.rst:10 -msgid "" -"Using the *New Source* button allows you to add new LDAP sources to your " -"installation. You're not limited in the number of sources, however, keep in " -"mind that many sources will also take more time to synchronize." +#: ../system/data-privacy.rst:38 +msgid "your own account" msgstr "" -#: ../system/integrations/ldap/manage.rst:14 -msgid "" -"You can choose between different encryption types, namely *SSL* and " -"*STARTTLS* or none of them (\"*No SSL*\"). If you choose *SSL* or " -"*STARTTLS*, Zammad will display an additional *SSL verification* option that " -"allows you to disable the verification, e.g. for self-signed SSL " -"certificates. You can also tell Zammad to use a different port by appending " -"``:`` to your hostname/IP." +#: ../system/data-privacy.rst:39 +msgid "the system's last remaining administrator account" msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "" -"Screenshot of configuring a new LDAP source with SSL encryption and SSL " -"verification" +#: ../system/data-privacy.rst:42 +msgid "Step 1: Find a User / Confirm Deletion" msgstr "" -#: ../system/integrations/ldap/manage.rst:26 -msgid "" -"New Source with SSL transport security enabled and certificate verification" +#: ../system/data-privacy.rst:44 +msgid "There are three ways to access the user deletion dialog:" msgstr "" -#: ../system/integrations/ldap/manage.rst:30 -msgid "" -"Using an user filter can be a good idea if you only require a small subset " -"of your LDAP users in Zammad." +#: ../system/data-privacy.rst:51 +msgid "**from the user's profile**" msgstr "" -#: ../system/integrations/ldap/manage.rst:42 -msgid "This especially affects inactive users" +#: ../system/data-privacy.rst:0 +msgid "Accessing the user deletion dialog in a user profile" msgstr "" -#: ../system/integrations/ldap/manage.rst:34 -msgid "" -"As every LDAP behaves differently on which attributes and how they are set, " -"Zammad doesn't care about any flags." +#: ../system/data-privacy.rst:51 +msgid "Click **Action > Delete**." msgstr "" -#: ../system/integrations/ldap/manage.rst:37 -msgid "" -"Users that no longer are returned by your LDAP source will automatically be " -"set to inactive. Zammad assumes that the user was deactivated." +#: ../system/data-privacy.rst:58 +msgid "**in the “Manage > Users” Admin Panel**" msgstr "" -#: ../system/integrations/ldap/manage.rst:41 -msgid "" -"Users will never be removed automatically! If you want to remove obsolete " -"users, use :doc:`/system/data-privacy`." +#: ../system/data-privacy.rst:0 +msgid "Accessing the user deletion dialog under “Users” in the Admin Panel" msgstr "" -#: ../system/integrations/ldap/manage.rst:46 -msgid "Active Directory admins" +#: ../system/data-privacy.rst:58 +msgid "Use the **⋮ Actions** menu for the target user." msgstr "" -#: ../system/integrations/ldap/manage.rst:45 -msgid "" -"Active Directories are quite specific on how to filter for active users only " -"- please see the `Microsoft documentation `_ for more " -"information." +#: ../system/data-privacy.rst:66 ../system/data-privacy.rst:104 +msgid "**in the “System > Data Privacy” Admin Panel**" msgstr "" -#: ../system/integrations/ldap/manage.rst:51 +#: ../system/data-privacy.rst:0 msgid "" -"*Do not* manually write pathes of either LDAP attributes or groups. If " -"Zammad does not display them, it either cannot find them or you have a lot " -"of users that don't have the attributes populated." +"Accessing the user deletion dialog under “Data Privacy” in the Admin Panel" msgstr "" -#: ../system/integrations/ldap/manage.rst:55 +#: ../system/data-privacy.rst:65 msgid "" -"Zammad will always only return attributes that are filled - this reduces the " -"returned list of attributes greatly." +"Use the **New Deletion Task** button. Search for users by name or email " +"address." msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing how to add a new LDAP source" -msgstr "" +#: ../system/data-privacy.rst:79 +#, fuzzy +msgid "**Delete organizations**" +msgstr "Billet > Organisation > Note" -#: ../system/integrations/ldap/manage.rst:63 +#: ../system/data-privacy.rst:69 msgid "" -"If your LDAP system doesn't allow anonymous bind, Zammad detects it and " -"provides you an editable \"Base DN\" *text* field instead of a prefilled " -"*select* field." -msgstr "" - -#: ../system/integrations/ldap/manage.rst:81 -msgid "Review or edit existing source" +"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:" msgstr "" -#: ../system/integrations/ldap/manage.rst:68 -msgid "" -"Clicking on a LDAP source will provide a configuration and mapping overview." +#: ../system/data-privacy.rst:0 +msgid "Deleting an organization via the user deletion dialog" msgstr "" -#: ../system/integrations/ldap/manage.rst:70 +#: ../system/data-privacy.rst:78 msgid "" -"If needed you can then use the *Change* button to update either the name, " -"active state or the whole configuration. If you're changing the whole " -"configuration, the dialogue will be identical to the source creation." +"If this option does not appear, make sure there are no pending deletion " +"tasks for other customers from this organization." msgstr "" -#: ../system/integrations/ldap/manage.rst:76 -msgid "" -"Did your LDAP server change? Different LDAP servers have different " -"structures and default attributes. This causes the LDAP synchronization to " -"likely fail. Consider removing the affected source and re-add it." +#: ../system/data-privacy.rst:82 +msgid "Step 2: Monitor Deletion Job Status" msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing the update of the source name." +#: ../system/data-privacy.rst:84 +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:" msgstr "" -#: ../system/integrations/ldap/manage.rst:89 -msgid "Re-arrange LDAP source's order" +#: ../system/data-privacy.rst:98 +msgid "**in the Activity Stream**" msgstr "" -#: ../system/integrations/ldap/manage.rst:84 -msgid "" -"You can change the synchronization order for each source at any time. Zammad " -"will synchronize the sources from top to bottom." +#: ../system/data-privacy.rst:0 +msgid "Activity Stream showing data privacy tasks" msgstr "" -#: ../system/integrations/ldap/manage.rst:0 +#: ../system/data-privacy.rst:94 msgid "" -"Screencasting showing how to change the source order by using\n" -"drag and drop." +"For each deleted user, the Activity Stream will be updated twice—once when " +"the task is created, and once when it's complete." msgstr "" -#: ../system/integrations/ldap/manage.rst:101 -msgid "Remove a source" +#: ../system/data-privacy.rst:97 +msgid "" +"These notifications are only visible to users with ``admin.data_privacy`` " +"permissions." msgstr "" -#: ../system/integrations/ldap/manage.rst:92 +#: ../system/data-privacy.rst:0 msgid "" -"If you no longer need the a LDAP source or simply want to start over, you " -"can remove them at any time. This will not remove synchronized users, data " -"synchronized or permissions." +"The task list within Data Privacy shows removals being in progress and " +"completed." msgstr "" -#: ../system/integrations/ldap/manage.rst:98 -msgid "" -"Not sure if you'd need the source later on? Set the source to inactive " -"instead of removing it - see *Review or edit existing source* for more." +#: ../system/data-privacy.rst:107 +msgid "Frequently Asked Questions" msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing how to remove LDAP sources." +#: ../system/data-privacy.rst:121 +msgid "What happens if I receive an email from a deleted customer?" msgstr "" -#: ../system/integrations/pgp/index.rst:2 -msgid "PGP" +#: ../system/data-privacy.rst:110 +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/integrations/pgp/index.rst:7 +#: ../system/data-privacy.rst:115 msgid "" -"Pretty Good Privacy (PGP) is another method for secure email communication. " -"With PGP, you can exchange **signed** and **encrypted** messages with others." +"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**." msgstr "" -#: ../system/integrations/pgp/index.rst:13 -#: ../system/integrations/smime/index.rst:17 -msgid "Signing" +#: ../system/data-privacy.rst:130 +msgid "What about user information stored in internal notes or other messages?" msgstr "" -#: ../system/integrations/pgp/index.rst:11 -msgid "is a proof that a message hasn't been manipulated on its way." +#: ../system/data-privacy.rst:124 +msgid "" +"The deletion process removes **user accounts and associated tickets only**." msgstr "" -#: ../system/integrations/pgp/index.rst:13 +#: ../system/data-privacy.rst:126 msgid "" -"In other words, it guarantees message **integrity** and **authenticity**." +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:19 -#: ../system/integrations/smime/index.rst:22 -msgid "Encryption" +#: ../system/data-privacy.rst:137 +msgid "I deleted an user and can still see a message they sent!" msgstr "" -#: ../system/integrations/pgp/index.rst:16 -#: ../system/integrations/smime/index.rst:20 +#: ../system/data-privacy.rst:133 msgid "" -"scrambles a message so that it can only be unscrambled by the intended " -"recipient." +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:19 +#: ../system/data-privacy.rst:141 +msgid "I removed a customer, now my reporting is off!" +msgstr "" + +#: ../system/data-privacy.rst:140 msgid "" -"In other words, it guarantees message **privacy** and **data security**." +"When removing users and their tickets, all references are removed. This also " +"affects e.g. Reporting - these information are lost." msgstr "" -#: ../system/integrations/pgp/index.rst:25 -msgid "Screenshot of ticket creation with encrypt and sign buttons" +#: ../system/data-privacy.rst:145 +msgid "How long does Zammad store created tasks?" msgstr "" -#: ../system/integrations/pgp/index.rst:25 +#: ../system/data-privacy.rst:144 msgid "" -"Once PGP has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " -"appear in the ticket composer." +"Please see the on-premise data section of the :docs:`data privacy ` chapter." msgstr "" -#: ../system/integrations/pgp/index.rst:28 -msgid "**Sign button not visible?**" +#: ../system/data-privacy.rst:150 +msgid "What about re-assigned tickets? I want to delete them, too." msgstr "" -#: ../system/integrations/pgp/index.rst:30 +#: ../system/data-privacy.rst:148 msgid "" -"Please note that the signing of emails is based on the outgoing email " -"account. That means you have to choose a group with a sender email account, " -"which has a private key assigned." +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:35 -msgid "Handling of Keys" +#: ../system/data-privacy.rst:154 +msgid "Why are there so many deletion task entries, I didn't create them!" msgstr "" -#: ../system/integrations/pgp/index.rst:36 +#: ../system/data-privacy.rst:153 msgid "" -"To use the PGP function, you have to enable the integration (PGP) by " -"switching the toggle to *enabled*." +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:39 -msgid "" -"You can add keys by clicking the *add key* button. The keys can be imported " -"from a file or you can paste the content of the key in the text box." +#: ../system/integrations/checkmk/admin-panel-reference.rst:2 +msgid "Admin Panel Reference" msgstr "" -#: ../system/integrations/pgp/index.rst:42 -msgid "**Which keys do I have to import?**" +#: ../system/integrations/checkmk/admin-panel-reference.rst:None +msgid "Screenshot of Checkmk settings overview" msgstr "" -#: ../system/integrations/pgp/index.rst:44 +#: ../system/integrations/checkmk/admin-panel-reference.rst:12 msgid "" -"For **signing** *outgoing* emails, you have to import the private key of " -"your Zammad email account." +"Which :doc:`group ` should Checkmk tickets be assigned " +"to as a default (*i.e.,* when none is specified)?" msgstr "" -#: ../system/integrations/pgp/index.rst:47 -msgid "" -"For **encrypting** *outgoing* emails, you have to import the public key of " -"the customer's email account." +#: ../system/integrations/checkmk/admin-panel-reference.rst:15 +msgid "(Applies to :ref:`API alerts ` only.)" msgstr "" -#: ../system/integrations/pgp/index.rst:50 -msgid "" -"For **verifying the signature** of signed *incoming* emails, you have to " -"import the public key of the customer." +#: ../system/integrations/checkmk/admin-panel-reference.rst:21 +msgid "Auto close" msgstr "" -#: ../system/integrations/pgp/index.rst:53 +#: ../system/integrations/checkmk/admin-panel-reference.rst:18 msgid "" -"For **decrypting** of encrypted *incoming* emails, you have to import the " -"private key of your Zammad email account." +"Should Zammad automatically close tickets if a service has recovered on its " +"own?" msgstr "" -#: ../system/integrations/pgp/index.rst:57 -msgid "Import Keys From a File" +#: ../system/integrations/checkmk/admin-panel-reference.rst:21 +msgid "(Agents will receive notifications for such closures as appropriate.)" msgstr "" -#: ../system/integrations/pgp/index.rst:58 -msgid "You can import keys from a file in the section **Upload key**:" +#: ../system/integrations/checkmk/admin-panel-reference.rst:30 +msgid "Auto-close state" msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of adding a key via file" +#: ../system/integrations/checkmk/admin-panel-reference.rst:24 +msgid "What ticket state should be applied when “auto-closing” a ticket?" msgstr "" -#: ../system/integrations/pgp/index.rst:64 +#: ../system/integrations/checkmk/admin-panel-reference.rst:26 msgid "" -"**Supported file formats:** ASCII-armor as well as binary GPG format " -"(basically any GPG supported key format) is supported here." +"You can choose from the seven built-in ticket states. If these states aren't " +"enough for you, you can :ref:`define a new ticket state ` for this purpose as well. This can be useful for tracking " +"tickets with :doc:`reports `, for example." msgstr "" -#: ../system/integrations/pgp/index.rst:68 -msgid "Import Keys by Pasting the Content" +#: ../system/integrations/checkmk/admin-panel-reference.rst:35 +#: ../system/integrations/cti/includes/recent-logs.include.rst:2 +#: ../system/integrations/ldap/index.rst:74 +#: ../system/integrations/pgp/index.rst:106 +msgid "Recent Logs" msgstr "" -#: ../system/integrations/pgp/index.rst:69 -msgid "You can also paste the key's content in the section **paste key**:" +#: ../system/integrations/checkmk/admin-panel-reference.rst:None +msgid "Screenshot of Checkmk \"Recent Logs\" section" msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of adding a key via pasting" +#: ../system/integrations/checkmk/admin-panel-reference.rst:41 +msgid "" +"If you're having trouble getting Zammad and Checkmk to play nicely together, " +"this section can help you troubleshoot." msgstr "" -#: ../system/integrations/pgp/index.rst:75 +#: ../system/integrations/checkmk/admin-panel-reference.rst:44 msgid "" -"**Supported format:** Please note that only ASCII-armor is supported here." +"It contains a record of the fifty most recent transactions that Zammad knows " +"about, including each one's request/response details and return status." msgstr "" -#: ../system/integrations/pgp/index.rst:78 -#, fuzzy -msgid "Deleting Keys" -msgstr "Bloquer les notifications" +#: ../system/integrations/checkmk/api-reference.rst:2 +msgid "API Reference" +msgstr "" -#: ../system/integrations/pgp/index.rst:79 +#: ../system/integrations/checkmk/api-reference.rst:4 msgid "" -"If you want to delete a specific key, you can do it by clicking on the menu " -"in the *actions* column and select **delete**:" +"For most users, :ref:`the sample scripts from the Setup Guide ` will do the job just fine. But if you want more fine-grained control" +"—for instance, to create high- and low-priority tickets for different types " +"of system events—then you'll have to customize the data those scripts send " +"to Zammad." msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of deleting a key" +#: ../system/integrations/checkmk/api-reference.rst:15 +msgid "" +"This custom script will automatically set all tickets it creates to **high " +"priority** and **assign them to charlie@chrispresso.com**." msgstr "" -#: ../system/integrations/pgp/index.rst:88 -msgid "Downloading Keys" +#: ../system/integrations/checkmk/api-reference.rst:32 +msgid "How Does it Work?" msgstr "" -#: ../system/integrations/pgp/index.rst:89 +#: ../system/integrations/checkmk/api-reference.rst:34 msgid "" -"If you want to download your keys, you can do this as well via corresponding " -"action buttons. Depending on the key, you can choose wether you want to " -"download the private or the public key." +"There are two kinds of data you can pass to the API, both in the form of key-" +"value pairs:" msgstr "" -#: ../system/integrations/pgp/index.rst:95 -#: ../system/integrations/smime/manage-certificates.rst:76 -msgid "Default Behavior" +#: ../system/integrations/checkmk/api-reference.rst:44 +msgid "Checkmk parameters" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:38 +msgid "" +"are required, and make up the **contents** of the resulting tickets/" +"articles. They also determine whether an event creates a new ticket or " +"updates/closes an existing one." msgstr "" -#: ../system/integrations/pgp/index.rst:96 +#: ../system/integrations/checkmk/api-reference.rst:42 msgid "" -"Here you can adjust on per group basis, if *sign* and *encryption* is on or " -"off by default. Please be aware, that agents can always override the setting " -"for each individual article." +"These are the only values used in the sample scripts. **Use them as-is**; " +"technically, they can be customized, but it's hard to imagine a good reason " +"for it." msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Adjusting default behavior on per group basis" -msgstr "" +#: ../system/integrations/checkmk/api-reference.rst:52 +msgid "Ticket attributes" +msgstr "Attributs d'un billet" -#: ../system/integrations/pgp/index.rst:107 +#: ../system/integrations/checkmk/api-reference.rst:47 msgid "" -"Here you can see the last actions regarding signing and encryption and if " -"they were successful." +"are optional, and can be used to **adjust settings** on newly created " +"tickets (*e.g.,* set the owner, group, priority, or state)." msgstr "" -#: ../system/integrations/pgp/index.rst:117 -msgid "**Sign button is not visible, but keys are imported.**" +#: ../system/integrations/checkmk/api-reference.rst:50 +msgid "" +"If you want to customize your Checkmk alert script, do it with these. Simply " +"add an extra “form” option for each one (``-F \"key=value\"``) to your " +"script's ``curl`` command line, as in the example above." msgstr "" -#: ../system/integrations/pgp/index.rst:115 -msgid "Did you choose a group in the ticket?" +#: ../system/integrations/checkmk/api-reference.rst:54 +msgid "💡 **It's just an API endpoint!**" msgstr "" -#: ../system/integrations/pgp/index.rst:116 +#: ../system/integrations/checkmk/api-reference.rst:56 msgid "" -"Did you import a private key for the email adress, which is used for " -"outgoing emails in the group?" -msgstr "" - -#: ../system/integrations/pgp/index.rst:122 -msgid "**How to obtain keys?**" +"When using Checkmk integration, messages need to be formatted in a certain " +"way, but that *doesn't mean the messages actually have to come from Checkmk*." msgstr "" -#: ../system/integrations/pgp/index.rst:120 +#: ../system/integrations/checkmk/api-reference.rst:59 msgid "" -"You can create them yourself! There are some good tutorials on the web on " -"how to create them. Providing keys to Zammad is a prerequisite to use the " -"PGP feature." +"If you use another monitoring tool that's not officially supported by " +"Zammad, there's probably a way to make it work with your Checkmk callback " +"URL." msgstr "" -#: ../system/integrations/pgp/index.rst:127 -msgid "**It says a passphrase is needed, but I haven't got one.**" +#: ../system/integrations/checkmk/api-reference.rst:63 +msgid "Checkmk Parameters" msgstr "" -#: ../system/integrations/pgp/index.rst:125 +#: ../system/integrations/checkmk/api-reference.rst:65 msgid "" -"If the key is secured with a passphrase, you have to provide it for the " -"import in Zammad. It is possible that keys may have an empty passphrase. " -"However, this is *not* recommended." +"When a notification is received, Zammad creates a new article containing the " +"details of the event that triggered it:" msgstr "" -#: ../system/integrations/pgp/index.rst:132 -msgid "**How do my customers get my new key?**" +#: ../system/integrations/checkmk/api-reference.rst:None +msgid "Checkmk article body" msgstr "" -#: ../system/integrations/pgp/index.rst:130 +#: ../system/integrations/checkmk/api-reference.rst:72 msgid "" -"You have to provide your **public** key in advance. Your customer also has " -"to configure PGP in their email workflow and import your public key. The " -"other way round, you have to get the public key of your customer and have to " -"import it to Zammad." +"These details come from the fields listed below, which correspond to " +"parameters provided by Checkmk (``$NOTIFY_*``)." msgstr "" -#: ../system/integrations/slack.rst:2 -msgid "Slack" +#: ../system/integrations/checkmk/api-reference.rst:75 +msgid "**Required fields are marked with an asterisk (\\*).**" msgstr "" -#: ../system/integrations/slack.rst:4 -msgid "**⚠️ Deprecation warning ⚠️**" +#: ../system/integrations/checkmk/api-reference.rst:79 +msgid "event_id\\*" msgstr "" -#: ../system/integrations/slack.rst:6 +#: ../system/integrations/checkmk/api-reference.rst:78 msgid "" -"Zammad 7 will no longer support this dedicated Slack integration. It is " -"recommended to switch to :doc:`pre-defined webhooks ` instead. Existing Slack integrations should " -"be migrated manually before this feature is dropped." +"A unique ID for the system event. (``$NOTIFY_SERVICEPROBLEMID`` / " +"``$NOTIFY_HOSTPROBLEMID``)" msgstr "" -#: ../system/integrations/slack.rst:14 -msgid "" -"In order to use this feature, please add a new Slack app to your Workspace. " -"The App you need is called ``Incoming WebHooks`` ." +#: ../system/integrations/checkmk/api-reference.rst:86 +msgid "host\\*" msgstr "" -#: ../system/integrations/slack.rst:18 -msgid "Why Do I Need This Feature?" +#: ../system/integrations/checkmk/api-reference.rst:82 +msgid "" +"The hostname of the system that the event originated from. " +"(``$NOTIFY_HOSTNAME``)" msgstr "" -#: ../system/integrations/slack.rst:20 +#: ../system/integrations/checkmk/api-reference.rst:85 msgid "" -"If you're already using Slack for your team communication, you'll love this " -"feature! Our Slack integration can push ticket notifications about the last " -"ticket article based on the following events:" +"Used to determine if a new event belongs to an existing ticket. Also used in " +"the subject line of the resulting article (“ is ”)." msgstr "" -#: ../system/integrations/slack.rst:24 -msgid "on Ticket creation" +#: ../system/integrations/checkmk/api-reference.rst:96 +msgid "service" msgstr "" -#: ../system/integrations/slack.rst:25 -msgid "on Ticket updates" +#: ../system/integrations/checkmk/api-reference.rst:89 +msgid "" +"The name of the service that the event originated from. " +"(``$NOTIFY_SERVICEDESC``)" msgstr "" -#: ../system/integrations/slack.rst:26 -msgid "on reached reminders" +#: ../system/integrations/checkmk/api-reference.rst:92 +msgid "Used to determine if a new event belongs to an existing ticket." msgstr "" -#: ../system/integrations/slack.rst:27 -msgid "a Ticket has escalated" +#: ../system/integrations/checkmk/api-reference.rst:94 +#: ../system/integrations/checkmk/api-reference.rst:110 +msgid "Displayed as ``-`` when omitted." msgstr "" -#: ../system/integrations/slack.rst:28 -msgid "a Ticket is going to escalate" +#: ../system/integrations/checkmk/api-reference.rst:104 +msgid "state\\*" msgstr "" -#: ../system/integrations/slack.rst:30 +#: ../system/integrations/checkmk/api-reference.rst:99 msgid "" -"Zammad will provide the Ticket title, a direct link to the Ticket, the event " -"type (creation, updated, escalation), the customer, time and the last " -"article that has triggered the notification." +"The current state of the service or host in question. " +"(``$NOTIFY_SERVICESTATE`` / ``$NOTIFY_HOSTSTATE``)" msgstr "" -#: ../system/integrations/slack.rst:34 +#: ../system/integrations/checkmk/api-reference.rst:102 msgid "" -"This will give you further options, as you can see e.g. escalating tickets " -"that are assigned to an agent that's e.g. absent. You can interact faster, " -"as you might see problems earlier (or even before the problem gets one)." +"Used to detect when a ticket should be auto-closed (*i.e.,* on ``OK``/" +"``UP``). Also used in the subject line of the resulting article (“ is " +"”)." msgstr "" -#: ../system/integrations/slack.rst:38 -msgid "" -"If needed and wanted, you can even discuss directly about the topic before " -"sending an answer to the customer. Another possible use case would be a " -"agent monitoring new agents and their answers to tickets." +#: ../system/integrations/checkmk/api-reference.rst:110 +msgid "text" msgstr "" -#: ../system/integrations/slack.rst:44 -#, fuzzy -msgid "Configure the Integration" -msgstr "Configuration du greffon de clavardage" - -#: ../system/integrations/slack.rst:46 +#: ../system/integrations/checkmk/api-reference.rst:107 msgid "" -"First of all, please go to your slack workspace - go to administration => " -"Manage Apps. If you don't have an app yet, you can simply add a new one - " -"just search for ``Incoming WebHooks`` and customize the app to your needs." +"The output of the process that triggered the event. " +"(``$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" msgstr "" -#: ../system/integrations/slack.rst:50 +#: ../system/integrations/checkmk/api-reference.rst:121 msgid "" -"Choose (or create) the channel Zammad should post it's information to and " -"press on \"Add Incoming WebHooks integration\". If you're ready, copy the " -"provided WebHook URL and go to your Zammad installation." +"The Object Manager attribute panel displays built-in and custom\n" +"attribute names." msgstr "" -#: ../system/integrations/slack.rst:56 -msgid "" -"You need administrative rights on the Slack Workspace. The link to the app " -"directory is normally ``https://[workspace-name].slack.com/apps`` ." +#: ../system/integrations/checkmk/api-reference.rst:121 +msgid "Find a complete list of ticket attributes in the Object Manager." msgstr "" -#: ../system/integrations/slack.rst:63 +#: ../system/integrations/checkmk/api-reference.rst:123 msgid "" -"To configure the slack integration, log in to Zammad and go to Integrations " -"(System) => Slack in the admin panel." +"Ticket attributes are entirely optional, and can be used to customize the " +"tickets that Checkmk creates. (Note that these attributes will be ignored if " +"a new event belongs to an existing ticket.)" msgstr "" -#: ../system/integrations/slack.rst:66 +#: ../system/integrations/checkmk/api-reference.rst:128 msgid "" -"Here you can choose on what evens Zammad should post information about a " -"ticket to your Slack channel. Next you need to device what groups shall be " -"affected by this, as anybody with access to that specific Slack channel can " -"read at least parts of the ticket this might be a privacy issue, if you " -"select the wrong groups. The username is simply the name that Zammad uses as " -"display name inside the Slack chat. The channel defines the Slack channel " -"the information is being posted in. As last option, you can set a custom " -"icon for posting to slack." +"Why would you want to do this? Maybe you have only one IT guy, and all " +"system monitoring issues should be automatically assigned to him. Or, maybe " +"you're creating multiple notification rules so that database outages take " +"higher priority than disk space warnings." msgstr "" -#: ../system/integrations/slack.rst:74 -msgid "" -"When you're ready, just hit \"Submit\" and enable the integration. Zammad " -"will now post new ticket information based on the trigger you chose. Below " -"the options you have the recent log that shows the latest requests to Slack " -"for debugging if needed." +#: ../system/integrations/checkmk/api-reference.rst:135 +msgid "In most cases, you'll probably want to set one of the following:" msgstr "" -#: ../system/integrations/slack.rst:81 -msgid "" -"If you leave the Icon URL empty, Zammad will use the Zammad logo instead. " -"The icon should be a square PNG file." +#: ../system/integrations/checkmk/api-reference.rst:137 +msgid "group" msgstr "" -#: ../system/integrations/slack.rst:90 -msgid "" -"The following figure shows how it will look if you choose to receive updates " -"on created and updated tickets. On every post Zammad sends to the Slack " -"channel, you can create new threads to discuss about the new article." +#: ../system/integrations/checkmk/api-reference.rst:139 +msgid "state" msgstr "" -#: ../system/integrations/slack.rst:96 -msgid "" -"If you just want to keep track of soon escalating or already escalated " -"tickets, it will look the the following figure. Zammad changes the color in " -"front of the post so you can easily see the state of the ticket." +#: ../system/integrations/checkmk/api-reference.rst:140 +msgid "priority" msgstr "" -#: ../system/integrations/slack.rst:102 +#: ../system/integrations/checkmk/api-reference.rst:142 msgid "" -"If you change the state, Zammad will also put information on what state the " -"ticket gets and (if pending state) the date until it pends. You'll also " -"recognize the color codes in front of posts on slack, as they are exact the " -"same the ticket state colors you'll see in Zammad!" +"but in practice, you can set almost any attribute, including :doc:`custom " +"ones you created through the Object Manager `." msgstr "" -#: ../system/integrations/smime/index.rst:2 -msgid "S/MIME" +#: ../system/integrations/checkmk/api-reference.rst:145 +msgid "Please note that the following attributes are **not customizable**:" msgstr "" -#: ../system/integrations/smime/index.rst:11 -msgid "" -"S/MIME is the most widely-supported method for secure email communication. " -"With S/MIME, you can exchange **signed** and **encrypted** messages with " -"others." +#: ../system/integrations/checkmk/api-reference.rst:147 +msgid "title" msgstr "" -#: ../system/integrations/smime/index.rst:15 -msgid "" -"is proof that a message hasn't been tampered with or sent by an impersonator." +#: ../system/integrations/checkmk/api-reference.rst:148 +msgid "id" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:149 +msgid "ticket number" msgstr "" -#: ../system/integrations/smime/index.rst:17 -msgid "" -"In other words, it guarantees a message's **integrity** and **authenticity**." +#: ../system/integrations/checkmk/api-reference.rst:151 +msgid "created_by_id" msgstr "" -#: ../system/integrations/smime/index.rst:22 -msgid "In other words, it guarantees **privacy** and **data security**." +#: ../system/integrations/checkmk/api-reference.rst:152 +msgid "updated_by_id" msgstr "" -#: ../system/integrations/smime/index.rst:28 -msgid "Screencast demo of S/MIME features for both new tickets and replies" +#: ../system/integrations/checkmk/api-reference.rst:155 +msgid "Which Values Can Be Set?" msgstr "" -#: ../system/integrations/smime/index.rst:28 +#: ../system/integrations/checkmk/api-reference.rst:157 +msgid "😵 **Invalid values → unpredictable behavior**" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:159 msgid "" -"Once S/MIME has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " -"appear in the ticket composer." +"If you provide a value that Zammad doesn't understand (*e.g.,* ``-F " +"\"priority=high\"``), it's not always clear what will happen. In some cases, " +"a ticket will be created with the default values instead - but in others, it " +"may not be created at all!" msgstr "" -#: ../system/integrations/smime/index.rst:32 -msgid ":doc:`🔪 Prerequisites `" +#: ../system/integrations/checkmk/api-reference.rst:164 +msgid "So what values does Zammad understand, then? Well, it depends..." msgstr "" -#: ../system/integrations/smime/index.rst:31 -msgid "" -"New to S/MIME? This section helps you to find certificate providers and " -"points out Limitations." +#: ../system/integrations/checkmk/api-reference.rst:168 +msgid "Use an email address or username:" msgstr "" -#: ../system/integrations/smime/index.rst:35 -msgid ":doc:`📝 Manage Certificates `" +#: ../system/integrations/checkmk/api-reference.rst:190 +msgid "group & priority" msgstr "" -#: ../system/integrations/smime/index.rst:35 -msgid "Add and download certificates; configure group default behaviors." +#: ../system/integrations/checkmk/api-reference.rst:175 +msgid "Refer to the dropdown menus in the ticket pane:" msgstr "" -#: ../system/integrations/smime/index.rst:38 -msgid ":doc:`😦 Troubleshooting `" +#: ../system/integrations/checkmk/api-reference.rst:0 +msgid "See possible values for certain attributes in the ticket pane." msgstr "" -#: ../system/integrations/smime/index.rst:38 -msgid "Took a wrong turn? About recent logs and common issues." +#: ../system/integrations/checkmk/api-reference.rst:187 +msgid "🙅 **Ticket state CANNOT be set this way!**" msgstr "" -#: ../system/integrations/smime/index.rst:43 +#: ../system/integrations/checkmk/api-reference.rst:189 msgid "" -"For more details on how S/MIME integration works on the agent side, see the :" -"user-docs:`user docs `." +"Why? Because ``-F \"state=...\"`` is already used :ref:`as a Checkmk " +"parameter `." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:2 -msgid "Manage Certificates" +#: ../system/integrations/checkmk/api-reference.rst:222 +msgid "Everything Else" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:4 +#: ../system/integrations/checkmk/api-reference.rst:193 msgid "" -"S/MIME is **disabled by default**. Enable it to start adding certificates." +"To set any other attributes, it helps to know your way around the :docs:" +"`rails console `. Valid values are those that you can " +"set with a string:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:10 -msgid "Dialogue to add new certificates or private keys" +#: ../system/integrations/checkmk/api-reference.rst:218 +msgid "These values can then be passed directly to the API:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:10 -msgid "" -"Manage certificates in the Admin Panel under **System > Integrations > S/" -"MIME**. Certificates may be pasted in as plain text or uploaded from a file." +#: ../system/integrations/checkmk/index.rst:16 +msgid "How does it work?" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:14 -#, fuzzy -msgid "Add Certificate Data" -msgstr "Bloquer les notifications" - -#: ../system/integrations/smime/manage-certificates.rst:36 -msgid "Add Certificate" +#: ../system/integrations/checkmk/index.rst:2 +msgid "Checkmk" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:17 +#: ../system/integrations/checkmk/index.rst:4 msgid "" -"Import public-key certificates for both your own organization and your " -"contacts." +"`Checkmk `_ is a powerful IT monitoring tool that can " +"send real-time status alerts to Zammad via email or REST API. Set these " +"alerts up in Checkmk, and Zammad will automatically create, update, and " +"close tickets based on the health of your system:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:19 -msgid "" -"You can also add a bunch of certificates in one go by providing a single " -"file with all relevant certificates." +#: ../system/integrations/checkmk/index.rst:14 +msgid "Screenshot of ticket created by Checkmk notifications" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:22 -msgid "🕵️ **ALWAYS verify certificates in-person or over the phone!**" +#: ../system/integrations/checkmk/index.rst:14 +msgid "Multiple alerts, same ticket." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:24 -msgid "" -"The whole point of signatures is to alert you when someone is trying to " -"pretend to be someone they're not. Never accept a certificate from someone " -"online without verifying it first." +#: ../system/integrations/checkmk/setup-guide.rst:2 +msgid "Setup Guide" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:28 -msgid "📇 **What about trusted certificate authorities?**" +#: ../system/integrations/checkmk/setup-guide.rst:4 +msgid "" +"Whenever the Checkmk integration is enabled, Zammad listens for messages on " +"its API and over email. As long as those messages follow the required " +"format, Zammad will create new tickets (or find and update existing ones) " +"based on the message contents." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:30 +#: ../system/integrations/checkmk/setup-guide.rst:10 msgid "" -"In some cases (e.g. when dealing with large enterprises), you may be given a " -"certificate for an entire CA, rather than a single contact. Add it here to " -"trust *all* certificates issued by that CA." +"That means that “setting up Checkmk integration” is simply a matter of " +"**adding configuration to your Checkmk site**: telling it when to send these " +"messages and what to say. To do that, you'll need to create a new " +"**notification rule** (see `Checkmk's official docs `_ for help with that)." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:35 +#: ../system/integrations/checkmk/setup-guide.rst:17 msgid "" -"Commercial CAs can usually be verified online. Zammad does not include a " -"list of built-in, trusted CAs." +"As part of this new rule, you'll have to choose a **notification method** " +"(*i.e.,* a script to execute whenever the rule is triggered). This script " +"will be written by you (samples below), and contain the logic for sending " +"API/email messages to Zammad:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:57 -msgid "Add Private Key" +#: ../system/integrations/checkmk/setup-guide.rst:26 +msgid "Checkmk \"New Rule\" dialog" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:39 +#: ../system/integrations/checkmk/setup-guide.rst:26 msgid "" -"Once you've added a public-key certificate, you can import its matching " -"private key." +"Find your custom scripts in the Checkmk WATO under **Notifications > New " +"Rule > Notification Method**." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:42 +#: ../system/integrations/checkmk/setup-guide.rst:29 msgid "" -"Private keys are for **your own organization only**; never ask your contacts " -"for their private keys." +"Once you're done setting up your new rule, you're all set! New tickets " +"should start coming in and auto-updating any time your rule is triggered." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:0 +#: ../system/integrations/checkmk/setup-guide.rst:33 msgid "" -"S/MIME integration showing configured certificates and possible issues with " -"Logging" +"(If you need help troubleshooting, be sure to check the :ref:`checkmk-recent-" +"logs`.)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:50 +#: ../system/integrations/checkmk/setup-guide.rst:38 +msgid "API Alerts" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:40 msgid "" -"A note is displayed on certificates with a matching private key (see line 2)." +"To add these scripts in the Checkmk WATO, copy them into your Checkmk " +"installation directory and make them executable. (Be sure to replace the " +"``zammad.example.com`` callback URL with the one found in your admin panel.)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:52 -msgid "📤 **Certificates and private keys must be uploaded separately.**" +#: ../system/integrations/checkmk/setup-guide.rst:60 +msgid "Service notification" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:54 +#: ../system/integrations/checkmk/setup-guide.rst:46 msgid "" -"If your certificate and private key are bundled together in the same file or " -"PEM block, import it twice (once using each button)." +"For updates on the status of the software running on your server (*e.g.,* " +"postgres)." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:57 -msgid "Please note that bulk imports of private keys are not possible." +#: ../system/integrations/checkmk/setup-guide.rst:75 +msgid "Host notification" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:60 -#, fuzzy -msgid "Download Certificate Data" -msgstr "Bloquer les notifications" +#: ../system/integrations/checkmk/setup-guide.rst:63 +msgid "For updates on the status of the server itself." +msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:62 -msgid "" -"You can download the earlier provided certificates and private keys at any " -"time from your Zammad instance." +#: ../system/integrations/checkmk/setup-guide.rst:77 +msgid "🤔 **What's with all the env vars?**" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:65 +#: ../system/integrations/checkmk/setup-guide.rst:79 msgid "" -"Please note that passphrase-protected private keys stay protected and when " -"you download them, you have to know the passphrase to use them after " -"downloading." +"Whenever Checkmk runs these scripts, it needs to provide some information " +"about the event that triggered the notification. This information is passed " +"in the form of these ``$NOTIFY_*`` environment variables." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:73 -msgid "Dialogue to download certificates or private keys" +#: ../system/integrations/checkmk/setup-guide.rst:85 +msgid "" +"You can specify additional parameters to pass to the script when you're " +"setting up your notification rule, but the ones you see here are all " +"provided by default." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:73 -msgid "Download stored certificates and their keys" +#: ../system/integrations/checkmk/setup-guide.rst:90 +msgid "Email Alerts" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:78 +#: ../system/integrations/checkmk/setup-guide.rst:94 msgid "" -"The ticket composer will set all outgoing messages to **signed and " -"encrypted** by default (assuming the required certificates exist)." +"🐞 **There are known bugs** in Zammad's processing of email from Checkmk. " +"This section will be completed once they have been resolved. (Learn more at " +"GitHub issues `#2377 `_ & " +"`#2180 `_.)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:82 -msgid "These defaults can be modified on a per-group basis:" +#: ../system/integrations/checkmk/setup-guide.rst:100 +msgid "In the meantime, we encourage you to set up API alerts instead." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:None -msgid "Zammad allowing to choose the default behavior on per group basis" +#: ../system/integrations/clearbit.rst:2 +msgid "Clearbit" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:89 +#: ../system/integrations/clearbit.rst:4 msgid "" -"Of course, agents can always manually change these settings on each email " -"they send out." +"With our Clearbit integration, you can easily enrich the information " +"provided by Zammad. If the customers or agents email address is known to " +"Clearbit, it will share all information it has regarding the user with " +"Zammad. Those information can include the following:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:4 -msgid "A certificate *and* private key for your own organization" +#: ../system/integrations/clearbit.rst:9 +msgid "Avatar" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:6 -msgid "" -"(Use this to ✒️ **sign outgoing messages** and 🔓 **decrypt incoming " -"messages**.)" +#: ../system/integrations/clearbit.rst:10 +msgid "Address information" +msgstr "" + +#: ../system/integrations/clearbit.rst:11 +msgid "Website information" +msgstr "" + +#: ../system/integrations/clearbit.rst:12 +msgid "A BIO (as Note by default)" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:9 +#: ../system/integrations/clearbit.rst:14 msgid "" -"Certificates belonging your contacts, or their issuing certificate authority " -"(CA)" +"If needed, you can add further custom objects and add mappings to them, so " +"the Clearbit information can be filled within the database. In general you " +"can get any information from Clearbit, as long as you have a mapping to an " +"Zammad object." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:11 +#: ../system/integrations/clearbit.rst:21 msgid "" -"(Use these to ✅ **verify incoming message signatures** and 🔒 **encrypt " -"outgoing messages**.)" +"Clearbit does have a mapping of fields like LDAP and Exchange have, but does " +"not \"win\" against Zammad information. This means that if you have e.g. the " +"last name field filled in already and Clearbit has other information on " +"that, it will not be updated." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:14 -msgid "🙋 **I'm new to S/MIME. Where can I get a certificate?**" +#: ../system/integrations/clearbit.rst:26 +msgid "" +"However: If let's say the last name has been set by Clearbit and Zammad " +"notices that the last name on the Clearbit source has changed, Zammad will " +"also update this value." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:16 +#: ../system/integrations/clearbit.rst:33 msgid "" -"The easiest way to get certificates is to buy an annual subscription through " -"a commercial CA, such as:" +"The configuration of Clearbit is really easy and done fast! Just login to " +"your Clearbit-Account, go to \"API\" and copy the secret-API-Key." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:19 +#: ../system/integrations/clearbit.rst:38 msgid "" -"`Sectigo (formerly Comodo) `_" +"Now change to your Zammad instance, go to Integrations (System) -> Clearbit " +"in the admin panel. Paste your API-Key into the API-Key-Field and decide if " +"Zammad should create unknown Organizations automatically, if the user does " +"not have one yet (and Clearbit knows it). The shared option decides if the " +"new organizations Zammad creates with Clearbit should be shared ones." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:20 -msgid "`Secorio `_" +#: ../system/integrations/clearbit.rst:47 +msgid "" +"If you're unsure what option to choose, better stick with \"no\". You can " +"also learn more about :doc:`/manage/organizations/index`." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:21 -msgid "`GlobalSign `_" +#: ../system/integrations/clearbit.rst:52 +msgid "" +"The Mapping option works similar to the mapping within the Exchange and LDAP " +"sync. You can add further mappings for e.g. custom fields if you need more " +"information that Clearbit can provide." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:23 -msgid "(Zammad is not affiliated with these CAs in any way.)" +#: ../system/integrations/clearbit.rst:58 +msgid "" +"If you want to add more Clearbit fields and want to learn more about " +"available fields on their API, you can take a look at their `API " +"documentation `_." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:25 +#: ../system/integrations/clearbit.rst:62 msgid "" -"You can also generate your own self-signed certificates, but the process is " -"complicated and usually 🙅 **involves extra work for your contacts**." +"If you're happy with the above chosen Settings and your mapping, just save " +"the changes and enable Clearbit integration. Zammad will now start polling " +"the Clearbit API as users contact you." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:29 +#: ../system/integrations/clearbit.rst:68 msgid "" -"Bear in mind that 🤝 **S/MIME only works if the other party is using it, too." -"**" +"Zammad does not synchronize with Clearbit on a regular basis, but on demand " +"if needed. This saves API calls." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:32 -msgid "Certificate and Private Key Checks on Upload" +#: ../system/integrations/clearbit.rst:73 +msgid "" +"Below the Settings and Mappings, you'll find our Integration log. You can " +"see what requests Zammad sent to Clearbit and also the APIs Response." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:34 +#: ../system/integrations/clearbit.rst:78 msgid "" -"The certificate and public key validation is based on the ``X509v3`` " -"extensions." +"By the way, you can also view the API log on the Clearbit website - the " +"information seen is basically the same." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:49 -msgid "Uploading a *client certificate*?" +#: ../system/integrations/clearbit.rst:84 +msgid "Example When Adding a User" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:41 -msgid "The following attributes are required then:" +#: ../system/integrations/clearbit.rst:86 +msgid "" +"To show you how fast information is added, we added a small Screencast " +"below. This shows the creation of the User Alex from Clearbit. As we already " +"set the last name of Alex to \"X\", Zammad did not update it. What Zammad " +"did was to add further information it received from Clearbit." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:39 -msgid "Subject Alternative Name (at least one email address has to be present)" +#: ../system/integrations/cti/generic.rst:2 +msgid "CTI (generic)" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:40 -msgid "Key Usage (``Digital Signature`` and/or ``Key Encipherment``)" +#: ../system/integrations/cti/includes/introduction.include.rst:1 +msgid "" +"This integration enables Zammad to provide a caller log to your agents. With " +"this your agents can greet your customers by their name and are supported by " +"Zammad with automatically opening a new ticket dialog or the user profile." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:41 -msgid "Public key algorithm (either ``RSA`` or ``EC``)" +#: ../system/integrations/cti/includes/introduction.include.rst:6 +msgid "" +"Click the toggle next to the heading to activate or deactivate this " +"integration." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:43 +#: ../system/integrations/cti/includes/introduction.include.rst:9 msgid "" -"The Extended Key Usage attribute is optional. If the certificate provides " -"the named attribute, than it must contain the value ``E-mail Protection``." +"If you want to learn more on how your agents can use this function, please " +"refer the :user-docs:`user documentation `." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:46 +#: ../system/integrations/cti/includes/introduction.include.rst:14 msgid "" -"Please note that any usable email adress has to be prefixed with ``email:`` " -"or ``rfc822:``." +"Automatically opening new ticket dialogues or user profiles requires agent " +"to extension mapping - see more below." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:49 -msgid "The named public key algorithms are mandatory for private keys as well." +#: ../system/integrations/cti/includes/introduction.include.rst:20 +msgid "Please note the following limitations to reduce confusion later on:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:54 -msgid "Uploading a *CA certificate*?" +#: ../system/integrations/cti/includes/introduction.include.rst:22 +msgid "CTI integrations provide caller log functions only." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:52 +#: ../system/integrations/cti/includes/introduction.include.rst:23 msgid "" -"In the case of an uploaded CA certificate, providing the value ``CA:TRUE`` " -"in the attribute *Basic Contstraints*, the previously mentioned attributes " -"are not verified." +"This integration does not provide any VoIP functionalities; you can't make " +"phone calls from within Zammad." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:56 +#: ../system/integrations/cti/includes/introduction.include.rst:25 msgid "" -"In general, the usage of any expired (``Not After``) or not yet valid (``Not " -"Before``) certificate is denied for outgoing emails." +"If your browser supports ``tel``-URLs, you can click on phone numbers for " +"automatic dialing. This requires additional software / configuration on your " +"agent's computers." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:59 -msgid "Example certificate:" +#: ../system/integrations/cti/generic.rst:9 +#: ../system/integrations/cti/placetel.rst:14 +#: ../system/integrations/cti/sipgate.rst:14 +msgid "Please provide the following requirements:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:85 +#: ../system/integrations/cti/generic.rst:11 msgid "" -"Please note that Zammad will distrust senders by default. This means that " -"you're always required to provide certificate data, no matter if for signing " -"or encrypting." -msgstr "" - -#: ../system/integrations/smime/prerequisites.rst:89 -msgid "This is by design and can't be adjusted." +"A telephone system that supports webhooks (outbound) (best option are those " +"that allow customizing the calls)." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:4 -msgid "" -"All of the system's latest S/MIME activity is displayed in the **Recent " -"Logs** section." +#: ../system/integrations/cti/generic.rst:13 +msgid "A unique Call-ID during the call session." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:11 -msgid "Sample entries of in- and outgoing S/MIME related emails." +#: ../system/integrations/cti/generic.rst:14 +msgid "Call event data (both numbers and direction)." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:11 -msgid "" -"Logs report the status and details of all mail, both incoming and outgoing, " -"that used signing/verification or encryption/decryption." +#: ../system/integrations/cti/generic.rst:15 +msgid "Your Zammad instance must be reachable for your telephony system." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:14 +#: ../system/integrations/cti/generic.rst:17 msgid "" -"This log does **not** include email sent by :doc:`triggers ` or the :doc:`scheduler `. For those, check your " -"``production.log``." +"If you want to learn more on what kind of requests are supported by Zammad " +"and what it expects, please consult our :docs:`CTI-API documentation `." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:20 -msgid "Common Issues" -msgstr "" +#: ../system/integrations/cti/generic.rst:22 +#: ../system/integrations/cti/placetel.rst:27 +#: ../system/integrations/cti/sipgate.rst:30 +#, fuzzy +msgid "Available Settings" +msgstr "Réglages avancés" -#: ../system/integrations/smime/troubleshooting.rst:30 -msgid "I received a signed/encrypted email before I set up S/MIME integration" -msgstr "" +#: ../system/integrations/cti/generic.rst:29 +#: ../system/integrations/cti/placetel.rst:41 +#: ../system/integrations/cti/sipgate.rst:40 +#, fuzzy +msgid "Endpoint Settings" +msgstr "Liste des réglages" -#: ../system/integrations/smime/troubleshooting.rst:23 +#: ../system/integrations/cti/generic.rst:25 msgid "" -"No problem. Once S/MIME has been enabled and the appropriate certificates " -"have been added, agents will be prompted to retry verification/decryption on " -"matching emails." -msgstr "" - -#: ../system/integrations/smime/troubleshooting.rst:0 -msgid "Screenshot of user prompt to retry decryption" +"Zammad will list your generic CTI endpoint here. It contains a unique token " +"so ensure to keep this URL save." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:38 -msgid "The 🔒 **Encrypt** button is disabled" +#: ../system/integrations/cti/generic.rst:28 +msgid "" +"You'll need this endpoint for your PBX to talk to Zammad, see :docs:`CTI-API " +"documentation `." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:33 -msgid "Have you added the recipient's certificate?" +#: ../system/integrations/cti/includes/important-dont-forget-saving.include.rst:3 +msgid "" +"All following options **do not save automatically**. Always use the Save " +"button on the lower end of the integration page!" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:34 -msgid "Are you sure the recipient's certificate is valid?" -msgstr "" +#: ../system/integrations/cti/generic.rst:43 +#: ../system/integrations/cti/placetel.rst:49 +#: ../system/integrations/cti/sipgate.rst:52 +#, fuzzy +msgid "Call Settings" +msgstr "Réglages" -#: ../system/integrations/smime/troubleshooting.rst:35 -msgid "Have you checked your ``production.log`` for more details?" +#: ../system/integrations/cti/generic.rst:39 +#: ../system/integrations/cti/placetel.rst:49 +#: ../system/integrations/cti/sipgate.rst:37 +#: ../system/integrations/cti/sipgate.rst:50 +msgid "Inbound" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:37 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:1 msgid "" -"If encryption doesn't work in the composer, it won't work in :doc:`triggers " -"` or the :doc:`scheduler ` either!" +"This option allows you to block specific incoming caller IDs. It allows you " +"to temporarily reject e.g. spam callers without having to contact providers " +"or PBX administrators." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:42 -msgid "The ✅ **Sign** button is disabled" +#: ../system/integrations/cti/includes/inbound-calls.include.rst:11 +msgid "Caller ID to block" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:41 -msgid "" -"Have you added **both the certificate and private key** for your " -"organization?" +#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 +msgid "Provide caller IDs to block in ``E.164`` format." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:42 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:8 msgid "" -"Does the email address on the certificate match the email address of the " -"agent/group composing the email?" +"Your telephony system has to support this function. Zammad will send a " +"``reject`` response which will cause your telephony system to hang up the " +"call. To callers this usually will feel like the line is busy." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:45 -msgid "Error: “Fingerprint already taken”" +#: ../system/integrations/cti/includes/inbound-calls.include.rst:14 +msgid "" +"Provide a meaningful note for your fellow administrators to remind yourself " +"why you've chosen to block the number." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:45 -msgid "Are you sure you haven't added this certificate already?" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:17 +#: ../system/integrations/cti/sipgate.rst:40 +msgid "Outbound" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:48 -msgid "Error: “❌ invalid byte sequence in UTF-8”" +#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:1 +msgid "" +"In many cases you may want to use a different caller ID depending on the " +"destination you're calling. This may apply due to specific connection rates " +"to other countries or because you want your customer to feel you're calling " +"from the same country." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:48 -msgid "Please ensure to provide PEM formatted certificate and keys." +#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:6 +msgid "This option expects ``E.164`` number formats." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:49 -msgid "Did you check if the provided file is a valid certificate or key?" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 +msgid "Destination caller ID" msgstr "" -#: ../system/integrations/zabbix.rst:2 -msgid "Zabbix Integration" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:5 +msgid "The caller ID or number you're trying to call." msgstr "" -#: ../system/integrations/zabbix.rst:5 -msgid "" -"This guide describes how to integrate your Zabbix 5.4 installation with " -"Zammad using the Zabbix webhook feature. This guide will provide " -"instructions on setting up a media type, a user and an action in Zabbix." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:7 +msgid "You can use wildcards for e.g. country specific outbound numbers like:" msgstr "" -#: ../system/integrations/zabbix.rst:12 -msgid "Zammad with enabled HTTP Token Authentication" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:9 +msgid "``49*`` for Germany" msgstr "" -#: ../system/integrations/zabbix.rst:13 -msgid "Zabbix version 5.4 or higher" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:10 +msgid "``4930*`` for Berlin / Germany landlines" msgstr "" -#: ../system/integrations/zabbix.rst:16 -msgid "Setting up a Zammad" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 +msgid "``33*`` for France" msgstr "" -#: ../system/integrations/zabbix.rst:18 -msgid "Enable **API Token Access** in Settings > System > API." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:15 +msgid "Set Outbound caller ID" msgstr "" -#: ../system/integrations/zabbix.rst:20 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:14 msgid "" -"Create a **new user** for a Zabbix alerter with an **email address** and " -"create a personal user token with **ticket.agent** permissions." +"The outbound caller ID to set (the number your customer sees on his display) " +"in ``E.164`` number format." msgstr "" -#: ../system/integrations/zabbix.rst:24 -#, fuzzy -msgid "Zabbix Webhook Configuration" -msgstr "Bloquer les notifications" - -#: ../system/integrations/zabbix.rst:27 -msgid "Create a Global Macro" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 +msgid "Provide a short description for fellow administrators." msgstr "" -#: ../system/integrations/zabbix.rst:29 +#: ../system/integrations/cti/includes/generic-cti-support-note.includes.rst:3 msgid "" -"Before setting up the **Webhook**, you need to setup the global macro " -"**{$ZABBIX.URL}**, which must contain the **URL** to the **Zabbix frontend**." +"This option requires your PBX to send a specific request to Zammad *before " +"dialing*. Please consult the :docs:`CTI API ` in case " +"you're not sure." msgstr "" -#: ../system/integrations/zabbix.rst:33 +#: ../system/integrations/cti/generic.rst:52 +#: ../system/integrations/cti/placetel.rst:54 +#: ../system/integrations/cti/sipgate.rst:59 +#, fuzzy +msgid "Other Settings" +msgstr "Réglages" + +#: ../system/integrations/cti/includes/other-settings-intro.include.rst:1 msgid "" -"In the **Administration** > **Media types** section, import the `Template`_." +"Below you can find all available additional settings for this CTI " +"integration. For your overview we're sorting them by appearance and " +"reference their description first." msgstr "" -#: ../system/integrations/zabbix.rst:38 -msgid "Open the added **Zammad** media type and set:" +#: ../system/integrations/cti/includes/default-caller-id.include.rst:2 +#: ../system/integrations/cti/includes/default-caller-id.include.rst:1 +msgid "Default caller ID for outbound calls" msgstr "" -#: ../system/integrations/zabbix.rst:40 -msgid "**zammad\\_access\\_token** to the your **Personal User Token**" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:16 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:15 +msgid "Shown records in caller log" msgstr "" -#: ../system/integrations/zabbix.rst:41 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:2 msgid "" -"**zammad\\_url** to the **frontend URL** of your **Zammad** installation" +"Allows you to set the number of shown caller log entries for all users. You " +"can choose from the following values:" msgstr "" -#: ../system/integrations/zabbix.rst:43 -msgid "**zammad\\_customer** to your **Zammad user email**." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:5 +msgid "60 (default)" msgstr "" -#: ../system/integrations/zabbix.rst:44 -msgid "" -"**zammad\\_enable\\_tags** to **true** or **false** to enable or disable " -"trigger tags. **Important**: if you enable tag support, each tag is set with " -"a separate request." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:6 +msgid "120" msgstr "" -#: ../system/integrations/zabbix.rst:48 -msgid "" -"If you want to prioritize issues according to **severity** values in Zabbix, " -"you can define mapping parameters:" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:7 +msgid "180" msgstr "" -#: ../system/integrations/zabbix.rst:51 -msgid "**severity\\_**: Zammad priority ID" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:8 +msgid "240" msgstr "" -#: ../system/integrations/zabbix.rst:53 -msgid "Click the **Update** button to save the **Webhook** settings." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:9 +msgid "300" msgstr "" -#: ../system/integrations/zabbix.rst:55 -msgid "" -"To receive notifications in **Zammad**, you need to create a **Zabbix user** " -"and add **Media** with the **Zammad** type." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:11 +msgid "**🥵 Potential performance issue**" msgstr "" -#: ../system/integrations/zabbix.rst:58 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:13 msgid "" -"For **Send to**: enter any text, as this value is not used, but is required." +"Setting this setting higher than 60 may cause serious performance issues on " +"very busy instances. Keep in mind that this setting causes Zammad to poll " +"and send up to 300 records to *all active agent sessions* in very short time " +"periods." msgstr "" -#: ../system/integrations/zabbix.rst:61 -msgid "" -"For more information, use the `Zabbix documentation `_." +#: ../system/integrations/cti/generic.rst:73 +msgid "Caller Log Filter" msgstr "" -#: ../system/maintenance.rst:2 -msgid "Maintenance" +#: ../system/integrations/cti/generic.rst:55 +msgid "" +"This function allows you to provide call information based on e.g. queues " +"only to agents that really need the information." msgstr "" -#: ../system/maintenance.rst:4 +#: ../system/integrations/cti/generic.rst:58 msgid "" -"Zammad comes with a maintenance mode that you can use for e.g. updating the " -"instance or changing settings while restricting availability and functions." +"Why? If you have a team for several countries or departments, you don't want " +"to bug your agents from other departments. Leaving these options empty will " +"fallback to showing everything to everyone." msgstr "" -#: ../system/maintenance.rst:13 -msgid "Mode" +#: ../system/integrations/cti/generic.rst:64 +msgid "Destination caller ID or Queue" msgstr "" -#: ../system/maintenance.rst:8 -#, fuzzy -msgid "The mode setting allows you to enable or disable the maintenance mode." +#: ../system/integrations/cti/generic.rst:63 +msgid "" +"This depends on your PBX and usually is either a queue ID, phone number or " +"extension." msgstr "" -"Avec ce paramètre, vous pouvez décider (si) où insérer le numéro de billet." -#: ../system/maintenance.rst:10 -msgid "Defaults to *off*." +#: ../system/integrations/cti/generic.rst:69 +msgid "Agents" msgstr "" -#: ../system/maintenance.rst:12 +#: ../system/integrations/cti/generic.rst:67 msgid "" -"The maintenance mode will restrict access to administrative roles only. This " -"means agents and customers are logged off." -msgstr "" - -#: ../system/maintenance.rst:23 -msgid "@Login" +"Select the agents that are responsible for the group. These agents will then " +"see caller log entries and call notifications fitting to said queue." msgstr "" -#: ../system/maintenance.rst:16 +#: ../system/integrations/cti/generic.rst:0 msgid "" -"This setting allows you to provide a login message within a green banner " -"above the login screen. Click into the green banner in the settings page to " -"adjust your message. To activate the message, activate the *@Login* setting." +"Screenshot showing the caller log filter table with pre filled sample data" msgstr "" -#: ../system/maintenance.rst:0 +#: ../system/integrations/cti/includes/recent-logs.include.rst:6 msgid "" -"Screenshot showing the default login message within the\n" -"settings page" +"With recent logs Zammad allows you to view the latest calls for the CTI " +"functionality. This usually comes in handy, when you're looking for errors." msgstr "" -#: ../system/maintenance.rst:26 +#: ../system/integrations/cti/includes/recent-logs.include.rst:0 msgid "" -"Send an informative message to **all active sessions**. This comes handy to " -"inform your agents e.g. about mayor outages or to force reloads after " -"configuration changes." +"Screenshot showing several incoming requests within Recent logs section." msgstr "" -#: ../system/maintenance.rst:31 -msgid "This is the messages title (slightly bigger than the normal message)." +#: ../system/integrations/cti/includes/recent-logs.include.rst:16 +msgid "I'm just here to clear floats up." msgstr "" -#: ../system/maintenance.rst:34 -msgid "The text you want to provide to your logged in sessions." +#: ../system/integrations/cti/includes/recent-logs.include.rst:20 +msgid "" +"By clicking on the entry of interest, Zammad will provide more details on " +"the call in question. You'll see the payload it received and also the " +"response that was sent." msgstr "" -#: ../system/maintenance.rst:39 -msgid "Reload application" +#: ../system/integrations/cti/includes/recent-logs.include.rst:0 +msgid "" +"Screenshot showing detailed information of a specific log entry of recent " +"logs" msgstr "" -#: ../system/maintenance.rst:37 -msgid "" -"Selecting this option will change the message acceptance button from *Close* " -"(with nothing happening) to *Continue session*, which forces the application " -"to reload." +#: ../system/integrations/cti/includes/recent-logs.include.rst:31 +msgid "x" msgstr "" -#: ../system/maintenance.rst:43 -msgid "" -"If you have customers that are logged in to Zammad, they'll also be notified " -"if they're active in that moment." +#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 +#: ../system/integrations/cti/includes/troubleshooting.include.rst:9 +msgid "My Phone page stays blank, signalling does work..." msgstr "" -#: ../system/maintenance.rst:48 -msgid "Example without reload application" +#: ../system/integrations/cti/includes/troubleshooting.include.rst:5 +msgid "" +"If you've made sure that signalling works (check Recent logs) and your " +"Caller Log still stays empty, please ensure that you only configured one CTI " +"integration version. Specifically defining more than one agent mapping on " +"the different integration variants will be the issue." msgstr "" -#: ../system/maintenance.rst:52 -msgid "" -"Message setting within Zammad's admin settings without ticket reload " -"application setting." +#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 +msgid "Clear the not needed agent mapping and reload your browser page." msgstr "" -#: ../system/maintenance.rst:0 +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:1 msgid "" -"Screenshot showing the send message settings without ticket\n" -"reload application set" +"By mapping your agents extension to their existing Zammad users, Zammad can " +"provide a new ticket dialog or open the user profile for the agent that " +"picks up the call." msgstr "" -#: ../system/maintenance.rst:61 ../system/maintenance.rst:85 +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:5 msgid "" -"The modal all other active sessions will see upon pressing *Send to clients*." +"This speeds up ticket aiding, no matter if it's for existing tickets or new " +"ones!" msgstr "" -#: ../system/maintenance.rst:0 +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:8 msgid "" -"Screenshot showing modal caused by maintenance's message\n" -"without reload application ticket" +"To see it work from the agent's perspective, have a look on :user-docs:`user " +"documentation `." msgstr "" -#: ../system/maintenance.rst:72 -msgid "Example with reload application" +#: ../system/integrations/cti/placetel.rst:2 +msgid "Placetel CTI" msgstr "" -#: ../system/maintenance.rst:76 -msgid "" -"Message setting within Zammad's admin settings with ticket reload " -"application setting." +#: ../system/integrations/cti/placetel.rst:16 +msgid "You need an administrative Placetel account for your organization." msgstr "" -#: ../system/maintenance.rst:0 +#: ../system/integrations/cti/placetel.rst:17 +#: ../system/integrations/cti/sipgate.rst:20 msgid "" -"Screenshot showing the send message settings with ticket\n" -"reload application set" +"Your Zammad instance must be allowed to communicate to external services." msgstr "" -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing modal caused by maintenance's message\n" -"with reload application ticket" +#: ../system/integrations/cti/placetel.rst:18 +msgid "Placetel must be able to reach your Zammad instance." msgstr "" -#: ../system/monitoring.rst:2 -msgid "Monitoring" +#: ../system/integrations/cti/placetel.rst:22 +msgid ":doc:`provider-configurations/placetel`" msgstr "" -#: ../system/monitoring.rst:4 +#: ../system/integrations/cti/placetel.rst:21 msgid "" -"This function is only available in self hosted instances. If you use Zammad " -"in our cloud, we are monitoring the system on our own and take steps to fix " -"potential problems directly." +"Learn how to configure Placetel to enable Zammad and Placetel to communicate " +"with each other." msgstr "" -#: ../system/monitoring.rst:11 +#: ../system/integrations/cti/placetel.rst:32 msgid "" -"On the monitoring page, you can see the current health state of Zammad under " -"\"*Current Status*\" at the bottom. This can be useful if you want to have a " -"look if everything is up and running. As an example, you could have a look " -"in the monitoring when you assume that some emails aren't processed from " -"Zammad." +"The here listed endpoint settings are relevant for the :doc:`integration " +"configuration with Placetel `." msgstr "" -#: ../system/monitoring.rst:17 -msgid "**Can't receive an email and the monitoring response is \"healthy\"?**" +#: ../system/integrations/cti/placetel.rst:37 +#: ../system/integrations/i-doit.rst:53 +msgid "Endpoint" msgstr "" -#: ../system/monitoring.rst:19 +#: ../system/integrations/cti/placetel.rst:36 msgid "" -"Zammad will just inform you about unprocessable emails. This is not the case " -"for oversized emails. You can adjust the maximum email size in :doc:`../" -"channels/email/settings`." +"This endpoint will be required for the Zammad integration within the " +"Placetel web interface." msgstr "" -#: ../system/monitoring.rst:24 -msgid "Monitoring API" +#: ../system/integrations/cti/placetel.rst:41 +msgid "API Token" msgstr "" -#: ../system/monitoring.rst:26 +#: ../system/integrations/cti/placetel.rst:40 msgid "" -"Beside the indication in the monitoring page, you can also use an external " -"monitoring tool to monitor Zammad's health. To request the health of Zammad, " -"you need to provide the API key (token) to the external monitoring tool. You " -"can copy the token from the \"*Current Token*\" field as well as the whole " -"API endpoint of your system (\"*Health Check*\" field), in which the API " -"token is already included." +"You'll receive this token within the ``Web API`` menu. Make sure to copy " +"this value, it's only shown once!" msgstr "" -#: ../system/monitoring.rst:37 -msgid "Screenshot showing Current Token and Health Check" +#: ../system/integrations/cti/placetel.rst:71 +#: ../system/integrations/cti/sipgate.rst:77 +msgid "Phone Extension to Agent Mapping" msgstr "" -#: ../system/monitoring.rst:37 -msgid "Screenshot showing Token and Health Check" +#: ../system/integrations/cti/placetel.rst:0 +msgid "Screenshot showing sample user mappings in between Placetel and Zammad" msgstr "" -#: ../system/monitoring.rst:39 +#: ../system/integrations/cti/placetel.rst:64 msgid "" -"In addition to that, you can reset the auto-generated token to make sure " -"that already configured monitoring systems won't work anymore. So, please " -"use this \"*Reset*\" button only if you know what you do!" +"You can find your agents Placetel username combination required within ⚙️ PBX " +"→ VoIP destinations. Within the \"Advanced settings\" section you're looking " +"for \"SIP user name\" and \"SIP server\"." msgstr "" -#: ../system/monitoring.rst:44 -#, fuzzy -msgid "Example Output" -msgstr "Exemple" - -#: ../system/monitoring.rst:0 -msgid "No issues found" +#: ../system/integrations/cti/placetel.rst:68 +msgid "Combine these two like so: ``@``." msgstr "" -#: ../system/monitoring.rst:48 ../system/monitoring.rst:60 -msgid "**Indicator in Zammad**:" +#: ../system/integrations/cti/placetel.rst:0 +msgid "Sample VoIP credentials for a Placetel user" msgstr "" -#: ../system/monitoring.rst:0 -msgid "Screenshot showing monitoring with no issues" +#: ../system/integrations/cti/provider-configurations/placetel.rst:2 +msgid "Setup Placetel connection for Zammad" msgstr "" -#: ../system/monitoring.rst:54 ../system/monitoring.rst:66 -msgid "**API response**::" +#: ../system/integrations/cti/provider-configurations/placetel.rst:6 +msgid "" +"This configuration step requires a *full* administrative Placetel account. " +"You may receive forbidden error messages with Placetel in case your " +"permissions are not high enough." msgstr "" -#: ../system/monitoring.rst:0 -msgid "Issues were found" +#: ../system/integrations/cti/provider-configurations/placetel.rst:10 +msgid "" +"The following actions can be configured via the `Placetel web interface " +"`_." msgstr "" -#: ../system/monitoring.rst:0 -msgid "Screenshot showing monitoring with issues" +#: ../system/integrations/cti/provider-configurations/placetel.rst:29 +msgid "Step 1: Activate Zammad integration" msgstr "" -#: ../system/objects.rst:2 -msgid "Objects" +#: ../system/integrations/cti/provider-configurations/placetel.rst:14 +msgid "" +"Within Integrations, scroll down to Partner integrations and select Zammad." msgstr "" -#: ../system/objects.rst:4 +#: ../system/integrations/cti/provider-configurations/placetel.rst:17 msgid "" -"In Zammad you can add your own fields to tickets, users, organizations and " -"even groups (these are called \"objects\"). This can be useful if you need " -"to add further information to a ticket or any other object in Zammad and the " -"information doesn't fit in any existing field." +"You can alternatively filter by \"Ticket Systems\" to reduce the number of " +"entries on the page. You'll still want to look for Partner integrations. 🤓" msgstr "" -#: ../system/objects.rst:11 +#: ../system/integrations/cti/provider-configurations/placetel.rst:21 msgid "" -"Try to avoid deleting attributes (and disable them instead) as Zammad might " -"run into unexpected conditions if they are referenced somewhere." +"Within the Zammad integration now press \"Activate\". A new tab ``API`` " +"becomes available - open this tab." msgstr "" -#: ../system/objects.rst:16 +#: ../system/integrations/cti/provider-configurations/placetel.rst:24 msgid "" -"Here's an overview of object attributes. On the upper right you can add new " -"attributes. By default, there will be no custom fields - standard attributes " -"will be grayed out, you can't delete or change those. You can edit custom " -"attributes (they are displayed in black font and have a trash bin on the " -"right side) just by clicking on them." +"Now tick \"Enable Call Control / Notify API\" and paste the Placetel " +"endpoint from your Zammad instance into the field \"URL of your API " +"endpoint\". Save to apply the settings" msgstr "" -#: ../system/objects.rst:24 -msgid "" -"Attributes you add to Zammad, no matter if they have default values or not, " -"will not update existing information. This means a new ticket field " -"technically will be empty unless you populate it." +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "Screencast showing how to activate the Zammad integration" msgstr "" -#: ../system/objects.rst:28 +#: ../system/integrations/cti/provider-configurations/placetel.rst:51 +msgid "Step 2: Generate API Token for Placetel" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:32 msgid "" -"Especially in ticket scope this also means that newly added attributes will " -"be indicated as \"changed\" to agents that view the ticket. This may " -"interfere with Zammad's tabs behavior." +"Go back to the integrations page and scroll down to \"Web API\". Generate a " +"new API token by using the \"Create a new API token\" button." msgstr "" -#: ../system/objects.rst:40 -#, fuzzy -msgid "Ordering Attributes" -msgstr "Attributs d'un billet" +#: ../system/integrations/cti/provider-configurations/placetel.rst:37 +msgid "" +"If you already generated a token either use your existing token or reset it " +"by using above mentioned button. Placetel will ask you to conform this reset." +msgstr "" -#: ../system/objects.rst:42 +#: ../system/integrations/cti/provider-configurations/placetel.rst:41 msgid "" -"Since Zammad introduced :doc:`/system/core-workflows` the need to have a " -"custom positioning for attributes has become more important than ever." +"Please keep in mind that existing API scripts may no longer work due to " +"token resets!" msgstr "" -#: ../system/objects.rst:45 +#: ../system/integrations/cti/provider-configurations/placetel.rst:44 msgid "" -"To adjust the position of such an attribute, simply click on the attribute " -"entry in question, scroll down and adjust the position number. Please note " -"that you cannot change the positioning of default attributes." +"Copy the provided API token and insert it into the \"API Token\" field " +"within Zammad's Placetel integration." msgstr "" -#: ../system/objects.rst:49 +#: ../system/integrations/cti/provider-configurations/placetel.rst:47 msgid "" -"In case two attributes have the same position value, Zammad will sort " -"alphabetically by name automatically." +"Apply your changes by using the \"Save\" button on the bottom of the " +"Placetel integration page and activate the Placetel integration." msgstr "" -#: ../system/objects.rst:None +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 msgid "" -"Screenshot showing custom attribute entries ordered in between default ones" +"Screencast showing how to retrieve an API token from Placetel for Zammad" msgstr "" -#: ../system/objects.rst:56 -msgid "Updating Database After Adding or Editing Attributes" +#: ../system/integrations/cti/provider-configurations/placetel.rst:73 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:77 +msgid "Step 3: Restrict the numbers to notify on" msgstr "" -#: ../system/objects.rst:58 +#: ../system/integrations/cti/provider-configurations/placetel.rst:54 msgid "" -"When adding or changing attributes, Zammad will not apply the changes " -"instantly, but instead shows you the changed attributes first. If you're " -"ready to go, just click on \"Update database\" to apply the changes to " -"Zammad. If you made a mistake or just want to discard your changes, click " -"\"Discard changes\"." +"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " +"the the Integrations page of the Placetel web interface, go to \"Notify " +"API\"." msgstr "" -#: ../system/objects.rst:64 +#: ../system/integrations/cti/provider-configurations/placetel.rst:58 msgid "" -"After applying the changes with \"Update Database\", a restart of Zammad is " -"**mandatory**. If you don't perform it, you may experience unexpected " -"behavior or even errors. You may want to do this kind of configuration " -"during maintenance windows." +"Lower on the page Placetel allows you to restrict the numbers to notify on. " +"You'll find this within the \"External routing API\" part." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "" +"Screenshot showing a sample selection of phone numbers to use for the " +"Placetels notify API" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:66 +msgid "" +"This menu point also provides a API request log from Placetel view. Just " +"open \"Recent responses of your API endpoint\" to learn more." msgstr "" -#: ../system/objects.rst:72 +#: ../system/integrations/cti/provider-configurations/placetel.rst:69 msgid "" -"Changes on objects require you to update the database to apply these changes." +"If you want to see Zammad's perspective, use the \"Recent Logs\" part from " +"within the Placetel integration page." msgstr "" -#: ../system/objects.rst:75 -msgid "**🤓 Service restarts can be automated**" +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "Screenshot showing sample log entries for Placetels API calls to Zammad" msgstr "" -#: ../system/objects.rst:0 -msgid "Hosted environments automatically restart for you." +#: ../system/integrations/cti/provider-configurations/placetel.rst:77 +msgid "Step 4 (optional): Further configurations for Placetel" msgstr "" -#: ../system/objects.rst:0 +#: ../system/integrations/cti/provider-configurations/placetel.rst:76 msgid "" -"If you're using a self-hosted installation you can use :docs:`environment " -"variables `" +"If needed, you can now configure Zammad's Placetel integration in more " +"detail. You can learn more about your options here: :ref:`Placetel " +"integration settings `." msgstr "" -#: ../system/objects.rst:82 -#, fuzzy -msgid "System Attributes" -msgstr "Attributs d'un billet" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:2 +msgid "Setup Sipgate connection for Zammad" +msgstr "" -#: ../system/objects.rst:84 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"Zammad comes with pre-configured attributes. Some of them can't be edited " -"via UI (or at all). This is required for proper operation of Zammad and not " -"a bug." +"Sipgate has no english web interface which is why this documentation page is " +"mixing up languages badly." msgstr "" -#: ../system/objects.rst:90 -#, fuzzy -msgid "Ticket State" -msgstr "Billet > État > Nom" - -#: ../system/objects.rst:92 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"If the pre-configured states aren't enough for you or you want to change " -"them, you can do so by clicking on the cogwheel icon in the state row in the " -"ticket tab. But you should be careful when changing pre-configured states. " -"This can lead to unwanted behavior in some cases." +"Please also note that the availability of API addons highly depends on your " +"package trier. Usage of sipgate.io packages *is not free*, please check " +"their `pricing page `_ before!" msgstr "" -#: ../system/objects.rst:None -msgid "Screenshot showing highlighted ticket state attribute" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:35 +msgid "Step 1: Book sipgate.io package" msgstr "" -#: ../system/objects.rst:122 -msgid "Handling of states" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:13 +msgid "Skip to step 2 if you already have the package booked!" msgstr "" -#: ../system/objects.rst:102 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:15 msgid "" -"In the state configuration screen, you can add new states, disable states or " -"change states." +"Login to an administrative Sipgate account and navigate to " +"``Accountverwaltung``. You'll see several different options depending on " +"your booked packages. Select ``Verträge & Produkte`` to continue." msgstr "" -#: ../system/objects.rst:0 -msgid "Screenshot showing table of default ticket states" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:19 +msgid "" +"Scroll down to the section ``Zusätzliche Produkte buchen`` and look for " +"``sipgate.io`` - select this product by using the ``Produkte anzeigen``-" +"Button." msgstr "" -#: ../system/objects.rst:110 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:23 msgid "" -"To add a new state, click on the \"New Ticket State\" button in the top " -"right corner. To change an existing state, simply click on the affected " -"state. This opens an edit dialog." +"On the next page select either one of the ``sipgate.io`` packages or ``Push-" +"API Package Free``. Follow the dialogue by booking the addon. You'll be " +"returned to your contract overview and now should see the selected addon in " +"your list." msgstr "" -#: ../system/objects.rst:114 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:30 msgid "" -"You can also clone a state or set them to \"Default for new tickets\" or " -"\"Default for follow-ups\" by clicking on the ⁝ action button and select the " -"desired function." +"The availability for ``sipgate.io`` packages and their levels highly depends " +"on the overall account type and product you've booked with Sipgate." msgstr "" -#: ../system/objects.rst:118 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"*Default for new tickets* means that this state is used for every newly " -"created ticket." +"Screencast showing the process on how to book the required sipgate.io addon" msgstr "" -#: ../system/objects.rst:121 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:52 +msgid "Step 2: Configure webhook for Zammad" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:38 msgid "" -"*Default for follow-ups* means that this state is used if the ticket is re-" -"opened after it was closed." +"Within your ``Accountverwaltung`` navicate to your product ``sipgate.io``. " +"In the newly opened tab, switch from \"Clients\" to \"Webhooks\" and paste " +"the endpoint URLs from your Zammad instance like so:" msgstr "" -#: ../system/objects.rst:171 -#, fuzzy -msgid "Ticket state in detail" -msgstr "Billet > État > Nom" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:42 +msgid "Inbound endpoint to \"Incoming\"" +msgstr "" -#: ../system/objects.rst:125 -msgid "" -"Below you can find a description for each field and option. Please head over " -"to the :ref:`example ` to see the edit dialog." +#: ../system/integrations/cti/provider-configurations/sipgate.rst:43 +msgid "Outbound endpoint to \"Outgoing\"" msgstr "" -#: ../system/objects.rst:129 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:47 msgid "" -"This is the name of the state and what you and your agents are seeing when " -"choosing a state somewhere (e.g. in tickets, trigger configuration)." +"Ensure to select at least one call group or phoneline within \"Sources\". " +"Other wise Sipgate will not indicate any incoming or outgoing calls to " +"Zammad." msgstr "" -#: ../system/objects.rst:137 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"There are different state types you can choose from. By default, Zammad " -"comes with one state per state type." +"Screencast showing how to add Zammad's endpoint URLs to sipgate.ios webhook " +"configuration" msgstr "" -#: ../system/objects.rst:140 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:55 msgid "" -"**new**: for states for tickets that are new and it hasn't been worked on " -"them" +"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " +"the Webhooks → URLs section of Sipgate you can select which *sources* " +"Sipgate should notify Zammad about in- and outgoing calls." msgstr "" -#: ../system/objects.rst:142 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:59 msgid "" -"**open**: for states for tickets that are in progress and agents are working " -"on them" +"Use either specific phone lines or use the option \"Use for all phonelines " +"and groups\" to notify Zammad about all existing lines of your Sipgate " +"account." msgstr "" -#: ../system/objects.rst:144 -msgid "**merged**: for states for tickets that are merged with other tickets" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "" +"Screenshot showing a sample selection of phone numbers to use for the " +"Sipgates webhooks API" msgstr "" -#: ../system/objects.rst:145 -msgid "" -"**pending reminder**: for states for tickets that are in progress and you " -"want to set a reminder. (default example: *pending reminder*)" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:68 +msgid "This section also allows you to enable a Debug log." msgstr "" -#: ../system/objects.rst:147 -msgid "" -"**pending action**: for states for tickets that are waiting for a specified " -"time and then change their state (default example: *pending close*)" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "Screenshot showing an enabled Debug log option" msgstr "" -#: ../system/objects.rst:150 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:73 msgid "" -"**closed**: for states for tickets that are finished and do not need to be " -"processed further" +"After enabling you can use the Debug log section to see all sent webhook " +"calls to Zammad. You'll also can see the response." msgstr "" -#: ../system/objects.rst:153 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"⚠️ Choosing the correct state type is important! If you are in doubt, have a " -"look on the default states and their types!" +"Screenshot showing sample log entries for Sipgates webhook calls to Zammad" msgstr "" -#: ../system/objects.rst:158 -msgid "Ignore escalation" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:81 +msgid "Step 4 (optional): Further configurations for Sipgate" msgstr "" -#: ../system/objects.rst:157 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:80 msgid "" -"Here you can define whether tickets of this state will count to escalation " -"time or not." +"If needed, you can now configure Zammad's Sipgate integration in more " +"detail. You can learn more about your options here: :ref:`Sipgate " +"integration settings `." msgstr "" -#: ../system/objects.rst:161 -msgid "" -"You can create a note for the state to inform other admins about the state. " -"This has no effect on tickets." +#: ../system/integrations/cti/sipgate.rst:2 +msgid "Sipgate (sipgate.io)" msgstr "" -#: ../system/objects.rst:165 -msgid "Set the state to *active* or *inactive*." +#: ../system/integrations/cti/sipgate.rst:16 +msgid "You need an administrative Sipgate account for your organization." msgstr "" -#: ../system/objects.rst:167 +#: ../system/integrations/cti/sipgate.rst:17 msgid "" -"it is technically possible to set all states to inactive. To keep Zammad " -"working in such a case, the inactive flag of one of the states is ignored." +"Zammad requires a ``sipgate.io`` addon from the feature store (please note " +"that API calls are not free with Sipgate. Rates may apply and differ from " +"account to account)." msgstr "" -#: ../system/objects.rst:194 -#, fuzzy -msgid "Ticket state example" -msgstr "Billet > État > Nom" - -#: ../system/objects.rst:174 -msgid "" -"Let's assume we want to create a new state which indicates that the ticket " -"has to wait for a response of a third party (e.g. service contractor or " -"manufacturer) and we want to to be able to set a reminder." +#: ../system/integrations/cti/sipgate.rst:21 +msgid "Sipgate must be able to reach your Zammad instance." msgstr "" -#: ../system/objects.rst:178 -msgid "" -"First we give the new state a proper name. In this example we call it " -"\"waiting for manufacturer\"." +#: ../system/integrations/cti/sipgate.rst:25 +msgid ":doc:`provider-configurations/sipgate`" msgstr "" -#: ../system/objects.rst:181 +#: ../system/integrations/cti/sipgate.rst:24 msgid "" -"As state type we choose \"pending reminder\". This indicates that the ticket " -"is still open and we can set a reminder. This reminder can be useful if our " -"manufacturer sometimes isn't responding or we want to remind him to give us " -"an answer." +"Learn how to configure Sipgate to enable Zammad and Sipgate to communicate " +"with each other." msgstr "" -#: ../system/objects.rst:186 +#: ../system/integrations/cti/sipgate.rst:33 msgid "" -"We choose \"no\" for \"ignore escalation\" because we want to escalate the " -"tickets even if we are waiting on the manufacturer's feedback." +"Below endpoint settings affect the :doc:`sipgate.io configuration `." msgstr "" -#: ../system/objects.rst:189 -#, fuzzy -msgid "The **result** in the creation dialog will look like this:" -msgstr "Le résultat final ressemblera à ceci:" - -#: ../system/objects.rst:0 -msgid "Screenshot showing ticket state creation dialog with example" +#: ../system/integrations/cti/sipgate.rst:37 +msgid "This endpoint is required for incoming call hooks." msgstr "" -#: ../system/objects.rst:197 ../system/objects.rst:199 -#, fuzzy -msgid "Ticket Priority" -msgstr "Billet > Priorité > Nom" - -#: ../system/objects.rst:199 ../system/objects.rst:201 -msgid "" -"If the pre-configured priorities aren't enough for you or you want to change " -"them, you can do so by clicking on the cogwheel icon in the priority row in " -"the ticket tab:" +#: ../system/integrations/cti/sipgate.rst:40 +msgid "This endpoint is required for outgoing call hooks." msgstr "" -#: ../system/objects.rst:None -msgid "Screenshot showing highlighted ticket priority attribute" +#: ../system/integrations/cti/sipgate.rst:0 +msgid "Screenshot showing sample user mappings in between Sipgate and Zammad" msgstr "" -#: ../system/objects.rst:224 ../system/objects.rst:226 -msgid "Handling of priorities" +#: ../system/integrations/cti/sipgate.rst:69 +msgid "" +"You can find your agent's Sipgate username within ``Accountverwaltung → " +"Benutzer``. You're looking for the SIP-ID." msgstr "" -#: ../system/objects.rst:208 ../system/objects.rst:210 -msgid "" -"In the priority configuration screen, you can add new priorities, disable " -"priorities or change priorities." +#: ../system/integrations/cti/sipgate.rst:0 +msgid "Sample VoIP credentials for a Sipgate user" msgstr "" -#: ../system/objects.rst:0 -msgid "Screenshot showing table of default ticket priorities" +#: ../system/integrations/cti/sipgate.rst:77 +msgid "Users with several devices also have several SIP-IDs." msgstr "" -#: ../system/objects.rst:216 ../system/objects.rst:218 -msgid "" -"To add a new priority, click on the \"New Priority\" button in the top right " -"corner. To change an existing priority, simply click on the affected " -"priority. This opens an edit dialog." +#: ../system/integrations/elasticsearch.rst:2 +msgid "Elasticsearch (SaaS)" msgstr "" -#: ../system/objects.rst:220 ../system/objects.rst:222 +#: ../system/integrations/elasticsearch.rst:4 msgid "" -"You can also clone a priority or set them to \"Default for new tickets\" by " -"clicking on the ⁝ action button and select the desired function." +"The Elasticsearch integration allows you to create a read-only user to use " +"with your favorite reporting tool (e.g. like Grafana)." msgstr "" -#: ../system/objects.rst:223 ../system/objects.rst:225 +#: ../system/integrations/elasticsearch.rst:7 msgid "" -"*Default for new tickets* means that this priority is used for every newly " -"created ticket." +"If you want to take full advantage of the Zammad reporting, have a look at " +"our :docs:`Grafana ` " +"setup page as well." msgstr "" -#: ../system/objects.rst:246 ../system/objects.rst:248 -msgid "Priorities in detail" +#: ../system/integrations/elasticsearch.rst:11 ../system/subscription.rst:7 +msgid "**🚧 Hosted environment specific 🚧**" msgstr "" -#: ../system/objects.rst:227 ../system/objects.rst:229 -msgid "Below you can find a description for each field and option." +#: ../system/integrations/elasticsearch.rst:13 +msgid "" +"This integration is only available for Hosted setups. In order to use " +"Elasticsearch you'll need the **Plus** subscription." msgstr "" -#: ../system/objects.rst:230 ../system/objects.rst:232 +#: ../system/integrations/elasticsearch.rst:16 msgid "" -"This is the name of the priority and what you and your agents are seeing " -"when choosing a priority somewhere (e.g. in tickets, trigger configuration)." +"Self hosted users have all the control over their self hosted Elasticsearch " +"instances." msgstr "" -#: ../system/objects.rst:240 ../system/objects.rst:242 -msgid "Highlight color" +#: ../system/integrations/elasticsearch.rst:None +msgid "Elasticsearch integration page on SaaS environments" msgstr "" -#: ../system/objects.rst:235 ../system/objects.rst:237 +#: ../system/integrations/elasticsearch.rst:27 msgid "" -"Switch between *Low priority* (light blue), *High priority* (red) and - " -"(default). This affects the displayed color for ticket titles in overviews." +"Please note the following limitations of Elasticsearch access on hosted " +"environments:" msgstr "" -#: ../system/objects.rst:239 ../system/objects.rst:241 -msgid "The color options are currently limited to the mentioned options." +#: ../system/integrations/elasticsearch.rst:30 +msgid "access to the Elasticsearch index is read-only access" msgstr "" -#: ../system/objects.rst:243 ../system/objects.rst:245 -msgid "" -"You can create a note for the priority to inform other admins about the " -"priority. This has no effect on tickets." +#: ../system/integrations/elasticsearch.rst:31 +msgid "currently you're limited to user only" msgstr "" -#: ../system/objects.rst:247 ../system/objects.rst:249 -msgid "Set the priority to *active* or *inactive*." +#: ../system/integrations/elasticsearch.rst:32 +msgid "" +"Reporting tools that require to write into the indexes (like Kibana) are not " +"supported" msgstr "" -#: ../system/objects/external-data-source-example.rst:2 -msgid "External Data Source" +#: ../system/integrations/elasticsearch.rst:34 +msgid "IP access restriction is currently not yet supported" msgstr "" -#: ../system/objects/external-data-source-example.rst:4 -msgid "" -"We assume you already had a look on :doc:`types` where you can find a " -"description of the individual fields." +#: ../system/integrations/elasticsearch.rst:37 +msgid "Activating Elasticsearch Access" msgstr "" -#: ../system/objects/external-data-source-example.rst:7 +#: ../system/integrations/elasticsearch.rst:39 msgid "" -"To reproduce this example, choose a category you want to add a custom field, " -"click on *New Attribute* and select *External data source field* under " -"*Format*." +"By default external access to your Elasticsearch index is not active. You " +"can enable the integration at any time if needed." msgstr "" -#: ../system/objects/external-data-source-example.rst:11 +#: ../system/integrations/elasticsearch.rst:42 msgid "" -"Our example story is to fetch data from an external product database. We " -"want to add our products to the tickets so that the products can be searched " -"and chosen from a list and also create a link to the product website." +"Please ensure to note down the password provided - you won't have access to " +"it afterwards." msgstr "" -#: ../system/objects/external-data-source-example.rst:16 -msgid "Base configuration" +#: ../system/integrations/elasticsearch.rst:None +msgid "Screencast showing activation of Elasticsearch integration" msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Initial steps to configure external data source object type" +#: ../system/integrations/elasticsearch.rst:51 +msgid "Connection Settings" msgstr "" -#: ../system/objects/external-data-source-example.rst:23 -#: ../system/variables.rst:85 -#, fuzzy -msgid "**Example:**" -msgstr "Exemple" - -#: ../system/objects/external-data-source-example.rst:25 -msgid "Name: *product*" +#: ../system/integrations/elasticsearch.rst:53 +msgid "" +"This section holds the most important general information for accessing your " +"Elasticsearch indexes - such as:" msgstr "" -#: ../system/objects/external-data-source-example.rst:26 -msgid "Display: *Product*" +#: ../system/integrations/elasticsearch.rst:57 +msgid "A unique subdomain that does not tell your real instance URL." msgstr "" -#: ../system/objects/external-data-source-example.rst:29 -msgid "External data source configuration" +#: ../system/integrations/elasticsearch.rst:61 +msgid "Software" msgstr "" -#: ../system/objects/external-data-source-example.rst:31 +#: ../system/integrations/elasticsearch.rst:60 msgid "" -"First, enter the search URL making sure it contains ``#{search.term}`` as a " -"parameter:" -msgstr "" - -#: ../system/objects/external-data-source-example.rst:34 -msgid "**Example:** ``https://dummyjson.com/products/search?q=#{search.term}``" +"The major version of the search index being used. This is required by some " +"Reporting tools like Grafana." msgstr "" -#: ../system/objects/external-data-source-example.rst:36 -msgid "" -"After that, head down to the preview section and enter a search input for " -"the external data source." +#: ../system/integrations/elasticsearch.rst:64 +msgid "Authentication" msgstr "" -#: ../system/objects/external-data-source-example.rst:39 -#, fuzzy -msgid "**Example:** ``mac``" -msgstr "Exemple" - -#: ../system/objects/external-data-source-example.rst:41 -msgid "Then you can find a preview of the response data below:" +#: ../system/integrations/elasticsearch.rst:64 +msgid "The authentication type being supported. ``Basic Authentication``" msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of JSON response based on search term" +#: ../system/integrations/elasticsearch.rst:67 +msgid "Available Indexes" msgstr "" -#: ../system/objects/external-data-source-example.rst:48 +#: ../system/integrations/elasticsearch.rst:69 msgid "" -"We recommend using the preview to have a look on the structure. There is a " -"top-level element called ``products``. One level below, you can find the " -"attributes ``id`` and ``title``." -msgstr "" - -#: ../system/objects/external-data-source-example.rst:52 -msgid "**Search result response based on search from example:**" +"Within this section we're displaying the -in our opinion- most important " +"indexes for a Zammad instance." msgstr "" -#: ../system/objects/external-data-source-example.rst:119 +#: ../system/integrations/elasticsearch.rst:72 msgid "" -"To tell the remote system that the desired data is located below the " -"``products`` level, you have to put it in the field *Search result list key*." +"If you require all indexes or our listing is not good enough for you, point " +"your browser to the URL we're providing and append ``/_aliases?" +"pretty=true``. The result should look like this: ``https://.zammad.com/" +"_aliases?pretty=true``." msgstr "" -#: ../system/objects/external-data-source-example.rst:122 +#: ../system/integrations/elasticsearch.rst:77 msgid "" -"After inserting ``products`` in the mentioned field, you get an extended " -"preview. You can find an additional box *Search result list* with a JSON " -"structure. This is the same response as before but stripped from the upper " -"``products`` element by the external data source." +"Your browser will automatically ask for your credentials - you'll then see " +"something like this:" msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of JSON response search result list" +#: ../system/integrations/elasticsearch.rst:125 +msgid "Credentials" msgstr "" -#: ../system/objects/external-data-source-example.rst:132 +#: ../system/integrations/elasticsearch.rst:127 msgid "" -"Now you need to provide the keys for the search result values and labels. As " -"already mentioned, we are looking for the ``id`` and the ``title`` of our " -"products. If you haven't already, it is now a good time to look at the " -"preview of the *Search result list*." +"Within this section Zammad displays your available users. The password is " +"provided once (upon activation) and cannot be retrieved after that." msgstr "" -#: ../system/objects/external-data-source-example.rst:197 +#: ../system/integrations/elasticsearch.rst:131 msgid "" -"After locating our two keys, we insert them in *search result value key* " -"(``id``) and in *Search result label key* (``title``)." +"If you need to change or reset your Elasticsearch user password, use the " +"\"Reset password\" button in the credentials table. Doing so creates a brand " +"new password for the account in question. This change is immediate, keep in " +"mind that this may affect third party tools connected to your instance." msgstr "" -#: ../system/objects/external-data-source-example.rst:200 -msgid "" -"Basically, we configured the external data source already and we can see a " -"table in the preview section:" +#: ../system/integrations/exchange.rst:2 +msgid "Exchange" msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of product table based on search term" +#: ../system/integrations/exchange.rst:4 +msgid "" +"With Zammad's Exchange integration, you can easily use existing address " +"books without having to update more than one source." msgstr "" -#: ../system/objects/external-data-source-example.rst:208 +#: ../system/integrations/exchange.rst:7 msgid "" -"According to our example story, now just the *Link template* is missing." +"However, you should refrain from syncing all addresses, as the results may " +"not be what you expect (Exchange collects huge amounts of addresses). A " +"central address book of your company to sync makes more sense, as you can " +"ensure that Zammad gets only the data you need and want. Apart from this, it " +"is even not possible to sync the Global Address List (GAL) of your Exchange " +"system with Zammad." msgstr "" -#: ../system/objects/external-data-source-example.rst:210 +#: ../system/integrations/exchange.rst:16 msgid "" -"Please note that this is an optional feature. If you don't want to use such " -"links, of course you don't have to configure it." +"**Exchange and LDAP:** The exchange sync can be overruled by Zammad's LDAP " +"integration. If you have the same users in both sources, the LDAP version " +"will always be Zammad's pick." msgstr "" -#: ../system/objects/external-data-source-example.rst:213 +#: ../system/integrations/exchange.rst:19 msgid "" -"We can add now an address where additional product information can be found." +"**One way sync:** the Exchange sync is one way. Exchange => Zammad. Changes " +"to your users inside of Zammad might be overwritten by the Exchange sync." msgstr "" -#: ../system/objects/external-data-source-example.rst:215 -msgid "Example: ``https://your_domain.com/q=#{ticket.product}``" +#: ../system/integrations/exchange.rst:24 +msgid "" +"To configure Exchange integration, simply go to the System > Integrations > " +"Exchange in the admin panel. Press \"change\" and follow the wizard for " +"adding the needed Exchange information to Zammad. On the last two steps " +"Zammad will ask you for the address book(s) and your desired attribute " +"mapping. By default, Zammad only maps email address, first- and lastname. " +"Technically, you can map any Exchange object to a Zammad user object (this " +"also works for custom objects!)." msgstr "" -#: ../system/objects/external-data-source-example.rst:217 -msgid "In the example, the parameter means:" +#: ../system/integrations/exchange.rst:35 +msgid "" +"If the SSL verification fails while connecting to Exchange, Zammad will ask " +"you to turn it off temporarily." msgstr "" -#: ../system/objects/external-data-source-example.rst:219 -msgid "``#{}``: \"Frame\" for the insertion of information" +#: ../system/integrations/exchange.rst:38 +msgid "" +"Please be aware that **turning off SSL verification is a security risk**. It " +"should only be used temporarily or for testing purposes. If turned off, " +"there is no verification of the certificate, which means that every " +"presented certificate will be accepted." msgstr "" -#: ../system/objects/external-data-source-example.rst:220 -msgid "``ticket``: object level, where you create your custom object" +#: ../system/integrations/exchange.rst:43 +msgid "" +"After pressing Continue, Zammad will check if the configuration is okay. You " +"can then enable Exchange and start your first sync. The sync will then run " +"hourly - if you need to change mappings or the address book(s), you can " +"change the configuration at any time." msgstr "" -#: ../system/objects/external-data-source-example.rst:221 -msgid "``product``: name of the (custom) object" +#: ../system/integrations/exchange.rst:50 +msgid "" +"After the sync has finished, you can find the new Exchange contacts under " +"\"Users\". Zammad integrates them just as normal users." msgstr "" -#: ../system/objects/external-data-source-example.rst:223 +#: ../system/integrations/exchange.rst:55 msgid "" -"After configuring your *Link template*, there will be another column in the " -"preview. Hovering on the icons in the *Link* column will show you where it " -"forwards you." +"In some cases you might see unique IDs as \"Login\" instead of the email " +"address. This is normal and doesn't affect the login or email mapping for " +"that entry." msgstr "" -#: ../system/objects/external-data-source-example.rst:232 +#: ../system/integrations/github.rst:4 msgid "" -"In our example, one of the links looks like: https://your_domain.com/q=6, " -"where the 6 is the product id." +"Use GitHub integration to track GitHub issues directly within Zammad " +"tickets. Add issue hyperlinks and get a live summary of metadata like status " +"(open/closed), assignee, labels, and more." msgstr "" -#: ../system/objects/external-data-source-example.rst:235 -msgid "You can find more information regarding the URL in :doc:`types`." +#: ../system/integrations/github.rst:8 +msgid "Please note that our GitHub integration does not support pull requests." msgstr "" -#: ../system/objects/includes/adding-values-hint.include.rst:3 -msgid "" -"Adding values can be tricky for first timers, don't forget to press \"➕ " -"Add\" after typing your values. Otherwise you may loose a value." +#: ../system/integrations/github.rst:None +msgid "Integration page for GitHub" msgstr "" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:1 -#: ../system/objects/includes/reposition-values.include.rst:1 -msgid "**↕️ This field type allows the positioning of its values ↔️**" +#: ../system/integrations/github.rst:18 +msgid "" +"In your GitHub settings, create a new API token under **Developer settings > " +"Personal access tokens > Generate new token**. Leave the **Scopes** section " +"empty." msgstr "" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:3 -msgid "" -"In order to re-arrange the field values, first edit the field. Then you can " -"use ☰ to drag the values in question to the correct position. If you want to " -"change the layer depth, double click on ☰. With it you can cycle through the " -"available layers." +#: ../system/integrations/github.rst:0 ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to create a new API token" msgstr "" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:8 -msgid "When you're ready, submit your changes to save the object attribute." +#: ../system/integrations/github.rst:27 +msgid "Create a new API key with no scopes/privileges." msgstr "" -#: :0 ../system/objects/types.rst:0 -msgid "" -"Screencast showing how to re-position values on tree select like\n" -"fields" +#: ../system/integrations/github.rst:29 +msgid "🔒 **Will this work for private repos?**" msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:3 +#: ../system/integrations/github.rst:31 msgid "" -"In order to re-arrange the field values, edit the field and scroll below the " -"values. Make sure to tick the option \"Use custom option sort\"." +"No. To link private repo issues, **use the** ``repo`` **scope instead**. " +"Bear in mind that the resulting token will have `lots of permissions that it " +"doesn't actually need `_, which presents a security risk if your token ever falls into " +"the wrong hands." msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:8 +#: ../system/integrations/github.rst:37 msgid "" -"If you do not tick this field, all manual positioning you did above will be " -"lost upon saving! ☠️" +"Unfortunately, because of how GitHub's OAuth token scopes are set up, this " +"is the only way to link issues on private repos." msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:11 -msgid "" -"Now use ☰ to drag the values in question to the correct position. When " -"you're ready, submit your changes to save the object attribute." +#: ../system/integrations/github.rst:40 +msgid "Enter your new API token in Zammad and enable GitHub integration." msgstr "" -#: :0 ../system/objects/types.rst:0 -msgid "Screencast showing how to re-position values" +#: ../system/integrations/github.rst:0 +msgid "Screencast showing how to configure Zammad's GitHub integration" msgstr "" -#: ../system/objects/includes/url-template-hint.include.rst:3 +#: ../system/integrations/github.rst:47 msgid "" -"This field allows using :ref:`URL fields (Link Templates) `." +"Use the default API endpoint (``https://api.github.com/graphql``) unless " +"you're using GitHub Enterprise Server." msgstr "" -#: ../system/objects/permissions.rst:2 -#, fuzzy -msgid "Attribute Permissions" -msgstr "Attributs d'article" - -#: ../system/objects/permissions.rst:7 +#: ../system/integrations/github.rst:50 msgid "" -"In the object attributes configuration you can define if a field is shown " -"and if the input in the field is mandatory, separated by different screens " -"and for different :doc:`roles/permissions `." +"Once completed, a new GitHub issues tab will appear in the ticket pane. 🎉" msgstr "" -#: ../system/objects/permissions.rst:17 -msgid "Screenshot shows object attribute permission table" +#: ../system/integrations/github.rst:59 ../system/integrations/gitlab.rst:52 +msgid "Token verification is taking a long time" msgstr "" -#: ../system/objects/permissions.rst:17 +#: ../system/integrations/github.rst:56 ../system/integrations/gitlab.rst:49 msgid "" -"Some of the possible permissions and screen options for a user object " -"attribute." +"Slight delays are normal (<2 min.), especially for systems under heavy load." msgstr "" -#: ../system/objects/permissions.rst:19 +#: ../system/integrations/github.rst:58 msgid "" -"Based on the object context (ticket, agent, organization, user), the " -"selectable roles (to be precise: the required permissions) and screens " -"differ. Be aware that these settings aren't affecting data creation via " -"other channels than the UI." +"Self-hosted administrators, please check your network settings to ensure " +"that your Zammad server can reach ``api.github.com``." msgstr "" -#: ../system/objects/permissions.rst:24 +#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 +msgid "I reloaded the page and now the API token is gone" +msgstr "" + +#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 msgid "" -"If you want to have further customization possibilities, you should have a " -"look at the :doc:`core workflows `." +"This may indicate that Zammad is still verifying your API token. Try " +"reloading the page again in a couple minutes." msgstr "" -#: ../system/objects/permissions.rst:28 -msgid "Screens" +#: ../system/integrations/gitlab.rst:2 +msgid "GitLab" msgstr "" -#: ../system/objects/permissions.rst:30 +#: ../system/integrations/gitlab.rst:4 msgid "" -"In the table below you can find an overview about the different permissions " -"and the available screens Zammad distinguishes between." +"Use GitLab integration to track GitLab issues directly within Zammad " +"tickets. Add issue hyperlinks and get a live summary of metadata like status " +"(open/closed), assignee, labels, and more." msgstr "" -#: ../system/objects/permissions.rst:37 -msgid "Screen" +#: ../system/integrations/gitlab.rst:8 +msgid "" +"Please note that our GitLab integration does not support merge requests." msgstr "" -#: ../system/objects/permissions.rst:38 -#, fuzzy -msgid "Available for" -msgstr "Variable" - -#: ../system/objects/permissions.rst:40 -msgid "create" +#: ../system/integrations/gitlab.rst:None +msgid "Integration page for GitLab" msgstr "" -#: ../system/objects/permissions.rst:41 ../system/objects/permissions.rst:52 -#: ../system/objects/permissions.rst:59 ../system/objects/permissions.rst:73 -msgid "admin.user" +#: ../system/integrations/gitlab.rst:18 +msgid "" +"In your GitLab preferences, create a new API token under **Access Tokens**." msgstr "" -#: ../system/objects/permissions.rst:42 ../system/objects/permissions.rst:53 -#: ../system/objects/permissions.rst:60 -#, fuzzy -msgid "admin.organization" -msgstr "Billet > Organisation > Note" - -#: ../system/objects/permissions.rst:43 ../system/objects/permissions.rst:54 -#: ../system/objects/permissions.rst:61 -msgid "admin.group" +#: ../system/integrations/gitlab.rst:20 +msgid "Under **Select scopes**, choose ``read_api`` only." msgstr "" -#: ../system/objects/permissions.rst:44 -msgid "Creation dialog for not yet existing data" +#: ../system/integrations/gitlab.rst:27 +msgid "🔒 **If you wish to link issues on any private repos...**" msgstr "" -#: ../system/objects/permissions.rst:45 -msgid "create_middle" +#: ../system/integrations/gitlab.rst:29 +msgid "Your API token must belong to an account with access to those repos." msgstr "" -#: ../system/objects/permissions.rst:46 ../system/objects/permissions.rst:50 -#: ../system/objects/permissions.rst:57 ../system/objects/permissions.rst:66 -#: ../system/objects/permissions.rst:70 -#, fuzzy -msgid "ticket.customer" -msgstr "L'agent sera défini comme client du billet." - -#: ../system/objects/permissions.rst:47 ../system/objects/permissions.rst:51 -#: ../system/objects/permissions.rst:58 ../system/objects/permissions.rst:69 -#, fuzzy -msgid "ticket.agent" -msgstr "Billet" - -#: ../system/objects/permissions.rst:48 -msgid "Ticket create dialog (middle section)" +#: ../system/integrations/gitlab.rst:31 +msgid "Enter your new API token in Zammad and enable GitLab integration." msgstr "" -#: ../system/objects/permissions.rst:49 -msgid "edit" +#: ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to configure Zammad's GitLab integration" msgstr "" -#: ../system/objects/permissions.rst:55 -msgid "Editing dialog for already existing data" +#: ../system/integrations/gitlab.rst:40 +msgid "" +"Use the default API endpoint (``https://gitlab.com/api/graphql``) unless " +"you're a self-hosted GitLab user." msgstr "" -#: ../system/objects/permissions.rst:56 -msgid "view" +#: ../system/integrations/gitlab.rst:43 +msgid "" +"Once completed, a new GitLab issues tab will appear in the ticket pane. 🎉" msgstr "" -#: ../system/objects/permissions.rst:62 -msgid "View-only dialog for already existing data" +#: ../system/integrations/gitlab.rst:51 +msgid "" +"Self-hosted administrators, please check your network settings to ensure " +"that your Zammad server can reach ``gitlab.com``." msgstr "" -#: ../system/objects/permissions.rst:64 -msgid "(e.g. user or organization from search)" +#: ../system/integrations/i-doit.rst:2 +msgid "i-doit" msgstr "" -#: ../system/objects/permissions.rst:65 -msgid "signup" +#: ../system/integrations/i-doit.rst:4 +msgid "" +"`i-doit `_ is an open-source **configuration " +"management database** - in other words, a tool for keeping tabs on every " +"single piece of your physical and digital infrastructure, from network " +"equipment to virtual machines on down to the faceplates on your rack shelves " +"and more." msgstr "" -#: ../system/objects/permissions.rst:67 -msgid "Sign-up screen for new customers" +#: ../system/integrations/i-doit.rst:10 +msgid "" +"What's that got to do with Zammad? Well, if you used tickets to track issues " +"with all that hardware, you might start wishing there was a way they could " +"talk to each other." msgstr "" -#: ../system/objects/permissions.rst:68 -msgid "invite_customer" +#: ../system/integrations/i-doit.rst:14 +msgid "Zammad gives you two:" msgstr "" -#: ../system/objects/permissions.rst:71 -msgid "" -"Customer invitation screen (from :doc:`First Steps ` area)" +#: ../system/integrations/i-doit.rst:17 +msgid "1. Add i-doit Links to Zammad Tickets" msgstr "" -#: ../system/objects/permissions.rst:72 -msgid "invite_agent" +#: ../system/integrations/i-doit.rst:20 ../system/integrations/i-doit.rst:80 +msgid "What Users See" msgstr "" -#: ../system/objects/permissions.rst:74 -msgid "" -"Agent invitation screen (from :doc:`First Steps ` area)" +#: ../system/integrations/i-doit.rst:26 +msgid "i-doit integration in Zammad's ticket pane" msgstr "" -#: ../system/objects/permissions.rst:78 -msgid "Screen Options" +#: ../system/integrations/i-doit.rst:26 +msgid "" +"The i-doit integration will appear under a new 🖨 tab in the ticket pane." msgstr "" -#: ../system/objects/permissions.rst:80 +#: ../system/integrations/i-doit.rst:28 msgid "" -"For the different screens you can select \"show\" and \"required\" options." +"i-doit integration puts a new tab in Zammad's ticket pane where you can add " +"links to existing i-doit devices for easy reference. (See our :user-docs:" +"`user documentation ` to learn " +"how it works in practice)." msgstr "" -#: ../system/objects/permissions.rst:82 -msgid "**shown:** Show (check) or hide (uncheck) a field." +#: ../system/integrations/i-doit.rst:36 ../system/integrations/i-doit.rst:93 +msgid "How to Set it Up" msgstr "" -#: ../system/objects/permissions.rst:83 +#: ../system/integrations/i-doit.rst:38 msgid "" -"**required:** Set a field to mandatory (check). Forces users (via UI and " -"API) to populate the field." +"It requires i-doit's `API Add-on `_. Make sure to have it properly set up. Use the following setting:" msgstr "" -#: ../system/objects/types.rst:7 -#, fuzzy -msgid "Example external data source" -msgstr "Réglages avancés" +#: ../system/integrations/i-doit.rst:42 +msgid "Active: ``Yes``" +msgstr "" -#: ../system/objects/types.rst:2 -#, fuzzy -msgid "Attribute types" -msgstr "Attributs d'article" +#: ../system/integrations/i-doit.rst:43 +msgid "Enforce authentication by username and password: ``No``" +msgstr "" -#: ../system/objects/types.rst:4 +#: ../system/integrations/i-doit.rst:45 msgid "" -"When adding a new object attribute, you can choose between the following " -"attribute types." +"To set it up, enable the integration in the Zammad admin panel under " +"**System > Integrations > i-doit**:" msgstr "" -#: ../system/objects/types.rst:14 -msgid "" -"You cannot change the attribute format / type as soon as it is applied. If " -"you no longer need an object attribute, consider disabling it instead of " -"removing." +#: ../system/integrations/i-doit.rst:None +msgid "i-doit settings within the integration pages" msgstr "" -#: ../system/objects/types.rst:18 -msgid "**What about the translation of my attributes?**" +#: ../system/integrations/i-doit.rst:53 +msgid "The root URL of your i-doit installation." msgstr "" -#: ../system/objects/types.rst:20 -msgid "" -"For some attribute types you can decide if they should be translatable or " -"not. To be precise, it works only for the selectable fields because the " -"possible choices are known and limited. For the following attribute types, " -"you can set the translatable flag:" +#: ../system/integrations/i-doit.rst:62 +msgid "API token" msgstr "" -#: ../system/objects/types.rst:25 -msgid "*Boolean field*" +#: ../system/integrations/i-doit.rst:56 +msgid "" +"Found in the i-doit admin panel under **Interfaces / external data > JSON-" +"RPC API > Common Settings**." msgstr "" -#: ../system/objects/types.rst:26 -#, fuzzy -msgid "*Single selection field*" -msgstr "Réglages avancés" +#: ../system/integrations/i-doit.rst:0 +msgid "i-doit administration interface with API configuration" +msgstr "" -#: ../system/objects/types.rst:27 -#, fuzzy -msgid "*Multiple selection field*" -msgstr "Réglages avancés" +#: ../system/integrations/i-doit.rst:67 +msgid "Client ID" +msgstr "" -#: ../system/objects/types.rst:28 -#, fuzzy -msgid "*Single tree selection field*" -msgstr "Réglages avancés" +#: ../system/integrations/i-doit.rst:65 +msgid "A unique name to identify Zammad within i-doit." +msgstr "" -#: ../system/objects/types.rst:29 -#, fuzzy -msgid "*Multiple tree selection field*" -msgstr "Réglages avancés" +#: ../system/integrations/i-doit.rst:67 +msgid "(Zammad does not require you to enter a value here, but i-doit might!)" +msgstr "" -#: ../system/objects/types.rst:31 +#: ../system/integrations/i-doit.rst:70 msgid "" -"For these types, you can find an additional field *Translate field contents*:" +"Here you can decide if the certificate of your i-doit system has to be " +"verified or not. In case you are using custom certificates, please have a " +"look at :doc:`how to add them to Zammad `." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Screenshot showing translatable attribute types" +#: ../system/integrations/i-doit.rst:77 +msgid "2. List / Create Zammad Tickets in i-doit" msgstr "" -#: ../system/objects/types.rst:38 -msgid "Screenshot with example of translatable attribute type" +#: ../system/integrations/i-doit.rst:None +msgid "Zammad integration in i-doit's device view" msgstr "" -#: ../system/objects/types.rst:45 -msgid "Boolean field" +#: ../system/integrations/i-doit.rst:86 +msgid "" +"i-doit's ticket system integration gives you a way to see all the tickets " +"for a given device without ever leaving i-doit. (See our :user-docs:`user " +"documentation ` to learn how it " +"works in practice)." msgstr "" -#: ../system/objects/types.rst:41 +#: ../system/integrations/i-doit.rst:95 msgid "" -"Provides a drop-down field with display values for ``true`` and ``false``. " -"Setting a default is mandatory." +"Enable this integration in the i-doit admin panel under **Interfaces / " +"external data > Trouble Ticket System (TTS) > Configuration**:" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Boolean fields" +#: ../system/integrations/i-doit.rst:None +msgid "i-doit administration interface with TTS configuration" msgstr "" -#: ../system/objects/types.rst:55 -msgid "Date field" +#: ../system/integrations/i-doit.rst:104 +msgid "TTS-Type" msgstr "" -#: ../system/objects/types.rst:48 -msgid "Provides a date picker field and does not allow default values." +#: ../system/integrations/i-doit.rst:104 +msgid "``Zammad``" msgstr "" -#: ../system/objects/types.rst:52 -msgid "Default time diff (hours)" +#: ../system/integrations/i-doit.rst:115 +msgid "Username / Password" msgstr "" -#: ../system/objects/types.rst:51 -msgid "" -"This setting helps the user by highlighting the day from now plus the " -"provided value. It *does not* pre-fill the field." +#: ../system/integrations/i-doit.rst:107 +msgid "Login credentials for a Zammad agent." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Date fields" +#: ../system/integrations/i-doit.rst:109 +msgid "" +"This agent must have **read permission** for all :doc:`groups ` that plan on using the i-doit integration." msgstr "" -#: ../system/objects/types.rst:73 -msgid "Date & time field" +#: ../system/integrations/i-doit.rst:113 +msgid "" +"You may even wish to create a dedicated agent account just for this " +"integration (otherwise, if the agent ever changes her password, you will " +"have to remember to update it here)." msgstr "" -#: ../system/objects/types.rst:58 -msgid "Provides a date and time picker – does not allow default values" +#: ../system/integrations/i-doit.rst:117 +msgid "URL incl. protocol" msgstr "" -#: ../system/objects/types.rst:62 -msgid "Allow future" +#: ../system/integrations/i-doit.rst:118 +msgid "``https://your.zammad.domain``" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Forbid dates and times in the future." +#: ../system/integrations/index.rst:2 +msgid "Integrations" msgstr "" -#: ../system/objects/types.rst:66 -msgid "Allow past" +#: ../system/integrations/index.rst:4 +msgid "" +"Zammad offers numerous integrations that add rich features to your instance." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Forbid dates and times in the past." +#: ../system/integrations/index.rst:6 +msgid "We're still working on this part of our documentation, stay tight!" msgstr "" -#: ../system/objects/types.rst:70 -msgid "Default time diff (minutes)" +#: ../system/integrations/index.rst:10 +msgid "Integrations for Phone Systems" msgstr "" -#: ../system/objects/types.rst:69 +#: ../system/integrations/index.rst:14 msgid "" -"This setting helps the user by highlighting the day from now plus the " -"provided value. It does not pre-fill the field." +"Your VoIP provider or telephony system is not listed? Possibly your provider " +"supports Zammad by using the generic CTI - if you're unsure ask your " +"provider." msgstr "" -#: ../system/objects/types.rst:0 -#, fuzzy -msgid "Available settings for Date & time fields" -msgstr "Réglages avancés" +#: ../system/integrations/index.rst:18 +msgid "" +"Provider does not support Zammad? Consider creating a `feature request in " +"the Zammad Community `_." +msgstr "" -#: ../system/objects/types.rst:86 -msgid "Integer field" +#: ../system/integrations/index.rst:31 +msgid "Integrations for Authentication and Customers" msgstr "" -#: ../system/objects/types.rst:76 -msgid "" -"Provides an input field that allows integer usage only. You may define a " -"default value. You cannot enforce comma separation." +#: ../system/integrations/index.rst:44 +msgid "Integrations for Monitoring Systems" msgstr "" -#: ../system/objects/types.rst:80 -msgid "Minimal" +#: ../system/integrations/index.rst:46 +msgid "This section currently misses the following integrations:" msgstr "" -#: ../system/objects/types.rst:80 -msgid "The minimal value the field accepts." +#: ../system/integrations/index.rst:48 +msgid "Icinga" msgstr "" -#: ../system/objects/types.rst:83 -msgid "Maximal" +#: ../system/integrations/index.rst:49 +msgid "Monit" msgstr "" -#: ../system/objects/types.rst:83 -msgid "The maximum value the field accepts." +#: ../system/integrations/index.rst:50 +msgid "Nagios" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Integer fields" +#: ../system/integrations/index.rst:60 +msgid "Integrations for Issue Trackers" msgstr "" -#: ../system/objects/types.rst:99 -msgid "Multiple selection field" +#: ../system/integrations/index.rst:70 +msgid "Other Integrations" msgstr "" -#: ../system/objects/types.rst:89 +#: ../system/integrations/index.rst:72 msgid "" -"Provides a selection field that allows the selection of one or more out of " -"several. This field does allow setting a default value." +"This section will hold any other integration that can't be grouped up (yet)." msgstr "" -#: ../system/objects/types.rst:0 -#, fuzzy -msgid "Available settings for Multiple selection fields" -msgstr "Réglages avancés" +#: ../system/integrations/ldap/index.rst:2 +msgid "LDAP / Active Directory" +msgstr "" -#: ../system/objects/types.rst:112 -msgid "Single selection field" +#: ../system/integrations/ldap/index.rst:4 +msgid "" +"Zammad comes with a powerful LDAP integration that allows you to have a " +"single source of truth. By this you reduce the number of login credentials " +"your user has to remember." +msgstr "" + +#: ../system/integrations/ldap/index.rst:10 +msgid "" +"The LDAP source is also a perfect candidate for Zammad's :docs:`Kerberos " +"Single Sign-On ` but also works as addition " +"to other :doc:`/settings/security/third-party`." msgstr "" -#: ../system/objects/types.rst:102 -msgid "" -"Provides a drop-down field that allows selection of one value out of " -"several. This field does allow setting a default value." +#: ../system/integrations/ldap/index.rst:None +msgid "Zammands LDAP management page" msgstr "" -#: ../system/objects/types.rst:0 +#: ../system/integrations/ldap/index.rst:25 #, fuzzy -msgid "Available settings for Single selection fields" -msgstr "Réglages avancés" - -#: ../system/objects/types.rst:142 -msgid "Textarea field" -msgstr "" +msgid "📝 :doc:`manage`" +msgstr "Dernière valeur de contact utilisée à :doc:`/manage/trigger`" -#: ../system/objects/types.rst:115 -msgid "" -"Provides a text area input field (multiple lines) and thus allows e.g. new " -"lines. You can set a default field value." +#: ../system/integrations/ldap/index.rst:25 +msgid "Add, modify, remove or re-arrange your LDAP-Sources as needed." msgstr "" -#: ../system/objects/types.rst:120 -msgid "" -"Please note that this field *does not* support text formatting or HTML " -"content (rich text)." +#: ../system/integrations/ldap/index.rst:30 +msgid "Before you continue, please note the following limitations." msgstr "" -#: ../system/objects/types.rst:123 -msgid "**🥵 This field can consume a lot of visual space**" +#: ../system/integrations/ldap/index.rst:32 +msgid "Mapping / Synchronizing organizations is not possible" msgstr "" -#: ../system/objects/types.rst:125 +#: ../system/integrations/ldap/index.rst:36 msgid "" -"Depending on where you use this field type, it may use a lot of visual space " -"if you provide a lot of text. This may be an issue to work with." -msgstr "" - -#: ../system/objects/types.rst:130 -msgid "Default" +"You may want to consider using domain based assignments to overcome this " +"issue. Learn more on :doc:`/manage/organizations/index`." msgstr "" -#: ../system/objects/types.rst:129 +#: ../system/integrations/ldap/index.rst:39 msgid "" -"The here provided text will be shown within the text area field or new data " -"sets." +"Zammad's LDAP sync is one way. Editing user settings or permissions may be " +"overwritten upon the next sync depending on your configuration." msgstr "" -#: ../system/objects/types.rst:134 ../system/objects/types.rst:160 -msgid "Maxlength" +#: ../system/integrations/ldap/index.rst:41 +msgid "Nested groups are not supported." msgstr "" -#: ../system/objects/types.rst:0 ../system/objects/types.rst:160 -msgid "You can pick the maximum length of the field." +#: ../system/integrations/ldap/index.rst:42 +msgid "Synchronizing user avatars from LDAP is not supported." msgstr "" -#: ../system/objects/types.rst:0 -msgid "The default length of this object is ``500``." +#: ../system/integrations/ldap/index.rst:43 +msgid "Unlike user filters, group filters cannot be changed." msgstr "" -#: ../system/objects/types.rst:139 -msgid "Rows" +#: ../system/integrations/ldap/index.rst:44 +msgid "" +"When a user originates from an LDAP server, Zammad will try to verify the " +"login credentials against LDAP first - if this fails Zammad will check its " +"local database." msgstr "" -#: ../system/objects/types.rst:0 +#: ../system/integrations/ldap/index.rst:50 msgid "" -"Change the number of rows to dislay so that you can use only the space you " -"really need." +"Users can have local passwords even if they're LDAP users! You can learn " +"more about user accounts in general on :doc:`/manage/users/index`." msgstr "" -#: ../system/objects/types.rst:0 -msgid "The default number of rows is ``4``." +#: ../system/integrations/ldap/index.rst:54 +msgid "" +"When several LDAP sources contain the same user (meaning the same email " +"address), the user in question will be updated with every source configured. " +"*The last LDAP source will win.*" msgstr "" -#: ../system/objects/types.rst:0 +#: ../system/integrations/ldap/index.rst:58 #, fuzzy -msgid "Available settings for Textarea fields" -msgstr "Réglages avancés" +msgid "" +"This is subject to change with `Issue 4109 `_ in the future." +msgstr "" +"Actuellement non disponible, voir `Issue 2769 `_" -#: ../system/objects/types.rst:165 -msgid "Text field" +#: ../system/integrations/ldap/index.rst:60 +msgid "" +"Synchronization statistics currently affect *all* configured LDAP sources. " +"This also applies for newly added or updated sources." msgstr "" -#: ../system/objects/types.rst:145 -msgid "Provides a text field (one line) and allows choosing a default value." +#: ../system/integrations/ldap/index.rst:63 +#, fuzzy +msgid "" +"This is subject to change with `Issue 4108 `_ in the future." msgstr "" +"Actuellement non disponible, voir `Issue 2769 `_" -#: ../system/objects/types.rst:148 +#: ../system/integrations/ldap/index.rst:65 msgid "" -"Defines the type of the input field. This allows e.g. your browser to ensure " -"that you provide the specific type." +"Zammad currently has limited fallback server support. You can workaround " +"this by providing several sources - however, ensure to have the exact same " +"configuration on your fallback." msgstr "" -#: ../system/objects/types.rst:152 -msgid "Currently available:" +#: ../system/integrations/ldap/index.rst:69 +#, fuzzy +msgid "" +"This is subject to improve with `Issue 4107 `_ in the future." msgstr "" +"Actuellement non disponible, voir `Issue 2769 `_" -#: ../system/objects/types.rst:155 -msgid "Phone" +#: ../system/integrations/ldap/index.rst:76 +msgid "" +"This section holds all requests Zammad handled for all LDAP sources. These " +"entries can either contain synchronization information or logins " +"(authentication attempts via Zammad's login interface)." msgstr "" -#: ../system/objects/types.rst:156 -msgid "Text" +#: ../system/integrations/ldap/index.rst:80 +msgid "" +"By clicking on any request, Zammad will provide even more information. The " +"provided information can be useful when something does not work as expected." msgstr "" -#: ../system/objects/types.rst:157 -msgid "Url *(URL fields disable link-template availability)*" +#: ../system/integrations/ldap/index.rst:85 +msgid "" +"Especially a LDAP synchronization can cause many log entries. The web " +"interface will always limit the number of shown entries to the last 50 " +"entries." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Text fields" +#: ../system/integrations/ldap/index.rst:None +msgid "" +"Screencast showing LDAP integration log entries and a detail view on\n" +"an entry." msgstr "" -#: ../system/objects/types.rst:174 -msgid "Single tree selection field" +#: ../system/integrations/ldap/manage.rst:2 +msgid "Manage LDAP-Sources" msgstr "" -#: ../system/objects/types.rst:168 +#: ../system/integrations/ldap/manage.rst:6 msgid "" -"Provides a select-like field with up to 6 layers of options. Does not allow " -"setting a default value." +"Please keep in mind all current limitations for the LDAP synchronization. " +"This will help to understand scopes of the following operations better." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Tree Select fields" +#: ../system/integrations/ldap/manage.rst:65 +msgid "Add new source" msgstr "" -#: ../system/objects/types.rst:183 -msgid "Multiple tree selection field" +#: ../system/integrations/ldap/manage.rst:10 +msgid "" +"Using the *New Source* button allows you to add new LDAP sources to your " +"installation. You're not limited in the number of sources, however, keep in " +"mind that many sources will also take more time to synchronize." msgstr "" -#: ../system/objects/types.rst:177 +#: ../system/integrations/ldap/manage.rst:14 msgid "" -"Provides a select-like field with up to 6 layers of options allowing the " -"selection of multiple values. Does not allow setting a default value." +"You can choose between different encryption types, namely *SSL* and " +"*STARTTLS* or none of them (\"*No SSL*\"). If you choose *SSL* or " +"*STARTTLS*, Zammad will display an additional *SSL verification* option that " +"allows you to disable the verification, e.g. for self-signed SSL " +"certificates. You can also tell Zammad to use a different port by appending " +"``:`` to your hostname/IP." msgstr "" -#: ../system/objects/types.rst:302 -msgid "External Data Source field" +#: ../system/integrations/ldap/manage.rst:0 +msgid "" +"Screenshot of configuring a new LDAP source with SSL encryption and SSL " +"verification" msgstr "" -#: ../system/objects/types.rst:186 +#: ../system/integrations/ldap/manage.rst:26 msgid "" -"Provides a searchable field which fetches data from an external system. This " -"can be useful if you have data outside of Zammad and don't want to maintain " -"both data sources." +"New Source with SSL transport security enabled and certificate verification" msgstr "" -#: ../system/objects/types.rst:190 -msgid "The feature works as follows:" +#: ../system/integrations/ldap/manage.rst:30 +msgid "" +"Using an user filter can be a good idea if you only require a small subset " +"of your LDAP users in Zammad." msgstr "" -#: ../system/objects/types.rst:192 -msgid "" -"Zammad sends a query with a search string (free text from agent or based on " -"a variable) in a pre-defined format (\"Search URL\") to an external system." +#: ../system/integrations/ldap/manage.rst:42 +msgid "This especially affects inactive users" msgstr "" -#: ../system/objects/types.rst:195 +#: ../system/integrations/ldap/manage.rst:34 msgid "" -"This external system searches for matches and provides a response as a JSON " -"structure to Zammad." +"As every LDAP behaves differently on which attributes and how they are set, " +"Zammad doesn't care about any flags." msgstr "" -#: ../system/objects/types.rst:197 +#: ../system/integrations/ldap/manage.rst:37 msgid "" -"Zammad just looks for the defined list and value keys, reads the content and " -"displays the value to the user. There is no search on Zammad side." +"Users that no longer are returned by your LDAP source will automatically be " +"set to inactive. Zammad assumes that the user was deactivated." msgstr "" -#: ../system/objects/types.rst:201 +#: ../system/integrations/ldap/manage.rst:41 msgid "" -"The usage of a PostgreSQL database for Zammad is required. In any other " -"case, Zammad will hide the external data source type and you are not able to " -"use it. If you want to use this feature, consider to :docs:`migrate your " -"database `." +"Users will never be removed automatically! If you want to remove obsolete " +"users, use :doc:`/system/data-privacy`." msgstr "" -#: ../system/objects/types.rst:205 -msgid "Currently, only ``GET`` is supported as request method." +#: ../system/integrations/ldap/manage.rst:46 +msgid "Active Directory admins" msgstr "" -#: ../system/objects/types.rst:206 +#: ../system/integrations/ldap/manage.rst:45 msgid "" -"The data structure must be in JSON format and provide the objects in an " -"array." +"Active Directories are quite specific on how to filter for active users only " +"- please see the `Microsoft documentation `_ for more " +"information." msgstr "" -#: ../system/objects/types.rst:208 +#: ../system/integrations/ldap/manage.rst:51 msgid "" -"The endpoint for the external data source has to support search. On Zammad " -"side, there is no search/logic implemented; however, you can define the " -"output key and value based on the result(s) from the response (which " -"provides already filtered content based on the search)." +"*Do not* manually write pathes of either LDAP attributes or groups. If " +"Zammad does not display them, it either cannot find them or you have a lot " +"of users that don't have the attributes populated." msgstr "" -#: ../system/objects/types.rst:212 +#: ../system/integrations/ldap/manage.rst:55 msgid "" -"If you receive more results as expected, your external data source search " -"may not work properly or the structure of the URL is not correct. You should " -"get in touch with a responsible person from the external system." +"Zammad will always only return attributes that are filled - this reduces the " +"returned list of attributes greatly." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing how to add a new LDAP source" msgstr "" -#: ../system/objects/types.rst:217 +#: ../system/integrations/ldap/manage.rst:63 msgid "" -"Please have a look :doc:`at our example `, where you can find a possible configuration for a public " -"dummy endpoint." +"If your LDAP system doesn't allow anonymous bind, Zammad detects it and " +"provides you an editable \"Base DN\" *text* field instead of a prefilled " +"*select* field." msgstr "" -#: ../system/objects/types.rst:0 -#, fuzzy -msgid "Available settings for external data source fields" -msgstr "Réglages avancés" - -#: ../system/objects/types.rst:242 -msgid "Search URL" +#: ../system/integrations/ldap/manage.rst:81 +msgid "Review or edit existing source" msgstr "" -#: ../system/objects/types.rst:227 +#: ../system/integrations/ldap/manage.rst:68 msgid "" -"Set your endpoint where Zammad fetches the data. Please make sure to include " -"a valid search :doc:`variable <../variables>` as an URL parameter. Example " -"for a free text search at user input: ``#{search.term}``" +"Clicking on a LDAP source will provide a configuration and mapping overview." msgstr "" -#: ../system/objects/types.rst:232 +#: ../system/integrations/ldap/manage.rst:70 msgid "" -"If in doubt, ask the responsible person for the external data source how " -"they expect the strucuture of the URL." +"If needed you can then use the *Change* button to update either the name, " +"active state or the whole configuration. If you're changing the whole " +"configuration, the dialogue will be identical to the source creation." msgstr "" -#: ../system/objects/types.rst:236 +#: ../system/integrations/ldap/manage.rst:76 msgid "" -"Depending on your search variable, the preview might work or not. The reason " -"is that the context might not be available and it is no bug." +"Did your LDAP server change? Different LDAP servers have different " +"structures and default attributes. This causes the LDAP synchronization to " +"likely fail. Consider removing the affected source and re-add it." msgstr "" -#: ../system/objects/types.rst:239 -msgid "" -"Please also make sure to use a variable which is available in your object " -"context. For example you won't be able to search for a ticket in a user " -"object context." +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing the update of the source name." msgstr "" -#: ../system/objects/types.rst:252 -#, fuzzy -msgid "SSL Verification" -msgstr "Bloquer les notifications" +#: ../system/integrations/ldap/manage.rst:89 +msgid "Re-arrange LDAP source's order" +msgstr "" -#: ../system/objects/types.rst:245 -msgid "Here you can switch the SSL verification to no." +#: ../system/integrations/ldap/manage.rst:84 +msgid "" +"You can change the synchronization order for each source at any time. Zammad " +"will synchronize the sources from top to bottom." msgstr "" -#: ../system/objects/types.rst:249 +#: ../system/integrations/ldap/manage.rst:0 msgid "" -"If your external data source system is using self signed certificates, " -"please have a look :doc:`here ` for " -"further information about how to handle them in Zammad, so you can keep the " -"SSL verification activated." +"Screencasting showing how to change the source order by using\n" +"drag and drop." msgstr "" -#: ../system/objects/types.rst:258 -msgid "HTTP Authentication" +#: ../system/integrations/ldap/manage.rst:101 +msgid "Remove a source" msgstr "" -#: ../system/objects/types.rst:255 +#: ../system/integrations/ldap/manage.rst:92 msgid "" -"If your external data source requires an authentication, you can set it " -"here. You can leave it empty or choose between *Basic Authentication* or " -"*Authentication Token* (selecting one of the two methods leads to additional " -"fields where you can enter your credentials/token)." +"If you no longer need the a LDAP source or simply want to start over, you " +"can remove them at any time. This will not remove synchronized users, data " +"synchronized or permissions." msgstr "" -#: ../system/objects/types.rst:265 -msgid "Search result list key" +#: ../system/integrations/ldap/manage.rst:98 +msgid "" +"Not sure if you'd need the source later on? Set the source to inactive " +"instead of removing it - see *Review or edit existing source* for more." msgstr "" -#: ../system/objects/types.rst:261 -msgid "" -"Defines the level in the JSON structure which provides the list with search " -"results. You can leave it empty, if the data is already provided as an " -"array. If you have to go deeper in the structure, you can provide a path " -"with ``.`` as separators, e.g. ``key.subkey.sub-sub-key``." +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing how to remove LDAP sources." msgstr "" -#: ../system/objects/types.rst:271 -msgid "Search result value key" +#: ../system/integrations/pgp/index.rst:2 +msgid "PGP" msgstr "" -#: ../system/objects/types.rst:268 +#: ../system/integrations/pgp/index.rst:7 msgid "" -"Defines the attribute in the structure in which your external data source " -"provides the *value* for your data. An example would be a product *number*. " -"If you have to go deeper in the structure, you can provide a path with ``.`` " -"as separators, e.g. ``key.subkey.sub-sub-key``." +"Pretty Good Privacy (PGP) is another method for secure email communication. " +"With PGP, you can exchange **signed** and **encrypted** messages with others." msgstr "" -#: ../system/objects/types.rst:277 -msgid "Search result label key" +#: ../system/integrations/pgp/index.rst:13 +#: ../system/integrations/smime/index.rst:17 +msgid "Signing" msgstr "" -#: ../system/objects/types.rst:274 -msgid "" -"Defines the attribute in the structure in which your external data source " -"provides the *label* for your data. An example would be a product *name*. If " -"you have to go deeper in the structure, you can provide a path with ``.`` as " -"separators, e.g. ``key.subkey.sub-sub-key``." +#: ../system/integrations/pgp/index.rst:11 +msgid "is a proof that a message hasn't been manipulated on its way." msgstr "" -#: ../system/objects/types.rst:280 +#: ../system/integrations/pgp/index.rst:13 msgid "" -"In the preview area, you can find the following items (depending on your " -"configuration above):" +"In other words, it guarantees message **integrity** and **authenticity**." msgstr "" -#: ../system/objects/types.rst:283 -msgid "" -"**Error/hint message** (only if configuration is not complete): Zammad tells " -"you, if there is a problem and what you should change in your configuration." +#: ../system/integrations/pgp/index.rst:19 +#: ../system/integrations/smime/index.rst:22 +msgid "Encryption" msgstr "" -#: ../system/objects/types.rst:286 +#: ../system/integrations/pgp/index.rst:16 +#: ../system/integrations/smime/index.rst:20 msgid "" -"**Search field**: search for an existing attribute in the data source to get " -"a preview. This is required for the fields below to show up." +"scrambles a message so that it can only be unscrambled by the intended " +"recipient." msgstr "" -#: ../system/objects/types.rst:288 +#: ../system/integrations/pgp/index.rst:19 msgid "" -"**Search result response** (only if configuration is not complete): here you " -"can find a syntax highlighted JSON preview of the response, based on the " -"search term you entered." +"In other words, it guarantees message **privacy** and **data security**." msgstr "" -#: ../system/objects/types.rst:291 -msgid "" -"**Search result list** (only if *search result list key* is properly set): " -"output of the structure under the configured *search result list key*." +#: ../system/integrations/pgp/index.rst:25 +msgid "Screenshot of ticket creation with encrypt and sign buttons" msgstr "" -#: ../system/objects/types.rst:294 +#: ../system/integrations/pgp/index.rst:25 msgid "" -"**Preview table** (when fully configured): Zammad shows you a table which " -"includes the found items based on the search string (value, label and " -"optional link). You can use this preview if you don't have the complete data " -"structure of the external system in mind." +"Once PGP has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " +"appear in the ticket composer." msgstr "" -#: ../system/objects/types.rst:299 -msgid "" -"An example of a configured external data source field from agent perspective:" +#: ../system/integrations/pgp/index.rst:28 +msgid "**Sign button not visible?**" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Screencast showing the search for a product in a ticket" +#: ../system/integrations/pgp/index.rst:30 +msgid "" +"Please note that the signing of emails is based on the outgoing email " +"account. That means you have to choose a group with a sender email account, " +"which has a private key assigned." msgstr "" -#: ../system/objects/types.rst:307 -msgid "URL fields (Link-Template)" +#: ../system/integrations/pgp/index.rst:35 +msgid "Handling of Keys" msgstr "" -#: ../system/objects/types.rst:311 +#: ../system/integrations/pgp/index.rst:36 msgid "" -"This function is restricted to Text, Select and External data source types " -"only." +"To use the PGP function, you have to enable the integration (PGP) by " +"switching the toggle to *enabled*." msgstr "" -#: ../system/objects/types.rst:314 +#: ../system/integrations/pgp/index.rst:39 msgid "" -"Link-Templates are an amazing way to dynamically generate URLs. They allow " -"you to integrate other systems better without having to manually copy data " -"from Zammad if possible." +"You can add keys by clicking the *add key* button. The keys can be imported " +"from a file or you can paste the content of the key in the text box." msgstr "" -#: ../system/objects/types.rst:320 -msgid "" -"Another great way of communicating with another system may be Zammad's :doc:" -"`Webhooks `." +#: ../system/integrations/pgp/index.rst:42 +msgid "**Which keys do I have to import?**" msgstr "" -#: ../system/objects/types.rst:323 +#: ../system/integrations/pgp/index.rst:44 msgid "" -"After filling a link-template enabled field, an URL icon will appear on its " -"right. Clicking on the icon opens a new tab." +"For **signing** *outgoing* emails, you have to import the private key of " +"your Zammad email account." msgstr "" -#: ../system/objects/types.rst:328 +#: ../system/integrations/pgp/index.rst:47 msgid "" -"Even though Zammad displays the link template within object edit and create " -"screens, the function is optional. It's only active if you populate the " -"field." +"For **encrypting** *outgoing* emails, you have to import the public key of " +"the customer's email account." msgstr "" -#: ../system/objects/types.rst:333 +#: ../system/integrations/pgp/index.rst:50 msgid "" -"What's the difference between URL and text fields with link template...?!" +"For **verifying the signature** of signed *incoming* emails, you have to " +"import the public key of the customer." msgstr "" -#: ../system/objects/types.rst:335 +#: ../system/integrations/pgp/index.rst:53 msgid "" -"Both fields have different use cases. Use ``text`` type text fields when " -"ever you have a *static* url that requires dynamic parameters. If you " -"require a drag & drop like field that you can put in any URL, use ``URL`` " -"type text fields." +"For **decrypting** of encrypted *incoming* emails, you have to import the " +"private key of your Zammad email account." msgstr "" -#: ../system/objects/types.rst:340 -msgid "" -"The difference is easier to spot when comparing the fields directly, below " -"screencast shows the result - the dynamic approach uses existing values in " -"the moment of updating to built the URL - e.g. ``https://google.com/search?" -"q=cookies`` - while the URL approach uses the actual URL of the field - e.g. " -"``https://zammad.com``." +#: ../system/integrations/pgp/index.rst:57 +msgid "Import Keys From a File" msgstr "" -#: ../system/objects/types.rst:None -msgid "" -"Screencast showing the differents in between URL and text type fields with " -"actual values" +#: ../system/integrations/pgp/index.rst:58 +msgid "You can import keys from a file in the section **Upload key**:" msgstr "" -#: ../system/objects/types.rst:352 -msgid "How does this work...?!" +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of adding a key via file" msgstr "" -#: ../system/objects/types.rst:354 +#: ../system/integrations/pgp/index.rst:64 msgid "" -"As an example, let's say you have an attribute called ``amazing_attribute`` " -"and you want to open a google search directly with the input from that field." +"**Supported file formats:** ASCII-armor as well as binary GPG format " +"(basically any GPG supported key format) is supported here." msgstr "" -#: ../system/objects/types.rst:357 -msgid "" -"Providing the link-template field below allows you to do so: ``https://www." -"google.com/search?q=#{ticket.amazing_attribute}``" +#: ../system/integrations/pgp/index.rst:68 +msgid "Import Keys by Pasting the Content" msgstr "" -#: ../system/objects/types.rst:362 +#: ../system/integrations/pgp/index.rst:69 +msgid "You can also paste the key's content in the section **paste key**:" +msgstr "" + +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of adding a key via pasting" +msgstr "" + +#: ../system/integrations/pgp/index.rst:75 msgid "" -"You can use any :doc:`Zammad variable ` as long as it's " -"available in the moment you need it." +"**Supported format:** Please note that only ASCII-armor is supported here." msgstr "" -#: ../system/objects/types.rst:365 +#: ../system/integrations/pgp/index.rst:78 +#, fuzzy +msgid "Deleting Keys" +msgstr "Bloquer les notifications" + +#: ../system/integrations/pgp/index.rst:79 msgid "" -"As a result, you are redirected to Google with a search for the value of the " -"attribute, if you click on the button in the ticket (as you can see in the " -"screencast above)." +"If you want to delete a specific key, you can do it by clicking on the menu " +"in the *actions* column and select **delete**:" msgstr "" -#: ../system/packages.rst:2 -msgid "Packages" +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of deleting a key" msgstr "" -#: ../system/packages.rst:4 -msgid "That's the package management-area." +#: ../system/integrations/pgp/index.rst:88 +msgid "Downloading Keys" msgstr "" -#: ../system/packages.rst:6 -msgid "Individual add-ons for Zammad can be installed and managed here." +#: ../system/integrations/pgp/index.rst:89 +msgid "" +"If you want to download your keys, you can do this as well via corresponding " +"action buttons. Depending on the key, you can choose wether you want to " +"download the private or the public key." msgstr "" -#: ../system/sessions.rst:2 -msgid "Sessions" +#: ../system/integrations/pgp/index.rst:95 +#: ../system/integrations/smime/manage-certificates.rst:76 +msgid "Default Behavior" msgstr "" -#: ../system/sessions.rst:4 +#: ../system/integrations/pgp/index.rst:96 msgid "" -"Sessions management allows reviewing currently known user sessions and " -"allows to end these. The session timeout is affected by :ref:" -"`security_session_timeout` configurations from security settings." -msgstr "" - -#: ../system/sessions.rst:None -msgid "Screenshot showing Zammad's session management" +"Here you can adjust on per group basis, if *sign* and *encryption* is on or " +"off by default. Please be aware, that agents can always override the setting " +"for each individual article." msgstr "" -#: ../system/sessions.rst:13 -msgid "Zammad will provide the following information:" +#: ../system/integrations/pgp/index.rst:None +msgid "Adjusting default behavior on per group basis" msgstr "" -#: ../system/sessions.rst:16 +#: ../system/integrations/pgp/index.rst:107 msgid "" -"The user account this session entry belongs to. It can be normal if a user " -"has several sessions in the list. This can be due to changed browser " -"information or if you use e.g. single sign on methods where the user does " -"not use the log off button." +"Here you can see the last actions regarding signing and encryption and if " +"they were successful." msgstr "" -#: ../system/sessions.rst:22 -msgid "Browser" +#: ../system/integrations/pgp/index.rst:117 +msgid "**Sign button is not visible, but keys are imported.**" msgstr "" -#: ../system/sessions.rst:22 -msgid "The browser agent communicated to Zammad." +#: ../system/integrations/pgp/index.rst:115 +msgid "Did you choose a group in the ticket?" msgstr "" -#: ../system/sessions.rst:40 -#, fuzzy -msgid "Location" -msgstr "Bloquer les notifications" - -#: ../system/sessions.rst:25 +#: ../system/integrations/pgp/index.rst:116 msgid "" -"The anticipated location based on the users IP address. Depending on the IP " -"address the result shown may differ. This option depends on :doc:`/settings/" -"system/services`." -msgstr "" - -#: ../system/sessions.rst:29 -msgid "The following information can be shown:" +"Did you import a private key for the email adress, which is used for " +"outgoing emails in the group?" msgstr "" -#: ../system/sessions.rst:33 -msgid "IP address" +#: ../system/integrations/pgp/index.rst:122 +msgid "**How to obtain keys?**" msgstr "" -#: ../system/sessions.rst:32 +#: ../system/integrations/pgp/index.rst:120 msgid "" -"Either if you set *Geo IP services* to inactive or you're using internal IP " -"address which do not provide location information." +"You can create them yourself! There are some good tutorials on the web on " +"how to create them. Providing keys to Zammad is a prerequisite to use the " +"PGP feature." msgstr "" -#: ../system/sessions.rst:40 -msgid "Country (or Country + City)" +#: ../system/integrations/pgp/index.rst:127 +msgid "**It says a passphrase is needed, but I haven't got one.**" msgstr "" -#: ../system/sessions.rst:36 +#: ../system/integrations/pgp/index.rst:125 msgid "" -"If *Geo IP services* is enabled only. Depends on how detailed the available " -"IP address information are." +"If the key is secured with a passphrase, you have to provide it for the " +"import in Zammad. It is possible that keys may have an empty passphrase. " +"However, this is *not* recommended." msgstr "" -#: ../system/sessions.rst:39 +#: ../system/integrations/pgp/index.rst:132 +msgid "**How do my customers get my new key?**" +msgstr "" + +#: ../system/integrations/pgp/index.rst:130 msgid "" -"Be aware that results can be inaccurate - this technically is not an error." +"You have to provide your **public** key in advance. Your customer also has " +"to configure PGP in their email workflow and import your public key. The " +"other way round, you have to get the public key of your customer and have to " +"import it to Zammad." msgstr "" -#: ../system/sessions.rst:43 -msgid "Age" +#: ../system/integrations/slack.rst:2 +msgid "Slack" msgstr "" -#: ../system/sessions.rst:43 -msgid "Provides the time when the session initially has been created." +#: ../system/integrations/slack.rst:4 +msgid "**⚠️ Deprecation warning ⚠️**" msgstr "" -#: ../system/sessions.rst:50 -msgid "Update" +#: ../system/integrations/slack.rst:6 +msgid "" +"Zammad 7 will no longer support this dedicated Slack integration. It is " +"recommended to switch to :doc:`pre-defined webhooks ` instead. Existing Slack integrations should " +"be migrated manually before this feature is dropped." msgstr "" -#: ../system/sessions.rst:46 +#: ../system/integrations/slack.rst:14 msgid "" -"Provides the time the user used this session to open Zammad. This timestamp " -"is only updated if the user e.g. reloads, not during normal work on tickets." +"In order to use this feature, please add a new Slack app to your Workspace. " +"The App you need is called ``Incoming WebHooks`` ." msgstr "" -#: ../system/sessions.rst:50 -msgid "This timestamp is being used for the session timeout." +#: ../system/integrations/slack.rst:18 +msgid "Why Do I Need This Feature?" msgstr "" -#: ../system/sessions.rst:53 +#: ../system/integrations/slack.rst:20 msgid "" -"Use the delete button to remove a single session on behalf of your user." +"If you're already using Slack for your team communication, you'll love this " +"feature! Our Slack integration can push ticket notifications about the last " +"ticket article based on the following events:" msgstr "" -#: ../system/subscription/billing.rst:2 -msgid "Billing" +#: ../system/integrations/slack.rst:24 +msgid "on Ticket creation" msgstr "" -#: ../system/subscription/billing.rst:4 -msgid "" -"Within the billing tab you can control all billing relevant information like " -"invoices, billing address and the option to cancel your subscription." +#: ../system/integrations/slack.rst:25 +msgid "on Ticket updates" msgstr "" -#: ../system/subscription/billing.rst:33 -msgid "Billing information" +#: ../system/integrations/slack.rst:26 +msgid "on reached reminders" msgstr "" -#: ../system/subscription/billing.rst:8 -msgid "" -"All adjusted billing information below only affect future invoices. If your " -"invoice was issued wrong, please contact `our sales team `_." +#: ../system/integrations/slack.rst:27 +msgid "a Ticket has escalated" msgstr "" -#: ../system/subscription/billing.rst:14 -msgid "Billing address" +#: ../system/integrations/slack.rst:28 +msgid "a Ticket is going to escalate" msgstr "" -#: ../system/subscription/billing.rst:13 +#: ../system/integrations/slack.rst:30 msgid "" -"Provide your company address here, make sure to include the companies name " -"in case required. This address will be referenced on your invoice." +"Zammad will provide the Ticket title, a direct link to the Ticket, the event " +"type (creation, updated, escalation), the customer, time and the last " +"article that has triggered the notification." msgstr "" -#: ../system/subscription/billing.rst:18 -msgid "VAT ID" +#: ../system/integrations/slack.rst:34 +msgid "" +"This will give you further options, as you can see e.g. escalating tickets " +"that are assigned to an agent that's e.g. absent. You can interact faster, " +"as you might see problems earlier (or even before the problem gets one)." msgstr "" -#: ../system/subscription/billing.rst:17 +#: ../system/integrations/slack.rst:38 msgid "" -"Provide your VAT ID here. If applicable your invoice will not contain German " -"VAT. Please make sure to pay the VAT in your country as required." +"If needed and wanted, you can even discuss directly about the topic before " +"sending an answer to the customer. Another possible use case would be a " +"agent monitoring new agents and their answers to tickets." msgstr "" -#: ../system/subscription/billing.rst:27 -msgid "Billing Email Address" +#: ../system/integrations/slack.rst:44 +#, fuzzy +msgid "Configure the Integration" +msgstr "Configuration du greffon de clavardage" + +#: ../system/integrations/slack.rst:46 +msgid "" +"First of all, please go to your slack workspace - go to administration => " +"Manage Apps. If you don't have an app yet, you can simply add a new one - " +"just search for ``Incoming WebHooks`` and customize the app to your needs." msgstr "" -#: ../system/subscription/billing.rst:21 +#: ../system/integrations/slack.rst:50 msgid "" -"Usually the instance owner (the person that registered the instance) will " -"receive all emails including the invoices. In case you have your own billing " -"department, you can provide their email address here." +"Choose (or create) the channel Zammad should post it's information to and " +"press on \"Add Incoming WebHooks integration\". If you're ready, copy the " +"provided WebHook URL and go to your Zammad installation." msgstr "" -#: ../system/subscription/billing.rst:25 +#: ../system/integrations/slack.rst:56 msgid "" -"All billing relevant information will then be sent to this email address." +"You need administrative rights on the Slack Workspace. The link to the app " +"directory is normally ``https://[workspace-name].slack.com/apps`` ." msgstr "" -#: ../system/subscription/billing.rst:27 -msgid "Invoices are sent as attachment (PDF) to this email address." +#: ../system/integrations/slack.rst:63 +msgid "" +"To configure the slack integration, log in to Zammad and go to Integrations " +"(System) => Slack in the admin panel." msgstr "" -#: ../system/subscription/billing.rst:29 +#: ../system/integrations/slack.rst:66 msgid "" -"Don't forget to press the *Submit* button after you changed above settings." +"Here you can choose on what evens Zammad should post information about a " +"ticket to your Slack channel. Next you need to device what groups shall be " +"affected by this, as anybody with access to that specific Slack channel can " +"read at least parts of the ticket this might be a privacy issue, if you " +"select the wrong groups. The username is simply the name that Zammad uses as " +"display name inside the Slack chat. The channel defines the Slack channel " +"the information is being posted in. As last option, you can set a custom " +"icon for posting to slack." msgstr "" -#: ../system/subscription/billing.rst:0 +#: ../system/integrations/slack.rst:74 msgid "" -"Screenshot showing options for billing information within the\n" -"subscription menu" +"When you're ready, just hit \"Submit\" and enable the integration. Zammad " +"will now post new ticket information based on the trigger you chose. Below " +"the options you have the recent log that shows the latest requests to Slack " +"for debugging if needed." msgstr "" -#: ../system/subscription/billing.rst:70 -msgid "Payment history" +#: ../system/integrations/slack.rst:81 +msgid "" +"If you leave the Icon URL empty, Zammad will use the Zammad logo instead. " +"The icon should be a square PNG file." msgstr "" -#: ../system/subscription/billing.rst:36 +#: ../system/integrations/slack.rst:90 msgid "" -"The payment history will display a history of all paid invoices. At this " -"point you can also download these in case you need them again." +"The following figure shows how it will look if you choose to receive updates " +"on created and updated tickets. On every post Zammad sends to the Slack " +"channel, you can create new threads to discuss about the new article." msgstr "" -#: ../system/subscription/billing.rst:41 +#: ../system/integrations/slack.rst:96 msgid "" -"You will only find *paid* invoices here. Invoices that are to be billed are " -"not available before the payment is completed." +"If you just want to keep track of soon escalating or already escalated " +"tickets, it will look the the following figure. Zammad changes the color in " +"front of the post so you can easily see the state of the ticket." msgstr "" -#: ../system/subscription/billing.rst:46 -msgid "Date" +#: ../system/integrations/slack.rst:102 +msgid "" +"If you change the state, Zammad will also put information on what state the " +"ticket gets and (if pending state) the date until it pends. You'll also " +"recognize the color codes in front of posts on slack, as they are exact the " +"same the ticket state colors you'll see in Zammad!" msgstr "" -#: ../system/subscription/billing.rst:46 -msgid "Date of the invoice creation." +#: ../system/integrations/smime/index.rst:2 +msgid "S/MIME" msgstr "" -#: ../system/subscription/billing.rst:49 -#, fuzzy -msgid "Amount" -msgstr "Comptes" +#: ../system/integrations/smime/index.rst:11 +msgid "" +"S/MIME is the most widely-supported method for secure email communication. " +"With S/MIME, you can exchange **signed** and **encrypted** messages with " +"others." +msgstr "" -#: ../system/subscription/billing.rst:49 -msgid "Invoice total including VAT if applicable." +#: ../system/integrations/smime/index.rst:15 +msgid "" +"is proof that a message hasn't been tampered with or sent by an impersonator." msgstr "" -#: ../system/subscription/billing.rst:52 +#: ../system/integrations/smime/index.rst:17 msgid "" -"Contains contract period (monthly or yearly) and hosted plan for the " -"subscription period in question." +"In other words, it guarantees a message's **integrity** and **authenticity**." msgstr "" -#: ../system/subscription/billing.rst:63 -msgid "Payment method / Service period" +#: ../system/integrations/smime/index.rst:22 +msgid "In other words, it guarantees **privacy** and **data security**." msgstr "" -#: ../system/subscription/billing.rst:56 -msgid "" -"Used bank account or credit card as well as the subscription period the " -"invoice is about." +#: ../system/integrations/smime/index.rst:28 +msgid "Screencast demo of S/MIME features for both new tickets and replies" msgstr "" -#: ../system/subscription/billing.rst:61 +#: ../system/integrations/smime/index.rst:28 msgid "" -"It might happen that the invoice date and subscription period differ. This " -"is nothing to worry about, the subscription periods will be accounted later " -"on." +"Once S/MIME has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " +"appear in the ticket composer." msgstr "" -#: ../system/subscription/billing.rst:67 -msgid "Receipt" +#: ../system/integrations/smime/index.rst:32 +msgid ":doc:`🔪 Prerequisites `" msgstr "" -#: ../system/subscription/billing.rst:66 +#: ../system/integrations/smime/index.rst:31 msgid "" -"Use the arrow to download the invoice in question. You can download all " -"available invoices any time you need to here!" +"New to S/MIME? This section helps you to find certificate providers and " +"points out Limitations." msgstr "" -#: ../system/subscription/billing.rst:0 -msgid "Screenshot showing payment history of a hosted instance" +#: ../system/integrations/smime/index.rst:35 +msgid ":doc:`📝 Manage Certificates `" msgstr "" -#: ../system/subscription/billing.rst:94 -msgid "Do you want to cancel your subscription?" +#: ../system/integrations/smime/index.rst:35 +msgid "Add and download certificates; configure group default behaviors." msgstr "" -#: ../system/subscription/billing.rst:73 -msgid "" -"In case you no longer want to use Zammad's SaaS, you can cancel your " -"subscription by using the red *Yes, please cancel my subscription* button." +#: ../system/integrations/smime/index.rst:38 +msgid ":doc:`😦 Troubleshooting `" msgstr "" -#: ../system/subscription/billing.rst:76 -msgid "" -"Your subscription will end the day after your trial or billing period ends." +#: ../system/integrations/smime/index.rst:38 +msgid "Took a wrong turn? About recent logs and common issues." msgstr "" -#: ../system/subscription/billing.rst:80 +#: ../system/integrations/smime/index.rst:43 msgid "" -"We will remind you about your cancelled subscription several times up front. " -"After the subscription ended all instance data will be removed. A restore " -"*is not* possible after that point!" +"For more details on how S/MIME integration works on the agent side, see the :" +"user-docs:`user docs `." msgstr "" -#: ../system/subscription/billing.rst:0 -msgid "Screencast showing how to cancel a subscription" +#: ../system/integrations/smime/manage-certificates.rst:2 +msgid "Manage Certificates" msgstr "" -#: ../system/subscription/billing.rst:87 -msgid "**😖 Cancelled by accident?**" +#: ../system/integrations/smime/manage-certificates.rst:4 +msgid "" +"S/MIME is **disabled by default**. Enable it to start adding certificates." msgstr "" -#: ../system/subscription/billing.rst:89 -msgid "" -"You can always undo the cancellation via the *Yes, undo the cancellation of " -"my subscription* button up to the last subscription day!" +#: ../system/integrations/smime/manage-certificates.rst:10 +msgid "Dialogue to add new certificates or private keys" msgstr "" -#: ../system/subscription/billing.rst:0 +#: ../system/integrations/smime/manage-certificates.rst:10 msgid "" -"Screenshot showing a red button to cancel the subscription\n" -"cancellation" +"Manage certificates in the Admin Panel under **System > Integrations > S/" +"MIME**. Certificates may be pasted in as plain text or uploaded from a file." msgstr "" -#: ../system/subscription/index.rst:2 -msgid "Subscription (SaaS)" -msgstr "" +#: ../system/integrations/smime/manage-certificates.rst:14 +#, fuzzy +msgid "Add Certificate Data" +msgstr "Bloquer les notifications" -#: ../system/subscription/index.rst:4 -msgid "" -"The subscription settings page allows you to configure your instances " -"package and number of agents required." +#: ../system/integrations/smime/manage-certificates.rst:36 +msgid "Add Certificate" msgstr "" -#: ../system/subscription/index.rst:9 +#: ../system/integrations/smime/manage-certificates.rst:17 msgid "" -"This setting section is only available for Hosted setups. If you're looking " -"for on premise support contracts, please see the `Zammad pricing page " -"`_." +"Import public-key certificates for both your own organization and your " +"contacts." msgstr "" -#: ../system/subscription/index.rst:20 +#: ../system/integrations/smime/manage-certificates.rst:19 msgid "" -"The subscription section currently consists of two tabs: Plan & Billing. For " -"your overview we've divided those two tabs into independent sub pages:" +"You can also add a bunch of certificates in one go by providing a single " +"file with all relevant certificates." msgstr "" -#: ../system/subscription/index.rst:25 -msgid ":doc:`💰 Subscription plan `" +#: ../system/integrations/smime/manage-certificates.rst:22 +msgid "🕵️ **ALWAYS verify certificates in-person or over the phone!**" msgstr "" -#: ../system/subscription/index.rst:24 +#: ../system/integrations/smime/manage-certificates.rst:24 msgid "" -"Everything affecting your instance subscription functions like number of " -"agents, package and payment method." +"The whole point of signatures is to alert you when someone is trying to " +"pretend to be someone they're not. Never accept a certificate from someone " +"online without verifying it first." msgstr "" -#: ../system/subscription/index.rst:28 -msgid ":doc:`🧾 Subscription billing `" +#: ../system/integrations/smime/manage-certificates.rst:28 +msgid "📇 **What about trusted certificate authorities?**" msgstr "" -#: ../system/subscription/index.rst:28 +#: ../system/integrations/smime/manage-certificates.rst:30 msgid "" -"Everything regarding billing address, invoices and account cancellation." +"In some cases (e.g. when dealing with large enterprises), you may be given a " +"certificate for an entire CA, rather than a single contact. Add it here to " +"trust *all* certificates issued by that CA." msgstr "" -#: ../system/subscription/index.rst:33 -msgid "FAQ" +#: ../system/integrations/smime/manage-certificates.rst:35 +msgid "" +"Commercial CAs can usually be verified online. Zammad does not include a " +"list of built-in, trusted CAs." msgstr "" -#: ../system/subscription/index.rst:37 -msgid "I set up a trial account but am missing functions to test" +#: ../system/integrations/smime/manage-certificates.rst:57 +msgid "Add Private Key" msgstr "" -#: ../system/subscription/index.rst:36 +#: ../system/integrations/smime/manage-certificates.rst:39 msgid "" -"The trial instance is running within the professional package allowing up to " -"three agents." -msgstr "" - -#: ../system/subscription/index.rst:40 -msgid "Can I change package within the trial?" +"Once you've added a public-key certificate, you can import its matching " +"private key." msgstr "" -#: ../system/subscription/index.rst:40 -msgid "No. As soon as the package is changed the subscription begins." +#: ../system/integrations/smime/manage-certificates.rst:42 +msgid "" +"Private keys are for **your own organization only**; never ask your contacts " +"for their private keys." msgstr "" -#: ../system/subscription/index.rst:45 -msgid "What happens to my trial instance after the trial period ended?" +#: ../system/integrations/smime/manage-certificates.rst:0 +msgid "" +"S/MIME integration showing configured certificates and possible issues with " +"Logging" msgstr "" -#: ../system/subscription/index.rst:43 +#: ../system/integrations/smime/manage-certificates.rst:50 msgid "" -"Your instance will automatically be canceled for you. Please see *What " -"happens to my instance after it has been canceled?* for more." +"A note is displayed on certificates with a matching private key (see line 2)." msgstr "" -#: ../system/subscription/index.rst:58 -msgid "What happens to my instance after it has been canceled?" +#: ../system/integrations/smime/manage-certificates.rst:52 +msgid "📤 **Certificates and private keys must be uploaded separately.**" msgstr "" -#: ../system/subscription/index.rst:48 -msgid "That depends slightly on your instance state:" +#: ../system/integrations/smime/manage-certificates.rst:54 +msgid "" +"If your certificate and private key are bundled together in the same file or " +"PEM block, import it twice (once using each button)." msgstr "" -#: ../system/subscription/index.rst:54 -msgid "Trial instance" +#: ../system/integrations/smime/manage-certificates.rst:57 +msgid "Please note that bulk imports of private keys are not possible." msgstr "" -#: ../system/subscription/index.rst:51 +#: ../system/integrations/smime/manage-certificates.rst:60 +#, fuzzy +msgid "Download Certificate Data" +msgstr "Bloquer les notifications" + +#: ../system/integrations/smime/manage-certificates.rst:62 msgid "" -"If you're still on trial, we will ice your instance and remind you once " -"again about your instance. We then will wait some days and remove your " -"instance from our system. This is the last time we will inform you by Email." +"You can download the earlier provided certificates and private keys at any " +"time from your Zammad instance." msgstr "" -#: ../system/subscription/index.rst:58 -msgid "Paid instance" +#: ../system/integrations/smime/manage-certificates.rst:65 +msgid "" +"Please note that passphrase-protected private keys stay protected and when " +"you download them, you have to know the passphrase to use them after " +"downloading." msgstr "" -#: ../system/subscription/index.rst:57 -msgid "" -"If you're a paying customer and canceled your subscription, the instance " -"removal will take place the day after your last subscription day." +#: ../system/integrations/smime/manage-certificates.rst:73 +msgid "Dialogue to download certificates or private keys" msgstr "" -#: ../system/subscription/index.rst:60 -msgid "Can removed instances be restored?" +#: ../system/integrations/smime/manage-certificates.rst:73 +msgid "Download stored certificates and their keys" msgstr "" -#: ../system/subscription/index.rst:61 -msgid "No. Once your instance has been removed, a restoration is not possible." +#: ../system/integrations/smime/manage-certificates.rst:78 +msgid "" +"The ticket composer will set all outgoing messages to **signed and " +"encrypted** by default (assuming the required certificates exist)." msgstr "" -#: ../system/subscription/plan.rst:2 ../system/subscription/plan.rst:38 -msgid "Plan" +#: ../system/integrations/smime/manage-certificates.rst:82 +msgid "These defaults can be modified on a per-group basis:" msgstr "" -#: ../system/subscription/plan.rst:16 -msgid "Subscription" +#: ../system/integrations/smime/manage-certificates.rst:None +msgid "Zammad allowing to choose the default behavior on per group basis" msgstr "" -#: ../system/subscription/plan.rst:5 +#: ../system/integrations/smime/manage-certificates.rst:89 msgid "" -"On the top of the subscription summary you'll find the number of used and " -"available (booked) agent seats. By using the *see more* link you can also " -"expand an agent list to see the currently configured active agents. This " -"list *does not* count accounts with admin permissions only." +"Of course, agents can always manually change these settings on each email " +"they send out." msgstr "" -#: ../system/subscription/plan.rst:0 -msgid "" -"Within subscription you can always see how many agents are still\n" -"available to add and who uses the seats." +#: ../system/integrations/smime/prerequisites.rst:4 +msgid "A certificate *and* private key for your own organization" msgstr "" -#: ../system/subscription/plan.rst:14 +#: ../system/integrations/smime/prerequisites.rst:6 msgid "" -"Learn more on how to manage your agents in general :doc:`here `." +"(Use this to ✒️ **sign outgoing messages** and 🔓 **decrypt incoming " +"messages**.)" msgstr "" -#: ../system/subscription/plan.rst:19 +#: ../system/integrations/smime/prerequisites.rst:9 msgid "" -"This section gives you an overview of the available plans and their " -"functions / limits. If you require a more detailed table, check our " -"`detailed pricing table `_ for more." +"Certificates belonging your contacts, or their issuing certificate authority " +"(CA)" msgstr "" -#: ../system/subscription/plan.rst:23 +#: ../system/integrations/smime/prerequisites.rst:11 msgid "" -"Your selection in this step will decide on the base agent price and e.g. " -"agent limits that might apply in the summary step." +"(Use these to ✅ **verify incoming message signatures** and 🔒 **encrypt " +"outgoing messages**.)" msgstr "" -#: ../system/subscription/plan.rst:26 -msgid "" -"The green *Selected* button will also tell you what plan you're currently in." +#: ../system/integrations/smime/prerequisites.rst:14 +msgid "🙋 **I'm new to S/MIME. Where can I get a certificate?**" msgstr "" -#: ../system/subscription/plan.rst:30 +#: ../system/integrations/smime/prerequisites.rst:16 msgid "" -"Trial instances are running at Professional with 3 agents. The plan cannot " -"be changed during the trial for technical reasons, if you require more " -"agents for testing, please contact `our sales team `_ with a reason for the raise request." +"The easiest way to get certificates is to buy an annual subscription through " +"a commercial CA, such as:" msgstr "" -#: ../system/subscription/plan.rst:0 +#: ../system/integrations/smime/prerequisites.rst:19 msgid "" -"Screenshot showing three available packages for a hosted Zammad\n" -"instance" +"`Sectigo (formerly Comodo) `_" msgstr "" -#: ../system/subscription/plan.rst:83 -msgid "Summary" +#: ../system/integrations/smime/prerequisites.rst:20 +msgid "`Secorio `_" msgstr "" -#: ../system/subscription/plan.rst:41 -msgid "" -"In this section you can adjust the settings of the previous selected plan." +#: ../system/integrations/smime/prerequisites.rst:21 +msgid "`GlobalSign `_" msgstr "" -#: ../system/subscription/plan.rst:45 -msgid "" -"Note that upgrading (more agents, higher package) is always possible, " -"however, downgrading will only happen when your billing period renews." +#: ../system/integrations/smime/prerequisites.rst:23 +msgid "(Zammad is not affiliated with these CAs in any way.)" msgstr "" -#: ../system/subscription/plan.rst:49 +#: ../system/integrations/smime/prerequisites.rst:25 msgid "" -"Upgrading resets your billing period and existing credit will be deducted " -"from the new total." +"You can also generate your own self-signed certificates, but the process is " +"complicated and usually 🙅 **involves extra work for your contacts**." msgstr "" -#: ../system/subscription/plan.rst:58 -msgid "Billing cycle" +#: ../system/integrations/smime/prerequisites.rst:29 +msgid "" +"Bear in mind that 🤝 **S/MIME only works if the other party is using it, too." +"**" msgstr "" -#: ../system/subscription/plan.rst:53 -msgid "" -"You can choose between either monthly or yearly billing. The price per agent " -"will be cheaper if you decide for yearly billing." +#: ../system/integrations/smime/prerequisites.rst:32 +msgid "Certificate and Private Key Checks on Upload" msgstr "" -#: ../system/subscription/plan.rst:56 +#: ../system/integrations/smime/prerequisites.rst:34 msgid "" -"If you're still trying out things and are unsure of the right package for " -"your instance, you may want to choose monthly first and then upgrade to " -"yearly when you're sure." +"The certificate and public key validation is based on the ``X509v3`` " +"extensions." msgstr "" -#: ../system/subscription/plan.rst:66 -msgid "Plan: (Starter|Professional|Plus) - Agents" +#: ../system/integrations/smime/prerequisites.rst:49 +msgid "Uploading a *client certificate*?" msgstr "" -#: ../system/subscription/plan.rst:61 -msgid "Choose the number of agents you require for your instance." +#: ../system/integrations/smime/prerequisites.rst:41 +msgid "The following attributes are required then:" msgstr "" -#: ../system/subscription/plan.rst:63 -msgid "" -"Keep in mind that some packages may have agent limits. Depending on the " -"previous chosen package, you won't be able to exceed specific agent numbers. " -"Also note that setting less agents than currently configured is not possible." +#: ../system/integrations/smime/prerequisites.rst:39 +msgid "Subject Alternative Name (at least one email address has to be present)" msgstr "" -#: ../system/subscription/plan.rst:69 -msgid "Total" +#: ../system/integrations/smime/prerequisites.rst:40 +msgid "Key Usage (``Digital Signature`` and/or ``Key Encipherment``)" msgstr "" -#: ../system/subscription/plan.rst:69 -msgid "This will be the net total you're going to be billed." +#: ../system/integrations/smime/prerequisites.rst:41 +msgid "Public key algorithm (either ``RSA`` or ``EC``)" msgstr "" -#: ../system/subscription/plan.rst:71 +#: ../system/integrations/smime/prerequisites.rst:43 msgid "" -"By using the *Update subscription* button, the instance package will be " -"adjusted immediately. If you didn't provide a payment method yet, Zammad " -"will request you to provide one at this point." +"The Extended Key Usage attribute is optional. If the certificate provides " +"the named attribute, than it must contain the value ``E-mail Protection``." msgstr "" -#: ../system/subscription/plan.rst:77 +#: ../system/integrations/smime/prerequisites.rst:46 msgid "" -"In case you're still within the trial period, this means that the trial will " -"be over immediately!" +"Please note that any usable email adress has to be prefixed with ``email:`` " +"or ``rfc822:``." msgstr "" -#: ../system/subscription/plan.rst:80 -msgid "Down- or upgrading during the trial period *is not* possible." +#: ../system/integrations/smime/prerequisites.rst:49 +msgid "The named public key algorithms are mandatory for private keys as well." msgstr "" -#: ../system/subscription/plan.rst:0 -msgid "Screenshot showing payment options and a pricing summary" +#: ../system/integrations/smime/prerequisites.rst:54 +msgid "Uploading a *CA certificate*?" msgstr "" -#: ../system/subscription/plan.rst:99 -msgid "Payment method" +#: ../system/integrations/smime/prerequisites.rst:52 +msgid "" +"In the case of an uploaded CA certificate, providing the value ``CA:TRUE`` " +"in the attribute *Basic Contstraints*, the previously mentioned attributes " +"are not verified." msgstr "" -#: ../system/subscription/plan.rst:86 -msgid "You can pay via credit card or SEPA mandate." +#: ../system/integrations/smime/prerequisites.rst:56 +msgid "" +"In general, the usage of any expired (``Not After``) or not yet valid (``Not " +"Before``) certificate is denied for outgoing emails." msgstr "" -#: ../system/subscription/plan.rst:91 -msgid "Credit card" +#: ../system/integrations/smime/prerequisites.rst:59 +msgid "Example certificate:" msgstr "" -#: ../system/subscription/plan.rst:89 +#: ../system/integrations/smime/prerequisites.rst:85 msgid "" -"Simply follow the dialogue by clicking *authorize* and confirm -if required " -"by your bank- your consent to Zammad using your card for the payments." +"Please note that Zammad will distrust senders by default. This means that " +"you're always required to provide certificate data, no matter if for signing " +"or encrypting." msgstr "" -#: ../system/subscription/plan.rst:95 -msgid "SEPA" +#: ../system/integrations/smime/prerequisites.rst:89 +msgid "This is by design and can't be adjusted." msgstr "" -#: ../system/subscription/plan.rst:94 +#: ../system/integrations/smime/troubleshooting.rst:4 msgid "" -"Provide the requested information of the bank account holder and update if " -"you're ready. You'll then receive an email with the SEPA mandate." +"All of the system's latest S/MIME activity is displayed in the **Recent " +"Logs** section." msgstr "" -#: ../system/subscription/plan.rst:97 -msgid "" -"Technically there's also the possibility to pay via invoice, however - this " -"method only applies to a fairly low number of instances. Please contact `our " -"sales team `_ for more information." +#: ../system/integrations/smime/troubleshooting.rst:11 +msgid "Sample entries of in- and outgoing S/MIME related emails." msgstr "" -#: ../system/translations.rst:2 -msgid "Translations" +#: ../system/integrations/smime/troubleshooting.rst:11 +msgid "" +"Logs report the status and details of all mail, both incoming and outgoing, " +"that used signing/verification or encryption/decryption." msgstr "" -#: ../system/translations.rst:4 +#: ../system/integrations/smime/troubleshooting.rst:14 msgid "" -"Translations of Zammad are processed centrally in our `Weblate instance " -"`_. This allows non-developers to review " -"and update translation texts of the language they actually speak." +"This log does **not** include email sent by :doc:`triggers ` or the :doc:`scheduler `. For those, check your " +"``production.log``." msgstr "" -#: ../system/translations.rst:9 -msgid "" -"Your language is in an incomplete translation state or has typos? Please " -"consider helping us in sorting this out! All you need is either a GitHub " -"account or to register directly in our instance." +#: ../system/integrations/smime/troubleshooting.rst:20 +msgid "Common Issues" msgstr "" -#: ../system/translations.rst:13 -msgid "" -"Did you know? This is also where the documentation translations are handled. " -"🤓" +#: ../system/integrations/smime/troubleshooting.rst:30 +msgid "I received a signed/encrypted email before I set up S/MIME integration" msgstr "" -#: ../system/translations.rst:15 +#: ../system/integrations/smime/troubleshooting.rst:23 msgid "" -"Have a look in our :docs:`contribution section ` in the system documentation to get started!" +"No problem. Once S/MIME has been enabled and the appropriate certificates " +"have been added, agents will be prompted to retry verification/decryption on " +"matching emails." msgstr "" -#: ../system/translations.rst:20 -#, fuzzy -msgid "Local Translations" -msgstr "Bloquer les notifications" +#: ../system/integrations/smime/troubleshooting.rst:0 +msgid "Screenshot of user prompt to retry decryption" +msgstr "" -#: ../system/translations.rst:22 -msgid "" -"Apart from these system translations, there's still local translations you " -"can manage. This is relevant if you added custom objects that require " -"translations or even custom states and priorities." +#: ../system/integrations/smime/troubleshooting.rst:38 +msgid "The 🔒 **Encrypt** button is disabled" msgstr "" -#: ../system/translations.rst:None -msgid "Translation management screen within the admin menu" +#: ../system/integrations/smime/troubleshooting.rst:33 +msgid "Have you added the recipient's certificate?" msgstr "" -#: ../system/translations.rst:31 -msgid "Updating Translations" +#: ../system/integrations/smime/troubleshooting.rst:34 +msgid "Are you sure the recipient's certificate is valid?" msgstr "" -#: ../system/translations.rst:33 +#: ../system/integrations/smime/troubleshooting.rst:35 +msgid "Have you checked your ``production.log`` for more details?" +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:37 msgid "" -"Because of how Zammad ships translations, the only way to update the system " -"translations is to update your Zammad installation. The benefit of this is " -"that you no longer need internet access during a Zammad upgrade as the " -"package has everything it requires already." +"If encryption doesn't work in the composer, it won't work in :doc:`triggers " +"` or the :doc:`scheduler ` either!" msgstr "" -#: ../system/translations.rst:39 -msgid "Translation of Custom Objects" +#: ../system/integrations/smime/troubleshooting.rst:42 +msgid "The ✅ **Sign** button is disabled" msgstr "" -#: ../system/translations.rst:41 +#: ../system/integrations/smime/troubleshooting.rst:41 msgid "" -"No problem at all! You can customize any translation locally, even if it is " -"not initially provided by the system." +"Have you added **both the certificate and private key** for your " +"organization?" msgstr "" -#: ../system/translations.rst:44 +#: ../system/integrations/smime/troubleshooting.rst:42 msgid "" -"Translation is supported for a broad number of features, including but not " -"limited to custom:" +"Does the email address on the certificate match the email address of the " +"agent/group composing the email?" msgstr "" -#: ../system/translations.rst:47 -#, fuzzy -msgid "Object Attributes" -msgstr "Attributs d'un billet" - -#: ../system/translations.rst:48 -#, fuzzy -msgid "Ticket Macros" -msgstr "Billet > Étiquettes" - -#: ../system/translations.rst:49 -#, fuzzy -msgid "Ticket Overviews" -msgstr "Variables de billet" - -#: ../system/translations.rst:50 -#, fuzzy -msgid "Ticket Priorities" -msgstr "Billet > Priorité > Nom" - -#: ../system/translations.rst:51 -#, fuzzy -msgid "Ticket States" -msgstr "Billet > État > Nom" +#: ../system/integrations/smime/troubleshooting.rst:45 +msgid "Error: “Fingerprint already taken”" +msgstr "" -#: ../system/translations.rst:54 -msgid "Customizing Translations" +#: ../system/integrations/smime/troubleshooting.rst:45 +msgid "Are you sure you haven't added this certificate already?" msgstr "" -#: ../system/translations.rst:56 -msgid "" -"Within the translation screen, simply click on the **New Translation** " -"button." +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Error: “❌ invalid byte sequence in UTF-8”" msgstr "" -#: ../system/translations.rst:None -msgid "New translation dialog" +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Please ensure to provide PEM formatted certificate and keys." msgstr "" -#: ../system/translations.rst:62 -msgid "" -"In the dialog you can immediately enter the exact translation source (if you " -"know it) and your custom translation text for it and click **Submit**." +#: ../system/integrations/smime/troubleshooting.rst:49 +msgid "Did you check if the provided file is a valid certificate or key?" msgstr "" -#: ../system/translations.rst:65 -msgid "" -"Alternatively, try to search for translation suggestions in the list below. " -"Selecting an item from the list will pre-fill the translation source for you " -"and then you can just enter your custom translation." +#: ../system/integrations/zabbix.rst:2 +msgid "Zabbix Integration" msgstr "" -#: ../system/translations.rst:69 +#: ../system/integrations/zabbix.rst:5 msgid "" -"The target language will always default to your current language selection. " -"If you need to translate for a different language, simply change the " -"selection before submitting." +"This guide describes how to integrate your Zabbix 5.4 installation with " +"Zammad using the Zabbix webhook feature. This guide will provide " +"instructions on setting up a media type, a user and an action in Zabbix." msgstr "" -#: ../system/translations.rst:73 -msgid "" -"All your custom translations will show up in the overview table when added. " -"And they will even persist across Zammad updates!" +#: ../system/integrations/zabbix.rst:12 +msgid "Zammad with enabled HTTP Token Authentication" msgstr "" -#: ../system/translations.rst:76 -msgid "" -"Make sure to reload your browser if a translated string is not displayed." +#: ../system/integrations/zabbix.rst:13 +msgid "Zabbix version 5.4 or higher" msgstr "" -#: ../system/translations.rst:80 -msgid "Reverting to Original Translations" +#: ../system/integrations/zabbix.rst:16 +msgid "Setting up a Zammad" msgstr "" -#: ../system/translations.rst:82 -msgid "" -"If you want to revert a custom translation to original text, simply use the " -"appropriate action within the row of the overview table." +#: ../system/integrations/zabbix.rst:18 +msgid "Enable **API Token Access** in Settings > System > API." msgstr "" -#: ../system/translations.rst:85 +#: ../system/integrations/zabbix.rst:20 msgid "" -"Depending on the type of the translation source, the action has a slightly " -"different name:" +"Create a **new user** for a Zabbix alerter with an **email address** and " +"create a personal user token with **ticket.agent** permissions." msgstr "" -#: ../system/translations.rst:88 -msgid "**Reset** for customized system translations" -msgstr "" +#: ../system/integrations/zabbix.rst:24 +#, fuzzy +msgid "Zabbix Webhook Configuration" +msgstr "Bloquer les notifications" -#: ../system/translations.rst:89 -msgid "**Remove** for customized local translations" +#: ../system/integrations/zabbix.rst:27 +msgid "Create a Global Macro" msgstr "" -#: ../system/translations.rst:91 +#: ../system/integrations/zabbix.rst:29 msgid "" -"In both cases, the action will remove the customized translation after a " -"confirmation." +"Before setting up the **Webhook**, you need to setup the global macro " +"**{$ZABBIX.URL}**, which must contain the **URL** to the **Zabbix frontend**." msgstr "" -#: ../system/translations.rst:None -msgid "Screenshot showing the location of the Remove action" +#: ../system/integrations/zabbix.rst:33 +msgid "" +"In the **Administration** > **Media types** section, import the `Template`_." msgstr "" -#: ../system/translations.rst:99 -#, fuzzy -msgid "Inline Translations" -msgstr "Bloquer les notifications" +#: ../system/integrations/zabbix.rst:38 +msgid "Open the added **Zammad** media type and set:" +msgstr "" -#: ../system/translations.rst:101 -msgid "" -"If you prefer a more hands-on approach, you can activate the inline or on-" -"screen translation feature by pressing ``ctrl`` + ``alt`` + ``t`` at any " -"time and on any screen." +#: ../system/integrations/zabbix.rst:40 +msgid "**zammad\\_access\\_token** to the your **Personal User Token**" msgstr "" -#: ../system/translations.rst:105 +#: ../system/integrations/zabbix.rst:41 msgid "" -"All customizable translation texts will be highlighted for you on the " -"screen. Just click into the highlighted area and update the text in place." +"**zammad\\_url** to the **frontend URL** of your **Zammad** installation" msgstr "" -#: ../system/translations.rst:None -msgid "Inline translation mode activated for the Overview screen" +#: ../system/integrations/zabbix.rst:43 +msgid "**zammad\\_customer** to your **Zammad user email**." msgstr "" -#: ../system/translations.rst:112 +#: ../system/integrations/zabbix.rst:44 msgid "" -"When finished editing, simply press ``ctrl`` + ``alt`` + ``t`` again to " -"deactivate." +"**zammad\\_enable\\_tags** to **true** or **false** to enable or disable " +"trigger tags. **Important**: if you enable tag support, each tag is set with " +"a separate request." msgstr "" -#: ../system/translations.rst:117 +#: ../system/integrations/zabbix.rst:48 msgid "" -"Even though it's available on any screen, the inline translation feature " -"requires admin permissions. It works only for the current language " -"selection. If you need to translate a different language, first change the " -"language in your :user-docs:`profile settings `." +"If you want to prioritize issues according to **severity** values in Zabbix, " +"you can define mapping parameters:" msgstr "" -#: ../system/variables.rst:2 -msgid "Variables" +#: ../system/integrations/zabbix.rst:51 +msgid "**severity\\_**: Zammad priority ID" msgstr "" -#: ../system/variables.rst:4 -msgid "" -"Please note that this is just an overview of available variables. It might " -"be incomplete or variables might not be available within some functions. If " -"you're missing variables or are not sure if something is not working as " -"expected, feel free to ask over at the `Community `_." +#: ../system/integrations/zabbix.rst:53 +msgid "Click the **Update** button to save the **Webhook** settings." msgstr "" -#: ../system/variables.rst:10 +#: ../system/integrations/zabbix.rst:55 msgid "" -"Variables can be called by typing ``::`` (just like text modules in the " -"frontend), as long as you're in a supported text field within the backend. " -"Zammad will display all variables being available within this context and " -"replace it to the variable as soon as you selected an entry." +"To receive notifications in **Zammad**, you need to create a **Zabbix user** " +"and add **Media** with the **Zammad** type." msgstr "" -#: ../system/variables.rst:15 +#: ../system/integrations/zabbix.rst:58 msgid "" -"You have an empty field which you referenced and it appears as ``-``? That's " -"currently working as designed - you might want to ensure that these fields " -"always have a value." +"For **Send to**: enter any text, as this value is not used, but is required." msgstr "" -#: ../system/variables.rst:20 -msgid "Variable Categories" +#: ../system/integrations/zabbix.rst:61 +msgid "" +"For more information, use the `Zabbix documentation `_." msgstr "" -#: ../system/variables.rst:31 -msgid "Wait, What About Custom Objects?" +#: ../system/maintenance.rst:2 +msgid "Maintenance" msgstr "" -#: ../system/variables.rst:33 +#: ../system/maintenance.rst:4 msgid "" -"Good point! Of course, we can't predict what objects you might create, but " -"we can give you a hint on how to put the puzzle together to get your custom " -"values." +"Zammad comes with a maintenance mode that you can use for e.g. updating the " +"instance or changing settings while restricting availability and functions." msgstr "" -#: ../system/variables.rst:36 -msgid "" -"For this, we'll talk about the inner part of the variable (so everything " -"within ``#{}``), please put the outer part around to have a valid variable. " -"The first part of the variable name consist of the object type. Currently " -"these are:" +#: ../system/maintenance.rst:13 +msgid "Mode" msgstr "" -#: ../system/variables.rst:41 -msgid "Ticket (``ticket``)" +#: ../system/maintenance.rst:8 +#, fuzzy +msgid "The mode setting allows you to enable or disable the maintenance mode." msgstr "" +"Avec ce paramètre, vous pouvez décider (si) où insérer le numéro de billet." -#: ../system/variables.rst:42 -msgid "User (``user``)" +#: ../system/maintenance.rst:10 +msgid "Defaults to *off*." msgstr "" -#: ../system/variables.rst:43 -msgid "Organization (``organization``)" +#: ../system/maintenance.rst:12 +msgid "" +"The maintenance mode will restrict access to administrative roles only. This " +"means agents and customers are logged off." msgstr "" -#: ../system/variables.rst:44 -msgid "Group (``group``)" +#: ../system/maintenance.rst:23 +msgid "@Login" msgstr "" -#: ../system/variables.rst:46 +#: ../system/maintenance.rst:16 msgid "" -"The second part is the name of the object. This is the name you define " -"during object creation and can be found within the object menu at any time. " -"The first and second part of a variable is divided by a point, e.g.: " -"``ticket.number`` which will in total be ``#{ticket.number}``." +"This setting allows you to provide a login message within a green banner " +"above the login screen. Click into the green banner in the settings page to " +"adjust your message. To activate the message, activate the *@Login* setting." msgstr "" -#: ../system/variables.rst:51 +#: ../system/maintenance.rst:0 msgid "" -"Now, in some situations it's possible that you'll need to use a third part. " -"The best example for such a situation would be a ``select`` or ``tree-" -"select`` field which will by default return the key value, not it's display " -"name. For this, just extend your variable with ``.value``. This will result " -"in ``#{ticket.select.value}``." -msgstr "" - -#: ../system/variables.rst:60 -msgid "Using Translated Variables" +"Screenshot showing the default login message within the\n" +"settings page" msgstr "" -#: ../system/variables.rst:62 +#: ../system/maintenance.rst:26 msgid "" -"If you want to use a translated variable in triggers or schedulers, you can " -"extend the placeholder like this: ``#{t(ticket.state.name)}``. The ``t`` " -"tells Zammad to search for fitting translated strings. The used output " -"language is based on the system language of Zammad which you can set in the " -"admin panel under :doc:`/settings/branding` or based on the selected locale " -"in the trigger/scheduler edit dialog." +"Send an informative message to **all active sessions**. This comes handy to " +"inform your agents e.g. about mayor outages or to force reloads after " +"configuration changes." msgstr "" -#: ../system/variables.rst:69 -msgid "" -"A possible use-case: you want to send your customers updates on tickets via " -"trigger or scheduler which should include the state of the ticket. Using the " -"default ``#{ticket.state.name}`` (without the translation flag ``t()``) " -"would lead to the output of the original (english) name of the state." +#: ../system/maintenance.rst:31 +msgid "This is the messages title (slightly bigger than the normal message)." msgstr "" -#: ../system/variables.rst:75 -msgid "Date and Time Formatting" +#: ../system/maintenance.rst:34 +msgid "The text you want to provide to your logged in sessions." msgstr "" -#: ../system/variables.rst:77 -msgid "" -"The system (trigger/scheduler selected) locale and timezone predefines a " -"default format of date and timestamp. This format is customizable by using " -"the ``dt()`` method." +#: ../system/maintenance.rst:39 +msgid "Reload application" msgstr "" -#: ../system/variables.rst:79 -msgid "The method arguments are as follows:" +#: ../system/maintenance.rst:37 +msgid "" +"Selecting this option will change the message acceptance button from *Close* " +"(with nothing happening) to *Continue session*, which forces the application " +"to reload." msgstr "" -#: ../system/variables.rst:81 -msgid "The date or timestamp variable you want to format." +#: ../system/maintenance.rst:43 +msgid "" +"If you have customers that are logged in to Zammad, they'll also be notified " +"if they're active in that moment." msgstr "" -#: ../system/variables.rst:82 -msgid "The output format string." +#: ../system/maintenance.rst:48 +msgid "Example without reload application" msgstr "" -#: ../system/variables.rst:83 -msgid "The timezone to apply (optional)." +#: ../system/maintenance.rst:52 +msgid "" +"Message setting within Zammad's admin settings without ticket reload " +"application setting." msgstr "" -#: ../system/variables.rst:86 +#: ../system/maintenance.rst:0 msgid "" -"``#{dt(ticket.updated_at, \"%A %Y-%m-%d %H:%M in the office\", \"Europe/" -"Berlin\")}``" +"Screenshot showing the send message settings without ticket\n" +"reload application set" msgstr "" -#: ../system/variables.rst:87 -msgid "Monday, 2024-03-18 15:31 in the office" +#: ../system/maintenance.rst:61 ../system/maintenance.rst:85 +msgid "" +"The modal all other active sessions will see upon pressing *Send to clients*." msgstr "" -#: ../system/variables.rst:89 +#: ../system/maintenance.rst:0 msgid "" -"If you want to use our example, make sure to paste the string above without " -"formatting (``CTRL+Shift+v``), otherwise it won't work." +"Screenshot showing modal caused by maintenance's message\n" +"without reload application ticket" msgstr "" -#: ../system/variables.rst:93 -msgid "The following table lists available format directives:" +#: ../system/maintenance.rst:72 +msgid "Example with reload application" msgstr "" -#: ../system/variables.rst:99 -msgid "Parameter" +#: ../system/maintenance.rst:76 +msgid "" +"Message setting within Zammad's admin settings with ticket reload " +"application setting." msgstr "" -#: ../system/variables.rst:102 -msgid "``%Y``" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing the send message settings with ticket\n" +"reload application set" msgstr "" -#: ../system/variables.rst:103 -msgid "Year with 4 digits" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing modal caused by maintenance's message\n" +"with reload application ticket" msgstr "" -#: ../system/variables.rst:104 -msgid "Use ``%y`` for year with 2 digits" +#: ../system/monitoring.rst:2 +msgid "Monitoring" msgstr "" -#: ../system/variables.rst:105 -msgid "``%m``" +#: ../system/monitoring.rst:4 +msgid "" +"This function is only available in self hosted instances. If you use Zammad " +"in our cloud, we are monitoring the system on our own and take steps to fix " +"potential problems directly." msgstr "" -#: ../system/variables.rst:106 -msgid "Month of year (as number with zero-padding)" +#: ../system/monitoring.rst:11 +msgid "" +"On the monitoring page, you can see the current health state of Zammad under " +"\"*Current Status*\" at the bottom. This can be useful if you want to have a " +"look if everything is up and running. As an example, you could have a look " +"in the monitoring when you assume that some emails aren't processed from " +"Zammad." msgstr "" -#: ../system/variables.rst:107 -msgid "Use ``%-m`` for month without zero-padding" +#: ../system/monitoring.rst:17 +msgid "**Can't receive an email and the monitoring response is \"healthy\"?**" msgstr "" -#: ../system/variables.rst:108 -msgid "``%d``" +#: ../system/monitoring.rst:19 +msgid "" +"Zammad will just inform you about unprocessable emails. This is not the case " +"for oversized emails. You can adjust the maximum email size in :doc:`../" +"channels/email/settings`." msgstr "" -#: ../system/variables.rst:109 -msgid "Day of month (as number with zero-padding)" +#: ../system/monitoring.rst:24 +msgid "Monitoring API" msgstr "" -#: ../system/variables.rst:110 -msgid "Use ``%e`` for day without zero-padding" +#: ../system/monitoring.rst:26 +msgid "" +"Beside the indication in the monitoring page, you can also use an external " +"monitoring tool to monitor Zammad's health. To request the health of Zammad, " +"you need to provide the API key (token) to the external monitoring tool. You " +"can copy the token from the \"*Current Token*\" field as well as the whole " +"API endpoint of your system (\"*Health Check*\" field), in which the API " +"token is already included." msgstr "" -#: ../system/variables.rst:111 -msgid "``%H``" +#: ../system/monitoring.rst:37 +msgid "Screenshot showing Current Token and Health Check" msgstr "" -#: ../system/variables.rst:112 -msgid "Hour of day in 24h notation with zero-padding" +#: ../system/monitoring.rst:37 +msgid "Screenshot showing Token and Health Check" msgstr "" -#: ../system/variables.rst:113 -msgid "Use ``%k`` for hour without zero-padding" +#: ../system/monitoring.rst:39 +msgid "" +"In addition to that, you can reset the auto-generated token to make sure " +"that already configured monitoring systems won't work anymore. So, please " +"use this \"*Reset*\" button only if you know what you do!" msgstr "" -#: ../system/variables.rst:114 -msgid "``%I``" +#: ../system/monitoring.rst:44 +#, fuzzy +msgid "Example Output" +msgstr "Exemple" + +#: ../system/monitoring.rst:0 +msgid "No issues found" msgstr "" -#: ../system/variables.rst:115 -msgid "Hour of day in 12h notation with zero-padding" +#: ../system/monitoring.rst:48 ../system/monitoring.rst:60 +msgid "**Indicator in Zammad**:" msgstr "" -#: ../system/variables.rst:116 -msgid "" -"Use ``%l`` for hour without zero-padding and ``%p`` / ``%P`` for meridian " -"indicator" +#: ../system/monitoring.rst:0 +msgid "Screenshot showing monitoring with no issues" msgstr "" -#: ../system/variables.rst:117 -msgid "``%M``" +#: ../system/monitoring.rst:54 ../system/monitoring.rst:66 +msgid "**API response**::" msgstr "" -#: ../system/variables.rst:118 -msgid "Minute of hour" +#: ../system/monitoring.rst:0 +msgid "Issues were found" msgstr "" -#: ../system/variables.rst:120 -msgid "``%S``" +#: ../system/monitoring.rst:0 +msgid "Screenshot showing monitoring with issues" msgstr "" -#: ../system/variables.rst:121 -msgid "Second of Minute" +#: ../system/objects.rst:2 +msgid "Objects" msgstr "" -#: ../system/variables.rst:123 -msgid "``%A``" +#: ../system/objects.rst:4 +msgid "" +"In Zammad you can add your own fields to tickets, users, organizations and " +"even groups (these are called \"objects\"). This can be useful if you need " +"to add further information to a ticket or any other object in Zammad and the " +"information doesn't fit in any existing field." msgstr "" -#: ../system/variables.rst:124 -msgid "Weekday name" +#: ../system/objects.rst:11 +msgid "" +"Try to avoid deleting attributes (and disable them instead) as Zammad might " +"run into unexpected conditions if they are referenced somewhere." msgstr "" -#: ../system/variables.rst:125 -msgid "Use ``%a`` for abbreviated name or ``%^A`` for uppercase name" +#: ../system/objects.rst:16 +msgid "" +"Here's an overview of object attributes. On the upper right you can add new " +"attributes. By default, there will be no custom fields - standard attributes " +"will be grayed out, you can't delete or change those. You can edit custom " +"attributes (they are displayed in black font and have a trash bin on the " +"right side) just by clicking on them." msgstr "" -#: ../system/variables.rst:126 -msgid "``%B``" +#: ../system/objects.rst:24 +msgid "" +"Attributes you add to Zammad, no matter if they have default values or not, " +"will not update existing information. This means a new ticket field " +"technically will be empty unless you populate it." msgstr "" -#: ../system/variables.rst:127 -msgid "Month name" +#: ../system/objects.rst:28 +msgid "" +"Especially in ticket scope this also means that newly added attributes will " +"be indicated as \"changed\" to agents that view the ticket. This may " +"interfere with Zammad's tabs behavior." msgstr "" -#: ../system/variables.rst:128 -msgid "Use ``%b`` for abbreviated name" -msgstr "" +#: ../system/objects.rst:40 +#, fuzzy +msgid "Ordering Attributes" +msgstr "Attributs d'un billet" -#: ../system/variables.rst:129 -msgid "``%U``" +#: ../system/objects.rst:42 +msgid "" +"Since Zammad introduced :doc:`/system/core-workflows` the need to have a " +"custom positioning for attributes has become more important than ever." msgstr "" -#: ../system/variables.rst:130 -msgid "Week number of current year" +#: ../system/objects.rst:45 +msgid "" +"To adjust the position of such an attribute, simply click on the attribute " +"entry in question, scroll down and adjust the position number. Please note " +"that you cannot change the positioning of default attributes." msgstr "" -#: ../system/variables.rst:131 -msgid "Use ``%W`` for a different calculation method" +#: ../system/objects.rst:49 +msgid "" +"In case two attributes have the same position value, Zammad will sort " +"alphabetically by name automatically." msgstr "" -#: ../system/variables.rst:134 +#: ../system/objects.rst:None msgid "" -"We support the known format directives for the Ruby built-in method " -"``strftime`` of the ``DateTime`` class. For more information, see `here " -"`_." +"Screenshot showing custom attribute entries ordered in between default ones" msgstr "" -#: ../system/variables/article.rst:2 -msgid "Articles" +#: ../system/objects.rst:56 +msgid "Updating Database After Adding or Editing Attributes" msgstr "" -#: ../system/variables/article.rst:4 ../system/variables/config.rst:4 -#: ../system/variables/current-user.rst:4 ../system/variables/ticket.rst:4 +#: ../system/objects.rst:58 msgid "" -"If you're missing variables or are not sure if something is not working as " -"expected, feel free to ask over at the `Community `_." +"When adding or changing attributes, Zammad will not apply the changes " +"instantly, but instead shows you the changed attributes first. If you're " +"ready to go, just click on \"Update database\" to apply the changes to " +"Zammad. If you made a mistake or just want to discard your changes, click " +"\"Discard changes\"." msgstr "" -"Si vous manquez de variables ou n'êtes pas certain que quelque chose ne " -"fonctionne pas tel que prévu, n'hésitez pas à demander à la `Communauté " -"` _." -#: ../system/variables/article.rst:6 +#: ../system/objects.rst:64 msgid "" -"Below you can find all available ticket article-based variables within " -"Zammad. These can be called via Triggers for example. If you're unsure if " -"Zammad does support variables at the point you're at, you can try to type " -"``::`` to check." +"After applying the changes with \"Update Database\", a restart of Zammad is " +"**mandatory**. If you don't perform it, you may experience unexpected " +"behavior or even errors. You may want to do this kind of configuration " +"during maintenance windows." msgstr "" -#: ../system/variables/article.rst:9 ../system/variables/config.rst:9 -#: ../system/variables/ticket.rst:9 +#: ../system/objects.rst:72 msgid "" -"The below list gives you an example what kind of data you can expect, it's " -"not intended to explain the data itself." +"Changes on objects require you to update the database to apply these changes." msgstr "" -"La liste ci-dessous vous donne un exemple du type de données auquel vous " -"pouvez vous attendre; cependant, elle n'est pas destinée à expliquer les " -"données elles-mêmes." -#: ../system/variables/article.rst:11 -msgid "Article Variables" +#: ../system/objects.rst:75 +msgid "**🤓 Service restarts can be automated**" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "name" -msgstr "Nom" +#: ../system/objects.rst:0 +msgid "Hosted environments automatically restart for you." +msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "variable" -msgstr "Variable" +#: ../system/objects.rst:0 +msgid "" +"If you're using a self-hosted installation you can use :docs:`environment " +"variables `" +msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "example" -msgstr "Exemple" +#: ../system/objects.rst:82 +#, fuzzy +msgid "System Attributes" +msgstr "Attributs d'un billet" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Web" +#: ../system/objects.rst:84 +msgid "" +"Zammad comes with pre-configured attributes. Some of them can't be edited " +"via UI (or at all). This is required for proper operation of Zammad and not " +"a bug." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.web}``" +#: ../system/objects.rst:90 +#, fuzzy +msgid "Ticket State" +msgstr "Billet > État > Nom" + +#: ../system/objects.rst:92 +msgid "" +"If the pre-configured states aren't enough for you or you want to change " +"them, you can do so by clicking on the cogwheel icon in the state row in the " +"ticket tab. But you should be careful when changing pre-configured states. " +"This can lead to unwanted behavior in some cases." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``https://zammad.com`` or empty if not set in user object" +#: ../system/objects.rst:None +msgid "Screenshot showing highlighted ticket state attribute" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > VIP" +#: ../system/objects.rst:122 +msgid "Handling of states" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.vip}``" +#: ../system/objects.rst:102 +msgid "" +"In the state configuration screen, you can add new states, disable states or " +"change states." msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -msgid "``true`` or ``false``" +#: ../system/objects.rst:0 +msgid "Screenshot showing table of default ticket states" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Phone" +#: ../system/objects.rst:110 +msgid "" +"To add a new state, click on the \"New Ticket State\" button in the top " +"right corner. To change an existing state, simply click on the affected " +"state. This opens an edit dialog." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.phone}``" +#: ../system/objects.rst:114 +msgid "" +"You can also clone a state or set them to \"Default for new tickets\" or " +"\"Default for follow-ups\" by clicking on the ⁝ action button and select the " +"desired function." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``+4930123456789`` or empty if not set in user object" +#: ../system/objects.rst:118 +msgid "" +"*Default for new tickets* means that this state is used for every newly " +"created ticket." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Note" +#: ../system/objects.rst:121 +msgid "" +"*Default for follow-ups* means that this state is used if the ticket is re-" +"opened after it was closed." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.note}``" +#: ../system/objects.rst:171 +#, fuzzy +msgid "Ticket state in detail" +msgstr "Billet > État > Nom" + +#: ../system/objects.rst:125 +msgid "" +"Below you can find a description for each field and option. Please head over " +"to the :ref:`example ` to see the edit dialog." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Some note about user`` or empty if not set in user object" +#: ../system/objects.rst:129 +msgid "" +"This is the name of the state and what you and your agents are seeing when " +"choosing a state somewhere (e.g. in tickets, trigger configuration)." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Mobile" +#: ../system/objects.rst:137 +msgid "" +"There are different state types you can choose from. By default, Zammad " +"comes with one state per state type." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.mobile}``" +#: ../system/objects.rst:140 +msgid "" +"**new**: for states for tickets that are new and it hasn't been worked on " +"them" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Login" +#: ../system/objects.rst:142 +msgid "" +"**open**: for states for tickets that are in progress and agents are working " +"on them" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.login}``" +#: ../system/objects.rst:144 +msgid "**merged**: for states for tickets that are merged with other tickets" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -#: ../system/variables/ticket.rst:1 -msgid "``jdoe``" -msgstr "``jdoe``" +#: ../system/objects.rst:145 +msgid "" +"**pending reminder**: for states for tickets that are in progress and you " +"want to set a reminder. (default example: *pending reminder*)" +msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Lastname" +#: ../system/objects.rst:147 +msgid "" +"**pending action**: for states for tickets that are waiting for a specified " +"time and then change their state (default example: *pending close*)" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.lastname}``" +#: ../system/objects.rst:150 +msgid "" +"**closed**: for states for tickets that are finished and do not need to be " +"processed further" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -#: ../system/variables/ticket.rst:1 -msgid "``Doe`` or empty if not set" -msgstr "``Doe`` ou vide si non défini" +#: ../system/objects.rst:153 +msgid "" +"⚠️ Choosing the correct state type is important! If you are in doubt, have a " +"look on the default states and their types!" +msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Firstname" +#: ../system/objects.rst:158 +msgid "Ignore escalation" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.firstname}``" +#: ../system/objects.rst:157 +msgid "" +"Here you can define whether tickets of this state will count to escalation " +"time or not." msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "``Joe`` or empty if not set" -msgstr "``Joe`` ou vide si non défini" +#: ../system/objects.rst:161 +msgid "" +"You can create a note for the state to inform other admins about the state. " +"This has no effect on tickets." +msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Fax" +#: ../system/objects.rst:165 +msgid "Set the state to *active* or *inactive*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.fax}``" +#: ../system/objects.rst:167 +msgid "" +"it is technically possible to set all states to inactive. To keep Zammad " +"working in such a case, the inactive flag of one of the states is ignored." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Email" +#: ../system/objects.rst:194 +#, fuzzy +msgid "Ticket state example" +msgstr "Billet > État > Nom" + +#: ../system/objects.rst:174 +msgid "" +"Let's assume we want to create a new state which indicates that the ticket " +"has to wait for a response of a third party (e.g. service contractor or " +"manufacturer) and we want to to be able to set a reminder." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.email}``" +#: ../system/objects.rst:178 +msgid "" +"First we give the new state a proper name. In this example we call it " +"\"waiting for manufacturer\"." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``jdoe@example.com``" +#: ../system/objects.rst:181 +msgid "" +"As state type we choose \"pending reminder\". This indicates that the ticket " +"is still open and we can set a reminder. This reminder can be useful if our " +"manufacturer sometimes isn't responding or we want to remind him to give us " +"an answer." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Department" +#: ../system/objects.rst:186 +msgid "" +"We choose \"no\" for \"ignore escalation\" because we want to escalate the " +"tickets even if we are waiting on the manufacturer's feedback." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.department}``" -msgstr "" +#: ../system/objects.rst:189 +#, fuzzy +msgid "The **result** in the creation dialog will look like this:" +msgstr "Le résultat final ressemblera à ceci:" -#: ../system/variables/article.rst:1 -msgid "``Sales`` or empty if not set in user object" +#: ../system/objects.rst:0 +msgid "Screenshot showing ticket state creation dialog with example" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Address" -msgstr "" +#: ../system/objects.rst:199 +#, fuzzy +msgid "Ticket Priority" +msgstr "Billet > Priorité > Nom" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.address}``" +#: ../system/objects.rst:201 +msgid "" +"If the pre-configured priorities aren't enough for you or you want to change " +"them, you can do so by clicking on the cogwheel icon in the priority row in " +"the ticket tab:" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Some street 1, 12345 Berlin`` or empty if not set in user object" +#: ../system/objects.rst:None +msgid "Screenshot showing highlighted ticket priority attribute" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated" +#: ../system/objects.rst:226 +msgid "Handling of priorities" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_at}``" +#: ../system/objects.rst:210 +msgid "" +"In the priority configuration screen, you can add new priorities, disable " +"priorities or change priorities." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``2019-10-08 15:24:47 UTC``" +#: ../system/objects.rst:0 +msgid "Screenshot showing table of default ticket priorities" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Type > Name" +#: ../system/objects.rst:218 +msgid "" +"To add a new priority, click on the \"New Priority\" button in the top right " +"corner. To change an existing priority, simply click on the affected " +"priority. This opens an edit dialog." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.type.name}``" +#: ../system/objects.rst:222 +msgid "" +"You can also clone a priority or set them to \"Default for new tickets\" by " +"clicking on the ⁝ action button and select the desired function." msgstr "" -#: ../system/variables/article.rst:1 +#: ../system/objects.rst:225 msgid "" -"``email`` (`list of article types `_)" +"*Default for new tickets* means that this priority is used for every newly " +"created ticket." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > To" +#: ../system/objects.rst:248 +msgid "Priorities in detail" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.to}``" +#: ../system/objects.rst:229 +msgid "Below you can find a description for each field and option." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``helpdesk@example.com``" +#: ../system/objects.rst:232 +msgid "" +"This is the name of the priority and what you and your agents are seeing " +"when choosing a priority somewhere (e.g. in tickets, trigger configuration)." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > TicketID" +#: ../system/objects.rst:242 +msgid "Highlight color" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.ticket_id}``" +#: ../system/objects.rst:237 +msgid "" +"Switch between *Low priority* (light blue), *High priority* (red) and - " +"(default). This affects the displayed color for ticket titles in overviews." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``1`` (not ticket number)" +#: ../system/objects.rst:241 +msgid "The color options are currently limited to the mentioned options." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Subject" +#: ../system/objects.rst:245 +msgid "" +"You can create a note for the priority to inform other admins about the " +"priority. This has no effect on tickets." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.subject}``" +#: ../system/objects.rst:249 +msgid "Set the priority to *active* or *inactive*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``My amazing subject``" +#: ../system/objects/external-data-source-example.rst:2 +msgid "External Data Source" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Sender > Name" +#: ../system/objects/external-data-source-example.rst:4 +msgid "" +"We assume you already had a look on :doc:`types` where you can find a " +"description of the individual fields." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.sender.name}``" +#: ../system/objects/external-data-source-example.rst:7 +msgid "" +"To reproduce this example, choose a category you want to add a custom field, " +"click on *New Attribute* and select *External data source field* under " +"*Format*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Customer``, ``Agent`` or ``System``" +#: ../system/objects/external-data-source-example.rst:11 +msgid "" +"Our example story is to fetch data from an external product database. We " +"want to add our products to the tickets so that the products can be searched " +"and chosen from a list and also create a link to the product website." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Visibility" +#: ../system/objects/external-data-source-example.rst:16 +msgid "Base configuration" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.internal}``" +#: ../system/objects/external-data-source-example.rst:None +msgid "Initial steps to configure external data source object type" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``false`` or ``true`` (false if not internal)" +#: ../system/objects/external-data-source-example.rst:25 +msgid "Name: *product*" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > From" +#: ../system/objects/external-data-source-example.rst:26 +msgid "Display: *Product*" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.from}``" +#: ../system/objects/external-data-source-example.rst:29 +msgid "External data source configuration" msgstr "" -#: ../system/variables/article.rst:1 +#: ../system/objects/external-data-source-example.rst:31 msgid "" -"``Joe Doe `` may differ, depends on ``FROM`` of send mail" -msgstr "" - -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Web" +"First, enter the search URL making sure it contains ``#{search.term}`` as a " +"parameter:" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.web}``" +#: ../system/objects/external-data-source-example.rst:34 +msgid "**Example:** ``https://dummyjson.com/products/search?q=#{search.term}``" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > VIP" +#: ../system/objects/external-data-source-example.rst:36 +msgid "" +"After that, head down to the preview section and enter a search input for " +"the external data source." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.vip}``" -msgstr "" +#: ../system/objects/external-data-source-example.rst:39 +#, fuzzy +msgid "**Example:** ``mac``" +msgstr "Exemple" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Phone" +#: ../system/objects/external-data-source-example.rst:41 +msgid "Then you can find a preview of the response data below:" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.phone}``" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of JSON response based on search term" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Note" +#: ../system/objects/external-data-source-example.rst:48 +msgid "" +"We recommend using the preview to have a look on the structure. There is a " +"top-level element called ``products``. One level below, you can find the " +"attributes ``id`` and ``title``." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.note}``" +#: ../system/objects/external-data-source-example.rst:52 +msgid "**Search result response based on search from example:**" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Mobile" +#: ../system/objects/external-data-source-example.rst:119 +msgid "" +"To tell the remote system that the desired data is located below the " +"``products`` level, you have to put it in the field *Search result list key*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.mobile}``" +#: ../system/objects/external-data-source-example.rst:122 +msgid "" +"After inserting ``products`` in the mentioned field, you get an extended " +"preview. You can find an additional box *Search result list* with a JSON " +"structure. This is the same response as before but stripped from the upper " +"``products`` element by the external data source." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Login" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of JSON response search result list" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.login}``" +#: ../system/objects/external-data-source-example.rst:132 +msgid "" +"Now you need to provide the keys for the search result values and labels. As " +"already mentioned, we are looking for the ``id`` and the ``title`` of our " +"products. If you haven't already, it is now a good time to look at the " +"preview of the *Search result list*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Lastname" +#: ../system/objects/external-data-source-example.rst:197 +msgid "" +"After locating our two keys, we insert them in *search result value key* " +"(``id``) and in *Search result label key* (``title``)." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.lastname}``" +#: ../system/objects/external-data-source-example.rst:200 +msgid "" +"Basically, we configured the external data source already and we can see a " +"table in the preview section:" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Firstname" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of product table based on search term" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.firstname}``" +#: ../system/objects/external-data-source-example.rst:208 +msgid "" +"According to our example story, now just the *Link template* is missing." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Fax" +#: ../system/objects/external-data-source-example.rst:210 +msgid "" +"Please note that this is an optional feature. If you don't want to use such " +"links, of course you don't have to configure it." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.fax}``" +#: ../system/objects/external-data-source-example.rst:213 +msgid "" +"We can add now an address where additional product information can be found." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Email" +#: ../system/objects/external-data-source-example.rst:215 +msgid "Example: ``https://your_domain.com/q=#{ticket.product}``" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.email}``" +#: ../system/objects/external-data-source-example.rst:217 +msgid "In the example, the parameter means:" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Department" +#: ../system/objects/external-data-source-example.rst:219 +msgid "``#{}``: \"Frame\" for the insertion of information" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.department}``" +#: ../system/objects/external-data-source-example.rst:220 +msgid "``ticket``: object level, where you create your custom object" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Address" +#: ../system/objects/external-data-source-example.rst:221 +msgid "``product``: name of the (custom) object" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.address}``" +#: ../system/objects/external-data-source-example.rst:223 +msgid "" +"After configuring your *Link template*, there will be another column in the " +"preview. Hovering on the icons in the *Link* column will show you where it " +"forwards you." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created" +#: ../system/objects/external-data-source-example.rst:232 +msgid "" +"In our example, one of the links looks like: https://your_domain.com/q=6, " +"where the 6 is the product id." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_at}``" +#: ../system/objects/external-data-source-example.rst:235 +msgid "You can find more information regarding the URL in :doc:`types`." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Cc" +#: ../system/objects/includes/adding-values-hint.include.rst:3 +msgid "" +"Adding values can be tricky for first timers, don't forget to press \"➕ " +"Add\" after typing your values. Otherwise you may loose a value." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.cc}``" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:1 +#: ../system/objects/includes/reposition-values.include.rst:1 +msgid "**↕️ This field type allows the positioning of its values ↔️**" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``jdoe@example.com, company@example.com``" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:3 +msgid "" +"In order to re-arrange the field values, first edit the field. Then you can " +"use ☰ to drag the values in question to the correct position. If you want to " +"change the layer depth, double click on ☰. With it you can cycle through the " +"available layers." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Text" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:8 +msgid "When you're ready, submit your changes to save the object attribute." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.body}``" +#: :0 ../system/objects/types.rst:0 +msgid "" +"Screencast showing how to re-position values on tree select like\n" +"fields" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Test`` without formatting (plain)" +#: ../system/objects/includes/reposition-values.include.rst:3 +msgid "" +"In order to re-arrange the field values, edit the field and scroll below the " +"values. Make sure to tick the option \"Use custom option sort\"." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article Text as HTML (not referenced)" +#: ../system/objects/includes/reposition-values.include.rst:8 +msgid "" +"If you do not tick this field, all manual positioning you did above will be " +"lost upon saving! ☠️" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.body_as_html}``" +#: ../system/objects/includes/reposition-values.include.rst:11 +msgid "" +"Now use ☰ to drag the values in question to the correct position. When " +"you're ready, submit your changes to save the object attribute." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Test`` with formatting" +#: :0 ../system/objects/types.rst:0 +msgid "Screencast showing how to re-position values" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "Ticket > Article#" -msgstr "Billet > Article #:" +#: ../system/objects/includes/url-template-hint.include.rst:3 +msgid "" +"This field allows using :ref:`URL fields (Link Templates) `." +msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "``#{ticket.article_count}``" -msgstr "``#{ticket.article_count}``" +#: ../system/objects/permissions.rst:2 +#, fuzzy +msgid "Attribute Permissions" +msgstr "Attributs d'article" -#: ../system/variables/article.rst:1 -msgid "``1`` number of ticket articles" +#: ../system/objects/permissions.rst:7 +msgid "" +"In the object attributes configuration you can define if a field is shown " +"and if the input in the field is mandatory, separated by different screens " +"and for different :doc:`roles/permissions `." msgstr "" -#: ../system/variables/config.rst:2 -msgid "Config" +#: ../system/objects/permissions.rst:17 +msgid "Screenshot shows object attribute permission table" msgstr "" -#: ../system/variables/config.rst:6 +#: ../system/objects/permissions.rst:17 msgid "" -"Below you'll find config related variables. These hold useful configuration " -"information that you can use within e.g. triggers to show necessary " -"information to your customer." +"Some of the possible permissions and screen options for a user object " +"attribute." msgstr "" -#: ../system/variables/config.rst:11 -msgid "Config Variables" +#: ../system/objects/permissions.rst:19 +msgid "" +"Based on the object context (ticket, agent, organization, user), the " +"selectable roles (to be precise: the required permissions) and screens " +"differ. Be aware that these settings aren't affecting data creation via " +"other channels than the UI." msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Fully Qualified Domain Name" +#: ../system/objects/permissions.rst:24 +msgid "" +"If you want to have further customization possibilities, you should have a " +"look at the :doc:`core workflows `." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.fqdn}``" +#: ../system/objects/permissions.rst:28 +msgid "Screens" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``zammad.example.com``" +#: ../system/objects/permissions.rst:30 +msgid "" +"In the table below you can find an overview about the different permissions " +"and the available screens Zammad distinguishes between." msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Ticket Hook" +#: ../system/objects/permissions.rst:37 +msgid "Screen" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.ticket_hook}``" -msgstr "" +#: ../system/objects/permissions.rst:38 +#, fuzzy +msgid "Available for" +msgstr "Variable" -#: ../system/variables/config.rst:1 -msgid "``Ticket#``" +#: ../system/objects/permissions.rst:40 +msgid "create" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > HTTP type" +#: ../system/objects/permissions.rst:41 ../system/objects/permissions.rst:52 +#: ../system/objects/permissions.rst:59 ../system/objects/permissions.rst:73 +msgid "admin.user" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.http_type}``" -msgstr "" +#: ../system/objects/permissions.rst:42 ../system/objects/permissions.rst:53 +#: ../system/objects/permissions.rst:60 +#, fuzzy +msgid "admin.organization" +msgstr "Billet > Organisation > Note" -#: ../system/variables/config.rst:1 -msgid "``https`` or ``http``" +#: ../system/objects/permissions.rst:43 ../system/objects/permissions.rst:54 +#: ../system/objects/permissions.rst:61 +msgid "admin.group" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > SystemID" +#: ../system/objects/permissions.rst:44 +msgid "Creation dialog for not yet existing data" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.system_id}``" +#: ../system/objects/permissions.rst:45 +msgid "create_middle" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``31`` (value between 1 and 99)" -msgstr "" +#: ../system/objects/permissions.rst:46 ../system/objects/permissions.rst:50 +#: ../system/objects/permissions.rst:57 ../system/objects/permissions.rst:66 +#: ../system/objects/permissions.rst:70 +#, fuzzy +msgid "ticket.customer" +msgstr "L'agent sera défini comme client du billet." -#: ../system/variables/config.rst:1 -msgid "Config > Organization" +#: ../system/objects/permissions.rst:47 ../system/objects/permissions.rst:51 +#: ../system/objects/permissions.rst:58 ../system/objects/permissions.rst:69 +#, fuzzy +msgid "ticket.agent" +msgstr "Billet" + +#: ../system/objects/permissions.rst:48 +msgid "Ticket create dialog (middle section)" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.organization}``" +#: ../system/objects/permissions.rst:49 +msgid "edit" msgstr "" -#: ../system/variables/config.rst:1 -msgid "" -"``Zammad GmbH`` value set in `Branding `_" +#: ../system/objects/permissions.rst:55 +msgid "Editing dialog for already existing data" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Product Name" +#: ../system/objects/permissions.rst:56 +msgid "view" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.product_name}``" +#: ../system/objects/permissions.rst:62 +msgid "View-only dialog for already existing data" msgstr "" -#: ../system/variables/config.rst:1 -msgid "" -"``Helpdesk`` value set in `Branding `_" +#: ../system/objects/permissions.rst:64 +msgid "(e.g. user or organization from search)" msgstr "" -#: ../system/variables/current-user.rst:2 -msgid "Current User" +#: ../system/objects/permissions.rst:65 +msgid "signup" msgstr "" -#: ../system/variables/current-user.rst:6 -msgid "" -"Current user variables always return values of the current user that caused " -"e.g. a trigger to run." +#: ../system/objects/permissions.rst:67 +msgid "Sign-up screen for new customers" msgstr "" -#: ../system/variables/current-user.rst:8 -msgid "" -"Due to the above fact, these variables are often not (yet) set or available " -"for usage." +#: ../system/objects/permissions.rst:68 +msgid "invite_customer" msgstr "" -#: ../system/variables/current-user.rst:10 +#: ../system/objects/permissions.rst:71 msgid "" -"In situations where e.g. schedulers or triggers run, this most likely is " -"nothing you want to use." +"Customer invitation screen (from :doc:`First Steps ` area)" msgstr "" -#: ../system/variables/current-user.rst:13 -msgid "Current User Variables" +#: ../system/objects/permissions.rst:72 +msgid "invite_agent" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Web" +#: ../system/objects/permissions.rst:74 +msgid "" +"Agent invitation screen (from :doc:`First Steps ` area)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.web}``" +#: ../system/objects/permissions.rst:78 +msgid "Screen Options" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``https://zammad.org`` or empty if not set" -msgstr "``https://zammad.org`` ou vide si non défini" +#: ../system/objects/permissions.rst:80 +msgid "" +"For the different screens you can select \"show\" and \"required\" options." +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > VIP" +#: ../system/objects/permissions.rst:82 +msgid "**shown:** Show (check) or hide (uncheck) a field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.vip}``" +#: ../system/objects/permissions.rst:83 +msgid "" +"**required:** Set a field to mandatory (check). Forces users (via UI and " +"API) to populate the field." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``false`` or ``true``" -msgstr "``false`` ou ``true``" +#: ../system/objects/types.rst:7 +#, fuzzy +msgid "Example external data source" +msgstr "Réglages avancés" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Web" -msgstr "" +#: ../system/objects/types.rst:2 +#, fuzzy +msgid "Attribute types" +msgstr "Attributs d'article" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.web}``" +#: ../system/objects/types.rst:4 +msgid "" +"When adding a new object attribute, you can choose between the following " +"attribute types." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > VIP" +#: ../system/objects/types.rst:14 +msgid "" +"You cannot change the attribute format / type as soon as it is applied. If " +"you no longer need an object attribute, consider disabling it instead of " +"removing." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.vip}``" +#: ../system/objects/types.rst:18 +msgid "**What about the translation of my attributes?**" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Phone" +#: ../system/objects/types.rst:20 +msgid "" +"For some attribute types you can decide if they should be translatable or " +"not. To be precise, it works only for the selectable fields because the " +"possible choices are known and limited. For the following attribute types, " +"you can set the translatable flag:" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.phone}``" +#: ../system/objects/types.rst:25 +msgid "*Boolean field*" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``004930123456789`` or empty if not set" -msgstr "``004930123456789`` ou vide si non défini" - -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Note" -msgstr "" +#: ../system/objects/types.rst:26 +#, fuzzy +msgid "*Single selection field*" +msgstr "Réglages avancés" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.note}``" -msgstr "" +#: ../system/objects/types.rst:27 +#, fuzzy +msgid "*Multiple selection field*" +msgstr "Réglages avancés" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Some note to this user`` or empty if not set" -msgstr "``Quelques notes à cet utilisateur` ou vide si non défini" +#: ../system/objects/types.rst:28 +#, fuzzy +msgid "*Single tree selection field*" +msgstr "Réglages avancés" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Mobile" -msgstr "" +#: ../system/objects/types.rst:29 +#, fuzzy +msgid "*Multiple tree selection field*" +msgstr "Réglages avancés" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.mobile}``" +#: ../system/objects/types.rst:31 +msgid "" +"For these types, you can find an additional field *Translate field contents*:" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``0049176123456789`` or empty if not set" -msgstr "``0049176123456789`` ou vide si non défini" - -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Login" +#: ../system/objects/types.rst:0 +msgid "Screenshot showing translatable attribute types" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.login}``" +#: ../system/objects/types.rst:38 +msgid "Screenshot with example of translatable attribute type" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Lastname" +#: ../system/objects/types.rst:45 +msgid "Boolean field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.lastname}``" +#: ../system/objects/types.rst:41 +msgid "" +"Provides a drop-down field with display values for ``true`` and ``false``. " +"Setting a default is mandatory." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Firstname" +#: ../system/objects/types.rst:0 +msgid "Available settings for Boolean fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.firstname}``" +#: ../system/objects/types.rst:55 +msgid "Date field" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``John`` or empty if not set" -msgstr "``John`` ou vide si non défini" - -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Fax" +#: ../system/objects/types.rst:48 +msgid "Provides a date picker field and does not allow default values." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.fax}``" +#: ../system/objects/types.rst:52 +msgid "Default time diff (hours)" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``004930123464789`` or empty if not set" -msgstr "``004930123464789`` ou vide si non défini" - -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Email" +#: ../system/objects/types.rst:51 +msgid "" +"This setting helps the user by highlighting the day from now plus the " +"provided value. It *does not* pre-fill the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.email}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Date fields" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``jdoe@customer.tld``" -msgstr "``jdoe@customer.tld``" - -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Department" +#: ../system/objects/types.rst:73 +msgid "Date & time field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.department}``" +#: ../system/objects/types.rst:58 +msgid "Provides a date and time picker – does not allow default values" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Sales`` or empty if not set" -msgstr "``Ventes`` ou vide si non défini" - -#: ../system/variables/current-user.rst:1 -#, fuzzy -msgid "Current User > Updated by > Avatar" -msgstr "Billet > mis à jour par > Nom de famille" - -#: ../system/variables/current-user.rst:1 -#, fuzzy -msgid "``#{user.updated_by.avatar(60,60)}``" -msgstr "``#{ticket.updated_by.lastname}``" - -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "avatar picture with width and height in pixel (e.g. 60,60)" +#: ../system/objects/types.rst:62 +msgid "Allow future" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Address" +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the future." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.address}``" +#: ../system/objects/types.rst:66 +msgid "Allow past" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Some street 1, 12345 Berlin`` or empty if not set" -msgstr "``12345, rue des Cadeaux, Pôle Nord HoH oHo`` ou vide si non défini" +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the past." +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated at" +#: ../system/objects/types.rst:70 +msgid "Default time diff (minutes)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_at}``" +#: ../system/objects/types.rst:69 +msgid "" +"This setting helps the user by highlighting the day from now plus the " +"provided value. It does not pre-fill the field." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC``" -msgstr "``2019-10-07 16:25:00 UTC``" +#: ../system/objects/types.rst:0 +#, fuzzy +msgid "Available settings for Date & time fields" +msgstr "Réglages avancés" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Phone" +#: ../system/objects/types.rst:86 +msgid "Integer field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.phone}``" +#: ../system/objects/types.rst:76 +msgid "" +"Provides an input field that allows integer usage only. You may define a " +"default value. You cannot enforce comma separation." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Shared organization" +#: ../system/objects/types.rst:80 +msgid "Minimal" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.shared}``" +#: ../system/objects/types.rst:80 +msgid "The minimal value the field accepts." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Note" +#: ../system/objects/types.rst:83 +msgid "Maximal" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.note}``" +#: ../system/objects/types.rst:83 +msgid "The maximum value the field accepts." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``A note to the organization of the user`` or empty if not set" -msgstr "``Une note à l'organisation de l'utilisateur` ou vide si non défini" - -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Name" +#: ../system/objects/types.rst:0 +msgid "Available settings for Integer fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.name}``" +#: ../system/objects/types.rst:99 +msgid "Multiple selection field" msgstr "" -#: ../system/variables/current-user.rst:1 -#, fuzzy -msgid "``Zammad GmbH``" -msgstr "``Zammad GmbH`` ou vide si non défini" - -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Domain based assignment" +#: ../system/objects/types.rst:89 +msgid "" +"Provides a selection field that allows the selection of one or more out of " +"several. This field does allow setting a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.domain_assignment}``" -msgstr "" +#: ../system/objects/types.rst:0 +#, fuzzy +msgid "Available settings for Multiple selection fields" +msgstr "Réglages avancés" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Domain" +#: ../system/objects/types.rst:112 +msgid "Single selection field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.domain}``" +#: ../system/objects/types.rst:102 +msgid "" +"Provides a drop-down field that allows selection of one value out of " +"several. This field does allow setting a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -#, fuzzy -msgid "``zammad.com`` or empty if not set" -msgstr "``https://zammad.com`` ou vide si non défini" - -#: ../system/variables/current-user.rst:1 -#, fuzzy -msgid "Current User > Organization > VIP" -msgstr "Billet > Organisation > Note" - -#: ../system/variables/current-user.rst:1 +#: ../system/objects/types.rst:0 #, fuzzy -msgid "``#{user.organization.vip}``" -msgstr "``#{ticket.organization.domain}``" +msgid "Available settings for Single selection fields" +msgstr "Réglages avancés" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Note" +#: ../system/objects/types.rst:142 +msgid "Textarea field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.note}``" +#: ../system/objects/types.rst:115 +msgid "" +"Provides a text area input field (multiple lines) and thus allows e.g. new " +"lines. You can set a default field value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Mobile" +#: ../system/objects/types.rst:120 +msgid "" +"Please note that this field *does not* support text formatting or HTML " +"content (rich text)." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.mobile}``" +#: ../system/objects/types.rst:123 +msgid "**🥵 This field can consume a lot of visual space**" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Login" +#: ../system/objects/types.rst:125 +msgid "" +"Depending on where you use this field type, it may use a lot of visual space " +"if you provide a lot of text. This may be an issue to work with." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.login}``" +#: ../system/objects/types.rst:130 +msgid "Default" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Lastname" +#: ../system/objects/types.rst:129 +msgid "" +"The here provided text will be shown within the text area field or new data " +"sets." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.lastname}``" +#: ../system/objects/types.rst:134 ../system/objects/types.rst:160 +msgid "Maxlength" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Firstname" +#: ../system/objects/types.rst:0 ../system/objects/types.rst:160 +msgid "You can pick the maximum length of the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.firstname}``" +#: ../system/objects/types.rst:0 +msgid "The default length of this object is ``500``." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Fax" +#: ../system/objects/types.rst:139 +msgid "Rows" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.fax}``" +#: ../system/objects/types.rst:0 +msgid "" +"Change the number of rows to dislay so that you can use only the space you " +"really need." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Email" +#: ../system/objects/types.rst:0 +msgid "The default number of rows is ``4``." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.email}``" +#: ../system/objects/types.rst:0 +#, fuzzy +msgid "Available settings for Textarea fields" +msgstr "Réglages avancés" + +#: ../system/objects/types.rst:165 +msgid "Text field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Department" +#: ../system/objects/types.rst:145 +msgid "Provides a text field (one line) and allows choosing a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.department}``" +#: ../system/objects/types.rst:148 +msgid "" +"Defines the type of the input field. This allows e.g. your browser to ensure " +"that you provide the specific type." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Web" +#: ../system/objects/types.rst:152 +msgid "Currently available:" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.web}``" +#: ../system/objects/types.rst:155 +msgid "Phone" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > VIP" +#: ../system/objects/types.rst:156 +msgid "Text" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.vip}``" +#: ../system/objects/types.rst:157 +msgid "Url *(URL fields disable link-template availability)*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Phone" +#: ../system/objects/types.rst:0 +msgid "Available settings for Text fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.phone}``" +#: ../system/objects/types.rst:174 +msgid "Single tree selection field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Note" +#: ../system/objects/types.rst:168 +msgid "" +"Provides a select-like field with up to 6 layers of options. Does not allow " +"setting a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.note}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Tree Select fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Mobile" +#: ../system/objects/types.rst:183 +msgid "Multiple tree selection field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.mobile}``" +#: ../system/objects/types.rst:177 +msgid "" +"Provides a select-like field with up to 6 layers of options allowing the " +"selection of multiple values. Does not allow setting a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Login" +#: ../system/objects/types.rst:302 +msgid "External Data Source field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.login}``" +#: ../system/objects/types.rst:186 +msgid "" +"Provides a searchable field which fetches data from an external system. This " +"can be useful if you have data outside of Zammad and don't want to maintain " +"both data sources." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Lastname" +#: ../system/objects/types.rst:190 +msgid "The feature works as follows:" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.lastname}``" +#: ../system/objects/types.rst:192 +msgid "" +"Zammad sends a query with a search string (free text from agent or based on " +"a variable) in a pre-defined format (\"Search URL\") to an external system." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Firstname" +#: ../system/objects/types.rst:195 +msgid "" +"This external system searches for matches and provides a response as a JSON " +"structure to Zammad." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.firstname}``" +#: ../system/objects/types.rst:197 +msgid "" +"Zammad just looks for the defined list and value keys, reads the content and " +"displays the value to the user. There is no search on Zammad side." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Fax" +#: ../system/objects/types.rst:201 +msgid "" +"The usage of a PostgreSQL database for Zammad is required. In any other " +"case, Zammad will hide the external data source type and you are not able to " +"use it. If you want to use this feature, consider to :docs:`migrate your " +"database `." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.fax}``" +#: ../system/objects/types.rst:205 +msgid "Currently, only ``GET`` is supported as request method." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Email" +#: ../system/objects/types.rst:206 +msgid "" +"The data structure must be in JSON format and provide the objects in an " +"array." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.email}``" +#: ../system/objects/types.rst:208 +msgid "" +"The endpoint for the external data source has to support search. On Zammad " +"side, there is no search/logic implemented; however, you can define the " +"output key and value based on the result(s) from the response (which " +"provides already filtered content based on the search)." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Department" +#: ../system/objects/types.rst:212 +msgid "" +"If you receive more results as expected, your external data source search " +"may not work properly or the structure of the URL is not correct. You should " +"get in touch with a responsible person from the external system." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.department}``" +#: ../system/objects/types.rst:217 +msgid "" +"Please have a look :doc:`at our example `, where you can find a possible configuration for a public " +"dummy endpoint." msgstr "" -#: ../system/variables/current-user.rst:1 +#: ../system/objects/types.rst:0 #, fuzzy -msgid "Current User > Created by > Avatar" -msgstr "Billet > Créé par > Nom de famille" +msgid "Available settings for external data source fields" +msgstr "Réglages avancés" -#: ../system/variables/current-user.rst:1 -#, fuzzy -msgid "``#{user.created_by.avatar(60,60)}``" -msgstr "``#{ticket.created_by.lastname}``" +#: ../system/objects/types.rst:242 +msgid "Search URL" +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Address" +#: ../system/objects/types.rst:227 +msgid "" +"Set your endpoint where Zammad fetches the data. Please make sure to include " +"a valid search :doc:`variable ` as an URL parameter. " +"Example for a free text search at user input: ``#{search.term}``" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.address}``" +#: ../system/objects/types.rst:232 +msgid "" +"If in doubt, ask the responsible person for the external data source how " +"they expect the structure of the URL." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created at" +#: ../system/objects/types.rst:236 +msgid "" +"Depending on your search variable, the preview might work or not. The reason " +"is that the context might not be available and it is no bug." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_at}``" +#: ../system/objects/types.rst:239 +msgid "" +"Please also make sure to use a variable which is available in your object " +"context. For example you won't be able to search for a ticket in a user " +"object context." msgstr "" -#: ../system/variables/current-user.rst:1 +#: ../system/objects/types.rst:252 #, fuzzy -msgid "Current User > Avatar" -msgstr "Billet > Organisation > Note" +msgid "SSL Verification" +msgstr "Bloquer les notifications" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.avatar(60,60)}``" +#: ../system/objects/types.rst:245 +msgid "Here you can switch the SSL verification to no." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Address" +#: ../system/objects/types.rst:249 +msgid "" +"If your external data source system is using self signed certificates, " +"please have a look :doc:`here ` for " +"further information about how to handle them in Zammad, so you can keep the " +"SSL verification activated." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.address}``" +#: ../system/objects/types.rst:258 +msgid "HTTP Authentication" msgstr "" -#: ../system/variables/ticket.rst:6 +#: ../system/objects/types.rst:255 msgid "" -"Below you can find all available ticket-based variables within Zammad. These " -"can be called via Triggers for example. If you're unsure if Zammad does " -"support variables at the point you're at, you can try to type ``::`` to " -"check." +"If your external data source requires an authentication, you can set it " +"here. You can leave it empty or choose between *Basic Authentication* or " +"*Authentication Token* (selecting one of the two methods leads to additional " +"fields where you can enter your credentials/token)." msgstr "" -"Vous trouverez ci-dessous toutes les variables, disponibles dans Zammad, " -"basées sur les billets. Par exemple, celles-ci peuvent être appelées via des " -"déclencheurs. Si vous ne savez pas si Zammad prend en charge une certaine " -"variable, vous pouvez essayer de taper ``::`` pour vérifier." - -#: ../system/variables/ticket.rst:12 -msgid "Ticket Variables" -msgstr "Variables de billet" - -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Web" -msgstr "Billet > mis à jour par > Web" - -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.web}``" -msgstr "``#{ticket.updated_by.web}``" - -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > VIP" -msgstr "Billet > mis à jour par > VIP" - -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.vip}``" -msgstr "``#{ticket.updated_by.vip}``" - -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Phone" -msgstr "Billet > mis à jour par > Téléphone" - -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.phone}``" -msgstr "``#{ticket.updated_by.phone}``" - -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Note" -msgstr "Billet > mis à jour par > Note" - -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.note}``" -msgstr "``#{ticket.updated_by.note}``" - -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Mobile" -msgstr "Billet > mis à jour par > Mobile" - -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.mobile}``" -msgstr "``#{ticket.updated_by.mobile}``" - -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Login" -msgstr "Billet > mis à jour par > Login" - -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.login}``" -msgstr "``#{ticket.updated_by.login}``" - -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Lastname" -msgstr "Billet > mis à jour par > Nom de famille" - -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.lastname}``" -msgstr "``#{ticket.updated_by.lastname}``" - -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Firstname" -msgstr "Billet > mis à jour par > Prénom" - -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.firstname}``" -msgstr "``#{ticket.updated_by.firstname}``" - -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Fax" -msgstr "Billet > mis à jour par > Télécopieur" - -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.fax}``" -msgstr "``#{ticket.updated_by.fax}``" - -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Email" -msgstr "Billet > mis à jour par > Courriel" - -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.email}``" -msgstr "``#{ticket.updated_by.email}``" - -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Department" -msgstr "Billet > mis à jour par > Département" - -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.department}``" -msgstr "``#{ticket.updated_by.department}``" - -#: ../system/variables/ticket.rst:1 -#, fuzzy -msgid "Ticket > Updated by > Avatar" -msgstr "Billet > mis à jour par > Télécopieur" - -#: ../system/variables/ticket.rst:1 -#, fuzzy -msgid "``#{ticket.updated_by.avatar(60,60)}``" -msgstr "``#{ticket.updated_by.lastname}``" - -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Address" -msgstr "Billet > mis à jour par > Adresse" - -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.address}``" -msgstr "``#{ticket.updated_by.address}``" - -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated at" -msgstr "Billet > mis à jour à:" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_at}``" -msgstr "``#{ticket.updated_at}``" +#: ../system/objects/types.rst:265 +msgid "Search result list key" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Title" -msgstr "Billet > Titre" +#: ../system/objects/types.rst:261 +msgid "" +"Defines the level in the JSON structure which provides the list with search " +"results. You can leave it empty, if the data is already provided as an " +"array. If you have to go deeper in the structure, you can provide a path " +"with ``.`` as separators, e.g. ``key.subkey.sub-sub-key``." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.title}``" -msgstr "``#{ticket.title}``" +#: ../system/objects/types.rst:271 +msgid "Search result value key" +msgstr "" -#: ../system/variables/ticket.rst:1 +#: ../system/objects/types.rst:268 msgid "" -"``My amazing Subject`` (normally subject, can be edited within Interface and " -"thus differ)" +"Defines the attribute in the structure in which your external data source " +"provides the *value* for your data. An example would be a product *number*. " +"If you have to go deeper in the structure, you can provide a path with ``.`` " +"as separators, e.g. ``key.subkey.sub-sub-key``." msgstr "" -"``Mon incroyable sujet`` (normalement le sujet peut être modifié dans " -"l'interface et donc être différent)" - -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Accounted Time" -msgstr "Billet > Temps comptabilisé" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.time_unit}``" -msgstr "``#{ticket.time_unit}``" +#: ../system/objects/types.rst:277 +msgid "Search result label key" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``1``, ``2.75`` or empty response" -msgstr "``1``, ``2.75`` ou vide si non défini" +#: ../system/objects/types.rst:274 +msgid "" +"Defines the attribute in the structure in which your external data source " +"provides the *label* for your data. An example would be a product *name*. If " +"you have to go deeper in the structure, you can provide a path with ``.`` as " +"separators, e.g. ``key.subkey.sub-sub-key``." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Tags" -msgstr "Billet > Étiquettes" +#: ../system/objects/types.rst:280 +msgid "" +"In the preview area, you can find the following items (depending on your " +"configuration above):" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.tags}``" -msgstr "``#{ticket.tags}``" +#: ../system/objects/types.rst:283 +msgid "" +"**Error/hint message** (only if configuration is not complete): Zammad tells " +"you, if there is a problem and what you should change in your configuration." +msgstr "" -#: ../system/variables/ticket.rst:1 +#: ../system/objects/types.rst:286 msgid "" -"Currently not available, see `Issue 2769 `_" +"**Search field**: search for an existing attribute in the data source to get " +"a preview. This is required for the fields below to show up." msgstr "" -"Actuellement non disponible, voir `Issue 2769 `_" - -#: ../system/variables/ticket.rst:1 -msgid "Ticket > State > Name" -msgstr "Billet > État > Nom" - -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.state.name}``" -msgstr "``#{ticket.state.name}``" - -#: ../system/variables/ticket.rst:1 -msgid "``new``, ``open``, ..." -msgstr "``new``, ``open``, ..." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Priority > Name" -msgstr "Billet > Priorité > Nom" - -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.priority.name}``" -msgstr "``#{ticket.priority.name}``" +#: ../system/objects/types.rst:288 +msgid "" +"**Search result response** (only if configuration is not complete): here you " +"can find a syntax highlighted JSON preview of the response, based on the " +"search term you entered." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2 normal``" -msgstr "``2 normal``" +#: ../system/objects/types.rst:291 +msgid "" +"**Search result list** (only if *search result list key* is properly set): " +"output of the structure under the configured *search result list key*." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Pending till" -msgstr "Billet > En attente jusqu'à" +#: ../system/objects/types.rst:294 +msgid "" +"**Preview table** (when fully configured): Zammad shows you a table which " +"includes the found items based on the search string (value, label and " +"optional link). You can use this preview if you don't have the complete data " +"structure of the external system in mind." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.pending_time}``" -msgstr "``#{ticket.pending_time}``" +#: ../system/objects/types.rst:299 +msgid "" +"An example of a configured external data source field from agent perspective:" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not set" -msgstr "``2019-10-07 16:25:00 UTC`` ou vide si non défini" +#: ../system/objects/types.rst:0 +msgid "Screencast showing the search for a product in a ticket" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Web" -msgstr "Billet > Propriétaire > Web" +#: ../system/objects/types.rst:307 +msgid "URL fields (Link-Template)" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.web}``" -msgstr "``#{ticket.owner.web}``" +#: ../system/objects/types.rst:311 +msgid "" +"This function is restricted to Text, Select and External data source types " +"only." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``https://zammad.com`` or empty if not set" -msgstr "``https://zammad.com`` ou vide si non défini" +#: ../system/objects/types.rst:314 +msgid "" +"Link-Templates are an amazing way to dynamically generate URLs. They allow " +"you to integrate other systems better without having to manually copy data " +"from Zammad if possible." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > VIP" -msgstr "Billet > Propriétaire > VIP" +#: ../system/objects/types.rst:320 +msgid "" +"Another great way of communicating with another system may be Zammad's :doc:" +"`Webhooks `." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.vip}``" -msgstr "``#{ticket.owner.vip}``" +#: ../system/objects/types.rst:323 +msgid "" +"After filling a link-template enabled field, an URL icon will appear on its " +"right. Clicking on the icon opens a new tab." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Phone" -msgstr "Billet > Propriétaire > Téléphone" +#: ../system/objects/types.rst:328 +msgid "" +"Even though Zammad displays the link template within object edit and create " +"screens, the function is optional. It's only active if you populate the " +"field." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.phone}``" -msgstr "``#{ticket.owner.phone}``" +#: ../system/objects/types.rst:333 +msgid "" +"What's the difference between URL and text fields with link template...?!" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Note" -msgstr "Billet > Propriétaire > Note" +#: ../system/objects/types.rst:335 +msgid "" +"Both fields have different use cases. Use ``text`` type text fields when " +"ever you have a *static* url that requires dynamic parameters. If you " +"require a drag & drop like field that you can put in any URL, use ``URL`` " +"type text fields." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.note}``" -msgstr "``#{ticket.owner.note}``" +#: ../system/objects/types.rst:340 +msgid "" +"The difference is easier to spot when comparing the fields directly, below " +"screencast shows the result - the dynamic approach uses existing values in " +"the moment of updating to built the URL - e.g. ``https://google.com/search?" +"q=cookies`` - while the URL approach uses the actual URL of the field - e.g. " +"``https://zammad.com``." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Mobile" -msgstr "Billet > Propriétaire > Mobile" +#: ../system/objects/types.rst:None +msgid "" +"Screencast showing the differents in between URL and text type fields with " +"actual values" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.mobile}``" -msgstr "``#{ticket.owner.mobile}``" +#: ../system/objects/types.rst:352 +msgid "How does this work...?!" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Login" -msgstr "Billet > Propriétaire > Login" +#: ../system/objects/types.rst:354 +msgid "" +"As an example, let's say you have an attribute called ``amazing_attribute`` " +"and you want to open a google search directly with the input from that field." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.login}``" -msgstr "``#{ticket.owner.login}``" +#: ../system/objects/types.rst:357 +msgid "" +"Providing the link-template field below allows you to do so: ``https://www." +"google.com/search?q=#{ticket.amazing_attribute}``" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``agent``" -msgstr "``Agent``" +#: ../system/objects/types.rst:362 +msgid "" +"You can use any :doc:`Zammad variable ` as long as it's " +"available in the moment you need it." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Lastname" -msgstr "Billet > Propriétaire > Nom de famille" +#: ../system/objects/types.rst:365 +msgid "" +"As a result, you are redirected to Google with a search for the value of the " +"attribute, if you click on the button in the ticket (as you can see in the " +"screencast above)." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.lastname}``" -msgstr "``#{ticket.owner.lastname}``" +#: ../system/packages.rst:2 +msgid "Packages" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Mustermann`` or empty if not set" -msgstr "``Mustermann`` ou vide si non défini" +#: ../system/packages.rst:4 +msgid "That's the package management-area." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Firstname" -msgstr "Billet > Propriétaire > Prénom" +#: ../system/packages.rst:6 +msgid "Individual add-ons for Zammad can be installed and managed here." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.firstname}``" -msgstr "``#{ticket.owner.firstname}``" +#: ../system/sessions.rst:2 +msgid "Sessions" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Max`` or empty if not set" -msgstr "``Max`` ou vide si non défini" +#: ../system/sessions.rst:4 +msgid "" +"Sessions management allows reviewing currently known user sessions and " +"allows to end these. The session timeout is affected by :ref:" +"`security_session_timeout` configurations from security settings." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Fax" -msgstr "Billet > Propriétaire > Télécopieur" +#: ../system/sessions.rst:None +msgid "Screenshot showing Zammad's session management" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.fax}``" -msgstr "``#{ticket.owner.fax}``" +#: ../system/sessions.rst:13 +msgid "Zammad will provide the following information:" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Email" -msgstr "Billet > Propriétaire > Courriel" +#: ../system/sessions.rst:16 +msgid "" +"The user account this session entry belongs to. It can be normal if a user " +"has several sessions in the list. This can be due to changed browser " +"information or if you use e.g. single sign on methods where the user does " +"not use the log off button." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.email}``" -msgstr "``#{ticket.owner.email}``" +#: ../system/sessions.rst:22 +msgid "Browser" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``agent@company.tld`` or empty if not set" -msgstr "``agent@company.tld`` ou vide si non défini" +#: ../system/sessions.rst:22 +msgid "The browser agent communicated to Zammad." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Department" -msgstr "Billet > Propriétaire > Département" +#: ../system/sessions.rst:40 +#, fuzzy +msgid "Location" +msgstr "Bloquer les notifications" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.department}``" -msgstr "``#{ticket.owner.department}``" +#: ../system/sessions.rst:25 +msgid "" +"The anticipated location based on the users IP address. Depending on the IP " +"address the result shown may differ. This option depends on :doc:`/settings/" +"system/services`." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Support`` or empty if not set" -msgstr "``Assistance`` ou vide si non défini" +#: ../system/sessions.rst:29 +msgid "The following information can be shown:" +msgstr "" -#: ../system/variables/ticket.rst:1 -#, fuzzy -msgid "Ticket > Owner > Avatar" -msgstr "Billet > Propriétaire > Télécopieur" +#: ../system/sessions.rst:33 +msgid "IP address" +msgstr "" -#: ../system/variables/ticket.rst:1 -#, fuzzy -msgid "``#{ticket.owner.avatar(60,60)}``" -msgstr "``#{ticket.owner.lastname}``" +#: ../system/sessions.rst:32 +msgid "" +"Either if you set *Geo IP services* to inactive or you're using internal IP " +"address which do not provide location information." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Address" -msgstr "Billet > Propriétaire > Adresse" +#: ../system/sessions.rst:40 +msgid "Country (or Country + City)" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.address}``" -msgstr "``#{ticket.owner.address}``" +#: ../system/sessions.rst:36 +msgid "" +"If *Geo IP services* is enabled only. Depends on how detailed the available " +"IP address information are." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Shared organization" -msgstr "Billet > Prganisation > Organisation partagée" +#: ../system/sessions.rst:39 +msgid "" +"Be aware that results can be inaccurate - this technically is not an error." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.shared}``" -msgstr "``#{ticket.organization.shared}``" +#: ../system/sessions.rst:43 +msgid "Age" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Note" -msgstr "Billet > Organisation > Note" +#: ../system/sessions.rst:43 +msgid "Provides the time when the session initially has been created." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.note}``" -msgstr "``#{ticket.organization.note}``" +#: ../system/sessions.rst:50 +msgid "Update" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Name" -msgstr "Billet > Organisation > Nom" +#: ../system/sessions.rst:46 +msgid "" +"Provides the time the user used this session to open Zammad. This timestamp " +"is only updated if the user e.g. reloads, not during normal work on tickets." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.name}``" -msgstr "``#{ticket.organization.name}``" +#: ../system/sessions.rst:50 +msgid "This timestamp is being used for the session timeout." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Zammad GmbH`` or empty if not set" -msgstr "``Zammad GmbH`` ou vide si non défini" +#: ../system/sessions.rst:53 +msgid "" +"Use the delete button to remove a single session on behalf of your user." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Domain based assignment" -msgstr "Billet > Organisation > Affectation basée sur un domaine" +#: ../system/subscription.rst:2 +msgid "Subscription (SaaS)" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.domain_assignment}``" -msgstr "``#{ticket.organization.domain_assignment}``" +#: ../system/subscription.rst:4 +msgid "" +"The subscription settings page allows you to configure your instances " +"package and number of agents required." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Domain" -msgstr "Billet > Organisation > Domaine" +#: ../system/subscription.rst:9 +msgid "" +"This setting section is only available for Hosted setups. If you're looking " +"for on premise support contracts, please see the `Zammad pricing page " +"`_." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.domain}``" -msgstr "``#{ticket.organization.domain}``" +#: ../system/subscription.rst:14 ../system/subscription.rst:34 +msgid "Plan" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``domain.tld`` or empty if not set" -msgstr "``domaine.tld`` ou vide si non défini" +#: ../system/subscription.rst:16 +msgid "" +"Here you can set up everything affecting your instance subscription " +"functions like number of agents and package." +msgstr "" -#: ../system/variables/ticket.rst:1 -#, fuzzy -msgid "Ticket > Organization > VIP" -msgstr "Billet > Organisation > Note" +#: ../system/subscription.rst:19 +msgid "" +"On top of the page you can find a subscription summary. You'll find the " +"number of used and available (booked) agent seats there. By using the *see " +"more* link you can also expand an agent list to see the currently configured " +"active agents. This list *does not* count accounts with admin permissions " +"only." +msgstr "" -#: ../system/variables/ticket.rst:1 -#, fuzzy -msgid "``#{ticket.organization.vip}``" -msgstr "``#{ticket.organization.domain}``" +#: ../system/subscription.rst:None +msgid "" +"Within subscription you can always see how many agents are still\n" +"available to add and who uses the seats." +msgstr "" -#: ../system/variables/ticket.rst:1 -#, fuzzy -msgid "Ticket > Number" -msgstr "Billet > #:" +#: ../system/subscription.rst:29 +msgid "" +"Learn more on how to manage your agents in general :doc:`here `." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.number}``" -msgstr "``#{ticket.number}``" +#: ../system/subscription.rst:36 +msgid "" +"This section gives you an overview of the available plans and their " +"functions / limits. If you require a more detailed table, check our " +"`detailed pricing table `_ for more." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``31001``, ``201910731001``, ..." -msgstr "``31001``, ``201910731001``, ..." +#: ../system/subscription.rst:40 +msgid "" +"Your selection in this step will decide on the base agent price and e.g. " +"agent limits that might apply in the summary step." +msgstr "" -#: ../system/variables/ticket.rst:1 -#, fuzzy -msgid "Ticket > ID" -msgstr "Billet > #:" +#: ../system/subscription.rst:43 +msgid "" +"The green *Selected* button will also tell you what plan you're currently in." +msgstr "" -#: ../system/variables/ticket.rst:1 -#, fuzzy -msgid "``#{ticket.id}``" -msgstr "``#{ticket.title}``" +#: ../system/subscription.rst:47 +msgid "" +"Trial instances are running at Professional with 3 agents. The plan cannot " +"be changed during the trial for technical reasons, if you require more " +"agents for testing, please contact `our sales team `_ with a reason for the raise request." +msgstr "" -#: ../system/variables/ticket.rst:1 -#, fuzzy -msgid "``17``, ``5281``, ..." -msgstr "``new``, ``open``, ..." +#: ../system/subscription.rst:None +msgid "" +"Screenshot showing three available packages for a hosted Zammad\n" +"instance" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact (customer)" -msgstr "Billet > Dernier contact (client)" +#: ../system/subscription.rst:57 +msgid "" +"At the bottom of this block you can find a summary where you can adjust the " +"settings of the previous selected plan." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_customer_at}``" -msgstr "``#{ticket.last_contact_customer_at}``" +#: ../system/subscription.rst:62 +msgid "" +"Note that upgrading (more agents, higher package) is always possible, " +"however, downgrading will only happen when your billing period renews." +msgstr "" -#: ../system/variables/ticket.rst:1 -#, fuzzy +#: ../system/subscription.rst:66 msgid "" -"``2019-10-07 16:25:00 UTC`` or empty if not applicable yet (Please note " -"`Ticket last contact behavior Settings `_ for this)" +"Upgrading resets your billing period and existing credit will be deducted " +"from the new total." msgstr "" -"``2019-10-07 16:25:00 UTC`` ou vide si ne s'applique pas encore (veuillez " -"noter ``Paramètres: comportement du dernier contact du billet ``_ pour cela)" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact" -msgstr "Billet > Dernier contact" +#: ../system/subscription.rst:75 +msgid "Billing cycle" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_at}``" -msgstr "``#{ticket.last_contact_at}``" +#: ../system/subscription.rst:70 +msgid "" +"You can choose between either monthly or yearly billing. The price per agent " +"will be cheaper if you decide for yearly billing." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact (agent)" -msgstr "Billet > Dernier contact (Agent)" +#: ../system/subscription.rst:73 +msgid "" +"If you're still trying out things and are unsure of the right package for " +"your instance, you may want to choose monthly first and then upgrade to " +"yearly when you're sure." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_agent_at}``" -msgstr "``#{ticket.last_contact_agent_at}``" +#: ../system/subscription.rst:83 +msgid "Plan: (Starter|Professional|Plus) - Agents" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable yet" -msgstr "``2019-10-07 16:25:00 UTC`` ou vide si non encore applicable" +#: ../system/subscription.rst:78 +msgid "Choose the number of agents you require for your instance." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Note" -msgstr "Billet > Groupe > Note" +#: ../system/subscription.rst:80 +msgid "" +"Keep in mind that some packages may have agent limits. Depending on the " +"previous chosen package, you won't be able to exceed specific agent numbers. " +"Also note that setting less agents than currently configured is not possible." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.note}``" -msgstr "``#{ticket.group.note}``" +#: ../system/subscription.rst:86 +msgid "Total" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Note about this group``" -msgstr "``Note à propos de ce groupe``" +#: ../system/subscription.rst:86 +msgid "This will be the net total you're going to be billed." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Name" -msgstr "Billet > Groupe > Name" +#: ../system/subscription.rst:88 +msgid "" +"By using the *Update subscription* button, the instance package will be " +"adjusted immediately. If you didn't provide a payment method yet, Zammad " +"will request you to provide one at this point." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.name}``" -msgstr "``#{ticket.group.name}``" +#: ../system/subscription.rst:94 +msgid "" +"In case you're still within the trial period, this means that the trial will " +"be over immediately!" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Sales``" -msgstr "``Ventes``" +#: ../system/subscription.rst:97 +msgid "Down- or upgrading during the trial period *is not* possible." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Follow-up possible" -msgstr "Billet > Groupe > Suivi possible" +#: ../system/subscription.rst:None +msgid "Screenshot showing payment options and a pricing summary" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.follow_up_possible}``" -msgstr "``#{ticket.group.follow_up_possible}``" +#: ../system/subscription.rst:103 +msgid "Billing Information" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``no`` or ``yes``" -msgstr "``no`` ou ``yes``" +#: ../system/subscription.rst:105 +msgid "" +"You can control all billing relevant information like invoices, billing " +"address and the option to cancel your subscription." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Assign Follow-Ups" -msgstr "Ticket > Groupe > Attribuer des suivis" +#: ../system/subscription.rst:108 +msgid "" +"All adjusted billing information below only affect future invoices. If your " +"invoice was issued wrong, please contact `our sales team `_." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.follow_up_assignment}``" -msgstr "``#{ticket.group.follow_up_assignment}``" +#: ../system/subscription.rst:114 +msgid "Billing address" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Assignment Timeout" -msgstr "Ticket > Groupe > Délai d'attente d'affectation" +#: ../system/subscription.rst:113 +msgid "" +"Provide your company address here, make sure to include the companies name " +"in case required. This address will be referenced on your invoice." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.assignment_timeout}``" -msgstr "``#{ticket.group.assignment_timeout}``" +#: ../system/subscription.rst:118 +msgid "VAT ID" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``20`` or empty if not configured" -msgstr "``20`` ou vide si non défini" +#: ../system/subscription.rst:117 +msgid "" +"Provide your VAT ID here. If applicable your invoice will not contain German " +"VAT. Please make sure to pay the VAT in your country as required." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > First response" -msgstr "Billet > Première réponse" +#: ../system/subscription.rst:127 +msgid "Billing Email Address" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.first_response_at}``" -msgstr "``#{ticket.first_response_at}``" +#: ../system/subscription.rst:121 +msgid "" +"Usually the instance owner (the person that registered the instance) will " +"receive all emails including the invoices. In case you have your own billing " +"department, you can provide their email address here." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Escalation at" -msgstr "Billet > Escalade à" +#: ../system/subscription.rst:125 +msgid "" +"All billing relevant information will then be sent to this email address." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.escalation_at}``" -msgstr "``#{ticket.escalation_at}``" +#: ../system/subscription.rst:127 +msgid "Invoices are sent as attachment (PDF) to this email address." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable" -msgstr "``2019-10-07 16:25:00 UTC`` ou vide si non défini" +#: ../system/subscription.rst:129 +msgid "" +"Don't forget to press the *Update billing information* button after you " +"changed above settings." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Web" -msgstr "Billet > Client > Web" +#: ../system/subscription.rst:None +msgid "" +"Screenshot showing options for billing information within the\n" +"subscription menu" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.web}``" -msgstr "``#{ticket.customer.web}``" +#: ../system/subscription.rst:137 +msgid "Payment Method" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > VIP" -msgstr "Billet > Client > VIP" +#: ../system/subscription.rst:139 +msgid "You can pay via credit card or SEPA mandate." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.vip}``" -msgstr "``#{ticket.customer.vip}``" +#: ../system/subscription.rst:144 +msgid "Credit card" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Phone" -msgstr "Billet > Client > Téléphone" +#: ../system/subscription.rst:142 +msgid "" +"Simply follow the dialogue by clicking *authorize credit card* and confirm -" +"if required by your bank- your consent to Zammad using your card for the " +"payments." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.phone}``" -msgstr "``#{ticket.customer.phone}``" +#: ../system/subscription.rst:148 +msgid "SEPA Direct Debit" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Note" -msgstr "Billet > Client > Note" +#: ../system/subscription.rst:147 +msgid "" +"Provide the requested information of the bank account holder and update if " +"you're ready. You'll then receive an email with the SEPA mandate." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.note}``" -msgstr "``#{ticket.customer.note}``" +#: ../system/subscription.rst:150 +msgid "" +"Technically there's also the possibility to pay via invoice, however - this " +"method only applies to a fairly low number of instances. Please contact `our " +"sales team `_ for more information." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Mobile" -msgstr "Billet > Client > Mobile" +#: ../system/subscription.rst:156 +msgid "Cancel Subscription" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.mobile}``" -msgstr "``#{ticket.customer.mobile}``" +#: ../system/subscription.rst:158 +msgid "" +"Do you want to cancel your subscription? In case you no longer want to use " +"Zammad's SaaS, you can cancel your subscription by using the red *Yes, " +"please cancel my subscription* button." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Login" -msgstr "Billet > Client > Login" +#: ../system/subscription.rst:162 +msgid "" +"To cancel the description, enter the FQDN of your Zammad instance and " +"provide a reason for your cancellation." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.login}``" -msgstr "``#{ticket.customer.login}``" +#: ../system/subscription.rst:165 +msgid "" +"Your subscription will end the day after your trial or billing period ends." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Lastname" -msgstr "Billet > Client > Nom de famille" +#: ../system/subscription.rst:None +msgid "Screenshot showing subscription cancellation dialog" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.lastname}``" -msgstr "``#{ticket.customer.lastname}``" +#: ../system/subscription.rst:174 +msgid "" +"We will remind you about your cancelled subscription several times up front. " +"After the subscription ended all instance data will be removed. A restore " +"*is not* possible after that point!" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Firstname" -msgstr "Billet > Client > Prénom" +#: ../system/subscription.rst:178 +msgid "**😖 Cancelled by accident?**" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.firstname}``" -msgstr "``#{ticket.customer.firstname}``" +#: ../system/subscription.rst:180 +msgid "" +"You can always undo the cancellation via the *Yes, undo the cancellation of " +"my subscription* button up to the last subscription day!" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Fax" -msgstr "Billet > Client > Télécopieur" +#: ../system/subscription.rst:0 +msgid "" +"Screenshot showing a red button to cancel the subscription\n" +"cancellation" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.fax}``" -msgstr "``#{ticket.customer.fax}``" +#: ../system/subscription.rst:189 +msgid "Payment History" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Email" -msgstr "Billet > Client > Courriel" +#: ../system/subscription.rst:191 +msgid "" +"The payment history will display a history of all paid invoices. At this " +"point you can also download these in case you need them again." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.email}``" -msgstr "``#{ticket.customer.email}``" +#: ../system/subscription.rst:196 +msgid "" +"You will only find *paid* invoices here. Invoices that are to be billed are " +"not available before the payment is completed." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Department" -msgstr "Billet > Client > Département" +#: ../system/subscription.rst:201 +msgid "Date" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.department}``" -msgstr "``#{ticket.customer.department}``" +#: ../system/subscription.rst:201 +msgid "Date of the invoice creation." +msgstr "" -#: ../system/variables/ticket.rst:1 +#: ../system/subscription.rst:204 #, fuzzy -msgid "Ticket > Customer > Avatar" -msgstr "Billet > Client > Télécopieur" +msgid "Amount" +msgstr "Comptes" -#: ../system/variables/ticket.rst:1 -#, fuzzy -msgid "``#{ticket.customer.avatar(60,60)}``" -msgstr "``#{ticket.customer.lastname}``" +#: ../system/subscription.rst:204 +msgid "Invoice total including VAT if applicable." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Address" -msgstr "Billet > Client > Adresse" +#: ../system/subscription.rst:207 +msgid "" +"Contains contract period (monthly or yearly) and hosted plan for the " +"subscription period in question." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.address}``" -msgstr "``#{ticket.customer.address}``" +#: ../system/subscription.rst:218 +msgid "Payment method / Service period" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Web" -msgstr "Billet > Créé par le > Web" +#: ../system/subscription.rst:211 +msgid "" +"Used bank account or credit card as well as the subscription period the " +"invoice is about." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.web}``" -msgstr "``#{ticket.created_by.web}``" +#: ../system/subscription.rst:216 +msgid "" +"It might happen that the invoice date and subscription period differ. This " +"is nothing to worry about, the subscription periods will be accounted later " +"on." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > VIP" -msgstr "Billet > Créé par > VIP" +#: ../system/subscription.rst:222 +msgid "Receipt" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.vip}``" -msgstr "``#{ticket.created_by.vip}``" +#: ../system/subscription.rst:221 +msgid "" +"Use the arrow to download the invoice in question. You can download all " +"available invoices any time you need to here!" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Phone" -msgstr "Billet > Créé par > Téléphone" +#: ../system/subscription.rst:None +msgid "Screenshot showing payment history of a hosted instance" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.phone}``" -msgstr "``#{ticket.created_by.phone}``" +#: ../system/subscription.rst:229 +msgid "FAQ" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Note" -msgstr "Billet > Créé par > Note" +#: ../system/subscription.rst:233 +msgid "I set up a trial account but am missing functions to test" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.note}``" -msgstr "``#{ticket.created_by.note}``" +#: ../system/subscription.rst:232 +msgid "" +"The trial instance is running within the professional package allowing up to " +"three agents." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Mobile" -msgstr "Billet > Créé par > Mobile" +#: ../system/subscription.rst:236 +msgid "Can I change package within the trial?" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.mobile}``" -msgstr "``#{ticket.created_by.mobile}``" +#: ../system/subscription.rst:236 +msgid "No. As soon as the package is changed the subscription begins." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Login" -msgstr "Billet > Créé par > Login" +#: ../system/subscription.rst:241 +msgid "What happens to my trial instance after the trial period ended?" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.login}``" -msgstr "``#{ticket.created_by.login}``" +#: ../system/subscription.rst:239 +msgid "" +"Your instance will automatically be canceled for you. Please see *What " +"happens to my instance after it has been canceled?* for more." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Lastname" -msgstr "Billet > Créé par > Nom de famille" +#: ../system/subscription.rst:254 +msgid "What happens to my instance after it has been canceled?" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.lastname}``" -msgstr "``#{ticket.created_by.lastname}``" +#: ../system/subscription.rst:244 +msgid "That depends slightly on your instance state:" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Firstname" -msgstr "Billet > Créé par > Prénom" +#: ../system/subscription.rst:250 +msgid "Trial instance" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.firstname}``" -msgstr "``#{ticket.created_by.firstname}``" +#: ../system/subscription.rst:247 +msgid "" +"If you're still on trial, we will ice your instance and remind you once " +"again about your instance. We then will wait some days and remove your " +"instance from our system. This is the last time we will inform you by Email." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Fax" -msgstr "Billet > Créé par > Télécopieur" +#: ../system/subscription.rst:254 +msgid "Paid instance" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.fax}``" -msgstr "``#{ticket.created_by.fax}``" +#: ../system/subscription.rst:253 +msgid "" +"If you're a paying customer and canceled your subscription, the instance " +"removal will take place the day after your last subscription day." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Email" -msgstr "Billet > Créé par > Courriel" +#: ../system/subscription.rst:256 +msgid "Can removed instances be restored?" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.email}``" -msgstr "``#{ticket.created_by.email}``" +#: ../system/subscription.rst:257 +msgid "No. Once your instance has been removed, a restoration is not possible." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Department" -msgstr "Billet > Créé par > Département" +#: ../system/system-report.rst:2 +#, fuzzy +msgid "System Report" +msgstr "Filtres" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.department}``" -msgstr "``#{ticket.created_by.department}``" +#: ../system/system-report.rst:4 +msgid "" +"In this place you can't configure Zammad. Instead you can obtain a system " +"report about Zammad and its configuration." +msgstr "" -#: ../system/variables/ticket.rst:1 -#, fuzzy -msgid "Ticket > Created by > Avatar" -msgstr "Billet > Créé par > Télécopieur" +#: ../system/system-report.rst:7 +msgid "" +"See the description in Zammad for an explanation. You can even find a " +"preview of the included data below the **Download** button." +msgstr "" -#: ../system/variables/ticket.rst:1 -#, fuzzy -msgid "``#{ticket.created_by.avatar(60,60)}``" -msgstr "``#{ticket.created_by.lastname}``" +#: ../system/system-report.rst:10 +msgid "" +"Zammad never sends this automatically to anyone. It is a manual process only " +"to provide better support based on your configuration." +msgstr "" + +#: ../system/translations.rst:2 +msgid "Translations" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Address" -msgstr "Billet > Créé par > Adresse" +#: ../system/translations.rst:4 +msgid "" +"Translations of Zammad are processed centrally in our `Weblate instance " +"`_. This allows non-developers to review " +"and update translation texts of the language they actually speak." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.address}``" -msgstr "``#{ticket.created_by.address}``" +#: ../system/translations.rst:9 +msgid "" +"Your language is in an incomplete translation state or has typos? Please " +"consider helping us in sorting this out! All you need is either a GitHub " +"account or to register directly in our instance." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created at" -msgstr "Billet créé à" +#: ../system/translations.rst:13 +msgid "" +"Did you know? This is also where the documentation translations are handled. " +"🤓" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_at}``" -msgstr "``#{ticket.created_at}``" +#: ../system/translations.rst:15 +msgid "" +"Have a look in our :docs:`contribution section ` in the system documentation to get started!" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "2019-10-07 16:25:00 UTC" -msgstr "2019-10-07 16:25:00 UTC" +#: ../system/translations.rst:20 +#, fuzzy +msgid "Local Translations" +msgstr "Bloquer les notifications" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Closing time" -msgstr "Ticket > Heure de fermeture à" +#: ../system/translations.rst:22 +msgid "" +"Apart from these system translations, there's still local translations you " +"can manage. This is relevant if you added custom objects that require " +"translations or even custom states and priorities." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.close_at}``" -msgstr "``#{ticket.close_at}``" +#: ../system/translations.rst:None +msgid "Translation management screen within the admin menu" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "2019-10-07 17:25:00 UTC" -msgstr "2019-10-07 17:25:00 UTC" +#: ../system/translations.rst:31 +msgid "Updating Translations" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``3``, any number of articles existing in the ticket right now" -msgstr "``3``, nombre d'articles existant pour le billet en ce moment" +#: ../system/translations.rst:33 +msgid "" +"Because of how Zammad ships translations, the only way to update the system " +"translations is to update your Zammad installation. The benefit of this is " +"that you no longer need internet access during a Zammad upgrade as the " +"package has everything it requires already." +msgstr "" -#: ../system/version.rst:2 -msgid "Version" +#: ../system/translations.rst:39 +msgid "Translation of Custom Objects" msgstr "" -#: ../system/version.rst:4 -msgid "Shows which version is currently being used on your Zammad-instance." +#: ../system/translations.rst:41 +msgid "" +"No problem at all! You can customize any translation locally, even if it is " +"not initially provided by the system." msgstr "" -#: ../manage/roles/admin-permissions.rst:53 -msgid "``admin.checklist``" +#: ../system/translations.rst:44 +msgid "" +"Translation is supported for a broad number of features, including but not " +"limited to custom:" msgstr "" -#: ../manage/roles/admin-permissions.rst:54 +#: ../system/translations.rst:47 #, fuzzy -msgid ":doc:`Manage > Checklist `" -msgstr "Billet > Prganisation > Organisation partagée" +msgid "Object Attributes" +msgstr "Attributs d'un billet" -#: ../manage/roles/admin-permissions.rst:83 -msgid "``admin.channel_whatsapp``" -msgstr "" +#: ../system/translations.rst:48 +#, fuzzy +msgid "Ticket Macros" +msgstr "Billet > Étiquettes" -#: ../manage/roles/admin-permissions.rst:84 +#: ../system/translations.rst:49 #, fuzzy -msgid ":doc:`Channels > Whatsapp `" -msgstr "Billet > Prganisation > Organisation partagée" +msgid "Ticket Overviews" +msgstr "Variables de billet" -#: ../manage/roles/admin-permissions.rst:124 -msgid "``admin.public_links``" -msgstr "" +#: ../system/translations.rst:50 +#, fuzzy +msgid "Ticket Priorities" +msgstr "Billet > Priorité > Nom" -#: ../manage/roles/admin-permissions.rst:125 +#: ../system/translations.rst:51 #, fuzzy -msgid ":doc:`Manage > Public Links `" -msgstr "Billet > Prganisation > Organisation partagée" +msgid "Ticket States" +msgstr "Billet > État > Nom" -#: ../manage/roles/admin-permissions.rst:151 -msgid "``admin.system_report``" +#: ../system/translations.rst:54 +msgid "Customizing Translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:152 -#, fuzzy -msgid ":doc:`System > System Report `" -msgstr "Billet > Prganisation > Organisation partagée" +#: ../system/translations.rst:56 +msgid "" +"Within the translation screen, simply click on the **New Translation** " +"button." +msgstr "" -#: ../manage/roles/admin-permissions.rst:166 -#, fuzzy -msgid "``admin.ticket_auto_assignment``" -msgstr "``#{ticket.group.follow_up_assignment}``" +#: ../system/translations.rst:None +msgid "New translation dialog" +msgstr "" -#: ../manage/roles/admin-permissions.rst:167 -msgid ":ref:`Settings > Ticket > Auto Assignment `" +#: ../system/translations.rst:62 +msgid "" +"In the dialog you can immediately enter the exact translation source (if you " +"know it) and your custom translation text for it and click **Submit**." msgstr "" -#: ../manage/roles/admin-permissions.rst:169 -msgid "``admin.ticket_duplicate_detection``" +#: ../system/translations.rst:65 +msgid "" +"Alternatively, try to search for translation suggestions in the list below. " +"Selecting an item from the list will pre-fill the translation source for you " +"and then you can just enter your custom translation." msgstr "" -#: ../manage/roles/admin-permissions.rst:170 -msgid ":ref:`Settings > Ticket > Duplicate Detection `" +#: ../system/translations.rst:69 +msgid "" +"The target language will always default to your current language selection. " +"If you need to translate for a different language, simply change the " +"selection before submitting." msgstr "" -#: ../manage/roles/admin-permissions.rst:172 -#, fuzzy -msgid "``admin.ticket_priority``" -msgstr "``#{ticket.priority.name}``" +#: ../system/translations.rst:73 +msgid "" +"All your custom translations will show up in the overview table when added. " +"And they will even persist across Zammad updates!" +msgstr "" -#: ../manage/roles/admin-permissions.rst:173 -msgid ":ref:`System > Objects >Ticket Priority `" +#: ../system/translations.rst:76 +msgid "" +"Make sure to reload your browser if a translated string is not displayed." msgstr "" -#: ../manage/roles/admin-permissions.rst:175 -#, fuzzy -msgid "``admin.ticket_state``" -msgstr "``#{ticket.state.name}``" +#: ../system/translations.rst:80 +msgid "Reverting to Original Translations" +msgstr "" -#: ../manage/roles/admin-permissions.rst:176 -msgid ":ref:`System > Objects >Ticket State `" +#: ../system/translations.rst:82 +msgid "" +"If you want to revert a custom translation to original text, simply use the " +"appropriate action within the row of the overview table." msgstr "" -#: ../manage/roles/admin-permissions.rst:193 -msgid "``admin.webhook``" +#: ../system/translations.rst:85 +msgid "" +"Depending on the type of the translation source, the action has a slightly " +"different name:" msgstr "" -#: ../manage/roles/admin-permissions.rst:194 -#, fuzzy -msgid ":doc:`Manage > Webhook `" -msgstr "Billet > Prganisation > Organisation partagée" +#: ../system/translations.rst:88 +msgid "**Reset** for customized system translations" +msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:43 -msgid "``user_preferences.appearance``" +#: ../system/translations.rst:89 +msgid "**Remove** for customized local translations" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:44 +#: ../system/translations.rst:91 +msgid "" +"In both cases, the action will remove the customized translation after a " +"confirmation." +msgstr "" + +#: ../system/translations.rst:None +msgid "Screenshot showing the location of the Remove action" +msgstr "" + +#: ../system/translations.rst:99 #, fuzzy -msgid "Appearance configuration" +msgid "Inline Translations" msgstr "Bloquer les notifications" -#: ../manage/roles/user-preferences-permissions.rst:0 -msgid "Users can switch between dark, light and" +#: ../system/translations.rst:101 +msgid "" +"If you prefer a more hands-on approach, you can activate the inline or on-" +"screen translation feature by pressing ``ctrl`` + ``alt`` + ``t`` at any " +"time and on any screen." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:0 -msgid "automatic mode." +#: ../system/translations.rst:105 +msgid "" +"All customizable translation texts will be highlighted for you on the " +"screen. Just click into the highlighted area and update the text in place." msgstr "" -#: ../system/system-report.rst:2 -#, fuzzy -msgid "System Report" -msgstr "Filtres" +#: ../system/translations.rst:None +msgid "Inline translation mode activated for the Overview screen" +msgstr "" -#: ../system/system-report.rst:4 +#: ../system/translations.rst:112 msgid "" -"In this place you can't configure Zammad. Instead you can obtain a system " -"report about Zammad and its configuration." +"When finished editing, simply press ``ctrl`` + ``alt`` + ``t`` again to " +"deactivate." msgstr "" -#: ../system/system-report.rst:7 +#: ../system/translations.rst:117 msgid "" -"See the description in Zammad for an explanation. You can even find a " -"preview of the included data below the **Download** button." +"Even though it's available on any screen, the inline translation feature " +"requires admin permissions. It works only for the current language " +"selection. If you need to translate a different language, first change the " +"language in your :user-docs:`profile settings `." msgstr "" -#: ../system/system-report.rst:10 -msgid "" -"Zammad never sends this automatically to anyone. It is a manual process only " -"to provide better support based on your configuration." +#: ../system/version.rst:2 +msgid "Version" +msgstr "" + +#: ../system/version.rst:4 +msgid "Shows which version is currently being used on your Zammad-instance." msgstr "" #~ msgid "" diff --git a/locale/hr/LC_MESSAGES/admin-docs.po b/locale/hr/LC_MESSAGES/admin-docs.po index 0c2f033f..5ac51173 100644 --- a/locale/hr/LC_MESSAGES/admin-docs.po +++ b/locale/hr/LC_MESSAGES/admin-docs.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Zammad\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-11-06 10:31+0100\n" +"POT-Creation-Date: 2024-11-12 16:31+0100\n" "PO-Revision-Date: 2022-06-15 13:40+0000\n" "Last-Translator: Ivan Perovic \n" "Language-Team: Croatian Checklist `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:56 msgid "``admin.channel_email``" msgstr "" -#: ../manage/roles/admin-permissions.rst:54 #: ../manage/roles/admin-permissions.rst:57 msgid ":doc:`Channels > Email `" msgstr "" -#: ../manage/roles/admin-permissions.rst:56 #: ../manage/roles/admin-permissions.rst:59 msgid "``admin.channel_facebook``" msgstr "" -#: ../manage/roles/admin-permissions.rst:57 #: ../manage/roles/admin-permissions.rst:60 msgid ":doc:`Channels > Facebook `" msgstr "" -#: ../manage/roles/admin-permissions.rst:58 #: ../manage/roles/admin-permissions.rst:61 msgid "" "Accessing Facebook tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:59 #: ../manage/roles/admin-permissions.rst:62 msgid "``admin.channel_formular``" msgstr "" -#: ../manage/roles/admin-permissions.rst:60 #: ../manage/roles/admin-permissions.rst:63 msgid ":doc:`Channels > Form `" msgstr "" -#: ../manage/roles/admin-permissions.rst:62 #: ../manage/roles/admin-permissions.rst:65 msgid "``admin.channel_google``" msgstr "" -#: ../manage/roles/admin-permissions.rst:63 #: ../manage/roles/admin-permissions.rst:66 msgid ":doc:`Channels > Google `" msgstr "" -#: ../manage/roles/admin-permissions.rst:65 #: ../manage/roles/admin-permissions.rst:68 msgid "``admin.channel_microsoft365``" msgstr "" -#: ../manage/roles/admin-permissions.rst:66 #: ../manage/roles/admin-permissions.rst:69 msgid ":doc:`Channels > Microsoft 365 `" msgstr "" -#: ../manage/roles/admin-permissions.rst:68 #: ../manage/roles/admin-permissions.rst:71 msgid "``admin.channel_sms``" msgstr "" -#: ../manage/roles/admin-permissions.rst:69 #: ../manage/roles/admin-permissions.rst:72 msgid ":doc:`Channels > SMS `" msgstr "" -#: ../manage/roles/admin-permissions.rst:71 #: ../manage/roles/admin-permissions.rst:74 msgid "``admin.channel_telegram``" msgstr "" -#: ../manage/roles/admin-permissions.rst:72 #: ../manage/roles/admin-permissions.rst:75 msgid ":doc:`Channels > Telegram `" msgstr "" -#: ../manage/roles/admin-permissions.rst:73 #: ../manage/roles/admin-permissions.rst:76 msgid "" "Accessing Telegram tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:74 #: ../manage/roles/admin-permissions.rst:77 msgid "``admin.channel_twitter``" msgstr "" -#: ../manage/roles/admin-permissions.rst:75 #: ../manage/roles/admin-permissions.rst:78 msgid ":doc:`Channels > Twitter `" msgstr "" -#: ../manage/roles/admin-permissions.rst:76 #: ../manage/roles/admin-permissions.rst:79 msgid "" "Accessing Twitter/X tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:77 #: ../manage/roles/admin-permissions.rst:80 msgid "``admin.channel_web``" msgstr "" -#: ../manage/roles/admin-permissions.rst:78 #: ../manage/roles/admin-permissions.rst:81 msgid ":doc:`Channels > Web `" msgstr "" -#: ../manage/roles/admin-permissions.rst:80 +#: ../manage/roles/admin-permissions.rst:83 +msgid "``admin.channel_whatsapp``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:84 +msgid ":doc:`Channels > Whatsapp `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:86 msgid "``admin.core_workflows``" msgstr "" -#: ../manage/roles/admin-permissions.rst:81 #: ../manage/roles/admin-permissions.rst:87 msgid ":doc:`System > Core Workflows `" msgstr "" -#: ../manage/roles/admin-permissions.rst:83 #: ../manage/roles/admin-permissions.rst:89 msgid "``admin.data_privacy``" msgstr "" -#: ../manage/roles/admin-permissions.rst:84 #: ../manage/roles/admin-permissions.rst:90 msgid ":doc:`System > Data Privacy `" msgstr "" -#: ../manage/roles/admin-permissions.rst:85 #: ../manage/roles/admin-permissions.rst:91 msgid "" "🔥 Be careful, it allows users to permanently delete data on the system." msgstr "" -#: ../manage/roles/admin-permissions.rst:86 #: ../manage/roles/admin-permissions.rst:92 msgid "``admin.group``" msgstr "" -#: ../manage/roles/admin-permissions.rst:87 #: ../manage/roles/admin-permissions.rst:93 msgid ":doc:`Manage > Groups `" msgstr "" -#: ../manage/roles/admin-permissions.rst:89 #: ../manage/roles/admin-permissions.rst:95 msgid "``admin.integration``" msgstr "" -#: ../manage/roles/admin-permissions.rst:90 #: ../manage/roles/admin-permissions.rst:96 msgid ":doc:`System > Integrations `" msgstr "" -#: ../manage/roles/admin-permissions.rst:92 #: ../manage/roles/admin-permissions.rst:98 msgid "``admin.knowledge_base``" msgstr "" -#: ../manage/roles/admin-permissions.rst:93 #: ../manage/roles/admin-permissions.rst:99 msgid ":doc:`Manage > Knowledge Base `" msgstr "" @@ -8608,57 +8591,46 @@ msgid "" "knowledge-base.html#editing-answers>`." msgstr "" -#: ../manage/roles/admin-permissions.rst:98 #: ../manage/roles/admin-permissions.rst:104 msgid "``admin.macro``" msgstr "" -#: ../manage/roles/admin-permissions.rst:99 #: ../manage/roles/admin-permissions.rst:105 msgid ":doc:`Manage > Macros `" msgstr "" -#: ../manage/roles/admin-permissions.rst:100 #: ../manage/roles/admin-permissions.rst:106 msgid "In some cases, macros may also require ``admin.tag``" msgstr "" -#: ../manage/roles/admin-permissions.rst:101 #: ../manage/roles/admin-permissions.rst:107 msgid "``admin.maintenance``" msgstr "" -#: ../manage/roles/admin-permissions.rst:102 #: ../manage/roles/admin-permissions.rst:108 msgid ":doc:`System > Maintenance `" msgstr "" -#: ../manage/roles/admin-permissions.rst:104 #: ../manage/roles/admin-permissions.rst:110 msgid "``admin.monitoring``" msgstr "" -#: ../manage/roles/admin-permissions.rst:105 #: ../manage/roles/admin-permissions.rst:111 msgid ":doc:`System > Monitoring `" msgstr "" -#: ../manage/roles/admin-permissions.rst:107 #: ../manage/roles/admin-permissions.rst:113 msgid "``admin.object``" msgstr "" -#: ../manage/roles/admin-permissions.rst:108 #: ../manage/roles/admin-permissions.rst:114 msgid ":doc:`System > Objects `" msgstr "" -#: ../manage/roles/admin-permissions.rst:110 #: ../manage/roles/admin-permissions.rst:116 msgid "``admin.organization``" msgstr "" -#: ../manage/roles/admin-permissions.rst:111 #: ../manage/roles/admin-permissions.rst:117 msgid ":doc:`Manage > Organizations `" msgstr "" @@ -8675,202 +8647,211 @@ msgstr "" msgid "They can even edit an organization's name, domain, and notes!" msgstr "" -#: ../manage/roles/admin-permissions.rst:115 #: ../manage/roles/admin-permissions.rst:121 msgid "``admin.overview``" msgstr "" -#: ../manage/roles/admin-permissions.rst:116 #: ../manage/roles/admin-permissions.rst:122 msgid ":doc:`Manage > Overviews`" msgstr "" -#: ../manage/roles/admin-permissions.rst:118 +#: ../manage/roles/admin-permissions.rst:124 +msgid "``admin.public_links``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:125 +msgid ":doc:`Manage > Public Links `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:127 msgid "``admin.package``" msgstr "" -#: ../manage/roles/admin-permissions.rst:119 #: ../manage/roles/admin-permissions.rst:128 msgid ":doc:`System > Packages `" msgstr "" -#: ../manage/roles/admin-permissions.rst:121 #: ../manage/roles/admin-permissions.rst:130 msgid "``admin.report_profile``" msgstr "" -#: ../manage/roles/admin-permissions.rst:122 #: ../manage/roles/admin-permissions.rst:131 msgid ":doc:`Manage > Report Profiles `" msgstr "" -#: ../manage/roles/admin-permissions.rst:123 #: ../manage/roles/admin-permissions.rst:132 msgid "Access to view reports: ``report``" msgstr "" -#: ../manage/roles/admin-permissions.rst:124 #: ../manage/roles/admin-permissions.rst:133 msgid "``admin.role``" msgstr "" -#: ../manage/roles/admin-permissions.rst:125 #: ../manage/roles/admin-permissions.rst:134 msgid ":doc:`Manage > Roles `" msgstr "" -#: ../manage/roles/admin-permissions.rst:127 #: ../manage/roles/admin-permissions.rst:136 msgid "``admin.scheduler``" msgstr "" -#: ../manage/roles/admin-permissions.rst:128 #: ../manage/roles/admin-permissions.rst:137 msgid ":doc:`Manage > Scheduler `" msgstr "" -#: ../manage/roles/admin-permissions.rst:129 #: ../manage/roles/admin-permissions.rst:138 msgid "For automation on tickets" msgstr "" -#: ../manage/roles/admin-permissions.rst:130 #: ../manage/roles/admin-permissions.rst:139 msgid "``admin.security``" msgstr "" -#: ../manage/roles/admin-permissions.rst:131 #: ../manage/roles/admin-permissions.rst:140 msgid ":doc:`Settings > Security `" msgstr "" -#: ../manage/roles/admin-permissions.rst:132 #: ../manage/roles/admin-permissions.rst:141 msgid "Settings of Zammad. This also covers third party authentications." msgstr "" -#: ../manage/roles/admin-permissions.rst:133 #: ../manage/roles/admin-permissions.rst:142 msgid "``admin.session``" msgstr "" -#: ../manage/roles/admin-permissions.rst:134 #: ../manage/roles/admin-permissions.rst:143 msgid ":doc:`System > Sessions `" msgstr "" -#: ../manage/roles/admin-permissions.rst:136 #: ../manage/roles/admin-permissions.rst:145 msgid "``admin.setting_system``" msgstr "" -#: ../manage/roles/admin-permissions.rst:137 #: ../manage/roles/admin-permissions.rst:146 msgid ":doc:`Settings > System `" msgstr "" -#: ../manage/roles/admin-permissions.rst:139 #: ../manage/roles/admin-permissions.rst:148 msgid "``admin.sla``" msgstr "" -#: ../manage/roles/admin-permissions.rst:140 #: ../manage/roles/admin-permissions.rst:149 msgid ":doc:`Manage > SLAs `" msgstr "" -#: ../manage/roles/admin-permissions.rst:142 +#: ../manage/roles/admin-permissions.rst:151 +msgid "``admin.system_report``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:152 +msgid ":doc:`System > System Report `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:154 msgid "``admin.tag``" msgstr "" -#: ../manage/roles/admin-permissions.rst:143 #: ../manage/roles/admin-permissions.rst:155 msgid ":doc:`Manage > Tags `" msgstr "" -#: ../manage/roles/admin-permissions.rst:145 #: ../manage/roles/admin-permissions.rst:157 msgid "``admin.template``" msgstr "" -#: ../manage/roles/admin-permissions.rst:146 #: ../manage/roles/admin-permissions.rst:158 msgid ":doc:`Manage > Templates `" msgstr "" -#: ../manage/roles/admin-permissions.rst:148 #: ../manage/roles/admin-permissions.rst:160 msgid "``admin.text_module``" msgstr "" -#: ../manage/roles/admin-permissions.rst:149 #: ../manage/roles/admin-permissions.rst:161 msgid ":doc:`Manage > Text Modules `" msgstr "" -#: ../manage/roles/admin-permissions.rst:151 #: ../manage/roles/admin-permissions.rst:163 msgid "``admin.ticket``" msgstr "" -#: ../manage/roles/admin-permissions.rst:152 #: ../manage/roles/admin-permissions.rst:164 msgid ":doc:`Settings > Tickets `" msgstr "" -#: ../manage/roles/admin-permissions.rst:153 #: ../manage/roles/admin-permissions.rst:165 msgid "Does not grant access to :doc:`/misc/composer`" msgstr "" -#: ../manage/roles/admin-permissions.rst:154 +#: ../manage/roles/admin-permissions.rst:166 +msgid "``admin.ticket_auto_assignment``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:167 +msgid ":ref:`Settings > Ticket > Auto Assignment `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:169 +msgid "``admin.ticket_duplicate_detection``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:170 +msgid ":ref:`Settings > Ticket > Duplicate Detection `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:172 +#, fuzzy +msgid "``admin.ticket_priority``" +msgstr "prioritet" + +#: ../manage/roles/admin-permissions.rst:173 +msgid ":ref:`System > Objects >Ticket Priority `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:175 +msgid "``admin.ticket_state``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:176 +msgid ":ref:`System > Objects >Ticket State `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:178 msgid "``admin.time_accounting``" msgstr "" -#: ../manage/roles/admin-permissions.rst:155 #: ../manage/roles/admin-permissions.rst:179 msgid ":doc:`Manage > Time Accounting `" msgstr "" -#: ../manage/roles/admin-permissions.rst:156 #: ../manage/roles/admin-permissions.rst:180 msgid "Also allows the export of timekeeping records." msgstr "" -#: ../manage/roles/admin-permissions.rst:157 #: ../manage/roles/admin-permissions.rst:181 msgid "``admin.translation``" msgstr "" -#: ../manage/roles/admin-permissions.rst:158 #: ../manage/roles/admin-permissions.rst:182 msgid ":doc:`System > Translations `" msgstr "" -#: ../manage/roles/admin-permissions.rst:159 #: ../manage/roles/admin-permissions.rst:183 msgid "Also enables inline translation" msgstr "" -#: ../manage/roles/admin-permissions.rst:160 #: ../manage/roles/admin-permissions.rst:184 msgid "``admin.trigger``" msgstr "" -#: ../manage/roles/admin-permissions.rst:161 #: ../manage/roles/admin-permissions.rst:185 msgid ":doc:`Manage > Triggers `" msgstr "" -#: ../manage/roles/admin-permissions.rst:163 #: ../manage/roles/admin-permissions.rst:187 msgid "``admin.user``" msgstr "" -#: ../manage/roles/admin-permissions.rst:164 #: ../manage/roles/admin-permissions.rst:188 msgid ":doc:`Manage > Users `" msgstr "" @@ -8889,6 +8870,14 @@ msgid "" "from-users-perspective>` ." msgstr "" +#: ../manage/roles/admin-permissions.rst:193 +msgid "``admin.webhook``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:194 +msgid ":doc:`Manage > Webhook `" +msgstr "" + #: ../manage/roles/agent-permissions.rst:2 msgid "Agent Permissions" msgstr "" @@ -9308,36 +9297,45 @@ msgid "than the user that generated them." msgstr "" #: ../manage/roles/user-preferences-permissions.rst:43 +msgid "``user_preferences.appearance``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:44 +msgid "Appearance configuration" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "Users can switch between dark, light and" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "automatic mode." +msgstr "" + #: ../manage/roles/user-preferences-permissions.rst:47 msgid "``user_preferences.avatar``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:44 #: ../manage/roles/user-preferences-permissions.rst:48 msgid "Avatar settings" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:45 #: ../manage/roles/user-preferences-permissions.rst:49 msgid "Override the default Gravatar with a custom avatar" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:46 #: ../manage/roles/user-preferences-permissions.rst:50 msgid "``user_preferences.calendar``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:47 #: ../manage/roles/user-preferences-permissions.rst:51 msgid "Configure the calendar feed" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:49 #: ../manage/roles/user-preferences-permissions.rst:53 msgid "``user_preferences.device``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:50 #: ../manage/roles/user-preferences-permissions.rst:54 msgid "Manage device login sessions" msgstr "" @@ -9354,22 +9352,18 @@ msgstr "" msgid "To learn more, see :doc:`/manage/trigger/system-notifications`." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:54 #: ../manage/roles/user-preferences-permissions.rst:58 msgid "``user_preferences.language``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:55 #: ../manage/roles/user-preferences-permissions.rst:59 msgid "Configure the UI locale/language" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:57 #: ../manage/roles/user-preferences-permissions.rst:61 msgid "``user_preferences.linked_accounts``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:58 #: ../manage/roles/user-preferences-permissions.rst:62 #, fuzzy msgid "Account linking" @@ -9394,7 +9388,6 @@ msgstr "" msgid "is the only way users can utilize third-party logins." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:63 #: ../manage/roles/user-preferences-permissions.rst:67 msgid "``user_preferences.notifications``" msgstr "" @@ -9422,7 +9415,6 @@ msgstr "" msgid "Customers can't receive ticket notifications at all." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:69 #: ../manage/roles/user-preferences-permissions.rst:73 msgid "``user_preferences.out_of_office``" msgstr "" @@ -9447,7 +9439,6 @@ msgstr "" msgid "they're replacing." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:75 #: ../manage/roles/user-preferences-permissions.rst:79 msgid "``user_preferences.overview_sorting``" msgstr "" @@ -9476,12 +9467,10 @@ msgstr "" msgid "overviews has no effect on custom orders." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:82 #: ../manage/roles/user-preferences-permissions.rst:86 msgid "``user_preferences.password``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:83 #: ../manage/roles/user-preferences-permissions.rst:87 msgid "Change account password" msgstr "" @@ -9498,7 +9487,6 @@ msgstr "" msgid "your only allowed authentication method." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:87 #: ../manage/roles/user-preferences-permissions.rst:91 msgid "``user_preferences.two_factor_authentication``" msgstr "" @@ -9535,7 +9523,7 @@ msgstr "" #: ../manage/scheduler.rst:19 msgid "" -"Schedulers can be used to send periodic reminder emails. Use :doc:`/system/" +"Schedulers can be used to send periodic reminder emails. Use :doc:`/misc/" "variables` to build highly-customized email templates." msgstr "" @@ -10533,7 +10521,7 @@ msgstr "" #: ../manage/text-modules.rst:57 msgid "" -"The example text modules below use :doc:`/system/variables` to dynamically " +"The example text modules below use :doc:`/misc/variables` to dynamically " "insert information like the customer's or agent's names." msgstr "" @@ -10874,8 +10862,8 @@ msgstr "" #: ../misc/object-conditions/basics.rst:144 #: ../misc/object-conditions/basics.rst:160 #: ../misc/object-conditions/basics.rst:168 -#: ../misc/object-conditions/basics.rst:178 ../settings/ticket.rst:2 -#: ../system/variables/ticket.rst:2 +#: ../misc/object-conditions/basics.rst:178 ../misc/variables/ticket.rst:2 +#: ../settings/ticket.rst:2 msgid "Ticket" msgstr "" @@ -11109,7 +11097,7 @@ msgstr "" #: ../manage/trigger/how-do-they-work.rst:79 msgid "" -"Certain actions (such as *email*, *SMS* and *notes*) support :doc:`/system/" +"Certain actions (such as *email*, *SMS* and *notes*) support :doc:`/misc/" "variables`, which can be used to build highly-customized message templates." msgstr "" @@ -11138,7 +11126,7 @@ msgstr "" msgid "" "You can also combine static text with placeholders for text fields. Remember " "that the placeholders' values have to be known during trigger runtime. Learn " -"more about :doc:`/system/variables`." +"more about :doc:`/misc/variables`." msgstr "" #: ../manage/trigger/how-do-they-work.rst:105 @@ -12104,7 +12092,7 @@ msgstr "" msgid "" "When switched on, a code editor will be shown below, where you can configure " "custom payload for your webhook in JSON format. To insert supported :doc:`/" -"system/variables` use ``::`` or ``#{`` shortcuts for autocomplete." +"misc/variables` use ``::`` or ``#{`` shortcuts for autocomplete." msgstr "" #: ../manage/webhook/add.rst:103 @@ -14694,11967 +14682,11859 @@ msgid "" "powerful conditions with AND/OR relations." msgstr "" -#: ../settings/branding.rst:10 -msgid "Product Name" +#: ../misc/variables.rst:2 +msgid "Variables" msgstr "" -#: ../settings/branding.rst:7 +#: ../misc/variables.rst:4 msgid "" -"Defines the name of the application, shown in the web interface, tabs and " -"title bar of the web browser." +"Please note that this is just an overview of available variables. It might " +"be incomplete or variables might not be available within some functions. If " +"you're missing variables or are not sure if something is not working as " +"expected, feel free to ask over at the `Community `_." msgstr "" -#: ../settings/branding.rst:10 -msgid "Default value: ``Zammad Helpdesk``" +#: ../misc/variables.rst:10 +msgid "" +"Variables can be called by typing ``::`` (just like text modules in the " +"frontend), as long as you're in a supported text field within the backend. " +"Zammad will display all variables being available within this context and " +"replace it to the variable as soon as you selected an entry." msgstr "" -#: ../settings/branding.rst:13 -msgid "Will be shown in the app and is included in email footers." +#: ../misc/variables.rst:15 +msgid "" +"You have an empty field which you referenced and it appears as ``-``? That's " +"currently working as designed - you might want to ensure that these fields " +"always have a value." msgstr "" -#: ../settings/branding.rst:19 -msgid "Logo" +#: ../misc/variables.rst:20 +msgid "Variable Categories" msgstr "" -#: ../settings/branding.rst:16 -msgid "Defines the logo of the application, shown in the login page of Zammad." +#: ../misc/variables.rst:31 +msgid "Wait, What About Custom Objects?" msgstr "" -#: ../settings/branding.rst:18 +#: ../misc/variables.rst:33 msgid "" -"Ensure to hit the \"Submit\" button after uploading the logo. Otherwise your " -"change will not be saved." +"Good point! Of course, we can't predict what objects you might create, but " +"we can give you a hint on how to put the puzzle together to get your custom " +"values." msgstr "" -#: ../settings/branding.rst:22 +#: ../misc/variables.rst:36 msgid "" -"Allows to set the default language of the Zammad instance. The here defined " -"locale mostly acts as a fallback for:" +"For this, we'll talk about the inner part of the variable (so everything " +"within ``#{}``), please put the outer part around to have a valid variable. " +"The first part of the variable name consist of the object type. Currently " +"these are:" msgstr "" -#: ../settings/branding.rst:25 -msgid "user preferences (if Zammad can't detect the users locale)" +#: ../misc/variables.rst:41 +msgid "Ticket (``ticket``)" msgstr "" -#: ../settings/branding.rst:26 -msgid "CSV output (reporting, time accounting)" +#: ../misc/variables.rst:42 +msgid "User (``user``)" msgstr "" -#: ../settings/branding.rst:30 -msgid "Define the timezone of your Zammad installation." +#: ../misc/variables.rst:43 +msgid "Organization (``organization``)" msgstr "" -#: ../settings/branding.rst:32 +#: ../misc/variables.rst:44 +msgid "Group (``group``)" +msgstr "" + +#: ../misc/variables.rst:46 msgid "" -"This does not have any effect on timings for your agents or how Zammad " -"stores date and time values." +"The second part is the name of the attribute. This is the name you define " +"during object creation and can be found within the object attribute menu at " +"any time. The first and second part of a variable is divided by a point, e." +"g.: ``ticket.number`` which will in total be ``#{ticket.number}``." msgstr "" -#: ../settings/branding.rst:35 -msgid "Changing this value has direct consequences on the following areas:" +#: ../misc/variables.rst:51 +msgid "" +"Now, in some situations it's possible that you'll need to use a third part. " +"The best example for such a situation would be a ``select`` or ``tree-" +"select`` field which will by default return the key value, not it's display " +"name. For this, just extend your variable with ``.value``. This will result " +"in ``#{ticket.select.value}``." msgstr "" -#: ../settings/branding.rst:37 -msgid ":doc:`/manage/scheduler` tasks" +#: ../misc/variables.rst:60 +msgid "Using Translated Variables" msgstr "" -#: ../settings/branding.rst:38 -msgid "search indexing (and thus reporting)" +#: ../misc/variables.rst:62 +msgid "" +"If you want to use a translated variable in triggers or schedulers, you can " +"extend the placeholder like this: ``#{t(ticket.state.name)}``. The ``t`` " +"tells Zammad to search for fitting translated strings. The used output " +"language is based on the system language of Zammad which you can set in the " +"admin panel under :doc:`/settings/branding` or based on the selected locale " +"in the trigger/scheduler edit dialog." msgstr "" -#: ../settings/branding.rst:40 -msgid "calendar subscriptions" +#: ../misc/variables.rst:69 +msgid "" +"A possible use-case: you want to send your customers updates on tickets via " +"trigger or scheduler which should include the state of the ticket. Using the " +"default ``#{ticket.state.name}`` (without the translation flag ``t()``) " +"would lead to the output of the original (english) name of the state." msgstr "" -#: ../settings/branding.rst:41 -msgid "browser printing" +#: ../misc/variables.rst:75 +msgid "Date and Time Formatting" msgstr "" -#: ../settings/branding.rst:43 +#: ../misc/variables.rst:77 msgid "" -"Please note that some of above are fallbacks in case Zammad could not detect " -"the agents timezone correctly." +"The system (trigger/scheduler selected) locale and timezone predefines a " +"default format of date and timestamp. This format is customizable by using " +"the ``dt()`` method." msgstr "" -#: ../settings/branding.rst:77 -msgid "Pretty Date" +#: ../misc/variables.rst:79 +msgid "The method arguments are as follows:" msgstr "" -#: ../settings/branding.rst:47 -msgid "" -"This setting allows you to define how Zammad should display time stamps " -"within the interface to all users." +#: ../misc/variables.rst:81 +msgid "The date or timestamp variable you want to format." msgstr "" -#: ../settings/branding.rst:50 -msgid "" -"This does not have any effect on how Zammad returns e.g. time values via " -"variables." +#: ../misc/variables.rst:82 +msgid "The output format string." msgstr "" -#: ../settings/branding.rst:77 -msgid "Choose in between the following options:" +#: ../misc/variables.rst:83 +msgid "The timezone to apply (optional)." msgstr "" -#: ../settings/branding.rst:64 -msgid "relative" -msgstr "" +#: ../misc/variables.rst:85 +#: ../system/objects/external-data-source-example.rst:23 +#, fuzzy +msgid "**Example:**" +msgstr "Primjer" -#: ../settings/branding.rst:55 +#: ../misc/variables.rst:86 msgid "" -"This timestamp shows a relative time span until it switches to a date. Over " -"time, it will change as follows:" +"``#{dt(ticket.updated_at, \"%A %Y-%m-%d %H:%M in the office\", \"Europe/" +"Berlin\")}``" msgstr "" -#: ../settings/branding.rst:58 -msgid "just now" +#: ../misc/variables.rst:87 +msgid "Monday, 2024-03-18 15:31 in the office" msgstr "" -#: ../settings/branding.rst:59 -msgid "5 minutes ago" +#: ../misc/variables.rst:89 +msgid "" +"If you want to use our example, make sure to paste the string above without " +"formatting (``CTRL+Shift+v``), otherwise it won't work." msgstr "" -#: ../settings/branding.rst:60 -msgid "3 days 1 hour ago" +#: ../misc/variables.rst:93 +msgid "The following table lists available format directives:" msgstr "" -#: ../settings/branding.rst:61 -msgid "``03/04/2022``" +#: ../misc/variables.rst:99 +msgid "Parameter" msgstr "" -#: ../settings/branding.rst:63 -msgid "Hovering the timestamp helps, you'll always get a clean timestamp then." +#: ../misc/variables.rst:102 +msgid "``%Y``" msgstr "" -#: ../settings/branding.rst:71 -msgid "absolute" +#: ../misc/variables.rst:103 +msgid "Year with 4 digits" msgstr "" -#: ../settings/branding.rst:67 -msgid "" -"This timestamp always includes the week day. For one week after creation, " -"the timestamp will not contain the date itself: Thursday 18:35." +#: ../misc/variables.rst:104 +msgid "Use ``%y`` for year with 2 digits" msgstr "" -#: ../settings/branding.rst:71 -msgid "After a week it will switch to: ``Friday 4. Mar 16:00``." +#: ../misc/variables.rst:105 +msgid "``%m``" msgstr "" -#: ../settings/branding.rst:76 -msgid "timestamp" +#: ../misc/variables.rst:106 +msgid "Month of year (as number with zero-padding)" msgstr "" -#: ../settings/branding.rst:74 -msgid "" -"This will cause Zammad to show a complete timestamp according to your locale " -"defaults. For English this could be e.g. ``2022/12/03 2:40 pm`` or for " -"German e.g. ``12.03.2022 14:40``." +#: ../misc/variables.rst:107 +msgid "Use ``%-m`` for month without zero-padding" msgstr "" -#: ../settings/branding.rst:78 -msgid "Default setting: ``relative``." +#: ../misc/variables.rst:108 +msgid "``%d``" msgstr "" -#: ../settings/security.rst:2 -msgid "Security" +#: ../misc/variables.rst:109 +msgid "Day of month (as number with zero-padding)" msgstr "" -#: ../settings/security.rst:4 -msgid "" -"For your overview we split each tab within security settings into its own " -"page:" +#: ../misc/variables.rst:110 +msgid "Use ``%e`` for day without zero-padding" msgstr "" -#: ../settings/security/base.rst:2 ../settings/system/base.rst:2 -#: ../settings/ticket.rst:8 -msgid "Base" +#: ../misc/variables.rst:111 +msgid "``%H``" msgstr "" -#: ../settings/security/base.rst:5 -msgid "New User Accounts" +#: ../misc/variables.rst:112 +msgid "Hour of day in 24h notation with zero-padding" msgstr "" -#: ../settings/security/base.rst:9 -msgid "" -"Activates the `register as a new customer` function on the login page. If " -"set to ``no`` only administrators or agents can create new accounts manually." +#: ../misc/variables.rst:113 +msgid "Use ``%k`` for hour without zero-padding" msgstr "" -#: ../settings/security/base.rst:13 ../settings/security/base.rst:38 -#: ../settings/security/base.rst:66 -msgid "Default setting: ``yes``" +#: ../misc/variables.rst:114 +msgid "``%I``" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing activated \"New User Accounts\" setting" +#: ../misc/variables.rst:115 +msgid "Hour of day in 12h notation with zero-padding" msgstr "" -#: ../settings/security/base.rst:22 +#: ../misc/variables.rst:116 msgid "" -"Deactivation of above function **does not** deactivate automatic account " -"creation! This means: If a user writes e.g. an email to Zammad and has no " -"account yet, Zammad will automatically create the account. User accounts are " -"a direct dependency of tickets and thus technically mandatory." +"Use ``%l`` for hour without zero-padding and ``%p`` / ``%P`` for meridian " +"indicator" msgstr "" -#: ../settings/security/base.rst:29 -msgid "Lost Password" +#: ../misc/variables.rst:117 +msgid "``%M``" msgstr "" -#: ../settings/security/base.rst:33 -msgid "" -"Activates the `lost password` function on the login page. If set to ``no`` " -"only administrators may change the user's password - users may update their " -"own password if they're still logged in and they have the required :doc:" -"`permission `." +#: ../misc/variables.rst:118 +msgid "Minute of hour" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing activated \"Lost Password\" setting" +#: ../misc/variables.rst:120 +msgid "``%S``" msgstr "" -#: ../settings/security/base.rst:49 -msgid "" -"With third party authentications - but especially LDAP - you may want to " -"disable this function. Zammad **will not** change third party login " -"passwords and instead set or change the local password!" +#: ../misc/variables.rst:121 +msgid "Second of Minute" msgstr "" -#: ../settings/security/base.rst:56 -msgid "Password Login" +#: ../misc/variables.rst:123 +msgid "``%A``" msgstr "" -#: ../settings/security/base.rst:60 -msgid "" -"Activates the username & password login by default and if no third-party " -"login is activated. Disabling password login on the Zammad login page only " -"takes effect if you enable any :doc:`third-party`." +#: ../misc/variables.rst:124 +msgid "Weekday name" msgstr "" -#: ../settings/security/base.rst:64 -msgid "See :doc:`third-party` for supported third-party logins." +#: ../misc/variables.rst:125 +msgid "Use ``%a`` for abbreviated name or ``%^A`` for uppercase name" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing de-activated \"Password Login\" setting" +#: ../misc/variables.rst:126 +msgid "``%B``" msgstr "" -#: ../settings/security/base.rst:77 -msgid "" -"To help administrators to overcome \"login issues\", Zammad automatically " -"offers a password request for administrator users. This allows you to adjust " -"Third-Party applications even if the login does no longer work!" +#: ../misc/variables.rst:127 +msgid "Month name" msgstr "" -#: ../settings/security/base.rst:84 -msgid "Session Timeout" +#: ../misc/variables.rst:128 +msgid "Use ``%b`` for abbreviated name" msgstr "" -#: ../settings/security/base.rst:86 -msgid "" -"All settings below by default are set to ``4 weeks``. Session Timeout " -"defines the life time of a users session. As soon as it's reached, Zammad " -"will automatically log off the session in question." +#: ../misc/variables.rst:129 +msgid "``%U``" msgstr "" -#: ../settings/security/base.rst:91 -msgid "" -"Zammad takes the highest value set assigned for the user based on the " -"permissions." +#: ../misc/variables.rst:130 +msgid "Week number of current year" msgstr "" -#: ../settings/security/base.rst:94 -msgid "``admin``" +#: ../misc/variables.rst:131 +msgid "Use ``%W`` for a different calculation method" msgstr "" -#: ../settings/security/base.rst:96 -msgid "``ticket.customer``" +#: ../misc/variables.rst:134 +msgid "" +"We support the known format directives for the Ruby built-in method " +"``strftime`` of the ``DateTime`` class. For more information, see `here " +"`_." msgstr "" -#: ../settings/security/base.rst:97 -msgid "``default`` (fallback if user doesn't have above permissions set)" +#: ../misc/variables/article.rst:2 +msgid "Articles" msgstr "" -#: ../settings/security/base.rst:99 +#: ../misc/variables/article.rst:4 ../misc/variables/config.rst:4 +#: ../misc/variables/current-user.rst:4 ../misc/variables/ticket.rst:4 msgid "" -"All settings act independently from each other allowing you to disable the " -"timeouts for e.g. admins, but not agents." +"If you're missing variables or are not sure if something is not working as " +"expected, feel free to ask over at the `Community `_." msgstr "" -#: ../settings/security/base.rst:115 -#: ../system/integrations/checkmk/api-reference.rst:13 -msgid "Example" -msgstr "Primjer" +#: ../misc/variables/article.rst:6 +msgid "" +"Below you can find all available ticket article-based variables within " +"Zammad. These can be called via triggers for example. If you're unsure if " +"Zammad does support variables at the point you're at, you can try to type " +"``::`` to check." +msgstr "" -#: ../settings/security/base.rst:107 -msgid "Let's suppose you configured the following session timeouts" +#: ../misc/variables/article.rst:9 ../misc/variables/config.rst:9 +#: ../misc/variables/ticket.rst:9 +msgid "" +"The below list gives you an example what kind of data you can expect, it's " +"not intended to explain the data itself." msgstr "" -#: ../settings/security/base.rst:104 -msgid "default: 3 weeks" +#: ../misc/variables/article.rst:11 +msgid "Article Variables" msgstr "" -#: ../settings/security/base.rst:105 -msgid "admin: 2 weeks" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "name" msgstr "" -#: ../settings/security/base.rst:106 -msgid "ticket.agent: 4 weeks" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "variable" msgstr "" -#: ../settings/security/base.rst:107 -msgid "ticket.customer: 1 week" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "example" msgstr "" -#: ../settings/security/base.rst:115 -msgid "This results in the following situations" +#: ../misc/variables/article.rst:1 +msgid "Article > Cc" msgstr "" -#: ../settings/security/base.rst:110 -msgid "a user with ``admin`` permission will have a timeout of 2 weeks" +#: ../misc/variables/article.rst:1 +msgid "``#{article.cc}``" msgstr "" -#: ../settings/security/base.rst:111 -msgid "" -"a user with ``admin`` and ``ticket.agent`` permissions will have a timeout " -"of 2 weeks" +#: ../misc/variables/article.rst:1 +msgid "``jdoe@example.com, company@example.com``" msgstr "" -#: ../settings/security/base.rst:113 -msgid "" -"a user with ``ticket.customer`` permission will have a timeout of 1 week" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Address" msgstr "" -#: ../settings/security/base.rst:115 -msgid "" -"a user with neither ``admin``, ``ticket.agent`` nor ``ticket.customer`` " -"permissions will have a timeout of 3 weeks" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.address}``" msgstr "" -#: ../settings/security/password.rst:4 -msgid "" -"This section allows you to define password requirements for the local user " -"accounts." +#: ../misc/variables/article.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:9 -msgid "" -"Zammad does **not** allow you to change your LDAP password, instead, it will " -"set a password in its local database which might confuse your users. This " -"might be addressed in the future by `#1169 `_." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Department" msgstr "" -#: ../settings/security/password.rst:14 -msgid "**Exception for admins**" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.department}``" msgstr "" -#: ../settings/security/password.rst:16 -msgid "" -"Please note that below password policies *do not* affect administrators " -"setting passwords on user accounts. While this seems strange and not safe we " -"believe that an administrator knowing an user's password is insecure as well." +#: ../misc/variables/article.rst:1 +msgid "``Sales`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:21 -msgid "The suggested workflow is either:" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Email" msgstr "" -#: ../settings/security/password.rst:23 -msgid "" -"to use third party logins to not require local passwords at all **- or -**" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.email}``" msgstr "" -#: ../settings/security/password.rst:25 -msgid "to require your *user to reset the password* upon first login." +#: ../misc/variables/article.rst:1 +msgid "``jdoe@example.com``" msgstr "" -#: ../settings/security/password.rst:27 -msgid "" -"This way administrators are not required to set a user's password at all!" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Fax" msgstr "" -#: ../settings/security/password.rst:31 -msgid "Maximum Failed Logins" -msgstr "" - -#: ../settings/security/password.rst:33 -msgid "" -"You can choose a value between ``4`` and ``20``. This defines how often a " -"login to a user account may fail until Zammad will lock it. Your users can " -"always use the \"forgot password\" function to change their password and " -"unlock their account." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.fax}``" msgstr "" -#: ../settings/security/password.rst:38 -msgid "The default value is ``10``." +#: ../misc/variables/article.rst:1 +msgid "``+4930123456789`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:42 -msgid "Beside changing the user's password, you can also unlock accounts via" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Firstname" msgstr "" -#: ../settings/security/password.rst:44 -msgid ":ref:`user management list `" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.firstname}``" msgstr "" -#: ../settings/security/password.rst:45 -msgid ":docs:`console `" +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Joe`` or empty if not set" msgstr "" -#: ../settings/security/password.rst:46 -msgid ":docs:`API `" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Lastname" msgstr "" -#: ../settings/security/password.rst:50 -msgid "Failed logins via LDAP no longer lock accounts." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.lastname}``" msgstr "" -#: ../settings/security/password.rst:53 -msgid "2 Lower Case And 2 Upper Case Characters" +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +#: ../misc/variables/ticket.rst:1 +msgid "``Doe`` or empty if not set" msgstr "" -#: ../settings/security/password.rst:55 -msgid "" -"You can add complexity to passwords by enforcing at least 2 upper and lower " -"case characters." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Login" msgstr "" -#: ../settings/security/password.rst:58 ../settings/security/password.rst:83 -msgid "The default value is ``no``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.login}``" msgstr "" -#: ../settings/security/password.rst:62 -msgid "Minimum Length" +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +#: ../misc/variables/ticket.rst:1 +msgid "``jdoe``" msgstr "" -#: ../settings/security/password.rst:64 -msgid "" -"This defines the minimum password length required for users to provide (from " -"``4`` to ``20``)." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Mobile" msgstr "" -#: ../settings/security/password.rst:67 -msgid "The default value is ``6``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.mobile}``" msgstr "" -#: ../settings/security/password.rst:71 -msgid "Digit Required" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Note" msgstr "" -#: ../settings/security/password.rst:73 -msgid "This enforces your users to use at least one digit within the password." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.note}``" msgstr "" -#: ../settings/security/password.rst:75 -msgid "The default value is ``yes``." +#: ../misc/variables/article.rst:1 +msgid "``Some note about user`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:78 -msgid "Special Character Required" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Phone" msgstr "" -#: ../settings/security/password.rst:80 -msgid "" -"This setting allows you to improve your password quality even more by " -"enforcing the password to contain at least one special character." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.phone}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:2 -msgid "SSL Certificates" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > VIP" msgstr "" -#: ../settings/security/ssl-certificates.rst:7 -msgid "" -"Zammad offers the possibility to upload custom certificates and custom " -"Certificate Authority (CA) certificates. This can be useful if you want to " -"connect Zammad the secure way to other systems which are using custom " -"certificates." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.vip}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:12 -msgid "" -"An example usecase might be: You have an internal LDAP server that is not " -"accessible from the internet, and you want a SSL-encrypted connection, using " -"a custom certificate." +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +msgid "``true`` or ``false``" msgstr "" -#: ../settings/security/ssl-certificates.rst:19 -msgid "" -"You should have an existing custom certificate file and/or a custom CA " -"certificate file, which you want to add to Zammad. As filetype ``.crt`` is " -"supported and the certificate format has to be PEM (Base64 ASCII)." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Web" msgstr "" -#: ../settings/security/ssl-certificates.rst:25 -msgid "" -"When you import a custom CA certificate, all certificates generated with " -"this are trusted. This can be useful if you have more than one system/" -"certificate you want to connect to and the certificates are issued from the " -"same custom CA." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.web}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:31 -msgid "Add a Certificate" +#: ../misc/variables/article.rst:1 +msgid "``https://zammad.com`` or empty if not set in user object" msgstr "" -#: ../settings/security/ssl-certificates.rst:33 -msgid "" -"To add a custom certificate or a custom CA certificate, head over to the " -"Admin panel > Settings > Security > SSL Certificates. Here you can find a " -"\"Add SSL Certificate\" button. In the dialog you can either select a " -"certificate file or paste the content of the certificate:" +#: ../misc/variables/article.rst:1 +msgid "Article > Created" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate adding dialog" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_at}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:43 -msgid "" -"After selecting a file or pasting the content of the certificate, click on " -"the \"Add\" button to finally upload it to Zammad. Then, the certificates " -"are immediately effective, no restart or similar required." +#: ../misc/variables/article.rst:1 +msgid "``2019-10-08 15:24:47 UTC``" msgstr "" -#: ../settings/security/ssl-certificates.rst:49 -msgid "" -"Please note that only single certificate files are supported. That means if " -"you want to import a certificate / CA certificate, it must contain **only " -"one** certificate." +#: ../misc/variables/article.rst:1 +msgid "Article > From" msgstr "" -#: ../settings/security/ssl-certificates.rst:54 -msgid "Certificate Overview" +#: ../misc/variables/article.rst:1 +msgid "``#{article.from}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:56 +#: ../misc/variables/article.rst:1 msgid "" -"After you added a certificate, you can see a table with information for each " -"added certificate:" +"``Joe Doe `` may differ, depends on ``FROM`` of send mail" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing table of added certificates" +#: ../misc/variables/article.rst:1 +msgid "Article > Sender > Name" msgstr "" -#: ../settings/security/ssl-certificates.rst:64 -msgid "" -"Here you can download the certificate or delete it, if you don't need it " -"anymore." +#: ../misc/variables/article.rst:1 +msgid "``#{article.sender.name}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:68 -msgid "Deleting Certificates" +#: ../misc/variables/article.rst:1 +msgid "``Customer``, ``Agent`` or ``System``" msgstr "" -#: ../settings/security/ssl-certificates.rst:70 -msgid "" -"If you want to delete a specific certificate, you can do it by clicking on " -"the menu in the actions column and selecting delete:" +#: ../misc/variables/article.rst:1 +msgid "Article > Subject" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate deletion button" +#: ../misc/variables/article.rst:1 +msgid "``#{article.subject}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:79 -msgid "Downloading Certificates" +#: ../misc/variables/article.rst:1 +msgid "``My amazing subject``" msgstr "" -#: ../settings/security/ssl-certificates.rst:81 -msgid "" -"If you want to download your certificates, you can do this as well via " -"corresponding action buttons." +#: ../misc/variables/article.rst:1 +msgid "Article > Text" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate download button" +#: ../misc/variables/article.rst:1 +msgid "``#{article.body}``" msgstr "" -#: ../settings/security/third-party.rst:13 -msgid "Login Providers" +#: ../misc/variables/article.rst:1 +msgid "``Test`` without formatting (plain)" msgstr "" -#: ../settings/security/third-party.rst:2 -msgid "Third-Party Applications" +#: ../misc/variables/article.rst:1 +msgid "Article > TicketID" msgstr "" -#: ../settings/security/third-party.rst:4 -msgid "" -"Third party authentication is a great way to help your users to login to " -"Zammad more easily. If the account is yet unknown, Zammad will create a new " -"user automatically, without the user needed to interact (e.g. type in his " -"name). Another big advantage of this feature is that your user doesn't need " -"to remember another password." +#: ../misc/variables/article.rst:1 +msgid "``#{article.ticket_id}``" msgstr "" -#: ../settings/security/third-party.rst:10 -msgid "" -"You can deactivate logging in via :ref:`security_password_login` if any of " -"the mentioned authentication providers are enabled in your instance." +#: ../misc/variables/article.rst:1 +msgid "``1`` (not ticket number)" msgstr "" -#: ../settings/security/third-party.rst:27 -msgid "" -"We're currently missing documentation for the following login providers:" +#: ../misc/variables/article.rst:1 +msgid "Article > To" msgstr "" -#: ../settings/security/third-party.rst:29 -msgid "LinkedIn" +#: ../misc/variables/article.rst:1 +msgid "``#{article.to}``" msgstr "" -#: ../settings/security/third-party.rst:30 -msgid "Weibo" +#: ../misc/variables/article.rst:1 +msgid "``helpdesk@example.com``" msgstr "" -#: ../settings/security/third-party.rst:35 -#, fuzzy -msgid "Automatic Account Link on Initial Logon" -msgstr ":doc:`accounts/email-notification`" +#: ../misc/variables/article.rst:1 +msgid "Article > Type > Name" +msgstr "" -#: ../settings/security/third-party.rst:37 -msgid "" -"In general there's two possible options for Zammad on how to deal with " -"already known users as they try to authenticate against a third-party " -"application. By default, Zammad will not automatically link \"unknown\" " -"authentication providers to existing accounts." +#: ../misc/variables/article.rst:1 +msgid "``#{article.type.name}``" msgstr "" -#: ../settings/security/third-party.rst:42 +#: ../misc/variables/article.rst:1 msgid "" -"This means that the user has to manually link authentication providers to " -"their accounts (for more about this :user-docs:`consult the user " -"documentation `)." +"``email`` (`list of article types `_)" msgstr "" -#: ../settings/security/third-party.rst:46 -msgid "" -"Sometimes this doesn't come in handy as this also means you'll receive error " -"messages about \"email address being in use already\" for (yet) unknown " -"third-party authentication methods." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Address" msgstr "" -#: ../settings/security/third-party.rst:50 -msgid "" -"If you want to allow your users to always be able to log in, no matter what, " -"you may want to enable ``Automatic account link on initial logon``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.address}``" msgstr "" -#: ../settings/security/third-party.rst:None -msgid "" -"Screenshot highlighting the \"Automatic account link on initial logon\"\n" -"setting" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Department" msgstr "" -#: ../settings/security/third-party.rst:60 -#, fuzzy -msgid "Automatic Account Linking Notification" -msgstr ":doc:`accounts/email-notification`" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.department}``" +msgstr "" -#: ../settings/security/third-party.rst:64 -msgid "" -"To improve security and your users awareness, you can enable Zammad to " -"notify your users when a new third-party application has been linked to " -"their account." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Email" msgstr "" -#: ../settings/security/third-party.rst:68 -msgid "" -"This notification is sent out once per third-party application. Zammad does " -"also mention the method used, e.g.: ``Microsoft``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.email}``" msgstr "" -#: ../settings/security/third-party.rst:71 -msgid "By default this setting is not active (set to ``no``)." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Fax" msgstr "" -#: ../settings/security/third-party.rst:0 -msgid "" -"Screenshot showing sample notification mail after initial\n" -"third-party linking" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.fax}``" msgstr "" -#: ../settings/security/third-party.rst:85 -msgid "" -"This notification is only sent if the account in question already exists. If " -"the login via the third-party also creates the missing account, the " -"notification will be skipped." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Firstname" msgstr "" -#: ../settings/security/third-party.rst:89 -msgid "This means it only affects:" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.firstname}``" msgstr "" -#: ../settings/security/third-party.rst:91 -msgid "manual account linking within the third-party page of the users profile" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Lastname" msgstr "" -#: ../settings/security/third-party.rst:92 -msgid "" -"logging into an existing local account by utilizing the *automatic account " -"link on initial logon* functionality" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.lastname}``" msgstr "" -#: ../settings/security/third-party.rst:None -msgid "" -"Screenshot showing the \"automatic account linking notification\"\n" -"setting" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Login" msgstr "" -#: ../settings/security/third-party.rst:100 -msgid "No User Creation on Logon" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.login}``" msgstr "" -#: ../settings/security/third-party.rst:102 -msgid "" -"By default, Zammad will create a new user account if the user logs in via a " -"third-party application and the account doesn't exist yet." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Mobile" msgstr "" -#: ../settings/security/third-party.rst:105 -msgid "" -"If you want to prevent Zammad from creating new accounts on logon, you can " -"disable this feature by setting ``No user creation on logon`` to ``yes``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.mobile}``" msgstr "" -#: ../settings/security/third-party.rst:None -msgid "Screenshot showing the \"no user creation on logon\" setting" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Note" msgstr "" -#: ../settings/security/third-party/facebook.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via Facebook To do " -"so, you need to follow these steps:" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.note}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:9 -msgid "Register Facebook App" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Phone" msgstr "" -#: ../settings/security/third-party/facebook.rst:11 -msgid "" -"Visit [https://developers.facebook.com/apps/] and click on \"Add a new App\"" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.phone}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "initial page" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > VIP" msgstr "" -#: ../settings/security/third-party/facebook.rst:17 -msgid "After that enter the app settings" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.vip}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "Create App" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Web" msgstr "" -#: ../settings/security/third-party/facebook.rst:22 -msgid "Navigate to \"Settings\" and fill in this infromation" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.web}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "App Settings" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated" msgstr "" -#: ../settings/security/third-party/facebook.rst:27 -msgid "Navigate to app review and Check \"Make [appname] public?\"" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_at}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "App Review" +#: ../misc/variables/article.rst:1 +msgid "Article > Visibility" msgstr "" -#: ../settings/security/third-party/facebook.rst:35 -msgid "Configure Zammad as Facebook App" +#: ../misc/variables/article.rst:1 +msgid "``#{article.internal}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:37 -msgid "" -"Navigate to \"Admin -> Security -> Third Party Applications\" and enter the " -"App ID and the App Secret. You can find this Key in the Dashbard of your " -"Facebok app." +#: ../misc/variables/article.rst:1 +msgid "``false`` or ``true`` (false if not internal)" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "Zammad Configuration" +#: ../misc/variables/article.rst:1 +msgid "Article Text as HTML (not referenced)" msgstr "" -#: ../settings/security/third-party/facebook.rst:44 -#: ../settings/security/third-party/github.rst:43 -#: ../settings/security/third-party/gitlab.rst:46 -msgid "" -"Now you can link accounts via \"Avatar -> Profile -> Link Accounts\" or " -"login via Zammad login page." +#: ../misc/variables/article.rst:1 +msgid "``#{article.body_as_html}``" msgstr "" -#: ../settings/security/third-party/github.rst:2 -#: ../system/integrations/github.rst:2 -msgid "GitHub" +#: ../misc/variables/article.rst:1 +msgid "``Test`` with formatting" msgstr "" -#: ../settings/security/third-party/github.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via GitHub. To " -"activate the quick login you need to enable OAuth for GitHub." +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "Ticket > Article#" msgstr "" -#: ../settings/security/third-party/github.rst:8 -msgid "Register GitHub App" +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "``#{ticket.article_count}``" msgstr "" -#: ../settings/security/third-party/github.rst:10 -msgid "" -"Visit https://www.github.com/settings/applications/new and enter the app " -"settings. As callback URL enter \"https://zammad_host/auth/github/callback\" " -"where zammad_host has to be replaced with your Zammad FQDN" +#: ../misc/variables/article.rst:1 +msgid "``1`` number of ticket articles" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "Register OAuth app on www.github.com" +#: ../misc/variables/config.rst:2 +msgid "Config" msgstr "" -#: ../settings/security/third-party/github.rst:19 -msgid "Configure Zammad as GitHub App" +#: ../misc/variables/config.rst:6 +msgid "" +"Below you'll find config related variables. These hold useful configuration " +"information that you can use within e.g. triggers to show necessary " +"information to your customer." msgstr "" -#: ../settings/security/third-party/github.rst:21 -msgid "" -"Enter the \"APP ID\" and the \"APP SECRET\" from the GitHub OAUTH " -"Applications Dashboard" +#: ../misc/variables/config.rst:11 +msgid "Config Variables" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub config in Zammad admin interface" +#: ../misc/variables/config.rst:1 +msgid "Config > Fully Qualified Domain Name" msgstr "" -#: ../settings/security/third-party/github.rst:28 -msgid "" -"After you configured the GitHub credentials and activated the login method, " -"you should see a new icon on the login page." +#: ../misc/variables/config.rst:1 +msgid "``#{config.fqdn}``" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub logo on login page" +#: ../misc/variables/config.rst:1 +msgid "``zammad.example.com``" msgstr "" -#: ../settings/security/third-party/github.rst:34 -msgid "" -"If you click on the icon you will be redirected to GitHub and see something " -"similar to this:" +#: ../misc/variables/config.rst:1 +msgid "Config > HTTP type" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub oauth page" +#: ../misc/variables/config.rst:1 +msgid "``#{config.http_type}``" msgstr "" -#: ../settings/security/third-party/github.rst:40 -#: ../settings/security/third-party/gitlab.rst:42 -msgid "" -"When you grant the access you will be redirected to your Zammad instance and " -"logged in as a customer." +#: ../misc/variables/config.rst:1 +msgid "``https`` or ``http``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:2 -msgid "Gitlab" +#: ../misc/variables/config.rst:1 +msgid "Config > Organization" msgstr "" -#: ../settings/security/third-party/gitlab.rst:4 +#: ../misc/variables/config.rst:1 +msgid "``#{config.organization}``" +msgstr "" + +#: ../misc/variables/config.rst:1 msgid "" -"It is possible to create a quick login for your helpdesk via Gitlab. To " -"activate the quick login you need to enable OAuth for Gitlab." +"``Zammad GmbH`` value set in `Branding `_" msgstr "" -#: ../settings/security/third-party/gitlab.rst:8 -msgid "Register Gitlab App" +#: ../misc/variables/config.rst:1 +msgid "Config > Product Name" msgstr "" -#: ../settings/security/third-party/gitlab.rst:10 -msgid "To register an app in Gitlab open your profile and select applications." +#: ../misc/variables/config.rst:1 +msgid "``#{config.product_name}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:12 +#: ../misc/variables/config.rst:1 msgid "" -"As callback URL enter \"https://zammad-fqdn/auth/gitlab/callback\" where " -"zammad-fqdn has to be replaced with your Zammad FQDN" +"``Helpdesk`` value set in `Branding `_" msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Register OAuth app on gitlab instance" +#: ../misc/variables/config.rst:1 +msgid "Config > SystemID" msgstr "" -#: ../settings/security/third-party/gitlab.rst:18 -msgid "Just select *read_user* under scopes as in the screenshot and save it." +#: ../misc/variables/config.rst:1 +msgid "``#{config.system_id}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:21 -msgid "Configure Zammad as Gitlab App" +#: ../misc/variables/config.rst:1 +msgid "``31`` (value between 1 and 99)" msgstr "" -#: ../settings/security/third-party/gitlab.rst:23 -msgid "" -"Enter the \"APP ID\" and the \"APP SECRET\" from the Gitlab OAUTH " -"Applications Dashboard and your Gitlab-URL in the \"SITE\" field." +#: ../misc/variables/config.rst:1 +msgid "Config > Ticket Hook" msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab config in Zammad admin interface" +#: ../misc/variables/config.rst:1 +msgid "``#{config.ticket_hook}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:30 -msgid "" -"After you configured the Gitlab credentials and activated the login method, " -"you should see a new icon on the login page." +#: ../misc/variables/config.rst:1 +msgid "``Ticket#``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab logo on login page" +#: ../misc/variables/current-user.rst:2 +msgid "Current User" msgstr "" -#: ../settings/security/third-party/gitlab.rst:36 +#: ../misc/variables/current-user.rst:6 msgid "" -"If you click on the icon you will be redirected to Gitlab and see something " -"similar to this:" +"Current user variables always return values of the current user that caused " +"e.g. a trigger to run." msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab oauth page" +#: ../misc/variables/current-user.rst:8 +msgid "" +"Due to the above fact, these variables are often not (yet) set or available " +"for usage." msgstr "" -#: ../settings/security/third-party/google.rst:4 +#: ../misc/variables/current-user.rst:10 msgid "" -"With some easy and fast steps, you can enable Zammad to authenticate your " -"users via Google." +"In situations where e.g. schedulers or triggers run, this most likely is " +"nothing you want to use." msgstr "" -#: ../settings/security/third-party/google.rst:8 -msgid "Register a Google App" +#: ../misc/variables/current-user.rst:13 +msgid "Current User Variables" msgstr "" -#: ../settings/security/third-party/google.rst:10 -msgid "" -"First of all, we need to create a new project - you can skip this step if " -"you already have one." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Address" msgstr "" -#: ../settings/security/third-party/google.rst:15 -msgid "" -"Use this link to create a new project: https://console.cloud.google.com/" -"projectcreate" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.address}``" msgstr "" -#: ../settings/security/third-party/google.rst:18 -msgid "" -"Now expand the menu, expand \"APIs & Services\" and select \"Credentials\". " -"Go to the tab \"OAuth consent screen\" first and ensure to fill in the " -"requested information - without doing so you can't create credentials!" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set" msgstr "" -#: ../settings/security/third-party/google.rst:None -msgid "Creating a consent screen" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Avatar" msgstr "" -#: ../settings/security/third-party/google.rst:25 -msgid "" -"After filling in and saving the consent screen information, you can go to " -"the \"Credentials\" tab and create new \"OAuth client ID\"-Credentials." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/google.rst:28 -msgid "" -"Fill in the necessary information as follows and replace ``zammad_host`` " -"with your FQDN:" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "avatar picture with width and height in pixel (e.g. 60,60)" msgstr "" -#: ../settings/security/third-party/google.rst:31 -msgid "**Application type** ``[x] Web application``" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created at" msgstr "" -#: ../settings/security/third-party/google.rst:34 -msgid "**Authorized JavaScript origins** ``https://zammad_host/``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_at}``" msgstr "" -#: ../settings/security/third-party/google.rst:37 -msgid "" -"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" -"callback``" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC``" msgstr "" -#: ../settings/security/third-party/google.rst:None -msgid "Adding a new OAuth client ID" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Address" msgstr "" -#: ../settings/security/third-party/google.rst:43 -msgid "" -"After creating the credentials, go to your Zammad installation and navigate " -"to \"Admin > Security > Third Party Applications\" > Google. Enter your " -"Client ID and Client secret here." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.address}``" msgstr "" -#: ../settings/security/third-party/google.rst:None -msgid "Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Avatar" msgstr "" -#: ../settings/security/third-party/google.rst:50 -msgid "After submitting, the login via Google can be used." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:2 -msgid "Microsoft" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Department" msgstr "" -#: ../settings/security/third-party/microsoft.rst:4 -msgid "" -"Zammad's Microsoft connection allows your users with Microsoft accounts to " -"login. This works for Azure users as well and can be an alternative to :doc:" -"`/system/integrations/ldap/index`." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.department}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:10 -msgid "" -"This documentation part does not cover our :doc:`📧 Microsoft 365 email " -"channel `." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Sales`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screenshot showing Microsoft login button on Zammad login screen." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Email" msgstr "" -#: ../settings/security/third-party/microsoft.rst:30 -#: ../settings/security/third-party/microsoft.rst:53 -msgid "Supported account types:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.email}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:22 -msgid "" -"Please note that Zammad only supports these account types (App dependent):" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``jdoe@customer.tld``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:35 -msgid "Avatars of signing in users:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Fax" msgstr "" -#: ../settings/security/third-party/microsoft.rst:33 -msgid "" -"Zammad currently ignores user avatars. If the user is registered with e.g. " -"Gravatar, Zammad will fetch the avatar from there if enabled. See :doc:" -"`Zammad Image Service ` for more." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.fax}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:38 -msgid "Step 1 - Register a Microsoft App for Zammad" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``004930123464789`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:40 -msgid "" -"Login to the `Microsoft Azure Portal `_ and " -"navigate to App registrations to create a new app. Provide the requested " -"information as follows and register your app." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Firstname" msgstr "" -#: ../settings/security/third-party/microsoft.rst:46 -msgid "Name:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.firstname}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:45 -msgid "" -"Any meaningful name fitting, this name will be displayed to users trying to " -"authenticate with this app." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``John`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:49 -msgid "Choose one of the above mentioned account types (see Limitations)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Lastname" msgstr "" -#: ../settings/security/third-party/microsoft.rst:51 -msgid "" -"The correct account type depends on your use case. If you want to use the " -"authentication internal only, choose the first option. If you're unsure, use " -"the \"Help me choose...\" link." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.lastname}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:58 -msgid "Redirect URI (optional):" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Login" msgstr "" -#: ../settings/security/third-party/microsoft.rst:56 -msgid "" -"Select web and provide your callback URL. The callback URL looks like this: " -"``https://zammad.domain.tld/auth/microsoft_office365/callback``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.login}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to register a Microsoft app" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Mobile" msgstr "" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "Within **API permissions** add the following permissions:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.mobile}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:69 -msgid "``User.Read``" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``0049176123456789`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "Contacts" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Note" msgstr "" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "``Contacts.Read``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.note}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:73 -msgid "" -"You can find these permissions within *Microsoft Graph → Delegated " -"permissions*." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Some note to this user`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to add required API permissions" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Phone" msgstr "" -#: ../settings/security/third-party/microsoft.rst:80 -msgid "" -"Within **Certificates & secrets** create a new client secret. Note down the " -"returned secret **value** for later. **Do not** use the secret ID!" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.phone}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to create a new app secret" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``004930123456789`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:88 -msgid "" -"From **Overview** copy your apps *Application (client) ID*. If you're using " -"a single tenant app, please also copy *Directory (tenant) ID*. You now have " -"all required information for Zammad." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > VIP" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to retreive application client and tenant IDs" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.vip}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:98 -msgid "Step 2 - Add App Credentials to Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Web" msgstr "" -#: ../settings/security/third-party/microsoft.rst:100 -msgid "" -"Navigate to Security > Third-party Applications (Tab) within Zammad's admin " -"settings. Scroll down to the section *Authentication via Microsoft* and fill " -"in the required information." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.web}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:105 -msgid "App ID:" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``https://zammad.org`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:105 -msgid "This is your *Application (client) ID*." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Department" msgstr "" -#: ../settings/security/third-party/microsoft.rst:108 -msgid "App secret:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.department}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:108 -msgid "This is your *client secret* (value)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Email" msgstr "" -#: ../settings/security/third-party/microsoft.rst:113 -msgid "App Tenant ID:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.email}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:111 -msgid "" -"**optional** only required for apps that use account type *Accounts in this " -"organizational directory only (Default Directory only - Single tenant).*" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Fax" msgstr "" -#: ../settings/security/third-party/microsoft.rst:115 -msgid "" -"Apply your settings by pressing submit and activate *Authentication via " -"Microsoft*." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.fax}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "" -"Screencast showing how to add app credentials and activating the\n" -"authentication method" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Firstname" msgstr "" -#: ../settings/security/third-party/saml.rst:2 -msgid "SAML" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.firstname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:4 -msgid "" -"Connect your SAML (Security Assertion Markup Language) identity provider as " -"a single sign-on (SSO) method." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Lastname" msgstr "" -#: ../settings/security/third-party/saml.rst:7 -msgid "" -"SAML is an open standard for SSO authentication (among other things). Sign-" -"ins are shared across multiple **service providers** and managed by a " -"central **identity provider** (IdP)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.lastname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:11 -msgid "" -"In this case, the service provider is Zammad, and the IdP is a software " -"service that you either host or subscribe to (*e.g.,* `Keycloak `_, `Redhat SSO Server `_, `ADFS `_, or `Okta `_)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Login" msgstr "" -#: ../settings/security/third-party/saml.rst:18 -msgid "" -"This guide assumes you are already using SAML within your organization (i." -"e., that your IdP is fully set up)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.login}``" msgstr "" -#: ../settings/security/third-party/saml.rst:21 -msgid "" -"Please note: Our instructions are based on connecting Zammad with Keycloak." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Mobile" msgstr "" -#: ../settings/security/third-party/saml.rst:25 -msgid "Step 1: Configure Your IdP" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.mobile}``" msgstr "" -#: ../settings/security/third-party/saml.rst:28 -msgid "Add Zammad as a Client/App" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Note" msgstr "" -#: ../settings/security/third-party/saml.rst:30 -msgid "" -"Import Zammad into your IdP using the XML configuration found at ``https://" -"your.zammad.domain/auth/saml/metadata``." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.note}``" msgstr "" -#: ../settings/security/third-party/saml.rst:33 -msgid "" -"If your IdP doesn't support XML import, you will have to configure Zammad as " -"a new client/app manually using the above XML metadata file for reference." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Domain based assignment" msgstr "" -#: ../settings/security/third-party/saml.rst:36 -msgid "For instance, when you see this tag:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.domain_assignment}``" msgstr "" -#: ../settings/security/third-party/saml.rst:42 -msgid "" -"Set the **Assertion Consumer Service Binding URL** (sometimes also listed as " -"**Valid Redirect URIs**) to ``http://your.zammad.domain/auth/saml/callback``." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Domain" msgstr "" -#: ../settings/security/third-party/saml.rst:47 -msgid "Set Up User Attribute Mapping" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.domain}``" msgstr "" -#: ../settings/security/third-party/saml.rst:49 -msgid "" -"Zammad requests the following user attributes (or “properties”) from the IdP:" +#: ../misc/variables/current-user.rst:1 +msgid "``zammad.com`` or empty if not set" msgstr "" -#: ../settings/security/third-party/saml.rst:51 -msgid "Email address (``email``)" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Name" msgstr "" -#: ../settings/security/third-party/saml.rst:52 -msgid "Full name (``name``)" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.name}``" msgstr "" -#: ../settings/security/third-party/saml.rst:53 -msgid "Given name (``first_name``)" +#: ../misc/variables/current-user.rst:1 +msgid "``Zammad GmbH``" msgstr "" -#: ../settings/security/third-party/saml.rst:54 -msgid "Family name (``last_name``)" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Note" msgstr "" -#: ../settings/security/third-party/saml.rst:56 -msgid "" -"You may need to set up “mappers” (or “mappings”) to tell your IdP how user " -"attributes in SAML correspond to those in Zammad. For a more detailed " -"breakdown, refer to the XML metadata file referenced in the previous section." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.note}``" msgstr "" -#: ../settings/security/third-party/saml.rst:62 -msgid "Per-IdP Instructions" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``A note to the organization of the user`` or empty if not set" msgstr "" -#: ../settings/security/third-party/saml.rst:102 -msgid "Keycloak" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Shared organization" msgstr "" -#: ../settings/security/third-party/saml.rst:65 -msgid "" -"**To add Zammad as a client,** save the XML configuration to disk (``https://" -"your.zammad.domain/auth/saml/metadata``) and use **Clients > Clients list > " -"Import client** in the Keycloak admin panel." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.shared}``" msgstr "" -#: ../settings/security/third-party/saml.rst:70 -msgid "" -"To help Zammad **match its own user accounts to Keycloak users**, create a " -"user attribute (or “property”) mapper. In **Clients list**, click on your " -"newly created Client ID, choose the tab **Client scopes** and click on the " -"link which refers to your Zammad instance. Choose **Add mapper > By " -"configuration > User Property** and create a mapper with the following " -"entries:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > VIP" msgstr "" -#: ../settings/security/third-party/saml.rst:78 -msgid "**Name**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.vip}``" msgstr "" -#: ../settings/security/third-party/saml.rst:80 -msgid "**Mapper Type**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Phone" msgstr "" -#: ../settings/security/third-party/saml.rst:81 -msgid "``User Property``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.phone}``" msgstr "" -#: ../settings/security/third-party/saml.rst:82 -msgid "**Property**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated at" msgstr "" -#: ../settings/security/third-party/saml.rst:83 -msgid "``emailAddress``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_at}``" msgstr "" -#: ../settings/security/third-party/saml.rst:84 -msgid "**SAML Attribute Name**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Address" msgstr "" -#: ../settings/security/third-party/saml.rst:86 -msgid "**SAML Attribute NameFormat**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.address}``" msgstr "" -#: ../settings/security/third-party/saml.rst:87 -msgid "``basic``" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Avatar" msgstr "" -#: ../settings/security/third-party/saml.rst:89 -msgid "" -"In the example above, we're telling Zammad that whenever it receives a SAML " -"login request, it should take the ``email`` property from Keycloak, look for " -"a Zammad user with the same ``email`` attribute, and create a new session " -"for that user." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/saml.rst:95 -msgid "" -"If your Keycloak users' email addresses are stored on another property (*e." -"g.,* ``username``), adjust accordingly." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Department" msgstr "" -#: ../settings/security/third-party/saml.rst:98 -msgid "" -"Back in **Settings**, enter the Client ID (``https://your.zammad.domain/auth/" -"saml/metadata``) in the field **Master SAML Processing URL**." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.department}``" msgstr "" -#: ../settings/security/third-party/saml.rst:101 -msgid "You also need to enable **Sign assertions**." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Email" msgstr "" -#: ../settings/security/third-party/saml.rst:105 -msgid "Step 2: Configure Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.email}``" msgstr "" -#: ../settings/security/third-party/saml.rst:107 -msgid "" -"Enable SAML and enter your IdP's details in the Admin Panel under **Settings " -"> Security > Third Party Applications > Authentication via SAML**:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Fax" msgstr "" -#: ../settings/security/third-party/saml.rst:None -msgid "Example configuration of SAML part 1" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.fax}``" msgstr "" -#: ../settings/security/third-party/saml.rst:119 -msgid "Display name" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Firstname" msgstr "" -#: ../settings/security/third-party/saml.rst:116 -msgid "" -"Allows you to define a custom button name for SAML. This helps your users to " -"understand better what the button on the login page does." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.firstname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:119 -msgid "Defaults to ``SAML``." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Lastname" msgstr "" -#: ../settings/security/third-party/saml.rst:123 -msgid "IDP SSO target URL" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.lastname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:122 -msgid "" -"This is the target URL Zammad shall redirect to when the user presses the " -"SAML button. For Keycloak, this needs to look like https://your.domain/" -"realms/your-realm/protocol/saml" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Login" msgstr "" -#: ../settings/security/third-party/saml.rst:127 -msgid "IDP single logout target URL" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.login}``" msgstr "" -#: ../settings/security/third-party/saml.rst:126 -msgid "" -"This is the URL to which the single logout request and response should be " -"sent." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Mobile" msgstr "" -#: ../settings/security/third-party/saml.rst:131 -msgid "IDP certificate" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.mobile}``" msgstr "" -#: ../settings/security/third-party/saml.rst:130 -msgid "" -"The public certificate of your IDP for Zammad to verify during the callback " -"phase." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Note" msgstr "" -#: ../settings/security/third-party/saml.rst:145 -msgid "IDP certificate fingerprint" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.note}``" msgstr "" -#: ../settings/security/third-party/saml.rst:134 -msgid "" -"The fingerprint of your IDPs public certificate to verify during callback " -"phase." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Phone" msgstr "" -#: ../settings/security/third-party/saml.rst:137 -msgid "🔏 **For the IdP certificate / certificate fingerprint:**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.phone}``" msgstr "" -#: ../settings/security/third-party/saml.rst:139 -msgid "" -"Provide **only one or the other**—do not provide both! (Between the two, we " -"recommend the signing certificate itself: fingerprints use SHA-1, which `has " -"been broken for a while now `_.)" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > VIP" msgstr "" -#: ../settings/security/third-party/saml.rst:144 -msgid "" -"**Keycloak users:** Find your certificate in the Keycloak admin panel under " -"**Realm Settings > Keys > Algorithm: RS256 > Certificate**." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.vip}``" msgstr "" -#: ../settings/security/third-party/saml.rst:151 -msgid "Name identifier format" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``false`` or ``true``" msgstr "" -#: ../settings/security/third-party/saml.rst:148 -msgid "" -"This is the unique identifiers field type. Usually it should be ``urn:oasis:" -"names:tc:SAML:1.1:nameid-format:emailAddress``." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Web" msgstr "" -#: ../settings/security/third-party/saml.rst:151 -msgid "Zammad **expects an email address as unique identifier**!" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.web}``" msgstr "" -#: ../settings/security/third-party/saml.rst:155 -msgid "UID attribute name" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > VIP" msgstr "" -#: ../settings/security/third-party/saml.rst:154 -msgid "" -"Here you can define an attribute that uniquely identifies the user. If " -"unset, the name identifier returned by the IDP is used." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.vip}``" msgstr "" -#: ../settings/security/third-party/saml.rst:None -msgid "Example configuration of SAML part 2" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Web" msgstr "" -#: ../settings/security/third-party/saml.rst:163 -msgid "" -"Decide if the certificate for the connection to the IdP service has to be " -"verified or not (default: ``yes``)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.web}``" msgstr "" -#: ../settings/security/third-party/saml.rst:169 -msgid "Signing & Encrypting" +#: ../misc/variables/ticket.rst:6 +msgid "" +"Below you can find all available ticket-based variables within Zammad. These " +"can be called via triggers for example. If you're unsure if Zammad does " +"support variables at the point you're at, you can try to type ``::`` to " +"check." msgstr "" -#: ../settings/security/third-party/saml.rst:169 -msgid "" -"Define if you want to sign, encrypt, do both or nothing for the requests." +#: ../misc/variables/ticket.rst:12 +msgid "Ticket Variables" msgstr "" -#: ../settings/security/third-party/saml.rst:179 -msgid "Certificate (PEM)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Accounted Time" msgstr "" -#: ../settings/security/third-party/saml.rst:172 -msgid "" -"Paste the public certificate of your Zammad SAML client, if you want to " -"encrypt the requests." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.time_unit}``" msgstr "" -#: ../settings/security/third-party/saml.rst:175 -msgid "Make sure the certificate is:" +#: ../misc/variables/ticket.rst:1 +msgid "``1``, ``2.75`` or empty response" msgstr "" -#: ../settings/security/third-party/saml.rst:177 -msgid "already valid and not yet expired" +#: ../misc/variables/ticket.rst:1 +msgid "``3``, any number of articles existing in the ticket right now" msgstr "" -#: ../settings/security/third-party/saml.rst:178 -msgid "no CA certificate" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Closing time" msgstr "" -#: ../settings/security/third-party/saml.rst:179 -msgid "valid for signing and encrypting" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.close_at}``" msgstr "" -#: ../settings/security/third-party/saml.rst:185 -msgid "Private key (PEM)" +#: ../misc/variables/ticket.rst:1 +msgid "2019-10-07 17:25:00 UTC" msgstr "" -#: ../settings/security/third-party/saml.rst:182 -msgid "" -"Paste the private key of your Zammad SAML client here, if you want to sign " -"the requests." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created at" msgstr "" -#: ../settings/security/third-party/saml.rst:185 -msgid "Make sure the key is an RSA key with a length of at least 2048 bits." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_at}``" msgstr "" -#: ../settings/security/third-party/saml.rst:188 -msgid "Private key secret" +#: ../misc/variables/ticket.rst:1 +msgid "2019-10-07 16:25:00 UTC" msgstr "" -#: ../settings/security/third-party/saml.rst:188 -msgid "If your private key is secured with a secret, you can provide it here." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Address" msgstr "" -#: ../settings/security/third-party/saml.rst:192 -msgid "Your callback URL" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.address}``" msgstr "" -#: ../settings/security/third-party/saml.rst:191 -msgid "" -"This URL is needed for your IdP configuration so it knows where to redirect " -"to after successful authentication." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Avatar" msgstr "" -#: ../settings/security/third-party/saml.rst:194 -msgid "" -"After saving your input by clicking on the \"Submit\" button, Zammad " -"verifies the provided keys/certificates (e.g. if they are valid for signing/" -"encrypting and if they aren't expired)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/saml.rst:199 -msgid "" -"See :ref:`automatic account linking ` for details " -"on how to link existing Zammad accounts to IdP accounts." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Department" msgstr "" -#: ../settings/security/third-party/saml.rst:205 -#, fuzzy -msgid "Automatic account linking doesn't work" -msgstr ":doc:`accounts/email-notification`" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.department}``" +msgstr "" -#: ../settings/security/third-party/saml.rst:206 -msgid "" -"Have you double-checked your IdP's user attribute mapping configuration?" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Email" msgstr "" -#: ../settings/security/third-party/twitter.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via Twitter. To do " -"so, you need to follow these steps:" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.email}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:8 -msgid "Register Twitter App" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Fax" msgstr "" -#: ../settings/security/third-party/twitter.rst:10 -msgid "Go to https://dev.twitter.com/apps and login with your account." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.fax}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:15 -msgid "Click on \"Create App\"" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Firstname" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "new app page" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.firstname}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:20 -msgid "" -"Enter app settings. As \"Callback URL\" you need to enter ``https://" -"zammad_host/api/v1/external_credentials/twitter/callback``. You need to " -"replace ``zammad_host`` with the domain of your Zammad system." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Lastname" msgstr "" -#: ../settings/security/third-party/twitter.rst:24 -msgid "" -"After the app has been created, update the application icon and organization " -"attributes." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.lastname}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "set permissions to receive and send direct messages" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Login" msgstr "" -#: ../settings/security/third-party/twitter.rst:30 -msgid "" -"Next we need to set ``read, write and access direct messages`` permissions " -"for the app." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.login}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "click on Keys & Access Token, note them" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Mobile" msgstr "" -#: ../settings/security/third-party/twitter.rst:36 -msgid "" -"Go to \"Keys and Access Token\" tab and note the \"Consumer Key\" and " -"\"Consumer Secret\"." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.mobile}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:40 -msgid "Configure Zammad as Twitter App" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Note" msgstr "" -#: ../settings/security/third-party/twitter.rst:42 -msgid "" -"Go to \"Admin > Security > Twitter > Third Party Applications > Twitter\" " -"Section." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.note}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "Admin > Security > Third Party Applications" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Phone" msgstr "" -#: ../settings/security/third-party/twitter.rst:48 -msgid "" -"Fill in the \"Twitter Key\" and the \"Twitter Secret\" and click the " -"\"Submit\" button." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.phone}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:51 -msgid "" -"Now you can link accounts via \"Avatar > Profile > Link Accounts\" or login " -"via Zammad login page." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > VIP" msgstr "" -#: ../settings/security/two-factor.rst:11 -msgid "Two-factor Authentication Methods" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.vip}``" msgstr "" -#: ../settings/security/two-factor.rst:2 -msgid "Two-Factor Authentication" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Web" msgstr "" -#: ../settings/security/two-factor.rst:4 -msgid "" -"Two-factor authentication (2FA) enhances the security of Zammad accounts by " -"adding an extra layer of verification beyond a password. It requires users " -"to provide two different types of authentication factors, typically " -"something they know (like a password) and something they possess (like a " -"mobile device or a security token), to ensure that only authorized " -"individuals can access the account." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.web}``" msgstr "" -#: ../settings/security/two-factor.rst:19 -msgid "Enable Recovery Codes" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Address" msgstr "" -#: ../settings/security/two-factor.rst:21 -msgid "" -"Recovery codes are one-time use security codes that can be used by the user " -"if they lose access to their other two-factor authentication methods. They " -"cannot be used on their own, they can only be activated if at least one two-" -"factor authentication method is enabled." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.address}``" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Enable Recovery Codes Setting" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Avatar" msgstr "" -#: ../settings/security/two-factor.rst:30 -msgid "" -"Recovery codes can only be used as a backup method. If enabled, they will be " -"automatically generated for the user once they set up their initial two-" -"factor authentication method." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.avatar(60,60)}``" msgstr "" -#: ../settings/security/two-factor.rst:34 -msgid "" -"The user will be asked to print out or save the generated recovery codes in " -"a safe place. Once used, a recovery code cannot be reused." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Department" msgstr "" -#: ../settings/security/two-factor.rst:37 -msgid "" -"Users will also have an option to regenerate their recovery codes at any " -"time, which invalidates already existing recovery codes and provides them " -"with a list of fresh codes." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.department}``" msgstr "" -#: ../settings/security/two-factor.rst:41 -msgid "" -"After you enable this setting, when the user completes a setup of their " -"initial two-factor authentication method, they will be presented with a list " -"of recovery codes and instructed to save them for later use." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Email" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Recovery Codes Generation Modal Dialog" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.email}``" msgstr "" -#: ../settings/security/two-factor.rst:50 -msgid "Enforce the Set Up of the Two-Factor Authentication" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Fax" msgstr "" -#: ../settings/security/two-factor.rst:52 -msgid "" -"In case you wish to require your users to set up at least one two-factor " -"authentication method for their account, you can do this by selecting " -"specific user roles the requirement applies to in **Enforced for user " -"roles** setting. Of course you must have at least one two-factor " -"authentication method enabled for this setting to take effect." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.fax}``" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Enforced for User Roles Setting" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Firstname" msgstr "" -#: ../settings/security/two-factor.rst:62 -msgid "" -"After you change this setting, if the user has one of the selected roles on " -"their account, they will be forced to set up the two-factor authentication " -"upon next sign in or application reload." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.firstname}``" msgstr "" -#: ../settings/security/two-factor.rst:66 -msgid "" -"A modal dialog with instructions will be shown, and they will not be able to " -"do any work before they set up at least one two-factor method." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Lastname" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Modal Dialog for Enforcing Two-Factor Authentication Set Up" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.lastname}``" msgstr "" -#: ../settings/security/two-factor.rst:74 -msgid "Reset Two-Factor Authentication for a Specific User" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Login" msgstr "" -#: ../settings/security/two-factor.rst:76 -msgid "" -"In case an user isn't able to login anymore because of an inaccessible " -"second factor, you can reset the user's 2FA method." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.login}``" msgstr "" -#: ../settings/security/two-factor.rst:79 -msgid "" -"To do this, go to the user management and search for the relevant user. " -"After you found the account, click the button in the action column and " -"select \"Manage Two-Factor Authentication\":" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Mobile" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Context menu in action column in user management" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.mobile}``" msgstr "" -#: ../settings/security/two-factor.rst:87 -msgid "" -"After selecting this, you can see a dialog where you can either reset one " -"2FA method or reset all of the user's 2FA methods:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Note" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Dialog for resetting user's 2FA method" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.note}``" msgstr "" -#: ../settings/security/two-factor.rst:94 -msgid "" -"Choose the fitting one, click on the corresponding \"Remove ...\" button and " -"confirm your action. The user now has to setup a new 2FA method, depending " -"on your 2FA configuration." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Phone" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:2 -msgid "Authenticator App" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.phone}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:4 -msgid "" -"The authenticator app method is a type of two-factor authentication that " -"uses a mobile application to generate one-time codes for account " -"verification. After setting up the authenticator app on their device, the " -"user links it to their Zammad account." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > VIP" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:12 -msgid "" -"When logging in, the user is prompted to enter a time-sensitive code " -"generated by the app, in addition to their password. This code acts as the " -"second factor of authentication, providing an extra layer of security as it " -"changes periodically and is unique to the user's device." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.vip}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:None -msgid "Security Code in Google Authenticator App" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Web" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:22 -msgid "" -"The app generates codes based on a shared secret key stored securely on both " -"the user's device and the server, ensuring a synchronized and secure " -"authentication process. The method of generating the codes is sometimes also " -"called TOTP (time-based one-time password)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.web}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:28 -msgid "Enabling the Authenticator App Method" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Escalation at" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:30 -#: ../settings/security/two-factor/security-keys.rst:28 -msgid "To enable the method, just toggle the switch on in the settings." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.escalation_at}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:None -msgid "Authenticator App Switch in Settings" +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:36 -msgid "" -"Now the users will be able to set up this two-factor authentication method " -"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " -"Once they do, on next sign-in with password, they will be asked to provide " -"an additional security code generated by their mobile device." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > First response" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:2 -msgid "Security Keys" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.first_response_at}``" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:4 -msgid "" -"The security keys method is a type of a two-factor authentication that uses " -"Web Authentication API in the browser for verifying user's identity. The " -"user can register multiple hardware or software security keys with their " -"Zammad account and then they can use it during the sign-in process." +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable yet" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:12 -msgid "" -"When logging in, the user is prompted to provide the same security key they " -"registered with their account, in addition to their password. This key acts " -"as the second factor of authentication, providing an extra layer of security." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Assign Follow-Ups" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:None -msgid "Security Key dialog in Safari on macOS" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_assignment}``" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:21 -msgid "" -"The type of the key can range from hardware USB sticks to passkeys stored in " -"a device of user's choice. Which type can be used depends on the browser " -"flavor and the platform of the user." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Assignment Timeout" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:26 -msgid "Enabling the Security Keys Method" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.assignment_timeout}``" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:None -msgid "Security Keys Switch in Settings" +#: ../misc/variables/ticket.rst:1 +msgid "``20`` or empty if not configured" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:34 -msgid "" -"Now the users will be able to set up this two-factor authentication method " -"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " -"Once they do, on next sign-in with password, they will be asked to provide " -"the same security key they registered during the setup." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Follow-up possible" msgstr "" -#: ../settings/system/system-selfhosted.include.rst:3 -msgid "" -"Below settings are only available to self hosted users. In hosted " -"environments we're handling these settings for you to ensure service " -"stability." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_possible}``" msgstr "" -#: ../settings/system/base.rst:11 -msgid "Fully Qualified Domain Name" +#: ../misc/variables/ticket.rst:1 +msgid "``no`` or ``yes``" msgstr "" -#: ../settings/system/base.rst:7 -msgid "The URL of your Zammad installation." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Name" msgstr "" -#: ../settings/system/base.rst:9 ../settings/system/base.rst:17 -msgid "This setting is used within :doc:`/system/variables` and notifications." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.name}``" msgstr "" -#: ../settings/system/system-base.include.rst:1 -msgid "It is automatically set by the *Getting Started wizard*." +#: ../misc/variables/ticket.rst:1 +msgid "``Sales``" msgstr "" -#: ../settings/system/system-base.include.rst:5 -msgid "Changing this setting also changes callback URLs for your channels etc." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Note" msgstr "" -#: ../settings/system/system-base.include.rst:6 -msgid "This setting can have negative affects on being able to login." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.note}``" msgstr "" -#: ../settings/system/base.rst:19 -msgid "HTTP type" +#: ../misc/variables/ticket.rst:1 +msgid "``Note about this group``" msgstr "" -#: ../settings/system/base.rst:14 -msgid "" -"The HTTP type tells your installation how your clients connect. This is " -"relevant for authentication and cookie security." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > ID" msgstr "" -#: ../settings/system/base.rst:31 -msgid "SystemID" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.id}``" msgstr "" -#: ../settings/system/base.rst:22 -msgid "" -"This ID is being used within your ticket number. In case you're " -"communicating with another ticket system with similar ticket number schemes " -"this ID greatly reduces the risk of false follow ups." +#: ../misc/variables/ticket.rst:1 +msgid "``17``, ``5281``, ..." msgstr "" -#: ../settings/system/base.rst:26 -msgid "" -"The SystemID is randomly selected upon installation of Zammad (``1-99``)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact (agent)" msgstr "" -#: ../settings/system/base.rst:30 -msgid "" -"**Do not** change this setting in a productive system! Your Zammad " -"installation may no longer recognize old ticket number based follow ups upon " -"change!" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_agent_at}``" msgstr "" -#: ../settings/system/frontend.rst:2 -msgid "Frontend" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact (customer)" msgstr "" -#: ../settings/system/frontend.rst:22 -msgid "Core Workflow Ajax Mode" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_customer_at}``" msgstr "" -#: ../settings/system/frontend.rst:6 +#: ../misc/variables/ticket.rst:1 msgid "" -"This setting allows administrators to enforce :doc:`/system/core-workflows` " -"to use Ajax-Calls instead of web sockets. You'll usually only need this if " -"you experience serious issues as noted below." +"``2019-10-07 16:25:00 UTC`` or empty if not applicable yet (Please note " +"`Ticket last contact behavior Settings `_ for this)" msgstr "" -#: ../settings/system/frontend.rst:10 -msgid "**🤓 Possible (technical) reasons**" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact" msgstr "" -#: ../settings/system/frontend.rst:12 -msgid "" -"In some cases, your network structure (e.g. firewalls, proxies) may " -"disconnect long web socket connections. This leads to select fields staying " -"empty (e.g. owner selection *after* selecting your group) or fields not " -"shown / hidden (e.g. when switching to or from pending states, the \"pending " -"till\" field not showing / hiding)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_at}``" msgstr "" -#: ../settings/system/frontend.rst:18 -msgid "" -"Please keep in mind that the Ajax fallback may cause serious pressure on " -"your application server. If you have the choice stick to web sockets." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Number" msgstr "" -#: ../settings/system/frontend.rst:22 -msgid "Default: ``no`` (inactive)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.number}``" msgstr "" -#: ../settings/system/frontend.rst:53 -msgid "Show calendar weeks in the picker of date/datetime fields" +#: ../misc/variables/ticket.rst:1 +msgid "``31001``, ``201910731001``, ..." msgstr "" -#: ../settings/system/frontend.rst:25 -msgid "" -"With this setting you can instruct Zammad to provide week number display " -"globally for all users. Calendar with week number display are usually used " -"in business sectors and may not be relevant for everyone." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain based assignment" msgstr "" -#: ../settings/system/frontend.rst:29 -msgid "" -"This setting affects *all areas* - you'll also see week numbers in the admin " -"panel for e.g. triggers and macros." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain_assignment}``" msgstr "" -#: ../settings/system/frontend.rst:32 -msgid "Default: ``no`` (not shown)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain" msgstr "" -#: ../settings/system/frontend.rst:53 -msgid "Here's the difference:" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain}``" msgstr "" -#: ../settings/system/frontend.rst:0 -msgid "Screenshot showing Zammad's date picker (in the default way)" +#: ../misc/variables/ticket.rst:1 +msgid "``domain.tld`` or empty if not set" msgstr "" -#: ../settings/system/frontend.rst:41 -msgid "Set to ``no``" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Name" msgstr "" -#: ../settings/system/frontend.rst:0 -msgid "" -"Screenshot showing Zammad's date picker with\n" -"week numbers enabled" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.name}``" msgstr "" -#: ../settings/system/frontend.rst:50 -msgid "Set to ``yes``" +#: ../misc/variables/ticket.rst:1 +msgid "``Zammad GmbH`` or empty if not set" msgstr "" -#: ../settings/system/index.rst:4 -msgid "" -"For your overview we split each tab within system settings into its own page:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Note" msgstr "" -#: ../settings/system/index.rst:16 -msgid "Console Based Settings" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.note}``" msgstr "" -#: ../settings/system/index.rst:18 -msgid "" -"There's some console based settings we didn't put into the UI. However, you " -"may find them helpful - you can find them in our :docs:`hidden settings ` section." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Shared organization" msgstr "" -#: ../settings/system/network.rst:2 -msgid "Network" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.shared}``" msgstr "" -#: ../settings/system/network.rst:8 -msgid "" -"The proxy settings can only be saved after successfully testing the proxy " -"connection." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > VIP" msgstr "" -#: ../settings/system/network.rst:15 -msgid "Proxy Address." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.vip}``" msgstr "" -#: ../settings/system/network.rst:12 -msgid "" -"Allows you to provide a proxy server if needed. This is relevant for network " -"communication by Zammad." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Address" msgstr "" -#: ../settings/system/network.rst:15 -msgid "It **does not** affect the update process or Elasticsearch." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.address}``" msgstr "" -#: ../settings/system/network.rst:18 -msgid "Username for proxy connection." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Avatar" msgstr "" -#: ../settings/system/network.rst:18 -msgid "" -"If your proxy server requires authentication, provide the username here." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.avatar(60,60)}``" msgstr "" -#: ../settings/system/network.rst:21 -msgid "Password for proxy connection." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Department" msgstr "" -#: ../settings/system/network.rst:21 -msgid "" -"If your proxy server requires authentication, provide the password here." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.department}``" msgstr "" -#: ../settings/system/network.rst:26 -msgid "No proxy for the following hosts." +#: ../misc/variables/ticket.rst:1 +msgid "``Support`` or empty if not set" msgstr "" -#: ../settings/system/network.rst:24 -msgid "" -"Exception list for hosts you can't or don't want to reach via proxy server." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Email" msgstr "" -#: ../settings/system/network.rst:27 -msgid "Default: ``localhost,127.0.0.0,::1``" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.email}``" msgstr "" -#: ../settings/system/services.rst:2 -msgid "Services" +#: ../misc/variables/ticket.rst:1 +msgid "``agent@company.tld`` or empty if not set" msgstr "" -#: ../settings/system/services.rst:10 -msgid "Image Service" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Fax" msgstr "" -#: ../settings/system/services.rst:5 -msgid "Defines the backend for user and organization image lookups." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.fax}``" msgstr "" -#: ../settings/system/services.rst:7 -msgid "Default: ``Zammad Image Service`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Firstname" msgstr "" -#: ../settings/system/services.rst:9 -msgid "" -"Make sure your on premise installation has ``HTTPS`` access to ``images." -"zammad.com``." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.firstname}``" msgstr "" -#: ../settings/system/services.rst:18 -msgid "Geo Calendar Service" +#: ../misc/variables/ticket.rst:1 +msgid "``Max`` or empty if not set" msgstr "" -#: ../settings/system/services.rst:13 -msgid "" -"Defines the backend for geo calendar lookups. Used for initial calendar " -"setup." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Lastname" msgstr "" -#: ../settings/system/services.rst:16 -msgid "Default: ``Zammad GeoCalendar Service`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.lastname}``" msgstr "" -#: ../settings/system/services.include.rst:2 -msgid "" -"Make sure your on premise installation has ``HTTPS`` access to ``geo.zammad." -"com``." +#: ../misc/variables/ticket.rst:1 +msgid "``Mustermann`` or empty if not set" msgstr "" -#: ../settings/system/services.rst:26 -msgid "Geo IP Service" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Login" msgstr "" -#: ../settings/system/services.rst:21 -msgid "" -"Defines the backend for geo IP lookups. Shows also location of an IP address " -"if an IP address is shown." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.login}``" msgstr "" -#: ../settings/system/services.rst:24 -msgid "Default: ``Zammad GeoIP Service`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "``agent``" msgstr "" -#: ../settings/system/services.rst:32 -msgid "Geo Location Service" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Mobile" msgstr "" -#: ../settings/system/services.rst:29 -msgid "" -"Defines the backend for geo location lookups to store geo locations for " -"addresses." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.mobile}``" msgstr "" -#: ../settings/system/services.rst:32 -msgid "" -"Default: ``OpenStreetMap (ODbL 1.0, http://osm.org/copyright)`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Note" msgstr "" -#: ../settings/system/services.rst:36 -msgid "" -"You can find a detailed privacy information on what we store for how long on " -"our :docs:`Privacy Appendix ` inside of our System " -"Documentation." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.note}``" msgstr "" -#: ../settings/system/storage.rst:2 -msgid "Storage" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Phone" msgstr "" -#: ../settings/system/storage.rst:6 -msgid "" -"Here you can define where Zammad stores attachments for tickets and the " -"knowledge base. By default, we're writing to the ``Database`` - you can " -"switch to ``Filesystem`` or ``Simple Storage (S3)`` at any time. In this " -"case please have a look on the following instructions." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.phone}``" msgstr "" -#: ../settings/system/storage.rst:11 -msgid "" -"If you have a busy Zammad instance, we strongly encourage you to use " -"filesystem storage instead of \"Database\". This will greatly improve system " -"performance (de-crease database load and size)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > VIP" msgstr "" -#: ../settings/system/storage.rst:19 -msgid "Database" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.vip}``" msgstr "" -#: ../settings/system/storage.rst:17 -msgid "" -"This is the default storage method. The attachments are stored directly in " -"the database. If your Zammad instance grows, we recommend one of the other " -"methods to maintain performance." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Web" msgstr "" -#: ../settings/system/storage.rst:38 -msgid "Filesystem" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.web}``" msgstr "" -#: ../settings/system/storage.rst:22 -msgid "" -"This storage method is recommended for all Zammad instances, especially for " -"those with a higher load. If you choose filesystem, your files are written " -"to ``/opt/zammad/storage/``." +#: ../misc/variables/ticket.rst:1 +msgid "``https://zammad.com`` or empty if not set" msgstr "" -#: ../settings/system/storage.rst:26 -msgid "" -"Moving attachments from \"Database\" to \"Filesystem\" can be run during " -"production use. However, you should consider your framework conditions (e.g. " -"bandwidth, system load in production) to define the right moment." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Pending till" msgstr "" -#: ../settings/system/storage.rst:32 -msgid "**You noticed slow updates of Zammad?**" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.pending_time}``" msgstr "" -#: ../settings/system/storage.rst:34 -msgid "" -"While Zammad is beeing updated, it enforces a recursive \"change " -"owner\" (chown) for this directory. For instances with many files this can " -"be time consuming. To mitigate that you can move your files and create a " -"symlink in ``/opt/zammad/storage/`` to the new directory. Of course you have " -"to make sure on your own that the permissions are always correct." +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not set" msgstr "" -#: ../settings/system/storage.rst:95 -msgid "Simple Storage (S3)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Priority > Name" msgstr "" -#: ../settings/system/storage.rst:41 -msgid "" -"To use the Simple Storage (S3), you have to provide some settings, which " -"can't be accessed in the UI (see instructions below)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.priority.name}``" msgstr "" -#: ../settings/system/storage.rst:44 -msgid "" -"⚠️ Please note that the current implementation is in its early stages and can " -"be modified in the future." +#: ../misc/variables/ticket.rst:1 +msgid "``2 normal``" msgstr "" -#: ../settings/system/storage.rst:47 -msgid "" -"The prerequisite is to have access to a S3-compatible storage and to have " -"all necessary parameters available (which depends on your storage provider; " -"if in doubt, please ask there for help)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > State > Name" msgstr "" -#: ../settings/system/storage.rst:51 -msgid "Steps to configure S3:" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.state.name}``" msgstr "" -#: ../settings/system/storage.rst:53 -msgid "" -"Copy ``config/zammad/storage.yml.dist`` to ``config/zammad/storage.yml``" +#: ../misc/variables/ticket.rst:1 +msgid "``new``, ``open``, ..." msgstr "" -#: ../settings/system/storage.rst:54 -msgid "Edit the copied file in one of the following ways:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Tags" msgstr "" -#: ../settings/system/storage.rst:56 -msgid "" -"Either provide your S3 configuration with one attribute per line like in the " -"upper area of the file" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.tags}``" msgstr "" -#: ../settings/system/storage.rst:58 +#: ../misc/variables/ticket.rst:1 msgid "" -"Or provide your S3 configuration as an URL (which you can find at the end of " -"the file). Note: you can also provide this URL as environment variable (:" -"docs:`see system documentation `) without using this yml-file." +"Currently not available, see `Issue 2769 `_" msgstr "" -#: ../settings/system/storage.rst:62 -msgid "" -"We recommend the deletion of the not used configuration style to avoid " -"inconsistencies." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Title" msgstr "" -#: ../settings/system/storage.rst:65 -msgid "Restart Zammad so the config file / environment variable is loaded" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.title}``" msgstr "" -#: ../settings/system/storage.rst:66 +#: ../misc/variables/ticket.rst:1 msgid "" -"Set the \"Storage Method\" in Zammad to ``Simple Storage (S3)`` in Settings " -"> System > Storage and click on \"Submit\". After that, Zammad checks your " -"configuration and the connection to the service and will raise an error " -"message if something is wrong." +"``My amazing Subject`` (normally subject, can be edited within Interface and " +"thus differ)" msgstr "" -#: ../settings/system/storage.rst:72 -msgid "A very simple storage configuration could look like this:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated at" msgstr "" -#: ../settings/system/storage.rst:85 -msgid "" -"Before setting the storage method to ``Simple Storage (S3)`` (step 4), " -"please make sure to have a working setup." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_at}``" msgstr "" -#: ../settings/system/storage.rst:88 -msgid "" -"You can verify this by running ``rails r 'Rails.logger = Logger.new(STDOUT); " -"pp Store::Provider::S3.ping?'`` in your Zammad directory. If everything is " -"fine, you should see ``true``, else you should see ``false`` and a simple " -"error message." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Address" msgstr "" -#: ../settings/system/storage.rst:93 -msgid "" -"If you installed Zammad through a package manager (rather than from source), " -"replace ``rails r`` with ``zammad run rails r`` above. To learn more, see :" -"docs:`Administration via Console `." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.address}``" msgstr "" -#: ../settings/ticket.rst:4 -msgid "" -"Here you can adjust general ticket settings. Additional ones for the ticket " -"composer interface can be found in the :doc:`/misc/composer`." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Avatar" msgstr "" -#: ../settings/ticket.rst:11 -msgid "Ticket Hook (default: ``Ticket#``)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.avatar(60,60)}``" msgstr "" -#: ../settings/ticket.rst:11 -msgid "The identifier for a ticket; *e.g.,* Ticket#, Call#, MyTicket#." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Department" msgstr "" -#: ../settings/ticket.rst:38 -msgid "Ticket Hook Position (default: ``right``)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.department}``" msgstr "" -#: ../settings/ticket.rst:14 -msgid "" -"With this setting you can decide (if) where to insert the ticket number." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Email" msgstr "" -#: ../settings/ticket.rst:20 -msgid "*Right*" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.email}``" msgstr "" -#: ../settings/ticket.rst:17 -msgid "" -"This setting will add the ticket reference on the right site of the subject." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Fax" msgstr "" -#: ../settings/ticket.rst:20 -msgid "Example: ``Some Subject [Ticket#12345]``" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.fax}``" msgstr "" -#: ../settings/ticket.rst:26 -msgid "*Left*" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Firstname" msgstr "" -#: ../settings/ticket.rst:23 -msgid "" -"This setting will add the ticket reference on the left site of the subject." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.firstname}``" msgstr "" -#: ../settings/ticket.rst:26 -msgid "Example: ``[Ticket#12345] Some Subject``" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Lastname" msgstr "" -#: ../settings/ticket.rst:29 -msgid "*None*" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.lastname}``" msgstr "" -#: ../settings/ticket.rst:29 -msgid "This will completely remove ticket references from the subject." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Login" msgstr "" -#: ../settings/ticket.rst:33 -msgid "" -"Please ensure to take a look at :doc:`/channels/email/settings` within the " -"email channel to ensure you have at least one reference that helps Zammad to " -"assign follow-ups correctly." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.login}``" msgstr "" -#: ../settings/ticket.rst:37 -msgid "" -"Disabling this and not setting up any further follow up search will lead to " -"unexpected results!" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Mobile" msgstr "" -#: ../settings/ticket.rst:65 -msgid "" -"Ticket Last Contact Behaviour (default: ``Use the start time of the last " -"customer thread (which may consist of multiple articles).``)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.mobile}``" msgstr "" -#: ../settings/ticket.rst:41 -msgid "" -"This setting changes the way Zammad updates the ``Last Contact`` value of a " -"ticket. This is fairly important for overviews and what you expect upon " -"ticket updates of a customer." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Note" msgstr "" -#: ../settings/ticket.rst:52 -msgid "" -"Use the start time of the last customer thread (which may consist of " -"multiple articles)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.note}``" msgstr "" -#: ../settings/ticket.rst:46 -msgid "" -"If this option is chosen, Zammad will update the last updated value just " -"once if a customer replies. After that, Zammad will wait for an agent to " -"react." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Phone" msgstr "" -#: ../settings/ticket.rst:50 -msgid "" -"This comes in handy if you want to work tickets in the order of their first " -"update. This will not change ticket orders if customers decide to \"bump\" " -"the ticket affected." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.phone}``" msgstr "" -#: ../settings/ticket.rst:57 -msgid "Use the time of the very last customer article." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > VIP" msgstr "" -#: ../settings/ticket.rst:55 -msgid "" -"When setting this option, Zammad will always update the last updated value. " -"This means that if ordering by ``Last Update``, ticket orders will change if " -"customers \"bump\" the ticket." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.vip}``" msgstr "" -#: ../settings/ticket.rst:64 -msgid "Last contact value used on :doc:`/manage/overviews`" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Web" msgstr "" -#: ../settings/ticket.rst:65 -msgid "Last contact value used on :doc:`/manage/trigger`" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.web}``" msgstr "" -#: ../settings/ticket.rst:88 -msgid "" -"Ticket Organization Reassignment (default: ``Update the most recent tickets." -"``)" +#: ../settings/branding.rst:10 +msgid "Product Name" msgstr "" -#: ../settings/ticket.rst:68 +#: ../settings/branding.rst:7 msgid "" -"This setting changes the way Zammad updates the organization field of the " -"tickets whenever the primary organization of a user is changed." -msgstr "" - -#: ../settings/ticket.rst:74 -msgid "Update the most recent tickets." +"Defines the name of the application, shown in the web interface, tabs and " +"title bar of the web browser." msgstr "" -#: ../settings/ticket.rst:72 -msgid "" -"If this option is chosen, Zammad will update the 100 most recent tickets " -"where the user is the ticket customer. The ticket organization field will be " -"automatically set to the new primary organization of the user." +#: ../settings/branding.rst:10 +msgid "Default value: ``Zammad Helpdesk``" msgstr "" -#: ../settings/ticket.rst:88 -msgid "Do not update any tickets." +#: ../settings/branding.rst:13 +msgid "Will be shown in the app and is included in email footers." msgstr "" -#: ../settings/ticket.rst:77 -msgid "" -"When choosing this option, Zammad will not update any tickets when the " -"user's primary organization is changed." +#: ../settings/branding.rst:19 +msgid "Logo" msgstr "" -#: ../settings/ticket.rst:80 -msgid "**Use with care!**" +#: ../settings/branding.rst:16 +msgid "Defines the logo of the application, shown in the login page of Zammad." msgstr "" -#: ../settings/ticket.rst:82 +#: ../settings/branding.rst:18 msgid "" -"Using this option may lead to inconsistencies in the system as the ticket " -"organization may become decoupled from the ticket customer." +"Ensure to hit the \"Submit\" button after uploading the logo. Otherwise your " +"change will not be saved." msgstr "" -#: ../settings/ticket.rst:85 +#: ../settings/branding.rst:22 msgid "" -"However, you may use this option if you wish to maintain :ref:`the shared " -"access ` to the ticket for all organization " -"members of the original organization of the customer." +"Allows to set the default language of the Zammad instance. The here defined " +"locale mostly acts as a fallback for:" msgstr "" -#: ../settings/ticket.rst:110 -msgid "Ticket Number Format (default: ``Increment (SystemID.Counter)``)" +#: ../settings/branding.rst:25 +msgid "user preferences (if Zammad can't detect the users locale)" msgstr "" -#: ../settings/ticket.rst:94 -msgid "" -"This setting defines the way Zammad's ticket number will look. Changing this " -"setting in production will cause follow up detection to fail." +#: ../settings/branding.rst:26 +msgid "CSV output (reporting, time accounting)" msgstr "" -#: ../settings/ticket.rst:102 -msgid "Increment (SystemID.Counter)" +#: ../settings/branding.rst:30 +msgid "Define the timezone of your Zammad installation." msgstr "" -#: ../settings/ticket.rst:98 +#: ../settings/branding.rst:32 msgid "" -"The increment value contains the SystemID (automatically generated during " -"installation) and a increment which counts up with every new Ticket. The " -"increment will automatically get another digit if needed." +"This does not have any effect on timings for your agents or how Zammad " +"stores date and time values." msgstr "" -#: ../settings/ticket.rst:102 -msgid "Examples: ``1010138``, ``1010139``" +#: ../settings/branding.rst:35 +msgid "Changing this value has direct consequences on the following areas:" msgstr "" -#: ../settings/ticket.rst:110 -msgid "Date (Year.Month.Day.SystemID.Counter)" +#: ../settings/branding.rst:37 +msgid ":doc:`/manage/scheduler` tasks" msgstr "" -#: ../settings/ticket.rst:105 -msgid "" -"This version of the ticket number is fairly long. However, because it " -"contains the date of ticket creation, it also allows you to see when the " -"ticket has been created. You may feel familiar with this number format if " -"you've worked with OTRS already." +#: ../settings/branding.rst:38 +msgid "search indexing (and thus reporting)" msgstr "" -#: ../settings/ticket.rst:110 -msgid "Examples: ``201206231010138``, ``201206231010139``" +#: ../settings/branding.rst:40 +msgid "calendar subscriptions" msgstr "" -#: ../settings/ticket.rst:137 -msgid "OPTIONS" +#: ../settings/branding.rst:41 +msgid "browser printing" msgstr "" -#: ../settings/ticket.rst:113 +#: ../settings/branding.rst:43 msgid "" -"The below options allow you to further customize your ticket number. The " -"availability of options differ depending of the chosen ticket number format " -"above." +"Please note that some of above are fallbacks in case Zammad could not detect " +"the agents timezone correctly." msgstr "" -#: ../settings/ticket.rst:122 -msgid "Checksum (default: ``no``)" +#: ../settings/branding.rst:77 +msgid "Pretty Date" msgstr "" -#: ../settings/ticket.rst:118 +#: ../settings/branding.rst:47 msgid "" -"If set to yes, we'll built a checksum to further \"unique\" the ticket " -"number of your system. If you're dealing with many other ticket systems this " -"might help to prevent false positive follow up detection on tickets." +"This setting allows you to define how Zammad should display time stamps " +"within the interface to all users." msgstr "" -#: ../settings/ticket.rst:122 -msgid "This will also add another digit to the ticket number." +#: ../settings/branding.rst:50 +msgid "" +"This does not have any effect on how Zammad returns e.g. time values via " +"variables." msgstr "" -#: ../settings/ticket.rst:137 -msgid "Min. size of Number (default: ``5``)" +#: ../settings/branding.rst:77 +msgid "Choose in between the following options:" msgstr "" -#: ../settings/ticket.rst:125 -msgid "" -"This setting defines the minimum length of your ticket number. If your " -"counter is not yet high enough, Zammad will fill the number with zeros to " -"ensure the wanted length." +#: ../settings/branding.rst:64 +msgid "relative" msgstr "" -#: ../settings/ticket.rst:129 +#: ../settings/branding.rst:55 msgid "" -"Please note that the minimum length is ``3`` (SystemID + at least one digit " -"if below 10). Also, if the length is no longer long enough, the number will " -"automatically get one digit longer. Ticket-Numbers **do not overflow**, thus " -"it's save to keep it at 5 or set it lower if wanted." +"This timestamp shows a relative time span until it switches to a date. Over " +"time, it will change as follows:" msgstr "" -#: ../settings/ticket.rst:135 -msgid "" -"This option is only available if ticket number format is set to " -"``Increment``!" +#: ../settings/branding.rst:58 +msgid "just now" msgstr "" -#: ../settings/ticket.rst:142 -msgid "Auto-Assignment" +#: ../settings/branding.rst:59 +msgid "5 minutes ago" msgstr "" -#: ../settings/ticket.rst:144 -msgid "" -"In a larger Zammad environment, it happens that several agents open the same " -"ticket at the same time. Although collision detection is then effective, the " -"efficiency of processing can be increased by means of the automatic " -"assignment of tickets when a ticket is opened." +#: ../settings/branding.rst:60 +msgid "3 days 1 hour ago" msgstr "" -#: ../settings/ticket.rst:149 -msgid "" -"The automatic assignment of tickets can be activated and configured in the " -"admin area under Settings > Ticket > Auto Assignment." +#: ../settings/branding.rst:61 +msgid "``03/04/2022``" msgstr "" -#: ../settings/ticket.rst:152 -msgid "" -"The auto assignment only works if the ticket has no owner yet. By default, " -"the agent can always reset the ticket owner to ``-`` if needed." +#: ../settings/branding.rst:63 +msgid "Hovering the timestamp helps, you'll always get a clean timestamp then." msgstr "" -#: ../settings/ticket.rst:155 -msgid "" -"If you want to use this function for only specific tickets, you can " -"configure the conditions accordingly to meet your requirement. By default " -"the condition affects all tickets with the state ``open``." +#: ../settings/branding.rst:71 +msgid "absolute" msgstr "" -#: ../settings/ticket.rst:161 +#: ../settings/branding.rst:67 msgid "" -"If you need to exclude users (e.g. a group leader), you can search and " -"select the desired agents in the ``Exception Users`` list. The search " -"function in this area is only effective, if you have too many agents to " -"display at once to help you with the configuration." +"This timestamp always includes the week day. For one week after creation, " +"the timestamp will not contain the date itself: Thursday 18:35." msgstr "" -#: ../settings/ticket.rst:167 -msgid "Notifications" +#: ../settings/branding.rst:71 +msgid "After a week it will switch to: ``Friday 4. Mar 16:00``." msgstr "" -#: ../settings/ticket.rst:191 -msgid "Default Notifications" +#: ../settings/branding.rst:76 +msgid "timestamp" msgstr "" -#: ../settings/ticket.rst:170 +#: ../settings/branding.rst:74 msgid "" -"This setting allows you to configure the default ticket notifications that " -"will be applied to all new agent users (incl. users who were just assigned " -"agent role). Simply change the notification matrix to desired state and " -"press **Save**." +"This will cause Zammad to show a complete timestamp according to your locale " +"defaults. For English this could be e.g. ``2022/12/03 2:40 pm`` or for " +"German e.g. ``12.03.2022 14:40``." msgstr "" -#: ../settings/ticket.rst:175 -msgid "" -"In case an agent already exists, their ticket notification preferences will " -"be preserved. Optionally, you can also **Apply current defaults to all " -"agents**." +#: ../settings/branding.rst:78 +msgid "Default setting: ``relative``." msgstr "" -#: ../settings/ticket.rst:181 -msgid "" -"**Potential time-consuming action:** Applying default ticket notifications " -"to all agent users may take some time to complete, be patient! The exact " -"time will depend on the size of your system and the number of agents." +#: ../settings/security.rst:2 +msgid "Security" msgstr "" -#: ../settings/ticket.rst:185 +#: ../settings/security.rst:4 msgid "" -"**Active agents only!** When current default ticket notifications are " -"applied, only active agent users are considered. In case an agent is re-" -"activated *after* this action, they will still have the old notification " -"configuration." +"For your overview we split each tab within security settings into its own " +"page:" msgstr "" -#: ../settings/ticket.rst:190 -msgid "" -"In case you want to go back to the initial state of ticket notifications, " -"you can click on **Reset to default** button." +#: ../settings/security/base.rst:2 ../settings/system/base.rst:2 +#: ../settings/ticket.rst:8 +msgid "Base" msgstr "" -#: ../settings/ticket.rst:194 ../settings/ticket.rst:196 -msgid "Duplicate Detection" +#: ../settings/security/base.rst:5 +msgid "New User Accounts" msgstr "" -#: ../settings/ticket.rst:236 ../settings/ticket.rst:238 -msgid "Detect Duplicate Ticket Creation" +#: ../settings/security/base.rst:9 +msgid "" +"Activates the `register as a new customer` function on the login page. If " +"set to ``no`` only administrators or agents can create new accounts manually." msgstr "" -#: ../settings/ticket.rst:197 ../settings/ticket.rst:199 -msgid "" -"This setting turns on the duplicate ticket detection mechanism during ticket " -"creation. If similar tickets are found in the system, a suitable warning " -"will be shown to the user trying to create a ticket." +#: ../settings/security/base.rst:13 ../settings/security/base.rst:38 +#: ../settings/security/base.rst:66 +msgid "Default setting: ``yes``" msgstr "" -#: ../settings/ticket.rst:204 ../settings/ticket.rst:206 -msgid "A Sample Duplicate Ticket Warning" +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"New User Accounts\" setting" msgstr "" -#: ../settings/ticket.rst:206 ../settings/ticket.rst:208 +#: ../settings/security/base.rst:22 msgid "" -"You can choose which ticket attributes will be matched by selecting them in " -"**Attributes to compare** field. Only if the ticket attribute value provided " -"by the user in the ticket create form is *equal* with the attribute in an " -"existing ticket, the warning will be shown." +"Deactivation of above function **does not** deactivate automatic account " +"creation! This means: If a user writes e.g. an email to Zammad and has no " +"account yet, Zammad will automatically create the account. User accounts are " +"a direct dependency of tickets and thus technically mandatory." msgstr "" -#: ../settings/ticket.rst:211 ../settings/ticket.rst:213 -msgid "**Warning title** and **Warning message** are configurable as well." +#: ../settings/security/base.rst:29 +msgid "Lost Password" msgstr "" -#: ../settings/ticket.rst:213 ../settings/ticket.rst:215 +#: ../settings/security/base.rst:33 msgid "" -"You can limit the detection only to certain user roles. By default, only " -"agents will see the warning." +"Activates the `lost password` function on the login page. If set to ``no`` " +"only administrators may change the user's password - users may update their " +"own password if they're still logged in and they have the required :doc:" +"`permission `." msgstr "" -#: ../settings/ticket.rst:216 ../settings/ticket.rst:218 -msgid "" -"If you don't want to show the matched tickets as part of the warning, you " -"can set **Show matching ticket(s) in the warning** setting to *no*." +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"Lost Password\" setting" msgstr "" -#: ../settings/ticket.rst:219 ../settings/ticket.rst:221 +#: ../settings/security/base.rst:49 msgid "" -"By default, **Permission level for looking up ticket** is set to *User*, " -"which means user permissions will be honored during sarch. The user will " -"see the warning only if tickets they have access to are matched. " -"Alternatively, you can set this setting to *System*, in which case the " -"search will happen within *all* tickets in the system, regardless of user " -"permissions." +"With third party authentications - but especially LDAP - you may want to " +"disable this function. Zammad **will not** change third party login " +"passwords and instead set or change the local password!" msgstr "" -#: ../settings/ticket.rst:225 ../settings/ticket.rst:227 -msgid "**🦺 Safety first!**" +#: ../settings/security/base.rst:56 +msgid "Password Login" msgstr "" -#: ../settings/ticket.rst:227 ../settings/ticket.rst:229 +#: ../settings/security/base.rst:60 msgid "" -"Even if the permission level is set to *System*, the user will not be shown " -"the tickets they don't have access to in the warning, even if they match." +"Activates the username & password login by default and if no third-party " +"login is activated. Disabling password login on the Zammad login page only " +"takes effect if you enable any :doc:`third-party`." msgstr "" -#: ../settings/ticket.rst:231 ../settings/ticket.rst:233 -msgid "" -"However, just the confirmation about the existence of the tickets in the " -"system may be considered an unwanted information disclosure. Use this option " -"carefully!" +#: ../settings/security/base.rst:64 +msgid "See :doc:`third-party` for supported third-party logins." +msgstr "" + +#: ../settings/security/base.rst:0 +msgid "Figure showing de-activated \"Password Login\" setting" msgstr "" -#: ../settings/ticket.rst:235 ../settings/ticket.rst:237 +#: ../settings/security/base.rst:77 msgid "" -"Finally, you can configure between matching within **All tickets** or **Open " -"tickets** only by setting **Match tickets in following states**. Depending " -"on the current ticket state, a ticket may or not be matched." +"To help administrators to overcome \"login issues\", Zammad automatically " +"offers a password request for administrator users. This allows you to adjust " +"Third-Party applications even if the login does no longer work!" msgstr "" -#: ../system/core-workflows.rst:2 -msgid "Core Workflows" +#: ../settings/security/base.rst:84 +msgid "Session Timeout" msgstr "" -#: ../system/core-workflows.rst:4 +#: ../settings/security/base.rst:86 msgid "" -"Core Workflows allow you to adjust object attributes in many ways. For " -"example:" +"All settings below by default are set to ``4 weeks``. Session Timeout " +"defines the life time of a users session. As soon as it's reached, Zammad " +"will automatically log off the session in question." msgstr "" -#: ../system/core-workflows.rst:7 -msgid "show / hide fields" +#: ../settings/security/base.rst:91 +msgid "" +"Zammad takes the highest value set assigned for the user based on the " +"permissions." msgstr "" -#: ../system/core-workflows.rst:8 -msgid "adjust mandatory setting" +#: ../settings/security/base.rst:94 +msgid "``admin``" msgstr "" -#: ../system/core-workflows.rst:9 -msgid "manipulate available options" +#: ../settings/security/base.rst:96 +msgid "``ticket.customer``" msgstr "" -#: ../system/core-workflows.rst:11 -msgid "" -"With this, you can provide exactly the information your users really need!" +#: ../settings/security/base.rst:97 +msgid "``default`` (fallback if user doesn't have above permissions set)" msgstr "" -#: ../system/core-workflows.rst:15 +#: ../settings/security/base.rst:99 msgid "" -"If the pre-defined :doc:`/system/objects` are not enough, please add them " -"beforehand." +"All settings act independently from each other allowing you to disable the " +"timeouts for e.g. admins, but not agents." msgstr "" -#: ../system/core-workflows.rst:17 -msgid "" -"If you experience slow or unreliable field updates, please see :ref:`Core " -"Workflow Ajax Modus `" -msgstr "" +#: ../settings/security/base.rst:115 +#: ../system/integrations/checkmk/api-reference.rst:13 +msgid "Example" +msgstr "Primjer" -#: ../system/core-workflows.rst:22 -msgid "" -"This is a very enhanced functionality and can cause unexpected UI behavior. " -"Please ensure to test your use cases after configuration to reduce surprises." +#: ../settings/security/base.rst:107 +msgid "Let's suppose you configured the following session timeouts" msgstr "" -#: ../system/core-workflows.rst:None -msgid "Dialogue for adding a new workflow" +#: ../settings/security/base.rst:104 +msgid "default: 3 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:2 -msgid "Core Workflow Condition Operators" +#: ../settings/security/base.rst:105 +msgid "admin: 2 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:4 -msgid "" -"You might know that there is a separate section for explaining :doc:" -"`condition operators `. Head over there to " -"see a detailed explanation of many conditions and operators." +#: ../settings/security/base.rst:106 +msgid "ticket.agent: 4 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:8 -msgid "" -"Due to differences to other places in Zammad which are also using conditions " -"(e.g. triggers), you can find a dedicated description of operators for core " -"workflows below." +#: ../settings/security/base.rst:107 +msgid "ticket.customer: 1 week" msgstr "" -#: ../system/core-workflows/condition-operators.rst:12 -msgid "" -"Be aware that the availability of the operators depends on the selected " -"attribute and its field type. Some of the operators may only be available " -"for system attributes (e.g. for \"tags\", \"active\")." +#: ../settings/security/base.rst:115 +msgid "This results in the following situations" msgstr "" -#: ../system/core-workflows/condition-operators.rst:20 -msgid "Operator" +#: ../settings/security/base.rst:110 +msgid "a user with ``admin`` permission will have a timeout of 2 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:22 -msgid "after (absolute)" +#: ../settings/security/base.rst:111 +msgid "" +"a user with ``admin`` and ``ticket.agent`` permissions will have a timeout " +"of 2 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:23 -msgid "Matches if a date/time is after a specific point in time." +#: ../settings/security/base.rst:113 +msgid "" +"a user with ``ticket.customer`` permission will have a timeout of 1 week" msgstr "" -#: ../system/core-workflows/condition-operators.rst:24 -msgid "after (relative)" +#: ../settings/security/base.rst:115 +msgid "" +"a user with neither ``admin``, ``ticket.agent`` nor ``ticket.customer`` " +"permissions will have a timeout of 3 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:25 -msgid "Matches if a time span after a specified event has passed." +#: ../settings/security/password.rst:4 +msgid "" +"This section allows you to define password requirements for the local user " +"accounts." msgstr "" -#: ../system/core-workflows/condition-operators.rst:26 -msgid "before (absolute)" +#: ../settings/security/password.rst:9 +msgid "" +"Zammad does **not** allow you to change your LDAP password, instead, it will " +"set a password in its local database which might confuse your users. This " +"might be addressed in the future by `#1169 `_." msgstr "" -#: ../system/core-workflows/condition-operators.rst:27 -msgid "Matches if a date/time is before a specific point in time." +#: ../settings/security/password.rst:14 +msgid "**Exception for admins**" msgstr "" -#: ../system/core-workflows/condition-operators.rst:28 -msgid "before (relative)" +#: ../settings/security/password.rst:16 +msgid "" +"Please note that below password policies *do not* affect administrators " +"setting passwords on user accounts. While this seems strange and not safe we " +"believe that an administrator knowing an user's password is insecure as well." msgstr "" -#: ../system/core-workflows/condition-operators.rst:29 -msgid "Matches if a time span after a specified event has not passed." +#: ../settings/security/password.rst:21 +msgid "The suggested workflow is either:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:30 -msgid "contains" +#: ../settings/security/password.rst:23 +msgid "" +"to use third party logins to not require local passwords at all **- or -**" msgstr "" -#: ../system/core-workflows/condition-operators.rst:31 -msgid "Matches if a specified value is present." +#: ../settings/security/password.rst:25 +msgid "to require your *user to reset the password* upon first login." msgstr "" -#: ../system/core-workflows/condition-operators.rst:33 -msgid "Matches if all of the specified values are present." +#: ../settings/security/password.rst:27 +msgid "" +"This way administrators are not required to set a user's password at all!" msgstr "" -#: ../system/core-workflows/condition-operators.rst:35 -msgid "Matches if none of the specified values are present." +#: ../settings/security/password.rst:31 +msgid "Maximum Failed Logins" msgstr "" -#: ../system/core-workflows/condition-operators.rst:36 -msgid "contains not" +#: ../settings/security/password.rst:33 +msgid "" +"You can choose a value between ``4`` and ``20``. This defines how often a " +"login to a user account may fail until Zammad will lock it. Your users can " +"always use the \"forgot password\" function to change their password and " +"unlock their account." msgstr "" -#: ../system/core-workflows/condition-operators.rst:37 -msgid "Matches if a specified value is not present." +#: ../settings/security/password.rst:38 +msgid "The default value is ``10``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:39 -msgid "Matches if one specified value is present." +#: ../settings/security/password.rst:42 +msgid "Beside changing the user's password, you can also unlock accounts via" msgstr "" -#: ../system/core-workflows/condition-operators.rst:41 -msgid "Matches if one specified value is not present." +#: ../settings/security/password.rst:44 +msgid ":ref:`user management list `" msgstr "" -#: ../system/core-workflows/condition-operators.rst:42 -msgid "does not match regex" +#: ../settings/security/password.rst:45 +msgid ":docs:`console `" msgstr "" -#: ../system/core-workflows/condition-operators.rst:43 -msgid "Matches if content doesn't fit to regex rule." +#: ../settings/security/password.rst:46 +msgid ":docs:`API `" msgstr "" -#: ../system/core-workflows/condition-operators.rst:44 -msgid "ends with" +#: ../settings/security/password.rst:50 +msgid "Failed logins via LDAP no longer lock accounts." msgstr "" -#: ../system/core-workflows/condition-operators.rst:45 -msgid "Matches if content ends with specified value." +#: ../settings/security/password.rst:53 +msgid "2 Lower Case And 2 Upper Case Characters" msgstr "" -#: ../system/core-workflows/condition-operators.rst:46 -msgid "ends with one of" +#: ../settings/security/password.rst:55 +msgid "" +"You can add complexity to passwords by enforcing at least 2 upper and lower " +"case characters." msgstr "" -#: ../system/core-workflows/condition-operators.rst:47 -msgid "Matches if content ends with one of the specified values." +#: ../settings/security/password.rst:58 ../settings/security/password.rst:83 +msgid "The default value is ``no``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:48 -msgid "from (relative)" +#: ../settings/security/password.rst:62 +msgid "Minimum Length" msgstr "" -#: ../system/core-workflows/condition-operators.rst:49 -msgid "Matches if date/time is after a period of time after an event." +#: ../settings/security/password.rst:64 +msgid "" +"This defines the minimum password length required for users to provide (from " +"``4`` to ``20``)." msgstr "" -#: ../system/core-workflows/condition-operators.rst:51 -msgid "Matches if content is equal to a specified value." +#: ../settings/security/password.rst:67 +msgid "The default value is ``6``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:52 -msgid "is any of" +#: ../settings/security/password.rst:71 +msgid "Digit Required" msgstr "" -#: ../system/core-workflows/condition-operators.rst:53 -msgid "Matches if content is equal to any of specified values." +#: ../settings/security/password.rst:73 +msgid "This enforces your users to use at least one digit within the password." msgstr "" -#: ../system/core-workflows/condition-operators.rst:54 -msgid "is modified" +#: ../settings/security/password.rst:75 +msgid "The default value is ``yes``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:55 -msgid "Matches if content is modified." +#: ../settings/security/password.rst:78 +msgid "Special Character Required" msgstr "" -#: ../system/core-workflows/condition-operators.rst:57 -#: ../system/core-workflows/condition-operators.rst:61 -msgid "True from the moment of changing content until form submit." +#: ../settings/security/password.rst:80 +msgid "" +"This setting allows you to improve your password quality even more by " +"enforcing the password to contain at least one special character." msgstr "" -#: ../system/core-workflows/condition-operators.rst:58 -msgid "is modified to" +#: ../settings/security/ssl-certificates.rst:2 +msgid "SSL Certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:59 -msgid "Matches if content is modified to a specific value." +#: ../settings/security/ssl-certificates.rst:7 +msgid "" +"Zammad offers the possibility to upload custom certificates and custom " +"Certificate Authority (CA) certificates. This can be useful if you want to " +"connect Zammad the secure way to other systems which are using custom " +"certificates." msgstr "" -#: ../system/core-workflows/condition-operators.rst:62 -msgid "is none of" +#: ../settings/security/ssl-certificates.rst:12 +msgid "" +"An example usecase might be: You have an internal LDAP server that is not " +"accessible from the internet, and you want a SSL-encrypted connection, using " +"a custom certificate." msgstr "" -#: ../system/core-workflows/condition-operators.rst:63 -msgid "Matches if content is none of any specified values." +#: ../settings/security/ssl-certificates.rst:19 +msgid "" +"You should have an existing custom certificate file and/or a custom CA " +"certificate file, which you want to add to Zammad. As filetype ``.crt`` is " +"supported and the certificate format has to be PEM (Base64 ASCII)." msgstr "" -#: ../system/core-workflows/condition-operators.rst:65 -msgid "Matches if content is not equal to a specified value." +#: ../settings/security/ssl-certificates.rst:25 +msgid "" +"When you import a custom CA certificate, all certificates generated with " +"this are trusted. This can be useful if you have more than one system/" +"certificate you want to connect to and the certificates are issued from the " +"same custom CA." msgstr "" -#: ../system/core-workflows/condition-operators.rst:67 -msgid "Matches if content is present." +#: ../settings/security/ssl-certificates.rst:31 +msgid "Add a Certificate" msgstr "" -#: ../system/core-workflows/condition-operators.rst:68 -msgid "just changed" +#: ../settings/security/ssl-certificates.rst:33 +msgid "" +"To add a custom certificate or a custom CA certificate, head over to the " +"Admin panel > Settings > Security > SSL Certificates. Here you can find a " +"\"Add SSL Certificate\" button. In the dialog you can either select a " +"certificate file or paste the content of the certificate:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:69 -msgid "Matches if content has changed." +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate adding dialog" msgstr "" -#: ../system/core-workflows/condition-operators.rst:71 -#: ../system/core-workflows/condition-operators.rst:75 +#: ../settings/security/ssl-certificates.rst:43 msgid "" -"Only true for the moment of changing content until next form field action/" -"click." +"After selecting a file or pasting the content of the certificate, click on " +"the \"Add\" button to finally upload it to Zammad. Then, the certificates " +"are immediately effective, no restart or similar required." msgstr "" -#: ../system/core-workflows/condition-operators.rst:72 -msgid "just changed to" +#: ../settings/security/ssl-certificates.rst:49 +msgid "" +"Please note that only single certificate files are supported. That means if " +"you want to import a certificate / CA certificate, it must contain **only " +"one** certificate." msgstr "" -#: ../system/core-workflows/condition-operators.rst:73 -msgid "Matches if content has changed to a specified value." -msgstr "" - -#: ../system/core-workflows/condition-operators.rst:76 -msgid "matches regex" +#: ../settings/security/ssl-certificates.rst:54 +msgid "Certificate Overview" msgstr "" -#: ../system/core-workflows/condition-operators.rst:77 -msgid "Matches if value fits to regex rule." +#: ../settings/security/ssl-certificates.rst:56 +msgid "" +"After you added a certificate, you can see a table with information for each " +"added certificate:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:79 -msgid "Matches if no content is present." +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing table of added certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:80 -msgid "starts with" +#: ../settings/security/ssl-certificates.rst:64 +msgid "" +"Here you can download the certificate or delete it, if you don't need it " +"anymore." msgstr "" -#: ../system/core-workflows/condition-operators.rst:81 -msgid "Matches if content starts with specified value." +#: ../settings/security/ssl-certificates.rst:68 +msgid "Deleting Certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:82 -msgid "starts with one of" +#: ../settings/security/ssl-certificates.rst:70 +msgid "" +"If you want to delete a specific certificate, you can do it by clicking on " +"the menu in the actions column and selecting delete:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:83 -msgid "Matches if content starts with one of the specified values." +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate deletion button" msgstr "" -#: ../system/core-workflows/condition-operators.rst:84 -msgid "till (relative)" +#: ../settings/security/ssl-certificates.rst:79 +msgid "Downloading Certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:85 -msgid "Matches if date/time is before a period of time before an event." +#: ../settings/security/ssl-certificates.rst:81 +msgid "" +"If you want to download your certificates, you can do this as well via " +"corresponding action buttons." msgstr "" -#: ../system/core-workflows/condition-operators.rst:86 -msgid "today" +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate download button" msgstr "" -#: ../system/core-workflows/condition-operators.rst:87 -msgid "Matches if date/time is today." +#: ../settings/security/third-party.rst:13 +msgid "Login Providers" msgstr "" -#: ../system/core-workflows/condition-operators.rst:88 -msgid "within last (relative)" +#: ../settings/security/third-party.rst:2 +msgid "Third-Party Applications" msgstr "" -#: ../system/core-workflows/condition-operators.rst:89 +#: ../settings/security/third-party.rst:4 msgid "" -"Matches if date/time content is within specified period of time before now." +"Third party authentication is a great way to help your users to login to " +"Zammad more easily. If the account is yet unknown, Zammad will create a new " +"user automatically, without the user needed to interact (e.g. type in his " +"name). Another big advantage of this feature is that your user doesn't need " +"to remember another password." msgstr "" -#: ../system/core-workflows/condition-operators.rst:91 -msgid "within next (relative)" +#: ../settings/security/third-party.rst:10 +msgid "" +"You can deactivate logging in via :ref:`security_password_login` if any of " +"the mentioned authentication providers are enabled in your instance." msgstr "" -#: ../system/core-workflows/condition-operators.rst:92 +#: ../settings/security/third-party.rst:27 msgid "" -"Matches if date/time content is within specified period of time after now." +"We're currently missing documentation for the following login providers:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:2 -msgid "How do they work?" +#: ../settings/security/third-party.rst:29 +msgid "LinkedIn" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:4 -msgid "" -"Core Workflows are executed according to their priority. If two workflows " -"have the same priority, they are executed in alphabetical order based on " -"their **name**." +#: ../settings/security/third-party.rst:30 +msgid "Weibo" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:8 -msgid "" -"Because of the way Core Workflows work, all changes to attributes are " -"checked with the application server - please see :doc:`limitations` for " -"possible issues." -msgstr "" +#: ../settings/security/third-party.rst:35 +#, fuzzy +msgid "Automatic Account Link on Initial Logon" +msgstr ":doc:`accounts/email-notification`" -#: ../system/core-workflows/how-do-they-work.rst:12 +#: ../settings/security/third-party.rst:37 msgid "" -"Below we're talking about settings that are important and not self-" -"explanatory." +"In general there's two possible options for Zammad on how to deal with " +"already known users as they try to authenticate against a third-party " +"application. By default, Zammad will not automatically link \"unknown\" " +"authentication providers to existing accounts." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:17 +#: ../settings/security/third-party.rst:42 msgid "" -"Choose the object context you want to run the workflow in. This will decide " -"on your available attributes and actions." -msgstr "" - -#: ../system/core-workflows/how-do-they-work.rst:20 -msgid "Ticket objects also have access to the ticket customer." +"This means that the user has to manually link authentication providers to " +"their accounts (for more about this :user-docs:`consult the user " +"documentation `)." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:25 +#: ../settings/security/third-party.rst:46 msgid "" -"Choose in which situation the workflow is applied. Contexts can be combined " -"to avoid duplicate workflows." +"Sometimes this doesn't come in handy as this also means you'll receive error " +"messages about \"email address being in use already\" for (yet) unknown " +"third-party authentication methods." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:30 -msgid "Creation mask" +#: ../settings/security/third-party.rst:50 +msgid "" +"If you want to allow your users to always be able to log in, no matter what, " +"you may want to enable ``Automatic account link on initial logon``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:29 +#: ../settings/security/third-party.rst:None msgid "" -"If selected, your conditions and actions will affect all applicable creation " -"masks." +"Screenshot highlighting the \"Automatic account link on initial logon\"\n" +"setting" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:34 -msgid "Edit mask" -msgstr "" +#: ../settings/security/third-party.rst:60 +#, fuzzy +msgid "Automatic Account Linking Notification" +msgstr ":doc:`accounts/email-notification`" -#: ../system/core-workflows/how-do-they-work.rst:33 +#: ../settings/security/third-party.rst:64 msgid "" -"If selected, your conditions and actions will affect all applicable edit " -"masks." +"To improve security and your users awareness, you can enable Zammad to " +"notify your users when a new third-party application has been linked to " +"their account." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:39 +#: ../settings/security/third-party.rst:68 msgid "" -"Zammad differentiates between selected and saved conditions. These can be " -"combined wherever needed." +"This notification is sent out once per third-party application. Zammad does " +"also mention the method used, e.g.: ``Microsoft``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:42 -msgid "**⚠️ Restrict workflows to specific roles if needed!**" +#: ../settings/security/third-party.rst:71 +msgid "By default this setting is not active (set to ``no``)." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:44 +#: ../settings/security/third-party.rst:0 msgid "" -"By default and unless configured in conditions, workflow rules are executed " -"for **all roles**. This also affects your customers!" +"Screenshot showing sample notification mail after initial\n" +"third-party linking" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:50 -msgid "Selected Conditions" +#: ../settings/security/third-party.rst:85 +msgid "" +"This notification is only sent if the account in question already exists. If " +"the login via the third-party also creates the missing account, the " +"notification will be skipped." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:48 -msgid "" -"These conditions are based on form values and match if an appropriate " -"selection is made (e.g. choosing another group in the ticket without " -"saving). This applies for drafts (active selection) and currently saved " -"values." +#: ../settings/security/third-party.rst:89 +msgid "This means it only affects:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:64 -msgid "Saved Conditions" +#: ../settings/security/third-party.rst:91 +msgid "manual account linking within the third-party page of the users profile" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:53 +#: ../settings/security/third-party.rst:92 msgid "" -"These conditions only match if the selected values are stored in the " -"database. It ignores the current value or selection of the field, as long as " -"the changes are not saved (e.g. performing field operations for an existing " -"ticket, which is viewed/opened by an agent)." +"logging into an existing local account by utilizing the *automatic account " +"link on initial logon* functionality" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:60 +#: ../settings/security/third-party.rst:None msgid "" -"Keep in mind that the value has to be available in the situation where you " -"need it. Otherwise the condition won't match." +"Screenshot showing the \"automatic account linking notification\"\n" +"setting" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:63 -msgid "" -"Example: you can't perform any actions with *saved condition* on a ticket in " -"creation, because there are no saved values at that time." +#: ../settings/security/third-party.rst:100 +msgid "No User Creation on Logon" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:66 +#: ../settings/security/third-party.rst:102 msgid "" -"You can find a description of the condition operators for core workflows :" -"doc:`here `." +"By default, Zammad will create a new user account if the user logs in via a " +"third-party application and the account doesn't exist yet." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:72 +#: ../settings/security/third-party.rst:105 msgid "" -"Which actions should we run on the relevant fields? The possible actions " -"depend on the object type. However, usually you can at least change the " -"visibility and whether the field is mandatory." +"If you want to prevent Zammad from creating new accounts on logon, you can " +"disable this feature by setting ``No user creation on logon`` to ``yes``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:76 -msgid "Be aware that actions are not available for **related** context." +#: ../settings/security/third-party.rst:None +msgid "Screenshot showing the \"no user creation on logon\" setting" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:78 +#: ../settings/security/third-party/facebook.rst:4 msgid "" -"**Example:** Let's assume you are working in the ticket context. While you " -"can have customer *conditions*, you *can't adjust* objects with actions in " -"that scope. That's because this wouldn't have any impact on the ticket " -"dialog. Of course all ticket attributes (state, owner, ...) are available." +"It is possible to create a quick login for your helpdesk via Facebook To do " +"so, you need to follow these steps:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:84 -msgid "" -"Please also have a look at our :doc:`limitations` to be safe from surprises." +#: ../settings/security/third-party/facebook.rst:9 +msgid "Register Facebook App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:88 -msgid "Available Operators" +#: ../settings/security/third-party/facebook.rst:11 +msgid "" +"Visit [https://developers.facebook.com/apps/] and click on \"Add a new App\"" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:90 -msgid "The availability of operators depends on the object type and scope." +#: ../settings/security/third-party/facebook.rst:None +msgid "initial page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:94 -msgid "" -"Please note that actions may or may not restrict API based access to " -"attributes. We're displaying the following icons for your overview to " -"understand these limits better:" +#: ../settings/security/third-party/facebook.rst:17 +msgid "After that enter the app settings" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:0 -msgid "|api| This icon indicates the action affects the API." +#: ../settings/security/third-party/facebook.rst:None +msgid "Create App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:163 -msgid "api" +#: ../settings/security/third-party/facebook.rst:22 +msgid "Navigate to \"Settings\" and fill in this infromation" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:0 -msgid "|ui| This icon indicates the action only affects the web interface." +#: ../settings/security/third-party/facebook.rst:None +msgid "App Settings" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:167 -msgid "ui" +#: ../settings/security/third-party/facebook.rst:27 +msgid "Navigate to app review and Check \"Make [appname] public?\"" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:102 -msgid "show |ui|" +#: ../settings/security/third-party/facebook.rst:None +msgid "App Review" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:102 -msgid "Display the chosen field. Allows setting of values." +#: ../settings/security/third-party/facebook.rst:35 +msgid "Configure Zammad as Facebook App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:109 -msgid "hide |ui|" +#: ../settings/security/third-party/facebook.rst:37 +msgid "" +"Navigate to \"Admin -> Security -> Third Party Applications\" and enter the " +"App ID and the App Secret. You can find this Key in the Dashbard of your " +"Facebok app." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:105 -msgid "" -"Hide the chosen field. However, it technically still allows setting the " -"field." +#: ../settings/security/third-party/facebook.rst:None +msgid "Zammad Configuration" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:108 +#: ../settings/security/third-party/facebook.rst:44 +#: ../settings/security/third-party/github.rst:43 +#: ../settings/security/third-party/gitlab.rst:46 msgid "" -"Please note that the field is **not** gone and still contains an existing " -"value (if set)! Consider *remove* instead, if you want this field to be gone." +"Now you can link accounts via \"Avatar -> Profile -> Link Accounts\" or " +"login via Zammad login page." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:112 -msgid "remove |ui|" +#: ../settings/security/third-party/github.rst:2 +#: ../system/integrations/github.rst:2 +msgid "GitHub" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:112 -msgid "Entirely removes the field. The field value will not be evaluated." +#: ../settings/security/third-party/github.rst:4 +msgid "" +"It is possible to create a quick login for your helpdesk via GitHub. To " +"activate the quick login you need to enable OAuth for GitHub." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:115 -msgid "set mandatory |ui| |api|" +#: ../settings/security/third-party/github.rst:8 +msgid "Register GitHub App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:115 -msgid "Sets the field to mandatory." +#: ../settings/security/third-party/github.rst:10 +msgid "" +"Visit https://www.github.com/settings/applications/new and enter the app " +"settings. As callback URL enter \"https://zammad_host/auth/github/callback\" " +"where zammad_host has to be replaced with your Zammad FQDN" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:118 -msgid "set optional |ui| |api|" +#: ../settings/security/third-party/github.rst:None +msgid "Register OAuth app on www.github.com" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:118 -msgid "Sets the field to optional." +#: ../settings/security/third-party/github.rst:19 +msgid "Configure Zammad as GitHub App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:124 -msgid "add option |ui| |api|" +#: ../settings/security/third-party/github.rst:21 +msgid "" +"Enter the \"APP ID\" and the \"APP SECRET\" from the GitHub OAUTH " +"Applications Dashboard" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:121 -msgid "Allows adding options to tree selects or selects." +#: ../settings/security/third-party/github.rst:None +msgid "GitHub config in Zammad admin interface" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:123 +#: ../settings/security/third-party/github.rst:28 msgid "" -"You have to use the \"remove option\" before performing this action. It " -"allows you to use *existing* configured values." +"After you configured the GitHub credentials and activated the login method, " +"you should see a new icon on the login page." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:128 -msgid "remove option |ui| |api|" +#: ../settings/security/third-party/github.rst:None +msgid "GitHub logo on login page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:127 +#: ../settings/security/third-party/github.rst:34 msgid "" -"Allows removing options from tree selects or selects. It allows you to use " -"*existing* configured values." +"If you click on the icon you will be redirected to GitHub and see something " +"similar to this:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:134 -msgid "set fixed to |ui| |api|" +#: ../settings/security/third-party/github.rst:None +msgid "GitHub oauth page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:131 -msgid "Reduces the available options by your selection." +#: ../settings/security/third-party/github.rst:40 +#: ../settings/security/third-party/gitlab.rst:42 +msgid "" +"When you grant the access you will be redirected to your Zammad instance and " +"logged in as a customer." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:133 -msgid "" -"This reduces your workflows in terms of *add option* and *remove option*." +#: ../settings/security/third-party/gitlab.rst:2 +msgid "Gitlab" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:137 -msgid "fill in |ui|" +#: ../settings/security/third-party/gitlab.rst:4 +msgid "" +"It is possible to create a quick login for your helpdesk via Gitlab. To " +"activate the quick login you need to enable OAuth for Gitlab." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:137 -msgid "Allows filling in of string and integer fields with your values." +#: ../settings/security/third-party/gitlab.rst:8 +msgid "Register Gitlab App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:141 -msgid "fill in empty |ui|" +#: ../settings/security/third-party/gitlab.rst:10 +msgid "To register an app in Gitlab open your profile and select applications." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:140 +#: ../settings/security/third-party/gitlab.rst:12 msgid "" -"Allows filling in of string and integer fields with your values **if the " -"field is empty**." +"As callback URL enter \"https://zammad-fqdn/auth/gitlab/callback\" where " +"zammad-fqdn has to be replaced with your Zammad FQDN" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:144 -msgid "select |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Register OAuth app on gitlab instance" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:144 -msgid "Select a specific value within a select, tree select or boolean field." +#: ../settings/security/third-party/gitlab.rst:18 +msgid "Just select *read_user* under scopes as in the screenshot and save it." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:153 -msgid "auto select |ui|" +#: ../settings/security/third-party/gitlab.rst:21 +msgid "Configure Zammad as Gitlab App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:147 -msgid "Helps users with tree select and select fields:" +#: ../settings/security/third-party/gitlab.rst:23 +msgid "" +"Enter the \"APP ID\" and the \"APP SECRET\" from the Gitlab OAUTH " +"Applications Dashboard and your Gitlab-URL in the \"SITE\" field." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:149 -msgid "" -"If the field has only one option available for selection and no value yet, " -"the value will be automatically set." +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab config in Zammad admin interface" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:152 +#: ../settings/security/third-party/gitlab.rst:30 msgid "" -"This option only works if you have one value and doesn't work if there is " -"more than one option available." +"After you configured the Gitlab credentials and activated the login method, " +"you should see a new icon on the login page." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:157 -msgid "set readonly |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab logo on login page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:156 +#: ../settings/security/third-party/gitlab.rst:36 msgid "" -"Allows you to display an attribute as read only (which means no changes are " -"possible)." +"If you click on the icon you will be redirected to Gitlab and see something " +"similar to this:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:161 -msgid "unset readonly |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab oauth page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:160 +#: ../settings/security/third-party/google.rst:4 msgid "" -"In case a workflow set the field in question to read only, you can undo this " -"with option above." +"With some easy and fast steps, you can enable Zammad to authenticate your " +"users via Google." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:172 -msgid "Stop after match" +#: ../settings/security/third-party/google.rst:8 +msgid "Register a Google App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:174 +#: ../settings/security/third-party/google.rst:10 msgid "" -"Here you can decide if other workflows are executed after the current one." +"First of all, we need to create a new project - you can skip this step if " +"you already have one." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:176 +#: ../settings/security/third-party/google.rst:15 msgid "" -"If set to ``no`` (default), further workflows will be executed if they match " -"the condition. In this case, it is possible that your actions from the " -"current workflow can be overwritten by another workflow." +"Use this link to create a new project: https://console.cloud.google.com/" +"projectcreate" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:180 +#: ../settings/security/third-party/google.rst:18 msgid "" -"If set to ``yes``, no further worflows will be executed after the current " -"one." +"Now expand the menu, expand \"APIs & Services\" and select \"Credentials\". " +"Go to the tab \"OAuth consent screen\" first and ensure to fill in the " +"requested information - without doing so you can't create credentials!" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:184 -msgid "Priority" +#: ../settings/security/third-party/google.rst:None +msgid "Creating a consent screen" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:186 +#: ../settings/security/third-party/google.rst:25 msgid "" -"You can define the sequence, in which the workflows are executed. The " -"default value is ``500``." +"After filling in and saving the consent screen information, you can go to " +"the \"Credentials\" tab and create new \"OAuth client ID\"-Credentials." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:189 +#: ../settings/security/third-party/google.rst:28 msgid "" -"The workflows are executed in ascending order by their priority. That means " -"lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." +"Fill in the necessary information as follows and replace ``zammad_host`` " +"with your FQDN:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:2 -#, fuzzy -msgid "Learn by Example" -msgstr "Primjer" +#: ../settings/security/third-party/google.rst:31 +msgid "**Application type** ``[x] Web application``" +msgstr "" -#: ../system/core-workflows/learn-by-example.rst:4 -msgid "" -"This page provides some basic examples for Core Workflows. Of course you can " -"build much more complex workflows if needed." +#: ../settings/security/third-party/google.rst:34 +msgid "**Authorized JavaScript origins** ``https://zammad_host/``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:7 +#: ../settings/security/third-party/google.rst:37 msgid "" -"To learn about Core Workflows in detail, first go to :doc:`how-do-they-work`." +"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" +"callback``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:10 -#, fuzzy -msgid "Group Based Examples" -msgstr "Primjer" +#: ../settings/security/third-party/google.rst:None +msgid "Adding a new OAuth client ID" +msgstr "" -#: ../system/core-workflows/learn-by-example.rst:12 +#: ../settings/security/third-party/google.rst:43 msgid "" -"All following workflows have the same base configurations. The workflow may " -"not use them all." +"After creating the credentials, go to your Zammad installation and navigate " +"to \"Admin > Security > Third Party Applications\" > Google. Enter your " +"Client ID and Client secret here." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:15 -#, fuzzy -msgid "Groups:" -msgstr "grupa" +#: ../settings/security/third-party/google.rst:None +msgid "Zammad" +msgstr "" -#: ../system/core-workflows/learn-by-example.rst:20 -msgid "Attributes:" +#: ../settings/security/third-party/google.rst:50 +msgid "After submitting, the login via Google can be used." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:22 -msgid "Category (Single tree selection field, not mandatory, agents only)" +#: ../settings/security/third-party/microsoft.rst:2 +msgid "Microsoft" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:23 +#: ../settings/security/third-party/microsoft.rst:4 msgid "" -"Approved (Boolean field, not mandatory, not shown, ``false`` as default)" +"Zammad's Microsoft connection allows your users with Microsoft accounts to " +"login. This works for Azure users as well and can be an alternative to :doc:" +"`/system/integrations/ldap/index`." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:24 -msgid "Operating System (Text field, not mandatory, not shown)" +#: ../settings/security/third-party/microsoft.rst:10 +msgid "" +"This documentation part does not cover our :doc:`📧 Microsoft 365 email " +"channel `." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:25 -msgid "Software used (Single selection field, not mandatory, not shown)" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screenshot showing Microsoft login button on Zammad login screen." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:68 -msgid "Group specific values and fields" +#: ../settings/security/third-party/microsoft.rst:30 +#: ../settings/security/third-party/microsoft.rst:53 +msgid "Supported account types:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:28 +#: ../settings/security/third-party/microsoft.rst:22 msgid "" -"This workflow set depends on the category field. It reduces the available " -"set of values based on the group selected." +"Please note that Zammad only supports these account types (App dependent):" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:33 -msgid "Workflow 2nd Level group" +#: ../settings/security/third-party/microsoft.rst:35 +msgid "Avatars of signing in users:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:35 +#: ../settings/security/third-party/microsoft.rst:33 msgid "" -"This reduces the category options to ``2nd Level/*``, ``Internal/*`` and " -"``Others``. It also sets further required fields to mandatory and visible." -msgstr "" - -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for 2nd level" +"Zammad currently ignores user avatars. If the user is registered with e.g. " +"Gravatar, Zammad will fetch the avatar from there if enabled. See :doc:" +"`Zammad Image Service ` for more." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:43 -msgid "Workflow Support group" +#: ../settings/security/third-party/microsoft.rst:38 +msgid "Step 1 - Register a Microsoft App for Zammad" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:45 +#: ../settings/security/third-party/microsoft.rst:40 msgid "" -"This reduces the category options to ``Support/*``, ``Internal/*`` and " -"``Others``. It also sets further required fields to visible." -msgstr "" - -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for support" +"Login to the `Microsoft Azure Portal `_ and " +"navigate to App registrations to create a new app. Provide the requested " +"information as follows and register your app." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:53 -msgid "Workflow Sales group" +#: ../settings/security/third-party/microsoft.rst:46 +msgid "Name:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:55 +#: ../settings/security/third-party/microsoft.rst:45 msgid "" -"This reduces the category options to ``Sales/*``, ``Internal/*`` and " -"``Others``." +"Any meaningful name fitting, this name will be displayed to users trying to " +"authenticate with this app." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for sales" +#: ../settings/security/third-party/microsoft.rst:49 +msgid "Choose one of the above mentioned account types (see Limitations)." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:68 -#: ../system/integrations/slack.rst:88 -msgid "The Result" +#: ../settings/security/third-party/microsoft.rst:51 +msgid "" +"The correct account type depends on your use case. If you want to use the " +"authentication internal only, choose the first option. If you're unsure, use " +"the \"Help me choose...\" link." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:63 -msgid "" -"This is what the agent would experience with the above workflows in place." +#: ../settings/security/third-party/microsoft.rst:58 +msgid "Redirect URI (optional):" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 +#: ../settings/security/third-party/microsoft.rst:56 msgid "" -"Workflow shows objects and limits options based on selections on the group" +"Select web and provide your callback URL. The callback URL looks like this: " +"``https://zammad.domain.tld/auth/microsoft_office365/callback``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:90 -msgid "Approval process" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to register a Microsoft app" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:71 -msgid "" -"In this case ``approved`` is visible to agents by default. For this " -"workflow, an additional role ``Approval person`` is required (no further " -"permissions)." +#: ../settings/security/third-party/microsoft.rst:71 +msgid "Within **API permissions** add the following permissions:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that restricts an approval attribute to specific roles" +#: ../settings/security/third-party/microsoft.rst:69 +msgid "``User.Read``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:81 -msgid "" -"This workflow may work best in combination with a :doc:`trigger ` but technically, this is not required." +#: ../settings/security/third-party/microsoft.rst:71 +msgid "Contacts" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:84 -msgid "" -"Select fields may be a better approach because they allow more values than " -"just a simple ``true`` or ``false``." +#: ../settings/security/third-party/microsoft.rst:71 +msgid "``Contacts.Read``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 +#: ../settings/security/third-party/microsoft.rst:73 msgid "" -"Workflow fixes possible values of \"Approved ?\" to a specific selection " -"depending on the users role" +"You can find these permissions within *Microsoft Graph → Delegated " +"permissions*." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:103 -msgid "State dependent mandatory fields" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to add required API permissions" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:93 +#: ../settings/security/third-party/microsoft.rst:80 msgid "" -"This workflow sets ``Category`` to mandatory if the agent wants to set the " -"states ``closed`` or ``pending close`` to enforce categorization." +"Within **Certificates & secrets** create a new client secret. Note down the " +"returned secret **value** for later. **Do not** use the secret ID!" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that sets fields to mandatory on specific states" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to create a new app secret" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 +#: ../settings/security/third-party/microsoft.rst:88 msgid "" -"Workflow sets category field to mandatory upon choosing closed or pending " -"close as state" +"From **Overview** copy your apps *Application (client) ID*. If you're using " +"a single tenant app, please also copy *Directory (tenant) ID*. You now have " +"all required information for Zammad." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:106 -msgid "Manual Ticket Handover Process" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to retreive application client and tenant IDs" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:108 -msgid "This example covers the handover of a ticket from one agent to another:" +#: ../settings/security/third-party/microsoft.rst:98 +msgid "Step 2 - Add App Credentials to Zammad" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:110 +#: ../settings/security/third-party/microsoft.rst:100 msgid "" -"When the ticket owner is modified, a new text field (\"Handover\") shows up " -"for a comment" +"Navigate to Security > Third-party Applications (Tab) within Zammad's admin " +"settings. Scroll down to the section *Authentication via Microsoft* and fill " +"in the required information." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:112 -msgid "" -"This may only be visible when the owner is changed, therefore it has to be " -"hidden in general" +#: ../settings/security/third-party/microsoft.rst:105 +msgid "App ID:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:114 -msgid "The input in this handover text field is mandatory" +#: ../settings/security/third-party/microsoft.rst:105 +msgid "This is your *Application (client) ID*." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:115 -msgid "" -"After submitting changes, the value of the handover field must be added as " -"an note to the ticket (via trigger)" +#: ../settings/security/third-party/microsoft.rst:108 +msgid "App secret:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:121 -msgid "Hiding handover field" +#: ../settings/security/third-party/microsoft.rst:108 +msgid "This is your *client secret* (value)." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Hiding the handover field in core workflows" +#: ../settings/security/third-party/microsoft.rst:113 +msgid "App Tenant ID:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:126 -msgid "Showing handover field and setting it to mandatory" +#: ../settings/security/third-party/microsoft.rst:111 +msgid "" +"**optional** only required for apps that use account type *Accounts in this " +"organizational directory only (Default Directory only - Single tenant).*" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Showing the handover field and set it as mandatory" +#: ../settings/security/third-party/microsoft.rst:115 +msgid "" +"Apply your settings by pressing submit and activate *Authentication via " +"Microsoft*." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:131 -msgid "Trigger writing handover input to a new article" +#: ../settings/security/third-party/microsoft.rst:None +msgid "" +"Screencast showing how to add app credentials and activating the\n" +"authentication method" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Write handover content to a new article" +#: ../settings/security/third-party/saml.rst:2 +msgid "SAML" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:133 +#: ../settings/security/third-party/saml.rst:4 msgid "" -"As a result, the ticket includes an article of the type note which includes " -"the predefined text and the handover comment." +"Connect your SAML (Security Assertion Markup Language) identity provider as " +"a single sign-on (SSO) method." msgstr "" -#: ../system/core-workflows/limitations.rst:6 -msgid "Core Workflows do not replace Triggers" +#: ../settings/security/third-party/saml.rst:7 +msgid "" +"SAML is an open standard for SSO authentication (among other things). Sign-" +"ins are shared across multiple **service providers** and managed by a " +"central **identity provider** (IdP)." msgstr "" -#: ../system/core-workflows/limitations.rst:5 +#: ../settings/security/third-party/saml.rst:11 msgid "" -"Workflows manipulate the behavior of fields. However, they do not set values " -"in fields because of actions." +"In this case, the service provider is Zammad, and the IdP is a software " +"service that you either host or subscribe to (*e.g.,* `Keycloak `_, `Redhat SSO Server `_, `ADFS `_, or `Okta `_)." msgstr "" -#: ../system/core-workflows/limitations.rst:16 -msgid "API calls are only partly affected" +#: ../settings/security/third-party/saml.rst:18 +msgid "" +"This guide assumes you are already using SAML within your organization (i." +"e., that your IdP is fully set up)." msgstr "" -#: ../system/core-workflows/limitations.rst:9 +#: ../settings/security/third-party/saml.rst:21 msgid "" -"Some options affect UI only and thus do not restrict responses and calls." +"Please note: Our instructions are based on connecting Zammad with Keycloak." msgstr "" -#: ../system/core-workflows/limitations.rst:11 -msgid "This affects the following actions:" +#: ../settings/security/third-party/saml.rst:25 +msgid "Step 1: Configure Your IdP" msgstr "" -#: ../system/core-workflows/limitations.rst:13 -msgid "select" +#: ../settings/security/third-party/saml.rst:28 +msgid "Add Zammad as a Client/App" msgstr "" -#: ../system/core-workflows/limitations.rst:14 -msgid "auto select" -msgstr "" - -#: ../system/core-workflows/limitations.rst:15 -msgid "show" -msgstr "" - -#: ../system/core-workflows/limitations.rst:16 -msgid "hide" -msgstr "" - -#: ../system/core-workflows/limitations.rst:25 -msgid "Some fields stay unavailable to customers" -msgstr "" - -#: ../system/core-workflows/limitations.rst:19 +#: ../settings/security/third-party/saml.rst:30 msgid "" -"For technical and security reasons, some default fields (the pale ones you " -"can't edit) stay unavailable for display and usage on customer permissions." +"Import Zammad into your IdP using the XML configuration found at ``https://" +"your.zammad.domain/auth/saml/metadata``." msgstr "" -#: ../system/core-workflows/limitations.rst:23 +#: ../settings/security/third-party/saml.rst:33 msgid "" -"If you require your customers to change e.g. priorities, please consider " -"using workarounds via :doc:`/system/objects` and :doc:`/manage/trigger`." +"If your IdP doesn't support XML import, you will have to configure Zammad as " +"a new client/app manually using the above XML metadata file for reference." msgstr "" -#: ../system/core-workflows/limitations.rst:29 -msgid "Ticket title changes not supported in edit mask" +#: ../settings/security/third-party/saml.rst:36 +msgid "For instance, when you see this tag:" msgstr "" -#: ../system/core-workflows/limitations.rst:28 +#: ../settings/security/third-party/saml.rst:42 msgid "" -"It is currently not possible to perform changes of the ticket title in the " -"edit mask (e.g. renaming, set to read-only)." +"Set the **Assertion Consumer Service Binding URL** (sometimes also listed as " +"**Valid Redirect URIs**) to ``http://your.zammad.domain/auth/saml/callback``." msgstr "" -#: ../system/core-workflows/limitations.rst:37 -msgid "What is out of scope of Core Workflows?" +#: ../settings/security/third-party/saml.rst:47 +msgid "Set Up User Attribute Mapping" msgstr "" -#: ../system/core-workflows/limitations.rst:32 +#: ../settings/security/third-party/saml.rst:49 msgid "" -"There are some things that would count as workflow but are either done via :" -"doc:`/manage/trigger` or :doc:`/manage/scheduler`." +"Zammad requests the following user attributes (or “properties”) from the IdP:" msgstr "" -#: ../system/core-workflows/limitations.rst:35 -msgid "Such as (but not limited to):" +#: ../settings/security/third-party/saml.rst:51 +msgid "Email address (``email``)" msgstr "" -#: ../system/core-workflows/limitations.rst:37 -msgid "up- or downgrade permissions of users" +#: ../settings/security/third-party/saml.rst:52 +msgid "Full name (``name``)" msgstr "" -#: ../system/core-workflows/limitations.rst:38 -msgid "affecting article creation or listing" +#: ../settings/security/third-party/saml.rst:53 +msgid "Given name (``first_name``)" msgstr "" -#: ../system/data-privacy.rst:2 -msgid "Data Privacy" +#: ../settings/security/third-party/saml.rst:54 +msgid "Family name (``last_name``)" msgstr "" -#: ../system/data-privacy.rst:4 +#: ../settings/security/third-party/saml.rst:56 msgid "" -"For compliance with GDPR and other data privacy laws, you may wish to " -"**permanently delete users from the system**, along with **all of their " -"associated tickets**." +"You may need to set up “mappers” (or “mappings”) to tell your IdP how user " +"attributes in SAML correspond to those in Zammad. For a more detailed " +"breakdown, refer to the XML metadata file referenced in the previous section." 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 `!" +#: ../settings/security/third-party/saml.rst:62 +msgid "Per-IdP Instructions" msgstr "" -#: ../system/data-privacy.rst:12 -msgid "" -"Access to this panel requires ``admin.data_privacy`` permissions (introduced " -"in Zammad 3.5)." +#: ../settings/security/third-party/saml.rst:102 +msgid "Keycloak" msgstr "" -#: ../system/data-privacy.rst:15 +#: ../settings/security/third-party/saml.rst:65 msgid "" -"On older systems that have not been updated yet, customers can also be :docs:" -"`deleted via the Zammad console `." -msgstr "" - -#: ../system/data-privacy.rst:22 -msgid "User deletion dialog in the Data Privacy panel" +"**To add Zammad as a client,** save the XML configuration to disk (``https://" +"your.zammad.domain/auth/saml/metadata``) and use **Clients > Clients list > " +"Import client** in the Keycloak admin panel." msgstr "" -#: ../system/data-privacy.rst:22 +#: ../settings/security/third-party/saml.rst:70 msgid "" -"The user deletion dialog lists some of the tickets that will be removed from " -"the system along with the user." +"To help Zammad **match its own user accounts to Keycloak users**, create a " +"user attribute (or “property”) mapper. In **Clients list**, click on your " +"newly created Client ID, choose the tab **Client scopes** and click on the " +"link which refers to your Zammad instance. Choose **Add mapper > By " +"configuration > User Property** and create a mapper with the following " +"entries:" msgstr "" -#: ../system/data-privacy.rst:27 -msgid "Deleting Users via GUI" +#: ../settings/security/third-party/saml.rst:78 +msgid "**Name**" msgstr "" -#: ../system/data-privacy.rst:29 -msgid "🔥 **All deletions are FINAL!**" +#: ../settings/security/third-party/saml.rst:80 +msgid "**Mapper Type**" msgstr "" -#: ../system/data-privacy.rst:31 -msgid "Once you click “Delete”, the action cannot be canceled or undone." +#: ../settings/security/third-party/saml.rst:81 +msgid "``User Property``" msgstr "" -#: ../system/data-privacy.rst:33 -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." +#: ../settings/security/third-party/saml.rst:82 +msgid "**Property**" msgstr "" -#: ../system/data-privacy.rst:36 -msgid "**The following records cannot be deleted:**" +#: ../settings/security/third-party/saml.rst:83 +msgid "``emailAddress``" msgstr "" -#: ../system/data-privacy.rst:38 -msgid "your own account" +#: ../settings/security/third-party/saml.rst:84 +msgid "**SAML Attribute Name**" msgstr "" -#: ../system/data-privacy.rst:39 -msgid "the system's last remaining administrator account" +#: ../settings/security/third-party/saml.rst:86 +msgid "**SAML Attribute NameFormat**" msgstr "" -#: ../system/data-privacy.rst:42 -msgid "Step 1: Find a User / Confirm Deletion" +#: ../settings/security/third-party/saml.rst:87 +msgid "``basic``" msgstr "" -#: ../system/data-privacy.rst:44 -msgid "There are three ways to access the user deletion dialog:" +#: ../settings/security/third-party/saml.rst:89 +msgid "" +"In the example above, we're telling Zammad that whenever it receives a SAML " +"login request, it should take the ``email`` property from Keycloak, look for " +"a Zammad user with the same ``email`` attribute, and create a new session " +"for that user." msgstr "" -#: ../system/data-privacy.rst:51 -msgid "**from the user's profile**" +#: ../settings/security/third-party/saml.rst:95 +msgid "" +"If your Keycloak users' email addresses are stored on another property (*e." +"g.,* ``username``), adjust accordingly." msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Accessing the user deletion dialog in a user profile" +#: ../settings/security/third-party/saml.rst:98 +msgid "" +"Back in **Settings**, enter the Client ID (``https://your.zammad.domain/auth/" +"saml/metadata``) in the field **Master SAML Processing URL**." msgstr "" -#: ../system/data-privacy.rst:51 -msgid "Click **Action > Delete**." +#: ../settings/security/third-party/saml.rst:101 +msgid "You also need to enable **Sign assertions**." msgstr "" -#: ../system/data-privacy.rst:58 -msgid "**in the “Manage > Users” Admin Panel**" +#: ../settings/security/third-party/saml.rst:105 +msgid "Step 2: Configure Zammad" msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Accessing the user deletion dialog under “Users” in the Admin Panel" +#: ../settings/security/third-party/saml.rst:107 +msgid "" +"Enable SAML and enter your IdP's details in the Admin Panel under **Settings " +"> Security > Third Party Applications > Authentication via SAML**:" msgstr "" -#: ../system/data-privacy.rst:58 -msgid "Use the **⋮ Actions** menu for the target user." +#: ../settings/security/third-party/saml.rst:None +msgid "Example configuration of SAML part 1" msgstr "" -#: ../system/data-privacy.rst:66 ../system/data-privacy.rst:104 -msgid "**in the “System > Data Privacy” Admin Panel**" +#: ../settings/security/third-party/saml.rst:119 +msgid "Display name" msgstr "" -#: ../system/data-privacy.rst:0 +#: ../settings/security/third-party/saml.rst:116 msgid "" -"Accessing the user deletion dialog under “Data Privacy” in the Admin Panel" +"Allows you to define a custom button name for SAML. This helps your users to " +"understand better what the button on the login page does." msgstr "" -#: ../system/data-privacy.rst:65 -msgid "" -"Use the **New Deletion Task** button. Search for users by name or email " -"address." +#: ../settings/security/third-party/saml.rst:119 +msgid "Defaults to ``SAML``." msgstr "" -#: ../system/data-privacy.rst:79 -msgid "**Delete organizations**" +#: ../settings/security/third-party/saml.rst:123 +msgid "IDP SSO target URL" msgstr "" -#: ../system/data-privacy.rst:69 +#: ../settings/security/third-party/saml.rst:122 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:" +"This is the target URL Zammad shall redirect to when the user presses the " +"SAML button. For Keycloak, this needs to look like https://your.domain/" +"realms/your-realm/protocol/saml" msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Deleting an organization via the user deletion dialog" +#: ../settings/security/third-party/saml.rst:127 +msgid "IDP single logout target URL" msgstr "" -#: ../system/data-privacy.rst:78 +#: ../settings/security/third-party/saml.rst:126 msgid "" -"If this option does not appear, make sure there are no pending deletion " -"tasks for other customers from this organization." +"This is the URL to which the single logout request and response should be " +"sent." msgstr "" -#: ../system/data-privacy.rst:82 -msgid "Step 2: Monitor Deletion Job Status" +#: ../settings/security/third-party/saml.rst:131 +msgid "IDP certificate" msgstr "" -#: ../system/data-privacy.rst:84 +#: ../settings/security/third-party/saml.rst:130 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:" +"The public certificate of your IDP for Zammad to verify during the callback " +"phase." msgstr "" -#: ../system/data-privacy.rst:98 -msgid "**in the Activity Stream**" +#: ../settings/security/third-party/saml.rst:145 +msgid "IDP certificate fingerprint" msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Activity Stream showing data privacy tasks" +#: ../settings/security/third-party/saml.rst:134 +msgid "" +"The fingerprint of your IDPs public certificate to verify during callback " +"phase." msgstr "" -#: ../system/data-privacy.rst:94 -msgid "" -"For each deleted user, the Activity Stream will be updated twice—once when " -"the task is created, and once when it's complete." +#: ../settings/security/third-party/saml.rst:137 +msgid "🔏 **For the IdP certificate / certificate fingerprint:**" msgstr "" -#: ../system/data-privacy.rst:97 +#: ../settings/security/third-party/saml.rst:139 msgid "" -"These notifications are only visible to users with ``admin.data_privacy`` " -"permissions." +"Provide **only one or the other**—do not provide both! (Between the two, we " +"recommend the signing certificate itself: fingerprints use SHA-1, which `has " +"been broken for a while now `_.)" msgstr "" -#: ../system/data-privacy.rst:0 +#: ../settings/security/third-party/saml.rst:144 msgid "" -"The task list within Data Privacy shows removals being in progress and " -"completed." +"**Keycloak users:** Find your certificate in the Keycloak admin panel under " +"**Realm Settings > Keys > Algorithm: RS256 > Certificate**." msgstr "" -#: ../system/data-privacy.rst:107 -msgid "Frequently Asked Questions" -msgstr "" - -#: ../system/data-privacy.rst:121 -msgid "What happens if I receive an email from a deleted customer?" +#: ../settings/security/third-party/saml.rst:151 +msgid "Name identifier format" msgstr "" -#: ../system/data-privacy.rst:110 +#: ../settings/security/third-party/saml.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." +"This is the unique identifiers field type. Usually it should be ``urn:oasis:" +"names:tc:SAML:1.1:nameid-format:emailAddress``." msgstr "" -#: ../system/data-privacy.rst:115 -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**." +#: ../settings/security/third-party/saml.rst:151 +msgid "Zammad **expects an email address as unique identifier**!" msgstr "" -#: ../system/data-privacy.rst:130 -msgid "What about user information stored in internal notes or other messages?" +#: ../settings/security/third-party/saml.rst:155 +msgid "UID attribute name" msgstr "" -#: ../system/data-privacy.rst:124 +#: ../settings/security/third-party/saml.rst:154 msgid "" -"The deletion process removes **user accounts and associated tickets only**." +"Here you can define an attribute that uniquely identifies the user. If " +"unset, the name identifier returned by the IDP is used." msgstr "" -#: ../system/data-privacy.rst:126 +#: ../settings/security/third-party/saml.rst:None +msgid "Example configuration of SAML part 2" +msgstr "" + +#: ../settings/security/third-party/saml.rst:163 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." +"Decide if the certificate for the connection to the IdP service has to be " +"verified or not (default: ``yes``)." msgstr "" -#: ../system/data-privacy.rst:137 -msgid "I deleted an user and can still see a message they sent!" +#: ../settings/security/third-party/saml.rst:169 +msgid "Signing & Encrypting" msgstr "" -#: ../system/data-privacy.rst:133 +#: ../settings/security/third-party/saml.rst:169 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." +"Define if you want to sign, encrypt, do both or nothing for the requests." msgstr "" -#: ../system/data-privacy.rst:141 -msgid "I removed a customer, now my reporting is off!" +#: ../settings/security/third-party/saml.rst:179 +msgid "Certificate (PEM)" msgstr "" -#: ../system/data-privacy.rst:140 +#: ../settings/security/third-party/saml.rst:172 msgid "" -"When removing users and their tickets, all references are removed. This also " -"affects e.g. Reporting - these information are lost." +"Paste the public certificate of your Zammad SAML client, if you want to " +"encrypt the requests." msgstr "" -#: ../system/data-privacy.rst:145 -msgid "How long does Zammad store created tasks?" +#: ../settings/security/third-party/saml.rst:175 +msgid "Make sure the certificate is:" msgstr "" -#: ../system/data-privacy.rst:144 -msgid "" -"Please see the on-premise data section of the :docs:`data privacy ` chapter." +#: ../settings/security/third-party/saml.rst:177 +msgid "already valid and not yet expired" msgstr "" -#: ../system/data-privacy.rst:150 -msgid "What about re-assigned tickets? I want to delete them, too." +#: ../settings/security/third-party/saml.rst:178 +msgid "no CA certificate" msgstr "" -#: ../system/data-privacy.rst:148 -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." +#: ../settings/security/third-party/saml.rst:179 +msgid "valid for signing and encrypting" msgstr "" -#: ../system/data-privacy.rst:154 -msgid "Why are there so many deletion task entries, I didn't create them!" +#: ../settings/security/third-party/saml.rst:185 +msgid "Private key (PEM)" msgstr "" -#: ../system/data-privacy.rst:153 +#: ../settings/security/third-party/saml.rst:182 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." -msgstr "" - -#: ../system/integrations/checkmk/admin-panel-reference.rst:2 -msgid "Admin Panel Reference" +"Paste the private key of your Zammad SAML client here, if you want to sign " +"the requests." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:None -msgid "Screenshot of Checkmk settings overview" +#: ../settings/security/third-party/saml.rst:185 +msgid "Make sure the key is an RSA key with a length of at least 2048 bits." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:12 -msgid "" -"Which :doc:`group ` should Checkmk tickets be assigned " -"to as a default (*i.e.,* when none is specified)?" +#: ../settings/security/third-party/saml.rst:188 +msgid "Private key secret" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:15 -msgid "(Applies to :ref:`API alerts ` only.)" +#: ../settings/security/third-party/saml.rst:188 +msgid "If your private key is secured with a secret, you can provide it here." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:21 -msgid "Auto close" +#: ../settings/security/third-party/saml.rst:192 +msgid "Your callback URL" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:18 +#: ../settings/security/third-party/saml.rst:191 msgid "" -"Should Zammad automatically close tickets if a service has recovered on its " -"own?" +"This URL is needed for your IdP configuration so it knows where to redirect " +"to after successful authentication." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:21 -msgid "(Agents will receive notifications for such closures as appropriate.)" +#: ../settings/security/third-party/saml.rst:194 +msgid "" +"After saving your input by clicking on the \"Submit\" button, Zammad " +"verifies the provided keys/certificates (e.g. if they are valid for signing/" +"encrypting and if they aren't expired)." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:30 -msgid "Auto-close state" +#: ../settings/security/third-party/saml.rst:199 +msgid "" +"See :ref:`automatic account linking ` for details " +"on how to link existing Zammad accounts to IdP accounts." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:24 -msgid "What ticket state should be applied when “auto-closing” a ticket?" -msgstr "" +#: ../settings/security/third-party/saml.rst:205 +#, fuzzy +msgid "Automatic account linking doesn't work" +msgstr ":doc:`accounts/email-notification`" -#: ../system/integrations/checkmk/admin-panel-reference.rst:26 +#: ../settings/security/third-party/saml.rst:206 msgid "" -"You can choose from the seven built-in ticket states. If these states aren't " -"enough for you, you can :ref:`define a new ticket state ` for this purpose as well. This can be useful for tracking " -"tickets with :doc:`reports `, for example." +"Have you double-checked your IdP's user attribute mapping configuration?" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:35 -#: ../system/integrations/cti/includes/recent-logs.include.rst:2 -#: ../system/integrations/ldap/index.rst:74 -#: ../system/integrations/pgp/index.rst:106 -msgid "Recent Logs" +#: ../settings/security/third-party/twitter.rst:4 +msgid "" +"It is possible to create a quick login for your helpdesk via Twitter. To do " +"so, you need to follow these steps:" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:None -msgid "Screenshot of Checkmk \"Recent Logs\" section" +#: ../settings/security/third-party/twitter.rst:8 +msgid "Register Twitter App" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:41 -msgid "" -"If you're having trouble getting Zammad and Checkmk to play nicely together, " -"this section can help you troubleshoot." +#: ../settings/security/third-party/twitter.rst:10 +msgid "Go to https://dev.twitter.com/apps and login with your account." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:44 -msgid "" -"It contains a record of the fifty most recent transactions that Zammad knows " -"about, including each one's request/response details and return status." +#: ../settings/security/third-party/twitter.rst:15 +msgid "Click on \"Create App\"" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:2 -msgid "API Reference" +#: ../settings/security/third-party/twitter.rst:None +msgid "new app page" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:4 +#: ../settings/security/third-party/twitter.rst:20 msgid "" -"For most users, :ref:`the sample scripts from the Setup Guide ` will do the job just fine. But if you want more fine-grained control" -"—for instance, to create high- and low-priority tickets for different types " -"of system events—then you'll have to customize the data those scripts send " -"to Zammad." +"Enter app settings. As \"Callback URL\" you need to enter ``https://" +"zammad_host/api/v1/external_credentials/twitter/callback``. You need to " +"replace ``zammad_host`` with the domain of your Zammad system." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:15 +#: ../settings/security/third-party/twitter.rst:24 msgid "" -"This custom script will automatically set all tickets it creates to **high " -"priority** and **assign them to charlie@chrispresso.com**." +"After the app has been created, update the application icon and organization " +"attributes." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:32 -msgid "How Does it Work?" +#: ../settings/security/third-party/twitter.rst:None +msgid "set permissions to receive and send direct messages" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:34 +#: ../settings/security/third-party/twitter.rst:30 msgid "" -"There are two kinds of data you can pass to the API, both in the form of key-" -"value pairs:" +"Next we need to set ``read, write and access direct messages`` permissions " +"for the app." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:44 -msgid "Checkmk parameters" +#: ../settings/security/third-party/twitter.rst:None +msgid "click on Keys & Access Token, note them" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:38 +#: ../settings/security/third-party/twitter.rst:36 msgid "" -"are required, and make up the **contents** of the resulting tickets/" -"articles. They also determine whether an event creates a new ticket or " -"updates/closes an existing one." +"Go to \"Keys and Access Token\" tab and note the \"Consumer Key\" and " +"\"Consumer Secret\"." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:42 +#: ../settings/security/third-party/twitter.rst:40 +msgid "Configure Zammad as Twitter App" +msgstr "" + +#: ../settings/security/third-party/twitter.rst:42 msgid "" -"These are the only values used in the sample scripts. **Use them as-is**; " -"technically, they can be customized, but it's hard to imagine a good reason " -"for it." +"Go to \"Admin > Security > Twitter > Third Party Applications > Twitter\" " +"Section." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:52 -msgid "Ticket attributes" +#: ../settings/security/third-party/twitter.rst:None +msgid "Admin > Security > Third Party Applications" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:47 +#: ../settings/security/third-party/twitter.rst:48 msgid "" -"are optional, and can be used to **adjust settings** on newly created " -"tickets (*e.g.,* set the owner, group, priority, or state)." +"Fill in the \"Twitter Key\" and the \"Twitter Secret\" and click the " +"\"Submit\" button." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:50 +#: ../settings/security/third-party/twitter.rst:51 msgid "" -"If you want to customize your Checkmk alert script, do it with these. Simply " -"add an extra “form” option for each one (``-F \"key=value\"``) to your " -"script's ``curl`` command line, as in the example above." +"Now you can link accounts via \"Avatar > Profile > Link Accounts\" or login " +"via Zammad login page." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:54 -msgid "💡 **It's just an API endpoint!**" +#: ../settings/security/two-factor.rst:11 +msgid "Two-factor Authentication Methods" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:56 -msgid "" -"When using Checkmk integration, messages need to be formatted in a certain " -"way, but that *doesn't mean the messages actually have to come from Checkmk*." -msgstr "" +#: ../settings/security/two-factor.rst:2 +msgid "Two-Factor Authentication" +msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:59 +#: ../settings/security/two-factor.rst:4 msgid "" -"If you use another monitoring tool that's not officially supported by " -"Zammad, there's probably a way to make it work with your Checkmk callback " -"URL." +"Two-factor authentication (2FA) enhances the security of Zammad accounts by " +"adding an extra layer of verification beyond a password. It requires users " +"to provide two different types of authentication factors, typically " +"something they know (like a password) and something they possess (like a " +"mobile device or a security token), to ensure that only authorized " +"individuals can access the account." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:63 -msgid "Checkmk Parameters" +#: ../settings/security/two-factor.rst:19 +msgid "Enable Recovery Codes" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:65 +#: ../settings/security/two-factor.rst:21 msgid "" -"When a notification is received, Zammad creates a new article containing the " -"details of the event that triggered it:" +"Recovery codes are one-time use security codes that can be used by the user " +"if they lose access to their other two-factor authentication methods. They " +"cannot be used on their own, they can only be activated if at least one two-" +"factor authentication method is enabled." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:None -msgid "Checkmk article body" +#: ../settings/security/two-factor.rst:None +msgid "Enable Recovery Codes Setting" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:72 +#: ../settings/security/two-factor.rst:30 msgid "" -"These details come from the fields listed below, which correspond to " -"parameters provided by Checkmk (``$NOTIFY_*``)." +"Recovery codes can only be used as a backup method. If enabled, they will be " +"automatically generated for the user once they set up their initial two-" +"factor authentication method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:75 -msgid "**Required fields are marked with an asterisk (\\*).**" +#: ../settings/security/two-factor.rst:34 +msgid "" +"The user will be asked to print out or save the generated recovery codes in " +"a safe place. Once used, a recovery code cannot be reused." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:79 -msgid "event_id\\*" +#: ../settings/security/two-factor.rst:37 +msgid "" +"Users will also have an option to regenerate their recovery codes at any " +"time, which invalidates already existing recovery codes and provides them " +"with a list of fresh codes." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:78 +#: ../settings/security/two-factor.rst:41 msgid "" -"A unique ID for the system event. (``$NOTIFY_SERVICEPROBLEMID`` / " -"``$NOTIFY_HOSTPROBLEMID``)" +"After you enable this setting, when the user completes a setup of their " +"initial two-factor authentication method, they will be presented with a list " +"of recovery codes and instructed to save them for later use." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:86 -msgid "host\\*" +#: ../settings/security/two-factor.rst:None +msgid "Recovery Codes Generation Modal Dialog" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:82 -msgid "" -"The hostname of the system that the event originated from. " -"(``$NOTIFY_HOSTNAME``)" +#: ../settings/security/two-factor.rst:50 +msgid "Enforce the Set Up of the Two-Factor Authentication" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:85 +#: ../settings/security/two-factor.rst:52 msgid "" -"Used to determine if a new event belongs to an existing ticket. Also used in " -"the subject line of the resulting article (“ is ”)." +"In case you wish to require your users to set up at least one two-factor " +"authentication method for their account, you can do this by selecting " +"specific user roles the requirement applies to in **Enforced for user " +"roles** setting. Of course you must have at least one two-factor " +"authentication method enabled for this setting to take effect." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:96 -msgid "service" +#: ../settings/security/two-factor.rst:None +msgid "Enforced for User Roles Setting" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:89 +#: ../settings/security/two-factor.rst:62 msgid "" -"The name of the service that the event originated from. " -"(``$NOTIFY_SERVICEDESC``)" +"After you change this setting, if the user has one of the selected roles on " +"their account, they will be forced to set up the two-factor authentication " +"upon next sign in or application reload." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:92 -msgid "Used to determine if a new event belongs to an existing ticket." +#: ../settings/security/two-factor.rst:66 +msgid "" +"A modal dialog with instructions will be shown, and they will not be able to " +"do any work before they set up at least one two-factor method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:94 -#: ../system/integrations/checkmk/api-reference.rst:110 -msgid "Displayed as ``-`` when omitted." +#: ../settings/security/two-factor.rst:None +msgid "Modal Dialog for Enforcing Two-Factor Authentication Set Up" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:104 -msgid "state\\*" +#: ../settings/security/two-factor.rst:74 +msgid "Reset Two-Factor Authentication for a Specific User" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:99 +#: ../settings/security/two-factor.rst:76 msgid "" -"The current state of the service or host in question. " -"(``$NOTIFY_SERVICESTATE`` / ``$NOTIFY_HOSTSTATE``)" +"In case an user isn't able to login anymore because of an inaccessible " +"second factor, you can reset the user's 2FA method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:102 +#: ../settings/security/two-factor.rst:79 msgid "" -"Used to detect when a ticket should be auto-closed (*i.e.,* on ``OK``/" -"``UP``). Also used in the subject line of the resulting article (“ is " -"”)." +"To do this, go to the user management and search for the relevant user. " +"After you found the account, click the button in the action column and " +"select \"Manage Two-Factor Authentication\":" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:110 -msgid "text" +#: ../settings/security/two-factor.rst:None +msgid "Context menu in action column in user management" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:107 +#: ../settings/security/two-factor.rst:87 msgid "" -"The output of the process that triggered the event. " -"(``$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" +"After selecting this, you can see a dialog where you can either reset one " +"2FA method or reset all of the user's 2FA methods:" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:121 +#: ../settings/security/two-factor.rst:None +msgid "Dialog for resetting user's 2FA method" +msgstr "" + +#: ../settings/security/two-factor.rst:94 msgid "" -"The Object Manager attribute panel displays built-in and custom\n" -"attribute names." +"Choose the fitting one, click on the corresponding \"Remove ...\" button and " +"confirm your action. The user now has to setup a new 2FA method, depending " +"on your 2FA configuration." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:121 -msgid "Find a complete list of ticket attributes in the Object Manager." +#: ../settings/security/two-factor/authenticator-app.rst:2 +msgid "Authenticator App" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:123 +#: ../settings/security/two-factor/authenticator-app.rst:4 msgid "" -"Ticket attributes are entirely optional, and can be used to customize the " -"tickets that Checkmk creates. (Note that these attributes will be ignored if " -"a new event belongs to an existing ticket.)" +"The authenticator app method is a type of two-factor authentication that " +"uses a mobile application to generate one-time codes for account " +"verification. After setting up the authenticator app on their device, the " +"user links it to their Zammad account." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:128 +#: ../settings/security/two-factor/authenticator-app.rst:12 msgid "" -"Why would you want to do this? Maybe you have only one IT guy, and all " -"system monitoring issues should be automatically assigned to him. Or, maybe " -"you're creating multiple notification rules so that database outages take " -"higher priority than disk space warnings." +"When logging in, the user is prompted to enter a time-sensitive code " +"generated by the app, in addition to their password. This code acts as the " +"second factor of authentication, providing an extra layer of security as it " +"changes periodically and is unique to the user's device." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:135 -msgid "In most cases, you'll probably want to set one of the following:" +#: ../settings/security/two-factor/authenticator-app.rst:None +msgid "Security Code in Google Authenticator App" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:137 -msgid "group" -msgstr "grupa" - -#: ../system/integrations/checkmk/api-reference.rst:139 -msgid "state" -msgstr "status" - -#: ../system/integrations/checkmk/api-reference.rst:140 -msgid "priority" -msgstr "prioritet" - -#: ../system/integrations/checkmk/api-reference.rst:142 +#: ../settings/security/two-factor/authenticator-app.rst:22 msgid "" -"but in practice, you can set almost any attribute, including :doc:`custom " -"ones you created through the Object Manager `." +"The app generates codes based on a shared secret key stored securely on both " +"the user's device and the server, ensuring a synchronized and secure " +"authentication process. The method of generating the codes is sometimes also " +"called TOTP (time-based one-time password)." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:145 -msgid "Please note that the following attributes are **not customizable**:" +#: ../settings/security/two-factor/authenticator-app.rst:28 +msgid "Enabling the Authenticator App Method" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:147 -msgid "title" -msgstr "naslov" +#: ../settings/security/two-factor/authenticator-app.rst:30 +#: ../settings/security/two-factor/security-keys.rst:28 +msgid "To enable the method, just toggle the switch on in the settings." +msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:148 -msgid "id" +#: ../settings/security/two-factor/authenticator-app.rst:None +msgid "Authenticator App Switch in Settings" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:149 -msgid "ticket number" +#: ../settings/security/two-factor/authenticator-app.rst:36 +msgid "" +"Now the users will be able to set up this two-factor authentication method " +"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " +"Once they do, on next sign-in with password, they will be asked to provide " +"an additional security code generated by their mobile device." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:151 -msgid "created_by_id" +#: ../settings/security/two-factor/security-keys.rst:2 +msgid "Security Keys" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:152 -msgid "updated_by_id" +#: ../settings/security/two-factor/security-keys.rst:4 +msgid "" +"The security keys method is a type of a two-factor authentication that uses " +"Web Authentication API in the browser for verifying user's identity. The " +"user can register multiple hardware or software security keys with their " +"Zammad account and then they can use it during the sign-in process." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:155 -msgid "Which Values Can Be Set?" +#: ../settings/security/two-factor/security-keys.rst:12 +msgid "" +"When logging in, the user is prompted to provide the same security key they " +"registered with their account, in addition to their password. This key acts " +"as the second factor of authentication, providing an extra layer of security." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:157 -msgid "😵 **Invalid values → unpredictable behavior**" +#: ../settings/security/two-factor/security-keys.rst:None +msgid "Security Key dialog in Safari on macOS" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:159 +#: ../settings/security/two-factor/security-keys.rst:21 msgid "" -"If you provide a value that Zammad doesn't understand (*e.g.,* ``-F " -"\"priority=high\"``), it's not always clear what will happen. In some cases, " -"a ticket will be created with the default values instead - but in others, it " -"may not be created at all!" +"The type of the key can range from hardware USB sticks to passkeys stored in " +"a device of user's choice. Which type can be used depends on the browser " +"flavor and the platform of the user." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:164 -msgid "So what values does Zammad understand, then? Well, it depends..." +#: ../settings/security/two-factor/security-keys.rst:26 +msgid "Enabling the Security Keys Method" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:168 -msgid "Use an email address or username:" +#: ../settings/security/two-factor/security-keys.rst:None +msgid "Security Keys Switch in Settings" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:190 -msgid "group & priority" +#: ../settings/security/two-factor/security-keys.rst:34 +msgid "" +"Now the users will be able to set up this two-factor authentication method " +"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " +"Once they do, on next sign-in with password, they will be asked to provide " +"the same security key they registered during the setup." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:175 -msgid "Refer to the dropdown menus in the ticket pane:" -msgstr "" - -#: ../system/integrations/checkmk/api-reference.rst:0 -msgid "See possible values for certain attributes in the ticket pane." +#: ../settings/system/system-selfhosted.include.rst:3 +msgid "" +"Below settings are only available to self hosted users. In hosted " +"environments we're handling these settings for you to ensure service " +"stability." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:187 -msgid "🙅 **Ticket state CANNOT be set this way!**" +#: ../settings/system/base.rst:11 +msgid "Fully Qualified Domain Name" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:189 -msgid "" -"Why? Because ``-F \"state=...\"`` is already used :ref:`as a Checkmk " -"parameter `." +#: ../settings/system/base.rst:7 +msgid "The URL of your Zammad installation." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:222 -msgid "Everything Else" +#: ../settings/system/base.rst:9 ../settings/system/base.rst:17 +msgid "This setting is used within :doc:`/misc/variables` and notifications." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:193 -msgid "" -"To set any other attributes, it helps to know your way around the :docs:" -"`rails console `. Valid values are those that you can " -"set with a string:" +#: ../settings/system/system-base.include.rst:1 +msgid "It is automatically set by the *Getting Started wizard*." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:218 -msgid "These values can then be passed directly to the API:" +#: ../settings/system/system-base.include.rst:5 +msgid "Changing this setting also changes callback URLs for your channels etc." msgstr "" -#: ../system/integrations/checkmk/index.rst:16 -msgid "How does it work?" +#: ../settings/system/system-base.include.rst:6 +msgid "This setting can have negative affects on being able to login." msgstr "" -#: ../system/integrations/checkmk/index.rst:2 -msgid "Checkmk" +#: ../settings/system/base.rst:19 +msgid "HTTP type" msgstr "" -#: ../system/integrations/checkmk/index.rst:4 +#: ../settings/system/base.rst:14 msgid "" -"`Checkmk `_ is a powerful IT monitoring tool that can " -"send real-time status alerts to Zammad via email or REST API. Set these " -"alerts up in Checkmk, and Zammad will automatically create, update, and " -"close tickets based on the health of your system:" +"The HTTP type tells your installation how your clients connect. This is " +"relevant for authentication and cookie security." msgstr "" -#: ../system/integrations/checkmk/index.rst:14 -msgid "Screenshot of ticket created by Checkmk notifications" +#: ../settings/system/base.rst:31 +msgid "SystemID" msgstr "" -#: ../system/integrations/checkmk/index.rst:14 -msgid "Multiple alerts, same ticket." +#: ../settings/system/base.rst:22 +msgid "" +"This ID is being used within your ticket number. In case you're " +"communicating with another ticket system with similar ticket number schemes " +"this ID greatly reduces the risk of false follow ups." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:2 -msgid "Setup Guide" +#: ../settings/system/base.rst:26 +msgid "" +"The SystemID is randomly selected upon installation of Zammad (``1-99``)." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:4 +#: ../settings/system/base.rst:30 msgid "" -"Whenever the Checkmk integration is enabled, Zammad listens for messages on " -"its API and over email. As long as those messages follow the required " -"format, Zammad will create new tickets (or find and update existing ones) " -"based on the message contents." +"**Do not** change this setting in a productive system! Your Zammad " +"installation may no longer recognize old ticket number based follow ups upon " +"change!" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:10 -msgid "" -"That means that “setting up Checkmk integration” is simply a matter of " -"**adding configuration to your Checkmk site**: telling it when to send these " -"messages and what to say. To do that, you'll need to create a new " -"**notification rule** (see `Checkmk's official docs `_ for help with that)." +#: ../settings/system/frontend.rst:2 +msgid "Frontend" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:17 +#: ../settings/system/frontend.rst:22 +msgid "Core Workflow Ajax Mode" +msgstr "" + +#: ../settings/system/frontend.rst:6 msgid "" -"As part of this new rule, you'll have to choose a **notification method** " -"(*i.e.,* a script to execute whenever the rule is triggered). This script " -"will be written by you (samples below), and contain the logic for sending " -"API/email messages to Zammad:" +"This setting allows administrators to enforce :doc:`/system/core-workflows` " +"to use Ajax-Calls instead of web sockets. You'll usually only need this if " +"you experience serious issues as noted below." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:26 -msgid "Checkmk \"New Rule\" dialog" +#: ../settings/system/frontend.rst:10 +msgid "**🤓 Possible (technical) reasons**" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:26 +#: ../settings/system/frontend.rst:12 msgid "" -"Find your custom scripts in the Checkmk WATO under **Notifications > New " -"Rule > Notification Method**." +"In some cases, your network structure (e.g. firewalls, proxies) may " +"disconnect long web socket connections. This leads to select fields staying " +"empty (e.g. owner selection *after* selecting your group) or fields not " +"shown / hidden (e.g. when switching to or from pending states, the \"pending " +"till\" field not showing / hiding)." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:29 +#: ../settings/system/frontend.rst:18 msgid "" -"Once you're done setting up your new rule, you're all set! New tickets " -"should start coming in and auto-updating any time your rule is triggered." +"Please keep in mind that the Ajax fallback may cause serious pressure on " +"your application server. If you have the choice stick to web sockets." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:33 -msgid "" -"(If you need help troubleshooting, be sure to check the :ref:`checkmk-recent-" -"logs`.)" +#: ../settings/system/frontend.rst:22 +msgid "Default: ``no`` (inactive)" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:38 -msgid "API Alerts" +#: ../settings/system/frontend.rst:53 +msgid "Show calendar weeks in the picker of date/datetime fields" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:40 +#: ../settings/system/frontend.rst:25 msgid "" -"To add these scripts in the Checkmk WATO, copy them into your Checkmk " -"installation directory and make them executable. (Be sure to replace the " -"``zammad.example.com`` callback URL with the one found in your admin panel.)" +"With this setting you can instruct Zammad to provide week number display " +"globally for all users. Calendar with week number display are usually used " +"in business sectors and may not be relevant for everyone." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:60 -msgid "Service notification" +#: ../settings/system/frontend.rst:29 +msgid "" +"This setting affects *all areas* - you'll also see week numbers in the admin " +"panel for e.g. triggers and macros." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:46 -msgid "" -"For updates on the status of the software running on your server (*e.g.,* " -"postgres)." +#: ../settings/system/frontend.rst:32 +msgid "Default: ``no`` (not shown)" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:75 -msgid "Host notification" +#: ../settings/system/frontend.rst:53 +msgid "Here's the difference:" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:63 -msgid "For updates on the status of the server itself." +#: ../settings/system/frontend.rst:0 +msgid "Screenshot showing Zammad's date picker (in the default way)" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:77 -msgid "🤔 **What's with all the env vars?**" +#: ../settings/system/frontend.rst:41 +msgid "Set to ``no``" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:79 +#: ../settings/system/frontend.rst:0 msgid "" -"Whenever Checkmk runs these scripts, it needs to provide some information " -"about the event that triggered the notification. This information is passed " -"in the form of these ``$NOTIFY_*`` environment variables." +"Screenshot showing Zammad's date picker with\n" +"week numbers enabled" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:85 +#: ../settings/system/frontend.rst:50 +msgid "Set to ``yes``" +msgstr "" + +#: ../settings/system/index.rst:4 msgid "" -"You can specify additional parameters to pass to the script when you're " -"setting up your notification rule, but the ones you see here are all " -"provided by default." +"For your overview we split each tab within system settings into its own page:" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:90 -msgid "Email Alerts" +#: ../settings/system/index.rst:16 +msgid "Console Based Settings" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:94 +#: ../settings/system/index.rst:18 msgid "" -"🐞 **There are known bugs** in Zammad's processing of email from Checkmk. " -"This section will be completed once they have been resolved. (Learn more at " -"GitHub issues `#2377 `_ & " -"`#2180 `_.)" +"There's some console based settings we didn't put into the UI. However, you " +"may find them helpful - you can find them in our :docs:`hidden settings ` section." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:100 -msgid "In the meantime, we encourage you to set up API alerts instead." +#: ../settings/system/network.rst:2 +msgid "Network" msgstr "" -#: ../system/integrations/clearbit.rst:2 -msgid "Clearbit" +#: ../settings/system/network.rst:8 +msgid "" +"The proxy settings can only be saved after successfully testing the proxy " +"connection." msgstr "" -#: ../system/integrations/clearbit.rst:4 +#: ../settings/system/network.rst:15 +msgid "Proxy Address." +msgstr "" + +#: ../settings/system/network.rst:12 msgid "" -"With our Clearbit integration, you can easily enrich the information " -"provided by Zammad. If the customers or agents email address is known to " -"Clearbit, it will share all information it has regarding the user with " -"Zammad. Those information can include the following:" +"Allows you to provide a proxy server if needed. This is relevant for network " +"communication by Zammad." msgstr "" -#: ../system/integrations/clearbit.rst:9 -msgid "Avatar" +#: ../settings/system/network.rst:15 +msgid "It **does not** affect the update process or Elasticsearch." msgstr "" -#: ../system/integrations/clearbit.rst:10 -msgid "Address information" +#: ../settings/system/network.rst:18 +msgid "Username for proxy connection." msgstr "" -#: ../system/integrations/clearbit.rst:11 -msgid "Website information" +#: ../settings/system/network.rst:18 +msgid "" +"If your proxy server requires authentication, provide the username here." msgstr "" -#: ../system/integrations/clearbit.rst:12 -msgid "A BIO (as Note by default)" +#: ../settings/system/network.rst:21 +msgid "Password for proxy connection." msgstr "" -#: ../system/integrations/clearbit.rst:14 +#: ../settings/system/network.rst:21 msgid "" -"If needed, you can add further custom objects and add mappings to them, so " -"the Clearbit information can be filled within the database. In general you " -"can get any information from Clearbit, as long as you have a mapping to an " -"Zammad object." +"If your proxy server requires authentication, provide the password here." msgstr "" -#: ../system/integrations/clearbit.rst:21 -msgid "" -"Clearbit does have a mapping of fields like LDAP and Exchange have, but does " -"not \"win\" against Zammad information. This means that if you have e.g. the " -"last name field filled in already and Clearbit has other information on " -"that, it will not be updated." +#: ../settings/system/network.rst:26 +msgid "No proxy for the following hosts." msgstr "" -#: ../system/integrations/clearbit.rst:26 +#: ../settings/system/network.rst:24 msgid "" -"However: If let's say the last name has been set by Clearbit and Zammad " -"notices that the last name on the Clearbit source has changed, Zammad will " -"also update this value." +"Exception list for hosts you can't or don't want to reach via proxy server." msgstr "" -#: ../system/integrations/clearbit.rst:33 -msgid "" -"The configuration of Clearbit is really easy and done fast! Just login to " -"your Clearbit-Account, go to \"API\" and copy the secret-API-Key." +#: ../settings/system/network.rst:27 +msgid "Default: ``localhost,127.0.0.0,::1``" msgstr "" -#: ../system/integrations/clearbit.rst:38 -msgid "" -"Now change to your Zammad instance, go to Integrations (System) -> Clearbit " -"in the admin panel. Paste your API-Key into the API-Key-Field and decide if " -"Zammad should create unknown Organizations automatically, if the user does " -"not have one yet (and Clearbit knows it). The shared option decides if the " -"new organizations Zammad creates with Clearbit should be shared ones." +#: ../settings/system/services.rst:2 +msgid "Services" msgstr "" -#: ../system/integrations/clearbit.rst:47 -msgid "" -"If you're unsure what option to choose, better stick with \"no\". You can " -"also learn more about :doc:`/manage/organizations/index`." +#: ../settings/system/services.rst:10 +msgid "Image Service" msgstr "" -#: ../system/integrations/clearbit.rst:52 -msgid "" -"The Mapping option works similar to the mapping within the Exchange and LDAP " -"sync. You can add further mappings for e.g. custom fields if you need more " -"information that Clearbit can provide." +#: ../settings/system/services.rst:5 +msgid "Defines the backend for user and organization image lookups." msgstr "" -#: ../system/integrations/clearbit.rst:58 -msgid "" -"If you want to add more Clearbit fields and want to learn more about " -"available fields on their API, you can take a look at their `API " -"documentation `_." +#: ../settings/system/services.rst:7 +msgid "Default: ``Zammad Image Service`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:62 +#: ../settings/system/services.rst:9 msgid "" -"If you're happy with the above chosen Settings and your mapping, just save " -"the changes and enable Clearbit integration. Zammad will now start polling " -"the Clearbit API as users contact you." +"Make sure your on premise installation has ``HTTPS`` access to ``images." +"zammad.com``." msgstr "" -#: ../system/integrations/clearbit.rst:68 -msgid "" -"Zammad does not synchronize with Clearbit on a regular basis, but on demand " -"if needed. This saves API calls." +#: ../settings/system/services.rst:18 +msgid "Geo Calendar Service" msgstr "" -#: ../system/integrations/clearbit.rst:73 +#: ../settings/system/services.rst:13 msgid "" -"Below the Settings and Mappings, you'll find our Integration log. You can " -"see what requests Zammad sent to Clearbit and also the APIs Response." +"Defines the backend for geo calendar lookups. Used for initial calendar " +"setup." msgstr "" -#: ../system/integrations/clearbit.rst:78 +#: ../settings/system/services.rst:16 +msgid "Default: ``Zammad GeoCalendar Service`` (active)" +msgstr "" + +#: ../settings/system/services.include.rst:2 msgid "" -"By the way, you can also view the API log on the Clearbit website - the " -"information seen is basically the same." +"Make sure your on premise installation has ``HTTPS`` access to ``geo.zammad." +"com``." msgstr "" -#: ../system/integrations/clearbit.rst:84 -msgid "Example When Adding a User" +#: ../settings/system/services.rst:26 +msgid "Geo IP Service" msgstr "" -#: ../system/integrations/clearbit.rst:86 +#: ../settings/system/services.rst:21 msgid "" -"To show you how fast information is added, we added a small Screencast " -"below. This shows the creation of the User Alex from Clearbit. As we already " -"set the last name of Alex to \"X\", Zammad did not update it. What Zammad " -"did was to add further information it received from Clearbit." +"Defines the backend for geo IP lookups. Shows also location of an IP address " +"if an IP address is shown." msgstr "" -#: ../system/integrations/cti/generic.rst:2 -msgid "CTI (generic)" +#: ../settings/system/services.rst:24 +msgid "Default: ``Zammad GeoIP Service`` (active)" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:1 -msgid "" -"This integration enables Zammad to provide a caller log to your agents. With " -"this your agents can greet your customers by their name and are supported by " -"Zammad with automatically opening a new ticket dialog or the user profile." +#: ../settings/system/services.rst:32 +msgid "Geo Location Service" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:6 +#: ../settings/system/services.rst:29 msgid "" -"Click the toggle next to the heading to activate or deactivate this " -"integration." +"Defines the backend for geo location lookups to store geo locations for " +"addresses." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:9 +#: ../settings/system/services.rst:32 msgid "" -"If you want to learn more on how your agents can use this function, please " -"refer the :user-docs:`user documentation `." +"Default: ``OpenStreetMap (ODbL 1.0, http://osm.org/copyright)`` (active)" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:14 +#: ../settings/system/services.rst:36 msgid "" -"Automatically opening new ticket dialogues or user profiles requires agent " -"to extension mapping - see more below." -msgstr "" - -#: ../system/integrations/cti/includes/introduction.include.rst:20 -msgid "Please note the following limitations to reduce confusion later on:" +"You can find a detailed privacy information on what we store for how long on " +"our :docs:`Privacy Appendix ` inside of our System " +"Documentation." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:22 -msgid "CTI integrations provide caller log functions only." +#: ../settings/system/storage.rst:2 +msgid "Storage" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:23 +#: ../settings/system/storage.rst:6 msgid "" -"This integration does not provide any VoIP functionalities; you can't make " -"phone calls from within Zammad." +"Here you can define where Zammad stores attachments for tickets and the " +"knowledge base. By default, we're writing to the ``Database`` - you can " +"switch to ``Filesystem`` or ``Simple Storage (S3)`` at any time. In this " +"case please have a look on the following instructions." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:25 +#: ../settings/system/storage.rst:11 msgid "" -"If your browser supports ``tel``-URLs, you can click on phone numbers for " -"automatic dialing. This requires additional software / configuration on your " -"agent's computers." +"If you have a busy Zammad instance, we strongly encourage you to use " +"filesystem storage instead of \"Database\". This will greatly improve system " +"performance (de-crease database load and size)." msgstr "" -#: ../system/integrations/cti/generic.rst:9 -#: ../system/integrations/cti/placetel.rst:14 -#: ../system/integrations/cti/sipgate.rst:14 -msgid "Please provide the following requirements:" +#: ../settings/system/storage.rst:19 +msgid "Database" msgstr "" -#: ../system/integrations/cti/generic.rst:11 +#: ../settings/system/storage.rst:17 msgid "" -"A telephone system that supports webhooks (outbound) (best option are those " -"that allow customizing the calls)." -msgstr "" - -#: ../system/integrations/cti/generic.rst:13 -msgid "A unique Call-ID during the call session." +"This is the default storage method. The attachments are stored directly in " +"the database. If your Zammad instance grows, we recommend one of the other " +"methods to maintain performance." msgstr "" -#: ../system/integrations/cti/generic.rst:14 -msgid "Call event data (both numbers and direction)." +#: ../settings/system/storage.rst:38 +msgid "Filesystem" msgstr "" -#: ../system/integrations/cti/generic.rst:15 -msgid "Your Zammad instance must be reachable for your telephony system." +#: ../settings/system/storage.rst:22 +msgid "" +"This storage method is recommended for all Zammad instances, especially for " +"those with a higher load. If you choose filesystem, your files are written " +"to ``/opt/zammad/storage/``." msgstr "" -#: ../system/integrations/cti/generic.rst:17 +#: ../settings/system/storage.rst:26 msgid "" -"If you want to learn more on what kind of requests are supported by Zammad " -"and what it expects, please consult our :docs:`CTI-API documentation `." +"Moving attachments from \"Database\" to \"Filesystem\" can be run during " +"production use. However, you should consider your framework conditions (e.g. " +"bandwidth, system load in production) to define the right moment." msgstr "" -#: ../system/integrations/cti/generic.rst:22 -#: ../system/integrations/cti/placetel.rst:27 -#: ../system/integrations/cti/sipgate.rst:30 -msgid "Available Settings" +#: ../settings/system/storage.rst:32 +msgid "**You noticed slow updates of Zammad?**" msgstr "" -#: ../system/integrations/cti/generic.rst:29 -#: ../system/integrations/cti/placetel.rst:41 -#: ../system/integrations/cti/sipgate.rst:40 -msgid "Endpoint Settings" +#: ../settings/system/storage.rst:34 +msgid "" +"While Zammad is beeing updated, it enforces a recursive \"change " +"owner\" (chown) for this directory. For instances with many files this can " +"be time consuming. To mitigate that you can move your files and create a " +"symlink in ``/opt/zammad/storage/`` to the new directory. Of course you have " +"to make sure on your own that the permissions are always correct." msgstr "" -#: ../system/integrations/cti/generic.rst:25 -msgid "" -"Zammad will list your generic CTI endpoint here. It contains a unique token " -"so ensure to keep this URL save." +#: ../settings/system/storage.rst:95 +msgid "Simple Storage (S3)" msgstr "" -#: ../system/integrations/cti/generic.rst:28 +#: ../settings/system/storage.rst:41 msgid "" -"You'll need this endpoint for your PBX to talk to Zammad, see :docs:`CTI-API " -"documentation `." +"To use the Simple Storage (S3), you have to provide some settings, which " +"can't be accessed in the UI (see instructions below)." msgstr "" -#: ../system/integrations/cti/includes/important-dont-forget-saving.include.rst:3 +#: ../settings/system/storage.rst:44 msgid "" -"All following options **do not save automatically**. Always use the Save " -"button on the lower end of the integration page!" +"⚠️ Please note that the current implementation is in its early stages and can " +"be modified in the future." msgstr "" -#: ../system/integrations/cti/generic.rst:43 -#: ../system/integrations/cti/placetel.rst:49 -#: ../system/integrations/cti/sipgate.rst:52 -msgid "Call Settings" +#: ../settings/system/storage.rst:47 +msgid "" +"The prerequisite is to have access to a S3-compatible storage and to have " +"all necessary parameters available (which depends on your storage provider; " +"if in doubt, please ask there for help)." msgstr "" -#: ../system/integrations/cti/generic.rst:39 -#: ../system/integrations/cti/placetel.rst:49 -#: ../system/integrations/cti/sipgate.rst:37 -#: ../system/integrations/cti/sipgate.rst:50 -msgid "Inbound" +#: ../settings/system/storage.rst:51 +msgid "Steps to configure S3:" msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:1 +#: ../settings/system/storage.rst:53 msgid "" -"This option allows you to block specific incoming caller IDs. It allows you " -"to temporarily reject e.g. spam callers without having to contact providers " -"or PBX administrators." +"Copy ``config/zammad/storage.yml.dist`` to ``config/zammad/storage.yml``" msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:11 -msgid "Caller ID to block" +#: ../settings/system/storage.rst:54 +msgid "Edit the copied file in one of the following ways:" msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 -msgid "Provide caller IDs to block in ``E.164`` format." +#: ../settings/system/storage.rst:56 +msgid "" +"Either provide your S3 configuration with one attribute per line like in the " +"upper area of the file" msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:8 +#: ../settings/system/storage.rst:58 msgid "" -"Your telephony system has to support this function. Zammad will send a " -"``reject`` response which will cause your telephony system to hang up the " -"call. To callers this usually will feel like the line is busy." +"Or provide your S3 configuration as an URL (which you can find at the end of " +"the file). Note: you can also provide this URL as environment variable (:" +"docs:`see system documentation `) without using this yml-file." msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:14 +#: ../settings/system/storage.rst:62 msgid "" -"Provide a meaningful note for your fellow administrators to remind yourself " -"why you've chosen to block the number." +"We recommend the deletion of the not used configuration style to avoid " +"inconsistencies." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 -#: ../system/integrations/cti/includes/outbound-calls.include.rst:17 -#: ../system/integrations/cti/sipgate.rst:40 -msgid "Outbound" +#: ../settings/system/storage.rst:65 +msgid "Restart Zammad so the config file / environment variable is loaded" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:1 +#: ../settings/system/storage.rst:66 msgid "" -"In many cases you may want to use a different caller ID depending on the " -"destination you're calling. This may apply due to specific connection rates " -"to other countries or because you want your customer to feel you're calling " -"from the same country." +"Set the \"Storage Method\" in Zammad to ``Simple Storage (S3)`` in Settings " +"> System > Storage and click on \"Submit\". After that, Zammad checks your " +"configuration and the connection to the service and will raise an error " +"message if something is wrong." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:6 -msgid "This option expects ``E.164`` number formats." -msgstr "" - -#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 -msgid "Destination caller ID" -msgstr "" - -#: ../system/integrations/cti/includes/outbound-calls.include.rst:5 -msgid "The caller ID or number you're trying to call." +#: ../settings/system/storage.rst:72 +msgid "A very simple storage configuration could look like this:" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:7 -msgid "You can use wildcards for e.g. country specific outbound numbers like:" +#: ../settings/system/storage.rst:85 +msgid "" +"Before setting the storage method to ``Simple Storage (S3)`` (step 4), " +"please make sure to have a working setup." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:9 -msgid "``49*`` for Germany" +#: ../settings/system/storage.rst:88 +msgid "" +"You can verify this by running ``rails r 'Rails.logger = Logger.new(STDOUT); " +"pp Store::Provider::S3.ping?'`` in your Zammad directory. If everything is " +"fine, you should see ``true``, else you should see ``false`` and a simple " +"error message." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:10 -msgid "``4930*`` for Berlin / Germany landlines" +#: ../settings/system/storage.rst:93 +msgid "" +"If you installed Zammad through a package manager (rather than from source), " +"replace ``rails r`` with ``zammad run rails r`` above. To learn more, see :" +"docs:`Administration via Console `." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 -msgid "``33*`` for France" +#: ../settings/ticket.rst:4 +msgid "" +"Here you can adjust general ticket settings. Additional ones for the ticket " +"composer interface can be found in the :doc:`/misc/composer`." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:15 -msgid "Set Outbound caller ID" +#: ../settings/ticket.rst:11 +msgid "Ticket Hook (default: ``Ticket#``)" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:14 -msgid "" -"The outbound caller ID to set (the number your customer sees on his display) " -"in ``E.164`` number format." +#: ../settings/ticket.rst:11 +msgid "The identifier for a ticket; *e.g.,* Ticket#, Call#, MyTicket#." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 -msgid "Provide a short description for fellow administrators." +#: ../settings/ticket.rst:38 +msgid "Ticket Hook Position (default: ``right``)" msgstr "" -#: ../system/integrations/cti/includes/generic-cti-support-note.includes.rst:3 +#: ../settings/ticket.rst:14 msgid "" -"This option requires your PBX to send a specific request to Zammad *before " -"dialing*. Please consult the :docs:`CTI API ` in case " -"you're not sure." +"With this setting you can decide (if) where to insert the ticket number." msgstr "" -#: ../system/integrations/cti/generic.rst:52 -#: ../system/integrations/cti/placetel.rst:54 -#: ../system/integrations/cti/sipgate.rst:59 -msgid "Other Settings" +#: ../settings/ticket.rst:20 +msgid "*Right*" msgstr "" -#: ../system/integrations/cti/includes/other-settings-intro.include.rst:1 +#: ../settings/ticket.rst:17 msgid "" -"Below you can find all available additional settings for this CTI " -"integration. For your overview we're sorting them by appearance and " -"reference their description first." +"This setting will add the ticket reference on the right site of the subject." msgstr "" -#: ../system/integrations/cti/includes/default-caller-id.include.rst:2 -#: ../system/integrations/cti/includes/default-caller-id.include.rst:1 -msgid "Default caller ID for outbound calls" +#: ../settings/ticket.rst:20 +msgid "Example: ``Some Subject [Ticket#12345]``" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:16 -#: ../system/integrations/cti/includes/records-caller-log.include.rst:15 -msgid "Shown records in caller log" +#: ../settings/ticket.rst:26 +msgid "*Left*" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:2 +#: ../settings/ticket.rst:23 msgid "" -"Allows you to set the number of shown caller log entries for all users. You " -"can choose from the following values:" +"This setting will add the ticket reference on the left site of the subject." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:5 -msgid "60 (default)" +#: ../settings/ticket.rst:26 +msgid "Example: ``[Ticket#12345] Some Subject``" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:6 -msgid "120" +#: ../settings/ticket.rst:29 +msgid "*None*" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:7 -msgid "180" +#: ../settings/ticket.rst:29 +msgid "This will completely remove ticket references from the subject." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:8 -msgid "240" +#: ../settings/ticket.rst:33 +msgid "" +"Please ensure to take a look at :doc:`/channels/email/settings` within the " +"email channel to ensure you have at least one reference that helps Zammad to " +"assign follow-ups correctly." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:9 -msgid "300" +#: ../settings/ticket.rst:37 +msgid "" +"Disabling this and not setting up any further follow up search will lead to " +"unexpected results!" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:11 -msgid "**🥵 Potential performance issue**" +#: ../settings/ticket.rst:65 +msgid "" +"Ticket Last Contact Behaviour (default: ``Use the start time of the last " +"customer thread (which may consist of multiple articles).``)" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:13 +#: ../settings/ticket.rst:41 msgid "" -"Setting this setting higher than 60 may cause serious performance issues on " -"very busy instances. Keep in mind that this setting causes Zammad to poll " -"and send up to 300 records to *all active agent sessions* in very short time " -"periods." +"This setting changes the way Zammad updates the ``Last Contact`` value of a " +"ticket. This is fairly important for overviews and what you expect upon " +"ticket updates of a customer." msgstr "" -#: ../system/integrations/cti/generic.rst:73 -msgid "Caller Log Filter" +#: ../settings/ticket.rst:52 +msgid "" +"Use the start time of the last customer thread (which may consist of " +"multiple articles)." msgstr "" -#: ../system/integrations/cti/generic.rst:55 +#: ../settings/ticket.rst:46 msgid "" -"This function allows you to provide call information based on e.g. queues " -"only to agents that really need the information." +"If this option is chosen, Zammad will update the last updated value just " +"once if a customer replies. After that, Zammad will wait for an agent to " +"react." msgstr "" -#: ../system/integrations/cti/generic.rst:58 +#: ../settings/ticket.rst:50 msgid "" -"Why? If you have a team for several countries or departments, you don't want " -"to bug your agents from other departments. Leaving these options empty will " -"fallback to showing everything to everyone." +"This comes in handy if you want to work tickets in the order of their first " +"update. This will not change ticket orders if customers decide to \"bump\" " +"the ticket affected." msgstr "" -#: ../system/integrations/cti/generic.rst:64 -msgid "Destination caller ID or Queue" +#: ../settings/ticket.rst:57 +msgid "Use the time of the very last customer article." msgstr "" -#: ../system/integrations/cti/generic.rst:63 +#: ../settings/ticket.rst:55 msgid "" -"This depends on your PBX and usually is either a queue ID, phone number or " -"extension." +"When setting this option, Zammad will always update the last updated value. " +"This means that if ordering by ``Last Update``, ticket orders will change if " +"customers \"bump\" the ticket." msgstr "" -#: ../system/integrations/cti/generic.rst:69 -msgid "Agents" +#: ../settings/ticket.rst:64 +msgid "Last contact value used on :doc:`/manage/overviews`" msgstr "" -#: ../system/integrations/cti/generic.rst:67 -msgid "" -"Select the agents that are responsible for the group. These agents will then " -"see caller log entries and call notifications fitting to said queue." +#: ../settings/ticket.rst:65 +msgid "Last contact value used on :doc:`/manage/trigger`" msgstr "" -#: ../system/integrations/cti/generic.rst:0 +#: ../settings/ticket.rst:88 msgid "" -"Screenshot showing the caller log filter table with pre filled sample data" +"Ticket Organization Reassignment (default: ``Update the most recent tickets." +"``)" msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:6 +#: ../settings/ticket.rst:68 msgid "" -"With recent logs Zammad allows you to view the latest calls for the CTI " -"functionality. This usually comes in handy, when you're looking for errors." +"This setting changes the way Zammad updates the organization field of the " +"tickets whenever the primary organization of a user is changed." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:0 -msgid "" -"Screenshot showing several incoming requests within Recent logs section." +#: ../settings/ticket.rst:74 +msgid "Update the most recent tickets." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:16 -msgid "I'm just here to clear floats up." +#: ../settings/ticket.rst:72 +msgid "" +"If this option is chosen, Zammad will update the 100 most recent tickets " +"where the user is the ticket customer. The ticket organization field will be " +"automatically set to the new primary organization of the user." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:20 -msgid "" -"By clicking on the entry of interest, Zammad will provide more details on " -"the call in question. You'll see the payload it received and also the " -"response that was sent." +#: ../settings/ticket.rst:88 +msgid "Do not update any tickets." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:0 +#: ../settings/ticket.rst:77 msgid "" -"Screenshot showing detailed information of a specific log entry of recent " -"logs" +"When choosing this option, Zammad will not update any tickets when the " +"user's primary organization is changed." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:31 -msgid "x" +#: ../settings/ticket.rst:80 +msgid "**Use with care!**" msgstr "" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 -#: ../system/integrations/cti/includes/troubleshooting.include.rst:9 -msgid "My Phone page stays blank, signalling does work..." +#: ../settings/ticket.rst:82 +msgid "" +"Using this option may lead to inconsistencies in the system as the ticket " +"organization may become decoupled from the ticket customer." msgstr "" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:5 +#: ../settings/ticket.rst:85 msgid "" -"If you've made sure that signalling works (check Recent logs) and your " -"Caller Log still stays empty, please ensure that you only configured one CTI " -"integration version. Specifically defining more than one agent mapping on " -"the different integration variants will be the issue." +"However, you may use this option if you wish to maintain :ref:`the shared " +"access ` to the ticket for all organization " +"members of the original organization of the customer." msgstr "" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 -msgid "Clear the not needed agent mapping and reload your browser page." +#: ../settings/ticket.rst:110 +msgid "Ticket Number Format (default: ``Increment (SystemID.Counter)``)" msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:1 +#: ../settings/ticket.rst:94 msgid "" -"By mapping your agents extension to their existing Zammad users, Zammad can " -"provide a new ticket dialog or open the user profile for the agent that " -"picks up the call." +"This setting defines the way Zammad's ticket number will look. Changing this " +"setting in production will cause follow up detection to fail." msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:5 -msgid "" -"This speeds up ticket aiding, no matter if it's for existing tickets or new " -"ones!" +#: ../settings/ticket.rst:102 +msgid "Increment (SystemID.Counter)" msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:8 +#: ../settings/ticket.rst:98 msgid "" -"To see it work from the agent's perspective, have a look on :user-docs:`user " -"documentation `." +"The increment value contains the SystemID (automatically generated during " +"installation) and a increment which counts up with every new Ticket. The " +"increment will automatically get another digit if needed." msgstr "" -#: ../system/integrations/cti/placetel.rst:2 -msgid "Placetel CTI" +#: ../settings/ticket.rst:102 +msgid "Examples: ``1010138``, ``1010139``" msgstr "" -#: ../system/integrations/cti/placetel.rst:16 -msgid "You need an administrative Placetel account for your organization." +#: ../settings/ticket.rst:110 +msgid "Date (Year.Month.Day.SystemID.Counter)" msgstr "" -#: ../system/integrations/cti/placetel.rst:17 -#: ../system/integrations/cti/sipgate.rst:20 +#: ../settings/ticket.rst:105 msgid "" -"Your Zammad instance must be allowed to communicate to external services." +"This version of the ticket number is fairly long. However, because it " +"contains the date of ticket creation, it also allows you to see when the " +"ticket has been created. You may feel familiar with this number format if " +"you've worked with OTRS already." msgstr "" -#: ../system/integrations/cti/placetel.rst:18 -msgid "Placetel must be able to reach your Zammad instance." +#: ../settings/ticket.rst:110 +msgid "Examples: ``201206231010138``, ``201206231010139``" msgstr "" -#: ../system/integrations/cti/placetel.rst:22 -msgid ":doc:`provider-configurations/placetel`" +#: ../settings/ticket.rst:137 +msgid "OPTIONS" msgstr "" -#: ../system/integrations/cti/placetel.rst:21 +#: ../settings/ticket.rst:113 msgid "" -"Learn how to configure Placetel to enable Zammad and Placetel to communicate " -"with each other." +"The below options allow you to further customize your ticket number. The " +"availability of options differ depending of the chosen ticket number format " +"above." msgstr "" -#: ../system/integrations/cti/placetel.rst:32 +#: ../settings/ticket.rst:122 +msgid "Checksum (default: ``no``)" +msgstr "" + +#: ../settings/ticket.rst:118 msgid "" -"The here listed endpoint settings are relevant for the :doc:`integration " -"configuration with Placetel `." +"If set to yes, we'll built a checksum to further \"unique\" the ticket " +"number of your system. If you're dealing with many other ticket systems this " +"might help to prevent false positive follow up detection on tickets." msgstr "" -#: ../system/integrations/cti/placetel.rst:37 -#: ../system/integrations/i-doit.rst:53 -msgid "Endpoint" +#: ../settings/ticket.rst:122 +msgid "This will also add another digit to the ticket number." msgstr "" -#: ../system/integrations/cti/placetel.rst:36 -msgid "" -"This endpoint will be required for the Zammad integration within the " -"Placetel web interface." +#: ../settings/ticket.rst:137 +msgid "Min. size of Number (default: ``5``)" msgstr "" -#: ../system/integrations/cti/placetel.rst:41 -msgid "API Token" +#: ../settings/ticket.rst:125 +msgid "" +"This setting defines the minimum length of your ticket number. If your " +"counter is not yet high enough, Zammad will fill the number with zeros to " +"ensure the wanted length." msgstr "" -#: ../system/integrations/cti/placetel.rst:40 +#: ../settings/ticket.rst:129 msgid "" -"You'll receive this token within the ``Web API`` menu. Make sure to copy " -"this value, it's only shown once!" +"Please note that the minimum length is ``3`` (SystemID + at least one digit " +"if below 10). Also, if the length is no longer long enough, the number will " +"automatically get one digit longer. Ticket-Numbers **do not overflow**, thus " +"it's save to keep it at 5 or set it lower if wanted." msgstr "" -#: ../system/integrations/cti/placetel.rst:71 -#: ../system/integrations/cti/sipgate.rst:77 -msgid "Phone Extension to Agent Mapping" +#: ../settings/ticket.rst:135 +msgid "" +"This option is only available if ticket number format is set to " +"``Increment``!" msgstr "" -#: ../system/integrations/cti/placetel.rst:0 -msgid "Screenshot showing sample user mappings in between Placetel and Zammad" +#: ../settings/ticket.rst:142 +msgid "Auto-Assignment" msgstr "" -#: ../system/integrations/cti/placetel.rst:64 +#: ../settings/ticket.rst:144 msgid "" -"You can find your agents Placetel username combination required within ⚙️ PBX " -"→ VoIP destinations. Within the \"Advanced settings\" section you're looking " -"for \"SIP user name\" and \"SIP server\"." +"In a larger Zammad environment, it happens that several agents open the same " +"ticket at the same time. Although collision detection is then effective, the " +"efficiency of processing can be increased by means of the automatic " +"assignment of tickets when a ticket is opened." msgstr "" -#: ../system/integrations/cti/placetel.rst:68 -msgid "Combine these two like so: ``@``." +#: ../settings/ticket.rst:149 +msgid "" +"The automatic assignment of tickets can be activated and configured in the " +"admin area under Settings > Ticket > Auto Assignment." msgstr "" -#: ../system/integrations/cti/placetel.rst:0 -msgid "Sample VoIP credentials for a Placetel user" +#: ../settings/ticket.rst:152 +msgid "" +"The auto assignment only works if the ticket has no owner yet. By default, " +"the agent can always reset the ticket owner to ``-`` if needed." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:2 -msgid "Setup Placetel connection for Zammad" +#: ../settings/ticket.rst:155 +msgid "" +"If you want to use this function for only specific tickets, you can " +"configure the conditions accordingly to meet your requirement. By default " +"the condition affects all tickets with the state ``open``." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:6 +#: ../settings/ticket.rst:161 msgid "" -"This configuration step requires a *full* administrative Placetel account. " -"You may receive forbidden error messages with Placetel in case your " -"permissions are not high enough." +"If you need to exclude users (e.g. a group leader), you can search and " +"select the desired agents in the ``Exception Users`` list. The search " +"function in this area is only effective, if you have too many agents to " +"display at once to help you with the configuration." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:10 -msgid "" -"The following actions can be configured via the `Placetel web interface " -"`_." +#: ../settings/ticket.rst:167 +msgid "Notifications" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:29 -msgid "Step 1: Activate Zammad integration" +#: ../settings/ticket.rst:191 +msgid "Default Notifications" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:14 +#: ../settings/ticket.rst:170 msgid "" -"Within Integrations, scroll down to Partner integrations and select Zammad." +"This setting allows you to configure the default ticket notifications that " +"will be applied to all new agent users (incl. users who were just assigned " +"agent role). Simply change the notification matrix to desired state and " +"press **Save**." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:17 +#: ../settings/ticket.rst:175 msgid "" -"You can alternatively filter by \"Ticket Systems\" to reduce the number of " -"entries on the page. You'll still want to look for Partner integrations. 🤓" +"In case an agent already exists, their ticket notification preferences will " +"be preserved. Optionally, you can also **Apply current defaults to all " +"agents**." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:21 +#: ../settings/ticket.rst:181 msgid "" -"Within the Zammad integration now press \"Activate\". A new tab ``API`` " -"becomes available - open this tab." +"**Potential time-consuming action:** Applying default ticket notifications " +"to all agent users may take some time to complete, be patient! The exact " +"time will depend on the size of your system and the number of agents." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:24 +#: ../settings/ticket.rst:185 msgid "" -"Now tick \"Enable Call Control / Notify API\" and paste the Placetel " -"endpoint from your Zammad instance into the field \"URL of your API " -"endpoint\". Save to apply the settings" +"**Active agents only!** When current default ticket notifications are " +"applied, only active agent users are considered. In case an agent is re-" +"activated *after* this action, they will still have the old notification " +"configuration." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 -msgid "Screencast showing how to activate the Zammad integration" +#: ../settings/ticket.rst:190 +msgid "" +"In case you want to go back to the initial state of ticket notifications, " +"you can click on **Reset to default** button." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:51 -msgid "Step 2: Generate API Token for Placetel" +#: ../settings/ticket.rst:196 +msgid "Duplicate Detection" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:32 -msgid "" -"Go back to the integrations page and scroll down to \"Web API\". Generate a " -"new API token by using the \"Create a new API token\" button." +#: ../settings/ticket.rst:238 +msgid "Detect Duplicate Ticket Creation" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:37 +#: ../settings/ticket.rst:199 msgid "" -"If you already generated a token either use your existing token or reset it " -"by using above mentioned button. Placetel will ask you to conform this reset." +"This setting turns on the duplicate ticket detection mechanism during ticket " +"creation. If similar tickets are found in the system, a suitable warning " +"will be shown to the user trying to create a ticket." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:41 -msgid "" -"Please keep in mind that existing API scripts may no longer work due to " -"token resets!" +#: ../settings/ticket.rst:206 +msgid "A Sample Duplicate Ticket Warning" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:44 +#: ../settings/ticket.rst:208 msgid "" -"Copy the provided API token and insert it into the \"API Token\" field " -"within Zammad's Placetel integration." +"You can choose which ticket attributes will be matched by selecting them in " +"**Attributes to compare** field. Only if the ticket attribute value provided " +"by the user in the ticket create form is *equal* with the attribute in an " +"existing ticket, the warning will be shown." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:47 -msgid "" -"Apply your changes by using the \"Save\" button on the bottom of the " -"Placetel integration page and activate the Placetel integration." +#: ../settings/ticket.rst:213 +msgid "**Warning title** and **Warning message** are configurable as well." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +#: ../settings/ticket.rst:215 msgid "" -"Screencast showing how to retrieve an API token from Placetel for Zammad" +"You can limit the detection only to certain user roles. By default, only " +"agents will see the warning." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:73 -#: ../system/integrations/cti/provider-configurations/sipgate.rst:77 -msgid "Step 3: Restrict the numbers to notify on" +#: ../settings/ticket.rst:218 +msgid "" +"If you don't want to show the matched tickets as part of the warning, you " +"can set **Show matching ticket(s) in the warning** setting to *no*." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:54 +#: ../settings/ticket.rst:221 msgid "" -"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " -"the the Integrations page of the Placetel web interface, go to \"Notify " -"API\"." +"By default, **Permission level for looking up ticket** is set to *User*, " +"which means user permissions will be honored during sarch. The user will " +"see the warning only if tickets they have access to are matched. " +"Alternatively, you can set this setting to *System*, in which case the " +"search will happen within *all* tickets in the system, regardless of user " +"permissions." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:58 -msgid "" -"Lower on the page Placetel allows you to restrict the numbers to notify on. " -"You'll find this within the \"External routing API\" part." +#: ../settings/ticket.rst:227 +msgid "**🦺 Safety first!**" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +#: ../settings/ticket.rst:229 msgid "" -"Screenshot showing a sample selection of phone numbers to use for the " -"Placetels notify API" +"Even if the permission level is set to *System*, the user will not be shown " +"the tickets they don't have access to in the warning, even if they match." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:66 +#: ../settings/ticket.rst:233 msgid "" -"This menu point also provides a API request log from Placetel view. Just " -"open \"Recent responses of your API endpoint\" to learn more." +"However, just the confirmation about the existence of the tickets in the " +"system may be considered an unwanted information disclosure. Use this option " +"carefully!" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:69 +#: ../settings/ticket.rst:237 msgid "" -"If you want to see Zammad's perspective, use the \"Recent Logs\" part from " -"within the Placetel integration page." +"Finally, you can configure between matching within **All tickets** or **Open " +"tickets** only by setting **Match tickets in following states**. Depending " +"on the current ticket state, a ticket may or not be matched." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 -msgid "Screenshot showing sample log entries for Placetels API calls to Zammad" +#: ../system/core-workflows.rst:2 +msgid "Core Workflows" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:77 -msgid "Step 4 (optional): Further configurations for Placetel" +#: ../system/core-workflows.rst:4 +msgid "" +"Core Workflows allow you to adjust object attributes in many ways. For " +"example:" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:76 -msgid "" -"If needed, you can now configure Zammad's Placetel integration in more " -"detail. You can learn more about your options here: :ref:`Placetel " -"integration settings `." +#: ../system/core-workflows.rst:7 +msgid "show / hide fields" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:2 -msgid "Setup Sipgate connection for Zammad" +#: ../system/core-workflows.rst:8 +msgid "adjust mandatory setting" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Sipgate has no english web interface which is why this documentation page is " -"mixing up languages badly." +#: ../system/core-workflows.rst:9 +msgid "manipulate available options" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +#: ../system/core-workflows.rst:11 msgid "" -"Please also note that the availability of API addons highly depends on your " -"package trier. Usage of sipgate.io packages *is not free*, please check " -"their `pricing page `_ before!" -msgstr "" - -#: ../system/integrations/cti/provider-configurations/sipgate.rst:35 -msgid "Step 1: Book sipgate.io package" +"With this, you can provide exactly the information your users really need!" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:13 -msgid "Skip to step 2 if you already have the package booked!" +#: ../system/core-workflows.rst:15 +msgid "" +"If the pre-defined :doc:`/system/objects` are not enough, please add them " +"beforehand." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:15 +#: ../system/core-workflows.rst:17 msgid "" -"Login to an administrative Sipgate account and navigate to " -"``Accountverwaltung``. You'll see several different options depending on " -"your booked packages. Select ``Verträge & Produkte`` to continue." +"If you experience slow or unreliable field updates, please see :ref:`Core " +"Workflow Ajax Modus `" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:19 +#: ../system/core-workflows.rst:22 msgid "" -"Scroll down to the section ``Zusätzliche Produkte buchen`` and look for " -"``sipgate.io`` - select this product by using the ``Produkte anzeigen``-" -"Button." +"This is a very enhanced functionality and can cause unexpected UI behavior. " +"Please ensure to test your use cases after configuration to reduce surprises." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:23 -msgid "" -"On the next page select either one of the ``sipgate.io`` packages or ``Push-" -"API Package Free``. Follow the dialogue by booking the addon. You'll be " -"returned to your contract overview and now should see the selected addon in " -"your list." +#: ../system/core-workflows.rst:None +msgid "Dialogue for adding a new workflow" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:30 -msgid "" -"The availability for ``sipgate.io`` packages and their levels highly depends " -"on the overall account type and product you've booked with Sipgate." +#: ../system/core-workflows/condition-operators.rst:2 +msgid "Core Workflow Condition Operators" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +#: ../system/core-workflows/condition-operators.rst:4 msgid "" -"Screencast showing the process on how to book the required sipgate.io addon" +"You might know that there is a separate section for explaining :doc:" +"`condition operators `. Head over there to " +"see a detailed explanation of many conditions and operators." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:52 -msgid "Step 2: Configure webhook for Zammad" +#: ../system/core-workflows/condition-operators.rst:8 +msgid "" +"Due to differences to other places in Zammad which are also using conditions " +"(e.g. triggers), you can find a dedicated description of operators for core " +"workflows below." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:38 +#: ../system/core-workflows/condition-operators.rst:12 msgid "" -"Within your ``Accountverwaltung`` navicate to your product ``sipgate.io``. " -"In the newly opened tab, switch from \"Clients\" to \"Webhooks\" and paste " -"the endpoint URLs from your Zammad instance like so:" +"Be aware that the availability of the operators depends on the selected " +"attribute and its field type. Some of the operators may only be available " +"for system attributes (e.g. for \"tags\", \"active\")." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:42 -msgid "Inbound endpoint to \"Incoming\"" +#: ../system/core-workflows/condition-operators.rst:20 +msgid "Operator" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:43 -msgid "Outbound endpoint to \"Outgoing\"" +#: ../system/core-workflows/condition-operators.rst:22 +msgid "after (absolute)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:47 -msgid "" -"Ensure to select at least one call group or phoneline within \"Sources\". " -"Other wise Sipgate will not indicate any incoming or outgoing calls to " -"Zammad." +#: ../system/core-workflows/condition-operators.rst:23 +msgid "Matches if a date/time is after a specific point in time." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screencast showing how to add Zammad's endpoint URLs to sipgate.ios webhook " -"configuration" +#: ../system/core-workflows/condition-operators.rst:24 +msgid "after (relative)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:55 -msgid "" -"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " -"the Webhooks → URLs section of Sipgate you can select which *sources* " -"Sipgate should notify Zammad about in- and outgoing calls." +#: ../system/core-workflows/condition-operators.rst:25 +msgid "Matches if a time span after a specified event has passed." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:59 -msgid "" -"Use either specific phone lines or use the option \"Use for all phonelines " -"and groups\" to notify Zammad about all existing lines of your Sipgate " -"account." +#: ../system/core-workflows/condition-operators.rst:26 +msgid "before (absolute)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screenshot showing a sample selection of phone numbers to use for the " -"Sipgates webhooks API" +#: ../system/core-workflows/condition-operators.rst:27 +msgid "Matches if a date/time is before a specific point in time." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:68 -msgid "This section also allows you to enable a Debug log." +#: ../system/core-workflows/condition-operators.rst:28 +msgid "before (relative)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "Screenshot showing an enabled Debug log option" +#: ../system/core-workflows/condition-operators.rst:29 +msgid "Matches if a time span after a specified event has not passed." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:73 -msgid "" -"After enabling you can use the Debug log section to see all sent webhook " -"calls to Zammad. You'll also can see the response." +#: ../system/core-workflows/condition-operators.rst:30 +msgid "contains" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screenshot showing sample log entries for Sipgates webhook calls to Zammad" +#: ../system/core-workflows/condition-operators.rst:31 +msgid "Matches if a specified value is present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:81 -msgid "Step 4 (optional): Further configurations for Sipgate" +#: ../system/core-workflows/condition-operators.rst:33 +msgid "Matches if all of the specified values are present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:80 -msgid "" -"If needed, you can now configure Zammad's Sipgate integration in more " -"detail. You can learn more about your options here: :ref:`Sipgate " -"integration settings `." +#: ../system/core-workflows/condition-operators.rst:35 +msgid "Matches if none of the specified values are present." msgstr "" -#: ../system/integrations/cti/sipgate.rst:2 -msgid "Sipgate (sipgate.io)" +#: ../system/core-workflows/condition-operators.rst:36 +msgid "contains not" msgstr "" -#: ../system/integrations/cti/sipgate.rst:16 -msgid "You need an administrative Sipgate account for your organization." +#: ../system/core-workflows/condition-operators.rst:37 +msgid "Matches if a specified value is not present." msgstr "" -#: ../system/integrations/cti/sipgate.rst:17 -msgid "" -"Zammad requires a ``sipgate.io`` addon from the feature store (please note " -"that API calls are not free with Sipgate. Rates may apply and differ from " -"account to account)." +#: ../system/core-workflows/condition-operators.rst:39 +msgid "Matches if one specified value is present." msgstr "" -#: ../system/integrations/cti/sipgate.rst:21 -msgid "Sipgate must be able to reach your Zammad instance." +#: ../system/core-workflows/condition-operators.rst:41 +msgid "Matches if one specified value is not present." msgstr "" -#: ../system/integrations/cti/sipgate.rst:25 -msgid ":doc:`provider-configurations/sipgate`" +#: ../system/core-workflows/condition-operators.rst:42 +msgid "does not match regex" msgstr "" -#: ../system/integrations/cti/sipgate.rst:24 -msgid "" -"Learn how to configure Sipgate to enable Zammad and Sipgate to communicate " -"with each other." +#: ../system/core-workflows/condition-operators.rst:43 +msgid "Matches if content doesn't fit to regex rule." msgstr "" -#: ../system/integrations/cti/sipgate.rst:33 -msgid "" -"Below endpoint settings affect the :doc:`sipgate.io configuration `." +#: ../system/core-workflows/condition-operators.rst:44 +msgid "ends with" msgstr "" -#: ../system/integrations/cti/sipgate.rst:37 -msgid "This endpoint is required for incoming call hooks." +#: ../system/core-workflows/condition-operators.rst:45 +msgid "Matches if content ends with specified value." msgstr "" -#: ../system/integrations/cti/sipgate.rst:40 -msgid "This endpoint is required for outgoing call hooks." +#: ../system/core-workflows/condition-operators.rst:46 +msgid "ends with one of" msgstr "" -#: ../system/integrations/cti/sipgate.rst:0 -msgid "Screenshot showing sample user mappings in between Sipgate and Zammad" +#: ../system/core-workflows/condition-operators.rst:47 +msgid "Matches if content ends with one of the specified values." msgstr "" -#: ../system/integrations/cti/sipgate.rst:69 -msgid "" -"You can find your agent's Sipgate username within ``Accountverwaltung → " -"Benutzer``. You're looking for the SIP-ID." +#: ../system/core-workflows/condition-operators.rst:48 +msgid "from (relative)" msgstr "" -#: ../system/integrations/cti/sipgate.rst:0 -msgid "Sample VoIP credentials for a Sipgate user" +#: ../system/core-workflows/condition-operators.rst:49 +msgid "Matches if date/time is after a period of time after an event." msgstr "" -#: ../system/integrations/cti/sipgate.rst:77 -msgid "Users with several devices also have several SIP-IDs." +#: ../system/core-workflows/condition-operators.rst:51 +msgid "Matches if content is equal to a specified value." msgstr "" -#: ../system/integrations/elasticsearch.rst:2 -msgid "Elasticsearch (SaaS)" +#: ../system/core-workflows/condition-operators.rst:52 +msgid "is any of" msgstr "" -#: ../system/integrations/elasticsearch.rst:4 -msgid "" -"The Elasticsearch integration allows you to create a read-only user to use " -"with your favorite reporting tool (e.g. like Grafana)." +#: ../system/core-workflows/condition-operators.rst:53 +msgid "Matches if content is equal to any of specified values." msgstr "" -#: ../system/integrations/elasticsearch.rst:7 -msgid "" -"If you want to take full advantage of the Zammad reporting, have a look at " -"our :docs:`Grafana ` " -"setup page as well." +#: ../system/core-workflows/condition-operators.rst:54 +msgid "is modified" msgstr "" -#: ../system/integrations/elasticsearch.rst:11 -#: ../system/subscription/index.rst:7 -msgid "**🚧 Hosted environment specific 🚧**" +#: ../system/core-workflows/condition-operators.rst:55 +msgid "Matches if content is modified." msgstr "" -#: ../system/integrations/elasticsearch.rst:13 -msgid "" -"This integration is only available for Hosted setups. In order to use " -"Elasticsearch you'll need the **Plus** subscription." +#: ../system/core-workflows/condition-operators.rst:57 +#: ../system/core-workflows/condition-operators.rst:61 +msgid "True from the moment of changing content until form submit." msgstr "" -#: ../system/integrations/elasticsearch.rst:16 -msgid "" -"Self hosted users have all the control over their self hosted Elasticsearch " -"instances." +#: ../system/core-workflows/condition-operators.rst:58 +msgid "is modified to" msgstr "" -#: ../system/integrations/elasticsearch.rst:None -msgid "Elasticsearch integration page on SaaS environments" +#: ../system/core-workflows/condition-operators.rst:59 +msgid "Matches if content is modified to a specific value." msgstr "" -#: ../system/integrations/elasticsearch.rst:27 -msgid "" -"Please note the following limitations of Elasticsearch access on hosted " -"environments:" +#: ../system/core-workflows/condition-operators.rst:62 +msgid "is none of" msgstr "" -#: ../system/integrations/elasticsearch.rst:30 -msgid "access to the Elasticsearch index is read-only access" +#: ../system/core-workflows/condition-operators.rst:63 +msgid "Matches if content is none of any specified values." msgstr "" -#: ../system/integrations/elasticsearch.rst:31 -msgid "currently you're limited to user only" +#: ../system/core-workflows/condition-operators.rst:65 +msgid "Matches if content is not equal to a specified value." msgstr "" -#: ../system/integrations/elasticsearch.rst:32 -msgid "" -"Reporting tools that require to write into the indexes (like Kibana) are not " -"supported" +#: ../system/core-workflows/condition-operators.rst:67 +msgid "Matches if content is present." msgstr "" -#: ../system/integrations/elasticsearch.rst:34 -msgid "IP access restriction is currently not yet supported" +#: ../system/core-workflows/condition-operators.rst:68 +msgid "just changed" msgstr "" -#: ../system/integrations/elasticsearch.rst:37 -msgid "Activating Elasticsearch Access" +#: ../system/core-workflows/condition-operators.rst:69 +msgid "Matches if content has changed." msgstr "" -#: ../system/integrations/elasticsearch.rst:39 +#: ../system/core-workflows/condition-operators.rst:71 +#: ../system/core-workflows/condition-operators.rst:75 msgid "" -"By default external access to your Elasticsearch index is not active. You " -"can enable the integration at any time if needed." +"Only true for the moment of changing content until next form field action/" +"click." msgstr "" -#: ../system/integrations/elasticsearch.rst:42 -msgid "" -"Please ensure to note down the password provided - you won't have access to " -"it afterwards." +#: ../system/core-workflows/condition-operators.rst:72 +msgid "just changed to" msgstr "" -#: ../system/integrations/elasticsearch.rst:None -msgid "Screencast showing activation of Elasticsearch integration" +#: ../system/core-workflows/condition-operators.rst:73 +msgid "Matches if content has changed to a specified value." msgstr "" -#: ../system/integrations/elasticsearch.rst:51 -msgid "Connection Settings" +#: ../system/core-workflows/condition-operators.rst:76 +msgid "matches regex" msgstr "" -#: ../system/integrations/elasticsearch.rst:53 -msgid "" -"This section holds the most important general information for accessing your " -"Elasticsearch indexes - such as:" +#: ../system/core-workflows/condition-operators.rst:77 +msgid "Matches if value fits to regex rule." msgstr "" -#: ../system/integrations/elasticsearch.rst:57 -msgid "A unique subdomain that does not tell your real instance URL." +#: ../system/core-workflows/condition-operators.rst:79 +msgid "Matches if no content is present." msgstr "" -#: ../system/integrations/elasticsearch.rst:61 -msgid "Software" +#: ../system/core-workflows/condition-operators.rst:80 +msgid "starts with" msgstr "" -#: ../system/integrations/elasticsearch.rst:60 -msgid "" -"The major version of the search index being used. This is required by some " -"Reporting tools like Grafana." +#: ../system/core-workflows/condition-operators.rst:81 +msgid "Matches if content starts with specified value." msgstr "" -#: ../system/integrations/elasticsearch.rst:64 -msgid "Authentication" +#: ../system/core-workflows/condition-operators.rst:82 +msgid "starts with one of" msgstr "" -#: ../system/integrations/elasticsearch.rst:64 -msgid "The authentication type being supported. ``Basic Authentication``" +#: ../system/core-workflows/condition-operators.rst:83 +msgid "Matches if content starts with one of the specified values." msgstr "" -#: ../system/integrations/elasticsearch.rst:67 -msgid "Available Indexes" +#: ../system/core-workflows/condition-operators.rst:84 +msgid "till (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:69 -msgid "" -"Within this section we're displaying the -in our opinion- most important " -"indexes for a Zammad instance." +#: ../system/core-workflows/condition-operators.rst:85 +msgid "Matches if date/time is before a period of time before an event." msgstr "" -#: ../system/integrations/elasticsearch.rst:72 -msgid "" -"If you require all indexes or our listing is not good enough for you, point " -"your browser to the URL we're providing and append ``/_aliases?" -"pretty=true``. The result should look like this: ``https://.zammad.com/" -"_aliases?pretty=true``." +#: ../system/core-workflows/condition-operators.rst:86 +msgid "today" msgstr "" -#: ../system/integrations/elasticsearch.rst:77 -msgid "" -"Your browser will automatically ask for your credentials - you'll then see " -"something like this:" +#: ../system/core-workflows/condition-operators.rst:87 +msgid "Matches if date/time is today." msgstr "" -#: ../system/integrations/elasticsearch.rst:125 -msgid "Credentials" +#: ../system/core-workflows/condition-operators.rst:88 +msgid "within last (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:127 +#: ../system/core-workflows/condition-operators.rst:89 msgid "" -"Within this section Zammad displays your available users. The password is " -"provided once (upon activation) and cannot be retrieved after that." +"Matches if date/time content is within specified period of time before now." msgstr "" -#: ../system/integrations/elasticsearch.rst:131 -msgid "" -"If you need to change or reset your Elasticsearch user password, use the " -"\"Reset password\" button in the credentials table. Doing so creates a brand " -"new password for the account in question. This change is immediate, keep in " -"mind that this may affect third party tools connected to your instance." +#: ../system/core-workflows/condition-operators.rst:91 +msgid "within next (relative)" msgstr "" -#: ../system/integrations/exchange.rst:2 -msgid "Exchange" +#: ../system/core-workflows/condition-operators.rst:92 +msgid "" +"Matches if date/time content is within specified period of time after now." msgstr "" -#: ../system/integrations/exchange.rst:4 -msgid "" -"With Zammad's Exchange integration, you can easily use existing address " -"books without having to update more than one source." +#: ../system/core-workflows/how-do-they-work.rst:2 +msgid "How do they work?" msgstr "" -#: ../system/integrations/exchange.rst:7 +#: ../system/core-workflows/how-do-they-work.rst:4 msgid "" -"However, you should refrain from syncing all addresses, as the results may " -"not be what you expect (Exchange collects huge amounts of addresses). A " -"central address book of your company to sync makes more sense, as you can " -"ensure that Zammad gets only the data you need and want. Apart from this, it " -"is even not possible to sync the Global Address List (GAL) of your Exchange " -"system with Zammad." +"Core Workflows are executed according to their priority. If two workflows " +"have the same priority, they are executed in alphabetical order based on " +"their **name**." msgstr "" -#: ../system/integrations/exchange.rst:16 +#: ../system/core-workflows/how-do-they-work.rst:8 msgid "" -"**Exchange and LDAP:** The exchange sync can be overruled by Zammad's LDAP " -"integration. If you have the same users in both sources, the LDAP version " -"will always be Zammad's pick." +"Because of the way Core Workflows work, all changes to attributes are " +"checked with the application server - please see :doc:`limitations` for " +"possible issues." msgstr "" -#: ../system/integrations/exchange.rst:19 +#: ../system/core-workflows/how-do-they-work.rst:12 msgid "" -"**One way sync:** the Exchange sync is one way. Exchange => Zammad. Changes " -"to your users inside of Zammad might be overwritten by the Exchange sync." +"Below we're talking about settings that are important and not self-" +"explanatory." msgstr "" -#: ../system/integrations/exchange.rst:24 +#: ../system/core-workflows/how-do-they-work.rst:17 msgid "" -"To configure Exchange integration, simply go to the System > Integrations > " -"Exchange in the admin panel. Press \"change\" and follow the wizard for " -"adding the needed Exchange information to Zammad. On the last two steps " -"Zammad will ask you for the address book(s) and your desired attribute " -"mapping. By default, Zammad only maps email address, first- and lastname. " -"Technically, you can map any Exchange object to a Zammad user object (this " -"also works for custom objects!)." +"Choose the object context you want to run the workflow in. This will decide " +"on your available attributes and actions." msgstr "" -#: ../system/integrations/exchange.rst:35 -msgid "" -"If the SSL verification fails while connecting to Exchange, Zammad will ask " -"you to turn it off temporarily." +#: ../system/core-workflows/how-do-they-work.rst:20 +msgid "Ticket objects also have access to the ticket customer." msgstr "" -#: ../system/integrations/exchange.rst:38 +#: ../system/core-workflows/how-do-they-work.rst:25 msgid "" -"Please be aware that **turning off SSL verification is a security risk**. It " -"should only be used temporarily or for testing purposes. If turned off, " -"there is no verification of the certificate, which means that every " -"presented certificate will be accepted." +"Choose in which situation the workflow is applied. Contexts can be combined " +"to avoid duplicate workflows." msgstr "" -#: ../system/integrations/exchange.rst:43 -msgid "" -"After pressing Continue, Zammad will check if the configuration is okay. You " -"can then enable Exchange and start your first sync. The sync will then run " -"hourly - if you need to change mappings or the address book(s), you can " -"change the configuration at any time." +#: ../system/core-workflows/how-do-they-work.rst:30 +msgid "Creation mask" msgstr "" -#: ../system/integrations/exchange.rst:50 +#: ../system/core-workflows/how-do-they-work.rst:29 msgid "" -"After the sync has finished, you can find the new Exchange contacts under " -"\"Users\". Zammad integrates them just as normal users." +"If selected, your conditions and actions will affect all applicable creation " +"masks." msgstr "" -#: ../system/integrations/exchange.rst:55 -msgid "" -"In some cases you might see unique IDs as \"Login\" instead of the email " -"address. This is normal and doesn't affect the login or email mapping for " -"that entry." +#: ../system/core-workflows/how-do-they-work.rst:34 +msgid "Edit mask" msgstr "" -#: ../system/integrations/github.rst:4 +#: ../system/core-workflows/how-do-they-work.rst:33 msgid "" -"Use GitHub integration to track GitHub issues directly within Zammad " -"tickets. Add issue hyperlinks and get a live summary of metadata like status " -"(open/closed), assignee, labels, and more." +"If selected, your conditions and actions will affect all applicable edit " +"masks." msgstr "" -#: ../system/integrations/github.rst:8 -msgid "Please note that our GitHub integration does not support pull requests." +#: ../system/core-workflows/how-do-they-work.rst:39 +msgid "" +"Zammad differentiates between selected and saved conditions. These can be " +"combined wherever needed." msgstr "" -#: ../system/integrations/github.rst:None -msgid "Integration page for GitHub" +#: ../system/core-workflows/how-do-they-work.rst:42 +msgid "**⚠️ Restrict workflows to specific roles if needed!**" msgstr "" -#: ../system/integrations/github.rst:18 +#: ../system/core-workflows/how-do-they-work.rst:44 msgid "" -"In your GitHub settings, create a new API token under **Developer settings > " -"Personal access tokens > Generate new token**. Leave the **Scopes** section " -"empty." +"By default and unless configured in conditions, workflow rules are executed " +"for **all roles**. This also affects your customers!" msgstr "" -#: ../system/integrations/github.rst:0 ../system/integrations/gitlab.rst:0 -msgid "Screencast showing how to create a new API token" +#: ../system/core-workflows/how-do-they-work.rst:50 +msgid "Selected Conditions" msgstr "" -#: ../system/integrations/github.rst:27 -msgid "Create a new API key with no scopes/privileges." +#: ../system/core-workflows/how-do-they-work.rst:48 +msgid "" +"These conditions are based on form values and match if an appropriate " +"selection is made (e.g. choosing another group in the ticket without " +"saving). This applies for drafts (active selection) and currently saved " +"values." msgstr "" -#: ../system/integrations/github.rst:29 -msgid "🔒 **Will this work for private repos?**" +#: ../system/core-workflows/how-do-they-work.rst:64 +msgid "Saved Conditions" msgstr "" -#: ../system/integrations/github.rst:31 +#: ../system/core-workflows/how-do-they-work.rst:53 msgid "" -"No. To link private repo issues, **use the** ``repo`` **scope instead**. " -"Bear in mind that the resulting token will have `lots of permissions that it " -"doesn't actually need `_, which presents a security risk if your token ever falls into " -"the wrong hands." +"These conditions only match if the selected values are stored in the " +"database. It ignores the current value or selection of the field, as long as " +"the changes are not saved (e.g. performing field operations for an existing " +"ticket, which is viewed/opened by an agent)." msgstr "" -#: ../system/integrations/github.rst:37 +#: ../system/core-workflows/how-do-they-work.rst:60 msgid "" -"Unfortunately, because of how GitHub's OAuth token scopes are set up, this " -"is the only way to link issues on private repos." +"Keep in mind that the value has to be available in the situation where you " +"need it. Otherwise the condition won't match." msgstr "" -#: ../system/integrations/github.rst:40 -msgid "Enter your new API token in Zammad and enable GitHub integration." +#: ../system/core-workflows/how-do-they-work.rst:63 +msgid "" +"Example: you can't perform any actions with *saved condition* on a ticket in " +"creation, because there are no saved values at that time." msgstr "" -#: ../system/integrations/github.rst:0 -msgid "Screencast showing how to configure Zammad's GitHub integration" +#: ../system/core-workflows/how-do-they-work.rst:66 +msgid "" +"You can find a description of the condition operators for core workflows :" +"doc:`here `." msgstr "" -#: ../system/integrations/github.rst:47 +#: ../system/core-workflows/how-do-they-work.rst:72 msgid "" -"Use the default API endpoint (``https://api.github.com/graphql``) unless " -"you're using GitHub Enterprise Server." +"Which actions should we run on the relevant fields? The possible actions " +"depend on the object type. However, usually you can at least change the " +"visibility and whether the field is mandatory." msgstr "" -#: ../system/integrations/github.rst:50 -msgid "" -"Once completed, a new GitHub issues tab will appear in the ticket pane. 🎉" +#: ../system/core-workflows/how-do-they-work.rst:76 +msgid "Be aware that actions are not available for **related** context." msgstr "" -#: ../system/integrations/github.rst:59 ../system/integrations/gitlab.rst:52 -msgid "Token verification is taking a long time" -msgstr "" - -#: ../system/integrations/github.rst:56 ../system/integrations/gitlab.rst:49 -msgid "" -"Slight delays are normal (<2 min.), especially for systems under heavy load." -msgstr "" - -#: ../system/integrations/github.rst:58 +#: ../system/core-workflows/how-do-they-work.rst:78 msgid "" -"Self-hosted administrators, please check your network settings to ensure " -"that your Zammad server can reach ``api.github.com``." -msgstr "" - -#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 -msgid "I reloaded the page and now the API token is gone" +"**Example:** Let's assume you are working in the ticket context. While you " +"can have customer *conditions*, you *can't adjust* objects with actions in " +"that scope. That's because this wouldn't have any impact on the ticket " +"dialog. Of course all ticket attributes (state, owner, ...) are available." msgstr "" -#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 +#: ../system/core-workflows/how-do-they-work.rst:84 msgid "" -"This may indicate that Zammad is still verifying your API token. Try " -"reloading the page again in a couple minutes." +"Please also have a look at our :doc:`limitations` to be safe from surprises." msgstr "" -#: ../system/integrations/gitlab.rst:2 -msgid "GitLab" +#: ../system/core-workflows/how-do-they-work.rst:88 +msgid "Available Operators" msgstr "" -#: ../system/integrations/gitlab.rst:4 -msgid "" -"Use GitLab integration to track GitLab issues directly within Zammad " -"tickets. Add issue hyperlinks and get a live summary of metadata like status " -"(open/closed), assignee, labels, and more." +#: ../system/core-workflows/how-do-they-work.rst:90 +msgid "The availability of operators depends on the object type and scope." msgstr "" -#: ../system/integrations/gitlab.rst:8 +#: ../system/core-workflows/how-do-they-work.rst:94 msgid "" -"Please note that our GitLab integration does not support merge requests." -msgstr "" - -#: ../system/integrations/gitlab.rst:None -msgid "Integration page for GitLab" +"Please note that actions may or may not restrict API based access to " +"attributes. We're displaying the following icons for your overview to " +"understand these limits better:" msgstr "" -#: ../system/integrations/gitlab.rst:18 -msgid "" -"In your GitLab preferences, create a new API token under **Access Tokens**." +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|api| This icon indicates the action affects the API." msgstr "" -#: ../system/integrations/gitlab.rst:20 -msgid "Under **Select scopes**, choose ``read_api`` only." +#: ../system/core-workflows/how-do-they-work.rst:163 +msgid "api" msgstr "" -#: ../system/integrations/gitlab.rst:27 -msgid "🔒 **If you wish to link issues on any private repos...**" +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|ui| This icon indicates the action only affects the web interface." msgstr "" -#: ../system/integrations/gitlab.rst:29 -msgid "Your API token must belong to an account with access to those repos." +#: ../system/core-workflows/how-do-they-work.rst:167 +msgid "ui" msgstr "" -#: ../system/integrations/gitlab.rst:31 -msgid "Enter your new API token in Zammad and enable GitLab integration." +#: ../system/core-workflows/how-do-they-work.rst:102 +msgid "show |ui|" msgstr "" -#: ../system/integrations/gitlab.rst:0 -msgid "Screencast showing how to configure Zammad's GitLab integration" +#: ../system/core-workflows/how-do-they-work.rst:102 +msgid "Display the chosen field. Allows setting of values." msgstr "" -#: ../system/integrations/gitlab.rst:40 -msgid "" -"Use the default API endpoint (``https://gitlab.com/api/graphql``) unless " -"you're a self-hosted GitLab user." +#: ../system/core-workflows/how-do-they-work.rst:109 +msgid "hide |ui|" msgstr "" -#: ../system/integrations/gitlab.rst:43 +#: ../system/core-workflows/how-do-they-work.rst:105 msgid "" -"Once completed, a new GitLab issues tab will appear in the ticket pane. 🎉" +"Hide the chosen field. However, it technically still allows setting the " +"field." msgstr "" -#: ../system/integrations/gitlab.rst:51 +#: ../system/core-workflows/how-do-they-work.rst:108 msgid "" -"Self-hosted administrators, please check your network settings to ensure " -"that your Zammad server can reach ``gitlab.com``." +"Please note that the field is **not** gone and still contains an existing " +"value (if set)! Consider *remove* instead, if you want this field to be gone." msgstr "" -#: ../system/integrations/i-doit.rst:2 -msgid "i-doit" +#: ../system/core-workflows/how-do-they-work.rst:112 +msgid "remove |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:4 -msgid "" -"`i-doit `_ is an open-source **configuration " -"management database** - in other words, a tool for keeping tabs on every " -"single piece of your physical and digital infrastructure, from network " -"equipment to virtual machines on down to the faceplates on your rack shelves " -"and more." +#: ../system/core-workflows/how-do-they-work.rst:112 +msgid "Entirely removes the field. The field value will not be evaluated." msgstr "" -#: ../system/integrations/i-doit.rst:10 -msgid "" -"What's that got to do with Zammad? Well, if you used tickets to track issues " -"with all that hardware, you might start wishing there was a way they could " -"talk to each other." +#: ../system/core-workflows/how-do-they-work.rst:115 +msgid "set mandatory |ui| |api|" msgstr "" -#: ../system/integrations/i-doit.rst:14 -msgid "Zammad gives you two:" +#: ../system/core-workflows/how-do-they-work.rst:115 +msgid "Sets the field to mandatory." msgstr "" -#: ../system/integrations/i-doit.rst:17 -msgid "1. Add i-doit Links to Zammad Tickets" +#: ../system/core-workflows/how-do-they-work.rst:118 +msgid "set optional |ui| |api|" msgstr "" -#: ../system/integrations/i-doit.rst:20 ../system/integrations/i-doit.rst:80 -msgid "What Users See" +#: ../system/core-workflows/how-do-they-work.rst:118 +msgid "Sets the field to optional." msgstr "" -#: ../system/integrations/i-doit.rst:26 -msgid "i-doit integration in Zammad's ticket pane" +#: ../system/core-workflows/how-do-they-work.rst:124 +msgid "add option |ui| |api|" msgstr "" -#: ../system/integrations/i-doit.rst:26 -msgid "" -"The i-doit integration will appear under a new 🖨 tab in the ticket pane." +#: ../system/core-workflows/how-do-they-work.rst:121 +msgid "Allows adding options to tree selects or selects." msgstr "" -#: ../system/integrations/i-doit.rst:28 +#: ../system/core-workflows/how-do-they-work.rst:123 msgid "" -"i-doit integration puts a new tab in Zammad's ticket pane where you can add " -"links to existing i-doit devices for easy reference. (See our :user-docs:" -"`user documentation ` to learn " -"how it works in practice)." +"You have to use the \"remove option\" before performing this action. It " +"allows you to use *existing* configured values." msgstr "" -#: ../system/integrations/i-doit.rst:36 ../system/integrations/i-doit.rst:93 -msgid "How to Set it Up" +#: ../system/core-workflows/how-do-they-work.rst:128 +msgid "remove option |ui| |api|" msgstr "" -#: ../system/integrations/i-doit.rst:38 +#: ../system/core-workflows/how-do-they-work.rst:127 msgid "" -"It requires i-doit's `API Add-on `_. Make sure to have it properly set up. Use the following setting:" +"Allows removing options from tree selects or selects. It allows you to use " +"*existing* configured values." msgstr "" -#: ../system/integrations/i-doit.rst:42 -msgid "Active: ``Yes``" +#: ../system/core-workflows/how-do-they-work.rst:134 +msgid "set fixed to |ui| |api|" msgstr "" -#: ../system/integrations/i-doit.rst:43 -msgid "Enforce authentication by username and password: ``No``" +#: ../system/core-workflows/how-do-they-work.rst:131 +msgid "Reduces the available options by your selection." msgstr "" -#: ../system/integrations/i-doit.rst:45 +#: ../system/core-workflows/how-do-they-work.rst:133 msgid "" -"To set it up, enable the integration in the Zammad admin panel under " -"**System > Integrations > i-doit**:" +"This reduces your workflows in terms of *add option* and *remove option*." msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "i-doit settings within the integration pages" +#: ../system/core-workflows/how-do-they-work.rst:137 +msgid "fill in |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:53 -msgid "The root URL of your i-doit installation." +#: ../system/core-workflows/how-do-they-work.rst:137 +msgid "Allows filling in of string and integer fields with your values." msgstr "" -#: ../system/integrations/i-doit.rst:62 -msgid "API token" +#: ../system/core-workflows/how-do-they-work.rst:141 +msgid "fill in empty |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:56 +#: ../system/core-workflows/how-do-they-work.rst:140 msgid "" -"Found in the i-doit admin panel under **Interfaces / external data > JSON-" -"RPC API > Common Settings**." +"Allows filling in of string and integer fields with your values **if the " +"field is empty**." msgstr "" -#: ../system/integrations/i-doit.rst:0 -msgid "i-doit administration interface with API configuration" +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "select |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:67 -msgid "Client ID" +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "Select a specific value within a select, tree select or boolean field." msgstr "" -#: ../system/integrations/i-doit.rst:65 -msgid "A unique name to identify Zammad within i-doit." +#: ../system/core-workflows/how-do-they-work.rst:153 +msgid "auto select |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:67 -msgid "(Zammad does not require you to enter a value here, but i-doit might!)" +#: ../system/core-workflows/how-do-they-work.rst:147 +msgid "Helps users with tree select and select fields:" msgstr "" -#: ../system/integrations/i-doit.rst:70 +#: ../system/core-workflows/how-do-they-work.rst:149 msgid "" -"Here you can decide if the certificate of your i-doit system has to be " -"verified or not. In case you are using custom certificates, please have a " -"look at :doc:`how to add them to Zammad `." +"If the field has only one option available for selection and no value yet, " +"the value will be automatically set." msgstr "" -#: ../system/integrations/i-doit.rst:77 -msgid "2. List / Create Zammad Tickets in i-doit" +#: ../system/core-workflows/how-do-they-work.rst:152 +msgid "" +"This option only works if you have one value and doesn't work if there is " +"more than one option available." msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "Zammad integration in i-doit's device view" +#: ../system/core-workflows/how-do-they-work.rst:157 +msgid "set readonly |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:86 +#: ../system/core-workflows/how-do-they-work.rst:156 msgid "" -"i-doit's ticket system integration gives you a way to see all the tickets " -"for a given device without ever leaving i-doit. (See our :user-docs:`user " -"documentation ` to learn how it " -"works in practice)." +"Allows you to display an attribute as read only (which means no changes are " +"possible)." msgstr "" -#: ../system/integrations/i-doit.rst:95 -msgid "" -"Enable this integration in the i-doit admin panel under **Interfaces / " -"external data > Trouble Ticket System (TTS) > Configuration**:" +#: ../system/core-workflows/how-do-they-work.rst:161 +msgid "unset readonly |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "i-doit administration interface with TTS configuration" +#: ../system/core-workflows/how-do-they-work.rst:160 +msgid "" +"In case a workflow set the field in question to read only, you can undo this " +"with option above." msgstr "" -#: ../system/integrations/i-doit.rst:104 -msgid "TTS-Type" +#: ../system/core-workflows/how-do-they-work.rst:172 +msgid "Stop after match" msgstr "" -#: ../system/integrations/i-doit.rst:104 -msgid "``Zammad``" +#: ../system/core-workflows/how-do-they-work.rst:174 +msgid "" +"Here you can decide if other workflows are executed after the current one." msgstr "" -#: ../system/integrations/i-doit.rst:115 -msgid "Username / Password" +#: ../system/core-workflows/how-do-they-work.rst:176 +msgid "" +"If set to ``no`` (default), further workflows will be executed if they match " +"the condition. In this case, it is possible that your actions from the " +"current workflow can be overwritten by another workflow." msgstr "" -#: ../system/integrations/i-doit.rst:107 -msgid "Login credentials for a Zammad agent." +#: ../system/core-workflows/how-do-they-work.rst:180 +msgid "" +"If set to ``yes``, no further worflows will be executed after the current " +"one." msgstr "" -#: ../system/integrations/i-doit.rst:109 -msgid "" -"This agent must have **read permission** for all :doc:`groups ` that plan on using the i-doit integration." +#: ../system/core-workflows/how-do-they-work.rst:184 +msgid "Priority" msgstr "" -#: ../system/integrations/i-doit.rst:113 +#: ../system/core-workflows/how-do-they-work.rst:186 msgid "" -"You may even wish to create a dedicated agent account just for this " -"integration (otherwise, if the agent ever changes her password, you will " -"have to remember to update it here)." -msgstr "" - -#: ../system/integrations/i-doit.rst:117 -msgid "URL incl. protocol" +"You can define the sequence, in which the workflows are executed. The " +"default value is ``500``." msgstr "" -#: ../system/integrations/i-doit.rst:118 -msgid "``https://your.zammad.domain``" +#: ../system/core-workflows/how-do-they-work.rst:189 +msgid "" +"The workflows are executed in ascending order by their priority. That means " +"lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." msgstr "" -#: ../system/integrations/index.rst:2 -msgid "Integrations" -msgstr "" +#: ../system/core-workflows/learn-by-example.rst:2 +#, fuzzy +msgid "Learn by Example" +msgstr "Primjer" -#: ../system/integrations/index.rst:4 +#: ../system/core-workflows/learn-by-example.rst:4 msgid "" -"Zammad offers numerous integrations that add rich features to your instance." +"This page provides some basic examples for Core Workflows. Of course you can " +"build much more complex workflows if needed." msgstr "" -#: ../system/integrations/index.rst:6 -msgid "We're still working on this part of our documentation, stay tight!" +#: ../system/core-workflows/learn-by-example.rst:7 +msgid "" +"To learn about Core Workflows in detail, first go to :doc:`how-do-they-work`." msgstr "" -#: ../system/integrations/index.rst:10 -msgid "Integrations for Phone Systems" -msgstr "" +#: ../system/core-workflows/learn-by-example.rst:10 +#, fuzzy +msgid "Group Based Examples" +msgstr "Primjer" -#: ../system/integrations/index.rst:14 +#: ../system/core-workflows/learn-by-example.rst:12 msgid "" -"Your VoIP provider or telephony system is not listed? Possibly your provider " -"supports Zammad by using the generic CTI - if you're unsure ask your " -"provider." +"All following workflows have the same base configurations. The workflow may " +"not use them all." msgstr "" -#: ../system/integrations/index.rst:18 -msgid "" -"Provider does not support Zammad? Consider creating a `feature request in " -"the Zammad Community `_." -msgstr "" +#: ../system/core-workflows/learn-by-example.rst:15 +#, fuzzy +msgid "Groups:" +msgstr "grupa" -#: ../system/integrations/index.rst:31 -msgid "Integrations for Authentication and Customers" +#: ../system/core-workflows/learn-by-example.rst:20 +msgid "Attributes:" msgstr "" -#: ../system/integrations/index.rst:44 -msgid "Integrations for Monitoring Systems" +#: ../system/core-workflows/learn-by-example.rst:22 +msgid "Category (Single tree selection field, not mandatory, agents only)" msgstr "" -#: ../system/integrations/index.rst:46 -msgid "This section currently misses the following integrations:" +#: ../system/core-workflows/learn-by-example.rst:23 +msgid "" +"Approved (Boolean field, not mandatory, not shown, ``false`` as default)" msgstr "" -#: ../system/integrations/index.rst:48 -msgid "Icinga" +#: ../system/core-workflows/learn-by-example.rst:24 +msgid "Operating System (Text field, not mandatory, not shown)" msgstr "" -#: ../system/integrations/index.rst:49 -msgid "Monit" +#: ../system/core-workflows/learn-by-example.rst:25 +msgid "Software used (Single selection field, not mandatory, not shown)" msgstr "" -#: ../system/integrations/index.rst:50 -msgid "Nagios" +#: ../system/core-workflows/learn-by-example.rst:68 +msgid "Group specific values and fields" msgstr "" -#: ../system/integrations/index.rst:60 -msgid "Integrations for Issue Trackers" +#: ../system/core-workflows/learn-by-example.rst:28 +msgid "" +"This workflow set depends on the category field. It reduces the available " +"set of values based on the group selected." msgstr "" -#: ../system/integrations/index.rst:70 -msgid "Other Integrations" +#: ../system/core-workflows/learn-by-example.rst:33 +msgid "Workflow 2nd Level group" msgstr "" -#: ../system/integrations/index.rst:72 +#: ../system/core-workflows/learn-by-example.rst:35 msgid "" -"This section will hold any other integration that can't be grouped up (yet)." +"This reduces the category options to ``2nd Level/*``, ``Internal/*`` and " +"``Others``. It also sets further required fields to mandatory and visible." msgstr "" -#: ../system/integrations/ldap/index.rst:2 -msgid "LDAP / Active Directory" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for 2nd level" msgstr "" -#: ../system/integrations/ldap/index.rst:4 -msgid "" -"Zammad comes with a powerful LDAP integration that allows you to have a " -"single source of truth. By this you reduce the number of login credentials " -"your user has to remember." +#: ../system/core-workflows/learn-by-example.rst:43 +msgid "Workflow Support group" msgstr "" -#: ../system/integrations/ldap/index.rst:10 +#: ../system/core-workflows/learn-by-example.rst:45 msgid "" -"The LDAP source is also a perfect candidate for Zammad's :docs:`Kerberos " -"Single Sign-On ` but also works as addition " -"to other :doc:`/settings/security/third-party`." +"This reduces the category options to ``Support/*``, ``Internal/*`` and " +"``Others``. It also sets further required fields to visible." msgstr "" -#: ../system/integrations/ldap/index.rst:None -msgid "Zammands LDAP management page" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for support" msgstr "" -#: ../system/integrations/ldap/index.rst:25 -msgid "📝 :doc:`manage`" +#: ../system/core-workflows/learn-by-example.rst:53 +msgid "Workflow Sales group" msgstr "" -#: ../system/integrations/ldap/index.rst:25 -msgid "Add, modify, remove or re-arrange your LDAP-Sources as needed." +#: ../system/core-workflows/learn-by-example.rst:55 +msgid "" +"This reduces the category options to ``Sales/*``, ``Internal/*`` and " +"``Others``." msgstr "" -#: ../system/integrations/ldap/index.rst:30 -msgid "Before you continue, please note the following limitations." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for sales" msgstr "" -#: ../system/integrations/ldap/index.rst:32 -msgid "Mapping / Synchronizing organizations is not possible" +#: ../system/core-workflows/learn-by-example.rst:68 +#: ../system/integrations/slack.rst:88 +msgid "The Result" msgstr "" -#: ../system/integrations/ldap/index.rst:36 +#: ../system/core-workflows/learn-by-example.rst:63 msgid "" -"You may want to consider using domain based assignments to overcome this " -"issue. Learn more on :doc:`/manage/organizations/index`." +"This is what the agent would experience with the above workflows in place." msgstr "" -#: ../system/integrations/ldap/index.rst:39 +#: ../system/core-workflows/learn-by-example.rst:0 msgid "" -"Zammad's LDAP sync is one way. Editing user settings or permissions may be " -"overwritten upon the next sync depending on your configuration." -msgstr "" - -#: ../system/integrations/ldap/index.rst:41 -msgid "Nested groups are not supported." +"Workflow shows objects and limits options based on selections on the group" msgstr "" -#: ../system/integrations/ldap/index.rst:42 -msgid "Synchronizing user avatars from LDAP is not supported." +#: ../system/core-workflows/learn-by-example.rst:90 +msgid "Approval process" msgstr "" -#: ../system/integrations/ldap/index.rst:43 -msgid "Unlike user filters, group filters cannot be changed." +#: ../system/core-workflows/learn-by-example.rst:71 +msgid "" +"In this case ``approved`` is visible to agents by default. For this " +"workflow, an additional role ``Approval person`` is required (no further " +"permissions)." msgstr "" -#: ../system/integrations/ldap/index.rst:44 -msgid "" -"When a user originates from an LDAP server, Zammad will try to verify the " -"login credentials against LDAP first - if this fails Zammad will check its " -"local database." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that restricts an approval attribute to specific roles" msgstr "" -#: ../system/integrations/ldap/index.rst:50 +#: ../system/core-workflows/learn-by-example.rst:81 msgid "" -"Users can have local passwords even if they're LDAP users! You can learn " -"more about user accounts in general on :doc:`/manage/users/index`." +"This workflow may work best in combination with a :doc:`trigger ` but technically, this is not required." msgstr "" -#: ../system/integrations/ldap/index.rst:54 +#: ../system/core-workflows/learn-by-example.rst:84 msgid "" -"When several LDAP sources contain the same user (meaning the same email " -"address), the user in question will be updated with every source configured. " -"*The last LDAP source will win.*" +"Select fields may be a better approach because they allow more values than " +"just a simple ``true`` or ``false``." msgstr "" -#: ../system/integrations/ldap/index.rst:58 +#: ../system/core-workflows/learn-by-example.rst:0 msgid "" -"This is subject to change with `Issue 4109 `_ in the future." +"Workflow fixes possible values of \"Approved ?\" to a specific selection " +"depending on the users role" msgstr "" -#: ../system/integrations/ldap/index.rst:60 -msgid "" -"Synchronization statistics currently affect *all* configured LDAP sources. " -"This also applies for newly added or updated sources." +#: ../system/core-workflows/learn-by-example.rst:103 +msgid "State dependent mandatory fields" msgstr "" -#: ../system/integrations/ldap/index.rst:63 +#: ../system/core-workflows/learn-by-example.rst:93 msgid "" -"This is subject to change with `Issue 4108 `_ in the future." +"This workflow sets ``Category`` to mandatory if the agent wants to set the " +"states ``closed`` or ``pending close`` to enforce categorization." msgstr "" -#: ../system/integrations/ldap/index.rst:65 -msgid "" -"Zammad currently has limited fallback server support. You can workaround " -"this by providing several sources - however, ensure to have the exact same " -"configuration on your fallback." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that sets fields to mandatory on specific states" msgstr "" -#: ../system/integrations/ldap/index.rst:69 +#: ../system/core-workflows/learn-by-example.rst:0 msgid "" -"This is subject to improve with `Issue 4107 `_ in the future." +"Workflow sets category field to mandatory upon choosing closed or pending " +"close as state" msgstr "" -#: ../system/integrations/ldap/index.rst:76 -msgid "" -"This section holds all requests Zammad handled for all LDAP sources. These " -"entries can either contain synchronization information or logins " -"(authentication attempts via Zammad's login interface)." +#: ../system/core-workflows/learn-by-example.rst:106 +msgid "Manual Ticket Handover Process" msgstr "" -#: ../system/integrations/ldap/index.rst:80 -msgid "" -"By clicking on any request, Zammad will provide even more information. The " -"provided information can be useful when something does not work as expected." +#: ../system/core-workflows/learn-by-example.rst:108 +msgid "This example covers the handover of a ticket from one agent to another:" msgstr "" -#: ../system/integrations/ldap/index.rst:85 +#: ../system/core-workflows/learn-by-example.rst:110 msgid "" -"Especially a LDAP synchronization can cause many log entries. The web " -"interface will always limit the number of shown entries to the last 50 " -"entries." +"When the ticket owner is modified, a new text field (\"Handover\") shows up " +"for a comment" msgstr "" -#: ../system/integrations/ldap/index.rst:None +#: ../system/core-workflows/learn-by-example.rst:112 msgid "" -"Screencast showing LDAP integration log entries and a detail view on\n" -"an entry." +"This may only be visible when the owner is changed, therefore it has to be " +"hidden in general" msgstr "" -#: ../system/integrations/ldap/manage.rst:2 -msgid "Manage LDAP-Sources" +#: ../system/core-workflows/learn-by-example.rst:114 +msgid "The input in this handover text field is mandatory" msgstr "" -#: ../system/integrations/ldap/manage.rst:6 +#: ../system/core-workflows/learn-by-example.rst:115 msgid "" -"Please keep in mind all current limitations for the LDAP synchronization. " -"This will help to understand scopes of the following operations better." +"After submitting changes, the value of the handover field must be added as " +"an note to the ticket (via trigger)" msgstr "" -#: ../system/integrations/ldap/manage.rst:65 -msgid "Add new source" -msgstr "" - -#: ../system/integrations/ldap/manage.rst:10 -msgid "" -"Using the *New Source* button allows you to add new LDAP sources to your " -"installation. You're not limited in the number of sources, however, keep in " -"mind that many sources will also take more time to synchronize." +#: ../system/core-workflows/learn-by-example.rst:121 +msgid "Hiding handover field" msgstr "" -#: ../system/integrations/ldap/manage.rst:14 -msgid "" -"You can choose between different encryption types, namely *SSL* and " -"*STARTTLS* or none of them (\"*No SSL*\"). If you choose *SSL* or " -"*STARTTLS*, Zammad will display an additional *SSL verification* option that " -"allows you to disable the verification, e.g. for self-signed SSL " -"certificates. You can also tell Zammad to use a different port by appending " -"``:`` to your hostname/IP." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Hiding the handover field in core workflows" msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "" -"Screenshot of configuring a new LDAP source with SSL encryption and SSL " -"verification" +#: ../system/core-workflows/learn-by-example.rst:126 +msgid "Showing handover field and setting it to mandatory" msgstr "" -#: ../system/integrations/ldap/manage.rst:26 -msgid "" -"New Source with SSL transport security enabled and certificate verification" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Showing the handover field and set it as mandatory" msgstr "" -#: ../system/integrations/ldap/manage.rst:30 -msgid "" -"Using an user filter can be a good idea if you only require a small subset " -"of your LDAP users in Zammad." +#: ../system/core-workflows/learn-by-example.rst:131 +msgid "Trigger writing handover input to a new article" msgstr "" -#: ../system/integrations/ldap/manage.rst:42 -msgid "This especially affects inactive users" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Write handover content to a new article" msgstr "" -#: ../system/integrations/ldap/manage.rst:34 +#: ../system/core-workflows/learn-by-example.rst:133 msgid "" -"As every LDAP behaves differently on which attributes and how they are set, " -"Zammad doesn't care about any flags." +"As a result, the ticket includes an article of the type note which includes " +"the predefined text and the handover comment." msgstr "" -#: ../system/integrations/ldap/manage.rst:37 -msgid "" -"Users that no longer are returned by your LDAP source will automatically be " -"set to inactive. Zammad assumes that the user was deactivated." +#: ../system/core-workflows/limitations.rst:6 +msgid "Core Workflows do not replace Triggers" msgstr "" -#: ../system/integrations/ldap/manage.rst:41 +#: ../system/core-workflows/limitations.rst:5 msgid "" -"Users will never be removed automatically! If you want to remove obsolete " -"users, use :doc:`/system/data-privacy`." +"Workflows manipulate the behavior of fields. However, they do not set values " +"in fields because of actions." msgstr "" -#: ../system/integrations/ldap/manage.rst:46 -msgid "Active Directory admins" +#: ../system/core-workflows/limitations.rst:16 +msgid "API calls are only partly affected" msgstr "" -#: ../system/integrations/ldap/manage.rst:45 +#: ../system/core-workflows/limitations.rst:9 msgid "" -"Active Directories are quite specific on how to filter for active users only " -"- please see the `Microsoft documentation `_ for more " -"information." +"Some options affect UI only and thus do not restrict responses and calls." msgstr "" -#: ../system/integrations/ldap/manage.rst:51 -msgid "" -"*Do not* manually write pathes of either LDAP attributes or groups. If " -"Zammad does not display them, it either cannot find them or you have a lot " -"of users that don't have the attributes populated." +#: ../system/core-workflows/limitations.rst:11 +msgid "This affects the following actions:" msgstr "" -#: ../system/integrations/ldap/manage.rst:55 -msgid "" -"Zammad will always only return attributes that are filled - this reduces the " -"returned list of attributes greatly." +#: ../system/core-workflows/limitations.rst:13 +msgid "select" msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing how to add a new LDAP source" +#: ../system/core-workflows/limitations.rst:14 +msgid "auto select" msgstr "" -#: ../system/integrations/ldap/manage.rst:63 -msgid "" -"If your LDAP system doesn't allow anonymous bind, Zammad detects it and " -"provides you an editable \"Base DN\" *text* field instead of a prefilled " -"*select* field." +#: ../system/core-workflows/limitations.rst:15 +msgid "show" msgstr "" -#: ../system/integrations/ldap/manage.rst:81 -msgid "Review or edit existing source" +#: ../system/core-workflows/limitations.rst:16 +msgid "hide" msgstr "" -#: ../system/integrations/ldap/manage.rst:68 -msgid "" -"Clicking on a LDAP source will provide a configuration and mapping overview." +#: ../system/core-workflows/limitations.rst:25 +msgid "Some fields stay unavailable to customers" msgstr "" -#: ../system/integrations/ldap/manage.rst:70 +#: ../system/core-workflows/limitations.rst:19 msgid "" -"If needed you can then use the *Change* button to update either the name, " -"active state or the whole configuration. If you're changing the whole " -"configuration, the dialogue will be identical to the source creation." +"For technical and security reasons, some default fields (the pale ones you " +"can't edit) stay unavailable for display and usage on customer permissions." msgstr "" -#: ../system/integrations/ldap/manage.rst:76 +#: ../system/core-workflows/limitations.rst:23 msgid "" -"Did your LDAP server change? Different LDAP servers have different " -"structures and default attributes. This causes the LDAP synchronization to " -"likely fail. Consider removing the affected source and re-add it." -msgstr "" - -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing the update of the source name." +"If you require your customers to change e.g. priorities, please consider " +"using workarounds via :doc:`/system/objects` and :doc:`/manage/trigger`." msgstr "" -#: ../system/integrations/ldap/manage.rst:89 -msgid "Re-arrange LDAP source's order" +#: ../system/core-workflows/limitations.rst:29 +msgid "Ticket title changes not supported in edit mask" msgstr "" -#: ../system/integrations/ldap/manage.rst:84 +#: ../system/core-workflows/limitations.rst:28 msgid "" -"You can change the synchronization order for each source at any time. Zammad " -"will synchronize the sources from top to bottom." +"It is currently not possible to perform changes of the ticket title in the " +"edit mask (e.g. renaming, set to read-only)." msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "" -"Screencasting showing how to change the source order by using\n" -"drag and drop." +#: ../system/core-workflows/limitations.rst:37 +msgid "What is out of scope of Core Workflows?" msgstr "" -#: ../system/integrations/ldap/manage.rst:101 -msgid "Remove a source" +#: ../system/core-workflows/limitations.rst:32 +msgid "" +"There are some things that would count as workflow but are either done via :" +"doc:`/manage/trigger` or :doc:`/manage/scheduler`." msgstr "" -#: ../system/integrations/ldap/manage.rst:92 -msgid "" -"If you no longer need the a LDAP source or simply want to start over, you " -"can remove them at any time. This will not remove synchronized users, data " -"synchronized or permissions." +#: ../system/core-workflows/limitations.rst:35 +msgid "Such as (but not limited to):" msgstr "" -#: ../system/integrations/ldap/manage.rst:98 -msgid "" -"Not sure if you'd need the source later on? Set the source to inactive " -"instead of removing it - see *Review or edit existing source* for more." +#: ../system/core-workflows/limitations.rst:37 +msgid "up- or downgrade permissions of users" msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing how to remove LDAP sources." +#: ../system/core-workflows/limitations.rst:38 +msgid "affecting article creation or listing" msgstr "" -#: ../system/integrations/pgp/index.rst:2 -msgid "PGP" +#: ../system/data-privacy.rst:2 +msgid "Data Privacy" msgstr "" -#: ../system/integrations/pgp/index.rst:7 +#: ../system/data-privacy.rst:4 msgid "" -"Pretty Good Privacy (PGP) is another method for secure email communication. " -"With PGP, you can exchange **signed** and **encrypted** messages with others." +"For compliance with GDPR and other data privacy laws, you may wish to " +"**permanently delete users from the system**, along with **all of their " +"associated tickets**." msgstr "" -#: ../system/integrations/pgp/index.rst:13 -#: ../system/integrations/smime/index.rst:17 -msgid "Signing" +#: ../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 `!" msgstr "" -#: ../system/integrations/pgp/index.rst:11 -msgid "is a proof that a message hasn't been manipulated on its way." +#: ../system/data-privacy.rst:12 +msgid "" +"Access to this panel requires ``admin.data_privacy`` permissions (introduced " +"in Zammad 3.5)." msgstr "" -#: ../system/integrations/pgp/index.rst:13 +#: ../system/data-privacy.rst:15 msgid "" -"In other words, it guarantees message **integrity** and **authenticity**." +"On older systems that have not been updated yet, customers can also be :docs:" +"`deleted via the Zammad console `." msgstr "" -#: ../system/integrations/pgp/index.rst:19 -#: ../system/integrations/smime/index.rst:22 -msgid "Encryption" +#: ../system/data-privacy.rst:22 +msgid "User deletion dialog in the Data Privacy panel" msgstr "" -#: ../system/integrations/pgp/index.rst:16 -#: ../system/integrations/smime/index.rst:20 +#: ../system/data-privacy.rst:22 msgid "" -"scrambles a message so that it can only be unscrambled by the intended " -"recipient." +"The user deletion dialog lists some of the tickets that will be removed from " +"the system along with the user." msgstr "" -#: ../system/integrations/pgp/index.rst:19 -msgid "" -"In other words, it guarantees message **privacy** and **data security**." +#: ../system/data-privacy.rst:27 +msgid "Deleting Users via GUI" msgstr "" -#: ../system/integrations/pgp/index.rst:25 -msgid "Screenshot of ticket creation with encrypt and sign buttons" +#: ../system/data-privacy.rst:29 +msgid "🔥 **All deletions are FINAL!**" msgstr "" -#: ../system/integrations/pgp/index.rst:25 +#: ../system/data-privacy.rst:31 +msgid "Once you click “Delete”, the action cannot be canceled or undone." +msgstr "" + +#: ../system/data-privacy.rst:33 msgid "" -"Once PGP has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " -"appear in the ticket composer." +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:28 -msgid "**Sign button not visible?**" +#: ../system/data-privacy.rst:36 +msgid "**The following records cannot be deleted:**" msgstr "" -#: ../system/integrations/pgp/index.rst:30 -msgid "" -"Please note that the signing of emails is based on the outgoing email " -"account. That means you have to choose a group with a sender email account, " -"which has a private key assigned." +#: ../system/data-privacy.rst:38 +msgid "your own account" msgstr "" -#: ../system/integrations/pgp/index.rst:35 -msgid "Handling of Keys" +#: ../system/data-privacy.rst:39 +msgid "the system's last remaining administrator account" msgstr "" -#: ../system/integrations/pgp/index.rst:36 -msgid "" -"To use the PGP function, you have to enable the integration (PGP) by " -"switching the toggle to *enabled*." +#: ../system/data-privacy.rst:42 +msgid "Step 1: Find a User / Confirm Deletion" msgstr "" -#: ../system/integrations/pgp/index.rst:39 -msgid "" -"You can add keys by clicking the *add key* button. The keys can be imported " -"from a file or you can paste the content of the key in the text box." +#: ../system/data-privacy.rst:44 +msgid "There are three ways to access the user deletion dialog:" msgstr "" -#: ../system/integrations/pgp/index.rst:42 -msgid "**Which keys do I have to import?**" +#: ../system/data-privacy.rst:51 +msgid "**from the user's profile**" msgstr "" -#: ../system/integrations/pgp/index.rst:44 -msgid "" -"For **signing** *outgoing* emails, you have to import the private key of " -"your Zammad email account." +#: ../system/data-privacy.rst:0 +msgid "Accessing the user deletion dialog in a user profile" msgstr "" -#: ../system/integrations/pgp/index.rst:47 -msgid "" -"For **encrypting** *outgoing* emails, you have to import the public key of " -"the customer's email account." +#: ../system/data-privacy.rst:51 +msgid "Click **Action > Delete**." msgstr "" -#: ../system/integrations/pgp/index.rst:50 -msgid "" -"For **verifying the signature** of signed *incoming* emails, you have to " -"import the public key of the customer." +#: ../system/data-privacy.rst:58 +msgid "**in the “Manage > Users” Admin Panel**" msgstr "" -#: ../system/integrations/pgp/index.rst:53 -msgid "" -"For **decrypting** of encrypted *incoming* emails, you have to import the " -"private key of your Zammad email account." +#: ../system/data-privacy.rst:0 +msgid "Accessing the user deletion dialog under “Users” in the Admin Panel" msgstr "" -#: ../system/integrations/pgp/index.rst:57 -msgid "Import Keys From a File" +#: ../system/data-privacy.rst:58 +msgid "Use the **⋮ Actions** menu for the target user." msgstr "" -#: ../system/integrations/pgp/index.rst:58 -msgid "You can import keys from a file in the section **Upload key**:" +#: ../system/data-privacy.rst:66 ../system/data-privacy.rst:104 +msgid "**in the “System > Data Privacy” Admin Panel**" msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of adding a key via file" +#: ../system/data-privacy.rst:0 +msgid "" +"Accessing the user deletion dialog under “Data Privacy” in the Admin Panel" msgstr "" -#: ../system/integrations/pgp/index.rst:64 +#: ../system/data-privacy.rst:65 msgid "" -"**Supported file formats:** ASCII-armor as well as binary GPG format " -"(basically any GPG supported key format) is supported here." +"Use the **New Deletion Task** button. Search for users by name or email " +"address." msgstr "" -#: ../system/integrations/pgp/index.rst:68 -msgid "Import Keys by Pasting the Content" +#: ../system/data-privacy.rst:79 +msgid "**Delete organizations**" msgstr "" -#: ../system/integrations/pgp/index.rst:69 -msgid "You can also paste the key's content in the section **paste key**:" +#: ../system/data-privacy.rst:69 +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:" msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of adding a key via pasting" +#: ../system/data-privacy.rst:0 +msgid "Deleting an organization via the user deletion dialog" msgstr "" -#: ../system/integrations/pgp/index.rst:75 +#: ../system/data-privacy.rst:78 msgid "" -"**Supported format:** Please note that only ASCII-armor is supported here." +"If this option does not appear, make sure there are no pending deletion " +"tasks for other customers from this organization." msgstr "" -#: ../system/integrations/pgp/index.rst:78 -msgid "Deleting Keys" +#: ../system/data-privacy.rst:82 +msgid "Step 2: Monitor Deletion Job Status" msgstr "" -#: ../system/integrations/pgp/index.rst:79 +#: ../system/data-privacy.rst:84 msgid "" -"If you want to delete a specific key, you can do it by clicking on the menu " -"in the *actions* column and select **delete**:" +"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:" msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of deleting a key" +#: ../system/data-privacy.rst:98 +msgid "**in the Activity Stream**" msgstr "" -#: ../system/integrations/pgp/index.rst:88 -msgid "Downloading Keys" +#: ../system/data-privacy.rst:0 +msgid "Activity Stream showing data privacy tasks" msgstr "" -#: ../system/integrations/pgp/index.rst:89 +#: ../system/data-privacy.rst:94 msgid "" -"If you want to download your keys, you can do this as well via corresponding " -"action buttons. Depending on the key, you can choose wether you want to " -"download the private or the public key." +"For each deleted user, the Activity Stream will be updated twice—once when " +"the task is created, and once when it's complete." msgstr "" -#: ../system/integrations/pgp/index.rst:95 -#: ../system/integrations/smime/manage-certificates.rst:76 -msgid "Default Behavior" +#: ../system/data-privacy.rst:97 +msgid "" +"These notifications are only visible to users with ``admin.data_privacy`` " +"permissions." msgstr "" -#: ../system/integrations/pgp/index.rst:96 +#: ../system/data-privacy.rst:0 msgid "" -"Here you can adjust on per group basis, if *sign* and *encryption* is on or " -"off by default. Please be aware, that agents can always override the setting " -"for each individual article." +"The task list within Data Privacy shows removals being in progress and " +"completed." msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Adjusting default behavior on per group basis" +#: ../system/data-privacy.rst:107 +msgid "Frequently Asked Questions" msgstr "" -#: ../system/integrations/pgp/index.rst:107 -msgid "" -"Here you can see the last actions regarding signing and encryption and if " -"they were successful." +#: ../system/data-privacy.rst:121 +msgid "What happens if I receive an email from a deleted customer?" msgstr "" -#: ../system/integrations/pgp/index.rst:117 -msgid "**Sign button is not visible, but keys are imported.**" +#: ../system/data-privacy.rst:110 +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/integrations/pgp/index.rst:115 -msgid "Did you choose a group in the ticket?" +#: ../system/data-privacy.rst:115 +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**." msgstr "" -#: ../system/integrations/pgp/index.rst:116 -msgid "" -"Did you import a private key for the email adress, which is used for " -"outgoing emails in the group?" +#: ../system/data-privacy.rst:130 +msgid "What about user information stored in internal notes or other messages?" msgstr "" -#: ../system/integrations/pgp/index.rst:122 -msgid "**How to obtain keys?**" +#: ../system/data-privacy.rst:124 +msgid "" +"The deletion process removes **user accounts and associated tickets only**." msgstr "" -#: ../system/integrations/pgp/index.rst:120 +#: ../system/data-privacy.rst:126 msgid "" -"You can create them yourself! There are some good tutorials on the web on " -"how to create them. Providing keys to Zammad is a prerequisite to use the " -"PGP feature." +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:127 -msgid "**It says a passphrase is needed, but I haven't got one.**" +#: ../system/data-privacy.rst:137 +msgid "I deleted an user and can still see a message they sent!" msgstr "" -#: ../system/integrations/pgp/index.rst:125 +#: ../system/data-privacy.rst:133 msgid "" -"If the key is secured with a passphrase, you have to provide it for the " -"import in Zammad. It is possible that keys may have an empty passphrase. " -"However, this is *not* recommended." +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:132 -msgid "**How do my customers get my new key?**" +#: ../system/data-privacy.rst:141 +msgid "I removed a customer, now my reporting is off!" msgstr "" -#: ../system/integrations/pgp/index.rst:130 +#: ../system/data-privacy.rst:140 msgid "" -"You have to provide your **public** key in advance. Your customer also has " -"to configure PGP in their email workflow and import your public key. The " -"other way round, you have to get the public key of your customer and have to " -"import it to Zammad." +"When removing users and their tickets, all references are removed. This also " +"affects e.g. Reporting - these information are lost." msgstr "" -#: ../system/integrations/slack.rst:2 -msgid "Slack" +#: ../system/data-privacy.rst:145 +msgid "How long does Zammad store created tasks?" msgstr "" -#: ../system/integrations/slack.rst:4 -msgid "**⚠️ Deprecation warning ⚠️**" +#: ../system/data-privacy.rst:144 +msgid "" +"Please see the on-premise data section of the :docs:`data privacy ` chapter." msgstr "" -#: ../system/integrations/slack.rst:6 -msgid "" -"Zammad 7 will no longer support this dedicated Slack integration. It is " -"recommended to switch to :doc:`pre-defined webhooks ` instead. Existing Slack integrations should " -"be migrated manually before this feature is dropped." +#: ../system/data-privacy.rst:150 +msgid "What about re-assigned tickets? I want to delete them, too." msgstr "" -#: ../system/integrations/slack.rst:14 +#: ../system/data-privacy.rst:148 msgid "" -"In order to use this feature, please add a new Slack app to your Workspace. " -"The App you need is called ``Incoming WebHooks`` ." +"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." msgstr "" -#: ../system/integrations/slack.rst:18 -msgid "Why Do I Need This Feature?" +#: ../system/data-privacy.rst:154 +msgid "Why are there so many deletion task entries, I didn't create them!" msgstr "" -#: ../system/integrations/slack.rst:20 +#: ../system/data-privacy.rst:153 msgid "" -"If you're already using Slack for your team communication, you'll love this " -"feature! Our Slack integration can push ticket notifications about the last " -"ticket article based on the following events:" +"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." msgstr "" -#: ../system/integrations/slack.rst:24 -msgid "on Ticket creation" +#: ../system/integrations/checkmk/admin-panel-reference.rst:2 +msgid "Admin Panel Reference" msgstr "" -#: ../system/integrations/slack.rst:25 -msgid "on Ticket updates" +#: ../system/integrations/checkmk/admin-panel-reference.rst:None +msgid "Screenshot of Checkmk settings overview" msgstr "" -#: ../system/integrations/slack.rst:26 -msgid "on reached reminders" +#: ../system/integrations/checkmk/admin-panel-reference.rst:12 +msgid "" +"Which :doc:`group ` should Checkmk tickets be assigned " +"to as a default (*i.e.,* when none is specified)?" msgstr "" -#: ../system/integrations/slack.rst:27 -msgid "a Ticket has escalated" +#: ../system/integrations/checkmk/admin-panel-reference.rst:15 +msgid "(Applies to :ref:`API alerts ` only.)" msgstr "" -#: ../system/integrations/slack.rst:28 -msgid "a Ticket is going to escalate" +#: ../system/integrations/checkmk/admin-panel-reference.rst:21 +msgid "Auto close" msgstr "" -#: ../system/integrations/slack.rst:30 +#: ../system/integrations/checkmk/admin-panel-reference.rst:18 msgid "" -"Zammad will provide the Ticket title, a direct link to the Ticket, the event " -"type (creation, updated, escalation), the customer, time and the last " -"article that has triggered the notification." +"Should Zammad automatically close tickets if a service has recovered on its " +"own?" msgstr "" -#: ../system/integrations/slack.rst:34 -msgid "" -"This will give you further options, as you can see e.g. escalating tickets " -"that are assigned to an agent that's e.g. absent. You can interact faster, " -"as you might see problems earlier (or even before the problem gets one)." +#: ../system/integrations/checkmk/admin-panel-reference.rst:21 +msgid "(Agents will receive notifications for such closures as appropriate.)" msgstr "" -#: ../system/integrations/slack.rst:38 -msgid "" -"If needed and wanted, you can even discuss directly about the topic before " -"sending an answer to the customer. Another possible use case would be a " -"agent monitoring new agents and their answers to tickets." +#: ../system/integrations/checkmk/admin-panel-reference.rst:30 +msgid "Auto-close state" msgstr "" -#: ../system/integrations/slack.rst:44 -#, fuzzy -msgid "Configure the Integration" -msgstr "Konfiguracija chat widgeta" - -#: ../system/integrations/slack.rst:46 -msgid "" -"First of all, please go to your slack workspace - go to administration => " -"Manage Apps. If you don't have an app yet, you can simply add a new one - " -"just search for ``Incoming WebHooks`` and customize the app to your needs." +#: ../system/integrations/checkmk/admin-panel-reference.rst:24 +msgid "What ticket state should be applied when “auto-closing” a ticket?" msgstr "" -#: ../system/integrations/slack.rst:50 +#: ../system/integrations/checkmk/admin-panel-reference.rst:26 msgid "" -"Choose (or create) the channel Zammad should post it's information to and " -"press on \"Add Incoming WebHooks integration\". If you're ready, copy the " -"provided WebHook URL and go to your Zammad installation." +"You can choose from the seven built-in ticket states. If these states aren't " +"enough for you, you can :ref:`define a new ticket state ` for this purpose as well. This can be useful for tracking " +"tickets with :doc:`reports `, for example." msgstr "" -#: ../system/integrations/slack.rst:56 -msgid "" -"You need administrative rights on the Slack Workspace. The link to the app " -"directory is normally ``https://[workspace-name].slack.com/apps`` ." +#: ../system/integrations/checkmk/admin-panel-reference.rst:35 +#: ../system/integrations/cti/includes/recent-logs.include.rst:2 +#: ../system/integrations/ldap/index.rst:74 +#: ../system/integrations/pgp/index.rst:106 +msgid "Recent Logs" msgstr "" -#: ../system/integrations/slack.rst:63 -msgid "" -"To configure the slack integration, log in to Zammad and go to Integrations " -"(System) => Slack in the admin panel." +#: ../system/integrations/checkmk/admin-panel-reference.rst:None +msgid "Screenshot of Checkmk \"Recent Logs\" section" msgstr "" -#: ../system/integrations/slack.rst:66 +#: ../system/integrations/checkmk/admin-panel-reference.rst:41 msgid "" -"Here you can choose on what evens Zammad should post information about a " -"ticket to your Slack channel. Next you need to device what groups shall be " -"affected by this, as anybody with access to that specific Slack channel can " -"read at least parts of the ticket this might be a privacy issue, if you " -"select the wrong groups. The username is simply the name that Zammad uses as " -"display name inside the Slack chat. The channel defines the Slack channel " -"the information is being posted in. As last option, you can set a custom " -"icon for posting to slack." +"If you're having trouble getting Zammad and Checkmk to play nicely together, " +"this section can help you troubleshoot." msgstr "" -#: ../system/integrations/slack.rst:74 +#: ../system/integrations/checkmk/admin-panel-reference.rst:44 msgid "" -"When you're ready, just hit \"Submit\" and enable the integration. Zammad " -"will now post new ticket information based on the trigger you chose. Below " -"the options you have the recent log that shows the latest requests to Slack " -"for debugging if needed." +"It contains a record of the fifty most recent transactions that Zammad knows " +"about, including each one's request/response details and return status." msgstr "" -#: ../system/integrations/slack.rst:81 -msgid "" -"If you leave the Icon URL empty, Zammad will use the Zammad logo instead. " -"The icon should be a square PNG file." +#: ../system/integrations/checkmk/api-reference.rst:2 +msgid "API Reference" msgstr "" -#: ../system/integrations/slack.rst:90 +#: ../system/integrations/checkmk/api-reference.rst:4 msgid "" -"The following figure shows how it will look if you choose to receive updates " -"on created and updated tickets. On every post Zammad sends to the Slack " -"channel, you can create new threads to discuss about the new article." +"For most users, :ref:`the sample scripts from the Setup Guide ` will do the job just fine. But if you want more fine-grained control" +"—for instance, to create high- and low-priority tickets for different types " +"of system events—then you'll have to customize the data those scripts send " +"to Zammad." msgstr "" -#: ../system/integrations/slack.rst:96 +#: ../system/integrations/checkmk/api-reference.rst:15 msgid "" -"If you just want to keep track of soon escalating or already escalated " -"tickets, it will look the the following figure. Zammad changes the color in " -"front of the post so you can easily see the state of the ticket." +"This custom script will automatically set all tickets it creates to **high " +"priority** and **assign them to charlie@chrispresso.com**." msgstr "" -#: ../system/integrations/slack.rst:102 -msgid "" -"If you change the state, Zammad will also put information on what state the " -"ticket gets and (if pending state) the date until it pends. You'll also " -"recognize the color codes in front of posts on slack, as they are exact the " -"same the ticket state colors you'll see in Zammad!" +#: ../system/integrations/checkmk/api-reference.rst:32 +msgid "How Does it Work?" msgstr "" -#: ../system/integrations/smime/index.rst:2 -msgid "S/MIME" +#: ../system/integrations/checkmk/api-reference.rst:34 +msgid "" +"There are two kinds of data you can pass to the API, both in the form of key-" +"value pairs:" msgstr "" -#: ../system/integrations/smime/index.rst:11 -msgid "" -"S/MIME is the most widely-supported method for secure email communication. " -"With S/MIME, you can exchange **signed** and **encrypted** messages with " -"others." +#: ../system/integrations/checkmk/api-reference.rst:44 +msgid "Checkmk parameters" msgstr "" -#: ../system/integrations/smime/index.rst:15 +#: ../system/integrations/checkmk/api-reference.rst:38 msgid "" -"is proof that a message hasn't been tampered with or sent by an impersonator." +"are required, and make up the **contents** of the resulting tickets/" +"articles. They also determine whether an event creates a new ticket or " +"updates/closes an existing one." msgstr "" -#: ../system/integrations/smime/index.rst:17 +#: ../system/integrations/checkmk/api-reference.rst:42 msgid "" -"In other words, it guarantees a message's **integrity** and **authenticity**." +"These are the only values used in the sample scripts. **Use them as-is**; " +"technically, they can be customized, but it's hard to imagine a good reason " +"for it." msgstr "" -#: ../system/integrations/smime/index.rst:22 -msgid "In other words, it guarantees **privacy** and **data security**." +#: ../system/integrations/checkmk/api-reference.rst:52 +msgid "Ticket attributes" msgstr "" -#: ../system/integrations/smime/index.rst:28 -msgid "Screencast demo of S/MIME features for both new tickets and replies" +#: ../system/integrations/checkmk/api-reference.rst:47 +msgid "" +"are optional, and can be used to **adjust settings** on newly created " +"tickets (*e.g.,* set the owner, group, priority, or state)." msgstr "" -#: ../system/integrations/smime/index.rst:28 +#: ../system/integrations/checkmk/api-reference.rst:50 msgid "" -"Once S/MIME has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " -"appear in the ticket composer." +"If you want to customize your Checkmk alert script, do it with these. Simply " +"add an extra “form” option for each one (``-F \"key=value\"``) to your " +"script's ``curl`` command line, as in the example above." msgstr "" -#: ../system/integrations/smime/index.rst:32 -msgid ":doc:`🔪 Prerequisites `" +#: ../system/integrations/checkmk/api-reference.rst:54 +msgid "💡 **It's just an API endpoint!**" msgstr "" -#: ../system/integrations/smime/index.rst:31 +#: ../system/integrations/checkmk/api-reference.rst:56 msgid "" -"New to S/MIME? This section helps you to find certificate providers and " -"points out Limitations." +"When using Checkmk integration, messages need to be formatted in a certain " +"way, but that *doesn't mean the messages actually have to come from Checkmk*." msgstr "" -#: ../system/integrations/smime/index.rst:35 -msgid ":doc:`📝 Manage Certificates `" +#: ../system/integrations/checkmk/api-reference.rst:59 +msgid "" +"If you use another monitoring tool that's not officially supported by " +"Zammad, there's probably a way to make it work with your Checkmk callback " +"URL." msgstr "" -#: ../system/integrations/smime/index.rst:35 -msgid "Add and download certificates; configure group default behaviors." +#: ../system/integrations/checkmk/api-reference.rst:63 +msgid "Checkmk Parameters" msgstr "" -#: ../system/integrations/smime/index.rst:38 -msgid ":doc:`😦 Troubleshooting `" +#: ../system/integrations/checkmk/api-reference.rst:65 +msgid "" +"When a notification is received, Zammad creates a new article containing the " +"details of the event that triggered it:" msgstr "" -#: ../system/integrations/smime/index.rst:38 -msgid "Took a wrong turn? About recent logs and common issues." +#: ../system/integrations/checkmk/api-reference.rst:None +msgid "Checkmk article body" msgstr "" -#: ../system/integrations/smime/index.rst:43 +#: ../system/integrations/checkmk/api-reference.rst:72 msgid "" -"For more details on how S/MIME integration works on the agent side, see the :" -"user-docs:`user docs `." -msgstr "" - -#: ../system/integrations/smime/manage-certificates.rst:2 -msgid "Manage Certificates" +"These details come from the fields listed below, which correspond to " +"parameters provided by Checkmk (``$NOTIFY_*``)." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:4 -msgid "" -"S/MIME is **disabled by default**. Enable it to start adding certificates." +#: ../system/integrations/checkmk/api-reference.rst:75 +msgid "**Required fields are marked with an asterisk (\\*).**" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:10 -msgid "Dialogue to add new certificates or private keys" +#: ../system/integrations/checkmk/api-reference.rst:79 +msgid "event_id\\*" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:10 +#: ../system/integrations/checkmk/api-reference.rst:78 msgid "" -"Manage certificates in the Admin Panel under **System > Integrations > S/" -"MIME**. Certificates may be pasted in as plain text or uploaded from a file." +"A unique ID for the system event. (``$NOTIFY_SERVICEPROBLEMID`` / " +"``$NOTIFY_HOSTPROBLEMID``)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:14 -msgid "Add Certificate Data" +#: ../system/integrations/checkmk/api-reference.rst:86 +msgid "host\\*" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:36 -msgid "Add Certificate" +#: ../system/integrations/checkmk/api-reference.rst:82 +msgid "" +"The hostname of the system that the event originated from. " +"(``$NOTIFY_HOSTNAME``)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:17 +#: ../system/integrations/checkmk/api-reference.rst:85 msgid "" -"Import public-key certificates for both your own organization and your " -"contacts." +"Used to determine if a new event belongs to an existing ticket. Also used in " +"the subject line of the resulting article (“ is ”)." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:19 +#: ../system/integrations/checkmk/api-reference.rst:96 +msgid "service" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:89 msgid "" -"You can also add a bunch of certificates in one go by providing a single " -"file with all relevant certificates." +"The name of the service that the event originated from. " +"(``$NOTIFY_SERVICEDESC``)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:22 -msgid "🕵️ **ALWAYS verify certificates in-person or over the phone!**" +#: ../system/integrations/checkmk/api-reference.rst:92 +msgid "Used to determine if a new event belongs to an existing ticket." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:24 -msgid "" -"The whole point of signatures is to alert you when someone is trying to " -"pretend to be someone they're not. Never accept a certificate from someone " -"online without verifying it first." +#: ../system/integrations/checkmk/api-reference.rst:94 +#: ../system/integrations/checkmk/api-reference.rst:110 +msgid "Displayed as ``-`` when omitted." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:28 -msgid "📇 **What about trusted certificate authorities?**" +#: ../system/integrations/checkmk/api-reference.rst:104 +msgid "state\\*" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:30 +#: ../system/integrations/checkmk/api-reference.rst:99 msgid "" -"In some cases (e.g. when dealing with large enterprises), you may be given a " -"certificate for an entire CA, rather than a single contact. Add it here to " -"trust *all* certificates issued by that CA." +"The current state of the service or host in question. " +"(``$NOTIFY_SERVICESTATE`` / ``$NOTIFY_HOSTSTATE``)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:35 +#: ../system/integrations/checkmk/api-reference.rst:102 msgid "" -"Commercial CAs can usually be verified online. Zammad does not include a " -"list of built-in, trusted CAs." +"Used to detect when a ticket should be auto-closed (*i.e.,* on ``OK``/" +"``UP``). Also used in the subject line of the resulting article (“ is " +"”)." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:57 -msgid "Add Private Key" +#: ../system/integrations/checkmk/api-reference.rst:110 +msgid "text" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:39 +#: ../system/integrations/checkmk/api-reference.rst:107 msgid "" -"Once you've added a public-key certificate, you can import its matching " -"private key." +"The output of the process that triggered the event. " +"(``$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:42 +#: ../system/integrations/checkmk/api-reference.rst:121 msgid "" -"Private keys are for **your own organization only**; never ask your contacts " -"for their private keys." +"The Object Manager attribute panel displays built-in and custom\n" +"attribute names." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:0 -msgid "" -"S/MIME integration showing configured certificates and possible issues with " -"Logging" +#: ../system/integrations/checkmk/api-reference.rst:121 +msgid "Find a complete list of ticket attributes in the Object Manager." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:50 +#: ../system/integrations/checkmk/api-reference.rst:123 msgid "" -"A note is displayed on certificates with a matching private key (see line 2)." -msgstr "" - -#: ../system/integrations/smime/manage-certificates.rst:52 -msgid "📤 **Certificates and private keys must be uploaded separately.**" +"Ticket attributes are entirely optional, and can be used to customize the " +"tickets that Checkmk creates. (Note that these attributes will be ignored if " +"a new event belongs to an existing ticket.)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:54 +#: ../system/integrations/checkmk/api-reference.rst:128 msgid "" -"If your certificate and private key are bundled together in the same file or " -"PEM block, import it twice (once using each button)." +"Why would you want to do this? Maybe you have only one IT guy, and all " +"system monitoring issues should be automatically assigned to him. Or, maybe " +"you're creating multiple notification rules so that database outages take " +"higher priority than disk space warnings." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:57 -msgid "Please note that bulk imports of private keys are not possible." +#: ../system/integrations/checkmk/api-reference.rst:135 +msgid "In most cases, you'll probably want to set one of the following:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:60 -msgid "Download Certificate Data" -msgstr "" +#: ../system/integrations/checkmk/api-reference.rst:137 +msgid "group" +msgstr "grupa" -#: ../system/integrations/smime/manage-certificates.rst:62 -msgid "" -"You can download the earlier provided certificates and private keys at any " -"time from your Zammad instance." -msgstr "" +#: ../system/integrations/checkmk/api-reference.rst:139 +msgid "state" +msgstr "status" -#: ../system/integrations/smime/manage-certificates.rst:65 +#: ../system/integrations/checkmk/api-reference.rst:140 +msgid "priority" +msgstr "prioritet" + +#: ../system/integrations/checkmk/api-reference.rst:142 msgid "" -"Please note that passphrase-protected private keys stay protected and when " -"you download them, you have to know the passphrase to use them after " -"downloading." +"but in practice, you can set almost any attribute, including :doc:`custom " +"ones you created through the Object Manager `." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:73 -msgid "Dialogue to download certificates or private keys" +#: ../system/integrations/checkmk/api-reference.rst:145 +msgid "Please note that the following attributes are **not customizable**:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:73 -msgid "Download stored certificates and their keys" -msgstr "" +#: ../system/integrations/checkmk/api-reference.rst:147 +msgid "title" +msgstr "naslov" -#: ../system/integrations/smime/manage-certificates.rst:78 -msgid "" -"The ticket composer will set all outgoing messages to **signed and " -"encrypted** by default (assuming the required certificates exist)." +#: ../system/integrations/checkmk/api-reference.rst:148 +msgid "id" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:82 -msgid "These defaults can be modified on a per-group basis:" +#: ../system/integrations/checkmk/api-reference.rst:149 +msgid "ticket number" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:None -msgid "Zammad allowing to choose the default behavior on per group basis" +#: ../system/integrations/checkmk/api-reference.rst:151 +msgid "created_by_id" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:89 -msgid "" -"Of course, agents can always manually change these settings on each email " -"they send out." +#: ../system/integrations/checkmk/api-reference.rst:152 +msgid "updated_by_id" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:4 -msgid "A certificate *and* private key for your own organization" +#: ../system/integrations/checkmk/api-reference.rst:155 +msgid "Which Values Can Be Set?" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:6 -msgid "" -"(Use this to ✒️ **sign outgoing messages** and 🔓 **decrypt incoming " -"messages**.)" +#: ../system/integrations/checkmk/api-reference.rst:157 +msgid "😵 **Invalid values → unpredictable behavior**" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:9 +#: ../system/integrations/checkmk/api-reference.rst:159 msgid "" -"Certificates belonging your contacts, or their issuing certificate authority " -"(CA)" +"If you provide a value that Zammad doesn't understand (*e.g.,* ``-F " +"\"priority=high\"``), it's not always clear what will happen. In some cases, " +"a ticket will be created with the default values instead - but in others, it " +"may not be created at all!" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:11 -msgid "" -"(Use these to ✅ **verify incoming message signatures** and 🔒 **encrypt " -"outgoing messages**.)" +#: ../system/integrations/checkmk/api-reference.rst:164 +msgid "So what values does Zammad understand, then? Well, it depends..." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:14 -msgid "🙋 **I'm new to S/MIME. Where can I get a certificate?**" +#: ../system/integrations/checkmk/api-reference.rst:168 +msgid "Use an email address or username:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:16 -msgid "" -"The easiest way to get certificates is to buy an annual subscription through " -"a commercial CA, such as:" +#: ../system/integrations/checkmk/api-reference.rst:190 +msgid "group & priority" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:19 -msgid "" -"`Sectigo (formerly Comodo) `_" +#: ../system/integrations/checkmk/api-reference.rst:175 +msgid "Refer to the dropdown menus in the ticket pane:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:20 -msgid "`Secorio `_" +#: ../system/integrations/checkmk/api-reference.rst:0 +msgid "See possible values for certain attributes in the ticket pane." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:21 -msgid "`GlobalSign `_" +#: ../system/integrations/checkmk/api-reference.rst:187 +msgid "🙅 **Ticket state CANNOT be set this way!**" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:23 -msgid "(Zammad is not affiliated with these CAs in any way.)" +#: ../system/integrations/checkmk/api-reference.rst:189 +msgid "" +"Why? Because ``-F \"state=...\"`` is already used :ref:`as a Checkmk " +"parameter `." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:25 -msgid "" -"You can also generate your own self-signed certificates, but the process is " -"complicated and usually 🙅 **involves extra work for your contacts**." +#: ../system/integrations/checkmk/api-reference.rst:222 +msgid "Everything Else" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:29 +#: ../system/integrations/checkmk/api-reference.rst:193 msgid "" -"Bear in mind that 🤝 **S/MIME only works if the other party is using it, too." -"**" +"To set any other attributes, it helps to know your way around the :docs:" +"`rails console `. Valid values are those that you can " +"set with a string:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:32 -msgid "Certificate and Private Key Checks on Upload" +#: ../system/integrations/checkmk/api-reference.rst:218 +msgid "These values can then be passed directly to the API:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:34 -msgid "" -"The certificate and public key validation is based on the ``X509v3`` " -"extensions." +#: ../system/integrations/checkmk/index.rst:16 +msgid "How does it work?" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:49 -msgid "Uploading a *client certificate*?" +#: ../system/integrations/checkmk/index.rst:2 +msgid "Checkmk" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:41 -msgid "The following attributes are required then:" +#: ../system/integrations/checkmk/index.rst:4 +msgid "" +"`Checkmk `_ is a powerful IT monitoring tool that can " +"send real-time status alerts to Zammad via email or REST API. Set these " +"alerts up in Checkmk, and Zammad will automatically create, update, and " +"close tickets based on the health of your system:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:39 -msgid "Subject Alternative Name (at least one email address has to be present)" +#: ../system/integrations/checkmk/index.rst:14 +msgid "Screenshot of ticket created by Checkmk notifications" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:40 -msgid "Key Usage (``Digital Signature`` and/or ``Key Encipherment``)" +#: ../system/integrations/checkmk/index.rst:14 +msgid "Multiple alerts, same ticket." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:41 -msgid "Public key algorithm (either ``RSA`` or ``EC``)" +#: ../system/integrations/checkmk/setup-guide.rst:2 +msgid "Setup Guide" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:43 +#: ../system/integrations/checkmk/setup-guide.rst:4 msgid "" -"The Extended Key Usage attribute is optional. If the certificate provides " -"the named attribute, than it must contain the value ``E-mail Protection``." +"Whenever the Checkmk integration is enabled, Zammad listens for messages on " +"its API and over email. As long as those messages follow the required " +"format, Zammad will create new tickets (or find and update existing ones) " +"based on the message contents." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:46 +#: ../system/integrations/checkmk/setup-guide.rst:10 msgid "" -"Please note that any usable email adress has to be prefixed with ``email:`` " -"or ``rfc822:``." +"That means that “setting up Checkmk integration” is simply a matter of " +"**adding configuration to your Checkmk site**: telling it when to send these " +"messages and what to say. To do that, you'll need to create a new " +"**notification rule** (see `Checkmk's official docs `_ for help with that)." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:49 -msgid "The named public key algorithms are mandatory for private keys as well." +#: ../system/integrations/checkmk/setup-guide.rst:17 +msgid "" +"As part of this new rule, you'll have to choose a **notification method** " +"(*i.e.,* a script to execute whenever the rule is triggered). This script " +"will be written by you (samples below), and contain the logic for sending " +"API/email messages to Zammad:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:54 -msgid "Uploading a *CA certificate*?" +#: ../system/integrations/checkmk/setup-guide.rst:26 +msgid "Checkmk \"New Rule\" dialog" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:52 +#: ../system/integrations/checkmk/setup-guide.rst:26 msgid "" -"In the case of an uploaded CA certificate, providing the value ``CA:TRUE`` " -"in the attribute *Basic Contstraints*, the previously mentioned attributes " -"are not verified." +"Find your custom scripts in the Checkmk WATO under **Notifications > New " +"Rule > Notification Method**." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:56 +#: ../system/integrations/checkmk/setup-guide.rst:29 msgid "" -"In general, the usage of any expired (``Not After``) or not yet valid (``Not " -"Before``) certificate is denied for outgoing emails." -msgstr "" - -#: ../system/integrations/smime/prerequisites.rst:59 -msgid "Example certificate:" +"Once you're done setting up your new rule, you're all set! New tickets " +"should start coming in and auto-updating any time your rule is triggered." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:85 +#: ../system/integrations/checkmk/setup-guide.rst:33 msgid "" -"Please note that Zammad will distrust senders by default. This means that " -"you're always required to provide certificate data, no matter if for signing " -"or encrypting." +"(If you need help troubleshooting, be sure to check the :ref:`checkmk-recent-" +"logs`.)" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:89 -msgid "This is by design and can't be adjusted." +#: ../system/integrations/checkmk/setup-guide.rst:38 +msgid "API Alerts" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:4 +#: ../system/integrations/checkmk/setup-guide.rst:40 msgid "" -"All of the system's latest S/MIME activity is displayed in the **Recent " -"Logs** section." +"To add these scripts in the Checkmk WATO, copy them into your Checkmk " +"installation directory and make them executable. (Be sure to replace the " +"``zammad.example.com`` callback URL with the one found in your admin panel.)" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:11 -msgid "Sample entries of in- and outgoing S/MIME related emails." +#: ../system/integrations/checkmk/setup-guide.rst:60 +msgid "Service notification" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:11 +#: ../system/integrations/checkmk/setup-guide.rst:46 msgid "" -"Logs report the status and details of all mail, both incoming and outgoing, " -"that used signing/verification or encryption/decryption." +"For updates on the status of the software running on your server (*e.g.,* " +"postgres)." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:14 -msgid "" -"This log does **not** include email sent by :doc:`triggers ` or the :doc:`scheduler `. For those, check your " -"``production.log``." +#: ../system/integrations/checkmk/setup-guide.rst:75 +msgid "Host notification" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:20 -msgid "Common Issues" +#: ../system/integrations/checkmk/setup-guide.rst:63 +msgid "For updates on the status of the server itself." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:30 -msgid "I received a signed/encrypted email before I set up S/MIME integration" +#: ../system/integrations/checkmk/setup-guide.rst:77 +msgid "🤔 **What's with all the env vars?**" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:23 +#: ../system/integrations/checkmk/setup-guide.rst:79 msgid "" -"No problem. Once S/MIME has been enabled and the appropriate certificates " -"have been added, agents will be prompted to retry verification/decryption on " -"matching emails." -msgstr "" - -#: ../system/integrations/smime/troubleshooting.rst:0 -msgid "Screenshot of user prompt to retry decryption" -msgstr "" - -#: ../system/integrations/smime/troubleshooting.rst:38 -msgid "The 🔒 **Encrypt** button is disabled" -msgstr "" - -#: ../system/integrations/smime/troubleshooting.rst:33 -msgid "Have you added the recipient's certificate?" +"Whenever Checkmk runs these scripts, it needs to provide some information " +"about the event that triggered the notification. This information is passed " +"in the form of these ``$NOTIFY_*`` environment variables." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:34 -msgid "Are you sure the recipient's certificate is valid?" +#: ../system/integrations/checkmk/setup-guide.rst:85 +msgid "" +"You can specify additional parameters to pass to the script when you're " +"setting up your notification rule, but the ones you see here are all " +"provided by default." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:35 -msgid "Have you checked your ``production.log`` for more details?" +#: ../system/integrations/checkmk/setup-guide.rst:90 +msgid "Email Alerts" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:37 +#: ../system/integrations/checkmk/setup-guide.rst:94 msgid "" -"If encryption doesn't work in the composer, it won't work in :doc:`triggers " -"` or the :doc:`scheduler ` either!" +"🐞 **There are known bugs** in Zammad's processing of email from Checkmk. " +"This section will be completed once they have been resolved. (Learn more at " +"GitHub issues `#2377 `_ & " +"`#2180 `_.)" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:42 -msgid "The ✅ **Sign** button is disabled" +#: ../system/integrations/checkmk/setup-guide.rst:100 +msgid "In the meantime, we encourage you to set up API alerts instead." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:41 -msgid "" -"Have you added **both the certificate and private key** for your " -"organization?" +#: ../system/integrations/clearbit.rst:2 +msgid "Clearbit" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:42 +#: ../system/integrations/clearbit.rst:4 msgid "" -"Does the email address on the certificate match the email address of the " -"agent/group composing the email?" +"With our Clearbit integration, you can easily enrich the information " +"provided by Zammad. If the customers or agents email address is known to " +"Clearbit, it will share all information it has regarding the user with " +"Zammad. Those information can include the following:" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:45 -msgid "Error: “Fingerprint already taken”" +#: ../system/integrations/clearbit.rst:9 +msgid "Avatar" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:45 -msgid "Are you sure you haven't added this certificate already?" +#: ../system/integrations/clearbit.rst:10 +msgid "Address information" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:48 -msgid "Error: “❌ invalid byte sequence in UTF-8”" +#: ../system/integrations/clearbit.rst:11 +msgid "Website information" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:48 -msgid "Please ensure to provide PEM formatted certificate and keys." +#: ../system/integrations/clearbit.rst:12 +msgid "A BIO (as Note by default)" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:49 -msgid "Did you check if the provided file is a valid certificate or key?" +#: ../system/integrations/clearbit.rst:14 +msgid "" +"If needed, you can add further custom objects and add mappings to them, so " +"the Clearbit information can be filled within the database. In general you " +"can get any information from Clearbit, as long as you have a mapping to an " +"Zammad object." msgstr "" -#: ../system/integrations/zabbix.rst:2 -msgid "Zabbix Integration" +#: ../system/integrations/clearbit.rst:21 +msgid "" +"Clearbit does have a mapping of fields like LDAP and Exchange have, but does " +"not \"win\" against Zammad information. This means that if you have e.g. the " +"last name field filled in already and Clearbit has other information on " +"that, it will not be updated." msgstr "" -#: ../system/integrations/zabbix.rst:5 +#: ../system/integrations/clearbit.rst:26 msgid "" -"This guide describes how to integrate your Zabbix 5.4 installation with " -"Zammad using the Zabbix webhook feature. This guide will provide " -"instructions on setting up a media type, a user and an action in Zabbix." +"However: If let's say the last name has been set by Clearbit and Zammad " +"notices that the last name on the Clearbit source has changed, Zammad will " +"also update this value." msgstr "" -#: ../system/integrations/zabbix.rst:12 -msgid "Zammad with enabled HTTP Token Authentication" +#: ../system/integrations/clearbit.rst:33 +msgid "" +"The configuration of Clearbit is really easy and done fast! Just login to " +"your Clearbit-Account, go to \"API\" and copy the secret-API-Key." msgstr "" -#: ../system/integrations/zabbix.rst:13 -msgid "Zabbix version 5.4 or higher" +#: ../system/integrations/clearbit.rst:38 +msgid "" +"Now change to your Zammad instance, go to Integrations (System) -> Clearbit " +"in the admin panel. Paste your API-Key into the API-Key-Field and decide if " +"Zammad should create unknown Organizations automatically, if the user does " +"not have one yet (and Clearbit knows it). The shared option decides if the " +"new organizations Zammad creates with Clearbit should be shared ones." msgstr "" -#: ../system/integrations/zabbix.rst:16 -msgid "Setting up a Zammad" +#: ../system/integrations/clearbit.rst:47 +msgid "" +"If you're unsure what option to choose, better stick with \"no\". You can " +"also learn more about :doc:`/manage/organizations/index`." msgstr "" -#: ../system/integrations/zabbix.rst:18 -msgid "Enable **API Token Access** in Settings > System > API." +#: ../system/integrations/clearbit.rst:52 +msgid "" +"The Mapping option works similar to the mapping within the Exchange and LDAP " +"sync. You can add further mappings for e.g. custom fields if you need more " +"information that Clearbit can provide." msgstr "" -#: ../system/integrations/zabbix.rst:20 +#: ../system/integrations/clearbit.rst:58 msgid "" -"Create a **new user** for a Zabbix alerter with an **email address** and " -"create a personal user token with **ticket.agent** permissions." +"If you want to add more Clearbit fields and want to learn more about " +"available fields on their API, you can take a look at their `API " +"documentation `_." msgstr "" -#: ../system/integrations/zabbix.rst:24 -msgid "Zabbix Webhook Configuration" +#: ../system/integrations/clearbit.rst:62 +msgid "" +"If you're happy with the above chosen Settings and your mapping, just save " +"the changes and enable Clearbit integration. Zammad will now start polling " +"the Clearbit API as users contact you." msgstr "" -#: ../system/integrations/zabbix.rst:27 -#, fuzzy -msgid "Create a Global Macro" -msgstr "Makro-naredbe" - -#: ../system/integrations/zabbix.rst:29 +#: ../system/integrations/clearbit.rst:68 msgid "" -"Before setting up the **Webhook**, you need to setup the global macro " -"**{$ZABBIX.URL}**, which must contain the **URL** to the **Zabbix frontend**." +"Zammad does not synchronize with Clearbit on a regular basis, but on demand " +"if needed. This saves API calls." msgstr "" -#: ../system/integrations/zabbix.rst:33 +#: ../system/integrations/clearbit.rst:73 msgid "" -"In the **Administration** > **Media types** section, import the `Template`_." +"Below the Settings and Mappings, you'll find our Integration log. You can " +"see what requests Zammad sent to Clearbit and also the APIs Response." msgstr "" -#: ../system/integrations/zabbix.rst:38 -msgid "Open the added **Zammad** media type and set:" +#: ../system/integrations/clearbit.rst:78 +msgid "" +"By the way, you can also view the API log on the Clearbit website - the " +"information seen is basically the same." msgstr "" -#: ../system/integrations/zabbix.rst:40 -msgid "**zammad\\_access\\_token** to the your **Personal User Token**" +#: ../system/integrations/clearbit.rst:84 +msgid "Example When Adding a User" msgstr "" -#: ../system/integrations/zabbix.rst:41 +#: ../system/integrations/clearbit.rst:86 msgid "" -"**zammad\\_url** to the **frontend URL** of your **Zammad** installation" +"To show you how fast information is added, we added a small Screencast " +"below. This shows the creation of the User Alex from Clearbit. As we already " +"set the last name of Alex to \"X\", Zammad did not update it. What Zammad " +"did was to add further information it received from Clearbit." msgstr "" -#: ../system/integrations/zabbix.rst:43 -msgid "**zammad\\_customer** to your **Zammad user email**." +#: ../system/integrations/cti/generic.rst:2 +msgid "CTI (generic)" msgstr "" -#: ../system/integrations/zabbix.rst:44 +#: ../system/integrations/cti/includes/introduction.include.rst:1 msgid "" -"**zammad\\_enable\\_tags** to **true** or **false** to enable or disable " -"trigger tags. **Important**: if you enable tag support, each tag is set with " -"a separate request." +"This integration enables Zammad to provide a caller log to your agents. With " +"this your agents can greet your customers by their name and are supported by " +"Zammad with automatically opening a new ticket dialog or the user profile." msgstr "" -#: ../system/integrations/zabbix.rst:48 +#: ../system/integrations/cti/includes/introduction.include.rst:6 msgid "" -"If you want to prioritize issues according to **severity** values in Zabbix, " -"you can define mapping parameters:" +"Click the toggle next to the heading to activate or deactivate this " +"integration." msgstr "" -#: ../system/integrations/zabbix.rst:51 -msgid "**severity\\_**: Zammad priority ID" +#: ../system/integrations/cti/includes/introduction.include.rst:9 +msgid "" +"If you want to learn more on how your agents can use this function, please " +"refer the :user-docs:`user documentation `." msgstr "" -#: ../system/integrations/zabbix.rst:53 -msgid "Click the **Update** button to save the **Webhook** settings." +#: ../system/integrations/cti/includes/introduction.include.rst:14 +msgid "" +"Automatically opening new ticket dialogues or user profiles requires agent " +"to extension mapping - see more below." msgstr "" -#: ../system/integrations/zabbix.rst:55 -msgid "" -"To receive notifications in **Zammad**, you need to create a **Zabbix user** " -"and add **Media** with the **Zammad** type." +#: ../system/integrations/cti/includes/introduction.include.rst:20 +msgid "Please note the following limitations to reduce confusion later on:" msgstr "" -#: ../system/integrations/zabbix.rst:58 +#: ../system/integrations/cti/includes/introduction.include.rst:22 +msgid "CTI integrations provide caller log functions only." +msgstr "" + +#: ../system/integrations/cti/includes/introduction.include.rst:23 msgid "" -"For **Send to**: enter any text, as this value is not used, but is required." +"This integration does not provide any VoIP functionalities; you can't make " +"phone calls from within Zammad." msgstr "" -#: ../system/integrations/zabbix.rst:61 +#: ../system/integrations/cti/includes/introduction.include.rst:25 msgid "" -"For more information, use the `Zabbix documentation `_." +"If your browser supports ``tel``-URLs, you can click on phone numbers for " +"automatic dialing. This requires additional software / configuration on your " +"agent's computers." msgstr "" -#: ../system/maintenance.rst:2 -msgid "Maintenance" +#: ../system/integrations/cti/generic.rst:9 +#: ../system/integrations/cti/placetel.rst:14 +#: ../system/integrations/cti/sipgate.rst:14 +msgid "Please provide the following requirements:" msgstr "" -#: ../system/maintenance.rst:4 +#: ../system/integrations/cti/generic.rst:11 msgid "" -"Zammad comes with a maintenance mode that you can use for e.g. updating the " -"instance or changing settings while restricting availability and functions." +"A telephone system that supports webhooks (outbound) (best option are those " +"that allow customizing the calls)." msgstr "" -#: ../system/maintenance.rst:13 -msgid "Mode" +#: ../system/integrations/cti/generic.rst:13 +msgid "A unique Call-ID during the call session." msgstr "" -#: ../system/maintenance.rst:8 -msgid "The mode setting allows you to enable or disable the maintenance mode." +#: ../system/integrations/cti/generic.rst:14 +msgid "Call event data (both numbers and direction)." msgstr "" -#: ../system/maintenance.rst:10 -msgid "Defaults to *off*." +#: ../system/integrations/cti/generic.rst:15 +msgid "Your Zammad instance must be reachable for your telephony system." msgstr "" -#: ../system/maintenance.rst:12 +#: ../system/integrations/cti/generic.rst:17 msgid "" -"The maintenance mode will restrict access to administrative roles only. This " -"means agents and customers are logged off." +"If you want to learn more on what kind of requests are supported by Zammad " +"and what it expects, please consult our :docs:`CTI-API documentation `." msgstr "" -#: ../system/maintenance.rst:23 -msgid "@Login" +#: ../system/integrations/cti/generic.rst:22 +#: ../system/integrations/cti/placetel.rst:27 +#: ../system/integrations/cti/sipgate.rst:30 +msgid "Available Settings" msgstr "" -#: ../system/maintenance.rst:16 -msgid "" -"This setting allows you to provide a login message within a green banner " -"above the login screen. Click into the green banner in the settings page to " -"adjust your message. To activate the message, activate the *@Login* setting." +#: ../system/integrations/cti/generic.rst:29 +#: ../system/integrations/cti/placetel.rst:41 +#: ../system/integrations/cti/sipgate.rst:40 +msgid "Endpoint Settings" msgstr "" -#: ../system/maintenance.rst:0 +#: ../system/integrations/cti/generic.rst:25 msgid "" -"Screenshot showing the default login message within the\n" -"settings page" +"Zammad will list your generic CTI endpoint here. It contains a unique token " +"so ensure to keep this URL save." msgstr "" -#: ../system/maintenance.rst:26 +#: ../system/integrations/cti/generic.rst:28 msgid "" -"Send an informative message to **all active sessions**. This comes handy to " -"inform your agents e.g. about mayor outages or to force reloads after " -"configuration changes." +"You'll need this endpoint for your PBX to talk to Zammad, see :docs:`CTI-API " +"documentation `." msgstr "" -#: ../system/maintenance.rst:31 -msgid "This is the messages title (slightly bigger than the normal message)." +#: ../system/integrations/cti/includes/important-dont-forget-saving.include.rst:3 +msgid "" +"All following options **do not save automatically**. Always use the Save " +"button on the lower end of the integration page!" msgstr "" -#: ../system/maintenance.rst:34 -msgid "The text you want to provide to your logged in sessions." +#: ../system/integrations/cti/generic.rst:43 +#: ../system/integrations/cti/placetel.rst:49 +#: ../system/integrations/cti/sipgate.rst:52 +msgid "Call Settings" msgstr "" -#: ../system/maintenance.rst:39 -msgid "Reload application" +#: ../system/integrations/cti/generic.rst:39 +#: ../system/integrations/cti/placetel.rst:49 +#: ../system/integrations/cti/sipgate.rst:37 +#: ../system/integrations/cti/sipgate.rst:50 +msgid "Inbound" msgstr "" -#: ../system/maintenance.rst:37 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:1 msgid "" -"Selecting this option will change the message acceptance button from *Close* " -"(with nothing happening) to *Continue session*, which forces the application " -"to reload." +"This option allows you to block specific incoming caller IDs. It allows you " +"to temporarily reject e.g. spam callers without having to contact providers " +"or PBX administrators." msgstr "" -#: ../system/maintenance.rst:43 -msgid "" -"If you have customers that are logged in to Zammad, they'll also be notified " -"if they're active in that moment." +#: ../system/integrations/cti/includes/inbound-calls.include.rst:11 +msgid "Caller ID to block" msgstr "" -#: ../system/maintenance.rst:48 -msgid "Example without reload application" +#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 +msgid "Provide caller IDs to block in ``E.164`` format." msgstr "" -#: ../system/maintenance.rst:52 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:8 msgid "" -"Message setting within Zammad's admin settings without ticket reload " -"application setting." +"Your telephony system has to support this function. Zammad will send a " +"``reject`` response which will cause your telephony system to hang up the " +"call. To callers this usually will feel like the line is busy." msgstr "" -#: ../system/maintenance.rst:0 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:14 msgid "" -"Screenshot showing the send message settings without ticket\n" -"reload application set" +"Provide a meaningful note for your fellow administrators to remind yourself " +"why you've chosen to block the number." msgstr "" -#: ../system/maintenance.rst:61 ../system/maintenance.rst:85 -msgid "" -"The modal all other active sessions will see upon pressing *Send to clients*." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:17 +#: ../system/integrations/cti/sipgate.rst:40 +msgid "Outbound" msgstr "" -#: ../system/maintenance.rst:0 +#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:1 msgid "" -"Screenshot showing modal caused by maintenance's message\n" -"without reload application ticket" +"In many cases you may want to use a different caller ID depending on the " +"destination you're calling. This may apply due to specific connection rates " +"to other countries or because you want your customer to feel you're calling " +"from the same country." msgstr "" -#: ../system/maintenance.rst:72 -msgid "Example with reload application" +#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:6 +msgid "This option expects ``E.164`` number formats." msgstr "" -#: ../system/maintenance.rst:76 -msgid "" -"Message setting within Zammad's admin settings with ticket reload " -"application setting." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 +msgid "Destination caller ID" msgstr "" -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing the send message settings with ticket\n" -"reload application set" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:5 +msgid "The caller ID or number you're trying to call." msgstr "" -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing modal caused by maintenance's message\n" -"with reload application ticket" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:7 +msgid "You can use wildcards for e.g. country specific outbound numbers like:" msgstr "" -#: ../system/monitoring.rst:2 -msgid "Monitoring" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:9 +msgid "``49*`` for Germany" msgstr "" -#: ../system/monitoring.rst:4 -msgid "" -"This function is only available in self hosted instances. If you use Zammad " -"in our cloud, we are monitoring the system on our own and take steps to fix " -"potential problems directly." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:10 +msgid "``4930*`` for Berlin / Germany landlines" msgstr "" -#: ../system/monitoring.rst:11 -msgid "" -"On the monitoring page, you can see the current health state of Zammad under " -"\"*Current Status*\" at the bottom. This can be useful if you want to have a " -"look if everything is up and running. As an example, you could have a look " -"in the monitoring when you assume that some emails aren't processed from " -"Zammad." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 +msgid "``33*`` for France" msgstr "" -#: ../system/monitoring.rst:17 -msgid "**Can't receive an email and the monitoring response is \"healthy\"?**" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:15 +msgid "Set Outbound caller ID" msgstr "" -#: ../system/monitoring.rst:19 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:14 msgid "" -"Zammad will just inform you about unprocessable emails. This is not the case " -"for oversized emails. You can adjust the maximum email size in :doc:`../" -"channels/email/settings`." +"The outbound caller ID to set (the number your customer sees on his display) " +"in ``E.164`` number format." msgstr "" -#: ../system/monitoring.rst:24 -msgid "Monitoring API" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 +msgid "Provide a short description for fellow administrators." msgstr "" -#: ../system/monitoring.rst:26 +#: ../system/integrations/cti/includes/generic-cti-support-note.includes.rst:3 msgid "" -"Beside the indication in the monitoring page, you can also use an external " -"monitoring tool to monitor Zammad's health. To request the health of Zammad, " -"you need to provide the API key (token) to the external monitoring tool. You " -"can copy the token from the \"*Current Token*\" field as well as the whole " -"API endpoint of your system (\"*Health Check*\" field), in which the API " -"token is already included." +"This option requires your PBX to send a specific request to Zammad *before " +"dialing*. Please consult the :docs:`CTI API ` in case " +"you're not sure." msgstr "" -#: ../system/monitoring.rst:37 -msgid "Screenshot showing Current Token and Health Check" +#: ../system/integrations/cti/generic.rst:52 +#: ../system/integrations/cti/placetel.rst:54 +#: ../system/integrations/cti/sipgate.rst:59 +msgid "Other Settings" msgstr "" -#: ../system/monitoring.rst:37 -msgid "Screenshot showing Token and Health Check" +#: ../system/integrations/cti/includes/other-settings-intro.include.rst:1 +msgid "" +"Below you can find all available additional settings for this CTI " +"integration. For your overview we're sorting them by appearance and " +"reference their description first." msgstr "" -#: ../system/monitoring.rst:39 -msgid "" -"In addition to that, you can reset the auto-generated token to make sure " -"that already configured monitoring systems won't work anymore. So, please " -"use this \"*Reset*\" button only if you know what you do!" +#: ../system/integrations/cti/includes/default-caller-id.include.rst:2 +#: ../system/integrations/cti/includes/default-caller-id.include.rst:1 +msgid "Default caller ID for outbound calls" msgstr "" -#: ../system/monitoring.rst:44 -#, fuzzy -msgid "Example Output" -msgstr "Primjer" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:16 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:15 +msgid "Shown records in caller log" +msgstr "" -#: ../system/monitoring.rst:0 -msgid "No issues found" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:2 +msgid "" +"Allows you to set the number of shown caller log entries for all users. You " +"can choose from the following values:" msgstr "" -#: ../system/monitoring.rst:48 ../system/monitoring.rst:60 -msgid "**Indicator in Zammad**:" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:5 +msgid "60 (default)" msgstr "" -#: ../system/monitoring.rst:0 -msgid "Screenshot showing monitoring with no issues" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:6 +msgid "120" msgstr "" -#: ../system/monitoring.rst:54 ../system/monitoring.rst:66 -msgid "**API response**::" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:7 +msgid "180" msgstr "" -#: ../system/monitoring.rst:0 -msgid "Issues were found" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:8 +msgid "240" msgstr "" -#: ../system/monitoring.rst:0 -msgid "Screenshot showing monitoring with issues" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:9 +msgid "300" msgstr "" -#: ../system/objects.rst:2 -msgid "Objects" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:11 +msgid "**🥵 Potential performance issue**" msgstr "" -#: ../system/objects.rst:4 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:13 msgid "" -"In Zammad you can add your own fields to tickets, users, organizations and " -"even groups (these are called \"objects\"). This can be useful if you need " -"to add further information to a ticket or any other object in Zammad and the " -"information doesn't fit in any existing field." +"Setting this setting higher than 60 may cause serious performance issues on " +"very busy instances. Keep in mind that this setting causes Zammad to poll " +"and send up to 300 records to *all active agent sessions* in very short time " +"periods." msgstr "" -#: ../system/objects.rst:11 +#: ../system/integrations/cti/generic.rst:73 +msgid "Caller Log Filter" +msgstr "" + +#: ../system/integrations/cti/generic.rst:55 msgid "" -"Try to avoid deleting attributes (and disable them instead) as Zammad might " -"run into unexpected conditions if they are referenced somewhere." +"This function allows you to provide call information based on e.g. queues " +"only to agents that really need the information." msgstr "" -#: ../system/objects.rst:16 +#: ../system/integrations/cti/generic.rst:58 msgid "" -"Here's an overview of object attributes. On the upper right you can add new " -"attributes. By default, there will be no custom fields - standard attributes " -"will be grayed out, you can't delete or change those. You can edit custom " -"attributes (they are displayed in black font and have a trash bin on the " -"right side) just by clicking on them." +"Why? If you have a team for several countries or departments, you don't want " +"to bug your agents from other departments. Leaving these options empty will " +"fallback to showing everything to everyone." msgstr "" -#: ../system/objects.rst:24 -msgid "" -"Attributes you add to Zammad, no matter if they have default values or not, " -"will not update existing information. This means a new ticket field " -"technically will be empty unless you populate it." +#: ../system/integrations/cti/generic.rst:64 +msgid "Destination caller ID or Queue" msgstr "" -#: ../system/objects.rst:28 +#: ../system/integrations/cti/generic.rst:63 msgid "" -"Especially in ticket scope this also means that newly added attributes will " -"be indicated as \"changed\" to agents that view the ticket. This may " -"interfere with Zammad's tabs behavior." +"This depends on your PBX and usually is either a queue ID, phone number or " +"extension." msgstr "" -#: ../system/objects.rst:40 -msgid "Ordering Attributes" +#: ../system/integrations/cti/generic.rst:69 +msgid "Agents" msgstr "" -#: ../system/objects.rst:42 +#: ../system/integrations/cti/generic.rst:67 msgid "" -"Since Zammad introduced :doc:`/system/core-workflows` the need to have a " -"custom positioning for attributes has become more important than ever." +"Select the agents that are responsible for the group. These agents will then " +"see caller log entries and call notifications fitting to said queue." msgstr "" -#: ../system/objects.rst:45 +#: ../system/integrations/cti/generic.rst:0 msgid "" -"To adjust the position of such an attribute, simply click on the attribute " -"entry in question, scroll down and adjust the position number. Please note " -"that you cannot change the positioning of default attributes." +"Screenshot showing the caller log filter table with pre filled sample data" msgstr "" -#: ../system/objects.rst:49 +#: ../system/integrations/cti/includes/recent-logs.include.rst:6 msgid "" -"In case two attributes have the same position value, Zammad will sort " -"alphabetically by name automatically." +"With recent logs Zammad allows you to view the latest calls for the CTI " +"functionality. This usually comes in handy, when you're looking for errors." msgstr "" -#: ../system/objects.rst:None +#: ../system/integrations/cti/includes/recent-logs.include.rst:0 msgid "" -"Screenshot showing custom attribute entries ordered in between default ones" -msgstr "" - -#: ../system/objects.rst:56 -msgid "Updating Database After Adding or Editing Attributes" +"Screenshot showing several incoming requests within Recent logs section." msgstr "" -#: ../system/objects.rst:58 -msgid "" -"When adding or changing attributes, Zammad will not apply the changes " -"instantly, but instead shows you the changed attributes first. If you're " -"ready to go, just click on \"Update database\" to apply the changes to " -"Zammad. If you made a mistake or just want to discard your changes, click " -"\"Discard changes\"." +#: ../system/integrations/cti/includes/recent-logs.include.rst:16 +msgid "I'm just here to clear floats up." msgstr "" -#: ../system/objects.rst:64 +#: ../system/integrations/cti/includes/recent-logs.include.rst:20 msgid "" -"After applying the changes with \"Update Database\", a restart of Zammad is " -"**mandatory**. If you don't perform it, you may experience unexpected " -"behavior or even errors. You may want to do this kind of configuration " -"during maintenance windows." +"By clicking on the entry of interest, Zammad will provide more details on " +"the call in question. You'll see the payload it received and also the " +"response that was sent." msgstr "" -#: ../system/objects.rst:72 +#: ../system/integrations/cti/includes/recent-logs.include.rst:0 msgid "" -"Changes on objects require you to update the database to apply these changes." +"Screenshot showing detailed information of a specific log entry of recent " +"logs" msgstr "" -#: ../system/objects.rst:75 -msgid "**🤓 Service restarts can be automated**" +#: ../system/integrations/cti/includes/recent-logs.include.rst:31 +msgid "x" msgstr "" -#: ../system/objects.rst:0 -msgid "Hosted environments automatically restart for you." +#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 +#: ../system/integrations/cti/includes/troubleshooting.include.rst:9 +msgid "My Phone page stays blank, signalling does work..." msgstr "" -#: ../system/objects.rst:0 +#: ../system/integrations/cti/includes/troubleshooting.include.rst:5 msgid "" -"If you're using a self-hosted installation you can use :docs:`environment " -"variables `" +"If you've made sure that signalling works (check Recent logs) and your " +"Caller Log still stays empty, please ensure that you only configured one CTI " +"integration version. Specifically defining more than one agent mapping on " +"the different integration variants will be the issue." msgstr "" -#: ../system/objects.rst:82 -msgid "System Attributes" +#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 +msgid "Clear the not needed agent mapping and reload your browser page." msgstr "" -#: ../system/objects.rst:84 +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:1 msgid "" -"Zammad comes with pre-configured attributes. Some of them can't be edited " -"via UI (or at all). This is required for proper operation of Zammad and not " -"a bug." +"By mapping your agents extension to their existing Zammad users, Zammad can " +"provide a new ticket dialog or open the user profile for the agent that " +"picks up the call." msgstr "" -#: ../system/objects.rst:90 -msgid "Ticket State" +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:5 +msgid "" +"This speeds up ticket aiding, no matter if it's for existing tickets or new " +"ones!" msgstr "" -#: ../system/objects.rst:92 +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:8 msgid "" -"If the pre-configured states aren't enough for you or you want to change " -"them, you can do so by clicking on the cogwheel icon in the state row in the " -"ticket tab. But you should be careful when changing pre-configured states. " -"This can lead to unwanted behavior in some cases." +"To see it work from the agent's perspective, have a look on :user-docs:`user " +"documentation `." msgstr "" -#: ../system/objects.rst:None -msgid "Screenshot showing highlighted ticket state attribute" +#: ../system/integrations/cti/placetel.rst:2 +msgid "Placetel CTI" msgstr "" -#: ../system/objects.rst:122 -msgid "Handling of states" +#: ../system/integrations/cti/placetel.rst:16 +msgid "You need an administrative Placetel account for your organization." msgstr "" -#: ../system/objects.rst:102 +#: ../system/integrations/cti/placetel.rst:17 +#: ../system/integrations/cti/sipgate.rst:20 msgid "" -"In the state configuration screen, you can add new states, disable states or " -"change states." +"Your Zammad instance must be allowed to communicate to external services." msgstr "" -#: ../system/objects.rst:0 -msgid "Screenshot showing table of default ticket states" +#: ../system/integrations/cti/placetel.rst:18 +msgid "Placetel must be able to reach your Zammad instance." msgstr "" -#: ../system/objects.rst:110 -msgid "" -"To add a new state, click on the \"New Ticket State\" button in the top " -"right corner. To change an existing state, simply click on the affected " -"state. This opens an edit dialog." +#: ../system/integrations/cti/placetel.rst:22 +msgid ":doc:`provider-configurations/placetel`" msgstr "" -#: ../system/objects.rst:114 +#: ../system/integrations/cti/placetel.rst:21 msgid "" -"You can also clone a state or set them to \"Default for new tickets\" or " -"\"Default for follow-ups\" by clicking on the ⁝ action button and select the " -"desired function." +"Learn how to configure Placetel to enable Zammad and Placetel to communicate " +"with each other." msgstr "" -#: ../system/objects.rst:118 +#: ../system/integrations/cti/placetel.rst:32 msgid "" -"*Default for new tickets* means that this state is used for every newly " -"created ticket." +"The here listed endpoint settings are relevant for the :doc:`integration " +"configuration with Placetel `." msgstr "" -#: ../system/objects.rst:121 -msgid "" -"*Default for follow-ups* means that this state is used if the ticket is re-" -"opened after it was closed." +#: ../system/integrations/cti/placetel.rst:37 +#: ../system/integrations/i-doit.rst:53 +msgid "Endpoint" msgstr "" -#: ../system/objects.rst:171 -msgid "Ticket state in detail" +#: ../system/integrations/cti/placetel.rst:36 +msgid "" +"This endpoint will be required for the Zammad integration within the " +"Placetel web interface." msgstr "" -#: ../system/objects.rst:125 -msgid "" -"Below you can find a description for each field and option. Please head over " -"to the :ref:`example ` to see the edit dialog." +#: ../system/integrations/cti/placetel.rst:41 +msgid "API Token" msgstr "" -#: ../system/objects.rst:129 +#: ../system/integrations/cti/placetel.rst:40 msgid "" -"This is the name of the state and what you and your agents are seeing when " -"choosing a state somewhere (e.g. in tickets, trigger configuration)." +"You'll receive this token within the ``Web API`` menu. Make sure to copy " +"this value, it's only shown once!" msgstr "" -#: ../system/objects.rst:137 -msgid "" -"There are different state types you can choose from. By default, Zammad " -"comes with one state per state type." +#: ../system/integrations/cti/placetel.rst:71 +#: ../system/integrations/cti/sipgate.rst:77 +msgid "Phone Extension to Agent Mapping" msgstr "" -#: ../system/objects.rst:140 -msgid "" -"**new**: for states for tickets that are new and it hasn't been worked on " -"them" +#: ../system/integrations/cti/placetel.rst:0 +msgid "Screenshot showing sample user mappings in between Placetel and Zammad" msgstr "" -#: ../system/objects.rst:142 +#: ../system/integrations/cti/placetel.rst:64 msgid "" -"**open**: for states for tickets that are in progress and agents are working " -"on them" +"You can find your agents Placetel username combination required within ⚙️ PBX " +"→ VoIP destinations. Within the \"Advanced settings\" section you're looking " +"for \"SIP user name\" and \"SIP server\"." msgstr "" -#: ../system/objects.rst:144 -msgid "**merged**: for states for tickets that are merged with other tickets" +#: ../system/integrations/cti/placetel.rst:68 +msgid "Combine these two like so: ``@``." msgstr "" -#: ../system/objects.rst:145 -msgid "" -"**pending reminder**: for states for tickets that are in progress and you " -"want to set a reminder. (default example: *pending reminder*)" +#: ../system/integrations/cti/placetel.rst:0 +msgid "Sample VoIP credentials for a Placetel user" msgstr "" -#: ../system/objects.rst:147 -msgid "" -"**pending action**: for states for tickets that are waiting for a specified " -"time and then change their state (default example: *pending close*)" +#: ../system/integrations/cti/provider-configurations/placetel.rst:2 +msgid "Setup Placetel connection for Zammad" msgstr "" -#: ../system/objects.rst:150 +#: ../system/integrations/cti/provider-configurations/placetel.rst:6 msgid "" -"**closed**: for states for tickets that are finished and do not need to be " -"processed further" +"This configuration step requires a *full* administrative Placetel account. " +"You may receive forbidden error messages with Placetel in case your " +"permissions are not high enough." msgstr "" -#: ../system/objects.rst:153 +#: ../system/integrations/cti/provider-configurations/placetel.rst:10 msgid "" -"⚠️ Choosing the correct state type is important! If you are in doubt, have a " -"look on the default states and their types!" +"The following actions can be configured via the `Placetel web interface " +"`_." msgstr "" -#: ../system/objects.rst:158 -msgid "Ignore escalation" +#: ../system/integrations/cti/provider-configurations/placetel.rst:29 +msgid "Step 1: Activate Zammad integration" msgstr "" -#: ../system/objects.rst:157 +#: ../system/integrations/cti/provider-configurations/placetel.rst:14 msgid "" -"Here you can define whether tickets of this state will count to escalation " -"time or not." +"Within Integrations, scroll down to Partner integrations and select Zammad." msgstr "" -#: ../system/objects.rst:161 +#: ../system/integrations/cti/provider-configurations/placetel.rst:17 msgid "" -"You can create a note for the state to inform other admins about the state. " -"This has no effect on tickets." -msgstr "" - -#: ../system/objects.rst:165 -msgid "Set the state to *active* or *inactive*." +"You can alternatively filter by \"Ticket Systems\" to reduce the number of " +"entries on the page. You'll still want to look for Partner integrations. 🤓" msgstr "" -#: ../system/objects.rst:167 +#: ../system/integrations/cti/provider-configurations/placetel.rst:21 msgid "" -"it is technically possible to set all states to inactive. To keep Zammad " -"working in such a case, the inactive flag of one of the states is ignored." +"Within the Zammad integration now press \"Activate\". A new tab ``API`` " +"becomes available - open this tab." msgstr "" -#: ../system/objects.rst:194 -msgid "Ticket state example" +#: ../system/integrations/cti/provider-configurations/placetel.rst:24 +msgid "" +"Now tick \"Enable Call Control / Notify API\" and paste the Placetel " +"endpoint from your Zammad instance into the field \"URL of your API " +"endpoint\". Save to apply the settings" msgstr "" -#: ../system/objects.rst:174 -msgid "" -"Let's assume we want to create a new state which indicates that the ticket " -"has to wait for a response of a third party (e.g. service contractor or " -"manufacturer) and we want to to be able to set a reminder." +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "Screencast showing how to activate the Zammad integration" msgstr "" -#: ../system/objects.rst:178 -msgid "" -"First we give the new state a proper name. In this example we call it " -"\"waiting for manufacturer\"." +#: ../system/integrations/cti/provider-configurations/placetel.rst:51 +msgid "Step 2: Generate API Token for Placetel" msgstr "" -#: ../system/objects.rst:181 +#: ../system/integrations/cti/provider-configurations/placetel.rst:32 msgid "" -"As state type we choose \"pending reminder\". This indicates that the ticket " -"is still open and we can set a reminder. This reminder can be useful if our " -"manufacturer sometimes isn't responding or we want to remind him to give us " -"an answer." +"Go back to the integrations page and scroll down to \"Web API\". Generate a " +"new API token by using the \"Create a new API token\" button." msgstr "" -#: ../system/objects.rst:186 +#: ../system/integrations/cti/provider-configurations/placetel.rst:37 msgid "" -"We choose \"no\" for \"ignore escalation\" because we want to escalate the " -"tickets even if we are waiting on the manufacturer's feedback." +"If you already generated a token either use your existing token or reset it " +"by using above mentioned button. Placetel will ask you to conform this reset." msgstr "" -#: ../system/objects.rst:189 -#, fuzzy -msgid "The **result** in the creation dialog will look like this:" -msgstr "Krajnji rezultat će izgledati ovako:" - -#: ../system/objects.rst:0 -msgid "Screenshot showing ticket state creation dialog with example" +#: ../system/integrations/cti/provider-configurations/placetel.rst:41 +msgid "" +"Please keep in mind that existing API scripts may no longer work due to " +"token resets!" msgstr "" -#: ../system/objects.rst:197 ../system/objects.rst:199 -#, fuzzy -msgid "Ticket Priority" -msgstr "prioritet" +#: ../system/integrations/cti/provider-configurations/placetel.rst:44 +msgid "" +"Copy the provided API token and insert it into the \"API Token\" field " +"within Zammad's Placetel integration." +msgstr "" -#: ../system/objects.rst:199 ../system/objects.rst:201 +#: ../system/integrations/cti/provider-configurations/placetel.rst:47 msgid "" -"If the pre-configured priorities aren't enough for you or you want to change " -"them, you can do so by clicking on the cogwheel icon in the priority row in " -"the ticket tab:" +"Apply your changes by using the \"Save\" button on the bottom of the " +"Placetel integration page and activate the Placetel integration." msgstr "" -#: ../system/objects.rst:None -msgid "Screenshot showing highlighted ticket priority attribute" +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "" +"Screencast showing how to retrieve an API token from Placetel for Zammad" msgstr "" -#: ../system/objects.rst:224 ../system/objects.rst:226 -msgid "Handling of priorities" +#: ../system/integrations/cti/provider-configurations/placetel.rst:73 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:77 +msgid "Step 3: Restrict the numbers to notify on" msgstr "" -#: ../system/objects.rst:208 ../system/objects.rst:210 +#: ../system/integrations/cti/provider-configurations/placetel.rst:54 msgid "" -"In the priority configuration screen, you can add new priorities, disable " -"priorities or change priorities." +"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " +"the the Integrations page of the Placetel web interface, go to \"Notify " +"API\"." msgstr "" -#: ../system/objects.rst:0 -msgid "Screenshot showing table of default ticket priorities" +#: ../system/integrations/cti/provider-configurations/placetel.rst:58 +msgid "" +"Lower on the page Placetel allows you to restrict the numbers to notify on. " +"You'll find this within the \"External routing API\" part." msgstr "" -#: ../system/objects.rst:216 ../system/objects.rst:218 +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 msgid "" -"To add a new priority, click on the \"New Priority\" button in the top right " -"corner. To change an existing priority, simply click on the affected " -"priority. This opens an edit dialog." +"Screenshot showing a sample selection of phone numbers to use for the " +"Placetels notify API" msgstr "" -#: ../system/objects.rst:220 ../system/objects.rst:222 +#: ../system/integrations/cti/provider-configurations/placetel.rst:66 msgid "" -"You can also clone a priority or set them to \"Default for new tickets\" by " -"clicking on the ⁝ action button and select the desired function." +"This menu point also provides a API request log from Placetel view. Just " +"open \"Recent responses of your API endpoint\" to learn more." msgstr "" -#: ../system/objects.rst:223 ../system/objects.rst:225 +#: ../system/integrations/cti/provider-configurations/placetel.rst:69 msgid "" -"*Default for new tickets* means that this priority is used for every newly " -"created ticket." +"If you want to see Zammad's perspective, use the \"Recent Logs\" part from " +"within the Placetel integration page." msgstr "" -#: ../system/objects.rst:246 ../system/objects.rst:248 -msgid "Priorities in detail" +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "Screenshot showing sample log entries for Placetels API calls to Zammad" msgstr "" -#: ../system/objects.rst:227 ../system/objects.rst:229 -msgid "Below you can find a description for each field and option." +#: ../system/integrations/cti/provider-configurations/placetel.rst:77 +msgid "Step 4 (optional): Further configurations for Placetel" msgstr "" -#: ../system/objects.rst:230 ../system/objects.rst:232 +#: ../system/integrations/cti/provider-configurations/placetel.rst:76 msgid "" -"This is the name of the priority and what you and your agents are seeing " -"when choosing a priority somewhere (e.g. in tickets, trigger configuration)." +"If needed, you can now configure Zammad's Placetel integration in more " +"detail. You can learn more about your options here: :ref:`Placetel " +"integration settings `." msgstr "" -#: ../system/objects.rst:240 ../system/objects.rst:242 -msgid "Highlight color" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:2 +msgid "Setup Sipgate connection for Zammad" msgstr "" -#: ../system/objects.rst:235 ../system/objects.rst:237 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"Switch between *Low priority* (light blue), *High priority* (red) and - " -"(default). This affects the displayed color for ticket titles in overviews." -msgstr "" - -#: ../system/objects.rst:239 ../system/objects.rst:241 -msgid "The color options are currently limited to the mentioned options." +"Sipgate has no english web interface which is why this documentation page is " +"mixing up languages badly." msgstr "" -#: ../system/objects.rst:243 ../system/objects.rst:245 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"You can create a note for the priority to inform other admins about the " -"priority. This has no effect on tickets." +"Please also note that the availability of API addons highly depends on your " +"package trier. Usage of sipgate.io packages *is not free*, please check " +"their `pricing page `_ before!" msgstr "" -#: ../system/objects.rst:247 ../system/objects.rst:249 -msgid "Set the priority to *active* or *inactive*." +#: ../system/integrations/cti/provider-configurations/sipgate.rst:35 +msgid "Step 1: Book sipgate.io package" msgstr "" -#: ../system/objects/external-data-source-example.rst:2 -msgid "External Data Source" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:13 +msgid "Skip to step 2 if you already have the package booked!" msgstr "" -#: ../system/objects/external-data-source-example.rst:4 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:15 msgid "" -"We assume you already had a look on :doc:`types` where you can find a " -"description of the individual fields." +"Login to an administrative Sipgate account and navigate to " +"``Accountverwaltung``. You'll see several different options depending on " +"your booked packages. Select ``Verträge & Produkte`` to continue." msgstr "" -#: ../system/objects/external-data-source-example.rst:7 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:19 msgid "" -"To reproduce this example, choose a category you want to add a custom field, " -"click on *New Attribute* and select *External data source field* under " -"*Format*." +"Scroll down to the section ``Zusätzliche Produkte buchen`` and look for " +"``sipgate.io`` - select this product by using the ``Produkte anzeigen``-" +"Button." msgstr "" -#: ../system/objects/external-data-source-example.rst:11 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:23 msgid "" -"Our example story is to fetch data from an external product database. We " -"want to add our products to the tickets so that the products can be searched " -"and chosen from a list and also create a link to the product website." +"On the next page select either one of the ``sipgate.io`` packages or ``Push-" +"API Package Free``. Follow the dialogue by booking the addon. You'll be " +"returned to your contract overview and now should see the selected addon in " +"your list." msgstr "" -#: ../system/objects/external-data-source-example.rst:16 -msgid "Base configuration" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:30 +msgid "" +"The availability for ``sipgate.io`` packages and their levels highly depends " +"on the overall account type and product you've booked with Sipgate." msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Initial steps to configure external data source object type" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "" +"Screencast showing the process on how to book the required sipgate.io addon" msgstr "" -#: ../system/objects/external-data-source-example.rst:23 -#: ../system/variables.rst:85 -#, fuzzy -msgid "**Example:**" -msgstr "Primjer" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:52 +msgid "Step 2: Configure webhook for Zammad" +msgstr "" -#: ../system/objects/external-data-source-example.rst:25 -msgid "Name: *product*" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:38 +msgid "" +"Within your ``Accountverwaltung`` navicate to your product ``sipgate.io``. " +"In the newly opened tab, switch from \"Clients\" to \"Webhooks\" and paste " +"the endpoint URLs from your Zammad instance like so:" msgstr "" -#: ../system/objects/external-data-source-example.rst:26 -msgid "Display: *Product*" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:42 +msgid "Inbound endpoint to \"Incoming\"" msgstr "" -#: ../system/objects/external-data-source-example.rst:29 -msgid "External data source configuration" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:43 +msgid "Outbound endpoint to \"Outgoing\"" msgstr "" -#: ../system/objects/external-data-source-example.rst:31 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:47 msgid "" -"First, enter the search URL making sure it contains ``#{search.term}`` as a " -"parameter:" +"Ensure to select at least one call group or phoneline within \"Sources\". " +"Other wise Sipgate will not indicate any incoming or outgoing calls to " +"Zammad." msgstr "" -#: ../system/objects/external-data-source-example.rst:34 -msgid "**Example:** ``https://dummyjson.com/products/search?q=#{search.term}``" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "" +"Screencast showing how to add Zammad's endpoint URLs to sipgate.ios webhook " +"configuration" msgstr "" -#: ../system/objects/external-data-source-example.rst:36 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:55 msgid "" -"After that, head down to the preview section and enter a search input for " -"the external data source." +"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " +"the Webhooks → URLs section of Sipgate you can select which *sources* " +"Sipgate should notify Zammad about in- and outgoing calls." msgstr "" -#: ../system/objects/external-data-source-example.rst:39 -#, fuzzy -msgid "**Example:** ``mac``" -msgstr "Primjer" - -#: ../system/objects/external-data-source-example.rst:41 -msgid "Then you can find a preview of the response data below:" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:59 +msgid "" +"Use either specific phone lines or use the option \"Use for all phonelines " +"and groups\" to notify Zammad about all existing lines of your Sipgate " +"account." msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of JSON response based on search term" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "" +"Screenshot showing a sample selection of phone numbers to use for the " +"Sipgates webhooks API" msgstr "" -#: ../system/objects/external-data-source-example.rst:48 -msgid "" -"We recommend using the preview to have a look on the structure. There is a " -"top-level element called ``products``. One level below, you can find the " -"attributes ``id`` and ``title``." +#: ../system/integrations/cti/provider-configurations/sipgate.rst:68 +msgid "This section also allows you to enable a Debug log." msgstr "" -#: ../system/objects/external-data-source-example.rst:52 -msgid "**Search result response based on search from example:**" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "Screenshot showing an enabled Debug log option" msgstr "" -#: ../system/objects/external-data-source-example.rst:119 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:73 msgid "" -"To tell the remote system that the desired data is located below the " -"``products`` level, you have to put it in the field *Search result list key*." +"After enabling you can use the Debug log section to see all sent webhook " +"calls to Zammad. You'll also can see the response." msgstr "" -#: ../system/objects/external-data-source-example.rst:122 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"After inserting ``products`` in the mentioned field, you get an extended " -"preview. You can find an additional box *Search result list* with a JSON " -"structure. This is the same response as before but stripped from the upper " -"``products`` element by the external data source." +"Screenshot showing sample log entries for Sipgates webhook calls to Zammad" msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of JSON response search result list" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:81 +msgid "Step 4 (optional): Further configurations for Sipgate" msgstr "" -#: ../system/objects/external-data-source-example.rst:132 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:80 msgid "" -"Now you need to provide the keys for the search result values and labels. As " -"already mentioned, we are looking for the ``id`` and the ``title`` of our " -"products. If you haven't already, it is now a good time to look at the " -"preview of the *Search result list*." -msgstr "" - -#: ../system/objects/external-data-source-example.rst:197 -msgid "" -"After locating our two keys, we insert them in *search result value key* " -"(``id``) and in *Search result label key* (``title``)." -msgstr "" - -#: ../system/objects/external-data-source-example.rst:200 -msgid "" -"Basically, we configured the external data source already and we can see a " -"table in the preview section:" +"If needed, you can now configure Zammad's Sipgate integration in more " +"detail. You can learn more about your options here: :ref:`Sipgate " +"integration settings `." msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of product table based on search term" +#: ../system/integrations/cti/sipgate.rst:2 +msgid "Sipgate (sipgate.io)" msgstr "" -#: ../system/objects/external-data-source-example.rst:208 -msgid "" -"According to our example story, now just the *Link template* is missing." +#: ../system/integrations/cti/sipgate.rst:16 +msgid "You need an administrative Sipgate account for your organization." msgstr "" -#: ../system/objects/external-data-source-example.rst:210 +#: ../system/integrations/cti/sipgate.rst:17 msgid "" -"Please note that this is an optional feature. If you don't want to use such " -"links, of course you don't have to configure it." +"Zammad requires a ``sipgate.io`` addon from the feature store (please note " +"that API calls are not free with Sipgate. Rates may apply and differ from " +"account to account)." msgstr "" -#: ../system/objects/external-data-source-example.rst:213 -msgid "" -"We can add now an address where additional product information can be found." +#: ../system/integrations/cti/sipgate.rst:21 +msgid "Sipgate must be able to reach your Zammad instance." msgstr "" -#: ../system/objects/external-data-source-example.rst:215 -msgid "Example: ``https://your_domain.com/q=#{ticket.product}``" +#: ../system/integrations/cti/sipgate.rst:25 +msgid ":doc:`provider-configurations/sipgate`" msgstr "" -#: ../system/objects/external-data-source-example.rst:217 -msgid "In the example, the parameter means:" +#: ../system/integrations/cti/sipgate.rst:24 +msgid "" +"Learn how to configure Sipgate to enable Zammad and Sipgate to communicate " +"with each other." msgstr "" -#: ../system/objects/external-data-source-example.rst:219 -msgid "``#{}``: \"Frame\" for the insertion of information" +#: ../system/integrations/cti/sipgate.rst:33 +msgid "" +"Below endpoint settings affect the :doc:`sipgate.io configuration `." msgstr "" -#: ../system/objects/external-data-source-example.rst:220 -msgid "``ticket``: object level, where you create your custom object" +#: ../system/integrations/cti/sipgate.rst:37 +msgid "This endpoint is required for incoming call hooks." msgstr "" -#: ../system/objects/external-data-source-example.rst:221 -msgid "``product``: name of the (custom) object" +#: ../system/integrations/cti/sipgate.rst:40 +msgid "This endpoint is required for outgoing call hooks." msgstr "" -#: ../system/objects/external-data-source-example.rst:223 -msgid "" -"After configuring your *Link template*, there will be another column in the " -"preview. Hovering on the icons in the *Link* column will show you where it " -"forwards you." +#: ../system/integrations/cti/sipgate.rst:0 +msgid "Screenshot showing sample user mappings in between Sipgate and Zammad" msgstr "" -#: ../system/objects/external-data-source-example.rst:232 +#: ../system/integrations/cti/sipgate.rst:69 msgid "" -"In our example, one of the links looks like: https://your_domain.com/q=6, " -"where the 6 is the product id." +"You can find your agent's Sipgate username within ``Accountverwaltung → " +"Benutzer``. You're looking for the SIP-ID." msgstr "" -#: ../system/objects/external-data-source-example.rst:235 -#, fuzzy -msgid "You can find more information regarding the URL in :doc:`types`." +#: ../system/integrations/cti/sipgate.rst:0 +msgid "Sample VoIP credentials for a Sipgate user" msgstr "" -"Dodatne informacije o konfiguriranju chata možete pronaći u " -"administratorskoj dokumentaciji." -#: ../system/objects/includes/adding-values-hint.include.rst:3 -msgid "" -"Adding values can be tricky for first timers, don't forget to press \"➕ " -"Add\" after typing your values. Otherwise you may loose a value." +#: ../system/integrations/cti/sipgate.rst:77 +msgid "Users with several devices also have several SIP-IDs." msgstr "" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:1 -#: ../system/objects/includes/reposition-values.include.rst:1 -msgid "**↕️ This field type allows the positioning of its values ↔️**" +#: ../system/integrations/elasticsearch.rst:2 +msgid "Elasticsearch (SaaS)" msgstr "" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:3 +#: ../system/integrations/elasticsearch.rst:4 msgid "" -"In order to re-arrange the field values, first edit the field. Then you can " -"use ☰ to drag the values in question to the correct position. If you want to " -"change the layer depth, double click on ☰. With it you can cycle through the " -"available layers." -msgstr "" - -#: ../system/objects/includes/reposition-treeselect-values.include.rst:8 -msgid "When you're ready, submit your changes to save the object attribute." +"The Elasticsearch integration allows you to create a read-only user to use " +"with your favorite reporting tool (e.g. like Grafana)." msgstr "" -#: :0 ../system/objects/types.rst:0 +#: ../system/integrations/elasticsearch.rst:7 msgid "" -"Screencast showing how to re-position values on tree select like\n" -"fields" +"If you want to take full advantage of the Zammad reporting, have a look at " +"our :docs:`Grafana ` " +"setup page as well." msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:3 -msgid "" -"In order to re-arrange the field values, edit the field and scroll below the " -"values. Make sure to tick the option \"Use custom option sort\"." +#: ../system/integrations/elasticsearch.rst:11 ../system/subscription.rst:7 +msgid "**🚧 Hosted environment specific 🚧**" msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:8 +#: ../system/integrations/elasticsearch.rst:13 msgid "" -"If you do not tick this field, all manual positioning you did above will be " -"lost upon saving! ☠️" +"This integration is only available for Hosted setups. In order to use " +"Elasticsearch you'll need the **Plus** subscription." msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:11 +#: ../system/integrations/elasticsearch.rst:16 msgid "" -"Now use ☰ to drag the values in question to the correct position. When " -"you're ready, submit your changes to save the object attribute." +"Self hosted users have all the control over their self hosted Elasticsearch " +"instances." msgstr "" -#: :0 ../system/objects/types.rst:0 -msgid "Screencast showing how to re-position values" +#: ../system/integrations/elasticsearch.rst:None +msgid "Elasticsearch integration page on SaaS environments" msgstr "" -#: ../system/objects/includes/url-template-hint.include.rst:3 +#: ../system/integrations/elasticsearch.rst:27 msgid "" -"This field allows using :ref:`URL fields (Link Templates) `." -msgstr "" - -#: ../system/objects/permissions.rst:2 -msgid "Attribute Permissions" +"Please note the following limitations of Elasticsearch access on hosted " +"environments:" msgstr "" -#: ../system/objects/permissions.rst:7 -msgid "" -"In the object attributes configuration you can define if a field is shown " -"and if the input in the field is mandatory, separated by different screens " -"and for different :doc:`roles/permissions `." +#: ../system/integrations/elasticsearch.rst:30 +msgid "access to the Elasticsearch index is read-only access" msgstr "" -#: ../system/objects/permissions.rst:17 -msgid "Screenshot shows object attribute permission table" +#: ../system/integrations/elasticsearch.rst:31 +msgid "currently you're limited to user only" msgstr "" -#: ../system/objects/permissions.rst:17 +#: ../system/integrations/elasticsearch.rst:32 msgid "" -"Some of the possible permissions and screen options for a user object " -"attribute." +"Reporting tools that require to write into the indexes (like Kibana) are not " +"supported" msgstr "" -#: ../system/objects/permissions.rst:19 -msgid "" -"Based on the object context (ticket, agent, organization, user), the " -"selectable roles (to be precise: the required permissions) and screens " -"differ. Be aware that these settings aren't affecting data creation via " -"other channels than the UI." +#: ../system/integrations/elasticsearch.rst:34 +msgid "IP access restriction is currently not yet supported" msgstr "" -#: ../system/objects/permissions.rst:24 -msgid "" -"If you want to have further customization possibilities, you should have a " -"look at the :doc:`core workflows `." +#: ../system/integrations/elasticsearch.rst:37 +msgid "Activating Elasticsearch Access" msgstr "" -#: ../system/objects/permissions.rst:28 -msgid "Screens" +#: ../system/integrations/elasticsearch.rst:39 +msgid "" +"By default external access to your Elasticsearch index is not active. You " +"can enable the integration at any time if needed." msgstr "" -#: ../system/objects/permissions.rst:30 +#: ../system/integrations/elasticsearch.rst:42 msgid "" -"In the table below you can find an overview about the different permissions " -"and the available screens Zammad distinguishes between." +"Please ensure to note down the password provided - you won't have access to " +"it afterwards." msgstr "" -#: ../system/objects/permissions.rst:37 -msgid "Screen" +#: ../system/integrations/elasticsearch.rst:None +msgid "Screencast showing activation of Elasticsearch integration" msgstr "" -#: ../system/objects/permissions.rst:38 -msgid "Available for" +#: ../system/integrations/elasticsearch.rst:51 +msgid "Connection Settings" msgstr "" -#: ../system/objects/permissions.rst:40 -msgid "create" +#: ../system/integrations/elasticsearch.rst:53 +msgid "" +"This section holds the most important general information for accessing your " +"Elasticsearch indexes - such as:" msgstr "" -#: ../system/objects/permissions.rst:41 ../system/objects/permissions.rst:52 -#: ../system/objects/permissions.rst:59 ../system/objects/permissions.rst:73 -msgid "admin.user" +#: ../system/integrations/elasticsearch.rst:57 +msgid "A unique subdomain that does not tell your real instance URL." msgstr "" -#: ../system/objects/permissions.rst:42 ../system/objects/permissions.rst:53 -#: ../system/objects/permissions.rst:60 -msgid "admin.organization" +#: ../system/integrations/elasticsearch.rst:61 +msgid "Software" msgstr "" -#: ../system/objects/permissions.rst:43 ../system/objects/permissions.rst:54 -#: ../system/objects/permissions.rst:61 -#, fuzzy -msgid "admin.group" -msgstr "grupa" - -#: ../system/objects/permissions.rst:44 -msgid "Creation dialog for not yet existing data" +#: ../system/integrations/elasticsearch.rst:60 +msgid "" +"The major version of the search index being used. This is required by some " +"Reporting tools like Grafana." msgstr "" -#: ../system/objects/permissions.rst:45 -msgid "create_middle" +#: ../system/integrations/elasticsearch.rst:64 +msgid "Authentication" msgstr "" -#: ../system/objects/permissions.rst:46 ../system/objects/permissions.rst:50 -#: ../system/objects/permissions.rst:57 ../system/objects/permissions.rst:66 -#: ../system/objects/permissions.rst:70 -#, fuzzy -msgid "ticket.customer" -msgstr "Makro-naredbe" - -#: ../system/objects/permissions.rst:47 ../system/objects/permissions.rst:51 -#: ../system/objects/permissions.rst:58 ../system/objects/permissions.rst:69 -#, fuzzy -msgid "ticket.agent" -msgstr "Makro-naredbe" - -#: ../system/objects/permissions.rst:48 -msgid "Ticket create dialog (middle section)" +#: ../system/integrations/elasticsearch.rst:64 +msgid "The authentication type being supported. ``Basic Authentication``" msgstr "" -#: ../system/objects/permissions.rst:49 -msgid "edit" +#: ../system/integrations/elasticsearch.rst:67 +msgid "Available Indexes" msgstr "" -#: ../system/objects/permissions.rst:55 -msgid "Editing dialog for already existing data" +#: ../system/integrations/elasticsearch.rst:69 +msgid "" +"Within this section we're displaying the -in our opinion- most important " +"indexes for a Zammad instance." msgstr "" -#: ../system/objects/permissions.rst:56 -msgid "view" +#: ../system/integrations/elasticsearch.rst:72 +msgid "" +"If you require all indexes or our listing is not good enough for you, point " +"your browser to the URL we're providing and append ``/_aliases?" +"pretty=true``. The result should look like this: ``https://.zammad.com/" +"_aliases?pretty=true``." msgstr "" -#: ../system/objects/permissions.rst:62 -msgid "View-only dialog for already existing data" +#: ../system/integrations/elasticsearch.rst:77 +msgid "" +"Your browser will automatically ask for your credentials - you'll then see " +"something like this:" msgstr "" -#: ../system/objects/permissions.rst:64 -msgid "(e.g. user or organization from search)" +#: ../system/integrations/elasticsearch.rst:125 +msgid "Credentials" msgstr "" -#: ../system/objects/permissions.rst:65 -msgid "signup" +#: ../system/integrations/elasticsearch.rst:127 +msgid "" +"Within this section Zammad displays your available users. The password is " +"provided once (upon activation) and cannot be retrieved after that." msgstr "" -#: ../system/objects/permissions.rst:67 -msgid "Sign-up screen for new customers" +#: ../system/integrations/elasticsearch.rst:131 +msgid "" +"If you need to change or reset your Elasticsearch user password, use the " +"\"Reset password\" button in the credentials table. Doing so creates a brand " +"new password for the account in question. This change is immediate, keep in " +"mind that this may affect third party tools connected to your instance." msgstr "" -#: ../system/objects/permissions.rst:68 -msgid "invite_customer" +#: ../system/integrations/exchange.rst:2 +msgid "Exchange" msgstr "" -#: ../system/objects/permissions.rst:71 +#: ../system/integrations/exchange.rst:4 msgid "" -"Customer invitation screen (from :doc:`First Steps ` area)" +"With Zammad's Exchange integration, you can easily use existing address " +"books without having to update more than one source." msgstr "" -#: ../system/objects/permissions.rst:72 -msgid "invite_agent" +#: ../system/integrations/exchange.rst:7 +msgid "" +"However, you should refrain from syncing all addresses, as the results may " +"not be what you expect (Exchange collects huge amounts of addresses). A " +"central address book of your company to sync makes more sense, as you can " +"ensure that Zammad gets only the data you need and want. Apart from this, it " +"is even not possible to sync the Global Address List (GAL) of your Exchange " +"system with Zammad." msgstr "" -#: ../system/objects/permissions.rst:74 +#: ../system/integrations/exchange.rst:16 msgid "" -"Agent invitation screen (from :doc:`First Steps ` area)" +"**Exchange and LDAP:** The exchange sync can be overruled by Zammad's LDAP " +"integration. If you have the same users in both sources, the LDAP version " +"will always be Zammad's pick." msgstr "" -#: ../system/objects/permissions.rst:78 -msgid "Screen Options" +#: ../system/integrations/exchange.rst:19 +msgid "" +"**One way sync:** the Exchange sync is one way. Exchange => Zammad. Changes " +"to your users inside of Zammad might be overwritten by the Exchange sync." msgstr "" -#: ../system/objects/permissions.rst:80 +#: ../system/integrations/exchange.rst:24 msgid "" -"For the different screens you can select \"show\" and \"required\" options." +"To configure Exchange integration, simply go to the System > Integrations > " +"Exchange in the admin panel. Press \"change\" and follow the wizard for " +"adding the needed Exchange information to Zammad. On the last two steps " +"Zammad will ask you for the address book(s) and your desired attribute " +"mapping. By default, Zammad only maps email address, first- and lastname. " +"Technically, you can map any Exchange object to a Zammad user object (this " +"also works for custom objects!)." msgstr "" -#: ../system/objects/permissions.rst:82 -msgid "**shown:** Show (check) or hide (uncheck) a field." +#: ../system/integrations/exchange.rst:35 +msgid "" +"If the SSL verification fails while connecting to Exchange, Zammad will ask " +"you to turn it off temporarily." msgstr "" -#: ../system/objects/permissions.rst:83 +#: ../system/integrations/exchange.rst:38 msgid "" -"**required:** Set a field to mandatory (check). Forces users (via UI and " -"API) to populate the field." +"Please be aware that **turning off SSL verification is a security risk**. It " +"should only be used temporarily or for testing purposes. If turned off, " +"there is no verification of the certificate, which means that every " +"presented certificate will be accepted." msgstr "" -#: ../system/objects/types.rst:7 -msgid "Example external data source" +#: ../system/integrations/exchange.rst:43 +msgid "" +"After pressing Continue, Zammad will check if the configuration is okay. You " +"can then enable Exchange and start your first sync. The sync will then run " +"hourly - if you need to change mappings or the address book(s), you can " +"change the configuration at any time." msgstr "" -#: ../system/objects/types.rst:2 -msgid "Attribute types" +#: ../system/integrations/exchange.rst:50 +msgid "" +"After the sync has finished, you can find the new Exchange contacts under " +"\"Users\". Zammad integrates them just as normal users." msgstr "" -#: ../system/objects/types.rst:4 +#: ../system/integrations/exchange.rst:55 msgid "" -"When adding a new object attribute, you can choose between the following " -"attribute types." +"In some cases you might see unique IDs as \"Login\" instead of the email " +"address. This is normal and doesn't affect the login or email mapping for " +"that entry." msgstr "" -#: ../system/objects/types.rst:14 +#: ../system/integrations/github.rst:4 msgid "" -"You cannot change the attribute format / type as soon as it is applied. If " -"you no longer need an object attribute, consider disabling it instead of " -"removing." +"Use GitHub integration to track GitHub issues directly within Zammad " +"tickets. Add issue hyperlinks and get a live summary of metadata like status " +"(open/closed), assignee, labels, and more." msgstr "" -#: ../system/objects/types.rst:18 -msgid "**What about the translation of my attributes?**" +#: ../system/integrations/github.rst:8 +msgid "Please note that our GitHub integration does not support pull requests." msgstr "" -#: ../system/objects/types.rst:20 -msgid "" -"For some attribute types you can decide if they should be translatable or " -"not. To be precise, it works only for the selectable fields because the " -"possible choices are known and limited. For the following attribute types, " -"you can set the translatable flag:" +#: ../system/integrations/github.rst:None +msgid "Integration page for GitHub" msgstr "" -#: ../system/objects/types.rst:25 -msgid "*Boolean field*" +#: ../system/integrations/github.rst:18 +msgid "" +"In your GitHub settings, create a new API token under **Developer settings > " +"Personal access tokens > Generate new token**. Leave the **Scopes** section " +"empty." msgstr "" -#: ../system/objects/types.rst:26 -msgid "*Single selection field*" +#: ../system/integrations/github.rst:0 ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to create a new API token" msgstr "" -#: ../system/objects/types.rst:27 -msgid "*Multiple selection field*" +#: ../system/integrations/github.rst:27 +msgid "Create a new API key with no scopes/privileges." msgstr "" -#: ../system/objects/types.rst:28 -msgid "*Single tree selection field*" +#: ../system/integrations/github.rst:29 +msgid "🔒 **Will this work for private repos?**" msgstr "" -#: ../system/objects/types.rst:29 -msgid "*Multiple tree selection field*" +#: ../system/integrations/github.rst:31 +msgid "" +"No. To link private repo issues, **use the** ``repo`` **scope instead**. " +"Bear in mind that the resulting token will have `lots of permissions that it " +"doesn't actually need `_, which presents a security risk if your token ever falls into " +"the wrong hands." msgstr "" -#: ../system/objects/types.rst:31 +#: ../system/integrations/github.rst:37 msgid "" -"For these types, you can find an additional field *Translate field contents*:" +"Unfortunately, because of how GitHub's OAuth token scopes are set up, this " +"is the only way to link issues on private repos." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Screenshot showing translatable attribute types" +#: ../system/integrations/github.rst:40 +msgid "Enter your new API token in Zammad and enable GitHub integration." msgstr "" -#: ../system/objects/types.rst:38 -msgid "Screenshot with example of translatable attribute type" +#: ../system/integrations/github.rst:0 +msgid "Screencast showing how to configure Zammad's GitHub integration" msgstr "" -#: ../system/objects/types.rst:45 -msgid "Boolean field" +#: ../system/integrations/github.rst:47 +msgid "" +"Use the default API endpoint (``https://api.github.com/graphql``) unless " +"you're using GitHub Enterprise Server." msgstr "" -#: ../system/objects/types.rst:41 +#: ../system/integrations/github.rst:50 msgid "" -"Provides a drop-down field with display values for ``true`` and ``false``. " -"Setting a default is mandatory." +"Once completed, a new GitHub issues tab will appear in the ticket pane. 🎉" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Boolean fields" +#: ../system/integrations/github.rst:59 ../system/integrations/gitlab.rst:52 +msgid "Token verification is taking a long time" msgstr "" -#: ../system/objects/types.rst:55 -msgid "Date field" +#: ../system/integrations/github.rst:56 ../system/integrations/gitlab.rst:49 +msgid "" +"Slight delays are normal (<2 min.), especially for systems under heavy load." msgstr "" -#: ../system/objects/types.rst:48 -msgid "Provides a date picker field and does not allow default values." +#: ../system/integrations/github.rst:58 +msgid "" +"Self-hosted administrators, please check your network settings to ensure " +"that your Zammad server can reach ``api.github.com``." msgstr "" -#: ../system/objects/types.rst:52 -msgid "Default time diff (hours)" +#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 +msgid "I reloaded the page and now the API token is gone" msgstr "" -#: ../system/objects/types.rst:51 +#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 msgid "" -"This setting helps the user by highlighting the day from now plus the " -"provided value. It *does not* pre-fill the field." -msgstr "" - -#: ../system/objects/types.rst:0 -msgid "Available settings for Date fields" +"This may indicate that Zammad is still verifying your API token. Try " +"reloading the page again in a couple minutes." msgstr "" -#: ../system/objects/types.rst:73 -msgid "Date & time field" +#: ../system/integrations/gitlab.rst:2 +msgid "GitLab" msgstr "" -#: ../system/objects/types.rst:58 -msgid "Provides a date and time picker – does not allow default values" +#: ../system/integrations/gitlab.rst:4 +msgid "" +"Use GitLab integration to track GitLab issues directly within Zammad " +"tickets. Add issue hyperlinks and get a live summary of metadata like status " +"(open/closed), assignee, labels, and more." msgstr "" -#: ../system/objects/types.rst:62 -msgid "Allow future" +#: ../system/integrations/gitlab.rst:8 +msgid "" +"Please note that our GitLab integration does not support merge requests." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Forbid dates and times in the future." +#: ../system/integrations/gitlab.rst:None +msgid "Integration page for GitLab" msgstr "" -#: ../system/objects/types.rst:66 -msgid "Allow past" +#: ../system/integrations/gitlab.rst:18 +msgid "" +"In your GitLab preferences, create a new API token under **Access Tokens**." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Forbid dates and times in the past." +#: ../system/integrations/gitlab.rst:20 +msgid "Under **Select scopes**, choose ``read_api`` only." msgstr "" -#: ../system/objects/types.rst:70 -msgid "Default time diff (minutes)" +#: ../system/integrations/gitlab.rst:27 +msgid "🔒 **If you wish to link issues on any private repos...**" msgstr "" -#: ../system/objects/types.rst:69 -msgid "" -"This setting helps the user by highlighting the day from now plus the " -"provided value. It does not pre-fill the field." +#: ../system/integrations/gitlab.rst:29 +msgid "Your API token must belong to an account with access to those repos." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Date & time fields" +#: ../system/integrations/gitlab.rst:31 +msgid "Enter your new API token in Zammad and enable GitLab integration." msgstr "" -#: ../system/objects/types.rst:86 -msgid "Integer field" +#: ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to configure Zammad's GitLab integration" msgstr "" -#: ../system/objects/types.rst:76 +#: ../system/integrations/gitlab.rst:40 msgid "" -"Provides an input field that allows integer usage only. You may define a " -"default value. You cannot enforce comma separation." +"Use the default API endpoint (``https://gitlab.com/api/graphql``) unless " +"you're a self-hosted GitLab user." msgstr "" -#: ../system/objects/types.rst:80 -msgid "Minimal" +#: ../system/integrations/gitlab.rst:43 +msgid "" +"Once completed, a new GitLab issues tab will appear in the ticket pane. 🎉" msgstr "" -#: ../system/objects/types.rst:80 -msgid "The minimal value the field accepts." +#: ../system/integrations/gitlab.rst:51 +msgid "" +"Self-hosted administrators, please check your network settings to ensure " +"that your Zammad server can reach ``gitlab.com``." msgstr "" -#: ../system/objects/types.rst:83 -msgid "Maximal" +#: ../system/integrations/i-doit.rst:2 +msgid "i-doit" msgstr "" -#: ../system/objects/types.rst:83 -msgid "The maximum value the field accepts." +#: ../system/integrations/i-doit.rst:4 +msgid "" +"`i-doit `_ is an open-source **configuration " +"management database** - in other words, a tool for keeping tabs on every " +"single piece of your physical and digital infrastructure, from network " +"equipment to virtual machines on down to the faceplates on your rack shelves " +"and more." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Integer fields" +#: ../system/integrations/i-doit.rst:10 +msgid "" +"What's that got to do with Zammad? Well, if you used tickets to track issues " +"with all that hardware, you might start wishing there was a way they could " +"talk to each other." msgstr "" -#: ../system/objects/types.rst:99 -msgid "Multiple selection field" +#: ../system/integrations/i-doit.rst:14 +msgid "Zammad gives you two:" msgstr "" -#: ../system/objects/types.rst:89 -msgid "" -"Provides a selection field that allows the selection of one or more out of " -"several. This field does allow setting a default value." +#: ../system/integrations/i-doit.rst:17 +msgid "1. Add i-doit Links to Zammad Tickets" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Multiple selection fields" +#: ../system/integrations/i-doit.rst:20 ../system/integrations/i-doit.rst:80 +msgid "What Users See" msgstr "" -#: ../system/objects/types.rst:112 -msgid "Single selection field" +#: ../system/integrations/i-doit.rst:26 +msgid "i-doit integration in Zammad's ticket pane" msgstr "" -#: ../system/objects/types.rst:102 +#: ../system/integrations/i-doit.rst:26 msgid "" -"Provides a drop-down field that allows selection of one value out of " -"several. This field does allow setting a default value." +"The i-doit integration will appear under a new 🖨 tab in the ticket pane." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Single selection fields" +#: ../system/integrations/i-doit.rst:28 +msgid "" +"i-doit integration puts a new tab in Zammad's ticket pane where you can add " +"links to existing i-doit devices for easy reference. (See our :user-docs:" +"`user documentation ` to learn " +"how it works in practice)." msgstr "" -#: ../system/objects/types.rst:142 -msgid "Textarea field" +#: ../system/integrations/i-doit.rst:36 ../system/integrations/i-doit.rst:93 +msgid "How to Set it Up" msgstr "" -#: ../system/objects/types.rst:115 +#: ../system/integrations/i-doit.rst:38 msgid "" -"Provides a text area input field (multiple lines) and thus allows e.g. new " -"lines. You can set a default field value." +"It requires i-doit's `API Add-on `_. Make sure to have it properly set up. Use the following setting:" msgstr "" -#: ../system/objects/types.rst:120 -msgid "" -"Please note that this field *does not* support text formatting or HTML " -"content (rich text)." +#: ../system/integrations/i-doit.rst:42 +msgid "Active: ``Yes``" msgstr "" -#: ../system/objects/types.rst:123 -msgid "**🥵 This field can consume a lot of visual space**" +#: ../system/integrations/i-doit.rst:43 +msgid "Enforce authentication by username and password: ``No``" msgstr "" -#: ../system/objects/types.rst:125 +#: ../system/integrations/i-doit.rst:45 msgid "" -"Depending on where you use this field type, it may use a lot of visual space " -"if you provide a lot of text. This may be an issue to work with." +"To set it up, enable the integration in the Zammad admin panel under " +"**System > Integrations > i-doit**:" msgstr "" -#: ../system/objects/types.rst:130 -msgid "Default" +#: ../system/integrations/i-doit.rst:None +msgid "i-doit settings within the integration pages" msgstr "" -#: ../system/objects/types.rst:129 -msgid "" -"The here provided text will be shown within the text area field or new data " -"sets." +#: ../system/integrations/i-doit.rst:53 +msgid "The root URL of your i-doit installation." msgstr "" -#: ../system/objects/types.rst:134 ../system/objects/types.rst:160 -msgid "Maxlength" +#: ../system/integrations/i-doit.rst:62 +msgid "API token" msgstr "" -#: ../system/objects/types.rst:0 ../system/objects/types.rst:160 -msgid "You can pick the maximum length of the field." +#: ../system/integrations/i-doit.rst:56 +msgid "" +"Found in the i-doit admin panel under **Interfaces / external data > JSON-" +"RPC API > Common Settings**." msgstr "" -#: ../system/objects/types.rst:0 -msgid "The default length of this object is ``500``." +#: ../system/integrations/i-doit.rst:0 +msgid "i-doit administration interface with API configuration" msgstr "" -#: ../system/objects/types.rst:139 -msgid "Rows" +#: ../system/integrations/i-doit.rst:67 +msgid "Client ID" msgstr "" -#: ../system/objects/types.rst:0 -msgid "" -"Change the number of rows to dislay so that you can use only the space you " -"really need." +#: ../system/integrations/i-doit.rst:65 +msgid "A unique name to identify Zammad within i-doit." msgstr "" -#: ../system/objects/types.rst:0 -msgid "The default number of rows is ``4``." +#: ../system/integrations/i-doit.rst:67 +msgid "(Zammad does not require you to enter a value here, but i-doit might!)" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Textarea fields" +#: ../system/integrations/i-doit.rst:70 +msgid "" +"Here you can decide if the certificate of your i-doit system has to be " +"verified or not. In case you are using custom certificates, please have a " +"look at :doc:`how to add them to Zammad `." msgstr "" -#: ../system/objects/types.rst:165 -msgid "Text field" +#: ../system/integrations/i-doit.rst:77 +msgid "2. List / Create Zammad Tickets in i-doit" msgstr "" -#: ../system/objects/types.rst:145 -msgid "Provides a text field (one line) and allows choosing a default value." +#: ../system/integrations/i-doit.rst:None +msgid "Zammad integration in i-doit's device view" msgstr "" -#: ../system/objects/types.rst:148 +#: ../system/integrations/i-doit.rst:86 msgid "" -"Defines the type of the input field. This allows e.g. your browser to ensure " -"that you provide the specific type." +"i-doit's ticket system integration gives you a way to see all the tickets " +"for a given device without ever leaving i-doit. (See our :user-docs:`user " +"documentation ` to learn how it " +"works in practice)." msgstr "" -#: ../system/objects/types.rst:152 -msgid "Currently available:" +#: ../system/integrations/i-doit.rst:95 +msgid "" +"Enable this integration in the i-doit admin panel under **Interfaces / " +"external data > Trouble Ticket System (TTS) > Configuration**:" msgstr "" -#: ../system/objects/types.rst:155 -msgid "Phone" +#: ../system/integrations/i-doit.rst:None +msgid "i-doit administration interface with TTS configuration" msgstr "" -#: ../system/objects/types.rst:156 -msgid "Text" +#: ../system/integrations/i-doit.rst:104 +msgid "TTS-Type" msgstr "" -#: ../system/objects/types.rst:157 -msgid "Url *(URL fields disable link-template availability)*" +#: ../system/integrations/i-doit.rst:104 +msgid "``Zammad``" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Text fields" +#: ../system/integrations/i-doit.rst:115 +msgid "Username / Password" msgstr "" -#: ../system/objects/types.rst:174 -msgid "Single tree selection field" +#: ../system/integrations/i-doit.rst:107 +msgid "Login credentials for a Zammad agent." msgstr "" -#: ../system/objects/types.rst:168 +#: ../system/integrations/i-doit.rst:109 msgid "" -"Provides a select-like field with up to 6 layers of options. Does not allow " -"setting a default value." +"This agent must have **read permission** for all :doc:`groups ` that plan on using the i-doit integration." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Tree Select fields" +#: ../system/integrations/i-doit.rst:113 +msgid "" +"You may even wish to create a dedicated agent account just for this " +"integration (otherwise, if the agent ever changes her password, you will " +"have to remember to update it here)." msgstr "" -#: ../system/objects/types.rst:183 -msgid "Multiple tree selection field" +#: ../system/integrations/i-doit.rst:117 +msgid "URL incl. protocol" msgstr "" -#: ../system/objects/types.rst:177 -msgid "" -"Provides a select-like field with up to 6 layers of options allowing the " -"selection of multiple values. Does not allow setting a default value." +#: ../system/integrations/i-doit.rst:118 +msgid "``https://your.zammad.domain``" msgstr "" -#: ../system/objects/types.rst:302 -msgid "External Data Source field" +#: ../system/integrations/index.rst:2 +msgid "Integrations" msgstr "" -#: ../system/objects/types.rst:186 +#: ../system/integrations/index.rst:4 msgid "" -"Provides a searchable field which fetches data from an external system. This " -"can be useful if you have data outside of Zammad and don't want to maintain " -"both data sources." +"Zammad offers numerous integrations that add rich features to your instance." msgstr "" -#: ../system/objects/types.rst:190 -msgid "The feature works as follows:" +#: ../system/integrations/index.rst:6 +msgid "We're still working on this part of our documentation, stay tight!" msgstr "" -#: ../system/objects/types.rst:192 -msgid "" -"Zammad sends a query with a search string (free text from agent or based on " -"a variable) in a pre-defined format (\"Search URL\") to an external system." +#: ../system/integrations/index.rst:10 +msgid "Integrations for Phone Systems" msgstr "" -#: ../system/objects/types.rst:195 +#: ../system/integrations/index.rst:14 msgid "" -"This external system searches for matches and provides a response as a JSON " -"structure to Zammad." +"Your VoIP provider or telephony system is not listed? Possibly your provider " +"supports Zammad by using the generic CTI - if you're unsure ask your " +"provider." msgstr "" -#: ../system/objects/types.rst:197 +#: ../system/integrations/index.rst:18 msgid "" -"Zammad just looks for the defined list and value keys, reads the content and " -"displays the value to the user. There is no search on Zammad side." +"Provider does not support Zammad? Consider creating a `feature request in " +"the Zammad Community `_." msgstr "" -#: ../system/objects/types.rst:201 -msgid "" -"The usage of a PostgreSQL database for Zammad is required. In any other " -"case, Zammad will hide the external data source type and you are not able to " -"use it. If you want to use this feature, consider to :docs:`migrate your " -"database `." +#: ../system/integrations/index.rst:31 +msgid "Integrations for Authentication and Customers" msgstr "" -#: ../system/objects/types.rst:205 -msgid "Currently, only ``GET`` is supported as request method." +#: ../system/integrations/index.rst:44 +msgid "Integrations for Monitoring Systems" msgstr "" -#: ../system/objects/types.rst:206 -msgid "" -"The data structure must be in JSON format and provide the objects in an " -"array." +#: ../system/integrations/index.rst:46 +msgid "This section currently misses the following integrations:" msgstr "" -#: ../system/objects/types.rst:208 -msgid "" -"The endpoint for the external data source has to support search. On Zammad " -"side, there is no search/logic implemented; however, you can define the " -"output key and value based on the result(s) from the response (which " -"provides already filtered content based on the search)." +#: ../system/integrations/index.rst:48 +msgid "Icinga" msgstr "" -#: ../system/objects/types.rst:212 -msgid "" -"If you receive more results as expected, your external data source search " -"may not work properly or the structure of the URL is not correct. You should " -"get in touch with a responsible person from the external system." +#: ../system/integrations/index.rst:49 +msgid "Monit" msgstr "" -#: ../system/objects/types.rst:217 -msgid "" -"Please have a look :doc:`at our example `, where you can find a possible configuration for a public " -"dummy endpoint." +#: ../system/integrations/index.rst:50 +msgid "Nagios" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for external data source fields" +#: ../system/integrations/index.rst:60 +msgid "Integrations for Issue Trackers" msgstr "" -#: ../system/objects/types.rst:242 -msgid "Search URL" +#: ../system/integrations/index.rst:70 +msgid "Other Integrations" msgstr "" -#: ../system/objects/types.rst:227 +#: ../system/integrations/index.rst:72 msgid "" -"Set your endpoint where Zammad fetches the data. Please make sure to include " -"a valid search :doc:`variable <../variables>` as an URL parameter. Example " -"for a free text search at user input: ``#{search.term}``" +"This section will hold any other integration that can't be grouped up (yet)." msgstr "" -#: ../system/objects/types.rst:232 -msgid "" -"If in doubt, ask the responsible person for the external data source how " -"they expect the strucuture of the URL." +#: ../system/integrations/ldap/index.rst:2 +msgid "LDAP / Active Directory" msgstr "" -#: ../system/objects/types.rst:236 +#: ../system/integrations/ldap/index.rst:4 msgid "" -"Depending on your search variable, the preview might work or not. The reason " -"is that the context might not be available and it is no bug." +"Zammad comes with a powerful LDAP integration that allows you to have a " +"single source of truth. By this you reduce the number of login credentials " +"your user has to remember." msgstr "" -#: ../system/objects/types.rst:239 +#: ../system/integrations/ldap/index.rst:10 msgid "" -"Please also make sure to use a variable which is available in your object " -"context. For example you won't be able to search for a ticket in a user " -"object context." -msgstr "" - -#: ../system/objects/types.rst:252 -msgid "SSL Verification" +"The LDAP source is also a perfect candidate for Zammad's :docs:`Kerberos " +"Single Sign-On ` but also works as addition " +"to other :doc:`/settings/security/third-party`." msgstr "" -#: ../system/objects/types.rst:245 -msgid "Here you can switch the SSL verification to no." +#: ../system/integrations/ldap/index.rst:None +msgid "Zammands LDAP management page" msgstr "" -#: ../system/objects/types.rst:249 -msgid "" -"If your external data source system is using self signed certificates, " -"please have a look :doc:`here ` for " -"further information about how to handle them in Zammad, so you can keep the " -"SSL verification activated." +#: ../system/integrations/ldap/index.rst:25 +msgid "📝 :doc:`manage`" msgstr "" -#: ../system/objects/types.rst:258 -msgid "HTTP Authentication" +#: ../system/integrations/ldap/index.rst:25 +msgid "Add, modify, remove or re-arrange your LDAP-Sources as needed." msgstr "" -#: ../system/objects/types.rst:255 -msgid "" -"If your external data source requires an authentication, you can set it " -"here. You can leave it empty or choose between *Basic Authentication* or " -"*Authentication Token* (selecting one of the two methods leads to additional " -"fields where you can enter your credentials/token)." +#: ../system/integrations/ldap/index.rst:30 +msgid "Before you continue, please note the following limitations." msgstr "" -#: ../system/objects/types.rst:265 -msgid "Search result list key" +#: ../system/integrations/ldap/index.rst:32 +msgid "Mapping / Synchronizing organizations is not possible" msgstr "" -#: ../system/objects/types.rst:261 +#: ../system/integrations/ldap/index.rst:36 msgid "" -"Defines the level in the JSON structure which provides the list with search " -"results. You can leave it empty, if the data is already provided as an " -"array. If you have to go deeper in the structure, you can provide a path " -"with ``.`` as separators, e.g. ``key.subkey.sub-sub-key``." -msgstr "" - -#: ../system/objects/types.rst:271 -msgid "Search result value key" +"You may want to consider using domain based assignments to overcome this " +"issue. Learn more on :doc:`/manage/organizations/index`." msgstr "" -#: ../system/objects/types.rst:268 +#: ../system/integrations/ldap/index.rst:39 msgid "" -"Defines the attribute in the structure in which your external data source " -"provides the *value* for your data. An example would be a product *number*. " -"If you have to go deeper in the structure, you can provide a path with ``.`` " -"as separators, e.g. ``key.subkey.sub-sub-key``." +"Zammad's LDAP sync is one way. Editing user settings or permissions may be " +"overwritten upon the next sync depending on your configuration." msgstr "" -#: ../system/objects/types.rst:277 -msgid "Search result label key" +#: ../system/integrations/ldap/index.rst:41 +msgid "Nested groups are not supported." msgstr "" -#: ../system/objects/types.rst:274 -msgid "" -"Defines the attribute in the structure in which your external data source " -"provides the *label* for your data. An example would be a product *name*. If " -"you have to go deeper in the structure, you can provide a path with ``.`` as " -"separators, e.g. ``key.subkey.sub-sub-key``." +#: ../system/integrations/ldap/index.rst:42 +msgid "Synchronizing user avatars from LDAP is not supported." msgstr "" -#: ../system/objects/types.rst:280 -msgid "" -"In the preview area, you can find the following items (depending on your " -"configuration above):" +#: ../system/integrations/ldap/index.rst:43 +msgid "Unlike user filters, group filters cannot be changed." msgstr "" -#: ../system/objects/types.rst:283 +#: ../system/integrations/ldap/index.rst:44 msgid "" -"**Error/hint message** (only if configuration is not complete): Zammad tells " -"you, if there is a problem and what you should change in your configuration." +"When a user originates from an LDAP server, Zammad will try to verify the " +"login credentials against LDAP first - if this fails Zammad will check its " +"local database." msgstr "" -#: ../system/objects/types.rst:286 +#: ../system/integrations/ldap/index.rst:50 msgid "" -"**Search field**: search for an existing attribute in the data source to get " -"a preview. This is required for the fields below to show up." +"Users can have local passwords even if they're LDAP users! You can learn " +"more about user accounts in general on :doc:`/manage/users/index`." msgstr "" -#: ../system/objects/types.rst:288 +#: ../system/integrations/ldap/index.rst:54 msgid "" -"**Search result response** (only if configuration is not complete): here you " -"can find a syntax highlighted JSON preview of the response, based on the " -"search term you entered." +"When several LDAP sources contain the same user (meaning the same email " +"address), the user in question will be updated with every source configured. " +"*The last LDAP source will win.*" msgstr "" -#: ../system/objects/types.rst:291 +#: ../system/integrations/ldap/index.rst:58 msgid "" -"**Search result list** (only if *search result list key* is properly set): " -"output of the structure under the configured *search result list key*." +"This is subject to change with `Issue 4109 `_ in the future." msgstr "" -#: ../system/objects/types.rst:294 +#: ../system/integrations/ldap/index.rst:60 msgid "" -"**Preview table** (when fully configured): Zammad shows you a table which " -"includes the found items based on the search string (value, label and " -"optional link). You can use this preview if you don't have the complete data " -"structure of the external system in mind." +"Synchronization statistics currently affect *all* configured LDAP sources. " +"This also applies for newly added or updated sources." msgstr "" -#: ../system/objects/types.rst:299 +#: ../system/integrations/ldap/index.rst:63 msgid "" -"An example of a configured external data source field from agent perspective:" +"This is subject to change with `Issue 4108 `_ in the future." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Screencast showing the search for a product in a ticket" +#: ../system/integrations/ldap/index.rst:65 +msgid "" +"Zammad currently has limited fallback server support. You can workaround " +"this by providing several sources - however, ensure to have the exact same " +"configuration on your fallback." msgstr "" -#: ../system/objects/types.rst:307 -msgid "URL fields (Link-Template)" +#: ../system/integrations/ldap/index.rst:69 +msgid "" +"This is subject to improve with `Issue 4107 `_ in the future." msgstr "" -#: ../system/objects/types.rst:311 +#: ../system/integrations/ldap/index.rst:76 msgid "" -"This function is restricted to Text, Select and External data source types " -"only." +"This section holds all requests Zammad handled for all LDAP sources. These " +"entries can either contain synchronization information or logins " +"(authentication attempts via Zammad's login interface)." msgstr "" -#: ../system/objects/types.rst:314 +#: ../system/integrations/ldap/index.rst:80 msgid "" -"Link-Templates are an amazing way to dynamically generate URLs. They allow " -"you to integrate other systems better without having to manually copy data " -"from Zammad if possible." +"By clicking on any request, Zammad will provide even more information. The " +"provided information can be useful when something does not work as expected." msgstr "" -#: ../system/objects/types.rst:320 +#: ../system/integrations/ldap/index.rst:85 msgid "" -"Another great way of communicating with another system may be Zammad's :doc:" -"`Webhooks `." +"Especially a LDAP synchronization can cause many log entries. The web " +"interface will always limit the number of shown entries to the last 50 " +"entries." msgstr "" -#: ../system/objects/types.rst:323 +#: ../system/integrations/ldap/index.rst:None msgid "" -"After filling a link-template enabled field, an URL icon will appear on its " -"right. Clicking on the icon opens a new tab." +"Screencast showing LDAP integration log entries and a detail view on\n" +"an entry." msgstr "" -#: ../system/objects/types.rst:328 -msgid "" -"Even though Zammad displays the link template within object edit and create " -"screens, the function is optional. It's only active if you populate the " -"field." +#: ../system/integrations/ldap/manage.rst:2 +msgid "Manage LDAP-Sources" msgstr "" -#: ../system/objects/types.rst:333 +#: ../system/integrations/ldap/manage.rst:6 msgid "" -"What's the difference between URL and text fields with link template...?!" +"Please keep in mind all current limitations for the LDAP synchronization. " +"This will help to understand scopes of the following operations better." msgstr "" -#: ../system/objects/types.rst:335 -msgid "" -"Both fields have different use cases. Use ``text`` type text fields when " -"ever you have a *static* url that requires dynamic parameters. If you " -"require a drag & drop like field that you can put in any URL, use ``URL`` " -"type text fields." +#: ../system/integrations/ldap/manage.rst:65 +msgid "Add new source" msgstr "" -#: ../system/objects/types.rst:340 +#: ../system/integrations/ldap/manage.rst:10 msgid "" -"The difference is easier to spot when comparing the fields directly, below " -"screencast shows the result - the dynamic approach uses existing values in " -"the moment of updating to built the URL - e.g. ``https://google.com/search?" -"q=cookies`` - while the URL approach uses the actual URL of the field - e.g. " -"``https://zammad.com``." +"Using the *New Source* button allows you to add new LDAP sources to your " +"installation. You're not limited in the number of sources, however, keep in " +"mind that many sources will also take more time to synchronize." msgstr "" -#: ../system/objects/types.rst:None +#: ../system/integrations/ldap/manage.rst:14 msgid "" -"Screencast showing the differents in between URL and text type fields with " -"actual values" +"You can choose between different encryption types, namely *SSL* and " +"*STARTTLS* or none of them (\"*No SSL*\"). If you choose *SSL* or " +"*STARTTLS*, Zammad will display an additional *SSL verification* option that " +"allows you to disable the verification, e.g. for self-signed SSL " +"certificates. You can also tell Zammad to use a different port by appending " +"``:`` to your hostname/IP." msgstr "" -#: ../system/objects/types.rst:352 -msgid "How does this work...?!" +#: ../system/integrations/ldap/manage.rst:0 +msgid "" +"Screenshot of configuring a new LDAP source with SSL encryption and SSL " +"verification" msgstr "" -#: ../system/objects/types.rst:354 +#: ../system/integrations/ldap/manage.rst:26 msgid "" -"As an example, let's say you have an attribute called ``amazing_attribute`` " -"and you want to open a google search directly with the input from that field." +"New Source with SSL transport security enabled and certificate verification" msgstr "" -#: ../system/objects/types.rst:357 +#: ../system/integrations/ldap/manage.rst:30 msgid "" -"Providing the link-template field below allows you to do so: ``https://www." -"google.com/search?q=#{ticket.amazing_attribute}``" +"Using an user filter can be a good idea if you only require a small subset " +"of your LDAP users in Zammad." msgstr "" -#: ../system/objects/types.rst:362 -msgid "" -"You can use any :doc:`Zammad variable ` as long as it's " -"available in the moment you need it." +#: ../system/integrations/ldap/manage.rst:42 +msgid "This especially affects inactive users" msgstr "" -#: ../system/objects/types.rst:365 +#: ../system/integrations/ldap/manage.rst:34 msgid "" -"As a result, you are redirected to Google with a search for the value of the " -"attribute, if you click on the button in the ticket (as you can see in the " -"screencast above)." +"As every LDAP behaves differently on which attributes and how they are set, " +"Zammad doesn't care about any flags." msgstr "" -#: ../system/packages.rst:2 -msgid "Packages" +#: ../system/integrations/ldap/manage.rst:37 +msgid "" +"Users that no longer are returned by your LDAP source will automatically be " +"set to inactive. Zammad assumes that the user was deactivated." msgstr "" -#: ../system/packages.rst:4 -msgid "That's the package management-area." +#: ../system/integrations/ldap/manage.rst:41 +msgid "" +"Users will never be removed automatically! If you want to remove obsolete " +"users, use :doc:`/system/data-privacy`." msgstr "" -#: ../system/packages.rst:6 -msgid "Individual add-ons for Zammad can be installed and managed here." +#: ../system/integrations/ldap/manage.rst:46 +msgid "Active Directory admins" msgstr "" -#: ../system/sessions.rst:2 -msgid "Sessions" +#: ../system/integrations/ldap/manage.rst:45 +msgid "" +"Active Directories are quite specific on how to filter for active users only " +"- please see the `Microsoft documentation `_ for more " +"information." msgstr "" -#: ../system/sessions.rst:4 +#: ../system/integrations/ldap/manage.rst:51 msgid "" -"Sessions management allows reviewing currently known user sessions and " -"allows to end these. The session timeout is affected by :ref:" -"`security_session_timeout` configurations from security settings." +"*Do not* manually write pathes of either LDAP attributes or groups. If " +"Zammad does not display them, it either cannot find them or you have a lot " +"of users that don't have the attributes populated." msgstr "" -#: ../system/sessions.rst:None -msgid "Screenshot showing Zammad's session management" +#: ../system/integrations/ldap/manage.rst:55 +msgid "" +"Zammad will always only return attributes that are filled - this reduces the " +"returned list of attributes greatly." msgstr "" -#: ../system/sessions.rst:13 -msgid "Zammad will provide the following information:" +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing how to add a new LDAP source" msgstr "" -#: ../system/sessions.rst:16 +#: ../system/integrations/ldap/manage.rst:63 msgid "" -"The user account this session entry belongs to. It can be normal if a user " -"has several sessions in the list. This can be due to changed browser " -"information or if you use e.g. single sign on methods where the user does " -"not use the log off button." +"If your LDAP system doesn't allow anonymous bind, Zammad detects it and " +"provides you an editable \"Base DN\" *text* field instead of a prefilled " +"*select* field." msgstr "" -#: ../system/sessions.rst:22 -msgid "Browser" +#: ../system/integrations/ldap/manage.rst:81 +msgid "Review or edit existing source" msgstr "" -#: ../system/sessions.rst:22 -msgid "The browser agent communicated to Zammad." +#: ../system/integrations/ldap/manage.rst:68 +msgid "" +"Clicking on a LDAP source will provide a configuration and mapping overview." msgstr "" -#: ../system/sessions.rst:40 -msgid "Location" +#: ../system/integrations/ldap/manage.rst:70 +msgid "" +"If needed you can then use the *Change* button to update either the name, " +"active state or the whole configuration. If you're changing the whole " +"configuration, the dialogue will be identical to the source creation." msgstr "" -#: ../system/sessions.rst:25 +#: ../system/integrations/ldap/manage.rst:76 msgid "" -"The anticipated location based on the users IP address. Depending on the IP " -"address the result shown may differ. This option depends on :doc:`/settings/" -"system/services`." +"Did your LDAP server change? Different LDAP servers have different " +"structures and default attributes. This causes the LDAP synchronization to " +"likely fail. Consider removing the affected source and re-add it." msgstr "" -#: ../system/sessions.rst:29 -msgid "The following information can be shown:" +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing the update of the source name." msgstr "" -#: ../system/sessions.rst:33 -msgid "IP address" +#: ../system/integrations/ldap/manage.rst:89 +msgid "Re-arrange LDAP source's order" msgstr "" -#: ../system/sessions.rst:32 +#: ../system/integrations/ldap/manage.rst:84 msgid "" -"Either if you set *Geo IP services* to inactive or you're using internal IP " -"address which do not provide location information." +"You can change the synchronization order for each source at any time. Zammad " +"will synchronize the sources from top to bottom." msgstr "" -#: ../system/sessions.rst:40 -msgid "Country (or Country + City)" +#: ../system/integrations/ldap/manage.rst:0 +msgid "" +"Screencasting showing how to change the source order by using\n" +"drag and drop." msgstr "" -#: ../system/sessions.rst:36 +#: ../system/integrations/ldap/manage.rst:101 +msgid "Remove a source" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:92 msgid "" -"If *Geo IP services* is enabled only. Depends on how detailed the available " -"IP address information are." +"If you no longer need the a LDAP source or simply want to start over, you " +"can remove them at any time. This will not remove synchronized users, data " +"synchronized or permissions." msgstr "" -#: ../system/sessions.rst:39 +#: ../system/integrations/ldap/manage.rst:98 msgid "" -"Be aware that results can be inaccurate - this technically is not an error." +"Not sure if you'd need the source later on? Set the source to inactive " +"instead of removing it - see *Review or edit existing source* for more." msgstr "" -#: ../system/sessions.rst:43 -msgid "Age" +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing how to remove LDAP sources." msgstr "" -#: ../system/sessions.rst:43 -msgid "Provides the time when the session initially has been created." +#: ../system/integrations/pgp/index.rst:2 +msgid "PGP" msgstr "" -#: ../system/sessions.rst:50 -msgid "Update" +#: ../system/integrations/pgp/index.rst:7 +msgid "" +"Pretty Good Privacy (PGP) is another method for secure email communication. " +"With PGP, you can exchange **signed** and **encrypted** messages with others." msgstr "" -#: ../system/sessions.rst:46 -msgid "" -"Provides the time the user used this session to open Zammad. This timestamp " -"is only updated if the user e.g. reloads, not during normal work on tickets." +#: ../system/integrations/pgp/index.rst:13 +#: ../system/integrations/smime/index.rst:17 +msgid "Signing" msgstr "" -#: ../system/sessions.rst:50 -msgid "This timestamp is being used for the session timeout." +#: ../system/integrations/pgp/index.rst:11 +msgid "is a proof that a message hasn't been manipulated on its way." msgstr "" -#: ../system/sessions.rst:53 +#: ../system/integrations/pgp/index.rst:13 msgid "" -"Use the delete button to remove a single session on behalf of your user." +"In other words, it guarantees message **integrity** and **authenticity**." msgstr "" -#: ../system/subscription/billing.rst:2 -msgid "Billing" +#: ../system/integrations/pgp/index.rst:19 +#: ../system/integrations/smime/index.rst:22 +msgid "Encryption" msgstr "" -#: ../system/subscription/billing.rst:4 +#: ../system/integrations/pgp/index.rst:16 +#: ../system/integrations/smime/index.rst:20 msgid "" -"Within the billing tab you can control all billing relevant information like " -"invoices, billing address and the option to cancel your subscription." -msgstr "" - -#: ../system/subscription/billing.rst:33 -msgid "Billing information" +"scrambles a message so that it can only be unscrambled by the intended " +"recipient." msgstr "" -#: ../system/subscription/billing.rst:8 +#: ../system/integrations/pgp/index.rst:19 msgid "" -"All adjusted billing information below only affect future invoices. If your " -"invoice was issued wrong, please contact `our sales team `_." +"In other words, it guarantees message **privacy** and **data security**." msgstr "" -#: ../system/subscription/billing.rst:14 -msgid "Billing address" +#: ../system/integrations/pgp/index.rst:25 +msgid "Screenshot of ticket creation with encrypt and sign buttons" msgstr "" -#: ../system/subscription/billing.rst:13 +#: ../system/integrations/pgp/index.rst:25 msgid "" -"Provide your company address here, make sure to include the companies name " -"in case required. This address will be referenced on your invoice." +"Once PGP has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " +"appear in the ticket composer." msgstr "" -#: ../system/subscription/billing.rst:18 -msgid "VAT ID" +#: ../system/integrations/pgp/index.rst:28 +msgid "**Sign button not visible?**" msgstr "" -#: ../system/subscription/billing.rst:17 +#: ../system/integrations/pgp/index.rst:30 msgid "" -"Provide your VAT ID here. If applicable your invoice will not contain German " -"VAT. Please make sure to pay the VAT in your country as required." +"Please note that the signing of emails is based on the outgoing email " +"account. That means you have to choose a group with a sender email account, " +"which has a private key assigned." msgstr "" -#: ../system/subscription/billing.rst:27 -msgid "Billing Email Address" +#: ../system/integrations/pgp/index.rst:35 +msgid "Handling of Keys" msgstr "" -#: ../system/subscription/billing.rst:21 +#: ../system/integrations/pgp/index.rst:36 msgid "" -"Usually the instance owner (the person that registered the instance) will " -"receive all emails including the invoices. In case you have your own billing " -"department, you can provide their email address here." +"To use the PGP function, you have to enable the integration (PGP) by " +"switching the toggle to *enabled*." msgstr "" -#: ../system/subscription/billing.rst:25 +#: ../system/integrations/pgp/index.rst:39 msgid "" -"All billing relevant information will then be sent to this email address." +"You can add keys by clicking the *add key* button. The keys can be imported " +"from a file or you can paste the content of the key in the text box." msgstr "" -#: ../system/subscription/billing.rst:27 -msgid "Invoices are sent as attachment (PDF) to this email address." +#: ../system/integrations/pgp/index.rst:42 +msgid "**Which keys do I have to import?**" msgstr "" -#: ../system/subscription/billing.rst:29 +#: ../system/integrations/pgp/index.rst:44 msgid "" -"Don't forget to press the *Submit* button after you changed above settings." +"For **signing** *outgoing* emails, you have to import the private key of " +"your Zammad email account." msgstr "" -#: ../system/subscription/billing.rst:0 +#: ../system/integrations/pgp/index.rst:47 msgid "" -"Screenshot showing options for billing information within the\n" -"subscription menu" -msgstr "" - -#: ../system/subscription/billing.rst:70 -msgid "Payment history" +"For **encrypting** *outgoing* emails, you have to import the public key of " +"the customer's email account." msgstr "" -#: ../system/subscription/billing.rst:36 +#: ../system/integrations/pgp/index.rst:50 msgid "" -"The payment history will display a history of all paid invoices. At this " -"point you can also download these in case you need them again." +"For **verifying the signature** of signed *incoming* emails, you have to " +"import the public key of the customer." msgstr "" -#: ../system/subscription/billing.rst:41 +#: ../system/integrations/pgp/index.rst:53 msgid "" -"You will only find *paid* invoices here. Invoices that are to be billed are " -"not available before the payment is completed." +"For **decrypting** of encrypted *incoming* emails, you have to import the " +"private key of your Zammad email account." msgstr "" -#: ../system/subscription/billing.rst:46 -msgid "Date" +#: ../system/integrations/pgp/index.rst:57 +msgid "Import Keys From a File" msgstr "" -#: ../system/subscription/billing.rst:46 -msgid "Date of the invoice creation." +#: ../system/integrations/pgp/index.rst:58 +msgid "You can import keys from a file in the section **Upload key**:" msgstr "" -#: ../system/subscription/billing.rst:49 -msgid "Amount" +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of adding a key via file" msgstr "" -#: ../system/subscription/billing.rst:49 -msgid "Invoice total including VAT if applicable." +#: ../system/integrations/pgp/index.rst:64 +msgid "" +"**Supported file formats:** ASCII-armor as well as binary GPG format " +"(basically any GPG supported key format) is supported here." msgstr "" -#: ../system/subscription/billing.rst:52 -msgid "" -"Contains contract period (monthly or yearly) and hosted plan for the " -"subscription period in question." +#: ../system/integrations/pgp/index.rst:68 +msgid "Import Keys by Pasting the Content" msgstr "" -#: ../system/subscription/billing.rst:63 -msgid "Payment method / Service period" +#: ../system/integrations/pgp/index.rst:69 +msgid "You can also paste the key's content in the section **paste key**:" msgstr "" -#: ../system/subscription/billing.rst:56 -msgid "" -"Used bank account or credit card as well as the subscription period the " -"invoice is about." +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of adding a key via pasting" msgstr "" -#: ../system/subscription/billing.rst:61 +#: ../system/integrations/pgp/index.rst:75 msgid "" -"It might happen that the invoice date and subscription period differ. This " -"is nothing to worry about, the subscription periods will be accounted later " -"on." +"**Supported format:** Please note that only ASCII-armor is supported here." msgstr "" -#: ../system/subscription/billing.rst:67 -msgid "Receipt" +#: ../system/integrations/pgp/index.rst:78 +msgid "Deleting Keys" msgstr "" -#: ../system/subscription/billing.rst:66 +#: ../system/integrations/pgp/index.rst:79 msgid "" -"Use the arrow to download the invoice in question. You can download all " -"available invoices any time you need to here!" +"If you want to delete a specific key, you can do it by clicking on the menu " +"in the *actions* column and select **delete**:" msgstr "" -#: ../system/subscription/billing.rst:0 -msgid "Screenshot showing payment history of a hosted instance" +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of deleting a key" msgstr "" -#: ../system/subscription/billing.rst:94 -msgid "Do you want to cancel your subscription?" +#: ../system/integrations/pgp/index.rst:88 +msgid "Downloading Keys" msgstr "" -#: ../system/subscription/billing.rst:73 +#: ../system/integrations/pgp/index.rst:89 msgid "" -"In case you no longer want to use Zammad's SaaS, you can cancel your " -"subscription by using the red *Yes, please cancel my subscription* button." +"If you want to download your keys, you can do this as well via corresponding " +"action buttons. Depending on the key, you can choose wether you want to " +"download the private or the public key." msgstr "" -#: ../system/subscription/billing.rst:76 -msgid "" -"Your subscription will end the day after your trial or billing period ends." +#: ../system/integrations/pgp/index.rst:95 +#: ../system/integrations/smime/manage-certificates.rst:76 +msgid "Default Behavior" msgstr "" -#: ../system/subscription/billing.rst:80 +#: ../system/integrations/pgp/index.rst:96 msgid "" -"We will remind you about your cancelled subscription several times up front. " -"After the subscription ended all instance data will be removed. A restore " -"*is not* possible after that point!" +"Here you can adjust on per group basis, if *sign* and *encryption* is on or " +"off by default. Please be aware, that agents can always override the setting " +"for each individual article." msgstr "" -#: ../system/subscription/billing.rst:0 -msgid "Screencast showing how to cancel a subscription" +#: ../system/integrations/pgp/index.rst:None +msgid "Adjusting default behavior on per group basis" msgstr "" -#: ../system/subscription/billing.rst:87 -msgid "**😖 Cancelled by accident?**" +#: ../system/integrations/pgp/index.rst:107 +msgid "" +"Here you can see the last actions regarding signing and encryption and if " +"they were successful." msgstr "" -#: ../system/subscription/billing.rst:89 -msgid "" -"You can always undo the cancellation via the *Yes, undo the cancellation of " -"my subscription* button up to the last subscription day!" +#: ../system/integrations/pgp/index.rst:117 +msgid "**Sign button is not visible, but keys are imported.**" +msgstr "" + +#: ../system/integrations/pgp/index.rst:115 +msgid "Did you choose a group in the ticket?" msgstr "" -#: ../system/subscription/billing.rst:0 +#: ../system/integrations/pgp/index.rst:116 msgid "" -"Screenshot showing a red button to cancel the subscription\n" -"cancellation" +"Did you import a private key for the email adress, which is used for " +"outgoing emails in the group?" msgstr "" -#: ../system/subscription/index.rst:2 -msgid "Subscription (SaaS)" +#: ../system/integrations/pgp/index.rst:122 +msgid "**How to obtain keys?**" msgstr "" -#: ../system/subscription/index.rst:4 +#: ../system/integrations/pgp/index.rst:120 msgid "" -"The subscription settings page allows you to configure your instances " -"package and number of agents required." +"You can create them yourself! There are some good tutorials on the web on " +"how to create them. Providing keys to Zammad is a prerequisite to use the " +"PGP feature." msgstr "" -#: ../system/subscription/index.rst:9 -msgid "" -"This setting section is only available for Hosted setups. If you're looking " -"for on premise support contracts, please see the `Zammad pricing page " -"`_." +#: ../system/integrations/pgp/index.rst:127 +msgid "**It says a passphrase is needed, but I haven't got one.**" msgstr "" -#: ../system/subscription/index.rst:20 +#: ../system/integrations/pgp/index.rst:125 msgid "" -"The subscription section currently consists of two tabs: Plan & Billing. For " -"your overview we've divided those two tabs into independent sub pages:" +"If the key is secured with a passphrase, you have to provide it for the " +"import in Zammad. It is possible that keys may have an empty passphrase. " +"However, this is *not* recommended." msgstr "" -#: ../system/subscription/index.rst:25 -msgid ":doc:`💰 Subscription plan `" +#: ../system/integrations/pgp/index.rst:132 +msgid "**How do my customers get my new key?**" msgstr "" -#: ../system/subscription/index.rst:24 +#: ../system/integrations/pgp/index.rst:130 msgid "" -"Everything affecting your instance subscription functions like number of " -"agents, package and payment method." +"You have to provide your **public** key in advance. Your customer also has " +"to configure PGP in their email workflow and import your public key. The " +"other way round, you have to get the public key of your customer and have to " +"import it to Zammad." +msgstr "" + +#: ../system/integrations/slack.rst:2 +msgid "Slack" msgstr "" -#: ../system/subscription/index.rst:28 -msgid ":doc:`🧾 Subscription billing `" +#: ../system/integrations/slack.rst:4 +msgid "**⚠️ Deprecation warning ⚠️**" msgstr "" -#: ../system/subscription/index.rst:28 +#: ../system/integrations/slack.rst:6 msgid "" -"Everything regarding billing address, invoices and account cancellation." +"Zammad 7 will no longer support this dedicated Slack integration. It is " +"recommended to switch to :doc:`pre-defined webhooks ` instead. Existing Slack integrations should " +"be migrated manually before this feature is dropped." msgstr "" -#: ../system/subscription/index.rst:33 -msgid "FAQ" +#: ../system/integrations/slack.rst:14 +msgid "" +"In order to use this feature, please add a new Slack app to your Workspace. " +"The App you need is called ``Incoming WebHooks`` ." msgstr "" -#: ../system/subscription/index.rst:37 -msgid "I set up a trial account but am missing functions to test" +#: ../system/integrations/slack.rst:18 +msgid "Why Do I Need This Feature?" msgstr "" -#: ../system/subscription/index.rst:36 +#: ../system/integrations/slack.rst:20 msgid "" -"The trial instance is running within the professional package allowing up to " -"three agents." +"If you're already using Slack for your team communication, you'll love this " +"feature! Our Slack integration can push ticket notifications about the last " +"ticket article based on the following events:" msgstr "" -#: ../system/subscription/index.rst:40 -msgid "Can I change package within the trial?" +#: ../system/integrations/slack.rst:24 +msgid "on Ticket creation" msgstr "" -#: ../system/subscription/index.rst:40 -msgid "No. As soon as the package is changed the subscription begins." +#: ../system/integrations/slack.rst:25 +msgid "on Ticket updates" msgstr "" -#: ../system/subscription/index.rst:45 -msgid "What happens to my trial instance after the trial period ended?" +#: ../system/integrations/slack.rst:26 +msgid "on reached reminders" msgstr "" -#: ../system/subscription/index.rst:43 -msgid "" -"Your instance will automatically be canceled for you. Please see *What " -"happens to my instance after it has been canceled?* for more." +#: ../system/integrations/slack.rst:27 +msgid "a Ticket has escalated" msgstr "" -#: ../system/subscription/index.rst:58 -msgid "What happens to my instance after it has been canceled?" +#: ../system/integrations/slack.rst:28 +msgid "a Ticket is going to escalate" msgstr "" -#: ../system/subscription/index.rst:48 -msgid "That depends slightly on your instance state:" +#: ../system/integrations/slack.rst:30 +msgid "" +"Zammad will provide the Ticket title, a direct link to the Ticket, the event " +"type (creation, updated, escalation), the customer, time and the last " +"article that has triggered the notification." msgstr "" -#: ../system/subscription/index.rst:54 -msgid "Trial instance" +#: ../system/integrations/slack.rst:34 +msgid "" +"This will give you further options, as you can see e.g. escalating tickets " +"that are assigned to an agent that's e.g. absent. You can interact faster, " +"as you might see problems earlier (or even before the problem gets one)." msgstr "" -#: ../system/subscription/index.rst:51 +#: ../system/integrations/slack.rst:38 msgid "" -"If you're still on trial, we will ice your instance and remind you once " -"again about your instance. We then will wait some days and remove your " -"instance from our system. This is the last time we will inform you by Email." +"If needed and wanted, you can even discuss directly about the topic before " +"sending an answer to the customer. Another possible use case would be a " +"agent monitoring new agents and their answers to tickets." msgstr "" -#: ../system/subscription/index.rst:58 -msgid "Paid instance" -msgstr "" +#: ../system/integrations/slack.rst:44 +#, fuzzy +msgid "Configure the Integration" +msgstr "Konfiguracija chat widgeta" -#: ../system/subscription/index.rst:57 +#: ../system/integrations/slack.rst:46 msgid "" -"If you're a paying customer and canceled your subscription, the instance " -"removal will take place the day after your last subscription day." +"First of all, please go to your slack workspace - go to administration => " +"Manage Apps. If you don't have an app yet, you can simply add a new one - " +"just search for ``Incoming WebHooks`` and customize the app to your needs." msgstr "" -#: ../system/subscription/index.rst:60 -msgid "Can removed instances be restored?" +#: ../system/integrations/slack.rst:50 +msgid "" +"Choose (or create) the channel Zammad should post it's information to and " +"press on \"Add Incoming WebHooks integration\". If you're ready, copy the " +"provided WebHook URL and go to your Zammad installation." msgstr "" -#: ../system/subscription/index.rst:61 -msgid "No. Once your instance has been removed, a restoration is not possible." +#: ../system/integrations/slack.rst:56 +msgid "" +"You need administrative rights on the Slack Workspace. The link to the app " +"directory is normally ``https://[workspace-name].slack.com/apps`` ." msgstr "" -#: ../system/subscription/plan.rst:2 ../system/subscription/plan.rst:38 -msgid "Plan" +#: ../system/integrations/slack.rst:63 +msgid "" +"To configure the slack integration, log in to Zammad and go to Integrations " +"(System) => Slack in the admin panel." msgstr "" -#: ../system/subscription/plan.rst:16 -msgid "Subscription" +#: ../system/integrations/slack.rst:66 +msgid "" +"Here you can choose on what evens Zammad should post information about a " +"ticket to your Slack channel. Next you need to device what groups shall be " +"affected by this, as anybody with access to that specific Slack channel can " +"read at least parts of the ticket this might be a privacy issue, if you " +"select the wrong groups. The username is simply the name that Zammad uses as " +"display name inside the Slack chat. The channel defines the Slack channel " +"the information is being posted in. As last option, you can set a custom " +"icon for posting to slack." msgstr "" -#: ../system/subscription/plan.rst:5 +#: ../system/integrations/slack.rst:74 msgid "" -"On the top of the subscription summary you'll find the number of used and " -"available (booked) agent seats. By using the *see more* link you can also " -"expand an agent list to see the currently configured active agents. This " -"list *does not* count accounts with admin permissions only." +"When you're ready, just hit \"Submit\" and enable the integration. Zammad " +"will now post new ticket information based on the trigger you chose. Below " +"the options you have the recent log that shows the latest requests to Slack " +"for debugging if needed." msgstr "" -#: ../system/subscription/plan.rst:0 +#: ../system/integrations/slack.rst:81 msgid "" -"Within subscription you can always see how many agents are still\n" -"available to add and who uses the seats." +"If you leave the Icon URL empty, Zammad will use the Zammad logo instead. " +"The icon should be a square PNG file." msgstr "" -#: ../system/subscription/plan.rst:14 +#: ../system/integrations/slack.rst:90 msgid "" -"Learn more on how to manage your agents in general :doc:`here `." +"The following figure shows how it will look if you choose to receive updates " +"on created and updated tickets. On every post Zammad sends to the Slack " +"channel, you can create new threads to discuss about the new article." msgstr "" -#: ../system/subscription/plan.rst:19 +#: ../system/integrations/slack.rst:96 msgid "" -"This section gives you an overview of the available plans and their " -"functions / limits. If you require a more detailed table, check our " -"`detailed pricing table `_ for more." +"If you just want to keep track of soon escalating or already escalated " +"tickets, it will look the the following figure. Zammad changes the color in " +"front of the post so you can easily see the state of the ticket." msgstr "" -#: ../system/subscription/plan.rst:23 +#: ../system/integrations/slack.rst:102 msgid "" -"Your selection in this step will decide on the base agent price and e.g. " -"agent limits that might apply in the summary step." +"If you change the state, Zammad will also put information on what state the " +"ticket gets and (if pending state) the date until it pends. You'll also " +"recognize the color codes in front of posts on slack, as they are exact the " +"same the ticket state colors you'll see in Zammad!" msgstr "" -#: ../system/subscription/plan.rst:26 -msgid "" -"The green *Selected* button will also tell you what plan you're currently in." +#: ../system/integrations/smime/index.rst:2 +msgid "S/MIME" msgstr "" -#: ../system/subscription/plan.rst:30 +#: ../system/integrations/smime/index.rst:11 msgid "" -"Trial instances are running at Professional with 3 agents. The plan cannot " -"be changed during the trial for technical reasons, if you require more " -"agents for testing, please contact `our sales team `_ with a reason for the raise request." +"S/MIME is the most widely-supported method for secure email communication. " +"With S/MIME, you can exchange **signed** and **encrypted** messages with " +"others." msgstr "" -#: ../system/subscription/plan.rst:0 +#: ../system/integrations/smime/index.rst:15 msgid "" -"Screenshot showing three available packages for a hosted Zammad\n" -"instance" +"is proof that a message hasn't been tampered with or sent by an impersonator." msgstr "" -#: ../system/subscription/plan.rst:83 -msgid "Summary" +#: ../system/integrations/smime/index.rst:17 +msgid "" +"In other words, it guarantees a message's **integrity** and **authenticity**." msgstr "" -#: ../system/subscription/plan.rst:41 -msgid "" -"In this section you can adjust the settings of the previous selected plan." +#: ../system/integrations/smime/index.rst:22 +msgid "In other words, it guarantees **privacy** and **data security**." msgstr "" -#: ../system/subscription/plan.rst:45 -msgid "" -"Note that upgrading (more agents, higher package) is always possible, " -"however, downgrading will only happen when your billing period renews." +#: ../system/integrations/smime/index.rst:28 +msgid "Screencast demo of S/MIME features for both new tickets and replies" msgstr "" -#: ../system/subscription/plan.rst:49 +#: ../system/integrations/smime/index.rst:28 msgid "" -"Upgrading resets your billing period and existing credit will be deducted " -"from the new total." +"Once S/MIME has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " +"appear in the ticket composer." msgstr "" -#: ../system/subscription/plan.rst:58 -msgid "Billing cycle" +#: ../system/integrations/smime/index.rst:32 +msgid ":doc:`🔪 Prerequisites `" msgstr "" -#: ../system/subscription/plan.rst:53 +#: ../system/integrations/smime/index.rst:31 msgid "" -"You can choose between either monthly or yearly billing. The price per agent " -"will be cheaper if you decide for yearly billing." +"New to S/MIME? This section helps you to find certificate providers and " +"points out Limitations." msgstr "" -#: ../system/subscription/plan.rst:56 -msgid "" -"If you're still trying out things and are unsure of the right package for " -"your instance, you may want to choose monthly first and then upgrade to " -"yearly when you're sure." +#: ../system/integrations/smime/index.rst:35 +msgid ":doc:`📝 Manage Certificates `" msgstr "" -#: ../system/subscription/plan.rst:66 -msgid "Plan: (Starter|Professional|Plus) - Agents" +#: ../system/integrations/smime/index.rst:35 +msgid "Add and download certificates; configure group default behaviors." msgstr "" -#: ../system/subscription/plan.rst:61 -msgid "Choose the number of agents you require for your instance." +#: ../system/integrations/smime/index.rst:38 +msgid ":doc:`😦 Troubleshooting `" msgstr "" -#: ../system/subscription/plan.rst:63 -msgid "" -"Keep in mind that some packages may have agent limits. Depending on the " -"previous chosen package, you won't be able to exceed specific agent numbers. " -"Also note that setting less agents than currently configured is not possible." +#: ../system/integrations/smime/index.rst:38 +msgid "Took a wrong turn? About recent logs and common issues." msgstr "" -#: ../system/subscription/plan.rst:69 -msgid "Total" +#: ../system/integrations/smime/index.rst:43 +msgid "" +"For more details on how S/MIME integration works on the agent side, see the :" +"user-docs:`user docs `." msgstr "" -#: ../system/subscription/plan.rst:69 -msgid "This will be the net total you're going to be billed." +#: ../system/integrations/smime/manage-certificates.rst:2 +msgid "Manage Certificates" msgstr "" -#: ../system/subscription/plan.rst:71 +#: ../system/integrations/smime/manage-certificates.rst:4 msgid "" -"By using the *Update subscription* button, the instance package will be " -"adjusted immediately. If you didn't provide a payment method yet, Zammad " -"will request you to provide one at this point." +"S/MIME is **disabled by default**. Enable it to start adding certificates." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:10 +msgid "Dialogue to add new certificates or private keys" msgstr "" -#: ../system/subscription/plan.rst:77 +#: ../system/integrations/smime/manage-certificates.rst:10 msgid "" -"In case you're still within the trial period, this means that the trial will " -"be over immediately!" +"Manage certificates in the Admin Panel under **System > Integrations > S/" +"MIME**. Certificates may be pasted in as plain text or uploaded from a file." msgstr "" -#: ../system/subscription/plan.rst:80 -msgid "Down- or upgrading during the trial period *is not* possible." +#: ../system/integrations/smime/manage-certificates.rst:14 +msgid "Add Certificate Data" msgstr "" -#: ../system/subscription/plan.rst:0 -msgid "Screenshot showing payment options and a pricing summary" +#: ../system/integrations/smime/manage-certificates.rst:36 +msgid "Add Certificate" msgstr "" -#: ../system/subscription/plan.rst:99 -msgid "Payment method" +#: ../system/integrations/smime/manage-certificates.rst:17 +msgid "" +"Import public-key certificates for both your own organization and your " +"contacts." msgstr "" -#: ../system/subscription/plan.rst:86 -msgid "You can pay via credit card or SEPA mandate." +#: ../system/integrations/smime/manage-certificates.rst:19 +msgid "" +"You can also add a bunch of certificates in one go by providing a single " +"file with all relevant certificates." msgstr "" -#: ../system/subscription/plan.rst:91 -msgid "Credit card" +#: ../system/integrations/smime/manage-certificates.rst:22 +msgid "🕵️ **ALWAYS verify certificates in-person or over the phone!**" msgstr "" -#: ../system/subscription/plan.rst:89 +#: ../system/integrations/smime/manage-certificates.rst:24 msgid "" -"Simply follow the dialogue by clicking *authorize* and confirm -if required " -"by your bank- your consent to Zammad using your card for the payments." +"The whole point of signatures is to alert you when someone is trying to " +"pretend to be someone they're not. Never accept a certificate from someone " +"online without verifying it first." msgstr "" -#: ../system/subscription/plan.rst:95 -msgid "SEPA" +#: ../system/integrations/smime/manage-certificates.rst:28 +msgid "📇 **What about trusted certificate authorities?**" msgstr "" -#: ../system/subscription/plan.rst:94 +#: ../system/integrations/smime/manage-certificates.rst:30 msgid "" -"Provide the requested information of the bank account holder and update if " -"you're ready. You'll then receive an email with the SEPA mandate." +"In some cases (e.g. when dealing with large enterprises), you may be given a " +"certificate for an entire CA, rather than a single contact. Add it here to " +"trust *all* certificates issued by that CA." msgstr "" -#: ../system/subscription/plan.rst:97 +#: ../system/integrations/smime/manage-certificates.rst:35 msgid "" -"Technically there's also the possibility to pay via invoice, however - this " -"method only applies to a fairly low number of instances. Please contact `our " -"sales team `_ for more information." +"Commercial CAs can usually be verified online. Zammad does not include a " +"list of built-in, trusted CAs." msgstr "" -#: ../system/translations.rst:2 -msgid "Translations" +#: ../system/integrations/smime/manage-certificates.rst:57 +msgid "Add Private Key" msgstr "" -#: ../system/translations.rst:4 +#: ../system/integrations/smime/manage-certificates.rst:39 msgid "" -"Translations of Zammad are processed centrally in our `Weblate instance " -"`_. This allows non-developers to review " -"and update translation texts of the language they actually speak." +"Once you've added a public-key certificate, you can import its matching " +"private key." msgstr "" -#: ../system/translations.rst:9 +#: ../system/integrations/smime/manage-certificates.rst:42 msgid "" -"Your language is in an incomplete translation state or has typos? Please " -"consider helping us in sorting this out! All you need is either a GitHub " -"account or to register directly in our instance." +"Private keys are for **your own organization only**; never ask your contacts " +"for their private keys." msgstr "" -#: ../system/translations.rst:13 +#: ../system/integrations/smime/manage-certificates.rst:0 msgid "" -"Did you know? This is also where the documentation translations are handled. " -"🤓" +"S/MIME integration showing configured certificates and possible issues with " +"Logging" msgstr "" -#: ../system/translations.rst:15 +#: ../system/integrations/smime/manage-certificates.rst:50 msgid "" -"Have a look in our :docs:`contribution section ` in the system documentation to get started!" +"A note is displayed on certificates with a matching private key (see line 2)." msgstr "" -#: ../system/translations.rst:20 -msgid "Local Translations" +#: ../system/integrations/smime/manage-certificates.rst:52 +msgid "📤 **Certificates and private keys must be uploaded separately.**" msgstr "" -#: ../system/translations.rst:22 +#: ../system/integrations/smime/manage-certificates.rst:54 msgid "" -"Apart from these system translations, there's still local translations you " -"can manage. This is relevant if you added custom objects that require " -"translations or even custom states and priorities." +"If your certificate and private key are bundled together in the same file or " +"PEM block, import it twice (once using each button)." msgstr "" -#: ../system/translations.rst:None -msgid "Translation management screen within the admin menu" +#: ../system/integrations/smime/manage-certificates.rst:57 +msgid "Please note that bulk imports of private keys are not possible." msgstr "" -#: ../system/translations.rst:31 -msgid "Updating Translations" +#: ../system/integrations/smime/manage-certificates.rst:60 +msgid "Download Certificate Data" msgstr "" -#: ../system/translations.rst:33 +#: ../system/integrations/smime/manage-certificates.rst:62 msgid "" -"Because of how Zammad ships translations, the only way to update the system " -"translations is to update your Zammad installation. The benefit of this is " -"that you no longer need internet access during a Zammad upgrade as the " -"package has everything it requires already." +"You can download the earlier provided certificates and private keys at any " +"time from your Zammad instance." msgstr "" -#: ../system/translations.rst:39 -msgid "Translation of Custom Objects" +#: ../system/integrations/smime/manage-certificates.rst:65 +msgid "" +"Please note that passphrase-protected private keys stay protected and when " +"you download them, you have to know the passphrase to use them after " +"downloading." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:73 +msgid "Dialogue to download certificates or private keys" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:73 +msgid "Download stored certificates and their keys" msgstr "" -#: ../system/translations.rst:41 +#: ../system/integrations/smime/manage-certificates.rst:78 msgid "" -"No problem at all! You can customize any translation locally, even if it is " -"not initially provided by the system." +"The ticket composer will set all outgoing messages to **signed and " +"encrypted** by default (assuming the required certificates exist)." msgstr "" -#: ../system/translations.rst:44 -msgid "" -"Translation is supported for a broad number of features, including but not " -"limited to custom:" +#: ../system/integrations/smime/manage-certificates.rst:82 +msgid "These defaults can be modified on a per-group basis:" msgstr "" -#: ../system/translations.rst:47 -msgid "Object Attributes" +#: ../system/integrations/smime/manage-certificates.rst:None +msgid "Zammad allowing to choose the default behavior on per group basis" msgstr "" -#: ../system/translations.rst:48 -#, fuzzy -msgid "Ticket Macros" -msgstr "Makro-naredbe" - -#: ../system/translations.rst:49 -msgid "Ticket Overviews" +#: ../system/integrations/smime/manage-certificates.rst:89 +msgid "" +"Of course, agents can always manually change these settings on each email " +"they send out." msgstr "" -#: ../system/translations.rst:50 -#, fuzzy -msgid "Ticket Priorities" -msgstr "prioritet" +#: ../system/integrations/smime/prerequisites.rst:4 +msgid "A certificate *and* private key for your own organization" +msgstr "" -#: ../system/translations.rst:51 -msgid "Ticket States" +#: ../system/integrations/smime/prerequisites.rst:6 +msgid "" +"(Use this to ✒️ **sign outgoing messages** and 🔓 **decrypt incoming " +"messages**.)" msgstr "" -#: ../system/translations.rst:54 -msgid "Customizing Translations" +#: ../system/integrations/smime/prerequisites.rst:9 +msgid "" +"Certificates belonging your contacts, or their issuing certificate authority " +"(CA)" msgstr "" -#: ../system/translations.rst:56 +#: ../system/integrations/smime/prerequisites.rst:11 msgid "" -"Within the translation screen, simply click on the **New Translation** " -"button." +"(Use these to ✅ **verify incoming message signatures** and 🔒 **encrypt " +"outgoing messages**.)" msgstr "" -#: ../system/translations.rst:None -#, fuzzy -msgid "New translation dialog" -msgstr "Dodavanje novog e-mail računa" +#: ../system/integrations/smime/prerequisites.rst:14 +msgid "🙋 **I'm new to S/MIME. Where can I get a certificate?**" +msgstr "" -#: ../system/translations.rst:62 +#: ../system/integrations/smime/prerequisites.rst:16 msgid "" -"In the dialog you can immediately enter the exact translation source (if you " -"know it) and your custom translation text for it and click **Submit**." +"The easiest way to get certificates is to buy an annual subscription through " +"a commercial CA, such as:" msgstr "" -#: ../system/translations.rst:65 +#: ../system/integrations/smime/prerequisites.rst:19 msgid "" -"Alternatively, try to search for translation suggestions in the list below. " -"Selecting an item from the list will pre-fill the translation source for you " -"and then you can just enter your custom translation." +"`Sectigo (formerly Comodo) `_" msgstr "" -#: ../system/translations.rst:69 -msgid "" -"The target language will always default to your current language selection. " -"If you need to translate for a different language, simply change the " -"selection before submitting." +#: ../system/integrations/smime/prerequisites.rst:20 +msgid "`Secorio `_" msgstr "" -#: ../system/translations.rst:73 -msgid "" -"All your custom translations will show up in the overview table when added. " -"And they will even persist across Zammad updates!" +#: ../system/integrations/smime/prerequisites.rst:21 +msgid "`GlobalSign `_" msgstr "" -#: ../system/translations.rst:76 -msgid "" -"Make sure to reload your browser if a translated string is not displayed." +#: ../system/integrations/smime/prerequisites.rst:23 +msgid "(Zammad is not affiliated with these CAs in any way.)" msgstr "" -#: ../system/translations.rst:80 -msgid "Reverting to Original Translations" +#: ../system/integrations/smime/prerequisites.rst:25 +msgid "" +"You can also generate your own self-signed certificates, but the process is " +"complicated and usually 🙅 **involves extra work for your contacts**." msgstr "" -#: ../system/translations.rst:82 +#: ../system/integrations/smime/prerequisites.rst:29 msgid "" -"If you want to revert a custom translation to original text, simply use the " -"appropriate action within the row of the overview table." +"Bear in mind that 🤝 **S/MIME only works if the other party is using it, too." +"**" msgstr "" -#: ../system/translations.rst:85 +#: ../system/integrations/smime/prerequisites.rst:32 +msgid "Certificate and Private Key Checks on Upload" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:34 msgid "" -"Depending on the type of the translation source, the action has a slightly " -"different name:" +"The certificate and public key validation is based on the ``X509v3`` " +"extensions." msgstr "" -#: ../system/translations.rst:88 -msgid "**Reset** for customized system translations" +#: ../system/integrations/smime/prerequisites.rst:49 +msgid "Uploading a *client certificate*?" msgstr "" -#: ../system/translations.rst:89 -msgid "**Remove** for customized local translations" +#: ../system/integrations/smime/prerequisites.rst:41 +msgid "The following attributes are required then:" msgstr "" -#: ../system/translations.rst:91 -msgid "" -"In both cases, the action will remove the customized translation after a " -"confirmation." +#: ../system/integrations/smime/prerequisites.rst:39 +msgid "Subject Alternative Name (at least one email address has to be present)" msgstr "" -#: ../system/translations.rst:None -msgid "Screenshot showing the location of the Remove action" +#: ../system/integrations/smime/prerequisites.rst:40 +msgid "Key Usage (``Digital Signature`` and/or ``Key Encipherment``)" msgstr "" -#: ../system/translations.rst:99 -msgid "Inline Translations" +#: ../system/integrations/smime/prerequisites.rst:41 +msgid "Public key algorithm (either ``RSA`` or ``EC``)" msgstr "" -#: ../system/translations.rst:101 +#: ../system/integrations/smime/prerequisites.rst:43 msgid "" -"If you prefer a more hands-on approach, you can activate the inline or on-" -"screen translation feature by pressing ``ctrl`` + ``alt`` + ``t`` at any " -"time and on any screen." +"The Extended Key Usage attribute is optional. If the certificate provides " +"the named attribute, than it must contain the value ``E-mail Protection``." msgstr "" -#: ../system/translations.rst:105 +#: ../system/integrations/smime/prerequisites.rst:46 msgid "" -"All customizable translation texts will be highlighted for you on the " -"screen. Just click into the highlighted area and update the text in place." +"Please note that any usable email adress has to be prefixed with ``email:`` " +"or ``rfc822:``." msgstr "" -#: ../system/translations.rst:None -msgid "Inline translation mode activated for the Overview screen" +#: ../system/integrations/smime/prerequisites.rst:49 +msgid "The named public key algorithms are mandatory for private keys as well." msgstr "" -#: ../system/translations.rst:112 +#: ../system/integrations/smime/prerequisites.rst:54 +msgid "Uploading a *CA certificate*?" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:52 msgid "" -"When finished editing, simply press ``ctrl`` + ``alt`` + ``t`` again to " -"deactivate." +"In the case of an uploaded CA certificate, providing the value ``CA:TRUE`` " +"in the attribute *Basic Contstraints*, the previously mentioned attributes " +"are not verified." msgstr "" -#: ../system/translations.rst:117 +#: ../system/integrations/smime/prerequisites.rst:56 msgid "" -"Even though it's available on any screen, the inline translation feature " -"requires admin permissions. It works only for the current language " -"selection. If you need to translate a different language, first change the " -"language in your :user-docs:`profile settings `." +"In general, the usage of any expired (``Not After``) or not yet valid (``Not " +"Before``) certificate is denied for outgoing emails." msgstr "" -#: ../system/variables.rst:2 -msgid "Variables" +#: ../system/integrations/smime/prerequisites.rst:59 +msgid "Example certificate:" msgstr "" -#: ../system/variables.rst:4 +#: ../system/integrations/smime/prerequisites.rst:85 msgid "" -"Please note that this is just an overview of available variables. It might " -"be incomplete or variables might not be available within some functions. If " -"you're missing variables or are not sure if something is not working as " -"expected, feel free to ask over at the `Community `_." +"Please note that Zammad will distrust senders by default. This means that " +"you're always required to provide certificate data, no matter if for signing " +"or encrypting." msgstr "" -#: ../system/variables.rst:10 -msgid "" -"Variables can be called by typing ``::`` (just like text modules in the " -"frontend), as long as you're in a supported text field within the backend. " -"Zammad will display all variables being available within this context and " -"replace it to the variable as soon as you selected an entry." +#: ../system/integrations/smime/prerequisites.rst:89 +msgid "This is by design and can't be adjusted." msgstr "" -#: ../system/variables.rst:15 +#: ../system/integrations/smime/troubleshooting.rst:4 msgid "" -"You have an empty field which you referenced and it appears as ``-``? That's " -"currently working as designed - you might want to ensure that these fields " -"always have a value." +"All of the system's latest S/MIME activity is displayed in the **Recent " +"Logs** section." msgstr "" -#: ../system/variables.rst:20 -msgid "Variable Categories" +#: ../system/integrations/smime/troubleshooting.rst:11 +msgid "Sample entries of in- and outgoing S/MIME related emails." msgstr "" -#: ../system/variables.rst:31 -msgid "Wait, What About Custom Objects?" +#: ../system/integrations/smime/troubleshooting.rst:11 +msgid "" +"Logs report the status and details of all mail, both incoming and outgoing, " +"that used signing/verification or encryption/decryption." msgstr "" -#: ../system/variables.rst:33 +#: ../system/integrations/smime/troubleshooting.rst:14 msgid "" -"Good point! Of course, we can't predict what objects you might create, but " -"we can give you a hint on how to put the puzzle together to get your custom " -"values." +"This log does **not** include email sent by :doc:`triggers ` or the :doc:`scheduler `. For those, check your " +"``production.log``." msgstr "" -#: ../system/variables.rst:36 -msgid "" -"For this, we'll talk about the inner part of the variable (so everything " -"within ``#{}``), please put the outer part around to have a valid variable. " -"The first part of the variable name consist of the object type. Currently " -"these are:" +#: ../system/integrations/smime/troubleshooting.rst:20 +msgid "Common Issues" msgstr "" -#: ../system/variables.rst:41 -msgid "Ticket (``ticket``)" +#: ../system/integrations/smime/troubleshooting.rst:30 +msgid "I received a signed/encrypted email before I set up S/MIME integration" msgstr "" -#: ../system/variables.rst:42 -msgid "User (``user``)" +#: ../system/integrations/smime/troubleshooting.rst:23 +msgid "" +"No problem. Once S/MIME has been enabled and the appropriate certificates " +"have been added, agents will be prompted to retry verification/decryption on " +"matching emails." msgstr "" -#: ../system/variables.rst:43 -msgid "Organization (``organization``)" +#: ../system/integrations/smime/troubleshooting.rst:0 +msgid "Screenshot of user prompt to retry decryption" msgstr "" -#: ../system/variables.rst:44 -msgid "Group (``group``)" +#: ../system/integrations/smime/troubleshooting.rst:38 +msgid "The 🔒 **Encrypt** button is disabled" msgstr "" -#: ../system/variables.rst:46 -msgid "" -"The second part is the name of the object. This is the name you define " -"during object creation and can be found within the object menu at any time. " -"The first and second part of a variable is divided by a point, e.g.: " -"``ticket.number`` which will in total be ``#{ticket.number}``." +#: ../system/integrations/smime/troubleshooting.rst:33 +msgid "Have you added the recipient's certificate?" msgstr "" -#: ../system/variables.rst:51 -msgid "" -"Now, in some situations it's possible that you'll need to use a third part. " -"The best example for such a situation would be a ``select`` or ``tree-" -"select`` field which will by default return the key value, not it's display " -"name. For this, just extend your variable with ``.value``. This will result " -"in ``#{ticket.select.value}``." +#: ../system/integrations/smime/troubleshooting.rst:34 +msgid "Are you sure the recipient's certificate is valid?" msgstr "" -#: ../system/variables.rst:60 -msgid "Using Translated Variables" +#: ../system/integrations/smime/troubleshooting.rst:35 +msgid "Have you checked your ``production.log`` for more details?" msgstr "" -#: ../system/variables.rst:62 +#: ../system/integrations/smime/troubleshooting.rst:37 msgid "" -"If you want to use a translated variable in triggers or schedulers, you can " -"extend the placeholder like this: ``#{t(ticket.state.name)}``. The ``t`` " -"tells Zammad to search for fitting translated strings. The used output " -"language is based on the system language of Zammad which you can set in the " -"admin panel under :doc:`/settings/branding` or based on the selected locale " -"in the trigger/scheduler edit dialog." +"If encryption doesn't work in the composer, it won't work in :doc:`triggers " +"` or the :doc:`scheduler ` either!" msgstr "" -#: ../system/variables.rst:69 -msgid "" -"A possible use-case: you want to send your customers updates on tickets via " -"trigger or scheduler which should include the state of the ticket. Using the " -"default ``#{ticket.state.name}`` (without the translation flag ``t()``) " -"would lead to the output of the original (english) name of the state." +#: ../system/integrations/smime/troubleshooting.rst:42 +msgid "The ✅ **Sign** button is disabled" msgstr "" -#: ../system/variables.rst:75 -msgid "Date and Time Formatting" +#: ../system/integrations/smime/troubleshooting.rst:41 +msgid "" +"Have you added **both the certificate and private key** for your " +"organization?" msgstr "" -#: ../system/variables.rst:77 +#: ../system/integrations/smime/troubleshooting.rst:42 msgid "" -"The system (trigger/scheduler selected) locale and timezone predefines a " -"default format of date and timestamp. This format is customizable by using " -"the ``dt()`` method." +"Does the email address on the certificate match the email address of the " +"agent/group composing the email?" msgstr "" -#: ../system/variables.rst:79 -msgid "The method arguments are as follows:" +#: ../system/integrations/smime/troubleshooting.rst:45 +msgid "Error: “Fingerprint already taken”" msgstr "" -#: ../system/variables.rst:81 -msgid "The date or timestamp variable you want to format." +#: ../system/integrations/smime/troubleshooting.rst:45 +msgid "Are you sure you haven't added this certificate already?" msgstr "" -#: ../system/variables.rst:82 -msgid "The output format string." +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Error: “❌ invalid byte sequence in UTF-8”" msgstr "" -#: ../system/variables.rst:83 -msgid "The timezone to apply (optional)." +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Please ensure to provide PEM formatted certificate and keys." msgstr "" -#: ../system/variables.rst:86 -msgid "" -"``#{dt(ticket.updated_at, \"%A %Y-%m-%d %H:%M in the office\", \"Europe/" -"Berlin\")}``" +#: ../system/integrations/smime/troubleshooting.rst:49 +msgid "Did you check if the provided file is a valid certificate or key?" msgstr "" -#: ../system/variables.rst:87 -msgid "Monday, 2024-03-18 15:31 in the office" +#: ../system/integrations/zabbix.rst:2 +msgid "Zabbix Integration" msgstr "" -#: ../system/variables.rst:89 +#: ../system/integrations/zabbix.rst:5 msgid "" -"If you want to use our example, make sure to paste the string above without " -"formatting (``CTRL+Shift+v``), otherwise it won't work." +"This guide describes how to integrate your Zabbix 5.4 installation with " +"Zammad using the Zabbix webhook feature. This guide will provide " +"instructions on setting up a media type, a user and an action in Zabbix." msgstr "" -#: ../system/variables.rst:93 -msgid "The following table lists available format directives:" +#: ../system/integrations/zabbix.rst:12 +msgid "Zammad with enabled HTTP Token Authentication" msgstr "" -#: ../system/variables.rst:99 -msgid "Parameter" +#: ../system/integrations/zabbix.rst:13 +msgid "Zabbix version 5.4 or higher" msgstr "" -#: ../system/variables.rst:102 -msgid "``%Y``" +#: ../system/integrations/zabbix.rst:16 +msgid "Setting up a Zammad" msgstr "" -#: ../system/variables.rst:103 -msgid "Year with 4 digits" +#: ../system/integrations/zabbix.rst:18 +msgid "Enable **API Token Access** in Settings > System > API." msgstr "" -#: ../system/variables.rst:104 -msgid "Use ``%y`` for year with 2 digits" +#: ../system/integrations/zabbix.rst:20 +msgid "" +"Create a **new user** for a Zabbix alerter with an **email address** and " +"create a personal user token with **ticket.agent** permissions." msgstr "" -#: ../system/variables.rst:105 -msgid "``%m``" +#: ../system/integrations/zabbix.rst:24 +msgid "Zabbix Webhook Configuration" msgstr "" -#: ../system/variables.rst:106 -msgid "Month of year (as number with zero-padding)" -msgstr "" +#: ../system/integrations/zabbix.rst:27 +#, fuzzy +msgid "Create a Global Macro" +msgstr "Makro-naredbe" -#: ../system/variables.rst:107 -msgid "Use ``%-m`` for month without zero-padding" +#: ../system/integrations/zabbix.rst:29 +msgid "" +"Before setting up the **Webhook**, you need to setup the global macro " +"**{$ZABBIX.URL}**, which must contain the **URL** to the **Zabbix frontend**." msgstr "" -#: ../system/variables.rst:108 -msgid "``%d``" +#: ../system/integrations/zabbix.rst:33 +msgid "" +"In the **Administration** > **Media types** section, import the `Template`_." msgstr "" -#: ../system/variables.rst:109 -msgid "Day of month (as number with zero-padding)" +#: ../system/integrations/zabbix.rst:38 +msgid "Open the added **Zammad** media type and set:" msgstr "" -#: ../system/variables.rst:110 -msgid "Use ``%e`` for day without zero-padding" +#: ../system/integrations/zabbix.rst:40 +msgid "**zammad\\_access\\_token** to the your **Personal User Token**" msgstr "" -#: ../system/variables.rst:111 -msgid "``%H``" +#: ../system/integrations/zabbix.rst:41 +msgid "" +"**zammad\\_url** to the **frontend URL** of your **Zammad** installation" msgstr "" -#: ../system/variables.rst:112 -msgid "Hour of day in 24h notation with zero-padding" +#: ../system/integrations/zabbix.rst:43 +msgid "**zammad\\_customer** to your **Zammad user email**." msgstr "" -#: ../system/variables.rst:113 -msgid "Use ``%k`` for hour without zero-padding" +#: ../system/integrations/zabbix.rst:44 +msgid "" +"**zammad\\_enable\\_tags** to **true** or **false** to enable or disable " +"trigger tags. **Important**: if you enable tag support, each tag is set with " +"a separate request." msgstr "" -#: ../system/variables.rst:114 -msgid "``%I``" +#: ../system/integrations/zabbix.rst:48 +msgid "" +"If you want to prioritize issues according to **severity** values in Zabbix, " +"you can define mapping parameters:" msgstr "" -#: ../system/variables.rst:115 -msgid "Hour of day in 12h notation with zero-padding" +#: ../system/integrations/zabbix.rst:51 +msgid "**severity\\_**: Zammad priority ID" msgstr "" -#: ../system/variables.rst:116 -msgid "" -"Use ``%l`` for hour without zero-padding and ``%p`` / ``%P`` for meridian " -"indicator" +#: ../system/integrations/zabbix.rst:53 +msgid "Click the **Update** button to save the **Webhook** settings." msgstr "" -#: ../system/variables.rst:117 -msgid "``%M``" +#: ../system/integrations/zabbix.rst:55 +msgid "" +"To receive notifications in **Zammad**, you need to create a **Zabbix user** " +"and add **Media** with the **Zammad** type." msgstr "" -#: ../system/variables.rst:118 -msgid "Minute of hour" +#: ../system/integrations/zabbix.rst:58 +msgid "" +"For **Send to**: enter any text, as this value is not used, but is required." msgstr "" -#: ../system/variables.rst:120 -msgid "``%S``" +#: ../system/integrations/zabbix.rst:61 +msgid "" +"For more information, use the `Zabbix documentation `_." msgstr "" -#: ../system/variables.rst:121 -msgid "Second of Minute" +#: ../system/maintenance.rst:2 +msgid "Maintenance" msgstr "" -#: ../system/variables.rst:123 -msgid "``%A``" +#: ../system/maintenance.rst:4 +msgid "" +"Zammad comes with a maintenance mode that you can use for e.g. updating the " +"instance or changing settings while restricting availability and functions." msgstr "" -#: ../system/variables.rst:124 -msgid "Weekday name" +#: ../system/maintenance.rst:13 +msgid "Mode" msgstr "" -#: ../system/variables.rst:125 -msgid "Use ``%a`` for abbreviated name or ``%^A`` for uppercase name" +#: ../system/maintenance.rst:8 +msgid "The mode setting allows you to enable or disable the maintenance mode." msgstr "" -#: ../system/variables.rst:126 -msgid "``%B``" +#: ../system/maintenance.rst:10 +msgid "Defaults to *off*." msgstr "" -#: ../system/variables.rst:127 -msgid "Month name" +#: ../system/maintenance.rst:12 +msgid "" +"The maintenance mode will restrict access to administrative roles only. This " +"means agents and customers are logged off." msgstr "" -#: ../system/variables.rst:128 -msgid "Use ``%b`` for abbreviated name" +#: ../system/maintenance.rst:23 +msgid "@Login" msgstr "" -#: ../system/variables.rst:129 -msgid "``%U``" +#: ../system/maintenance.rst:16 +msgid "" +"This setting allows you to provide a login message within a green banner " +"above the login screen. Click into the green banner in the settings page to " +"adjust your message. To activate the message, activate the *@Login* setting." msgstr "" -#: ../system/variables.rst:130 -msgid "Week number of current year" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing the default login message within the\n" +"settings page" msgstr "" -#: ../system/variables.rst:131 -msgid "Use ``%W`` for a different calculation method" +#: ../system/maintenance.rst:26 +msgid "" +"Send an informative message to **all active sessions**. This comes handy to " +"inform your agents e.g. about mayor outages or to force reloads after " +"configuration changes." msgstr "" -#: ../system/variables.rst:134 -msgid "" -"We support the known format directives for the Ruby built-in method " -"``strftime`` of the ``DateTime`` class. For more information, see `here " -"`_." +#: ../system/maintenance.rst:31 +msgid "This is the messages title (slightly bigger than the normal message)." msgstr "" -#: ../system/variables/article.rst:2 -msgid "Articles" +#: ../system/maintenance.rst:34 +msgid "The text you want to provide to your logged in sessions." msgstr "" -#: ../system/variables/article.rst:4 ../system/variables/config.rst:4 -#: ../system/variables/current-user.rst:4 ../system/variables/ticket.rst:4 -msgid "" -"If you're missing variables or are not sure if something is not working as " -"expected, feel free to ask over at the `Community `_." +#: ../system/maintenance.rst:39 +msgid "Reload application" msgstr "" -#: ../system/variables/article.rst:6 +#: ../system/maintenance.rst:37 msgid "" -"Below you can find all available ticket article-based variables within " -"Zammad. These can be called via Triggers for example. If you're unsure if " -"Zammad does support variables at the point you're at, you can try to type " -"``::`` to check." +"Selecting this option will change the message acceptance button from *Close* " +"(with nothing happening) to *Continue session*, which forces the application " +"to reload." msgstr "" -#: ../system/variables/article.rst:9 ../system/variables/config.rst:9 -#: ../system/variables/ticket.rst:9 +#: ../system/maintenance.rst:43 msgid "" -"The below list gives you an example what kind of data you can expect, it's " -"not intended to explain the data itself." +"If you have customers that are logged in to Zammad, they'll also be notified " +"if they're active in that moment." msgstr "" -#: ../system/variables/article.rst:11 -msgid "Article Variables" +#: ../system/maintenance.rst:48 +msgid "Example without reload application" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "name" +#: ../system/maintenance.rst:52 +msgid "" +"Message setting within Zammad's admin settings without ticket reload " +"application setting." msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "variable" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing the send message settings without ticket\n" +"reload application set" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "example" +#: ../system/maintenance.rst:61 ../system/maintenance.rst:85 +msgid "" +"The modal all other active sessions will see upon pressing *Send to clients*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Web" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing modal caused by maintenance's message\n" +"without reload application ticket" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.web}``" +#: ../system/maintenance.rst:72 +msgid "Example with reload application" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``https://zammad.com`` or empty if not set in user object" +#: ../system/maintenance.rst:76 +msgid "" +"Message setting within Zammad's admin settings with ticket reload " +"application setting." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > VIP" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing the send message settings with ticket\n" +"reload application set" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.vip}``" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing modal caused by maintenance's message\n" +"with reload application ticket" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -msgid "``true`` or ``false``" +#: ../system/monitoring.rst:2 +msgid "Monitoring" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Phone" +#: ../system/monitoring.rst:4 +msgid "" +"This function is only available in self hosted instances. If you use Zammad " +"in our cloud, we are monitoring the system on our own and take steps to fix " +"potential problems directly." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.phone}``" +#: ../system/monitoring.rst:11 +msgid "" +"On the monitoring page, you can see the current health state of Zammad under " +"\"*Current Status*\" at the bottom. This can be useful if you want to have a " +"look if everything is up and running. As an example, you could have a look " +"in the monitoring when you assume that some emails aren't processed from " +"Zammad." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``+4930123456789`` or empty if not set in user object" +#: ../system/monitoring.rst:17 +msgid "**Can't receive an email and the monitoring response is \"healthy\"?**" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Note" +#: ../system/monitoring.rst:19 +msgid "" +"Zammad will just inform you about unprocessable emails. This is not the case " +"for oversized emails. You can adjust the maximum email size in :doc:`../" +"channels/email/settings`." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.note}``" +#: ../system/monitoring.rst:24 +msgid "Monitoring API" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Some note about user`` or empty if not set in user object" +#: ../system/monitoring.rst:26 +msgid "" +"Beside the indication in the monitoring page, you can also use an external " +"monitoring tool to monitor Zammad's health. To request the health of Zammad, " +"you need to provide the API key (token) to the external monitoring tool. You " +"can copy the token from the \"*Current Token*\" field as well as the whole " +"API endpoint of your system (\"*Health Check*\" field), in which the API " +"token is already included." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Mobile" +#: ../system/monitoring.rst:37 +msgid "Screenshot showing Current Token and Health Check" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.mobile}``" +#: ../system/monitoring.rst:37 +msgid "Screenshot showing Token and Health Check" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Login" +#: ../system/monitoring.rst:39 +msgid "" +"In addition to that, you can reset the auto-generated token to make sure " +"that already configured monitoring systems won't work anymore. So, please " +"use this \"*Reset*\" button only if you know what you do!" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.login}``" -msgstr "" +#: ../system/monitoring.rst:44 +#, fuzzy +msgid "Example Output" +msgstr "Primjer" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -#: ../system/variables/ticket.rst:1 -msgid "``jdoe``" +#: ../system/monitoring.rst:0 +msgid "No issues found" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Lastname" +#: ../system/monitoring.rst:48 ../system/monitoring.rst:60 +msgid "**Indicator in Zammad**:" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.lastname}``" +#: ../system/monitoring.rst:0 +msgid "Screenshot showing monitoring with no issues" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -#: ../system/variables/ticket.rst:1 -msgid "``Doe`` or empty if not set" +#: ../system/monitoring.rst:54 ../system/monitoring.rst:66 +msgid "**API response**::" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Firstname" +#: ../system/monitoring.rst:0 +msgid "Issues were found" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.firstname}``" +#: ../system/monitoring.rst:0 +msgid "Screenshot showing monitoring with issues" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "``Joe`` or empty if not set" +#: ../system/objects.rst:2 +msgid "Objects" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Fax" +#: ../system/objects.rst:4 +msgid "" +"In Zammad you can add your own fields to tickets, users, organizations and " +"even groups (these are called \"objects\"). This can be useful if you need " +"to add further information to a ticket or any other object in Zammad and the " +"information doesn't fit in any existing field." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.fax}``" +#: ../system/objects.rst:11 +msgid "" +"Try to avoid deleting attributes (and disable them instead) as Zammad might " +"run into unexpected conditions if they are referenced somewhere." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Email" +#: ../system/objects.rst:16 +msgid "" +"Here's an overview of object attributes. On the upper right you can add new " +"attributes. By default, there will be no custom fields - standard attributes " +"will be grayed out, you can't delete or change those. You can edit custom " +"attributes (they are displayed in black font and have a trash bin on the " +"right side) just by clicking on them." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.email}``" +#: ../system/objects.rst:24 +msgid "" +"Attributes you add to Zammad, no matter if they have default values or not, " +"will not update existing information. This means a new ticket field " +"technically will be empty unless you populate it." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``jdoe@example.com``" +#: ../system/objects.rst:28 +msgid "" +"Especially in ticket scope this also means that newly added attributes will " +"be indicated as \"changed\" to agents that view the ticket. This may " +"interfere with Zammad's tabs behavior." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Department" +#: ../system/objects.rst:40 +msgid "Ordering Attributes" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.department}``" +#: ../system/objects.rst:42 +msgid "" +"Since Zammad introduced :doc:`/system/core-workflows` the need to have a " +"custom positioning for attributes has become more important than ever." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Sales`` or empty if not set in user object" +#: ../system/objects.rst:45 +msgid "" +"To adjust the position of such an attribute, simply click on the attribute " +"entry in question, scroll down and adjust the position number. Please note " +"that you cannot change the positioning of default attributes." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Address" +#: ../system/objects.rst:49 +msgid "" +"In case two attributes have the same position value, Zammad will sort " +"alphabetically by name automatically." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.address}``" +#: ../system/objects.rst:None +msgid "" +"Screenshot showing custom attribute entries ordered in between default ones" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Some street 1, 12345 Berlin`` or empty if not set in user object" +#: ../system/objects.rst:56 +msgid "Updating Database After Adding or Editing Attributes" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated" +#: ../system/objects.rst:58 +msgid "" +"When adding or changing attributes, Zammad will not apply the changes " +"instantly, but instead shows you the changed attributes first. If you're " +"ready to go, just click on \"Update database\" to apply the changes to " +"Zammad. If you made a mistake or just want to discard your changes, click " +"\"Discard changes\"." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_at}``" +#: ../system/objects.rst:64 +msgid "" +"After applying the changes with \"Update Database\", a restart of Zammad is " +"**mandatory**. If you don't perform it, you may experience unexpected " +"behavior or even errors. You may want to do this kind of configuration " +"during maintenance windows." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``2019-10-08 15:24:47 UTC``" +#: ../system/objects.rst:72 +msgid "" +"Changes on objects require you to update the database to apply these changes." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Type > Name" +#: ../system/objects.rst:75 +msgid "**🤓 Service restarts can be automated**" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.type.name}``" +#: ../system/objects.rst:0 +msgid "Hosted environments automatically restart for you." msgstr "" -#: ../system/variables/article.rst:1 +#: ../system/objects.rst:0 msgid "" -"``email`` (`list of article types `_)" +"If you're using a self-hosted installation you can use :docs:`environment " +"variables `" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > To" +#: ../system/objects.rst:82 +msgid "System Attributes" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.to}``" +#: ../system/objects.rst:84 +msgid "" +"Zammad comes with pre-configured attributes. Some of them can't be edited " +"via UI (or at all). This is required for proper operation of Zammad and not " +"a bug." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``helpdesk@example.com``" +#: ../system/objects.rst:90 +msgid "Ticket State" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > TicketID" +#: ../system/objects.rst:92 +msgid "" +"If the pre-configured states aren't enough for you or you want to change " +"them, you can do so by clicking on the cogwheel icon in the state row in the " +"ticket tab. But you should be careful when changing pre-configured states. " +"This can lead to unwanted behavior in some cases." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.ticket_id}``" +#: ../system/objects.rst:None +msgid "Screenshot showing highlighted ticket state attribute" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``1`` (not ticket number)" +#: ../system/objects.rst:122 +msgid "Handling of states" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Subject" +#: ../system/objects.rst:102 +msgid "" +"In the state configuration screen, you can add new states, disable states or " +"change states." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.subject}``" +#: ../system/objects.rst:0 +msgid "Screenshot showing table of default ticket states" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``My amazing subject``" +#: ../system/objects.rst:110 +msgid "" +"To add a new state, click on the \"New Ticket State\" button in the top " +"right corner. To change an existing state, simply click on the affected " +"state. This opens an edit dialog." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Sender > Name" +#: ../system/objects.rst:114 +msgid "" +"You can also clone a state or set them to \"Default for new tickets\" or " +"\"Default for follow-ups\" by clicking on the ⁝ action button and select the " +"desired function." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.sender.name}``" +#: ../system/objects.rst:118 +msgid "" +"*Default for new tickets* means that this state is used for every newly " +"created ticket." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Customer``, ``Agent`` or ``System``" +#: ../system/objects.rst:121 +msgid "" +"*Default for follow-ups* means that this state is used if the ticket is re-" +"opened after it was closed." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Visibility" +#: ../system/objects.rst:171 +msgid "Ticket state in detail" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.internal}``" +#: ../system/objects.rst:125 +msgid "" +"Below you can find a description for each field and option. Please head over " +"to the :ref:`example ` to see the edit dialog." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``false`` or ``true`` (false if not internal)" +#: ../system/objects.rst:129 +msgid "" +"This is the name of the state and what you and your agents are seeing when " +"choosing a state somewhere (e.g. in tickets, trigger configuration)." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > From" +#: ../system/objects.rst:137 +msgid "" +"There are different state types you can choose from. By default, Zammad " +"comes with one state per state type." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.from}``" +#: ../system/objects.rst:140 +msgid "" +"**new**: for states for tickets that are new and it hasn't been worked on " +"them" msgstr "" -#: ../system/variables/article.rst:1 +#: ../system/objects.rst:142 msgid "" -"``Joe Doe `` may differ, depends on ``FROM`` of send mail" +"**open**: for states for tickets that are in progress and agents are working " +"on them" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Web" +#: ../system/objects.rst:144 +msgid "**merged**: for states for tickets that are merged with other tickets" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.web}``" +#: ../system/objects.rst:145 +msgid "" +"**pending reminder**: for states for tickets that are in progress and you " +"want to set a reminder. (default example: *pending reminder*)" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > VIP" +#: ../system/objects.rst:147 +msgid "" +"**pending action**: for states for tickets that are waiting for a specified " +"time and then change their state (default example: *pending close*)" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.vip}``" +#: ../system/objects.rst:150 +msgid "" +"**closed**: for states for tickets that are finished and do not need to be " +"processed further" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Phone" +#: ../system/objects.rst:153 +msgid "" +"⚠️ Choosing the correct state type is important! If you are in doubt, have a " +"look on the default states and their types!" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.phone}``" +#: ../system/objects.rst:158 +msgid "Ignore escalation" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Note" +#: ../system/objects.rst:157 +msgid "" +"Here you can define whether tickets of this state will count to escalation " +"time or not." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.note}``" +#: ../system/objects.rst:161 +msgid "" +"You can create a note for the state to inform other admins about the state. " +"This has no effect on tickets." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Mobile" +#: ../system/objects.rst:165 +msgid "Set the state to *active* or *inactive*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.mobile}``" +#: ../system/objects.rst:167 +msgid "" +"it is technically possible to set all states to inactive. To keep Zammad " +"working in such a case, the inactive flag of one of the states is ignored." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Login" +#: ../system/objects.rst:194 +msgid "Ticket state example" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.login}``" +#: ../system/objects.rst:174 +msgid "" +"Let's assume we want to create a new state which indicates that the ticket " +"has to wait for a response of a third party (e.g. service contractor or " +"manufacturer) and we want to to be able to set a reminder." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Lastname" +#: ../system/objects.rst:178 +msgid "" +"First we give the new state a proper name. In this example we call it " +"\"waiting for manufacturer\"." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.lastname}``" +#: ../system/objects.rst:181 +msgid "" +"As state type we choose \"pending reminder\". This indicates that the ticket " +"is still open and we can set a reminder. This reminder can be useful if our " +"manufacturer sometimes isn't responding or we want to remind him to give us " +"an answer." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Firstname" +#: ../system/objects.rst:186 +msgid "" +"We choose \"no\" for \"ignore escalation\" because we want to escalate the " +"tickets even if we are waiting on the manufacturer's feedback." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.firstname}``" -msgstr "" +#: ../system/objects.rst:189 +#, fuzzy +msgid "The **result** in the creation dialog will look like this:" +msgstr "Krajnji rezultat će izgledati ovako:" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Fax" +#: ../system/objects.rst:0 +msgid "Screenshot showing ticket state creation dialog with example" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.fax}``" -msgstr "" +#: ../system/objects.rst:199 +#, fuzzy +msgid "Ticket Priority" +msgstr "prioritet" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Email" +#: ../system/objects.rst:201 +msgid "" +"If the pre-configured priorities aren't enough for you or you want to change " +"them, you can do so by clicking on the cogwheel icon in the priority row in " +"the ticket tab:" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.email}``" +#: ../system/objects.rst:None +msgid "Screenshot showing highlighted ticket priority attribute" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Department" +#: ../system/objects.rst:226 +msgid "Handling of priorities" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.department}``" +#: ../system/objects.rst:210 +msgid "" +"In the priority configuration screen, you can add new priorities, disable " +"priorities or change priorities." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Address" +#: ../system/objects.rst:0 +msgid "Screenshot showing table of default ticket priorities" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.address}``" +#: ../system/objects.rst:218 +msgid "" +"To add a new priority, click on the \"New Priority\" button in the top right " +"corner. To change an existing priority, simply click on the affected " +"priority. This opens an edit dialog." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created" +#: ../system/objects.rst:222 +msgid "" +"You can also clone a priority or set them to \"Default for new tickets\" by " +"clicking on the ⁝ action button and select the desired function." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_at}``" +#: ../system/objects.rst:225 +msgid "" +"*Default for new tickets* means that this priority is used for every newly " +"created ticket." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Cc" +#: ../system/objects.rst:248 +msgid "Priorities in detail" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.cc}``" +#: ../system/objects.rst:229 +msgid "Below you can find a description for each field and option." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``jdoe@example.com, company@example.com``" +#: ../system/objects.rst:232 +msgid "" +"This is the name of the priority and what you and your agents are seeing " +"when choosing a priority somewhere (e.g. in tickets, trigger configuration)." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Text" +#: ../system/objects.rst:242 +msgid "Highlight color" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.body}``" +#: ../system/objects.rst:237 +msgid "" +"Switch between *Low priority* (light blue), *High priority* (red) and - " +"(default). This affects the displayed color for ticket titles in overviews." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Test`` without formatting (plain)" +#: ../system/objects.rst:241 +msgid "The color options are currently limited to the mentioned options." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article Text as HTML (not referenced)" +#: ../system/objects.rst:245 +msgid "" +"You can create a note for the priority to inform other admins about the " +"priority. This has no effect on tickets." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.body_as_html}``" +#: ../system/objects.rst:249 +msgid "Set the priority to *active* or *inactive*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Test`` with formatting" +#: ../system/objects/external-data-source-example.rst:2 +msgid "External Data Source" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "Ticket > Article#" +#: ../system/objects/external-data-source-example.rst:4 +msgid "" +"We assume you already had a look on :doc:`types` where you can find a " +"description of the individual fields." msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "``#{ticket.article_count}``" +#: ../system/objects/external-data-source-example.rst:7 +msgid "" +"To reproduce this example, choose a category you want to add a custom field, " +"click on *New Attribute* and select *External data source field* under " +"*Format*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``1`` number of ticket articles" +#: ../system/objects/external-data-source-example.rst:11 +msgid "" +"Our example story is to fetch data from an external product database. We " +"want to add our products to the tickets so that the products can be searched " +"and chosen from a list and also create a link to the product website." msgstr "" -#: ../system/variables/config.rst:2 -msgid "Config" +#: ../system/objects/external-data-source-example.rst:16 +msgid "Base configuration" msgstr "" -#: ../system/variables/config.rst:6 -msgid "" -"Below you'll find config related variables. These hold useful configuration " -"information that you can use within e.g. triggers to show necessary " -"information to your customer." +#: ../system/objects/external-data-source-example.rst:None +msgid "Initial steps to configure external data source object type" msgstr "" -#: ../system/variables/config.rst:11 -msgid "Config Variables" +#: ../system/objects/external-data-source-example.rst:25 +msgid "Name: *product*" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Fully Qualified Domain Name" +#: ../system/objects/external-data-source-example.rst:26 +msgid "Display: *Product*" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.fqdn}``" +#: ../system/objects/external-data-source-example.rst:29 +msgid "External data source configuration" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``zammad.example.com``" +#: ../system/objects/external-data-source-example.rst:31 +msgid "" +"First, enter the search URL making sure it contains ``#{search.term}`` as a " +"parameter:" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Ticket Hook" +#: ../system/objects/external-data-source-example.rst:34 +msgid "**Example:** ``https://dummyjson.com/products/search?q=#{search.term}``" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.ticket_hook}``" +#: ../system/objects/external-data-source-example.rst:36 +msgid "" +"After that, head down to the preview section and enter a search input for " +"the external data source." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``Ticket#``" -msgstr "" +#: ../system/objects/external-data-source-example.rst:39 +#, fuzzy +msgid "**Example:** ``mac``" +msgstr "Primjer" -#: ../system/variables/config.rst:1 -msgid "Config > HTTP type" +#: ../system/objects/external-data-source-example.rst:41 +msgid "Then you can find a preview of the response data below:" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.http_type}``" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of JSON response based on search term" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``https`` or ``http``" +#: ../system/objects/external-data-source-example.rst:48 +msgid "" +"We recommend using the preview to have a look on the structure. There is a " +"top-level element called ``products``. One level below, you can find the " +"attributes ``id`` and ``title``." msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > SystemID" +#: ../system/objects/external-data-source-example.rst:52 +msgid "**Search result response based on search from example:**" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.system_id}``" +#: ../system/objects/external-data-source-example.rst:119 +msgid "" +"To tell the remote system that the desired data is located below the " +"``products`` level, you have to put it in the field *Search result list key*." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``31`` (value between 1 and 99)" +#: ../system/objects/external-data-source-example.rst:122 +msgid "" +"After inserting ``products`` in the mentioned field, you get an extended " +"preview. You can find an additional box *Search result list* with a JSON " +"structure. This is the same response as before but stripped from the upper " +"``products`` element by the external data source." msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Organization" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of JSON response search result list" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.organization}``" +#: ../system/objects/external-data-source-example.rst:132 +msgid "" +"Now you need to provide the keys for the search result values and labels. As " +"already mentioned, we are looking for the ``id`` and the ``title`` of our " +"products. If you haven't already, it is now a good time to look at the " +"preview of the *Search result list*." msgstr "" -#: ../system/variables/config.rst:1 +#: ../system/objects/external-data-source-example.rst:197 msgid "" -"``Zammad GmbH`` value set in `Branding `_" +"After locating our two keys, we insert them in *search result value key* " +"(``id``) and in *Search result label key* (``title``)." msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Product Name" +#: ../system/objects/external-data-source-example.rst:200 +msgid "" +"Basically, we configured the external data source already and we can see a " +"table in the preview section:" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.product_name}``" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of product table based on search term" msgstr "" -#: ../system/variables/config.rst:1 +#: ../system/objects/external-data-source-example.rst:208 msgid "" -"``Helpdesk`` value set in `Branding `_" +"According to our example story, now just the *Link template* is missing." msgstr "" -#: ../system/variables/current-user.rst:2 -msgid "Current User" +#: ../system/objects/external-data-source-example.rst:210 +msgid "" +"Please note that this is an optional feature. If you don't want to use such " +"links, of course you don't have to configure it." msgstr "" -#: ../system/variables/current-user.rst:6 +#: ../system/objects/external-data-source-example.rst:213 msgid "" -"Current user variables always return values of the current user that caused " -"e.g. a trigger to run." +"We can add now an address where additional product information can be found." msgstr "" -#: ../system/variables/current-user.rst:8 -msgid "" -"Due to the above fact, these variables are often not (yet) set or available " -"for usage." +#: ../system/objects/external-data-source-example.rst:215 +msgid "Example: ``https://your_domain.com/q=#{ticket.product}``" msgstr "" -#: ../system/variables/current-user.rst:10 -msgid "" -"In situations where e.g. schedulers or triggers run, this most likely is " -"nothing you want to use." +#: ../system/objects/external-data-source-example.rst:217 +msgid "In the example, the parameter means:" msgstr "" -#: ../system/variables/current-user.rst:13 -msgid "Current User Variables" +#: ../system/objects/external-data-source-example.rst:219 +msgid "``#{}``: \"Frame\" for the insertion of information" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Web" +#: ../system/objects/external-data-source-example.rst:220 +msgid "``ticket``: object level, where you create your custom object" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.web}``" +#: ../system/objects/external-data-source-example.rst:221 +msgid "``product``: name of the (custom) object" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``https://zammad.org`` or empty if not set" +#: ../system/objects/external-data-source-example.rst:223 +msgid "" +"After configuring your *Link template*, there will be another column in the " +"preview. Hovering on the icons in the *Link* column will show you where it " +"forwards you." +msgstr "" + +#: ../system/objects/external-data-source-example.rst:232 +msgid "" +"In our example, one of the links looks like: https://your_domain.com/q=6, " +"where the 6 is the product id." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > VIP" +#: ../system/objects/external-data-source-example.rst:235 +#, fuzzy +msgid "You can find more information regarding the URL in :doc:`types`." msgstr "" +"Dodatne informacije o konfiguriranju chata možete pronaći u " +"administratorskoj dokumentaciji." -#: ../system/variables/current-user.rst:1 -msgid "``#{user.vip}``" +#: ../system/objects/includes/adding-values-hint.include.rst:3 +msgid "" +"Adding values can be tricky for first timers, don't forget to press \"➕ " +"Add\" after typing your values. Otherwise you may loose a value." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``false`` or ``true``" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:1 +#: ../system/objects/includes/reposition-values.include.rst:1 +msgid "**↕️ This field type allows the positioning of its values ↔️**" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Web" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:3 +msgid "" +"In order to re-arrange the field values, first edit the field. Then you can " +"use ☰ to drag the values in question to the correct position. If you want to " +"change the layer depth, double click on ☰. With it you can cycle through the " +"available layers." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.web}``" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:8 +msgid "When you're ready, submit your changes to save the object attribute." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > VIP" +#: :0 ../system/objects/types.rst:0 +msgid "" +"Screencast showing how to re-position values on tree select like\n" +"fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.vip}``" +#: ../system/objects/includes/reposition-values.include.rst:3 +msgid "" +"In order to re-arrange the field values, edit the field and scroll below the " +"values. Make sure to tick the option \"Use custom option sort\"." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Phone" +#: ../system/objects/includes/reposition-values.include.rst:8 +msgid "" +"If you do not tick this field, all manual positioning you did above will be " +"lost upon saving! ☠️" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.phone}``" +#: ../system/objects/includes/reposition-values.include.rst:11 +msgid "" +"Now use ☰ to drag the values in question to the correct position. When " +"you're ready, submit your changes to save the object attribute." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``004930123456789`` or empty if not set" +#: :0 ../system/objects/types.rst:0 +msgid "Screencast showing how to re-position values" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Note" +#: ../system/objects/includes/url-template-hint.include.rst:3 +msgid "" +"This field allows using :ref:`URL fields (Link Templates) `." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.note}``" +#: ../system/objects/permissions.rst:2 +msgid "Attribute Permissions" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Some note to this user`` or empty if not set" +#: ../system/objects/permissions.rst:7 +msgid "" +"In the object attributes configuration you can define if a field is shown " +"and if the input in the field is mandatory, separated by different screens " +"and for different :doc:`roles/permissions `." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Mobile" +#: ../system/objects/permissions.rst:17 +msgid "Screenshot shows object attribute permission table" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.mobile}``" +#: ../system/objects/permissions.rst:17 +msgid "" +"Some of the possible permissions and screen options for a user object " +"attribute." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``0049176123456789`` or empty if not set" +#: ../system/objects/permissions.rst:19 +msgid "" +"Based on the object context (ticket, agent, organization, user), the " +"selectable roles (to be precise: the required permissions) and screens " +"differ. Be aware that these settings aren't affecting data creation via " +"other channels than the UI." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Login" +#: ../system/objects/permissions.rst:24 +msgid "" +"If you want to have further customization possibilities, you should have a " +"look at the :doc:`core workflows `." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.login}``" +#: ../system/objects/permissions.rst:28 +msgid "Screens" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Lastname" +#: ../system/objects/permissions.rst:30 +msgid "" +"In the table below you can find an overview about the different permissions " +"and the available screens Zammad distinguishes between." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.lastname}``" +#: ../system/objects/permissions.rst:37 +msgid "Screen" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Firstname" +#: ../system/objects/permissions.rst:38 +msgid "Available for" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.firstname}``" +#: ../system/objects/permissions.rst:40 +msgid "create" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``John`` or empty if not set" +#: ../system/objects/permissions.rst:41 ../system/objects/permissions.rst:52 +#: ../system/objects/permissions.rst:59 ../system/objects/permissions.rst:73 +msgid "admin.user" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Fax" +#: ../system/objects/permissions.rst:42 ../system/objects/permissions.rst:53 +#: ../system/objects/permissions.rst:60 +msgid "admin.organization" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.fax}``" -msgstr "" +#: ../system/objects/permissions.rst:43 ../system/objects/permissions.rst:54 +#: ../system/objects/permissions.rst:61 +#, fuzzy +msgid "admin.group" +msgstr "grupa" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``004930123464789`` or empty if not set" +#: ../system/objects/permissions.rst:44 +msgid "Creation dialog for not yet existing data" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Email" +#: ../system/objects/permissions.rst:45 +msgid "create_middle" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.email}``" -msgstr "" +#: ../system/objects/permissions.rst:46 ../system/objects/permissions.rst:50 +#: ../system/objects/permissions.rst:57 ../system/objects/permissions.rst:66 +#: ../system/objects/permissions.rst:70 +#, fuzzy +msgid "ticket.customer" +msgstr "Makro-naredbe" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``jdoe@customer.tld``" -msgstr "" +#: ../system/objects/permissions.rst:47 ../system/objects/permissions.rst:51 +#: ../system/objects/permissions.rst:58 ../system/objects/permissions.rst:69 +#, fuzzy +msgid "ticket.agent" +msgstr "Makro-naredbe" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Department" +#: ../system/objects/permissions.rst:48 +msgid "Ticket create dialog (middle section)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.department}``" +#: ../system/objects/permissions.rst:49 +msgid "edit" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Sales`` or empty if not set" +#: ../system/objects/permissions.rst:55 +msgid "Editing dialog for already existing data" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Avatar" +#: ../system/objects/permissions.rst:56 +msgid "view" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.avatar(60,60)}``" +#: ../system/objects/permissions.rst:62 +msgid "View-only dialog for already existing data" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "avatar picture with width and height in pixel (e.g. 60,60)" +#: ../system/objects/permissions.rst:64 +msgid "(e.g. user or organization from search)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Address" +#: ../system/objects/permissions.rst:65 +msgid "signup" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.address}``" +#: ../system/objects/permissions.rst:67 +msgid "Sign-up screen for new customers" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Some street 1, 12345 Berlin`` or empty if not set" +#: ../system/objects/permissions.rst:68 +msgid "invite_customer" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated at" +#: ../system/objects/permissions.rst:71 +msgid "" +"Customer invitation screen (from :doc:`First Steps ` area)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_at}``" +#: ../system/objects/permissions.rst:72 +msgid "invite_agent" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC``" +#: ../system/objects/permissions.rst:74 +msgid "" +"Agent invitation screen (from :doc:`First Steps ` area)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Phone" +#: ../system/objects/permissions.rst:78 +msgid "Screen Options" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.phone}``" +#: ../system/objects/permissions.rst:80 +msgid "" +"For the different screens you can select \"show\" and \"required\" options." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Shared organization" +#: ../system/objects/permissions.rst:82 +msgid "**shown:** Show (check) or hide (uncheck) a field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.shared}``" +#: ../system/objects/permissions.rst:83 +msgid "" +"**required:** Set a field to mandatory (check). Forces users (via UI and " +"API) to populate the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Note" +#: ../system/objects/types.rst:7 +msgid "Example external data source" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.note}``" +#: ../system/objects/types.rst:2 +msgid "Attribute types" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``A note to the organization of the user`` or empty if not set" +#: ../system/objects/types.rst:4 +msgid "" +"When adding a new object attribute, you can choose between the following " +"attribute types." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Name" +#: ../system/objects/types.rst:14 +msgid "" +"You cannot change the attribute format / type as soon as it is applied. If " +"you no longer need an object attribute, consider disabling it instead of " +"removing." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.name}``" +#: ../system/objects/types.rst:18 +msgid "**What about the translation of my attributes?**" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``Zammad GmbH``" +#: ../system/objects/types.rst:20 +msgid "" +"For some attribute types you can decide if they should be translatable or " +"not. To be precise, it works only for the selectable fields because the " +"possible choices are known and limited. For the following attribute types, " +"you can set the translatable flag:" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Domain based assignment" +#: ../system/objects/types.rst:25 +msgid "*Boolean field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.domain_assignment}``" +#: ../system/objects/types.rst:26 +msgid "*Single selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Domain" +#: ../system/objects/types.rst:27 +msgid "*Multiple selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.domain}``" +#: ../system/objects/types.rst:28 +msgid "*Single tree selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``zammad.com`` or empty if not set" +#: ../system/objects/types.rst:29 +msgid "*Multiple tree selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > VIP" +#: ../system/objects/types.rst:31 +msgid "" +"For these types, you can find an additional field *Translate field contents*:" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.vip}``" +#: ../system/objects/types.rst:0 +msgid "Screenshot showing translatable attribute types" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Note" +#: ../system/objects/types.rst:38 +msgid "Screenshot with example of translatable attribute type" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.note}``" +#: ../system/objects/types.rst:45 +msgid "Boolean field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Mobile" +#: ../system/objects/types.rst:41 +msgid "" +"Provides a drop-down field with display values for ``true`` and ``false``. " +"Setting a default is mandatory." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.mobile}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Boolean fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Login" +#: ../system/objects/types.rst:55 +msgid "Date field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.login}``" +#: ../system/objects/types.rst:48 +msgid "Provides a date picker field and does not allow default values." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Lastname" +#: ../system/objects/types.rst:52 +msgid "Default time diff (hours)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.lastname}``" +#: ../system/objects/types.rst:51 +msgid "" +"This setting helps the user by highlighting the day from now plus the " +"provided value. It *does not* pre-fill the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Firstname" +#: ../system/objects/types.rst:0 +msgid "Available settings for Date fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.firstname}``" +#: ../system/objects/types.rst:73 +msgid "Date & time field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Fax" +#: ../system/objects/types.rst:58 +msgid "Provides a date and time picker – does not allow default values" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.fax}``" +#: ../system/objects/types.rst:62 +msgid "Allow future" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Email" +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the future." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.email}``" +#: ../system/objects/types.rst:66 +msgid "Allow past" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Department" +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the past." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.department}``" +#: ../system/objects/types.rst:70 +msgid "Default time diff (minutes)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Web" +#: ../system/objects/types.rst:69 +msgid "" +"This setting helps the user by highlighting the day from now plus the " +"provided value. It does not pre-fill the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.web}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Date & time fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > VIP" +#: ../system/objects/types.rst:86 +msgid "Integer field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.vip}``" +#: ../system/objects/types.rst:76 +msgid "" +"Provides an input field that allows integer usage only. You may define a " +"default value. You cannot enforce comma separation." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Phone" +#: ../system/objects/types.rst:80 +msgid "Minimal" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.phone}``" +#: ../system/objects/types.rst:80 +msgid "The minimal value the field accepts." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Note" +#: ../system/objects/types.rst:83 +msgid "Maximal" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.note}``" +#: ../system/objects/types.rst:83 +msgid "The maximum value the field accepts." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Mobile" +#: ../system/objects/types.rst:0 +msgid "Available settings for Integer fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.mobile}``" +#: ../system/objects/types.rst:99 +msgid "Multiple selection field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Login" +#: ../system/objects/types.rst:89 +msgid "" +"Provides a selection field that allows the selection of one or more out of " +"several. This field does allow setting a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.login}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Multiple selection fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Lastname" +#: ../system/objects/types.rst:112 +msgid "Single selection field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.lastname}``" +#: ../system/objects/types.rst:102 +msgid "" +"Provides a drop-down field that allows selection of one value out of " +"several. This field does allow setting a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Firstname" +#: ../system/objects/types.rst:0 +msgid "Available settings for Single selection fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.firstname}``" +#: ../system/objects/types.rst:142 +msgid "Textarea field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Fax" +#: ../system/objects/types.rst:115 +msgid "" +"Provides a text area input field (multiple lines) and thus allows e.g. new " +"lines. You can set a default field value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.fax}``" +#: ../system/objects/types.rst:120 +msgid "" +"Please note that this field *does not* support text formatting or HTML " +"content (rich text)." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Email" +#: ../system/objects/types.rst:123 +msgid "**🥵 This field can consume a lot of visual space**" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.email}``" +#: ../system/objects/types.rst:125 +msgid "" +"Depending on where you use this field type, it may use a lot of visual space " +"if you provide a lot of text. This may be an issue to work with." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Department" +#: ../system/objects/types.rst:130 +msgid "Default" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.department}``" +#: ../system/objects/types.rst:129 +msgid "" +"The here provided text will be shown within the text area field or new data " +"sets." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Avatar" +#: ../system/objects/types.rst:134 ../system/objects/types.rst:160 +msgid "Maxlength" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.avatar(60,60)}``" +#: ../system/objects/types.rst:0 ../system/objects/types.rst:160 +msgid "You can pick the maximum length of the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Address" +#: ../system/objects/types.rst:0 +msgid "The default length of this object is ``500``." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.address}``" +#: ../system/objects/types.rst:139 +msgid "Rows" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created at" +#: ../system/objects/types.rst:0 +msgid "" +"Change the number of rows to dislay so that you can use only the space you " +"really need." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_at}``" +#: ../system/objects/types.rst:0 +msgid "The default number of rows is ``4``." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Avatar" +#: ../system/objects/types.rst:0 +msgid "Available settings for Textarea fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.avatar(60,60)}``" +#: ../system/objects/types.rst:165 +msgid "Text field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Address" +#: ../system/objects/types.rst:145 +msgid "Provides a text field (one line) and allows choosing a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.address}``" +#: ../system/objects/types.rst:148 +msgid "" +"Defines the type of the input field. This allows e.g. your browser to ensure " +"that you provide the specific type." msgstr "" -#: ../system/variables/ticket.rst:6 -msgid "" -"Below you can find all available ticket-based variables within Zammad. These " -"can be called via Triggers for example. If you're unsure if Zammad does " -"support variables at the point you're at, you can try to type ``::`` to " -"check." +#: ../system/objects/types.rst:152 +msgid "Currently available:" msgstr "" -#: ../system/variables/ticket.rst:12 -msgid "Ticket Variables" +#: ../system/objects/types.rst:155 +msgid "Phone" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Web" +#: ../system/objects/types.rst:156 +msgid "Text" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.web}``" +#: ../system/objects/types.rst:157 +msgid "Url *(URL fields disable link-template availability)*" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > VIP" +#: ../system/objects/types.rst:0 +msgid "Available settings for Text fields" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.vip}``" +#: ../system/objects/types.rst:174 +msgid "Single tree selection field" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Phone" +#: ../system/objects/types.rst:168 +msgid "" +"Provides a select-like field with up to 6 layers of options. Does not allow " +"setting a default value." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.phone}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Tree Select fields" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Note" +#: ../system/objects/types.rst:183 +msgid "Multiple tree selection field" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.note}``" +#: ../system/objects/types.rst:177 +msgid "" +"Provides a select-like field with up to 6 layers of options allowing the " +"selection of multiple values. Does not allow setting a default value." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Mobile" +#: ../system/objects/types.rst:302 +msgid "External Data Source field" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.mobile}``" +#: ../system/objects/types.rst:186 +msgid "" +"Provides a searchable field which fetches data from an external system. This " +"can be useful if you have data outside of Zammad and don't want to maintain " +"both data sources." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Login" +#: ../system/objects/types.rst:190 +msgid "The feature works as follows:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.login}``" +#: ../system/objects/types.rst:192 +msgid "" +"Zammad sends a query with a search string (free text from agent or based on " +"a variable) in a pre-defined format (\"Search URL\") to an external system." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Lastname" +#: ../system/objects/types.rst:195 +msgid "" +"This external system searches for matches and provides a response as a JSON " +"structure to Zammad." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.lastname}``" +#: ../system/objects/types.rst:197 +msgid "" +"Zammad just looks for the defined list and value keys, reads the content and " +"displays the value to the user. There is no search on Zammad side." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Firstname" +#: ../system/objects/types.rst:201 +msgid "" +"The usage of a PostgreSQL database for Zammad is required. In any other " +"case, Zammad will hide the external data source type and you are not able to " +"use it. If you want to use this feature, consider to :docs:`migrate your " +"database `." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.firstname}``" +#: ../system/objects/types.rst:205 +msgid "Currently, only ``GET`` is supported as request method." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Fax" +#: ../system/objects/types.rst:206 +msgid "" +"The data structure must be in JSON format and provide the objects in an " +"array." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.fax}``" +#: ../system/objects/types.rst:208 +msgid "" +"The endpoint for the external data source has to support search. On Zammad " +"side, there is no search/logic implemented; however, you can define the " +"output key and value based on the result(s) from the response (which " +"provides already filtered content based on the search)." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Email" +#: ../system/objects/types.rst:212 +msgid "" +"If you receive more results as expected, your external data source search " +"may not work properly or the structure of the URL is not correct. You should " +"get in touch with a responsible person from the external system." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.email}``" +#: ../system/objects/types.rst:217 +msgid "" +"Please have a look :doc:`at our example `, where you can find a possible configuration for a public " +"dummy endpoint." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Department" +#: ../system/objects/types.rst:0 +msgid "Available settings for external data source fields" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.department}``" +#: ../system/objects/types.rst:242 +msgid "Search URL" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Avatar" +#: ../system/objects/types.rst:227 +msgid "" +"Set your endpoint where Zammad fetches the data. Please make sure to include " +"a valid search :doc:`variable ` as an URL parameter. " +"Example for a free text search at user input: ``#{search.term}``" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.avatar(60,60)}``" +#: ../system/objects/types.rst:232 +msgid "" +"If in doubt, ask the responsible person for the external data source how " +"they expect the structure of the URL." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Address" +#: ../system/objects/types.rst:236 +msgid "" +"Depending on your search variable, the preview might work or not. The reason " +"is that the context might not be available and it is no bug." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.address}``" +#: ../system/objects/types.rst:239 +msgid "" +"Please also make sure to use a variable which is available in your object " +"context. For example you won't be able to search for a ticket in a user " +"object context." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated at" +#: ../system/objects/types.rst:252 +msgid "SSL Verification" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_at}``" +#: ../system/objects/types.rst:245 +msgid "Here you can switch the SSL verification to no." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Title" +#: ../system/objects/types.rst:249 +msgid "" +"If your external data source system is using self signed certificates, " +"please have a look :doc:`here ` for " +"further information about how to handle them in Zammad, so you can keep the " +"SSL verification activated." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.title}``" +#: ../system/objects/types.rst:258 +msgid "HTTP Authentication" msgstr "" -#: ../system/variables/ticket.rst:1 +#: ../system/objects/types.rst:255 msgid "" -"``My amazing Subject`` (normally subject, can be edited within Interface and " -"thus differ)" +"If your external data source requires an authentication, you can set it " +"here. You can leave it empty or choose between *Basic Authentication* or " +"*Authentication Token* (selecting one of the two methods leads to additional " +"fields where you can enter your credentials/token)." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Accounted Time" +#: ../system/objects/types.rst:265 +msgid "Search result list key" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.time_unit}``" +#: ../system/objects/types.rst:261 +msgid "" +"Defines the level in the JSON structure which provides the list with search " +"results. You can leave it empty, if the data is already provided as an " +"array. If you have to go deeper in the structure, you can provide a path " +"with ``.`` as separators, e.g. ``key.subkey.sub-sub-key``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``1``, ``2.75`` or empty response" +#: ../system/objects/types.rst:271 +msgid "Search result value key" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Tags" +#: ../system/objects/types.rst:268 +msgid "" +"Defines the attribute in the structure in which your external data source " +"provides the *value* for your data. An example would be a product *number*. " +"If you have to go deeper in the structure, you can provide a path with ``.`` " +"as separators, e.g. ``key.subkey.sub-sub-key``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.tags}``" +#: ../system/objects/types.rst:277 +msgid "Search result label key" msgstr "" -#: ../system/variables/ticket.rst:1 +#: ../system/objects/types.rst:274 msgid "" -"Currently not available, see `Issue 2769 `_" +"Defines the attribute in the structure in which your external data source " +"provides the *label* for your data. An example would be a product *name*. If " +"you have to go deeper in the structure, you can provide a path with ``.`` as " +"separators, e.g. ``key.subkey.sub-sub-key``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > State > Name" +#: ../system/objects/types.rst:280 +msgid "" +"In the preview area, you can find the following items (depending on your " +"configuration above):" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.state.name}``" +#: ../system/objects/types.rst:283 +msgid "" +"**Error/hint message** (only if configuration is not complete): Zammad tells " +"you, if there is a problem and what you should change in your configuration." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``new``, ``open``, ..." +#: ../system/objects/types.rst:286 +msgid "" +"**Search field**: search for an existing attribute in the data source to get " +"a preview. This is required for the fields below to show up." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Priority > Name" +#: ../system/objects/types.rst:288 +msgid "" +"**Search result response** (only if configuration is not complete): here you " +"can find a syntax highlighted JSON preview of the response, based on the " +"search term you entered." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.priority.name}``" +#: ../system/objects/types.rst:291 +msgid "" +"**Search result list** (only if *search result list key* is properly set): " +"output of the structure under the configured *search result list key*." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2 normal``" +#: ../system/objects/types.rst:294 +msgid "" +"**Preview table** (when fully configured): Zammad shows you a table which " +"includes the found items based on the search string (value, label and " +"optional link). You can use this preview if you don't have the complete data " +"structure of the external system in mind." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Pending till" +#: ../system/objects/types.rst:299 +msgid "" +"An example of a configured external data source field from agent perspective:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.pending_time}``" +#: ../system/objects/types.rst:0 +msgid "Screencast showing the search for a product in a ticket" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not set" +#: ../system/objects/types.rst:307 +msgid "URL fields (Link-Template)" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Web" +#: ../system/objects/types.rst:311 +msgid "" +"This function is restricted to Text, Select and External data source types " +"only." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.web}``" +#: ../system/objects/types.rst:314 +msgid "" +"Link-Templates are an amazing way to dynamically generate URLs. They allow " +"you to integrate other systems better without having to manually copy data " +"from Zammad if possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``https://zammad.com`` or empty if not set" +#: ../system/objects/types.rst:320 +msgid "" +"Another great way of communicating with another system may be Zammad's :doc:" +"`Webhooks `." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > VIP" +#: ../system/objects/types.rst:323 +msgid "" +"After filling a link-template enabled field, an URL icon will appear on its " +"right. Clicking on the icon opens a new tab." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.vip}``" +#: ../system/objects/types.rst:328 +msgid "" +"Even though Zammad displays the link template within object edit and create " +"screens, the function is optional. It's only active if you populate the " +"field." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Phone" +#: ../system/objects/types.rst:333 +msgid "" +"What's the difference between URL and text fields with link template...?!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.phone}``" +#: ../system/objects/types.rst:335 +msgid "" +"Both fields have different use cases. Use ``text`` type text fields when " +"ever you have a *static* url that requires dynamic parameters. If you " +"require a drag & drop like field that you can put in any URL, use ``URL`` " +"type text fields." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Note" +#: ../system/objects/types.rst:340 +msgid "" +"The difference is easier to spot when comparing the fields directly, below " +"screencast shows the result - the dynamic approach uses existing values in " +"the moment of updating to built the URL - e.g. ``https://google.com/search?" +"q=cookies`` - while the URL approach uses the actual URL of the field - e.g. " +"``https://zammad.com``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.note}``" +#: ../system/objects/types.rst:None +msgid "" +"Screencast showing the differents in between URL and text type fields with " +"actual values" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Mobile" +#: ../system/objects/types.rst:352 +msgid "How does this work...?!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.mobile}``" +#: ../system/objects/types.rst:354 +msgid "" +"As an example, let's say you have an attribute called ``amazing_attribute`` " +"and you want to open a google search directly with the input from that field." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Login" +#: ../system/objects/types.rst:357 +msgid "" +"Providing the link-template field below allows you to do so: ``https://www." +"google.com/search?q=#{ticket.amazing_attribute}``" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.login}``" +#: ../system/objects/types.rst:362 +msgid "" +"You can use any :doc:`Zammad variable ` as long as it's " +"available in the moment you need it." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``agent``" +#: ../system/objects/types.rst:365 +msgid "" +"As a result, you are redirected to Google with a search for the value of the " +"attribute, if you click on the button in the ticket (as you can see in the " +"screencast above)." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Lastname" +#: ../system/packages.rst:2 +msgid "Packages" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.lastname}``" +#: ../system/packages.rst:4 +msgid "That's the package management-area." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Mustermann`` or empty if not set" +#: ../system/packages.rst:6 +msgid "Individual add-ons for Zammad can be installed and managed here." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Firstname" +#: ../system/sessions.rst:2 +msgid "Sessions" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.firstname}``" +#: ../system/sessions.rst:4 +msgid "" +"Sessions management allows reviewing currently known user sessions and " +"allows to end these. The session timeout is affected by :ref:" +"`security_session_timeout` configurations from security settings." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Max`` or empty if not set" +#: ../system/sessions.rst:None +msgid "Screenshot showing Zammad's session management" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Fax" +#: ../system/sessions.rst:13 +msgid "Zammad will provide the following information:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.fax}``" +#: ../system/sessions.rst:16 +msgid "" +"The user account this session entry belongs to. It can be normal if a user " +"has several sessions in the list. This can be due to changed browser " +"information or if you use e.g. single sign on methods where the user does " +"not use the log off button." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Email" +#: ../system/sessions.rst:22 +msgid "Browser" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.email}``" +#: ../system/sessions.rst:22 +msgid "The browser agent communicated to Zammad." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``agent@company.tld`` or empty if not set" +#: ../system/sessions.rst:40 +msgid "Location" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Department" +#: ../system/sessions.rst:25 +msgid "" +"The anticipated location based on the users IP address. Depending on the IP " +"address the result shown may differ. This option depends on :doc:`/settings/" +"system/services`." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.department}``" +#: ../system/sessions.rst:29 +msgid "The following information can be shown:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Support`` or empty if not set" +#: ../system/sessions.rst:33 +msgid "IP address" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Avatar" +#: ../system/sessions.rst:32 +msgid "" +"Either if you set *Geo IP services* to inactive or you're using internal IP " +"address which do not provide location information." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.avatar(60,60)}``" +#: ../system/sessions.rst:40 +msgid "Country (or Country + City)" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Address" +#: ../system/sessions.rst:36 +msgid "" +"If *Geo IP services* is enabled only. Depends on how detailed the available " +"IP address information are." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.address}``" +#: ../system/sessions.rst:39 +msgid "" +"Be aware that results can be inaccurate - this technically is not an error." +msgstr "" + +#: ../system/sessions.rst:43 +msgid "Age" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Shared organization" +#: ../system/sessions.rst:43 +msgid "Provides the time when the session initially has been created." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.shared}``" +#: ../system/sessions.rst:50 +msgid "Update" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Note" +#: ../system/sessions.rst:46 +msgid "" +"Provides the time the user used this session to open Zammad. This timestamp " +"is only updated if the user e.g. reloads, not during normal work on tickets." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.note}``" +#: ../system/sessions.rst:50 +msgid "This timestamp is being used for the session timeout." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Name" +#: ../system/sessions.rst:53 +msgid "" +"Use the delete button to remove a single session on behalf of your user." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.name}``" +#: ../system/subscription.rst:2 +msgid "Subscription (SaaS)" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Zammad GmbH`` or empty if not set" +#: ../system/subscription.rst:4 +msgid "" +"The subscription settings page allows you to configure your instances " +"package and number of agents required." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Domain based assignment" +#: ../system/subscription.rst:9 +msgid "" +"This setting section is only available for Hosted setups. If you're looking " +"for on premise support contracts, please see the `Zammad pricing page " +"`_." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.domain_assignment}``" +#: ../system/subscription.rst:14 ../system/subscription.rst:34 +msgid "Plan" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Domain" +#: ../system/subscription.rst:16 +msgid "" +"Here you can set up everything affecting your instance subscription " +"functions like number of agents and package." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.domain}``" +#: ../system/subscription.rst:19 +msgid "" +"On top of the page you can find a subscription summary. You'll find the " +"number of used and available (booked) agent seats there. By using the *see " +"more* link you can also expand an agent list to see the currently configured " +"active agents. This list *does not* count accounts with admin permissions " +"only." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``domain.tld`` or empty if not set" +#: ../system/subscription.rst:None +msgid "" +"Within subscription you can always see how many agents are still\n" +"available to add and who uses the seats." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > VIP" +#: ../system/subscription.rst:29 +msgid "" +"Learn more on how to manage your agents in general :doc:`here `." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.vip}``" +#: ../system/subscription.rst:36 +msgid "" +"This section gives you an overview of the available plans and their " +"functions / limits. If you require a more detailed table, check our " +"`detailed pricing table `_ for more." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Number" +#: ../system/subscription.rst:40 +msgid "" +"Your selection in this step will decide on the base agent price and e.g. " +"agent limits that might apply in the summary step." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.number}``" +#: ../system/subscription.rst:43 +msgid "" +"The green *Selected* button will also tell you what plan you're currently in." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``31001``, ``201910731001``, ..." +#: ../system/subscription.rst:47 +msgid "" +"Trial instances are running at Professional with 3 agents. The plan cannot " +"be changed during the trial for technical reasons, if you require more " +"agents for testing, please contact `our sales team `_ with a reason for the raise request." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > ID" +#: ../system/subscription.rst:None +msgid "" +"Screenshot showing three available packages for a hosted Zammad\n" +"instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.id}``" +#: ../system/subscription.rst:57 +msgid "" +"At the bottom of this block you can find a summary where you can adjust the " +"settings of the previous selected plan." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``17``, ``5281``, ..." +#: ../system/subscription.rst:62 +msgid "" +"Note that upgrading (more agents, higher package) is always possible, " +"however, downgrading will only happen when your billing period renews." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact (customer)" +#: ../system/subscription.rst:66 +msgid "" +"Upgrading resets your billing period and existing credit will be deducted " +"from the new total." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_customer_at}``" +#: ../system/subscription.rst:75 +msgid "Billing cycle" msgstr "" -#: ../system/variables/ticket.rst:1 +#: ../system/subscription.rst:70 msgid "" -"``2019-10-07 16:25:00 UTC`` or empty if not applicable yet (Please note " -"`Ticket last contact behavior Settings `_ for this)" +"You can choose between either monthly or yearly billing. The price per agent " +"will be cheaper if you decide for yearly billing." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact" +#: ../system/subscription.rst:73 +msgid "" +"If you're still trying out things and are unsure of the right package for " +"your instance, you may want to choose monthly first and then upgrade to " +"yearly when you're sure." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_at}``" +#: ../system/subscription.rst:83 +msgid "Plan: (Starter|Professional|Plus) - Agents" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact (agent)" +#: ../system/subscription.rst:78 +msgid "Choose the number of agents you require for your instance." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_agent_at}``" +#: ../system/subscription.rst:80 +msgid "" +"Keep in mind that some packages may have agent limits. Depending on the " +"previous chosen package, you won't be able to exceed specific agent numbers. " +"Also note that setting less agents than currently configured is not possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable yet" +#: ../system/subscription.rst:86 +msgid "Total" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Note" +#: ../system/subscription.rst:86 +msgid "This will be the net total you're going to be billed." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.note}``" +#: ../system/subscription.rst:88 +msgid "" +"By using the *Update subscription* button, the instance package will be " +"adjusted immediately. If you didn't provide a payment method yet, Zammad " +"will request you to provide one at this point." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Note about this group``" +#: ../system/subscription.rst:94 +msgid "" +"In case you're still within the trial period, this means that the trial will " +"be over immediately!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Name" +#: ../system/subscription.rst:97 +msgid "Down- or upgrading during the trial period *is not* possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.name}``" +#: ../system/subscription.rst:None +msgid "Screenshot showing payment options and a pricing summary" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Sales``" +#: ../system/subscription.rst:103 +msgid "Billing Information" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Follow-up possible" +#: ../system/subscription.rst:105 +msgid "" +"You can control all billing relevant information like invoices, billing " +"address and the option to cancel your subscription." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.follow_up_possible}``" +#: ../system/subscription.rst:108 +msgid "" +"All adjusted billing information below only affect future invoices. If your " +"invoice was issued wrong, please contact `our sales team `_." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``no`` or ``yes``" +#: ../system/subscription.rst:114 +msgid "Billing address" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Assign Follow-Ups" +#: ../system/subscription.rst:113 +msgid "" +"Provide your company address here, make sure to include the companies name " +"in case required. This address will be referenced on your invoice." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.follow_up_assignment}``" +#: ../system/subscription.rst:118 +msgid "VAT ID" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Assignment Timeout" +#: ../system/subscription.rst:117 +msgid "" +"Provide your VAT ID here. If applicable your invoice will not contain German " +"VAT. Please make sure to pay the VAT in your country as required." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.assignment_timeout}``" +#: ../system/subscription.rst:127 +msgid "Billing Email Address" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``20`` or empty if not configured" +#: ../system/subscription.rst:121 +msgid "" +"Usually the instance owner (the person that registered the instance) will " +"receive all emails including the invoices. In case you have your own billing " +"department, you can provide their email address here." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > First response" +#: ../system/subscription.rst:125 +msgid "" +"All billing relevant information will then be sent to this email address." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.first_response_at}``" +#: ../system/subscription.rst:127 +msgid "Invoices are sent as attachment (PDF) to this email address." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Escalation at" +#: ../system/subscription.rst:129 +msgid "" +"Don't forget to press the *Update billing information* button after you " +"changed above settings." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.escalation_at}``" +#: ../system/subscription.rst:None +msgid "" +"Screenshot showing options for billing information within the\n" +"subscription menu" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable" +#: ../system/subscription.rst:137 +msgid "Payment Method" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Web" +#: ../system/subscription.rst:139 +msgid "You can pay via credit card or SEPA mandate." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.web}``" +#: ../system/subscription.rst:144 +msgid "Credit card" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > VIP" +#: ../system/subscription.rst:142 +msgid "" +"Simply follow the dialogue by clicking *authorize credit card* and confirm -" +"if required by your bank- your consent to Zammad using your card for the " +"payments." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.vip}``" +#: ../system/subscription.rst:148 +msgid "SEPA Direct Debit" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Phone" +#: ../system/subscription.rst:147 +msgid "" +"Provide the requested information of the bank account holder and update if " +"you're ready. You'll then receive an email with the SEPA mandate." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.phone}``" +#: ../system/subscription.rst:150 +msgid "" +"Technically there's also the possibility to pay via invoice, however - this " +"method only applies to a fairly low number of instances. Please contact `our " +"sales team `_ for more information." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Note" -msgstr "" +#: ../system/subscription.rst:156 +#, fuzzy +#| msgid "Description" +msgid "Cancel Subscription" +msgstr "Opis" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.note}``" +#: ../system/subscription.rst:158 +msgid "" +"Do you want to cancel your subscription? In case you no longer want to use " +"Zammad's SaaS, you can cancel your subscription by using the red *Yes, " +"please cancel my subscription* button." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Mobile" +#: ../system/subscription.rst:162 +msgid "" +"To cancel the description, enter the FQDN of your Zammad instance and " +"provide a reason for your cancellation." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.mobile}``" +#: ../system/subscription.rst:165 +msgid "" +"Your subscription will end the day after your trial or billing period ends." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Login" +#: ../system/subscription.rst:None +msgid "Screenshot showing subscription cancellation dialog" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.login}``" +#: ../system/subscription.rst:174 +msgid "" +"We will remind you about your cancelled subscription several times up front. " +"After the subscription ended all instance data will be removed. A restore " +"*is not* possible after that point!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Lastname" +#: ../system/subscription.rst:178 +msgid "**😖 Cancelled by accident?**" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.lastname}``" +#: ../system/subscription.rst:180 +msgid "" +"You can always undo the cancellation via the *Yes, undo the cancellation of " +"my subscription* button up to the last subscription day!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Firstname" +#: ../system/subscription.rst:0 +msgid "" +"Screenshot showing a red button to cancel the subscription\n" +"cancellation" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.firstname}``" +#: ../system/subscription.rst:189 +msgid "Payment History" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Fax" +#: ../system/subscription.rst:191 +msgid "" +"The payment history will display a history of all paid invoices. At this " +"point you can also download these in case you need them again." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.fax}``" +#: ../system/subscription.rst:196 +msgid "" +"You will only find *paid* invoices here. Invoices that are to be billed are " +"not available before the payment is completed." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Email" +#: ../system/subscription.rst:201 +msgid "Date" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.email}``" +#: ../system/subscription.rst:201 +msgid "Date of the invoice creation." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Department" +#: ../system/subscription.rst:204 +msgid "Amount" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.department}``" +#: ../system/subscription.rst:204 +msgid "Invoice total including VAT if applicable." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Avatar" +#: ../system/subscription.rst:207 +msgid "" +"Contains contract period (monthly or yearly) and hosted plan for the " +"subscription period in question." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.avatar(60,60)}``" +#: ../system/subscription.rst:218 +msgid "Payment method / Service period" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Address" +#: ../system/subscription.rst:211 +msgid "" +"Used bank account or credit card as well as the subscription period the " +"invoice is about." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.address}``" +#: ../system/subscription.rst:216 +msgid "" +"It might happen that the invoice date and subscription period differ. This " +"is nothing to worry about, the subscription periods will be accounted later " +"on." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Web" +#: ../system/subscription.rst:222 +msgid "Receipt" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.web}``" +#: ../system/subscription.rst:221 +msgid "" +"Use the arrow to download the invoice in question. You can download all " +"available invoices any time you need to here!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > VIP" +#: ../system/subscription.rst:None +msgid "Screenshot showing payment history of a hosted instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.vip}``" +#: ../system/subscription.rst:229 +msgid "FAQ" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Phone" +#: ../system/subscription.rst:233 +msgid "I set up a trial account but am missing functions to test" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.phone}``" +#: ../system/subscription.rst:232 +msgid "" +"The trial instance is running within the professional package allowing up to " +"three agents." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Note" +#: ../system/subscription.rst:236 +msgid "Can I change package within the trial?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.note}``" +#: ../system/subscription.rst:236 +msgid "No. As soon as the package is changed the subscription begins." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Mobile" +#: ../system/subscription.rst:241 +msgid "What happens to my trial instance after the trial period ended?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.mobile}``" +#: ../system/subscription.rst:239 +msgid "" +"Your instance will automatically be canceled for you. Please see *What " +"happens to my instance after it has been canceled?* for more." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Login" +#: ../system/subscription.rst:254 +msgid "What happens to my instance after it has been canceled?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.login}``" +#: ../system/subscription.rst:244 +msgid "That depends slightly on your instance state:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Lastname" +#: ../system/subscription.rst:250 +msgid "Trial instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.lastname}``" +#: ../system/subscription.rst:247 +msgid "" +"If you're still on trial, we will ice your instance and remind you once " +"again about your instance. We then will wait some days and remove your " +"instance from our system. This is the last time we will inform you by Email." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Firstname" +#: ../system/subscription.rst:254 +msgid "Paid instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.firstname}``" +#: ../system/subscription.rst:253 +msgid "" +"If you're a paying customer and canceled your subscription, the instance " +"removal will take place the day after your last subscription day." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Fax" +#: ../system/subscription.rst:256 +msgid "Can removed instances be restored?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.fax}``" +#: ../system/subscription.rst:257 +msgid "No. Once your instance has been removed, a restoration is not possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Email" +#: ../system/system-report.rst:2 +msgid "System Report" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.email}``" +#: ../system/system-report.rst:4 +msgid "" +"In this place you can't configure Zammad. Instead you can obtain a system " +"report about Zammad and its configuration." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Department" +#: ../system/system-report.rst:7 +msgid "" +"See the description in Zammad for an explanation. You can even find a " +"preview of the included data below the **Download** button." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.department}``" +#: ../system/system-report.rst:10 +msgid "" +"Zammad never sends this automatically to anyone. It is a manual process only " +"to provide better support based on your configuration." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Avatar" +#: ../system/translations.rst:2 +msgid "Translations" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.avatar(60,60)}``" +#: ../system/translations.rst:4 +msgid "" +"Translations of Zammad are processed centrally in our `Weblate instance " +"`_. This allows non-developers to review " +"and update translation texts of the language they actually speak." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Address" +#: ../system/translations.rst:9 +msgid "" +"Your language is in an incomplete translation state or has typos? Please " +"consider helping us in sorting this out! All you need is either a GitHub " +"account or to register directly in our instance." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.address}``" +#: ../system/translations.rst:13 +msgid "" +"Did you know? This is also where the documentation translations are handled. " +"🤓" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created at" +#: ../system/translations.rst:15 +msgid "" +"Have a look in our :docs:`contribution section ` in the system documentation to get started!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_at}``" +#: ../system/translations.rst:20 +msgid "Local Translations" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "2019-10-07 16:25:00 UTC" +#: ../system/translations.rst:22 +msgid "" +"Apart from these system translations, there's still local translations you " +"can manage. This is relevant if you added custom objects that require " +"translations or even custom states and priorities." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Closing time" +#: ../system/translations.rst:None +msgid "Translation management screen within the admin menu" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.close_at}``" +#: ../system/translations.rst:31 +msgid "Updating Translations" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "2019-10-07 17:25:00 UTC" +#: ../system/translations.rst:33 +msgid "" +"Because of how Zammad ships translations, the only way to update the system " +"translations is to update your Zammad installation. The benefit of this is " +"that you no longer need internet access during a Zammad upgrade as the " +"package has everything it requires already." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``3``, any number of articles existing in the ticket right now" +#: ../system/translations.rst:39 +msgid "Translation of Custom Objects" msgstr "" -#: ../system/version.rst:2 -msgid "Version" +#: ../system/translations.rst:41 +msgid "" +"No problem at all! You can customize any translation locally, even if it is " +"not initially provided by the system." msgstr "" -#: ../system/version.rst:4 -msgid "Shows which version is currently being used on your Zammad-instance." +#: ../system/translations.rst:44 +msgid "" +"Translation is supported for a broad number of features, including but not " +"limited to custom:" msgstr "" -#: ../manage/roles/admin-permissions.rst:53 -msgid "``admin.checklist``" +#: ../system/translations.rst:47 +msgid "Object Attributes" msgstr "" -#: ../manage/roles/admin-permissions.rst:54 -msgid ":doc:`Manage > Checklist `" -msgstr "" +#: ../system/translations.rst:48 +#, fuzzy +msgid "Ticket Macros" +msgstr "Makro-naredbe" -#: ../manage/roles/admin-permissions.rst:83 -msgid "``admin.channel_whatsapp``" +#: ../system/translations.rst:49 +msgid "Ticket Overviews" msgstr "" -#: ../manage/roles/admin-permissions.rst:84 -msgid ":doc:`Channels > Whatsapp `" -msgstr "" +#: ../system/translations.rst:50 +#, fuzzy +msgid "Ticket Priorities" +msgstr "prioritet" -#: ../manage/roles/admin-permissions.rst:124 -msgid "``admin.public_links``" +#: ../system/translations.rst:51 +msgid "Ticket States" msgstr "" -#: ../manage/roles/admin-permissions.rst:125 -msgid ":doc:`Manage > Public Links `" +#: ../system/translations.rst:54 +msgid "Customizing Translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:151 -msgid "``admin.system_report``" +#: ../system/translations.rst:56 +msgid "" +"Within the translation screen, simply click on the **New Translation** " +"button." msgstr "" -#: ../manage/roles/admin-permissions.rst:152 -msgid ":doc:`System > System Report `" +#: ../system/translations.rst:None +#, fuzzy +msgid "New translation dialog" +msgstr "Dodavanje novog e-mail računa" + +#: ../system/translations.rst:62 +msgid "" +"In the dialog you can immediately enter the exact translation source (if you " +"know it) and your custom translation text for it and click **Submit**." msgstr "" -#: ../manage/roles/admin-permissions.rst:166 -msgid "``admin.ticket_auto_assignment``" +#: ../system/translations.rst:65 +msgid "" +"Alternatively, try to search for translation suggestions in the list below. " +"Selecting an item from the list will pre-fill the translation source for you " +"and then you can just enter your custom translation." msgstr "" -#: ../manage/roles/admin-permissions.rst:167 -msgid ":ref:`Settings > Ticket > Auto Assignment `" +#: ../system/translations.rst:69 +msgid "" +"The target language will always default to your current language selection. " +"If you need to translate for a different language, simply change the " +"selection before submitting." msgstr "" -#: ../manage/roles/admin-permissions.rst:169 -msgid "``admin.ticket_duplicate_detection``" +#: ../system/translations.rst:73 +msgid "" +"All your custom translations will show up in the overview table when added. " +"And they will even persist across Zammad updates!" msgstr "" -#: ../manage/roles/admin-permissions.rst:170 -msgid ":ref:`Settings > Ticket > Duplicate Detection `" +#: ../system/translations.rst:76 +msgid "" +"Make sure to reload your browser if a translated string is not displayed." msgstr "" -#: ../manage/roles/admin-permissions.rst:172 -#, fuzzy -msgid "``admin.ticket_priority``" -msgstr "prioritet" +#: ../system/translations.rst:80 +msgid "Reverting to Original Translations" +msgstr "" -#: ../manage/roles/admin-permissions.rst:173 -msgid ":ref:`System > Objects >Ticket Priority `" +#: ../system/translations.rst:82 +msgid "" +"If you want to revert a custom translation to original text, simply use the " +"appropriate action within the row of the overview table." msgstr "" -#: ../manage/roles/admin-permissions.rst:175 -msgid "``admin.ticket_state``" +#: ../system/translations.rst:85 +msgid "" +"Depending on the type of the translation source, the action has a slightly " +"different name:" msgstr "" -#: ../manage/roles/admin-permissions.rst:176 -msgid ":ref:`System > Objects >Ticket State `" +#: ../system/translations.rst:88 +msgid "**Reset** for customized system translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:193 -msgid "``admin.webhook``" +#: ../system/translations.rst:89 +msgid "**Remove** for customized local translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:194 -msgid ":doc:`Manage > Webhook `" +#: ../system/translations.rst:91 +msgid "" +"In both cases, the action will remove the customized translation after a " +"confirmation." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:43 -msgid "``user_preferences.appearance``" +#: ../system/translations.rst:None +msgid "Screenshot showing the location of the Remove action" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:44 -msgid "Appearance configuration" +#: ../system/translations.rst:99 +msgid "Inline Translations" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:0 -msgid "Users can switch between dark, light and" +#: ../system/translations.rst:101 +msgid "" +"If you prefer a more hands-on approach, you can activate the inline or on-" +"screen translation feature by pressing ``ctrl`` + ``alt`` + ``t`` at any " +"time and on any screen." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:0 -msgid "automatic mode." +#: ../system/translations.rst:105 +msgid "" +"All customizable translation texts will be highlighted for you on the " +"screen. Just click into the highlighted area and update the text in place." msgstr "" -#: ../system/system-report.rst:2 -msgid "System Report" +#: ../system/translations.rst:None +msgid "Inline translation mode activated for the Overview screen" msgstr "" -#: ../system/system-report.rst:4 +#: ../system/translations.rst:112 msgid "" -"In this place you can't configure Zammad. Instead you can obtain a system " -"report about Zammad and its configuration." +"When finished editing, simply press ``ctrl`` + ``alt`` + ``t`` again to " +"deactivate." msgstr "" -#: ../system/system-report.rst:7 +#: ../system/translations.rst:117 msgid "" -"See the description in Zammad for an explanation. You can even find a " -"preview of the included data below the **Download** button." +"Even though it's available on any screen, the inline translation feature " +"requires admin permissions. It works only for the current language " +"selection. If you need to translate a different language, first change the " +"language in your :user-docs:`profile settings `." msgstr "" -#: ../system/system-report.rst:10 -msgid "" -"Zammad never sends this automatically to anyone. It is a manual process only " -"to provide better support based on your configuration." +#: ../system/version.rst:2 +msgid "Version" +msgstr "" + +#: ../system/version.rst:4 +msgid "Shows which version is currently being used on your Zammad-instance." msgstr "" #, fuzzy diff --git a/locale/hu/LC_MESSAGES/admin-docs.po b/locale/hu/LC_MESSAGES/admin-docs.po index 082b1053..6abcaa1d 100644 --- a/locale/hu/LC_MESSAGES/admin-docs.po +++ b/locale/hu/LC_MESSAGES/admin-docs.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Zammad\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-11-06 10:31+0100\n" +"POT-Creation-Date: 2024-11-12 16:31+0100\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -1040,12 +1040,12 @@ msgstr "" #: ../manage/roles/agent-permissions.rst:31 #: ../manage/roles/user-preferences-permissions.rst:37 #: ../manage/scheduler.rst:108 ../manage/webhook/add.rst:116 +#: ../misc/variables.rst:101 #: ../system/integrations/cti/includes/inbound-calls.include.rst:15 #: ../system/integrations/cti/includes/outbound-calls.include.rst:18 #: ../system/integrations/cti/includes/inbound-calls.include.rst:14 #: ../system/integrations/cti/includes/outbound-calls.include.rst:17 -#: ../system/objects.rst:162 ../system/objects.rst:244 -#: ../system/variables.rst:101 ../system/objects.rst:246 +#: ../system/objects.rst:162 ../system/objects.rst:246 msgid "Note" msgstr "" @@ -2257,7 +2257,7 @@ msgstr "" #: ../channels/email/signatures.rst:22 msgid "" "To individualize the signatures, it is possible to automatically load " -"specific information into a signature via :doc:`/system/variables`. All " +"specific information into a signature via :doc:`/misc/variables`. All " "information stored on the ticket, assigned customers or agents can be " "inserted. This makes it possible to design the signature individually. To " "load a list of available variables, enter two colons (``::``) into the " @@ -2550,7 +2550,7 @@ msgstr "" #: ../channels/form.rst:19 ../manage/groups/settings.rst:14 #: ../manage/scheduler.rst:39 ../manage/slas/how-do-they-work.rst:26 #: ../manage/templates.rst:33 ../system/objects.rst:130 -#: ../system/objects.rst:232 ../system/objects.rst:234 +#: ../system/objects.rst:234 msgid "Name" msgstr "" @@ -2579,7 +2579,7 @@ msgstr "" #: ../manage/macros/how-do-they-work.rst:0 ../manage/overviews.rst:0 #: ../manage/scheduler.rst:111 ../manage/templates.rst:43 #: ../manage/webhook/add.rst:123 ../system/objects.rst:169 -#: ../system/objects.rst:246 ../system/objects.rst:248 +#: ../system/objects.rst:248 msgid "Active" msgstr "" @@ -2921,10 +2921,9 @@ msgid "Default value" msgstr "" #: ../channels/form.rst:219 ../manage/public-links.rst:47 -#: ../misc/object-conditions/basics.rst:64 +#: ../misc/object-conditions/basics.rst:64 ../misc/variables.rst:100 #: ../system/core-workflows/condition-operators.rst:21 -#: ../system/objects/permissions.rst:39 ../system/subscription/billing.rst:53 -#: ../system/variables.rst:100 +#: ../system/objects/permissions.rst:39 ../system/subscription.rst:208 msgid "Description" msgstr "" @@ -5908,7 +5907,7 @@ msgstr "" msgid "System" msgstr "" -#: ../index.rst:87 ../index.rst:88 +#: ../index.rst:87 msgid "Misc" msgstr "" @@ -7142,7 +7141,7 @@ msgstr "" #: ../manage/macros/how-do-they-work.rst:28 msgid "" "Unlike triggers, the scheduler, and text modules, macro actions do **not** " -"support the use of :doc:`/system/variables`." +"support the use of :doc:`/misc/variables`." msgstr "" #: ../manage/macros/how-do-they-work.rst:32 @@ -8370,165 +8369,149 @@ msgid "Accessing chat for agents: ``chat.agent``" msgstr "" #: ../manage/roles/admin-permissions.rst:53 +msgid "``admin.checklist``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:54 +msgid ":doc:`Manage > Checklist `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:56 msgid "``admin.channel_email``" msgstr "" -#: ../manage/roles/admin-permissions.rst:54 #: ../manage/roles/admin-permissions.rst:57 msgid ":doc:`Channels > Email `" msgstr "" -#: ../manage/roles/admin-permissions.rst:56 #: ../manage/roles/admin-permissions.rst:59 msgid "``admin.channel_facebook``" msgstr "" -#: ../manage/roles/admin-permissions.rst:57 #: ../manage/roles/admin-permissions.rst:60 msgid ":doc:`Channels > Facebook `" msgstr "" -#: ../manage/roles/admin-permissions.rst:58 #: ../manage/roles/admin-permissions.rst:61 msgid "" "Accessing Facebook tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:59 #: ../manage/roles/admin-permissions.rst:62 msgid "``admin.channel_formular``" msgstr "" -#: ../manage/roles/admin-permissions.rst:60 #: ../manage/roles/admin-permissions.rst:63 msgid ":doc:`Channels > Form `" msgstr "" -#: ../manage/roles/admin-permissions.rst:62 #: ../manage/roles/admin-permissions.rst:65 msgid "``admin.channel_google``" msgstr "" -#: ../manage/roles/admin-permissions.rst:63 #: ../manage/roles/admin-permissions.rst:66 msgid ":doc:`Channels > Google `" msgstr "" -#: ../manage/roles/admin-permissions.rst:65 #: ../manage/roles/admin-permissions.rst:68 msgid "``admin.channel_microsoft365``" msgstr "" -#: ../manage/roles/admin-permissions.rst:66 #: ../manage/roles/admin-permissions.rst:69 msgid ":doc:`Channels > Microsoft 365 `" msgstr "" -#: ../manage/roles/admin-permissions.rst:68 #: ../manage/roles/admin-permissions.rst:71 msgid "``admin.channel_sms``" msgstr "" -#: ../manage/roles/admin-permissions.rst:69 #: ../manage/roles/admin-permissions.rst:72 msgid ":doc:`Channels > SMS `" msgstr "" -#: ../manage/roles/admin-permissions.rst:71 #: ../manage/roles/admin-permissions.rst:74 msgid "``admin.channel_telegram``" msgstr "" -#: ../manage/roles/admin-permissions.rst:72 #: ../manage/roles/admin-permissions.rst:75 msgid ":doc:`Channels > Telegram `" msgstr "" -#: ../manage/roles/admin-permissions.rst:73 #: ../manage/roles/admin-permissions.rst:76 msgid "" "Accessing Telegram tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:74 #: ../manage/roles/admin-permissions.rst:77 msgid "``admin.channel_twitter``" msgstr "" -#: ../manage/roles/admin-permissions.rst:75 #: ../manage/roles/admin-permissions.rst:78 msgid ":doc:`Channels > Twitter `" msgstr "" -#: ../manage/roles/admin-permissions.rst:76 #: ../manage/roles/admin-permissions.rst:79 msgid "" "Accessing Twitter/X tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:77 #: ../manage/roles/admin-permissions.rst:80 msgid "``admin.channel_web``" msgstr "" -#: ../manage/roles/admin-permissions.rst:78 #: ../manage/roles/admin-permissions.rst:81 msgid ":doc:`Channels > Web `" msgstr "" -#: ../manage/roles/admin-permissions.rst:80 +#: ../manage/roles/admin-permissions.rst:83 +msgid "``admin.channel_whatsapp``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:84 +msgid ":doc:`Channels > Whatsapp `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:86 msgid "``admin.core_workflows``" msgstr "" -#: ../manage/roles/admin-permissions.rst:81 #: ../manage/roles/admin-permissions.rst:87 msgid ":doc:`System > Core Workflows `" msgstr "" -#: ../manage/roles/admin-permissions.rst:83 #: ../manage/roles/admin-permissions.rst:89 msgid "``admin.data_privacy``" msgstr "" -#: ../manage/roles/admin-permissions.rst:84 #: ../manage/roles/admin-permissions.rst:90 msgid ":doc:`System > Data Privacy `" msgstr "" -#: ../manage/roles/admin-permissions.rst:85 #: ../manage/roles/admin-permissions.rst:91 msgid "" "🔥 Be careful, it allows users to permanently delete data on the system." msgstr "" -#: ../manage/roles/admin-permissions.rst:86 #: ../manage/roles/admin-permissions.rst:92 msgid "``admin.group``" msgstr "" -#: ../manage/roles/admin-permissions.rst:87 #: ../manage/roles/admin-permissions.rst:93 msgid ":doc:`Manage > Groups `" msgstr "" -#: ../manage/roles/admin-permissions.rst:89 #: ../manage/roles/admin-permissions.rst:95 msgid "``admin.integration``" msgstr "" -#: ../manage/roles/admin-permissions.rst:90 #: ../manage/roles/admin-permissions.rst:96 msgid ":doc:`System > Integrations `" msgstr "" -#: ../manage/roles/admin-permissions.rst:92 #: ../manage/roles/admin-permissions.rst:98 msgid "``admin.knowledge_base``" msgstr "" -#: ../manage/roles/admin-permissions.rst:93 #: ../manage/roles/admin-permissions.rst:99 msgid ":doc:`Manage > Knowledge Base `" msgstr "" @@ -8548,57 +8531,46 @@ msgid "" "knowledge-base.html#editing-answers>`." msgstr "" -#: ../manage/roles/admin-permissions.rst:98 #: ../manage/roles/admin-permissions.rst:104 msgid "``admin.macro``" msgstr "" -#: ../manage/roles/admin-permissions.rst:99 #: ../manage/roles/admin-permissions.rst:105 msgid ":doc:`Manage > Macros `" msgstr "" -#: ../manage/roles/admin-permissions.rst:100 #: ../manage/roles/admin-permissions.rst:106 msgid "In some cases, macros may also require ``admin.tag``" msgstr "" -#: ../manage/roles/admin-permissions.rst:101 #: ../manage/roles/admin-permissions.rst:107 msgid "``admin.maintenance``" msgstr "" -#: ../manage/roles/admin-permissions.rst:102 #: ../manage/roles/admin-permissions.rst:108 msgid ":doc:`System > Maintenance `" msgstr "" -#: ../manage/roles/admin-permissions.rst:104 #: ../manage/roles/admin-permissions.rst:110 msgid "``admin.monitoring``" msgstr "" -#: ../manage/roles/admin-permissions.rst:105 #: ../manage/roles/admin-permissions.rst:111 msgid ":doc:`System > Monitoring `" msgstr "" -#: ../manage/roles/admin-permissions.rst:107 #: ../manage/roles/admin-permissions.rst:113 msgid "``admin.object``" msgstr "" -#: ../manage/roles/admin-permissions.rst:108 #: ../manage/roles/admin-permissions.rst:114 msgid ":doc:`System > Objects `" msgstr "" -#: ../manage/roles/admin-permissions.rst:110 #: ../manage/roles/admin-permissions.rst:116 msgid "``admin.organization``" msgstr "" -#: ../manage/roles/admin-permissions.rst:111 #: ../manage/roles/admin-permissions.rst:117 msgid ":doc:`Manage > Organizations `" msgstr "" @@ -8615,202 +8587,210 @@ msgstr "" msgid "They can even edit an organization's name, domain, and notes!" msgstr "" -#: ../manage/roles/admin-permissions.rst:115 #: ../manage/roles/admin-permissions.rst:121 msgid "``admin.overview``" msgstr "" -#: ../manage/roles/admin-permissions.rst:116 #: ../manage/roles/admin-permissions.rst:122 msgid ":doc:`Manage > Overviews`" msgstr "" -#: ../manage/roles/admin-permissions.rst:118 +#: ../manage/roles/admin-permissions.rst:124 +msgid "``admin.public_links``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:125 +msgid ":doc:`Manage > Public Links `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:127 msgid "``admin.package``" msgstr "" -#: ../manage/roles/admin-permissions.rst:119 #: ../manage/roles/admin-permissions.rst:128 msgid ":doc:`System > Packages `" msgstr "" -#: ../manage/roles/admin-permissions.rst:121 #: ../manage/roles/admin-permissions.rst:130 msgid "``admin.report_profile``" msgstr "" -#: ../manage/roles/admin-permissions.rst:122 #: ../manage/roles/admin-permissions.rst:131 msgid ":doc:`Manage > Report Profiles `" msgstr "" -#: ../manage/roles/admin-permissions.rst:123 #: ../manage/roles/admin-permissions.rst:132 msgid "Access to view reports: ``report``" msgstr "" -#: ../manage/roles/admin-permissions.rst:124 #: ../manage/roles/admin-permissions.rst:133 msgid "``admin.role``" msgstr "" -#: ../manage/roles/admin-permissions.rst:125 #: ../manage/roles/admin-permissions.rst:134 msgid ":doc:`Manage > Roles `" msgstr "" -#: ../manage/roles/admin-permissions.rst:127 #: ../manage/roles/admin-permissions.rst:136 msgid "``admin.scheduler``" msgstr "" -#: ../manage/roles/admin-permissions.rst:128 #: ../manage/roles/admin-permissions.rst:137 msgid ":doc:`Manage > Scheduler `" msgstr "" -#: ../manage/roles/admin-permissions.rst:129 #: ../manage/roles/admin-permissions.rst:138 msgid "For automation on tickets" msgstr "" -#: ../manage/roles/admin-permissions.rst:130 #: ../manage/roles/admin-permissions.rst:139 msgid "``admin.security``" msgstr "" -#: ../manage/roles/admin-permissions.rst:131 #: ../manage/roles/admin-permissions.rst:140 msgid ":doc:`Settings > Security `" msgstr "" -#: ../manage/roles/admin-permissions.rst:132 #: ../manage/roles/admin-permissions.rst:141 msgid "Settings of Zammad. This also covers third party authentications." msgstr "" -#: ../manage/roles/admin-permissions.rst:133 #: ../manage/roles/admin-permissions.rst:142 msgid "``admin.session``" msgstr "" -#: ../manage/roles/admin-permissions.rst:134 #: ../manage/roles/admin-permissions.rst:143 msgid ":doc:`System > Sessions `" msgstr "" -#: ../manage/roles/admin-permissions.rst:136 #: ../manage/roles/admin-permissions.rst:145 msgid "``admin.setting_system``" msgstr "" -#: ../manage/roles/admin-permissions.rst:137 #: ../manage/roles/admin-permissions.rst:146 msgid ":doc:`Settings > System `" msgstr "" -#: ../manage/roles/admin-permissions.rst:139 #: ../manage/roles/admin-permissions.rst:148 msgid "``admin.sla``" msgstr "" -#: ../manage/roles/admin-permissions.rst:140 #: ../manage/roles/admin-permissions.rst:149 msgid ":doc:`Manage > SLAs `" msgstr "" -#: ../manage/roles/admin-permissions.rst:142 +#: ../manage/roles/admin-permissions.rst:151 +msgid "``admin.system_report``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:152 +msgid ":doc:`System > System Report `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:154 msgid "``admin.tag``" msgstr "" -#: ../manage/roles/admin-permissions.rst:143 #: ../manage/roles/admin-permissions.rst:155 msgid ":doc:`Manage > Tags `" msgstr "" -#: ../manage/roles/admin-permissions.rst:145 #: ../manage/roles/admin-permissions.rst:157 msgid "``admin.template``" msgstr "" -#: ../manage/roles/admin-permissions.rst:146 #: ../manage/roles/admin-permissions.rst:158 msgid ":doc:`Manage > Templates `" msgstr "" -#: ../manage/roles/admin-permissions.rst:148 #: ../manage/roles/admin-permissions.rst:160 msgid "``admin.text_module``" msgstr "" -#: ../manage/roles/admin-permissions.rst:149 #: ../manage/roles/admin-permissions.rst:161 msgid ":doc:`Manage > Text Modules `" msgstr "" -#: ../manage/roles/admin-permissions.rst:151 #: ../manage/roles/admin-permissions.rst:163 msgid "``admin.ticket``" msgstr "" -#: ../manage/roles/admin-permissions.rst:152 #: ../manage/roles/admin-permissions.rst:164 msgid ":doc:`Settings > Tickets `" msgstr "" -#: ../manage/roles/admin-permissions.rst:153 #: ../manage/roles/admin-permissions.rst:165 msgid "Does not grant access to :doc:`/misc/composer`" msgstr "" -#: ../manage/roles/admin-permissions.rst:154 +#: ../manage/roles/admin-permissions.rst:166 +msgid "``admin.ticket_auto_assignment``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:167 +msgid ":ref:`Settings > Ticket > Auto Assignment `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:169 +msgid "``admin.ticket_duplicate_detection``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:170 +msgid ":ref:`Settings > Ticket > Duplicate Detection `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:172 +msgid "``admin.ticket_priority``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:173 +msgid ":ref:`System > Objects >Ticket Priority `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:175 +msgid "``admin.ticket_state``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:176 +msgid ":ref:`System > Objects >Ticket State `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:178 msgid "``admin.time_accounting``" msgstr "" -#: ../manage/roles/admin-permissions.rst:155 #: ../manage/roles/admin-permissions.rst:179 msgid ":doc:`Manage > Time Accounting `" msgstr "" -#: ../manage/roles/admin-permissions.rst:156 #: ../manage/roles/admin-permissions.rst:180 msgid "Also allows the export of timekeeping records." msgstr "" -#: ../manage/roles/admin-permissions.rst:157 #: ../manage/roles/admin-permissions.rst:181 msgid "``admin.translation``" msgstr "" -#: ../manage/roles/admin-permissions.rst:158 #: ../manage/roles/admin-permissions.rst:182 msgid ":doc:`System > Translations `" msgstr "" -#: ../manage/roles/admin-permissions.rst:159 #: ../manage/roles/admin-permissions.rst:183 msgid "Also enables inline translation" msgstr "" -#: ../manage/roles/admin-permissions.rst:160 #: ../manage/roles/admin-permissions.rst:184 msgid "``admin.trigger``" msgstr "" -#: ../manage/roles/admin-permissions.rst:161 #: ../manage/roles/admin-permissions.rst:185 msgid ":doc:`Manage > Triggers `" msgstr "" -#: ../manage/roles/admin-permissions.rst:163 #: ../manage/roles/admin-permissions.rst:187 msgid "``admin.user``" msgstr "" -#: ../manage/roles/admin-permissions.rst:164 #: ../manage/roles/admin-permissions.rst:188 msgid ":doc:`Manage > Users `" msgstr "" @@ -8829,6 +8809,14 @@ msgid "" "from-users-perspective>` ." msgstr "" +#: ../manage/roles/admin-permissions.rst:193 +msgid "``admin.webhook``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:194 +msgid ":doc:`Manage > Webhook `" +msgstr "" + #: ../manage/roles/agent-permissions.rst:2 msgid "Agent Permissions" msgstr "" @@ -9247,36 +9235,45 @@ msgid "than the user that generated them." msgstr "" #: ../manage/roles/user-preferences-permissions.rst:43 +msgid "``user_preferences.appearance``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:44 +msgid "Appearance configuration" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "Users can switch between dark, light and" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "automatic mode." +msgstr "" + #: ../manage/roles/user-preferences-permissions.rst:47 msgid "``user_preferences.avatar``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:44 #: ../manage/roles/user-preferences-permissions.rst:48 msgid "Avatar settings" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:45 #: ../manage/roles/user-preferences-permissions.rst:49 msgid "Override the default Gravatar with a custom avatar" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:46 #: ../manage/roles/user-preferences-permissions.rst:50 msgid "``user_preferences.calendar``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:47 #: ../manage/roles/user-preferences-permissions.rst:51 msgid "Configure the calendar feed" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:49 #: ../manage/roles/user-preferences-permissions.rst:53 msgid "``user_preferences.device``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:50 #: ../manage/roles/user-preferences-permissions.rst:54 msgid "Manage device login sessions" msgstr "" @@ -9293,22 +9290,18 @@ msgstr "" msgid "To learn more, see :doc:`/manage/trigger/system-notifications`." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:54 #: ../manage/roles/user-preferences-permissions.rst:58 msgid "``user_preferences.language``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:55 #: ../manage/roles/user-preferences-permissions.rst:59 msgid "Configure the UI locale/language" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:57 #: ../manage/roles/user-preferences-permissions.rst:61 msgid "``user_preferences.linked_accounts``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:58 #: ../manage/roles/user-preferences-permissions.rst:62 msgid "Account linking" msgstr "" @@ -9332,7 +9325,6 @@ msgstr "" msgid "is the only way users can utilize third-party logins." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:63 #: ../manage/roles/user-preferences-permissions.rst:67 msgid "``user_preferences.notifications``" msgstr "" @@ -9359,7 +9351,6 @@ msgstr "" msgid "Customers can't receive ticket notifications at all." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:69 #: ../manage/roles/user-preferences-permissions.rst:73 msgid "``user_preferences.out_of_office``" msgstr "" @@ -9384,7 +9375,6 @@ msgstr "" msgid "they're replacing." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:75 #: ../manage/roles/user-preferences-permissions.rst:79 msgid "``user_preferences.overview_sorting``" msgstr "" @@ -9413,12 +9403,10 @@ msgstr "" msgid "overviews has no effect on custom orders." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:82 #: ../manage/roles/user-preferences-permissions.rst:86 msgid "``user_preferences.password``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:83 #: ../manage/roles/user-preferences-permissions.rst:87 msgid "Change account password" msgstr "" @@ -9435,7 +9423,6 @@ msgstr "" msgid "your only allowed authentication method." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:87 #: ../manage/roles/user-preferences-permissions.rst:91 msgid "``user_preferences.two_factor_authentication``" msgstr "" @@ -9472,7 +9459,7 @@ msgstr "" #: ../manage/scheduler.rst:19 msgid "" -"Schedulers can be used to send periodic reminder emails. Use :doc:`/system/" +"Schedulers can be used to send periodic reminder emails. Use :doc:`/misc/" "variables` to build highly-customized email templates." msgstr "" @@ -10468,7 +10455,7 @@ msgstr "" #: ../manage/text-modules.rst:57 msgid "" -"The example text modules below use :doc:`/system/variables` to dynamically " +"The example text modules below use :doc:`/misc/variables` to dynamically " "insert information like the customer's or agent's names." msgstr "" @@ -10808,8 +10795,8 @@ msgstr "" #: ../misc/object-conditions/basics.rst:144 #: ../misc/object-conditions/basics.rst:160 #: ../misc/object-conditions/basics.rst:168 -#: ../misc/object-conditions/basics.rst:178 ../settings/ticket.rst:2 -#: ../system/variables/ticket.rst:2 +#: ../misc/object-conditions/basics.rst:178 ../misc/variables/ticket.rst:2 +#: ../settings/ticket.rst:2 msgid "Ticket" msgstr "" @@ -11043,7 +11030,7 @@ msgstr "" #: ../manage/trigger/how-do-they-work.rst:79 msgid "" -"Certain actions (such as *email*, *SMS* and *notes*) support :doc:`/system/" +"Certain actions (such as *email*, *SMS* and *notes*) support :doc:`/misc/" "variables`, which can be used to build highly-customized message templates." msgstr "" @@ -11072,7 +11059,7 @@ msgstr "" msgid "" "You can also combine static text with placeholders for text fields. Remember " "that the placeholders' values have to be known during trigger runtime. Learn " -"more about :doc:`/system/variables`." +"more about :doc:`/misc/variables`." msgstr "" #: ../manage/trigger/how-do-they-work.rst:105 @@ -12037,7 +12024,7 @@ msgstr "" msgid "" "When switched on, a code editor will be shown below, where you can configure " "custom payload for your webhook in JSON format. To insert supported :doc:`/" -"system/variables` use ``::`` or ``#{`` shortcuts for autocomplete." +"misc/variables` use ``::`` or ``#{`` shortcuts for autocomplete." msgstr "" #: ../manage/webhook/add.rst:103 @@ -14614,11942 +14601,11833 @@ msgid "" "powerful conditions with AND/OR relations." msgstr "" -#: ../settings/branding.rst:10 -msgid "Product Name" +#: ../misc/variables.rst:2 +msgid "Variables" msgstr "" -#: ../settings/branding.rst:7 +#: ../misc/variables.rst:4 msgid "" -"Defines the name of the application, shown in the web interface, tabs and " -"title bar of the web browser." +"Please note that this is just an overview of available variables. It might " +"be incomplete or variables might not be available within some functions. If " +"you're missing variables or are not sure if something is not working as " +"expected, feel free to ask over at the `Community `_." msgstr "" -#: ../settings/branding.rst:10 -msgid "Default value: ``Zammad Helpdesk``" +#: ../misc/variables.rst:10 +msgid "" +"Variables can be called by typing ``::`` (just like text modules in the " +"frontend), as long as you're in a supported text field within the backend. " +"Zammad will display all variables being available within this context and " +"replace it to the variable as soon as you selected an entry." msgstr "" -#: ../settings/branding.rst:13 -msgid "Will be shown in the app and is included in email footers." +#: ../misc/variables.rst:15 +msgid "" +"You have an empty field which you referenced and it appears as ``-``? That's " +"currently working as designed - you might want to ensure that these fields " +"always have a value." msgstr "" -#: ../settings/branding.rst:19 -msgid "Logo" +#: ../misc/variables.rst:20 +msgid "Variable Categories" msgstr "" -#: ../settings/branding.rst:16 -msgid "Defines the logo of the application, shown in the login page of Zammad." +#: ../misc/variables.rst:31 +msgid "Wait, What About Custom Objects?" msgstr "" -#: ../settings/branding.rst:18 +#: ../misc/variables.rst:33 msgid "" -"Ensure to hit the \"Submit\" button after uploading the logo. Otherwise your " -"change will not be saved." +"Good point! Of course, we can't predict what objects you might create, but " +"we can give you a hint on how to put the puzzle together to get your custom " +"values." msgstr "" -#: ../settings/branding.rst:22 +#: ../misc/variables.rst:36 msgid "" -"Allows to set the default language of the Zammad instance. The here defined " -"locale mostly acts as a fallback for:" -msgstr "" - -#: ../settings/branding.rst:25 -msgid "user preferences (if Zammad can't detect the users locale)" +"For this, we'll talk about the inner part of the variable (so everything " +"within ``#{}``), please put the outer part around to have a valid variable. " +"The first part of the variable name consist of the object type. Currently " +"these are:" msgstr "" -#: ../settings/branding.rst:26 -msgid "CSV output (reporting, time accounting)" +#: ../misc/variables.rst:41 +msgid "Ticket (``ticket``)" msgstr "" -#: ../settings/branding.rst:30 -msgid "Define the timezone of your Zammad installation." +#: ../misc/variables.rst:42 +msgid "User (``user``)" msgstr "" -#: ../settings/branding.rst:32 -msgid "" -"This does not have any effect on timings for your agents or how Zammad " -"stores date and time values." +#: ../misc/variables.rst:43 +msgid "Organization (``organization``)" msgstr "" -#: ../settings/branding.rst:35 -msgid "Changing this value has direct consequences on the following areas:" +#: ../misc/variables.rst:44 +msgid "Group (``group``)" msgstr "" -#: ../settings/branding.rst:37 -msgid ":doc:`/manage/scheduler` tasks" +#: ../misc/variables.rst:46 +msgid "" +"The second part is the name of the attribute. This is the name you define " +"during object creation and can be found within the object attribute menu at " +"any time. The first and second part of a variable is divided by a point, e." +"g.: ``ticket.number`` which will in total be ``#{ticket.number}``." msgstr "" -#: ../settings/branding.rst:38 -msgid "search indexing (and thus reporting)" +#: ../misc/variables.rst:51 +msgid "" +"Now, in some situations it's possible that you'll need to use a third part. " +"The best example for such a situation would be a ``select`` or ``tree-" +"select`` field which will by default return the key value, not it's display " +"name. For this, just extend your variable with ``.value``. This will result " +"in ``#{ticket.select.value}``." msgstr "" -#: ../settings/branding.rst:40 -msgid "calendar subscriptions" +#: ../misc/variables.rst:60 +msgid "Using Translated Variables" msgstr "" -#: ../settings/branding.rst:41 -msgid "browser printing" +#: ../misc/variables.rst:62 +msgid "" +"If you want to use a translated variable in triggers or schedulers, you can " +"extend the placeholder like this: ``#{t(ticket.state.name)}``. The ``t`` " +"tells Zammad to search for fitting translated strings. The used output " +"language is based on the system language of Zammad which you can set in the " +"admin panel under :doc:`/settings/branding` or based on the selected locale " +"in the trigger/scheduler edit dialog." msgstr "" -#: ../settings/branding.rst:43 +#: ../misc/variables.rst:69 msgid "" -"Please note that some of above are fallbacks in case Zammad could not detect " -"the agents timezone correctly." +"A possible use-case: you want to send your customers updates on tickets via " +"trigger or scheduler which should include the state of the ticket. Using the " +"default ``#{ticket.state.name}`` (without the translation flag ``t()``) " +"would lead to the output of the original (english) name of the state." msgstr "" -#: ../settings/branding.rst:77 -msgid "Pretty Date" +#: ../misc/variables.rst:75 +msgid "Date and Time Formatting" msgstr "" -#: ../settings/branding.rst:47 +#: ../misc/variables.rst:77 msgid "" -"This setting allows you to define how Zammad should display time stamps " -"within the interface to all users." +"The system (trigger/scheduler selected) locale and timezone predefines a " +"default format of date and timestamp. This format is customizable by using " +"the ``dt()`` method." msgstr "" -#: ../settings/branding.rst:50 -msgid "" -"This does not have any effect on how Zammad returns e.g. time values via " -"variables." +#: ../misc/variables.rst:79 +msgid "The method arguments are as follows:" msgstr "" -#: ../settings/branding.rst:77 -msgid "Choose in between the following options:" +#: ../misc/variables.rst:81 +msgid "The date or timestamp variable you want to format." msgstr "" -#: ../settings/branding.rst:64 -msgid "relative" +#: ../misc/variables.rst:82 +msgid "The output format string." msgstr "" -#: ../settings/branding.rst:55 +#: ../misc/variables.rst:83 +msgid "The timezone to apply (optional)." +msgstr "" + +#: ../misc/variables.rst:85 +#: ../system/objects/external-data-source-example.rst:23 +msgid "**Example:**" +msgstr "" + +#: ../misc/variables.rst:86 msgid "" -"This timestamp shows a relative time span until it switches to a date. Over " -"time, it will change as follows:" +"``#{dt(ticket.updated_at, \"%A %Y-%m-%d %H:%M in the office\", \"Europe/" +"Berlin\")}``" msgstr "" -#: ../settings/branding.rst:58 -msgid "just now" +#: ../misc/variables.rst:87 +msgid "Monday, 2024-03-18 15:31 in the office" msgstr "" -#: ../settings/branding.rst:59 -msgid "5 minutes ago" +#: ../misc/variables.rst:89 +msgid "" +"If you want to use our example, make sure to paste the string above without " +"formatting (``CTRL+Shift+v``), otherwise it won't work." msgstr "" -#: ../settings/branding.rst:60 -msgid "3 days 1 hour ago" +#: ../misc/variables.rst:93 +msgid "The following table lists available format directives:" msgstr "" -#: ../settings/branding.rst:61 -msgid "``03/04/2022``" +#: ../misc/variables.rst:99 +msgid "Parameter" msgstr "" -#: ../settings/branding.rst:63 -msgid "Hovering the timestamp helps, you'll always get a clean timestamp then." +#: ../misc/variables.rst:102 +msgid "``%Y``" msgstr "" -#: ../settings/branding.rst:71 -msgid "absolute" +#: ../misc/variables.rst:103 +msgid "Year with 4 digits" msgstr "" -#: ../settings/branding.rst:67 -msgid "" -"This timestamp always includes the week day. For one week after creation, " -"the timestamp will not contain the date itself: Thursday 18:35." +#: ../misc/variables.rst:104 +msgid "Use ``%y`` for year with 2 digits" msgstr "" -#: ../settings/branding.rst:71 -msgid "After a week it will switch to: ``Friday 4. Mar 16:00``." +#: ../misc/variables.rst:105 +msgid "``%m``" msgstr "" -#: ../settings/branding.rst:76 -msgid "timestamp" +#: ../misc/variables.rst:106 +msgid "Month of year (as number with zero-padding)" msgstr "" -#: ../settings/branding.rst:74 -msgid "" -"This will cause Zammad to show a complete timestamp according to your locale " -"defaults. For English this could be e.g. ``2022/12/03 2:40 pm`` or for " -"German e.g. ``12.03.2022 14:40``." +#: ../misc/variables.rst:107 +msgid "Use ``%-m`` for month without zero-padding" msgstr "" -#: ../settings/branding.rst:78 -msgid "Default setting: ``relative``." +#: ../misc/variables.rst:108 +msgid "``%d``" msgstr "" -#: ../settings/security.rst:2 -msgid "Security" +#: ../misc/variables.rst:109 +msgid "Day of month (as number with zero-padding)" msgstr "" -#: ../settings/security.rst:4 -msgid "" -"For your overview we split each tab within security settings into its own " -"page:" +#: ../misc/variables.rst:110 +msgid "Use ``%e`` for day without zero-padding" msgstr "" -#: ../settings/security/base.rst:2 ../settings/system/base.rst:2 -#: ../settings/ticket.rst:8 -msgid "Base" +#: ../misc/variables.rst:111 +msgid "``%H``" msgstr "" -#: ../settings/security/base.rst:5 -msgid "New User Accounts" +#: ../misc/variables.rst:112 +msgid "Hour of day in 24h notation with zero-padding" msgstr "" -#: ../settings/security/base.rst:9 -msgid "" -"Activates the `register as a new customer` function on the login page. If " -"set to ``no`` only administrators or agents can create new accounts manually." +#: ../misc/variables.rst:113 +msgid "Use ``%k`` for hour without zero-padding" msgstr "" -#: ../settings/security/base.rst:13 ../settings/security/base.rst:38 -#: ../settings/security/base.rst:66 -msgid "Default setting: ``yes``" +#: ../misc/variables.rst:114 +msgid "``%I``" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing activated \"New User Accounts\" setting" +#: ../misc/variables.rst:115 +msgid "Hour of day in 12h notation with zero-padding" msgstr "" -#: ../settings/security/base.rst:22 +#: ../misc/variables.rst:116 msgid "" -"Deactivation of above function **does not** deactivate automatic account " -"creation! This means: If a user writes e.g. an email to Zammad and has no " -"account yet, Zammad will automatically create the account. User accounts are " -"a direct dependency of tickets and thus technically mandatory." +"Use ``%l`` for hour without zero-padding and ``%p`` / ``%P`` for meridian " +"indicator" msgstr "" -#: ../settings/security/base.rst:29 -msgid "Lost Password" +#: ../misc/variables.rst:117 +msgid "``%M``" msgstr "" -#: ../settings/security/base.rst:33 -msgid "" -"Activates the `lost password` function on the login page. If set to ``no`` " -"only administrators may change the user's password - users may update their " -"own password if they're still logged in and they have the required :doc:" -"`permission `." +#: ../misc/variables.rst:118 +msgid "Minute of hour" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing activated \"Lost Password\" setting" +#: ../misc/variables.rst:120 +msgid "``%S``" msgstr "" -#: ../settings/security/base.rst:49 -msgid "" -"With third party authentications - but especially LDAP - you may want to " -"disable this function. Zammad **will not** change third party login " -"passwords and instead set or change the local password!" +#: ../misc/variables.rst:121 +msgid "Second of Minute" msgstr "" -#: ../settings/security/base.rst:56 -msgid "Password Login" +#: ../misc/variables.rst:123 +msgid "``%A``" msgstr "" -#: ../settings/security/base.rst:60 -msgid "" -"Activates the username & password login by default and if no third-party " -"login is activated. Disabling password login on the Zammad login page only " -"takes effect if you enable any :doc:`third-party`." +#: ../misc/variables.rst:124 +msgid "Weekday name" msgstr "" -#: ../settings/security/base.rst:64 -msgid "See :doc:`third-party` for supported third-party logins." +#: ../misc/variables.rst:125 +msgid "Use ``%a`` for abbreviated name or ``%^A`` for uppercase name" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing de-activated \"Password Login\" setting" +#: ../misc/variables.rst:126 +msgid "``%B``" msgstr "" -#: ../settings/security/base.rst:77 -msgid "" -"To help administrators to overcome \"login issues\", Zammad automatically " -"offers a password request for administrator users. This allows you to adjust " -"Third-Party applications even if the login does no longer work!" +#: ../misc/variables.rst:127 +msgid "Month name" msgstr "" -#: ../settings/security/base.rst:84 -msgid "Session Timeout" +#: ../misc/variables.rst:128 +msgid "Use ``%b`` for abbreviated name" msgstr "" -#: ../settings/security/base.rst:86 -msgid "" -"All settings below by default are set to ``4 weeks``. Session Timeout " -"defines the life time of a users session. As soon as it's reached, Zammad " -"will automatically log off the session in question." +#: ../misc/variables.rst:129 +msgid "``%U``" msgstr "" -#: ../settings/security/base.rst:91 -msgid "" -"Zammad takes the highest value set assigned for the user based on the " -"permissions." +#: ../misc/variables.rst:130 +msgid "Week number of current year" msgstr "" -#: ../settings/security/base.rst:94 -msgid "``admin``" +#: ../misc/variables.rst:131 +msgid "Use ``%W`` for a different calculation method" msgstr "" -#: ../settings/security/base.rst:96 -msgid "``ticket.customer``" +#: ../misc/variables.rst:134 +msgid "" +"We support the known format directives for the Ruby built-in method " +"``strftime`` of the ``DateTime`` class. For more information, see `here " +"`_." msgstr "" -#: ../settings/security/base.rst:97 -msgid "``default`` (fallback if user doesn't have above permissions set)" +#: ../misc/variables/article.rst:2 +msgid "Articles" msgstr "" -#: ../settings/security/base.rst:99 +#: ../misc/variables/article.rst:4 ../misc/variables/config.rst:4 +#: ../misc/variables/current-user.rst:4 ../misc/variables/ticket.rst:4 msgid "" -"All settings act independently from each other allowing you to disable the " -"timeouts for e.g. admins, but not agents." +"If you're missing variables or are not sure if something is not working as " +"expected, feel free to ask over at the `Community `_." msgstr "" -#: ../settings/security/base.rst:115 -#: ../system/integrations/checkmk/api-reference.rst:13 -msgid "Example" +#: ../misc/variables/article.rst:6 +msgid "" +"Below you can find all available ticket article-based variables within " +"Zammad. These can be called via triggers for example. If you're unsure if " +"Zammad does support variables at the point you're at, you can try to type " +"``::`` to check." msgstr "" -#: ../settings/security/base.rst:107 -msgid "Let's suppose you configured the following session timeouts" +#: ../misc/variables/article.rst:9 ../misc/variables/config.rst:9 +#: ../misc/variables/ticket.rst:9 +msgid "" +"The below list gives you an example what kind of data you can expect, it's " +"not intended to explain the data itself." msgstr "" -#: ../settings/security/base.rst:104 -msgid "default: 3 weeks" +#: ../misc/variables/article.rst:11 +msgid "Article Variables" msgstr "" -#: ../settings/security/base.rst:105 -msgid "admin: 2 weeks" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "name" msgstr "" -#: ../settings/security/base.rst:106 -msgid "ticket.agent: 4 weeks" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "variable" msgstr "" -#: ../settings/security/base.rst:107 -msgid "ticket.customer: 1 week" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "example" msgstr "" -#: ../settings/security/base.rst:115 -msgid "This results in the following situations" +#: ../misc/variables/article.rst:1 +msgid "Article > Cc" msgstr "" -#: ../settings/security/base.rst:110 -msgid "a user with ``admin`` permission will have a timeout of 2 weeks" +#: ../misc/variables/article.rst:1 +msgid "``#{article.cc}``" msgstr "" -#: ../settings/security/base.rst:111 -msgid "" -"a user with ``admin`` and ``ticket.agent`` permissions will have a timeout " -"of 2 weeks" +#: ../misc/variables/article.rst:1 +msgid "``jdoe@example.com, company@example.com``" msgstr "" -#: ../settings/security/base.rst:113 -msgid "" -"a user with ``ticket.customer`` permission will have a timeout of 1 week" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Address" msgstr "" -#: ../settings/security/base.rst:115 -msgid "" -"a user with neither ``admin``, ``ticket.agent`` nor ``ticket.customer`` " -"permissions will have a timeout of 3 weeks" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.address}``" msgstr "" -#: ../settings/security/password.rst:4 -msgid "" -"This section allows you to define password requirements for the local user " -"accounts." +#: ../misc/variables/article.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:9 -msgid "" -"Zammad does **not** allow you to change your LDAP password, instead, it will " -"set a password in its local database which might confuse your users. This " -"might be addressed in the future by `#1169 `_." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Department" msgstr "" -#: ../settings/security/password.rst:14 -msgid "**Exception for admins**" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.department}``" msgstr "" -#: ../settings/security/password.rst:16 -msgid "" -"Please note that below password policies *do not* affect administrators " -"setting passwords on user accounts. While this seems strange and not safe we " -"believe that an administrator knowing an user's password is insecure as well." +#: ../misc/variables/article.rst:1 +msgid "``Sales`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:21 -msgid "The suggested workflow is either:" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Email" msgstr "" -#: ../settings/security/password.rst:23 -msgid "" -"to use third party logins to not require local passwords at all **- or -**" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.email}``" msgstr "" -#: ../settings/security/password.rst:25 -msgid "to require your *user to reset the password* upon first login." +#: ../misc/variables/article.rst:1 +msgid "``jdoe@example.com``" msgstr "" -#: ../settings/security/password.rst:27 -msgid "" -"This way administrators are not required to set a user's password at all!" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Fax" msgstr "" -#: ../settings/security/password.rst:31 -msgid "Maximum Failed Logins" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.fax}``" msgstr "" -#: ../settings/security/password.rst:33 -msgid "" -"You can choose a value between ``4`` and ``20``. This defines how often a " -"login to a user account may fail until Zammad will lock it. Your users can " -"always use the \"forgot password\" function to change their password and " -"unlock their account." -msgstr "" - -#: ../settings/security/password.rst:38 -msgid "The default value is ``10``." +#: ../misc/variables/article.rst:1 +msgid "``+4930123456789`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:42 -msgid "Beside changing the user's password, you can also unlock accounts via" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Firstname" msgstr "" -#: ../settings/security/password.rst:44 -msgid ":ref:`user management list `" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.firstname}``" msgstr "" -#: ../settings/security/password.rst:45 -msgid ":docs:`console `" +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Joe`` or empty if not set" msgstr "" -#: ../settings/security/password.rst:46 -msgid ":docs:`API `" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Lastname" msgstr "" -#: ../settings/security/password.rst:50 -msgid "Failed logins via LDAP no longer lock accounts." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.lastname}``" msgstr "" -#: ../settings/security/password.rst:53 -msgid "2 Lower Case And 2 Upper Case Characters" +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +#: ../misc/variables/ticket.rst:1 +msgid "``Doe`` or empty if not set" msgstr "" -#: ../settings/security/password.rst:55 -msgid "" -"You can add complexity to passwords by enforcing at least 2 upper and lower " -"case characters." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Login" msgstr "" -#: ../settings/security/password.rst:58 ../settings/security/password.rst:83 -msgid "The default value is ``no``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.login}``" msgstr "" -#: ../settings/security/password.rst:62 -msgid "Minimum Length" +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +#: ../misc/variables/ticket.rst:1 +msgid "``jdoe``" msgstr "" -#: ../settings/security/password.rst:64 -msgid "" -"This defines the minimum password length required for users to provide (from " -"``4`` to ``20``)." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Mobile" msgstr "" -#: ../settings/security/password.rst:67 -msgid "The default value is ``6``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.mobile}``" msgstr "" -#: ../settings/security/password.rst:71 -msgid "Digit Required" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Note" msgstr "" -#: ../settings/security/password.rst:73 -msgid "This enforces your users to use at least one digit within the password." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.note}``" msgstr "" -#: ../settings/security/password.rst:75 -msgid "The default value is ``yes``." +#: ../misc/variables/article.rst:1 +msgid "``Some note about user`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:78 -msgid "Special Character Required" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Phone" msgstr "" -#: ../settings/security/password.rst:80 -msgid "" -"This setting allows you to improve your password quality even more by " -"enforcing the password to contain at least one special character." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.phone}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:2 -msgid "SSL Certificates" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > VIP" msgstr "" -#: ../settings/security/ssl-certificates.rst:7 -msgid "" -"Zammad offers the possibility to upload custom certificates and custom " -"Certificate Authority (CA) certificates. This can be useful if you want to " -"connect Zammad the secure way to other systems which are using custom " -"certificates." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.vip}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:12 -msgid "" -"An example usecase might be: You have an internal LDAP server that is not " -"accessible from the internet, and you want a SSL-encrypted connection, using " -"a custom certificate." +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +msgid "``true`` or ``false``" msgstr "" -#: ../settings/security/ssl-certificates.rst:19 -msgid "" -"You should have an existing custom certificate file and/or a custom CA " -"certificate file, which you want to add to Zammad. As filetype ``.crt`` is " -"supported and the certificate format has to be PEM (Base64 ASCII)." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Web" msgstr "" -#: ../settings/security/ssl-certificates.rst:25 -msgid "" -"When you import a custom CA certificate, all certificates generated with " -"this are trusted. This can be useful if you have more than one system/" -"certificate you want to connect to and the certificates are issued from the " -"same custom CA." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.web}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:31 -msgid "Add a Certificate" +#: ../misc/variables/article.rst:1 +msgid "``https://zammad.com`` or empty if not set in user object" msgstr "" -#: ../settings/security/ssl-certificates.rst:33 -msgid "" -"To add a custom certificate or a custom CA certificate, head over to the " -"Admin panel > Settings > Security > SSL Certificates. Here you can find a " -"\"Add SSL Certificate\" button. In the dialog you can either select a " -"certificate file or paste the content of the certificate:" +#: ../misc/variables/article.rst:1 +msgid "Article > Created" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate adding dialog" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_at}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:43 -msgid "" -"After selecting a file or pasting the content of the certificate, click on " -"the \"Add\" button to finally upload it to Zammad. Then, the certificates " -"are immediately effective, no restart or similar required." +#: ../misc/variables/article.rst:1 +msgid "``2019-10-08 15:24:47 UTC``" msgstr "" -#: ../settings/security/ssl-certificates.rst:49 -msgid "" -"Please note that only single certificate files are supported. That means if " -"you want to import a certificate / CA certificate, it must contain **only " -"one** certificate." +#: ../misc/variables/article.rst:1 +msgid "Article > From" msgstr "" -#: ../settings/security/ssl-certificates.rst:54 -msgid "Certificate Overview" +#: ../misc/variables/article.rst:1 +msgid "``#{article.from}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:56 +#: ../misc/variables/article.rst:1 msgid "" -"After you added a certificate, you can see a table with information for each " -"added certificate:" +"``Joe Doe `` may differ, depends on ``FROM`` of send mail" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing table of added certificates" +#: ../misc/variables/article.rst:1 +msgid "Article > Sender > Name" msgstr "" -#: ../settings/security/ssl-certificates.rst:64 -msgid "" -"Here you can download the certificate or delete it, if you don't need it " -"anymore." +#: ../misc/variables/article.rst:1 +msgid "``#{article.sender.name}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:68 -msgid "Deleting Certificates" +#: ../misc/variables/article.rst:1 +msgid "``Customer``, ``Agent`` or ``System``" msgstr "" -#: ../settings/security/ssl-certificates.rst:70 -msgid "" -"If you want to delete a specific certificate, you can do it by clicking on " -"the menu in the actions column and selecting delete:" +#: ../misc/variables/article.rst:1 +msgid "Article > Subject" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate deletion button" +#: ../misc/variables/article.rst:1 +msgid "``#{article.subject}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:79 -msgid "Downloading Certificates" +#: ../misc/variables/article.rst:1 +msgid "``My amazing subject``" msgstr "" -#: ../settings/security/ssl-certificates.rst:81 -msgid "" -"If you want to download your certificates, you can do this as well via " -"corresponding action buttons." +#: ../misc/variables/article.rst:1 +msgid "Article > Text" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate download button" +#: ../misc/variables/article.rst:1 +msgid "``#{article.body}``" msgstr "" -#: ../settings/security/third-party.rst:13 -msgid "Login Providers" +#: ../misc/variables/article.rst:1 +msgid "``Test`` without formatting (plain)" msgstr "" -#: ../settings/security/third-party.rst:2 -msgid "Third-Party Applications" +#: ../misc/variables/article.rst:1 +msgid "Article > TicketID" msgstr "" -#: ../settings/security/third-party.rst:4 -msgid "" -"Third party authentication is a great way to help your users to login to " -"Zammad more easily. If the account is yet unknown, Zammad will create a new " -"user automatically, without the user needed to interact (e.g. type in his " -"name). Another big advantage of this feature is that your user doesn't need " -"to remember another password." +#: ../misc/variables/article.rst:1 +msgid "``#{article.ticket_id}``" msgstr "" -#: ../settings/security/third-party.rst:10 -msgid "" -"You can deactivate logging in via :ref:`security_password_login` if any of " -"the mentioned authentication providers are enabled in your instance." +#: ../misc/variables/article.rst:1 +msgid "``1`` (not ticket number)" msgstr "" -#: ../settings/security/third-party.rst:27 -msgid "" -"We're currently missing documentation for the following login providers:" +#: ../misc/variables/article.rst:1 +msgid "Article > To" msgstr "" -#: ../settings/security/third-party.rst:29 -msgid "LinkedIn" +#: ../misc/variables/article.rst:1 +msgid "``#{article.to}``" msgstr "" -#: ../settings/security/third-party.rst:30 -msgid "Weibo" +#: ../misc/variables/article.rst:1 +msgid "``helpdesk@example.com``" msgstr "" -#: ../settings/security/third-party.rst:35 -msgid "Automatic Account Link on Initial Logon" +#: ../misc/variables/article.rst:1 +msgid "Article > Type > Name" msgstr "" -#: ../settings/security/third-party.rst:37 -msgid "" -"In general there's two possible options for Zammad on how to deal with " -"already known users as they try to authenticate against a third-party " -"application. By default, Zammad will not automatically link \"unknown\" " -"authentication providers to existing accounts." +#: ../misc/variables/article.rst:1 +msgid "``#{article.type.name}``" msgstr "" -#: ../settings/security/third-party.rst:42 +#: ../misc/variables/article.rst:1 msgid "" -"This means that the user has to manually link authentication providers to " -"their accounts (for more about this :user-docs:`consult the user " -"documentation `)." +"``email`` (`list of article types `_)" msgstr "" -#: ../settings/security/third-party.rst:46 -msgid "" -"Sometimes this doesn't come in handy as this also means you'll receive error " -"messages about \"email address being in use already\" for (yet) unknown " -"third-party authentication methods." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Address" msgstr "" -#: ../settings/security/third-party.rst:50 -msgid "" -"If you want to allow your users to always be able to log in, no matter what, " -"you may want to enable ``Automatic account link on initial logon``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.address}``" msgstr "" -#: ../settings/security/third-party.rst:None -msgid "" -"Screenshot highlighting the \"Automatic account link on initial logon\"\n" -"setting" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Department" msgstr "" -#: ../settings/security/third-party.rst:60 -msgid "Automatic Account Linking Notification" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.department}``" msgstr "" -#: ../settings/security/third-party.rst:64 -msgid "" -"To improve security and your users awareness, you can enable Zammad to " -"notify your users when a new third-party application has been linked to " -"their account." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Email" msgstr "" -#: ../settings/security/third-party.rst:68 -msgid "" -"This notification is sent out once per third-party application. Zammad does " -"also mention the method used, e.g.: ``Microsoft``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.email}``" msgstr "" -#: ../settings/security/third-party.rst:71 -msgid "By default this setting is not active (set to ``no``)." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Fax" msgstr "" -#: ../settings/security/third-party.rst:0 -msgid "" -"Screenshot showing sample notification mail after initial\n" -"third-party linking" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.fax}``" msgstr "" -#: ../settings/security/third-party.rst:85 -msgid "" -"This notification is only sent if the account in question already exists. If " -"the login via the third-party also creates the missing account, the " -"notification will be skipped." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Firstname" msgstr "" -#: ../settings/security/third-party.rst:89 -msgid "This means it only affects:" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.firstname}``" msgstr "" -#: ../settings/security/third-party.rst:91 -msgid "manual account linking within the third-party page of the users profile" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Lastname" msgstr "" -#: ../settings/security/third-party.rst:92 -msgid "" -"logging into an existing local account by utilizing the *automatic account " -"link on initial logon* functionality" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.lastname}``" msgstr "" -#: ../settings/security/third-party.rst:None -msgid "" -"Screenshot showing the \"automatic account linking notification\"\n" -"setting" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Login" msgstr "" -#: ../settings/security/third-party.rst:100 -msgid "No User Creation on Logon" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.login}``" msgstr "" -#: ../settings/security/third-party.rst:102 -msgid "" -"By default, Zammad will create a new user account if the user logs in via a " -"third-party application and the account doesn't exist yet." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Mobile" msgstr "" -#: ../settings/security/third-party.rst:105 -msgid "" -"If you want to prevent Zammad from creating new accounts on logon, you can " -"disable this feature by setting ``No user creation on logon`` to ``yes``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.mobile}``" msgstr "" -#: ../settings/security/third-party.rst:None -msgid "Screenshot showing the \"no user creation on logon\" setting" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Note" msgstr "" -#: ../settings/security/third-party/facebook.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via Facebook To do " -"so, you need to follow these steps:" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.note}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:9 -msgid "Register Facebook App" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Phone" msgstr "" -#: ../settings/security/third-party/facebook.rst:11 -msgid "" -"Visit [https://developers.facebook.com/apps/] and click on \"Add a new App\"" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.phone}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "initial page" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > VIP" msgstr "" -#: ../settings/security/third-party/facebook.rst:17 -msgid "After that enter the app settings" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.vip}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "Create App" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Web" msgstr "" -#: ../settings/security/third-party/facebook.rst:22 -msgid "Navigate to \"Settings\" and fill in this infromation" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.web}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "App Settings" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated" msgstr "" -#: ../settings/security/third-party/facebook.rst:27 -msgid "Navigate to app review and Check \"Make [appname] public?\"" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_at}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "App Review" +#: ../misc/variables/article.rst:1 +msgid "Article > Visibility" msgstr "" -#: ../settings/security/third-party/facebook.rst:35 -msgid "Configure Zammad as Facebook App" +#: ../misc/variables/article.rst:1 +msgid "``#{article.internal}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:37 -msgid "" -"Navigate to \"Admin -> Security -> Third Party Applications\" and enter the " -"App ID and the App Secret. You can find this Key in the Dashbard of your " -"Facebok app." +#: ../misc/variables/article.rst:1 +msgid "``false`` or ``true`` (false if not internal)" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "Zammad Configuration" +#: ../misc/variables/article.rst:1 +msgid "Article Text as HTML (not referenced)" msgstr "" -#: ../settings/security/third-party/facebook.rst:44 -#: ../settings/security/third-party/github.rst:43 -#: ../settings/security/third-party/gitlab.rst:46 -msgid "" -"Now you can link accounts via \"Avatar -> Profile -> Link Accounts\" or " -"login via Zammad login page." +#: ../misc/variables/article.rst:1 +msgid "``#{article.body_as_html}``" msgstr "" -#: ../settings/security/third-party/github.rst:2 -#: ../system/integrations/github.rst:2 -msgid "GitHub" +#: ../misc/variables/article.rst:1 +msgid "``Test`` with formatting" msgstr "" -#: ../settings/security/third-party/github.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via GitHub. To " -"activate the quick login you need to enable OAuth for GitHub." +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "Ticket > Article#" msgstr "" -#: ../settings/security/third-party/github.rst:8 -msgid "Register GitHub App" +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "``#{ticket.article_count}``" msgstr "" -#: ../settings/security/third-party/github.rst:10 -msgid "" -"Visit https://www.github.com/settings/applications/new and enter the app " -"settings. As callback URL enter \"https://zammad_host/auth/github/callback\" " -"where zammad_host has to be replaced with your Zammad FQDN" +#: ../misc/variables/article.rst:1 +msgid "``1`` number of ticket articles" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "Register OAuth app on www.github.com" +#: ../misc/variables/config.rst:2 +msgid "Config" msgstr "" -#: ../settings/security/third-party/github.rst:19 -msgid "Configure Zammad as GitHub App" +#: ../misc/variables/config.rst:6 +msgid "" +"Below you'll find config related variables. These hold useful configuration " +"information that you can use within e.g. triggers to show necessary " +"information to your customer." msgstr "" -#: ../settings/security/third-party/github.rst:21 -msgid "" -"Enter the \"APP ID\" and the \"APP SECRET\" from the GitHub OAUTH " -"Applications Dashboard" +#: ../misc/variables/config.rst:11 +msgid "Config Variables" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub config in Zammad admin interface" +#: ../misc/variables/config.rst:1 +msgid "Config > Fully Qualified Domain Name" msgstr "" -#: ../settings/security/third-party/github.rst:28 -msgid "" -"After you configured the GitHub credentials and activated the login method, " -"you should see a new icon on the login page." +#: ../misc/variables/config.rst:1 +msgid "``#{config.fqdn}``" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub logo on login page" +#: ../misc/variables/config.rst:1 +msgid "``zammad.example.com``" msgstr "" -#: ../settings/security/third-party/github.rst:34 -msgid "" -"If you click on the icon you will be redirected to GitHub and see something " -"similar to this:" +#: ../misc/variables/config.rst:1 +msgid "Config > HTTP type" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub oauth page" +#: ../misc/variables/config.rst:1 +msgid "``#{config.http_type}``" msgstr "" -#: ../settings/security/third-party/github.rst:40 -#: ../settings/security/third-party/gitlab.rst:42 -msgid "" -"When you grant the access you will be redirected to your Zammad instance and " -"logged in as a customer." +#: ../misc/variables/config.rst:1 +msgid "``https`` or ``http``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:2 -msgid "Gitlab" +#: ../misc/variables/config.rst:1 +msgid "Config > Organization" msgstr "" -#: ../settings/security/third-party/gitlab.rst:4 +#: ../misc/variables/config.rst:1 +msgid "``#{config.organization}``" +msgstr "" + +#: ../misc/variables/config.rst:1 msgid "" -"It is possible to create a quick login for your helpdesk via Gitlab. To " -"activate the quick login you need to enable OAuth for Gitlab." +"``Zammad GmbH`` value set in `Branding `_" msgstr "" -#: ../settings/security/third-party/gitlab.rst:8 -msgid "Register Gitlab App" +#: ../misc/variables/config.rst:1 +msgid "Config > Product Name" msgstr "" -#: ../settings/security/third-party/gitlab.rst:10 -msgid "To register an app in Gitlab open your profile and select applications." +#: ../misc/variables/config.rst:1 +msgid "``#{config.product_name}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:12 +#: ../misc/variables/config.rst:1 msgid "" -"As callback URL enter \"https://zammad-fqdn/auth/gitlab/callback\" where " -"zammad-fqdn has to be replaced with your Zammad FQDN" +"``Helpdesk`` value set in `Branding `_" msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Register OAuth app on gitlab instance" +#: ../misc/variables/config.rst:1 +msgid "Config > SystemID" msgstr "" -#: ../settings/security/third-party/gitlab.rst:18 -msgid "Just select *read_user* under scopes as in the screenshot and save it." +#: ../misc/variables/config.rst:1 +msgid "``#{config.system_id}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:21 -msgid "Configure Zammad as Gitlab App" +#: ../misc/variables/config.rst:1 +msgid "``31`` (value between 1 and 99)" msgstr "" -#: ../settings/security/third-party/gitlab.rst:23 -msgid "" -"Enter the \"APP ID\" and the \"APP SECRET\" from the Gitlab OAUTH " -"Applications Dashboard and your Gitlab-URL in the \"SITE\" field." +#: ../misc/variables/config.rst:1 +msgid "Config > Ticket Hook" msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab config in Zammad admin interface" +#: ../misc/variables/config.rst:1 +msgid "``#{config.ticket_hook}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:30 -msgid "" -"After you configured the Gitlab credentials and activated the login method, " -"you should see a new icon on the login page." +#: ../misc/variables/config.rst:1 +msgid "``Ticket#``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab logo on login page" +#: ../misc/variables/current-user.rst:2 +msgid "Current User" msgstr "" -#: ../settings/security/third-party/gitlab.rst:36 +#: ../misc/variables/current-user.rst:6 msgid "" -"If you click on the icon you will be redirected to Gitlab and see something " -"similar to this:" +"Current user variables always return values of the current user that caused " +"e.g. a trigger to run." msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab oauth page" +#: ../misc/variables/current-user.rst:8 +msgid "" +"Due to the above fact, these variables are often not (yet) set or available " +"for usage." msgstr "" -#: ../settings/security/third-party/google.rst:4 +#: ../misc/variables/current-user.rst:10 msgid "" -"With some easy and fast steps, you can enable Zammad to authenticate your " -"users via Google." +"In situations where e.g. schedulers or triggers run, this most likely is " +"nothing you want to use." msgstr "" -#: ../settings/security/third-party/google.rst:8 -msgid "Register a Google App" +#: ../misc/variables/current-user.rst:13 +msgid "Current User Variables" msgstr "" -#: ../settings/security/third-party/google.rst:10 -msgid "" -"First of all, we need to create a new project - you can skip this step if " -"you already have one." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Address" msgstr "" -#: ../settings/security/third-party/google.rst:15 -msgid "" -"Use this link to create a new project: https://console.cloud.google.com/" -"projectcreate" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.address}``" msgstr "" -#: ../settings/security/third-party/google.rst:18 -msgid "" -"Now expand the menu, expand \"APIs & Services\" and select \"Credentials\". " -"Go to the tab \"OAuth consent screen\" first and ensure to fill in the " -"requested information - without doing so you can't create credentials!" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set" msgstr "" -#: ../settings/security/third-party/google.rst:None -msgid "Creating a consent screen" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Avatar" msgstr "" -#: ../settings/security/third-party/google.rst:25 -msgid "" -"After filling in and saving the consent screen information, you can go to " -"the \"Credentials\" tab and create new \"OAuth client ID\"-Credentials." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/google.rst:28 -msgid "" -"Fill in the necessary information as follows and replace ``zammad_host`` " -"with your FQDN:" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "avatar picture with width and height in pixel (e.g. 60,60)" msgstr "" -#: ../settings/security/third-party/google.rst:31 -msgid "**Application type** ``[x] Web application``" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created at" msgstr "" -#: ../settings/security/third-party/google.rst:34 -msgid "**Authorized JavaScript origins** ``https://zammad_host/``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_at}``" msgstr "" -#: ../settings/security/third-party/google.rst:37 -msgid "" -"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" -"callback``" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC``" msgstr "" -#: ../settings/security/third-party/google.rst:None -msgid "Adding a new OAuth client ID" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Address" msgstr "" -#: ../settings/security/third-party/google.rst:43 -msgid "" -"After creating the credentials, go to your Zammad installation and navigate " -"to \"Admin > Security > Third Party Applications\" > Google. Enter your " -"Client ID and Client secret here." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.address}``" msgstr "" -#: ../settings/security/third-party/google.rst:None -msgid "Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Avatar" msgstr "" -#: ../settings/security/third-party/google.rst:50 -msgid "After submitting, the login via Google can be used." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:2 -msgid "Microsoft" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Department" msgstr "" -#: ../settings/security/third-party/microsoft.rst:4 -msgid "" -"Zammad's Microsoft connection allows your users with Microsoft accounts to " -"login. This works for Azure users as well and can be an alternative to :doc:" -"`/system/integrations/ldap/index`." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.department}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:10 -msgid "" -"This documentation part does not cover our :doc:`📧 Microsoft 365 email " -"channel `." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Sales`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screenshot showing Microsoft login button on Zammad login screen." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Email" msgstr "" -#: ../settings/security/third-party/microsoft.rst:30 -#: ../settings/security/third-party/microsoft.rst:53 -msgid "Supported account types:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.email}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:22 -msgid "" -"Please note that Zammad only supports these account types (App dependent):" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``jdoe@customer.tld``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:35 -msgid "Avatars of signing in users:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Fax" msgstr "" -#: ../settings/security/third-party/microsoft.rst:33 -msgid "" -"Zammad currently ignores user avatars. If the user is registered with e.g. " -"Gravatar, Zammad will fetch the avatar from there if enabled. See :doc:" -"`Zammad Image Service ` for more." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.fax}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:38 -msgid "Step 1 - Register a Microsoft App for Zammad" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``004930123464789`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:40 -msgid "" -"Login to the `Microsoft Azure Portal `_ and " -"navigate to App registrations to create a new app. Provide the requested " -"information as follows and register your app." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Firstname" msgstr "" -#: ../settings/security/third-party/microsoft.rst:46 -msgid "Name:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.firstname}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:45 -msgid "" -"Any meaningful name fitting, this name will be displayed to users trying to " -"authenticate with this app." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``John`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:49 -msgid "Choose one of the above mentioned account types (see Limitations)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Lastname" msgstr "" -#: ../settings/security/third-party/microsoft.rst:51 -msgid "" -"The correct account type depends on your use case. If you want to use the " -"authentication internal only, choose the first option. If you're unsure, use " -"the \"Help me choose...\" link." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.lastname}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:58 -msgid "Redirect URI (optional):" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Login" msgstr "" -#: ../settings/security/third-party/microsoft.rst:56 -msgid "" -"Select web and provide your callback URL. The callback URL looks like this: " -"``https://zammad.domain.tld/auth/microsoft_office365/callback``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.login}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to register a Microsoft app" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Mobile" msgstr "" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "Within **API permissions** add the following permissions:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.mobile}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:69 -msgid "``User.Read``" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``0049176123456789`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "Contacts" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Note" msgstr "" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "``Contacts.Read``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.note}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:73 -msgid "" -"You can find these permissions within *Microsoft Graph → Delegated " -"permissions*." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Some note to this user`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to add required API permissions" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Phone" msgstr "" -#: ../settings/security/third-party/microsoft.rst:80 -msgid "" -"Within **Certificates & secrets** create a new client secret. Note down the " -"returned secret **value** for later. **Do not** use the secret ID!" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.phone}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to create a new app secret" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``004930123456789`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:88 -msgid "" -"From **Overview** copy your apps *Application (client) ID*. If you're using " -"a single tenant app, please also copy *Directory (tenant) ID*. You now have " -"all required information for Zammad." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > VIP" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to retreive application client and tenant IDs" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.vip}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:98 -msgid "Step 2 - Add App Credentials to Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Web" msgstr "" -#: ../settings/security/third-party/microsoft.rst:100 -msgid "" -"Navigate to Security > Third-party Applications (Tab) within Zammad's admin " -"settings. Scroll down to the section *Authentication via Microsoft* and fill " -"in the required information." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.web}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:105 -msgid "App ID:" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``https://zammad.org`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:105 -msgid "This is your *Application (client) ID*." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Department" msgstr "" -#: ../settings/security/third-party/microsoft.rst:108 -msgid "App secret:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.department}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:108 -msgid "This is your *client secret* (value)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Email" msgstr "" -#: ../settings/security/third-party/microsoft.rst:113 -msgid "App Tenant ID:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.email}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:111 -msgid "" -"**optional** only required for apps that use account type *Accounts in this " -"organizational directory only (Default Directory only - Single tenant).*" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Fax" msgstr "" -#: ../settings/security/third-party/microsoft.rst:115 -msgid "" -"Apply your settings by pressing submit and activate *Authentication via " -"Microsoft*." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.fax}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "" -"Screencast showing how to add app credentials and activating the\n" -"authentication method" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Firstname" msgstr "" -#: ../settings/security/third-party/saml.rst:2 -msgid "SAML" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.firstname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:4 -msgid "" -"Connect your SAML (Security Assertion Markup Language) identity provider as " -"a single sign-on (SSO) method." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Lastname" msgstr "" -#: ../settings/security/third-party/saml.rst:7 -msgid "" -"SAML is an open standard for SSO authentication (among other things). Sign-" -"ins are shared across multiple **service providers** and managed by a " -"central **identity provider** (IdP)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.lastname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:11 -msgid "" -"In this case, the service provider is Zammad, and the IdP is a software " -"service that you either host or subscribe to (*e.g.,* `Keycloak `_, `Redhat SSO Server `_, `ADFS `_, or `Okta `_)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Login" msgstr "" -#: ../settings/security/third-party/saml.rst:18 -msgid "" -"This guide assumes you are already using SAML within your organization (i." -"e., that your IdP is fully set up)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.login}``" msgstr "" -#: ../settings/security/third-party/saml.rst:21 -msgid "" -"Please note: Our instructions are based on connecting Zammad with Keycloak." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Mobile" msgstr "" -#: ../settings/security/third-party/saml.rst:25 -msgid "Step 1: Configure Your IdP" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.mobile}``" msgstr "" -#: ../settings/security/third-party/saml.rst:28 -msgid "Add Zammad as a Client/App" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Note" msgstr "" -#: ../settings/security/third-party/saml.rst:30 -msgid "" -"Import Zammad into your IdP using the XML configuration found at ``https://" -"your.zammad.domain/auth/saml/metadata``." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.note}``" msgstr "" -#: ../settings/security/third-party/saml.rst:33 -msgid "" -"If your IdP doesn't support XML import, you will have to configure Zammad as " -"a new client/app manually using the above XML metadata file for reference." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Domain based assignment" msgstr "" -#: ../settings/security/third-party/saml.rst:36 -msgid "For instance, when you see this tag:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.domain_assignment}``" msgstr "" -#: ../settings/security/third-party/saml.rst:42 -msgid "" -"Set the **Assertion Consumer Service Binding URL** (sometimes also listed as " -"**Valid Redirect URIs**) to ``http://your.zammad.domain/auth/saml/callback``." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Domain" msgstr "" -#: ../settings/security/third-party/saml.rst:47 -msgid "Set Up User Attribute Mapping" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.domain}``" msgstr "" -#: ../settings/security/third-party/saml.rst:49 -msgid "" -"Zammad requests the following user attributes (or “properties”) from the IdP:" +#: ../misc/variables/current-user.rst:1 +msgid "``zammad.com`` or empty if not set" msgstr "" -#: ../settings/security/third-party/saml.rst:51 -msgid "Email address (``email``)" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Name" msgstr "" -#: ../settings/security/third-party/saml.rst:52 -msgid "Full name (``name``)" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.name}``" msgstr "" -#: ../settings/security/third-party/saml.rst:53 -msgid "Given name (``first_name``)" +#: ../misc/variables/current-user.rst:1 +msgid "``Zammad GmbH``" msgstr "" -#: ../settings/security/third-party/saml.rst:54 -msgid "Family name (``last_name``)" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Note" msgstr "" -#: ../settings/security/third-party/saml.rst:56 -msgid "" -"You may need to set up “mappers” (or “mappings”) to tell your IdP how user " -"attributes in SAML correspond to those in Zammad. For a more detailed " -"breakdown, refer to the XML metadata file referenced in the previous section." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.note}``" msgstr "" -#: ../settings/security/third-party/saml.rst:62 -msgid "Per-IdP Instructions" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``A note to the organization of the user`` or empty if not set" msgstr "" -#: ../settings/security/third-party/saml.rst:102 -msgid "Keycloak" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Shared organization" msgstr "" -#: ../settings/security/third-party/saml.rst:65 -msgid "" -"**To add Zammad as a client,** save the XML configuration to disk (``https://" -"your.zammad.domain/auth/saml/metadata``) and use **Clients > Clients list > " -"Import client** in the Keycloak admin panel." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.shared}``" msgstr "" -#: ../settings/security/third-party/saml.rst:70 -msgid "" -"To help Zammad **match its own user accounts to Keycloak users**, create a " -"user attribute (or “property”) mapper. In **Clients list**, click on your " -"newly created Client ID, choose the tab **Client scopes** and click on the " -"link which refers to your Zammad instance. Choose **Add mapper > By " -"configuration > User Property** and create a mapper with the following " -"entries:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > VIP" msgstr "" -#: ../settings/security/third-party/saml.rst:78 -msgid "**Name**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.vip}``" msgstr "" -#: ../settings/security/third-party/saml.rst:80 -msgid "**Mapper Type**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Phone" msgstr "" -#: ../settings/security/third-party/saml.rst:81 -msgid "``User Property``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.phone}``" msgstr "" -#: ../settings/security/third-party/saml.rst:82 -msgid "**Property**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated at" msgstr "" -#: ../settings/security/third-party/saml.rst:83 -msgid "``emailAddress``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_at}``" msgstr "" -#: ../settings/security/third-party/saml.rst:84 -msgid "**SAML Attribute Name**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Address" msgstr "" -#: ../settings/security/third-party/saml.rst:86 -msgid "**SAML Attribute NameFormat**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.address}``" msgstr "" -#: ../settings/security/third-party/saml.rst:87 -msgid "``basic``" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Avatar" msgstr "" -#: ../settings/security/third-party/saml.rst:89 -msgid "" -"In the example above, we're telling Zammad that whenever it receives a SAML " -"login request, it should take the ``email`` property from Keycloak, look for " -"a Zammad user with the same ``email`` attribute, and create a new session " -"for that user." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/saml.rst:95 -msgid "" -"If your Keycloak users' email addresses are stored on another property (*e." -"g.,* ``username``), adjust accordingly." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Department" msgstr "" -#: ../settings/security/third-party/saml.rst:98 -msgid "" -"Back in **Settings**, enter the Client ID (``https://your.zammad.domain/auth/" -"saml/metadata``) in the field **Master SAML Processing URL**." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.department}``" msgstr "" -#: ../settings/security/third-party/saml.rst:101 -msgid "You also need to enable **Sign assertions**." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Email" msgstr "" -#: ../settings/security/third-party/saml.rst:105 -msgid "Step 2: Configure Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.email}``" msgstr "" -#: ../settings/security/third-party/saml.rst:107 -msgid "" -"Enable SAML and enter your IdP's details in the Admin Panel under **Settings " -"> Security > Third Party Applications > Authentication via SAML**:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Fax" msgstr "" -#: ../settings/security/third-party/saml.rst:None -msgid "Example configuration of SAML part 1" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.fax}``" msgstr "" -#: ../settings/security/third-party/saml.rst:119 -msgid "Display name" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Firstname" msgstr "" -#: ../settings/security/third-party/saml.rst:116 -msgid "" -"Allows you to define a custom button name for SAML. This helps your users to " -"understand better what the button on the login page does." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.firstname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:119 -msgid "Defaults to ``SAML``." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Lastname" msgstr "" -#: ../settings/security/third-party/saml.rst:123 -msgid "IDP SSO target URL" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.lastname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:122 -msgid "" -"This is the target URL Zammad shall redirect to when the user presses the " -"SAML button. For Keycloak, this needs to look like https://your.domain/" -"realms/your-realm/protocol/saml" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Login" msgstr "" -#: ../settings/security/third-party/saml.rst:127 -msgid "IDP single logout target URL" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.login}``" msgstr "" -#: ../settings/security/third-party/saml.rst:126 -msgid "" -"This is the URL to which the single logout request and response should be " -"sent." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Mobile" msgstr "" -#: ../settings/security/third-party/saml.rst:131 -msgid "IDP certificate" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.mobile}``" msgstr "" -#: ../settings/security/third-party/saml.rst:130 -msgid "" -"The public certificate of your IDP for Zammad to verify during the callback " -"phase." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Note" msgstr "" -#: ../settings/security/third-party/saml.rst:145 -msgid "IDP certificate fingerprint" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.note}``" msgstr "" -#: ../settings/security/third-party/saml.rst:134 -msgid "" -"The fingerprint of your IDPs public certificate to verify during callback " -"phase." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Phone" msgstr "" -#: ../settings/security/third-party/saml.rst:137 -msgid "🔏 **For the IdP certificate / certificate fingerprint:**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.phone}``" msgstr "" -#: ../settings/security/third-party/saml.rst:139 -msgid "" -"Provide **only one or the other**—do not provide both! (Between the two, we " -"recommend the signing certificate itself: fingerprints use SHA-1, which `has " -"been broken for a while now `_.)" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > VIP" msgstr "" -#: ../settings/security/third-party/saml.rst:144 -msgid "" -"**Keycloak users:** Find your certificate in the Keycloak admin panel under " -"**Realm Settings > Keys > Algorithm: RS256 > Certificate**." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.vip}``" msgstr "" -#: ../settings/security/third-party/saml.rst:151 -msgid "Name identifier format" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``false`` or ``true``" msgstr "" -#: ../settings/security/third-party/saml.rst:148 -msgid "" -"This is the unique identifiers field type. Usually it should be ``urn:oasis:" -"names:tc:SAML:1.1:nameid-format:emailAddress``." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Web" msgstr "" -#: ../settings/security/third-party/saml.rst:151 -msgid "Zammad **expects an email address as unique identifier**!" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.web}``" msgstr "" -#: ../settings/security/third-party/saml.rst:155 -msgid "UID attribute name" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > VIP" msgstr "" -#: ../settings/security/third-party/saml.rst:154 -msgid "" -"Here you can define an attribute that uniquely identifies the user. If " -"unset, the name identifier returned by the IDP is used." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.vip}``" msgstr "" -#: ../settings/security/third-party/saml.rst:None -msgid "Example configuration of SAML part 2" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Web" msgstr "" -#: ../settings/security/third-party/saml.rst:163 -msgid "" -"Decide if the certificate for the connection to the IdP service has to be " -"verified or not (default: ``yes``)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.web}``" msgstr "" -#: ../settings/security/third-party/saml.rst:169 -msgid "Signing & Encrypting" +#: ../misc/variables/ticket.rst:6 +msgid "" +"Below you can find all available ticket-based variables within Zammad. These " +"can be called via triggers for example. If you're unsure if Zammad does " +"support variables at the point you're at, you can try to type ``::`` to " +"check." msgstr "" -#: ../settings/security/third-party/saml.rst:169 -msgid "" -"Define if you want to sign, encrypt, do both or nothing for the requests." +#: ../misc/variables/ticket.rst:12 +msgid "Ticket Variables" msgstr "" -#: ../settings/security/third-party/saml.rst:179 -msgid "Certificate (PEM)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Accounted Time" msgstr "" -#: ../settings/security/third-party/saml.rst:172 -msgid "" -"Paste the public certificate of your Zammad SAML client, if you want to " -"encrypt the requests." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.time_unit}``" msgstr "" -#: ../settings/security/third-party/saml.rst:175 -msgid "Make sure the certificate is:" +#: ../misc/variables/ticket.rst:1 +msgid "``1``, ``2.75`` or empty response" msgstr "" -#: ../settings/security/third-party/saml.rst:177 -msgid "already valid and not yet expired" +#: ../misc/variables/ticket.rst:1 +msgid "``3``, any number of articles existing in the ticket right now" msgstr "" -#: ../settings/security/third-party/saml.rst:178 -msgid "no CA certificate" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Closing time" msgstr "" -#: ../settings/security/third-party/saml.rst:179 -msgid "valid for signing and encrypting" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.close_at}``" msgstr "" -#: ../settings/security/third-party/saml.rst:185 -msgid "Private key (PEM)" +#: ../misc/variables/ticket.rst:1 +msgid "2019-10-07 17:25:00 UTC" msgstr "" -#: ../settings/security/third-party/saml.rst:182 -msgid "" -"Paste the private key of your Zammad SAML client here, if you want to sign " -"the requests." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created at" msgstr "" -#: ../settings/security/third-party/saml.rst:185 -msgid "Make sure the key is an RSA key with a length of at least 2048 bits." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_at}``" msgstr "" -#: ../settings/security/third-party/saml.rst:188 -msgid "Private key secret" +#: ../misc/variables/ticket.rst:1 +msgid "2019-10-07 16:25:00 UTC" msgstr "" -#: ../settings/security/third-party/saml.rst:188 -msgid "If your private key is secured with a secret, you can provide it here." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Address" msgstr "" -#: ../settings/security/third-party/saml.rst:192 -msgid "Your callback URL" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.address}``" msgstr "" -#: ../settings/security/third-party/saml.rst:191 -msgid "" -"This URL is needed for your IdP configuration so it knows where to redirect " -"to after successful authentication." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Avatar" msgstr "" -#: ../settings/security/third-party/saml.rst:194 -msgid "" -"After saving your input by clicking on the \"Submit\" button, Zammad " -"verifies the provided keys/certificates (e.g. if they are valid for signing/" -"encrypting and if they aren't expired)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/saml.rst:199 -msgid "" -"See :ref:`automatic account linking ` for details " -"on how to link existing Zammad accounts to IdP accounts." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Department" msgstr "" -#: ../settings/security/third-party/saml.rst:205 -msgid "Automatic account linking doesn't work" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.department}``" msgstr "" -#: ../settings/security/third-party/saml.rst:206 -msgid "" -"Have you double-checked your IdP's user attribute mapping configuration?" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Email" msgstr "" -#: ../settings/security/third-party/twitter.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via Twitter. To do " -"so, you need to follow these steps:" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.email}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:8 -msgid "Register Twitter App" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Fax" msgstr "" -#: ../settings/security/third-party/twitter.rst:10 -msgid "Go to https://dev.twitter.com/apps and login with your account." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.fax}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:15 -msgid "Click on \"Create App\"" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Firstname" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "new app page" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.firstname}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:20 -msgid "" -"Enter app settings. As \"Callback URL\" you need to enter ``https://" -"zammad_host/api/v1/external_credentials/twitter/callback``. You need to " -"replace ``zammad_host`` with the domain of your Zammad system." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Lastname" msgstr "" -#: ../settings/security/third-party/twitter.rst:24 -msgid "" -"After the app has been created, update the application icon and organization " -"attributes." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.lastname}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "set permissions to receive and send direct messages" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Login" msgstr "" -#: ../settings/security/third-party/twitter.rst:30 -msgid "" -"Next we need to set ``read, write and access direct messages`` permissions " -"for the app." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.login}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "click on Keys & Access Token, note them" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Mobile" msgstr "" -#: ../settings/security/third-party/twitter.rst:36 -msgid "" -"Go to \"Keys and Access Token\" tab and note the \"Consumer Key\" and " -"\"Consumer Secret\"." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.mobile}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:40 -msgid "Configure Zammad as Twitter App" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Note" msgstr "" -#: ../settings/security/third-party/twitter.rst:42 -msgid "" -"Go to \"Admin > Security > Twitter > Third Party Applications > Twitter\" " -"Section." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.note}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "Admin > Security > Third Party Applications" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Phone" msgstr "" -#: ../settings/security/third-party/twitter.rst:48 -msgid "" -"Fill in the \"Twitter Key\" and the \"Twitter Secret\" and click the " -"\"Submit\" button." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.phone}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:51 -msgid "" -"Now you can link accounts via \"Avatar > Profile > Link Accounts\" or login " -"via Zammad login page." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > VIP" msgstr "" -#: ../settings/security/two-factor.rst:11 -msgid "Two-factor Authentication Methods" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.vip}``" msgstr "" -#: ../settings/security/two-factor.rst:2 -msgid "Two-Factor Authentication" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Web" msgstr "" -#: ../settings/security/two-factor.rst:4 -msgid "" -"Two-factor authentication (2FA) enhances the security of Zammad accounts by " -"adding an extra layer of verification beyond a password. It requires users " -"to provide two different types of authentication factors, typically " -"something they know (like a password) and something they possess (like a " -"mobile device or a security token), to ensure that only authorized " -"individuals can access the account." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.web}``" msgstr "" -#: ../settings/security/two-factor.rst:19 -msgid "Enable Recovery Codes" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Address" msgstr "" -#: ../settings/security/two-factor.rst:21 -msgid "" -"Recovery codes are one-time use security codes that can be used by the user " -"if they lose access to their other two-factor authentication methods. They " -"cannot be used on their own, they can only be activated if at least one two-" -"factor authentication method is enabled." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.address}``" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Enable Recovery Codes Setting" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Avatar" msgstr "" -#: ../settings/security/two-factor.rst:30 -msgid "" -"Recovery codes can only be used as a backup method. If enabled, they will be " -"automatically generated for the user once they set up their initial two-" -"factor authentication method." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.avatar(60,60)}``" msgstr "" -#: ../settings/security/two-factor.rst:34 -msgid "" -"The user will be asked to print out or save the generated recovery codes in " -"a safe place. Once used, a recovery code cannot be reused." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Department" msgstr "" -#: ../settings/security/two-factor.rst:37 -msgid "" -"Users will also have an option to regenerate their recovery codes at any " -"time, which invalidates already existing recovery codes and provides them " -"with a list of fresh codes." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.department}``" msgstr "" -#: ../settings/security/two-factor.rst:41 -msgid "" -"After you enable this setting, when the user completes a setup of their " -"initial two-factor authentication method, they will be presented with a list " -"of recovery codes and instructed to save them for later use." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Email" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Recovery Codes Generation Modal Dialog" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.email}``" msgstr "" -#: ../settings/security/two-factor.rst:50 -msgid "Enforce the Set Up of the Two-Factor Authentication" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Fax" msgstr "" -#: ../settings/security/two-factor.rst:52 -msgid "" -"In case you wish to require your users to set up at least one two-factor " -"authentication method for their account, you can do this by selecting " -"specific user roles the requirement applies to in **Enforced for user " -"roles** setting. Of course you must have at least one two-factor " -"authentication method enabled for this setting to take effect." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.fax}``" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Enforced for User Roles Setting" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Firstname" msgstr "" -#: ../settings/security/two-factor.rst:62 -msgid "" -"After you change this setting, if the user has one of the selected roles on " -"their account, they will be forced to set up the two-factor authentication " -"upon next sign in or application reload." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.firstname}``" msgstr "" -#: ../settings/security/two-factor.rst:66 -msgid "" -"A modal dialog with instructions will be shown, and they will not be able to " -"do any work before they set up at least one two-factor method." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Lastname" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Modal Dialog for Enforcing Two-Factor Authentication Set Up" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.lastname}``" msgstr "" -#: ../settings/security/two-factor.rst:74 -msgid "Reset Two-Factor Authentication for a Specific User" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Login" msgstr "" -#: ../settings/security/two-factor.rst:76 -msgid "" -"In case an user isn't able to login anymore because of an inaccessible " -"second factor, you can reset the user's 2FA method." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.login}``" msgstr "" -#: ../settings/security/two-factor.rst:79 -msgid "" -"To do this, go to the user management and search for the relevant user. " -"After you found the account, click the button in the action column and " -"select \"Manage Two-Factor Authentication\":" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Mobile" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Context menu in action column in user management" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.mobile}``" msgstr "" -#: ../settings/security/two-factor.rst:87 -msgid "" -"After selecting this, you can see a dialog where you can either reset one " -"2FA method or reset all of the user's 2FA methods:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Note" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Dialog for resetting user's 2FA method" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.note}``" msgstr "" -#: ../settings/security/two-factor.rst:94 -msgid "" -"Choose the fitting one, click on the corresponding \"Remove ...\" button and " -"confirm your action. The user now has to setup a new 2FA method, depending " -"on your 2FA configuration." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Phone" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:2 -msgid "Authenticator App" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.phone}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:4 -msgid "" -"The authenticator app method is a type of two-factor authentication that " -"uses a mobile application to generate one-time codes for account " -"verification. After setting up the authenticator app on their device, the " -"user links it to their Zammad account." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > VIP" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:12 -msgid "" -"When logging in, the user is prompted to enter a time-sensitive code " -"generated by the app, in addition to their password. This code acts as the " -"second factor of authentication, providing an extra layer of security as it " -"changes periodically and is unique to the user's device." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.vip}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:None -msgid "Security Code in Google Authenticator App" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Web" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:22 -msgid "" -"The app generates codes based on a shared secret key stored securely on both " -"the user's device and the server, ensuring a synchronized and secure " -"authentication process. The method of generating the codes is sometimes also " -"called TOTP (time-based one-time password)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.web}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:28 -msgid "Enabling the Authenticator App Method" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Escalation at" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:30 -#: ../settings/security/two-factor/security-keys.rst:28 -msgid "To enable the method, just toggle the switch on in the settings." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.escalation_at}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:None -msgid "Authenticator App Switch in Settings" +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:36 -msgid "" -"Now the users will be able to set up this two-factor authentication method " -"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " -"Once they do, on next sign-in with password, they will be asked to provide " -"an additional security code generated by their mobile device." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > First response" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:2 -msgid "Security Keys" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.first_response_at}``" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:4 -msgid "" -"The security keys method is a type of a two-factor authentication that uses " -"Web Authentication API in the browser for verifying user's identity. The " -"user can register multiple hardware or software security keys with their " -"Zammad account and then they can use it during the sign-in process." +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable yet" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:12 -msgid "" -"When logging in, the user is prompted to provide the same security key they " -"registered with their account, in addition to their password. This key acts " -"as the second factor of authentication, providing an extra layer of security." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Assign Follow-Ups" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:None -msgid "Security Key dialog in Safari on macOS" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_assignment}``" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:21 -msgid "" -"The type of the key can range from hardware USB sticks to passkeys stored in " -"a device of user's choice. Which type can be used depends on the browser " -"flavor and the platform of the user." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Assignment Timeout" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:26 -msgid "Enabling the Security Keys Method" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.assignment_timeout}``" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:None -msgid "Security Keys Switch in Settings" +#: ../misc/variables/ticket.rst:1 +msgid "``20`` or empty if not configured" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:34 -msgid "" -"Now the users will be able to set up this two-factor authentication method " -"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " -"Once they do, on next sign-in with password, they will be asked to provide " -"the same security key they registered during the setup." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Follow-up possible" msgstr "" -#: ../settings/system/system-selfhosted.include.rst:3 -msgid "" -"Below settings are only available to self hosted users. In hosted " -"environments we're handling these settings for you to ensure service " -"stability." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_possible}``" msgstr "" -#: ../settings/system/base.rst:11 -msgid "Fully Qualified Domain Name" +#: ../misc/variables/ticket.rst:1 +msgid "``no`` or ``yes``" msgstr "" -#: ../settings/system/base.rst:7 -msgid "The URL of your Zammad installation." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Name" msgstr "" -#: ../settings/system/base.rst:9 ../settings/system/base.rst:17 -msgid "This setting is used within :doc:`/system/variables` and notifications." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.name}``" msgstr "" -#: ../settings/system/system-base.include.rst:1 -msgid "It is automatically set by the *Getting Started wizard*." +#: ../misc/variables/ticket.rst:1 +msgid "``Sales``" msgstr "" -#: ../settings/system/system-base.include.rst:5 -msgid "Changing this setting also changes callback URLs for your channels etc." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Note" msgstr "" -#: ../settings/system/system-base.include.rst:6 -msgid "This setting can have negative affects on being able to login." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.note}``" msgstr "" -#: ../settings/system/base.rst:19 -msgid "HTTP type" +#: ../misc/variables/ticket.rst:1 +msgid "``Note about this group``" msgstr "" -#: ../settings/system/base.rst:14 -msgid "" -"The HTTP type tells your installation how your clients connect. This is " -"relevant for authentication and cookie security." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > ID" msgstr "" -#: ../settings/system/base.rst:31 -msgid "SystemID" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.id}``" msgstr "" -#: ../settings/system/base.rst:22 -msgid "" -"This ID is being used within your ticket number. In case you're " -"communicating with another ticket system with similar ticket number schemes " -"this ID greatly reduces the risk of false follow ups." +#: ../misc/variables/ticket.rst:1 +msgid "``17``, ``5281``, ..." msgstr "" -#: ../settings/system/base.rst:26 -msgid "" -"The SystemID is randomly selected upon installation of Zammad (``1-99``)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact (agent)" msgstr "" -#: ../settings/system/base.rst:30 -msgid "" -"**Do not** change this setting in a productive system! Your Zammad " -"installation may no longer recognize old ticket number based follow ups upon " -"change!" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_agent_at}``" msgstr "" -#: ../settings/system/frontend.rst:2 -msgid "Frontend" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact (customer)" msgstr "" -#: ../settings/system/frontend.rst:22 -msgid "Core Workflow Ajax Mode" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_customer_at}``" msgstr "" -#: ../settings/system/frontend.rst:6 +#: ../misc/variables/ticket.rst:1 msgid "" -"This setting allows administrators to enforce :doc:`/system/core-workflows` " -"to use Ajax-Calls instead of web sockets. You'll usually only need this if " -"you experience serious issues as noted below." +"``2019-10-07 16:25:00 UTC`` or empty if not applicable yet (Please note " +"`Ticket last contact behavior Settings `_ for this)" msgstr "" -#: ../settings/system/frontend.rst:10 -msgid "**🤓 Possible (technical) reasons**" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact" msgstr "" -#: ../settings/system/frontend.rst:12 -msgid "" -"In some cases, your network structure (e.g. firewalls, proxies) may " -"disconnect long web socket connections. This leads to select fields staying " -"empty (e.g. owner selection *after* selecting your group) or fields not " -"shown / hidden (e.g. when switching to or from pending states, the \"pending " -"till\" field not showing / hiding)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_at}``" msgstr "" -#: ../settings/system/frontend.rst:18 -msgid "" -"Please keep in mind that the Ajax fallback may cause serious pressure on " -"your application server. If you have the choice stick to web sockets." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Number" msgstr "" -#: ../settings/system/frontend.rst:22 -msgid "Default: ``no`` (inactive)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.number}``" msgstr "" -#: ../settings/system/frontend.rst:53 -msgid "Show calendar weeks in the picker of date/datetime fields" +#: ../misc/variables/ticket.rst:1 +msgid "``31001``, ``201910731001``, ..." msgstr "" -#: ../settings/system/frontend.rst:25 -msgid "" -"With this setting you can instruct Zammad to provide week number display " -"globally for all users. Calendar with week number display are usually used " -"in business sectors and may not be relevant for everyone." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain based assignment" msgstr "" -#: ../settings/system/frontend.rst:29 -msgid "" -"This setting affects *all areas* - you'll also see week numbers in the admin " -"panel for e.g. triggers and macros." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain_assignment}``" msgstr "" -#: ../settings/system/frontend.rst:32 -msgid "Default: ``no`` (not shown)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain" msgstr "" -#: ../settings/system/frontend.rst:53 -msgid "Here's the difference:" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain}``" msgstr "" -#: ../settings/system/frontend.rst:0 -msgid "Screenshot showing Zammad's date picker (in the default way)" +#: ../misc/variables/ticket.rst:1 +msgid "``domain.tld`` or empty if not set" msgstr "" -#: ../settings/system/frontend.rst:41 -msgid "Set to ``no``" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Name" msgstr "" -#: ../settings/system/frontend.rst:0 -msgid "" -"Screenshot showing Zammad's date picker with\n" -"week numbers enabled" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.name}``" msgstr "" -#: ../settings/system/frontend.rst:50 -msgid "Set to ``yes``" +#: ../misc/variables/ticket.rst:1 +msgid "``Zammad GmbH`` or empty if not set" msgstr "" -#: ../settings/system/index.rst:4 -msgid "" -"For your overview we split each tab within system settings into its own page:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Note" msgstr "" -#: ../settings/system/index.rst:16 -msgid "Console Based Settings" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.note}``" msgstr "" -#: ../settings/system/index.rst:18 -msgid "" -"There's some console based settings we didn't put into the UI. However, you " -"may find them helpful - you can find them in our :docs:`hidden settings ` section." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Shared organization" msgstr "" -#: ../settings/system/network.rst:2 -msgid "Network" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.shared}``" msgstr "" -#: ../settings/system/network.rst:8 -msgid "" -"The proxy settings can only be saved after successfully testing the proxy " -"connection." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > VIP" msgstr "" -#: ../settings/system/network.rst:15 -msgid "Proxy Address." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.vip}``" msgstr "" -#: ../settings/system/network.rst:12 -msgid "" -"Allows you to provide a proxy server if needed. This is relevant for network " -"communication by Zammad." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Address" msgstr "" -#: ../settings/system/network.rst:15 -msgid "It **does not** affect the update process or Elasticsearch." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.address}``" msgstr "" -#: ../settings/system/network.rst:18 -msgid "Username for proxy connection." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Avatar" msgstr "" -#: ../settings/system/network.rst:18 -msgid "" -"If your proxy server requires authentication, provide the username here." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.avatar(60,60)}``" msgstr "" -#: ../settings/system/network.rst:21 -msgid "Password for proxy connection." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Department" msgstr "" -#: ../settings/system/network.rst:21 -msgid "" -"If your proxy server requires authentication, provide the password here." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.department}``" msgstr "" -#: ../settings/system/network.rst:26 -msgid "No proxy for the following hosts." +#: ../misc/variables/ticket.rst:1 +msgid "``Support`` or empty if not set" msgstr "" -#: ../settings/system/network.rst:24 -msgid "" -"Exception list for hosts you can't or don't want to reach via proxy server." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Email" msgstr "" -#: ../settings/system/network.rst:27 -msgid "Default: ``localhost,127.0.0.0,::1``" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.email}``" msgstr "" -#: ../settings/system/services.rst:2 -msgid "Services" +#: ../misc/variables/ticket.rst:1 +msgid "``agent@company.tld`` or empty if not set" msgstr "" -#: ../settings/system/services.rst:10 -msgid "Image Service" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Fax" msgstr "" -#: ../settings/system/services.rst:5 -msgid "Defines the backend for user and organization image lookups." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.fax}``" msgstr "" -#: ../settings/system/services.rst:7 -msgid "Default: ``Zammad Image Service`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Firstname" msgstr "" -#: ../settings/system/services.rst:9 -msgid "" -"Make sure your on premise installation has ``HTTPS`` access to ``images." -"zammad.com``." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.firstname}``" msgstr "" -#: ../settings/system/services.rst:18 -msgid "Geo Calendar Service" +#: ../misc/variables/ticket.rst:1 +msgid "``Max`` or empty if not set" msgstr "" -#: ../settings/system/services.rst:13 -msgid "" -"Defines the backend for geo calendar lookups. Used for initial calendar " -"setup." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Lastname" msgstr "" -#: ../settings/system/services.rst:16 -msgid "Default: ``Zammad GeoCalendar Service`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.lastname}``" msgstr "" -#: ../settings/system/services.include.rst:2 -msgid "" -"Make sure your on premise installation has ``HTTPS`` access to ``geo.zammad." -"com``." +#: ../misc/variables/ticket.rst:1 +msgid "``Mustermann`` or empty if not set" msgstr "" -#: ../settings/system/services.rst:26 -msgid "Geo IP Service" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Login" msgstr "" -#: ../settings/system/services.rst:21 -msgid "" -"Defines the backend for geo IP lookups. Shows also location of an IP address " -"if an IP address is shown." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.login}``" msgstr "" -#: ../settings/system/services.rst:24 -msgid "Default: ``Zammad GeoIP Service`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "``agent``" msgstr "" -#: ../settings/system/services.rst:32 -msgid "Geo Location Service" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Mobile" msgstr "" -#: ../settings/system/services.rst:29 -msgid "" -"Defines the backend for geo location lookups to store geo locations for " -"addresses." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.mobile}``" msgstr "" -#: ../settings/system/services.rst:32 -msgid "" -"Default: ``OpenStreetMap (ODbL 1.0, http://osm.org/copyright)`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Note" msgstr "" -#: ../settings/system/services.rst:36 -msgid "" -"You can find a detailed privacy information on what we store for how long on " -"our :docs:`Privacy Appendix ` inside of our System " -"Documentation." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.note}``" msgstr "" -#: ../settings/system/storage.rst:2 -msgid "Storage" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Phone" msgstr "" -#: ../settings/system/storage.rst:6 -msgid "" -"Here you can define where Zammad stores attachments for tickets and the " -"knowledge base. By default, we're writing to the ``Database`` - you can " -"switch to ``Filesystem`` or ``Simple Storage (S3)`` at any time. In this " -"case please have a look on the following instructions." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.phone}``" msgstr "" -#: ../settings/system/storage.rst:11 -msgid "" -"If you have a busy Zammad instance, we strongly encourage you to use " -"filesystem storage instead of \"Database\". This will greatly improve system " -"performance (de-crease database load and size)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > VIP" msgstr "" -#: ../settings/system/storage.rst:19 -msgid "Database" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.vip}``" msgstr "" -#: ../settings/system/storage.rst:17 -msgid "" -"This is the default storage method. The attachments are stored directly in " -"the database. If your Zammad instance grows, we recommend one of the other " -"methods to maintain performance." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Web" msgstr "" -#: ../settings/system/storage.rst:38 -msgid "Filesystem" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.web}``" msgstr "" -#: ../settings/system/storage.rst:22 -msgid "" -"This storage method is recommended for all Zammad instances, especially for " -"those with a higher load. If you choose filesystem, your files are written " -"to ``/opt/zammad/storage/``." +#: ../misc/variables/ticket.rst:1 +msgid "``https://zammad.com`` or empty if not set" msgstr "" -#: ../settings/system/storage.rst:26 -msgid "" -"Moving attachments from \"Database\" to \"Filesystem\" can be run during " -"production use. However, you should consider your framework conditions (e.g. " -"bandwidth, system load in production) to define the right moment." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Pending till" msgstr "" -#: ../settings/system/storage.rst:32 -msgid "**You noticed slow updates of Zammad?**" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.pending_time}``" msgstr "" -#: ../settings/system/storage.rst:34 -msgid "" -"While Zammad is beeing updated, it enforces a recursive \"change " -"owner\" (chown) for this directory. For instances with many files this can " -"be time consuming. To mitigate that you can move your files and create a " -"symlink in ``/opt/zammad/storage/`` to the new directory. Of course you have " -"to make sure on your own that the permissions are always correct." +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not set" msgstr "" -#: ../settings/system/storage.rst:95 -msgid "Simple Storage (S3)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Priority > Name" msgstr "" -#: ../settings/system/storage.rst:41 -msgid "" -"To use the Simple Storage (S3), you have to provide some settings, which " -"can't be accessed in the UI (see instructions below)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.priority.name}``" msgstr "" -#: ../settings/system/storage.rst:44 -msgid "" -"⚠️ Please note that the current implementation is in its early stages and can " -"be modified in the future." +#: ../misc/variables/ticket.rst:1 +msgid "``2 normal``" msgstr "" -#: ../settings/system/storage.rst:47 -msgid "" -"The prerequisite is to have access to a S3-compatible storage and to have " -"all necessary parameters available (which depends on your storage provider; " -"if in doubt, please ask there for help)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > State > Name" msgstr "" -#: ../settings/system/storage.rst:51 -msgid "Steps to configure S3:" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.state.name}``" msgstr "" -#: ../settings/system/storage.rst:53 -msgid "" -"Copy ``config/zammad/storage.yml.dist`` to ``config/zammad/storage.yml``" +#: ../misc/variables/ticket.rst:1 +msgid "``new``, ``open``, ..." msgstr "" -#: ../settings/system/storage.rst:54 -msgid "Edit the copied file in one of the following ways:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Tags" msgstr "" -#: ../settings/system/storage.rst:56 -msgid "" -"Either provide your S3 configuration with one attribute per line like in the " -"upper area of the file" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.tags}``" msgstr "" -#: ../settings/system/storage.rst:58 +#: ../misc/variables/ticket.rst:1 msgid "" -"Or provide your S3 configuration as an URL (which you can find at the end of " -"the file). Note: you can also provide this URL as environment variable (:" -"docs:`see system documentation `) without using this yml-file." +"Currently not available, see `Issue 2769 `_" msgstr "" -#: ../settings/system/storage.rst:62 -msgid "" -"We recommend the deletion of the not used configuration style to avoid " -"inconsistencies." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Title" msgstr "" -#: ../settings/system/storage.rst:65 -msgid "Restart Zammad so the config file / environment variable is loaded" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.title}``" msgstr "" -#: ../settings/system/storage.rst:66 +#: ../misc/variables/ticket.rst:1 msgid "" -"Set the \"Storage Method\" in Zammad to ``Simple Storage (S3)`` in Settings " -"> System > Storage and click on \"Submit\". After that, Zammad checks your " -"configuration and the connection to the service and will raise an error " -"message if something is wrong." +"``My amazing Subject`` (normally subject, can be edited within Interface and " +"thus differ)" msgstr "" -#: ../settings/system/storage.rst:72 -msgid "A very simple storage configuration could look like this:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated at" msgstr "" -#: ../settings/system/storage.rst:85 -msgid "" -"Before setting the storage method to ``Simple Storage (S3)`` (step 4), " -"please make sure to have a working setup." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_at}``" msgstr "" -#: ../settings/system/storage.rst:88 -msgid "" -"You can verify this by running ``rails r 'Rails.logger = Logger.new(STDOUT); " -"pp Store::Provider::S3.ping?'`` in your Zammad directory. If everything is " -"fine, you should see ``true``, else you should see ``false`` and a simple " -"error message." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Address" msgstr "" -#: ../settings/system/storage.rst:93 -msgid "" -"If you installed Zammad through a package manager (rather than from source), " -"replace ``rails r`` with ``zammad run rails r`` above. To learn more, see :" -"docs:`Administration via Console `." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.address}``" msgstr "" -#: ../settings/ticket.rst:4 -msgid "" -"Here you can adjust general ticket settings. Additional ones for the ticket " -"composer interface can be found in the :doc:`/misc/composer`." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Avatar" msgstr "" -#: ../settings/ticket.rst:11 -msgid "Ticket Hook (default: ``Ticket#``)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.avatar(60,60)}``" msgstr "" -#: ../settings/ticket.rst:11 -msgid "The identifier for a ticket; *e.g.,* Ticket#, Call#, MyTicket#." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Department" msgstr "" -#: ../settings/ticket.rst:38 -msgid "Ticket Hook Position (default: ``right``)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.department}``" msgstr "" -#: ../settings/ticket.rst:14 -msgid "" -"With this setting you can decide (if) where to insert the ticket number." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Email" msgstr "" -#: ../settings/ticket.rst:20 -msgid "*Right*" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.email}``" msgstr "" -#: ../settings/ticket.rst:17 -msgid "" -"This setting will add the ticket reference on the right site of the subject." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Fax" msgstr "" -#: ../settings/ticket.rst:20 -msgid "Example: ``Some Subject [Ticket#12345]``" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.fax}``" msgstr "" -#: ../settings/ticket.rst:26 -msgid "*Left*" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Firstname" msgstr "" -#: ../settings/ticket.rst:23 -msgid "" -"This setting will add the ticket reference on the left site of the subject." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.firstname}``" msgstr "" -#: ../settings/ticket.rst:26 -msgid "Example: ``[Ticket#12345] Some Subject``" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Lastname" msgstr "" -#: ../settings/ticket.rst:29 -msgid "*None*" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.lastname}``" msgstr "" -#: ../settings/ticket.rst:29 -msgid "This will completely remove ticket references from the subject." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Login" msgstr "" -#: ../settings/ticket.rst:33 -msgid "" -"Please ensure to take a look at :doc:`/channels/email/settings` within the " -"email channel to ensure you have at least one reference that helps Zammad to " -"assign follow-ups correctly." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.login}``" msgstr "" -#: ../settings/ticket.rst:37 -msgid "" -"Disabling this and not setting up any further follow up search will lead to " -"unexpected results!" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Mobile" msgstr "" -#: ../settings/ticket.rst:65 -msgid "" -"Ticket Last Contact Behaviour (default: ``Use the start time of the last " -"customer thread (which may consist of multiple articles).``)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.mobile}``" msgstr "" -#: ../settings/ticket.rst:41 -msgid "" -"This setting changes the way Zammad updates the ``Last Contact`` value of a " -"ticket. This is fairly important for overviews and what you expect upon " -"ticket updates of a customer." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Note" msgstr "" -#: ../settings/ticket.rst:52 -msgid "" -"Use the start time of the last customer thread (which may consist of " -"multiple articles)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.note}``" msgstr "" -#: ../settings/ticket.rst:46 -msgid "" -"If this option is chosen, Zammad will update the last updated value just " -"once if a customer replies. After that, Zammad will wait for an agent to " -"react." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Phone" msgstr "" -#: ../settings/ticket.rst:50 -msgid "" -"This comes in handy if you want to work tickets in the order of their first " -"update. This will not change ticket orders if customers decide to \"bump\" " -"the ticket affected." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.phone}``" msgstr "" -#: ../settings/ticket.rst:57 -msgid "Use the time of the very last customer article." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > VIP" msgstr "" -#: ../settings/ticket.rst:55 -msgid "" -"When setting this option, Zammad will always update the last updated value. " -"This means that if ordering by ``Last Update``, ticket orders will change if " -"customers \"bump\" the ticket." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.vip}``" msgstr "" -#: ../settings/ticket.rst:64 -msgid "Last contact value used on :doc:`/manage/overviews`" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Web" msgstr "" -#: ../settings/ticket.rst:65 -msgid "Last contact value used on :doc:`/manage/trigger`" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.web}``" msgstr "" -#: ../settings/ticket.rst:88 -msgid "" -"Ticket Organization Reassignment (default: ``Update the most recent tickets." -"``)" +#: ../settings/branding.rst:10 +msgid "Product Name" msgstr "" -#: ../settings/ticket.rst:68 +#: ../settings/branding.rst:7 msgid "" -"This setting changes the way Zammad updates the organization field of the " -"tickets whenever the primary organization of a user is changed." -msgstr "" - -#: ../settings/ticket.rst:74 -msgid "Update the most recent tickets." +"Defines the name of the application, shown in the web interface, tabs and " +"title bar of the web browser." msgstr "" -#: ../settings/ticket.rst:72 -msgid "" -"If this option is chosen, Zammad will update the 100 most recent tickets " -"where the user is the ticket customer. The ticket organization field will be " -"automatically set to the new primary organization of the user." +#: ../settings/branding.rst:10 +msgid "Default value: ``Zammad Helpdesk``" msgstr "" -#: ../settings/ticket.rst:88 -msgid "Do not update any tickets." +#: ../settings/branding.rst:13 +msgid "Will be shown in the app and is included in email footers." msgstr "" -#: ../settings/ticket.rst:77 -msgid "" -"When choosing this option, Zammad will not update any tickets when the " -"user's primary organization is changed." +#: ../settings/branding.rst:19 +msgid "Logo" msgstr "" -#: ../settings/ticket.rst:80 -msgid "**Use with care!**" +#: ../settings/branding.rst:16 +msgid "Defines the logo of the application, shown in the login page of Zammad." msgstr "" -#: ../settings/ticket.rst:82 +#: ../settings/branding.rst:18 msgid "" -"Using this option may lead to inconsistencies in the system as the ticket " -"organization may become decoupled from the ticket customer." +"Ensure to hit the \"Submit\" button after uploading the logo. Otherwise your " +"change will not be saved." msgstr "" -#: ../settings/ticket.rst:85 +#: ../settings/branding.rst:22 msgid "" -"However, you may use this option if you wish to maintain :ref:`the shared " -"access ` to the ticket for all organization " -"members of the original organization of the customer." +"Allows to set the default language of the Zammad instance. The here defined " +"locale mostly acts as a fallback for:" msgstr "" -#: ../settings/ticket.rst:110 -msgid "Ticket Number Format (default: ``Increment (SystemID.Counter)``)" +#: ../settings/branding.rst:25 +msgid "user preferences (if Zammad can't detect the users locale)" msgstr "" -#: ../settings/ticket.rst:94 -msgid "" -"This setting defines the way Zammad's ticket number will look. Changing this " -"setting in production will cause follow up detection to fail." +#: ../settings/branding.rst:26 +msgid "CSV output (reporting, time accounting)" msgstr "" -#: ../settings/ticket.rst:102 -msgid "Increment (SystemID.Counter)" +#: ../settings/branding.rst:30 +msgid "Define the timezone of your Zammad installation." msgstr "" -#: ../settings/ticket.rst:98 +#: ../settings/branding.rst:32 msgid "" -"The increment value contains the SystemID (automatically generated during " -"installation) and a increment which counts up with every new Ticket. The " -"increment will automatically get another digit if needed." +"This does not have any effect on timings for your agents or how Zammad " +"stores date and time values." msgstr "" -#: ../settings/ticket.rst:102 -msgid "Examples: ``1010138``, ``1010139``" +#: ../settings/branding.rst:35 +msgid "Changing this value has direct consequences on the following areas:" msgstr "" -#: ../settings/ticket.rst:110 -msgid "Date (Year.Month.Day.SystemID.Counter)" +#: ../settings/branding.rst:37 +msgid ":doc:`/manage/scheduler` tasks" msgstr "" -#: ../settings/ticket.rst:105 -msgid "" -"This version of the ticket number is fairly long. However, because it " -"contains the date of ticket creation, it also allows you to see when the " -"ticket has been created. You may feel familiar with this number format if " -"you've worked with OTRS already." +#: ../settings/branding.rst:38 +msgid "search indexing (and thus reporting)" msgstr "" -#: ../settings/ticket.rst:110 -msgid "Examples: ``201206231010138``, ``201206231010139``" +#: ../settings/branding.rst:40 +msgid "calendar subscriptions" msgstr "" -#: ../settings/ticket.rst:137 -msgid "OPTIONS" +#: ../settings/branding.rst:41 +msgid "browser printing" msgstr "" -#: ../settings/ticket.rst:113 +#: ../settings/branding.rst:43 msgid "" -"The below options allow you to further customize your ticket number. The " -"availability of options differ depending of the chosen ticket number format " -"above." +"Please note that some of above are fallbacks in case Zammad could not detect " +"the agents timezone correctly." msgstr "" -#: ../settings/ticket.rst:122 -msgid "Checksum (default: ``no``)" +#: ../settings/branding.rst:77 +msgid "Pretty Date" msgstr "" -#: ../settings/ticket.rst:118 +#: ../settings/branding.rst:47 msgid "" -"If set to yes, we'll built a checksum to further \"unique\" the ticket " -"number of your system. If you're dealing with many other ticket systems this " -"might help to prevent false positive follow up detection on tickets." +"This setting allows you to define how Zammad should display time stamps " +"within the interface to all users." msgstr "" -#: ../settings/ticket.rst:122 -msgid "This will also add another digit to the ticket number." +#: ../settings/branding.rst:50 +msgid "" +"This does not have any effect on how Zammad returns e.g. time values via " +"variables." msgstr "" -#: ../settings/ticket.rst:137 -msgid "Min. size of Number (default: ``5``)" +#: ../settings/branding.rst:77 +msgid "Choose in between the following options:" msgstr "" -#: ../settings/ticket.rst:125 -msgid "" -"This setting defines the minimum length of your ticket number. If your " -"counter is not yet high enough, Zammad will fill the number with zeros to " -"ensure the wanted length." +#: ../settings/branding.rst:64 +msgid "relative" msgstr "" -#: ../settings/ticket.rst:129 +#: ../settings/branding.rst:55 msgid "" -"Please note that the minimum length is ``3`` (SystemID + at least one digit " -"if below 10). Also, if the length is no longer long enough, the number will " -"automatically get one digit longer. Ticket-Numbers **do not overflow**, thus " -"it's save to keep it at 5 or set it lower if wanted." +"This timestamp shows a relative time span until it switches to a date. Over " +"time, it will change as follows:" msgstr "" -#: ../settings/ticket.rst:135 -msgid "" -"This option is only available if ticket number format is set to " -"``Increment``!" +#: ../settings/branding.rst:58 +msgid "just now" msgstr "" -#: ../settings/ticket.rst:142 -msgid "Auto-Assignment" +#: ../settings/branding.rst:59 +msgid "5 minutes ago" msgstr "" -#: ../settings/ticket.rst:144 -msgid "" -"In a larger Zammad environment, it happens that several agents open the same " -"ticket at the same time. Although collision detection is then effective, the " -"efficiency of processing can be increased by means of the automatic " -"assignment of tickets when a ticket is opened." +#: ../settings/branding.rst:60 +msgid "3 days 1 hour ago" msgstr "" -#: ../settings/ticket.rst:149 -msgid "" -"The automatic assignment of tickets can be activated and configured in the " -"admin area under Settings > Ticket > Auto Assignment." +#: ../settings/branding.rst:61 +msgid "``03/04/2022``" msgstr "" -#: ../settings/ticket.rst:152 -msgid "" -"The auto assignment only works if the ticket has no owner yet. By default, " -"the agent can always reset the ticket owner to ``-`` if needed." +#: ../settings/branding.rst:63 +msgid "Hovering the timestamp helps, you'll always get a clean timestamp then." msgstr "" -#: ../settings/ticket.rst:155 -msgid "" -"If you want to use this function for only specific tickets, you can " -"configure the conditions accordingly to meet your requirement. By default " -"the condition affects all tickets with the state ``open``." +#: ../settings/branding.rst:71 +msgid "absolute" msgstr "" -#: ../settings/ticket.rst:161 +#: ../settings/branding.rst:67 msgid "" -"If you need to exclude users (e.g. a group leader), you can search and " -"select the desired agents in the ``Exception Users`` list. The search " -"function in this area is only effective, if you have too many agents to " -"display at once to help you with the configuration." +"This timestamp always includes the week day. For one week after creation, " +"the timestamp will not contain the date itself: Thursday 18:35." msgstr "" -#: ../settings/ticket.rst:167 -msgid "Notifications" +#: ../settings/branding.rst:71 +msgid "After a week it will switch to: ``Friday 4. Mar 16:00``." msgstr "" -#: ../settings/ticket.rst:191 -msgid "Default Notifications" +#: ../settings/branding.rst:76 +msgid "timestamp" msgstr "" -#: ../settings/ticket.rst:170 +#: ../settings/branding.rst:74 msgid "" -"This setting allows you to configure the default ticket notifications that " -"will be applied to all new agent users (incl. users who were just assigned " -"agent role). Simply change the notification matrix to desired state and " -"press **Save**." +"This will cause Zammad to show a complete timestamp according to your locale " +"defaults. For English this could be e.g. ``2022/12/03 2:40 pm`` or for " +"German e.g. ``12.03.2022 14:40``." msgstr "" -#: ../settings/ticket.rst:175 -msgid "" -"In case an agent already exists, their ticket notification preferences will " -"be preserved. Optionally, you can also **Apply current defaults to all " -"agents**." +#: ../settings/branding.rst:78 +msgid "Default setting: ``relative``." msgstr "" -#: ../settings/ticket.rst:181 -msgid "" -"**Potential time-consuming action:** Applying default ticket notifications " -"to all agent users may take some time to complete, be patient! The exact " -"time will depend on the size of your system and the number of agents." +#: ../settings/security.rst:2 +msgid "Security" msgstr "" -#: ../settings/ticket.rst:185 +#: ../settings/security.rst:4 msgid "" -"**Active agents only!** When current default ticket notifications are " -"applied, only active agent users are considered. In case an agent is re-" -"activated *after* this action, they will still have the old notification " -"configuration." +"For your overview we split each tab within security settings into its own " +"page:" msgstr "" -#: ../settings/ticket.rst:190 +#: ../settings/security/base.rst:2 ../settings/system/base.rst:2 +#: ../settings/ticket.rst:8 +msgid "Base" +msgstr "" + +#: ../settings/security/base.rst:5 +msgid "New User Accounts" +msgstr "" + +#: ../settings/security/base.rst:9 msgid "" -"In case you want to go back to the initial state of ticket notifications, " -"you can click on **Reset to default** button." +"Activates the `register as a new customer` function on the login page. If " +"set to ``no`` only administrators or agents can create new accounts manually." msgstr "" -#: ../settings/ticket.rst:194 ../settings/ticket.rst:196 -msgid "Duplicate Detection" +#: ../settings/security/base.rst:13 ../settings/security/base.rst:38 +#: ../settings/security/base.rst:66 +msgid "Default setting: ``yes``" msgstr "" -#: ../settings/ticket.rst:236 ../settings/ticket.rst:238 -msgid "Detect Duplicate Ticket Creation" +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"New User Accounts\" setting" msgstr "" -#: ../settings/ticket.rst:197 ../settings/ticket.rst:199 +#: ../settings/security/base.rst:22 msgid "" -"This setting turns on the duplicate ticket detection mechanism during ticket " -"creation. If similar tickets are found in the system, a suitable warning " -"will be shown to the user trying to create a ticket." +"Deactivation of above function **does not** deactivate automatic account " +"creation! This means: If a user writes e.g. an email to Zammad and has no " +"account yet, Zammad will automatically create the account. User accounts are " +"a direct dependency of tickets and thus technically mandatory." msgstr "" -#: ../settings/ticket.rst:204 ../settings/ticket.rst:206 -msgid "A Sample Duplicate Ticket Warning" +#: ../settings/security/base.rst:29 +msgid "Lost Password" msgstr "" -#: ../settings/ticket.rst:206 ../settings/ticket.rst:208 +#: ../settings/security/base.rst:33 msgid "" -"You can choose which ticket attributes will be matched by selecting them in " -"**Attributes to compare** field. Only if the ticket attribute value provided " -"by the user in the ticket create form is *equal* with the attribute in an " -"existing ticket, the warning will be shown." +"Activates the `lost password` function on the login page. If set to ``no`` " +"only administrators may change the user's password - users may update their " +"own password if they're still logged in and they have the required :doc:" +"`permission `." msgstr "" -#: ../settings/ticket.rst:211 ../settings/ticket.rst:213 -msgid "**Warning title** and **Warning message** are configurable as well." +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"Lost Password\" setting" msgstr "" -#: ../settings/ticket.rst:213 ../settings/ticket.rst:215 +#: ../settings/security/base.rst:49 msgid "" -"You can limit the detection only to certain user roles. By default, only " -"agents will see the warning." +"With third party authentications - but especially LDAP - you may want to " +"disable this function. Zammad **will not** change third party login " +"passwords and instead set or change the local password!" msgstr "" -#: ../settings/ticket.rst:216 ../settings/ticket.rst:218 -msgid "" -"If you don't want to show the matched tickets as part of the warning, you " -"can set **Show matching ticket(s) in the warning** setting to *no*." +#: ../settings/security/base.rst:56 +msgid "Password Login" msgstr "" -#: ../settings/ticket.rst:219 ../settings/ticket.rst:221 +#: ../settings/security/base.rst:60 msgid "" -"By default, **Permission level for looking up ticket** is set to *User*, " -"which means user permissions will be honored during sarch. The user will " -"see the warning only if tickets they have access to are matched. " -"Alternatively, you can set this setting to *System*, in which case the " -"search will happen within *all* tickets in the system, regardless of user " -"permissions." +"Activates the username & password login by default and if no third-party " +"login is activated. Disabling password login on the Zammad login page only " +"takes effect if you enable any :doc:`third-party`." msgstr "" -#: ../settings/ticket.rst:225 ../settings/ticket.rst:227 -msgid "**🦺 Safety first!**" +#: ../settings/security/base.rst:64 +msgid "See :doc:`third-party` for supported third-party logins." msgstr "" -#: ../settings/ticket.rst:227 ../settings/ticket.rst:229 -msgid "" -"Even if the permission level is set to *System*, the user will not be shown " -"the tickets they don't have access to in the warning, even if they match." +#: ../settings/security/base.rst:0 +msgid "Figure showing de-activated \"Password Login\" setting" msgstr "" -#: ../settings/ticket.rst:231 ../settings/ticket.rst:233 +#: ../settings/security/base.rst:77 msgid "" -"However, just the confirmation about the existence of the tickets in the " -"system may be considered an unwanted information disclosure. Use this option " -"carefully!" +"To help administrators to overcome \"login issues\", Zammad automatically " +"offers a password request for administrator users. This allows you to adjust " +"Third-Party applications even if the login does no longer work!" msgstr "" -#: ../settings/ticket.rst:235 ../settings/ticket.rst:237 -msgid "" -"Finally, you can configure between matching within **All tickets** or **Open " -"tickets** only by setting **Match tickets in following states**. Depending " -"on the current ticket state, a ticket may or not be matched." +#: ../settings/security/base.rst:84 +msgid "Session Timeout" msgstr "" -#: ../system/core-workflows.rst:2 -msgid "Core Workflows" +#: ../settings/security/base.rst:86 +msgid "" +"All settings below by default are set to ``4 weeks``. Session Timeout " +"defines the life time of a users session. As soon as it's reached, Zammad " +"will automatically log off the session in question." msgstr "" -#: ../system/core-workflows.rst:4 +#: ../settings/security/base.rst:91 msgid "" -"Core Workflows allow you to adjust object attributes in many ways. For " -"example:" +"Zammad takes the highest value set assigned for the user based on the " +"permissions." msgstr "" -#: ../system/core-workflows.rst:7 -msgid "show / hide fields" +#: ../settings/security/base.rst:94 +msgid "``admin``" msgstr "" -#: ../system/core-workflows.rst:8 -msgid "adjust mandatory setting" +#: ../settings/security/base.rst:96 +msgid "``ticket.customer``" msgstr "" -#: ../system/core-workflows.rst:9 -msgid "manipulate available options" +#: ../settings/security/base.rst:97 +msgid "``default`` (fallback if user doesn't have above permissions set)" msgstr "" -#: ../system/core-workflows.rst:11 +#: ../settings/security/base.rst:99 msgid "" -"With this, you can provide exactly the information your users really need!" +"All settings act independently from each other allowing you to disable the " +"timeouts for e.g. admins, but not agents." msgstr "" -#: ../system/core-workflows.rst:15 -msgid "" -"If the pre-defined :doc:`/system/objects` are not enough, please add them " -"beforehand." +#: ../settings/security/base.rst:115 +#: ../system/integrations/checkmk/api-reference.rst:13 +msgid "Example" msgstr "" -#: ../system/core-workflows.rst:17 -msgid "" -"If you experience slow or unreliable field updates, please see :ref:`Core " -"Workflow Ajax Modus `" +#: ../settings/security/base.rst:107 +msgid "Let's suppose you configured the following session timeouts" msgstr "" -#: ../system/core-workflows.rst:22 -msgid "" -"This is a very enhanced functionality and can cause unexpected UI behavior. " -"Please ensure to test your use cases after configuration to reduce surprises." +#: ../settings/security/base.rst:104 +msgid "default: 3 weeks" msgstr "" -#: ../system/core-workflows.rst:None -msgid "Dialogue for adding a new workflow" +#: ../settings/security/base.rst:105 +msgid "admin: 2 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:2 -msgid "Core Workflow Condition Operators" +#: ../settings/security/base.rst:106 +msgid "ticket.agent: 4 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:4 -msgid "" -"You might know that there is a separate section for explaining :doc:" -"`condition operators `. Head over there to " -"see a detailed explanation of many conditions and operators." +#: ../settings/security/base.rst:107 +msgid "ticket.customer: 1 week" msgstr "" -#: ../system/core-workflows/condition-operators.rst:8 -msgid "" -"Due to differences to other places in Zammad which are also using conditions " -"(e.g. triggers), you can find a dedicated description of operators for core " -"workflows below." +#: ../settings/security/base.rst:115 +msgid "This results in the following situations" msgstr "" -#: ../system/core-workflows/condition-operators.rst:12 -msgid "" -"Be aware that the availability of the operators depends on the selected " -"attribute and its field type. Some of the operators may only be available " -"for system attributes (e.g. for \"tags\", \"active\")." +#: ../settings/security/base.rst:110 +msgid "a user with ``admin`` permission will have a timeout of 2 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:20 -msgid "Operator" +#: ../settings/security/base.rst:111 +msgid "" +"a user with ``admin`` and ``ticket.agent`` permissions will have a timeout " +"of 2 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:22 -msgid "after (absolute)" +#: ../settings/security/base.rst:113 +msgid "" +"a user with ``ticket.customer`` permission will have a timeout of 1 week" msgstr "" -#: ../system/core-workflows/condition-operators.rst:23 -msgid "Matches if a date/time is after a specific point in time." +#: ../settings/security/base.rst:115 +msgid "" +"a user with neither ``admin``, ``ticket.agent`` nor ``ticket.customer`` " +"permissions will have a timeout of 3 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:24 -msgid "after (relative)" +#: ../settings/security/password.rst:4 +msgid "" +"This section allows you to define password requirements for the local user " +"accounts." msgstr "" -#: ../system/core-workflows/condition-operators.rst:25 -msgid "Matches if a time span after a specified event has passed." +#: ../settings/security/password.rst:9 +msgid "" +"Zammad does **not** allow you to change your LDAP password, instead, it will " +"set a password in its local database which might confuse your users. This " +"might be addressed in the future by `#1169 `_." msgstr "" -#: ../system/core-workflows/condition-operators.rst:26 -msgid "before (absolute)" +#: ../settings/security/password.rst:14 +msgid "**Exception for admins**" msgstr "" -#: ../system/core-workflows/condition-operators.rst:27 -msgid "Matches if a date/time is before a specific point in time." +#: ../settings/security/password.rst:16 +msgid "" +"Please note that below password policies *do not* affect administrators " +"setting passwords on user accounts. While this seems strange and not safe we " +"believe that an administrator knowing an user's password is insecure as well." msgstr "" -#: ../system/core-workflows/condition-operators.rst:28 -msgid "before (relative)" +#: ../settings/security/password.rst:21 +msgid "The suggested workflow is either:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:29 -msgid "Matches if a time span after a specified event has not passed." +#: ../settings/security/password.rst:23 +msgid "" +"to use third party logins to not require local passwords at all **- or -**" msgstr "" -#: ../system/core-workflows/condition-operators.rst:30 -msgid "contains" +#: ../settings/security/password.rst:25 +msgid "to require your *user to reset the password* upon first login." msgstr "" -#: ../system/core-workflows/condition-operators.rst:31 -msgid "Matches if a specified value is present." +#: ../settings/security/password.rst:27 +msgid "" +"This way administrators are not required to set a user's password at all!" msgstr "" -#: ../system/core-workflows/condition-operators.rst:33 -msgid "Matches if all of the specified values are present." +#: ../settings/security/password.rst:31 +msgid "Maximum Failed Logins" msgstr "" -#: ../system/core-workflows/condition-operators.rst:35 -msgid "Matches if none of the specified values are present." +#: ../settings/security/password.rst:33 +msgid "" +"You can choose a value between ``4`` and ``20``. This defines how often a " +"login to a user account may fail until Zammad will lock it. Your users can " +"always use the \"forgot password\" function to change their password and " +"unlock their account." msgstr "" -#: ../system/core-workflows/condition-operators.rst:36 -msgid "contains not" +#: ../settings/security/password.rst:38 +msgid "The default value is ``10``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:37 -msgid "Matches if a specified value is not present." +#: ../settings/security/password.rst:42 +msgid "Beside changing the user's password, you can also unlock accounts via" msgstr "" -#: ../system/core-workflows/condition-operators.rst:39 -msgid "Matches if one specified value is present." +#: ../settings/security/password.rst:44 +msgid ":ref:`user management list `" msgstr "" -#: ../system/core-workflows/condition-operators.rst:41 -msgid "Matches if one specified value is not present." +#: ../settings/security/password.rst:45 +msgid ":docs:`console `" msgstr "" -#: ../system/core-workflows/condition-operators.rst:42 -msgid "does not match regex" +#: ../settings/security/password.rst:46 +msgid ":docs:`API `" msgstr "" -#: ../system/core-workflows/condition-operators.rst:43 -msgid "Matches if content doesn't fit to regex rule." +#: ../settings/security/password.rst:50 +msgid "Failed logins via LDAP no longer lock accounts." msgstr "" -#: ../system/core-workflows/condition-operators.rst:44 -msgid "ends with" +#: ../settings/security/password.rst:53 +msgid "2 Lower Case And 2 Upper Case Characters" msgstr "" -#: ../system/core-workflows/condition-operators.rst:45 -msgid "Matches if content ends with specified value." +#: ../settings/security/password.rst:55 +msgid "" +"You can add complexity to passwords by enforcing at least 2 upper and lower " +"case characters." msgstr "" -#: ../system/core-workflows/condition-operators.rst:46 -msgid "ends with one of" +#: ../settings/security/password.rst:58 ../settings/security/password.rst:83 +msgid "The default value is ``no``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:47 -msgid "Matches if content ends with one of the specified values." +#: ../settings/security/password.rst:62 +msgid "Minimum Length" msgstr "" -#: ../system/core-workflows/condition-operators.rst:48 -msgid "from (relative)" +#: ../settings/security/password.rst:64 +msgid "" +"This defines the minimum password length required for users to provide (from " +"``4`` to ``20``)." msgstr "" -#: ../system/core-workflows/condition-operators.rst:49 -msgid "Matches if date/time is after a period of time after an event." +#: ../settings/security/password.rst:67 +msgid "The default value is ``6``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:51 -msgid "Matches if content is equal to a specified value." +#: ../settings/security/password.rst:71 +msgid "Digit Required" msgstr "" -#: ../system/core-workflows/condition-operators.rst:52 -msgid "is any of" +#: ../settings/security/password.rst:73 +msgid "This enforces your users to use at least one digit within the password." msgstr "" -#: ../system/core-workflows/condition-operators.rst:53 -msgid "Matches if content is equal to any of specified values." +#: ../settings/security/password.rst:75 +msgid "The default value is ``yes``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:54 -msgid "is modified" +#: ../settings/security/password.rst:78 +msgid "Special Character Required" msgstr "" -#: ../system/core-workflows/condition-operators.rst:55 -msgid "Matches if content is modified." +#: ../settings/security/password.rst:80 +msgid "" +"This setting allows you to improve your password quality even more by " +"enforcing the password to contain at least one special character." msgstr "" -#: ../system/core-workflows/condition-operators.rst:57 -#: ../system/core-workflows/condition-operators.rst:61 -msgid "True from the moment of changing content until form submit." +#: ../settings/security/ssl-certificates.rst:2 +msgid "SSL Certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:58 -msgid "is modified to" +#: ../settings/security/ssl-certificates.rst:7 +msgid "" +"Zammad offers the possibility to upload custom certificates and custom " +"Certificate Authority (CA) certificates. This can be useful if you want to " +"connect Zammad the secure way to other systems which are using custom " +"certificates." msgstr "" -#: ../system/core-workflows/condition-operators.rst:59 -msgid "Matches if content is modified to a specific value." +#: ../settings/security/ssl-certificates.rst:12 +msgid "" +"An example usecase might be: You have an internal LDAP server that is not " +"accessible from the internet, and you want a SSL-encrypted connection, using " +"a custom certificate." msgstr "" -#: ../system/core-workflows/condition-operators.rst:62 -msgid "is none of" +#: ../settings/security/ssl-certificates.rst:19 +msgid "" +"You should have an existing custom certificate file and/or a custom CA " +"certificate file, which you want to add to Zammad. As filetype ``.crt`` is " +"supported and the certificate format has to be PEM (Base64 ASCII)." msgstr "" -#: ../system/core-workflows/condition-operators.rst:63 -msgid "Matches if content is none of any specified values." +#: ../settings/security/ssl-certificates.rst:25 +msgid "" +"When you import a custom CA certificate, all certificates generated with " +"this are trusted. This can be useful if you have more than one system/" +"certificate you want to connect to and the certificates are issued from the " +"same custom CA." msgstr "" -#: ../system/core-workflows/condition-operators.rst:65 -msgid "Matches if content is not equal to a specified value." +#: ../settings/security/ssl-certificates.rst:31 +msgid "Add a Certificate" msgstr "" -#: ../system/core-workflows/condition-operators.rst:67 -msgid "Matches if content is present." +#: ../settings/security/ssl-certificates.rst:33 +msgid "" +"To add a custom certificate or a custom CA certificate, head over to the " +"Admin panel > Settings > Security > SSL Certificates. Here you can find a " +"\"Add SSL Certificate\" button. In the dialog you can either select a " +"certificate file or paste the content of the certificate:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:68 -msgid "just changed" +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate adding dialog" msgstr "" -#: ../system/core-workflows/condition-operators.rst:69 -msgid "Matches if content has changed." +#: ../settings/security/ssl-certificates.rst:43 +msgid "" +"After selecting a file or pasting the content of the certificate, click on " +"the \"Add\" button to finally upload it to Zammad. Then, the certificates " +"are immediately effective, no restart or similar required." msgstr "" -#: ../system/core-workflows/condition-operators.rst:71 -#: ../system/core-workflows/condition-operators.rst:75 +#: ../settings/security/ssl-certificates.rst:49 msgid "" -"Only true for the moment of changing content until next form field action/" -"click." +"Please note that only single certificate files are supported. That means if " +"you want to import a certificate / CA certificate, it must contain **only " +"one** certificate." msgstr "" -#: ../system/core-workflows/condition-operators.rst:72 -msgid "just changed to" +#: ../settings/security/ssl-certificates.rst:54 +msgid "Certificate Overview" msgstr "" -#: ../system/core-workflows/condition-operators.rst:73 -msgid "Matches if content has changed to a specified value." +#: ../settings/security/ssl-certificates.rst:56 +msgid "" +"After you added a certificate, you can see a table with information for each " +"added certificate:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:76 -msgid "matches regex" +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing table of added certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:77 -msgid "Matches if value fits to regex rule." -msgstr "" - -#: ../system/core-workflows/condition-operators.rst:79 -msgid "Matches if no content is present." -msgstr "" - -#: ../system/core-workflows/condition-operators.rst:80 -msgid "starts with" +#: ../settings/security/ssl-certificates.rst:64 +msgid "" +"Here you can download the certificate or delete it, if you don't need it " +"anymore." msgstr "" -#: ../system/core-workflows/condition-operators.rst:81 -msgid "Matches if content starts with specified value." +#: ../settings/security/ssl-certificates.rst:68 +msgid "Deleting Certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:82 -msgid "starts with one of" +#: ../settings/security/ssl-certificates.rst:70 +msgid "" +"If you want to delete a specific certificate, you can do it by clicking on " +"the menu in the actions column and selecting delete:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:83 -msgid "Matches if content starts with one of the specified values." +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate deletion button" msgstr "" -#: ../system/core-workflows/condition-operators.rst:84 -msgid "till (relative)" +#: ../settings/security/ssl-certificates.rst:79 +msgid "Downloading Certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:85 -msgid "Matches if date/time is before a period of time before an event." +#: ../settings/security/ssl-certificates.rst:81 +msgid "" +"If you want to download your certificates, you can do this as well via " +"corresponding action buttons." msgstr "" -#: ../system/core-workflows/condition-operators.rst:86 -msgid "today" +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate download button" msgstr "" -#: ../system/core-workflows/condition-operators.rst:87 -msgid "Matches if date/time is today." +#: ../settings/security/third-party.rst:13 +msgid "Login Providers" msgstr "" -#: ../system/core-workflows/condition-operators.rst:88 -msgid "within last (relative)" +#: ../settings/security/third-party.rst:2 +msgid "Third-Party Applications" msgstr "" -#: ../system/core-workflows/condition-operators.rst:89 +#: ../settings/security/third-party.rst:4 msgid "" -"Matches if date/time content is within specified period of time before now." +"Third party authentication is a great way to help your users to login to " +"Zammad more easily. If the account is yet unknown, Zammad will create a new " +"user automatically, without the user needed to interact (e.g. type in his " +"name). Another big advantage of this feature is that your user doesn't need " +"to remember another password." msgstr "" -#: ../system/core-workflows/condition-operators.rst:91 -msgid "within next (relative)" +#: ../settings/security/third-party.rst:10 +msgid "" +"You can deactivate logging in via :ref:`security_password_login` if any of " +"the mentioned authentication providers are enabled in your instance." msgstr "" -#: ../system/core-workflows/condition-operators.rst:92 +#: ../settings/security/third-party.rst:27 msgid "" -"Matches if date/time content is within specified period of time after now." +"We're currently missing documentation for the following login providers:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:2 -msgid "How do they work?" +#: ../settings/security/third-party.rst:29 +msgid "LinkedIn" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:4 -msgid "" -"Core Workflows are executed according to their priority. If two workflows " -"have the same priority, they are executed in alphabetical order based on " -"their **name**." +#: ../settings/security/third-party.rst:30 +msgid "Weibo" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:8 -msgid "" -"Because of the way Core Workflows work, all changes to attributes are " -"checked with the application server - please see :doc:`limitations` for " -"possible issues." +#: ../settings/security/third-party.rst:35 +msgid "Automatic Account Link on Initial Logon" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:12 +#: ../settings/security/third-party.rst:37 msgid "" -"Below we're talking about settings that are important and not self-" -"explanatory." +"In general there's two possible options for Zammad on how to deal with " +"already known users as they try to authenticate against a third-party " +"application. By default, Zammad will not automatically link \"unknown\" " +"authentication providers to existing accounts." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:17 +#: ../settings/security/third-party.rst:42 msgid "" -"Choose the object context you want to run the workflow in. This will decide " -"on your available attributes and actions." -msgstr "" - -#: ../system/core-workflows/how-do-they-work.rst:20 -msgid "Ticket objects also have access to the ticket customer." +"This means that the user has to manually link authentication providers to " +"their accounts (for more about this :user-docs:`consult the user " +"documentation `)." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:25 +#: ../settings/security/third-party.rst:46 msgid "" -"Choose in which situation the workflow is applied. Contexts can be combined " -"to avoid duplicate workflows." +"Sometimes this doesn't come in handy as this also means you'll receive error " +"messages about \"email address being in use already\" for (yet) unknown " +"third-party authentication methods." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:30 -msgid "Creation mask" +#: ../settings/security/third-party.rst:50 +msgid "" +"If you want to allow your users to always be able to log in, no matter what, " +"you may want to enable ``Automatic account link on initial logon``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:29 +#: ../settings/security/third-party.rst:None msgid "" -"If selected, your conditions and actions will affect all applicable creation " -"masks." +"Screenshot highlighting the \"Automatic account link on initial logon\"\n" +"setting" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:34 -msgid "Edit mask" +#: ../settings/security/third-party.rst:60 +msgid "Automatic Account Linking Notification" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:33 +#: ../settings/security/third-party.rst:64 msgid "" -"If selected, your conditions and actions will affect all applicable edit " -"masks." +"To improve security and your users awareness, you can enable Zammad to " +"notify your users when a new third-party application has been linked to " +"their account." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:39 +#: ../settings/security/third-party.rst:68 msgid "" -"Zammad differentiates between selected and saved conditions. These can be " -"combined wherever needed." +"This notification is sent out once per third-party application. Zammad does " +"also mention the method used, e.g.: ``Microsoft``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:42 -msgid "**⚠️ Restrict workflows to specific roles if needed!**" +#: ../settings/security/third-party.rst:71 +msgid "By default this setting is not active (set to ``no``)." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:44 +#: ../settings/security/third-party.rst:0 msgid "" -"By default and unless configured in conditions, workflow rules are executed " -"for **all roles**. This also affects your customers!" +"Screenshot showing sample notification mail after initial\n" +"third-party linking" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:50 -msgid "Selected Conditions" +#: ../settings/security/third-party.rst:85 +msgid "" +"This notification is only sent if the account in question already exists. If " +"the login via the third-party also creates the missing account, the " +"notification will be skipped." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:48 -msgid "" -"These conditions are based on form values and match if an appropriate " -"selection is made (e.g. choosing another group in the ticket without " -"saving). This applies for drafts (active selection) and currently saved " -"values." +#: ../settings/security/third-party.rst:89 +msgid "This means it only affects:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:64 -msgid "Saved Conditions" +#: ../settings/security/third-party.rst:91 +msgid "manual account linking within the third-party page of the users profile" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:53 +#: ../settings/security/third-party.rst:92 msgid "" -"These conditions only match if the selected values are stored in the " -"database. It ignores the current value or selection of the field, as long as " -"the changes are not saved (e.g. performing field operations for an existing " -"ticket, which is viewed/opened by an agent)." +"logging into an existing local account by utilizing the *automatic account " +"link on initial logon* functionality" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:60 +#: ../settings/security/third-party.rst:None msgid "" -"Keep in mind that the value has to be available in the situation where you " -"need it. Otherwise the condition won't match." +"Screenshot showing the \"automatic account linking notification\"\n" +"setting" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:63 -msgid "" -"Example: you can't perform any actions with *saved condition* on a ticket in " -"creation, because there are no saved values at that time." +#: ../settings/security/third-party.rst:100 +msgid "No User Creation on Logon" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:66 +#: ../settings/security/third-party.rst:102 msgid "" -"You can find a description of the condition operators for core workflows :" -"doc:`here `." +"By default, Zammad will create a new user account if the user logs in via a " +"third-party application and the account doesn't exist yet." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:72 +#: ../settings/security/third-party.rst:105 msgid "" -"Which actions should we run on the relevant fields? The possible actions " -"depend on the object type. However, usually you can at least change the " -"visibility and whether the field is mandatory." +"If you want to prevent Zammad from creating new accounts on logon, you can " +"disable this feature by setting ``No user creation on logon`` to ``yes``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:76 -msgid "Be aware that actions are not available for **related** context." +#: ../settings/security/third-party.rst:None +msgid "Screenshot showing the \"no user creation on logon\" setting" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:78 +#: ../settings/security/third-party/facebook.rst:4 msgid "" -"**Example:** Let's assume you are working in the ticket context. While you " -"can have customer *conditions*, you *can't adjust* objects with actions in " -"that scope. That's because this wouldn't have any impact on the ticket " -"dialog. Of course all ticket attributes (state, owner, ...) are available." +"It is possible to create a quick login for your helpdesk via Facebook To do " +"so, you need to follow these steps:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:84 +#: ../settings/security/third-party/facebook.rst:9 +msgid "Register Facebook App" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:11 msgid "" -"Please also have a look at our :doc:`limitations` to be safe from surprises." +"Visit [https://developers.facebook.com/apps/] and click on \"Add a new App\"" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:88 -msgid "Available Operators" +#: ../settings/security/third-party/facebook.rst:None +msgid "initial page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:90 -msgid "The availability of operators depends on the object type and scope." +#: ../settings/security/third-party/facebook.rst:17 +msgid "After that enter the app settings" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:94 -msgid "" -"Please note that actions may or may not restrict API based access to " -"attributes. We're displaying the following icons for your overview to " -"understand these limits better:" +#: ../settings/security/third-party/facebook.rst:None +msgid "Create App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:0 -msgid "|api| This icon indicates the action affects the API." +#: ../settings/security/third-party/facebook.rst:22 +msgid "Navigate to \"Settings\" and fill in this infromation" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:163 -msgid "api" +#: ../settings/security/third-party/facebook.rst:None +msgid "App Settings" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:0 -msgid "|ui| This icon indicates the action only affects the web interface." +#: ../settings/security/third-party/facebook.rst:27 +msgid "Navigate to app review and Check \"Make [appname] public?\"" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:167 -msgid "ui" +#: ../settings/security/third-party/facebook.rst:None +msgid "App Review" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:102 -msgid "show |ui|" +#: ../settings/security/third-party/facebook.rst:35 +msgid "Configure Zammad as Facebook App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:102 -msgid "Display the chosen field. Allows setting of values." -msgstr "" - -#: ../system/core-workflows/how-do-they-work.rst:109 -msgid "hide |ui|" +#: ../settings/security/third-party/facebook.rst:37 +msgid "" +"Navigate to \"Admin -> Security -> Third Party Applications\" and enter the " +"App ID and the App Secret. You can find this Key in the Dashbard of your " +"Facebok app." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:105 -msgid "" -"Hide the chosen field. However, it technically still allows setting the " -"field." +#: ../settings/security/third-party/facebook.rst:None +msgid "Zammad Configuration" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:108 +#: ../settings/security/third-party/facebook.rst:44 +#: ../settings/security/third-party/github.rst:43 +#: ../settings/security/third-party/gitlab.rst:46 msgid "" -"Please note that the field is **not** gone and still contains an existing " -"value (if set)! Consider *remove* instead, if you want this field to be gone." +"Now you can link accounts via \"Avatar -> Profile -> Link Accounts\" or " +"login via Zammad login page." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:112 -msgid "remove |ui|" +#: ../settings/security/third-party/github.rst:2 +#: ../system/integrations/github.rst:2 +msgid "GitHub" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:112 -msgid "Entirely removes the field. The field value will not be evaluated." +#: ../settings/security/third-party/github.rst:4 +msgid "" +"It is possible to create a quick login for your helpdesk via GitHub. To " +"activate the quick login you need to enable OAuth for GitHub." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:115 -msgid "set mandatory |ui| |api|" +#: ../settings/security/third-party/github.rst:8 +msgid "Register GitHub App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:115 -msgid "Sets the field to mandatory." +#: ../settings/security/third-party/github.rst:10 +msgid "" +"Visit https://www.github.com/settings/applications/new and enter the app " +"settings. As callback URL enter \"https://zammad_host/auth/github/callback\" " +"where zammad_host has to be replaced with your Zammad FQDN" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:118 -msgid "set optional |ui| |api|" +#: ../settings/security/third-party/github.rst:None +msgid "Register OAuth app on www.github.com" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:118 -msgid "Sets the field to optional." +#: ../settings/security/third-party/github.rst:19 +msgid "Configure Zammad as GitHub App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:124 -msgid "add option |ui| |api|" +#: ../settings/security/third-party/github.rst:21 +msgid "" +"Enter the \"APP ID\" and the \"APP SECRET\" from the GitHub OAUTH " +"Applications Dashboard" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:121 -msgid "Allows adding options to tree selects or selects." +#: ../settings/security/third-party/github.rst:None +msgid "GitHub config in Zammad admin interface" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:123 +#: ../settings/security/third-party/github.rst:28 msgid "" -"You have to use the \"remove option\" before performing this action. It " -"allows you to use *existing* configured values." +"After you configured the GitHub credentials and activated the login method, " +"you should see a new icon on the login page." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:128 -msgid "remove option |ui| |api|" +#: ../settings/security/third-party/github.rst:None +msgid "GitHub logo on login page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:127 +#: ../settings/security/third-party/github.rst:34 msgid "" -"Allows removing options from tree selects or selects. It allows you to use " -"*existing* configured values." +"If you click on the icon you will be redirected to GitHub and see something " +"similar to this:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:134 -msgid "set fixed to |ui| |api|" +#: ../settings/security/third-party/github.rst:None +msgid "GitHub oauth page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:131 -msgid "Reduces the available options by your selection." +#: ../settings/security/third-party/github.rst:40 +#: ../settings/security/third-party/gitlab.rst:42 +msgid "" +"When you grant the access you will be redirected to your Zammad instance and " +"logged in as a customer." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:133 -msgid "" -"This reduces your workflows in terms of *add option* and *remove option*." +#: ../settings/security/third-party/gitlab.rst:2 +msgid "Gitlab" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:137 -msgid "fill in |ui|" +#: ../settings/security/third-party/gitlab.rst:4 +msgid "" +"It is possible to create a quick login for your helpdesk via Gitlab. To " +"activate the quick login you need to enable OAuth for Gitlab." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:137 -msgid "Allows filling in of string and integer fields with your values." +#: ../settings/security/third-party/gitlab.rst:8 +msgid "Register Gitlab App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:141 -msgid "fill in empty |ui|" +#: ../settings/security/third-party/gitlab.rst:10 +msgid "To register an app in Gitlab open your profile and select applications." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:140 +#: ../settings/security/third-party/gitlab.rst:12 msgid "" -"Allows filling in of string and integer fields with your values **if the " -"field is empty**." +"As callback URL enter \"https://zammad-fqdn/auth/gitlab/callback\" where " +"zammad-fqdn has to be replaced with your Zammad FQDN" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:144 -msgid "select |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Register OAuth app on gitlab instance" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:144 -msgid "Select a specific value within a select, tree select or boolean field." +#: ../settings/security/third-party/gitlab.rst:18 +msgid "Just select *read_user* under scopes as in the screenshot and save it." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:153 -msgid "auto select |ui|" +#: ../settings/security/third-party/gitlab.rst:21 +msgid "Configure Zammad as Gitlab App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:147 -msgid "Helps users with tree select and select fields:" +#: ../settings/security/third-party/gitlab.rst:23 +msgid "" +"Enter the \"APP ID\" and the \"APP SECRET\" from the Gitlab OAUTH " +"Applications Dashboard and your Gitlab-URL in the \"SITE\" field." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:149 -msgid "" -"If the field has only one option available for selection and no value yet, " -"the value will be automatically set." +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab config in Zammad admin interface" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:152 +#: ../settings/security/third-party/gitlab.rst:30 msgid "" -"This option only works if you have one value and doesn't work if there is " -"more than one option available." +"After you configured the Gitlab credentials and activated the login method, " +"you should see a new icon on the login page." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:157 -msgid "set readonly |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab logo on login page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:156 +#: ../settings/security/third-party/gitlab.rst:36 msgid "" -"Allows you to display an attribute as read only (which means no changes are " -"possible)." +"If you click on the icon you will be redirected to Gitlab and see something " +"similar to this:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:161 -msgid "unset readonly |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab oauth page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:160 +#: ../settings/security/third-party/google.rst:4 msgid "" -"In case a workflow set the field in question to read only, you can undo this " -"with option above." +"With some easy and fast steps, you can enable Zammad to authenticate your " +"users via Google." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:172 -msgid "Stop after match" +#: ../settings/security/third-party/google.rst:8 +msgid "Register a Google App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:174 +#: ../settings/security/third-party/google.rst:10 msgid "" -"Here you can decide if other workflows are executed after the current one." +"First of all, we need to create a new project - you can skip this step if " +"you already have one." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:176 +#: ../settings/security/third-party/google.rst:15 msgid "" -"If set to ``no`` (default), further workflows will be executed if they match " -"the condition. In this case, it is possible that your actions from the " -"current workflow can be overwritten by another workflow." +"Use this link to create a new project: https://console.cloud.google.com/" +"projectcreate" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:180 +#: ../settings/security/third-party/google.rst:18 msgid "" -"If set to ``yes``, no further worflows will be executed after the current " -"one." +"Now expand the menu, expand \"APIs & Services\" and select \"Credentials\". " +"Go to the tab \"OAuth consent screen\" first and ensure to fill in the " +"requested information - without doing so you can't create credentials!" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:184 -msgid "Priority" +#: ../settings/security/third-party/google.rst:None +msgid "Creating a consent screen" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:186 +#: ../settings/security/third-party/google.rst:25 msgid "" -"You can define the sequence, in which the workflows are executed. The " -"default value is ``500``." +"After filling in and saving the consent screen information, you can go to " +"the \"Credentials\" tab and create new \"OAuth client ID\"-Credentials." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:189 +#: ../settings/security/third-party/google.rst:28 msgid "" -"The workflows are executed in ascending order by their priority. That means " -"lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." +"Fill in the necessary information as follows and replace ``zammad_host`` " +"with your FQDN:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:2 -msgid "Learn by Example" +#: ../settings/security/third-party/google.rst:31 +msgid "**Application type** ``[x] Web application``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:4 -msgid "" -"This page provides some basic examples for Core Workflows. Of course you can " -"build much more complex workflows if needed." +#: ../settings/security/third-party/google.rst:34 +msgid "**Authorized JavaScript origins** ``https://zammad_host/``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:7 +#: ../settings/security/third-party/google.rst:37 msgid "" -"To learn about Core Workflows in detail, first go to :doc:`how-do-they-work`." +"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" +"callback``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:10 -msgid "Group Based Examples" +#: ../settings/security/third-party/google.rst:None +msgid "Adding a new OAuth client ID" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:12 +#: ../settings/security/third-party/google.rst:43 msgid "" -"All following workflows have the same base configurations. The workflow may " -"not use them all." +"After creating the credentials, go to your Zammad installation and navigate " +"to \"Admin > Security > Third Party Applications\" > Google. Enter your " +"Client ID and Client secret here." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:15 -msgid "Groups:" +#: ../settings/security/third-party/google.rst:None +msgid "Zammad" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:20 -msgid "Attributes:" +#: ../settings/security/third-party/google.rst:50 +msgid "After submitting, the login via Google can be used." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:22 -msgid "Category (Single tree selection field, not mandatory, agents only)" +#: ../settings/security/third-party/microsoft.rst:2 +msgid "Microsoft" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:23 +#: ../settings/security/third-party/microsoft.rst:4 msgid "" -"Approved (Boolean field, not mandatory, not shown, ``false`` as default)" +"Zammad's Microsoft connection allows your users with Microsoft accounts to " +"login. This works for Azure users as well and can be an alternative to :doc:" +"`/system/integrations/ldap/index`." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:24 -msgid "Operating System (Text field, not mandatory, not shown)" +#: ../settings/security/third-party/microsoft.rst:10 +msgid "" +"This documentation part does not cover our :doc:`📧 Microsoft 365 email " +"channel `." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:25 -msgid "Software used (Single selection field, not mandatory, not shown)" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screenshot showing Microsoft login button on Zammad login screen." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:68 -msgid "Group specific values and fields" +#: ../settings/security/third-party/microsoft.rst:30 +#: ../settings/security/third-party/microsoft.rst:53 +msgid "Supported account types:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:28 +#: ../settings/security/third-party/microsoft.rst:22 msgid "" -"This workflow set depends on the category field. It reduces the available " -"set of values based on the group selected." +"Please note that Zammad only supports these account types (App dependent):" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:33 -msgid "Workflow 2nd Level group" +#: ../settings/security/third-party/microsoft.rst:35 +msgid "Avatars of signing in users:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:35 +#: ../settings/security/third-party/microsoft.rst:33 msgid "" -"This reduces the category options to ``2nd Level/*``, ``Internal/*`` and " -"``Others``. It also sets further required fields to mandatory and visible." -msgstr "" - -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for 2nd level" +"Zammad currently ignores user avatars. If the user is registered with e.g. " +"Gravatar, Zammad will fetch the avatar from there if enabled. See :doc:" +"`Zammad Image Service ` for more." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:43 -msgid "Workflow Support group" +#: ../settings/security/third-party/microsoft.rst:38 +msgid "Step 1 - Register a Microsoft App for Zammad" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:45 +#: ../settings/security/third-party/microsoft.rst:40 msgid "" -"This reduces the category options to ``Support/*``, ``Internal/*`` and " -"``Others``. It also sets further required fields to visible." -msgstr "" - -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for support" +"Login to the `Microsoft Azure Portal `_ and " +"navigate to App registrations to create a new app. Provide the requested " +"information as follows and register your app." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:53 -msgid "Workflow Sales group" +#: ../settings/security/third-party/microsoft.rst:46 +msgid "Name:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:55 +#: ../settings/security/third-party/microsoft.rst:45 msgid "" -"This reduces the category options to ``Sales/*``, ``Internal/*`` and " -"``Others``." +"Any meaningful name fitting, this name will be displayed to users trying to " +"authenticate with this app." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for sales" +#: ../settings/security/third-party/microsoft.rst:49 +msgid "Choose one of the above mentioned account types (see Limitations)." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:68 -#: ../system/integrations/slack.rst:88 -msgid "The Result" +#: ../settings/security/third-party/microsoft.rst:51 +msgid "" +"The correct account type depends on your use case. If you want to use the " +"authentication internal only, choose the first option. If you're unsure, use " +"the \"Help me choose...\" link." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:63 -msgid "" -"This is what the agent would experience with the above workflows in place." +#: ../settings/security/third-party/microsoft.rst:58 +msgid "Redirect URI (optional):" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 +#: ../settings/security/third-party/microsoft.rst:56 msgid "" -"Workflow shows objects and limits options based on selections on the group" +"Select web and provide your callback URL. The callback URL looks like this: " +"``https://zammad.domain.tld/auth/microsoft_office365/callback``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:90 -msgid "Approval process" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to register a Microsoft app" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:71 -msgid "" -"In this case ``approved`` is visible to agents by default. For this " -"workflow, an additional role ``Approval person`` is required (no further " -"permissions)." +#: ../settings/security/third-party/microsoft.rst:71 +msgid "Within **API permissions** add the following permissions:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that restricts an approval attribute to specific roles" +#: ../settings/security/third-party/microsoft.rst:69 +msgid "``User.Read``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:81 -msgid "" -"This workflow may work best in combination with a :doc:`trigger ` but technically, this is not required." +#: ../settings/security/third-party/microsoft.rst:71 +msgid "Contacts" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:84 -msgid "" -"Select fields may be a better approach because they allow more values than " -"just a simple ``true`` or ``false``." +#: ../settings/security/third-party/microsoft.rst:71 +msgid "``Contacts.Read``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 +#: ../settings/security/third-party/microsoft.rst:73 msgid "" -"Workflow fixes possible values of \"Approved ?\" to a specific selection " -"depending on the users role" +"You can find these permissions within *Microsoft Graph → Delegated " +"permissions*." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:103 -msgid "State dependent mandatory fields" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to add required API permissions" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:93 +#: ../settings/security/third-party/microsoft.rst:80 msgid "" -"This workflow sets ``Category`` to mandatory if the agent wants to set the " -"states ``closed`` or ``pending close`` to enforce categorization." +"Within **Certificates & secrets** create a new client secret. Note down the " +"returned secret **value** for later. **Do not** use the secret ID!" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that sets fields to mandatory on specific states" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to create a new app secret" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 +#: ../settings/security/third-party/microsoft.rst:88 msgid "" -"Workflow sets category field to mandatory upon choosing closed or pending " -"close as state" +"From **Overview** copy your apps *Application (client) ID*. If you're using " +"a single tenant app, please also copy *Directory (tenant) ID*. You now have " +"all required information for Zammad." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:106 -msgid "Manual Ticket Handover Process" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to retreive application client and tenant IDs" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:108 -msgid "This example covers the handover of a ticket from one agent to another:" +#: ../settings/security/third-party/microsoft.rst:98 +msgid "Step 2 - Add App Credentials to Zammad" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:110 +#: ../settings/security/third-party/microsoft.rst:100 msgid "" -"When the ticket owner is modified, a new text field (\"Handover\") shows up " -"for a comment" +"Navigate to Security > Third-party Applications (Tab) within Zammad's admin " +"settings. Scroll down to the section *Authentication via Microsoft* and fill " +"in the required information." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:112 -msgid "" -"This may only be visible when the owner is changed, therefore it has to be " -"hidden in general" +#: ../settings/security/third-party/microsoft.rst:105 +msgid "App ID:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:114 -msgid "The input in this handover text field is mandatory" +#: ../settings/security/third-party/microsoft.rst:105 +msgid "This is your *Application (client) ID*." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:115 -msgid "" -"After submitting changes, the value of the handover field must be added as " -"an note to the ticket (via trigger)" +#: ../settings/security/third-party/microsoft.rst:108 +msgid "App secret:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:121 -msgid "Hiding handover field" +#: ../settings/security/third-party/microsoft.rst:108 +msgid "This is your *client secret* (value)." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Hiding the handover field in core workflows" +#: ../settings/security/third-party/microsoft.rst:113 +msgid "App Tenant ID:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:126 -msgid "Showing handover field and setting it to mandatory" +#: ../settings/security/third-party/microsoft.rst:111 +msgid "" +"**optional** only required for apps that use account type *Accounts in this " +"organizational directory only (Default Directory only - Single tenant).*" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Showing the handover field and set it as mandatory" +#: ../settings/security/third-party/microsoft.rst:115 +msgid "" +"Apply your settings by pressing submit and activate *Authentication via " +"Microsoft*." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:131 -msgid "Trigger writing handover input to a new article" +#: ../settings/security/third-party/microsoft.rst:None +msgid "" +"Screencast showing how to add app credentials and activating the\n" +"authentication method" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Write handover content to a new article" +#: ../settings/security/third-party/saml.rst:2 +msgid "SAML" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:133 +#: ../settings/security/third-party/saml.rst:4 msgid "" -"As a result, the ticket includes an article of the type note which includes " -"the predefined text and the handover comment." +"Connect your SAML (Security Assertion Markup Language) identity provider as " +"a single sign-on (SSO) method." msgstr "" -#: ../system/core-workflows/limitations.rst:6 -msgid "Core Workflows do not replace Triggers" +#: ../settings/security/third-party/saml.rst:7 +msgid "" +"SAML is an open standard for SSO authentication (among other things). Sign-" +"ins are shared across multiple **service providers** and managed by a " +"central **identity provider** (IdP)." msgstr "" -#: ../system/core-workflows/limitations.rst:5 +#: ../settings/security/third-party/saml.rst:11 msgid "" -"Workflows manipulate the behavior of fields. However, they do not set values " -"in fields because of actions." +"In this case, the service provider is Zammad, and the IdP is a software " +"service that you either host or subscribe to (*e.g.,* `Keycloak `_, `Redhat SSO Server `_, `ADFS `_, or `Okta `_)." msgstr "" -#: ../system/core-workflows/limitations.rst:16 -msgid "API calls are only partly affected" +#: ../settings/security/third-party/saml.rst:18 +msgid "" +"This guide assumes you are already using SAML within your organization (i." +"e., that your IdP is fully set up)." msgstr "" -#: ../system/core-workflows/limitations.rst:9 +#: ../settings/security/third-party/saml.rst:21 msgid "" -"Some options affect UI only and thus do not restrict responses and calls." +"Please note: Our instructions are based on connecting Zammad with Keycloak." msgstr "" -#: ../system/core-workflows/limitations.rst:11 -msgid "This affects the following actions:" +#: ../settings/security/third-party/saml.rst:25 +msgid "Step 1: Configure Your IdP" msgstr "" -#: ../system/core-workflows/limitations.rst:13 -msgid "select" +#: ../settings/security/third-party/saml.rst:28 +msgid "Add Zammad as a Client/App" msgstr "" -#: ../system/core-workflows/limitations.rst:14 -msgid "auto select" +#: ../settings/security/third-party/saml.rst:30 +msgid "" +"Import Zammad into your IdP using the XML configuration found at ``https://" +"your.zammad.domain/auth/saml/metadata``." msgstr "" -#: ../system/core-workflows/limitations.rst:15 -msgid "show" +#: ../settings/security/third-party/saml.rst:33 +msgid "" +"If your IdP doesn't support XML import, you will have to configure Zammad as " +"a new client/app manually using the above XML metadata file for reference." msgstr "" -#: ../system/core-workflows/limitations.rst:16 -msgid "hide" +#: ../settings/security/third-party/saml.rst:36 +msgid "For instance, when you see this tag:" msgstr "" -#: ../system/core-workflows/limitations.rst:25 -msgid "Some fields stay unavailable to customers" +#: ../settings/security/third-party/saml.rst:42 +msgid "" +"Set the **Assertion Consumer Service Binding URL** (sometimes also listed as " +"**Valid Redirect URIs**) to ``http://your.zammad.domain/auth/saml/callback``." msgstr "" -#: ../system/core-workflows/limitations.rst:19 -msgid "" -"For technical and security reasons, some default fields (the pale ones you " -"can't edit) stay unavailable for display and usage on customer permissions." +#: ../settings/security/third-party/saml.rst:47 +msgid "Set Up User Attribute Mapping" msgstr "" -#: ../system/core-workflows/limitations.rst:23 +#: ../settings/security/third-party/saml.rst:49 msgid "" -"If you require your customers to change e.g. priorities, please consider " -"using workarounds via :doc:`/system/objects` and :doc:`/manage/trigger`." +"Zammad requests the following user attributes (or “properties”) from the IdP:" msgstr "" -#: ../system/core-workflows/limitations.rst:29 -msgid "Ticket title changes not supported in edit mask" +#: ../settings/security/third-party/saml.rst:51 +msgid "Email address (``email``)" msgstr "" -#: ../system/core-workflows/limitations.rst:28 -msgid "" -"It is currently not possible to perform changes of the ticket title in the " -"edit mask (e.g. renaming, set to read-only)." +#: ../settings/security/third-party/saml.rst:52 +msgid "Full name (``name``)" msgstr "" -#: ../system/core-workflows/limitations.rst:37 -msgid "What is out of scope of Core Workflows?" +#: ../settings/security/third-party/saml.rst:53 +msgid "Given name (``first_name``)" msgstr "" -#: ../system/core-workflows/limitations.rst:32 -msgid "" -"There are some things that would count as workflow but are either done via :" -"doc:`/manage/trigger` or :doc:`/manage/scheduler`." +#: ../settings/security/third-party/saml.rst:54 +msgid "Family name (``last_name``)" msgstr "" -#: ../system/core-workflows/limitations.rst:35 -msgid "Such as (but not limited to):" +#: ../settings/security/third-party/saml.rst:56 +msgid "" +"You may need to set up “mappers” (or “mappings”) to tell your IdP how user " +"attributes in SAML correspond to those in Zammad. For a more detailed " +"breakdown, refer to the XML metadata file referenced in the previous section." msgstr "" -#: ../system/core-workflows/limitations.rst:37 -msgid "up- or downgrade permissions of users" +#: ../settings/security/third-party/saml.rst:62 +msgid "Per-IdP Instructions" msgstr "" -#: ../system/core-workflows/limitations.rst:38 -msgid "affecting article creation or listing" +#: ../settings/security/third-party/saml.rst:102 +msgid "Keycloak" msgstr "" -#: ../system/data-privacy.rst:2 -msgid "Data Privacy" +#: ../settings/security/third-party/saml.rst:65 +msgid "" +"**To add Zammad as a client,** save the XML configuration to disk (``https://" +"your.zammad.domain/auth/saml/metadata``) and use **Clients > Clients list > " +"Import client** in the Keycloak admin panel." msgstr "" -#: ../system/data-privacy.rst:4 +#: ../settings/security/third-party/saml.rst:70 msgid "" -"For compliance with GDPR and other data privacy laws, you may wish to " -"**permanently delete users from the system**, along with **all of their " -"associated tickets**." +"To help Zammad **match its own user accounts to Keycloak users**, create a " +"user attribute (or “property”) mapper. In **Clients list**, click on your " +"newly created Client ID, choose the tab **Client scopes** and click on the " +"link which refers to your Zammad instance. Choose **Add mapper > By " +"configuration > User Property** and create a mapper with the following " +"entries:" 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 `!" +#: ../settings/security/third-party/saml.rst:78 +msgid "**Name**" msgstr "" -#: ../system/data-privacy.rst:12 -msgid "" -"Access to this panel requires ``admin.data_privacy`` permissions (introduced " -"in Zammad 3.5)." +#: ../settings/security/third-party/saml.rst:80 +msgid "**Mapper Type**" msgstr "" -#: ../system/data-privacy.rst:15 -msgid "" -"On older systems that have not been updated yet, customers can also be :docs:" -"`deleted via the Zammad console `." +#: ../settings/security/third-party/saml.rst:81 +msgid "``User Property``" msgstr "" -#: ../system/data-privacy.rst:22 -msgid "User deletion dialog in the Data Privacy panel" +#: ../settings/security/third-party/saml.rst:82 +msgid "**Property**" msgstr "" -#: ../system/data-privacy.rst:22 -msgid "" -"The user deletion dialog lists some of the tickets that will be removed from " -"the system along with the user." +#: ../settings/security/third-party/saml.rst:83 +msgid "``emailAddress``" msgstr "" -#: ../system/data-privacy.rst:27 -msgid "Deleting Users via GUI" +#: ../settings/security/third-party/saml.rst:84 +msgid "**SAML Attribute Name**" msgstr "" -#: ../system/data-privacy.rst:29 -msgid "🔥 **All deletions are FINAL!**" +#: ../settings/security/third-party/saml.rst:86 +msgid "**SAML Attribute NameFormat**" msgstr "" -#: ../system/data-privacy.rst:31 -msgid "Once you click “Delete”, the action cannot be canceled or undone." +#: ../settings/security/third-party/saml.rst:87 +msgid "``basic``" msgstr "" -#: ../system/data-privacy.rst:33 +#: ../settings/security/third-party/saml.rst:89 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." +"In the example above, we're telling Zammad that whenever it receives a SAML " +"login request, it should take the ``email`` property from Keycloak, look for " +"a Zammad user with the same ``email`` attribute, and create a new session " +"for that user." msgstr "" -#: ../system/data-privacy.rst:36 -msgid "**The following records cannot be deleted:**" +#: ../settings/security/third-party/saml.rst:95 +msgid "" +"If your Keycloak users' email addresses are stored on another property (*e." +"g.,* ``username``), adjust accordingly." msgstr "" -#: ../system/data-privacy.rst:38 -msgid "your own account" +#: ../settings/security/third-party/saml.rst:98 +msgid "" +"Back in **Settings**, enter the Client ID (``https://your.zammad.domain/auth/" +"saml/metadata``) in the field **Master SAML Processing URL**." msgstr "" -#: ../system/data-privacy.rst:39 -msgid "the system's last remaining administrator account" +#: ../settings/security/third-party/saml.rst:101 +msgid "You also need to enable **Sign assertions**." msgstr "" -#: ../system/data-privacy.rst:42 -msgid "Step 1: Find a User / Confirm Deletion" +#: ../settings/security/third-party/saml.rst:105 +msgid "Step 2: Configure Zammad" msgstr "" -#: ../system/data-privacy.rst:44 -msgid "There are three ways to access the user deletion dialog:" +#: ../settings/security/third-party/saml.rst:107 +msgid "" +"Enable SAML and enter your IdP's details in the Admin Panel under **Settings " +"> Security > Third Party Applications > Authentication via SAML**:" msgstr "" -#: ../system/data-privacy.rst:51 -msgid "**from the user's profile**" +#: ../settings/security/third-party/saml.rst:None +msgid "Example configuration of SAML part 1" msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Accessing the user deletion dialog in a user profile" +#: ../settings/security/third-party/saml.rst:119 +msgid "Display name" msgstr "" -#: ../system/data-privacy.rst:51 -msgid "Click **Action > Delete**." +#: ../settings/security/third-party/saml.rst:116 +msgid "" +"Allows you to define a custom button name for SAML. This helps your users to " +"understand better what the button on the login page does." msgstr "" -#: ../system/data-privacy.rst:58 -msgid "**in the “Manage > Users” Admin Panel**" +#: ../settings/security/third-party/saml.rst:119 +msgid "Defaults to ``SAML``." msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Accessing the user deletion dialog under “Users” in the Admin Panel" +#: ../settings/security/third-party/saml.rst:123 +msgid "IDP SSO target URL" msgstr "" -#: ../system/data-privacy.rst:58 -msgid "Use the **⋮ Actions** menu for the target user." +#: ../settings/security/third-party/saml.rst:122 +msgid "" +"This is the target URL Zammad shall redirect to when the user presses the " +"SAML button. For Keycloak, this needs to look like https://your.domain/" +"realms/your-realm/protocol/saml" msgstr "" -#: ../system/data-privacy.rst:66 ../system/data-privacy.rst:104 -msgid "**in the “System > Data Privacy” Admin Panel**" +#: ../settings/security/third-party/saml.rst:127 +msgid "IDP single logout target URL" msgstr "" -#: ../system/data-privacy.rst:0 +#: ../settings/security/third-party/saml.rst:126 msgid "" -"Accessing the user deletion dialog under “Data Privacy” in the Admin Panel" +"This is the URL to which the single logout request and response should be " +"sent." msgstr "" -#: ../system/data-privacy.rst:65 +#: ../settings/security/third-party/saml.rst:131 +msgid "IDP certificate" +msgstr "" + +#: ../settings/security/third-party/saml.rst:130 msgid "" -"Use the **New Deletion Task** button. Search for users by name or email " -"address." +"The public certificate of your IDP for Zammad to verify during the callback " +"phase." msgstr "" -#: ../system/data-privacy.rst:79 -msgid "**Delete organizations**" +#: ../settings/security/third-party/saml.rst:145 +msgid "IDP certificate fingerprint" msgstr "" -#: ../system/data-privacy.rst:69 +#: ../settings/security/third-party/saml.rst:134 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:" +"The fingerprint of your IDPs public certificate to verify during callback " +"phase." msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Deleting an organization via the user deletion dialog" +#: ../settings/security/third-party/saml.rst:137 +msgid "🔏 **For the IdP certificate / certificate fingerprint:**" msgstr "" -#: ../system/data-privacy.rst:78 +#: ../settings/security/third-party/saml.rst:139 msgid "" -"If this option does not appear, make sure there are no pending deletion " -"tasks for other customers from this organization." +"Provide **only one or the other**—do not provide both! (Between the two, we " +"recommend the signing certificate itself: fingerprints use SHA-1, which `has " +"been broken for a while now `_.)" msgstr "" -#: ../system/data-privacy.rst:82 -msgid "Step 2: Monitor Deletion Job Status" +#: ../settings/security/third-party/saml.rst:144 +msgid "" +"**Keycloak users:** Find your certificate in the Keycloak admin panel under " +"**Realm Settings > Keys > Algorithm: RS256 > Certificate**." msgstr "" -#: ../system/data-privacy.rst:84 +#: ../settings/security/third-party/saml.rst:151 +msgid "Name identifier format" +msgstr "" + +#: ../settings/security/third-party/saml.rst:148 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:" +"This is the unique identifiers field type. Usually it should be ``urn:oasis:" +"names:tc:SAML:1.1:nameid-format:emailAddress``." msgstr "" -#: ../system/data-privacy.rst:98 -msgid "**in the Activity Stream**" +#: ../settings/security/third-party/saml.rst:151 +msgid "Zammad **expects an email address as unique identifier**!" msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Activity Stream showing data privacy tasks" +#: ../settings/security/third-party/saml.rst:155 +msgid "UID attribute name" msgstr "" -#: ../system/data-privacy.rst:94 +#: ../settings/security/third-party/saml.rst:154 msgid "" -"For each deleted user, the Activity Stream will be updated twice—once when " -"the task is created, and once when it's complete." +"Here you can define an attribute that uniquely identifies the user. If " +"unset, the name identifier returned by the IDP is used." msgstr "" -#: ../system/data-privacy.rst:97 -msgid "" -"These notifications are only visible to users with ``admin.data_privacy`` " -"permissions." +#: ../settings/security/third-party/saml.rst:None +msgid "Example configuration of SAML part 2" msgstr "" -#: ../system/data-privacy.rst:0 +#: ../settings/security/third-party/saml.rst:163 msgid "" -"The task list within Data Privacy shows removals being in progress and " -"completed." +"Decide if the certificate for the connection to the IdP service has to be " +"verified or not (default: ``yes``)." msgstr "" -#: ../system/data-privacy.rst:107 -msgid "Frequently Asked Questions" +#: ../settings/security/third-party/saml.rst:169 +msgid "Signing & Encrypting" msgstr "" -#: ../system/data-privacy.rst:121 -msgid "What happens if I receive an email from a deleted customer?" -msgstr "" - -#: ../system/data-privacy.rst:110 +#: ../settings/security/third-party/saml.rst:169 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." +"Define if you want to sign, encrypt, do both or nothing for the requests." msgstr "" -#: ../system/data-privacy.rst:115 -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**." +#: ../settings/security/third-party/saml.rst:179 +msgid "Certificate (PEM)" msgstr "" -#: ../system/data-privacy.rst:130 -msgid "What about user information stored in internal notes or other messages?" +#: ../settings/security/third-party/saml.rst:172 +msgid "" +"Paste the public certificate of your Zammad SAML client, if you want to " +"encrypt the requests." msgstr "" -#: ../system/data-privacy.rst:124 -msgid "" -"The deletion process removes **user accounts and associated tickets only**." +#: ../settings/security/third-party/saml.rst:175 +msgid "Make sure the certificate is:" msgstr "" -#: ../system/data-privacy.rst:126 -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." +#: ../settings/security/third-party/saml.rst:177 +msgid "already valid and not yet expired" msgstr "" -#: ../system/data-privacy.rst:137 -msgid "I deleted an user and can still see a message they sent!" +#: ../settings/security/third-party/saml.rst:178 +msgid "no CA certificate" msgstr "" -#: ../system/data-privacy.rst:133 -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." +#: ../settings/security/third-party/saml.rst:179 +msgid "valid for signing and encrypting" msgstr "" -#: ../system/data-privacy.rst:141 -msgid "I removed a customer, now my reporting is off!" +#: ../settings/security/third-party/saml.rst:185 +msgid "Private key (PEM)" msgstr "" -#: ../system/data-privacy.rst:140 +#: ../settings/security/third-party/saml.rst:182 msgid "" -"When removing users and their tickets, all references are removed. This also " -"affects e.g. Reporting - these information are lost." +"Paste the private key of your Zammad SAML client here, if you want to sign " +"the requests." msgstr "" -#: ../system/data-privacy.rst:145 -msgid "How long does Zammad store created tasks?" +#: ../settings/security/third-party/saml.rst:185 +msgid "Make sure the key is an RSA key with a length of at least 2048 bits." msgstr "" -#: ../system/data-privacy.rst:144 -msgid "" -"Please see the on-premise data section of the :docs:`data privacy ` chapter." +#: ../settings/security/third-party/saml.rst:188 +msgid "Private key secret" msgstr "" -#: ../system/data-privacy.rst:150 -msgid "What about re-assigned tickets? I want to delete them, too." +#: ../settings/security/third-party/saml.rst:188 +msgid "If your private key is secured with a secret, you can provide it here." msgstr "" -#: ../system/data-privacy.rst:148 -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." +#: ../settings/security/third-party/saml.rst:192 +msgid "Your callback URL" msgstr "" -#: ../system/data-privacy.rst:154 -msgid "Why are there so many deletion task entries, I didn't create them!" +#: ../settings/security/third-party/saml.rst:191 +msgid "" +"This URL is needed for your IdP configuration so it knows where to redirect " +"to after successful authentication." msgstr "" -#: ../system/data-privacy.rst:153 +#: ../settings/security/third-party/saml.rst:194 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." +"After saving your input by clicking on the \"Submit\" button, Zammad " +"verifies the provided keys/certificates (e.g. if they are valid for signing/" +"encrypting and if they aren't expired)." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:2 -msgid "Admin Panel Reference" +#: ../settings/security/third-party/saml.rst:199 +msgid "" +"See :ref:`automatic account linking ` for details " +"on how to link existing Zammad accounts to IdP accounts." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:None -msgid "Screenshot of Checkmk settings overview" +#: ../settings/security/third-party/saml.rst:205 +msgid "Automatic account linking doesn't work" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:12 +#: ../settings/security/third-party/saml.rst:206 msgid "" -"Which :doc:`group ` should Checkmk tickets be assigned " -"to as a default (*i.e.,* when none is specified)?" +"Have you double-checked your IdP's user attribute mapping configuration?" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:15 -msgid "(Applies to :ref:`API alerts ` only.)" +#: ../settings/security/third-party/twitter.rst:4 +msgid "" +"It is possible to create a quick login for your helpdesk via Twitter. To do " +"so, you need to follow these steps:" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:21 -msgid "Auto close" +#: ../settings/security/third-party/twitter.rst:8 +msgid "Register Twitter App" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:18 -msgid "" -"Should Zammad automatically close tickets if a service has recovered on its " -"own?" +#: ../settings/security/third-party/twitter.rst:10 +msgid "Go to https://dev.twitter.com/apps and login with your account." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:21 -msgid "(Agents will receive notifications for such closures as appropriate.)" +#: ../settings/security/third-party/twitter.rst:15 +msgid "Click on \"Create App\"" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:30 -msgid "Auto-close state" +#: ../settings/security/third-party/twitter.rst:None +msgid "new app page" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:24 -msgid "What ticket state should be applied when “auto-closing” a ticket?" +#: ../settings/security/third-party/twitter.rst:20 +msgid "" +"Enter app settings. As \"Callback URL\" you need to enter ``https://" +"zammad_host/api/v1/external_credentials/twitter/callback``. You need to " +"replace ``zammad_host`` with the domain of your Zammad system." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:26 +#: ../settings/security/third-party/twitter.rst:24 msgid "" -"You can choose from the seven built-in ticket states. If these states aren't " -"enough for you, you can :ref:`define a new ticket state ` for this purpose as well. This can be useful for tracking " -"tickets with :doc:`reports `, for example." +"After the app has been created, update the application icon and organization " +"attributes." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:35 -#: ../system/integrations/cti/includes/recent-logs.include.rst:2 -#: ../system/integrations/ldap/index.rst:74 -#: ../system/integrations/pgp/index.rst:106 -msgid "Recent Logs" +#: ../settings/security/third-party/twitter.rst:None +msgid "set permissions to receive and send direct messages" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:None -msgid "Screenshot of Checkmk \"Recent Logs\" section" +#: ../settings/security/third-party/twitter.rst:30 +msgid "" +"Next we need to set ``read, write and access direct messages`` permissions " +"for the app." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:41 -msgid "" -"If you're having trouble getting Zammad and Checkmk to play nicely together, " -"this section can help you troubleshoot." +#: ../settings/security/third-party/twitter.rst:None +msgid "click on Keys & Access Token, note them" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:44 +#: ../settings/security/third-party/twitter.rst:36 msgid "" -"It contains a record of the fifty most recent transactions that Zammad knows " -"about, including each one's request/response details and return status." +"Go to \"Keys and Access Token\" tab and note the \"Consumer Key\" and " +"\"Consumer Secret\"." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:2 -msgid "API Reference" +#: ../settings/security/third-party/twitter.rst:40 +msgid "Configure Zammad as Twitter App" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:4 +#: ../settings/security/third-party/twitter.rst:42 msgid "" -"For most users, :ref:`the sample scripts from the Setup Guide ` will do the job just fine. But if you want more fine-grained control" -"—for instance, to create high- and low-priority tickets for different types " -"of system events—then you'll have to customize the data those scripts send " -"to Zammad." +"Go to \"Admin > Security > Twitter > Third Party Applications > Twitter\" " +"Section." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:15 -msgid "" -"This custom script will automatically set all tickets it creates to **high " -"priority** and **assign them to charlie@chrispresso.com**." +#: ../settings/security/third-party/twitter.rst:None +msgid "Admin > Security > Third Party Applications" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:32 -msgid "How Does it Work?" +#: ../settings/security/third-party/twitter.rst:48 +msgid "" +"Fill in the \"Twitter Key\" and the \"Twitter Secret\" and click the " +"\"Submit\" button." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:34 +#: ../settings/security/third-party/twitter.rst:51 msgid "" -"There are two kinds of data you can pass to the API, both in the form of key-" -"value pairs:" +"Now you can link accounts via \"Avatar > Profile > Link Accounts\" or login " +"via Zammad login page." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:44 -msgid "Checkmk parameters" +#: ../settings/security/two-factor.rst:11 +msgid "Two-factor Authentication Methods" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:38 -msgid "" -"are required, and make up the **contents** of the resulting tickets/" -"articles. They also determine whether an event creates a new ticket or " -"updates/closes an existing one." +#: ../settings/security/two-factor.rst:2 +msgid "Two-Factor Authentication" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:42 +#: ../settings/security/two-factor.rst:4 msgid "" -"These are the only values used in the sample scripts. **Use them as-is**; " -"technically, they can be customized, but it's hard to imagine a good reason " -"for it." +"Two-factor authentication (2FA) enhances the security of Zammad accounts by " +"adding an extra layer of verification beyond a password. It requires users " +"to provide two different types of authentication factors, typically " +"something they know (like a password) and something they possess (like a " +"mobile device or a security token), to ensure that only authorized " +"individuals can access the account." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:52 -msgid "Ticket attributes" +#: ../settings/security/two-factor.rst:19 +msgid "Enable Recovery Codes" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:47 +#: ../settings/security/two-factor.rst:21 msgid "" -"are optional, and can be used to **adjust settings** on newly created " -"tickets (*e.g.,* set the owner, group, priority, or state)." +"Recovery codes are one-time use security codes that can be used by the user " +"if they lose access to their other two-factor authentication methods. They " +"cannot be used on their own, they can only be activated if at least one two-" +"factor authentication method is enabled." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:50 -msgid "" -"If you want to customize your Checkmk alert script, do it with these. Simply " -"add an extra “form” option for each one (``-F \"key=value\"``) to your " -"script's ``curl`` command line, as in the example above." +#: ../settings/security/two-factor.rst:None +msgid "Enable Recovery Codes Setting" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:54 -msgid "💡 **It's just an API endpoint!**" +#: ../settings/security/two-factor.rst:30 +msgid "" +"Recovery codes can only be used as a backup method. If enabled, they will be " +"automatically generated for the user once they set up their initial two-" +"factor authentication method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:56 +#: ../settings/security/two-factor.rst:34 msgid "" -"When using Checkmk integration, messages need to be formatted in a certain " -"way, but that *doesn't mean the messages actually have to come from Checkmk*." +"The user will be asked to print out or save the generated recovery codes in " +"a safe place. Once used, a recovery code cannot be reused." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:59 +#: ../settings/security/two-factor.rst:37 msgid "" -"If you use another monitoring tool that's not officially supported by " -"Zammad, there's probably a way to make it work with your Checkmk callback " -"URL." +"Users will also have an option to regenerate their recovery codes at any " +"time, which invalidates already existing recovery codes and provides them " +"with a list of fresh codes." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:63 -msgid "Checkmk Parameters" +#: ../settings/security/two-factor.rst:41 +msgid "" +"After you enable this setting, when the user completes a setup of their " +"initial two-factor authentication method, they will be presented with a list " +"of recovery codes and instructed to save them for later use." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:65 -msgid "" -"When a notification is received, Zammad creates a new article containing the " -"details of the event that triggered it:" +#: ../settings/security/two-factor.rst:None +msgid "Recovery Codes Generation Modal Dialog" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:None -msgid "Checkmk article body" +#: ../settings/security/two-factor.rst:50 +msgid "Enforce the Set Up of the Two-Factor Authentication" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:72 +#: ../settings/security/two-factor.rst:52 msgid "" -"These details come from the fields listed below, which correspond to " -"parameters provided by Checkmk (``$NOTIFY_*``)." +"In case you wish to require your users to set up at least one two-factor " +"authentication method for their account, you can do this by selecting " +"specific user roles the requirement applies to in **Enforced for user " +"roles** setting. Of course you must have at least one two-factor " +"authentication method enabled for this setting to take effect." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:75 -msgid "**Required fields are marked with an asterisk (\\*).**" +#: ../settings/security/two-factor.rst:None +msgid "Enforced for User Roles Setting" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:79 -msgid "event_id\\*" +#: ../settings/security/two-factor.rst:62 +msgid "" +"After you change this setting, if the user has one of the selected roles on " +"their account, they will be forced to set up the two-factor authentication " +"upon next sign in or application reload." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:78 +#: ../settings/security/two-factor.rst:66 msgid "" -"A unique ID for the system event. (``$NOTIFY_SERVICEPROBLEMID`` / " -"``$NOTIFY_HOSTPROBLEMID``)" +"A modal dialog with instructions will be shown, and they will not be able to " +"do any work before they set up at least one two-factor method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:86 -msgid "host\\*" +#: ../settings/security/two-factor.rst:None +msgid "Modal Dialog for Enforcing Two-Factor Authentication Set Up" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:82 +#: ../settings/security/two-factor.rst:74 +msgid "Reset Two-Factor Authentication for a Specific User" +msgstr "" + +#: ../settings/security/two-factor.rst:76 msgid "" -"The hostname of the system that the event originated from. " -"(``$NOTIFY_HOSTNAME``)" +"In case an user isn't able to login anymore because of an inaccessible " +"second factor, you can reset the user's 2FA method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:85 +#: ../settings/security/two-factor.rst:79 msgid "" -"Used to determine if a new event belongs to an existing ticket. Also used in " -"the subject line of the resulting article (“ is ”)." +"To do this, go to the user management and search for the relevant user. " +"After you found the account, click the button in the action column and " +"select \"Manage Two-Factor Authentication\":" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:96 -msgid "service" +#: ../settings/security/two-factor.rst:None +msgid "Context menu in action column in user management" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:89 +#: ../settings/security/two-factor.rst:87 msgid "" -"The name of the service that the event originated from. " -"(``$NOTIFY_SERVICEDESC``)" +"After selecting this, you can see a dialog where you can either reset one " +"2FA method or reset all of the user's 2FA methods:" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:92 -msgid "Used to determine if a new event belongs to an existing ticket." +#: ../settings/security/two-factor.rst:None +msgid "Dialog for resetting user's 2FA method" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:94 -#: ../system/integrations/checkmk/api-reference.rst:110 -msgid "Displayed as ``-`` when omitted." +#: ../settings/security/two-factor.rst:94 +msgid "" +"Choose the fitting one, click on the corresponding \"Remove ...\" button and " +"confirm your action. The user now has to setup a new 2FA method, depending " +"on your 2FA configuration." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:104 -msgid "state\\*" +#: ../settings/security/two-factor/authenticator-app.rst:2 +msgid "Authenticator App" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:99 +#: ../settings/security/two-factor/authenticator-app.rst:4 msgid "" -"The current state of the service or host in question. " -"(``$NOTIFY_SERVICESTATE`` / ``$NOTIFY_HOSTSTATE``)" +"The authenticator app method is a type of two-factor authentication that " +"uses a mobile application to generate one-time codes for account " +"verification. After setting up the authenticator app on their device, the " +"user links it to their Zammad account." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:102 +#: ../settings/security/two-factor/authenticator-app.rst:12 msgid "" -"Used to detect when a ticket should be auto-closed (*i.e.,* on ``OK``/" -"``UP``). Also used in the subject line of the resulting article (“ is " -"”)." +"When logging in, the user is prompted to enter a time-sensitive code " +"generated by the app, in addition to their password. This code acts as the " +"second factor of authentication, providing an extra layer of security as it " +"changes periodically and is unique to the user's device." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:110 -msgid "text" +#: ../settings/security/two-factor/authenticator-app.rst:None +msgid "Security Code in Google Authenticator App" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:107 +#: ../settings/security/two-factor/authenticator-app.rst:22 msgid "" -"The output of the process that triggered the event. " -"(``$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" +"The app generates codes based on a shared secret key stored securely on both " +"the user's device and the server, ensuring a synchronized and secure " +"authentication process. The method of generating the codes is sometimes also " +"called TOTP (time-based one-time password)." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:121 -msgid "" -"The Object Manager attribute panel displays built-in and custom\n" -"attribute names." +#: ../settings/security/two-factor/authenticator-app.rst:28 +msgid "Enabling the Authenticator App Method" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:121 -msgid "Find a complete list of ticket attributes in the Object Manager." +#: ../settings/security/two-factor/authenticator-app.rst:30 +#: ../settings/security/two-factor/security-keys.rst:28 +msgid "To enable the method, just toggle the switch on in the settings." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:123 -msgid "" -"Ticket attributes are entirely optional, and can be used to customize the " -"tickets that Checkmk creates. (Note that these attributes will be ignored if " -"a new event belongs to an existing ticket.)" +#: ../settings/security/two-factor/authenticator-app.rst:None +msgid "Authenticator App Switch in Settings" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:128 +#: ../settings/security/two-factor/authenticator-app.rst:36 msgid "" -"Why would you want to do this? Maybe you have only one IT guy, and all " -"system monitoring issues should be automatically assigned to him. Or, maybe " -"you're creating multiple notification rules so that database outages take " -"higher priority than disk space warnings." +"Now the users will be able to set up this two-factor authentication method " +"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " +"Once they do, on next sign-in with password, they will be asked to provide " +"an additional security code generated by their mobile device." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:135 -msgid "In most cases, you'll probably want to set one of the following:" +#: ../settings/security/two-factor/security-keys.rst:2 +msgid "Security Keys" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:137 -msgid "group" +#: ../settings/security/two-factor/security-keys.rst:4 +msgid "" +"The security keys method is a type of a two-factor authentication that uses " +"Web Authentication API in the browser for verifying user's identity. The " +"user can register multiple hardware or software security keys with their " +"Zammad account and then they can use it during the sign-in process." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:139 -msgid "state" +#: ../settings/security/two-factor/security-keys.rst:12 +msgid "" +"When logging in, the user is prompted to provide the same security key they " +"registered with their account, in addition to their password. This key acts " +"as the second factor of authentication, providing an extra layer of security." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:140 -msgid "priority" +#: ../settings/security/two-factor/security-keys.rst:None +msgid "Security Key dialog in Safari on macOS" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:142 +#: ../settings/security/two-factor/security-keys.rst:21 msgid "" -"but in practice, you can set almost any attribute, including :doc:`custom " -"ones you created through the Object Manager `." -msgstr "" - -#: ../system/integrations/checkmk/api-reference.rst:145 -msgid "Please note that the following attributes are **not customizable**:" +"The type of the key can range from hardware USB sticks to passkeys stored in " +"a device of user's choice. Which type can be used depends on the browser " +"flavor and the platform of the user." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:147 -msgid "title" +#: ../settings/security/two-factor/security-keys.rst:26 +msgid "Enabling the Security Keys Method" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:148 -msgid "id" +#: ../settings/security/two-factor/security-keys.rst:None +msgid "Security Keys Switch in Settings" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:149 -msgid "ticket number" +#: ../settings/security/two-factor/security-keys.rst:34 +msgid "" +"Now the users will be able to set up this two-factor authentication method " +"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " +"Once they do, on next sign-in with password, they will be asked to provide " +"the same security key they registered during the setup." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:151 -msgid "created_by_id" +#: ../settings/system/system-selfhosted.include.rst:3 +msgid "" +"Below settings are only available to self hosted users. In hosted " +"environments we're handling these settings for you to ensure service " +"stability." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:152 -msgid "updated_by_id" +#: ../settings/system/base.rst:11 +msgid "Fully Qualified Domain Name" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:155 -msgid "Which Values Can Be Set?" +#: ../settings/system/base.rst:7 +msgid "The URL of your Zammad installation." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:157 -msgid "😵 **Invalid values → unpredictable behavior**" +#: ../settings/system/base.rst:9 ../settings/system/base.rst:17 +msgid "This setting is used within :doc:`/misc/variables` and notifications." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:159 -msgid "" -"If you provide a value that Zammad doesn't understand (*e.g.,* ``-F " -"\"priority=high\"``), it's not always clear what will happen. In some cases, " -"a ticket will be created with the default values instead - but in others, it " -"may not be created at all!" +#: ../settings/system/system-base.include.rst:1 +msgid "It is automatically set by the *Getting Started wizard*." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:164 -msgid "So what values does Zammad understand, then? Well, it depends..." +#: ../settings/system/system-base.include.rst:5 +msgid "Changing this setting also changes callback URLs for your channels etc." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:168 -msgid "Use an email address or username:" +#: ../settings/system/system-base.include.rst:6 +msgid "This setting can have negative affects on being able to login." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:190 -msgid "group & priority" +#: ../settings/system/base.rst:19 +msgid "HTTP type" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:175 -msgid "Refer to the dropdown menus in the ticket pane:" +#: ../settings/system/base.rst:14 +msgid "" +"The HTTP type tells your installation how your clients connect. This is " +"relevant for authentication and cookie security." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:0 -msgid "See possible values for certain attributes in the ticket pane." +#: ../settings/system/base.rst:31 +msgid "SystemID" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:187 -msgid "🙅 **Ticket state CANNOT be set this way!**" +#: ../settings/system/base.rst:22 +msgid "" +"This ID is being used within your ticket number. In case you're " +"communicating with another ticket system with similar ticket number schemes " +"this ID greatly reduces the risk of false follow ups." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:189 +#: ../settings/system/base.rst:26 msgid "" -"Why? Because ``-F \"state=...\"`` is already used :ref:`as a Checkmk " -"parameter `." +"The SystemID is randomly selected upon installation of Zammad (``1-99``)." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:222 -msgid "Everything Else" +#: ../settings/system/base.rst:30 +msgid "" +"**Do not** change this setting in a productive system! Your Zammad " +"installation may no longer recognize old ticket number based follow ups upon " +"change!" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:193 -msgid "" -"To set any other attributes, it helps to know your way around the :docs:" -"`rails console `. Valid values are those that you can " -"set with a string:" +#: ../settings/system/frontend.rst:2 +msgid "Frontend" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:218 -msgid "These values can then be passed directly to the API:" +#: ../settings/system/frontend.rst:22 +msgid "Core Workflow Ajax Mode" msgstr "" -#: ../system/integrations/checkmk/index.rst:16 -msgid "How does it work?" +#: ../settings/system/frontend.rst:6 +msgid "" +"This setting allows administrators to enforce :doc:`/system/core-workflows` " +"to use Ajax-Calls instead of web sockets. You'll usually only need this if " +"you experience serious issues as noted below." msgstr "" -#: ../system/integrations/checkmk/index.rst:2 -msgid "Checkmk" +#: ../settings/system/frontend.rst:10 +msgid "**🤓 Possible (technical) reasons**" msgstr "" -#: ../system/integrations/checkmk/index.rst:4 +#: ../settings/system/frontend.rst:12 msgid "" -"`Checkmk `_ is a powerful IT monitoring tool that can " -"send real-time status alerts to Zammad via email or REST API. Set these " -"alerts up in Checkmk, and Zammad will automatically create, update, and " -"close tickets based on the health of your system:" +"In some cases, your network structure (e.g. firewalls, proxies) may " +"disconnect long web socket connections. This leads to select fields staying " +"empty (e.g. owner selection *after* selecting your group) or fields not " +"shown / hidden (e.g. when switching to or from pending states, the \"pending " +"till\" field not showing / hiding)." msgstr "" -#: ../system/integrations/checkmk/index.rst:14 -msgid "Screenshot of ticket created by Checkmk notifications" +#: ../settings/system/frontend.rst:18 +msgid "" +"Please keep in mind that the Ajax fallback may cause serious pressure on " +"your application server. If you have the choice stick to web sockets." msgstr "" -#: ../system/integrations/checkmk/index.rst:14 -msgid "Multiple alerts, same ticket." +#: ../settings/system/frontend.rst:22 +msgid "Default: ``no`` (inactive)" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:2 -msgid "Setup Guide" +#: ../settings/system/frontend.rst:53 +msgid "Show calendar weeks in the picker of date/datetime fields" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:4 +#: ../settings/system/frontend.rst:25 msgid "" -"Whenever the Checkmk integration is enabled, Zammad listens for messages on " -"its API and over email. As long as those messages follow the required " -"format, Zammad will create new tickets (or find and update existing ones) " -"based on the message contents." +"With this setting you can instruct Zammad to provide week number display " +"globally for all users. Calendar with week number display are usually used " +"in business sectors and may not be relevant for everyone." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:10 +#: ../settings/system/frontend.rst:29 msgid "" -"That means that “setting up Checkmk integration” is simply a matter of " -"**adding configuration to your Checkmk site**: telling it when to send these " -"messages and what to say. To do that, you'll need to create a new " -"**notification rule** (see `Checkmk's official docs `_ for help with that)." +"This setting affects *all areas* - you'll also see week numbers in the admin " +"panel for e.g. triggers and macros." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:17 -msgid "" -"As part of this new rule, you'll have to choose a **notification method** " -"(*i.e.,* a script to execute whenever the rule is triggered). This script " -"will be written by you (samples below), and contain the logic for sending " -"API/email messages to Zammad:" +#: ../settings/system/frontend.rst:32 +msgid "Default: ``no`` (not shown)" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:26 -msgid "Checkmk \"New Rule\" dialog" +#: ../settings/system/frontend.rst:53 +msgid "Here's the difference:" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:26 -msgid "" -"Find your custom scripts in the Checkmk WATO under **Notifications > New " -"Rule > Notification Method**." +#: ../settings/system/frontend.rst:0 +msgid "Screenshot showing Zammad's date picker (in the default way)" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:29 -msgid "" -"Once you're done setting up your new rule, you're all set! New tickets " -"should start coming in and auto-updating any time your rule is triggered." +#: ../settings/system/frontend.rst:41 +msgid "Set to ``no``" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:33 +#: ../settings/system/frontend.rst:0 msgid "" -"(If you need help troubleshooting, be sure to check the :ref:`checkmk-recent-" -"logs`.)" +"Screenshot showing Zammad's date picker with\n" +"week numbers enabled" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:38 -msgid "API Alerts" +#: ../settings/system/frontend.rst:50 +msgid "Set to ``yes``" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:40 +#: ../settings/system/index.rst:4 msgid "" -"To add these scripts in the Checkmk WATO, copy them into your Checkmk " -"installation directory and make them executable. (Be sure to replace the " -"``zammad.example.com`` callback URL with the one found in your admin panel.)" +"For your overview we split each tab within system settings into its own page:" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:60 -msgid "Service notification" +#: ../settings/system/index.rst:16 +msgid "Console Based Settings" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:46 +#: ../settings/system/index.rst:18 msgid "" -"For updates on the status of the software running on your server (*e.g.,* " -"postgres)." +"There's some console based settings we didn't put into the UI. However, you " +"may find them helpful - you can find them in our :docs:`hidden settings ` section." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:75 -msgid "Host notification" +#: ../settings/system/network.rst:2 +msgid "Network" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:63 -msgid "For updates on the status of the server itself." +#: ../settings/system/network.rst:8 +msgid "" +"The proxy settings can only be saved after successfully testing the proxy " +"connection." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:77 -msgid "🤔 **What's with all the env vars?**" +#: ../settings/system/network.rst:15 +msgid "Proxy Address." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:79 +#: ../settings/system/network.rst:12 msgid "" -"Whenever Checkmk runs these scripts, it needs to provide some information " -"about the event that triggered the notification. This information is passed " -"in the form of these ``$NOTIFY_*`` environment variables." +"Allows you to provide a proxy server if needed. This is relevant for network " +"communication by Zammad." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:85 -msgid "" -"You can specify additional parameters to pass to the script when you're " -"setting up your notification rule, but the ones you see here are all " -"provided by default." +#: ../settings/system/network.rst:15 +msgid "It **does not** affect the update process or Elasticsearch." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:90 -msgid "Email Alerts" +#: ../settings/system/network.rst:18 +msgid "Username for proxy connection." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:94 +#: ../settings/system/network.rst:18 msgid "" -"🐞 **There are known bugs** in Zammad's processing of email from Checkmk. " -"This section will be completed once they have been resolved. (Learn more at " -"GitHub issues `#2377 `_ & " -"`#2180 `_.)" +"If your proxy server requires authentication, provide the username here." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:100 -msgid "In the meantime, we encourage you to set up API alerts instead." +#: ../settings/system/network.rst:21 +msgid "Password for proxy connection." msgstr "" -#: ../system/integrations/clearbit.rst:2 -msgid "Clearbit" +#: ../settings/system/network.rst:21 +msgid "" +"If your proxy server requires authentication, provide the password here." msgstr "" -#: ../system/integrations/clearbit.rst:4 +#: ../settings/system/network.rst:26 +msgid "No proxy for the following hosts." +msgstr "" + +#: ../settings/system/network.rst:24 msgid "" -"With our Clearbit integration, you can easily enrich the information " -"provided by Zammad. If the customers or agents email address is known to " -"Clearbit, it will share all information it has regarding the user with " -"Zammad. Those information can include the following:" +"Exception list for hosts you can't or don't want to reach via proxy server." msgstr "" -#: ../system/integrations/clearbit.rst:9 -msgid "Avatar" +#: ../settings/system/network.rst:27 +msgid "Default: ``localhost,127.0.0.0,::1``" msgstr "" -#: ../system/integrations/clearbit.rst:10 -msgid "Address information" +#: ../settings/system/services.rst:2 +msgid "Services" msgstr "" -#: ../system/integrations/clearbit.rst:11 -msgid "Website information" +#: ../settings/system/services.rst:10 +msgid "Image Service" msgstr "" -#: ../system/integrations/clearbit.rst:12 -msgid "A BIO (as Note by default)" +#: ../settings/system/services.rst:5 +msgid "Defines the backend for user and organization image lookups." msgstr "" -#: ../system/integrations/clearbit.rst:14 -msgid "" -"If needed, you can add further custom objects and add mappings to them, so " -"the Clearbit information can be filled within the database. In general you " -"can get any information from Clearbit, as long as you have a mapping to an " -"Zammad object." +#: ../settings/system/services.rst:7 +msgid "Default: ``Zammad Image Service`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:21 +#: ../settings/system/services.rst:9 msgid "" -"Clearbit does have a mapping of fields like LDAP and Exchange have, but does " -"not \"win\" against Zammad information. This means that if you have e.g. the " -"last name field filled in already and Clearbit has other information on " -"that, it will not be updated." +"Make sure your on premise installation has ``HTTPS`` access to ``images." +"zammad.com``." msgstr "" -#: ../system/integrations/clearbit.rst:26 -msgid "" -"However: If let's say the last name has been set by Clearbit and Zammad " -"notices that the last name on the Clearbit source has changed, Zammad will " -"also update this value." +#: ../settings/system/services.rst:18 +msgid "Geo Calendar Service" msgstr "" -#: ../system/integrations/clearbit.rst:33 +#: ../settings/system/services.rst:13 msgid "" -"The configuration of Clearbit is really easy and done fast! Just login to " -"your Clearbit-Account, go to \"API\" and copy the secret-API-Key." +"Defines the backend for geo calendar lookups. Used for initial calendar " +"setup." msgstr "" -#: ../system/integrations/clearbit.rst:38 -msgid "" -"Now change to your Zammad instance, go to Integrations (System) -> Clearbit " -"in the admin panel. Paste your API-Key into the API-Key-Field and decide if " -"Zammad should create unknown Organizations automatically, if the user does " -"not have one yet (and Clearbit knows it). The shared option decides if the " -"new organizations Zammad creates with Clearbit should be shared ones." +#: ../settings/system/services.rst:16 +msgid "Default: ``Zammad GeoCalendar Service`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:47 +#: ../settings/system/services.include.rst:2 msgid "" -"If you're unsure what option to choose, better stick with \"no\". You can " -"also learn more about :doc:`/manage/organizations/index`." +"Make sure your on premise installation has ``HTTPS`` access to ``geo.zammad." +"com``." msgstr "" -#: ../system/integrations/clearbit.rst:52 -msgid "" -"The Mapping option works similar to the mapping within the Exchange and LDAP " -"sync. You can add further mappings for e.g. custom fields if you need more " -"information that Clearbit can provide." +#: ../settings/system/services.rst:26 +msgid "Geo IP Service" msgstr "" -#: ../system/integrations/clearbit.rst:58 +#: ../settings/system/services.rst:21 msgid "" -"If you want to add more Clearbit fields and want to learn more about " -"available fields on their API, you can take a look at their `API " -"documentation `_." +"Defines the backend for geo IP lookups. Shows also location of an IP address " +"if an IP address is shown." msgstr "" -#: ../system/integrations/clearbit.rst:62 -msgid "" -"If you're happy with the above chosen Settings and your mapping, just save " -"the changes and enable Clearbit integration. Zammad will now start polling " -"the Clearbit API as users contact you." +#: ../settings/system/services.rst:24 +msgid "Default: ``Zammad GeoIP Service`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:68 -msgid "" -"Zammad does not synchronize with Clearbit on a regular basis, but on demand " -"if needed. This saves API calls." +#: ../settings/system/services.rst:32 +msgid "Geo Location Service" msgstr "" -#: ../system/integrations/clearbit.rst:73 +#: ../settings/system/services.rst:29 msgid "" -"Below the Settings and Mappings, you'll find our Integration log. You can " -"see what requests Zammad sent to Clearbit and also the APIs Response." +"Defines the backend for geo location lookups to store geo locations for " +"addresses." msgstr "" -#: ../system/integrations/clearbit.rst:78 +#: ../settings/system/services.rst:32 msgid "" -"By the way, you can also view the API log on the Clearbit website - the " -"information seen is basically the same." -msgstr "" - -#: ../system/integrations/clearbit.rst:84 -msgid "Example When Adding a User" +"Default: ``OpenStreetMap (ODbL 1.0, http://osm.org/copyright)`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:86 +#: ../settings/system/services.rst:36 msgid "" -"To show you how fast information is added, we added a small Screencast " -"below. This shows the creation of the User Alex from Clearbit. As we already " -"set the last name of Alex to \"X\", Zammad did not update it. What Zammad " -"did was to add further information it received from Clearbit." +"You can find a detailed privacy information on what we store for how long on " +"our :docs:`Privacy Appendix ` inside of our System " +"Documentation." msgstr "" -#: ../system/integrations/cti/generic.rst:2 -msgid "CTI (generic)" +#: ../settings/system/storage.rst:2 +msgid "Storage" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:1 +#: ../settings/system/storage.rst:6 msgid "" -"This integration enables Zammad to provide a caller log to your agents. With " -"this your agents can greet your customers by their name and are supported by " -"Zammad with automatically opening a new ticket dialog or the user profile." +"Here you can define where Zammad stores attachments for tickets and the " +"knowledge base. By default, we're writing to the ``Database`` - you can " +"switch to ``Filesystem`` or ``Simple Storage (S3)`` at any time. In this " +"case please have a look on the following instructions." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:6 +#: ../settings/system/storage.rst:11 msgid "" -"Click the toggle next to the heading to activate or deactivate this " -"integration." +"If you have a busy Zammad instance, we strongly encourage you to use " +"filesystem storage instead of \"Database\". This will greatly improve system " +"performance (de-crease database load and size)." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:9 -msgid "" -"If you want to learn more on how your agents can use this function, please " -"refer the :user-docs:`user documentation `." +#: ../settings/system/storage.rst:19 +msgid "Database" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:14 +#: ../settings/system/storage.rst:17 msgid "" -"Automatically opening new ticket dialogues or user profiles requires agent " -"to extension mapping - see more below." -msgstr "" - -#: ../system/integrations/cti/includes/introduction.include.rst:20 -msgid "Please note the following limitations to reduce confusion later on:" +"This is the default storage method. The attachments are stored directly in " +"the database. If your Zammad instance grows, we recommend one of the other " +"methods to maintain performance." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:22 -msgid "CTI integrations provide caller log functions only." +#: ../settings/system/storage.rst:38 +msgid "Filesystem" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:23 +#: ../settings/system/storage.rst:22 msgid "" -"This integration does not provide any VoIP functionalities; you can't make " -"phone calls from within Zammad." +"This storage method is recommended for all Zammad instances, especially for " +"those with a higher load. If you choose filesystem, your files are written " +"to ``/opt/zammad/storage/``." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:25 +#: ../settings/system/storage.rst:26 msgid "" -"If your browser supports ``tel``-URLs, you can click on phone numbers for " -"automatic dialing. This requires additional software / configuration on your " -"agent's computers." +"Moving attachments from \"Database\" to \"Filesystem\" can be run during " +"production use. However, you should consider your framework conditions (e.g. " +"bandwidth, system load in production) to define the right moment." msgstr "" -#: ../system/integrations/cti/generic.rst:9 -#: ../system/integrations/cti/placetel.rst:14 -#: ../system/integrations/cti/sipgate.rst:14 -msgid "Please provide the following requirements:" +#: ../settings/system/storage.rst:32 +msgid "**You noticed slow updates of Zammad?**" msgstr "" -#: ../system/integrations/cti/generic.rst:11 +#: ../settings/system/storage.rst:34 msgid "" -"A telephone system that supports webhooks (outbound) (best option are those " -"that allow customizing the calls)." +"While Zammad is beeing updated, it enforces a recursive \"change " +"owner\" (chown) for this directory. For instances with many files this can " +"be time consuming. To mitigate that you can move your files and create a " +"symlink in ``/opt/zammad/storage/`` to the new directory. Of course you have " +"to make sure on your own that the permissions are always correct." msgstr "" -#: ../system/integrations/cti/generic.rst:13 -msgid "A unique Call-ID during the call session." +#: ../settings/system/storage.rst:95 +msgid "Simple Storage (S3)" msgstr "" -#: ../system/integrations/cti/generic.rst:14 -msgid "Call event data (both numbers and direction)." +#: ../settings/system/storage.rst:41 +msgid "" +"To use the Simple Storage (S3), you have to provide some settings, which " +"can't be accessed in the UI (see instructions below)." msgstr "" -#: ../system/integrations/cti/generic.rst:15 -msgid "Your Zammad instance must be reachable for your telephony system." +#: ../settings/system/storage.rst:44 +msgid "" +"⚠️ Please note that the current implementation is in its early stages and can " +"be modified in the future." msgstr "" -#: ../system/integrations/cti/generic.rst:17 +#: ../settings/system/storage.rst:47 msgid "" -"If you want to learn more on what kind of requests are supported by Zammad " -"and what it expects, please consult our :docs:`CTI-API documentation `." +"The prerequisite is to have access to a S3-compatible storage and to have " +"all necessary parameters available (which depends on your storage provider; " +"if in doubt, please ask there for help)." msgstr "" -#: ../system/integrations/cti/generic.rst:22 -#: ../system/integrations/cti/placetel.rst:27 -#: ../system/integrations/cti/sipgate.rst:30 -msgid "Available Settings" +#: ../settings/system/storage.rst:51 +msgid "Steps to configure S3:" msgstr "" -#: ../system/integrations/cti/generic.rst:29 -#: ../system/integrations/cti/placetel.rst:41 -#: ../system/integrations/cti/sipgate.rst:40 -msgid "Endpoint Settings" +#: ../settings/system/storage.rst:53 +msgid "" +"Copy ``config/zammad/storage.yml.dist`` to ``config/zammad/storage.yml``" msgstr "" -#: ../system/integrations/cti/generic.rst:25 -msgid "" -"Zammad will list your generic CTI endpoint here. It contains a unique token " -"so ensure to keep this URL save." +#: ../settings/system/storage.rst:54 +msgid "Edit the copied file in one of the following ways:" msgstr "" -#: ../system/integrations/cti/generic.rst:28 +#: ../settings/system/storage.rst:56 msgid "" -"You'll need this endpoint for your PBX to talk to Zammad, see :docs:`CTI-API " -"documentation `." +"Either provide your S3 configuration with one attribute per line like in the " +"upper area of the file" msgstr "" -#: ../system/integrations/cti/includes/important-dont-forget-saving.include.rst:3 +#: ../settings/system/storage.rst:58 msgid "" -"All following options **do not save automatically**. Always use the Save " -"button on the lower end of the integration page!" +"Or provide your S3 configuration as an URL (which you can find at the end of " +"the file). Note: you can also provide this URL as environment variable (:" +"docs:`see system documentation `) without using this yml-file." msgstr "" -#: ../system/integrations/cti/generic.rst:43 -#: ../system/integrations/cti/placetel.rst:49 -#: ../system/integrations/cti/sipgate.rst:52 -msgid "Call Settings" +#: ../settings/system/storage.rst:62 +msgid "" +"We recommend the deletion of the not used configuration style to avoid " +"inconsistencies." msgstr "" -#: ../system/integrations/cti/generic.rst:39 -#: ../system/integrations/cti/placetel.rst:49 -#: ../system/integrations/cti/sipgate.rst:37 -#: ../system/integrations/cti/sipgate.rst:50 -msgid "Inbound" +#: ../settings/system/storage.rst:65 +msgid "Restart Zammad so the config file / environment variable is loaded" msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:1 +#: ../settings/system/storage.rst:66 msgid "" -"This option allows you to block specific incoming caller IDs. It allows you " -"to temporarily reject e.g. spam callers without having to contact providers " -"or PBX administrators." +"Set the \"Storage Method\" in Zammad to ``Simple Storage (S3)`` in Settings " +"> System > Storage and click on \"Submit\". After that, Zammad checks your " +"configuration and the connection to the service and will raise an error " +"message if something is wrong." msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:11 -msgid "Caller ID to block" +#: ../settings/system/storage.rst:72 +msgid "A very simple storage configuration could look like this:" msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 -msgid "Provide caller IDs to block in ``E.164`` format." +#: ../settings/system/storage.rst:85 +msgid "" +"Before setting the storage method to ``Simple Storage (S3)`` (step 4), " +"please make sure to have a working setup." msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:8 +#: ../settings/system/storage.rst:88 msgid "" -"Your telephony system has to support this function. Zammad will send a " -"``reject`` response which will cause your telephony system to hang up the " -"call. To callers this usually will feel like the line is busy." +"You can verify this by running ``rails r 'Rails.logger = Logger.new(STDOUT); " +"pp Store::Provider::S3.ping?'`` in your Zammad directory. If everything is " +"fine, you should see ``true``, else you should see ``false`` and a simple " +"error message." msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:14 +#: ../settings/system/storage.rst:93 msgid "" -"Provide a meaningful note for your fellow administrators to remind yourself " -"why you've chosen to block the number." +"If you installed Zammad through a package manager (rather than from source), " +"replace ``rails r`` with ``zammad run rails r`` above. To learn more, see :" +"docs:`Administration via Console `." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 -#: ../system/integrations/cti/includes/outbound-calls.include.rst:17 -#: ../system/integrations/cti/sipgate.rst:40 -msgid "Outbound" +#: ../settings/ticket.rst:4 +msgid "" +"Here you can adjust general ticket settings. Additional ones for the ticket " +"composer interface can be found in the :doc:`/misc/composer`." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:1 -msgid "" -"In many cases you may want to use a different caller ID depending on the " -"destination you're calling. This may apply due to specific connection rates " -"to other countries or because you want your customer to feel you're calling " -"from the same country." +#: ../settings/ticket.rst:11 +msgid "Ticket Hook (default: ``Ticket#``)" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:6 -msgid "This option expects ``E.164`` number formats." +#: ../settings/ticket.rst:11 +msgid "The identifier for a ticket; *e.g.,* Ticket#, Call#, MyTicket#." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 -msgid "Destination caller ID" +#: ../settings/ticket.rst:38 +msgid "Ticket Hook Position (default: ``right``)" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:5 -msgid "The caller ID or number you're trying to call." +#: ../settings/ticket.rst:14 +msgid "" +"With this setting you can decide (if) where to insert the ticket number." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:7 -msgid "You can use wildcards for e.g. country specific outbound numbers like:" +#: ../settings/ticket.rst:20 +msgid "*Right*" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:9 -msgid "``49*`` for Germany" +#: ../settings/ticket.rst:17 +msgid "" +"This setting will add the ticket reference on the right site of the subject." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:10 -msgid "``4930*`` for Berlin / Germany landlines" +#: ../settings/ticket.rst:20 +msgid "Example: ``Some Subject [Ticket#12345]``" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 -msgid "``33*`` for France" +#: ../settings/ticket.rst:26 +msgid "*Left*" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:15 -msgid "Set Outbound caller ID" +#: ../settings/ticket.rst:23 +msgid "" +"This setting will add the ticket reference on the left site of the subject." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:14 -msgid "" -"The outbound caller ID to set (the number your customer sees on his display) " -"in ``E.164`` number format." +#: ../settings/ticket.rst:26 +msgid "Example: ``[Ticket#12345] Some Subject``" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 -msgid "Provide a short description for fellow administrators." +#: ../settings/ticket.rst:29 +msgid "*None*" msgstr "" -#: ../system/integrations/cti/includes/generic-cti-support-note.includes.rst:3 -msgid "" -"This option requires your PBX to send a specific request to Zammad *before " -"dialing*. Please consult the :docs:`CTI API ` in case " -"you're not sure." +#: ../settings/ticket.rst:29 +msgid "This will completely remove ticket references from the subject." msgstr "" -#: ../system/integrations/cti/generic.rst:52 -#: ../system/integrations/cti/placetel.rst:54 -#: ../system/integrations/cti/sipgate.rst:59 -msgid "Other Settings" +#: ../settings/ticket.rst:33 +msgid "" +"Please ensure to take a look at :doc:`/channels/email/settings` within the " +"email channel to ensure you have at least one reference that helps Zammad to " +"assign follow-ups correctly." msgstr "" -#: ../system/integrations/cti/includes/other-settings-intro.include.rst:1 +#: ../settings/ticket.rst:37 msgid "" -"Below you can find all available additional settings for this CTI " -"integration. For your overview we're sorting them by appearance and " -"reference their description first." +"Disabling this and not setting up any further follow up search will lead to " +"unexpected results!" msgstr "" -#: ../system/integrations/cti/includes/default-caller-id.include.rst:2 -#: ../system/integrations/cti/includes/default-caller-id.include.rst:1 -msgid "Default caller ID for outbound calls" +#: ../settings/ticket.rst:65 +msgid "" +"Ticket Last Contact Behaviour (default: ``Use the start time of the last " +"customer thread (which may consist of multiple articles).``)" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:16 -#: ../system/integrations/cti/includes/records-caller-log.include.rst:15 -msgid "Shown records in caller log" +#: ../settings/ticket.rst:41 +msgid "" +"This setting changes the way Zammad updates the ``Last Contact`` value of a " +"ticket. This is fairly important for overviews and what you expect upon " +"ticket updates of a customer." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:2 +#: ../settings/ticket.rst:52 msgid "" -"Allows you to set the number of shown caller log entries for all users. You " -"can choose from the following values:" +"Use the start time of the last customer thread (which may consist of " +"multiple articles)." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:5 -msgid "60 (default)" +#: ../settings/ticket.rst:46 +msgid "" +"If this option is chosen, Zammad will update the last updated value just " +"once if a customer replies. After that, Zammad will wait for an agent to " +"react." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:6 -msgid "120" +#: ../settings/ticket.rst:50 +msgid "" +"This comes in handy if you want to work tickets in the order of their first " +"update. This will not change ticket orders if customers decide to \"bump\" " +"the ticket affected." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:7 -msgid "180" +#: ../settings/ticket.rst:57 +msgid "Use the time of the very last customer article." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:8 -msgid "240" +#: ../settings/ticket.rst:55 +msgid "" +"When setting this option, Zammad will always update the last updated value. " +"This means that if ordering by ``Last Update``, ticket orders will change if " +"customers \"bump\" the ticket." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:9 -msgid "300" +#: ../settings/ticket.rst:64 +msgid "Last contact value used on :doc:`/manage/overviews`" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:11 -msgid "**🥵 Potential performance issue**" +#: ../settings/ticket.rst:65 +msgid "Last contact value used on :doc:`/manage/trigger`" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:13 +#: ../settings/ticket.rst:88 msgid "" -"Setting this setting higher than 60 may cause serious performance issues on " -"very busy instances. Keep in mind that this setting causes Zammad to poll " -"and send up to 300 records to *all active agent sessions* in very short time " -"periods." +"Ticket Organization Reassignment (default: ``Update the most recent tickets." +"``)" msgstr "" -#: ../system/integrations/cti/generic.rst:73 -msgid "Caller Log Filter" +#: ../settings/ticket.rst:68 +msgid "" +"This setting changes the way Zammad updates the organization field of the " +"tickets whenever the primary organization of a user is changed." msgstr "" -#: ../system/integrations/cti/generic.rst:55 -msgid "" -"This function allows you to provide call information based on e.g. queues " -"only to agents that really need the information." +#: ../settings/ticket.rst:74 +msgid "Update the most recent tickets." msgstr "" -#: ../system/integrations/cti/generic.rst:58 +#: ../settings/ticket.rst:72 msgid "" -"Why? If you have a team for several countries or departments, you don't want " -"to bug your agents from other departments. Leaving these options empty will " -"fallback to showing everything to everyone." +"If this option is chosen, Zammad will update the 100 most recent tickets " +"where the user is the ticket customer. The ticket organization field will be " +"automatically set to the new primary organization of the user." msgstr "" -#: ../system/integrations/cti/generic.rst:64 -msgid "Destination caller ID or Queue" +#: ../settings/ticket.rst:88 +msgid "Do not update any tickets." msgstr "" -#: ../system/integrations/cti/generic.rst:63 +#: ../settings/ticket.rst:77 msgid "" -"This depends on your PBX and usually is either a queue ID, phone number or " -"extension." +"When choosing this option, Zammad will not update any tickets when the " +"user's primary organization is changed." msgstr "" -#: ../system/integrations/cti/generic.rst:69 -msgid "Agents" +#: ../settings/ticket.rst:80 +msgid "**Use with care!**" msgstr "" -#: ../system/integrations/cti/generic.rst:67 +#: ../settings/ticket.rst:82 msgid "" -"Select the agents that are responsible for the group. These agents will then " -"see caller log entries and call notifications fitting to said queue." +"Using this option may lead to inconsistencies in the system as the ticket " +"organization may become decoupled from the ticket customer." msgstr "" -#: ../system/integrations/cti/generic.rst:0 +#: ../settings/ticket.rst:85 msgid "" -"Screenshot showing the caller log filter table with pre filled sample data" +"However, you may use this option if you wish to maintain :ref:`the shared " +"access ` to the ticket for all organization " +"members of the original organization of the customer." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:6 -msgid "" -"With recent logs Zammad allows you to view the latest calls for the CTI " -"functionality. This usually comes in handy, when you're looking for errors." +#: ../settings/ticket.rst:110 +msgid "Ticket Number Format (default: ``Increment (SystemID.Counter)``)" msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:0 +#: ../settings/ticket.rst:94 msgid "" -"Screenshot showing several incoming requests within Recent logs section." +"This setting defines the way Zammad's ticket number will look. Changing this " +"setting in production will cause follow up detection to fail." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:16 -msgid "I'm just here to clear floats up." +#: ../settings/ticket.rst:102 +msgid "Increment (SystemID.Counter)" msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:20 +#: ../settings/ticket.rst:98 msgid "" -"By clicking on the entry of interest, Zammad will provide more details on " -"the call in question. You'll see the payload it received and also the " -"response that was sent." +"The increment value contains the SystemID (automatically generated during " +"installation) and a increment which counts up with every new Ticket. The " +"increment will automatically get another digit if needed." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:0 -msgid "" -"Screenshot showing detailed information of a specific log entry of recent " -"logs" +#: ../settings/ticket.rst:102 +msgid "Examples: ``1010138``, ``1010139``" msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:31 -msgid "x" +#: ../settings/ticket.rst:110 +msgid "Date (Year.Month.Day.SystemID.Counter)" msgstr "" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 -#: ../system/integrations/cti/includes/troubleshooting.include.rst:9 -msgid "My Phone page stays blank, signalling does work..." +#: ../settings/ticket.rst:105 +msgid "" +"This version of the ticket number is fairly long. However, because it " +"contains the date of ticket creation, it also allows you to see when the " +"ticket has been created. You may feel familiar with this number format if " +"you've worked with OTRS already." msgstr "" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:5 -msgid "" -"If you've made sure that signalling works (check Recent logs) and your " -"Caller Log still stays empty, please ensure that you only configured one CTI " -"integration version. Specifically defining more than one agent mapping on " -"the different integration variants will be the issue." +#: ../settings/ticket.rst:110 +msgid "Examples: ``201206231010138``, ``201206231010139``" msgstr "" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 -msgid "Clear the not needed agent mapping and reload your browser page." +#: ../settings/ticket.rst:137 +msgid "OPTIONS" msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:1 +#: ../settings/ticket.rst:113 msgid "" -"By mapping your agents extension to their existing Zammad users, Zammad can " -"provide a new ticket dialog or open the user profile for the agent that " -"picks up the call." +"The below options allow you to further customize your ticket number. The " +"availability of options differ depending of the chosen ticket number format " +"above." msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:5 -msgid "" -"This speeds up ticket aiding, no matter if it's for existing tickets or new " -"ones!" +#: ../settings/ticket.rst:122 +msgid "Checksum (default: ``no``)" msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:8 +#: ../settings/ticket.rst:118 msgid "" -"To see it work from the agent's perspective, have a look on :user-docs:`user " -"documentation `." +"If set to yes, we'll built a checksum to further \"unique\" the ticket " +"number of your system. If you're dealing with many other ticket systems this " +"might help to prevent false positive follow up detection on tickets." msgstr "" -#: ../system/integrations/cti/placetel.rst:2 -msgid "Placetel CTI" +#: ../settings/ticket.rst:122 +msgid "This will also add another digit to the ticket number." msgstr "" -#: ../system/integrations/cti/placetel.rst:16 -msgid "You need an administrative Placetel account for your organization." +#: ../settings/ticket.rst:137 +msgid "Min. size of Number (default: ``5``)" msgstr "" -#: ../system/integrations/cti/placetel.rst:17 -#: ../system/integrations/cti/sipgate.rst:20 +#: ../settings/ticket.rst:125 msgid "" -"Your Zammad instance must be allowed to communicate to external services." +"This setting defines the minimum length of your ticket number. If your " +"counter is not yet high enough, Zammad will fill the number with zeros to " +"ensure the wanted length." msgstr "" -#: ../system/integrations/cti/placetel.rst:18 -msgid "Placetel must be able to reach your Zammad instance." -msgstr "" - -#: ../system/integrations/cti/placetel.rst:22 -msgid ":doc:`provider-configurations/placetel`" -msgstr "" - -#: ../system/integrations/cti/placetel.rst:21 +#: ../settings/ticket.rst:129 msgid "" -"Learn how to configure Placetel to enable Zammad and Placetel to communicate " -"with each other." +"Please note that the minimum length is ``3`` (SystemID + at least one digit " +"if below 10). Also, if the length is no longer long enough, the number will " +"automatically get one digit longer. Ticket-Numbers **do not overflow**, thus " +"it's save to keep it at 5 or set it lower if wanted." msgstr "" -#: ../system/integrations/cti/placetel.rst:32 +#: ../settings/ticket.rst:135 msgid "" -"The here listed endpoint settings are relevant for the :doc:`integration " -"configuration with Placetel `." +"This option is only available if ticket number format is set to " +"``Increment``!" msgstr "" -#: ../system/integrations/cti/placetel.rst:37 -#: ../system/integrations/i-doit.rst:53 -msgid "Endpoint" +#: ../settings/ticket.rst:142 +msgid "Auto-Assignment" msgstr "" -#: ../system/integrations/cti/placetel.rst:36 +#: ../settings/ticket.rst:144 msgid "" -"This endpoint will be required for the Zammad integration within the " -"Placetel web interface." -msgstr "" - -#: ../system/integrations/cti/placetel.rst:41 -msgid "API Token" +"In a larger Zammad environment, it happens that several agents open the same " +"ticket at the same time. Although collision detection is then effective, the " +"efficiency of processing can be increased by means of the automatic " +"assignment of tickets when a ticket is opened." msgstr "" -#: ../system/integrations/cti/placetel.rst:40 +#: ../settings/ticket.rst:149 msgid "" -"You'll receive this token within the ``Web API`` menu. Make sure to copy " -"this value, it's only shown once!" -msgstr "" - -#: ../system/integrations/cti/placetel.rst:71 -#: ../system/integrations/cti/sipgate.rst:77 -msgid "Phone Extension to Agent Mapping" +"The automatic assignment of tickets can be activated and configured in the " +"admin area under Settings > Ticket > Auto Assignment." msgstr "" -#: ../system/integrations/cti/placetel.rst:0 -msgid "Screenshot showing sample user mappings in between Placetel and Zammad" +#: ../settings/ticket.rst:152 +msgid "" +"The auto assignment only works if the ticket has no owner yet. By default, " +"the agent can always reset the ticket owner to ``-`` if needed." msgstr "" -#: ../system/integrations/cti/placetel.rst:64 +#: ../settings/ticket.rst:155 msgid "" -"You can find your agents Placetel username combination required within ⚙️ PBX " -"→ VoIP destinations. Within the \"Advanced settings\" section you're looking " -"for \"SIP user name\" and \"SIP server\"." +"If you want to use this function for only specific tickets, you can " +"configure the conditions accordingly to meet your requirement. By default " +"the condition affects all tickets with the state ``open``." msgstr "" -#: ../system/integrations/cti/placetel.rst:68 -msgid "Combine these two like so: ``@``." +#: ../settings/ticket.rst:161 +msgid "" +"If you need to exclude users (e.g. a group leader), you can search and " +"select the desired agents in the ``Exception Users`` list. The search " +"function in this area is only effective, if you have too many agents to " +"display at once to help you with the configuration." msgstr "" -#: ../system/integrations/cti/placetel.rst:0 -msgid "Sample VoIP credentials for a Placetel user" +#: ../settings/ticket.rst:167 +msgid "Notifications" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:2 -msgid "Setup Placetel connection for Zammad" +#: ../settings/ticket.rst:191 +msgid "Default Notifications" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:6 +#: ../settings/ticket.rst:170 msgid "" -"This configuration step requires a *full* administrative Placetel account. " -"You may receive forbidden error messages with Placetel in case your " -"permissions are not high enough." +"This setting allows you to configure the default ticket notifications that " +"will be applied to all new agent users (incl. users who were just assigned " +"agent role). Simply change the notification matrix to desired state and " +"press **Save**." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:10 +#: ../settings/ticket.rst:175 msgid "" -"The following actions can be configured via the `Placetel web interface " -"`_." -msgstr "" - -#: ../system/integrations/cti/provider-configurations/placetel.rst:29 -msgid "Step 1: Activate Zammad integration" +"In case an agent already exists, their ticket notification preferences will " +"be preserved. Optionally, you can also **Apply current defaults to all " +"agents**." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:14 +#: ../settings/ticket.rst:181 msgid "" -"Within Integrations, scroll down to Partner integrations and select Zammad." +"**Potential time-consuming action:** Applying default ticket notifications " +"to all agent users may take some time to complete, be patient! The exact " +"time will depend on the size of your system and the number of agents." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:17 +#: ../settings/ticket.rst:185 msgid "" -"You can alternatively filter by \"Ticket Systems\" to reduce the number of " -"entries on the page. You'll still want to look for Partner integrations. 🤓" +"**Active agents only!** When current default ticket notifications are " +"applied, only active agent users are considered. In case an agent is re-" +"activated *after* this action, they will still have the old notification " +"configuration." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:21 +#: ../settings/ticket.rst:190 msgid "" -"Within the Zammad integration now press \"Activate\". A new tab ``API`` " -"becomes available - open this tab." +"In case you want to go back to the initial state of ticket notifications, " +"you can click on **Reset to default** button." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:24 -msgid "" -"Now tick \"Enable Call Control / Notify API\" and paste the Placetel " -"endpoint from your Zammad instance into the field \"URL of your API " -"endpoint\". Save to apply the settings" +#: ../settings/ticket.rst:196 +msgid "Duplicate Detection" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 -msgid "Screencast showing how to activate the Zammad integration" +#: ../settings/ticket.rst:238 +msgid "Detect Duplicate Ticket Creation" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:51 -msgid "Step 2: Generate API Token for Placetel" +#: ../settings/ticket.rst:199 +msgid "" +"This setting turns on the duplicate ticket detection mechanism during ticket " +"creation. If similar tickets are found in the system, a suitable warning " +"will be shown to the user trying to create a ticket." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:32 -msgid "" -"Go back to the integrations page and scroll down to \"Web API\". Generate a " -"new API token by using the \"Create a new API token\" button." +#: ../settings/ticket.rst:206 +msgid "A Sample Duplicate Ticket Warning" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:37 +#: ../settings/ticket.rst:208 msgid "" -"If you already generated a token either use your existing token or reset it " -"by using above mentioned button. Placetel will ask you to conform this reset." +"You can choose which ticket attributes will be matched by selecting them in " +"**Attributes to compare** field. Only if the ticket attribute value provided " +"by the user in the ticket create form is *equal* with the attribute in an " +"existing ticket, the warning will be shown." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:41 -msgid "" -"Please keep in mind that existing API scripts may no longer work due to " -"token resets!" +#: ../settings/ticket.rst:213 +msgid "**Warning title** and **Warning message** are configurable as well." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:44 +#: ../settings/ticket.rst:215 msgid "" -"Copy the provided API token and insert it into the \"API Token\" field " -"within Zammad's Placetel integration." +"You can limit the detection only to certain user roles. By default, only " +"agents will see the warning." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:47 +#: ../settings/ticket.rst:218 msgid "" -"Apply your changes by using the \"Save\" button on the bottom of the " -"Placetel integration page and activate the Placetel integration." +"If you don't want to show the matched tickets as part of the warning, you " +"can set **Show matching ticket(s) in the warning** setting to *no*." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +#: ../settings/ticket.rst:221 msgid "" -"Screencast showing how to retrieve an API token from Placetel for Zammad" +"By default, **Permission level for looking up ticket** is set to *User*, " +"which means user permissions will be honored during sarch. The user will " +"see the warning only if tickets they have access to are matched. " +"Alternatively, you can set this setting to *System*, in which case the " +"search will happen within *all* tickets in the system, regardless of user " +"permissions." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:73 -#: ../system/integrations/cti/provider-configurations/sipgate.rst:77 -msgid "Step 3: Restrict the numbers to notify on" +#: ../settings/ticket.rst:227 +msgid "**🦺 Safety first!**" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:54 +#: ../settings/ticket.rst:229 msgid "" -"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " -"the the Integrations page of the Placetel web interface, go to \"Notify " -"API\"." +"Even if the permission level is set to *System*, the user will not be shown " +"the tickets they don't have access to in the warning, even if they match." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:58 +#: ../settings/ticket.rst:233 msgid "" -"Lower on the page Placetel allows you to restrict the numbers to notify on. " -"You'll find this within the \"External routing API\" part." +"However, just the confirmation about the existence of the tickets in the " +"system may be considered an unwanted information disclosure. Use this option " +"carefully!" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +#: ../settings/ticket.rst:237 msgid "" -"Screenshot showing a sample selection of phone numbers to use for the " -"Placetels notify API" +"Finally, you can configure between matching within **All tickets** or **Open " +"tickets** only by setting **Match tickets in following states**. Depending " +"on the current ticket state, a ticket may or not be matched." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:66 -msgid "" -"This menu point also provides a API request log from Placetel view. Just " -"open \"Recent responses of your API endpoint\" to learn more." +#: ../system/core-workflows.rst:2 +msgid "Core Workflows" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:69 +#: ../system/core-workflows.rst:4 msgid "" -"If you want to see Zammad's perspective, use the \"Recent Logs\" part from " -"within the Placetel integration page." +"Core Workflows allow you to adjust object attributes in many ways. For " +"example:" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 -msgid "Screenshot showing sample log entries for Placetels API calls to Zammad" +#: ../system/core-workflows.rst:7 +msgid "show / hide fields" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:77 -msgid "Step 4 (optional): Further configurations for Placetel" +#: ../system/core-workflows.rst:8 +msgid "adjust mandatory setting" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:76 +#: ../system/core-workflows.rst:9 +msgid "manipulate available options" +msgstr "" + +#: ../system/core-workflows.rst:11 msgid "" -"If needed, you can now configure Zammad's Placetel integration in more " -"detail. You can learn more about your options here: :ref:`Placetel " -"integration settings `." +"With this, you can provide exactly the information your users really need!" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:2 -msgid "Setup Sipgate connection for Zammad" +#: ../system/core-workflows.rst:15 +msgid "" +"If the pre-defined :doc:`/system/objects` are not enough, please add them " +"beforehand." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +#: ../system/core-workflows.rst:17 msgid "" -"Sipgate has no english web interface which is why this documentation page is " -"mixing up languages badly." +"If you experience slow or unreliable field updates, please see :ref:`Core " +"Workflow Ajax Modus `" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +#: ../system/core-workflows.rst:22 msgid "" -"Please also note that the availability of API addons highly depends on your " -"package trier. Usage of sipgate.io packages *is not free*, please check " -"their `pricing page `_ before!" +"This is a very enhanced functionality and can cause unexpected UI behavior. " +"Please ensure to test your use cases after configuration to reduce surprises." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:35 -msgid "Step 1: Book sipgate.io package" +#: ../system/core-workflows.rst:None +msgid "Dialogue for adding a new workflow" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:13 -msgid "Skip to step 2 if you already have the package booked!" +#: ../system/core-workflows/condition-operators.rst:2 +msgid "Core Workflow Condition Operators" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:15 +#: ../system/core-workflows/condition-operators.rst:4 msgid "" -"Login to an administrative Sipgate account and navigate to " -"``Accountverwaltung``. You'll see several different options depending on " -"your booked packages. Select ``Verträge & Produkte`` to continue." +"You might know that there is a separate section for explaining :doc:" +"`condition operators `. Head over there to " +"see a detailed explanation of many conditions and operators." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:19 +#: ../system/core-workflows/condition-operators.rst:8 msgid "" -"Scroll down to the section ``Zusätzliche Produkte buchen`` and look for " -"``sipgate.io`` - select this product by using the ``Produkte anzeigen``-" -"Button." -msgstr "" - -#: ../system/integrations/cti/provider-configurations/sipgate.rst:23 -msgid "" -"On the next page select either one of the ``sipgate.io`` packages or ``Push-" -"API Package Free``. Follow the dialogue by booking the addon. You'll be " -"returned to your contract overview and now should see the selected addon in " -"your list." +"Due to differences to other places in Zammad which are also using conditions " +"(e.g. triggers), you can find a dedicated description of operators for core " +"workflows below." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:30 +#: ../system/core-workflows/condition-operators.rst:12 msgid "" -"The availability for ``sipgate.io`` packages and their levels highly depends " -"on the overall account type and product you've booked with Sipgate." +"Be aware that the availability of the operators depends on the selected " +"attribute and its field type. Some of the operators may only be available " +"for system attributes (e.g. for \"tags\", \"active\")." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screencast showing the process on how to book the required sipgate.io addon" +#: ../system/core-workflows/condition-operators.rst:20 +msgid "Operator" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:52 -msgid "Step 2: Configure webhook for Zammad" +#: ../system/core-workflows/condition-operators.rst:22 +msgid "after (absolute)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:38 -msgid "" -"Within your ``Accountverwaltung`` navicate to your product ``sipgate.io``. " -"In the newly opened tab, switch from \"Clients\" to \"Webhooks\" and paste " -"the endpoint URLs from your Zammad instance like so:" +#: ../system/core-workflows/condition-operators.rst:23 +msgid "Matches if a date/time is after a specific point in time." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:42 -msgid "Inbound endpoint to \"Incoming\"" +#: ../system/core-workflows/condition-operators.rst:24 +msgid "after (relative)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:43 -msgid "Outbound endpoint to \"Outgoing\"" +#: ../system/core-workflows/condition-operators.rst:25 +msgid "Matches if a time span after a specified event has passed." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:47 -msgid "" -"Ensure to select at least one call group or phoneline within \"Sources\". " -"Other wise Sipgate will not indicate any incoming or outgoing calls to " -"Zammad." +#: ../system/core-workflows/condition-operators.rst:26 +msgid "before (absolute)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screencast showing how to add Zammad's endpoint URLs to sipgate.ios webhook " -"configuration" +#: ../system/core-workflows/condition-operators.rst:27 +msgid "Matches if a date/time is before a specific point in time." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:55 -msgid "" -"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " -"the Webhooks → URLs section of Sipgate you can select which *sources* " -"Sipgate should notify Zammad about in- and outgoing calls." +#: ../system/core-workflows/condition-operators.rst:28 +msgid "before (relative)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:59 -msgid "" -"Use either specific phone lines or use the option \"Use for all phonelines " -"and groups\" to notify Zammad about all existing lines of your Sipgate " -"account." +#: ../system/core-workflows/condition-operators.rst:29 +msgid "Matches if a time span after a specified event has not passed." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screenshot showing a sample selection of phone numbers to use for the " -"Sipgates webhooks API" +#: ../system/core-workflows/condition-operators.rst:30 +msgid "contains" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:68 -msgid "This section also allows you to enable a Debug log." +#: ../system/core-workflows/condition-operators.rst:31 +msgid "Matches if a specified value is present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "Screenshot showing an enabled Debug log option" +#: ../system/core-workflows/condition-operators.rst:33 +msgid "Matches if all of the specified values are present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:73 -msgid "" -"After enabling you can use the Debug log section to see all sent webhook " -"calls to Zammad. You'll also can see the response." +#: ../system/core-workflows/condition-operators.rst:35 +msgid "Matches if none of the specified values are present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screenshot showing sample log entries for Sipgates webhook calls to Zammad" +#: ../system/core-workflows/condition-operators.rst:36 +msgid "contains not" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:81 -msgid "Step 4 (optional): Further configurations for Sipgate" +#: ../system/core-workflows/condition-operators.rst:37 +msgid "Matches if a specified value is not present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:80 -msgid "" -"If needed, you can now configure Zammad's Sipgate integration in more " -"detail. You can learn more about your options here: :ref:`Sipgate " -"integration settings `." +#: ../system/core-workflows/condition-operators.rst:39 +msgid "Matches if one specified value is present." msgstr "" -#: ../system/integrations/cti/sipgate.rst:2 -msgid "Sipgate (sipgate.io)" +#: ../system/core-workflows/condition-operators.rst:41 +msgid "Matches if one specified value is not present." msgstr "" -#: ../system/integrations/cti/sipgate.rst:16 -msgid "You need an administrative Sipgate account for your organization." +#: ../system/core-workflows/condition-operators.rst:42 +msgid "does not match regex" msgstr "" -#: ../system/integrations/cti/sipgate.rst:17 -msgid "" -"Zammad requires a ``sipgate.io`` addon from the feature store (please note " -"that API calls are not free with Sipgate. Rates may apply and differ from " -"account to account)." +#: ../system/core-workflows/condition-operators.rst:43 +msgid "Matches if content doesn't fit to regex rule." msgstr "" -#: ../system/integrations/cti/sipgate.rst:21 -msgid "Sipgate must be able to reach your Zammad instance." +#: ../system/core-workflows/condition-operators.rst:44 +msgid "ends with" msgstr "" -#: ../system/integrations/cti/sipgate.rst:25 -msgid ":doc:`provider-configurations/sipgate`" +#: ../system/core-workflows/condition-operators.rst:45 +msgid "Matches if content ends with specified value." msgstr "" -#: ../system/integrations/cti/sipgate.rst:24 -msgid "" -"Learn how to configure Sipgate to enable Zammad and Sipgate to communicate " -"with each other." +#: ../system/core-workflows/condition-operators.rst:46 +msgid "ends with one of" msgstr "" -#: ../system/integrations/cti/sipgate.rst:33 -msgid "" -"Below endpoint settings affect the :doc:`sipgate.io configuration `." +#: ../system/core-workflows/condition-operators.rst:47 +msgid "Matches if content ends with one of the specified values." msgstr "" -#: ../system/integrations/cti/sipgate.rst:37 -msgid "This endpoint is required for incoming call hooks." +#: ../system/core-workflows/condition-operators.rst:48 +msgid "from (relative)" msgstr "" -#: ../system/integrations/cti/sipgate.rst:40 -msgid "This endpoint is required for outgoing call hooks." +#: ../system/core-workflows/condition-operators.rst:49 +msgid "Matches if date/time is after a period of time after an event." msgstr "" -#: ../system/integrations/cti/sipgate.rst:0 -msgid "Screenshot showing sample user mappings in between Sipgate and Zammad" +#: ../system/core-workflows/condition-operators.rst:51 +msgid "Matches if content is equal to a specified value." msgstr "" -#: ../system/integrations/cti/sipgate.rst:69 -msgid "" -"You can find your agent's Sipgate username within ``Accountverwaltung → " -"Benutzer``. You're looking for the SIP-ID." +#: ../system/core-workflows/condition-operators.rst:52 +msgid "is any of" msgstr "" -#: ../system/integrations/cti/sipgate.rst:0 -msgid "Sample VoIP credentials for a Sipgate user" +#: ../system/core-workflows/condition-operators.rst:53 +msgid "Matches if content is equal to any of specified values." msgstr "" -#: ../system/integrations/cti/sipgate.rst:77 -msgid "Users with several devices also have several SIP-IDs." +#: ../system/core-workflows/condition-operators.rst:54 +msgid "is modified" msgstr "" -#: ../system/integrations/elasticsearch.rst:2 -msgid "Elasticsearch (SaaS)" +#: ../system/core-workflows/condition-operators.rst:55 +msgid "Matches if content is modified." msgstr "" -#: ../system/integrations/elasticsearch.rst:4 -msgid "" -"The Elasticsearch integration allows you to create a read-only user to use " -"with your favorite reporting tool (e.g. like Grafana)." +#: ../system/core-workflows/condition-operators.rst:57 +#: ../system/core-workflows/condition-operators.rst:61 +msgid "True from the moment of changing content until form submit." msgstr "" -#: ../system/integrations/elasticsearch.rst:7 -msgid "" -"If you want to take full advantage of the Zammad reporting, have a look at " -"our :docs:`Grafana ` " -"setup page as well." +#: ../system/core-workflows/condition-operators.rst:58 +msgid "is modified to" msgstr "" -#: ../system/integrations/elasticsearch.rst:11 -#: ../system/subscription/index.rst:7 -msgid "**🚧 Hosted environment specific 🚧**" +#: ../system/core-workflows/condition-operators.rst:59 +msgid "Matches if content is modified to a specific value." msgstr "" -#: ../system/integrations/elasticsearch.rst:13 -msgid "" -"This integration is only available for Hosted setups. In order to use " -"Elasticsearch you'll need the **Plus** subscription." +#: ../system/core-workflows/condition-operators.rst:62 +msgid "is none of" msgstr "" -#: ../system/integrations/elasticsearch.rst:16 -msgid "" -"Self hosted users have all the control over their self hosted Elasticsearch " -"instances." +#: ../system/core-workflows/condition-operators.rst:63 +msgid "Matches if content is none of any specified values." msgstr "" -#: ../system/integrations/elasticsearch.rst:None -msgid "Elasticsearch integration page on SaaS environments" +#: ../system/core-workflows/condition-operators.rst:65 +msgid "Matches if content is not equal to a specified value." msgstr "" -#: ../system/integrations/elasticsearch.rst:27 -msgid "" -"Please note the following limitations of Elasticsearch access on hosted " -"environments:" +#: ../system/core-workflows/condition-operators.rst:67 +msgid "Matches if content is present." msgstr "" -#: ../system/integrations/elasticsearch.rst:30 -msgid "access to the Elasticsearch index is read-only access" +#: ../system/core-workflows/condition-operators.rst:68 +msgid "just changed" msgstr "" -#: ../system/integrations/elasticsearch.rst:31 -msgid "currently you're limited to user only" +#: ../system/core-workflows/condition-operators.rst:69 +msgid "Matches if content has changed." msgstr "" -#: ../system/integrations/elasticsearch.rst:32 +#: ../system/core-workflows/condition-operators.rst:71 +#: ../system/core-workflows/condition-operators.rst:75 msgid "" -"Reporting tools that require to write into the indexes (like Kibana) are not " -"supported" +"Only true for the moment of changing content until next form field action/" +"click." msgstr "" -#: ../system/integrations/elasticsearch.rst:34 -msgid "IP access restriction is currently not yet supported" +#: ../system/core-workflows/condition-operators.rst:72 +msgid "just changed to" msgstr "" -#: ../system/integrations/elasticsearch.rst:37 -msgid "Activating Elasticsearch Access" +#: ../system/core-workflows/condition-operators.rst:73 +msgid "Matches if content has changed to a specified value." msgstr "" -#: ../system/integrations/elasticsearch.rst:39 -msgid "" -"By default external access to your Elasticsearch index is not active. You " -"can enable the integration at any time if needed." +#: ../system/core-workflows/condition-operators.rst:76 +msgid "matches regex" msgstr "" -#: ../system/integrations/elasticsearch.rst:42 -msgid "" -"Please ensure to note down the password provided - you won't have access to " -"it afterwards." +#: ../system/core-workflows/condition-operators.rst:77 +msgid "Matches if value fits to regex rule." msgstr "" -#: ../system/integrations/elasticsearch.rst:None -msgid "Screencast showing activation of Elasticsearch integration" +#: ../system/core-workflows/condition-operators.rst:79 +msgid "Matches if no content is present." msgstr "" -#: ../system/integrations/elasticsearch.rst:51 -msgid "Connection Settings" +#: ../system/core-workflows/condition-operators.rst:80 +msgid "starts with" msgstr "" -#: ../system/integrations/elasticsearch.rst:53 -msgid "" -"This section holds the most important general information for accessing your " -"Elasticsearch indexes - such as:" -msgstr "" - -#: ../system/integrations/elasticsearch.rst:57 -msgid "A unique subdomain that does not tell your real instance URL." +#: ../system/core-workflows/condition-operators.rst:81 +msgid "Matches if content starts with specified value." msgstr "" -#: ../system/integrations/elasticsearch.rst:61 -msgid "Software" +#: ../system/core-workflows/condition-operators.rst:82 +msgid "starts with one of" msgstr "" -#: ../system/integrations/elasticsearch.rst:60 -msgid "" -"The major version of the search index being used. This is required by some " -"Reporting tools like Grafana." +#: ../system/core-workflows/condition-operators.rst:83 +msgid "Matches if content starts with one of the specified values." msgstr "" -#: ../system/integrations/elasticsearch.rst:64 -msgid "Authentication" +#: ../system/core-workflows/condition-operators.rst:84 +msgid "till (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:64 -msgid "The authentication type being supported. ``Basic Authentication``" +#: ../system/core-workflows/condition-operators.rst:85 +msgid "Matches if date/time is before a period of time before an event." msgstr "" -#: ../system/integrations/elasticsearch.rst:67 -msgid "Available Indexes" +#: ../system/core-workflows/condition-operators.rst:86 +msgid "today" msgstr "" -#: ../system/integrations/elasticsearch.rst:69 -msgid "" -"Within this section we're displaying the -in our opinion- most important " -"indexes for a Zammad instance." +#: ../system/core-workflows/condition-operators.rst:87 +msgid "Matches if date/time is today." msgstr "" -#: ../system/integrations/elasticsearch.rst:72 -msgid "" -"If you require all indexes or our listing is not good enough for you, point " -"your browser to the URL we're providing and append ``/_aliases?" -"pretty=true``. The result should look like this: ``https://.zammad.com/" -"_aliases?pretty=true``." +#: ../system/core-workflows/condition-operators.rst:88 +msgid "within last (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:77 +#: ../system/core-workflows/condition-operators.rst:89 msgid "" -"Your browser will automatically ask for your credentials - you'll then see " -"something like this:" +"Matches if date/time content is within specified period of time before now." msgstr "" -#: ../system/integrations/elasticsearch.rst:125 -msgid "Credentials" +#: ../system/core-workflows/condition-operators.rst:91 +msgid "within next (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:127 +#: ../system/core-workflows/condition-operators.rst:92 msgid "" -"Within this section Zammad displays your available users. The password is " -"provided once (upon activation) and cannot be retrieved after that." +"Matches if date/time content is within specified period of time after now." msgstr "" -#: ../system/integrations/elasticsearch.rst:131 -msgid "" -"If you need to change or reset your Elasticsearch user password, use the " -"\"Reset password\" button in the credentials table. Doing so creates a brand " -"new password for the account in question. This change is immediate, keep in " -"mind that this may affect third party tools connected to your instance." +#: ../system/core-workflows/how-do-they-work.rst:2 +msgid "How do they work?" msgstr "" -#: ../system/integrations/exchange.rst:2 -msgid "Exchange" +#: ../system/core-workflows/how-do-they-work.rst:4 +msgid "" +"Core Workflows are executed according to their priority. If two workflows " +"have the same priority, they are executed in alphabetical order based on " +"their **name**." msgstr "" -#: ../system/integrations/exchange.rst:4 +#: ../system/core-workflows/how-do-they-work.rst:8 msgid "" -"With Zammad's Exchange integration, you can easily use existing address " -"books without having to update more than one source." +"Because of the way Core Workflows work, all changes to attributes are " +"checked with the application server - please see :doc:`limitations` for " +"possible issues." msgstr "" -#: ../system/integrations/exchange.rst:7 +#: ../system/core-workflows/how-do-they-work.rst:12 msgid "" -"However, you should refrain from syncing all addresses, as the results may " -"not be what you expect (Exchange collects huge amounts of addresses). A " -"central address book of your company to sync makes more sense, as you can " -"ensure that Zammad gets only the data you need and want. Apart from this, it " -"is even not possible to sync the Global Address List (GAL) of your Exchange " -"system with Zammad." +"Below we're talking about settings that are important and not self-" +"explanatory." msgstr "" -#: ../system/integrations/exchange.rst:16 +#: ../system/core-workflows/how-do-they-work.rst:17 msgid "" -"**Exchange and LDAP:** The exchange sync can be overruled by Zammad's LDAP " -"integration. If you have the same users in both sources, the LDAP version " -"will always be Zammad's pick." +"Choose the object context you want to run the workflow in. This will decide " +"on your available attributes and actions." msgstr "" -#: ../system/integrations/exchange.rst:19 -msgid "" -"**One way sync:** the Exchange sync is one way. Exchange => Zammad. Changes " -"to your users inside of Zammad might be overwritten by the Exchange sync." +#: ../system/core-workflows/how-do-they-work.rst:20 +msgid "Ticket objects also have access to the ticket customer." msgstr "" -#: ../system/integrations/exchange.rst:24 +#: ../system/core-workflows/how-do-they-work.rst:25 msgid "" -"To configure Exchange integration, simply go to the System > Integrations > " -"Exchange in the admin panel. Press \"change\" and follow the wizard for " -"adding the needed Exchange information to Zammad. On the last two steps " -"Zammad will ask you for the address book(s) and your desired attribute " -"mapping. By default, Zammad only maps email address, first- and lastname. " -"Technically, you can map any Exchange object to a Zammad user object (this " -"also works for custom objects!)." +"Choose in which situation the workflow is applied. Contexts can be combined " +"to avoid duplicate workflows." msgstr "" -#: ../system/integrations/exchange.rst:35 -msgid "" -"If the SSL verification fails while connecting to Exchange, Zammad will ask " -"you to turn it off temporarily." +#: ../system/core-workflows/how-do-they-work.rst:30 +msgid "Creation mask" msgstr "" -#: ../system/integrations/exchange.rst:38 +#: ../system/core-workflows/how-do-they-work.rst:29 msgid "" -"Please be aware that **turning off SSL verification is a security risk**. It " -"should only be used temporarily or for testing purposes. If turned off, " -"there is no verification of the certificate, which means that every " -"presented certificate will be accepted." +"If selected, your conditions and actions will affect all applicable creation " +"masks." msgstr "" -#: ../system/integrations/exchange.rst:43 -msgid "" -"After pressing Continue, Zammad will check if the configuration is okay. You " -"can then enable Exchange and start your first sync. The sync will then run " -"hourly - if you need to change mappings or the address book(s), you can " -"change the configuration at any time." +#: ../system/core-workflows/how-do-they-work.rst:34 +msgid "Edit mask" msgstr "" -#: ../system/integrations/exchange.rst:50 +#: ../system/core-workflows/how-do-they-work.rst:33 msgid "" -"After the sync has finished, you can find the new Exchange contacts under " -"\"Users\". Zammad integrates them just as normal users." +"If selected, your conditions and actions will affect all applicable edit " +"masks." msgstr "" -#: ../system/integrations/exchange.rst:55 +#: ../system/core-workflows/how-do-they-work.rst:39 msgid "" -"In some cases you might see unique IDs as \"Login\" instead of the email " -"address. This is normal and doesn't affect the login or email mapping for " -"that entry." +"Zammad differentiates between selected and saved conditions. These can be " +"combined wherever needed." msgstr "" -#: ../system/integrations/github.rst:4 -msgid "" -"Use GitHub integration to track GitHub issues directly within Zammad " -"tickets. Add issue hyperlinks and get a live summary of metadata like status " -"(open/closed), assignee, labels, and more." +#: ../system/core-workflows/how-do-they-work.rst:42 +msgid "**⚠️ Restrict workflows to specific roles if needed!**" msgstr "" -#: ../system/integrations/github.rst:8 -msgid "Please note that our GitHub integration does not support pull requests." +#: ../system/core-workflows/how-do-they-work.rst:44 +msgid "" +"By default and unless configured in conditions, workflow rules are executed " +"for **all roles**. This also affects your customers!" msgstr "" -#: ../system/integrations/github.rst:None -msgid "Integration page for GitHub" +#: ../system/core-workflows/how-do-they-work.rst:50 +msgid "Selected Conditions" msgstr "" -#: ../system/integrations/github.rst:18 +#: ../system/core-workflows/how-do-they-work.rst:48 msgid "" -"In your GitHub settings, create a new API token under **Developer settings > " -"Personal access tokens > Generate new token**. Leave the **Scopes** section " -"empty." +"These conditions are based on form values and match if an appropriate " +"selection is made (e.g. choosing another group in the ticket without " +"saving). This applies for drafts (active selection) and currently saved " +"values." msgstr "" -#: ../system/integrations/github.rst:0 ../system/integrations/gitlab.rst:0 -msgid "Screencast showing how to create a new API token" +#: ../system/core-workflows/how-do-they-work.rst:64 +msgid "Saved Conditions" msgstr "" -#: ../system/integrations/github.rst:27 -msgid "Create a new API key with no scopes/privileges." +#: ../system/core-workflows/how-do-they-work.rst:53 +msgid "" +"These conditions only match if the selected values are stored in the " +"database. It ignores the current value or selection of the field, as long as " +"the changes are not saved (e.g. performing field operations for an existing " +"ticket, which is viewed/opened by an agent)." msgstr "" -#: ../system/integrations/github.rst:29 -msgid "🔒 **Will this work for private repos?**" +#: ../system/core-workflows/how-do-they-work.rst:60 +msgid "" +"Keep in mind that the value has to be available in the situation where you " +"need it. Otherwise the condition won't match." msgstr "" -#: ../system/integrations/github.rst:31 +#: ../system/core-workflows/how-do-they-work.rst:63 msgid "" -"No. To link private repo issues, **use the** ``repo`` **scope instead**. " -"Bear in mind that the resulting token will have `lots of permissions that it " -"doesn't actually need `_, which presents a security risk if your token ever falls into " -"the wrong hands." +"Example: you can't perform any actions with *saved condition* on a ticket in " +"creation, because there are no saved values at that time." msgstr "" -#: ../system/integrations/github.rst:37 +#: ../system/core-workflows/how-do-they-work.rst:66 msgid "" -"Unfortunately, because of how GitHub's OAuth token scopes are set up, this " -"is the only way to link issues on private repos." +"You can find a description of the condition operators for core workflows :" +"doc:`here `." msgstr "" -#: ../system/integrations/github.rst:40 -msgid "Enter your new API token in Zammad and enable GitHub integration." +#: ../system/core-workflows/how-do-they-work.rst:72 +msgid "" +"Which actions should we run on the relevant fields? The possible actions " +"depend on the object type. However, usually you can at least change the " +"visibility and whether the field is mandatory." msgstr "" -#: ../system/integrations/github.rst:0 -msgid "Screencast showing how to configure Zammad's GitHub integration" +#: ../system/core-workflows/how-do-they-work.rst:76 +msgid "Be aware that actions are not available for **related** context." msgstr "" -#: ../system/integrations/github.rst:47 +#: ../system/core-workflows/how-do-they-work.rst:78 msgid "" -"Use the default API endpoint (``https://api.github.com/graphql``) unless " -"you're using GitHub Enterprise Server." +"**Example:** Let's assume you are working in the ticket context. While you " +"can have customer *conditions*, you *can't adjust* objects with actions in " +"that scope. That's because this wouldn't have any impact on the ticket " +"dialog. Of course all ticket attributes (state, owner, ...) are available." msgstr "" -#: ../system/integrations/github.rst:50 +#: ../system/core-workflows/how-do-they-work.rst:84 msgid "" -"Once completed, a new GitHub issues tab will appear in the ticket pane. 🎉" +"Please also have a look at our :doc:`limitations` to be safe from surprises." msgstr "" -#: ../system/integrations/github.rst:59 ../system/integrations/gitlab.rst:52 -msgid "Token verification is taking a long time" +#: ../system/core-workflows/how-do-they-work.rst:88 +msgid "Available Operators" msgstr "" -#: ../system/integrations/github.rst:56 ../system/integrations/gitlab.rst:49 -msgid "" -"Slight delays are normal (<2 min.), especially for systems under heavy load." +#: ../system/core-workflows/how-do-they-work.rst:90 +msgid "The availability of operators depends on the object type and scope." msgstr "" -#: ../system/integrations/github.rst:58 +#: ../system/core-workflows/how-do-they-work.rst:94 msgid "" -"Self-hosted administrators, please check your network settings to ensure " -"that your Zammad server can reach ``api.github.com``." +"Please note that actions may or may not restrict API based access to " +"attributes. We're displaying the following icons for your overview to " +"understand these limits better:" msgstr "" -#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 -msgid "I reloaded the page and now the API token is gone" +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|api| This icon indicates the action affects the API." msgstr "" -#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 -msgid "" -"This may indicate that Zammad is still verifying your API token. Try " -"reloading the page again in a couple minutes." +#: ../system/core-workflows/how-do-they-work.rst:163 +msgid "api" msgstr "" -#: ../system/integrations/gitlab.rst:2 -msgid "GitLab" +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|ui| This icon indicates the action only affects the web interface." msgstr "" -#: ../system/integrations/gitlab.rst:4 -msgid "" -"Use GitLab integration to track GitLab issues directly within Zammad " -"tickets. Add issue hyperlinks and get a live summary of metadata like status " -"(open/closed), assignee, labels, and more." +#: ../system/core-workflows/how-do-they-work.rst:167 +msgid "ui" msgstr "" -#: ../system/integrations/gitlab.rst:8 -msgid "" -"Please note that our GitLab integration does not support merge requests." +#: ../system/core-workflows/how-do-they-work.rst:102 +msgid "show |ui|" msgstr "" -#: ../system/integrations/gitlab.rst:None -msgid "Integration page for GitLab" +#: ../system/core-workflows/how-do-they-work.rst:102 +msgid "Display the chosen field. Allows setting of values." msgstr "" -#: ../system/integrations/gitlab.rst:18 -msgid "" -"In your GitLab preferences, create a new API token under **Access Tokens**." +#: ../system/core-workflows/how-do-they-work.rst:109 +msgid "hide |ui|" msgstr "" -#: ../system/integrations/gitlab.rst:20 -msgid "Under **Select scopes**, choose ``read_api`` only." +#: ../system/core-workflows/how-do-they-work.rst:105 +msgid "" +"Hide the chosen field. However, it technically still allows setting the " +"field." msgstr "" -#: ../system/integrations/gitlab.rst:27 -msgid "🔒 **If you wish to link issues on any private repos...**" +#: ../system/core-workflows/how-do-they-work.rst:108 +msgid "" +"Please note that the field is **not** gone and still contains an existing " +"value (if set)! Consider *remove* instead, if you want this field to be gone." msgstr "" -#: ../system/integrations/gitlab.rst:29 -msgid "Your API token must belong to an account with access to those repos." +#: ../system/core-workflows/how-do-they-work.rst:112 +msgid "remove |ui|" msgstr "" -#: ../system/integrations/gitlab.rst:31 -msgid "Enter your new API token in Zammad and enable GitLab integration." +#: ../system/core-workflows/how-do-they-work.rst:112 +msgid "Entirely removes the field. The field value will not be evaluated." msgstr "" -#: ../system/integrations/gitlab.rst:0 -msgid "Screencast showing how to configure Zammad's GitLab integration" +#: ../system/core-workflows/how-do-they-work.rst:115 +msgid "set mandatory |ui| |api|" msgstr "" -#: ../system/integrations/gitlab.rst:40 -msgid "" -"Use the default API endpoint (``https://gitlab.com/api/graphql``) unless " -"you're a self-hosted GitLab user." +#: ../system/core-workflows/how-do-they-work.rst:115 +msgid "Sets the field to mandatory." msgstr "" -#: ../system/integrations/gitlab.rst:43 -msgid "" -"Once completed, a new GitLab issues tab will appear in the ticket pane. 🎉" +#: ../system/core-workflows/how-do-they-work.rst:118 +msgid "set optional |ui| |api|" msgstr "" -#: ../system/integrations/gitlab.rst:51 -msgid "" -"Self-hosted administrators, please check your network settings to ensure " -"that your Zammad server can reach ``gitlab.com``." +#: ../system/core-workflows/how-do-they-work.rst:118 +msgid "Sets the field to optional." msgstr "" -#: ../system/integrations/i-doit.rst:2 -msgid "i-doit" +#: ../system/core-workflows/how-do-they-work.rst:124 +msgid "add option |ui| |api|" msgstr "" -#: ../system/integrations/i-doit.rst:4 -msgid "" -"`i-doit `_ is an open-source **configuration " -"management database** - in other words, a tool for keeping tabs on every " -"single piece of your physical and digital infrastructure, from network " -"equipment to virtual machines on down to the faceplates on your rack shelves " -"and more." +#: ../system/core-workflows/how-do-they-work.rst:121 +msgid "Allows adding options to tree selects or selects." msgstr "" -#: ../system/integrations/i-doit.rst:10 +#: ../system/core-workflows/how-do-they-work.rst:123 msgid "" -"What's that got to do with Zammad? Well, if you used tickets to track issues " -"with all that hardware, you might start wishing there was a way they could " -"talk to each other." -msgstr "" - -#: ../system/integrations/i-doit.rst:14 -msgid "Zammad gives you two:" +"You have to use the \"remove option\" before performing this action. It " +"allows you to use *existing* configured values." msgstr "" -#: ../system/integrations/i-doit.rst:17 -msgid "1. Add i-doit Links to Zammad Tickets" +#: ../system/core-workflows/how-do-they-work.rst:128 +msgid "remove option |ui| |api|" msgstr "" -#: ../system/integrations/i-doit.rst:20 ../system/integrations/i-doit.rst:80 -msgid "What Users See" +#: ../system/core-workflows/how-do-they-work.rst:127 +msgid "" +"Allows removing options from tree selects or selects. It allows you to use " +"*existing* configured values." msgstr "" -#: ../system/integrations/i-doit.rst:26 -msgid "i-doit integration in Zammad's ticket pane" +#: ../system/core-workflows/how-do-they-work.rst:134 +msgid "set fixed to |ui| |api|" msgstr "" -#: ../system/integrations/i-doit.rst:26 -msgid "" -"The i-doit integration will appear under a new 🖨 tab in the ticket pane." +#: ../system/core-workflows/how-do-they-work.rst:131 +msgid "Reduces the available options by your selection." msgstr "" -#: ../system/integrations/i-doit.rst:28 +#: ../system/core-workflows/how-do-they-work.rst:133 msgid "" -"i-doit integration puts a new tab in Zammad's ticket pane where you can add " -"links to existing i-doit devices for easy reference. (See our :user-docs:" -"`user documentation ` to learn " -"how it works in practice)." +"This reduces your workflows in terms of *add option* and *remove option*." msgstr "" -#: ../system/integrations/i-doit.rst:36 ../system/integrations/i-doit.rst:93 -msgid "How to Set it Up" +#: ../system/core-workflows/how-do-they-work.rst:137 +msgid "fill in |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:38 -msgid "" -"It requires i-doit's `API Add-on `_. Make sure to have it properly set up. Use the following setting:" +#: ../system/core-workflows/how-do-they-work.rst:137 +msgid "Allows filling in of string and integer fields with your values." msgstr "" -#: ../system/integrations/i-doit.rst:42 -msgid "Active: ``Yes``" +#: ../system/core-workflows/how-do-they-work.rst:141 +msgid "fill in empty |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:43 -msgid "Enforce authentication by username and password: ``No``" +#: ../system/core-workflows/how-do-they-work.rst:140 +msgid "" +"Allows filling in of string and integer fields with your values **if the " +"field is empty**." msgstr "" -#: ../system/integrations/i-doit.rst:45 -msgid "" -"To set it up, enable the integration in the Zammad admin panel under " -"**System > Integrations > i-doit**:" +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "select |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "i-doit settings within the integration pages" +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "Select a specific value within a select, tree select or boolean field." msgstr "" -#: ../system/integrations/i-doit.rst:53 -msgid "The root URL of your i-doit installation." +#: ../system/core-workflows/how-do-they-work.rst:153 +msgid "auto select |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:62 -msgid "API token" +#: ../system/core-workflows/how-do-they-work.rst:147 +msgid "Helps users with tree select and select fields:" msgstr "" -#: ../system/integrations/i-doit.rst:56 +#: ../system/core-workflows/how-do-they-work.rst:149 msgid "" -"Found in the i-doit admin panel under **Interfaces / external data > JSON-" -"RPC API > Common Settings**." +"If the field has only one option available for selection and no value yet, " +"the value will be automatically set." msgstr "" -#: ../system/integrations/i-doit.rst:0 -msgid "i-doit administration interface with API configuration" +#: ../system/core-workflows/how-do-they-work.rst:152 +msgid "" +"This option only works if you have one value and doesn't work if there is " +"more than one option available." msgstr "" -#: ../system/integrations/i-doit.rst:67 -msgid "Client ID" +#: ../system/core-workflows/how-do-they-work.rst:157 +msgid "set readonly |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:65 -msgid "A unique name to identify Zammad within i-doit." +#: ../system/core-workflows/how-do-they-work.rst:156 +msgid "" +"Allows you to display an attribute as read only (which means no changes are " +"possible)." msgstr "" -#: ../system/integrations/i-doit.rst:67 -msgid "(Zammad does not require you to enter a value here, but i-doit might!)" +#: ../system/core-workflows/how-do-they-work.rst:161 +msgid "unset readonly |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:70 +#: ../system/core-workflows/how-do-they-work.rst:160 msgid "" -"Here you can decide if the certificate of your i-doit system has to be " -"verified or not. In case you are using custom certificates, please have a " -"look at :doc:`how to add them to Zammad `." -msgstr "" - -#: ../system/integrations/i-doit.rst:77 -msgid "2. List / Create Zammad Tickets in i-doit" +"In case a workflow set the field in question to read only, you can undo this " +"with option above." msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "Zammad integration in i-doit's device view" +#: ../system/core-workflows/how-do-they-work.rst:172 +msgid "Stop after match" msgstr "" -#: ../system/integrations/i-doit.rst:86 +#: ../system/core-workflows/how-do-they-work.rst:174 msgid "" -"i-doit's ticket system integration gives you a way to see all the tickets " -"for a given device without ever leaving i-doit. (See our :user-docs:`user " -"documentation ` to learn how it " -"works in practice)." +"Here you can decide if other workflows are executed after the current one." msgstr "" -#: ../system/integrations/i-doit.rst:95 +#: ../system/core-workflows/how-do-they-work.rst:176 msgid "" -"Enable this integration in the i-doit admin panel under **Interfaces / " -"external data > Trouble Ticket System (TTS) > Configuration**:" +"If set to ``no`` (default), further workflows will be executed if they match " +"the condition. In this case, it is possible that your actions from the " +"current workflow can be overwritten by another workflow." msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "i-doit administration interface with TTS configuration" +#: ../system/core-workflows/how-do-they-work.rst:180 +msgid "" +"If set to ``yes``, no further worflows will be executed after the current " +"one." msgstr "" -#: ../system/integrations/i-doit.rst:104 -msgid "TTS-Type" +#: ../system/core-workflows/how-do-they-work.rst:184 +msgid "Priority" msgstr "" -#: ../system/integrations/i-doit.rst:104 -msgid "``Zammad``" +#: ../system/core-workflows/how-do-they-work.rst:186 +msgid "" +"You can define the sequence, in which the workflows are executed. The " +"default value is ``500``." msgstr "" -#: ../system/integrations/i-doit.rst:115 -msgid "Username / Password" +#: ../system/core-workflows/how-do-they-work.rst:189 +msgid "" +"The workflows are executed in ascending order by their priority. That means " +"lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." msgstr "" -#: ../system/integrations/i-doit.rst:107 -msgid "Login credentials for a Zammad agent." +#: ../system/core-workflows/learn-by-example.rst:2 +msgid "Learn by Example" msgstr "" -#: ../system/integrations/i-doit.rst:109 +#: ../system/core-workflows/learn-by-example.rst:4 msgid "" -"This agent must have **read permission** for all :doc:`groups ` that plan on using the i-doit integration." +"This page provides some basic examples for Core Workflows. Of course you can " +"build much more complex workflows if needed." msgstr "" -#: ../system/integrations/i-doit.rst:113 +#: ../system/core-workflows/learn-by-example.rst:7 msgid "" -"You may even wish to create a dedicated agent account just for this " -"integration (otherwise, if the agent ever changes her password, you will " -"have to remember to update it here)." +"To learn about Core Workflows in detail, first go to :doc:`how-do-they-work`." msgstr "" -#: ../system/integrations/i-doit.rst:117 -msgid "URL incl. protocol" +#: ../system/core-workflows/learn-by-example.rst:10 +msgid "Group Based Examples" msgstr "" -#: ../system/integrations/i-doit.rst:118 -msgid "``https://your.zammad.domain``" +#: ../system/core-workflows/learn-by-example.rst:12 +msgid "" +"All following workflows have the same base configurations. The workflow may " +"not use them all." msgstr "" -#: ../system/integrations/index.rst:2 -msgid "Integrations" +#: ../system/core-workflows/learn-by-example.rst:15 +msgid "Groups:" msgstr "" -#: ../system/integrations/index.rst:4 +#: ../system/core-workflows/learn-by-example.rst:20 +msgid "Attributes:" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:22 +msgid "Category (Single tree selection field, not mandatory, agents only)" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:23 msgid "" -"Zammad offers numerous integrations that add rich features to your instance." +"Approved (Boolean field, not mandatory, not shown, ``false`` as default)" msgstr "" -#: ../system/integrations/index.rst:6 -msgid "We're still working on this part of our documentation, stay tight!" +#: ../system/core-workflows/learn-by-example.rst:24 +msgid "Operating System (Text field, not mandatory, not shown)" msgstr "" -#: ../system/integrations/index.rst:10 -msgid "Integrations for Phone Systems" +#: ../system/core-workflows/learn-by-example.rst:25 +msgid "Software used (Single selection field, not mandatory, not shown)" msgstr "" -#: ../system/integrations/index.rst:14 -msgid "" -"Your VoIP provider or telephony system is not listed? Possibly your provider " -"supports Zammad by using the generic CTI - if you're unsure ask your " -"provider." +#: ../system/core-workflows/learn-by-example.rst:68 +msgid "Group specific values and fields" msgstr "" -#: ../system/integrations/index.rst:18 +#: ../system/core-workflows/learn-by-example.rst:28 msgid "" -"Provider does not support Zammad? Consider creating a `feature request in " -"the Zammad Community `_." +"This workflow set depends on the category field. It reduces the available " +"set of values based on the group selected." msgstr "" -#: ../system/integrations/index.rst:31 -msgid "Integrations for Authentication and Customers" +#: ../system/core-workflows/learn-by-example.rst:33 +msgid "Workflow 2nd Level group" msgstr "" -#: ../system/integrations/index.rst:44 -msgid "Integrations for Monitoring Systems" +#: ../system/core-workflows/learn-by-example.rst:35 +msgid "" +"This reduces the category options to ``2nd Level/*``, ``Internal/*`` and " +"``Others``. It also sets further required fields to mandatory and visible." msgstr "" -#: ../system/integrations/index.rst:46 -msgid "This section currently misses the following integrations:" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for 2nd level" msgstr "" -#: ../system/integrations/index.rst:48 -msgid "Icinga" +#: ../system/core-workflows/learn-by-example.rst:43 +msgid "Workflow Support group" msgstr "" -#: ../system/integrations/index.rst:49 -msgid "Monit" +#: ../system/core-workflows/learn-by-example.rst:45 +msgid "" +"This reduces the category options to ``Support/*``, ``Internal/*`` and " +"``Others``. It also sets further required fields to visible." msgstr "" -#: ../system/integrations/index.rst:50 -msgid "Nagios" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for support" msgstr "" -#: ../system/integrations/index.rst:60 -msgid "Integrations for Issue Trackers" +#: ../system/core-workflows/learn-by-example.rst:53 +msgid "Workflow Sales group" msgstr "" -#: ../system/integrations/index.rst:70 -msgid "Other Integrations" +#: ../system/core-workflows/learn-by-example.rst:55 +msgid "" +"This reduces the category options to ``Sales/*``, ``Internal/*`` and " +"``Others``." msgstr "" -#: ../system/integrations/index.rst:72 -msgid "" -"This section will hold any other integration that can't be grouped up (yet)." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for sales" msgstr "" -#: ../system/integrations/ldap/index.rst:2 -msgid "LDAP / Active Directory" +#: ../system/core-workflows/learn-by-example.rst:68 +#: ../system/integrations/slack.rst:88 +msgid "The Result" msgstr "" -#: ../system/integrations/ldap/index.rst:4 +#: ../system/core-workflows/learn-by-example.rst:63 msgid "" -"Zammad comes with a powerful LDAP integration that allows you to have a " -"single source of truth. By this you reduce the number of login credentials " -"your user has to remember." +"This is what the agent would experience with the above workflows in place." msgstr "" -#: ../system/integrations/ldap/index.rst:10 +#: ../system/core-workflows/learn-by-example.rst:0 msgid "" -"The LDAP source is also a perfect candidate for Zammad's :docs:`Kerberos " -"Single Sign-On ` but also works as addition " -"to other :doc:`/settings/security/third-party`." +"Workflow shows objects and limits options based on selections on the group" msgstr "" -#: ../system/integrations/ldap/index.rst:None -msgid "Zammands LDAP management page" +#: ../system/core-workflows/learn-by-example.rst:90 +msgid "Approval process" msgstr "" -#: ../system/integrations/ldap/index.rst:25 -msgid "📝 :doc:`manage`" +#: ../system/core-workflows/learn-by-example.rst:71 +msgid "" +"In this case ``approved`` is visible to agents by default. For this " +"workflow, an additional role ``Approval person`` is required (no further " +"permissions)." msgstr "" -#: ../system/integrations/ldap/index.rst:25 -msgid "Add, modify, remove or re-arrange your LDAP-Sources as needed." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that restricts an approval attribute to specific roles" msgstr "" -#: ../system/integrations/ldap/index.rst:30 -msgid "Before you continue, please note the following limitations." +#: ../system/core-workflows/learn-by-example.rst:81 +msgid "" +"This workflow may work best in combination with a :doc:`trigger ` but technically, this is not required." msgstr "" -#: ../system/integrations/ldap/index.rst:32 -msgid "Mapping / Synchronizing organizations is not possible" +#: ../system/core-workflows/learn-by-example.rst:84 +msgid "" +"Select fields may be a better approach because they allow more values than " +"just a simple ``true`` or ``false``." msgstr "" -#: ../system/integrations/ldap/index.rst:36 +#: ../system/core-workflows/learn-by-example.rst:0 msgid "" -"You may want to consider using domain based assignments to overcome this " -"issue. Learn more on :doc:`/manage/organizations/index`." +"Workflow fixes possible values of \"Approved ?\" to a specific selection " +"depending on the users role" msgstr "" -#: ../system/integrations/ldap/index.rst:39 +#: ../system/core-workflows/learn-by-example.rst:103 +msgid "State dependent mandatory fields" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:93 msgid "" -"Zammad's LDAP sync is one way. Editing user settings or permissions may be " -"overwritten upon the next sync depending on your configuration." +"This workflow sets ``Category`` to mandatory if the agent wants to set the " +"states ``closed`` or ``pending close`` to enforce categorization." msgstr "" -#: ../system/integrations/ldap/index.rst:41 -msgid "Nested groups are not supported." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that sets fields to mandatory on specific states" msgstr "" -#: ../system/integrations/ldap/index.rst:42 -msgid "Synchronizing user avatars from LDAP is not supported." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "" +"Workflow sets category field to mandatory upon choosing closed or pending " +"close as state" msgstr "" -#: ../system/integrations/ldap/index.rst:43 -msgid "Unlike user filters, group filters cannot be changed." +#: ../system/core-workflows/learn-by-example.rst:106 +msgid "Manual Ticket Handover Process" msgstr "" -#: ../system/integrations/ldap/index.rst:44 -msgid "" -"When a user originates from an LDAP server, Zammad will try to verify the " -"login credentials against LDAP first - if this fails Zammad will check its " -"local database." +#: ../system/core-workflows/learn-by-example.rst:108 +msgid "This example covers the handover of a ticket from one agent to another:" msgstr "" -#: ../system/integrations/ldap/index.rst:50 +#: ../system/core-workflows/learn-by-example.rst:110 msgid "" -"Users can have local passwords even if they're LDAP users! You can learn " -"more about user accounts in general on :doc:`/manage/users/index`." +"When the ticket owner is modified, a new text field (\"Handover\") shows up " +"for a comment" msgstr "" -#: ../system/integrations/ldap/index.rst:54 +#: ../system/core-workflows/learn-by-example.rst:112 msgid "" -"When several LDAP sources contain the same user (meaning the same email " -"address), the user in question will be updated with every source configured. " -"*The last LDAP source will win.*" +"This may only be visible when the owner is changed, therefore it has to be " +"hidden in general" msgstr "" -#: ../system/integrations/ldap/index.rst:58 -msgid "" -"This is subject to change with `Issue 4109 `_ in the future." +#: ../system/core-workflows/learn-by-example.rst:114 +msgid "The input in this handover text field is mandatory" msgstr "" -#: ../system/integrations/ldap/index.rst:60 +#: ../system/core-workflows/learn-by-example.rst:115 msgid "" -"Synchronization statistics currently affect *all* configured LDAP sources. " -"This also applies for newly added or updated sources." +"After submitting changes, the value of the handover field must be added as " +"an note to the ticket (via trigger)" msgstr "" -#: ../system/integrations/ldap/index.rst:63 -msgid "" -"This is subject to change with `Issue 4108 `_ in the future." +#: ../system/core-workflows/learn-by-example.rst:121 +msgid "Hiding handover field" msgstr "" -#: ../system/integrations/ldap/index.rst:65 -msgid "" -"Zammad currently has limited fallback server support. You can workaround " -"this by providing several sources - however, ensure to have the exact same " -"configuration on your fallback." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Hiding the handover field in core workflows" msgstr "" -#: ../system/integrations/ldap/index.rst:69 -msgid "" -"This is subject to improve with `Issue 4107 `_ in the future." +#: ../system/core-workflows/learn-by-example.rst:126 +msgid "Showing handover field and setting it to mandatory" msgstr "" -#: ../system/integrations/ldap/index.rst:76 -msgid "" -"This section holds all requests Zammad handled for all LDAP sources. These " -"entries can either contain synchronization information or logins " -"(authentication attempts via Zammad's login interface)." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Showing the handover field and set it as mandatory" msgstr "" -#: ../system/integrations/ldap/index.rst:80 -msgid "" -"By clicking on any request, Zammad will provide even more information. The " -"provided information can be useful when something does not work as expected." +#: ../system/core-workflows/learn-by-example.rst:131 +msgid "Trigger writing handover input to a new article" msgstr "" -#: ../system/integrations/ldap/index.rst:85 -msgid "" -"Especially a LDAP synchronization can cause many log entries. The web " -"interface will always limit the number of shown entries to the last 50 " -"entries." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Write handover content to a new article" msgstr "" -#: ../system/integrations/ldap/index.rst:None +#: ../system/core-workflows/learn-by-example.rst:133 msgid "" -"Screencast showing LDAP integration log entries and a detail view on\n" -"an entry." +"As a result, the ticket includes an article of the type note which includes " +"the predefined text and the handover comment." msgstr "" -#: ../system/integrations/ldap/manage.rst:2 -msgid "Manage LDAP-Sources" +#: ../system/core-workflows/limitations.rst:6 +msgid "Core Workflows do not replace Triggers" msgstr "" -#: ../system/integrations/ldap/manage.rst:6 +#: ../system/core-workflows/limitations.rst:5 msgid "" -"Please keep in mind all current limitations for the LDAP synchronization. " -"This will help to understand scopes of the following operations better." +"Workflows manipulate the behavior of fields. However, they do not set values " +"in fields because of actions." msgstr "" -#: ../system/integrations/ldap/manage.rst:65 -msgid "Add new source" +#: ../system/core-workflows/limitations.rst:16 +msgid "API calls are only partly affected" msgstr "" -#: ../system/integrations/ldap/manage.rst:10 +#: ../system/core-workflows/limitations.rst:9 msgid "" -"Using the *New Source* button allows you to add new LDAP sources to your " -"installation. You're not limited in the number of sources, however, keep in " -"mind that many sources will also take more time to synchronize." +"Some options affect UI only and thus do not restrict responses and calls." msgstr "" -#: ../system/integrations/ldap/manage.rst:14 -msgid "" -"You can choose between different encryption types, namely *SSL* and " -"*STARTTLS* or none of them (\"*No SSL*\"). If you choose *SSL* or " -"*STARTTLS*, Zammad will display an additional *SSL verification* option that " -"allows you to disable the verification, e.g. for self-signed SSL " -"certificates. You can also tell Zammad to use a different port by appending " -"``:`` to your hostname/IP." +#: ../system/core-workflows/limitations.rst:11 +msgid "This affects the following actions:" msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "" -"Screenshot of configuring a new LDAP source with SSL encryption and SSL " -"verification" +#: ../system/core-workflows/limitations.rst:13 +msgid "select" msgstr "" -#: ../system/integrations/ldap/manage.rst:26 -msgid "" -"New Source with SSL transport security enabled and certificate verification" +#: ../system/core-workflows/limitations.rst:14 +msgid "auto select" msgstr "" -#: ../system/integrations/ldap/manage.rst:30 -msgid "" -"Using an user filter can be a good idea if you only require a small subset " -"of your LDAP users in Zammad." +#: ../system/core-workflows/limitations.rst:15 +msgid "show" msgstr "" -#: ../system/integrations/ldap/manage.rst:42 -msgid "This especially affects inactive users" +#: ../system/core-workflows/limitations.rst:16 +msgid "hide" msgstr "" -#: ../system/integrations/ldap/manage.rst:34 -msgid "" -"As every LDAP behaves differently on which attributes and how they are set, " -"Zammad doesn't care about any flags." +#: ../system/core-workflows/limitations.rst:25 +msgid "Some fields stay unavailable to customers" msgstr "" -#: ../system/integrations/ldap/manage.rst:37 +#: ../system/core-workflows/limitations.rst:19 msgid "" -"Users that no longer are returned by your LDAP source will automatically be " -"set to inactive. Zammad assumes that the user was deactivated." +"For technical and security reasons, some default fields (the pale ones you " +"can't edit) stay unavailable for display and usage on customer permissions." msgstr "" -#: ../system/integrations/ldap/manage.rst:41 +#: ../system/core-workflows/limitations.rst:23 msgid "" -"Users will never be removed automatically! If you want to remove obsolete " -"users, use :doc:`/system/data-privacy`." +"If you require your customers to change e.g. priorities, please consider " +"using workarounds via :doc:`/system/objects` and :doc:`/manage/trigger`." msgstr "" -#: ../system/integrations/ldap/manage.rst:46 -msgid "Active Directory admins" +#: ../system/core-workflows/limitations.rst:29 +msgid "Ticket title changes not supported in edit mask" msgstr "" -#: ../system/integrations/ldap/manage.rst:45 +#: ../system/core-workflows/limitations.rst:28 msgid "" -"Active Directories are quite specific on how to filter for active users only " -"- please see the `Microsoft documentation `_ for more " -"information." +"It is currently not possible to perform changes of the ticket title in the " +"edit mask (e.g. renaming, set to read-only)." msgstr "" -#: ../system/integrations/ldap/manage.rst:51 -msgid "" -"*Do not* manually write pathes of either LDAP attributes or groups. If " -"Zammad does not display them, it either cannot find them or you have a lot " -"of users that don't have the attributes populated." +#: ../system/core-workflows/limitations.rst:37 +msgid "What is out of scope of Core Workflows?" msgstr "" -#: ../system/integrations/ldap/manage.rst:55 +#: ../system/core-workflows/limitations.rst:32 msgid "" -"Zammad will always only return attributes that are filled - this reduces the " -"returned list of attributes greatly." +"There are some things that would count as workflow but are either done via :" +"doc:`/manage/trigger` or :doc:`/manage/scheduler`." msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing how to add a new LDAP source" +#: ../system/core-workflows/limitations.rst:35 +msgid "Such as (but not limited to):" msgstr "" -#: ../system/integrations/ldap/manage.rst:63 -msgid "" -"If your LDAP system doesn't allow anonymous bind, Zammad detects it and " -"provides you an editable \"Base DN\" *text* field instead of a prefilled " -"*select* field." +#: ../system/core-workflows/limitations.rst:37 +msgid "up- or downgrade permissions of users" msgstr "" -#: ../system/integrations/ldap/manage.rst:81 -msgid "Review or edit existing source" +#: ../system/core-workflows/limitations.rst:38 +msgid "affecting article creation or listing" msgstr "" -#: ../system/integrations/ldap/manage.rst:68 +#: ../system/data-privacy.rst:2 +msgid "Data Privacy" +msgstr "" + +#: ../system/data-privacy.rst:4 msgid "" -"Clicking on a LDAP source will provide a configuration and mapping overview." +"For compliance with GDPR and other data privacy laws, you may wish to " +"**permanently delete users from the system**, along with **all of their " +"associated tickets**." msgstr "" -#: ../system/integrations/ldap/manage.rst:70 +#: ../system/data-privacy.rst:8 msgid "" -"If needed you can then use the *Change* button to update either the name, " -"active state or the whole configuration. If you're changing the whole " -"configuration, the dialogue will be identical to the source creation." +"You can create manual deletion tasks or even automated deletion tasks for " +"tickets and users based on custom conditions via :doc:`scheduler `!" msgstr "" -#: ../system/integrations/ldap/manage.rst:76 +#: ../system/data-privacy.rst:12 msgid "" -"Did your LDAP server change? Different LDAP servers have different " -"structures and default attributes. This causes the LDAP synchronization to " -"likely fail. Consider removing the affected source and re-add it." +"Access to this panel requires ``admin.data_privacy`` permissions (introduced " +"in Zammad 3.5)." msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing the update of the source name." +#: ../system/data-privacy.rst:15 +msgid "" +"On older systems that have not been updated yet, customers can also be :docs:" +"`deleted via the Zammad console `." msgstr "" -#: ../system/integrations/ldap/manage.rst:89 -msgid "Re-arrange LDAP source's order" +#: ../system/data-privacy.rst:22 +msgid "User deletion dialog in the Data Privacy panel" msgstr "" -#: ../system/integrations/ldap/manage.rst:84 +#: ../system/data-privacy.rst:22 msgid "" -"You can change the synchronization order for each source at any time. Zammad " -"will synchronize the sources from top to bottom." +"The user deletion dialog lists some of the tickets that will be removed from " +"the system along with the user." msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "" -"Screencasting showing how to change the source order by using\n" -"drag and drop." +#: ../system/data-privacy.rst:27 +msgid "Deleting Users via GUI" msgstr "" -#: ../system/integrations/ldap/manage.rst:101 -msgid "Remove a source" +#: ../system/data-privacy.rst:29 +msgid "🔥 **All deletions are FINAL!**" msgstr "" -#: ../system/integrations/ldap/manage.rst:92 -msgid "" -"If you no longer need the a LDAP source or simply want to start over, you " -"can remove them at any time. This will not remove synchronized users, data " -"synchronized or permissions." +#: ../system/data-privacy.rst:31 +msgid "Once you click “Delete”, the action cannot be canceled or undone." msgstr "" -#: ../system/integrations/ldap/manage.rst:98 +#: ../system/data-privacy.rst:33 msgid "" -"Not sure if you'd need the source later on? Set the source to inactive " -"instead of removing it - see *Review or edit existing source* for more." +"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." msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing how to remove LDAP sources." +#: ../system/data-privacy.rst:36 +msgid "**The following records cannot be deleted:**" msgstr "" -#: ../system/integrations/pgp/index.rst:2 -msgid "PGP" +#: ../system/data-privacy.rst:38 +msgid "your own account" msgstr "" -#: ../system/integrations/pgp/index.rst:7 -msgid "" -"Pretty Good Privacy (PGP) is another method for secure email communication. " -"With PGP, you can exchange **signed** and **encrypted** messages with others." +#: ../system/data-privacy.rst:39 +msgid "the system's last remaining administrator account" msgstr "" -#: ../system/integrations/pgp/index.rst:13 -#: ../system/integrations/smime/index.rst:17 -msgid "Signing" +#: ../system/data-privacy.rst:42 +msgid "Step 1: Find a User / Confirm Deletion" msgstr "" -#: ../system/integrations/pgp/index.rst:11 -msgid "is a proof that a message hasn't been manipulated on its way." +#: ../system/data-privacy.rst:44 +msgid "There are three ways to access the user deletion dialog:" msgstr "" -#: ../system/integrations/pgp/index.rst:13 -msgid "" -"In other words, it guarantees message **integrity** and **authenticity**." +#: ../system/data-privacy.rst:51 +msgid "**from the user's profile**" msgstr "" -#: ../system/integrations/pgp/index.rst:19 -#: ../system/integrations/smime/index.rst:22 -msgid "Encryption" +#: ../system/data-privacy.rst:0 +msgid "Accessing the user deletion dialog in a user profile" msgstr "" -#: ../system/integrations/pgp/index.rst:16 -#: ../system/integrations/smime/index.rst:20 -msgid "" -"scrambles a message so that it can only be unscrambled by the intended " -"recipient." +#: ../system/data-privacy.rst:51 +msgid "Click **Action > Delete**." msgstr "" -#: ../system/integrations/pgp/index.rst:19 -msgid "" -"In other words, it guarantees message **privacy** and **data security**." +#: ../system/data-privacy.rst:58 +msgid "**in the “Manage > Users” Admin Panel**" msgstr "" -#: ../system/integrations/pgp/index.rst:25 -msgid "Screenshot of ticket creation with encrypt and sign buttons" +#: ../system/data-privacy.rst:0 +msgid "Accessing the user deletion dialog under “Users” in the Admin Panel" msgstr "" -#: ../system/integrations/pgp/index.rst:25 -msgid "" -"Once PGP has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " -"appear in the ticket composer." +#: ../system/data-privacy.rst:58 +msgid "Use the **⋮ Actions** menu for the target user." msgstr "" -#: ../system/integrations/pgp/index.rst:28 -msgid "**Sign button not visible?**" +#: ../system/data-privacy.rst:66 ../system/data-privacy.rst:104 +msgid "**in the “System > Data Privacy” Admin Panel**" msgstr "" -#: ../system/integrations/pgp/index.rst:30 +#: ../system/data-privacy.rst:0 msgid "" -"Please note that the signing of emails is based on the outgoing email " -"account. That means you have to choose a group with a sender email account, " -"which has a private key assigned." +"Accessing the user deletion dialog under “Data Privacy” in the Admin Panel" msgstr "" -#: ../system/integrations/pgp/index.rst:35 -msgid "Handling of Keys" +#: ../system/data-privacy.rst:65 +msgid "" +"Use the **New Deletion Task** button. Search for users by name or email " +"address." msgstr "" -#: ../system/integrations/pgp/index.rst:36 -msgid "" -"To use the PGP function, you have to enable the integration (PGP) by " -"switching the toggle to *enabled*." +#: ../system/data-privacy.rst:79 +msgid "**Delete organizations**" msgstr "" -#: ../system/integrations/pgp/index.rst:39 +#: ../system/data-privacy.rst:69 msgid "" -"You can add keys by clicking the *add key* button. The keys can be imported " -"from a file or you can paste the content of the key in the text box." +"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:" msgstr "" -#: ../system/integrations/pgp/index.rst:42 -msgid "**Which keys do I have to import?**" +#: ../system/data-privacy.rst:0 +msgid "Deleting an organization via the user deletion dialog" msgstr "" -#: ../system/integrations/pgp/index.rst:44 +#: ../system/data-privacy.rst:78 msgid "" -"For **signing** *outgoing* emails, you have to import the private key of " -"your Zammad email account." +"If this option does not appear, make sure there are no pending deletion " +"tasks for other customers from this organization." msgstr "" -#: ../system/integrations/pgp/index.rst:47 -msgid "" -"For **encrypting** *outgoing* emails, you have to import the public key of " -"the customer's email account." +#: ../system/data-privacy.rst:82 +msgid "Step 2: Monitor Deletion Job Status" msgstr "" -#: ../system/integrations/pgp/index.rst:50 +#: ../system/data-privacy.rst:84 msgid "" -"For **verifying the signature** of signed *incoming* emails, you have to " -"import the public key of the customer." +"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:" msgstr "" -#: ../system/integrations/pgp/index.rst:53 -msgid "" -"For **decrypting** of encrypted *incoming* emails, you have to import the " -"private key of your Zammad email account." +#: ../system/data-privacy.rst:98 +msgid "**in the Activity Stream**" msgstr "" -#: ../system/integrations/pgp/index.rst:57 -msgid "Import Keys From a File" +#: ../system/data-privacy.rst:0 +msgid "Activity Stream showing data privacy tasks" msgstr "" -#: ../system/integrations/pgp/index.rst:58 -msgid "You can import keys from a file in the section **Upload key**:" +#: ../system/data-privacy.rst:94 +msgid "" +"For each deleted user, the Activity Stream will be updated twice—once when " +"the task is created, and once when it's complete." msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of adding a key via file" +#: ../system/data-privacy.rst:97 +msgid "" +"These notifications are only visible to users with ``admin.data_privacy`` " +"permissions." msgstr "" -#: ../system/integrations/pgp/index.rst:64 +#: ../system/data-privacy.rst:0 msgid "" -"**Supported file formats:** ASCII-armor as well as binary GPG format " -"(basically any GPG supported key format) is supported here." +"The task list within Data Privacy shows removals being in progress and " +"completed." msgstr "" -#: ../system/integrations/pgp/index.rst:68 -msgid "Import Keys by Pasting the Content" +#: ../system/data-privacy.rst:107 +msgid "Frequently Asked Questions" msgstr "" -#: ../system/integrations/pgp/index.rst:69 -msgid "You can also paste the key's content in the section **paste key**:" +#: ../system/data-privacy.rst:121 +msgid "What happens if I receive an email from a deleted customer?" msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of adding a key via pasting" +#: ../system/data-privacy.rst:110 +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/integrations/pgp/index.rst:75 +#: ../system/data-privacy.rst:115 msgid "" -"**Supported format:** Please note that only ASCII-armor is supported here." +"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**." msgstr "" -#: ../system/integrations/pgp/index.rst:78 -msgid "Deleting Keys" +#: ../system/data-privacy.rst:130 +msgid "What about user information stored in internal notes or other messages?" msgstr "" -#: ../system/integrations/pgp/index.rst:79 +#: ../system/data-privacy.rst:124 msgid "" -"If you want to delete a specific key, you can do it by clicking on the menu " -"in the *actions* column and select **delete**:" +"The deletion process removes **user accounts and associated tickets only**." msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of deleting a key" +#: ../system/data-privacy.rst:126 +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." msgstr "" -#: ../system/integrations/pgp/index.rst:88 -msgid "Downloading Keys" +#: ../system/data-privacy.rst:137 +msgid "I deleted an user and can still see a message they sent!" msgstr "" -#: ../system/integrations/pgp/index.rst:89 +#: ../system/data-privacy.rst:133 msgid "" -"If you want to download your keys, you can do this as well via corresponding " -"action buttons. Depending on the key, you can choose wether you want to " -"download the private or the public key." +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:95 -#: ../system/integrations/smime/manage-certificates.rst:76 -msgid "Default Behavior" +#: ../system/data-privacy.rst:141 +msgid "I removed a customer, now my reporting is off!" msgstr "" -#: ../system/integrations/pgp/index.rst:96 +#: ../system/data-privacy.rst:140 msgid "" -"Here you can adjust on per group basis, if *sign* and *encryption* is on or " -"off by default. Please be aware, that agents can always override the setting " -"for each individual article." +"When removing users and their tickets, all references are removed. This also " +"affects e.g. Reporting - these information are lost." msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Adjusting default behavior on per group basis" +#: ../system/data-privacy.rst:145 +msgid "How long does Zammad store created tasks?" msgstr "" -#: ../system/integrations/pgp/index.rst:107 +#: ../system/data-privacy.rst:144 msgid "" -"Here you can see the last actions regarding signing and encryption and if " -"they were successful." -msgstr "" - -#: ../system/integrations/pgp/index.rst:117 -msgid "**Sign button is not visible, but keys are imported.**" +"Please see the on-premise data section of the :docs:`data privacy ` chapter." msgstr "" -#: ../system/integrations/pgp/index.rst:115 -msgid "Did you choose a group in the ticket?" +#: ../system/data-privacy.rst:150 +msgid "What about re-assigned tickets? I want to delete them, too." msgstr "" -#: ../system/integrations/pgp/index.rst:116 +#: ../system/data-privacy.rst:148 msgid "" -"Did you import a private key for the email adress, which is used for " -"outgoing emails in the group?" +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:122 -msgid "**How to obtain keys?**" +#: ../system/data-privacy.rst:154 +msgid "Why are there so many deletion task entries, I didn't create them!" msgstr "" -#: ../system/integrations/pgp/index.rst:120 +#: ../system/data-privacy.rst:153 msgid "" -"You can create them yourself! There are some good tutorials on the web on " -"how to create them. Providing keys to Zammad is a prerequisite to use the " -"PGP feature." -msgstr "" - -#: ../system/integrations/pgp/index.rst:127 -msgid "**It says a passphrase is needed, but I haven't got one.**" +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:125 -msgid "" -"If the key is secured with a passphrase, you have to provide it for the " -"import in Zammad. It is possible that keys may have an empty passphrase. " -"However, this is *not* recommended." +#: ../system/integrations/checkmk/admin-panel-reference.rst:2 +msgid "Admin Panel Reference" msgstr "" -#: ../system/integrations/pgp/index.rst:132 -msgid "**How do my customers get my new key?**" +#: ../system/integrations/checkmk/admin-panel-reference.rst:None +msgid "Screenshot of Checkmk settings overview" msgstr "" -#: ../system/integrations/pgp/index.rst:130 +#: ../system/integrations/checkmk/admin-panel-reference.rst:12 msgid "" -"You have to provide your **public** key in advance. Your customer also has " -"to configure PGP in their email workflow and import your public key. The " -"other way round, you have to get the public key of your customer and have to " -"import it to Zammad." +"Which :doc:`group ` should Checkmk tickets be assigned " +"to as a default (*i.e.,* when none is specified)?" msgstr "" -#: ../system/integrations/slack.rst:2 -msgid "Slack" +#: ../system/integrations/checkmk/admin-panel-reference.rst:15 +msgid "(Applies to :ref:`API alerts ` only.)" msgstr "" -#: ../system/integrations/slack.rst:4 -msgid "**⚠️ Deprecation warning ⚠️**" +#: ../system/integrations/checkmk/admin-panel-reference.rst:21 +msgid "Auto close" msgstr "" -#: ../system/integrations/slack.rst:6 +#: ../system/integrations/checkmk/admin-panel-reference.rst:18 msgid "" -"Zammad 7 will no longer support this dedicated Slack integration. It is " -"recommended to switch to :doc:`pre-defined webhooks ` instead. Existing Slack integrations should " -"be migrated manually before this feature is dropped." +"Should Zammad automatically close tickets if a service has recovered on its " +"own?" msgstr "" -#: ../system/integrations/slack.rst:14 -msgid "" -"In order to use this feature, please add a new Slack app to your Workspace. " -"The App you need is called ``Incoming WebHooks`` ." +#: ../system/integrations/checkmk/admin-panel-reference.rst:21 +msgid "(Agents will receive notifications for such closures as appropriate.)" msgstr "" -#: ../system/integrations/slack.rst:18 -msgid "Why Do I Need This Feature?" +#: ../system/integrations/checkmk/admin-panel-reference.rst:30 +msgid "Auto-close state" msgstr "" -#: ../system/integrations/slack.rst:20 -msgid "" -"If you're already using Slack for your team communication, you'll love this " -"feature! Our Slack integration can push ticket notifications about the last " -"ticket article based on the following events:" +#: ../system/integrations/checkmk/admin-panel-reference.rst:24 +msgid "What ticket state should be applied when “auto-closing” a ticket?" msgstr "" -#: ../system/integrations/slack.rst:24 -msgid "on Ticket creation" +#: ../system/integrations/checkmk/admin-panel-reference.rst:26 +msgid "" +"You can choose from the seven built-in ticket states. If these states aren't " +"enough for you, you can :ref:`define a new ticket state ` for this purpose as well. This can be useful for tracking " +"tickets with :doc:`reports `, for example." msgstr "" -#: ../system/integrations/slack.rst:25 -msgid "on Ticket updates" +#: ../system/integrations/checkmk/admin-panel-reference.rst:35 +#: ../system/integrations/cti/includes/recent-logs.include.rst:2 +#: ../system/integrations/ldap/index.rst:74 +#: ../system/integrations/pgp/index.rst:106 +msgid "Recent Logs" msgstr "" -#: ../system/integrations/slack.rst:26 -msgid "on reached reminders" +#: ../system/integrations/checkmk/admin-panel-reference.rst:None +msgid "Screenshot of Checkmk \"Recent Logs\" section" msgstr "" -#: ../system/integrations/slack.rst:27 -msgid "a Ticket has escalated" +#: ../system/integrations/checkmk/admin-panel-reference.rst:41 +msgid "" +"If you're having trouble getting Zammad and Checkmk to play nicely together, " +"this section can help you troubleshoot." msgstr "" -#: ../system/integrations/slack.rst:28 -msgid "a Ticket is going to escalate" +#: ../system/integrations/checkmk/admin-panel-reference.rst:44 +msgid "" +"It contains a record of the fifty most recent transactions that Zammad knows " +"about, including each one's request/response details and return status." msgstr "" -#: ../system/integrations/slack.rst:30 -msgid "" -"Zammad will provide the Ticket title, a direct link to the Ticket, the event " -"type (creation, updated, escalation), the customer, time and the last " -"article that has triggered the notification." +#: ../system/integrations/checkmk/api-reference.rst:2 +msgid "API Reference" msgstr "" -#: ../system/integrations/slack.rst:34 +#: ../system/integrations/checkmk/api-reference.rst:4 msgid "" -"This will give you further options, as you can see e.g. escalating tickets " -"that are assigned to an agent that's e.g. absent. You can interact faster, " -"as you might see problems earlier (or even before the problem gets one)." +"For most users, :ref:`the sample scripts from the Setup Guide ` will do the job just fine. But if you want more fine-grained control" +"—for instance, to create high- and low-priority tickets for different types " +"of system events—then you'll have to customize the data those scripts send " +"to Zammad." msgstr "" -#: ../system/integrations/slack.rst:38 +#: ../system/integrations/checkmk/api-reference.rst:15 msgid "" -"If needed and wanted, you can even discuss directly about the topic before " -"sending an answer to the customer. Another possible use case would be a " -"agent monitoring new agents and their answers to tickets." +"This custom script will automatically set all tickets it creates to **high " +"priority** and **assign them to charlie@chrispresso.com**." msgstr "" -#: ../system/integrations/slack.rst:44 -msgid "Configure the Integration" +#: ../system/integrations/checkmk/api-reference.rst:32 +msgid "How Does it Work?" msgstr "" -#: ../system/integrations/slack.rst:46 +#: ../system/integrations/checkmk/api-reference.rst:34 msgid "" -"First of all, please go to your slack workspace - go to administration => " -"Manage Apps. If you don't have an app yet, you can simply add a new one - " -"just search for ``Incoming WebHooks`` and customize the app to your needs." +"There are two kinds of data you can pass to the API, both in the form of key-" +"value pairs:" msgstr "" -#: ../system/integrations/slack.rst:50 -msgid "" -"Choose (or create) the channel Zammad should post it's information to and " -"press on \"Add Incoming WebHooks integration\". If you're ready, copy the " -"provided WebHook URL and go to your Zammad installation." +#: ../system/integrations/checkmk/api-reference.rst:44 +msgid "Checkmk parameters" msgstr "" -#: ../system/integrations/slack.rst:56 +#: ../system/integrations/checkmk/api-reference.rst:38 msgid "" -"You need administrative rights on the Slack Workspace. The link to the app " -"directory is normally ``https://[workspace-name].slack.com/apps`` ." +"are required, and make up the **contents** of the resulting tickets/" +"articles. They also determine whether an event creates a new ticket or " +"updates/closes an existing one." msgstr "" -#: ../system/integrations/slack.rst:63 +#: ../system/integrations/checkmk/api-reference.rst:42 msgid "" -"To configure the slack integration, log in to Zammad and go to Integrations " -"(System) => Slack in the admin panel." +"These are the only values used in the sample scripts. **Use them as-is**; " +"technically, they can be customized, but it's hard to imagine a good reason " +"for it." msgstr "" -#: ../system/integrations/slack.rst:66 -msgid "" -"Here you can choose on what evens Zammad should post information about a " -"ticket to your Slack channel. Next you need to device what groups shall be " -"affected by this, as anybody with access to that specific Slack channel can " -"read at least parts of the ticket this might be a privacy issue, if you " -"select the wrong groups. The username is simply the name that Zammad uses as " -"display name inside the Slack chat. The channel defines the Slack channel " -"the information is being posted in. As last option, you can set a custom " -"icon for posting to slack." +#: ../system/integrations/checkmk/api-reference.rst:52 +msgid "Ticket attributes" msgstr "" -#: ../system/integrations/slack.rst:74 +#: ../system/integrations/checkmk/api-reference.rst:47 msgid "" -"When you're ready, just hit \"Submit\" and enable the integration. Zammad " -"will now post new ticket information based on the trigger you chose. Below " -"the options you have the recent log that shows the latest requests to Slack " -"for debugging if needed." +"are optional, and can be used to **adjust settings** on newly created " +"tickets (*e.g.,* set the owner, group, priority, or state)." msgstr "" -#: ../system/integrations/slack.rst:81 +#: ../system/integrations/checkmk/api-reference.rst:50 msgid "" -"If you leave the Icon URL empty, Zammad will use the Zammad logo instead. " -"The icon should be a square PNG file." +"If you want to customize your Checkmk alert script, do it with these. Simply " +"add an extra “form” option for each one (``-F \"key=value\"``) to your " +"script's ``curl`` command line, as in the example above." msgstr "" -#: ../system/integrations/slack.rst:90 -msgid "" -"The following figure shows how it will look if you choose to receive updates " -"on created and updated tickets. On every post Zammad sends to the Slack " -"channel, you can create new threads to discuss about the new article." +#: ../system/integrations/checkmk/api-reference.rst:54 +msgid "💡 **It's just an API endpoint!**" msgstr "" -#: ../system/integrations/slack.rst:96 +#: ../system/integrations/checkmk/api-reference.rst:56 msgid "" -"If you just want to keep track of soon escalating or already escalated " -"tickets, it will look the the following figure. Zammad changes the color in " -"front of the post so you can easily see the state of the ticket." +"When using Checkmk integration, messages need to be formatted in a certain " +"way, but that *doesn't mean the messages actually have to come from Checkmk*." msgstr "" -#: ../system/integrations/slack.rst:102 +#: ../system/integrations/checkmk/api-reference.rst:59 msgid "" -"If you change the state, Zammad will also put information on what state the " -"ticket gets and (if pending state) the date until it pends. You'll also " -"recognize the color codes in front of posts on slack, as they are exact the " -"same the ticket state colors you'll see in Zammad!" +"If you use another monitoring tool that's not officially supported by " +"Zammad, there's probably a way to make it work with your Checkmk callback " +"URL." msgstr "" -#: ../system/integrations/smime/index.rst:2 -msgid "S/MIME" +#: ../system/integrations/checkmk/api-reference.rst:63 +msgid "Checkmk Parameters" msgstr "" -#: ../system/integrations/smime/index.rst:11 +#: ../system/integrations/checkmk/api-reference.rst:65 msgid "" -"S/MIME is the most widely-supported method for secure email communication. " -"With S/MIME, you can exchange **signed** and **encrypted** messages with " -"others." +"When a notification is received, Zammad creates a new article containing the " +"details of the event that triggered it:" msgstr "" -#: ../system/integrations/smime/index.rst:15 -msgid "" -"is proof that a message hasn't been tampered with or sent by an impersonator." +#: ../system/integrations/checkmk/api-reference.rst:None +msgid "Checkmk article body" msgstr "" -#: ../system/integrations/smime/index.rst:17 +#: ../system/integrations/checkmk/api-reference.rst:72 msgid "" -"In other words, it guarantees a message's **integrity** and **authenticity**." +"These details come from the fields listed below, which correspond to " +"parameters provided by Checkmk (``$NOTIFY_*``)." msgstr "" -#: ../system/integrations/smime/index.rst:22 -msgid "In other words, it guarantees **privacy** and **data security**." +#: ../system/integrations/checkmk/api-reference.rst:75 +msgid "**Required fields are marked with an asterisk (\\*).**" msgstr "" -#: ../system/integrations/smime/index.rst:28 -msgid "Screencast demo of S/MIME features for both new tickets and replies" +#: ../system/integrations/checkmk/api-reference.rst:79 +msgid "event_id\\*" msgstr "" -#: ../system/integrations/smime/index.rst:28 +#: ../system/integrations/checkmk/api-reference.rst:78 msgid "" -"Once S/MIME has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " -"appear in the ticket composer." +"A unique ID for the system event. (``$NOTIFY_SERVICEPROBLEMID`` / " +"``$NOTIFY_HOSTPROBLEMID``)" msgstr "" -#: ../system/integrations/smime/index.rst:32 -msgid ":doc:`🔪 Prerequisites `" +#: ../system/integrations/checkmk/api-reference.rst:86 +msgid "host\\*" msgstr "" -#: ../system/integrations/smime/index.rst:31 +#: ../system/integrations/checkmk/api-reference.rst:82 msgid "" -"New to S/MIME? This section helps you to find certificate providers and " -"points out Limitations." +"The hostname of the system that the event originated from. " +"(``$NOTIFY_HOSTNAME``)" msgstr "" -#: ../system/integrations/smime/index.rst:35 -msgid ":doc:`📝 Manage Certificates `" +#: ../system/integrations/checkmk/api-reference.rst:85 +msgid "" +"Used to determine if a new event belongs to an existing ticket. Also used in " +"the subject line of the resulting article (“ is ”)." msgstr "" -#: ../system/integrations/smime/index.rst:35 -msgid "Add and download certificates; configure group default behaviors." +#: ../system/integrations/checkmk/api-reference.rst:96 +msgid "service" msgstr "" -#: ../system/integrations/smime/index.rst:38 -msgid ":doc:`😦 Troubleshooting `" +#: ../system/integrations/checkmk/api-reference.rst:89 +msgid "" +"The name of the service that the event originated from. " +"(``$NOTIFY_SERVICEDESC``)" msgstr "" -#: ../system/integrations/smime/index.rst:38 -msgid "Took a wrong turn? About recent logs and common issues." +#: ../system/integrations/checkmk/api-reference.rst:92 +msgid "Used to determine if a new event belongs to an existing ticket." msgstr "" -#: ../system/integrations/smime/index.rst:43 -msgid "" -"For more details on how S/MIME integration works on the agent side, see the :" -"user-docs:`user docs `." +#: ../system/integrations/checkmk/api-reference.rst:94 +#: ../system/integrations/checkmk/api-reference.rst:110 +msgid "Displayed as ``-`` when omitted." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:2 -msgid "Manage Certificates" +#: ../system/integrations/checkmk/api-reference.rst:104 +msgid "state\\*" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:4 +#: ../system/integrations/checkmk/api-reference.rst:99 msgid "" -"S/MIME is **disabled by default**. Enable it to start adding certificates." +"The current state of the service or host in question. " +"(``$NOTIFY_SERVICESTATE`` / ``$NOTIFY_HOSTSTATE``)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:10 -msgid "Dialogue to add new certificates or private keys" +#: ../system/integrations/checkmk/api-reference.rst:102 +msgid "" +"Used to detect when a ticket should be auto-closed (*i.e.,* on ``OK``/" +"``UP``). Also used in the subject line of the resulting article (“ is " +"”)." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:10 +#: ../system/integrations/checkmk/api-reference.rst:110 +msgid "text" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:107 msgid "" -"Manage certificates in the Admin Panel under **System > Integrations > S/" -"MIME**. Certificates may be pasted in as plain text or uploaded from a file." +"The output of the process that triggered the event. " +"(``$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:14 -msgid "Add Certificate Data" +#: ../system/integrations/checkmk/api-reference.rst:121 +msgid "" +"The Object Manager attribute panel displays built-in and custom\n" +"attribute names." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:36 -msgid "Add Certificate" +#: ../system/integrations/checkmk/api-reference.rst:121 +msgid "Find a complete list of ticket attributes in the Object Manager." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:17 +#: ../system/integrations/checkmk/api-reference.rst:123 msgid "" -"Import public-key certificates for both your own organization and your " -"contacts." +"Ticket attributes are entirely optional, and can be used to customize the " +"tickets that Checkmk creates. (Note that these attributes will be ignored if " +"a new event belongs to an existing ticket.)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:19 +#: ../system/integrations/checkmk/api-reference.rst:128 msgid "" -"You can also add a bunch of certificates in one go by providing a single " -"file with all relevant certificates." +"Why would you want to do this? Maybe you have only one IT guy, and all " +"system monitoring issues should be automatically assigned to him. Or, maybe " +"you're creating multiple notification rules so that database outages take " +"higher priority than disk space warnings." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:22 -msgid "🕵️ **ALWAYS verify certificates in-person or over the phone!**" +#: ../system/integrations/checkmk/api-reference.rst:135 +msgid "In most cases, you'll probably want to set one of the following:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:24 -msgid "" -"The whole point of signatures is to alert you when someone is trying to " -"pretend to be someone they're not. Never accept a certificate from someone " -"online without verifying it first." +#: ../system/integrations/checkmk/api-reference.rst:137 +msgid "group" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:28 -msgid "📇 **What about trusted certificate authorities?**" +#: ../system/integrations/checkmk/api-reference.rst:139 +msgid "state" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:30 -msgid "" -"In some cases (e.g. when dealing with large enterprises), you may be given a " -"certificate for an entire CA, rather than a single contact. Add it here to " -"trust *all* certificates issued by that CA." +#: ../system/integrations/checkmk/api-reference.rst:140 +msgid "priority" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:35 +#: ../system/integrations/checkmk/api-reference.rst:142 msgid "" -"Commercial CAs can usually be verified online. Zammad does not include a " -"list of built-in, trusted CAs." +"but in practice, you can set almost any attribute, including :doc:`custom " +"ones you created through the Object Manager `." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:57 -msgid "Add Private Key" +#: ../system/integrations/checkmk/api-reference.rst:145 +msgid "Please note that the following attributes are **not customizable**:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:39 -msgid "" -"Once you've added a public-key certificate, you can import its matching " -"private key." +#: ../system/integrations/checkmk/api-reference.rst:147 +msgid "title" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:42 -msgid "" -"Private keys are for **your own organization only**; never ask your contacts " -"for their private keys." +#: ../system/integrations/checkmk/api-reference.rst:148 +msgid "id" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:0 -msgid "" -"S/MIME integration showing configured certificates and possible issues with " -"Logging" +#: ../system/integrations/checkmk/api-reference.rst:149 +msgid "ticket number" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:50 -msgid "" -"A note is displayed on certificates with a matching private key (see line 2)." +#: ../system/integrations/checkmk/api-reference.rst:151 +msgid "created_by_id" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:52 -msgid "📤 **Certificates and private keys must be uploaded separately.**" +#: ../system/integrations/checkmk/api-reference.rst:152 +msgid "updated_by_id" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:54 -msgid "" -"If your certificate and private key are bundled together in the same file or " -"PEM block, import it twice (once using each button)." -msgstr "" - -#: ../system/integrations/smime/manage-certificates.rst:57 -msgid "Please note that bulk imports of private keys are not possible." +#: ../system/integrations/checkmk/api-reference.rst:155 +msgid "Which Values Can Be Set?" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:60 -msgid "Download Certificate Data" +#: ../system/integrations/checkmk/api-reference.rst:157 +msgid "😵 **Invalid values → unpredictable behavior**" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:62 +#: ../system/integrations/checkmk/api-reference.rst:159 msgid "" -"You can download the earlier provided certificates and private keys at any " -"time from your Zammad instance." +"If you provide a value that Zammad doesn't understand (*e.g.,* ``-F " +"\"priority=high\"``), it's not always clear what will happen. In some cases, " +"a ticket will be created with the default values instead - but in others, it " +"may not be created at all!" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:65 -msgid "" -"Please note that passphrase-protected private keys stay protected and when " -"you download them, you have to know the passphrase to use them after " -"downloading." +#: ../system/integrations/checkmk/api-reference.rst:164 +msgid "So what values does Zammad understand, then? Well, it depends..." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:73 -msgid "Dialogue to download certificates or private keys" +#: ../system/integrations/checkmk/api-reference.rst:168 +msgid "Use an email address or username:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:73 -msgid "Download stored certificates and their keys" +#: ../system/integrations/checkmk/api-reference.rst:190 +msgid "group & priority" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:78 -msgid "" -"The ticket composer will set all outgoing messages to **signed and " -"encrypted** by default (assuming the required certificates exist)." +#: ../system/integrations/checkmk/api-reference.rst:175 +msgid "Refer to the dropdown menus in the ticket pane:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:82 -msgid "These defaults can be modified on a per-group basis:" +#: ../system/integrations/checkmk/api-reference.rst:0 +msgid "See possible values for certain attributes in the ticket pane." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:None -msgid "Zammad allowing to choose the default behavior on per group basis" +#: ../system/integrations/checkmk/api-reference.rst:187 +msgid "🙅 **Ticket state CANNOT be set this way!**" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:89 +#: ../system/integrations/checkmk/api-reference.rst:189 msgid "" -"Of course, agents can always manually change these settings on each email " -"they send out." +"Why? Because ``-F \"state=...\"`` is already used :ref:`as a Checkmk " +"parameter `." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:4 -msgid "A certificate *and* private key for your own organization" +#: ../system/integrations/checkmk/api-reference.rst:222 +msgid "Everything Else" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:6 +#: ../system/integrations/checkmk/api-reference.rst:193 msgid "" -"(Use this to ✒️ **sign outgoing messages** and 🔓 **decrypt incoming " -"messages**.)" +"To set any other attributes, it helps to know your way around the :docs:" +"`rails console `. Valid values are those that you can " +"set with a string:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:9 -msgid "" -"Certificates belonging your contacts, or their issuing certificate authority " -"(CA)" +#: ../system/integrations/checkmk/api-reference.rst:218 +msgid "These values can then be passed directly to the API:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:11 -msgid "" -"(Use these to ✅ **verify incoming message signatures** and 🔒 **encrypt " -"outgoing messages**.)" +#: ../system/integrations/checkmk/index.rst:16 +msgid "How does it work?" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:14 -msgid "🙋 **I'm new to S/MIME. Where can I get a certificate?**" +#: ../system/integrations/checkmk/index.rst:2 +msgid "Checkmk" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:16 +#: ../system/integrations/checkmk/index.rst:4 msgid "" -"The easiest way to get certificates is to buy an annual subscription through " -"a commercial CA, such as:" +"`Checkmk `_ is a powerful IT monitoring tool that can " +"send real-time status alerts to Zammad via email or REST API. Set these " +"alerts up in Checkmk, and Zammad will automatically create, update, and " +"close tickets based on the health of your system:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:19 -msgid "" -"`Sectigo (formerly Comodo) `_" +#: ../system/integrations/checkmk/index.rst:14 +msgid "Screenshot of ticket created by Checkmk notifications" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:20 -msgid "`Secorio `_" +#: ../system/integrations/checkmk/index.rst:14 +msgid "Multiple alerts, same ticket." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:21 -msgid "`GlobalSign `_" +#: ../system/integrations/checkmk/setup-guide.rst:2 +msgid "Setup Guide" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:23 -msgid "(Zammad is not affiliated with these CAs in any way.)" +#: ../system/integrations/checkmk/setup-guide.rst:4 +msgid "" +"Whenever the Checkmk integration is enabled, Zammad listens for messages on " +"its API and over email. As long as those messages follow the required " +"format, Zammad will create new tickets (or find and update existing ones) " +"based on the message contents." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:25 +#: ../system/integrations/checkmk/setup-guide.rst:10 msgid "" -"You can also generate your own self-signed certificates, but the process is " -"complicated and usually 🙅 **involves extra work for your contacts**." +"That means that “setting up Checkmk integration” is simply a matter of " +"**adding configuration to your Checkmk site**: telling it when to send these " +"messages and what to say. To do that, you'll need to create a new " +"**notification rule** (see `Checkmk's official docs `_ for help with that)." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:29 +#: ../system/integrations/checkmk/setup-guide.rst:17 msgid "" -"Bear in mind that 🤝 **S/MIME only works if the other party is using it, too." -"**" +"As part of this new rule, you'll have to choose a **notification method** " +"(*i.e.,* a script to execute whenever the rule is triggered). This script " +"will be written by you (samples below), and contain the logic for sending " +"API/email messages to Zammad:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:32 -msgid "Certificate and Private Key Checks on Upload" +#: ../system/integrations/checkmk/setup-guide.rst:26 +msgid "Checkmk \"New Rule\" dialog" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:34 +#: ../system/integrations/checkmk/setup-guide.rst:26 msgid "" -"The certificate and public key validation is based on the ``X509v3`` " -"extensions." +"Find your custom scripts in the Checkmk WATO under **Notifications > New " +"Rule > Notification Method**." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:49 -msgid "Uploading a *client certificate*?" +#: ../system/integrations/checkmk/setup-guide.rst:29 +msgid "" +"Once you're done setting up your new rule, you're all set! New tickets " +"should start coming in and auto-updating any time your rule is triggered." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:41 -msgid "The following attributes are required then:" +#: ../system/integrations/checkmk/setup-guide.rst:33 +msgid "" +"(If you need help troubleshooting, be sure to check the :ref:`checkmk-recent-" +"logs`.)" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:39 -msgid "Subject Alternative Name (at least one email address has to be present)" +#: ../system/integrations/checkmk/setup-guide.rst:38 +msgid "API Alerts" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:40 -msgid "Key Usage (``Digital Signature`` and/or ``Key Encipherment``)" +#: ../system/integrations/checkmk/setup-guide.rst:40 +msgid "" +"To add these scripts in the Checkmk WATO, copy them into your Checkmk " +"installation directory and make them executable. (Be sure to replace the " +"``zammad.example.com`` callback URL with the one found in your admin panel.)" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:41 -msgid "Public key algorithm (either ``RSA`` or ``EC``)" +#: ../system/integrations/checkmk/setup-guide.rst:60 +msgid "Service notification" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:43 +#: ../system/integrations/checkmk/setup-guide.rst:46 msgid "" -"The Extended Key Usage attribute is optional. If the certificate provides " -"the named attribute, than it must contain the value ``E-mail Protection``." +"For updates on the status of the software running on your server (*e.g.,* " +"postgres)." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:46 -msgid "" -"Please note that any usable email adress has to be prefixed with ``email:`` " -"or ``rfc822:``." +#: ../system/integrations/checkmk/setup-guide.rst:75 +msgid "Host notification" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:49 -msgid "The named public key algorithms are mandatory for private keys as well." +#: ../system/integrations/checkmk/setup-guide.rst:63 +msgid "For updates on the status of the server itself." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:54 -msgid "Uploading a *CA certificate*?" +#: ../system/integrations/checkmk/setup-guide.rst:77 +msgid "🤔 **What's with all the env vars?**" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:52 +#: ../system/integrations/checkmk/setup-guide.rst:79 msgid "" -"In the case of an uploaded CA certificate, providing the value ``CA:TRUE`` " -"in the attribute *Basic Contstraints*, the previously mentioned attributes " -"are not verified." +"Whenever Checkmk runs these scripts, it needs to provide some information " +"about the event that triggered the notification. This information is passed " +"in the form of these ``$NOTIFY_*`` environment variables." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:56 +#: ../system/integrations/checkmk/setup-guide.rst:85 msgid "" -"In general, the usage of any expired (``Not After``) or not yet valid (``Not " -"Before``) certificate is denied for outgoing emails." +"You can specify additional parameters to pass to the script when you're " +"setting up your notification rule, but the ones you see here are all " +"provided by default." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:59 -msgid "Example certificate:" +#: ../system/integrations/checkmk/setup-guide.rst:90 +msgid "Email Alerts" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:85 +#: ../system/integrations/checkmk/setup-guide.rst:94 msgid "" -"Please note that Zammad will distrust senders by default. This means that " -"you're always required to provide certificate data, no matter if for signing " -"or encrypting." +"🐞 **There are known bugs** in Zammad's processing of email from Checkmk. " +"This section will be completed once they have been resolved. (Learn more at " +"GitHub issues `#2377 `_ & " +"`#2180 `_.)" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:89 -msgid "This is by design and can't be adjusted." +#: ../system/integrations/checkmk/setup-guide.rst:100 +msgid "In the meantime, we encourage you to set up API alerts instead." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:4 -msgid "" -"All of the system's latest S/MIME activity is displayed in the **Recent " -"Logs** section." +#: ../system/integrations/clearbit.rst:2 +msgid "Clearbit" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:11 -msgid "Sample entries of in- and outgoing S/MIME related emails." +#: ../system/integrations/clearbit.rst:4 +msgid "" +"With our Clearbit integration, you can easily enrich the information " +"provided by Zammad. If the customers or agents email address is known to " +"Clearbit, it will share all information it has regarding the user with " +"Zammad. Those information can include the following:" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:11 -msgid "" -"Logs report the status and details of all mail, both incoming and outgoing, " -"that used signing/verification or encryption/decryption." +#: ../system/integrations/clearbit.rst:9 +msgid "Avatar" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:14 -msgid "" -"This log does **not** include email sent by :doc:`triggers ` or the :doc:`scheduler `. For those, check your " -"``production.log``." +#: ../system/integrations/clearbit.rst:10 +msgid "Address information" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:20 -msgid "Common Issues" +#: ../system/integrations/clearbit.rst:11 +msgid "Website information" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:30 -msgid "I received a signed/encrypted email before I set up S/MIME integration" +#: ../system/integrations/clearbit.rst:12 +msgid "A BIO (as Note by default)" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:23 +#: ../system/integrations/clearbit.rst:14 msgid "" -"No problem. Once S/MIME has been enabled and the appropriate certificates " -"have been added, agents will be prompted to retry verification/decryption on " -"matching emails." +"If needed, you can add further custom objects and add mappings to them, so " +"the Clearbit information can be filled within the database. In general you " +"can get any information from Clearbit, as long as you have a mapping to an " +"Zammad object." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:0 -msgid "Screenshot of user prompt to retry decryption" +#: ../system/integrations/clearbit.rst:21 +msgid "" +"Clearbit does have a mapping of fields like LDAP and Exchange have, but does " +"not \"win\" against Zammad information. This means that if you have e.g. the " +"last name field filled in already and Clearbit has other information on " +"that, it will not be updated." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:38 -msgid "The 🔒 **Encrypt** button is disabled" +#: ../system/integrations/clearbit.rst:26 +msgid "" +"However: If let's say the last name has been set by Clearbit and Zammad " +"notices that the last name on the Clearbit source has changed, Zammad will " +"also update this value." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:33 -msgid "Have you added the recipient's certificate?" +#: ../system/integrations/clearbit.rst:33 +msgid "" +"The configuration of Clearbit is really easy and done fast! Just login to " +"your Clearbit-Account, go to \"API\" and copy the secret-API-Key." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:34 -msgid "Are you sure the recipient's certificate is valid?" +#: ../system/integrations/clearbit.rst:38 +msgid "" +"Now change to your Zammad instance, go to Integrations (System) -> Clearbit " +"in the admin panel. Paste your API-Key into the API-Key-Field and decide if " +"Zammad should create unknown Organizations automatically, if the user does " +"not have one yet (and Clearbit knows it). The shared option decides if the " +"new organizations Zammad creates with Clearbit should be shared ones." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:35 -msgid "Have you checked your ``production.log`` for more details?" +#: ../system/integrations/clearbit.rst:47 +msgid "" +"If you're unsure what option to choose, better stick with \"no\". You can " +"also learn more about :doc:`/manage/organizations/index`." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:37 +#: ../system/integrations/clearbit.rst:52 msgid "" -"If encryption doesn't work in the composer, it won't work in :doc:`triggers " -"` or the :doc:`scheduler ` either!" +"The Mapping option works similar to the mapping within the Exchange and LDAP " +"sync. You can add further mappings for e.g. custom fields if you need more " +"information that Clearbit can provide." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:42 -msgid "The ✅ **Sign** button is disabled" +#: ../system/integrations/clearbit.rst:58 +msgid "" +"If you want to add more Clearbit fields and want to learn more about " +"available fields on their API, you can take a look at their `API " +"documentation `_." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:41 +#: ../system/integrations/clearbit.rst:62 msgid "" -"Have you added **both the certificate and private key** for your " -"organization?" +"If you're happy with the above chosen Settings and your mapping, just save " +"the changes and enable Clearbit integration. Zammad will now start polling " +"the Clearbit API as users contact you." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:42 +#: ../system/integrations/clearbit.rst:68 msgid "" -"Does the email address on the certificate match the email address of the " -"agent/group composing the email?" +"Zammad does not synchronize with Clearbit on a regular basis, but on demand " +"if needed. This saves API calls." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:45 -msgid "Error: “Fingerprint already taken”" +#: ../system/integrations/clearbit.rst:73 +msgid "" +"Below the Settings and Mappings, you'll find our Integration log. You can " +"see what requests Zammad sent to Clearbit and also the APIs Response." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:45 -msgid "Are you sure you haven't added this certificate already?" +#: ../system/integrations/clearbit.rst:78 +msgid "" +"By the way, you can also view the API log on the Clearbit website - the " +"information seen is basically the same." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:48 -msgid "Error: “❌ invalid byte sequence in UTF-8”" +#: ../system/integrations/clearbit.rst:84 +msgid "Example When Adding a User" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:48 -msgid "Please ensure to provide PEM formatted certificate and keys." +#: ../system/integrations/clearbit.rst:86 +msgid "" +"To show you how fast information is added, we added a small Screencast " +"below. This shows the creation of the User Alex from Clearbit. As we already " +"set the last name of Alex to \"X\", Zammad did not update it. What Zammad " +"did was to add further information it received from Clearbit." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:49 -msgid "Did you check if the provided file is a valid certificate or key?" +#: ../system/integrations/cti/generic.rst:2 +msgid "CTI (generic)" msgstr "" -#: ../system/integrations/zabbix.rst:2 -msgid "Zabbix Integration" +#: ../system/integrations/cti/includes/introduction.include.rst:1 +msgid "" +"This integration enables Zammad to provide a caller log to your agents. With " +"this your agents can greet your customers by their name and are supported by " +"Zammad with automatically opening a new ticket dialog or the user profile." msgstr "" -#: ../system/integrations/zabbix.rst:5 +#: ../system/integrations/cti/includes/introduction.include.rst:6 msgid "" -"This guide describes how to integrate your Zabbix 5.4 installation with " -"Zammad using the Zabbix webhook feature. This guide will provide " -"instructions on setting up a media type, a user and an action in Zabbix." +"Click the toggle next to the heading to activate or deactivate this " +"integration." msgstr "" -#: ../system/integrations/zabbix.rst:12 -msgid "Zammad with enabled HTTP Token Authentication" +#: ../system/integrations/cti/includes/introduction.include.rst:9 +msgid "" +"If you want to learn more on how your agents can use this function, please " +"refer the :user-docs:`user documentation `." msgstr "" -#: ../system/integrations/zabbix.rst:13 -msgid "Zabbix version 5.4 or higher" +#: ../system/integrations/cti/includes/introduction.include.rst:14 +msgid "" +"Automatically opening new ticket dialogues or user profiles requires agent " +"to extension mapping - see more below." msgstr "" -#: ../system/integrations/zabbix.rst:16 -msgid "Setting up a Zammad" +#: ../system/integrations/cti/includes/introduction.include.rst:20 +msgid "Please note the following limitations to reduce confusion later on:" msgstr "" -#: ../system/integrations/zabbix.rst:18 -msgid "Enable **API Token Access** in Settings > System > API." +#: ../system/integrations/cti/includes/introduction.include.rst:22 +msgid "CTI integrations provide caller log functions only." msgstr "" -#: ../system/integrations/zabbix.rst:20 +#: ../system/integrations/cti/includes/introduction.include.rst:23 msgid "" -"Create a **new user** for a Zabbix alerter with an **email address** and " -"create a personal user token with **ticket.agent** permissions." +"This integration does not provide any VoIP functionalities; you can't make " +"phone calls from within Zammad." msgstr "" -#: ../system/integrations/zabbix.rst:24 -msgid "Zabbix Webhook Configuration" +#: ../system/integrations/cti/includes/introduction.include.rst:25 +msgid "" +"If your browser supports ``tel``-URLs, you can click on phone numbers for " +"automatic dialing. This requires additional software / configuration on your " +"agent's computers." msgstr "" -#: ../system/integrations/zabbix.rst:27 -msgid "Create a Global Macro" +#: ../system/integrations/cti/generic.rst:9 +#: ../system/integrations/cti/placetel.rst:14 +#: ../system/integrations/cti/sipgate.rst:14 +msgid "Please provide the following requirements:" msgstr "" -#: ../system/integrations/zabbix.rst:29 +#: ../system/integrations/cti/generic.rst:11 msgid "" -"Before setting up the **Webhook**, you need to setup the global macro " -"**{$ZABBIX.URL}**, which must contain the **URL** to the **Zabbix frontend**." +"A telephone system that supports webhooks (outbound) (best option are those " +"that allow customizing the calls)." msgstr "" -#: ../system/integrations/zabbix.rst:33 -msgid "" -"In the **Administration** > **Media types** section, import the `Template`_." +#: ../system/integrations/cti/generic.rst:13 +msgid "A unique Call-ID during the call session." msgstr "" -#: ../system/integrations/zabbix.rst:38 -msgid "Open the added **Zammad** media type and set:" +#: ../system/integrations/cti/generic.rst:14 +msgid "Call event data (both numbers and direction)." msgstr "" -#: ../system/integrations/zabbix.rst:40 -msgid "**zammad\\_access\\_token** to the your **Personal User Token**" +#: ../system/integrations/cti/generic.rst:15 +msgid "Your Zammad instance must be reachable for your telephony system." msgstr "" -#: ../system/integrations/zabbix.rst:41 +#: ../system/integrations/cti/generic.rst:17 msgid "" -"**zammad\\_url** to the **frontend URL** of your **Zammad** installation" +"If you want to learn more on what kind of requests are supported by Zammad " +"and what it expects, please consult our :docs:`CTI-API documentation `." msgstr "" -#: ../system/integrations/zabbix.rst:43 -msgid "**zammad\\_customer** to your **Zammad user email**." +#: ../system/integrations/cti/generic.rst:22 +#: ../system/integrations/cti/placetel.rst:27 +#: ../system/integrations/cti/sipgate.rst:30 +msgid "Available Settings" msgstr "" -#: ../system/integrations/zabbix.rst:44 -msgid "" -"**zammad\\_enable\\_tags** to **true** or **false** to enable or disable " -"trigger tags. **Important**: if you enable tag support, each tag is set with " -"a separate request." +#: ../system/integrations/cti/generic.rst:29 +#: ../system/integrations/cti/placetel.rst:41 +#: ../system/integrations/cti/sipgate.rst:40 +msgid "Endpoint Settings" msgstr "" -#: ../system/integrations/zabbix.rst:48 +#: ../system/integrations/cti/generic.rst:25 msgid "" -"If you want to prioritize issues according to **severity** values in Zabbix, " -"you can define mapping parameters:" -msgstr "" - -#: ../system/integrations/zabbix.rst:51 -msgid "**severity\\_**: Zammad priority ID" -msgstr "" - -#: ../system/integrations/zabbix.rst:53 -msgid "Click the **Update** button to save the **Webhook** settings." +"Zammad will list your generic CTI endpoint here. It contains a unique token " +"so ensure to keep this URL save." msgstr "" -#: ../system/integrations/zabbix.rst:55 +#: ../system/integrations/cti/generic.rst:28 msgid "" -"To receive notifications in **Zammad**, you need to create a **Zabbix user** " -"and add **Media** with the **Zammad** type." +"You'll need this endpoint for your PBX to talk to Zammad, see :docs:`CTI-API " +"documentation `." msgstr "" -#: ../system/integrations/zabbix.rst:58 +#: ../system/integrations/cti/includes/important-dont-forget-saving.include.rst:3 msgid "" -"For **Send to**: enter any text, as this value is not used, but is required." +"All following options **do not save automatically**. Always use the Save " +"button on the lower end of the integration page!" msgstr "" -#: ../system/integrations/zabbix.rst:61 -msgid "" -"For more information, use the `Zabbix documentation `_." +#: ../system/integrations/cti/generic.rst:43 +#: ../system/integrations/cti/placetel.rst:49 +#: ../system/integrations/cti/sipgate.rst:52 +msgid "Call Settings" msgstr "" -#: ../system/maintenance.rst:2 -msgid "Maintenance" +#: ../system/integrations/cti/generic.rst:39 +#: ../system/integrations/cti/placetel.rst:49 +#: ../system/integrations/cti/sipgate.rst:37 +#: ../system/integrations/cti/sipgate.rst:50 +msgid "Inbound" msgstr "" -#: ../system/maintenance.rst:4 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:1 msgid "" -"Zammad comes with a maintenance mode that you can use for e.g. updating the " -"instance or changing settings while restricting availability and functions." +"This option allows you to block specific incoming caller IDs. It allows you " +"to temporarily reject e.g. spam callers without having to contact providers " +"or PBX administrators." msgstr "" -#: ../system/maintenance.rst:13 -msgid "Mode" +#: ../system/integrations/cti/includes/inbound-calls.include.rst:11 +msgid "Caller ID to block" msgstr "" -#: ../system/maintenance.rst:8 -msgid "The mode setting allows you to enable or disable the maintenance mode." +#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 +msgid "Provide caller IDs to block in ``E.164`` format." msgstr "" -#: ../system/maintenance.rst:10 -msgid "Defaults to *off*." +#: ../system/integrations/cti/includes/inbound-calls.include.rst:8 +msgid "" +"Your telephony system has to support this function. Zammad will send a " +"``reject`` response which will cause your telephony system to hang up the " +"call. To callers this usually will feel like the line is busy." msgstr "" -#: ../system/maintenance.rst:12 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:14 msgid "" -"The maintenance mode will restrict access to administrative roles only. This " -"means agents and customers are logged off." -msgstr "" - -#: ../system/maintenance.rst:23 -msgid "@Login" -msgstr "" - -#: ../system/maintenance.rst:16 -msgid "" -"This setting allows you to provide a login message within a green banner " -"above the login screen. Click into the green banner in the settings page to " -"adjust your message. To activate the message, activate the *@Login* setting." -msgstr "" - -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing the default login message within the\n" -"settings page" -msgstr "" - -#: ../system/maintenance.rst:26 -msgid "" -"Send an informative message to **all active sessions**. This comes handy to " -"inform your agents e.g. about mayor outages or to force reloads after " -"configuration changes." -msgstr "" - -#: ../system/maintenance.rst:31 -msgid "This is the messages title (slightly bigger than the normal message)." -msgstr "" - -#: ../system/maintenance.rst:34 -msgid "The text you want to provide to your logged in sessions." -msgstr "" - -#: ../system/maintenance.rst:39 -msgid "Reload application" -msgstr "" - -#: ../system/maintenance.rst:37 -msgid "" -"Selecting this option will change the message acceptance button from *Close* " -"(with nothing happening) to *Continue session*, which forces the application " -"to reload." -msgstr "" - -#: ../system/maintenance.rst:43 -msgid "" -"If you have customers that are logged in to Zammad, they'll also be notified " -"if they're active in that moment." -msgstr "" - -#: ../system/maintenance.rst:48 -msgid "Example without reload application" +"Provide a meaningful note for your fellow administrators to remind yourself " +"why you've chosen to block the number." msgstr "" -#: ../system/maintenance.rst:52 -msgid "" -"Message setting within Zammad's admin settings without ticket reload " -"application setting." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:17 +#: ../system/integrations/cti/sipgate.rst:40 +msgid "Outbound" msgstr "" -#: ../system/maintenance.rst:0 +#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:1 msgid "" -"Screenshot showing the send message settings without ticket\n" -"reload application set" +"In many cases you may want to use a different caller ID depending on the " +"destination you're calling. This may apply due to specific connection rates " +"to other countries or because you want your customer to feel you're calling " +"from the same country." msgstr "" -#: ../system/maintenance.rst:61 ../system/maintenance.rst:85 -msgid "" -"The modal all other active sessions will see upon pressing *Send to clients*." +#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:6 +msgid "This option expects ``E.164`` number formats." msgstr "" -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing modal caused by maintenance's message\n" -"without reload application ticket" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 +msgid "Destination caller ID" msgstr "" -#: ../system/maintenance.rst:72 -msgid "Example with reload application" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:5 +msgid "The caller ID or number you're trying to call." msgstr "" -#: ../system/maintenance.rst:76 -msgid "" -"Message setting within Zammad's admin settings with ticket reload " -"application setting." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:7 +msgid "You can use wildcards for e.g. country specific outbound numbers like:" msgstr "" -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing the send message settings with ticket\n" -"reload application set" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:9 +msgid "``49*`` for Germany" msgstr "" -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing modal caused by maintenance's message\n" -"with reload application ticket" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:10 +msgid "``4930*`` for Berlin / Germany landlines" msgstr "" -#: ../system/monitoring.rst:2 -msgid "Monitoring" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 +msgid "``33*`` for France" msgstr "" -#: ../system/monitoring.rst:4 -msgid "" -"This function is only available in self hosted instances. If you use Zammad " -"in our cloud, we are monitoring the system on our own and take steps to fix " -"potential problems directly." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:15 +msgid "Set Outbound caller ID" msgstr "" -#: ../system/monitoring.rst:11 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:14 msgid "" -"On the monitoring page, you can see the current health state of Zammad under " -"\"*Current Status*\" at the bottom. This can be useful if you want to have a " -"look if everything is up and running. As an example, you could have a look " -"in the monitoring when you assume that some emails aren't processed from " -"Zammad." +"The outbound caller ID to set (the number your customer sees on his display) " +"in ``E.164`` number format." msgstr "" -#: ../system/monitoring.rst:17 -msgid "**Can't receive an email and the monitoring response is \"healthy\"?**" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 +msgid "Provide a short description for fellow administrators." msgstr "" -#: ../system/monitoring.rst:19 +#: ../system/integrations/cti/includes/generic-cti-support-note.includes.rst:3 msgid "" -"Zammad will just inform you about unprocessable emails. This is not the case " -"for oversized emails. You can adjust the maximum email size in :doc:`../" -"channels/email/settings`." +"This option requires your PBX to send a specific request to Zammad *before " +"dialing*. Please consult the :docs:`CTI API ` in case " +"you're not sure." msgstr "" -#: ../system/monitoring.rst:24 -msgid "Monitoring API" +#: ../system/integrations/cti/generic.rst:52 +#: ../system/integrations/cti/placetel.rst:54 +#: ../system/integrations/cti/sipgate.rst:59 +msgid "Other Settings" msgstr "" -#: ../system/monitoring.rst:26 +#: ../system/integrations/cti/includes/other-settings-intro.include.rst:1 msgid "" -"Beside the indication in the monitoring page, you can also use an external " -"monitoring tool to monitor Zammad's health. To request the health of Zammad, " -"you need to provide the API key (token) to the external monitoring tool. You " -"can copy the token from the \"*Current Token*\" field as well as the whole " -"API endpoint of your system (\"*Health Check*\" field), in which the API " -"token is already included." +"Below you can find all available additional settings for this CTI " +"integration. For your overview we're sorting them by appearance and " +"reference their description first." msgstr "" -#: ../system/monitoring.rst:37 -msgid "Screenshot showing Current Token and Health Check" +#: ../system/integrations/cti/includes/default-caller-id.include.rst:2 +#: ../system/integrations/cti/includes/default-caller-id.include.rst:1 +msgid "Default caller ID for outbound calls" msgstr "" -#: ../system/monitoring.rst:37 -msgid "Screenshot showing Token and Health Check" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:16 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:15 +msgid "Shown records in caller log" msgstr "" -#: ../system/monitoring.rst:39 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:2 msgid "" -"In addition to that, you can reset the auto-generated token to make sure " -"that already configured monitoring systems won't work anymore. So, please " -"use this \"*Reset*\" button only if you know what you do!" -msgstr "" - -#: ../system/monitoring.rst:44 -msgid "Example Output" -msgstr "" - -#: ../system/monitoring.rst:0 -msgid "No issues found" -msgstr "" - -#: ../system/monitoring.rst:48 ../system/monitoring.rst:60 -msgid "**Indicator in Zammad**:" -msgstr "" - -#: ../system/monitoring.rst:0 -msgid "Screenshot showing monitoring with no issues" -msgstr "" - -#: ../system/monitoring.rst:54 ../system/monitoring.rst:66 -msgid "**API response**::" -msgstr "" - -#: ../system/monitoring.rst:0 -msgid "Issues were found" -msgstr "" - -#: ../system/monitoring.rst:0 -msgid "Screenshot showing monitoring with issues" -msgstr "" - -#: ../system/objects.rst:2 -msgid "Objects" +"Allows you to set the number of shown caller log entries for all users. You " +"can choose from the following values:" msgstr "" -#: ../system/objects.rst:4 -msgid "" -"In Zammad you can add your own fields to tickets, users, organizations and " -"even groups (these are called \"objects\"). This can be useful if you need " -"to add further information to a ticket or any other object in Zammad and the " -"information doesn't fit in any existing field." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:5 +msgid "60 (default)" msgstr "" -#: ../system/objects.rst:11 -msgid "" -"Try to avoid deleting attributes (and disable them instead) as Zammad might " -"run into unexpected conditions if they are referenced somewhere." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:6 +msgid "120" msgstr "" -#: ../system/objects.rst:16 -msgid "" -"Here's an overview of object attributes. On the upper right you can add new " -"attributes. By default, there will be no custom fields - standard attributes " -"will be grayed out, you can't delete or change those. You can edit custom " -"attributes (they are displayed in black font and have a trash bin on the " -"right side) just by clicking on them." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:7 +msgid "180" msgstr "" -#: ../system/objects.rst:24 -msgid "" -"Attributes you add to Zammad, no matter if they have default values or not, " -"will not update existing information. This means a new ticket field " -"technically will be empty unless you populate it." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:8 +msgid "240" msgstr "" -#: ../system/objects.rst:28 -msgid "" -"Especially in ticket scope this also means that newly added attributes will " -"be indicated as \"changed\" to agents that view the ticket. This may " -"interfere with Zammad's tabs behavior." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:9 +msgid "300" msgstr "" -#: ../system/objects.rst:40 -msgid "Ordering Attributes" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:11 +msgid "**🥵 Potential performance issue**" msgstr "" -#: ../system/objects.rst:42 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:13 msgid "" -"Since Zammad introduced :doc:`/system/core-workflows` the need to have a " -"custom positioning for attributes has become more important than ever." +"Setting this setting higher than 60 may cause serious performance issues on " +"very busy instances. Keep in mind that this setting causes Zammad to poll " +"and send up to 300 records to *all active agent sessions* in very short time " +"periods." msgstr "" -#: ../system/objects.rst:45 -msgid "" -"To adjust the position of such an attribute, simply click on the attribute " -"entry in question, scroll down and adjust the position number. Please note " -"that you cannot change the positioning of default attributes." +#: ../system/integrations/cti/generic.rst:73 +msgid "Caller Log Filter" msgstr "" -#: ../system/objects.rst:49 +#: ../system/integrations/cti/generic.rst:55 msgid "" -"In case two attributes have the same position value, Zammad will sort " -"alphabetically by name automatically." +"This function allows you to provide call information based on e.g. queues " +"only to agents that really need the information." msgstr "" -#: ../system/objects.rst:None +#: ../system/integrations/cti/generic.rst:58 msgid "" -"Screenshot showing custom attribute entries ordered in between default ones" +"Why? If you have a team for several countries or departments, you don't want " +"to bug your agents from other departments. Leaving these options empty will " +"fallback to showing everything to everyone." msgstr "" -#: ../system/objects.rst:56 -msgid "Updating Database After Adding or Editing Attributes" +#: ../system/integrations/cti/generic.rst:64 +msgid "Destination caller ID or Queue" msgstr "" -#: ../system/objects.rst:58 +#: ../system/integrations/cti/generic.rst:63 msgid "" -"When adding or changing attributes, Zammad will not apply the changes " -"instantly, but instead shows you the changed attributes first. If you're " -"ready to go, just click on \"Update database\" to apply the changes to " -"Zammad. If you made a mistake or just want to discard your changes, click " -"\"Discard changes\"." +"This depends on your PBX and usually is either a queue ID, phone number or " +"extension." msgstr "" -#: ../system/objects.rst:64 -msgid "" -"After applying the changes with \"Update Database\", a restart of Zammad is " -"**mandatory**. If you don't perform it, you may experience unexpected " -"behavior or even errors. You may want to do this kind of configuration " -"during maintenance windows." +#: ../system/integrations/cti/generic.rst:69 +msgid "Agents" msgstr "" -#: ../system/objects.rst:72 +#: ../system/integrations/cti/generic.rst:67 msgid "" -"Changes on objects require you to update the database to apply these changes." +"Select the agents that are responsible for the group. These agents will then " +"see caller log entries and call notifications fitting to said queue." msgstr "" -#: ../system/objects.rst:75 -msgid "**🤓 Service restarts can be automated**" +#: ../system/integrations/cti/generic.rst:0 +msgid "" +"Screenshot showing the caller log filter table with pre filled sample data" msgstr "" -#: ../system/objects.rst:0 -msgid "Hosted environments automatically restart for you." +#: ../system/integrations/cti/includes/recent-logs.include.rst:6 +msgid "" +"With recent logs Zammad allows you to view the latest calls for the CTI " +"functionality. This usually comes in handy, when you're looking for errors." msgstr "" -#: ../system/objects.rst:0 +#: ../system/integrations/cti/includes/recent-logs.include.rst:0 msgid "" -"If you're using a self-hosted installation you can use :docs:`environment " -"variables `" +"Screenshot showing several incoming requests within Recent logs section." msgstr "" -#: ../system/objects.rst:82 -msgid "System Attributes" +#: ../system/integrations/cti/includes/recent-logs.include.rst:16 +msgid "I'm just here to clear floats up." msgstr "" -#: ../system/objects.rst:84 +#: ../system/integrations/cti/includes/recent-logs.include.rst:20 msgid "" -"Zammad comes with pre-configured attributes. Some of them can't be edited " -"via UI (or at all). This is required for proper operation of Zammad and not " -"a bug." -msgstr "" - -#: ../system/objects.rst:90 -msgid "Ticket State" +"By clicking on the entry of interest, Zammad will provide more details on " +"the call in question. You'll see the payload it received and also the " +"response that was sent." msgstr "" -#: ../system/objects.rst:92 +#: ../system/integrations/cti/includes/recent-logs.include.rst:0 msgid "" -"If the pre-configured states aren't enough for you or you want to change " -"them, you can do so by clicking on the cogwheel icon in the state row in the " -"ticket tab. But you should be careful when changing pre-configured states. " -"This can lead to unwanted behavior in some cases." +"Screenshot showing detailed information of a specific log entry of recent " +"logs" msgstr "" -#: ../system/objects.rst:None -msgid "Screenshot showing highlighted ticket state attribute" +#: ../system/integrations/cti/includes/recent-logs.include.rst:31 +msgid "x" msgstr "" -#: ../system/objects.rst:122 -msgid "Handling of states" +#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 +#: ../system/integrations/cti/includes/troubleshooting.include.rst:9 +msgid "My Phone page stays blank, signalling does work..." msgstr "" -#: ../system/objects.rst:102 +#: ../system/integrations/cti/includes/troubleshooting.include.rst:5 msgid "" -"In the state configuration screen, you can add new states, disable states or " -"change states." +"If you've made sure that signalling works (check Recent logs) and your " +"Caller Log still stays empty, please ensure that you only configured one CTI " +"integration version. Specifically defining more than one agent mapping on " +"the different integration variants will be the issue." msgstr "" -#: ../system/objects.rst:0 -msgid "Screenshot showing table of default ticket states" +#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 +msgid "Clear the not needed agent mapping and reload your browser page." msgstr "" -#: ../system/objects.rst:110 +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:1 msgid "" -"To add a new state, click on the \"New Ticket State\" button in the top " -"right corner. To change an existing state, simply click on the affected " -"state. This opens an edit dialog." +"By mapping your agents extension to their existing Zammad users, Zammad can " +"provide a new ticket dialog or open the user profile for the agent that " +"picks up the call." msgstr "" -#: ../system/objects.rst:114 +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:5 msgid "" -"You can also clone a state or set them to \"Default for new tickets\" or " -"\"Default for follow-ups\" by clicking on the ⁝ action button and select the " -"desired function." +"This speeds up ticket aiding, no matter if it's for existing tickets or new " +"ones!" msgstr "" -#: ../system/objects.rst:118 +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:8 msgid "" -"*Default for new tickets* means that this state is used for every newly " -"created ticket." +"To see it work from the agent's perspective, have a look on :user-docs:`user " +"documentation `." msgstr "" -#: ../system/objects.rst:121 -msgid "" -"*Default for follow-ups* means that this state is used if the ticket is re-" -"opened after it was closed." +#: ../system/integrations/cti/placetel.rst:2 +msgid "Placetel CTI" msgstr "" -#: ../system/objects.rst:171 -msgid "Ticket state in detail" +#: ../system/integrations/cti/placetel.rst:16 +msgid "You need an administrative Placetel account for your organization." msgstr "" -#: ../system/objects.rst:125 +#: ../system/integrations/cti/placetel.rst:17 +#: ../system/integrations/cti/sipgate.rst:20 msgid "" -"Below you can find a description for each field and option. Please head over " -"to the :ref:`example ` to see the edit dialog." +"Your Zammad instance must be allowed to communicate to external services." msgstr "" -#: ../system/objects.rst:129 -msgid "" -"This is the name of the state and what you and your agents are seeing when " -"choosing a state somewhere (e.g. in tickets, trigger configuration)." +#: ../system/integrations/cti/placetel.rst:18 +msgid "Placetel must be able to reach your Zammad instance." msgstr "" -#: ../system/objects.rst:137 -msgid "" -"There are different state types you can choose from. By default, Zammad " -"comes with one state per state type." +#: ../system/integrations/cti/placetel.rst:22 +msgid ":doc:`provider-configurations/placetel`" msgstr "" -#: ../system/objects.rst:140 +#: ../system/integrations/cti/placetel.rst:21 msgid "" -"**new**: for states for tickets that are new and it hasn't been worked on " -"them" +"Learn how to configure Placetel to enable Zammad and Placetel to communicate " +"with each other." msgstr "" -#: ../system/objects.rst:142 +#: ../system/integrations/cti/placetel.rst:32 msgid "" -"**open**: for states for tickets that are in progress and agents are working " -"on them" -msgstr "" - -#: ../system/objects.rst:144 -msgid "**merged**: for states for tickets that are merged with other tickets" +"The here listed endpoint settings are relevant for the :doc:`integration " +"configuration with Placetel `." msgstr "" -#: ../system/objects.rst:145 -msgid "" -"**pending reminder**: for states for tickets that are in progress and you " -"want to set a reminder. (default example: *pending reminder*)" +#: ../system/integrations/cti/placetel.rst:37 +#: ../system/integrations/i-doit.rst:53 +msgid "Endpoint" msgstr "" -#: ../system/objects.rst:147 +#: ../system/integrations/cti/placetel.rst:36 msgid "" -"**pending action**: for states for tickets that are waiting for a specified " -"time and then change their state (default example: *pending close*)" +"This endpoint will be required for the Zammad integration within the " +"Placetel web interface." msgstr "" -#: ../system/objects.rst:150 -msgid "" -"**closed**: for states for tickets that are finished and do not need to be " -"processed further" +#: ../system/integrations/cti/placetel.rst:41 +msgid "API Token" msgstr "" -#: ../system/objects.rst:153 +#: ../system/integrations/cti/placetel.rst:40 msgid "" -"⚠️ Choosing the correct state type is important! If you are in doubt, have a " -"look on the default states and their types!" +"You'll receive this token within the ``Web API`` menu. Make sure to copy " +"this value, it's only shown once!" msgstr "" -#: ../system/objects.rst:158 -msgid "Ignore escalation" +#: ../system/integrations/cti/placetel.rst:71 +#: ../system/integrations/cti/sipgate.rst:77 +msgid "Phone Extension to Agent Mapping" msgstr "" -#: ../system/objects.rst:157 -msgid "" -"Here you can define whether tickets of this state will count to escalation " -"time or not." +#: ../system/integrations/cti/placetel.rst:0 +msgid "Screenshot showing sample user mappings in between Placetel and Zammad" msgstr "" -#: ../system/objects.rst:161 +#: ../system/integrations/cti/placetel.rst:64 msgid "" -"You can create a note for the state to inform other admins about the state. " -"This has no effect on tickets." +"You can find your agents Placetel username combination required within ⚙️ PBX " +"→ VoIP destinations. Within the \"Advanced settings\" section you're looking " +"for \"SIP user name\" and \"SIP server\"." msgstr "" -#: ../system/objects.rst:165 -msgid "Set the state to *active* or *inactive*." +#: ../system/integrations/cti/placetel.rst:68 +msgid "Combine these two like so: ``@``." msgstr "" -#: ../system/objects.rst:167 -msgid "" -"it is technically possible to set all states to inactive. To keep Zammad " -"working in such a case, the inactive flag of one of the states is ignored." +#: ../system/integrations/cti/placetel.rst:0 +msgid "Sample VoIP credentials for a Placetel user" msgstr "" -#: ../system/objects.rst:194 -msgid "Ticket state example" +#: ../system/integrations/cti/provider-configurations/placetel.rst:2 +msgid "Setup Placetel connection for Zammad" msgstr "" -#: ../system/objects.rst:174 +#: ../system/integrations/cti/provider-configurations/placetel.rst:6 msgid "" -"Let's assume we want to create a new state which indicates that the ticket " -"has to wait for a response of a third party (e.g. service contractor or " -"manufacturer) and we want to to be able to set a reminder." +"This configuration step requires a *full* administrative Placetel account. " +"You may receive forbidden error messages with Placetel in case your " +"permissions are not high enough." msgstr "" -#: ../system/objects.rst:178 +#: ../system/integrations/cti/provider-configurations/placetel.rst:10 msgid "" -"First we give the new state a proper name. In this example we call it " -"\"waiting for manufacturer\"." +"The following actions can be configured via the `Placetel web interface " +"`_." msgstr "" -#: ../system/objects.rst:181 -msgid "" -"As state type we choose \"pending reminder\". This indicates that the ticket " -"is still open and we can set a reminder. This reminder can be useful if our " -"manufacturer sometimes isn't responding or we want to remind him to give us " -"an answer." +#: ../system/integrations/cti/provider-configurations/placetel.rst:29 +msgid "Step 1: Activate Zammad integration" msgstr "" -#: ../system/objects.rst:186 +#: ../system/integrations/cti/provider-configurations/placetel.rst:14 msgid "" -"We choose \"no\" for \"ignore escalation\" because we want to escalate the " -"tickets even if we are waiting on the manufacturer's feedback." -msgstr "" - -#: ../system/objects.rst:189 -msgid "The **result** in the creation dialog will look like this:" +"Within Integrations, scroll down to Partner integrations and select Zammad." msgstr "" -#: ../system/objects.rst:0 -msgid "Screenshot showing ticket state creation dialog with example" +#: ../system/integrations/cti/provider-configurations/placetel.rst:17 +msgid "" +"You can alternatively filter by \"Ticket Systems\" to reduce the number of " +"entries on the page. You'll still want to look for Partner integrations. 🤓" msgstr "" -#: ../system/objects.rst:197 ../system/objects.rst:199 -msgid "Ticket Priority" +#: ../system/integrations/cti/provider-configurations/placetel.rst:21 +msgid "" +"Within the Zammad integration now press \"Activate\". A new tab ``API`` " +"becomes available - open this tab." msgstr "" -#: ../system/objects.rst:199 ../system/objects.rst:201 +#: ../system/integrations/cti/provider-configurations/placetel.rst:24 msgid "" -"If the pre-configured priorities aren't enough for you or you want to change " -"them, you can do so by clicking on the cogwheel icon in the priority row in " -"the ticket tab:" +"Now tick \"Enable Call Control / Notify API\" and paste the Placetel " +"endpoint from your Zammad instance into the field \"URL of your API " +"endpoint\". Save to apply the settings" msgstr "" -#: ../system/objects.rst:None -msgid "Screenshot showing highlighted ticket priority attribute" +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "Screencast showing how to activate the Zammad integration" msgstr "" -#: ../system/objects.rst:224 ../system/objects.rst:226 -msgid "Handling of priorities" +#: ../system/integrations/cti/provider-configurations/placetel.rst:51 +msgid "Step 2: Generate API Token for Placetel" msgstr "" -#: ../system/objects.rst:208 ../system/objects.rst:210 +#: ../system/integrations/cti/provider-configurations/placetel.rst:32 msgid "" -"In the priority configuration screen, you can add new priorities, disable " -"priorities or change priorities." +"Go back to the integrations page and scroll down to \"Web API\". Generate a " +"new API token by using the \"Create a new API token\" button." msgstr "" -#: ../system/objects.rst:0 -msgid "Screenshot showing table of default ticket priorities" +#: ../system/integrations/cti/provider-configurations/placetel.rst:37 +msgid "" +"If you already generated a token either use your existing token or reset it " +"by using above mentioned button. Placetel will ask you to conform this reset." msgstr "" -#: ../system/objects.rst:216 ../system/objects.rst:218 +#: ../system/integrations/cti/provider-configurations/placetel.rst:41 msgid "" -"To add a new priority, click on the \"New Priority\" button in the top right " -"corner. To change an existing priority, simply click on the affected " -"priority. This opens an edit dialog." +"Please keep in mind that existing API scripts may no longer work due to " +"token resets!" msgstr "" -#: ../system/objects.rst:220 ../system/objects.rst:222 +#: ../system/integrations/cti/provider-configurations/placetel.rst:44 msgid "" -"You can also clone a priority or set them to \"Default for new tickets\" by " -"clicking on the ⁝ action button and select the desired function." +"Copy the provided API token and insert it into the \"API Token\" field " +"within Zammad's Placetel integration." msgstr "" -#: ../system/objects.rst:223 ../system/objects.rst:225 +#: ../system/integrations/cti/provider-configurations/placetel.rst:47 msgid "" -"*Default for new tickets* means that this priority is used for every newly " -"created ticket." +"Apply your changes by using the \"Save\" button on the bottom of the " +"Placetel integration page and activate the Placetel integration." msgstr "" -#: ../system/objects.rst:246 ../system/objects.rst:248 -msgid "Priorities in detail" +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "" +"Screencast showing how to retrieve an API token from Placetel for Zammad" msgstr "" -#: ../system/objects.rst:227 ../system/objects.rst:229 -msgid "Below you can find a description for each field and option." +#: ../system/integrations/cti/provider-configurations/placetel.rst:73 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:77 +msgid "Step 3: Restrict the numbers to notify on" msgstr "" -#: ../system/objects.rst:230 ../system/objects.rst:232 +#: ../system/integrations/cti/provider-configurations/placetel.rst:54 msgid "" -"This is the name of the priority and what you and your agents are seeing " -"when choosing a priority somewhere (e.g. in tickets, trigger configuration)." +"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " +"the the Integrations page of the Placetel web interface, go to \"Notify " +"API\"." msgstr "" -#: ../system/objects.rst:240 ../system/objects.rst:242 -msgid "Highlight color" +#: ../system/integrations/cti/provider-configurations/placetel.rst:58 +msgid "" +"Lower on the page Placetel allows you to restrict the numbers to notify on. " +"You'll find this within the \"External routing API\" part." msgstr "" -#: ../system/objects.rst:235 ../system/objects.rst:237 +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 msgid "" -"Switch between *Low priority* (light blue), *High priority* (red) and - " -"(default). This affects the displayed color for ticket titles in overviews." +"Screenshot showing a sample selection of phone numbers to use for the " +"Placetels notify API" msgstr "" -#: ../system/objects.rst:239 ../system/objects.rst:241 -msgid "The color options are currently limited to the mentioned options." +#: ../system/integrations/cti/provider-configurations/placetel.rst:66 +msgid "" +"This menu point also provides a API request log from Placetel view. Just " +"open \"Recent responses of your API endpoint\" to learn more." msgstr "" -#: ../system/objects.rst:243 ../system/objects.rst:245 +#: ../system/integrations/cti/provider-configurations/placetel.rst:69 msgid "" -"You can create a note for the priority to inform other admins about the " -"priority. This has no effect on tickets." +"If you want to see Zammad's perspective, use the \"Recent Logs\" part from " +"within the Placetel integration page." msgstr "" -#: ../system/objects.rst:247 ../system/objects.rst:249 -msgid "Set the priority to *active* or *inactive*." +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "Screenshot showing sample log entries for Placetels API calls to Zammad" msgstr "" -#: ../system/objects/external-data-source-example.rst:2 -msgid "External Data Source" +#: ../system/integrations/cti/provider-configurations/placetel.rst:77 +msgid "Step 4 (optional): Further configurations for Placetel" msgstr "" -#: ../system/objects/external-data-source-example.rst:4 +#: ../system/integrations/cti/provider-configurations/placetel.rst:76 msgid "" -"We assume you already had a look on :doc:`types` where you can find a " -"description of the individual fields." +"If needed, you can now configure Zammad's Placetel integration in more " +"detail. You can learn more about your options here: :ref:`Placetel " +"integration settings `." msgstr "" -#: ../system/objects/external-data-source-example.rst:7 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:2 +msgid "Setup Sipgate connection for Zammad" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"To reproduce this example, choose a category you want to add a custom field, " -"click on *New Attribute* and select *External data source field* under " -"*Format*." +"Sipgate has no english web interface which is why this documentation page is " +"mixing up languages badly." msgstr "" -#: ../system/objects/external-data-source-example.rst:11 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"Our example story is to fetch data from an external product database. We " -"want to add our products to the tickets so that the products can be searched " -"and chosen from a list and also create a link to the product website." +"Please also note that the availability of API addons highly depends on your " +"package trier. Usage of sipgate.io packages *is not free*, please check " +"their `pricing page `_ before!" msgstr "" -#: ../system/objects/external-data-source-example.rst:16 -msgid "Base configuration" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:35 +msgid "Step 1: Book sipgate.io package" msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Initial steps to configure external data source object type" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:13 +msgid "Skip to step 2 if you already have the package booked!" msgstr "" -#: ../system/objects/external-data-source-example.rst:23 -#: ../system/variables.rst:85 -msgid "**Example:**" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:15 +msgid "" +"Login to an administrative Sipgate account and navigate to " +"``Accountverwaltung``. You'll see several different options depending on " +"your booked packages. Select ``Verträge & Produkte`` to continue." msgstr "" -#: ../system/objects/external-data-source-example.rst:25 -msgid "Name: *product*" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:19 +msgid "" +"Scroll down to the section ``Zusätzliche Produkte buchen`` and look for " +"``sipgate.io`` - select this product by using the ``Produkte anzeigen``-" +"Button." msgstr "" -#: ../system/objects/external-data-source-example.rst:26 -msgid "Display: *Product*" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:23 +msgid "" +"On the next page select either one of the ``sipgate.io`` packages or ``Push-" +"API Package Free``. Follow the dialogue by booking the addon. You'll be " +"returned to your contract overview and now should see the selected addon in " +"your list." msgstr "" -#: ../system/objects/external-data-source-example.rst:29 -msgid "External data source configuration" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:30 +msgid "" +"The availability for ``sipgate.io`` packages and their levels highly depends " +"on the overall account type and product you've booked with Sipgate." msgstr "" -#: ../system/objects/external-data-source-example.rst:31 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"First, enter the search URL making sure it contains ``#{search.term}`` as a " -"parameter:" +"Screencast showing the process on how to book the required sipgate.io addon" msgstr "" -#: ../system/objects/external-data-source-example.rst:34 -msgid "**Example:** ``https://dummyjson.com/products/search?q=#{search.term}``" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:52 +msgid "Step 2: Configure webhook for Zammad" msgstr "" -#: ../system/objects/external-data-source-example.rst:36 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:38 msgid "" -"After that, head down to the preview section and enter a search input for " -"the external data source." +"Within your ``Accountverwaltung`` navicate to your product ``sipgate.io``. " +"In the newly opened tab, switch from \"Clients\" to \"Webhooks\" and paste " +"the endpoint URLs from your Zammad instance like so:" msgstr "" -#: ../system/objects/external-data-source-example.rst:39 -msgid "**Example:** ``mac``" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:42 +msgid "Inbound endpoint to \"Incoming\"" msgstr "" -#: ../system/objects/external-data-source-example.rst:41 -msgid "Then you can find a preview of the response data below:" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:43 +msgid "Outbound endpoint to \"Outgoing\"" msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of JSON response based on search term" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:47 +msgid "" +"Ensure to select at least one call group or phoneline within \"Sources\". " +"Other wise Sipgate will not indicate any incoming or outgoing calls to " +"Zammad." msgstr "" -#: ../system/objects/external-data-source-example.rst:48 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"We recommend using the preview to have a look on the structure. There is a " -"top-level element called ``products``. One level below, you can find the " -"attributes ``id`` and ``title``." +"Screencast showing how to add Zammad's endpoint URLs to sipgate.ios webhook " +"configuration" msgstr "" -#: ../system/objects/external-data-source-example.rst:52 -msgid "**Search result response based on search from example:**" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:55 +msgid "" +"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " +"the Webhooks → URLs section of Sipgate you can select which *sources* " +"Sipgate should notify Zammad about in- and outgoing calls." msgstr "" -#: ../system/objects/external-data-source-example.rst:119 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:59 msgid "" -"To tell the remote system that the desired data is located below the " -"``products`` level, you have to put it in the field *Search result list key*." +"Use either specific phone lines or use the option \"Use for all phonelines " +"and groups\" to notify Zammad about all existing lines of your Sipgate " +"account." msgstr "" -#: ../system/objects/external-data-source-example.rst:122 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"After inserting ``products`` in the mentioned field, you get an extended " -"preview. You can find an additional box *Search result list* with a JSON " -"structure. This is the same response as before but stripped from the upper " -"``products`` element by the external data source." +"Screenshot showing a sample selection of phone numbers to use for the " +"Sipgates webhooks API" msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of JSON response search result list" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:68 +msgid "This section also allows you to enable a Debug log." msgstr "" -#: ../system/objects/external-data-source-example.rst:132 -msgid "" -"Now you need to provide the keys for the search result values and labels. As " -"already mentioned, we are looking for the ``id`` and the ``title`` of our " -"products. If you haven't already, it is now a good time to look at the " -"preview of the *Search result list*." +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "Screenshot showing an enabled Debug log option" msgstr "" -#: ../system/objects/external-data-source-example.rst:197 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:73 msgid "" -"After locating our two keys, we insert them in *search result value key* " -"(``id``) and in *Search result label key* (``title``)." +"After enabling you can use the Debug log section to see all sent webhook " +"calls to Zammad. You'll also can see the response." msgstr "" -#: ../system/objects/external-data-source-example.rst:200 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"Basically, we configured the external data source already and we can see a " -"table in the preview section:" -msgstr "" - -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of product table based on search term" +"Screenshot showing sample log entries for Sipgates webhook calls to Zammad" msgstr "" -#: ../system/objects/external-data-source-example.rst:208 -msgid "" -"According to our example story, now just the *Link template* is missing." +#: ../system/integrations/cti/provider-configurations/sipgate.rst:81 +msgid "Step 4 (optional): Further configurations for Sipgate" msgstr "" -#: ../system/objects/external-data-source-example.rst:210 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:80 msgid "" -"Please note that this is an optional feature. If you don't want to use such " -"links, of course you don't have to configure it." +"If needed, you can now configure Zammad's Sipgate integration in more " +"detail. You can learn more about your options here: :ref:`Sipgate " +"integration settings `." msgstr "" -#: ../system/objects/external-data-source-example.rst:213 -msgid "" -"We can add now an address where additional product information can be found." +#: ../system/integrations/cti/sipgate.rst:2 +msgid "Sipgate (sipgate.io)" msgstr "" -#: ../system/objects/external-data-source-example.rst:215 -msgid "Example: ``https://your_domain.com/q=#{ticket.product}``" +#: ../system/integrations/cti/sipgate.rst:16 +msgid "You need an administrative Sipgate account for your organization." msgstr "" -#: ../system/objects/external-data-source-example.rst:217 -msgid "In the example, the parameter means:" +#: ../system/integrations/cti/sipgate.rst:17 +msgid "" +"Zammad requires a ``sipgate.io`` addon from the feature store (please note " +"that API calls are not free with Sipgate. Rates may apply and differ from " +"account to account)." msgstr "" -#: ../system/objects/external-data-source-example.rst:219 -msgid "``#{}``: \"Frame\" for the insertion of information" +#: ../system/integrations/cti/sipgate.rst:21 +msgid "Sipgate must be able to reach your Zammad instance." msgstr "" -#: ../system/objects/external-data-source-example.rst:220 -msgid "``ticket``: object level, where you create your custom object" +#: ../system/integrations/cti/sipgate.rst:25 +msgid ":doc:`provider-configurations/sipgate`" msgstr "" -#: ../system/objects/external-data-source-example.rst:221 -msgid "``product``: name of the (custom) object" +#: ../system/integrations/cti/sipgate.rst:24 +msgid "" +"Learn how to configure Sipgate to enable Zammad and Sipgate to communicate " +"with each other." msgstr "" -#: ../system/objects/external-data-source-example.rst:223 +#: ../system/integrations/cti/sipgate.rst:33 msgid "" -"After configuring your *Link template*, there will be another column in the " -"preview. Hovering on the icons in the *Link* column will show you where it " -"forwards you." +"Below endpoint settings affect the :doc:`sipgate.io configuration `." msgstr "" -#: ../system/objects/external-data-source-example.rst:232 -msgid "" -"In our example, one of the links looks like: https://your_domain.com/q=6, " -"where the 6 is the product id." +#: ../system/integrations/cti/sipgate.rst:37 +msgid "This endpoint is required for incoming call hooks." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:40 +msgid "This endpoint is required for outgoing call hooks." msgstr "" -#: ../system/objects/external-data-source-example.rst:235 -msgid "You can find more information regarding the URL in :doc:`types`." +#: ../system/integrations/cti/sipgate.rst:0 +msgid "Screenshot showing sample user mappings in between Sipgate and Zammad" msgstr "" -#: ../system/objects/includes/adding-values-hint.include.rst:3 +#: ../system/integrations/cti/sipgate.rst:69 msgid "" -"Adding values can be tricky for first timers, don't forget to press \"➕ " -"Add\" after typing your values. Otherwise you may loose a value." +"You can find your agent's Sipgate username within ``Accountverwaltung → " +"Benutzer``. You're looking for the SIP-ID." msgstr "" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:1 -#: ../system/objects/includes/reposition-values.include.rst:1 -msgid "**↕️ This field type allows the positioning of its values ↔️**" +#: ../system/integrations/cti/sipgate.rst:0 +msgid "Sample VoIP credentials for a Sipgate user" msgstr "" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:3 -msgid "" -"In order to re-arrange the field values, first edit the field. Then you can " -"use ☰ to drag the values in question to the correct position. If you want to " -"change the layer depth, double click on ☰. With it you can cycle through the " -"available layers." +#: ../system/integrations/cti/sipgate.rst:77 +msgid "Users with several devices also have several SIP-IDs." msgstr "" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:8 -msgid "When you're ready, submit your changes to save the object attribute." +#: ../system/integrations/elasticsearch.rst:2 +msgid "Elasticsearch (SaaS)" msgstr "" -#: :0 ../system/objects/types.rst:0 +#: ../system/integrations/elasticsearch.rst:4 msgid "" -"Screencast showing how to re-position values on tree select like\n" -"fields" +"The Elasticsearch integration allows you to create a read-only user to use " +"with your favorite reporting tool (e.g. like Grafana)." msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:3 +#: ../system/integrations/elasticsearch.rst:7 msgid "" -"In order to re-arrange the field values, edit the field and scroll below the " -"values. Make sure to tick the option \"Use custom option sort\"." +"If you want to take full advantage of the Zammad reporting, have a look at " +"our :docs:`Grafana ` " +"setup page as well." msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:8 -msgid "" -"If you do not tick this field, all manual positioning you did above will be " -"lost upon saving! ☠️" +#: ../system/integrations/elasticsearch.rst:11 ../system/subscription.rst:7 +msgid "**🚧 Hosted environment specific 🚧**" msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:11 +#: ../system/integrations/elasticsearch.rst:13 msgid "" -"Now use ☰ to drag the values in question to the correct position. When " -"you're ready, submit your changes to save the object attribute." -msgstr "" - -#: :0 ../system/objects/types.rst:0 -msgid "Screencast showing how to re-position values" +"This integration is only available for Hosted setups. In order to use " +"Elasticsearch you'll need the **Plus** subscription." msgstr "" -#: ../system/objects/includes/url-template-hint.include.rst:3 +#: ../system/integrations/elasticsearch.rst:16 msgid "" -"This field allows using :ref:`URL fields (Link Templates) `." +"Self hosted users have all the control over their self hosted Elasticsearch " +"instances." msgstr "" -#: ../system/objects/permissions.rst:2 -msgid "Attribute Permissions" +#: ../system/integrations/elasticsearch.rst:None +msgid "Elasticsearch integration page on SaaS environments" msgstr "" -#: ../system/objects/permissions.rst:7 +#: ../system/integrations/elasticsearch.rst:27 msgid "" -"In the object attributes configuration you can define if a field is shown " -"and if the input in the field is mandatory, separated by different screens " -"and for different :doc:`roles/permissions `." +"Please note the following limitations of Elasticsearch access on hosted " +"environments:" msgstr "" -#: ../system/objects/permissions.rst:17 -msgid "Screenshot shows object attribute permission table" +#: ../system/integrations/elasticsearch.rst:30 +msgid "access to the Elasticsearch index is read-only access" msgstr "" -#: ../system/objects/permissions.rst:17 -msgid "" -"Some of the possible permissions and screen options for a user object " -"attribute." +#: ../system/integrations/elasticsearch.rst:31 +msgid "currently you're limited to user only" msgstr "" -#: ../system/objects/permissions.rst:19 +#: ../system/integrations/elasticsearch.rst:32 msgid "" -"Based on the object context (ticket, agent, organization, user), the " -"selectable roles (to be precise: the required permissions) and screens " -"differ. Be aware that these settings aren't affecting data creation via " -"other channels than the UI." +"Reporting tools that require to write into the indexes (like Kibana) are not " +"supported" msgstr "" -#: ../system/objects/permissions.rst:24 -msgid "" -"If you want to have further customization possibilities, you should have a " -"look at the :doc:`core workflows `." +#: ../system/integrations/elasticsearch.rst:34 +msgid "IP access restriction is currently not yet supported" msgstr "" -#: ../system/objects/permissions.rst:28 -msgid "Screens" +#: ../system/integrations/elasticsearch.rst:37 +msgid "Activating Elasticsearch Access" msgstr "" -#: ../system/objects/permissions.rst:30 +#: ../system/integrations/elasticsearch.rst:39 msgid "" -"In the table below you can find an overview about the different permissions " -"and the available screens Zammad distinguishes between." -msgstr "" - -#: ../system/objects/permissions.rst:37 -msgid "Screen" +"By default external access to your Elasticsearch index is not active. You " +"can enable the integration at any time if needed." msgstr "" -#: ../system/objects/permissions.rst:38 -msgid "Available for" +#: ../system/integrations/elasticsearch.rst:42 +msgid "" +"Please ensure to note down the password provided - you won't have access to " +"it afterwards." msgstr "" -#: ../system/objects/permissions.rst:40 -msgid "create" +#: ../system/integrations/elasticsearch.rst:None +msgid "Screencast showing activation of Elasticsearch integration" msgstr "" -#: ../system/objects/permissions.rst:41 ../system/objects/permissions.rst:52 -#: ../system/objects/permissions.rst:59 ../system/objects/permissions.rst:73 -msgid "admin.user" +#: ../system/integrations/elasticsearch.rst:51 +msgid "Connection Settings" msgstr "" -#: ../system/objects/permissions.rst:42 ../system/objects/permissions.rst:53 -#: ../system/objects/permissions.rst:60 -msgid "admin.organization" +#: ../system/integrations/elasticsearch.rst:53 +msgid "" +"This section holds the most important general information for accessing your " +"Elasticsearch indexes - such as:" msgstr "" -#: ../system/objects/permissions.rst:43 ../system/objects/permissions.rst:54 -#: ../system/objects/permissions.rst:61 -msgid "admin.group" +#: ../system/integrations/elasticsearch.rst:57 +msgid "A unique subdomain that does not tell your real instance URL." msgstr "" -#: ../system/objects/permissions.rst:44 -msgid "Creation dialog for not yet existing data" +#: ../system/integrations/elasticsearch.rst:61 +msgid "Software" msgstr "" -#: ../system/objects/permissions.rst:45 -msgid "create_middle" +#: ../system/integrations/elasticsearch.rst:60 +msgid "" +"The major version of the search index being used. This is required by some " +"Reporting tools like Grafana." msgstr "" -#: ../system/objects/permissions.rst:46 ../system/objects/permissions.rst:50 -#: ../system/objects/permissions.rst:57 ../system/objects/permissions.rst:66 -#: ../system/objects/permissions.rst:70 -msgid "ticket.customer" +#: ../system/integrations/elasticsearch.rst:64 +msgid "Authentication" msgstr "" -#: ../system/objects/permissions.rst:47 ../system/objects/permissions.rst:51 -#: ../system/objects/permissions.rst:58 ../system/objects/permissions.rst:69 -msgid "ticket.agent" +#: ../system/integrations/elasticsearch.rst:64 +msgid "The authentication type being supported. ``Basic Authentication``" msgstr "" -#: ../system/objects/permissions.rst:48 -msgid "Ticket create dialog (middle section)" +#: ../system/integrations/elasticsearch.rst:67 +msgid "Available Indexes" msgstr "" -#: ../system/objects/permissions.rst:49 -msgid "edit" +#: ../system/integrations/elasticsearch.rst:69 +msgid "" +"Within this section we're displaying the -in our opinion- most important " +"indexes for a Zammad instance." msgstr "" -#: ../system/objects/permissions.rst:55 -msgid "Editing dialog for already existing data" +#: ../system/integrations/elasticsearch.rst:72 +msgid "" +"If you require all indexes or our listing is not good enough for you, point " +"your browser to the URL we're providing and append ``/_aliases?" +"pretty=true``. The result should look like this: ``https://.zammad.com/" +"_aliases?pretty=true``." msgstr "" -#: ../system/objects/permissions.rst:56 -msgid "view" +#: ../system/integrations/elasticsearch.rst:77 +msgid "" +"Your browser will automatically ask for your credentials - you'll then see " +"something like this:" msgstr "" -#: ../system/objects/permissions.rst:62 -msgid "View-only dialog for already existing data" +#: ../system/integrations/elasticsearch.rst:125 +msgid "Credentials" msgstr "" -#: ../system/objects/permissions.rst:64 -msgid "(e.g. user or organization from search)" +#: ../system/integrations/elasticsearch.rst:127 +msgid "" +"Within this section Zammad displays your available users. The password is " +"provided once (upon activation) and cannot be retrieved after that." msgstr "" -#: ../system/objects/permissions.rst:65 -msgid "signup" +#: ../system/integrations/elasticsearch.rst:131 +msgid "" +"If you need to change or reset your Elasticsearch user password, use the " +"\"Reset password\" button in the credentials table. Doing so creates a brand " +"new password for the account in question. This change is immediate, keep in " +"mind that this may affect third party tools connected to your instance." msgstr "" -#: ../system/objects/permissions.rst:67 -msgid "Sign-up screen for new customers" +#: ../system/integrations/exchange.rst:2 +msgid "Exchange" msgstr "" -#: ../system/objects/permissions.rst:68 -msgid "invite_customer" +#: ../system/integrations/exchange.rst:4 +msgid "" +"With Zammad's Exchange integration, you can easily use existing address " +"books without having to update more than one source." msgstr "" -#: ../system/objects/permissions.rst:71 +#: ../system/integrations/exchange.rst:7 msgid "" -"Customer invitation screen (from :doc:`First Steps ` area)" +"However, you should refrain from syncing all addresses, as the results may " +"not be what you expect (Exchange collects huge amounts of addresses). A " +"central address book of your company to sync makes more sense, as you can " +"ensure that Zammad gets only the data you need and want. Apart from this, it " +"is even not possible to sync the Global Address List (GAL) of your Exchange " +"system with Zammad." msgstr "" -#: ../system/objects/permissions.rst:72 -msgid "invite_agent" +#: ../system/integrations/exchange.rst:16 +msgid "" +"**Exchange and LDAP:** The exchange sync can be overruled by Zammad's LDAP " +"integration. If you have the same users in both sources, the LDAP version " +"will always be Zammad's pick." msgstr "" -#: ../system/objects/permissions.rst:74 +#: ../system/integrations/exchange.rst:19 msgid "" -"Agent invitation screen (from :doc:`First Steps ` area)" +"**One way sync:** the Exchange sync is one way. Exchange => Zammad. Changes " +"to your users inside of Zammad might be overwritten by the Exchange sync." msgstr "" -#: ../system/objects/permissions.rst:78 -msgid "Screen Options" +#: ../system/integrations/exchange.rst:24 +msgid "" +"To configure Exchange integration, simply go to the System > Integrations > " +"Exchange in the admin panel. Press \"change\" and follow the wizard for " +"adding the needed Exchange information to Zammad. On the last two steps " +"Zammad will ask you for the address book(s) and your desired attribute " +"mapping. By default, Zammad only maps email address, first- and lastname. " +"Technically, you can map any Exchange object to a Zammad user object (this " +"also works for custom objects!)." msgstr "" -#: ../system/objects/permissions.rst:80 +#: ../system/integrations/exchange.rst:35 msgid "" -"For the different screens you can select \"show\" and \"required\" options." +"If the SSL verification fails while connecting to Exchange, Zammad will ask " +"you to turn it off temporarily." msgstr "" -#: ../system/objects/permissions.rst:82 -msgid "**shown:** Show (check) or hide (uncheck) a field." +#: ../system/integrations/exchange.rst:38 +msgid "" +"Please be aware that **turning off SSL verification is a security risk**. It " +"should only be used temporarily or for testing purposes. If turned off, " +"there is no verification of the certificate, which means that every " +"presented certificate will be accepted." msgstr "" -#: ../system/objects/permissions.rst:83 +#: ../system/integrations/exchange.rst:43 msgid "" -"**required:** Set a field to mandatory (check). Forces users (via UI and " -"API) to populate the field." -msgstr "" - -#: ../system/objects/types.rst:7 -msgid "Example external data source" +"After pressing Continue, Zammad will check if the configuration is okay. You " +"can then enable Exchange and start your first sync. The sync will then run " +"hourly - if you need to change mappings or the address book(s), you can " +"change the configuration at any time." msgstr "" -#: ../system/objects/types.rst:2 -msgid "Attribute types" +#: ../system/integrations/exchange.rst:50 +msgid "" +"After the sync has finished, you can find the new Exchange contacts under " +"\"Users\". Zammad integrates them just as normal users." msgstr "" -#: ../system/objects/types.rst:4 +#: ../system/integrations/exchange.rst:55 msgid "" -"When adding a new object attribute, you can choose between the following " -"attribute types." +"In some cases you might see unique IDs as \"Login\" instead of the email " +"address. This is normal and doesn't affect the login or email mapping for " +"that entry." msgstr "" -#: ../system/objects/types.rst:14 +#: ../system/integrations/github.rst:4 msgid "" -"You cannot change the attribute format / type as soon as it is applied. If " -"you no longer need an object attribute, consider disabling it instead of " -"removing." +"Use GitHub integration to track GitHub issues directly within Zammad " +"tickets. Add issue hyperlinks and get a live summary of metadata like status " +"(open/closed), assignee, labels, and more." msgstr "" -#: ../system/objects/types.rst:18 -msgid "**What about the translation of my attributes?**" +#: ../system/integrations/github.rst:8 +msgid "Please note that our GitHub integration does not support pull requests." msgstr "" -#: ../system/objects/types.rst:20 -msgid "" -"For some attribute types you can decide if they should be translatable or " -"not. To be precise, it works only for the selectable fields because the " -"possible choices are known and limited. For the following attribute types, " -"you can set the translatable flag:" +#: ../system/integrations/github.rst:None +msgid "Integration page for GitHub" msgstr "" -#: ../system/objects/types.rst:25 -msgid "*Boolean field*" +#: ../system/integrations/github.rst:18 +msgid "" +"In your GitHub settings, create a new API token under **Developer settings > " +"Personal access tokens > Generate new token**. Leave the **Scopes** section " +"empty." msgstr "" -#: ../system/objects/types.rst:26 -msgid "*Single selection field*" +#: ../system/integrations/github.rst:0 ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to create a new API token" msgstr "" -#: ../system/objects/types.rst:27 -msgid "*Multiple selection field*" +#: ../system/integrations/github.rst:27 +msgid "Create a new API key with no scopes/privileges." msgstr "" -#: ../system/objects/types.rst:28 -msgid "*Single tree selection field*" +#: ../system/integrations/github.rst:29 +msgid "🔒 **Will this work for private repos?**" msgstr "" -#: ../system/objects/types.rst:29 -msgid "*Multiple tree selection field*" +#: ../system/integrations/github.rst:31 +msgid "" +"No. To link private repo issues, **use the** ``repo`` **scope instead**. " +"Bear in mind that the resulting token will have `lots of permissions that it " +"doesn't actually need `_, which presents a security risk if your token ever falls into " +"the wrong hands." msgstr "" -#: ../system/objects/types.rst:31 +#: ../system/integrations/github.rst:37 msgid "" -"For these types, you can find an additional field *Translate field contents*:" +"Unfortunately, because of how GitHub's OAuth token scopes are set up, this " +"is the only way to link issues on private repos." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Screenshot showing translatable attribute types" +#: ../system/integrations/github.rst:40 +msgid "Enter your new API token in Zammad and enable GitHub integration." msgstr "" -#: ../system/objects/types.rst:38 -msgid "Screenshot with example of translatable attribute type" +#: ../system/integrations/github.rst:0 +msgid "Screencast showing how to configure Zammad's GitHub integration" msgstr "" -#: ../system/objects/types.rst:45 -msgid "Boolean field" +#: ../system/integrations/github.rst:47 +msgid "" +"Use the default API endpoint (``https://api.github.com/graphql``) unless " +"you're using GitHub Enterprise Server." msgstr "" -#: ../system/objects/types.rst:41 +#: ../system/integrations/github.rst:50 msgid "" -"Provides a drop-down field with display values for ``true`` and ``false``. " -"Setting a default is mandatory." +"Once completed, a new GitHub issues tab will appear in the ticket pane. 🎉" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Boolean fields" +#: ../system/integrations/github.rst:59 ../system/integrations/gitlab.rst:52 +msgid "Token verification is taking a long time" msgstr "" -#: ../system/objects/types.rst:55 -msgid "Date field" +#: ../system/integrations/github.rst:56 ../system/integrations/gitlab.rst:49 +msgid "" +"Slight delays are normal (<2 min.), especially for systems under heavy load." msgstr "" -#: ../system/objects/types.rst:48 -msgid "Provides a date picker field and does not allow default values." +#: ../system/integrations/github.rst:58 +msgid "" +"Self-hosted administrators, please check your network settings to ensure " +"that your Zammad server can reach ``api.github.com``." msgstr "" -#: ../system/objects/types.rst:52 -msgid "Default time diff (hours)" +#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 +msgid "I reloaded the page and now the API token is gone" msgstr "" -#: ../system/objects/types.rst:51 +#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 msgid "" -"This setting helps the user by highlighting the day from now plus the " -"provided value. It *does not* pre-fill the field." -msgstr "" - -#: ../system/objects/types.rst:0 -msgid "Available settings for Date fields" +"This may indicate that Zammad is still verifying your API token. Try " +"reloading the page again in a couple minutes." msgstr "" -#: ../system/objects/types.rst:73 -msgid "Date & time field" +#: ../system/integrations/gitlab.rst:2 +msgid "GitLab" msgstr "" -#: ../system/objects/types.rst:58 -msgid "Provides a date and time picker – does not allow default values" +#: ../system/integrations/gitlab.rst:4 +msgid "" +"Use GitLab integration to track GitLab issues directly within Zammad " +"tickets. Add issue hyperlinks and get a live summary of metadata like status " +"(open/closed), assignee, labels, and more." msgstr "" -#: ../system/objects/types.rst:62 -msgid "Allow future" +#: ../system/integrations/gitlab.rst:8 +msgid "" +"Please note that our GitLab integration does not support merge requests." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Forbid dates and times in the future." +#: ../system/integrations/gitlab.rst:None +msgid "Integration page for GitLab" msgstr "" -#: ../system/objects/types.rst:66 -msgid "Allow past" +#: ../system/integrations/gitlab.rst:18 +msgid "" +"In your GitLab preferences, create a new API token under **Access Tokens**." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Forbid dates and times in the past." +#: ../system/integrations/gitlab.rst:20 +msgid "Under **Select scopes**, choose ``read_api`` only." msgstr "" -#: ../system/objects/types.rst:70 -msgid "Default time diff (minutes)" +#: ../system/integrations/gitlab.rst:27 +msgid "🔒 **If you wish to link issues on any private repos...**" msgstr "" -#: ../system/objects/types.rst:69 -msgid "" -"This setting helps the user by highlighting the day from now plus the " -"provided value. It does not pre-fill the field." +#: ../system/integrations/gitlab.rst:29 +msgid "Your API token must belong to an account with access to those repos." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Date & time fields" +#: ../system/integrations/gitlab.rst:31 +msgid "Enter your new API token in Zammad and enable GitLab integration." msgstr "" -#: ../system/objects/types.rst:86 -msgid "Integer field" +#: ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to configure Zammad's GitLab integration" msgstr "" -#: ../system/objects/types.rst:76 +#: ../system/integrations/gitlab.rst:40 msgid "" -"Provides an input field that allows integer usage only. You may define a " -"default value. You cannot enforce comma separation." +"Use the default API endpoint (``https://gitlab.com/api/graphql``) unless " +"you're a self-hosted GitLab user." msgstr "" -#: ../system/objects/types.rst:80 -msgid "Minimal" +#: ../system/integrations/gitlab.rst:43 +msgid "" +"Once completed, a new GitLab issues tab will appear in the ticket pane. 🎉" msgstr "" -#: ../system/objects/types.rst:80 -msgid "The minimal value the field accepts." +#: ../system/integrations/gitlab.rst:51 +msgid "" +"Self-hosted administrators, please check your network settings to ensure " +"that your Zammad server can reach ``gitlab.com``." msgstr "" -#: ../system/objects/types.rst:83 -msgid "Maximal" +#: ../system/integrations/i-doit.rst:2 +msgid "i-doit" msgstr "" -#: ../system/objects/types.rst:83 -msgid "The maximum value the field accepts." +#: ../system/integrations/i-doit.rst:4 +msgid "" +"`i-doit `_ is an open-source **configuration " +"management database** - in other words, a tool for keeping tabs on every " +"single piece of your physical and digital infrastructure, from network " +"equipment to virtual machines on down to the faceplates on your rack shelves " +"and more." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Integer fields" +#: ../system/integrations/i-doit.rst:10 +msgid "" +"What's that got to do with Zammad? Well, if you used tickets to track issues " +"with all that hardware, you might start wishing there was a way they could " +"talk to each other." msgstr "" -#: ../system/objects/types.rst:99 -msgid "Multiple selection field" +#: ../system/integrations/i-doit.rst:14 +msgid "Zammad gives you two:" msgstr "" -#: ../system/objects/types.rst:89 -msgid "" -"Provides a selection field that allows the selection of one or more out of " -"several. This field does allow setting a default value." +#: ../system/integrations/i-doit.rst:17 +msgid "1. Add i-doit Links to Zammad Tickets" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Multiple selection fields" +#: ../system/integrations/i-doit.rst:20 ../system/integrations/i-doit.rst:80 +msgid "What Users See" msgstr "" -#: ../system/objects/types.rst:112 -msgid "Single selection field" +#: ../system/integrations/i-doit.rst:26 +msgid "i-doit integration in Zammad's ticket pane" msgstr "" -#: ../system/objects/types.rst:102 +#: ../system/integrations/i-doit.rst:26 msgid "" -"Provides a drop-down field that allows selection of one value out of " -"several. This field does allow setting a default value." +"The i-doit integration will appear under a new 🖨 tab in the ticket pane." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Single selection fields" +#: ../system/integrations/i-doit.rst:28 +msgid "" +"i-doit integration puts a new tab in Zammad's ticket pane where you can add " +"links to existing i-doit devices for easy reference. (See our :user-docs:" +"`user documentation ` to learn " +"how it works in practice)." msgstr "" -#: ../system/objects/types.rst:142 -msgid "Textarea field" +#: ../system/integrations/i-doit.rst:36 ../system/integrations/i-doit.rst:93 +msgid "How to Set it Up" msgstr "" -#: ../system/objects/types.rst:115 +#: ../system/integrations/i-doit.rst:38 msgid "" -"Provides a text area input field (multiple lines) and thus allows e.g. new " -"lines. You can set a default field value." +"It requires i-doit's `API Add-on `_. Make sure to have it properly set up. Use the following setting:" msgstr "" -#: ../system/objects/types.rst:120 -msgid "" -"Please note that this field *does not* support text formatting or HTML " -"content (rich text)." +#: ../system/integrations/i-doit.rst:42 +msgid "Active: ``Yes``" msgstr "" -#: ../system/objects/types.rst:123 -msgid "**🥵 This field can consume a lot of visual space**" +#: ../system/integrations/i-doit.rst:43 +msgid "Enforce authentication by username and password: ``No``" msgstr "" -#: ../system/objects/types.rst:125 +#: ../system/integrations/i-doit.rst:45 msgid "" -"Depending on where you use this field type, it may use a lot of visual space " -"if you provide a lot of text. This may be an issue to work with." +"To set it up, enable the integration in the Zammad admin panel under " +"**System > Integrations > i-doit**:" msgstr "" -#: ../system/objects/types.rst:130 -msgid "Default" +#: ../system/integrations/i-doit.rst:None +msgid "i-doit settings within the integration pages" msgstr "" -#: ../system/objects/types.rst:129 -msgid "" -"The here provided text will be shown within the text area field or new data " -"sets." +#: ../system/integrations/i-doit.rst:53 +msgid "The root URL of your i-doit installation." msgstr "" -#: ../system/objects/types.rst:134 ../system/objects/types.rst:160 -msgid "Maxlength" +#: ../system/integrations/i-doit.rst:62 +msgid "API token" msgstr "" -#: ../system/objects/types.rst:0 ../system/objects/types.rst:160 -msgid "You can pick the maximum length of the field." +#: ../system/integrations/i-doit.rst:56 +msgid "" +"Found in the i-doit admin panel under **Interfaces / external data > JSON-" +"RPC API > Common Settings**." msgstr "" -#: ../system/objects/types.rst:0 -msgid "The default length of this object is ``500``." +#: ../system/integrations/i-doit.rst:0 +msgid "i-doit administration interface with API configuration" msgstr "" -#: ../system/objects/types.rst:139 -msgid "Rows" +#: ../system/integrations/i-doit.rst:67 +msgid "Client ID" msgstr "" -#: ../system/objects/types.rst:0 -msgid "" -"Change the number of rows to dislay so that you can use only the space you " -"really need." +#: ../system/integrations/i-doit.rst:65 +msgid "A unique name to identify Zammad within i-doit." msgstr "" -#: ../system/objects/types.rst:0 -msgid "The default number of rows is ``4``." +#: ../system/integrations/i-doit.rst:67 +msgid "(Zammad does not require you to enter a value here, but i-doit might!)" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Textarea fields" +#: ../system/integrations/i-doit.rst:70 +msgid "" +"Here you can decide if the certificate of your i-doit system has to be " +"verified or not. In case you are using custom certificates, please have a " +"look at :doc:`how to add them to Zammad `." msgstr "" -#: ../system/objects/types.rst:165 -msgid "Text field" +#: ../system/integrations/i-doit.rst:77 +msgid "2. List / Create Zammad Tickets in i-doit" msgstr "" -#: ../system/objects/types.rst:145 -msgid "Provides a text field (one line) and allows choosing a default value." +#: ../system/integrations/i-doit.rst:None +msgid "Zammad integration in i-doit's device view" msgstr "" -#: ../system/objects/types.rst:148 +#: ../system/integrations/i-doit.rst:86 msgid "" -"Defines the type of the input field. This allows e.g. your browser to ensure " -"that you provide the specific type." +"i-doit's ticket system integration gives you a way to see all the tickets " +"for a given device without ever leaving i-doit. (See our :user-docs:`user " +"documentation ` to learn how it " +"works in practice)." msgstr "" -#: ../system/objects/types.rst:152 -msgid "Currently available:" +#: ../system/integrations/i-doit.rst:95 +msgid "" +"Enable this integration in the i-doit admin panel under **Interfaces / " +"external data > Trouble Ticket System (TTS) > Configuration**:" msgstr "" -#: ../system/objects/types.rst:155 -msgid "Phone" +#: ../system/integrations/i-doit.rst:None +msgid "i-doit administration interface with TTS configuration" msgstr "" -#: ../system/objects/types.rst:156 -msgid "Text" +#: ../system/integrations/i-doit.rst:104 +msgid "TTS-Type" msgstr "" -#: ../system/objects/types.rst:157 -msgid "Url *(URL fields disable link-template availability)*" +#: ../system/integrations/i-doit.rst:104 +msgid "``Zammad``" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Text fields" +#: ../system/integrations/i-doit.rst:115 +msgid "Username / Password" msgstr "" -#: ../system/objects/types.rst:174 -msgid "Single tree selection field" +#: ../system/integrations/i-doit.rst:107 +msgid "Login credentials for a Zammad agent." msgstr "" -#: ../system/objects/types.rst:168 +#: ../system/integrations/i-doit.rst:109 msgid "" -"Provides a select-like field with up to 6 layers of options. Does not allow " -"setting a default value." +"This agent must have **read permission** for all :doc:`groups ` that plan on using the i-doit integration." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Tree Select fields" +#: ../system/integrations/i-doit.rst:113 +msgid "" +"You may even wish to create a dedicated agent account just for this " +"integration (otherwise, if the agent ever changes her password, you will " +"have to remember to update it here)." msgstr "" -#: ../system/objects/types.rst:183 -msgid "Multiple tree selection field" +#: ../system/integrations/i-doit.rst:117 +msgid "URL incl. protocol" msgstr "" -#: ../system/objects/types.rst:177 -msgid "" -"Provides a select-like field with up to 6 layers of options allowing the " -"selection of multiple values. Does not allow setting a default value." +#: ../system/integrations/i-doit.rst:118 +msgid "``https://your.zammad.domain``" msgstr "" -#: ../system/objects/types.rst:302 -msgid "External Data Source field" +#: ../system/integrations/index.rst:2 +msgid "Integrations" msgstr "" -#: ../system/objects/types.rst:186 +#: ../system/integrations/index.rst:4 msgid "" -"Provides a searchable field which fetches data from an external system. This " -"can be useful if you have data outside of Zammad and don't want to maintain " -"both data sources." +"Zammad offers numerous integrations that add rich features to your instance." msgstr "" -#: ../system/objects/types.rst:190 -msgid "The feature works as follows:" +#: ../system/integrations/index.rst:6 +msgid "We're still working on this part of our documentation, stay tight!" msgstr "" -#: ../system/objects/types.rst:192 -msgid "" -"Zammad sends a query with a search string (free text from agent or based on " -"a variable) in a pre-defined format (\"Search URL\") to an external system." +#: ../system/integrations/index.rst:10 +msgid "Integrations for Phone Systems" msgstr "" -#: ../system/objects/types.rst:195 +#: ../system/integrations/index.rst:14 msgid "" -"This external system searches for matches and provides a response as a JSON " -"structure to Zammad." +"Your VoIP provider or telephony system is not listed? Possibly your provider " +"supports Zammad by using the generic CTI - if you're unsure ask your " +"provider." msgstr "" -#: ../system/objects/types.rst:197 +#: ../system/integrations/index.rst:18 msgid "" -"Zammad just looks for the defined list and value keys, reads the content and " -"displays the value to the user. There is no search on Zammad side." +"Provider does not support Zammad? Consider creating a `feature request in " +"the Zammad Community `_." msgstr "" -#: ../system/objects/types.rst:201 -msgid "" -"The usage of a PostgreSQL database for Zammad is required. In any other " -"case, Zammad will hide the external data source type and you are not able to " -"use it. If you want to use this feature, consider to :docs:`migrate your " -"database `." +#: ../system/integrations/index.rst:31 +msgid "Integrations for Authentication and Customers" msgstr "" -#: ../system/objects/types.rst:205 -msgid "Currently, only ``GET`` is supported as request method." +#: ../system/integrations/index.rst:44 +msgid "Integrations for Monitoring Systems" msgstr "" -#: ../system/objects/types.rst:206 -msgid "" -"The data structure must be in JSON format and provide the objects in an " -"array." +#: ../system/integrations/index.rst:46 +msgid "This section currently misses the following integrations:" msgstr "" -#: ../system/objects/types.rst:208 -msgid "" -"The endpoint for the external data source has to support search. On Zammad " -"side, there is no search/logic implemented; however, you can define the " -"output key and value based on the result(s) from the response (which " -"provides already filtered content based on the search)." +#: ../system/integrations/index.rst:48 +msgid "Icinga" msgstr "" -#: ../system/objects/types.rst:212 -msgid "" -"If you receive more results as expected, your external data source search " -"may not work properly or the structure of the URL is not correct. You should " -"get in touch with a responsible person from the external system." +#: ../system/integrations/index.rst:49 +msgid "Monit" msgstr "" -#: ../system/objects/types.rst:217 -msgid "" -"Please have a look :doc:`at our example `, where you can find a possible configuration for a public " -"dummy endpoint." +#: ../system/integrations/index.rst:50 +msgid "Nagios" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for external data source fields" +#: ../system/integrations/index.rst:60 +msgid "Integrations for Issue Trackers" msgstr "" -#: ../system/objects/types.rst:242 -msgid "Search URL" +#: ../system/integrations/index.rst:70 +msgid "Other Integrations" msgstr "" -#: ../system/objects/types.rst:227 +#: ../system/integrations/index.rst:72 msgid "" -"Set your endpoint where Zammad fetches the data. Please make sure to include " -"a valid search :doc:`variable <../variables>` as an URL parameter. Example " -"for a free text search at user input: ``#{search.term}``" +"This section will hold any other integration that can't be grouped up (yet)." msgstr "" -#: ../system/objects/types.rst:232 -msgid "" -"If in doubt, ask the responsible person for the external data source how " -"they expect the strucuture of the URL." +#: ../system/integrations/ldap/index.rst:2 +msgid "LDAP / Active Directory" msgstr "" -#: ../system/objects/types.rst:236 +#: ../system/integrations/ldap/index.rst:4 msgid "" -"Depending on your search variable, the preview might work or not. The reason " -"is that the context might not be available and it is no bug." +"Zammad comes with a powerful LDAP integration that allows you to have a " +"single source of truth. By this you reduce the number of login credentials " +"your user has to remember." msgstr "" -#: ../system/objects/types.rst:239 +#: ../system/integrations/ldap/index.rst:10 msgid "" -"Please also make sure to use a variable which is available in your object " -"context. For example you won't be able to search for a ticket in a user " -"object context." -msgstr "" - -#: ../system/objects/types.rst:252 -msgid "SSL Verification" +"The LDAP source is also a perfect candidate for Zammad's :docs:`Kerberos " +"Single Sign-On ` but also works as addition " +"to other :doc:`/settings/security/third-party`." msgstr "" -#: ../system/objects/types.rst:245 -msgid "Here you can switch the SSL verification to no." +#: ../system/integrations/ldap/index.rst:None +msgid "Zammands LDAP management page" msgstr "" -#: ../system/objects/types.rst:249 -msgid "" -"If your external data source system is using self signed certificates, " -"please have a look :doc:`here ` for " -"further information about how to handle them in Zammad, so you can keep the " -"SSL verification activated." +#: ../system/integrations/ldap/index.rst:25 +msgid "📝 :doc:`manage`" msgstr "" -#: ../system/objects/types.rst:258 -msgid "HTTP Authentication" +#: ../system/integrations/ldap/index.rst:25 +msgid "Add, modify, remove or re-arrange your LDAP-Sources as needed." msgstr "" -#: ../system/objects/types.rst:255 -msgid "" -"If your external data source requires an authentication, you can set it " -"here. You can leave it empty or choose between *Basic Authentication* or " -"*Authentication Token* (selecting one of the two methods leads to additional " -"fields where you can enter your credentials/token)." +#: ../system/integrations/ldap/index.rst:30 +msgid "Before you continue, please note the following limitations." msgstr "" -#: ../system/objects/types.rst:265 -msgid "Search result list key" +#: ../system/integrations/ldap/index.rst:32 +msgid "Mapping / Synchronizing organizations is not possible" msgstr "" -#: ../system/objects/types.rst:261 +#: ../system/integrations/ldap/index.rst:36 msgid "" -"Defines the level in the JSON structure which provides the list with search " -"results. You can leave it empty, if the data is already provided as an " -"array. If you have to go deeper in the structure, you can provide a path " -"with ``.`` as separators, e.g. ``key.subkey.sub-sub-key``." +"You may want to consider using domain based assignments to overcome this " +"issue. Learn more on :doc:`/manage/organizations/index`." msgstr "" -#: ../system/objects/types.rst:271 -msgid "Search result value key" +#: ../system/integrations/ldap/index.rst:39 +msgid "" +"Zammad's LDAP sync is one way. Editing user settings or permissions may be " +"overwritten upon the next sync depending on your configuration." msgstr "" -#: ../system/objects/types.rst:268 -msgid "" -"Defines the attribute in the structure in which your external data source " -"provides the *value* for your data. An example would be a product *number*. " -"If you have to go deeper in the structure, you can provide a path with ``.`` " -"as separators, e.g. ``key.subkey.sub-sub-key``." +#: ../system/integrations/ldap/index.rst:41 +msgid "Nested groups are not supported." msgstr "" -#: ../system/objects/types.rst:277 -msgid "Search result label key" +#: ../system/integrations/ldap/index.rst:42 +msgid "Synchronizing user avatars from LDAP is not supported." msgstr "" -#: ../system/objects/types.rst:274 -msgid "" -"Defines the attribute in the structure in which your external data source " -"provides the *label* for your data. An example would be a product *name*. If " -"you have to go deeper in the structure, you can provide a path with ``.`` as " -"separators, e.g. ``key.subkey.sub-sub-key``." +#: ../system/integrations/ldap/index.rst:43 +msgid "Unlike user filters, group filters cannot be changed." msgstr "" -#: ../system/objects/types.rst:280 +#: ../system/integrations/ldap/index.rst:44 msgid "" -"In the preview area, you can find the following items (depending on your " -"configuration above):" +"When a user originates from an LDAP server, Zammad will try to verify the " +"login credentials against LDAP first - if this fails Zammad will check its " +"local database." msgstr "" -#: ../system/objects/types.rst:283 +#: ../system/integrations/ldap/index.rst:50 msgid "" -"**Error/hint message** (only if configuration is not complete): Zammad tells " -"you, if there is a problem and what you should change in your configuration." +"Users can have local passwords even if they're LDAP users! You can learn " +"more about user accounts in general on :doc:`/manage/users/index`." msgstr "" -#: ../system/objects/types.rst:286 +#: ../system/integrations/ldap/index.rst:54 msgid "" -"**Search field**: search for an existing attribute in the data source to get " -"a preview. This is required for the fields below to show up." +"When several LDAP sources contain the same user (meaning the same email " +"address), the user in question will be updated with every source configured. " +"*The last LDAP source will win.*" msgstr "" -#: ../system/objects/types.rst:288 +#: ../system/integrations/ldap/index.rst:58 msgid "" -"**Search result response** (only if configuration is not complete): here you " -"can find a syntax highlighted JSON preview of the response, based on the " -"search term you entered." +"This is subject to change with `Issue 4109 `_ in the future." msgstr "" -#: ../system/objects/types.rst:291 +#: ../system/integrations/ldap/index.rst:60 msgid "" -"**Search result list** (only if *search result list key* is properly set): " -"output of the structure under the configured *search result list key*." +"Synchronization statistics currently affect *all* configured LDAP sources. " +"This also applies for newly added or updated sources." msgstr "" -#: ../system/objects/types.rst:294 +#: ../system/integrations/ldap/index.rst:63 msgid "" -"**Preview table** (when fully configured): Zammad shows you a table which " -"includes the found items based on the search string (value, label and " -"optional link). You can use this preview if you don't have the complete data " -"structure of the external system in mind." +"This is subject to change with `Issue 4108 `_ in the future." msgstr "" -#: ../system/objects/types.rst:299 +#: ../system/integrations/ldap/index.rst:65 msgid "" -"An example of a configured external data source field from agent perspective:" +"Zammad currently has limited fallback server support. You can workaround " +"this by providing several sources - however, ensure to have the exact same " +"configuration on your fallback." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Screencast showing the search for a product in a ticket" +#: ../system/integrations/ldap/index.rst:69 +msgid "" +"This is subject to improve with `Issue 4107 `_ in the future." msgstr "" -#: ../system/objects/types.rst:307 -msgid "URL fields (Link-Template)" +#: ../system/integrations/ldap/index.rst:76 +msgid "" +"This section holds all requests Zammad handled for all LDAP sources. These " +"entries can either contain synchronization information or logins " +"(authentication attempts via Zammad's login interface)." msgstr "" -#: ../system/objects/types.rst:311 +#: ../system/integrations/ldap/index.rst:80 msgid "" -"This function is restricted to Text, Select and External data source types " -"only." +"By clicking on any request, Zammad will provide even more information. The " +"provided information can be useful when something does not work as expected." msgstr "" -#: ../system/objects/types.rst:314 +#: ../system/integrations/ldap/index.rst:85 msgid "" -"Link-Templates are an amazing way to dynamically generate URLs. They allow " -"you to integrate other systems better without having to manually copy data " -"from Zammad if possible." +"Especially a LDAP synchronization can cause many log entries. The web " +"interface will always limit the number of shown entries to the last 50 " +"entries." msgstr "" -#: ../system/objects/types.rst:320 +#: ../system/integrations/ldap/index.rst:None msgid "" -"Another great way of communicating with another system may be Zammad's :doc:" -"`Webhooks `." +"Screencast showing LDAP integration log entries and a detail view on\n" +"an entry." msgstr "" -#: ../system/objects/types.rst:323 -msgid "" -"After filling a link-template enabled field, an URL icon will appear on its " -"right. Clicking on the icon opens a new tab." +#: ../system/integrations/ldap/manage.rst:2 +msgid "Manage LDAP-Sources" msgstr "" -#: ../system/objects/types.rst:328 +#: ../system/integrations/ldap/manage.rst:6 msgid "" -"Even though Zammad displays the link template within object edit and create " -"screens, the function is optional. It's only active if you populate the " -"field." +"Please keep in mind all current limitations for the LDAP synchronization. " +"This will help to understand scopes of the following operations better." msgstr "" -#: ../system/objects/types.rst:333 -msgid "" -"What's the difference between URL and text fields with link template...?!" +#: ../system/integrations/ldap/manage.rst:65 +msgid "Add new source" msgstr "" -#: ../system/objects/types.rst:335 +#: ../system/integrations/ldap/manage.rst:10 msgid "" -"Both fields have different use cases. Use ``text`` type text fields when " -"ever you have a *static* url that requires dynamic parameters. If you " -"require a drag & drop like field that you can put in any URL, use ``URL`` " -"type text fields." +"Using the *New Source* button allows you to add new LDAP sources to your " +"installation. You're not limited in the number of sources, however, keep in " +"mind that many sources will also take more time to synchronize." msgstr "" -#: ../system/objects/types.rst:340 +#: ../system/integrations/ldap/manage.rst:14 msgid "" -"The difference is easier to spot when comparing the fields directly, below " -"screencast shows the result - the dynamic approach uses existing values in " -"the moment of updating to built the URL - e.g. ``https://google.com/search?" -"q=cookies`` - while the URL approach uses the actual URL of the field - e.g. " -"``https://zammad.com``." +"You can choose between different encryption types, namely *SSL* and " +"*STARTTLS* or none of them (\"*No SSL*\"). If you choose *SSL* or " +"*STARTTLS*, Zammad will display an additional *SSL verification* option that " +"allows you to disable the verification, e.g. for self-signed SSL " +"certificates. You can also tell Zammad to use a different port by appending " +"``:`` to your hostname/IP." msgstr "" -#: ../system/objects/types.rst:None +#: ../system/integrations/ldap/manage.rst:0 msgid "" -"Screencast showing the differents in between URL and text type fields with " -"actual values" +"Screenshot of configuring a new LDAP source with SSL encryption and SSL " +"verification" msgstr "" -#: ../system/objects/types.rst:352 -msgid "How does this work...?!" +#: ../system/integrations/ldap/manage.rst:26 +msgid "" +"New Source with SSL transport security enabled and certificate verification" msgstr "" -#: ../system/objects/types.rst:354 +#: ../system/integrations/ldap/manage.rst:30 msgid "" -"As an example, let's say you have an attribute called ``amazing_attribute`` " -"and you want to open a google search directly with the input from that field." +"Using an user filter can be a good idea if you only require a small subset " +"of your LDAP users in Zammad." msgstr "" -#: ../system/objects/types.rst:357 -msgid "" -"Providing the link-template field below allows you to do so: ``https://www." -"google.com/search?q=#{ticket.amazing_attribute}``" +#: ../system/integrations/ldap/manage.rst:42 +msgid "This especially affects inactive users" msgstr "" -#: ../system/objects/types.rst:362 +#: ../system/integrations/ldap/manage.rst:34 msgid "" -"You can use any :doc:`Zammad variable ` as long as it's " -"available in the moment you need it." +"As every LDAP behaves differently on which attributes and how they are set, " +"Zammad doesn't care about any flags." msgstr "" -#: ../system/objects/types.rst:365 +#: ../system/integrations/ldap/manage.rst:37 msgid "" -"As a result, you are redirected to Google with a search for the value of the " -"attribute, if you click on the button in the ticket (as you can see in the " -"screencast above)." +"Users that no longer are returned by your LDAP source will automatically be " +"set to inactive. Zammad assumes that the user was deactivated." msgstr "" -#: ../system/packages.rst:2 -msgid "Packages" +#: ../system/integrations/ldap/manage.rst:41 +msgid "" +"Users will never be removed automatically! If you want to remove obsolete " +"users, use :doc:`/system/data-privacy`." msgstr "" -#: ../system/packages.rst:4 -msgid "That's the package management-area." +#: ../system/integrations/ldap/manage.rst:46 +msgid "Active Directory admins" msgstr "" -#: ../system/packages.rst:6 -msgid "Individual add-ons for Zammad can be installed and managed here." +#: ../system/integrations/ldap/manage.rst:45 +msgid "" +"Active Directories are quite specific on how to filter for active users only " +"- please see the `Microsoft documentation `_ for more " +"information." msgstr "" -#: ../system/sessions.rst:2 -msgid "Sessions" +#: ../system/integrations/ldap/manage.rst:51 +msgid "" +"*Do not* manually write pathes of either LDAP attributes or groups. If " +"Zammad does not display them, it either cannot find them or you have a lot " +"of users that don't have the attributes populated." msgstr "" -#: ../system/sessions.rst:4 +#: ../system/integrations/ldap/manage.rst:55 msgid "" -"Sessions management allows reviewing currently known user sessions and " -"allows to end these. The session timeout is affected by :ref:" -"`security_session_timeout` configurations from security settings." +"Zammad will always only return attributes that are filled - this reduces the " +"returned list of attributes greatly." msgstr "" -#: ../system/sessions.rst:None -msgid "Screenshot showing Zammad's session management" +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing how to add a new LDAP source" msgstr "" -#: ../system/sessions.rst:13 -msgid "Zammad will provide the following information:" +#: ../system/integrations/ldap/manage.rst:63 +msgid "" +"If your LDAP system doesn't allow anonymous bind, Zammad detects it and " +"provides you an editable \"Base DN\" *text* field instead of a prefilled " +"*select* field." msgstr "" -#: ../system/sessions.rst:16 -msgid "" -"The user account this session entry belongs to. It can be normal if a user " -"has several sessions in the list. This can be due to changed browser " -"information or if you use e.g. single sign on methods where the user does " -"not use the log off button." +#: ../system/integrations/ldap/manage.rst:81 +msgid "Review or edit existing source" msgstr "" -#: ../system/sessions.rst:22 -msgid "Browser" +#: ../system/integrations/ldap/manage.rst:68 +msgid "" +"Clicking on a LDAP source will provide a configuration and mapping overview." msgstr "" -#: ../system/sessions.rst:22 -msgid "The browser agent communicated to Zammad." +#: ../system/integrations/ldap/manage.rst:70 +msgid "" +"If needed you can then use the *Change* button to update either the name, " +"active state or the whole configuration. If you're changing the whole " +"configuration, the dialogue will be identical to the source creation." msgstr "" -#: ../system/sessions.rst:40 -msgid "Location" +#: ../system/integrations/ldap/manage.rst:76 +msgid "" +"Did your LDAP server change? Different LDAP servers have different " +"structures and default attributes. This causes the LDAP synchronization to " +"likely fail. Consider removing the affected source and re-add it." msgstr "" -#: ../system/sessions.rst:25 -msgid "" -"The anticipated location based on the users IP address. Depending on the IP " -"address the result shown may differ. This option depends on :doc:`/settings/" -"system/services`." +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing the update of the source name." msgstr "" -#: ../system/sessions.rst:29 -msgid "The following information can be shown:" +#: ../system/integrations/ldap/manage.rst:89 +msgid "Re-arrange LDAP source's order" msgstr "" -#: ../system/sessions.rst:33 -msgid "IP address" +#: ../system/integrations/ldap/manage.rst:84 +msgid "" +"You can change the synchronization order for each source at any time. Zammad " +"will synchronize the sources from top to bottom." msgstr "" -#: ../system/sessions.rst:32 +#: ../system/integrations/ldap/manage.rst:0 msgid "" -"Either if you set *Geo IP services* to inactive or you're using internal IP " -"address which do not provide location information." +"Screencasting showing how to change the source order by using\n" +"drag and drop." msgstr "" -#: ../system/sessions.rst:40 -msgid "Country (or Country + City)" +#: ../system/integrations/ldap/manage.rst:101 +msgid "Remove a source" msgstr "" -#: ../system/sessions.rst:36 +#: ../system/integrations/ldap/manage.rst:92 msgid "" -"If *Geo IP services* is enabled only. Depends on how detailed the available " -"IP address information are." +"If you no longer need the a LDAP source or simply want to start over, you " +"can remove them at any time. This will not remove synchronized users, data " +"synchronized or permissions." msgstr "" -#: ../system/sessions.rst:39 +#: ../system/integrations/ldap/manage.rst:98 msgid "" -"Be aware that results can be inaccurate - this technically is not an error." +"Not sure if you'd need the source later on? Set the source to inactive " +"instead of removing it - see *Review or edit existing source* for more." msgstr "" -#: ../system/sessions.rst:43 -msgid "Age" +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing how to remove LDAP sources." msgstr "" -#: ../system/sessions.rst:43 -msgid "Provides the time when the session initially has been created." +#: ../system/integrations/pgp/index.rst:2 +msgid "PGP" msgstr "" -#: ../system/sessions.rst:50 -msgid "Update" +#: ../system/integrations/pgp/index.rst:7 +msgid "" +"Pretty Good Privacy (PGP) is another method for secure email communication. " +"With PGP, you can exchange **signed** and **encrypted** messages with others." msgstr "" -#: ../system/sessions.rst:46 -msgid "" -"Provides the time the user used this session to open Zammad. This timestamp " -"is only updated if the user e.g. reloads, not during normal work on tickets." +#: ../system/integrations/pgp/index.rst:13 +#: ../system/integrations/smime/index.rst:17 +msgid "Signing" msgstr "" -#: ../system/sessions.rst:50 -msgid "This timestamp is being used for the session timeout." +#: ../system/integrations/pgp/index.rst:11 +msgid "is a proof that a message hasn't been manipulated on its way." msgstr "" -#: ../system/sessions.rst:53 +#: ../system/integrations/pgp/index.rst:13 msgid "" -"Use the delete button to remove a single session on behalf of your user." +"In other words, it guarantees message **integrity** and **authenticity**." msgstr "" -#: ../system/subscription/billing.rst:2 -msgid "Billing" +#: ../system/integrations/pgp/index.rst:19 +#: ../system/integrations/smime/index.rst:22 +msgid "Encryption" msgstr "" -#: ../system/subscription/billing.rst:4 +#: ../system/integrations/pgp/index.rst:16 +#: ../system/integrations/smime/index.rst:20 msgid "" -"Within the billing tab you can control all billing relevant information like " -"invoices, billing address and the option to cancel your subscription." -msgstr "" - -#: ../system/subscription/billing.rst:33 -msgid "Billing information" +"scrambles a message so that it can only be unscrambled by the intended " +"recipient." msgstr "" -#: ../system/subscription/billing.rst:8 +#: ../system/integrations/pgp/index.rst:19 msgid "" -"All adjusted billing information below only affect future invoices. If your " -"invoice was issued wrong, please contact `our sales team `_." +"In other words, it guarantees message **privacy** and **data security**." msgstr "" -#: ../system/subscription/billing.rst:14 -msgid "Billing address" +#: ../system/integrations/pgp/index.rst:25 +msgid "Screenshot of ticket creation with encrypt and sign buttons" msgstr "" -#: ../system/subscription/billing.rst:13 +#: ../system/integrations/pgp/index.rst:25 msgid "" -"Provide your company address here, make sure to include the companies name " -"in case required. This address will be referenced on your invoice." +"Once PGP has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " +"appear in the ticket composer." msgstr "" -#: ../system/subscription/billing.rst:18 -msgid "VAT ID" +#: ../system/integrations/pgp/index.rst:28 +msgid "**Sign button not visible?**" msgstr "" -#: ../system/subscription/billing.rst:17 +#: ../system/integrations/pgp/index.rst:30 msgid "" -"Provide your VAT ID here. If applicable your invoice will not contain German " -"VAT. Please make sure to pay the VAT in your country as required." +"Please note that the signing of emails is based on the outgoing email " +"account. That means you have to choose a group with a sender email account, " +"which has a private key assigned." msgstr "" -#: ../system/subscription/billing.rst:27 -msgid "Billing Email Address" +#: ../system/integrations/pgp/index.rst:35 +msgid "Handling of Keys" msgstr "" -#: ../system/subscription/billing.rst:21 +#: ../system/integrations/pgp/index.rst:36 msgid "" -"Usually the instance owner (the person that registered the instance) will " -"receive all emails including the invoices. In case you have your own billing " -"department, you can provide their email address here." +"To use the PGP function, you have to enable the integration (PGP) by " +"switching the toggle to *enabled*." msgstr "" -#: ../system/subscription/billing.rst:25 +#: ../system/integrations/pgp/index.rst:39 msgid "" -"All billing relevant information will then be sent to this email address." +"You can add keys by clicking the *add key* button. The keys can be imported " +"from a file or you can paste the content of the key in the text box." msgstr "" -#: ../system/subscription/billing.rst:27 -msgid "Invoices are sent as attachment (PDF) to this email address." +#: ../system/integrations/pgp/index.rst:42 +msgid "**Which keys do I have to import?**" msgstr "" -#: ../system/subscription/billing.rst:29 +#: ../system/integrations/pgp/index.rst:44 msgid "" -"Don't forget to press the *Submit* button after you changed above settings." +"For **signing** *outgoing* emails, you have to import the private key of " +"your Zammad email account." msgstr "" -#: ../system/subscription/billing.rst:0 +#: ../system/integrations/pgp/index.rst:47 msgid "" -"Screenshot showing options for billing information within the\n" -"subscription menu" -msgstr "" - -#: ../system/subscription/billing.rst:70 -msgid "Payment history" +"For **encrypting** *outgoing* emails, you have to import the public key of " +"the customer's email account." msgstr "" -#: ../system/subscription/billing.rst:36 +#: ../system/integrations/pgp/index.rst:50 msgid "" -"The payment history will display a history of all paid invoices. At this " -"point you can also download these in case you need them again." +"For **verifying the signature** of signed *incoming* emails, you have to " +"import the public key of the customer." msgstr "" -#: ../system/subscription/billing.rst:41 +#: ../system/integrations/pgp/index.rst:53 msgid "" -"You will only find *paid* invoices here. Invoices that are to be billed are " -"not available before the payment is completed." +"For **decrypting** of encrypted *incoming* emails, you have to import the " +"private key of your Zammad email account." msgstr "" -#: ../system/subscription/billing.rst:46 -msgid "Date" +#: ../system/integrations/pgp/index.rst:57 +msgid "Import Keys From a File" msgstr "" -#: ../system/subscription/billing.rst:46 -msgid "Date of the invoice creation." +#: ../system/integrations/pgp/index.rst:58 +msgid "You can import keys from a file in the section **Upload key**:" msgstr "" -#: ../system/subscription/billing.rst:49 -msgid "Amount" +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of adding a key via file" msgstr "" -#: ../system/subscription/billing.rst:49 -msgid "Invoice total including VAT if applicable." +#: ../system/integrations/pgp/index.rst:64 +msgid "" +"**Supported file formats:** ASCII-armor as well as binary GPG format " +"(basically any GPG supported key format) is supported here." msgstr "" -#: ../system/subscription/billing.rst:52 -msgid "" -"Contains contract period (monthly or yearly) and hosted plan for the " -"subscription period in question." +#: ../system/integrations/pgp/index.rst:68 +msgid "Import Keys by Pasting the Content" msgstr "" -#: ../system/subscription/billing.rst:63 -msgid "Payment method / Service period" +#: ../system/integrations/pgp/index.rst:69 +msgid "You can also paste the key's content in the section **paste key**:" msgstr "" -#: ../system/subscription/billing.rst:56 -msgid "" -"Used bank account or credit card as well as the subscription period the " -"invoice is about." +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of adding a key via pasting" msgstr "" -#: ../system/subscription/billing.rst:61 +#: ../system/integrations/pgp/index.rst:75 msgid "" -"It might happen that the invoice date and subscription period differ. This " -"is nothing to worry about, the subscription periods will be accounted later " -"on." +"**Supported format:** Please note that only ASCII-armor is supported here." msgstr "" -#: ../system/subscription/billing.rst:67 -msgid "Receipt" +#: ../system/integrations/pgp/index.rst:78 +msgid "Deleting Keys" msgstr "" -#: ../system/subscription/billing.rst:66 +#: ../system/integrations/pgp/index.rst:79 msgid "" -"Use the arrow to download the invoice in question. You can download all " -"available invoices any time you need to here!" +"If you want to delete a specific key, you can do it by clicking on the menu " +"in the *actions* column and select **delete**:" msgstr "" -#: ../system/subscription/billing.rst:0 -msgid "Screenshot showing payment history of a hosted instance" +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of deleting a key" msgstr "" -#: ../system/subscription/billing.rst:94 -msgid "Do you want to cancel your subscription?" +#: ../system/integrations/pgp/index.rst:88 +msgid "Downloading Keys" msgstr "" -#: ../system/subscription/billing.rst:73 +#: ../system/integrations/pgp/index.rst:89 msgid "" -"In case you no longer want to use Zammad's SaaS, you can cancel your " -"subscription by using the red *Yes, please cancel my subscription* button." +"If you want to download your keys, you can do this as well via corresponding " +"action buttons. Depending on the key, you can choose wether you want to " +"download the private or the public key." msgstr "" -#: ../system/subscription/billing.rst:76 -msgid "" -"Your subscription will end the day after your trial or billing period ends." +#: ../system/integrations/pgp/index.rst:95 +#: ../system/integrations/smime/manage-certificates.rst:76 +msgid "Default Behavior" msgstr "" -#: ../system/subscription/billing.rst:80 +#: ../system/integrations/pgp/index.rst:96 msgid "" -"We will remind you about your cancelled subscription several times up front. " -"After the subscription ended all instance data will be removed. A restore " -"*is not* possible after that point!" +"Here you can adjust on per group basis, if *sign* and *encryption* is on or " +"off by default. Please be aware, that agents can always override the setting " +"for each individual article." msgstr "" -#: ../system/subscription/billing.rst:0 -msgid "Screencast showing how to cancel a subscription" +#: ../system/integrations/pgp/index.rst:None +msgid "Adjusting default behavior on per group basis" msgstr "" -#: ../system/subscription/billing.rst:87 -msgid "**😖 Cancelled by accident?**" +#: ../system/integrations/pgp/index.rst:107 +msgid "" +"Here you can see the last actions regarding signing and encryption and if " +"they were successful." msgstr "" -#: ../system/subscription/billing.rst:89 -msgid "" -"You can always undo the cancellation via the *Yes, undo the cancellation of " -"my subscription* button up to the last subscription day!" +#: ../system/integrations/pgp/index.rst:117 +msgid "**Sign button is not visible, but keys are imported.**" +msgstr "" + +#: ../system/integrations/pgp/index.rst:115 +msgid "Did you choose a group in the ticket?" msgstr "" -#: ../system/subscription/billing.rst:0 +#: ../system/integrations/pgp/index.rst:116 msgid "" -"Screenshot showing a red button to cancel the subscription\n" -"cancellation" +"Did you import a private key for the email adress, which is used for " +"outgoing emails in the group?" msgstr "" -#: ../system/subscription/index.rst:2 -msgid "Subscription (SaaS)" +#: ../system/integrations/pgp/index.rst:122 +msgid "**How to obtain keys?**" msgstr "" -#: ../system/subscription/index.rst:4 +#: ../system/integrations/pgp/index.rst:120 msgid "" -"The subscription settings page allows you to configure your instances " -"package and number of agents required." +"You can create them yourself! There are some good tutorials on the web on " +"how to create them. Providing keys to Zammad is a prerequisite to use the " +"PGP feature." msgstr "" -#: ../system/subscription/index.rst:9 -msgid "" -"This setting section is only available for Hosted setups. If you're looking " -"for on premise support contracts, please see the `Zammad pricing page " -"`_." +#: ../system/integrations/pgp/index.rst:127 +msgid "**It says a passphrase is needed, but I haven't got one.**" msgstr "" -#: ../system/subscription/index.rst:20 +#: ../system/integrations/pgp/index.rst:125 msgid "" -"The subscription section currently consists of two tabs: Plan & Billing. For " -"your overview we've divided those two tabs into independent sub pages:" +"If the key is secured with a passphrase, you have to provide it for the " +"import in Zammad. It is possible that keys may have an empty passphrase. " +"However, this is *not* recommended." msgstr "" -#: ../system/subscription/index.rst:25 -msgid ":doc:`💰 Subscription plan `" +#: ../system/integrations/pgp/index.rst:132 +msgid "**How do my customers get my new key?**" msgstr "" -#: ../system/subscription/index.rst:24 +#: ../system/integrations/pgp/index.rst:130 msgid "" -"Everything affecting your instance subscription functions like number of " -"agents, package and payment method." +"You have to provide your **public** key in advance. Your customer also has " +"to configure PGP in their email workflow and import your public key. The " +"other way round, you have to get the public key of your customer and have to " +"import it to Zammad." +msgstr "" + +#: ../system/integrations/slack.rst:2 +msgid "Slack" msgstr "" -#: ../system/subscription/index.rst:28 -msgid ":doc:`🧾 Subscription billing `" +#: ../system/integrations/slack.rst:4 +msgid "**⚠️ Deprecation warning ⚠️**" msgstr "" -#: ../system/subscription/index.rst:28 +#: ../system/integrations/slack.rst:6 msgid "" -"Everything regarding billing address, invoices and account cancellation." +"Zammad 7 will no longer support this dedicated Slack integration. It is " +"recommended to switch to :doc:`pre-defined webhooks ` instead. Existing Slack integrations should " +"be migrated manually before this feature is dropped." msgstr "" -#: ../system/subscription/index.rst:33 -msgid "FAQ" +#: ../system/integrations/slack.rst:14 +msgid "" +"In order to use this feature, please add a new Slack app to your Workspace. " +"The App you need is called ``Incoming WebHooks`` ." msgstr "" -#: ../system/subscription/index.rst:37 -msgid "I set up a trial account but am missing functions to test" +#: ../system/integrations/slack.rst:18 +msgid "Why Do I Need This Feature?" msgstr "" -#: ../system/subscription/index.rst:36 +#: ../system/integrations/slack.rst:20 msgid "" -"The trial instance is running within the professional package allowing up to " -"three agents." +"If you're already using Slack for your team communication, you'll love this " +"feature! Our Slack integration can push ticket notifications about the last " +"ticket article based on the following events:" msgstr "" -#: ../system/subscription/index.rst:40 -msgid "Can I change package within the trial?" +#: ../system/integrations/slack.rst:24 +msgid "on Ticket creation" msgstr "" -#: ../system/subscription/index.rst:40 -msgid "No. As soon as the package is changed the subscription begins." +#: ../system/integrations/slack.rst:25 +msgid "on Ticket updates" msgstr "" -#: ../system/subscription/index.rst:45 -msgid "What happens to my trial instance after the trial period ended?" +#: ../system/integrations/slack.rst:26 +msgid "on reached reminders" msgstr "" -#: ../system/subscription/index.rst:43 -msgid "" -"Your instance will automatically be canceled for you. Please see *What " -"happens to my instance after it has been canceled?* for more." +#: ../system/integrations/slack.rst:27 +msgid "a Ticket has escalated" msgstr "" -#: ../system/subscription/index.rst:58 -msgid "What happens to my instance after it has been canceled?" +#: ../system/integrations/slack.rst:28 +msgid "a Ticket is going to escalate" msgstr "" -#: ../system/subscription/index.rst:48 -msgid "That depends slightly on your instance state:" +#: ../system/integrations/slack.rst:30 +msgid "" +"Zammad will provide the Ticket title, a direct link to the Ticket, the event " +"type (creation, updated, escalation), the customer, time and the last " +"article that has triggered the notification." msgstr "" -#: ../system/subscription/index.rst:54 -msgid "Trial instance" +#: ../system/integrations/slack.rst:34 +msgid "" +"This will give you further options, as you can see e.g. escalating tickets " +"that are assigned to an agent that's e.g. absent. You can interact faster, " +"as you might see problems earlier (or even before the problem gets one)." msgstr "" -#: ../system/subscription/index.rst:51 +#: ../system/integrations/slack.rst:38 msgid "" -"If you're still on trial, we will ice your instance and remind you once " -"again about your instance. We then will wait some days and remove your " -"instance from our system. This is the last time we will inform you by Email." +"If needed and wanted, you can even discuss directly about the topic before " +"sending an answer to the customer. Another possible use case would be a " +"agent monitoring new agents and their answers to tickets." msgstr "" -#: ../system/subscription/index.rst:58 -msgid "Paid instance" +#: ../system/integrations/slack.rst:44 +msgid "Configure the Integration" msgstr "" -#: ../system/subscription/index.rst:57 +#: ../system/integrations/slack.rst:46 msgid "" -"If you're a paying customer and canceled your subscription, the instance " -"removal will take place the day after your last subscription day." +"First of all, please go to your slack workspace - go to administration => " +"Manage Apps. If you don't have an app yet, you can simply add a new one - " +"just search for ``Incoming WebHooks`` and customize the app to your needs." msgstr "" -#: ../system/subscription/index.rst:60 -msgid "Can removed instances be restored?" +#: ../system/integrations/slack.rst:50 +msgid "" +"Choose (or create) the channel Zammad should post it's information to and " +"press on \"Add Incoming WebHooks integration\". If you're ready, copy the " +"provided WebHook URL and go to your Zammad installation." msgstr "" -#: ../system/subscription/index.rst:61 -msgid "No. Once your instance has been removed, a restoration is not possible." +#: ../system/integrations/slack.rst:56 +msgid "" +"You need administrative rights on the Slack Workspace. The link to the app " +"directory is normally ``https://[workspace-name].slack.com/apps`` ." msgstr "" -#: ../system/subscription/plan.rst:2 ../system/subscription/plan.rst:38 -msgid "Plan" +#: ../system/integrations/slack.rst:63 +msgid "" +"To configure the slack integration, log in to Zammad and go to Integrations " +"(System) => Slack in the admin panel." msgstr "" -#: ../system/subscription/plan.rst:16 -msgid "Subscription" +#: ../system/integrations/slack.rst:66 +msgid "" +"Here you can choose on what evens Zammad should post information about a " +"ticket to your Slack channel. Next you need to device what groups shall be " +"affected by this, as anybody with access to that specific Slack channel can " +"read at least parts of the ticket this might be a privacy issue, if you " +"select the wrong groups. The username is simply the name that Zammad uses as " +"display name inside the Slack chat. The channel defines the Slack channel " +"the information is being posted in. As last option, you can set a custom " +"icon for posting to slack." msgstr "" -#: ../system/subscription/plan.rst:5 +#: ../system/integrations/slack.rst:74 msgid "" -"On the top of the subscription summary you'll find the number of used and " -"available (booked) agent seats. By using the *see more* link you can also " -"expand an agent list to see the currently configured active agents. This " -"list *does not* count accounts with admin permissions only." +"When you're ready, just hit \"Submit\" and enable the integration. Zammad " +"will now post new ticket information based on the trigger you chose. Below " +"the options you have the recent log that shows the latest requests to Slack " +"for debugging if needed." msgstr "" -#: ../system/subscription/plan.rst:0 +#: ../system/integrations/slack.rst:81 msgid "" -"Within subscription you can always see how many agents are still\n" -"available to add and who uses the seats." +"If you leave the Icon URL empty, Zammad will use the Zammad logo instead. " +"The icon should be a square PNG file." msgstr "" -#: ../system/subscription/plan.rst:14 +#: ../system/integrations/slack.rst:90 msgid "" -"Learn more on how to manage your agents in general :doc:`here `." +"The following figure shows how it will look if you choose to receive updates " +"on created and updated tickets. On every post Zammad sends to the Slack " +"channel, you can create new threads to discuss about the new article." msgstr "" -#: ../system/subscription/plan.rst:19 +#: ../system/integrations/slack.rst:96 msgid "" -"This section gives you an overview of the available plans and their " -"functions / limits. If you require a more detailed table, check our " -"`detailed pricing table `_ for more." +"If you just want to keep track of soon escalating or already escalated " +"tickets, it will look the the following figure. Zammad changes the color in " +"front of the post so you can easily see the state of the ticket." msgstr "" -#: ../system/subscription/plan.rst:23 +#: ../system/integrations/slack.rst:102 msgid "" -"Your selection in this step will decide on the base agent price and e.g. " -"agent limits that might apply in the summary step." +"If you change the state, Zammad will also put information on what state the " +"ticket gets and (if pending state) the date until it pends. You'll also " +"recognize the color codes in front of posts on slack, as they are exact the " +"same the ticket state colors you'll see in Zammad!" msgstr "" -#: ../system/subscription/plan.rst:26 -msgid "" -"The green *Selected* button will also tell you what plan you're currently in." +#: ../system/integrations/smime/index.rst:2 +msgid "S/MIME" msgstr "" -#: ../system/subscription/plan.rst:30 +#: ../system/integrations/smime/index.rst:11 msgid "" -"Trial instances are running at Professional with 3 agents. The plan cannot " -"be changed during the trial for technical reasons, if you require more " -"agents for testing, please contact `our sales team `_ with a reason for the raise request." +"S/MIME is the most widely-supported method for secure email communication. " +"With S/MIME, you can exchange **signed** and **encrypted** messages with " +"others." msgstr "" -#: ../system/subscription/plan.rst:0 +#: ../system/integrations/smime/index.rst:15 msgid "" -"Screenshot showing three available packages for a hosted Zammad\n" -"instance" +"is proof that a message hasn't been tampered with or sent by an impersonator." msgstr "" -#: ../system/subscription/plan.rst:83 -msgid "Summary" +#: ../system/integrations/smime/index.rst:17 +msgid "" +"In other words, it guarantees a message's **integrity** and **authenticity**." msgstr "" -#: ../system/subscription/plan.rst:41 -msgid "" -"In this section you can adjust the settings of the previous selected plan." +#: ../system/integrations/smime/index.rst:22 +msgid "In other words, it guarantees **privacy** and **data security**." msgstr "" -#: ../system/subscription/plan.rst:45 -msgid "" -"Note that upgrading (more agents, higher package) is always possible, " -"however, downgrading will only happen when your billing period renews." +#: ../system/integrations/smime/index.rst:28 +msgid "Screencast demo of S/MIME features for both new tickets and replies" msgstr "" -#: ../system/subscription/plan.rst:49 +#: ../system/integrations/smime/index.rst:28 msgid "" -"Upgrading resets your billing period and existing credit will be deducted " -"from the new total." +"Once S/MIME has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " +"appear in the ticket composer." msgstr "" -#: ../system/subscription/plan.rst:58 -msgid "Billing cycle" +#: ../system/integrations/smime/index.rst:32 +msgid ":doc:`🔪 Prerequisites `" msgstr "" -#: ../system/subscription/plan.rst:53 +#: ../system/integrations/smime/index.rst:31 msgid "" -"You can choose between either monthly or yearly billing. The price per agent " -"will be cheaper if you decide for yearly billing." +"New to S/MIME? This section helps you to find certificate providers and " +"points out Limitations." msgstr "" -#: ../system/subscription/plan.rst:56 -msgid "" -"If you're still trying out things and are unsure of the right package for " -"your instance, you may want to choose monthly first and then upgrade to " -"yearly when you're sure." +#: ../system/integrations/smime/index.rst:35 +msgid ":doc:`📝 Manage Certificates `" msgstr "" -#: ../system/subscription/plan.rst:66 -msgid "Plan: (Starter|Professional|Plus) - Agents" +#: ../system/integrations/smime/index.rst:35 +msgid "Add and download certificates; configure group default behaviors." msgstr "" -#: ../system/subscription/plan.rst:61 -msgid "Choose the number of agents you require for your instance." +#: ../system/integrations/smime/index.rst:38 +msgid ":doc:`😦 Troubleshooting `" msgstr "" -#: ../system/subscription/plan.rst:63 -msgid "" -"Keep in mind that some packages may have agent limits. Depending on the " -"previous chosen package, you won't be able to exceed specific agent numbers. " -"Also note that setting less agents than currently configured is not possible." +#: ../system/integrations/smime/index.rst:38 +msgid "Took a wrong turn? About recent logs and common issues." msgstr "" -#: ../system/subscription/plan.rst:69 -msgid "Total" +#: ../system/integrations/smime/index.rst:43 +msgid "" +"For more details on how S/MIME integration works on the agent side, see the :" +"user-docs:`user docs `." msgstr "" -#: ../system/subscription/plan.rst:69 -msgid "This will be the net total you're going to be billed." +#: ../system/integrations/smime/manage-certificates.rst:2 +msgid "Manage Certificates" msgstr "" -#: ../system/subscription/plan.rst:71 +#: ../system/integrations/smime/manage-certificates.rst:4 msgid "" -"By using the *Update subscription* button, the instance package will be " -"adjusted immediately. If you didn't provide a payment method yet, Zammad " -"will request you to provide one at this point." +"S/MIME is **disabled by default**. Enable it to start adding certificates." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:10 +msgid "Dialogue to add new certificates or private keys" msgstr "" -#: ../system/subscription/plan.rst:77 +#: ../system/integrations/smime/manage-certificates.rst:10 msgid "" -"In case you're still within the trial period, this means that the trial will " -"be over immediately!" +"Manage certificates in the Admin Panel under **System > Integrations > S/" +"MIME**. Certificates may be pasted in as plain text or uploaded from a file." msgstr "" -#: ../system/subscription/plan.rst:80 -msgid "Down- or upgrading during the trial period *is not* possible." +#: ../system/integrations/smime/manage-certificates.rst:14 +msgid "Add Certificate Data" msgstr "" -#: ../system/subscription/plan.rst:0 -msgid "Screenshot showing payment options and a pricing summary" +#: ../system/integrations/smime/manage-certificates.rst:36 +msgid "Add Certificate" msgstr "" -#: ../system/subscription/plan.rst:99 -msgid "Payment method" +#: ../system/integrations/smime/manage-certificates.rst:17 +msgid "" +"Import public-key certificates for both your own organization and your " +"contacts." msgstr "" -#: ../system/subscription/plan.rst:86 -msgid "You can pay via credit card or SEPA mandate." +#: ../system/integrations/smime/manage-certificates.rst:19 +msgid "" +"You can also add a bunch of certificates in one go by providing a single " +"file with all relevant certificates." msgstr "" -#: ../system/subscription/plan.rst:91 -msgid "Credit card" +#: ../system/integrations/smime/manage-certificates.rst:22 +msgid "🕵️ **ALWAYS verify certificates in-person or over the phone!**" msgstr "" -#: ../system/subscription/plan.rst:89 +#: ../system/integrations/smime/manage-certificates.rst:24 msgid "" -"Simply follow the dialogue by clicking *authorize* and confirm -if required " -"by your bank- your consent to Zammad using your card for the payments." +"The whole point of signatures is to alert you when someone is trying to " +"pretend to be someone they're not. Never accept a certificate from someone " +"online without verifying it first." msgstr "" -#: ../system/subscription/plan.rst:95 -msgid "SEPA" +#: ../system/integrations/smime/manage-certificates.rst:28 +msgid "📇 **What about trusted certificate authorities?**" msgstr "" -#: ../system/subscription/plan.rst:94 +#: ../system/integrations/smime/manage-certificates.rst:30 msgid "" -"Provide the requested information of the bank account holder and update if " -"you're ready. You'll then receive an email with the SEPA mandate." +"In some cases (e.g. when dealing with large enterprises), you may be given a " +"certificate for an entire CA, rather than a single contact. Add it here to " +"trust *all* certificates issued by that CA." msgstr "" -#: ../system/subscription/plan.rst:97 +#: ../system/integrations/smime/manage-certificates.rst:35 msgid "" -"Technically there's also the possibility to pay via invoice, however - this " -"method only applies to a fairly low number of instances. Please contact `our " -"sales team `_ for more information." +"Commercial CAs can usually be verified online. Zammad does not include a " +"list of built-in, trusted CAs." msgstr "" -#: ../system/translations.rst:2 -msgid "Translations" +#: ../system/integrations/smime/manage-certificates.rst:57 +msgid "Add Private Key" msgstr "" -#: ../system/translations.rst:4 +#: ../system/integrations/smime/manage-certificates.rst:39 msgid "" -"Translations of Zammad are processed centrally in our `Weblate instance " -"`_. This allows non-developers to review " -"and update translation texts of the language they actually speak." +"Once you've added a public-key certificate, you can import its matching " +"private key." msgstr "" -#: ../system/translations.rst:9 +#: ../system/integrations/smime/manage-certificates.rst:42 msgid "" -"Your language is in an incomplete translation state or has typos? Please " -"consider helping us in sorting this out! All you need is either a GitHub " -"account or to register directly in our instance." +"Private keys are for **your own organization only**; never ask your contacts " +"for their private keys." msgstr "" -#: ../system/translations.rst:13 +#: ../system/integrations/smime/manage-certificates.rst:0 msgid "" -"Did you know? This is also where the documentation translations are handled. " -"🤓" +"S/MIME integration showing configured certificates and possible issues with " +"Logging" msgstr "" -#: ../system/translations.rst:15 +#: ../system/integrations/smime/manage-certificates.rst:50 msgid "" -"Have a look in our :docs:`contribution section ` in the system documentation to get started!" +"A note is displayed on certificates with a matching private key (see line 2)." msgstr "" -#: ../system/translations.rst:20 -msgid "Local Translations" +#: ../system/integrations/smime/manage-certificates.rst:52 +msgid "📤 **Certificates and private keys must be uploaded separately.**" msgstr "" -#: ../system/translations.rst:22 +#: ../system/integrations/smime/manage-certificates.rst:54 msgid "" -"Apart from these system translations, there's still local translations you " -"can manage. This is relevant if you added custom objects that require " -"translations or even custom states and priorities." +"If your certificate and private key are bundled together in the same file or " +"PEM block, import it twice (once using each button)." msgstr "" -#: ../system/translations.rst:None -msgid "Translation management screen within the admin menu" +#: ../system/integrations/smime/manage-certificates.rst:57 +msgid "Please note that bulk imports of private keys are not possible." msgstr "" -#: ../system/translations.rst:31 -msgid "Updating Translations" +#: ../system/integrations/smime/manage-certificates.rst:60 +msgid "Download Certificate Data" msgstr "" -#: ../system/translations.rst:33 +#: ../system/integrations/smime/manage-certificates.rst:62 msgid "" -"Because of how Zammad ships translations, the only way to update the system " -"translations is to update your Zammad installation. The benefit of this is " -"that you no longer need internet access during a Zammad upgrade as the " -"package has everything it requires already." +"You can download the earlier provided certificates and private keys at any " +"time from your Zammad instance." msgstr "" -#: ../system/translations.rst:39 -msgid "Translation of Custom Objects" +#: ../system/integrations/smime/manage-certificates.rst:65 +msgid "" +"Please note that passphrase-protected private keys stay protected and when " +"you download them, you have to know the passphrase to use them after " +"downloading." msgstr "" -#: ../system/translations.rst:41 -msgid "" -"No problem at all! You can customize any translation locally, even if it is " -"not initially provided by the system." +#: ../system/integrations/smime/manage-certificates.rst:73 +msgid "Dialogue to download certificates or private keys" msgstr "" -#: ../system/translations.rst:44 +#: ../system/integrations/smime/manage-certificates.rst:73 +msgid "Download stored certificates and their keys" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:78 msgid "" -"Translation is supported for a broad number of features, including but not " -"limited to custom:" +"The ticket composer will set all outgoing messages to **signed and " +"encrypted** by default (assuming the required certificates exist)." msgstr "" -#: ../system/translations.rst:47 -msgid "Object Attributes" +#: ../system/integrations/smime/manage-certificates.rst:82 +msgid "These defaults can be modified on a per-group basis:" msgstr "" -#: ../system/translations.rst:48 -msgid "Ticket Macros" +#: ../system/integrations/smime/manage-certificates.rst:None +msgid "Zammad allowing to choose the default behavior on per group basis" msgstr "" -#: ../system/translations.rst:49 -msgid "Ticket Overviews" +#: ../system/integrations/smime/manage-certificates.rst:89 +msgid "" +"Of course, agents can always manually change these settings on each email " +"they send out." msgstr "" -#: ../system/translations.rst:50 -msgid "Ticket Priorities" +#: ../system/integrations/smime/prerequisites.rst:4 +msgid "A certificate *and* private key for your own organization" msgstr "" -#: ../system/translations.rst:51 -msgid "Ticket States" +#: ../system/integrations/smime/prerequisites.rst:6 +msgid "" +"(Use this to ✒️ **sign outgoing messages** and 🔓 **decrypt incoming " +"messages**.)" msgstr "" -#: ../system/translations.rst:54 -msgid "Customizing Translations" +#: ../system/integrations/smime/prerequisites.rst:9 +msgid "" +"Certificates belonging your contacts, or their issuing certificate authority " +"(CA)" msgstr "" -#: ../system/translations.rst:56 +#: ../system/integrations/smime/prerequisites.rst:11 msgid "" -"Within the translation screen, simply click on the **New Translation** " -"button." +"(Use these to ✅ **verify incoming message signatures** and 🔒 **encrypt " +"outgoing messages**.)" msgstr "" -#: ../system/translations.rst:None -msgid "New translation dialog" +#: ../system/integrations/smime/prerequisites.rst:14 +msgid "🙋 **I'm new to S/MIME. Where can I get a certificate?**" msgstr "" -#: ../system/translations.rst:62 +#: ../system/integrations/smime/prerequisites.rst:16 msgid "" -"In the dialog you can immediately enter the exact translation source (if you " -"know it) and your custom translation text for it and click **Submit**." +"The easiest way to get certificates is to buy an annual subscription through " +"a commercial CA, such as:" msgstr "" -#: ../system/translations.rst:65 +#: ../system/integrations/smime/prerequisites.rst:19 msgid "" -"Alternatively, try to search for translation suggestions in the list below. " -"Selecting an item from the list will pre-fill the translation source for you " -"and then you can just enter your custom translation." +"`Sectigo (formerly Comodo) `_" msgstr "" -#: ../system/translations.rst:69 -msgid "" -"The target language will always default to your current language selection. " -"If you need to translate for a different language, simply change the " -"selection before submitting." +#: ../system/integrations/smime/prerequisites.rst:20 +msgid "`Secorio `_" msgstr "" -#: ../system/translations.rst:73 -msgid "" -"All your custom translations will show up in the overview table when added. " -"And they will even persist across Zammad updates!" +#: ../system/integrations/smime/prerequisites.rst:21 +msgid "`GlobalSign `_" msgstr "" -#: ../system/translations.rst:76 -msgid "" -"Make sure to reload your browser if a translated string is not displayed." +#: ../system/integrations/smime/prerequisites.rst:23 +msgid "(Zammad is not affiliated with these CAs in any way.)" msgstr "" -#: ../system/translations.rst:80 -msgid "Reverting to Original Translations" +#: ../system/integrations/smime/prerequisites.rst:25 +msgid "" +"You can also generate your own self-signed certificates, but the process is " +"complicated and usually 🙅 **involves extra work for your contacts**." msgstr "" -#: ../system/translations.rst:82 +#: ../system/integrations/smime/prerequisites.rst:29 msgid "" -"If you want to revert a custom translation to original text, simply use the " -"appropriate action within the row of the overview table." +"Bear in mind that 🤝 **S/MIME only works if the other party is using it, too." +"**" msgstr "" -#: ../system/translations.rst:85 +#: ../system/integrations/smime/prerequisites.rst:32 +msgid "Certificate and Private Key Checks on Upload" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:34 msgid "" -"Depending on the type of the translation source, the action has a slightly " -"different name:" +"The certificate and public key validation is based on the ``X509v3`` " +"extensions." msgstr "" -#: ../system/translations.rst:88 -msgid "**Reset** for customized system translations" +#: ../system/integrations/smime/prerequisites.rst:49 +msgid "Uploading a *client certificate*?" msgstr "" -#: ../system/translations.rst:89 -msgid "**Remove** for customized local translations" +#: ../system/integrations/smime/prerequisites.rst:41 +msgid "The following attributes are required then:" msgstr "" -#: ../system/translations.rst:91 -msgid "" -"In both cases, the action will remove the customized translation after a " -"confirmation." +#: ../system/integrations/smime/prerequisites.rst:39 +msgid "Subject Alternative Name (at least one email address has to be present)" msgstr "" -#: ../system/translations.rst:None -msgid "Screenshot showing the location of the Remove action" +#: ../system/integrations/smime/prerequisites.rst:40 +msgid "Key Usage (``Digital Signature`` and/or ``Key Encipherment``)" msgstr "" -#: ../system/translations.rst:99 -msgid "Inline Translations" +#: ../system/integrations/smime/prerequisites.rst:41 +msgid "Public key algorithm (either ``RSA`` or ``EC``)" msgstr "" -#: ../system/translations.rst:101 +#: ../system/integrations/smime/prerequisites.rst:43 msgid "" -"If you prefer a more hands-on approach, you can activate the inline or on-" -"screen translation feature by pressing ``ctrl`` + ``alt`` + ``t`` at any " -"time and on any screen." +"The Extended Key Usage attribute is optional. If the certificate provides " +"the named attribute, than it must contain the value ``E-mail Protection``." msgstr "" -#: ../system/translations.rst:105 +#: ../system/integrations/smime/prerequisites.rst:46 msgid "" -"All customizable translation texts will be highlighted for you on the " -"screen. Just click into the highlighted area and update the text in place." +"Please note that any usable email adress has to be prefixed with ``email:`` " +"or ``rfc822:``." msgstr "" -#: ../system/translations.rst:None -msgid "Inline translation mode activated for the Overview screen" +#: ../system/integrations/smime/prerequisites.rst:49 +msgid "The named public key algorithms are mandatory for private keys as well." msgstr "" -#: ../system/translations.rst:112 +#: ../system/integrations/smime/prerequisites.rst:54 +msgid "Uploading a *CA certificate*?" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:52 msgid "" -"When finished editing, simply press ``ctrl`` + ``alt`` + ``t`` again to " -"deactivate." +"In the case of an uploaded CA certificate, providing the value ``CA:TRUE`` " +"in the attribute *Basic Contstraints*, the previously mentioned attributes " +"are not verified." msgstr "" -#: ../system/translations.rst:117 +#: ../system/integrations/smime/prerequisites.rst:56 msgid "" -"Even though it's available on any screen, the inline translation feature " -"requires admin permissions. It works only for the current language " -"selection. If you need to translate a different language, first change the " -"language in your :user-docs:`profile settings `." +"In general, the usage of any expired (``Not After``) or not yet valid (``Not " +"Before``) certificate is denied for outgoing emails." msgstr "" -#: ../system/variables.rst:2 -msgid "Variables" +#: ../system/integrations/smime/prerequisites.rst:59 +msgid "Example certificate:" msgstr "" -#: ../system/variables.rst:4 +#: ../system/integrations/smime/prerequisites.rst:85 msgid "" -"Please note that this is just an overview of available variables. It might " -"be incomplete or variables might not be available within some functions. If " -"you're missing variables or are not sure if something is not working as " -"expected, feel free to ask over at the `Community `_." +"Please note that Zammad will distrust senders by default. This means that " +"you're always required to provide certificate data, no matter if for signing " +"or encrypting." msgstr "" -#: ../system/variables.rst:10 -msgid "" -"Variables can be called by typing ``::`` (just like text modules in the " -"frontend), as long as you're in a supported text field within the backend. " -"Zammad will display all variables being available within this context and " -"replace it to the variable as soon as you selected an entry." +#: ../system/integrations/smime/prerequisites.rst:89 +msgid "This is by design and can't be adjusted." msgstr "" -#: ../system/variables.rst:15 +#: ../system/integrations/smime/troubleshooting.rst:4 msgid "" -"You have an empty field which you referenced and it appears as ``-``? That's " -"currently working as designed - you might want to ensure that these fields " -"always have a value." +"All of the system's latest S/MIME activity is displayed in the **Recent " +"Logs** section." msgstr "" -#: ../system/variables.rst:20 -msgid "Variable Categories" +#: ../system/integrations/smime/troubleshooting.rst:11 +msgid "Sample entries of in- and outgoing S/MIME related emails." msgstr "" -#: ../system/variables.rst:31 -msgid "Wait, What About Custom Objects?" +#: ../system/integrations/smime/troubleshooting.rst:11 +msgid "" +"Logs report the status and details of all mail, both incoming and outgoing, " +"that used signing/verification or encryption/decryption." msgstr "" -#: ../system/variables.rst:33 +#: ../system/integrations/smime/troubleshooting.rst:14 msgid "" -"Good point! Of course, we can't predict what objects you might create, but " -"we can give you a hint on how to put the puzzle together to get your custom " -"values." +"This log does **not** include email sent by :doc:`triggers ` or the :doc:`scheduler `. For those, check your " +"``production.log``." +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:20 +msgid "Common Issues" +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:30 +msgid "I received a signed/encrypted email before I set up S/MIME integration" msgstr "" -#: ../system/variables.rst:36 +#: ../system/integrations/smime/troubleshooting.rst:23 msgid "" -"For this, we'll talk about the inner part of the variable (so everything " -"within ``#{}``), please put the outer part around to have a valid variable. " -"The first part of the variable name consist of the object type. Currently " -"these are:" +"No problem. Once S/MIME has been enabled and the appropriate certificates " +"have been added, agents will be prompted to retry verification/decryption on " +"matching emails." msgstr "" -#: ../system/variables.rst:41 -msgid "Ticket (``ticket``)" +#: ../system/integrations/smime/troubleshooting.rst:0 +msgid "Screenshot of user prompt to retry decryption" msgstr "" -#: ../system/variables.rst:42 -msgid "User (``user``)" +#: ../system/integrations/smime/troubleshooting.rst:38 +msgid "The 🔒 **Encrypt** button is disabled" msgstr "" -#: ../system/variables.rst:43 -msgid "Organization (``organization``)" +#: ../system/integrations/smime/troubleshooting.rst:33 +msgid "Have you added the recipient's certificate?" msgstr "" -#: ../system/variables.rst:44 -msgid "Group (``group``)" +#: ../system/integrations/smime/troubleshooting.rst:34 +msgid "Are you sure the recipient's certificate is valid?" msgstr "" -#: ../system/variables.rst:46 -msgid "" -"The second part is the name of the object. This is the name you define " -"during object creation and can be found within the object menu at any time. " -"The first and second part of a variable is divided by a point, e.g.: " -"``ticket.number`` which will in total be ``#{ticket.number}``." +#: ../system/integrations/smime/troubleshooting.rst:35 +msgid "Have you checked your ``production.log`` for more details?" msgstr "" -#: ../system/variables.rst:51 +#: ../system/integrations/smime/troubleshooting.rst:37 msgid "" -"Now, in some situations it's possible that you'll need to use a third part. " -"The best example for such a situation would be a ``select`` or ``tree-" -"select`` field which will by default return the key value, not it's display " -"name. For this, just extend your variable with ``.value``. This will result " -"in ``#{ticket.select.value}``." +"If encryption doesn't work in the composer, it won't work in :doc:`triggers " +"` or the :doc:`scheduler ` either!" msgstr "" -#: ../system/variables.rst:60 -msgid "Using Translated Variables" +#: ../system/integrations/smime/troubleshooting.rst:42 +msgid "The ✅ **Sign** button is disabled" msgstr "" -#: ../system/variables.rst:62 +#: ../system/integrations/smime/troubleshooting.rst:41 msgid "" -"If you want to use a translated variable in triggers or schedulers, you can " -"extend the placeholder like this: ``#{t(ticket.state.name)}``. The ``t`` " -"tells Zammad to search for fitting translated strings. The used output " -"language is based on the system language of Zammad which you can set in the " -"admin panel under :doc:`/settings/branding` or based on the selected locale " -"in the trigger/scheduler edit dialog." +"Have you added **both the certificate and private key** for your " +"organization?" msgstr "" -#: ../system/variables.rst:69 +#: ../system/integrations/smime/troubleshooting.rst:42 msgid "" -"A possible use-case: you want to send your customers updates on tickets via " -"trigger or scheduler which should include the state of the ticket. Using the " -"default ``#{ticket.state.name}`` (without the translation flag ``t()``) " -"would lead to the output of the original (english) name of the state." +"Does the email address on the certificate match the email address of the " +"agent/group composing the email?" msgstr "" -#: ../system/variables.rst:75 -msgid "Date and Time Formatting" +#: ../system/integrations/smime/troubleshooting.rst:45 +msgid "Error: “Fingerprint already taken”" msgstr "" -#: ../system/variables.rst:77 -msgid "" -"The system (trigger/scheduler selected) locale and timezone predefines a " -"default format of date and timestamp. This format is customizable by using " -"the ``dt()`` method." +#: ../system/integrations/smime/troubleshooting.rst:45 +msgid "Are you sure you haven't added this certificate already?" msgstr "" -#: ../system/variables.rst:79 -msgid "The method arguments are as follows:" +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Error: “❌ invalid byte sequence in UTF-8”" msgstr "" -#: ../system/variables.rst:81 -msgid "The date or timestamp variable you want to format." +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Please ensure to provide PEM formatted certificate and keys." msgstr "" -#: ../system/variables.rst:82 -msgid "The output format string." +#: ../system/integrations/smime/troubleshooting.rst:49 +msgid "Did you check if the provided file is a valid certificate or key?" msgstr "" -#: ../system/variables.rst:83 -msgid "The timezone to apply (optional)." +#: ../system/integrations/zabbix.rst:2 +msgid "Zabbix Integration" msgstr "" -#: ../system/variables.rst:86 +#: ../system/integrations/zabbix.rst:5 msgid "" -"``#{dt(ticket.updated_at, \"%A %Y-%m-%d %H:%M in the office\", \"Europe/" -"Berlin\")}``" +"This guide describes how to integrate your Zabbix 5.4 installation with " +"Zammad using the Zabbix webhook feature. This guide will provide " +"instructions on setting up a media type, a user and an action in Zabbix." msgstr "" -#: ../system/variables.rst:87 -msgid "Monday, 2024-03-18 15:31 in the office" +#: ../system/integrations/zabbix.rst:12 +msgid "Zammad with enabled HTTP Token Authentication" msgstr "" -#: ../system/variables.rst:89 -msgid "" -"If you want to use our example, make sure to paste the string above without " -"formatting (``CTRL+Shift+v``), otherwise it won't work." +#: ../system/integrations/zabbix.rst:13 +msgid "Zabbix version 5.4 or higher" msgstr "" -#: ../system/variables.rst:93 -msgid "The following table lists available format directives:" +#: ../system/integrations/zabbix.rst:16 +msgid "Setting up a Zammad" msgstr "" -#: ../system/variables.rst:99 -msgid "Parameter" +#: ../system/integrations/zabbix.rst:18 +msgid "Enable **API Token Access** in Settings > System > API." msgstr "" -#: ../system/variables.rst:102 -msgid "``%Y``" +#: ../system/integrations/zabbix.rst:20 +msgid "" +"Create a **new user** for a Zabbix alerter with an **email address** and " +"create a personal user token with **ticket.agent** permissions." msgstr "" -#: ../system/variables.rst:103 -msgid "Year with 4 digits" +#: ../system/integrations/zabbix.rst:24 +msgid "Zabbix Webhook Configuration" msgstr "" -#: ../system/variables.rst:104 -msgid "Use ``%y`` for year with 2 digits" +#: ../system/integrations/zabbix.rst:27 +msgid "Create a Global Macro" msgstr "" -#: ../system/variables.rst:105 -msgid "``%m``" +#: ../system/integrations/zabbix.rst:29 +msgid "" +"Before setting up the **Webhook**, you need to setup the global macro " +"**{$ZABBIX.URL}**, which must contain the **URL** to the **Zabbix frontend**." msgstr "" -#: ../system/variables.rst:106 -msgid "Month of year (as number with zero-padding)" +#: ../system/integrations/zabbix.rst:33 +msgid "" +"In the **Administration** > **Media types** section, import the `Template`_." msgstr "" -#: ../system/variables.rst:107 -msgid "Use ``%-m`` for month without zero-padding" +#: ../system/integrations/zabbix.rst:38 +msgid "Open the added **Zammad** media type and set:" msgstr "" -#: ../system/variables.rst:108 -msgid "``%d``" +#: ../system/integrations/zabbix.rst:40 +msgid "**zammad\\_access\\_token** to the your **Personal User Token**" msgstr "" -#: ../system/variables.rst:109 -msgid "Day of month (as number with zero-padding)" +#: ../system/integrations/zabbix.rst:41 +msgid "" +"**zammad\\_url** to the **frontend URL** of your **Zammad** installation" msgstr "" -#: ../system/variables.rst:110 -msgid "Use ``%e`` for day without zero-padding" +#: ../system/integrations/zabbix.rst:43 +msgid "**zammad\\_customer** to your **Zammad user email**." msgstr "" -#: ../system/variables.rst:111 -msgid "``%H``" +#: ../system/integrations/zabbix.rst:44 +msgid "" +"**zammad\\_enable\\_tags** to **true** or **false** to enable or disable " +"trigger tags. **Important**: if you enable tag support, each tag is set with " +"a separate request." msgstr "" -#: ../system/variables.rst:112 -msgid "Hour of day in 24h notation with zero-padding" +#: ../system/integrations/zabbix.rst:48 +msgid "" +"If you want to prioritize issues according to **severity** values in Zabbix, " +"you can define mapping parameters:" msgstr "" -#: ../system/variables.rst:113 -msgid "Use ``%k`` for hour without zero-padding" +#: ../system/integrations/zabbix.rst:51 +msgid "**severity\\_**: Zammad priority ID" msgstr "" -#: ../system/variables.rst:114 -msgid "``%I``" +#: ../system/integrations/zabbix.rst:53 +msgid "Click the **Update** button to save the **Webhook** settings." msgstr "" -#: ../system/variables.rst:115 -msgid "Hour of day in 12h notation with zero-padding" +#: ../system/integrations/zabbix.rst:55 +msgid "" +"To receive notifications in **Zammad**, you need to create a **Zabbix user** " +"and add **Media** with the **Zammad** type." msgstr "" -#: ../system/variables.rst:116 +#: ../system/integrations/zabbix.rst:58 msgid "" -"Use ``%l`` for hour without zero-padding and ``%p`` / ``%P`` for meridian " -"indicator" +"For **Send to**: enter any text, as this value is not used, but is required." msgstr "" -#: ../system/variables.rst:117 -msgid "``%M``" +#: ../system/integrations/zabbix.rst:61 +msgid "" +"For more information, use the `Zabbix documentation `_." msgstr "" -#: ../system/variables.rst:118 -msgid "Minute of hour" +#: ../system/maintenance.rst:2 +msgid "Maintenance" msgstr "" -#: ../system/variables.rst:120 -msgid "``%S``" +#: ../system/maintenance.rst:4 +msgid "" +"Zammad comes with a maintenance mode that you can use for e.g. updating the " +"instance or changing settings while restricting availability and functions." msgstr "" -#: ../system/variables.rst:121 -msgid "Second of Minute" +#: ../system/maintenance.rst:13 +msgid "Mode" msgstr "" -#: ../system/variables.rst:123 -msgid "``%A``" +#: ../system/maintenance.rst:8 +msgid "The mode setting allows you to enable or disable the maintenance mode." msgstr "" -#: ../system/variables.rst:124 -msgid "Weekday name" +#: ../system/maintenance.rst:10 +msgid "Defaults to *off*." msgstr "" -#: ../system/variables.rst:125 -msgid "Use ``%a`` for abbreviated name or ``%^A`` for uppercase name" +#: ../system/maintenance.rst:12 +msgid "" +"The maintenance mode will restrict access to administrative roles only. This " +"means agents and customers are logged off." msgstr "" -#: ../system/variables.rst:126 -msgid "``%B``" +#: ../system/maintenance.rst:23 +msgid "@Login" msgstr "" -#: ../system/variables.rst:127 -msgid "Month name" +#: ../system/maintenance.rst:16 +msgid "" +"This setting allows you to provide a login message within a green banner " +"above the login screen. Click into the green banner in the settings page to " +"adjust your message. To activate the message, activate the *@Login* setting." msgstr "" -#: ../system/variables.rst:128 -msgid "Use ``%b`` for abbreviated name" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing the default login message within the\n" +"settings page" msgstr "" -#: ../system/variables.rst:129 -msgid "``%U``" +#: ../system/maintenance.rst:26 +msgid "" +"Send an informative message to **all active sessions**. This comes handy to " +"inform your agents e.g. about mayor outages or to force reloads after " +"configuration changes." msgstr "" -#: ../system/variables.rst:130 -msgid "Week number of current year" +#: ../system/maintenance.rst:31 +msgid "This is the messages title (slightly bigger than the normal message)." msgstr "" -#: ../system/variables.rst:131 -msgid "Use ``%W`` for a different calculation method" +#: ../system/maintenance.rst:34 +msgid "The text you want to provide to your logged in sessions." msgstr "" -#: ../system/variables.rst:134 +#: ../system/maintenance.rst:39 +msgid "Reload application" +msgstr "" + +#: ../system/maintenance.rst:37 msgid "" -"We support the known format directives for the Ruby built-in method " -"``strftime`` of the ``DateTime`` class. For more information, see `here " -"`_." +"Selecting this option will change the message acceptance button from *Close* " +"(with nothing happening) to *Continue session*, which forces the application " +"to reload." msgstr "" -#: ../system/variables/article.rst:2 -msgid "Articles" +#: ../system/maintenance.rst:43 +msgid "" +"If you have customers that are logged in to Zammad, they'll also be notified " +"if they're active in that moment." msgstr "" -#: ../system/variables/article.rst:4 ../system/variables/config.rst:4 -#: ../system/variables/current-user.rst:4 ../system/variables/ticket.rst:4 +#: ../system/maintenance.rst:48 +msgid "Example without reload application" +msgstr "" + +#: ../system/maintenance.rst:52 msgid "" -"If you're missing variables or are not sure if something is not working as " -"expected, feel free to ask over at the `Community `_." +"Message setting within Zammad's admin settings without ticket reload " +"application setting." msgstr "" -#: ../system/variables/article.rst:6 +#: ../system/maintenance.rst:0 msgid "" -"Below you can find all available ticket article-based variables within " -"Zammad. These can be called via Triggers for example. If you're unsure if " -"Zammad does support variables at the point you're at, you can try to type " -"``::`` to check." +"Screenshot showing the send message settings without ticket\n" +"reload application set" msgstr "" -#: ../system/variables/article.rst:9 ../system/variables/config.rst:9 -#: ../system/variables/ticket.rst:9 +#: ../system/maintenance.rst:61 ../system/maintenance.rst:85 msgid "" -"The below list gives you an example what kind of data you can expect, it's " -"not intended to explain the data itself." +"The modal all other active sessions will see upon pressing *Send to clients*." msgstr "" -#: ../system/variables/article.rst:11 -msgid "Article Variables" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing modal caused by maintenance's message\n" +"without reload application ticket" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "name" +#: ../system/maintenance.rst:72 +msgid "Example with reload application" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "variable" +#: ../system/maintenance.rst:76 +msgid "" +"Message setting within Zammad's admin settings with ticket reload " +"application setting." msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "example" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing the send message settings with ticket\n" +"reload application set" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Web" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing modal caused by maintenance's message\n" +"with reload application ticket" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.web}``" +#: ../system/monitoring.rst:2 +msgid "Monitoring" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``https://zammad.com`` or empty if not set in user object" +#: ../system/monitoring.rst:4 +msgid "" +"This function is only available in self hosted instances. If you use Zammad " +"in our cloud, we are monitoring the system on our own and take steps to fix " +"potential problems directly." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > VIP" +#: ../system/monitoring.rst:11 +msgid "" +"On the monitoring page, you can see the current health state of Zammad under " +"\"*Current Status*\" at the bottom. This can be useful if you want to have a " +"look if everything is up and running. As an example, you could have a look " +"in the monitoring when you assume that some emails aren't processed from " +"Zammad." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.vip}``" +#: ../system/monitoring.rst:17 +msgid "**Can't receive an email and the monitoring response is \"healthy\"?**" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -msgid "``true`` or ``false``" +#: ../system/monitoring.rst:19 +msgid "" +"Zammad will just inform you about unprocessable emails. This is not the case " +"for oversized emails. You can adjust the maximum email size in :doc:`../" +"channels/email/settings`." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Phone" +#: ../system/monitoring.rst:24 +msgid "Monitoring API" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.phone}``" +#: ../system/monitoring.rst:26 +msgid "" +"Beside the indication in the monitoring page, you can also use an external " +"monitoring tool to monitor Zammad's health. To request the health of Zammad, " +"you need to provide the API key (token) to the external monitoring tool. You " +"can copy the token from the \"*Current Token*\" field as well as the whole " +"API endpoint of your system (\"*Health Check*\" field), in which the API " +"token is already included." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``+4930123456789`` or empty if not set in user object" +#: ../system/monitoring.rst:37 +msgid "Screenshot showing Current Token and Health Check" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Note" +#: ../system/monitoring.rst:37 +msgid "Screenshot showing Token and Health Check" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.note}``" +#: ../system/monitoring.rst:39 +msgid "" +"In addition to that, you can reset the auto-generated token to make sure " +"that already configured monitoring systems won't work anymore. So, please " +"use this \"*Reset*\" button only if you know what you do!" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Some note about user`` or empty if not set in user object" +#: ../system/monitoring.rst:44 +msgid "Example Output" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Mobile" +#: ../system/monitoring.rst:0 +msgid "No issues found" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.mobile}``" +#: ../system/monitoring.rst:48 ../system/monitoring.rst:60 +msgid "**Indicator in Zammad**:" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Login" +#: ../system/monitoring.rst:0 +msgid "Screenshot showing monitoring with no issues" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.login}``" +#: ../system/monitoring.rst:54 ../system/monitoring.rst:66 +msgid "**API response**::" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -#: ../system/variables/ticket.rst:1 -msgid "``jdoe``" +#: ../system/monitoring.rst:0 +msgid "Issues were found" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Lastname" +#: ../system/monitoring.rst:0 +msgid "Screenshot showing monitoring with issues" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.lastname}``" +#: ../system/objects.rst:2 +msgid "Objects" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -#: ../system/variables/ticket.rst:1 -msgid "``Doe`` or empty if not set" +#: ../system/objects.rst:4 +msgid "" +"In Zammad you can add your own fields to tickets, users, organizations and " +"even groups (these are called \"objects\"). This can be useful if you need " +"to add further information to a ticket or any other object in Zammad and the " +"information doesn't fit in any existing field." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Firstname" +#: ../system/objects.rst:11 +msgid "" +"Try to avoid deleting attributes (and disable them instead) as Zammad might " +"run into unexpected conditions if they are referenced somewhere." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.firstname}``" +#: ../system/objects.rst:16 +msgid "" +"Here's an overview of object attributes. On the upper right you can add new " +"attributes. By default, there will be no custom fields - standard attributes " +"will be grayed out, you can't delete or change those. You can edit custom " +"attributes (they are displayed in black font and have a trash bin on the " +"right side) just by clicking on them." msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "``Joe`` or empty if not set" +#: ../system/objects.rst:24 +msgid "" +"Attributes you add to Zammad, no matter if they have default values or not, " +"will not update existing information. This means a new ticket field " +"technically will be empty unless you populate it." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Fax" +#: ../system/objects.rst:28 +msgid "" +"Especially in ticket scope this also means that newly added attributes will " +"be indicated as \"changed\" to agents that view the ticket. This may " +"interfere with Zammad's tabs behavior." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.fax}``" +#: ../system/objects.rst:40 +msgid "Ordering Attributes" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Email" +#: ../system/objects.rst:42 +msgid "" +"Since Zammad introduced :doc:`/system/core-workflows` the need to have a " +"custom positioning for attributes has become more important than ever." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.email}``" +#: ../system/objects.rst:45 +msgid "" +"To adjust the position of such an attribute, simply click on the attribute " +"entry in question, scroll down and adjust the position number. Please note " +"that you cannot change the positioning of default attributes." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``jdoe@example.com``" +#: ../system/objects.rst:49 +msgid "" +"In case two attributes have the same position value, Zammad will sort " +"alphabetically by name automatically." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Department" +#: ../system/objects.rst:None +msgid "" +"Screenshot showing custom attribute entries ordered in between default ones" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.department}``" +#: ../system/objects.rst:56 +msgid "Updating Database After Adding or Editing Attributes" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Sales`` or empty if not set in user object" +#: ../system/objects.rst:58 +msgid "" +"When adding or changing attributes, Zammad will not apply the changes " +"instantly, but instead shows you the changed attributes first. If you're " +"ready to go, just click on \"Update database\" to apply the changes to " +"Zammad. If you made a mistake or just want to discard your changes, click " +"\"Discard changes\"." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Address" +#: ../system/objects.rst:64 +msgid "" +"After applying the changes with \"Update Database\", a restart of Zammad is " +"**mandatory**. If you don't perform it, you may experience unexpected " +"behavior or even errors. You may want to do this kind of configuration " +"during maintenance windows." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.address}``" +#: ../system/objects.rst:72 +msgid "" +"Changes on objects require you to update the database to apply these changes." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Some street 1, 12345 Berlin`` or empty if not set in user object" +#: ../system/objects.rst:75 +msgid "**🤓 Service restarts can be automated**" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated" +#: ../system/objects.rst:0 +msgid "Hosted environments automatically restart for you." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_at}``" +#: ../system/objects.rst:0 +msgid "" +"If you're using a self-hosted installation you can use :docs:`environment " +"variables `" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``2019-10-08 15:24:47 UTC``" +#: ../system/objects.rst:82 +msgid "System Attributes" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Type > Name" +#: ../system/objects.rst:84 +msgid "" +"Zammad comes with pre-configured attributes. Some of them can't be edited " +"via UI (or at all). This is required for proper operation of Zammad and not " +"a bug." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.type.name}``" +#: ../system/objects.rst:90 +msgid "Ticket State" msgstr "" -#: ../system/variables/article.rst:1 +#: ../system/objects.rst:92 msgid "" -"``email`` (`list of article types `_)" +"If the pre-configured states aren't enough for you or you want to change " +"them, you can do so by clicking on the cogwheel icon in the state row in the " +"ticket tab. But you should be careful when changing pre-configured states. " +"This can lead to unwanted behavior in some cases." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > To" +#: ../system/objects.rst:None +msgid "Screenshot showing highlighted ticket state attribute" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.to}``" +#: ../system/objects.rst:122 +msgid "Handling of states" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``helpdesk@example.com``" +#: ../system/objects.rst:102 +msgid "" +"In the state configuration screen, you can add new states, disable states or " +"change states." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > TicketID" +#: ../system/objects.rst:0 +msgid "Screenshot showing table of default ticket states" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.ticket_id}``" +#: ../system/objects.rst:110 +msgid "" +"To add a new state, click on the \"New Ticket State\" button in the top " +"right corner. To change an existing state, simply click on the affected " +"state. This opens an edit dialog." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``1`` (not ticket number)" +#: ../system/objects.rst:114 +msgid "" +"You can also clone a state or set them to \"Default for new tickets\" or " +"\"Default for follow-ups\" by clicking on the ⁝ action button and select the " +"desired function." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Subject" +#: ../system/objects.rst:118 +msgid "" +"*Default for new tickets* means that this state is used for every newly " +"created ticket." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.subject}``" +#: ../system/objects.rst:121 +msgid "" +"*Default for follow-ups* means that this state is used if the ticket is re-" +"opened after it was closed." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``My amazing subject``" +#: ../system/objects.rst:171 +msgid "Ticket state in detail" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Sender > Name" +#: ../system/objects.rst:125 +msgid "" +"Below you can find a description for each field and option. Please head over " +"to the :ref:`example ` to see the edit dialog." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.sender.name}``" +#: ../system/objects.rst:129 +msgid "" +"This is the name of the state and what you and your agents are seeing when " +"choosing a state somewhere (e.g. in tickets, trigger configuration)." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Customer``, ``Agent`` or ``System``" +#: ../system/objects.rst:137 +msgid "" +"There are different state types you can choose from. By default, Zammad " +"comes with one state per state type." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Visibility" +#: ../system/objects.rst:140 +msgid "" +"**new**: for states for tickets that are new and it hasn't been worked on " +"them" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.internal}``" +#: ../system/objects.rst:142 +msgid "" +"**open**: for states for tickets that are in progress and agents are working " +"on them" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``false`` or ``true`` (false if not internal)" +#: ../system/objects.rst:144 +msgid "**merged**: for states for tickets that are merged with other tickets" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > From" +#: ../system/objects.rst:145 +msgid "" +"**pending reminder**: for states for tickets that are in progress and you " +"want to set a reminder. (default example: *pending reminder*)" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.from}``" +#: ../system/objects.rst:147 +msgid "" +"**pending action**: for states for tickets that are waiting for a specified " +"time and then change their state (default example: *pending close*)" msgstr "" -#: ../system/variables/article.rst:1 +#: ../system/objects.rst:150 msgid "" -"``Joe Doe `` may differ, depends on ``FROM`` of send mail" +"**closed**: for states for tickets that are finished and do not need to be " +"processed further" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Web" +#: ../system/objects.rst:153 +msgid "" +"⚠️ Choosing the correct state type is important! If you are in doubt, have a " +"look on the default states and their types!" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.web}``" +#: ../system/objects.rst:158 +msgid "Ignore escalation" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > VIP" +#: ../system/objects.rst:157 +msgid "" +"Here you can define whether tickets of this state will count to escalation " +"time or not." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.vip}``" +#: ../system/objects.rst:161 +msgid "" +"You can create a note for the state to inform other admins about the state. " +"This has no effect on tickets." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Phone" +#: ../system/objects.rst:165 +msgid "Set the state to *active* or *inactive*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.phone}``" +#: ../system/objects.rst:167 +msgid "" +"it is technically possible to set all states to inactive. To keep Zammad " +"working in such a case, the inactive flag of one of the states is ignored." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Note" +#: ../system/objects.rst:194 +msgid "Ticket state example" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.note}``" +#: ../system/objects.rst:174 +msgid "" +"Let's assume we want to create a new state which indicates that the ticket " +"has to wait for a response of a third party (e.g. service contractor or " +"manufacturer) and we want to to be able to set a reminder." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Mobile" +#: ../system/objects.rst:178 +msgid "" +"First we give the new state a proper name. In this example we call it " +"\"waiting for manufacturer\"." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.mobile}``" +#: ../system/objects.rst:181 +msgid "" +"As state type we choose \"pending reminder\". This indicates that the ticket " +"is still open and we can set a reminder. This reminder can be useful if our " +"manufacturer sometimes isn't responding or we want to remind him to give us " +"an answer." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Login" +#: ../system/objects.rst:186 +msgid "" +"We choose \"no\" for \"ignore escalation\" because we want to escalate the " +"tickets even if we are waiting on the manufacturer's feedback." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.login}``" +#: ../system/objects.rst:189 +msgid "The **result** in the creation dialog will look like this:" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Lastname" +#: ../system/objects.rst:0 +msgid "Screenshot showing ticket state creation dialog with example" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.lastname}``" +#: ../system/objects.rst:199 +msgid "Ticket Priority" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Firstname" +#: ../system/objects.rst:201 +msgid "" +"If the pre-configured priorities aren't enough for you or you want to change " +"them, you can do so by clicking on the cogwheel icon in the priority row in " +"the ticket tab:" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.firstname}``" +#: ../system/objects.rst:None +msgid "Screenshot showing highlighted ticket priority attribute" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Fax" +#: ../system/objects.rst:226 +msgid "Handling of priorities" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.fax}``" +#: ../system/objects.rst:210 +msgid "" +"In the priority configuration screen, you can add new priorities, disable " +"priorities or change priorities." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Email" +#: ../system/objects.rst:0 +msgid "Screenshot showing table of default ticket priorities" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.email}``" +#: ../system/objects.rst:218 +msgid "" +"To add a new priority, click on the \"New Priority\" button in the top right " +"corner. To change an existing priority, simply click on the affected " +"priority. This opens an edit dialog." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Department" +#: ../system/objects.rst:222 +msgid "" +"You can also clone a priority or set them to \"Default for new tickets\" by " +"clicking on the ⁝ action button and select the desired function." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.department}``" +#: ../system/objects.rst:225 +msgid "" +"*Default for new tickets* means that this priority is used for every newly " +"created ticket." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Address" +#: ../system/objects.rst:248 +msgid "Priorities in detail" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.address}``" +#: ../system/objects.rst:229 +msgid "Below you can find a description for each field and option." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created" +#: ../system/objects.rst:232 +msgid "" +"This is the name of the priority and what you and your agents are seeing " +"when choosing a priority somewhere (e.g. in tickets, trigger configuration)." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_at}``" +#: ../system/objects.rst:242 +msgid "Highlight color" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Cc" +#: ../system/objects.rst:237 +msgid "" +"Switch between *Low priority* (light blue), *High priority* (red) and - " +"(default). This affects the displayed color for ticket titles in overviews." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.cc}``" +#: ../system/objects.rst:241 +msgid "The color options are currently limited to the mentioned options." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``jdoe@example.com, company@example.com``" +#: ../system/objects.rst:245 +msgid "" +"You can create a note for the priority to inform other admins about the " +"priority. This has no effect on tickets." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Text" +#: ../system/objects.rst:249 +msgid "Set the priority to *active* or *inactive*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.body}``" +#: ../system/objects/external-data-source-example.rst:2 +msgid "External Data Source" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Test`` without formatting (plain)" +#: ../system/objects/external-data-source-example.rst:4 +msgid "" +"We assume you already had a look on :doc:`types` where you can find a " +"description of the individual fields." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article Text as HTML (not referenced)" +#: ../system/objects/external-data-source-example.rst:7 +msgid "" +"To reproduce this example, choose a category you want to add a custom field, " +"click on *New Attribute* and select *External data source field* under " +"*Format*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.body_as_html}``" +#: ../system/objects/external-data-source-example.rst:11 +msgid "" +"Our example story is to fetch data from an external product database. We " +"want to add our products to the tickets so that the products can be searched " +"and chosen from a list and also create a link to the product website." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Test`` with formatting" +#: ../system/objects/external-data-source-example.rst:16 +msgid "Base configuration" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "Ticket > Article#" +#: ../system/objects/external-data-source-example.rst:None +msgid "Initial steps to configure external data source object type" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "``#{ticket.article_count}``" +#: ../system/objects/external-data-source-example.rst:25 +msgid "Name: *product*" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``1`` number of ticket articles" +#: ../system/objects/external-data-source-example.rst:26 +msgid "Display: *Product*" msgstr "" -#: ../system/variables/config.rst:2 -msgid "Config" +#: ../system/objects/external-data-source-example.rst:29 +msgid "External data source configuration" msgstr "" -#: ../system/variables/config.rst:6 +#: ../system/objects/external-data-source-example.rst:31 msgid "" -"Below you'll find config related variables. These hold useful configuration " -"information that you can use within e.g. triggers to show necessary " -"information to your customer." +"First, enter the search URL making sure it contains ``#{search.term}`` as a " +"parameter:" msgstr "" -#: ../system/variables/config.rst:11 -msgid "Config Variables" +#: ../system/objects/external-data-source-example.rst:34 +msgid "**Example:** ``https://dummyjson.com/products/search?q=#{search.term}``" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Fully Qualified Domain Name" +#: ../system/objects/external-data-source-example.rst:36 +msgid "" +"After that, head down to the preview section and enter a search input for " +"the external data source." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.fqdn}``" +#: ../system/objects/external-data-source-example.rst:39 +msgid "**Example:** ``mac``" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``zammad.example.com``" +#: ../system/objects/external-data-source-example.rst:41 +msgid "Then you can find a preview of the response data below:" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Ticket Hook" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of JSON response based on search term" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.ticket_hook}``" +#: ../system/objects/external-data-source-example.rst:48 +msgid "" +"We recommend using the preview to have a look on the structure. There is a " +"top-level element called ``products``. One level below, you can find the " +"attributes ``id`` and ``title``." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``Ticket#``" +#: ../system/objects/external-data-source-example.rst:52 +msgid "**Search result response based on search from example:**" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > HTTP type" +#: ../system/objects/external-data-source-example.rst:119 +msgid "" +"To tell the remote system that the desired data is located below the " +"``products`` level, you have to put it in the field *Search result list key*." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.http_type}``" +#: ../system/objects/external-data-source-example.rst:122 +msgid "" +"After inserting ``products`` in the mentioned field, you get an extended " +"preview. You can find an additional box *Search result list* with a JSON " +"structure. This is the same response as before but stripped from the upper " +"``products`` element by the external data source." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``https`` or ``http``" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of JSON response search result list" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > SystemID" +#: ../system/objects/external-data-source-example.rst:132 +msgid "" +"Now you need to provide the keys for the search result values and labels. As " +"already mentioned, we are looking for the ``id`` and the ``title`` of our " +"products. If you haven't already, it is now a good time to look at the " +"preview of the *Search result list*." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.system_id}``" +#: ../system/objects/external-data-source-example.rst:197 +msgid "" +"After locating our two keys, we insert them in *search result value key* " +"(``id``) and in *Search result label key* (``title``)." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``31`` (value between 1 and 99)" +#: ../system/objects/external-data-source-example.rst:200 +msgid "" +"Basically, we configured the external data source already and we can see a " +"table in the preview section:" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Organization" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of product table based on search term" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.organization}``" +#: ../system/objects/external-data-source-example.rst:208 +msgid "" +"According to our example story, now just the *Link template* is missing." msgstr "" -#: ../system/variables/config.rst:1 +#: ../system/objects/external-data-source-example.rst:210 msgid "" -"``Zammad GmbH`` value set in `Branding `_" +"Please note that this is an optional feature. If you don't want to use such " +"links, of course you don't have to configure it." msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Product Name" +#: ../system/objects/external-data-source-example.rst:213 +msgid "" +"We can add now an address where additional product information can be found." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.product_name}``" +#: ../system/objects/external-data-source-example.rst:215 +msgid "Example: ``https://your_domain.com/q=#{ticket.product}``" msgstr "" -#: ../system/variables/config.rst:1 -msgid "" -"``Helpdesk`` value set in `Branding `_" +#: ../system/objects/external-data-source-example.rst:217 +msgid "In the example, the parameter means:" +msgstr "" + +#: ../system/objects/external-data-source-example.rst:219 +msgid "``#{}``: \"Frame\" for the insertion of information" msgstr "" -#: ../system/variables/current-user.rst:2 -msgid "Current User" +#: ../system/objects/external-data-source-example.rst:220 +msgid "``ticket``: object level, where you create your custom object" msgstr "" -#: ../system/variables/current-user.rst:6 -msgid "" -"Current user variables always return values of the current user that caused " -"e.g. a trigger to run." +#: ../system/objects/external-data-source-example.rst:221 +msgid "``product``: name of the (custom) object" msgstr "" -#: ../system/variables/current-user.rst:8 +#: ../system/objects/external-data-source-example.rst:223 msgid "" -"Due to the above fact, these variables are often not (yet) set or available " -"for usage." +"After configuring your *Link template*, there will be another column in the " +"preview. Hovering on the icons in the *Link* column will show you where it " +"forwards you." msgstr "" -#: ../system/variables/current-user.rst:10 +#: ../system/objects/external-data-source-example.rst:232 msgid "" -"In situations where e.g. schedulers or triggers run, this most likely is " -"nothing you want to use." -msgstr "" - -#: ../system/variables/current-user.rst:13 -msgid "Current User Variables" +"In our example, one of the links looks like: https://your_domain.com/q=6, " +"where the 6 is the product id." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Web" +#: ../system/objects/external-data-source-example.rst:235 +msgid "You can find more information regarding the URL in :doc:`types`." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.web}``" +#: ../system/objects/includes/adding-values-hint.include.rst:3 +msgid "" +"Adding values can be tricky for first timers, don't forget to press \"➕ " +"Add\" after typing your values. Otherwise you may loose a value." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``https://zammad.org`` or empty if not set" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:1 +#: ../system/objects/includes/reposition-values.include.rst:1 +msgid "**↕️ This field type allows the positioning of its values ↔️**" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > VIP" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:3 +msgid "" +"In order to re-arrange the field values, first edit the field. Then you can " +"use ☰ to drag the values in question to the correct position. If you want to " +"change the layer depth, double click on ☰. With it you can cycle through the " +"available layers." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.vip}``" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:8 +msgid "When you're ready, submit your changes to save the object attribute." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``false`` or ``true``" +#: :0 ../system/objects/types.rst:0 +msgid "" +"Screencast showing how to re-position values on tree select like\n" +"fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Web" +#: ../system/objects/includes/reposition-values.include.rst:3 +msgid "" +"In order to re-arrange the field values, edit the field and scroll below the " +"values. Make sure to tick the option \"Use custom option sort\"." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.web}``" +#: ../system/objects/includes/reposition-values.include.rst:8 +msgid "" +"If you do not tick this field, all manual positioning you did above will be " +"lost upon saving! ☠️" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > VIP" +#: ../system/objects/includes/reposition-values.include.rst:11 +msgid "" +"Now use ☰ to drag the values in question to the correct position. When " +"you're ready, submit your changes to save the object attribute." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.vip}``" +#: :0 ../system/objects/types.rst:0 +msgid "Screencast showing how to re-position values" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Phone" +#: ../system/objects/includes/url-template-hint.include.rst:3 +msgid "" +"This field allows using :ref:`URL fields (Link Templates) `." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.phone}``" +#: ../system/objects/permissions.rst:2 +msgid "Attribute Permissions" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``004930123456789`` or empty if not set" +#: ../system/objects/permissions.rst:7 +msgid "" +"In the object attributes configuration you can define if a field is shown " +"and if the input in the field is mandatory, separated by different screens " +"and for different :doc:`roles/permissions `." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Note" +#: ../system/objects/permissions.rst:17 +msgid "Screenshot shows object attribute permission table" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.note}``" +#: ../system/objects/permissions.rst:17 +msgid "" +"Some of the possible permissions and screen options for a user object " +"attribute." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Some note to this user`` or empty if not set" +#: ../system/objects/permissions.rst:19 +msgid "" +"Based on the object context (ticket, agent, organization, user), the " +"selectable roles (to be precise: the required permissions) and screens " +"differ. Be aware that these settings aren't affecting data creation via " +"other channels than the UI." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Mobile" +#: ../system/objects/permissions.rst:24 +msgid "" +"If you want to have further customization possibilities, you should have a " +"look at the :doc:`core workflows `." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.mobile}``" +#: ../system/objects/permissions.rst:28 +msgid "Screens" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``0049176123456789`` or empty if not set" +#: ../system/objects/permissions.rst:30 +msgid "" +"In the table below you can find an overview about the different permissions " +"and the available screens Zammad distinguishes between." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Login" +#: ../system/objects/permissions.rst:37 +msgid "Screen" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.login}``" +#: ../system/objects/permissions.rst:38 +msgid "Available for" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Lastname" +#: ../system/objects/permissions.rst:40 +msgid "create" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.lastname}``" +#: ../system/objects/permissions.rst:41 ../system/objects/permissions.rst:52 +#: ../system/objects/permissions.rst:59 ../system/objects/permissions.rst:73 +msgid "admin.user" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Firstname" +#: ../system/objects/permissions.rst:42 ../system/objects/permissions.rst:53 +#: ../system/objects/permissions.rst:60 +msgid "admin.organization" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.firstname}``" +#: ../system/objects/permissions.rst:43 ../system/objects/permissions.rst:54 +#: ../system/objects/permissions.rst:61 +msgid "admin.group" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``John`` or empty if not set" +#: ../system/objects/permissions.rst:44 +msgid "Creation dialog for not yet existing data" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Fax" +#: ../system/objects/permissions.rst:45 +msgid "create_middle" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.fax}``" +#: ../system/objects/permissions.rst:46 ../system/objects/permissions.rst:50 +#: ../system/objects/permissions.rst:57 ../system/objects/permissions.rst:66 +#: ../system/objects/permissions.rst:70 +msgid "ticket.customer" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``004930123464789`` or empty if not set" +#: ../system/objects/permissions.rst:47 ../system/objects/permissions.rst:51 +#: ../system/objects/permissions.rst:58 ../system/objects/permissions.rst:69 +msgid "ticket.agent" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Email" +#: ../system/objects/permissions.rst:48 +msgid "Ticket create dialog (middle section)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.email}``" +#: ../system/objects/permissions.rst:49 +msgid "edit" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``jdoe@customer.tld``" +#: ../system/objects/permissions.rst:55 +msgid "Editing dialog for already existing data" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Department" +#: ../system/objects/permissions.rst:56 +msgid "view" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.department}``" +#: ../system/objects/permissions.rst:62 +msgid "View-only dialog for already existing data" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Sales`` or empty if not set" +#: ../system/objects/permissions.rst:64 +msgid "(e.g. user or organization from search)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Avatar" +#: ../system/objects/permissions.rst:65 +msgid "signup" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.avatar(60,60)}``" +#: ../system/objects/permissions.rst:67 +msgid "Sign-up screen for new customers" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "avatar picture with width and height in pixel (e.g. 60,60)" +#: ../system/objects/permissions.rst:68 +msgid "invite_customer" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Address" +#: ../system/objects/permissions.rst:71 +msgid "" +"Customer invitation screen (from :doc:`First Steps ` area)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.address}``" +#: ../system/objects/permissions.rst:72 +msgid "invite_agent" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Some street 1, 12345 Berlin`` or empty if not set" +#: ../system/objects/permissions.rst:74 +msgid "" +"Agent invitation screen (from :doc:`First Steps ` area)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated at" +#: ../system/objects/permissions.rst:78 +msgid "Screen Options" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_at}``" +#: ../system/objects/permissions.rst:80 +msgid "" +"For the different screens you can select \"show\" and \"required\" options." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC``" +#: ../system/objects/permissions.rst:82 +msgid "**shown:** Show (check) or hide (uncheck) a field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Phone" +#: ../system/objects/permissions.rst:83 +msgid "" +"**required:** Set a field to mandatory (check). Forces users (via UI and " +"API) to populate the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.phone}``" +#: ../system/objects/types.rst:7 +msgid "Example external data source" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Shared organization" +#: ../system/objects/types.rst:2 +msgid "Attribute types" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.shared}``" +#: ../system/objects/types.rst:4 +msgid "" +"When adding a new object attribute, you can choose between the following " +"attribute types." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Note" +#: ../system/objects/types.rst:14 +msgid "" +"You cannot change the attribute format / type as soon as it is applied. If " +"you no longer need an object attribute, consider disabling it instead of " +"removing." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.note}``" +#: ../system/objects/types.rst:18 +msgid "**What about the translation of my attributes?**" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``A note to the organization of the user`` or empty if not set" +#: ../system/objects/types.rst:20 +msgid "" +"For some attribute types you can decide if they should be translatable or " +"not. To be precise, it works only for the selectable fields because the " +"possible choices are known and limited. For the following attribute types, " +"you can set the translatable flag:" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Name" +#: ../system/objects/types.rst:25 +msgid "*Boolean field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.name}``" +#: ../system/objects/types.rst:26 +msgid "*Single selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``Zammad GmbH``" +#: ../system/objects/types.rst:27 +msgid "*Multiple selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Domain based assignment" +#: ../system/objects/types.rst:28 +msgid "*Single tree selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.domain_assignment}``" +#: ../system/objects/types.rst:29 +msgid "*Multiple tree selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Domain" +#: ../system/objects/types.rst:31 +msgid "" +"For these types, you can find an additional field *Translate field contents*:" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.domain}``" +#: ../system/objects/types.rst:0 +msgid "Screenshot showing translatable attribute types" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``zammad.com`` or empty if not set" +#: ../system/objects/types.rst:38 +msgid "Screenshot with example of translatable attribute type" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > VIP" +#: ../system/objects/types.rst:45 +msgid "Boolean field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.vip}``" +#: ../system/objects/types.rst:41 +msgid "" +"Provides a drop-down field with display values for ``true`` and ``false``. " +"Setting a default is mandatory." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Note" +#: ../system/objects/types.rst:0 +msgid "Available settings for Boolean fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.note}``" +#: ../system/objects/types.rst:55 +msgid "Date field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Mobile" +#: ../system/objects/types.rst:48 +msgid "Provides a date picker field and does not allow default values." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.mobile}``" +#: ../system/objects/types.rst:52 +msgid "Default time diff (hours)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Login" +#: ../system/objects/types.rst:51 +msgid "" +"This setting helps the user by highlighting the day from now plus the " +"provided value. It *does not* pre-fill the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.login}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Date fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Lastname" +#: ../system/objects/types.rst:73 +msgid "Date & time field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.lastname}``" +#: ../system/objects/types.rst:58 +msgid "Provides a date and time picker – does not allow default values" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Firstname" +#: ../system/objects/types.rst:62 +msgid "Allow future" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.firstname}``" +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the future." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Fax" +#: ../system/objects/types.rst:66 +msgid "Allow past" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.fax}``" +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the past." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Email" +#: ../system/objects/types.rst:70 +msgid "Default time diff (minutes)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.email}``" +#: ../system/objects/types.rst:69 +msgid "" +"This setting helps the user by highlighting the day from now plus the " +"provided value. It does not pre-fill the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Department" +#: ../system/objects/types.rst:0 +msgid "Available settings for Date & time fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.department}``" +#: ../system/objects/types.rst:86 +msgid "Integer field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Web" +#: ../system/objects/types.rst:76 +msgid "" +"Provides an input field that allows integer usage only. You may define a " +"default value. You cannot enforce comma separation." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.web}``" +#: ../system/objects/types.rst:80 +msgid "Minimal" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > VIP" +#: ../system/objects/types.rst:80 +msgid "The minimal value the field accepts." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.vip}``" +#: ../system/objects/types.rst:83 +msgid "Maximal" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Phone" +#: ../system/objects/types.rst:83 +msgid "The maximum value the field accepts." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.phone}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Integer fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Note" +#: ../system/objects/types.rst:99 +msgid "Multiple selection field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.note}``" +#: ../system/objects/types.rst:89 +msgid "" +"Provides a selection field that allows the selection of one or more out of " +"several. This field does allow setting a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Mobile" +#: ../system/objects/types.rst:0 +msgid "Available settings for Multiple selection fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.mobile}``" +#: ../system/objects/types.rst:112 +msgid "Single selection field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Login" +#: ../system/objects/types.rst:102 +msgid "" +"Provides a drop-down field that allows selection of one value out of " +"several. This field does allow setting a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.login}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Single selection fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Lastname" +#: ../system/objects/types.rst:142 +msgid "Textarea field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.lastname}``" +#: ../system/objects/types.rst:115 +msgid "" +"Provides a text area input field (multiple lines) and thus allows e.g. new " +"lines. You can set a default field value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Firstname" +#: ../system/objects/types.rst:120 +msgid "" +"Please note that this field *does not* support text formatting or HTML " +"content (rich text)." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.firstname}``" +#: ../system/objects/types.rst:123 +msgid "**🥵 This field can consume a lot of visual space**" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Fax" +#: ../system/objects/types.rst:125 +msgid "" +"Depending on where you use this field type, it may use a lot of visual space " +"if you provide a lot of text. This may be an issue to work with." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.fax}``" +#: ../system/objects/types.rst:130 +msgid "Default" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Email" +#: ../system/objects/types.rst:129 +msgid "" +"The here provided text will be shown within the text area field or new data " +"sets." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.email}``" +#: ../system/objects/types.rst:134 ../system/objects/types.rst:160 +msgid "Maxlength" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Department" +#: ../system/objects/types.rst:0 ../system/objects/types.rst:160 +msgid "You can pick the maximum length of the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.department}``" +#: ../system/objects/types.rst:0 +msgid "The default length of this object is ``500``." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Avatar" +#: ../system/objects/types.rst:139 +msgid "Rows" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.avatar(60,60)}``" +#: ../system/objects/types.rst:0 +msgid "" +"Change the number of rows to dislay so that you can use only the space you " +"really need." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Address" +#: ../system/objects/types.rst:0 +msgid "The default number of rows is ``4``." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.address}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Textarea fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created at" +#: ../system/objects/types.rst:165 +msgid "Text field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_at}``" +#: ../system/objects/types.rst:145 +msgid "Provides a text field (one line) and allows choosing a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Avatar" +#: ../system/objects/types.rst:148 +msgid "" +"Defines the type of the input field. This allows e.g. your browser to ensure " +"that you provide the specific type." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.avatar(60,60)}``" +#: ../system/objects/types.rst:152 +msgid "Currently available:" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Address" +#: ../system/objects/types.rst:155 +msgid "Phone" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.address}``" +#: ../system/objects/types.rst:156 +msgid "Text" msgstr "" -#: ../system/variables/ticket.rst:6 -msgid "" -"Below you can find all available ticket-based variables within Zammad. These " -"can be called via Triggers for example. If you're unsure if Zammad does " -"support variables at the point you're at, you can try to type ``::`` to " -"check." +#: ../system/objects/types.rst:157 +msgid "Url *(URL fields disable link-template availability)*" msgstr "" -#: ../system/variables/ticket.rst:12 -msgid "Ticket Variables" +#: ../system/objects/types.rst:0 +msgid "Available settings for Text fields" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Web" +#: ../system/objects/types.rst:174 +msgid "Single tree selection field" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.web}``" +#: ../system/objects/types.rst:168 +msgid "" +"Provides a select-like field with up to 6 layers of options. Does not allow " +"setting a default value." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > VIP" +#: ../system/objects/types.rst:0 +msgid "Available settings for Tree Select fields" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.vip}``" +#: ../system/objects/types.rst:183 +msgid "Multiple tree selection field" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Phone" +#: ../system/objects/types.rst:177 +msgid "" +"Provides a select-like field with up to 6 layers of options allowing the " +"selection of multiple values. Does not allow setting a default value." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.phone}``" +#: ../system/objects/types.rst:302 +msgid "External Data Source field" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Note" +#: ../system/objects/types.rst:186 +msgid "" +"Provides a searchable field which fetches data from an external system. This " +"can be useful if you have data outside of Zammad and don't want to maintain " +"both data sources." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.note}``" +#: ../system/objects/types.rst:190 +msgid "The feature works as follows:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Mobile" +#: ../system/objects/types.rst:192 +msgid "" +"Zammad sends a query with a search string (free text from agent or based on " +"a variable) in a pre-defined format (\"Search URL\") to an external system." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.mobile}``" +#: ../system/objects/types.rst:195 +msgid "" +"This external system searches for matches and provides a response as a JSON " +"structure to Zammad." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Login" +#: ../system/objects/types.rst:197 +msgid "" +"Zammad just looks for the defined list and value keys, reads the content and " +"displays the value to the user. There is no search on Zammad side." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.login}``" +#: ../system/objects/types.rst:201 +msgid "" +"The usage of a PostgreSQL database for Zammad is required. In any other " +"case, Zammad will hide the external data source type and you are not able to " +"use it. If you want to use this feature, consider to :docs:`migrate your " +"database `." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Lastname" +#: ../system/objects/types.rst:205 +msgid "Currently, only ``GET`` is supported as request method." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.lastname}``" +#: ../system/objects/types.rst:206 +msgid "" +"The data structure must be in JSON format and provide the objects in an " +"array." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Firstname" +#: ../system/objects/types.rst:208 +msgid "" +"The endpoint for the external data source has to support search. On Zammad " +"side, there is no search/logic implemented; however, you can define the " +"output key and value based on the result(s) from the response (which " +"provides already filtered content based on the search)." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.firstname}``" +#: ../system/objects/types.rst:212 +msgid "" +"If you receive more results as expected, your external data source search " +"may not work properly or the structure of the URL is not correct. You should " +"get in touch with a responsible person from the external system." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Fax" +#: ../system/objects/types.rst:217 +msgid "" +"Please have a look :doc:`at our example `, where you can find a possible configuration for a public " +"dummy endpoint." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.fax}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for external data source fields" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Email" +#: ../system/objects/types.rst:242 +msgid "Search URL" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.email}``" +#: ../system/objects/types.rst:227 +msgid "" +"Set your endpoint where Zammad fetches the data. Please make sure to include " +"a valid search :doc:`variable ` as an URL parameter. " +"Example for a free text search at user input: ``#{search.term}``" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Department" +#: ../system/objects/types.rst:232 +msgid "" +"If in doubt, ask the responsible person for the external data source how " +"they expect the structure of the URL." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.department}``" +#: ../system/objects/types.rst:236 +msgid "" +"Depending on your search variable, the preview might work or not. The reason " +"is that the context might not be available and it is no bug." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Avatar" +#: ../system/objects/types.rst:239 +msgid "" +"Please also make sure to use a variable which is available in your object " +"context. For example you won't be able to search for a ticket in a user " +"object context." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.avatar(60,60)}``" +#: ../system/objects/types.rst:252 +msgid "SSL Verification" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Address" +#: ../system/objects/types.rst:245 +msgid "Here you can switch the SSL verification to no." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.address}``" +#: ../system/objects/types.rst:249 +msgid "" +"If your external data source system is using self signed certificates, " +"please have a look :doc:`here ` for " +"further information about how to handle them in Zammad, so you can keep the " +"SSL verification activated." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated at" +#: ../system/objects/types.rst:258 +msgid "HTTP Authentication" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_at}``" +#: ../system/objects/types.rst:255 +msgid "" +"If your external data source requires an authentication, you can set it " +"here. You can leave it empty or choose between *Basic Authentication* or " +"*Authentication Token* (selecting one of the two methods leads to additional " +"fields where you can enter your credentials/token)." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Title" +#: ../system/objects/types.rst:265 +msgid "Search result list key" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.title}``" +#: ../system/objects/types.rst:261 +msgid "" +"Defines the level in the JSON structure which provides the list with search " +"results. You can leave it empty, if the data is already provided as an " +"array. If you have to go deeper in the structure, you can provide a path " +"with ``.`` as separators, e.g. ``key.subkey.sub-sub-key``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "" -"``My amazing Subject`` (normally subject, can be edited within Interface and " -"thus differ)" +#: ../system/objects/types.rst:271 +msgid "Search result value key" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Accounted Time" +#: ../system/objects/types.rst:268 +msgid "" +"Defines the attribute in the structure in which your external data source " +"provides the *value* for your data. An example would be a product *number*. " +"If you have to go deeper in the structure, you can provide a path with ``.`` " +"as separators, e.g. ``key.subkey.sub-sub-key``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.time_unit}``" +#: ../system/objects/types.rst:277 +msgid "Search result label key" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``1``, ``2.75`` or empty response" +#: ../system/objects/types.rst:274 +msgid "" +"Defines the attribute in the structure in which your external data source " +"provides the *label* for your data. An example would be a product *name*. If " +"you have to go deeper in the structure, you can provide a path with ``.`` as " +"separators, e.g. ``key.subkey.sub-sub-key``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Tags" +#: ../system/objects/types.rst:280 +msgid "" +"In the preview area, you can find the following items (depending on your " +"configuration above):" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.tags}``" +#: ../system/objects/types.rst:283 +msgid "" +"**Error/hint message** (only if configuration is not complete): Zammad tells " +"you, if there is a problem and what you should change in your configuration." msgstr "" -#: ../system/variables/ticket.rst:1 +#: ../system/objects/types.rst:286 msgid "" -"Currently not available, see `Issue 2769 `_" +"**Search field**: search for an existing attribute in the data source to get " +"a preview. This is required for the fields below to show up." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > State > Name" +#: ../system/objects/types.rst:288 +msgid "" +"**Search result response** (only if configuration is not complete): here you " +"can find a syntax highlighted JSON preview of the response, based on the " +"search term you entered." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.state.name}``" +#: ../system/objects/types.rst:291 +msgid "" +"**Search result list** (only if *search result list key* is properly set): " +"output of the structure under the configured *search result list key*." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``new``, ``open``, ..." +#: ../system/objects/types.rst:294 +msgid "" +"**Preview table** (when fully configured): Zammad shows you a table which " +"includes the found items based on the search string (value, label and " +"optional link). You can use this preview if you don't have the complete data " +"structure of the external system in mind." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Priority > Name" +#: ../system/objects/types.rst:299 +msgid "" +"An example of a configured external data source field from agent perspective:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.priority.name}``" +#: ../system/objects/types.rst:0 +msgid "Screencast showing the search for a product in a ticket" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2 normal``" +#: ../system/objects/types.rst:307 +msgid "URL fields (Link-Template)" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Pending till" +#: ../system/objects/types.rst:311 +msgid "" +"This function is restricted to Text, Select and External data source types " +"only." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.pending_time}``" +#: ../system/objects/types.rst:314 +msgid "" +"Link-Templates are an amazing way to dynamically generate URLs. They allow " +"you to integrate other systems better without having to manually copy data " +"from Zammad if possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not set" +#: ../system/objects/types.rst:320 +msgid "" +"Another great way of communicating with another system may be Zammad's :doc:" +"`Webhooks `." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Web" +#: ../system/objects/types.rst:323 +msgid "" +"After filling a link-template enabled field, an URL icon will appear on its " +"right. Clicking on the icon opens a new tab." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.web}``" +#: ../system/objects/types.rst:328 +msgid "" +"Even though Zammad displays the link template within object edit and create " +"screens, the function is optional. It's only active if you populate the " +"field." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``https://zammad.com`` or empty if not set" +#: ../system/objects/types.rst:333 +msgid "" +"What's the difference between URL and text fields with link template...?!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > VIP" +#: ../system/objects/types.rst:335 +msgid "" +"Both fields have different use cases. Use ``text`` type text fields when " +"ever you have a *static* url that requires dynamic parameters. If you " +"require a drag & drop like field that you can put in any URL, use ``URL`` " +"type text fields." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.vip}``" +#: ../system/objects/types.rst:340 +msgid "" +"The difference is easier to spot when comparing the fields directly, below " +"screencast shows the result - the dynamic approach uses existing values in " +"the moment of updating to built the URL - e.g. ``https://google.com/search?" +"q=cookies`` - while the URL approach uses the actual URL of the field - e.g. " +"``https://zammad.com``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Phone" +#: ../system/objects/types.rst:None +msgid "" +"Screencast showing the differents in between URL and text type fields with " +"actual values" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.phone}``" +#: ../system/objects/types.rst:352 +msgid "How does this work...?!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Note" +#: ../system/objects/types.rst:354 +msgid "" +"As an example, let's say you have an attribute called ``amazing_attribute`` " +"and you want to open a google search directly with the input from that field." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.note}``" +#: ../system/objects/types.rst:357 +msgid "" +"Providing the link-template field below allows you to do so: ``https://www." +"google.com/search?q=#{ticket.amazing_attribute}``" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Mobile" +#: ../system/objects/types.rst:362 +msgid "" +"You can use any :doc:`Zammad variable ` as long as it's " +"available in the moment you need it." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.mobile}``" +#: ../system/objects/types.rst:365 +msgid "" +"As a result, you are redirected to Google with a search for the value of the " +"attribute, if you click on the button in the ticket (as you can see in the " +"screencast above)." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Login" +#: ../system/packages.rst:2 +msgid "Packages" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.login}``" +#: ../system/packages.rst:4 +msgid "That's the package management-area." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``agent``" +#: ../system/packages.rst:6 +msgid "Individual add-ons for Zammad can be installed and managed here." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Lastname" +#: ../system/sessions.rst:2 +msgid "Sessions" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.lastname}``" +#: ../system/sessions.rst:4 +msgid "" +"Sessions management allows reviewing currently known user sessions and " +"allows to end these. The session timeout is affected by :ref:" +"`security_session_timeout` configurations from security settings." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Mustermann`` or empty if not set" +#: ../system/sessions.rst:None +msgid "Screenshot showing Zammad's session management" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Firstname" +#: ../system/sessions.rst:13 +msgid "Zammad will provide the following information:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.firstname}``" +#: ../system/sessions.rst:16 +msgid "" +"The user account this session entry belongs to. It can be normal if a user " +"has several sessions in the list. This can be due to changed browser " +"information or if you use e.g. single sign on methods where the user does " +"not use the log off button." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Max`` or empty if not set" +#: ../system/sessions.rst:22 +msgid "Browser" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Fax" +#: ../system/sessions.rst:22 +msgid "The browser agent communicated to Zammad." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.fax}``" +#: ../system/sessions.rst:40 +msgid "Location" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Email" +#: ../system/sessions.rst:25 +msgid "" +"The anticipated location based on the users IP address. Depending on the IP " +"address the result shown may differ. This option depends on :doc:`/settings/" +"system/services`." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.email}``" +#: ../system/sessions.rst:29 +msgid "The following information can be shown:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``agent@company.tld`` or empty if not set" +#: ../system/sessions.rst:33 +msgid "IP address" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Department" +#: ../system/sessions.rst:32 +msgid "" +"Either if you set *Geo IP services* to inactive or you're using internal IP " +"address which do not provide location information." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.department}``" +#: ../system/sessions.rst:40 +msgid "Country (or Country + City)" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Support`` or empty if not set" +#: ../system/sessions.rst:36 +msgid "" +"If *Geo IP services* is enabled only. Depends on how detailed the available " +"IP address information are." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Avatar" +#: ../system/sessions.rst:39 +msgid "" +"Be aware that results can be inaccurate - this technically is not an error." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.avatar(60,60)}``" +#: ../system/sessions.rst:43 +msgid "Age" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Address" +#: ../system/sessions.rst:43 +msgid "Provides the time when the session initially has been created." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.address}``" +#: ../system/sessions.rst:50 +msgid "Update" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Shared organization" +#: ../system/sessions.rst:46 +msgid "" +"Provides the time the user used this session to open Zammad. This timestamp " +"is only updated if the user e.g. reloads, not during normal work on tickets." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.shared}``" +#: ../system/sessions.rst:50 +msgid "This timestamp is being used for the session timeout." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Note" +#: ../system/sessions.rst:53 +msgid "" +"Use the delete button to remove a single session on behalf of your user." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.note}``" +#: ../system/subscription.rst:2 +msgid "Subscription (SaaS)" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Name" +#: ../system/subscription.rst:4 +msgid "" +"The subscription settings page allows you to configure your instances " +"package and number of agents required." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.name}``" +#: ../system/subscription.rst:9 +msgid "" +"This setting section is only available for Hosted setups. If you're looking " +"for on premise support contracts, please see the `Zammad pricing page " +"`_." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Zammad GmbH`` or empty if not set" +#: ../system/subscription.rst:14 ../system/subscription.rst:34 +msgid "Plan" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Domain based assignment" +#: ../system/subscription.rst:16 +msgid "" +"Here you can set up everything affecting your instance subscription " +"functions like number of agents and package." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.domain_assignment}``" +#: ../system/subscription.rst:19 +msgid "" +"On top of the page you can find a subscription summary. You'll find the " +"number of used and available (booked) agent seats there. By using the *see " +"more* link you can also expand an agent list to see the currently configured " +"active agents. This list *does not* count accounts with admin permissions " +"only." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Domain" +#: ../system/subscription.rst:None +msgid "" +"Within subscription you can always see how many agents are still\n" +"available to add and who uses the seats." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.domain}``" +#: ../system/subscription.rst:29 +msgid "" +"Learn more on how to manage your agents in general :doc:`here `." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``domain.tld`` or empty if not set" +#: ../system/subscription.rst:36 +msgid "" +"This section gives you an overview of the available plans and their " +"functions / limits. If you require a more detailed table, check our " +"`detailed pricing table `_ for more." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > VIP" +#: ../system/subscription.rst:40 +msgid "" +"Your selection in this step will decide on the base agent price and e.g. " +"agent limits that might apply in the summary step." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.vip}``" +#: ../system/subscription.rst:43 +msgid "" +"The green *Selected* button will also tell you what plan you're currently in." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Number" +#: ../system/subscription.rst:47 +msgid "" +"Trial instances are running at Professional with 3 agents. The plan cannot " +"be changed during the trial for technical reasons, if you require more " +"agents for testing, please contact `our sales team `_ with a reason for the raise request." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.number}``" +#: ../system/subscription.rst:None +msgid "" +"Screenshot showing three available packages for a hosted Zammad\n" +"instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``31001``, ``201910731001``, ..." +#: ../system/subscription.rst:57 +msgid "" +"At the bottom of this block you can find a summary where you can adjust the " +"settings of the previous selected plan." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > ID" +#: ../system/subscription.rst:62 +msgid "" +"Note that upgrading (more agents, higher package) is always possible, " +"however, downgrading will only happen when your billing period renews." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.id}``" +#: ../system/subscription.rst:66 +msgid "" +"Upgrading resets your billing period and existing credit will be deducted " +"from the new total." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``17``, ``5281``, ..." +#: ../system/subscription.rst:75 +msgid "Billing cycle" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact (customer)" +#: ../system/subscription.rst:70 +msgid "" +"You can choose between either monthly or yearly billing. The price per agent " +"will be cheaper if you decide for yearly billing." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_customer_at}``" +#: ../system/subscription.rst:73 +msgid "" +"If you're still trying out things and are unsure of the right package for " +"your instance, you may want to choose monthly first and then upgrade to " +"yearly when you're sure." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "" -"``2019-10-07 16:25:00 UTC`` or empty if not applicable yet (Please note " -"`Ticket last contact behavior Settings `_ for this)" +#: ../system/subscription.rst:83 +msgid "Plan: (Starter|Professional|Plus) - Agents" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact" +#: ../system/subscription.rst:78 +msgid "Choose the number of agents you require for your instance." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_at}``" +#: ../system/subscription.rst:80 +msgid "" +"Keep in mind that some packages may have agent limits. Depending on the " +"previous chosen package, you won't be able to exceed specific agent numbers. " +"Also note that setting less agents than currently configured is not possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact (agent)" +#: ../system/subscription.rst:86 +msgid "Total" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_agent_at}``" +#: ../system/subscription.rst:86 +msgid "This will be the net total you're going to be billed." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable yet" +#: ../system/subscription.rst:88 +msgid "" +"By using the *Update subscription* button, the instance package will be " +"adjusted immediately. If you didn't provide a payment method yet, Zammad " +"will request you to provide one at this point." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Note" +#: ../system/subscription.rst:94 +msgid "" +"In case you're still within the trial period, this means that the trial will " +"be over immediately!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.note}``" +#: ../system/subscription.rst:97 +msgid "Down- or upgrading during the trial period *is not* possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Note about this group``" +#: ../system/subscription.rst:None +msgid "Screenshot showing payment options and a pricing summary" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Name" +#: ../system/subscription.rst:103 +msgid "Billing Information" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.name}``" +#: ../system/subscription.rst:105 +msgid "" +"You can control all billing relevant information like invoices, billing " +"address and the option to cancel your subscription." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Sales``" +#: ../system/subscription.rst:108 +msgid "" +"All adjusted billing information below only affect future invoices. If your " +"invoice was issued wrong, please contact `our sales team `_." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Follow-up possible" +#: ../system/subscription.rst:114 +msgid "Billing address" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.follow_up_possible}``" +#: ../system/subscription.rst:113 +msgid "" +"Provide your company address here, make sure to include the companies name " +"in case required. This address will be referenced on your invoice." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``no`` or ``yes``" +#: ../system/subscription.rst:118 +msgid "VAT ID" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Assign Follow-Ups" +#: ../system/subscription.rst:117 +msgid "" +"Provide your VAT ID here. If applicable your invoice will not contain German " +"VAT. Please make sure to pay the VAT in your country as required." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.follow_up_assignment}``" +#: ../system/subscription.rst:127 +msgid "Billing Email Address" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Assignment Timeout" +#: ../system/subscription.rst:121 +msgid "" +"Usually the instance owner (the person that registered the instance) will " +"receive all emails including the invoices. In case you have your own billing " +"department, you can provide their email address here." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.assignment_timeout}``" +#: ../system/subscription.rst:125 +msgid "" +"All billing relevant information will then be sent to this email address." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``20`` or empty if not configured" +#: ../system/subscription.rst:127 +msgid "Invoices are sent as attachment (PDF) to this email address." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > First response" +#: ../system/subscription.rst:129 +msgid "" +"Don't forget to press the *Update billing information* button after you " +"changed above settings." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.first_response_at}``" +#: ../system/subscription.rst:None +msgid "" +"Screenshot showing options for billing information within the\n" +"subscription menu" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Escalation at" +#: ../system/subscription.rst:137 +msgid "Payment Method" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.escalation_at}``" +#: ../system/subscription.rst:139 +msgid "You can pay via credit card or SEPA mandate." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable" +#: ../system/subscription.rst:144 +msgid "Credit card" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Web" +#: ../system/subscription.rst:142 +msgid "" +"Simply follow the dialogue by clicking *authorize credit card* and confirm -" +"if required by your bank- your consent to Zammad using your card for the " +"payments." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.web}``" +#: ../system/subscription.rst:148 +msgid "SEPA Direct Debit" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > VIP" +#: ../system/subscription.rst:147 +msgid "" +"Provide the requested information of the bank account holder and update if " +"you're ready. You'll then receive an email with the SEPA mandate." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.vip}``" +#: ../system/subscription.rst:150 +msgid "" +"Technically there's also the possibility to pay via invoice, however - this " +"method only applies to a fairly low number of instances. Please contact `our " +"sales team `_ for more information." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Phone" +#: ../system/subscription.rst:156 +msgid "Cancel Subscription" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.phone}``" +#: ../system/subscription.rst:158 +msgid "" +"Do you want to cancel your subscription? In case you no longer want to use " +"Zammad's SaaS, you can cancel your subscription by using the red *Yes, " +"please cancel my subscription* button." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Note" +#: ../system/subscription.rst:162 +msgid "" +"To cancel the description, enter the FQDN of your Zammad instance and " +"provide a reason for your cancellation." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.note}``" +#: ../system/subscription.rst:165 +msgid "" +"Your subscription will end the day after your trial or billing period ends." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Mobile" +#: ../system/subscription.rst:None +msgid "Screenshot showing subscription cancellation dialog" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.mobile}``" +#: ../system/subscription.rst:174 +msgid "" +"We will remind you about your cancelled subscription several times up front. " +"After the subscription ended all instance data will be removed. A restore " +"*is not* possible after that point!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Login" +#: ../system/subscription.rst:178 +msgid "**😖 Cancelled by accident?**" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.login}``" +#: ../system/subscription.rst:180 +msgid "" +"You can always undo the cancellation via the *Yes, undo the cancellation of " +"my subscription* button up to the last subscription day!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Lastname" +#: ../system/subscription.rst:0 +msgid "" +"Screenshot showing a red button to cancel the subscription\n" +"cancellation" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.lastname}``" +#: ../system/subscription.rst:189 +msgid "Payment History" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Firstname" +#: ../system/subscription.rst:191 +msgid "" +"The payment history will display a history of all paid invoices. At this " +"point you can also download these in case you need them again." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.firstname}``" +#: ../system/subscription.rst:196 +msgid "" +"You will only find *paid* invoices here. Invoices that are to be billed are " +"not available before the payment is completed." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Fax" +#: ../system/subscription.rst:201 +msgid "Date" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.fax}``" +#: ../system/subscription.rst:201 +msgid "Date of the invoice creation." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Email" +#: ../system/subscription.rst:204 +msgid "Amount" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.email}``" +#: ../system/subscription.rst:204 +msgid "Invoice total including VAT if applicable." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Department" +#: ../system/subscription.rst:207 +msgid "" +"Contains contract period (monthly or yearly) and hosted plan for the " +"subscription period in question." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.department}``" +#: ../system/subscription.rst:218 +msgid "Payment method / Service period" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Avatar" +#: ../system/subscription.rst:211 +msgid "" +"Used bank account or credit card as well as the subscription period the " +"invoice is about." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.avatar(60,60)}``" +#: ../system/subscription.rst:216 +msgid "" +"It might happen that the invoice date and subscription period differ. This " +"is nothing to worry about, the subscription periods will be accounted later " +"on." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Address" +#: ../system/subscription.rst:222 +msgid "Receipt" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.address}``" +#: ../system/subscription.rst:221 +msgid "" +"Use the arrow to download the invoice in question. You can download all " +"available invoices any time you need to here!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Web" +#: ../system/subscription.rst:None +msgid "Screenshot showing payment history of a hosted instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.web}``" +#: ../system/subscription.rst:229 +msgid "FAQ" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > VIP" +#: ../system/subscription.rst:233 +msgid "I set up a trial account but am missing functions to test" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.vip}``" +#: ../system/subscription.rst:232 +msgid "" +"The trial instance is running within the professional package allowing up to " +"three agents." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Phone" +#: ../system/subscription.rst:236 +msgid "Can I change package within the trial?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.phone}``" +#: ../system/subscription.rst:236 +msgid "No. As soon as the package is changed the subscription begins." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Note" +#: ../system/subscription.rst:241 +msgid "What happens to my trial instance after the trial period ended?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.note}``" +#: ../system/subscription.rst:239 +msgid "" +"Your instance will automatically be canceled for you. Please see *What " +"happens to my instance after it has been canceled?* for more." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Mobile" +#: ../system/subscription.rst:254 +msgid "What happens to my instance after it has been canceled?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.mobile}``" +#: ../system/subscription.rst:244 +msgid "That depends slightly on your instance state:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Login" +#: ../system/subscription.rst:250 +msgid "Trial instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.login}``" +#: ../system/subscription.rst:247 +msgid "" +"If you're still on trial, we will ice your instance and remind you once " +"again about your instance. We then will wait some days and remove your " +"instance from our system. This is the last time we will inform you by Email." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Lastname" +#: ../system/subscription.rst:254 +msgid "Paid instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.lastname}``" +#: ../system/subscription.rst:253 +msgid "" +"If you're a paying customer and canceled your subscription, the instance " +"removal will take place the day after your last subscription day." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Firstname" +#: ../system/subscription.rst:256 +msgid "Can removed instances be restored?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.firstname}``" +#: ../system/subscription.rst:257 +msgid "No. Once your instance has been removed, a restoration is not possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Fax" +#: ../system/system-report.rst:2 +msgid "System Report" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.fax}``" +#: ../system/system-report.rst:4 +msgid "" +"In this place you can't configure Zammad. Instead you can obtain a system " +"report about Zammad and its configuration." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Email" +#: ../system/system-report.rst:7 +msgid "" +"See the description in Zammad for an explanation. You can even find a " +"preview of the included data below the **Download** button." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.email}``" +#: ../system/system-report.rst:10 +msgid "" +"Zammad never sends this automatically to anyone. It is a manual process only " +"to provide better support based on your configuration." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Department" +#: ../system/translations.rst:2 +msgid "Translations" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.department}``" +#: ../system/translations.rst:4 +msgid "" +"Translations of Zammad are processed centrally in our `Weblate instance " +"`_. This allows non-developers to review " +"and update translation texts of the language they actually speak." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Avatar" +#: ../system/translations.rst:9 +msgid "" +"Your language is in an incomplete translation state or has typos? Please " +"consider helping us in sorting this out! All you need is either a GitHub " +"account or to register directly in our instance." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.avatar(60,60)}``" +#: ../system/translations.rst:13 +msgid "" +"Did you know? This is also where the documentation translations are handled. " +"🤓" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Address" +#: ../system/translations.rst:15 +msgid "" +"Have a look in our :docs:`contribution section ` in the system documentation to get started!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.address}``" +#: ../system/translations.rst:20 +msgid "Local Translations" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created at" +#: ../system/translations.rst:22 +msgid "" +"Apart from these system translations, there's still local translations you " +"can manage. This is relevant if you added custom objects that require " +"translations or even custom states and priorities." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_at}``" +#: ../system/translations.rst:None +msgid "Translation management screen within the admin menu" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "2019-10-07 16:25:00 UTC" +#: ../system/translations.rst:31 +msgid "Updating Translations" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Closing time" +#: ../system/translations.rst:33 +msgid "" +"Because of how Zammad ships translations, the only way to update the system " +"translations is to update your Zammad installation. The benefit of this is " +"that you no longer need internet access during a Zammad upgrade as the " +"package has everything it requires already." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.close_at}``" +#: ../system/translations.rst:39 +msgid "Translation of Custom Objects" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "2019-10-07 17:25:00 UTC" +#: ../system/translations.rst:41 +msgid "" +"No problem at all! You can customize any translation locally, even if it is " +"not initially provided by the system." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``3``, any number of articles existing in the ticket right now" +#: ../system/translations.rst:44 +msgid "" +"Translation is supported for a broad number of features, including but not " +"limited to custom:" msgstr "" -#: ../system/version.rst:2 -msgid "Version" +#: ../system/translations.rst:47 +msgid "Object Attributes" msgstr "" -#: ../system/version.rst:4 -msgid "Shows which version is currently being used on your Zammad-instance." +#: ../system/translations.rst:48 +msgid "Ticket Macros" msgstr "" -#: ../manage/roles/admin-permissions.rst:53 -msgid "``admin.checklist``" +#: ../system/translations.rst:49 +msgid "Ticket Overviews" msgstr "" -#: ../manage/roles/admin-permissions.rst:54 -msgid ":doc:`Manage > Checklist `" +#: ../system/translations.rst:50 +msgid "Ticket Priorities" msgstr "" -#: ../manage/roles/admin-permissions.rst:83 -msgid "``admin.channel_whatsapp``" +#: ../system/translations.rst:51 +msgid "Ticket States" msgstr "" -#: ../manage/roles/admin-permissions.rst:84 -msgid ":doc:`Channels > Whatsapp `" +#: ../system/translations.rst:54 +msgid "Customizing Translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:124 -msgid "``admin.public_links``" +#: ../system/translations.rst:56 +msgid "" +"Within the translation screen, simply click on the **New Translation** " +"button." msgstr "" -#: ../manage/roles/admin-permissions.rst:125 -msgid ":doc:`Manage > Public Links `" +#: ../system/translations.rst:None +msgid "New translation dialog" msgstr "" -#: ../manage/roles/admin-permissions.rst:151 -msgid "``admin.system_report``" +#: ../system/translations.rst:62 +msgid "" +"In the dialog you can immediately enter the exact translation source (if you " +"know it) and your custom translation text for it and click **Submit**." msgstr "" -#: ../manage/roles/admin-permissions.rst:152 -msgid ":doc:`System > System Report `" +#: ../system/translations.rst:65 +msgid "" +"Alternatively, try to search for translation suggestions in the list below. " +"Selecting an item from the list will pre-fill the translation source for you " +"and then you can just enter your custom translation." msgstr "" -#: ../manage/roles/admin-permissions.rst:166 -msgid "``admin.ticket_auto_assignment``" +#: ../system/translations.rst:69 +msgid "" +"The target language will always default to your current language selection. " +"If you need to translate for a different language, simply change the " +"selection before submitting." msgstr "" -#: ../manage/roles/admin-permissions.rst:167 -msgid ":ref:`Settings > Ticket > Auto Assignment `" +#: ../system/translations.rst:73 +msgid "" +"All your custom translations will show up in the overview table when added. " +"And they will even persist across Zammad updates!" msgstr "" -#: ../manage/roles/admin-permissions.rst:169 -msgid "``admin.ticket_duplicate_detection``" +#: ../system/translations.rst:76 +msgid "" +"Make sure to reload your browser if a translated string is not displayed." msgstr "" -#: ../manage/roles/admin-permissions.rst:170 -msgid ":ref:`Settings > Ticket > Duplicate Detection `" +#: ../system/translations.rst:80 +msgid "Reverting to Original Translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:172 -msgid "``admin.ticket_priority``" +#: ../system/translations.rst:82 +msgid "" +"If you want to revert a custom translation to original text, simply use the " +"appropriate action within the row of the overview table." msgstr "" -#: ../manage/roles/admin-permissions.rst:173 -msgid ":ref:`System > Objects >Ticket Priority `" +#: ../system/translations.rst:85 +msgid "" +"Depending on the type of the translation source, the action has a slightly " +"different name:" msgstr "" -#: ../manage/roles/admin-permissions.rst:175 -msgid "``admin.ticket_state``" +#: ../system/translations.rst:88 +msgid "**Reset** for customized system translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:176 -msgid ":ref:`System > Objects >Ticket State `" +#: ../system/translations.rst:89 +msgid "**Remove** for customized local translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:193 -msgid "``admin.webhook``" +#: ../system/translations.rst:91 +msgid "" +"In both cases, the action will remove the customized translation after a " +"confirmation." msgstr "" -#: ../manage/roles/admin-permissions.rst:194 -msgid ":doc:`Manage > Webhook `" +#: ../system/translations.rst:None +msgid "Screenshot showing the location of the Remove action" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:43 -msgid "``user_preferences.appearance``" +#: ../system/translations.rst:99 +msgid "Inline Translations" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:44 -msgid "Appearance configuration" +#: ../system/translations.rst:101 +msgid "" +"If you prefer a more hands-on approach, you can activate the inline or on-" +"screen translation feature by pressing ``ctrl`` + ``alt`` + ``t`` at any " +"time and on any screen." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:0 -msgid "Users can switch between dark, light and" +#: ../system/translations.rst:105 +msgid "" +"All customizable translation texts will be highlighted for you on the " +"screen. Just click into the highlighted area and update the text in place." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:0 -msgid "automatic mode." +#: ../system/translations.rst:None +msgid "Inline translation mode activated for the Overview screen" msgstr "" -#: ../system/system-report.rst:2 -msgid "System Report" +#: ../system/translations.rst:112 +msgid "" +"When finished editing, simply press ``ctrl`` + ``alt`` + ``t`` again to " +"deactivate." msgstr "" -#: ../system/system-report.rst:4 +#: ../system/translations.rst:117 msgid "" -"In this place you can't configure Zammad. Instead you can obtain a system " -"report about Zammad and its configuration." +"Even though it's available on any screen, the inline translation feature " +"requires admin permissions. It works only for the current language " +"selection. If you need to translate a different language, first change the " +"language in your :user-docs:`profile settings `." msgstr "" -#: ../system/system-report.rst:7 -msgid "" -"See the description in Zammad for an explanation. You can even find a " -"preview of the included data below the **Download** button." +#: ../system/version.rst:2 +msgid "Version" msgstr "" -#: ../system/system-report.rst:10 -msgid "" -"Zammad never sends this automatically to anyone. It is a manual process only " -"to provide better support based on your configuration." +#: ../system/version.rst:4 +msgid "Shows which version is currently being used on your Zammad-instance." msgstr "" diff --git a/locale/it/LC_MESSAGES/admin-docs.po b/locale/it/LC_MESSAGES/admin-docs.po index 771f7dee..d06bfa62 100644 --- a/locale/it/LC_MESSAGES/admin-docs.po +++ b/locale/it/LC_MESSAGES/admin-docs.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Zammad\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-11-06 10:31+0100\n" +"POT-Creation-Date: 2024-11-12 16:31+0100\n" "PO-Revision-Date: 2023-04-15 10:17+0000\n" "Last-Translator: crnfpp \n" "Language-Team: Italian Checklist `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:56 msgid "``admin.channel_email``" msgstr "" -#: ../manage/roles/admin-permissions.rst:54 #: ../manage/roles/admin-permissions.rst:57 msgid ":doc:`Channels > Email `" msgstr "" -#: ../manage/roles/admin-permissions.rst:56 #: ../manage/roles/admin-permissions.rst:59 msgid "``admin.channel_facebook``" msgstr "" -#: ../manage/roles/admin-permissions.rst:57 #: ../manage/roles/admin-permissions.rst:60 msgid ":doc:`Channels > Facebook `" msgstr "" -#: ../manage/roles/admin-permissions.rst:58 #: ../manage/roles/admin-permissions.rst:61 msgid "" "Accessing Facebook tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:59 #: ../manage/roles/admin-permissions.rst:62 msgid "``admin.channel_formular``" msgstr "" -#: ../manage/roles/admin-permissions.rst:60 #: ../manage/roles/admin-permissions.rst:63 msgid ":doc:`Channels > Form `" msgstr "" -#: ../manage/roles/admin-permissions.rst:62 #: ../manage/roles/admin-permissions.rst:65 msgid "``admin.channel_google``" msgstr "" -#: ../manage/roles/admin-permissions.rst:63 #: ../manage/roles/admin-permissions.rst:66 msgid ":doc:`Channels > Google `" msgstr "" -#: ../manage/roles/admin-permissions.rst:65 #: ../manage/roles/admin-permissions.rst:68 msgid "``admin.channel_microsoft365``" msgstr "" -#: ../manage/roles/admin-permissions.rst:66 #: ../manage/roles/admin-permissions.rst:69 msgid ":doc:`Channels > Microsoft 365 `" msgstr "" -#: ../manage/roles/admin-permissions.rst:68 #: ../manage/roles/admin-permissions.rst:71 msgid "``admin.channel_sms``" msgstr "" -#: ../manage/roles/admin-permissions.rst:69 #: ../manage/roles/admin-permissions.rst:72 msgid ":doc:`Channels > SMS `" msgstr "" -#: ../manage/roles/admin-permissions.rst:71 #: ../manage/roles/admin-permissions.rst:74 msgid "``admin.channel_telegram``" msgstr "" -#: ../manage/roles/admin-permissions.rst:72 #: ../manage/roles/admin-permissions.rst:75 msgid ":doc:`Channels > Telegram `" msgstr "" -#: ../manage/roles/admin-permissions.rst:73 #: ../manage/roles/admin-permissions.rst:76 msgid "" "Accessing Telegram tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:74 #: ../manage/roles/admin-permissions.rst:77 msgid "``admin.channel_twitter``" msgstr "" -#: ../manage/roles/admin-permissions.rst:75 #: ../manage/roles/admin-permissions.rst:78 msgid ":doc:`Channels > Twitter `" msgstr "" -#: ../manage/roles/admin-permissions.rst:76 #: ../manage/roles/admin-permissions.rst:79 msgid "" "Accessing Twitter/X tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:77 #: ../manage/roles/admin-permissions.rst:80 msgid "``admin.channel_web``" msgstr "" -#: ../manage/roles/admin-permissions.rst:78 #: ../manage/roles/admin-permissions.rst:81 msgid ":doc:`Channels > Web `" msgstr "" -#: ../manage/roles/admin-permissions.rst:80 +#: ../manage/roles/admin-permissions.rst:83 +msgid "``admin.channel_whatsapp``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:84 +msgid ":doc:`Channels > Whatsapp `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:86 msgid "``admin.core_workflows``" msgstr "" -#: ../manage/roles/admin-permissions.rst:81 #: ../manage/roles/admin-permissions.rst:87 msgid ":doc:`System > Core Workflows `" msgstr "" -#: ../manage/roles/admin-permissions.rst:83 #: ../manage/roles/admin-permissions.rst:89 msgid "``admin.data_privacy``" msgstr "" -#: ../manage/roles/admin-permissions.rst:84 #: ../manage/roles/admin-permissions.rst:90 msgid ":doc:`System > Data Privacy `" msgstr "" -#: ../manage/roles/admin-permissions.rst:85 #: ../manage/roles/admin-permissions.rst:91 msgid "" "🔥 Be careful, it allows users to permanently delete data on the system." msgstr "" -#: ../manage/roles/admin-permissions.rst:86 #: ../manage/roles/admin-permissions.rst:92 msgid "``admin.group``" msgstr "" -#: ../manage/roles/admin-permissions.rst:87 #: ../manage/roles/admin-permissions.rst:93 msgid ":doc:`Manage > Groups `" msgstr "" -#: ../manage/roles/admin-permissions.rst:89 #: ../manage/roles/admin-permissions.rst:95 msgid "``admin.integration``" msgstr "" -#: ../manage/roles/admin-permissions.rst:90 #: ../manage/roles/admin-permissions.rst:96 msgid ":doc:`System > Integrations `" msgstr "" -#: ../manage/roles/admin-permissions.rst:92 #: ../manage/roles/admin-permissions.rst:98 msgid "``admin.knowledge_base``" msgstr "" -#: ../manage/roles/admin-permissions.rst:93 #: ../manage/roles/admin-permissions.rst:99 msgid ":doc:`Manage > Knowledge Base `" msgstr "" @@ -8559,57 +8542,46 @@ msgid "" "knowledge-base.html#editing-answers>`." msgstr "" -#: ../manage/roles/admin-permissions.rst:98 #: ../manage/roles/admin-permissions.rst:104 msgid "``admin.macro``" msgstr "" -#: ../manage/roles/admin-permissions.rst:99 #: ../manage/roles/admin-permissions.rst:105 msgid ":doc:`Manage > Macros `" msgstr "" -#: ../manage/roles/admin-permissions.rst:100 #: ../manage/roles/admin-permissions.rst:106 msgid "In some cases, macros may also require ``admin.tag``" msgstr "" -#: ../manage/roles/admin-permissions.rst:101 #: ../manage/roles/admin-permissions.rst:107 msgid "``admin.maintenance``" msgstr "" -#: ../manage/roles/admin-permissions.rst:102 #: ../manage/roles/admin-permissions.rst:108 msgid ":doc:`System > Maintenance `" msgstr "" -#: ../manage/roles/admin-permissions.rst:104 #: ../manage/roles/admin-permissions.rst:110 msgid "``admin.monitoring``" msgstr "" -#: ../manage/roles/admin-permissions.rst:105 #: ../manage/roles/admin-permissions.rst:111 msgid ":doc:`System > Monitoring `" msgstr "" -#: ../manage/roles/admin-permissions.rst:107 #: ../manage/roles/admin-permissions.rst:113 msgid "``admin.object``" msgstr "" -#: ../manage/roles/admin-permissions.rst:108 #: ../manage/roles/admin-permissions.rst:114 msgid ":doc:`System > Objects `" msgstr "" -#: ../manage/roles/admin-permissions.rst:110 #: ../manage/roles/admin-permissions.rst:116 msgid "``admin.organization``" msgstr "" -#: ../manage/roles/admin-permissions.rst:111 #: ../manage/roles/admin-permissions.rst:117 msgid ":doc:`Manage > Organizations `" msgstr "" @@ -8626,202 +8598,210 @@ msgstr "" msgid "They can even edit an organization's name, domain, and notes!" msgstr "" -#: ../manage/roles/admin-permissions.rst:115 #: ../manage/roles/admin-permissions.rst:121 msgid "``admin.overview``" msgstr "" -#: ../manage/roles/admin-permissions.rst:116 #: ../manage/roles/admin-permissions.rst:122 msgid ":doc:`Manage > Overviews`" msgstr "" -#: ../manage/roles/admin-permissions.rst:118 +#: ../manage/roles/admin-permissions.rst:124 +msgid "``admin.public_links``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:125 +msgid ":doc:`Manage > Public Links `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:127 msgid "``admin.package``" msgstr "" -#: ../manage/roles/admin-permissions.rst:119 #: ../manage/roles/admin-permissions.rst:128 msgid ":doc:`System > Packages `" msgstr "" -#: ../manage/roles/admin-permissions.rst:121 #: ../manage/roles/admin-permissions.rst:130 msgid "``admin.report_profile``" msgstr "" -#: ../manage/roles/admin-permissions.rst:122 #: ../manage/roles/admin-permissions.rst:131 msgid ":doc:`Manage > Report Profiles `" msgstr "" -#: ../manage/roles/admin-permissions.rst:123 #: ../manage/roles/admin-permissions.rst:132 msgid "Access to view reports: ``report``" msgstr "" -#: ../manage/roles/admin-permissions.rst:124 #: ../manage/roles/admin-permissions.rst:133 msgid "``admin.role``" msgstr "" -#: ../manage/roles/admin-permissions.rst:125 #: ../manage/roles/admin-permissions.rst:134 msgid ":doc:`Manage > Roles `" msgstr "" -#: ../manage/roles/admin-permissions.rst:127 #: ../manage/roles/admin-permissions.rst:136 msgid "``admin.scheduler``" msgstr "" -#: ../manage/roles/admin-permissions.rst:128 #: ../manage/roles/admin-permissions.rst:137 msgid ":doc:`Manage > Scheduler `" msgstr "" -#: ../manage/roles/admin-permissions.rst:129 #: ../manage/roles/admin-permissions.rst:138 msgid "For automation on tickets" msgstr "" -#: ../manage/roles/admin-permissions.rst:130 #: ../manage/roles/admin-permissions.rst:139 msgid "``admin.security``" msgstr "" -#: ../manage/roles/admin-permissions.rst:131 #: ../manage/roles/admin-permissions.rst:140 msgid ":doc:`Settings > Security `" msgstr "" -#: ../manage/roles/admin-permissions.rst:132 #: ../manage/roles/admin-permissions.rst:141 msgid "Settings of Zammad. This also covers third party authentications." msgstr "" -#: ../manage/roles/admin-permissions.rst:133 #: ../manage/roles/admin-permissions.rst:142 msgid "``admin.session``" msgstr "" -#: ../manage/roles/admin-permissions.rst:134 #: ../manage/roles/admin-permissions.rst:143 msgid ":doc:`System > Sessions `" msgstr "" -#: ../manage/roles/admin-permissions.rst:136 #: ../manage/roles/admin-permissions.rst:145 msgid "``admin.setting_system``" msgstr "" -#: ../manage/roles/admin-permissions.rst:137 #: ../manage/roles/admin-permissions.rst:146 msgid ":doc:`Settings > System `" msgstr "" -#: ../manage/roles/admin-permissions.rst:139 #: ../manage/roles/admin-permissions.rst:148 msgid "``admin.sla``" msgstr "" -#: ../manage/roles/admin-permissions.rst:140 #: ../manage/roles/admin-permissions.rst:149 msgid ":doc:`Manage > SLAs `" msgstr "" -#: ../manage/roles/admin-permissions.rst:142 +#: ../manage/roles/admin-permissions.rst:151 +msgid "``admin.system_report``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:152 +msgid ":doc:`System > System Report `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:154 msgid "``admin.tag``" msgstr "" -#: ../manage/roles/admin-permissions.rst:143 #: ../manage/roles/admin-permissions.rst:155 msgid ":doc:`Manage > Tags `" msgstr "" -#: ../manage/roles/admin-permissions.rst:145 #: ../manage/roles/admin-permissions.rst:157 msgid "``admin.template``" msgstr "" -#: ../manage/roles/admin-permissions.rst:146 #: ../manage/roles/admin-permissions.rst:158 msgid ":doc:`Manage > Templates `" msgstr "" -#: ../manage/roles/admin-permissions.rst:148 #: ../manage/roles/admin-permissions.rst:160 msgid "``admin.text_module``" msgstr "" -#: ../manage/roles/admin-permissions.rst:149 #: ../manage/roles/admin-permissions.rst:161 msgid ":doc:`Manage > Text Modules `" msgstr "" -#: ../manage/roles/admin-permissions.rst:151 #: ../manage/roles/admin-permissions.rst:163 msgid "``admin.ticket``" msgstr "" -#: ../manage/roles/admin-permissions.rst:152 #: ../manage/roles/admin-permissions.rst:164 msgid ":doc:`Settings > Tickets `" msgstr "" -#: ../manage/roles/admin-permissions.rst:153 #: ../manage/roles/admin-permissions.rst:165 msgid "Does not grant access to :doc:`/misc/composer`" msgstr "" -#: ../manage/roles/admin-permissions.rst:154 +#: ../manage/roles/admin-permissions.rst:166 +msgid "``admin.ticket_auto_assignment``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:167 +msgid ":ref:`Settings > Ticket > Auto Assignment `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:169 +msgid "``admin.ticket_duplicate_detection``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:170 +msgid ":ref:`Settings > Ticket > Duplicate Detection `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:172 +msgid "``admin.ticket_priority``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:173 +msgid ":ref:`System > Objects >Ticket Priority `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:175 +msgid "``admin.ticket_state``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:176 +msgid ":ref:`System > Objects >Ticket State `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:178 msgid "``admin.time_accounting``" msgstr "" -#: ../manage/roles/admin-permissions.rst:155 #: ../manage/roles/admin-permissions.rst:179 msgid ":doc:`Manage > Time Accounting `" msgstr "" -#: ../manage/roles/admin-permissions.rst:156 #: ../manage/roles/admin-permissions.rst:180 msgid "Also allows the export of timekeeping records." msgstr "" -#: ../manage/roles/admin-permissions.rst:157 #: ../manage/roles/admin-permissions.rst:181 msgid "``admin.translation``" msgstr "" -#: ../manage/roles/admin-permissions.rst:158 #: ../manage/roles/admin-permissions.rst:182 msgid ":doc:`System > Translations `" msgstr "" -#: ../manage/roles/admin-permissions.rst:159 #: ../manage/roles/admin-permissions.rst:183 msgid "Also enables inline translation" msgstr "" -#: ../manage/roles/admin-permissions.rst:160 #: ../manage/roles/admin-permissions.rst:184 msgid "``admin.trigger``" msgstr "" -#: ../manage/roles/admin-permissions.rst:161 #: ../manage/roles/admin-permissions.rst:185 msgid ":doc:`Manage > Triggers `" msgstr "" -#: ../manage/roles/admin-permissions.rst:163 #: ../manage/roles/admin-permissions.rst:187 msgid "``admin.user``" msgstr "" -#: ../manage/roles/admin-permissions.rst:164 #: ../manage/roles/admin-permissions.rst:188 msgid ":doc:`Manage > Users `" msgstr "" @@ -8840,6 +8820,14 @@ msgid "" "from-users-perspective>` ." msgstr "" +#: ../manage/roles/admin-permissions.rst:193 +msgid "``admin.webhook``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:194 +msgid ":doc:`Manage > Webhook `" +msgstr "" + #: ../manage/roles/agent-permissions.rst:2 msgid "Agent Permissions" msgstr "" @@ -9258,36 +9246,45 @@ msgid "than the user that generated them." msgstr "" #: ../manage/roles/user-preferences-permissions.rst:43 +msgid "``user_preferences.appearance``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:44 +msgid "Appearance configuration" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "Users can switch between dark, light and" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "automatic mode." +msgstr "" + #: ../manage/roles/user-preferences-permissions.rst:47 msgid "``user_preferences.avatar``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:44 #: ../manage/roles/user-preferences-permissions.rst:48 msgid "Avatar settings" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:45 #: ../manage/roles/user-preferences-permissions.rst:49 msgid "Override the default Gravatar with a custom avatar" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:46 #: ../manage/roles/user-preferences-permissions.rst:50 msgid "``user_preferences.calendar``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:47 #: ../manage/roles/user-preferences-permissions.rst:51 msgid "Configure the calendar feed" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:49 #: ../manage/roles/user-preferences-permissions.rst:53 msgid "``user_preferences.device``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:50 #: ../manage/roles/user-preferences-permissions.rst:54 msgid "Manage device login sessions" msgstr "" @@ -9304,22 +9301,18 @@ msgstr "" msgid "To learn more, see :doc:`/manage/trigger/system-notifications`." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:54 #: ../manage/roles/user-preferences-permissions.rst:58 msgid "``user_preferences.language``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:55 #: ../manage/roles/user-preferences-permissions.rst:59 msgid "Configure the UI locale/language" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:57 #: ../manage/roles/user-preferences-permissions.rst:61 msgid "``user_preferences.linked_accounts``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:58 #: ../manage/roles/user-preferences-permissions.rst:62 #, fuzzy msgid "Account linking" @@ -9344,7 +9337,6 @@ msgstr "" msgid "is the only way users can utilize third-party logins." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:63 #: ../manage/roles/user-preferences-permissions.rst:67 msgid "``user_preferences.notifications``" msgstr "" @@ -9371,7 +9363,6 @@ msgstr "" msgid "Customers can't receive ticket notifications at all." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:69 #: ../manage/roles/user-preferences-permissions.rst:73 msgid "``user_preferences.out_of_office``" msgstr "" @@ -9396,7 +9387,6 @@ msgstr "" msgid "they're replacing." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:75 #: ../manage/roles/user-preferences-permissions.rst:79 msgid "``user_preferences.overview_sorting``" msgstr "" @@ -9425,12 +9415,10 @@ msgstr "" msgid "overviews has no effect on custom orders." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:82 #: ../manage/roles/user-preferences-permissions.rst:86 msgid "``user_preferences.password``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:83 #: ../manage/roles/user-preferences-permissions.rst:87 msgid "Change account password" msgstr "" @@ -9447,7 +9435,6 @@ msgstr "" msgid "your only allowed authentication method." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:87 #: ../manage/roles/user-preferences-permissions.rst:91 msgid "``user_preferences.two_factor_authentication``" msgstr "" @@ -9484,7 +9471,7 @@ msgstr "" #: ../manage/scheduler.rst:19 msgid "" -"Schedulers can be used to send periodic reminder emails. Use :doc:`/system/" +"Schedulers can be used to send periodic reminder emails. Use :doc:`/misc/" "variables` to build highly-customized email templates." msgstr "" @@ -10480,7 +10467,7 @@ msgstr "" #: ../manage/text-modules.rst:57 msgid "" -"The example text modules below use :doc:`/system/variables` to dynamically " +"The example text modules below use :doc:`/misc/variables` to dynamically " "insert information like the customer's or agent's names." msgstr "" @@ -10824,8 +10811,8 @@ msgstr "" #: ../misc/object-conditions/basics.rst:144 #: ../misc/object-conditions/basics.rst:160 #: ../misc/object-conditions/basics.rst:168 -#: ../misc/object-conditions/basics.rst:178 ../settings/ticket.rst:2 -#: ../system/variables/ticket.rst:2 +#: ../misc/object-conditions/basics.rst:178 ../misc/variables/ticket.rst:2 +#: ../settings/ticket.rst:2 msgid "Ticket" msgstr "" @@ -11059,7 +11046,7 @@ msgstr "" #: ../manage/trigger/how-do-they-work.rst:79 msgid "" -"Certain actions (such as *email*, *SMS* and *notes*) support :doc:`/system/" +"Certain actions (such as *email*, *SMS* and *notes*) support :doc:`/misc/" "variables`, which can be used to build highly-customized message templates." msgstr "" @@ -11088,7 +11075,7 @@ msgstr "" msgid "" "You can also combine static text with placeholders for text fields. Remember " "that the placeholders' values have to be known during trigger runtime. Learn " -"more about :doc:`/system/variables`." +"more about :doc:`/misc/variables`." msgstr "" #: ../manage/trigger/how-do-they-work.rst:105 @@ -12053,7 +12040,7 @@ msgstr "" msgid "" "When switched on, a code editor will be shown below, where you can configure " "custom payload for your webhook in JSON format. To insert supported :doc:`/" -"system/variables` use ``::`` or ``#{`` shortcuts for autocomplete." +"misc/variables` use ``::`` or ``#{`` shortcuts for autocomplete." msgstr "" #: ../manage/webhook/add.rst:103 @@ -14634,11948 +14621,11839 @@ msgid "" "powerful conditions with AND/OR relations." msgstr "" -#: ../settings/branding.rst:10 -msgid "Product Name" +#: ../misc/variables.rst:2 +msgid "Variables" msgstr "" -#: ../settings/branding.rst:7 +#: ../misc/variables.rst:4 msgid "" -"Defines the name of the application, shown in the web interface, tabs and " -"title bar of the web browser." +"Please note that this is just an overview of available variables. It might " +"be incomplete or variables might not be available within some functions. If " +"you're missing variables or are not sure if something is not working as " +"expected, feel free to ask over at the `Community `_." msgstr "" -#: ../settings/branding.rst:10 -msgid "Default value: ``Zammad Helpdesk``" +#: ../misc/variables.rst:10 +msgid "" +"Variables can be called by typing ``::`` (just like text modules in the " +"frontend), as long as you're in a supported text field within the backend. " +"Zammad will display all variables being available within this context and " +"replace it to the variable as soon as you selected an entry." msgstr "" -#: ../settings/branding.rst:13 -msgid "Will be shown in the app and is included in email footers." +#: ../misc/variables.rst:15 +msgid "" +"You have an empty field which you referenced and it appears as ``-``? That's " +"currently working as designed - you might want to ensure that these fields " +"always have a value." msgstr "" -#: ../settings/branding.rst:19 -msgid "Logo" +#: ../misc/variables.rst:20 +msgid "Variable Categories" msgstr "" -#: ../settings/branding.rst:16 -msgid "Defines the logo of the application, shown in the login page of Zammad." +#: ../misc/variables.rst:31 +msgid "Wait, What About Custom Objects?" msgstr "" -#: ../settings/branding.rst:18 +#: ../misc/variables.rst:33 msgid "" -"Ensure to hit the \"Submit\" button after uploading the logo. Otherwise your " -"change will not be saved." +"Good point! Of course, we can't predict what objects you might create, but " +"we can give you a hint on how to put the puzzle together to get your custom " +"values." msgstr "" -#: ../settings/branding.rst:22 +#: ../misc/variables.rst:36 msgid "" -"Allows to set the default language of the Zammad instance. The here defined " -"locale mostly acts as a fallback for:" -msgstr "" - -#: ../settings/branding.rst:25 -msgid "user preferences (if Zammad can't detect the users locale)" +"For this, we'll talk about the inner part of the variable (so everything " +"within ``#{}``), please put the outer part around to have a valid variable. " +"The first part of the variable name consist of the object type. Currently " +"these are:" msgstr "" -#: ../settings/branding.rst:26 -msgid "CSV output (reporting, time accounting)" +#: ../misc/variables.rst:41 +msgid "Ticket (``ticket``)" msgstr "" -#: ../settings/branding.rst:30 -msgid "Define the timezone of your Zammad installation." +#: ../misc/variables.rst:42 +msgid "User (``user``)" msgstr "" -#: ../settings/branding.rst:32 -msgid "" -"This does not have any effect on timings for your agents or how Zammad " -"stores date and time values." +#: ../misc/variables.rst:43 +msgid "Organization (``organization``)" msgstr "" -#: ../settings/branding.rst:35 -msgid "Changing this value has direct consequences on the following areas:" +#: ../misc/variables.rst:44 +msgid "Group (``group``)" msgstr "" -#: ../settings/branding.rst:37 -msgid ":doc:`/manage/scheduler` tasks" +#: ../misc/variables.rst:46 +msgid "" +"The second part is the name of the attribute. This is the name you define " +"during object creation and can be found within the object attribute menu at " +"any time. The first and second part of a variable is divided by a point, e." +"g.: ``ticket.number`` which will in total be ``#{ticket.number}``." msgstr "" -#: ../settings/branding.rst:38 -msgid "search indexing (and thus reporting)" +#: ../misc/variables.rst:51 +msgid "" +"Now, in some situations it's possible that you'll need to use a third part. " +"The best example for such a situation would be a ``select`` or ``tree-" +"select`` field which will by default return the key value, not it's display " +"name. For this, just extend your variable with ``.value``. This will result " +"in ``#{ticket.select.value}``." msgstr "" -#: ../settings/branding.rst:40 -msgid "calendar subscriptions" +#: ../misc/variables.rst:60 +msgid "Using Translated Variables" msgstr "" -#: ../settings/branding.rst:41 -msgid "browser printing" +#: ../misc/variables.rst:62 +msgid "" +"If you want to use a translated variable in triggers or schedulers, you can " +"extend the placeholder like this: ``#{t(ticket.state.name)}``. The ``t`` " +"tells Zammad to search for fitting translated strings. The used output " +"language is based on the system language of Zammad which you can set in the " +"admin panel under :doc:`/settings/branding` or based on the selected locale " +"in the trigger/scheduler edit dialog." msgstr "" -#: ../settings/branding.rst:43 +#: ../misc/variables.rst:69 msgid "" -"Please note that some of above are fallbacks in case Zammad could not detect " -"the agents timezone correctly." +"A possible use-case: you want to send your customers updates on tickets via " +"trigger or scheduler which should include the state of the ticket. Using the " +"default ``#{ticket.state.name}`` (without the translation flag ``t()``) " +"would lead to the output of the original (english) name of the state." msgstr "" -#: ../settings/branding.rst:77 -msgid "Pretty Date" +#: ../misc/variables.rst:75 +msgid "Date and Time Formatting" msgstr "" -#: ../settings/branding.rst:47 +#: ../misc/variables.rst:77 msgid "" -"This setting allows you to define how Zammad should display time stamps " -"within the interface to all users." +"The system (trigger/scheduler selected) locale and timezone predefines a " +"default format of date and timestamp. This format is customizable by using " +"the ``dt()`` method." msgstr "" -#: ../settings/branding.rst:50 -msgid "" -"This does not have any effect on how Zammad returns e.g. time values via " -"variables." +#: ../misc/variables.rst:79 +msgid "The method arguments are as follows:" msgstr "" -#: ../settings/branding.rst:77 -msgid "Choose in between the following options:" +#: ../misc/variables.rst:81 +msgid "The date or timestamp variable you want to format." msgstr "" -#: ../settings/branding.rst:64 -msgid "relative" +#: ../misc/variables.rst:82 +msgid "The output format string." msgstr "" -#: ../settings/branding.rst:55 +#: ../misc/variables.rst:83 +msgid "The timezone to apply (optional)." +msgstr "" + +#: ../misc/variables.rst:85 +#: ../system/objects/external-data-source-example.rst:23 +msgid "**Example:**" +msgstr "" + +#: ../misc/variables.rst:86 msgid "" -"This timestamp shows a relative time span until it switches to a date. Over " -"time, it will change as follows:" +"``#{dt(ticket.updated_at, \"%A %Y-%m-%d %H:%M in the office\", \"Europe/" +"Berlin\")}``" msgstr "" -#: ../settings/branding.rst:58 -msgid "just now" +#: ../misc/variables.rst:87 +msgid "Monday, 2024-03-18 15:31 in the office" msgstr "" -#: ../settings/branding.rst:59 -msgid "5 minutes ago" +#: ../misc/variables.rst:89 +msgid "" +"If you want to use our example, make sure to paste the string above without " +"formatting (``CTRL+Shift+v``), otherwise it won't work." msgstr "" -#: ../settings/branding.rst:60 -msgid "3 days 1 hour ago" +#: ../misc/variables.rst:93 +msgid "The following table lists available format directives:" msgstr "" -#: ../settings/branding.rst:61 -msgid "``03/04/2022``" +#: ../misc/variables.rst:99 +msgid "Parameter" msgstr "" -#: ../settings/branding.rst:63 -msgid "Hovering the timestamp helps, you'll always get a clean timestamp then." +#: ../misc/variables.rst:102 +msgid "``%Y``" msgstr "" -#: ../settings/branding.rst:71 -msgid "absolute" +#: ../misc/variables.rst:103 +msgid "Year with 4 digits" msgstr "" -#: ../settings/branding.rst:67 -msgid "" -"This timestamp always includes the week day. For one week after creation, " -"the timestamp will not contain the date itself: Thursday 18:35." +#: ../misc/variables.rst:104 +msgid "Use ``%y`` for year with 2 digits" msgstr "" -#: ../settings/branding.rst:71 -msgid "After a week it will switch to: ``Friday 4. Mar 16:00``." +#: ../misc/variables.rst:105 +msgid "``%m``" msgstr "" -#: ../settings/branding.rst:76 -msgid "timestamp" +#: ../misc/variables.rst:106 +msgid "Month of year (as number with zero-padding)" msgstr "" -#: ../settings/branding.rst:74 -msgid "" -"This will cause Zammad to show a complete timestamp according to your locale " -"defaults. For English this could be e.g. ``2022/12/03 2:40 pm`` or for " -"German e.g. ``12.03.2022 14:40``." +#: ../misc/variables.rst:107 +msgid "Use ``%-m`` for month without zero-padding" msgstr "" -#: ../settings/branding.rst:78 -msgid "Default setting: ``relative``." +#: ../misc/variables.rst:108 +msgid "``%d``" msgstr "" -#: ../settings/security.rst:2 -msgid "Security" +#: ../misc/variables.rst:109 +msgid "Day of month (as number with zero-padding)" msgstr "" -#: ../settings/security.rst:4 -msgid "" -"For your overview we split each tab within security settings into its own " -"page:" +#: ../misc/variables.rst:110 +msgid "Use ``%e`` for day without zero-padding" msgstr "" -#: ../settings/security/base.rst:2 ../settings/system/base.rst:2 -#: ../settings/ticket.rst:8 -msgid "Base" +#: ../misc/variables.rst:111 +msgid "``%H``" msgstr "" -#: ../settings/security/base.rst:5 -msgid "New User Accounts" +#: ../misc/variables.rst:112 +msgid "Hour of day in 24h notation with zero-padding" msgstr "" -#: ../settings/security/base.rst:9 -msgid "" -"Activates the `register as a new customer` function on the login page. If " -"set to ``no`` only administrators or agents can create new accounts manually." +#: ../misc/variables.rst:113 +msgid "Use ``%k`` for hour without zero-padding" msgstr "" -#: ../settings/security/base.rst:13 ../settings/security/base.rst:38 -#: ../settings/security/base.rst:66 -msgid "Default setting: ``yes``" +#: ../misc/variables.rst:114 +msgid "``%I``" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing activated \"New User Accounts\" setting" +#: ../misc/variables.rst:115 +msgid "Hour of day in 12h notation with zero-padding" msgstr "" -#: ../settings/security/base.rst:22 +#: ../misc/variables.rst:116 msgid "" -"Deactivation of above function **does not** deactivate automatic account " -"creation! This means: If a user writes e.g. an email to Zammad and has no " -"account yet, Zammad will automatically create the account. User accounts are " -"a direct dependency of tickets and thus technically mandatory." +"Use ``%l`` for hour without zero-padding and ``%p`` / ``%P`` for meridian " +"indicator" msgstr "" -#: ../settings/security/base.rst:29 -msgid "Lost Password" +#: ../misc/variables.rst:117 +msgid "``%M``" msgstr "" -#: ../settings/security/base.rst:33 -msgid "" -"Activates the `lost password` function on the login page. If set to ``no`` " -"only administrators may change the user's password - users may update their " -"own password if they're still logged in and they have the required :doc:" -"`permission `." +#: ../misc/variables.rst:118 +msgid "Minute of hour" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing activated \"Lost Password\" setting" +#: ../misc/variables.rst:120 +msgid "``%S``" msgstr "" -#: ../settings/security/base.rst:49 -msgid "" -"With third party authentications - but especially LDAP - you may want to " -"disable this function. Zammad **will not** change third party login " -"passwords and instead set or change the local password!" +#: ../misc/variables.rst:121 +msgid "Second of Minute" msgstr "" -#: ../settings/security/base.rst:56 -msgid "Password Login" +#: ../misc/variables.rst:123 +msgid "``%A``" msgstr "" -#: ../settings/security/base.rst:60 -msgid "" -"Activates the username & password login by default and if no third-party " -"login is activated. Disabling password login on the Zammad login page only " -"takes effect if you enable any :doc:`third-party`." +#: ../misc/variables.rst:124 +msgid "Weekday name" msgstr "" -#: ../settings/security/base.rst:64 -msgid "See :doc:`third-party` for supported third-party logins." +#: ../misc/variables.rst:125 +msgid "Use ``%a`` for abbreviated name or ``%^A`` for uppercase name" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing de-activated \"Password Login\" setting" +#: ../misc/variables.rst:126 +msgid "``%B``" msgstr "" -#: ../settings/security/base.rst:77 -msgid "" -"To help administrators to overcome \"login issues\", Zammad automatically " -"offers a password request for administrator users. This allows you to adjust " -"Third-Party applications even if the login does no longer work!" +#: ../misc/variables.rst:127 +msgid "Month name" msgstr "" -#: ../settings/security/base.rst:84 -msgid "Session Timeout" +#: ../misc/variables.rst:128 +msgid "Use ``%b`` for abbreviated name" msgstr "" -#: ../settings/security/base.rst:86 -msgid "" -"All settings below by default are set to ``4 weeks``. Session Timeout " -"defines the life time of a users session. As soon as it's reached, Zammad " -"will automatically log off the session in question." +#: ../misc/variables.rst:129 +msgid "``%U``" msgstr "" -#: ../settings/security/base.rst:91 -msgid "" -"Zammad takes the highest value set assigned for the user based on the " -"permissions." +#: ../misc/variables.rst:130 +msgid "Week number of current year" msgstr "" -#: ../settings/security/base.rst:94 -msgid "``admin``" +#: ../misc/variables.rst:131 +msgid "Use ``%W`` for a different calculation method" msgstr "" -#: ../settings/security/base.rst:96 -msgid "``ticket.customer``" +#: ../misc/variables.rst:134 +msgid "" +"We support the known format directives for the Ruby built-in method " +"``strftime`` of the ``DateTime`` class. For more information, see `here " +"`_." msgstr "" -#: ../settings/security/base.rst:97 -msgid "``default`` (fallback if user doesn't have above permissions set)" +#: ../misc/variables/article.rst:2 +msgid "Articles" msgstr "" -#: ../settings/security/base.rst:99 +#: ../misc/variables/article.rst:4 ../misc/variables/config.rst:4 +#: ../misc/variables/current-user.rst:4 ../misc/variables/ticket.rst:4 msgid "" -"All settings act independently from each other allowing you to disable the " -"timeouts for e.g. admins, but not agents." +"If you're missing variables or are not sure if something is not working as " +"expected, feel free to ask over at the `Community `_." msgstr "" -#: ../settings/security/base.rst:115 -#: ../system/integrations/checkmk/api-reference.rst:13 -msgid "Example" +#: ../misc/variables/article.rst:6 +msgid "" +"Below you can find all available ticket article-based variables within " +"Zammad. These can be called via triggers for example. If you're unsure if " +"Zammad does support variables at the point you're at, you can try to type " +"``::`` to check." msgstr "" -#: ../settings/security/base.rst:107 -msgid "Let's suppose you configured the following session timeouts" +#: ../misc/variables/article.rst:9 ../misc/variables/config.rst:9 +#: ../misc/variables/ticket.rst:9 +msgid "" +"The below list gives you an example what kind of data you can expect, it's " +"not intended to explain the data itself." msgstr "" -#: ../settings/security/base.rst:104 -msgid "default: 3 weeks" +#: ../misc/variables/article.rst:11 +msgid "Article Variables" msgstr "" -#: ../settings/security/base.rst:105 -msgid "admin: 2 weeks" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "name" msgstr "" -#: ../settings/security/base.rst:106 -msgid "ticket.agent: 4 weeks" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "variable" msgstr "" -#: ../settings/security/base.rst:107 -msgid "ticket.customer: 1 week" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "example" msgstr "" -#: ../settings/security/base.rst:115 -msgid "This results in the following situations" +#: ../misc/variables/article.rst:1 +msgid "Article > Cc" msgstr "" -#: ../settings/security/base.rst:110 -msgid "a user with ``admin`` permission will have a timeout of 2 weeks" +#: ../misc/variables/article.rst:1 +msgid "``#{article.cc}``" msgstr "" -#: ../settings/security/base.rst:111 -msgid "" -"a user with ``admin`` and ``ticket.agent`` permissions will have a timeout " -"of 2 weeks" +#: ../misc/variables/article.rst:1 +msgid "``jdoe@example.com, company@example.com``" msgstr "" -#: ../settings/security/base.rst:113 -msgid "" -"a user with ``ticket.customer`` permission will have a timeout of 1 week" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Address" msgstr "" -#: ../settings/security/base.rst:115 -msgid "" -"a user with neither ``admin``, ``ticket.agent`` nor ``ticket.customer`` " -"permissions will have a timeout of 3 weeks" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.address}``" msgstr "" -#: ../settings/security/password.rst:4 -msgid "" -"This section allows you to define password requirements for the local user " -"accounts." +#: ../misc/variables/article.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:9 -msgid "" -"Zammad does **not** allow you to change your LDAP password, instead, it will " -"set a password in its local database which might confuse your users. This " -"might be addressed in the future by `#1169 `_." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Department" msgstr "" -#: ../settings/security/password.rst:14 -msgid "**Exception for admins**" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.department}``" msgstr "" -#: ../settings/security/password.rst:16 -msgid "" -"Please note that below password policies *do not* affect administrators " -"setting passwords on user accounts. While this seems strange and not safe we " -"believe that an administrator knowing an user's password is insecure as well." +#: ../misc/variables/article.rst:1 +msgid "``Sales`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:21 -msgid "The suggested workflow is either:" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Email" msgstr "" -#: ../settings/security/password.rst:23 -msgid "" -"to use third party logins to not require local passwords at all **- or -**" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.email}``" msgstr "" -#: ../settings/security/password.rst:25 -msgid "to require your *user to reset the password* upon first login." +#: ../misc/variables/article.rst:1 +msgid "``jdoe@example.com``" msgstr "" -#: ../settings/security/password.rst:27 -msgid "" -"This way administrators are not required to set a user's password at all!" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Fax" msgstr "" -#: ../settings/security/password.rst:31 -msgid "Maximum Failed Logins" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.fax}``" msgstr "" -#: ../settings/security/password.rst:33 -msgid "" -"You can choose a value between ``4`` and ``20``. This defines how often a " -"login to a user account may fail until Zammad will lock it. Your users can " -"always use the \"forgot password\" function to change their password and " -"unlock their account." -msgstr "" - -#: ../settings/security/password.rst:38 -msgid "The default value is ``10``." +#: ../misc/variables/article.rst:1 +msgid "``+4930123456789`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:42 -msgid "Beside changing the user's password, you can also unlock accounts via" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Firstname" msgstr "" -#: ../settings/security/password.rst:44 -msgid ":ref:`user management list `" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.firstname}``" msgstr "" -#: ../settings/security/password.rst:45 -msgid ":docs:`console `" +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Joe`` or empty if not set" msgstr "" -#: ../settings/security/password.rst:46 -msgid ":docs:`API `" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Lastname" msgstr "" -#: ../settings/security/password.rst:50 -msgid "Failed logins via LDAP no longer lock accounts." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.lastname}``" msgstr "" -#: ../settings/security/password.rst:53 -msgid "2 Lower Case And 2 Upper Case Characters" +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +#: ../misc/variables/ticket.rst:1 +msgid "``Doe`` or empty if not set" msgstr "" -#: ../settings/security/password.rst:55 -msgid "" -"You can add complexity to passwords by enforcing at least 2 upper and lower " -"case characters." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Login" msgstr "" -#: ../settings/security/password.rst:58 ../settings/security/password.rst:83 -msgid "The default value is ``no``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.login}``" msgstr "" -#: ../settings/security/password.rst:62 -msgid "Minimum Length" +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +#: ../misc/variables/ticket.rst:1 +msgid "``jdoe``" msgstr "" -#: ../settings/security/password.rst:64 -msgid "" -"This defines the minimum password length required for users to provide (from " -"``4`` to ``20``)." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Mobile" msgstr "" -#: ../settings/security/password.rst:67 -msgid "The default value is ``6``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.mobile}``" msgstr "" -#: ../settings/security/password.rst:71 -msgid "Digit Required" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Note" msgstr "" -#: ../settings/security/password.rst:73 -msgid "This enforces your users to use at least one digit within the password." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.note}``" msgstr "" -#: ../settings/security/password.rst:75 -msgid "The default value is ``yes``." +#: ../misc/variables/article.rst:1 +msgid "``Some note about user`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:78 -msgid "Special Character Required" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Phone" msgstr "" -#: ../settings/security/password.rst:80 -msgid "" -"This setting allows you to improve your password quality even more by " -"enforcing the password to contain at least one special character." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.phone}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:2 -msgid "SSL Certificates" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > VIP" msgstr "" -#: ../settings/security/ssl-certificates.rst:7 -msgid "" -"Zammad offers the possibility to upload custom certificates and custom " -"Certificate Authority (CA) certificates. This can be useful if you want to " -"connect Zammad the secure way to other systems which are using custom " -"certificates." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.vip}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:12 -msgid "" -"An example usecase might be: You have an internal LDAP server that is not " -"accessible from the internet, and you want a SSL-encrypted connection, using " -"a custom certificate." +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +msgid "``true`` or ``false``" msgstr "" -#: ../settings/security/ssl-certificates.rst:19 -msgid "" -"You should have an existing custom certificate file and/or a custom CA " -"certificate file, which you want to add to Zammad. As filetype ``.crt`` is " -"supported and the certificate format has to be PEM (Base64 ASCII)." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Web" msgstr "" -#: ../settings/security/ssl-certificates.rst:25 -msgid "" -"When you import a custom CA certificate, all certificates generated with " -"this are trusted. This can be useful if you have more than one system/" -"certificate you want to connect to and the certificates are issued from the " -"same custom CA." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.web}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:31 -msgid "Add a Certificate" +#: ../misc/variables/article.rst:1 +msgid "``https://zammad.com`` or empty if not set in user object" msgstr "" -#: ../settings/security/ssl-certificates.rst:33 -msgid "" -"To add a custom certificate or a custom CA certificate, head over to the " -"Admin panel > Settings > Security > SSL Certificates. Here you can find a " -"\"Add SSL Certificate\" button. In the dialog you can either select a " -"certificate file or paste the content of the certificate:" +#: ../misc/variables/article.rst:1 +msgid "Article > Created" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate adding dialog" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_at}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:43 -msgid "" -"After selecting a file or pasting the content of the certificate, click on " -"the \"Add\" button to finally upload it to Zammad. Then, the certificates " -"are immediately effective, no restart or similar required." +#: ../misc/variables/article.rst:1 +msgid "``2019-10-08 15:24:47 UTC``" msgstr "" -#: ../settings/security/ssl-certificates.rst:49 -msgid "" -"Please note that only single certificate files are supported. That means if " -"you want to import a certificate / CA certificate, it must contain **only " -"one** certificate." +#: ../misc/variables/article.rst:1 +msgid "Article > From" msgstr "" -#: ../settings/security/ssl-certificates.rst:54 -msgid "Certificate Overview" +#: ../misc/variables/article.rst:1 +msgid "``#{article.from}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:56 +#: ../misc/variables/article.rst:1 msgid "" -"After you added a certificate, you can see a table with information for each " -"added certificate:" +"``Joe Doe `` may differ, depends on ``FROM`` of send mail" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing table of added certificates" +#: ../misc/variables/article.rst:1 +msgid "Article > Sender > Name" msgstr "" -#: ../settings/security/ssl-certificates.rst:64 -msgid "" -"Here you can download the certificate or delete it, if you don't need it " -"anymore." +#: ../misc/variables/article.rst:1 +msgid "``#{article.sender.name}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:68 -msgid "Deleting Certificates" +#: ../misc/variables/article.rst:1 +msgid "``Customer``, ``Agent`` or ``System``" msgstr "" -#: ../settings/security/ssl-certificates.rst:70 -msgid "" -"If you want to delete a specific certificate, you can do it by clicking on " -"the menu in the actions column and selecting delete:" +#: ../misc/variables/article.rst:1 +msgid "Article > Subject" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate deletion button" +#: ../misc/variables/article.rst:1 +msgid "``#{article.subject}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:79 -msgid "Downloading Certificates" +#: ../misc/variables/article.rst:1 +msgid "``My amazing subject``" msgstr "" -#: ../settings/security/ssl-certificates.rst:81 -msgid "" -"If you want to download your certificates, you can do this as well via " -"corresponding action buttons." +#: ../misc/variables/article.rst:1 +msgid "Article > Text" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate download button" +#: ../misc/variables/article.rst:1 +msgid "``#{article.body}``" msgstr "" -#: ../settings/security/third-party.rst:13 -msgid "Login Providers" +#: ../misc/variables/article.rst:1 +msgid "``Test`` without formatting (plain)" msgstr "" -#: ../settings/security/third-party.rst:2 -msgid "Third-Party Applications" +#: ../misc/variables/article.rst:1 +msgid "Article > TicketID" msgstr "" -#: ../settings/security/third-party.rst:4 -msgid "" -"Third party authentication is a great way to help your users to login to " -"Zammad more easily. If the account is yet unknown, Zammad will create a new " -"user automatically, without the user needed to interact (e.g. type in his " -"name). Another big advantage of this feature is that your user doesn't need " -"to remember another password." +#: ../misc/variables/article.rst:1 +msgid "``#{article.ticket_id}``" msgstr "" -#: ../settings/security/third-party.rst:10 -msgid "" -"You can deactivate logging in via :ref:`security_password_login` if any of " -"the mentioned authentication providers are enabled in your instance." +#: ../misc/variables/article.rst:1 +msgid "``1`` (not ticket number)" msgstr "" -#: ../settings/security/third-party.rst:27 -msgid "" -"We're currently missing documentation for the following login providers:" +#: ../misc/variables/article.rst:1 +msgid "Article > To" msgstr "" -#: ../settings/security/third-party.rst:29 -msgid "LinkedIn" +#: ../misc/variables/article.rst:1 +msgid "``#{article.to}``" msgstr "" -#: ../settings/security/third-party.rst:30 -msgid "Weibo" +#: ../misc/variables/article.rst:1 +msgid "``helpdesk@example.com``" msgstr "" -#: ../settings/security/third-party.rst:35 -msgid "Automatic Account Link on Initial Logon" +#: ../misc/variables/article.rst:1 +msgid "Article > Type > Name" msgstr "" -#: ../settings/security/third-party.rst:37 -msgid "" -"In general there's two possible options for Zammad on how to deal with " -"already known users as they try to authenticate against a third-party " -"application. By default, Zammad will not automatically link \"unknown\" " -"authentication providers to existing accounts." +#: ../misc/variables/article.rst:1 +msgid "``#{article.type.name}``" msgstr "" -#: ../settings/security/third-party.rst:42 +#: ../misc/variables/article.rst:1 msgid "" -"This means that the user has to manually link authentication providers to " -"their accounts (for more about this :user-docs:`consult the user " -"documentation `)." +"``email`` (`list of article types `_)" msgstr "" -#: ../settings/security/third-party.rst:46 -msgid "" -"Sometimes this doesn't come in handy as this also means you'll receive error " -"messages about \"email address being in use already\" for (yet) unknown " -"third-party authentication methods." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Address" msgstr "" -#: ../settings/security/third-party.rst:50 -msgid "" -"If you want to allow your users to always be able to log in, no matter what, " -"you may want to enable ``Automatic account link on initial logon``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.address}``" msgstr "" -#: ../settings/security/third-party.rst:None -msgid "" -"Screenshot highlighting the \"Automatic account link on initial logon\"\n" -"setting" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Department" msgstr "" -#: ../settings/security/third-party.rst:60 -msgid "Automatic Account Linking Notification" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.department}``" msgstr "" -#: ../settings/security/third-party.rst:64 -msgid "" -"To improve security and your users awareness, you can enable Zammad to " -"notify your users when a new third-party application has been linked to " -"their account." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Email" msgstr "" -#: ../settings/security/third-party.rst:68 -msgid "" -"This notification is sent out once per third-party application. Zammad does " -"also mention the method used, e.g.: ``Microsoft``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.email}``" msgstr "" -#: ../settings/security/third-party.rst:71 -msgid "By default this setting is not active (set to ``no``)." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Fax" msgstr "" -#: ../settings/security/third-party.rst:0 -msgid "" -"Screenshot showing sample notification mail after initial\n" -"third-party linking" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.fax}``" msgstr "" -#: ../settings/security/third-party.rst:85 -msgid "" -"This notification is only sent if the account in question already exists. If " -"the login via the third-party also creates the missing account, the " -"notification will be skipped." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Firstname" msgstr "" -#: ../settings/security/third-party.rst:89 -msgid "This means it only affects:" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.firstname}``" msgstr "" -#: ../settings/security/third-party.rst:91 -msgid "manual account linking within the third-party page of the users profile" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Lastname" msgstr "" -#: ../settings/security/third-party.rst:92 -msgid "" -"logging into an existing local account by utilizing the *automatic account " -"link on initial logon* functionality" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.lastname}``" msgstr "" -#: ../settings/security/third-party.rst:None -msgid "" -"Screenshot showing the \"automatic account linking notification\"\n" -"setting" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Login" msgstr "" -#: ../settings/security/third-party.rst:100 -msgid "No User Creation on Logon" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.login}``" msgstr "" -#: ../settings/security/third-party.rst:102 -msgid "" -"By default, Zammad will create a new user account if the user logs in via a " -"third-party application and the account doesn't exist yet." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Mobile" msgstr "" -#: ../settings/security/third-party.rst:105 -msgid "" -"If you want to prevent Zammad from creating new accounts on logon, you can " -"disable this feature by setting ``No user creation on logon`` to ``yes``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.mobile}``" msgstr "" -#: ../settings/security/third-party.rst:None -msgid "Screenshot showing the \"no user creation on logon\" setting" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Note" msgstr "" -#: ../settings/security/third-party/facebook.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via Facebook To do " -"so, you need to follow these steps:" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.note}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:9 -msgid "Register Facebook App" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Phone" msgstr "" -#: ../settings/security/third-party/facebook.rst:11 -msgid "" -"Visit [https://developers.facebook.com/apps/] and click on \"Add a new App\"" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.phone}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "initial page" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > VIP" msgstr "" -#: ../settings/security/third-party/facebook.rst:17 -msgid "After that enter the app settings" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.vip}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "Create App" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Web" msgstr "" -#: ../settings/security/third-party/facebook.rst:22 -msgid "Navigate to \"Settings\" and fill in this infromation" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.web}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "App Settings" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated" msgstr "" -#: ../settings/security/third-party/facebook.rst:27 -msgid "Navigate to app review and Check \"Make [appname] public?\"" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_at}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "App Review" +#: ../misc/variables/article.rst:1 +msgid "Article > Visibility" msgstr "" -#: ../settings/security/third-party/facebook.rst:35 -msgid "Configure Zammad as Facebook App" +#: ../misc/variables/article.rst:1 +msgid "``#{article.internal}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:37 -msgid "" -"Navigate to \"Admin -> Security -> Third Party Applications\" and enter the " -"App ID and the App Secret. You can find this Key in the Dashbard of your " -"Facebok app." +#: ../misc/variables/article.rst:1 +msgid "``false`` or ``true`` (false if not internal)" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "Zammad Configuration" +#: ../misc/variables/article.rst:1 +msgid "Article Text as HTML (not referenced)" msgstr "" -#: ../settings/security/third-party/facebook.rst:44 -#: ../settings/security/third-party/github.rst:43 -#: ../settings/security/third-party/gitlab.rst:46 -msgid "" -"Now you can link accounts via \"Avatar -> Profile -> Link Accounts\" or " -"login via Zammad login page." +#: ../misc/variables/article.rst:1 +msgid "``#{article.body_as_html}``" msgstr "" -#: ../settings/security/third-party/github.rst:2 -#: ../system/integrations/github.rst:2 -msgid "GitHub" +#: ../misc/variables/article.rst:1 +msgid "``Test`` with formatting" msgstr "" -#: ../settings/security/third-party/github.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via GitHub. To " -"activate the quick login you need to enable OAuth for GitHub." +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "Ticket > Article#" msgstr "" -#: ../settings/security/third-party/github.rst:8 -msgid "Register GitHub App" +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "``#{ticket.article_count}``" msgstr "" -#: ../settings/security/third-party/github.rst:10 -msgid "" -"Visit https://www.github.com/settings/applications/new and enter the app " -"settings. As callback URL enter \"https://zammad_host/auth/github/callback\" " -"where zammad_host has to be replaced with your Zammad FQDN" +#: ../misc/variables/article.rst:1 +msgid "``1`` number of ticket articles" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "Register OAuth app on www.github.com" +#: ../misc/variables/config.rst:2 +msgid "Config" msgstr "" -#: ../settings/security/third-party/github.rst:19 -msgid "Configure Zammad as GitHub App" +#: ../misc/variables/config.rst:6 +msgid "" +"Below you'll find config related variables. These hold useful configuration " +"information that you can use within e.g. triggers to show necessary " +"information to your customer." msgstr "" -#: ../settings/security/third-party/github.rst:21 -msgid "" -"Enter the \"APP ID\" and the \"APP SECRET\" from the GitHub OAUTH " -"Applications Dashboard" +#: ../misc/variables/config.rst:11 +msgid "Config Variables" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub config in Zammad admin interface" +#: ../misc/variables/config.rst:1 +msgid "Config > Fully Qualified Domain Name" msgstr "" -#: ../settings/security/third-party/github.rst:28 -msgid "" -"After you configured the GitHub credentials and activated the login method, " -"you should see a new icon on the login page." +#: ../misc/variables/config.rst:1 +msgid "``#{config.fqdn}``" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub logo on login page" +#: ../misc/variables/config.rst:1 +msgid "``zammad.example.com``" msgstr "" -#: ../settings/security/third-party/github.rst:34 -msgid "" -"If you click on the icon you will be redirected to GitHub and see something " -"similar to this:" +#: ../misc/variables/config.rst:1 +msgid "Config > HTTP type" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub oauth page" +#: ../misc/variables/config.rst:1 +msgid "``#{config.http_type}``" msgstr "" -#: ../settings/security/third-party/github.rst:40 -#: ../settings/security/third-party/gitlab.rst:42 -msgid "" -"When you grant the access you will be redirected to your Zammad instance and " -"logged in as a customer." +#: ../misc/variables/config.rst:1 +msgid "``https`` or ``http``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:2 -msgid "Gitlab" +#: ../misc/variables/config.rst:1 +msgid "Config > Organization" msgstr "" -#: ../settings/security/third-party/gitlab.rst:4 +#: ../misc/variables/config.rst:1 +msgid "``#{config.organization}``" +msgstr "" + +#: ../misc/variables/config.rst:1 msgid "" -"It is possible to create a quick login for your helpdesk via Gitlab. To " -"activate the quick login you need to enable OAuth for Gitlab." +"``Zammad GmbH`` value set in `Branding `_" msgstr "" -#: ../settings/security/third-party/gitlab.rst:8 -msgid "Register Gitlab App" +#: ../misc/variables/config.rst:1 +msgid "Config > Product Name" msgstr "" -#: ../settings/security/third-party/gitlab.rst:10 -msgid "To register an app in Gitlab open your profile and select applications." +#: ../misc/variables/config.rst:1 +msgid "``#{config.product_name}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:12 +#: ../misc/variables/config.rst:1 msgid "" -"As callback URL enter \"https://zammad-fqdn/auth/gitlab/callback\" where " -"zammad-fqdn has to be replaced with your Zammad FQDN" +"``Helpdesk`` value set in `Branding `_" msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Register OAuth app on gitlab instance" +#: ../misc/variables/config.rst:1 +msgid "Config > SystemID" msgstr "" -#: ../settings/security/third-party/gitlab.rst:18 -msgid "Just select *read_user* under scopes as in the screenshot and save it." +#: ../misc/variables/config.rst:1 +msgid "``#{config.system_id}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:21 -msgid "Configure Zammad as Gitlab App" +#: ../misc/variables/config.rst:1 +msgid "``31`` (value between 1 and 99)" msgstr "" -#: ../settings/security/third-party/gitlab.rst:23 -msgid "" -"Enter the \"APP ID\" and the \"APP SECRET\" from the Gitlab OAUTH " -"Applications Dashboard and your Gitlab-URL in the \"SITE\" field." +#: ../misc/variables/config.rst:1 +msgid "Config > Ticket Hook" msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab config in Zammad admin interface" +#: ../misc/variables/config.rst:1 +msgid "``#{config.ticket_hook}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:30 -msgid "" -"After you configured the Gitlab credentials and activated the login method, " -"you should see a new icon on the login page." +#: ../misc/variables/config.rst:1 +msgid "``Ticket#``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab logo on login page" +#: ../misc/variables/current-user.rst:2 +msgid "Current User" msgstr "" -#: ../settings/security/third-party/gitlab.rst:36 +#: ../misc/variables/current-user.rst:6 msgid "" -"If you click on the icon you will be redirected to Gitlab and see something " -"similar to this:" +"Current user variables always return values of the current user that caused " +"e.g. a trigger to run." msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab oauth page" +#: ../misc/variables/current-user.rst:8 +msgid "" +"Due to the above fact, these variables are often not (yet) set or available " +"for usage." msgstr "" -#: ../settings/security/third-party/google.rst:4 +#: ../misc/variables/current-user.rst:10 msgid "" -"With some easy and fast steps, you can enable Zammad to authenticate your " -"users via Google." +"In situations where e.g. schedulers or triggers run, this most likely is " +"nothing you want to use." msgstr "" -#: ../settings/security/third-party/google.rst:8 -msgid "Register a Google App" +#: ../misc/variables/current-user.rst:13 +msgid "Current User Variables" msgstr "" -#: ../settings/security/third-party/google.rst:10 -msgid "" -"First of all, we need to create a new project - you can skip this step if " -"you already have one." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Address" msgstr "" -#: ../settings/security/third-party/google.rst:15 -msgid "" -"Use this link to create a new project: https://console.cloud.google.com/" -"projectcreate" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.address}``" msgstr "" -#: ../settings/security/third-party/google.rst:18 -msgid "" -"Now expand the menu, expand \"APIs & Services\" and select \"Credentials\". " -"Go to the tab \"OAuth consent screen\" first and ensure to fill in the " -"requested information - without doing so you can't create credentials!" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set" msgstr "" -#: ../settings/security/third-party/google.rst:None -msgid "Creating a consent screen" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Avatar" msgstr "" -#: ../settings/security/third-party/google.rst:25 -msgid "" -"After filling in and saving the consent screen information, you can go to " -"the \"Credentials\" tab and create new \"OAuth client ID\"-Credentials." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/google.rst:28 -msgid "" -"Fill in the necessary information as follows and replace ``zammad_host`` " -"with your FQDN:" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "avatar picture with width and height in pixel (e.g. 60,60)" msgstr "" -#: ../settings/security/third-party/google.rst:31 -msgid "**Application type** ``[x] Web application``" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created at" msgstr "" -#: ../settings/security/third-party/google.rst:34 -msgid "**Authorized JavaScript origins** ``https://zammad_host/``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_at}``" msgstr "" -#: ../settings/security/third-party/google.rst:37 -msgid "" -"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" -"callback``" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC``" msgstr "" -#: ../settings/security/third-party/google.rst:None -msgid "Adding a new OAuth client ID" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Address" msgstr "" -#: ../settings/security/third-party/google.rst:43 -msgid "" -"After creating the credentials, go to your Zammad installation and navigate " -"to \"Admin > Security > Third Party Applications\" > Google. Enter your " -"Client ID and Client secret here." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.address}``" msgstr "" -#: ../settings/security/third-party/google.rst:None -msgid "Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Avatar" msgstr "" -#: ../settings/security/third-party/google.rst:50 -msgid "After submitting, the login via Google can be used." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:2 -msgid "Microsoft" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Department" msgstr "" -#: ../settings/security/third-party/microsoft.rst:4 -msgid "" -"Zammad's Microsoft connection allows your users with Microsoft accounts to " -"login. This works for Azure users as well and can be an alternative to :doc:" -"`/system/integrations/ldap/index`." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.department}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:10 -msgid "" -"This documentation part does not cover our :doc:`📧 Microsoft 365 email " -"channel `." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Sales`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screenshot showing Microsoft login button on Zammad login screen." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Email" msgstr "" -#: ../settings/security/third-party/microsoft.rst:30 -#: ../settings/security/third-party/microsoft.rst:53 -msgid "Supported account types:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.email}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:22 -msgid "" -"Please note that Zammad only supports these account types (App dependent):" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``jdoe@customer.tld``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:35 -msgid "Avatars of signing in users:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Fax" msgstr "" -#: ../settings/security/third-party/microsoft.rst:33 -msgid "" -"Zammad currently ignores user avatars. If the user is registered with e.g. " -"Gravatar, Zammad will fetch the avatar from there if enabled. See :doc:" -"`Zammad Image Service ` for more." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.fax}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:38 -msgid "Step 1 - Register a Microsoft App for Zammad" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``004930123464789`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:40 -msgid "" -"Login to the `Microsoft Azure Portal `_ and " -"navigate to App registrations to create a new app. Provide the requested " -"information as follows and register your app." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Firstname" msgstr "" -#: ../settings/security/third-party/microsoft.rst:46 -msgid "Name:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.firstname}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:45 -msgid "" -"Any meaningful name fitting, this name will be displayed to users trying to " -"authenticate with this app." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``John`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:49 -msgid "Choose one of the above mentioned account types (see Limitations)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Lastname" msgstr "" -#: ../settings/security/third-party/microsoft.rst:51 -msgid "" -"The correct account type depends on your use case. If you want to use the " -"authentication internal only, choose the first option. If you're unsure, use " -"the \"Help me choose...\" link." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.lastname}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:58 -msgid "Redirect URI (optional):" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Login" msgstr "" -#: ../settings/security/third-party/microsoft.rst:56 -msgid "" -"Select web and provide your callback URL. The callback URL looks like this: " -"``https://zammad.domain.tld/auth/microsoft_office365/callback``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.login}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to register a Microsoft app" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Mobile" msgstr "" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "Within **API permissions** add the following permissions:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.mobile}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:69 -msgid "``User.Read``" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``0049176123456789`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "Contacts" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Note" msgstr "" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "``Contacts.Read``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.note}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:73 -msgid "" -"You can find these permissions within *Microsoft Graph → Delegated " -"permissions*." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Some note to this user`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to add required API permissions" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Phone" msgstr "" -#: ../settings/security/third-party/microsoft.rst:80 -msgid "" -"Within **Certificates & secrets** create a new client secret. Note down the " -"returned secret **value** for later. **Do not** use the secret ID!" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.phone}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to create a new app secret" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``004930123456789`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:88 -msgid "" -"From **Overview** copy your apps *Application (client) ID*. If you're using " -"a single tenant app, please also copy *Directory (tenant) ID*. You now have " -"all required information for Zammad." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > VIP" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to retreive application client and tenant IDs" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.vip}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:98 -msgid "Step 2 - Add App Credentials to Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Web" msgstr "" -#: ../settings/security/third-party/microsoft.rst:100 -msgid "" -"Navigate to Security > Third-party Applications (Tab) within Zammad's admin " -"settings. Scroll down to the section *Authentication via Microsoft* and fill " -"in the required information." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.web}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:105 -msgid "App ID:" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``https://zammad.org`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:105 -msgid "This is your *Application (client) ID*." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Department" msgstr "" -#: ../settings/security/third-party/microsoft.rst:108 -msgid "App secret:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.department}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:108 -msgid "This is your *client secret* (value)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Email" msgstr "" -#: ../settings/security/third-party/microsoft.rst:113 -msgid "App Tenant ID:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.email}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:111 -msgid "" -"**optional** only required for apps that use account type *Accounts in this " -"organizational directory only (Default Directory only - Single tenant).*" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Fax" msgstr "" -#: ../settings/security/third-party/microsoft.rst:115 -msgid "" -"Apply your settings by pressing submit and activate *Authentication via " -"Microsoft*." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.fax}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "" -"Screencast showing how to add app credentials and activating the\n" -"authentication method" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Firstname" msgstr "" -#: ../settings/security/third-party/saml.rst:2 -msgid "SAML" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.firstname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:4 -msgid "" -"Connect your SAML (Security Assertion Markup Language) identity provider as " -"a single sign-on (SSO) method." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Lastname" msgstr "" -#: ../settings/security/third-party/saml.rst:7 -msgid "" -"SAML is an open standard for SSO authentication (among other things). Sign-" -"ins are shared across multiple **service providers** and managed by a " -"central **identity provider** (IdP)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.lastname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:11 -msgid "" -"In this case, the service provider is Zammad, and the IdP is a software " -"service that you either host or subscribe to (*e.g.,* `Keycloak `_, `Redhat SSO Server `_, `ADFS `_, or `Okta `_)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Login" msgstr "" -#: ../settings/security/third-party/saml.rst:18 -msgid "" -"This guide assumes you are already using SAML within your organization (i." -"e., that your IdP is fully set up)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.login}``" msgstr "" -#: ../settings/security/third-party/saml.rst:21 -msgid "" -"Please note: Our instructions are based on connecting Zammad with Keycloak." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Mobile" msgstr "" -#: ../settings/security/third-party/saml.rst:25 -msgid "Step 1: Configure Your IdP" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.mobile}``" msgstr "" -#: ../settings/security/third-party/saml.rst:28 -msgid "Add Zammad as a Client/App" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Note" msgstr "" -#: ../settings/security/third-party/saml.rst:30 -msgid "" -"Import Zammad into your IdP using the XML configuration found at ``https://" -"your.zammad.domain/auth/saml/metadata``." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.note}``" msgstr "" -#: ../settings/security/third-party/saml.rst:33 -msgid "" -"If your IdP doesn't support XML import, you will have to configure Zammad as " -"a new client/app manually using the above XML metadata file for reference." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Domain based assignment" msgstr "" -#: ../settings/security/third-party/saml.rst:36 -msgid "For instance, when you see this tag:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.domain_assignment}``" msgstr "" -#: ../settings/security/third-party/saml.rst:42 -msgid "" -"Set the **Assertion Consumer Service Binding URL** (sometimes also listed as " -"**Valid Redirect URIs**) to ``http://your.zammad.domain/auth/saml/callback``." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Domain" msgstr "" -#: ../settings/security/third-party/saml.rst:47 -msgid "Set Up User Attribute Mapping" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.domain}``" msgstr "" -#: ../settings/security/third-party/saml.rst:49 -msgid "" -"Zammad requests the following user attributes (or “properties”) from the IdP:" +#: ../misc/variables/current-user.rst:1 +msgid "``zammad.com`` or empty if not set" msgstr "" -#: ../settings/security/third-party/saml.rst:51 -msgid "Email address (``email``)" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Name" msgstr "" -#: ../settings/security/third-party/saml.rst:52 -msgid "Full name (``name``)" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.name}``" msgstr "" -#: ../settings/security/third-party/saml.rst:53 -msgid "Given name (``first_name``)" +#: ../misc/variables/current-user.rst:1 +msgid "``Zammad GmbH``" msgstr "" -#: ../settings/security/third-party/saml.rst:54 -msgid "Family name (``last_name``)" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Note" msgstr "" -#: ../settings/security/third-party/saml.rst:56 -msgid "" -"You may need to set up “mappers” (or “mappings”) to tell your IdP how user " -"attributes in SAML correspond to those in Zammad. For a more detailed " -"breakdown, refer to the XML metadata file referenced in the previous section." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.note}``" msgstr "" -#: ../settings/security/third-party/saml.rst:62 -msgid "Per-IdP Instructions" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``A note to the organization of the user`` or empty if not set" msgstr "" -#: ../settings/security/third-party/saml.rst:102 -msgid "Keycloak" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Shared organization" msgstr "" -#: ../settings/security/third-party/saml.rst:65 -msgid "" -"**To add Zammad as a client,** save the XML configuration to disk (``https://" -"your.zammad.domain/auth/saml/metadata``) and use **Clients > Clients list > " -"Import client** in the Keycloak admin panel." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.shared}``" msgstr "" -#: ../settings/security/third-party/saml.rst:70 -msgid "" -"To help Zammad **match its own user accounts to Keycloak users**, create a " -"user attribute (or “property”) mapper. In **Clients list**, click on your " -"newly created Client ID, choose the tab **Client scopes** and click on the " -"link which refers to your Zammad instance. Choose **Add mapper > By " -"configuration > User Property** and create a mapper with the following " -"entries:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > VIP" msgstr "" -#: ../settings/security/third-party/saml.rst:78 -msgid "**Name**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.vip}``" msgstr "" -#: ../settings/security/third-party/saml.rst:80 -msgid "**Mapper Type**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Phone" msgstr "" -#: ../settings/security/third-party/saml.rst:81 -msgid "``User Property``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.phone}``" msgstr "" -#: ../settings/security/third-party/saml.rst:82 -msgid "**Property**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated at" msgstr "" -#: ../settings/security/third-party/saml.rst:83 -msgid "``emailAddress``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_at}``" msgstr "" -#: ../settings/security/third-party/saml.rst:84 -msgid "**SAML Attribute Name**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Address" msgstr "" -#: ../settings/security/third-party/saml.rst:86 -msgid "**SAML Attribute NameFormat**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.address}``" msgstr "" -#: ../settings/security/third-party/saml.rst:87 -msgid "``basic``" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Avatar" msgstr "" -#: ../settings/security/third-party/saml.rst:89 -msgid "" -"In the example above, we're telling Zammad that whenever it receives a SAML " -"login request, it should take the ``email`` property from Keycloak, look for " -"a Zammad user with the same ``email`` attribute, and create a new session " -"for that user." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/saml.rst:95 -msgid "" -"If your Keycloak users' email addresses are stored on another property (*e." -"g.,* ``username``), adjust accordingly." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Department" msgstr "" -#: ../settings/security/third-party/saml.rst:98 -msgid "" -"Back in **Settings**, enter the Client ID (``https://your.zammad.domain/auth/" -"saml/metadata``) in the field **Master SAML Processing URL**." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.department}``" msgstr "" -#: ../settings/security/third-party/saml.rst:101 -msgid "You also need to enable **Sign assertions**." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Email" msgstr "" -#: ../settings/security/third-party/saml.rst:105 -msgid "Step 2: Configure Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.email}``" msgstr "" -#: ../settings/security/third-party/saml.rst:107 -msgid "" -"Enable SAML and enter your IdP's details in the Admin Panel under **Settings " -"> Security > Third Party Applications > Authentication via SAML**:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Fax" msgstr "" -#: ../settings/security/third-party/saml.rst:None -msgid "Example configuration of SAML part 1" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.fax}``" msgstr "" -#: ../settings/security/third-party/saml.rst:119 -msgid "Display name" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Firstname" msgstr "" -#: ../settings/security/third-party/saml.rst:116 -msgid "" -"Allows you to define a custom button name for SAML. This helps your users to " -"understand better what the button on the login page does." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.firstname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:119 -msgid "Defaults to ``SAML``." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Lastname" msgstr "" -#: ../settings/security/third-party/saml.rst:123 -msgid "IDP SSO target URL" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.lastname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:122 -msgid "" -"This is the target URL Zammad shall redirect to when the user presses the " -"SAML button. For Keycloak, this needs to look like https://your.domain/" -"realms/your-realm/protocol/saml" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Login" msgstr "" -#: ../settings/security/third-party/saml.rst:127 -msgid "IDP single logout target URL" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.login}``" msgstr "" -#: ../settings/security/third-party/saml.rst:126 -msgid "" -"This is the URL to which the single logout request and response should be " -"sent." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Mobile" msgstr "" -#: ../settings/security/third-party/saml.rst:131 -msgid "IDP certificate" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.mobile}``" msgstr "" -#: ../settings/security/third-party/saml.rst:130 -msgid "" -"The public certificate of your IDP for Zammad to verify during the callback " -"phase." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Note" msgstr "" -#: ../settings/security/third-party/saml.rst:145 -msgid "IDP certificate fingerprint" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.note}``" msgstr "" -#: ../settings/security/third-party/saml.rst:134 -msgid "" -"The fingerprint of your IDPs public certificate to verify during callback " -"phase." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Phone" msgstr "" -#: ../settings/security/third-party/saml.rst:137 -msgid "🔏 **For the IdP certificate / certificate fingerprint:**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.phone}``" msgstr "" -#: ../settings/security/third-party/saml.rst:139 -msgid "" -"Provide **only one or the other**—do not provide both! (Between the two, we " -"recommend the signing certificate itself: fingerprints use SHA-1, which `has " -"been broken for a while now `_.)" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > VIP" msgstr "" -#: ../settings/security/third-party/saml.rst:144 -msgid "" -"**Keycloak users:** Find your certificate in the Keycloak admin panel under " -"**Realm Settings > Keys > Algorithm: RS256 > Certificate**." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.vip}``" msgstr "" -#: ../settings/security/third-party/saml.rst:151 -msgid "Name identifier format" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``false`` or ``true``" msgstr "" -#: ../settings/security/third-party/saml.rst:148 -msgid "" -"This is the unique identifiers field type. Usually it should be ``urn:oasis:" -"names:tc:SAML:1.1:nameid-format:emailAddress``." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Web" msgstr "" -#: ../settings/security/third-party/saml.rst:151 -msgid "Zammad **expects an email address as unique identifier**!" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.web}``" msgstr "" -#: ../settings/security/third-party/saml.rst:155 -msgid "UID attribute name" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > VIP" msgstr "" -#: ../settings/security/third-party/saml.rst:154 -msgid "" -"Here you can define an attribute that uniquely identifies the user. If " -"unset, the name identifier returned by the IDP is used." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.vip}``" msgstr "" -#: ../settings/security/third-party/saml.rst:None -msgid "Example configuration of SAML part 2" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Web" msgstr "" -#: ../settings/security/third-party/saml.rst:163 -msgid "" -"Decide if the certificate for the connection to the IdP service has to be " -"verified or not (default: ``yes``)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.web}``" msgstr "" -#: ../settings/security/third-party/saml.rst:169 -msgid "Signing & Encrypting" +#: ../misc/variables/ticket.rst:6 +msgid "" +"Below you can find all available ticket-based variables within Zammad. These " +"can be called via triggers for example. If you're unsure if Zammad does " +"support variables at the point you're at, you can try to type ``::`` to " +"check." msgstr "" -#: ../settings/security/third-party/saml.rst:169 -msgid "" -"Define if you want to sign, encrypt, do both or nothing for the requests." +#: ../misc/variables/ticket.rst:12 +msgid "Ticket Variables" msgstr "" -#: ../settings/security/third-party/saml.rst:179 -msgid "Certificate (PEM)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Accounted Time" msgstr "" -#: ../settings/security/third-party/saml.rst:172 -msgid "" -"Paste the public certificate of your Zammad SAML client, if you want to " -"encrypt the requests." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.time_unit}``" msgstr "" -#: ../settings/security/third-party/saml.rst:175 -msgid "Make sure the certificate is:" +#: ../misc/variables/ticket.rst:1 +msgid "``1``, ``2.75`` or empty response" msgstr "" -#: ../settings/security/third-party/saml.rst:177 -msgid "already valid and not yet expired" +#: ../misc/variables/ticket.rst:1 +msgid "``3``, any number of articles existing in the ticket right now" msgstr "" -#: ../settings/security/third-party/saml.rst:178 -msgid "no CA certificate" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Closing time" msgstr "" -#: ../settings/security/third-party/saml.rst:179 -msgid "valid for signing and encrypting" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.close_at}``" msgstr "" -#: ../settings/security/third-party/saml.rst:185 -msgid "Private key (PEM)" +#: ../misc/variables/ticket.rst:1 +msgid "2019-10-07 17:25:00 UTC" msgstr "" -#: ../settings/security/third-party/saml.rst:182 -msgid "" -"Paste the private key of your Zammad SAML client here, if you want to sign " -"the requests." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created at" msgstr "" -#: ../settings/security/third-party/saml.rst:185 -msgid "Make sure the key is an RSA key with a length of at least 2048 bits." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_at}``" msgstr "" -#: ../settings/security/third-party/saml.rst:188 -msgid "Private key secret" +#: ../misc/variables/ticket.rst:1 +msgid "2019-10-07 16:25:00 UTC" msgstr "" -#: ../settings/security/third-party/saml.rst:188 -msgid "If your private key is secured with a secret, you can provide it here." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Address" msgstr "" -#: ../settings/security/third-party/saml.rst:192 -msgid "Your callback URL" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.address}``" msgstr "" -#: ../settings/security/third-party/saml.rst:191 -msgid "" -"This URL is needed for your IdP configuration so it knows where to redirect " -"to after successful authentication." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Avatar" msgstr "" -#: ../settings/security/third-party/saml.rst:194 -msgid "" -"After saving your input by clicking on the \"Submit\" button, Zammad " -"verifies the provided keys/certificates (e.g. if they are valid for signing/" -"encrypting and if they aren't expired)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/saml.rst:199 -msgid "" -"See :ref:`automatic account linking ` for details " -"on how to link existing Zammad accounts to IdP accounts." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Department" msgstr "" -#: ../settings/security/third-party/saml.rst:205 -msgid "Automatic account linking doesn't work" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.department}``" msgstr "" -#: ../settings/security/third-party/saml.rst:206 -msgid "" -"Have you double-checked your IdP's user attribute mapping configuration?" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Email" msgstr "" -#: ../settings/security/third-party/twitter.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via Twitter. To do " -"so, you need to follow these steps:" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.email}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:8 -msgid "Register Twitter App" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Fax" msgstr "" -#: ../settings/security/third-party/twitter.rst:10 -msgid "Go to https://dev.twitter.com/apps and login with your account." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.fax}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:15 -msgid "Click on \"Create App\"" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Firstname" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "new app page" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.firstname}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:20 -msgid "" -"Enter app settings. As \"Callback URL\" you need to enter ``https://" -"zammad_host/api/v1/external_credentials/twitter/callback``. You need to " -"replace ``zammad_host`` with the domain of your Zammad system." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Lastname" msgstr "" -#: ../settings/security/third-party/twitter.rst:24 -msgid "" -"After the app has been created, update the application icon and organization " -"attributes." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.lastname}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "set permissions to receive and send direct messages" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Login" msgstr "" -#: ../settings/security/third-party/twitter.rst:30 -msgid "" -"Next we need to set ``read, write and access direct messages`` permissions " -"for the app." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.login}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "click on Keys & Access Token, note them" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Mobile" msgstr "" -#: ../settings/security/third-party/twitter.rst:36 -msgid "" -"Go to \"Keys and Access Token\" tab and note the \"Consumer Key\" and " -"\"Consumer Secret\"." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.mobile}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:40 -msgid "Configure Zammad as Twitter App" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Note" msgstr "" -#: ../settings/security/third-party/twitter.rst:42 -msgid "" -"Go to \"Admin > Security > Twitter > Third Party Applications > Twitter\" " -"Section." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.note}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "Admin > Security > Third Party Applications" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Phone" msgstr "" -#: ../settings/security/third-party/twitter.rst:48 -msgid "" -"Fill in the \"Twitter Key\" and the \"Twitter Secret\" and click the " -"\"Submit\" button." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.phone}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:51 -msgid "" -"Now you can link accounts via \"Avatar > Profile > Link Accounts\" or login " -"via Zammad login page." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > VIP" msgstr "" -#: ../settings/security/two-factor.rst:11 -msgid "Two-factor Authentication Methods" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.vip}``" msgstr "" -#: ../settings/security/two-factor.rst:2 -msgid "Two-Factor Authentication" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Web" msgstr "" -#: ../settings/security/two-factor.rst:4 -msgid "" -"Two-factor authentication (2FA) enhances the security of Zammad accounts by " -"adding an extra layer of verification beyond a password. It requires users " -"to provide two different types of authentication factors, typically " -"something they know (like a password) and something they possess (like a " -"mobile device or a security token), to ensure that only authorized " -"individuals can access the account." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.web}``" msgstr "" -#: ../settings/security/two-factor.rst:19 -msgid "Enable Recovery Codes" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Address" msgstr "" -#: ../settings/security/two-factor.rst:21 -msgid "" -"Recovery codes are one-time use security codes that can be used by the user " -"if they lose access to their other two-factor authentication methods. They " -"cannot be used on their own, they can only be activated if at least one two-" -"factor authentication method is enabled." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.address}``" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Enable Recovery Codes Setting" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Avatar" msgstr "" -#: ../settings/security/two-factor.rst:30 -msgid "" -"Recovery codes can only be used as a backup method. If enabled, they will be " -"automatically generated for the user once they set up their initial two-" -"factor authentication method." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.avatar(60,60)}``" msgstr "" -#: ../settings/security/two-factor.rst:34 -msgid "" -"The user will be asked to print out or save the generated recovery codes in " -"a safe place. Once used, a recovery code cannot be reused." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Department" msgstr "" -#: ../settings/security/two-factor.rst:37 -msgid "" -"Users will also have an option to regenerate their recovery codes at any " -"time, which invalidates already existing recovery codes and provides them " -"with a list of fresh codes." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.department}``" msgstr "" -#: ../settings/security/two-factor.rst:41 -msgid "" -"After you enable this setting, when the user completes a setup of their " -"initial two-factor authentication method, they will be presented with a list " -"of recovery codes and instructed to save them for later use." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Email" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Recovery Codes Generation Modal Dialog" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.email}``" msgstr "" -#: ../settings/security/two-factor.rst:50 -msgid "Enforce the Set Up of the Two-Factor Authentication" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Fax" msgstr "" -#: ../settings/security/two-factor.rst:52 -msgid "" -"In case you wish to require your users to set up at least one two-factor " -"authentication method for their account, you can do this by selecting " -"specific user roles the requirement applies to in **Enforced for user " -"roles** setting. Of course you must have at least one two-factor " -"authentication method enabled for this setting to take effect." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.fax}``" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Enforced for User Roles Setting" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Firstname" msgstr "" -#: ../settings/security/two-factor.rst:62 -msgid "" -"After you change this setting, if the user has one of the selected roles on " -"their account, they will be forced to set up the two-factor authentication " -"upon next sign in or application reload." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.firstname}``" msgstr "" -#: ../settings/security/two-factor.rst:66 -msgid "" -"A modal dialog with instructions will be shown, and they will not be able to " -"do any work before they set up at least one two-factor method." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Lastname" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Modal Dialog for Enforcing Two-Factor Authentication Set Up" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.lastname}``" msgstr "" -#: ../settings/security/two-factor.rst:74 -msgid "Reset Two-Factor Authentication for a Specific User" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Login" msgstr "" -#: ../settings/security/two-factor.rst:76 -msgid "" -"In case an user isn't able to login anymore because of an inaccessible " -"second factor, you can reset the user's 2FA method." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.login}``" msgstr "" -#: ../settings/security/two-factor.rst:79 -msgid "" -"To do this, go to the user management and search for the relevant user. " -"After you found the account, click the button in the action column and " -"select \"Manage Two-Factor Authentication\":" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Mobile" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Context menu in action column in user management" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.mobile}``" msgstr "" -#: ../settings/security/two-factor.rst:87 -msgid "" -"After selecting this, you can see a dialog where you can either reset one " -"2FA method or reset all of the user's 2FA methods:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Note" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Dialog for resetting user's 2FA method" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.note}``" msgstr "" -#: ../settings/security/two-factor.rst:94 -msgid "" -"Choose the fitting one, click on the corresponding \"Remove ...\" button and " -"confirm your action. The user now has to setup a new 2FA method, depending " -"on your 2FA configuration." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Phone" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:2 -msgid "Authenticator App" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.phone}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:4 -msgid "" -"The authenticator app method is a type of two-factor authentication that " -"uses a mobile application to generate one-time codes for account " -"verification. After setting up the authenticator app on their device, the " -"user links it to their Zammad account." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > VIP" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:12 -msgid "" -"When logging in, the user is prompted to enter a time-sensitive code " -"generated by the app, in addition to their password. This code acts as the " -"second factor of authentication, providing an extra layer of security as it " -"changes periodically and is unique to the user's device." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.vip}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:None -msgid "Security Code in Google Authenticator App" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Web" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:22 -msgid "" -"The app generates codes based on a shared secret key stored securely on both " -"the user's device and the server, ensuring a synchronized and secure " -"authentication process. The method of generating the codes is sometimes also " -"called TOTP (time-based one-time password)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.web}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:28 -msgid "Enabling the Authenticator App Method" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Escalation at" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:30 -#: ../settings/security/two-factor/security-keys.rst:28 -msgid "To enable the method, just toggle the switch on in the settings." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.escalation_at}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:None -msgid "Authenticator App Switch in Settings" +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:36 -msgid "" -"Now the users will be able to set up this two-factor authentication method " -"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " -"Once they do, on next sign-in with password, they will be asked to provide " -"an additional security code generated by their mobile device." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > First response" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:2 -msgid "Security Keys" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.first_response_at}``" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:4 -msgid "" -"The security keys method is a type of a two-factor authentication that uses " -"Web Authentication API in the browser for verifying user's identity. The " -"user can register multiple hardware or software security keys with their " -"Zammad account and then they can use it during the sign-in process." +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable yet" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:12 -msgid "" -"When logging in, the user is prompted to provide the same security key they " -"registered with their account, in addition to their password. This key acts " -"as the second factor of authentication, providing an extra layer of security." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Assign Follow-Ups" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:None -msgid "Security Key dialog in Safari on macOS" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_assignment}``" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:21 -msgid "" -"The type of the key can range from hardware USB sticks to passkeys stored in " -"a device of user's choice. Which type can be used depends on the browser " -"flavor and the platform of the user." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Assignment Timeout" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:26 -msgid "Enabling the Security Keys Method" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.assignment_timeout}``" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:None -msgid "Security Keys Switch in Settings" +#: ../misc/variables/ticket.rst:1 +msgid "``20`` or empty if not configured" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:34 -msgid "" -"Now the users will be able to set up this two-factor authentication method " -"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " -"Once they do, on next sign-in with password, they will be asked to provide " -"the same security key they registered during the setup." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Follow-up possible" msgstr "" -#: ../settings/system/system-selfhosted.include.rst:3 -msgid "" -"Below settings are only available to self hosted users. In hosted " -"environments we're handling these settings for you to ensure service " -"stability." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_possible}``" msgstr "" -#: ../settings/system/base.rst:11 -msgid "Fully Qualified Domain Name" +#: ../misc/variables/ticket.rst:1 +msgid "``no`` or ``yes``" msgstr "" -#: ../settings/system/base.rst:7 -msgid "The URL of your Zammad installation." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Name" msgstr "" -#: ../settings/system/base.rst:9 ../settings/system/base.rst:17 -msgid "This setting is used within :doc:`/system/variables` and notifications." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.name}``" msgstr "" -#: ../settings/system/system-base.include.rst:1 -msgid "It is automatically set by the *Getting Started wizard*." +#: ../misc/variables/ticket.rst:1 +msgid "``Sales``" msgstr "" -#: ../settings/system/system-base.include.rst:5 -msgid "Changing this setting also changes callback URLs for your channels etc." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Note" msgstr "" -#: ../settings/system/system-base.include.rst:6 -msgid "This setting can have negative affects on being able to login." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.note}``" msgstr "" -#: ../settings/system/base.rst:19 -msgid "HTTP type" +#: ../misc/variables/ticket.rst:1 +msgid "``Note about this group``" msgstr "" -#: ../settings/system/base.rst:14 -msgid "" -"The HTTP type tells your installation how your clients connect. This is " -"relevant for authentication and cookie security." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > ID" msgstr "" -#: ../settings/system/base.rst:31 -msgid "SystemID" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.id}``" msgstr "" -#: ../settings/system/base.rst:22 -msgid "" -"This ID is being used within your ticket number. In case you're " -"communicating with another ticket system with similar ticket number schemes " -"this ID greatly reduces the risk of false follow ups." +#: ../misc/variables/ticket.rst:1 +msgid "``17``, ``5281``, ..." msgstr "" -#: ../settings/system/base.rst:26 -msgid "" -"The SystemID is randomly selected upon installation of Zammad (``1-99``)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact (agent)" msgstr "" -#: ../settings/system/base.rst:30 -msgid "" -"**Do not** change this setting in a productive system! Your Zammad " -"installation may no longer recognize old ticket number based follow ups upon " -"change!" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_agent_at}``" msgstr "" -#: ../settings/system/frontend.rst:2 -msgid "Frontend" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact (customer)" msgstr "" -#: ../settings/system/frontend.rst:22 -msgid "Core Workflow Ajax Mode" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_customer_at}``" msgstr "" -#: ../settings/system/frontend.rst:6 +#: ../misc/variables/ticket.rst:1 msgid "" -"This setting allows administrators to enforce :doc:`/system/core-workflows` " -"to use Ajax-Calls instead of web sockets. You'll usually only need this if " -"you experience serious issues as noted below." +"``2019-10-07 16:25:00 UTC`` or empty if not applicable yet (Please note " +"`Ticket last contact behavior Settings `_ for this)" msgstr "" -#: ../settings/system/frontend.rst:10 -msgid "**🤓 Possible (technical) reasons**" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact" msgstr "" -#: ../settings/system/frontend.rst:12 -msgid "" -"In some cases, your network structure (e.g. firewalls, proxies) may " -"disconnect long web socket connections. This leads to select fields staying " -"empty (e.g. owner selection *after* selecting your group) or fields not " -"shown / hidden (e.g. when switching to or from pending states, the \"pending " -"till\" field not showing / hiding)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_at}``" msgstr "" -#: ../settings/system/frontend.rst:18 -msgid "" -"Please keep in mind that the Ajax fallback may cause serious pressure on " -"your application server. If you have the choice stick to web sockets." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Number" msgstr "" -#: ../settings/system/frontend.rst:22 -msgid "Default: ``no`` (inactive)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.number}``" msgstr "" -#: ../settings/system/frontend.rst:53 -msgid "Show calendar weeks in the picker of date/datetime fields" +#: ../misc/variables/ticket.rst:1 +msgid "``31001``, ``201910731001``, ..." msgstr "" -#: ../settings/system/frontend.rst:25 -msgid "" -"With this setting you can instruct Zammad to provide week number display " -"globally for all users. Calendar with week number display are usually used " -"in business sectors and may not be relevant for everyone." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain based assignment" msgstr "" -#: ../settings/system/frontend.rst:29 -msgid "" -"This setting affects *all areas* - you'll also see week numbers in the admin " -"panel for e.g. triggers and macros." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain_assignment}``" msgstr "" -#: ../settings/system/frontend.rst:32 -msgid "Default: ``no`` (not shown)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain" msgstr "" -#: ../settings/system/frontend.rst:53 -msgid "Here's the difference:" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain}``" msgstr "" -#: ../settings/system/frontend.rst:0 -msgid "Screenshot showing Zammad's date picker (in the default way)" +#: ../misc/variables/ticket.rst:1 +msgid "``domain.tld`` or empty if not set" msgstr "" -#: ../settings/system/frontend.rst:41 -msgid "Set to ``no``" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Name" msgstr "" -#: ../settings/system/frontend.rst:0 -msgid "" -"Screenshot showing Zammad's date picker with\n" -"week numbers enabled" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.name}``" msgstr "" -#: ../settings/system/frontend.rst:50 -msgid "Set to ``yes``" +#: ../misc/variables/ticket.rst:1 +msgid "``Zammad GmbH`` or empty if not set" msgstr "" -#: ../settings/system/index.rst:4 -msgid "" -"For your overview we split each tab within system settings into its own page:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Note" msgstr "" -#: ../settings/system/index.rst:16 -msgid "Console Based Settings" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.note}``" msgstr "" -#: ../settings/system/index.rst:18 -msgid "" -"There's some console based settings we didn't put into the UI. However, you " -"may find them helpful - you can find them in our :docs:`hidden settings ` section." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Shared organization" msgstr "" -#: ../settings/system/network.rst:2 -msgid "Network" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.shared}``" msgstr "" -#: ../settings/system/network.rst:8 -msgid "" -"The proxy settings can only be saved after successfully testing the proxy " -"connection." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > VIP" msgstr "" -#: ../settings/system/network.rst:15 -msgid "Proxy Address." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.vip}``" msgstr "" -#: ../settings/system/network.rst:12 -msgid "" -"Allows you to provide a proxy server if needed. This is relevant for network " -"communication by Zammad." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Address" msgstr "" -#: ../settings/system/network.rst:15 -msgid "It **does not** affect the update process or Elasticsearch." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.address}``" msgstr "" -#: ../settings/system/network.rst:18 -msgid "Username for proxy connection." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Avatar" msgstr "" -#: ../settings/system/network.rst:18 -msgid "" -"If your proxy server requires authentication, provide the username here." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.avatar(60,60)}``" msgstr "" -#: ../settings/system/network.rst:21 -msgid "Password for proxy connection." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Department" msgstr "" -#: ../settings/system/network.rst:21 -msgid "" -"If your proxy server requires authentication, provide the password here." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.department}``" msgstr "" -#: ../settings/system/network.rst:26 -msgid "No proxy for the following hosts." +#: ../misc/variables/ticket.rst:1 +msgid "``Support`` or empty if not set" msgstr "" -#: ../settings/system/network.rst:24 -msgid "" -"Exception list for hosts you can't or don't want to reach via proxy server." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Email" msgstr "" -#: ../settings/system/network.rst:27 -msgid "Default: ``localhost,127.0.0.0,::1``" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.email}``" msgstr "" -#: ../settings/system/services.rst:2 -msgid "Services" +#: ../misc/variables/ticket.rst:1 +msgid "``agent@company.tld`` or empty if not set" msgstr "" -#: ../settings/system/services.rst:10 -msgid "Image Service" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Fax" msgstr "" -#: ../settings/system/services.rst:5 -msgid "Defines the backend for user and organization image lookups." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.fax}``" msgstr "" -#: ../settings/system/services.rst:7 -msgid "Default: ``Zammad Image Service`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Firstname" msgstr "" -#: ../settings/system/services.rst:9 -msgid "" -"Make sure your on premise installation has ``HTTPS`` access to ``images." -"zammad.com``." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.firstname}``" msgstr "" -#: ../settings/system/services.rst:18 -msgid "Geo Calendar Service" +#: ../misc/variables/ticket.rst:1 +msgid "``Max`` or empty if not set" msgstr "" -#: ../settings/system/services.rst:13 -msgid "" -"Defines the backend for geo calendar lookups. Used for initial calendar " -"setup." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Lastname" msgstr "" -#: ../settings/system/services.rst:16 -msgid "Default: ``Zammad GeoCalendar Service`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.lastname}``" msgstr "" -#: ../settings/system/services.include.rst:2 -msgid "" -"Make sure your on premise installation has ``HTTPS`` access to ``geo.zammad." -"com``." +#: ../misc/variables/ticket.rst:1 +msgid "``Mustermann`` or empty if not set" msgstr "" -#: ../settings/system/services.rst:26 -msgid "Geo IP Service" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Login" msgstr "" -#: ../settings/system/services.rst:21 -msgid "" -"Defines the backend for geo IP lookups. Shows also location of an IP address " -"if an IP address is shown." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.login}``" msgstr "" -#: ../settings/system/services.rst:24 -msgid "Default: ``Zammad GeoIP Service`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "``agent``" msgstr "" -#: ../settings/system/services.rst:32 -msgid "Geo Location Service" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Mobile" msgstr "" -#: ../settings/system/services.rst:29 -msgid "" -"Defines the backend for geo location lookups to store geo locations for " -"addresses." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.mobile}``" msgstr "" -#: ../settings/system/services.rst:32 -msgid "" -"Default: ``OpenStreetMap (ODbL 1.0, http://osm.org/copyright)`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Note" msgstr "" -#: ../settings/system/services.rst:36 -msgid "" -"You can find a detailed privacy information on what we store for how long on " -"our :docs:`Privacy Appendix ` inside of our System " -"Documentation." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.note}``" msgstr "" -#: ../settings/system/storage.rst:2 -msgid "Storage" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Phone" msgstr "" -#: ../settings/system/storage.rst:6 -msgid "" -"Here you can define where Zammad stores attachments for tickets and the " -"knowledge base. By default, we're writing to the ``Database`` - you can " -"switch to ``Filesystem`` or ``Simple Storage (S3)`` at any time. In this " -"case please have a look on the following instructions." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.phone}``" msgstr "" -#: ../settings/system/storage.rst:11 -msgid "" -"If you have a busy Zammad instance, we strongly encourage you to use " -"filesystem storage instead of \"Database\". This will greatly improve system " -"performance (de-crease database load and size)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > VIP" msgstr "" -#: ../settings/system/storage.rst:19 -msgid "Database" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.vip}``" msgstr "" -#: ../settings/system/storage.rst:17 -msgid "" -"This is the default storage method. The attachments are stored directly in " -"the database. If your Zammad instance grows, we recommend one of the other " -"methods to maintain performance." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Web" msgstr "" -#: ../settings/system/storage.rst:38 -msgid "Filesystem" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.web}``" msgstr "" -#: ../settings/system/storage.rst:22 -msgid "" -"This storage method is recommended for all Zammad instances, especially for " -"those with a higher load. If you choose filesystem, your files are written " -"to ``/opt/zammad/storage/``." +#: ../misc/variables/ticket.rst:1 +msgid "``https://zammad.com`` or empty if not set" msgstr "" -#: ../settings/system/storage.rst:26 -msgid "" -"Moving attachments from \"Database\" to \"Filesystem\" can be run during " -"production use. However, you should consider your framework conditions (e.g. " -"bandwidth, system load in production) to define the right moment." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Pending till" msgstr "" -#: ../settings/system/storage.rst:32 -msgid "**You noticed slow updates of Zammad?**" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.pending_time}``" msgstr "" -#: ../settings/system/storage.rst:34 -msgid "" -"While Zammad is beeing updated, it enforces a recursive \"change " -"owner\" (chown) for this directory. For instances with many files this can " -"be time consuming. To mitigate that you can move your files and create a " -"symlink in ``/opt/zammad/storage/`` to the new directory. Of course you have " -"to make sure on your own that the permissions are always correct." +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not set" msgstr "" -#: ../settings/system/storage.rst:95 -msgid "Simple Storage (S3)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Priority > Name" msgstr "" -#: ../settings/system/storage.rst:41 -msgid "" -"To use the Simple Storage (S3), you have to provide some settings, which " -"can't be accessed in the UI (see instructions below)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.priority.name}``" msgstr "" -#: ../settings/system/storage.rst:44 -msgid "" -"⚠️ Please note that the current implementation is in its early stages and can " -"be modified in the future." +#: ../misc/variables/ticket.rst:1 +msgid "``2 normal``" msgstr "" -#: ../settings/system/storage.rst:47 -msgid "" -"The prerequisite is to have access to a S3-compatible storage and to have " -"all necessary parameters available (which depends on your storage provider; " -"if in doubt, please ask there for help)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > State > Name" msgstr "" -#: ../settings/system/storage.rst:51 -msgid "Steps to configure S3:" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.state.name}``" msgstr "" -#: ../settings/system/storage.rst:53 -msgid "" -"Copy ``config/zammad/storage.yml.dist`` to ``config/zammad/storage.yml``" +#: ../misc/variables/ticket.rst:1 +msgid "``new``, ``open``, ..." msgstr "" -#: ../settings/system/storage.rst:54 -msgid "Edit the copied file in one of the following ways:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Tags" msgstr "" -#: ../settings/system/storage.rst:56 -msgid "" -"Either provide your S3 configuration with one attribute per line like in the " -"upper area of the file" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.tags}``" msgstr "" -#: ../settings/system/storage.rst:58 +#: ../misc/variables/ticket.rst:1 msgid "" -"Or provide your S3 configuration as an URL (which you can find at the end of " -"the file). Note: you can also provide this URL as environment variable (:" -"docs:`see system documentation `) without using this yml-file." +"Currently not available, see `Issue 2769 `_" msgstr "" -#: ../settings/system/storage.rst:62 -msgid "" -"We recommend the deletion of the not used configuration style to avoid " -"inconsistencies." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Title" msgstr "" -#: ../settings/system/storage.rst:65 -msgid "Restart Zammad so the config file / environment variable is loaded" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.title}``" msgstr "" -#: ../settings/system/storage.rst:66 +#: ../misc/variables/ticket.rst:1 msgid "" -"Set the \"Storage Method\" in Zammad to ``Simple Storage (S3)`` in Settings " -"> System > Storage and click on \"Submit\". After that, Zammad checks your " -"configuration and the connection to the service and will raise an error " -"message if something is wrong." +"``My amazing Subject`` (normally subject, can be edited within Interface and " +"thus differ)" msgstr "" -#: ../settings/system/storage.rst:72 -msgid "A very simple storage configuration could look like this:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated at" msgstr "" -#: ../settings/system/storage.rst:85 -msgid "" -"Before setting the storage method to ``Simple Storage (S3)`` (step 4), " -"please make sure to have a working setup." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_at}``" msgstr "" -#: ../settings/system/storage.rst:88 -msgid "" -"You can verify this by running ``rails r 'Rails.logger = Logger.new(STDOUT); " -"pp Store::Provider::S3.ping?'`` in your Zammad directory. If everything is " -"fine, you should see ``true``, else you should see ``false`` and a simple " -"error message." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Address" msgstr "" -#: ../settings/system/storage.rst:93 -msgid "" -"If you installed Zammad through a package manager (rather than from source), " -"replace ``rails r`` with ``zammad run rails r`` above. To learn more, see :" -"docs:`Administration via Console `." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.address}``" msgstr "" -#: ../settings/ticket.rst:4 -msgid "" -"Here you can adjust general ticket settings. Additional ones for the ticket " -"composer interface can be found in the :doc:`/misc/composer`." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Avatar" msgstr "" -#: ../settings/ticket.rst:11 -msgid "Ticket Hook (default: ``Ticket#``)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.avatar(60,60)}``" msgstr "" -#: ../settings/ticket.rst:11 -msgid "The identifier for a ticket; *e.g.,* Ticket#, Call#, MyTicket#." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Department" msgstr "" -#: ../settings/ticket.rst:38 -msgid "Ticket Hook Position (default: ``right``)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.department}``" msgstr "" -#: ../settings/ticket.rst:14 -msgid "" -"With this setting you can decide (if) where to insert the ticket number." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Email" msgstr "" -#: ../settings/ticket.rst:20 -msgid "*Right*" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.email}``" msgstr "" -#: ../settings/ticket.rst:17 -msgid "" -"This setting will add the ticket reference on the right site of the subject." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Fax" msgstr "" -#: ../settings/ticket.rst:20 -msgid "Example: ``Some Subject [Ticket#12345]``" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.fax}``" msgstr "" -#: ../settings/ticket.rst:26 -msgid "*Left*" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Firstname" msgstr "" -#: ../settings/ticket.rst:23 -msgid "" -"This setting will add the ticket reference on the left site of the subject." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.firstname}``" msgstr "" -#: ../settings/ticket.rst:26 -msgid "Example: ``[Ticket#12345] Some Subject``" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Lastname" msgstr "" -#: ../settings/ticket.rst:29 -msgid "*None*" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.lastname}``" msgstr "" -#: ../settings/ticket.rst:29 -msgid "This will completely remove ticket references from the subject." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Login" msgstr "" -#: ../settings/ticket.rst:33 -msgid "" -"Please ensure to take a look at :doc:`/channels/email/settings` within the " -"email channel to ensure you have at least one reference that helps Zammad to " -"assign follow-ups correctly." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.login}``" msgstr "" -#: ../settings/ticket.rst:37 -msgid "" -"Disabling this and not setting up any further follow up search will lead to " -"unexpected results!" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Mobile" msgstr "" -#: ../settings/ticket.rst:65 -msgid "" -"Ticket Last Contact Behaviour (default: ``Use the start time of the last " -"customer thread (which may consist of multiple articles).``)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.mobile}``" msgstr "" -#: ../settings/ticket.rst:41 -msgid "" -"This setting changes the way Zammad updates the ``Last Contact`` value of a " -"ticket. This is fairly important for overviews and what you expect upon " -"ticket updates of a customer." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Note" msgstr "" -#: ../settings/ticket.rst:52 -msgid "" -"Use the start time of the last customer thread (which may consist of " -"multiple articles)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.note}``" msgstr "" -#: ../settings/ticket.rst:46 -msgid "" -"If this option is chosen, Zammad will update the last updated value just " -"once if a customer replies. After that, Zammad will wait for an agent to " -"react." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Phone" msgstr "" -#: ../settings/ticket.rst:50 -msgid "" -"This comes in handy if you want to work tickets in the order of their first " -"update. This will not change ticket orders if customers decide to \"bump\" " -"the ticket affected." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.phone}``" msgstr "" -#: ../settings/ticket.rst:57 -msgid "Use the time of the very last customer article." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > VIP" msgstr "" -#: ../settings/ticket.rst:55 -msgid "" -"When setting this option, Zammad will always update the last updated value. " -"This means that if ordering by ``Last Update``, ticket orders will change if " -"customers \"bump\" the ticket." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.vip}``" msgstr "" -#: ../settings/ticket.rst:64 -msgid "Last contact value used on :doc:`/manage/overviews`" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Web" msgstr "" -#: ../settings/ticket.rst:65 -msgid "Last contact value used on :doc:`/manage/trigger`" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.web}``" msgstr "" -#: ../settings/ticket.rst:88 -msgid "" -"Ticket Organization Reassignment (default: ``Update the most recent tickets." -"``)" +#: ../settings/branding.rst:10 +msgid "Product Name" msgstr "" -#: ../settings/ticket.rst:68 +#: ../settings/branding.rst:7 msgid "" -"This setting changes the way Zammad updates the organization field of the " -"tickets whenever the primary organization of a user is changed." -msgstr "" - -#: ../settings/ticket.rst:74 -msgid "Update the most recent tickets." +"Defines the name of the application, shown in the web interface, tabs and " +"title bar of the web browser." msgstr "" -#: ../settings/ticket.rst:72 -msgid "" -"If this option is chosen, Zammad will update the 100 most recent tickets " -"where the user is the ticket customer. The ticket organization field will be " -"automatically set to the new primary organization of the user." +#: ../settings/branding.rst:10 +msgid "Default value: ``Zammad Helpdesk``" msgstr "" -#: ../settings/ticket.rst:88 -msgid "Do not update any tickets." +#: ../settings/branding.rst:13 +msgid "Will be shown in the app and is included in email footers." msgstr "" -#: ../settings/ticket.rst:77 -msgid "" -"When choosing this option, Zammad will not update any tickets when the " -"user's primary organization is changed." +#: ../settings/branding.rst:19 +msgid "Logo" msgstr "" -#: ../settings/ticket.rst:80 -msgid "**Use with care!**" +#: ../settings/branding.rst:16 +msgid "Defines the logo of the application, shown in the login page of Zammad." msgstr "" -#: ../settings/ticket.rst:82 +#: ../settings/branding.rst:18 msgid "" -"Using this option may lead to inconsistencies in the system as the ticket " -"organization may become decoupled from the ticket customer." +"Ensure to hit the \"Submit\" button after uploading the logo. Otherwise your " +"change will not be saved." msgstr "" -#: ../settings/ticket.rst:85 +#: ../settings/branding.rst:22 msgid "" -"However, you may use this option if you wish to maintain :ref:`the shared " -"access ` to the ticket for all organization " -"members of the original organization of the customer." +"Allows to set the default language of the Zammad instance. The here defined " +"locale mostly acts as a fallback for:" msgstr "" -#: ../settings/ticket.rst:110 -msgid "Ticket Number Format (default: ``Increment (SystemID.Counter)``)" +#: ../settings/branding.rst:25 +msgid "user preferences (if Zammad can't detect the users locale)" msgstr "" -#: ../settings/ticket.rst:94 -msgid "" -"This setting defines the way Zammad's ticket number will look. Changing this " -"setting in production will cause follow up detection to fail." +#: ../settings/branding.rst:26 +msgid "CSV output (reporting, time accounting)" msgstr "" -#: ../settings/ticket.rst:102 -msgid "Increment (SystemID.Counter)" +#: ../settings/branding.rst:30 +msgid "Define the timezone of your Zammad installation." msgstr "" -#: ../settings/ticket.rst:98 +#: ../settings/branding.rst:32 msgid "" -"The increment value contains the SystemID (automatically generated during " -"installation) and a increment which counts up with every new Ticket. The " -"increment will automatically get another digit if needed." +"This does not have any effect on timings for your agents or how Zammad " +"stores date and time values." msgstr "" -#: ../settings/ticket.rst:102 -msgid "Examples: ``1010138``, ``1010139``" +#: ../settings/branding.rst:35 +msgid "Changing this value has direct consequences on the following areas:" msgstr "" -#: ../settings/ticket.rst:110 -msgid "Date (Year.Month.Day.SystemID.Counter)" +#: ../settings/branding.rst:37 +msgid ":doc:`/manage/scheduler` tasks" msgstr "" -#: ../settings/ticket.rst:105 -msgid "" -"This version of the ticket number is fairly long. However, because it " -"contains the date of ticket creation, it also allows you to see when the " -"ticket has been created. You may feel familiar with this number format if " -"you've worked with OTRS already." +#: ../settings/branding.rst:38 +msgid "search indexing (and thus reporting)" msgstr "" -#: ../settings/ticket.rst:110 -msgid "Examples: ``201206231010138``, ``201206231010139``" +#: ../settings/branding.rst:40 +msgid "calendar subscriptions" msgstr "" -#: ../settings/ticket.rst:137 -msgid "OPTIONS" +#: ../settings/branding.rst:41 +msgid "browser printing" msgstr "" -#: ../settings/ticket.rst:113 +#: ../settings/branding.rst:43 msgid "" -"The below options allow you to further customize your ticket number. The " -"availability of options differ depending of the chosen ticket number format " -"above." +"Please note that some of above are fallbacks in case Zammad could not detect " +"the agents timezone correctly." msgstr "" -#: ../settings/ticket.rst:122 -msgid "Checksum (default: ``no``)" +#: ../settings/branding.rst:77 +msgid "Pretty Date" msgstr "" -#: ../settings/ticket.rst:118 +#: ../settings/branding.rst:47 msgid "" -"If set to yes, we'll built a checksum to further \"unique\" the ticket " -"number of your system. If you're dealing with many other ticket systems this " -"might help to prevent false positive follow up detection on tickets." +"This setting allows you to define how Zammad should display time stamps " +"within the interface to all users." msgstr "" -#: ../settings/ticket.rst:122 -msgid "This will also add another digit to the ticket number." +#: ../settings/branding.rst:50 +msgid "" +"This does not have any effect on how Zammad returns e.g. time values via " +"variables." msgstr "" -#: ../settings/ticket.rst:137 -msgid "Min. size of Number (default: ``5``)" +#: ../settings/branding.rst:77 +msgid "Choose in between the following options:" msgstr "" -#: ../settings/ticket.rst:125 -msgid "" -"This setting defines the minimum length of your ticket number. If your " -"counter is not yet high enough, Zammad will fill the number with zeros to " -"ensure the wanted length." +#: ../settings/branding.rst:64 +msgid "relative" msgstr "" -#: ../settings/ticket.rst:129 +#: ../settings/branding.rst:55 msgid "" -"Please note that the minimum length is ``3`` (SystemID + at least one digit " -"if below 10). Also, if the length is no longer long enough, the number will " -"automatically get one digit longer. Ticket-Numbers **do not overflow**, thus " -"it's save to keep it at 5 or set it lower if wanted." +"This timestamp shows a relative time span until it switches to a date. Over " +"time, it will change as follows:" msgstr "" -#: ../settings/ticket.rst:135 -msgid "" -"This option is only available if ticket number format is set to " -"``Increment``!" +#: ../settings/branding.rst:58 +msgid "just now" msgstr "" -#: ../settings/ticket.rst:142 -msgid "Auto-Assignment" +#: ../settings/branding.rst:59 +msgid "5 minutes ago" msgstr "" -#: ../settings/ticket.rst:144 -msgid "" -"In a larger Zammad environment, it happens that several agents open the same " -"ticket at the same time. Although collision detection is then effective, the " -"efficiency of processing can be increased by means of the automatic " -"assignment of tickets when a ticket is opened." +#: ../settings/branding.rst:60 +msgid "3 days 1 hour ago" msgstr "" -#: ../settings/ticket.rst:149 -msgid "" -"The automatic assignment of tickets can be activated and configured in the " -"admin area under Settings > Ticket > Auto Assignment." +#: ../settings/branding.rst:61 +msgid "``03/04/2022``" msgstr "" -#: ../settings/ticket.rst:152 -msgid "" -"The auto assignment only works if the ticket has no owner yet. By default, " -"the agent can always reset the ticket owner to ``-`` if needed." +#: ../settings/branding.rst:63 +msgid "Hovering the timestamp helps, you'll always get a clean timestamp then." msgstr "" -#: ../settings/ticket.rst:155 -msgid "" -"If you want to use this function for only specific tickets, you can " -"configure the conditions accordingly to meet your requirement. By default " -"the condition affects all tickets with the state ``open``." +#: ../settings/branding.rst:71 +msgid "absolute" msgstr "" -#: ../settings/ticket.rst:161 +#: ../settings/branding.rst:67 msgid "" -"If you need to exclude users (e.g. a group leader), you can search and " -"select the desired agents in the ``Exception Users`` list. The search " -"function in this area is only effective, if you have too many agents to " -"display at once to help you with the configuration." +"This timestamp always includes the week day. For one week after creation, " +"the timestamp will not contain the date itself: Thursday 18:35." msgstr "" -#: ../settings/ticket.rst:167 -msgid "Notifications" +#: ../settings/branding.rst:71 +msgid "After a week it will switch to: ``Friday 4. Mar 16:00``." msgstr "" -#: ../settings/ticket.rst:191 -msgid "Default Notifications" +#: ../settings/branding.rst:76 +msgid "timestamp" msgstr "" -#: ../settings/ticket.rst:170 +#: ../settings/branding.rst:74 msgid "" -"This setting allows you to configure the default ticket notifications that " -"will be applied to all new agent users (incl. users who were just assigned " -"agent role). Simply change the notification matrix to desired state and " -"press **Save**." +"This will cause Zammad to show a complete timestamp according to your locale " +"defaults. For English this could be e.g. ``2022/12/03 2:40 pm`` or for " +"German e.g. ``12.03.2022 14:40``." msgstr "" -#: ../settings/ticket.rst:175 -msgid "" -"In case an agent already exists, their ticket notification preferences will " -"be preserved. Optionally, you can also **Apply current defaults to all " -"agents**." +#: ../settings/branding.rst:78 +msgid "Default setting: ``relative``." msgstr "" -#: ../settings/ticket.rst:181 -msgid "" -"**Potential time-consuming action:** Applying default ticket notifications " -"to all agent users may take some time to complete, be patient! The exact " -"time will depend on the size of your system and the number of agents." +#: ../settings/security.rst:2 +msgid "Security" msgstr "" -#: ../settings/ticket.rst:185 +#: ../settings/security.rst:4 msgid "" -"**Active agents only!** When current default ticket notifications are " -"applied, only active agent users are considered. In case an agent is re-" -"activated *after* this action, they will still have the old notification " -"configuration." +"For your overview we split each tab within security settings into its own " +"page:" msgstr "" -#: ../settings/ticket.rst:190 +#: ../settings/security/base.rst:2 ../settings/system/base.rst:2 +#: ../settings/ticket.rst:8 +msgid "Base" +msgstr "" + +#: ../settings/security/base.rst:5 +msgid "New User Accounts" +msgstr "" + +#: ../settings/security/base.rst:9 msgid "" -"In case you want to go back to the initial state of ticket notifications, " -"you can click on **Reset to default** button." +"Activates the `register as a new customer` function on the login page. If " +"set to ``no`` only administrators or agents can create new accounts manually." msgstr "" -#: ../settings/ticket.rst:194 ../settings/ticket.rst:196 -msgid "Duplicate Detection" +#: ../settings/security/base.rst:13 ../settings/security/base.rst:38 +#: ../settings/security/base.rst:66 +msgid "Default setting: ``yes``" msgstr "" -#: ../settings/ticket.rst:236 ../settings/ticket.rst:238 -msgid "Detect Duplicate Ticket Creation" +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"New User Accounts\" setting" msgstr "" -#: ../settings/ticket.rst:197 ../settings/ticket.rst:199 +#: ../settings/security/base.rst:22 msgid "" -"This setting turns on the duplicate ticket detection mechanism during ticket " -"creation. If similar tickets are found in the system, a suitable warning " -"will be shown to the user trying to create a ticket." +"Deactivation of above function **does not** deactivate automatic account " +"creation! This means: If a user writes e.g. an email to Zammad and has no " +"account yet, Zammad will automatically create the account. User accounts are " +"a direct dependency of tickets and thus technically mandatory." msgstr "" -#: ../settings/ticket.rst:204 ../settings/ticket.rst:206 -msgid "A Sample Duplicate Ticket Warning" +#: ../settings/security/base.rst:29 +msgid "Lost Password" msgstr "" -#: ../settings/ticket.rst:206 ../settings/ticket.rst:208 +#: ../settings/security/base.rst:33 msgid "" -"You can choose which ticket attributes will be matched by selecting them in " -"**Attributes to compare** field. Only if the ticket attribute value provided " -"by the user in the ticket create form is *equal* with the attribute in an " -"existing ticket, the warning will be shown." +"Activates the `lost password` function on the login page. If set to ``no`` " +"only administrators may change the user's password - users may update their " +"own password if they're still logged in and they have the required :doc:" +"`permission `." msgstr "" -#: ../settings/ticket.rst:211 ../settings/ticket.rst:213 -msgid "**Warning title** and **Warning message** are configurable as well." +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"Lost Password\" setting" msgstr "" -#: ../settings/ticket.rst:213 ../settings/ticket.rst:215 +#: ../settings/security/base.rst:49 msgid "" -"You can limit the detection only to certain user roles. By default, only " -"agents will see the warning." +"With third party authentications - but especially LDAP - you may want to " +"disable this function. Zammad **will not** change third party login " +"passwords and instead set or change the local password!" msgstr "" -#: ../settings/ticket.rst:216 ../settings/ticket.rst:218 -msgid "" -"If you don't want to show the matched tickets as part of the warning, you " -"can set **Show matching ticket(s) in the warning** setting to *no*." +#: ../settings/security/base.rst:56 +msgid "Password Login" msgstr "" -#: ../settings/ticket.rst:219 ../settings/ticket.rst:221 +#: ../settings/security/base.rst:60 msgid "" -"By default, **Permission level for looking up ticket** is set to *User*, " -"which means user permissions will be honored during sarch. The user will " -"see the warning only if tickets they have access to are matched. " -"Alternatively, you can set this setting to *System*, in which case the " -"search will happen within *all* tickets in the system, regardless of user " -"permissions." +"Activates the username & password login by default and if no third-party " +"login is activated. Disabling password login on the Zammad login page only " +"takes effect if you enable any :doc:`third-party`." msgstr "" -#: ../settings/ticket.rst:225 ../settings/ticket.rst:227 -msgid "**🦺 Safety first!**" +#: ../settings/security/base.rst:64 +msgid "See :doc:`third-party` for supported third-party logins." msgstr "" -#: ../settings/ticket.rst:227 ../settings/ticket.rst:229 -msgid "" -"Even if the permission level is set to *System*, the user will not be shown " -"the tickets they don't have access to in the warning, even if they match." +#: ../settings/security/base.rst:0 +msgid "Figure showing de-activated \"Password Login\" setting" msgstr "" -#: ../settings/ticket.rst:231 ../settings/ticket.rst:233 +#: ../settings/security/base.rst:77 msgid "" -"However, just the confirmation about the existence of the tickets in the " -"system may be considered an unwanted information disclosure. Use this option " -"carefully!" +"To help administrators to overcome \"login issues\", Zammad automatically " +"offers a password request for administrator users. This allows you to adjust " +"Third-Party applications even if the login does no longer work!" msgstr "" -#: ../settings/ticket.rst:235 ../settings/ticket.rst:237 -msgid "" -"Finally, you can configure between matching within **All tickets** or **Open " -"tickets** only by setting **Match tickets in following states**. Depending " -"on the current ticket state, a ticket may or not be matched." +#: ../settings/security/base.rst:84 +msgid "Session Timeout" msgstr "" -#: ../system/core-workflows.rst:2 -msgid "Core Workflows" +#: ../settings/security/base.rst:86 +msgid "" +"All settings below by default are set to ``4 weeks``. Session Timeout " +"defines the life time of a users session. As soon as it's reached, Zammad " +"will automatically log off the session in question." msgstr "" -#: ../system/core-workflows.rst:4 +#: ../settings/security/base.rst:91 msgid "" -"Core Workflows allow you to adjust object attributes in many ways. For " -"example:" +"Zammad takes the highest value set assigned for the user based on the " +"permissions." msgstr "" -#: ../system/core-workflows.rst:7 -msgid "show / hide fields" +#: ../settings/security/base.rst:94 +msgid "``admin``" msgstr "" -#: ../system/core-workflows.rst:8 -msgid "adjust mandatory setting" +#: ../settings/security/base.rst:96 +msgid "``ticket.customer``" msgstr "" -#: ../system/core-workflows.rst:9 -msgid "manipulate available options" +#: ../settings/security/base.rst:97 +msgid "``default`` (fallback if user doesn't have above permissions set)" msgstr "" -#: ../system/core-workflows.rst:11 +#: ../settings/security/base.rst:99 msgid "" -"With this, you can provide exactly the information your users really need!" +"All settings act independently from each other allowing you to disable the " +"timeouts for e.g. admins, but not agents." msgstr "" -#: ../system/core-workflows.rst:15 -msgid "" -"If the pre-defined :doc:`/system/objects` are not enough, please add them " -"beforehand." +#: ../settings/security/base.rst:115 +#: ../system/integrations/checkmk/api-reference.rst:13 +msgid "Example" msgstr "" -#: ../system/core-workflows.rst:17 -msgid "" -"If you experience slow or unreliable field updates, please see :ref:`Core " -"Workflow Ajax Modus `" +#: ../settings/security/base.rst:107 +msgid "Let's suppose you configured the following session timeouts" msgstr "" -#: ../system/core-workflows.rst:22 -msgid "" -"This is a very enhanced functionality and can cause unexpected UI behavior. " -"Please ensure to test your use cases after configuration to reduce surprises." +#: ../settings/security/base.rst:104 +msgid "default: 3 weeks" msgstr "" -#: ../system/core-workflows.rst:None -msgid "Dialogue for adding a new workflow" +#: ../settings/security/base.rst:105 +msgid "admin: 2 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:2 -msgid "Core Workflow Condition Operators" +#: ../settings/security/base.rst:106 +msgid "ticket.agent: 4 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:4 -msgid "" -"You might know that there is a separate section for explaining :doc:" -"`condition operators `. Head over there to " -"see a detailed explanation of many conditions and operators." +#: ../settings/security/base.rst:107 +msgid "ticket.customer: 1 week" msgstr "" -#: ../system/core-workflows/condition-operators.rst:8 -msgid "" -"Due to differences to other places in Zammad which are also using conditions " -"(e.g. triggers), you can find a dedicated description of operators for core " -"workflows below." +#: ../settings/security/base.rst:115 +msgid "This results in the following situations" msgstr "" -#: ../system/core-workflows/condition-operators.rst:12 -msgid "" -"Be aware that the availability of the operators depends on the selected " -"attribute and its field type. Some of the operators may only be available " -"for system attributes (e.g. for \"tags\", \"active\")." +#: ../settings/security/base.rst:110 +msgid "a user with ``admin`` permission will have a timeout of 2 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:20 -msgid "Operator" +#: ../settings/security/base.rst:111 +msgid "" +"a user with ``admin`` and ``ticket.agent`` permissions will have a timeout " +"of 2 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:22 -msgid "after (absolute)" +#: ../settings/security/base.rst:113 +msgid "" +"a user with ``ticket.customer`` permission will have a timeout of 1 week" msgstr "" -#: ../system/core-workflows/condition-operators.rst:23 -msgid "Matches if a date/time is after a specific point in time." +#: ../settings/security/base.rst:115 +msgid "" +"a user with neither ``admin``, ``ticket.agent`` nor ``ticket.customer`` " +"permissions will have a timeout of 3 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:24 -msgid "after (relative)" +#: ../settings/security/password.rst:4 +msgid "" +"This section allows you to define password requirements for the local user " +"accounts." msgstr "" -#: ../system/core-workflows/condition-operators.rst:25 -msgid "Matches if a time span after a specified event has passed." +#: ../settings/security/password.rst:9 +msgid "" +"Zammad does **not** allow you to change your LDAP password, instead, it will " +"set a password in its local database which might confuse your users. This " +"might be addressed in the future by `#1169 `_." msgstr "" -#: ../system/core-workflows/condition-operators.rst:26 -msgid "before (absolute)" +#: ../settings/security/password.rst:14 +msgid "**Exception for admins**" msgstr "" -#: ../system/core-workflows/condition-operators.rst:27 -msgid "Matches if a date/time is before a specific point in time." +#: ../settings/security/password.rst:16 +msgid "" +"Please note that below password policies *do not* affect administrators " +"setting passwords on user accounts. While this seems strange and not safe we " +"believe that an administrator knowing an user's password is insecure as well." msgstr "" -#: ../system/core-workflows/condition-operators.rst:28 -msgid "before (relative)" +#: ../settings/security/password.rst:21 +msgid "The suggested workflow is either:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:29 -msgid "Matches if a time span after a specified event has not passed." +#: ../settings/security/password.rst:23 +msgid "" +"to use third party logins to not require local passwords at all **- or -**" msgstr "" -#: ../system/core-workflows/condition-operators.rst:30 -msgid "contains" +#: ../settings/security/password.rst:25 +msgid "to require your *user to reset the password* upon first login." msgstr "" -#: ../system/core-workflows/condition-operators.rst:31 -msgid "Matches if a specified value is present." +#: ../settings/security/password.rst:27 +msgid "" +"This way administrators are not required to set a user's password at all!" msgstr "" -#: ../system/core-workflows/condition-operators.rst:33 -msgid "Matches if all of the specified values are present." +#: ../settings/security/password.rst:31 +msgid "Maximum Failed Logins" msgstr "" -#: ../system/core-workflows/condition-operators.rst:35 -msgid "Matches if none of the specified values are present." +#: ../settings/security/password.rst:33 +msgid "" +"You can choose a value between ``4`` and ``20``. This defines how often a " +"login to a user account may fail until Zammad will lock it. Your users can " +"always use the \"forgot password\" function to change their password and " +"unlock their account." msgstr "" -#: ../system/core-workflows/condition-operators.rst:36 -msgid "contains not" +#: ../settings/security/password.rst:38 +msgid "The default value is ``10``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:37 -msgid "Matches if a specified value is not present." +#: ../settings/security/password.rst:42 +msgid "Beside changing the user's password, you can also unlock accounts via" msgstr "" -#: ../system/core-workflows/condition-operators.rst:39 -msgid "Matches if one specified value is present." +#: ../settings/security/password.rst:44 +msgid ":ref:`user management list `" msgstr "" -#: ../system/core-workflows/condition-operators.rst:41 -msgid "Matches if one specified value is not present." +#: ../settings/security/password.rst:45 +msgid ":docs:`console `" msgstr "" -#: ../system/core-workflows/condition-operators.rst:42 -msgid "does not match regex" +#: ../settings/security/password.rst:46 +msgid ":docs:`API `" msgstr "" -#: ../system/core-workflows/condition-operators.rst:43 -msgid "Matches if content doesn't fit to regex rule." +#: ../settings/security/password.rst:50 +msgid "Failed logins via LDAP no longer lock accounts." msgstr "" -#: ../system/core-workflows/condition-operators.rst:44 -msgid "ends with" +#: ../settings/security/password.rst:53 +msgid "2 Lower Case And 2 Upper Case Characters" msgstr "" -#: ../system/core-workflows/condition-operators.rst:45 -msgid "Matches if content ends with specified value." +#: ../settings/security/password.rst:55 +msgid "" +"You can add complexity to passwords by enforcing at least 2 upper and lower " +"case characters." msgstr "" -#: ../system/core-workflows/condition-operators.rst:46 -msgid "ends with one of" +#: ../settings/security/password.rst:58 ../settings/security/password.rst:83 +msgid "The default value is ``no``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:47 -msgid "Matches if content ends with one of the specified values." +#: ../settings/security/password.rst:62 +msgid "Minimum Length" msgstr "" -#: ../system/core-workflows/condition-operators.rst:48 -msgid "from (relative)" +#: ../settings/security/password.rst:64 +msgid "" +"This defines the minimum password length required for users to provide (from " +"``4`` to ``20``)." msgstr "" -#: ../system/core-workflows/condition-operators.rst:49 -msgid "Matches if date/time is after a period of time after an event." +#: ../settings/security/password.rst:67 +msgid "The default value is ``6``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:51 -msgid "Matches if content is equal to a specified value." +#: ../settings/security/password.rst:71 +msgid "Digit Required" msgstr "" -#: ../system/core-workflows/condition-operators.rst:52 -msgid "is any of" +#: ../settings/security/password.rst:73 +msgid "This enforces your users to use at least one digit within the password." msgstr "" -#: ../system/core-workflows/condition-operators.rst:53 -msgid "Matches if content is equal to any of specified values." +#: ../settings/security/password.rst:75 +msgid "The default value is ``yes``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:54 -msgid "is modified" +#: ../settings/security/password.rst:78 +msgid "Special Character Required" msgstr "" -#: ../system/core-workflows/condition-operators.rst:55 -msgid "Matches if content is modified." +#: ../settings/security/password.rst:80 +msgid "" +"This setting allows you to improve your password quality even more by " +"enforcing the password to contain at least one special character." msgstr "" -#: ../system/core-workflows/condition-operators.rst:57 -#: ../system/core-workflows/condition-operators.rst:61 -msgid "True from the moment of changing content until form submit." +#: ../settings/security/ssl-certificates.rst:2 +msgid "SSL Certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:58 -msgid "is modified to" +#: ../settings/security/ssl-certificates.rst:7 +msgid "" +"Zammad offers the possibility to upload custom certificates and custom " +"Certificate Authority (CA) certificates. This can be useful if you want to " +"connect Zammad the secure way to other systems which are using custom " +"certificates." msgstr "" -#: ../system/core-workflows/condition-operators.rst:59 -msgid "Matches if content is modified to a specific value." +#: ../settings/security/ssl-certificates.rst:12 +msgid "" +"An example usecase might be: You have an internal LDAP server that is not " +"accessible from the internet, and you want a SSL-encrypted connection, using " +"a custom certificate." msgstr "" -#: ../system/core-workflows/condition-operators.rst:62 -msgid "is none of" +#: ../settings/security/ssl-certificates.rst:19 +msgid "" +"You should have an existing custom certificate file and/or a custom CA " +"certificate file, which you want to add to Zammad. As filetype ``.crt`` is " +"supported and the certificate format has to be PEM (Base64 ASCII)." msgstr "" -#: ../system/core-workflows/condition-operators.rst:63 -msgid "Matches if content is none of any specified values." +#: ../settings/security/ssl-certificates.rst:25 +msgid "" +"When you import a custom CA certificate, all certificates generated with " +"this are trusted. This can be useful if you have more than one system/" +"certificate you want to connect to and the certificates are issued from the " +"same custom CA." msgstr "" -#: ../system/core-workflows/condition-operators.rst:65 -msgid "Matches if content is not equal to a specified value." +#: ../settings/security/ssl-certificates.rst:31 +msgid "Add a Certificate" msgstr "" -#: ../system/core-workflows/condition-operators.rst:67 -msgid "Matches if content is present." +#: ../settings/security/ssl-certificates.rst:33 +msgid "" +"To add a custom certificate or a custom CA certificate, head over to the " +"Admin panel > Settings > Security > SSL Certificates. Here you can find a " +"\"Add SSL Certificate\" button. In the dialog you can either select a " +"certificate file or paste the content of the certificate:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:68 -msgid "just changed" +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate adding dialog" msgstr "" -#: ../system/core-workflows/condition-operators.rst:69 -msgid "Matches if content has changed." +#: ../settings/security/ssl-certificates.rst:43 +msgid "" +"After selecting a file or pasting the content of the certificate, click on " +"the \"Add\" button to finally upload it to Zammad. Then, the certificates " +"are immediately effective, no restart or similar required." msgstr "" -#: ../system/core-workflows/condition-operators.rst:71 -#: ../system/core-workflows/condition-operators.rst:75 +#: ../settings/security/ssl-certificates.rst:49 msgid "" -"Only true for the moment of changing content until next form field action/" -"click." +"Please note that only single certificate files are supported. That means if " +"you want to import a certificate / CA certificate, it must contain **only " +"one** certificate." msgstr "" -#: ../system/core-workflows/condition-operators.rst:72 -msgid "just changed to" +#: ../settings/security/ssl-certificates.rst:54 +msgid "Certificate Overview" msgstr "" -#: ../system/core-workflows/condition-operators.rst:73 -msgid "Matches if content has changed to a specified value." +#: ../settings/security/ssl-certificates.rst:56 +msgid "" +"After you added a certificate, you can see a table with information for each " +"added certificate:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:76 -msgid "matches regex" +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing table of added certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:77 -msgid "Matches if value fits to regex rule." -msgstr "" - -#: ../system/core-workflows/condition-operators.rst:79 -msgid "Matches if no content is present." -msgstr "" - -#: ../system/core-workflows/condition-operators.rst:80 -msgid "starts with" +#: ../settings/security/ssl-certificates.rst:64 +msgid "" +"Here you can download the certificate or delete it, if you don't need it " +"anymore." msgstr "" -#: ../system/core-workflows/condition-operators.rst:81 -msgid "Matches if content starts with specified value." +#: ../settings/security/ssl-certificates.rst:68 +msgid "Deleting Certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:82 -msgid "starts with one of" +#: ../settings/security/ssl-certificates.rst:70 +msgid "" +"If you want to delete a specific certificate, you can do it by clicking on " +"the menu in the actions column and selecting delete:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:83 -msgid "Matches if content starts with one of the specified values." +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate deletion button" msgstr "" -#: ../system/core-workflows/condition-operators.rst:84 -msgid "till (relative)" +#: ../settings/security/ssl-certificates.rst:79 +msgid "Downloading Certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:85 -msgid "Matches if date/time is before a period of time before an event." +#: ../settings/security/ssl-certificates.rst:81 +msgid "" +"If you want to download your certificates, you can do this as well via " +"corresponding action buttons." msgstr "" -#: ../system/core-workflows/condition-operators.rst:86 -msgid "today" +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate download button" msgstr "" -#: ../system/core-workflows/condition-operators.rst:87 -msgid "Matches if date/time is today." +#: ../settings/security/third-party.rst:13 +msgid "Login Providers" msgstr "" -#: ../system/core-workflows/condition-operators.rst:88 -msgid "within last (relative)" +#: ../settings/security/third-party.rst:2 +msgid "Third-Party Applications" msgstr "" -#: ../system/core-workflows/condition-operators.rst:89 +#: ../settings/security/third-party.rst:4 msgid "" -"Matches if date/time content is within specified period of time before now." +"Third party authentication is a great way to help your users to login to " +"Zammad more easily. If the account is yet unknown, Zammad will create a new " +"user automatically, without the user needed to interact (e.g. type in his " +"name). Another big advantage of this feature is that your user doesn't need " +"to remember another password." msgstr "" -#: ../system/core-workflows/condition-operators.rst:91 -msgid "within next (relative)" +#: ../settings/security/third-party.rst:10 +msgid "" +"You can deactivate logging in via :ref:`security_password_login` if any of " +"the mentioned authentication providers are enabled in your instance." msgstr "" -#: ../system/core-workflows/condition-operators.rst:92 +#: ../settings/security/third-party.rst:27 msgid "" -"Matches if date/time content is within specified period of time after now." +"We're currently missing documentation for the following login providers:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:2 -msgid "How do they work?" +#: ../settings/security/third-party.rst:29 +msgid "LinkedIn" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:4 -msgid "" -"Core Workflows are executed according to their priority. If two workflows " -"have the same priority, they are executed in alphabetical order based on " -"their **name**." +#: ../settings/security/third-party.rst:30 +msgid "Weibo" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:8 -msgid "" -"Because of the way Core Workflows work, all changes to attributes are " -"checked with the application server - please see :doc:`limitations` for " -"possible issues." +#: ../settings/security/third-party.rst:35 +msgid "Automatic Account Link on Initial Logon" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:12 +#: ../settings/security/third-party.rst:37 msgid "" -"Below we're talking about settings that are important and not self-" -"explanatory." +"In general there's two possible options for Zammad on how to deal with " +"already known users as they try to authenticate against a third-party " +"application. By default, Zammad will not automatically link \"unknown\" " +"authentication providers to existing accounts." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:17 +#: ../settings/security/third-party.rst:42 msgid "" -"Choose the object context you want to run the workflow in. This will decide " -"on your available attributes and actions." -msgstr "" - -#: ../system/core-workflows/how-do-they-work.rst:20 -msgid "Ticket objects also have access to the ticket customer." +"This means that the user has to manually link authentication providers to " +"their accounts (for more about this :user-docs:`consult the user " +"documentation `)." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:25 +#: ../settings/security/third-party.rst:46 msgid "" -"Choose in which situation the workflow is applied. Contexts can be combined " -"to avoid duplicate workflows." +"Sometimes this doesn't come in handy as this also means you'll receive error " +"messages about \"email address being in use already\" for (yet) unknown " +"third-party authentication methods." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:30 -msgid "Creation mask" +#: ../settings/security/third-party.rst:50 +msgid "" +"If you want to allow your users to always be able to log in, no matter what, " +"you may want to enable ``Automatic account link on initial logon``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:29 +#: ../settings/security/third-party.rst:None msgid "" -"If selected, your conditions and actions will affect all applicable creation " -"masks." +"Screenshot highlighting the \"Automatic account link on initial logon\"\n" +"setting" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:34 -msgid "Edit mask" +#: ../settings/security/third-party.rst:60 +msgid "Automatic Account Linking Notification" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:33 +#: ../settings/security/third-party.rst:64 msgid "" -"If selected, your conditions and actions will affect all applicable edit " -"masks." +"To improve security and your users awareness, you can enable Zammad to " +"notify your users when a new third-party application has been linked to " +"their account." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:39 +#: ../settings/security/third-party.rst:68 msgid "" -"Zammad differentiates between selected and saved conditions. These can be " -"combined wherever needed." +"This notification is sent out once per third-party application. Zammad does " +"also mention the method used, e.g.: ``Microsoft``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:42 -msgid "**⚠️ Restrict workflows to specific roles if needed!**" +#: ../settings/security/third-party.rst:71 +msgid "By default this setting is not active (set to ``no``)." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:44 +#: ../settings/security/third-party.rst:0 msgid "" -"By default and unless configured in conditions, workflow rules are executed " -"for **all roles**. This also affects your customers!" +"Screenshot showing sample notification mail after initial\n" +"third-party linking" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:50 -msgid "Selected Conditions" +#: ../settings/security/third-party.rst:85 +msgid "" +"This notification is only sent if the account in question already exists. If " +"the login via the third-party also creates the missing account, the " +"notification will be skipped." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:48 -msgid "" -"These conditions are based on form values and match if an appropriate " -"selection is made (e.g. choosing another group in the ticket without " -"saving). This applies for drafts (active selection) and currently saved " -"values." +#: ../settings/security/third-party.rst:89 +msgid "This means it only affects:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:64 -msgid "Saved Conditions" +#: ../settings/security/third-party.rst:91 +msgid "manual account linking within the third-party page of the users profile" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:53 +#: ../settings/security/third-party.rst:92 msgid "" -"These conditions only match if the selected values are stored in the " -"database. It ignores the current value or selection of the field, as long as " -"the changes are not saved (e.g. performing field operations for an existing " -"ticket, which is viewed/opened by an agent)." +"logging into an existing local account by utilizing the *automatic account " +"link on initial logon* functionality" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:60 +#: ../settings/security/third-party.rst:None msgid "" -"Keep in mind that the value has to be available in the situation where you " -"need it. Otherwise the condition won't match." +"Screenshot showing the \"automatic account linking notification\"\n" +"setting" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:63 -msgid "" -"Example: you can't perform any actions with *saved condition* on a ticket in " -"creation, because there are no saved values at that time." +#: ../settings/security/third-party.rst:100 +msgid "No User Creation on Logon" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:66 +#: ../settings/security/third-party.rst:102 msgid "" -"You can find a description of the condition operators for core workflows :" -"doc:`here `." +"By default, Zammad will create a new user account if the user logs in via a " +"third-party application and the account doesn't exist yet." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:72 +#: ../settings/security/third-party.rst:105 msgid "" -"Which actions should we run on the relevant fields? The possible actions " -"depend on the object type. However, usually you can at least change the " -"visibility and whether the field is mandatory." +"If you want to prevent Zammad from creating new accounts on logon, you can " +"disable this feature by setting ``No user creation on logon`` to ``yes``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:76 -msgid "Be aware that actions are not available for **related** context." +#: ../settings/security/third-party.rst:None +msgid "Screenshot showing the \"no user creation on logon\" setting" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:78 +#: ../settings/security/third-party/facebook.rst:4 msgid "" -"**Example:** Let's assume you are working in the ticket context. While you " -"can have customer *conditions*, you *can't adjust* objects with actions in " -"that scope. That's because this wouldn't have any impact on the ticket " -"dialog. Of course all ticket attributes (state, owner, ...) are available." +"It is possible to create a quick login for your helpdesk via Facebook To do " +"so, you need to follow these steps:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:84 +#: ../settings/security/third-party/facebook.rst:9 +msgid "Register Facebook App" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:11 msgid "" -"Please also have a look at our :doc:`limitations` to be safe from surprises." +"Visit [https://developers.facebook.com/apps/] and click on \"Add a new App\"" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:88 -msgid "Available Operators" +#: ../settings/security/third-party/facebook.rst:None +msgid "initial page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:90 -msgid "The availability of operators depends on the object type and scope." +#: ../settings/security/third-party/facebook.rst:17 +msgid "After that enter the app settings" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:94 -msgid "" -"Please note that actions may or may not restrict API based access to " -"attributes. We're displaying the following icons for your overview to " -"understand these limits better:" +#: ../settings/security/third-party/facebook.rst:None +msgid "Create App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:0 -msgid "|api| This icon indicates the action affects the API." +#: ../settings/security/third-party/facebook.rst:22 +msgid "Navigate to \"Settings\" and fill in this infromation" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:163 -msgid "api" +#: ../settings/security/third-party/facebook.rst:None +msgid "App Settings" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:0 -msgid "|ui| This icon indicates the action only affects the web interface." +#: ../settings/security/third-party/facebook.rst:27 +msgid "Navigate to app review and Check \"Make [appname] public?\"" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:167 -msgid "ui" +#: ../settings/security/third-party/facebook.rst:None +msgid "App Review" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:102 -msgid "show |ui|" +#: ../settings/security/third-party/facebook.rst:35 +msgid "Configure Zammad as Facebook App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:102 -msgid "Display the chosen field. Allows setting of values." -msgstr "" - -#: ../system/core-workflows/how-do-they-work.rst:109 -msgid "hide |ui|" +#: ../settings/security/third-party/facebook.rst:37 +msgid "" +"Navigate to \"Admin -> Security -> Third Party Applications\" and enter the " +"App ID and the App Secret. You can find this Key in the Dashbard of your " +"Facebok app." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:105 -msgid "" -"Hide the chosen field. However, it technically still allows setting the " -"field." +#: ../settings/security/third-party/facebook.rst:None +msgid "Zammad Configuration" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:108 +#: ../settings/security/third-party/facebook.rst:44 +#: ../settings/security/third-party/github.rst:43 +#: ../settings/security/third-party/gitlab.rst:46 msgid "" -"Please note that the field is **not** gone and still contains an existing " -"value (if set)! Consider *remove* instead, if you want this field to be gone." +"Now you can link accounts via \"Avatar -> Profile -> Link Accounts\" or " +"login via Zammad login page." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:112 -msgid "remove |ui|" +#: ../settings/security/third-party/github.rst:2 +#: ../system/integrations/github.rst:2 +msgid "GitHub" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:112 -msgid "Entirely removes the field. The field value will not be evaluated." +#: ../settings/security/third-party/github.rst:4 +msgid "" +"It is possible to create a quick login for your helpdesk via GitHub. To " +"activate the quick login you need to enable OAuth for GitHub." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:115 -msgid "set mandatory |ui| |api|" +#: ../settings/security/third-party/github.rst:8 +msgid "Register GitHub App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:115 -msgid "Sets the field to mandatory." +#: ../settings/security/third-party/github.rst:10 +msgid "" +"Visit https://www.github.com/settings/applications/new and enter the app " +"settings. As callback URL enter \"https://zammad_host/auth/github/callback\" " +"where zammad_host has to be replaced with your Zammad FQDN" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:118 -msgid "set optional |ui| |api|" +#: ../settings/security/third-party/github.rst:None +msgid "Register OAuth app on www.github.com" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:118 -msgid "Sets the field to optional." +#: ../settings/security/third-party/github.rst:19 +msgid "Configure Zammad as GitHub App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:124 -msgid "add option |ui| |api|" +#: ../settings/security/third-party/github.rst:21 +msgid "" +"Enter the \"APP ID\" and the \"APP SECRET\" from the GitHub OAUTH " +"Applications Dashboard" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:121 -msgid "Allows adding options to tree selects or selects." +#: ../settings/security/third-party/github.rst:None +msgid "GitHub config in Zammad admin interface" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:123 +#: ../settings/security/third-party/github.rst:28 msgid "" -"You have to use the \"remove option\" before performing this action. It " -"allows you to use *existing* configured values." +"After you configured the GitHub credentials and activated the login method, " +"you should see a new icon on the login page." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:128 -msgid "remove option |ui| |api|" +#: ../settings/security/third-party/github.rst:None +msgid "GitHub logo on login page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:127 +#: ../settings/security/third-party/github.rst:34 msgid "" -"Allows removing options from tree selects or selects. It allows you to use " -"*existing* configured values." +"If you click on the icon you will be redirected to GitHub and see something " +"similar to this:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:134 -msgid "set fixed to |ui| |api|" +#: ../settings/security/third-party/github.rst:None +msgid "GitHub oauth page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:131 -msgid "Reduces the available options by your selection." +#: ../settings/security/third-party/github.rst:40 +#: ../settings/security/third-party/gitlab.rst:42 +msgid "" +"When you grant the access you will be redirected to your Zammad instance and " +"logged in as a customer." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:133 -msgid "" -"This reduces your workflows in terms of *add option* and *remove option*." +#: ../settings/security/third-party/gitlab.rst:2 +msgid "Gitlab" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:137 -msgid "fill in |ui|" +#: ../settings/security/third-party/gitlab.rst:4 +msgid "" +"It is possible to create a quick login for your helpdesk via Gitlab. To " +"activate the quick login you need to enable OAuth for Gitlab." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:137 -msgid "Allows filling in of string and integer fields with your values." +#: ../settings/security/third-party/gitlab.rst:8 +msgid "Register Gitlab App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:141 -msgid "fill in empty |ui|" +#: ../settings/security/third-party/gitlab.rst:10 +msgid "To register an app in Gitlab open your profile and select applications." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:140 +#: ../settings/security/third-party/gitlab.rst:12 msgid "" -"Allows filling in of string and integer fields with your values **if the " -"field is empty**." +"As callback URL enter \"https://zammad-fqdn/auth/gitlab/callback\" where " +"zammad-fqdn has to be replaced with your Zammad FQDN" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:144 -msgid "select |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Register OAuth app on gitlab instance" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:144 -msgid "Select a specific value within a select, tree select or boolean field." +#: ../settings/security/third-party/gitlab.rst:18 +msgid "Just select *read_user* under scopes as in the screenshot and save it." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:153 -msgid "auto select |ui|" +#: ../settings/security/third-party/gitlab.rst:21 +msgid "Configure Zammad as Gitlab App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:147 -msgid "Helps users with tree select and select fields:" +#: ../settings/security/third-party/gitlab.rst:23 +msgid "" +"Enter the \"APP ID\" and the \"APP SECRET\" from the Gitlab OAUTH " +"Applications Dashboard and your Gitlab-URL in the \"SITE\" field." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:149 -msgid "" -"If the field has only one option available for selection and no value yet, " -"the value will be automatically set." +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab config in Zammad admin interface" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:152 +#: ../settings/security/third-party/gitlab.rst:30 msgid "" -"This option only works if you have one value and doesn't work if there is " -"more than one option available." +"After you configured the Gitlab credentials and activated the login method, " +"you should see a new icon on the login page." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:157 -msgid "set readonly |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab logo on login page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:156 +#: ../settings/security/third-party/gitlab.rst:36 msgid "" -"Allows you to display an attribute as read only (which means no changes are " -"possible)." +"If you click on the icon you will be redirected to Gitlab and see something " +"similar to this:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:161 -msgid "unset readonly |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab oauth page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:160 +#: ../settings/security/third-party/google.rst:4 msgid "" -"In case a workflow set the field in question to read only, you can undo this " -"with option above." +"With some easy and fast steps, you can enable Zammad to authenticate your " +"users via Google." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:172 -msgid "Stop after match" +#: ../settings/security/third-party/google.rst:8 +msgid "Register a Google App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:174 +#: ../settings/security/third-party/google.rst:10 msgid "" -"Here you can decide if other workflows are executed after the current one." +"First of all, we need to create a new project - you can skip this step if " +"you already have one." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:176 +#: ../settings/security/third-party/google.rst:15 msgid "" -"If set to ``no`` (default), further workflows will be executed if they match " -"the condition. In this case, it is possible that your actions from the " -"current workflow can be overwritten by another workflow." +"Use this link to create a new project: https://console.cloud.google.com/" +"projectcreate" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:180 +#: ../settings/security/third-party/google.rst:18 msgid "" -"If set to ``yes``, no further worflows will be executed after the current " -"one." +"Now expand the menu, expand \"APIs & Services\" and select \"Credentials\". " +"Go to the tab \"OAuth consent screen\" first and ensure to fill in the " +"requested information - without doing so you can't create credentials!" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:184 -msgid "Priority" +#: ../settings/security/third-party/google.rst:None +msgid "Creating a consent screen" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:186 +#: ../settings/security/third-party/google.rst:25 msgid "" -"You can define the sequence, in which the workflows are executed. The " -"default value is ``500``." +"After filling in and saving the consent screen information, you can go to " +"the \"Credentials\" tab and create new \"OAuth client ID\"-Credentials." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:189 +#: ../settings/security/third-party/google.rst:28 msgid "" -"The workflows are executed in ascending order by their priority. That means " -"lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." +"Fill in the necessary information as follows and replace ``zammad_host`` " +"with your FQDN:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:2 -msgid "Learn by Example" +#: ../settings/security/third-party/google.rst:31 +msgid "**Application type** ``[x] Web application``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:4 -msgid "" -"This page provides some basic examples for Core Workflows. Of course you can " -"build much more complex workflows if needed." +#: ../settings/security/third-party/google.rst:34 +msgid "**Authorized JavaScript origins** ``https://zammad_host/``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:7 +#: ../settings/security/third-party/google.rst:37 msgid "" -"To learn about Core Workflows in detail, first go to :doc:`how-do-they-work`." +"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" +"callback``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:10 -msgid "Group Based Examples" +#: ../settings/security/third-party/google.rst:None +msgid "Adding a new OAuth client ID" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:12 +#: ../settings/security/third-party/google.rst:43 msgid "" -"All following workflows have the same base configurations. The workflow may " -"not use them all." +"After creating the credentials, go to your Zammad installation and navigate " +"to \"Admin > Security > Third Party Applications\" > Google. Enter your " +"Client ID and Client secret here." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:15 -msgid "Groups:" +#: ../settings/security/third-party/google.rst:None +msgid "Zammad" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:20 -msgid "Attributes:" +#: ../settings/security/third-party/google.rst:50 +msgid "After submitting, the login via Google can be used." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:22 -msgid "Category (Single tree selection field, not mandatory, agents only)" +#: ../settings/security/third-party/microsoft.rst:2 +msgid "Microsoft" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:23 +#: ../settings/security/third-party/microsoft.rst:4 msgid "" -"Approved (Boolean field, not mandatory, not shown, ``false`` as default)" +"Zammad's Microsoft connection allows your users with Microsoft accounts to " +"login. This works for Azure users as well and can be an alternative to :doc:" +"`/system/integrations/ldap/index`." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:24 -msgid "Operating System (Text field, not mandatory, not shown)" +#: ../settings/security/third-party/microsoft.rst:10 +msgid "" +"This documentation part does not cover our :doc:`📧 Microsoft 365 email " +"channel `." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:25 -msgid "Software used (Single selection field, not mandatory, not shown)" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screenshot showing Microsoft login button on Zammad login screen." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:68 -msgid "Group specific values and fields" +#: ../settings/security/third-party/microsoft.rst:30 +#: ../settings/security/third-party/microsoft.rst:53 +msgid "Supported account types:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:28 +#: ../settings/security/third-party/microsoft.rst:22 msgid "" -"This workflow set depends on the category field. It reduces the available " -"set of values based on the group selected." +"Please note that Zammad only supports these account types (App dependent):" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:33 -msgid "Workflow 2nd Level group" +#: ../settings/security/third-party/microsoft.rst:35 +msgid "Avatars of signing in users:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:35 +#: ../settings/security/third-party/microsoft.rst:33 msgid "" -"This reduces the category options to ``2nd Level/*``, ``Internal/*`` and " -"``Others``. It also sets further required fields to mandatory and visible." -msgstr "" - -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for 2nd level" +"Zammad currently ignores user avatars. If the user is registered with e.g. " +"Gravatar, Zammad will fetch the avatar from there if enabled. See :doc:" +"`Zammad Image Service ` for more." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:43 -msgid "Workflow Support group" +#: ../settings/security/third-party/microsoft.rst:38 +msgid "Step 1 - Register a Microsoft App for Zammad" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:45 +#: ../settings/security/third-party/microsoft.rst:40 msgid "" -"This reduces the category options to ``Support/*``, ``Internal/*`` and " -"``Others``. It also sets further required fields to visible." -msgstr "" - -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for support" +"Login to the `Microsoft Azure Portal `_ and " +"navigate to App registrations to create a new app. Provide the requested " +"information as follows and register your app." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:53 -msgid "Workflow Sales group" +#: ../settings/security/third-party/microsoft.rst:46 +msgid "Name:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:55 +#: ../settings/security/third-party/microsoft.rst:45 msgid "" -"This reduces the category options to ``Sales/*``, ``Internal/*`` and " -"``Others``." +"Any meaningful name fitting, this name will be displayed to users trying to " +"authenticate with this app." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for sales" +#: ../settings/security/third-party/microsoft.rst:49 +msgid "Choose one of the above mentioned account types (see Limitations)." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:68 -#: ../system/integrations/slack.rst:88 -msgid "The Result" +#: ../settings/security/third-party/microsoft.rst:51 +msgid "" +"The correct account type depends on your use case. If you want to use the " +"authentication internal only, choose the first option. If you're unsure, use " +"the \"Help me choose...\" link." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:63 -msgid "" -"This is what the agent would experience with the above workflows in place." +#: ../settings/security/third-party/microsoft.rst:58 +msgid "Redirect URI (optional):" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 +#: ../settings/security/third-party/microsoft.rst:56 msgid "" -"Workflow shows objects and limits options based on selections on the group" +"Select web and provide your callback URL. The callback URL looks like this: " +"``https://zammad.domain.tld/auth/microsoft_office365/callback``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:90 -msgid "Approval process" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to register a Microsoft app" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:71 -msgid "" -"In this case ``approved`` is visible to agents by default. For this " -"workflow, an additional role ``Approval person`` is required (no further " -"permissions)." +#: ../settings/security/third-party/microsoft.rst:71 +msgid "Within **API permissions** add the following permissions:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that restricts an approval attribute to specific roles" +#: ../settings/security/third-party/microsoft.rst:69 +msgid "``User.Read``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:81 -msgid "" -"This workflow may work best in combination with a :doc:`trigger ` but technically, this is not required." +#: ../settings/security/third-party/microsoft.rst:71 +msgid "Contacts" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:84 -msgid "" -"Select fields may be a better approach because they allow more values than " -"just a simple ``true`` or ``false``." +#: ../settings/security/third-party/microsoft.rst:71 +msgid "``Contacts.Read``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 +#: ../settings/security/third-party/microsoft.rst:73 msgid "" -"Workflow fixes possible values of \"Approved ?\" to a specific selection " -"depending on the users role" +"You can find these permissions within *Microsoft Graph → Delegated " +"permissions*." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:103 -msgid "State dependent mandatory fields" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to add required API permissions" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:93 +#: ../settings/security/third-party/microsoft.rst:80 msgid "" -"This workflow sets ``Category`` to mandatory if the agent wants to set the " -"states ``closed`` or ``pending close`` to enforce categorization." +"Within **Certificates & secrets** create a new client secret. Note down the " +"returned secret **value** for later. **Do not** use the secret ID!" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that sets fields to mandatory on specific states" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to create a new app secret" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 +#: ../settings/security/third-party/microsoft.rst:88 msgid "" -"Workflow sets category field to mandatory upon choosing closed or pending " -"close as state" +"From **Overview** copy your apps *Application (client) ID*. If you're using " +"a single tenant app, please also copy *Directory (tenant) ID*. You now have " +"all required information for Zammad." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:106 -msgid "Manual Ticket Handover Process" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to retreive application client and tenant IDs" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:108 -msgid "This example covers the handover of a ticket from one agent to another:" +#: ../settings/security/third-party/microsoft.rst:98 +msgid "Step 2 - Add App Credentials to Zammad" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:110 +#: ../settings/security/third-party/microsoft.rst:100 msgid "" -"When the ticket owner is modified, a new text field (\"Handover\") shows up " -"for a comment" +"Navigate to Security > Third-party Applications (Tab) within Zammad's admin " +"settings. Scroll down to the section *Authentication via Microsoft* and fill " +"in the required information." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:112 -msgid "" -"This may only be visible when the owner is changed, therefore it has to be " -"hidden in general" +#: ../settings/security/third-party/microsoft.rst:105 +msgid "App ID:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:114 -msgid "The input in this handover text field is mandatory" +#: ../settings/security/third-party/microsoft.rst:105 +msgid "This is your *Application (client) ID*." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:115 -msgid "" -"After submitting changes, the value of the handover field must be added as " -"an note to the ticket (via trigger)" +#: ../settings/security/third-party/microsoft.rst:108 +msgid "App secret:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:121 -msgid "Hiding handover field" +#: ../settings/security/third-party/microsoft.rst:108 +msgid "This is your *client secret* (value)." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Hiding the handover field in core workflows" +#: ../settings/security/third-party/microsoft.rst:113 +msgid "App Tenant ID:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:126 -msgid "Showing handover field and setting it to mandatory" +#: ../settings/security/third-party/microsoft.rst:111 +msgid "" +"**optional** only required for apps that use account type *Accounts in this " +"organizational directory only (Default Directory only - Single tenant).*" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Showing the handover field and set it as mandatory" +#: ../settings/security/third-party/microsoft.rst:115 +msgid "" +"Apply your settings by pressing submit and activate *Authentication via " +"Microsoft*." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:131 -msgid "Trigger writing handover input to a new article" +#: ../settings/security/third-party/microsoft.rst:None +msgid "" +"Screencast showing how to add app credentials and activating the\n" +"authentication method" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Write handover content to a new article" +#: ../settings/security/third-party/saml.rst:2 +msgid "SAML" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:133 +#: ../settings/security/third-party/saml.rst:4 msgid "" -"As a result, the ticket includes an article of the type note which includes " -"the predefined text and the handover comment." +"Connect your SAML (Security Assertion Markup Language) identity provider as " +"a single sign-on (SSO) method." msgstr "" -#: ../system/core-workflows/limitations.rst:6 -msgid "Core Workflows do not replace Triggers" +#: ../settings/security/third-party/saml.rst:7 +msgid "" +"SAML is an open standard for SSO authentication (among other things). Sign-" +"ins are shared across multiple **service providers** and managed by a " +"central **identity provider** (IdP)." msgstr "" -#: ../system/core-workflows/limitations.rst:5 +#: ../settings/security/third-party/saml.rst:11 msgid "" -"Workflows manipulate the behavior of fields. However, they do not set values " -"in fields because of actions." +"In this case, the service provider is Zammad, and the IdP is a software " +"service that you either host or subscribe to (*e.g.,* `Keycloak `_, `Redhat SSO Server `_, `ADFS `_, or `Okta `_)." msgstr "" -#: ../system/core-workflows/limitations.rst:16 -msgid "API calls are only partly affected" +#: ../settings/security/third-party/saml.rst:18 +msgid "" +"This guide assumes you are already using SAML within your organization (i." +"e., that your IdP is fully set up)." msgstr "" -#: ../system/core-workflows/limitations.rst:9 +#: ../settings/security/third-party/saml.rst:21 msgid "" -"Some options affect UI only and thus do not restrict responses and calls." +"Please note: Our instructions are based on connecting Zammad with Keycloak." msgstr "" -#: ../system/core-workflows/limitations.rst:11 -msgid "This affects the following actions:" +#: ../settings/security/third-party/saml.rst:25 +msgid "Step 1: Configure Your IdP" msgstr "" -#: ../system/core-workflows/limitations.rst:13 -msgid "select" +#: ../settings/security/third-party/saml.rst:28 +msgid "Add Zammad as a Client/App" msgstr "" -#: ../system/core-workflows/limitations.rst:14 -msgid "auto select" +#: ../settings/security/third-party/saml.rst:30 +msgid "" +"Import Zammad into your IdP using the XML configuration found at ``https://" +"your.zammad.domain/auth/saml/metadata``." msgstr "" -#: ../system/core-workflows/limitations.rst:15 -msgid "show" +#: ../settings/security/third-party/saml.rst:33 +msgid "" +"If your IdP doesn't support XML import, you will have to configure Zammad as " +"a new client/app manually using the above XML metadata file for reference." msgstr "" -#: ../system/core-workflows/limitations.rst:16 -msgid "hide" +#: ../settings/security/third-party/saml.rst:36 +msgid "For instance, when you see this tag:" msgstr "" -#: ../system/core-workflows/limitations.rst:25 -msgid "Some fields stay unavailable to customers" +#: ../settings/security/third-party/saml.rst:42 +msgid "" +"Set the **Assertion Consumer Service Binding URL** (sometimes also listed as " +"**Valid Redirect URIs**) to ``http://your.zammad.domain/auth/saml/callback``." msgstr "" -#: ../system/core-workflows/limitations.rst:19 -msgid "" -"For technical and security reasons, some default fields (the pale ones you " -"can't edit) stay unavailable for display and usage on customer permissions." +#: ../settings/security/third-party/saml.rst:47 +msgid "Set Up User Attribute Mapping" msgstr "" -#: ../system/core-workflows/limitations.rst:23 +#: ../settings/security/third-party/saml.rst:49 msgid "" -"If you require your customers to change e.g. priorities, please consider " -"using workarounds via :doc:`/system/objects` and :doc:`/manage/trigger`." +"Zammad requests the following user attributes (or “properties”) from the IdP:" msgstr "" -#: ../system/core-workflows/limitations.rst:29 -msgid "Ticket title changes not supported in edit mask" +#: ../settings/security/third-party/saml.rst:51 +msgid "Email address (``email``)" msgstr "" -#: ../system/core-workflows/limitations.rst:28 -msgid "" -"It is currently not possible to perform changes of the ticket title in the " -"edit mask (e.g. renaming, set to read-only)." +#: ../settings/security/third-party/saml.rst:52 +msgid "Full name (``name``)" msgstr "" -#: ../system/core-workflows/limitations.rst:37 -msgid "What is out of scope of Core Workflows?" +#: ../settings/security/third-party/saml.rst:53 +msgid "Given name (``first_name``)" msgstr "" -#: ../system/core-workflows/limitations.rst:32 -msgid "" -"There are some things that would count as workflow but are either done via :" -"doc:`/manage/trigger` or :doc:`/manage/scheduler`." +#: ../settings/security/third-party/saml.rst:54 +msgid "Family name (``last_name``)" msgstr "" -#: ../system/core-workflows/limitations.rst:35 -msgid "Such as (but not limited to):" +#: ../settings/security/third-party/saml.rst:56 +msgid "" +"You may need to set up “mappers” (or “mappings”) to tell your IdP how user " +"attributes in SAML correspond to those in Zammad. For a more detailed " +"breakdown, refer to the XML metadata file referenced in the previous section." msgstr "" -#: ../system/core-workflows/limitations.rst:37 -msgid "up- or downgrade permissions of users" +#: ../settings/security/third-party/saml.rst:62 +msgid "Per-IdP Instructions" msgstr "" -#: ../system/core-workflows/limitations.rst:38 -msgid "affecting article creation or listing" +#: ../settings/security/third-party/saml.rst:102 +msgid "Keycloak" msgstr "" -#: ../system/data-privacy.rst:2 -msgid "Data Privacy" +#: ../settings/security/third-party/saml.rst:65 +msgid "" +"**To add Zammad as a client,** save the XML configuration to disk (``https://" +"your.zammad.domain/auth/saml/metadata``) and use **Clients > Clients list > " +"Import client** in the Keycloak admin panel." msgstr "" -#: ../system/data-privacy.rst:4 +#: ../settings/security/third-party/saml.rst:70 msgid "" -"For compliance with GDPR and other data privacy laws, you may wish to " -"**permanently delete users from the system**, along with **all of their " -"associated tickets**." +"To help Zammad **match its own user accounts to Keycloak users**, create a " +"user attribute (or “property”) mapper. In **Clients list**, click on your " +"newly created Client ID, choose the tab **Client scopes** and click on the " +"link which refers to your Zammad instance. Choose **Add mapper > By " +"configuration > User Property** and create a mapper with the following " +"entries:" 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 `!" +#: ../settings/security/third-party/saml.rst:78 +msgid "**Name**" msgstr "" -#: ../system/data-privacy.rst:12 -msgid "" -"Access to this panel requires ``admin.data_privacy`` permissions (introduced " -"in Zammad 3.5)." +#: ../settings/security/third-party/saml.rst:80 +msgid "**Mapper Type**" msgstr "" -#: ../system/data-privacy.rst:15 -msgid "" -"On older systems that have not been updated yet, customers can also be :docs:" -"`deleted via the Zammad console `." +#: ../settings/security/third-party/saml.rst:81 +msgid "``User Property``" msgstr "" -#: ../system/data-privacy.rst:22 -msgid "User deletion dialog in the Data Privacy panel" +#: ../settings/security/third-party/saml.rst:82 +msgid "**Property**" msgstr "" -#: ../system/data-privacy.rst:22 -msgid "" -"The user deletion dialog lists some of the tickets that will be removed from " -"the system along with the user." +#: ../settings/security/third-party/saml.rst:83 +msgid "``emailAddress``" msgstr "" -#: ../system/data-privacy.rst:27 -msgid "Deleting Users via GUI" +#: ../settings/security/third-party/saml.rst:84 +msgid "**SAML Attribute Name**" msgstr "" -#: ../system/data-privacy.rst:29 -msgid "🔥 **All deletions are FINAL!**" +#: ../settings/security/third-party/saml.rst:86 +msgid "**SAML Attribute NameFormat**" msgstr "" -#: ../system/data-privacy.rst:31 -msgid "Once you click “Delete”, the action cannot be canceled or undone." +#: ../settings/security/third-party/saml.rst:87 +msgid "``basic``" msgstr "" -#: ../system/data-privacy.rst:33 +#: ../settings/security/third-party/saml.rst:89 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." +"In the example above, we're telling Zammad that whenever it receives a SAML " +"login request, it should take the ``email`` property from Keycloak, look for " +"a Zammad user with the same ``email`` attribute, and create a new session " +"for that user." msgstr "" -#: ../system/data-privacy.rst:36 -msgid "**The following records cannot be deleted:**" +#: ../settings/security/third-party/saml.rst:95 +msgid "" +"If your Keycloak users' email addresses are stored on another property (*e." +"g.,* ``username``), adjust accordingly." msgstr "" -#: ../system/data-privacy.rst:38 -msgid "your own account" +#: ../settings/security/third-party/saml.rst:98 +msgid "" +"Back in **Settings**, enter the Client ID (``https://your.zammad.domain/auth/" +"saml/metadata``) in the field **Master SAML Processing URL**." msgstr "" -#: ../system/data-privacy.rst:39 -msgid "the system's last remaining administrator account" +#: ../settings/security/third-party/saml.rst:101 +msgid "You also need to enable **Sign assertions**." msgstr "" -#: ../system/data-privacy.rst:42 -msgid "Step 1: Find a User / Confirm Deletion" +#: ../settings/security/third-party/saml.rst:105 +msgid "Step 2: Configure Zammad" msgstr "" -#: ../system/data-privacy.rst:44 -msgid "There are three ways to access the user deletion dialog:" +#: ../settings/security/third-party/saml.rst:107 +msgid "" +"Enable SAML and enter your IdP's details in the Admin Panel under **Settings " +"> Security > Third Party Applications > Authentication via SAML**:" msgstr "" -#: ../system/data-privacy.rst:51 -msgid "**from the user's profile**" +#: ../settings/security/third-party/saml.rst:None +msgid "Example configuration of SAML part 1" msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Accessing the user deletion dialog in a user profile" +#: ../settings/security/third-party/saml.rst:119 +msgid "Display name" msgstr "" -#: ../system/data-privacy.rst:51 -msgid "Click **Action > Delete**." +#: ../settings/security/third-party/saml.rst:116 +msgid "" +"Allows you to define a custom button name for SAML. This helps your users to " +"understand better what the button on the login page does." msgstr "" -#: ../system/data-privacy.rst:58 -msgid "**in the “Manage > Users” Admin Panel**" +#: ../settings/security/third-party/saml.rst:119 +msgid "Defaults to ``SAML``." msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Accessing the user deletion dialog under “Users” in the Admin Panel" +#: ../settings/security/third-party/saml.rst:123 +msgid "IDP SSO target URL" msgstr "" -#: ../system/data-privacy.rst:58 -msgid "Use the **⋮ Actions** menu for the target user." +#: ../settings/security/third-party/saml.rst:122 +msgid "" +"This is the target URL Zammad shall redirect to when the user presses the " +"SAML button. For Keycloak, this needs to look like https://your.domain/" +"realms/your-realm/protocol/saml" msgstr "" -#: ../system/data-privacy.rst:66 ../system/data-privacy.rst:104 -msgid "**in the “System > Data Privacy” Admin Panel**" +#: ../settings/security/third-party/saml.rst:127 +msgid "IDP single logout target URL" msgstr "" -#: ../system/data-privacy.rst:0 +#: ../settings/security/third-party/saml.rst:126 msgid "" -"Accessing the user deletion dialog under “Data Privacy” in the Admin Panel" +"This is the URL to which the single logout request and response should be " +"sent." msgstr "" -#: ../system/data-privacy.rst:65 +#: ../settings/security/third-party/saml.rst:131 +msgid "IDP certificate" +msgstr "" + +#: ../settings/security/third-party/saml.rst:130 msgid "" -"Use the **New Deletion Task** button. Search for users by name or email " -"address." +"The public certificate of your IDP for Zammad to verify during the callback " +"phase." msgstr "" -#: ../system/data-privacy.rst:79 -msgid "**Delete organizations**" +#: ../settings/security/third-party/saml.rst:145 +msgid "IDP certificate fingerprint" msgstr "" -#: ../system/data-privacy.rst:69 +#: ../settings/security/third-party/saml.rst:134 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:" +"The fingerprint of your IDPs public certificate to verify during callback " +"phase." msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Deleting an organization via the user deletion dialog" +#: ../settings/security/third-party/saml.rst:137 +msgid "🔏 **For the IdP certificate / certificate fingerprint:**" msgstr "" -#: ../system/data-privacy.rst:78 +#: ../settings/security/third-party/saml.rst:139 msgid "" -"If this option does not appear, make sure there are no pending deletion " -"tasks for other customers from this organization." +"Provide **only one or the other**—do not provide both! (Between the two, we " +"recommend the signing certificate itself: fingerprints use SHA-1, which `has " +"been broken for a while now `_.)" msgstr "" -#: ../system/data-privacy.rst:82 -msgid "Step 2: Monitor Deletion Job Status" +#: ../settings/security/third-party/saml.rst:144 +msgid "" +"**Keycloak users:** Find your certificate in the Keycloak admin panel under " +"**Realm Settings > Keys > Algorithm: RS256 > Certificate**." msgstr "" -#: ../system/data-privacy.rst:84 +#: ../settings/security/third-party/saml.rst:151 +msgid "Name identifier format" +msgstr "" + +#: ../settings/security/third-party/saml.rst:148 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:" +"This is the unique identifiers field type. Usually it should be ``urn:oasis:" +"names:tc:SAML:1.1:nameid-format:emailAddress``." msgstr "" -#: ../system/data-privacy.rst:98 -msgid "**in the Activity Stream**" +#: ../settings/security/third-party/saml.rst:151 +msgid "Zammad **expects an email address as unique identifier**!" msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Activity Stream showing data privacy tasks" +#: ../settings/security/third-party/saml.rst:155 +msgid "UID attribute name" msgstr "" -#: ../system/data-privacy.rst:94 +#: ../settings/security/third-party/saml.rst:154 msgid "" -"For each deleted user, the Activity Stream will be updated twice—once when " -"the task is created, and once when it's complete." +"Here you can define an attribute that uniquely identifies the user. If " +"unset, the name identifier returned by the IDP is used." msgstr "" -#: ../system/data-privacy.rst:97 -msgid "" -"These notifications are only visible to users with ``admin.data_privacy`` " -"permissions." +#: ../settings/security/third-party/saml.rst:None +msgid "Example configuration of SAML part 2" msgstr "" -#: ../system/data-privacy.rst:0 +#: ../settings/security/third-party/saml.rst:163 msgid "" -"The task list within Data Privacy shows removals being in progress and " -"completed." +"Decide if the certificate for the connection to the IdP service has to be " +"verified or not (default: ``yes``)." msgstr "" -#: ../system/data-privacy.rst:107 -msgid "Frequently Asked Questions" +#: ../settings/security/third-party/saml.rst:169 +msgid "Signing & Encrypting" msgstr "" -#: ../system/data-privacy.rst:121 -msgid "What happens if I receive an email from a deleted customer?" -msgstr "" - -#: ../system/data-privacy.rst:110 +#: ../settings/security/third-party/saml.rst:169 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." +"Define if you want to sign, encrypt, do both or nothing for the requests." msgstr "" -#: ../system/data-privacy.rst:115 -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**." +#: ../settings/security/third-party/saml.rst:179 +msgid "Certificate (PEM)" msgstr "" -#: ../system/data-privacy.rst:130 -msgid "What about user information stored in internal notes or other messages?" +#: ../settings/security/third-party/saml.rst:172 +msgid "" +"Paste the public certificate of your Zammad SAML client, if you want to " +"encrypt the requests." msgstr "" -#: ../system/data-privacy.rst:124 -msgid "" -"The deletion process removes **user accounts and associated tickets only**." +#: ../settings/security/third-party/saml.rst:175 +msgid "Make sure the certificate is:" msgstr "" -#: ../system/data-privacy.rst:126 -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." +#: ../settings/security/third-party/saml.rst:177 +msgid "already valid and not yet expired" msgstr "" -#: ../system/data-privacy.rst:137 -msgid "I deleted an user and can still see a message they sent!" +#: ../settings/security/third-party/saml.rst:178 +msgid "no CA certificate" msgstr "" -#: ../system/data-privacy.rst:133 -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." +#: ../settings/security/third-party/saml.rst:179 +msgid "valid for signing and encrypting" msgstr "" -#: ../system/data-privacy.rst:141 -msgid "I removed a customer, now my reporting is off!" +#: ../settings/security/third-party/saml.rst:185 +msgid "Private key (PEM)" msgstr "" -#: ../system/data-privacy.rst:140 +#: ../settings/security/third-party/saml.rst:182 msgid "" -"When removing users and their tickets, all references are removed. This also " -"affects e.g. Reporting - these information are lost." +"Paste the private key of your Zammad SAML client here, if you want to sign " +"the requests." msgstr "" -#: ../system/data-privacy.rst:145 -msgid "How long does Zammad store created tasks?" +#: ../settings/security/third-party/saml.rst:185 +msgid "Make sure the key is an RSA key with a length of at least 2048 bits." msgstr "" -#: ../system/data-privacy.rst:144 -msgid "" -"Please see the on-premise data section of the :docs:`data privacy ` chapter." +#: ../settings/security/third-party/saml.rst:188 +msgid "Private key secret" msgstr "" -#: ../system/data-privacy.rst:150 -msgid "What about re-assigned tickets? I want to delete them, too." +#: ../settings/security/third-party/saml.rst:188 +msgid "If your private key is secured with a secret, you can provide it here." msgstr "" -#: ../system/data-privacy.rst:148 -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." +#: ../settings/security/third-party/saml.rst:192 +msgid "Your callback URL" msgstr "" -#: ../system/data-privacy.rst:154 -msgid "Why are there so many deletion task entries, I didn't create them!" +#: ../settings/security/third-party/saml.rst:191 +msgid "" +"This URL is needed for your IdP configuration so it knows where to redirect " +"to after successful authentication." msgstr "" -#: ../system/data-privacy.rst:153 +#: ../settings/security/third-party/saml.rst:194 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." +"After saving your input by clicking on the \"Submit\" button, Zammad " +"verifies the provided keys/certificates (e.g. if they are valid for signing/" +"encrypting and if they aren't expired)." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:2 -msgid "Admin Panel Reference" +#: ../settings/security/third-party/saml.rst:199 +msgid "" +"See :ref:`automatic account linking ` for details " +"on how to link existing Zammad accounts to IdP accounts." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:None -msgid "Screenshot of Checkmk settings overview" +#: ../settings/security/third-party/saml.rst:205 +msgid "Automatic account linking doesn't work" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:12 +#: ../settings/security/third-party/saml.rst:206 msgid "" -"Which :doc:`group ` should Checkmk tickets be assigned " -"to as a default (*i.e.,* when none is specified)?" +"Have you double-checked your IdP's user attribute mapping configuration?" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:15 -msgid "(Applies to :ref:`API alerts ` only.)" +#: ../settings/security/third-party/twitter.rst:4 +msgid "" +"It is possible to create a quick login for your helpdesk via Twitter. To do " +"so, you need to follow these steps:" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:21 -msgid "Auto close" +#: ../settings/security/third-party/twitter.rst:8 +msgid "Register Twitter App" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:18 -msgid "" -"Should Zammad automatically close tickets if a service has recovered on its " -"own?" +#: ../settings/security/third-party/twitter.rst:10 +msgid "Go to https://dev.twitter.com/apps and login with your account." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:21 -msgid "(Agents will receive notifications for such closures as appropriate.)" +#: ../settings/security/third-party/twitter.rst:15 +msgid "Click on \"Create App\"" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:30 -msgid "Auto-close state" +#: ../settings/security/third-party/twitter.rst:None +msgid "new app page" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:24 -msgid "What ticket state should be applied when “auto-closing” a ticket?" +#: ../settings/security/third-party/twitter.rst:20 +msgid "" +"Enter app settings. As \"Callback URL\" you need to enter ``https://" +"zammad_host/api/v1/external_credentials/twitter/callback``. You need to " +"replace ``zammad_host`` with the domain of your Zammad system." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:26 +#: ../settings/security/third-party/twitter.rst:24 msgid "" -"You can choose from the seven built-in ticket states. If these states aren't " -"enough for you, you can :ref:`define a new ticket state ` for this purpose as well. This can be useful for tracking " -"tickets with :doc:`reports `, for example." +"After the app has been created, update the application icon and organization " +"attributes." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:35 -#: ../system/integrations/cti/includes/recent-logs.include.rst:2 -#: ../system/integrations/ldap/index.rst:74 -#: ../system/integrations/pgp/index.rst:106 -msgid "Recent Logs" +#: ../settings/security/third-party/twitter.rst:None +msgid "set permissions to receive and send direct messages" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:None -msgid "Screenshot of Checkmk \"Recent Logs\" section" +#: ../settings/security/third-party/twitter.rst:30 +msgid "" +"Next we need to set ``read, write and access direct messages`` permissions " +"for the app." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:41 -msgid "" -"If you're having trouble getting Zammad and Checkmk to play nicely together, " -"this section can help you troubleshoot." +#: ../settings/security/third-party/twitter.rst:None +msgid "click on Keys & Access Token, note them" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:44 +#: ../settings/security/third-party/twitter.rst:36 msgid "" -"It contains a record of the fifty most recent transactions that Zammad knows " -"about, including each one's request/response details and return status." +"Go to \"Keys and Access Token\" tab and note the \"Consumer Key\" and " +"\"Consumer Secret\"." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:2 -msgid "API Reference" +#: ../settings/security/third-party/twitter.rst:40 +msgid "Configure Zammad as Twitter App" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:4 +#: ../settings/security/third-party/twitter.rst:42 msgid "" -"For most users, :ref:`the sample scripts from the Setup Guide ` will do the job just fine. But if you want more fine-grained control" -"—for instance, to create high- and low-priority tickets for different types " -"of system events—then you'll have to customize the data those scripts send " -"to Zammad." +"Go to \"Admin > Security > Twitter > Third Party Applications > Twitter\" " +"Section." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:15 -msgid "" -"This custom script will automatically set all tickets it creates to **high " -"priority** and **assign them to charlie@chrispresso.com**." +#: ../settings/security/third-party/twitter.rst:None +msgid "Admin > Security > Third Party Applications" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:32 -msgid "How Does it Work?" +#: ../settings/security/third-party/twitter.rst:48 +msgid "" +"Fill in the \"Twitter Key\" and the \"Twitter Secret\" and click the " +"\"Submit\" button." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:34 +#: ../settings/security/third-party/twitter.rst:51 msgid "" -"There are two kinds of data you can pass to the API, both in the form of key-" -"value pairs:" +"Now you can link accounts via \"Avatar > Profile > Link Accounts\" or login " +"via Zammad login page." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:44 -msgid "Checkmk parameters" +#: ../settings/security/two-factor.rst:11 +msgid "Two-factor Authentication Methods" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:38 -msgid "" -"are required, and make up the **contents** of the resulting tickets/" -"articles. They also determine whether an event creates a new ticket or " -"updates/closes an existing one." +#: ../settings/security/two-factor.rst:2 +msgid "Two-Factor Authentication" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:42 +#: ../settings/security/two-factor.rst:4 msgid "" -"These are the only values used in the sample scripts. **Use them as-is**; " -"technically, they can be customized, but it's hard to imagine a good reason " -"for it." +"Two-factor authentication (2FA) enhances the security of Zammad accounts by " +"adding an extra layer of verification beyond a password. It requires users " +"to provide two different types of authentication factors, typically " +"something they know (like a password) and something they possess (like a " +"mobile device or a security token), to ensure that only authorized " +"individuals can access the account." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:52 -msgid "Ticket attributes" +#: ../settings/security/two-factor.rst:19 +msgid "Enable Recovery Codes" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:47 +#: ../settings/security/two-factor.rst:21 msgid "" -"are optional, and can be used to **adjust settings** on newly created " -"tickets (*e.g.,* set the owner, group, priority, or state)." +"Recovery codes are one-time use security codes that can be used by the user " +"if they lose access to their other two-factor authentication methods. They " +"cannot be used on their own, they can only be activated if at least one two-" +"factor authentication method is enabled." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:50 -msgid "" -"If you want to customize your Checkmk alert script, do it with these. Simply " -"add an extra “form” option for each one (``-F \"key=value\"``) to your " -"script's ``curl`` command line, as in the example above." +#: ../settings/security/two-factor.rst:None +msgid "Enable Recovery Codes Setting" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:54 -msgid "💡 **It's just an API endpoint!**" +#: ../settings/security/two-factor.rst:30 +msgid "" +"Recovery codes can only be used as a backup method. If enabled, they will be " +"automatically generated for the user once they set up their initial two-" +"factor authentication method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:56 +#: ../settings/security/two-factor.rst:34 msgid "" -"When using Checkmk integration, messages need to be formatted in a certain " -"way, but that *doesn't mean the messages actually have to come from Checkmk*." +"The user will be asked to print out or save the generated recovery codes in " +"a safe place. Once used, a recovery code cannot be reused." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:59 +#: ../settings/security/two-factor.rst:37 msgid "" -"If you use another monitoring tool that's not officially supported by " -"Zammad, there's probably a way to make it work with your Checkmk callback " -"URL." +"Users will also have an option to regenerate their recovery codes at any " +"time, which invalidates already existing recovery codes and provides them " +"with a list of fresh codes." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:63 -msgid "Checkmk Parameters" +#: ../settings/security/two-factor.rst:41 +msgid "" +"After you enable this setting, when the user completes a setup of their " +"initial two-factor authentication method, they will be presented with a list " +"of recovery codes and instructed to save them for later use." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:65 -msgid "" -"When a notification is received, Zammad creates a new article containing the " -"details of the event that triggered it:" +#: ../settings/security/two-factor.rst:None +msgid "Recovery Codes Generation Modal Dialog" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:None -msgid "Checkmk article body" +#: ../settings/security/two-factor.rst:50 +msgid "Enforce the Set Up of the Two-Factor Authentication" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:72 +#: ../settings/security/two-factor.rst:52 msgid "" -"These details come from the fields listed below, which correspond to " -"parameters provided by Checkmk (``$NOTIFY_*``)." +"In case you wish to require your users to set up at least one two-factor " +"authentication method for their account, you can do this by selecting " +"specific user roles the requirement applies to in **Enforced for user " +"roles** setting. Of course you must have at least one two-factor " +"authentication method enabled for this setting to take effect." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:75 -msgid "**Required fields are marked with an asterisk (\\*).**" +#: ../settings/security/two-factor.rst:None +msgid "Enforced for User Roles Setting" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:79 -msgid "event_id\\*" +#: ../settings/security/two-factor.rst:62 +msgid "" +"After you change this setting, if the user has one of the selected roles on " +"their account, they will be forced to set up the two-factor authentication " +"upon next sign in or application reload." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:78 +#: ../settings/security/two-factor.rst:66 msgid "" -"A unique ID for the system event. (``$NOTIFY_SERVICEPROBLEMID`` / " -"``$NOTIFY_HOSTPROBLEMID``)" +"A modal dialog with instructions will be shown, and they will not be able to " +"do any work before they set up at least one two-factor method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:86 -msgid "host\\*" +#: ../settings/security/two-factor.rst:None +msgid "Modal Dialog for Enforcing Two-Factor Authentication Set Up" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:82 +#: ../settings/security/two-factor.rst:74 +msgid "Reset Two-Factor Authentication for a Specific User" +msgstr "" + +#: ../settings/security/two-factor.rst:76 msgid "" -"The hostname of the system that the event originated from. " -"(``$NOTIFY_HOSTNAME``)" +"In case an user isn't able to login anymore because of an inaccessible " +"second factor, you can reset the user's 2FA method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:85 +#: ../settings/security/two-factor.rst:79 msgid "" -"Used to determine if a new event belongs to an existing ticket. Also used in " -"the subject line of the resulting article (“ is ”)." +"To do this, go to the user management and search for the relevant user. " +"After you found the account, click the button in the action column and " +"select \"Manage Two-Factor Authentication\":" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:96 -msgid "service" +#: ../settings/security/two-factor.rst:None +msgid "Context menu in action column in user management" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:89 +#: ../settings/security/two-factor.rst:87 msgid "" -"The name of the service that the event originated from. " -"(``$NOTIFY_SERVICEDESC``)" +"After selecting this, you can see a dialog where you can either reset one " +"2FA method or reset all of the user's 2FA methods:" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:92 -msgid "Used to determine if a new event belongs to an existing ticket." +#: ../settings/security/two-factor.rst:None +msgid "Dialog for resetting user's 2FA method" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:94 -#: ../system/integrations/checkmk/api-reference.rst:110 -msgid "Displayed as ``-`` when omitted." +#: ../settings/security/two-factor.rst:94 +msgid "" +"Choose the fitting one, click on the corresponding \"Remove ...\" button and " +"confirm your action. The user now has to setup a new 2FA method, depending " +"on your 2FA configuration." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:104 -msgid "state\\*" +#: ../settings/security/two-factor/authenticator-app.rst:2 +msgid "Authenticator App" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:99 +#: ../settings/security/two-factor/authenticator-app.rst:4 msgid "" -"The current state of the service or host in question. " -"(``$NOTIFY_SERVICESTATE`` / ``$NOTIFY_HOSTSTATE``)" +"The authenticator app method is a type of two-factor authentication that " +"uses a mobile application to generate one-time codes for account " +"verification. After setting up the authenticator app on their device, the " +"user links it to their Zammad account." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:102 +#: ../settings/security/two-factor/authenticator-app.rst:12 msgid "" -"Used to detect when a ticket should be auto-closed (*i.e.,* on ``OK``/" -"``UP``). Also used in the subject line of the resulting article (“ is " -"”)." +"When logging in, the user is prompted to enter a time-sensitive code " +"generated by the app, in addition to their password. This code acts as the " +"second factor of authentication, providing an extra layer of security as it " +"changes periodically and is unique to the user's device." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:110 -msgid "text" +#: ../settings/security/two-factor/authenticator-app.rst:None +msgid "Security Code in Google Authenticator App" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:107 +#: ../settings/security/two-factor/authenticator-app.rst:22 msgid "" -"The output of the process that triggered the event. " -"(``$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" +"The app generates codes based on a shared secret key stored securely on both " +"the user's device and the server, ensuring a synchronized and secure " +"authentication process. The method of generating the codes is sometimes also " +"called TOTP (time-based one-time password)." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:121 -msgid "" -"The Object Manager attribute panel displays built-in and custom\n" -"attribute names." +#: ../settings/security/two-factor/authenticator-app.rst:28 +msgid "Enabling the Authenticator App Method" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:121 -msgid "Find a complete list of ticket attributes in the Object Manager." +#: ../settings/security/two-factor/authenticator-app.rst:30 +#: ../settings/security/two-factor/security-keys.rst:28 +msgid "To enable the method, just toggle the switch on in the settings." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:123 -msgid "" -"Ticket attributes are entirely optional, and can be used to customize the " -"tickets that Checkmk creates. (Note that these attributes will be ignored if " -"a new event belongs to an existing ticket.)" +#: ../settings/security/two-factor/authenticator-app.rst:None +msgid "Authenticator App Switch in Settings" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:128 +#: ../settings/security/two-factor/authenticator-app.rst:36 msgid "" -"Why would you want to do this? Maybe you have only one IT guy, and all " -"system monitoring issues should be automatically assigned to him. Or, maybe " -"you're creating multiple notification rules so that database outages take " -"higher priority than disk space warnings." +"Now the users will be able to set up this two-factor authentication method " +"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " +"Once they do, on next sign-in with password, they will be asked to provide " +"an additional security code generated by their mobile device." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:135 -msgid "In most cases, you'll probably want to set one of the following:" +#: ../settings/security/two-factor/security-keys.rst:2 +msgid "Security Keys" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:137 -msgid "group" +#: ../settings/security/two-factor/security-keys.rst:4 +msgid "" +"The security keys method is a type of a two-factor authentication that uses " +"Web Authentication API in the browser for verifying user's identity. The " +"user can register multiple hardware or software security keys with their " +"Zammad account and then they can use it during the sign-in process." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:139 -msgid "state" +#: ../settings/security/two-factor/security-keys.rst:12 +msgid "" +"When logging in, the user is prompted to provide the same security key they " +"registered with their account, in addition to their password. This key acts " +"as the second factor of authentication, providing an extra layer of security." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:140 -msgid "priority" +#: ../settings/security/two-factor/security-keys.rst:None +msgid "Security Key dialog in Safari on macOS" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:142 +#: ../settings/security/two-factor/security-keys.rst:21 msgid "" -"but in practice, you can set almost any attribute, including :doc:`custom " -"ones you created through the Object Manager `." -msgstr "" - -#: ../system/integrations/checkmk/api-reference.rst:145 -msgid "Please note that the following attributes are **not customizable**:" +"The type of the key can range from hardware USB sticks to passkeys stored in " +"a device of user's choice. Which type can be used depends on the browser " +"flavor and the platform of the user." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:147 -msgid "title" +#: ../settings/security/two-factor/security-keys.rst:26 +msgid "Enabling the Security Keys Method" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:148 -msgid "id" +#: ../settings/security/two-factor/security-keys.rst:None +msgid "Security Keys Switch in Settings" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:149 -msgid "ticket number" +#: ../settings/security/two-factor/security-keys.rst:34 +msgid "" +"Now the users will be able to set up this two-factor authentication method " +"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " +"Once they do, on next sign-in with password, they will be asked to provide " +"the same security key they registered during the setup." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:151 -msgid "created_by_id" +#: ../settings/system/system-selfhosted.include.rst:3 +msgid "" +"Below settings are only available to self hosted users. In hosted " +"environments we're handling these settings for you to ensure service " +"stability." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:152 -msgid "updated_by_id" +#: ../settings/system/base.rst:11 +msgid "Fully Qualified Domain Name" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:155 -msgid "Which Values Can Be Set?" +#: ../settings/system/base.rst:7 +msgid "The URL of your Zammad installation." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:157 -msgid "😵 **Invalid values → unpredictable behavior**" +#: ../settings/system/base.rst:9 ../settings/system/base.rst:17 +msgid "This setting is used within :doc:`/misc/variables` and notifications." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:159 -msgid "" -"If you provide a value that Zammad doesn't understand (*e.g.,* ``-F " -"\"priority=high\"``), it's not always clear what will happen. In some cases, " -"a ticket will be created with the default values instead - but in others, it " -"may not be created at all!" +#: ../settings/system/system-base.include.rst:1 +msgid "It is automatically set by the *Getting Started wizard*." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:164 -msgid "So what values does Zammad understand, then? Well, it depends..." +#: ../settings/system/system-base.include.rst:5 +msgid "Changing this setting also changes callback URLs for your channels etc." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:168 -msgid "Use an email address or username:" +#: ../settings/system/system-base.include.rst:6 +msgid "This setting can have negative affects on being able to login." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:190 -msgid "group & priority" +#: ../settings/system/base.rst:19 +msgid "HTTP type" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:175 -msgid "Refer to the dropdown menus in the ticket pane:" +#: ../settings/system/base.rst:14 +msgid "" +"The HTTP type tells your installation how your clients connect. This is " +"relevant for authentication and cookie security." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:0 -msgid "See possible values for certain attributes in the ticket pane." +#: ../settings/system/base.rst:31 +msgid "SystemID" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:187 -msgid "🙅 **Ticket state CANNOT be set this way!**" +#: ../settings/system/base.rst:22 +msgid "" +"This ID is being used within your ticket number. In case you're " +"communicating with another ticket system with similar ticket number schemes " +"this ID greatly reduces the risk of false follow ups." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:189 +#: ../settings/system/base.rst:26 msgid "" -"Why? Because ``-F \"state=...\"`` is already used :ref:`as a Checkmk " -"parameter `." +"The SystemID is randomly selected upon installation of Zammad (``1-99``)." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:222 -msgid "Everything Else" +#: ../settings/system/base.rst:30 +msgid "" +"**Do not** change this setting in a productive system! Your Zammad " +"installation may no longer recognize old ticket number based follow ups upon " +"change!" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:193 -msgid "" -"To set any other attributes, it helps to know your way around the :docs:" -"`rails console `. Valid values are those that you can " -"set with a string:" +#: ../settings/system/frontend.rst:2 +msgid "Frontend" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:218 -msgid "These values can then be passed directly to the API:" +#: ../settings/system/frontend.rst:22 +msgid "Core Workflow Ajax Mode" msgstr "" -#: ../system/integrations/checkmk/index.rst:16 -msgid "How does it work?" +#: ../settings/system/frontend.rst:6 +msgid "" +"This setting allows administrators to enforce :doc:`/system/core-workflows` " +"to use Ajax-Calls instead of web sockets. You'll usually only need this if " +"you experience serious issues as noted below." msgstr "" -#: ../system/integrations/checkmk/index.rst:2 -msgid "Checkmk" +#: ../settings/system/frontend.rst:10 +msgid "**🤓 Possible (technical) reasons**" msgstr "" -#: ../system/integrations/checkmk/index.rst:4 +#: ../settings/system/frontend.rst:12 msgid "" -"`Checkmk `_ is a powerful IT monitoring tool that can " -"send real-time status alerts to Zammad via email or REST API. Set these " -"alerts up in Checkmk, and Zammad will automatically create, update, and " -"close tickets based on the health of your system:" +"In some cases, your network structure (e.g. firewalls, proxies) may " +"disconnect long web socket connections. This leads to select fields staying " +"empty (e.g. owner selection *after* selecting your group) or fields not " +"shown / hidden (e.g. when switching to or from pending states, the \"pending " +"till\" field not showing / hiding)." msgstr "" -#: ../system/integrations/checkmk/index.rst:14 -msgid "Screenshot of ticket created by Checkmk notifications" +#: ../settings/system/frontend.rst:18 +msgid "" +"Please keep in mind that the Ajax fallback may cause serious pressure on " +"your application server. If you have the choice stick to web sockets." msgstr "" -#: ../system/integrations/checkmk/index.rst:14 -msgid "Multiple alerts, same ticket." +#: ../settings/system/frontend.rst:22 +msgid "Default: ``no`` (inactive)" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:2 -msgid "Setup Guide" +#: ../settings/system/frontend.rst:53 +msgid "Show calendar weeks in the picker of date/datetime fields" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:4 +#: ../settings/system/frontend.rst:25 msgid "" -"Whenever the Checkmk integration is enabled, Zammad listens for messages on " -"its API and over email. As long as those messages follow the required " -"format, Zammad will create new tickets (or find and update existing ones) " -"based on the message contents." +"With this setting you can instruct Zammad to provide week number display " +"globally for all users. Calendar with week number display are usually used " +"in business sectors and may not be relevant for everyone." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:10 +#: ../settings/system/frontend.rst:29 msgid "" -"That means that “setting up Checkmk integration” is simply a matter of " -"**adding configuration to your Checkmk site**: telling it when to send these " -"messages and what to say. To do that, you'll need to create a new " -"**notification rule** (see `Checkmk's official docs `_ for help with that)." +"This setting affects *all areas* - you'll also see week numbers in the admin " +"panel for e.g. triggers and macros." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:17 -msgid "" -"As part of this new rule, you'll have to choose a **notification method** " -"(*i.e.,* a script to execute whenever the rule is triggered). This script " -"will be written by you (samples below), and contain the logic for sending " -"API/email messages to Zammad:" +#: ../settings/system/frontend.rst:32 +msgid "Default: ``no`` (not shown)" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:26 -msgid "Checkmk \"New Rule\" dialog" +#: ../settings/system/frontend.rst:53 +msgid "Here's the difference:" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:26 -msgid "" -"Find your custom scripts in the Checkmk WATO under **Notifications > New " -"Rule > Notification Method**." +#: ../settings/system/frontend.rst:0 +msgid "Screenshot showing Zammad's date picker (in the default way)" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:29 -msgid "" -"Once you're done setting up your new rule, you're all set! New tickets " -"should start coming in and auto-updating any time your rule is triggered." +#: ../settings/system/frontend.rst:41 +msgid "Set to ``no``" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:33 +#: ../settings/system/frontend.rst:0 msgid "" -"(If you need help troubleshooting, be sure to check the :ref:`checkmk-recent-" -"logs`.)" +"Screenshot showing Zammad's date picker with\n" +"week numbers enabled" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:38 -msgid "API Alerts" +#: ../settings/system/frontend.rst:50 +msgid "Set to ``yes``" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:40 +#: ../settings/system/index.rst:4 msgid "" -"To add these scripts in the Checkmk WATO, copy them into your Checkmk " -"installation directory and make them executable. (Be sure to replace the " -"``zammad.example.com`` callback URL with the one found in your admin panel.)" +"For your overview we split each tab within system settings into its own page:" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:60 -msgid "Service notification" +#: ../settings/system/index.rst:16 +msgid "Console Based Settings" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:46 +#: ../settings/system/index.rst:18 msgid "" -"For updates on the status of the software running on your server (*e.g.,* " -"postgres)." +"There's some console based settings we didn't put into the UI. However, you " +"may find them helpful - you can find them in our :docs:`hidden settings ` section." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:75 -msgid "Host notification" +#: ../settings/system/network.rst:2 +msgid "Network" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:63 -msgid "For updates on the status of the server itself." +#: ../settings/system/network.rst:8 +msgid "" +"The proxy settings can only be saved after successfully testing the proxy " +"connection." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:77 -msgid "🤔 **What's with all the env vars?**" +#: ../settings/system/network.rst:15 +msgid "Proxy Address." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:79 +#: ../settings/system/network.rst:12 msgid "" -"Whenever Checkmk runs these scripts, it needs to provide some information " -"about the event that triggered the notification. This information is passed " -"in the form of these ``$NOTIFY_*`` environment variables." +"Allows you to provide a proxy server if needed. This is relevant for network " +"communication by Zammad." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:85 -msgid "" -"You can specify additional parameters to pass to the script when you're " -"setting up your notification rule, but the ones you see here are all " -"provided by default." +#: ../settings/system/network.rst:15 +msgid "It **does not** affect the update process or Elasticsearch." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:90 -msgid "Email Alerts" +#: ../settings/system/network.rst:18 +msgid "Username for proxy connection." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:94 +#: ../settings/system/network.rst:18 msgid "" -"🐞 **There are known bugs** in Zammad's processing of email from Checkmk. " -"This section will be completed once they have been resolved. (Learn more at " -"GitHub issues `#2377 `_ & " -"`#2180 `_.)" +"If your proxy server requires authentication, provide the username here." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:100 -msgid "In the meantime, we encourage you to set up API alerts instead." +#: ../settings/system/network.rst:21 +msgid "Password for proxy connection." msgstr "" -#: ../system/integrations/clearbit.rst:2 -msgid "Clearbit" +#: ../settings/system/network.rst:21 +msgid "" +"If your proxy server requires authentication, provide the password here." msgstr "" -#: ../system/integrations/clearbit.rst:4 +#: ../settings/system/network.rst:26 +msgid "No proxy for the following hosts." +msgstr "" + +#: ../settings/system/network.rst:24 msgid "" -"With our Clearbit integration, you can easily enrich the information " -"provided by Zammad. If the customers or agents email address is known to " -"Clearbit, it will share all information it has regarding the user with " -"Zammad. Those information can include the following:" +"Exception list for hosts you can't or don't want to reach via proxy server." msgstr "" -#: ../system/integrations/clearbit.rst:9 -msgid "Avatar" +#: ../settings/system/network.rst:27 +msgid "Default: ``localhost,127.0.0.0,::1``" msgstr "" -#: ../system/integrations/clearbit.rst:10 -msgid "Address information" +#: ../settings/system/services.rst:2 +msgid "Services" msgstr "" -#: ../system/integrations/clearbit.rst:11 -msgid "Website information" +#: ../settings/system/services.rst:10 +msgid "Image Service" msgstr "" -#: ../system/integrations/clearbit.rst:12 -msgid "A BIO (as Note by default)" +#: ../settings/system/services.rst:5 +msgid "Defines the backend for user and organization image lookups." msgstr "" -#: ../system/integrations/clearbit.rst:14 -msgid "" -"If needed, you can add further custom objects and add mappings to them, so " -"the Clearbit information can be filled within the database. In general you " -"can get any information from Clearbit, as long as you have a mapping to an " -"Zammad object." +#: ../settings/system/services.rst:7 +msgid "Default: ``Zammad Image Service`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:21 +#: ../settings/system/services.rst:9 msgid "" -"Clearbit does have a mapping of fields like LDAP and Exchange have, but does " -"not \"win\" against Zammad information. This means that if you have e.g. the " -"last name field filled in already and Clearbit has other information on " -"that, it will not be updated." +"Make sure your on premise installation has ``HTTPS`` access to ``images." +"zammad.com``." msgstr "" -#: ../system/integrations/clearbit.rst:26 -msgid "" -"However: If let's say the last name has been set by Clearbit and Zammad " -"notices that the last name on the Clearbit source has changed, Zammad will " -"also update this value." +#: ../settings/system/services.rst:18 +msgid "Geo Calendar Service" msgstr "" -#: ../system/integrations/clearbit.rst:33 +#: ../settings/system/services.rst:13 msgid "" -"The configuration of Clearbit is really easy and done fast! Just login to " -"your Clearbit-Account, go to \"API\" and copy the secret-API-Key." +"Defines the backend for geo calendar lookups. Used for initial calendar " +"setup." msgstr "" -#: ../system/integrations/clearbit.rst:38 -msgid "" -"Now change to your Zammad instance, go to Integrations (System) -> Clearbit " -"in the admin panel. Paste your API-Key into the API-Key-Field and decide if " -"Zammad should create unknown Organizations automatically, if the user does " -"not have one yet (and Clearbit knows it). The shared option decides if the " -"new organizations Zammad creates with Clearbit should be shared ones." +#: ../settings/system/services.rst:16 +msgid "Default: ``Zammad GeoCalendar Service`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:47 +#: ../settings/system/services.include.rst:2 msgid "" -"If you're unsure what option to choose, better stick with \"no\". You can " -"also learn more about :doc:`/manage/organizations/index`." +"Make sure your on premise installation has ``HTTPS`` access to ``geo.zammad." +"com``." msgstr "" -#: ../system/integrations/clearbit.rst:52 -msgid "" -"The Mapping option works similar to the mapping within the Exchange and LDAP " -"sync. You can add further mappings for e.g. custom fields if you need more " -"information that Clearbit can provide." +#: ../settings/system/services.rst:26 +msgid "Geo IP Service" msgstr "" -#: ../system/integrations/clearbit.rst:58 +#: ../settings/system/services.rst:21 msgid "" -"If you want to add more Clearbit fields and want to learn more about " -"available fields on their API, you can take a look at their `API " -"documentation `_." +"Defines the backend for geo IP lookups. Shows also location of an IP address " +"if an IP address is shown." msgstr "" -#: ../system/integrations/clearbit.rst:62 -msgid "" -"If you're happy with the above chosen Settings and your mapping, just save " -"the changes and enable Clearbit integration. Zammad will now start polling " -"the Clearbit API as users contact you." +#: ../settings/system/services.rst:24 +msgid "Default: ``Zammad GeoIP Service`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:68 -msgid "" -"Zammad does not synchronize with Clearbit on a regular basis, but on demand " -"if needed. This saves API calls." +#: ../settings/system/services.rst:32 +msgid "Geo Location Service" msgstr "" -#: ../system/integrations/clearbit.rst:73 +#: ../settings/system/services.rst:29 msgid "" -"Below the Settings and Mappings, you'll find our Integration log. You can " -"see what requests Zammad sent to Clearbit and also the APIs Response." +"Defines the backend for geo location lookups to store geo locations for " +"addresses." msgstr "" -#: ../system/integrations/clearbit.rst:78 +#: ../settings/system/services.rst:32 msgid "" -"By the way, you can also view the API log on the Clearbit website - the " -"information seen is basically the same." -msgstr "" - -#: ../system/integrations/clearbit.rst:84 -msgid "Example When Adding a User" +"Default: ``OpenStreetMap (ODbL 1.0, http://osm.org/copyright)`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:86 +#: ../settings/system/services.rst:36 msgid "" -"To show you how fast information is added, we added a small Screencast " -"below. This shows the creation of the User Alex from Clearbit. As we already " -"set the last name of Alex to \"X\", Zammad did not update it. What Zammad " -"did was to add further information it received from Clearbit." +"You can find a detailed privacy information on what we store for how long on " +"our :docs:`Privacy Appendix ` inside of our System " +"Documentation." msgstr "" -#: ../system/integrations/cti/generic.rst:2 -msgid "CTI (generic)" +#: ../settings/system/storage.rst:2 +msgid "Storage" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:1 +#: ../settings/system/storage.rst:6 msgid "" -"This integration enables Zammad to provide a caller log to your agents. With " -"this your agents can greet your customers by their name and are supported by " -"Zammad with automatically opening a new ticket dialog or the user profile." +"Here you can define where Zammad stores attachments for tickets and the " +"knowledge base. By default, we're writing to the ``Database`` - you can " +"switch to ``Filesystem`` or ``Simple Storage (S3)`` at any time. In this " +"case please have a look on the following instructions." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:6 +#: ../settings/system/storage.rst:11 msgid "" -"Click the toggle next to the heading to activate or deactivate this " -"integration." +"If you have a busy Zammad instance, we strongly encourage you to use " +"filesystem storage instead of \"Database\". This will greatly improve system " +"performance (de-crease database load and size)." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:9 -msgid "" -"If you want to learn more on how your agents can use this function, please " -"refer the :user-docs:`user documentation `." +#: ../settings/system/storage.rst:19 +msgid "Database" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:14 +#: ../settings/system/storage.rst:17 msgid "" -"Automatically opening new ticket dialogues or user profiles requires agent " -"to extension mapping - see more below." -msgstr "" - -#: ../system/integrations/cti/includes/introduction.include.rst:20 -msgid "Please note the following limitations to reduce confusion later on:" +"This is the default storage method. The attachments are stored directly in " +"the database. If your Zammad instance grows, we recommend one of the other " +"methods to maintain performance." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:22 -msgid "CTI integrations provide caller log functions only." +#: ../settings/system/storage.rst:38 +msgid "Filesystem" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:23 +#: ../settings/system/storage.rst:22 msgid "" -"This integration does not provide any VoIP functionalities; you can't make " -"phone calls from within Zammad." +"This storage method is recommended for all Zammad instances, especially for " +"those with a higher load. If you choose filesystem, your files are written " +"to ``/opt/zammad/storage/``." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:25 +#: ../settings/system/storage.rst:26 msgid "" -"If your browser supports ``tel``-URLs, you can click on phone numbers for " -"automatic dialing. This requires additional software / configuration on your " -"agent's computers." +"Moving attachments from \"Database\" to \"Filesystem\" can be run during " +"production use. However, you should consider your framework conditions (e.g. " +"bandwidth, system load in production) to define the right moment." msgstr "" -#: ../system/integrations/cti/generic.rst:9 -#: ../system/integrations/cti/placetel.rst:14 -#: ../system/integrations/cti/sipgate.rst:14 -msgid "Please provide the following requirements:" +#: ../settings/system/storage.rst:32 +msgid "**You noticed slow updates of Zammad?**" msgstr "" -#: ../system/integrations/cti/generic.rst:11 +#: ../settings/system/storage.rst:34 msgid "" -"A telephone system that supports webhooks (outbound) (best option are those " -"that allow customizing the calls)." +"While Zammad is beeing updated, it enforces a recursive \"change " +"owner\" (chown) for this directory. For instances with many files this can " +"be time consuming. To mitigate that you can move your files and create a " +"symlink in ``/opt/zammad/storage/`` to the new directory. Of course you have " +"to make sure on your own that the permissions are always correct." msgstr "" -#: ../system/integrations/cti/generic.rst:13 -msgid "A unique Call-ID during the call session." +#: ../settings/system/storage.rst:95 +msgid "Simple Storage (S3)" msgstr "" -#: ../system/integrations/cti/generic.rst:14 -msgid "Call event data (both numbers and direction)." +#: ../settings/system/storage.rst:41 +msgid "" +"To use the Simple Storage (S3), you have to provide some settings, which " +"can't be accessed in the UI (see instructions below)." msgstr "" -#: ../system/integrations/cti/generic.rst:15 -msgid "Your Zammad instance must be reachable for your telephony system." +#: ../settings/system/storage.rst:44 +msgid "" +"⚠️ Please note that the current implementation is in its early stages and can " +"be modified in the future." msgstr "" -#: ../system/integrations/cti/generic.rst:17 +#: ../settings/system/storage.rst:47 msgid "" -"If you want to learn more on what kind of requests are supported by Zammad " -"and what it expects, please consult our :docs:`CTI-API documentation `." +"The prerequisite is to have access to a S3-compatible storage and to have " +"all necessary parameters available (which depends on your storage provider; " +"if in doubt, please ask there for help)." msgstr "" -#: ../system/integrations/cti/generic.rst:22 -#: ../system/integrations/cti/placetel.rst:27 -#: ../system/integrations/cti/sipgate.rst:30 -msgid "Available Settings" +#: ../settings/system/storage.rst:51 +msgid "Steps to configure S3:" msgstr "" -#: ../system/integrations/cti/generic.rst:29 -#: ../system/integrations/cti/placetel.rst:41 -#: ../system/integrations/cti/sipgate.rst:40 -msgid "Endpoint Settings" +#: ../settings/system/storage.rst:53 +msgid "" +"Copy ``config/zammad/storage.yml.dist`` to ``config/zammad/storage.yml``" msgstr "" -#: ../system/integrations/cti/generic.rst:25 -msgid "" -"Zammad will list your generic CTI endpoint here. It contains a unique token " -"so ensure to keep this URL save." +#: ../settings/system/storage.rst:54 +msgid "Edit the copied file in one of the following ways:" msgstr "" -#: ../system/integrations/cti/generic.rst:28 +#: ../settings/system/storage.rst:56 msgid "" -"You'll need this endpoint for your PBX to talk to Zammad, see :docs:`CTI-API " -"documentation `." +"Either provide your S3 configuration with one attribute per line like in the " +"upper area of the file" msgstr "" -#: ../system/integrations/cti/includes/important-dont-forget-saving.include.rst:3 +#: ../settings/system/storage.rst:58 msgid "" -"All following options **do not save automatically**. Always use the Save " -"button on the lower end of the integration page!" +"Or provide your S3 configuration as an URL (which you can find at the end of " +"the file). Note: you can also provide this URL as environment variable (:" +"docs:`see system documentation `) without using this yml-file." msgstr "" -#: ../system/integrations/cti/generic.rst:43 -#: ../system/integrations/cti/placetel.rst:49 -#: ../system/integrations/cti/sipgate.rst:52 -msgid "Call Settings" +#: ../settings/system/storage.rst:62 +msgid "" +"We recommend the deletion of the not used configuration style to avoid " +"inconsistencies." msgstr "" -#: ../system/integrations/cti/generic.rst:39 -#: ../system/integrations/cti/placetel.rst:49 -#: ../system/integrations/cti/sipgate.rst:37 -#: ../system/integrations/cti/sipgate.rst:50 -msgid "Inbound" +#: ../settings/system/storage.rst:65 +msgid "Restart Zammad so the config file / environment variable is loaded" msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:1 +#: ../settings/system/storage.rst:66 msgid "" -"This option allows you to block specific incoming caller IDs. It allows you " -"to temporarily reject e.g. spam callers without having to contact providers " -"or PBX administrators." +"Set the \"Storage Method\" in Zammad to ``Simple Storage (S3)`` in Settings " +"> System > Storage and click on \"Submit\". After that, Zammad checks your " +"configuration and the connection to the service and will raise an error " +"message if something is wrong." msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:11 -msgid "Caller ID to block" +#: ../settings/system/storage.rst:72 +msgid "A very simple storage configuration could look like this:" msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 -msgid "Provide caller IDs to block in ``E.164`` format." +#: ../settings/system/storage.rst:85 +msgid "" +"Before setting the storage method to ``Simple Storage (S3)`` (step 4), " +"please make sure to have a working setup." msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:8 +#: ../settings/system/storage.rst:88 msgid "" -"Your telephony system has to support this function. Zammad will send a " -"``reject`` response which will cause your telephony system to hang up the " -"call. To callers this usually will feel like the line is busy." +"You can verify this by running ``rails r 'Rails.logger = Logger.new(STDOUT); " +"pp Store::Provider::S3.ping?'`` in your Zammad directory. If everything is " +"fine, you should see ``true``, else you should see ``false`` and a simple " +"error message." msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:14 +#: ../settings/system/storage.rst:93 msgid "" -"Provide a meaningful note for your fellow administrators to remind yourself " -"why you've chosen to block the number." +"If you installed Zammad through a package manager (rather than from source), " +"replace ``rails r`` with ``zammad run rails r`` above. To learn more, see :" +"docs:`Administration via Console `." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 -#: ../system/integrations/cti/includes/outbound-calls.include.rst:17 -#: ../system/integrations/cti/sipgate.rst:40 -msgid "Outbound" +#: ../settings/ticket.rst:4 +msgid "" +"Here you can adjust general ticket settings. Additional ones for the ticket " +"composer interface can be found in the :doc:`/misc/composer`." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:1 -msgid "" -"In many cases you may want to use a different caller ID depending on the " -"destination you're calling. This may apply due to specific connection rates " -"to other countries or because you want your customer to feel you're calling " -"from the same country." +#: ../settings/ticket.rst:11 +msgid "Ticket Hook (default: ``Ticket#``)" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:6 -msgid "This option expects ``E.164`` number formats." +#: ../settings/ticket.rst:11 +msgid "The identifier for a ticket; *e.g.,* Ticket#, Call#, MyTicket#." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 -msgid "Destination caller ID" +#: ../settings/ticket.rst:38 +msgid "Ticket Hook Position (default: ``right``)" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:5 -msgid "The caller ID or number you're trying to call." +#: ../settings/ticket.rst:14 +msgid "" +"With this setting you can decide (if) where to insert the ticket number." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:7 -msgid "You can use wildcards for e.g. country specific outbound numbers like:" +#: ../settings/ticket.rst:20 +msgid "*Right*" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:9 -msgid "``49*`` for Germany" +#: ../settings/ticket.rst:17 +msgid "" +"This setting will add the ticket reference on the right site of the subject." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:10 -msgid "``4930*`` for Berlin / Germany landlines" +#: ../settings/ticket.rst:20 +msgid "Example: ``Some Subject [Ticket#12345]``" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 -msgid "``33*`` for France" +#: ../settings/ticket.rst:26 +msgid "*Left*" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:15 -msgid "Set Outbound caller ID" +#: ../settings/ticket.rst:23 +msgid "" +"This setting will add the ticket reference on the left site of the subject." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:14 -msgid "" -"The outbound caller ID to set (the number your customer sees on his display) " -"in ``E.164`` number format." +#: ../settings/ticket.rst:26 +msgid "Example: ``[Ticket#12345] Some Subject``" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 -msgid "Provide a short description for fellow administrators." +#: ../settings/ticket.rst:29 +msgid "*None*" msgstr "" -#: ../system/integrations/cti/includes/generic-cti-support-note.includes.rst:3 -msgid "" -"This option requires your PBX to send a specific request to Zammad *before " -"dialing*. Please consult the :docs:`CTI API ` in case " -"you're not sure." +#: ../settings/ticket.rst:29 +msgid "This will completely remove ticket references from the subject." msgstr "" -#: ../system/integrations/cti/generic.rst:52 -#: ../system/integrations/cti/placetel.rst:54 -#: ../system/integrations/cti/sipgate.rst:59 -msgid "Other Settings" +#: ../settings/ticket.rst:33 +msgid "" +"Please ensure to take a look at :doc:`/channels/email/settings` within the " +"email channel to ensure you have at least one reference that helps Zammad to " +"assign follow-ups correctly." msgstr "" -#: ../system/integrations/cti/includes/other-settings-intro.include.rst:1 +#: ../settings/ticket.rst:37 msgid "" -"Below you can find all available additional settings for this CTI " -"integration. For your overview we're sorting them by appearance and " -"reference their description first." +"Disabling this and not setting up any further follow up search will lead to " +"unexpected results!" msgstr "" -#: ../system/integrations/cti/includes/default-caller-id.include.rst:2 -#: ../system/integrations/cti/includes/default-caller-id.include.rst:1 -msgid "Default caller ID for outbound calls" +#: ../settings/ticket.rst:65 +msgid "" +"Ticket Last Contact Behaviour (default: ``Use the start time of the last " +"customer thread (which may consist of multiple articles).``)" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:16 -#: ../system/integrations/cti/includes/records-caller-log.include.rst:15 -msgid "Shown records in caller log" +#: ../settings/ticket.rst:41 +msgid "" +"This setting changes the way Zammad updates the ``Last Contact`` value of a " +"ticket. This is fairly important for overviews and what you expect upon " +"ticket updates of a customer." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:2 +#: ../settings/ticket.rst:52 msgid "" -"Allows you to set the number of shown caller log entries for all users. You " -"can choose from the following values:" +"Use the start time of the last customer thread (which may consist of " +"multiple articles)." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:5 -msgid "60 (default)" +#: ../settings/ticket.rst:46 +msgid "" +"If this option is chosen, Zammad will update the last updated value just " +"once if a customer replies. After that, Zammad will wait for an agent to " +"react." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:6 -msgid "120" +#: ../settings/ticket.rst:50 +msgid "" +"This comes in handy if you want to work tickets in the order of their first " +"update. This will not change ticket orders if customers decide to \"bump\" " +"the ticket affected." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:7 -msgid "180" +#: ../settings/ticket.rst:57 +msgid "Use the time of the very last customer article." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:8 -msgid "240" +#: ../settings/ticket.rst:55 +msgid "" +"When setting this option, Zammad will always update the last updated value. " +"This means that if ordering by ``Last Update``, ticket orders will change if " +"customers \"bump\" the ticket." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:9 -msgid "300" +#: ../settings/ticket.rst:64 +msgid "Last contact value used on :doc:`/manage/overviews`" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:11 -msgid "**🥵 Potential performance issue**" +#: ../settings/ticket.rst:65 +msgid "Last contact value used on :doc:`/manage/trigger`" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:13 +#: ../settings/ticket.rst:88 msgid "" -"Setting this setting higher than 60 may cause serious performance issues on " -"very busy instances. Keep in mind that this setting causes Zammad to poll " -"and send up to 300 records to *all active agent sessions* in very short time " -"periods." +"Ticket Organization Reassignment (default: ``Update the most recent tickets." +"``)" msgstr "" -#: ../system/integrations/cti/generic.rst:73 -msgid "Caller Log Filter" +#: ../settings/ticket.rst:68 +msgid "" +"This setting changes the way Zammad updates the organization field of the " +"tickets whenever the primary organization of a user is changed." msgstr "" -#: ../system/integrations/cti/generic.rst:55 -msgid "" -"This function allows you to provide call information based on e.g. queues " -"only to agents that really need the information." +#: ../settings/ticket.rst:74 +msgid "Update the most recent tickets." msgstr "" -#: ../system/integrations/cti/generic.rst:58 +#: ../settings/ticket.rst:72 msgid "" -"Why? If you have a team for several countries or departments, you don't want " -"to bug your agents from other departments. Leaving these options empty will " -"fallback to showing everything to everyone." +"If this option is chosen, Zammad will update the 100 most recent tickets " +"where the user is the ticket customer. The ticket organization field will be " +"automatically set to the new primary organization of the user." msgstr "" -#: ../system/integrations/cti/generic.rst:64 -msgid "Destination caller ID or Queue" +#: ../settings/ticket.rst:88 +msgid "Do not update any tickets." msgstr "" -#: ../system/integrations/cti/generic.rst:63 +#: ../settings/ticket.rst:77 msgid "" -"This depends on your PBX and usually is either a queue ID, phone number or " -"extension." +"When choosing this option, Zammad will not update any tickets when the " +"user's primary organization is changed." msgstr "" -#: ../system/integrations/cti/generic.rst:69 -msgid "Agents" +#: ../settings/ticket.rst:80 +msgid "**Use with care!**" msgstr "" -#: ../system/integrations/cti/generic.rst:67 +#: ../settings/ticket.rst:82 msgid "" -"Select the agents that are responsible for the group. These agents will then " -"see caller log entries and call notifications fitting to said queue." +"Using this option may lead to inconsistencies in the system as the ticket " +"organization may become decoupled from the ticket customer." msgstr "" -#: ../system/integrations/cti/generic.rst:0 +#: ../settings/ticket.rst:85 msgid "" -"Screenshot showing the caller log filter table with pre filled sample data" +"However, you may use this option if you wish to maintain :ref:`the shared " +"access ` to the ticket for all organization " +"members of the original organization of the customer." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:6 -msgid "" -"With recent logs Zammad allows you to view the latest calls for the CTI " -"functionality. This usually comes in handy, when you're looking for errors." +#: ../settings/ticket.rst:110 +msgid "Ticket Number Format (default: ``Increment (SystemID.Counter)``)" msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:0 +#: ../settings/ticket.rst:94 msgid "" -"Screenshot showing several incoming requests within Recent logs section." +"This setting defines the way Zammad's ticket number will look. Changing this " +"setting in production will cause follow up detection to fail." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:16 -msgid "I'm just here to clear floats up." +#: ../settings/ticket.rst:102 +msgid "Increment (SystemID.Counter)" msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:20 +#: ../settings/ticket.rst:98 msgid "" -"By clicking on the entry of interest, Zammad will provide more details on " -"the call in question. You'll see the payload it received and also the " -"response that was sent." +"The increment value contains the SystemID (automatically generated during " +"installation) and a increment which counts up with every new Ticket. The " +"increment will automatically get another digit if needed." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:0 -msgid "" -"Screenshot showing detailed information of a specific log entry of recent " -"logs" +#: ../settings/ticket.rst:102 +msgid "Examples: ``1010138``, ``1010139``" msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:31 -msgid "x" +#: ../settings/ticket.rst:110 +msgid "Date (Year.Month.Day.SystemID.Counter)" msgstr "" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 -#: ../system/integrations/cti/includes/troubleshooting.include.rst:9 -msgid "My Phone page stays blank, signalling does work..." +#: ../settings/ticket.rst:105 +msgid "" +"This version of the ticket number is fairly long. However, because it " +"contains the date of ticket creation, it also allows you to see when the " +"ticket has been created. You may feel familiar with this number format if " +"you've worked with OTRS already." msgstr "" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:5 -msgid "" -"If you've made sure that signalling works (check Recent logs) and your " -"Caller Log still stays empty, please ensure that you only configured one CTI " -"integration version. Specifically defining more than one agent mapping on " -"the different integration variants will be the issue." +#: ../settings/ticket.rst:110 +msgid "Examples: ``201206231010138``, ``201206231010139``" msgstr "" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 -msgid "Clear the not needed agent mapping and reload your browser page." +#: ../settings/ticket.rst:137 +msgid "OPTIONS" msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:1 +#: ../settings/ticket.rst:113 msgid "" -"By mapping your agents extension to their existing Zammad users, Zammad can " -"provide a new ticket dialog or open the user profile for the agent that " -"picks up the call." +"The below options allow you to further customize your ticket number. The " +"availability of options differ depending of the chosen ticket number format " +"above." msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:5 -msgid "" -"This speeds up ticket aiding, no matter if it's for existing tickets or new " -"ones!" +#: ../settings/ticket.rst:122 +msgid "Checksum (default: ``no``)" msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:8 +#: ../settings/ticket.rst:118 msgid "" -"To see it work from the agent's perspective, have a look on :user-docs:`user " -"documentation `." +"If set to yes, we'll built a checksum to further \"unique\" the ticket " +"number of your system. If you're dealing with many other ticket systems this " +"might help to prevent false positive follow up detection on tickets." msgstr "" -#: ../system/integrations/cti/placetel.rst:2 -msgid "Placetel CTI" +#: ../settings/ticket.rst:122 +msgid "This will also add another digit to the ticket number." msgstr "" -#: ../system/integrations/cti/placetel.rst:16 -msgid "You need an administrative Placetel account for your organization." +#: ../settings/ticket.rst:137 +msgid "Min. size of Number (default: ``5``)" msgstr "" -#: ../system/integrations/cti/placetel.rst:17 -#: ../system/integrations/cti/sipgate.rst:20 +#: ../settings/ticket.rst:125 msgid "" -"Your Zammad instance must be allowed to communicate to external services." +"This setting defines the minimum length of your ticket number. If your " +"counter is not yet high enough, Zammad will fill the number with zeros to " +"ensure the wanted length." msgstr "" -#: ../system/integrations/cti/placetel.rst:18 -msgid "Placetel must be able to reach your Zammad instance." -msgstr "" - -#: ../system/integrations/cti/placetel.rst:22 -msgid ":doc:`provider-configurations/placetel`" -msgstr "" - -#: ../system/integrations/cti/placetel.rst:21 +#: ../settings/ticket.rst:129 msgid "" -"Learn how to configure Placetel to enable Zammad and Placetel to communicate " -"with each other." +"Please note that the minimum length is ``3`` (SystemID + at least one digit " +"if below 10). Also, if the length is no longer long enough, the number will " +"automatically get one digit longer. Ticket-Numbers **do not overflow**, thus " +"it's save to keep it at 5 or set it lower if wanted." msgstr "" -#: ../system/integrations/cti/placetel.rst:32 +#: ../settings/ticket.rst:135 msgid "" -"The here listed endpoint settings are relevant for the :doc:`integration " -"configuration with Placetel `." +"This option is only available if ticket number format is set to " +"``Increment``!" msgstr "" -#: ../system/integrations/cti/placetel.rst:37 -#: ../system/integrations/i-doit.rst:53 -msgid "Endpoint" +#: ../settings/ticket.rst:142 +msgid "Auto-Assignment" msgstr "" -#: ../system/integrations/cti/placetel.rst:36 +#: ../settings/ticket.rst:144 msgid "" -"This endpoint will be required for the Zammad integration within the " -"Placetel web interface." -msgstr "" - -#: ../system/integrations/cti/placetel.rst:41 -msgid "API Token" +"In a larger Zammad environment, it happens that several agents open the same " +"ticket at the same time. Although collision detection is then effective, the " +"efficiency of processing can be increased by means of the automatic " +"assignment of tickets when a ticket is opened." msgstr "" -#: ../system/integrations/cti/placetel.rst:40 +#: ../settings/ticket.rst:149 msgid "" -"You'll receive this token within the ``Web API`` menu. Make sure to copy " -"this value, it's only shown once!" -msgstr "" - -#: ../system/integrations/cti/placetel.rst:71 -#: ../system/integrations/cti/sipgate.rst:77 -msgid "Phone Extension to Agent Mapping" +"The automatic assignment of tickets can be activated and configured in the " +"admin area under Settings > Ticket > Auto Assignment." msgstr "" -#: ../system/integrations/cti/placetel.rst:0 -msgid "Screenshot showing sample user mappings in between Placetel and Zammad" +#: ../settings/ticket.rst:152 +msgid "" +"The auto assignment only works if the ticket has no owner yet. By default, " +"the agent can always reset the ticket owner to ``-`` if needed." msgstr "" -#: ../system/integrations/cti/placetel.rst:64 +#: ../settings/ticket.rst:155 msgid "" -"You can find your agents Placetel username combination required within ⚙️ PBX " -"→ VoIP destinations. Within the \"Advanced settings\" section you're looking " -"for \"SIP user name\" and \"SIP server\"." +"If you want to use this function for only specific tickets, you can " +"configure the conditions accordingly to meet your requirement. By default " +"the condition affects all tickets with the state ``open``." msgstr "" -#: ../system/integrations/cti/placetel.rst:68 -msgid "Combine these two like so: ``@``." +#: ../settings/ticket.rst:161 +msgid "" +"If you need to exclude users (e.g. a group leader), you can search and " +"select the desired agents in the ``Exception Users`` list. The search " +"function in this area is only effective, if you have too many agents to " +"display at once to help you with the configuration." msgstr "" -#: ../system/integrations/cti/placetel.rst:0 -msgid "Sample VoIP credentials for a Placetel user" +#: ../settings/ticket.rst:167 +msgid "Notifications" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:2 -msgid "Setup Placetel connection for Zammad" +#: ../settings/ticket.rst:191 +msgid "Default Notifications" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:6 +#: ../settings/ticket.rst:170 msgid "" -"This configuration step requires a *full* administrative Placetel account. " -"You may receive forbidden error messages with Placetel in case your " -"permissions are not high enough." +"This setting allows you to configure the default ticket notifications that " +"will be applied to all new agent users (incl. users who were just assigned " +"agent role). Simply change the notification matrix to desired state and " +"press **Save**." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:10 +#: ../settings/ticket.rst:175 msgid "" -"The following actions can be configured via the `Placetel web interface " -"`_." -msgstr "" - -#: ../system/integrations/cti/provider-configurations/placetel.rst:29 -msgid "Step 1: Activate Zammad integration" +"In case an agent already exists, their ticket notification preferences will " +"be preserved. Optionally, you can also **Apply current defaults to all " +"agents**." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:14 +#: ../settings/ticket.rst:181 msgid "" -"Within Integrations, scroll down to Partner integrations and select Zammad." +"**Potential time-consuming action:** Applying default ticket notifications " +"to all agent users may take some time to complete, be patient! The exact " +"time will depend on the size of your system and the number of agents." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:17 +#: ../settings/ticket.rst:185 msgid "" -"You can alternatively filter by \"Ticket Systems\" to reduce the number of " -"entries on the page. You'll still want to look for Partner integrations. 🤓" +"**Active agents only!** When current default ticket notifications are " +"applied, only active agent users are considered. In case an agent is re-" +"activated *after* this action, they will still have the old notification " +"configuration." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:21 +#: ../settings/ticket.rst:190 msgid "" -"Within the Zammad integration now press \"Activate\". A new tab ``API`` " -"becomes available - open this tab." +"In case you want to go back to the initial state of ticket notifications, " +"you can click on **Reset to default** button." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:24 -msgid "" -"Now tick \"Enable Call Control / Notify API\" and paste the Placetel " -"endpoint from your Zammad instance into the field \"URL of your API " -"endpoint\". Save to apply the settings" +#: ../settings/ticket.rst:196 +msgid "Duplicate Detection" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 -msgid "Screencast showing how to activate the Zammad integration" +#: ../settings/ticket.rst:238 +msgid "Detect Duplicate Ticket Creation" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:51 -msgid "Step 2: Generate API Token for Placetel" +#: ../settings/ticket.rst:199 +msgid "" +"This setting turns on the duplicate ticket detection mechanism during ticket " +"creation. If similar tickets are found in the system, a suitable warning " +"will be shown to the user trying to create a ticket." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:32 -msgid "" -"Go back to the integrations page and scroll down to \"Web API\". Generate a " -"new API token by using the \"Create a new API token\" button." +#: ../settings/ticket.rst:206 +msgid "A Sample Duplicate Ticket Warning" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:37 +#: ../settings/ticket.rst:208 msgid "" -"If you already generated a token either use your existing token or reset it " -"by using above mentioned button. Placetel will ask you to conform this reset." +"You can choose which ticket attributes will be matched by selecting them in " +"**Attributes to compare** field. Only if the ticket attribute value provided " +"by the user in the ticket create form is *equal* with the attribute in an " +"existing ticket, the warning will be shown." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:41 -msgid "" -"Please keep in mind that existing API scripts may no longer work due to " -"token resets!" +#: ../settings/ticket.rst:213 +msgid "**Warning title** and **Warning message** are configurable as well." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:44 +#: ../settings/ticket.rst:215 msgid "" -"Copy the provided API token and insert it into the \"API Token\" field " -"within Zammad's Placetel integration." +"You can limit the detection only to certain user roles. By default, only " +"agents will see the warning." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:47 +#: ../settings/ticket.rst:218 msgid "" -"Apply your changes by using the \"Save\" button on the bottom of the " -"Placetel integration page and activate the Placetel integration." +"If you don't want to show the matched tickets as part of the warning, you " +"can set **Show matching ticket(s) in the warning** setting to *no*." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +#: ../settings/ticket.rst:221 msgid "" -"Screencast showing how to retrieve an API token from Placetel for Zammad" +"By default, **Permission level for looking up ticket** is set to *User*, " +"which means user permissions will be honored during sarch. The user will " +"see the warning only if tickets they have access to are matched. " +"Alternatively, you can set this setting to *System*, in which case the " +"search will happen within *all* tickets in the system, regardless of user " +"permissions." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:73 -#: ../system/integrations/cti/provider-configurations/sipgate.rst:77 -msgid "Step 3: Restrict the numbers to notify on" +#: ../settings/ticket.rst:227 +msgid "**🦺 Safety first!**" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:54 +#: ../settings/ticket.rst:229 msgid "" -"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " -"the the Integrations page of the Placetel web interface, go to \"Notify " -"API\"." +"Even if the permission level is set to *System*, the user will not be shown " +"the tickets they don't have access to in the warning, even if they match." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:58 +#: ../settings/ticket.rst:233 msgid "" -"Lower on the page Placetel allows you to restrict the numbers to notify on. " -"You'll find this within the \"External routing API\" part." +"However, just the confirmation about the existence of the tickets in the " +"system may be considered an unwanted information disclosure. Use this option " +"carefully!" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +#: ../settings/ticket.rst:237 msgid "" -"Screenshot showing a sample selection of phone numbers to use for the " -"Placetels notify API" +"Finally, you can configure between matching within **All tickets** or **Open " +"tickets** only by setting **Match tickets in following states**. Depending " +"on the current ticket state, a ticket may or not be matched." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:66 -msgid "" -"This menu point also provides a API request log from Placetel view. Just " -"open \"Recent responses of your API endpoint\" to learn more." +#: ../system/core-workflows.rst:2 +msgid "Core Workflows" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:69 +#: ../system/core-workflows.rst:4 msgid "" -"If you want to see Zammad's perspective, use the \"Recent Logs\" part from " -"within the Placetel integration page." +"Core Workflows allow you to adjust object attributes in many ways. For " +"example:" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 -msgid "Screenshot showing sample log entries for Placetels API calls to Zammad" +#: ../system/core-workflows.rst:7 +msgid "show / hide fields" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:77 -msgid "Step 4 (optional): Further configurations for Placetel" +#: ../system/core-workflows.rst:8 +msgid "adjust mandatory setting" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:76 +#: ../system/core-workflows.rst:9 +msgid "manipulate available options" +msgstr "" + +#: ../system/core-workflows.rst:11 msgid "" -"If needed, you can now configure Zammad's Placetel integration in more " -"detail. You can learn more about your options here: :ref:`Placetel " -"integration settings `." +"With this, you can provide exactly the information your users really need!" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:2 -msgid "Setup Sipgate connection for Zammad" +#: ../system/core-workflows.rst:15 +msgid "" +"If the pre-defined :doc:`/system/objects` are not enough, please add them " +"beforehand." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +#: ../system/core-workflows.rst:17 msgid "" -"Sipgate has no english web interface which is why this documentation page is " -"mixing up languages badly." +"If you experience slow or unreliable field updates, please see :ref:`Core " +"Workflow Ajax Modus `" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +#: ../system/core-workflows.rst:22 msgid "" -"Please also note that the availability of API addons highly depends on your " -"package trier. Usage of sipgate.io packages *is not free*, please check " -"their `pricing page `_ before!" +"This is a very enhanced functionality and can cause unexpected UI behavior. " +"Please ensure to test your use cases after configuration to reduce surprises." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:35 -msgid "Step 1: Book sipgate.io package" +#: ../system/core-workflows.rst:None +msgid "Dialogue for adding a new workflow" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:13 -msgid "Skip to step 2 if you already have the package booked!" +#: ../system/core-workflows/condition-operators.rst:2 +msgid "Core Workflow Condition Operators" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:15 +#: ../system/core-workflows/condition-operators.rst:4 msgid "" -"Login to an administrative Sipgate account and navigate to " -"``Accountverwaltung``. You'll see several different options depending on " -"your booked packages. Select ``Verträge & Produkte`` to continue." +"You might know that there is a separate section for explaining :doc:" +"`condition operators `. Head over there to " +"see a detailed explanation of many conditions and operators." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:19 +#: ../system/core-workflows/condition-operators.rst:8 msgid "" -"Scroll down to the section ``Zusätzliche Produkte buchen`` and look for " -"``sipgate.io`` - select this product by using the ``Produkte anzeigen``-" -"Button." -msgstr "" - -#: ../system/integrations/cti/provider-configurations/sipgate.rst:23 -msgid "" -"On the next page select either one of the ``sipgate.io`` packages or ``Push-" -"API Package Free``. Follow the dialogue by booking the addon. You'll be " -"returned to your contract overview and now should see the selected addon in " -"your list." +"Due to differences to other places in Zammad which are also using conditions " +"(e.g. triggers), you can find a dedicated description of operators for core " +"workflows below." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:30 +#: ../system/core-workflows/condition-operators.rst:12 msgid "" -"The availability for ``sipgate.io`` packages and their levels highly depends " -"on the overall account type and product you've booked with Sipgate." +"Be aware that the availability of the operators depends on the selected " +"attribute and its field type. Some of the operators may only be available " +"for system attributes (e.g. for \"tags\", \"active\")." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screencast showing the process on how to book the required sipgate.io addon" +#: ../system/core-workflows/condition-operators.rst:20 +msgid "Operator" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:52 -msgid "Step 2: Configure webhook for Zammad" +#: ../system/core-workflows/condition-operators.rst:22 +msgid "after (absolute)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:38 -msgid "" -"Within your ``Accountverwaltung`` navicate to your product ``sipgate.io``. " -"In the newly opened tab, switch from \"Clients\" to \"Webhooks\" and paste " -"the endpoint URLs from your Zammad instance like so:" +#: ../system/core-workflows/condition-operators.rst:23 +msgid "Matches if a date/time is after a specific point in time." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:42 -msgid "Inbound endpoint to \"Incoming\"" +#: ../system/core-workflows/condition-operators.rst:24 +msgid "after (relative)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:43 -msgid "Outbound endpoint to \"Outgoing\"" +#: ../system/core-workflows/condition-operators.rst:25 +msgid "Matches if a time span after a specified event has passed." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:47 -msgid "" -"Ensure to select at least one call group or phoneline within \"Sources\". " -"Other wise Sipgate will not indicate any incoming or outgoing calls to " -"Zammad." +#: ../system/core-workflows/condition-operators.rst:26 +msgid "before (absolute)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screencast showing how to add Zammad's endpoint URLs to sipgate.ios webhook " -"configuration" +#: ../system/core-workflows/condition-operators.rst:27 +msgid "Matches if a date/time is before a specific point in time." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:55 -msgid "" -"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " -"the Webhooks → URLs section of Sipgate you can select which *sources* " -"Sipgate should notify Zammad about in- and outgoing calls." +#: ../system/core-workflows/condition-operators.rst:28 +msgid "before (relative)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:59 -msgid "" -"Use either specific phone lines or use the option \"Use for all phonelines " -"and groups\" to notify Zammad about all existing lines of your Sipgate " -"account." +#: ../system/core-workflows/condition-operators.rst:29 +msgid "Matches if a time span after a specified event has not passed." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screenshot showing a sample selection of phone numbers to use for the " -"Sipgates webhooks API" +#: ../system/core-workflows/condition-operators.rst:30 +msgid "contains" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:68 -msgid "This section also allows you to enable a Debug log." +#: ../system/core-workflows/condition-operators.rst:31 +msgid "Matches if a specified value is present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "Screenshot showing an enabled Debug log option" +#: ../system/core-workflows/condition-operators.rst:33 +msgid "Matches if all of the specified values are present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:73 -msgid "" -"After enabling you can use the Debug log section to see all sent webhook " -"calls to Zammad. You'll also can see the response." +#: ../system/core-workflows/condition-operators.rst:35 +msgid "Matches if none of the specified values are present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screenshot showing sample log entries for Sipgates webhook calls to Zammad" +#: ../system/core-workflows/condition-operators.rst:36 +msgid "contains not" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:81 -msgid "Step 4 (optional): Further configurations for Sipgate" +#: ../system/core-workflows/condition-operators.rst:37 +msgid "Matches if a specified value is not present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:80 -msgid "" -"If needed, you can now configure Zammad's Sipgate integration in more " -"detail. You can learn more about your options here: :ref:`Sipgate " -"integration settings `." +#: ../system/core-workflows/condition-operators.rst:39 +msgid "Matches if one specified value is present." msgstr "" -#: ../system/integrations/cti/sipgate.rst:2 -msgid "Sipgate (sipgate.io)" +#: ../system/core-workflows/condition-operators.rst:41 +msgid "Matches if one specified value is not present." msgstr "" -#: ../system/integrations/cti/sipgate.rst:16 -msgid "You need an administrative Sipgate account for your organization." +#: ../system/core-workflows/condition-operators.rst:42 +msgid "does not match regex" msgstr "" -#: ../system/integrations/cti/sipgate.rst:17 -msgid "" -"Zammad requires a ``sipgate.io`` addon from the feature store (please note " -"that API calls are not free with Sipgate. Rates may apply and differ from " -"account to account)." +#: ../system/core-workflows/condition-operators.rst:43 +msgid "Matches if content doesn't fit to regex rule." msgstr "" -#: ../system/integrations/cti/sipgate.rst:21 -msgid "Sipgate must be able to reach your Zammad instance." +#: ../system/core-workflows/condition-operators.rst:44 +msgid "ends with" msgstr "" -#: ../system/integrations/cti/sipgate.rst:25 -msgid ":doc:`provider-configurations/sipgate`" +#: ../system/core-workflows/condition-operators.rst:45 +msgid "Matches if content ends with specified value." msgstr "" -#: ../system/integrations/cti/sipgate.rst:24 -msgid "" -"Learn how to configure Sipgate to enable Zammad and Sipgate to communicate " -"with each other." +#: ../system/core-workflows/condition-operators.rst:46 +msgid "ends with one of" msgstr "" -#: ../system/integrations/cti/sipgate.rst:33 -msgid "" -"Below endpoint settings affect the :doc:`sipgate.io configuration `." +#: ../system/core-workflows/condition-operators.rst:47 +msgid "Matches if content ends with one of the specified values." msgstr "" -#: ../system/integrations/cti/sipgate.rst:37 -msgid "This endpoint is required for incoming call hooks." +#: ../system/core-workflows/condition-operators.rst:48 +msgid "from (relative)" msgstr "" -#: ../system/integrations/cti/sipgate.rst:40 -msgid "This endpoint is required for outgoing call hooks." +#: ../system/core-workflows/condition-operators.rst:49 +msgid "Matches if date/time is after a period of time after an event." msgstr "" -#: ../system/integrations/cti/sipgate.rst:0 -msgid "Screenshot showing sample user mappings in between Sipgate and Zammad" +#: ../system/core-workflows/condition-operators.rst:51 +msgid "Matches if content is equal to a specified value." msgstr "" -#: ../system/integrations/cti/sipgate.rst:69 -msgid "" -"You can find your agent's Sipgate username within ``Accountverwaltung → " -"Benutzer``. You're looking for the SIP-ID." +#: ../system/core-workflows/condition-operators.rst:52 +msgid "is any of" msgstr "" -#: ../system/integrations/cti/sipgate.rst:0 -msgid "Sample VoIP credentials for a Sipgate user" +#: ../system/core-workflows/condition-operators.rst:53 +msgid "Matches if content is equal to any of specified values." msgstr "" -#: ../system/integrations/cti/sipgate.rst:77 -msgid "Users with several devices also have several SIP-IDs." +#: ../system/core-workflows/condition-operators.rst:54 +msgid "is modified" msgstr "" -#: ../system/integrations/elasticsearch.rst:2 -msgid "Elasticsearch (SaaS)" +#: ../system/core-workflows/condition-operators.rst:55 +msgid "Matches if content is modified." msgstr "" -#: ../system/integrations/elasticsearch.rst:4 -msgid "" -"The Elasticsearch integration allows you to create a read-only user to use " -"with your favorite reporting tool (e.g. like Grafana)." +#: ../system/core-workflows/condition-operators.rst:57 +#: ../system/core-workflows/condition-operators.rst:61 +msgid "True from the moment of changing content until form submit." msgstr "" -#: ../system/integrations/elasticsearch.rst:7 -msgid "" -"If you want to take full advantage of the Zammad reporting, have a look at " -"our :docs:`Grafana ` " -"setup page as well." +#: ../system/core-workflows/condition-operators.rst:58 +msgid "is modified to" msgstr "" -#: ../system/integrations/elasticsearch.rst:11 -#: ../system/subscription/index.rst:7 -msgid "**🚧 Hosted environment specific 🚧**" +#: ../system/core-workflows/condition-operators.rst:59 +msgid "Matches if content is modified to a specific value." msgstr "" -#: ../system/integrations/elasticsearch.rst:13 -msgid "" -"This integration is only available for Hosted setups. In order to use " -"Elasticsearch you'll need the **Plus** subscription." +#: ../system/core-workflows/condition-operators.rst:62 +msgid "is none of" msgstr "" -#: ../system/integrations/elasticsearch.rst:16 -msgid "" -"Self hosted users have all the control over their self hosted Elasticsearch " -"instances." +#: ../system/core-workflows/condition-operators.rst:63 +msgid "Matches if content is none of any specified values." msgstr "" -#: ../system/integrations/elasticsearch.rst:None -msgid "Elasticsearch integration page on SaaS environments" +#: ../system/core-workflows/condition-operators.rst:65 +msgid "Matches if content is not equal to a specified value." msgstr "" -#: ../system/integrations/elasticsearch.rst:27 -msgid "" -"Please note the following limitations of Elasticsearch access on hosted " -"environments:" +#: ../system/core-workflows/condition-operators.rst:67 +msgid "Matches if content is present." msgstr "" -#: ../system/integrations/elasticsearch.rst:30 -msgid "access to the Elasticsearch index is read-only access" +#: ../system/core-workflows/condition-operators.rst:68 +msgid "just changed" msgstr "" -#: ../system/integrations/elasticsearch.rst:31 -msgid "currently you're limited to user only" +#: ../system/core-workflows/condition-operators.rst:69 +msgid "Matches if content has changed." msgstr "" -#: ../system/integrations/elasticsearch.rst:32 +#: ../system/core-workflows/condition-operators.rst:71 +#: ../system/core-workflows/condition-operators.rst:75 msgid "" -"Reporting tools that require to write into the indexes (like Kibana) are not " -"supported" +"Only true for the moment of changing content until next form field action/" +"click." msgstr "" -#: ../system/integrations/elasticsearch.rst:34 -msgid "IP access restriction is currently not yet supported" +#: ../system/core-workflows/condition-operators.rst:72 +msgid "just changed to" msgstr "" -#: ../system/integrations/elasticsearch.rst:37 -msgid "Activating Elasticsearch Access" +#: ../system/core-workflows/condition-operators.rst:73 +msgid "Matches if content has changed to a specified value." msgstr "" -#: ../system/integrations/elasticsearch.rst:39 -msgid "" -"By default external access to your Elasticsearch index is not active. You " -"can enable the integration at any time if needed." +#: ../system/core-workflows/condition-operators.rst:76 +msgid "matches regex" msgstr "" -#: ../system/integrations/elasticsearch.rst:42 -msgid "" -"Please ensure to note down the password provided - you won't have access to " -"it afterwards." +#: ../system/core-workflows/condition-operators.rst:77 +msgid "Matches if value fits to regex rule." msgstr "" -#: ../system/integrations/elasticsearch.rst:None -msgid "Screencast showing activation of Elasticsearch integration" +#: ../system/core-workflows/condition-operators.rst:79 +msgid "Matches if no content is present." msgstr "" -#: ../system/integrations/elasticsearch.rst:51 -msgid "Connection Settings" +#: ../system/core-workflows/condition-operators.rst:80 +msgid "starts with" msgstr "" -#: ../system/integrations/elasticsearch.rst:53 -msgid "" -"This section holds the most important general information for accessing your " -"Elasticsearch indexes - such as:" -msgstr "" - -#: ../system/integrations/elasticsearch.rst:57 -msgid "A unique subdomain that does not tell your real instance URL." +#: ../system/core-workflows/condition-operators.rst:81 +msgid "Matches if content starts with specified value." msgstr "" -#: ../system/integrations/elasticsearch.rst:61 -msgid "Software" +#: ../system/core-workflows/condition-operators.rst:82 +msgid "starts with one of" msgstr "" -#: ../system/integrations/elasticsearch.rst:60 -msgid "" -"The major version of the search index being used. This is required by some " -"Reporting tools like Grafana." +#: ../system/core-workflows/condition-operators.rst:83 +msgid "Matches if content starts with one of the specified values." msgstr "" -#: ../system/integrations/elasticsearch.rst:64 -msgid "Authentication" +#: ../system/core-workflows/condition-operators.rst:84 +msgid "till (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:64 -msgid "The authentication type being supported. ``Basic Authentication``" +#: ../system/core-workflows/condition-operators.rst:85 +msgid "Matches if date/time is before a period of time before an event." msgstr "" -#: ../system/integrations/elasticsearch.rst:67 -msgid "Available Indexes" +#: ../system/core-workflows/condition-operators.rst:86 +msgid "today" msgstr "" -#: ../system/integrations/elasticsearch.rst:69 -msgid "" -"Within this section we're displaying the -in our opinion- most important " -"indexes for a Zammad instance." +#: ../system/core-workflows/condition-operators.rst:87 +msgid "Matches if date/time is today." msgstr "" -#: ../system/integrations/elasticsearch.rst:72 -msgid "" -"If you require all indexes or our listing is not good enough for you, point " -"your browser to the URL we're providing and append ``/_aliases?" -"pretty=true``. The result should look like this: ``https://.zammad.com/" -"_aliases?pretty=true``." +#: ../system/core-workflows/condition-operators.rst:88 +msgid "within last (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:77 +#: ../system/core-workflows/condition-operators.rst:89 msgid "" -"Your browser will automatically ask for your credentials - you'll then see " -"something like this:" +"Matches if date/time content is within specified period of time before now." msgstr "" -#: ../system/integrations/elasticsearch.rst:125 -msgid "Credentials" +#: ../system/core-workflows/condition-operators.rst:91 +msgid "within next (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:127 +#: ../system/core-workflows/condition-operators.rst:92 msgid "" -"Within this section Zammad displays your available users. The password is " -"provided once (upon activation) and cannot be retrieved after that." +"Matches if date/time content is within specified period of time after now." msgstr "" -#: ../system/integrations/elasticsearch.rst:131 -msgid "" -"If you need to change or reset your Elasticsearch user password, use the " -"\"Reset password\" button in the credentials table. Doing so creates a brand " -"new password for the account in question. This change is immediate, keep in " -"mind that this may affect third party tools connected to your instance." +#: ../system/core-workflows/how-do-they-work.rst:2 +msgid "How do they work?" msgstr "" -#: ../system/integrations/exchange.rst:2 -msgid "Exchange" +#: ../system/core-workflows/how-do-they-work.rst:4 +msgid "" +"Core Workflows are executed according to their priority. If two workflows " +"have the same priority, they are executed in alphabetical order based on " +"their **name**." msgstr "" -#: ../system/integrations/exchange.rst:4 +#: ../system/core-workflows/how-do-they-work.rst:8 msgid "" -"With Zammad's Exchange integration, you can easily use existing address " -"books without having to update more than one source." +"Because of the way Core Workflows work, all changes to attributes are " +"checked with the application server - please see :doc:`limitations` for " +"possible issues." msgstr "" -#: ../system/integrations/exchange.rst:7 +#: ../system/core-workflows/how-do-they-work.rst:12 msgid "" -"However, you should refrain from syncing all addresses, as the results may " -"not be what you expect (Exchange collects huge amounts of addresses). A " -"central address book of your company to sync makes more sense, as you can " -"ensure that Zammad gets only the data you need and want. Apart from this, it " -"is even not possible to sync the Global Address List (GAL) of your Exchange " -"system with Zammad." +"Below we're talking about settings that are important and not self-" +"explanatory." msgstr "" -#: ../system/integrations/exchange.rst:16 +#: ../system/core-workflows/how-do-they-work.rst:17 msgid "" -"**Exchange and LDAP:** The exchange sync can be overruled by Zammad's LDAP " -"integration. If you have the same users in both sources, the LDAP version " -"will always be Zammad's pick." +"Choose the object context you want to run the workflow in. This will decide " +"on your available attributes and actions." msgstr "" -#: ../system/integrations/exchange.rst:19 -msgid "" -"**One way sync:** the Exchange sync is one way. Exchange => Zammad. Changes " -"to your users inside of Zammad might be overwritten by the Exchange sync." +#: ../system/core-workflows/how-do-they-work.rst:20 +msgid "Ticket objects also have access to the ticket customer." msgstr "" -#: ../system/integrations/exchange.rst:24 +#: ../system/core-workflows/how-do-they-work.rst:25 msgid "" -"To configure Exchange integration, simply go to the System > Integrations > " -"Exchange in the admin panel. Press \"change\" and follow the wizard for " -"adding the needed Exchange information to Zammad. On the last two steps " -"Zammad will ask you for the address book(s) and your desired attribute " -"mapping. By default, Zammad only maps email address, first- and lastname. " -"Technically, you can map any Exchange object to a Zammad user object (this " -"also works for custom objects!)." +"Choose in which situation the workflow is applied. Contexts can be combined " +"to avoid duplicate workflows." msgstr "" -#: ../system/integrations/exchange.rst:35 -msgid "" -"If the SSL verification fails while connecting to Exchange, Zammad will ask " -"you to turn it off temporarily." +#: ../system/core-workflows/how-do-they-work.rst:30 +msgid "Creation mask" msgstr "" -#: ../system/integrations/exchange.rst:38 +#: ../system/core-workflows/how-do-they-work.rst:29 msgid "" -"Please be aware that **turning off SSL verification is a security risk**. It " -"should only be used temporarily or for testing purposes. If turned off, " -"there is no verification of the certificate, which means that every " -"presented certificate will be accepted." +"If selected, your conditions and actions will affect all applicable creation " +"masks." msgstr "" -#: ../system/integrations/exchange.rst:43 -msgid "" -"After pressing Continue, Zammad will check if the configuration is okay. You " -"can then enable Exchange and start your first sync. The sync will then run " -"hourly - if you need to change mappings or the address book(s), you can " -"change the configuration at any time." +#: ../system/core-workflows/how-do-they-work.rst:34 +msgid "Edit mask" msgstr "" -#: ../system/integrations/exchange.rst:50 +#: ../system/core-workflows/how-do-they-work.rst:33 msgid "" -"After the sync has finished, you can find the new Exchange contacts under " -"\"Users\". Zammad integrates them just as normal users." +"If selected, your conditions and actions will affect all applicable edit " +"masks." msgstr "" -#: ../system/integrations/exchange.rst:55 +#: ../system/core-workflows/how-do-they-work.rst:39 msgid "" -"In some cases you might see unique IDs as \"Login\" instead of the email " -"address. This is normal and doesn't affect the login or email mapping for " -"that entry." +"Zammad differentiates between selected and saved conditions. These can be " +"combined wherever needed." msgstr "" -#: ../system/integrations/github.rst:4 -msgid "" -"Use GitHub integration to track GitHub issues directly within Zammad " -"tickets. Add issue hyperlinks and get a live summary of metadata like status " -"(open/closed), assignee, labels, and more." +#: ../system/core-workflows/how-do-they-work.rst:42 +msgid "**⚠️ Restrict workflows to specific roles if needed!**" msgstr "" -#: ../system/integrations/github.rst:8 -msgid "Please note that our GitHub integration does not support pull requests." +#: ../system/core-workflows/how-do-they-work.rst:44 +msgid "" +"By default and unless configured in conditions, workflow rules are executed " +"for **all roles**. This also affects your customers!" msgstr "" -#: ../system/integrations/github.rst:None -msgid "Integration page for GitHub" +#: ../system/core-workflows/how-do-they-work.rst:50 +msgid "Selected Conditions" msgstr "" -#: ../system/integrations/github.rst:18 +#: ../system/core-workflows/how-do-they-work.rst:48 msgid "" -"In your GitHub settings, create a new API token under **Developer settings > " -"Personal access tokens > Generate new token**. Leave the **Scopes** section " -"empty." +"These conditions are based on form values and match if an appropriate " +"selection is made (e.g. choosing another group in the ticket without " +"saving). This applies for drafts (active selection) and currently saved " +"values." msgstr "" -#: ../system/integrations/github.rst:0 ../system/integrations/gitlab.rst:0 -msgid "Screencast showing how to create a new API token" +#: ../system/core-workflows/how-do-they-work.rst:64 +msgid "Saved Conditions" msgstr "" -#: ../system/integrations/github.rst:27 -msgid "Create a new API key with no scopes/privileges." +#: ../system/core-workflows/how-do-they-work.rst:53 +msgid "" +"These conditions only match if the selected values are stored in the " +"database. It ignores the current value or selection of the field, as long as " +"the changes are not saved (e.g. performing field operations for an existing " +"ticket, which is viewed/opened by an agent)." msgstr "" -#: ../system/integrations/github.rst:29 -msgid "🔒 **Will this work for private repos?**" +#: ../system/core-workflows/how-do-they-work.rst:60 +msgid "" +"Keep in mind that the value has to be available in the situation where you " +"need it. Otherwise the condition won't match." msgstr "" -#: ../system/integrations/github.rst:31 +#: ../system/core-workflows/how-do-they-work.rst:63 msgid "" -"No. To link private repo issues, **use the** ``repo`` **scope instead**. " -"Bear in mind that the resulting token will have `lots of permissions that it " -"doesn't actually need `_, which presents a security risk if your token ever falls into " -"the wrong hands." +"Example: you can't perform any actions with *saved condition* on a ticket in " +"creation, because there are no saved values at that time." msgstr "" -#: ../system/integrations/github.rst:37 +#: ../system/core-workflows/how-do-they-work.rst:66 msgid "" -"Unfortunately, because of how GitHub's OAuth token scopes are set up, this " -"is the only way to link issues on private repos." +"You can find a description of the condition operators for core workflows :" +"doc:`here `." msgstr "" -#: ../system/integrations/github.rst:40 -msgid "Enter your new API token in Zammad and enable GitHub integration." +#: ../system/core-workflows/how-do-they-work.rst:72 +msgid "" +"Which actions should we run on the relevant fields? The possible actions " +"depend on the object type. However, usually you can at least change the " +"visibility and whether the field is mandatory." msgstr "" -#: ../system/integrations/github.rst:0 -msgid "Screencast showing how to configure Zammad's GitHub integration" +#: ../system/core-workflows/how-do-they-work.rst:76 +msgid "Be aware that actions are not available for **related** context." msgstr "" -#: ../system/integrations/github.rst:47 +#: ../system/core-workflows/how-do-they-work.rst:78 msgid "" -"Use the default API endpoint (``https://api.github.com/graphql``) unless " -"you're using GitHub Enterprise Server." +"**Example:** Let's assume you are working in the ticket context. While you " +"can have customer *conditions*, you *can't adjust* objects with actions in " +"that scope. That's because this wouldn't have any impact on the ticket " +"dialog. Of course all ticket attributes (state, owner, ...) are available." msgstr "" -#: ../system/integrations/github.rst:50 +#: ../system/core-workflows/how-do-they-work.rst:84 msgid "" -"Once completed, a new GitHub issues tab will appear in the ticket pane. 🎉" +"Please also have a look at our :doc:`limitations` to be safe from surprises." msgstr "" -#: ../system/integrations/github.rst:59 ../system/integrations/gitlab.rst:52 -msgid "Token verification is taking a long time" +#: ../system/core-workflows/how-do-they-work.rst:88 +msgid "Available Operators" msgstr "" -#: ../system/integrations/github.rst:56 ../system/integrations/gitlab.rst:49 -msgid "" -"Slight delays are normal (<2 min.), especially for systems under heavy load." +#: ../system/core-workflows/how-do-they-work.rst:90 +msgid "The availability of operators depends on the object type and scope." msgstr "" -#: ../system/integrations/github.rst:58 +#: ../system/core-workflows/how-do-they-work.rst:94 msgid "" -"Self-hosted administrators, please check your network settings to ensure " -"that your Zammad server can reach ``api.github.com``." +"Please note that actions may or may not restrict API based access to " +"attributes. We're displaying the following icons for your overview to " +"understand these limits better:" msgstr "" -#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 -msgid "I reloaded the page and now the API token is gone" +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|api| This icon indicates the action affects the API." msgstr "" -#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 -msgid "" -"This may indicate that Zammad is still verifying your API token. Try " -"reloading the page again in a couple minutes." +#: ../system/core-workflows/how-do-they-work.rst:163 +msgid "api" msgstr "" -#: ../system/integrations/gitlab.rst:2 -msgid "GitLab" +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|ui| This icon indicates the action only affects the web interface." msgstr "" -#: ../system/integrations/gitlab.rst:4 -msgid "" -"Use GitLab integration to track GitLab issues directly within Zammad " -"tickets. Add issue hyperlinks and get a live summary of metadata like status " -"(open/closed), assignee, labels, and more." +#: ../system/core-workflows/how-do-they-work.rst:167 +msgid "ui" msgstr "" -#: ../system/integrations/gitlab.rst:8 -msgid "" -"Please note that our GitLab integration does not support merge requests." +#: ../system/core-workflows/how-do-they-work.rst:102 +msgid "show |ui|" msgstr "" -#: ../system/integrations/gitlab.rst:None -msgid "Integration page for GitLab" +#: ../system/core-workflows/how-do-they-work.rst:102 +msgid "Display the chosen field. Allows setting of values." msgstr "" -#: ../system/integrations/gitlab.rst:18 -msgid "" -"In your GitLab preferences, create a new API token under **Access Tokens**." +#: ../system/core-workflows/how-do-they-work.rst:109 +msgid "hide |ui|" msgstr "" -#: ../system/integrations/gitlab.rst:20 -msgid "Under **Select scopes**, choose ``read_api`` only." +#: ../system/core-workflows/how-do-they-work.rst:105 +msgid "" +"Hide the chosen field. However, it technically still allows setting the " +"field." msgstr "" -#: ../system/integrations/gitlab.rst:27 -msgid "🔒 **If you wish to link issues on any private repos...**" +#: ../system/core-workflows/how-do-they-work.rst:108 +msgid "" +"Please note that the field is **not** gone and still contains an existing " +"value (if set)! Consider *remove* instead, if you want this field to be gone." msgstr "" -#: ../system/integrations/gitlab.rst:29 -msgid "Your API token must belong to an account with access to those repos." +#: ../system/core-workflows/how-do-they-work.rst:112 +msgid "remove |ui|" msgstr "" -#: ../system/integrations/gitlab.rst:31 -msgid "Enter your new API token in Zammad and enable GitLab integration." +#: ../system/core-workflows/how-do-they-work.rst:112 +msgid "Entirely removes the field. The field value will not be evaluated." msgstr "" -#: ../system/integrations/gitlab.rst:0 -msgid "Screencast showing how to configure Zammad's GitLab integration" +#: ../system/core-workflows/how-do-they-work.rst:115 +msgid "set mandatory |ui| |api|" msgstr "" -#: ../system/integrations/gitlab.rst:40 -msgid "" -"Use the default API endpoint (``https://gitlab.com/api/graphql``) unless " -"you're a self-hosted GitLab user." +#: ../system/core-workflows/how-do-they-work.rst:115 +msgid "Sets the field to mandatory." msgstr "" -#: ../system/integrations/gitlab.rst:43 -msgid "" -"Once completed, a new GitLab issues tab will appear in the ticket pane. 🎉" +#: ../system/core-workflows/how-do-they-work.rst:118 +msgid "set optional |ui| |api|" msgstr "" -#: ../system/integrations/gitlab.rst:51 -msgid "" -"Self-hosted administrators, please check your network settings to ensure " -"that your Zammad server can reach ``gitlab.com``." +#: ../system/core-workflows/how-do-they-work.rst:118 +msgid "Sets the field to optional." msgstr "" -#: ../system/integrations/i-doit.rst:2 -msgid "i-doit" +#: ../system/core-workflows/how-do-they-work.rst:124 +msgid "add option |ui| |api|" msgstr "" -#: ../system/integrations/i-doit.rst:4 -msgid "" -"`i-doit `_ is an open-source **configuration " -"management database** - in other words, a tool for keeping tabs on every " -"single piece of your physical and digital infrastructure, from network " -"equipment to virtual machines on down to the faceplates on your rack shelves " -"and more." +#: ../system/core-workflows/how-do-they-work.rst:121 +msgid "Allows adding options to tree selects or selects." msgstr "" -#: ../system/integrations/i-doit.rst:10 +#: ../system/core-workflows/how-do-they-work.rst:123 msgid "" -"What's that got to do with Zammad? Well, if you used tickets to track issues " -"with all that hardware, you might start wishing there was a way they could " -"talk to each other." -msgstr "" - -#: ../system/integrations/i-doit.rst:14 -msgid "Zammad gives you two:" +"You have to use the \"remove option\" before performing this action. It " +"allows you to use *existing* configured values." msgstr "" -#: ../system/integrations/i-doit.rst:17 -msgid "1. Add i-doit Links to Zammad Tickets" +#: ../system/core-workflows/how-do-they-work.rst:128 +msgid "remove option |ui| |api|" msgstr "" -#: ../system/integrations/i-doit.rst:20 ../system/integrations/i-doit.rst:80 -msgid "What Users See" +#: ../system/core-workflows/how-do-they-work.rst:127 +msgid "" +"Allows removing options from tree selects or selects. It allows you to use " +"*existing* configured values." msgstr "" -#: ../system/integrations/i-doit.rst:26 -msgid "i-doit integration in Zammad's ticket pane" +#: ../system/core-workflows/how-do-they-work.rst:134 +msgid "set fixed to |ui| |api|" msgstr "" -#: ../system/integrations/i-doit.rst:26 -msgid "" -"The i-doit integration will appear under a new 🖨 tab in the ticket pane." +#: ../system/core-workflows/how-do-they-work.rst:131 +msgid "Reduces the available options by your selection." msgstr "" -#: ../system/integrations/i-doit.rst:28 +#: ../system/core-workflows/how-do-they-work.rst:133 msgid "" -"i-doit integration puts a new tab in Zammad's ticket pane where you can add " -"links to existing i-doit devices for easy reference. (See our :user-docs:" -"`user documentation ` to learn " -"how it works in practice)." +"This reduces your workflows in terms of *add option* and *remove option*." msgstr "" -#: ../system/integrations/i-doit.rst:36 ../system/integrations/i-doit.rst:93 -msgid "How to Set it Up" +#: ../system/core-workflows/how-do-they-work.rst:137 +msgid "fill in |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:38 -msgid "" -"It requires i-doit's `API Add-on `_. Make sure to have it properly set up. Use the following setting:" +#: ../system/core-workflows/how-do-they-work.rst:137 +msgid "Allows filling in of string and integer fields with your values." msgstr "" -#: ../system/integrations/i-doit.rst:42 -msgid "Active: ``Yes``" +#: ../system/core-workflows/how-do-they-work.rst:141 +msgid "fill in empty |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:43 -msgid "Enforce authentication by username and password: ``No``" +#: ../system/core-workflows/how-do-they-work.rst:140 +msgid "" +"Allows filling in of string and integer fields with your values **if the " +"field is empty**." msgstr "" -#: ../system/integrations/i-doit.rst:45 -msgid "" -"To set it up, enable the integration in the Zammad admin panel under " -"**System > Integrations > i-doit**:" +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "select |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "i-doit settings within the integration pages" +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "Select a specific value within a select, tree select or boolean field." msgstr "" -#: ../system/integrations/i-doit.rst:53 -msgid "The root URL of your i-doit installation." +#: ../system/core-workflows/how-do-they-work.rst:153 +msgid "auto select |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:62 -msgid "API token" +#: ../system/core-workflows/how-do-they-work.rst:147 +msgid "Helps users with tree select and select fields:" msgstr "" -#: ../system/integrations/i-doit.rst:56 +#: ../system/core-workflows/how-do-they-work.rst:149 msgid "" -"Found in the i-doit admin panel under **Interfaces / external data > JSON-" -"RPC API > Common Settings**." +"If the field has only one option available for selection and no value yet, " +"the value will be automatically set." msgstr "" -#: ../system/integrations/i-doit.rst:0 -msgid "i-doit administration interface with API configuration" +#: ../system/core-workflows/how-do-they-work.rst:152 +msgid "" +"This option only works if you have one value and doesn't work if there is " +"more than one option available." msgstr "" -#: ../system/integrations/i-doit.rst:67 -msgid "Client ID" +#: ../system/core-workflows/how-do-they-work.rst:157 +msgid "set readonly |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:65 -msgid "A unique name to identify Zammad within i-doit." +#: ../system/core-workflows/how-do-they-work.rst:156 +msgid "" +"Allows you to display an attribute as read only (which means no changes are " +"possible)." msgstr "" -#: ../system/integrations/i-doit.rst:67 -msgid "(Zammad does not require you to enter a value here, but i-doit might!)" +#: ../system/core-workflows/how-do-they-work.rst:161 +msgid "unset readonly |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:70 +#: ../system/core-workflows/how-do-they-work.rst:160 msgid "" -"Here you can decide if the certificate of your i-doit system has to be " -"verified or not. In case you are using custom certificates, please have a " -"look at :doc:`how to add them to Zammad `." -msgstr "" - -#: ../system/integrations/i-doit.rst:77 -msgid "2. List / Create Zammad Tickets in i-doit" +"In case a workflow set the field in question to read only, you can undo this " +"with option above." msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "Zammad integration in i-doit's device view" +#: ../system/core-workflows/how-do-they-work.rst:172 +msgid "Stop after match" msgstr "" -#: ../system/integrations/i-doit.rst:86 +#: ../system/core-workflows/how-do-they-work.rst:174 msgid "" -"i-doit's ticket system integration gives you a way to see all the tickets " -"for a given device without ever leaving i-doit. (See our :user-docs:`user " -"documentation ` to learn how it " -"works in practice)." +"Here you can decide if other workflows are executed after the current one." msgstr "" -#: ../system/integrations/i-doit.rst:95 +#: ../system/core-workflows/how-do-they-work.rst:176 msgid "" -"Enable this integration in the i-doit admin panel under **Interfaces / " -"external data > Trouble Ticket System (TTS) > Configuration**:" +"If set to ``no`` (default), further workflows will be executed if they match " +"the condition. In this case, it is possible that your actions from the " +"current workflow can be overwritten by another workflow." msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "i-doit administration interface with TTS configuration" +#: ../system/core-workflows/how-do-they-work.rst:180 +msgid "" +"If set to ``yes``, no further worflows will be executed after the current " +"one." msgstr "" -#: ../system/integrations/i-doit.rst:104 -msgid "TTS-Type" +#: ../system/core-workflows/how-do-they-work.rst:184 +msgid "Priority" msgstr "" -#: ../system/integrations/i-doit.rst:104 -msgid "``Zammad``" +#: ../system/core-workflows/how-do-they-work.rst:186 +msgid "" +"You can define the sequence, in which the workflows are executed. The " +"default value is ``500``." msgstr "" -#: ../system/integrations/i-doit.rst:115 -msgid "Username / Password" +#: ../system/core-workflows/how-do-they-work.rst:189 +msgid "" +"The workflows are executed in ascending order by their priority. That means " +"lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." msgstr "" -#: ../system/integrations/i-doit.rst:107 -msgid "Login credentials for a Zammad agent." +#: ../system/core-workflows/learn-by-example.rst:2 +msgid "Learn by Example" msgstr "" -#: ../system/integrations/i-doit.rst:109 +#: ../system/core-workflows/learn-by-example.rst:4 msgid "" -"This agent must have **read permission** for all :doc:`groups ` that plan on using the i-doit integration." +"This page provides some basic examples for Core Workflows. Of course you can " +"build much more complex workflows if needed." msgstr "" -#: ../system/integrations/i-doit.rst:113 +#: ../system/core-workflows/learn-by-example.rst:7 msgid "" -"You may even wish to create a dedicated agent account just for this " -"integration (otherwise, if the agent ever changes her password, you will " -"have to remember to update it here)." +"To learn about Core Workflows in detail, first go to :doc:`how-do-they-work`." msgstr "" -#: ../system/integrations/i-doit.rst:117 -msgid "URL incl. protocol" +#: ../system/core-workflows/learn-by-example.rst:10 +msgid "Group Based Examples" msgstr "" -#: ../system/integrations/i-doit.rst:118 -msgid "``https://your.zammad.domain``" +#: ../system/core-workflows/learn-by-example.rst:12 +msgid "" +"All following workflows have the same base configurations. The workflow may " +"not use them all." msgstr "" -#: ../system/integrations/index.rst:2 -msgid "Integrations" +#: ../system/core-workflows/learn-by-example.rst:15 +msgid "Groups:" msgstr "" -#: ../system/integrations/index.rst:4 +#: ../system/core-workflows/learn-by-example.rst:20 +msgid "Attributes:" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:22 +msgid "Category (Single tree selection field, not mandatory, agents only)" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:23 msgid "" -"Zammad offers numerous integrations that add rich features to your instance." +"Approved (Boolean field, not mandatory, not shown, ``false`` as default)" msgstr "" -#: ../system/integrations/index.rst:6 -msgid "We're still working on this part of our documentation, stay tight!" +#: ../system/core-workflows/learn-by-example.rst:24 +msgid "Operating System (Text field, not mandatory, not shown)" msgstr "" -#: ../system/integrations/index.rst:10 -msgid "Integrations for Phone Systems" +#: ../system/core-workflows/learn-by-example.rst:25 +msgid "Software used (Single selection field, not mandatory, not shown)" msgstr "" -#: ../system/integrations/index.rst:14 -msgid "" -"Your VoIP provider or telephony system is not listed? Possibly your provider " -"supports Zammad by using the generic CTI - if you're unsure ask your " -"provider." +#: ../system/core-workflows/learn-by-example.rst:68 +msgid "Group specific values and fields" msgstr "" -#: ../system/integrations/index.rst:18 +#: ../system/core-workflows/learn-by-example.rst:28 msgid "" -"Provider does not support Zammad? Consider creating a `feature request in " -"the Zammad Community `_." +"This workflow set depends on the category field. It reduces the available " +"set of values based on the group selected." msgstr "" -#: ../system/integrations/index.rst:31 -msgid "Integrations for Authentication and Customers" +#: ../system/core-workflows/learn-by-example.rst:33 +msgid "Workflow 2nd Level group" msgstr "" -#: ../system/integrations/index.rst:44 -msgid "Integrations for Monitoring Systems" +#: ../system/core-workflows/learn-by-example.rst:35 +msgid "" +"This reduces the category options to ``2nd Level/*``, ``Internal/*`` and " +"``Others``. It also sets further required fields to mandatory and visible." msgstr "" -#: ../system/integrations/index.rst:46 -msgid "This section currently misses the following integrations:" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for 2nd level" msgstr "" -#: ../system/integrations/index.rst:48 -msgid "Icinga" -msgstr "Icinga" - -#: ../system/integrations/index.rst:49 -msgid "Monit" +#: ../system/core-workflows/learn-by-example.rst:43 +msgid "Workflow Support group" msgstr "" -#: ../system/integrations/index.rst:50 -msgid "Nagios" +#: ../system/core-workflows/learn-by-example.rst:45 +msgid "" +"This reduces the category options to ``Support/*``, ``Internal/*`` and " +"``Others``. It also sets further required fields to visible." msgstr "" -#: ../system/integrations/index.rst:60 -msgid "Integrations for Issue Trackers" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for support" msgstr "" -#: ../system/integrations/index.rst:70 -msgid "Other Integrations" +#: ../system/core-workflows/learn-by-example.rst:53 +msgid "Workflow Sales group" msgstr "" -#: ../system/integrations/index.rst:72 +#: ../system/core-workflows/learn-by-example.rst:55 msgid "" -"This section will hold any other integration that can't be grouped up (yet)." +"This reduces the category options to ``Sales/*``, ``Internal/*`` and " +"``Others``." msgstr "" -#: ../system/integrations/ldap/index.rst:2 -msgid "LDAP / Active Directory" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for sales" msgstr "" -#: ../system/integrations/ldap/index.rst:4 -msgid "" -"Zammad comes with a powerful LDAP integration that allows you to have a " -"single source of truth. By this you reduce the number of login credentials " -"your user has to remember." +#: ../system/core-workflows/learn-by-example.rst:68 +#: ../system/integrations/slack.rst:88 +msgid "The Result" msgstr "" -#: ../system/integrations/ldap/index.rst:10 +#: ../system/core-workflows/learn-by-example.rst:63 msgid "" -"The LDAP source is also a perfect candidate for Zammad's :docs:`Kerberos " -"Single Sign-On ` but also works as addition " -"to other :doc:`/settings/security/third-party`." +"This is what the agent would experience with the above workflows in place." msgstr "" -#: ../system/integrations/ldap/index.rst:None -msgid "Zammands LDAP management page" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "" +"Workflow shows objects and limits options based on selections on the group" msgstr "" -#: ../system/integrations/ldap/index.rst:25 -msgid "📝 :doc:`manage`" +#: ../system/core-workflows/learn-by-example.rst:90 +msgid "Approval process" msgstr "" -#: ../system/integrations/ldap/index.rst:25 -msgid "Add, modify, remove or re-arrange your LDAP-Sources as needed." +#: ../system/core-workflows/learn-by-example.rst:71 +msgid "" +"In this case ``approved`` is visible to agents by default. For this " +"workflow, an additional role ``Approval person`` is required (no further " +"permissions)." msgstr "" -#: ../system/integrations/ldap/index.rst:30 -msgid "Before you continue, please note the following limitations." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that restricts an approval attribute to specific roles" msgstr "" -#: ../system/integrations/ldap/index.rst:32 -msgid "Mapping / Synchronizing organizations is not possible" +#: ../system/core-workflows/learn-by-example.rst:81 +msgid "" +"This workflow may work best in combination with a :doc:`trigger ` but technically, this is not required." msgstr "" -#: ../system/integrations/ldap/index.rst:36 +#: ../system/core-workflows/learn-by-example.rst:84 msgid "" -"You may want to consider using domain based assignments to overcome this " -"issue. Learn more on :doc:`/manage/organizations/index`." +"Select fields may be a better approach because they allow more values than " +"just a simple ``true`` or ``false``." msgstr "" -#: ../system/integrations/ldap/index.rst:39 +#: ../system/core-workflows/learn-by-example.rst:0 msgid "" -"Zammad's LDAP sync is one way. Editing user settings or permissions may be " -"overwritten upon the next sync depending on your configuration." +"Workflow fixes possible values of \"Approved ?\" to a specific selection " +"depending on the users role" msgstr "" -#: ../system/integrations/ldap/index.rst:41 -msgid "Nested groups are not supported." +#: ../system/core-workflows/learn-by-example.rst:103 +msgid "State dependent mandatory fields" msgstr "" -#: ../system/integrations/ldap/index.rst:42 -msgid "Synchronizing user avatars from LDAP is not supported." +#: ../system/core-workflows/learn-by-example.rst:93 +msgid "" +"This workflow sets ``Category`` to mandatory if the agent wants to set the " +"states ``closed`` or ``pending close`` to enforce categorization." msgstr "" -#: ../system/integrations/ldap/index.rst:43 -msgid "Unlike user filters, group filters cannot be changed." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that sets fields to mandatory on specific states" msgstr "" -#: ../system/integrations/ldap/index.rst:44 +#: ../system/core-workflows/learn-by-example.rst:0 msgid "" -"When a user originates from an LDAP server, Zammad will try to verify the " -"login credentials against LDAP first - if this fails Zammad will check its " -"local database." +"Workflow sets category field to mandatory upon choosing closed or pending " +"close as state" msgstr "" -#: ../system/integrations/ldap/index.rst:50 -msgid "" -"Users can have local passwords even if they're LDAP users! You can learn " -"more about user accounts in general on :doc:`/manage/users/index`." +#: ../system/core-workflows/learn-by-example.rst:106 +msgid "Manual Ticket Handover Process" msgstr "" -#: ../system/integrations/ldap/index.rst:54 -msgid "" -"When several LDAP sources contain the same user (meaning the same email " -"address), the user in question will be updated with every source configured. " -"*The last LDAP source will win.*" +#: ../system/core-workflows/learn-by-example.rst:108 +msgid "This example covers the handover of a ticket from one agent to another:" msgstr "" -#: ../system/integrations/ldap/index.rst:58 +#: ../system/core-workflows/learn-by-example.rst:110 msgid "" -"This is subject to change with `Issue 4109 `_ in the future." +"When the ticket owner is modified, a new text field (\"Handover\") shows up " +"for a comment" msgstr "" -#: ../system/integrations/ldap/index.rst:60 +#: ../system/core-workflows/learn-by-example.rst:112 msgid "" -"Synchronization statistics currently affect *all* configured LDAP sources. " -"This also applies for newly added or updated sources." +"This may only be visible when the owner is changed, therefore it has to be " +"hidden in general" msgstr "" -#: ../system/integrations/ldap/index.rst:63 -msgid "" -"This is subject to change with `Issue 4108 `_ in the future." +#: ../system/core-workflows/learn-by-example.rst:114 +msgid "The input in this handover text field is mandatory" msgstr "" -#: ../system/integrations/ldap/index.rst:65 +#: ../system/core-workflows/learn-by-example.rst:115 msgid "" -"Zammad currently has limited fallback server support. You can workaround " -"this by providing several sources - however, ensure to have the exact same " -"configuration on your fallback." +"After submitting changes, the value of the handover field must be added as " +"an note to the ticket (via trigger)" msgstr "" -#: ../system/integrations/ldap/index.rst:69 -msgid "" -"This is subject to improve with `Issue 4107 `_ in the future." +#: ../system/core-workflows/learn-by-example.rst:121 +msgid "Hiding handover field" msgstr "" -#: ../system/integrations/ldap/index.rst:76 -msgid "" -"This section holds all requests Zammad handled for all LDAP sources. These " -"entries can either contain synchronization information or logins " -"(authentication attempts via Zammad's login interface)." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Hiding the handover field in core workflows" msgstr "" -#: ../system/integrations/ldap/index.rst:80 -msgid "" -"By clicking on any request, Zammad will provide even more information. The " -"provided information can be useful when something does not work as expected." +#: ../system/core-workflows/learn-by-example.rst:126 +msgid "Showing handover field and setting it to mandatory" msgstr "" -#: ../system/integrations/ldap/index.rst:85 -msgid "" -"Especially a LDAP synchronization can cause many log entries. The web " -"interface will always limit the number of shown entries to the last 50 " -"entries." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Showing the handover field and set it as mandatory" msgstr "" -#: ../system/integrations/ldap/index.rst:None -msgid "" -"Screencast showing LDAP integration log entries and a detail view on\n" -"an entry." +#: ../system/core-workflows/learn-by-example.rst:131 +msgid "Trigger writing handover input to a new article" msgstr "" -#: ../system/integrations/ldap/manage.rst:2 -msgid "Manage LDAP-Sources" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Write handover content to a new article" msgstr "" -#: ../system/integrations/ldap/manage.rst:6 +#: ../system/core-workflows/learn-by-example.rst:133 msgid "" -"Please keep in mind all current limitations for the LDAP synchronization. " -"This will help to understand scopes of the following operations better." +"As a result, the ticket includes an article of the type note which includes " +"the predefined text and the handover comment." msgstr "" -#: ../system/integrations/ldap/manage.rst:65 -msgid "Add new source" +#: ../system/core-workflows/limitations.rst:6 +msgid "Core Workflows do not replace Triggers" msgstr "" -#: ../system/integrations/ldap/manage.rst:10 +#: ../system/core-workflows/limitations.rst:5 msgid "" -"Using the *New Source* button allows you to add new LDAP sources to your " -"installation. You're not limited in the number of sources, however, keep in " -"mind that many sources will also take more time to synchronize." +"Workflows manipulate the behavior of fields. However, they do not set values " +"in fields because of actions." msgstr "" -#: ../system/integrations/ldap/manage.rst:14 -msgid "" -"You can choose between different encryption types, namely *SSL* and " -"*STARTTLS* or none of them (\"*No SSL*\"). If you choose *SSL* or " -"*STARTTLS*, Zammad will display an additional *SSL verification* option that " -"allows you to disable the verification, e.g. for self-signed SSL " -"certificates. You can also tell Zammad to use a different port by appending " -"``:`` to your hostname/IP." +#: ../system/core-workflows/limitations.rst:16 +msgid "API calls are only partly affected" msgstr "" -#: ../system/integrations/ldap/manage.rst:0 +#: ../system/core-workflows/limitations.rst:9 msgid "" -"Screenshot of configuring a new LDAP source with SSL encryption and SSL " -"verification" +"Some options affect UI only and thus do not restrict responses and calls." msgstr "" -#: ../system/integrations/ldap/manage.rst:26 -msgid "" -"New Source with SSL transport security enabled and certificate verification" +#: ../system/core-workflows/limitations.rst:11 +msgid "This affects the following actions:" msgstr "" -#: ../system/integrations/ldap/manage.rst:30 -msgid "" -"Using an user filter can be a good idea if you only require a small subset " -"of your LDAP users in Zammad." +#: ../system/core-workflows/limitations.rst:13 +msgid "select" msgstr "" -#: ../system/integrations/ldap/manage.rst:42 -msgid "This especially affects inactive users" +#: ../system/core-workflows/limitations.rst:14 +msgid "auto select" msgstr "" -#: ../system/integrations/ldap/manage.rst:34 -msgid "" -"As every LDAP behaves differently on which attributes and how they are set, " -"Zammad doesn't care about any flags." +#: ../system/core-workflows/limitations.rst:15 +msgid "show" msgstr "" -#: ../system/integrations/ldap/manage.rst:37 -msgid "" -"Users that no longer are returned by your LDAP source will automatically be " -"set to inactive. Zammad assumes that the user was deactivated." +#: ../system/core-workflows/limitations.rst:16 +msgid "hide" msgstr "" -#: ../system/integrations/ldap/manage.rst:41 -msgid "" -"Users will never be removed automatically! If you want to remove obsolete " -"users, use :doc:`/system/data-privacy`." +#: ../system/core-workflows/limitations.rst:25 +msgid "Some fields stay unavailable to customers" msgstr "" -#: ../system/integrations/ldap/manage.rst:46 -msgid "Active Directory admins" +#: ../system/core-workflows/limitations.rst:19 +msgid "" +"For technical and security reasons, some default fields (the pale ones you " +"can't edit) stay unavailable for display and usage on customer permissions." msgstr "" -#: ../system/integrations/ldap/manage.rst:45 +#: ../system/core-workflows/limitations.rst:23 msgid "" -"Active Directories are quite specific on how to filter for active users only " -"- please see the `Microsoft documentation `_ for more " -"information." +"If you require your customers to change e.g. priorities, please consider " +"using workarounds via :doc:`/system/objects` and :doc:`/manage/trigger`." msgstr "" -#: ../system/integrations/ldap/manage.rst:51 -msgid "" -"*Do not* manually write pathes of either LDAP attributes or groups. If " -"Zammad does not display them, it either cannot find them or you have a lot " -"of users that don't have the attributes populated." +#: ../system/core-workflows/limitations.rst:29 +msgid "Ticket title changes not supported in edit mask" msgstr "" -#: ../system/integrations/ldap/manage.rst:55 +#: ../system/core-workflows/limitations.rst:28 msgid "" -"Zammad will always only return attributes that are filled - this reduces the " -"returned list of attributes greatly." +"It is currently not possible to perform changes of the ticket title in the " +"edit mask (e.g. renaming, set to read-only)." msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing how to add a new LDAP source" +#: ../system/core-workflows/limitations.rst:37 +msgid "What is out of scope of Core Workflows?" msgstr "" -#: ../system/integrations/ldap/manage.rst:63 +#: ../system/core-workflows/limitations.rst:32 msgid "" -"If your LDAP system doesn't allow anonymous bind, Zammad detects it and " -"provides you an editable \"Base DN\" *text* field instead of a prefilled " -"*select* field." +"There are some things that would count as workflow but are either done via :" +"doc:`/manage/trigger` or :doc:`/manage/scheduler`." msgstr "" -#: ../system/integrations/ldap/manage.rst:81 -msgid "Review or edit existing source" +#: ../system/core-workflows/limitations.rst:35 +msgid "Such as (but not limited to):" msgstr "" -#: ../system/integrations/ldap/manage.rst:68 -msgid "" -"Clicking on a LDAP source will provide a configuration and mapping overview." +#: ../system/core-workflows/limitations.rst:37 +msgid "up- or downgrade permissions of users" msgstr "" -#: ../system/integrations/ldap/manage.rst:70 -msgid "" -"If needed you can then use the *Change* button to update either the name, " -"active state or the whole configuration. If you're changing the whole " -"configuration, the dialogue will be identical to the source creation." +#: ../system/core-workflows/limitations.rst:38 +msgid "affecting article creation or listing" msgstr "" -#: ../system/integrations/ldap/manage.rst:76 -msgid "" -"Did your LDAP server change? Different LDAP servers have different " -"structures and default attributes. This causes the LDAP synchronization to " -"likely fail. Consider removing the affected source and re-add it." +#: ../system/data-privacy.rst:2 +msgid "Data Privacy" msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing the update of the source name." +#: ../system/data-privacy.rst:4 +msgid "" +"For compliance with GDPR and other data privacy laws, you may wish to " +"**permanently delete users from the system**, along with **all of their " +"associated tickets**." msgstr "" -#: ../system/integrations/ldap/manage.rst:89 -msgid "Re-arrange LDAP source's order" +#: ../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 `!" msgstr "" -#: ../system/integrations/ldap/manage.rst:84 +#: ../system/data-privacy.rst:12 msgid "" -"You can change the synchronization order for each source at any time. Zammad " -"will synchronize the sources from top to bottom." +"Access to this panel requires ``admin.data_privacy`` permissions (introduced " +"in Zammad 3.5)." msgstr "" -#: ../system/integrations/ldap/manage.rst:0 +#: ../system/data-privacy.rst:15 msgid "" -"Screencasting showing how to change the source order by using\n" -"drag and drop." +"On older systems that have not been updated yet, customers can also be :docs:" +"`deleted via the Zammad console `." msgstr "" -#: ../system/integrations/ldap/manage.rst:101 -msgid "Remove a source" +#: ../system/data-privacy.rst:22 +msgid "User deletion dialog in the Data Privacy panel" msgstr "" -#: ../system/integrations/ldap/manage.rst:92 +#: ../system/data-privacy.rst:22 msgid "" -"If you no longer need the a LDAP source or simply want to start over, you " -"can remove them at any time. This will not remove synchronized users, data " -"synchronized or permissions." +"The user deletion dialog lists some of the tickets that will be removed from " +"the system along with the user." msgstr "" -#: ../system/integrations/ldap/manage.rst:98 -msgid "" -"Not sure if you'd need the source later on? Set the source to inactive " -"instead of removing it - see *Review or edit existing source* for more." +#: ../system/data-privacy.rst:27 +msgid "Deleting Users via GUI" msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing how to remove LDAP sources." +#: ../system/data-privacy.rst:29 +msgid "🔥 **All deletions are FINAL!**" msgstr "" -#: ../system/integrations/pgp/index.rst:2 -msgid "PGP" +#: ../system/data-privacy.rst:31 +msgid "Once you click “Delete”, the action cannot be canceled or undone." msgstr "" -#: ../system/integrations/pgp/index.rst:7 +#: ../system/data-privacy.rst:33 msgid "" -"Pretty Good Privacy (PGP) is another method for secure email communication. " -"With PGP, you can exchange **signed** and **encrypted** messages with others." +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:13 -#: ../system/integrations/smime/index.rst:17 -msgid "Signing" +#: ../system/data-privacy.rst:36 +msgid "**The following records cannot be deleted:**" msgstr "" -#: ../system/integrations/pgp/index.rst:11 -msgid "is a proof that a message hasn't been manipulated on its way." +#: ../system/data-privacy.rst:38 +msgid "your own account" msgstr "" -#: ../system/integrations/pgp/index.rst:13 -msgid "" -"In other words, it guarantees message **integrity** and **authenticity**." +#: ../system/data-privacy.rst:39 +msgid "the system's last remaining administrator account" msgstr "" -#: ../system/integrations/pgp/index.rst:19 -#: ../system/integrations/smime/index.rst:22 -msgid "Encryption" +#: ../system/data-privacy.rst:42 +msgid "Step 1: Find a User / Confirm Deletion" msgstr "" -#: ../system/integrations/pgp/index.rst:16 -#: ../system/integrations/smime/index.rst:20 -msgid "" -"scrambles a message so that it can only be unscrambled by the intended " -"recipient." +#: ../system/data-privacy.rst:44 +msgid "There are three ways to access the user deletion dialog:" msgstr "" -#: ../system/integrations/pgp/index.rst:19 -msgid "" -"In other words, it guarantees message **privacy** and **data security**." +#: ../system/data-privacy.rst:51 +msgid "**from the user's profile**" msgstr "" -#: ../system/integrations/pgp/index.rst:25 -msgid "Screenshot of ticket creation with encrypt and sign buttons" +#: ../system/data-privacy.rst:0 +msgid "Accessing the user deletion dialog in a user profile" msgstr "" -#: ../system/integrations/pgp/index.rst:25 -msgid "" -"Once PGP has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " -"appear in the ticket composer." +#: ../system/data-privacy.rst:51 +msgid "Click **Action > Delete**." msgstr "" -#: ../system/integrations/pgp/index.rst:28 -msgid "**Sign button not visible?**" +#: ../system/data-privacy.rst:58 +msgid "**in the “Manage > Users” Admin Panel**" msgstr "" -#: ../system/integrations/pgp/index.rst:30 -msgid "" -"Please note that the signing of emails is based on the outgoing email " -"account. That means you have to choose a group with a sender email account, " -"which has a private key assigned." +#: ../system/data-privacy.rst:0 +msgid "Accessing the user deletion dialog under “Users” in the Admin Panel" msgstr "" -#: ../system/integrations/pgp/index.rst:35 -msgid "Handling of Keys" +#: ../system/data-privacy.rst:58 +msgid "Use the **⋮ Actions** menu for the target user." msgstr "" -#: ../system/integrations/pgp/index.rst:36 -msgid "" -"To use the PGP function, you have to enable the integration (PGP) by " -"switching the toggle to *enabled*." +#: ../system/data-privacy.rst:66 ../system/data-privacy.rst:104 +msgid "**in the “System > Data Privacy” Admin Panel**" msgstr "" -#: ../system/integrations/pgp/index.rst:39 +#: ../system/data-privacy.rst:0 msgid "" -"You can add keys by clicking the *add key* button. The keys can be imported " -"from a file or you can paste the content of the key in the text box." +"Accessing the user deletion dialog under “Data Privacy” in the Admin Panel" msgstr "" -#: ../system/integrations/pgp/index.rst:42 -msgid "**Which keys do I have to import?**" +#: ../system/data-privacy.rst:65 +msgid "" +"Use the **New Deletion Task** button. Search for users by name or email " +"address." msgstr "" -#: ../system/integrations/pgp/index.rst:44 -msgid "" -"For **signing** *outgoing* emails, you have to import the private key of " -"your Zammad email account." +#: ../system/data-privacy.rst:79 +msgid "**Delete organizations**" msgstr "" -#: ../system/integrations/pgp/index.rst:47 +#: ../system/data-privacy.rst:69 msgid "" -"For **encrypting** *outgoing* emails, you have to import the public key of " -"the customer's email account." +"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:" msgstr "" -#: ../system/integrations/pgp/index.rst:50 -msgid "" -"For **verifying the signature** of signed *incoming* emails, you have to " -"import the public key of the customer." +#: ../system/data-privacy.rst:0 +msgid "Deleting an organization via the user deletion dialog" msgstr "" -#: ../system/integrations/pgp/index.rst:53 +#: ../system/data-privacy.rst:78 msgid "" -"For **decrypting** of encrypted *incoming* emails, you have to import the " -"private key of your Zammad email account." -msgstr "" - -#: ../system/integrations/pgp/index.rst:57 -msgid "Import Keys From a File" -msgstr "" - -#: ../system/integrations/pgp/index.rst:58 -msgid "You can import keys from a file in the section **Upload key**:" +"If this option does not appear, make sure there are no pending deletion " +"tasks for other customers from this organization." msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of adding a key via file" +#: ../system/data-privacy.rst:82 +msgid "Step 2: Monitor Deletion Job Status" msgstr "" -#: ../system/integrations/pgp/index.rst:64 +#: ../system/data-privacy.rst:84 msgid "" -"**Supported file formats:** ASCII-armor as well as binary GPG format " -"(basically any GPG supported key format) is supported here." -msgstr "" - -#: ../system/integrations/pgp/index.rst:68 -msgid "Import Keys by Pasting the Content" +"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:" msgstr "" -#: ../system/integrations/pgp/index.rst:69 -msgid "You can also paste the key's content in the section **paste key**:" +#: ../system/data-privacy.rst:98 +msgid "**in the Activity Stream**" msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of adding a key via pasting" +#: ../system/data-privacy.rst:0 +msgid "Activity Stream showing data privacy tasks" msgstr "" -#: ../system/integrations/pgp/index.rst:75 +#: ../system/data-privacy.rst:94 msgid "" -"**Supported format:** Please note that only ASCII-armor is supported here." +"For each deleted user, the Activity Stream will be updated twice—once when " +"the task is created, and once when it's complete." msgstr "" -#: ../system/integrations/pgp/index.rst:78 -msgid "Deleting Keys" +#: ../system/data-privacy.rst:97 +msgid "" +"These notifications are only visible to users with ``admin.data_privacy`` " +"permissions." msgstr "" -#: ../system/integrations/pgp/index.rst:79 +#: ../system/data-privacy.rst:0 msgid "" -"If you want to delete a specific key, you can do it by clicking on the menu " -"in the *actions* column and select **delete**:" +"The task list within Data Privacy shows removals being in progress and " +"completed." msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of deleting a key" +#: ../system/data-privacy.rst:107 +msgid "Frequently Asked Questions" msgstr "" -#: ../system/integrations/pgp/index.rst:88 -msgid "Downloading Keys" +#: ../system/data-privacy.rst:121 +msgid "What happens if I receive an email from a deleted customer?" msgstr "" -#: ../system/integrations/pgp/index.rst:89 +#: ../system/data-privacy.rst:110 msgid "" -"If you want to download your keys, you can do this as well via corresponding " -"action buttons. Depending on the key, you can choose wether you want to " -"download the private or the public key." -msgstr "" - -#: ../system/integrations/pgp/index.rst:95 -#: ../system/integrations/smime/manage-certificates.rst:76 -msgid "Default Behavior" +"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/integrations/pgp/index.rst:96 +#: ../system/data-privacy.rst:115 msgid "" -"Here you can adjust on per group basis, if *sign* and *encryption* is on or " -"off by default. Please be aware, that agents can always override the setting " -"for each individual article." +"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**." msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Adjusting default behavior on per group basis" +#: ../system/data-privacy.rst:130 +msgid "What about user information stored in internal notes or other messages?" msgstr "" -#: ../system/integrations/pgp/index.rst:107 +#: ../system/data-privacy.rst:124 msgid "" -"Here you can see the last actions regarding signing and encryption and if " -"they were successful." +"The deletion process removes **user accounts and associated tickets only**." msgstr "" -#: ../system/integrations/pgp/index.rst:117 -msgid "**Sign button is not visible, but keys are imported.**" +#: ../system/data-privacy.rst:126 +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." msgstr "" -#: ../system/integrations/pgp/index.rst:115 -msgid "Did you choose a group in the ticket?" +#: ../system/data-privacy.rst:137 +msgid "I deleted an user and can still see a message they sent!" msgstr "" -#: ../system/integrations/pgp/index.rst:116 +#: ../system/data-privacy.rst:133 msgid "" -"Did you import a private key for the email adress, which is used for " -"outgoing emails in the group?" +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:122 -msgid "**How to obtain keys?**" +#: ../system/data-privacy.rst:141 +msgid "I removed a customer, now my reporting is off!" msgstr "" -#: ../system/integrations/pgp/index.rst:120 +#: ../system/data-privacy.rst:140 msgid "" -"You can create them yourself! There are some good tutorials on the web on " -"how to create them. Providing keys to Zammad is a prerequisite to use the " -"PGP feature." +"When removing users and their tickets, all references are removed. This also " +"affects e.g. Reporting - these information are lost." msgstr "" -#: ../system/integrations/pgp/index.rst:127 -msgid "**It says a passphrase is needed, but I haven't got one.**" +#: ../system/data-privacy.rst:145 +msgid "How long does Zammad store created tasks?" msgstr "" -#: ../system/integrations/pgp/index.rst:125 +#: ../system/data-privacy.rst:144 msgid "" -"If the key is secured with a passphrase, you have to provide it for the " -"import in Zammad. It is possible that keys may have an empty passphrase. " -"However, this is *not* recommended." +"Please see the on-premise data section of the :docs:`data privacy ` chapter." msgstr "" -#: ../system/integrations/pgp/index.rst:132 -msgid "**How do my customers get my new key?**" +#: ../system/data-privacy.rst:150 +msgid "What about re-assigned tickets? I want to delete them, too." msgstr "" -#: ../system/integrations/pgp/index.rst:130 +#: ../system/data-privacy.rst:148 msgid "" -"You have to provide your **public** key in advance. Your customer also has " -"to configure PGP in their email workflow and import your public key. The " -"other way round, you have to get the public key of your customer and have to " -"import it to Zammad." -msgstr "" - -#: ../system/integrations/slack.rst:2 -msgid "Slack" +"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." msgstr "" -#: ../system/integrations/slack.rst:4 -msgid "**⚠️ Deprecation warning ⚠️**" +#: ../system/data-privacy.rst:154 +msgid "Why are there so many deletion task entries, I didn't create them!" msgstr "" -#: ../system/integrations/slack.rst:6 +#: ../system/data-privacy.rst:153 msgid "" -"Zammad 7 will no longer support this dedicated Slack integration. It is " -"recommended to switch to :doc:`pre-defined webhooks ` instead. Existing Slack integrations should " -"be migrated manually before this feature is dropped." +"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." msgstr "" -#: ../system/integrations/slack.rst:14 -msgid "" -"In order to use this feature, please add a new Slack app to your Workspace. " -"The App you need is called ``Incoming WebHooks`` ." +#: ../system/integrations/checkmk/admin-panel-reference.rst:2 +msgid "Admin Panel Reference" msgstr "" -#: ../system/integrations/slack.rst:18 -msgid "Why Do I Need This Feature?" +#: ../system/integrations/checkmk/admin-panel-reference.rst:None +msgid "Screenshot of Checkmk settings overview" msgstr "" -#: ../system/integrations/slack.rst:20 +#: ../system/integrations/checkmk/admin-panel-reference.rst:12 msgid "" -"If you're already using Slack for your team communication, you'll love this " -"feature! Our Slack integration can push ticket notifications about the last " -"ticket article based on the following events:" +"Which :doc:`group ` should Checkmk tickets be assigned " +"to as a default (*i.e.,* when none is specified)?" msgstr "" -#: ../system/integrations/slack.rst:24 -msgid "on Ticket creation" +#: ../system/integrations/checkmk/admin-panel-reference.rst:15 +msgid "(Applies to :ref:`API alerts ` only.)" msgstr "" -#: ../system/integrations/slack.rst:25 -msgid "on Ticket updates" +#: ../system/integrations/checkmk/admin-panel-reference.rst:21 +msgid "Auto close" msgstr "" -#: ../system/integrations/slack.rst:26 -msgid "on reached reminders" +#: ../system/integrations/checkmk/admin-panel-reference.rst:18 +msgid "" +"Should Zammad automatically close tickets if a service has recovered on its " +"own?" msgstr "" -#: ../system/integrations/slack.rst:27 -msgid "a Ticket has escalated" +#: ../system/integrations/checkmk/admin-panel-reference.rst:21 +msgid "(Agents will receive notifications for such closures as appropriate.)" msgstr "" -#: ../system/integrations/slack.rst:28 -msgid "a Ticket is going to escalate" +#: ../system/integrations/checkmk/admin-panel-reference.rst:30 +msgid "Auto-close state" msgstr "" -#: ../system/integrations/slack.rst:30 -msgid "" -"Zammad will provide the Ticket title, a direct link to the Ticket, the event " -"type (creation, updated, escalation), the customer, time and the last " -"article that has triggered the notification." +#: ../system/integrations/checkmk/admin-panel-reference.rst:24 +msgid "What ticket state should be applied when “auto-closing” a ticket?" msgstr "" -#: ../system/integrations/slack.rst:34 +#: ../system/integrations/checkmk/admin-panel-reference.rst:26 msgid "" -"This will give you further options, as you can see e.g. escalating tickets " -"that are assigned to an agent that's e.g. absent. You can interact faster, " -"as you might see problems earlier (or even before the problem gets one)." +"You can choose from the seven built-in ticket states. If these states aren't " +"enough for you, you can :ref:`define a new ticket state ` for this purpose as well. This can be useful for tracking " +"tickets with :doc:`reports `, for example." msgstr "" -#: ../system/integrations/slack.rst:38 -msgid "" -"If needed and wanted, you can even discuss directly about the topic before " -"sending an answer to the customer. Another possible use case would be a " -"agent monitoring new agents and their answers to tickets." +#: ../system/integrations/checkmk/admin-panel-reference.rst:35 +#: ../system/integrations/cti/includes/recent-logs.include.rst:2 +#: ../system/integrations/ldap/index.rst:74 +#: ../system/integrations/pgp/index.rst:106 +msgid "Recent Logs" msgstr "" -#: ../system/integrations/slack.rst:44 -msgid "Configure the Integration" +#: ../system/integrations/checkmk/admin-panel-reference.rst:None +msgid "Screenshot of Checkmk \"Recent Logs\" section" msgstr "" -#: ../system/integrations/slack.rst:46 +#: ../system/integrations/checkmk/admin-panel-reference.rst:41 msgid "" -"First of all, please go to your slack workspace - go to administration => " -"Manage Apps. If you don't have an app yet, you can simply add a new one - " -"just search for ``Incoming WebHooks`` and customize the app to your needs." +"If you're having trouble getting Zammad and Checkmk to play nicely together, " +"this section can help you troubleshoot." msgstr "" -#: ../system/integrations/slack.rst:50 +#: ../system/integrations/checkmk/admin-panel-reference.rst:44 msgid "" -"Choose (or create) the channel Zammad should post it's information to and " -"press on \"Add Incoming WebHooks integration\". If you're ready, copy the " -"provided WebHook URL and go to your Zammad installation." +"It contains a record of the fifty most recent transactions that Zammad knows " +"about, including each one's request/response details and return status." msgstr "" -#: ../system/integrations/slack.rst:56 -msgid "" -"You need administrative rights on the Slack Workspace. The link to the app " -"directory is normally ``https://[workspace-name].slack.com/apps`` ." +#: ../system/integrations/checkmk/api-reference.rst:2 +msgid "API Reference" msgstr "" -#: ../system/integrations/slack.rst:63 +#: ../system/integrations/checkmk/api-reference.rst:4 msgid "" -"To configure the slack integration, log in to Zammad and go to Integrations " -"(System) => Slack in the admin panel." +"For most users, :ref:`the sample scripts from the Setup Guide ` will do the job just fine. But if you want more fine-grained control" +"—for instance, to create high- and low-priority tickets for different types " +"of system events—then you'll have to customize the data those scripts send " +"to Zammad." msgstr "" -#: ../system/integrations/slack.rst:66 +#: ../system/integrations/checkmk/api-reference.rst:15 msgid "" -"Here you can choose on what evens Zammad should post information about a " -"ticket to your Slack channel. Next you need to device what groups shall be " -"affected by this, as anybody with access to that specific Slack channel can " -"read at least parts of the ticket this might be a privacy issue, if you " -"select the wrong groups. The username is simply the name that Zammad uses as " -"display name inside the Slack chat. The channel defines the Slack channel " -"the information is being posted in. As last option, you can set a custom " -"icon for posting to slack." +"This custom script will automatically set all tickets it creates to **high " +"priority** and **assign them to charlie@chrispresso.com**." msgstr "" -#: ../system/integrations/slack.rst:74 -msgid "" -"When you're ready, just hit \"Submit\" and enable the integration. Zammad " -"will now post new ticket information based on the trigger you chose. Below " -"the options you have the recent log that shows the latest requests to Slack " -"for debugging if needed." +#: ../system/integrations/checkmk/api-reference.rst:32 +msgid "How Does it Work?" msgstr "" -#: ../system/integrations/slack.rst:81 +#: ../system/integrations/checkmk/api-reference.rst:34 msgid "" -"If you leave the Icon URL empty, Zammad will use the Zammad logo instead. " -"The icon should be a square PNG file." +"There are two kinds of data you can pass to the API, both in the form of key-" +"value pairs:" msgstr "" -#: ../system/integrations/slack.rst:90 -msgid "" -"The following figure shows how it will look if you choose to receive updates " -"on created and updated tickets. On every post Zammad sends to the Slack " -"channel, you can create new threads to discuss about the new article." +#: ../system/integrations/checkmk/api-reference.rst:44 +msgid "Checkmk parameters" msgstr "" -#: ../system/integrations/slack.rst:96 +#: ../system/integrations/checkmk/api-reference.rst:38 msgid "" -"If you just want to keep track of soon escalating or already escalated " -"tickets, it will look the the following figure. Zammad changes the color in " -"front of the post so you can easily see the state of the ticket." +"are required, and make up the **contents** of the resulting tickets/" +"articles. They also determine whether an event creates a new ticket or " +"updates/closes an existing one." msgstr "" -#: ../system/integrations/slack.rst:102 +#: ../system/integrations/checkmk/api-reference.rst:42 msgid "" -"If you change the state, Zammad will also put information on what state the " -"ticket gets and (if pending state) the date until it pends. You'll also " -"recognize the color codes in front of posts on slack, as they are exact the " -"same the ticket state colors you'll see in Zammad!" +"These are the only values used in the sample scripts. **Use them as-is**; " +"technically, they can be customized, but it's hard to imagine a good reason " +"for it." msgstr "" -#: ../system/integrations/smime/index.rst:2 -msgid "S/MIME" +#: ../system/integrations/checkmk/api-reference.rst:52 +msgid "Ticket attributes" msgstr "" -#: ../system/integrations/smime/index.rst:11 +#: ../system/integrations/checkmk/api-reference.rst:47 msgid "" -"S/MIME is the most widely-supported method for secure email communication. " -"With S/MIME, you can exchange **signed** and **encrypted** messages with " -"others." +"are optional, and can be used to **adjust settings** on newly created " +"tickets (*e.g.,* set the owner, group, priority, or state)." msgstr "" -#: ../system/integrations/smime/index.rst:15 +#: ../system/integrations/checkmk/api-reference.rst:50 msgid "" -"is proof that a message hasn't been tampered with or sent by an impersonator." +"If you want to customize your Checkmk alert script, do it with these. Simply " +"add an extra “form” option for each one (``-F \"key=value\"``) to your " +"script's ``curl`` command line, as in the example above." msgstr "" -#: ../system/integrations/smime/index.rst:17 +#: ../system/integrations/checkmk/api-reference.rst:54 +msgid "💡 **It's just an API endpoint!**" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:56 msgid "" -"In other words, it guarantees a message's **integrity** and **authenticity**." +"When using Checkmk integration, messages need to be formatted in a certain " +"way, but that *doesn't mean the messages actually have to come from Checkmk*." msgstr "" -#: ../system/integrations/smime/index.rst:22 -msgid "In other words, it guarantees **privacy** and **data security**." +#: ../system/integrations/checkmk/api-reference.rst:59 +msgid "" +"If you use another monitoring tool that's not officially supported by " +"Zammad, there's probably a way to make it work with your Checkmk callback " +"URL." msgstr "" -#: ../system/integrations/smime/index.rst:28 -msgid "Screencast demo of S/MIME features for both new tickets and replies" +#: ../system/integrations/checkmk/api-reference.rst:63 +msgid "Checkmk Parameters" msgstr "" -#: ../system/integrations/smime/index.rst:28 +#: ../system/integrations/checkmk/api-reference.rst:65 msgid "" -"Once S/MIME has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " -"appear in the ticket composer." +"When a notification is received, Zammad creates a new article containing the " +"details of the event that triggered it:" msgstr "" -#: ../system/integrations/smime/index.rst:32 -msgid ":doc:`🔪 Prerequisites `" +#: ../system/integrations/checkmk/api-reference.rst:None +msgid "Checkmk article body" msgstr "" -#: ../system/integrations/smime/index.rst:31 +#: ../system/integrations/checkmk/api-reference.rst:72 msgid "" -"New to S/MIME? This section helps you to find certificate providers and " -"points out Limitations." +"These details come from the fields listed below, which correspond to " +"parameters provided by Checkmk (``$NOTIFY_*``)." msgstr "" -#: ../system/integrations/smime/index.rst:35 -msgid ":doc:`📝 Manage Certificates `" +#: ../system/integrations/checkmk/api-reference.rst:75 +msgid "**Required fields are marked with an asterisk (\\*).**" msgstr "" -#: ../system/integrations/smime/index.rst:35 -msgid "Add and download certificates; configure group default behaviors." +#: ../system/integrations/checkmk/api-reference.rst:79 +msgid "event_id\\*" msgstr "" -#: ../system/integrations/smime/index.rst:38 -msgid ":doc:`😦 Troubleshooting `" +#: ../system/integrations/checkmk/api-reference.rst:78 +msgid "" +"A unique ID for the system event. (``$NOTIFY_SERVICEPROBLEMID`` / " +"``$NOTIFY_HOSTPROBLEMID``)" msgstr "" -#: ../system/integrations/smime/index.rst:38 -msgid "Took a wrong turn? About recent logs and common issues." +#: ../system/integrations/checkmk/api-reference.rst:86 +msgid "host\\*" msgstr "" -#: ../system/integrations/smime/index.rst:43 +#: ../system/integrations/checkmk/api-reference.rst:82 msgid "" -"For more details on how S/MIME integration works on the agent side, see the :" -"user-docs:`user docs `." -msgstr "" - -#: ../system/integrations/smime/manage-certificates.rst:2 -msgid "Manage Certificates" +"The hostname of the system that the event originated from. " +"(``$NOTIFY_HOSTNAME``)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:4 +#: ../system/integrations/checkmk/api-reference.rst:85 msgid "" -"S/MIME is **disabled by default**. Enable it to start adding certificates." +"Used to determine if a new event belongs to an existing ticket. Also used in " +"the subject line of the resulting article (“ is ”)." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:10 -msgid "Dialogue to add new certificates or private keys" +#: ../system/integrations/checkmk/api-reference.rst:96 +msgid "service" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:10 +#: ../system/integrations/checkmk/api-reference.rst:89 msgid "" -"Manage certificates in the Admin Panel under **System > Integrations > S/" -"MIME**. Certificates may be pasted in as plain text or uploaded from a file." +"The name of the service that the event originated from. " +"(``$NOTIFY_SERVICEDESC``)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:14 -msgid "Add Certificate Data" +#: ../system/integrations/checkmk/api-reference.rst:92 +msgid "Used to determine if a new event belongs to an existing ticket." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:36 -msgid "Add Certificate" +#: ../system/integrations/checkmk/api-reference.rst:94 +#: ../system/integrations/checkmk/api-reference.rst:110 +msgid "Displayed as ``-`` when omitted." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:17 -msgid "" -"Import public-key certificates for both your own organization and your " -"contacts." +#: ../system/integrations/checkmk/api-reference.rst:104 +msgid "state\\*" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:19 +#: ../system/integrations/checkmk/api-reference.rst:99 msgid "" -"You can also add a bunch of certificates in one go by providing a single " -"file with all relevant certificates." -msgstr "" - -#: ../system/integrations/smime/manage-certificates.rst:22 -msgid "🕵️ **ALWAYS verify certificates in-person or over the phone!**" +"The current state of the service or host in question. " +"(``$NOTIFY_SERVICESTATE`` / ``$NOTIFY_HOSTSTATE``)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:24 +#: ../system/integrations/checkmk/api-reference.rst:102 msgid "" -"The whole point of signatures is to alert you when someone is trying to " -"pretend to be someone they're not. Never accept a certificate from someone " -"online without verifying it first." +"Used to detect when a ticket should be auto-closed (*i.e.,* on ``OK``/" +"``UP``). Also used in the subject line of the resulting article (“ is " +"”)." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:28 -msgid "📇 **What about trusted certificate authorities?**" +#: ../system/integrations/checkmk/api-reference.rst:110 +msgid "text" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:30 +#: ../system/integrations/checkmk/api-reference.rst:107 msgid "" -"In some cases (e.g. when dealing with large enterprises), you may be given a " -"certificate for an entire CA, rather than a single contact. Add it here to " -"trust *all* certificates issued by that CA." +"The output of the process that triggered the event. " +"(``$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:35 +#: ../system/integrations/checkmk/api-reference.rst:121 msgid "" -"Commercial CAs can usually be verified online. Zammad does not include a " -"list of built-in, trusted CAs." +"The Object Manager attribute panel displays built-in and custom\n" +"attribute names." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:57 -msgid "Add Private Key" +#: ../system/integrations/checkmk/api-reference.rst:121 +msgid "Find a complete list of ticket attributes in the Object Manager." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:39 +#: ../system/integrations/checkmk/api-reference.rst:123 msgid "" -"Once you've added a public-key certificate, you can import its matching " -"private key." +"Ticket attributes are entirely optional, and can be used to customize the " +"tickets that Checkmk creates. (Note that these attributes will be ignored if " +"a new event belongs to an existing ticket.)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:42 +#: ../system/integrations/checkmk/api-reference.rst:128 msgid "" -"Private keys are for **your own organization only**; never ask your contacts " -"for their private keys." +"Why would you want to do this? Maybe you have only one IT guy, and all " +"system monitoring issues should be automatically assigned to him. Or, maybe " +"you're creating multiple notification rules so that database outages take " +"higher priority than disk space warnings." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:0 -msgid "" -"S/MIME integration showing configured certificates and possible issues with " -"Logging" +#: ../system/integrations/checkmk/api-reference.rst:135 +msgid "In most cases, you'll probably want to set one of the following:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:50 -msgid "" -"A note is displayed on certificates with a matching private key (see line 2)." +#: ../system/integrations/checkmk/api-reference.rst:137 +msgid "group" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:52 -msgid "📤 **Certificates and private keys must be uploaded separately.**" +#: ../system/integrations/checkmk/api-reference.rst:139 +msgid "state" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:54 +#: ../system/integrations/checkmk/api-reference.rst:140 +msgid "priority" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:142 msgid "" -"If your certificate and private key are bundled together in the same file or " -"PEM block, import it twice (once using each button)." +"but in practice, you can set almost any attribute, including :doc:`custom " +"ones you created through the Object Manager `." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:57 -msgid "Please note that bulk imports of private keys are not possible." +#: ../system/integrations/checkmk/api-reference.rst:145 +msgid "Please note that the following attributes are **not customizable**:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:60 -msgid "Download Certificate Data" +#: ../system/integrations/checkmk/api-reference.rst:147 +msgid "title" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:62 -msgid "" -"You can download the earlier provided certificates and private keys at any " -"time from your Zammad instance." -msgstr "" - -#: ../system/integrations/smime/manage-certificates.rst:65 -msgid "" -"Please note that passphrase-protected private keys stay protected and when " -"you download them, you have to know the passphrase to use them after " -"downloading." +#: ../system/integrations/checkmk/api-reference.rst:148 +msgid "id" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:73 -msgid "Dialogue to download certificates or private keys" +#: ../system/integrations/checkmk/api-reference.rst:149 +msgid "ticket number" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:73 -msgid "Download stored certificates and their keys" +#: ../system/integrations/checkmk/api-reference.rst:151 +msgid "created_by_id" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:78 -msgid "" -"The ticket composer will set all outgoing messages to **signed and " -"encrypted** by default (assuming the required certificates exist)." +#: ../system/integrations/checkmk/api-reference.rst:152 +msgid "updated_by_id" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:82 -msgid "These defaults can be modified on a per-group basis:" +#: ../system/integrations/checkmk/api-reference.rst:155 +msgid "Which Values Can Be Set?" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:None -msgid "Zammad allowing to choose the default behavior on per group basis" +#: ../system/integrations/checkmk/api-reference.rst:157 +msgid "😵 **Invalid values → unpredictable behavior**" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:89 +#: ../system/integrations/checkmk/api-reference.rst:159 msgid "" -"Of course, agents can always manually change these settings on each email " -"they send out." +"If you provide a value that Zammad doesn't understand (*e.g.,* ``-F " +"\"priority=high\"``), it's not always clear what will happen. In some cases, " +"a ticket will be created with the default values instead - but in others, it " +"may not be created at all!" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:4 -msgid "A certificate *and* private key for your own organization" +#: ../system/integrations/checkmk/api-reference.rst:164 +msgid "So what values does Zammad understand, then? Well, it depends..." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:6 -msgid "" -"(Use this to ✒️ **sign outgoing messages** and 🔓 **decrypt incoming " -"messages**.)" +#: ../system/integrations/checkmk/api-reference.rst:168 +msgid "Use an email address or username:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:9 -msgid "" -"Certificates belonging your contacts, or their issuing certificate authority " -"(CA)" +#: ../system/integrations/checkmk/api-reference.rst:190 +msgid "group & priority" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:11 -msgid "" -"(Use these to ✅ **verify incoming message signatures** and 🔒 **encrypt " -"outgoing messages**.)" +#: ../system/integrations/checkmk/api-reference.rst:175 +msgid "Refer to the dropdown menus in the ticket pane:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:14 -msgid "🙋 **I'm new to S/MIME. Where can I get a certificate?**" +#: ../system/integrations/checkmk/api-reference.rst:0 +msgid "See possible values for certain attributes in the ticket pane." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:16 -msgid "" -"The easiest way to get certificates is to buy an annual subscription through " -"a commercial CA, such as:" +#: ../system/integrations/checkmk/api-reference.rst:187 +msgid "🙅 **Ticket state CANNOT be set this way!**" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:19 +#: ../system/integrations/checkmk/api-reference.rst:189 msgid "" -"`Sectigo (formerly Comodo) `_" -msgstr "" - -#: ../system/integrations/smime/prerequisites.rst:20 -msgid "`Secorio `_" -msgstr "" - -#: ../system/integrations/smime/prerequisites.rst:21 -msgid "`GlobalSign `_" +"Why? Because ``-F \"state=...\"`` is already used :ref:`as a Checkmk " +"parameter `." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:23 -msgid "(Zammad is not affiliated with these CAs in any way.)" +#: ../system/integrations/checkmk/api-reference.rst:222 +msgid "Everything Else" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:25 +#: ../system/integrations/checkmk/api-reference.rst:193 msgid "" -"You can also generate your own self-signed certificates, but the process is " -"complicated and usually 🙅 **involves extra work for your contacts**." +"To set any other attributes, it helps to know your way around the :docs:" +"`rails console `. Valid values are those that you can " +"set with a string:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:29 -msgid "" -"Bear in mind that 🤝 **S/MIME only works if the other party is using it, too." -"**" +#: ../system/integrations/checkmk/api-reference.rst:218 +msgid "These values can then be passed directly to the API:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:32 -msgid "Certificate and Private Key Checks on Upload" +#: ../system/integrations/checkmk/index.rst:16 +msgid "How does it work?" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:34 -msgid "" -"The certificate and public key validation is based on the ``X509v3`` " -"extensions." +#: ../system/integrations/checkmk/index.rst:2 +msgid "Checkmk" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:49 -msgid "Uploading a *client certificate*?" +#: ../system/integrations/checkmk/index.rst:4 +msgid "" +"`Checkmk `_ is a powerful IT monitoring tool that can " +"send real-time status alerts to Zammad via email or REST API. Set these " +"alerts up in Checkmk, and Zammad will automatically create, update, and " +"close tickets based on the health of your system:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:41 -msgid "The following attributes are required then:" +#: ../system/integrations/checkmk/index.rst:14 +msgid "Screenshot of ticket created by Checkmk notifications" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:39 -msgid "Subject Alternative Name (at least one email address has to be present)" +#: ../system/integrations/checkmk/index.rst:14 +msgid "Multiple alerts, same ticket." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:40 -msgid "Key Usage (``Digital Signature`` and/or ``Key Encipherment``)" +#: ../system/integrations/checkmk/setup-guide.rst:2 +msgid "Setup Guide" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:41 -msgid "Public key algorithm (either ``RSA`` or ``EC``)" +#: ../system/integrations/checkmk/setup-guide.rst:4 +msgid "" +"Whenever the Checkmk integration is enabled, Zammad listens for messages on " +"its API and over email. As long as those messages follow the required " +"format, Zammad will create new tickets (or find and update existing ones) " +"based on the message contents." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:43 +#: ../system/integrations/checkmk/setup-guide.rst:10 msgid "" -"The Extended Key Usage attribute is optional. If the certificate provides " -"the named attribute, than it must contain the value ``E-mail Protection``." +"That means that “setting up Checkmk integration” is simply a matter of " +"**adding configuration to your Checkmk site**: telling it when to send these " +"messages and what to say. To do that, you'll need to create a new " +"**notification rule** (see `Checkmk's official docs `_ for help with that)." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:46 +#: ../system/integrations/checkmk/setup-guide.rst:17 msgid "" -"Please note that any usable email adress has to be prefixed with ``email:`` " -"or ``rfc822:``." +"As part of this new rule, you'll have to choose a **notification method** " +"(*i.e.,* a script to execute whenever the rule is triggered). This script " +"will be written by you (samples below), and contain the logic for sending " +"API/email messages to Zammad:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:49 -msgid "The named public key algorithms are mandatory for private keys as well." +#: ../system/integrations/checkmk/setup-guide.rst:26 +msgid "Checkmk \"New Rule\" dialog" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:54 -msgid "Uploading a *CA certificate*?" +#: ../system/integrations/checkmk/setup-guide.rst:26 +msgid "" +"Find your custom scripts in the Checkmk WATO under **Notifications > New " +"Rule > Notification Method**." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:52 +#: ../system/integrations/checkmk/setup-guide.rst:29 msgid "" -"In the case of an uploaded CA certificate, providing the value ``CA:TRUE`` " -"in the attribute *Basic Contstraints*, the previously mentioned attributes " -"are not verified." +"Once you're done setting up your new rule, you're all set! New tickets " +"should start coming in and auto-updating any time your rule is triggered." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:56 +#: ../system/integrations/checkmk/setup-guide.rst:33 msgid "" -"In general, the usage of any expired (``Not After``) or not yet valid (``Not " -"Before``) certificate is denied for outgoing emails." +"(If you need help troubleshooting, be sure to check the :ref:`checkmk-recent-" +"logs`.)" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:59 -msgid "Example certificate:" +#: ../system/integrations/checkmk/setup-guide.rst:38 +msgid "API Alerts" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:85 +#: ../system/integrations/checkmk/setup-guide.rst:40 msgid "" -"Please note that Zammad will distrust senders by default. This means that " -"you're always required to provide certificate data, no matter if for signing " -"or encrypting." +"To add these scripts in the Checkmk WATO, copy them into your Checkmk " +"installation directory and make them executable. (Be sure to replace the " +"``zammad.example.com`` callback URL with the one found in your admin panel.)" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:89 -msgid "This is by design and can't be adjusted." +#: ../system/integrations/checkmk/setup-guide.rst:60 +msgid "Service notification" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:4 +#: ../system/integrations/checkmk/setup-guide.rst:46 msgid "" -"All of the system's latest S/MIME activity is displayed in the **Recent " -"Logs** section." +"For updates on the status of the software running on your server (*e.g.,* " +"postgres)." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:11 -msgid "Sample entries of in- and outgoing S/MIME related emails." +#: ../system/integrations/checkmk/setup-guide.rst:75 +msgid "Host notification" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:11 -msgid "" -"Logs report the status and details of all mail, both incoming and outgoing, " -"that used signing/verification or encryption/decryption." +#: ../system/integrations/checkmk/setup-guide.rst:63 +msgid "For updates on the status of the server itself." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:14 +#: ../system/integrations/checkmk/setup-guide.rst:77 +msgid "🤔 **What's with all the env vars?**" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:79 msgid "" -"This log does **not** include email sent by :doc:`triggers ` or the :doc:`scheduler `. For those, check your " -"``production.log``." +"Whenever Checkmk runs these scripts, it needs to provide some information " +"about the event that triggered the notification. This information is passed " +"in the form of these ``$NOTIFY_*`` environment variables." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:20 -msgid "Common Issues" +#: ../system/integrations/checkmk/setup-guide.rst:85 +msgid "" +"You can specify additional parameters to pass to the script when you're " +"setting up your notification rule, but the ones you see here are all " +"provided by default." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:30 -msgid "I received a signed/encrypted email before I set up S/MIME integration" +#: ../system/integrations/checkmk/setup-guide.rst:90 +msgid "Email Alerts" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:23 +#: ../system/integrations/checkmk/setup-guide.rst:94 msgid "" -"No problem. Once S/MIME has been enabled and the appropriate certificates " -"have been added, agents will be prompted to retry verification/decryption on " -"matching emails." +"🐞 **There are known bugs** in Zammad's processing of email from Checkmk. " +"This section will be completed once they have been resolved. (Learn more at " +"GitHub issues `#2377 `_ & " +"`#2180 `_.)" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:0 -msgid "Screenshot of user prompt to retry decryption" +#: ../system/integrations/checkmk/setup-guide.rst:100 +msgid "In the meantime, we encourage you to set up API alerts instead." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:38 -msgid "The 🔒 **Encrypt** button is disabled" +#: ../system/integrations/clearbit.rst:2 +msgid "Clearbit" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:33 -msgid "Have you added the recipient's certificate?" +#: ../system/integrations/clearbit.rst:4 +msgid "" +"With our Clearbit integration, you can easily enrich the information " +"provided by Zammad. If the customers or agents email address is known to " +"Clearbit, it will share all information it has regarding the user with " +"Zammad. Those information can include the following:" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:34 -msgid "Are you sure the recipient's certificate is valid?" +#: ../system/integrations/clearbit.rst:9 +msgid "Avatar" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:35 -msgid "Have you checked your ``production.log`` for more details?" +#: ../system/integrations/clearbit.rst:10 +msgid "Address information" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:37 -msgid "" -"If encryption doesn't work in the composer, it won't work in :doc:`triggers " -"` or the :doc:`scheduler ` either!" +#: ../system/integrations/clearbit.rst:11 +msgid "Website information" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:42 -msgid "The ✅ **Sign** button is disabled" +#: ../system/integrations/clearbit.rst:12 +msgid "A BIO (as Note by default)" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:41 +#: ../system/integrations/clearbit.rst:14 msgid "" -"Have you added **both the certificate and private key** for your " -"organization?" +"If needed, you can add further custom objects and add mappings to them, so " +"the Clearbit information can be filled within the database. In general you " +"can get any information from Clearbit, as long as you have a mapping to an " +"Zammad object." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:42 +#: ../system/integrations/clearbit.rst:21 msgid "" -"Does the email address on the certificate match the email address of the " -"agent/group composing the email?" +"Clearbit does have a mapping of fields like LDAP and Exchange have, but does " +"not \"win\" against Zammad information. This means that if you have e.g. the " +"last name field filled in already and Clearbit has other information on " +"that, it will not be updated." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:45 -msgid "Error: “Fingerprint already taken”" +#: ../system/integrations/clearbit.rst:26 +msgid "" +"However: If let's say the last name has been set by Clearbit and Zammad " +"notices that the last name on the Clearbit source has changed, Zammad will " +"also update this value." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:45 -msgid "Are you sure you haven't added this certificate already?" +#: ../system/integrations/clearbit.rst:33 +msgid "" +"The configuration of Clearbit is really easy and done fast! Just login to " +"your Clearbit-Account, go to \"API\" and copy the secret-API-Key." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:48 -msgid "Error: “❌ invalid byte sequence in UTF-8”" +#: ../system/integrations/clearbit.rst:38 +msgid "" +"Now change to your Zammad instance, go to Integrations (System) -> Clearbit " +"in the admin panel. Paste your API-Key into the API-Key-Field and decide if " +"Zammad should create unknown Organizations automatically, if the user does " +"not have one yet (and Clearbit knows it). The shared option decides if the " +"new organizations Zammad creates with Clearbit should be shared ones." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:48 -msgid "Please ensure to provide PEM formatted certificate and keys." +#: ../system/integrations/clearbit.rst:47 +msgid "" +"If you're unsure what option to choose, better stick with \"no\". You can " +"also learn more about :doc:`/manage/organizations/index`." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:49 -msgid "Did you check if the provided file is a valid certificate or key?" +#: ../system/integrations/clearbit.rst:52 +msgid "" +"The Mapping option works similar to the mapping within the Exchange and LDAP " +"sync. You can add further mappings for e.g. custom fields if you need more " +"information that Clearbit can provide." msgstr "" -#: ../system/integrations/zabbix.rst:2 -msgid "Zabbix Integration" +#: ../system/integrations/clearbit.rst:58 +msgid "" +"If you want to add more Clearbit fields and want to learn more about " +"available fields on their API, you can take a look at their `API " +"documentation `_." msgstr "" -#: ../system/integrations/zabbix.rst:5 +#: ../system/integrations/clearbit.rst:62 msgid "" -"This guide describes how to integrate your Zabbix 5.4 installation with " -"Zammad using the Zabbix webhook feature. This guide will provide " -"instructions on setting up a media type, a user and an action in Zabbix." +"If you're happy with the above chosen Settings and your mapping, just save " +"the changes and enable Clearbit integration. Zammad will now start polling " +"the Clearbit API as users contact you." msgstr "" -#: ../system/integrations/zabbix.rst:12 -msgid "Zammad with enabled HTTP Token Authentication" +#: ../system/integrations/clearbit.rst:68 +msgid "" +"Zammad does not synchronize with Clearbit on a regular basis, but on demand " +"if needed. This saves API calls." msgstr "" -#: ../system/integrations/zabbix.rst:13 -msgid "Zabbix version 5.4 or higher" +#: ../system/integrations/clearbit.rst:73 +msgid "" +"Below the Settings and Mappings, you'll find our Integration log. You can " +"see what requests Zammad sent to Clearbit and also the APIs Response." msgstr "" -#: ../system/integrations/zabbix.rst:16 -msgid "Setting up a Zammad" +#: ../system/integrations/clearbit.rst:78 +msgid "" +"By the way, you can also view the API log on the Clearbit website - the " +"information seen is basically the same." msgstr "" -#: ../system/integrations/zabbix.rst:18 -msgid "Enable **API Token Access** in Settings > System > API." +#: ../system/integrations/clearbit.rst:84 +msgid "Example When Adding a User" msgstr "" -#: ../system/integrations/zabbix.rst:20 +#: ../system/integrations/clearbit.rst:86 msgid "" -"Create a **new user** for a Zabbix alerter with an **email address** and " -"create a personal user token with **ticket.agent** permissions." +"To show you how fast information is added, we added a small Screencast " +"below. This shows the creation of the User Alex from Clearbit. As we already " +"set the last name of Alex to \"X\", Zammad did not update it. What Zammad " +"did was to add further information it received from Clearbit." msgstr "" -#: ../system/integrations/zabbix.rst:24 -msgid "Zabbix Webhook Configuration" +#: ../system/integrations/cti/generic.rst:2 +msgid "CTI (generic)" msgstr "" -#: ../system/integrations/zabbix.rst:27 -#, fuzzy -msgid "Create a Global Macro" -msgstr "Macros" - -#: ../system/integrations/zabbix.rst:29 +#: ../system/integrations/cti/includes/introduction.include.rst:1 msgid "" -"Before setting up the **Webhook**, you need to setup the global macro " -"**{$ZABBIX.URL}**, which must contain the **URL** to the **Zabbix frontend**." +"This integration enables Zammad to provide a caller log to your agents. With " +"this your agents can greet your customers by their name and are supported by " +"Zammad with automatically opening a new ticket dialog or the user profile." msgstr "" -#: ../system/integrations/zabbix.rst:33 +#: ../system/integrations/cti/includes/introduction.include.rst:6 msgid "" -"In the **Administration** > **Media types** section, import the `Template`_." -msgstr "" - -#: ../system/integrations/zabbix.rst:38 -msgid "Open the added **Zammad** media type and set:" +"Click the toggle next to the heading to activate or deactivate this " +"integration." msgstr "" -#: ../system/integrations/zabbix.rst:40 -msgid "**zammad\\_access\\_token** to the your **Personal User Token**" +#: ../system/integrations/cti/includes/introduction.include.rst:9 +msgid "" +"If you want to learn more on how your agents can use this function, please " +"refer the :user-docs:`user documentation `." msgstr "" -#: ../system/integrations/zabbix.rst:41 +#: ../system/integrations/cti/includes/introduction.include.rst:14 msgid "" -"**zammad\\_url** to the **frontend URL** of your **Zammad** installation" +"Automatically opening new ticket dialogues or user profiles requires agent " +"to extension mapping - see more below." msgstr "" -#: ../system/integrations/zabbix.rst:43 -msgid "**zammad\\_customer** to your **Zammad user email**." +#: ../system/integrations/cti/includes/introduction.include.rst:20 +msgid "Please note the following limitations to reduce confusion later on:" msgstr "" -#: ../system/integrations/zabbix.rst:44 -msgid "" -"**zammad\\_enable\\_tags** to **true** or **false** to enable or disable " -"trigger tags. **Important**: if you enable tag support, each tag is set with " -"a separate request." +#: ../system/integrations/cti/includes/introduction.include.rst:22 +msgid "CTI integrations provide caller log functions only." msgstr "" -#: ../system/integrations/zabbix.rst:48 +#: ../system/integrations/cti/includes/introduction.include.rst:23 msgid "" -"If you want to prioritize issues according to **severity** values in Zabbix, " -"you can define mapping parameters:" +"This integration does not provide any VoIP functionalities; you can't make " +"phone calls from within Zammad." msgstr "" -#: ../system/integrations/zabbix.rst:51 -msgid "**severity\\_**: Zammad priority ID" +#: ../system/integrations/cti/includes/introduction.include.rst:25 +msgid "" +"If your browser supports ``tel``-URLs, you can click on phone numbers for " +"automatic dialing. This requires additional software / configuration on your " +"agent's computers." msgstr "" -#: ../system/integrations/zabbix.rst:53 -msgid "Click the **Update** button to save the **Webhook** settings." +#: ../system/integrations/cti/generic.rst:9 +#: ../system/integrations/cti/placetel.rst:14 +#: ../system/integrations/cti/sipgate.rst:14 +msgid "Please provide the following requirements:" msgstr "" -#: ../system/integrations/zabbix.rst:55 +#: ../system/integrations/cti/generic.rst:11 msgid "" -"To receive notifications in **Zammad**, you need to create a **Zabbix user** " -"and add **Media** with the **Zammad** type." +"A telephone system that supports webhooks (outbound) (best option are those " +"that allow customizing the calls)." msgstr "" -#: ../system/integrations/zabbix.rst:58 -msgid "" -"For **Send to**: enter any text, as this value is not used, but is required." +#: ../system/integrations/cti/generic.rst:13 +msgid "A unique Call-ID during the call session." msgstr "" -#: ../system/integrations/zabbix.rst:61 -msgid "" -"For more information, use the `Zabbix documentation `_." +#: ../system/integrations/cti/generic.rst:14 +msgid "Call event data (both numbers and direction)." msgstr "" -#: ../system/maintenance.rst:2 -msgid "Maintenance" +#: ../system/integrations/cti/generic.rst:15 +msgid "Your Zammad instance must be reachable for your telephony system." msgstr "" -#: ../system/maintenance.rst:4 +#: ../system/integrations/cti/generic.rst:17 msgid "" -"Zammad comes with a maintenance mode that you can use for e.g. updating the " -"instance or changing settings while restricting availability and functions." -msgstr "" - -#: ../system/maintenance.rst:13 -msgid "Mode" +"If you want to learn more on what kind of requests are supported by Zammad " +"and what it expects, please consult our :docs:`CTI-API documentation `." msgstr "" -#: ../system/maintenance.rst:8 -msgid "The mode setting allows you to enable or disable the maintenance mode." +#: ../system/integrations/cti/generic.rst:22 +#: ../system/integrations/cti/placetel.rst:27 +#: ../system/integrations/cti/sipgate.rst:30 +msgid "Available Settings" msgstr "" -#: ../system/maintenance.rst:10 -msgid "Defaults to *off*." +#: ../system/integrations/cti/generic.rst:29 +#: ../system/integrations/cti/placetel.rst:41 +#: ../system/integrations/cti/sipgate.rst:40 +msgid "Endpoint Settings" msgstr "" -#: ../system/maintenance.rst:12 +#: ../system/integrations/cti/generic.rst:25 msgid "" -"The maintenance mode will restrict access to administrative roles only. This " -"means agents and customers are logged off." -msgstr "" - -#: ../system/maintenance.rst:23 -msgid "@Login" +"Zammad will list your generic CTI endpoint here. It contains a unique token " +"so ensure to keep this URL save." msgstr "" -#: ../system/maintenance.rst:16 +#: ../system/integrations/cti/generic.rst:28 msgid "" -"This setting allows you to provide a login message within a green banner " -"above the login screen. Click into the green banner in the settings page to " -"adjust your message. To activate the message, activate the *@Login* setting." +"You'll need this endpoint for your PBX to talk to Zammad, see :docs:`CTI-API " +"documentation `." msgstr "" -#: ../system/maintenance.rst:0 +#: ../system/integrations/cti/includes/important-dont-forget-saving.include.rst:3 msgid "" -"Screenshot showing the default login message within the\n" -"settings page" +"All following options **do not save automatically**. Always use the Save " +"button on the lower end of the integration page!" msgstr "" -#: ../system/maintenance.rst:26 -msgid "" -"Send an informative message to **all active sessions**. This comes handy to " -"inform your agents e.g. about mayor outages or to force reloads after " -"configuration changes." -msgstr "" - -#: ../system/maintenance.rst:31 -msgid "This is the messages title (slightly bigger than the normal message)." -msgstr "" - -#: ../system/maintenance.rst:34 -msgid "The text you want to provide to your logged in sessions." +#: ../system/integrations/cti/generic.rst:43 +#: ../system/integrations/cti/placetel.rst:49 +#: ../system/integrations/cti/sipgate.rst:52 +msgid "Call Settings" msgstr "" -#: ../system/maintenance.rst:39 -msgid "Reload application" +#: ../system/integrations/cti/generic.rst:39 +#: ../system/integrations/cti/placetel.rst:49 +#: ../system/integrations/cti/sipgate.rst:37 +#: ../system/integrations/cti/sipgate.rst:50 +msgid "Inbound" msgstr "" -#: ../system/maintenance.rst:37 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:1 msgid "" -"Selecting this option will change the message acceptance button from *Close* " -"(with nothing happening) to *Continue session*, which forces the application " -"to reload." +"This option allows you to block specific incoming caller IDs. It allows you " +"to temporarily reject e.g. spam callers without having to contact providers " +"or PBX administrators." msgstr "" -#: ../system/maintenance.rst:43 -msgid "" -"If you have customers that are logged in to Zammad, they'll also be notified " -"if they're active in that moment." +#: ../system/integrations/cti/includes/inbound-calls.include.rst:11 +msgid "Caller ID to block" msgstr "" -#: ../system/maintenance.rst:48 -msgid "Example without reload application" +#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 +msgid "Provide caller IDs to block in ``E.164`` format." msgstr "" -#: ../system/maintenance.rst:52 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:8 msgid "" -"Message setting within Zammad's admin settings without ticket reload " -"application setting." +"Your telephony system has to support this function. Zammad will send a " +"``reject`` response which will cause your telephony system to hang up the " +"call. To callers this usually will feel like the line is busy." msgstr "" -#: ../system/maintenance.rst:0 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:14 msgid "" -"Screenshot showing the send message settings without ticket\n" -"reload application set" +"Provide a meaningful note for your fellow administrators to remind yourself " +"why you've chosen to block the number." msgstr "" -#: ../system/maintenance.rst:61 ../system/maintenance.rst:85 -msgid "" -"The modal all other active sessions will see upon pressing *Send to clients*." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:17 +#: ../system/integrations/cti/sipgate.rst:40 +msgid "Outbound" msgstr "" -#: ../system/maintenance.rst:0 +#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:1 msgid "" -"Screenshot showing modal caused by maintenance's message\n" -"without reload application ticket" +"In many cases you may want to use a different caller ID depending on the " +"destination you're calling. This may apply due to specific connection rates " +"to other countries or because you want your customer to feel you're calling " +"from the same country." msgstr "" -#: ../system/maintenance.rst:72 -msgid "Example with reload application" +#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:6 +msgid "This option expects ``E.164`` number formats." msgstr "" -#: ../system/maintenance.rst:76 -msgid "" -"Message setting within Zammad's admin settings with ticket reload " -"application setting." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 +msgid "Destination caller ID" msgstr "" -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing the send message settings with ticket\n" -"reload application set" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:5 +msgid "The caller ID or number you're trying to call." msgstr "" -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing modal caused by maintenance's message\n" -"with reload application ticket" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:7 +msgid "You can use wildcards for e.g. country specific outbound numbers like:" msgstr "" -#: ../system/monitoring.rst:2 -msgid "Monitoring" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:9 +msgid "``49*`` for Germany" msgstr "" -#: ../system/monitoring.rst:4 -msgid "" -"This function is only available in self hosted instances. If you use Zammad " -"in our cloud, we are monitoring the system on our own and take steps to fix " -"potential problems directly." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:10 +msgid "``4930*`` for Berlin / Germany landlines" msgstr "" -#: ../system/monitoring.rst:11 -msgid "" -"On the monitoring page, you can see the current health state of Zammad under " -"\"*Current Status*\" at the bottom. This can be useful if you want to have a " -"look if everything is up and running. As an example, you could have a look " -"in the monitoring when you assume that some emails aren't processed from " -"Zammad." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 +msgid "``33*`` for France" msgstr "" -#: ../system/monitoring.rst:17 -msgid "**Can't receive an email and the monitoring response is \"healthy\"?**" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:15 +msgid "Set Outbound caller ID" msgstr "" -#: ../system/monitoring.rst:19 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:14 msgid "" -"Zammad will just inform you about unprocessable emails. This is not the case " -"for oversized emails. You can adjust the maximum email size in :doc:`../" -"channels/email/settings`." +"The outbound caller ID to set (the number your customer sees on his display) " +"in ``E.164`` number format." msgstr "" -#: ../system/monitoring.rst:24 -msgid "Monitoring API" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 +msgid "Provide a short description for fellow administrators." msgstr "" -#: ../system/monitoring.rst:26 +#: ../system/integrations/cti/includes/generic-cti-support-note.includes.rst:3 msgid "" -"Beside the indication in the monitoring page, you can also use an external " -"monitoring tool to monitor Zammad's health. To request the health of Zammad, " -"you need to provide the API key (token) to the external monitoring tool. You " -"can copy the token from the \"*Current Token*\" field as well as the whole " -"API endpoint of your system (\"*Health Check*\" field), in which the API " -"token is already included." -msgstr "" - -#: ../system/monitoring.rst:37 -msgid "Screenshot showing Current Token and Health Check" +"This option requires your PBX to send a specific request to Zammad *before " +"dialing*. Please consult the :docs:`CTI API ` in case " +"you're not sure." msgstr "" -#: ../system/monitoring.rst:37 -msgid "Screenshot showing Token and Health Check" +#: ../system/integrations/cti/generic.rst:52 +#: ../system/integrations/cti/placetel.rst:54 +#: ../system/integrations/cti/sipgate.rst:59 +msgid "Other Settings" msgstr "" -#: ../system/monitoring.rst:39 +#: ../system/integrations/cti/includes/other-settings-intro.include.rst:1 msgid "" -"In addition to that, you can reset the auto-generated token to make sure " -"that already configured monitoring systems won't work anymore. So, please " -"use this \"*Reset*\" button only if you know what you do!" -msgstr "" - -#: ../system/monitoring.rst:44 -msgid "Example Output" -msgstr "" - -#: ../system/monitoring.rst:0 -msgid "No issues found" -msgstr "" - -#: ../system/monitoring.rst:48 ../system/monitoring.rst:60 -msgid "**Indicator in Zammad**:" -msgstr "" - -#: ../system/monitoring.rst:0 -msgid "Screenshot showing monitoring with no issues" -msgstr "" - -#: ../system/monitoring.rst:54 ../system/monitoring.rst:66 -msgid "**API response**::" -msgstr "" - -#: ../system/monitoring.rst:0 -msgid "Issues were found" +"Below you can find all available additional settings for this CTI " +"integration. For your overview we're sorting them by appearance and " +"reference their description first." msgstr "" -#: ../system/monitoring.rst:0 -msgid "Screenshot showing monitoring with issues" +#: ../system/integrations/cti/includes/default-caller-id.include.rst:2 +#: ../system/integrations/cti/includes/default-caller-id.include.rst:1 +msgid "Default caller ID for outbound calls" msgstr "" -#: ../system/objects.rst:2 -msgid "Objects" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:16 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:15 +msgid "Shown records in caller log" msgstr "" -#: ../system/objects.rst:4 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:2 msgid "" -"In Zammad you can add your own fields to tickets, users, organizations and " -"even groups (these are called \"objects\"). This can be useful if you need " -"to add further information to a ticket or any other object in Zammad and the " -"information doesn't fit in any existing field." +"Allows you to set the number of shown caller log entries for all users. You " +"can choose from the following values:" msgstr "" -#: ../system/objects.rst:11 -msgid "" -"Try to avoid deleting attributes (and disable them instead) as Zammad might " -"run into unexpected conditions if they are referenced somewhere." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:5 +msgid "60 (default)" msgstr "" -#: ../system/objects.rst:16 -msgid "" -"Here's an overview of object attributes. On the upper right you can add new " -"attributes. By default, there will be no custom fields - standard attributes " -"will be grayed out, you can't delete or change those. You can edit custom " -"attributes (they are displayed in black font and have a trash bin on the " -"right side) just by clicking on them." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:6 +msgid "120" msgstr "" -#: ../system/objects.rst:24 -msgid "" -"Attributes you add to Zammad, no matter if they have default values or not, " -"will not update existing information. This means a new ticket field " -"technically will be empty unless you populate it." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:7 +msgid "180" msgstr "" -#: ../system/objects.rst:28 -msgid "" -"Especially in ticket scope this also means that newly added attributes will " -"be indicated as \"changed\" to agents that view the ticket. This may " -"interfere with Zammad's tabs behavior." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:8 +msgid "240" msgstr "" -#: ../system/objects.rst:40 -msgid "Ordering Attributes" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:9 +msgid "300" msgstr "" -#: ../system/objects.rst:42 -msgid "" -"Since Zammad introduced :doc:`/system/core-workflows` the need to have a " -"custom positioning for attributes has become more important than ever." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:11 +msgid "**🥵 Potential performance issue**" msgstr "" -#: ../system/objects.rst:45 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:13 msgid "" -"To adjust the position of such an attribute, simply click on the attribute " -"entry in question, scroll down and adjust the position number. Please note " -"that you cannot change the positioning of default attributes." +"Setting this setting higher than 60 may cause serious performance issues on " +"very busy instances. Keep in mind that this setting causes Zammad to poll " +"and send up to 300 records to *all active agent sessions* in very short time " +"periods." msgstr "" -#: ../system/objects.rst:49 -msgid "" -"In case two attributes have the same position value, Zammad will sort " -"alphabetically by name automatically." +#: ../system/integrations/cti/generic.rst:73 +msgid "Caller Log Filter" msgstr "" -#: ../system/objects.rst:None +#: ../system/integrations/cti/generic.rst:55 msgid "" -"Screenshot showing custom attribute entries ordered in between default ones" -msgstr "" - -#: ../system/objects.rst:56 -msgid "Updating Database After Adding or Editing Attributes" +"This function allows you to provide call information based on e.g. queues " +"only to agents that really need the information." msgstr "" -#: ../system/objects.rst:58 +#: ../system/integrations/cti/generic.rst:58 msgid "" -"When adding or changing attributes, Zammad will not apply the changes " -"instantly, but instead shows you the changed attributes first. If you're " -"ready to go, just click on \"Update database\" to apply the changes to " -"Zammad. If you made a mistake or just want to discard your changes, click " -"\"Discard changes\"." +"Why? If you have a team for several countries or departments, you don't want " +"to bug your agents from other departments. Leaving these options empty will " +"fallback to showing everything to everyone." msgstr "" -#: ../system/objects.rst:64 -msgid "" -"After applying the changes with \"Update Database\", a restart of Zammad is " -"**mandatory**. If you don't perform it, you may experience unexpected " -"behavior or even errors. You may want to do this kind of configuration " -"during maintenance windows." +#: ../system/integrations/cti/generic.rst:64 +msgid "Destination caller ID or Queue" msgstr "" -#: ../system/objects.rst:72 +#: ../system/integrations/cti/generic.rst:63 msgid "" -"Changes on objects require you to update the database to apply these changes." -msgstr "" - -#: ../system/objects.rst:75 -msgid "**🤓 Service restarts can be automated**" +"This depends on your PBX and usually is either a queue ID, phone number or " +"extension." msgstr "" -#: ../system/objects.rst:0 -msgid "Hosted environments automatically restart for you." +#: ../system/integrations/cti/generic.rst:69 +msgid "Agents" msgstr "" -#: ../system/objects.rst:0 +#: ../system/integrations/cti/generic.rst:67 msgid "" -"If you're using a self-hosted installation you can use :docs:`environment " -"variables `" -msgstr "" - -#: ../system/objects.rst:82 -msgid "System Attributes" +"Select the agents that are responsible for the group. These agents will then " +"see caller log entries and call notifications fitting to said queue." msgstr "" -#: ../system/objects.rst:84 +#: ../system/integrations/cti/generic.rst:0 msgid "" -"Zammad comes with pre-configured attributes. Some of them can't be edited " -"via UI (or at all). This is required for proper operation of Zammad and not " -"a bug." +"Screenshot showing the caller log filter table with pre filled sample data" msgstr "" -#: ../system/objects.rst:90 -msgid "Ticket State" +#: ../system/integrations/cti/includes/recent-logs.include.rst:6 +msgid "" +"With recent logs Zammad allows you to view the latest calls for the CTI " +"functionality. This usually comes in handy, when you're looking for errors." msgstr "" -#: ../system/objects.rst:92 +#: ../system/integrations/cti/includes/recent-logs.include.rst:0 msgid "" -"If the pre-configured states aren't enough for you or you want to change " -"them, you can do so by clicking on the cogwheel icon in the state row in the " -"ticket tab. But you should be careful when changing pre-configured states. " -"This can lead to unwanted behavior in some cases." +"Screenshot showing several incoming requests within Recent logs section." msgstr "" -#: ../system/objects.rst:None -msgid "Screenshot showing highlighted ticket state attribute" +#: ../system/integrations/cti/includes/recent-logs.include.rst:16 +msgid "I'm just here to clear floats up." msgstr "" -#: ../system/objects.rst:122 -msgid "Handling of states" +#: ../system/integrations/cti/includes/recent-logs.include.rst:20 +msgid "" +"By clicking on the entry of interest, Zammad will provide more details on " +"the call in question. You'll see the payload it received and also the " +"response that was sent." msgstr "" -#: ../system/objects.rst:102 +#: ../system/integrations/cti/includes/recent-logs.include.rst:0 msgid "" -"In the state configuration screen, you can add new states, disable states or " -"change states." +"Screenshot showing detailed information of a specific log entry of recent " +"logs" msgstr "" -#: ../system/objects.rst:0 -msgid "Screenshot showing table of default ticket states" +#: ../system/integrations/cti/includes/recent-logs.include.rst:31 +msgid "x" msgstr "" -#: ../system/objects.rst:110 -msgid "" -"To add a new state, click on the \"New Ticket State\" button in the top " -"right corner. To change an existing state, simply click on the affected " -"state. This opens an edit dialog." +#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 +#: ../system/integrations/cti/includes/troubleshooting.include.rst:9 +msgid "My Phone page stays blank, signalling does work..." msgstr "" -#: ../system/objects.rst:114 +#: ../system/integrations/cti/includes/troubleshooting.include.rst:5 msgid "" -"You can also clone a state or set them to \"Default for new tickets\" or " -"\"Default for follow-ups\" by clicking on the ⁝ action button and select the " -"desired function." +"If you've made sure that signalling works (check Recent logs) and your " +"Caller Log still stays empty, please ensure that you only configured one CTI " +"integration version. Specifically defining more than one agent mapping on " +"the different integration variants will be the issue." msgstr "" -#: ../system/objects.rst:118 -msgid "" -"*Default for new tickets* means that this state is used for every newly " -"created ticket." +#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 +msgid "Clear the not needed agent mapping and reload your browser page." msgstr "" -#: ../system/objects.rst:121 +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:1 msgid "" -"*Default for follow-ups* means that this state is used if the ticket is re-" -"opened after it was closed." +"By mapping your agents extension to their existing Zammad users, Zammad can " +"provide a new ticket dialog or open the user profile for the agent that " +"picks up the call." msgstr "" -#: ../system/objects.rst:171 -msgid "Ticket state in detail" +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:5 +msgid "" +"This speeds up ticket aiding, no matter if it's for existing tickets or new " +"ones!" msgstr "" -#: ../system/objects.rst:125 +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:8 msgid "" -"Below you can find a description for each field and option. Please head over " -"to the :ref:`example ` to see the edit dialog." +"To see it work from the agent's perspective, have a look on :user-docs:`user " +"documentation `." msgstr "" -#: ../system/objects.rst:129 -msgid "" -"This is the name of the state and what you and your agents are seeing when " -"choosing a state somewhere (e.g. in tickets, trigger configuration)." +#: ../system/integrations/cti/placetel.rst:2 +msgid "Placetel CTI" msgstr "" -#: ../system/objects.rst:137 -msgid "" -"There are different state types you can choose from. By default, Zammad " -"comes with one state per state type." +#: ../system/integrations/cti/placetel.rst:16 +msgid "You need an administrative Placetel account for your organization." msgstr "" -#: ../system/objects.rst:140 +#: ../system/integrations/cti/placetel.rst:17 +#: ../system/integrations/cti/sipgate.rst:20 msgid "" -"**new**: for states for tickets that are new and it hasn't been worked on " -"them" +"Your Zammad instance must be allowed to communicate to external services." msgstr "" -#: ../system/objects.rst:142 -msgid "" -"**open**: for states for tickets that are in progress and agents are working " -"on them" +#: ../system/integrations/cti/placetel.rst:18 +msgid "Placetel must be able to reach your Zammad instance." msgstr "" -#: ../system/objects.rst:144 -msgid "**merged**: for states for tickets that are merged with other tickets" +#: ../system/integrations/cti/placetel.rst:22 +msgid ":doc:`provider-configurations/placetel`" msgstr "" -#: ../system/objects.rst:145 +#: ../system/integrations/cti/placetel.rst:21 msgid "" -"**pending reminder**: for states for tickets that are in progress and you " -"want to set a reminder. (default example: *pending reminder*)" +"Learn how to configure Placetel to enable Zammad and Placetel to communicate " +"with each other." msgstr "" -#: ../system/objects.rst:147 +#: ../system/integrations/cti/placetel.rst:32 msgid "" -"**pending action**: for states for tickets that are waiting for a specified " -"time and then change their state (default example: *pending close*)" +"The here listed endpoint settings are relevant for the :doc:`integration " +"configuration with Placetel `." msgstr "" -#: ../system/objects.rst:150 -msgid "" -"**closed**: for states for tickets that are finished and do not need to be " -"processed further" +#: ../system/integrations/cti/placetel.rst:37 +#: ../system/integrations/i-doit.rst:53 +msgid "Endpoint" msgstr "" -#: ../system/objects.rst:153 +#: ../system/integrations/cti/placetel.rst:36 msgid "" -"⚠️ Choosing the correct state type is important! If you are in doubt, have a " -"look on the default states and their types!" +"This endpoint will be required for the Zammad integration within the " +"Placetel web interface." msgstr "" -#: ../system/objects.rst:158 -msgid "Ignore escalation" +#: ../system/integrations/cti/placetel.rst:41 +msgid "API Token" msgstr "" -#: ../system/objects.rst:157 +#: ../system/integrations/cti/placetel.rst:40 msgid "" -"Here you can define whether tickets of this state will count to escalation " -"time or not." +"You'll receive this token within the ``Web API`` menu. Make sure to copy " +"this value, it's only shown once!" msgstr "" -#: ../system/objects.rst:161 -msgid "" -"You can create a note for the state to inform other admins about the state. " -"This has no effect on tickets." +#: ../system/integrations/cti/placetel.rst:71 +#: ../system/integrations/cti/sipgate.rst:77 +msgid "Phone Extension to Agent Mapping" msgstr "" -#: ../system/objects.rst:165 -msgid "Set the state to *active* or *inactive*." +#: ../system/integrations/cti/placetel.rst:0 +msgid "Screenshot showing sample user mappings in between Placetel and Zammad" msgstr "" -#: ../system/objects.rst:167 +#: ../system/integrations/cti/placetel.rst:64 msgid "" -"it is technically possible to set all states to inactive. To keep Zammad " -"working in such a case, the inactive flag of one of the states is ignored." +"You can find your agents Placetel username combination required within ⚙️ PBX " +"→ VoIP destinations. Within the \"Advanced settings\" section you're looking " +"for \"SIP user name\" and \"SIP server\"." msgstr "" -#: ../system/objects.rst:194 -msgid "Ticket state example" +#: ../system/integrations/cti/placetel.rst:68 +msgid "Combine these two like so: ``@``." msgstr "" -#: ../system/objects.rst:174 -msgid "" -"Let's assume we want to create a new state which indicates that the ticket " -"has to wait for a response of a third party (e.g. service contractor or " -"manufacturer) and we want to to be able to set a reminder." +#: ../system/integrations/cti/placetel.rst:0 +msgid "Sample VoIP credentials for a Placetel user" msgstr "" -#: ../system/objects.rst:178 -msgid "" -"First we give the new state a proper name. In this example we call it " -"\"waiting for manufacturer\"." +#: ../system/integrations/cti/provider-configurations/placetel.rst:2 +msgid "Setup Placetel connection for Zammad" msgstr "" -#: ../system/objects.rst:181 +#: ../system/integrations/cti/provider-configurations/placetel.rst:6 msgid "" -"As state type we choose \"pending reminder\". This indicates that the ticket " -"is still open and we can set a reminder. This reminder can be useful if our " -"manufacturer sometimes isn't responding or we want to remind him to give us " -"an answer." +"This configuration step requires a *full* administrative Placetel account. " +"You may receive forbidden error messages with Placetel in case your " +"permissions are not high enough." msgstr "" -#: ../system/objects.rst:186 +#: ../system/integrations/cti/provider-configurations/placetel.rst:10 msgid "" -"We choose \"no\" for \"ignore escalation\" because we want to escalate the " -"tickets even if we are waiting on the manufacturer's feedback." +"The following actions can be configured via the `Placetel web interface " +"`_." msgstr "" -#: ../system/objects.rst:189 -msgid "The **result** in the creation dialog will look like this:" +#: ../system/integrations/cti/provider-configurations/placetel.rst:29 +msgid "Step 1: Activate Zammad integration" msgstr "" -#: ../system/objects.rst:0 -msgid "Screenshot showing ticket state creation dialog with example" +#: ../system/integrations/cti/provider-configurations/placetel.rst:14 +msgid "" +"Within Integrations, scroll down to Partner integrations and select Zammad." msgstr "" -#: ../system/objects.rst:197 ../system/objects.rst:199 -msgid "Ticket Priority" +#: ../system/integrations/cti/provider-configurations/placetel.rst:17 +msgid "" +"You can alternatively filter by \"Ticket Systems\" to reduce the number of " +"entries on the page. You'll still want to look for Partner integrations. 🤓" msgstr "" -#: ../system/objects.rst:199 ../system/objects.rst:201 +#: ../system/integrations/cti/provider-configurations/placetel.rst:21 msgid "" -"If the pre-configured priorities aren't enough for you or you want to change " -"them, you can do so by clicking on the cogwheel icon in the priority row in " -"the ticket tab:" +"Within the Zammad integration now press \"Activate\". A new tab ``API`` " +"becomes available - open this tab." msgstr "" -#: ../system/objects.rst:None -msgid "Screenshot showing highlighted ticket priority attribute" +#: ../system/integrations/cti/provider-configurations/placetel.rst:24 +msgid "" +"Now tick \"Enable Call Control / Notify API\" and paste the Placetel " +"endpoint from your Zammad instance into the field \"URL of your API " +"endpoint\". Save to apply the settings" msgstr "" -#: ../system/objects.rst:224 ../system/objects.rst:226 -msgid "Handling of priorities" +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "Screencast showing how to activate the Zammad integration" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:51 +msgid "Step 2: Generate API Token for Placetel" msgstr "" -#: ../system/objects.rst:208 ../system/objects.rst:210 +#: ../system/integrations/cti/provider-configurations/placetel.rst:32 msgid "" -"In the priority configuration screen, you can add new priorities, disable " -"priorities or change priorities." +"Go back to the integrations page and scroll down to \"Web API\". Generate a " +"new API token by using the \"Create a new API token\" button." msgstr "" -#: ../system/objects.rst:0 -msgid "Screenshot showing table of default ticket priorities" +#: ../system/integrations/cti/provider-configurations/placetel.rst:37 +msgid "" +"If you already generated a token either use your existing token or reset it " +"by using above mentioned button. Placetel will ask you to conform this reset." msgstr "" -#: ../system/objects.rst:216 ../system/objects.rst:218 +#: ../system/integrations/cti/provider-configurations/placetel.rst:41 msgid "" -"To add a new priority, click on the \"New Priority\" button in the top right " -"corner. To change an existing priority, simply click on the affected " -"priority. This opens an edit dialog." +"Please keep in mind that existing API scripts may no longer work due to " +"token resets!" msgstr "" -#: ../system/objects.rst:220 ../system/objects.rst:222 +#: ../system/integrations/cti/provider-configurations/placetel.rst:44 msgid "" -"You can also clone a priority or set them to \"Default for new tickets\" by " -"clicking on the ⁝ action button and select the desired function." +"Copy the provided API token and insert it into the \"API Token\" field " +"within Zammad's Placetel integration." msgstr "" -#: ../system/objects.rst:223 ../system/objects.rst:225 +#: ../system/integrations/cti/provider-configurations/placetel.rst:47 msgid "" -"*Default for new tickets* means that this priority is used for every newly " -"created ticket." +"Apply your changes by using the \"Save\" button on the bottom of the " +"Placetel integration page and activate the Placetel integration." msgstr "" -#: ../system/objects.rst:246 ../system/objects.rst:248 -msgid "Priorities in detail" +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "" +"Screencast showing how to retrieve an API token from Placetel for Zammad" msgstr "" -#: ../system/objects.rst:227 ../system/objects.rst:229 -msgid "Below you can find a description for each field and option." +#: ../system/integrations/cti/provider-configurations/placetel.rst:73 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:77 +msgid "Step 3: Restrict the numbers to notify on" msgstr "" -#: ../system/objects.rst:230 ../system/objects.rst:232 +#: ../system/integrations/cti/provider-configurations/placetel.rst:54 msgid "" -"This is the name of the priority and what you and your agents are seeing " -"when choosing a priority somewhere (e.g. in tickets, trigger configuration)." +"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " +"the the Integrations page of the Placetel web interface, go to \"Notify " +"API\"." msgstr "" -#: ../system/objects.rst:240 ../system/objects.rst:242 -msgid "Highlight color" +#: ../system/integrations/cti/provider-configurations/placetel.rst:58 +msgid "" +"Lower on the page Placetel allows you to restrict the numbers to notify on. " +"You'll find this within the \"External routing API\" part." msgstr "" -#: ../system/objects.rst:235 ../system/objects.rst:237 +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 msgid "" -"Switch between *Low priority* (light blue), *High priority* (red) and - " -"(default). This affects the displayed color for ticket titles in overviews." +"Screenshot showing a sample selection of phone numbers to use for the " +"Placetels notify API" msgstr "" -#: ../system/objects.rst:239 ../system/objects.rst:241 -msgid "The color options are currently limited to the mentioned options." +#: ../system/integrations/cti/provider-configurations/placetel.rst:66 +msgid "" +"This menu point also provides a API request log from Placetel view. Just " +"open \"Recent responses of your API endpoint\" to learn more." msgstr "" -#: ../system/objects.rst:243 ../system/objects.rst:245 +#: ../system/integrations/cti/provider-configurations/placetel.rst:69 msgid "" -"You can create a note for the priority to inform other admins about the " -"priority. This has no effect on tickets." +"If you want to see Zammad's perspective, use the \"Recent Logs\" part from " +"within the Placetel integration page." msgstr "" -#: ../system/objects.rst:247 ../system/objects.rst:249 -msgid "Set the priority to *active* or *inactive*." +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "Screenshot showing sample log entries for Placetels API calls to Zammad" msgstr "" -#: ../system/objects/external-data-source-example.rst:2 -msgid "External Data Source" +#: ../system/integrations/cti/provider-configurations/placetel.rst:77 +msgid "Step 4 (optional): Further configurations for Placetel" msgstr "" -#: ../system/objects/external-data-source-example.rst:4 +#: ../system/integrations/cti/provider-configurations/placetel.rst:76 msgid "" -"We assume you already had a look on :doc:`types` where you can find a " -"description of the individual fields." +"If needed, you can now configure Zammad's Placetel integration in more " +"detail. You can learn more about your options here: :ref:`Placetel " +"integration settings `." msgstr "" -#: ../system/objects/external-data-source-example.rst:7 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:2 +msgid "Setup Sipgate connection for Zammad" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"To reproduce this example, choose a category you want to add a custom field, " -"click on *New Attribute* and select *External data source field* under " -"*Format*." +"Sipgate has no english web interface which is why this documentation page is " +"mixing up languages badly." msgstr "" -#: ../system/objects/external-data-source-example.rst:11 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"Our example story is to fetch data from an external product database. We " -"want to add our products to the tickets so that the products can be searched " -"and chosen from a list and also create a link to the product website." +"Please also note that the availability of API addons highly depends on your " +"package trier. Usage of sipgate.io packages *is not free*, please check " +"their `pricing page `_ before!" msgstr "" -#: ../system/objects/external-data-source-example.rst:16 -msgid "Base configuration" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:35 +msgid "Step 1: Book sipgate.io package" msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Initial steps to configure external data source object type" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:13 +msgid "Skip to step 2 if you already have the package booked!" msgstr "" -#: ../system/objects/external-data-source-example.rst:23 -#: ../system/variables.rst:85 -msgid "**Example:**" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:15 +msgid "" +"Login to an administrative Sipgate account and navigate to " +"``Accountverwaltung``. You'll see several different options depending on " +"your booked packages. Select ``Verträge & Produkte`` to continue." msgstr "" -#: ../system/objects/external-data-source-example.rst:25 -msgid "Name: *product*" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:19 +msgid "" +"Scroll down to the section ``Zusätzliche Produkte buchen`` and look for " +"``sipgate.io`` - select this product by using the ``Produkte anzeigen``-" +"Button." msgstr "" -#: ../system/objects/external-data-source-example.rst:26 -msgid "Display: *Product*" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:23 +msgid "" +"On the next page select either one of the ``sipgate.io`` packages or ``Push-" +"API Package Free``. Follow the dialogue by booking the addon. You'll be " +"returned to your contract overview and now should see the selected addon in " +"your list." msgstr "" -#: ../system/objects/external-data-source-example.rst:29 -msgid "External data source configuration" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:30 +msgid "" +"The availability for ``sipgate.io`` packages and their levels highly depends " +"on the overall account type and product you've booked with Sipgate." msgstr "" -#: ../system/objects/external-data-source-example.rst:31 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"First, enter the search URL making sure it contains ``#{search.term}`` as a " -"parameter:" +"Screencast showing the process on how to book the required sipgate.io addon" msgstr "" -#: ../system/objects/external-data-source-example.rst:34 -msgid "**Example:** ``https://dummyjson.com/products/search?q=#{search.term}``" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:52 +msgid "Step 2: Configure webhook for Zammad" msgstr "" -#: ../system/objects/external-data-source-example.rst:36 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:38 msgid "" -"After that, head down to the preview section and enter a search input for " -"the external data source." +"Within your ``Accountverwaltung`` navicate to your product ``sipgate.io``. " +"In the newly opened tab, switch from \"Clients\" to \"Webhooks\" and paste " +"the endpoint URLs from your Zammad instance like so:" msgstr "" -#: ../system/objects/external-data-source-example.rst:39 -msgid "**Example:** ``mac``" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:42 +msgid "Inbound endpoint to \"Incoming\"" msgstr "" -#: ../system/objects/external-data-source-example.rst:41 -msgid "Then you can find a preview of the response data below:" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:43 +msgid "Outbound endpoint to \"Outgoing\"" msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of JSON response based on search term" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:47 +msgid "" +"Ensure to select at least one call group or phoneline within \"Sources\". " +"Other wise Sipgate will not indicate any incoming or outgoing calls to " +"Zammad." msgstr "" -#: ../system/objects/external-data-source-example.rst:48 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"We recommend using the preview to have a look on the structure. There is a " -"top-level element called ``products``. One level below, you can find the " -"attributes ``id`` and ``title``." +"Screencast showing how to add Zammad's endpoint URLs to sipgate.ios webhook " +"configuration" msgstr "" -#: ../system/objects/external-data-source-example.rst:52 -msgid "**Search result response based on search from example:**" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:55 +msgid "" +"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " +"the Webhooks → URLs section of Sipgate you can select which *sources* " +"Sipgate should notify Zammad about in- and outgoing calls." msgstr "" -#: ../system/objects/external-data-source-example.rst:119 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:59 msgid "" -"To tell the remote system that the desired data is located below the " -"``products`` level, you have to put it in the field *Search result list key*." +"Use either specific phone lines or use the option \"Use for all phonelines " +"and groups\" to notify Zammad about all existing lines of your Sipgate " +"account." msgstr "" -#: ../system/objects/external-data-source-example.rst:122 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"After inserting ``products`` in the mentioned field, you get an extended " -"preview. You can find an additional box *Search result list* with a JSON " -"structure. This is the same response as before but stripped from the upper " -"``products`` element by the external data source." +"Screenshot showing a sample selection of phone numbers to use for the " +"Sipgates webhooks API" msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of JSON response search result list" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:68 +msgid "This section also allows you to enable a Debug log." msgstr "" -#: ../system/objects/external-data-source-example.rst:132 -msgid "" -"Now you need to provide the keys for the search result values and labels. As " -"already mentioned, we are looking for the ``id`` and the ``title`` of our " -"products. If you haven't already, it is now a good time to look at the " -"preview of the *Search result list*." +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "Screenshot showing an enabled Debug log option" msgstr "" -#: ../system/objects/external-data-source-example.rst:197 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:73 msgid "" -"After locating our two keys, we insert them in *search result value key* " -"(``id``) and in *Search result label key* (``title``)." +"After enabling you can use the Debug log section to see all sent webhook " +"calls to Zammad. You'll also can see the response." msgstr "" -#: ../system/objects/external-data-source-example.rst:200 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"Basically, we configured the external data source already and we can see a " -"table in the preview section:" +"Screenshot showing sample log entries for Sipgates webhook calls to Zammad" msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of product table based on search term" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:81 +msgid "Step 4 (optional): Further configurations for Sipgate" msgstr "" -#: ../system/objects/external-data-source-example.rst:208 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:80 msgid "" -"According to our example story, now just the *Link template* is missing." +"If needed, you can now configure Zammad's Sipgate integration in more " +"detail. You can learn more about your options here: :ref:`Sipgate " +"integration settings `." msgstr "" -#: ../system/objects/external-data-source-example.rst:210 -msgid "" -"Please note that this is an optional feature. If you don't want to use such " -"links, of course you don't have to configure it." +#: ../system/integrations/cti/sipgate.rst:2 +msgid "Sipgate (sipgate.io)" msgstr "" -#: ../system/objects/external-data-source-example.rst:213 -msgid "" -"We can add now an address where additional product information can be found." +#: ../system/integrations/cti/sipgate.rst:16 +msgid "You need an administrative Sipgate account for your organization." msgstr "" -#: ../system/objects/external-data-source-example.rst:215 -msgid "Example: ``https://your_domain.com/q=#{ticket.product}``" +#: ../system/integrations/cti/sipgate.rst:17 +msgid "" +"Zammad requires a ``sipgate.io`` addon from the feature store (please note " +"that API calls are not free with Sipgate. Rates may apply and differ from " +"account to account)." msgstr "" -#: ../system/objects/external-data-source-example.rst:217 -msgid "In the example, the parameter means:" +#: ../system/integrations/cti/sipgate.rst:21 +msgid "Sipgate must be able to reach your Zammad instance." msgstr "" -#: ../system/objects/external-data-source-example.rst:219 -msgid "``#{}``: \"Frame\" for the insertion of information" +#: ../system/integrations/cti/sipgate.rst:25 +msgid ":doc:`provider-configurations/sipgate`" msgstr "" -#: ../system/objects/external-data-source-example.rst:220 -msgid "``ticket``: object level, where you create your custom object" +#: ../system/integrations/cti/sipgate.rst:24 +msgid "" +"Learn how to configure Sipgate to enable Zammad and Sipgate to communicate " +"with each other." msgstr "" -#: ../system/objects/external-data-source-example.rst:221 -msgid "``product``: name of the (custom) object" +#: ../system/integrations/cti/sipgate.rst:33 +msgid "" +"Below endpoint settings affect the :doc:`sipgate.io configuration `." msgstr "" -#: ../system/objects/external-data-source-example.rst:223 -msgid "" -"After configuring your *Link template*, there will be another column in the " -"preview. Hovering on the icons in the *Link* column will show you where it " -"forwards you." +#: ../system/integrations/cti/sipgate.rst:37 +msgid "This endpoint is required for incoming call hooks." msgstr "" -#: ../system/objects/external-data-source-example.rst:232 -msgid "" -"In our example, one of the links looks like: https://your_domain.com/q=6, " -"where the 6 is the product id." +#: ../system/integrations/cti/sipgate.rst:40 +msgid "This endpoint is required for outgoing call hooks." msgstr "" -#: ../system/objects/external-data-source-example.rst:235 -msgid "You can find more information regarding the URL in :doc:`types`." +#: ../system/integrations/cti/sipgate.rst:0 +msgid "Screenshot showing sample user mappings in between Sipgate and Zammad" msgstr "" -#: ../system/objects/includes/adding-values-hint.include.rst:3 +#: ../system/integrations/cti/sipgate.rst:69 msgid "" -"Adding values can be tricky for first timers, don't forget to press \"➕ " -"Add\" after typing your values. Otherwise you may loose a value." +"You can find your agent's Sipgate username within ``Accountverwaltung → " +"Benutzer``. You're looking for the SIP-ID." msgstr "" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:1 -#: ../system/objects/includes/reposition-values.include.rst:1 -msgid "**↕️ This field type allows the positioning of its values ↔️**" +#: ../system/integrations/cti/sipgate.rst:0 +msgid "Sample VoIP credentials for a Sipgate user" msgstr "" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:3 -msgid "" -"In order to re-arrange the field values, first edit the field. Then you can " -"use ☰ to drag the values in question to the correct position. If you want to " -"change the layer depth, double click on ☰. With it you can cycle through the " -"available layers." +#: ../system/integrations/cti/sipgate.rst:77 +msgid "Users with several devices also have several SIP-IDs." msgstr "" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:8 -msgid "When you're ready, submit your changes to save the object attribute." +#: ../system/integrations/elasticsearch.rst:2 +msgid "Elasticsearch (SaaS)" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:4 +msgid "" +"The Elasticsearch integration allows you to create a read-only user to use " +"with your favorite reporting tool (e.g. like Grafana)." msgstr "" -#: :0 ../system/objects/types.rst:0 +#: ../system/integrations/elasticsearch.rst:7 msgid "" -"Screencast showing how to re-position values on tree select like\n" -"fields" +"If you want to take full advantage of the Zammad reporting, have a look at " +"our :docs:`Grafana ` " +"setup page as well." msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:3 -msgid "" -"In order to re-arrange the field values, edit the field and scroll below the " -"values. Make sure to tick the option \"Use custom option sort\"." +#: ../system/integrations/elasticsearch.rst:11 ../system/subscription.rst:7 +msgid "**🚧 Hosted environment specific 🚧**" msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:8 +#: ../system/integrations/elasticsearch.rst:13 msgid "" -"If you do not tick this field, all manual positioning you did above will be " -"lost upon saving! ☠️" +"This integration is only available for Hosted setups. In order to use " +"Elasticsearch you'll need the **Plus** subscription." msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:11 +#: ../system/integrations/elasticsearch.rst:16 msgid "" -"Now use ☰ to drag the values in question to the correct position. When " -"you're ready, submit your changes to save the object attribute." +"Self hosted users have all the control over their self hosted Elasticsearch " +"instances." msgstr "" -#: :0 ../system/objects/types.rst:0 -msgid "Screencast showing how to re-position values" +#: ../system/integrations/elasticsearch.rst:None +msgid "Elasticsearch integration page on SaaS environments" msgstr "" -#: ../system/objects/includes/url-template-hint.include.rst:3 +#: ../system/integrations/elasticsearch.rst:27 msgid "" -"This field allows using :ref:`URL fields (Link Templates) `." +"Please note the following limitations of Elasticsearch access on hosted " +"environments:" msgstr "" -#: ../system/objects/permissions.rst:2 -msgid "Attribute Permissions" +#: ../system/integrations/elasticsearch.rst:30 +msgid "access to the Elasticsearch index is read-only access" msgstr "" -#: ../system/objects/permissions.rst:7 +#: ../system/integrations/elasticsearch.rst:31 +msgid "currently you're limited to user only" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:32 msgid "" -"In the object attributes configuration you can define if a field is shown " -"and if the input in the field is mandatory, separated by different screens " -"and for different :doc:`roles/permissions `." +"Reporting tools that require to write into the indexes (like Kibana) are not " +"supported" msgstr "" -#: ../system/objects/permissions.rst:17 -msgid "Screenshot shows object attribute permission table" +#: ../system/integrations/elasticsearch.rst:34 +msgid "IP access restriction is currently not yet supported" msgstr "" -#: ../system/objects/permissions.rst:17 -msgid "" -"Some of the possible permissions and screen options for a user object " -"attribute." +#: ../system/integrations/elasticsearch.rst:37 +msgid "Activating Elasticsearch Access" msgstr "" -#: ../system/objects/permissions.rst:19 +#: ../system/integrations/elasticsearch.rst:39 msgid "" -"Based on the object context (ticket, agent, organization, user), the " -"selectable roles (to be precise: the required permissions) and screens " -"differ. Be aware that these settings aren't affecting data creation via " -"other channels than the UI." +"By default external access to your Elasticsearch index is not active. You " +"can enable the integration at any time if needed." msgstr "" -#: ../system/objects/permissions.rst:24 +#: ../system/integrations/elasticsearch.rst:42 msgid "" -"If you want to have further customization possibilities, you should have a " -"look at the :doc:`core workflows `." +"Please ensure to note down the password provided - you won't have access to " +"it afterwards." msgstr "" -#: ../system/objects/permissions.rst:28 -msgid "Screens" +#: ../system/integrations/elasticsearch.rst:None +msgid "Screencast showing activation of Elasticsearch integration" msgstr "" -#: ../system/objects/permissions.rst:30 -msgid "" -"In the table below you can find an overview about the different permissions " -"and the available screens Zammad distinguishes between." +#: ../system/integrations/elasticsearch.rst:51 +msgid "Connection Settings" msgstr "" -#: ../system/objects/permissions.rst:37 -msgid "Screen" +#: ../system/integrations/elasticsearch.rst:53 +msgid "" +"This section holds the most important general information for accessing your " +"Elasticsearch indexes - such as:" msgstr "" -#: ../system/objects/permissions.rst:38 -msgid "Available for" +#: ../system/integrations/elasticsearch.rst:57 +msgid "A unique subdomain that does not tell your real instance URL." msgstr "" -#: ../system/objects/permissions.rst:40 -msgid "create" +#: ../system/integrations/elasticsearch.rst:61 +msgid "Software" msgstr "" -#: ../system/objects/permissions.rst:41 ../system/objects/permissions.rst:52 -#: ../system/objects/permissions.rst:59 ../system/objects/permissions.rst:73 -msgid "admin.user" +#: ../system/integrations/elasticsearch.rst:60 +msgid "" +"The major version of the search index being used. This is required by some " +"Reporting tools like Grafana." msgstr "" -#: ../system/objects/permissions.rst:42 ../system/objects/permissions.rst:53 -#: ../system/objects/permissions.rst:60 -msgid "admin.organization" +#: ../system/integrations/elasticsearch.rst:64 +msgid "Authentication" msgstr "" -#: ../system/objects/permissions.rst:43 ../system/objects/permissions.rst:54 -#: ../system/objects/permissions.rst:61 -msgid "admin.group" +#: ../system/integrations/elasticsearch.rst:64 +msgid "The authentication type being supported. ``Basic Authentication``" msgstr "" -#: ../system/objects/permissions.rst:44 -msgid "Creation dialog for not yet existing data" +#: ../system/integrations/elasticsearch.rst:67 +msgid "Available Indexes" msgstr "" -#: ../system/objects/permissions.rst:45 -msgid "create_middle" +#: ../system/integrations/elasticsearch.rst:69 +msgid "" +"Within this section we're displaying the -in our opinion- most important " +"indexes for a Zammad instance." msgstr "" -#: ../system/objects/permissions.rst:46 ../system/objects/permissions.rst:50 -#: ../system/objects/permissions.rst:57 ../system/objects/permissions.rst:66 -#: ../system/objects/permissions.rst:70 -#, fuzzy -msgid "ticket.customer" -msgstr "Macros" - -#: ../system/objects/permissions.rst:47 ../system/objects/permissions.rst:51 -#: ../system/objects/permissions.rst:58 ../system/objects/permissions.rst:69 -#, fuzzy -msgid "ticket.agent" -msgstr "Macros" - -#: ../system/objects/permissions.rst:48 -msgid "Ticket create dialog (middle section)" +#: ../system/integrations/elasticsearch.rst:72 +msgid "" +"If you require all indexes or our listing is not good enough for you, point " +"your browser to the URL we're providing and append ``/_aliases?" +"pretty=true``. The result should look like this: ``https://.zammad.com/" +"_aliases?pretty=true``." msgstr "" -#: ../system/objects/permissions.rst:49 -msgid "edit" +#: ../system/integrations/elasticsearch.rst:77 +msgid "" +"Your browser will automatically ask for your credentials - you'll then see " +"something like this:" msgstr "" -#: ../system/objects/permissions.rst:55 -msgid "Editing dialog for already existing data" +#: ../system/integrations/elasticsearch.rst:125 +msgid "Credentials" msgstr "" -#: ../system/objects/permissions.rst:56 -msgid "view" +#: ../system/integrations/elasticsearch.rst:127 +msgid "" +"Within this section Zammad displays your available users. The password is " +"provided once (upon activation) and cannot be retrieved after that." msgstr "" -#: ../system/objects/permissions.rst:62 -msgid "View-only dialog for already existing data" +#: ../system/integrations/elasticsearch.rst:131 +msgid "" +"If you need to change or reset your Elasticsearch user password, use the " +"\"Reset password\" button in the credentials table. Doing so creates a brand " +"new password for the account in question. This change is immediate, keep in " +"mind that this may affect third party tools connected to your instance." msgstr "" -#: ../system/objects/permissions.rst:64 -msgid "(e.g. user or organization from search)" +#: ../system/integrations/exchange.rst:2 +msgid "Exchange" msgstr "" -#: ../system/objects/permissions.rst:65 -msgid "signup" +#: ../system/integrations/exchange.rst:4 +msgid "" +"With Zammad's Exchange integration, you can easily use existing address " +"books without having to update more than one source." msgstr "" -#: ../system/objects/permissions.rst:67 -msgid "Sign-up screen for new customers" +#: ../system/integrations/exchange.rst:7 +msgid "" +"However, you should refrain from syncing all addresses, as the results may " +"not be what you expect (Exchange collects huge amounts of addresses). A " +"central address book of your company to sync makes more sense, as you can " +"ensure that Zammad gets only the data you need and want. Apart from this, it " +"is even not possible to sync the Global Address List (GAL) of your Exchange " +"system with Zammad." msgstr "" -#: ../system/objects/permissions.rst:68 -msgid "invite_customer" +#: ../system/integrations/exchange.rst:16 +msgid "" +"**Exchange and LDAP:** The exchange sync can be overruled by Zammad's LDAP " +"integration. If you have the same users in both sources, the LDAP version " +"will always be Zammad's pick." msgstr "" -#: ../system/objects/permissions.rst:71 +#: ../system/integrations/exchange.rst:19 msgid "" -"Customer invitation screen (from :doc:`First Steps ` area)" +"**One way sync:** the Exchange sync is one way. Exchange => Zammad. Changes " +"to your users inside of Zammad might be overwritten by the Exchange sync." msgstr "" -#: ../system/objects/permissions.rst:72 -msgid "invite_agent" +#: ../system/integrations/exchange.rst:24 +msgid "" +"To configure Exchange integration, simply go to the System > Integrations > " +"Exchange in the admin panel. Press \"change\" and follow the wizard for " +"adding the needed Exchange information to Zammad. On the last two steps " +"Zammad will ask you for the address book(s) and your desired attribute " +"mapping. By default, Zammad only maps email address, first- and lastname. " +"Technically, you can map any Exchange object to a Zammad user object (this " +"also works for custom objects!)." msgstr "" -#: ../system/objects/permissions.rst:74 +#: ../system/integrations/exchange.rst:35 msgid "" -"Agent invitation screen (from :doc:`First Steps ` area)" +"If the SSL verification fails while connecting to Exchange, Zammad will ask " +"you to turn it off temporarily." msgstr "" -#: ../system/objects/permissions.rst:78 -msgid "Screen Options" +#: ../system/integrations/exchange.rst:38 +msgid "" +"Please be aware that **turning off SSL verification is a security risk**. It " +"should only be used temporarily or for testing purposes. If turned off, " +"there is no verification of the certificate, which means that every " +"presented certificate will be accepted." msgstr "" -#: ../system/objects/permissions.rst:80 +#: ../system/integrations/exchange.rst:43 msgid "" -"For the different screens you can select \"show\" and \"required\" options." +"After pressing Continue, Zammad will check if the configuration is okay. You " +"can then enable Exchange and start your first sync. The sync will then run " +"hourly - if you need to change mappings or the address book(s), you can " +"change the configuration at any time." msgstr "" -#: ../system/objects/permissions.rst:82 -msgid "**shown:** Show (check) or hide (uncheck) a field." +#: ../system/integrations/exchange.rst:50 +msgid "" +"After the sync has finished, you can find the new Exchange contacts under " +"\"Users\". Zammad integrates them just as normal users." msgstr "" -#: ../system/objects/permissions.rst:83 +#: ../system/integrations/exchange.rst:55 msgid "" -"**required:** Set a field to mandatory (check). Forces users (via UI and " -"API) to populate the field." +"In some cases you might see unique IDs as \"Login\" instead of the email " +"address. This is normal and doesn't affect the login or email mapping for " +"that entry." msgstr "" -#: ../system/objects/types.rst:7 -msgid "Example external data source" +#: ../system/integrations/github.rst:4 +msgid "" +"Use GitHub integration to track GitHub issues directly within Zammad " +"tickets. Add issue hyperlinks and get a live summary of metadata like status " +"(open/closed), assignee, labels, and more." msgstr "" -#: ../system/objects/types.rst:2 -msgid "Attribute types" +#: ../system/integrations/github.rst:8 +msgid "Please note that our GitHub integration does not support pull requests." msgstr "" -#: ../system/objects/types.rst:4 -msgid "" -"When adding a new object attribute, you can choose between the following " -"attribute types." +#: ../system/integrations/github.rst:None +msgid "Integration page for GitHub" msgstr "" -#: ../system/objects/types.rst:14 +#: ../system/integrations/github.rst:18 msgid "" -"You cannot change the attribute format / type as soon as it is applied. If " -"you no longer need an object attribute, consider disabling it instead of " -"removing." +"In your GitHub settings, create a new API token under **Developer settings > " +"Personal access tokens > Generate new token**. Leave the **Scopes** section " +"empty." msgstr "" -#: ../system/objects/types.rst:18 -msgid "**What about the translation of my attributes?**" +#: ../system/integrations/github.rst:0 ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to create a new API token" msgstr "" -#: ../system/objects/types.rst:20 -msgid "" -"For some attribute types you can decide if they should be translatable or " -"not. To be precise, it works only for the selectable fields because the " -"possible choices are known and limited. For the following attribute types, " -"you can set the translatable flag:" +#: ../system/integrations/github.rst:27 +msgid "Create a new API key with no scopes/privileges." msgstr "" -#: ../system/objects/types.rst:25 -msgid "*Boolean field*" +#: ../system/integrations/github.rst:29 +msgid "🔒 **Will this work for private repos?**" msgstr "" -#: ../system/objects/types.rst:26 -msgid "*Single selection field*" +#: ../system/integrations/github.rst:31 +msgid "" +"No. To link private repo issues, **use the** ``repo`` **scope instead**. " +"Bear in mind that the resulting token will have `lots of permissions that it " +"doesn't actually need `_, which presents a security risk if your token ever falls into " +"the wrong hands." msgstr "" -#: ../system/objects/types.rst:27 -msgid "*Multiple selection field*" +#: ../system/integrations/github.rst:37 +msgid "" +"Unfortunately, because of how GitHub's OAuth token scopes are set up, this " +"is the only way to link issues on private repos." msgstr "" -#: ../system/objects/types.rst:28 -msgid "*Single tree selection field*" +#: ../system/integrations/github.rst:40 +msgid "Enter your new API token in Zammad and enable GitHub integration." msgstr "" -#: ../system/objects/types.rst:29 -msgid "*Multiple tree selection field*" +#: ../system/integrations/github.rst:0 +msgid "Screencast showing how to configure Zammad's GitHub integration" msgstr "" -#: ../system/objects/types.rst:31 +#: ../system/integrations/github.rst:47 msgid "" -"For these types, you can find an additional field *Translate field contents*:" +"Use the default API endpoint (``https://api.github.com/graphql``) unless " +"you're using GitHub Enterprise Server." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Screenshot showing translatable attribute types" +#: ../system/integrations/github.rst:50 +msgid "" +"Once completed, a new GitHub issues tab will appear in the ticket pane. 🎉" msgstr "" -#: ../system/objects/types.rst:38 -msgid "Screenshot with example of translatable attribute type" +#: ../system/integrations/github.rst:59 ../system/integrations/gitlab.rst:52 +msgid "Token verification is taking a long time" msgstr "" -#: ../system/objects/types.rst:45 -msgid "Boolean field" +#: ../system/integrations/github.rst:56 ../system/integrations/gitlab.rst:49 +msgid "" +"Slight delays are normal (<2 min.), especially for systems under heavy load." msgstr "" -#: ../system/objects/types.rst:41 +#: ../system/integrations/github.rst:58 msgid "" -"Provides a drop-down field with display values for ``true`` and ``false``. " -"Setting a default is mandatory." +"Self-hosted administrators, please check your network settings to ensure " +"that your Zammad server can reach ``api.github.com``." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Boolean fields" +#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 +msgid "I reloaded the page and now the API token is gone" msgstr "" -#: ../system/objects/types.rst:55 -msgid "Date field" +#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 +msgid "" +"This may indicate that Zammad is still verifying your API token. Try " +"reloading the page again in a couple minutes." msgstr "" -#: ../system/objects/types.rst:48 -msgid "Provides a date picker field and does not allow default values." +#: ../system/integrations/gitlab.rst:2 +msgid "GitLab" msgstr "" -#: ../system/objects/types.rst:52 -msgid "Default time diff (hours)" +#: ../system/integrations/gitlab.rst:4 +msgid "" +"Use GitLab integration to track GitLab issues directly within Zammad " +"tickets. Add issue hyperlinks and get a live summary of metadata like status " +"(open/closed), assignee, labels, and more." msgstr "" -#: ../system/objects/types.rst:51 +#: ../system/integrations/gitlab.rst:8 msgid "" -"This setting helps the user by highlighting the day from now plus the " -"provided value. It *does not* pre-fill the field." +"Please note that our GitLab integration does not support merge requests." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Date fields" +#: ../system/integrations/gitlab.rst:None +msgid "Integration page for GitLab" msgstr "" -#: ../system/objects/types.rst:73 -msgid "Date & time field" +#: ../system/integrations/gitlab.rst:18 +msgid "" +"In your GitLab preferences, create a new API token under **Access Tokens**." msgstr "" -#: ../system/objects/types.rst:58 -msgid "Provides a date and time picker – does not allow default values" +#: ../system/integrations/gitlab.rst:20 +msgid "Under **Select scopes**, choose ``read_api`` only." msgstr "" -#: ../system/objects/types.rst:62 -msgid "Allow future" +#: ../system/integrations/gitlab.rst:27 +msgid "🔒 **If you wish to link issues on any private repos...**" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Forbid dates and times in the future." +#: ../system/integrations/gitlab.rst:29 +msgid "Your API token must belong to an account with access to those repos." msgstr "" -#: ../system/objects/types.rst:66 -msgid "Allow past" +#: ../system/integrations/gitlab.rst:31 +msgid "Enter your new API token in Zammad and enable GitLab integration." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Forbid dates and times in the past." +#: ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to configure Zammad's GitLab integration" msgstr "" -#: ../system/objects/types.rst:70 -msgid "Default time diff (minutes)" +#: ../system/integrations/gitlab.rst:40 +msgid "" +"Use the default API endpoint (``https://gitlab.com/api/graphql``) unless " +"you're a self-hosted GitLab user." msgstr "" -#: ../system/objects/types.rst:69 +#: ../system/integrations/gitlab.rst:43 msgid "" -"This setting helps the user by highlighting the day from now plus the " -"provided value. It does not pre-fill the field." +"Once completed, a new GitLab issues tab will appear in the ticket pane. 🎉" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Date & time fields" +#: ../system/integrations/gitlab.rst:51 +msgid "" +"Self-hosted administrators, please check your network settings to ensure " +"that your Zammad server can reach ``gitlab.com``." msgstr "" -#: ../system/objects/types.rst:86 -msgid "Integer field" +#: ../system/integrations/i-doit.rst:2 +msgid "i-doit" msgstr "" -#: ../system/objects/types.rst:76 +#: ../system/integrations/i-doit.rst:4 msgid "" -"Provides an input field that allows integer usage only. You may define a " -"default value. You cannot enforce comma separation." +"`i-doit `_ is an open-source **configuration " +"management database** - in other words, a tool for keeping tabs on every " +"single piece of your physical and digital infrastructure, from network " +"equipment to virtual machines on down to the faceplates on your rack shelves " +"and more." msgstr "" -#: ../system/objects/types.rst:80 -msgid "Minimal" +#: ../system/integrations/i-doit.rst:10 +msgid "" +"What's that got to do with Zammad? Well, if you used tickets to track issues " +"with all that hardware, you might start wishing there was a way they could " +"talk to each other." msgstr "" -#: ../system/objects/types.rst:80 -msgid "The minimal value the field accepts." +#: ../system/integrations/i-doit.rst:14 +msgid "Zammad gives you two:" msgstr "" -#: ../system/objects/types.rst:83 -msgid "Maximal" +#: ../system/integrations/i-doit.rst:17 +msgid "1. Add i-doit Links to Zammad Tickets" msgstr "" -#: ../system/objects/types.rst:83 -msgid "The maximum value the field accepts." +#: ../system/integrations/i-doit.rst:20 ../system/integrations/i-doit.rst:80 +msgid "What Users See" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Integer fields" +#: ../system/integrations/i-doit.rst:26 +msgid "i-doit integration in Zammad's ticket pane" msgstr "" -#: ../system/objects/types.rst:99 -msgid "Multiple selection field" +#: ../system/integrations/i-doit.rst:26 +msgid "" +"The i-doit integration will appear under a new 🖨 tab in the ticket pane." msgstr "" -#: ../system/objects/types.rst:89 +#: ../system/integrations/i-doit.rst:28 msgid "" -"Provides a selection field that allows the selection of one or more out of " -"several. This field does allow setting a default value." +"i-doit integration puts a new tab in Zammad's ticket pane where you can add " +"links to existing i-doit devices for easy reference. (See our :user-docs:" +"`user documentation ` to learn " +"how it works in practice)." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Multiple selection fields" +#: ../system/integrations/i-doit.rst:36 ../system/integrations/i-doit.rst:93 +msgid "How to Set it Up" msgstr "" -#: ../system/objects/types.rst:112 -msgid "Single selection field" +#: ../system/integrations/i-doit.rst:38 +msgid "" +"It requires i-doit's `API Add-on `_. Make sure to have it properly set up. Use the following setting:" msgstr "" -#: ../system/objects/types.rst:102 +#: ../system/integrations/i-doit.rst:42 +msgid "Active: ``Yes``" +msgstr "" + +#: ../system/integrations/i-doit.rst:43 +msgid "Enforce authentication by username and password: ``No``" +msgstr "" + +#: ../system/integrations/i-doit.rst:45 msgid "" -"Provides a drop-down field that allows selection of one value out of " -"several. This field does allow setting a default value." +"To set it up, enable the integration in the Zammad admin panel under " +"**System > Integrations > i-doit**:" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Single selection fields" +#: ../system/integrations/i-doit.rst:None +msgid "i-doit settings within the integration pages" msgstr "" -#: ../system/objects/types.rst:142 -msgid "Textarea field" +#: ../system/integrations/i-doit.rst:53 +msgid "The root URL of your i-doit installation." msgstr "" -#: ../system/objects/types.rst:115 -msgid "" -"Provides a text area input field (multiple lines) and thus allows e.g. new " -"lines. You can set a default field value." +#: ../system/integrations/i-doit.rst:62 +msgid "API token" msgstr "" -#: ../system/objects/types.rst:120 +#: ../system/integrations/i-doit.rst:56 msgid "" -"Please note that this field *does not* support text formatting or HTML " -"content (rich text)." +"Found in the i-doit admin panel under **Interfaces / external data > JSON-" +"RPC API > Common Settings**." msgstr "" -#: ../system/objects/types.rst:123 -msgid "**🥵 This field can consume a lot of visual space**" +#: ../system/integrations/i-doit.rst:0 +msgid "i-doit administration interface with API configuration" msgstr "" -#: ../system/objects/types.rst:125 -msgid "" -"Depending on where you use this field type, it may use a lot of visual space " -"if you provide a lot of text. This may be an issue to work with." +#: ../system/integrations/i-doit.rst:67 +msgid "Client ID" +msgstr "" + +#: ../system/integrations/i-doit.rst:65 +msgid "A unique name to identify Zammad within i-doit." msgstr "" -#: ../system/objects/types.rst:130 -msgid "Default" +#: ../system/integrations/i-doit.rst:67 +msgid "(Zammad does not require you to enter a value here, but i-doit might!)" msgstr "" -#: ../system/objects/types.rst:129 +#: ../system/integrations/i-doit.rst:70 msgid "" -"The here provided text will be shown within the text area field or new data " -"sets." +"Here you can decide if the certificate of your i-doit system has to be " +"verified or not. In case you are using custom certificates, please have a " +"look at :doc:`how to add them to Zammad `." msgstr "" -#: ../system/objects/types.rst:134 ../system/objects/types.rst:160 -msgid "Maxlength" +#: ../system/integrations/i-doit.rst:77 +msgid "2. List / Create Zammad Tickets in i-doit" msgstr "" -#: ../system/objects/types.rst:0 ../system/objects/types.rst:160 -msgid "You can pick the maximum length of the field." +#: ../system/integrations/i-doit.rst:None +msgid "Zammad integration in i-doit's device view" msgstr "" -#: ../system/objects/types.rst:0 -msgid "The default length of this object is ``500``." +#: ../system/integrations/i-doit.rst:86 +msgid "" +"i-doit's ticket system integration gives you a way to see all the tickets " +"for a given device without ever leaving i-doit. (See our :user-docs:`user " +"documentation ` to learn how it " +"works in practice)." msgstr "" -#: ../system/objects/types.rst:139 -msgid "Rows" +#: ../system/integrations/i-doit.rst:95 +msgid "" +"Enable this integration in the i-doit admin panel under **Interfaces / " +"external data > Trouble Ticket System (TTS) > Configuration**:" msgstr "" -#: ../system/objects/types.rst:0 -msgid "" -"Change the number of rows to dislay so that you can use only the space you " -"really need." +#: ../system/integrations/i-doit.rst:None +msgid "i-doit administration interface with TTS configuration" msgstr "" -#: ../system/objects/types.rst:0 -msgid "The default number of rows is ``4``." +#: ../system/integrations/i-doit.rst:104 +msgid "TTS-Type" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Textarea fields" +#: ../system/integrations/i-doit.rst:104 +msgid "``Zammad``" msgstr "" -#: ../system/objects/types.rst:165 -msgid "Text field" +#: ../system/integrations/i-doit.rst:115 +msgid "Username / Password" msgstr "" -#: ../system/objects/types.rst:145 -msgid "Provides a text field (one line) and allows choosing a default value." +#: ../system/integrations/i-doit.rst:107 +msgid "Login credentials for a Zammad agent." msgstr "" -#: ../system/objects/types.rst:148 +#: ../system/integrations/i-doit.rst:109 msgid "" -"Defines the type of the input field. This allows e.g. your browser to ensure " -"that you provide the specific type." +"This agent must have **read permission** for all :doc:`groups ` that plan on using the i-doit integration." msgstr "" -#: ../system/objects/types.rst:152 -msgid "Currently available:" +#: ../system/integrations/i-doit.rst:113 +msgid "" +"You may even wish to create a dedicated agent account just for this " +"integration (otherwise, if the agent ever changes her password, you will " +"have to remember to update it here)." msgstr "" -#: ../system/objects/types.rst:155 -msgid "Phone" +#: ../system/integrations/i-doit.rst:117 +msgid "URL incl. protocol" msgstr "" -#: ../system/objects/types.rst:156 -msgid "Text" +#: ../system/integrations/i-doit.rst:118 +msgid "``https://your.zammad.domain``" msgstr "" -#: ../system/objects/types.rst:157 -msgid "Url *(URL fields disable link-template availability)*" +#: ../system/integrations/index.rst:2 +msgid "Integrations" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Text fields" +#: ../system/integrations/index.rst:4 +msgid "" +"Zammad offers numerous integrations that add rich features to your instance." msgstr "" -#: ../system/objects/types.rst:174 -msgid "Single tree selection field" +#: ../system/integrations/index.rst:6 +msgid "We're still working on this part of our documentation, stay tight!" msgstr "" -#: ../system/objects/types.rst:168 -msgid "" -"Provides a select-like field with up to 6 layers of options. Does not allow " -"setting a default value." +#: ../system/integrations/index.rst:10 +msgid "Integrations for Phone Systems" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Tree Select fields" +#: ../system/integrations/index.rst:14 +msgid "" +"Your VoIP provider or telephony system is not listed? Possibly your provider " +"supports Zammad by using the generic CTI - if you're unsure ask your " +"provider." msgstr "" -#: ../system/objects/types.rst:183 -msgid "Multiple tree selection field" +#: ../system/integrations/index.rst:18 +msgid "" +"Provider does not support Zammad? Consider creating a `feature request in " +"the Zammad Community `_." msgstr "" -#: ../system/objects/types.rst:177 -msgid "" -"Provides a select-like field with up to 6 layers of options allowing the " -"selection of multiple values. Does not allow setting a default value." +#: ../system/integrations/index.rst:31 +msgid "Integrations for Authentication and Customers" msgstr "" -#: ../system/objects/types.rst:302 -msgid "External Data Source field" +#: ../system/integrations/index.rst:44 +msgid "Integrations for Monitoring Systems" msgstr "" -#: ../system/objects/types.rst:186 -msgid "" -"Provides a searchable field which fetches data from an external system. This " -"can be useful if you have data outside of Zammad and don't want to maintain " -"both data sources." +#: ../system/integrations/index.rst:46 +msgid "This section currently misses the following integrations:" msgstr "" -#: ../system/objects/types.rst:190 -msgid "The feature works as follows:" +#: ../system/integrations/index.rst:48 +msgid "Icinga" +msgstr "Icinga" + +#: ../system/integrations/index.rst:49 +msgid "Monit" msgstr "" -#: ../system/objects/types.rst:192 -msgid "" -"Zammad sends a query with a search string (free text from agent or based on " -"a variable) in a pre-defined format (\"Search URL\") to an external system." +#: ../system/integrations/index.rst:50 +msgid "Nagios" msgstr "" -#: ../system/objects/types.rst:195 -msgid "" -"This external system searches for matches and provides a response as a JSON " -"structure to Zammad." +#: ../system/integrations/index.rst:60 +msgid "Integrations for Issue Trackers" msgstr "" -#: ../system/objects/types.rst:197 -msgid "" -"Zammad just looks for the defined list and value keys, reads the content and " -"displays the value to the user. There is no search on Zammad side." +#: ../system/integrations/index.rst:70 +msgid "Other Integrations" msgstr "" -#: ../system/objects/types.rst:201 +#: ../system/integrations/index.rst:72 msgid "" -"The usage of a PostgreSQL database for Zammad is required. In any other " -"case, Zammad will hide the external data source type and you are not able to " -"use it. If you want to use this feature, consider to :docs:`migrate your " -"database `." +"This section will hold any other integration that can't be grouped up (yet)." msgstr "" -#: ../system/objects/types.rst:205 -msgid "Currently, only ``GET`` is supported as request method." +#: ../system/integrations/ldap/index.rst:2 +msgid "LDAP / Active Directory" msgstr "" -#: ../system/objects/types.rst:206 +#: ../system/integrations/ldap/index.rst:4 msgid "" -"The data structure must be in JSON format and provide the objects in an " -"array." +"Zammad comes with a powerful LDAP integration that allows you to have a " +"single source of truth. By this you reduce the number of login credentials " +"your user has to remember." msgstr "" -#: ../system/objects/types.rst:208 +#: ../system/integrations/ldap/index.rst:10 msgid "" -"The endpoint for the external data source has to support search. On Zammad " -"side, there is no search/logic implemented; however, you can define the " -"output key and value based on the result(s) from the response (which " -"provides already filtered content based on the search)." +"The LDAP source is also a perfect candidate for Zammad's :docs:`Kerberos " +"Single Sign-On ` but also works as addition " +"to other :doc:`/settings/security/third-party`." msgstr "" -#: ../system/objects/types.rst:212 -msgid "" -"If you receive more results as expected, your external data source search " -"may not work properly or the structure of the URL is not correct. You should " -"get in touch with a responsible person from the external system." +#: ../system/integrations/ldap/index.rst:None +msgid "Zammands LDAP management page" msgstr "" -#: ../system/objects/types.rst:217 -msgid "" -"Please have a look :doc:`at our example `, where you can find a possible configuration for a public " -"dummy endpoint." +#: ../system/integrations/ldap/index.rst:25 +msgid "📝 :doc:`manage`" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for external data source fields" +#: ../system/integrations/ldap/index.rst:25 +msgid "Add, modify, remove or re-arrange your LDAP-Sources as needed." msgstr "" -#: ../system/objects/types.rst:242 -msgid "Search URL" +#: ../system/integrations/ldap/index.rst:30 +msgid "Before you continue, please note the following limitations." msgstr "" -#: ../system/objects/types.rst:227 -msgid "" -"Set your endpoint where Zammad fetches the data. Please make sure to include " -"a valid search :doc:`variable <../variables>` as an URL parameter. Example " -"for a free text search at user input: ``#{search.term}``" +#: ../system/integrations/ldap/index.rst:32 +msgid "Mapping / Synchronizing organizations is not possible" msgstr "" -#: ../system/objects/types.rst:232 +#: ../system/integrations/ldap/index.rst:36 msgid "" -"If in doubt, ask the responsible person for the external data source how " -"they expect the strucuture of the URL." +"You may want to consider using domain based assignments to overcome this " +"issue. Learn more on :doc:`/manage/organizations/index`." msgstr "" -#: ../system/objects/types.rst:236 +#: ../system/integrations/ldap/index.rst:39 msgid "" -"Depending on your search variable, the preview might work or not. The reason " -"is that the context might not be available and it is no bug." +"Zammad's LDAP sync is one way. Editing user settings or permissions may be " +"overwritten upon the next sync depending on your configuration." msgstr "" -#: ../system/objects/types.rst:239 -msgid "" -"Please also make sure to use a variable which is available in your object " -"context. For example you won't be able to search for a ticket in a user " -"object context." +#: ../system/integrations/ldap/index.rst:41 +msgid "Nested groups are not supported." msgstr "" -#: ../system/objects/types.rst:252 -msgid "SSL Verification" +#: ../system/integrations/ldap/index.rst:42 +msgid "Synchronizing user avatars from LDAP is not supported." msgstr "" -#: ../system/objects/types.rst:245 -msgid "Here you can switch the SSL verification to no." +#: ../system/integrations/ldap/index.rst:43 +msgid "Unlike user filters, group filters cannot be changed." msgstr "" -#: ../system/objects/types.rst:249 +#: ../system/integrations/ldap/index.rst:44 msgid "" -"If your external data source system is using self signed certificates, " -"please have a look :doc:`here ` for " -"further information about how to handle them in Zammad, so you can keep the " -"SSL verification activated." +"When a user originates from an LDAP server, Zammad will try to verify the " +"login credentials against LDAP first - if this fails Zammad will check its " +"local database." msgstr "" -#: ../system/objects/types.rst:258 -msgid "HTTP Authentication" +#: ../system/integrations/ldap/index.rst:50 +msgid "" +"Users can have local passwords even if they're LDAP users! You can learn " +"more about user accounts in general on :doc:`/manage/users/index`." +msgstr "" + +#: ../system/integrations/ldap/index.rst:54 +msgid "" +"When several LDAP sources contain the same user (meaning the same email " +"address), the user in question will be updated with every source configured. " +"*The last LDAP source will win.*" msgstr "" -#: ../system/objects/types.rst:255 +#: ../system/integrations/ldap/index.rst:58 msgid "" -"If your external data source requires an authentication, you can set it " -"here. You can leave it empty or choose between *Basic Authentication* or " -"*Authentication Token* (selecting one of the two methods leads to additional " -"fields where you can enter your credentials/token)." +"This is subject to change with `Issue 4109 `_ in the future." msgstr "" -#: ../system/objects/types.rst:265 -msgid "Search result list key" +#: ../system/integrations/ldap/index.rst:60 +msgid "" +"Synchronization statistics currently affect *all* configured LDAP sources. " +"This also applies for newly added or updated sources." msgstr "" -#: ../system/objects/types.rst:261 +#: ../system/integrations/ldap/index.rst:63 msgid "" -"Defines the level in the JSON structure which provides the list with search " -"results. You can leave it empty, if the data is already provided as an " -"array. If you have to go deeper in the structure, you can provide a path " -"with ``.`` as separators, e.g. ``key.subkey.sub-sub-key``." +"This is subject to change with `Issue 4108 `_ in the future." msgstr "" -#: ../system/objects/types.rst:271 -msgid "Search result value key" +#: ../system/integrations/ldap/index.rst:65 +msgid "" +"Zammad currently has limited fallback server support. You can workaround " +"this by providing several sources - however, ensure to have the exact same " +"configuration on your fallback." msgstr "" -#: ../system/objects/types.rst:268 +#: ../system/integrations/ldap/index.rst:69 msgid "" -"Defines the attribute in the structure in which your external data source " -"provides the *value* for your data. An example would be a product *number*. " -"If you have to go deeper in the structure, you can provide a path with ``.`` " -"as separators, e.g. ``key.subkey.sub-sub-key``." +"This is subject to improve with `Issue 4107 `_ in the future." msgstr "" -#: ../system/objects/types.rst:277 -msgid "Search result label key" +#: ../system/integrations/ldap/index.rst:76 +msgid "" +"This section holds all requests Zammad handled for all LDAP sources. These " +"entries can either contain synchronization information or logins " +"(authentication attempts via Zammad's login interface)." msgstr "" -#: ../system/objects/types.rst:274 +#: ../system/integrations/ldap/index.rst:80 msgid "" -"Defines the attribute in the structure in which your external data source " -"provides the *label* for your data. An example would be a product *name*. If " -"you have to go deeper in the structure, you can provide a path with ``.`` as " -"separators, e.g. ``key.subkey.sub-sub-key``." +"By clicking on any request, Zammad will provide even more information. The " +"provided information can be useful when something does not work as expected." msgstr "" -#: ../system/objects/types.rst:280 +#: ../system/integrations/ldap/index.rst:85 msgid "" -"In the preview area, you can find the following items (depending on your " -"configuration above):" +"Especially a LDAP synchronization can cause many log entries. The web " +"interface will always limit the number of shown entries to the last 50 " +"entries." msgstr "" -#: ../system/objects/types.rst:283 +#: ../system/integrations/ldap/index.rst:None msgid "" -"**Error/hint message** (only if configuration is not complete): Zammad tells " -"you, if there is a problem and what you should change in your configuration." +"Screencast showing LDAP integration log entries and a detail view on\n" +"an entry." msgstr "" -#: ../system/objects/types.rst:286 -msgid "" -"**Search field**: search for an existing attribute in the data source to get " -"a preview. This is required for the fields below to show up." +#: ../system/integrations/ldap/manage.rst:2 +msgid "Manage LDAP-Sources" msgstr "" -#: ../system/objects/types.rst:288 +#: ../system/integrations/ldap/manage.rst:6 msgid "" -"**Search result response** (only if configuration is not complete): here you " -"can find a syntax highlighted JSON preview of the response, based on the " -"search term you entered." +"Please keep in mind all current limitations for the LDAP synchronization. " +"This will help to understand scopes of the following operations better." msgstr "" -#: ../system/objects/types.rst:291 -msgid "" -"**Search result list** (only if *search result list key* is properly set): " -"output of the structure under the configured *search result list key*." +#: ../system/integrations/ldap/manage.rst:65 +msgid "Add new source" msgstr "" -#: ../system/objects/types.rst:294 +#: ../system/integrations/ldap/manage.rst:10 msgid "" -"**Preview table** (when fully configured): Zammad shows you a table which " -"includes the found items based on the search string (value, label and " -"optional link). You can use this preview if you don't have the complete data " -"structure of the external system in mind." +"Using the *New Source* button allows you to add new LDAP sources to your " +"installation. You're not limited in the number of sources, however, keep in " +"mind that many sources will also take more time to synchronize." msgstr "" -#: ../system/objects/types.rst:299 +#: ../system/integrations/ldap/manage.rst:14 msgid "" -"An example of a configured external data source field from agent perspective:" +"You can choose between different encryption types, namely *SSL* and " +"*STARTTLS* or none of them (\"*No SSL*\"). If you choose *SSL* or " +"*STARTTLS*, Zammad will display an additional *SSL verification* option that " +"allows you to disable the verification, e.g. for self-signed SSL " +"certificates. You can also tell Zammad to use a different port by appending " +"``:`` to your hostname/IP." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Screencast showing the search for a product in a ticket" +#: ../system/integrations/ldap/manage.rst:0 +msgid "" +"Screenshot of configuring a new LDAP source with SSL encryption and SSL " +"verification" msgstr "" -#: ../system/objects/types.rst:307 -msgid "URL fields (Link-Template)" +#: ../system/integrations/ldap/manage.rst:26 +msgid "" +"New Source with SSL transport security enabled and certificate verification" msgstr "" -#: ../system/objects/types.rst:311 +#: ../system/integrations/ldap/manage.rst:30 msgid "" -"This function is restricted to Text, Select and External data source types " -"only." +"Using an user filter can be a good idea if you only require a small subset " +"of your LDAP users in Zammad." msgstr "" -#: ../system/objects/types.rst:314 -msgid "" -"Link-Templates are an amazing way to dynamically generate URLs. They allow " -"you to integrate other systems better without having to manually copy data " -"from Zammad if possible." +#: ../system/integrations/ldap/manage.rst:42 +msgid "This especially affects inactive users" msgstr "" -#: ../system/objects/types.rst:320 +#: ../system/integrations/ldap/manage.rst:34 msgid "" -"Another great way of communicating with another system may be Zammad's :doc:" -"`Webhooks `." +"As every LDAP behaves differently on which attributes and how they are set, " +"Zammad doesn't care about any flags." msgstr "" -#: ../system/objects/types.rst:323 +#: ../system/integrations/ldap/manage.rst:37 msgid "" -"After filling a link-template enabled field, an URL icon will appear on its " -"right. Clicking on the icon opens a new tab." +"Users that no longer are returned by your LDAP source will automatically be " +"set to inactive. Zammad assumes that the user was deactivated." msgstr "" -#: ../system/objects/types.rst:328 +#: ../system/integrations/ldap/manage.rst:41 msgid "" -"Even though Zammad displays the link template within object edit and create " -"screens, the function is optional. It's only active if you populate the " -"field." +"Users will never be removed automatically! If you want to remove obsolete " +"users, use :doc:`/system/data-privacy`." msgstr "" -#: ../system/objects/types.rst:333 -msgid "" -"What's the difference between URL and text fields with link template...?!" +#: ../system/integrations/ldap/manage.rst:46 +msgid "Active Directory admins" msgstr "" -#: ../system/objects/types.rst:335 +#: ../system/integrations/ldap/manage.rst:45 msgid "" -"Both fields have different use cases. Use ``text`` type text fields when " -"ever you have a *static* url that requires dynamic parameters. If you " -"require a drag & drop like field that you can put in any URL, use ``URL`` " -"type text fields." +"Active Directories are quite specific on how to filter for active users only " +"- please see the `Microsoft documentation `_ for more " +"information." msgstr "" -#: ../system/objects/types.rst:340 +#: ../system/integrations/ldap/manage.rst:51 msgid "" -"The difference is easier to spot when comparing the fields directly, below " -"screencast shows the result - the dynamic approach uses existing values in " -"the moment of updating to built the URL - e.g. ``https://google.com/search?" -"q=cookies`` - while the URL approach uses the actual URL of the field - e.g. " -"``https://zammad.com``." +"*Do not* manually write pathes of either LDAP attributes or groups. If " +"Zammad does not display them, it either cannot find them or you have a lot " +"of users that don't have the attributes populated." msgstr "" -#: ../system/objects/types.rst:None +#: ../system/integrations/ldap/manage.rst:55 msgid "" -"Screencast showing the differents in between URL and text type fields with " -"actual values" +"Zammad will always only return attributes that are filled - this reduces the " +"returned list of attributes greatly." msgstr "" -#: ../system/objects/types.rst:352 -msgid "How does this work...?!" +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing how to add a new LDAP source" msgstr "" -#: ../system/objects/types.rst:354 +#: ../system/integrations/ldap/manage.rst:63 msgid "" -"As an example, let's say you have an attribute called ``amazing_attribute`` " -"and you want to open a google search directly with the input from that field." +"If your LDAP system doesn't allow anonymous bind, Zammad detects it and " +"provides you an editable \"Base DN\" *text* field instead of a prefilled " +"*select* field." msgstr "" -#: ../system/objects/types.rst:357 -msgid "" -"Providing the link-template field below allows you to do so: ``https://www." -"google.com/search?q=#{ticket.amazing_attribute}``" +#: ../system/integrations/ldap/manage.rst:81 +msgid "Review or edit existing source" msgstr "" -#: ../system/objects/types.rst:362 +#: ../system/integrations/ldap/manage.rst:68 msgid "" -"You can use any :doc:`Zammad variable ` as long as it's " -"available in the moment you need it." +"Clicking on a LDAP source will provide a configuration and mapping overview." msgstr "" -#: ../system/objects/types.rst:365 +#: ../system/integrations/ldap/manage.rst:70 msgid "" -"As a result, you are redirected to Google with a search for the value of the " -"attribute, if you click on the button in the ticket (as you can see in the " -"screencast above)." -msgstr "" - -#: ../system/packages.rst:2 -msgid "Packages" +"If needed you can then use the *Change* button to update either the name, " +"active state or the whole configuration. If you're changing the whole " +"configuration, the dialogue will be identical to the source creation." msgstr "" -#: ../system/packages.rst:4 -msgid "That's the package management-area." +#: ../system/integrations/ldap/manage.rst:76 +msgid "" +"Did your LDAP server change? Different LDAP servers have different " +"structures and default attributes. This causes the LDAP synchronization to " +"likely fail. Consider removing the affected source and re-add it." msgstr "" -#: ../system/packages.rst:6 -msgid "Individual add-ons for Zammad can be installed and managed here." +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing the update of the source name." msgstr "" -#: ../system/sessions.rst:2 -msgid "Sessions" +#: ../system/integrations/ldap/manage.rst:89 +msgid "Re-arrange LDAP source's order" msgstr "" -#: ../system/sessions.rst:4 +#: ../system/integrations/ldap/manage.rst:84 msgid "" -"Sessions management allows reviewing currently known user sessions and " -"allows to end these. The session timeout is affected by :ref:" -"`security_session_timeout` configurations from security settings." +"You can change the synchronization order for each source at any time. Zammad " +"will synchronize the sources from top to bottom." msgstr "" -#: ../system/sessions.rst:None -msgid "Screenshot showing Zammad's session management" +#: ../system/integrations/ldap/manage.rst:0 +msgid "" +"Screencasting showing how to change the source order by using\n" +"drag and drop." msgstr "" -#: ../system/sessions.rst:13 -msgid "Zammad will provide the following information:" +#: ../system/integrations/ldap/manage.rst:101 +msgid "Remove a source" msgstr "" -#: ../system/sessions.rst:16 +#: ../system/integrations/ldap/manage.rst:92 msgid "" -"The user account this session entry belongs to. It can be normal if a user " -"has several sessions in the list. This can be due to changed browser " -"information or if you use e.g. single sign on methods where the user does " -"not use the log off button." +"If you no longer need the a LDAP source or simply want to start over, you " +"can remove them at any time. This will not remove synchronized users, data " +"synchronized or permissions." msgstr "" -#: ../system/sessions.rst:22 -msgid "Browser" +#: ../system/integrations/ldap/manage.rst:98 +msgid "" +"Not sure if you'd need the source later on? Set the source to inactive " +"instead of removing it - see *Review or edit existing source* for more." msgstr "" -#: ../system/sessions.rst:22 -msgid "The browser agent communicated to Zammad." +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing how to remove LDAP sources." msgstr "" -#: ../system/sessions.rst:40 -msgid "Location" +#: ../system/integrations/pgp/index.rst:2 +msgid "PGP" msgstr "" -#: ../system/sessions.rst:25 +#: ../system/integrations/pgp/index.rst:7 msgid "" -"The anticipated location based on the users IP address. Depending on the IP " -"address the result shown may differ. This option depends on :doc:`/settings/" -"system/services`." +"Pretty Good Privacy (PGP) is another method for secure email communication. " +"With PGP, you can exchange **signed** and **encrypted** messages with others." msgstr "" -#: ../system/sessions.rst:29 -msgid "The following information can be shown:" +#: ../system/integrations/pgp/index.rst:13 +#: ../system/integrations/smime/index.rst:17 +msgid "Signing" msgstr "" -#: ../system/sessions.rst:33 -msgid "IP address" +#: ../system/integrations/pgp/index.rst:11 +msgid "is a proof that a message hasn't been manipulated on its way." msgstr "" -#: ../system/sessions.rst:32 +#: ../system/integrations/pgp/index.rst:13 msgid "" -"Either if you set *Geo IP services* to inactive or you're using internal IP " -"address which do not provide location information." +"In other words, it guarantees message **integrity** and **authenticity**." msgstr "" -#: ../system/sessions.rst:40 -msgid "Country (or Country + City)" +#: ../system/integrations/pgp/index.rst:19 +#: ../system/integrations/smime/index.rst:22 +msgid "Encryption" msgstr "" -#: ../system/sessions.rst:36 +#: ../system/integrations/pgp/index.rst:16 +#: ../system/integrations/smime/index.rst:20 msgid "" -"If *Geo IP services* is enabled only. Depends on how detailed the available " -"IP address information are." +"scrambles a message so that it can only be unscrambled by the intended " +"recipient." msgstr "" -#: ../system/sessions.rst:39 +#: ../system/integrations/pgp/index.rst:19 msgid "" -"Be aware that results can be inaccurate - this technically is not an error." +"In other words, it guarantees message **privacy** and **data security**." msgstr "" -#: ../system/sessions.rst:43 -msgid "Age" +#: ../system/integrations/pgp/index.rst:25 +msgid "Screenshot of ticket creation with encrypt and sign buttons" msgstr "" -#: ../system/sessions.rst:43 -msgid "Provides the time when the session initially has been created." +#: ../system/integrations/pgp/index.rst:25 +msgid "" +"Once PGP has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " +"appear in the ticket composer." msgstr "" -#: ../system/sessions.rst:50 -msgid "Update" +#: ../system/integrations/pgp/index.rst:28 +msgid "**Sign button not visible?**" msgstr "" -#: ../system/sessions.rst:46 +#: ../system/integrations/pgp/index.rst:30 msgid "" -"Provides the time the user used this session to open Zammad. This timestamp " -"is only updated if the user e.g. reloads, not during normal work on tickets." +"Please note that the signing of emails is based on the outgoing email " +"account. That means you have to choose a group with a sender email account, " +"which has a private key assigned." msgstr "" -#: ../system/sessions.rst:50 -msgid "This timestamp is being used for the session timeout." +#: ../system/integrations/pgp/index.rst:35 +msgid "Handling of Keys" msgstr "" -#: ../system/sessions.rst:53 +#: ../system/integrations/pgp/index.rst:36 msgid "" -"Use the delete button to remove a single session on behalf of your user." -msgstr "" - -#: ../system/subscription/billing.rst:2 -msgid "Billing" +"To use the PGP function, you have to enable the integration (PGP) by " +"switching the toggle to *enabled*." msgstr "" -#: ../system/subscription/billing.rst:4 +#: ../system/integrations/pgp/index.rst:39 msgid "" -"Within the billing tab you can control all billing relevant information like " -"invoices, billing address and the option to cancel your subscription." +"You can add keys by clicking the *add key* button. The keys can be imported " +"from a file or you can paste the content of the key in the text box." msgstr "" -#: ../system/subscription/billing.rst:33 -msgid "Billing information" +#: ../system/integrations/pgp/index.rst:42 +msgid "**Which keys do I have to import?**" msgstr "" -#: ../system/subscription/billing.rst:8 +#: ../system/integrations/pgp/index.rst:44 msgid "" -"All adjusted billing information below only affect future invoices. If your " -"invoice was issued wrong, please contact `our sales team `_." +"For **signing** *outgoing* emails, you have to import the private key of " +"your Zammad email account." msgstr "" -#: ../system/subscription/billing.rst:14 -msgid "Billing address" +#: ../system/integrations/pgp/index.rst:47 +msgid "" +"For **encrypting** *outgoing* emails, you have to import the public key of " +"the customer's email account." msgstr "" -#: ../system/subscription/billing.rst:13 +#: ../system/integrations/pgp/index.rst:50 msgid "" -"Provide your company address here, make sure to include the companies name " -"in case required. This address will be referenced on your invoice." +"For **verifying the signature** of signed *incoming* emails, you have to " +"import the public key of the customer." msgstr "" -#: ../system/subscription/billing.rst:18 -msgid "VAT ID" +#: ../system/integrations/pgp/index.rst:53 +msgid "" +"For **decrypting** of encrypted *incoming* emails, you have to import the " +"private key of your Zammad email account." msgstr "" -#: ../system/subscription/billing.rst:17 -msgid "" -"Provide your VAT ID here. If applicable your invoice will not contain German " -"VAT. Please make sure to pay the VAT in your country as required." +#: ../system/integrations/pgp/index.rst:57 +msgid "Import Keys From a File" msgstr "" -#: ../system/subscription/billing.rst:27 -msgid "Billing Email Address" +#: ../system/integrations/pgp/index.rst:58 +msgid "You can import keys from a file in the section **Upload key**:" msgstr "" -#: ../system/subscription/billing.rst:21 -msgid "" -"Usually the instance owner (the person that registered the instance) will " -"receive all emails including the invoices. In case you have your own billing " -"department, you can provide their email address here." +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of adding a key via file" msgstr "" -#: ../system/subscription/billing.rst:25 +#: ../system/integrations/pgp/index.rst:64 msgid "" -"All billing relevant information will then be sent to this email address." +"**Supported file formats:** ASCII-armor as well as binary GPG format " +"(basically any GPG supported key format) is supported here." msgstr "" -#: ../system/subscription/billing.rst:27 -msgid "Invoices are sent as attachment (PDF) to this email address." +#: ../system/integrations/pgp/index.rst:68 +msgid "Import Keys by Pasting the Content" msgstr "" -#: ../system/subscription/billing.rst:29 -msgid "" -"Don't forget to press the *Submit* button after you changed above settings." +#: ../system/integrations/pgp/index.rst:69 +msgid "You can also paste the key's content in the section **paste key**:" msgstr "" -#: ../system/subscription/billing.rst:0 -msgid "" -"Screenshot showing options for billing information within the\n" -"subscription menu" +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of adding a key via pasting" msgstr "" -#: ../system/subscription/billing.rst:70 -msgid "Payment history" +#: ../system/integrations/pgp/index.rst:75 +msgid "" +"**Supported format:** Please note that only ASCII-armor is supported here." msgstr "" -#: ../system/subscription/billing.rst:36 -msgid "" -"The payment history will display a history of all paid invoices. At this " -"point you can also download these in case you need them again." +#: ../system/integrations/pgp/index.rst:78 +msgid "Deleting Keys" msgstr "" -#: ../system/subscription/billing.rst:41 +#: ../system/integrations/pgp/index.rst:79 msgid "" -"You will only find *paid* invoices here. Invoices that are to be billed are " -"not available before the payment is completed." +"If you want to delete a specific key, you can do it by clicking on the menu " +"in the *actions* column and select **delete**:" msgstr "" -#: ../system/subscription/billing.rst:46 -msgid "Date" +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of deleting a key" msgstr "" -#: ../system/subscription/billing.rst:46 -msgid "Date of the invoice creation." +#: ../system/integrations/pgp/index.rst:88 +msgid "Downloading Keys" msgstr "" -#: ../system/subscription/billing.rst:49 -msgid "Amount" +#: ../system/integrations/pgp/index.rst:89 +msgid "" +"If you want to download your keys, you can do this as well via corresponding " +"action buttons. Depending on the key, you can choose wether you want to " +"download the private or the public key." msgstr "" -#: ../system/subscription/billing.rst:49 -msgid "Invoice total including VAT if applicable." +#: ../system/integrations/pgp/index.rst:95 +#: ../system/integrations/smime/manage-certificates.rst:76 +msgid "Default Behavior" msgstr "" -#: ../system/subscription/billing.rst:52 +#: ../system/integrations/pgp/index.rst:96 msgid "" -"Contains contract period (monthly or yearly) and hosted plan for the " -"subscription period in question." +"Here you can adjust on per group basis, if *sign* and *encryption* is on or " +"off by default. Please be aware, that agents can always override the setting " +"for each individual article." msgstr "" -#: ../system/subscription/billing.rst:63 -msgid "Payment method / Service period" +#: ../system/integrations/pgp/index.rst:None +msgid "Adjusting default behavior on per group basis" msgstr "" -#: ../system/subscription/billing.rst:56 +#: ../system/integrations/pgp/index.rst:107 msgid "" -"Used bank account or credit card as well as the subscription period the " -"invoice is about." +"Here you can see the last actions regarding signing and encryption and if " +"they were successful." msgstr "" -#: ../system/subscription/billing.rst:61 -msgid "" -"It might happen that the invoice date and subscription period differ. This " -"is nothing to worry about, the subscription periods will be accounted later " -"on." +#: ../system/integrations/pgp/index.rst:117 +msgid "**Sign button is not visible, but keys are imported.**" msgstr "" -#: ../system/subscription/billing.rst:67 -msgid "Receipt" +#: ../system/integrations/pgp/index.rst:115 +msgid "Did you choose a group in the ticket?" msgstr "" -#: ../system/subscription/billing.rst:66 +#: ../system/integrations/pgp/index.rst:116 msgid "" -"Use the arrow to download the invoice in question. You can download all " -"available invoices any time you need to here!" +"Did you import a private key for the email adress, which is used for " +"outgoing emails in the group?" msgstr "" -#: ../system/subscription/billing.rst:0 -msgid "Screenshot showing payment history of a hosted instance" +#: ../system/integrations/pgp/index.rst:122 +msgid "**How to obtain keys?**" msgstr "" -#: ../system/subscription/billing.rst:94 -msgid "Do you want to cancel your subscription?" +#: ../system/integrations/pgp/index.rst:120 +msgid "" +"You can create them yourself! There are some good tutorials on the web on " +"how to create them. Providing keys to Zammad is a prerequisite to use the " +"PGP feature." msgstr "" -#: ../system/subscription/billing.rst:73 -msgid "" -"In case you no longer want to use Zammad's SaaS, you can cancel your " -"subscription by using the red *Yes, please cancel my subscription* button." +#: ../system/integrations/pgp/index.rst:127 +msgid "**It says a passphrase is needed, but I haven't got one.**" msgstr "" -#: ../system/subscription/billing.rst:76 +#: ../system/integrations/pgp/index.rst:125 msgid "" -"Your subscription will end the day after your trial or billing period ends." +"If the key is secured with a passphrase, you have to provide it for the " +"import in Zammad. It is possible that keys may have an empty passphrase. " +"However, this is *not* recommended." +msgstr "" + +#: ../system/integrations/pgp/index.rst:132 +msgid "**How do my customers get my new key?**" msgstr "" -#: ../system/subscription/billing.rst:80 +#: ../system/integrations/pgp/index.rst:130 msgid "" -"We will remind you about your cancelled subscription several times up front. " -"After the subscription ended all instance data will be removed. A restore " -"*is not* possible after that point!" +"You have to provide your **public** key in advance. Your customer also has " +"to configure PGP in their email workflow and import your public key. The " +"other way round, you have to get the public key of your customer and have to " +"import it to Zammad." msgstr "" -#: ../system/subscription/billing.rst:0 -msgid "Screencast showing how to cancel a subscription" +#: ../system/integrations/slack.rst:2 +msgid "Slack" msgstr "" -#: ../system/subscription/billing.rst:87 -msgid "**😖 Cancelled by accident?**" +#: ../system/integrations/slack.rst:4 +msgid "**⚠️ Deprecation warning ⚠️**" msgstr "" -#: ../system/subscription/billing.rst:89 +#: ../system/integrations/slack.rst:6 msgid "" -"You can always undo the cancellation via the *Yes, undo the cancellation of " -"my subscription* button up to the last subscription day!" +"Zammad 7 will no longer support this dedicated Slack integration. It is " +"recommended to switch to :doc:`pre-defined webhooks ` instead. Existing Slack integrations should " +"be migrated manually before this feature is dropped." msgstr "" -#: ../system/subscription/billing.rst:0 +#: ../system/integrations/slack.rst:14 msgid "" -"Screenshot showing a red button to cancel the subscription\n" -"cancellation" +"In order to use this feature, please add a new Slack app to your Workspace. " +"The App you need is called ``Incoming WebHooks`` ." msgstr "" -#: ../system/subscription/index.rst:2 -msgid "Subscription (SaaS)" +#: ../system/integrations/slack.rst:18 +msgid "Why Do I Need This Feature?" msgstr "" -#: ../system/subscription/index.rst:4 +#: ../system/integrations/slack.rst:20 msgid "" -"The subscription settings page allows you to configure your instances " -"package and number of agents required." +"If you're already using Slack for your team communication, you'll love this " +"feature! Our Slack integration can push ticket notifications about the last " +"ticket article based on the following events:" msgstr "" -#: ../system/subscription/index.rst:9 -msgid "" -"This setting section is only available for Hosted setups. If you're looking " -"for on premise support contracts, please see the `Zammad pricing page " -"`_." +#: ../system/integrations/slack.rst:24 +msgid "on Ticket creation" +msgstr "" + +#: ../system/integrations/slack.rst:25 +msgid "on Ticket updates" +msgstr "" + +#: ../system/integrations/slack.rst:26 +msgid "on reached reminders" msgstr "" -#: ../system/subscription/index.rst:20 -msgid "" -"The subscription section currently consists of two tabs: Plan & Billing. For " -"your overview we've divided those two tabs into independent sub pages:" +#: ../system/integrations/slack.rst:27 +msgid "a Ticket has escalated" msgstr "" -#: ../system/subscription/index.rst:25 -msgid ":doc:`💰 Subscription plan `" +#: ../system/integrations/slack.rst:28 +msgid "a Ticket is going to escalate" msgstr "" -#: ../system/subscription/index.rst:24 +#: ../system/integrations/slack.rst:30 msgid "" -"Everything affecting your instance subscription functions like number of " -"agents, package and payment method." +"Zammad will provide the Ticket title, a direct link to the Ticket, the event " +"type (creation, updated, escalation), the customer, time and the last " +"article that has triggered the notification." msgstr "" -#: ../system/subscription/index.rst:28 -msgid ":doc:`🧾 Subscription billing `" +#: ../system/integrations/slack.rst:34 +msgid "" +"This will give you further options, as you can see e.g. escalating tickets " +"that are assigned to an agent that's e.g. absent. You can interact faster, " +"as you might see problems earlier (or even before the problem gets one)." msgstr "" -#: ../system/subscription/index.rst:28 +#: ../system/integrations/slack.rst:38 msgid "" -"Everything regarding billing address, invoices and account cancellation." +"If needed and wanted, you can even discuss directly about the topic before " +"sending an answer to the customer. Another possible use case would be a " +"agent monitoring new agents and their answers to tickets." msgstr "" -#: ../system/subscription/index.rst:33 -msgid "FAQ" +#: ../system/integrations/slack.rst:44 +msgid "Configure the Integration" msgstr "" -#: ../system/subscription/index.rst:37 -msgid "I set up a trial account but am missing functions to test" +#: ../system/integrations/slack.rst:46 +msgid "" +"First of all, please go to your slack workspace - go to administration => " +"Manage Apps. If you don't have an app yet, you can simply add a new one - " +"just search for ``Incoming WebHooks`` and customize the app to your needs." msgstr "" -#: ../system/subscription/index.rst:36 +#: ../system/integrations/slack.rst:50 msgid "" -"The trial instance is running within the professional package allowing up to " -"three agents." +"Choose (or create) the channel Zammad should post it's information to and " +"press on \"Add Incoming WebHooks integration\". If you're ready, copy the " +"provided WebHook URL and go to your Zammad installation." msgstr "" -#: ../system/subscription/index.rst:40 -msgid "Can I change package within the trial?" +#: ../system/integrations/slack.rst:56 +msgid "" +"You need administrative rights on the Slack Workspace. The link to the app " +"directory is normally ``https://[workspace-name].slack.com/apps`` ." msgstr "" -#: ../system/subscription/index.rst:40 -msgid "No. As soon as the package is changed the subscription begins." +#: ../system/integrations/slack.rst:63 +msgid "" +"To configure the slack integration, log in to Zammad and go to Integrations " +"(System) => Slack in the admin panel." msgstr "" -#: ../system/subscription/index.rst:45 -msgid "What happens to my trial instance after the trial period ended?" +#: ../system/integrations/slack.rst:66 +msgid "" +"Here you can choose on what evens Zammad should post information about a " +"ticket to your Slack channel. Next you need to device what groups shall be " +"affected by this, as anybody with access to that specific Slack channel can " +"read at least parts of the ticket this might be a privacy issue, if you " +"select the wrong groups. The username is simply the name that Zammad uses as " +"display name inside the Slack chat. The channel defines the Slack channel " +"the information is being posted in. As last option, you can set a custom " +"icon for posting to slack." msgstr "" -#: ../system/subscription/index.rst:43 +#: ../system/integrations/slack.rst:74 msgid "" -"Your instance will automatically be canceled for you. Please see *What " -"happens to my instance after it has been canceled?* for more." +"When you're ready, just hit \"Submit\" and enable the integration. Zammad " +"will now post new ticket information based on the trigger you chose. Below " +"the options you have the recent log that shows the latest requests to Slack " +"for debugging if needed." msgstr "" -#: ../system/subscription/index.rst:58 -msgid "What happens to my instance after it has been canceled?" +#: ../system/integrations/slack.rst:81 +msgid "" +"If you leave the Icon URL empty, Zammad will use the Zammad logo instead. " +"The icon should be a square PNG file." msgstr "" -#: ../system/subscription/index.rst:48 -msgid "That depends slightly on your instance state:" +#: ../system/integrations/slack.rst:90 +msgid "" +"The following figure shows how it will look if you choose to receive updates " +"on created and updated tickets. On every post Zammad sends to the Slack " +"channel, you can create new threads to discuss about the new article." msgstr "" -#: ../system/subscription/index.rst:54 -msgid "Trial instance" +#: ../system/integrations/slack.rst:96 +msgid "" +"If you just want to keep track of soon escalating or already escalated " +"tickets, it will look the the following figure. Zammad changes the color in " +"front of the post so you can easily see the state of the ticket." msgstr "" -#: ../system/subscription/index.rst:51 +#: ../system/integrations/slack.rst:102 msgid "" -"If you're still on trial, we will ice your instance and remind you once " -"again about your instance. We then will wait some days and remove your " -"instance from our system. This is the last time we will inform you by Email." +"If you change the state, Zammad will also put information on what state the " +"ticket gets and (if pending state) the date until it pends. You'll also " +"recognize the color codes in front of posts on slack, as they are exact the " +"same the ticket state colors you'll see in Zammad!" msgstr "" -#: ../system/subscription/index.rst:58 -msgid "Paid instance" +#: ../system/integrations/smime/index.rst:2 +msgid "S/MIME" msgstr "" -#: ../system/subscription/index.rst:57 +#: ../system/integrations/smime/index.rst:11 msgid "" -"If you're a paying customer and canceled your subscription, the instance " -"removal will take place the day after your last subscription day." +"S/MIME is the most widely-supported method for secure email communication. " +"With S/MIME, you can exchange **signed** and **encrypted** messages with " +"others." msgstr "" -#: ../system/subscription/index.rst:60 -msgid "Can removed instances be restored?" +#: ../system/integrations/smime/index.rst:15 +msgid "" +"is proof that a message hasn't been tampered with or sent by an impersonator." msgstr "" -#: ../system/subscription/index.rst:61 -msgid "No. Once your instance has been removed, a restoration is not possible." +#: ../system/integrations/smime/index.rst:17 +msgid "" +"In other words, it guarantees a message's **integrity** and **authenticity**." msgstr "" -#: ../system/subscription/plan.rst:2 ../system/subscription/plan.rst:38 -msgid "Plan" +#: ../system/integrations/smime/index.rst:22 +msgid "In other words, it guarantees **privacy** and **data security**." msgstr "" -#: ../system/subscription/plan.rst:16 -msgid "Subscription" +#: ../system/integrations/smime/index.rst:28 +msgid "Screencast demo of S/MIME features for both new tickets and replies" msgstr "" -#: ../system/subscription/plan.rst:5 +#: ../system/integrations/smime/index.rst:28 msgid "" -"On the top of the subscription summary you'll find the number of used and " -"available (booked) agent seats. By using the *see more* link you can also " -"expand an agent list to see the currently configured active agents. This " -"list *does not* count accounts with admin permissions only." +"Once S/MIME has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " +"appear in the ticket composer." msgstr "" -#: ../system/subscription/plan.rst:0 -msgid "" -"Within subscription you can always see how many agents are still\n" -"available to add and who uses the seats." +#: ../system/integrations/smime/index.rst:32 +msgid ":doc:`🔪 Prerequisites `" msgstr "" -#: ../system/subscription/plan.rst:14 +#: ../system/integrations/smime/index.rst:31 msgid "" -"Learn more on how to manage your agents in general :doc:`here `." +"New to S/MIME? This section helps you to find certificate providers and " +"points out Limitations." msgstr "" -#: ../system/subscription/plan.rst:19 -msgid "" -"This section gives you an overview of the available plans and their " -"functions / limits. If you require a more detailed table, check our " -"`detailed pricing table `_ for more." +#: ../system/integrations/smime/index.rst:35 +msgid ":doc:`📝 Manage Certificates `" msgstr "" -#: ../system/subscription/plan.rst:23 -msgid "" -"Your selection in this step will decide on the base agent price and e.g. " -"agent limits that might apply in the summary step." +#: ../system/integrations/smime/index.rst:35 +msgid "Add and download certificates; configure group default behaviors." msgstr "" -#: ../system/subscription/plan.rst:26 -msgid "" -"The green *Selected* button will also tell you what plan you're currently in." +#: ../system/integrations/smime/index.rst:38 +msgid ":doc:`😦 Troubleshooting `" msgstr "" -#: ../system/subscription/plan.rst:30 -msgid "" -"Trial instances are running at Professional with 3 agents. The plan cannot " -"be changed during the trial for technical reasons, if you require more " -"agents for testing, please contact `our sales team `_ with a reason for the raise request." +#: ../system/integrations/smime/index.rst:38 +msgid "Took a wrong turn? About recent logs and common issues." msgstr "" -#: ../system/subscription/plan.rst:0 +#: ../system/integrations/smime/index.rst:43 msgid "" -"Screenshot showing three available packages for a hosted Zammad\n" -"instance" +"For more details on how S/MIME integration works on the agent side, see the :" +"user-docs:`user docs `." msgstr "" -#: ../system/subscription/plan.rst:83 -msgid "Summary" +#: ../system/integrations/smime/manage-certificates.rst:2 +msgid "Manage Certificates" msgstr "" -#: ../system/subscription/plan.rst:41 +#: ../system/integrations/smime/manage-certificates.rst:4 msgid "" -"In this section you can adjust the settings of the previous selected plan." +"S/MIME is **disabled by default**. Enable it to start adding certificates." msgstr "" -#: ../system/subscription/plan.rst:45 -msgid "" -"Note that upgrading (more agents, higher package) is always possible, " -"however, downgrading will only happen when your billing period renews." +#: ../system/integrations/smime/manage-certificates.rst:10 +msgid "Dialogue to add new certificates or private keys" msgstr "" -#: ../system/subscription/plan.rst:49 +#: ../system/integrations/smime/manage-certificates.rst:10 msgid "" -"Upgrading resets your billing period and existing credit will be deducted " -"from the new total." +"Manage certificates in the Admin Panel under **System > Integrations > S/" +"MIME**. Certificates may be pasted in as plain text or uploaded from a file." msgstr "" -#: ../system/subscription/plan.rst:58 -msgid "Billing cycle" +#: ../system/integrations/smime/manage-certificates.rst:14 +msgid "Add Certificate Data" msgstr "" -#: ../system/subscription/plan.rst:53 -msgid "" -"You can choose between either monthly or yearly billing. The price per agent " -"will be cheaper if you decide for yearly billing." +#: ../system/integrations/smime/manage-certificates.rst:36 +msgid "Add Certificate" msgstr "" -#: ../system/subscription/plan.rst:56 +#: ../system/integrations/smime/manage-certificates.rst:17 msgid "" -"If you're still trying out things and are unsure of the right package for " -"your instance, you may want to choose monthly first and then upgrade to " -"yearly when you're sure." +"Import public-key certificates for both your own organization and your " +"contacts." msgstr "" -#: ../system/subscription/plan.rst:66 -msgid "Plan: (Starter|Professional|Plus) - Agents" +#: ../system/integrations/smime/manage-certificates.rst:19 +msgid "" +"You can also add a bunch of certificates in one go by providing a single " +"file with all relevant certificates." msgstr "" -#: ../system/subscription/plan.rst:61 -msgid "Choose the number of agents you require for your instance." +#: ../system/integrations/smime/manage-certificates.rst:22 +msgid "🕵️ **ALWAYS verify certificates in-person or over the phone!**" msgstr "" -#: ../system/subscription/plan.rst:63 +#: ../system/integrations/smime/manage-certificates.rst:24 msgid "" -"Keep in mind that some packages may have agent limits. Depending on the " -"previous chosen package, you won't be able to exceed specific agent numbers. " -"Also note that setting less agents than currently configured is not possible." -msgstr "" - -#: ../system/subscription/plan.rst:69 -msgid "Total" +"The whole point of signatures is to alert you when someone is trying to " +"pretend to be someone they're not. Never accept a certificate from someone " +"online without verifying it first." msgstr "" -#: ../system/subscription/plan.rst:69 -msgid "This will be the net total you're going to be billed." +#: ../system/integrations/smime/manage-certificates.rst:28 +msgid "📇 **What about trusted certificate authorities?**" msgstr "" -#: ../system/subscription/plan.rst:71 +#: ../system/integrations/smime/manage-certificates.rst:30 msgid "" -"By using the *Update subscription* button, the instance package will be " -"adjusted immediately. If you didn't provide a payment method yet, Zammad " -"will request you to provide one at this point." +"In some cases (e.g. when dealing with large enterprises), you may be given a " +"certificate for an entire CA, rather than a single contact. Add it here to " +"trust *all* certificates issued by that CA." msgstr "" -#: ../system/subscription/plan.rst:77 +#: ../system/integrations/smime/manage-certificates.rst:35 msgid "" -"In case you're still within the trial period, this means that the trial will " -"be over immediately!" -msgstr "" - -#: ../system/subscription/plan.rst:80 -msgid "Down- or upgrading during the trial period *is not* possible." -msgstr "" - -#: ../system/subscription/plan.rst:0 -msgid "Screenshot showing payment options and a pricing summary" +"Commercial CAs can usually be verified online. Zammad does not include a " +"list of built-in, trusted CAs." msgstr "" -#: ../system/subscription/plan.rst:99 -msgid "Payment method" +#: ../system/integrations/smime/manage-certificates.rst:57 +msgid "Add Private Key" msgstr "" -#: ../system/subscription/plan.rst:86 -msgid "You can pay via credit card or SEPA mandate." +#: ../system/integrations/smime/manage-certificates.rst:39 +msgid "" +"Once you've added a public-key certificate, you can import its matching " +"private key." msgstr "" -#: ../system/subscription/plan.rst:91 -msgid "Credit card" +#: ../system/integrations/smime/manage-certificates.rst:42 +msgid "" +"Private keys are for **your own organization only**; never ask your contacts " +"for their private keys." msgstr "" -#: ../system/subscription/plan.rst:89 +#: ../system/integrations/smime/manage-certificates.rst:0 msgid "" -"Simply follow the dialogue by clicking *authorize* and confirm -if required " -"by your bank- your consent to Zammad using your card for the payments." +"S/MIME integration showing configured certificates and possible issues with " +"Logging" msgstr "" -#: ../system/subscription/plan.rst:95 -msgid "SEPA" +#: ../system/integrations/smime/manage-certificates.rst:50 +msgid "" +"A note is displayed on certificates with a matching private key (see line 2)." msgstr "" -#: ../system/subscription/plan.rst:94 -msgid "" -"Provide the requested information of the bank account holder and update if " -"you're ready. You'll then receive an email with the SEPA mandate." +#: ../system/integrations/smime/manage-certificates.rst:52 +msgid "📤 **Certificates and private keys must be uploaded separately.**" msgstr "" -#: ../system/subscription/plan.rst:97 +#: ../system/integrations/smime/manage-certificates.rst:54 msgid "" -"Technically there's also the possibility to pay via invoice, however - this " -"method only applies to a fairly low number of instances. Please contact `our " -"sales team `_ for more information." +"If your certificate and private key are bundled together in the same file or " +"PEM block, import it twice (once using each button)." msgstr "" -#: ../system/translations.rst:2 -msgid "Translations" +#: ../system/integrations/smime/manage-certificates.rst:57 +msgid "Please note that bulk imports of private keys are not possible." msgstr "" - -#: ../system/translations.rst:4 -msgid "" -"Translations of Zammad are processed centrally in our `Weblate instance " -"`_. This allows non-developers to review " -"and update translation texts of the language they actually speak." + +#: ../system/integrations/smime/manage-certificates.rst:60 +msgid "Download Certificate Data" msgstr "" -#: ../system/translations.rst:9 +#: ../system/integrations/smime/manage-certificates.rst:62 msgid "" -"Your language is in an incomplete translation state or has typos? Please " -"consider helping us in sorting this out! All you need is either a GitHub " -"account or to register directly in our instance." +"You can download the earlier provided certificates and private keys at any " +"time from your Zammad instance." msgstr "" -#: ../system/translations.rst:13 +#: ../system/integrations/smime/manage-certificates.rst:65 msgid "" -"Did you know? This is also where the documentation translations are handled. " -"🤓" +"Please note that passphrase-protected private keys stay protected and when " +"you download them, you have to know the passphrase to use them after " +"downloading." msgstr "" -#: ../system/translations.rst:15 -msgid "" -"Have a look in our :docs:`contribution section ` in the system documentation to get started!" +#: ../system/integrations/smime/manage-certificates.rst:73 +msgid "Dialogue to download certificates or private keys" msgstr "" -#: ../system/translations.rst:20 -msgid "Local Translations" +#: ../system/integrations/smime/manage-certificates.rst:73 +msgid "Download stored certificates and their keys" msgstr "" -#: ../system/translations.rst:22 +#: ../system/integrations/smime/manage-certificates.rst:78 msgid "" -"Apart from these system translations, there's still local translations you " -"can manage. This is relevant if you added custom objects that require " -"translations or even custom states and priorities." +"The ticket composer will set all outgoing messages to **signed and " +"encrypted** by default (assuming the required certificates exist)." msgstr "" -#: ../system/translations.rst:None -msgid "Translation management screen within the admin menu" +#: ../system/integrations/smime/manage-certificates.rst:82 +msgid "These defaults can be modified on a per-group basis:" msgstr "" -#: ../system/translations.rst:31 -msgid "Updating Translations" +#: ../system/integrations/smime/manage-certificates.rst:None +msgid "Zammad allowing to choose the default behavior on per group basis" msgstr "" -#: ../system/translations.rst:33 +#: ../system/integrations/smime/manage-certificates.rst:89 msgid "" -"Because of how Zammad ships translations, the only way to update the system " -"translations is to update your Zammad installation. The benefit of this is " -"that you no longer need internet access during a Zammad upgrade as the " -"package has everything it requires already." +"Of course, agents can always manually change these settings on each email " +"they send out." msgstr "" -#: ../system/translations.rst:39 -msgid "Translation of Custom Objects" +#: ../system/integrations/smime/prerequisites.rst:4 +msgid "A certificate *and* private key for your own organization" msgstr "" -#: ../system/translations.rst:41 +#: ../system/integrations/smime/prerequisites.rst:6 msgid "" -"No problem at all! You can customize any translation locally, even if it is " -"not initially provided by the system." +"(Use this to ✒️ **sign outgoing messages** and 🔓 **decrypt incoming " +"messages**.)" msgstr "" -#: ../system/translations.rst:44 +#: ../system/integrations/smime/prerequisites.rst:9 msgid "" -"Translation is supported for a broad number of features, including but not " -"limited to custom:" +"Certificates belonging your contacts, or their issuing certificate authority " +"(CA)" msgstr "" -#: ../system/translations.rst:47 -msgid "Object Attributes" +#: ../system/integrations/smime/prerequisites.rst:11 +msgid "" +"(Use these to ✅ **verify incoming message signatures** and 🔒 **encrypt " +"outgoing messages**.)" msgstr "" -#: ../system/translations.rst:48 -#, fuzzy -msgid "Ticket Macros" -msgstr "Macros" - -#: ../system/translations.rst:49 -msgid "Ticket Overviews" +#: ../system/integrations/smime/prerequisites.rst:14 +msgid "🙋 **I'm new to S/MIME. Where can I get a certificate?**" msgstr "" -#: ../system/translations.rst:50 -msgid "Ticket Priorities" +#: ../system/integrations/smime/prerequisites.rst:16 +msgid "" +"The easiest way to get certificates is to buy an annual subscription through " +"a commercial CA, such as:" msgstr "" -#: ../system/translations.rst:51 -msgid "Ticket States" +#: ../system/integrations/smime/prerequisites.rst:19 +msgid "" +"`Sectigo (formerly Comodo) `_" msgstr "" -#: ../system/translations.rst:54 -msgid "Customizing Translations" +#: ../system/integrations/smime/prerequisites.rst:20 +msgid "`Secorio `_" msgstr "" -#: ../system/translations.rst:56 -msgid "" -"Within the translation screen, simply click on the **New Translation** " -"button." +#: ../system/integrations/smime/prerequisites.rst:21 +msgid "`GlobalSign `_" msgstr "" -#: ../system/translations.rst:None -msgid "New translation dialog" +#: ../system/integrations/smime/prerequisites.rst:23 +msgid "(Zammad is not affiliated with these CAs in any way.)" msgstr "" -#: ../system/translations.rst:62 +#: ../system/integrations/smime/prerequisites.rst:25 msgid "" -"In the dialog you can immediately enter the exact translation source (if you " -"know it) and your custom translation text for it and click **Submit**." +"You can also generate your own self-signed certificates, but the process is " +"complicated and usually 🙅 **involves extra work for your contacts**." msgstr "" -#: ../system/translations.rst:65 +#: ../system/integrations/smime/prerequisites.rst:29 msgid "" -"Alternatively, try to search for translation suggestions in the list below. " -"Selecting an item from the list will pre-fill the translation source for you " -"and then you can just enter your custom translation." +"Bear in mind that 🤝 **S/MIME only works if the other party is using it, too." +"**" msgstr "" -#: ../system/translations.rst:69 -msgid "" -"The target language will always default to your current language selection. " -"If you need to translate for a different language, simply change the " -"selection before submitting." +#: ../system/integrations/smime/prerequisites.rst:32 +msgid "Certificate and Private Key Checks on Upload" msgstr "" -#: ../system/translations.rst:73 +#: ../system/integrations/smime/prerequisites.rst:34 msgid "" -"All your custom translations will show up in the overview table when added. " -"And they will even persist across Zammad updates!" +"The certificate and public key validation is based on the ``X509v3`` " +"extensions." msgstr "" -#: ../system/translations.rst:76 -msgid "" -"Make sure to reload your browser if a translated string is not displayed." +#: ../system/integrations/smime/prerequisites.rst:49 +msgid "Uploading a *client certificate*?" msgstr "" -#: ../system/translations.rst:80 -msgid "Reverting to Original Translations" +#: ../system/integrations/smime/prerequisites.rst:41 +msgid "The following attributes are required then:" msgstr "" -#: ../system/translations.rst:82 -msgid "" -"If you want to revert a custom translation to original text, simply use the " -"appropriate action within the row of the overview table." +#: ../system/integrations/smime/prerequisites.rst:39 +msgid "Subject Alternative Name (at least one email address has to be present)" msgstr "" -#: ../system/translations.rst:85 -msgid "" -"Depending on the type of the translation source, the action has a slightly " -"different name:" +#: ../system/integrations/smime/prerequisites.rst:40 +msgid "Key Usage (``Digital Signature`` and/or ``Key Encipherment``)" msgstr "" -#: ../system/translations.rst:88 -msgid "**Reset** for customized system translations" +#: ../system/integrations/smime/prerequisites.rst:41 +msgid "Public key algorithm (either ``RSA`` or ``EC``)" msgstr "" -#: ../system/translations.rst:89 -msgid "**Remove** for customized local translations" +#: ../system/integrations/smime/prerequisites.rst:43 +msgid "" +"The Extended Key Usage attribute is optional. If the certificate provides " +"the named attribute, than it must contain the value ``E-mail Protection``." msgstr "" -#: ../system/translations.rst:91 +#: ../system/integrations/smime/prerequisites.rst:46 msgid "" -"In both cases, the action will remove the customized translation after a " -"confirmation." +"Please note that any usable email adress has to be prefixed with ``email:`` " +"or ``rfc822:``." msgstr "" -#: ../system/translations.rst:None -msgid "Screenshot showing the location of the Remove action" +#: ../system/integrations/smime/prerequisites.rst:49 +msgid "The named public key algorithms are mandatory for private keys as well." msgstr "" -#: ../system/translations.rst:99 -msgid "Inline Translations" +#: ../system/integrations/smime/prerequisites.rst:54 +msgid "Uploading a *CA certificate*?" msgstr "" -#: ../system/translations.rst:101 +#: ../system/integrations/smime/prerequisites.rst:52 msgid "" -"If you prefer a more hands-on approach, you can activate the inline or on-" -"screen translation feature by pressing ``ctrl`` + ``alt`` + ``t`` at any " -"time and on any screen." +"In the case of an uploaded CA certificate, providing the value ``CA:TRUE`` " +"in the attribute *Basic Contstraints*, the previously mentioned attributes " +"are not verified." msgstr "" -#: ../system/translations.rst:105 +#: ../system/integrations/smime/prerequisites.rst:56 msgid "" -"All customizable translation texts will be highlighted for you on the " -"screen. Just click into the highlighted area and update the text in place." -msgstr "" - -#: ../system/translations.rst:None -msgid "Inline translation mode activated for the Overview screen" +"In general, the usage of any expired (``Not After``) or not yet valid (``Not " +"Before``) certificate is denied for outgoing emails." msgstr "" -#: ../system/translations.rst:112 -msgid "" -"When finished editing, simply press ``ctrl`` + ``alt`` + ``t`` again to " -"deactivate." +#: ../system/integrations/smime/prerequisites.rst:59 +msgid "Example certificate:" msgstr "" -#: ../system/translations.rst:117 +#: ../system/integrations/smime/prerequisites.rst:85 msgid "" -"Even though it's available on any screen, the inline translation feature " -"requires admin permissions. It works only for the current language " -"selection. If you need to translate a different language, first change the " -"language in your :user-docs:`profile settings `." +"Please note that Zammad will distrust senders by default. This means that " +"you're always required to provide certificate data, no matter if for signing " +"or encrypting." msgstr "" -#: ../system/variables.rst:2 -msgid "Variables" +#: ../system/integrations/smime/prerequisites.rst:89 +msgid "This is by design and can't be adjusted." msgstr "" -#: ../system/variables.rst:4 +#: ../system/integrations/smime/troubleshooting.rst:4 msgid "" -"Please note that this is just an overview of available variables. It might " -"be incomplete or variables might not be available within some functions. If " -"you're missing variables or are not sure if something is not working as " -"expected, feel free to ask over at the `Community `_." +"All of the system's latest S/MIME activity is displayed in the **Recent " +"Logs** section." msgstr "" -#: ../system/variables.rst:10 -msgid "" -"Variables can be called by typing ``::`` (just like text modules in the " -"frontend), as long as you're in a supported text field within the backend. " -"Zammad will display all variables being available within this context and " -"replace it to the variable as soon as you selected an entry." +#: ../system/integrations/smime/troubleshooting.rst:11 +msgid "Sample entries of in- and outgoing S/MIME related emails." msgstr "" -#: ../system/variables.rst:15 +#: ../system/integrations/smime/troubleshooting.rst:11 msgid "" -"You have an empty field which you referenced and it appears as ``-``? That's " -"currently working as designed - you might want to ensure that these fields " -"always have a value." +"Logs report the status and details of all mail, both incoming and outgoing, " +"that used signing/verification or encryption/decryption." msgstr "" -#: ../system/variables.rst:20 -msgid "Variable Categories" +#: ../system/integrations/smime/troubleshooting.rst:14 +msgid "" +"This log does **not** include email sent by :doc:`triggers ` or the :doc:`scheduler `. For those, check your " +"``production.log``." msgstr "" -#: ../system/variables.rst:31 -msgid "Wait, What About Custom Objects?" +#: ../system/integrations/smime/troubleshooting.rst:20 +msgid "Common Issues" msgstr "" -#: ../system/variables.rst:33 -msgid "" -"Good point! Of course, we can't predict what objects you might create, but " -"we can give you a hint on how to put the puzzle together to get your custom " -"values." +#: ../system/integrations/smime/troubleshooting.rst:30 +msgid "I received a signed/encrypted email before I set up S/MIME integration" msgstr "" -#: ../system/variables.rst:36 -msgid "" -"For this, we'll talk about the inner part of the variable (so everything " -"within ``#{}``), please put the outer part around to have a valid variable. " -"The first part of the variable name consist of the object type. Currently " -"these are:" +#: ../system/integrations/smime/troubleshooting.rst:23 +msgid "" +"No problem. Once S/MIME has been enabled and the appropriate certificates " +"have been added, agents will be prompted to retry verification/decryption on " +"matching emails." msgstr "" -#: ../system/variables.rst:41 -msgid "Ticket (``ticket``)" +#: ../system/integrations/smime/troubleshooting.rst:0 +msgid "Screenshot of user prompt to retry decryption" msgstr "" -#: ../system/variables.rst:42 -msgid "User (``user``)" +#: ../system/integrations/smime/troubleshooting.rst:38 +msgid "The 🔒 **Encrypt** button is disabled" msgstr "" -#: ../system/variables.rst:43 -msgid "Organization (``organization``)" +#: ../system/integrations/smime/troubleshooting.rst:33 +msgid "Have you added the recipient's certificate?" msgstr "" -#: ../system/variables.rst:44 -msgid "Group (``group``)" +#: ../system/integrations/smime/troubleshooting.rst:34 +msgid "Are you sure the recipient's certificate is valid?" msgstr "" -#: ../system/variables.rst:46 -msgid "" -"The second part is the name of the object. This is the name you define " -"during object creation and can be found within the object menu at any time. " -"The first and second part of a variable is divided by a point, e.g.: " -"``ticket.number`` which will in total be ``#{ticket.number}``." +#: ../system/integrations/smime/troubleshooting.rst:35 +msgid "Have you checked your ``production.log`` for more details?" msgstr "" -#: ../system/variables.rst:51 +#: ../system/integrations/smime/troubleshooting.rst:37 msgid "" -"Now, in some situations it's possible that you'll need to use a third part. " -"The best example for such a situation would be a ``select`` or ``tree-" -"select`` field which will by default return the key value, not it's display " -"name. For this, just extend your variable with ``.value``. This will result " -"in ``#{ticket.select.value}``." +"If encryption doesn't work in the composer, it won't work in :doc:`triggers " +"` or the :doc:`scheduler ` either!" msgstr "" -#: ../system/variables.rst:60 -msgid "Using Translated Variables" +#: ../system/integrations/smime/troubleshooting.rst:42 +msgid "The ✅ **Sign** button is disabled" msgstr "" -#: ../system/variables.rst:62 +#: ../system/integrations/smime/troubleshooting.rst:41 msgid "" -"If you want to use a translated variable in triggers or schedulers, you can " -"extend the placeholder like this: ``#{t(ticket.state.name)}``. The ``t`` " -"tells Zammad to search for fitting translated strings. The used output " -"language is based on the system language of Zammad which you can set in the " -"admin panel under :doc:`/settings/branding` or based on the selected locale " -"in the trigger/scheduler edit dialog." +"Have you added **both the certificate and private key** for your " +"organization?" msgstr "" -#: ../system/variables.rst:69 +#: ../system/integrations/smime/troubleshooting.rst:42 msgid "" -"A possible use-case: you want to send your customers updates on tickets via " -"trigger or scheduler which should include the state of the ticket. Using the " -"default ``#{ticket.state.name}`` (without the translation flag ``t()``) " -"would lead to the output of the original (english) name of the state." +"Does the email address on the certificate match the email address of the " +"agent/group composing the email?" msgstr "" -#: ../system/variables.rst:75 -msgid "Date and Time Formatting" +#: ../system/integrations/smime/troubleshooting.rst:45 +msgid "Error: “Fingerprint already taken”" msgstr "" -#: ../system/variables.rst:77 -msgid "" -"The system (trigger/scheduler selected) locale and timezone predefines a " -"default format of date and timestamp. This format is customizable by using " -"the ``dt()`` method." +#: ../system/integrations/smime/troubleshooting.rst:45 +msgid "Are you sure you haven't added this certificate already?" msgstr "" -#: ../system/variables.rst:79 -msgid "The method arguments are as follows:" +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Error: “❌ invalid byte sequence in UTF-8”" msgstr "" -#: ../system/variables.rst:81 -msgid "The date or timestamp variable you want to format." +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Please ensure to provide PEM formatted certificate and keys." msgstr "" -#: ../system/variables.rst:82 -msgid "The output format string." +#: ../system/integrations/smime/troubleshooting.rst:49 +msgid "Did you check if the provided file is a valid certificate or key?" msgstr "" -#: ../system/variables.rst:83 -msgid "The timezone to apply (optional)." +#: ../system/integrations/zabbix.rst:2 +msgid "Zabbix Integration" msgstr "" -#: ../system/variables.rst:86 +#: ../system/integrations/zabbix.rst:5 msgid "" -"``#{dt(ticket.updated_at, \"%A %Y-%m-%d %H:%M in the office\", \"Europe/" -"Berlin\")}``" +"This guide describes how to integrate your Zabbix 5.4 installation with " +"Zammad using the Zabbix webhook feature. This guide will provide " +"instructions on setting up a media type, a user and an action in Zabbix." msgstr "" -#: ../system/variables.rst:87 -msgid "Monday, 2024-03-18 15:31 in the office" +#: ../system/integrations/zabbix.rst:12 +msgid "Zammad with enabled HTTP Token Authentication" msgstr "" -#: ../system/variables.rst:89 -msgid "" -"If you want to use our example, make sure to paste the string above without " -"formatting (``CTRL+Shift+v``), otherwise it won't work." +#: ../system/integrations/zabbix.rst:13 +msgid "Zabbix version 5.4 or higher" msgstr "" -#: ../system/variables.rst:93 -msgid "The following table lists available format directives:" +#: ../system/integrations/zabbix.rst:16 +msgid "Setting up a Zammad" msgstr "" -#: ../system/variables.rst:99 -msgid "Parameter" +#: ../system/integrations/zabbix.rst:18 +msgid "Enable **API Token Access** in Settings > System > API." msgstr "" -#: ../system/variables.rst:102 -msgid "``%Y``" +#: ../system/integrations/zabbix.rst:20 +msgid "" +"Create a **new user** for a Zabbix alerter with an **email address** and " +"create a personal user token with **ticket.agent** permissions." msgstr "" -#: ../system/variables.rst:103 -msgid "Year with 4 digits" +#: ../system/integrations/zabbix.rst:24 +msgid "Zabbix Webhook Configuration" msgstr "" -#: ../system/variables.rst:104 -msgid "Use ``%y`` for year with 2 digits" +#: ../system/integrations/zabbix.rst:27 +#, fuzzy +msgid "Create a Global Macro" +msgstr "Macros" + +#: ../system/integrations/zabbix.rst:29 +msgid "" +"Before setting up the **Webhook**, you need to setup the global macro " +"**{$ZABBIX.URL}**, which must contain the **URL** to the **Zabbix frontend**." msgstr "" -#: ../system/variables.rst:105 -msgid "``%m``" +#: ../system/integrations/zabbix.rst:33 +msgid "" +"In the **Administration** > **Media types** section, import the `Template`_." msgstr "" -#: ../system/variables.rst:106 -msgid "Month of year (as number with zero-padding)" +#: ../system/integrations/zabbix.rst:38 +msgid "Open the added **Zammad** media type and set:" msgstr "" -#: ../system/variables.rst:107 -msgid "Use ``%-m`` for month without zero-padding" +#: ../system/integrations/zabbix.rst:40 +msgid "**zammad\\_access\\_token** to the your **Personal User Token**" msgstr "" -#: ../system/variables.rst:108 -msgid "``%d``" +#: ../system/integrations/zabbix.rst:41 +msgid "" +"**zammad\\_url** to the **frontend URL** of your **Zammad** installation" msgstr "" -#: ../system/variables.rst:109 -msgid "Day of month (as number with zero-padding)" +#: ../system/integrations/zabbix.rst:43 +msgid "**zammad\\_customer** to your **Zammad user email**." msgstr "" -#: ../system/variables.rst:110 -msgid "Use ``%e`` for day without zero-padding" +#: ../system/integrations/zabbix.rst:44 +msgid "" +"**zammad\\_enable\\_tags** to **true** or **false** to enable or disable " +"trigger tags. **Important**: if you enable tag support, each tag is set with " +"a separate request." msgstr "" -#: ../system/variables.rst:111 -msgid "``%H``" +#: ../system/integrations/zabbix.rst:48 +msgid "" +"If you want to prioritize issues according to **severity** values in Zabbix, " +"you can define mapping parameters:" msgstr "" -#: ../system/variables.rst:112 -msgid "Hour of day in 24h notation with zero-padding" +#: ../system/integrations/zabbix.rst:51 +msgid "**severity\\_**: Zammad priority ID" msgstr "" -#: ../system/variables.rst:113 -msgid "Use ``%k`` for hour without zero-padding" +#: ../system/integrations/zabbix.rst:53 +msgid "Click the **Update** button to save the **Webhook** settings." msgstr "" -#: ../system/variables.rst:114 -msgid "``%I``" +#: ../system/integrations/zabbix.rst:55 +msgid "" +"To receive notifications in **Zammad**, you need to create a **Zabbix user** " +"and add **Media** with the **Zammad** type." msgstr "" -#: ../system/variables.rst:115 -msgid "Hour of day in 12h notation with zero-padding" +#: ../system/integrations/zabbix.rst:58 +msgid "" +"For **Send to**: enter any text, as this value is not used, but is required." msgstr "" -#: ../system/variables.rst:116 +#: ../system/integrations/zabbix.rst:61 msgid "" -"Use ``%l`` for hour without zero-padding and ``%p`` / ``%P`` for meridian " -"indicator" +"For more information, use the `Zabbix documentation `_." msgstr "" -#: ../system/variables.rst:117 -msgid "``%M``" +#: ../system/maintenance.rst:2 +msgid "Maintenance" msgstr "" -#: ../system/variables.rst:118 -msgid "Minute of hour" +#: ../system/maintenance.rst:4 +msgid "" +"Zammad comes with a maintenance mode that you can use for e.g. updating the " +"instance or changing settings while restricting availability and functions." msgstr "" -#: ../system/variables.rst:120 -msgid "``%S``" +#: ../system/maintenance.rst:13 +msgid "Mode" msgstr "" -#: ../system/variables.rst:121 -msgid "Second of Minute" +#: ../system/maintenance.rst:8 +msgid "The mode setting allows you to enable or disable the maintenance mode." msgstr "" -#: ../system/variables.rst:123 -msgid "``%A``" +#: ../system/maintenance.rst:10 +msgid "Defaults to *off*." msgstr "" -#: ../system/variables.rst:124 -msgid "Weekday name" +#: ../system/maintenance.rst:12 +msgid "" +"The maintenance mode will restrict access to administrative roles only. This " +"means agents and customers are logged off." msgstr "" -#: ../system/variables.rst:125 -msgid "Use ``%a`` for abbreviated name or ``%^A`` for uppercase name" +#: ../system/maintenance.rst:23 +msgid "@Login" msgstr "" -#: ../system/variables.rst:126 -msgid "``%B``" +#: ../system/maintenance.rst:16 +msgid "" +"This setting allows you to provide a login message within a green banner " +"above the login screen. Click into the green banner in the settings page to " +"adjust your message. To activate the message, activate the *@Login* setting." msgstr "" -#: ../system/variables.rst:127 -msgid "Month name" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing the default login message within the\n" +"settings page" msgstr "" -#: ../system/variables.rst:128 -msgid "Use ``%b`` for abbreviated name" +#: ../system/maintenance.rst:26 +msgid "" +"Send an informative message to **all active sessions**. This comes handy to " +"inform your agents e.g. about mayor outages or to force reloads after " +"configuration changes." msgstr "" -#: ../system/variables.rst:129 -msgid "``%U``" +#: ../system/maintenance.rst:31 +msgid "This is the messages title (slightly bigger than the normal message)." msgstr "" -#: ../system/variables.rst:130 -msgid "Week number of current year" +#: ../system/maintenance.rst:34 +msgid "The text you want to provide to your logged in sessions." msgstr "" -#: ../system/variables.rst:131 -msgid "Use ``%W`` for a different calculation method" +#: ../system/maintenance.rst:39 +msgid "Reload application" msgstr "" -#: ../system/variables.rst:134 +#: ../system/maintenance.rst:37 msgid "" -"We support the known format directives for the Ruby built-in method " -"``strftime`` of the ``DateTime`` class. For more information, see `here " -"`_." +"Selecting this option will change the message acceptance button from *Close* " +"(with nothing happening) to *Continue session*, which forces the application " +"to reload." msgstr "" -#: ../system/variables/article.rst:2 -msgid "Articles" +#: ../system/maintenance.rst:43 +msgid "" +"If you have customers that are logged in to Zammad, they'll also be notified " +"if they're active in that moment." +msgstr "" + +#: ../system/maintenance.rst:48 +msgid "Example without reload application" msgstr "" -#: ../system/variables/article.rst:4 ../system/variables/config.rst:4 -#: ../system/variables/current-user.rst:4 ../system/variables/ticket.rst:4 +#: ../system/maintenance.rst:52 msgid "" -"If you're missing variables or are not sure if something is not working as " -"expected, feel free to ask over at the `Community `_." +"Message setting within Zammad's admin settings without ticket reload " +"application setting." msgstr "" -#: ../system/variables/article.rst:6 +#: ../system/maintenance.rst:0 msgid "" -"Below you can find all available ticket article-based variables within " -"Zammad. These can be called via Triggers for example. If you're unsure if " -"Zammad does support variables at the point you're at, you can try to type " -"``::`` to check." +"Screenshot showing the send message settings without ticket\n" +"reload application set" msgstr "" -#: ../system/variables/article.rst:9 ../system/variables/config.rst:9 -#: ../system/variables/ticket.rst:9 +#: ../system/maintenance.rst:61 ../system/maintenance.rst:85 msgid "" -"The below list gives you an example what kind of data you can expect, it's " -"not intended to explain the data itself." +"The modal all other active sessions will see upon pressing *Send to clients*." msgstr "" -#: ../system/variables/article.rst:11 -msgid "Article Variables" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing modal caused by maintenance's message\n" +"without reload application ticket" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "name" +#: ../system/maintenance.rst:72 +msgid "Example with reload application" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "variable" +#: ../system/maintenance.rst:76 +msgid "" +"Message setting within Zammad's admin settings with ticket reload " +"application setting." msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "example" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing the send message settings with ticket\n" +"reload application set" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Web" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing modal caused by maintenance's message\n" +"with reload application ticket" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.web}``" +#: ../system/monitoring.rst:2 +msgid "Monitoring" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``https://zammad.com`` or empty if not set in user object" +#: ../system/monitoring.rst:4 +msgid "" +"This function is only available in self hosted instances. If you use Zammad " +"in our cloud, we are monitoring the system on our own and take steps to fix " +"potential problems directly." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > VIP" +#: ../system/monitoring.rst:11 +msgid "" +"On the monitoring page, you can see the current health state of Zammad under " +"\"*Current Status*\" at the bottom. This can be useful if you want to have a " +"look if everything is up and running. As an example, you could have a look " +"in the monitoring when you assume that some emails aren't processed from " +"Zammad." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.vip}``" +#: ../system/monitoring.rst:17 +msgid "**Can't receive an email and the monitoring response is \"healthy\"?**" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -msgid "``true`` or ``false``" +#: ../system/monitoring.rst:19 +msgid "" +"Zammad will just inform you about unprocessable emails. This is not the case " +"for oversized emails. You can adjust the maximum email size in :doc:`../" +"channels/email/settings`." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Phone" +#: ../system/monitoring.rst:24 +msgid "Monitoring API" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.phone}``" +#: ../system/monitoring.rst:26 +msgid "" +"Beside the indication in the monitoring page, you can also use an external " +"monitoring tool to monitor Zammad's health. To request the health of Zammad, " +"you need to provide the API key (token) to the external monitoring tool. You " +"can copy the token from the \"*Current Token*\" field as well as the whole " +"API endpoint of your system (\"*Health Check*\" field), in which the API " +"token is already included." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``+4930123456789`` or empty if not set in user object" +#: ../system/monitoring.rst:37 +msgid "Screenshot showing Current Token and Health Check" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Note" +#: ../system/monitoring.rst:37 +msgid "Screenshot showing Token and Health Check" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.note}``" +#: ../system/monitoring.rst:39 +msgid "" +"In addition to that, you can reset the auto-generated token to make sure " +"that already configured monitoring systems won't work anymore. So, please " +"use this \"*Reset*\" button only if you know what you do!" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Some note about user`` or empty if not set in user object" +#: ../system/monitoring.rst:44 +msgid "Example Output" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Mobile" +#: ../system/monitoring.rst:0 +msgid "No issues found" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.mobile}``" +#: ../system/monitoring.rst:48 ../system/monitoring.rst:60 +msgid "**Indicator in Zammad**:" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Login" +#: ../system/monitoring.rst:0 +msgid "Screenshot showing monitoring with no issues" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.login}``" +#: ../system/monitoring.rst:54 ../system/monitoring.rst:66 +msgid "**API response**::" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -#: ../system/variables/ticket.rst:1 -msgid "``jdoe``" +#: ../system/monitoring.rst:0 +msgid "Issues were found" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Lastname" +#: ../system/monitoring.rst:0 +msgid "Screenshot showing monitoring with issues" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.lastname}``" +#: ../system/objects.rst:2 +msgid "Objects" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -#: ../system/variables/ticket.rst:1 -msgid "``Doe`` or empty if not set" +#: ../system/objects.rst:4 +msgid "" +"In Zammad you can add your own fields to tickets, users, organizations and " +"even groups (these are called \"objects\"). This can be useful if you need " +"to add further information to a ticket or any other object in Zammad and the " +"information doesn't fit in any existing field." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Firstname" +#: ../system/objects.rst:11 +msgid "" +"Try to avoid deleting attributes (and disable them instead) as Zammad might " +"run into unexpected conditions if they are referenced somewhere." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.firstname}``" +#: ../system/objects.rst:16 +msgid "" +"Here's an overview of object attributes. On the upper right you can add new " +"attributes. By default, there will be no custom fields - standard attributes " +"will be grayed out, you can't delete or change those. You can edit custom " +"attributes (they are displayed in black font and have a trash bin on the " +"right side) just by clicking on them." msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "``Joe`` or empty if not set" +#: ../system/objects.rst:24 +msgid "" +"Attributes you add to Zammad, no matter if they have default values or not, " +"will not update existing information. This means a new ticket field " +"technically will be empty unless you populate it." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Fax" +#: ../system/objects.rst:28 +msgid "" +"Especially in ticket scope this also means that newly added attributes will " +"be indicated as \"changed\" to agents that view the ticket. This may " +"interfere with Zammad's tabs behavior." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.fax}``" +#: ../system/objects.rst:40 +msgid "Ordering Attributes" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Email" +#: ../system/objects.rst:42 +msgid "" +"Since Zammad introduced :doc:`/system/core-workflows` the need to have a " +"custom positioning for attributes has become more important than ever." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.email}``" +#: ../system/objects.rst:45 +msgid "" +"To adjust the position of such an attribute, simply click on the attribute " +"entry in question, scroll down and adjust the position number. Please note " +"that you cannot change the positioning of default attributes." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``jdoe@example.com``" +#: ../system/objects.rst:49 +msgid "" +"In case two attributes have the same position value, Zammad will sort " +"alphabetically by name automatically." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Department" +#: ../system/objects.rst:None +msgid "" +"Screenshot showing custom attribute entries ordered in between default ones" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.department}``" +#: ../system/objects.rst:56 +msgid "Updating Database After Adding or Editing Attributes" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Sales`` or empty if not set in user object" +#: ../system/objects.rst:58 +msgid "" +"When adding or changing attributes, Zammad will not apply the changes " +"instantly, but instead shows you the changed attributes first. If you're " +"ready to go, just click on \"Update database\" to apply the changes to " +"Zammad. If you made a mistake or just want to discard your changes, click " +"\"Discard changes\"." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Address" +#: ../system/objects.rst:64 +msgid "" +"After applying the changes with \"Update Database\", a restart of Zammad is " +"**mandatory**. If you don't perform it, you may experience unexpected " +"behavior or even errors. You may want to do this kind of configuration " +"during maintenance windows." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.address}``" +#: ../system/objects.rst:72 +msgid "" +"Changes on objects require you to update the database to apply these changes." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Some street 1, 12345 Berlin`` or empty if not set in user object" +#: ../system/objects.rst:75 +msgid "**🤓 Service restarts can be automated**" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated" +#: ../system/objects.rst:0 +msgid "Hosted environments automatically restart for you." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_at}``" +#: ../system/objects.rst:0 +msgid "" +"If you're using a self-hosted installation you can use :docs:`environment " +"variables `" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``2019-10-08 15:24:47 UTC``" +#: ../system/objects.rst:82 +msgid "System Attributes" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Type > Name" +#: ../system/objects.rst:84 +msgid "" +"Zammad comes with pre-configured attributes. Some of them can't be edited " +"via UI (or at all). This is required for proper operation of Zammad and not " +"a bug." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.type.name}``" +#: ../system/objects.rst:90 +msgid "Ticket State" msgstr "" -#: ../system/variables/article.rst:1 +#: ../system/objects.rst:92 msgid "" -"``email`` (`list of article types `_)" +"If the pre-configured states aren't enough for you or you want to change " +"them, you can do so by clicking on the cogwheel icon in the state row in the " +"ticket tab. But you should be careful when changing pre-configured states. " +"This can lead to unwanted behavior in some cases." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > To" +#: ../system/objects.rst:None +msgid "Screenshot showing highlighted ticket state attribute" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.to}``" +#: ../system/objects.rst:122 +msgid "Handling of states" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``helpdesk@example.com``" +#: ../system/objects.rst:102 +msgid "" +"In the state configuration screen, you can add new states, disable states or " +"change states." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > TicketID" +#: ../system/objects.rst:0 +msgid "Screenshot showing table of default ticket states" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.ticket_id}``" +#: ../system/objects.rst:110 +msgid "" +"To add a new state, click on the \"New Ticket State\" button in the top " +"right corner. To change an existing state, simply click on the affected " +"state. This opens an edit dialog." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``1`` (not ticket number)" +#: ../system/objects.rst:114 +msgid "" +"You can also clone a state or set them to \"Default for new tickets\" or " +"\"Default for follow-ups\" by clicking on the ⁝ action button and select the " +"desired function." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Subject" +#: ../system/objects.rst:118 +msgid "" +"*Default for new tickets* means that this state is used for every newly " +"created ticket." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.subject}``" +#: ../system/objects.rst:121 +msgid "" +"*Default for follow-ups* means that this state is used if the ticket is re-" +"opened after it was closed." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``My amazing subject``" +#: ../system/objects.rst:171 +msgid "Ticket state in detail" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Sender > Name" +#: ../system/objects.rst:125 +msgid "" +"Below you can find a description for each field and option. Please head over " +"to the :ref:`example ` to see the edit dialog." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.sender.name}``" +#: ../system/objects.rst:129 +msgid "" +"This is the name of the state and what you and your agents are seeing when " +"choosing a state somewhere (e.g. in tickets, trigger configuration)." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Customer``, ``Agent`` or ``System``" +#: ../system/objects.rst:137 +msgid "" +"There are different state types you can choose from. By default, Zammad " +"comes with one state per state type." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Visibility" +#: ../system/objects.rst:140 +msgid "" +"**new**: for states for tickets that are new and it hasn't been worked on " +"them" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.internal}``" +#: ../system/objects.rst:142 +msgid "" +"**open**: for states for tickets that are in progress and agents are working " +"on them" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``false`` or ``true`` (false if not internal)" +#: ../system/objects.rst:144 +msgid "**merged**: for states for tickets that are merged with other tickets" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > From" +#: ../system/objects.rst:145 +msgid "" +"**pending reminder**: for states for tickets that are in progress and you " +"want to set a reminder. (default example: *pending reminder*)" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.from}``" +#: ../system/objects.rst:147 +msgid "" +"**pending action**: for states for tickets that are waiting for a specified " +"time and then change their state (default example: *pending close*)" msgstr "" -#: ../system/variables/article.rst:1 +#: ../system/objects.rst:150 msgid "" -"``Joe Doe `` may differ, depends on ``FROM`` of send mail" +"**closed**: for states for tickets that are finished and do not need to be " +"processed further" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Web" +#: ../system/objects.rst:153 +msgid "" +"⚠️ Choosing the correct state type is important! If you are in doubt, have a " +"look on the default states and their types!" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.web}``" +#: ../system/objects.rst:158 +msgid "Ignore escalation" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > VIP" +#: ../system/objects.rst:157 +msgid "" +"Here you can define whether tickets of this state will count to escalation " +"time or not." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.vip}``" +#: ../system/objects.rst:161 +msgid "" +"You can create a note for the state to inform other admins about the state. " +"This has no effect on tickets." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Phone" +#: ../system/objects.rst:165 +msgid "Set the state to *active* or *inactive*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.phone}``" +#: ../system/objects.rst:167 +msgid "" +"it is technically possible to set all states to inactive. To keep Zammad " +"working in such a case, the inactive flag of one of the states is ignored." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Note" +#: ../system/objects.rst:194 +msgid "Ticket state example" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.note}``" +#: ../system/objects.rst:174 +msgid "" +"Let's assume we want to create a new state which indicates that the ticket " +"has to wait for a response of a third party (e.g. service contractor or " +"manufacturer) and we want to to be able to set a reminder." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Mobile" +#: ../system/objects.rst:178 +msgid "" +"First we give the new state a proper name. In this example we call it " +"\"waiting for manufacturer\"." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.mobile}``" +#: ../system/objects.rst:181 +msgid "" +"As state type we choose \"pending reminder\". This indicates that the ticket " +"is still open and we can set a reminder. This reminder can be useful if our " +"manufacturer sometimes isn't responding or we want to remind him to give us " +"an answer." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Login" +#: ../system/objects.rst:186 +msgid "" +"We choose \"no\" for \"ignore escalation\" because we want to escalate the " +"tickets even if we are waiting on the manufacturer's feedback." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.login}``" +#: ../system/objects.rst:189 +msgid "The **result** in the creation dialog will look like this:" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Lastname" +#: ../system/objects.rst:0 +msgid "Screenshot showing ticket state creation dialog with example" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.lastname}``" +#: ../system/objects.rst:199 +msgid "Ticket Priority" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Firstname" +#: ../system/objects.rst:201 +msgid "" +"If the pre-configured priorities aren't enough for you or you want to change " +"them, you can do so by clicking on the cogwheel icon in the priority row in " +"the ticket tab:" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.firstname}``" +#: ../system/objects.rst:None +msgid "Screenshot showing highlighted ticket priority attribute" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Fax" +#: ../system/objects.rst:226 +msgid "Handling of priorities" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.fax}``" +#: ../system/objects.rst:210 +msgid "" +"In the priority configuration screen, you can add new priorities, disable " +"priorities or change priorities." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Email" +#: ../system/objects.rst:0 +msgid "Screenshot showing table of default ticket priorities" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.email}``" +#: ../system/objects.rst:218 +msgid "" +"To add a new priority, click on the \"New Priority\" button in the top right " +"corner. To change an existing priority, simply click on the affected " +"priority. This opens an edit dialog." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Department" +#: ../system/objects.rst:222 +msgid "" +"You can also clone a priority or set them to \"Default for new tickets\" by " +"clicking on the ⁝ action button and select the desired function." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.department}``" +#: ../system/objects.rst:225 +msgid "" +"*Default for new tickets* means that this priority is used for every newly " +"created ticket." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Address" +#: ../system/objects.rst:248 +msgid "Priorities in detail" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.address}``" +#: ../system/objects.rst:229 +msgid "Below you can find a description for each field and option." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created" +#: ../system/objects.rst:232 +msgid "" +"This is the name of the priority and what you and your agents are seeing " +"when choosing a priority somewhere (e.g. in tickets, trigger configuration)." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_at}``" +#: ../system/objects.rst:242 +msgid "Highlight color" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Cc" +#: ../system/objects.rst:237 +msgid "" +"Switch between *Low priority* (light blue), *High priority* (red) and - " +"(default). This affects the displayed color for ticket titles in overviews." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.cc}``" +#: ../system/objects.rst:241 +msgid "The color options are currently limited to the mentioned options." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``jdoe@example.com, company@example.com``" +#: ../system/objects.rst:245 +msgid "" +"You can create a note for the priority to inform other admins about the " +"priority. This has no effect on tickets." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Text" +#: ../system/objects.rst:249 +msgid "Set the priority to *active* or *inactive*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.body}``" +#: ../system/objects/external-data-source-example.rst:2 +msgid "External Data Source" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Test`` without formatting (plain)" +#: ../system/objects/external-data-source-example.rst:4 +msgid "" +"We assume you already had a look on :doc:`types` where you can find a " +"description of the individual fields." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article Text as HTML (not referenced)" +#: ../system/objects/external-data-source-example.rst:7 +msgid "" +"To reproduce this example, choose a category you want to add a custom field, " +"click on *New Attribute* and select *External data source field* under " +"*Format*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.body_as_html}``" +#: ../system/objects/external-data-source-example.rst:11 +msgid "" +"Our example story is to fetch data from an external product database. We " +"want to add our products to the tickets so that the products can be searched " +"and chosen from a list and also create a link to the product website." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Test`` with formatting" +#: ../system/objects/external-data-source-example.rst:16 +msgid "Base configuration" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "Ticket > Article#" +#: ../system/objects/external-data-source-example.rst:None +msgid "Initial steps to configure external data source object type" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "``#{ticket.article_count}``" +#: ../system/objects/external-data-source-example.rst:25 +msgid "Name: *product*" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``1`` number of ticket articles" +#: ../system/objects/external-data-source-example.rst:26 +msgid "Display: *Product*" msgstr "" -#: ../system/variables/config.rst:2 -msgid "Config" +#: ../system/objects/external-data-source-example.rst:29 +msgid "External data source configuration" msgstr "" -#: ../system/variables/config.rst:6 +#: ../system/objects/external-data-source-example.rst:31 msgid "" -"Below you'll find config related variables. These hold useful configuration " -"information that you can use within e.g. triggers to show necessary " -"information to your customer." -msgstr "" - -#: ../system/variables/config.rst:11 -msgid "Config Variables" +"First, enter the search URL making sure it contains ``#{search.term}`` as a " +"parameter:" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Fully Qualified Domain Name" +#: ../system/objects/external-data-source-example.rst:34 +msgid "**Example:** ``https://dummyjson.com/products/search?q=#{search.term}``" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.fqdn}``" +#: ../system/objects/external-data-source-example.rst:36 +msgid "" +"After that, head down to the preview section and enter a search input for " +"the external data source." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``zammad.example.com``" +#: ../system/objects/external-data-source-example.rst:39 +msgid "**Example:** ``mac``" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Ticket Hook" +#: ../system/objects/external-data-source-example.rst:41 +msgid "Then you can find a preview of the response data below:" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.ticket_hook}``" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of JSON response based on search term" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``Ticket#``" +#: ../system/objects/external-data-source-example.rst:48 +msgid "" +"We recommend using the preview to have a look on the structure. There is a " +"top-level element called ``products``. One level below, you can find the " +"attributes ``id`` and ``title``." msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > HTTP type" +#: ../system/objects/external-data-source-example.rst:52 +msgid "**Search result response based on search from example:**" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.http_type}``" +#: ../system/objects/external-data-source-example.rst:119 +msgid "" +"To tell the remote system that the desired data is located below the " +"``products`` level, you have to put it in the field *Search result list key*." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``https`` or ``http``" +#: ../system/objects/external-data-source-example.rst:122 +msgid "" +"After inserting ``products`` in the mentioned field, you get an extended " +"preview. You can find an additional box *Search result list* with a JSON " +"structure. This is the same response as before but stripped from the upper " +"``products`` element by the external data source." msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > SystemID" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of JSON response search result list" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.system_id}``" +#: ../system/objects/external-data-source-example.rst:132 +msgid "" +"Now you need to provide the keys for the search result values and labels. As " +"already mentioned, we are looking for the ``id`` and the ``title`` of our " +"products. If you haven't already, it is now a good time to look at the " +"preview of the *Search result list*." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``31`` (value between 1 and 99)" +#: ../system/objects/external-data-source-example.rst:197 +msgid "" +"After locating our two keys, we insert them in *search result value key* " +"(``id``) and in *Search result label key* (``title``)." msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Organization" +#: ../system/objects/external-data-source-example.rst:200 +msgid "" +"Basically, we configured the external data source already and we can see a " +"table in the preview section:" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.organization}``" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of product table based on search term" msgstr "" -#: ../system/variables/config.rst:1 +#: ../system/objects/external-data-source-example.rst:208 msgid "" -"``Zammad GmbH`` value set in `Branding `_" -msgstr "" - -#: ../system/variables/config.rst:1 -msgid "Config > Product Name" +"According to our example story, now just the *Link template* is missing." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.product_name}``" +#: ../system/objects/external-data-source-example.rst:210 +msgid "" +"Please note that this is an optional feature. If you don't want to use such " +"links, of course you don't have to configure it." msgstr "" -#: ../system/variables/config.rst:1 +#: ../system/objects/external-data-source-example.rst:213 msgid "" -"``Helpdesk`` value set in `Branding `_" +"We can add now an address where additional product information can be found." msgstr "" -#: ../system/variables/current-user.rst:2 -msgid "Current User" +#: ../system/objects/external-data-source-example.rst:215 +msgid "Example: ``https://your_domain.com/q=#{ticket.product}``" msgstr "" -#: ../system/variables/current-user.rst:6 -msgid "" -"Current user variables always return values of the current user that caused " -"e.g. a trigger to run." +#: ../system/objects/external-data-source-example.rst:217 +msgid "In the example, the parameter means:" msgstr "" -#: ../system/variables/current-user.rst:8 -msgid "" -"Due to the above fact, these variables are often not (yet) set or available " -"for usage." +#: ../system/objects/external-data-source-example.rst:219 +msgid "``#{}``: \"Frame\" for the insertion of information" msgstr "" -#: ../system/variables/current-user.rst:10 -msgid "" -"In situations where e.g. schedulers or triggers run, this most likely is " -"nothing you want to use." +#: ../system/objects/external-data-source-example.rst:220 +msgid "``ticket``: object level, where you create your custom object" msgstr "" -#: ../system/variables/current-user.rst:13 -msgid "Current User Variables" +#: ../system/objects/external-data-source-example.rst:221 +msgid "``product``: name of the (custom) object" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Web" +#: ../system/objects/external-data-source-example.rst:223 +msgid "" +"After configuring your *Link template*, there will be another column in the " +"preview. Hovering on the icons in the *Link* column will show you where it " +"forwards you." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.web}``" +#: ../system/objects/external-data-source-example.rst:232 +msgid "" +"In our example, one of the links looks like: https://your_domain.com/q=6, " +"where the 6 is the product id." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``https://zammad.org`` or empty if not set" +#: ../system/objects/external-data-source-example.rst:235 +msgid "You can find more information regarding the URL in :doc:`types`." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > VIP" +#: ../system/objects/includes/adding-values-hint.include.rst:3 +msgid "" +"Adding values can be tricky for first timers, don't forget to press \"➕ " +"Add\" after typing your values. Otherwise you may loose a value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.vip}``" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:1 +#: ../system/objects/includes/reposition-values.include.rst:1 +msgid "**↕️ This field type allows the positioning of its values ↔️**" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``false`` or ``true``" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:3 +msgid "" +"In order to re-arrange the field values, first edit the field. Then you can " +"use ☰ to drag the values in question to the correct position. If you want to " +"change the layer depth, double click on ☰. With it you can cycle through the " +"available layers." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Web" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:8 +msgid "When you're ready, submit your changes to save the object attribute." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.web}``" +#: :0 ../system/objects/types.rst:0 +msgid "" +"Screencast showing how to re-position values on tree select like\n" +"fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > VIP" +#: ../system/objects/includes/reposition-values.include.rst:3 +msgid "" +"In order to re-arrange the field values, edit the field and scroll below the " +"values. Make sure to tick the option \"Use custom option sort\"." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.vip}``" +#: ../system/objects/includes/reposition-values.include.rst:8 +msgid "" +"If you do not tick this field, all manual positioning you did above will be " +"lost upon saving! ☠️" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Phone" +#: ../system/objects/includes/reposition-values.include.rst:11 +msgid "" +"Now use ☰ to drag the values in question to the correct position. When " +"you're ready, submit your changes to save the object attribute." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.phone}``" +#: :0 ../system/objects/types.rst:0 +msgid "Screencast showing how to re-position values" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``004930123456789`` or empty if not set" +#: ../system/objects/includes/url-template-hint.include.rst:3 +msgid "" +"This field allows using :ref:`URL fields (Link Templates) `." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Note" +#: ../system/objects/permissions.rst:2 +msgid "Attribute Permissions" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.note}``" +#: ../system/objects/permissions.rst:7 +msgid "" +"In the object attributes configuration you can define if a field is shown " +"and if the input in the field is mandatory, separated by different screens " +"and for different :doc:`roles/permissions `." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Some note to this user`` or empty if not set" +#: ../system/objects/permissions.rst:17 +msgid "Screenshot shows object attribute permission table" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Mobile" +#: ../system/objects/permissions.rst:17 +msgid "" +"Some of the possible permissions and screen options for a user object " +"attribute." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.mobile}``" +#: ../system/objects/permissions.rst:19 +msgid "" +"Based on the object context (ticket, agent, organization, user), the " +"selectable roles (to be precise: the required permissions) and screens " +"differ. Be aware that these settings aren't affecting data creation via " +"other channels than the UI." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``0049176123456789`` or empty if not set" +#: ../system/objects/permissions.rst:24 +msgid "" +"If you want to have further customization possibilities, you should have a " +"look at the :doc:`core workflows `." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Login" +#: ../system/objects/permissions.rst:28 +msgid "Screens" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.login}``" +#: ../system/objects/permissions.rst:30 +msgid "" +"In the table below you can find an overview about the different permissions " +"and the available screens Zammad distinguishes between." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Lastname" +#: ../system/objects/permissions.rst:37 +msgid "Screen" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.lastname}``" +#: ../system/objects/permissions.rst:38 +msgid "Available for" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Firstname" +#: ../system/objects/permissions.rst:40 +msgid "create" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.firstname}``" +#: ../system/objects/permissions.rst:41 ../system/objects/permissions.rst:52 +#: ../system/objects/permissions.rst:59 ../system/objects/permissions.rst:73 +msgid "admin.user" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``John`` or empty if not set" +#: ../system/objects/permissions.rst:42 ../system/objects/permissions.rst:53 +#: ../system/objects/permissions.rst:60 +msgid "admin.organization" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Fax" +#: ../system/objects/permissions.rst:43 ../system/objects/permissions.rst:54 +#: ../system/objects/permissions.rst:61 +msgid "admin.group" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.fax}``" +#: ../system/objects/permissions.rst:44 +msgid "Creation dialog for not yet existing data" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``004930123464789`` or empty if not set" +#: ../system/objects/permissions.rst:45 +msgid "create_middle" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Email" -msgstr "" +#: ../system/objects/permissions.rst:46 ../system/objects/permissions.rst:50 +#: ../system/objects/permissions.rst:57 ../system/objects/permissions.rst:66 +#: ../system/objects/permissions.rst:70 +#, fuzzy +msgid "ticket.customer" +msgstr "Macros" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.email}``" +#: ../system/objects/permissions.rst:47 ../system/objects/permissions.rst:51 +#: ../system/objects/permissions.rst:58 ../system/objects/permissions.rst:69 +#, fuzzy +msgid "ticket.agent" +msgstr "Macros" + +#: ../system/objects/permissions.rst:48 +msgid "Ticket create dialog (middle section)" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``jdoe@customer.tld``" +#: ../system/objects/permissions.rst:49 +msgid "edit" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Department" +#: ../system/objects/permissions.rst:55 +msgid "Editing dialog for already existing data" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.department}``" +#: ../system/objects/permissions.rst:56 +msgid "view" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Sales`` or empty if not set" +#: ../system/objects/permissions.rst:62 +msgid "View-only dialog for already existing data" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Avatar" +#: ../system/objects/permissions.rst:64 +msgid "(e.g. user or organization from search)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.avatar(60,60)}``" +#: ../system/objects/permissions.rst:65 +msgid "signup" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "avatar picture with width and height in pixel (e.g. 60,60)" +#: ../system/objects/permissions.rst:67 +msgid "Sign-up screen for new customers" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Address" +#: ../system/objects/permissions.rst:68 +msgid "invite_customer" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.address}``" +#: ../system/objects/permissions.rst:71 +msgid "" +"Customer invitation screen (from :doc:`First Steps ` area)" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Some street 1, 12345 Berlin`` or empty if not set" +#: ../system/objects/permissions.rst:72 +msgid "invite_agent" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated at" +#: ../system/objects/permissions.rst:74 +msgid "" +"Agent invitation screen (from :doc:`First Steps ` area)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_at}``" +#: ../system/objects/permissions.rst:78 +msgid "Screen Options" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC``" +#: ../system/objects/permissions.rst:80 +msgid "" +"For the different screens you can select \"show\" and \"required\" options." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Phone" +#: ../system/objects/permissions.rst:82 +msgid "**shown:** Show (check) or hide (uncheck) a field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.phone}``" +#: ../system/objects/permissions.rst:83 +msgid "" +"**required:** Set a field to mandatory (check). Forces users (via UI and " +"API) to populate the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Shared organization" +#: ../system/objects/types.rst:7 +msgid "Example external data source" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.shared}``" +#: ../system/objects/types.rst:2 +msgid "Attribute types" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Note" +#: ../system/objects/types.rst:4 +msgid "" +"When adding a new object attribute, you can choose between the following " +"attribute types." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.note}``" +#: ../system/objects/types.rst:14 +msgid "" +"You cannot change the attribute format / type as soon as it is applied. If " +"you no longer need an object attribute, consider disabling it instead of " +"removing." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``A note to the organization of the user`` or empty if not set" +#: ../system/objects/types.rst:18 +msgid "**What about the translation of my attributes?**" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Name" +#: ../system/objects/types.rst:20 +msgid "" +"For some attribute types you can decide if they should be translatable or " +"not. To be precise, it works only for the selectable fields because the " +"possible choices are known and limited. For the following attribute types, " +"you can set the translatable flag:" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.name}``" +#: ../system/objects/types.rst:25 +msgid "*Boolean field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``Zammad GmbH``" +#: ../system/objects/types.rst:26 +msgid "*Single selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Domain based assignment" +#: ../system/objects/types.rst:27 +msgid "*Multiple selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.domain_assignment}``" +#: ../system/objects/types.rst:28 +msgid "*Single tree selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Domain" +#: ../system/objects/types.rst:29 +msgid "*Multiple tree selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.domain}``" +#: ../system/objects/types.rst:31 +msgid "" +"For these types, you can find an additional field *Translate field contents*:" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``zammad.com`` or empty if not set" +#: ../system/objects/types.rst:0 +msgid "Screenshot showing translatable attribute types" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > VIP" +#: ../system/objects/types.rst:38 +msgid "Screenshot with example of translatable attribute type" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.vip}``" +#: ../system/objects/types.rst:45 +msgid "Boolean field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Note" +#: ../system/objects/types.rst:41 +msgid "" +"Provides a drop-down field with display values for ``true`` and ``false``. " +"Setting a default is mandatory." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.note}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Boolean fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Mobile" +#: ../system/objects/types.rst:55 +msgid "Date field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.mobile}``" +#: ../system/objects/types.rst:48 +msgid "Provides a date picker field and does not allow default values." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Login" +#: ../system/objects/types.rst:52 +msgid "Default time diff (hours)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.login}``" +#: ../system/objects/types.rst:51 +msgid "" +"This setting helps the user by highlighting the day from now plus the " +"provided value. It *does not* pre-fill the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Lastname" +#: ../system/objects/types.rst:0 +msgid "Available settings for Date fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.lastname}``" +#: ../system/objects/types.rst:73 +msgid "Date & time field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Firstname" +#: ../system/objects/types.rst:58 +msgid "Provides a date and time picker – does not allow default values" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.firstname}``" +#: ../system/objects/types.rst:62 +msgid "Allow future" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Fax" +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the future." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.fax}``" +#: ../system/objects/types.rst:66 +msgid "Allow past" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Email" +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the past." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.email}``" +#: ../system/objects/types.rst:70 +msgid "Default time diff (minutes)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Department" +#: ../system/objects/types.rst:69 +msgid "" +"This setting helps the user by highlighting the day from now plus the " +"provided value. It does not pre-fill the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.department}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Date & time fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Web" +#: ../system/objects/types.rst:86 +msgid "Integer field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.web}``" +#: ../system/objects/types.rst:76 +msgid "" +"Provides an input field that allows integer usage only. You may define a " +"default value. You cannot enforce comma separation." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > VIP" +#: ../system/objects/types.rst:80 +msgid "Minimal" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.vip}``" +#: ../system/objects/types.rst:80 +msgid "The minimal value the field accepts." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Phone" +#: ../system/objects/types.rst:83 +msgid "Maximal" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.phone}``" +#: ../system/objects/types.rst:83 +msgid "The maximum value the field accepts." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Note" +#: ../system/objects/types.rst:0 +msgid "Available settings for Integer fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.note}``" +#: ../system/objects/types.rst:99 +msgid "Multiple selection field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Mobile" +#: ../system/objects/types.rst:89 +msgid "" +"Provides a selection field that allows the selection of one or more out of " +"several. This field does allow setting a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.mobile}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Multiple selection fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Login" +#: ../system/objects/types.rst:112 +msgid "Single selection field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.login}``" +#: ../system/objects/types.rst:102 +msgid "" +"Provides a drop-down field that allows selection of one value out of " +"several. This field does allow setting a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Lastname" +#: ../system/objects/types.rst:0 +msgid "Available settings for Single selection fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.lastname}``" +#: ../system/objects/types.rst:142 +msgid "Textarea field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Firstname" +#: ../system/objects/types.rst:115 +msgid "" +"Provides a text area input field (multiple lines) and thus allows e.g. new " +"lines. You can set a default field value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.firstname}``" +#: ../system/objects/types.rst:120 +msgid "" +"Please note that this field *does not* support text formatting or HTML " +"content (rich text)." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Fax" +#: ../system/objects/types.rst:123 +msgid "**🥵 This field can consume a lot of visual space**" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.fax}``" +#: ../system/objects/types.rst:125 +msgid "" +"Depending on where you use this field type, it may use a lot of visual space " +"if you provide a lot of text. This may be an issue to work with." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Email" +#: ../system/objects/types.rst:130 +msgid "Default" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.email}``" +#: ../system/objects/types.rst:129 +msgid "" +"The here provided text will be shown within the text area field or new data " +"sets." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Department" +#: ../system/objects/types.rst:134 ../system/objects/types.rst:160 +msgid "Maxlength" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.department}``" +#: ../system/objects/types.rst:0 ../system/objects/types.rst:160 +msgid "You can pick the maximum length of the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Avatar" +#: ../system/objects/types.rst:0 +msgid "The default length of this object is ``500``." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.avatar(60,60)}``" +#: ../system/objects/types.rst:139 +msgid "Rows" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Address" +#: ../system/objects/types.rst:0 +msgid "" +"Change the number of rows to dislay so that you can use only the space you " +"really need." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.address}``" +#: ../system/objects/types.rst:0 +msgid "The default number of rows is ``4``." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created at" +#: ../system/objects/types.rst:0 +msgid "Available settings for Textarea fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_at}``" +#: ../system/objects/types.rst:165 +msgid "Text field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Avatar" +#: ../system/objects/types.rst:145 +msgid "Provides a text field (one line) and allows choosing a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.avatar(60,60)}``" +#: ../system/objects/types.rst:148 +msgid "" +"Defines the type of the input field. This allows e.g. your browser to ensure " +"that you provide the specific type." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Address" +#: ../system/objects/types.rst:152 +msgid "Currently available:" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.address}``" +#: ../system/objects/types.rst:155 +msgid "Phone" msgstr "" -#: ../system/variables/ticket.rst:6 -msgid "" -"Below you can find all available ticket-based variables within Zammad. These " -"can be called via Triggers for example. If you're unsure if Zammad does " -"support variables at the point you're at, you can try to type ``::`` to " -"check." +#: ../system/objects/types.rst:156 +msgid "Text" msgstr "" -#: ../system/variables/ticket.rst:12 -msgid "Ticket Variables" +#: ../system/objects/types.rst:157 +msgid "Url *(URL fields disable link-template availability)*" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Web" +#: ../system/objects/types.rst:0 +msgid "Available settings for Text fields" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.web}``" +#: ../system/objects/types.rst:174 +msgid "Single tree selection field" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > VIP" +#: ../system/objects/types.rst:168 +msgid "" +"Provides a select-like field with up to 6 layers of options. Does not allow " +"setting a default value." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.vip}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Tree Select fields" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Phone" +#: ../system/objects/types.rst:183 +msgid "Multiple tree selection field" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.phone}``" +#: ../system/objects/types.rst:177 +msgid "" +"Provides a select-like field with up to 6 layers of options allowing the " +"selection of multiple values. Does not allow setting a default value." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Note" +#: ../system/objects/types.rst:302 +msgid "External Data Source field" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.note}``" +#: ../system/objects/types.rst:186 +msgid "" +"Provides a searchable field which fetches data from an external system. This " +"can be useful if you have data outside of Zammad and don't want to maintain " +"both data sources." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Mobile" +#: ../system/objects/types.rst:190 +msgid "The feature works as follows:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.mobile}``" +#: ../system/objects/types.rst:192 +msgid "" +"Zammad sends a query with a search string (free text from agent or based on " +"a variable) in a pre-defined format (\"Search URL\") to an external system." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Login" +#: ../system/objects/types.rst:195 +msgid "" +"This external system searches for matches and provides a response as a JSON " +"structure to Zammad." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.login}``" +#: ../system/objects/types.rst:197 +msgid "" +"Zammad just looks for the defined list and value keys, reads the content and " +"displays the value to the user. There is no search on Zammad side." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Lastname" +#: ../system/objects/types.rst:201 +msgid "" +"The usage of a PostgreSQL database for Zammad is required. In any other " +"case, Zammad will hide the external data source type and you are not able to " +"use it. If you want to use this feature, consider to :docs:`migrate your " +"database `." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.lastname}``" +#: ../system/objects/types.rst:205 +msgid "Currently, only ``GET`` is supported as request method." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Firstname" +#: ../system/objects/types.rst:206 +msgid "" +"The data structure must be in JSON format and provide the objects in an " +"array." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.firstname}``" +#: ../system/objects/types.rst:208 +msgid "" +"The endpoint for the external data source has to support search. On Zammad " +"side, there is no search/logic implemented; however, you can define the " +"output key and value based on the result(s) from the response (which " +"provides already filtered content based on the search)." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Fax" +#: ../system/objects/types.rst:212 +msgid "" +"If you receive more results as expected, your external data source search " +"may not work properly or the structure of the URL is not correct. You should " +"get in touch with a responsible person from the external system." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.fax}``" +#: ../system/objects/types.rst:217 +msgid "" +"Please have a look :doc:`at our example `, where you can find a possible configuration for a public " +"dummy endpoint." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Email" +#: ../system/objects/types.rst:0 +msgid "Available settings for external data source fields" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.email}``" +#: ../system/objects/types.rst:242 +msgid "Search URL" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Department" +#: ../system/objects/types.rst:227 +msgid "" +"Set your endpoint where Zammad fetches the data. Please make sure to include " +"a valid search :doc:`variable ` as an URL parameter. " +"Example for a free text search at user input: ``#{search.term}``" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.department}``" +#: ../system/objects/types.rst:232 +msgid "" +"If in doubt, ask the responsible person for the external data source how " +"they expect the structure of the URL." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Avatar" +#: ../system/objects/types.rst:236 +msgid "" +"Depending on your search variable, the preview might work or not. The reason " +"is that the context might not be available and it is no bug." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.avatar(60,60)}``" +#: ../system/objects/types.rst:239 +msgid "" +"Please also make sure to use a variable which is available in your object " +"context. For example you won't be able to search for a ticket in a user " +"object context." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Address" +#: ../system/objects/types.rst:252 +msgid "SSL Verification" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.address}``" +#: ../system/objects/types.rst:245 +msgid "Here you can switch the SSL verification to no." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated at" +#: ../system/objects/types.rst:249 +msgid "" +"If your external data source system is using self signed certificates, " +"please have a look :doc:`here ` for " +"further information about how to handle them in Zammad, so you can keep the " +"SSL verification activated." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_at}``" +#: ../system/objects/types.rst:258 +msgid "HTTP Authentication" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Title" +#: ../system/objects/types.rst:255 +msgid "" +"If your external data source requires an authentication, you can set it " +"here. You can leave it empty or choose between *Basic Authentication* or " +"*Authentication Token* (selecting one of the two methods leads to additional " +"fields where you can enter your credentials/token)." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.title}``" +#: ../system/objects/types.rst:265 +msgid "Search result list key" msgstr "" -#: ../system/variables/ticket.rst:1 +#: ../system/objects/types.rst:261 msgid "" -"``My amazing Subject`` (normally subject, can be edited within Interface and " -"thus differ)" +"Defines the level in the JSON structure which provides the list with search " +"results. You can leave it empty, if the data is already provided as an " +"array. If you have to go deeper in the structure, you can provide a path " +"with ``.`` as separators, e.g. ``key.subkey.sub-sub-key``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Accounted Time" +#: ../system/objects/types.rst:271 +msgid "Search result value key" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.time_unit}``" +#: ../system/objects/types.rst:268 +msgid "" +"Defines the attribute in the structure in which your external data source " +"provides the *value* for your data. An example would be a product *number*. " +"If you have to go deeper in the structure, you can provide a path with ``.`` " +"as separators, e.g. ``key.subkey.sub-sub-key``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``1``, ``2.75`` or empty response" +#: ../system/objects/types.rst:277 +msgid "Search result label key" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Tags" +#: ../system/objects/types.rst:274 +msgid "" +"Defines the attribute in the structure in which your external data source " +"provides the *label* for your data. An example would be a product *name*. If " +"you have to go deeper in the structure, you can provide a path with ``.`` as " +"separators, e.g. ``key.subkey.sub-sub-key``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.tags}``" +#: ../system/objects/types.rst:280 +msgid "" +"In the preview area, you can find the following items (depending on your " +"configuration above):" msgstr "" -#: ../system/variables/ticket.rst:1 +#: ../system/objects/types.rst:283 msgid "" -"Currently not available, see `Issue 2769 `_" +"**Error/hint message** (only if configuration is not complete): Zammad tells " +"you, if there is a problem and what you should change in your configuration." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > State > Name" +#: ../system/objects/types.rst:286 +msgid "" +"**Search field**: search for an existing attribute in the data source to get " +"a preview. This is required for the fields below to show up." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.state.name}``" +#: ../system/objects/types.rst:288 +msgid "" +"**Search result response** (only if configuration is not complete): here you " +"can find a syntax highlighted JSON preview of the response, based on the " +"search term you entered." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``new``, ``open``, ..." +#: ../system/objects/types.rst:291 +msgid "" +"**Search result list** (only if *search result list key* is properly set): " +"output of the structure under the configured *search result list key*." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Priority > Name" +#: ../system/objects/types.rst:294 +msgid "" +"**Preview table** (when fully configured): Zammad shows you a table which " +"includes the found items based on the search string (value, label and " +"optional link). You can use this preview if you don't have the complete data " +"structure of the external system in mind." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.priority.name}``" +#: ../system/objects/types.rst:299 +msgid "" +"An example of a configured external data source field from agent perspective:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2 normal``" +#: ../system/objects/types.rst:0 +msgid "Screencast showing the search for a product in a ticket" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Pending till" +#: ../system/objects/types.rst:307 +msgid "URL fields (Link-Template)" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.pending_time}``" +#: ../system/objects/types.rst:311 +msgid "" +"This function is restricted to Text, Select and External data source types " +"only." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not set" +#: ../system/objects/types.rst:314 +msgid "" +"Link-Templates are an amazing way to dynamically generate URLs. They allow " +"you to integrate other systems better without having to manually copy data " +"from Zammad if possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Web" +#: ../system/objects/types.rst:320 +msgid "" +"Another great way of communicating with another system may be Zammad's :doc:" +"`Webhooks `." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.web}``" +#: ../system/objects/types.rst:323 +msgid "" +"After filling a link-template enabled field, an URL icon will appear on its " +"right. Clicking on the icon opens a new tab." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``https://zammad.com`` or empty if not set" +#: ../system/objects/types.rst:328 +msgid "" +"Even though Zammad displays the link template within object edit and create " +"screens, the function is optional. It's only active if you populate the " +"field." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > VIP" +#: ../system/objects/types.rst:333 +msgid "" +"What's the difference between URL and text fields with link template...?!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.vip}``" +#: ../system/objects/types.rst:335 +msgid "" +"Both fields have different use cases. Use ``text`` type text fields when " +"ever you have a *static* url that requires dynamic parameters. If you " +"require a drag & drop like field that you can put in any URL, use ``URL`` " +"type text fields." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Phone" +#: ../system/objects/types.rst:340 +msgid "" +"The difference is easier to spot when comparing the fields directly, below " +"screencast shows the result - the dynamic approach uses existing values in " +"the moment of updating to built the URL - e.g. ``https://google.com/search?" +"q=cookies`` - while the URL approach uses the actual URL of the field - e.g. " +"``https://zammad.com``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.phone}``" +#: ../system/objects/types.rst:None +msgid "" +"Screencast showing the differents in between URL and text type fields with " +"actual values" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Note" +#: ../system/objects/types.rst:352 +msgid "How does this work...?!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.note}``" +#: ../system/objects/types.rst:354 +msgid "" +"As an example, let's say you have an attribute called ``amazing_attribute`` " +"and you want to open a google search directly with the input from that field." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Mobile" +#: ../system/objects/types.rst:357 +msgid "" +"Providing the link-template field below allows you to do so: ``https://www." +"google.com/search?q=#{ticket.amazing_attribute}``" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.mobile}``" +#: ../system/objects/types.rst:362 +msgid "" +"You can use any :doc:`Zammad variable ` as long as it's " +"available in the moment you need it." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Login" +#: ../system/objects/types.rst:365 +msgid "" +"As a result, you are redirected to Google with a search for the value of the " +"attribute, if you click on the button in the ticket (as you can see in the " +"screencast above)." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.login}``" +#: ../system/packages.rst:2 +msgid "Packages" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``agent``" +#: ../system/packages.rst:4 +msgid "That's the package management-area." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Lastname" +#: ../system/packages.rst:6 +msgid "Individual add-ons for Zammad can be installed and managed here." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.lastname}``" +#: ../system/sessions.rst:2 +msgid "Sessions" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Mustermann`` or empty if not set" +#: ../system/sessions.rst:4 +msgid "" +"Sessions management allows reviewing currently known user sessions and " +"allows to end these. The session timeout is affected by :ref:" +"`security_session_timeout` configurations from security settings." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Firstname" +#: ../system/sessions.rst:None +msgid "Screenshot showing Zammad's session management" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.firstname}``" +#: ../system/sessions.rst:13 +msgid "Zammad will provide the following information:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Max`` or empty if not set" +#: ../system/sessions.rst:16 +msgid "" +"The user account this session entry belongs to. It can be normal if a user " +"has several sessions in the list. This can be due to changed browser " +"information or if you use e.g. single sign on methods where the user does " +"not use the log off button." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Fax" +#: ../system/sessions.rst:22 +msgid "Browser" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.fax}``" +#: ../system/sessions.rst:22 +msgid "The browser agent communicated to Zammad." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Email" +#: ../system/sessions.rst:40 +msgid "Location" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.email}``" +#: ../system/sessions.rst:25 +msgid "" +"The anticipated location based on the users IP address. Depending on the IP " +"address the result shown may differ. This option depends on :doc:`/settings/" +"system/services`." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``agent@company.tld`` or empty if not set" +#: ../system/sessions.rst:29 +msgid "The following information can be shown:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Department" +#: ../system/sessions.rst:33 +msgid "IP address" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.department}``" +#: ../system/sessions.rst:32 +msgid "" +"Either if you set *Geo IP services* to inactive or you're using internal IP " +"address which do not provide location information." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Support`` or empty if not set" +#: ../system/sessions.rst:40 +msgid "Country (or Country + City)" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Avatar" +#: ../system/sessions.rst:36 +msgid "" +"If *Geo IP services* is enabled only. Depends on how detailed the available " +"IP address information are." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.avatar(60,60)}``" +#: ../system/sessions.rst:39 +msgid "" +"Be aware that results can be inaccurate - this technically is not an error." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Address" +#: ../system/sessions.rst:43 +msgid "Age" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.address}``" +#: ../system/sessions.rst:43 +msgid "Provides the time when the session initially has been created." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Shared organization" +#: ../system/sessions.rst:50 +msgid "Update" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.shared}``" +#: ../system/sessions.rst:46 +msgid "" +"Provides the time the user used this session to open Zammad. This timestamp " +"is only updated if the user e.g. reloads, not during normal work on tickets." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Note" +#: ../system/sessions.rst:50 +msgid "This timestamp is being used for the session timeout." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.note}``" +#: ../system/sessions.rst:53 +msgid "" +"Use the delete button to remove a single session on behalf of your user." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Name" +#: ../system/subscription.rst:2 +msgid "Subscription (SaaS)" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.name}``" +#: ../system/subscription.rst:4 +msgid "" +"The subscription settings page allows you to configure your instances " +"package and number of agents required." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Zammad GmbH`` or empty if not set" +#: ../system/subscription.rst:9 +msgid "" +"This setting section is only available for Hosted setups. If you're looking " +"for on premise support contracts, please see the `Zammad pricing page " +"`_." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Domain based assignment" +#: ../system/subscription.rst:14 ../system/subscription.rst:34 +msgid "Plan" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.domain_assignment}``" +#: ../system/subscription.rst:16 +msgid "" +"Here you can set up everything affecting your instance subscription " +"functions like number of agents and package." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Domain" +#: ../system/subscription.rst:19 +msgid "" +"On top of the page you can find a subscription summary. You'll find the " +"number of used and available (booked) agent seats there. By using the *see " +"more* link you can also expand an agent list to see the currently configured " +"active agents. This list *does not* count accounts with admin permissions " +"only." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.domain}``" +#: ../system/subscription.rst:None +msgid "" +"Within subscription you can always see how many agents are still\n" +"available to add and who uses the seats." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``domain.tld`` or empty if not set" +#: ../system/subscription.rst:29 +msgid "" +"Learn more on how to manage your agents in general :doc:`here `." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > VIP" +#: ../system/subscription.rst:36 +msgid "" +"This section gives you an overview of the available plans and their " +"functions / limits. If you require a more detailed table, check our " +"`detailed pricing table `_ for more." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.vip}``" +#: ../system/subscription.rst:40 +msgid "" +"Your selection in this step will decide on the base agent price and e.g. " +"agent limits that might apply in the summary step." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Number" +#: ../system/subscription.rst:43 +msgid "" +"The green *Selected* button will also tell you what plan you're currently in." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.number}``" +#: ../system/subscription.rst:47 +msgid "" +"Trial instances are running at Professional with 3 agents. The plan cannot " +"be changed during the trial for technical reasons, if you require more " +"agents for testing, please contact `our sales team `_ with a reason for the raise request." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``31001``, ``201910731001``, ..." +#: ../system/subscription.rst:None +msgid "" +"Screenshot showing three available packages for a hosted Zammad\n" +"instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > ID" +#: ../system/subscription.rst:57 +msgid "" +"At the bottom of this block you can find a summary where you can adjust the " +"settings of the previous selected plan." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.id}``" +#: ../system/subscription.rst:62 +msgid "" +"Note that upgrading (more agents, higher package) is always possible, " +"however, downgrading will only happen when your billing period renews." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``17``, ``5281``, ..." +#: ../system/subscription.rst:66 +msgid "" +"Upgrading resets your billing period and existing credit will be deducted " +"from the new total." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact (customer)" +#: ../system/subscription.rst:75 +msgid "Billing cycle" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_customer_at}``" +#: ../system/subscription.rst:70 +msgid "" +"You can choose between either monthly or yearly billing. The price per agent " +"will be cheaper if you decide for yearly billing." msgstr "" -#: ../system/variables/ticket.rst:1 +#: ../system/subscription.rst:73 msgid "" -"``2019-10-07 16:25:00 UTC`` or empty if not applicable yet (Please note " -"`Ticket last contact behavior Settings `_ for this)" +"If you're still trying out things and are unsure of the right package for " +"your instance, you may want to choose monthly first and then upgrade to " +"yearly when you're sure." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact" +#: ../system/subscription.rst:83 +msgid "Plan: (Starter|Professional|Plus) - Agents" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_at}``" +#: ../system/subscription.rst:78 +msgid "Choose the number of agents you require for your instance." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact (agent)" +#: ../system/subscription.rst:80 +msgid "" +"Keep in mind that some packages may have agent limits. Depending on the " +"previous chosen package, you won't be able to exceed specific agent numbers. " +"Also note that setting less agents than currently configured is not possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_agent_at}``" +#: ../system/subscription.rst:86 +msgid "Total" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable yet" +#: ../system/subscription.rst:86 +msgid "This will be the net total you're going to be billed." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Note" +#: ../system/subscription.rst:88 +msgid "" +"By using the *Update subscription* button, the instance package will be " +"adjusted immediately. If you didn't provide a payment method yet, Zammad " +"will request you to provide one at this point." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.note}``" +#: ../system/subscription.rst:94 +msgid "" +"In case you're still within the trial period, this means that the trial will " +"be over immediately!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Note about this group``" +#: ../system/subscription.rst:97 +msgid "Down- or upgrading during the trial period *is not* possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Name" +#: ../system/subscription.rst:None +msgid "Screenshot showing payment options and a pricing summary" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.name}``" +#: ../system/subscription.rst:103 +msgid "Billing Information" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Sales``" +#: ../system/subscription.rst:105 +msgid "" +"You can control all billing relevant information like invoices, billing " +"address and the option to cancel your subscription." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Follow-up possible" +#: ../system/subscription.rst:108 +msgid "" +"All adjusted billing information below only affect future invoices. If your " +"invoice was issued wrong, please contact `our sales team `_." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.follow_up_possible}``" +#: ../system/subscription.rst:114 +msgid "Billing address" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``no`` or ``yes``" +#: ../system/subscription.rst:113 +msgid "" +"Provide your company address here, make sure to include the companies name " +"in case required. This address will be referenced on your invoice." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Assign Follow-Ups" +#: ../system/subscription.rst:118 +msgid "VAT ID" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.follow_up_assignment}``" +#: ../system/subscription.rst:117 +msgid "" +"Provide your VAT ID here. If applicable your invoice will not contain German " +"VAT. Please make sure to pay the VAT in your country as required." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Assignment Timeout" +#: ../system/subscription.rst:127 +msgid "Billing Email Address" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.assignment_timeout}``" +#: ../system/subscription.rst:121 +msgid "" +"Usually the instance owner (the person that registered the instance) will " +"receive all emails including the invoices. In case you have your own billing " +"department, you can provide their email address here." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``20`` or empty if not configured" +#: ../system/subscription.rst:125 +msgid "" +"All billing relevant information will then be sent to this email address." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > First response" +#: ../system/subscription.rst:127 +msgid "Invoices are sent as attachment (PDF) to this email address." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.first_response_at}``" +#: ../system/subscription.rst:129 +msgid "" +"Don't forget to press the *Update billing information* button after you " +"changed above settings." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Escalation at" +#: ../system/subscription.rst:None +msgid "" +"Screenshot showing options for billing information within the\n" +"subscription menu" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.escalation_at}``" +#: ../system/subscription.rst:137 +msgid "Payment Method" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable" +#: ../system/subscription.rst:139 +msgid "You can pay via credit card or SEPA mandate." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Web" +#: ../system/subscription.rst:144 +msgid "Credit card" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.web}``" +#: ../system/subscription.rst:142 +msgid "" +"Simply follow the dialogue by clicking *authorize credit card* and confirm -" +"if required by your bank- your consent to Zammad using your card for the " +"payments." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > VIP" +#: ../system/subscription.rst:148 +msgid "SEPA Direct Debit" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.vip}``" +#: ../system/subscription.rst:147 +msgid "" +"Provide the requested information of the bank account holder and update if " +"you're ready. You'll then receive an email with the SEPA mandate." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Phone" +#: ../system/subscription.rst:150 +msgid "" +"Technically there's also the possibility to pay via invoice, however - this " +"method only applies to a fairly low number of instances. Please contact `our " +"sales team `_ for more information." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.phone}``" +#: ../system/subscription.rst:156 +msgid "Cancel Subscription" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Note" +#: ../system/subscription.rst:158 +msgid "" +"Do you want to cancel your subscription? In case you no longer want to use " +"Zammad's SaaS, you can cancel your subscription by using the red *Yes, " +"please cancel my subscription* button." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.note}``" +#: ../system/subscription.rst:162 +msgid "" +"To cancel the description, enter the FQDN of your Zammad instance and " +"provide a reason for your cancellation." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Mobile" +#: ../system/subscription.rst:165 +msgid "" +"Your subscription will end the day after your trial or billing period ends." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.mobile}``" +#: ../system/subscription.rst:None +msgid "Screenshot showing subscription cancellation dialog" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Login" +#: ../system/subscription.rst:174 +msgid "" +"We will remind you about your cancelled subscription several times up front. " +"After the subscription ended all instance data will be removed. A restore " +"*is not* possible after that point!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.login}``" +#: ../system/subscription.rst:178 +msgid "**😖 Cancelled by accident?**" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Lastname" +#: ../system/subscription.rst:180 +msgid "" +"You can always undo the cancellation via the *Yes, undo the cancellation of " +"my subscription* button up to the last subscription day!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.lastname}``" +#: ../system/subscription.rst:0 +msgid "" +"Screenshot showing a red button to cancel the subscription\n" +"cancellation" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Firstname" +#: ../system/subscription.rst:189 +msgid "Payment History" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.firstname}``" +#: ../system/subscription.rst:191 +msgid "" +"The payment history will display a history of all paid invoices. At this " +"point you can also download these in case you need them again." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Fax" +#: ../system/subscription.rst:196 +msgid "" +"You will only find *paid* invoices here. Invoices that are to be billed are " +"not available before the payment is completed." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.fax}``" +#: ../system/subscription.rst:201 +msgid "Date" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Email" +#: ../system/subscription.rst:201 +msgid "Date of the invoice creation." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.email}``" +#: ../system/subscription.rst:204 +msgid "Amount" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Department" +#: ../system/subscription.rst:204 +msgid "Invoice total including VAT if applicable." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.department}``" +#: ../system/subscription.rst:207 +msgid "" +"Contains contract period (monthly or yearly) and hosted plan for the " +"subscription period in question." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Avatar" +#: ../system/subscription.rst:218 +msgid "Payment method / Service period" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.avatar(60,60)}``" +#: ../system/subscription.rst:211 +msgid "" +"Used bank account or credit card as well as the subscription period the " +"invoice is about." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Address" +#: ../system/subscription.rst:216 +msgid "" +"It might happen that the invoice date and subscription period differ. This " +"is nothing to worry about, the subscription periods will be accounted later " +"on." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.address}``" +#: ../system/subscription.rst:222 +msgid "Receipt" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Web" +#: ../system/subscription.rst:221 +msgid "" +"Use the arrow to download the invoice in question. You can download all " +"available invoices any time you need to here!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.web}``" +#: ../system/subscription.rst:None +msgid "Screenshot showing payment history of a hosted instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > VIP" +#: ../system/subscription.rst:229 +msgid "FAQ" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.vip}``" +#: ../system/subscription.rst:233 +msgid "I set up a trial account but am missing functions to test" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Phone" +#: ../system/subscription.rst:232 +msgid "" +"The trial instance is running within the professional package allowing up to " +"three agents." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.phone}``" +#: ../system/subscription.rst:236 +msgid "Can I change package within the trial?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Note" +#: ../system/subscription.rst:236 +msgid "No. As soon as the package is changed the subscription begins." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.note}``" +#: ../system/subscription.rst:241 +msgid "What happens to my trial instance after the trial period ended?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Mobile" +#: ../system/subscription.rst:239 +msgid "" +"Your instance will automatically be canceled for you. Please see *What " +"happens to my instance after it has been canceled?* for more." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.mobile}``" +#: ../system/subscription.rst:254 +msgid "What happens to my instance after it has been canceled?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Login" +#: ../system/subscription.rst:244 +msgid "That depends slightly on your instance state:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.login}``" +#: ../system/subscription.rst:250 +msgid "Trial instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Lastname" +#: ../system/subscription.rst:247 +msgid "" +"If you're still on trial, we will ice your instance and remind you once " +"again about your instance. We then will wait some days and remove your " +"instance from our system. This is the last time we will inform you by Email." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.lastname}``" +#: ../system/subscription.rst:254 +msgid "Paid instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Firstname" +#: ../system/subscription.rst:253 +msgid "" +"If you're a paying customer and canceled your subscription, the instance " +"removal will take place the day after your last subscription day." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.firstname}``" +#: ../system/subscription.rst:256 +msgid "Can removed instances be restored?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Fax" +#: ../system/subscription.rst:257 +msgid "No. Once your instance has been removed, a restoration is not possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.fax}``" +#: ../system/system-report.rst:2 +msgid "System Report" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Email" +#: ../system/system-report.rst:4 +msgid "" +"In this place you can't configure Zammad. Instead you can obtain a system " +"report about Zammad and its configuration." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.email}``" +#: ../system/system-report.rst:7 +msgid "" +"See the description in Zammad for an explanation. You can even find a " +"preview of the included data below the **Download** button." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Department" +#: ../system/system-report.rst:10 +msgid "" +"Zammad never sends this automatically to anyone. It is a manual process only " +"to provide better support based on your configuration." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.department}``" +#: ../system/translations.rst:2 +msgid "Translations" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Avatar" +#: ../system/translations.rst:4 +msgid "" +"Translations of Zammad are processed centrally in our `Weblate instance " +"`_. This allows non-developers to review " +"and update translation texts of the language they actually speak." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.avatar(60,60)}``" +#: ../system/translations.rst:9 +msgid "" +"Your language is in an incomplete translation state or has typos? Please " +"consider helping us in sorting this out! All you need is either a GitHub " +"account or to register directly in our instance." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Address" +#: ../system/translations.rst:13 +msgid "" +"Did you know? This is also where the documentation translations are handled. " +"🤓" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.address}``" +#: ../system/translations.rst:15 +msgid "" +"Have a look in our :docs:`contribution section ` in the system documentation to get started!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created at" +#: ../system/translations.rst:20 +msgid "Local Translations" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_at}``" +#: ../system/translations.rst:22 +msgid "" +"Apart from these system translations, there's still local translations you " +"can manage. This is relevant if you added custom objects that require " +"translations or even custom states and priorities." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "2019-10-07 16:25:00 UTC" +#: ../system/translations.rst:None +msgid "Translation management screen within the admin menu" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Closing time" +#: ../system/translations.rst:31 +msgid "Updating Translations" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.close_at}``" +#: ../system/translations.rst:33 +msgid "" +"Because of how Zammad ships translations, the only way to update the system " +"translations is to update your Zammad installation. The benefit of this is " +"that you no longer need internet access during a Zammad upgrade as the " +"package has everything it requires already." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "2019-10-07 17:25:00 UTC" +#: ../system/translations.rst:39 +msgid "Translation of Custom Objects" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``3``, any number of articles existing in the ticket right now" +#: ../system/translations.rst:41 +msgid "" +"No problem at all! You can customize any translation locally, even if it is " +"not initially provided by the system." msgstr "" -#: ../system/version.rst:2 -msgid "Version" +#: ../system/translations.rst:44 +msgid "" +"Translation is supported for a broad number of features, including but not " +"limited to custom:" msgstr "" -#: ../system/version.rst:4 -msgid "Shows which version is currently being used on your Zammad-instance." +#: ../system/translations.rst:47 +msgid "Object Attributes" msgstr "" -#: ../manage/roles/admin-permissions.rst:53 -msgid "``admin.checklist``" -msgstr "" +#: ../system/translations.rst:48 +#, fuzzy +msgid "Ticket Macros" +msgstr "Macros" -#: ../manage/roles/admin-permissions.rst:54 -msgid ":doc:`Manage > Checklist `" +#: ../system/translations.rst:49 +msgid "Ticket Overviews" msgstr "" -#: ../manage/roles/admin-permissions.rst:83 -msgid "``admin.channel_whatsapp``" +#: ../system/translations.rst:50 +msgid "Ticket Priorities" msgstr "" -#: ../manage/roles/admin-permissions.rst:84 -msgid ":doc:`Channels > Whatsapp `" +#: ../system/translations.rst:51 +msgid "Ticket States" msgstr "" -#: ../manage/roles/admin-permissions.rst:124 -msgid "``admin.public_links``" +#: ../system/translations.rst:54 +msgid "Customizing Translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:125 -msgid ":doc:`Manage > Public Links `" +#: ../system/translations.rst:56 +msgid "" +"Within the translation screen, simply click on the **New Translation** " +"button." msgstr "" -#: ../manage/roles/admin-permissions.rst:151 -msgid "``admin.system_report``" +#: ../system/translations.rst:None +msgid "New translation dialog" msgstr "" -#: ../manage/roles/admin-permissions.rst:152 -msgid ":doc:`System > System Report `" +#: ../system/translations.rst:62 +msgid "" +"In the dialog you can immediately enter the exact translation source (if you " +"know it) and your custom translation text for it and click **Submit**." msgstr "" -#: ../manage/roles/admin-permissions.rst:166 -msgid "``admin.ticket_auto_assignment``" +#: ../system/translations.rst:65 +msgid "" +"Alternatively, try to search for translation suggestions in the list below. " +"Selecting an item from the list will pre-fill the translation source for you " +"and then you can just enter your custom translation." msgstr "" -#: ../manage/roles/admin-permissions.rst:167 -msgid ":ref:`Settings > Ticket > Auto Assignment `" +#: ../system/translations.rst:69 +msgid "" +"The target language will always default to your current language selection. " +"If you need to translate for a different language, simply change the " +"selection before submitting." msgstr "" -#: ../manage/roles/admin-permissions.rst:169 -msgid "``admin.ticket_duplicate_detection``" +#: ../system/translations.rst:73 +msgid "" +"All your custom translations will show up in the overview table when added. " +"And they will even persist across Zammad updates!" msgstr "" -#: ../manage/roles/admin-permissions.rst:170 -msgid ":ref:`Settings > Ticket > Duplicate Detection `" +#: ../system/translations.rst:76 +msgid "" +"Make sure to reload your browser if a translated string is not displayed." msgstr "" -#: ../manage/roles/admin-permissions.rst:172 -msgid "``admin.ticket_priority``" +#: ../system/translations.rst:80 +msgid "Reverting to Original Translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:173 -msgid ":ref:`System > Objects >Ticket Priority `" +#: ../system/translations.rst:82 +msgid "" +"If you want to revert a custom translation to original text, simply use the " +"appropriate action within the row of the overview table." msgstr "" -#: ../manage/roles/admin-permissions.rst:175 -msgid "``admin.ticket_state``" +#: ../system/translations.rst:85 +msgid "" +"Depending on the type of the translation source, the action has a slightly " +"different name:" msgstr "" -#: ../manage/roles/admin-permissions.rst:176 -msgid ":ref:`System > Objects >Ticket State `" +#: ../system/translations.rst:88 +msgid "**Reset** for customized system translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:193 -msgid "``admin.webhook``" +#: ../system/translations.rst:89 +msgid "**Remove** for customized local translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:194 -msgid ":doc:`Manage > Webhook `" +#: ../system/translations.rst:91 +msgid "" +"In both cases, the action will remove the customized translation after a " +"confirmation." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:43 -msgid "``user_preferences.appearance``" +#: ../system/translations.rst:None +msgid "Screenshot showing the location of the Remove action" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:44 -msgid "Appearance configuration" +#: ../system/translations.rst:99 +msgid "Inline Translations" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:0 -msgid "Users can switch between dark, light and" +#: ../system/translations.rst:101 +msgid "" +"If you prefer a more hands-on approach, you can activate the inline or on-" +"screen translation feature by pressing ``ctrl`` + ``alt`` + ``t`` at any " +"time and on any screen." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:0 -msgid "automatic mode." +#: ../system/translations.rst:105 +msgid "" +"All customizable translation texts will be highlighted for you on the " +"screen. Just click into the highlighted area and update the text in place." msgstr "" -#: ../system/system-report.rst:2 -msgid "System Report" +#: ../system/translations.rst:None +msgid "Inline translation mode activated for the Overview screen" msgstr "" -#: ../system/system-report.rst:4 +#: ../system/translations.rst:112 msgid "" -"In this place you can't configure Zammad. Instead you can obtain a system " -"report about Zammad and its configuration." +"When finished editing, simply press ``ctrl`` + ``alt`` + ``t`` again to " +"deactivate." msgstr "" -#: ../system/system-report.rst:7 +#: ../system/translations.rst:117 msgid "" -"See the description in Zammad for an explanation. You can even find a " -"preview of the included data below the **Download** button." +"Even though it's available on any screen, the inline translation feature " +"requires admin permissions. It works only for the current language " +"selection. If you need to translate a different language, first change the " +"language in your :user-docs:`profile settings `." msgstr "" -#: ../system/system-report.rst:10 -msgid "" -"Zammad never sends this automatically to anyone. It is a manual process only " -"to provide better support based on your configuration." +#: ../system/version.rst:2 +msgid "Version" +msgstr "" + +#: ../system/version.rst:4 +msgid "Shows which version is currently being used on your Zammad-instance." msgstr "" #, fuzzy diff --git a/locale/nl/LC_MESSAGES/admin-docs.po b/locale/nl/LC_MESSAGES/admin-docs.po index b13b07bb..a7ab6bd0 100644 --- a/locale/nl/LC_MESSAGES/admin-docs.po +++ b/locale/nl/LC_MESSAGES/admin-docs.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Zammad\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-11-06 10:31+0100\n" +"POT-Creation-Date: 2024-11-12 16:31+0100\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -1040,12 +1040,12 @@ msgstr "" #: ../manage/roles/agent-permissions.rst:31 #: ../manage/roles/user-preferences-permissions.rst:37 #: ../manage/scheduler.rst:108 ../manage/webhook/add.rst:116 +#: ../misc/variables.rst:101 #: ../system/integrations/cti/includes/inbound-calls.include.rst:15 #: ../system/integrations/cti/includes/outbound-calls.include.rst:18 #: ../system/integrations/cti/includes/inbound-calls.include.rst:14 #: ../system/integrations/cti/includes/outbound-calls.include.rst:17 -#: ../system/objects.rst:162 ../system/objects.rst:244 -#: ../system/variables.rst:101 ../system/objects.rst:246 +#: ../system/objects.rst:162 ../system/objects.rst:246 msgid "Note" msgstr "" @@ -2257,7 +2257,7 @@ msgstr "" #: ../channels/email/signatures.rst:22 msgid "" "To individualize the signatures, it is possible to automatically load " -"specific information into a signature via :doc:`/system/variables`. All " +"specific information into a signature via :doc:`/misc/variables`. All " "information stored on the ticket, assigned customers or agents can be " "inserted. This makes it possible to design the signature individually. To " "load a list of available variables, enter two colons (``::``) into the " @@ -2550,7 +2550,7 @@ msgstr "" #: ../channels/form.rst:19 ../manage/groups/settings.rst:14 #: ../manage/scheduler.rst:39 ../manage/slas/how-do-they-work.rst:26 #: ../manage/templates.rst:33 ../system/objects.rst:130 -#: ../system/objects.rst:232 ../system/objects.rst:234 +#: ../system/objects.rst:234 msgid "Name" msgstr "" @@ -2579,7 +2579,7 @@ msgstr "" #: ../manage/macros/how-do-they-work.rst:0 ../manage/overviews.rst:0 #: ../manage/scheduler.rst:111 ../manage/templates.rst:43 #: ../manage/webhook/add.rst:123 ../system/objects.rst:169 -#: ../system/objects.rst:246 ../system/objects.rst:248 +#: ../system/objects.rst:248 msgid "Active" msgstr "" @@ -2921,10 +2921,9 @@ msgid "Default value" msgstr "" #: ../channels/form.rst:219 ../manage/public-links.rst:47 -#: ../misc/object-conditions/basics.rst:64 +#: ../misc/object-conditions/basics.rst:64 ../misc/variables.rst:100 #: ../system/core-workflows/condition-operators.rst:21 -#: ../system/objects/permissions.rst:39 ../system/subscription/billing.rst:53 -#: ../system/variables.rst:100 +#: ../system/objects/permissions.rst:39 ../system/subscription.rst:208 msgid "Description" msgstr "" @@ -5908,7 +5907,7 @@ msgstr "" msgid "System" msgstr "" -#: ../index.rst:87 ../index.rst:88 +#: ../index.rst:87 msgid "Misc" msgstr "" @@ -7142,7 +7141,7 @@ msgstr "" #: ../manage/macros/how-do-they-work.rst:28 msgid "" "Unlike triggers, the scheduler, and text modules, macro actions do **not** " -"support the use of :doc:`/system/variables`." +"support the use of :doc:`/misc/variables`." msgstr "" #: ../manage/macros/how-do-they-work.rst:32 @@ -8370,165 +8369,149 @@ msgid "Accessing chat for agents: ``chat.agent``" msgstr "" #: ../manage/roles/admin-permissions.rst:53 +msgid "``admin.checklist``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:54 +msgid ":doc:`Manage > Checklist `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:56 msgid "``admin.channel_email``" msgstr "" -#: ../manage/roles/admin-permissions.rst:54 #: ../manage/roles/admin-permissions.rst:57 msgid ":doc:`Channels > Email `" msgstr "" -#: ../manage/roles/admin-permissions.rst:56 #: ../manage/roles/admin-permissions.rst:59 msgid "``admin.channel_facebook``" msgstr "" -#: ../manage/roles/admin-permissions.rst:57 #: ../manage/roles/admin-permissions.rst:60 msgid ":doc:`Channels > Facebook `" msgstr "" -#: ../manage/roles/admin-permissions.rst:58 #: ../manage/roles/admin-permissions.rst:61 msgid "" "Accessing Facebook tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:59 #: ../manage/roles/admin-permissions.rst:62 msgid "``admin.channel_formular``" msgstr "" -#: ../manage/roles/admin-permissions.rst:60 #: ../manage/roles/admin-permissions.rst:63 msgid ":doc:`Channels > Form `" msgstr "" -#: ../manage/roles/admin-permissions.rst:62 #: ../manage/roles/admin-permissions.rst:65 msgid "``admin.channel_google``" msgstr "" -#: ../manage/roles/admin-permissions.rst:63 #: ../manage/roles/admin-permissions.rst:66 msgid ":doc:`Channels > Google `" msgstr "" -#: ../manage/roles/admin-permissions.rst:65 #: ../manage/roles/admin-permissions.rst:68 msgid "``admin.channel_microsoft365``" msgstr "" -#: ../manage/roles/admin-permissions.rst:66 #: ../manage/roles/admin-permissions.rst:69 msgid ":doc:`Channels > Microsoft 365 `" msgstr "" -#: ../manage/roles/admin-permissions.rst:68 #: ../manage/roles/admin-permissions.rst:71 msgid "``admin.channel_sms``" msgstr "" -#: ../manage/roles/admin-permissions.rst:69 #: ../manage/roles/admin-permissions.rst:72 msgid ":doc:`Channels > SMS `" msgstr "" -#: ../manage/roles/admin-permissions.rst:71 #: ../manage/roles/admin-permissions.rst:74 msgid "``admin.channel_telegram``" msgstr "" -#: ../manage/roles/admin-permissions.rst:72 #: ../manage/roles/admin-permissions.rst:75 msgid ":doc:`Channels > Telegram `" msgstr "" -#: ../manage/roles/admin-permissions.rst:73 #: ../manage/roles/admin-permissions.rst:76 msgid "" "Accessing Telegram tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:74 #: ../manage/roles/admin-permissions.rst:77 msgid "``admin.channel_twitter``" msgstr "" -#: ../manage/roles/admin-permissions.rst:75 #: ../manage/roles/admin-permissions.rst:78 msgid ":doc:`Channels > Twitter `" msgstr "" -#: ../manage/roles/admin-permissions.rst:76 #: ../manage/roles/admin-permissions.rst:79 msgid "" "Accessing Twitter/X tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:77 #: ../manage/roles/admin-permissions.rst:80 msgid "``admin.channel_web``" msgstr "" -#: ../manage/roles/admin-permissions.rst:78 #: ../manage/roles/admin-permissions.rst:81 msgid ":doc:`Channels > Web `" msgstr "" -#: ../manage/roles/admin-permissions.rst:80 +#: ../manage/roles/admin-permissions.rst:83 +msgid "``admin.channel_whatsapp``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:84 +msgid ":doc:`Channels > Whatsapp `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:86 msgid "``admin.core_workflows``" msgstr "" -#: ../manage/roles/admin-permissions.rst:81 #: ../manage/roles/admin-permissions.rst:87 msgid ":doc:`System > Core Workflows `" msgstr "" -#: ../manage/roles/admin-permissions.rst:83 #: ../manage/roles/admin-permissions.rst:89 msgid "``admin.data_privacy``" msgstr "" -#: ../manage/roles/admin-permissions.rst:84 #: ../manage/roles/admin-permissions.rst:90 msgid ":doc:`System > Data Privacy `" msgstr "" -#: ../manage/roles/admin-permissions.rst:85 #: ../manage/roles/admin-permissions.rst:91 msgid "" "🔥 Be careful, it allows users to permanently delete data on the system." msgstr "" -#: ../manage/roles/admin-permissions.rst:86 #: ../manage/roles/admin-permissions.rst:92 msgid "``admin.group``" msgstr "" -#: ../manage/roles/admin-permissions.rst:87 #: ../manage/roles/admin-permissions.rst:93 msgid ":doc:`Manage > Groups `" msgstr "" -#: ../manage/roles/admin-permissions.rst:89 #: ../manage/roles/admin-permissions.rst:95 msgid "``admin.integration``" msgstr "" -#: ../manage/roles/admin-permissions.rst:90 #: ../manage/roles/admin-permissions.rst:96 msgid ":doc:`System > Integrations `" msgstr "" -#: ../manage/roles/admin-permissions.rst:92 #: ../manage/roles/admin-permissions.rst:98 msgid "``admin.knowledge_base``" msgstr "" -#: ../manage/roles/admin-permissions.rst:93 #: ../manage/roles/admin-permissions.rst:99 msgid ":doc:`Manage > Knowledge Base `" msgstr "" @@ -8548,57 +8531,46 @@ msgid "" "knowledge-base.html#editing-answers>`." msgstr "" -#: ../manage/roles/admin-permissions.rst:98 #: ../manage/roles/admin-permissions.rst:104 msgid "``admin.macro``" msgstr "" -#: ../manage/roles/admin-permissions.rst:99 #: ../manage/roles/admin-permissions.rst:105 msgid ":doc:`Manage > Macros `" msgstr "" -#: ../manage/roles/admin-permissions.rst:100 #: ../manage/roles/admin-permissions.rst:106 msgid "In some cases, macros may also require ``admin.tag``" msgstr "" -#: ../manage/roles/admin-permissions.rst:101 #: ../manage/roles/admin-permissions.rst:107 msgid "``admin.maintenance``" msgstr "" -#: ../manage/roles/admin-permissions.rst:102 #: ../manage/roles/admin-permissions.rst:108 msgid ":doc:`System > Maintenance `" msgstr "" -#: ../manage/roles/admin-permissions.rst:104 #: ../manage/roles/admin-permissions.rst:110 msgid "``admin.monitoring``" msgstr "" -#: ../manage/roles/admin-permissions.rst:105 #: ../manage/roles/admin-permissions.rst:111 msgid ":doc:`System > Monitoring `" msgstr "" -#: ../manage/roles/admin-permissions.rst:107 #: ../manage/roles/admin-permissions.rst:113 msgid "``admin.object``" msgstr "" -#: ../manage/roles/admin-permissions.rst:108 #: ../manage/roles/admin-permissions.rst:114 msgid ":doc:`System > Objects `" msgstr "" -#: ../manage/roles/admin-permissions.rst:110 #: ../manage/roles/admin-permissions.rst:116 msgid "``admin.organization``" msgstr "" -#: ../manage/roles/admin-permissions.rst:111 #: ../manage/roles/admin-permissions.rst:117 msgid ":doc:`Manage > Organizations `" msgstr "" @@ -8615,202 +8587,210 @@ msgstr "" msgid "They can even edit an organization's name, domain, and notes!" msgstr "" -#: ../manage/roles/admin-permissions.rst:115 #: ../manage/roles/admin-permissions.rst:121 msgid "``admin.overview``" msgstr "" -#: ../manage/roles/admin-permissions.rst:116 #: ../manage/roles/admin-permissions.rst:122 msgid ":doc:`Manage > Overviews`" msgstr "" -#: ../manage/roles/admin-permissions.rst:118 +#: ../manage/roles/admin-permissions.rst:124 +msgid "``admin.public_links``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:125 +msgid ":doc:`Manage > Public Links `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:127 msgid "``admin.package``" msgstr "" -#: ../manage/roles/admin-permissions.rst:119 #: ../manage/roles/admin-permissions.rst:128 msgid ":doc:`System > Packages `" msgstr "" -#: ../manage/roles/admin-permissions.rst:121 #: ../manage/roles/admin-permissions.rst:130 msgid "``admin.report_profile``" msgstr "" -#: ../manage/roles/admin-permissions.rst:122 #: ../manage/roles/admin-permissions.rst:131 msgid ":doc:`Manage > Report Profiles `" msgstr "" -#: ../manage/roles/admin-permissions.rst:123 #: ../manage/roles/admin-permissions.rst:132 msgid "Access to view reports: ``report``" msgstr "" -#: ../manage/roles/admin-permissions.rst:124 #: ../manage/roles/admin-permissions.rst:133 msgid "``admin.role``" msgstr "" -#: ../manage/roles/admin-permissions.rst:125 #: ../manage/roles/admin-permissions.rst:134 msgid ":doc:`Manage > Roles `" msgstr "" -#: ../manage/roles/admin-permissions.rst:127 #: ../manage/roles/admin-permissions.rst:136 msgid "``admin.scheduler``" msgstr "" -#: ../manage/roles/admin-permissions.rst:128 #: ../manage/roles/admin-permissions.rst:137 msgid ":doc:`Manage > Scheduler `" msgstr "" -#: ../manage/roles/admin-permissions.rst:129 #: ../manage/roles/admin-permissions.rst:138 msgid "For automation on tickets" msgstr "" -#: ../manage/roles/admin-permissions.rst:130 #: ../manage/roles/admin-permissions.rst:139 msgid "``admin.security``" msgstr "" -#: ../manage/roles/admin-permissions.rst:131 #: ../manage/roles/admin-permissions.rst:140 msgid ":doc:`Settings > Security `" msgstr "" -#: ../manage/roles/admin-permissions.rst:132 #: ../manage/roles/admin-permissions.rst:141 msgid "Settings of Zammad. This also covers third party authentications." msgstr "" -#: ../manage/roles/admin-permissions.rst:133 #: ../manage/roles/admin-permissions.rst:142 msgid "``admin.session``" msgstr "" -#: ../manage/roles/admin-permissions.rst:134 #: ../manage/roles/admin-permissions.rst:143 msgid ":doc:`System > Sessions `" msgstr "" -#: ../manage/roles/admin-permissions.rst:136 #: ../manage/roles/admin-permissions.rst:145 msgid "``admin.setting_system``" msgstr "" -#: ../manage/roles/admin-permissions.rst:137 #: ../manage/roles/admin-permissions.rst:146 msgid ":doc:`Settings > System `" msgstr "" -#: ../manage/roles/admin-permissions.rst:139 #: ../manage/roles/admin-permissions.rst:148 msgid "``admin.sla``" msgstr "" -#: ../manage/roles/admin-permissions.rst:140 #: ../manage/roles/admin-permissions.rst:149 msgid ":doc:`Manage > SLAs `" msgstr "" -#: ../manage/roles/admin-permissions.rst:142 +#: ../manage/roles/admin-permissions.rst:151 +msgid "``admin.system_report``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:152 +msgid ":doc:`System > System Report `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:154 msgid "``admin.tag``" msgstr "" -#: ../manage/roles/admin-permissions.rst:143 #: ../manage/roles/admin-permissions.rst:155 msgid ":doc:`Manage > Tags `" msgstr "" -#: ../manage/roles/admin-permissions.rst:145 #: ../manage/roles/admin-permissions.rst:157 msgid "``admin.template``" msgstr "" -#: ../manage/roles/admin-permissions.rst:146 #: ../manage/roles/admin-permissions.rst:158 msgid ":doc:`Manage > Templates `" msgstr "" -#: ../manage/roles/admin-permissions.rst:148 #: ../manage/roles/admin-permissions.rst:160 msgid "``admin.text_module``" msgstr "" -#: ../manage/roles/admin-permissions.rst:149 #: ../manage/roles/admin-permissions.rst:161 msgid ":doc:`Manage > Text Modules `" msgstr "" -#: ../manage/roles/admin-permissions.rst:151 #: ../manage/roles/admin-permissions.rst:163 msgid "``admin.ticket``" msgstr "" -#: ../manage/roles/admin-permissions.rst:152 #: ../manage/roles/admin-permissions.rst:164 msgid ":doc:`Settings > Tickets `" msgstr "" -#: ../manage/roles/admin-permissions.rst:153 #: ../manage/roles/admin-permissions.rst:165 msgid "Does not grant access to :doc:`/misc/composer`" msgstr "" -#: ../manage/roles/admin-permissions.rst:154 +#: ../manage/roles/admin-permissions.rst:166 +msgid "``admin.ticket_auto_assignment``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:167 +msgid ":ref:`Settings > Ticket > Auto Assignment `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:169 +msgid "``admin.ticket_duplicate_detection``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:170 +msgid ":ref:`Settings > Ticket > Duplicate Detection `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:172 +msgid "``admin.ticket_priority``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:173 +msgid ":ref:`System > Objects >Ticket Priority `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:175 +msgid "``admin.ticket_state``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:176 +msgid ":ref:`System > Objects >Ticket State `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:178 msgid "``admin.time_accounting``" msgstr "" -#: ../manage/roles/admin-permissions.rst:155 #: ../manage/roles/admin-permissions.rst:179 msgid ":doc:`Manage > Time Accounting `" msgstr "" -#: ../manage/roles/admin-permissions.rst:156 #: ../manage/roles/admin-permissions.rst:180 msgid "Also allows the export of timekeeping records." msgstr "" -#: ../manage/roles/admin-permissions.rst:157 #: ../manage/roles/admin-permissions.rst:181 msgid "``admin.translation``" msgstr "" -#: ../manage/roles/admin-permissions.rst:158 #: ../manage/roles/admin-permissions.rst:182 msgid ":doc:`System > Translations `" msgstr "" -#: ../manage/roles/admin-permissions.rst:159 #: ../manage/roles/admin-permissions.rst:183 msgid "Also enables inline translation" msgstr "" -#: ../manage/roles/admin-permissions.rst:160 #: ../manage/roles/admin-permissions.rst:184 msgid "``admin.trigger``" msgstr "" -#: ../manage/roles/admin-permissions.rst:161 #: ../manage/roles/admin-permissions.rst:185 msgid ":doc:`Manage > Triggers `" msgstr "" -#: ../manage/roles/admin-permissions.rst:163 #: ../manage/roles/admin-permissions.rst:187 msgid "``admin.user``" msgstr "" -#: ../manage/roles/admin-permissions.rst:164 #: ../manage/roles/admin-permissions.rst:188 msgid ":doc:`Manage > Users `" msgstr "" @@ -8829,6 +8809,14 @@ msgid "" "from-users-perspective>` ." msgstr "" +#: ../manage/roles/admin-permissions.rst:193 +msgid "``admin.webhook``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:194 +msgid ":doc:`Manage > Webhook `" +msgstr "" + #: ../manage/roles/agent-permissions.rst:2 msgid "Agent Permissions" msgstr "" @@ -9247,36 +9235,45 @@ msgid "than the user that generated them." msgstr "" #: ../manage/roles/user-preferences-permissions.rst:43 +msgid "``user_preferences.appearance``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:44 +msgid "Appearance configuration" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "Users can switch between dark, light and" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "automatic mode." +msgstr "" + #: ../manage/roles/user-preferences-permissions.rst:47 msgid "``user_preferences.avatar``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:44 #: ../manage/roles/user-preferences-permissions.rst:48 msgid "Avatar settings" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:45 #: ../manage/roles/user-preferences-permissions.rst:49 msgid "Override the default Gravatar with a custom avatar" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:46 #: ../manage/roles/user-preferences-permissions.rst:50 msgid "``user_preferences.calendar``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:47 #: ../manage/roles/user-preferences-permissions.rst:51 msgid "Configure the calendar feed" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:49 #: ../manage/roles/user-preferences-permissions.rst:53 msgid "``user_preferences.device``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:50 #: ../manage/roles/user-preferences-permissions.rst:54 msgid "Manage device login sessions" msgstr "" @@ -9293,22 +9290,18 @@ msgstr "" msgid "To learn more, see :doc:`/manage/trigger/system-notifications`." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:54 #: ../manage/roles/user-preferences-permissions.rst:58 msgid "``user_preferences.language``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:55 #: ../manage/roles/user-preferences-permissions.rst:59 msgid "Configure the UI locale/language" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:57 #: ../manage/roles/user-preferences-permissions.rst:61 msgid "``user_preferences.linked_accounts``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:58 #: ../manage/roles/user-preferences-permissions.rst:62 msgid "Account linking" msgstr "" @@ -9332,7 +9325,6 @@ msgstr "" msgid "is the only way users can utilize third-party logins." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:63 #: ../manage/roles/user-preferences-permissions.rst:67 msgid "``user_preferences.notifications``" msgstr "" @@ -9359,7 +9351,6 @@ msgstr "" msgid "Customers can't receive ticket notifications at all." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:69 #: ../manage/roles/user-preferences-permissions.rst:73 msgid "``user_preferences.out_of_office``" msgstr "" @@ -9384,7 +9375,6 @@ msgstr "" msgid "they're replacing." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:75 #: ../manage/roles/user-preferences-permissions.rst:79 msgid "``user_preferences.overview_sorting``" msgstr "" @@ -9413,12 +9403,10 @@ msgstr "" msgid "overviews has no effect on custom orders." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:82 #: ../manage/roles/user-preferences-permissions.rst:86 msgid "``user_preferences.password``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:83 #: ../manage/roles/user-preferences-permissions.rst:87 msgid "Change account password" msgstr "" @@ -9435,7 +9423,6 @@ msgstr "" msgid "your only allowed authentication method." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:87 #: ../manage/roles/user-preferences-permissions.rst:91 msgid "``user_preferences.two_factor_authentication``" msgstr "" @@ -9472,7 +9459,7 @@ msgstr "" #: ../manage/scheduler.rst:19 msgid "" -"Schedulers can be used to send periodic reminder emails. Use :doc:`/system/" +"Schedulers can be used to send periodic reminder emails. Use :doc:`/misc/" "variables` to build highly-customized email templates." msgstr "" @@ -10468,7 +10455,7 @@ msgstr "" #: ../manage/text-modules.rst:57 msgid "" -"The example text modules below use :doc:`/system/variables` to dynamically " +"The example text modules below use :doc:`/misc/variables` to dynamically " "insert information like the customer's or agent's names." msgstr "" @@ -10808,8 +10795,8 @@ msgstr "" #: ../misc/object-conditions/basics.rst:144 #: ../misc/object-conditions/basics.rst:160 #: ../misc/object-conditions/basics.rst:168 -#: ../misc/object-conditions/basics.rst:178 ../settings/ticket.rst:2 -#: ../system/variables/ticket.rst:2 +#: ../misc/object-conditions/basics.rst:178 ../misc/variables/ticket.rst:2 +#: ../settings/ticket.rst:2 msgid "Ticket" msgstr "" @@ -11043,7 +11030,7 @@ msgstr "" #: ../manage/trigger/how-do-they-work.rst:79 msgid "" -"Certain actions (such as *email*, *SMS* and *notes*) support :doc:`/system/" +"Certain actions (such as *email*, *SMS* and *notes*) support :doc:`/misc/" "variables`, which can be used to build highly-customized message templates." msgstr "" @@ -11072,7 +11059,7 @@ msgstr "" msgid "" "You can also combine static text with placeholders for text fields. Remember " "that the placeholders' values have to be known during trigger runtime. Learn " -"more about :doc:`/system/variables`." +"more about :doc:`/misc/variables`." msgstr "" #: ../manage/trigger/how-do-they-work.rst:105 @@ -12037,7 +12024,7 @@ msgstr "" msgid "" "When switched on, a code editor will be shown below, where you can configure " "custom payload for your webhook in JSON format. To insert supported :doc:`/" -"system/variables` use ``::`` or ``#{`` shortcuts for autocomplete." +"misc/variables` use ``::`` or ``#{`` shortcuts for autocomplete." msgstr "" #: ../manage/webhook/add.rst:103 @@ -14614,11942 +14601,11833 @@ msgid "" "powerful conditions with AND/OR relations." msgstr "" -#: ../settings/branding.rst:10 -msgid "Product Name" +#: ../misc/variables.rst:2 +msgid "Variables" msgstr "" -#: ../settings/branding.rst:7 +#: ../misc/variables.rst:4 msgid "" -"Defines the name of the application, shown in the web interface, tabs and " -"title bar of the web browser." +"Please note that this is just an overview of available variables. It might " +"be incomplete or variables might not be available within some functions. If " +"you're missing variables or are not sure if something is not working as " +"expected, feel free to ask over at the `Community `_." msgstr "" -#: ../settings/branding.rst:10 -msgid "Default value: ``Zammad Helpdesk``" +#: ../misc/variables.rst:10 +msgid "" +"Variables can be called by typing ``::`` (just like text modules in the " +"frontend), as long as you're in a supported text field within the backend. " +"Zammad will display all variables being available within this context and " +"replace it to the variable as soon as you selected an entry." msgstr "" -#: ../settings/branding.rst:13 -msgid "Will be shown in the app and is included in email footers." +#: ../misc/variables.rst:15 +msgid "" +"You have an empty field which you referenced and it appears as ``-``? That's " +"currently working as designed - you might want to ensure that these fields " +"always have a value." msgstr "" -#: ../settings/branding.rst:19 -msgid "Logo" +#: ../misc/variables.rst:20 +msgid "Variable Categories" msgstr "" -#: ../settings/branding.rst:16 -msgid "Defines the logo of the application, shown in the login page of Zammad." +#: ../misc/variables.rst:31 +msgid "Wait, What About Custom Objects?" msgstr "" -#: ../settings/branding.rst:18 +#: ../misc/variables.rst:33 msgid "" -"Ensure to hit the \"Submit\" button after uploading the logo. Otherwise your " -"change will not be saved." +"Good point! Of course, we can't predict what objects you might create, but " +"we can give you a hint on how to put the puzzle together to get your custom " +"values." msgstr "" -#: ../settings/branding.rst:22 +#: ../misc/variables.rst:36 msgid "" -"Allows to set the default language of the Zammad instance. The here defined " -"locale mostly acts as a fallback for:" -msgstr "" - -#: ../settings/branding.rst:25 -msgid "user preferences (if Zammad can't detect the users locale)" +"For this, we'll talk about the inner part of the variable (so everything " +"within ``#{}``), please put the outer part around to have a valid variable. " +"The first part of the variable name consist of the object type. Currently " +"these are:" msgstr "" -#: ../settings/branding.rst:26 -msgid "CSV output (reporting, time accounting)" +#: ../misc/variables.rst:41 +msgid "Ticket (``ticket``)" msgstr "" -#: ../settings/branding.rst:30 -msgid "Define the timezone of your Zammad installation." +#: ../misc/variables.rst:42 +msgid "User (``user``)" msgstr "" -#: ../settings/branding.rst:32 -msgid "" -"This does not have any effect on timings for your agents or how Zammad " -"stores date and time values." +#: ../misc/variables.rst:43 +msgid "Organization (``organization``)" msgstr "" -#: ../settings/branding.rst:35 -msgid "Changing this value has direct consequences on the following areas:" +#: ../misc/variables.rst:44 +msgid "Group (``group``)" msgstr "" -#: ../settings/branding.rst:37 -msgid ":doc:`/manage/scheduler` tasks" +#: ../misc/variables.rst:46 +msgid "" +"The second part is the name of the attribute. This is the name you define " +"during object creation and can be found within the object attribute menu at " +"any time. The first and second part of a variable is divided by a point, e." +"g.: ``ticket.number`` which will in total be ``#{ticket.number}``." msgstr "" -#: ../settings/branding.rst:38 -msgid "search indexing (and thus reporting)" +#: ../misc/variables.rst:51 +msgid "" +"Now, in some situations it's possible that you'll need to use a third part. " +"The best example for such a situation would be a ``select`` or ``tree-" +"select`` field which will by default return the key value, not it's display " +"name. For this, just extend your variable with ``.value``. This will result " +"in ``#{ticket.select.value}``." msgstr "" -#: ../settings/branding.rst:40 -msgid "calendar subscriptions" +#: ../misc/variables.rst:60 +msgid "Using Translated Variables" msgstr "" -#: ../settings/branding.rst:41 -msgid "browser printing" +#: ../misc/variables.rst:62 +msgid "" +"If you want to use a translated variable in triggers or schedulers, you can " +"extend the placeholder like this: ``#{t(ticket.state.name)}``. The ``t`` " +"tells Zammad to search for fitting translated strings. The used output " +"language is based on the system language of Zammad which you can set in the " +"admin panel under :doc:`/settings/branding` or based on the selected locale " +"in the trigger/scheduler edit dialog." msgstr "" -#: ../settings/branding.rst:43 +#: ../misc/variables.rst:69 msgid "" -"Please note that some of above are fallbacks in case Zammad could not detect " -"the agents timezone correctly." +"A possible use-case: you want to send your customers updates on tickets via " +"trigger or scheduler which should include the state of the ticket. Using the " +"default ``#{ticket.state.name}`` (without the translation flag ``t()``) " +"would lead to the output of the original (english) name of the state." msgstr "" -#: ../settings/branding.rst:77 -msgid "Pretty Date" +#: ../misc/variables.rst:75 +msgid "Date and Time Formatting" msgstr "" -#: ../settings/branding.rst:47 +#: ../misc/variables.rst:77 msgid "" -"This setting allows you to define how Zammad should display time stamps " -"within the interface to all users." +"The system (trigger/scheduler selected) locale and timezone predefines a " +"default format of date and timestamp. This format is customizable by using " +"the ``dt()`` method." msgstr "" -#: ../settings/branding.rst:50 -msgid "" -"This does not have any effect on how Zammad returns e.g. time values via " -"variables." +#: ../misc/variables.rst:79 +msgid "The method arguments are as follows:" msgstr "" -#: ../settings/branding.rst:77 -msgid "Choose in between the following options:" +#: ../misc/variables.rst:81 +msgid "The date or timestamp variable you want to format." msgstr "" -#: ../settings/branding.rst:64 -msgid "relative" +#: ../misc/variables.rst:82 +msgid "The output format string." msgstr "" -#: ../settings/branding.rst:55 +#: ../misc/variables.rst:83 +msgid "The timezone to apply (optional)." +msgstr "" + +#: ../misc/variables.rst:85 +#: ../system/objects/external-data-source-example.rst:23 +msgid "**Example:**" +msgstr "" + +#: ../misc/variables.rst:86 msgid "" -"This timestamp shows a relative time span until it switches to a date. Over " -"time, it will change as follows:" +"``#{dt(ticket.updated_at, \"%A %Y-%m-%d %H:%M in the office\", \"Europe/" +"Berlin\")}``" msgstr "" -#: ../settings/branding.rst:58 -msgid "just now" +#: ../misc/variables.rst:87 +msgid "Monday, 2024-03-18 15:31 in the office" msgstr "" -#: ../settings/branding.rst:59 -msgid "5 minutes ago" +#: ../misc/variables.rst:89 +msgid "" +"If you want to use our example, make sure to paste the string above without " +"formatting (``CTRL+Shift+v``), otherwise it won't work." msgstr "" -#: ../settings/branding.rst:60 -msgid "3 days 1 hour ago" +#: ../misc/variables.rst:93 +msgid "The following table lists available format directives:" msgstr "" -#: ../settings/branding.rst:61 -msgid "``03/04/2022``" +#: ../misc/variables.rst:99 +msgid "Parameter" msgstr "" -#: ../settings/branding.rst:63 -msgid "Hovering the timestamp helps, you'll always get a clean timestamp then." +#: ../misc/variables.rst:102 +msgid "``%Y``" msgstr "" -#: ../settings/branding.rst:71 -msgid "absolute" +#: ../misc/variables.rst:103 +msgid "Year with 4 digits" msgstr "" -#: ../settings/branding.rst:67 -msgid "" -"This timestamp always includes the week day. For one week after creation, " -"the timestamp will not contain the date itself: Thursday 18:35." +#: ../misc/variables.rst:104 +msgid "Use ``%y`` for year with 2 digits" msgstr "" -#: ../settings/branding.rst:71 -msgid "After a week it will switch to: ``Friday 4. Mar 16:00``." +#: ../misc/variables.rst:105 +msgid "``%m``" msgstr "" -#: ../settings/branding.rst:76 -msgid "timestamp" +#: ../misc/variables.rst:106 +msgid "Month of year (as number with zero-padding)" msgstr "" -#: ../settings/branding.rst:74 -msgid "" -"This will cause Zammad to show a complete timestamp according to your locale " -"defaults. For English this could be e.g. ``2022/12/03 2:40 pm`` or for " -"German e.g. ``12.03.2022 14:40``." +#: ../misc/variables.rst:107 +msgid "Use ``%-m`` for month without zero-padding" msgstr "" -#: ../settings/branding.rst:78 -msgid "Default setting: ``relative``." +#: ../misc/variables.rst:108 +msgid "``%d``" msgstr "" -#: ../settings/security.rst:2 -msgid "Security" +#: ../misc/variables.rst:109 +msgid "Day of month (as number with zero-padding)" msgstr "" -#: ../settings/security.rst:4 -msgid "" -"For your overview we split each tab within security settings into its own " -"page:" +#: ../misc/variables.rst:110 +msgid "Use ``%e`` for day without zero-padding" msgstr "" -#: ../settings/security/base.rst:2 ../settings/system/base.rst:2 -#: ../settings/ticket.rst:8 -msgid "Base" +#: ../misc/variables.rst:111 +msgid "``%H``" msgstr "" -#: ../settings/security/base.rst:5 -msgid "New User Accounts" +#: ../misc/variables.rst:112 +msgid "Hour of day in 24h notation with zero-padding" msgstr "" -#: ../settings/security/base.rst:9 -msgid "" -"Activates the `register as a new customer` function on the login page. If " -"set to ``no`` only administrators or agents can create new accounts manually." +#: ../misc/variables.rst:113 +msgid "Use ``%k`` for hour without zero-padding" msgstr "" -#: ../settings/security/base.rst:13 ../settings/security/base.rst:38 -#: ../settings/security/base.rst:66 -msgid "Default setting: ``yes``" +#: ../misc/variables.rst:114 +msgid "``%I``" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing activated \"New User Accounts\" setting" +#: ../misc/variables.rst:115 +msgid "Hour of day in 12h notation with zero-padding" msgstr "" -#: ../settings/security/base.rst:22 +#: ../misc/variables.rst:116 msgid "" -"Deactivation of above function **does not** deactivate automatic account " -"creation! This means: If a user writes e.g. an email to Zammad and has no " -"account yet, Zammad will automatically create the account. User accounts are " -"a direct dependency of tickets and thus technically mandatory." +"Use ``%l`` for hour without zero-padding and ``%p`` / ``%P`` for meridian " +"indicator" msgstr "" -#: ../settings/security/base.rst:29 -msgid "Lost Password" +#: ../misc/variables.rst:117 +msgid "``%M``" msgstr "" -#: ../settings/security/base.rst:33 -msgid "" -"Activates the `lost password` function on the login page. If set to ``no`` " -"only administrators may change the user's password - users may update their " -"own password if they're still logged in and they have the required :doc:" -"`permission `." +#: ../misc/variables.rst:118 +msgid "Minute of hour" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing activated \"Lost Password\" setting" +#: ../misc/variables.rst:120 +msgid "``%S``" msgstr "" -#: ../settings/security/base.rst:49 -msgid "" -"With third party authentications - but especially LDAP - you may want to " -"disable this function. Zammad **will not** change third party login " -"passwords and instead set or change the local password!" +#: ../misc/variables.rst:121 +msgid "Second of Minute" msgstr "" -#: ../settings/security/base.rst:56 -msgid "Password Login" +#: ../misc/variables.rst:123 +msgid "``%A``" msgstr "" -#: ../settings/security/base.rst:60 -msgid "" -"Activates the username & password login by default and if no third-party " -"login is activated. Disabling password login on the Zammad login page only " -"takes effect if you enable any :doc:`third-party`." +#: ../misc/variables.rst:124 +msgid "Weekday name" msgstr "" -#: ../settings/security/base.rst:64 -msgid "See :doc:`third-party` for supported third-party logins." +#: ../misc/variables.rst:125 +msgid "Use ``%a`` for abbreviated name or ``%^A`` for uppercase name" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing de-activated \"Password Login\" setting" +#: ../misc/variables.rst:126 +msgid "``%B``" msgstr "" -#: ../settings/security/base.rst:77 -msgid "" -"To help administrators to overcome \"login issues\", Zammad automatically " -"offers a password request for administrator users. This allows you to adjust " -"Third-Party applications even if the login does no longer work!" +#: ../misc/variables.rst:127 +msgid "Month name" msgstr "" -#: ../settings/security/base.rst:84 -msgid "Session Timeout" +#: ../misc/variables.rst:128 +msgid "Use ``%b`` for abbreviated name" msgstr "" -#: ../settings/security/base.rst:86 -msgid "" -"All settings below by default are set to ``4 weeks``. Session Timeout " -"defines the life time of a users session. As soon as it's reached, Zammad " -"will automatically log off the session in question." +#: ../misc/variables.rst:129 +msgid "``%U``" msgstr "" -#: ../settings/security/base.rst:91 -msgid "" -"Zammad takes the highest value set assigned for the user based on the " -"permissions." +#: ../misc/variables.rst:130 +msgid "Week number of current year" msgstr "" -#: ../settings/security/base.rst:94 -msgid "``admin``" +#: ../misc/variables.rst:131 +msgid "Use ``%W`` for a different calculation method" msgstr "" -#: ../settings/security/base.rst:96 -msgid "``ticket.customer``" +#: ../misc/variables.rst:134 +msgid "" +"We support the known format directives for the Ruby built-in method " +"``strftime`` of the ``DateTime`` class. For more information, see `here " +"`_." msgstr "" -#: ../settings/security/base.rst:97 -msgid "``default`` (fallback if user doesn't have above permissions set)" +#: ../misc/variables/article.rst:2 +msgid "Articles" msgstr "" -#: ../settings/security/base.rst:99 +#: ../misc/variables/article.rst:4 ../misc/variables/config.rst:4 +#: ../misc/variables/current-user.rst:4 ../misc/variables/ticket.rst:4 msgid "" -"All settings act independently from each other allowing you to disable the " -"timeouts for e.g. admins, but not agents." +"If you're missing variables or are not sure if something is not working as " +"expected, feel free to ask over at the `Community `_." msgstr "" -#: ../settings/security/base.rst:115 -#: ../system/integrations/checkmk/api-reference.rst:13 -msgid "Example" +#: ../misc/variables/article.rst:6 +msgid "" +"Below you can find all available ticket article-based variables within " +"Zammad. These can be called via triggers for example. If you're unsure if " +"Zammad does support variables at the point you're at, you can try to type " +"``::`` to check." msgstr "" -#: ../settings/security/base.rst:107 -msgid "Let's suppose you configured the following session timeouts" +#: ../misc/variables/article.rst:9 ../misc/variables/config.rst:9 +#: ../misc/variables/ticket.rst:9 +msgid "" +"The below list gives you an example what kind of data you can expect, it's " +"not intended to explain the data itself." msgstr "" -#: ../settings/security/base.rst:104 -msgid "default: 3 weeks" +#: ../misc/variables/article.rst:11 +msgid "Article Variables" msgstr "" -#: ../settings/security/base.rst:105 -msgid "admin: 2 weeks" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "name" msgstr "" -#: ../settings/security/base.rst:106 -msgid "ticket.agent: 4 weeks" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "variable" msgstr "" -#: ../settings/security/base.rst:107 -msgid "ticket.customer: 1 week" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "example" msgstr "" -#: ../settings/security/base.rst:115 -msgid "This results in the following situations" +#: ../misc/variables/article.rst:1 +msgid "Article > Cc" msgstr "" -#: ../settings/security/base.rst:110 -msgid "a user with ``admin`` permission will have a timeout of 2 weeks" +#: ../misc/variables/article.rst:1 +msgid "``#{article.cc}``" msgstr "" -#: ../settings/security/base.rst:111 -msgid "" -"a user with ``admin`` and ``ticket.agent`` permissions will have a timeout " -"of 2 weeks" +#: ../misc/variables/article.rst:1 +msgid "``jdoe@example.com, company@example.com``" msgstr "" -#: ../settings/security/base.rst:113 -msgid "" -"a user with ``ticket.customer`` permission will have a timeout of 1 week" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Address" msgstr "" -#: ../settings/security/base.rst:115 -msgid "" -"a user with neither ``admin``, ``ticket.agent`` nor ``ticket.customer`` " -"permissions will have a timeout of 3 weeks" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.address}``" msgstr "" -#: ../settings/security/password.rst:4 -msgid "" -"This section allows you to define password requirements for the local user " -"accounts." +#: ../misc/variables/article.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:9 -msgid "" -"Zammad does **not** allow you to change your LDAP password, instead, it will " -"set a password in its local database which might confuse your users. This " -"might be addressed in the future by `#1169 `_." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Department" msgstr "" -#: ../settings/security/password.rst:14 -msgid "**Exception for admins**" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.department}``" msgstr "" -#: ../settings/security/password.rst:16 -msgid "" -"Please note that below password policies *do not* affect administrators " -"setting passwords on user accounts. While this seems strange and not safe we " -"believe that an administrator knowing an user's password is insecure as well." +#: ../misc/variables/article.rst:1 +msgid "``Sales`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:21 -msgid "The suggested workflow is either:" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Email" msgstr "" -#: ../settings/security/password.rst:23 -msgid "" -"to use third party logins to not require local passwords at all **- or -**" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.email}``" msgstr "" -#: ../settings/security/password.rst:25 -msgid "to require your *user to reset the password* upon first login." +#: ../misc/variables/article.rst:1 +msgid "``jdoe@example.com``" msgstr "" -#: ../settings/security/password.rst:27 -msgid "" -"This way administrators are not required to set a user's password at all!" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Fax" msgstr "" -#: ../settings/security/password.rst:31 -msgid "Maximum Failed Logins" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.fax}``" msgstr "" -#: ../settings/security/password.rst:33 -msgid "" -"You can choose a value between ``4`` and ``20``. This defines how often a " -"login to a user account may fail until Zammad will lock it. Your users can " -"always use the \"forgot password\" function to change their password and " -"unlock their account." -msgstr "" - -#: ../settings/security/password.rst:38 -msgid "The default value is ``10``." +#: ../misc/variables/article.rst:1 +msgid "``+4930123456789`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:42 -msgid "Beside changing the user's password, you can also unlock accounts via" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Firstname" msgstr "" -#: ../settings/security/password.rst:44 -msgid ":ref:`user management list `" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.firstname}``" msgstr "" -#: ../settings/security/password.rst:45 -msgid ":docs:`console `" +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Joe`` or empty if not set" msgstr "" -#: ../settings/security/password.rst:46 -msgid ":docs:`API `" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Lastname" msgstr "" -#: ../settings/security/password.rst:50 -msgid "Failed logins via LDAP no longer lock accounts." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.lastname}``" msgstr "" -#: ../settings/security/password.rst:53 -msgid "2 Lower Case And 2 Upper Case Characters" +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +#: ../misc/variables/ticket.rst:1 +msgid "``Doe`` or empty if not set" msgstr "" -#: ../settings/security/password.rst:55 -msgid "" -"You can add complexity to passwords by enforcing at least 2 upper and lower " -"case characters." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Login" msgstr "" -#: ../settings/security/password.rst:58 ../settings/security/password.rst:83 -msgid "The default value is ``no``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.login}``" msgstr "" -#: ../settings/security/password.rst:62 -msgid "Minimum Length" +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +#: ../misc/variables/ticket.rst:1 +msgid "``jdoe``" msgstr "" -#: ../settings/security/password.rst:64 -msgid "" -"This defines the minimum password length required for users to provide (from " -"``4`` to ``20``)." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Mobile" msgstr "" -#: ../settings/security/password.rst:67 -msgid "The default value is ``6``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.mobile}``" msgstr "" -#: ../settings/security/password.rst:71 -msgid "Digit Required" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Note" msgstr "" -#: ../settings/security/password.rst:73 -msgid "This enforces your users to use at least one digit within the password." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.note}``" msgstr "" -#: ../settings/security/password.rst:75 -msgid "The default value is ``yes``." +#: ../misc/variables/article.rst:1 +msgid "``Some note about user`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:78 -msgid "Special Character Required" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Phone" msgstr "" -#: ../settings/security/password.rst:80 -msgid "" -"This setting allows you to improve your password quality even more by " -"enforcing the password to contain at least one special character." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.phone}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:2 -msgid "SSL Certificates" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > VIP" msgstr "" -#: ../settings/security/ssl-certificates.rst:7 -msgid "" -"Zammad offers the possibility to upload custom certificates and custom " -"Certificate Authority (CA) certificates. This can be useful if you want to " -"connect Zammad the secure way to other systems which are using custom " -"certificates." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.vip}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:12 -msgid "" -"An example usecase might be: You have an internal LDAP server that is not " -"accessible from the internet, and you want a SSL-encrypted connection, using " -"a custom certificate." +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +msgid "``true`` or ``false``" msgstr "" -#: ../settings/security/ssl-certificates.rst:19 -msgid "" -"You should have an existing custom certificate file and/or a custom CA " -"certificate file, which you want to add to Zammad. As filetype ``.crt`` is " -"supported and the certificate format has to be PEM (Base64 ASCII)." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Web" msgstr "" -#: ../settings/security/ssl-certificates.rst:25 -msgid "" -"When you import a custom CA certificate, all certificates generated with " -"this are trusted. This can be useful if you have more than one system/" -"certificate you want to connect to and the certificates are issued from the " -"same custom CA." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.web}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:31 -msgid "Add a Certificate" +#: ../misc/variables/article.rst:1 +msgid "``https://zammad.com`` or empty if not set in user object" msgstr "" -#: ../settings/security/ssl-certificates.rst:33 -msgid "" -"To add a custom certificate or a custom CA certificate, head over to the " -"Admin panel > Settings > Security > SSL Certificates. Here you can find a " -"\"Add SSL Certificate\" button. In the dialog you can either select a " -"certificate file or paste the content of the certificate:" +#: ../misc/variables/article.rst:1 +msgid "Article > Created" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate adding dialog" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_at}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:43 -msgid "" -"After selecting a file or pasting the content of the certificate, click on " -"the \"Add\" button to finally upload it to Zammad. Then, the certificates " -"are immediately effective, no restart or similar required." +#: ../misc/variables/article.rst:1 +msgid "``2019-10-08 15:24:47 UTC``" msgstr "" -#: ../settings/security/ssl-certificates.rst:49 -msgid "" -"Please note that only single certificate files are supported. That means if " -"you want to import a certificate / CA certificate, it must contain **only " -"one** certificate." +#: ../misc/variables/article.rst:1 +msgid "Article > From" msgstr "" -#: ../settings/security/ssl-certificates.rst:54 -msgid "Certificate Overview" +#: ../misc/variables/article.rst:1 +msgid "``#{article.from}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:56 +#: ../misc/variables/article.rst:1 msgid "" -"After you added a certificate, you can see a table with information for each " -"added certificate:" +"``Joe Doe `` may differ, depends on ``FROM`` of send mail" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing table of added certificates" +#: ../misc/variables/article.rst:1 +msgid "Article > Sender > Name" msgstr "" -#: ../settings/security/ssl-certificates.rst:64 -msgid "" -"Here you can download the certificate or delete it, if you don't need it " -"anymore." +#: ../misc/variables/article.rst:1 +msgid "``#{article.sender.name}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:68 -msgid "Deleting Certificates" +#: ../misc/variables/article.rst:1 +msgid "``Customer``, ``Agent`` or ``System``" msgstr "" -#: ../settings/security/ssl-certificates.rst:70 -msgid "" -"If you want to delete a specific certificate, you can do it by clicking on " -"the menu in the actions column and selecting delete:" +#: ../misc/variables/article.rst:1 +msgid "Article > Subject" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate deletion button" +#: ../misc/variables/article.rst:1 +msgid "``#{article.subject}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:79 -msgid "Downloading Certificates" +#: ../misc/variables/article.rst:1 +msgid "``My amazing subject``" msgstr "" -#: ../settings/security/ssl-certificates.rst:81 -msgid "" -"If you want to download your certificates, you can do this as well via " -"corresponding action buttons." +#: ../misc/variables/article.rst:1 +msgid "Article > Text" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate download button" +#: ../misc/variables/article.rst:1 +msgid "``#{article.body}``" msgstr "" -#: ../settings/security/third-party.rst:13 -msgid "Login Providers" +#: ../misc/variables/article.rst:1 +msgid "``Test`` without formatting (plain)" msgstr "" -#: ../settings/security/third-party.rst:2 -msgid "Third-Party Applications" +#: ../misc/variables/article.rst:1 +msgid "Article > TicketID" msgstr "" -#: ../settings/security/third-party.rst:4 -msgid "" -"Third party authentication is a great way to help your users to login to " -"Zammad more easily. If the account is yet unknown, Zammad will create a new " -"user automatically, without the user needed to interact (e.g. type in his " -"name). Another big advantage of this feature is that your user doesn't need " -"to remember another password." +#: ../misc/variables/article.rst:1 +msgid "``#{article.ticket_id}``" msgstr "" -#: ../settings/security/third-party.rst:10 -msgid "" -"You can deactivate logging in via :ref:`security_password_login` if any of " -"the mentioned authentication providers are enabled in your instance." +#: ../misc/variables/article.rst:1 +msgid "``1`` (not ticket number)" msgstr "" -#: ../settings/security/third-party.rst:27 -msgid "" -"We're currently missing documentation for the following login providers:" +#: ../misc/variables/article.rst:1 +msgid "Article > To" msgstr "" -#: ../settings/security/third-party.rst:29 -msgid "LinkedIn" +#: ../misc/variables/article.rst:1 +msgid "``#{article.to}``" msgstr "" -#: ../settings/security/third-party.rst:30 -msgid "Weibo" +#: ../misc/variables/article.rst:1 +msgid "``helpdesk@example.com``" msgstr "" -#: ../settings/security/third-party.rst:35 -msgid "Automatic Account Link on Initial Logon" +#: ../misc/variables/article.rst:1 +msgid "Article > Type > Name" msgstr "" -#: ../settings/security/third-party.rst:37 -msgid "" -"In general there's two possible options for Zammad on how to deal with " -"already known users as they try to authenticate against a third-party " -"application. By default, Zammad will not automatically link \"unknown\" " -"authentication providers to existing accounts." +#: ../misc/variables/article.rst:1 +msgid "``#{article.type.name}``" msgstr "" -#: ../settings/security/third-party.rst:42 +#: ../misc/variables/article.rst:1 msgid "" -"This means that the user has to manually link authentication providers to " -"their accounts (for more about this :user-docs:`consult the user " -"documentation `)." +"``email`` (`list of article types `_)" msgstr "" -#: ../settings/security/third-party.rst:46 -msgid "" -"Sometimes this doesn't come in handy as this also means you'll receive error " -"messages about \"email address being in use already\" for (yet) unknown " -"third-party authentication methods." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Address" msgstr "" -#: ../settings/security/third-party.rst:50 -msgid "" -"If you want to allow your users to always be able to log in, no matter what, " -"you may want to enable ``Automatic account link on initial logon``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.address}``" msgstr "" -#: ../settings/security/third-party.rst:None -msgid "" -"Screenshot highlighting the \"Automatic account link on initial logon\"\n" -"setting" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Department" msgstr "" -#: ../settings/security/third-party.rst:60 -msgid "Automatic Account Linking Notification" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.department}``" msgstr "" -#: ../settings/security/third-party.rst:64 -msgid "" -"To improve security and your users awareness, you can enable Zammad to " -"notify your users when a new third-party application has been linked to " -"their account." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Email" msgstr "" -#: ../settings/security/third-party.rst:68 -msgid "" -"This notification is sent out once per third-party application. Zammad does " -"also mention the method used, e.g.: ``Microsoft``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.email}``" msgstr "" -#: ../settings/security/third-party.rst:71 -msgid "By default this setting is not active (set to ``no``)." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Fax" msgstr "" -#: ../settings/security/third-party.rst:0 -msgid "" -"Screenshot showing sample notification mail after initial\n" -"third-party linking" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.fax}``" msgstr "" -#: ../settings/security/third-party.rst:85 -msgid "" -"This notification is only sent if the account in question already exists. If " -"the login via the third-party also creates the missing account, the " -"notification will be skipped." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Firstname" msgstr "" -#: ../settings/security/third-party.rst:89 -msgid "This means it only affects:" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.firstname}``" msgstr "" -#: ../settings/security/third-party.rst:91 -msgid "manual account linking within the third-party page of the users profile" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Lastname" msgstr "" -#: ../settings/security/third-party.rst:92 -msgid "" -"logging into an existing local account by utilizing the *automatic account " -"link on initial logon* functionality" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.lastname}``" msgstr "" -#: ../settings/security/third-party.rst:None -msgid "" -"Screenshot showing the \"automatic account linking notification\"\n" -"setting" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Login" msgstr "" -#: ../settings/security/third-party.rst:100 -msgid "No User Creation on Logon" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.login}``" msgstr "" -#: ../settings/security/third-party.rst:102 -msgid "" -"By default, Zammad will create a new user account if the user logs in via a " -"third-party application and the account doesn't exist yet." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Mobile" msgstr "" -#: ../settings/security/third-party.rst:105 -msgid "" -"If you want to prevent Zammad from creating new accounts on logon, you can " -"disable this feature by setting ``No user creation on logon`` to ``yes``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.mobile}``" msgstr "" -#: ../settings/security/third-party.rst:None -msgid "Screenshot showing the \"no user creation on logon\" setting" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Note" msgstr "" -#: ../settings/security/third-party/facebook.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via Facebook To do " -"so, you need to follow these steps:" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.note}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:9 -msgid "Register Facebook App" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Phone" msgstr "" -#: ../settings/security/third-party/facebook.rst:11 -msgid "" -"Visit [https://developers.facebook.com/apps/] and click on \"Add a new App\"" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.phone}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "initial page" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > VIP" msgstr "" -#: ../settings/security/third-party/facebook.rst:17 -msgid "After that enter the app settings" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.vip}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "Create App" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Web" msgstr "" -#: ../settings/security/third-party/facebook.rst:22 -msgid "Navigate to \"Settings\" and fill in this infromation" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.web}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "App Settings" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated" msgstr "" -#: ../settings/security/third-party/facebook.rst:27 -msgid "Navigate to app review and Check \"Make [appname] public?\"" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_at}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "App Review" +#: ../misc/variables/article.rst:1 +msgid "Article > Visibility" msgstr "" -#: ../settings/security/third-party/facebook.rst:35 -msgid "Configure Zammad as Facebook App" +#: ../misc/variables/article.rst:1 +msgid "``#{article.internal}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:37 -msgid "" -"Navigate to \"Admin -> Security -> Third Party Applications\" and enter the " -"App ID and the App Secret. You can find this Key in the Dashbard of your " -"Facebok app." +#: ../misc/variables/article.rst:1 +msgid "``false`` or ``true`` (false if not internal)" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "Zammad Configuration" +#: ../misc/variables/article.rst:1 +msgid "Article Text as HTML (not referenced)" msgstr "" -#: ../settings/security/third-party/facebook.rst:44 -#: ../settings/security/third-party/github.rst:43 -#: ../settings/security/third-party/gitlab.rst:46 -msgid "" -"Now you can link accounts via \"Avatar -> Profile -> Link Accounts\" or " -"login via Zammad login page." +#: ../misc/variables/article.rst:1 +msgid "``#{article.body_as_html}``" msgstr "" -#: ../settings/security/third-party/github.rst:2 -#: ../system/integrations/github.rst:2 -msgid "GitHub" +#: ../misc/variables/article.rst:1 +msgid "``Test`` with formatting" msgstr "" -#: ../settings/security/third-party/github.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via GitHub. To " -"activate the quick login you need to enable OAuth for GitHub." +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "Ticket > Article#" msgstr "" -#: ../settings/security/third-party/github.rst:8 -msgid "Register GitHub App" +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "``#{ticket.article_count}``" msgstr "" -#: ../settings/security/third-party/github.rst:10 -msgid "" -"Visit https://www.github.com/settings/applications/new and enter the app " -"settings. As callback URL enter \"https://zammad_host/auth/github/callback\" " -"where zammad_host has to be replaced with your Zammad FQDN" +#: ../misc/variables/article.rst:1 +msgid "``1`` number of ticket articles" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "Register OAuth app on www.github.com" +#: ../misc/variables/config.rst:2 +msgid "Config" msgstr "" -#: ../settings/security/third-party/github.rst:19 -msgid "Configure Zammad as GitHub App" +#: ../misc/variables/config.rst:6 +msgid "" +"Below you'll find config related variables. These hold useful configuration " +"information that you can use within e.g. triggers to show necessary " +"information to your customer." msgstr "" -#: ../settings/security/third-party/github.rst:21 -msgid "" -"Enter the \"APP ID\" and the \"APP SECRET\" from the GitHub OAUTH " -"Applications Dashboard" +#: ../misc/variables/config.rst:11 +msgid "Config Variables" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub config in Zammad admin interface" +#: ../misc/variables/config.rst:1 +msgid "Config > Fully Qualified Domain Name" msgstr "" -#: ../settings/security/third-party/github.rst:28 -msgid "" -"After you configured the GitHub credentials and activated the login method, " -"you should see a new icon on the login page." +#: ../misc/variables/config.rst:1 +msgid "``#{config.fqdn}``" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub logo on login page" +#: ../misc/variables/config.rst:1 +msgid "``zammad.example.com``" msgstr "" -#: ../settings/security/third-party/github.rst:34 -msgid "" -"If you click on the icon you will be redirected to GitHub and see something " -"similar to this:" +#: ../misc/variables/config.rst:1 +msgid "Config > HTTP type" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub oauth page" +#: ../misc/variables/config.rst:1 +msgid "``#{config.http_type}``" msgstr "" -#: ../settings/security/third-party/github.rst:40 -#: ../settings/security/third-party/gitlab.rst:42 -msgid "" -"When you grant the access you will be redirected to your Zammad instance and " -"logged in as a customer." +#: ../misc/variables/config.rst:1 +msgid "``https`` or ``http``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:2 -msgid "Gitlab" +#: ../misc/variables/config.rst:1 +msgid "Config > Organization" msgstr "" -#: ../settings/security/third-party/gitlab.rst:4 +#: ../misc/variables/config.rst:1 +msgid "``#{config.organization}``" +msgstr "" + +#: ../misc/variables/config.rst:1 msgid "" -"It is possible to create a quick login for your helpdesk via Gitlab. To " -"activate the quick login you need to enable OAuth for Gitlab." +"``Zammad GmbH`` value set in `Branding `_" msgstr "" -#: ../settings/security/third-party/gitlab.rst:8 -msgid "Register Gitlab App" +#: ../misc/variables/config.rst:1 +msgid "Config > Product Name" msgstr "" -#: ../settings/security/third-party/gitlab.rst:10 -msgid "To register an app in Gitlab open your profile and select applications." +#: ../misc/variables/config.rst:1 +msgid "``#{config.product_name}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:12 +#: ../misc/variables/config.rst:1 msgid "" -"As callback URL enter \"https://zammad-fqdn/auth/gitlab/callback\" where " -"zammad-fqdn has to be replaced with your Zammad FQDN" +"``Helpdesk`` value set in `Branding `_" msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Register OAuth app on gitlab instance" +#: ../misc/variables/config.rst:1 +msgid "Config > SystemID" msgstr "" -#: ../settings/security/third-party/gitlab.rst:18 -msgid "Just select *read_user* under scopes as in the screenshot and save it." +#: ../misc/variables/config.rst:1 +msgid "``#{config.system_id}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:21 -msgid "Configure Zammad as Gitlab App" +#: ../misc/variables/config.rst:1 +msgid "``31`` (value between 1 and 99)" msgstr "" -#: ../settings/security/third-party/gitlab.rst:23 -msgid "" -"Enter the \"APP ID\" and the \"APP SECRET\" from the Gitlab OAUTH " -"Applications Dashboard and your Gitlab-URL in the \"SITE\" field." +#: ../misc/variables/config.rst:1 +msgid "Config > Ticket Hook" msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab config in Zammad admin interface" +#: ../misc/variables/config.rst:1 +msgid "``#{config.ticket_hook}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:30 -msgid "" -"After you configured the Gitlab credentials and activated the login method, " -"you should see a new icon on the login page." +#: ../misc/variables/config.rst:1 +msgid "``Ticket#``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab logo on login page" +#: ../misc/variables/current-user.rst:2 +msgid "Current User" msgstr "" -#: ../settings/security/third-party/gitlab.rst:36 +#: ../misc/variables/current-user.rst:6 msgid "" -"If you click on the icon you will be redirected to Gitlab and see something " -"similar to this:" +"Current user variables always return values of the current user that caused " +"e.g. a trigger to run." msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab oauth page" +#: ../misc/variables/current-user.rst:8 +msgid "" +"Due to the above fact, these variables are often not (yet) set or available " +"for usage." msgstr "" -#: ../settings/security/third-party/google.rst:4 +#: ../misc/variables/current-user.rst:10 msgid "" -"With some easy and fast steps, you can enable Zammad to authenticate your " -"users via Google." +"In situations where e.g. schedulers or triggers run, this most likely is " +"nothing you want to use." msgstr "" -#: ../settings/security/third-party/google.rst:8 -msgid "Register a Google App" +#: ../misc/variables/current-user.rst:13 +msgid "Current User Variables" msgstr "" -#: ../settings/security/third-party/google.rst:10 -msgid "" -"First of all, we need to create a new project - you can skip this step if " -"you already have one." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Address" msgstr "" -#: ../settings/security/third-party/google.rst:15 -msgid "" -"Use this link to create a new project: https://console.cloud.google.com/" -"projectcreate" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.address}``" msgstr "" -#: ../settings/security/third-party/google.rst:18 -msgid "" -"Now expand the menu, expand \"APIs & Services\" and select \"Credentials\". " -"Go to the tab \"OAuth consent screen\" first and ensure to fill in the " -"requested information - without doing so you can't create credentials!" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set" msgstr "" -#: ../settings/security/third-party/google.rst:None -msgid "Creating a consent screen" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Avatar" msgstr "" -#: ../settings/security/third-party/google.rst:25 -msgid "" -"After filling in and saving the consent screen information, you can go to " -"the \"Credentials\" tab and create new \"OAuth client ID\"-Credentials." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/google.rst:28 -msgid "" -"Fill in the necessary information as follows and replace ``zammad_host`` " -"with your FQDN:" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "avatar picture with width and height in pixel (e.g. 60,60)" msgstr "" -#: ../settings/security/third-party/google.rst:31 -msgid "**Application type** ``[x] Web application``" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created at" msgstr "" -#: ../settings/security/third-party/google.rst:34 -msgid "**Authorized JavaScript origins** ``https://zammad_host/``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_at}``" msgstr "" -#: ../settings/security/third-party/google.rst:37 -msgid "" -"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" -"callback``" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC``" msgstr "" -#: ../settings/security/third-party/google.rst:None -msgid "Adding a new OAuth client ID" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Address" msgstr "" -#: ../settings/security/third-party/google.rst:43 -msgid "" -"After creating the credentials, go to your Zammad installation and navigate " -"to \"Admin > Security > Third Party Applications\" > Google. Enter your " -"Client ID and Client secret here." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.address}``" msgstr "" -#: ../settings/security/third-party/google.rst:None -msgid "Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Avatar" msgstr "" -#: ../settings/security/third-party/google.rst:50 -msgid "After submitting, the login via Google can be used." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:2 -msgid "Microsoft" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Department" msgstr "" -#: ../settings/security/third-party/microsoft.rst:4 -msgid "" -"Zammad's Microsoft connection allows your users with Microsoft accounts to " -"login. This works for Azure users as well and can be an alternative to :doc:" -"`/system/integrations/ldap/index`." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.department}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:10 -msgid "" -"This documentation part does not cover our :doc:`📧 Microsoft 365 email " -"channel `." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Sales`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screenshot showing Microsoft login button on Zammad login screen." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Email" msgstr "" -#: ../settings/security/third-party/microsoft.rst:30 -#: ../settings/security/third-party/microsoft.rst:53 -msgid "Supported account types:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.email}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:22 -msgid "" -"Please note that Zammad only supports these account types (App dependent):" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``jdoe@customer.tld``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:35 -msgid "Avatars of signing in users:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Fax" msgstr "" -#: ../settings/security/third-party/microsoft.rst:33 -msgid "" -"Zammad currently ignores user avatars. If the user is registered with e.g. " -"Gravatar, Zammad will fetch the avatar from there if enabled. See :doc:" -"`Zammad Image Service ` for more." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.fax}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:38 -msgid "Step 1 - Register a Microsoft App for Zammad" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``004930123464789`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:40 -msgid "" -"Login to the `Microsoft Azure Portal `_ and " -"navigate to App registrations to create a new app. Provide the requested " -"information as follows and register your app." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Firstname" msgstr "" -#: ../settings/security/third-party/microsoft.rst:46 -msgid "Name:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.firstname}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:45 -msgid "" -"Any meaningful name fitting, this name will be displayed to users trying to " -"authenticate with this app." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``John`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:49 -msgid "Choose one of the above mentioned account types (see Limitations)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Lastname" msgstr "" -#: ../settings/security/third-party/microsoft.rst:51 -msgid "" -"The correct account type depends on your use case. If you want to use the " -"authentication internal only, choose the first option. If you're unsure, use " -"the \"Help me choose...\" link." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.lastname}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:58 -msgid "Redirect URI (optional):" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Login" msgstr "" -#: ../settings/security/third-party/microsoft.rst:56 -msgid "" -"Select web and provide your callback URL. The callback URL looks like this: " -"``https://zammad.domain.tld/auth/microsoft_office365/callback``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.login}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to register a Microsoft app" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Mobile" msgstr "" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "Within **API permissions** add the following permissions:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.mobile}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:69 -msgid "``User.Read``" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``0049176123456789`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "Contacts" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Note" msgstr "" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "``Contacts.Read``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.note}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:73 -msgid "" -"You can find these permissions within *Microsoft Graph → Delegated " -"permissions*." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Some note to this user`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to add required API permissions" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Phone" msgstr "" -#: ../settings/security/third-party/microsoft.rst:80 -msgid "" -"Within **Certificates & secrets** create a new client secret. Note down the " -"returned secret **value** for later. **Do not** use the secret ID!" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.phone}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to create a new app secret" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``004930123456789`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:88 -msgid "" -"From **Overview** copy your apps *Application (client) ID*. If you're using " -"a single tenant app, please also copy *Directory (tenant) ID*. You now have " -"all required information for Zammad." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > VIP" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to retreive application client and tenant IDs" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.vip}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:98 -msgid "Step 2 - Add App Credentials to Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Web" msgstr "" -#: ../settings/security/third-party/microsoft.rst:100 -msgid "" -"Navigate to Security > Third-party Applications (Tab) within Zammad's admin " -"settings. Scroll down to the section *Authentication via Microsoft* and fill " -"in the required information." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.web}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:105 -msgid "App ID:" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``https://zammad.org`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:105 -msgid "This is your *Application (client) ID*." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Department" msgstr "" -#: ../settings/security/third-party/microsoft.rst:108 -msgid "App secret:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.department}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:108 -msgid "This is your *client secret* (value)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Email" msgstr "" -#: ../settings/security/third-party/microsoft.rst:113 -msgid "App Tenant ID:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.email}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:111 -msgid "" -"**optional** only required for apps that use account type *Accounts in this " -"organizational directory only (Default Directory only - Single tenant).*" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Fax" msgstr "" -#: ../settings/security/third-party/microsoft.rst:115 -msgid "" -"Apply your settings by pressing submit and activate *Authentication via " -"Microsoft*." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.fax}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "" -"Screencast showing how to add app credentials and activating the\n" -"authentication method" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Firstname" msgstr "" -#: ../settings/security/third-party/saml.rst:2 -msgid "SAML" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.firstname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:4 -msgid "" -"Connect your SAML (Security Assertion Markup Language) identity provider as " -"a single sign-on (SSO) method." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Lastname" msgstr "" -#: ../settings/security/third-party/saml.rst:7 -msgid "" -"SAML is an open standard for SSO authentication (among other things). Sign-" -"ins are shared across multiple **service providers** and managed by a " -"central **identity provider** (IdP)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.lastname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:11 -msgid "" -"In this case, the service provider is Zammad, and the IdP is a software " -"service that you either host or subscribe to (*e.g.,* `Keycloak `_, `Redhat SSO Server `_, `ADFS `_, or `Okta `_)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Login" msgstr "" -#: ../settings/security/third-party/saml.rst:18 -msgid "" -"This guide assumes you are already using SAML within your organization (i." -"e., that your IdP is fully set up)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.login}``" msgstr "" -#: ../settings/security/third-party/saml.rst:21 -msgid "" -"Please note: Our instructions are based on connecting Zammad with Keycloak." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Mobile" msgstr "" -#: ../settings/security/third-party/saml.rst:25 -msgid "Step 1: Configure Your IdP" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.mobile}``" msgstr "" -#: ../settings/security/third-party/saml.rst:28 -msgid "Add Zammad as a Client/App" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Note" msgstr "" -#: ../settings/security/third-party/saml.rst:30 -msgid "" -"Import Zammad into your IdP using the XML configuration found at ``https://" -"your.zammad.domain/auth/saml/metadata``." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.note}``" msgstr "" -#: ../settings/security/third-party/saml.rst:33 -msgid "" -"If your IdP doesn't support XML import, you will have to configure Zammad as " -"a new client/app manually using the above XML metadata file for reference." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Domain based assignment" msgstr "" -#: ../settings/security/third-party/saml.rst:36 -msgid "For instance, when you see this tag:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.domain_assignment}``" msgstr "" -#: ../settings/security/third-party/saml.rst:42 -msgid "" -"Set the **Assertion Consumer Service Binding URL** (sometimes also listed as " -"**Valid Redirect URIs**) to ``http://your.zammad.domain/auth/saml/callback``." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Domain" msgstr "" -#: ../settings/security/third-party/saml.rst:47 -msgid "Set Up User Attribute Mapping" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.domain}``" msgstr "" -#: ../settings/security/third-party/saml.rst:49 -msgid "" -"Zammad requests the following user attributes (or “properties”) from the IdP:" +#: ../misc/variables/current-user.rst:1 +msgid "``zammad.com`` or empty if not set" msgstr "" -#: ../settings/security/third-party/saml.rst:51 -msgid "Email address (``email``)" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Name" msgstr "" -#: ../settings/security/third-party/saml.rst:52 -msgid "Full name (``name``)" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.name}``" msgstr "" -#: ../settings/security/third-party/saml.rst:53 -msgid "Given name (``first_name``)" +#: ../misc/variables/current-user.rst:1 +msgid "``Zammad GmbH``" msgstr "" -#: ../settings/security/third-party/saml.rst:54 -msgid "Family name (``last_name``)" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Note" msgstr "" -#: ../settings/security/third-party/saml.rst:56 -msgid "" -"You may need to set up “mappers” (or “mappings”) to tell your IdP how user " -"attributes in SAML correspond to those in Zammad. For a more detailed " -"breakdown, refer to the XML metadata file referenced in the previous section." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.note}``" msgstr "" -#: ../settings/security/third-party/saml.rst:62 -msgid "Per-IdP Instructions" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``A note to the organization of the user`` or empty if not set" msgstr "" -#: ../settings/security/third-party/saml.rst:102 -msgid "Keycloak" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Shared organization" msgstr "" -#: ../settings/security/third-party/saml.rst:65 -msgid "" -"**To add Zammad as a client,** save the XML configuration to disk (``https://" -"your.zammad.domain/auth/saml/metadata``) and use **Clients > Clients list > " -"Import client** in the Keycloak admin panel." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.shared}``" msgstr "" -#: ../settings/security/third-party/saml.rst:70 -msgid "" -"To help Zammad **match its own user accounts to Keycloak users**, create a " -"user attribute (or “property”) mapper. In **Clients list**, click on your " -"newly created Client ID, choose the tab **Client scopes** and click on the " -"link which refers to your Zammad instance. Choose **Add mapper > By " -"configuration > User Property** and create a mapper with the following " -"entries:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > VIP" msgstr "" -#: ../settings/security/third-party/saml.rst:78 -msgid "**Name**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.vip}``" msgstr "" -#: ../settings/security/third-party/saml.rst:80 -msgid "**Mapper Type**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Phone" msgstr "" -#: ../settings/security/third-party/saml.rst:81 -msgid "``User Property``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.phone}``" msgstr "" -#: ../settings/security/third-party/saml.rst:82 -msgid "**Property**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated at" msgstr "" -#: ../settings/security/third-party/saml.rst:83 -msgid "``emailAddress``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_at}``" msgstr "" -#: ../settings/security/third-party/saml.rst:84 -msgid "**SAML Attribute Name**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Address" msgstr "" -#: ../settings/security/third-party/saml.rst:86 -msgid "**SAML Attribute NameFormat**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.address}``" msgstr "" -#: ../settings/security/third-party/saml.rst:87 -msgid "``basic``" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Avatar" msgstr "" -#: ../settings/security/third-party/saml.rst:89 -msgid "" -"In the example above, we're telling Zammad that whenever it receives a SAML " -"login request, it should take the ``email`` property from Keycloak, look for " -"a Zammad user with the same ``email`` attribute, and create a new session " -"for that user." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/saml.rst:95 -msgid "" -"If your Keycloak users' email addresses are stored on another property (*e." -"g.,* ``username``), adjust accordingly." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Department" msgstr "" -#: ../settings/security/third-party/saml.rst:98 -msgid "" -"Back in **Settings**, enter the Client ID (``https://your.zammad.domain/auth/" -"saml/metadata``) in the field **Master SAML Processing URL**." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.department}``" msgstr "" -#: ../settings/security/third-party/saml.rst:101 -msgid "You also need to enable **Sign assertions**." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Email" msgstr "" -#: ../settings/security/third-party/saml.rst:105 -msgid "Step 2: Configure Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.email}``" msgstr "" -#: ../settings/security/third-party/saml.rst:107 -msgid "" -"Enable SAML and enter your IdP's details in the Admin Panel under **Settings " -"> Security > Third Party Applications > Authentication via SAML**:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Fax" msgstr "" -#: ../settings/security/third-party/saml.rst:None -msgid "Example configuration of SAML part 1" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.fax}``" msgstr "" -#: ../settings/security/third-party/saml.rst:119 -msgid "Display name" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Firstname" msgstr "" -#: ../settings/security/third-party/saml.rst:116 -msgid "" -"Allows you to define a custom button name for SAML. This helps your users to " -"understand better what the button on the login page does." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.firstname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:119 -msgid "Defaults to ``SAML``." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Lastname" msgstr "" -#: ../settings/security/third-party/saml.rst:123 -msgid "IDP SSO target URL" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.lastname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:122 -msgid "" -"This is the target URL Zammad shall redirect to when the user presses the " -"SAML button. For Keycloak, this needs to look like https://your.domain/" -"realms/your-realm/protocol/saml" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Login" msgstr "" -#: ../settings/security/third-party/saml.rst:127 -msgid "IDP single logout target URL" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.login}``" msgstr "" -#: ../settings/security/third-party/saml.rst:126 -msgid "" -"This is the URL to which the single logout request and response should be " -"sent." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Mobile" msgstr "" -#: ../settings/security/third-party/saml.rst:131 -msgid "IDP certificate" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.mobile}``" msgstr "" -#: ../settings/security/third-party/saml.rst:130 -msgid "" -"The public certificate of your IDP for Zammad to verify during the callback " -"phase." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Note" msgstr "" -#: ../settings/security/third-party/saml.rst:145 -msgid "IDP certificate fingerprint" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.note}``" msgstr "" -#: ../settings/security/third-party/saml.rst:134 -msgid "" -"The fingerprint of your IDPs public certificate to verify during callback " -"phase." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Phone" msgstr "" -#: ../settings/security/third-party/saml.rst:137 -msgid "🔏 **For the IdP certificate / certificate fingerprint:**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.phone}``" msgstr "" -#: ../settings/security/third-party/saml.rst:139 -msgid "" -"Provide **only one or the other**—do not provide both! (Between the two, we " -"recommend the signing certificate itself: fingerprints use SHA-1, which `has " -"been broken for a while now `_.)" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > VIP" msgstr "" -#: ../settings/security/third-party/saml.rst:144 -msgid "" -"**Keycloak users:** Find your certificate in the Keycloak admin panel under " -"**Realm Settings > Keys > Algorithm: RS256 > Certificate**." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.vip}``" msgstr "" -#: ../settings/security/third-party/saml.rst:151 -msgid "Name identifier format" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``false`` or ``true``" msgstr "" -#: ../settings/security/third-party/saml.rst:148 -msgid "" -"This is the unique identifiers field type. Usually it should be ``urn:oasis:" -"names:tc:SAML:1.1:nameid-format:emailAddress``." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Web" msgstr "" -#: ../settings/security/third-party/saml.rst:151 -msgid "Zammad **expects an email address as unique identifier**!" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.web}``" msgstr "" -#: ../settings/security/third-party/saml.rst:155 -msgid "UID attribute name" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > VIP" msgstr "" -#: ../settings/security/third-party/saml.rst:154 -msgid "" -"Here you can define an attribute that uniquely identifies the user. If " -"unset, the name identifier returned by the IDP is used." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.vip}``" msgstr "" -#: ../settings/security/third-party/saml.rst:None -msgid "Example configuration of SAML part 2" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Web" msgstr "" -#: ../settings/security/third-party/saml.rst:163 -msgid "" -"Decide if the certificate for the connection to the IdP service has to be " -"verified or not (default: ``yes``)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.web}``" msgstr "" -#: ../settings/security/third-party/saml.rst:169 -msgid "Signing & Encrypting" +#: ../misc/variables/ticket.rst:6 +msgid "" +"Below you can find all available ticket-based variables within Zammad. These " +"can be called via triggers for example. If you're unsure if Zammad does " +"support variables at the point you're at, you can try to type ``::`` to " +"check." msgstr "" -#: ../settings/security/third-party/saml.rst:169 -msgid "" -"Define if you want to sign, encrypt, do both or nothing for the requests." +#: ../misc/variables/ticket.rst:12 +msgid "Ticket Variables" msgstr "" -#: ../settings/security/third-party/saml.rst:179 -msgid "Certificate (PEM)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Accounted Time" msgstr "" -#: ../settings/security/third-party/saml.rst:172 -msgid "" -"Paste the public certificate of your Zammad SAML client, if you want to " -"encrypt the requests." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.time_unit}``" msgstr "" -#: ../settings/security/third-party/saml.rst:175 -msgid "Make sure the certificate is:" +#: ../misc/variables/ticket.rst:1 +msgid "``1``, ``2.75`` or empty response" msgstr "" -#: ../settings/security/third-party/saml.rst:177 -msgid "already valid and not yet expired" +#: ../misc/variables/ticket.rst:1 +msgid "``3``, any number of articles existing in the ticket right now" msgstr "" -#: ../settings/security/third-party/saml.rst:178 -msgid "no CA certificate" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Closing time" msgstr "" -#: ../settings/security/third-party/saml.rst:179 -msgid "valid for signing and encrypting" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.close_at}``" msgstr "" -#: ../settings/security/third-party/saml.rst:185 -msgid "Private key (PEM)" +#: ../misc/variables/ticket.rst:1 +msgid "2019-10-07 17:25:00 UTC" msgstr "" -#: ../settings/security/third-party/saml.rst:182 -msgid "" -"Paste the private key of your Zammad SAML client here, if you want to sign " -"the requests." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created at" msgstr "" -#: ../settings/security/third-party/saml.rst:185 -msgid "Make sure the key is an RSA key with a length of at least 2048 bits." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_at}``" msgstr "" -#: ../settings/security/third-party/saml.rst:188 -msgid "Private key secret" +#: ../misc/variables/ticket.rst:1 +msgid "2019-10-07 16:25:00 UTC" msgstr "" -#: ../settings/security/third-party/saml.rst:188 -msgid "If your private key is secured with a secret, you can provide it here." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Address" msgstr "" -#: ../settings/security/third-party/saml.rst:192 -msgid "Your callback URL" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.address}``" msgstr "" -#: ../settings/security/third-party/saml.rst:191 -msgid "" -"This URL is needed for your IdP configuration so it knows where to redirect " -"to after successful authentication." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Avatar" msgstr "" -#: ../settings/security/third-party/saml.rst:194 -msgid "" -"After saving your input by clicking on the \"Submit\" button, Zammad " -"verifies the provided keys/certificates (e.g. if they are valid for signing/" -"encrypting and if they aren't expired)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/saml.rst:199 -msgid "" -"See :ref:`automatic account linking ` for details " -"on how to link existing Zammad accounts to IdP accounts." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Department" msgstr "" -#: ../settings/security/third-party/saml.rst:205 -msgid "Automatic account linking doesn't work" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.department}``" msgstr "" -#: ../settings/security/third-party/saml.rst:206 -msgid "" -"Have you double-checked your IdP's user attribute mapping configuration?" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Email" msgstr "" -#: ../settings/security/third-party/twitter.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via Twitter. To do " -"so, you need to follow these steps:" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.email}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:8 -msgid "Register Twitter App" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Fax" msgstr "" -#: ../settings/security/third-party/twitter.rst:10 -msgid "Go to https://dev.twitter.com/apps and login with your account." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.fax}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:15 -msgid "Click on \"Create App\"" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Firstname" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "new app page" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.firstname}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:20 -msgid "" -"Enter app settings. As \"Callback URL\" you need to enter ``https://" -"zammad_host/api/v1/external_credentials/twitter/callback``. You need to " -"replace ``zammad_host`` with the domain of your Zammad system." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Lastname" msgstr "" -#: ../settings/security/third-party/twitter.rst:24 -msgid "" -"After the app has been created, update the application icon and organization " -"attributes." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.lastname}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "set permissions to receive and send direct messages" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Login" msgstr "" -#: ../settings/security/third-party/twitter.rst:30 -msgid "" -"Next we need to set ``read, write and access direct messages`` permissions " -"for the app." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.login}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "click on Keys & Access Token, note them" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Mobile" msgstr "" -#: ../settings/security/third-party/twitter.rst:36 -msgid "" -"Go to \"Keys and Access Token\" tab and note the \"Consumer Key\" and " -"\"Consumer Secret\"." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.mobile}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:40 -msgid "Configure Zammad as Twitter App" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Note" msgstr "" -#: ../settings/security/third-party/twitter.rst:42 -msgid "" -"Go to \"Admin > Security > Twitter > Third Party Applications > Twitter\" " -"Section." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.note}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "Admin > Security > Third Party Applications" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Phone" msgstr "" -#: ../settings/security/third-party/twitter.rst:48 -msgid "" -"Fill in the \"Twitter Key\" and the \"Twitter Secret\" and click the " -"\"Submit\" button." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.phone}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:51 -msgid "" -"Now you can link accounts via \"Avatar > Profile > Link Accounts\" or login " -"via Zammad login page." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > VIP" msgstr "" -#: ../settings/security/two-factor.rst:11 -msgid "Two-factor Authentication Methods" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.vip}``" msgstr "" -#: ../settings/security/two-factor.rst:2 -msgid "Two-Factor Authentication" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Web" msgstr "" -#: ../settings/security/two-factor.rst:4 -msgid "" -"Two-factor authentication (2FA) enhances the security of Zammad accounts by " -"adding an extra layer of verification beyond a password. It requires users " -"to provide two different types of authentication factors, typically " -"something they know (like a password) and something they possess (like a " -"mobile device or a security token), to ensure that only authorized " -"individuals can access the account." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.web}``" msgstr "" -#: ../settings/security/two-factor.rst:19 -msgid "Enable Recovery Codes" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Address" msgstr "" -#: ../settings/security/two-factor.rst:21 -msgid "" -"Recovery codes are one-time use security codes that can be used by the user " -"if they lose access to their other two-factor authentication methods. They " -"cannot be used on their own, they can only be activated if at least one two-" -"factor authentication method is enabled." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.address}``" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Enable Recovery Codes Setting" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Avatar" msgstr "" -#: ../settings/security/two-factor.rst:30 -msgid "" -"Recovery codes can only be used as a backup method. If enabled, they will be " -"automatically generated for the user once they set up their initial two-" -"factor authentication method." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.avatar(60,60)}``" msgstr "" -#: ../settings/security/two-factor.rst:34 -msgid "" -"The user will be asked to print out or save the generated recovery codes in " -"a safe place. Once used, a recovery code cannot be reused." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Department" msgstr "" -#: ../settings/security/two-factor.rst:37 -msgid "" -"Users will also have an option to regenerate their recovery codes at any " -"time, which invalidates already existing recovery codes and provides them " -"with a list of fresh codes." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.department}``" msgstr "" -#: ../settings/security/two-factor.rst:41 -msgid "" -"After you enable this setting, when the user completes a setup of their " -"initial two-factor authentication method, they will be presented with a list " -"of recovery codes and instructed to save them for later use." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Email" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Recovery Codes Generation Modal Dialog" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.email}``" msgstr "" -#: ../settings/security/two-factor.rst:50 -msgid "Enforce the Set Up of the Two-Factor Authentication" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Fax" msgstr "" -#: ../settings/security/two-factor.rst:52 -msgid "" -"In case you wish to require your users to set up at least one two-factor " -"authentication method for their account, you can do this by selecting " -"specific user roles the requirement applies to in **Enforced for user " -"roles** setting. Of course you must have at least one two-factor " -"authentication method enabled for this setting to take effect." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.fax}``" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Enforced for User Roles Setting" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Firstname" msgstr "" -#: ../settings/security/two-factor.rst:62 -msgid "" -"After you change this setting, if the user has one of the selected roles on " -"their account, they will be forced to set up the two-factor authentication " -"upon next sign in or application reload." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.firstname}``" msgstr "" -#: ../settings/security/two-factor.rst:66 -msgid "" -"A modal dialog with instructions will be shown, and they will not be able to " -"do any work before they set up at least one two-factor method." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Lastname" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Modal Dialog for Enforcing Two-Factor Authentication Set Up" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.lastname}``" msgstr "" -#: ../settings/security/two-factor.rst:74 -msgid "Reset Two-Factor Authentication for a Specific User" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Login" msgstr "" -#: ../settings/security/two-factor.rst:76 -msgid "" -"In case an user isn't able to login anymore because of an inaccessible " -"second factor, you can reset the user's 2FA method." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.login}``" msgstr "" -#: ../settings/security/two-factor.rst:79 -msgid "" -"To do this, go to the user management and search for the relevant user. " -"After you found the account, click the button in the action column and " -"select \"Manage Two-Factor Authentication\":" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Mobile" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Context menu in action column in user management" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.mobile}``" msgstr "" -#: ../settings/security/two-factor.rst:87 -msgid "" -"After selecting this, you can see a dialog where you can either reset one " -"2FA method or reset all of the user's 2FA methods:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Note" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Dialog for resetting user's 2FA method" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.note}``" msgstr "" -#: ../settings/security/two-factor.rst:94 -msgid "" -"Choose the fitting one, click on the corresponding \"Remove ...\" button and " -"confirm your action. The user now has to setup a new 2FA method, depending " -"on your 2FA configuration." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Phone" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:2 -msgid "Authenticator App" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.phone}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:4 -msgid "" -"The authenticator app method is a type of two-factor authentication that " -"uses a mobile application to generate one-time codes for account " -"verification. After setting up the authenticator app on their device, the " -"user links it to their Zammad account." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > VIP" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:12 -msgid "" -"When logging in, the user is prompted to enter a time-sensitive code " -"generated by the app, in addition to their password. This code acts as the " -"second factor of authentication, providing an extra layer of security as it " -"changes periodically and is unique to the user's device." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.vip}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:None -msgid "Security Code in Google Authenticator App" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Web" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:22 -msgid "" -"The app generates codes based on a shared secret key stored securely on both " -"the user's device and the server, ensuring a synchronized and secure " -"authentication process. The method of generating the codes is sometimes also " -"called TOTP (time-based one-time password)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.web}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:28 -msgid "Enabling the Authenticator App Method" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Escalation at" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:30 -#: ../settings/security/two-factor/security-keys.rst:28 -msgid "To enable the method, just toggle the switch on in the settings." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.escalation_at}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:None -msgid "Authenticator App Switch in Settings" +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:36 -msgid "" -"Now the users will be able to set up this two-factor authentication method " -"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " -"Once they do, on next sign-in with password, they will be asked to provide " -"an additional security code generated by their mobile device." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > First response" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:2 -msgid "Security Keys" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.first_response_at}``" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:4 -msgid "" -"The security keys method is a type of a two-factor authentication that uses " -"Web Authentication API in the browser for verifying user's identity. The " -"user can register multiple hardware or software security keys with their " -"Zammad account and then they can use it during the sign-in process." +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable yet" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:12 -msgid "" -"When logging in, the user is prompted to provide the same security key they " -"registered with their account, in addition to their password. This key acts " -"as the second factor of authentication, providing an extra layer of security." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Assign Follow-Ups" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:None -msgid "Security Key dialog in Safari on macOS" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_assignment}``" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:21 -msgid "" -"The type of the key can range from hardware USB sticks to passkeys stored in " -"a device of user's choice. Which type can be used depends on the browser " -"flavor and the platform of the user." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Assignment Timeout" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:26 -msgid "Enabling the Security Keys Method" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.assignment_timeout}``" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:None -msgid "Security Keys Switch in Settings" +#: ../misc/variables/ticket.rst:1 +msgid "``20`` or empty if not configured" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:34 -msgid "" -"Now the users will be able to set up this two-factor authentication method " -"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " -"Once they do, on next sign-in with password, they will be asked to provide " -"the same security key they registered during the setup." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Follow-up possible" msgstr "" -#: ../settings/system/system-selfhosted.include.rst:3 -msgid "" -"Below settings are only available to self hosted users. In hosted " -"environments we're handling these settings for you to ensure service " -"stability." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_possible}``" msgstr "" -#: ../settings/system/base.rst:11 -msgid "Fully Qualified Domain Name" +#: ../misc/variables/ticket.rst:1 +msgid "``no`` or ``yes``" msgstr "" -#: ../settings/system/base.rst:7 -msgid "The URL of your Zammad installation." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Name" msgstr "" -#: ../settings/system/base.rst:9 ../settings/system/base.rst:17 -msgid "This setting is used within :doc:`/system/variables` and notifications." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.name}``" msgstr "" -#: ../settings/system/system-base.include.rst:1 -msgid "It is automatically set by the *Getting Started wizard*." +#: ../misc/variables/ticket.rst:1 +msgid "``Sales``" msgstr "" -#: ../settings/system/system-base.include.rst:5 -msgid "Changing this setting also changes callback URLs for your channels etc." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Note" msgstr "" -#: ../settings/system/system-base.include.rst:6 -msgid "This setting can have negative affects on being able to login." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.note}``" msgstr "" -#: ../settings/system/base.rst:19 -msgid "HTTP type" +#: ../misc/variables/ticket.rst:1 +msgid "``Note about this group``" msgstr "" -#: ../settings/system/base.rst:14 -msgid "" -"The HTTP type tells your installation how your clients connect. This is " -"relevant for authentication and cookie security." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > ID" msgstr "" -#: ../settings/system/base.rst:31 -msgid "SystemID" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.id}``" msgstr "" -#: ../settings/system/base.rst:22 -msgid "" -"This ID is being used within your ticket number. In case you're " -"communicating with another ticket system with similar ticket number schemes " -"this ID greatly reduces the risk of false follow ups." +#: ../misc/variables/ticket.rst:1 +msgid "``17``, ``5281``, ..." msgstr "" -#: ../settings/system/base.rst:26 -msgid "" -"The SystemID is randomly selected upon installation of Zammad (``1-99``)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact (agent)" msgstr "" -#: ../settings/system/base.rst:30 -msgid "" -"**Do not** change this setting in a productive system! Your Zammad " -"installation may no longer recognize old ticket number based follow ups upon " -"change!" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_agent_at}``" msgstr "" -#: ../settings/system/frontend.rst:2 -msgid "Frontend" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact (customer)" msgstr "" -#: ../settings/system/frontend.rst:22 -msgid "Core Workflow Ajax Mode" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_customer_at}``" msgstr "" -#: ../settings/system/frontend.rst:6 +#: ../misc/variables/ticket.rst:1 msgid "" -"This setting allows administrators to enforce :doc:`/system/core-workflows` " -"to use Ajax-Calls instead of web sockets. You'll usually only need this if " -"you experience serious issues as noted below." +"``2019-10-07 16:25:00 UTC`` or empty if not applicable yet (Please note " +"`Ticket last contact behavior Settings `_ for this)" msgstr "" -#: ../settings/system/frontend.rst:10 -msgid "**🤓 Possible (technical) reasons**" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact" msgstr "" -#: ../settings/system/frontend.rst:12 -msgid "" -"In some cases, your network structure (e.g. firewalls, proxies) may " -"disconnect long web socket connections. This leads to select fields staying " -"empty (e.g. owner selection *after* selecting your group) or fields not " -"shown / hidden (e.g. when switching to or from pending states, the \"pending " -"till\" field not showing / hiding)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_at}``" msgstr "" -#: ../settings/system/frontend.rst:18 -msgid "" -"Please keep in mind that the Ajax fallback may cause serious pressure on " -"your application server. If you have the choice stick to web sockets." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Number" msgstr "" -#: ../settings/system/frontend.rst:22 -msgid "Default: ``no`` (inactive)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.number}``" msgstr "" -#: ../settings/system/frontend.rst:53 -msgid "Show calendar weeks in the picker of date/datetime fields" +#: ../misc/variables/ticket.rst:1 +msgid "``31001``, ``201910731001``, ..." msgstr "" -#: ../settings/system/frontend.rst:25 -msgid "" -"With this setting you can instruct Zammad to provide week number display " -"globally for all users. Calendar with week number display are usually used " -"in business sectors and may not be relevant for everyone." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain based assignment" msgstr "" -#: ../settings/system/frontend.rst:29 -msgid "" -"This setting affects *all areas* - you'll also see week numbers in the admin " -"panel for e.g. triggers and macros." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain_assignment}``" msgstr "" -#: ../settings/system/frontend.rst:32 -msgid "Default: ``no`` (not shown)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain" msgstr "" -#: ../settings/system/frontend.rst:53 -msgid "Here's the difference:" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain}``" msgstr "" -#: ../settings/system/frontend.rst:0 -msgid "Screenshot showing Zammad's date picker (in the default way)" +#: ../misc/variables/ticket.rst:1 +msgid "``domain.tld`` or empty if not set" msgstr "" -#: ../settings/system/frontend.rst:41 -msgid "Set to ``no``" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Name" msgstr "" -#: ../settings/system/frontend.rst:0 -msgid "" -"Screenshot showing Zammad's date picker with\n" -"week numbers enabled" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.name}``" msgstr "" -#: ../settings/system/frontend.rst:50 -msgid "Set to ``yes``" +#: ../misc/variables/ticket.rst:1 +msgid "``Zammad GmbH`` or empty if not set" msgstr "" -#: ../settings/system/index.rst:4 -msgid "" -"For your overview we split each tab within system settings into its own page:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Note" msgstr "" -#: ../settings/system/index.rst:16 -msgid "Console Based Settings" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.note}``" msgstr "" -#: ../settings/system/index.rst:18 -msgid "" -"There's some console based settings we didn't put into the UI. However, you " -"may find them helpful - you can find them in our :docs:`hidden settings ` section." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Shared organization" msgstr "" -#: ../settings/system/network.rst:2 -msgid "Network" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.shared}``" msgstr "" -#: ../settings/system/network.rst:8 -msgid "" -"The proxy settings can only be saved after successfully testing the proxy " -"connection." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > VIP" msgstr "" -#: ../settings/system/network.rst:15 -msgid "Proxy Address." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.vip}``" msgstr "" -#: ../settings/system/network.rst:12 -msgid "" -"Allows you to provide a proxy server if needed. This is relevant for network " -"communication by Zammad." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Address" msgstr "" -#: ../settings/system/network.rst:15 -msgid "It **does not** affect the update process or Elasticsearch." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.address}``" msgstr "" -#: ../settings/system/network.rst:18 -msgid "Username for proxy connection." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Avatar" msgstr "" -#: ../settings/system/network.rst:18 -msgid "" -"If your proxy server requires authentication, provide the username here." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.avatar(60,60)}``" msgstr "" -#: ../settings/system/network.rst:21 -msgid "Password for proxy connection." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Department" msgstr "" -#: ../settings/system/network.rst:21 -msgid "" -"If your proxy server requires authentication, provide the password here." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.department}``" msgstr "" -#: ../settings/system/network.rst:26 -msgid "No proxy for the following hosts." +#: ../misc/variables/ticket.rst:1 +msgid "``Support`` or empty if not set" msgstr "" -#: ../settings/system/network.rst:24 -msgid "" -"Exception list for hosts you can't or don't want to reach via proxy server." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Email" msgstr "" -#: ../settings/system/network.rst:27 -msgid "Default: ``localhost,127.0.0.0,::1``" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.email}``" msgstr "" -#: ../settings/system/services.rst:2 -msgid "Services" +#: ../misc/variables/ticket.rst:1 +msgid "``agent@company.tld`` or empty if not set" msgstr "" -#: ../settings/system/services.rst:10 -msgid "Image Service" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Fax" msgstr "" -#: ../settings/system/services.rst:5 -msgid "Defines the backend for user and organization image lookups." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.fax}``" msgstr "" -#: ../settings/system/services.rst:7 -msgid "Default: ``Zammad Image Service`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Firstname" msgstr "" -#: ../settings/system/services.rst:9 -msgid "" -"Make sure your on premise installation has ``HTTPS`` access to ``images." -"zammad.com``." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.firstname}``" msgstr "" -#: ../settings/system/services.rst:18 -msgid "Geo Calendar Service" +#: ../misc/variables/ticket.rst:1 +msgid "``Max`` or empty if not set" msgstr "" -#: ../settings/system/services.rst:13 -msgid "" -"Defines the backend for geo calendar lookups. Used for initial calendar " -"setup." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Lastname" msgstr "" -#: ../settings/system/services.rst:16 -msgid "Default: ``Zammad GeoCalendar Service`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.lastname}``" msgstr "" -#: ../settings/system/services.include.rst:2 -msgid "" -"Make sure your on premise installation has ``HTTPS`` access to ``geo.zammad." -"com``." +#: ../misc/variables/ticket.rst:1 +msgid "``Mustermann`` or empty if not set" msgstr "" -#: ../settings/system/services.rst:26 -msgid "Geo IP Service" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Login" msgstr "" -#: ../settings/system/services.rst:21 -msgid "" -"Defines the backend for geo IP lookups. Shows also location of an IP address " -"if an IP address is shown." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.login}``" msgstr "" -#: ../settings/system/services.rst:24 -msgid "Default: ``Zammad GeoIP Service`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "``agent``" msgstr "" -#: ../settings/system/services.rst:32 -msgid "Geo Location Service" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Mobile" msgstr "" -#: ../settings/system/services.rst:29 -msgid "" -"Defines the backend for geo location lookups to store geo locations for " -"addresses." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.mobile}``" msgstr "" -#: ../settings/system/services.rst:32 -msgid "" -"Default: ``OpenStreetMap (ODbL 1.0, http://osm.org/copyright)`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Note" msgstr "" -#: ../settings/system/services.rst:36 -msgid "" -"You can find a detailed privacy information on what we store for how long on " -"our :docs:`Privacy Appendix ` inside of our System " -"Documentation." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.note}``" msgstr "" -#: ../settings/system/storage.rst:2 -msgid "Storage" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Phone" msgstr "" -#: ../settings/system/storage.rst:6 -msgid "" -"Here you can define where Zammad stores attachments for tickets and the " -"knowledge base. By default, we're writing to the ``Database`` - you can " -"switch to ``Filesystem`` or ``Simple Storage (S3)`` at any time. In this " -"case please have a look on the following instructions." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.phone}``" msgstr "" -#: ../settings/system/storage.rst:11 -msgid "" -"If you have a busy Zammad instance, we strongly encourage you to use " -"filesystem storage instead of \"Database\". This will greatly improve system " -"performance (de-crease database load and size)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > VIP" msgstr "" -#: ../settings/system/storage.rst:19 -msgid "Database" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.vip}``" msgstr "" -#: ../settings/system/storage.rst:17 -msgid "" -"This is the default storage method. The attachments are stored directly in " -"the database. If your Zammad instance grows, we recommend one of the other " -"methods to maintain performance." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Web" msgstr "" -#: ../settings/system/storage.rst:38 -msgid "Filesystem" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.web}``" msgstr "" -#: ../settings/system/storage.rst:22 -msgid "" -"This storage method is recommended for all Zammad instances, especially for " -"those with a higher load. If you choose filesystem, your files are written " -"to ``/opt/zammad/storage/``." +#: ../misc/variables/ticket.rst:1 +msgid "``https://zammad.com`` or empty if not set" msgstr "" -#: ../settings/system/storage.rst:26 -msgid "" -"Moving attachments from \"Database\" to \"Filesystem\" can be run during " -"production use. However, you should consider your framework conditions (e.g. " -"bandwidth, system load in production) to define the right moment." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Pending till" msgstr "" -#: ../settings/system/storage.rst:32 -msgid "**You noticed slow updates of Zammad?**" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.pending_time}``" msgstr "" -#: ../settings/system/storage.rst:34 -msgid "" -"While Zammad is beeing updated, it enforces a recursive \"change " -"owner\" (chown) for this directory. For instances with many files this can " -"be time consuming. To mitigate that you can move your files and create a " -"symlink in ``/opt/zammad/storage/`` to the new directory. Of course you have " -"to make sure on your own that the permissions are always correct." +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not set" msgstr "" -#: ../settings/system/storage.rst:95 -msgid "Simple Storage (S3)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Priority > Name" msgstr "" -#: ../settings/system/storage.rst:41 -msgid "" -"To use the Simple Storage (S3), you have to provide some settings, which " -"can't be accessed in the UI (see instructions below)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.priority.name}``" msgstr "" -#: ../settings/system/storage.rst:44 -msgid "" -"⚠️ Please note that the current implementation is in its early stages and can " -"be modified in the future." +#: ../misc/variables/ticket.rst:1 +msgid "``2 normal``" msgstr "" -#: ../settings/system/storage.rst:47 -msgid "" -"The prerequisite is to have access to a S3-compatible storage and to have " -"all necessary parameters available (which depends on your storage provider; " -"if in doubt, please ask there for help)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > State > Name" msgstr "" -#: ../settings/system/storage.rst:51 -msgid "Steps to configure S3:" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.state.name}``" msgstr "" -#: ../settings/system/storage.rst:53 -msgid "" -"Copy ``config/zammad/storage.yml.dist`` to ``config/zammad/storage.yml``" +#: ../misc/variables/ticket.rst:1 +msgid "``new``, ``open``, ..." msgstr "" -#: ../settings/system/storage.rst:54 -msgid "Edit the copied file in one of the following ways:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Tags" msgstr "" -#: ../settings/system/storage.rst:56 -msgid "" -"Either provide your S3 configuration with one attribute per line like in the " -"upper area of the file" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.tags}``" msgstr "" -#: ../settings/system/storage.rst:58 +#: ../misc/variables/ticket.rst:1 msgid "" -"Or provide your S3 configuration as an URL (which you can find at the end of " -"the file). Note: you can also provide this URL as environment variable (:" -"docs:`see system documentation `) without using this yml-file." +"Currently not available, see `Issue 2769 `_" msgstr "" -#: ../settings/system/storage.rst:62 -msgid "" -"We recommend the deletion of the not used configuration style to avoid " -"inconsistencies." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Title" msgstr "" -#: ../settings/system/storage.rst:65 -msgid "Restart Zammad so the config file / environment variable is loaded" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.title}``" msgstr "" -#: ../settings/system/storage.rst:66 +#: ../misc/variables/ticket.rst:1 msgid "" -"Set the \"Storage Method\" in Zammad to ``Simple Storage (S3)`` in Settings " -"> System > Storage and click on \"Submit\". After that, Zammad checks your " -"configuration and the connection to the service and will raise an error " -"message if something is wrong." +"``My amazing Subject`` (normally subject, can be edited within Interface and " +"thus differ)" msgstr "" -#: ../settings/system/storage.rst:72 -msgid "A very simple storage configuration could look like this:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated at" msgstr "" -#: ../settings/system/storage.rst:85 -msgid "" -"Before setting the storage method to ``Simple Storage (S3)`` (step 4), " -"please make sure to have a working setup." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_at}``" msgstr "" -#: ../settings/system/storage.rst:88 -msgid "" -"You can verify this by running ``rails r 'Rails.logger = Logger.new(STDOUT); " -"pp Store::Provider::S3.ping?'`` in your Zammad directory. If everything is " -"fine, you should see ``true``, else you should see ``false`` and a simple " -"error message." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Address" msgstr "" -#: ../settings/system/storage.rst:93 -msgid "" -"If you installed Zammad through a package manager (rather than from source), " -"replace ``rails r`` with ``zammad run rails r`` above. To learn more, see :" -"docs:`Administration via Console `." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.address}``" msgstr "" -#: ../settings/ticket.rst:4 -msgid "" -"Here you can adjust general ticket settings. Additional ones for the ticket " -"composer interface can be found in the :doc:`/misc/composer`." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Avatar" msgstr "" -#: ../settings/ticket.rst:11 -msgid "Ticket Hook (default: ``Ticket#``)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.avatar(60,60)}``" msgstr "" -#: ../settings/ticket.rst:11 -msgid "The identifier for a ticket; *e.g.,* Ticket#, Call#, MyTicket#." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Department" msgstr "" -#: ../settings/ticket.rst:38 -msgid "Ticket Hook Position (default: ``right``)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.department}``" msgstr "" -#: ../settings/ticket.rst:14 -msgid "" -"With this setting you can decide (if) where to insert the ticket number." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Email" msgstr "" -#: ../settings/ticket.rst:20 -msgid "*Right*" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.email}``" msgstr "" -#: ../settings/ticket.rst:17 -msgid "" -"This setting will add the ticket reference on the right site of the subject." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Fax" msgstr "" -#: ../settings/ticket.rst:20 -msgid "Example: ``Some Subject [Ticket#12345]``" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.fax}``" msgstr "" -#: ../settings/ticket.rst:26 -msgid "*Left*" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Firstname" msgstr "" -#: ../settings/ticket.rst:23 -msgid "" -"This setting will add the ticket reference on the left site of the subject." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.firstname}``" msgstr "" -#: ../settings/ticket.rst:26 -msgid "Example: ``[Ticket#12345] Some Subject``" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Lastname" msgstr "" -#: ../settings/ticket.rst:29 -msgid "*None*" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.lastname}``" msgstr "" -#: ../settings/ticket.rst:29 -msgid "This will completely remove ticket references from the subject." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Login" msgstr "" -#: ../settings/ticket.rst:33 -msgid "" -"Please ensure to take a look at :doc:`/channels/email/settings` within the " -"email channel to ensure you have at least one reference that helps Zammad to " -"assign follow-ups correctly." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.login}``" msgstr "" -#: ../settings/ticket.rst:37 -msgid "" -"Disabling this and not setting up any further follow up search will lead to " -"unexpected results!" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Mobile" msgstr "" -#: ../settings/ticket.rst:65 -msgid "" -"Ticket Last Contact Behaviour (default: ``Use the start time of the last " -"customer thread (which may consist of multiple articles).``)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.mobile}``" msgstr "" -#: ../settings/ticket.rst:41 -msgid "" -"This setting changes the way Zammad updates the ``Last Contact`` value of a " -"ticket. This is fairly important for overviews and what you expect upon " -"ticket updates of a customer." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Note" msgstr "" -#: ../settings/ticket.rst:52 -msgid "" -"Use the start time of the last customer thread (which may consist of " -"multiple articles)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.note}``" msgstr "" -#: ../settings/ticket.rst:46 -msgid "" -"If this option is chosen, Zammad will update the last updated value just " -"once if a customer replies. After that, Zammad will wait for an agent to " -"react." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Phone" msgstr "" -#: ../settings/ticket.rst:50 -msgid "" -"This comes in handy if you want to work tickets in the order of their first " -"update. This will not change ticket orders if customers decide to \"bump\" " -"the ticket affected." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.phone}``" msgstr "" -#: ../settings/ticket.rst:57 -msgid "Use the time of the very last customer article." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > VIP" msgstr "" -#: ../settings/ticket.rst:55 -msgid "" -"When setting this option, Zammad will always update the last updated value. " -"This means that if ordering by ``Last Update``, ticket orders will change if " -"customers \"bump\" the ticket." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.vip}``" msgstr "" -#: ../settings/ticket.rst:64 -msgid "Last contact value used on :doc:`/manage/overviews`" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Web" msgstr "" -#: ../settings/ticket.rst:65 -msgid "Last contact value used on :doc:`/manage/trigger`" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.web}``" msgstr "" -#: ../settings/ticket.rst:88 -msgid "" -"Ticket Organization Reassignment (default: ``Update the most recent tickets." -"``)" +#: ../settings/branding.rst:10 +msgid "Product Name" msgstr "" -#: ../settings/ticket.rst:68 +#: ../settings/branding.rst:7 msgid "" -"This setting changes the way Zammad updates the organization field of the " -"tickets whenever the primary organization of a user is changed." -msgstr "" - -#: ../settings/ticket.rst:74 -msgid "Update the most recent tickets." +"Defines the name of the application, shown in the web interface, tabs and " +"title bar of the web browser." msgstr "" -#: ../settings/ticket.rst:72 -msgid "" -"If this option is chosen, Zammad will update the 100 most recent tickets " -"where the user is the ticket customer. The ticket organization field will be " -"automatically set to the new primary organization of the user." +#: ../settings/branding.rst:10 +msgid "Default value: ``Zammad Helpdesk``" msgstr "" -#: ../settings/ticket.rst:88 -msgid "Do not update any tickets." +#: ../settings/branding.rst:13 +msgid "Will be shown in the app and is included in email footers." msgstr "" -#: ../settings/ticket.rst:77 -msgid "" -"When choosing this option, Zammad will not update any tickets when the " -"user's primary organization is changed." +#: ../settings/branding.rst:19 +msgid "Logo" msgstr "" -#: ../settings/ticket.rst:80 -msgid "**Use with care!**" +#: ../settings/branding.rst:16 +msgid "Defines the logo of the application, shown in the login page of Zammad." msgstr "" -#: ../settings/ticket.rst:82 +#: ../settings/branding.rst:18 msgid "" -"Using this option may lead to inconsistencies in the system as the ticket " -"organization may become decoupled from the ticket customer." +"Ensure to hit the \"Submit\" button after uploading the logo. Otherwise your " +"change will not be saved." msgstr "" -#: ../settings/ticket.rst:85 +#: ../settings/branding.rst:22 msgid "" -"However, you may use this option if you wish to maintain :ref:`the shared " -"access ` to the ticket for all organization " -"members of the original organization of the customer." +"Allows to set the default language of the Zammad instance. The here defined " +"locale mostly acts as a fallback for:" msgstr "" -#: ../settings/ticket.rst:110 -msgid "Ticket Number Format (default: ``Increment (SystemID.Counter)``)" +#: ../settings/branding.rst:25 +msgid "user preferences (if Zammad can't detect the users locale)" msgstr "" -#: ../settings/ticket.rst:94 -msgid "" -"This setting defines the way Zammad's ticket number will look. Changing this " -"setting in production will cause follow up detection to fail." +#: ../settings/branding.rst:26 +msgid "CSV output (reporting, time accounting)" msgstr "" -#: ../settings/ticket.rst:102 -msgid "Increment (SystemID.Counter)" +#: ../settings/branding.rst:30 +msgid "Define the timezone of your Zammad installation." msgstr "" -#: ../settings/ticket.rst:98 +#: ../settings/branding.rst:32 msgid "" -"The increment value contains the SystemID (automatically generated during " -"installation) and a increment which counts up with every new Ticket. The " -"increment will automatically get another digit if needed." +"This does not have any effect on timings for your agents or how Zammad " +"stores date and time values." msgstr "" -#: ../settings/ticket.rst:102 -msgid "Examples: ``1010138``, ``1010139``" +#: ../settings/branding.rst:35 +msgid "Changing this value has direct consequences on the following areas:" msgstr "" -#: ../settings/ticket.rst:110 -msgid "Date (Year.Month.Day.SystemID.Counter)" +#: ../settings/branding.rst:37 +msgid ":doc:`/manage/scheduler` tasks" msgstr "" -#: ../settings/ticket.rst:105 -msgid "" -"This version of the ticket number is fairly long. However, because it " -"contains the date of ticket creation, it also allows you to see when the " -"ticket has been created. You may feel familiar with this number format if " -"you've worked with OTRS already." +#: ../settings/branding.rst:38 +msgid "search indexing (and thus reporting)" msgstr "" -#: ../settings/ticket.rst:110 -msgid "Examples: ``201206231010138``, ``201206231010139``" +#: ../settings/branding.rst:40 +msgid "calendar subscriptions" msgstr "" -#: ../settings/ticket.rst:137 -msgid "OPTIONS" +#: ../settings/branding.rst:41 +msgid "browser printing" msgstr "" -#: ../settings/ticket.rst:113 +#: ../settings/branding.rst:43 msgid "" -"The below options allow you to further customize your ticket number. The " -"availability of options differ depending of the chosen ticket number format " -"above." +"Please note that some of above are fallbacks in case Zammad could not detect " +"the agents timezone correctly." msgstr "" -#: ../settings/ticket.rst:122 -msgid "Checksum (default: ``no``)" +#: ../settings/branding.rst:77 +msgid "Pretty Date" msgstr "" -#: ../settings/ticket.rst:118 +#: ../settings/branding.rst:47 msgid "" -"If set to yes, we'll built a checksum to further \"unique\" the ticket " -"number of your system. If you're dealing with many other ticket systems this " -"might help to prevent false positive follow up detection on tickets." +"This setting allows you to define how Zammad should display time stamps " +"within the interface to all users." msgstr "" -#: ../settings/ticket.rst:122 -msgid "This will also add another digit to the ticket number." +#: ../settings/branding.rst:50 +msgid "" +"This does not have any effect on how Zammad returns e.g. time values via " +"variables." msgstr "" -#: ../settings/ticket.rst:137 -msgid "Min. size of Number (default: ``5``)" +#: ../settings/branding.rst:77 +msgid "Choose in between the following options:" msgstr "" -#: ../settings/ticket.rst:125 -msgid "" -"This setting defines the minimum length of your ticket number. If your " -"counter is not yet high enough, Zammad will fill the number with zeros to " -"ensure the wanted length." +#: ../settings/branding.rst:64 +msgid "relative" msgstr "" -#: ../settings/ticket.rst:129 +#: ../settings/branding.rst:55 msgid "" -"Please note that the minimum length is ``3`` (SystemID + at least one digit " -"if below 10). Also, if the length is no longer long enough, the number will " -"automatically get one digit longer. Ticket-Numbers **do not overflow**, thus " -"it's save to keep it at 5 or set it lower if wanted." +"This timestamp shows a relative time span until it switches to a date. Over " +"time, it will change as follows:" msgstr "" -#: ../settings/ticket.rst:135 -msgid "" -"This option is only available if ticket number format is set to " -"``Increment``!" +#: ../settings/branding.rst:58 +msgid "just now" msgstr "" -#: ../settings/ticket.rst:142 -msgid "Auto-Assignment" +#: ../settings/branding.rst:59 +msgid "5 minutes ago" msgstr "" -#: ../settings/ticket.rst:144 -msgid "" -"In a larger Zammad environment, it happens that several agents open the same " -"ticket at the same time. Although collision detection is then effective, the " -"efficiency of processing can be increased by means of the automatic " -"assignment of tickets when a ticket is opened." +#: ../settings/branding.rst:60 +msgid "3 days 1 hour ago" msgstr "" -#: ../settings/ticket.rst:149 -msgid "" -"The automatic assignment of tickets can be activated and configured in the " -"admin area under Settings > Ticket > Auto Assignment." +#: ../settings/branding.rst:61 +msgid "``03/04/2022``" msgstr "" -#: ../settings/ticket.rst:152 -msgid "" -"The auto assignment only works if the ticket has no owner yet. By default, " -"the agent can always reset the ticket owner to ``-`` if needed." +#: ../settings/branding.rst:63 +msgid "Hovering the timestamp helps, you'll always get a clean timestamp then." msgstr "" -#: ../settings/ticket.rst:155 -msgid "" -"If you want to use this function for only specific tickets, you can " -"configure the conditions accordingly to meet your requirement. By default " -"the condition affects all tickets with the state ``open``." +#: ../settings/branding.rst:71 +msgid "absolute" msgstr "" -#: ../settings/ticket.rst:161 +#: ../settings/branding.rst:67 msgid "" -"If you need to exclude users (e.g. a group leader), you can search and " -"select the desired agents in the ``Exception Users`` list. The search " -"function in this area is only effective, if you have too many agents to " -"display at once to help you with the configuration." +"This timestamp always includes the week day. For one week after creation, " +"the timestamp will not contain the date itself: Thursday 18:35." msgstr "" -#: ../settings/ticket.rst:167 -msgid "Notifications" +#: ../settings/branding.rst:71 +msgid "After a week it will switch to: ``Friday 4. Mar 16:00``." msgstr "" -#: ../settings/ticket.rst:191 -msgid "Default Notifications" +#: ../settings/branding.rst:76 +msgid "timestamp" msgstr "" -#: ../settings/ticket.rst:170 +#: ../settings/branding.rst:74 msgid "" -"This setting allows you to configure the default ticket notifications that " -"will be applied to all new agent users (incl. users who were just assigned " -"agent role). Simply change the notification matrix to desired state and " -"press **Save**." +"This will cause Zammad to show a complete timestamp according to your locale " +"defaults. For English this could be e.g. ``2022/12/03 2:40 pm`` or for " +"German e.g. ``12.03.2022 14:40``." msgstr "" -#: ../settings/ticket.rst:175 -msgid "" -"In case an agent already exists, their ticket notification preferences will " -"be preserved. Optionally, you can also **Apply current defaults to all " -"agents**." +#: ../settings/branding.rst:78 +msgid "Default setting: ``relative``." msgstr "" -#: ../settings/ticket.rst:181 -msgid "" -"**Potential time-consuming action:** Applying default ticket notifications " -"to all agent users may take some time to complete, be patient! The exact " -"time will depend on the size of your system and the number of agents." +#: ../settings/security.rst:2 +msgid "Security" msgstr "" -#: ../settings/ticket.rst:185 +#: ../settings/security.rst:4 msgid "" -"**Active agents only!** When current default ticket notifications are " -"applied, only active agent users are considered. In case an agent is re-" -"activated *after* this action, they will still have the old notification " -"configuration." +"For your overview we split each tab within security settings into its own " +"page:" msgstr "" -#: ../settings/ticket.rst:190 +#: ../settings/security/base.rst:2 ../settings/system/base.rst:2 +#: ../settings/ticket.rst:8 +msgid "Base" +msgstr "" + +#: ../settings/security/base.rst:5 +msgid "New User Accounts" +msgstr "" + +#: ../settings/security/base.rst:9 msgid "" -"In case you want to go back to the initial state of ticket notifications, " -"you can click on **Reset to default** button." +"Activates the `register as a new customer` function on the login page. If " +"set to ``no`` only administrators or agents can create new accounts manually." msgstr "" -#: ../settings/ticket.rst:194 ../settings/ticket.rst:196 -msgid "Duplicate Detection" +#: ../settings/security/base.rst:13 ../settings/security/base.rst:38 +#: ../settings/security/base.rst:66 +msgid "Default setting: ``yes``" msgstr "" -#: ../settings/ticket.rst:236 ../settings/ticket.rst:238 -msgid "Detect Duplicate Ticket Creation" +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"New User Accounts\" setting" msgstr "" -#: ../settings/ticket.rst:197 ../settings/ticket.rst:199 +#: ../settings/security/base.rst:22 msgid "" -"This setting turns on the duplicate ticket detection mechanism during ticket " -"creation. If similar tickets are found in the system, a suitable warning " -"will be shown to the user trying to create a ticket." +"Deactivation of above function **does not** deactivate automatic account " +"creation! This means: If a user writes e.g. an email to Zammad and has no " +"account yet, Zammad will automatically create the account. User accounts are " +"a direct dependency of tickets and thus technically mandatory." msgstr "" -#: ../settings/ticket.rst:204 ../settings/ticket.rst:206 -msgid "A Sample Duplicate Ticket Warning" +#: ../settings/security/base.rst:29 +msgid "Lost Password" msgstr "" -#: ../settings/ticket.rst:206 ../settings/ticket.rst:208 +#: ../settings/security/base.rst:33 msgid "" -"You can choose which ticket attributes will be matched by selecting them in " -"**Attributes to compare** field. Only if the ticket attribute value provided " -"by the user in the ticket create form is *equal* with the attribute in an " -"existing ticket, the warning will be shown." +"Activates the `lost password` function on the login page. If set to ``no`` " +"only administrators may change the user's password - users may update their " +"own password if they're still logged in and they have the required :doc:" +"`permission `." msgstr "" -#: ../settings/ticket.rst:211 ../settings/ticket.rst:213 -msgid "**Warning title** and **Warning message** are configurable as well." +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"Lost Password\" setting" msgstr "" -#: ../settings/ticket.rst:213 ../settings/ticket.rst:215 +#: ../settings/security/base.rst:49 msgid "" -"You can limit the detection only to certain user roles. By default, only " -"agents will see the warning." +"With third party authentications - but especially LDAP - you may want to " +"disable this function. Zammad **will not** change third party login " +"passwords and instead set or change the local password!" msgstr "" -#: ../settings/ticket.rst:216 ../settings/ticket.rst:218 -msgid "" -"If you don't want to show the matched tickets as part of the warning, you " -"can set **Show matching ticket(s) in the warning** setting to *no*." +#: ../settings/security/base.rst:56 +msgid "Password Login" msgstr "" -#: ../settings/ticket.rst:219 ../settings/ticket.rst:221 +#: ../settings/security/base.rst:60 msgid "" -"By default, **Permission level for looking up ticket** is set to *User*, " -"which means user permissions will be honored during sarch. The user will " -"see the warning only if tickets they have access to are matched. " -"Alternatively, you can set this setting to *System*, in which case the " -"search will happen within *all* tickets in the system, regardless of user " -"permissions." +"Activates the username & password login by default and if no third-party " +"login is activated. Disabling password login on the Zammad login page only " +"takes effect if you enable any :doc:`third-party`." msgstr "" -#: ../settings/ticket.rst:225 ../settings/ticket.rst:227 -msgid "**🦺 Safety first!**" +#: ../settings/security/base.rst:64 +msgid "See :doc:`third-party` for supported third-party logins." msgstr "" -#: ../settings/ticket.rst:227 ../settings/ticket.rst:229 -msgid "" -"Even if the permission level is set to *System*, the user will not be shown " -"the tickets they don't have access to in the warning, even if they match." +#: ../settings/security/base.rst:0 +msgid "Figure showing de-activated \"Password Login\" setting" msgstr "" -#: ../settings/ticket.rst:231 ../settings/ticket.rst:233 +#: ../settings/security/base.rst:77 msgid "" -"However, just the confirmation about the existence of the tickets in the " -"system may be considered an unwanted information disclosure. Use this option " -"carefully!" +"To help administrators to overcome \"login issues\", Zammad automatically " +"offers a password request for administrator users. This allows you to adjust " +"Third-Party applications even if the login does no longer work!" msgstr "" -#: ../settings/ticket.rst:235 ../settings/ticket.rst:237 -msgid "" -"Finally, you can configure between matching within **All tickets** or **Open " -"tickets** only by setting **Match tickets in following states**. Depending " -"on the current ticket state, a ticket may or not be matched." +#: ../settings/security/base.rst:84 +msgid "Session Timeout" msgstr "" -#: ../system/core-workflows.rst:2 -msgid "Core Workflows" +#: ../settings/security/base.rst:86 +msgid "" +"All settings below by default are set to ``4 weeks``. Session Timeout " +"defines the life time of a users session. As soon as it's reached, Zammad " +"will automatically log off the session in question." msgstr "" -#: ../system/core-workflows.rst:4 +#: ../settings/security/base.rst:91 msgid "" -"Core Workflows allow you to adjust object attributes in many ways. For " -"example:" +"Zammad takes the highest value set assigned for the user based on the " +"permissions." msgstr "" -#: ../system/core-workflows.rst:7 -msgid "show / hide fields" +#: ../settings/security/base.rst:94 +msgid "``admin``" msgstr "" -#: ../system/core-workflows.rst:8 -msgid "adjust mandatory setting" +#: ../settings/security/base.rst:96 +msgid "``ticket.customer``" msgstr "" -#: ../system/core-workflows.rst:9 -msgid "manipulate available options" +#: ../settings/security/base.rst:97 +msgid "``default`` (fallback if user doesn't have above permissions set)" msgstr "" -#: ../system/core-workflows.rst:11 +#: ../settings/security/base.rst:99 msgid "" -"With this, you can provide exactly the information your users really need!" +"All settings act independently from each other allowing you to disable the " +"timeouts for e.g. admins, but not agents." msgstr "" -#: ../system/core-workflows.rst:15 -msgid "" -"If the pre-defined :doc:`/system/objects` are not enough, please add them " -"beforehand." +#: ../settings/security/base.rst:115 +#: ../system/integrations/checkmk/api-reference.rst:13 +msgid "Example" msgstr "" -#: ../system/core-workflows.rst:17 -msgid "" -"If you experience slow or unreliable field updates, please see :ref:`Core " -"Workflow Ajax Modus `" +#: ../settings/security/base.rst:107 +msgid "Let's suppose you configured the following session timeouts" msgstr "" -#: ../system/core-workflows.rst:22 -msgid "" -"This is a very enhanced functionality and can cause unexpected UI behavior. " -"Please ensure to test your use cases after configuration to reduce surprises." +#: ../settings/security/base.rst:104 +msgid "default: 3 weeks" msgstr "" -#: ../system/core-workflows.rst:None -msgid "Dialogue for adding a new workflow" +#: ../settings/security/base.rst:105 +msgid "admin: 2 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:2 -msgid "Core Workflow Condition Operators" +#: ../settings/security/base.rst:106 +msgid "ticket.agent: 4 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:4 -msgid "" -"You might know that there is a separate section for explaining :doc:" -"`condition operators `. Head over there to " -"see a detailed explanation of many conditions and operators." +#: ../settings/security/base.rst:107 +msgid "ticket.customer: 1 week" msgstr "" -#: ../system/core-workflows/condition-operators.rst:8 -msgid "" -"Due to differences to other places in Zammad which are also using conditions " -"(e.g. triggers), you can find a dedicated description of operators for core " -"workflows below." +#: ../settings/security/base.rst:115 +msgid "This results in the following situations" msgstr "" -#: ../system/core-workflows/condition-operators.rst:12 -msgid "" -"Be aware that the availability of the operators depends on the selected " -"attribute and its field type. Some of the operators may only be available " -"for system attributes (e.g. for \"tags\", \"active\")." +#: ../settings/security/base.rst:110 +msgid "a user with ``admin`` permission will have a timeout of 2 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:20 -msgid "Operator" +#: ../settings/security/base.rst:111 +msgid "" +"a user with ``admin`` and ``ticket.agent`` permissions will have a timeout " +"of 2 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:22 -msgid "after (absolute)" +#: ../settings/security/base.rst:113 +msgid "" +"a user with ``ticket.customer`` permission will have a timeout of 1 week" msgstr "" -#: ../system/core-workflows/condition-operators.rst:23 -msgid "Matches if a date/time is after a specific point in time." +#: ../settings/security/base.rst:115 +msgid "" +"a user with neither ``admin``, ``ticket.agent`` nor ``ticket.customer`` " +"permissions will have a timeout of 3 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:24 -msgid "after (relative)" +#: ../settings/security/password.rst:4 +msgid "" +"This section allows you to define password requirements for the local user " +"accounts." msgstr "" -#: ../system/core-workflows/condition-operators.rst:25 -msgid "Matches if a time span after a specified event has passed." +#: ../settings/security/password.rst:9 +msgid "" +"Zammad does **not** allow you to change your LDAP password, instead, it will " +"set a password in its local database which might confuse your users. This " +"might be addressed in the future by `#1169 `_." msgstr "" -#: ../system/core-workflows/condition-operators.rst:26 -msgid "before (absolute)" +#: ../settings/security/password.rst:14 +msgid "**Exception for admins**" msgstr "" -#: ../system/core-workflows/condition-operators.rst:27 -msgid "Matches if a date/time is before a specific point in time." +#: ../settings/security/password.rst:16 +msgid "" +"Please note that below password policies *do not* affect administrators " +"setting passwords on user accounts. While this seems strange and not safe we " +"believe that an administrator knowing an user's password is insecure as well." msgstr "" -#: ../system/core-workflows/condition-operators.rst:28 -msgid "before (relative)" +#: ../settings/security/password.rst:21 +msgid "The suggested workflow is either:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:29 -msgid "Matches if a time span after a specified event has not passed." +#: ../settings/security/password.rst:23 +msgid "" +"to use third party logins to not require local passwords at all **- or -**" msgstr "" -#: ../system/core-workflows/condition-operators.rst:30 -msgid "contains" +#: ../settings/security/password.rst:25 +msgid "to require your *user to reset the password* upon first login." msgstr "" -#: ../system/core-workflows/condition-operators.rst:31 -msgid "Matches if a specified value is present." +#: ../settings/security/password.rst:27 +msgid "" +"This way administrators are not required to set a user's password at all!" msgstr "" -#: ../system/core-workflows/condition-operators.rst:33 -msgid "Matches if all of the specified values are present." +#: ../settings/security/password.rst:31 +msgid "Maximum Failed Logins" msgstr "" -#: ../system/core-workflows/condition-operators.rst:35 -msgid "Matches if none of the specified values are present." +#: ../settings/security/password.rst:33 +msgid "" +"You can choose a value between ``4`` and ``20``. This defines how often a " +"login to a user account may fail until Zammad will lock it. Your users can " +"always use the \"forgot password\" function to change their password and " +"unlock their account." msgstr "" -#: ../system/core-workflows/condition-operators.rst:36 -msgid "contains not" +#: ../settings/security/password.rst:38 +msgid "The default value is ``10``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:37 -msgid "Matches if a specified value is not present." +#: ../settings/security/password.rst:42 +msgid "Beside changing the user's password, you can also unlock accounts via" msgstr "" -#: ../system/core-workflows/condition-operators.rst:39 -msgid "Matches if one specified value is present." +#: ../settings/security/password.rst:44 +msgid ":ref:`user management list `" msgstr "" -#: ../system/core-workflows/condition-operators.rst:41 -msgid "Matches if one specified value is not present." +#: ../settings/security/password.rst:45 +msgid ":docs:`console `" msgstr "" -#: ../system/core-workflows/condition-operators.rst:42 -msgid "does not match regex" +#: ../settings/security/password.rst:46 +msgid ":docs:`API `" msgstr "" -#: ../system/core-workflows/condition-operators.rst:43 -msgid "Matches if content doesn't fit to regex rule." +#: ../settings/security/password.rst:50 +msgid "Failed logins via LDAP no longer lock accounts." msgstr "" -#: ../system/core-workflows/condition-operators.rst:44 -msgid "ends with" +#: ../settings/security/password.rst:53 +msgid "2 Lower Case And 2 Upper Case Characters" msgstr "" -#: ../system/core-workflows/condition-operators.rst:45 -msgid "Matches if content ends with specified value." +#: ../settings/security/password.rst:55 +msgid "" +"You can add complexity to passwords by enforcing at least 2 upper and lower " +"case characters." msgstr "" -#: ../system/core-workflows/condition-operators.rst:46 -msgid "ends with one of" +#: ../settings/security/password.rst:58 ../settings/security/password.rst:83 +msgid "The default value is ``no``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:47 -msgid "Matches if content ends with one of the specified values." +#: ../settings/security/password.rst:62 +msgid "Minimum Length" msgstr "" -#: ../system/core-workflows/condition-operators.rst:48 -msgid "from (relative)" +#: ../settings/security/password.rst:64 +msgid "" +"This defines the minimum password length required for users to provide (from " +"``4`` to ``20``)." msgstr "" -#: ../system/core-workflows/condition-operators.rst:49 -msgid "Matches if date/time is after a period of time after an event." +#: ../settings/security/password.rst:67 +msgid "The default value is ``6``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:51 -msgid "Matches if content is equal to a specified value." +#: ../settings/security/password.rst:71 +msgid "Digit Required" msgstr "" -#: ../system/core-workflows/condition-operators.rst:52 -msgid "is any of" +#: ../settings/security/password.rst:73 +msgid "This enforces your users to use at least one digit within the password." msgstr "" -#: ../system/core-workflows/condition-operators.rst:53 -msgid "Matches if content is equal to any of specified values." +#: ../settings/security/password.rst:75 +msgid "The default value is ``yes``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:54 -msgid "is modified" +#: ../settings/security/password.rst:78 +msgid "Special Character Required" msgstr "" -#: ../system/core-workflows/condition-operators.rst:55 -msgid "Matches if content is modified." +#: ../settings/security/password.rst:80 +msgid "" +"This setting allows you to improve your password quality even more by " +"enforcing the password to contain at least one special character." msgstr "" -#: ../system/core-workflows/condition-operators.rst:57 -#: ../system/core-workflows/condition-operators.rst:61 -msgid "True from the moment of changing content until form submit." +#: ../settings/security/ssl-certificates.rst:2 +msgid "SSL Certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:58 -msgid "is modified to" +#: ../settings/security/ssl-certificates.rst:7 +msgid "" +"Zammad offers the possibility to upload custom certificates and custom " +"Certificate Authority (CA) certificates. This can be useful if you want to " +"connect Zammad the secure way to other systems which are using custom " +"certificates." msgstr "" -#: ../system/core-workflows/condition-operators.rst:59 -msgid "Matches if content is modified to a specific value." +#: ../settings/security/ssl-certificates.rst:12 +msgid "" +"An example usecase might be: You have an internal LDAP server that is not " +"accessible from the internet, and you want a SSL-encrypted connection, using " +"a custom certificate." msgstr "" -#: ../system/core-workflows/condition-operators.rst:62 -msgid "is none of" +#: ../settings/security/ssl-certificates.rst:19 +msgid "" +"You should have an existing custom certificate file and/or a custom CA " +"certificate file, which you want to add to Zammad. As filetype ``.crt`` is " +"supported and the certificate format has to be PEM (Base64 ASCII)." msgstr "" -#: ../system/core-workflows/condition-operators.rst:63 -msgid "Matches if content is none of any specified values." +#: ../settings/security/ssl-certificates.rst:25 +msgid "" +"When you import a custom CA certificate, all certificates generated with " +"this are trusted. This can be useful if you have more than one system/" +"certificate you want to connect to and the certificates are issued from the " +"same custom CA." msgstr "" -#: ../system/core-workflows/condition-operators.rst:65 -msgid "Matches if content is not equal to a specified value." +#: ../settings/security/ssl-certificates.rst:31 +msgid "Add a Certificate" msgstr "" -#: ../system/core-workflows/condition-operators.rst:67 -msgid "Matches if content is present." +#: ../settings/security/ssl-certificates.rst:33 +msgid "" +"To add a custom certificate or a custom CA certificate, head over to the " +"Admin panel > Settings > Security > SSL Certificates. Here you can find a " +"\"Add SSL Certificate\" button. In the dialog you can either select a " +"certificate file or paste the content of the certificate:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:68 -msgid "just changed" +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate adding dialog" msgstr "" -#: ../system/core-workflows/condition-operators.rst:69 -msgid "Matches if content has changed." +#: ../settings/security/ssl-certificates.rst:43 +msgid "" +"After selecting a file or pasting the content of the certificate, click on " +"the \"Add\" button to finally upload it to Zammad. Then, the certificates " +"are immediately effective, no restart or similar required." msgstr "" -#: ../system/core-workflows/condition-operators.rst:71 -#: ../system/core-workflows/condition-operators.rst:75 +#: ../settings/security/ssl-certificates.rst:49 msgid "" -"Only true for the moment of changing content until next form field action/" -"click." +"Please note that only single certificate files are supported. That means if " +"you want to import a certificate / CA certificate, it must contain **only " +"one** certificate." msgstr "" -#: ../system/core-workflows/condition-operators.rst:72 -msgid "just changed to" +#: ../settings/security/ssl-certificates.rst:54 +msgid "Certificate Overview" msgstr "" -#: ../system/core-workflows/condition-operators.rst:73 -msgid "Matches if content has changed to a specified value." +#: ../settings/security/ssl-certificates.rst:56 +msgid "" +"After you added a certificate, you can see a table with information for each " +"added certificate:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:76 -msgid "matches regex" +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing table of added certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:77 -msgid "Matches if value fits to regex rule." -msgstr "" - -#: ../system/core-workflows/condition-operators.rst:79 -msgid "Matches if no content is present." -msgstr "" - -#: ../system/core-workflows/condition-operators.rst:80 -msgid "starts with" +#: ../settings/security/ssl-certificates.rst:64 +msgid "" +"Here you can download the certificate or delete it, if you don't need it " +"anymore." msgstr "" -#: ../system/core-workflows/condition-operators.rst:81 -msgid "Matches if content starts with specified value." +#: ../settings/security/ssl-certificates.rst:68 +msgid "Deleting Certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:82 -msgid "starts with one of" +#: ../settings/security/ssl-certificates.rst:70 +msgid "" +"If you want to delete a specific certificate, you can do it by clicking on " +"the menu in the actions column and selecting delete:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:83 -msgid "Matches if content starts with one of the specified values." +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate deletion button" msgstr "" -#: ../system/core-workflows/condition-operators.rst:84 -msgid "till (relative)" +#: ../settings/security/ssl-certificates.rst:79 +msgid "Downloading Certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:85 -msgid "Matches if date/time is before a period of time before an event." +#: ../settings/security/ssl-certificates.rst:81 +msgid "" +"If you want to download your certificates, you can do this as well via " +"corresponding action buttons." msgstr "" -#: ../system/core-workflows/condition-operators.rst:86 -msgid "today" +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate download button" msgstr "" -#: ../system/core-workflows/condition-operators.rst:87 -msgid "Matches if date/time is today." +#: ../settings/security/third-party.rst:13 +msgid "Login Providers" msgstr "" -#: ../system/core-workflows/condition-operators.rst:88 -msgid "within last (relative)" +#: ../settings/security/third-party.rst:2 +msgid "Third-Party Applications" msgstr "" -#: ../system/core-workflows/condition-operators.rst:89 +#: ../settings/security/third-party.rst:4 msgid "" -"Matches if date/time content is within specified period of time before now." +"Third party authentication is a great way to help your users to login to " +"Zammad more easily. If the account is yet unknown, Zammad will create a new " +"user automatically, without the user needed to interact (e.g. type in his " +"name). Another big advantage of this feature is that your user doesn't need " +"to remember another password." msgstr "" -#: ../system/core-workflows/condition-operators.rst:91 -msgid "within next (relative)" +#: ../settings/security/third-party.rst:10 +msgid "" +"You can deactivate logging in via :ref:`security_password_login` if any of " +"the mentioned authentication providers are enabled in your instance." msgstr "" -#: ../system/core-workflows/condition-operators.rst:92 +#: ../settings/security/third-party.rst:27 msgid "" -"Matches if date/time content is within specified period of time after now." +"We're currently missing documentation for the following login providers:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:2 -msgid "How do they work?" +#: ../settings/security/third-party.rst:29 +msgid "LinkedIn" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:4 -msgid "" -"Core Workflows are executed according to their priority. If two workflows " -"have the same priority, they are executed in alphabetical order based on " -"their **name**." +#: ../settings/security/third-party.rst:30 +msgid "Weibo" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:8 -msgid "" -"Because of the way Core Workflows work, all changes to attributes are " -"checked with the application server - please see :doc:`limitations` for " -"possible issues." +#: ../settings/security/third-party.rst:35 +msgid "Automatic Account Link on Initial Logon" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:12 +#: ../settings/security/third-party.rst:37 msgid "" -"Below we're talking about settings that are important and not self-" -"explanatory." +"In general there's two possible options for Zammad on how to deal with " +"already known users as they try to authenticate against a third-party " +"application. By default, Zammad will not automatically link \"unknown\" " +"authentication providers to existing accounts." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:17 +#: ../settings/security/third-party.rst:42 msgid "" -"Choose the object context you want to run the workflow in. This will decide " -"on your available attributes and actions." -msgstr "" - -#: ../system/core-workflows/how-do-they-work.rst:20 -msgid "Ticket objects also have access to the ticket customer." +"This means that the user has to manually link authentication providers to " +"their accounts (for more about this :user-docs:`consult the user " +"documentation `)." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:25 +#: ../settings/security/third-party.rst:46 msgid "" -"Choose in which situation the workflow is applied. Contexts can be combined " -"to avoid duplicate workflows." +"Sometimes this doesn't come in handy as this also means you'll receive error " +"messages about \"email address being in use already\" for (yet) unknown " +"third-party authentication methods." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:30 -msgid "Creation mask" +#: ../settings/security/third-party.rst:50 +msgid "" +"If you want to allow your users to always be able to log in, no matter what, " +"you may want to enable ``Automatic account link on initial logon``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:29 +#: ../settings/security/third-party.rst:None msgid "" -"If selected, your conditions and actions will affect all applicable creation " -"masks." +"Screenshot highlighting the \"Automatic account link on initial logon\"\n" +"setting" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:34 -msgid "Edit mask" +#: ../settings/security/third-party.rst:60 +msgid "Automatic Account Linking Notification" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:33 +#: ../settings/security/third-party.rst:64 msgid "" -"If selected, your conditions and actions will affect all applicable edit " -"masks." +"To improve security and your users awareness, you can enable Zammad to " +"notify your users when a new third-party application has been linked to " +"their account." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:39 +#: ../settings/security/third-party.rst:68 msgid "" -"Zammad differentiates between selected and saved conditions. These can be " -"combined wherever needed." +"This notification is sent out once per third-party application. Zammad does " +"also mention the method used, e.g.: ``Microsoft``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:42 -msgid "**⚠️ Restrict workflows to specific roles if needed!**" +#: ../settings/security/third-party.rst:71 +msgid "By default this setting is not active (set to ``no``)." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:44 +#: ../settings/security/third-party.rst:0 msgid "" -"By default and unless configured in conditions, workflow rules are executed " -"for **all roles**. This also affects your customers!" +"Screenshot showing sample notification mail after initial\n" +"third-party linking" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:50 -msgid "Selected Conditions" +#: ../settings/security/third-party.rst:85 +msgid "" +"This notification is only sent if the account in question already exists. If " +"the login via the third-party also creates the missing account, the " +"notification will be skipped." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:48 -msgid "" -"These conditions are based on form values and match if an appropriate " -"selection is made (e.g. choosing another group in the ticket without " -"saving). This applies for drafts (active selection) and currently saved " -"values." +#: ../settings/security/third-party.rst:89 +msgid "This means it only affects:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:64 -msgid "Saved Conditions" +#: ../settings/security/third-party.rst:91 +msgid "manual account linking within the third-party page of the users profile" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:53 +#: ../settings/security/third-party.rst:92 msgid "" -"These conditions only match if the selected values are stored in the " -"database. It ignores the current value or selection of the field, as long as " -"the changes are not saved (e.g. performing field operations for an existing " -"ticket, which is viewed/opened by an agent)." +"logging into an existing local account by utilizing the *automatic account " +"link on initial logon* functionality" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:60 +#: ../settings/security/third-party.rst:None msgid "" -"Keep in mind that the value has to be available in the situation where you " -"need it. Otherwise the condition won't match." +"Screenshot showing the \"automatic account linking notification\"\n" +"setting" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:63 -msgid "" -"Example: you can't perform any actions with *saved condition* on a ticket in " -"creation, because there are no saved values at that time." +#: ../settings/security/third-party.rst:100 +msgid "No User Creation on Logon" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:66 +#: ../settings/security/third-party.rst:102 msgid "" -"You can find a description of the condition operators for core workflows :" -"doc:`here `." +"By default, Zammad will create a new user account if the user logs in via a " +"third-party application and the account doesn't exist yet." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:72 +#: ../settings/security/third-party.rst:105 msgid "" -"Which actions should we run on the relevant fields? The possible actions " -"depend on the object type. However, usually you can at least change the " -"visibility and whether the field is mandatory." +"If you want to prevent Zammad from creating new accounts on logon, you can " +"disable this feature by setting ``No user creation on logon`` to ``yes``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:76 -msgid "Be aware that actions are not available for **related** context." +#: ../settings/security/third-party.rst:None +msgid "Screenshot showing the \"no user creation on logon\" setting" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:78 +#: ../settings/security/third-party/facebook.rst:4 msgid "" -"**Example:** Let's assume you are working in the ticket context. While you " -"can have customer *conditions*, you *can't adjust* objects with actions in " -"that scope. That's because this wouldn't have any impact on the ticket " -"dialog. Of course all ticket attributes (state, owner, ...) are available." +"It is possible to create a quick login for your helpdesk via Facebook To do " +"so, you need to follow these steps:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:84 +#: ../settings/security/third-party/facebook.rst:9 +msgid "Register Facebook App" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:11 msgid "" -"Please also have a look at our :doc:`limitations` to be safe from surprises." +"Visit [https://developers.facebook.com/apps/] and click on \"Add a new App\"" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:88 -msgid "Available Operators" +#: ../settings/security/third-party/facebook.rst:None +msgid "initial page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:90 -msgid "The availability of operators depends on the object type and scope." +#: ../settings/security/third-party/facebook.rst:17 +msgid "After that enter the app settings" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:94 -msgid "" -"Please note that actions may or may not restrict API based access to " -"attributes. We're displaying the following icons for your overview to " -"understand these limits better:" +#: ../settings/security/third-party/facebook.rst:None +msgid "Create App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:0 -msgid "|api| This icon indicates the action affects the API." +#: ../settings/security/third-party/facebook.rst:22 +msgid "Navigate to \"Settings\" and fill in this infromation" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:163 -msgid "api" +#: ../settings/security/third-party/facebook.rst:None +msgid "App Settings" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:0 -msgid "|ui| This icon indicates the action only affects the web interface." +#: ../settings/security/third-party/facebook.rst:27 +msgid "Navigate to app review and Check \"Make [appname] public?\"" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:167 -msgid "ui" +#: ../settings/security/third-party/facebook.rst:None +msgid "App Review" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:102 -msgid "show |ui|" +#: ../settings/security/third-party/facebook.rst:35 +msgid "Configure Zammad as Facebook App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:102 -msgid "Display the chosen field. Allows setting of values." -msgstr "" - -#: ../system/core-workflows/how-do-they-work.rst:109 -msgid "hide |ui|" +#: ../settings/security/third-party/facebook.rst:37 +msgid "" +"Navigate to \"Admin -> Security -> Third Party Applications\" and enter the " +"App ID and the App Secret. You can find this Key in the Dashbard of your " +"Facebok app." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:105 -msgid "" -"Hide the chosen field. However, it technically still allows setting the " -"field." +#: ../settings/security/third-party/facebook.rst:None +msgid "Zammad Configuration" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:108 +#: ../settings/security/third-party/facebook.rst:44 +#: ../settings/security/third-party/github.rst:43 +#: ../settings/security/third-party/gitlab.rst:46 msgid "" -"Please note that the field is **not** gone and still contains an existing " -"value (if set)! Consider *remove* instead, if you want this field to be gone." +"Now you can link accounts via \"Avatar -> Profile -> Link Accounts\" or " +"login via Zammad login page." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:112 -msgid "remove |ui|" +#: ../settings/security/third-party/github.rst:2 +#: ../system/integrations/github.rst:2 +msgid "GitHub" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:112 -msgid "Entirely removes the field. The field value will not be evaluated." +#: ../settings/security/third-party/github.rst:4 +msgid "" +"It is possible to create a quick login for your helpdesk via GitHub. To " +"activate the quick login you need to enable OAuth for GitHub." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:115 -msgid "set mandatory |ui| |api|" +#: ../settings/security/third-party/github.rst:8 +msgid "Register GitHub App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:115 -msgid "Sets the field to mandatory." +#: ../settings/security/third-party/github.rst:10 +msgid "" +"Visit https://www.github.com/settings/applications/new and enter the app " +"settings. As callback URL enter \"https://zammad_host/auth/github/callback\" " +"where zammad_host has to be replaced with your Zammad FQDN" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:118 -msgid "set optional |ui| |api|" +#: ../settings/security/third-party/github.rst:None +msgid "Register OAuth app on www.github.com" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:118 -msgid "Sets the field to optional." +#: ../settings/security/third-party/github.rst:19 +msgid "Configure Zammad as GitHub App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:124 -msgid "add option |ui| |api|" +#: ../settings/security/third-party/github.rst:21 +msgid "" +"Enter the \"APP ID\" and the \"APP SECRET\" from the GitHub OAUTH " +"Applications Dashboard" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:121 -msgid "Allows adding options to tree selects or selects." +#: ../settings/security/third-party/github.rst:None +msgid "GitHub config in Zammad admin interface" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:123 +#: ../settings/security/third-party/github.rst:28 msgid "" -"You have to use the \"remove option\" before performing this action. It " -"allows you to use *existing* configured values." +"After you configured the GitHub credentials and activated the login method, " +"you should see a new icon on the login page." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:128 -msgid "remove option |ui| |api|" +#: ../settings/security/third-party/github.rst:None +msgid "GitHub logo on login page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:127 +#: ../settings/security/third-party/github.rst:34 msgid "" -"Allows removing options from tree selects or selects. It allows you to use " -"*existing* configured values." +"If you click on the icon you will be redirected to GitHub and see something " +"similar to this:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:134 -msgid "set fixed to |ui| |api|" +#: ../settings/security/third-party/github.rst:None +msgid "GitHub oauth page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:131 -msgid "Reduces the available options by your selection." +#: ../settings/security/third-party/github.rst:40 +#: ../settings/security/third-party/gitlab.rst:42 +msgid "" +"When you grant the access you will be redirected to your Zammad instance and " +"logged in as a customer." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:133 -msgid "" -"This reduces your workflows in terms of *add option* and *remove option*." +#: ../settings/security/third-party/gitlab.rst:2 +msgid "Gitlab" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:137 -msgid "fill in |ui|" +#: ../settings/security/third-party/gitlab.rst:4 +msgid "" +"It is possible to create a quick login for your helpdesk via Gitlab. To " +"activate the quick login you need to enable OAuth for Gitlab." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:137 -msgid "Allows filling in of string and integer fields with your values." +#: ../settings/security/third-party/gitlab.rst:8 +msgid "Register Gitlab App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:141 -msgid "fill in empty |ui|" +#: ../settings/security/third-party/gitlab.rst:10 +msgid "To register an app in Gitlab open your profile and select applications." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:140 +#: ../settings/security/third-party/gitlab.rst:12 msgid "" -"Allows filling in of string and integer fields with your values **if the " -"field is empty**." +"As callback URL enter \"https://zammad-fqdn/auth/gitlab/callback\" where " +"zammad-fqdn has to be replaced with your Zammad FQDN" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:144 -msgid "select |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Register OAuth app on gitlab instance" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:144 -msgid "Select a specific value within a select, tree select or boolean field." +#: ../settings/security/third-party/gitlab.rst:18 +msgid "Just select *read_user* under scopes as in the screenshot and save it." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:153 -msgid "auto select |ui|" +#: ../settings/security/third-party/gitlab.rst:21 +msgid "Configure Zammad as Gitlab App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:147 -msgid "Helps users with tree select and select fields:" +#: ../settings/security/third-party/gitlab.rst:23 +msgid "" +"Enter the \"APP ID\" and the \"APP SECRET\" from the Gitlab OAUTH " +"Applications Dashboard and your Gitlab-URL in the \"SITE\" field." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:149 -msgid "" -"If the field has only one option available for selection and no value yet, " -"the value will be automatically set." +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab config in Zammad admin interface" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:152 +#: ../settings/security/third-party/gitlab.rst:30 msgid "" -"This option only works if you have one value and doesn't work if there is " -"more than one option available." +"After you configured the Gitlab credentials and activated the login method, " +"you should see a new icon on the login page." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:157 -msgid "set readonly |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab logo on login page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:156 +#: ../settings/security/third-party/gitlab.rst:36 msgid "" -"Allows you to display an attribute as read only (which means no changes are " -"possible)." +"If you click on the icon you will be redirected to Gitlab and see something " +"similar to this:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:161 -msgid "unset readonly |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab oauth page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:160 +#: ../settings/security/third-party/google.rst:4 msgid "" -"In case a workflow set the field in question to read only, you can undo this " -"with option above." +"With some easy and fast steps, you can enable Zammad to authenticate your " +"users via Google." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:172 -msgid "Stop after match" +#: ../settings/security/third-party/google.rst:8 +msgid "Register a Google App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:174 +#: ../settings/security/third-party/google.rst:10 msgid "" -"Here you can decide if other workflows are executed after the current one." +"First of all, we need to create a new project - you can skip this step if " +"you already have one." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:176 +#: ../settings/security/third-party/google.rst:15 msgid "" -"If set to ``no`` (default), further workflows will be executed if they match " -"the condition. In this case, it is possible that your actions from the " -"current workflow can be overwritten by another workflow." +"Use this link to create a new project: https://console.cloud.google.com/" +"projectcreate" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:180 +#: ../settings/security/third-party/google.rst:18 msgid "" -"If set to ``yes``, no further worflows will be executed after the current " -"one." +"Now expand the menu, expand \"APIs & Services\" and select \"Credentials\". " +"Go to the tab \"OAuth consent screen\" first and ensure to fill in the " +"requested information - without doing so you can't create credentials!" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:184 -msgid "Priority" +#: ../settings/security/third-party/google.rst:None +msgid "Creating a consent screen" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:186 +#: ../settings/security/third-party/google.rst:25 msgid "" -"You can define the sequence, in which the workflows are executed. The " -"default value is ``500``." +"After filling in and saving the consent screen information, you can go to " +"the \"Credentials\" tab and create new \"OAuth client ID\"-Credentials." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:189 +#: ../settings/security/third-party/google.rst:28 msgid "" -"The workflows are executed in ascending order by their priority. That means " -"lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." +"Fill in the necessary information as follows and replace ``zammad_host`` " +"with your FQDN:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:2 -msgid "Learn by Example" +#: ../settings/security/third-party/google.rst:31 +msgid "**Application type** ``[x] Web application``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:4 -msgid "" -"This page provides some basic examples for Core Workflows. Of course you can " -"build much more complex workflows if needed." +#: ../settings/security/third-party/google.rst:34 +msgid "**Authorized JavaScript origins** ``https://zammad_host/``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:7 +#: ../settings/security/third-party/google.rst:37 msgid "" -"To learn about Core Workflows in detail, first go to :doc:`how-do-they-work`." +"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" +"callback``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:10 -msgid "Group Based Examples" +#: ../settings/security/third-party/google.rst:None +msgid "Adding a new OAuth client ID" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:12 +#: ../settings/security/third-party/google.rst:43 msgid "" -"All following workflows have the same base configurations. The workflow may " -"not use them all." +"After creating the credentials, go to your Zammad installation and navigate " +"to \"Admin > Security > Third Party Applications\" > Google. Enter your " +"Client ID and Client secret here." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:15 -msgid "Groups:" +#: ../settings/security/third-party/google.rst:None +msgid "Zammad" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:20 -msgid "Attributes:" +#: ../settings/security/third-party/google.rst:50 +msgid "After submitting, the login via Google can be used." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:22 -msgid "Category (Single tree selection field, not mandatory, agents only)" +#: ../settings/security/third-party/microsoft.rst:2 +msgid "Microsoft" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:23 +#: ../settings/security/third-party/microsoft.rst:4 msgid "" -"Approved (Boolean field, not mandatory, not shown, ``false`` as default)" +"Zammad's Microsoft connection allows your users with Microsoft accounts to " +"login. This works for Azure users as well and can be an alternative to :doc:" +"`/system/integrations/ldap/index`." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:24 -msgid "Operating System (Text field, not mandatory, not shown)" +#: ../settings/security/third-party/microsoft.rst:10 +msgid "" +"This documentation part does not cover our :doc:`📧 Microsoft 365 email " +"channel `." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:25 -msgid "Software used (Single selection field, not mandatory, not shown)" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screenshot showing Microsoft login button on Zammad login screen." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:68 -msgid "Group specific values and fields" +#: ../settings/security/third-party/microsoft.rst:30 +#: ../settings/security/third-party/microsoft.rst:53 +msgid "Supported account types:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:28 +#: ../settings/security/third-party/microsoft.rst:22 msgid "" -"This workflow set depends on the category field. It reduces the available " -"set of values based on the group selected." +"Please note that Zammad only supports these account types (App dependent):" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:33 -msgid "Workflow 2nd Level group" +#: ../settings/security/third-party/microsoft.rst:35 +msgid "Avatars of signing in users:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:35 +#: ../settings/security/third-party/microsoft.rst:33 msgid "" -"This reduces the category options to ``2nd Level/*``, ``Internal/*`` and " -"``Others``. It also sets further required fields to mandatory and visible." -msgstr "" - -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for 2nd level" +"Zammad currently ignores user avatars. If the user is registered with e.g. " +"Gravatar, Zammad will fetch the avatar from there if enabled. See :doc:" +"`Zammad Image Service ` for more." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:43 -msgid "Workflow Support group" +#: ../settings/security/third-party/microsoft.rst:38 +msgid "Step 1 - Register a Microsoft App for Zammad" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:45 +#: ../settings/security/third-party/microsoft.rst:40 msgid "" -"This reduces the category options to ``Support/*``, ``Internal/*`` and " -"``Others``. It also sets further required fields to visible." -msgstr "" - -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for support" +"Login to the `Microsoft Azure Portal `_ and " +"navigate to App registrations to create a new app. Provide the requested " +"information as follows and register your app." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:53 -msgid "Workflow Sales group" +#: ../settings/security/third-party/microsoft.rst:46 +msgid "Name:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:55 +#: ../settings/security/third-party/microsoft.rst:45 msgid "" -"This reduces the category options to ``Sales/*``, ``Internal/*`` and " -"``Others``." +"Any meaningful name fitting, this name will be displayed to users trying to " +"authenticate with this app." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for sales" +#: ../settings/security/third-party/microsoft.rst:49 +msgid "Choose one of the above mentioned account types (see Limitations)." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:68 -#: ../system/integrations/slack.rst:88 -msgid "The Result" +#: ../settings/security/third-party/microsoft.rst:51 +msgid "" +"The correct account type depends on your use case. If you want to use the " +"authentication internal only, choose the first option. If you're unsure, use " +"the \"Help me choose...\" link." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:63 -msgid "" -"This is what the agent would experience with the above workflows in place." +#: ../settings/security/third-party/microsoft.rst:58 +msgid "Redirect URI (optional):" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 +#: ../settings/security/third-party/microsoft.rst:56 msgid "" -"Workflow shows objects and limits options based on selections on the group" +"Select web and provide your callback URL. The callback URL looks like this: " +"``https://zammad.domain.tld/auth/microsoft_office365/callback``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:90 -msgid "Approval process" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to register a Microsoft app" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:71 -msgid "" -"In this case ``approved`` is visible to agents by default. For this " -"workflow, an additional role ``Approval person`` is required (no further " -"permissions)." +#: ../settings/security/third-party/microsoft.rst:71 +msgid "Within **API permissions** add the following permissions:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that restricts an approval attribute to specific roles" +#: ../settings/security/third-party/microsoft.rst:69 +msgid "``User.Read``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:81 -msgid "" -"This workflow may work best in combination with a :doc:`trigger ` but technically, this is not required." +#: ../settings/security/third-party/microsoft.rst:71 +msgid "Contacts" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:84 -msgid "" -"Select fields may be a better approach because they allow more values than " -"just a simple ``true`` or ``false``." +#: ../settings/security/third-party/microsoft.rst:71 +msgid "``Contacts.Read``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 +#: ../settings/security/third-party/microsoft.rst:73 msgid "" -"Workflow fixes possible values of \"Approved ?\" to a specific selection " -"depending on the users role" +"You can find these permissions within *Microsoft Graph → Delegated " +"permissions*." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:103 -msgid "State dependent mandatory fields" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to add required API permissions" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:93 +#: ../settings/security/third-party/microsoft.rst:80 msgid "" -"This workflow sets ``Category`` to mandatory if the agent wants to set the " -"states ``closed`` or ``pending close`` to enforce categorization." +"Within **Certificates & secrets** create a new client secret. Note down the " +"returned secret **value** for later. **Do not** use the secret ID!" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that sets fields to mandatory on specific states" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to create a new app secret" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 +#: ../settings/security/third-party/microsoft.rst:88 msgid "" -"Workflow sets category field to mandatory upon choosing closed or pending " -"close as state" +"From **Overview** copy your apps *Application (client) ID*. If you're using " +"a single tenant app, please also copy *Directory (tenant) ID*. You now have " +"all required information for Zammad." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:106 -msgid "Manual Ticket Handover Process" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to retreive application client and tenant IDs" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:108 -msgid "This example covers the handover of a ticket from one agent to another:" +#: ../settings/security/third-party/microsoft.rst:98 +msgid "Step 2 - Add App Credentials to Zammad" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:110 +#: ../settings/security/third-party/microsoft.rst:100 msgid "" -"When the ticket owner is modified, a new text field (\"Handover\") shows up " -"for a comment" +"Navigate to Security > Third-party Applications (Tab) within Zammad's admin " +"settings. Scroll down to the section *Authentication via Microsoft* and fill " +"in the required information." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:112 -msgid "" -"This may only be visible when the owner is changed, therefore it has to be " -"hidden in general" +#: ../settings/security/third-party/microsoft.rst:105 +msgid "App ID:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:114 -msgid "The input in this handover text field is mandatory" +#: ../settings/security/third-party/microsoft.rst:105 +msgid "This is your *Application (client) ID*." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:115 -msgid "" -"After submitting changes, the value of the handover field must be added as " -"an note to the ticket (via trigger)" +#: ../settings/security/third-party/microsoft.rst:108 +msgid "App secret:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:121 -msgid "Hiding handover field" +#: ../settings/security/third-party/microsoft.rst:108 +msgid "This is your *client secret* (value)." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Hiding the handover field in core workflows" +#: ../settings/security/third-party/microsoft.rst:113 +msgid "App Tenant ID:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:126 -msgid "Showing handover field and setting it to mandatory" +#: ../settings/security/third-party/microsoft.rst:111 +msgid "" +"**optional** only required for apps that use account type *Accounts in this " +"organizational directory only (Default Directory only - Single tenant).*" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Showing the handover field and set it as mandatory" +#: ../settings/security/third-party/microsoft.rst:115 +msgid "" +"Apply your settings by pressing submit and activate *Authentication via " +"Microsoft*." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:131 -msgid "Trigger writing handover input to a new article" +#: ../settings/security/third-party/microsoft.rst:None +msgid "" +"Screencast showing how to add app credentials and activating the\n" +"authentication method" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Write handover content to a new article" +#: ../settings/security/third-party/saml.rst:2 +msgid "SAML" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:133 +#: ../settings/security/third-party/saml.rst:4 msgid "" -"As a result, the ticket includes an article of the type note which includes " -"the predefined text and the handover comment." +"Connect your SAML (Security Assertion Markup Language) identity provider as " +"a single sign-on (SSO) method." msgstr "" -#: ../system/core-workflows/limitations.rst:6 -msgid "Core Workflows do not replace Triggers" +#: ../settings/security/third-party/saml.rst:7 +msgid "" +"SAML is an open standard for SSO authentication (among other things). Sign-" +"ins are shared across multiple **service providers** and managed by a " +"central **identity provider** (IdP)." msgstr "" -#: ../system/core-workflows/limitations.rst:5 +#: ../settings/security/third-party/saml.rst:11 msgid "" -"Workflows manipulate the behavior of fields. However, they do not set values " -"in fields because of actions." +"In this case, the service provider is Zammad, and the IdP is a software " +"service that you either host or subscribe to (*e.g.,* `Keycloak `_, `Redhat SSO Server `_, `ADFS `_, or `Okta `_)." msgstr "" -#: ../system/core-workflows/limitations.rst:16 -msgid "API calls are only partly affected" +#: ../settings/security/third-party/saml.rst:18 +msgid "" +"This guide assumes you are already using SAML within your organization (i." +"e., that your IdP is fully set up)." msgstr "" -#: ../system/core-workflows/limitations.rst:9 +#: ../settings/security/third-party/saml.rst:21 msgid "" -"Some options affect UI only and thus do not restrict responses and calls." +"Please note: Our instructions are based on connecting Zammad with Keycloak." msgstr "" -#: ../system/core-workflows/limitations.rst:11 -msgid "This affects the following actions:" +#: ../settings/security/third-party/saml.rst:25 +msgid "Step 1: Configure Your IdP" msgstr "" -#: ../system/core-workflows/limitations.rst:13 -msgid "select" +#: ../settings/security/third-party/saml.rst:28 +msgid "Add Zammad as a Client/App" msgstr "" -#: ../system/core-workflows/limitations.rst:14 -msgid "auto select" +#: ../settings/security/third-party/saml.rst:30 +msgid "" +"Import Zammad into your IdP using the XML configuration found at ``https://" +"your.zammad.domain/auth/saml/metadata``." msgstr "" -#: ../system/core-workflows/limitations.rst:15 -msgid "show" +#: ../settings/security/third-party/saml.rst:33 +msgid "" +"If your IdP doesn't support XML import, you will have to configure Zammad as " +"a new client/app manually using the above XML metadata file for reference." msgstr "" -#: ../system/core-workflows/limitations.rst:16 -msgid "hide" +#: ../settings/security/third-party/saml.rst:36 +msgid "For instance, when you see this tag:" msgstr "" -#: ../system/core-workflows/limitations.rst:25 -msgid "Some fields stay unavailable to customers" +#: ../settings/security/third-party/saml.rst:42 +msgid "" +"Set the **Assertion Consumer Service Binding URL** (sometimes also listed as " +"**Valid Redirect URIs**) to ``http://your.zammad.domain/auth/saml/callback``." msgstr "" -#: ../system/core-workflows/limitations.rst:19 -msgid "" -"For technical and security reasons, some default fields (the pale ones you " -"can't edit) stay unavailable for display and usage on customer permissions." +#: ../settings/security/third-party/saml.rst:47 +msgid "Set Up User Attribute Mapping" msgstr "" -#: ../system/core-workflows/limitations.rst:23 +#: ../settings/security/third-party/saml.rst:49 msgid "" -"If you require your customers to change e.g. priorities, please consider " -"using workarounds via :doc:`/system/objects` and :doc:`/manage/trigger`." +"Zammad requests the following user attributes (or “properties”) from the IdP:" msgstr "" -#: ../system/core-workflows/limitations.rst:29 -msgid "Ticket title changes not supported in edit mask" +#: ../settings/security/third-party/saml.rst:51 +msgid "Email address (``email``)" msgstr "" -#: ../system/core-workflows/limitations.rst:28 -msgid "" -"It is currently not possible to perform changes of the ticket title in the " -"edit mask (e.g. renaming, set to read-only)." +#: ../settings/security/third-party/saml.rst:52 +msgid "Full name (``name``)" msgstr "" -#: ../system/core-workflows/limitations.rst:37 -msgid "What is out of scope of Core Workflows?" +#: ../settings/security/third-party/saml.rst:53 +msgid "Given name (``first_name``)" msgstr "" -#: ../system/core-workflows/limitations.rst:32 -msgid "" -"There are some things that would count as workflow but are either done via :" -"doc:`/manage/trigger` or :doc:`/manage/scheduler`." +#: ../settings/security/third-party/saml.rst:54 +msgid "Family name (``last_name``)" msgstr "" -#: ../system/core-workflows/limitations.rst:35 -msgid "Such as (but not limited to):" +#: ../settings/security/third-party/saml.rst:56 +msgid "" +"You may need to set up “mappers” (or “mappings”) to tell your IdP how user " +"attributes in SAML correspond to those in Zammad. For a more detailed " +"breakdown, refer to the XML metadata file referenced in the previous section." msgstr "" -#: ../system/core-workflows/limitations.rst:37 -msgid "up- or downgrade permissions of users" +#: ../settings/security/third-party/saml.rst:62 +msgid "Per-IdP Instructions" msgstr "" -#: ../system/core-workflows/limitations.rst:38 -msgid "affecting article creation or listing" +#: ../settings/security/third-party/saml.rst:102 +msgid "Keycloak" msgstr "" -#: ../system/data-privacy.rst:2 -msgid "Data Privacy" +#: ../settings/security/third-party/saml.rst:65 +msgid "" +"**To add Zammad as a client,** save the XML configuration to disk (``https://" +"your.zammad.domain/auth/saml/metadata``) and use **Clients > Clients list > " +"Import client** in the Keycloak admin panel." msgstr "" -#: ../system/data-privacy.rst:4 +#: ../settings/security/third-party/saml.rst:70 msgid "" -"For compliance with GDPR and other data privacy laws, you may wish to " -"**permanently delete users from the system**, along with **all of their " -"associated tickets**." +"To help Zammad **match its own user accounts to Keycloak users**, create a " +"user attribute (or “property”) mapper. In **Clients list**, click on your " +"newly created Client ID, choose the tab **Client scopes** and click on the " +"link which refers to your Zammad instance. Choose **Add mapper > By " +"configuration > User Property** and create a mapper with the following " +"entries:" 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 `!" +#: ../settings/security/third-party/saml.rst:78 +msgid "**Name**" msgstr "" -#: ../system/data-privacy.rst:12 -msgid "" -"Access to this panel requires ``admin.data_privacy`` permissions (introduced " -"in Zammad 3.5)." +#: ../settings/security/third-party/saml.rst:80 +msgid "**Mapper Type**" msgstr "" -#: ../system/data-privacy.rst:15 -msgid "" -"On older systems that have not been updated yet, customers can also be :docs:" -"`deleted via the Zammad console `." +#: ../settings/security/third-party/saml.rst:81 +msgid "``User Property``" msgstr "" -#: ../system/data-privacy.rst:22 -msgid "User deletion dialog in the Data Privacy panel" +#: ../settings/security/third-party/saml.rst:82 +msgid "**Property**" msgstr "" -#: ../system/data-privacy.rst:22 -msgid "" -"The user deletion dialog lists some of the tickets that will be removed from " -"the system along with the user." +#: ../settings/security/third-party/saml.rst:83 +msgid "``emailAddress``" msgstr "" -#: ../system/data-privacy.rst:27 -msgid "Deleting Users via GUI" +#: ../settings/security/third-party/saml.rst:84 +msgid "**SAML Attribute Name**" msgstr "" -#: ../system/data-privacy.rst:29 -msgid "🔥 **All deletions are FINAL!**" +#: ../settings/security/third-party/saml.rst:86 +msgid "**SAML Attribute NameFormat**" msgstr "" -#: ../system/data-privacy.rst:31 -msgid "Once you click “Delete”, the action cannot be canceled or undone." +#: ../settings/security/third-party/saml.rst:87 +msgid "``basic``" msgstr "" -#: ../system/data-privacy.rst:33 +#: ../settings/security/third-party/saml.rst:89 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." +"In the example above, we're telling Zammad that whenever it receives a SAML " +"login request, it should take the ``email`` property from Keycloak, look for " +"a Zammad user with the same ``email`` attribute, and create a new session " +"for that user." msgstr "" -#: ../system/data-privacy.rst:36 -msgid "**The following records cannot be deleted:**" +#: ../settings/security/third-party/saml.rst:95 +msgid "" +"If your Keycloak users' email addresses are stored on another property (*e." +"g.,* ``username``), adjust accordingly." msgstr "" -#: ../system/data-privacy.rst:38 -msgid "your own account" +#: ../settings/security/third-party/saml.rst:98 +msgid "" +"Back in **Settings**, enter the Client ID (``https://your.zammad.domain/auth/" +"saml/metadata``) in the field **Master SAML Processing URL**." msgstr "" -#: ../system/data-privacy.rst:39 -msgid "the system's last remaining administrator account" +#: ../settings/security/third-party/saml.rst:101 +msgid "You also need to enable **Sign assertions**." msgstr "" -#: ../system/data-privacy.rst:42 -msgid "Step 1: Find a User / Confirm Deletion" +#: ../settings/security/third-party/saml.rst:105 +msgid "Step 2: Configure Zammad" msgstr "" -#: ../system/data-privacy.rst:44 -msgid "There are three ways to access the user deletion dialog:" +#: ../settings/security/third-party/saml.rst:107 +msgid "" +"Enable SAML and enter your IdP's details in the Admin Panel under **Settings " +"> Security > Third Party Applications > Authentication via SAML**:" msgstr "" -#: ../system/data-privacy.rst:51 -msgid "**from the user's profile**" +#: ../settings/security/third-party/saml.rst:None +msgid "Example configuration of SAML part 1" msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Accessing the user deletion dialog in a user profile" +#: ../settings/security/third-party/saml.rst:119 +msgid "Display name" msgstr "" -#: ../system/data-privacy.rst:51 -msgid "Click **Action > Delete**." +#: ../settings/security/third-party/saml.rst:116 +msgid "" +"Allows you to define a custom button name for SAML. This helps your users to " +"understand better what the button on the login page does." msgstr "" -#: ../system/data-privacy.rst:58 -msgid "**in the “Manage > Users” Admin Panel**" +#: ../settings/security/third-party/saml.rst:119 +msgid "Defaults to ``SAML``." msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Accessing the user deletion dialog under “Users” in the Admin Panel" +#: ../settings/security/third-party/saml.rst:123 +msgid "IDP SSO target URL" msgstr "" -#: ../system/data-privacy.rst:58 -msgid "Use the **⋮ Actions** menu for the target user." +#: ../settings/security/third-party/saml.rst:122 +msgid "" +"This is the target URL Zammad shall redirect to when the user presses the " +"SAML button. For Keycloak, this needs to look like https://your.domain/" +"realms/your-realm/protocol/saml" msgstr "" -#: ../system/data-privacy.rst:66 ../system/data-privacy.rst:104 -msgid "**in the “System > Data Privacy” Admin Panel**" +#: ../settings/security/third-party/saml.rst:127 +msgid "IDP single logout target URL" msgstr "" -#: ../system/data-privacy.rst:0 +#: ../settings/security/third-party/saml.rst:126 msgid "" -"Accessing the user deletion dialog under “Data Privacy” in the Admin Panel" +"This is the URL to which the single logout request and response should be " +"sent." msgstr "" -#: ../system/data-privacy.rst:65 +#: ../settings/security/third-party/saml.rst:131 +msgid "IDP certificate" +msgstr "" + +#: ../settings/security/third-party/saml.rst:130 msgid "" -"Use the **New Deletion Task** button. Search for users by name or email " -"address." +"The public certificate of your IDP for Zammad to verify during the callback " +"phase." msgstr "" -#: ../system/data-privacy.rst:79 -msgid "**Delete organizations**" +#: ../settings/security/third-party/saml.rst:145 +msgid "IDP certificate fingerprint" msgstr "" -#: ../system/data-privacy.rst:69 +#: ../settings/security/third-party/saml.rst:134 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:" +"The fingerprint of your IDPs public certificate to verify during callback " +"phase." msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Deleting an organization via the user deletion dialog" +#: ../settings/security/third-party/saml.rst:137 +msgid "🔏 **For the IdP certificate / certificate fingerprint:**" msgstr "" -#: ../system/data-privacy.rst:78 +#: ../settings/security/third-party/saml.rst:139 msgid "" -"If this option does not appear, make sure there are no pending deletion " -"tasks for other customers from this organization." +"Provide **only one or the other**—do not provide both! (Between the two, we " +"recommend the signing certificate itself: fingerprints use SHA-1, which `has " +"been broken for a while now `_.)" msgstr "" -#: ../system/data-privacy.rst:82 -msgid "Step 2: Monitor Deletion Job Status" +#: ../settings/security/third-party/saml.rst:144 +msgid "" +"**Keycloak users:** Find your certificate in the Keycloak admin panel under " +"**Realm Settings > Keys > Algorithm: RS256 > Certificate**." msgstr "" -#: ../system/data-privacy.rst:84 +#: ../settings/security/third-party/saml.rst:151 +msgid "Name identifier format" +msgstr "" + +#: ../settings/security/third-party/saml.rst:148 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:" +"This is the unique identifiers field type. Usually it should be ``urn:oasis:" +"names:tc:SAML:1.1:nameid-format:emailAddress``." msgstr "" -#: ../system/data-privacy.rst:98 -msgid "**in the Activity Stream**" +#: ../settings/security/third-party/saml.rst:151 +msgid "Zammad **expects an email address as unique identifier**!" msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Activity Stream showing data privacy tasks" +#: ../settings/security/third-party/saml.rst:155 +msgid "UID attribute name" msgstr "" -#: ../system/data-privacy.rst:94 +#: ../settings/security/third-party/saml.rst:154 msgid "" -"For each deleted user, the Activity Stream will be updated twice—once when " -"the task is created, and once when it's complete." +"Here you can define an attribute that uniquely identifies the user. If " +"unset, the name identifier returned by the IDP is used." msgstr "" -#: ../system/data-privacy.rst:97 -msgid "" -"These notifications are only visible to users with ``admin.data_privacy`` " -"permissions." +#: ../settings/security/third-party/saml.rst:None +msgid "Example configuration of SAML part 2" msgstr "" -#: ../system/data-privacy.rst:0 +#: ../settings/security/third-party/saml.rst:163 msgid "" -"The task list within Data Privacy shows removals being in progress and " -"completed." +"Decide if the certificate for the connection to the IdP service has to be " +"verified or not (default: ``yes``)." msgstr "" -#: ../system/data-privacy.rst:107 -msgid "Frequently Asked Questions" +#: ../settings/security/third-party/saml.rst:169 +msgid "Signing & Encrypting" msgstr "" -#: ../system/data-privacy.rst:121 -msgid "What happens if I receive an email from a deleted customer?" -msgstr "" - -#: ../system/data-privacy.rst:110 +#: ../settings/security/third-party/saml.rst:169 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." +"Define if you want to sign, encrypt, do both or nothing for the requests." msgstr "" -#: ../system/data-privacy.rst:115 -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**." +#: ../settings/security/third-party/saml.rst:179 +msgid "Certificate (PEM)" msgstr "" -#: ../system/data-privacy.rst:130 -msgid "What about user information stored in internal notes or other messages?" +#: ../settings/security/third-party/saml.rst:172 +msgid "" +"Paste the public certificate of your Zammad SAML client, if you want to " +"encrypt the requests." msgstr "" -#: ../system/data-privacy.rst:124 -msgid "" -"The deletion process removes **user accounts and associated tickets only**." +#: ../settings/security/third-party/saml.rst:175 +msgid "Make sure the certificate is:" msgstr "" -#: ../system/data-privacy.rst:126 -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." +#: ../settings/security/third-party/saml.rst:177 +msgid "already valid and not yet expired" msgstr "" -#: ../system/data-privacy.rst:137 -msgid "I deleted an user and can still see a message they sent!" +#: ../settings/security/third-party/saml.rst:178 +msgid "no CA certificate" msgstr "" -#: ../system/data-privacy.rst:133 -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." +#: ../settings/security/third-party/saml.rst:179 +msgid "valid for signing and encrypting" msgstr "" -#: ../system/data-privacy.rst:141 -msgid "I removed a customer, now my reporting is off!" +#: ../settings/security/third-party/saml.rst:185 +msgid "Private key (PEM)" msgstr "" -#: ../system/data-privacy.rst:140 +#: ../settings/security/third-party/saml.rst:182 msgid "" -"When removing users and their tickets, all references are removed. This also " -"affects e.g. Reporting - these information are lost." +"Paste the private key of your Zammad SAML client here, if you want to sign " +"the requests." msgstr "" -#: ../system/data-privacy.rst:145 -msgid "How long does Zammad store created tasks?" +#: ../settings/security/third-party/saml.rst:185 +msgid "Make sure the key is an RSA key with a length of at least 2048 bits." msgstr "" -#: ../system/data-privacy.rst:144 -msgid "" -"Please see the on-premise data section of the :docs:`data privacy ` chapter." +#: ../settings/security/third-party/saml.rst:188 +msgid "Private key secret" msgstr "" -#: ../system/data-privacy.rst:150 -msgid "What about re-assigned tickets? I want to delete them, too." +#: ../settings/security/third-party/saml.rst:188 +msgid "If your private key is secured with a secret, you can provide it here." msgstr "" -#: ../system/data-privacy.rst:148 -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." +#: ../settings/security/third-party/saml.rst:192 +msgid "Your callback URL" msgstr "" -#: ../system/data-privacy.rst:154 -msgid "Why are there so many deletion task entries, I didn't create them!" +#: ../settings/security/third-party/saml.rst:191 +msgid "" +"This URL is needed for your IdP configuration so it knows where to redirect " +"to after successful authentication." msgstr "" -#: ../system/data-privacy.rst:153 +#: ../settings/security/third-party/saml.rst:194 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." +"After saving your input by clicking on the \"Submit\" button, Zammad " +"verifies the provided keys/certificates (e.g. if they are valid for signing/" +"encrypting and if they aren't expired)." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:2 -msgid "Admin Panel Reference" +#: ../settings/security/third-party/saml.rst:199 +msgid "" +"See :ref:`automatic account linking ` for details " +"on how to link existing Zammad accounts to IdP accounts." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:None -msgid "Screenshot of Checkmk settings overview" +#: ../settings/security/third-party/saml.rst:205 +msgid "Automatic account linking doesn't work" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:12 +#: ../settings/security/third-party/saml.rst:206 msgid "" -"Which :doc:`group ` should Checkmk tickets be assigned " -"to as a default (*i.e.,* when none is specified)?" +"Have you double-checked your IdP's user attribute mapping configuration?" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:15 -msgid "(Applies to :ref:`API alerts ` only.)" +#: ../settings/security/third-party/twitter.rst:4 +msgid "" +"It is possible to create a quick login for your helpdesk via Twitter. To do " +"so, you need to follow these steps:" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:21 -msgid "Auto close" +#: ../settings/security/third-party/twitter.rst:8 +msgid "Register Twitter App" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:18 -msgid "" -"Should Zammad automatically close tickets if a service has recovered on its " -"own?" +#: ../settings/security/third-party/twitter.rst:10 +msgid "Go to https://dev.twitter.com/apps and login with your account." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:21 -msgid "(Agents will receive notifications for such closures as appropriate.)" +#: ../settings/security/third-party/twitter.rst:15 +msgid "Click on \"Create App\"" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:30 -msgid "Auto-close state" +#: ../settings/security/third-party/twitter.rst:None +msgid "new app page" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:24 -msgid "What ticket state should be applied when “auto-closing” a ticket?" +#: ../settings/security/third-party/twitter.rst:20 +msgid "" +"Enter app settings. As \"Callback URL\" you need to enter ``https://" +"zammad_host/api/v1/external_credentials/twitter/callback``. You need to " +"replace ``zammad_host`` with the domain of your Zammad system." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:26 +#: ../settings/security/third-party/twitter.rst:24 msgid "" -"You can choose from the seven built-in ticket states. If these states aren't " -"enough for you, you can :ref:`define a new ticket state ` for this purpose as well. This can be useful for tracking " -"tickets with :doc:`reports `, for example." +"After the app has been created, update the application icon and organization " +"attributes." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:35 -#: ../system/integrations/cti/includes/recent-logs.include.rst:2 -#: ../system/integrations/ldap/index.rst:74 -#: ../system/integrations/pgp/index.rst:106 -msgid "Recent Logs" +#: ../settings/security/third-party/twitter.rst:None +msgid "set permissions to receive and send direct messages" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:None -msgid "Screenshot of Checkmk \"Recent Logs\" section" +#: ../settings/security/third-party/twitter.rst:30 +msgid "" +"Next we need to set ``read, write and access direct messages`` permissions " +"for the app." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:41 -msgid "" -"If you're having trouble getting Zammad and Checkmk to play nicely together, " -"this section can help you troubleshoot." +#: ../settings/security/third-party/twitter.rst:None +msgid "click on Keys & Access Token, note them" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:44 +#: ../settings/security/third-party/twitter.rst:36 msgid "" -"It contains a record of the fifty most recent transactions that Zammad knows " -"about, including each one's request/response details and return status." +"Go to \"Keys and Access Token\" tab and note the \"Consumer Key\" and " +"\"Consumer Secret\"." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:2 -msgid "API Reference" +#: ../settings/security/third-party/twitter.rst:40 +msgid "Configure Zammad as Twitter App" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:4 +#: ../settings/security/third-party/twitter.rst:42 msgid "" -"For most users, :ref:`the sample scripts from the Setup Guide ` will do the job just fine. But if you want more fine-grained control" -"—for instance, to create high- and low-priority tickets for different types " -"of system events—then you'll have to customize the data those scripts send " -"to Zammad." +"Go to \"Admin > Security > Twitter > Third Party Applications > Twitter\" " +"Section." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:15 -msgid "" -"This custom script will automatically set all tickets it creates to **high " -"priority** and **assign them to charlie@chrispresso.com**." +#: ../settings/security/third-party/twitter.rst:None +msgid "Admin > Security > Third Party Applications" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:32 -msgid "How Does it Work?" +#: ../settings/security/third-party/twitter.rst:48 +msgid "" +"Fill in the \"Twitter Key\" and the \"Twitter Secret\" and click the " +"\"Submit\" button." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:34 +#: ../settings/security/third-party/twitter.rst:51 msgid "" -"There are two kinds of data you can pass to the API, both in the form of key-" -"value pairs:" +"Now you can link accounts via \"Avatar > Profile > Link Accounts\" or login " +"via Zammad login page." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:44 -msgid "Checkmk parameters" +#: ../settings/security/two-factor.rst:11 +msgid "Two-factor Authentication Methods" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:38 -msgid "" -"are required, and make up the **contents** of the resulting tickets/" -"articles. They also determine whether an event creates a new ticket or " -"updates/closes an existing one." +#: ../settings/security/two-factor.rst:2 +msgid "Two-Factor Authentication" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:42 +#: ../settings/security/two-factor.rst:4 msgid "" -"These are the only values used in the sample scripts. **Use them as-is**; " -"technically, they can be customized, but it's hard to imagine a good reason " -"for it." +"Two-factor authentication (2FA) enhances the security of Zammad accounts by " +"adding an extra layer of verification beyond a password. It requires users " +"to provide two different types of authentication factors, typically " +"something they know (like a password) and something they possess (like a " +"mobile device or a security token), to ensure that only authorized " +"individuals can access the account." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:52 -msgid "Ticket attributes" +#: ../settings/security/two-factor.rst:19 +msgid "Enable Recovery Codes" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:47 +#: ../settings/security/two-factor.rst:21 msgid "" -"are optional, and can be used to **adjust settings** on newly created " -"tickets (*e.g.,* set the owner, group, priority, or state)." +"Recovery codes are one-time use security codes that can be used by the user " +"if they lose access to their other two-factor authentication methods. They " +"cannot be used on their own, they can only be activated if at least one two-" +"factor authentication method is enabled." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:50 -msgid "" -"If you want to customize your Checkmk alert script, do it with these. Simply " -"add an extra “form” option for each one (``-F \"key=value\"``) to your " -"script's ``curl`` command line, as in the example above." +#: ../settings/security/two-factor.rst:None +msgid "Enable Recovery Codes Setting" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:54 -msgid "💡 **It's just an API endpoint!**" +#: ../settings/security/two-factor.rst:30 +msgid "" +"Recovery codes can only be used as a backup method. If enabled, they will be " +"automatically generated for the user once they set up their initial two-" +"factor authentication method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:56 +#: ../settings/security/two-factor.rst:34 msgid "" -"When using Checkmk integration, messages need to be formatted in a certain " -"way, but that *doesn't mean the messages actually have to come from Checkmk*." +"The user will be asked to print out or save the generated recovery codes in " +"a safe place. Once used, a recovery code cannot be reused." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:59 +#: ../settings/security/two-factor.rst:37 msgid "" -"If you use another monitoring tool that's not officially supported by " -"Zammad, there's probably a way to make it work with your Checkmk callback " -"URL." +"Users will also have an option to regenerate their recovery codes at any " +"time, which invalidates already existing recovery codes and provides them " +"with a list of fresh codes." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:63 -msgid "Checkmk Parameters" +#: ../settings/security/two-factor.rst:41 +msgid "" +"After you enable this setting, when the user completes a setup of their " +"initial two-factor authentication method, they will be presented with a list " +"of recovery codes and instructed to save them for later use." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:65 -msgid "" -"When a notification is received, Zammad creates a new article containing the " -"details of the event that triggered it:" +#: ../settings/security/two-factor.rst:None +msgid "Recovery Codes Generation Modal Dialog" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:None -msgid "Checkmk article body" +#: ../settings/security/two-factor.rst:50 +msgid "Enforce the Set Up of the Two-Factor Authentication" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:72 +#: ../settings/security/two-factor.rst:52 msgid "" -"These details come from the fields listed below, which correspond to " -"parameters provided by Checkmk (``$NOTIFY_*``)." +"In case you wish to require your users to set up at least one two-factor " +"authentication method for their account, you can do this by selecting " +"specific user roles the requirement applies to in **Enforced for user " +"roles** setting. Of course you must have at least one two-factor " +"authentication method enabled for this setting to take effect." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:75 -msgid "**Required fields are marked with an asterisk (\\*).**" +#: ../settings/security/two-factor.rst:None +msgid "Enforced for User Roles Setting" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:79 -msgid "event_id\\*" +#: ../settings/security/two-factor.rst:62 +msgid "" +"After you change this setting, if the user has one of the selected roles on " +"their account, they will be forced to set up the two-factor authentication " +"upon next sign in or application reload." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:78 +#: ../settings/security/two-factor.rst:66 msgid "" -"A unique ID for the system event. (``$NOTIFY_SERVICEPROBLEMID`` / " -"``$NOTIFY_HOSTPROBLEMID``)" +"A modal dialog with instructions will be shown, and they will not be able to " +"do any work before they set up at least one two-factor method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:86 -msgid "host\\*" +#: ../settings/security/two-factor.rst:None +msgid "Modal Dialog for Enforcing Two-Factor Authentication Set Up" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:82 +#: ../settings/security/two-factor.rst:74 +msgid "Reset Two-Factor Authentication for a Specific User" +msgstr "" + +#: ../settings/security/two-factor.rst:76 msgid "" -"The hostname of the system that the event originated from. " -"(``$NOTIFY_HOSTNAME``)" +"In case an user isn't able to login anymore because of an inaccessible " +"second factor, you can reset the user's 2FA method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:85 +#: ../settings/security/two-factor.rst:79 msgid "" -"Used to determine if a new event belongs to an existing ticket. Also used in " -"the subject line of the resulting article (“ is ”)." +"To do this, go to the user management and search for the relevant user. " +"After you found the account, click the button in the action column and " +"select \"Manage Two-Factor Authentication\":" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:96 -msgid "service" +#: ../settings/security/two-factor.rst:None +msgid "Context menu in action column in user management" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:89 +#: ../settings/security/two-factor.rst:87 msgid "" -"The name of the service that the event originated from. " -"(``$NOTIFY_SERVICEDESC``)" +"After selecting this, you can see a dialog where you can either reset one " +"2FA method or reset all of the user's 2FA methods:" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:92 -msgid "Used to determine if a new event belongs to an existing ticket." +#: ../settings/security/two-factor.rst:None +msgid "Dialog for resetting user's 2FA method" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:94 -#: ../system/integrations/checkmk/api-reference.rst:110 -msgid "Displayed as ``-`` when omitted." +#: ../settings/security/two-factor.rst:94 +msgid "" +"Choose the fitting one, click on the corresponding \"Remove ...\" button and " +"confirm your action. The user now has to setup a new 2FA method, depending " +"on your 2FA configuration." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:104 -msgid "state\\*" +#: ../settings/security/two-factor/authenticator-app.rst:2 +msgid "Authenticator App" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:99 +#: ../settings/security/two-factor/authenticator-app.rst:4 msgid "" -"The current state of the service or host in question. " -"(``$NOTIFY_SERVICESTATE`` / ``$NOTIFY_HOSTSTATE``)" +"The authenticator app method is a type of two-factor authentication that " +"uses a mobile application to generate one-time codes for account " +"verification. After setting up the authenticator app on their device, the " +"user links it to their Zammad account." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:102 +#: ../settings/security/two-factor/authenticator-app.rst:12 msgid "" -"Used to detect when a ticket should be auto-closed (*i.e.,* on ``OK``/" -"``UP``). Also used in the subject line of the resulting article (“ is " -"”)." +"When logging in, the user is prompted to enter a time-sensitive code " +"generated by the app, in addition to their password. This code acts as the " +"second factor of authentication, providing an extra layer of security as it " +"changes periodically and is unique to the user's device." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:110 -msgid "text" +#: ../settings/security/two-factor/authenticator-app.rst:None +msgid "Security Code in Google Authenticator App" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:107 +#: ../settings/security/two-factor/authenticator-app.rst:22 msgid "" -"The output of the process that triggered the event. " -"(``$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" +"The app generates codes based on a shared secret key stored securely on both " +"the user's device and the server, ensuring a synchronized and secure " +"authentication process. The method of generating the codes is sometimes also " +"called TOTP (time-based one-time password)." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:121 -msgid "" -"The Object Manager attribute panel displays built-in and custom\n" -"attribute names." +#: ../settings/security/two-factor/authenticator-app.rst:28 +msgid "Enabling the Authenticator App Method" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:121 -msgid "Find a complete list of ticket attributes in the Object Manager." +#: ../settings/security/two-factor/authenticator-app.rst:30 +#: ../settings/security/two-factor/security-keys.rst:28 +msgid "To enable the method, just toggle the switch on in the settings." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:123 -msgid "" -"Ticket attributes are entirely optional, and can be used to customize the " -"tickets that Checkmk creates. (Note that these attributes will be ignored if " -"a new event belongs to an existing ticket.)" +#: ../settings/security/two-factor/authenticator-app.rst:None +msgid "Authenticator App Switch in Settings" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:128 +#: ../settings/security/two-factor/authenticator-app.rst:36 msgid "" -"Why would you want to do this? Maybe you have only one IT guy, and all " -"system monitoring issues should be automatically assigned to him. Or, maybe " -"you're creating multiple notification rules so that database outages take " -"higher priority than disk space warnings." +"Now the users will be able to set up this two-factor authentication method " +"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " +"Once they do, on next sign-in with password, they will be asked to provide " +"an additional security code generated by their mobile device." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:135 -msgid "In most cases, you'll probably want to set one of the following:" +#: ../settings/security/two-factor/security-keys.rst:2 +msgid "Security Keys" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:137 -msgid "group" +#: ../settings/security/two-factor/security-keys.rst:4 +msgid "" +"The security keys method is a type of a two-factor authentication that uses " +"Web Authentication API in the browser for verifying user's identity. The " +"user can register multiple hardware or software security keys with their " +"Zammad account and then they can use it during the sign-in process." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:139 -msgid "state" +#: ../settings/security/two-factor/security-keys.rst:12 +msgid "" +"When logging in, the user is prompted to provide the same security key they " +"registered with their account, in addition to their password. This key acts " +"as the second factor of authentication, providing an extra layer of security." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:140 -msgid "priority" +#: ../settings/security/two-factor/security-keys.rst:None +msgid "Security Key dialog in Safari on macOS" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:142 +#: ../settings/security/two-factor/security-keys.rst:21 msgid "" -"but in practice, you can set almost any attribute, including :doc:`custom " -"ones you created through the Object Manager `." -msgstr "" - -#: ../system/integrations/checkmk/api-reference.rst:145 -msgid "Please note that the following attributes are **not customizable**:" +"The type of the key can range from hardware USB sticks to passkeys stored in " +"a device of user's choice. Which type can be used depends on the browser " +"flavor and the platform of the user." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:147 -msgid "title" +#: ../settings/security/two-factor/security-keys.rst:26 +msgid "Enabling the Security Keys Method" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:148 -msgid "id" +#: ../settings/security/two-factor/security-keys.rst:None +msgid "Security Keys Switch in Settings" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:149 -msgid "ticket number" +#: ../settings/security/two-factor/security-keys.rst:34 +msgid "" +"Now the users will be able to set up this two-factor authentication method " +"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " +"Once they do, on next sign-in with password, they will be asked to provide " +"the same security key they registered during the setup." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:151 -msgid "created_by_id" +#: ../settings/system/system-selfhosted.include.rst:3 +msgid "" +"Below settings are only available to self hosted users. In hosted " +"environments we're handling these settings for you to ensure service " +"stability." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:152 -msgid "updated_by_id" +#: ../settings/system/base.rst:11 +msgid "Fully Qualified Domain Name" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:155 -msgid "Which Values Can Be Set?" +#: ../settings/system/base.rst:7 +msgid "The URL of your Zammad installation." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:157 -msgid "😵 **Invalid values → unpredictable behavior**" +#: ../settings/system/base.rst:9 ../settings/system/base.rst:17 +msgid "This setting is used within :doc:`/misc/variables` and notifications." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:159 -msgid "" -"If you provide a value that Zammad doesn't understand (*e.g.,* ``-F " -"\"priority=high\"``), it's not always clear what will happen. In some cases, " -"a ticket will be created with the default values instead - but in others, it " -"may not be created at all!" +#: ../settings/system/system-base.include.rst:1 +msgid "It is automatically set by the *Getting Started wizard*." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:164 -msgid "So what values does Zammad understand, then? Well, it depends..." +#: ../settings/system/system-base.include.rst:5 +msgid "Changing this setting also changes callback URLs for your channels etc." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:168 -msgid "Use an email address or username:" +#: ../settings/system/system-base.include.rst:6 +msgid "This setting can have negative affects on being able to login." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:190 -msgid "group & priority" +#: ../settings/system/base.rst:19 +msgid "HTTP type" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:175 -msgid "Refer to the dropdown menus in the ticket pane:" +#: ../settings/system/base.rst:14 +msgid "" +"The HTTP type tells your installation how your clients connect. This is " +"relevant for authentication and cookie security." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:0 -msgid "See possible values for certain attributes in the ticket pane." +#: ../settings/system/base.rst:31 +msgid "SystemID" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:187 -msgid "🙅 **Ticket state CANNOT be set this way!**" +#: ../settings/system/base.rst:22 +msgid "" +"This ID is being used within your ticket number. In case you're " +"communicating with another ticket system with similar ticket number schemes " +"this ID greatly reduces the risk of false follow ups." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:189 +#: ../settings/system/base.rst:26 msgid "" -"Why? Because ``-F \"state=...\"`` is already used :ref:`as a Checkmk " -"parameter `." +"The SystemID is randomly selected upon installation of Zammad (``1-99``)." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:222 -msgid "Everything Else" +#: ../settings/system/base.rst:30 +msgid "" +"**Do not** change this setting in a productive system! Your Zammad " +"installation may no longer recognize old ticket number based follow ups upon " +"change!" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:193 -msgid "" -"To set any other attributes, it helps to know your way around the :docs:" -"`rails console `. Valid values are those that you can " -"set with a string:" +#: ../settings/system/frontend.rst:2 +msgid "Frontend" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:218 -msgid "These values can then be passed directly to the API:" +#: ../settings/system/frontend.rst:22 +msgid "Core Workflow Ajax Mode" msgstr "" -#: ../system/integrations/checkmk/index.rst:16 -msgid "How does it work?" +#: ../settings/system/frontend.rst:6 +msgid "" +"This setting allows administrators to enforce :doc:`/system/core-workflows` " +"to use Ajax-Calls instead of web sockets. You'll usually only need this if " +"you experience serious issues as noted below." msgstr "" -#: ../system/integrations/checkmk/index.rst:2 -msgid "Checkmk" +#: ../settings/system/frontend.rst:10 +msgid "**🤓 Possible (technical) reasons**" msgstr "" -#: ../system/integrations/checkmk/index.rst:4 +#: ../settings/system/frontend.rst:12 msgid "" -"`Checkmk `_ is a powerful IT monitoring tool that can " -"send real-time status alerts to Zammad via email or REST API. Set these " -"alerts up in Checkmk, and Zammad will automatically create, update, and " -"close tickets based on the health of your system:" +"In some cases, your network structure (e.g. firewalls, proxies) may " +"disconnect long web socket connections. This leads to select fields staying " +"empty (e.g. owner selection *after* selecting your group) or fields not " +"shown / hidden (e.g. when switching to or from pending states, the \"pending " +"till\" field not showing / hiding)." msgstr "" -#: ../system/integrations/checkmk/index.rst:14 -msgid "Screenshot of ticket created by Checkmk notifications" +#: ../settings/system/frontend.rst:18 +msgid "" +"Please keep in mind that the Ajax fallback may cause serious pressure on " +"your application server. If you have the choice stick to web sockets." msgstr "" -#: ../system/integrations/checkmk/index.rst:14 -msgid "Multiple alerts, same ticket." +#: ../settings/system/frontend.rst:22 +msgid "Default: ``no`` (inactive)" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:2 -msgid "Setup Guide" +#: ../settings/system/frontend.rst:53 +msgid "Show calendar weeks in the picker of date/datetime fields" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:4 +#: ../settings/system/frontend.rst:25 msgid "" -"Whenever the Checkmk integration is enabled, Zammad listens for messages on " -"its API and over email. As long as those messages follow the required " -"format, Zammad will create new tickets (or find and update existing ones) " -"based on the message contents." +"With this setting you can instruct Zammad to provide week number display " +"globally for all users. Calendar with week number display are usually used " +"in business sectors and may not be relevant for everyone." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:10 +#: ../settings/system/frontend.rst:29 msgid "" -"That means that “setting up Checkmk integration” is simply a matter of " -"**adding configuration to your Checkmk site**: telling it when to send these " -"messages and what to say. To do that, you'll need to create a new " -"**notification rule** (see `Checkmk's official docs `_ for help with that)." +"This setting affects *all areas* - you'll also see week numbers in the admin " +"panel for e.g. triggers and macros." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:17 -msgid "" -"As part of this new rule, you'll have to choose a **notification method** " -"(*i.e.,* a script to execute whenever the rule is triggered). This script " -"will be written by you (samples below), and contain the logic for sending " -"API/email messages to Zammad:" +#: ../settings/system/frontend.rst:32 +msgid "Default: ``no`` (not shown)" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:26 -msgid "Checkmk \"New Rule\" dialog" +#: ../settings/system/frontend.rst:53 +msgid "Here's the difference:" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:26 -msgid "" -"Find your custom scripts in the Checkmk WATO under **Notifications > New " -"Rule > Notification Method**." +#: ../settings/system/frontend.rst:0 +msgid "Screenshot showing Zammad's date picker (in the default way)" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:29 -msgid "" -"Once you're done setting up your new rule, you're all set! New tickets " -"should start coming in and auto-updating any time your rule is triggered." +#: ../settings/system/frontend.rst:41 +msgid "Set to ``no``" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:33 +#: ../settings/system/frontend.rst:0 msgid "" -"(If you need help troubleshooting, be sure to check the :ref:`checkmk-recent-" -"logs`.)" +"Screenshot showing Zammad's date picker with\n" +"week numbers enabled" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:38 -msgid "API Alerts" +#: ../settings/system/frontend.rst:50 +msgid "Set to ``yes``" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:40 +#: ../settings/system/index.rst:4 msgid "" -"To add these scripts in the Checkmk WATO, copy them into your Checkmk " -"installation directory and make them executable. (Be sure to replace the " -"``zammad.example.com`` callback URL with the one found in your admin panel.)" +"For your overview we split each tab within system settings into its own page:" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:60 -msgid "Service notification" +#: ../settings/system/index.rst:16 +msgid "Console Based Settings" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:46 +#: ../settings/system/index.rst:18 msgid "" -"For updates on the status of the software running on your server (*e.g.,* " -"postgres)." +"There's some console based settings we didn't put into the UI. However, you " +"may find them helpful - you can find them in our :docs:`hidden settings ` section." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:75 -msgid "Host notification" +#: ../settings/system/network.rst:2 +msgid "Network" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:63 -msgid "For updates on the status of the server itself." +#: ../settings/system/network.rst:8 +msgid "" +"The proxy settings can only be saved after successfully testing the proxy " +"connection." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:77 -msgid "🤔 **What's with all the env vars?**" +#: ../settings/system/network.rst:15 +msgid "Proxy Address." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:79 +#: ../settings/system/network.rst:12 msgid "" -"Whenever Checkmk runs these scripts, it needs to provide some information " -"about the event that triggered the notification. This information is passed " -"in the form of these ``$NOTIFY_*`` environment variables." +"Allows you to provide a proxy server if needed. This is relevant for network " +"communication by Zammad." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:85 -msgid "" -"You can specify additional parameters to pass to the script when you're " -"setting up your notification rule, but the ones you see here are all " -"provided by default." +#: ../settings/system/network.rst:15 +msgid "It **does not** affect the update process or Elasticsearch." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:90 -msgid "Email Alerts" +#: ../settings/system/network.rst:18 +msgid "Username for proxy connection." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:94 +#: ../settings/system/network.rst:18 msgid "" -"🐞 **There are known bugs** in Zammad's processing of email from Checkmk. " -"This section will be completed once they have been resolved. (Learn more at " -"GitHub issues `#2377 `_ & " -"`#2180 `_.)" +"If your proxy server requires authentication, provide the username here." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:100 -msgid "In the meantime, we encourage you to set up API alerts instead." +#: ../settings/system/network.rst:21 +msgid "Password for proxy connection." msgstr "" -#: ../system/integrations/clearbit.rst:2 -msgid "Clearbit" +#: ../settings/system/network.rst:21 +msgid "" +"If your proxy server requires authentication, provide the password here." msgstr "" -#: ../system/integrations/clearbit.rst:4 +#: ../settings/system/network.rst:26 +msgid "No proxy for the following hosts." +msgstr "" + +#: ../settings/system/network.rst:24 msgid "" -"With our Clearbit integration, you can easily enrich the information " -"provided by Zammad. If the customers or agents email address is known to " -"Clearbit, it will share all information it has regarding the user with " -"Zammad. Those information can include the following:" +"Exception list for hosts you can't or don't want to reach via proxy server." msgstr "" -#: ../system/integrations/clearbit.rst:9 -msgid "Avatar" +#: ../settings/system/network.rst:27 +msgid "Default: ``localhost,127.0.0.0,::1``" msgstr "" -#: ../system/integrations/clearbit.rst:10 -msgid "Address information" +#: ../settings/system/services.rst:2 +msgid "Services" msgstr "" -#: ../system/integrations/clearbit.rst:11 -msgid "Website information" +#: ../settings/system/services.rst:10 +msgid "Image Service" msgstr "" -#: ../system/integrations/clearbit.rst:12 -msgid "A BIO (as Note by default)" +#: ../settings/system/services.rst:5 +msgid "Defines the backend for user and organization image lookups." msgstr "" -#: ../system/integrations/clearbit.rst:14 -msgid "" -"If needed, you can add further custom objects and add mappings to them, so " -"the Clearbit information can be filled within the database. In general you " -"can get any information from Clearbit, as long as you have a mapping to an " -"Zammad object." +#: ../settings/system/services.rst:7 +msgid "Default: ``Zammad Image Service`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:21 +#: ../settings/system/services.rst:9 msgid "" -"Clearbit does have a mapping of fields like LDAP and Exchange have, but does " -"not \"win\" against Zammad information. This means that if you have e.g. the " -"last name field filled in already and Clearbit has other information on " -"that, it will not be updated." +"Make sure your on premise installation has ``HTTPS`` access to ``images." +"zammad.com``." msgstr "" -#: ../system/integrations/clearbit.rst:26 -msgid "" -"However: If let's say the last name has been set by Clearbit and Zammad " -"notices that the last name on the Clearbit source has changed, Zammad will " -"also update this value." +#: ../settings/system/services.rst:18 +msgid "Geo Calendar Service" msgstr "" -#: ../system/integrations/clearbit.rst:33 +#: ../settings/system/services.rst:13 msgid "" -"The configuration of Clearbit is really easy and done fast! Just login to " -"your Clearbit-Account, go to \"API\" and copy the secret-API-Key." +"Defines the backend for geo calendar lookups. Used for initial calendar " +"setup." msgstr "" -#: ../system/integrations/clearbit.rst:38 -msgid "" -"Now change to your Zammad instance, go to Integrations (System) -> Clearbit " -"in the admin panel. Paste your API-Key into the API-Key-Field and decide if " -"Zammad should create unknown Organizations automatically, if the user does " -"not have one yet (and Clearbit knows it). The shared option decides if the " -"new organizations Zammad creates with Clearbit should be shared ones." +#: ../settings/system/services.rst:16 +msgid "Default: ``Zammad GeoCalendar Service`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:47 +#: ../settings/system/services.include.rst:2 msgid "" -"If you're unsure what option to choose, better stick with \"no\". You can " -"also learn more about :doc:`/manage/organizations/index`." +"Make sure your on premise installation has ``HTTPS`` access to ``geo.zammad." +"com``." msgstr "" -#: ../system/integrations/clearbit.rst:52 -msgid "" -"The Mapping option works similar to the mapping within the Exchange and LDAP " -"sync. You can add further mappings for e.g. custom fields if you need more " -"information that Clearbit can provide." +#: ../settings/system/services.rst:26 +msgid "Geo IP Service" msgstr "" -#: ../system/integrations/clearbit.rst:58 +#: ../settings/system/services.rst:21 msgid "" -"If you want to add more Clearbit fields and want to learn more about " -"available fields on their API, you can take a look at their `API " -"documentation `_." +"Defines the backend for geo IP lookups. Shows also location of an IP address " +"if an IP address is shown." msgstr "" -#: ../system/integrations/clearbit.rst:62 -msgid "" -"If you're happy with the above chosen Settings and your mapping, just save " -"the changes and enable Clearbit integration. Zammad will now start polling " -"the Clearbit API as users contact you." +#: ../settings/system/services.rst:24 +msgid "Default: ``Zammad GeoIP Service`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:68 -msgid "" -"Zammad does not synchronize with Clearbit on a regular basis, but on demand " -"if needed. This saves API calls." +#: ../settings/system/services.rst:32 +msgid "Geo Location Service" msgstr "" -#: ../system/integrations/clearbit.rst:73 +#: ../settings/system/services.rst:29 msgid "" -"Below the Settings and Mappings, you'll find our Integration log. You can " -"see what requests Zammad sent to Clearbit and also the APIs Response." +"Defines the backend for geo location lookups to store geo locations for " +"addresses." msgstr "" -#: ../system/integrations/clearbit.rst:78 +#: ../settings/system/services.rst:32 msgid "" -"By the way, you can also view the API log on the Clearbit website - the " -"information seen is basically the same." -msgstr "" - -#: ../system/integrations/clearbit.rst:84 -msgid "Example When Adding a User" +"Default: ``OpenStreetMap (ODbL 1.0, http://osm.org/copyright)`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:86 +#: ../settings/system/services.rst:36 msgid "" -"To show you how fast information is added, we added a small Screencast " -"below. This shows the creation of the User Alex from Clearbit. As we already " -"set the last name of Alex to \"X\", Zammad did not update it. What Zammad " -"did was to add further information it received from Clearbit." +"You can find a detailed privacy information on what we store for how long on " +"our :docs:`Privacy Appendix ` inside of our System " +"Documentation." msgstr "" -#: ../system/integrations/cti/generic.rst:2 -msgid "CTI (generic)" +#: ../settings/system/storage.rst:2 +msgid "Storage" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:1 +#: ../settings/system/storage.rst:6 msgid "" -"This integration enables Zammad to provide a caller log to your agents. With " -"this your agents can greet your customers by their name and are supported by " -"Zammad with automatically opening a new ticket dialog or the user profile." +"Here you can define where Zammad stores attachments for tickets and the " +"knowledge base. By default, we're writing to the ``Database`` - you can " +"switch to ``Filesystem`` or ``Simple Storage (S3)`` at any time. In this " +"case please have a look on the following instructions." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:6 +#: ../settings/system/storage.rst:11 msgid "" -"Click the toggle next to the heading to activate or deactivate this " -"integration." +"If you have a busy Zammad instance, we strongly encourage you to use " +"filesystem storage instead of \"Database\". This will greatly improve system " +"performance (de-crease database load and size)." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:9 -msgid "" -"If you want to learn more on how your agents can use this function, please " -"refer the :user-docs:`user documentation `." +#: ../settings/system/storage.rst:19 +msgid "Database" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:14 +#: ../settings/system/storage.rst:17 msgid "" -"Automatically opening new ticket dialogues or user profiles requires agent " -"to extension mapping - see more below." -msgstr "" - -#: ../system/integrations/cti/includes/introduction.include.rst:20 -msgid "Please note the following limitations to reduce confusion later on:" +"This is the default storage method. The attachments are stored directly in " +"the database. If your Zammad instance grows, we recommend one of the other " +"methods to maintain performance." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:22 -msgid "CTI integrations provide caller log functions only." +#: ../settings/system/storage.rst:38 +msgid "Filesystem" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:23 +#: ../settings/system/storage.rst:22 msgid "" -"This integration does not provide any VoIP functionalities; you can't make " -"phone calls from within Zammad." +"This storage method is recommended for all Zammad instances, especially for " +"those with a higher load. If you choose filesystem, your files are written " +"to ``/opt/zammad/storage/``." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:25 +#: ../settings/system/storage.rst:26 msgid "" -"If your browser supports ``tel``-URLs, you can click on phone numbers for " -"automatic dialing. This requires additional software / configuration on your " -"agent's computers." +"Moving attachments from \"Database\" to \"Filesystem\" can be run during " +"production use. However, you should consider your framework conditions (e.g. " +"bandwidth, system load in production) to define the right moment." msgstr "" -#: ../system/integrations/cti/generic.rst:9 -#: ../system/integrations/cti/placetel.rst:14 -#: ../system/integrations/cti/sipgate.rst:14 -msgid "Please provide the following requirements:" +#: ../settings/system/storage.rst:32 +msgid "**You noticed slow updates of Zammad?**" msgstr "" -#: ../system/integrations/cti/generic.rst:11 +#: ../settings/system/storage.rst:34 msgid "" -"A telephone system that supports webhooks (outbound) (best option are those " -"that allow customizing the calls)." +"While Zammad is beeing updated, it enforces a recursive \"change " +"owner\" (chown) for this directory. For instances with many files this can " +"be time consuming. To mitigate that you can move your files and create a " +"symlink in ``/opt/zammad/storage/`` to the new directory. Of course you have " +"to make sure on your own that the permissions are always correct." msgstr "" -#: ../system/integrations/cti/generic.rst:13 -msgid "A unique Call-ID during the call session." +#: ../settings/system/storage.rst:95 +msgid "Simple Storage (S3)" msgstr "" -#: ../system/integrations/cti/generic.rst:14 -msgid "Call event data (both numbers and direction)." +#: ../settings/system/storage.rst:41 +msgid "" +"To use the Simple Storage (S3), you have to provide some settings, which " +"can't be accessed in the UI (see instructions below)." msgstr "" -#: ../system/integrations/cti/generic.rst:15 -msgid "Your Zammad instance must be reachable for your telephony system." +#: ../settings/system/storage.rst:44 +msgid "" +"⚠️ Please note that the current implementation is in its early stages and can " +"be modified in the future." msgstr "" -#: ../system/integrations/cti/generic.rst:17 +#: ../settings/system/storage.rst:47 msgid "" -"If you want to learn more on what kind of requests are supported by Zammad " -"and what it expects, please consult our :docs:`CTI-API documentation `." +"The prerequisite is to have access to a S3-compatible storage and to have " +"all necessary parameters available (which depends on your storage provider; " +"if in doubt, please ask there for help)." msgstr "" -#: ../system/integrations/cti/generic.rst:22 -#: ../system/integrations/cti/placetel.rst:27 -#: ../system/integrations/cti/sipgate.rst:30 -msgid "Available Settings" +#: ../settings/system/storage.rst:51 +msgid "Steps to configure S3:" msgstr "" -#: ../system/integrations/cti/generic.rst:29 -#: ../system/integrations/cti/placetel.rst:41 -#: ../system/integrations/cti/sipgate.rst:40 -msgid "Endpoint Settings" +#: ../settings/system/storage.rst:53 +msgid "" +"Copy ``config/zammad/storage.yml.dist`` to ``config/zammad/storage.yml``" msgstr "" -#: ../system/integrations/cti/generic.rst:25 -msgid "" -"Zammad will list your generic CTI endpoint here. It contains a unique token " -"so ensure to keep this URL save." +#: ../settings/system/storage.rst:54 +msgid "Edit the copied file in one of the following ways:" msgstr "" -#: ../system/integrations/cti/generic.rst:28 +#: ../settings/system/storage.rst:56 msgid "" -"You'll need this endpoint for your PBX to talk to Zammad, see :docs:`CTI-API " -"documentation `." +"Either provide your S3 configuration with one attribute per line like in the " +"upper area of the file" msgstr "" -#: ../system/integrations/cti/includes/important-dont-forget-saving.include.rst:3 +#: ../settings/system/storage.rst:58 msgid "" -"All following options **do not save automatically**. Always use the Save " -"button on the lower end of the integration page!" +"Or provide your S3 configuration as an URL (which you can find at the end of " +"the file). Note: you can also provide this URL as environment variable (:" +"docs:`see system documentation `) without using this yml-file." msgstr "" -#: ../system/integrations/cti/generic.rst:43 -#: ../system/integrations/cti/placetel.rst:49 -#: ../system/integrations/cti/sipgate.rst:52 -msgid "Call Settings" +#: ../settings/system/storage.rst:62 +msgid "" +"We recommend the deletion of the not used configuration style to avoid " +"inconsistencies." msgstr "" -#: ../system/integrations/cti/generic.rst:39 -#: ../system/integrations/cti/placetel.rst:49 -#: ../system/integrations/cti/sipgate.rst:37 -#: ../system/integrations/cti/sipgate.rst:50 -msgid "Inbound" +#: ../settings/system/storage.rst:65 +msgid "Restart Zammad so the config file / environment variable is loaded" msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:1 +#: ../settings/system/storage.rst:66 msgid "" -"This option allows you to block specific incoming caller IDs. It allows you " -"to temporarily reject e.g. spam callers without having to contact providers " -"or PBX administrators." +"Set the \"Storage Method\" in Zammad to ``Simple Storage (S3)`` in Settings " +"> System > Storage and click on \"Submit\". After that, Zammad checks your " +"configuration and the connection to the service and will raise an error " +"message if something is wrong." msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:11 -msgid "Caller ID to block" +#: ../settings/system/storage.rst:72 +msgid "A very simple storage configuration could look like this:" msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 -msgid "Provide caller IDs to block in ``E.164`` format." +#: ../settings/system/storage.rst:85 +msgid "" +"Before setting the storage method to ``Simple Storage (S3)`` (step 4), " +"please make sure to have a working setup." msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:8 +#: ../settings/system/storage.rst:88 msgid "" -"Your telephony system has to support this function. Zammad will send a " -"``reject`` response which will cause your telephony system to hang up the " -"call. To callers this usually will feel like the line is busy." +"You can verify this by running ``rails r 'Rails.logger = Logger.new(STDOUT); " +"pp Store::Provider::S3.ping?'`` in your Zammad directory. If everything is " +"fine, you should see ``true``, else you should see ``false`` and a simple " +"error message." msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:14 +#: ../settings/system/storage.rst:93 msgid "" -"Provide a meaningful note for your fellow administrators to remind yourself " -"why you've chosen to block the number." +"If you installed Zammad through a package manager (rather than from source), " +"replace ``rails r`` with ``zammad run rails r`` above. To learn more, see :" +"docs:`Administration via Console `." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 -#: ../system/integrations/cti/includes/outbound-calls.include.rst:17 -#: ../system/integrations/cti/sipgate.rst:40 -msgid "Outbound" +#: ../settings/ticket.rst:4 +msgid "" +"Here you can adjust general ticket settings. Additional ones for the ticket " +"composer interface can be found in the :doc:`/misc/composer`." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:1 -msgid "" -"In many cases you may want to use a different caller ID depending on the " -"destination you're calling. This may apply due to specific connection rates " -"to other countries or because you want your customer to feel you're calling " -"from the same country." +#: ../settings/ticket.rst:11 +msgid "Ticket Hook (default: ``Ticket#``)" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:6 -msgid "This option expects ``E.164`` number formats." +#: ../settings/ticket.rst:11 +msgid "The identifier for a ticket; *e.g.,* Ticket#, Call#, MyTicket#." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 -msgid "Destination caller ID" +#: ../settings/ticket.rst:38 +msgid "Ticket Hook Position (default: ``right``)" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:5 -msgid "The caller ID or number you're trying to call." +#: ../settings/ticket.rst:14 +msgid "" +"With this setting you can decide (if) where to insert the ticket number." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:7 -msgid "You can use wildcards for e.g. country specific outbound numbers like:" +#: ../settings/ticket.rst:20 +msgid "*Right*" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:9 -msgid "``49*`` for Germany" +#: ../settings/ticket.rst:17 +msgid "" +"This setting will add the ticket reference on the right site of the subject." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:10 -msgid "``4930*`` for Berlin / Germany landlines" +#: ../settings/ticket.rst:20 +msgid "Example: ``Some Subject [Ticket#12345]``" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 -msgid "``33*`` for France" +#: ../settings/ticket.rst:26 +msgid "*Left*" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:15 -msgid "Set Outbound caller ID" +#: ../settings/ticket.rst:23 +msgid "" +"This setting will add the ticket reference on the left site of the subject." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:14 -msgid "" -"The outbound caller ID to set (the number your customer sees on his display) " -"in ``E.164`` number format." +#: ../settings/ticket.rst:26 +msgid "Example: ``[Ticket#12345] Some Subject``" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 -msgid "Provide a short description for fellow administrators." +#: ../settings/ticket.rst:29 +msgid "*None*" msgstr "" -#: ../system/integrations/cti/includes/generic-cti-support-note.includes.rst:3 -msgid "" -"This option requires your PBX to send a specific request to Zammad *before " -"dialing*. Please consult the :docs:`CTI API ` in case " -"you're not sure." +#: ../settings/ticket.rst:29 +msgid "This will completely remove ticket references from the subject." msgstr "" -#: ../system/integrations/cti/generic.rst:52 -#: ../system/integrations/cti/placetel.rst:54 -#: ../system/integrations/cti/sipgate.rst:59 -msgid "Other Settings" +#: ../settings/ticket.rst:33 +msgid "" +"Please ensure to take a look at :doc:`/channels/email/settings` within the " +"email channel to ensure you have at least one reference that helps Zammad to " +"assign follow-ups correctly." msgstr "" -#: ../system/integrations/cti/includes/other-settings-intro.include.rst:1 +#: ../settings/ticket.rst:37 msgid "" -"Below you can find all available additional settings for this CTI " -"integration. For your overview we're sorting them by appearance and " -"reference their description first." +"Disabling this and not setting up any further follow up search will lead to " +"unexpected results!" msgstr "" -#: ../system/integrations/cti/includes/default-caller-id.include.rst:2 -#: ../system/integrations/cti/includes/default-caller-id.include.rst:1 -msgid "Default caller ID for outbound calls" +#: ../settings/ticket.rst:65 +msgid "" +"Ticket Last Contact Behaviour (default: ``Use the start time of the last " +"customer thread (which may consist of multiple articles).``)" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:16 -#: ../system/integrations/cti/includes/records-caller-log.include.rst:15 -msgid "Shown records in caller log" +#: ../settings/ticket.rst:41 +msgid "" +"This setting changes the way Zammad updates the ``Last Contact`` value of a " +"ticket. This is fairly important for overviews and what you expect upon " +"ticket updates of a customer." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:2 +#: ../settings/ticket.rst:52 msgid "" -"Allows you to set the number of shown caller log entries for all users. You " -"can choose from the following values:" +"Use the start time of the last customer thread (which may consist of " +"multiple articles)." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:5 -msgid "60 (default)" +#: ../settings/ticket.rst:46 +msgid "" +"If this option is chosen, Zammad will update the last updated value just " +"once if a customer replies. After that, Zammad will wait for an agent to " +"react." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:6 -msgid "120" +#: ../settings/ticket.rst:50 +msgid "" +"This comes in handy if you want to work tickets in the order of their first " +"update. This will not change ticket orders if customers decide to \"bump\" " +"the ticket affected." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:7 -msgid "180" +#: ../settings/ticket.rst:57 +msgid "Use the time of the very last customer article." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:8 -msgid "240" +#: ../settings/ticket.rst:55 +msgid "" +"When setting this option, Zammad will always update the last updated value. " +"This means that if ordering by ``Last Update``, ticket orders will change if " +"customers \"bump\" the ticket." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:9 -msgid "300" +#: ../settings/ticket.rst:64 +msgid "Last contact value used on :doc:`/manage/overviews`" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:11 -msgid "**🥵 Potential performance issue**" +#: ../settings/ticket.rst:65 +msgid "Last contact value used on :doc:`/manage/trigger`" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:13 +#: ../settings/ticket.rst:88 msgid "" -"Setting this setting higher than 60 may cause serious performance issues on " -"very busy instances. Keep in mind that this setting causes Zammad to poll " -"and send up to 300 records to *all active agent sessions* in very short time " -"periods." +"Ticket Organization Reassignment (default: ``Update the most recent tickets." +"``)" msgstr "" -#: ../system/integrations/cti/generic.rst:73 -msgid "Caller Log Filter" +#: ../settings/ticket.rst:68 +msgid "" +"This setting changes the way Zammad updates the organization field of the " +"tickets whenever the primary organization of a user is changed." msgstr "" -#: ../system/integrations/cti/generic.rst:55 -msgid "" -"This function allows you to provide call information based on e.g. queues " -"only to agents that really need the information." +#: ../settings/ticket.rst:74 +msgid "Update the most recent tickets." msgstr "" -#: ../system/integrations/cti/generic.rst:58 +#: ../settings/ticket.rst:72 msgid "" -"Why? If you have a team for several countries or departments, you don't want " -"to bug your agents from other departments. Leaving these options empty will " -"fallback to showing everything to everyone." +"If this option is chosen, Zammad will update the 100 most recent tickets " +"where the user is the ticket customer. The ticket organization field will be " +"automatically set to the new primary organization of the user." msgstr "" -#: ../system/integrations/cti/generic.rst:64 -msgid "Destination caller ID or Queue" +#: ../settings/ticket.rst:88 +msgid "Do not update any tickets." msgstr "" -#: ../system/integrations/cti/generic.rst:63 +#: ../settings/ticket.rst:77 msgid "" -"This depends on your PBX and usually is either a queue ID, phone number or " -"extension." +"When choosing this option, Zammad will not update any tickets when the " +"user's primary organization is changed." msgstr "" -#: ../system/integrations/cti/generic.rst:69 -msgid "Agents" +#: ../settings/ticket.rst:80 +msgid "**Use with care!**" msgstr "" -#: ../system/integrations/cti/generic.rst:67 +#: ../settings/ticket.rst:82 msgid "" -"Select the agents that are responsible for the group. These agents will then " -"see caller log entries and call notifications fitting to said queue." +"Using this option may lead to inconsistencies in the system as the ticket " +"organization may become decoupled from the ticket customer." msgstr "" -#: ../system/integrations/cti/generic.rst:0 +#: ../settings/ticket.rst:85 msgid "" -"Screenshot showing the caller log filter table with pre filled sample data" +"However, you may use this option if you wish to maintain :ref:`the shared " +"access ` to the ticket for all organization " +"members of the original organization of the customer." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:6 -msgid "" -"With recent logs Zammad allows you to view the latest calls for the CTI " -"functionality. This usually comes in handy, when you're looking for errors." +#: ../settings/ticket.rst:110 +msgid "Ticket Number Format (default: ``Increment (SystemID.Counter)``)" msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:0 +#: ../settings/ticket.rst:94 msgid "" -"Screenshot showing several incoming requests within Recent logs section." +"This setting defines the way Zammad's ticket number will look. Changing this " +"setting in production will cause follow up detection to fail." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:16 -msgid "I'm just here to clear floats up." +#: ../settings/ticket.rst:102 +msgid "Increment (SystemID.Counter)" msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:20 +#: ../settings/ticket.rst:98 msgid "" -"By clicking on the entry of interest, Zammad will provide more details on " -"the call in question. You'll see the payload it received and also the " -"response that was sent." +"The increment value contains the SystemID (automatically generated during " +"installation) and a increment which counts up with every new Ticket. The " +"increment will automatically get another digit if needed." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:0 -msgid "" -"Screenshot showing detailed information of a specific log entry of recent " -"logs" +#: ../settings/ticket.rst:102 +msgid "Examples: ``1010138``, ``1010139``" msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:31 -msgid "x" +#: ../settings/ticket.rst:110 +msgid "Date (Year.Month.Day.SystemID.Counter)" msgstr "" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 -#: ../system/integrations/cti/includes/troubleshooting.include.rst:9 -msgid "My Phone page stays blank, signalling does work..." +#: ../settings/ticket.rst:105 +msgid "" +"This version of the ticket number is fairly long. However, because it " +"contains the date of ticket creation, it also allows you to see when the " +"ticket has been created. You may feel familiar with this number format if " +"you've worked with OTRS already." msgstr "" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:5 -msgid "" -"If you've made sure that signalling works (check Recent logs) and your " -"Caller Log still stays empty, please ensure that you only configured one CTI " -"integration version. Specifically defining more than one agent mapping on " -"the different integration variants will be the issue." +#: ../settings/ticket.rst:110 +msgid "Examples: ``201206231010138``, ``201206231010139``" msgstr "" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 -msgid "Clear the not needed agent mapping and reload your browser page." +#: ../settings/ticket.rst:137 +msgid "OPTIONS" msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:1 +#: ../settings/ticket.rst:113 msgid "" -"By mapping your agents extension to their existing Zammad users, Zammad can " -"provide a new ticket dialog or open the user profile for the agent that " -"picks up the call." +"The below options allow you to further customize your ticket number. The " +"availability of options differ depending of the chosen ticket number format " +"above." msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:5 -msgid "" -"This speeds up ticket aiding, no matter if it's for existing tickets or new " -"ones!" +#: ../settings/ticket.rst:122 +msgid "Checksum (default: ``no``)" msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:8 +#: ../settings/ticket.rst:118 msgid "" -"To see it work from the agent's perspective, have a look on :user-docs:`user " -"documentation `." +"If set to yes, we'll built a checksum to further \"unique\" the ticket " +"number of your system. If you're dealing with many other ticket systems this " +"might help to prevent false positive follow up detection on tickets." msgstr "" -#: ../system/integrations/cti/placetel.rst:2 -msgid "Placetel CTI" +#: ../settings/ticket.rst:122 +msgid "This will also add another digit to the ticket number." msgstr "" -#: ../system/integrations/cti/placetel.rst:16 -msgid "You need an administrative Placetel account for your organization." +#: ../settings/ticket.rst:137 +msgid "Min. size of Number (default: ``5``)" msgstr "" -#: ../system/integrations/cti/placetel.rst:17 -#: ../system/integrations/cti/sipgate.rst:20 +#: ../settings/ticket.rst:125 msgid "" -"Your Zammad instance must be allowed to communicate to external services." +"This setting defines the minimum length of your ticket number. If your " +"counter is not yet high enough, Zammad will fill the number with zeros to " +"ensure the wanted length." msgstr "" -#: ../system/integrations/cti/placetel.rst:18 -msgid "Placetel must be able to reach your Zammad instance." -msgstr "" - -#: ../system/integrations/cti/placetel.rst:22 -msgid ":doc:`provider-configurations/placetel`" -msgstr "" - -#: ../system/integrations/cti/placetel.rst:21 +#: ../settings/ticket.rst:129 msgid "" -"Learn how to configure Placetel to enable Zammad and Placetel to communicate " -"with each other." +"Please note that the minimum length is ``3`` (SystemID + at least one digit " +"if below 10). Also, if the length is no longer long enough, the number will " +"automatically get one digit longer. Ticket-Numbers **do not overflow**, thus " +"it's save to keep it at 5 or set it lower if wanted." msgstr "" -#: ../system/integrations/cti/placetel.rst:32 +#: ../settings/ticket.rst:135 msgid "" -"The here listed endpoint settings are relevant for the :doc:`integration " -"configuration with Placetel `." +"This option is only available if ticket number format is set to " +"``Increment``!" msgstr "" -#: ../system/integrations/cti/placetel.rst:37 -#: ../system/integrations/i-doit.rst:53 -msgid "Endpoint" +#: ../settings/ticket.rst:142 +msgid "Auto-Assignment" msgstr "" -#: ../system/integrations/cti/placetel.rst:36 +#: ../settings/ticket.rst:144 msgid "" -"This endpoint will be required for the Zammad integration within the " -"Placetel web interface." -msgstr "" - -#: ../system/integrations/cti/placetel.rst:41 -msgid "API Token" +"In a larger Zammad environment, it happens that several agents open the same " +"ticket at the same time. Although collision detection is then effective, the " +"efficiency of processing can be increased by means of the automatic " +"assignment of tickets when a ticket is opened." msgstr "" -#: ../system/integrations/cti/placetel.rst:40 +#: ../settings/ticket.rst:149 msgid "" -"You'll receive this token within the ``Web API`` menu. Make sure to copy " -"this value, it's only shown once!" -msgstr "" - -#: ../system/integrations/cti/placetel.rst:71 -#: ../system/integrations/cti/sipgate.rst:77 -msgid "Phone Extension to Agent Mapping" +"The automatic assignment of tickets can be activated and configured in the " +"admin area under Settings > Ticket > Auto Assignment." msgstr "" -#: ../system/integrations/cti/placetel.rst:0 -msgid "Screenshot showing sample user mappings in between Placetel and Zammad" +#: ../settings/ticket.rst:152 +msgid "" +"The auto assignment only works if the ticket has no owner yet. By default, " +"the agent can always reset the ticket owner to ``-`` if needed." msgstr "" -#: ../system/integrations/cti/placetel.rst:64 +#: ../settings/ticket.rst:155 msgid "" -"You can find your agents Placetel username combination required within ⚙️ PBX " -"→ VoIP destinations. Within the \"Advanced settings\" section you're looking " -"for \"SIP user name\" and \"SIP server\"." +"If you want to use this function for only specific tickets, you can " +"configure the conditions accordingly to meet your requirement. By default " +"the condition affects all tickets with the state ``open``." msgstr "" -#: ../system/integrations/cti/placetel.rst:68 -msgid "Combine these two like so: ``@``." +#: ../settings/ticket.rst:161 +msgid "" +"If you need to exclude users (e.g. a group leader), you can search and " +"select the desired agents in the ``Exception Users`` list. The search " +"function in this area is only effective, if you have too many agents to " +"display at once to help you with the configuration." msgstr "" -#: ../system/integrations/cti/placetel.rst:0 -msgid "Sample VoIP credentials for a Placetel user" +#: ../settings/ticket.rst:167 +msgid "Notifications" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:2 -msgid "Setup Placetel connection for Zammad" +#: ../settings/ticket.rst:191 +msgid "Default Notifications" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:6 +#: ../settings/ticket.rst:170 msgid "" -"This configuration step requires a *full* administrative Placetel account. " -"You may receive forbidden error messages with Placetel in case your " -"permissions are not high enough." +"This setting allows you to configure the default ticket notifications that " +"will be applied to all new agent users (incl. users who were just assigned " +"agent role). Simply change the notification matrix to desired state and " +"press **Save**." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:10 +#: ../settings/ticket.rst:175 msgid "" -"The following actions can be configured via the `Placetel web interface " -"`_." -msgstr "" - -#: ../system/integrations/cti/provider-configurations/placetel.rst:29 -msgid "Step 1: Activate Zammad integration" +"In case an agent already exists, their ticket notification preferences will " +"be preserved. Optionally, you can also **Apply current defaults to all " +"agents**." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:14 +#: ../settings/ticket.rst:181 msgid "" -"Within Integrations, scroll down to Partner integrations and select Zammad." +"**Potential time-consuming action:** Applying default ticket notifications " +"to all agent users may take some time to complete, be patient! The exact " +"time will depend on the size of your system and the number of agents." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:17 +#: ../settings/ticket.rst:185 msgid "" -"You can alternatively filter by \"Ticket Systems\" to reduce the number of " -"entries on the page. You'll still want to look for Partner integrations. 🤓" +"**Active agents only!** When current default ticket notifications are " +"applied, only active agent users are considered. In case an agent is re-" +"activated *after* this action, they will still have the old notification " +"configuration." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:21 +#: ../settings/ticket.rst:190 msgid "" -"Within the Zammad integration now press \"Activate\". A new tab ``API`` " -"becomes available - open this tab." +"In case you want to go back to the initial state of ticket notifications, " +"you can click on **Reset to default** button." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:24 -msgid "" -"Now tick \"Enable Call Control / Notify API\" and paste the Placetel " -"endpoint from your Zammad instance into the field \"URL of your API " -"endpoint\". Save to apply the settings" +#: ../settings/ticket.rst:196 +msgid "Duplicate Detection" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 -msgid "Screencast showing how to activate the Zammad integration" +#: ../settings/ticket.rst:238 +msgid "Detect Duplicate Ticket Creation" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:51 -msgid "Step 2: Generate API Token for Placetel" +#: ../settings/ticket.rst:199 +msgid "" +"This setting turns on the duplicate ticket detection mechanism during ticket " +"creation. If similar tickets are found in the system, a suitable warning " +"will be shown to the user trying to create a ticket." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:32 -msgid "" -"Go back to the integrations page and scroll down to \"Web API\". Generate a " -"new API token by using the \"Create a new API token\" button." +#: ../settings/ticket.rst:206 +msgid "A Sample Duplicate Ticket Warning" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:37 +#: ../settings/ticket.rst:208 msgid "" -"If you already generated a token either use your existing token or reset it " -"by using above mentioned button. Placetel will ask you to conform this reset." +"You can choose which ticket attributes will be matched by selecting them in " +"**Attributes to compare** field. Only if the ticket attribute value provided " +"by the user in the ticket create form is *equal* with the attribute in an " +"existing ticket, the warning will be shown." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:41 -msgid "" -"Please keep in mind that existing API scripts may no longer work due to " -"token resets!" +#: ../settings/ticket.rst:213 +msgid "**Warning title** and **Warning message** are configurable as well." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:44 +#: ../settings/ticket.rst:215 msgid "" -"Copy the provided API token and insert it into the \"API Token\" field " -"within Zammad's Placetel integration." +"You can limit the detection only to certain user roles. By default, only " +"agents will see the warning." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:47 +#: ../settings/ticket.rst:218 msgid "" -"Apply your changes by using the \"Save\" button on the bottom of the " -"Placetel integration page and activate the Placetel integration." +"If you don't want to show the matched tickets as part of the warning, you " +"can set **Show matching ticket(s) in the warning** setting to *no*." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +#: ../settings/ticket.rst:221 msgid "" -"Screencast showing how to retrieve an API token from Placetel for Zammad" +"By default, **Permission level for looking up ticket** is set to *User*, " +"which means user permissions will be honored during sarch. The user will " +"see the warning only if tickets they have access to are matched. " +"Alternatively, you can set this setting to *System*, in which case the " +"search will happen within *all* tickets in the system, regardless of user " +"permissions." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:73 -#: ../system/integrations/cti/provider-configurations/sipgate.rst:77 -msgid "Step 3: Restrict the numbers to notify on" +#: ../settings/ticket.rst:227 +msgid "**🦺 Safety first!**" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:54 +#: ../settings/ticket.rst:229 msgid "" -"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " -"the the Integrations page of the Placetel web interface, go to \"Notify " -"API\"." +"Even if the permission level is set to *System*, the user will not be shown " +"the tickets they don't have access to in the warning, even if they match." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:58 +#: ../settings/ticket.rst:233 msgid "" -"Lower on the page Placetel allows you to restrict the numbers to notify on. " -"You'll find this within the \"External routing API\" part." +"However, just the confirmation about the existence of the tickets in the " +"system may be considered an unwanted information disclosure. Use this option " +"carefully!" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +#: ../settings/ticket.rst:237 msgid "" -"Screenshot showing a sample selection of phone numbers to use for the " -"Placetels notify API" +"Finally, you can configure between matching within **All tickets** or **Open " +"tickets** only by setting **Match tickets in following states**. Depending " +"on the current ticket state, a ticket may or not be matched." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:66 -msgid "" -"This menu point also provides a API request log from Placetel view. Just " -"open \"Recent responses of your API endpoint\" to learn more." +#: ../system/core-workflows.rst:2 +msgid "Core Workflows" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:69 +#: ../system/core-workflows.rst:4 msgid "" -"If you want to see Zammad's perspective, use the \"Recent Logs\" part from " -"within the Placetel integration page." +"Core Workflows allow you to adjust object attributes in many ways. For " +"example:" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 -msgid "Screenshot showing sample log entries for Placetels API calls to Zammad" +#: ../system/core-workflows.rst:7 +msgid "show / hide fields" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:77 -msgid "Step 4 (optional): Further configurations for Placetel" +#: ../system/core-workflows.rst:8 +msgid "adjust mandatory setting" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:76 +#: ../system/core-workflows.rst:9 +msgid "manipulate available options" +msgstr "" + +#: ../system/core-workflows.rst:11 msgid "" -"If needed, you can now configure Zammad's Placetel integration in more " -"detail. You can learn more about your options here: :ref:`Placetel " -"integration settings `." +"With this, you can provide exactly the information your users really need!" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:2 -msgid "Setup Sipgate connection for Zammad" +#: ../system/core-workflows.rst:15 +msgid "" +"If the pre-defined :doc:`/system/objects` are not enough, please add them " +"beforehand." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +#: ../system/core-workflows.rst:17 msgid "" -"Sipgate has no english web interface which is why this documentation page is " -"mixing up languages badly." +"If you experience slow or unreliable field updates, please see :ref:`Core " +"Workflow Ajax Modus `" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +#: ../system/core-workflows.rst:22 msgid "" -"Please also note that the availability of API addons highly depends on your " -"package trier. Usage of sipgate.io packages *is not free*, please check " -"their `pricing page `_ before!" +"This is a very enhanced functionality and can cause unexpected UI behavior. " +"Please ensure to test your use cases after configuration to reduce surprises." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:35 -msgid "Step 1: Book sipgate.io package" +#: ../system/core-workflows.rst:None +msgid "Dialogue for adding a new workflow" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:13 -msgid "Skip to step 2 if you already have the package booked!" +#: ../system/core-workflows/condition-operators.rst:2 +msgid "Core Workflow Condition Operators" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:15 +#: ../system/core-workflows/condition-operators.rst:4 msgid "" -"Login to an administrative Sipgate account and navigate to " -"``Accountverwaltung``. You'll see several different options depending on " -"your booked packages. Select ``Verträge & Produkte`` to continue." +"You might know that there is a separate section for explaining :doc:" +"`condition operators `. Head over there to " +"see a detailed explanation of many conditions and operators." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:19 +#: ../system/core-workflows/condition-operators.rst:8 msgid "" -"Scroll down to the section ``Zusätzliche Produkte buchen`` and look for " -"``sipgate.io`` - select this product by using the ``Produkte anzeigen``-" -"Button." -msgstr "" - -#: ../system/integrations/cti/provider-configurations/sipgate.rst:23 -msgid "" -"On the next page select either one of the ``sipgate.io`` packages or ``Push-" -"API Package Free``. Follow the dialogue by booking the addon. You'll be " -"returned to your contract overview and now should see the selected addon in " -"your list." +"Due to differences to other places in Zammad which are also using conditions " +"(e.g. triggers), you can find a dedicated description of operators for core " +"workflows below." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:30 +#: ../system/core-workflows/condition-operators.rst:12 msgid "" -"The availability for ``sipgate.io`` packages and their levels highly depends " -"on the overall account type and product you've booked with Sipgate." +"Be aware that the availability of the operators depends on the selected " +"attribute and its field type. Some of the operators may only be available " +"for system attributes (e.g. for \"tags\", \"active\")." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screencast showing the process on how to book the required sipgate.io addon" +#: ../system/core-workflows/condition-operators.rst:20 +msgid "Operator" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:52 -msgid "Step 2: Configure webhook for Zammad" +#: ../system/core-workflows/condition-operators.rst:22 +msgid "after (absolute)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:38 -msgid "" -"Within your ``Accountverwaltung`` navicate to your product ``sipgate.io``. " -"In the newly opened tab, switch from \"Clients\" to \"Webhooks\" and paste " -"the endpoint URLs from your Zammad instance like so:" +#: ../system/core-workflows/condition-operators.rst:23 +msgid "Matches if a date/time is after a specific point in time." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:42 -msgid "Inbound endpoint to \"Incoming\"" +#: ../system/core-workflows/condition-operators.rst:24 +msgid "after (relative)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:43 -msgid "Outbound endpoint to \"Outgoing\"" +#: ../system/core-workflows/condition-operators.rst:25 +msgid "Matches if a time span after a specified event has passed." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:47 -msgid "" -"Ensure to select at least one call group or phoneline within \"Sources\". " -"Other wise Sipgate will not indicate any incoming or outgoing calls to " -"Zammad." +#: ../system/core-workflows/condition-operators.rst:26 +msgid "before (absolute)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screencast showing how to add Zammad's endpoint URLs to sipgate.ios webhook " -"configuration" +#: ../system/core-workflows/condition-operators.rst:27 +msgid "Matches if a date/time is before a specific point in time." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:55 -msgid "" -"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " -"the Webhooks → URLs section of Sipgate you can select which *sources* " -"Sipgate should notify Zammad about in- and outgoing calls." +#: ../system/core-workflows/condition-operators.rst:28 +msgid "before (relative)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:59 -msgid "" -"Use either specific phone lines or use the option \"Use for all phonelines " -"and groups\" to notify Zammad about all existing lines of your Sipgate " -"account." +#: ../system/core-workflows/condition-operators.rst:29 +msgid "Matches if a time span after a specified event has not passed." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screenshot showing a sample selection of phone numbers to use for the " -"Sipgates webhooks API" +#: ../system/core-workflows/condition-operators.rst:30 +msgid "contains" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:68 -msgid "This section also allows you to enable a Debug log." +#: ../system/core-workflows/condition-operators.rst:31 +msgid "Matches if a specified value is present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "Screenshot showing an enabled Debug log option" +#: ../system/core-workflows/condition-operators.rst:33 +msgid "Matches if all of the specified values are present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:73 -msgid "" -"After enabling you can use the Debug log section to see all sent webhook " -"calls to Zammad. You'll also can see the response." +#: ../system/core-workflows/condition-operators.rst:35 +msgid "Matches if none of the specified values are present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screenshot showing sample log entries for Sipgates webhook calls to Zammad" +#: ../system/core-workflows/condition-operators.rst:36 +msgid "contains not" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:81 -msgid "Step 4 (optional): Further configurations for Sipgate" +#: ../system/core-workflows/condition-operators.rst:37 +msgid "Matches if a specified value is not present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:80 -msgid "" -"If needed, you can now configure Zammad's Sipgate integration in more " -"detail. You can learn more about your options here: :ref:`Sipgate " -"integration settings `." +#: ../system/core-workflows/condition-operators.rst:39 +msgid "Matches if one specified value is present." msgstr "" -#: ../system/integrations/cti/sipgate.rst:2 -msgid "Sipgate (sipgate.io)" +#: ../system/core-workflows/condition-operators.rst:41 +msgid "Matches if one specified value is not present." msgstr "" -#: ../system/integrations/cti/sipgate.rst:16 -msgid "You need an administrative Sipgate account for your organization." +#: ../system/core-workflows/condition-operators.rst:42 +msgid "does not match regex" msgstr "" -#: ../system/integrations/cti/sipgate.rst:17 -msgid "" -"Zammad requires a ``sipgate.io`` addon from the feature store (please note " -"that API calls are not free with Sipgate. Rates may apply and differ from " -"account to account)." +#: ../system/core-workflows/condition-operators.rst:43 +msgid "Matches if content doesn't fit to regex rule." msgstr "" -#: ../system/integrations/cti/sipgate.rst:21 -msgid "Sipgate must be able to reach your Zammad instance." +#: ../system/core-workflows/condition-operators.rst:44 +msgid "ends with" msgstr "" -#: ../system/integrations/cti/sipgate.rst:25 -msgid ":doc:`provider-configurations/sipgate`" +#: ../system/core-workflows/condition-operators.rst:45 +msgid "Matches if content ends with specified value." msgstr "" -#: ../system/integrations/cti/sipgate.rst:24 -msgid "" -"Learn how to configure Sipgate to enable Zammad and Sipgate to communicate " -"with each other." +#: ../system/core-workflows/condition-operators.rst:46 +msgid "ends with one of" msgstr "" -#: ../system/integrations/cti/sipgate.rst:33 -msgid "" -"Below endpoint settings affect the :doc:`sipgate.io configuration `." +#: ../system/core-workflows/condition-operators.rst:47 +msgid "Matches if content ends with one of the specified values." msgstr "" -#: ../system/integrations/cti/sipgate.rst:37 -msgid "This endpoint is required for incoming call hooks." +#: ../system/core-workflows/condition-operators.rst:48 +msgid "from (relative)" msgstr "" -#: ../system/integrations/cti/sipgate.rst:40 -msgid "This endpoint is required for outgoing call hooks." +#: ../system/core-workflows/condition-operators.rst:49 +msgid "Matches if date/time is after a period of time after an event." msgstr "" -#: ../system/integrations/cti/sipgate.rst:0 -msgid "Screenshot showing sample user mappings in between Sipgate and Zammad" +#: ../system/core-workflows/condition-operators.rst:51 +msgid "Matches if content is equal to a specified value." msgstr "" -#: ../system/integrations/cti/sipgate.rst:69 -msgid "" -"You can find your agent's Sipgate username within ``Accountverwaltung → " -"Benutzer``. You're looking for the SIP-ID." +#: ../system/core-workflows/condition-operators.rst:52 +msgid "is any of" msgstr "" -#: ../system/integrations/cti/sipgate.rst:0 -msgid "Sample VoIP credentials for a Sipgate user" +#: ../system/core-workflows/condition-operators.rst:53 +msgid "Matches if content is equal to any of specified values." msgstr "" -#: ../system/integrations/cti/sipgate.rst:77 -msgid "Users with several devices also have several SIP-IDs." +#: ../system/core-workflows/condition-operators.rst:54 +msgid "is modified" msgstr "" -#: ../system/integrations/elasticsearch.rst:2 -msgid "Elasticsearch (SaaS)" +#: ../system/core-workflows/condition-operators.rst:55 +msgid "Matches if content is modified." msgstr "" -#: ../system/integrations/elasticsearch.rst:4 -msgid "" -"The Elasticsearch integration allows you to create a read-only user to use " -"with your favorite reporting tool (e.g. like Grafana)." +#: ../system/core-workflows/condition-operators.rst:57 +#: ../system/core-workflows/condition-operators.rst:61 +msgid "True from the moment of changing content until form submit." msgstr "" -#: ../system/integrations/elasticsearch.rst:7 -msgid "" -"If you want to take full advantage of the Zammad reporting, have a look at " -"our :docs:`Grafana ` " -"setup page as well." +#: ../system/core-workflows/condition-operators.rst:58 +msgid "is modified to" msgstr "" -#: ../system/integrations/elasticsearch.rst:11 -#: ../system/subscription/index.rst:7 -msgid "**🚧 Hosted environment specific 🚧**" +#: ../system/core-workflows/condition-operators.rst:59 +msgid "Matches if content is modified to a specific value." msgstr "" -#: ../system/integrations/elasticsearch.rst:13 -msgid "" -"This integration is only available for Hosted setups. In order to use " -"Elasticsearch you'll need the **Plus** subscription." +#: ../system/core-workflows/condition-operators.rst:62 +msgid "is none of" msgstr "" -#: ../system/integrations/elasticsearch.rst:16 -msgid "" -"Self hosted users have all the control over their self hosted Elasticsearch " -"instances." +#: ../system/core-workflows/condition-operators.rst:63 +msgid "Matches if content is none of any specified values." msgstr "" -#: ../system/integrations/elasticsearch.rst:None -msgid "Elasticsearch integration page on SaaS environments" +#: ../system/core-workflows/condition-operators.rst:65 +msgid "Matches if content is not equal to a specified value." msgstr "" -#: ../system/integrations/elasticsearch.rst:27 -msgid "" -"Please note the following limitations of Elasticsearch access on hosted " -"environments:" +#: ../system/core-workflows/condition-operators.rst:67 +msgid "Matches if content is present." msgstr "" -#: ../system/integrations/elasticsearch.rst:30 -msgid "access to the Elasticsearch index is read-only access" +#: ../system/core-workflows/condition-operators.rst:68 +msgid "just changed" msgstr "" -#: ../system/integrations/elasticsearch.rst:31 -msgid "currently you're limited to user only" +#: ../system/core-workflows/condition-operators.rst:69 +msgid "Matches if content has changed." msgstr "" -#: ../system/integrations/elasticsearch.rst:32 +#: ../system/core-workflows/condition-operators.rst:71 +#: ../system/core-workflows/condition-operators.rst:75 msgid "" -"Reporting tools that require to write into the indexes (like Kibana) are not " -"supported" +"Only true for the moment of changing content until next form field action/" +"click." msgstr "" -#: ../system/integrations/elasticsearch.rst:34 -msgid "IP access restriction is currently not yet supported" +#: ../system/core-workflows/condition-operators.rst:72 +msgid "just changed to" msgstr "" -#: ../system/integrations/elasticsearch.rst:37 -msgid "Activating Elasticsearch Access" +#: ../system/core-workflows/condition-operators.rst:73 +msgid "Matches if content has changed to a specified value." msgstr "" -#: ../system/integrations/elasticsearch.rst:39 -msgid "" -"By default external access to your Elasticsearch index is not active. You " -"can enable the integration at any time if needed." +#: ../system/core-workflows/condition-operators.rst:76 +msgid "matches regex" msgstr "" -#: ../system/integrations/elasticsearch.rst:42 -msgid "" -"Please ensure to note down the password provided - you won't have access to " -"it afterwards." +#: ../system/core-workflows/condition-operators.rst:77 +msgid "Matches if value fits to regex rule." msgstr "" -#: ../system/integrations/elasticsearch.rst:None -msgid "Screencast showing activation of Elasticsearch integration" +#: ../system/core-workflows/condition-operators.rst:79 +msgid "Matches if no content is present." msgstr "" -#: ../system/integrations/elasticsearch.rst:51 -msgid "Connection Settings" +#: ../system/core-workflows/condition-operators.rst:80 +msgid "starts with" msgstr "" -#: ../system/integrations/elasticsearch.rst:53 -msgid "" -"This section holds the most important general information for accessing your " -"Elasticsearch indexes - such as:" -msgstr "" - -#: ../system/integrations/elasticsearch.rst:57 -msgid "A unique subdomain that does not tell your real instance URL." +#: ../system/core-workflows/condition-operators.rst:81 +msgid "Matches if content starts with specified value." msgstr "" -#: ../system/integrations/elasticsearch.rst:61 -msgid "Software" +#: ../system/core-workflows/condition-operators.rst:82 +msgid "starts with one of" msgstr "" -#: ../system/integrations/elasticsearch.rst:60 -msgid "" -"The major version of the search index being used. This is required by some " -"Reporting tools like Grafana." +#: ../system/core-workflows/condition-operators.rst:83 +msgid "Matches if content starts with one of the specified values." msgstr "" -#: ../system/integrations/elasticsearch.rst:64 -msgid "Authentication" +#: ../system/core-workflows/condition-operators.rst:84 +msgid "till (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:64 -msgid "The authentication type being supported. ``Basic Authentication``" +#: ../system/core-workflows/condition-operators.rst:85 +msgid "Matches if date/time is before a period of time before an event." msgstr "" -#: ../system/integrations/elasticsearch.rst:67 -msgid "Available Indexes" +#: ../system/core-workflows/condition-operators.rst:86 +msgid "today" msgstr "" -#: ../system/integrations/elasticsearch.rst:69 -msgid "" -"Within this section we're displaying the -in our opinion- most important " -"indexes for a Zammad instance." +#: ../system/core-workflows/condition-operators.rst:87 +msgid "Matches if date/time is today." msgstr "" -#: ../system/integrations/elasticsearch.rst:72 -msgid "" -"If you require all indexes or our listing is not good enough for you, point " -"your browser to the URL we're providing and append ``/_aliases?" -"pretty=true``. The result should look like this: ``https://.zammad.com/" -"_aliases?pretty=true``." +#: ../system/core-workflows/condition-operators.rst:88 +msgid "within last (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:77 +#: ../system/core-workflows/condition-operators.rst:89 msgid "" -"Your browser will automatically ask for your credentials - you'll then see " -"something like this:" +"Matches if date/time content is within specified period of time before now." msgstr "" -#: ../system/integrations/elasticsearch.rst:125 -msgid "Credentials" +#: ../system/core-workflows/condition-operators.rst:91 +msgid "within next (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:127 +#: ../system/core-workflows/condition-operators.rst:92 msgid "" -"Within this section Zammad displays your available users. The password is " -"provided once (upon activation) and cannot be retrieved after that." +"Matches if date/time content is within specified period of time after now." msgstr "" -#: ../system/integrations/elasticsearch.rst:131 -msgid "" -"If you need to change or reset your Elasticsearch user password, use the " -"\"Reset password\" button in the credentials table. Doing so creates a brand " -"new password for the account in question. This change is immediate, keep in " -"mind that this may affect third party tools connected to your instance." +#: ../system/core-workflows/how-do-they-work.rst:2 +msgid "How do they work?" msgstr "" -#: ../system/integrations/exchange.rst:2 -msgid "Exchange" +#: ../system/core-workflows/how-do-they-work.rst:4 +msgid "" +"Core Workflows are executed according to their priority. If two workflows " +"have the same priority, they are executed in alphabetical order based on " +"their **name**." msgstr "" -#: ../system/integrations/exchange.rst:4 +#: ../system/core-workflows/how-do-they-work.rst:8 msgid "" -"With Zammad's Exchange integration, you can easily use existing address " -"books without having to update more than one source." +"Because of the way Core Workflows work, all changes to attributes are " +"checked with the application server - please see :doc:`limitations` for " +"possible issues." msgstr "" -#: ../system/integrations/exchange.rst:7 +#: ../system/core-workflows/how-do-they-work.rst:12 msgid "" -"However, you should refrain from syncing all addresses, as the results may " -"not be what you expect (Exchange collects huge amounts of addresses). A " -"central address book of your company to sync makes more sense, as you can " -"ensure that Zammad gets only the data you need and want. Apart from this, it " -"is even not possible to sync the Global Address List (GAL) of your Exchange " -"system with Zammad." +"Below we're talking about settings that are important and not self-" +"explanatory." msgstr "" -#: ../system/integrations/exchange.rst:16 +#: ../system/core-workflows/how-do-they-work.rst:17 msgid "" -"**Exchange and LDAP:** The exchange sync can be overruled by Zammad's LDAP " -"integration. If you have the same users in both sources, the LDAP version " -"will always be Zammad's pick." +"Choose the object context you want to run the workflow in. This will decide " +"on your available attributes and actions." msgstr "" -#: ../system/integrations/exchange.rst:19 -msgid "" -"**One way sync:** the Exchange sync is one way. Exchange => Zammad. Changes " -"to your users inside of Zammad might be overwritten by the Exchange sync." +#: ../system/core-workflows/how-do-they-work.rst:20 +msgid "Ticket objects also have access to the ticket customer." msgstr "" -#: ../system/integrations/exchange.rst:24 +#: ../system/core-workflows/how-do-they-work.rst:25 msgid "" -"To configure Exchange integration, simply go to the System > Integrations > " -"Exchange in the admin panel. Press \"change\" and follow the wizard for " -"adding the needed Exchange information to Zammad. On the last two steps " -"Zammad will ask you for the address book(s) and your desired attribute " -"mapping. By default, Zammad only maps email address, first- and lastname. " -"Technically, you can map any Exchange object to a Zammad user object (this " -"also works for custom objects!)." +"Choose in which situation the workflow is applied. Contexts can be combined " +"to avoid duplicate workflows." msgstr "" -#: ../system/integrations/exchange.rst:35 -msgid "" -"If the SSL verification fails while connecting to Exchange, Zammad will ask " -"you to turn it off temporarily." +#: ../system/core-workflows/how-do-they-work.rst:30 +msgid "Creation mask" msgstr "" -#: ../system/integrations/exchange.rst:38 +#: ../system/core-workflows/how-do-they-work.rst:29 msgid "" -"Please be aware that **turning off SSL verification is a security risk**. It " -"should only be used temporarily or for testing purposes. If turned off, " -"there is no verification of the certificate, which means that every " -"presented certificate will be accepted." +"If selected, your conditions and actions will affect all applicable creation " +"masks." msgstr "" -#: ../system/integrations/exchange.rst:43 -msgid "" -"After pressing Continue, Zammad will check if the configuration is okay. You " -"can then enable Exchange and start your first sync. The sync will then run " -"hourly - if you need to change mappings or the address book(s), you can " -"change the configuration at any time." +#: ../system/core-workflows/how-do-they-work.rst:34 +msgid "Edit mask" msgstr "" -#: ../system/integrations/exchange.rst:50 +#: ../system/core-workflows/how-do-they-work.rst:33 msgid "" -"After the sync has finished, you can find the new Exchange contacts under " -"\"Users\". Zammad integrates them just as normal users." +"If selected, your conditions and actions will affect all applicable edit " +"masks." msgstr "" -#: ../system/integrations/exchange.rst:55 +#: ../system/core-workflows/how-do-they-work.rst:39 msgid "" -"In some cases you might see unique IDs as \"Login\" instead of the email " -"address. This is normal and doesn't affect the login or email mapping for " -"that entry." +"Zammad differentiates between selected and saved conditions. These can be " +"combined wherever needed." msgstr "" -#: ../system/integrations/github.rst:4 -msgid "" -"Use GitHub integration to track GitHub issues directly within Zammad " -"tickets. Add issue hyperlinks and get a live summary of metadata like status " -"(open/closed), assignee, labels, and more." +#: ../system/core-workflows/how-do-they-work.rst:42 +msgid "**⚠️ Restrict workflows to specific roles if needed!**" msgstr "" -#: ../system/integrations/github.rst:8 -msgid "Please note that our GitHub integration does not support pull requests." +#: ../system/core-workflows/how-do-they-work.rst:44 +msgid "" +"By default and unless configured in conditions, workflow rules are executed " +"for **all roles**. This also affects your customers!" msgstr "" -#: ../system/integrations/github.rst:None -msgid "Integration page for GitHub" +#: ../system/core-workflows/how-do-they-work.rst:50 +msgid "Selected Conditions" msgstr "" -#: ../system/integrations/github.rst:18 +#: ../system/core-workflows/how-do-they-work.rst:48 msgid "" -"In your GitHub settings, create a new API token under **Developer settings > " -"Personal access tokens > Generate new token**. Leave the **Scopes** section " -"empty." +"These conditions are based on form values and match if an appropriate " +"selection is made (e.g. choosing another group in the ticket without " +"saving). This applies for drafts (active selection) and currently saved " +"values." msgstr "" -#: ../system/integrations/github.rst:0 ../system/integrations/gitlab.rst:0 -msgid "Screencast showing how to create a new API token" +#: ../system/core-workflows/how-do-they-work.rst:64 +msgid "Saved Conditions" msgstr "" -#: ../system/integrations/github.rst:27 -msgid "Create a new API key with no scopes/privileges." +#: ../system/core-workflows/how-do-they-work.rst:53 +msgid "" +"These conditions only match if the selected values are stored in the " +"database. It ignores the current value or selection of the field, as long as " +"the changes are not saved (e.g. performing field operations for an existing " +"ticket, which is viewed/opened by an agent)." msgstr "" -#: ../system/integrations/github.rst:29 -msgid "🔒 **Will this work for private repos?**" +#: ../system/core-workflows/how-do-they-work.rst:60 +msgid "" +"Keep in mind that the value has to be available in the situation where you " +"need it. Otherwise the condition won't match." msgstr "" -#: ../system/integrations/github.rst:31 +#: ../system/core-workflows/how-do-they-work.rst:63 msgid "" -"No. To link private repo issues, **use the** ``repo`` **scope instead**. " -"Bear in mind that the resulting token will have `lots of permissions that it " -"doesn't actually need `_, which presents a security risk if your token ever falls into " -"the wrong hands." +"Example: you can't perform any actions with *saved condition* on a ticket in " +"creation, because there are no saved values at that time." msgstr "" -#: ../system/integrations/github.rst:37 +#: ../system/core-workflows/how-do-they-work.rst:66 msgid "" -"Unfortunately, because of how GitHub's OAuth token scopes are set up, this " -"is the only way to link issues on private repos." +"You can find a description of the condition operators for core workflows :" +"doc:`here `." msgstr "" -#: ../system/integrations/github.rst:40 -msgid "Enter your new API token in Zammad and enable GitHub integration." +#: ../system/core-workflows/how-do-they-work.rst:72 +msgid "" +"Which actions should we run on the relevant fields? The possible actions " +"depend on the object type. However, usually you can at least change the " +"visibility and whether the field is mandatory." msgstr "" -#: ../system/integrations/github.rst:0 -msgid "Screencast showing how to configure Zammad's GitHub integration" +#: ../system/core-workflows/how-do-they-work.rst:76 +msgid "Be aware that actions are not available for **related** context." msgstr "" -#: ../system/integrations/github.rst:47 +#: ../system/core-workflows/how-do-they-work.rst:78 msgid "" -"Use the default API endpoint (``https://api.github.com/graphql``) unless " -"you're using GitHub Enterprise Server." +"**Example:** Let's assume you are working in the ticket context. While you " +"can have customer *conditions*, you *can't adjust* objects with actions in " +"that scope. That's because this wouldn't have any impact on the ticket " +"dialog. Of course all ticket attributes (state, owner, ...) are available." msgstr "" -#: ../system/integrations/github.rst:50 +#: ../system/core-workflows/how-do-they-work.rst:84 msgid "" -"Once completed, a new GitHub issues tab will appear in the ticket pane. 🎉" +"Please also have a look at our :doc:`limitations` to be safe from surprises." msgstr "" -#: ../system/integrations/github.rst:59 ../system/integrations/gitlab.rst:52 -msgid "Token verification is taking a long time" +#: ../system/core-workflows/how-do-they-work.rst:88 +msgid "Available Operators" msgstr "" -#: ../system/integrations/github.rst:56 ../system/integrations/gitlab.rst:49 -msgid "" -"Slight delays are normal (<2 min.), especially for systems under heavy load." +#: ../system/core-workflows/how-do-they-work.rst:90 +msgid "The availability of operators depends on the object type and scope." msgstr "" -#: ../system/integrations/github.rst:58 +#: ../system/core-workflows/how-do-they-work.rst:94 msgid "" -"Self-hosted administrators, please check your network settings to ensure " -"that your Zammad server can reach ``api.github.com``." +"Please note that actions may or may not restrict API based access to " +"attributes. We're displaying the following icons for your overview to " +"understand these limits better:" msgstr "" -#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 -msgid "I reloaded the page and now the API token is gone" +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|api| This icon indicates the action affects the API." msgstr "" -#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 -msgid "" -"This may indicate that Zammad is still verifying your API token. Try " -"reloading the page again in a couple minutes." +#: ../system/core-workflows/how-do-they-work.rst:163 +msgid "api" msgstr "" -#: ../system/integrations/gitlab.rst:2 -msgid "GitLab" +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|ui| This icon indicates the action only affects the web interface." msgstr "" -#: ../system/integrations/gitlab.rst:4 -msgid "" -"Use GitLab integration to track GitLab issues directly within Zammad " -"tickets. Add issue hyperlinks and get a live summary of metadata like status " -"(open/closed), assignee, labels, and more." +#: ../system/core-workflows/how-do-they-work.rst:167 +msgid "ui" msgstr "" -#: ../system/integrations/gitlab.rst:8 -msgid "" -"Please note that our GitLab integration does not support merge requests." +#: ../system/core-workflows/how-do-they-work.rst:102 +msgid "show |ui|" msgstr "" -#: ../system/integrations/gitlab.rst:None -msgid "Integration page for GitLab" +#: ../system/core-workflows/how-do-they-work.rst:102 +msgid "Display the chosen field. Allows setting of values." msgstr "" -#: ../system/integrations/gitlab.rst:18 -msgid "" -"In your GitLab preferences, create a new API token under **Access Tokens**." +#: ../system/core-workflows/how-do-they-work.rst:109 +msgid "hide |ui|" msgstr "" -#: ../system/integrations/gitlab.rst:20 -msgid "Under **Select scopes**, choose ``read_api`` only." +#: ../system/core-workflows/how-do-they-work.rst:105 +msgid "" +"Hide the chosen field. However, it technically still allows setting the " +"field." msgstr "" -#: ../system/integrations/gitlab.rst:27 -msgid "🔒 **If you wish to link issues on any private repos...**" +#: ../system/core-workflows/how-do-they-work.rst:108 +msgid "" +"Please note that the field is **not** gone and still contains an existing " +"value (if set)! Consider *remove* instead, if you want this field to be gone." msgstr "" -#: ../system/integrations/gitlab.rst:29 -msgid "Your API token must belong to an account with access to those repos." +#: ../system/core-workflows/how-do-they-work.rst:112 +msgid "remove |ui|" msgstr "" -#: ../system/integrations/gitlab.rst:31 -msgid "Enter your new API token in Zammad and enable GitLab integration." +#: ../system/core-workflows/how-do-they-work.rst:112 +msgid "Entirely removes the field. The field value will not be evaluated." msgstr "" -#: ../system/integrations/gitlab.rst:0 -msgid "Screencast showing how to configure Zammad's GitLab integration" +#: ../system/core-workflows/how-do-they-work.rst:115 +msgid "set mandatory |ui| |api|" msgstr "" -#: ../system/integrations/gitlab.rst:40 -msgid "" -"Use the default API endpoint (``https://gitlab.com/api/graphql``) unless " -"you're a self-hosted GitLab user." +#: ../system/core-workflows/how-do-they-work.rst:115 +msgid "Sets the field to mandatory." msgstr "" -#: ../system/integrations/gitlab.rst:43 -msgid "" -"Once completed, a new GitLab issues tab will appear in the ticket pane. 🎉" +#: ../system/core-workflows/how-do-they-work.rst:118 +msgid "set optional |ui| |api|" msgstr "" -#: ../system/integrations/gitlab.rst:51 -msgid "" -"Self-hosted administrators, please check your network settings to ensure " -"that your Zammad server can reach ``gitlab.com``." +#: ../system/core-workflows/how-do-they-work.rst:118 +msgid "Sets the field to optional." msgstr "" -#: ../system/integrations/i-doit.rst:2 -msgid "i-doit" +#: ../system/core-workflows/how-do-they-work.rst:124 +msgid "add option |ui| |api|" msgstr "" -#: ../system/integrations/i-doit.rst:4 -msgid "" -"`i-doit `_ is an open-source **configuration " -"management database** - in other words, a tool for keeping tabs on every " -"single piece of your physical and digital infrastructure, from network " -"equipment to virtual machines on down to the faceplates on your rack shelves " -"and more." +#: ../system/core-workflows/how-do-they-work.rst:121 +msgid "Allows adding options to tree selects or selects." msgstr "" -#: ../system/integrations/i-doit.rst:10 +#: ../system/core-workflows/how-do-they-work.rst:123 msgid "" -"What's that got to do with Zammad? Well, if you used tickets to track issues " -"with all that hardware, you might start wishing there was a way they could " -"talk to each other." -msgstr "" - -#: ../system/integrations/i-doit.rst:14 -msgid "Zammad gives you two:" +"You have to use the \"remove option\" before performing this action. It " +"allows you to use *existing* configured values." msgstr "" -#: ../system/integrations/i-doit.rst:17 -msgid "1. Add i-doit Links to Zammad Tickets" +#: ../system/core-workflows/how-do-they-work.rst:128 +msgid "remove option |ui| |api|" msgstr "" -#: ../system/integrations/i-doit.rst:20 ../system/integrations/i-doit.rst:80 -msgid "What Users See" +#: ../system/core-workflows/how-do-they-work.rst:127 +msgid "" +"Allows removing options from tree selects or selects. It allows you to use " +"*existing* configured values." msgstr "" -#: ../system/integrations/i-doit.rst:26 -msgid "i-doit integration in Zammad's ticket pane" +#: ../system/core-workflows/how-do-they-work.rst:134 +msgid "set fixed to |ui| |api|" msgstr "" -#: ../system/integrations/i-doit.rst:26 -msgid "" -"The i-doit integration will appear under a new 🖨 tab in the ticket pane." +#: ../system/core-workflows/how-do-they-work.rst:131 +msgid "Reduces the available options by your selection." msgstr "" -#: ../system/integrations/i-doit.rst:28 +#: ../system/core-workflows/how-do-they-work.rst:133 msgid "" -"i-doit integration puts a new tab in Zammad's ticket pane where you can add " -"links to existing i-doit devices for easy reference. (See our :user-docs:" -"`user documentation ` to learn " -"how it works in practice)." +"This reduces your workflows in terms of *add option* and *remove option*." msgstr "" -#: ../system/integrations/i-doit.rst:36 ../system/integrations/i-doit.rst:93 -msgid "How to Set it Up" +#: ../system/core-workflows/how-do-they-work.rst:137 +msgid "fill in |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:38 -msgid "" -"It requires i-doit's `API Add-on `_. Make sure to have it properly set up. Use the following setting:" +#: ../system/core-workflows/how-do-they-work.rst:137 +msgid "Allows filling in of string and integer fields with your values." msgstr "" -#: ../system/integrations/i-doit.rst:42 -msgid "Active: ``Yes``" +#: ../system/core-workflows/how-do-they-work.rst:141 +msgid "fill in empty |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:43 -msgid "Enforce authentication by username and password: ``No``" +#: ../system/core-workflows/how-do-they-work.rst:140 +msgid "" +"Allows filling in of string and integer fields with your values **if the " +"field is empty**." msgstr "" -#: ../system/integrations/i-doit.rst:45 -msgid "" -"To set it up, enable the integration in the Zammad admin panel under " -"**System > Integrations > i-doit**:" +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "select |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "i-doit settings within the integration pages" +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "Select a specific value within a select, tree select or boolean field." msgstr "" -#: ../system/integrations/i-doit.rst:53 -msgid "The root URL of your i-doit installation." +#: ../system/core-workflows/how-do-they-work.rst:153 +msgid "auto select |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:62 -msgid "API token" +#: ../system/core-workflows/how-do-they-work.rst:147 +msgid "Helps users with tree select and select fields:" msgstr "" -#: ../system/integrations/i-doit.rst:56 +#: ../system/core-workflows/how-do-they-work.rst:149 msgid "" -"Found in the i-doit admin panel under **Interfaces / external data > JSON-" -"RPC API > Common Settings**." +"If the field has only one option available for selection and no value yet, " +"the value will be automatically set." msgstr "" -#: ../system/integrations/i-doit.rst:0 -msgid "i-doit administration interface with API configuration" +#: ../system/core-workflows/how-do-they-work.rst:152 +msgid "" +"This option only works if you have one value and doesn't work if there is " +"more than one option available." msgstr "" -#: ../system/integrations/i-doit.rst:67 -msgid "Client ID" +#: ../system/core-workflows/how-do-they-work.rst:157 +msgid "set readonly |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:65 -msgid "A unique name to identify Zammad within i-doit." +#: ../system/core-workflows/how-do-they-work.rst:156 +msgid "" +"Allows you to display an attribute as read only (which means no changes are " +"possible)." msgstr "" -#: ../system/integrations/i-doit.rst:67 -msgid "(Zammad does not require you to enter a value here, but i-doit might!)" +#: ../system/core-workflows/how-do-they-work.rst:161 +msgid "unset readonly |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:70 +#: ../system/core-workflows/how-do-they-work.rst:160 msgid "" -"Here you can decide if the certificate of your i-doit system has to be " -"verified or not. In case you are using custom certificates, please have a " -"look at :doc:`how to add them to Zammad `." -msgstr "" - -#: ../system/integrations/i-doit.rst:77 -msgid "2. List / Create Zammad Tickets in i-doit" +"In case a workflow set the field in question to read only, you can undo this " +"with option above." msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "Zammad integration in i-doit's device view" +#: ../system/core-workflows/how-do-they-work.rst:172 +msgid "Stop after match" msgstr "" -#: ../system/integrations/i-doit.rst:86 +#: ../system/core-workflows/how-do-they-work.rst:174 msgid "" -"i-doit's ticket system integration gives you a way to see all the tickets " -"for a given device without ever leaving i-doit. (See our :user-docs:`user " -"documentation ` to learn how it " -"works in practice)." +"Here you can decide if other workflows are executed after the current one." msgstr "" -#: ../system/integrations/i-doit.rst:95 +#: ../system/core-workflows/how-do-they-work.rst:176 msgid "" -"Enable this integration in the i-doit admin panel under **Interfaces / " -"external data > Trouble Ticket System (TTS) > Configuration**:" +"If set to ``no`` (default), further workflows will be executed if they match " +"the condition. In this case, it is possible that your actions from the " +"current workflow can be overwritten by another workflow." msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "i-doit administration interface with TTS configuration" +#: ../system/core-workflows/how-do-they-work.rst:180 +msgid "" +"If set to ``yes``, no further worflows will be executed after the current " +"one." msgstr "" -#: ../system/integrations/i-doit.rst:104 -msgid "TTS-Type" +#: ../system/core-workflows/how-do-they-work.rst:184 +msgid "Priority" msgstr "" -#: ../system/integrations/i-doit.rst:104 -msgid "``Zammad``" +#: ../system/core-workflows/how-do-they-work.rst:186 +msgid "" +"You can define the sequence, in which the workflows are executed. The " +"default value is ``500``." msgstr "" -#: ../system/integrations/i-doit.rst:115 -msgid "Username / Password" +#: ../system/core-workflows/how-do-they-work.rst:189 +msgid "" +"The workflows are executed in ascending order by their priority. That means " +"lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." msgstr "" -#: ../system/integrations/i-doit.rst:107 -msgid "Login credentials for a Zammad agent." +#: ../system/core-workflows/learn-by-example.rst:2 +msgid "Learn by Example" msgstr "" -#: ../system/integrations/i-doit.rst:109 +#: ../system/core-workflows/learn-by-example.rst:4 msgid "" -"This agent must have **read permission** for all :doc:`groups ` that plan on using the i-doit integration." +"This page provides some basic examples for Core Workflows. Of course you can " +"build much more complex workflows if needed." msgstr "" -#: ../system/integrations/i-doit.rst:113 +#: ../system/core-workflows/learn-by-example.rst:7 msgid "" -"You may even wish to create a dedicated agent account just for this " -"integration (otherwise, if the agent ever changes her password, you will " -"have to remember to update it here)." +"To learn about Core Workflows in detail, first go to :doc:`how-do-they-work`." msgstr "" -#: ../system/integrations/i-doit.rst:117 -msgid "URL incl. protocol" +#: ../system/core-workflows/learn-by-example.rst:10 +msgid "Group Based Examples" msgstr "" -#: ../system/integrations/i-doit.rst:118 -msgid "``https://your.zammad.domain``" +#: ../system/core-workflows/learn-by-example.rst:12 +msgid "" +"All following workflows have the same base configurations. The workflow may " +"not use them all." msgstr "" -#: ../system/integrations/index.rst:2 -msgid "Integrations" +#: ../system/core-workflows/learn-by-example.rst:15 +msgid "Groups:" msgstr "" -#: ../system/integrations/index.rst:4 +#: ../system/core-workflows/learn-by-example.rst:20 +msgid "Attributes:" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:22 +msgid "Category (Single tree selection field, not mandatory, agents only)" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:23 msgid "" -"Zammad offers numerous integrations that add rich features to your instance." +"Approved (Boolean field, not mandatory, not shown, ``false`` as default)" msgstr "" -#: ../system/integrations/index.rst:6 -msgid "We're still working on this part of our documentation, stay tight!" +#: ../system/core-workflows/learn-by-example.rst:24 +msgid "Operating System (Text field, not mandatory, not shown)" msgstr "" -#: ../system/integrations/index.rst:10 -msgid "Integrations for Phone Systems" +#: ../system/core-workflows/learn-by-example.rst:25 +msgid "Software used (Single selection field, not mandatory, not shown)" msgstr "" -#: ../system/integrations/index.rst:14 -msgid "" -"Your VoIP provider or telephony system is not listed? Possibly your provider " -"supports Zammad by using the generic CTI - if you're unsure ask your " -"provider." +#: ../system/core-workflows/learn-by-example.rst:68 +msgid "Group specific values and fields" msgstr "" -#: ../system/integrations/index.rst:18 +#: ../system/core-workflows/learn-by-example.rst:28 msgid "" -"Provider does not support Zammad? Consider creating a `feature request in " -"the Zammad Community `_." +"This workflow set depends on the category field. It reduces the available " +"set of values based on the group selected." msgstr "" -#: ../system/integrations/index.rst:31 -msgid "Integrations for Authentication and Customers" +#: ../system/core-workflows/learn-by-example.rst:33 +msgid "Workflow 2nd Level group" msgstr "" -#: ../system/integrations/index.rst:44 -msgid "Integrations for Monitoring Systems" +#: ../system/core-workflows/learn-by-example.rst:35 +msgid "" +"This reduces the category options to ``2nd Level/*``, ``Internal/*`` and " +"``Others``. It also sets further required fields to mandatory and visible." msgstr "" -#: ../system/integrations/index.rst:46 -msgid "This section currently misses the following integrations:" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for 2nd level" msgstr "" -#: ../system/integrations/index.rst:48 -msgid "Icinga" +#: ../system/core-workflows/learn-by-example.rst:43 +msgid "Workflow Support group" msgstr "" -#: ../system/integrations/index.rst:49 -msgid "Monit" +#: ../system/core-workflows/learn-by-example.rst:45 +msgid "" +"This reduces the category options to ``Support/*``, ``Internal/*`` and " +"``Others``. It also sets further required fields to visible." msgstr "" -#: ../system/integrations/index.rst:50 -msgid "Nagios" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for support" msgstr "" -#: ../system/integrations/index.rst:60 -msgid "Integrations for Issue Trackers" +#: ../system/core-workflows/learn-by-example.rst:53 +msgid "Workflow Sales group" msgstr "" -#: ../system/integrations/index.rst:70 -msgid "Other Integrations" +#: ../system/core-workflows/learn-by-example.rst:55 +msgid "" +"This reduces the category options to ``Sales/*``, ``Internal/*`` and " +"``Others``." msgstr "" -#: ../system/integrations/index.rst:72 -msgid "" -"This section will hold any other integration that can't be grouped up (yet)." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for sales" msgstr "" -#: ../system/integrations/ldap/index.rst:2 -msgid "LDAP / Active Directory" +#: ../system/core-workflows/learn-by-example.rst:68 +#: ../system/integrations/slack.rst:88 +msgid "The Result" msgstr "" -#: ../system/integrations/ldap/index.rst:4 +#: ../system/core-workflows/learn-by-example.rst:63 msgid "" -"Zammad comes with a powerful LDAP integration that allows you to have a " -"single source of truth. By this you reduce the number of login credentials " -"your user has to remember." +"This is what the agent would experience with the above workflows in place." msgstr "" -#: ../system/integrations/ldap/index.rst:10 +#: ../system/core-workflows/learn-by-example.rst:0 msgid "" -"The LDAP source is also a perfect candidate for Zammad's :docs:`Kerberos " -"Single Sign-On ` but also works as addition " -"to other :doc:`/settings/security/third-party`." +"Workflow shows objects and limits options based on selections on the group" msgstr "" -#: ../system/integrations/ldap/index.rst:None -msgid "Zammands LDAP management page" +#: ../system/core-workflows/learn-by-example.rst:90 +msgid "Approval process" msgstr "" -#: ../system/integrations/ldap/index.rst:25 -msgid "📝 :doc:`manage`" +#: ../system/core-workflows/learn-by-example.rst:71 +msgid "" +"In this case ``approved`` is visible to agents by default. For this " +"workflow, an additional role ``Approval person`` is required (no further " +"permissions)." msgstr "" -#: ../system/integrations/ldap/index.rst:25 -msgid "Add, modify, remove or re-arrange your LDAP-Sources as needed." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that restricts an approval attribute to specific roles" msgstr "" -#: ../system/integrations/ldap/index.rst:30 -msgid "Before you continue, please note the following limitations." +#: ../system/core-workflows/learn-by-example.rst:81 +msgid "" +"This workflow may work best in combination with a :doc:`trigger ` but technically, this is not required." msgstr "" -#: ../system/integrations/ldap/index.rst:32 -msgid "Mapping / Synchronizing organizations is not possible" +#: ../system/core-workflows/learn-by-example.rst:84 +msgid "" +"Select fields may be a better approach because they allow more values than " +"just a simple ``true`` or ``false``." msgstr "" -#: ../system/integrations/ldap/index.rst:36 +#: ../system/core-workflows/learn-by-example.rst:0 msgid "" -"You may want to consider using domain based assignments to overcome this " -"issue. Learn more on :doc:`/manage/organizations/index`." +"Workflow fixes possible values of \"Approved ?\" to a specific selection " +"depending on the users role" msgstr "" -#: ../system/integrations/ldap/index.rst:39 +#: ../system/core-workflows/learn-by-example.rst:103 +msgid "State dependent mandatory fields" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:93 msgid "" -"Zammad's LDAP sync is one way. Editing user settings or permissions may be " -"overwritten upon the next sync depending on your configuration." +"This workflow sets ``Category`` to mandatory if the agent wants to set the " +"states ``closed`` or ``pending close`` to enforce categorization." msgstr "" -#: ../system/integrations/ldap/index.rst:41 -msgid "Nested groups are not supported." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that sets fields to mandatory on specific states" msgstr "" -#: ../system/integrations/ldap/index.rst:42 -msgid "Synchronizing user avatars from LDAP is not supported." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "" +"Workflow sets category field to mandatory upon choosing closed or pending " +"close as state" msgstr "" -#: ../system/integrations/ldap/index.rst:43 -msgid "Unlike user filters, group filters cannot be changed." +#: ../system/core-workflows/learn-by-example.rst:106 +msgid "Manual Ticket Handover Process" msgstr "" -#: ../system/integrations/ldap/index.rst:44 -msgid "" -"When a user originates from an LDAP server, Zammad will try to verify the " -"login credentials against LDAP first - if this fails Zammad will check its " -"local database." +#: ../system/core-workflows/learn-by-example.rst:108 +msgid "This example covers the handover of a ticket from one agent to another:" msgstr "" -#: ../system/integrations/ldap/index.rst:50 +#: ../system/core-workflows/learn-by-example.rst:110 msgid "" -"Users can have local passwords even if they're LDAP users! You can learn " -"more about user accounts in general on :doc:`/manage/users/index`." +"When the ticket owner is modified, a new text field (\"Handover\") shows up " +"for a comment" msgstr "" -#: ../system/integrations/ldap/index.rst:54 +#: ../system/core-workflows/learn-by-example.rst:112 msgid "" -"When several LDAP sources contain the same user (meaning the same email " -"address), the user in question will be updated with every source configured. " -"*The last LDAP source will win.*" +"This may only be visible when the owner is changed, therefore it has to be " +"hidden in general" msgstr "" -#: ../system/integrations/ldap/index.rst:58 -msgid "" -"This is subject to change with `Issue 4109 `_ in the future." +#: ../system/core-workflows/learn-by-example.rst:114 +msgid "The input in this handover text field is mandatory" msgstr "" -#: ../system/integrations/ldap/index.rst:60 +#: ../system/core-workflows/learn-by-example.rst:115 msgid "" -"Synchronization statistics currently affect *all* configured LDAP sources. " -"This also applies for newly added or updated sources." +"After submitting changes, the value of the handover field must be added as " +"an note to the ticket (via trigger)" msgstr "" -#: ../system/integrations/ldap/index.rst:63 -msgid "" -"This is subject to change with `Issue 4108 `_ in the future." +#: ../system/core-workflows/learn-by-example.rst:121 +msgid "Hiding handover field" msgstr "" -#: ../system/integrations/ldap/index.rst:65 -msgid "" -"Zammad currently has limited fallback server support. You can workaround " -"this by providing several sources - however, ensure to have the exact same " -"configuration on your fallback." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Hiding the handover field in core workflows" msgstr "" -#: ../system/integrations/ldap/index.rst:69 -msgid "" -"This is subject to improve with `Issue 4107 `_ in the future." +#: ../system/core-workflows/learn-by-example.rst:126 +msgid "Showing handover field and setting it to mandatory" msgstr "" -#: ../system/integrations/ldap/index.rst:76 -msgid "" -"This section holds all requests Zammad handled for all LDAP sources. These " -"entries can either contain synchronization information or logins " -"(authentication attempts via Zammad's login interface)." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Showing the handover field and set it as mandatory" msgstr "" -#: ../system/integrations/ldap/index.rst:80 -msgid "" -"By clicking on any request, Zammad will provide even more information. The " -"provided information can be useful when something does not work as expected." +#: ../system/core-workflows/learn-by-example.rst:131 +msgid "Trigger writing handover input to a new article" msgstr "" -#: ../system/integrations/ldap/index.rst:85 -msgid "" -"Especially a LDAP synchronization can cause many log entries. The web " -"interface will always limit the number of shown entries to the last 50 " -"entries." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Write handover content to a new article" msgstr "" -#: ../system/integrations/ldap/index.rst:None +#: ../system/core-workflows/learn-by-example.rst:133 msgid "" -"Screencast showing LDAP integration log entries and a detail view on\n" -"an entry." +"As a result, the ticket includes an article of the type note which includes " +"the predefined text and the handover comment." msgstr "" -#: ../system/integrations/ldap/manage.rst:2 -msgid "Manage LDAP-Sources" +#: ../system/core-workflows/limitations.rst:6 +msgid "Core Workflows do not replace Triggers" msgstr "" -#: ../system/integrations/ldap/manage.rst:6 +#: ../system/core-workflows/limitations.rst:5 msgid "" -"Please keep in mind all current limitations for the LDAP synchronization. " -"This will help to understand scopes of the following operations better." +"Workflows manipulate the behavior of fields. However, they do not set values " +"in fields because of actions." msgstr "" -#: ../system/integrations/ldap/manage.rst:65 -msgid "Add new source" +#: ../system/core-workflows/limitations.rst:16 +msgid "API calls are only partly affected" msgstr "" -#: ../system/integrations/ldap/manage.rst:10 +#: ../system/core-workflows/limitations.rst:9 msgid "" -"Using the *New Source* button allows you to add new LDAP sources to your " -"installation. You're not limited in the number of sources, however, keep in " -"mind that many sources will also take more time to synchronize." +"Some options affect UI only and thus do not restrict responses and calls." msgstr "" -#: ../system/integrations/ldap/manage.rst:14 -msgid "" -"You can choose between different encryption types, namely *SSL* and " -"*STARTTLS* or none of them (\"*No SSL*\"). If you choose *SSL* or " -"*STARTTLS*, Zammad will display an additional *SSL verification* option that " -"allows you to disable the verification, e.g. for self-signed SSL " -"certificates. You can also tell Zammad to use a different port by appending " -"``:`` to your hostname/IP." +#: ../system/core-workflows/limitations.rst:11 +msgid "This affects the following actions:" msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "" -"Screenshot of configuring a new LDAP source with SSL encryption and SSL " -"verification" +#: ../system/core-workflows/limitations.rst:13 +msgid "select" msgstr "" -#: ../system/integrations/ldap/manage.rst:26 -msgid "" -"New Source with SSL transport security enabled and certificate verification" +#: ../system/core-workflows/limitations.rst:14 +msgid "auto select" msgstr "" -#: ../system/integrations/ldap/manage.rst:30 -msgid "" -"Using an user filter can be a good idea if you only require a small subset " -"of your LDAP users in Zammad." +#: ../system/core-workflows/limitations.rst:15 +msgid "show" msgstr "" -#: ../system/integrations/ldap/manage.rst:42 -msgid "This especially affects inactive users" +#: ../system/core-workflows/limitations.rst:16 +msgid "hide" msgstr "" -#: ../system/integrations/ldap/manage.rst:34 -msgid "" -"As every LDAP behaves differently on which attributes and how they are set, " -"Zammad doesn't care about any flags." +#: ../system/core-workflows/limitations.rst:25 +msgid "Some fields stay unavailable to customers" msgstr "" -#: ../system/integrations/ldap/manage.rst:37 +#: ../system/core-workflows/limitations.rst:19 msgid "" -"Users that no longer are returned by your LDAP source will automatically be " -"set to inactive. Zammad assumes that the user was deactivated." +"For technical and security reasons, some default fields (the pale ones you " +"can't edit) stay unavailable for display and usage on customer permissions." msgstr "" -#: ../system/integrations/ldap/manage.rst:41 +#: ../system/core-workflows/limitations.rst:23 msgid "" -"Users will never be removed automatically! If you want to remove obsolete " -"users, use :doc:`/system/data-privacy`." +"If you require your customers to change e.g. priorities, please consider " +"using workarounds via :doc:`/system/objects` and :doc:`/manage/trigger`." msgstr "" -#: ../system/integrations/ldap/manage.rst:46 -msgid "Active Directory admins" +#: ../system/core-workflows/limitations.rst:29 +msgid "Ticket title changes not supported in edit mask" msgstr "" -#: ../system/integrations/ldap/manage.rst:45 +#: ../system/core-workflows/limitations.rst:28 msgid "" -"Active Directories are quite specific on how to filter for active users only " -"- please see the `Microsoft documentation `_ for more " -"information." +"It is currently not possible to perform changes of the ticket title in the " +"edit mask (e.g. renaming, set to read-only)." msgstr "" -#: ../system/integrations/ldap/manage.rst:51 -msgid "" -"*Do not* manually write pathes of either LDAP attributes or groups. If " -"Zammad does not display them, it either cannot find them or you have a lot " -"of users that don't have the attributes populated." +#: ../system/core-workflows/limitations.rst:37 +msgid "What is out of scope of Core Workflows?" msgstr "" -#: ../system/integrations/ldap/manage.rst:55 +#: ../system/core-workflows/limitations.rst:32 msgid "" -"Zammad will always only return attributes that are filled - this reduces the " -"returned list of attributes greatly." +"There are some things that would count as workflow but are either done via :" +"doc:`/manage/trigger` or :doc:`/manage/scheduler`." msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing how to add a new LDAP source" +#: ../system/core-workflows/limitations.rst:35 +msgid "Such as (but not limited to):" msgstr "" -#: ../system/integrations/ldap/manage.rst:63 -msgid "" -"If your LDAP system doesn't allow anonymous bind, Zammad detects it and " -"provides you an editable \"Base DN\" *text* field instead of a prefilled " -"*select* field." +#: ../system/core-workflows/limitations.rst:37 +msgid "up- or downgrade permissions of users" msgstr "" -#: ../system/integrations/ldap/manage.rst:81 -msgid "Review or edit existing source" +#: ../system/core-workflows/limitations.rst:38 +msgid "affecting article creation or listing" msgstr "" -#: ../system/integrations/ldap/manage.rst:68 +#: ../system/data-privacy.rst:2 +msgid "Data Privacy" +msgstr "" + +#: ../system/data-privacy.rst:4 msgid "" -"Clicking on a LDAP source will provide a configuration and mapping overview." +"For compliance with GDPR and other data privacy laws, you may wish to " +"**permanently delete users from the system**, along with **all of their " +"associated tickets**." msgstr "" -#: ../system/integrations/ldap/manage.rst:70 +#: ../system/data-privacy.rst:8 msgid "" -"If needed you can then use the *Change* button to update either the name, " -"active state or the whole configuration. If you're changing the whole " -"configuration, the dialogue will be identical to the source creation." +"You can create manual deletion tasks or even automated deletion tasks for " +"tickets and users based on custom conditions via :doc:`scheduler `!" msgstr "" -#: ../system/integrations/ldap/manage.rst:76 +#: ../system/data-privacy.rst:12 msgid "" -"Did your LDAP server change? Different LDAP servers have different " -"structures and default attributes. This causes the LDAP synchronization to " -"likely fail. Consider removing the affected source and re-add it." +"Access to this panel requires ``admin.data_privacy`` permissions (introduced " +"in Zammad 3.5)." msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing the update of the source name." +#: ../system/data-privacy.rst:15 +msgid "" +"On older systems that have not been updated yet, customers can also be :docs:" +"`deleted via the Zammad console `." msgstr "" -#: ../system/integrations/ldap/manage.rst:89 -msgid "Re-arrange LDAP source's order" +#: ../system/data-privacy.rst:22 +msgid "User deletion dialog in the Data Privacy panel" msgstr "" -#: ../system/integrations/ldap/manage.rst:84 +#: ../system/data-privacy.rst:22 msgid "" -"You can change the synchronization order for each source at any time. Zammad " -"will synchronize the sources from top to bottom." +"The user deletion dialog lists some of the tickets that will be removed from " +"the system along with the user." msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "" -"Screencasting showing how to change the source order by using\n" -"drag and drop." +#: ../system/data-privacy.rst:27 +msgid "Deleting Users via GUI" msgstr "" -#: ../system/integrations/ldap/manage.rst:101 -msgid "Remove a source" +#: ../system/data-privacy.rst:29 +msgid "🔥 **All deletions are FINAL!**" msgstr "" -#: ../system/integrations/ldap/manage.rst:92 -msgid "" -"If you no longer need the a LDAP source or simply want to start over, you " -"can remove them at any time. This will not remove synchronized users, data " -"synchronized or permissions." +#: ../system/data-privacy.rst:31 +msgid "Once you click “Delete”, the action cannot be canceled or undone." msgstr "" -#: ../system/integrations/ldap/manage.rst:98 +#: ../system/data-privacy.rst:33 msgid "" -"Not sure if you'd need the source later on? Set the source to inactive " -"instead of removing it - see *Review or edit existing source* for more." +"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." msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing how to remove LDAP sources." +#: ../system/data-privacy.rst:36 +msgid "**The following records cannot be deleted:**" msgstr "" -#: ../system/integrations/pgp/index.rst:2 -msgid "PGP" +#: ../system/data-privacy.rst:38 +msgid "your own account" msgstr "" -#: ../system/integrations/pgp/index.rst:7 -msgid "" -"Pretty Good Privacy (PGP) is another method for secure email communication. " -"With PGP, you can exchange **signed** and **encrypted** messages with others." +#: ../system/data-privacy.rst:39 +msgid "the system's last remaining administrator account" msgstr "" -#: ../system/integrations/pgp/index.rst:13 -#: ../system/integrations/smime/index.rst:17 -msgid "Signing" +#: ../system/data-privacy.rst:42 +msgid "Step 1: Find a User / Confirm Deletion" msgstr "" -#: ../system/integrations/pgp/index.rst:11 -msgid "is a proof that a message hasn't been manipulated on its way." +#: ../system/data-privacy.rst:44 +msgid "There are three ways to access the user deletion dialog:" msgstr "" -#: ../system/integrations/pgp/index.rst:13 -msgid "" -"In other words, it guarantees message **integrity** and **authenticity**." +#: ../system/data-privacy.rst:51 +msgid "**from the user's profile**" msgstr "" -#: ../system/integrations/pgp/index.rst:19 -#: ../system/integrations/smime/index.rst:22 -msgid "Encryption" +#: ../system/data-privacy.rst:0 +msgid "Accessing the user deletion dialog in a user profile" msgstr "" -#: ../system/integrations/pgp/index.rst:16 -#: ../system/integrations/smime/index.rst:20 -msgid "" -"scrambles a message so that it can only be unscrambled by the intended " -"recipient." +#: ../system/data-privacy.rst:51 +msgid "Click **Action > Delete**." msgstr "" -#: ../system/integrations/pgp/index.rst:19 -msgid "" -"In other words, it guarantees message **privacy** and **data security**." +#: ../system/data-privacy.rst:58 +msgid "**in the “Manage > Users” Admin Panel**" msgstr "" -#: ../system/integrations/pgp/index.rst:25 -msgid "Screenshot of ticket creation with encrypt and sign buttons" +#: ../system/data-privacy.rst:0 +msgid "Accessing the user deletion dialog under “Users” in the Admin Panel" msgstr "" -#: ../system/integrations/pgp/index.rst:25 -msgid "" -"Once PGP has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " -"appear in the ticket composer." +#: ../system/data-privacy.rst:58 +msgid "Use the **⋮ Actions** menu for the target user." msgstr "" -#: ../system/integrations/pgp/index.rst:28 -msgid "**Sign button not visible?**" +#: ../system/data-privacy.rst:66 ../system/data-privacy.rst:104 +msgid "**in the “System > Data Privacy” Admin Panel**" msgstr "" -#: ../system/integrations/pgp/index.rst:30 +#: ../system/data-privacy.rst:0 msgid "" -"Please note that the signing of emails is based on the outgoing email " -"account. That means you have to choose a group with a sender email account, " -"which has a private key assigned." +"Accessing the user deletion dialog under “Data Privacy” in the Admin Panel" msgstr "" -#: ../system/integrations/pgp/index.rst:35 -msgid "Handling of Keys" +#: ../system/data-privacy.rst:65 +msgid "" +"Use the **New Deletion Task** button. Search for users by name or email " +"address." msgstr "" -#: ../system/integrations/pgp/index.rst:36 -msgid "" -"To use the PGP function, you have to enable the integration (PGP) by " -"switching the toggle to *enabled*." +#: ../system/data-privacy.rst:79 +msgid "**Delete organizations**" msgstr "" -#: ../system/integrations/pgp/index.rst:39 +#: ../system/data-privacy.rst:69 msgid "" -"You can add keys by clicking the *add key* button. The keys can be imported " -"from a file or you can paste the content of the key in the text box." +"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:" msgstr "" -#: ../system/integrations/pgp/index.rst:42 -msgid "**Which keys do I have to import?**" +#: ../system/data-privacy.rst:0 +msgid "Deleting an organization via the user deletion dialog" msgstr "" -#: ../system/integrations/pgp/index.rst:44 +#: ../system/data-privacy.rst:78 msgid "" -"For **signing** *outgoing* emails, you have to import the private key of " -"your Zammad email account." +"If this option does not appear, make sure there are no pending deletion " +"tasks for other customers from this organization." msgstr "" -#: ../system/integrations/pgp/index.rst:47 -msgid "" -"For **encrypting** *outgoing* emails, you have to import the public key of " -"the customer's email account." +#: ../system/data-privacy.rst:82 +msgid "Step 2: Monitor Deletion Job Status" msgstr "" -#: ../system/integrations/pgp/index.rst:50 +#: ../system/data-privacy.rst:84 msgid "" -"For **verifying the signature** of signed *incoming* emails, you have to " -"import the public key of the customer." +"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:" msgstr "" -#: ../system/integrations/pgp/index.rst:53 -msgid "" -"For **decrypting** of encrypted *incoming* emails, you have to import the " -"private key of your Zammad email account." +#: ../system/data-privacy.rst:98 +msgid "**in the Activity Stream**" msgstr "" -#: ../system/integrations/pgp/index.rst:57 -msgid "Import Keys From a File" +#: ../system/data-privacy.rst:0 +msgid "Activity Stream showing data privacy tasks" msgstr "" -#: ../system/integrations/pgp/index.rst:58 -msgid "You can import keys from a file in the section **Upload key**:" +#: ../system/data-privacy.rst:94 +msgid "" +"For each deleted user, the Activity Stream will be updated twice—once when " +"the task is created, and once when it's complete." msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of adding a key via file" +#: ../system/data-privacy.rst:97 +msgid "" +"These notifications are only visible to users with ``admin.data_privacy`` " +"permissions." msgstr "" -#: ../system/integrations/pgp/index.rst:64 +#: ../system/data-privacy.rst:0 msgid "" -"**Supported file formats:** ASCII-armor as well as binary GPG format " -"(basically any GPG supported key format) is supported here." +"The task list within Data Privacy shows removals being in progress and " +"completed." msgstr "" -#: ../system/integrations/pgp/index.rst:68 -msgid "Import Keys by Pasting the Content" +#: ../system/data-privacy.rst:107 +msgid "Frequently Asked Questions" msgstr "" -#: ../system/integrations/pgp/index.rst:69 -msgid "You can also paste the key's content in the section **paste key**:" +#: ../system/data-privacy.rst:121 +msgid "What happens if I receive an email from a deleted customer?" msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of adding a key via pasting" +#: ../system/data-privacy.rst:110 +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/integrations/pgp/index.rst:75 +#: ../system/data-privacy.rst:115 msgid "" -"**Supported format:** Please note that only ASCII-armor is supported here." +"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**." msgstr "" -#: ../system/integrations/pgp/index.rst:78 -msgid "Deleting Keys" +#: ../system/data-privacy.rst:130 +msgid "What about user information stored in internal notes or other messages?" msgstr "" -#: ../system/integrations/pgp/index.rst:79 +#: ../system/data-privacy.rst:124 msgid "" -"If you want to delete a specific key, you can do it by clicking on the menu " -"in the *actions* column and select **delete**:" +"The deletion process removes **user accounts and associated tickets only**." msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of deleting a key" +#: ../system/data-privacy.rst:126 +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." msgstr "" -#: ../system/integrations/pgp/index.rst:88 -msgid "Downloading Keys" +#: ../system/data-privacy.rst:137 +msgid "I deleted an user and can still see a message they sent!" msgstr "" -#: ../system/integrations/pgp/index.rst:89 +#: ../system/data-privacy.rst:133 msgid "" -"If you want to download your keys, you can do this as well via corresponding " -"action buttons. Depending on the key, you can choose wether you want to " -"download the private or the public key." +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:95 -#: ../system/integrations/smime/manage-certificates.rst:76 -msgid "Default Behavior" +#: ../system/data-privacy.rst:141 +msgid "I removed a customer, now my reporting is off!" msgstr "" -#: ../system/integrations/pgp/index.rst:96 +#: ../system/data-privacy.rst:140 msgid "" -"Here you can adjust on per group basis, if *sign* and *encryption* is on or " -"off by default. Please be aware, that agents can always override the setting " -"for each individual article." +"When removing users and their tickets, all references are removed. This also " +"affects e.g. Reporting - these information are lost." msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Adjusting default behavior on per group basis" +#: ../system/data-privacy.rst:145 +msgid "How long does Zammad store created tasks?" msgstr "" -#: ../system/integrations/pgp/index.rst:107 +#: ../system/data-privacy.rst:144 msgid "" -"Here you can see the last actions regarding signing and encryption and if " -"they were successful." -msgstr "" - -#: ../system/integrations/pgp/index.rst:117 -msgid "**Sign button is not visible, but keys are imported.**" +"Please see the on-premise data section of the :docs:`data privacy ` chapter." msgstr "" -#: ../system/integrations/pgp/index.rst:115 -msgid "Did you choose a group in the ticket?" +#: ../system/data-privacy.rst:150 +msgid "What about re-assigned tickets? I want to delete them, too." msgstr "" -#: ../system/integrations/pgp/index.rst:116 +#: ../system/data-privacy.rst:148 msgid "" -"Did you import a private key for the email adress, which is used for " -"outgoing emails in the group?" +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:122 -msgid "**How to obtain keys?**" +#: ../system/data-privacy.rst:154 +msgid "Why are there so many deletion task entries, I didn't create them!" msgstr "" -#: ../system/integrations/pgp/index.rst:120 +#: ../system/data-privacy.rst:153 msgid "" -"You can create them yourself! There are some good tutorials on the web on " -"how to create them. Providing keys to Zammad is a prerequisite to use the " -"PGP feature." -msgstr "" - -#: ../system/integrations/pgp/index.rst:127 -msgid "**It says a passphrase is needed, but I haven't got one.**" +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:125 -msgid "" -"If the key is secured with a passphrase, you have to provide it for the " -"import in Zammad. It is possible that keys may have an empty passphrase. " -"However, this is *not* recommended." +#: ../system/integrations/checkmk/admin-panel-reference.rst:2 +msgid "Admin Panel Reference" msgstr "" -#: ../system/integrations/pgp/index.rst:132 -msgid "**How do my customers get my new key?**" +#: ../system/integrations/checkmk/admin-panel-reference.rst:None +msgid "Screenshot of Checkmk settings overview" msgstr "" -#: ../system/integrations/pgp/index.rst:130 +#: ../system/integrations/checkmk/admin-panel-reference.rst:12 msgid "" -"You have to provide your **public** key in advance. Your customer also has " -"to configure PGP in their email workflow and import your public key. The " -"other way round, you have to get the public key of your customer and have to " -"import it to Zammad." +"Which :doc:`group ` should Checkmk tickets be assigned " +"to as a default (*i.e.,* when none is specified)?" msgstr "" -#: ../system/integrations/slack.rst:2 -msgid "Slack" +#: ../system/integrations/checkmk/admin-panel-reference.rst:15 +msgid "(Applies to :ref:`API alerts ` only.)" msgstr "" -#: ../system/integrations/slack.rst:4 -msgid "**⚠️ Deprecation warning ⚠️**" +#: ../system/integrations/checkmk/admin-panel-reference.rst:21 +msgid "Auto close" msgstr "" -#: ../system/integrations/slack.rst:6 +#: ../system/integrations/checkmk/admin-panel-reference.rst:18 msgid "" -"Zammad 7 will no longer support this dedicated Slack integration. It is " -"recommended to switch to :doc:`pre-defined webhooks ` instead. Existing Slack integrations should " -"be migrated manually before this feature is dropped." +"Should Zammad automatically close tickets if a service has recovered on its " +"own?" msgstr "" -#: ../system/integrations/slack.rst:14 -msgid "" -"In order to use this feature, please add a new Slack app to your Workspace. " -"The App you need is called ``Incoming WebHooks`` ." +#: ../system/integrations/checkmk/admin-panel-reference.rst:21 +msgid "(Agents will receive notifications for such closures as appropriate.)" msgstr "" -#: ../system/integrations/slack.rst:18 -msgid "Why Do I Need This Feature?" +#: ../system/integrations/checkmk/admin-panel-reference.rst:30 +msgid "Auto-close state" msgstr "" -#: ../system/integrations/slack.rst:20 -msgid "" -"If you're already using Slack for your team communication, you'll love this " -"feature! Our Slack integration can push ticket notifications about the last " -"ticket article based on the following events:" +#: ../system/integrations/checkmk/admin-panel-reference.rst:24 +msgid "What ticket state should be applied when “auto-closing” a ticket?" msgstr "" -#: ../system/integrations/slack.rst:24 -msgid "on Ticket creation" +#: ../system/integrations/checkmk/admin-panel-reference.rst:26 +msgid "" +"You can choose from the seven built-in ticket states. If these states aren't " +"enough for you, you can :ref:`define a new ticket state ` for this purpose as well. This can be useful for tracking " +"tickets with :doc:`reports `, for example." msgstr "" -#: ../system/integrations/slack.rst:25 -msgid "on Ticket updates" +#: ../system/integrations/checkmk/admin-panel-reference.rst:35 +#: ../system/integrations/cti/includes/recent-logs.include.rst:2 +#: ../system/integrations/ldap/index.rst:74 +#: ../system/integrations/pgp/index.rst:106 +msgid "Recent Logs" msgstr "" -#: ../system/integrations/slack.rst:26 -msgid "on reached reminders" +#: ../system/integrations/checkmk/admin-panel-reference.rst:None +msgid "Screenshot of Checkmk \"Recent Logs\" section" msgstr "" -#: ../system/integrations/slack.rst:27 -msgid "a Ticket has escalated" +#: ../system/integrations/checkmk/admin-panel-reference.rst:41 +msgid "" +"If you're having trouble getting Zammad and Checkmk to play nicely together, " +"this section can help you troubleshoot." msgstr "" -#: ../system/integrations/slack.rst:28 -msgid "a Ticket is going to escalate" +#: ../system/integrations/checkmk/admin-panel-reference.rst:44 +msgid "" +"It contains a record of the fifty most recent transactions that Zammad knows " +"about, including each one's request/response details and return status." msgstr "" -#: ../system/integrations/slack.rst:30 -msgid "" -"Zammad will provide the Ticket title, a direct link to the Ticket, the event " -"type (creation, updated, escalation), the customer, time and the last " -"article that has triggered the notification." +#: ../system/integrations/checkmk/api-reference.rst:2 +msgid "API Reference" msgstr "" -#: ../system/integrations/slack.rst:34 +#: ../system/integrations/checkmk/api-reference.rst:4 msgid "" -"This will give you further options, as you can see e.g. escalating tickets " -"that are assigned to an agent that's e.g. absent. You can interact faster, " -"as you might see problems earlier (or even before the problem gets one)." +"For most users, :ref:`the sample scripts from the Setup Guide ` will do the job just fine. But if you want more fine-grained control" +"—for instance, to create high- and low-priority tickets for different types " +"of system events—then you'll have to customize the data those scripts send " +"to Zammad." msgstr "" -#: ../system/integrations/slack.rst:38 +#: ../system/integrations/checkmk/api-reference.rst:15 msgid "" -"If needed and wanted, you can even discuss directly about the topic before " -"sending an answer to the customer. Another possible use case would be a " -"agent monitoring new agents and their answers to tickets." +"This custom script will automatically set all tickets it creates to **high " +"priority** and **assign them to charlie@chrispresso.com**." msgstr "" -#: ../system/integrations/slack.rst:44 -msgid "Configure the Integration" +#: ../system/integrations/checkmk/api-reference.rst:32 +msgid "How Does it Work?" msgstr "" -#: ../system/integrations/slack.rst:46 +#: ../system/integrations/checkmk/api-reference.rst:34 msgid "" -"First of all, please go to your slack workspace - go to administration => " -"Manage Apps. If you don't have an app yet, you can simply add a new one - " -"just search for ``Incoming WebHooks`` and customize the app to your needs." +"There are two kinds of data you can pass to the API, both in the form of key-" +"value pairs:" msgstr "" -#: ../system/integrations/slack.rst:50 -msgid "" -"Choose (or create) the channel Zammad should post it's information to and " -"press on \"Add Incoming WebHooks integration\". If you're ready, copy the " -"provided WebHook URL and go to your Zammad installation." +#: ../system/integrations/checkmk/api-reference.rst:44 +msgid "Checkmk parameters" msgstr "" -#: ../system/integrations/slack.rst:56 +#: ../system/integrations/checkmk/api-reference.rst:38 msgid "" -"You need administrative rights on the Slack Workspace. The link to the app " -"directory is normally ``https://[workspace-name].slack.com/apps`` ." +"are required, and make up the **contents** of the resulting tickets/" +"articles. They also determine whether an event creates a new ticket or " +"updates/closes an existing one." msgstr "" -#: ../system/integrations/slack.rst:63 +#: ../system/integrations/checkmk/api-reference.rst:42 msgid "" -"To configure the slack integration, log in to Zammad and go to Integrations " -"(System) => Slack in the admin panel." +"These are the only values used in the sample scripts. **Use them as-is**; " +"technically, they can be customized, but it's hard to imagine a good reason " +"for it." msgstr "" -#: ../system/integrations/slack.rst:66 -msgid "" -"Here you can choose on what evens Zammad should post information about a " -"ticket to your Slack channel. Next you need to device what groups shall be " -"affected by this, as anybody with access to that specific Slack channel can " -"read at least parts of the ticket this might be a privacy issue, if you " -"select the wrong groups. The username is simply the name that Zammad uses as " -"display name inside the Slack chat. The channel defines the Slack channel " -"the information is being posted in. As last option, you can set a custom " -"icon for posting to slack." +#: ../system/integrations/checkmk/api-reference.rst:52 +msgid "Ticket attributes" msgstr "" -#: ../system/integrations/slack.rst:74 +#: ../system/integrations/checkmk/api-reference.rst:47 msgid "" -"When you're ready, just hit \"Submit\" and enable the integration. Zammad " -"will now post new ticket information based on the trigger you chose. Below " -"the options you have the recent log that shows the latest requests to Slack " -"for debugging if needed." +"are optional, and can be used to **adjust settings** on newly created " +"tickets (*e.g.,* set the owner, group, priority, or state)." msgstr "" -#: ../system/integrations/slack.rst:81 +#: ../system/integrations/checkmk/api-reference.rst:50 msgid "" -"If you leave the Icon URL empty, Zammad will use the Zammad logo instead. " -"The icon should be a square PNG file." +"If you want to customize your Checkmk alert script, do it with these. Simply " +"add an extra “form” option for each one (``-F \"key=value\"``) to your " +"script's ``curl`` command line, as in the example above." msgstr "" -#: ../system/integrations/slack.rst:90 -msgid "" -"The following figure shows how it will look if you choose to receive updates " -"on created and updated tickets. On every post Zammad sends to the Slack " -"channel, you can create new threads to discuss about the new article." +#: ../system/integrations/checkmk/api-reference.rst:54 +msgid "💡 **It's just an API endpoint!**" msgstr "" -#: ../system/integrations/slack.rst:96 +#: ../system/integrations/checkmk/api-reference.rst:56 msgid "" -"If you just want to keep track of soon escalating or already escalated " -"tickets, it will look the the following figure. Zammad changes the color in " -"front of the post so you can easily see the state of the ticket." +"When using Checkmk integration, messages need to be formatted in a certain " +"way, but that *doesn't mean the messages actually have to come from Checkmk*." msgstr "" -#: ../system/integrations/slack.rst:102 +#: ../system/integrations/checkmk/api-reference.rst:59 msgid "" -"If you change the state, Zammad will also put information on what state the " -"ticket gets and (if pending state) the date until it pends. You'll also " -"recognize the color codes in front of posts on slack, as they are exact the " -"same the ticket state colors you'll see in Zammad!" +"If you use another monitoring tool that's not officially supported by " +"Zammad, there's probably a way to make it work with your Checkmk callback " +"URL." msgstr "" -#: ../system/integrations/smime/index.rst:2 -msgid "S/MIME" +#: ../system/integrations/checkmk/api-reference.rst:63 +msgid "Checkmk Parameters" msgstr "" -#: ../system/integrations/smime/index.rst:11 +#: ../system/integrations/checkmk/api-reference.rst:65 msgid "" -"S/MIME is the most widely-supported method for secure email communication. " -"With S/MIME, you can exchange **signed** and **encrypted** messages with " -"others." +"When a notification is received, Zammad creates a new article containing the " +"details of the event that triggered it:" msgstr "" -#: ../system/integrations/smime/index.rst:15 -msgid "" -"is proof that a message hasn't been tampered with or sent by an impersonator." +#: ../system/integrations/checkmk/api-reference.rst:None +msgid "Checkmk article body" msgstr "" -#: ../system/integrations/smime/index.rst:17 +#: ../system/integrations/checkmk/api-reference.rst:72 msgid "" -"In other words, it guarantees a message's **integrity** and **authenticity**." +"These details come from the fields listed below, which correspond to " +"parameters provided by Checkmk (``$NOTIFY_*``)." msgstr "" -#: ../system/integrations/smime/index.rst:22 -msgid "In other words, it guarantees **privacy** and **data security**." +#: ../system/integrations/checkmk/api-reference.rst:75 +msgid "**Required fields are marked with an asterisk (\\*).**" msgstr "" -#: ../system/integrations/smime/index.rst:28 -msgid "Screencast demo of S/MIME features for both new tickets and replies" +#: ../system/integrations/checkmk/api-reference.rst:79 +msgid "event_id\\*" msgstr "" -#: ../system/integrations/smime/index.rst:28 +#: ../system/integrations/checkmk/api-reference.rst:78 msgid "" -"Once S/MIME has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " -"appear in the ticket composer." +"A unique ID for the system event. (``$NOTIFY_SERVICEPROBLEMID`` / " +"``$NOTIFY_HOSTPROBLEMID``)" msgstr "" -#: ../system/integrations/smime/index.rst:32 -msgid ":doc:`🔪 Prerequisites `" +#: ../system/integrations/checkmk/api-reference.rst:86 +msgid "host\\*" msgstr "" -#: ../system/integrations/smime/index.rst:31 +#: ../system/integrations/checkmk/api-reference.rst:82 msgid "" -"New to S/MIME? This section helps you to find certificate providers and " -"points out Limitations." +"The hostname of the system that the event originated from. " +"(``$NOTIFY_HOSTNAME``)" msgstr "" -#: ../system/integrations/smime/index.rst:35 -msgid ":doc:`📝 Manage Certificates `" +#: ../system/integrations/checkmk/api-reference.rst:85 +msgid "" +"Used to determine if a new event belongs to an existing ticket. Also used in " +"the subject line of the resulting article (“ is ”)." msgstr "" -#: ../system/integrations/smime/index.rst:35 -msgid "Add and download certificates; configure group default behaviors." +#: ../system/integrations/checkmk/api-reference.rst:96 +msgid "service" msgstr "" -#: ../system/integrations/smime/index.rst:38 -msgid ":doc:`😦 Troubleshooting `" +#: ../system/integrations/checkmk/api-reference.rst:89 +msgid "" +"The name of the service that the event originated from. " +"(``$NOTIFY_SERVICEDESC``)" msgstr "" -#: ../system/integrations/smime/index.rst:38 -msgid "Took a wrong turn? About recent logs and common issues." +#: ../system/integrations/checkmk/api-reference.rst:92 +msgid "Used to determine if a new event belongs to an existing ticket." msgstr "" -#: ../system/integrations/smime/index.rst:43 -msgid "" -"For more details on how S/MIME integration works on the agent side, see the :" -"user-docs:`user docs `." +#: ../system/integrations/checkmk/api-reference.rst:94 +#: ../system/integrations/checkmk/api-reference.rst:110 +msgid "Displayed as ``-`` when omitted." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:2 -msgid "Manage Certificates" +#: ../system/integrations/checkmk/api-reference.rst:104 +msgid "state\\*" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:4 +#: ../system/integrations/checkmk/api-reference.rst:99 msgid "" -"S/MIME is **disabled by default**. Enable it to start adding certificates." +"The current state of the service or host in question. " +"(``$NOTIFY_SERVICESTATE`` / ``$NOTIFY_HOSTSTATE``)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:10 -msgid "Dialogue to add new certificates or private keys" +#: ../system/integrations/checkmk/api-reference.rst:102 +msgid "" +"Used to detect when a ticket should be auto-closed (*i.e.,* on ``OK``/" +"``UP``). Also used in the subject line of the resulting article (“ is " +"”)." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:10 +#: ../system/integrations/checkmk/api-reference.rst:110 +msgid "text" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:107 msgid "" -"Manage certificates in the Admin Panel under **System > Integrations > S/" -"MIME**. Certificates may be pasted in as plain text or uploaded from a file." +"The output of the process that triggered the event. " +"(``$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:14 -msgid "Add Certificate Data" +#: ../system/integrations/checkmk/api-reference.rst:121 +msgid "" +"The Object Manager attribute panel displays built-in and custom\n" +"attribute names." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:36 -msgid "Add Certificate" +#: ../system/integrations/checkmk/api-reference.rst:121 +msgid "Find a complete list of ticket attributes in the Object Manager." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:17 +#: ../system/integrations/checkmk/api-reference.rst:123 msgid "" -"Import public-key certificates for both your own organization and your " -"contacts." +"Ticket attributes are entirely optional, and can be used to customize the " +"tickets that Checkmk creates. (Note that these attributes will be ignored if " +"a new event belongs to an existing ticket.)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:19 +#: ../system/integrations/checkmk/api-reference.rst:128 msgid "" -"You can also add a bunch of certificates in one go by providing a single " -"file with all relevant certificates." +"Why would you want to do this? Maybe you have only one IT guy, and all " +"system monitoring issues should be automatically assigned to him. Or, maybe " +"you're creating multiple notification rules so that database outages take " +"higher priority than disk space warnings." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:22 -msgid "🕵️ **ALWAYS verify certificates in-person or over the phone!**" +#: ../system/integrations/checkmk/api-reference.rst:135 +msgid "In most cases, you'll probably want to set one of the following:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:24 -msgid "" -"The whole point of signatures is to alert you when someone is trying to " -"pretend to be someone they're not. Never accept a certificate from someone " -"online without verifying it first." +#: ../system/integrations/checkmk/api-reference.rst:137 +msgid "group" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:28 -msgid "📇 **What about trusted certificate authorities?**" +#: ../system/integrations/checkmk/api-reference.rst:139 +msgid "state" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:30 -msgid "" -"In some cases (e.g. when dealing with large enterprises), you may be given a " -"certificate for an entire CA, rather than a single contact. Add it here to " -"trust *all* certificates issued by that CA." +#: ../system/integrations/checkmk/api-reference.rst:140 +msgid "priority" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:35 +#: ../system/integrations/checkmk/api-reference.rst:142 msgid "" -"Commercial CAs can usually be verified online. Zammad does not include a " -"list of built-in, trusted CAs." +"but in practice, you can set almost any attribute, including :doc:`custom " +"ones you created through the Object Manager `." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:57 -msgid "Add Private Key" +#: ../system/integrations/checkmk/api-reference.rst:145 +msgid "Please note that the following attributes are **not customizable**:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:39 -msgid "" -"Once you've added a public-key certificate, you can import its matching " -"private key." +#: ../system/integrations/checkmk/api-reference.rst:147 +msgid "title" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:42 -msgid "" -"Private keys are for **your own organization only**; never ask your contacts " -"for their private keys." +#: ../system/integrations/checkmk/api-reference.rst:148 +msgid "id" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:0 -msgid "" -"S/MIME integration showing configured certificates and possible issues with " -"Logging" +#: ../system/integrations/checkmk/api-reference.rst:149 +msgid "ticket number" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:50 -msgid "" -"A note is displayed on certificates with a matching private key (see line 2)." +#: ../system/integrations/checkmk/api-reference.rst:151 +msgid "created_by_id" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:52 -msgid "📤 **Certificates and private keys must be uploaded separately.**" +#: ../system/integrations/checkmk/api-reference.rst:152 +msgid "updated_by_id" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:54 -msgid "" -"If your certificate and private key are bundled together in the same file or " -"PEM block, import it twice (once using each button)." -msgstr "" - -#: ../system/integrations/smime/manage-certificates.rst:57 -msgid "Please note that bulk imports of private keys are not possible." +#: ../system/integrations/checkmk/api-reference.rst:155 +msgid "Which Values Can Be Set?" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:60 -msgid "Download Certificate Data" +#: ../system/integrations/checkmk/api-reference.rst:157 +msgid "😵 **Invalid values → unpredictable behavior**" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:62 +#: ../system/integrations/checkmk/api-reference.rst:159 msgid "" -"You can download the earlier provided certificates and private keys at any " -"time from your Zammad instance." +"If you provide a value that Zammad doesn't understand (*e.g.,* ``-F " +"\"priority=high\"``), it's not always clear what will happen. In some cases, " +"a ticket will be created with the default values instead - but in others, it " +"may not be created at all!" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:65 -msgid "" -"Please note that passphrase-protected private keys stay protected and when " -"you download them, you have to know the passphrase to use them after " -"downloading." +#: ../system/integrations/checkmk/api-reference.rst:164 +msgid "So what values does Zammad understand, then? Well, it depends..." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:73 -msgid "Dialogue to download certificates or private keys" +#: ../system/integrations/checkmk/api-reference.rst:168 +msgid "Use an email address or username:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:73 -msgid "Download stored certificates and their keys" +#: ../system/integrations/checkmk/api-reference.rst:190 +msgid "group & priority" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:78 -msgid "" -"The ticket composer will set all outgoing messages to **signed and " -"encrypted** by default (assuming the required certificates exist)." +#: ../system/integrations/checkmk/api-reference.rst:175 +msgid "Refer to the dropdown menus in the ticket pane:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:82 -msgid "These defaults can be modified on a per-group basis:" +#: ../system/integrations/checkmk/api-reference.rst:0 +msgid "See possible values for certain attributes in the ticket pane." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:None -msgid "Zammad allowing to choose the default behavior on per group basis" +#: ../system/integrations/checkmk/api-reference.rst:187 +msgid "🙅 **Ticket state CANNOT be set this way!**" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:89 +#: ../system/integrations/checkmk/api-reference.rst:189 msgid "" -"Of course, agents can always manually change these settings on each email " -"they send out." +"Why? Because ``-F \"state=...\"`` is already used :ref:`as a Checkmk " +"parameter `." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:4 -msgid "A certificate *and* private key for your own organization" +#: ../system/integrations/checkmk/api-reference.rst:222 +msgid "Everything Else" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:6 +#: ../system/integrations/checkmk/api-reference.rst:193 msgid "" -"(Use this to ✒️ **sign outgoing messages** and 🔓 **decrypt incoming " -"messages**.)" +"To set any other attributes, it helps to know your way around the :docs:" +"`rails console `. Valid values are those that you can " +"set with a string:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:9 -msgid "" -"Certificates belonging your contacts, or their issuing certificate authority " -"(CA)" +#: ../system/integrations/checkmk/api-reference.rst:218 +msgid "These values can then be passed directly to the API:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:11 -msgid "" -"(Use these to ✅ **verify incoming message signatures** and 🔒 **encrypt " -"outgoing messages**.)" +#: ../system/integrations/checkmk/index.rst:16 +msgid "How does it work?" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:14 -msgid "🙋 **I'm new to S/MIME. Where can I get a certificate?**" +#: ../system/integrations/checkmk/index.rst:2 +msgid "Checkmk" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:16 +#: ../system/integrations/checkmk/index.rst:4 msgid "" -"The easiest way to get certificates is to buy an annual subscription through " -"a commercial CA, such as:" +"`Checkmk `_ is a powerful IT monitoring tool that can " +"send real-time status alerts to Zammad via email or REST API. Set these " +"alerts up in Checkmk, and Zammad will automatically create, update, and " +"close tickets based on the health of your system:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:19 -msgid "" -"`Sectigo (formerly Comodo) `_" +#: ../system/integrations/checkmk/index.rst:14 +msgid "Screenshot of ticket created by Checkmk notifications" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:20 -msgid "`Secorio `_" +#: ../system/integrations/checkmk/index.rst:14 +msgid "Multiple alerts, same ticket." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:21 -msgid "`GlobalSign `_" +#: ../system/integrations/checkmk/setup-guide.rst:2 +msgid "Setup Guide" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:23 -msgid "(Zammad is not affiliated with these CAs in any way.)" +#: ../system/integrations/checkmk/setup-guide.rst:4 +msgid "" +"Whenever the Checkmk integration is enabled, Zammad listens for messages on " +"its API and over email. As long as those messages follow the required " +"format, Zammad will create new tickets (or find and update existing ones) " +"based on the message contents." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:25 +#: ../system/integrations/checkmk/setup-guide.rst:10 msgid "" -"You can also generate your own self-signed certificates, but the process is " -"complicated and usually 🙅 **involves extra work for your contacts**." +"That means that “setting up Checkmk integration” is simply a matter of " +"**adding configuration to your Checkmk site**: telling it when to send these " +"messages and what to say. To do that, you'll need to create a new " +"**notification rule** (see `Checkmk's official docs `_ for help with that)." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:29 +#: ../system/integrations/checkmk/setup-guide.rst:17 msgid "" -"Bear in mind that 🤝 **S/MIME only works if the other party is using it, too." -"**" +"As part of this new rule, you'll have to choose a **notification method** " +"(*i.e.,* a script to execute whenever the rule is triggered). This script " +"will be written by you (samples below), and contain the logic for sending " +"API/email messages to Zammad:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:32 -msgid "Certificate and Private Key Checks on Upload" +#: ../system/integrations/checkmk/setup-guide.rst:26 +msgid "Checkmk \"New Rule\" dialog" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:34 +#: ../system/integrations/checkmk/setup-guide.rst:26 msgid "" -"The certificate and public key validation is based on the ``X509v3`` " -"extensions." +"Find your custom scripts in the Checkmk WATO under **Notifications > New " +"Rule > Notification Method**." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:49 -msgid "Uploading a *client certificate*?" +#: ../system/integrations/checkmk/setup-guide.rst:29 +msgid "" +"Once you're done setting up your new rule, you're all set! New tickets " +"should start coming in and auto-updating any time your rule is triggered." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:41 -msgid "The following attributes are required then:" +#: ../system/integrations/checkmk/setup-guide.rst:33 +msgid "" +"(If you need help troubleshooting, be sure to check the :ref:`checkmk-recent-" +"logs`.)" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:39 -msgid "Subject Alternative Name (at least one email address has to be present)" +#: ../system/integrations/checkmk/setup-guide.rst:38 +msgid "API Alerts" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:40 -msgid "Key Usage (``Digital Signature`` and/or ``Key Encipherment``)" +#: ../system/integrations/checkmk/setup-guide.rst:40 +msgid "" +"To add these scripts in the Checkmk WATO, copy them into your Checkmk " +"installation directory and make them executable. (Be sure to replace the " +"``zammad.example.com`` callback URL with the one found in your admin panel.)" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:41 -msgid "Public key algorithm (either ``RSA`` or ``EC``)" +#: ../system/integrations/checkmk/setup-guide.rst:60 +msgid "Service notification" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:43 +#: ../system/integrations/checkmk/setup-guide.rst:46 msgid "" -"The Extended Key Usage attribute is optional. If the certificate provides " -"the named attribute, than it must contain the value ``E-mail Protection``." +"For updates on the status of the software running on your server (*e.g.,* " +"postgres)." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:46 -msgid "" -"Please note that any usable email adress has to be prefixed with ``email:`` " -"or ``rfc822:``." +#: ../system/integrations/checkmk/setup-guide.rst:75 +msgid "Host notification" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:49 -msgid "The named public key algorithms are mandatory for private keys as well." +#: ../system/integrations/checkmk/setup-guide.rst:63 +msgid "For updates on the status of the server itself." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:54 -msgid "Uploading a *CA certificate*?" +#: ../system/integrations/checkmk/setup-guide.rst:77 +msgid "🤔 **What's with all the env vars?**" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:52 +#: ../system/integrations/checkmk/setup-guide.rst:79 msgid "" -"In the case of an uploaded CA certificate, providing the value ``CA:TRUE`` " -"in the attribute *Basic Contstraints*, the previously mentioned attributes " -"are not verified." +"Whenever Checkmk runs these scripts, it needs to provide some information " +"about the event that triggered the notification. This information is passed " +"in the form of these ``$NOTIFY_*`` environment variables." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:56 +#: ../system/integrations/checkmk/setup-guide.rst:85 msgid "" -"In general, the usage of any expired (``Not After``) or not yet valid (``Not " -"Before``) certificate is denied for outgoing emails." +"You can specify additional parameters to pass to the script when you're " +"setting up your notification rule, but the ones you see here are all " +"provided by default." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:59 -msgid "Example certificate:" +#: ../system/integrations/checkmk/setup-guide.rst:90 +msgid "Email Alerts" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:85 +#: ../system/integrations/checkmk/setup-guide.rst:94 msgid "" -"Please note that Zammad will distrust senders by default. This means that " -"you're always required to provide certificate data, no matter if for signing " -"or encrypting." +"🐞 **There are known bugs** in Zammad's processing of email from Checkmk. " +"This section will be completed once they have been resolved. (Learn more at " +"GitHub issues `#2377 `_ & " +"`#2180 `_.)" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:89 -msgid "This is by design and can't be adjusted." +#: ../system/integrations/checkmk/setup-guide.rst:100 +msgid "In the meantime, we encourage you to set up API alerts instead." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:4 -msgid "" -"All of the system's latest S/MIME activity is displayed in the **Recent " -"Logs** section." +#: ../system/integrations/clearbit.rst:2 +msgid "Clearbit" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:11 -msgid "Sample entries of in- and outgoing S/MIME related emails." +#: ../system/integrations/clearbit.rst:4 +msgid "" +"With our Clearbit integration, you can easily enrich the information " +"provided by Zammad. If the customers or agents email address is known to " +"Clearbit, it will share all information it has regarding the user with " +"Zammad. Those information can include the following:" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:11 -msgid "" -"Logs report the status and details of all mail, both incoming and outgoing, " -"that used signing/verification or encryption/decryption." +#: ../system/integrations/clearbit.rst:9 +msgid "Avatar" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:14 -msgid "" -"This log does **not** include email sent by :doc:`triggers ` or the :doc:`scheduler `. For those, check your " -"``production.log``." +#: ../system/integrations/clearbit.rst:10 +msgid "Address information" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:20 -msgid "Common Issues" +#: ../system/integrations/clearbit.rst:11 +msgid "Website information" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:30 -msgid "I received a signed/encrypted email before I set up S/MIME integration" +#: ../system/integrations/clearbit.rst:12 +msgid "A BIO (as Note by default)" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:23 +#: ../system/integrations/clearbit.rst:14 msgid "" -"No problem. Once S/MIME has been enabled and the appropriate certificates " -"have been added, agents will be prompted to retry verification/decryption on " -"matching emails." +"If needed, you can add further custom objects and add mappings to them, so " +"the Clearbit information can be filled within the database. In general you " +"can get any information from Clearbit, as long as you have a mapping to an " +"Zammad object." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:0 -msgid "Screenshot of user prompt to retry decryption" +#: ../system/integrations/clearbit.rst:21 +msgid "" +"Clearbit does have a mapping of fields like LDAP and Exchange have, but does " +"not \"win\" against Zammad information. This means that if you have e.g. the " +"last name field filled in already and Clearbit has other information on " +"that, it will not be updated." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:38 -msgid "The 🔒 **Encrypt** button is disabled" +#: ../system/integrations/clearbit.rst:26 +msgid "" +"However: If let's say the last name has been set by Clearbit and Zammad " +"notices that the last name on the Clearbit source has changed, Zammad will " +"also update this value." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:33 -msgid "Have you added the recipient's certificate?" +#: ../system/integrations/clearbit.rst:33 +msgid "" +"The configuration of Clearbit is really easy and done fast! Just login to " +"your Clearbit-Account, go to \"API\" and copy the secret-API-Key." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:34 -msgid "Are you sure the recipient's certificate is valid?" +#: ../system/integrations/clearbit.rst:38 +msgid "" +"Now change to your Zammad instance, go to Integrations (System) -> Clearbit " +"in the admin panel. Paste your API-Key into the API-Key-Field and decide if " +"Zammad should create unknown Organizations automatically, if the user does " +"not have one yet (and Clearbit knows it). The shared option decides if the " +"new organizations Zammad creates with Clearbit should be shared ones." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:35 -msgid "Have you checked your ``production.log`` for more details?" +#: ../system/integrations/clearbit.rst:47 +msgid "" +"If you're unsure what option to choose, better stick with \"no\". You can " +"also learn more about :doc:`/manage/organizations/index`." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:37 +#: ../system/integrations/clearbit.rst:52 msgid "" -"If encryption doesn't work in the composer, it won't work in :doc:`triggers " -"` or the :doc:`scheduler ` either!" +"The Mapping option works similar to the mapping within the Exchange and LDAP " +"sync. You can add further mappings for e.g. custom fields if you need more " +"information that Clearbit can provide." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:42 -msgid "The ✅ **Sign** button is disabled" +#: ../system/integrations/clearbit.rst:58 +msgid "" +"If you want to add more Clearbit fields and want to learn more about " +"available fields on their API, you can take a look at their `API " +"documentation `_." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:41 +#: ../system/integrations/clearbit.rst:62 msgid "" -"Have you added **both the certificate and private key** for your " -"organization?" +"If you're happy with the above chosen Settings and your mapping, just save " +"the changes and enable Clearbit integration. Zammad will now start polling " +"the Clearbit API as users contact you." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:42 +#: ../system/integrations/clearbit.rst:68 msgid "" -"Does the email address on the certificate match the email address of the " -"agent/group composing the email?" +"Zammad does not synchronize with Clearbit on a regular basis, but on demand " +"if needed. This saves API calls." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:45 -msgid "Error: “Fingerprint already taken”" +#: ../system/integrations/clearbit.rst:73 +msgid "" +"Below the Settings and Mappings, you'll find our Integration log. You can " +"see what requests Zammad sent to Clearbit and also the APIs Response." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:45 -msgid "Are you sure you haven't added this certificate already?" +#: ../system/integrations/clearbit.rst:78 +msgid "" +"By the way, you can also view the API log on the Clearbit website - the " +"information seen is basically the same." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:48 -msgid "Error: “❌ invalid byte sequence in UTF-8”" +#: ../system/integrations/clearbit.rst:84 +msgid "Example When Adding a User" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:48 -msgid "Please ensure to provide PEM formatted certificate and keys." +#: ../system/integrations/clearbit.rst:86 +msgid "" +"To show you how fast information is added, we added a small Screencast " +"below. This shows the creation of the User Alex from Clearbit. As we already " +"set the last name of Alex to \"X\", Zammad did not update it. What Zammad " +"did was to add further information it received from Clearbit." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:49 -msgid "Did you check if the provided file is a valid certificate or key?" +#: ../system/integrations/cti/generic.rst:2 +msgid "CTI (generic)" msgstr "" -#: ../system/integrations/zabbix.rst:2 -msgid "Zabbix Integration" +#: ../system/integrations/cti/includes/introduction.include.rst:1 +msgid "" +"This integration enables Zammad to provide a caller log to your agents. With " +"this your agents can greet your customers by their name and are supported by " +"Zammad with automatically opening a new ticket dialog or the user profile." msgstr "" -#: ../system/integrations/zabbix.rst:5 +#: ../system/integrations/cti/includes/introduction.include.rst:6 msgid "" -"This guide describes how to integrate your Zabbix 5.4 installation with " -"Zammad using the Zabbix webhook feature. This guide will provide " -"instructions on setting up a media type, a user and an action in Zabbix." +"Click the toggle next to the heading to activate or deactivate this " +"integration." msgstr "" -#: ../system/integrations/zabbix.rst:12 -msgid "Zammad with enabled HTTP Token Authentication" +#: ../system/integrations/cti/includes/introduction.include.rst:9 +msgid "" +"If you want to learn more on how your agents can use this function, please " +"refer the :user-docs:`user documentation `." msgstr "" -#: ../system/integrations/zabbix.rst:13 -msgid "Zabbix version 5.4 or higher" +#: ../system/integrations/cti/includes/introduction.include.rst:14 +msgid "" +"Automatically opening new ticket dialogues or user profiles requires agent " +"to extension mapping - see more below." msgstr "" -#: ../system/integrations/zabbix.rst:16 -msgid "Setting up a Zammad" +#: ../system/integrations/cti/includes/introduction.include.rst:20 +msgid "Please note the following limitations to reduce confusion later on:" msgstr "" -#: ../system/integrations/zabbix.rst:18 -msgid "Enable **API Token Access** in Settings > System > API." +#: ../system/integrations/cti/includes/introduction.include.rst:22 +msgid "CTI integrations provide caller log functions only." msgstr "" -#: ../system/integrations/zabbix.rst:20 +#: ../system/integrations/cti/includes/introduction.include.rst:23 msgid "" -"Create a **new user** for a Zabbix alerter with an **email address** and " -"create a personal user token with **ticket.agent** permissions." +"This integration does not provide any VoIP functionalities; you can't make " +"phone calls from within Zammad." msgstr "" -#: ../system/integrations/zabbix.rst:24 -msgid "Zabbix Webhook Configuration" +#: ../system/integrations/cti/includes/introduction.include.rst:25 +msgid "" +"If your browser supports ``tel``-URLs, you can click on phone numbers for " +"automatic dialing. This requires additional software / configuration on your " +"agent's computers." msgstr "" -#: ../system/integrations/zabbix.rst:27 -msgid "Create a Global Macro" +#: ../system/integrations/cti/generic.rst:9 +#: ../system/integrations/cti/placetel.rst:14 +#: ../system/integrations/cti/sipgate.rst:14 +msgid "Please provide the following requirements:" msgstr "" -#: ../system/integrations/zabbix.rst:29 +#: ../system/integrations/cti/generic.rst:11 msgid "" -"Before setting up the **Webhook**, you need to setup the global macro " -"**{$ZABBIX.URL}**, which must contain the **URL** to the **Zabbix frontend**." +"A telephone system that supports webhooks (outbound) (best option are those " +"that allow customizing the calls)." msgstr "" -#: ../system/integrations/zabbix.rst:33 -msgid "" -"In the **Administration** > **Media types** section, import the `Template`_." +#: ../system/integrations/cti/generic.rst:13 +msgid "A unique Call-ID during the call session." msgstr "" -#: ../system/integrations/zabbix.rst:38 -msgid "Open the added **Zammad** media type and set:" +#: ../system/integrations/cti/generic.rst:14 +msgid "Call event data (both numbers and direction)." msgstr "" -#: ../system/integrations/zabbix.rst:40 -msgid "**zammad\\_access\\_token** to the your **Personal User Token**" +#: ../system/integrations/cti/generic.rst:15 +msgid "Your Zammad instance must be reachable for your telephony system." msgstr "" -#: ../system/integrations/zabbix.rst:41 +#: ../system/integrations/cti/generic.rst:17 msgid "" -"**zammad\\_url** to the **frontend URL** of your **Zammad** installation" +"If you want to learn more on what kind of requests are supported by Zammad " +"and what it expects, please consult our :docs:`CTI-API documentation `." msgstr "" -#: ../system/integrations/zabbix.rst:43 -msgid "**zammad\\_customer** to your **Zammad user email**." +#: ../system/integrations/cti/generic.rst:22 +#: ../system/integrations/cti/placetel.rst:27 +#: ../system/integrations/cti/sipgate.rst:30 +msgid "Available Settings" msgstr "" -#: ../system/integrations/zabbix.rst:44 -msgid "" -"**zammad\\_enable\\_tags** to **true** or **false** to enable or disable " -"trigger tags. **Important**: if you enable tag support, each tag is set with " -"a separate request." +#: ../system/integrations/cti/generic.rst:29 +#: ../system/integrations/cti/placetel.rst:41 +#: ../system/integrations/cti/sipgate.rst:40 +msgid "Endpoint Settings" msgstr "" -#: ../system/integrations/zabbix.rst:48 +#: ../system/integrations/cti/generic.rst:25 msgid "" -"If you want to prioritize issues according to **severity** values in Zabbix, " -"you can define mapping parameters:" -msgstr "" - -#: ../system/integrations/zabbix.rst:51 -msgid "**severity\\_**: Zammad priority ID" -msgstr "" - -#: ../system/integrations/zabbix.rst:53 -msgid "Click the **Update** button to save the **Webhook** settings." +"Zammad will list your generic CTI endpoint here. It contains a unique token " +"so ensure to keep this URL save." msgstr "" -#: ../system/integrations/zabbix.rst:55 +#: ../system/integrations/cti/generic.rst:28 msgid "" -"To receive notifications in **Zammad**, you need to create a **Zabbix user** " -"and add **Media** with the **Zammad** type." +"You'll need this endpoint for your PBX to talk to Zammad, see :docs:`CTI-API " +"documentation `." msgstr "" -#: ../system/integrations/zabbix.rst:58 +#: ../system/integrations/cti/includes/important-dont-forget-saving.include.rst:3 msgid "" -"For **Send to**: enter any text, as this value is not used, but is required." +"All following options **do not save automatically**. Always use the Save " +"button on the lower end of the integration page!" msgstr "" -#: ../system/integrations/zabbix.rst:61 -msgid "" -"For more information, use the `Zabbix documentation `_." +#: ../system/integrations/cti/generic.rst:43 +#: ../system/integrations/cti/placetel.rst:49 +#: ../system/integrations/cti/sipgate.rst:52 +msgid "Call Settings" msgstr "" -#: ../system/maintenance.rst:2 -msgid "Maintenance" +#: ../system/integrations/cti/generic.rst:39 +#: ../system/integrations/cti/placetel.rst:49 +#: ../system/integrations/cti/sipgate.rst:37 +#: ../system/integrations/cti/sipgate.rst:50 +msgid "Inbound" msgstr "" -#: ../system/maintenance.rst:4 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:1 msgid "" -"Zammad comes with a maintenance mode that you can use for e.g. updating the " -"instance or changing settings while restricting availability and functions." +"This option allows you to block specific incoming caller IDs. It allows you " +"to temporarily reject e.g. spam callers without having to contact providers " +"or PBX administrators." msgstr "" -#: ../system/maintenance.rst:13 -msgid "Mode" +#: ../system/integrations/cti/includes/inbound-calls.include.rst:11 +msgid "Caller ID to block" msgstr "" -#: ../system/maintenance.rst:8 -msgid "The mode setting allows you to enable or disable the maintenance mode." +#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 +msgid "Provide caller IDs to block in ``E.164`` format." msgstr "" -#: ../system/maintenance.rst:10 -msgid "Defaults to *off*." +#: ../system/integrations/cti/includes/inbound-calls.include.rst:8 +msgid "" +"Your telephony system has to support this function. Zammad will send a " +"``reject`` response which will cause your telephony system to hang up the " +"call. To callers this usually will feel like the line is busy." msgstr "" -#: ../system/maintenance.rst:12 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:14 msgid "" -"The maintenance mode will restrict access to administrative roles only. This " -"means agents and customers are logged off." -msgstr "" - -#: ../system/maintenance.rst:23 -msgid "@Login" -msgstr "" - -#: ../system/maintenance.rst:16 -msgid "" -"This setting allows you to provide a login message within a green banner " -"above the login screen. Click into the green banner in the settings page to " -"adjust your message. To activate the message, activate the *@Login* setting." -msgstr "" - -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing the default login message within the\n" -"settings page" -msgstr "" - -#: ../system/maintenance.rst:26 -msgid "" -"Send an informative message to **all active sessions**. This comes handy to " -"inform your agents e.g. about mayor outages or to force reloads after " -"configuration changes." -msgstr "" - -#: ../system/maintenance.rst:31 -msgid "This is the messages title (slightly bigger than the normal message)." -msgstr "" - -#: ../system/maintenance.rst:34 -msgid "The text you want to provide to your logged in sessions." -msgstr "" - -#: ../system/maintenance.rst:39 -msgid "Reload application" -msgstr "" - -#: ../system/maintenance.rst:37 -msgid "" -"Selecting this option will change the message acceptance button from *Close* " -"(with nothing happening) to *Continue session*, which forces the application " -"to reload." -msgstr "" - -#: ../system/maintenance.rst:43 -msgid "" -"If you have customers that are logged in to Zammad, they'll also be notified " -"if they're active in that moment." -msgstr "" - -#: ../system/maintenance.rst:48 -msgid "Example without reload application" +"Provide a meaningful note for your fellow administrators to remind yourself " +"why you've chosen to block the number." msgstr "" -#: ../system/maintenance.rst:52 -msgid "" -"Message setting within Zammad's admin settings without ticket reload " -"application setting." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:17 +#: ../system/integrations/cti/sipgate.rst:40 +msgid "Outbound" msgstr "" -#: ../system/maintenance.rst:0 +#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:1 msgid "" -"Screenshot showing the send message settings without ticket\n" -"reload application set" +"In many cases you may want to use a different caller ID depending on the " +"destination you're calling. This may apply due to specific connection rates " +"to other countries or because you want your customer to feel you're calling " +"from the same country." msgstr "" -#: ../system/maintenance.rst:61 ../system/maintenance.rst:85 -msgid "" -"The modal all other active sessions will see upon pressing *Send to clients*." +#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:6 +msgid "This option expects ``E.164`` number formats." msgstr "" -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing modal caused by maintenance's message\n" -"without reload application ticket" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 +msgid "Destination caller ID" msgstr "" -#: ../system/maintenance.rst:72 -msgid "Example with reload application" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:5 +msgid "The caller ID or number you're trying to call." msgstr "" -#: ../system/maintenance.rst:76 -msgid "" -"Message setting within Zammad's admin settings with ticket reload " -"application setting." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:7 +msgid "You can use wildcards for e.g. country specific outbound numbers like:" msgstr "" -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing the send message settings with ticket\n" -"reload application set" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:9 +msgid "``49*`` for Germany" msgstr "" -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing modal caused by maintenance's message\n" -"with reload application ticket" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:10 +msgid "``4930*`` for Berlin / Germany landlines" msgstr "" -#: ../system/monitoring.rst:2 -msgid "Monitoring" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 +msgid "``33*`` for France" msgstr "" -#: ../system/monitoring.rst:4 -msgid "" -"This function is only available in self hosted instances. If you use Zammad " -"in our cloud, we are monitoring the system on our own and take steps to fix " -"potential problems directly." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:15 +msgid "Set Outbound caller ID" msgstr "" -#: ../system/monitoring.rst:11 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:14 msgid "" -"On the monitoring page, you can see the current health state of Zammad under " -"\"*Current Status*\" at the bottom. This can be useful if you want to have a " -"look if everything is up and running. As an example, you could have a look " -"in the monitoring when you assume that some emails aren't processed from " -"Zammad." +"The outbound caller ID to set (the number your customer sees on his display) " +"in ``E.164`` number format." msgstr "" -#: ../system/monitoring.rst:17 -msgid "**Can't receive an email and the monitoring response is \"healthy\"?**" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 +msgid "Provide a short description for fellow administrators." msgstr "" -#: ../system/monitoring.rst:19 +#: ../system/integrations/cti/includes/generic-cti-support-note.includes.rst:3 msgid "" -"Zammad will just inform you about unprocessable emails. This is not the case " -"for oversized emails. You can adjust the maximum email size in :doc:`../" -"channels/email/settings`." +"This option requires your PBX to send a specific request to Zammad *before " +"dialing*. Please consult the :docs:`CTI API ` in case " +"you're not sure." msgstr "" -#: ../system/monitoring.rst:24 -msgid "Monitoring API" +#: ../system/integrations/cti/generic.rst:52 +#: ../system/integrations/cti/placetel.rst:54 +#: ../system/integrations/cti/sipgate.rst:59 +msgid "Other Settings" msgstr "" -#: ../system/monitoring.rst:26 +#: ../system/integrations/cti/includes/other-settings-intro.include.rst:1 msgid "" -"Beside the indication in the monitoring page, you can also use an external " -"monitoring tool to monitor Zammad's health. To request the health of Zammad, " -"you need to provide the API key (token) to the external monitoring tool. You " -"can copy the token from the \"*Current Token*\" field as well as the whole " -"API endpoint of your system (\"*Health Check*\" field), in which the API " -"token is already included." +"Below you can find all available additional settings for this CTI " +"integration. For your overview we're sorting them by appearance and " +"reference their description first." msgstr "" -#: ../system/monitoring.rst:37 -msgid "Screenshot showing Current Token and Health Check" +#: ../system/integrations/cti/includes/default-caller-id.include.rst:2 +#: ../system/integrations/cti/includes/default-caller-id.include.rst:1 +msgid "Default caller ID for outbound calls" msgstr "" -#: ../system/monitoring.rst:37 -msgid "Screenshot showing Token and Health Check" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:16 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:15 +msgid "Shown records in caller log" msgstr "" -#: ../system/monitoring.rst:39 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:2 msgid "" -"In addition to that, you can reset the auto-generated token to make sure " -"that already configured monitoring systems won't work anymore. So, please " -"use this \"*Reset*\" button only if you know what you do!" -msgstr "" - -#: ../system/monitoring.rst:44 -msgid "Example Output" -msgstr "" - -#: ../system/monitoring.rst:0 -msgid "No issues found" -msgstr "" - -#: ../system/monitoring.rst:48 ../system/monitoring.rst:60 -msgid "**Indicator in Zammad**:" -msgstr "" - -#: ../system/monitoring.rst:0 -msgid "Screenshot showing monitoring with no issues" -msgstr "" - -#: ../system/monitoring.rst:54 ../system/monitoring.rst:66 -msgid "**API response**::" -msgstr "" - -#: ../system/monitoring.rst:0 -msgid "Issues were found" -msgstr "" - -#: ../system/monitoring.rst:0 -msgid "Screenshot showing monitoring with issues" -msgstr "" - -#: ../system/objects.rst:2 -msgid "Objects" +"Allows you to set the number of shown caller log entries for all users. You " +"can choose from the following values:" msgstr "" -#: ../system/objects.rst:4 -msgid "" -"In Zammad you can add your own fields to tickets, users, organizations and " -"even groups (these are called \"objects\"). This can be useful if you need " -"to add further information to a ticket or any other object in Zammad and the " -"information doesn't fit in any existing field." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:5 +msgid "60 (default)" msgstr "" -#: ../system/objects.rst:11 -msgid "" -"Try to avoid deleting attributes (and disable them instead) as Zammad might " -"run into unexpected conditions if they are referenced somewhere." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:6 +msgid "120" msgstr "" -#: ../system/objects.rst:16 -msgid "" -"Here's an overview of object attributes. On the upper right you can add new " -"attributes. By default, there will be no custom fields - standard attributes " -"will be grayed out, you can't delete or change those. You can edit custom " -"attributes (they are displayed in black font and have a trash bin on the " -"right side) just by clicking on them." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:7 +msgid "180" msgstr "" -#: ../system/objects.rst:24 -msgid "" -"Attributes you add to Zammad, no matter if they have default values or not, " -"will not update existing information. This means a new ticket field " -"technically will be empty unless you populate it." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:8 +msgid "240" msgstr "" -#: ../system/objects.rst:28 -msgid "" -"Especially in ticket scope this also means that newly added attributes will " -"be indicated as \"changed\" to agents that view the ticket. This may " -"interfere with Zammad's tabs behavior." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:9 +msgid "300" msgstr "" -#: ../system/objects.rst:40 -msgid "Ordering Attributes" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:11 +msgid "**🥵 Potential performance issue**" msgstr "" -#: ../system/objects.rst:42 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:13 msgid "" -"Since Zammad introduced :doc:`/system/core-workflows` the need to have a " -"custom positioning for attributes has become more important than ever." +"Setting this setting higher than 60 may cause serious performance issues on " +"very busy instances. Keep in mind that this setting causes Zammad to poll " +"and send up to 300 records to *all active agent sessions* in very short time " +"periods." msgstr "" -#: ../system/objects.rst:45 -msgid "" -"To adjust the position of such an attribute, simply click on the attribute " -"entry in question, scroll down and adjust the position number. Please note " -"that you cannot change the positioning of default attributes." +#: ../system/integrations/cti/generic.rst:73 +msgid "Caller Log Filter" msgstr "" -#: ../system/objects.rst:49 +#: ../system/integrations/cti/generic.rst:55 msgid "" -"In case two attributes have the same position value, Zammad will sort " -"alphabetically by name automatically." +"This function allows you to provide call information based on e.g. queues " +"only to agents that really need the information." msgstr "" -#: ../system/objects.rst:None +#: ../system/integrations/cti/generic.rst:58 msgid "" -"Screenshot showing custom attribute entries ordered in between default ones" +"Why? If you have a team for several countries or departments, you don't want " +"to bug your agents from other departments. Leaving these options empty will " +"fallback to showing everything to everyone." msgstr "" -#: ../system/objects.rst:56 -msgid "Updating Database After Adding or Editing Attributes" +#: ../system/integrations/cti/generic.rst:64 +msgid "Destination caller ID or Queue" msgstr "" -#: ../system/objects.rst:58 +#: ../system/integrations/cti/generic.rst:63 msgid "" -"When adding or changing attributes, Zammad will not apply the changes " -"instantly, but instead shows you the changed attributes first. If you're " -"ready to go, just click on \"Update database\" to apply the changes to " -"Zammad. If you made a mistake or just want to discard your changes, click " -"\"Discard changes\"." +"This depends on your PBX and usually is either a queue ID, phone number or " +"extension." msgstr "" -#: ../system/objects.rst:64 -msgid "" -"After applying the changes with \"Update Database\", a restart of Zammad is " -"**mandatory**. If you don't perform it, you may experience unexpected " -"behavior or even errors. You may want to do this kind of configuration " -"during maintenance windows." +#: ../system/integrations/cti/generic.rst:69 +msgid "Agents" msgstr "" -#: ../system/objects.rst:72 +#: ../system/integrations/cti/generic.rst:67 msgid "" -"Changes on objects require you to update the database to apply these changes." +"Select the agents that are responsible for the group. These agents will then " +"see caller log entries and call notifications fitting to said queue." msgstr "" -#: ../system/objects.rst:75 -msgid "**🤓 Service restarts can be automated**" +#: ../system/integrations/cti/generic.rst:0 +msgid "" +"Screenshot showing the caller log filter table with pre filled sample data" msgstr "" -#: ../system/objects.rst:0 -msgid "Hosted environments automatically restart for you." +#: ../system/integrations/cti/includes/recent-logs.include.rst:6 +msgid "" +"With recent logs Zammad allows you to view the latest calls for the CTI " +"functionality. This usually comes in handy, when you're looking for errors." msgstr "" -#: ../system/objects.rst:0 +#: ../system/integrations/cti/includes/recent-logs.include.rst:0 msgid "" -"If you're using a self-hosted installation you can use :docs:`environment " -"variables `" +"Screenshot showing several incoming requests within Recent logs section." msgstr "" -#: ../system/objects.rst:82 -msgid "System Attributes" +#: ../system/integrations/cti/includes/recent-logs.include.rst:16 +msgid "I'm just here to clear floats up." msgstr "" -#: ../system/objects.rst:84 +#: ../system/integrations/cti/includes/recent-logs.include.rst:20 msgid "" -"Zammad comes with pre-configured attributes. Some of them can't be edited " -"via UI (or at all). This is required for proper operation of Zammad and not " -"a bug." -msgstr "" - -#: ../system/objects.rst:90 -msgid "Ticket State" +"By clicking on the entry of interest, Zammad will provide more details on " +"the call in question. You'll see the payload it received and also the " +"response that was sent." msgstr "" -#: ../system/objects.rst:92 +#: ../system/integrations/cti/includes/recent-logs.include.rst:0 msgid "" -"If the pre-configured states aren't enough for you or you want to change " -"them, you can do so by clicking on the cogwheel icon in the state row in the " -"ticket tab. But you should be careful when changing pre-configured states. " -"This can lead to unwanted behavior in some cases." +"Screenshot showing detailed information of a specific log entry of recent " +"logs" msgstr "" -#: ../system/objects.rst:None -msgid "Screenshot showing highlighted ticket state attribute" +#: ../system/integrations/cti/includes/recent-logs.include.rst:31 +msgid "x" msgstr "" -#: ../system/objects.rst:122 -msgid "Handling of states" +#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 +#: ../system/integrations/cti/includes/troubleshooting.include.rst:9 +msgid "My Phone page stays blank, signalling does work..." msgstr "" -#: ../system/objects.rst:102 +#: ../system/integrations/cti/includes/troubleshooting.include.rst:5 msgid "" -"In the state configuration screen, you can add new states, disable states or " -"change states." +"If you've made sure that signalling works (check Recent logs) and your " +"Caller Log still stays empty, please ensure that you only configured one CTI " +"integration version. Specifically defining more than one agent mapping on " +"the different integration variants will be the issue." msgstr "" -#: ../system/objects.rst:0 -msgid "Screenshot showing table of default ticket states" +#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 +msgid "Clear the not needed agent mapping and reload your browser page." msgstr "" -#: ../system/objects.rst:110 +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:1 msgid "" -"To add a new state, click on the \"New Ticket State\" button in the top " -"right corner. To change an existing state, simply click on the affected " -"state. This opens an edit dialog." +"By mapping your agents extension to their existing Zammad users, Zammad can " +"provide a new ticket dialog or open the user profile for the agent that " +"picks up the call." msgstr "" -#: ../system/objects.rst:114 +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:5 msgid "" -"You can also clone a state or set them to \"Default for new tickets\" or " -"\"Default for follow-ups\" by clicking on the ⁝ action button and select the " -"desired function." +"This speeds up ticket aiding, no matter if it's for existing tickets or new " +"ones!" msgstr "" -#: ../system/objects.rst:118 +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:8 msgid "" -"*Default for new tickets* means that this state is used for every newly " -"created ticket." +"To see it work from the agent's perspective, have a look on :user-docs:`user " +"documentation `." msgstr "" -#: ../system/objects.rst:121 -msgid "" -"*Default for follow-ups* means that this state is used if the ticket is re-" -"opened after it was closed." +#: ../system/integrations/cti/placetel.rst:2 +msgid "Placetel CTI" msgstr "" -#: ../system/objects.rst:171 -msgid "Ticket state in detail" +#: ../system/integrations/cti/placetel.rst:16 +msgid "You need an administrative Placetel account for your organization." msgstr "" -#: ../system/objects.rst:125 +#: ../system/integrations/cti/placetel.rst:17 +#: ../system/integrations/cti/sipgate.rst:20 msgid "" -"Below you can find a description for each field and option. Please head over " -"to the :ref:`example ` to see the edit dialog." +"Your Zammad instance must be allowed to communicate to external services." msgstr "" -#: ../system/objects.rst:129 -msgid "" -"This is the name of the state and what you and your agents are seeing when " -"choosing a state somewhere (e.g. in tickets, trigger configuration)." +#: ../system/integrations/cti/placetel.rst:18 +msgid "Placetel must be able to reach your Zammad instance." msgstr "" -#: ../system/objects.rst:137 -msgid "" -"There are different state types you can choose from. By default, Zammad " -"comes with one state per state type." +#: ../system/integrations/cti/placetel.rst:22 +msgid ":doc:`provider-configurations/placetel`" msgstr "" -#: ../system/objects.rst:140 +#: ../system/integrations/cti/placetel.rst:21 msgid "" -"**new**: for states for tickets that are new and it hasn't been worked on " -"them" +"Learn how to configure Placetel to enable Zammad and Placetel to communicate " +"with each other." msgstr "" -#: ../system/objects.rst:142 +#: ../system/integrations/cti/placetel.rst:32 msgid "" -"**open**: for states for tickets that are in progress and agents are working " -"on them" -msgstr "" - -#: ../system/objects.rst:144 -msgid "**merged**: for states for tickets that are merged with other tickets" +"The here listed endpoint settings are relevant for the :doc:`integration " +"configuration with Placetel `." msgstr "" -#: ../system/objects.rst:145 -msgid "" -"**pending reminder**: for states for tickets that are in progress and you " -"want to set a reminder. (default example: *pending reminder*)" +#: ../system/integrations/cti/placetel.rst:37 +#: ../system/integrations/i-doit.rst:53 +msgid "Endpoint" msgstr "" -#: ../system/objects.rst:147 +#: ../system/integrations/cti/placetel.rst:36 msgid "" -"**pending action**: for states for tickets that are waiting for a specified " -"time and then change their state (default example: *pending close*)" +"This endpoint will be required for the Zammad integration within the " +"Placetel web interface." msgstr "" -#: ../system/objects.rst:150 -msgid "" -"**closed**: for states for tickets that are finished and do not need to be " -"processed further" +#: ../system/integrations/cti/placetel.rst:41 +msgid "API Token" msgstr "" -#: ../system/objects.rst:153 +#: ../system/integrations/cti/placetel.rst:40 msgid "" -"⚠️ Choosing the correct state type is important! If you are in doubt, have a " -"look on the default states and their types!" +"You'll receive this token within the ``Web API`` menu. Make sure to copy " +"this value, it's only shown once!" msgstr "" -#: ../system/objects.rst:158 -msgid "Ignore escalation" +#: ../system/integrations/cti/placetel.rst:71 +#: ../system/integrations/cti/sipgate.rst:77 +msgid "Phone Extension to Agent Mapping" msgstr "" -#: ../system/objects.rst:157 -msgid "" -"Here you can define whether tickets of this state will count to escalation " -"time or not." +#: ../system/integrations/cti/placetel.rst:0 +msgid "Screenshot showing sample user mappings in between Placetel and Zammad" msgstr "" -#: ../system/objects.rst:161 +#: ../system/integrations/cti/placetel.rst:64 msgid "" -"You can create a note for the state to inform other admins about the state. " -"This has no effect on tickets." +"You can find your agents Placetel username combination required within ⚙️ PBX " +"→ VoIP destinations. Within the \"Advanced settings\" section you're looking " +"for \"SIP user name\" and \"SIP server\"." msgstr "" -#: ../system/objects.rst:165 -msgid "Set the state to *active* or *inactive*." +#: ../system/integrations/cti/placetel.rst:68 +msgid "Combine these two like so: ``@``." msgstr "" -#: ../system/objects.rst:167 -msgid "" -"it is technically possible to set all states to inactive. To keep Zammad " -"working in such a case, the inactive flag of one of the states is ignored." +#: ../system/integrations/cti/placetel.rst:0 +msgid "Sample VoIP credentials for a Placetel user" msgstr "" -#: ../system/objects.rst:194 -msgid "Ticket state example" +#: ../system/integrations/cti/provider-configurations/placetel.rst:2 +msgid "Setup Placetel connection for Zammad" msgstr "" -#: ../system/objects.rst:174 +#: ../system/integrations/cti/provider-configurations/placetel.rst:6 msgid "" -"Let's assume we want to create a new state which indicates that the ticket " -"has to wait for a response of a third party (e.g. service contractor or " -"manufacturer) and we want to to be able to set a reminder." +"This configuration step requires a *full* administrative Placetel account. " +"You may receive forbidden error messages with Placetel in case your " +"permissions are not high enough." msgstr "" -#: ../system/objects.rst:178 +#: ../system/integrations/cti/provider-configurations/placetel.rst:10 msgid "" -"First we give the new state a proper name. In this example we call it " -"\"waiting for manufacturer\"." +"The following actions can be configured via the `Placetel web interface " +"`_." msgstr "" -#: ../system/objects.rst:181 -msgid "" -"As state type we choose \"pending reminder\". This indicates that the ticket " -"is still open and we can set a reminder. This reminder can be useful if our " -"manufacturer sometimes isn't responding or we want to remind him to give us " -"an answer." +#: ../system/integrations/cti/provider-configurations/placetel.rst:29 +msgid "Step 1: Activate Zammad integration" msgstr "" -#: ../system/objects.rst:186 +#: ../system/integrations/cti/provider-configurations/placetel.rst:14 msgid "" -"We choose \"no\" for \"ignore escalation\" because we want to escalate the " -"tickets even if we are waiting on the manufacturer's feedback." -msgstr "" - -#: ../system/objects.rst:189 -msgid "The **result** in the creation dialog will look like this:" +"Within Integrations, scroll down to Partner integrations and select Zammad." msgstr "" -#: ../system/objects.rst:0 -msgid "Screenshot showing ticket state creation dialog with example" +#: ../system/integrations/cti/provider-configurations/placetel.rst:17 +msgid "" +"You can alternatively filter by \"Ticket Systems\" to reduce the number of " +"entries on the page. You'll still want to look for Partner integrations. 🤓" msgstr "" -#: ../system/objects.rst:197 ../system/objects.rst:199 -msgid "Ticket Priority" +#: ../system/integrations/cti/provider-configurations/placetel.rst:21 +msgid "" +"Within the Zammad integration now press \"Activate\". A new tab ``API`` " +"becomes available - open this tab." msgstr "" -#: ../system/objects.rst:199 ../system/objects.rst:201 +#: ../system/integrations/cti/provider-configurations/placetel.rst:24 msgid "" -"If the pre-configured priorities aren't enough for you or you want to change " -"them, you can do so by clicking on the cogwheel icon in the priority row in " -"the ticket tab:" +"Now tick \"Enable Call Control / Notify API\" and paste the Placetel " +"endpoint from your Zammad instance into the field \"URL of your API " +"endpoint\". Save to apply the settings" msgstr "" -#: ../system/objects.rst:None -msgid "Screenshot showing highlighted ticket priority attribute" +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "Screencast showing how to activate the Zammad integration" msgstr "" -#: ../system/objects.rst:224 ../system/objects.rst:226 -msgid "Handling of priorities" +#: ../system/integrations/cti/provider-configurations/placetel.rst:51 +msgid "Step 2: Generate API Token for Placetel" msgstr "" -#: ../system/objects.rst:208 ../system/objects.rst:210 +#: ../system/integrations/cti/provider-configurations/placetel.rst:32 msgid "" -"In the priority configuration screen, you can add new priorities, disable " -"priorities or change priorities." +"Go back to the integrations page and scroll down to \"Web API\". Generate a " +"new API token by using the \"Create a new API token\" button." msgstr "" -#: ../system/objects.rst:0 -msgid "Screenshot showing table of default ticket priorities" +#: ../system/integrations/cti/provider-configurations/placetel.rst:37 +msgid "" +"If you already generated a token either use your existing token or reset it " +"by using above mentioned button. Placetel will ask you to conform this reset." msgstr "" -#: ../system/objects.rst:216 ../system/objects.rst:218 +#: ../system/integrations/cti/provider-configurations/placetel.rst:41 msgid "" -"To add a new priority, click on the \"New Priority\" button in the top right " -"corner. To change an existing priority, simply click on the affected " -"priority. This opens an edit dialog." +"Please keep in mind that existing API scripts may no longer work due to " +"token resets!" msgstr "" -#: ../system/objects.rst:220 ../system/objects.rst:222 +#: ../system/integrations/cti/provider-configurations/placetel.rst:44 msgid "" -"You can also clone a priority or set them to \"Default for new tickets\" by " -"clicking on the ⁝ action button and select the desired function." +"Copy the provided API token and insert it into the \"API Token\" field " +"within Zammad's Placetel integration." msgstr "" -#: ../system/objects.rst:223 ../system/objects.rst:225 +#: ../system/integrations/cti/provider-configurations/placetel.rst:47 msgid "" -"*Default for new tickets* means that this priority is used for every newly " -"created ticket." +"Apply your changes by using the \"Save\" button on the bottom of the " +"Placetel integration page and activate the Placetel integration." msgstr "" -#: ../system/objects.rst:246 ../system/objects.rst:248 -msgid "Priorities in detail" +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "" +"Screencast showing how to retrieve an API token from Placetel for Zammad" msgstr "" -#: ../system/objects.rst:227 ../system/objects.rst:229 -msgid "Below you can find a description for each field and option." +#: ../system/integrations/cti/provider-configurations/placetel.rst:73 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:77 +msgid "Step 3: Restrict the numbers to notify on" msgstr "" -#: ../system/objects.rst:230 ../system/objects.rst:232 +#: ../system/integrations/cti/provider-configurations/placetel.rst:54 msgid "" -"This is the name of the priority and what you and your agents are seeing " -"when choosing a priority somewhere (e.g. in tickets, trigger configuration)." +"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " +"the the Integrations page of the Placetel web interface, go to \"Notify " +"API\"." msgstr "" -#: ../system/objects.rst:240 ../system/objects.rst:242 -msgid "Highlight color" +#: ../system/integrations/cti/provider-configurations/placetel.rst:58 +msgid "" +"Lower on the page Placetel allows you to restrict the numbers to notify on. " +"You'll find this within the \"External routing API\" part." msgstr "" -#: ../system/objects.rst:235 ../system/objects.rst:237 +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 msgid "" -"Switch between *Low priority* (light blue), *High priority* (red) and - " -"(default). This affects the displayed color for ticket titles in overviews." +"Screenshot showing a sample selection of phone numbers to use for the " +"Placetels notify API" msgstr "" -#: ../system/objects.rst:239 ../system/objects.rst:241 -msgid "The color options are currently limited to the mentioned options." +#: ../system/integrations/cti/provider-configurations/placetel.rst:66 +msgid "" +"This menu point also provides a API request log from Placetel view. Just " +"open \"Recent responses of your API endpoint\" to learn more." msgstr "" -#: ../system/objects.rst:243 ../system/objects.rst:245 +#: ../system/integrations/cti/provider-configurations/placetel.rst:69 msgid "" -"You can create a note for the priority to inform other admins about the " -"priority. This has no effect on tickets." +"If you want to see Zammad's perspective, use the \"Recent Logs\" part from " +"within the Placetel integration page." msgstr "" -#: ../system/objects.rst:247 ../system/objects.rst:249 -msgid "Set the priority to *active* or *inactive*." +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "Screenshot showing sample log entries for Placetels API calls to Zammad" msgstr "" -#: ../system/objects/external-data-source-example.rst:2 -msgid "External Data Source" +#: ../system/integrations/cti/provider-configurations/placetel.rst:77 +msgid "Step 4 (optional): Further configurations for Placetel" msgstr "" -#: ../system/objects/external-data-source-example.rst:4 +#: ../system/integrations/cti/provider-configurations/placetel.rst:76 msgid "" -"We assume you already had a look on :doc:`types` where you can find a " -"description of the individual fields." +"If needed, you can now configure Zammad's Placetel integration in more " +"detail. You can learn more about your options here: :ref:`Placetel " +"integration settings `." msgstr "" -#: ../system/objects/external-data-source-example.rst:7 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:2 +msgid "Setup Sipgate connection for Zammad" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"To reproduce this example, choose a category you want to add a custom field, " -"click on *New Attribute* and select *External data source field* under " -"*Format*." +"Sipgate has no english web interface which is why this documentation page is " +"mixing up languages badly." msgstr "" -#: ../system/objects/external-data-source-example.rst:11 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"Our example story is to fetch data from an external product database. We " -"want to add our products to the tickets so that the products can be searched " -"and chosen from a list and also create a link to the product website." +"Please also note that the availability of API addons highly depends on your " +"package trier. Usage of sipgate.io packages *is not free*, please check " +"their `pricing page `_ before!" msgstr "" -#: ../system/objects/external-data-source-example.rst:16 -msgid "Base configuration" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:35 +msgid "Step 1: Book sipgate.io package" msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Initial steps to configure external data source object type" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:13 +msgid "Skip to step 2 if you already have the package booked!" msgstr "" -#: ../system/objects/external-data-source-example.rst:23 -#: ../system/variables.rst:85 -msgid "**Example:**" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:15 +msgid "" +"Login to an administrative Sipgate account and navigate to " +"``Accountverwaltung``. You'll see several different options depending on " +"your booked packages. Select ``Verträge & Produkte`` to continue." msgstr "" -#: ../system/objects/external-data-source-example.rst:25 -msgid "Name: *product*" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:19 +msgid "" +"Scroll down to the section ``Zusätzliche Produkte buchen`` and look for " +"``sipgate.io`` - select this product by using the ``Produkte anzeigen``-" +"Button." msgstr "" -#: ../system/objects/external-data-source-example.rst:26 -msgid "Display: *Product*" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:23 +msgid "" +"On the next page select either one of the ``sipgate.io`` packages or ``Push-" +"API Package Free``. Follow the dialogue by booking the addon. You'll be " +"returned to your contract overview and now should see the selected addon in " +"your list." msgstr "" -#: ../system/objects/external-data-source-example.rst:29 -msgid "External data source configuration" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:30 +msgid "" +"The availability for ``sipgate.io`` packages and their levels highly depends " +"on the overall account type and product you've booked with Sipgate." msgstr "" -#: ../system/objects/external-data-source-example.rst:31 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"First, enter the search URL making sure it contains ``#{search.term}`` as a " -"parameter:" +"Screencast showing the process on how to book the required sipgate.io addon" msgstr "" -#: ../system/objects/external-data-source-example.rst:34 -msgid "**Example:** ``https://dummyjson.com/products/search?q=#{search.term}``" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:52 +msgid "Step 2: Configure webhook for Zammad" msgstr "" -#: ../system/objects/external-data-source-example.rst:36 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:38 msgid "" -"After that, head down to the preview section and enter a search input for " -"the external data source." +"Within your ``Accountverwaltung`` navicate to your product ``sipgate.io``. " +"In the newly opened tab, switch from \"Clients\" to \"Webhooks\" and paste " +"the endpoint URLs from your Zammad instance like so:" msgstr "" -#: ../system/objects/external-data-source-example.rst:39 -msgid "**Example:** ``mac``" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:42 +msgid "Inbound endpoint to \"Incoming\"" msgstr "" -#: ../system/objects/external-data-source-example.rst:41 -msgid "Then you can find a preview of the response data below:" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:43 +msgid "Outbound endpoint to \"Outgoing\"" msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of JSON response based on search term" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:47 +msgid "" +"Ensure to select at least one call group or phoneline within \"Sources\". " +"Other wise Sipgate will not indicate any incoming or outgoing calls to " +"Zammad." msgstr "" -#: ../system/objects/external-data-source-example.rst:48 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"We recommend using the preview to have a look on the structure. There is a " -"top-level element called ``products``. One level below, you can find the " -"attributes ``id`` and ``title``." +"Screencast showing how to add Zammad's endpoint URLs to sipgate.ios webhook " +"configuration" msgstr "" -#: ../system/objects/external-data-source-example.rst:52 -msgid "**Search result response based on search from example:**" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:55 +msgid "" +"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " +"the Webhooks → URLs section of Sipgate you can select which *sources* " +"Sipgate should notify Zammad about in- and outgoing calls." msgstr "" -#: ../system/objects/external-data-source-example.rst:119 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:59 msgid "" -"To tell the remote system that the desired data is located below the " -"``products`` level, you have to put it in the field *Search result list key*." +"Use either specific phone lines or use the option \"Use for all phonelines " +"and groups\" to notify Zammad about all existing lines of your Sipgate " +"account." msgstr "" -#: ../system/objects/external-data-source-example.rst:122 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"After inserting ``products`` in the mentioned field, you get an extended " -"preview. You can find an additional box *Search result list* with a JSON " -"structure. This is the same response as before but stripped from the upper " -"``products`` element by the external data source." +"Screenshot showing a sample selection of phone numbers to use for the " +"Sipgates webhooks API" msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of JSON response search result list" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:68 +msgid "This section also allows you to enable a Debug log." msgstr "" -#: ../system/objects/external-data-source-example.rst:132 -msgid "" -"Now you need to provide the keys for the search result values and labels. As " -"already mentioned, we are looking for the ``id`` and the ``title`` of our " -"products. If you haven't already, it is now a good time to look at the " -"preview of the *Search result list*." +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "Screenshot showing an enabled Debug log option" msgstr "" -#: ../system/objects/external-data-source-example.rst:197 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:73 msgid "" -"After locating our two keys, we insert them in *search result value key* " -"(``id``) and in *Search result label key* (``title``)." +"After enabling you can use the Debug log section to see all sent webhook " +"calls to Zammad. You'll also can see the response." msgstr "" -#: ../system/objects/external-data-source-example.rst:200 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"Basically, we configured the external data source already and we can see a " -"table in the preview section:" -msgstr "" - -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of product table based on search term" +"Screenshot showing sample log entries for Sipgates webhook calls to Zammad" msgstr "" -#: ../system/objects/external-data-source-example.rst:208 -msgid "" -"According to our example story, now just the *Link template* is missing." +#: ../system/integrations/cti/provider-configurations/sipgate.rst:81 +msgid "Step 4 (optional): Further configurations for Sipgate" msgstr "" -#: ../system/objects/external-data-source-example.rst:210 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:80 msgid "" -"Please note that this is an optional feature. If you don't want to use such " -"links, of course you don't have to configure it." +"If needed, you can now configure Zammad's Sipgate integration in more " +"detail. You can learn more about your options here: :ref:`Sipgate " +"integration settings `." msgstr "" -#: ../system/objects/external-data-source-example.rst:213 -msgid "" -"We can add now an address where additional product information can be found." +#: ../system/integrations/cti/sipgate.rst:2 +msgid "Sipgate (sipgate.io)" msgstr "" -#: ../system/objects/external-data-source-example.rst:215 -msgid "Example: ``https://your_domain.com/q=#{ticket.product}``" +#: ../system/integrations/cti/sipgate.rst:16 +msgid "You need an administrative Sipgate account for your organization." msgstr "" -#: ../system/objects/external-data-source-example.rst:217 -msgid "In the example, the parameter means:" +#: ../system/integrations/cti/sipgate.rst:17 +msgid "" +"Zammad requires a ``sipgate.io`` addon from the feature store (please note " +"that API calls are not free with Sipgate. Rates may apply and differ from " +"account to account)." msgstr "" -#: ../system/objects/external-data-source-example.rst:219 -msgid "``#{}``: \"Frame\" for the insertion of information" +#: ../system/integrations/cti/sipgate.rst:21 +msgid "Sipgate must be able to reach your Zammad instance." msgstr "" -#: ../system/objects/external-data-source-example.rst:220 -msgid "``ticket``: object level, where you create your custom object" +#: ../system/integrations/cti/sipgate.rst:25 +msgid ":doc:`provider-configurations/sipgate`" msgstr "" -#: ../system/objects/external-data-source-example.rst:221 -msgid "``product``: name of the (custom) object" +#: ../system/integrations/cti/sipgate.rst:24 +msgid "" +"Learn how to configure Sipgate to enable Zammad and Sipgate to communicate " +"with each other." msgstr "" -#: ../system/objects/external-data-source-example.rst:223 +#: ../system/integrations/cti/sipgate.rst:33 msgid "" -"After configuring your *Link template*, there will be another column in the " -"preview. Hovering on the icons in the *Link* column will show you where it " -"forwards you." +"Below endpoint settings affect the :doc:`sipgate.io configuration `." msgstr "" -#: ../system/objects/external-data-source-example.rst:232 -msgid "" -"In our example, one of the links looks like: https://your_domain.com/q=6, " -"where the 6 is the product id." +#: ../system/integrations/cti/sipgate.rst:37 +msgid "This endpoint is required for incoming call hooks." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:40 +msgid "This endpoint is required for outgoing call hooks." msgstr "" -#: ../system/objects/external-data-source-example.rst:235 -msgid "You can find more information regarding the URL in :doc:`types`." +#: ../system/integrations/cti/sipgate.rst:0 +msgid "Screenshot showing sample user mappings in between Sipgate and Zammad" msgstr "" -#: ../system/objects/includes/adding-values-hint.include.rst:3 +#: ../system/integrations/cti/sipgate.rst:69 msgid "" -"Adding values can be tricky for first timers, don't forget to press \"➕ " -"Add\" after typing your values. Otherwise you may loose a value." +"You can find your agent's Sipgate username within ``Accountverwaltung → " +"Benutzer``. You're looking for the SIP-ID." msgstr "" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:1 -#: ../system/objects/includes/reposition-values.include.rst:1 -msgid "**↕️ This field type allows the positioning of its values ↔️**" +#: ../system/integrations/cti/sipgate.rst:0 +msgid "Sample VoIP credentials for a Sipgate user" msgstr "" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:3 -msgid "" -"In order to re-arrange the field values, first edit the field. Then you can " -"use ☰ to drag the values in question to the correct position. If you want to " -"change the layer depth, double click on ☰. With it you can cycle through the " -"available layers." +#: ../system/integrations/cti/sipgate.rst:77 +msgid "Users with several devices also have several SIP-IDs." msgstr "" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:8 -msgid "When you're ready, submit your changes to save the object attribute." +#: ../system/integrations/elasticsearch.rst:2 +msgid "Elasticsearch (SaaS)" msgstr "" -#: :0 ../system/objects/types.rst:0 +#: ../system/integrations/elasticsearch.rst:4 msgid "" -"Screencast showing how to re-position values on tree select like\n" -"fields" +"The Elasticsearch integration allows you to create a read-only user to use " +"with your favorite reporting tool (e.g. like Grafana)." msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:3 +#: ../system/integrations/elasticsearch.rst:7 msgid "" -"In order to re-arrange the field values, edit the field and scroll below the " -"values. Make sure to tick the option \"Use custom option sort\"." +"If you want to take full advantage of the Zammad reporting, have a look at " +"our :docs:`Grafana ` " +"setup page as well." msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:8 -msgid "" -"If you do not tick this field, all manual positioning you did above will be " -"lost upon saving! ☠️" +#: ../system/integrations/elasticsearch.rst:11 ../system/subscription.rst:7 +msgid "**🚧 Hosted environment specific 🚧**" msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:11 +#: ../system/integrations/elasticsearch.rst:13 msgid "" -"Now use ☰ to drag the values in question to the correct position. When " -"you're ready, submit your changes to save the object attribute." -msgstr "" - -#: :0 ../system/objects/types.rst:0 -msgid "Screencast showing how to re-position values" +"This integration is only available for Hosted setups. In order to use " +"Elasticsearch you'll need the **Plus** subscription." msgstr "" -#: ../system/objects/includes/url-template-hint.include.rst:3 +#: ../system/integrations/elasticsearch.rst:16 msgid "" -"This field allows using :ref:`URL fields (Link Templates) `." +"Self hosted users have all the control over their self hosted Elasticsearch " +"instances." msgstr "" -#: ../system/objects/permissions.rst:2 -msgid "Attribute Permissions" +#: ../system/integrations/elasticsearch.rst:None +msgid "Elasticsearch integration page on SaaS environments" msgstr "" -#: ../system/objects/permissions.rst:7 +#: ../system/integrations/elasticsearch.rst:27 msgid "" -"In the object attributes configuration you can define if a field is shown " -"and if the input in the field is mandatory, separated by different screens " -"and for different :doc:`roles/permissions `." +"Please note the following limitations of Elasticsearch access on hosted " +"environments:" msgstr "" -#: ../system/objects/permissions.rst:17 -msgid "Screenshot shows object attribute permission table" +#: ../system/integrations/elasticsearch.rst:30 +msgid "access to the Elasticsearch index is read-only access" msgstr "" -#: ../system/objects/permissions.rst:17 -msgid "" -"Some of the possible permissions and screen options for a user object " -"attribute." +#: ../system/integrations/elasticsearch.rst:31 +msgid "currently you're limited to user only" msgstr "" -#: ../system/objects/permissions.rst:19 +#: ../system/integrations/elasticsearch.rst:32 msgid "" -"Based on the object context (ticket, agent, organization, user), the " -"selectable roles (to be precise: the required permissions) and screens " -"differ. Be aware that these settings aren't affecting data creation via " -"other channels than the UI." +"Reporting tools that require to write into the indexes (like Kibana) are not " +"supported" msgstr "" -#: ../system/objects/permissions.rst:24 -msgid "" -"If you want to have further customization possibilities, you should have a " -"look at the :doc:`core workflows `." +#: ../system/integrations/elasticsearch.rst:34 +msgid "IP access restriction is currently not yet supported" msgstr "" -#: ../system/objects/permissions.rst:28 -msgid "Screens" +#: ../system/integrations/elasticsearch.rst:37 +msgid "Activating Elasticsearch Access" msgstr "" -#: ../system/objects/permissions.rst:30 +#: ../system/integrations/elasticsearch.rst:39 msgid "" -"In the table below you can find an overview about the different permissions " -"and the available screens Zammad distinguishes between." -msgstr "" - -#: ../system/objects/permissions.rst:37 -msgid "Screen" +"By default external access to your Elasticsearch index is not active. You " +"can enable the integration at any time if needed." msgstr "" -#: ../system/objects/permissions.rst:38 -msgid "Available for" +#: ../system/integrations/elasticsearch.rst:42 +msgid "" +"Please ensure to note down the password provided - you won't have access to " +"it afterwards." msgstr "" -#: ../system/objects/permissions.rst:40 -msgid "create" +#: ../system/integrations/elasticsearch.rst:None +msgid "Screencast showing activation of Elasticsearch integration" msgstr "" -#: ../system/objects/permissions.rst:41 ../system/objects/permissions.rst:52 -#: ../system/objects/permissions.rst:59 ../system/objects/permissions.rst:73 -msgid "admin.user" +#: ../system/integrations/elasticsearch.rst:51 +msgid "Connection Settings" msgstr "" -#: ../system/objects/permissions.rst:42 ../system/objects/permissions.rst:53 -#: ../system/objects/permissions.rst:60 -msgid "admin.organization" +#: ../system/integrations/elasticsearch.rst:53 +msgid "" +"This section holds the most important general information for accessing your " +"Elasticsearch indexes - such as:" msgstr "" -#: ../system/objects/permissions.rst:43 ../system/objects/permissions.rst:54 -#: ../system/objects/permissions.rst:61 -msgid "admin.group" +#: ../system/integrations/elasticsearch.rst:57 +msgid "A unique subdomain that does not tell your real instance URL." msgstr "" -#: ../system/objects/permissions.rst:44 -msgid "Creation dialog for not yet existing data" +#: ../system/integrations/elasticsearch.rst:61 +msgid "Software" msgstr "" -#: ../system/objects/permissions.rst:45 -msgid "create_middle" +#: ../system/integrations/elasticsearch.rst:60 +msgid "" +"The major version of the search index being used. This is required by some " +"Reporting tools like Grafana." msgstr "" -#: ../system/objects/permissions.rst:46 ../system/objects/permissions.rst:50 -#: ../system/objects/permissions.rst:57 ../system/objects/permissions.rst:66 -#: ../system/objects/permissions.rst:70 -msgid "ticket.customer" +#: ../system/integrations/elasticsearch.rst:64 +msgid "Authentication" msgstr "" -#: ../system/objects/permissions.rst:47 ../system/objects/permissions.rst:51 -#: ../system/objects/permissions.rst:58 ../system/objects/permissions.rst:69 -msgid "ticket.agent" +#: ../system/integrations/elasticsearch.rst:64 +msgid "The authentication type being supported. ``Basic Authentication``" msgstr "" -#: ../system/objects/permissions.rst:48 -msgid "Ticket create dialog (middle section)" +#: ../system/integrations/elasticsearch.rst:67 +msgid "Available Indexes" msgstr "" -#: ../system/objects/permissions.rst:49 -msgid "edit" +#: ../system/integrations/elasticsearch.rst:69 +msgid "" +"Within this section we're displaying the -in our opinion- most important " +"indexes for a Zammad instance." msgstr "" -#: ../system/objects/permissions.rst:55 -msgid "Editing dialog for already existing data" +#: ../system/integrations/elasticsearch.rst:72 +msgid "" +"If you require all indexes or our listing is not good enough for you, point " +"your browser to the URL we're providing and append ``/_aliases?" +"pretty=true``. The result should look like this: ``https://.zammad.com/" +"_aliases?pretty=true``." msgstr "" -#: ../system/objects/permissions.rst:56 -msgid "view" +#: ../system/integrations/elasticsearch.rst:77 +msgid "" +"Your browser will automatically ask for your credentials - you'll then see " +"something like this:" msgstr "" -#: ../system/objects/permissions.rst:62 -msgid "View-only dialog for already existing data" +#: ../system/integrations/elasticsearch.rst:125 +msgid "Credentials" msgstr "" -#: ../system/objects/permissions.rst:64 -msgid "(e.g. user or organization from search)" +#: ../system/integrations/elasticsearch.rst:127 +msgid "" +"Within this section Zammad displays your available users. The password is " +"provided once (upon activation) and cannot be retrieved after that." msgstr "" -#: ../system/objects/permissions.rst:65 -msgid "signup" +#: ../system/integrations/elasticsearch.rst:131 +msgid "" +"If you need to change or reset your Elasticsearch user password, use the " +"\"Reset password\" button in the credentials table. Doing so creates a brand " +"new password for the account in question. This change is immediate, keep in " +"mind that this may affect third party tools connected to your instance." msgstr "" -#: ../system/objects/permissions.rst:67 -msgid "Sign-up screen for new customers" +#: ../system/integrations/exchange.rst:2 +msgid "Exchange" msgstr "" -#: ../system/objects/permissions.rst:68 -msgid "invite_customer" +#: ../system/integrations/exchange.rst:4 +msgid "" +"With Zammad's Exchange integration, you can easily use existing address " +"books without having to update more than one source." msgstr "" -#: ../system/objects/permissions.rst:71 +#: ../system/integrations/exchange.rst:7 msgid "" -"Customer invitation screen (from :doc:`First Steps ` area)" +"However, you should refrain from syncing all addresses, as the results may " +"not be what you expect (Exchange collects huge amounts of addresses). A " +"central address book of your company to sync makes more sense, as you can " +"ensure that Zammad gets only the data you need and want. Apart from this, it " +"is even not possible to sync the Global Address List (GAL) of your Exchange " +"system with Zammad." msgstr "" -#: ../system/objects/permissions.rst:72 -msgid "invite_agent" +#: ../system/integrations/exchange.rst:16 +msgid "" +"**Exchange and LDAP:** The exchange sync can be overruled by Zammad's LDAP " +"integration. If you have the same users in both sources, the LDAP version " +"will always be Zammad's pick." msgstr "" -#: ../system/objects/permissions.rst:74 +#: ../system/integrations/exchange.rst:19 msgid "" -"Agent invitation screen (from :doc:`First Steps ` area)" +"**One way sync:** the Exchange sync is one way. Exchange => Zammad. Changes " +"to your users inside of Zammad might be overwritten by the Exchange sync." msgstr "" -#: ../system/objects/permissions.rst:78 -msgid "Screen Options" +#: ../system/integrations/exchange.rst:24 +msgid "" +"To configure Exchange integration, simply go to the System > Integrations > " +"Exchange in the admin panel. Press \"change\" and follow the wizard for " +"adding the needed Exchange information to Zammad. On the last two steps " +"Zammad will ask you for the address book(s) and your desired attribute " +"mapping. By default, Zammad only maps email address, first- and lastname. " +"Technically, you can map any Exchange object to a Zammad user object (this " +"also works for custom objects!)." msgstr "" -#: ../system/objects/permissions.rst:80 +#: ../system/integrations/exchange.rst:35 msgid "" -"For the different screens you can select \"show\" and \"required\" options." +"If the SSL verification fails while connecting to Exchange, Zammad will ask " +"you to turn it off temporarily." msgstr "" -#: ../system/objects/permissions.rst:82 -msgid "**shown:** Show (check) or hide (uncheck) a field." +#: ../system/integrations/exchange.rst:38 +msgid "" +"Please be aware that **turning off SSL verification is a security risk**. It " +"should only be used temporarily or for testing purposes. If turned off, " +"there is no verification of the certificate, which means that every " +"presented certificate will be accepted." msgstr "" -#: ../system/objects/permissions.rst:83 +#: ../system/integrations/exchange.rst:43 msgid "" -"**required:** Set a field to mandatory (check). Forces users (via UI and " -"API) to populate the field." -msgstr "" - -#: ../system/objects/types.rst:7 -msgid "Example external data source" +"After pressing Continue, Zammad will check if the configuration is okay. You " +"can then enable Exchange and start your first sync. The sync will then run " +"hourly - if you need to change mappings or the address book(s), you can " +"change the configuration at any time." msgstr "" -#: ../system/objects/types.rst:2 -msgid "Attribute types" +#: ../system/integrations/exchange.rst:50 +msgid "" +"After the sync has finished, you can find the new Exchange contacts under " +"\"Users\". Zammad integrates them just as normal users." msgstr "" -#: ../system/objects/types.rst:4 +#: ../system/integrations/exchange.rst:55 msgid "" -"When adding a new object attribute, you can choose between the following " -"attribute types." +"In some cases you might see unique IDs as \"Login\" instead of the email " +"address. This is normal and doesn't affect the login or email mapping for " +"that entry." msgstr "" -#: ../system/objects/types.rst:14 +#: ../system/integrations/github.rst:4 msgid "" -"You cannot change the attribute format / type as soon as it is applied. If " -"you no longer need an object attribute, consider disabling it instead of " -"removing." +"Use GitHub integration to track GitHub issues directly within Zammad " +"tickets. Add issue hyperlinks and get a live summary of metadata like status " +"(open/closed), assignee, labels, and more." msgstr "" -#: ../system/objects/types.rst:18 -msgid "**What about the translation of my attributes?**" +#: ../system/integrations/github.rst:8 +msgid "Please note that our GitHub integration does not support pull requests." msgstr "" -#: ../system/objects/types.rst:20 -msgid "" -"For some attribute types you can decide if they should be translatable or " -"not. To be precise, it works only for the selectable fields because the " -"possible choices are known and limited. For the following attribute types, " -"you can set the translatable flag:" +#: ../system/integrations/github.rst:None +msgid "Integration page for GitHub" msgstr "" -#: ../system/objects/types.rst:25 -msgid "*Boolean field*" +#: ../system/integrations/github.rst:18 +msgid "" +"In your GitHub settings, create a new API token under **Developer settings > " +"Personal access tokens > Generate new token**. Leave the **Scopes** section " +"empty." msgstr "" -#: ../system/objects/types.rst:26 -msgid "*Single selection field*" +#: ../system/integrations/github.rst:0 ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to create a new API token" msgstr "" -#: ../system/objects/types.rst:27 -msgid "*Multiple selection field*" +#: ../system/integrations/github.rst:27 +msgid "Create a new API key with no scopes/privileges." msgstr "" -#: ../system/objects/types.rst:28 -msgid "*Single tree selection field*" +#: ../system/integrations/github.rst:29 +msgid "🔒 **Will this work for private repos?**" msgstr "" -#: ../system/objects/types.rst:29 -msgid "*Multiple tree selection field*" +#: ../system/integrations/github.rst:31 +msgid "" +"No. To link private repo issues, **use the** ``repo`` **scope instead**. " +"Bear in mind that the resulting token will have `lots of permissions that it " +"doesn't actually need `_, which presents a security risk if your token ever falls into " +"the wrong hands." msgstr "" -#: ../system/objects/types.rst:31 +#: ../system/integrations/github.rst:37 msgid "" -"For these types, you can find an additional field *Translate field contents*:" +"Unfortunately, because of how GitHub's OAuth token scopes are set up, this " +"is the only way to link issues on private repos." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Screenshot showing translatable attribute types" +#: ../system/integrations/github.rst:40 +msgid "Enter your new API token in Zammad and enable GitHub integration." msgstr "" -#: ../system/objects/types.rst:38 -msgid "Screenshot with example of translatable attribute type" +#: ../system/integrations/github.rst:0 +msgid "Screencast showing how to configure Zammad's GitHub integration" msgstr "" -#: ../system/objects/types.rst:45 -msgid "Boolean field" +#: ../system/integrations/github.rst:47 +msgid "" +"Use the default API endpoint (``https://api.github.com/graphql``) unless " +"you're using GitHub Enterprise Server." msgstr "" -#: ../system/objects/types.rst:41 +#: ../system/integrations/github.rst:50 msgid "" -"Provides a drop-down field with display values for ``true`` and ``false``. " -"Setting a default is mandatory." +"Once completed, a new GitHub issues tab will appear in the ticket pane. 🎉" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Boolean fields" +#: ../system/integrations/github.rst:59 ../system/integrations/gitlab.rst:52 +msgid "Token verification is taking a long time" msgstr "" -#: ../system/objects/types.rst:55 -msgid "Date field" +#: ../system/integrations/github.rst:56 ../system/integrations/gitlab.rst:49 +msgid "" +"Slight delays are normal (<2 min.), especially for systems under heavy load." msgstr "" -#: ../system/objects/types.rst:48 -msgid "Provides a date picker field and does not allow default values." +#: ../system/integrations/github.rst:58 +msgid "" +"Self-hosted administrators, please check your network settings to ensure " +"that your Zammad server can reach ``api.github.com``." msgstr "" -#: ../system/objects/types.rst:52 -msgid "Default time diff (hours)" +#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 +msgid "I reloaded the page and now the API token is gone" msgstr "" -#: ../system/objects/types.rst:51 +#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 msgid "" -"This setting helps the user by highlighting the day from now plus the " -"provided value. It *does not* pre-fill the field." -msgstr "" - -#: ../system/objects/types.rst:0 -msgid "Available settings for Date fields" +"This may indicate that Zammad is still verifying your API token. Try " +"reloading the page again in a couple minutes." msgstr "" -#: ../system/objects/types.rst:73 -msgid "Date & time field" +#: ../system/integrations/gitlab.rst:2 +msgid "GitLab" msgstr "" -#: ../system/objects/types.rst:58 -msgid "Provides a date and time picker – does not allow default values" +#: ../system/integrations/gitlab.rst:4 +msgid "" +"Use GitLab integration to track GitLab issues directly within Zammad " +"tickets. Add issue hyperlinks and get a live summary of metadata like status " +"(open/closed), assignee, labels, and more." msgstr "" -#: ../system/objects/types.rst:62 -msgid "Allow future" +#: ../system/integrations/gitlab.rst:8 +msgid "" +"Please note that our GitLab integration does not support merge requests." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Forbid dates and times in the future." +#: ../system/integrations/gitlab.rst:None +msgid "Integration page for GitLab" msgstr "" -#: ../system/objects/types.rst:66 -msgid "Allow past" +#: ../system/integrations/gitlab.rst:18 +msgid "" +"In your GitLab preferences, create a new API token under **Access Tokens**." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Forbid dates and times in the past." +#: ../system/integrations/gitlab.rst:20 +msgid "Under **Select scopes**, choose ``read_api`` only." msgstr "" -#: ../system/objects/types.rst:70 -msgid "Default time diff (minutes)" +#: ../system/integrations/gitlab.rst:27 +msgid "🔒 **If you wish to link issues on any private repos...**" msgstr "" -#: ../system/objects/types.rst:69 -msgid "" -"This setting helps the user by highlighting the day from now plus the " -"provided value. It does not pre-fill the field." +#: ../system/integrations/gitlab.rst:29 +msgid "Your API token must belong to an account with access to those repos." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Date & time fields" +#: ../system/integrations/gitlab.rst:31 +msgid "Enter your new API token in Zammad and enable GitLab integration." msgstr "" -#: ../system/objects/types.rst:86 -msgid "Integer field" +#: ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to configure Zammad's GitLab integration" msgstr "" -#: ../system/objects/types.rst:76 +#: ../system/integrations/gitlab.rst:40 msgid "" -"Provides an input field that allows integer usage only. You may define a " -"default value. You cannot enforce comma separation." +"Use the default API endpoint (``https://gitlab.com/api/graphql``) unless " +"you're a self-hosted GitLab user." msgstr "" -#: ../system/objects/types.rst:80 -msgid "Minimal" +#: ../system/integrations/gitlab.rst:43 +msgid "" +"Once completed, a new GitLab issues tab will appear in the ticket pane. 🎉" msgstr "" -#: ../system/objects/types.rst:80 -msgid "The minimal value the field accepts." +#: ../system/integrations/gitlab.rst:51 +msgid "" +"Self-hosted administrators, please check your network settings to ensure " +"that your Zammad server can reach ``gitlab.com``." msgstr "" -#: ../system/objects/types.rst:83 -msgid "Maximal" +#: ../system/integrations/i-doit.rst:2 +msgid "i-doit" msgstr "" -#: ../system/objects/types.rst:83 -msgid "The maximum value the field accepts." +#: ../system/integrations/i-doit.rst:4 +msgid "" +"`i-doit `_ is an open-source **configuration " +"management database** - in other words, a tool for keeping tabs on every " +"single piece of your physical and digital infrastructure, from network " +"equipment to virtual machines on down to the faceplates on your rack shelves " +"and more." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Integer fields" +#: ../system/integrations/i-doit.rst:10 +msgid "" +"What's that got to do with Zammad? Well, if you used tickets to track issues " +"with all that hardware, you might start wishing there was a way they could " +"talk to each other." msgstr "" -#: ../system/objects/types.rst:99 -msgid "Multiple selection field" +#: ../system/integrations/i-doit.rst:14 +msgid "Zammad gives you two:" msgstr "" -#: ../system/objects/types.rst:89 -msgid "" -"Provides a selection field that allows the selection of one or more out of " -"several. This field does allow setting a default value." +#: ../system/integrations/i-doit.rst:17 +msgid "1. Add i-doit Links to Zammad Tickets" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Multiple selection fields" +#: ../system/integrations/i-doit.rst:20 ../system/integrations/i-doit.rst:80 +msgid "What Users See" msgstr "" -#: ../system/objects/types.rst:112 -msgid "Single selection field" +#: ../system/integrations/i-doit.rst:26 +msgid "i-doit integration in Zammad's ticket pane" msgstr "" -#: ../system/objects/types.rst:102 +#: ../system/integrations/i-doit.rst:26 msgid "" -"Provides a drop-down field that allows selection of one value out of " -"several. This field does allow setting a default value." +"The i-doit integration will appear under a new 🖨 tab in the ticket pane." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Single selection fields" +#: ../system/integrations/i-doit.rst:28 +msgid "" +"i-doit integration puts a new tab in Zammad's ticket pane where you can add " +"links to existing i-doit devices for easy reference. (See our :user-docs:" +"`user documentation ` to learn " +"how it works in practice)." msgstr "" -#: ../system/objects/types.rst:142 -msgid "Textarea field" +#: ../system/integrations/i-doit.rst:36 ../system/integrations/i-doit.rst:93 +msgid "How to Set it Up" msgstr "" -#: ../system/objects/types.rst:115 +#: ../system/integrations/i-doit.rst:38 msgid "" -"Provides a text area input field (multiple lines) and thus allows e.g. new " -"lines. You can set a default field value." +"It requires i-doit's `API Add-on `_. Make sure to have it properly set up. Use the following setting:" msgstr "" -#: ../system/objects/types.rst:120 -msgid "" -"Please note that this field *does not* support text formatting or HTML " -"content (rich text)." +#: ../system/integrations/i-doit.rst:42 +msgid "Active: ``Yes``" msgstr "" -#: ../system/objects/types.rst:123 -msgid "**🥵 This field can consume a lot of visual space**" +#: ../system/integrations/i-doit.rst:43 +msgid "Enforce authentication by username and password: ``No``" msgstr "" -#: ../system/objects/types.rst:125 +#: ../system/integrations/i-doit.rst:45 msgid "" -"Depending on where you use this field type, it may use a lot of visual space " -"if you provide a lot of text. This may be an issue to work with." +"To set it up, enable the integration in the Zammad admin panel under " +"**System > Integrations > i-doit**:" msgstr "" -#: ../system/objects/types.rst:130 -msgid "Default" +#: ../system/integrations/i-doit.rst:None +msgid "i-doit settings within the integration pages" msgstr "" -#: ../system/objects/types.rst:129 -msgid "" -"The here provided text will be shown within the text area field or new data " -"sets." +#: ../system/integrations/i-doit.rst:53 +msgid "The root URL of your i-doit installation." msgstr "" -#: ../system/objects/types.rst:134 ../system/objects/types.rst:160 -msgid "Maxlength" +#: ../system/integrations/i-doit.rst:62 +msgid "API token" msgstr "" -#: ../system/objects/types.rst:0 ../system/objects/types.rst:160 -msgid "You can pick the maximum length of the field." +#: ../system/integrations/i-doit.rst:56 +msgid "" +"Found in the i-doit admin panel under **Interfaces / external data > JSON-" +"RPC API > Common Settings**." msgstr "" -#: ../system/objects/types.rst:0 -msgid "The default length of this object is ``500``." +#: ../system/integrations/i-doit.rst:0 +msgid "i-doit administration interface with API configuration" msgstr "" -#: ../system/objects/types.rst:139 -msgid "Rows" +#: ../system/integrations/i-doit.rst:67 +msgid "Client ID" msgstr "" -#: ../system/objects/types.rst:0 -msgid "" -"Change the number of rows to dislay so that you can use only the space you " -"really need." +#: ../system/integrations/i-doit.rst:65 +msgid "A unique name to identify Zammad within i-doit." msgstr "" -#: ../system/objects/types.rst:0 -msgid "The default number of rows is ``4``." +#: ../system/integrations/i-doit.rst:67 +msgid "(Zammad does not require you to enter a value here, but i-doit might!)" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Textarea fields" +#: ../system/integrations/i-doit.rst:70 +msgid "" +"Here you can decide if the certificate of your i-doit system has to be " +"verified or not. In case you are using custom certificates, please have a " +"look at :doc:`how to add them to Zammad `." msgstr "" -#: ../system/objects/types.rst:165 -msgid "Text field" +#: ../system/integrations/i-doit.rst:77 +msgid "2. List / Create Zammad Tickets in i-doit" msgstr "" -#: ../system/objects/types.rst:145 -msgid "Provides a text field (one line) and allows choosing a default value." +#: ../system/integrations/i-doit.rst:None +msgid "Zammad integration in i-doit's device view" msgstr "" -#: ../system/objects/types.rst:148 +#: ../system/integrations/i-doit.rst:86 msgid "" -"Defines the type of the input field. This allows e.g. your browser to ensure " -"that you provide the specific type." +"i-doit's ticket system integration gives you a way to see all the tickets " +"for a given device without ever leaving i-doit. (See our :user-docs:`user " +"documentation ` to learn how it " +"works in practice)." msgstr "" -#: ../system/objects/types.rst:152 -msgid "Currently available:" +#: ../system/integrations/i-doit.rst:95 +msgid "" +"Enable this integration in the i-doit admin panel under **Interfaces / " +"external data > Trouble Ticket System (TTS) > Configuration**:" msgstr "" -#: ../system/objects/types.rst:155 -msgid "Phone" +#: ../system/integrations/i-doit.rst:None +msgid "i-doit administration interface with TTS configuration" msgstr "" -#: ../system/objects/types.rst:156 -msgid "Text" +#: ../system/integrations/i-doit.rst:104 +msgid "TTS-Type" msgstr "" -#: ../system/objects/types.rst:157 -msgid "Url *(URL fields disable link-template availability)*" +#: ../system/integrations/i-doit.rst:104 +msgid "``Zammad``" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Text fields" +#: ../system/integrations/i-doit.rst:115 +msgid "Username / Password" msgstr "" -#: ../system/objects/types.rst:174 -msgid "Single tree selection field" +#: ../system/integrations/i-doit.rst:107 +msgid "Login credentials for a Zammad agent." msgstr "" -#: ../system/objects/types.rst:168 +#: ../system/integrations/i-doit.rst:109 msgid "" -"Provides a select-like field with up to 6 layers of options. Does not allow " -"setting a default value." +"This agent must have **read permission** for all :doc:`groups ` that plan on using the i-doit integration." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Tree Select fields" +#: ../system/integrations/i-doit.rst:113 +msgid "" +"You may even wish to create a dedicated agent account just for this " +"integration (otherwise, if the agent ever changes her password, you will " +"have to remember to update it here)." msgstr "" -#: ../system/objects/types.rst:183 -msgid "Multiple tree selection field" +#: ../system/integrations/i-doit.rst:117 +msgid "URL incl. protocol" msgstr "" -#: ../system/objects/types.rst:177 -msgid "" -"Provides a select-like field with up to 6 layers of options allowing the " -"selection of multiple values. Does not allow setting a default value." +#: ../system/integrations/i-doit.rst:118 +msgid "``https://your.zammad.domain``" msgstr "" -#: ../system/objects/types.rst:302 -msgid "External Data Source field" +#: ../system/integrations/index.rst:2 +msgid "Integrations" msgstr "" -#: ../system/objects/types.rst:186 +#: ../system/integrations/index.rst:4 msgid "" -"Provides a searchable field which fetches data from an external system. This " -"can be useful if you have data outside of Zammad and don't want to maintain " -"both data sources." +"Zammad offers numerous integrations that add rich features to your instance." msgstr "" -#: ../system/objects/types.rst:190 -msgid "The feature works as follows:" +#: ../system/integrations/index.rst:6 +msgid "We're still working on this part of our documentation, stay tight!" msgstr "" -#: ../system/objects/types.rst:192 -msgid "" -"Zammad sends a query with a search string (free text from agent or based on " -"a variable) in a pre-defined format (\"Search URL\") to an external system." +#: ../system/integrations/index.rst:10 +msgid "Integrations for Phone Systems" msgstr "" -#: ../system/objects/types.rst:195 +#: ../system/integrations/index.rst:14 msgid "" -"This external system searches for matches and provides a response as a JSON " -"structure to Zammad." +"Your VoIP provider or telephony system is not listed? Possibly your provider " +"supports Zammad by using the generic CTI - if you're unsure ask your " +"provider." msgstr "" -#: ../system/objects/types.rst:197 +#: ../system/integrations/index.rst:18 msgid "" -"Zammad just looks for the defined list and value keys, reads the content and " -"displays the value to the user. There is no search on Zammad side." +"Provider does not support Zammad? Consider creating a `feature request in " +"the Zammad Community `_." msgstr "" -#: ../system/objects/types.rst:201 -msgid "" -"The usage of a PostgreSQL database for Zammad is required. In any other " -"case, Zammad will hide the external data source type and you are not able to " -"use it. If you want to use this feature, consider to :docs:`migrate your " -"database `." +#: ../system/integrations/index.rst:31 +msgid "Integrations for Authentication and Customers" msgstr "" -#: ../system/objects/types.rst:205 -msgid "Currently, only ``GET`` is supported as request method." +#: ../system/integrations/index.rst:44 +msgid "Integrations for Monitoring Systems" msgstr "" -#: ../system/objects/types.rst:206 -msgid "" -"The data structure must be in JSON format and provide the objects in an " -"array." +#: ../system/integrations/index.rst:46 +msgid "This section currently misses the following integrations:" msgstr "" -#: ../system/objects/types.rst:208 -msgid "" -"The endpoint for the external data source has to support search. On Zammad " -"side, there is no search/logic implemented; however, you can define the " -"output key and value based on the result(s) from the response (which " -"provides already filtered content based on the search)." +#: ../system/integrations/index.rst:48 +msgid "Icinga" msgstr "" -#: ../system/objects/types.rst:212 -msgid "" -"If you receive more results as expected, your external data source search " -"may not work properly or the structure of the URL is not correct. You should " -"get in touch with a responsible person from the external system." +#: ../system/integrations/index.rst:49 +msgid "Monit" msgstr "" -#: ../system/objects/types.rst:217 -msgid "" -"Please have a look :doc:`at our example `, where you can find a possible configuration for a public " -"dummy endpoint." +#: ../system/integrations/index.rst:50 +msgid "Nagios" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for external data source fields" +#: ../system/integrations/index.rst:60 +msgid "Integrations for Issue Trackers" msgstr "" -#: ../system/objects/types.rst:242 -msgid "Search URL" +#: ../system/integrations/index.rst:70 +msgid "Other Integrations" msgstr "" -#: ../system/objects/types.rst:227 +#: ../system/integrations/index.rst:72 msgid "" -"Set your endpoint where Zammad fetches the data. Please make sure to include " -"a valid search :doc:`variable <../variables>` as an URL parameter. Example " -"for a free text search at user input: ``#{search.term}``" +"This section will hold any other integration that can't be grouped up (yet)." msgstr "" -#: ../system/objects/types.rst:232 -msgid "" -"If in doubt, ask the responsible person for the external data source how " -"they expect the strucuture of the URL." +#: ../system/integrations/ldap/index.rst:2 +msgid "LDAP / Active Directory" msgstr "" -#: ../system/objects/types.rst:236 +#: ../system/integrations/ldap/index.rst:4 msgid "" -"Depending on your search variable, the preview might work or not. The reason " -"is that the context might not be available and it is no bug." +"Zammad comes with a powerful LDAP integration that allows you to have a " +"single source of truth. By this you reduce the number of login credentials " +"your user has to remember." msgstr "" -#: ../system/objects/types.rst:239 +#: ../system/integrations/ldap/index.rst:10 msgid "" -"Please also make sure to use a variable which is available in your object " -"context. For example you won't be able to search for a ticket in a user " -"object context." -msgstr "" - -#: ../system/objects/types.rst:252 -msgid "SSL Verification" +"The LDAP source is also a perfect candidate for Zammad's :docs:`Kerberos " +"Single Sign-On ` but also works as addition " +"to other :doc:`/settings/security/third-party`." msgstr "" -#: ../system/objects/types.rst:245 -msgid "Here you can switch the SSL verification to no." +#: ../system/integrations/ldap/index.rst:None +msgid "Zammands LDAP management page" msgstr "" -#: ../system/objects/types.rst:249 -msgid "" -"If your external data source system is using self signed certificates, " -"please have a look :doc:`here ` for " -"further information about how to handle them in Zammad, so you can keep the " -"SSL verification activated." +#: ../system/integrations/ldap/index.rst:25 +msgid "📝 :doc:`manage`" msgstr "" -#: ../system/objects/types.rst:258 -msgid "HTTP Authentication" +#: ../system/integrations/ldap/index.rst:25 +msgid "Add, modify, remove or re-arrange your LDAP-Sources as needed." msgstr "" -#: ../system/objects/types.rst:255 -msgid "" -"If your external data source requires an authentication, you can set it " -"here. You can leave it empty or choose between *Basic Authentication* or " -"*Authentication Token* (selecting one of the two methods leads to additional " -"fields where you can enter your credentials/token)." +#: ../system/integrations/ldap/index.rst:30 +msgid "Before you continue, please note the following limitations." msgstr "" -#: ../system/objects/types.rst:265 -msgid "Search result list key" +#: ../system/integrations/ldap/index.rst:32 +msgid "Mapping / Synchronizing organizations is not possible" msgstr "" -#: ../system/objects/types.rst:261 +#: ../system/integrations/ldap/index.rst:36 msgid "" -"Defines the level in the JSON structure which provides the list with search " -"results. You can leave it empty, if the data is already provided as an " -"array. If you have to go deeper in the structure, you can provide a path " -"with ``.`` as separators, e.g. ``key.subkey.sub-sub-key``." +"You may want to consider using domain based assignments to overcome this " +"issue. Learn more on :doc:`/manage/organizations/index`." msgstr "" -#: ../system/objects/types.rst:271 -msgid "Search result value key" +#: ../system/integrations/ldap/index.rst:39 +msgid "" +"Zammad's LDAP sync is one way. Editing user settings or permissions may be " +"overwritten upon the next sync depending on your configuration." msgstr "" -#: ../system/objects/types.rst:268 -msgid "" -"Defines the attribute in the structure in which your external data source " -"provides the *value* for your data. An example would be a product *number*. " -"If you have to go deeper in the structure, you can provide a path with ``.`` " -"as separators, e.g. ``key.subkey.sub-sub-key``." +#: ../system/integrations/ldap/index.rst:41 +msgid "Nested groups are not supported." msgstr "" -#: ../system/objects/types.rst:277 -msgid "Search result label key" +#: ../system/integrations/ldap/index.rst:42 +msgid "Synchronizing user avatars from LDAP is not supported." msgstr "" -#: ../system/objects/types.rst:274 -msgid "" -"Defines the attribute in the structure in which your external data source " -"provides the *label* for your data. An example would be a product *name*. If " -"you have to go deeper in the structure, you can provide a path with ``.`` as " -"separators, e.g. ``key.subkey.sub-sub-key``." +#: ../system/integrations/ldap/index.rst:43 +msgid "Unlike user filters, group filters cannot be changed." msgstr "" -#: ../system/objects/types.rst:280 +#: ../system/integrations/ldap/index.rst:44 msgid "" -"In the preview area, you can find the following items (depending on your " -"configuration above):" +"When a user originates from an LDAP server, Zammad will try to verify the " +"login credentials against LDAP first - if this fails Zammad will check its " +"local database." msgstr "" -#: ../system/objects/types.rst:283 +#: ../system/integrations/ldap/index.rst:50 msgid "" -"**Error/hint message** (only if configuration is not complete): Zammad tells " -"you, if there is a problem and what you should change in your configuration." +"Users can have local passwords even if they're LDAP users! You can learn " +"more about user accounts in general on :doc:`/manage/users/index`." msgstr "" -#: ../system/objects/types.rst:286 +#: ../system/integrations/ldap/index.rst:54 msgid "" -"**Search field**: search for an existing attribute in the data source to get " -"a preview. This is required for the fields below to show up." +"When several LDAP sources contain the same user (meaning the same email " +"address), the user in question will be updated with every source configured. " +"*The last LDAP source will win.*" msgstr "" -#: ../system/objects/types.rst:288 +#: ../system/integrations/ldap/index.rst:58 msgid "" -"**Search result response** (only if configuration is not complete): here you " -"can find a syntax highlighted JSON preview of the response, based on the " -"search term you entered." +"This is subject to change with `Issue 4109 `_ in the future." msgstr "" -#: ../system/objects/types.rst:291 +#: ../system/integrations/ldap/index.rst:60 msgid "" -"**Search result list** (only if *search result list key* is properly set): " -"output of the structure under the configured *search result list key*." +"Synchronization statistics currently affect *all* configured LDAP sources. " +"This also applies for newly added or updated sources." msgstr "" -#: ../system/objects/types.rst:294 +#: ../system/integrations/ldap/index.rst:63 msgid "" -"**Preview table** (when fully configured): Zammad shows you a table which " -"includes the found items based on the search string (value, label and " -"optional link). You can use this preview if you don't have the complete data " -"structure of the external system in mind." +"This is subject to change with `Issue 4108 `_ in the future." msgstr "" -#: ../system/objects/types.rst:299 +#: ../system/integrations/ldap/index.rst:65 msgid "" -"An example of a configured external data source field from agent perspective:" +"Zammad currently has limited fallback server support. You can workaround " +"this by providing several sources - however, ensure to have the exact same " +"configuration on your fallback." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Screencast showing the search for a product in a ticket" +#: ../system/integrations/ldap/index.rst:69 +msgid "" +"This is subject to improve with `Issue 4107 `_ in the future." msgstr "" -#: ../system/objects/types.rst:307 -msgid "URL fields (Link-Template)" +#: ../system/integrations/ldap/index.rst:76 +msgid "" +"This section holds all requests Zammad handled for all LDAP sources. These " +"entries can either contain synchronization information or logins " +"(authentication attempts via Zammad's login interface)." msgstr "" -#: ../system/objects/types.rst:311 +#: ../system/integrations/ldap/index.rst:80 msgid "" -"This function is restricted to Text, Select and External data source types " -"only." +"By clicking on any request, Zammad will provide even more information. The " +"provided information can be useful when something does not work as expected." msgstr "" -#: ../system/objects/types.rst:314 +#: ../system/integrations/ldap/index.rst:85 msgid "" -"Link-Templates are an amazing way to dynamically generate URLs. They allow " -"you to integrate other systems better without having to manually copy data " -"from Zammad if possible." +"Especially a LDAP synchronization can cause many log entries. The web " +"interface will always limit the number of shown entries to the last 50 " +"entries." msgstr "" -#: ../system/objects/types.rst:320 +#: ../system/integrations/ldap/index.rst:None msgid "" -"Another great way of communicating with another system may be Zammad's :doc:" -"`Webhooks `." +"Screencast showing LDAP integration log entries and a detail view on\n" +"an entry." msgstr "" -#: ../system/objects/types.rst:323 -msgid "" -"After filling a link-template enabled field, an URL icon will appear on its " -"right. Clicking on the icon opens a new tab." +#: ../system/integrations/ldap/manage.rst:2 +msgid "Manage LDAP-Sources" msgstr "" -#: ../system/objects/types.rst:328 +#: ../system/integrations/ldap/manage.rst:6 msgid "" -"Even though Zammad displays the link template within object edit and create " -"screens, the function is optional. It's only active if you populate the " -"field." +"Please keep in mind all current limitations for the LDAP synchronization. " +"This will help to understand scopes of the following operations better." msgstr "" -#: ../system/objects/types.rst:333 -msgid "" -"What's the difference between URL and text fields with link template...?!" +#: ../system/integrations/ldap/manage.rst:65 +msgid "Add new source" msgstr "" -#: ../system/objects/types.rst:335 +#: ../system/integrations/ldap/manage.rst:10 msgid "" -"Both fields have different use cases. Use ``text`` type text fields when " -"ever you have a *static* url that requires dynamic parameters. If you " -"require a drag & drop like field that you can put in any URL, use ``URL`` " -"type text fields." +"Using the *New Source* button allows you to add new LDAP sources to your " +"installation. You're not limited in the number of sources, however, keep in " +"mind that many sources will also take more time to synchronize." msgstr "" -#: ../system/objects/types.rst:340 +#: ../system/integrations/ldap/manage.rst:14 msgid "" -"The difference is easier to spot when comparing the fields directly, below " -"screencast shows the result - the dynamic approach uses existing values in " -"the moment of updating to built the URL - e.g. ``https://google.com/search?" -"q=cookies`` - while the URL approach uses the actual URL of the field - e.g. " -"``https://zammad.com``." +"You can choose between different encryption types, namely *SSL* and " +"*STARTTLS* or none of them (\"*No SSL*\"). If you choose *SSL* or " +"*STARTTLS*, Zammad will display an additional *SSL verification* option that " +"allows you to disable the verification, e.g. for self-signed SSL " +"certificates. You can also tell Zammad to use a different port by appending " +"``:`` to your hostname/IP." msgstr "" -#: ../system/objects/types.rst:None +#: ../system/integrations/ldap/manage.rst:0 msgid "" -"Screencast showing the differents in between URL and text type fields with " -"actual values" +"Screenshot of configuring a new LDAP source with SSL encryption and SSL " +"verification" msgstr "" -#: ../system/objects/types.rst:352 -msgid "How does this work...?!" +#: ../system/integrations/ldap/manage.rst:26 +msgid "" +"New Source with SSL transport security enabled and certificate verification" msgstr "" -#: ../system/objects/types.rst:354 +#: ../system/integrations/ldap/manage.rst:30 msgid "" -"As an example, let's say you have an attribute called ``amazing_attribute`` " -"and you want to open a google search directly with the input from that field." +"Using an user filter can be a good idea if you only require a small subset " +"of your LDAP users in Zammad." msgstr "" -#: ../system/objects/types.rst:357 -msgid "" -"Providing the link-template field below allows you to do so: ``https://www." -"google.com/search?q=#{ticket.amazing_attribute}``" +#: ../system/integrations/ldap/manage.rst:42 +msgid "This especially affects inactive users" msgstr "" -#: ../system/objects/types.rst:362 +#: ../system/integrations/ldap/manage.rst:34 msgid "" -"You can use any :doc:`Zammad variable ` as long as it's " -"available in the moment you need it." +"As every LDAP behaves differently on which attributes and how they are set, " +"Zammad doesn't care about any flags." msgstr "" -#: ../system/objects/types.rst:365 +#: ../system/integrations/ldap/manage.rst:37 msgid "" -"As a result, you are redirected to Google with a search for the value of the " -"attribute, if you click on the button in the ticket (as you can see in the " -"screencast above)." +"Users that no longer are returned by your LDAP source will automatically be " +"set to inactive. Zammad assumes that the user was deactivated." msgstr "" -#: ../system/packages.rst:2 -msgid "Packages" +#: ../system/integrations/ldap/manage.rst:41 +msgid "" +"Users will never be removed automatically! If you want to remove obsolete " +"users, use :doc:`/system/data-privacy`." msgstr "" -#: ../system/packages.rst:4 -msgid "That's the package management-area." +#: ../system/integrations/ldap/manage.rst:46 +msgid "Active Directory admins" msgstr "" -#: ../system/packages.rst:6 -msgid "Individual add-ons for Zammad can be installed and managed here." +#: ../system/integrations/ldap/manage.rst:45 +msgid "" +"Active Directories are quite specific on how to filter for active users only " +"- please see the `Microsoft documentation `_ for more " +"information." msgstr "" -#: ../system/sessions.rst:2 -msgid "Sessions" +#: ../system/integrations/ldap/manage.rst:51 +msgid "" +"*Do not* manually write pathes of either LDAP attributes or groups. If " +"Zammad does not display them, it either cannot find them or you have a lot " +"of users that don't have the attributes populated." msgstr "" -#: ../system/sessions.rst:4 +#: ../system/integrations/ldap/manage.rst:55 msgid "" -"Sessions management allows reviewing currently known user sessions and " -"allows to end these. The session timeout is affected by :ref:" -"`security_session_timeout` configurations from security settings." +"Zammad will always only return attributes that are filled - this reduces the " +"returned list of attributes greatly." msgstr "" -#: ../system/sessions.rst:None -msgid "Screenshot showing Zammad's session management" +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing how to add a new LDAP source" msgstr "" -#: ../system/sessions.rst:13 -msgid "Zammad will provide the following information:" +#: ../system/integrations/ldap/manage.rst:63 +msgid "" +"If your LDAP system doesn't allow anonymous bind, Zammad detects it and " +"provides you an editable \"Base DN\" *text* field instead of a prefilled " +"*select* field." msgstr "" -#: ../system/sessions.rst:16 -msgid "" -"The user account this session entry belongs to. It can be normal if a user " -"has several sessions in the list. This can be due to changed browser " -"information or if you use e.g. single sign on methods where the user does " -"not use the log off button." +#: ../system/integrations/ldap/manage.rst:81 +msgid "Review or edit existing source" msgstr "" -#: ../system/sessions.rst:22 -msgid "Browser" +#: ../system/integrations/ldap/manage.rst:68 +msgid "" +"Clicking on a LDAP source will provide a configuration and mapping overview." msgstr "" -#: ../system/sessions.rst:22 -msgid "The browser agent communicated to Zammad." +#: ../system/integrations/ldap/manage.rst:70 +msgid "" +"If needed you can then use the *Change* button to update either the name, " +"active state or the whole configuration. If you're changing the whole " +"configuration, the dialogue will be identical to the source creation." msgstr "" -#: ../system/sessions.rst:40 -msgid "Location" +#: ../system/integrations/ldap/manage.rst:76 +msgid "" +"Did your LDAP server change? Different LDAP servers have different " +"structures and default attributes. This causes the LDAP synchronization to " +"likely fail. Consider removing the affected source and re-add it." msgstr "" -#: ../system/sessions.rst:25 -msgid "" -"The anticipated location based on the users IP address. Depending on the IP " -"address the result shown may differ. This option depends on :doc:`/settings/" -"system/services`." +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing the update of the source name." msgstr "" -#: ../system/sessions.rst:29 -msgid "The following information can be shown:" +#: ../system/integrations/ldap/manage.rst:89 +msgid "Re-arrange LDAP source's order" msgstr "" -#: ../system/sessions.rst:33 -msgid "IP address" +#: ../system/integrations/ldap/manage.rst:84 +msgid "" +"You can change the synchronization order for each source at any time. Zammad " +"will synchronize the sources from top to bottom." msgstr "" -#: ../system/sessions.rst:32 +#: ../system/integrations/ldap/manage.rst:0 msgid "" -"Either if you set *Geo IP services* to inactive or you're using internal IP " -"address which do not provide location information." +"Screencasting showing how to change the source order by using\n" +"drag and drop." msgstr "" -#: ../system/sessions.rst:40 -msgid "Country (or Country + City)" +#: ../system/integrations/ldap/manage.rst:101 +msgid "Remove a source" msgstr "" -#: ../system/sessions.rst:36 +#: ../system/integrations/ldap/manage.rst:92 msgid "" -"If *Geo IP services* is enabled only. Depends on how detailed the available " -"IP address information are." +"If you no longer need the a LDAP source or simply want to start over, you " +"can remove them at any time. This will not remove synchronized users, data " +"synchronized or permissions." msgstr "" -#: ../system/sessions.rst:39 +#: ../system/integrations/ldap/manage.rst:98 msgid "" -"Be aware that results can be inaccurate - this technically is not an error." +"Not sure if you'd need the source later on? Set the source to inactive " +"instead of removing it - see *Review or edit existing source* for more." msgstr "" -#: ../system/sessions.rst:43 -msgid "Age" +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing how to remove LDAP sources." msgstr "" -#: ../system/sessions.rst:43 -msgid "Provides the time when the session initially has been created." +#: ../system/integrations/pgp/index.rst:2 +msgid "PGP" msgstr "" -#: ../system/sessions.rst:50 -msgid "Update" +#: ../system/integrations/pgp/index.rst:7 +msgid "" +"Pretty Good Privacy (PGP) is another method for secure email communication. " +"With PGP, you can exchange **signed** and **encrypted** messages with others." msgstr "" -#: ../system/sessions.rst:46 -msgid "" -"Provides the time the user used this session to open Zammad. This timestamp " -"is only updated if the user e.g. reloads, not during normal work on tickets." +#: ../system/integrations/pgp/index.rst:13 +#: ../system/integrations/smime/index.rst:17 +msgid "Signing" msgstr "" -#: ../system/sessions.rst:50 -msgid "This timestamp is being used for the session timeout." +#: ../system/integrations/pgp/index.rst:11 +msgid "is a proof that a message hasn't been manipulated on its way." msgstr "" -#: ../system/sessions.rst:53 +#: ../system/integrations/pgp/index.rst:13 msgid "" -"Use the delete button to remove a single session on behalf of your user." +"In other words, it guarantees message **integrity** and **authenticity**." msgstr "" -#: ../system/subscription/billing.rst:2 -msgid "Billing" +#: ../system/integrations/pgp/index.rst:19 +#: ../system/integrations/smime/index.rst:22 +msgid "Encryption" msgstr "" -#: ../system/subscription/billing.rst:4 +#: ../system/integrations/pgp/index.rst:16 +#: ../system/integrations/smime/index.rst:20 msgid "" -"Within the billing tab you can control all billing relevant information like " -"invoices, billing address and the option to cancel your subscription." -msgstr "" - -#: ../system/subscription/billing.rst:33 -msgid "Billing information" +"scrambles a message so that it can only be unscrambled by the intended " +"recipient." msgstr "" -#: ../system/subscription/billing.rst:8 +#: ../system/integrations/pgp/index.rst:19 msgid "" -"All adjusted billing information below only affect future invoices. If your " -"invoice was issued wrong, please contact `our sales team `_." +"In other words, it guarantees message **privacy** and **data security**." msgstr "" -#: ../system/subscription/billing.rst:14 -msgid "Billing address" +#: ../system/integrations/pgp/index.rst:25 +msgid "Screenshot of ticket creation with encrypt and sign buttons" msgstr "" -#: ../system/subscription/billing.rst:13 +#: ../system/integrations/pgp/index.rst:25 msgid "" -"Provide your company address here, make sure to include the companies name " -"in case required. This address will be referenced on your invoice." +"Once PGP has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " +"appear in the ticket composer." msgstr "" -#: ../system/subscription/billing.rst:18 -msgid "VAT ID" +#: ../system/integrations/pgp/index.rst:28 +msgid "**Sign button not visible?**" msgstr "" -#: ../system/subscription/billing.rst:17 +#: ../system/integrations/pgp/index.rst:30 msgid "" -"Provide your VAT ID here. If applicable your invoice will not contain German " -"VAT. Please make sure to pay the VAT in your country as required." +"Please note that the signing of emails is based on the outgoing email " +"account. That means you have to choose a group with a sender email account, " +"which has a private key assigned." msgstr "" -#: ../system/subscription/billing.rst:27 -msgid "Billing Email Address" +#: ../system/integrations/pgp/index.rst:35 +msgid "Handling of Keys" msgstr "" -#: ../system/subscription/billing.rst:21 +#: ../system/integrations/pgp/index.rst:36 msgid "" -"Usually the instance owner (the person that registered the instance) will " -"receive all emails including the invoices. In case you have your own billing " -"department, you can provide their email address here." +"To use the PGP function, you have to enable the integration (PGP) by " +"switching the toggle to *enabled*." msgstr "" -#: ../system/subscription/billing.rst:25 +#: ../system/integrations/pgp/index.rst:39 msgid "" -"All billing relevant information will then be sent to this email address." +"You can add keys by clicking the *add key* button. The keys can be imported " +"from a file or you can paste the content of the key in the text box." msgstr "" -#: ../system/subscription/billing.rst:27 -msgid "Invoices are sent as attachment (PDF) to this email address." +#: ../system/integrations/pgp/index.rst:42 +msgid "**Which keys do I have to import?**" msgstr "" -#: ../system/subscription/billing.rst:29 +#: ../system/integrations/pgp/index.rst:44 msgid "" -"Don't forget to press the *Submit* button after you changed above settings." +"For **signing** *outgoing* emails, you have to import the private key of " +"your Zammad email account." msgstr "" -#: ../system/subscription/billing.rst:0 +#: ../system/integrations/pgp/index.rst:47 msgid "" -"Screenshot showing options for billing information within the\n" -"subscription menu" -msgstr "" - -#: ../system/subscription/billing.rst:70 -msgid "Payment history" +"For **encrypting** *outgoing* emails, you have to import the public key of " +"the customer's email account." msgstr "" -#: ../system/subscription/billing.rst:36 +#: ../system/integrations/pgp/index.rst:50 msgid "" -"The payment history will display a history of all paid invoices. At this " -"point you can also download these in case you need them again." +"For **verifying the signature** of signed *incoming* emails, you have to " +"import the public key of the customer." msgstr "" -#: ../system/subscription/billing.rst:41 +#: ../system/integrations/pgp/index.rst:53 msgid "" -"You will only find *paid* invoices here. Invoices that are to be billed are " -"not available before the payment is completed." +"For **decrypting** of encrypted *incoming* emails, you have to import the " +"private key of your Zammad email account." msgstr "" -#: ../system/subscription/billing.rst:46 -msgid "Date" +#: ../system/integrations/pgp/index.rst:57 +msgid "Import Keys From a File" msgstr "" -#: ../system/subscription/billing.rst:46 -msgid "Date of the invoice creation." +#: ../system/integrations/pgp/index.rst:58 +msgid "You can import keys from a file in the section **Upload key**:" msgstr "" -#: ../system/subscription/billing.rst:49 -msgid "Amount" +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of adding a key via file" msgstr "" -#: ../system/subscription/billing.rst:49 -msgid "Invoice total including VAT if applicable." +#: ../system/integrations/pgp/index.rst:64 +msgid "" +"**Supported file formats:** ASCII-armor as well as binary GPG format " +"(basically any GPG supported key format) is supported here." msgstr "" -#: ../system/subscription/billing.rst:52 -msgid "" -"Contains contract period (monthly or yearly) and hosted plan for the " -"subscription period in question." +#: ../system/integrations/pgp/index.rst:68 +msgid "Import Keys by Pasting the Content" msgstr "" -#: ../system/subscription/billing.rst:63 -msgid "Payment method / Service period" +#: ../system/integrations/pgp/index.rst:69 +msgid "You can also paste the key's content in the section **paste key**:" msgstr "" -#: ../system/subscription/billing.rst:56 -msgid "" -"Used bank account or credit card as well as the subscription period the " -"invoice is about." +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of adding a key via pasting" msgstr "" -#: ../system/subscription/billing.rst:61 +#: ../system/integrations/pgp/index.rst:75 msgid "" -"It might happen that the invoice date and subscription period differ. This " -"is nothing to worry about, the subscription periods will be accounted later " -"on." +"**Supported format:** Please note that only ASCII-armor is supported here." msgstr "" -#: ../system/subscription/billing.rst:67 -msgid "Receipt" +#: ../system/integrations/pgp/index.rst:78 +msgid "Deleting Keys" msgstr "" -#: ../system/subscription/billing.rst:66 +#: ../system/integrations/pgp/index.rst:79 msgid "" -"Use the arrow to download the invoice in question. You can download all " -"available invoices any time you need to here!" +"If you want to delete a specific key, you can do it by clicking on the menu " +"in the *actions* column and select **delete**:" msgstr "" -#: ../system/subscription/billing.rst:0 -msgid "Screenshot showing payment history of a hosted instance" +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of deleting a key" msgstr "" -#: ../system/subscription/billing.rst:94 -msgid "Do you want to cancel your subscription?" +#: ../system/integrations/pgp/index.rst:88 +msgid "Downloading Keys" msgstr "" -#: ../system/subscription/billing.rst:73 +#: ../system/integrations/pgp/index.rst:89 msgid "" -"In case you no longer want to use Zammad's SaaS, you can cancel your " -"subscription by using the red *Yes, please cancel my subscription* button." +"If you want to download your keys, you can do this as well via corresponding " +"action buttons. Depending on the key, you can choose wether you want to " +"download the private or the public key." msgstr "" -#: ../system/subscription/billing.rst:76 -msgid "" -"Your subscription will end the day after your trial or billing period ends." +#: ../system/integrations/pgp/index.rst:95 +#: ../system/integrations/smime/manage-certificates.rst:76 +msgid "Default Behavior" msgstr "" -#: ../system/subscription/billing.rst:80 +#: ../system/integrations/pgp/index.rst:96 msgid "" -"We will remind you about your cancelled subscription several times up front. " -"After the subscription ended all instance data will be removed. A restore " -"*is not* possible after that point!" +"Here you can adjust on per group basis, if *sign* and *encryption* is on or " +"off by default. Please be aware, that agents can always override the setting " +"for each individual article." msgstr "" -#: ../system/subscription/billing.rst:0 -msgid "Screencast showing how to cancel a subscription" +#: ../system/integrations/pgp/index.rst:None +msgid "Adjusting default behavior on per group basis" msgstr "" -#: ../system/subscription/billing.rst:87 -msgid "**😖 Cancelled by accident?**" +#: ../system/integrations/pgp/index.rst:107 +msgid "" +"Here you can see the last actions regarding signing and encryption and if " +"they were successful." msgstr "" -#: ../system/subscription/billing.rst:89 -msgid "" -"You can always undo the cancellation via the *Yes, undo the cancellation of " -"my subscription* button up to the last subscription day!" +#: ../system/integrations/pgp/index.rst:117 +msgid "**Sign button is not visible, but keys are imported.**" +msgstr "" + +#: ../system/integrations/pgp/index.rst:115 +msgid "Did you choose a group in the ticket?" msgstr "" -#: ../system/subscription/billing.rst:0 +#: ../system/integrations/pgp/index.rst:116 msgid "" -"Screenshot showing a red button to cancel the subscription\n" -"cancellation" +"Did you import a private key for the email adress, which is used for " +"outgoing emails in the group?" msgstr "" -#: ../system/subscription/index.rst:2 -msgid "Subscription (SaaS)" +#: ../system/integrations/pgp/index.rst:122 +msgid "**How to obtain keys?**" msgstr "" -#: ../system/subscription/index.rst:4 +#: ../system/integrations/pgp/index.rst:120 msgid "" -"The subscription settings page allows you to configure your instances " -"package and number of agents required." +"You can create them yourself! There are some good tutorials on the web on " +"how to create them. Providing keys to Zammad is a prerequisite to use the " +"PGP feature." msgstr "" -#: ../system/subscription/index.rst:9 -msgid "" -"This setting section is only available for Hosted setups. If you're looking " -"for on premise support contracts, please see the `Zammad pricing page " -"`_." +#: ../system/integrations/pgp/index.rst:127 +msgid "**It says a passphrase is needed, but I haven't got one.**" msgstr "" -#: ../system/subscription/index.rst:20 +#: ../system/integrations/pgp/index.rst:125 msgid "" -"The subscription section currently consists of two tabs: Plan & Billing. For " -"your overview we've divided those two tabs into independent sub pages:" +"If the key is secured with a passphrase, you have to provide it for the " +"import in Zammad. It is possible that keys may have an empty passphrase. " +"However, this is *not* recommended." msgstr "" -#: ../system/subscription/index.rst:25 -msgid ":doc:`💰 Subscription plan `" +#: ../system/integrations/pgp/index.rst:132 +msgid "**How do my customers get my new key?**" msgstr "" -#: ../system/subscription/index.rst:24 +#: ../system/integrations/pgp/index.rst:130 msgid "" -"Everything affecting your instance subscription functions like number of " -"agents, package and payment method." +"You have to provide your **public** key in advance. Your customer also has " +"to configure PGP in their email workflow and import your public key. The " +"other way round, you have to get the public key of your customer and have to " +"import it to Zammad." +msgstr "" + +#: ../system/integrations/slack.rst:2 +msgid "Slack" msgstr "" -#: ../system/subscription/index.rst:28 -msgid ":doc:`🧾 Subscription billing `" +#: ../system/integrations/slack.rst:4 +msgid "**⚠️ Deprecation warning ⚠️**" msgstr "" -#: ../system/subscription/index.rst:28 +#: ../system/integrations/slack.rst:6 msgid "" -"Everything regarding billing address, invoices and account cancellation." +"Zammad 7 will no longer support this dedicated Slack integration. It is " +"recommended to switch to :doc:`pre-defined webhooks ` instead. Existing Slack integrations should " +"be migrated manually before this feature is dropped." msgstr "" -#: ../system/subscription/index.rst:33 -msgid "FAQ" +#: ../system/integrations/slack.rst:14 +msgid "" +"In order to use this feature, please add a new Slack app to your Workspace. " +"The App you need is called ``Incoming WebHooks`` ." msgstr "" -#: ../system/subscription/index.rst:37 -msgid "I set up a trial account but am missing functions to test" +#: ../system/integrations/slack.rst:18 +msgid "Why Do I Need This Feature?" msgstr "" -#: ../system/subscription/index.rst:36 +#: ../system/integrations/slack.rst:20 msgid "" -"The trial instance is running within the professional package allowing up to " -"three agents." +"If you're already using Slack for your team communication, you'll love this " +"feature! Our Slack integration can push ticket notifications about the last " +"ticket article based on the following events:" msgstr "" -#: ../system/subscription/index.rst:40 -msgid "Can I change package within the trial?" +#: ../system/integrations/slack.rst:24 +msgid "on Ticket creation" msgstr "" -#: ../system/subscription/index.rst:40 -msgid "No. As soon as the package is changed the subscription begins." +#: ../system/integrations/slack.rst:25 +msgid "on Ticket updates" msgstr "" -#: ../system/subscription/index.rst:45 -msgid "What happens to my trial instance after the trial period ended?" +#: ../system/integrations/slack.rst:26 +msgid "on reached reminders" msgstr "" -#: ../system/subscription/index.rst:43 -msgid "" -"Your instance will automatically be canceled for you. Please see *What " -"happens to my instance after it has been canceled?* for more." +#: ../system/integrations/slack.rst:27 +msgid "a Ticket has escalated" msgstr "" -#: ../system/subscription/index.rst:58 -msgid "What happens to my instance after it has been canceled?" +#: ../system/integrations/slack.rst:28 +msgid "a Ticket is going to escalate" msgstr "" -#: ../system/subscription/index.rst:48 -msgid "That depends slightly on your instance state:" +#: ../system/integrations/slack.rst:30 +msgid "" +"Zammad will provide the Ticket title, a direct link to the Ticket, the event " +"type (creation, updated, escalation), the customer, time and the last " +"article that has triggered the notification." msgstr "" -#: ../system/subscription/index.rst:54 -msgid "Trial instance" +#: ../system/integrations/slack.rst:34 +msgid "" +"This will give you further options, as you can see e.g. escalating tickets " +"that are assigned to an agent that's e.g. absent. You can interact faster, " +"as you might see problems earlier (or even before the problem gets one)." msgstr "" -#: ../system/subscription/index.rst:51 +#: ../system/integrations/slack.rst:38 msgid "" -"If you're still on trial, we will ice your instance and remind you once " -"again about your instance. We then will wait some days and remove your " -"instance from our system. This is the last time we will inform you by Email." +"If needed and wanted, you can even discuss directly about the topic before " +"sending an answer to the customer. Another possible use case would be a " +"agent monitoring new agents and their answers to tickets." msgstr "" -#: ../system/subscription/index.rst:58 -msgid "Paid instance" +#: ../system/integrations/slack.rst:44 +msgid "Configure the Integration" msgstr "" -#: ../system/subscription/index.rst:57 +#: ../system/integrations/slack.rst:46 msgid "" -"If you're a paying customer and canceled your subscription, the instance " -"removal will take place the day after your last subscription day." +"First of all, please go to your slack workspace - go to administration => " +"Manage Apps. If you don't have an app yet, you can simply add a new one - " +"just search for ``Incoming WebHooks`` and customize the app to your needs." msgstr "" -#: ../system/subscription/index.rst:60 -msgid "Can removed instances be restored?" +#: ../system/integrations/slack.rst:50 +msgid "" +"Choose (or create) the channel Zammad should post it's information to and " +"press on \"Add Incoming WebHooks integration\". If you're ready, copy the " +"provided WebHook URL and go to your Zammad installation." msgstr "" -#: ../system/subscription/index.rst:61 -msgid "No. Once your instance has been removed, a restoration is not possible." +#: ../system/integrations/slack.rst:56 +msgid "" +"You need administrative rights on the Slack Workspace. The link to the app " +"directory is normally ``https://[workspace-name].slack.com/apps`` ." msgstr "" -#: ../system/subscription/plan.rst:2 ../system/subscription/plan.rst:38 -msgid "Plan" +#: ../system/integrations/slack.rst:63 +msgid "" +"To configure the slack integration, log in to Zammad and go to Integrations " +"(System) => Slack in the admin panel." msgstr "" -#: ../system/subscription/plan.rst:16 -msgid "Subscription" +#: ../system/integrations/slack.rst:66 +msgid "" +"Here you can choose on what evens Zammad should post information about a " +"ticket to your Slack channel. Next you need to device what groups shall be " +"affected by this, as anybody with access to that specific Slack channel can " +"read at least parts of the ticket this might be a privacy issue, if you " +"select the wrong groups. The username is simply the name that Zammad uses as " +"display name inside the Slack chat. The channel defines the Slack channel " +"the information is being posted in. As last option, you can set a custom " +"icon for posting to slack." msgstr "" -#: ../system/subscription/plan.rst:5 +#: ../system/integrations/slack.rst:74 msgid "" -"On the top of the subscription summary you'll find the number of used and " -"available (booked) agent seats. By using the *see more* link you can also " -"expand an agent list to see the currently configured active agents. This " -"list *does not* count accounts with admin permissions only." +"When you're ready, just hit \"Submit\" and enable the integration. Zammad " +"will now post new ticket information based on the trigger you chose. Below " +"the options you have the recent log that shows the latest requests to Slack " +"for debugging if needed." msgstr "" -#: ../system/subscription/plan.rst:0 +#: ../system/integrations/slack.rst:81 msgid "" -"Within subscription you can always see how many agents are still\n" -"available to add and who uses the seats." +"If you leave the Icon URL empty, Zammad will use the Zammad logo instead. " +"The icon should be a square PNG file." msgstr "" -#: ../system/subscription/plan.rst:14 +#: ../system/integrations/slack.rst:90 msgid "" -"Learn more on how to manage your agents in general :doc:`here `." +"The following figure shows how it will look if you choose to receive updates " +"on created and updated tickets. On every post Zammad sends to the Slack " +"channel, you can create new threads to discuss about the new article." msgstr "" -#: ../system/subscription/plan.rst:19 +#: ../system/integrations/slack.rst:96 msgid "" -"This section gives you an overview of the available plans and their " -"functions / limits. If you require a more detailed table, check our " -"`detailed pricing table `_ for more." +"If you just want to keep track of soon escalating or already escalated " +"tickets, it will look the the following figure. Zammad changes the color in " +"front of the post so you can easily see the state of the ticket." msgstr "" -#: ../system/subscription/plan.rst:23 +#: ../system/integrations/slack.rst:102 msgid "" -"Your selection in this step will decide on the base agent price and e.g. " -"agent limits that might apply in the summary step." +"If you change the state, Zammad will also put information on what state the " +"ticket gets and (if pending state) the date until it pends. You'll also " +"recognize the color codes in front of posts on slack, as they are exact the " +"same the ticket state colors you'll see in Zammad!" msgstr "" -#: ../system/subscription/plan.rst:26 -msgid "" -"The green *Selected* button will also tell you what plan you're currently in." +#: ../system/integrations/smime/index.rst:2 +msgid "S/MIME" msgstr "" -#: ../system/subscription/plan.rst:30 +#: ../system/integrations/smime/index.rst:11 msgid "" -"Trial instances are running at Professional with 3 agents. The plan cannot " -"be changed during the trial for technical reasons, if you require more " -"agents for testing, please contact `our sales team `_ with a reason for the raise request." +"S/MIME is the most widely-supported method for secure email communication. " +"With S/MIME, you can exchange **signed** and **encrypted** messages with " +"others." msgstr "" -#: ../system/subscription/plan.rst:0 +#: ../system/integrations/smime/index.rst:15 msgid "" -"Screenshot showing three available packages for a hosted Zammad\n" -"instance" +"is proof that a message hasn't been tampered with or sent by an impersonator." msgstr "" -#: ../system/subscription/plan.rst:83 -msgid "Summary" +#: ../system/integrations/smime/index.rst:17 +msgid "" +"In other words, it guarantees a message's **integrity** and **authenticity**." msgstr "" -#: ../system/subscription/plan.rst:41 -msgid "" -"In this section you can adjust the settings of the previous selected plan." +#: ../system/integrations/smime/index.rst:22 +msgid "In other words, it guarantees **privacy** and **data security**." msgstr "" -#: ../system/subscription/plan.rst:45 -msgid "" -"Note that upgrading (more agents, higher package) is always possible, " -"however, downgrading will only happen when your billing period renews." +#: ../system/integrations/smime/index.rst:28 +msgid "Screencast demo of S/MIME features for both new tickets and replies" msgstr "" -#: ../system/subscription/plan.rst:49 +#: ../system/integrations/smime/index.rst:28 msgid "" -"Upgrading resets your billing period and existing credit will be deducted " -"from the new total." +"Once S/MIME has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " +"appear in the ticket composer." msgstr "" -#: ../system/subscription/plan.rst:58 -msgid "Billing cycle" +#: ../system/integrations/smime/index.rst:32 +msgid ":doc:`🔪 Prerequisites `" msgstr "" -#: ../system/subscription/plan.rst:53 +#: ../system/integrations/smime/index.rst:31 msgid "" -"You can choose between either monthly or yearly billing. The price per agent " -"will be cheaper if you decide for yearly billing." +"New to S/MIME? This section helps you to find certificate providers and " +"points out Limitations." msgstr "" -#: ../system/subscription/plan.rst:56 -msgid "" -"If you're still trying out things and are unsure of the right package for " -"your instance, you may want to choose monthly first and then upgrade to " -"yearly when you're sure." +#: ../system/integrations/smime/index.rst:35 +msgid ":doc:`📝 Manage Certificates `" msgstr "" -#: ../system/subscription/plan.rst:66 -msgid "Plan: (Starter|Professional|Plus) - Agents" +#: ../system/integrations/smime/index.rst:35 +msgid "Add and download certificates; configure group default behaviors." msgstr "" -#: ../system/subscription/plan.rst:61 -msgid "Choose the number of agents you require for your instance." +#: ../system/integrations/smime/index.rst:38 +msgid ":doc:`😦 Troubleshooting `" msgstr "" -#: ../system/subscription/plan.rst:63 -msgid "" -"Keep in mind that some packages may have agent limits. Depending on the " -"previous chosen package, you won't be able to exceed specific agent numbers. " -"Also note that setting less agents than currently configured is not possible." +#: ../system/integrations/smime/index.rst:38 +msgid "Took a wrong turn? About recent logs and common issues." msgstr "" -#: ../system/subscription/plan.rst:69 -msgid "Total" +#: ../system/integrations/smime/index.rst:43 +msgid "" +"For more details on how S/MIME integration works on the agent side, see the :" +"user-docs:`user docs `." msgstr "" -#: ../system/subscription/plan.rst:69 -msgid "This will be the net total you're going to be billed." +#: ../system/integrations/smime/manage-certificates.rst:2 +msgid "Manage Certificates" msgstr "" -#: ../system/subscription/plan.rst:71 +#: ../system/integrations/smime/manage-certificates.rst:4 msgid "" -"By using the *Update subscription* button, the instance package will be " -"adjusted immediately. If you didn't provide a payment method yet, Zammad " -"will request you to provide one at this point." +"S/MIME is **disabled by default**. Enable it to start adding certificates." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:10 +msgid "Dialogue to add new certificates or private keys" msgstr "" -#: ../system/subscription/plan.rst:77 +#: ../system/integrations/smime/manage-certificates.rst:10 msgid "" -"In case you're still within the trial period, this means that the trial will " -"be over immediately!" +"Manage certificates in the Admin Panel under **System > Integrations > S/" +"MIME**. Certificates may be pasted in as plain text or uploaded from a file." msgstr "" -#: ../system/subscription/plan.rst:80 -msgid "Down- or upgrading during the trial period *is not* possible." +#: ../system/integrations/smime/manage-certificates.rst:14 +msgid "Add Certificate Data" msgstr "" -#: ../system/subscription/plan.rst:0 -msgid "Screenshot showing payment options and a pricing summary" +#: ../system/integrations/smime/manage-certificates.rst:36 +msgid "Add Certificate" msgstr "" -#: ../system/subscription/plan.rst:99 -msgid "Payment method" +#: ../system/integrations/smime/manage-certificates.rst:17 +msgid "" +"Import public-key certificates for both your own organization and your " +"contacts." msgstr "" -#: ../system/subscription/plan.rst:86 -msgid "You can pay via credit card or SEPA mandate." +#: ../system/integrations/smime/manage-certificates.rst:19 +msgid "" +"You can also add a bunch of certificates in one go by providing a single " +"file with all relevant certificates." msgstr "" -#: ../system/subscription/plan.rst:91 -msgid "Credit card" +#: ../system/integrations/smime/manage-certificates.rst:22 +msgid "🕵️ **ALWAYS verify certificates in-person or over the phone!**" msgstr "" -#: ../system/subscription/plan.rst:89 +#: ../system/integrations/smime/manage-certificates.rst:24 msgid "" -"Simply follow the dialogue by clicking *authorize* and confirm -if required " -"by your bank- your consent to Zammad using your card for the payments." +"The whole point of signatures is to alert you when someone is trying to " +"pretend to be someone they're not. Never accept a certificate from someone " +"online without verifying it first." msgstr "" -#: ../system/subscription/plan.rst:95 -msgid "SEPA" +#: ../system/integrations/smime/manage-certificates.rst:28 +msgid "📇 **What about trusted certificate authorities?**" msgstr "" -#: ../system/subscription/plan.rst:94 +#: ../system/integrations/smime/manage-certificates.rst:30 msgid "" -"Provide the requested information of the bank account holder and update if " -"you're ready. You'll then receive an email with the SEPA mandate." +"In some cases (e.g. when dealing with large enterprises), you may be given a " +"certificate for an entire CA, rather than a single contact. Add it here to " +"trust *all* certificates issued by that CA." msgstr "" -#: ../system/subscription/plan.rst:97 +#: ../system/integrations/smime/manage-certificates.rst:35 msgid "" -"Technically there's also the possibility to pay via invoice, however - this " -"method only applies to a fairly low number of instances. Please contact `our " -"sales team `_ for more information." +"Commercial CAs can usually be verified online. Zammad does not include a " +"list of built-in, trusted CAs." msgstr "" -#: ../system/translations.rst:2 -msgid "Translations" +#: ../system/integrations/smime/manage-certificates.rst:57 +msgid "Add Private Key" msgstr "" -#: ../system/translations.rst:4 +#: ../system/integrations/smime/manage-certificates.rst:39 msgid "" -"Translations of Zammad are processed centrally in our `Weblate instance " -"`_. This allows non-developers to review " -"and update translation texts of the language they actually speak." +"Once you've added a public-key certificate, you can import its matching " +"private key." msgstr "" -#: ../system/translations.rst:9 +#: ../system/integrations/smime/manage-certificates.rst:42 msgid "" -"Your language is in an incomplete translation state or has typos? Please " -"consider helping us in sorting this out! All you need is either a GitHub " -"account or to register directly in our instance." +"Private keys are for **your own organization only**; never ask your contacts " +"for their private keys." msgstr "" -#: ../system/translations.rst:13 +#: ../system/integrations/smime/manage-certificates.rst:0 msgid "" -"Did you know? This is also where the documentation translations are handled. " -"🤓" +"S/MIME integration showing configured certificates and possible issues with " +"Logging" msgstr "" -#: ../system/translations.rst:15 +#: ../system/integrations/smime/manage-certificates.rst:50 msgid "" -"Have a look in our :docs:`contribution section ` in the system documentation to get started!" +"A note is displayed on certificates with a matching private key (see line 2)." msgstr "" -#: ../system/translations.rst:20 -msgid "Local Translations" +#: ../system/integrations/smime/manage-certificates.rst:52 +msgid "📤 **Certificates and private keys must be uploaded separately.**" msgstr "" -#: ../system/translations.rst:22 +#: ../system/integrations/smime/manage-certificates.rst:54 msgid "" -"Apart from these system translations, there's still local translations you " -"can manage. This is relevant if you added custom objects that require " -"translations or even custom states and priorities." +"If your certificate and private key are bundled together in the same file or " +"PEM block, import it twice (once using each button)." msgstr "" -#: ../system/translations.rst:None -msgid "Translation management screen within the admin menu" +#: ../system/integrations/smime/manage-certificates.rst:57 +msgid "Please note that bulk imports of private keys are not possible." msgstr "" -#: ../system/translations.rst:31 -msgid "Updating Translations" +#: ../system/integrations/smime/manage-certificates.rst:60 +msgid "Download Certificate Data" msgstr "" -#: ../system/translations.rst:33 +#: ../system/integrations/smime/manage-certificates.rst:62 msgid "" -"Because of how Zammad ships translations, the only way to update the system " -"translations is to update your Zammad installation. The benefit of this is " -"that you no longer need internet access during a Zammad upgrade as the " -"package has everything it requires already." +"You can download the earlier provided certificates and private keys at any " +"time from your Zammad instance." msgstr "" -#: ../system/translations.rst:39 -msgid "Translation of Custom Objects" +#: ../system/integrations/smime/manage-certificates.rst:65 +msgid "" +"Please note that passphrase-protected private keys stay protected and when " +"you download them, you have to know the passphrase to use them after " +"downloading." msgstr "" -#: ../system/translations.rst:41 -msgid "" -"No problem at all! You can customize any translation locally, even if it is " -"not initially provided by the system." +#: ../system/integrations/smime/manage-certificates.rst:73 +msgid "Dialogue to download certificates or private keys" msgstr "" -#: ../system/translations.rst:44 +#: ../system/integrations/smime/manage-certificates.rst:73 +msgid "Download stored certificates and their keys" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:78 msgid "" -"Translation is supported for a broad number of features, including but not " -"limited to custom:" +"The ticket composer will set all outgoing messages to **signed and " +"encrypted** by default (assuming the required certificates exist)." msgstr "" -#: ../system/translations.rst:47 -msgid "Object Attributes" +#: ../system/integrations/smime/manage-certificates.rst:82 +msgid "These defaults can be modified on a per-group basis:" msgstr "" -#: ../system/translations.rst:48 -msgid "Ticket Macros" +#: ../system/integrations/smime/manage-certificates.rst:None +msgid "Zammad allowing to choose the default behavior on per group basis" msgstr "" -#: ../system/translations.rst:49 -msgid "Ticket Overviews" +#: ../system/integrations/smime/manage-certificates.rst:89 +msgid "" +"Of course, agents can always manually change these settings on each email " +"they send out." msgstr "" -#: ../system/translations.rst:50 -msgid "Ticket Priorities" +#: ../system/integrations/smime/prerequisites.rst:4 +msgid "A certificate *and* private key for your own organization" msgstr "" -#: ../system/translations.rst:51 -msgid "Ticket States" +#: ../system/integrations/smime/prerequisites.rst:6 +msgid "" +"(Use this to ✒️ **sign outgoing messages** and 🔓 **decrypt incoming " +"messages**.)" msgstr "" -#: ../system/translations.rst:54 -msgid "Customizing Translations" +#: ../system/integrations/smime/prerequisites.rst:9 +msgid "" +"Certificates belonging your contacts, or their issuing certificate authority " +"(CA)" msgstr "" -#: ../system/translations.rst:56 +#: ../system/integrations/smime/prerequisites.rst:11 msgid "" -"Within the translation screen, simply click on the **New Translation** " -"button." +"(Use these to ✅ **verify incoming message signatures** and 🔒 **encrypt " +"outgoing messages**.)" msgstr "" -#: ../system/translations.rst:None -msgid "New translation dialog" +#: ../system/integrations/smime/prerequisites.rst:14 +msgid "🙋 **I'm new to S/MIME. Where can I get a certificate?**" msgstr "" -#: ../system/translations.rst:62 +#: ../system/integrations/smime/prerequisites.rst:16 msgid "" -"In the dialog you can immediately enter the exact translation source (if you " -"know it) and your custom translation text for it and click **Submit**." +"The easiest way to get certificates is to buy an annual subscription through " +"a commercial CA, such as:" msgstr "" -#: ../system/translations.rst:65 +#: ../system/integrations/smime/prerequisites.rst:19 msgid "" -"Alternatively, try to search for translation suggestions in the list below. " -"Selecting an item from the list will pre-fill the translation source for you " -"and then you can just enter your custom translation." +"`Sectigo (formerly Comodo) `_" msgstr "" -#: ../system/translations.rst:69 -msgid "" -"The target language will always default to your current language selection. " -"If you need to translate for a different language, simply change the " -"selection before submitting." +#: ../system/integrations/smime/prerequisites.rst:20 +msgid "`Secorio `_" msgstr "" -#: ../system/translations.rst:73 -msgid "" -"All your custom translations will show up in the overview table when added. " -"And they will even persist across Zammad updates!" +#: ../system/integrations/smime/prerequisites.rst:21 +msgid "`GlobalSign `_" msgstr "" -#: ../system/translations.rst:76 -msgid "" -"Make sure to reload your browser if a translated string is not displayed." +#: ../system/integrations/smime/prerequisites.rst:23 +msgid "(Zammad is not affiliated with these CAs in any way.)" msgstr "" -#: ../system/translations.rst:80 -msgid "Reverting to Original Translations" +#: ../system/integrations/smime/prerequisites.rst:25 +msgid "" +"You can also generate your own self-signed certificates, but the process is " +"complicated and usually 🙅 **involves extra work for your contacts**." msgstr "" -#: ../system/translations.rst:82 +#: ../system/integrations/smime/prerequisites.rst:29 msgid "" -"If you want to revert a custom translation to original text, simply use the " -"appropriate action within the row of the overview table." +"Bear in mind that 🤝 **S/MIME only works if the other party is using it, too." +"**" msgstr "" -#: ../system/translations.rst:85 +#: ../system/integrations/smime/prerequisites.rst:32 +msgid "Certificate and Private Key Checks on Upload" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:34 msgid "" -"Depending on the type of the translation source, the action has a slightly " -"different name:" +"The certificate and public key validation is based on the ``X509v3`` " +"extensions." msgstr "" -#: ../system/translations.rst:88 -msgid "**Reset** for customized system translations" +#: ../system/integrations/smime/prerequisites.rst:49 +msgid "Uploading a *client certificate*?" msgstr "" -#: ../system/translations.rst:89 -msgid "**Remove** for customized local translations" +#: ../system/integrations/smime/prerequisites.rst:41 +msgid "The following attributes are required then:" msgstr "" -#: ../system/translations.rst:91 -msgid "" -"In both cases, the action will remove the customized translation after a " -"confirmation." +#: ../system/integrations/smime/prerequisites.rst:39 +msgid "Subject Alternative Name (at least one email address has to be present)" msgstr "" -#: ../system/translations.rst:None -msgid "Screenshot showing the location of the Remove action" +#: ../system/integrations/smime/prerequisites.rst:40 +msgid "Key Usage (``Digital Signature`` and/or ``Key Encipherment``)" msgstr "" -#: ../system/translations.rst:99 -msgid "Inline Translations" +#: ../system/integrations/smime/prerequisites.rst:41 +msgid "Public key algorithm (either ``RSA`` or ``EC``)" msgstr "" -#: ../system/translations.rst:101 +#: ../system/integrations/smime/prerequisites.rst:43 msgid "" -"If you prefer a more hands-on approach, you can activate the inline or on-" -"screen translation feature by pressing ``ctrl`` + ``alt`` + ``t`` at any " -"time and on any screen." +"The Extended Key Usage attribute is optional. If the certificate provides " +"the named attribute, than it must contain the value ``E-mail Protection``." msgstr "" -#: ../system/translations.rst:105 +#: ../system/integrations/smime/prerequisites.rst:46 msgid "" -"All customizable translation texts will be highlighted for you on the " -"screen. Just click into the highlighted area and update the text in place." +"Please note that any usable email adress has to be prefixed with ``email:`` " +"or ``rfc822:``." msgstr "" -#: ../system/translations.rst:None -msgid "Inline translation mode activated for the Overview screen" +#: ../system/integrations/smime/prerequisites.rst:49 +msgid "The named public key algorithms are mandatory for private keys as well." msgstr "" -#: ../system/translations.rst:112 +#: ../system/integrations/smime/prerequisites.rst:54 +msgid "Uploading a *CA certificate*?" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:52 msgid "" -"When finished editing, simply press ``ctrl`` + ``alt`` + ``t`` again to " -"deactivate." +"In the case of an uploaded CA certificate, providing the value ``CA:TRUE`` " +"in the attribute *Basic Contstraints*, the previously mentioned attributes " +"are not verified." msgstr "" -#: ../system/translations.rst:117 +#: ../system/integrations/smime/prerequisites.rst:56 msgid "" -"Even though it's available on any screen, the inline translation feature " -"requires admin permissions. It works only for the current language " -"selection. If you need to translate a different language, first change the " -"language in your :user-docs:`profile settings `." +"In general, the usage of any expired (``Not After``) or not yet valid (``Not " +"Before``) certificate is denied for outgoing emails." msgstr "" -#: ../system/variables.rst:2 -msgid "Variables" +#: ../system/integrations/smime/prerequisites.rst:59 +msgid "Example certificate:" msgstr "" -#: ../system/variables.rst:4 +#: ../system/integrations/smime/prerequisites.rst:85 msgid "" -"Please note that this is just an overview of available variables. It might " -"be incomplete or variables might not be available within some functions. If " -"you're missing variables or are not sure if something is not working as " -"expected, feel free to ask over at the `Community `_." +"Please note that Zammad will distrust senders by default. This means that " +"you're always required to provide certificate data, no matter if for signing " +"or encrypting." msgstr "" -#: ../system/variables.rst:10 -msgid "" -"Variables can be called by typing ``::`` (just like text modules in the " -"frontend), as long as you're in a supported text field within the backend. " -"Zammad will display all variables being available within this context and " -"replace it to the variable as soon as you selected an entry." +#: ../system/integrations/smime/prerequisites.rst:89 +msgid "This is by design and can't be adjusted." msgstr "" -#: ../system/variables.rst:15 +#: ../system/integrations/smime/troubleshooting.rst:4 msgid "" -"You have an empty field which you referenced and it appears as ``-``? That's " -"currently working as designed - you might want to ensure that these fields " -"always have a value." +"All of the system's latest S/MIME activity is displayed in the **Recent " +"Logs** section." msgstr "" -#: ../system/variables.rst:20 -msgid "Variable Categories" +#: ../system/integrations/smime/troubleshooting.rst:11 +msgid "Sample entries of in- and outgoing S/MIME related emails." msgstr "" -#: ../system/variables.rst:31 -msgid "Wait, What About Custom Objects?" +#: ../system/integrations/smime/troubleshooting.rst:11 +msgid "" +"Logs report the status and details of all mail, both incoming and outgoing, " +"that used signing/verification or encryption/decryption." msgstr "" -#: ../system/variables.rst:33 +#: ../system/integrations/smime/troubleshooting.rst:14 msgid "" -"Good point! Of course, we can't predict what objects you might create, but " -"we can give you a hint on how to put the puzzle together to get your custom " -"values." +"This log does **not** include email sent by :doc:`triggers ` or the :doc:`scheduler `. For those, check your " +"``production.log``." +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:20 +msgid "Common Issues" +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:30 +msgid "I received a signed/encrypted email before I set up S/MIME integration" msgstr "" -#: ../system/variables.rst:36 +#: ../system/integrations/smime/troubleshooting.rst:23 msgid "" -"For this, we'll talk about the inner part of the variable (so everything " -"within ``#{}``), please put the outer part around to have a valid variable. " -"The first part of the variable name consist of the object type. Currently " -"these are:" +"No problem. Once S/MIME has been enabled and the appropriate certificates " +"have been added, agents will be prompted to retry verification/decryption on " +"matching emails." msgstr "" -#: ../system/variables.rst:41 -msgid "Ticket (``ticket``)" +#: ../system/integrations/smime/troubleshooting.rst:0 +msgid "Screenshot of user prompt to retry decryption" msgstr "" -#: ../system/variables.rst:42 -msgid "User (``user``)" +#: ../system/integrations/smime/troubleshooting.rst:38 +msgid "The 🔒 **Encrypt** button is disabled" msgstr "" -#: ../system/variables.rst:43 -msgid "Organization (``organization``)" +#: ../system/integrations/smime/troubleshooting.rst:33 +msgid "Have you added the recipient's certificate?" msgstr "" -#: ../system/variables.rst:44 -msgid "Group (``group``)" +#: ../system/integrations/smime/troubleshooting.rst:34 +msgid "Are you sure the recipient's certificate is valid?" msgstr "" -#: ../system/variables.rst:46 -msgid "" -"The second part is the name of the object. This is the name you define " -"during object creation and can be found within the object menu at any time. " -"The first and second part of a variable is divided by a point, e.g.: " -"``ticket.number`` which will in total be ``#{ticket.number}``." +#: ../system/integrations/smime/troubleshooting.rst:35 +msgid "Have you checked your ``production.log`` for more details?" msgstr "" -#: ../system/variables.rst:51 +#: ../system/integrations/smime/troubleshooting.rst:37 msgid "" -"Now, in some situations it's possible that you'll need to use a third part. " -"The best example for such a situation would be a ``select`` or ``tree-" -"select`` field which will by default return the key value, not it's display " -"name. For this, just extend your variable with ``.value``. This will result " -"in ``#{ticket.select.value}``." +"If encryption doesn't work in the composer, it won't work in :doc:`triggers " +"` or the :doc:`scheduler ` either!" msgstr "" -#: ../system/variables.rst:60 -msgid "Using Translated Variables" +#: ../system/integrations/smime/troubleshooting.rst:42 +msgid "The ✅ **Sign** button is disabled" msgstr "" -#: ../system/variables.rst:62 +#: ../system/integrations/smime/troubleshooting.rst:41 msgid "" -"If you want to use a translated variable in triggers or schedulers, you can " -"extend the placeholder like this: ``#{t(ticket.state.name)}``. The ``t`` " -"tells Zammad to search for fitting translated strings. The used output " -"language is based on the system language of Zammad which you can set in the " -"admin panel under :doc:`/settings/branding` or based on the selected locale " -"in the trigger/scheduler edit dialog." +"Have you added **both the certificate and private key** for your " +"organization?" msgstr "" -#: ../system/variables.rst:69 +#: ../system/integrations/smime/troubleshooting.rst:42 msgid "" -"A possible use-case: you want to send your customers updates on tickets via " -"trigger or scheduler which should include the state of the ticket. Using the " -"default ``#{ticket.state.name}`` (without the translation flag ``t()``) " -"would lead to the output of the original (english) name of the state." +"Does the email address on the certificate match the email address of the " +"agent/group composing the email?" msgstr "" -#: ../system/variables.rst:75 -msgid "Date and Time Formatting" +#: ../system/integrations/smime/troubleshooting.rst:45 +msgid "Error: “Fingerprint already taken”" msgstr "" -#: ../system/variables.rst:77 -msgid "" -"The system (trigger/scheduler selected) locale and timezone predefines a " -"default format of date and timestamp. This format is customizable by using " -"the ``dt()`` method." +#: ../system/integrations/smime/troubleshooting.rst:45 +msgid "Are you sure you haven't added this certificate already?" msgstr "" -#: ../system/variables.rst:79 -msgid "The method arguments are as follows:" +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Error: “❌ invalid byte sequence in UTF-8”" msgstr "" -#: ../system/variables.rst:81 -msgid "The date or timestamp variable you want to format." +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Please ensure to provide PEM formatted certificate and keys." msgstr "" -#: ../system/variables.rst:82 -msgid "The output format string." +#: ../system/integrations/smime/troubleshooting.rst:49 +msgid "Did you check if the provided file is a valid certificate or key?" msgstr "" -#: ../system/variables.rst:83 -msgid "The timezone to apply (optional)." +#: ../system/integrations/zabbix.rst:2 +msgid "Zabbix Integration" msgstr "" -#: ../system/variables.rst:86 +#: ../system/integrations/zabbix.rst:5 msgid "" -"``#{dt(ticket.updated_at, \"%A %Y-%m-%d %H:%M in the office\", \"Europe/" -"Berlin\")}``" +"This guide describes how to integrate your Zabbix 5.4 installation with " +"Zammad using the Zabbix webhook feature. This guide will provide " +"instructions on setting up a media type, a user and an action in Zabbix." msgstr "" -#: ../system/variables.rst:87 -msgid "Monday, 2024-03-18 15:31 in the office" +#: ../system/integrations/zabbix.rst:12 +msgid "Zammad with enabled HTTP Token Authentication" msgstr "" -#: ../system/variables.rst:89 -msgid "" -"If you want to use our example, make sure to paste the string above without " -"formatting (``CTRL+Shift+v``), otherwise it won't work." +#: ../system/integrations/zabbix.rst:13 +msgid "Zabbix version 5.4 or higher" msgstr "" -#: ../system/variables.rst:93 -msgid "The following table lists available format directives:" +#: ../system/integrations/zabbix.rst:16 +msgid "Setting up a Zammad" msgstr "" -#: ../system/variables.rst:99 -msgid "Parameter" +#: ../system/integrations/zabbix.rst:18 +msgid "Enable **API Token Access** in Settings > System > API." msgstr "" -#: ../system/variables.rst:102 -msgid "``%Y``" +#: ../system/integrations/zabbix.rst:20 +msgid "" +"Create a **new user** for a Zabbix alerter with an **email address** and " +"create a personal user token with **ticket.agent** permissions." msgstr "" -#: ../system/variables.rst:103 -msgid "Year with 4 digits" +#: ../system/integrations/zabbix.rst:24 +msgid "Zabbix Webhook Configuration" msgstr "" -#: ../system/variables.rst:104 -msgid "Use ``%y`` for year with 2 digits" +#: ../system/integrations/zabbix.rst:27 +msgid "Create a Global Macro" msgstr "" -#: ../system/variables.rst:105 -msgid "``%m``" +#: ../system/integrations/zabbix.rst:29 +msgid "" +"Before setting up the **Webhook**, you need to setup the global macro " +"**{$ZABBIX.URL}**, which must contain the **URL** to the **Zabbix frontend**." msgstr "" -#: ../system/variables.rst:106 -msgid "Month of year (as number with zero-padding)" +#: ../system/integrations/zabbix.rst:33 +msgid "" +"In the **Administration** > **Media types** section, import the `Template`_." msgstr "" -#: ../system/variables.rst:107 -msgid "Use ``%-m`` for month without zero-padding" +#: ../system/integrations/zabbix.rst:38 +msgid "Open the added **Zammad** media type and set:" msgstr "" -#: ../system/variables.rst:108 -msgid "``%d``" +#: ../system/integrations/zabbix.rst:40 +msgid "**zammad\\_access\\_token** to the your **Personal User Token**" msgstr "" -#: ../system/variables.rst:109 -msgid "Day of month (as number with zero-padding)" +#: ../system/integrations/zabbix.rst:41 +msgid "" +"**zammad\\_url** to the **frontend URL** of your **Zammad** installation" msgstr "" -#: ../system/variables.rst:110 -msgid "Use ``%e`` for day without zero-padding" +#: ../system/integrations/zabbix.rst:43 +msgid "**zammad\\_customer** to your **Zammad user email**." msgstr "" -#: ../system/variables.rst:111 -msgid "``%H``" +#: ../system/integrations/zabbix.rst:44 +msgid "" +"**zammad\\_enable\\_tags** to **true** or **false** to enable or disable " +"trigger tags. **Important**: if you enable tag support, each tag is set with " +"a separate request." msgstr "" -#: ../system/variables.rst:112 -msgid "Hour of day in 24h notation with zero-padding" +#: ../system/integrations/zabbix.rst:48 +msgid "" +"If you want to prioritize issues according to **severity** values in Zabbix, " +"you can define mapping parameters:" msgstr "" -#: ../system/variables.rst:113 -msgid "Use ``%k`` for hour without zero-padding" +#: ../system/integrations/zabbix.rst:51 +msgid "**severity\\_**: Zammad priority ID" msgstr "" -#: ../system/variables.rst:114 -msgid "``%I``" +#: ../system/integrations/zabbix.rst:53 +msgid "Click the **Update** button to save the **Webhook** settings." msgstr "" -#: ../system/variables.rst:115 -msgid "Hour of day in 12h notation with zero-padding" +#: ../system/integrations/zabbix.rst:55 +msgid "" +"To receive notifications in **Zammad**, you need to create a **Zabbix user** " +"and add **Media** with the **Zammad** type." msgstr "" -#: ../system/variables.rst:116 +#: ../system/integrations/zabbix.rst:58 msgid "" -"Use ``%l`` for hour without zero-padding and ``%p`` / ``%P`` for meridian " -"indicator" +"For **Send to**: enter any text, as this value is not used, but is required." msgstr "" -#: ../system/variables.rst:117 -msgid "``%M``" +#: ../system/integrations/zabbix.rst:61 +msgid "" +"For more information, use the `Zabbix documentation `_." msgstr "" -#: ../system/variables.rst:118 -msgid "Minute of hour" +#: ../system/maintenance.rst:2 +msgid "Maintenance" msgstr "" -#: ../system/variables.rst:120 -msgid "``%S``" +#: ../system/maintenance.rst:4 +msgid "" +"Zammad comes with a maintenance mode that you can use for e.g. updating the " +"instance or changing settings while restricting availability and functions." msgstr "" -#: ../system/variables.rst:121 -msgid "Second of Minute" +#: ../system/maintenance.rst:13 +msgid "Mode" msgstr "" -#: ../system/variables.rst:123 -msgid "``%A``" +#: ../system/maintenance.rst:8 +msgid "The mode setting allows you to enable or disable the maintenance mode." msgstr "" -#: ../system/variables.rst:124 -msgid "Weekday name" +#: ../system/maintenance.rst:10 +msgid "Defaults to *off*." msgstr "" -#: ../system/variables.rst:125 -msgid "Use ``%a`` for abbreviated name or ``%^A`` for uppercase name" +#: ../system/maintenance.rst:12 +msgid "" +"The maintenance mode will restrict access to administrative roles only. This " +"means agents and customers are logged off." msgstr "" -#: ../system/variables.rst:126 -msgid "``%B``" +#: ../system/maintenance.rst:23 +msgid "@Login" msgstr "" -#: ../system/variables.rst:127 -msgid "Month name" +#: ../system/maintenance.rst:16 +msgid "" +"This setting allows you to provide a login message within a green banner " +"above the login screen. Click into the green banner in the settings page to " +"adjust your message. To activate the message, activate the *@Login* setting." msgstr "" -#: ../system/variables.rst:128 -msgid "Use ``%b`` for abbreviated name" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing the default login message within the\n" +"settings page" msgstr "" -#: ../system/variables.rst:129 -msgid "``%U``" +#: ../system/maintenance.rst:26 +msgid "" +"Send an informative message to **all active sessions**. This comes handy to " +"inform your agents e.g. about mayor outages or to force reloads after " +"configuration changes." msgstr "" -#: ../system/variables.rst:130 -msgid "Week number of current year" +#: ../system/maintenance.rst:31 +msgid "This is the messages title (slightly bigger than the normal message)." msgstr "" -#: ../system/variables.rst:131 -msgid "Use ``%W`` for a different calculation method" +#: ../system/maintenance.rst:34 +msgid "The text you want to provide to your logged in sessions." msgstr "" -#: ../system/variables.rst:134 +#: ../system/maintenance.rst:39 +msgid "Reload application" +msgstr "" + +#: ../system/maintenance.rst:37 msgid "" -"We support the known format directives for the Ruby built-in method " -"``strftime`` of the ``DateTime`` class. For more information, see `here " -"`_." +"Selecting this option will change the message acceptance button from *Close* " +"(with nothing happening) to *Continue session*, which forces the application " +"to reload." msgstr "" -#: ../system/variables/article.rst:2 -msgid "Articles" +#: ../system/maintenance.rst:43 +msgid "" +"If you have customers that are logged in to Zammad, they'll also be notified " +"if they're active in that moment." msgstr "" -#: ../system/variables/article.rst:4 ../system/variables/config.rst:4 -#: ../system/variables/current-user.rst:4 ../system/variables/ticket.rst:4 +#: ../system/maintenance.rst:48 +msgid "Example without reload application" +msgstr "" + +#: ../system/maintenance.rst:52 msgid "" -"If you're missing variables or are not sure if something is not working as " -"expected, feel free to ask over at the `Community `_." +"Message setting within Zammad's admin settings without ticket reload " +"application setting." msgstr "" -#: ../system/variables/article.rst:6 +#: ../system/maintenance.rst:0 msgid "" -"Below you can find all available ticket article-based variables within " -"Zammad. These can be called via Triggers for example. If you're unsure if " -"Zammad does support variables at the point you're at, you can try to type " -"``::`` to check." +"Screenshot showing the send message settings without ticket\n" +"reload application set" msgstr "" -#: ../system/variables/article.rst:9 ../system/variables/config.rst:9 -#: ../system/variables/ticket.rst:9 +#: ../system/maintenance.rst:61 ../system/maintenance.rst:85 msgid "" -"The below list gives you an example what kind of data you can expect, it's " -"not intended to explain the data itself." +"The modal all other active sessions will see upon pressing *Send to clients*." msgstr "" -#: ../system/variables/article.rst:11 -msgid "Article Variables" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing modal caused by maintenance's message\n" +"without reload application ticket" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "name" +#: ../system/maintenance.rst:72 +msgid "Example with reload application" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "variable" +#: ../system/maintenance.rst:76 +msgid "" +"Message setting within Zammad's admin settings with ticket reload " +"application setting." msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "example" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing the send message settings with ticket\n" +"reload application set" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Web" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing modal caused by maintenance's message\n" +"with reload application ticket" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.web}``" +#: ../system/monitoring.rst:2 +msgid "Monitoring" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``https://zammad.com`` or empty if not set in user object" +#: ../system/monitoring.rst:4 +msgid "" +"This function is only available in self hosted instances. If you use Zammad " +"in our cloud, we are monitoring the system on our own and take steps to fix " +"potential problems directly." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > VIP" +#: ../system/monitoring.rst:11 +msgid "" +"On the monitoring page, you can see the current health state of Zammad under " +"\"*Current Status*\" at the bottom. This can be useful if you want to have a " +"look if everything is up and running. As an example, you could have a look " +"in the monitoring when you assume that some emails aren't processed from " +"Zammad." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.vip}``" +#: ../system/monitoring.rst:17 +msgid "**Can't receive an email and the monitoring response is \"healthy\"?**" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -msgid "``true`` or ``false``" +#: ../system/monitoring.rst:19 +msgid "" +"Zammad will just inform you about unprocessable emails. This is not the case " +"for oversized emails. You can adjust the maximum email size in :doc:`../" +"channels/email/settings`." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Phone" +#: ../system/monitoring.rst:24 +msgid "Monitoring API" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.phone}``" +#: ../system/monitoring.rst:26 +msgid "" +"Beside the indication in the monitoring page, you can also use an external " +"monitoring tool to monitor Zammad's health. To request the health of Zammad, " +"you need to provide the API key (token) to the external monitoring tool. You " +"can copy the token from the \"*Current Token*\" field as well as the whole " +"API endpoint of your system (\"*Health Check*\" field), in which the API " +"token is already included." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``+4930123456789`` or empty if not set in user object" +#: ../system/monitoring.rst:37 +msgid "Screenshot showing Current Token and Health Check" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Note" +#: ../system/monitoring.rst:37 +msgid "Screenshot showing Token and Health Check" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.note}``" +#: ../system/monitoring.rst:39 +msgid "" +"In addition to that, you can reset the auto-generated token to make sure " +"that already configured monitoring systems won't work anymore. So, please " +"use this \"*Reset*\" button only if you know what you do!" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Some note about user`` or empty if not set in user object" +#: ../system/monitoring.rst:44 +msgid "Example Output" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Mobile" +#: ../system/monitoring.rst:0 +msgid "No issues found" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.mobile}``" +#: ../system/monitoring.rst:48 ../system/monitoring.rst:60 +msgid "**Indicator in Zammad**:" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Login" +#: ../system/monitoring.rst:0 +msgid "Screenshot showing monitoring with no issues" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.login}``" +#: ../system/monitoring.rst:54 ../system/monitoring.rst:66 +msgid "**API response**::" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -#: ../system/variables/ticket.rst:1 -msgid "``jdoe``" +#: ../system/monitoring.rst:0 +msgid "Issues were found" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Lastname" +#: ../system/monitoring.rst:0 +msgid "Screenshot showing monitoring with issues" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.lastname}``" +#: ../system/objects.rst:2 +msgid "Objects" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -#: ../system/variables/ticket.rst:1 -msgid "``Doe`` or empty if not set" +#: ../system/objects.rst:4 +msgid "" +"In Zammad you can add your own fields to tickets, users, organizations and " +"even groups (these are called \"objects\"). This can be useful if you need " +"to add further information to a ticket or any other object in Zammad and the " +"information doesn't fit in any existing field." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Firstname" +#: ../system/objects.rst:11 +msgid "" +"Try to avoid deleting attributes (and disable them instead) as Zammad might " +"run into unexpected conditions if they are referenced somewhere." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.firstname}``" +#: ../system/objects.rst:16 +msgid "" +"Here's an overview of object attributes. On the upper right you can add new " +"attributes. By default, there will be no custom fields - standard attributes " +"will be grayed out, you can't delete or change those. You can edit custom " +"attributes (they are displayed in black font and have a trash bin on the " +"right side) just by clicking on them." msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "``Joe`` or empty if not set" +#: ../system/objects.rst:24 +msgid "" +"Attributes you add to Zammad, no matter if they have default values or not, " +"will not update existing information. This means a new ticket field " +"technically will be empty unless you populate it." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Fax" +#: ../system/objects.rst:28 +msgid "" +"Especially in ticket scope this also means that newly added attributes will " +"be indicated as \"changed\" to agents that view the ticket. This may " +"interfere with Zammad's tabs behavior." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.fax}``" +#: ../system/objects.rst:40 +msgid "Ordering Attributes" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Email" +#: ../system/objects.rst:42 +msgid "" +"Since Zammad introduced :doc:`/system/core-workflows` the need to have a " +"custom positioning for attributes has become more important than ever." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.email}``" +#: ../system/objects.rst:45 +msgid "" +"To adjust the position of such an attribute, simply click on the attribute " +"entry in question, scroll down and adjust the position number. Please note " +"that you cannot change the positioning of default attributes." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``jdoe@example.com``" +#: ../system/objects.rst:49 +msgid "" +"In case two attributes have the same position value, Zammad will sort " +"alphabetically by name automatically." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Department" +#: ../system/objects.rst:None +msgid "" +"Screenshot showing custom attribute entries ordered in between default ones" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.department}``" +#: ../system/objects.rst:56 +msgid "Updating Database After Adding or Editing Attributes" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Sales`` or empty if not set in user object" +#: ../system/objects.rst:58 +msgid "" +"When adding or changing attributes, Zammad will not apply the changes " +"instantly, but instead shows you the changed attributes first. If you're " +"ready to go, just click on \"Update database\" to apply the changes to " +"Zammad. If you made a mistake or just want to discard your changes, click " +"\"Discard changes\"." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Address" +#: ../system/objects.rst:64 +msgid "" +"After applying the changes with \"Update Database\", a restart of Zammad is " +"**mandatory**. If you don't perform it, you may experience unexpected " +"behavior or even errors. You may want to do this kind of configuration " +"during maintenance windows." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.address}``" +#: ../system/objects.rst:72 +msgid "" +"Changes on objects require you to update the database to apply these changes." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Some street 1, 12345 Berlin`` or empty if not set in user object" +#: ../system/objects.rst:75 +msgid "**🤓 Service restarts can be automated**" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated" +#: ../system/objects.rst:0 +msgid "Hosted environments automatically restart for you." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_at}``" +#: ../system/objects.rst:0 +msgid "" +"If you're using a self-hosted installation you can use :docs:`environment " +"variables `" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``2019-10-08 15:24:47 UTC``" +#: ../system/objects.rst:82 +msgid "System Attributes" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Type > Name" +#: ../system/objects.rst:84 +msgid "" +"Zammad comes with pre-configured attributes. Some of them can't be edited " +"via UI (or at all). This is required for proper operation of Zammad and not " +"a bug." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.type.name}``" +#: ../system/objects.rst:90 +msgid "Ticket State" msgstr "" -#: ../system/variables/article.rst:1 +#: ../system/objects.rst:92 msgid "" -"``email`` (`list of article types `_)" +"If the pre-configured states aren't enough for you or you want to change " +"them, you can do so by clicking on the cogwheel icon in the state row in the " +"ticket tab. But you should be careful when changing pre-configured states. " +"This can lead to unwanted behavior in some cases." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > To" +#: ../system/objects.rst:None +msgid "Screenshot showing highlighted ticket state attribute" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.to}``" +#: ../system/objects.rst:122 +msgid "Handling of states" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``helpdesk@example.com``" +#: ../system/objects.rst:102 +msgid "" +"In the state configuration screen, you can add new states, disable states or " +"change states." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > TicketID" +#: ../system/objects.rst:0 +msgid "Screenshot showing table of default ticket states" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.ticket_id}``" +#: ../system/objects.rst:110 +msgid "" +"To add a new state, click on the \"New Ticket State\" button in the top " +"right corner. To change an existing state, simply click on the affected " +"state. This opens an edit dialog." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``1`` (not ticket number)" +#: ../system/objects.rst:114 +msgid "" +"You can also clone a state or set them to \"Default for new tickets\" or " +"\"Default for follow-ups\" by clicking on the ⁝ action button and select the " +"desired function." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Subject" +#: ../system/objects.rst:118 +msgid "" +"*Default for new tickets* means that this state is used for every newly " +"created ticket." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.subject}``" +#: ../system/objects.rst:121 +msgid "" +"*Default for follow-ups* means that this state is used if the ticket is re-" +"opened after it was closed." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``My amazing subject``" +#: ../system/objects.rst:171 +msgid "Ticket state in detail" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Sender > Name" +#: ../system/objects.rst:125 +msgid "" +"Below you can find a description for each field and option. Please head over " +"to the :ref:`example ` to see the edit dialog." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.sender.name}``" +#: ../system/objects.rst:129 +msgid "" +"This is the name of the state and what you and your agents are seeing when " +"choosing a state somewhere (e.g. in tickets, trigger configuration)." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Customer``, ``Agent`` or ``System``" +#: ../system/objects.rst:137 +msgid "" +"There are different state types you can choose from. By default, Zammad " +"comes with one state per state type." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Visibility" +#: ../system/objects.rst:140 +msgid "" +"**new**: for states for tickets that are new and it hasn't been worked on " +"them" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.internal}``" +#: ../system/objects.rst:142 +msgid "" +"**open**: for states for tickets that are in progress and agents are working " +"on them" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``false`` or ``true`` (false if not internal)" +#: ../system/objects.rst:144 +msgid "**merged**: for states for tickets that are merged with other tickets" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > From" +#: ../system/objects.rst:145 +msgid "" +"**pending reminder**: for states for tickets that are in progress and you " +"want to set a reminder. (default example: *pending reminder*)" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.from}``" +#: ../system/objects.rst:147 +msgid "" +"**pending action**: for states for tickets that are waiting for a specified " +"time and then change their state (default example: *pending close*)" msgstr "" -#: ../system/variables/article.rst:1 +#: ../system/objects.rst:150 msgid "" -"``Joe Doe `` may differ, depends on ``FROM`` of send mail" +"**closed**: for states for tickets that are finished and do not need to be " +"processed further" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Web" +#: ../system/objects.rst:153 +msgid "" +"⚠️ Choosing the correct state type is important! If you are in doubt, have a " +"look on the default states and their types!" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.web}``" +#: ../system/objects.rst:158 +msgid "Ignore escalation" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > VIP" +#: ../system/objects.rst:157 +msgid "" +"Here you can define whether tickets of this state will count to escalation " +"time or not." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.vip}``" +#: ../system/objects.rst:161 +msgid "" +"You can create a note for the state to inform other admins about the state. " +"This has no effect on tickets." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Phone" +#: ../system/objects.rst:165 +msgid "Set the state to *active* or *inactive*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.phone}``" +#: ../system/objects.rst:167 +msgid "" +"it is technically possible to set all states to inactive. To keep Zammad " +"working in such a case, the inactive flag of one of the states is ignored." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Note" +#: ../system/objects.rst:194 +msgid "Ticket state example" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.note}``" +#: ../system/objects.rst:174 +msgid "" +"Let's assume we want to create a new state which indicates that the ticket " +"has to wait for a response of a third party (e.g. service contractor or " +"manufacturer) and we want to to be able to set a reminder." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Mobile" +#: ../system/objects.rst:178 +msgid "" +"First we give the new state a proper name. In this example we call it " +"\"waiting for manufacturer\"." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.mobile}``" +#: ../system/objects.rst:181 +msgid "" +"As state type we choose \"pending reminder\". This indicates that the ticket " +"is still open and we can set a reminder. This reminder can be useful if our " +"manufacturer sometimes isn't responding or we want to remind him to give us " +"an answer." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Login" +#: ../system/objects.rst:186 +msgid "" +"We choose \"no\" for \"ignore escalation\" because we want to escalate the " +"tickets even if we are waiting on the manufacturer's feedback." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.login}``" +#: ../system/objects.rst:189 +msgid "The **result** in the creation dialog will look like this:" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Lastname" +#: ../system/objects.rst:0 +msgid "Screenshot showing ticket state creation dialog with example" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.lastname}``" +#: ../system/objects.rst:199 +msgid "Ticket Priority" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Firstname" +#: ../system/objects.rst:201 +msgid "" +"If the pre-configured priorities aren't enough for you or you want to change " +"them, you can do so by clicking on the cogwheel icon in the priority row in " +"the ticket tab:" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.firstname}``" +#: ../system/objects.rst:None +msgid "Screenshot showing highlighted ticket priority attribute" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Fax" +#: ../system/objects.rst:226 +msgid "Handling of priorities" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.fax}``" +#: ../system/objects.rst:210 +msgid "" +"In the priority configuration screen, you can add new priorities, disable " +"priorities or change priorities." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Email" +#: ../system/objects.rst:0 +msgid "Screenshot showing table of default ticket priorities" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.email}``" +#: ../system/objects.rst:218 +msgid "" +"To add a new priority, click on the \"New Priority\" button in the top right " +"corner. To change an existing priority, simply click on the affected " +"priority. This opens an edit dialog." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Department" +#: ../system/objects.rst:222 +msgid "" +"You can also clone a priority or set them to \"Default for new tickets\" by " +"clicking on the ⁝ action button and select the desired function." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.department}``" +#: ../system/objects.rst:225 +msgid "" +"*Default for new tickets* means that this priority is used for every newly " +"created ticket." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Address" +#: ../system/objects.rst:248 +msgid "Priorities in detail" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.address}``" +#: ../system/objects.rst:229 +msgid "Below you can find a description for each field and option." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created" +#: ../system/objects.rst:232 +msgid "" +"This is the name of the priority and what you and your agents are seeing " +"when choosing a priority somewhere (e.g. in tickets, trigger configuration)." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_at}``" +#: ../system/objects.rst:242 +msgid "Highlight color" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Cc" +#: ../system/objects.rst:237 +msgid "" +"Switch between *Low priority* (light blue), *High priority* (red) and - " +"(default). This affects the displayed color for ticket titles in overviews." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.cc}``" +#: ../system/objects.rst:241 +msgid "The color options are currently limited to the mentioned options." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``jdoe@example.com, company@example.com``" +#: ../system/objects.rst:245 +msgid "" +"You can create a note for the priority to inform other admins about the " +"priority. This has no effect on tickets." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Text" +#: ../system/objects.rst:249 +msgid "Set the priority to *active* or *inactive*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.body}``" +#: ../system/objects/external-data-source-example.rst:2 +msgid "External Data Source" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Test`` without formatting (plain)" +#: ../system/objects/external-data-source-example.rst:4 +msgid "" +"We assume you already had a look on :doc:`types` where you can find a " +"description of the individual fields." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article Text as HTML (not referenced)" +#: ../system/objects/external-data-source-example.rst:7 +msgid "" +"To reproduce this example, choose a category you want to add a custom field, " +"click on *New Attribute* and select *External data source field* under " +"*Format*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.body_as_html}``" +#: ../system/objects/external-data-source-example.rst:11 +msgid "" +"Our example story is to fetch data from an external product database. We " +"want to add our products to the tickets so that the products can be searched " +"and chosen from a list and also create a link to the product website." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Test`` with formatting" +#: ../system/objects/external-data-source-example.rst:16 +msgid "Base configuration" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "Ticket > Article#" +#: ../system/objects/external-data-source-example.rst:None +msgid "Initial steps to configure external data source object type" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "``#{ticket.article_count}``" +#: ../system/objects/external-data-source-example.rst:25 +msgid "Name: *product*" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``1`` number of ticket articles" +#: ../system/objects/external-data-source-example.rst:26 +msgid "Display: *Product*" msgstr "" -#: ../system/variables/config.rst:2 -msgid "Config" +#: ../system/objects/external-data-source-example.rst:29 +msgid "External data source configuration" msgstr "" -#: ../system/variables/config.rst:6 +#: ../system/objects/external-data-source-example.rst:31 msgid "" -"Below you'll find config related variables. These hold useful configuration " -"information that you can use within e.g. triggers to show necessary " -"information to your customer." +"First, enter the search URL making sure it contains ``#{search.term}`` as a " +"parameter:" msgstr "" -#: ../system/variables/config.rst:11 -msgid "Config Variables" +#: ../system/objects/external-data-source-example.rst:34 +msgid "**Example:** ``https://dummyjson.com/products/search?q=#{search.term}``" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Fully Qualified Domain Name" +#: ../system/objects/external-data-source-example.rst:36 +msgid "" +"After that, head down to the preview section and enter a search input for " +"the external data source." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.fqdn}``" +#: ../system/objects/external-data-source-example.rst:39 +msgid "**Example:** ``mac``" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``zammad.example.com``" +#: ../system/objects/external-data-source-example.rst:41 +msgid "Then you can find a preview of the response data below:" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Ticket Hook" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of JSON response based on search term" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.ticket_hook}``" +#: ../system/objects/external-data-source-example.rst:48 +msgid "" +"We recommend using the preview to have a look on the structure. There is a " +"top-level element called ``products``. One level below, you can find the " +"attributes ``id`` and ``title``." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``Ticket#``" +#: ../system/objects/external-data-source-example.rst:52 +msgid "**Search result response based on search from example:**" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > HTTP type" +#: ../system/objects/external-data-source-example.rst:119 +msgid "" +"To tell the remote system that the desired data is located below the " +"``products`` level, you have to put it in the field *Search result list key*." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.http_type}``" +#: ../system/objects/external-data-source-example.rst:122 +msgid "" +"After inserting ``products`` in the mentioned field, you get an extended " +"preview. You can find an additional box *Search result list* with a JSON " +"structure. This is the same response as before but stripped from the upper " +"``products`` element by the external data source." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``https`` or ``http``" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of JSON response search result list" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > SystemID" +#: ../system/objects/external-data-source-example.rst:132 +msgid "" +"Now you need to provide the keys for the search result values and labels. As " +"already mentioned, we are looking for the ``id`` and the ``title`` of our " +"products. If you haven't already, it is now a good time to look at the " +"preview of the *Search result list*." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.system_id}``" +#: ../system/objects/external-data-source-example.rst:197 +msgid "" +"After locating our two keys, we insert them in *search result value key* " +"(``id``) and in *Search result label key* (``title``)." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``31`` (value between 1 and 99)" +#: ../system/objects/external-data-source-example.rst:200 +msgid "" +"Basically, we configured the external data source already and we can see a " +"table in the preview section:" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Organization" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of product table based on search term" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.organization}``" +#: ../system/objects/external-data-source-example.rst:208 +msgid "" +"According to our example story, now just the *Link template* is missing." msgstr "" -#: ../system/variables/config.rst:1 +#: ../system/objects/external-data-source-example.rst:210 msgid "" -"``Zammad GmbH`` value set in `Branding `_" +"Please note that this is an optional feature. If you don't want to use such " +"links, of course you don't have to configure it." msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Product Name" +#: ../system/objects/external-data-source-example.rst:213 +msgid "" +"We can add now an address where additional product information can be found." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.product_name}``" +#: ../system/objects/external-data-source-example.rst:215 +msgid "Example: ``https://your_domain.com/q=#{ticket.product}``" msgstr "" -#: ../system/variables/config.rst:1 -msgid "" -"``Helpdesk`` value set in `Branding `_" +#: ../system/objects/external-data-source-example.rst:217 +msgid "In the example, the parameter means:" +msgstr "" + +#: ../system/objects/external-data-source-example.rst:219 +msgid "``#{}``: \"Frame\" for the insertion of information" msgstr "" -#: ../system/variables/current-user.rst:2 -msgid "Current User" +#: ../system/objects/external-data-source-example.rst:220 +msgid "``ticket``: object level, where you create your custom object" msgstr "" -#: ../system/variables/current-user.rst:6 -msgid "" -"Current user variables always return values of the current user that caused " -"e.g. a trigger to run." +#: ../system/objects/external-data-source-example.rst:221 +msgid "``product``: name of the (custom) object" msgstr "" -#: ../system/variables/current-user.rst:8 +#: ../system/objects/external-data-source-example.rst:223 msgid "" -"Due to the above fact, these variables are often not (yet) set or available " -"for usage." +"After configuring your *Link template*, there will be another column in the " +"preview. Hovering on the icons in the *Link* column will show you where it " +"forwards you." msgstr "" -#: ../system/variables/current-user.rst:10 +#: ../system/objects/external-data-source-example.rst:232 msgid "" -"In situations where e.g. schedulers or triggers run, this most likely is " -"nothing you want to use." -msgstr "" - -#: ../system/variables/current-user.rst:13 -msgid "Current User Variables" +"In our example, one of the links looks like: https://your_domain.com/q=6, " +"where the 6 is the product id." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Web" +#: ../system/objects/external-data-source-example.rst:235 +msgid "You can find more information regarding the URL in :doc:`types`." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.web}``" +#: ../system/objects/includes/adding-values-hint.include.rst:3 +msgid "" +"Adding values can be tricky for first timers, don't forget to press \"➕ " +"Add\" after typing your values. Otherwise you may loose a value." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``https://zammad.org`` or empty if not set" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:1 +#: ../system/objects/includes/reposition-values.include.rst:1 +msgid "**↕️ This field type allows the positioning of its values ↔️**" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > VIP" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:3 +msgid "" +"In order to re-arrange the field values, first edit the field. Then you can " +"use ☰ to drag the values in question to the correct position. If you want to " +"change the layer depth, double click on ☰. With it you can cycle through the " +"available layers." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.vip}``" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:8 +msgid "When you're ready, submit your changes to save the object attribute." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``false`` or ``true``" +#: :0 ../system/objects/types.rst:0 +msgid "" +"Screencast showing how to re-position values on tree select like\n" +"fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Web" +#: ../system/objects/includes/reposition-values.include.rst:3 +msgid "" +"In order to re-arrange the field values, edit the field and scroll below the " +"values. Make sure to tick the option \"Use custom option sort\"." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.web}``" +#: ../system/objects/includes/reposition-values.include.rst:8 +msgid "" +"If you do not tick this field, all manual positioning you did above will be " +"lost upon saving! ☠️" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > VIP" +#: ../system/objects/includes/reposition-values.include.rst:11 +msgid "" +"Now use ☰ to drag the values in question to the correct position. When " +"you're ready, submit your changes to save the object attribute." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.vip}``" +#: :0 ../system/objects/types.rst:0 +msgid "Screencast showing how to re-position values" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Phone" +#: ../system/objects/includes/url-template-hint.include.rst:3 +msgid "" +"This field allows using :ref:`URL fields (Link Templates) `." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.phone}``" +#: ../system/objects/permissions.rst:2 +msgid "Attribute Permissions" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``004930123456789`` or empty if not set" +#: ../system/objects/permissions.rst:7 +msgid "" +"In the object attributes configuration you can define if a field is shown " +"and if the input in the field is mandatory, separated by different screens " +"and for different :doc:`roles/permissions `." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Note" +#: ../system/objects/permissions.rst:17 +msgid "Screenshot shows object attribute permission table" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.note}``" +#: ../system/objects/permissions.rst:17 +msgid "" +"Some of the possible permissions and screen options for a user object " +"attribute." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Some note to this user`` or empty if not set" +#: ../system/objects/permissions.rst:19 +msgid "" +"Based on the object context (ticket, agent, organization, user), the " +"selectable roles (to be precise: the required permissions) and screens " +"differ. Be aware that these settings aren't affecting data creation via " +"other channels than the UI." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Mobile" +#: ../system/objects/permissions.rst:24 +msgid "" +"If you want to have further customization possibilities, you should have a " +"look at the :doc:`core workflows `." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.mobile}``" +#: ../system/objects/permissions.rst:28 +msgid "Screens" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``0049176123456789`` or empty if not set" +#: ../system/objects/permissions.rst:30 +msgid "" +"In the table below you can find an overview about the different permissions " +"and the available screens Zammad distinguishes between." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Login" +#: ../system/objects/permissions.rst:37 +msgid "Screen" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.login}``" +#: ../system/objects/permissions.rst:38 +msgid "Available for" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Lastname" +#: ../system/objects/permissions.rst:40 +msgid "create" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.lastname}``" +#: ../system/objects/permissions.rst:41 ../system/objects/permissions.rst:52 +#: ../system/objects/permissions.rst:59 ../system/objects/permissions.rst:73 +msgid "admin.user" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Firstname" +#: ../system/objects/permissions.rst:42 ../system/objects/permissions.rst:53 +#: ../system/objects/permissions.rst:60 +msgid "admin.organization" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.firstname}``" +#: ../system/objects/permissions.rst:43 ../system/objects/permissions.rst:54 +#: ../system/objects/permissions.rst:61 +msgid "admin.group" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``John`` or empty if not set" +#: ../system/objects/permissions.rst:44 +msgid "Creation dialog for not yet existing data" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Fax" +#: ../system/objects/permissions.rst:45 +msgid "create_middle" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.fax}``" +#: ../system/objects/permissions.rst:46 ../system/objects/permissions.rst:50 +#: ../system/objects/permissions.rst:57 ../system/objects/permissions.rst:66 +#: ../system/objects/permissions.rst:70 +msgid "ticket.customer" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``004930123464789`` or empty if not set" +#: ../system/objects/permissions.rst:47 ../system/objects/permissions.rst:51 +#: ../system/objects/permissions.rst:58 ../system/objects/permissions.rst:69 +msgid "ticket.agent" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Email" +#: ../system/objects/permissions.rst:48 +msgid "Ticket create dialog (middle section)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.email}``" +#: ../system/objects/permissions.rst:49 +msgid "edit" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``jdoe@customer.tld``" +#: ../system/objects/permissions.rst:55 +msgid "Editing dialog for already existing data" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Department" +#: ../system/objects/permissions.rst:56 +msgid "view" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.department}``" +#: ../system/objects/permissions.rst:62 +msgid "View-only dialog for already existing data" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Sales`` or empty if not set" +#: ../system/objects/permissions.rst:64 +msgid "(e.g. user or organization from search)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Avatar" +#: ../system/objects/permissions.rst:65 +msgid "signup" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.avatar(60,60)}``" +#: ../system/objects/permissions.rst:67 +msgid "Sign-up screen for new customers" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "avatar picture with width and height in pixel (e.g. 60,60)" +#: ../system/objects/permissions.rst:68 +msgid "invite_customer" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Address" +#: ../system/objects/permissions.rst:71 +msgid "" +"Customer invitation screen (from :doc:`First Steps ` area)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.address}``" +#: ../system/objects/permissions.rst:72 +msgid "invite_agent" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Some street 1, 12345 Berlin`` or empty if not set" +#: ../system/objects/permissions.rst:74 +msgid "" +"Agent invitation screen (from :doc:`First Steps ` area)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated at" +#: ../system/objects/permissions.rst:78 +msgid "Screen Options" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_at}``" +#: ../system/objects/permissions.rst:80 +msgid "" +"For the different screens you can select \"show\" and \"required\" options." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC``" +#: ../system/objects/permissions.rst:82 +msgid "**shown:** Show (check) or hide (uncheck) a field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Phone" +#: ../system/objects/permissions.rst:83 +msgid "" +"**required:** Set a field to mandatory (check). Forces users (via UI and " +"API) to populate the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.phone}``" +#: ../system/objects/types.rst:7 +msgid "Example external data source" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Shared organization" +#: ../system/objects/types.rst:2 +msgid "Attribute types" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.shared}``" +#: ../system/objects/types.rst:4 +msgid "" +"When adding a new object attribute, you can choose between the following " +"attribute types." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Note" +#: ../system/objects/types.rst:14 +msgid "" +"You cannot change the attribute format / type as soon as it is applied. If " +"you no longer need an object attribute, consider disabling it instead of " +"removing." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.note}``" +#: ../system/objects/types.rst:18 +msgid "**What about the translation of my attributes?**" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``A note to the organization of the user`` or empty if not set" +#: ../system/objects/types.rst:20 +msgid "" +"For some attribute types you can decide if they should be translatable or " +"not. To be precise, it works only for the selectable fields because the " +"possible choices are known and limited. For the following attribute types, " +"you can set the translatable flag:" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Name" +#: ../system/objects/types.rst:25 +msgid "*Boolean field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.name}``" +#: ../system/objects/types.rst:26 +msgid "*Single selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``Zammad GmbH``" +#: ../system/objects/types.rst:27 +msgid "*Multiple selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Domain based assignment" +#: ../system/objects/types.rst:28 +msgid "*Single tree selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.domain_assignment}``" +#: ../system/objects/types.rst:29 +msgid "*Multiple tree selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Domain" +#: ../system/objects/types.rst:31 +msgid "" +"For these types, you can find an additional field *Translate field contents*:" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.domain}``" +#: ../system/objects/types.rst:0 +msgid "Screenshot showing translatable attribute types" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``zammad.com`` or empty if not set" +#: ../system/objects/types.rst:38 +msgid "Screenshot with example of translatable attribute type" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > VIP" +#: ../system/objects/types.rst:45 +msgid "Boolean field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.vip}``" +#: ../system/objects/types.rst:41 +msgid "" +"Provides a drop-down field with display values for ``true`` and ``false``. " +"Setting a default is mandatory." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Note" +#: ../system/objects/types.rst:0 +msgid "Available settings for Boolean fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.note}``" +#: ../system/objects/types.rst:55 +msgid "Date field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Mobile" +#: ../system/objects/types.rst:48 +msgid "Provides a date picker field and does not allow default values." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.mobile}``" +#: ../system/objects/types.rst:52 +msgid "Default time diff (hours)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Login" +#: ../system/objects/types.rst:51 +msgid "" +"This setting helps the user by highlighting the day from now plus the " +"provided value. It *does not* pre-fill the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.login}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Date fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Lastname" +#: ../system/objects/types.rst:73 +msgid "Date & time field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.lastname}``" +#: ../system/objects/types.rst:58 +msgid "Provides a date and time picker – does not allow default values" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Firstname" +#: ../system/objects/types.rst:62 +msgid "Allow future" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.firstname}``" +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the future." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Fax" +#: ../system/objects/types.rst:66 +msgid "Allow past" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.fax}``" +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the past." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Email" +#: ../system/objects/types.rst:70 +msgid "Default time diff (minutes)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.email}``" +#: ../system/objects/types.rst:69 +msgid "" +"This setting helps the user by highlighting the day from now plus the " +"provided value. It does not pre-fill the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Department" +#: ../system/objects/types.rst:0 +msgid "Available settings for Date & time fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.department}``" +#: ../system/objects/types.rst:86 +msgid "Integer field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Web" +#: ../system/objects/types.rst:76 +msgid "" +"Provides an input field that allows integer usage only. You may define a " +"default value. You cannot enforce comma separation." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.web}``" +#: ../system/objects/types.rst:80 +msgid "Minimal" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > VIP" +#: ../system/objects/types.rst:80 +msgid "The minimal value the field accepts." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.vip}``" +#: ../system/objects/types.rst:83 +msgid "Maximal" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Phone" +#: ../system/objects/types.rst:83 +msgid "The maximum value the field accepts." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.phone}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Integer fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Note" +#: ../system/objects/types.rst:99 +msgid "Multiple selection field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.note}``" +#: ../system/objects/types.rst:89 +msgid "" +"Provides a selection field that allows the selection of one or more out of " +"several. This field does allow setting a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Mobile" +#: ../system/objects/types.rst:0 +msgid "Available settings for Multiple selection fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.mobile}``" +#: ../system/objects/types.rst:112 +msgid "Single selection field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Login" +#: ../system/objects/types.rst:102 +msgid "" +"Provides a drop-down field that allows selection of one value out of " +"several. This field does allow setting a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.login}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Single selection fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Lastname" +#: ../system/objects/types.rst:142 +msgid "Textarea field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.lastname}``" +#: ../system/objects/types.rst:115 +msgid "" +"Provides a text area input field (multiple lines) and thus allows e.g. new " +"lines. You can set a default field value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Firstname" +#: ../system/objects/types.rst:120 +msgid "" +"Please note that this field *does not* support text formatting or HTML " +"content (rich text)." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.firstname}``" +#: ../system/objects/types.rst:123 +msgid "**🥵 This field can consume a lot of visual space**" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Fax" +#: ../system/objects/types.rst:125 +msgid "" +"Depending on where you use this field type, it may use a lot of visual space " +"if you provide a lot of text. This may be an issue to work with." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.fax}``" +#: ../system/objects/types.rst:130 +msgid "Default" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Email" +#: ../system/objects/types.rst:129 +msgid "" +"The here provided text will be shown within the text area field or new data " +"sets." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.email}``" +#: ../system/objects/types.rst:134 ../system/objects/types.rst:160 +msgid "Maxlength" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Department" +#: ../system/objects/types.rst:0 ../system/objects/types.rst:160 +msgid "You can pick the maximum length of the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.department}``" +#: ../system/objects/types.rst:0 +msgid "The default length of this object is ``500``." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Avatar" +#: ../system/objects/types.rst:139 +msgid "Rows" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.avatar(60,60)}``" +#: ../system/objects/types.rst:0 +msgid "" +"Change the number of rows to dislay so that you can use only the space you " +"really need." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Address" +#: ../system/objects/types.rst:0 +msgid "The default number of rows is ``4``." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.address}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Textarea fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created at" +#: ../system/objects/types.rst:165 +msgid "Text field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_at}``" +#: ../system/objects/types.rst:145 +msgid "Provides a text field (one line) and allows choosing a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Avatar" +#: ../system/objects/types.rst:148 +msgid "" +"Defines the type of the input field. This allows e.g. your browser to ensure " +"that you provide the specific type." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.avatar(60,60)}``" +#: ../system/objects/types.rst:152 +msgid "Currently available:" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Address" +#: ../system/objects/types.rst:155 +msgid "Phone" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.address}``" +#: ../system/objects/types.rst:156 +msgid "Text" msgstr "" -#: ../system/variables/ticket.rst:6 -msgid "" -"Below you can find all available ticket-based variables within Zammad. These " -"can be called via Triggers for example. If you're unsure if Zammad does " -"support variables at the point you're at, you can try to type ``::`` to " -"check." +#: ../system/objects/types.rst:157 +msgid "Url *(URL fields disable link-template availability)*" msgstr "" -#: ../system/variables/ticket.rst:12 -msgid "Ticket Variables" +#: ../system/objects/types.rst:0 +msgid "Available settings for Text fields" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Web" +#: ../system/objects/types.rst:174 +msgid "Single tree selection field" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.web}``" +#: ../system/objects/types.rst:168 +msgid "" +"Provides a select-like field with up to 6 layers of options. Does not allow " +"setting a default value." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > VIP" +#: ../system/objects/types.rst:0 +msgid "Available settings for Tree Select fields" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.vip}``" +#: ../system/objects/types.rst:183 +msgid "Multiple tree selection field" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Phone" +#: ../system/objects/types.rst:177 +msgid "" +"Provides a select-like field with up to 6 layers of options allowing the " +"selection of multiple values. Does not allow setting a default value." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.phone}``" +#: ../system/objects/types.rst:302 +msgid "External Data Source field" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Note" +#: ../system/objects/types.rst:186 +msgid "" +"Provides a searchable field which fetches data from an external system. This " +"can be useful if you have data outside of Zammad and don't want to maintain " +"both data sources." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.note}``" +#: ../system/objects/types.rst:190 +msgid "The feature works as follows:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Mobile" +#: ../system/objects/types.rst:192 +msgid "" +"Zammad sends a query with a search string (free text from agent or based on " +"a variable) in a pre-defined format (\"Search URL\") to an external system." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.mobile}``" +#: ../system/objects/types.rst:195 +msgid "" +"This external system searches for matches and provides a response as a JSON " +"structure to Zammad." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Login" +#: ../system/objects/types.rst:197 +msgid "" +"Zammad just looks for the defined list and value keys, reads the content and " +"displays the value to the user. There is no search on Zammad side." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.login}``" +#: ../system/objects/types.rst:201 +msgid "" +"The usage of a PostgreSQL database for Zammad is required. In any other " +"case, Zammad will hide the external data source type and you are not able to " +"use it. If you want to use this feature, consider to :docs:`migrate your " +"database `." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Lastname" +#: ../system/objects/types.rst:205 +msgid "Currently, only ``GET`` is supported as request method." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.lastname}``" +#: ../system/objects/types.rst:206 +msgid "" +"The data structure must be in JSON format and provide the objects in an " +"array." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Firstname" +#: ../system/objects/types.rst:208 +msgid "" +"The endpoint for the external data source has to support search. On Zammad " +"side, there is no search/logic implemented; however, you can define the " +"output key and value based on the result(s) from the response (which " +"provides already filtered content based on the search)." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.firstname}``" +#: ../system/objects/types.rst:212 +msgid "" +"If you receive more results as expected, your external data source search " +"may not work properly or the structure of the URL is not correct. You should " +"get in touch with a responsible person from the external system." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Fax" +#: ../system/objects/types.rst:217 +msgid "" +"Please have a look :doc:`at our example `, where you can find a possible configuration for a public " +"dummy endpoint." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.fax}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for external data source fields" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Email" +#: ../system/objects/types.rst:242 +msgid "Search URL" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.email}``" +#: ../system/objects/types.rst:227 +msgid "" +"Set your endpoint where Zammad fetches the data. Please make sure to include " +"a valid search :doc:`variable ` as an URL parameter. " +"Example for a free text search at user input: ``#{search.term}``" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Department" +#: ../system/objects/types.rst:232 +msgid "" +"If in doubt, ask the responsible person for the external data source how " +"they expect the structure of the URL." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.department}``" +#: ../system/objects/types.rst:236 +msgid "" +"Depending on your search variable, the preview might work or not. The reason " +"is that the context might not be available and it is no bug." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Avatar" +#: ../system/objects/types.rst:239 +msgid "" +"Please also make sure to use a variable which is available in your object " +"context. For example you won't be able to search for a ticket in a user " +"object context." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.avatar(60,60)}``" +#: ../system/objects/types.rst:252 +msgid "SSL Verification" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Address" +#: ../system/objects/types.rst:245 +msgid "Here you can switch the SSL verification to no." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.address}``" +#: ../system/objects/types.rst:249 +msgid "" +"If your external data source system is using self signed certificates, " +"please have a look :doc:`here ` for " +"further information about how to handle them in Zammad, so you can keep the " +"SSL verification activated." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated at" +#: ../system/objects/types.rst:258 +msgid "HTTP Authentication" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_at}``" +#: ../system/objects/types.rst:255 +msgid "" +"If your external data source requires an authentication, you can set it " +"here. You can leave it empty or choose between *Basic Authentication* or " +"*Authentication Token* (selecting one of the two methods leads to additional " +"fields where you can enter your credentials/token)." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Title" +#: ../system/objects/types.rst:265 +msgid "Search result list key" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.title}``" +#: ../system/objects/types.rst:261 +msgid "" +"Defines the level in the JSON structure which provides the list with search " +"results. You can leave it empty, if the data is already provided as an " +"array. If you have to go deeper in the structure, you can provide a path " +"with ``.`` as separators, e.g. ``key.subkey.sub-sub-key``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "" -"``My amazing Subject`` (normally subject, can be edited within Interface and " -"thus differ)" +#: ../system/objects/types.rst:271 +msgid "Search result value key" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Accounted Time" +#: ../system/objects/types.rst:268 +msgid "" +"Defines the attribute in the structure in which your external data source " +"provides the *value* for your data. An example would be a product *number*. " +"If you have to go deeper in the structure, you can provide a path with ``.`` " +"as separators, e.g. ``key.subkey.sub-sub-key``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.time_unit}``" +#: ../system/objects/types.rst:277 +msgid "Search result label key" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``1``, ``2.75`` or empty response" +#: ../system/objects/types.rst:274 +msgid "" +"Defines the attribute in the structure in which your external data source " +"provides the *label* for your data. An example would be a product *name*. If " +"you have to go deeper in the structure, you can provide a path with ``.`` as " +"separators, e.g. ``key.subkey.sub-sub-key``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Tags" +#: ../system/objects/types.rst:280 +msgid "" +"In the preview area, you can find the following items (depending on your " +"configuration above):" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.tags}``" +#: ../system/objects/types.rst:283 +msgid "" +"**Error/hint message** (only if configuration is not complete): Zammad tells " +"you, if there is a problem and what you should change in your configuration." msgstr "" -#: ../system/variables/ticket.rst:1 +#: ../system/objects/types.rst:286 msgid "" -"Currently not available, see `Issue 2769 `_" +"**Search field**: search for an existing attribute in the data source to get " +"a preview. This is required for the fields below to show up." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > State > Name" +#: ../system/objects/types.rst:288 +msgid "" +"**Search result response** (only if configuration is not complete): here you " +"can find a syntax highlighted JSON preview of the response, based on the " +"search term you entered." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.state.name}``" +#: ../system/objects/types.rst:291 +msgid "" +"**Search result list** (only if *search result list key* is properly set): " +"output of the structure under the configured *search result list key*." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``new``, ``open``, ..." +#: ../system/objects/types.rst:294 +msgid "" +"**Preview table** (when fully configured): Zammad shows you a table which " +"includes the found items based on the search string (value, label and " +"optional link). You can use this preview if you don't have the complete data " +"structure of the external system in mind." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Priority > Name" +#: ../system/objects/types.rst:299 +msgid "" +"An example of a configured external data source field from agent perspective:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.priority.name}``" +#: ../system/objects/types.rst:0 +msgid "Screencast showing the search for a product in a ticket" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2 normal``" +#: ../system/objects/types.rst:307 +msgid "URL fields (Link-Template)" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Pending till" +#: ../system/objects/types.rst:311 +msgid "" +"This function is restricted to Text, Select and External data source types " +"only." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.pending_time}``" +#: ../system/objects/types.rst:314 +msgid "" +"Link-Templates are an amazing way to dynamically generate URLs. They allow " +"you to integrate other systems better without having to manually copy data " +"from Zammad if possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not set" +#: ../system/objects/types.rst:320 +msgid "" +"Another great way of communicating with another system may be Zammad's :doc:" +"`Webhooks `." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Web" +#: ../system/objects/types.rst:323 +msgid "" +"After filling a link-template enabled field, an URL icon will appear on its " +"right. Clicking on the icon opens a new tab." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.web}``" +#: ../system/objects/types.rst:328 +msgid "" +"Even though Zammad displays the link template within object edit and create " +"screens, the function is optional. It's only active if you populate the " +"field." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``https://zammad.com`` or empty if not set" +#: ../system/objects/types.rst:333 +msgid "" +"What's the difference between URL and text fields with link template...?!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > VIP" +#: ../system/objects/types.rst:335 +msgid "" +"Both fields have different use cases. Use ``text`` type text fields when " +"ever you have a *static* url that requires dynamic parameters. If you " +"require a drag & drop like field that you can put in any URL, use ``URL`` " +"type text fields." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.vip}``" +#: ../system/objects/types.rst:340 +msgid "" +"The difference is easier to spot when comparing the fields directly, below " +"screencast shows the result - the dynamic approach uses existing values in " +"the moment of updating to built the URL - e.g. ``https://google.com/search?" +"q=cookies`` - while the URL approach uses the actual URL of the field - e.g. " +"``https://zammad.com``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Phone" +#: ../system/objects/types.rst:None +msgid "" +"Screencast showing the differents in between URL and text type fields with " +"actual values" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.phone}``" +#: ../system/objects/types.rst:352 +msgid "How does this work...?!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Note" +#: ../system/objects/types.rst:354 +msgid "" +"As an example, let's say you have an attribute called ``amazing_attribute`` " +"and you want to open a google search directly with the input from that field." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.note}``" +#: ../system/objects/types.rst:357 +msgid "" +"Providing the link-template field below allows you to do so: ``https://www." +"google.com/search?q=#{ticket.amazing_attribute}``" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Mobile" +#: ../system/objects/types.rst:362 +msgid "" +"You can use any :doc:`Zammad variable ` as long as it's " +"available in the moment you need it." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.mobile}``" +#: ../system/objects/types.rst:365 +msgid "" +"As a result, you are redirected to Google with a search for the value of the " +"attribute, if you click on the button in the ticket (as you can see in the " +"screencast above)." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Login" +#: ../system/packages.rst:2 +msgid "Packages" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.login}``" +#: ../system/packages.rst:4 +msgid "That's the package management-area." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``agent``" +#: ../system/packages.rst:6 +msgid "Individual add-ons for Zammad can be installed and managed here." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Lastname" +#: ../system/sessions.rst:2 +msgid "Sessions" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.lastname}``" +#: ../system/sessions.rst:4 +msgid "" +"Sessions management allows reviewing currently known user sessions and " +"allows to end these. The session timeout is affected by :ref:" +"`security_session_timeout` configurations from security settings." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Mustermann`` or empty if not set" +#: ../system/sessions.rst:None +msgid "Screenshot showing Zammad's session management" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Firstname" +#: ../system/sessions.rst:13 +msgid "Zammad will provide the following information:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.firstname}``" +#: ../system/sessions.rst:16 +msgid "" +"The user account this session entry belongs to. It can be normal if a user " +"has several sessions in the list. This can be due to changed browser " +"information or if you use e.g. single sign on methods where the user does " +"not use the log off button." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Max`` or empty if not set" +#: ../system/sessions.rst:22 +msgid "Browser" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Fax" +#: ../system/sessions.rst:22 +msgid "The browser agent communicated to Zammad." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.fax}``" +#: ../system/sessions.rst:40 +msgid "Location" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Email" +#: ../system/sessions.rst:25 +msgid "" +"The anticipated location based on the users IP address. Depending on the IP " +"address the result shown may differ. This option depends on :doc:`/settings/" +"system/services`." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.email}``" +#: ../system/sessions.rst:29 +msgid "The following information can be shown:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``agent@company.tld`` or empty if not set" +#: ../system/sessions.rst:33 +msgid "IP address" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Department" +#: ../system/sessions.rst:32 +msgid "" +"Either if you set *Geo IP services* to inactive or you're using internal IP " +"address which do not provide location information." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.department}``" +#: ../system/sessions.rst:40 +msgid "Country (or Country + City)" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Support`` or empty if not set" +#: ../system/sessions.rst:36 +msgid "" +"If *Geo IP services* is enabled only. Depends on how detailed the available " +"IP address information are." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Avatar" +#: ../system/sessions.rst:39 +msgid "" +"Be aware that results can be inaccurate - this technically is not an error." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.avatar(60,60)}``" +#: ../system/sessions.rst:43 +msgid "Age" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Address" +#: ../system/sessions.rst:43 +msgid "Provides the time when the session initially has been created." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.address}``" +#: ../system/sessions.rst:50 +msgid "Update" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Shared organization" +#: ../system/sessions.rst:46 +msgid "" +"Provides the time the user used this session to open Zammad. This timestamp " +"is only updated if the user e.g. reloads, not during normal work on tickets." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.shared}``" +#: ../system/sessions.rst:50 +msgid "This timestamp is being used for the session timeout." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Note" +#: ../system/sessions.rst:53 +msgid "" +"Use the delete button to remove a single session on behalf of your user." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.note}``" +#: ../system/subscription.rst:2 +msgid "Subscription (SaaS)" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Name" +#: ../system/subscription.rst:4 +msgid "" +"The subscription settings page allows you to configure your instances " +"package and number of agents required." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.name}``" +#: ../system/subscription.rst:9 +msgid "" +"This setting section is only available for Hosted setups. If you're looking " +"for on premise support contracts, please see the `Zammad pricing page " +"`_." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Zammad GmbH`` or empty if not set" +#: ../system/subscription.rst:14 ../system/subscription.rst:34 +msgid "Plan" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Domain based assignment" +#: ../system/subscription.rst:16 +msgid "" +"Here you can set up everything affecting your instance subscription " +"functions like number of agents and package." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.domain_assignment}``" +#: ../system/subscription.rst:19 +msgid "" +"On top of the page you can find a subscription summary. You'll find the " +"number of used and available (booked) agent seats there. By using the *see " +"more* link you can also expand an agent list to see the currently configured " +"active agents. This list *does not* count accounts with admin permissions " +"only." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Domain" +#: ../system/subscription.rst:None +msgid "" +"Within subscription you can always see how many agents are still\n" +"available to add and who uses the seats." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.domain}``" +#: ../system/subscription.rst:29 +msgid "" +"Learn more on how to manage your agents in general :doc:`here `." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``domain.tld`` or empty if not set" +#: ../system/subscription.rst:36 +msgid "" +"This section gives you an overview of the available plans and their " +"functions / limits. If you require a more detailed table, check our " +"`detailed pricing table `_ for more." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > VIP" +#: ../system/subscription.rst:40 +msgid "" +"Your selection in this step will decide on the base agent price and e.g. " +"agent limits that might apply in the summary step." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.vip}``" +#: ../system/subscription.rst:43 +msgid "" +"The green *Selected* button will also tell you what plan you're currently in." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Number" +#: ../system/subscription.rst:47 +msgid "" +"Trial instances are running at Professional with 3 agents. The plan cannot " +"be changed during the trial for technical reasons, if you require more " +"agents for testing, please contact `our sales team `_ with a reason for the raise request." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.number}``" +#: ../system/subscription.rst:None +msgid "" +"Screenshot showing three available packages for a hosted Zammad\n" +"instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``31001``, ``201910731001``, ..." +#: ../system/subscription.rst:57 +msgid "" +"At the bottom of this block you can find a summary where you can adjust the " +"settings of the previous selected plan." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > ID" +#: ../system/subscription.rst:62 +msgid "" +"Note that upgrading (more agents, higher package) is always possible, " +"however, downgrading will only happen when your billing period renews." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.id}``" +#: ../system/subscription.rst:66 +msgid "" +"Upgrading resets your billing period and existing credit will be deducted " +"from the new total." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``17``, ``5281``, ..." +#: ../system/subscription.rst:75 +msgid "Billing cycle" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact (customer)" +#: ../system/subscription.rst:70 +msgid "" +"You can choose between either monthly or yearly billing. The price per agent " +"will be cheaper if you decide for yearly billing." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_customer_at}``" +#: ../system/subscription.rst:73 +msgid "" +"If you're still trying out things and are unsure of the right package for " +"your instance, you may want to choose monthly first and then upgrade to " +"yearly when you're sure." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "" -"``2019-10-07 16:25:00 UTC`` or empty if not applicable yet (Please note " -"`Ticket last contact behavior Settings `_ for this)" +#: ../system/subscription.rst:83 +msgid "Plan: (Starter|Professional|Plus) - Agents" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact" +#: ../system/subscription.rst:78 +msgid "Choose the number of agents you require for your instance." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_at}``" +#: ../system/subscription.rst:80 +msgid "" +"Keep in mind that some packages may have agent limits. Depending on the " +"previous chosen package, you won't be able to exceed specific agent numbers. " +"Also note that setting less agents than currently configured is not possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact (agent)" +#: ../system/subscription.rst:86 +msgid "Total" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_agent_at}``" +#: ../system/subscription.rst:86 +msgid "This will be the net total you're going to be billed." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable yet" +#: ../system/subscription.rst:88 +msgid "" +"By using the *Update subscription* button, the instance package will be " +"adjusted immediately. If you didn't provide a payment method yet, Zammad " +"will request you to provide one at this point." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Note" +#: ../system/subscription.rst:94 +msgid "" +"In case you're still within the trial period, this means that the trial will " +"be over immediately!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.note}``" +#: ../system/subscription.rst:97 +msgid "Down- or upgrading during the trial period *is not* possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Note about this group``" +#: ../system/subscription.rst:None +msgid "Screenshot showing payment options and a pricing summary" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Name" +#: ../system/subscription.rst:103 +msgid "Billing Information" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.name}``" +#: ../system/subscription.rst:105 +msgid "" +"You can control all billing relevant information like invoices, billing " +"address and the option to cancel your subscription." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Sales``" +#: ../system/subscription.rst:108 +msgid "" +"All adjusted billing information below only affect future invoices. If your " +"invoice was issued wrong, please contact `our sales team `_." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Follow-up possible" +#: ../system/subscription.rst:114 +msgid "Billing address" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.follow_up_possible}``" +#: ../system/subscription.rst:113 +msgid "" +"Provide your company address here, make sure to include the companies name " +"in case required. This address will be referenced on your invoice." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``no`` or ``yes``" +#: ../system/subscription.rst:118 +msgid "VAT ID" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Assign Follow-Ups" +#: ../system/subscription.rst:117 +msgid "" +"Provide your VAT ID here. If applicable your invoice will not contain German " +"VAT. Please make sure to pay the VAT in your country as required." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.follow_up_assignment}``" +#: ../system/subscription.rst:127 +msgid "Billing Email Address" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Assignment Timeout" +#: ../system/subscription.rst:121 +msgid "" +"Usually the instance owner (the person that registered the instance) will " +"receive all emails including the invoices. In case you have your own billing " +"department, you can provide their email address here." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.assignment_timeout}``" +#: ../system/subscription.rst:125 +msgid "" +"All billing relevant information will then be sent to this email address." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``20`` or empty if not configured" +#: ../system/subscription.rst:127 +msgid "Invoices are sent as attachment (PDF) to this email address." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > First response" +#: ../system/subscription.rst:129 +msgid "" +"Don't forget to press the *Update billing information* button after you " +"changed above settings." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.first_response_at}``" +#: ../system/subscription.rst:None +msgid "" +"Screenshot showing options for billing information within the\n" +"subscription menu" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Escalation at" +#: ../system/subscription.rst:137 +msgid "Payment Method" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.escalation_at}``" +#: ../system/subscription.rst:139 +msgid "You can pay via credit card or SEPA mandate." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable" +#: ../system/subscription.rst:144 +msgid "Credit card" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Web" +#: ../system/subscription.rst:142 +msgid "" +"Simply follow the dialogue by clicking *authorize credit card* and confirm -" +"if required by your bank- your consent to Zammad using your card for the " +"payments." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.web}``" +#: ../system/subscription.rst:148 +msgid "SEPA Direct Debit" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > VIP" +#: ../system/subscription.rst:147 +msgid "" +"Provide the requested information of the bank account holder and update if " +"you're ready. You'll then receive an email with the SEPA mandate." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.vip}``" +#: ../system/subscription.rst:150 +msgid "" +"Technically there's also the possibility to pay via invoice, however - this " +"method only applies to a fairly low number of instances. Please contact `our " +"sales team `_ for more information." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Phone" +#: ../system/subscription.rst:156 +msgid "Cancel Subscription" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.phone}``" +#: ../system/subscription.rst:158 +msgid "" +"Do you want to cancel your subscription? In case you no longer want to use " +"Zammad's SaaS, you can cancel your subscription by using the red *Yes, " +"please cancel my subscription* button." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Note" +#: ../system/subscription.rst:162 +msgid "" +"To cancel the description, enter the FQDN of your Zammad instance and " +"provide a reason for your cancellation." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.note}``" +#: ../system/subscription.rst:165 +msgid "" +"Your subscription will end the day after your trial or billing period ends." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Mobile" +#: ../system/subscription.rst:None +msgid "Screenshot showing subscription cancellation dialog" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.mobile}``" +#: ../system/subscription.rst:174 +msgid "" +"We will remind you about your cancelled subscription several times up front. " +"After the subscription ended all instance data will be removed. A restore " +"*is not* possible after that point!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Login" +#: ../system/subscription.rst:178 +msgid "**😖 Cancelled by accident?**" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.login}``" +#: ../system/subscription.rst:180 +msgid "" +"You can always undo the cancellation via the *Yes, undo the cancellation of " +"my subscription* button up to the last subscription day!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Lastname" +#: ../system/subscription.rst:0 +msgid "" +"Screenshot showing a red button to cancel the subscription\n" +"cancellation" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.lastname}``" +#: ../system/subscription.rst:189 +msgid "Payment History" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Firstname" +#: ../system/subscription.rst:191 +msgid "" +"The payment history will display a history of all paid invoices. At this " +"point you can also download these in case you need them again." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.firstname}``" +#: ../system/subscription.rst:196 +msgid "" +"You will only find *paid* invoices here. Invoices that are to be billed are " +"not available before the payment is completed." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Fax" +#: ../system/subscription.rst:201 +msgid "Date" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.fax}``" +#: ../system/subscription.rst:201 +msgid "Date of the invoice creation." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Email" +#: ../system/subscription.rst:204 +msgid "Amount" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.email}``" +#: ../system/subscription.rst:204 +msgid "Invoice total including VAT if applicable." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Department" +#: ../system/subscription.rst:207 +msgid "" +"Contains contract period (monthly or yearly) and hosted plan for the " +"subscription period in question." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.department}``" +#: ../system/subscription.rst:218 +msgid "Payment method / Service period" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Avatar" +#: ../system/subscription.rst:211 +msgid "" +"Used bank account or credit card as well as the subscription period the " +"invoice is about." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.avatar(60,60)}``" +#: ../system/subscription.rst:216 +msgid "" +"It might happen that the invoice date and subscription period differ. This " +"is nothing to worry about, the subscription periods will be accounted later " +"on." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Address" +#: ../system/subscription.rst:222 +msgid "Receipt" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.address}``" +#: ../system/subscription.rst:221 +msgid "" +"Use the arrow to download the invoice in question. You can download all " +"available invoices any time you need to here!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Web" +#: ../system/subscription.rst:None +msgid "Screenshot showing payment history of a hosted instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.web}``" +#: ../system/subscription.rst:229 +msgid "FAQ" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > VIP" +#: ../system/subscription.rst:233 +msgid "I set up a trial account but am missing functions to test" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.vip}``" +#: ../system/subscription.rst:232 +msgid "" +"The trial instance is running within the professional package allowing up to " +"three agents." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Phone" +#: ../system/subscription.rst:236 +msgid "Can I change package within the trial?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.phone}``" +#: ../system/subscription.rst:236 +msgid "No. As soon as the package is changed the subscription begins." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Note" +#: ../system/subscription.rst:241 +msgid "What happens to my trial instance after the trial period ended?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.note}``" +#: ../system/subscription.rst:239 +msgid "" +"Your instance will automatically be canceled for you. Please see *What " +"happens to my instance after it has been canceled?* for more." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Mobile" +#: ../system/subscription.rst:254 +msgid "What happens to my instance after it has been canceled?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.mobile}``" +#: ../system/subscription.rst:244 +msgid "That depends slightly on your instance state:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Login" +#: ../system/subscription.rst:250 +msgid "Trial instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.login}``" +#: ../system/subscription.rst:247 +msgid "" +"If you're still on trial, we will ice your instance and remind you once " +"again about your instance. We then will wait some days and remove your " +"instance from our system. This is the last time we will inform you by Email." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Lastname" +#: ../system/subscription.rst:254 +msgid "Paid instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.lastname}``" +#: ../system/subscription.rst:253 +msgid "" +"If you're a paying customer and canceled your subscription, the instance " +"removal will take place the day after your last subscription day." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Firstname" +#: ../system/subscription.rst:256 +msgid "Can removed instances be restored?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.firstname}``" +#: ../system/subscription.rst:257 +msgid "No. Once your instance has been removed, a restoration is not possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Fax" +#: ../system/system-report.rst:2 +msgid "System Report" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.fax}``" +#: ../system/system-report.rst:4 +msgid "" +"In this place you can't configure Zammad. Instead you can obtain a system " +"report about Zammad and its configuration." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Email" +#: ../system/system-report.rst:7 +msgid "" +"See the description in Zammad for an explanation. You can even find a " +"preview of the included data below the **Download** button." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.email}``" +#: ../system/system-report.rst:10 +msgid "" +"Zammad never sends this automatically to anyone. It is a manual process only " +"to provide better support based on your configuration." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Department" +#: ../system/translations.rst:2 +msgid "Translations" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.department}``" +#: ../system/translations.rst:4 +msgid "" +"Translations of Zammad are processed centrally in our `Weblate instance " +"`_. This allows non-developers to review " +"and update translation texts of the language they actually speak." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Avatar" +#: ../system/translations.rst:9 +msgid "" +"Your language is in an incomplete translation state or has typos? Please " +"consider helping us in sorting this out! All you need is either a GitHub " +"account or to register directly in our instance." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.avatar(60,60)}``" +#: ../system/translations.rst:13 +msgid "" +"Did you know? This is also where the documentation translations are handled. " +"🤓" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Address" +#: ../system/translations.rst:15 +msgid "" +"Have a look in our :docs:`contribution section ` in the system documentation to get started!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.address}``" +#: ../system/translations.rst:20 +msgid "Local Translations" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created at" +#: ../system/translations.rst:22 +msgid "" +"Apart from these system translations, there's still local translations you " +"can manage. This is relevant if you added custom objects that require " +"translations or even custom states and priorities." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_at}``" +#: ../system/translations.rst:None +msgid "Translation management screen within the admin menu" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "2019-10-07 16:25:00 UTC" +#: ../system/translations.rst:31 +msgid "Updating Translations" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Closing time" +#: ../system/translations.rst:33 +msgid "" +"Because of how Zammad ships translations, the only way to update the system " +"translations is to update your Zammad installation. The benefit of this is " +"that you no longer need internet access during a Zammad upgrade as the " +"package has everything it requires already." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.close_at}``" +#: ../system/translations.rst:39 +msgid "Translation of Custom Objects" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "2019-10-07 17:25:00 UTC" +#: ../system/translations.rst:41 +msgid "" +"No problem at all! You can customize any translation locally, even if it is " +"not initially provided by the system." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``3``, any number of articles existing in the ticket right now" +#: ../system/translations.rst:44 +msgid "" +"Translation is supported for a broad number of features, including but not " +"limited to custom:" msgstr "" -#: ../system/version.rst:2 -msgid "Version" +#: ../system/translations.rst:47 +msgid "Object Attributes" msgstr "" -#: ../system/version.rst:4 -msgid "Shows which version is currently being used on your Zammad-instance." +#: ../system/translations.rst:48 +msgid "Ticket Macros" msgstr "" -#: ../manage/roles/admin-permissions.rst:53 -msgid "``admin.checklist``" +#: ../system/translations.rst:49 +msgid "Ticket Overviews" msgstr "" -#: ../manage/roles/admin-permissions.rst:54 -msgid ":doc:`Manage > Checklist `" +#: ../system/translations.rst:50 +msgid "Ticket Priorities" msgstr "" -#: ../manage/roles/admin-permissions.rst:83 -msgid "``admin.channel_whatsapp``" +#: ../system/translations.rst:51 +msgid "Ticket States" msgstr "" -#: ../manage/roles/admin-permissions.rst:84 -msgid ":doc:`Channels > Whatsapp `" +#: ../system/translations.rst:54 +msgid "Customizing Translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:124 -msgid "``admin.public_links``" +#: ../system/translations.rst:56 +msgid "" +"Within the translation screen, simply click on the **New Translation** " +"button." msgstr "" -#: ../manage/roles/admin-permissions.rst:125 -msgid ":doc:`Manage > Public Links `" +#: ../system/translations.rst:None +msgid "New translation dialog" msgstr "" -#: ../manage/roles/admin-permissions.rst:151 -msgid "``admin.system_report``" +#: ../system/translations.rst:62 +msgid "" +"In the dialog you can immediately enter the exact translation source (if you " +"know it) and your custom translation text for it and click **Submit**." msgstr "" -#: ../manage/roles/admin-permissions.rst:152 -msgid ":doc:`System > System Report `" +#: ../system/translations.rst:65 +msgid "" +"Alternatively, try to search for translation suggestions in the list below. " +"Selecting an item from the list will pre-fill the translation source for you " +"and then you can just enter your custom translation." msgstr "" -#: ../manage/roles/admin-permissions.rst:166 -msgid "``admin.ticket_auto_assignment``" +#: ../system/translations.rst:69 +msgid "" +"The target language will always default to your current language selection. " +"If you need to translate for a different language, simply change the " +"selection before submitting." msgstr "" -#: ../manage/roles/admin-permissions.rst:167 -msgid ":ref:`Settings > Ticket > Auto Assignment `" +#: ../system/translations.rst:73 +msgid "" +"All your custom translations will show up in the overview table when added. " +"And they will even persist across Zammad updates!" msgstr "" -#: ../manage/roles/admin-permissions.rst:169 -msgid "``admin.ticket_duplicate_detection``" +#: ../system/translations.rst:76 +msgid "" +"Make sure to reload your browser if a translated string is not displayed." msgstr "" -#: ../manage/roles/admin-permissions.rst:170 -msgid ":ref:`Settings > Ticket > Duplicate Detection `" +#: ../system/translations.rst:80 +msgid "Reverting to Original Translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:172 -msgid "``admin.ticket_priority``" +#: ../system/translations.rst:82 +msgid "" +"If you want to revert a custom translation to original text, simply use the " +"appropriate action within the row of the overview table." msgstr "" -#: ../manage/roles/admin-permissions.rst:173 -msgid ":ref:`System > Objects >Ticket Priority `" +#: ../system/translations.rst:85 +msgid "" +"Depending on the type of the translation source, the action has a slightly " +"different name:" msgstr "" -#: ../manage/roles/admin-permissions.rst:175 -msgid "``admin.ticket_state``" +#: ../system/translations.rst:88 +msgid "**Reset** for customized system translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:176 -msgid ":ref:`System > Objects >Ticket State `" +#: ../system/translations.rst:89 +msgid "**Remove** for customized local translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:193 -msgid "``admin.webhook``" +#: ../system/translations.rst:91 +msgid "" +"In both cases, the action will remove the customized translation after a " +"confirmation." msgstr "" -#: ../manage/roles/admin-permissions.rst:194 -msgid ":doc:`Manage > Webhook `" +#: ../system/translations.rst:None +msgid "Screenshot showing the location of the Remove action" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:43 -msgid "``user_preferences.appearance``" +#: ../system/translations.rst:99 +msgid "Inline Translations" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:44 -msgid "Appearance configuration" +#: ../system/translations.rst:101 +msgid "" +"If you prefer a more hands-on approach, you can activate the inline or on-" +"screen translation feature by pressing ``ctrl`` + ``alt`` + ``t`` at any " +"time and on any screen." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:0 -msgid "Users can switch between dark, light and" +#: ../system/translations.rst:105 +msgid "" +"All customizable translation texts will be highlighted for you on the " +"screen. Just click into the highlighted area and update the text in place." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:0 -msgid "automatic mode." +#: ../system/translations.rst:None +msgid "Inline translation mode activated for the Overview screen" msgstr "" -#: ../system/system-report.rst:2 -msgid "System Report" +#: ../system/translations.rst:112 +msgid "" +"When finished editing, simply press ``ctrl`` + ``alt`` + ``t`` again to " +"deactivate." msgstr "" -#: ../system/system-report.rst:4 +#: ../system/translations.rst:117 msgid "" -"In this place you can't configure Zammad. Instead you can obtain a system " -"report about Zammad and its configuration." +"Even though it's available on any screen, the inline translation feature " +"requires admin permissions. It works only for the current language " +"selection. If you need to translate a different language, first change the " +"language in your :user-docs:`profile settings `." msgstr "" -#: ../system/system-report.rst:7 -msgid "" -"See the description in Zammad for an explanation. You can even find a " -"preview of the included data below the **Download** button." +#: ../system/version.rst:2 +msgid "Version" msgstr "" -#: ../system/system-report.rst:10 -msgid "" -"Zammad never sends this automatically to anyone. It is a manual process only " -"to provide better support based on your configuration." +#: ../system/version.rst:4 +msgid "Shows which version is currently being used on your Zammad-instance." msgstr "" diff --git a/locale/pl/LC_MESSAGES/admin-docs.po b/locale/pl/LC_MESSAGES/admin-docs.po index 2e1d7b91..10ce614a 100644 --- a/locale/pl/LC_MESSAGES/admin-docs.po +++ b/locale/pl/LC_MESSAGES/admin-docs.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Zammad\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-11-06 10:31+0100\n" +"POT-Creation-Date: 2024-11-12 16:31+0100\n" "PO-Revision-Date: 2024-06-20 06:00+0000\n" "Last-Translator: MBekspert \n" "Language-Team: Polish Checklist `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:56 msgid "``admin.channel_email``" msgstr "" -#: ../manage/roles/admin-permissions.rst:54 #: ../manage/roles/admin-permissions.rst:57 msgid ":doc:`Channels > Email `" msgstr "" -#: ../manage/roles/admin-permissions.rst:56 #: ../manage/roles/admin-permissions.rst:59 msgid "``admin.channel_facebook``" msgstr "" -#: ../manage/roles/admin-permissions.rst:57 #: ../manage/roles/admin-permissions.rst:60 msgid ":doc:`Channels > Facebook `" msgstr "" -#: ../manage/roles/admin-permissions.rst:58 #: ../manage/roles/admin-permissions.rst:61 msgid "" "Accessing Facebook tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:59 #: ../manage/roles/admin-permissions.rst:62 msgid "``admin.channel_formular``" msgstr "" -#: ../manage/roles/admin-permissions.rst:60 #: ../manage/roles/admin-permissions.rst:63 msgid ":doc:`Channels > Form `" msgstr "" -#: ../manage/roles/admin-permissions.rst:62 #: ../manage/roles/admin-permissions.rst:65 msgid "``admin.channel_google``" msgstr "" -#: ../manage/roles/admin-permissions.rst:63 #: ../manage/roles/admin-permissions.rst:66 msgid ":doc:`Channels > Google `" msgstr "" -#: ../manage/roles/admin-permissions.rst:65 #: ../manage/roles/admin-permissions.rst:68 msgid "``admin.channel_microsoft365``" msgstr "" -#: ../manage/roles/admin-permissions.rst:66 #: ../manage/roles/admin-permissions.rst:69 msgid ":doc:`Channels > Microsoft 365 `" msgstr "" -#: ../manage/roles/admin-permissions.rst:68 #: ../manage/roles/admin-permissions.rst:71 msgid "``admin.channel_sms``" msgstr "" -#: ../manage/roles/admin-permissions.rst:69 #: ../manage/roles/admin-permissions.rst:72 msgid ":doc:`Channels > SMS `" msgstr "" -#: ../manage/roles/admin-permissions.rst:71 #: ../manage/roles/admin-permissions.rst:74 msgid "``admin.channel_telegram``" msgstr "" -#: ../manage/roles/admin-permissions.rst:72 #: ../manage/roles/admin-permissions.rst:75 msgid ":doc:`Channels > Telegram `" msgstr "" -#: ../manage/roles/admin-permissions.rst:73 #: ../manage/roles/admin-permissions.rst:76 msgid "" "Accessing Telegram tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:74 #: ../manage/roles/admin-permissions.rst:77 msgid "``admin.channel_twitter``" msgstr "" -#: ../manage/roles/admin-permissions.rst:75 #: ../manage/roles/admin-permissions.rst:78 msgid ":doc:`Channels > Twitter `" msgstr "" -#: ../manage/roles/admin-permissions.rst:76 #: ../manage/roles/admin-permissions.rst:79 msgid "" "Accessing Twitter/X tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:77 #: ../manage/roles/admin-permissions.rst:80 msgid "``admin.channel_web``" msgstr "" -#: ../manage/roles/admin-permissions.rst:78 #: ../manage/roles/admin-permissions.rst:81 msgid ":doc:`Channels > Web `" msgstr "" -#: ../manage/roles/admin-permissions.rst:80 +#: ../manage/roles/admin-permissions.rst:83 +msgid "``admin.channel_whatsapp``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:84 +msgid ":doc:`Channels > Whatsapp `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:86 msgid "``admin.core_workflows``" msgstr "" -#: ../manage/roles/admin-permissions.rst:81 #: ../manage/roles/admin-permissions.rst:87 msgid ":doc:`System > Core Workflows `" msgstr "" -#: ../manage/roles/admin-permissions.rst:83 #: ../manage/roles/admin-permissions.rst:89 msgid "``admin.data_privacy``" msgstr "" -#: ../manage/roles/admin-permissions.rst:84 #: ../manage/roles/admin-permissions.rst:90 msgid ":doc:`System > Data Privacy `" msgstr "" -#: ../manage/roles/admin-permissions.rst:85 #: ../manage/roles/admin-permissions.rst:91 msgid "" "🔥 Be careful, it allows users to permanently delete data on the system." msgstr "" -#: ../manage/roles/admin-permissions.rst:86 #: ../manage/roles/admin-permissions.rst:92 msgid "``admin.group``" msgstr "" -#: ../manage/roles/admin-permissions.rst:87 #: ../manage/roles/admin-permissions.rst:93 msgid ":doc:`Manage > Groups `" msgstr "" -#: ../manage/roles/admin-permissions.rst:89 #: ../manage/roles/admin-permissions.rst:95 msgid "``admin.integration``" msgstr "" -#: ../manage/roles/admin-permissions.rst:90 #: ../manage/roles/admin-permissions.rst:96 msgid ":doc:`System > Integrations `" msgstr "" -#: ../manage/roles/admin-permissions.rst:92 #: ../manage/roles/admin-permissions.rst:98 msgid "``admin.knowledge_base``" msgstr "" -#: ../manage/roles/admin-permissions.rst:93 #: ../manage/roles/admin-permissions.rst:99 msgid ":doc:`Manage > Knowledge Base `" msgstr "" @@ -8559,57 +8542,46 @@ msgid "" "knowledge-base.html#editing-answers>`." msgstr "" -#: ../manage/roles/admin-permissions.rst:98 #: ../manage/roles/admin-permissions.rst:104 msgid "``admin.macro``" msgstr "" -#: ../manage/roles/admin-permissions.rst:99 #: ../manage/roles/admin-permissions.rst:105 msgid ":doc:`Manage > Macros `" msgstr "" -#: ../manage/roles/admin-permissions.rst:100 #: ../manage/roles/admin-permissions.rst:106 msgid "In some cases, macros may also require ``admin.tag``" msgstr "" -#: ../manage/roles/admin-permissions.rst:101 #: ../manage/roles/admin-permissions.rst:107 msgid "``admin.maintenance``" msgstr "" -#: ../manage/roles/admin-permissions.rst:102 #: ../manage/roles/admin-permissions.rst:108 msgid ":doc:`System > Maintenance `" msgstr "" -#: ../manage/roles/admin-permissions.rst:104 #: ../manage/roles/admin-permissions.rst:110 msgid "``admin.monitoring``" msgstr "" -#: ../manage/roles/admin-permissions.rst:105 #: ../manage/roles/admin-permissions.rst:111 msgid ":doc:`System > Monitoring `" msgstr "" -#: ../manage/roles/admin-permissions.rst:107 #: ../manage/roles/admin-permissions.rst:113 msgid "``admin.object``" msgstr "" -#: ../manage/roles/admin-permissions.rst:108 #: ../manage/roles/admin-permissions.rst:114 msgid ":doc:`System > Objects `" msgstr "" -#: ../manage/roles/admin-permissions.rst:110 #: ../manage/roles/admin-permissions.rst:116 msgid "``admin.organization``" msgstr "" -#: ../manage/roles/admin-permissions.rst:111 #: ../manage/roles/admin-permissions.rst:117 msgid ":doc:`Manage > Organizations `" msgstr "" @@ -8626,202 +8598,211 @@ msgstr "" msgid "They can even edit an organization's name, domain, and notes!" msgstr "" -#: ../manage/roles/admin-permissions.rst:115 #: ../manage/roles/admin-permissions.rst:121 msgid "``admin.overview``" msgstr "" -#: ../manage/roles/admin-permissions.rst:116 #: ../manage/roles/admin-permissions.rst:122 msgid ":doc:`Manage > Overviews`" msgstr "" -#: ../manage/roles/admin-permissions.rst:118 +#: ../manage/roles/admin-permissions.rst:124 +msgid "``admin.public_links``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:125 +msgid ":doc:`Manage > Public Links `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:127 msgid "``admin.package``" msgstr "" -#: ../manage/roles/admin-permissions.rst:119 #: ../manage/roles/admin-permissions.rst:128 msgid ":doc:`System > Packages `" msgstr "" -#: ../manage/roles/admin-permissions.rst:121 #: ../manage/roles/admin-permissions.rst:130 msgid "``admin.report_profile``" msgstr "" -#: ../manage/roles/admin-permissions.rst:122 #: ../manage/roles/admin-permissions.rst:131 msgid ":doc:`Manage > Report Profiles `" msgstr "" -#: ../manage/roles/admin-permissions.rst:123 #: ../manage/roles/admin-permissions.rst:132 msgid "Access to view reports: ``report``" msgstr "" -#: ../manage/roles/admin-permissions.rst:124 #: ../manage/roles/admin-permissions.rst:133 msgid "``admin.role``" msgstr "" -#: ../manage/roles/admin-permissions.rst:125 #: ../manage/roles/admin-permissions.rst:134 msgid ":doc:`Manage > Roles `" msgstr "" -#: ../manage/roles/admin-permissions.rst:127 #: ../manage/roles/admin-permissions.rst:136 msgid "``admin.scheduler``" msgstr "" -#: ../manage/roles/admin-permissions.rst:128 #: ../manage/roles/admin-permissions.rst:137 msgid ":doc:`Manage > Scheduler `" msgstr "" -#: ../manage/roles/admin-permissions.rst:129 #: ../manage/roles/admin-permissions.rst:138 msgid "For automation on tickets" msgstr "" -#: ../manage/roles/admin-permissions.rst:130 #: ../manage/roles/admin-permissions.rst:139 msgid "``admin.security``" msgstr "" -#: ../manage/roles/admin-permissions.rst:131 #: ../manage/roles/admin-permissions.rst:140 msgid ":doc:`Settings > Security `" msgstr "" -#: ../manage/roles/admin-permissions.rst:132 #: ../manage/roles/admin-permissions.rst:141 msgid "Settings of Zammad. This also covers third party authentications." msgstr "" -#: ../manage/roles/admin-permissions.rst:133 #: ../manage/roles/admin-permissions.rst:142 msgid "``admin.session``" msgstr "" -#: ../manage/roles/admin-permissions.rst:134 #: ../manage/roles/admin-permissions.rst:143 msgid ":doc:`System > Sessions `" msgstr "" -#: ../manage/roles/admin-permissions.rst:136 #: ../manage/roles/admin-permissions.rst:145 msgid "``admin.setting_system``" msgstr "" -#: ../manage/roles/admin-permissions.rst:137 #: ../manage/roles/admin-permissions.rst:146 msgid ":doc:`Settings > System `" msgstr "" -#: ../manage/roles/admin-permissions.rst:139 #: ../manage/roles/admin-permissions.rst:148 msgid "``admin.sla``" msgstr "" -#: ../manage/roles/admin-permissions.rst:140 #: ../manage/roles/admin-permissions.rst:149 msgid ":doc:`Manage > SLAs `" msgstr "" -#: ../manage/roles/admin-permissions.rst:142 +#: ../manage/roles/admin-permissions.rst:151 +msgid "``admin.system_report``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:152 +msgid ":doc:`System > System Report `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:154 msgid "``admin.tag``" msgstr "" -#: ../manage/roles/admin-permissions.rst:143 #: ../manage/roles/admin-permissions.rst:155 msgid ":doc:`Manage > Tags `" msgstr "" -#: ../manage/roles/admin-permissions.rst:145 #: ../manage/roles/admin-permissions.rst:157 msgid "``admin.template``" msgstr "" -#: ../manage/roles/admin-permissions.rst:146 #: ../manage/roles/admin-permissions.rst:158 msgid ":doc:`Manage > Templates `" msgstr "" -#: ../manage/roles/admin-permissions.rst:148 #: ../manage/roles/admin-permissions.rst:160 msgid "``admin.text_module``" msgstr "" -#: ../manage/roles/admin-permissions.rst:149 #: ../manage/roles/admin-permissions.rst:161 msgid ":doc:`Manage > Text Modules `" msgstr "" -#: ../manage/roles/admin-permissions.rst:151 #: ../manage/roles/admin-permissions.rst:163 msgid "``admin.ticket``" msgstr "" -#: ../manage/roles/admin-permissions.rst:152 #: ../manage/roles/admin-permissions.rst:164 msgid ":doc:`Settings > Tickets `" msgstr "" -#: ../manage/roles/admin-permissions.rst:153 #: ../manage/roles/admin-permissions.rst:165 msgid "Does not grant access to :doc:`/misc/composer`" msgstr "" -#: ../manage/roles/admin-permissions.rst:154 +#: ../manage/roles/admin-permissions.rst:166 +msgid "``admin.ticket_auto_assignment``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:167 +msgid ":ref:`Settings > Ticket > Auto Assignment `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:169 +msgid "``admin.ticket_duplicate_detection``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:170 +msgid ":ref:`Settings > Ticket > Duplicate Detection `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:172 +#, fuzzy +msgid "``admin.ticket_priority``" +msgstr "priorytet" + +#: ../manage/roles/admin-permissions.rst:173 +msgid ":ref:`System > Objects >Ticket Priority `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:175 +msgid "``admin.ticket_state``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:176 +msgid ":ref:`System > Objects >Ticket State `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:178 msgid "``admin.time_accounting``" msgstr "" -#: ../manage/roles/admin-permissions.rst:155 #: ../manage/roles/admin-permissions.rst:179 msgid ":doc:`Manage > Time Accounting `" msgstr "" -#: ../manage/roles/admin-permissions.rst:156 #: ../manage/roles/admin-permissions.rst:180 msgid "Also allows the export of timekeeping records." msgstr "" -#: ../manage/roles/admin-permissions.rst:157 #: ../manage/roles/admin-permissions.rst:181 msgid "``admin.translation``" msgstr "" -#: ../manage/roles/admin-permissions.rst:158 #: ../manage/roles/admin-permissions.rst:182 msgid ":doc:`System > Translations `" msgstr "" -#: ../manage/roles/admin-permissions.rst:159 #: ../manage/roles/admin-permissions.rst:183 msgid "Also enables inline translation" msgstr "" -#: ../manage/roles/admin-permissions.rst:160 #: ../manage/roles/admin-permissions.rst:184 msgid "``admin.trigger``" msgstr "" -#: ../manage/roles/admin-permissions.rst:161 #: ../manage/roles/admin-permissions.rst:185 msgid ":doc:`Manage > Triggers `" msgstr "" -#: ../manage/roles/admin-permissions.rst:163 #: ../manage/roles/admin-permissions.rst:187 msgid "``admin.user``" msgstr "" -#: ../manage/roles/admin-permissions.rst:164 #: ../manage/roles/admin-permissions.rst:188 msgid ":doc:`Manage > Users `" msgstr "" @@ -8840,6 +8821,14 @@ msgid "" "from-users-perspective>` ." msgstr "" +#: ../manage/roles/admin-permissions.rst:193 +msgid "``admin.webhook``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:194 +msgid ":doc:`Manage > Webhook `" +msgstr "" + #: ../manage/roles/agent-permissions.rst:2 msgid "Agent Permissions" msgstr "" @@ -9258,36 +9247,45 @@ msgid "than the user that generated them." msgstr "" #: ../manage/roles/user-preferences-permissions.rst:43 +msgid "``user_preferences.appearance``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:44 +msgid "Appearance configuration" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "Users can switch between dark, light and" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "automatic mode." +msgstr "" + #: ../manage/roles/user-preferences-permissions.rst:47 msgid "``user_preferences.avatar``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:44 #: ../manage/roles/user-preferences-permissions.rst:48 msgid "Avatar settings" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:45 #: ../manage/roles/user-preferences-permissions.rst:49 msgid "Override the default Gravatar with a custom avatar" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:46 #: ../manage/roles/user-preferences-permissions.rst:50 msgid "``user_preferences.calendar``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:47 #: ../manage/roles/user-preferences-permissions.rst:51 msgid "Configure the calendar feed" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:49 #: ../manage/roles/user-preferences-permissions.rst:53 msgid "``user_preferences.device``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:50 #: ../manage/roles/user-preferences-permissions.rst:54 msgid "Manage device login sessions" msgstr "" @@ -9304,22 +9302,18 @@ msgstr "" msgid "To learn more, see :doc:`/manage/trigger/system-notifications`." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:54 #: ../manage/roles/user-preferences-permissions.rst:58 msgid "``user_preferences.language``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:55 #: ../manage/roles/user-preferences-permissions.rst:59 msgid "Configure the UI locale/language" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:57 #: ../manage/roles/user-preferences-permissions.rst:61 msgid "``user_preferences.linked_accounts``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:58 #: ../manage/roles/user-preferences-permissions.rst:62 msgid "Account linking" msgstr "" @@ -9343,7 +9337,6 @@ msgstr "" msgid "is the only way users can utilize third-party logins." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:63 #: ../manage/roles/user-preferences-permissions.rst:67 msgid "``user_preferences.notifications``" msgstr "" @@ -9370,7 +9363,6 @@ msgstr "" msgid "Customers can't receive ticket notifications at all." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:69 #: ../manage/roles/user-preferences-permissions.rst:73 msgid "``user_preferences.out_of_office``" msgstr "" @@ -9395,7 +9387,6 @@ msgstr "" msgid "they're replacing." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:75 #: ../manage/roles/user-preferences-permissions.rst:79 msgid "``user_preferences.overview_sorting``" msgstr "" @@ -9424,12 +9415,10 @@ msgstr "" msgid "overviews has no effect on custom orders." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:82 #: ../manage/roles/user-preferences-permissions.rst:86 msgid "``user_preferences.password``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:83 #: ../manage/roles/user-preferences-permissions.rst:87 msgid "Change account password" msgstr "" @@ -9446,7 +9435,6 @@ msgstr "" msgid "your only allowed authentication method." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:87 #: ../manage/roles/user-preferences-permissions.rst:91 msgid "``user_preferences.two_factor_authentication``" msgstr "" @@ -9483,7 +9471,7 @@ msgstr "" #: ../manage/scheduler.rst:19 msgid "" -"Schedulers can be used to send periodic reminder emails. Use :doc:`/system/" +"Schedulers can be used to send periodic reminder emails. Use :doc:`/misc/" "variables` to build highly-customized email templates." msgstr "" @@ -10480,7 +10468,7 @@ msgstr "" #: ../manage/text-modules.rst:57 msgid "" -"The example text modules below use :doc:`/system/variables` to dynamically " +"The example text modules below use :doc:`/misc/variables` to dynamically " "insert information like the customer's or agent's names." msgstr "" @@ -10820,8 +10808,8 @@ msgstr "" #: ../misc/object-conditions/basics.rst:144 #: ../misc/object-conditions/basics.rst:160 #: ../misc/object-conditions/basics.rst:168 -#: ../misc/object-conditions/basics.rst:178 ../settings/ticket.rst:2 -#: ../system/variables/ticket.rst:2 +#: ../misc/object-conditions/basics.rst:178 ../misc/variables/ticket.rst:2 +#: ../settings/ticket.rst:2 msgid "Ticket" msgstr "" @@ -11055,7 +11043,7 @@ msgstr "" #: ../manage/trigger/how-do-they-work.rst:79 msgid "" -"Certain actions (such as *email*, *SMS* and *notes*) support :doc:`/system/" +"Certain actions (such as *email*, *SMS* and *notes*) support :doc:`/misc/" "variables`, which can be used to build highly-customized message templates." msgstr "" @@ -11084,7 +11072,7 @@ msgstr "" msgid "" "You can also combine static text with placeholders for text fields. Remember " "that the placeholders' values have to be known during trigger runtime. Learn " -"more about :doc:`/system/variables`." +"more about :doc:`/misc/variables`." msgstr "" #: ../manage/trigger/how-do-they-work.rst:105 @@ -12050,7 +12038,7 @@ msgstr "" msgid "" "When switched on, a code editor will be shown below, where you can configure " "custom payload for your webhook in JSON format. To insert supported :doc:`/" -"system/variables` use ``::`` or ``#{`` shortcuts for autocomplete." +"misc/variables` use ``::`` or ``#{`` shortcuts for autocomplete." msgstr "" #: ../manage/webhook/add.rst:103 @@ -14632,11967 +14620,11858 @@ msgid "" "powerful conditions with AND/OR relations." msgstr "" -#: ../settings/branding.rst:10 -msgid "Product Name" +#: ../misc/variables.rst:2 +msgid "Variables" msgstr "" -#: ../settings/branding.rst:7 +#: ../misc/variables.rst:4 msgid "" -"Defines the name of the application, shown in the web interface, tabs and " -"title bar of the web browser." +"Please note that this is just an overview of available variables. It might " +"be incomplete or variables might not be available within some functions. If " +"you're missing variables or are not sure if something is not working as " +"expected, feel free to ask over at the `Community `_." msgstr "" -#: ../settings/branding.rst:10 -msgid "Default value: ``Zammad Helpdesk``" +#: ../misc/variables.rst:10 +msgid "" +"Variables can be called by typing ``::`` (just like text modules in the " +"frontend), as long as you're in a supported text field within the backend. " +"Zammad will display all variables being available within this context and " +"replace it to the variable as soon as you selected an entry." msgstr "" -#: ../settings/branding.rst:13 -msgid "Will be shown in the app and is included in email footers." +#: ../misc/variables.rst:15 +msgid "" +"You have an empty field which you referenced and it appears as ``-``? That's " +"currently working as designed - you might want to ensure that these fields " +"always have a value." msgstr "" -#: ../settings/branding.rst:19 -msgid "Logo" +#: ../misc/variables.rst:20 +msgid "Variable Categories" msgstr "" -#: ../settings/branding.rst:16 -msgid "Defines the logo of the application, shown in the login page of Zammad." +#: ../misc/variables.rst:31 +msgid "Wait, What About Custom Objects?" msgstr "" -#: ../settings/branding.rst:18 +#: ../misc/variables.rst:33 msgid "" -"Ensure to hit the \"Submit\" button after uploading the logo. Otherwise your " -"change will not be saved." +"Good point! Of course, we can't predict what objects you might create, but " +"we can give you a hint on how to put the puzzle together to get your custom " +"values." msgstr "" -#: ../settings/branding.rst:22 +#: ../misc/variables.rst:36 msgid "" -"Allows to set the default language of the Zammad instance. The here defined " -"locale mostly acts as a fallback for:" +"For this, we'll talk about the inner part of the variable (so everything " +"within ``#{}``), please put the outer part around to have a valid variable. " +"The first part of the variable name consist of the object type. Currently " +"these are:" msgstr "" -#: ../settings/branding.rst:25 -msgid "user preferences (if Zammad can't detect the users locale)" +#: ../misc/variables.rst:41 +msgid "Ticket (``ticket``)" msgstr "" -#: ../settings/branding.rst:26 -msgid "CSV output (reporting, time accounting)" +#: ../misc/variables.rst:42 +msgid "User (``user``)" msgstr "" -#: ../settings/branding.rst:30 -msgid "Define the timezone of your Zammad installation." +#: ../misc/variables.rst:43 +msgid "Organization (``organization``)" msgstr "" -#: ../settings/branding.rst:32 +#: ../misc/variables.rst:44 +msgid "Group (``group``)" +msgstr "" + +#: ../misc/variables.rst:46 msgid "" -"This does not have any effect on timings for your agents or how Zammad " -"stores date and time values." +"The second part is the name of the attribute. This is the name you define " +"during object creation and can be found within the object attribute menu at " +"any time. The first and second part of a variable is divided by a point, e." +"g.: ``ticket.number`` which will in total be ``#{ticket.number}``." msgstr "" -#: ../settings/branding.rst:35 -msgid "Changing this value has direct consequences on the following areas:" +#: ../misc/variables.rst:51 +msgid "" +"Now, in some situations it's possible that you'll need to use a third part. " +"The best example for such a situation would be a ``select`` or ``tree-" +"select`` field which will by default return the key value, not it's display " +"name. For this, just extend your variable with ``.value``. This will result " +"in ``#{ticket.select.value}``." msgstr "" -#: ../settings/branding.rst:37 -msgid ":doc:`/manage/scheduler` tasks" +#: ../misc/variables.rst:60 +msgid "Using Translated Variables" msgstr "" -#: ../settings/branding.rst:38 -msgid "search indexing (and thus reporting)" +#: ../misc/variables.rst:62 +msgid "" +"If you want to use a translated variable in triggers or schedulers, you can " +"extend the placeholder like this: ``#{t(ticket.state.name)}``. The ``t`` " +"tells Zammad to search for fitting translated strings. The used output " +"language is based on the system language of Zammad which you can set in the " +"admin panel under :doc:`/settings/branding` or based on the selected locale " +"in the trigger/scheduler edit dialog." msgstr "" -#: ../settings/branding.rst:40 -msgid "calendar subscriptions" +#: ../misc/variables.rst:69 +msgid "" +"A possible use-case: you want to send your customers updates on tickets via " +"trigger or scheduler which should include the state of the ticket. Using the " +"default ``#{ticket.state.name}`` (without the translation flag ``t()``) " +"would lead to the output of the original (english) name of the state." msgstr "" -#: ../settings/branding.rst:41 -msgid "browser printing" +#: ../misc/variables.rst:75 +msgid "Date and Time Formatting" msgstr "" -#: ../settings/branding.rst:43 +#: ../misc/variables.rst:77 msgid "" -"Please note that some of above are fallbacks in case Zammad could not detect " -"the agents timezone correctly." +"The system (trigger/scheduler selected) locale and timezone predefines a " +"default format of date and timestamp. This format is customizable by using " +"the ``dt()`` method." msgstr "" -#: ../settings/branding.rst:77 -msgid "Pretty Date" +#: ../misc/variables.rst:79 +msgid "The method arguments are as follows:" msgstr "" -#: ../settings/branding.rst:47 -msgid "" -"This setting allows you to define how Zammad should display time stamps " -"within the interface to all users." +#: ../misc/variables.rst:81 +msgid "The date or timestamp variable you want to format." msgstr "" -#: ../settings/branding.rst:50 -msgid "" -"This does not have any effect on how Zammad returns e.g. time values via " -"variables." +#: ../misc/variables.rst:82 +msgid "The output format string." msgstr "" -#: ../settings/branding.rst:77 -msgid "Choose in between the following options:" +#: ../misc/variables.rst:83 +msgid "The timezone to apply (optional)." msgstr "" -#: ../settings/branding.rst:64 -msgid "relative" -msgstr "" +#: ../misc/variables.rst:85 +#: ../system/objects/external-data-source-example.rst:23 +#, fuzzy +msgid "**Example:**" +msgstr "Przykład" -#: ../settings/branding.rst:55 +#: ../misc/variables.rst:86 msgid "" -"This timestamp shows a relative time span until it switches to a date. Over " -"time, it will change as follows:" +"``#{dt(ticket.updated_at, \"%A %Y-%m-%d %H:%M in the office\", \"Europe/" +"Berlin\")}``" msgstr "" -#: ../settings/branding.rst:58 -msgid "just now" +#: ../misc/variables.rst:87 +msgid "Monday, 2024-03-18 15:31 in the office" msgstr "" -#: ../settings/branding.rst:59 -msgid "5 minutes ago" +#: ../misc/variables.rst:89 +msgid "" +"If you want to use our example, make sure to paste the string above without " +"formatting (``CTRL+Shift+v``), otherwise it won't work." msgstr "" -#: ../settings/branding.rst:60 -msgid "3 days 1 hour ago" +#: ../misc/variables.rst:93 +msgid "The following table lists available format directives:" msgstr "" -#: ../settings/branding.rst:61 -msgid "``03/04/2022``" +#: ../misc/variables.rst:99 +msgid "Parameter" msgstr "" -#: ../settings/branding.rst:63 -msgid "Hovering the timestamp helps, you'll always get a clean timestamp then." +#: ../misc/variables.rst:102 +msgid "``%Y``" msgstr "" -#: ../settings/branding.rst:71 -msgid "absolute" +#: ../misc/variables.rst:103 +msgid "Year with 4 digits" msgstr "" -#: ../settings/branding.rst:67 -msgid "" -"This timestamp always includes the week day. For one week after creation, " -"the timestamp will not contain the date itself: Thursday 18:35." +#: ../misc/variables.rst:104 +msgid "Use ``%y`` for year with 2 digits" msgstr "" -#: ../settings/branding.rst:71 -msgid "After a week it will switch to: ``Friday 4. Mar 16:00``." +#: ../misc/variables.rst:105 +msgid "``%m``" msgstr "" -#: ../settings/branding.rst:76 -msgid "timestamp" +#: ../misc/variables.rst:106 +msgid "Month of year (as number with zero-padding)" msgstr "" -#: ../settings/branding.rst:74 -msgid "" -"This will cause Zammad to show a complete timestamp according to your locale " -"defaults. For English this could be e.g. ``2022/12/03 2:40 pm`` or for " -"German e.g. ``12.03.2022 14:40``." +#: ../misc/variables.rst:107 +msgid "Use ``%-m`` for month without zero-padding" msgstr "" -#: ../settings/branding.rst:78 -msgid "Default setting: ``relative``." +#: ../misc/variables.rst:108 +msgid "``%d``" msgstr "" -#: ../settings/security.rst:2 -msgid "Security" +#: ../misc/variables.rst:109 +msgid "Day of month (as number with zero-padding)" msgstr "" -#: ../settings/security.rst:4 -msgid "" -"For your overview we split each tab within security settings into its own " -"page:" +#: ../misc/variables.rst:110 +msgid "Use ``%e`` for day without zero-padding" msgstr "" -#: ../settings/security/base.rst:2 ../settings/system/base.rst:2 -#: ../settings/ticket.rst:8 -msgid "Base" +#: ../misc/variables.rst:111 +msgid "``%H``" msgstr "" -#: ../settings/security/base.rst:5 -msgid "New User Accounts" +#: ../misc/variables.rst:112 +msgid "Hour of day in 24h notation with zero-padding" msgstr "" -#: ../settings/security/base.rst:9 -msgid "" -"Activates the `register as a new customer` function on the login page. If " -"set to ``no`` only administrators or agents can create new accounts manually." +#: ../misc/variables.rst:113 +msgid "Use ``%k`` for hour without zero-padding" msgstr "" -#: ../settings/security/base.rst:13 ../settings/security/base.rst:38 -#: ../settings/security/base.rst:66 -msgid "Default setting: ``yes``" +#: ../misc/variables.rst:114 +msgid "``%I``" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing activated \"New User Accounts\" setting" +#: ../misc/variables.rst:115 +msgid "Hour of day in 12h notation with zero-padding" msgstr "" -#: ../settings/security/base.rst:22 +#: ../misc/variables.rst:116 msgid "" -"Deactivation of above function **does not** deactivate automatic account " -"creation! This means: If a user writes e.g. an email to Zammad and has no " -"account yet, Zammad will automatically create the account. User accounts are " -"a direct dependency of tickets and thus technically mandatory." +"Use ``%l`` for hour without zero-padding and ``%p`` / ``%P`` for meridian " +"indicator" msgstr "" -#: ../settings/security/base.rst:29 -msgid "Lost Password" +#: ../misc/variables.rst:117 +msgid "``%M``" msgstr "" -#: ../settings/security/base.rst:33 -msgid "" -"Activates the `lost password` function on the login page. If set to ``no`` " -"only administrators may change the user's password - users may update their " -"own password if they're still logged in and they have the required :doc:" -"`permission `." +#: ../misc/variables.rst:118 +msgid "Minute of hour" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing activated \"Lost Password\" setting" +#: ../misc/variables.rst:120 +msgid "``%S``" msgstr "" -#: ../settings/security/base.rst:49 -msgid "" -"With third party authentications - but especially LDAP - you may want to " -"disable this function. Zammad **will not** change third party login " -"passwords and instead set or change the local password!" +#: ../misc/variables.rst:121 +msgid "Second of Minute" msgstr "" -#: ../settings/security/base.rst:56 -msgid "Password Login" +#: ../misc/variables.rst:123 +msgid "``%A``" msgstr "" -#: ../settings/security/base.rst:60 -msgid "" -"Activates the username & password login by default and if no third-party " -"login is activated. Disabling password login on the Zammad login page only " -"takes effect if you enable any :doc:`third-party`." +#: ../misc/variables.rst:124 +msgid "Weekday name" msgstr "" -#: ../settings/security/base.rst:64 -msgid "See :doc:`third-party` for supported third-party logins." +#: ../misc/variables.rst:125 +msgid "Use ``%a`` for abbreviated name or ``%^A`` for uppercase name" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing de-activated \"Password Login\" setting" +#: ../misc/variables.rst:126 +msgid "``%B``" msgstr "" -#: ../settings/security/base.rst:77 -msgid "" -"To help administrators to overcome \"login issues\", Zammad automatically " -"offers a password request for administrator users. This allows you to adjust " -"Third-Party applications even if the login does no longer work!" +#: ../misc/variables.rst:127 +msgid "Month name" msgstr "" -#: ../settings/security/base.rst:84 -msgid "Session Timeout" +#: ../misc/variables.rst:128 +msgid "Use ``%b`` for abbreviated name" msgstr "" -#: ../settings/security/base.rst:86 -msgid "" -"All settings below by default are set to ``4 weeks``. Session Timeout " -"defines the life time of a users session. As soon as it's reached, Zammad " -"will automatically log off the session in question." +#: ../misc/variables.rst:129 +msgid "``%U``" msgstr "" -#: ../settings/security/base.rst:91 -msgid "" -"Zammad takes the highest value set assigned for the user based on the " -"permissions." +#: ../misc/variables.rst:130 +msgid "Week number of current year" msgstr "" -#: ../settings/security/base.rst:94 -msgid "``admin``" +#: ../misc/variables.rst:131 +msgid "Use ``%W`` for a different calculation method" msgstr "" -#: ../settings/security/base.rst:96 -msgid "``ticket.customer``" +#: ../misc/variables.rst:134 +msgid "" +"We support the known format directives for the Ruby built-in method " +"``strftime`` of the ``DateTime`` class. For more information, see `here " +"`_." msgstr "" -#: ../settings/security/base.rst:97 -msgid "``default`` (fallback if user doesn't have above permissions set)" +#: ../misc/variables/article.rst:2 +msgid "Articles" msgstr "" -#: ../settings/security/base.rst:99 +#: ../misc/variables/article.rst:4 ../misc/variables/config.rst:4 +#: ../misc/variables/current-user.rst:4 ../misc/variables/ticket.rst:4 msgid "" -"All settings act independently from each other allowing you to disable the " -"timeouts for e.g. admins, but not agents." +"If you're missing variables or are not sure if something is not working as " +"expected, feel free to ask over at the `Community `_." msgstr "" -#: ../settings/security/base.rst:115 -#: ../system/integrations/checkmk/api-reference.rst:13 -#, fuzzy -msgid "Example" -msgstr "Przykład" +#: ../misc/variables/article.rst:6 +msgid "" +"Below you can find all available ticket article-based variables within " +"Zammad. These can be called via triggers for example. If you're unsure if " +"Zammad does support variables at the point you're at, you can try to type " +"``::`` to check." +msgstr "" -#: ../settings/security/base.rst:107 -msgid "Let's suppose you configured the following session timeouts" +#: ../misc/variables/article.rst:9 ../misc/variables/config.rst:9 +#: ../misc/variables/ticket.rst:9 +msgid "" +"The below list gives you an example what kind of data you can expect, it's " +"not intended to explain the data itself." msgstr "" -#: ../settings/security/base.rst:104 -msgid "default: 3 weeks" +#: ../misc/variables/article.rst:11 +msgid "Article Variables" msgstr "" -#: ../settings/security/base.rst:105 -msgid "admin: 2 weeks" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "name" msgstr "" -#: ../settings/security/base.rst:106 -msgid "ticket.agent: 4 weeks" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "variable" msgstr "" -#: ../settings/security/base.rst:107 -msgid "ticket.customer: 1 week" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "example" msgstr "" -#: ../settings/security/base.rst:115 -msgid "This results in the following situations" +#: ../misc/variables/article.rst:1 +msgid "Article > Cc" msgstr "" -#: ../settings/security/base.rst:110 -msgid "a user with ``admin`` permission will have a timeout of 2 weeks" +#: ../misc/variables/article.rst:1 +msgid "``#{article.cc}``" msgstr "" -#: ../settings/security/base.rst:111 -msgid "" -"a user with ``admin`` and ``ticket.agent`` permissions will have a timeout " -"of 2 weeks" +#: ../misc/variables/article.rst:1 +msgid "``jdoe@example.com, company@example.com``" msgstr "" -#: ../settings/security/base.rst:113 -msgid "" -"a user with ``ticket.customer`` permission will have a timeout of 1 week" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Address" msgstr "" -#: ../settings/security/base.rst:115 -msgid "" -"a user with neither ``admin``, ``ticket.agent`` nor ``ticket.customer`` " -"permissions will have a timeout of 3 weeks" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.address}``" msgstr "" -#: ../settings/security/password.rst:4 -msgid "" -"This section allows you to define password requirements for the local user " -"accounts." +#: ../misc/variables/article.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:9 -msgid "" -"Zammad does **not** allow you to change your LDAP password, instead, it will " -"set a password in its local database which might confuse your users. This " -"might be addressed in the future by `#1169 `_." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Department" msgstr "" -#: ../settings/security/password.rst:14 -msgid "**Exception for admins**" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.department}``" msgstr "" -#: ../settings/security/password.rst:16 -msgid "" -"Please note that below password policies *do not* affect administrators " -"setting passwords on user accounts. While this seems strange and not safe we " -"believe that an administrator knowing an user's password is insecure as well." +#: ../misc/variables/article.rst:1 +msgid "``Sales`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:21 -msgid "The suggested workflow is either:" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Email" msgstr "" -#: ../settings/security/password.rst:23 -msgid "" -"to use third party logins to not require local passwords at all **- or -**" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.email}``" msgstr "" -#: ../settings/security/password.rst:25 -msgid "to require your *user to reset the password* upon first login." +#: ../misc/variables/article.rst:1 +msgid "``jdoe@example.com``" msgstr "" -#: ../settings/security/password.rst:27 -msgid "" -"This way administrators are not required to set a user's password at all!" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Fax" msgstr "" -#: ../settings/security/password.rst:31 -msgid "Maximum Failed Logins" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.fax}``" msgstr "" -#: ../settings/security/password.rst:33 -msgid "" -"You can choose a value between ``4`` and ``20``. This defines how often a " -"login to a user account may fail until Zammad will lock it. Your users can " -"always use the \"forgot password\" function to change their password and " -"unlock their account." +#: ../misc/variables/article.rst:1 +msgid "``+4930123456789`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:38 -msgid "The default value is ``10``." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Firstname" msgstr "" -#: ../settings/security/password.rst:42 -msgid "Beside changing the user's password, you can also unlock accounts via" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.firstname}``" msgstr "" -#: ../settings/security/password.rst:44 -msgid ":ref:`user management list `" +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Joe`` or empty if not set" msgstr "" -#: ../settings/security/password.rst:45 -msgid ":docs:`console `" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Lastname" msgstr "" -#: ../settings/security/password.rst:46 -msgid ":docs:`API `" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.lastname}``" msgstr "" -#: ../settings/security/password.rst:50 -msgid "Failed logins via LDAP no longer lock accounts." +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +#: ../misc/variables/ticket.rst:1 +msgid "``Doe`` or empty if not set" msgstr "" -#: ../settings/security/password.rst:53 -msgid "2 Lower Case And 2 Upper Case Characters" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Login" msgstr "" -#: ../settings/security/password.rst:55 -msgid "" -"You can add complexity to passwords by enforcing at least 2 upper and lower " -"case characters." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.login}``" msgstr "" -#: ../settings/security/password.rst:58 ../settings/security/password.rst:83 -msgid "The default value is ``no``." +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +#: ../misc/variables/ticket.rst:1 +msgid "``jdoe``" msgstr "" -#: ../settings/security/password.rst:62 -msgid "Minimum Length" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Mobile" msgstr "" -#: ../settings/security/password.rst:64 -msgid "" -"This defines the minimum password length required for users to provide (from " -"``4`` to ``20``)." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.mobile}``" msgstr "" -#: ../settings/security/password.rst:67 -msgid "The default value is ``6``." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Note" msgstr "" -#: ../settings/security/password.rst:71 -msgid "Digit Required" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.note}``" msgstr "" -#: ../settings/security/password.rst:73 -msgid "This enforces your users to use at least one digit within the password." +#: ../misc/variables/article.rst:1 +msgid "``Some note about user`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:75 -msgid "The default value is ``yes``." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Phone" msgstr "" -#: ../settings/security/password.rst:78 -msgid "Special Character Required" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.phone}``" msgstr "" -#: ../settings/security/password.rst:80 -msgid "" -"This setting allows you to improve your password quality even more by " -"enforcing the password to contain at least one special character." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > VIP" msgstr "" -#: ../settings/security/ssl-certificates.rst:2 -msgid "SSL Certificates" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.vip}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:7 -msgid "" -"Zammad offers the possibility to upload custom certificates and custom " -"Certificate Authority (CA) certificates. This can be useful if you want to " -"connect Zammad the secure way to other systems which are using custom " -"certificates." +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +msgid "``true`` or ``false``" msgstr "" -#: ../settings/security/ssl-certificates.rst:12 -msgid "" -"An example usecase might be: You have an internal LDAP server that is not " -"accessible from the internet, and you want a SSL-encrypted connection, using " -"a custom certificate." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Web" msgstr "" -#: ../settings/security/ssl-certificates.rst:19 -msgid "" -"You should have an existing custom certificate file and/or a custom CA " -"certificate file, which you want to add to Zammad. As filetype ``.crt`` is " -"supported and the certificate format has to be PEM (Base64 ASCII)." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.web}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:25 -msgid "" -"When you import a custom CA certificate, all certificates generated with " -"this are trusted. This can be useful if you have more than one system/" -"certificate you want to connect to and the certificates are issued from the " -"same custom CA." +#: ../misc/variables/article.rst:1 +msgid "``https://zammad.com`` or empty if not set in user object" msgstr "" -#: ../settings/security/ssl-certificates.rst:31 -msgid "Add a Certificate" +#: ../misc/variables/article.rst:1 +msgid "Article > Created" msgstr "" -#: ../settings/security/ssl-certificates.rst:33 -msgid "" -"To add a custom certificate or a custom CA certificate, head over to the " -"Admin panel > Settings > Security > SSL Certificates. Here you can find a " -"\"Add SSL Certificate\" button. In the dialog you can either select a " -"certificate file or paste the content of the certificate:" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_at}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate adding dialog" +#: ../misc/variables/article.rst:1 +msgid "``2019-10-08 15:24:47 UTC``" msgstr "" -#: ../settings/security/ssl-certificates.rst:43 -msgid "" -"After selecting a file or pasting the content of the certificate, click on " -"the \"Add\" button to finally upload it to Zammad. Then, the certificates " -"are immediately effective, no restart or similar required." +#: ../misc/variables/article.rst:1 +msgid "Article > From" msgstr "" -#: ../settings/security/ssl-certificates.rst:49 -msgid "" -"Please note that only single certificate files are supported. That means if " -"you want to import a certificate / CA certificate, it must contain **only " -"one** certificate." +#: ../misc/variables/article.rst:1 +msgid "``#{article.from}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:54 -msgid "Certificate Overview" +#: ../misc/variables/article.rst:1 +msgid "" +"``Joe Doe `` may differ, depends on ``FROM`` of send mail" msgstr "" -#: ../settings/security/ssl-certificates.rst:56 -msgid "" -"After you added a certificate, you can see a table with information for each " -"added certificate:" +#: ../misc/variables/article.rst:1 +msgid "Article > Sender > Name" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing table of added certificates" +#: ../misc/variables/article.rst:1 +msgid "``#{article.sender.name}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:64 -msgid "" -"Here you can download the certificate or delete it, if you don't need it " -"anymore." +#: ../misc/variables/article.rst:1 +msgid "``Customer``, ``Agent`` or ``System``" msgstr "" -#: ../settings/security/ssl-certificates.rst:68 -msgid "Deleting Certificates" +#: ../misc/variables/article.rst:1 +msgid "Article > Subject" msgstr "" -#: ../settings/security/ssl-certificates.rst:70 -msgid "" -"If you want to delete a specific certificate, you can do it by clicking on " -"the menu in the actions column and selecting delete:" +#: ../misc/variables/article.rst:1 +msgid "``#{article.subject}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate deletion button" +#: ../misc/variables/article.rst:1 +msgid "``My amazing subject``" msgstr "" -#: ../settings/security/ssl-certificates.rst:79 -msgid "Downloading Certificates" +#: ../misc/variables/article.rst:1 +msgid "Article > Text" msgstr "" -#: ../settings/security/ssl-certificates.rst:81 -msgid "" -"If you want to download your certificates, you can do this as well via " -"corresponding action buttons." +#: ../misc/variables/article.rst:1 +msgid "``#{article.body}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate download button" +#: ../misc/variables/article.rst:1 +msgid "``Test`` without formatting (plain)" msgstr "" -#: ../settings/security/third-party.rst:13 -msgid "Login Providers" +#: ../misc/variables/article.rst:1 +msgid "Article > TicketID" msgstr "" -#: ../settings/security/third-party.rst:2 -msgid "Third-Party Applications" +#: ../misc/variables/article.rst:1 +msgid "``#{article.ticket_id}``" msgstr "" -#: ../settings/security/third-party.rst:4 -msgid "" -"Third party authentication is a great way to help your users to login to " -"Zammad more easily. If the account is yet unknown, Zammad will create a new " -"user automatically, without the user needed to interact (e.g. type in his " -"name). Another big advantage of this feature is that your user doesn't need " -"to remember another password." +#: ../misc/variables/article.rst:1 +msgid "``1`` (not ticket number)" msgstr "" -#: ../settings/security/third-party.rst:10 -msgid "" -"You can deactivate logging in via :ref:`security_password_login` if any of " -"the mentioned authentication providers are enabled in your instance." +#: ../misc/variables/article.rst:1 +msgid "Article > To" msgstr "" -#: ../settings/security/third-party.rst:27 -msgid "" -"We're currently missing documentation for the following login providers:" +#: ../misc/variables/article.rst:1 +msgid "``#{article.to}``" msgstr "" -#: ../settings/security/third-party.rst:29 -msgid "LinkedIn" +#: ../misc/variables/article.rst:1 +msgid "``helpdesk@example.com``" msgstr "" -#: ../settings/security/third-party.rst:30 -msgid "Weibo" +#: ../misc/variables/article.rst:1 +msgid "Article > Type > Name" msgstr "" -#: ../settings/security/third-party.rst:35 -msgid "Automatic Account Link on Initial Logon" +#: ../misc/variables/article.rst:1 +msgid "``#{article.type.name}``" msgstr "" -#: ../settings/security/third-party.rst:37 +#: ../misc/variables/article.rst:1 msgid "" -"In general there's two possible options for Zammad on how to deal with " -"already known users as they try to authenticate against a third-party " -"application. By default, Zammad will not automatically link \"unknown\" " -"authentication providers to existing accounts." +"``email`` (`list of article types `_)" msgstr "" -#: ../settings/security/third-party.rst:42 -msgid "" -"This means that the user has to manually link authentication providers to " -"their accounts (for more about this :user-docs:`consult the user " -"documentation `)." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Address" msgstr "" -#: ../settings/security/third-party.rst:46 -msgid "" -"Sometimes this doesn't come in handy as this also means you'll receive error " -"messages about \"email address being in use already\" for (yet) unknown " -"third-party authentication methods." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.address}``" msgstr "" -#: ../settings/security/third-party.rst:50 -msgid "" -"If you want to allow your users to always be able to log in, no matter what, " -"you may want to enable ``Automatic account link on initial logon``." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Department" msgstr "" -#: ../settings/security/third-party.rst:None -msgid "" -"Screenshot highlighting the \"Automatic account link on initial logon\"\n" -"setting" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.department}``" msgstr "" -#: ../settings/security/third-party.rst:60 -msgid "Automatic Account Linking Notification" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Email" msgstr "" -#: ../settings/security/third-party.rst:64 -msgid "" -"To improve security and your users awareness, you can enable Zammad to " -"notify your users when a new third-party application has been linked to " -"their account." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.email}``" msgstr "" -#: ../settings/security/third-party.rst:68 -msgid "" -"This notification is sent out once per third-party application. Zammad does " -"also mention the method used, e.g.: ``Microsoft``." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Fax" msgstr "" -#: ../settings/security/third-party.rst:71 -msgid "By default this setting is not active (set to ``no``)." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.fax}``" msgstr "" -#: ../settings/security/third-party.rst:0 -msgid "" -"Screenshot showing sample notification mail after initial\n" -"third-party linking" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Firstname" msgstr "" -#: ../settings/security/third-party.rst:85 -msgid "" -"This notification is only sent if the account in question already exists. If " -"the login via the third-party also creates the missing account, the " -"notification will be skipped." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.firstname}``" msgstr "" -#: ../settings/security/third-party.rst:89 -msgid "This means it only affects:" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Lastname" msgstr "" -#: ../settings/security/third-party.rst:91 -msgid "manual account linking within the third-party page of the users profile" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.lastname}``" msgstr "" -#: ../settings/security/third-party.rst:92 -msgid "" -"logging into an existing local account by utilizing the *automatic account " -"link on initial logon* functionality" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Login" msgstr "" -#: ../settings/security/third-party.rst:None -msgid "" -"Screenshot showing the \"automatic account linking notification\"\n" -"setting" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.login}``" msgstr "" -#: ../settings/security/third-party.rst:100 -msgid "No User Creation on Logon" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Mobile" msgstr "" -#: ../settings/security/third-party.rst:102 -msgid "" -"By default, Zammad will create a new user account if the user logs in via a " -"third-party application and the account doesn't exist yet." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.mobile}``" msgstr "" -#: ../settings/security/third-party.rst:105 -msgid "" -"If you want to prevent Zammad from creating new accounts on logon, you can " -"disable this feature by setting ``No user creation on logon`` to ``yes``." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Note" msgstr "" -#: ../settings/security/third-party.rst:None -msgid "Screenshot showing the \"no user creation on logon\" setting" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.note}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via Facebook To do " -"so, you need to follow these steps:" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Phone" msgstr "" -#: ../settings/security/third-party/facebook.rst:9 -msgid "Register Facebook App" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.phone}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:11 -msgid "" -"Visit [https://developers.facebook.com/apps/] and click on \"Add a new App\"" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > VIP" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "initial page" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.vip}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:17 -msgid "After that enter the app settings" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Web" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "Create App" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.web}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:22 -msgid "Navigate to \"Settings\" and fill in this infromation" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "App Settings" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_at}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:27 -msgid "Navigate to app review and Check \"Make [appname] public?\"" +#: ../misc/variables/article.rst:1 +msgid "Article > Visibility" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "App Review" +#: ../misc/variables/article.rst:1 +msgid "``#{article.internal}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:35 -msgid "Configure Zammad as Facebook App" +#: ../misc/variables/article.rst:1 +msgid "``false`` or ``true`` (false if not internal)" msgstr "" -#: ../settings/security/third-party/facebook.rst:37 -msgid "" -"Navigate to \"Admin -> Security -> Third Party Applications\" and enter the " -"App ID and the App Secret. You can find this Key in the Dashbard of your " -"Facebok app." +#: ../misc/variables/article.rst:1 +msgid "Article Text as HTML (not referenced)" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "Zammad Configuration" +#: ../misc/variables/article.rst:1 +msgid "``#{article.body_as_html}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:44 -#: ../settings/security/third-party/github.rst:43 -#: ../settings/security/third-party/gitlab.rst:46 -msgid "" -"Now you can link accounts via \"Avatar -> Profile -> Link Accounts\" or " -"login via Zammad login page." +#: ../misc/variables/article.rst:1 +msgid "``Test`` with formatting" msgstr "" -#: ../settings/security/third-party/github.rst:2 -#: ../system/integrations/github.rst:2 -msgid "GitHub" +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "Ticket > Article#" msgstr "" -#: ../settings/security/third-party/github.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via GitHub. To " -"activate the quick login you need to enable OAuth for GitHub." +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "``#{ticket.article_count}``" msgstr "" -#: ../settings/security/third-party/github.rst:8 -msgid "Register GitHub App" +#: ../misc/variables/article.rst:1 +msgid "``1`` number of ticket articles" msgstr "" -#: ../settings/security/third-party/github.rst:10 -msgid "" -"Visit https://www.github.com/settings/applications/new and enter the app " -"settings. As callback URL enter \"https://zammad_host/auth/github/callback\" " -"where zammad_host has to be replaced with your Zammad FQDN" +#: ../misc/variables/config.rst:2 +msgid "Config" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "Register OAuth app on www.github.com" +#: ../misc/variables/config.rst:6 +msgid "" +"Below you'll find config related variables. These hold useful configuration " +"information that you can use within e.g. triggers to show necessary " +"information to your customer." msgstr "" -#: ../settings/security/third-party/github.rst:19 -msgid "Configure Zammad as GitHub App" +#: ../misc/variables/config.rst:11 +msgid "Config Variables" msgstr "" -#: ../settings/security/third-party/github.rst:21 -msgid "" -"Enter the \"APP ID\" and the \"APP SECRET\" from the GitHub OAUTH " -"Applications Dashboard" +#: ../misc/variables/config.rst:1 +msgid "Config > Fully Qualified Domain Name" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub config in Zammad admin interface" +#: ../misc/variables/config.rst:1 +msgid "``#{config.fqdn}``" msgstr "" -#: ../settings/security/third-party/github.rst:28 -msgid "" -"After you configured the GitHub credentials and activated the login method, " -"you should see a new icon on the login page." +#: ../misc/variables/config.rst:1 +msgid "``zammad.example.com``" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub logo on login page" +#: ../misc/variables/config.rst:1 +msgid "Config > HTTP type" msgstr "" -#: ../settings/security/third-party/github.rst:34 -msgid "" -"If you click on the icon you will be redirected to GitHub and see something " -"similar to this:" +#: ../misc/variables/config.rst:1 +msgid "``#{config.http_type}``" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub oauth page" +#: ../misc/variables/config.rst:1 +msgid "``https`` or ``http``" msgstr "" -#: ../settings/security/third-party/github.rst:40 -#: ../settings/security/third-party/gitlab.rst:42 -msgid "" -"When you grant the access you will be redirected to your Zammad instance and " -"logged in as a customer." +#: ../misc/variables/config.rst:1 +msgid "Config > Organization" msgstr "" -#: ../settings/security/third-party/gitlab.rst:2 -msgid "Gitlab" +#: ../misc/variables/config.rst:1 +msgid "``#{config.organization}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:4 +#: ../misc/variables/config.rst:1 msgid "" -"It is possible to create a quick login for your helpdesk via Gitlab. To " -"activate the quick login you need to enable OAuth for Gitlab." +"``Zammad GmbH`` value set in `Branding `_" msgstr "" -#: ../settings/security/third-party/gitlab.rst:8 -msgid "Register Gitlab App" +#: ../misc/variables/config.rst:1 +msgid "Config > Product Name" msgstr "" -#: ../settings/security/third-party/gitlab.rst:10 -msgid "To register an app in Gitlab open your profile and select applications." +#: ../misc/variables/config.rst:1 +msgid "``#{config.product_name}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:12 +#: ../misc/variables/config.rst:1 msgid "" -"As callback URL enter \"https://zammad-fqdn/auth/gitlab/callback\" where " -"zammad-fqdn has to be replaced with your Zammad FQDN" +"``Helpdesk`` value set in `Branding `_" msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Register OAuth app on gitlab instance" +#: ../misc/variables/config.rst:1 +msgid "Config > SystemID" msgstr "" -#: ../settings/security/third-party/gitlab.rst:18 -msgid "Just select *read_user* under scopes as in the screenshot and save it." +#: ../misc/variables/config.rst:1 +msgid "``#{config.system_id}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:21 -msgid "Configure Zammad as Gitlab App" +#: ../misc/variables/config.rst:1 +msgid "``31`` (value between 1 and 99)" msgstr "" -#: ../settings/security/third-party/gitlab.rst:23 -msgid "" -"Enter the \"APP ID\" and the \"APP SECRET\" from the Gitlab OAUTH " -"Applications Dashboard and your Gitlab-URL in the \"SITE\" field." +#: ../misc/variables/config.rst:1 +msgid "Config > Ticket Hook" msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab config in Zammad admin interface" +#: ../misc/variables/config.rst:1 +msgid "``#{config.ticket_hook}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:30 -msgid "" -"After you configured the Gitlab credentials and activated the login method, " -"you should see a new icon on the login page." +#: ../misc/variables/config.rst:1 +msgid "``Ticket#``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab logo on login page" +#: ../misc/variables/current-user.rst:2 +msgid "Current User" msgstr "" -#: ../settings/security/third-party/gitlab.rst:36 +#: ../misc/variables/current-user.rst:6 msgid "" -"If you click on the icon you will be redirected to Gitlab and see something " -"similar to this:" +"Current user variables always return values of the current user that caused " +"e.g. a trigger to run." msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab oauth page" +#: ../misc/variables/current-user.rst:8 +msgid "" +"Due to the above fact, these variables are often not (yet) set or available " +"for usage." msgstr "" -#: ../settings/security/third-party/google.rst:4 +#: ../misc/variables/current-user.rst:10 msgid "" -"With some easy and fast steps, you can enable Zammad to authenticate your " -"users via Google." +"In situations where e.g. schedulers or triggers run, this most likely is " +"nothing you want to use." msgstr "" -#: ../settings/security/third-party/google.rst:8 -msgid "Register a Google App" +#: ../misc/variables/current-user.rst:13 +msgid "Current User Variables" msgstr "" -#: ../settings/security/third-party/google.rst:10 -msgid "" -"First of all, we need to create a new project - you can skip this step if " -"you already have one." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Address" msgstr "" -#: ../settings/security/third-party/google.rst:15 -msgid "" -"Use this link to create a new project: https://console.cloud.google.com/" -"projectcreate" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.address}``" msgstr "" -#: ../settings/security/third-party/google.rst:18 -msgid "" -"Now expand the menu, expand \"APIs & Services\" and select \"Credentials\". " -"Go to the tab \"OAuth consent screen\" first and ensure to fill in the " -"requested information - without doing so you can't create credentials!" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set" msgstr "" -#: ../settings/security/third-party/google.rst:None -msgid "Creating a consent screen" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Avatar" msgstr "" -#: ../settings/security/third-party/google.rst:25 -msgid "" -"After filling in and saving the consent screen information, you can go to " -"the \"Credentials\" tab and create new \"OAuth client ID\"-Credentials." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/google.rst:28 -msgid "" -"Fill in the necessary information as follows and replace ``zammad_host`` " -"with your FQDN:" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "avatar picture with width and height in pixel (e.g. 60,60)" msgstr "" -#: ../settings/security/third-party/google.rst:31 -msgid "**Application type** ``[x] Web application``" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created at" msgstr "" -#: ../settings/security/third-party/google.rst:34 -msgid "**Authorized JavaScript origins** ``https://zammad_host/``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_at}``" msgstr "" -#: ../settings/security/third-party/google.rst:37 -msgid "" -"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" -"callback``" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC``" msgstr "" -#: ../settings/security/third-party/google.rst:None -msgid "Adding a new OAuth client ID" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Address" msgstr "" -#: ../settings/security/third-party/google.rst:43 -msgid "" -"After creating the credentials, go to your Zammad installation and navigate " -"to \"Admin > Security > Third Party Applications\" > Google. Enter your " -"Client ID and Client secret here." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.address}``" msgstr "" -#: ../settings/security/third-party/google.rst:None -msgid "Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Avatar" msgstr "" -#: ../settings/security/third-party/google.rst:50 -msgid "After submitting, the login via Google can be used." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:2 -msgid "Microsoft" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Department" msgstr "" -#: ../settings/security/third-party/microsoft.rst:4 -msgid "" -"Zammad's Microsoft connection allows your users with Microsoft accounts to " -"login. This works for Azure users as well and can be an alternative to :doc:" -"`/system/integrations/ldap/index`." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.department}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:10 -msgid "" -"This documentation part does not cover our :doc:`📧 Microsoft 365 email " -"channel `." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Sales`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screenshot showing Microsoft login button on Zammad login screen." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Email" msgstr "" -#: ../settings/security/third-party/microsoft.rst:30 -#: ../settings/security/third-party/microsoft.rst:53 -msgid "Supported account types:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.email}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:22 -msgid "" -"Please note that Zammad only supports these account types (App dependent):" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``jdoe@customer.tld``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:35 -msgid "Avatars of signing in users:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Fax" msgstr "" -#: ../settings/security/third-party/microsoft.rst:33 -msgid "" -"Zammad currently ignores user avatars. If the user is registered with e.g. " -"Gravatar, Zammad will fetch the avatar from there if enabled. See :doc:" -"`Zammad Image Service ` for more." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.fax}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:38 -msgid "Step 1 - Register a Microsoft App for Zammad" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``004930123464789`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:40 -msgid "" -"Login to the `Microsoft Azure Portal `_ and " -"navigate to App registrations to create a new app. Provide the requested " -"information as follows and register your app." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Firstname" msgstr "" -#: ../settings/security/third-party/microsoft.rst:46 -msgid "Name:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.firstname}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:45 -msgid "" -"Any meaningful name fitting, this name will be displayed to users trying to " -"authenticate with this app." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``John`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:49 -msgid "Choose one of the above mentioned account types (see Limitations)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Lastname" msgstr "" -#: ../settings/security/third-party/microsoft.rst:51 -msgid "" -"The correct account type depends on your use case. If you want to use the " -"authentication internal only, choose the first option. If you're unsure, use " -"the \"Help me choose...\" link." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.lastname}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:58 -msgid "Redirect URI (optional):" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Login" msgstr "" -#: ../settings/security/third-party/microsoft.rst:56 -msgid "" -"Select web and provide your callback URL. The callback URL looks like this: " -"``https://zammad.domain.tld/auth/microsoft_office365/callback``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.login}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to register a Microsoft app" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Mobile" msgstr "" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "Within **API permissions** add the following permissions:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.mobile}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:69 -msgid "``User.Read``" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``0049176123456789`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "Contacts" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Note" msgstr "" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "``Contacts.Read``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.note}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:73 -msgid "" -"You can find these permissions within *Microsoft Graph → Delegated " -"permissions*." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Some note to this user`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to add required API permissions" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Phone" msgstr "" -#: ../settings/security/third-party/microsoft.rst:80 -msgid "" -"Within **Certificates & secrets** create a new client secret. Note down the " -"returned secret **value** for later. **Do not** use the secret ID!" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.phone}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to create a new app secret" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``004930123456789`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:88 -msgid "" -"From **Overview** copy your apps *Application (client) ID*. If you're using " -"a single tenant app, please also copy *Directory (tenant) ID*. You now have " -"all required information for Zammad." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > VIP" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to retreive application client and tenant IDs" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.vip}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:98 -msgid "Step 2 - Add App Credentials to Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Web" msgstr "" -#: ../settings/security/third-party/microsoft.rst:100 -msgid "" -"Navigate to Security > Third-party Applications (Tab) within Zammad's admin " -"settings. Scroll down to the section *Authentication via Microsoft* and fill " -"in the required information." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.web}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:105 -msgid "App ID:" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``https://zammad.org`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:105 -msgid "This is your *Application (client) ID*." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Department" msgstr "" -#: ../settings/security/third-party/microsoft.rst:108 -msgid "App secret:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.department}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:108 -msgid "This is your *client secret* (value)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Email" msgstr "" -#: ../settings/security/third-party/microsoft.rst:113 -msgid "App Tenant ID:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.email}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:111 -msgid "" -"**optional** only required for apps that use account type *Accounts in this " -"organizational directory only (Default Directory only - Single tenant).*" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Fax" msgstr "" -#: ../settings/security/third-party/microsoft.rst:115 -msgid "" -"Apply your settings by pressing submit and activate *Authentication via " -"Microsoft*." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.fax}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "" -"Screencast showing how to add app credentials and activating the\n" -"authentication method" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Firstname" msgstr "" -#: ../settings/security/third-party/saml.rst:2 -msgid "SAML" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.firstname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:4 -msgid "" -"Connect your SAML (Security Assertion Markup Language) identity provider as " -"a single sign-on (SSO) method." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Lastname" msgstr "" -#: ../settings/security/third-party/saml.rst:7 -msgid "" -"SAML is an open standard for SSO authentication (among other things). Sign-" -"ins are shared across multiple **service providers** and managed by a " -"central **identity provider** (IdP)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.lastname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:11 -msgid "" -"In this case, the service provider is Zammad, and the IdP is a software " -"service that you either host or subscribe to (*e.g.,* `Keycloak `_, `Redhat SSO Server `_, `ADFS `_, or `Okta `_)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Login" msgstr "" -#: ../settings/security/third-party/saml.rst:18 -msgid "" -"This guide assumes you are already using SAML within your organization (i." -"e., that your IdP is fully set up)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.login}``" msgstr "" -#: ../settings/security/third-party/saml.rst:21 -msgid "" -"Please note: Our instructions are based on connecting Zammad with Keycloak." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Mobile" msgstr "" -#: ../settings/security/third-party/saml.rst:25 -msgid "Step 1: Configure Your IdP" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.mobile}``" msgstr "" -#: ../settings/security/third-party/saml.rst:28 -msgid "Add Zammad as a Client/App" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Note" msgstr "" -#: ../settings/security/third-party/saml.rst:30 -msgid "" -"Import Zammad into your IdP using the XML configuration found at ``https://" -"your.zammad.domain/auth/saml/metadata``." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.note}``" msgstr "" -#: ../settings/security/third-party/saml.rst:33 -msgid "" -"If your IdP doesn't support XML import, you will have to configure Zammad as " -"a new client/app manually using the above XML metadata file for reference." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Domain based assignment" msgstr "" -#: ../settings/security/third-party/saml.rst:36 -msgid "For instance, when you see this tag:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.domain_assignment}``" msgstr "" -#: ../settings/security/third-party/saml.rst:42 -msgid "" -"Set the **Assertion Consumer Service Binding URL** (sometimes also listed as " -"**Valid Redirect URIs**) to ``http://your.zammad.domain/auth/saml/callback``." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Domain" msgstr "" -#: ../settings/security/third-party/saml.rst:47 -msgid "Set Up User Attribute Mapping" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.domain}``" msgstr "" -#: ../settings/security/third-party/saml.rst:49 -msgid "" -"Zammad requests the following user attributes (or “properties”) from the IdP:" +#: ../misc/variables/current-user.rst:1 +msgid "``zammad.com`` or empty if not set" msgstr "" -#: ../settings/security/third-party/saml.rst:51 -msgid "Email address (``email``)" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Name" msgstr "" -#: ../settings/security/third-party/saml.rst:52 -msgid "Full name (``name``)" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.name}``" msgstr "" -#: ../settings/security/third-party/saml.rst:53 -msgid "Given name (``first_name``)" +#: ../misc/variables/current-user.rst:1 +msgid "``Zammad GmbH``" msgstr "" -#: ../settings/security/third-party/saml.rst:54 -msgid "Family name (``last_name``)" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Note" msgstr "" -#: ../settings/security/third-party/saml.rst:56 -msgid "" -"You may need to set up “mappers” (or “mappings”) to tell your IdP how user " -"attributes in SAML correspond to those in Zammad. For a more detailed " -"breakdown, refer to the XML metadata file referenced in the previous section." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.note}``" msgstr "" -#: ../settings/security/third-party/saml.rst:62 -msgid "Per-IdP Instructions" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``A note to the organization of the user`` or empty if not set" msgstr "" -#: ../settings/security/third-party/saml.rst:102 -msgid "Keycloak" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Shared organization" msgstr "" -#: ../settings/security/third-party/saml.rst:65 -msgid "" -"**To add Zammad as a client,** save the XML configuration to disk (``https://" -"your.zammad.domain/auth/saml/metadata``) and use **Clients > Clients list > " -"Import client** in the Keycloak admin panel." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.shared}``" msgstr "" -#: ../settings/security/third-party/saml.rst:70 -msgid "" -"To help Zammad **match its own user accounts to Keycloak users**, create a " -"user attribute (or “property”) mapper. In **Clients list**, click on your " -"newly created Client ID, choose the tab **Client scopes** and click on the " -"link which refers to your Zammad instance. Choose **Add mapper > By " -"configuration > User Property** and create a mapper with the following " -"entries:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > VIP" msgstr "" -#: ../settings/security/third-party/saml.rst:78 -msgid "**Name**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.vip}``" msgstr "" -#: ../settings/security/third-party/saml.rst:80 -msgid "**Mapper Type**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Phone" msgstr "" -#: ../settings/security/third-party/saml.rst:81 -msgid "``User Property``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.phone}``" msgstr "" -#: ../settings/security/third-party/saml.rst:82 -msgid "**Property**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated at" msgstr "" -#: ../settings/security/third-party/saml.rst:83 -msgid "``emailAddress``" -msgstr "" - -#: ../settings/security/third-party/saml.rst:84 -msgid "**SAML Attribute Name**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_at}``" msgstr "" -#: ../settings/security/third-party/saml.rst:86 -msgid "**SAML Attribute NameFormat**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Address" msgstr "" -#: ../settings/security/third-party/saml.rst:87 -msgid "``basic``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.address}``" msgstr "" -#: ../settings/security/third-party/saml.rst:89 -msgid "" -"In the example above, we're telling Zammad that whenever it receives a SAML " -"login request, it should take the ``email`` property from Keycloak, look for " -"a Zammad user with the same ``email`` attribute, and create a new session " -"for that user." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Avatar" msgstr "" -#: ../settings/security/third-party/saml.rst:95 -msgid "" -"If your Keycloak users' email addresses are stored on another property (*e." -"g.,* ``username``), adjust accordingly." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/saml.rst:98 -msgid "" -"Back in **Settings**, enter the Client ID (``https://your.zammad.domain/auth/" -"saml/metadata``) in the field **Master SAML Processing URL**." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Department" msgstr "" -#: ../settings/security/third-party/saml.rst:101 -msgid "You also need to enable **Sign assertions**." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.department}``" msgstr "" -#: ../settings/security/third-party/saml.rst:105 -msgid "Step 2: Configure Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Email" msgstr "" -#: ../settings/security/third-party/saml.rst:107 -msgid "" -"Enable SAML and enter your IdP's details in the Admin Panel under **Settings " -"> Security > Third Party Applications > Authentication via SAML**:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.email}``" msgstr "" -#: ../settings/security/third-party/saml.rst:None -msgid "Example configuration of SAML part 1" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Fax" msgstr "" -#: ../settings/security/third-party/saml.rst:119 -msgid "Display name" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.fax}``" msgstr "" -#: ../settings/security/third-party/saml.rst:116 -msgid "" -"Allows you to define a custom button name for SAML. This helps your users to " -"understand better what the button on the login page does." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Firstname" msgstr "" -#: ../settings/security/third-party/saml.rst:119 -msgid "Defaults to ``SAML``." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.firstname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:123 -msgid "IDP SSO target URL" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Lastname" msgstr "" -#: ../settings/security/third-party/saml.rst:122 -msgid "" -"This is the target URL Zammad shall redirect to when the user presses the " -"SAML button. For Keycloak, this needs to look like https://your.domain/" -"realms/your-realm/protocol/saml" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.lastname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:127 -msgid "IDP single logout target URL" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Login" msgstr "" -#: ../settings/security/third-party/saml.rst:126 -msgid "" -"This is the URL to which the single logout request and response should be " -"sent." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.login}``" msgstr "" -#: ../settings/security/third-party/saml.rst:131 -msgid "IDP certificate" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Mobile" msgstr "" -#: ../settings/security/third-party/saml.rst:130 -msgid "" -"The public certificate of your IDP for Zammad to verify during the callback " -"phase." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.mobile}``" msgstr "" -#: ../settings/security/third-party/saml.rst:145 -msgid "IDP certificate fingerprint" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Note" msgstr "" -#: ../settings/security/third-party/saml.rst:134 -msgid "" -"The fingerprint of your IDPs public certificate to verify during callback " -"phase." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.note}``" msgstr "" -#: ../settings/security/third-party/saml.rst:137 -msgid "🔏 **For the IdP certificate / certificate fingerprint:**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Phone" msgstr "" -#: ../settings/security/third-party/saml.rst:139 -msgid "" -"Provide **only one or the other**—do not provide both! (Between the two, we " -"recommend the signing certificate itself: fingerprints use SHA-1, which `has " -"been broken for a while now `_.)" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.phone}``" msgstr "" -#: ../settings/security/third-party/saml.rst:144 -msgid "" -"**Keycloak users:** Find your certificate in the Keycloak admin panel under " -"**Realm Settings > Keys > Algorithm: RS256 > Certificate**." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > VIP" msgstr "" -#: ../settings/security/third-party/saml.rst:151 -msgid "Name identifier format" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.vip}``" msgstr "" -#: ../settings/security/third-party/saml.rst:148 -msgid "" -"This is the unique identifiers field type. Usually it should be ``urn:oasis:" -"names:tc:SAML:1.1:nameid-format:emailAddress``." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``false`` or ``true``" msgstr "" -#: ../settings/security/third-party/saml.rst:151 -msgid "Zammad **expects an email address as unique identifier**!" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Web" msgstr "" -#: ../settings/security/third-party/saml.rst:155 -msgid "UID attribute name" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.web}``" msgstr "" -#: ../settings/security/third-party/saml.rst:154 -msgid "" -"Here you can define an attribute that uniquely identifies the user. If " -"unset, the name identifier returned by the IDP is used." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > VIP" msgstr "" -#: ../settings/security/third-party/saml.rst:None -msgid "Example configuration of SAML part 2" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.vip}``" msgstr "" -#: ../settings/security/third-party/saml.rst:163 -msgid "" -"Decide if the certificate for the connection to the IdP service has to be " -"verified or not (default: ``yes``)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Web" msgstr "" -#: ../settings/security/third-party/saml.rst:169 -msgid "Signing & Encrypting" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.web}``" msgstr "" -#: ../settings/security/third-party/saml.rst:169 +#: ../misc/variables/ticket.rst:6 msgid "" -"Define if you want to sign, encrypt, do both or nothing for the requests." +"Below you can find all available ticket-based variables within Zammad. These " +"can be called via triggers for example. If you're unsure if Zammad does " +"support variables at the point you're at, you can try to type ``::`` to " +"check." msgstr "" -#: ../settings/security/third-party/saml.rst:179 -msgid "Certificate (PEM)" +#: ../misc/variables/ticket.rst:12 +msgid "Ticket Variables" msgstr "" -#: ../settings/security/third-party/saml.rst:172 -msgid "" -"Paste the public certificate of your Zammad SAML client, if you want to " -"encrypt the requests." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Accounted Time" msgstr "" -#: ../settings/security/third-party/saml.rst:175 -msgid "Make sure the certificate is:" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.time_unit}``" msgstr "" -#: ../settings/security/third-party/saml.rst:177 -msgid "already valid and not yet expired" +#: ../misc/variables/ticket.rst:1 +msgid "``1``, ``2.75`` or empty response" msgstr "" -#: ../settings/security/third-party/saml.rst:178 -msgid "no CA certificate" +#: ../misc/variables/ticket.rst:1 +msgid "``3``, any number of articles existing in the ticket right now" msgstr "" -#: ../settings/security/third-party/saml.rst:179 -msgid "valid for signing and encrypting" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Closing time" msgstr "" -#: ../settings/security/third-party/saml.rst:185 -msgid "Private key (PEM)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.close_at}``" msgstr "" -#: ../settings/security/third-party/saml.rst:182 -msgid "" -"Paste the private key of your Zammad SAML client here, if you want to sign " -"the requests." +#: ../misc/variables/ticket.rst:1 +msgid "2019-10-07 17:25:00 UTC" msgstr "" -#: ../settings/security/third-party/saml.rst:185 -msgid "Make sure the key is an RSA key with a length of at least 2048 bits." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created at" msgstr "" -#: ../settings/security/third-party/saml.rst:188 -msgid "Private key secret" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_at}``" msgstr "" -#: ../settings/security/third-party/saml.rst:188 -msgid "If your private key is secured with a secret, you can provide it here." +#: ../misc/variables/ticket.rst:1 +msgid "2019-10-07 16:25:00 UTC" msgstr "" -#: ../settings/security/third-party/saml.rst:192 -msgid "Your callback URL" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Address" msgstr "" -#: ../settings/security/third-party/saml.rst:191 -msgid "" -"This URL is needed for your IdP configuration so it knows where to redirect " -"to after successful authentication." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.address}``" msgstr "" -#: ../settings/security/third-party/saml.rst:194 -msgid "" -"After saving your input by clicking on the \"Submit\" button, Zammad " -"verifies the provided keys/certificates (e.g. if they are valid for signing/" -"encrypting and if they aren't expired)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Avatar" msgstr "" -#: ../settings/security/third-party/saml.rst:199 -msgid "" -"See :ref:`automatic account linking ` for details " -"on how to link existing Zammad accounts to IdP accounts." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/saml.rst:205 -msgid "Automatic account linking doesn't work" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Department" msgstr "" -#: ../settings/security/third-party/saml.rst:206 -msgid "" -"Have you double-checked your IdP's user attribute mapping configuration?" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.department}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via Twitter. To do " -"so, you need to follow these steps:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Email" msgstr "" -#: ../settings/security/third-party/twitter.rst:8 -msgid "Register Twitter App" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.email}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:10 -msgid "Go to https://dev.twitter.com/apps and login with your account." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Fax" msgstr "" -#: ../settings/security/third-party/twitter.rst:15 -msgid "Click on \"Create App\"" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.fax}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "new app page" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Firstname" msgstr "" -#: ../settings/security/third-party/twitter.rst:20 -msgid "" -"Enter app settings. As \"Callback URL\" you need to enter ``https://" -"zammad_host/api/v1/external_credentials/twitter/callback``. You need to " -"replace ``zammad_host`` with the domain of your Zammad system." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.firstname}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:24 -msgid "" -"After the app has been created, update the application icon and organization " -"attributes." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Lastname" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "set permissions to receive and send direct messages" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.lastname}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:30 -msgid "" -"Next we need to set ``read, write and access direct messages`` permissions " -"for the app." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Login" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "click on Keys & Access Token, note them" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.login}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:36 -msgid "" -"Go to \"Keys and Access Token\" tab and note the \"Consumer Key\" and " -"\"Consumer Secret\"." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Mobile" msgstr "" -#: ../settings/security/third-party/twitter.rst:40 -msgid "Configure Zammad as Twitter App" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.mobile}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:42 -msgid "" -"Go to \"Admin > Security > Twitter > Third Party Applications > Twitter\" " -"Section." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Note" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "Admin > Security > Third Party Applications" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.note}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:48 -msgid "" -"Fill in the \"Twitter Key\" and the \"Twitter Secret\" and click the " -"\"Submit\" button." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Phone" msgstr "" -#: ../settings/security/third-party/twitter.rst:51 -msgid "" -"Now you can link accounts via \"Avatar > Profile > Link Accounts\" or login " -"via Zammad login page." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.phone}``" msgstr "" -#: ../settings/security/two-factor.rst:11 -msgid "Two-factor Authentication Methods" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > VIP" msgstr "" -#: ../settings/security/two-factor.rst:2 -msgid "Two-Factor Authentication" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.vip}``" msgstr "" -#: ../settings/security/two-factor.rst:4 -msgid "" -"Two-factor authentication (2FA) enhances the security of Zammad accounts by " -"adding an extra layer of verification beyond a password. It requires users " -"to provide two different types of authentication factors, typically " -"something they know (like a password) and something they possess (like a " -"mobile device or a security token), to ensure that only authorized " -"individuals can access the account." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Web" msgstr "" -#: ../settings/security/two-factor.rst:19 -msgid "Enable Recovery Codes" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.web}``" msgstr "" -#: ../settings/security/two-factor.rst:21 -msgid "" -"Recovery codes are one-time use security codes that can be used by the user " -"if they lose access to their other two-factor authentication methods. They " -"cannot be used on their own, they can only be activated if at least one two-" -"factor authentication method is enabled." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Address" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Enable Recovery Codes Setting" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.address}``" msgstr "" -#: ../settings/security/two-factor.rst:30 -msgid "" -"Recovery codes can only be used as a backup method. If enabled, they will be " -"automatically generated for the user once they set up their initial two-" -"factor authentication method." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Avatar" msgstr "" -#: ../settings/security/two-factor.rst:34 -msgid "" -"The user will be asked to print out or save the generated recovery codes in " -"a safe place. Once used, a recovery code cannot be reused." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.avatar(60,60)}``" msgstr "" -#: ../settings/security/two-factor.rst:37 -msgid "" -"Users will also have an option to regenerate their recovery codes at any " -"time, which invalidates already existing recovery codes and provides them " -"with a list of fresh codes." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Department" msgstr "" -#: ../settings/security/two-factor.rst:41 -msgid "" -"After you enable this setting, when the user completes a setup of their " -"initial two-factor authentication method, they will be presented with a list " -"of recovery codes and instructed to save them for later use." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.department}``" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Recovery Codes Generation Modal Dialog" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Email" msgstr "" -#: ../settings/security/two-factor.rst:50 -msgid "Enforce the Set Up of the Two-Factor Authentication" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.email}``" msgstr "" -#: ../settings/security/two-factor.rst:52 -msgid "" -"In case you wish to require your users to set up at least one two-factor " -"authentication method for their account, you can do this by selecting " -"specific user roles the requirement applies to in **Enforced for user " -"roles** setting. Of course you must have at least one two-factor " -"authentication method enabled for this setting to take effect." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Fax" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Enforced for User Roles Setting" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.fax}``" msgstr "" -#: ../settings/security/two-factor.rst:62 -msgid "" -"After you change this setting, if the user has one of the selected roles on " -"their account, they will be forced to set up the two-factor authentication " -"upon next sign in or application reload." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Firstname" msgstr "" -#: ../settings/security/two-factor.rst:66 -msgid "" -"A modal dialog with instructions will be shown, and they will not be able to " -"do any work before they set up at least one two-factor method." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.firstname}``" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Modal Dialog for Enforcing Two-Factor Authentication Set Up" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Lastname" msgstr "" -#: ../settings/security/two-factor.rst:74 -msgid "Reset Two-Factor Authentication for a Specific User" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.lastname}``" msgstr "" -#: ../settings/security/two-factor.rst:76 -msgid "" -"In case an user isn't able to login anymore because of an inaccessible " -"second factor, you can reset the user's 2FA method." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Login" msgstr "" -#: ../settings/security/two-factor.rst:79 -msgid "" -"To do this, go to the user management and search for the relevant user. " -"After you found the account, click the button in the action column and " -"select \"Manage Two-Factor Authentication\":" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.login}``" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Context menu in action column in user management" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Mobile" msgstr "" -#: ../settings/security/two-factor.rst:87 -msgid "" -"After selecting this, you can see a dialog where you can either reset one " -"2FA method or reset all of the user's 2FA methods:" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.mobile}``" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Dialog for resetting user's 2FA method" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Note" msgstr "" -#: ../settings/security/two-factor.rst:94 -msgid "" -"Choose the fitting one, click on the corresponding \"Remove ...\" button and " -"confirm your action. The user now has to setup a new 2FA method, depending " -"on your 2FA configuration." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.note}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:2 -msgid "Authenticator App" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Phone" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:4 -msgid "" -"The authenticator app method is a type of two-factor authentication that " -"uses a mobile application to generate one-time codes for account " -"verification. After setting up the authenticator app on their device, the " -"user links it to their Zammad account." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.phone}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:12 -msgid "" -"When logging in, the user is prompted to enter a time-sensitive code " -"generated by the app, in addition to their password. This code acts as the " -"second factor of authentication, providing an extra layer of security as it " -"changes periodically and is unique to the user's device." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > VIP" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:None -msgid "Security Code in Google Authenticator App" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.vip}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:22 -msgid "" -"The app generates codes based on a shared secret key stored securely on both " -"the user's device and the server, ensuring a synchronized and secure " -"authentication process. The method of generating the codes is sometimes also " -"called TOTP (time-based one-time password)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Web" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:28 -msgid "Enabling the Authenticator App Method" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.web}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:30 -#: ../settings/security/two-factor/security-keys.rst:28 -msgid "To enable the method, just toggle the switch on in the settings." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Escalation at" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:None -msgid "Authenticator App Switch in Settings" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.escalation_at}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:36 -msgid "" -"Now the users will be able to set up this two-factor authentication method " -"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " -"Once they do, on next sign-in with password, they will be asked to provide " -"an additional security code generated by their mobile device." +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:2 -msgid "Security Keys" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > First response" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:4 -msgid "" -"The security keys method is a type of a two-factor authentication that uses " -"Web Authentication API in the browser for verifying user's identity. The " -"user can register multiple hardware or software security keys with their " -"Zammad account and then they can use it during the sign-in process." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.first_response_at}``" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:12 -msgid "" -"When logging in, the user is prompted to provide the same security key they " -"registered with their account, in addition to their password. This key acts " -"as the second factor of authentication, providing an extra layer of security." +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable yet" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:None -msgid "Security Key dialog in Safari on macOS" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Assign Follow-Ups" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:21 -msgid "" -"The type of the key can range from hardware USB sticks to passkeys stored in " -"a device of user's choice. Which type can be used depends on the browser " -"flavor and the platform of the user." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_assignment}``" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:26 -msgid "Enabling the Security Keys Method" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Assignment Timeout" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:None -msgid "Security Keys Switch in Settings" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.assignment_timeout}``" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:34 -msgid "" -"Now the users will be able to set up this two-factor authentication method " -"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " -"Once they do, on next sign-in with password, they will be asked to provide " -"the same security key they registered during the setup." +#: ../misc/variables/ticket.rst:1 +msgid "``20`` or empty if not configured" msgstr "" -#: ../settings/system/system-selfhosted.include.rst:3 -msgid "" -"Below settings are only available to self hosted users. In hosted " -"environments we're handling these settings for you to ensure service " -"stability." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Follow-up possible" msgstr "" -#: ../settings/system/base.rst:11 -msgid "Fully Qualified Domain Name" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_possible}``" msgstr "" -#: ../settings/system/base.rst:7 -msgid "The URL of your Zammad installation." +#: ../misc/variables/ticket.rst:1 +msgid "``no`` or ``yes``" msgstr "" -#: ../settings/system/base.rst:9 ../settings/system/base.rst:17 -msgid "This setting is used within :doc:`/system/variables` and notifications." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Name" msgstr "" -#: ../settings/system/system-base.include.rst:1 -msgid "It is automatically set by the *Getting Started wizard*." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.name}``" msgstr "" -#: ../settings/system/system-base.include.rst:5 -msgid "Changing this setting also changes callback URLs for your channels etc." +#: ../misc/variables/ticket.rst:1 +msgid "``Sales``" msgstr "" -#: ../settings/system/system-base.include.rst:6 -msgid "This setting can have negative affects on being able to login." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Note" msgstr "" -#: ../settings/system/base.rst:19 -msgid "HTTP type" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.note}``" msgstr "" -#: ../settings/system/base.rst:14 -msgid "" -"The HTTP type tells your installation how your clients connect. This is " -"relevant for authentication and cookie security." +#: ../misc/variables/ticket.rst:1 +msgid "``Note about this group``" msgstr "" -#: ../settings/system/base.rst:31 -msgid "SystemID" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > ID" msgstr "" -#: ../settings/system/base.rst:22 -msgid "" -"This ID is being used within your ticket number. In case you're " -"communicating with another ticket system with similar ticket number schemes " -"this ID greatly reduces the risk of false follow ups." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.id}``" msgstr "" -#: ../settings/system/base.rst:26 -msgid "" -"The SystemID is randomly selected upon installation of Zammad (``1-99``)." +#: ../misc/variables/ticket.rst:1 +msgid "``17``, ``5281``, ..." msgstr "" -#: ../settings/system/base.rst:30 -msgid "" -"**Do not** change this setting in a productive system! Your Zammad " -"installation may no longer recognize old ticket number based follow ups upon " -"change!" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact (agent)" msgstr "" -#: ../settings/system/frontend.rst:2 -msgid "Frontend" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_agent_at}``" msgstr "" -#: ../settings/system/frontend.rst:22 -msgid "Core Workflow Ajax Mode" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact (customer)" msgstr "" -#: ../settings/system/frontend.rst:6 +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_customer_at}``" +msgstr "" + +#: ../misc/variables/ticket.rst:1 msgid "" -"This setting allows administrators to enforce :doc:`/system/core-workflows` " -"to use Ajax-Calls instead of web sockets. You'll usually only need this if " -"you experience serious issues as noted below." +"``2019-10-07 16:25:00 UTC`` or empty if not applicable yet (Please note " +"`Ticket last contact behavior Settings `_ for this)" msgstr "" -#: ../settings/system/frontend.rst:10 -msgid "**🤓 Possible (technical) reasons**" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact" msgstr "" -#: ../settings/system/frontend.rst:12 -msgid "" -"In some cases, your network structure (e.g. firewalls, proxies) may " -"disconnect long web socket connections. This leads to select fields staying " -"empty (e.g. owner selection *after* selecting your group) or fields not " -"shown / hidden (e.g. when switching to or from pending states, the \"pending " -"till\" field not showing / hiding)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_at}``" msgstr "" -#: ../settings/system/frontend.rst:18 -msgid "" -"Please keep in mind that the Ajax fallback may cause serious pressure on " -"your application server. If you have the choice stick to web sockets." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Number" msgstr "" -#: ../settings/system/frontend.rst:22 -msgid "Default: ``no`` (inactive)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.number}``" msgstr "" -#: ../settings/system/frontend.rst:53 -msgid "Show calendar weeks in the picker of date/datetime fields" +#: ../misc/variables/ticket.rst:1 +msgid "``31001``, ``201910731001``, ..." msgstr "" -#: ../settings/system/frontend.rst:25 -msgid "" -"With this setting you can instruct Zammad to provide week number display " -"globally for all users. Calendar with week number display are usually used " -"in business sectors and may not be relevant for everyone." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain based assignment" msgstr "" -#: ../settings/system/frontend.rst:29 -msgid "" -"This setting affects *all areas* - you'll also see week numbers in the admin " -"panel for e.g. triggers and macros." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain_assignment}``" msgstr "" -#: ../settings/system/frontend.rst:32 -msgid "Default: ``no`` (not shown)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain" msgstr "" -#: ../settings/system/frontend.rst:53 -msgid "Here's the difference:" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain}``" msgstr "" -#: ../settings/system/frontend.rst:0 -msgid "Screenshot showing Zammad's date picker (in the default way)" +#: ../misc/variables/ticket.rst:1 +msgid "``domain.tld`` or empty if not set" msgstr "" -#: ../settings/system/frontend.rst:41 -msgid "Set to ``no``" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Name" msgstr "" -#: ../settings/system/frontend.rst:0 -msgid "" -"Screenshot showing Zammad's date picker with\n" -"week numbers enabled" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.name}``" msgstr "" -#: ../settings/system/frontend.rst:50 -msgid "Set to ``yes``" +#: ../misc/variables/ticket.rst:1 +msgid "``Zammad GmbH`` or empty if not set" msgstr "" -#: ../settings/system/index.rst:4 -msgid "" -"For your overview we split each tab within system settings into its own page:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Note" msgstr "" -#: ../settings/system/index.rst:16 -msgid "Console Based Settings" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.note}``" msgstr "" -#: ../settings/system/index.rst:18 -msgid "" -"There's some console based settings we didn't put into the UI. However, you " -"may find them helpful - you can find them in our :docs:`hidden settings ` section." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Shared organization" msgstr "" -#: ../settings/system/network.rst:2 -msgid "Network" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.shared}``" msgstr "" -#: ../settings/system/network.rst:8 -msgid "" -"The proxy settings can only be saved after successfully testing the proxy " -"connection." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > VIP" msgstr "" -#: ../settings/system/network.rst:15 -msgid "Proxy Address." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.vip}``" msgstr "" -#: ../settings/system/network.rst:12 -msgid "" -"Allows you to provide a proxy server if needed. This is relevant for network " -"communication by Zammad." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Address" msgstr "" -#: ../settings/system/network.rst:15 -msgid "It **does not** affect the update process or Elasticsearch." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.address}``" msgstr "" -#: ../settings/system/network.rst:18 -msgid "Username for proxy connection." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Avatar" msgstr "" -#: ../settings/system/network.rst:18 -msgid "" -"If your proxy server requires authentication, provide the username here." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.avatar(60,60)}``" msgstr "" -#: ../settings/system/network.rst:21 -msgid "Password for proxy connection." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Department" msgstr "" -#: ../settings/system/network.rst:21 -msgid "" -"If your proxy server requires authentication, provide the password here." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.department}``" msgstr "" -#: ../settings/system/network.rst:26 -msgid "No proxy for the following hosts." +#: ../misc/variables/ticket.rst:1 +msgid "``Support`` or empty if not set" msgstr "" -#: ../settings/system/network.rst:24 -msgid "" -"Exception list for hosts you can't or don't want to reach via proxy server." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Email" msgstr "" -#: ../settings/system/network.rst:27 -msgid "Default: ``localhost,127.0.0.0,::1``" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.email}``" msgstr "" -#: ../settings/system/services.rst:2 -msgid "Services" +#: ../misc/variables/ticket.rst:1 +msgid "``agent@company.tld`` or empty if not set" msgstr "" -#: ../settings/system/services.rst:10 -msgid "Image Service" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Fax" msgstr "" -#: ../settings/system/services.rst:5 -msgid "Defines the backend for user and organization image lookups." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.fax}``" msgstr "" -#: ../settings/system/services.rst:7 -msgid "Default: ``Zammad Image Service`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Firstname" msgstr "" -#: ../settings/system/services.rst:9 -msgid "" -"Make sure your on premise installation has ``HTTPS`` access to ``images." -"zammad.com``." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.firstname}``" msgstr "" -#: ../settings/system/services.rst:18 -msgid "Geo Calendar Service" +#: ../misc/variables/ticket.rst:1 +msgid "``Max`` or empty if not set" msgstr "" -#: ../settings/system/services.rst:13 -msgid "" -"Defines the backend for geo calendar lookups. Used for initial calendar " -"setup." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Lastname" msgstr "" -#: ../settings/system/services.rst:16 -msgid "Default: ``Zammad GeoCalendar Service`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.lastname}``" msgstr "" -#: ../settings/system/services.include.rst:2 -msgid "" -"Make sure your on premise installation has ``HTTPS`` access to ``geo.zammad." -"com``." +#: ../misc/variables/ticket.rst:1 +msgid "``Mustermann`` or empty if not set" msgstr "" -#: ../settings/system/services.rst:26 -msgid "Geo IP Service" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Login" msgstr "" -#: ../settings/system/services.rst:21 -msgid "" -"Defines the backend for geo IP lookups. Shows also location of an IP address " -"if an IP address is shown." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.login}``" msgstr "" -#: ../settings/system/services.rst:24 -msgid "Default: ``Zammad GeoIP Service`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "``agent``" msgstr "" -#: ../settings/system/services.rst:32 -msgid "Geo Location Service" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Mobile" msgstr "" -#: ../settings/system/services.rst:29 -msgid "" -"Defines the backend for geo location lookups to store geo locations for " -"addresses." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.mobile}``" msgstr "" -#: ../settings/system/services.rst:32 -msgid "" -"Default: ``OpenStreetMap (ODbL 1.0, http://osm.org/copyright)`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Note" msgstr "" -#: ../settings/system/services.rst:36 -msgid "" -"You can find a detailed privacy information on what we store for how long on " -"our :docs:`Privacy Appendix ` inside of our System " -"Documentation." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.note}``" msgstr "" -#: ../settings/system/storage.rst:2 -msgid "Storage" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Phone" msgstr "" -#: ../settings/system/storage.rst:6 -msgid "" -"Here you can define where Zammad stores attachments for tickets and the " -"knowledge base. By default, we're writing to the ``Database`` - you can " -"switch to ``Filesystem`` or ``Simple Storage (S3)`` at any time. In this " -"case please have a look on the following instructions." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.phone}``" msgstr "" -#: ../settings/system/storage.rst:11 -msgid "" -"If you have a busy Zammad instance, we strongly encourage you to use " -"filesystem storage instead of \"Database\". This will greatly improve system " -"performance (de-crease database load and size)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > VIP" msgstr "" -#: ../settings/system/storage.rst:19 -msgid "Database" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.vip}``" msgstr "" -#: ../settings/system/storage.rst:17 -msgid "" -"This is the default storage method. The attachments are stored directly in " -"the database. If your Zammad instance grows, we recommend one of the other " -"methods to maintain performance." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Web" msgstr "" -#: ../settings/system/storage.rst:38 -msgid "Filesystem" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.web}``" msgstr "" -#: ../settings/system/storage.rst:22 -msgid "" -"This storage method is recommended for all Zammad instances, especially for " -"those with a higher load. If you choose filesystem, your files are written " -"to ``/opt/zammad/storage/``." +#: ../misc/variables/ticket.rst:1 +msgid "``https://zammad.com`` or empty if not set" msgstr "" -#: ../settings/system/storage.rst:26 -msgid "" -"Moving attachments from \"Database\" to \"Filesystem\" can be run during " -"production use. However, you should consider your framework conditions (e.g. " -"bandwidth, system load in production) to define the right moment." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Pending till" msgstr "" -#: ../settings/system/storage.rst:32 -msgid "**You noticed slow updates of Zammad?**" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.pending_time}``" msgstr "" -#: ../settings/system/storage.rst:34 -msgid "" -"While Zammad is beeing updated, it enforces a recursive \"change " -"owner\" (chown) for this directory. For instances with many files this can " -"be time consuming. To mitigate that you can move your files and create a " -"symlink in ``/opt/zammad/storage/`` to the new directory. Of course you have " -"to make sure on your own that the permissions are always correct." +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not set" msgstr "" -#: ../settings/system/storage.rst:95 -msgid "Simple Storage (S3)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Priority > Name" msgstr "" -#: ../settings/system/storage.rst:41 -msgid "" -"To use the Simple Storage (S3), you have to provide some settings, which " -"can't be accessed in the UI (see instructions below)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.priority.name}``" msgstr "" -#: ../settings/system/storage.rst:44 -msgid "" -"⚠️ Please note that the current implementation is in its early stages and can " -"be modified in the future." +#: ../misc/variables/ticket.rst:1 +msgid "``2 normal``" msgstr "" -#: ../settings/system/storage.rst:47 -msgid "" -"The prerequisite is to have access to a S3-compatible storage and to have " -"all necessary parameters available (which depends on your storage provider; " -"if in doubt, please ask there for help)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > State > Name" msgstr "" -#: ../settings/system/storage.rst:51 -msgid "Steps to configure S3:" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.state.name}``" msgstr "" -#: ../settings/system/storage.rst:53 -msgid "" -"Copy ``config/zammad/storage.yml.dist`` to ``config/zammad/storage.yml``" +#: ../misc/variables/ticket.rst:1 +msgid "``new``, ``open``, ..." msgstr "" -#: ../settings/system/storage.rst:54 -msgid "Edit the copied file in one of the following ways:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Tags" msgstr "" -#: ../settings/system/storage.rst:56 -msgid "" -"Either provide your S3 configuration with one attribute per line like in the " -"upper area of the file" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.tags}``" msgstr "" -#: ../settings/system/storage.rst:58 +#: ../misc/variables/ticket.rst:1 msgid "" -"Or provide your S3 configuration as an URL (which you can find at the end of " -"the file). Note: you can also provide this URL as environment variable (:" -"docs:`see system documentation `) without using this yml-file." +"Currently not available, see `Issue 2769 `_" msgstr "" -#: ../settings/system/storage.rst:62 -msgid "" -"We recommend the deletion of the not used configuration style to avoid " -"inconsistencies." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Title" msgstr "" -#: ../settings/system/storage.rst:65 -msgid "Restart Zammad so the config file / environment variable is loaded" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.title}``" msgstr "" -#: ../settings/system/storage.rst:66 +#: ../misc/variables/ticket.rst:1 msgid "" -"Set the \"Storage Method\" in Zammad to ``Simple Storage (S3)`` in Settings " -"> System > Storage and click on \"Submit\". After that, Zammad checks your " -"configuration and the connection to the service and will raise an error " -"message if something is wrong." +"``My amazing Subject`` (normally subject, can be edited within Interface and " +"thus differ)" msgstr "" -#: ../settings/system/storage.rst:72 -msgid "A very simple storage configuration could look like this:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated at" msgstr "" -#: ../settings/system/storage.rst:85 -msgid "" -"Before setting the storage method to ``Simple Storage (S3)`` (step 4), " -"please make sure to have a working setup." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_at}``" msgstr "" -#: ../settings/system/storage.rst:88 -msgid "" -"You can verify this by running ``rails r 'Rails.logger = Logger.new(STDOUT); " -"pp Store::Provider::S3.ping?'`` in your Zammad directory. If everything is " -"fine, you should see ``true``, else you should see ``false`` and a simple " -"error message." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Address" msgstr "" -#: ../settings/system/storage.rst:93 -msgid "" -"If you installed Zammad through a package manager (rather than from source), " -"replace ``rails r`` with ``zammad run rails r`` above. To learn more, see :" -"docs:`Administration via Console `." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.address}``" msgstr "" -#: ../settings/ticket.rst:4 -msgid "" -"Here you can adjust general ticket settings. Additional ones for the ticket " -"composer interface can be found in the :doc:`/misc/composer`." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Avatar" msgstr "" -#: ../settings/ticket.rst:11 -msgid "Ticket Hook (default: ``Ticket#``)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.avatar(60,60)}``" msgstr "" -#: ../settings/ticket.rst:11 -msgid "The identifier for a ticket; *e.g.,* Ticket#, Call#, MyTicket#." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Department" msgstr "" -#: ../settings/ticket.rst:38 -msgid "Ticket Hook Position (default: ``right``)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.department}``" msgstr "" -#: ../settings/ticket.rst:14 -msgid "" -"With this setting you can decide (if) where to insert the ticket number." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Email" msgstr "" -#: ../settings/ticket.rst:20 -msgid "*Right*" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.email}``" msgstr "" -#: ../settings/ticket.rst:17 -msgid "" -"This setting will add the ticket reference on the right site of the subject." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Fax" msgstr "" -#: ../settings/ticket.rst:20 -msgid "Example: ``Some Subject [Ticket#12345]``" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.fax}``" msgstr "" -#: ../settings/ticket.rst:26 -msgid "*Left*" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Firstname" msgstr "" -#: ../settings/ticket.rst:23 -msgid "" -"This setting will add the ticket reference on the left site of the subject." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.firstname}``" msgstr "" -#: ../settings/ticket.rst:26 -msgid "Example: ``[Ticket#12345] Some Subject``" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Lastname" msgstr "" -#: ../settings/ticket.rst:29 -msgid "*None*" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.lastname}``" msgstr "" -#: ../settings/ticket.rst:29 -msgid "This will completely remove ticket references from the subject." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Login" msgstr "" -#: ../settings/ticket.rst:33 -msgid "" -"Please ensure to take a look at :doc:`/channels/email/settings` within the " -"email channel to ensure you have at least one reference that helps Zammad to " -"assign follow-ups correctly." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.login}``" msgstr "" -#: ../settings/ticket.rst:37 -msgid "" -"Disabling this and not setting up any further follow up search will lead to " -"unexpected results!" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Mobile" msgstr "" -#: ../settings/ticket.rst:65 -msgid "" -"Ticket Last Contact Behaviour (default: ``Use the start time of the last " -"customer thread (which may consist of multiple articles).``)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.mobile}``" msgstr "" -#: ../settings/ticket.rst:41 -msgid "" -"This setting changes the way Zammad updates the ``Last Contact`` value of a " -"ticket. This is fairly important for overviews and what you expect upon " -"ticket updates of a customer." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Note" msgstr "" -#: ../settings/ticket.rst:52 -msgid "" -"Use the start time of the last customer thread (which may consist of " -"multiple articles)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.note}``" msgstr "" -#: ../settings/ticket.rst:46 -msgid "" -"If this option is chosen, Zammad will update the last updated value just " -"once if a customer replies. After that, Zammad will wait for an agent to " -"react." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Phone" msgstr "" -#: ../settings/ticket.rst:50 -msgid "" -"This comes in handy if you want to work tickets in the order of their first " -"update. This will not change ticket orders if customers decide to \"bump\" " -"the ticket affected." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.phone}``" msgstr "" -#: ../settings/ticket.rst:57 -msgid "Use the time of the very last customer article." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > VIP" msgstr "" -#: ../settings/ticket.rst:55 -msgid "" -"When setting this option, Zammad will always update the last updated value. " -"This means that if ordering by ``Last Update``, ticket orders will change if " -"customers \"bump\" the ticket." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.vip}``" msgstr "" -#: ../settings/ticket.rst:64 -msgid "Last contact value used on :doc:`/manage/overviews`" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Web" msgstr "" -#: ../settings/ticket.rst:65 -msgid "Last contact value used on :doc:`/manage/trigger`" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.web}``" msgstr "" -#: ../settings/ticket.rst:88 -msgid "" -"Ticket Organization Reassignment (default: ``Update the most recent tickets." -"``)" +#: ../settings/branding.rst:10 +msgid "Product Name" msgstr "" -#: ../settings/ticket.rst:68 +#: ../settings/branding.rst:7 msgid "" -"This setting changes the way Zammad updates the organization field of the " -"tickets whenever the primary organization of a user is changed." -msgstr "" - -#: ../settings/ticket.rst:74 -msgid "Update the most recent tickets." +"Defines the name of the application, shown in the web interface, tabs and " +"title bar of the web browser." msgstr "" -#: ../settings/ticket.rst:72 -msgid "" -"If this option is chosen, Zammad will update the 100 most recent tickets " -"where the user is the ticket customer. The ticket organization field will be " -"automatically set to the new primary organization of the user." +#: ../settings/branding.rst:10 +msgid "Default value: ``Zammad Helpdesk``" msgstr "" -#: ../settings/ticket.rst:88 -msgid "Do not update any tickets." +#: ../settings/branding.rst:13 +msgid "Will be shown in the app and is included in email footers." msgstr "" -#: ../settings/ticket.rst:77 -msgid "" -"When choosing this option, Zammad will not update any tickets when the " -"user's primary organization is changed." +#: ../settings/branding.rst:19 +msgid "Logo" msgstr "" -#: ../settings/ticket.rst:80 -msgid "**Use with care!**" +#: ../settings/branding.rst:16 +msgid "Defines the logo of the application, shown in the login page of Zammad." msgstr "" -#: ../settings/ticket.rst:82 +#: ../settings/branding.rst:18 msgid "" -"Using this option may lead to inconsistencies in the system as the ticket " -"organization may become decoupled from the ticket customer." +"Ensure to hit the \"Submit\" button after uploading the logo. Otherwise your " +"change will not be saved." msgstr "" -#: ../settings/ticket.rst:85 +#: ../settings/branding.rst:22 msgid "" -"However, you may use this option if you wish to maintain :ref:`the shared " -"access ` to the ticket for all organization " -"members of the original organization of the customer." +"Allows to set the default language of the Zammad instance. The here defined " +"locale mostly acts as a fallback for:" msgstr "" -#: ../settings/ticket.rst:110 -msgid "Ticket Number Format (default: ``Increment (SystemID.Counter)``)" +#: ../settings/branding.rst:25 +msgid "user preferences (if Zammad can't detect the users locale)" msgstr "" -#: ../settings/ticket.rst:94 -msgid "" -"This setting defines the way Zammad's ticket number will look. Changing this " -"setting in production will cause follow up detection to fail." +#: ../settings/branding.rst:26 +msgid "CSV output (reporting, time accounting)" msgstr "" -#: ../settings/ticket.rst:102 -msgid "Increment (SystemID.Counter)" +#: ../settings/branding.rst:30 +msgid "Define the timezone of your Zammad installation." msgstr "" -#: ../settings/ticket.rst:98 +#: ../settings/branding.rst:32 msgid "" -"The increment value contains the SystemID (automatically generated during " -"installation) and a increment which counts up with every new Ticket. The " -"increment will automatically get another digit if needed." +"This does not have any effect on timings for your agents or how Zammad " +"stores date and time values." msgstr "" -#: ../settings/ticket.rst:102 -msgid "Examples: ``1010138``, ``1010139``" +#: ../settings/branding.rst:35 +msgid "Changing this value has direct consequences on the following areas:" msgstr "" -#: ../settings/ticket.rst:110 -msgid "Date (Year.Month.Day.SystemID.Counter)" +#: ../settings/branding.rst:37 +msgid ":doc:`/manage/scheduler` tasks" msgstr "" -#: ../settings/ticket.rst:105 -msgid "" -"This version of the ticket number is fairly long. However, because it " -"contains the date of ticket creation, it also allows you to see when the " -"ticket has been created. You may feel familiar with this number format if " -"you've worked with OTRS already." +#: ../settings/branding.rst:38 +msgid "search indexing (and thus reporting)" msgstr "" -#: ../settings/ticket.rst:110 -msgid "Examples: ``201206231010138``, ``201206231010139``" +#: ../settings/branding.rst:40 +msgid "calendar subscriptions" msgstr "" -#: ../settings/ticket.rst:137 -msgid "OPTIONS" +#: ../settings/branding.rst:41 +msgid "browser printing" msgstr "" -#: ../settings/ticket.rst:113 +#: ../settings/branding.rst:43 msgid "" -"The below options allow you to further customize your ticket number. The " -"availability of options differ depending of the chosen ticket number format " -"above." +"Please note that some of above are fallbacks in case Zammad could not detect " +"the agents timezone correctly." msgstr "" -#: ../settings/ticket.rst:122 -msgid "Checksum (default: ``no``)" +#: ../settings/branding.rst:77 +msgid "Pretty Date" msgstr "" -#: ../settings/ticket.rst:118 +#: ../settings/branding.rst:47 msgid "" -"If set to yes, we'll built a checksum to further \"unique\" the ticket " -"number of your system. If you're dealing with many other ticket systems this " -"might help to prevent false positive follow up detection on tickets." +"This setting allows you to define how Zammad should display time stamps " +"within the interface to all users." msgstr "" -#: ../settings/ticket.rst:122 -msgid "This will also add another digit to the ticket number." +#: ../settings/branding.rst:50 +msgid "" +"This does not have any effect on how Zammad returns e.g. time values via " +"variables." msgstr "" -#: ../settings/ticket.rst:137 -msgid "Min. size of Number (default: ``5``)" +#: ../settings/branding.rst:77 +msgid "Choose in between the following options:" msgstr "" -#: ../settings/ticket.rst:125 -msgid "" -"This setting defines the minimum length of your ticket number. If your " -"counter is not yet high enough, Zammad will fill the number with zeros to " -"ensure the wanted length." +#: ../settings/branding.rst:64 +msgid "relative" msgstr "" -#: ../settings/ticket.rst:129 +#: ../settings/branding.rst:55 msgid "" -"Please note that the minimum length is ``3`` (SystemID + at least one digit " -"if below 10). Also, if the length is no longer long enough, the number will " -"automatically get one digit longer. Ticket-Numbers **do not overflow**, thus " -"it's save to keep it at 5 or set it lower if wanted." +"This timestamp shows a relative time span until it switches to a date. Over " +"time, it will change as follows:" msgstr "" -#: ../settings/ticket.rst:135 -msgid "" -"This option is only available if ticket number format is set to " -"``Increment``!" +#: ../settings/branding.rst:58 +msgid "just now" msgstr "" -#: ../settings/ticket.rst:142 -msgid "Auto-Assignment" +#: ../settings/branding.rst:59 +msgid "5 minutes ago" msgstr "" -#: ../settings/ticket.rst:144 -msgid "" -"In a larger Zammad environment, it happens that several agents open the same " -"ticket at the same time. Although collision detection is then effective, the " -"efficiency of processing can be increased by means of the automatic " -"assignment of tickets when a ticket is opened." +#: ../settings/branding.rst:60 +msgid "3 days 1 hour ago" msgstr "" -#: ../settings/ticket.rst:149 -msgid "" -"The automatic assignment of tickets can be activated and configured in the " -"admin area under Settings > Ticket > Auto Assignment." +#: ../settings/branding.rst:61 +msgid "``03/04/2022``" msgstr "" -#: ../settings/ticket.rst:152 -msgid "" -"The auto assignment only works if the ticket has no owner yet. By default, " -"the agent can always reset the ticket owner to ``-`` if needed." +#: ../settings/branding.rst:63 +msgid "Hovering the timestamp helps, you'll always get a clean timestamp then." msgstr "" -#: ../settings/ticket.rst:155 -msgid "" -"If you want to use this function for only specific tickets, you can " -"configure the conditions accordingly to meet your requirement. By default " -"the condition affects all tickets with the state ``open``." +#: ../settings/branding.rst:71 +msgid "absolute" msgstr "" -#: ../settings/ticket.rst:161 +#: ../settings/branding.rst:67 msgid "" -"If you need to exclude users (e.g. a group leader), you can search and " -"select the desired agents in the ``Exception Users`` list. The search " -"function in this area is only effective, if you have too many agents to " -"display at once to help you with the configuration." +"This timestamp always includes the week day. For one week after creation, " +"the timestamp will not contain the date itself: Thursday 18:35." msgstr "" -#: ../settings/ticket.rst:167 -msgid "Notifications" +#: ../settings/branding.rst:71 +msgid "After a week it will switch to: ``Friday 4. Mar 16:00``." msgstr "" -#: ../settings/ticket.rst:191 -msgid "Default Notifications" +#: ../settings/branding.rst:76 +msgid "timestamp" msgstr "" -#: ../settings/ticket.rst:170 +#: ../settings/branding.rst:74 msgid "" -"This setting allows you to configure the default ticket notifications that " -"will be applied to all new agent users (incl. users who were just assigned " -"agent role). Simply change the notification matrix to desired state and " -"press **Save**." +"This will cause Zammad to show a complete timestamp according to your locale " +"defaults. For English this could be e.g. ``2022/12/03 2:40 pm`` or for " +"German e.g. ``12.03.2022 14:40``." msgstr "" -#: ../settings/ticket.rst:175 -msgid "" -"In case an agent already exists, their ticket notification preferences will " -"be preserved. Optionally, you can also **Apply current defaults to all " -"agents**." +#: ../settings/branding.rst:78 +msgid "Default setting: ``relative``." msgstr "" -#: ../settings/ticket.rst:181 -msgid "" -"**Potential time-consuming action:** Applying default ticket notifications " -"to all agent users may take some time to complete, be patient! The exact " -"time will depend on the size of your system and the number of agents." +#: ../settings/security.rst:2 +msgid "Security" msgstr "" -#: ../settings/ticket.rst:185 +#: ../settings/security.rst:4 msgid "" -"**Active agents only!** When current default ticket notifications are " -"applied, only active agent users are considered. In case an agent is re-" -"activated *after* this action, they will still have the old notification " -"configuration." +"For your overview we split each tab within security settings into its own " +"page:" msgstr "" -#: ../settings/ticket.rst:190 -msgid "" -"In case you want to go back to the initial state of ticket notifications, " -"you can click on **Reset to default** button." +#: ../settings/security/base.rst:2 ../settings/system/base.rst:2 +#: ../settings/ticket.rst:8 +msgid "Base" msgstr "" -#: ../settings/ticket.rst:194 ../settings/ticket.rst:196 -msgid "Duplicate Detection" +#: ../settings/security/base.rst:5 +msgid "New User Accounts" msgstr "" -#: ../settings/ticket.rst:236 ../settings/ticket.rst:238 -msgid "Detect Duplicate Ticket Creation" +#: ../settings/security/base.rst:9 +msgid "" +"Activates the `register as a new customer` function on the login page. If " +"set to ``no`` only administrators or agents can create new accounts manually." msgstr "" -#: ../settings/ticket.rst:197 ../settings/ticket.rst:199 -msgid "" -"This setting turns on the duplicate ticket detection mechanism during ticket " -"creation. If similar tickets are found in the system, a suitable warning " -"will be shown to the user trying to create a ticket." +#: ../settings/security/base.rst:13 ../settings/security/base.rst:38 +#: ../settings/security/base.rst:66 +msgid "Default setting: ``yes``" msgstr "" -#: ../settings/ticket.rst:204 ../settings/ticket.rst:206 -msgid "A Sample Duplicate Ticket Warning" +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"New User Accounts\" setting" msgstr "" -#: ../settings/ticket.rst:206 ../settings/ticket.rst:208 +#: ../settings/security/base.rst:22 msgid "" -"You can choose which ticket attributes will be matched by selecting them in " -"**Attributes to compare** field. Only if the ticket attribute value provided " -"by the user in the ticket create form is *equal* with the attribute in an " -"existing ticket, the warning will be shown." +"Deactivation of above function **does not** deactivate automatic account " +"creation! This means: If a user writes e.g. an email to Zammad and has no " +"account yet, Zammad will automatically create the account. User accounts are " +"a direct dependency of tickets and thus technically mandatory." msgstr "" -#: ../settings/ticket.rst:211 ../settings/ticket.rst:213 -msgid "**Warning title** and **Warning message** are configurable as well." +#: ../settings/security/base.rst:29 +msgid "Lost Password" msgstr "" -#: ../settings/ticket.rst:213 ../settings/ticket.rst:215 +#: ../settings/security/base.rst:33 msgid "" -"You can limit the detection only to certain user roles. By default, only " -"agents will see the warning." +"Activates the `lost password` function on the login page. If set to ``no`` " +"only administrators may change the user's password - users may update their " +"own password if they're still logged in and they have the required :doc:" +"`permission `." msgstr "" -#: ../settings/ticket.rst:216 ../settings/ticket.rst:218 -msgid "" -"If you don't want to show the matched tickets as part of the warning, you " -"can set **Show matching ticket(s) in the warning** setting to *no*." +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"Lost Password\" setting" msgstr "" -#: ../settings/ticket.rst:219 ../settings/ticket.rst:221 +#: ../settings/security/base.rst:49 msgid "" -"By default, **Permission level for looking up ticket** is set to *User*, " -"which means user permissions will be honored during sarch. The user will " -"see the warning only if tickets they have access to are matched. " -"Alternatively, you can set this setting to *System*, in which case the " -"search will happen within *all* tickets in the system, regardless of user " -"permissions." +"With third party authentications - but especially LDAP - you may want to " +"disable this function. Zammad **will not** change third party login " +"passwords and instead set or change the local password!" msgstr "" -#: ../settings/ticket.rst:225 ../settings/ticket.rst:227 -msgid "**🦺 Safety first!**" +#: ../settings/security/base.rst:56 +msgid "Password Login" msgstr "" -#: ../settings/ticket.rst:227 ../settings/ticket.rst:229 +#: ../settings/security/base.rst:60 msgid "" -"Even if the permission level is set to *System*, the user will not be shown " -"the tickets they don't have access to in the warning, even if they match." +"Activates the username & password login by default and if no third-party " +"login is activated. Disabling password login on the Zammad login page only " +"takes effect if you enable any :doc:`third-party`." msgstr "" -#: ../settings/ticket.rst:231 ../settings/ticket.rst:233 -msgid "" -"However, just the confirmation about the existence of the tickets in the " -"system may be considered an unwanted information disclosure. Use this option " -"carefully!" +#: ../settings/security/base.rst:64 +msgid "See :doc:`third-party` for supported third-party logins." +msgstr "" + +#: ../settings/security/base.rst:0 +msgid "Figure showing de-activated \"Password Login\" setting" msgstr "" -#: ../settings/ticket.rst:235 ../settings/ticket.rst:237 +#: ../settings/security/base.rst:77 msgid "" -"Finally, you can configure between matching within **All tickets** or **Open " -"tickets** only by setting **Match tickets in following states**. Depending " -"on the current ticket state, a ticket may or not be matched." +"To help administrators to overcome \"login issues\", Zammad automatically " +"offers a password request for administrator users. This allows you to adjust " +"Third-Party applications even if the login does no longer work!" msgstr "" -#: ../system/core-workflows.rst:2 -msgid "Core Workflows" +#: ../settings/security/base.rst:84 +msgid "Session Timeout" msgstr "" -#: ../system/core-workflows.rst:4 +#: ../settings/security/base.rst:86 msgid "" -"Core Workflows allow you to adjust object attributes in many ways. For " -"example:" +"All settings below by default are set to ``4 weeks``. Session Timeout " +"defines the life time of a users session. As soon as it's reached, Zammad " +"will automatically log off the session in question." msgstr "" -#: ../system/core-workflows.rst:7 -msgid "show / hide fields" +#: ../settings/security/base.rst:91 +msgid "" +"Zammad takes the highest value set assigned for the user based on the " +"permissions." msgstr "" -#: ../system/core-workflows.rst:8 -msgid "adjust mandatory setting" +#: ../settings/security/base.rst:94 +msgid "``admin``" msgstr "" -#: ../system/core-workflows.rst:9 -msgid "manipulate available options" +#: ../settings/security/base.rst:96 +msgid "``ticket.customer``" msgstr "" -#: ../system/core-workflows.rst:11 -msgid "" -"With this, you can provide exactly the information your users really need!" +#: ../settings/security/base.rst:97 +msgid "``default`` (fallback if user doesn't have above permissions set)" msgstr "" -#: ../system/core-workflows.rst:15 +#: ../settings/security/base.rst:99 msgid "" -"If the pre-defined :doc:`/system/objects` are not enough, please add them " -"beforehand." +"All settings act independently from each other allowing you to disable the " +"timeouts for e.g. admins, but not agents." msgstr "" -#: ../system/core-workflows.rst:17 -msgid "" -"If you experience slow or unreliable field updates, please see :ref:`Core " -"Workflow Ajax Modus `" +#: ../settings/security/base.rst:115 +#: ../system/integrations/checkmk/api-reference.rst:13 +#, fuzzy +msgid "Example" +msgstr "Przykład" + +#: ../settings/security/base.rst:107 +msgid "Let's suppose you configured the following session timeouts" msgstr "" -#: ../system/core-workflows.rst:22 -msgid "" -"This is a very enhanced functionality and can cause unexpected UI behavior. " -"Please ensure to test your use cases after configuration to reduce surprises." +#: ../settings/security/base.rst:104 +msgid "default: 3 weeks" msgstr "" -#: ../system/core-workflows.rst:None -msgid "Dialogue for adding a new workflow" +#: ../settings/security/base.rst:105 +msgid "admin: 2 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:2 -msgid "Core Workflow Condition Operators" +#: ../settings/security/base.rst:106 +msgid "ticket.agent: 4 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:4 -msgid "" -"You might know that there is a separate section for explaining :doc:" -"`condition operators `. Head over there to " -"see a detailed explanation of many conditions and operators." +#: ../settings/security/base.rst:107 +msgid "ticket.customer: 1 week" msgstr "" -#: ../system/core-workflows/condition-operators.rst:8 -msgid "" -"Due to differences to other places in Zammad which are also using conditions " -"(e.g. triggers), you can find a dedicated description of operators for core " -"workflows below." +#: ../settings/security/base.rst:115 +msgid "This results in the following situations" msgstr "" -#: ../system/core-workflows/condition-operators.rst:12 -msgid "" -"Be aware that the availability of the operators depends on the selected " -"attribute and its field type. Some of the operators may only be available " -"for system attributes (e.g. for \"tags\", \"active\")." +#: ../settings/security/base.rst:110 +msgid "a user with ``admin`` permission will have a timeout of 2 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:20 -msgid "Operator" +#: ../settings/security/base.rst:111 +msgid "" +"a user with ``admin`` and ``ticket.agent`` permissions will have a timeout " +"of 2 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:22 -msgid "after (absolute)" +#: ../settings/security/base.rst:113 +msgid "" +"a user with ``ticket.customer`` permission will have a timeout of 1 week" msgstr "" -#: ../system/core-workflows/condition-operators.rst:23 -msgid "Matches if a date/time is after a specific point in time." +#: ../settings/security/base.rst:115 +msgid "" +"a user with neither ``admin``, ``ticket.agent`` nor ``ticket.customer`` " +"permissions will have a timeout of 3 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:24 -msgid "after (relative)" +#: ../settings/security/password.rst:4 +msgid "" +"This section allows you to define password requirements for the local user " +"accounts." msgstr "" -#: ../system/core-workflows/condition-operators.rst:25 -msgid "Matches if a time span after a specified event has passed." +#: ../settings/security/password.rst:9 +msgid "" +"Zammad does **not** allow you to change your LDAP password, instead, it will " +"set a password in its local database which might confuse your users. This " +"might be addressed in the future by `#1169 `_." msgstr "" -#: ../system/core-workflows/condition-operators.rst:26 -msgid "before (absolute)" +#: ../settings/security/password.rst:14 +msgid "**Exception for admins**" msgstr "" -#: ../system/core-workflows/condition-operators.rst:27 -msgid "Matches if a date/time is before a specific point in time." +#: ../settings/security/password.rst:16 +msgid "" +"Please note that below password policies *do not* affect administrators " +"setting passwords on user accounts. While this seems strange and not safe we " +"believe that an administrator knowing an user's password is insecure as well." msgstr "" -#: ../system/core-workflows/condition-operators.rst:28 -msgid "before (relative)" +#: ../settings/security/password.rst:21 +msgid "The suggested workflow is either:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:29 -msgid "Matches if a time span after a specified event has not passed." +#: ../settings/security/password.rst:23 +msgid "" +"to use third party logins to not require local passwords at all **- or -**" msgstr "" -#: ../system/core-workflows/condition-operators.rst:30 -msgid "contains" +#: ../settings/security/password.rst:25 +msgid "to require your *user to reset the password* upon first login." msgstr "" -#: ../system/core-workflows/condition-operators.rst:31 -msgid "Matches if a specified value is present." +#: ../settings/security/password.rst:27 +msgid "" +"This way administrators are not required to set a user's password at all!" msgstr "" -#: ../system/core-workflows/condition-operators.rst:33 -msgid "Matches if all of the specified values are present." +#: ../settings/security/password.rst:31 +msgid "Maximum Failed Logins" msgstr "" -#: ../system/core-workflows/condition-operators.rst:35 -msgid "Matches if none of the specified values are present." +#: ../settings/security/password.rst:33 +msgid "" +"You can choose a value between ``4`` and ``20``. This defines how often a " +"login to a user account may fail until Zammad will lock it. Your users can " +"always use the \"forgot password\" function to change their password and " +"unlock their account." msgstr "" -#: ../system/core-workflows/condition-operators.rst:36 -msgid "contains not" +#: ../settings/security/password.rst:38 +msgid "The default value is ``10``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:37 -msgid "Matches if a specified value is not present." +#: ../settings/security/password.rst:42 +msgid "Beside changing the user's password, you can also unlock accounts via" msgstr "" -#: ../system/core-workflows/condition-operators.rst:39 -msgid "Matches if one specified value is present." +#: ../settings/security/password.rst:44 +msgid ":ref:`user management list `" msgstr "" -#: ../system/core-workflows/condition-operators.rst:41 -msgid "Matches if one specified value is not present." +#: ../settings/security/password.rst:45 +msgid ":docs:`console `" msgstr "" -#: ../system/core-workflows/condition-operators.rst:42 -msgid "does not match regex" +#: ../settings/security/password.rst:46 +msgid ":docs:`API `" msgstr "" -#: ../system/core-workflows/condition-operators.rst:43 -msgid "Matches if content doesn't fit to regex rule." +#: ../settings/security/password.rst:50 +msgid "Failed logins via LDAP no longer lock accounts." msgstr "" -#: ../system/core-workflows/condition-operators.rst:44 -msgid "ends with" +#: ../settings/security/password.rst:53 +msgid "2 Lower Case And 2 Upper Case Characters" msgstr "" -#: ../system/core-workflows/condition-operators.rst:45 -msgid "Matches if content ends with specified value." +#: ../settings/security/password.rst:55 +msgid "" +"You can add complexity to passwords by enforcing at least 2 upper and lower " +"case characters." msgstr "" -#: ../system/core-workflows/condition-operators.rst:46 -msgid "ends with one of" +#: ../settings/security/password.rst:58 ../settings/security/password.rst:83 +msgid "The default value is ``no``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:47 -msgid "Matches if content ends with one of the specified values." +#: ../settings/security/password.rst:62 +msgid "Minimum Length" msgstr "" -#: ../system/core-workflows/condition-operators.rst:48 -msgid "from (relative)" +#: ../settings/security/password.rst:64 +msgid "" +"This defines the minimum password length required for users to provide (from " +"``4`` to ``20``)." msgstr "" -#: ../system/core-workflows/condition-operators.rst:49 -msgid "Matches if date/time is after a period of time after an event." +#: ../settings/security/password.rst:67 +msgid "The default value is ``6``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:51 -msgid "Matches if content is equal to a specified value." +#: ../settings/security/password.rst:71 +msgid "Digit Required" msgstr "" -#: ../system/core-workflows/condition-operators.rst:52 -msgid "is any of" +#: ../settings/security/password.rst:73 +msgid "This enforces your users to use at least one digit within the password." msgstr "" -#: ../system/core-workflows/condition-operators.rst:53 -msgid "Matches if content is equal to any of specified values." +#: ../settings/security/password.rst:75 +msgid "The default value is ``yes``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:54 -msgid "is modified" +#: ../settings/security/password.rst:78 +msgid "Special Character Required" msgstr "" -#: ../system/core-workflows/condition-operators.rst:55 -msgid "Matches if content is modified." +#: ../settings/security/password.rst:80 +msgid "" +"This setting allows you to improve your password quality even more by " +"enforcing the password to contain at least one special character." msgstr "" -#: ../system/core-workflows/condition-operators.rst:57 -#: ../system/core-workflows/condition-operators.rst:61 -msgid "True from the moment of changing content until form submit." +#: ../settings/security/ssl-certificates.rst:2 +msgid "SSL Certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:58 -msgid "is modified to" +#: ../settings/security/ssl-certificates.rst:7 +msgid "" +"Zammad offers the possibility to upload custom certificates and custom " +"Certificate Authority (CA) certificates. This can be useful if you want to " +"connect Zammad the secure way to other systems which are using custom " +"certificates." msgstr "" -#: ../system/core-workflows/condition-operators.rst:59 -msgid "Matches if content is modified to a specific value." +#: ../settings/security/ssl-certificates.rst:12 +msgid "" +"An example usecase might be: You have an internal LDAP server that is not " +"accessible from the internet, and you want a SSL-encrypted connection, using " +"a custom certificate." msgstr "" -#: ../system/core-workflows/condition-operators.rst:62 -msgid "is none of" +#: ../settings/security/ssl-certificates.rst:19 +msgid "" +"You should have an existing custom certificate file and/or a custom CA " +"certificate file, which you want to add to Zammad. As filetype ``.crt`` is " +"supported and the certificate format has to be PEM (Base64 ASCII)." msgstr "" -#: ../system/core-workflows/condition-operators.rst:63 -msgid "Matches if content is none of any specified values." +#: ../settings/security/ssl-certificates.rst:25 +msgid "" +"When you import a custom CA certificate, all certificates generated with " +"this are trusted. This can be useful if you have more than one system/" +"certificate you want to connect to and the certificates are issued from the " +"same custom CA." msgstr "" -#: ../system/core-workflows/condition-operators.rst:65 -msgid "Matches if content is not equal to a specified value." +#: ../settings/security/ssl-certificates.rst:31 +msgid "Add a Certificate" msgstr "" -#: ../system/core-workflows/condition-operators.rst:67 -msgid "Matches if content is present." +#: ../settings/security/ssl-certificates.rst:33 +msgid "" +"To add a custom certificate or a custom CA certificate, head over to the " +"Admin panel > Settings > Security > SSL Certificates. Here you can find a " +"\"Add SSL Certificate\" button. In the dialog you can either select a " +"certificate file or paste the content of the certificate:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:68 -msgid "just changed" +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate adding dialog" msgstr "" -#: ../system/core-workflows/condition-operators.rst:69 -msgid "Matches if content has changed." +#: ../settings/security/ssl-certificates.rst:43 +msgid "" +"After selecting a file or pasting the content of the certificate, click on " +"the \"Add\" button to finally upload it to Zammad. Then, the certificates " +"are immediately effective, no restart or similar required." msgstr "" -#: ../system/core-workflows/condition-operators.rst:71 -#: ../system/core-workflows/condition-operators.rst:75 +#: ../settings/security/ssl-certificates.rst:49 msgid "" -"Only true for the moment of changing content until next form field action/" -"click." +"Please note that only single certificate files are supported. That means if " +"you want to import a certificate / CA certificate, it must contain **only " +"one** certificate." msgstr "" -#: ../system/core-workflows/condition-operators.rst:72 -msgid "just changed to" +#: ../settings/security/ssl-certificates.rst:54 +msgid "Certificate Overview" msgstr "" -#: ../system/core-workflows/condition-operators.rst:73 -msgid "Matches if content has changed to a specified value." +#: ../settings/security/ssl-certificates.rst:56 +msgid "" +"After you added a certificate, you can see a table with information for each " +"added certificate:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:76 -msgid "matches regex" +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing table of added certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:77 -msgid "Matches if value fits to regex rule." +#: ../settings/security/ssl-certificates.rst:64 +msgid "" +"Here you can download the certificate or delete it, if you don't need it " +"anymore." msgstr "" -#: ../system/core-workflows/condition-operators.rst:79 -msgid "Matches if no content is present." +#: ../settings/security/ssl-certificates.rst:68 +msgid "Deleting Certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:80 -msgid "starts with" +#: ../settings/security/ssl-certificates.rst:70 +msgid "" +"If you want to delete a specific certificate, you can do it by clicking on " +"the menu in the actions column and selecting delete:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:81 -msgid "Matches if content starts with specified value." +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate deletion button" msgstr "" -#: ../system/core-workflows/condition-operators.rst:82 -msgid "starts with one of" +#: ../settings/security/ssl-certificates.rst:79 +msgid "Downloading Certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:83 -msgid "Matches if content starts with one of the specified values." +#: ../settings/security/ssl-certificates.rst:81 +msgid "" +"If you want to download your certificates, you can do this as well via " +"corresponding action buttons." msgstr "" -#: ../system/core-workflows/condition-operators.rst:84 -msgid "till (relative)" +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate download button" msgstr "" -#: ../system/core-workflows/condition-operators.rst:85 -msgid "Matches if date/time is before a period of time before an event." +#: ../settings/security/third-party.rst:13 +msgid "Login Providers" msgstr "" -#: ../system/core-workflows/condition-operators.rst:86 -msgid "today" +#: ../settings/security/third-party.rst:2 +msgid "Third-Party Applications" msgstr "" -#: ../system/core-workflows/condition-operators.rst:87 -msgid "Matches if date/time is today." +#: ../settings/security/third-party.rst:4 +msgid "" +"Third party authentication is a great way to help your users to login to " +"Zammad more easily. If the account is yet unknown, Zammad will create a new " +"user automatically, without the user needed to interact (e.g. type in his " +"name). Another big advantage of this feature is that your user doesn't need " +"to remember another password." msgstr "" -#: ../system/core-workflows/condition-operators.rst:88 -msgid "within last (relative)" +#: ../settings/security/third-party.rst:10 +msgid "" +"You can deactivate logging in via :ref:`security_password_login` if any of " +"the mentioned authentication providers are enabled in your instance." msgstr "" -#: ../system/core-workflows/condition-operators.rst:89 +#: ../settings/security/third-party.rst:27 msgid "" -"Matches if date/time content is within specified period of time before now." +"We're currently missing documentation for the following login providers:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:91 -msgid "within next (relative)" +#: ../settings/security/third-party.rst:29 +msgid "LinkedIn" msgstr "" -#: ../system/core-workflows/condition-operators.rst:92 -msgid "" -"Matches if date/time content is within specified period of time after now." +#: ../settings/security/third-party.rst:30 +msgid "Weibo" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:2 -msgid "How do they work?" +#: ../settings/security/third-party.rst:35 +msgid "Automatic Account Link on Initial Logon" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:4 +#: ../settings/security/third-party.rst:37 msgid "" -"Core Workflows are executed according to their priority. If two workflows " -"have the same priority, they are executed in alphabetical order based on " -"their **name**." +"In general there's two possible options for Zammad on how to deal with " +"already known users as they try to authenticate against a third-party " +"application. By default, Zammad will not automatically link \"unknown\" " +"authentication providers to existing accounts." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:8 +#: ../settings/security/third-party.rst:42 msgid "" -"Because of the way Core Workflows work, all changes to attributes are " -"checked with the application server - please see :doc:`limitations` for " -"possible issues." +"This means that the user has to manually link authentication providers to " +"their accounts (for more about this :user-docs:`consult the user " +"documentation `)." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:12 +#: ../settings/security/third-party.rst:46 msgid "" -"Below we're talking about settings that are important and not self-" -"explanatory." +"Sometimes this doesn't come in handy as this also means you'll receive error " +"messages about \"email address being in use already\" for (yet) unknown " +"third-party authentication methods." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:17 +#: ../settings/security/third-party.rst:50 msgid "" -"Choose the object context you want to run the workflow in. This will decide " -"on your available attributes and actions." +"If you want to allow your users to always be able to log in, no matter what, " +"you may want to enable ``Automatic account link on initial logon``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:20 -msgid "Ticket objects also have access to the ticket customer." +#: ../settings/security/third-party.rst:None +msgid "" +"Screenshot highlighting the \"Automatic account link on initial logon\"\n" +"setting" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:25 -msgid "" -"Choose in which situation the workflow is applied. Contexts can be combined " -"to avoid duplicate workflows." +#: ../settings/security/third-party.rst:60 +msgid "Automatic Account Linking Notification" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:30 -msgid "Creation mask" +#: ../settings/security/third-party.rst:64 +msgid "" +"To improve security and your users awareness, you can enable Zammad to " +"notify your users when a new third-party application has been linked to " +"their account." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:29 +#: ../settings/security/third-party.rst:68 msgid "" -"If selected, your conditions and actions will affect all applicable creation " -"masks." +"This notification is sent out once per third-party application. Zammad does " +"also mention the method used, e.g.: ``Microsoft``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:34 -msgid "Edit mask" +#: ../settings/security/third-party.rst:71 +msgid "By default this setting is not active (set to ``no``)." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:33 +#: ../settings/security/third-party.rst:0 msgid "" -"If selected, your conditions and actions will affect all applicable edit " -"masks." +"Screenshot showing sample notification mail after initial\n" +"third-party linking" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:39 +#: ../settings/security/third-party.rst:85 msgid "" -"Zammad differentiates between selected and saved conditions. These can be " -"combined wherever needed." +"This notification is only sent if the account in question already exists. If " +"the login via the third-party also creates the missing account, the " +"notification will be skipped." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:42 -msgid "**⚠️ Restrict workflows to specific roles if needed!**" +#: ../settings/security/third-party.rst:89 +msgid "This means it only affects:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:44 -msgid "" -"By default and unless configured in conditions, workflow rules are executed " -"for **all roles**. This also affects your customers!" +#: ../settings/security/third-party.rst:91 +msgid "manual account linking within the third-party page of the users profile" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:50 -msgid "Selected Conditions" +#: ../settings/security/third-party.rst:92 +msgid "" +"logging into an existing local account by utilizing the *automatic account " +"link on initial logon* functionality" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:48 +#: ../settings/security/third-party.rst:None msgid "" -"These conditions are based on form values and match if an appropriate " -"selection is made (e.g. choosing another group in the ticket without " -"saving). This applies for drafts (active selection) and currently saved " -"values." +"Screenshot showing the \"automatic account linking notification\"\n" +"setting" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:64 -msgid "Saved Conditions" +#: ../settings/security/third-party.rst:100 +msgid "No User Creation on Logon" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:53 +#: ../settings/security/third-party.rst:102 msgid "" -"These conditions only match if the selected values are stored in the " -"database. It ignores the current value or selection of the field, as long as " -"the changes are not saved (e.g. performing field operations for an existing " -"ticket, which is viewed/opened by an agent)." +"By default, Zammad will create a new user account if the user logs in via a " +"third-party application and the account doesn't exist yet." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:60 +#: ../settings/security/third-party.rst:105 msgid "" -"Keep in mind that the value has to be available in the situation where you " -"need it. Otherwise the condition won't match." +"If you want to prevent Zammad from creating new accounts on logon, you can " +"disable this feature by setting ``No user creation on logon`` to ``yes``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:63 -msgid "" -"Example: you can't perform any actions with *saved condition* on a ticket in " -"creation, because there are no saved values at that time." +#: ../settings/security/third-party.rst:None +msgid "Screenshot showing the \"no user creation on logon\" setting" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:66 +#: ../settings/security/third-party/facebook.rst:4 msgid "" -"You can find a description of the condition operators for core workflows :" -"doc:`here `." +"It is possible to create a quick login for your helpdesk via Facebook To do " +"so, you need to follow these steps:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:72 -msgid "" -"Which actions should we run on the relevant fields? The possible actions " -"depend on the object type. However, usually you can at least change the " -"visibility and whether the field is mandatory." +#: ../settings/security/third-party/facebook.rst:9 +msgid "Register Facebook App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:76 -msgid "Be aware that actions are not available for **related** context." +#: ../settings/security/third-party/facebook.rst:11 +msgid "" +"Visit [https://developers.facebook.com/apps/] and click on \"Add a new App\"" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:78 -msgid "" -"**Example:** Let's assume you are working in the ticket context. While you " -"can have customer *conditions*, you *can't adjust* objects with actions in " -"that scope. That's because this wouldn't have any impact on the ticket " -"dialog. Of course all ticket attributes (state, owner, ...) are available." +#: ../settings/security/third-party/facebook.rst:None +msgid "initial page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:84 -msgid "" -"Please also have a look at our :doc:`limitations` to be safe from surprises." +#: ../settings/security/third-party/facebook.rst:17 +msgid "After that enter the app settings" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:88 -msgid "Available Operators" +#: ../settings/security/third-party/facebook.rst:None +msgid "Create App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:90 -msgid "The availability of operators depends on the object type and scope." +#: ../settings/security/third-party/facebook.rst:22 +msgid "Navigate to \"Settings\" and fill in this infromation" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:94 -msgid "" -"Please note that actions may or may not restrict API based access to " -"attributes. We're displaying the following icons for your overview to " -"understand these limits better:" +#: ../settings/security/third-party/facebook.rst:None +msgid "App Settings" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:0 -msgid "|api| This icon indicates the action affects the API." +#: ../settings/security/third-party/facebook.rst:27 +msgid "Navigate to app review and Check \"Make [appname] public?\"" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:163 -msgid "api" +#: ../settings/security/third-party/facebook.rst:None +msgid "App Review" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:0 -msgid "|ui| This icon indicates the action only affects the web interface." +#: ../settings/security/third-party/facebook.rst:35 +msgid "Configure Zammad as Facebook App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:167 -msgid "ui" +#: ../settings/security/third-party/facebook.rst:37 +msgid "" +"Navigate to \"Admin -> Security -> Third Party Applications\" and enter the " +"App ID and the App Secret. You can find this Key in the Dashbard of your " +"Facebok app." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:102 -msgid "show |ui|" +#: ../settings/security/third-party/facebook.rst:None +msgid "Zammad Configuration" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:102 -msgid "Display the chosen field. Allows setting of values." +#: ../settings/security/third-party/facebook.rst:44 +#: ../settings/security/third-party/github.rst:43 +#: ../settings/security/third-party/gitlab.rst:46 +msgid "" +"Now you can link accounts via \"Avatar -> Profile -> Link Accounts\" or " +"login via Zammad login page." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:109 -msgid "hide |ui|" +#: ../settings/security/third-party/github.rst:2 +#: ../system/integrations/github.rst:2 +msgid "GitHub" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:105 +#: ../settings/security/third-party/github.rst:4 msgid "" -"Hide the chosen field. However, it technically still allows setting the " -"field." +"It is possible to create a quick login for your helpdesk via GitHub. To " +"activate the quick login you need to enable OAuth for GitHub." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:108 +#: ../settings/security/third-party/github.rst:8 +msgid "Register GitHub App" +msgstr "" + +#: ../settings/security/third-party/github.rst:10 msgid "" -"Please note that the field is **not** gone and still contains an existing " -"value (if set)! Consider *remove* instead, if you want this field to be gone." +"Visit https://www.github.com/settings/applications/new and enter the app " +"settings. As callback URL enter \"https://zammad_host/auth/github/callback\" " +"where zammad_host has to be replaced with your Zammad FQDN" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:112 -msgid "remove |ui|" +#: ../settings/security/third-party/github.rst:None +msgid "Register OAuth app on www.github.com" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:112 -msgid "Entirely removes the field. The field value will not be evaluated." +#: ../settings/security/third-party/github.rst:19 +msgid "Configure Zammad as GitHub App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:115 -msgid "set mandatory |ui| |api|" +#: ../settings/security/third-party/github.rst:21 +msgid "" +"Enter the \"APP ID\" and the \"APP SECRET\" from the GitHub OAUTH " +"Applications Dashboard" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:115 -msgid "Sets the field to mandatory." +#: ../settings/security/third-party/github.rst:None +msgid "GitHub config in Zammad admin interface" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:118 -msgid "set optional |ui| |api|" +#: ../settings/security/third-party/github.rst:28 +msgid "" +"After you configured the GitHub credentials and activated the login method, " +"you should see a new icon on the login page." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:118 -msgid "Sets the field to optional." +#: ../settings/security/third-party/github.rst:None +msgid "GitHub logo on login page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:124 -msgid "add option |ui| |api|" +#: ../settings/security/third-party/github.rst:34 +msgid "" +"If you click on the icon you will be redirected to GitHub and see something " +"similar to this:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:121 -msgid "Allows adding options to tree selects or selects." +#: ../settings/security/third-party/github.rst:None +msgid "GitHub oauth page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:123 +#: ../settings/security/third-party/github.rst:40 +#: ../settings/security/third-party/gitlab.rst:42 msgid "" -"You have to use the \"remove option\" before performing this action. It " -"allows you to use *existing* configured values." +"When you grant the access you will be redirected to your Zammad instance and " +"logged in as a customer." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:128 -msgid "remove option |ui| |api|" +#: ../settings/security/third-party/gitlab.rst:2 +msgid "Gitlab" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:127 +#: ../settings/security/third-party/gitlab.rst:4 msgid "" -"Allows removing options from tree selects or selects. It allows you to use " -"*existing* configured values." +"It is possible to create a quick login for your helpdesk via Gitlab. To " +"activate the quick login you need to enable OAuth for Gitlab." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:134 -msgid "set fixed to |ui| |api|" +#: ../settings/security/third-party/gitlab.rst:8 +msgid "Register Gitlab App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:131 -msgid "Reduces the available options by your selection." +#: ../settings/security/third-party/gitlab.rst:10 +msgid "To register an app in Gitlab open your profile and select applications." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:133 +#: ../settings/security/third-party/gitlab.rst:12 msgid "" -"This reduces your workflows in terms of *add option* and *remove option*." +"As callback URL enter \"https://zammad-fqdn/auth/gitlab/callback\" where " +"zammad-fqdn has to be replaced with your Zammad FQDN" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:137 -msgid "fill in |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Register OAuth app on gitlab instance" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:137 -msgid "Allows filling in of string and integer fields with your values." +#: ../settings/security/third-party/gitlab.rst:18 +msgid "Just select *read_user* under scopes as in the screenshot and save it." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:141 -msgid "fill in empty |ui|" +#: ../settings/security/third-party/gitlab.rst:21 +msgid "Configure Zammad as Gitlab App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:140 +#: ../settings/security/third-party/gitlab.rst:23 msgid "" -"Allows filling in of string and integer fields with your values **if the " -"field is empty**." +"Enter the \"APP ID\" and the \"APP SECRET\" from the Gitlab OAUTH " +"Applications Dashboard and your Gitlab-URL in the \"SITE\" field." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:144 -msgid "select |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab config in Zammad admin interface" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:144 -msgid "Select a specific value within a select, tree select or boolean field." +#: ../settings/security/third-party/gitlab.rst:30 +msgid "" +"After you configured the Gitlab credentials and activated the login method, " +"you should see a new icon on the login page." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:153 -msgid "auto select |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab logo on login page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:147 -msgid "Helps users with tree select and select fields:" +#: ../settings/security/third-party/gitlab.rst:36 +msgid "" +"If you click on the icon you will be redirected to Gitlab and see something " +"similar to this:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:149 -msgid "" -"If the field has only one option available for selection and no value yet, " -"the value will be automatically set." +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab oauth page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:152 +#: ../settings/security/third-party/google.rst:4 msgid "" -"This option only works if you have one value and doesn't work if there is " -"more than one option available." +"With some easy and fast steps, you can enable Zammad to authenticate your " +"users via Google." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:157 -msgid "set readonly |ui|" +#: ../settings/security/third-party/google.rst:8 +msgid "Register a Google App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:156 +#: ../settings/security/third-party/google.rst:10 msgid "" -"Allows you to display an attribute as read only (which means no changes are " -"possible)." +"First of all, we need to create a new project - you can skip this step if " +"you already have one." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:161 -msgid "unset readonly |ui|" +#: ../settings/security/third-party/google.rst:15 +msgid "" +"Use this link to create a new project: https://console.cloud.google.com/" +"projectcreate" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:160 +#: ../settings/security/third-party/google.rst:18 msgid "" -"In case a workflow set the field in question to read only, you can undo this " -"with option above." +"Now expand the menu, expand \"APIs & Services\" and select \"Credentials\". " +"Go to the tab \"OAuth consent screen\" first and ensure to fill in the " +"requested information - without doing so you can't create credentials!" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:172 -msgid "Stop after match" +#: ../settings/security/third-party/google.rst:None +msgid "Creating a consent screen" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:174 +#: ../settings/security/third-party/google.rst:25 msgid "" -"Here you can decide if other workflows are executed after the current one." +"After filling in and saving the consent screen information, you can go to " +"the \"Credentials\" tab and create new \"OAuth client ID\"-Credentials." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:176 +#: ../settings/security/third-party/google.rst:28 msgid "" -"If set to ``no`` (default), further workflows will be executed if they match " -"the condition. In this case, it is possible that your actions from the " -"current workflow can be overwritten by another workflow." +"Fill in the necessary information as follows and replace ``zammad_host`` " +"with your FQDN:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:180 -msgid "" -"If set to ``yes``, no further worflows will be executed after the current " -"one." +#: ../settings/security/third-party/google.rst:31 +msgid "**Application type** ``[x] Web application``" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:184 -msgid "Priority" +#: ../settings/security/third-party/google.rst:34 +msgid "**Authorized JavaScript origins** ``https://zammad_host/``" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:186 +#: ../settings/security/third-party/google.rst:37 msgid "" -"You can define the sequence, in which the workflows are executed. The " -"default value is ``500``." +"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" +"callback``" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:189 -msgid "" -"The workflows are executed in ascending order by their priority. That means " -"lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." +#: ../settings/security/third-party/google.rst:None +msgid "Adding a new OAuth client ID" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:2 -#, fuzzy -msgid "Learn by Example" -msgstr "Przykład" - -#: ../system/core-workflows/learn-by-example.rst:4 +#: ../settings/security/third-party/google.rst:43 msgid "" -"This page provides some basic examples for Core Workflows. Of course you can " -"build much more complex workflows if needed." +"After creating the credentials, go to your Zammad installation and navigate " +"to \"Admin > Security > Third Party Applications\" > Google. Enter your " +"Client ID and Client secret here." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:7 -msgid "" -"To learn about Core Workflows in detail, first go to :doc:`how-do-they-work`." +#: ../settings/security/third-party/google.rst:None +msgid "Zammad" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:10 -#, fuzzy -msgid "Group Based Examples" -msgstr "Przykład" +#: ../settings/security/third-party/google.rst:50 +msgid "After submitting, the login via Google can be used." +msgstr "" -#: ../system/core-workflows/learn-by-example.rst:12 +#: ../settings/security/third-party/microsoft.rst:2 +msgid "Microsoft" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:4 msgid "" -"All following workflows have the same base configurations. The workflow may " -"not use them all." +"Zammad's Microsoft connection allows your users with Microsoft accounts to " +"login. This works for Azure users as well and can be an alternative to :doc:" +"`/system/integrations/ldap/index`." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:15 -#, fuzzy -msgid "Groups:" -msgstr "grupa" +#: ../settings/security/third-party/microsoft.rst:10 +msgid "" +"This documentation part does not cover our :doc:`📧 Microsoft 365 email " +"channel `." +msgstr "" -#: ../system/core-workflows/learn-by-example.rst:20 -msgid "Attributes:" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screenshot showing Microsoft login button on Zammad login screen." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:22 -msgid "Category (Single tree selection field, not mandatory, agents only)" +#: ../settings/security/third-party/microsoft.rst:30 +#: ../settings/security/third-party/microsoft.rst:53 +msgid "Supported account types:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:23 +#: ../settings/security/third-party/microsoft.rst:22 msgid "" -"Approved (Boolean field, not mandatory, not shown, ``false`` as default)" +"Please note that Zammad only supports these account types (App dependent):" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:24 -msgid "Operating System (Text field, not mandatory, not shown)" +#: ../settings/security/third-party/microsoft.rst:35 +msgid "Avatars of signing in users:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:25 -msgid "Software used (Single selection field, not mandatory, not shown)" +#: ../settings/security/third-party/microsoft.rst:33 +msgid "" +"Zammad currently ignores user avatars. If the user is registered with e.g. " +"Gravatar, Zammad will fetch the avatar from there if enabled. See :doc:" +"`Zammad Image Service ` for more." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:68 -msgid "Group specific values and fields" +#: ../settings/security/third-party/microsoft.rst:38 +msgid "Step 1 - Register a Microsoft App for Zammad" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:28 +#: ../settings/security/third-party/microsoft.rst:40 msgid "" -"This workflow set depends on the category field. It reduces the available " -"set of values based on the group selected." +"Login to the `Microsoft Azure Portal `_ and " +"navigate to App registrations to create a new app. Provide the requested " +"information as follows and register your app." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:33 -msgid "Workflow 2nd Level group" +#: ../settings/security/third-party/microsoft.rst:46 +msgid "Name:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:35 +#: ../settings/security/third-party/microsoft.rst:45 msgid "" -"This reduces the category options to ``2nd Level/*``, ``Internal/*`` and " -"``Others``. It also sets further required fields to mandatory and visible." +"Any meaningful name fitting, this name will be displayed to users trying to " +"authenticate with this app." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for 2nd level" +#: ../settings/security/third-party/microsoft.rst:49 +msgid "Choose one of the above mentioned account types (see Limitations)." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:43 -msgid "Workflow Support group" +#: ../settings/security/third-party/microsoft.rst:51 +msgid "" +"The correct account type depends on your use case. If you want to use the " +"authentication internal only, choose the first option. If you're unsure, use " +"the \"Help me choose...\" link." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:45 -msgid "" -"This reduces the category options to ``Support/*``, ``Internal/*`` and " -"``Others``. It also sets further required fields to visible." +#: ../settings/security/third-party/microsoft.rst:58 +msgid "Redirect URI (optional):" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for support" +#: ../settings/security/third-party/microsoft.rst:56 +msgid "" +"Select web and provide your callback URL. The callback URL looks like this: " +"``https://zammad.domain.tld/auth/microsoft_office365/callback``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:53 -msgid "Workflow Sales group" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to register a Microsoft app" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:55 -msgid "" -"This reduces the category options to ``Sales/*``, ``Internal/*`` and " -"``Others``." +#: ../settings/security/third-party/microsoft.rst:71 +msgid "Within **API permissions** add the following permissions:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for sales" +#: ../settings/security/third-party/microsoft.rst:69 +msgid "``User.Read``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:68 -#: ../system/integrations/slack.rst:88 -msgid "The Result" +#: ../settings/security/third-party/microsoft.rst:71 +msgid "Contacts" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:63 -msgid "" -"This is what the agent would experience with the above workflows in place." +#: ../settings/security/third-party/microsoft.rst:71 +msgid "``Contacts.Read``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 +#: ../settings/security/third-party/microsoft.rst:73 msgid "" -"Workflow shows objects and limits options based on selections on the group" +"You can find these permissions within *Microsoft Graph → Delegated " +"permissions*." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:90 -msgid "Approval process" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to add required API permissions" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:71 +#: ../settings/security/third-party/microsoft.rst:80 msgid "" -"In this case ``approved`` is visible to agents by default. For this " -"workflow, an additional role ``Approval person`` is required (no further " -"permissions)." +"Within **Certificates & secrets** create a new client secret. Note down the " +"returned secret **value** for later. **Do not** use the secret ID!" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that restricts an approval attribute to specific roles" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to create a new app secret" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:81 +#: ../settings/security/third-party/microsoft.rst:88 msgid "" -"This workflow may work best in combination with a :doc:`trigger ` but technically, this is not required." +"From **Overview** copy your apps *Application (client) ID*. If you're using " +"a single tenant app, please also copy *Directory (tenant) ID*. You now have " +"all required information for Zammad." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:84 -msgid "" -"Select fields may be a better approach because they allow more values than " -"just a simple ``true`` or ``false``." +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to retreive application client and tenant IDs" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 +#: ../settings/security/third-party/microsoft.rst:98 +msgid "Step 2 - Add App Credentials to Zammad" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:100 msgid "" -"Workflow fixes possible values of \"Approved ?\" to a specific selection " -"depending on the users role" +"Navigate to Security > Third-party Applications (Tab) within Zammad's admin " +"settings. Scroll down to the section *Authentication via Microsoft* and fill " +"in the required information." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:103 -msgid "State dependent mandatory fields" +#: ../settings/security/third-party/microsoft.rst:105 +msgid "App ID:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:93 -msgid "" -"This workflow sets ``Category`` to mandatory if the agent wants to set the " -"states ``closed`` or ``pending close`` to enforce categorization." +#: ../settings/security/third-party/microsoft.rst:105 +msgid "This is your *Application (client) ID*." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that sets fields to mandatory on specific states" +#: ../settings/security/third-party/microsoft.rst:108 +msgid "App secret:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "" -"Workflow sets category field to mandatory upon choosing closed or pending " -"close as state" +#: ../settings/security/third-party/microsoft.rst:108 +msgid "This is your *client secret* (value)." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:106 -msgid "Manual Ticket Handover Process" +#: ../settings/security/third-party/microsoft.rst:113 +msgid "App Tenant ID:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:108 -msgid "This example covers the handover of a ticket from one agent to another:" +#: ../settings/security/third-party/microsoft.rst:111 +msgid "" +"**optional** only required for apps that use account type *Accounts in this " +"organizational directory only (Default Directory only - Single tenant).*" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:110 +#: ../settings/security/third-party/microsoft.rst:115 msgid "" -"When the ticket owner is modified, a new text field (\"Handover\") shows up " -"for a comment" +"Apply your settings by pressing submit and activate *Authentication via " +"Microsoft*." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:112 +#: ../settings/security/third-party/microsoft.rst:None msgid "" -"This may only be visible when the owner is changed, therefore it has to be " -"hidden in general" +"Screencast showing how to add app credentials and activating the\n" +"authentication method" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:114 -msgid "The input in this handover text field is mandatory" +#: ../settings/security/third-party/saml.rst:2 +msgid "SAML" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:115 +#: ../settings/security/third-party/saml.rst:4 msgid "" -"After submitting changes, the value of the handover field must be added as " -"an note to the ticket (via trigger)" +"Connect your SAML (Security Assertion Markup Language) identity provider as " +"a single sign-on (SSO) method." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:121 -msgid "Hiding handover field" +#: ../settings/security/third-party/saml.rst:7 +msgid "" +"SAML is an open standard for SSO authentication (among other things). Sign-" +"ins are shared across multiple **service providers** and managed by a " +"central **identity provider** (IdP)." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Hiding the handover field in core workflows" +#: ../settings/security/third-party/saml.rst:11 +msgid "" +"In this case, the service provider is Zammad, and the IdP is a software " +"service that you either host or subscribe to (*e.g.,* `Keycloak `_, `Redhat SSO Server `_, `ADFS `_, or `Okta `_)." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:126 -msgid "Showing handover field and setting it to mandatory" +#: ../settings/security/third-party/saml.rst:18 +msgid "" +"This guide assumes you are already using SAML within your organization (i." +"e., that your IdP is fully set up)." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Showing the handover field and set it as mandatory" +#: ../settings/security/third-party/saml.rst:21 +msgid "" +"Please note: Our instructions are based on connecting Zammad with Keycloak." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:131 -msgid "Trigger writing handover input to a new article" +#: ../settings/security/third-party/saml.rst:25 +msgid "Step 1: Configure Your IdP" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Write handover content to a new article" +#: ../settings/security/third-party/saml.rst:28 +msgid "Add Zammad as a Client/App" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:133 +#: ../settings/security/third-party/saml.rst:30 msgid "" -"As a result, the ticket includes an article of the type note which includes " -"the predefined text and the handover comment." -msgstr "" - -#: ../system/core-workflows/limitations.rst:6 -msgid "Core Workflows do not replace Triggers" +"Import Zammad into your IdP using the XML configuration found at ``https://" +"your.zammad.domain/auth/saml/metadata``." msgstr "" -#: ../system/core-workflows/limitations.rst:5 +#: ../settings/security/third-party/saml.rst:33 msgid "" -"Workflows manipulate the behavior of fields. However, they do not set values " -"in fields because of actions." +"If your IdP doesn't support XML import, you will have to configure Zammad as " +"a new client/app manually using the above XML metadata file for reference." msgstr "" -#: ../system/core-workflows/limitations.rst:16 -msgid "API calls are only partly affected" +#: ../settings/security/third-party/saml.rst:36 +msgid "For instance, when you see this tag:" msgstr "" -#: ../system/core-workflows/limitations.rst:9 +#: ../settings/security/third-party/saml.rst:42 msgid "" -"Some options affect UI only and thus do not restrict responses and calls." -msgstr "" +"Set the **Assertion Consumer Service Binding URL** (sometimes also listed as " +"**Valid Redirect URIs**) to ``http://your.zammad.domain/auth/saml/callback``." +msgstr "" -#: ../system/core-workflows/limitations.rst:11 -msgid "This affects the following actions:" +#: ../settings/security/third-party/saml.rst:47 +msgid "Set Up User Attribute Mapping" msgstr "" -#: ../system/core-workflows/limitations.rst:13 -msgid "select" +#: ../settings/security/third-party/saml.rst:49 +msgid "" +"Zammad requests the following user attributes (or “properties”) from the IdP:" msgstr "" -#: ../system/core-workflows/limitations.rst:14 -msgid "auto select" +#: ../settings/security/third-party/saml.rst:51 +msgid "Email address (``email``)" msgstr "" -#: ../system/core-workflows/limitations.rst:15 -msgid "show" +#: ../settings/security/third-party/saml.rst:52 +msgid "Full name (``name``)" msgstr "" -#: ../system/core-workflows/limitations.rst:16 -msgid "hide" +#: ../settings/security/third-party/saml.rst:53 +msgid "Given name (``first_name``)" msgstr "" -#: ../system/core-workflows/limitations.rst:25 -msgid "Some fields stay unavailable to customers" +#: ../settings/security/third-party/saml.rst:54 +msgid "Family name (``last_name``)" msgstr "" -#: ../system/core-workflows/limitations.rst:19 +#: ../settings/security/third-party/saml.rst:56 msgid "" -"For technical and security reasons, some default fields (the pale ones you " -"can't edit) stay unavailable for display and usage on customer permissions." +"You may need to set up “mappers” (or “mappings”) to tell your IdP how user " +"attributes in SAML correspond to those in Zammad. For a more detailed " +"breakdown, refer to the XML metadata file referenced in the previous section." msgstr "" -#: ../system/core-workflows/limitations.rst:23 -msgid "" -"If you require your customers to change e.g. priorities, please consider " -"using workarounds via :doc:`/system/objects` and :doc:`/manage/trigger`." +#: ../settings/security/third-party/saml.rst:62 +msgid "Per-IdP Instructions" msgstr "" -#: ../system/core-workflows/limitations.rst:29 -msgid "Ticket title changes not supported in edit mask" +#: ../settings/security/third-party/saml.rst:102 +msgid "Keycloak" msgstr "" -#: ../system/core-workflows/limitations.rst:28 +#: ../settings/security/third-party/saml.rst:65 msgid "" -"It is currently not possible to perform changes of the ticket title in the " -"edit mask (e.g. renaming, set to read-only)." +"**To add Zammad as a client,** save the XML configuration to disk (``https://" +"your.zammad.domain/auth/saml/metadata``) and use **Clients > Clients list > " +"Import client** in the Keycloak admin panel." msgstr "" -#: ../system/core-workflows/limitations.rst:37 -msgid "What is out of scope of Core Workflows?" +#: ../settings/security/third-party/saml.rst:70 +msgid "" +"To help Zammad **match its own user accounts to Keycloak users**, create a " +"user attribute (or “property”) mapper. In **Clients list**, click on your " +"newly created Client ID, choose the tab **Client scopes** and click on the " +"link which refers to your Zammad instance. Choose **Add mapper > By " +"configuration > User Property** and create a mapper with the following " +"entries:" msgstr "" -#: ../system/core-workflows/limitations.rst:32 -msgid "" -"There are some things that would count as workflow but are either done via :" -"doc:`/manage/trigger` or :doc:`/manage/scheduler`." +#: ../settings/security/third-party/saml.rst:78 +msgid "**Name**" msgstr "" -#: ../system/core-workflows/limitations.rst:35 -msgid "Such as (but not limited to):" +#: ../settings/security/third-party/saml.rst:80 +msgid "**Mapper Type**" msgstr "" -#: ../system/core-workflows/limitations.rst:37 -msgid "up- or downgrade permissions of users" +#: ../settings/security/third-party/saml.rst:81 +msgid "``User Property``" msgstr "" -#: ../system/core-workflows/limitations.rst:38 -msgid "affecting article creation or listing" +#: ../settings/security/third-party/saml.rst:82 +msgid "**Property**" msgstr "" -#: ../system/data-privacy.rst:2 -msgid "Data Privacy" +#: ../settings/security/third-party/saml.rst:83 +msgid "``emailAddress``" msgstr "" -#: ../system/data-privacy.rst:4 -msgid "" -"For compliance with GDPR and other data privacy laws, you may wish to " -"**permanently delete users from the system**, along with **all of their " -"associated tickets**." +#: ../settings/security/third-party/saml.rst:84 +msgid "**SAML Attribute Name**" 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 `!" +#: ../settings/security/third-party/saml.rst:86 +msgid "**SAML Attribute NameFormat**" msgstr "" -#: ../system/data-privacy.rst:12 -msgid "" -"Access to this panel requires ``admin.data_privacy`` permissions (introduced " -"in Zammad 3.5)." +#: ../settings/security/third-party/saml.rst:87 +msgid "``basic``" msgstr "" -#: ../system/data-privacy.rst:15 +#: ../settings/security/third-party/saml.rst:89 msgid "" -"On older systems that have not been updated yet, customers can also be :docs:" -"`deleted via the Zammad console `." +"In the example above, we're telling Zammad that whenever it receives a SAML " +"login request, it should take the ``email`` property from Keycloak, look for " +"a Zammad user with the same ``email`` attribute, and create a new session " +"for that user." msgstr "" -#: ../system/data-privacy.rst:22 -msgid "User deletion dialog in the Data Privacy panel" +#: ../settings/security/third-party/saml.rst:95 +msgid "" +"If your Keycloak users' email addresses are stored on another property (*e." +"g.,* ``username``), adjust accordingly." msgstr "" -#: ../system/data-privacy.rst:22 +#: ../settings/security/third-party/saml.rst:98 msgid "" -"The user deletion dialog lists some of the tickets that will be removed from " -"the system along with the user." +"Back in **Settings**, enter the Client ID (``https://your.zammad.domain/auth/" +"saml/metadata``) in the field **Master SAML Processing URL**." msgstr "" -#: ../system/data-privacy.rst:27 -msgid "Deleting Users via GUI" +#: ../settings/security/third-party/saml.rst:101 +msgid "You also need to enable **Sign assertions**." msgstr "" -#: ../system/data-privacy.rst:29 -msgid "🔥 **All deletions are FINAL!**" +#: ../settings/security/third-party/saml.rst:105 +msgid "Step 2: Configure Zammad" msgstr "" -#: ../system/data-privacy.rst:31 -msgid "Once you click “Delete”, the action cannot be canceled or undone." +#: ../settings/security/third-party/saml.rst:107 +msgid "" +"Enable SAML and enter your IdP's details in the Admin Panel under **Settings " +"> Security > Third Party Applications > Authentication via SAML**:" msgstr "" -#: ../system/data-privacy.rst:33 -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." +#: ../settings/security/third-party/saml.rst:None +msgid "Example configuration of SAML part 1" msgstr "" -#: ../system/data-privacy.rst:36 -msgid "**The following records cannot be deleted:**" +#: ../settings/security/third-party/saml.rst:119 +msgid "Display name" msgstr "" -#: ../system/data-privacy.rst:38 -msgid "your own account" +#: ../settings/security/third-party/saml.rst:116 +msgid "" +"Allows you to define a custom button name for SAML. This helps your users to " +"understand better what the button on the login page does." msgstr "" -#: ../system/data-privacy.rst:39 -msgid "the system's last remaining administrator account" +#: ../settings/security/third-party/saml.rst:119 +msgid "Defaults to ``SAML``." msgstr "" -#: ../system/data-privacy.rst:42 -msgid "Step 1: Find a User / Confirm Deletion" +#: ../settings/security/third-party/saml.rst:123 +msgid "IDP SSO target URL" msgstr "" -#: ../system/data-privacy.rst:44 -msgid "There are three ways to access the user deletion dialog:" +#: ../settings/security/third-party/saml.rst:122 +msgid "" +"This is the target URL Zammad shall redirect to when the user presses the " +"SAML button. For Keycloak, this needs to look like https://your.domain/" +"realms/your-realm/protocol/saml" msgstr "" -#: ../system/data-privacy.rst:51 -msgid "**from the user's profile**" +#: ../settings/security/third-party/saml.rst:127 +msgid "IDP single logout target URL" msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Accessing the user deletion dialog in a user profile" +#: ../settings/security/third-party/saml.rst:126 +msgid "" +"This is the URL to which the single logout request and response should be " +"sent." msgstr "" -#: ../system/data-privacy.rst:51 -msgid "Click **Action > Delete**." +#: ../settings/security/third-party/saml.rst:131 +msgid "IDP certificate" msgstr "" -#: ../system/data-privacy.rst:58 -msgid "**in the “Manage > Users” Admin Panel**" +#: ../settings/security/third-party/saml.rst:130 +msgid "" +"The public certificate of your IDP for Zammad to verify during the callback " +"phase." msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Accessing the user deletion dialog under “Users” in the Admin Panel" +#: ../settings/security/third-party/saml.rst:145 +msgid "IDP certificate fingerprint" msgstr "" -#: ../system/data-privacy.rst:58 -msgid "Use the **⋮ Actions** menu for the target user." +#: ../settings/security/third-party/saml.rst:134 +msgid "" +"The fingerprint of your IDPs public certificate to verify during callback " +"phase." msgstr "" -#: ../system/data-privacy.rst:66 ../system/data-privacy.rst:104 -msgid "**in the “System > Data Privacy” Admin Panel**" +#: ../settings/security/third-party/saml.rst:137 +msgid "🔏 **For the IdP certificate / certificate fingerprint:**" msgstr "" -#: ../system/data-privacy.rst:0 +#: ../settings/security/third-party/saml.rst:139 msgid "" -"Accessing the user deletion dialog under “Data Privacy” in the Admin Panel" +"Provide **only one or the other**—do not provide both! (Between the two, we " +"recommend the signing certificate itself: fingerprints use SHA-1, which `has " +"been broken for a while now `_.)" msgstr "" -#: ../system/data-privacy.rst:65 +#: ../settings/security/third-party/saml.rst:144 msgid "" -"Use the **New Deletion Task** button. Search for users by name or email " -"address." +"**Keycloak users:** Find your certificate in the Keycloak admin panel under " +"**Realm Settings > Keys > Algorithm: RS256 > Certificate**." msgstr "" -#: ../system/data-privacy.rst:79 -msgid "**Delete organizations**" +#: ../settings/security/third-party/saml.rst:151 +msgid "Name identifier format" msgstr "" -#: ../system/data-privacy.rst:69 +#: ../settings/security/third-party/saml.rst:148 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:" +"This is the unique identifiers field type. Usually it should be ``urn:oasis:" +"names:tc:SAML:1.1:nameid-format:emailAddress``." msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Deleting an organization via the user deletion dialog" +#: ../settings/security/third-party/saml.rst:151 +msgid "Zammad **expects an email address as unique identifier**!" msgstr "" -#: ../system/data-privacy.rst:78 +#: ../settings/security/third-party/saml.rst:155 +msgid "UID attribute name" +msgstr "" + +#: ../settings/security/third-party/saml.rst:154 msgid "" -"If this option does not appear, make sure there are no pending deletion " -"tasks for other customers from this organization." +"Here you can define an attribute that uniquely identifies the user. If " +"unset, the name identifier returned by the IDP is used." msgstr "" -#: ../system/data-privacy.rst:82 -msgid "Step 2: Monitor Deletion Job Status" +#: ../settings/security/third-party/saml.rst:None +msgid "Example configuration of SAML part 2" msgstr "" -#: ../system/data-privacy.rst:84 +#: ../settings/security/third-party/saml.rst:163 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:" +"Decide if the certificate for the connection to the IdP service has to be " +"verified or not (default: ``yes``)." msgstr "" -#: ../system/data-privacy.rst:98 -msgid "**in the Activity Stream**" -msgstr "" - -#: ../system/data-privacy.rst:0 -msgid "Activity Stream showing data privacy tasks" +#: ../settings/security/third-party/saml.rst:169 +msgid "Signing & Encrypting" msgstr "" -#: ../system/data-privacy.rst:94 +#: ../settings/security/third-party/saml.rst:169 msgid "" -"For each deleted user, the Activity Stream will be updated twice—once when " -"the task is created, and once when it's complete." +"Define if you want to sign, encrypt, do both or nothing for the requests." msgstr "" -#: ../system/data-privacy.rst:97 -msgid "" -"These notifications are only visible to users with ``admin.data_privacy`` " -"permissions." +#: ../settings/security/third-party/saml.rst:179 +msgid "Certificate (PEM)" msgstr "" -#: ../system/data-privacy.rst:0 +#: ../settings/security/third-party/saml.rst:172 msgid "" -"The task list within Data Privacy shows removals being in progress and " -"completed." +"Paste the public certificate of your Zammad SAML client, if you want to " +"encrypt the requests." msgstr "" -#: ../system/data-privacy.rst:107 -msgid "Frequently Asked Questions" +#: ../settings/security/third-party/saml.rst:175 +msgid "Make sure the certificate is:" msgstr "" -#: ../system/data-privacy.rst:121 -msgid "What happens if I receive an email from a deleted customer?" +#: ../settings/security/third-party/saml.rst:177 +msgid "already valid and not yet expired" msgstr "" -#: ../system/data-privacy.rst:110 -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." +#: ../settings/security/third-party/saml.rst:178 +msgid "no CA certificate" msgstr "" -#: ../system/data-privacy.rst:115 -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**." +#: ../settings/security/third-party/saml.rst:179 +msgid "valid for signing and encrypting" msgstr "" -#: ../system/data-privacy.rst:130 -msgid "What about user information stored in internal notes or other messages?" +#: ../settings/security/third-party/saml.rst:185 +msgid "Private key (PEM)" msgstr "" -#: ../system/data-privacy.rst:124 +#: ../settings/security/third-party/saml.rst:182 msgid "" -"The deletion process removes **user accounts and associated tickets only**." +"Paste the private key of your Zammad SAML client here, if you want to sign " +"the requests." msgstr "" -#: ../system/data-privacy.rst:126 -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." +#: ../settings/security/third-party/saml.rst:185 +msgid "Make sure the key is an RSA key with a length of at least 2048 bits." msgstr "" -#: ../system/data-privacy.rst:137 -msgid "I deleted an user and can still see a message they sent!" +#: ../settings/security/third-party/saml.rst:188 +msgid "Private key secret" msgstr "" -#: ../system/data-privacy.rst:133 -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." +#: ../settings/security/third-party/saml.rst:188 +msgid "If your private key is secured with a secret, you can provide it here." msgstr "" -#: ../system/data-privacy.rst:141 -msgid "I removed a customer, now my reporting is off!" +#: ../settings/security/third-party/saml.rst:192 +msgid "Your callback URL" msgstr "" -#: ../system/data-privacy.rst:140 +#: ../settings/security/third-party/saml.rst:191 msgid "" -"When removing users and their tickets, all references are removed. This also " -"affects e.g. Reporting - these information are lost." +"This URL is needed for your IdP configuration so it knows where to redirect " +"to after successful authentication." msgstr "" -#: ../system/data-privacy.rst:145 -msgid "How long does Zammad store created tasks?" +#: ../settings/security/third-party/saml.rst:194 +msgid "" +"After saving your input by clicking on the \"Submit\" button, Zammad " +"verifies the provided keys/certificates (e.g. if they are valid for signing/" +"encrypting and if they aren't expired)." msgstr "" -#: ../system/data-privacy.rst:144 +#: ../settings/security/third-party/saml.rst:199 msgid "" -"Please see the on-premise data section of the :docs:`data privacy ` chapter." +"See :ref:`automatic account linking ` for details " +"on how to link existing Zammad accounts to IdP accounts." msgstr "" -#: ../system/data-privacy.rst:150 -msgid "What about re-assigned tickets? I want to delete them, too." +#: ../settings/security/third-party/saml.rst:205 +msgid "Automatic account linking doesn't work" msgstr "" -#: ../system/data-privacy.rst:148 +#: ../settings/security/third-party/saml.rst:206 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." -msgstr "" - -#: ../system/data-privacy.rst:154 -msgid "Why are there so many deletion task entries, I didn't create them!" +"Have you double-checked your IdP's user attribute mapping configuration?" msgstr "" -#: ../system/data-privacy.rst:153 +#: ../settings/security/third-party/twitter.rst:4 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." +"It is possible to create a quick login for your helpdesk via Twitter. To do " +"so, you need to follow these steps:" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:2 -msgid "Admin Panel Reference" +#: ../settings/security/third-party/twitter.rst:8 +msgid "Register Twitter App" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:None -msgid "Screenshot of Checkmk settings overview" +#: ../settings/security/third-party/twitter.rst:10 +msgid "Go to https://dev.twitter.com/apps and login with your account." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:12 -msgid "" -"Which :doc:`group ` should Checkmk tickets be assigned " -"to as a default (*i.e.,* when none is specified)?" +#: ../settings/security/third-party/twitter.rst:15 +msgid "Click on \"Create App\"" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:15 -msgid "(Applies to :ref:`API alerts ` only.)" +#: ../settings/security/third-party/twitter.rst:None +msgid "new app page" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:21 -msgid "Auto close" +#: ../settings/security/third-party/twitter.rst:20 +msgid "" +"Enter app settings. As \"Callback URL\" you need to enter ``https://" +"zammad_host/api/v1/external_credentials/twitter/callback``. You need to " +"replace ``zammad_host`` with the domain of your Zammad system." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:18 +#: ../settings/security/third-party/twitter.rst:24 msgid "" -"Should Zammad automatically close tickets if a service has recovered on its " -"own?" +"After the app has been created, update the application icon and organization " +"attributes." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:21 -msgid "(Agents will receive notifications for such closures as appropriate.)" +#: ../settings/security/third-party/twitter.rst:None +msgid "set permissions to receive and send direct messages" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:30 -msgid "Auto-close state" +#: ../settings/security/third-party/twitter.rst:30 +msgid "" +"Next we need to set ``read, write and access direct messages`` permissions " +"for the app." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:24 -msgid "What ticket state should be applied when “auto-closing” a ticket?" +#: ../settings/security/third-party/twitter.rst:None +msgid "click on Keys & Access Token, note them" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:26 +#: ../settings/security/third-party/twitter.rst:36 msgid "" -"You can choose from the seven built-in ticket states. If these states aren't " -"enough for you, you can :ref:`define a new ticket state ` for this purpose as well. This can be useful for tracking " -"tickets with :doc:`reports `, for example." +"Go to \"Keys and Access Token\" tab and note the \"Consumer Key\" and " +"\"Consumer Secret\"." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:35 -#: ../system/integrations/cti/includes/recent-logs.include.rst:2 -#: ../system/integrations/ldap/index.rst:74 -#: ../system/integrations/pgp/index.rst:106 -msgid "Recent Logs" +#: ../settings/security/third-party/twitter.rst:40 +msgid "Configure Zammad as Twitter App" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:None -msgid "Screenshot of Checkmk \"Recent Logs\" section" +#: ../settings/security/third-party/twitter.rst:42 +msgid "" +"Go to \"Admin > Security > Twitter > Third Party Applications > Twitter\" " +"Section." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:41 +#: ../settings/security/third-party/twitter.rst:None +msgid "Admin > Security > Third Party Applications" +msgstr "" + +#: ../settings/security/third-party/twitter.rst:48 msgid "" -"If you're having trouble getting Zammad and Checkmk to play nicely together, " -"this section can help you troubleshoot." +"Fill in the \"Twitter Key\" and the \"Twitter Secret\" and click the " +"\"Submit\" button." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:44 +#: ../settings/security/third-party/twitter.rst:51 msgid "" -"It contains a record of the fifty most recent transactions that Zammad knows " -"about, including each one's request/response details and return status." +"Now you can link accounts via \"Avatar > Profile > Link Accounts\" or login " +"via Zammad login page." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:2 -msgid "API Reference" +#: ../settings/security/two-factor.rst:11 +msgid "Two-factor Authentication Methods" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:4 -msgid "" -"For most users, :ref:`the sample scripts from the Setup Guide ` will do the job just fine. But if you want more fine-grained control" -"—for instance, to create high- and low-priority tickets for different types " -"of system events—then you'll have to customize the data those scripts send " -"to Zammad." +#: ../settings/security/two-factor.rst:2 +msgid "Two-Factor Authentication" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:15 +#: ../settings/security/two-factor.rst:4 msgid "" -"This custom script will automatically set all tickets it creates to **high " -"priority** and **assign them to charlie@chrispresso.com**." +"Two-factor authentication (2FA) enhances the security of Zammad accounts by " +"adding an extra layer of verification beyond a password. It requires users " +"to provide two different types of authentication factors, typically " +"something they know (like a password) and something they possess (like a " +"mobile device or a security token), to ensure that only authorized " +"individuals can access the account." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:32 -msgid "How Does it Work?" +#: ../settings/security/two-factor.rst:19 +msgid "Enable Recovery Codes" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:34 +#: ../settings/security/two-factor.rst:21 msgid "" -"There are two kinds of data you can pass to the API, both in the form of key-" -"value pairs:" +"Recovery codes are one-time use security codes that can be used by the user " +"if they lose access to their other two-factor authentication methods. They " +"cannot be used on their own, they can only be activated if at least one two-" +"factor authentication method is enabled." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:44 -msgid "Checkmk parameters" +#: ../settings/security/two-factor.rst:None +msgid "Enable Recovery Codes Setting" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:38 +#: ../settings/security/two-factor.rst:30 msgid "" -"are required, and make up the **contents** of the resulting tickets/" -"articles. They also determine whether an event creates a new ticket or " -"updates/closes an existing one." +"Recovery codes can only be used as a backup method. If enabled, they will be " +"automatically generated for the user once they set up their initial two-" +"factor authentication method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:42 +#: ../settings/security/two-factor.rst:34 msgid "" -"These are the only values used in the sample scripts. **Use them as-is**; " -"technically, they can be customized, but it's hard to imagine a good reason " -"for it." +"The user will be asked to print out or save the generated recovery codes in " +"a safe place. Once used, a recovery code cannot be reused." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:52 -msgid "Ticket attributes" -msgstr "" - -#: ../system/integrations/checkmk/api-reference.rst:47 +#: ../settings/security/two-factor.rst:37 msgid "" -"are optional, and can be used to **adjust settings** on newly created " -"tickets (*e.g.,* set the owner, group, priority, or state)." +"Users will also have an option to regenerate their recovery codes at any " +"time, which invalidates already existing recovery codes and provides them " +"with a list of fresh codes." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:50 +#: ../settings/security/two-factor.rst:41 msgid "" -"If you want to customize your Checkmk alert script, do it with these. Simply " -"add an extra “form” option for each one (``-F \"key=value\"``) to your " -"script's ``curl`` command line, as in the example above." +"After you enable this setting, when the user completes a setup of their " +"initial two-factor authentication method, they will be presented with a list " +"of recovery codes and instructed to save them for later use." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:54 -msgid "💡 **It's just an API endpoint!**" +#: ../settings/security/two-factor.rst:None +msgid "Recovery Codes Generation Modal Dialog" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:56 -msgid "" -"When using Checkmk integration, messages need to be formatted in a certain " -"way, but that *doesn't mean the messages actually have to come from Checkmk*." +#: ../settings/security/two-factor.rst:50 +msgid "Enforce the Set Up of the Two-Factor Authentication" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:59 +#: ../settings/security/two-factor.rst:52 msgid "" -"If you use another monitoring tool that's not officially supported by " -"Zammad, there's probably a way to make it work with your Checkmk callback " -"URL." +"In case you wish to require your users to set up at least one two-factor " +"authentication method for their account, you can do this by selecting " +"specific user roles the requirement applies to in **Enforced for user " +"roles** setting. Of course you must have at least one two-factor " +"authentication method enabled for this setting to take effect." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:63 -msgid "Checkmk Parameters" +#: ../settings/security/two-factor.rst:None +msgid "Enforced for User Roles Setting" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:65 +#: ../settings/security/two-factor.rst:62 msgid "" -"When a notification is received, Zammad creates a new article containing the " -"details of the event that triggered it:" -msgstr "" - -#: ../system/integrations/checkmk/api-reference.rst:None -msgid "Checkmk article body" +"After you change this setting, if the user has one of the selected roles on " +"their account, they will be forced to set up the two-factor authentication " +"upon next sign in or application reload." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:72 +#: ../settings/security/two-factor.rst:66 msgid "" -"These details come from the fields listed below, which correspond to " -"parameters provided by Checkmk (``$NOTIFY_*``)." +"A modal dialog with instructions will be shown, and they will not be able to " +"do any work before they set up at least one two-factor method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:75 -msgid "**Required fields are marked with an asterisk (\\*).**" +#: ../settings/security/two-factor.rst:None +msgid "Modal Dialog for Enforcing Two-Factor Authentication Set Up" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:79 -msgid "event_id\\*" +#: ../settings/security/two-factor.rst:74 +msgid "Reset Two-Factor Authentication for a Specific User" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:78 +#: ../settings/security/two-factor.rst:76 msgid "" -"A unique ID for the system event. (``$NOTIFY_SERVICEPROBLEMID`` / " -"``$NOTIFY_HOSTPROBLEMID``)" +"In case an user isn't able to login anymore because of an inaccessible " +"second factor, you can reset the user's 2FA method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:86 -msgid "host\\*" +#: ../settings/security/two-factor.rst:79 +msgid "" +"To do this, go to the user management and search for the relevant user. " +"After you found the account, click the button in the action column and " +"select \"Manage Two-Factor Authentication\":" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:82 -msgid "" -"The hostname of the system that the event originated from. " -"(``$NOTIFY_HOSTNAME``)" +#: ../settings/security/two-factor.rst:None +msgid "Context menu in action column in user management" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:85 +#: ../settings/security/two-factor.rst:87 msgid "" -"Used to determine if a new event belongs to an existing ticket. Also used in " -"the subject line of the resulting article (“ is ”)." +"After selecting this, you can see a dialog where you can either reset one " +"2FA method or reset all of the user's 2FA methods:" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:96 -msgid "service" +#: ../settings/security/two-factor.rst:None +msgid "Dialog for resetting user's 2FA method" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:89 +#: ../settings/security/two-factor.rst:94 msgid "" -"The name of the service that the event originated from. " -"(``$NOTIFY_SERVICEDESC``)" +"Choose the fitting one, click on the corresponding \"Remove ...\" button and " +"confirm your action. The user now has to setup a new 2FA method, depending " +"on your 2FA configuration." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:92 -msgid "Used to determine if a new event belongs to an existing ticket." +#: ../settings/security/two-factor/authenticator-app.rst:2 +msgid "Authenticator App" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:94 -#: ../system/integrations/checkmk/api-reference.rst:110 -msgid "Displayed as ``-`` when omitted." +#: ../settings/security/two-factor/authenticator-app.rst:4 +msgid "" +"The authenticator app method is a type of two-factor authentication that " +"uses a mobile application to generate one-time codes for account " +"verification. After setting up the authenticator app on their device, the " +"user links it to their Zammad account." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:104 -msgid "state\\*" +#: ../settings/security/two-factor/authenticator-app.rst:12 +msgid "" +"When logging in, the user is prompted to enter a time-sensitive code " +"generated by the app, in addition to their password. This code acts as the " +"second factor of authentication, providing an extra layer of security as it " +"changes periodically and is unique to the user's device." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:99 -msgid "" -"The current state of the service or host in question. " -"(``$NOTIFY_SERVICESTATE`` / ``$NOTIFY_HOSTSTATE``)" +#: ../settings/security/two-factor/authenticator-app.rst:None +msgid "Security Code in Google Authenticator App" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:102 +#: ../settings/security/two-factor/authenticator-app.rst:22 msgid "" -"Used to detect when a ticket should be auto-closed (*i.e.,* on ``OK``/" -"``UP``). Also used in the subject line of the resulting article (“ is " -"”)." +"The app generates codes based on a shared secret key stored securely on both " +"the user's device and the server, ensuring a synchronized and secure " +"authentication process. The method of generating the codes is sometimes also " +"called TOTP (time-based one-time password)." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:110 -msgid "text" +#: ../settings/security/two-factor/authenticator-app.rst:28 +msgid "Enabling the Authenticator App Method" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:107 -msgid "" -"The output of the process that triggered the event. " -"(``$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" +#: ../settings/security/two-factor/authenticator-app.rst:30 +#: ../settings/security/two-factor/security-keys.rst:28 +msgid "To enable the method, just toggle the switch on in the settings." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:121 +#: ../settings/security/two-factor/authenticator-app.rst:None +msgid "Authenticator App Switch in Settings" +msgstr "" + +#: ../settings/security/two-factor/authenticator-app.rst:36 msgid "" -"The Object Manager attribute panel displays built-in and custom\n" -"attribute names." +"Now the users will be able to set up this two-factor authentication method " +"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " +"Once they do, on next sign-in with password, they will be asked to provide " +"an additional security code generated by their mobile device." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:121 -msgid "Find a complete list of ticket attributes in the Object Manager." +#: ../settings/security/two-factor/security-keys.rst:2 +msgid "Security Keys" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:123 +#: ../settings/security/two-factor/security-keys.rst:4 msgid "" -"Ticket attributes are entirely optional, and can be used to customize the " -"tickets that Checkmk creates. (Note that these attributes will be ignored if " -"a new event belongs to an existing ticket.)" +"The security keys method is a type of a two-factor authentication that uses " +"Web Authentication API in the browser for verifying user's identity. The " +"user can register multiple hardware or software security keys with their " +"Zammad account and then they can use it during the sign-in process." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:128 +#: ../settings/security/two-factor/security-keys.rst:12 msgid "" -"Why would you want to do this? Maybe you have only one IT guy, and all " -"system monitoring issues should be automatically assigned to him. Or, maybe " -"you're creating multiple notification rules so that database outages take " -"higher priority than disk space warnings." +"When logging in, the user is prompted to provide the same security key they " +"registered with their account, in addition to their password. This key acts " +"as the second factor of authentication, providing an extra layer of security." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:135 -msgid "In most cases, you'll probably want to set one of the following:" +#: ../settings/security/two-factor/security-keys.rst:None +msgid "Security Key dialog in Safari on macOS" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:137 -msgid "group" -msgstr "grupa" +#: ../settings/security/two-factor/security-keys.rst:21 +msgid "" +"The type of the key can range from hardware USB sticks to passkeys stored in " +"a device of user's choice. Which type can be used depends on the browser " +"flavor and the platform of the user." +msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:139 -msgid "state" -msgstr "status" +#: ../settings/security/two-factor/security-keys.rst:26 +msgid "Enabling the Security Keys Method" +msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:140 -msgid "priority" -msgstr "priorytet" +#: ../settings/security/two-factor/security-keys.rst:None +msgid "Security Keys Switch in Settings" +msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:142 +#: ../settings/security/two-factor/security-keys.rst:34 msgid "" -"but in practice, you can set almost any attribute, including :doc:`custom " -"ones you created through the Object Manager `." +"Now the users will be able to set up this two-factor authentication method " +"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " +"Once they do, on next sign-in with password, they will be asked to provide " +"the same security key they registered during the setup." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:145 -msgid "Please note that the following attributes are **not customizable**:" +#: ../settings/system/system-selfhosted.include.rst:3 +msgid "" +"Below settings are only available to self hosted users. In hosted " +"environments we're handling these settings for you to ensure service " +"stability." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:147 -msgid "title" -msgstr "tytuł" +#: ../settings/system/base.rst:11 +msgid "Fully Qualified Domain Name" +msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:148 -msgid "id" +#: ../settings/system/base.rst:7 +msgid "The URL of your Zammad installation." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:149 -msgid "ticket number" +#: ../settings/system/base.rst:9 ../settings/system/base.rst:17 +msgid "This setting is used within :doc:`/misc/variables` and notifications." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:151 -msgid "created_by_id" +#: ../settings/system/system-base.include.rst:1 +msgid "It is automatically set by the *Getting Started wizard*." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:152 -msgid "updated_by_id" +#: ../settings/system/system-base.include.rst:5 +msgid "Changing this setting also changes callback URLs for your channels etc." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:155 -msgid "Which Values Can Be Set?" +#: ../settings/system/system-base.include.rst:6 +msgid "This setting can have negative affects on being able to login." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:157 -msgid "😵 **Invalid values → unpredictable behavior**" +#: ../settings/system/base.rst:19 +msgid "HTTP type" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:159 +#: ../settings/system/base.rst:14 msgid "" -"If you provide a value that Zammad doesn't understand (*e.g.,* ``-F " -"\"priority=high\"``), it's not always clear what will happen. In some cases, " -"a ticket will be created with the default values instead - but in others, it " -"may not be created at all!" +"The HTTP type tells your installation how your clients connect. This is " +"relevant for authentication and cookie security." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:164 -msgid "So what values does Zammad understand, then? Well, it depends..." +#: ../settings/system/base.rst:31 +msgid "SystemID" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:168 -msgid "Use an email address or username:" +#: ../settings/system/base.rst:22 +msgid "" +"This ID is being used within your ticket number. In case you're " +"communicating with another ticket system with similar ticket number schemes " +"this ID greatly reduces the risk of false follow ups." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:190 -msgid "group & priority" +#: ../settings/system/base.rst:26 +msgid "" +"The SystemID is randomly selected upon installation of Zammad (``1-99``)." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:175 -msgid "Refer to the dropdown menus in the ticket pane:" +#: ../settings/system/base.rst:30 +msgid "" +"**Do not** change this setting in a productive system! Your Zammad " +"installation may no longer recognize old ticket number based follow ups upon " +"change!" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:0 -msgid "See possible values for certain attributes in the ticket pane." +#: ../settings/system/frontend.rst:2 +msgid "Frontend" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:187 -msgid "🙅 **Ticket state CANNOT be set this way!**" +#: ../settings/system/frontend.rst:22 +msgid "Core Workflow Ajax Mode" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:189 +#: ../settings/system/frontend.rst:6 msgid "" -"Why? Because ``-F \"state=...\"`` is already used :ref:`as a Checkmk " -"parameter `." +"This setting allows administrators to enforce :doc:`/system/core-workflows` " +"to use Ajax-Calls instead of web sockets. You'll usually only need this if " +"you experience serious issues as noted below." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:222 -msgid "Everything Else" +#: ../settings/system/frontend.rst:10 +msgid "**🤓 Possible (technical) reasons**" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:193 +#: ../settings/system/frontend.rst:12 msgid "" -"To set any other attributes, it helps to know your way around the :docs:" -"`rails console `. Valid values are those that you can " -"set with a string:" +"In some cases, your network structure (e.g. firewalls, proxies) may " +"disconnect long web socket connections. This leads to select fields staying " +"empty (e.g. owner selection *after* selecting your group) or fields not " +"shown / hidden (e.g. when switching to or from pending states, the \"pending " +"till\" field not showing / hiding)." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:218 -msgid "These values can then be passed directly to the API:" +#: ../settings/system/frontend.rst:18 +msgid "" +"Please keep in mind that the Ajax fallback may cause serious pressure on " +"your application server. If you have the choice stick to web sockets." msgstr "" -#: ../system/integrations/checkmk/index.rst:16 -msgid "How does it work?" +#: ../settings/system/frontend.rst:22 +msgid "Default: ``no`` (inactive)" msgstr "" -#: ../system/integrations/checkmk/index.rst:2 -msgid "Checkmk" +#: ../settings/system/frontend.rst:53 +msgid "Show calendar weeks in the picker of date/datetime fields" msgstr "" -#: ../system/integrations/checkmk/index.rst:4 +#: ../settings/system/frontend.rst:25 msgid "" -"`Checkmk `_ is a powerful IT monitoring tool that can " -"send real-time status alerts to Zammad via email or REST API. Set these " -"alerts up in Checkmk, and Zammad will automatically create, update, and " -"close tickets based on the health of your system:" +"With this setting you can instruct Zammad to provide week number display " +"globally for all users. Calendar with week number display are usually used " +"in business sectors and may not be relevant for everyone." msgstr "" -#: ../system/integrations/checkmk/index.rst:14 -msgid "Screenshot of ticket created by Checkmk notifications" +#: ../settings/system/frontend.rst:29 +msgid "" +"This setting affects *all areas* - you'll also see week numbers in the admin " +"panel for e.g. triggers and macros." msgstr "" -#: ../system/integrations/checkmk/index.rst:14 -msgid "Multiple alerts, same ticket." +#: ../settings/system/frontend.rst:32 +msgid "Default: ``no`` (not shown)" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:2 -msgid "Setup Guide" +#: ../settings/system/frontend.rst:53 +msgid "Here's the difference:" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:4 -msgid "" -"Whenever the Checkmk integration is enabled, Zammad listens for messages on " -"its API and over email. As long as those messages follow the required " -"format, Zammad will create new tickets (or find and update existing ones) " -"based on the message contents." +#: ../settings/system/frontend.rst:0 +msgid "Screenshot showing Zammad's date picker (in the default way)" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:10 -msgid "" -"That means that “setting up Checkmk integration” is simply a matter of " -"**adding configuration to your Checkmk site**: telling it when to send these " -"messages and what to say. To do that, you'll need to create a new " -"**notification rule** (see `Checkmk's official docs `_ for help with that)." +#: ../settings/system/frontend.rst:41 +msgid "Set to ``no``" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:17 +#: ../settings/system/frontend.rst:0 msgid "" -"As part of this new rule, you'll have to choose a **notification method** " -"(*i.e.,* a script to execute whenever the rule is triggered). This script " -"will be written by you (samples below), and contain the logic for sending " -"API/email messages to Zammad:" +"Screenshot showing Zammad's date picker with\n" +"week numbers enabled" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:26 -msgid "Checkmk \"New Rule\" dialog" +#: ../settings/system/frontend.rst:50 +msgid "Set to ``yes``" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:26 +#: ../settings/system/index.rst:4 msgid "" -"Find your custom scripts in the Checkmk WATO under **Notifications > New " -"Rule > Notification Method**." +"For your overview we split each tab within system settings into its own page:" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:29 -msgid "" -"Once you're done setting up your new rule, you're all set! New tickets " -"should start coming in and auto-updating any time your rule is triggered." +#: ../settings/system/index.rst:16 +msgid "Console Based Settings" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:33 +#: ../settings/system/index.rst:18 msgid "" -"(If you need help troubleshooting, be sure to check the :ref:`checkmk-recent-" -"logs`.)" +"There's some console based settings we didn't put into the UI. However, you " +"may find them helpful - you can find them in our :docs:`hidden settings ` section." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:38 -msgid "API Alerts" +#: ../settings/system/network.rst:2 +msgid "Network" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:40 +#: ../settings/system/network.rst:8 msgid "" -"To add these scripts in the Checkmk WATO, copy them into your Checkmk " -"installation directory and make them executable. (Be sure to replace the " -"``zammad.example.com`` callback URL with the one found in your admin panel.)" +"The proxy settings can only be saved after successfully testing the proxy " +"connection." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:60 -msgid "Service notification" +#: ../settings/system/network.rst:15 +msgid "Proxy Address." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:46 +#: ../settings/system/network.rst:12 msgid "" -"For updates on the status of the software running on your server (*e.g.,* " -"postgres)." +"Allows you to provide a proxy server if needed. This is relevant for network " +"communication by Zammad." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:75 -msgid "Host notification" +#: ../settings/system/network.rst:15 +msgid "It **does not** affect the update process or Elasticsearch." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:63 -msgid "For updates on the status of the server itself." +#: ../settings/system/network.rst:18 +msgid "Username for proxy connection." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:77 -msgid "🤔 **What's with all the env vars?**" +#: ../settings/system/network.rst:18 +msgid "" +"If your proxy server requires authentication, provide the username here." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:79 -msgid "" -"Whenever Checkmk runs these scripts, it needs to provide some information " -"about the event that triggered the notification. This information is passed " -"in the form of these ``$NOTIFY_*`` environment variables." +#: ../settings/system/network.rst:21 +msgid "Password for proxy connection." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:85 +#: ../settings/system/network.rst:21 msgid "" -"You can specify additional parameters to pass to the script when you're " -"setting up your notification rule, but the ones you see here are all " -"provided by default." +"If your proxy server requires authentication, provide the password here." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:90 -msgid "Email Alerts" +#: ../settings/system/network.rst:26 +msgid "No proxy for the following hosts." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:94 +#: ../settings/system/network.rst:24 msgid "" -"🐞 **There are known bugs** in Zammad's processing of email from Checkmk. " -"This section will be completed once they have been resolved. (Learn more at " -"GitHub issues `#2377 `_ & " -"`#2180 `_.)" +"Exception list for hosts you can't or don't want to reach via proxy server." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:100 -msgid "In the meantime, we encourage you to set up API alerts instead." +#: ../settings/system/network.rst:27 +msgid "Default: ``localhost,127.0.0.0,::1``" msgstr "" -#: ../system/integrations/clearbit.rst:2 -msgid "Clearbit" +#: ../settings/system/services.rst:2 +msgid "Services" msgstr "" -#: ../system/integrations/clearbit.rst:4 -msgid "" -"With our Clearbit integration, you can easily enrich the information " -"provided by Zammad. If the customers or agents email address is known to " -"Clearbit, it will share all information it has regarding the user with " -"Zammad. Those information can include the following:" +#: ../settings/system/services.rst:10 +msgid "Image Service" msgstr "" -#: ../system/integrations/clearbit.rst:9 -msgid "Avatar" +#: ../settings/system/services.rst:5 +msgid "Defines the backend for user and organization image lookups." msgstr "" -#: ../system/integrations/clearbit.rst:10 -msgid "Address information" +#: ../settings/system/services.rst:7 +msgid "Default: ``Zammad Image Service`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:11 -msgid "Website information" +#: ../settings/system/services.rst:9 +msgid "" +"Make sure your on premise installation has ``HTTPS`` access to ``images." +"zammad.com``." msgstr "" -#: ../system/integrations/clearbit.rst:12 -msgid "A BIO (as Note by default)" +#: ../settings/system/services.rst:18 +msgid "Geo Calendar Service" msgstr "" -#: ../system/integrations/clearbit.rst:14 +#: ../settings/system/services.rst:13 msgid "" -"If needed, you can add further custom objects and add mappings to them, so " -"the Clearbit information can be filled within the database. In general you " -"can get any information from Clearbit, as long as you have a mapping to an " -"Zammad object." +"Defines the backend for geo calendar lookups. Used for initial calendar " +"setup." msgstr "" -#: ../system/integrations/clearbit.rst:21 -msgid "" -"Clearbit does have a mapping of fields like LDAP and Exchange have, but does " -"not \"win\" against Zammad information. This means that if you have e.g. the " -"last name field filled in already and Clearbit has other information on " -"that, it will not be updated." +#: ../settings/system/services.rst:16 +msgid "Default: ``Zammad GeoCalendar Service`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:26 +#: ../settings/system/services.include.rst:2 msgid "" -"However: If let's say the last name has been set by Clearbit and Zammad " -"notices that the last name on the Clearbit source has changed, Zammad will " -"also update this value." +"Make sure your on premise installation has ``HTTPS`` access to ``geo.zammad." +"com``." msgstr "" -#: ../system/integrations/clearbit.rst:33 -msgid "" -"The configuration of Clearbit is really easy and done fast! Just login to " -"your Clearbit-Account, go to \"API\" and copy the secret-API-Key." +#: ../settings/system/services.rst:26 +msgid "Geo IP Service" msgstr "" -#: ../system/integrations/clearbit.rst:38 +#: ../settings/system/services.rst:21 msgid "" -"Now change to your Zammad instance, go to Integrations (System) -> Clearbit " -"in the admin panel. Paste your API-Key into the API-Key-Field and decide if " -"Zammad should create unknown Organizations automatically, if the user does " -"not have one yet (and Clearbit knows it). The shared option decides if the " -"new organizations Zammad creates with Clearbit should be shared ones." +"Defines the backend for geo IP lookups. Shows also location of an IP address " +"if an IP address is shown." msgstr "" -#: ../system/integrations/clearbit.rst:47 -msgid "" -"If you're unsure what option to choose, better stick with \"no\". You can " -"also learn more about :doc:`/manage/organizations/index`." +#: ../settings/system/services.rst:24 +msgid "Default: ``Zammad GeoIP Service`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:52 -msgid "" -"The Mapping option works similar to the mapping within the Exchange and LDAP " -"sync. You can add further mappings for e.g. custom fields if you need more " -"information that Clearbit can provide." +#: ../settings/system/services.rst:32 +msgid "Geo Location Service" msgstr "" -#: ../system/integrations/clearbit.rst:58 +#: ../settings/system/services.rst:29 msgid "" -"If you want to add more Clearbit fields and want to learn more about " -"available fields on their API, you can take a look at their `API " -"documentation `_." +"Defines the backend for geo location lookups to store geo locations for " +"addresses." msgstr "" -#: ../system/integrations/clearbit.rst:62 +#: ../settings/system/services.rst:32 msgid "" -"If you're happy with the above chosen Settings and your mapping, just save " -"the changes and enable Clearbit integration. Zammad will now start polling " -"the Clearbit API as users contact you." +"Default: ``OpenStreetMap (ODbL 1.0, http://osm.org/copyright)`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:68 +#: ../settings/system/services.rst:36 msgid "" -"Zammad does not synchronize with Clearbit on a regular basis, but on demand " -"if needed. This saves API calls." +"You can find a detailed privacy information on what we store for how long on " +"our :docs:`Privacy Appendix ` inside of our System " +"Documentation." msgstr "" -#: ../system/integrations/clearbit.rst:73 +#: ../settings/system/storage.rst:2 +msgid "Storage" +msgstr "" + +#: ../settings/system/storage.rst:6 msgid "" -"Below the Settings and Mappings, you'll find our Integration log. You can " -"see what requests Zammad sent to Clearbit and also the APIs Response." +"Here you can define where Zammad stores attachments for tickets and the " +"knowledge base. By default, we're writing to the ``Database`` - you can " +"switch to ``Filesystem`` or ``Simple Storage (S3)`` at any time. In this " +"case please have a look on the following instructions." msgstr "" -#: ../system/integrations/clearbit.rst:78 +#: ../settings/system/storage.rst:11 msgid "" -"By the way, you can also view the API log on the Clearbit website - the " -"information seen is basically the same." +"If you have a busy Zammad instance, we strongly encourage you to use " +"filesystem storage instead of \"Database\". This will greatly improve system " +"performance (de-crease database load and size)." msgstr "" -#: ../system/integrations/clearbit.rst:84 -msgid "Example When Adding a User" +#: ../settings/system/storage.rst:19 +msgid "Database" msgstr "" -#: ../system/integrations/clearbit.rst:86 +#: ../settings/system/storage.rst:17 msgid "" -"To show you how fast information is added, we added a small Screencast " -"below. This shows the creation of the User Alex from Clearbit. As we already " -"set the last name of Alex to \"X\", Zammad did not update it. What Zammad " -"did was to add further information it received from Clearbit." +"This is the default storage method. The attachments are stored directly in " +"the database. If your Zammad instance grows, we recommend one of the other " +"methods to maintain performance." msgstr "" -#: ../system/integrations/cti/generic.rst:2 -msgid "CTI (generic)" +#: ../settings/system/storage.rst:38 +msgid "Filesystem" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:1 +#: ../settings/system/storage.rst:22 msgid "" -"This integration enables Zammad to provide a caller log to your agents. With " -"this your agents can greet your customers by their name and are supported by " -"Zammad with automatically opening a new ticket dialog or the user profile." +"This storage method is recommended for all Zammad instances, especially for " +"those with a higher load. If you choose filesystem, your files are written " +"to ``/opt/zammad/storage/``." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:6 +#: ../settings/system/storage.rst:26 msgid "" -"Click the toggle next to the heading to activate or deactivate this " -"integration." +"Moving attachments from \"Database\" to \"Filesystem\" can be run during " +"production use. However, you should consider your framework conditions (e.g. " +"bandwidth, system load in production) to define the right moment." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:9 -msgid "" -"If you want to learn more on how your agents can use this function, please " -"refer the :user-docs:`user documentation `." +#: ../settings/system/storage.rst:32 +msgid "**You noticed slow updates of Zammad?**" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:14 +#: ../settings/system/storage.rst:34 msgid "" -"Automatically opening new ticket dialogues or user profiles requires agent " -"to extension mapping - see more below." +"While Zammad is beeing updated, it enforces a recursive \"change " +"owner\" (chown) for this directory. For instances with many files this can " +"be time consuming. To mitigate that you can move your files and create a " +"symlink in ``/opt/zammad/storage/`` to the new directory. Of course you have " +"to make sure on your own that the permissions are always correct." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:20 -msgid "Please note the following limitations to reduce confusion later on:" +#: ../settings/system/storage.rst:95 +msgid "Simple Storage (S3)" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:22 -msgid "CTI integrations provide caller log functions only." +#: ../settings/system/storage.rst:41 +msgid "" +"To use the Simple Storage (S3), you have to provide some settings, which " +"can't be accessed in the UI (see instructions below)." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:23 +#: ../settings/system/storage.rst:44 msgid "" -"This integration does not provide any VoIP functionalities; you can't make " -"phone calls from within Zammad." +"⚠️ Please note that the current implementation is in its early stages and can " +"be modified in the future." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:25 +#: ../settings/system/storage.rst:47 msgid "" -"If your browser supports ``tel``-URLs, you can click on phone numbers for " -"automatic dialing. This requires additional software / configuration on your " -"agent's computers." +"The prerequisite is to have access to a S3-compatible storage and to have " +"all necessary parameters available (which depends on your storage provider; " +"if in doubt, please ask there for help)." msgstr "" -#: ../system/integrations/cti/generic.rst:9 -#: ../system/integrations/cti/placetel.rst:14 -#: ../system/integrations/cti/sipgate.rst:14 -msgid "Please provide the following requirements:" +#: ../settings/system/storage.rst:51 +msgid "Steps to configure S3:" msgstr "" -#: ../system/integrations/cti/generic.rst:11 +#: ../settings/system/storage.rst:53 msgid "" -"A telephone system that supports webhooks (outbound) (best option are those " -"that allow customizing the calls)." +"Copy ``config/zammad/storage.yml.dist`` to ``config/zammad/storage.yml``" msgstr "" -#: ../system/integrations/cti/generic.rst:13 -msgid "A unique Call-ID during the call session." +#: ../settings/system/storage.rst:54 +msgid "Edit the copied file in one of the following ways:" msgstr "" -#: ../system/integrations/cti/generic.rst:14 -msgid "Call event data (both numbers and direction)." +#: ../settings/system/storage.rst:56 +msgid "" +"Either provide your S3 configuration with one attribute per line like in the " +"upper area of the file" msgstr "" -#: ../system/integrations/cti/generic.rst:15 -msgid "Your Zammad instance must be reachable for your telephony system." +#: ../settings/system/storage.rst:58 +msgid "" +"Or provide your S3 configuration as an URL (which you can find at the end of " +"the file). Note: you can also provide this URL as environment variable (:" +"docs:`see system documentation `) without using this yml-file." msgstr "" -#: ../system/integrations/cti/generic.rst:17 +#: ../settings/system/storage.rst:62 msgid "" -"If you want to learn more on what kind of requests are supported by Zammad " -"and what it expects, please consult our :docs:`CTI-API documentation `." +"We recommend the deletion of the not used configuration style to avoid " +"inconsistencies." msgstr "" -#: ../system/integrations/cti/generic.rst:22 -#: ../system/integrations/cti/placetel.rst:27 -#: ../system/integrations/cti/sipgate.rst:30 -msgid "Available Settings" +#: ../settings/system/storage.rst:65 +msgid "Restart Zammad so the config file / environment variable is loaded" msgstr "" -#: ../system/integrations/cti/generic.rst:29 -#: ../system/integrations/cti/placetel.rst:41 -#: ../system/integrations/cti/sipgate.rst:40 -msgid "Endpoint Settings" +#: ../settings/system/storage.rst:66 +msgid "" +"Set the \"Storage Method\" in Zammad to ``Simple Storage (S3)`` in Settings " +"> System > Storage and click on \"Submit\". After that, Zammad checks your " +"configuration and the connection to the service and will raise an error " +"message if something is wrong." msgstr "" -#: ../system/integrations/cti/generic.rst:25 -msgid "" -"Zammad will list your generic CTI endpoint here. It contains a unique token " -"so ensure to keep this URL save." +#: ../settings/system/storage.rst:72 +msgid "A very simple storage configuration could look like this:" msgstr "" -#: ../system/integrations/cti/generic.rst:28 +#: ../settings/system/storage.rst:85 msgid "" -"You'll need this endpoint for your PBX to talk to Zammad, see :docs:`CTI-API " -"documentation `." +"Before setting the storage method to ``Simple Storage (S3)`` (step 4), " +"please make sure to have a working setup." msgstr "" -#: ../system/integrations/cti/includes/important-dont-forget-saving.include.rst:3 +#: ../settings/system/storage.rst:88 msgid "" -"All following options **do not save automatically**. Always use the Save " -"button on the lower end of the integration page!" +"You can verify this by running ``rails r 'Rails.logger = Logger.new(STDOUT); " +"pp Store::Provider::S3.ping?'`` in your Zammad directory. If everything is " +"fine, you should see ``true``, else you should see ``false`` and a simple " +"error message." msgstr "" -#: ../system/integrations/cti/generic.rst:43 -#: ../system/integrations/cti/placetel.rst:49 -#: ../system/integrations/cti/sipgate.rst:52 -msgid "Call Settings" +#: ../settings/system/storage.rst:93 +msgid "" +"If you installed Zammad through a package manager (rather than from source), " +"replace ``rails r`` with ``zammad run rails r`` above. To learn more, see :" +"docs:`Administration via Console `." msgstr "" -#: ../system/integrations/cti/generic.rst:39 -#: ../system/integrations/cti/placetel.rst:49 -#: ../system/integrations/cti/sipgate.rst:37 -#: ../system/integrations/cti/sipgate.rst:50 -msgid "Inbound" +#: ../settings/ticket.rst:4 +msgid "" +"Here you can adjust general ticket settings. Additional ones for the ticket " +"composer interface can be found in the :doc:`/misc/composer`." msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:1 -msgid "" -"This option allows you to block specific incoming caller IDs. It allows you " -"to temporarily reject e.g. spam callers without having to contact providers " -"or PBX administrators." +#: ../settings/ticket.rst:11 +msgid "Ticket Hook (default: ``Ticket#``)" msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:11 -msgid "Caller ID to block" +#: ../settings/ticket.rst:11 +msgid "The identifier for a ticket; *e.g.,* Ticket#, Call#, MyTicket#." msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 -msgid "Provide caller IDs to block in ``E.164`` format." +#: ../settings/ticket.rst:38 +msgid "Ticket Hook Position (default: ``right``)" msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:8 +#: ../settings/ticket.rst:14 msgid "" -"Your telephony system has to support this function. Zammad will send a " -"``reject`` response which will cause your telephony system to hang up the " -"call. To callers this usually will feel like the line is busy." +"With this setting you can decide (if) where to insert the ticket number." msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:14 -msgid "" -"Provide a meaningful note for your fellow administrators to remind yourself " -"why you've chosen to block the number." +#: ../settings/ticket.rst:20 +msgid "*Right*" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 -#: ../system/integrations/cti/includes/outbound-calls.include.rst:17 -#: ../system/integrations/cti/sipgate.rst:40 -msgid "Outbound" -msgstr "" - -#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:1 +#: ../settings/ticket.rst:17 msgid "" -"In many cases you may want to use a different caller ID depending on the " -"destination you're calling. This may apply due to specific connection rates " -"to other countries or because you want your customer to feel you're calling " -"from the same country." +"This setting will add the ticket reference on the right site of the subject." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:6 -msgid "This option expects ``E.164`` number formats." +#: ../settings/ticket.rst:20 +msgid "Example: ``Some Subject [Ticket#12345]``" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 -msgid "Destination caller ID" +#: ../settings/ticket.rst:26 +msgid "*Left*" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:5 -msgid "The caller ID or number you're trying to call." +#: ../settings/ticket.rst:23 +msgid "" +"This setting will add the ticket reference on the left site of the subject." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:7 -msgid "You can use wildcards for e.g. country specific outbound numbers like:" +#: ../settings/ticket.rst:26 +msgid "Example: ``[Ticket#12345] Some Subject``" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:9 -msgid "``49*`` for Germany" +#: ../settings/ticket.rst:29 +msgid "*None*" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:10 -msgid "``4930*`` for Berlin / Germany landlines" +#: ../settings/ticket.rst:29 +msgid "This will completely remove ticket references from the subject." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 -msgid "``33*`` for France" +#: ../settings/ticket.rst:33 +msgid "" +"Please ensure to take a look at :doc:`/channels/email/settings` within the " +"email channel to ensure you have at least one reference that helps Zammad to " +"assign follow-ups correctly." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:15 -msgid "Set Outbound caller ID" +#: ../settings/ticket.rst:37 +msgid "" +"Disabling this and not setting up any further follow up search will lead to " +"unexpected results!" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:14 +#: ../settings/ticket.rst:65 msgid "" -"The outbound caller ID to set (the number your customer sees on his display) " -"in ``E.164`` number format." +"Ticket Last Contact Behaviour (default: ``Use the start time of the last " +"customer thread (which may consist of multiple articles).``)" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 -msgid "Provide a short description for fellow administrators." +#: ../settings/ticket.rst:41 +msgid "" +"This setting changes the way Zammad updates the ``Last Contact`` value of a " +"ticket. This is fairly important for overviews and what you expect upon " +"ticket updates of a customer." msgstr "" -#: ../system/integrations/cti/includes/generic-cti-support-note.includes.rst:3 +#: ../settings/ticket.rst:52 msgid "" -"This option requires your PBX to send a specific request to Zammad *before " -"dialing*. Please consult the :docs:`CTI API ` in case " -"you're not sure." +"Use the start time of the last customer thread (which may consist of " +"multiple articles)." msgstr "" -#: ../system/integrations/cti/generic.rst:52 -#: ../system/integrations/cti/placetel.rst:54 -#: ../system/integrations/cti/sipgate.rst:59 -msgid "Other Settings" +#: ../settings/ticket.rst:46 +msgid "" +"If this option is chosen, Zammad will update the last updated value just " +"once if a customer replies. After that, Zammad will wait for an agent to " +"react." msgstr "" -#: ../system/integrations/cti/includes/other-settings-intro.include.rst:1 +#: ../settings/ticket.rst:50 msgid "" -"Below you can find all available additional settings for this CTI " -"integration. For your overview we're sorting them by appearance and " -"reference their description first." +"This comes in handy if you want to work tickets in the order of their first " +"update. This will not change ticket orders if customers decide to \"bump\" " +"the ticket affected." msgstr "" -#: ../system/integrations/cti/includes/default-caller-id.include.rst:2 -#: ../system/integrations/cti/includes/default-caller-id.include.rst:1 -msgid "Default caller ID for outbound calls" +#: ../settings/ticket.rst:57 +msgid "Use the time of the very last customer article." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:16 -#: ../system/integrations/cti/includes/records-caller-log.include.rst:15 -msgid "Shown records in caller log" +#: ../settings/ticket.rst:55 +msgid "" +"When setting this option, Zammad will always update the last updated value. " +"This means that if ordering by ``Last Update``, ticket orders will change if " +"customers \"bump\" the ticket." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:2 -msgid "" -"Allows you to set the number of shown caller log entries for all users. You " -"can choose from the following values:" +#: ../settings/ticket.rst:64 +msgid "Last contact value used on :doc:`/manage/overviews`" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:5 -msgid "60 (default)" +#: ../settings/ticket.rst:65 +msgid "Last contact value used on :doc:`/manage/trigger`" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:6 -msgid "120" +#: ../settings/ticket.rst:88 +msgid "" +"Ticket Organization Reassignment (default: ``Update the most recent tickets." +"``)" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:7 -msgid "180" +#: ../settings/ticket.rst:68 +msgid "" +"This setting changes the way Zammad updates the organization field of the " +"tickets whenever the primary organization of a user is changed." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:8 -msgid "240" +#: ../settings/ticket.rst:74 +msgid "Update the most recent tickets." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:9 -msgid "300" +#: ../settings/ticket.rst:72 +msgid "" +"If this option is chosen, Zammad will update the 100 most recent tickets " +"where the user is the ticket customer. The ticket organization field will be " +"automatically set to the new primary organization of the user." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:11 -msgid "**🥵 Potential performance issue**" +#: ../settings/ticket.rst:88 +msgid "Do not update any tickets." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:13 +#: ../settings/ticket.rst:77 msgid "" -"Setting this setting higher than 60 may cause serious performance issues on " -"very busy instances. Keep in mind that this setting causes Zammad to poll " -"and send up to 300 records to *all active agent sessions* in very short time " -"periods." +"When choosing this option, Zammad will not update any tickets when the " +"user's primary organization is changed." msgstr "" -#: ../system/integrations/cti/generic.rst:73 -msgid "Caller Log Filter" +#: ../settings/ticket.rst:80 +msgid "**Use with care!**" msgstr "" -#: ../system/integrations/cti/generic.rst:55 +#: ../settings/ticket.rst:82 msgid "" -"This function allows you to provide call information based on e.g. queues " -"only to agents that really need the information." +"Using this option may lead to inconsistencies in the system as the ticket " +"organization may become decoupled from the ticket customer." msgstr "" -#: ../system/integrations/cti/generic.rst:58 +#: ../settings/ticket.rst:85 msgid "" -"Why? If you have a team for several countries or departments, you don't want " -"to bug your agents from other departments. Leaving these options empty will " -"fallback to showing everything to everyone." +"However, you may use this option if you wish to maintain :ref:`the shared " +"access ` to the ticket for all organization " +"members of the original organization of the customer." msgstr "" -#: ../system/integrations/cti/generic.rst:64 -msgid "Destination caller ID or Queue" +#: ../settings/ticket.rst:110 +msgid "Ticket Number Format (default: ``Increment (SystemID.Counter)``)" msgstr "" -#: ../system/integrations/cti/generic.rst:63 +#: ../settings/ticket.rst:94 msgid "" -"This depends on your PBX and usually is either a queue ID, phone number or " -"extension." +"This setting defines the way Zammad's ticket number will look. Changing this " +"setting in production will cause follow up detection to fail." msgstr "" -#: ../system/integrations/cti/generic.rst:69 -msgid "Agents" +#: ../settings/ticket.rst:102 +msgid "Increment (SystemID.Counter)" msgstr "" -#: ../system/integrations/cti/generic.rst:67 +#: ../settings/ticket.rst:98 msgid "" -"Select the agents that are responsible for the group. These agents will then " -"see caller log entries and call notifications fitting to said queue." +"The increment value contains the SystemID (automatically generated during " +"installation) and a increment which counts up with every new Ticket. The " +"increment will automatically get another digit if needed." msgstr "" -#: ../system/integrations/cti/generic.rst:0 -msgid "" -"Screenshot showing the caller log filter table with pre filled sample data" +#: ../settings/ticket.rst:102 +msgid "Examples: ``1010138``, ``1010139``" msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:6 -msgid "" -"With recent logs Zammad allows you to view the latest calls for the CTI " -"functionality. This usually comes in handy, when you're looking for errors." +#: ../settings/ticket.rst:110 +msgid "Date (Year.Month.Day.SystemID.Counter)" msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:0 +#: ../settings/ticket.rst:105 msgid "" -"Screenshot showing several incoming requests within Recent logs section." +"This version of the ticket number is fairly long. However, because it " +"contains the date of ticket creation, it also allows you to see when the " +"ticket has been created. You may feel familiar with this number format if " +"you've worked with OTRS already." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:16 -msgid "I'm just here to clear floats up." +#: ../settings/ticket.rst:110 +msgid "Examples: ``201206231010138``, ``201206231010139``" msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:20 -msgid "" -"By clicking on the entry of interest, Zammad will provide more details on " -"the call in question. You'll see the payload it received and also the " -"response that was sent." +#: ../settings/ticket.rst:137 +msgid "OPTIONS" msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:0 +#: ../settings/ticket.rst:113 msgid "" -"Screenshot showing detailed information of a specific log entry of recent " -"logs" -msgstr "" - -#: ../system/integrations/cti/includes/recent-logs.include.rst:31 -msgid "x" +"The below options allow you to further customize your ticket number. The " +"availability of options differ depending of the chosen ticket number format " +"above." msgstr "" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 -#: ../system/integrations/cti/includes/troubleshooting.include.rst:9 -msgid "My Phone page stays blank, signalling does work..." +#: ../settings/ticket.rst:122 +msgid "Checksum (default: ``no``)" msgstr "" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:5 +#: ../settings/ticket.rst:118 msgid "" -"If you've made sure that signalling works (check Recent logs) and your " -"Caller Log still stays empty, please ensure that you only configured one CTI " -"integration version. Specifically defining more than one agent mapping on " -"the different integration variants will be the issue." +"If set to yes, we'll built a checksum to further \"unique\" the ticket " +"number of your system. If you're dealing with many other ticket systems this " +"might help to prevent false positive follow up detection on tickets." msgstr "" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 -msgid "Clear the not needed agent mapping and reload your browser page." +#: ../settings/ticket.rst:122 +msgid "This will also add another digit to the ticket number." msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:1 -msgid "" -"By mapping your agents extension to their existing Zammad users, Zammad can " -"provide a new ticket dialog or open the user profile for the agent that " -"picks up the call." +#: ../settings/ticket.rst:137 +msgid "Min. size of Number (default: ``5``)" msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:5 +#: ../settings/ticket.rst:125 msgid "" -"This speeds up ticket aiding, no matter if it's for existing tickets or new " -"ones!" +"This setting defines the minimum length of your ticket number. If your " +"counter is not yet high enough, Zammad will fill the number with zeros to " +"ensure the wanted length." msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:8 +#: ../settings/ticket.rst:129 msgid "" -"To see it work from the agent's perspective, have a look on :user-docs:`user " -"documentation `." -msgstr "" - -#: ../system/integrations/cti/placetel.rst:2 -msgid "Placetel CTI" -msgstr "" - -#: ../system/integrations/cti/placetel.rst:16 -msgid "You need an administrative Placetel account for your organization." +"Please note that the minimum length is ``3`` (SystemID + at least one digit " +"if below 10). Also, if the length is no longer long enough, the number will " +"automatically get one digit longer. Ticket-Numbers **do not overflow**, thus " +"it's save to keep it at 5 or set it lower if wanted." msgstr "" -#: ../system/integrations/cti/placetel.rst:17 -#: ../system/integrations/cti/sipgate.rst:20 +#: ../settings/ticket.rst:135 msgid "" -"Your Zammad instance must be allowed to communicate to external services." +"This option is only available if ticket number format is set to " +"``Increment``!" msgstr "" -#: ../system/integrations/cti/placetel.rst:18 -msgid "Placetel must be able to reach your Zammad instance." +#: ../settings/ticket.rst:142 +msgid "Auto-Assignment" msgstr "" -#: ../system/integrations/cti/placetel.rst:22 -msgid ":doc:`provider-configurations/placetel`" +#: ../settings/ticket.rst:144 +msgid "" +"In a larger Zammad environment, it happens that several agents open the same " +"ticket at the same time. Although collision detection is then effective, the " +"efficiency of processing can be increased by means of the automatic " +"assignment of tickets when a ticket is opened." msgstr "" -#: ../system/integrations/cti/placetel.rst:21 +#: ../settings/ticket.rst:149 msgid "" -"Learn how to configure Placetel to enable Zammad and Placetel to communicate " -"with each other." +"The automatic assignment of tickets can be activated and configured in the " +"admin area under Settings > Ticket > Auto Assignment." msgstr "" -#: ../system/integrations/cti/placetel.rst:32 +#: ../settings/ticket.rst:152 msgid "" -"The here listed endpoint settings are relevant for the :doc:`integration " -"configuration with Placetel `." +"The auto assignment only works if the ticket has no owner yet. By default, " +"the agent can always reset the ticket owner to ``-`` if needed." msgstr "" -#: ../system/integrations/cti/placetel.rst:37 -#: ../system/integrations/i-doit.rst:53 -msgid "Endpoint" +#: ../settings/ticket.rst:155 +msgid "" +"If you want to use this function for only specific tickets, you can " +"configure the conditions accordingly to meet your requirement. By default " +"the condition affects all tickets with the state ``open``." msgstr "" -#: ../system/integrations/cti/placetel.rst:36 +#: ../settings/ticket.rst:161 msgid "" -"This endpoint will be required for the Zammad integration within the " -"Placetel web interface." +"If you need to exclude users (e.g. a group leader), you can search and " +"select the desired agents in the ``Exception Users`` list. The search " +"function in this area is only effective, if you have too many agents to " +"display at once to help you with the configuration." msgstr "" -#: ../system/integrations/cti/placetel.rst:41 -msgid "API Token" +#: ../settings/ticket.rst:167 +msgid "Notifications" msgstr "" -#: ../system/integrations/cti/placetel.rst:40 -msgid "" -"You'll receive this token within the ``Web API`` menu. Make sure to copy " -"this value, it's only shown once!" +#: ../settings/ticket.rst:191 +msgid "Default Notifications" msgstr "" -#: ../system/integrations/cti/placetel.rst:71 -#: ../system/integrations/cti/sipgate.rst:77 -msgid "Phone Extension to Agent Mapping" +#: ../settings/ticket.rst:170 +msgid "" +"This setting allows you to configure the default ticket notifications that " +"will be applied to all new agent users (incl. users who were just assigned " +"agent role). Simply change the notification matrix to desired state and " +"press **Save**." msgstr "" -#: ../system/integrations/cti/placetel.rst:0 -msgid "Screenshot showing sample user mappings in between Placetel and Zammad" +#: ../settings/ticket.rst:175 +msgid "" +"In case an agent already exists, their ticket notification preferences will " +"be preserved. Optionally, you can also **Apply current defaults to all " +"agents**." msgstr "" -#: ../system/integrations/cti/placetel.rst:64 +#: ../settings/ticket.rst:181 msgid "" -"You can find your agents Placetel username combination required within ⚙️ PBX " -"→ VoIP destinations. Within the \"Advanced settings\" section you're looking " -"for \"SIP user name\" and \"SIP server\"." +"**Potential time-consuming action:** Applying default ticket notifications " +"to all agent users may take some time to complete, be patient! The exact " +"time will depend on the size of your system and the number of agents." msgstr "" -#: ../system/integrations/cti/placetel.rst:68 -msgid "Combine these two like so: ``@``." +#: ../settings/ticket.rst:185 +msgid "" +"**Active agents only!** When current default ticket notifications are " +"applied, only active agent users are considered. In case an agent is re-" +"activated *after* this action, they will still have the old notification " +"configuration." msgstr "" -#: ../system/integrations/cti/placetel.rst:0 -msgid "Sample VoIP credentials for a Placetel user" +#: ../settings/ticket.rst:190 +msgid "" +"In case you want to go back to the initial state of ticket notifications, " +"you can click on **Reset to default** button." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:2 -msgid "Setup Placetel connection for Zammad" +#: ../settings/ticket.rst:196 +msgid "Duplicate Detection" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:6 -msgid "" -"This configuration step requires a *full* administrative Placetel account. " -"You may receive forbidden error messages with Placetel in case your " -"permissions are not high enough." +#: ../settings/ticket.rst:238 +msgid "Detect Duplicate Ticket Creation" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:10 +#: ../settings/ticket.rst:199 msgid "" -"The following actions can be configured via the `Placetel web interface " -"`_." +"This setting turns on the duplicate ticket detection mechanism during ticket " +"creation. If similar tickets are found in the system, a suitable warning " +"will be shown to the user trying to create a ticket." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:29 -msgid "Step 1: Activate Zammad integration" +#: ../settings/ticket.rst:206 +msgid "A Sample Duplicate Ticket Warning" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:14 +#: ../settings/ticket.rst:208 msgid "" -"Within Integrations, scroll down to Partner integrations and select Zammad." +"You can choose which ticket attributes will be matched by selecting them in " +"**Attributes to compare** field. Only if the ticket attribute value provided " +"by the user in the ticket create form is *equal* with the attribute in an " +"existing ticket, the warning will be shown." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:17 -msgid "" -"You can alternatively filter by \"Ticket Systems\" to reduce the number of " -"entries on the page. You'll still want to look for Partner integrations. 🤓" +#: ../settings/ticket.rst:213 +msgid "**Warning title** and **Warning message** are configurable as well." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:21 +#: ../settings/ticket.rst:215 msgid "" -"Within the Zammad integration now press \"Activate\". A new tab ``API`` " -"becomes available - open this tab." +"You can limit the detection only to certain user roles. By default, only " +"agents will see the warning." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:24 +#: ../settings/ticket.rst:218 msgid "" -"Now tick \"Enable Call Control / Notify API\" and paste the Placetel " -"endpoint from your Zammad instance into the field \"URL of your API " -"endpoint\". Save to apply the settings" +"If you don't want to show the matched tickets as part of the warning, you " +"can set **Show matching ticket(s) in the warning** setting to *no*." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 -msgid "Screencast showing how to activate the Zammad integration" +#: ../settings/ticket.rst:221 +msgid "" +"By default, **Permission level for looking up ticket** is set to *User*, " +"which means user permissions will be honored during sarch. The user will " +"see the warning only if tickets they have access to are matched. " +"Alternatively, you can set this setting to *System*, in which case the " +"search will happen within *all* tickets in the system, regardless of user " +"permissions." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:51 -msgid "Step 2: Generate API Token for Placetel" +#: ../settings/ticket.rst:227 +msgid "**🦺 Safety first!**" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:32 +#: ../settings/ticket.rst:229 msgid "" -"Go back to the integrations page and scroll down to \"Web API\". Generate a " -"new API token by using the \"Create a new API token\" button." +"Even if the permission level is set to *System*, the user will not be shown " +"the tickets they don't have access to in the warning, even if they match." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:37 +#: ../settings/ticket.rst:233 msgid "" -"If you already generated a token either use your existing token or reset it " -"by using above mentioned button. Placetel will ask you to conform this reset." +"However, just the confirmation about the existence of the tickets in the " +"system may be considered an unwanted information disclosure. Use this option " +"carefully!" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:41 +#: ../settings/ticket.rst:237 msgid "" -"Please keep in mind that existing API scripts may no longer work due to " -"token resets!" +"Finally, you can configure between matching within **All tickets** or **Open " +"tickets** only by setting **Match tickets in following states**. Depending " +"on the current ticket state, a ticket may or not be matched." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:44 -msgid "" -"Copy the provided API token and insert it into the \"API Token\" field " -"within Zammad's Placetel integration." +#: ../system/core-workflows.rst:2 +msgid "Core Workflows" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:47 +#: ../system/core-workflows.rst:4 msgid "" -"Apply your changes by using the \"Save\" button on the bottom of the " -"Placetel integration page and activate the Placetel integration." +"Core Workflows allow you to adjust object attributes in many ways. For " +"example:" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 -msgid "" -"Screencast showing how to retrieve an API token from Placetel for Zammad" +#: ../system/core-workflows.rst:7 +msgid "show / hide fields" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:73 -#: ../system/integrations/cti/provider-configurations/sipgate.rst:77 -msgid "Step 3: Restrict the numbers to notify on" +#: ../system/core-workflows.rst:8 +msgid "adjust mandatory setting" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:54 -msgid "" -"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " -"the the Integrations page of the Placetel web interface, go to \"Notify " -"API\"." +#: ../system/core-workflows.rst:9 +msgid "manipulate available options" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:58 +#: ../system/core-workflows.rst:11 msgid "" -"Lower on the page Placetel allows you to restrict the numbers to notify on. " -"You'll find this within the \"External routing API\" part." +"With this, you can provide exactly the information your users really need!" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +#: ../system/core-workflows.rst:15 msgid "" -"Screenshot showing a sample selection of phone numbers to use for the " -"Placetels notify API" +"If the pre-defined :doc:`/system/objects` are not enough, please add them " +"beforehand." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:66 +#: ../system/core-workflows.rst:17 msgid "" -"This menu point also provides a API request log from Placetel view. Just " -"open \"Recent responses of your API endpoint\" to learn more." +"If you experience slow or unreliable field updates, please see :ref:`Core " +"Workflow Ajax Modus `" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:69 +#: ../system/core-workflows.rst:22 msgid "" -"If you want to see Zammad's perspective, use the \"Recent Logs\" part from " -"within the Placetel integration page." +"This is a very enhanced functionality and can cause unexpected UI behavior. " +"Please ensure to test your use cases after configuration to reduce surprises." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 -msgid "Screenshot showing sample log entries for Placetels API calls to Zammad" +#: ../system/core-workflows.rst:None +msgid "Dialogue for adding a new workflow" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:77 -msgid "Step 4 (optional): Further configurations for Placetel" +#: ../system/core-workflows/condition-operators.rst:2 +msgid "Core Workflow Condition Operators" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:76 +#: ../system/core-workflows/condition-operators.rst:4 msgid "" -"If needed, you can now configure Zammad's Placetel integration in more " -"detail. You can learn more about your options here: :ref:`Placetel " -"integration settings `." +"You might know that there is a separate section for explaining :doc:" +"`condition operators `. Head over there to " +"see a detailed explanation of many conditions and operators." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:2 -msgid "Setup Sipgate connection for Zammad" +#: ../system/core-workflows/condition-operators.rst:8 +msgid "" +"Due to differences to other places in Zammad which are also using conditions " +"(e.g. triggers), you can find a dedicated description of operators for core " +"workflows below." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +#: ../system/core-workflows/condition-operators.rst:12 msgid "" -"Sipgate has no english web interface which is why this documentation page is " -"mixing up languages badly." +"Be aware that the availability of the operators depends on the selected " +"attribute and its field type. Some of the operators may only be available " +"for system attributes (e.g. for \"tags\", \"active\")." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Please also note that the availability of API addons highly depends on your " -"package trier. Usage of sipgate.io packages *is not free*, please check " -"their `pricing page `_ before!" +#: ../system/core-workflows/condition-operators.rst:20 +msgid "Operator" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:35 -msgid "Step 1: Book sipgate.io package" +#: ../system/core-workflows/condition-operators.rst:22 +msgid "after (absolute)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:13 -msgid "Skip to step 2 if you already have the package booked!" +#: ../system/core-workflows/condition-operators.rst:23 +msgid "Matches if a date/time is after a specific point in time." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:15 -msgid "" -"Login to an administrative Sipgate account and navigate to " -"``Accountverwaltung``. You'll see several different options depending on " -"your booked packages. Select ``Verträge & Produkte`` to continue." +#: ../system/core-workflows/condition-operators.rst:24 +msgid "after (relative)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:19 -msgid "" -"Scroll down to the section ``Zusätzliche Produkte buchen`` and look for " -"``sipgate.io`` - select this product by using the ``Produkte anzeigen``-" -"Button." +#: ../system/core-workflows/condition-operators.rst:25 +msgid "Matches if a time span after a specified event has passed." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:23 -msgid "" -"On the next page select either one of the ``sipgate.io`` packages or ``Push-" -"API Package Free``. Follow the dialogue by booking the addon. You'll be " -"returned to your contract overview and now should see the selected addon in " -"your list." +#: ../system/core-workflows/condition-operators.rst:26 +msgid "before (absolute)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:30 -msgid "" -"The availability for ``sipgate.io`` packages and their levels highly depends " -"on the overall account type and product you've booked with Sipgate." +#: ../system/core-workflows/condition-operators.rst:27 +msgid "Matches if a date/time is before a specific point in time." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screencast showing the process on how to book the required sipgate.io addon" +#: ../system/core-workflows/condition-operators.rst:28 +msgid "before (relative)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:52 -msgid "Step 2: Configure webhook for Zammad" +#: ../system/core-workflows/condition-operators.rst:29 +msgid "Matches if a time span after a specified event has not passed." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:38 -msgid "" -"Within your ``Accountverwaltung`` navicate to your product ``sipgate.io``. " -"In the newly opened tab, switch from \"Clients\" to \"Webhooks\" and paste " -"the endpoint URLs from your Zammad instance like so:" +#: ../system/core-workflows/condition-operators.rst:30 +msgid "contains" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:42 -msgid "Inbound endpoint to \"Incoming\"" +#: ../system/core-workflows/condition-operators.rst:31 +msgid "Matches if a specified value is present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:43 -msgid "Outbound endpoint to \"Outgoing\"" +#: ../system/core-workflows/condition-operators.rst:33 +msgid "Matches if all of the specified values are present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:47 -msgid "" -"Ensure to select at least one call group or phoneline within \"Sources\". " -"Other wise Sipgate will not indicate any incoming or outgoing calls to " -"Zammad." +#: ../system/core-workflows/condition-operators.rst:35 +msgid "Matches if none of the specified values are present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screencast showing how to add Zammad's endpoint URLs to sipgate.ios webhook " -"configuration" +#: ../system/core-workflows/condition-operators.rst:36 +msgid "contains not" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:55 -msgid "" -"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " -"the Webhooks → URLs section of Sipgate you can select which *sources* " -"Sipgate should notify Zammad about in- and outgoing calls." +#: ../system/core-workflows/condition-operators.rst:37 +msgid "Matches if a specified value is not present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:59 -msgid "" -"Use either specific phone lines or use the option \"Use for all phonelines " -"and groups\" to notify Zammad about all existing lines of your Sipgate " -"account." +#: ../system/core-workflows/condition-operators.rst:39 +msgid "Matches if one specified value is present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screenshot showing a sample selection of phone numbers to use for the " -"Sipgates webhooks API" +#: ../system/core-workflows/condition-operators.rst:41 +msgid "Matches if one specified value is not present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:68 -msgid "This section also allows you to enable a Debug log." +#: ../system/core-workflows/condition-operators.rst:42 +msgid "does not match regex" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "Screenshot showing an enabled Debug log option" +#: ../system/core-workflows/condition-operators.rst:43 +msgid "Matches if content doesn't fit to regex rule." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:73 -msgid "" -"After enabling you can use the Debug log section to see all sent webhook " -"calls to Zammad. You'll also can see the response." +#: ../system/core-workflows/condition-operators.rst:44 +msgid "ends with" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screenshot showing sample log entries for Sipgates webhook calls to Zammad" +#: ../system/core-workflows/condition-operators.rst:45 +msgid "Matches if content ends with specified value." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:81 -msgid "Step 4 (optional): Further configurations for Sipgate" +#: ../system/core-workflows/condition-operators.rst:46 +msgid "ends with one of" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:80 -msgid "" -"If needed, you can now configure Zammad's Sipgate integration in more " -"detail. You can learn more about your options here: :ref:`Sipgate " -"integration settings `." +#: ../system/core-workflows/condition-operators.rst:47 +msgid "Matches if content ends with one of the specified values." msgstr "" -#: ../system/integrations/cti/sipgate.rst:2 -msgid "Sipgate (sipgate.io)" +#: ../system/core-workflows/condition-operators.rst:48 +msgid "from (relative)" msgstr "" -#: ../system/integrations/cti/sipgate.rst:16 -msgid "You need an administrative Sipgate account for your organization." +#: ../system/core-workflows/condition-operators.rst:49 +msgid "Matches if date/time is after a period of time after an event." msgstr "" -#: ../system/integrations/cti/sipgate.rst:17 -msgid "" -"Zammad requires a ``sipgate.io`` addon from the feature store (please note " -"that API calls are not free with Sipgate. Rates may apply and differ from " -"account to account)." +#: ../system/core-workflows/condition-operators.rst:51 +msgid "Matches if content is equal to a specified value." msgstr "" -#: ../system/integrations/cti/sipgate.rst:21 -msgid "Sipgate must be able to reach your Zammad instance." +#: ../system/core-workflows/condition-operators.rst:52 +msgid "is any of" msgstr "" -#: ../system/integrations/cti/sipgate.rst:25 -msgid ":doc:`provider-configurations/sipgate`" +#: ../system/core-workflows/condition-operators.rst:53 +msgid "Matches if content is equal to any of specified values." msgstr "" -#: ../system/integrations/cti/sipgate.rst:24 -msgid "" -"Learn how to configure Sipgate to enable Zammad and Sipgate to communicate " -"with each other." +#: ../system/core-workflows/condition-operators.rst:54 +msgid "is modified" msgstr "" -#: ../system/integrations/cti/sipgate.rst:33 -msgid "" -"Below endpoint settings affect the :doc:`sipgate.io configuration `." +#: ../system/core-workflows/condition-operators.rst:55 +msgid "Matches if content is modified." msgstr "" -#: ../system/integrations/cti/sipgate.rst:37 -msgid "This endpoint is required for incoming call hooks." +#: ../system/core-workflows/condition-operators.rst:57 +#: ../system/core-workflows/condition-operators.rst:61 +msgid "True from the moment of changing content until form submit." msgstr "" -#: ../system/integrations/cti/sipgate.rst:40 -msgid "This endpoint is required for outgoing call hooks." +#: ../system/core-workflows/condition-operators.rst:58 +msgid "is modified to" msgstr "" -#: ../system/integrations/cti/sipgate.rst:0 -msgid "Screenshot showing sample user mappings in between Sipgate and Zammad" +#: ../system/core-workflows/condition-operators.rst:59 +msgid "Matches if content is modified to a specific value." msgstr "" -#: ../system/integrations/cti/sipgate.rst:69 -msgid "" -"You can find your agent's Sipgate username within ``Accountverwaltung → " -"Benutzer``. You're looking for the SIP-ID." +#: ../system/core-workflows/condition-operators.rst:62 +msgid "is none of" msgstr "" -#: ../system/integrations/cti/sipgate.rst:0 -msgid "Sample VoIP credentials for a Sipgate user" +#: ../system/core-workflows/condition-operators.rst:63 +msgid "Matches if content is none of any specified values." msgstr "" -#: ../system/integrations/cti/sipgate.rst:77 -msgid "Users with several devices also have several SIP-IDs." +#: ../system/core-workflows/condition-operators.rst:65 +msgid "Matches if content is not equal to a specified value." msgstr "" -#: ../system/integrations/elasticsearch.rst:2 -msgid "Elasticsearch (SaaS)" +#: ../system/core-workflows/condition-operators.rst:67 +msgid "Matches if content is present." msgstr "" -#: ../system/integrations/elasticsearch.rst:4 -msgid "" -"The Elasticsearch integration allows you to create a read-only user to use " -"with your favorite reporting tool (e.g. like Grafana)." +#: ../system/core-workflows/condition-operators.rst:68 +msgid "just changed" msgstr "" -#: ../system/integrations/elasticsearch.rst:7 -msgid "" -"If you want to take full advantage of the Zammad reporting, have a look at " -"our :docs:`Grafana ` " -"setup page as well." +#: ../system/core-workflows/condition-operators.rst:69 +msgid "Matches if content has changed." msgstr "" -#: ../system/integrations/elasticsearch.rst:11 -#: ../system/subscription/index.rst:7 -msgid "**🚧 Hosted environment specific 🚧**" +#: ../system/core-workflows/condition-operators.rst:71 +#: ../system/core-workflows/condition-operators.rst:75 +msgid "" +"Only true for the moment of changing content until next form field action/" +"click." msgstr "" -#: ../system/integrations/elasticsearch.rst:13 -msgid "" -"This integration is only available for Hosted setups. In order to use " -"Elasticsearch you'll need the **Plus** subscription." +#: ../system/core-workflows/condition-operators.rst:72 +msgid "just changed to" msgstr "" -#: ../system/integrations/elasticsearch.rst:16 -msgid "" -"Self hosted users have all the control over their self hosted Elasticsearch " -"instances." +#: ../system/core-workflows/condition-operators.rst:73 +msgid "Matches if content has changed to a specified value." msgstr "" -#: ../system/integrations/elasticsearch.rst:None -msgid "Elasticsearch integration page on SaaS environments" +#: ../system/core-workflows/condition-operators.rst:76 +msgid "matches regex" msgstr "" -#: ../system/integrations/elasticsearch.rst:27 -msgid "" -"Please note the following limitations of Elasticsearch access on hosted " -"environments:" +#: ../system/core-workflows/condition-operators.rst:77 +msgid "Matches if value fits to regex rule." msgstr "" -#: ../system/integrations/elasticsearch.rst:30 -msgid "access to the Elasticsearch index is read-only access" +#: ../system/core-workflows/condition-operators.rst:79 +msgid "Matches if no content is present." msgstr "" -#: ../system/integrations/elasticsearch.rst:31 -msgid "currently you're limited to user only" +#: ../system/core-workflows/condition-operators.rst:80 +msgid "starts with" msgstr "" -#: ../system/integrations/elasticsearch.rst:32 -msgid "" -"Reporting tools that require to write into the indexes (like Kibana) are not " -"supported" +#: ../system/core-workflows/condition-operators.rst:81 +msgid "Matches if content starts with specified value." msgstr "" -#: ../system/integrations/elasticsearch.rst:34 -msgid "IP access restriction is currently not yet supported" +#: ../system/core-workflows/condition-operators.rst:82 +msgid "starts with one of" msgstr "" -#: ../system/integrations/elasticsearch.rst:37 -msgid "Activating Elasticsearch Access" +#: ../system/core-workflows/condition-operators.rst:83 +msgid "Matches if content starts with one of the specified values." msgstr "" -#: ../system/integrations/elasticsearch.rst:39 -msgid "" -"By default external access to your Elasticsearch index is not active. You " -"can enable the integration at any time if needed." +#: ../system/core-workflows/condition-operators.rst:84 +msgid "till (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:42 -msgid "" -"Please ensure to note down the password provided - you won't have access to " -"it afterwards." +#: ../system/core-workflows/condition-operators.rst:85 +msgid "Matches if date/time is before a period of time before an event." msgstr "" -#: ../system/integrations/elasticsearch.rst:None -msgid "Screencast showing activation of Elasticsearch integration" +#: ../system/core-workflows/condition-operators.rst:86 +msgid "today" msgstr "" -#: ../system/integrations/elasticsearch.rst:51 -msgid "Connection Settings" +#: ../system/core-workflows/condition-operators.rst:87 +msgid "Matches if date/time is today." msgstr "" -#: ../system/integrations/elasticsearch.rst:53 -msgid "" -"This section holds the most important general information for accessing your " -"Elasticsearch indexes - such as:" +#: ../system/core-workflows/condition-operators.rst:88 +msgid "within last (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:57 -msgid "A unique subdomain that does not tell your real instance URL." +#: ../system/core-workflows/condition-operators.rst:89 +msgid "" +"Matches if date/time content is within specified period of time before now." msgstr "" -#: ../system/integrations/elasticsearch.rst:61 -msgid "Software" +#: ../system/core-workflows/condition-operators.rst:91 +msgid "within next (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:60 +#: ../system/core-workflows/condition-operators.rst:92 msgid "" -"The major version of the search index being used. This is required by some " -"Reporting tools like Grafana." -msgstr "" - -#: ../system/integrations/elasticsearch.rst:64 -msgid "Authentication" +"Matches if date/time content is within specified period of time after now." msgstr "" -#: ../system/integrations/elasticsearch.rst:64 -msgid "The authentication type being supported. ``Basic Authentication``" +#: ../system/core-workflows/how-do-they-work.rst:2 +msgid "How do they work?" msgstr "" -#: ../system/integrations/elasticsearch.rst:67 -msgid "Available Indexes" +#: ../system/core-workflows/how-do-they-work.rst:4 +msgid "" +"Core Workflows are executed according to their priority. If two workflows " +"have the same priority, they are executed in alphabetical order based on " +"their **name**." msgstr "" -#: ../system/integrations/elasticsearch.rst:69 +#: ../system/core-workflows/how-do-they-work.rst:8 msgid "" -"Within this section we're displaying the -in our opinion- most important " -"indexes for a Zammad instance." +"Because of the way Core Workflows work, all changes to attributes are " +"checked with the application server - please see :doc:`limitations` for " +"possible issues." msgstr "" -#: ../system/integrations/elasticsearch.rst:72 +#: ../system/core-workflows/how-do-they-work.rst:12 msgid "" -"If you require all indexes or our listing is not good enough for you, point " -"your browser to the URL we're providing and append ``/_aliases?" -"pretty=true``. The result should look like this: ``https://.zammad.com/" -"_aliases?pretty=true``." +"Below we're talking about settings that are important and not self-" +"explanatory." msgstr "" -#: ../system/integrations/elasticsearch.rst:77 +#: ../system/core-workflows/how-do-they-work.rst:17 msgid "" -"Your browser will automatically ask for your credentials - you'll then see " -"something like this:" +"Choose the object context you want to run the workflow in. This will decide " +"on your available attributes and actions." msgstr "" -#: ../system/integrations/elasticsearch.rst:125 -msgid "Credentials" +#: ../system/core-workflows/how-do-they-work.rst:20 +msgid "Ticket objects also have access to the ticket customer." msgstr "" -#: ../system/integrations/elasticsearch.rst:127 +#: ../system/core-workflows/how-do-they-work.rst:25 msgid "" -"Within this section Zammad displays your available users. The password is " -"provided once (upon activation) and cannot be retrieved after that." +"Choose in which situation the workflow is applied. Contexts can be combined " +"to avoid duplicate workflows." msgstr "" -#: ../system/integrations/elasticsearch.rst:131 +#: ../system/core-workflows/how-do-they-work.rst:30 +msgid "Creation mask" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:29 msgid "" -"If you need to change or reset your Elasticsearch user password, use the " -"\"Reset password\" button in the credentials table. Doing so creates a brand " -"new password for the account in question. This change is immediate, keep in " -"mind that this may affect third party tools connected to your instance." +"If selected, your conditions and actions will affect all applicable creation " +"masks." msgstr "" -#: ../system/integrations/exchange.rst:2 -msgid "Exchange" +#: ../system/core-workflows/how-do-they-work.rst:34 +msgid "Edit mask" msgstr "" -#: ../system/integrations/exchange.rst:4 +#: ../system/core-workflows/how-do-they-work.rst:33 msgid "" -"With Zammad's Exchange integration, you can easily use existing address " -"books without having to update more than one source." +"If selected, your conditions and actions will affect all applicable edit " +"masks." msgstr "" -#: ../system/integrations/exchange.rst:7 +#: ../system/core-workflows/how-do-they-work.rst:39 msgid "" -"However, you should refrain from syncing all addresses, as the results may " -"not be what you expect (Exchange collects huge amounts of addresses). A " -"central address book of your company to sync makes more sense, as you can " -"ensure that Zammad gets only the data you need and want. Apart from this, it " -"is even not possible to sync the Global Address List (GAL) of your Exchange " -"system with Zammad." +"Zammad differentiates between selected and saved conditions. These can be " +"combined wherever needed." msgstr "" -#: ../system/integrations/exchange.rst:16 -msgid "" -"**Exchange and LDAP:** The exchange sync can be overruled by Zammad's LDAP " -"integration. If you have the same users in both sources, the LDAP version " -"will always be Zammad's pick." +#: ../system/core-workflows/how-do-they-work.rst:42 +msgid "**⚠️ Restrict workflows to specific roles if needed!**" msgstr "" -#: ../system/integrations/exchange.rst:19 +#: ../system/core-workflows/how-do-they-work.rst:44 msgid "" -"**One way sync:** the Exchange sync is one way. Exchange => Zammad. Changes " -"to your users inside of Zammad might be overwritten by the Exchange sync." +"By default and unless configured in conditions, workflow rules are executed " +"for **all roles**. This also affects your customers!" msgstr "" -#: ../system/integrations/exchange.rst:24 -msgid "" -"To configure Exchange integration, simply go to the System > Integrations > " -"Exchange in the admin panel. Press \"change\" and follow the wizard for " -"adding the needed Exchange information to Zammad. On the last two steps " -"Zammad will ask you for the address book(s) and your desired attribute " -"mapping. By default, Zammad only maps email address, first- and lastname. " -"Technically, you can map any Exchange object to a Zammad user object (this " -"also works for custom objects!)." +#: ../system/core-workflows/how-do-they-work.rst:50 +msgid "Selected Conditions" msgstr "" -#: ../system/integrations/exchange.rst:35 +#: ../system/core-workflows/how-do-they-work.rst:48 msgid "" -"If the SSL verification fails while connecting to Exchange, Zammad will ask " -"you to turn it off temporarily." +"These conditions are based on form values and match if an appropriate " +"selection is made (e.g. choosing another group in the ticket without " +"saving). This applies for drafts (active selection) and currently saved " +"values." msgstr "" -#: ../system/integrations/exchange.rst:38 -msgid "" -"Please be aware that **turning off SSL verification is a security risk**. It " -"should only be used temporarily or for testing purposes. If turned off, " -"there is no verification of the certificate, which means that every " -"presented certificate will be accepted." +#: ../system/core-workflows/how-do-they-work.rst:64 +msgid "Saved Conditions" msgstr "" -#: ../system/integrations/exchange.rst:43 +#: ../system/core-workflows/how-do-they-work.rst:53 msgid "" -"After pressing Continue, Zammad will check if the configuration is okay. You " -"can then enable Exchange and start your first sync. The sync will then run " -"hourly - if you need to change mappings or the address book(s), you can " -"change the configuration at any time." +"These conditions only match if the selected values are stored in the " +"database. It ignores the current value or selection of the field, as long as " +"the changes are not saved (e.g. performing field operations for an existing " +"ticket, which is viewed/opened by an agent)." msgstr "" -#: ../system/integrations/exchange.rst:50 +#: ../system/core-workflows/how-do-they-work.rst:60 msgid "" -"After the sync has finished, you can find the new Exchange contacts under " -"\"Users\". Zammad integrates them just as normal users." +"Keep in mind that the value has to be available in the situation where you " +"need it. Otherwise the condition won't match." msgstr "" -#: ../system/integrations/exchange.rst:55 +#: ../system/core-workflows/how-do-they-work.rst:63 msgid "" -"In some cases you might see unique IDs as \"Login\" instead of the email " -"address. This is normal and doesn't affect the login or email mapping for " -"that entry." +"Example: you can't perform any actions with *saved condition* on a ticket in " +"creation, because there are no saved values at that time." msgstr "" -#: ../system/integrations/github.rst:4 +#: ../system/core-workflows/how-do-they-work.rst:66 msgid "" -"Use GitHub integration to track GitHub issues directly within Zammad " -"tickets. Add issue hyperlinks and get a live summary of metadata like status " -"(open/closed), assignee, labels, and more." +"You can find a description of the condition operators for core workflows :" +"doc:`here `." msgstr "" -#: ../system/integrations/github.rst:8 -msgid "Please note that our GitHub integration does not support pull requests." +#: ../system/core-workflows/how-do-they-work.rst:72 +msgid "" +"Which actions should we run on the relevant fields? The possible actions " +"depend on the object type. However, usually you can at least change the " +"visibility and whether the field is mandatory." msgstr "" -#: ../system/integrations/github.rst:None -msgid "Integration page for GitHub" +#: ../system/core-workflows/how-do-they-work.rst:76 +msgid "Be aware that actions are not available for **related** context." msgstr "" -#: ../system/integrations/github.rst:18 +#: ../system/core-workflows/how-do-they-work.rst:78 msgid "" -"In your GitHub settings, create a new API token under **Developer settings > " -"Personal access tokens > Generate new token**. Leave the **Scopes** section " -"empty." +"**Example:** Let's assume you are working in the ticket context. While you " +"can have customer *conditions*, you *can't adjust* objects with actions in " +"that scope. That's because this wouldn't have any impact on the ticket " +"dialog. Of course all ticket attributes (state, owner, ...) are available." msgstr "" -#: ../system/integrations/github.rst:0 ../system/integrations/gitlab.rst:0 -msgid "Screencast showing how to create a new API token" +#: ../system/core-workflows/how-do-they-work.rst:84 +msgid "" +"Please also have a look at our :doc:`limitations` to be safe from surprises." msgstr "" -#: ../system/integrations/github.rst:27 -msgid "Create a new API key with no scopes/privileges." +#: ../system/core-workflows/how-do-they-work.rst:88 +msgid "Available Operators" msgstr "" -#: ../system/integrations/github.rst:29 -msgid "🔒 **Will this work for private repos?**" +#: ../system/core-workflows/how-do-they-work.rst:90 +msgid "The availability of operators depends on the object type and scope." msgstr "" -#: ../system/integrations/github.rst:31 +#: ../system/core-workflows/how-do-they-work.rst:94 msgid "" -"No. To link private repo issues, **use the** ``repo`` **scope instead**. " -"Bear in mind that the resulting token will have `lots of permissions that it " -"doesn't actually need `_, which presents a security risk if your token ever falls into " -"the wrong hands." +"Please note that actions may or may not restrict API based access to " +"attributes. We're displaying the following icons for your overview to " +"understand these limits better:" msgstr "" -#: ../system/integrations/github.rst:37 -msgid "" -"Unfortunately, because of how GitHub's OAuth token scopes are set up, this " -"is the only way to link issues on private repos." +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|api| This icon indicates the action affects the API." msgstr "" -#: ../system/integrations/github.rst:40 -msgid "Enter your new API token in Zammad and enable GitHub integration." +#: ../system/core-workflows/how-do-they-work.rst:163 +msgid "api" msgstr "" -#: ../system/integrations/github.rst:0 -msgid "Screencast showing how to configure Zammad's GitHub integration" +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|ui| This icon indicates the action only affects the web interface." msgstr "" -#: ../system/integrations/github.rst:47 -msgid "" -"Use the default API endpoint (``https://api.github.com/graphql``) unless " -"you're using GitHub Enterprise Server." +#: ../system/core-workflows/how-do-they-work.rst:167 +msgid "ui" msgstr "" -#: ../system/integrations/github.rst:50 -msgid "" -"Once completed, a new GitHub issues tab will appear in the ticket pane. 🎉" +#: ../system/core-workflows/how-do-they-work.rst:102 +msgid "show |ui|" msgstr "" -#: ../system/integrations/github.rst:59 ../system/integrations/gitlab.rst:52 -msgid "Token verification is taking a long time" +#: ../system/core-workflows/how-do-they-work.rst:102 +msgid "Display the chosen field. Allows setting of values." msgstr "" -#: ../system/integrations/github.rst:56 ../system/integrations/gitlab.rst:49 +#: ../system/core-workflows/how-do-they-work.rst:109 +msgid "hide |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:105 msgid "" -"Slight delays are normal (<2 min.), especially for systems under heavy load." +"Hide the chosen field. However, it technically still allows setting the " +"field." msgstr "" -#: ../system/integrations/github.rst:58 +#: ../system/core-workflows/how-do-they-work.rst:108 msgid "" -"Self-hosted administrators, please check your network settings to ensure " -"that your Zammad server can reach ``api.github.com``." +"Please note that the field is **not** gone and still contains an existing " +"value (if set)! Consider *remove* instead, if you want this field to be gone." msgstr "" -#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 -msgid "I reloaded the page and now the API token is gone" +#: ../system/core-workflows/how-do-they-work.rst:112 +msgid "remove |ui|" msgstr "" -#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 -msgid "" -"This may indicate that Zammad is still verifying your API token. Try " -"reloading the page again in a couple minutes." +#: ../system/core-workflows/how-do-they-work.rst:112 +msgid "Entirely removes the field. The field value will not be evaluated." msgstr "" -#: ../system/integrations/gitlab.rst:2 -msgid "GitLab" +#: ../system/core-workflows/how-do-they-work.rst:115 +msgid "set mandatory |ui| |api|" msgstr "" -#: ../system/integrations/gitlab.rst:4 -msgid "" -"Use GitLab integration to track GitLab issues directly within Zammad " -"tickets. Add issue hyperlinks and get a live summary of metadata like status " -"(open/closed), assignee, labels, and more." +#: ../system/core-workflows/how-do-they-work.rst:115 +msgid "Sets the field to mandatory." msgstr "" -#: ../system/integrations/gitlab.rst:8 -msgid "" -"Please note that our GitLab integration does not support merge requests." +#: ../system/core-workflows/how-do-they-work.rst:118 +msgid "set optional |ui| |api|" msgstr "" -#: ../system/integrations/gitlab.rst:None -msgid "Integration page for GitLab" +#: ../system/core-workflows/how-do-they-work.rst:118 +msgid "Sets the field to optional." msgstr "" -#: ../system/integrations/gitlab.rst:18 -msgid "" -"In your GitLab preferences, create a new API token under **Access Tokens**." +#: ../system/core-workflows/how-do-they-work.rst:124 +msgid "add option |ui| |api|" msgstr "" -#: ../system/integrations/gitlab.rst:20 -msgid "Under **Select scopes**, choose ``read_api`` only." +#: ../system/core-workflows/how-do-they-work.rst:121 +msgid "Allows adding options to tree selects or selects." msgstr "" -#: ../system/integrations/gitlab.rst:27 -msgid "🔒 **If you wish to link issues on any private repos...**" +#: ../system/core-workflows/how-do-they-work.rst:123 +msgid "" +"You have to use the \"remove option\" before performing this action. It " +"allows you to use *existing* configured values." msgstr "" -#: ../system/integrations/gitlab.rst:29 -msgid "Your API token must belong to an account with access to those repos." +#: ../system/core-workflows/how-do-they-work.rst:128 +msgid "remove option |ui| |api|" msgstr "" -#: ../system/integrations/gitlab.rst:31 -msgid "Enter your new API token in Zammad and enable GitLab integration." +#: ../system/core-workflows/how-do-they-work.rst:127 +msgid "" +"Allows removing options from tree selects or selects. It allows you to use " +"*existing* configured values." msgstr "" -#: ../system/integrations/gitlab.rst:0 -msgid "Screencast showing how to configure Zammad's GitLab integration" +#: ../system/core-workflows/how-do-they-work.rst:134 +msgid "set fixed to |ui| |api|" msgstr "" -#: ../system/integrations/gitlab.rst:40 -msgid "" -"Use the default API endpoint (``https://gitlab.com/api/graphql``) unless " -"you're a self-hosted GitLab user." +#: ../system/core-workflows/how-do-they-work.rst:131 +msgid "Reduces the available options by your selection." msgstr "" -#: ../system/integrations/gitlab.rst:43 +#: ../system/core-workflows/how-do-they-work.rst:133 msgid "" -"Once completed, a new GitLab issues tab will appear in the ticket pane. 🎉" +"This reduces your workflows in terms of *add option* and *remove option*." msgstr "" -#: ../system/integrations/gitlab.rst:51 -msgid "" -"Self-hosted administrators, please check your network settings to ensure " -"that your Zammad server can reach ``gitlab.com``." +#: ../system/core-workflows/how-do-they-work.rst:137 +msgid "fill in |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:2 -msgid "i-doit" +#: ../system/core-workflows/how-do-they-work.rst:137 +msgid "Allows filling in of string and integer fields with your values." msgstr "" -#: ../system/integrations/i-doit.rst:4 -msgid "" -"`i-doit `_ is an open-source **configuration " -"management database** - in other words, a tool for keeping tabs on every " -"single piece of your physical and digital infrastructure, from network " -"equipment to virtual machines on down to the faceplates on your rack shelves " -"and more." +#: ../system/core-workflows/how-do-they-work.rst:141 +msgid "fill in empty |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:10 +#: ../system/core-workflows/how-do-they-work.rst:140 msgid "" -"What's that got to do with Zammad? Well, if you used tickets to track issues " -"with all that hardware, you might start wishing there was a way they could " -"talk to each other." +"Allows filling in of string and integer fields with your values **if the " +"field is empty**." msgstr "" -#: ../system/integrations/i-doit.rst:14 -msgid "Zammad gives you two:" +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "select |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:17 -msgid "1. Add i-doit Links to Zammad Tickets" +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "Select a specific value within a select, tree select or boolean field." msgstr "" -#: ../system/integrations/i-doit.rst:20 ../system/integrations/i-doit.rst:80 -msgid "What Users See" +#: ../system/core-workflows/how-do-they-work.rst:153 +msgid "auto select |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:26 -msgid "i-doit integration in Zammad's ticket pane" +#: ../system/core-workflows/how-do-they-work.rst:147 +msgid "Helps users with tree select and select fields:" msgstr "" -#: ../system/integrations/i-doit.rst:26 +#: ../system/core-workflows/how-do-they-work.rst:149 msgid "" -"The i-doit integration will appear under a new 🖨 tab in the ticket pane." +"If the field has only one option available for selection and no value yet, " +"the value will be automatically set." msgstr "" -#: ../system/integrations/i-doit.rst:28 +#: ../system/core-workflows/how-do-they-work.rst:152 msgid "" -"i-doit integration puts a new tab in Zammad's ticket pane where you can add " -"links to existing i-doit devices for easy reference. (See our :user-docs:" -"`user documentation ` to learn " -"how it works in practice)." +"This option only works if you have one value and doesn't work if there is " +"more than one option available." msgstr "" -#: ../system/integrations/i-doit.rst:36 ../system/integrations/i-doit.rst:93 -msgid "How to Set it Up" +#: ../system/core-workflows/how-do-they-work.rst:157 +msgid "set readonly |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:38 +#: ../system/core-workflows/how-do-they-work.rst:156 msgid "" -"It requires i-doit's `API Add-on `_. Make sure to have it properly set up. Use the following setting:" +"Allows you to display an attribute as read only (which means no changes are " +"possible)." msgstr "" -#: ../system/integrations/i-doit.rst:42 -msgid "Active: ``Yes``" +#: ../system/core-workflows/how-do-they-work.rst:161 +msgid "unset readonly |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:43 -msgid "Enforce authentication by username and password: ``No``" +#: ../system/core-workflows/how-do-they-work.rst:160 +msgid "" +"In case a workflow set the field in question to read only, you can undo this " +"with option above." msgstr "" -#: ../system/integrations/i-doit.rst:45 +#: ../system/core-workflows/how-do-they-work.rst:172 +msgid "Stop after match" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:174 msgid "" -"To set it up, enable the integration in the Zammad admin panel under " -"**System > Integrations > i-doit**:" +"Here you can decide if other workflows are executed after the current one." msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "i-doit settings within the integration pages" +#: ../system/core-workflows/how-do-they-work.rst:176 +msgid "" +"If set to ``no`` (default), further workflows will be executed if they match " +"the condition. In this case, it is possible that your actions from the " +"current workflow can be overwritten by another workflow." msgstr "" -#: ../system/integrations/i-doit.rst:53 -msgid "The root URL of your i-doit installation." +#: ../system/core-workflows/how-do-they-work.rst:180 +msgid "" +"If set to ``yes``, no further worflows will be executed after the current " +"one." msgstr "" -#: ../system/integrations/i-doit.rst:62 -msgid "API token" +#: ../system/core-workflows/how-do-they-work.rst:184 +msgid "Priority" msgstr "" -#: ../system/integrations/i-doit.rst:56 +#: ../system/core-workflows/how-do-they-work.rst:186 msgid "" -"Found in the i-doit admin panel under **Interfaces / external data > JSON-" -"RPC API > Common Settings**." +"You can define the sequence, in which the workflows are executed. The " +"default value is ``500``." msgstr "" -#: ../system/integrations/i-doit.rst:0 -msgid "i-doit administration interface with API configuration" +#: ../system/core-workflows/how-do-they-work.rst:189 +msgid "" +"The workflows are executed in ascending order by their priority. That means " +"lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." msgstr "" -#: ../system/integrations/i-doit.rst:67 -msgid "Client ID" -msgstr "" +#: ../system/core-workflows/learn-by-example.rst:2 +#, fuzzy +msgid "Learn by Example" +msgstr "Przykład" -#: ../system/integrations/i-doit.rst:65 -msgid "A unique name to identify Zammad within i-doit." +#: ../system/core-workflows/learn-by-example.rst:4 +msgid "" +"This page provides some basic examples for Core Workflows. Of course you can " +"build much more complex workflows if needed." msgstr "" -#: ../system/integrations/i-doit.rst:67 -msgid "(Zammad does not require you to enter a value here, but i-doit might!)" +#: ../system/core-workflows/learn-by-example.rst:7 +msgid "" +"To learn about Core Workflows in detail, first go to :doc:`how-do-they-work`." msgstr "" -#: ../system/integrations/i-doit.rst:70 +#: ../system/core-workflows/learn-by-example.rst:10 +#, fuzzy +msgid "Group Based Examples" +msgstr "Przykład" + +#: ../system/core-workflows/learn-by-example.rst:12 msgid "" -"Here you can decide if the certificate of your i-doit system has to be " -"verified or not. In case you are using custom certificates, please have a " -"look at :doc:`how to add them to Zammad `." +"All following workflows have the same base configurations. The workflow may " +"not use them all." msgstr "" -#: ../system/integrations/i-doit.rst:77 -msgid "2. List / Create Zammad Tickets in i-doit" +#: ../system/core-workflows/learn-by-example.rst:15 +#, fuzzy +msgid "Groups:" +msgstr "grupa" + +#: ../system/core-workflows/learn-by-example.rst:20 +msgid "Attributes:" msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "Zammad integration in i-doit's device view" +#: ../system/core-workflows/learn-by-example.rst:22 +msgid "Category (Single tree selection field, not mandatory, agents only)" msgstr "" -#: ../system/integrations/i-doit.rst:86 +#: ../system/core-workflows/learn-by-example.rst:23 msgid "" -"i-doit's ticket system integration gives you a way to see all the tickets " -"for a given device without ever leaving i-doit. (See our :user-docs:`user " -"documentation ` to learn how it " -"works in practice)." +"Approved (Boolean field, not mandatory, not shown, ``false`` as default)" msgstr "" -#: ../system/integrations/i-doit.rst:95 -msgid "" -"Enable this integration in the i-doit admin panel under **Interfaces / " -"external data > Trouble Ticket System (TTS) > Configuration**:" +#: ../system/core-workflows/learn-by-example.rst:24 +msgid "Operating System (Text field, not mandatory, not shown)" msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "i-doit administration interface with TTS configuration" +#: ../system/core-workflows/learn-by-example.rst:25 +msgid "Software used (Single selection field, not mandatory, not shown)" msgstr "" -#: ../system/integrations/i-doit.rst:104 -msgid "TTS-Type" +#: ../system/core-workflows/learn-by-example.rst:68 +msgid "Group specific values and fields" msgstr "" -#: ../system/integrations/i-doit.rst:104 -msgid "``Zammad``" +#: ../system/core-workflows/learn-by-example.rst:28 +msgid "" +"This workflow set depends on the category field. It reduces the available " +"set of values based on the group selected." msgstr "" -#: ../system/integrations/i-doit.rst:115 -msgid "Username / Password" +#: ../system/core-workflows/learn-by-example.rst:33 +msgid "Workflow 2nd Level group" msgstr "" -#: ../system/integrations/i-doit.rst:107 -msgid "Login credentials for a Zammad agent." +#: ../system/core-workflows/learn-by-example.rst:35 +msgid "" +"This reduces the category options to ``2nd Level/*``, ``Internal/*`` and " +"``Others``. It also sets further required fields to mandatory and visible." msgstr "" -#: ../system/integrations/i-doit.rst:109 -msgid "" -"This agent must have **read permission** for all :doc:`groups ` that plan on using the i-doit integration." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for 2nd level" msgstr "" -#: ../system/integrations/i-doit.rst:113 -msgid "" -"You may even wish to create a dedicated agent account just for this " -"integration (otherwise, if the agent ever changes her password, you will " -"have to remember to update it here)." +#: ../system/core-workflows/learn-by-example.rst:43 +msgid "Workflow Support group" msgstr "" -#: ../system/integrations/i-doit.rst:117 -msgid "URL incl. protocol" +#: ../system/core-workflows/learn-by-example.rst:45 +msgid "" +"This reduces the category options to ``Support/*``, ``Internal/*`` and " +"``Others``. It also sets further required fields to visible." msgstr "" -#: ../system/integrations/i-doit.rst:118 -msgid "``https://your.zammad.domain``" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for support" msgstr "" -#: ../system/integrations/index.rst:2 -msgid "Integrations" +#: ../system/core-workflows/learn-by-example.rst:53 +msgid "Workflow Sales group" msgstr "" -#: ../system/integrations/index.rst:4 +#: ../system/core-workflows/learn-by-example.rst:55 msgid "" -"Zammad offers numerous integrations that add rich features to your instance." +"This reduces the category options to ``Sales/*``, ``Internal/*`` and " +"``Others``." msgstr "" -#: ../system/integrations/index.rst:6 -msgid "We're still working on this part of our documentation, stay tight!" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for sales" msgstr "" -#: ../system/integrations/index.rst:10 -msgid "Integrations for Phone Systems" +#: ../system/core-workflows/learn-by-example.rst:68 +#: ../system/integrations/slack.rst:88 +msgid "The Result" msgstr "" -#: ../system/integrations/index.rst:14 +#: ../system/core-workflows/learn-by-example.rst:63 msgid "" -"Your VoIP provider or telephony system is not listed? Possibly your provider " -"supports Zammad by using the generic CTI - if you're unsure ask your " -"provider." +"This is what the agent would experience with the above workflows in place." msgstr "" -#: ../system/integrations/index.rst:18 +#: ../system/core-workflows/learn-by-example.rst:0 msgid "" -"Provider does not support Zammad? Consider creating a `feature request in " -"the Zammad Community `_." -msgstr "" - -#: ../system/integrations/index.rst:31 -msgid "Integrations for Authentication and Customers" +"Workflow shows objects and limits options based on selections on the group" msgstr "" -#: ../system/integrations/index.rst:44 -msgid "Integrations for Monitoring Systems" +#: ../system/core-workflows/learn-by-example.rst:90 +msgid "Approval process" msgstr "" -#: ../system/integrations/index.rst:46 -msgid "This section currently misses the following integrations:" +#: ../system/core-workflows/learn-by-example.rst:71 +msgid "" +"In this case ``approved`` is visible to agents by default. For this " +"workflow, an additional role ``Approval person`` is required (no further " +"permissions)." msgstr "" -#: ../system/integrations/index.rst:48 -msgid "Icinga" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that restricts an approval attribute to specific roles" msgstr "" -#: ../system/integrations/index.rst:49 -msgid "Monit" +#: ../system/core-workflows/learn-by-example.rst:81 +msgid "" +"This workflow may work best in combination with a :doc:`trigger ` but technically, this is not required." msgstr "" -#: ../system/integrations/index.rst:50 -msgid "Nagios" +#: ../system/core-workflows/learn-by-example.rst:84 +msgid "" +"Select fields may be a better approach because they allow more values than " +"just a simple ``true`` or ``false``." msgstr "" -#: ../system/integrations/index.rst:60 -msgid "Integrations for Issue Trackers" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "" +"Workflow fixes possible values of \"Approved ?\" to a specific selection " +"depending on the users role" msgstr "" -#: ../system/integrations/index.rst:70 -msgid "Other Integrations" +#: ../system/core-workflows/learn-by-example.rst:103 +msgid "State dependent mandatory fields" msgstr "" -#: ../system/integrations/index.rst:72 +#: ../system/core-workflows/learn-by-example.rst:93 msgid "" -"This section will hold any other integration that can't be grouped up (yet)." -msgstr "" - -#: ../system/integrations/ldap/index.rst:2 -msgid "LDAP / Active Directory" +"This workflow sets ``Category`` to mandatory if the agent wants to set the " +"states ``closed`` or ``pending close`` to enforce categorization." msgstr "" -#: ../system/integrations/ldap/index.rst:4 -msgid "" -"Zammad comes with a powerful LDAP integration that allows you to have a " -"single source of truth. By this you reduce the number of login credentials " -"your user has to remember." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that sets fields to mandatory on specific states" msgstr "" -#: ../system/integrations/ldap/index.rst:10 +#: ../system/core-workflows/learn-by-example.rst:0 msgid "" -"The LDAP source is also a perfect candidate for Zammad's :docs:`Kerberos " -"Single Sign-On ` but also works as addition " -"to other :doc:`/settings/security/third-party`." +"Workflow sets category field to mandatory upon choosing closed or pending " +"close as state" msgstr "" -#: ../system/integrations/ldap/index.rst:None -msgid "Zammands LDAP management page" +#: ../system/core-workflows/learn-by-example.rst:106 +msgid "Manual Ticket Handover Process" msgstr "" -#: ../system/integrations/ldap/index.rst:25 -msgid "📝 :doc:`manage`" +#: ../system/core-workflows/learn-by-example.rst:108 +msgid "This example covers the handover of a ticket from one agent to another:" msgstr "" -#: ../system/integrations/ldap/index.rst:25 -msgid "Add, modify, remove or re-arrange your LDAP-Sources as needed." +#: ../system/core-workflows/learn-by-example.rst:110 +msgid "" +"When the ticket owner is modified, a new text field (\"Handover\") shows up " +"for a comment" msgstr "" -#: ../system/integrations/ldap/index.rst:30 -msgid "Before you continue, please note the following limitations." +#: ../system/core-workflows/learn-by-example.rst:112 +msgid "" +"This may only be visible when the owner is changed, therefore it has to be " +"hidden in general" msgstr "" -#: ../system/integrations/ldap/index.rst:32 -msgid "Mapping / Synchronizing organizations is not possible" +#: ../system/core-workflows/learn-by-example.rst:114 +msgid "The input in this handover text field is mandatory" msgstr "" -#: ../system/integrations/ldap/index.rst:36 +#: ../system/core-workflows/learn-by-example.rst:115 msgid "" -"You may want to consider using domain based assignments to overcome this " -"issue. Learn more on :doc:`/manage/organizations/index`." +"After submitting changes, the value of the handover field must be added as " +"an note to the ticket (via trigger)" msgstr "" -#: ../system/integrations/ldap/index.rst:39 -msgid "" -"Zammad's LDAP sync is one way. Editing user settings or permissions may be " -"overwritten upon the next sync depending on your configuration." +#: ../system/core-workflows/learn-by-example.rst:121 +msgid "Hiding handover field" msgstr "" -#: ../system/integrations/ldap/index.rst:41 -msgid "Nested groups are not supported." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Hiding the handover field in core workflows" msgstr "" -#: ../system/integrations/ldap/index.rst:42 -msgid "Synchronizing user avatars from LDAP is not supported." +#: ../system/core-workflows/learn-by-example.rst:126 +msgid "Showing handover field and setting it to mandatory" msgstr "" -#: ../system/integrations/ldap/index.rst:43 -msgid "Unlike user filters, group filters cannot be changed." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Showing the handover field and set it as mandatory" msgstr "" -#: ../system/integrations/ldap/index.rst:44 -msgid "" -"When a user originates from an LDAP server, Zammad will try to verify the " -"login credentials against LDAP first - if this fails Zammad will check its " -"local database." +#: ../system/core-workflows/learn-by-example.rst:131 +msgid "Trigger writing handover input to a new article" msgstr "" -#: ../system/integrations/ldap/index.rst:50 -msgid "" -"Users can have local passwords even if they're LDAP users! You can learn " -"more about user accounts in general on :doc:`/manage/users/index`." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Write handover content to a new article" msgstr "" -#: ../system/integrations/ldap/index.rst:54 +#: ../system/core-workflows/learn-by-example.rst:133 msgid "" -"When several LDAP sources contain the same user (meaning the same email " -"address), the user in question will be updated with every source configured. " -"*The last LDAP source will win.*" +"As a result, the ticket includes an article of the type note which includes " +"the predefined text and the handover comment." msgstr "" -#: ../system/integrations/ldap/index.rst:58 -msgid "" -"This is subject to change with `Issue 4109 `_ in the future." +#: ../system/core-workflows/limitations.rst:6 +msgid "Core Workflows do not replace Triggers" msgstr "" -#: ../system/integrations/ldap/index.rst:60 +#: ../system/core-workflows/limitations.rst:5 msgid "" -"Synchronization statistics currently affect *all* configured LDAP sources. " -"This also applies for newly added or updated sources." +"Workflows manipulate the behavior of fields. However, they do not set values " +"in fields because of actions." msgstr "" -#: ../system/integrations/ldap/index.rst:63 -msgid "" -"This is subject to change with `Issue 4108 `_ in the future." +#: ../system/core-workflows/limitations.rst:16 +msgid "API calls are only partly affected" msgstr "" -#: ../system/integrations/ldap/index.rst:65 +#: ../system/core-workflows/limitations.rst:9 msgid "" -"Zammad currently has limited fallback server support. You can workaround " -"this by providing several sources - however, ensure to have the exact same " -"configuration on your fallback." +"Some options affect UI only and thus do not restrict responses and calls." msgstr "" -#: ../system/integrations/ldap/index.rst:69 -msgid "" -"This is subject to improve with `Issue 4107 `_ in the future." +#: ../system/core-workflows/limitations.rst:11 +msgid "This affects the following actions:" msgstr "" -#: ../system/integrations/ldap/index.rst:76 -msgid "" -"This section holds all requests Zammad handled for all LDAP sources. These " -"entries can either contain synchronization information or logins " -"(authentication attempts via Zammad's login interface)." +#: ../system/core-workflows/limitations.rst:13 +msgid "select" msgstr "" -#: ../system/integrations/ldap/index.rst:80 -msgid "" -"By clicking on any request, Zammad will provide even more information. The " -"provided information can be useful when something does not work as expected." +#: ../system/core-workflows/limitations.rst:14 +msgid "auto select" msgstr "" -#: ../system/integrations/ldap/index.rst:85 -msgid "" -"Especially a LDAP synchronization can cause many log entries. The web " -"interface will always limit the number of shown entries to the last 50 " -"entries." +#: ../system/core-workflows/limitations.rst:15 +msgid "show" msgstr "" -#: ../system/integrations/ldap/index.rst:None -msgid "" -"Screencast showing LDAP integration log entries and a detail view on\n" -"an entry." +#: ../system/core-workflows/limitations.rst:16 +msgid "hide" msgstr "" -#: ../system/integrations/ldap/manage.rst:2 -msgid "Manage LDAP-Sources" +#: ../system/core-workflows/limitations.rst:25 +msgid "Some fields stay unavailable to customers" msgstr "" -#: ../system/integrations/ldap/manage.rst:6 +#: ../system/core-workflows/limitations.rst:19 msgid "" -"Please keep in mind all current limitations for the LDAP synchronization. " -"This will help to understand scopes of the following operations better." -msgstr "" - -#: ../system/integrations/ldap/manage.rst:65 -msgid "Add new source" +"For technical and security reasons, some default fields (the pale ones you " +"can't edit) stay unavailable for display and usage on customer permissions." msgstr "" -#: ../system/integrations/ldap/manage.rst:10 +#: ../system/core-workflows/limitations.rst:23 msgid "" -"Using the *New Source* button allows you to add new LDAP sources to your " -"installation. You're not limited in the number of sources, however, keep in " -"mind that many sources will also take more time to synchronize." +"If you require your customers to change e.g. priorities, please consider " +"using workarounds via :doc:`/system/objects` and :doc:`/manage/trigger`." msgstr "" -#: ../system/integrations/ldap/manage.rst:14 -msgid "" -"You can choose between different encryption types, namely *SSL* and " -"*STARTTLS* or none of them (\"*No SSL*\"). If you choose *SSL* or " -"*STARTTLS*, Zammad will display an additional *SSL verification* option that " -"allows you to disable the verification, e.g. for self-signed SSL " -"certificates. You can also tell Zammad to use a different port by appending " -"``:`` to your hostname/IP." +#: ../system/core-workflows/limitations.rst:29 +msgid "Ticket title changes not supported in edit mask" msgstr "" -#: ../system/integrations/ldap/manage.rst:0 +#: ../system/core-workflows/limitations.rst:28 msgid "" -"Screenshot of configuring a new LDAP source with SSL encryption and SSL " -"verification" +"It is currently not possible to perform changes of the ticket title in the " +"edit mask (e.g. renaming, set to read-only)." msgstr "" -#: ../system/integrations/ldap/manage.rst:26 -msgid "" -"New Source with SSL transport security enabled and certificate verification" +#: ../system/core-workflows/limitations.rst:37 +msgid "What is out of scope of Core Workflows?" msgstr "" -#: ../system/integrations/ldap/manage.rst:30 +#: ../system/core-workflows/limitations.rst:32 msgid "" -"Using an user filter can be a good idea if you only require a small subset " -"of your LDAP users in Zammad." +"There are some things that would count as workflow but are either done via :" +"doc:`/manage/trigger` or :doc:`/manage/scheduler`." msgstr "" -#: ../system/integrations/ldap/manage.rst:42 -msgid "This especially affects inactive users" +#: ../system/core-workflows/limitations.rst:35 +msgid "Such as (but not limited to):" msgstr "" -#: ../system/integrations/ldap/manage.rst:34 -msgid "" -"As every LDAP behaves differently on which attributes and how they are set, " -"Zammad doesn't care about any flags." +#: ../system/core-workflows/limitations.rst:37 +msgid "up- or downgrade permissions of users" msgstr "" -#: ../system/integrations/ldap/manage.rst:37 -msgid "" -"Users that no longer are returned by your LDAP source will automatically be " -"set to inactive. Zammad assumes that the user was deactivated." +#: ../system/core-workflows/limitations.rst:38 +msgid "affecting article creation or listing" msgstr "" -#: ../system/integrations/ldap/manage.rst:41 -msgid "" -"Users will never be removed automatically! If you want to remove obsolete " -"users, use :doc:`/system/data-privacy`." +#: ../system/data-privacy.rst:2 +msgid "Data Privacy" msgstr "" -#: ../system/integrations/ldap/manage.rst:46 -msgid "Active Directory admins" +#: ../system/data-privacy.rst:4 +msgid "" +"For compliance with GDPR and other data privacy laws, you may wish to " +"**permanently delete users from the system**, along with **all of their " +"associated tickets**." msgstr "" -#: ../system/integrations/ldap/manage.rst:45 +#: ../system/data-privacy.rst:8 msgid "" -"Active Directories are quite specific on how to filter for active users only " -"- please see the `Microsoft documentation `_ for more " -"information." +"You can create manual deletion tasks or even automated deletion tasks for " +"tickets and users based on custom conditions via :doc:`scheduler `!" msgstr "" -#: ../system/integrations/ldap/manage.rst:51 +#: ../system/data-privacy.rst:12 msgid "" -"*Do not* manually write pathes of either LDAP attributes or groups. If " -"Zammad does not display them, it either cannot find them or you have a lot " -"of users that don't have the attributes populated." +"Access to this panel requires ``admin.data_privacy`` permissions (introduced " +"in Zammad 3.5)." msgstr "" -#: ../system/integrations/ldap/manage.rst:55 +#: ../system/data-privacy.rst:15 msgid "" -"Zammad will always only return attributes that are filled - this reduces the " -"returned list of attributes greatly." +"On older systems that have not been updated yet, customers can also be :docs:" +"`deleted via the Zammad console `." msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing how to add a new LDAP source" +#: ../system/data-privacy.rst:22 +msgid "User deletion dialog in the Data Privacy panel" msgstr "" -#: ../system/integrations/ldap/manage.rst:63 +#: ../system/data-privacy.rst:22 msgid "" -"If your LDAP system doesn't allow anonymous bind, Zammad detects it and " -"provides you an editable \"Base DN\" *text* field instead of a prefilled " -"*select* field." +"The user deletion dialog lists some of the tickets that will be removed from " +"the system along with the user." msgstr "" -#: ../system/integrations/ldap/manage.rst:81 -msgid "Review or edit existing source" +#: ../system/data-privacy.rst:27 +msgid "Deleting Users via GUI" msgstr "" -#: ../system/integrations/ldap/manage.rst:68 -msgid "" -"Clicking on a LDAP source will provide a configuration and mapping overview." +#: ../system/data-privacy.rst:29 +msgid "🔥 **All deletions are FINAL!**" msgstr "" -#: ../system/integrations/ldap/manage.rst:70 -msgid "" -"If needed you can then use the *Change* button to update either the name, " -"active state or the whole configuration. If you're changing the whole " -"configuration, the dialogue will be identical to the source creation." +#: ../system/data-privacy.rst:31 +msgid "Once you click “Delete”, the action cannot be canceled or undone." msgstr "" -#: ../system/integrations/ldap/manage.rst:76 +#: ../system/data-privacy.rst:33 msgid "" -"Did your LDAP server change? Different LDAP servers have different " -"structures and default attributes. This causes the LDAP synchronization to " -"likely fail. Consider removing the affected source and re-add it." +"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." msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing the update of the source name." +#: ../system/data-privacy.rst:36 +msgid "**The following records cannot be deleted:**" msgstr "" -#: ../system/integrations/ldap/manage.rst:89 -msgid "Re-arrange LDAP source's order" +#: ../system/data-privacy.rst:38 +msgid "your own account" msgstr "" -#: ../system/integrations/ldap/manage.rst:84 -msgid "" -"You can change the synchronization order for each source at any time. Zammad " -"will synchronize the sources from top to bottom." +#: ../system/data-privacy.rst:39 +msgid "the system's last remaining administrator account" msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "" -"Screencasting showing how to change the source order by using\n" -"drag and drop." +#: ../system/data-privacy.rst:42 +msgid "Step 1: Find a User / Confirm Deletion" msgstr "" -#: ../system/integrations/ldap/manage.rst:101 -msgid "Remove a source" +#: ../system/data-privacy.rst:44 +msgid "There are three ways to access the user deletion dialog:" msgstr "" -#: ../system/integrations/ldap/manage.rst:92 -msgid "" -"If you no longer need the a LDAP source or simply want to start over, you " -"can remove them at any time. This will not remove synchronized users, data " -"synchronized or permissions." +#: ../system/data-privacy.rst:51 +msgid "**from the user's profile**" msgstr "" -#: ../system/integrations/ldap/manage.rst:98 -msgid "" -"Not sure if you'd need the source later on? Set the source to inactive " -"instead of removing it - see *Review or edit existing source* for more." +#: ../system/data-privacy.rst:0 +msgid "Accessing the user deletion dialog in a user profile" msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing how to remove LDAP sources." +#: ../system/data-privacy.rst:51 +msgid "Click **Action > Delete**." msgstr "" -#: ../system/integrations/pgp/index.rst:2 -msgid "PGP" +#: ../system/data-privacy.rst:58 +msgid "**in the “Manage > Users” Admin Panel**" msgstr "" -#: ../system/integrations/pgp/index.rst:7 -msgid "" -"Pretty Good Privacy (PGP) is another method for secure email communication. " -"With PGP, you can exchange **signed** and **encrypted** messages with others." +#: ../system/data-privacy.rst:0 +msgid "Accessing the user deletion dialog under “Users” in the Admin Panel" msgstr "" -#: ../system/integrations/pgp/index.rst:13 -#: ../system/integrations/smime/index.rst:17 -msgid "Signing" +#: ../system/data-privacy.rst:58 +msgid "Use the **⋮ Actions** menu for the target user." msgstr "" -#: ../system/integrations/pgp/index.rst:11 -msgid "is a proof that a message hasn't been manipulated on its way." +#: ../system/data-privacy.rst:66 ../system/data-privacy.rst:104 +msgid "**in the “System > Data Privacy” Admin Panel**" msgstr "" -#: ../system/integrations/pgp/index.rst:13 +#: ../system/data-privacy.rst:0 msgid "" -"In other words, it guarantees message **integrity** and **authenticity**." +"Accessing the user deletion dialog under “Data Privacy” in the Admin Panel" msgstr "" -#: ../system/integrations/pgp/index.rst:19 -#: ../system/integrations/smime/index.rst:22 -msgid "Encryption" +#: ../system/data-privacy.rst:65 +msgid "" +"Use the **New Deletion Task** button. Search for users by name or email " +"address." msgstr "" -#: ../system/integrations/pgp/index.rst:16 -#: ../system/integrations/smime/index.rst:20 -msgid "" -"scrambles a message so that it can only be unscrambled by the intended " -"recipient." +#: ../system/data-privacy.rst:79 +msgid "**Delete organizations**" msgstr "" -#: ../system/integrations/pgp/index.rst:19 +#: ../system/data-privacy.rst:69 msgid "" -"In other words, it guarantees message **privacy** and **data security**." +"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:" msgstr "" -#: ../system/integrations/pgp/index.rst:25 -msgid "Screenshot of ticket creation with encrypt and sign buttons" +#: ../system/data-privacy.rst:0 +msgid "Deleting an organization via the user deletion dialog" msgstr "" -#: ../system/integrations/pgp/index.rst:25 +#: ../system/data-privacy.rst:78 msgid "" -"Once PGP has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " -"appear in the ticket composer." +"If this option does not appear, make sure there are no pending deletion " +"tasks for other customers from this organization." msgstr "" -#: ../system/integrations/pgp/index.rst:28 -msgid "**Sign button not visible?**" +#: ../system/data-privacy.rst:82 +msgid "Step 2: Monitor Deletion Job Status" msgstr "" -#: ../system/integrations/pgp/index.rst:30 +#: ../system/data-privacy.rst:84 msgid "" -"Please note that the signing of emails is based on the outgoing email " -"account. That means you have to choose a group with a sender email account, " -"which has a private key assigned." +"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:" msgstr "" -#: ../system/integrations/pgp/index.rst:35 -msgid "Handling of Keys" +#: ../system/data-privacy.rst:98 +msgid "**in the Activity Stream**" msgstr "" -#: ../system/integrations/pgp/index.rst:36 -msgid "" -"To use the PGP function, you have to enable the integration (PGP) by " -"switching the toggle to *enabled*." +#: ../system/data-privacy.rst:0 +msgid "Activity Stream showing data privacy tasks" msgstr "" -#: ../system/integrations/pgp/index.rst:39 +#: ../system/data-privacy.rst:94 msgid "" -"You can add keys by clicking the *add key* button. The keys can be imported " -"from a file or you can paste the content of the key in the text box." -msgstr "" - -#: ../system/integrations/pgp/index.rst:42 -msgid "**Which keys do I have to import?**" +"For each deleted user, the Activity Stream will be updated twice—once when " +"the task is created, and once when it's complete." msgstr "" -#: ../system/integrations/pgp/index.rst:44 +#: ../system/data-privacy.rst:97 msgid "" -"For **signing** *outgoing* emails, you have to import the private key of " -"your Zammad email account." +"These notifications are only visible to users with ``admin.data_privacy`` " +"permissions." msgstr "" -#: ../system/integrations/pgp/index.rst:47 +#: ../system/data-privacy.rst:0 msgid "" -"For **encrypting** *outgoing* emails, you have to import the public key of " -"the customer's email account." +"The task list within Data Privacy shows removals being in progress and " +"completed." msgstr "" -#: ../system/integrations/pgp/index.rst:50 -msgid "" -"For **verifying the signature** of signed *incoming* emails, you have to " -"import the public key of the customer." +#: ../system/data-privacy.rst:107 +msgid "Frequently Asked Questions" msgstr "" -#: ../system/integrations/pgp/index.rst:53 -msgid "" -"For **decrypting** of encrypted *incoming* emails, you have to import the " -"private key of your Zammad email account." +#: ../system/data-privacy.rst:121 +msgid "What happens if I receive an email from a deleted customer?" msgstr "" -#: ../system/integrations/pgp/index.rst:57 -msgid "Import Keys From a File" +#: ../system/data-privacy.rst:110 +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/integrations/pgp/index.rst:58 -msgid "You can import keys from a file in the section **Upload key**:" +#: ../system/data-privacy.rst:115 +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**." msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of adding a key via file" +#: ../system/data-privacy.rst:130 +msgid "What about user information stored in internal notes or other messages?" msgstr "" -#: ../system/integrations/pgp/index.rst:64 +#: ../system/data-privacy.rst:124 msgid "" -"**Supported file formats:** ASCII-armor as well as binary GPG format " -"(basically any GPG supported key format) is supported here." -msgstr "" - -#: ../system/integrations/pgp/index.rst:68 -msgid "Import Keys by Pasting the Content" +"The deletion process removes **user accounts and associated tickets only**." msgstr "" -#: ../system/integrations/pgp/index.rst:69 -msgid "You can also paste the key's content in the section **paste key**:" +#: ../system/data-privacy.rst:126 +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." msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of adding a key via pasting" +#: ../system/data-privacy.rst:137 +msgid "I deleted an user and can still see a message they sent!" msgstr "" -#: ../system/integrations/pgp/index.rst:75 +#: ../system/data-privacy.rst:133 msgid "" -"**Supported format:** Please note that only ASCII-armor is supported here." +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:78 -msgid "Deleting Keys" +#: ../system/data-privacy.rst:141 +msgid "I removed a customer, now my reporting is off!" msgstr "" -#: ../system/integrations/pgp/index.rst:79 +#: ../system/data-privacy.rst:140 msgid "" -"If you want to delete a specific key, you can do it by clicking on the menu " -"in the *actions* column and select **delete**:" -msgstr "" - -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of deleting a key" +"When removing users and their tickets, all references are removed. This also " +"affects e.g. Reporting - these information are lost." msgstr "" -#: ../system/integrations/pgp/index.rst:88 -msgid "Downloading Keys" +#: ../system/data-privacy.rst:145 +msgid "How long does Zammad store created tasks?" msgstr "" -#: ../system/integrations/pgp/index.rst:89 +#: ../system/data-privacy.rst:144 msgid "" -"If you want to download your keys, you can do this as well via corresponding " -"action buttons. Depending on the key, you can choose wether you want to " -"download the private or the public key." +"Please see the on-premise data section of the :docs:`data privacy ` chapter." msgstr "" -#: ../system/integrations/pgp/index.rst:95 -#: ../system/integrations/smime/manage-certificates.rst:76 -msgid "Default Behavior" +#: ../system/data-privacy.rst:150 +msgid "What about re-assigned tickets? I want to delete them, too." msgstr "" -#: ../system/integrations/pgp/index.rst:96 +#: ../system/data-privacy.rst:148 msgid "" -"Here you can adjust on per group basis, if *sign* and *encryption* is on or " -"off by default. Please be aware, that agents can always override the setting " -"for each individual article." +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Adjusting default behavior on per group basis" +#: ../system/data-privacy.rst:154 +msgid "Why are there so many deletion task entries, I didn't create them!" msgstr "" -#: ../system/integrations/pgp/index.rst:107 +#: ../system/data-privacy.rst:153 msgid "" -"Here you can see the last actions regarding signing and encryption and if " -"they were successful." +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:117 -msgid "**Sign button is not visible, but keys are imported.**" +#: ../system/integrations/checkmk/admin-panel-reference.rst:2 +msgid "Admin Panel Reference" msgstr "" -#: ../system/integrations/pgp/index.rst:115 -msgid "Did you choose a group in the ticket?" +#: ../system/integrations/checkmk/admin-panel-reference.rst:None +msgid "Screenshot of Checkmk settings overview" msgstr "" -#: ../system/integrations/pgp/index.rst:116 +#: ../system/integrations/checkmk/admin-panel-reference.rst:12 msgid "" -"Did you import a private key for the email adress, which is used for " -"outgoing emails in the group?" +"Which :doc:`group ` should Checkmk tickets be assigned " +"to as a default (*i.e.,* when none is specified)?" msgstr "" -#: ../system/integrations/pgp/index.rst:122 -msgid "**How to obtain keys?**" +#: ../system/integrations/checkmk/admin-panel-reference.rst:15 +msgid "(Applies to :ref:`API alerts ` only.)" msgstr "" -#: ../system/integrations/pgp/index.rst:120 +#: ../system/integrations/checkmk/admin-panel-reference.rst:21 +msgid "Auto close" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:18 msgid "" -"You can create them yourself! There are some good tutorials on the web on " -"how to create them. Providing keys to Zammad is a prerequisite to use the " -"PGP feature." +"Should Zammad automatically close tickets if a service has recovered on its " +"own?" msgstr "" -#: ../system/integrations/pgp/index.rst:127 -msgid "**It says a passphrase is needed, but I haven't got one.**" +#: ../system/integrations/checkmk/admin-panel-reference.rst:21 +msgid "(Agents will receive notifications for such closures as appropriate.)" msgstr "" -#: ../system/integrations/pgp/index.rst:125 -msgid "" -"If the key is secured with a passphrase, you have to provide it for the " -"import in Zammad. It is possible that keys may have an empty passphrase. " -"However, this is *not* recommended." +#: ../system/integrations/checkmk/admin-panel-reference.rst:30 +msgid "Auto-close state" msgstr "" -#: ../system/integrations/pgp/index.rst:132 -msgid "**How do my customers get my new key?**" +#: ../system/integrations/checkmk/admin-panel-reference.rst:24 +msgid "What ticket state should be applied when “auto-closing” a ticket?" msgstr "" -#: ../system/integrations/pgp/index.rst:130 +#: ../system/integrations/checkmk/admin-panel-reference.rst:26 msgid "" -"You have to provide your **public** key in advance. Your customer also has " -"to configure PGP in their email workflow and import your public key. The " -"other way round, you have to get the public key of your customer and have to " -"import it to Zammad." +"You can choose from the seven built-in ticket states. If these states aren't " +"enough for you, you can :ref:`define a new ticket state ` for this purpose as well. This can be useful for tracking " +"tickets with :doc:`reports `, for example." msgstr "" -#: ../system/integrations/slack.rst:2 -msgid "Slack" +#: ../system/integrations/checkmk/admin-panel-reference.rst:35 +#: ../system/integrations/cti/includes/recent-logs.include.rst:2 +#: ../system/integrations/ldap/index.rst:74 +#: ../system/integrations/pgp/index.rst:106 +msgid "Recent Logs" msgstr "" -#: ../system/integrations/slack.rst:4 -msgid "**⚠️ Deprecation warning ⚠️**" +#: ../system/integrations/checkmk/admin-panel-reference.rst:None +msgid "Screenshot of Checkmk \"Recent Logs\" section" msgstr "" -#: ../system/integrations/slack.rst:6 +#: ../system/integrations/checkmk/admin-panel-reference.rst:41 msgid "" -"Zammad 7 will no longer support this dedicated Slack integration. It is " -"recommended to switch to :doc:`pre-defined webhooks ` instead. Existing Slack integrations should " -"be migrated manually before this feature is dropped." +"If you're having trouble getting Zammad and Checkmk to play nicely together, " +"this section can help you troubleshoot." msgstr "" -#: ../system/integrations/slack.rst:14 +#: ../system/integrations/checkmk/admin-panel-reference.rst:44 msgid "" -"In order to use this feature, please add a new Slack app to your Workspace. " -"The App you need is called ``Incoming WebHooks`` ." +"It contains a record of the fifty most recent transactions that Zammad knows " +"about, including each one's request/response details and return status." msgstr "" -#: ../system/integrations/slack.rst:18 -msgid "Why Do I Need This Feature?" +#: ../system/integrations/checkmk/api-reference.rst:2 +msgid "API Reference" msgstr "" -#: ../system/integrations/slack.rst:20 +#: ../system/integrations/checkmk/api-reference.rst:4 msgid "" -"If you're already using Slack for your team communication, you'll love this " -"feature! Our Slack integration can push ticket notifications about the last " -"ticket article based on the following events:" +"For most users, :ref:`the sample scripts from the Setup Guide ` will do the job just fine. But if you want more fine-grained control" +"—for instance, to create high- and low-priority tickets for different types " +"of system events—then you'll have to customize the data those scripts send " +"to Zammad." msgstr "" -#: ../system/integrations/slack.rst:24 -msgid "on Ticket creation" +#: ../system/integrations/checkmk/api-reference.rst:15 +msgid "" +"This custom script will automatically set all tickets it creates to **high " +"priority** and **assign them to charlie@chrispresso.com**." msgstr "" -#: ../system/integrations/slack.rst:25 -msgid "on Ticket updates" +#: ../system/integrations/checkmk/api-reference.rst:32 +msgid "How Does it Work?" msgstr "" -#: ../system/integrations/slack.rst:26 -msgid "on reached reminders" +#: ../system/integrations/checkmk/api-reference.rst:34 +msgid "" +"There are two kinds of data you can pass to the API, both in the form of key-" +"value pairs:" msgstr "" -#: ../system/integrations/slack.rst:27 -msgid "a Ticket has escalated" +#: ../system/integrations/checkmk/api-reference.rst:44 +msgid "Checkmk parameters" msgstr "" -#: ../system/integrations/slack.rst:28 -msgid "a Ticket is going to escalate" +#: ../system/integrations/checkmk/api-reference.rst:38 +msgid "" +"are required, and make up the **contents** of the resulting tickets/" +"articles. They also determine whether an event creates a new ticket or " +"updates/closes an existing one." msgstr "" -#: ../system/integrations/slack.rst:30 +#: ../system/integrations/checkmk/api-reference.rst:42 msgid "" -"Zammad will provide the Ticket title, a direct link to the Ticket, the event " -"type (creation, updated, escalation), the customer, time and the last " -"article that has triggered the notification." +"These are the only values used in the sample scripts. **Use them as-is**; " +"technically, they can be customized, but it's hard to imagine a good reason " +"for it." msgstr "" -#: ../system/integrations/slack.rst:34 -msgid "" -"This will give you further options, as you can see e.g. escalating tickets " -"that are assigned to an agent that's e.g. absent. You can interact faster, " -"as you might see problems earlier (or even before the problem gets one)." +#: ../system/integrations/checkmk/api-reference.rst:52 +msgid "Ticket attributes" msgstr "" -#: ../system/integrations/slack.rst:38 +#: ../system/integrations/checkmk/api-reference.rst:47 msgid "" -"If needed and wanted, you can even discuss directly about the topic before " -"sending an answer to the customer. Another possible use case would be a " -"agent monitoring new agents and their answers to tickets." +"are optional, and can be used to **adjust settings** on newly created " +"tickets (*e.g.,* set the owner, group, priority, or state)." msgstr "" -#: ../system/integrations/slack.rst:44 -msgid "Configure the Integration" +#: ../system/integrations/checkmk/api-reference.rst:50 +msgid "" +"If you want to customize your Checkmk alert script, do it with these. Simply " +"add an extra “form” option for each one (``-F \"key=value\"``) to your " +"script's ``curl`` command line, as in the example above." msgstr "" -#: ../system/integrations/slack.rst:46 -msgid "" -"First of all, please go to your slack workspace - go to administration => " -"Manage Apps. If you don't have an app yet, you can simply add a new one - " -"just search for ``Incoming WebHooks`` and customize the app to your needs." +#: ../system/integrations/checkmk/api-reference.rst:54 +msgid "💡 **It's just an API endpoint!**" msgstr "" -#: ../system/integrations/slack.rst:50 +#: ../system/integrations/checkmk/api-reference.rst:56 msgid "" -"Choose (or create) the channel Zammad should post it's information to and " -"press on \"Add Incoming WebHooks integration\". If you're ready, copy the " -"provided WebHook URL and go to your Zammad installation." +"When using Checkmk integration, messages need to be formatted in a certain " +"way, but that *doesn't mean the messages actually have to come from Checkmk*." msgstr "" -#: ../system/integrations/slack.rst:56 +#: ../system/integrations/checkmk/api-reference.rst:59 msgid "" -"You need administrative rights on the Slack Workspace. The link to the app " -"directory is normally ``https://[workspace-name].slack.com/apps`` ." +"If you use another monitoring tool that's not officially supported by " +"Zammad, there's probably a way to make it work with your Checkmk callback " +"URL." msgstr "" -#: ../system/integrations/slack.rst:63 -msgid "" -"To configure the slack integration, log in to Zammad and go to Integrations " -"(System) => Slack in the admin panel." +#: ../system/integrations/checkmk/api-reference.rst:63 +msgid "Checkmk Parameters" msgstr "" -#: ../system/integrations/slack.rst:66 +#: ../system/integrations/checkmk/api-reference.rst:65 msgid "" -"Here you can choose on what evens Zammad should post information about a " -"ticket to your Slack channel. Next you need to device what groups shall be " -"affected by this, as anybody with access to that specific Slack channel can " -"read at least parts of the ticket this might be a privacy issue, if you " -"select the wrong groups. The username is simply the name that Zammad uses as " -"display name inside the Slack chat. The channel defines the Slack channel " -"the information is being posted in. As last option, you can set a custom " -"icon for posting to slack." +"When a notification is received, Zammad creates a new article containing the " +"details of the event that triggered it:" msgstr "" -#: ../system/integrations/slack.rst:74 -msgid "" -"When you're ready, just hit \"Submit\" and enable the integration. Zammad " -"will now post new ticket information based on the trigger you chose. Below " -"the options you have the recent log that shows the latest requests to Slack " -"for debugging if needed." +#: ../system/integrations/checkmk/api-reference.rst:None +msgid "Checkmk article body" msgstr "" -#: ../system/integrations/slack.rst:81 +#: ../system/integrations/checkmk/api-reference.rst:72 msgid "" -"If you leave the Icon URL empty, Zammad will use the Zammad logo instead. " -"The icon should be a square PNG file." +"These details come from the fields listed below, which correspond to " +"parameters provided by Checkmk (``$NOTIFY_*``)." msgstr "" -#: ../system/integrations/slack.rst:90 -msgid "" -"The following figure shows how it will look if you choose to receive updates " -"on created and updated tickets. On every post Zammad sends to the Slack " -"channel, you can create new threads to discuss about the new article." +#: ../system/integrations/checkmk/api-reference.rst:75 +msgid "**Required fields are marked with an asterisk (\\*).**" msgstr "" -#: ../system/integrations/slack.rst:96 -msgid "" -"If you just want to keep track of soon escalating or already escalated " -"tickets, it will look the the following figure. Zammad changes the color in " -"front of the post so you can easily see the state of the ticket." +#: ../system/integrations/checkmk/api-reference.rst:79 +msgid "event_id\\*" msgstr "" -#: ../system/integrations/slack.rst:102 +#: ../system/integrations/checkmk/api-reference.rst:78 msgid "" -"If you change the state, Zammad will also put information on what state the " -"ticket gets and (if pending state) the date until it pends. You'll also " -"recognize the color codes in front of posts on slack, as they are exact the " -"same the ticket state colors you'll see in Zammad!" +"A unique ID for the system event. (``$NOTIFY_SERVICEPROBLEMID`` / " +"``$NOTIFY_HOSTPROBLEMID``)" msgstr "" -#: ../system/integrations/smime/index.rst:2 -msgid "S/MIME" +#: ../system/integrations/checkmk/api-reference.rst:86 +msgid "host\\*" msgstr "" -#: ../system/integrations/smime/index.rst:11 +#: ../system/integrations/checkmk/api-reference.rst:82 msgid "" -"S/MIME is the most widely-supported method for secure email communication. " -"With S/MIME, you can exchange **signed** and **encrypted** messages with " -"others." +"The hostname of the system that the event originated from. " +"(``$NOTIFY_HOSTNAME``)" msgstr "" -#: ../system/integrations/smime/index.rst:15 +#: ../system/integrations/checkmk/api-reference.rst:85 msgid "" -"is proof that a message hasn't been tampered with or sent by an impersonator." +"Used to determine if a new event belongs to an existing ticket. Also used in " +"the subject line of the resulting article (“ is ”)." msgstr "" -#: ../system/integrations/smime/index.rst:17 -msgid "" -"In other words, it guarantees a message's **integrity** and **authenticity**." +#: ../system/integrations/checkmk/api-reference.rst:96 +msgid "service" msgstr "" -#: ../system/integrations/smime/index.rst:22 -msgid "In other words, it guarantees **privacy** and **data security**." +#: ../system/integrations/checkmk/api-reference.rst:89 +msgid "" +"The name of the service that the event originated from. " +"(``$NOTIFY_SERVICEDESC``)" msgstr "" -#: ../system/integrations/smime/index.rst:28 -msgid "Screencast demo of S/MIME features for both new tickets and replies" +#: ../system/integrations/checkmk/api-reference.rst:92 +msgid "Used to determine if a new event belongs to an existing ticket." msgstr "" -#: ../system/integrations/smime/index.rst:28 -msgid "" -"Once S/MIME has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " -"appear in the ticket composer." +#: ../system/integrations/checkmk/api-reference.rst:94 +#: ../system/integrations/checkmk/api-reference.rst:110 +msgid "Displayed as ``-`` when omitted." msgstr "" -#: ../system/integrations/smime/index.rst:32 -msgid ":doc:`🔪 Prerequisites `" +#: ../system/integrations/checkmk/api-reference.rst:104 +msgid "state\\*" msgstr "" -#: ../system/integrations/smime/index.rst:31 +#: ../system/integrations/checkmk/api-reference.rst:99 msgid "" -"New to S/MIME? This section helps you to find certificate providers and " -"points out Limitations." +"The current state of the service or host in question. " +"(``$NOTIFY_SERVICESTATE`` / ``$NOTIFY_HOSTSTATE``)" msgstr "" -#: ../system/integrations/smime/index.rst:35 -msgid ":doc:`📝 Manage Certificates `" +#: ../system/integrations/checkmk/api-reference.rst:102 +msgid "" +"Used to detect when a ticket should be auto-closed (*i.e.,* on ``OK``/" +"``UP``). Also used in the subject line of the resulting article (“ is " +"”)." msgstr "" -#: ../system/integrations/smime/index.rst:35 -msgid "Add and download certificates; configure group default behaviors." +#: ../system/integrations/checkmk/api-reference.rst:110 +msgid "text" msgstr "" -#: ../system/integrations/smime/index.rst:38 -msgid ":doc:`😦 Troubleshooting `" +#: ../system/integrations/checkmk/api-reference.rst:107 +msgid "" +"The output of the process that triggered the event. " +"(``$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" msgstr "" -#: ../system/integrations/smime/index.rst:38 -msgid "Took a wrong turn? About recent logs and common issues." +#: ../system/integrations/checkmk/api-reference.rst:121 +msgid "" +"The Object Manager attribute panel displays built-in and custom\n" +"attribute names." msgstr "" -#: ../system/integrations/smime/index.rst:43 -msgid "" -"For more details on how S/MIME integration works on the agent side, see the :" -"user-docs:`user docs `." +#: ../system/integrations/checkmk/api-reference.rst:121 +msgid "Find a complete list of ticket attributes in the Object Manager." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:2 -msgid "Manage Certificates" +#: ../system/integrations/checkmk/api-reference.rst:123 +msgid "" +"Ticket attributes are entirely optional, and can be used to customize the " +"tickets that Checkmk creates. (Note that these attributes will be ignored if " +"a new event belongs to an existing ticket.)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:4 +#: ../system/integrations/checkmk/api-reference.rst:128 msgid "" -"S/MIME is **disabled by default**. Enable it to start adding certificates." +"Why would you want to do this? Maybe you have only one IT guy, and all " +"system monitoring issues should be automatically assigned to him. Or, maybe " +"you're creating multiple notification rules so that database outages take " +"higher priority than disk space warnings." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:10 -msgid "Dialogue to add new certificates or private keys" +#: ../system/integrations/checkmk/api-reference.rst:135 +msgid "In most cases, you'll probably want to set one of the following:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:10 +#: ../system/integrations/checkmk/api-reference.rst:137 +msgid "group" +msgstr "grupa" + +#: ../system/integrations/checkmk/api-reference.rst:139 +msgid "state" +msgstr "status" + +#: ../system/integrations/checkmk/api-reference.rst:140 +msgid "priority" +msgstr "priorytet" + +#: ../system/integrations/checkmk/api-reference.rst:142 msgid "" -"Manage certificates in the Admin Panel under **System > Integrations > S/" -"MIME**. Certificates may be pasted in as plain text or uploaded from a file." +"but in practice, you can set almost any attribute, including :doc:`custom " +"ones you created through the Object Manager `." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:14 -msgid "Add Certificate Data" +#: ../system/integrations/checkmk/api-reference.rst:145 +msgid "Please note that the following attributes are **not customizable**:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:36 -msgid "Add Certificate" +#: ../system/integrations/checkmk/api-reference.rst:147 +msgid "title" +msgstr "tytuł" + +#: ../system/integrations/checkmk/api-reference.rst:148 +msgid "id" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:17 -msgid "" -"Import public-key certificates for both your own organization and your " -"contacts." +#: ../system/integrations/checkmk/api-reference.rst:149 +msgid "ticket number" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:19 -msgid "" -"You can also add a bunch of certificates in one go by providing a single " -"file with all relevant certificates." +#: ../system/integrations/checkmk/api-reference.rst:151 +msgid "created_by_id" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:22 -msgid "🕵️ **ALWAYS verify certificates in-person or over the phone!**" +#: ../system/integrations/checkmk/api-reference.rst:152 +msgid "updated_by_id" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:24 -msgid "" -"The whole point of signatures is to alert you when someone is trying to " -"pretend to be someone they're not. Never accept a certificate from someone " -"online without verifying it first." +#: ../system/integrations/checkmk/api-reference.rst:155 +msgid "Which Values Can Be Set?" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:28 -msgid "📇 **What about trusted certificate authorities?**" +#: ../system/integrations/checkmk/api-reference.rst:157 +msgid "😵 **Invalid values → unpredictable behavior**" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:30 +#: ../system/integrations/checkmk/api-reference.rst:159 msgid "" -"In some cases (e.g. when dealing with large enterprises), you may be given a " -"certificate for an entire CA, rather than a single contact. Add it here to " -"trust *all* certificates issued by that CA." +"If you provide a value that Zammad doesn't understand (*e.g.,* ``-F " +"\"priority=high\"``), it's not always clear what will happen. In some cases, " +"a ticket will be created with the default values instead - but in others, it " +"may not be created at all!" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:35 -msgid "" -"Commercial CAs can usually be verified online. Zammad does not include a " -"list of built-in, trusted CAs." +#: ../system/integrations/checkmk/api-reference.rst:164 +msgid "So what values does Zammad understand, then? Well, it depends..." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:57 -msgid "Add Private Key" +#: ../system/integrations/checkmk/api-reference.rst:168 +msgid "Use an email address or username:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:39 -msgid "" -"Once you've added a public-key certificate, you can import its matching " -"private key." +#: ../system/integrations/checkmk/api-reference.rst:190 +msgid "group & priority" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:42 -msgid "" -"Private keys are for **your own organization only**; never ask your contacts " -"for their private keys." +#: ../system/integrations/checkmk/api-reference.rst:175 +msgid "Refer to the dropdown menus in the ticket pane:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:0 -msgid "" -"S/MIME integration showing configured certificates and possible issues with " -"Logging" +#: ../system/integrations/checkmk/api-reference.rst:0 +msgid "See possible values for certain attributes in the ticket pane." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:50 +#: ../system/integrations/checkmk/api-reference.rst:187 +msgid "🙅 **Ticket state CANNOT be set this way!**" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:189 msgid "" -"A note is displayed on certificates with a matching private key (see line 2)." +"Why? Because ``-F \"state=...\"`` is already used :ref:`as a Checkmk " +"parameter `." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:52 -msgid "📤 **Certificates and private keys must be uploaded separately.**" +#: ../system/integrations/checkmk/api-reference.rst:222 +msgid "Everything Else" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:54 +#: ../system/integrations/checkmk/api-reference.rst:193 msgid "" -"If your certificate and private key are bundled together in the same file or " -"PEM block, import it twice (once using each button)." +"To set any other attributes, it helps to know your way around the :docs:" +"`rails console `. Valid values are those that you can " +"set with a string:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:57 -msgid "Please note that bulk imports of private keys are not possible." +#: ../system/integrations/checkmk/api-reference.rst:218 +msgid "These values can then be passed directly to the API:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:60 -msgid "Download Certificate Data" +#: ../system/integrations/checkmk/index.rst:16 +msgid "How does it work?" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:62 -msgid "" -"You can download the earlier provided certificates and private keys at any " -"time from your Zammad instance." +#: ../system/integrations/checkmk/index.rst:2 +msgid "Checkmk" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:65 +#: ../system/integrations/checkmk/index.rst:4 msgid "" -"Please note that passphrase-protected private keys stay protected and when " -"you download them, you have to know the passphrase to use them after " -"downloading." +"`Checkmk `_ is a powerful IT monitoring tool that can " +"send real-time status alerts to Zammad via email or REST API. Set these " +"alerts up in Checkmk, and Zammad will automatically create, update, and " +"close tickets based on the health of your system:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:73 -msgid "Dialogue to download certificates or private keys" +#: ../system/integrations/checkmk/index.rst:14 +msgid "Screenshot of ticket created by Checkmk notifications" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:73 -msgid "Download stored certificates and their keys" +#: ../system/integrations/checkmk/index.rst:14 +msgid "Multiple alerts, same ticket." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:78 -msgid "" -"The ticket composer will set all outgoing messages to **signed and " -"encrypted** by default (assuming the required certificates exist)." +#: ../system/integrations/checkmk/setup-guide.rst:2 +msgid "Setup Guide" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:82 -msgid "These defaults can be modified on a per-group basis:" +#: ../system/integrations/checkmk/setup-guide.rst:4 +msgid "" +"Whenever the Checkmk integration is enabled, Zammad listens for messages on " +"its API and over email. As long as those messages follow the required " +"format, Zammad will create new tickets (or find and update existing ones) " +"based on the message contents." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:None -msgid "Zammad allowing to choose the default behavior on per group basis" +#: ../system/integrations/checkmk/setup-guide.rst:10 +msgid "" +"That means that “setting up Checkmk integration” is simply a matter of " +"**adding configuration to your Checkmk site**: telling it when to send these " +"messages and what to say. To do that, you'll need to create a new " +"**notification rule** (see `Checkmk's official docs `_ for help with that)." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:89 +#: ../system/integrations/checkmk/setup-guide.rst:17 msgid "" -"Of course, agents can always manually change these settings on each email " -"they send out." +"As part of this new rule, you'll have to choose a **notification method** " +"(*i.e.,* a script to execute whenever the rule is triggered). This script " +"will be written by you (samples below), and contain the logic for sending " +"API/email messages to Zammad:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:4 -msgid "A certificate *and* private key for your own organization" +#: ../system/integrations/checkmk/setup-guide.rst:26 +msgid "Checkmk \"New Rule\" dialog" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:6 +#: ../system/integrations/checkmk/setup-guide.rst:26 msgid "" -"(Use this to ✒️ **sign outgoing messages** and 🔓 **decrypt incoming " -"messages**.)" +"Find your custom scripts in the Checkmk WATO under **Notifications > New " +"Rule > Notification Method**." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:9 +#: ../system/integrations/checkmk/setup-guide.rst:29 msgid "" -"Certificates belonging your contacts, or their issuing certificate authority " -"(CA)" +"Once you're done setting up your new rule, you're all set! New tickets " +"should start coming in and auto-updating any time your rule is triggered." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:11 +#: ../system/integrations/checkmk/setup-guide.rst:33 msgid "" -"(Use these to ✅ **verify incoming message signatures** and 🔒 **encrypt " -"outgoing messages**.)" +"(If you need help troubleshooting, be sure to check the :ref:`checkmk-recent-" +"logs`.)" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:14 -msgid "🙋 **I'm new to S/MIME. Where can I get a certificate?**" +#: ../system/integrations/checkmk/setup-guide.rst:38 +msgid "API Alerts" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:16 +#: ../system/integrations/checkmk/setup-guide.rst:40 msgid "" -"The easiest way to get certificates is to buy an annual subscription through " -"a commercial CA, such as:" +"To add these scripts in the Checkmk WATO, copy them into your Checkmk " +"installation directory and make them executable. (Be sure to replace the " +"``zammad.example.com`` callback URL with the one found in your admin panel.)" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:19 +#: ../system/integrations/checkmk/setup-guide.rst:60 +msgid "Service notification" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:46 msgid "" -"`Sectigo (formerly Comodo) `_" +"For updates on the status of the software running on your server (*e.g.,* " +"postgres)." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:20 -msgid "`Secorio `_" +#: ../system/integrations/checkmk/setup-guide.rst:75 +msgid "Host notification" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:21 -msgid "`GlobalSign `_" +#: ../system/integrations/checkmk/setup-guide.rst:63 +msgid "For updates on the status of the server itself." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:23 -msgid "(Zammad is not affiliated with these CAs in any way.)" +#: ../system/integrations/checkmk/setup-guide.rst:77 +msgid "🤔 **What's with all the env vars?**" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:25 +#: ../system/integrations/checkmk/setup-guide.rst:79 msgid "" -"You can also generate your own self-signed certificates, but the process is " -"complicated and usually 🙅 **involves extra work for your contacts**." +"Whenever Checkmk runs these scripts, it needs to provide some information " +"about the event that triggered the notification. This information is passed " +"in the form of these ``$NOTIFY_*`` environment variables." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:29 +#: ../system/integrations/checkmk/setup-guide.rst:85 msgid "" -"Bear in mind that 🤝 **S/MIME only works if the other party is using it, too." -"**" +"You can specify additional parameters to pass to the script when you're " +"setting up your notification rule, but the ones you see here are all " +"provided by default." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:32 -msgid "Certificate and Private Key Checks on Upload" +#: ../system/integrations/checkmk/setup-guide.rst:90 +msgid "Email Alerts" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:34 +#: ../system/integrations/checkmk/setup-guide.rst:94 msgid "" -"The certificate and public key validation is based on the ``X509v3`` " -"extensions." +"🐞 **There are known bugs** in Zammad's processing of email from Checkmk. " +"This section will be completed once they have been resolved. (Learn more at " +"GitHub issues `#2377 `_ & " +"`#2180 `_.)" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:49 -msgid "Uploading a *client certificate*?" +#: ../system/integrations/checkmk/setup-guide.rst:100 +msgid "In the meantime, we encourage you to set up API alerts instead." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:41 -msgid "The following attributes are required then:" +#: ../system/integrations/clearbit.rst:2 +msgid "Clearbit" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:39 -msgid "Subject Alternative Name (at least one email address has to be present)" +#: ../system/integrations/clearbit.rst:4 +msgid "" +"With our Clearbit integration, you can easily enrich the information " +"provided by Zammad. If the customers or agents email address is known to " +"Clearbit, it will share all information it has regarding the user with " +"Zammad. Those information can include the following:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:40 -msgid "Key Usage (``Digital Signature`` and/or ``Key Encipherment``)" +#: ../system/integrations/clearbit.rst:9 +msgid "Avatar" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:41 -msgid "Public key algorithm (either ``RSA`` or ``EC``)" +#: ../system/integrations/clearbit.rst:10 +msgid "Address information" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:43 -msgid "" -"The Extended Key Usage attribute is optional. If the certificate provides " -"the named attribute, than it must contain the value ``E-mail Protection``." +#: ../system/integrations/clearbit.rst:11 +msgid "Website information" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:46 -msgid "" -"Please note that any usable email adress has to be prefixed with ``email:`` " -"or ``rfc822:``." +#: ../system/integrations/clearbit.rst:12 +msgid "A BIO (as Note by default)" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:49 -msgid "The named public key algorithms are mandatory for private keys as well." +#: ../system/integrations/clearbit.rst:14 +msgid "" +"If needed, you can add further custom objects and add mappings to them, so " +"the Clearbit information can be filled within the database. In general you " +"can get any information from Clearbit, as long as you have a mapping to an " +"Zammad object." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:54 -msgid "Uploading a *CA certificate*?" -msgstr "" - -#: ../system/integrations/smime/prerequisites.rst:52 +#: ../system/integrations/clearbit.rst:21 msgid "" -"In the case of an uploaded CA certificate, providing the value ``CA:TRUE`` " -"in the attribute *Basic Contstraints*, the previously mentioned attributes " -"are not verified." +"Clearbit does have a mapping of fields like LDAP and Exchange have, but does " +"not \"win\" against Zammad information. This means that if you have e.g. the " +"last name field filled in already and Clearbit has other information on " +"that, it will not be updated." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:56 +#: ../system/integrations/clearbit.rst:26 msgid "" -"In general, the usage of any expired (``Not After``) or not yet valid (``Not " -"Before``) certificate is denied for outgoing emails." +"However: If let's say the last name has been set by Clearbit and Zammad " +"notices that the last name on the Clearbit source has changed, Zammad will " +"also update this value." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:59 -msgid "Example certificate:" +#: ../system/integrations/clearbit.rst:33 +msgid "" +"The configuration of Clearbit is really easy and done fast! Just login to " +"your Clearbit-Account, go to \"API\" and copy the secret-API-Key." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:85 +#: ../system/integrations/clearbit.rst:38 msgid "" -"Please note that Zammad will distrust senders by default. This means that " -"you're always required to provide certificate data, no matter if for signing " -"or encrypting." +"Now change to your Zammad instance, go to Integrations (System) -> Clearbit " +"in the admin panel. Paste your API-Key into the API-Key-Field and decide if " +"Zammad should create unknown Organizations automatically, if the user does " +"not have one yet (and Clearbit knows it). The shared option decides if the " +"new organizations Zammad creates with Clearbit should be shared ones." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:89 -msgid "This is by design and can't be adjusted." +#: ../system/integrations/clearbit.rst:47 +msgid "" +"If you're unsure what option to choose, better stick with \"no\". You can " +"also learn more about :doc:`/manage/organizations/index`." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:4 +#: ../system/integrations/clearbit.rst:52 msgid "" -"All of the system's latest S/MIME activity is displayed in the **Recent " -"Logs** section." +"The Mapping option works similar to the mapping within the Exchange and LDAP " +"sync. You can add further mappings for e.g. custom fields if you need more " +"information that Clearbit can provide." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:11 -msgid "Sample entries of in- and outgoing S/MIME related emails." +#: ../system/integrations/clearbit.rst:58 +msgid "" +"If you want to add more Clearbit fields and want to learn more about " +"available fields on their API, you can take a look at their `API " +"documentation `_." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:11 +#: ../system/integrations/clearbit.rst:62 msgid "" -"Logs report the status and details of all mail, both incoming and outgoing, " -"that used signing/verification or encryption/decryption." +"If you're happy with the above chosen Settings and your mapping, just save " +"the changes and enable Clearbit integration. Zammad will now start polling " +"the Clearbit API as users contact you." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:14 +#: ../system/integrations/clearbit.rst:68 msgid "" -"This log does **not** include email sent by :doc:`triggers ` or the :doc:`scheduler `. For those, check your " -"``production.log``." +"Zammad does not synchronize with Clearbit on a regular basis, but on demand " +"if needed. This saves API calls." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:20 -msgid "Common Issues" +#: ../system/integrations/clearbit.rst:73 +msgid "" +"Below the Settings and Mappings, you'll find our Integration log. You can " +"see what requests Zammad sent to Clearbit and also the APIs Response." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:30 -msgid "I received a signed/encrypted email before I set up S/MIME integration" +#: ../system/integrations/clearbit.rst:78 +msgid "" +"By the way, you can also view the API log on the Clearbit website - the " +"information seen is basically the same." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:23 -msgid "" -"No problem. Once S/MIME has been enabled and the appropriate certificates " -"have been added, agents will be prompted to retry verification/decryption on " -"matching emails." +#: ../system/integrations/clearbit.rst:84 +msgid "Example When Adding a User" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:0 -msgid "Screenshot of user prompt to retry decryption" +#: ../system/integrations/clearbit.rst:86 +msgid "" +"To show you how fast information is added, we added a small Screencast " +"below. This shows the creation of the User Alex from Clearbit. As we already " +"set the last name of Alex to \"X\", Zammad did not update it. What Zammad " +"did was to add further information it received from Clearbit." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:38 -msgid "The 🔒 **Encrypt** button is disabled" +#: ../system/integrations/cti/generic.rst:2 +msgid "CTI (generic)" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:33 -msgid "Have you added the recipient's certificate?" +#: ../system/integrations/cti/includes/introduction.include.rst:1 +msgid "" +"This integration enables Zammad to provide a caller log to your agents. With " +"this your agents can greet your customers by their name and are supported by " +"Zammad with automatically opening a new ticket dialog or the user profile." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:34 -msgid "Are you sure the recipient's certificate is valid?" +#: ../system/integrations/cti/includes/introduction.include.rst:6 +msgid "" +"Click the toggle next to the heading to activate or deactivate this " +"integration." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:35 -msgid "Have you checked your ``production.log`` for more details?" +#: ../system/integrations/cti/includes/introduction.include.rst:9 +msgid "" +"If you want to learn more on how your agents can use this function, please " +"refer the :user-docs:`user documentation `." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:37 +#: ../system/integrations/cti/includes/introduction.include.rst:14 msgid "" -"If encryption doesn't work in the composer, it won't work in :doc:`triggers " -"` or the :doc:`scheduler ` either!" +"Automatically opening new ticket dialogues or user profiles requires agent " +"to extension mapping - see more below." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:42 -msgid "The ✅ **Sign** button is disabled" +#: ../system/integrations/cti/includes/introduction.include.rst:20 +msgid "Please note the following limitations to reduce confusion later on:" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:41 -msgid "" -"Have you added **both the certificate and private key** for your " -"organization?" +#: ../system/integrations/cti/includes/introduction.include.rst:22 +msgid "CTI integrations provide caller log functions only." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:42 +#: ../system/integrations/cti/includes/introduction.include.rst:23 msgid "" -"Does the email address on the certificate match the email address of the " -"agent/group composing the email?" +"This integration does not provide any VoIP functionalities; you can't make " +"phone calls from within Zammad." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:45 -msgid "Error: “Fingerprint already taken”" +#: ../system/integrations/cti/includes/introduction.include.rst:25 +msgid "" +"If your browser supports ``tel``-URLs, you can click on phone numbers for " +"automatic dialing. This requires additional software / configuration on your " +"agent's computers." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:45 -msgid "Are you sure you haven't added this certificate already?" +#: ../system/integrations/cti/generic.rst:9 +#: ../system/integrations/cti/placetel.rst:14 +#: ../system/integrations/cti/sipgate.rst:14 +msgid "Please provide the following requirements:" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:48 -msgid "Error: “❌ invalid byte sequence in UTF-8”" +#: ../system/integrations/cti/generic.rst:11 +msgid "" +"A telephone system that supports webhooks (outbound) (best option are those " +"that allow customizing the calls)." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:48 -msgid "Please ensure to provide PEM formatted certificate and keys." +#: ../system/integrations/cti/generic.rst:13 +msgid "A unique Call-ID during the call session." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:49 -msgid "Did you check if the provided file is a valid certificate or key?" +#: ../system/integrations/cti/generic.rst:14 +msgid "Call event data (both numbers and direction)." msgstr "" -#: ../system/integrations/zabbix.rst:2 -msgid "Zabbix Integration" +#: ../system/integrations/cti/generic.rst:15 +msgid "Your Zammad instance must be reachable for your telephony system." msgstr "" -#: ../system/integrations/zabbix.rst:5 +#: ../system/integrations/cti/generic.rst:17 msgid "" -"This guide describes how to integrate your Zabbix 5.4 installation with " -"Zammad using the Zabbix webhook feature. This guide will provide " -"instructions on setting up a media type, a user and an action in Zabbix." +"If you want to learn more on what kind of requests are supported by Zammad " +"and what it expects, please consult our :docs:`CTI-API documentation `." msgstr "" -#: ../system/integrations/zabbix.rst:12 -msgid "Zammad with enabled HTTP Token Authentication" +#: ../system/integrations/cti/generic.rst:22 +#: ../system/integrations/cti/placetel.rst:27 +#: ../system/integrations/cti/sipgate.rst:30 +msgid "Available Settings" msgstr "" -#: ../system/integrations/zabbix.rst:13 -msgid "Zabbix version 5.4 or higher" +#: ../system/integrations/cti/generic.rst:29 +#: ../system/integrations/cti/placetel.rst:41 +#: ../system/integrations/cti/sipgate.rst:40 +msgid "Endpoint Settings" msgstr "" -#: ../system/integrations/zabbix.rst:16 -msgid "Setting up a Zammad" +#: ../system/integrations/cti/generic.rst:25 +msgid "" +"Zammad will list your generic CTI endpoint here. It contains a unique token " +"so ensure to keep this URL save." msgstr "" -#: ../system/integrations/zabbix.rst:18 -msgid "Enable **API Token Access** in Settings > System > API." +#: ../system/integrations/cti/generic.rst:28 +msgid "" +"You'll need this endpoint for your PBX to talk to Zammad, see :docs:`CTI-API " +"documentation `." msgstr "" -#: ../system/integrations/zabbix.rst:20 +#: ../system/integrations/cti/includes/important-dont-forget-saving.include.rst:3 msgid "" -"Create a **new user** for a Zabbix alerter with an **email address** and " -"create a personal user token with **ticket.agent** permissions." +"All following options **do not save automatically**. Always use the Save " +"button on the lower end of the integration page!" msgstr "" -#: ../system/integrations/zabbix.rst:24 -msgid "Zabbix Webhook Configuration" +#: ../system/integrations/cti/generic.rst:43 +#: ../system/integrations/cti/placetel.rst:49 +#: ../system/integrations/cti/sipgate.rst:52 +msgid "Call Settings" msgstr "" -#: ../system/integrations/zabbix.rst:27 -#, fuzzy -msgid "Create a Global Macro" -msgstr "Makra" - -#: ../system/integrations/zabbix.rst:29 -msgid "" -"Before setting up the **Webhook**, you need to setup the global macro " -"**{$ZABBIX.URL}**, which must contain the **URL** to the **Zabbix frontend**." +#: ../system/integrations/cti/generic.rst:39 +#: ../system/integrations/cti/placetel.rst:49 +#: ../system/integrations/cti/sipgate.rst:37 +#: ../system/integrations/cti/sipgate.rst:50 +msgid "Inbound" msgstr "" -#: ../system/integrations/zabbix.rst:33 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:1 msgid "" -"In the **Administration** > **Media types** section, import the `Template`_." +"This option allows you to block specific incoming caller IDs. It allows you " +"to temporarily reject e.g. spam callers without having to contact providers " +"or PBX administrators." msgstr "" -#: ../system/integrations/zabbix.rst:38 -msgid "Open the added **Zammad** media type and set:" +#: ../system/integrations/cti/includes/inbound-calls.include.rst:11 +msgid "Caller ID to block" msgstr "" -#: ../system/integrations/zabbix.rst:40 -msgid "**zammad\\_access\\_token** to the your **Personal User Token**" +#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 +msgid "Provide caller IDs to block in ``E.164`` format." msgstr "" -#: ../system/integrations/zabbix.rst:41 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:8 msgid "" -"**zammad\\_url** to the **frontend URL** of your **Zammad** installation" +"Your telephony system has to support this function. Zammad will send a " +"``reject`` response which will cause your telephony system to hang up the " +"call. To callers this usually will feel like the line is busy." msgstr "" -#: ../system/integrations/zabbix.rst:43 -msgid "**zammad\\_customer** to your **Zammad user email**." +#: ../system/integrations/cti/includes/inbound-calls.include.rst:14 +msgid "" +"Provide a meaningful note for your fellow administrators to remind yourself " +"why you've chosen to block the number." msgstr "" -#: ../system/integrations/zabbix.rst:44 -msgid "" -"**zammad\\_enable\\_tags** to **true** or **false** to enable or disable " -"trigger tags. **Important**: if you enable tag support, each tag is set with " -"a separate request." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:17 +#: ../system/integrations/cti/sipgate.rst:40 +msgid "Outbound" msgstr "" -#: ../system/integrations/zabbix.rst:48 +#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:1 msgid "" -"If you want to prioritize issues according to **severity** values in Zabbix, " -"you can define mapping parameters:" +"In many cases you may want to use a different caller ID depending on the " +"destination you're calling. This may apply due to specific connection rates " +"to other countries or because you want your customer to feel you're calling " +"from the same country." msgstr "" -#: ../system/integrations/zabbix.rst:51 -msgid "**severity\\_**: Zammad priority ID" +#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:6 +msgid "This option expects ``E.164`` number formats." msgstr "" -#: ../system/integrations/zabbix.rst:53 -msgid "Click the **Update** button to save the **Webhook** settings." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 +msgid "Destination caller ID" msgstr "" -#: ../system/integrations/zabbix.rst:55 -msgid "" -"To receive notifications in **Zammad**, you need to create a **Zabbix user** " -"and add **Media** with the **Zammad** type." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:5 +msgid "The caller ID or number you're trying to call." msgstr "" -#: ../system/integrations/zabbix.rst:58 -msgid "" -"For **Send to**: enter any text, as this value is not used, but is required." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:7 +msgid "You can use wildcards for e.g. country specific outbound numbers like:" msgstr "" -#: ../system/integrations/zabbix.rst:61 -msgid "" -"For more information, use the `Zabbix documentation `_." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:9 +msgid "``49*`` for Germany" msgstr "" -#: ../system/maintenance.rst:2 -msgid "Maintenance" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:10 +msgid "``4930*`` for Berlin / Germany landlines" msgstr "" -#: ../system/maintenance.rst:4 -msgid "" -"Zammad comes with a maintenance mode that you can use for e.g. updating the " -"instance or changing settings while restricting availability and functions." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 +msgid "``33*`` for France" msgstr "" -#: ../system/maintenance.rst:13 -msgid "Mode" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:15 +msgid "Set Outbound caller ID" msgstr "" -#: ../system/maintenance.rst:8 -msgid "The mode setting allows you to enable or disable the maintenance mode." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:14 +msgid "" +"The outbound caller ID to set (the number your customer sees on his display) " +"in ``E.164`` number format." msgstr "" -#: ../system/maintenance.rst:10 -msgid "Defaults to *off*." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 +msgid "Provide a short description for fellow administrators." msgstr "" -#: ../system/maintenance.rst:12 +#: ../system/integrations/cti/includes/generic-cti-support-note.includes.rst:3 msgid "" -"The maintenance mode will restrict access to administrative roles only. This " -"means agents and customers are logged off." +"This option requires your PBX to send a specific request to Zammad *before " +"dialing*. Please consult the :docs:`CTI API ` in case " +"you're not sure." msgstr "" -#: ../system/maintenance.rst:23 -msgid "@Login" +#: ../system/integrations/cti/generic.rst:52 +#: ../system/integrations/cti/placetel.rst:54 +#: ../system/integrations/cti/sipgate.rst:59 +msgid "Other Settings" msgstr "" -#: ../system/maintenance.rst:16 +#: ../system/integrations/cti/includes/other-settings-intro.include.rst:1 msgid "" -"This setting allows you to provide a login message within a green banner " -"above the login screen. Click into the green banner in the settings page to " -"adjust your message. To activate the message, activate the *@Login* setting." +"Below you can find all available additional settings for this CTI " +"integration. For your overview we're sorting them by appearance and " +"reference their description first." msgstr "" -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing the default login message within the\n" -"settings page" +#: ../system/integrations/cti/includes/default-caller-id.include.rst:2 +#: ../system/integrations/cti/includes/default-caller-id.include.rst:1 +msgid "Default caller ID for outbound calls" msgstr "" -#: ../system/maintenance.rst:26 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:16 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:15 +msgid "Shown records in caller log" +msgstr "" + +#: ../system/integrations/cti/includes/records-caller-log.include.rst:2 msgid "" -"Send an informative message to **all active sessions**. This comes handy to " -"inform your agents e.g. about mayor outages or to force reloads after " -"configuration changes." +"Allows you to set the number of shown caller log entries for all users. You " +"can choose from the following values:" msgstr "" -#: ../system/maintenance.rst:31 -msgid "This is the messages title (slightly bigger than the normal message)." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:5 +msgid "60 (default)" msgstr "" -#: ../system/maintenance.rst:34 -msgid "The text you want to provide to your logged in sessions." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:6 +msgid "120" msgstr "" -#: ../system/maintenance.rst:39 -msgid "Reload application" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:7 +msgid "180" msgstr "" -#: ../system/maintenance.rst:37 -msgid "" -"Selecting this option will change the message acceptance button from *Close* " -"(with nothing happening) to *Continue session*, which forces the application " -"to reload." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:8 +msgid "240" msgstr "" -#: ../system/maintenance.rst:43 -msgid "" -"If you have customers that are logged in to Zammad, they'll also be notified " -"if they're active in that moment." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:9 +msgid "300" msgstr "" -#: ../system/maintenance.rst:48 -msgid "Example without reload application" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:11 +msgid "**🥵 Potential performance issue**" msgstr "" -#: ../system/maintenance.rst:52 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:13 msgid "" -"Message setting within Zammad's admin settings without ticket reload " -"application setting." +"Setting this setting higher than 60 may cause serious performance issues on " +"very busy instances. Keep in mind that this setting causes Zammad to poll " +"and send up to 300 records to *all active agent sessions* in very short time " +"periods." msgstr "" -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing the send message settings without ticket\n" -"reload application set" +#: ../system/integrations/cti/generic.rst:73 +msgid "Caller Log Filter" msgstr "" -#: ../system/maintenance.rst:61 ../system/maintenance.rst:85 +#: ../system/integrations/cti/generic.rst:55 msgid "" -"The modal all other active sessions will see upon pressing *Send to clients*." +"This function allows you to provide call information based on e.g. queues " +"only to agents that really need the information." msgstr "" -#: ../system/maintenance.rst:0 +#: ../system/integrations/cti/generic.rst:58 msgid "" -"Screenshot showing modal caused by maintenance's message\n" -"without reload application ticket" +"Why? If you have a team for several countries or departments, you don't want " +"to bug your agents from other departments. Leaving these options empty will " +"fallback to showing everything to everyone." msgstr "" -#: ../system/maintenance.rst:72 -msgid "Example with reload application" +#: ../system/integrations/cti/generic.rst:64 +msgid "Destination caller ID or Queue" msgstr "" -#: ../system/maintenance.rst:76 +#: ../system/integrations/cti/generic.rst:63 msgid "" -"Message setting within Zammad's admin settings with ticket reload " -"application setting." +"This depends on your PBX and usually is either a queue ID, phone number or " +"extension." msgstr "" -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing the send message settings with ticket\n" -"reload application set" +#: ../system/integrations/cti/generic.rst:69 +msgid "Agents" msgstr "" -#: ../system/maintenance.rst:0 +#: ../system/integrations/cti/generic.rst:67 msgid "" -"Screenshot showing modal caused by maintenance's message\n" -"with reload application ticket" +"Select the agents that are responsible for the group. These agents will then " +"see caller log entries and call notifications fitting to said queue." msgstr "" -#: ../system/monitoring.rst:2 -msgid "Monitoring" +#: ../system/integrations/cti/generic.rst:0 +msgid "" +"Screenshot showing the caller log filter table with pre filled sample data" msgstr "" -#: ../system/monitoring.rst:4 +#: ../system/integrations/cti/includes/recent-logs.include.rst:6 msgid "" -"This function is only available in self hosted instances. If you use Zammad " -"in our cloud, we are monitoring the system on our own and take steps to fix " -"potential problems directly." +"With recent logs Zammad allows you to view the latest calls for the CTI " +"functionality. This usually comes in handy, when you're looking for errors." msgstr "" -#: ../system/monitoring.rst:11 +#: ../system/integrations/cti/includes/recent-logs.include.rst:0 msgid "" -"On the monitoring page, you can see the current health state of Zammad under " -"\"*Current Status*\" at the bottom. This can be useful if you want to have a " -"look if everything is up and running. As an example, you could have a look " -"in the monitoring when you assume that some emails aren't processed from " -"Zammad." +"Screenshot showing several incoming requests within Recent logs section." msgstr "" -#: ../system/monitoring.rst:17 -msgid "**Can't receive an email and the monitoring response is \"healthy\"?**" +#: ../system/integrations/cti/includes/recent-logs.include.rst:16 +msgid "I'm just here to clear floats up." msgstr "" -#: ../system/monitoring.rst:19 +#: ../system/integrations/cti/includes/recent-logs.include.rst:20 msgid "" -"Zammad will just inform you about unprocessable emails. This is not the case " -"for oversized emails. You can adjust the maximum email size in :doc:`../" -"channels/email/settings`." -msgstr "" - -#: ../system/monitoring.rst:24 -msgid "Monitoring API" +"By clicking on the entry of interest, Zammad will provide more details on " +"the call in question. You'll see the payload it received and also the " +"response that was sent." msgstr "" -#: ../system/monitoring.rst:26 +#: ../system/integrations/cti/includes/recent-logs.include.rst:0 msgid "" -"Beside the indication in the monitoring page, you can also use an external " -"monitoring tool to monitor Zammad's health. To request the health of Zammad, " -"you need to provide the API key (token) to the external monitoring tool. You " -"can copy the token from the \"*Current Token*\" field as well as the whole " -"API endpoint of your system (\"*Health Check*\" field), in which the API " -"token is already included." +"Screenshot showing detailed information of a specific log entry of recent " +"logs" msgstr "" -#: ../system/monitoring.rst:37 -msgid "Screenshot showing Current Token and Health Check" +#: ../system/integrations/cti/includes/recent-logs.include.rst:31 +msgid "x" msgstr "" -#: ../system/monitoring.rst:37 -msgid "Screenshot showing Token and Health Check" +#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 +#: ../system/integrations/cti/includes/troubleshooting.include.rst:9 +msgid "My Phone page stays blank, signalling does work..." msgstr "" -#: ../system/monitoring.rst:39 +#: ../system/integrations/cti/includes/troubleshooting.include.rst:5 msgid "" -"In addition to that, you can reset the auto-generated token to make sure " -"that already configured monitoring systems won't work anymore. So, please " -"use this \"*Reset*\" button only if you know what you do!" +"If you've made sure that signalling works (check Recent logs) and your " +"Caller Log still stays empty, please ensure that you only configured one CTI " +"integration version. Specifically defining more than one agent mapping on " +"the different integration variants will be the issue." msgstr "" -#: ../system/monitoring.rst:44 -#, fuzzy -msgid "Example Output" -msgstr "Przykład" - -#: ../system/monitoring.rst:0 -msgid "No issues found" +#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 +msgid "Clear the not needed agent mapping and reload your browser page." msgstr "" -#: ../system/monitoring.rst:48 ../system/monitoring.rst:60 -msgid "**Indicator in Zammad**:" -msgstr "" - -#: ../system/monitoring.rst:0 -msgid "Screenshot showing monitoring with no issues" +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:1 +msgid "" +"By mapping your agents extension to their existing Zammad users, Zammad can " +"provide a new ticket dialog or open the user profile for the agent that " +"picks up the call." msgstr "" -#: ../system/monitoring.rst:54 ../system/monitoring.rst:66 -msgid "**API response**::" +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:5 +msgid "" +"This speeds up ticket aiding, no matter if it's for existing tickets or new " +"ones!" msgstr "" -#: ../system/monitoring.rst:0 -msgid "Issues were found" +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:8 +msgid "" +"To see it work from the agent's perspective, have a look on :user-docs:`user " +"documentation `." msgstr "" -#: ../system/monitoring.rst:0 -msgid "Screenshot showing monitoring with issues" +#: ../system/integrations/cti/placetel.rst:2 +msgid "Placetel CTI" msgstr "" -#: ../system/objects.rst:2 -msgid "Objects" +#: ../system/integrations/cti/placetel.rst:16 +msgid "You need an administrative Placetel account for your organization." msgstr "" -#: ../system/objects.rst:4 +#: ../system/integrations/cti/placetel.rst:17 +#: ../system/integrations/cti/sipgate.rst:20 msgid "" -"In Zammad you can add your own fields to tickets, users, organizations and " -"even groups (these are called \"objects\"). This can be useful if you need " -"to add further information to a ticket or any other object in Zammad and the " -"information doesn't fit in any existing field." +"Your Zammad instance must be allowed to communicate to external services." msgstr "" -#: ../system/objects.rst:11 -msgid "" -"Try to avoid deleting attributes (and disable them instead) as Zammad might " -"run into unexpected conditions if they are referenced somewhere." +#: ../system/integrations/cti/placetel.rst:18 +msgid "Placetel must be able to reach your Zammad instance." msgstr "" -#: ../system/objects.rst:16 -msgid "" -"Here's an overview of object attributes. On the upper right you can add new " -"attributes. By default, there will be no custom fields - standard attributes " -"will be grayed out, you can't delete or change those. You can edit custom " -"attributes (they are displayed in black font and have a trash bin on the " -"right side) just by clicking on them." +#: ../system/integrations/cti/placetel.rst:22 +msgid ":doc:`provider-configurations/placetel`" msgstr "" -#: ../system/objects.rst:24 +#: ../system/integrations/cti/placetel.rst:21 msgid "" -"Attributes you add to Zammad, no matter if they have default values or not, " -"will not update existing information. This means a new ticket field " -"technically will be empty unless you populate it." +"Learn how to configure Placetel to enable Zammad and Placetel to communicate " +"with each other." msgstr "" -#: ../system/objects.rst:28 +#: ../system/integrations/cti/placetel.rst:32 msgid "" -"Especially in ticket scope this also means that newly added attributes will " -"be indicated as \"changed\" to agents that view the ticket. This may " -"interfere with Zammad's tabs behavior." +"The here listed endpoint settings are relevant for the :doc:`integration " +"configuration with Placetel `." msgstr "" -#: ../system/objects.rst:40 -msgid "Ordering Attributes" +#: ../system/integrations/cti/placetel.rst:37 +#: ../system/integrations/i-doit.rst:53 +msgid "Endpoint" msgstr "" -#: ../system/objects.rst:42 +#: ../system/integrations/cti/placetel.rst:36 msgid "" -"Since Zammad introduced :doc:`/system/core-workflows` the need to have a " -"custom positioning for attributes has become more important than ever." +"This endpoint will be required for the Zammad integration within the " +"Placetel web interface." msgstr "" -#: ../system/objects.rst:45 -msgid "" -"To adjust the position of such an attribute, simply click on the attribute " -"entry in question, scroll down and adjust the position number. Please note " -"that you cannot change the positioning of default attributes." +#: ../system/integrations/cti/placetel.rst:41 +msgid "API Token" msgstr "" -#: ../system/objects.rst:49 +#: ../system/integrations/cti/placetel.rst:40 msgid "" -"In case two attributes have the same position value, Zammad will sort " -"alphabetically by name automatically." +"You'll receive this token within the ``Web API`` menu. Make sure to copy " +"this value, it's only shown once!" msgstr "" -#: ../system/objects.rst:None -msgid "" -"Screenshot showing custom attribute entries ordered in between default ones" +#: ../system/integrations/cti/placetel.rst:71 +#: ../system/integrations/cti/sipgate.rst:77 +msgid "Phone Extension to Agent Mapping" msgstr "" -#: ../system/objects.rst:56 -msgid "Updating Database After Adding or Editing Attributes" +#: ../system/integrations/cti/placetel.rst:0 +msgid "Screenshot showing sample user mappings in between Placetel and Zammad" msgstr "" -#: ../system/objects.rst:58 +#: ../system/integrations/cti/placetel.rst:64 msgid "" -"When adding or changing attributes, Zammad will not apply the changes " -"instantly, but instead shows you the changed attributes first. If you're " -"ready to go, just click on \"Update database\" to apply the changes to " -"Zammad. If you made a mistake or just want to discard your changes, click " -"\"Discard changes\"." +"You can find your agents Placetel username combination required within ⚙️ PBX " +"→ VoIP destinations. Within the \"Advanced settings\" section you're looking " +"for \"SIP user name\" and \"SIP server\"." msgstr "" -#: ../system/objects.rst:64 -msgid "" -"After applying the changes with \"Update Database\", a restart of Zammad is " -"**mandatory**. If you don't perform it, you may experience unexpected " -"behavior or even errors. You may want to do this kind of configuration " -"during maintenance windows." +#: ../system/integrations/cti/placetel.rst:68 +msgid "Combine these two like so: ``@``." msgstr "" -#: ../system/objects.rst:72 -msgid "" -"Changes on objects require you to update the database to apply these changes." +#: ../system/integrations/cti/placetel.rst:0 +msgid "Sample VoIP credentials for a Placetel user" msgstr "" -#: ../system/objects.rst:75 -msgid "**🤓 Service restarts can be automated**" +#: ../system/integrations/cti/provider-configurations/placetel.rst:2 +msgid "Setup Placetel connection for Zammad" msgstr "" -#: ../system/objects.rst:0 -msgid "Hosted environments automatically restart for you." +#: ../system/integrations/cti/provider-configurations/placetel.rst:6 +msgid "" +"This configuration step requires a *full* administrative Placetel account. " +"You may receive forbidden error messages with Placetel in case your " +"permissions are not high enough." msgstr "" -#: ../system/objects.rst:0 +#: ../system/integrations/cti/provider-configurations/placetel.rst:10 msgid "" -"If you're using a self-hosted installation you can use :docs:`environment " -"variables `" +"The following actions can be configured via the `Placetel web interface " +"`_." msgstr "" -#: ../system/objects.rst:82 -msgid "System Attributes" +#: ../system/integrations/cti/provider-configurations/placetel.rst:29 +msgid "Step 1: Activate Zammad integration" msgstr "" -#: ../system/objects.rst:84 +#: ../system/integrations/cti/provider-configurations/placetel.rst:14 msgid "" -"Zammad comes with pre-configured attributes. Some of them can't be edited " -"via UI (or at all). This is required for proper operation of Zammad and not " -"a bug." +"Within Integrations, scroll down to Partner integrations and select Zammad." msgstr "" -#: ../system/objects.rst:90 -msgid "Ticket State" +#: ../system/integrations/cti/provider-configurations/placetel.rst:17 +msgid "" +"You can alternatively filter by \"Ticket Systems\" to reduce the number of " +"entries on the page. You'll still want to look for Partner integrations. 🤓" msgstr "" -#: ../system/objects.rst:92 +#: ../system/integrations/cti/provider-configurations/placetel.rst:21 msgid "" -"If the pre-configured states aren't enough for you or you want to change " -"them, you can do so by clicking on the cogwheel icon in the state row in the " -"ticket tab. But you should be careful when changing pre-configured states. " -"This can lead to unwanted behavior in some cases." +"Within the Zammad integration now press \"Activate\". A new tab ``API`` " +"becomes available - open this tab." msgstr "" -#: ../system/objects.rst:None -msgid "Screenshot showing highlighted ticket state attribute" +#: ../system/integrations/cti/provider-configurations/placetel.rst:24 +msgid "" +"Now tick \"Enable Call Control / Notify API\" and paste the Placetel " +"endpoint from your Zammad instance into the field \"URL of your API " +"endpoint\". Save to apply the settings" msgstr "" -#: ../system/objects.rst:122 -msgid "Handling of states" +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "Screencast showing how to activate the Zammad integration" msgstr "" -#: ../system/objects.rst:102 +#: ../system/integrations/cti/provider-configurations/placetel.rst:51 +msgid "Step 2: Generate API Token for Placetel" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:32 msgid "" -"In the state configuration screen, you can add new states, disable states or " -"change states." +"Go back to the integrations page and scroll down to \"Web API\". Generate a " +"new API token by using the \"Create a new API token\" button." msgstr "" -#: ../system/objects.rst:0 -msgid "Screenshot showing table of default ticket states" +#: ../system/integrations/cti/provider-configurations/placetel.rst:37 +msgid "" +"If you already generated a token either use your existing token or reset it " +"by using above mentioned button. Placetel will ask you to conform this reset." msgstr "" -#: ../system/objects.rst:110 +#: ../system/integrations/cti/provider-configurations/placetel.rst:41 msgid "" -"To add a new state, click on the \"New Ticket State\" button in the top " -"right corner. To change an existing state, simply click on the affected " -"state. This opens an edit dialog." +"Please keep in mind that existing API scripts may no longer work due to " +"token resets!" msgstr "" -#: ../system/objects.rst:114 +#: ../system/integrations/cti/provider-configurations/placetel.rst:44 msgid "" -"You can also clone a state or set them to \"Default for new tickets\" or " -"\"Default for follow-ups\" by clicking on the ⁝ action button and select the " -"desired function." +"Copy the provided API token and insert it into the \"API Token\" field " +"within Zammad's Placetel integration." msgstr "" -#: ../system/objects.rst:118 +#: ../system/integrations/cti/provider-configurations/placetel.rst:47 msgid "" -"*Default for new tickets* means that this state is used for every newly " -"created ticket." +"Apply your changes by using the \"Save\" button on the bottom of the " +"Placetel integration page and activate the Placetel integration." msgstr "" -#: ../system/objects.rst:121 +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 msgid "" -"*Default for follow-ups* means that this state is used if the ticket is re-" -"opened after it was closed." +"Screencast showing how to retrieve an API token from Placetel for Zammad" msgstr "" -#: ../system/objects.rst:171 -msgid "Ticket state in detail" +#: ../system/integrations/cti/provider-configurations/placetel.rst:73 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:77 +msgid "Step 3: Restrict the numbers to notify on" msgstr "" -#: ../system/objects.rst:125 +#: ../system/integrations/cti/provider-configurations/placetel.rst:54 msgid "" -"Below you can find a description for each field and option. Please head over " -"to the :ref:`example ` to see the edit dialog." +"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " +"the the Integrations page of the Placetel web interface, go to \"Notify " +"API\"." msgstr "" -#: ../system/objects.rst:129 +#: ../system/integrations/cti/provider-configurations/placetel.rst:58 msgid "" -"This is the name of the state and what you and your agents are seeing when " -"choosing a state somewhere (e.g. in tickets, trigger configuration)." +"Lower on the page Placetel allows you to restrict the numbers to notify on. " +"You'll find this within the \"External routing API\" part." msgstr "" -#: ../system/objects.rst:137 +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 msgid "" -"There are different state types you can choose from. By default, Zammad " -"comes with one state per state type." +"Screenshot showing a sample selection of phone numbers to use for the " +"Placetels notify API" msgstr "" -#: ../system/objects.rst:140 +#: ../system/integrations/cti/provider-configurations/placetel.rst:66 msgid "" -"**new**: for states for tickets that are new and it hasn't been worked on " -"them" +"This menu point also provides a API request log from Placetel view. Just " +"open \"Recent responses of your API endpoint\" to learn more." msgstr "" -#: ../system/objects.rst:142 +#: ../system/integrations/cti/provider-configurations/placetel.rst:69 msgid "" -"**open**: for states for tickets that are in progress and agents are working " -"on them" +"If you want to see Zammad's perspective, use the \"Recent Logs\" part from " +"within the Placetel integration page." msgstr "" -#: ../system/objects.rst:144 -msgid "**merged**: for states for tickets that are merged with other tickets" +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "Screenshot showing sample log entries for Placetels API calls to Zammad" msgstr "" -#: ../system/objects.rst:145 -msgid "" -"**pending reminder**: for states for tickets that are in progress and you " -"want to set a reminder. (default example: *pending reminder*)" +#: ../system/integrations/cti/provider-configurations/placetel.rst:77 +msgid "Step 4 (optional): Further configurations for Placetel" msgstr "" -#: ../system/objects.rst:147 +#: ../system/integrations/cti/provider-configurations/placetel.rst:76 msgid "" -"**pending action**: for states for tickets that are waiting for a specified " -"time and then change their state (default example: *pending close*)" +"If needed, you can now configure Zammad's Placetel integration in more " +"detail. You can learn more about your options here: :ref:`Placetel " +"integration settings `." msgstr "" -#: ../system/objects.rst:150 -msgid "" -"**closed**: for states for tickets that are finished and do not need to be " -"processed further" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:2 +msgid "Setup Sipgate connection for Zammad" msgstr "" -#: ../system/objects.rst:153 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"⚠️ Choosing the correct state type is important! If you are in doubt, have a " -"look on the default states and their types!" -msgstr "" - -#: ../system/objects.rst:158 -msgid "Ignore escalation" +"Sipgate has no english web interface which is why this documentation page is " +"mixing up languages badly." msgstr "" -#: ../system/objects.rst:157 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"Here you can define whether tickets of this state will count to escalation " -"time or not." +"Please also note that the availability of API addons highly depends on your " +"package trier. Usage of sipgate.io packages *is not free*, please check " +"their `pricing page `_ before!" msgstr "" -#: ../system/objects.rst:161 -msgid "" -"You can create a note for the state to inform other admins about the state. " -"This has no effect on tickets." +#: ../system/integrations/cti/provider-configurations/sipgate.rst:35 +msgid "Step 1: Book sipgate.io package" msgstr "" -#: ../system/objects.rst:165 -msgid "Set the state to *active* or *inactive*." +#: ../system/integrations/cti/provider-configurations/sipgate.rst:13 +msgid "Skip to step 2 if you already have the package booked!" msgstr "" -#: ../system/objects.rst:167 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:15 msgid "" -"it is technically possible to set all states to inactive. To keep Zammad " -"working in such a case, the inactive flag of one of the states is ignored." -msgstr "" - -#: ../system/objects.rst:194 -msgid "Ticket state example" +"Login to an administrative Sipgate account and navigate to " +"``Accountverwaltung``. You'll see several different options depending on " +"your booked packages. Select ``Verträge & Produkte`` to continue." msgstr "" -#: ../system/objects.rst:174 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:19 msgid "" -"Let's assume we want to create a new state which indicates that the ticket " -"has to wait for a response of a third party (e.g. service contractor or " -"manufacturer) and we want to to be able to set a reminder." +"Scroll down to the section ``Zusätzliche Produkte buchen`` and look for " +"``sipgate.io`` - select this product by using the ``Produkte anzeigen``-" +"Button." msgstr "" -#: ../system/objects.rst:178 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:23 msgid "" -"First we give the new state a proper name. In this example we call it " -"\"waiting for manufacturer\"." +"On the next page select either one of the ``sipgate.io`` packages or ``Push-" +"API Package Free``. Follow the dialogue by booking the addon. You'll be " +"returned to your contract overview and now should see the selected addon in " +"your list." msgstr "" -#: ../system/objects.rst:181 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:30 msgid "" -"As state type we choose \"pending reminder\". This indicates that the ticket " -"is still open and we can set a reminder. This reminder can be useful if our " -"manufacturer sometimes isn't responding or we want to remind him to give us " -"an answer." +"The availability for ``sipgate.io`` packages and their levels highly depends " +"on the overall account type and product you've booked with Sipgate." msgstr "" -#: ../system/objects.rst:186 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"We choose \"no\" for \"ignore escalation\" because we want to escalate the " -"tickets even if we are waiting on the manufacturer's feedback." -msgstr "" - -#: ../system/objects.rst:189 -msgid "The **result** in the creation dialog will look like this:" +"Screencast showing the process on how to book the required sipgate.io addon" msgstr "" -#: ../system/objects.rst:0 -msgid "Screenshot showing ticket state creation dialog with example" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:52 +msgid "Step 2: Configure webhook for Zammad" msgstr "" -#: ../system/objects.rst:197 ../system/objects.rst:199 -#, fuzzy -msgid "Ticket Priority" -msgstr "priorytet" - -#: ../system/objects.rst:199 ../system/objects.rst:201 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:38 msgid "" -"If the pre-configured priorities aren't enough for you or you want to change " -"them, you can do so by clicking on the cogwheel icon in the priority row in " -"the ticket tab:" +"Within your ``Accountverwaltung`` navicate to your product ``sipgate.io``. " +"In the newly opened tab, switch from \"Clients\" to \"Webhooks\" and paste " +"the endpoint URLs from your Zammad instance like so:" msgstr "" -#: ../system/objects.rst:None -msgid "Screenshot showing highlighted ticket priority attribute" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:42 +msgid "Inbound endpoint to \"Incoming\"" msgstr "" -#: ../system/objects.rst:224 ../system/objects.rst:226 -msgid "Handling of priorities" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:43 +msgid "Outbound endpoint to \"Outgoing\"" msgstr "" -#: ../system/objects.rst:208 ../system/objects.rst:210 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:47 msgid "" -"In the priority configuration screen, you can add new priorities, disable " -"priorities or change priorities." +"Ensure to select at least one call group or phoneline within \"Sources\". " +"Other wise Sipgate will not indicate any incoming or outgoing calls to " +"Zammad." msgstr "" -#: ../system/objects.rst:0 -msgid "Screenshot showing table of default ticket priorities" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "" +"Screencast showing how to add Zammad's endpoint URLs to sipgate.ios webhook " +"configuration" msgstr "" -#: ../system/objects.rst:216 ../system/objects.rst:218 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:55 msgid "" -"To add a new priority, click on the \"New Priority\" button in the top right " -"corner. To change an existing priority, simply click on the affected " -"priority. This opens an edit dialog." +"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " +"the Webhooks → URLs section of Sipgate you can select which *sources* " +"Sipgate should notify Zammad about in- and outgoing calls." msgstr "" -#: ../system/objects.rst:220 ../system/objects.rst:222 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:59 msgid "" -"You can also clone a priority or set them to \"Default for new tickets\" by " -"clicking on the ⁝ action button and select the desired function." +"Use either specific phone lines or use the option \"Use for all phonelines " +"and groups\" to notify Zammad about all existing lines of your Sipgate " +"account." msgstr "" -#: ../system/objects.rst:223 ../system/objects.rst:225 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"*Default for new tickets* means that this priority is used for every newly " -"created ticket." +"Screenshot showing a sample selection of phone numbers to use for the " +"Sipgates webhooks API" msgstr "" -#: ../system/objects.rst:246 ../system/objects.rst:248 -msgid "Priorities in detail" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:68 +msgid "This section also allows you to enable a Debug log." msgstr "" -#: ../system/objects.rst:227 ../system/objects.rst:229 -msgid "Below you can find a description for each field and option." +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "Screenshot showing an enabled Debug log option" msgstr "" -#: ../system/objects.rst:230 ../system/objects.rst:232 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:73 msgid "" -"This is the name of the priority and what you and your agents are seeing " -"when choosing a priority somewhere (e.g. in tickets, trigger configuration)." -msgstr "" - -#: ../system/objects.rst:240 ../system/objects.rst:242 -msgid "Highlight color" +"After enabling you can use the Debug log section to see all sent webhook " +"calls to Zammad. You'll also can see the response." msgstr "" -#: ../system/objects.rst:235 ../system/objects.rst:237 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"Switch between *Low priority* (light blue), *High priority* (red) and - " -"(default). This affects the displayed color for ticket titles in overviews." +"Screenshot showing sample log entries for Sipgates webhook calls to Zammad" msgstr "" -#: ../system/objects.rst:239 ../system/objects.rst:241 -msgid "The color options are currently limited to the mentioned options." +#: ../system/integrations/cti/provider-configurations/sipgate.rst:81 +msgid "Step 4 (optional): Further configurations for Sipgate" msgstr "" -#: ../system/objects.rst:243 ../system/objects.rst:245 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:80 msgid "" -"You can create a note for the priority to inform other admins about the " -"priority. This has no effect on tickets." +"If needed, you can now configure Zammad's Sipgate integration in more " +"detail. You can learn more about your options here: :ref:`Sipgate " +"integration settings `." msgstr "" -#: ../system/objects.rst:247 ../system/objects.rst:249 -msgid "Set the priority to *active* or *inactive*." +#: ../system/integrations/cti/sipgate.rst:2 +msgid "Sipgate (sipgate.io)" msgstr "" -#: ../system/objects/external-data-source-example.rst:2 -msgid "External Data Source" +#: ../system/integrations/cti/sipgate.rst:16 +msgid "You need an administrative Sipgate account for your organization." msgstr "" -#: ../system/objects/external-data-source-example.rst:4 +#: ../system/integrations/cti/sipgate.rst:17 msgid "" -"We assume you already had a look on :doc:`types` where you can find a " -"description of the individual fields." +"Zammad requires a ``sipgate.io`` addon from the feature store (please note " +"that API calls are not free with Sipgate. Rates may apply and differ from " +"account to account)." msgstr "" -#: ../system/objects/external-data-source-example.rst:7 +#: ../system/integrations/cti/sipgate.rst:21 +msgid "Sipgate must be able to reach your Zammad instance." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:25 +msgid ":doc:`provider-configurations/sipgate`" +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:24 msgid "" -"To reproduce this example, choose a category you want to add a custom field, " -"click on *New Attribute* and select *External data source field* under " -"*Format*." +"Learn how to configure Sipgate to enable Zammad and Sipgate to communicate " +"with each other." msgstr "" -#: ../system/objects/external-data-source-example.rst:11 +#: ../system/integrations/cti/sipgate.rst:33 msgid "" -"Our example story is to fetch data from an external product database. We " -"want to add our products to the tickets so that the products can be searched " -"and chosen from a list and also create a link to the product website." +"Below endpoint settings affect the :doc:`sipgate.io configuration `." msgstr "" -#: ../system/objects/external-data-source-example.rst:16 -msgid "Base configuration" +#: ../system/integrations/cti/sipgate.rst:37 +msgid "This endpoint is required for incoming call hooks." msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Initial steps to configure external data source object type" +#: ../system/integrations/cti/sipgate.rst:40 +msgid "This endpoint is required for outgoing call hooks." msgstr "" -#: ../system/objects/external-data-source-example.rst:23 -#: ../system/variables.rst:85 -#, fuzzy -msgid "**Example:**" -msgstr "Przykład" +#: ../system/integrations/cti/sipgate.rst:0 +msgid "Screenshot showing sample user mappings in between Sipgate and Zammad" +msgstr "" -#: ../system/objects/external-data-source-example.rst:25 -msgid "Name: *product*" +#: ../system/integrations/cti/sipgate.rst:69 +msgid "" +"You can find your agent's Sipgate username within ``Accountverwaltung → " +"Benutzer``. You're looking for the SIP-ID." msgstr "" -#: ../system/objects/external-data-source-example.rst:26 -msgid "Display: *Product*" +#: ../system/integrations/cti/sipgate.rst:0 +msgid "Sample VoIP credentials for a Sipgate user" msgstr "" -#: ../system/objects/external-data-source-example.rst:29 -msgid "External data source configuration" +#: ../system/integrations/cti/sipgate.rst:77 +msgid "Users with several devices also have several SIP-IDs." msgstr "" -#: ../system/objects/external-data-source-example.rst:31 -msgid "" -"First, enter the search URL making sure it contains ``#{search.term}`` as a " -"parameter:" +#: ../system/integrations/elasticsearch.rst:2 +msgid "Elasticsearch (SaaS)" msgstr "" -#: ../system/objects/external-data-source-example.rst:34 -msgid "**Example:** ``https://dummyjson.com/products/search?q=#{search.term}``" +#: ../system/integrations/elasticsearch.rst:4 +msgid "" +"The Elasticsearch integration allows you to create a read-only user to use " +"with your favorite reporting tool (e.g. like Grafana)." msgstr "" -#: ../system/objects/external-data-source-example.rst:36 +#: ../system/integrations/elasticsearch.rst:7 msgid "" -"After that, head down to the preview section and enter a search input for " -"the external data source." +"If you want to take full advantage of the Zammad reporting, have a look at " +"our :docs:`Grafana ` " +"setup page as well." msgstr "" -#: ../system/objects/external-data-source-example.rst:39 -msgid "**Example:** ``mac``" +#: ../system/integrations/elasticsearch.rst:11 ../system/subscription.rst:7 +msgid "**🚧 Hosted environment specific 🚧**" msgstr "" -#: ../system/objects/external-data-source-example.rst:41 -msgid "Then you can find a preview of the response data below:" -msgstr "" - -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of JSON response based on search term" -msgstr "" - -#: ../system/objects/external-data-source-example.rst:48 +#: ../system/integrations/elasticsearch.rst:13 msgid "" -"We recommend using the preview to have a look on the structure. There is a " -"top-level element called ``products``. One level below, you can find the " -"attributes ``id`` and ``title``." -msgstr "" - -#: ../system/objects/external-data-source-example.rst:52 -msgid "**Search result response based on search from example:**" +"This integration is only available for Hosted setups. In order to use " +"Elasticsearch you'll need the **Plus** subscription." msgstr "" -#: ../system/objects/external-data-source-example.rst:119 +#: ../system/integrations/elasticsearch.rst:16 msgid "" -"To tell the remote system that the desired data is located below the " -"``products`` level, you have to put it in the field *Search result list key*." +"Self hosted users have all the control over their self hosted Elasticsearch " +"instances." msgstr "" -#: ../system/objects/external-data-source-example.rst:122 -msgid "" -"After inserting ``products`` in the mentioned field, you get an extended " -"preview. You can find an additional box *Search result list* with a JSON " -"structure. This is the same response as before but stripped from the upper " -"``products`` element by the external data source." +#: ../system/integrations/elasticsearch.rst:None +msgid "Elasticsearch integration page on SaaS environments" msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of JSON response search result list" +#: ../system/integrations/elasticsearch.rst:27 +msgid "" +"Please note the following limitations of Elasticsearch access on hosted " +"environments:" msgstr "" -#: ../system/objects/external-data-source-example.rst:132 -msgid "" -"Now you need to provide the keys for the search result values and labels. As " -"already mentioned, we are looking for the ``id`` and the ``title`` of our " -"products. If you haven't already, it is now a good time to look at the " -"preview of the *Search result list*." +#: ../system/integrations/elasticsearch.rst:30 +msgid "access to the Elasticsearch index is read-only access" msgstr "" -#: ../system/objects/external-data-source-example.rst:197 -msgid "" -"After locating our two keys, we insert them in *search result value key* " -"(``id``) and in *Search result label key* (``title``)." +#: ../system/integrations/elasticsearch.rst:31 +msgid "currently you're limited to user only" msgstr "" -#: ../system/objects/external-data-source-example.rst:200 +#: ../system/integrations/elasticsearch.rst:32 msgid "" -"Basically, we configured the external data source already and we can see a " -"table in the preview section:" +"Reporting tools that require to write into the indexes (like Kibana) are not " +"supported" msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of product table based on search term" +#: ../system/integrations/elasticsearch.rst:34 +msgid "IP access restriction is currently not yet supported" msgstr "" -#: ../system/objects/external-data-source-example.rst:208 -msgid "" -"According to our example story, now just the *Link template* is missing." +#: ../system/integrations/elasticsearch.rst:37 +msgid "Activating Elasticsearch Access" msgstr "" -#: ../system/objects/external-data-source-example.rst:210 +#: ../system/integrations/elasticsearch.rst:39 msgid "" -"Please note that this is an optional feature. If you don't want to use such " -"links, of course you don't have to configure it." +"By default external access to your Elasticsearch index is not active. You " +"can enable the integration at any time if needed." msgstr "" -#: ../system/objects/external-data-source-example.rst:213 +#: ../system/integrations/elasticsearch.rst:42 msgid "" -"We can add now an address where additional product information can be found." -msgstr "" - -#: ../system/objects/external-data-source-example.rst:215 -msgid "Example: ``https://your_domain.com/q=#{ticket.product}``" -msgstr "" - -#: ../system/objects/external-data-source-example.rst:217 -msgid "In the example, the parameter means:" -msgstr "" - -#: ../system/objects/external-data-source-example.rst:219 -msgid "``#{}``: \"Frame\" for the insertion of information" +"Please ensure to note down the password provided - you won't have access to " +"it afterwards." msgstr "" -#: ../system/objects/external-data-source-example.rst:220 -msgid "``ticket``: object level, where you create your custom object" +#: ../system/integrations/elasticsearch.rst:None +msgid "Screencast showing activation of Elasticsearch integration" msgstr "" -#: ../system/objects/external-data-source-example.rst:221 -msgid "``product``: name of the (custom) object" +#: ../system/integrations/elasticsearch.rst:51 +msgid "Connection Settings" msgstr "" -#: ../system/objects/external-data-source-example.rst:223 +#: ../system/integrations/elasticsearch.rst:53 msgid "" -"After configuring your *Link template*, there will be another column in the " -"preview. Hovering on the icons in the *Link* column will show you where it " -"forwards you." +"This section holds the most important general information for accessing your " +"Elasticsearch indexes - such as:" msgstr "" -#: ../system/objects/external-data-source-example.rst:232 -msgid "" -"In our example, one of the links looks like: https://your_domain.com/q=6, " -"where the 6 is the product id." +#: ../system/integrations/elasticsearch.rst:57 +msgid "A unique subdomain that does not tell your real instance URL." msgstr "" -#: ../system/objects/external-data-source-example.rst:235 -msgid "You can find more information regarding the URL in :doc:`types`." +#: ../system/integrations/elasticsearch.rst:61 +msgid "Software" msgstr "" -#: ../system/objects/includes/adding-values-hint.include.rst:3 +#: ../system/integrations/elasticsearch.rst:60 msgid "" -"Adding values can be tricky for first timers, don't forget to press \"➕ " -"Add\" after typing your values. Otherwise you may loose a value." -msgstr "" - -#: ../system/objects/includes/reposition-treeselect-values.include.rst:1 -#: ../system/objects/includes/reposition-values.include.rst:1 -msgid "**↕️ This field type allows the positioning of its values ↔️**" +"The major version of the search index being used. This is required by some " +"Reporting tools like Grafana." msgstr "" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:3 -msgid "" -"In order to re-arrange the field values, first edit the field. Then you can " -"use ☰ to drag the values in question to the correct position. If you want to " -"change the layer depth, double click on ☰. With it you can cycle through the " -"available layers." +#: ../system/integrations/elasticsearch.rst:64 +msgid "Authentication" msgstr "" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:8 -msgid "When you're ready, submit your changes to save the object attribute." +#: ../system/integrations/elasticsearch.rst:64 +msgid "The authentication type being supported. ``Basic Authentication``" msgstr "" -#: :0 ../system/objects/types.rst:0 -msgid "" -"Screencast showing how to re-position values on tree select like\n" -"fields" +#: ../system/integrations/elasticsearch.rst:67 +msgid "Available Indexes" msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:3 +#: ../system/integrations/elasticsearch.rst:69 msgid "" -"In order to re-arrange the field values, edit the field and scroll below the " -"values. Make sure to tick the option \"Use custom option sort\"." +"Within this section we're displaying the -in our opinion- most important " +"indexes for a Zammad instance." msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:8 +#: ../system/integrations/elasticsearch.rst:72 msgid "" -"If you do not tick this field, all manual positioning you did above will be " -"lost upon saving! ☠️" +"If you require all indexes or our listing is not good enough for you, point " +"your browser to the URL we're providing and append ``/_aliases?" +"pretty=true``. The result should look like this: ``https://.zammad.com/" +"_aliases?pretty=true``." msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:11 +#: ../system/integrations/elasticsearch.rst:77 msgid "" -"Now use ☰ to drag the values in question to the correct position. When " -"you're ready, submit your changes to save the object attribute." +"Your browser will automatically ask for your credentials - you'll then see " +"something like this:" msgstr "" -#: :0 ../system/objects/types.rst:0 -msgid "Screencast showing how to re-position values" +#: ../system/integrations/elasticsearch.rst:125 +msgid "Credentials" msgstr "" -#: ../system/objects/includes/url-template-hint.include.rst:3 +#: ../system/integrations/elasticsearch.rst:127 msgid "" -"This field allows using :ref:`URL fields (Link Templates) `." -msgstr "" - -#: ../system/objects/permissions.rst:2 -msgid "Attribute Permissions" +"Within this section Zammad displays your available users. The password is " +"provided once (upon activation) and cannot be retrieved after that." msgstr "" -#: ../system/objects/permissions.rst:7 +#: ../system/integrations/elasticsearch.rst:131 msgid "" -"In the object attributes configuration you can define if a field is shown " -"and if the input in the field is mandatory, separated by different screens " -"and for different :doc:`roles/permissions `." +"If you need to change or reset your Elasticsearch user password, use the " +"\"Reset password\" button in the credentials table. Doing so creates a brand " +"new password for the account in question. This change is immediate, keep in " +"mind that this may affect third party tools connected to your instance." msgstr "" -#: ../system/objects/permissions.rst:17 -msgid "Screenshot shows object attribute permission table" +#: ../system/integrations/exchange.rst:2 +msgid "Exchange" msgstr "" -#: ../system/objects/permissions.rst:17 +#: ../system/integrations/exchange.rst:4 msgid "" -"Some of the possible permissions and screen options for a user object " -"attribute." +"With Zammad's Exchange integration, you can easily use existing address " +"books without having to update more than one source." msgstr "" -#: ../system/objects/permissions.rst:19 +#: ../system/integrations/exchange.rst:7 msgid "" -"Based on the object context (ticket, agent, organization, user), the " -"selectable roles (to be precise: the required permissions) and screens " -"differ. Be aware that these settings aren't affecting data creation via " -"other channels than the UI." +"However, you should refrain from syncing all addresses, as the results may " +"not be what you expect (Exchange collects huge amounts of addresses). A " +"central address book of your company to sync makes more sense, as you can " +"ensure that Zammad gets only the data you need and want. Apart from this, it " +"is even not possible to sync the Global Address List (GAL) of your Exchange " +"system with Zammad." msgstr "" -#: ../system/objects/permissions.rst:24 +#: ../system/integrations/exchange.rst:16 msgid "" -"If you want to have further customization possibilities, you should have a " -"look at the :doc:`core workflows `." -msgstr "" - -#: ../system/objects/permissions.rst:28 -msgid "Screens" +"**Exchange and LDAP:** The exchange sync can be overruled by Zammad's LDAP " +"integration. If you have the same users in both sources, the LDAP version " +"will always be Zammad's pick." msgstr "" -#: ../system/objects/permissions.rst:30 +#: ../system/integrations/exchange.rst:19 msgid "" -"In the table below you can find an overview about the different permissions " -"and the available screens Zammad distinguishes between." -msgstr "" - -#: ../system/objects/permissions.rst:37 -msgid "Screen" -msgstr "" - -#: ../system/objects/permissions.rst:38 -msgid "Available for" -msgstr "" - -#: ../system/objects/permissions.rst:40 -msgid "create" -msgstr "" - -#: ../system/objects/permissions.rst:41 ../system/objects/permissions.rst:52 -#: ../system/objects/permissions.rst:59 ../system/objects/permissions.rst:73 -msgid "admin.user" -msgstr "" - -#: ../system/objects/permissions.rst:42 ../system/objects/permissions.rst:53 -#: ../system/objects/permissions.rst:60 -msgid "admin.organization" -msgstr "" - -#: ../system/objects/permissions.rst:43 ../system/objects/permissions.rst:54 -#: ../system/objects/permissions.rst:61 -#, fuzzy -msgid "admin.group" -msgstr "grupa" - -#: ../system/objects/permissions.rst:44 -msgid "Creation dialog for not yet existing data" -msgstr "" - -#: ../system/objects/permissions.rst:45 -msgid "create_middle" +"**One way sync:** the Exchange sync is one way. Exchange => Zammad. Changes " +"to your users inside of Zammad might be overwritten by the Exchange sync." msgstr "" -#: ../system/objects/permissions.rst:46 ../system/objects/permissions.rst:50 -#: ../system/objects/permissions.rst:57 ../system/objects/permissions.rst:66 -#: ../system/objects/permissions.rst:70 -#, fuzzy -msgid "ticket.customer" -msgstr "Makra" - -#: ../system/objects/permissions.rst:47 ../system/objects/permissions.rst:51 -#: ../system/objects/permissions.rst:58 ../system/objects/permissions.rst:69 -#, fuzzy -msgid "ticket.agent" -msgstr "Makra" - -#: ../system/objects/permissions.rst:48 -msgid "Ticket create dialog (middle section)" +#: ../system/integrations/exchange.rst:24 +msgid "" +"To configure Exchange integration, simply go to the System > Integrations > " +"Exchange in the admin panel. Press \"change\" and follow the wizard for " +"adding the needed Exchange information to Zammad. On the last two steps " +"Zammad will ask you for the address book(s) and your desired attribute " +"mapping. By default, Zammad only maps email address, first- and lastname. " +"Technically, you can map any Exchange object to a Zammad user object (this " +"also works for custom objects!)." msgstr "" -#: ../system/objects/permissions.rst:49 -msgid "edit" +#: ../system/integrations/exchange.rst:35 +msgid "" +"If the SSL verification fails while connecting to Exchange, Zammad will ask " +"you to turn it off temporarily." msgstr "" -#: ../system/objects/permissions.rst:55 -msgid "Editing dialog for already existing data" +#: ../system/integrations/exchange.rst:38 +msgid "" +"Please be aware that **turning off SSL verification is a security risk**. It " +"should only be used temporarily or for testing purposes. If turned off, " +"there is no verification of the certificate, which means that every " +"presented certificate will be accepted." msgstr "" -#: ../system/objects/permissions.rst:56 -msgid "view" +#: ../system/integrations/exchange.rst:43 +msgid "" +"After pressing Continue, Zammad will check if the configuration is okay. You " +"can then enable Exchange and start your first sync. The sync will then run " +"hourly - if you need to change mappings or the address book(s), you can " +"change the configuration at any time." msgstr "" -#: ../system/objects/permissions.rst:62 -msgid "View-only dialog for already existing data" +#: ../system/integrations/exchange.rst:50 +msgid "" +"After the sync has finished, you can find the new Exchange contacts under " +"\"Users\". Zammad integrates them just as normal users." msgstr "" -#: ../system/objects/permissions.rst:64 -msgid "(e.g. user or organization from search)" +#: ../system/integrations/exchange.rst:55 +msgid "" +"In some cases you might see unique IDs as \"Login\" instead of the email " +"address. This is normal and doesn't affect the login or email mapping for " +"that entry." msgstr "" -#: ../system/objects/permissions.rst:65 -msgid "signup" +#: ../system/integrations/github.rst:4 +msgid "" +"Use GitHub integration to track GitHub issues directly within Zammad " +"tickets. Add issue hyperlinks and get a live summary of metadata like status " +"(open/closed), assignee, labels, and more." msgstr "" -#: ../system/objects/permissions.rst:67 -msgid "Sign-up screen for new customers" +#: ../system/integrations/github.rst:8 +msgid "Please note that our GitHub integration does not support pull requests." msgstr "" -#: ../system/objects/permissions.rst:68 -msgid "invite_customer" +#: ../system/integrations/github.rst:None +msgid "Integration page for GitHub" msgstr "" -#: ../system/objects/permissions.rst:71 +#: ../system/integrations/github.rst:18 msgid "" -"Customer invitation screen (from :doc:`First Steps ` area)" +"In your GitHub settings, create a new API token under **Developer settings > " +"Personal access tokens > Generate new token**. Leave the **Scopes** section " +"empty." msgstr "" -#: ../system/objects/permissions.rst:72 -msgid "invite_agent" +#: ../system/integrations/github.rst:0 ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to create a new API token" msgstr "" -#: ../system/objects/permissions.rst:74 -msgid "" -"Agent invitation screen (from :doc:`First Steps ` area)" +#: ../system/integrations/github.rst:27 +msgid "Create a new API key with no scopes/privileges." msgstr "" -#: ../system/objects/permissions.rst:78 -msgid "Screen Options" +#: ../system/integrations/github.rst:29 +msgid "🔒 **Will this work for private repos?**" msgstr "" -#: ../system/objects/permissions.rst:80 +#: ../system/integrations/github.rst:31 msgid "" -"For the different screens you can select \"show\" and \"required\" options." -msgstr "" - -#: ../system/objects/permissions.rst:82 -msgid "**shown:** Show (check) or hide (uncheck) a field." +"No. To link private repo issues, **use the** ``repo`` **scope instead**. " +"Bear in mind that the resulting token will have `lots of permissions that it " +"doesn't actually need `_, which presents a security risk if your token ever falls into " +"the wrong hands." msgstr "" -#: ../system/objects/permissions.rst:83 +#: ../system/integrations/github.rst:37 msgid "" -"**required:** Set a field to mandatory (check). Forces users (via UI and " -"API) to populate the field." +"Unfortunately, because of how GitHub's OAuth token scopes are set up, this " +"is the only way to link issues on private repos." msgstr "" -#: ../system/objects/types.rst:7 -msgid "Example external data source" +#: ../system/integrations/github.rst:40 +msgid "Enter your new API token in Zammad and enable GitHub integration." msgstr "" -#: ../system/objects/types.rst:2 -msgid "Attribute types" +#: ../system/integrations/github.rst:0 +msgid "Screencast showing how to configure Zammad's GitHub integration" msgstr "" -#: ../system/objects/types.rst:4 +#: ../system/integrations/github.rst:47 msgid "" -"When adding a new object attribute, you can choose between the following " -"attribute types." +"Use the default API endpoint (``https://api.github.com/graphql``) unless " +"you're using GitHub Enterprise Server." msgstr "" -#: ../system/objects/types.rst:14 -msgid "" -"You cannot change the attribute format / type as soon as it is applied. If " -"you no longer need an object attribute, consider disabling it instead of " -"removing." +#: ../system/integrations/github.rst:50 +msgid "" +"Once completed, a new GitHub issues tab will appear in the ticket pane. 🎉" msgstr "" -#: ../system/objects/types.rst:18 -msgid "**What about the translation of my attributes?**" +#: ../system/integrations/github.rst:59 ../system/integrations/gitlab.rst:52 +msgid "Token verification is taking a long time" msgstr "" -#: ../system/objects/types.rst:20 +#: ../system/integrations/github.rst:56 ../system/integrations/gitlab.rst:49 msgid "" -"For some attribute types you can decide if they should be translatable or " -"not. To be precise, it works only for the selectable fields because the " -"possible choices are known and limited. For the following attribute types, " -"you can set the translatable flag:" +"Slight delays are normal (<2 min.), especially for systems under heavy load." msgstr "" -#: ../system/objects/types.rst:25 -msgid "*Boolean field*" +#: ../system/integrations/github.rst:58 +msgid "" +"Self-hosted administrators, please check your network settings to ensure " +"that your Zammad server can reach ``api.github.com``." msgstr "" -#: ../system/objects/types.rst:26 -msgid "*Single selection field*" +#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 +msgid "I reloaded the page and now the API token is gone" msgstr "" -#: ../system/objects/types.rst:27 -msgid "*Multiple selection field*" +#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 +msgid "" +"This may indicate that Zammad is still verifying your API token. Try " +"reloading the page again in a couple minutes." msgstr "" -#: ../system/objects/types.rst:28 -msgid "*Single tree selection field*" +#: ../system/integrations/gitlab.rst:2 +msgid "GitLab" msgstr "" -#: ../system/objects/types.rst:29 -msgid "*Multiple tree selection field*" +#: ../system/integrations/gitlab.rst:4 +msgid "" +"Use GitLab integration to track GitLab issues directly within Zammad " +"tickets. Add issue hyperlinks and get a live summary of metadata like status " +"(open/closed), assignee, labels, and more." msgstr "" -#: ../system/objects/types.rst:31 +#: ../system/integrations/gitlab.rst:8 msgid "" -"For these types, you can find an additional field *Translate field contents*:" +"Please note that our GitLab integration does not support merge requests." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Screenshot showing translatable attribute types" +#: ../system/integrations/gitlab.rst:None +msgid "Integration page for GitLab" msgstr "" -#: ../system/objects/types.rst:38 -msgid "Screenshot with example of translatable attribute type" +#: ../system/integrations/gitlab.rst:18 +msgid "" +"In your GitLab preferences, create a new API token under **Access Tokens**." msgstr "" -#: ../system/objects/types.rst:45 -msgid "Boolean field" +#: ../system/integrations/gitlab.rst:20 +msgid "Under **Select scopes**, choose ``read_api`` only." msgstr "" -#: ../system/objects/types.rst:41 -msgid "" -"Provides a drop-down field with display values for ``true`` and ``false``. " -"Setting a default is mandatory." +#: ../system/integrations/gitlab.rst:27 +msgid "🔒 **If you wish to link issues on any private repos...**" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Boolean fields" +#: ../system/integrations/gitlab.rst:29 +msgid "Your API token must belong to an account with access to those repos." msgstr "" -#: ../system/objects/types.rst:55 -msgid "Date field" +#: ../system/integrations/gitlab.rst:31 +msgid "Enter your new API token in Zammad and enable GitLab integration." msgstr "" -#: ../system/objects/types.rst:48 -msgid "Provides a date picker field and does not allow default values." +#: ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to configure Zammad's GitLab integration" msgstr "" -#: ../system/objects/types.rst:52 -msgid "Default time diff (hours)" +#: ../system/integrations/gitlab.rst:40 +msgid "" +"Use the default API endpoint (``https://gitlab.com/api/graphql``) unless " +"you're a self-hosted GitLab user." msgstr "" -#: ../system/objects/types.rst:51 +#: ../system/integrations/gitlab.rst:43 msgid "" -"This setting helps the user by highlighting the day from now plus the " -"provided value. It *does not* pre-fill the field." +"Once completed, a new GitLab issues tab will appear in the ticket pane. 🎉" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Date fields" +#: ../system/integrations/gitlab.rst:51 +msgid "" +"Self-hosted administrators, please check your network settings to ensure " +"that your Zammad server can reach ``gitlab.com``." msgstr "" -#: ../system/objects/types.rst:73 -msgid "Date & time field" +#: ../system/integrations/i-doit.rst:2 +msgid "i-doit" msgstr "" -#: ../system/objects/types.rst:58 -msgid "Provides a date and time picker – does not allow default values" +#: ../system/integrations/i-doit.rst:4 +msgid "" +"`i-doit `_ is an open-source **configuration " +"management database** - in other words, a tool for keeping tabs on every " +"single piece of your physical and digital infrastructure, from network " +"equipment to virtual machines on down to the faceplates on your rack shelves " +"and more." msgstr "" -#: ../system/objects/types.rst:62 -msgid "Allow future" +#: ../system/integrations/i-doit.rst:10 +msgid "" +"What's that got to do with Zammad? Well, if you used tickets to track issues " +"with all that hardware, you might start wishing there was a way they could " +"talk to each other." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Forbid dates and times in the future." +#: ../system/integrations/i-doit.rst:14 +msgid "Zammad gives you two:" msgstr "" -#: ../system/objects/types.rst:66 -msgid "Allow past" +#: ../system/integrations/i-doit.rst:17 +msgid "1. Add i-doit Links to Zammad Tickets" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Forbid dates and times in the past." +#: ../system/integrations/i-doit.rst:20 ../system/integrations/i-doit.rst:80 +msgid "What Users See" msgstr "" -#: ../system/objects/types.rst:70 -msgid "Default time diff (minutes)" +#: ../system/integrations/i-doit.rst:26 +msgid "i-doit integration in Zammad's ticket pane" msgstr "" -#: ../system/objects/types.rst:69 +#: ../system/integrations/i-doit.rst:26 msgid "" -"This setting helps the user by highlighting the day from now plus the " -"provided value. It does not pre-fill the field." +"The i-doit integration will appear under a new 🖨 tab in the ticket pane." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Date & time fields" +#: ../system/integrations/i-doit.rst:28 +msgid "" +"i-doit integration puts a new tab in Zammad's ticket pane where you can add " +"links to existing i-doit devices for easy reference. (See our :user-docs:" +"`user documentation ` to learn " +"how it works in practice)." msgstr "" -#: ../system/objects/types.rst:86 -msgid "Integer field" +#: ../system/integrations/i-doit.rst:36 ../system/integrations/i-doit.rst:93 +msgid "How to Set it Up" msgstr "" -#: ../system/objects/types.rst:76 +#: ../system/integrations/i-doit.rst:38 msgid "" -"Provides an input field that allows integer usage only. You may define a " -"default value. You cannot enforce comma separation." +"It requires i-doit's `API Add-on `_. Make sure to have it properly set up. Use the following setting:" msgstr "" -#: ../system/objects/types.rst:80 -msgid "Minimal" +#: ../system/integrations/i-doit.rst:42 +msgid "Active: ``Yes``" msgstr "" -#: ../system/objects/types.rst:80 -msgid "The minimal value the field accepts." +#: ../system/integrations/i-doit.rst:43 +msgid "Enforce authentication by username and password: ``No``" msgstr "" -#: ../system/objects/types.rst:83 -msgid "Maximal" +#: ../system/integrations/i-doit.rst:45 +msgid "" +"To set it up, enable the integration in the Zammad admin panel under " +"**System > Integrations > i-doit**:" msgstr "" -#: ../system/objects/types.rst:83 -msgid "The maximum value the field accepts." +#: ../system/integrations/i-doit.rst:None +msgid "i-doit settings within the integration pages" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Integer fields" +#: ../system/integrations/i-doit.rst:53 +msgid "The root URL of your i-doit installation." msgstr "" -#: ../system/objects/types.rst:99 -msgid "Multiple selection field" +#: ../system/integrations/i-doit.rst:62 +msgid "API token" msgstr "" -#: ../system/objects/types.rst:89 +#: ../system/integrations/i-doit.rst:56 msgid "" -"Provides a selection field that allows the selection of one or more out of " -"several. This field does allow setting a default value." +"Found in the i-doit admin panel under **Interfaces / external data > JSON-" +"RPC API > Common Settings**." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Multiple selection fields" +#: ../system/integrations/i-doit.rst:0 +msgid "i-doit administration interface with API configuration" msgstr "" -#: ../system/objects/types.rst:112 -msgid "Single selection field" +#: ../system/integrations/i-doit.rst:67 +msgid "Client ID" msgstr "" -#: ../system/objects/types.rst:102 +#: ../system/integrations/i-doit.rst:65 +msgid "A unique name to identify Zammad within i-doit." +msgstr "" + +#: ../system/integrations/i-doit.rst:67 +msgid "(Zammad does not require you to enter a value here, but i-doit might!)" +msgstr "" + +#: ../system/integrations/i-doit.rst:70 msgid "" -"Provides a drop-down field that allows selection of one value out of " -"several. This field does allow setting a default value." +"Here you can decide if the certificate of your i-doit system has to be " +"verified or not. In case you are using custom certificates, please have a " +"look at :doc:`how to add them to Zammad `." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Single selection fields" +#: ../system/integrations/i-doit.rst:77 +msgid "2. List / Create Zammad Tickets in i-doit" msgstr "" -#: ../system/objects/types.rst:142 -msgid "Textarea field" +#: ../system/integrations/i-doit.rst:None +msgid "Zammad integration in i-doit's device view" msgstr "" -#: ../system/objects/types.rst:115 +#: ../system/integrations/i-doit.rst:86 msgid "" -"Provides a text area input field (multiple lines) and thus allows e.g. new " -"lines. You can set a default field value." +"i-doit's ticket system integration gives you a way to see all the tickets " +"for a given device without ever leaving i-doit. (See our :user-docs:`user " +"documentation ` to learn how it " +"works in practice)." msgstr "" -#: ../system/objects/types.rst:120 +#: ../system/integrations/i-doit.rst:95 msgid "" -"Please note that this field *does not* support text formatting or HTML " -"content (rich text)." +"Enable this integration in the i-doit admin panel under **Interfaces / " +"external data > Trouble Ticket System (TTS) > Configuration**:" msgstr "" -#: ../system/objects/types.rst:123 -msgid "**🥵 This field can consume a lot of visual space**" +#: ../system/integrations/i-doit.rst:None +msgid "i-doit administration interface with TTS configuration" msgstr "" -#: ../system/objects/types.rst:125 -msgid "" -"Depending on where you use this field type, it may use a lot of visual space " -"if you provide a lot of text. This may be an issue to work with." +#: ../system/integrations/i-doit.rst:104 +msgid "TTS-Type" msgstr "" -#: ../system/objects/types.rst:130 -msgid "Default" +#: ../system/integrations/i-doit.rst:104 +msgid "``Zammad``" msgstr "" -#: ../system/objects/types.rst:129 -msgid "" -"The here provided text will be shown within the text area field or new data " -"sets." +#: ../system/integrations/i-doit.rst:115 +msgid "Username / Password" msgstr "" -#: ../system/objects/types.rst:134 ../system/objects/types.rst:160 -msgid "Maxlength" +#: ../system/integrations/i-doit.rst:107 +msgid "Login credentials for a Zammad agent." msgstr "" -#: ../system/objects/types.rst:0 ../system/objects/types.rst:160 -msgid "You can pick the maximum length of the field." +#: ../system/integrations/i-doit.rst:109 +msgid "" +"This agent must have **read permission** for all :doc:`groups ` that plan on using the i-doit integration." msgstr "" -#: ../system/objects/types.rst:0 -msgid "The default length of this object is ``500``." +#: ../system/integrations/i-doit.rst:113 +msgid "" +"You may even wish to create a dedicated agent account just for this " +"integration (otherwise, if the agent ever changes her password, you will " +"have to remember to update it here)." msgstr "" -#: ../system/objects/types.rst:139 -msgid "Rows" +#: ../system/integrations/i-doit.rst:117 +msgid "URL incl. protocol" msgstr "" -#: ../system/objects/types.rst:0 -msgid "" -"Change the number of rows to dislay so that you can use only the space you " -"really need." +#: ../system/integrations/i-doit.rst:118 +msgid "``https://your.zammad.domain``" msgstr "" -#: ../system/objects/types.rst:0 -msgid "The default number of rows is ``4``." +#: ../system/integrations/index.rst:2 +msgid "Integrations" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Textarea fields" +#: ../system/integrations/index.rst:4 +msgid "" +"Zammad offers numerous integrations that add rich features to your instance." msgstr "" -#: ../system/objects/types.rst:165 -msgid "Text field" +#: ../system/integrations/index.rst:6 +msgid "We're still working on this part of our documentation, stay tight!" msgstr "" -#: ../system/objects/types.rst:145 -msgid "Provides a text field (one line) and allows choosing a default value." +#: ../system/integrations/index.rst:10 +msgid "Integrations for Phone Systems" msgstr "" -#: ../system/objects/types.rst:148 +#: ../system/integrations/index.rst:14 msgid "" -"Defines the type of the input field. This allows e.g. your browser to ensure " -"that you provide the specific type." +"Your VoIP provider or telephony system is not listed? Possibly your provider " +"supports Zammad by using the generic CTI - if you're unsure ask your " +"provider." msgstr "" -#: ../system/objects/types.rst:152 -msgid "Currently available:" +#: ../system/integrations/index.rst:18 +msgid "" +"Provider does not support Zammad? Consider creating a `feature request in " +"the Zammad Community `_." msgstr "" -#: ../system/objects/types.rst:155 -msgid "Phone" +#: ../system/integrations/index.rst:31 +msgid "Integrations for Authentication and Customers" msgstr "" -#: ../system/objects/types.rst:156 -msgid "Text" +#: ../system/integrations/index.rst:44 +msgid "Integrations for Monitoring Systems" msgstr "" -#: ../system/objects/types.rst:157 -msgid "Url *(URL fields disable link-template availability)*" +#: ../system/integrations/index.rst:46 +msgid "This section currently misses the following integrations:" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Text fields" +#: ../system/integrations/index.rst:48 +msgid "Icinga" msgstr "" -#: ../system/objects/types.rst:174 -msgid "Single tree selection field" +#: ../system/integrations/index.rst:49 +msgid "Monit" msgstr "" -#: ../system/objects/types.rst:168 -msgid "" -"Provides a select-like field with up to 6 layers of options. Does not allow " -"setting a default value." +#: ../system/integrations/index.rst:50 +msgid "Nagios" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Tree Select fields" +#: ../system/integrations/index.rst:60 +msgid "Integrations for Issue Trackers" msgstr "" -#: ../system/objects/types.rst:183 -msgid "Multiple tree selection field" +#: ../system/integrations/index.rst:70 +msgid "Other Integrations" msgstr "" -#: ../system/objects/types.rst:177 +#: ../system/integrations/index.rst:72 msgid "" -"Provides a select-like field with up to 6 layers of options allowing the " -"selection of multiple values. Does not allow setting a default value." +"This section will hold any other integration that can't be grouped up (yet)." msgstr "" -#: ../system/objects/types.rst:302 -msgid "External Data Source field" +#: ../system/integrations/ldap/index.rst:2 +msgid "LDAP / Active Directory" msgstr "" -#: ../system/objects/types.rst:186 +#: ../system/integrations/ldap/index.rst:4 msgid "" -"Provides a searchable field which fetches data from an external system. This " -"can be useful if you have data outside of Zammad and don't want to maintain " -"both data sources." +"Zammad comes with a powerful LDAP integration that allows you to have a " +"single source of truth. By this you reduce the number of login credentials " +"your user has to remember." msgstr "" -#: ../system/objects/types.rst:190 -msgid "The feature works as follows:" +#: ../system/integrations/ldap/index.rst:10 +msgid "" +"The LDAP source is also a perfect candidate for Zammad's :docs:`Kerberos " +"Single Sign-On ` but also works as addition " +"to other :doc:`/settings/security/third-party`." msgstr "" -#: ../system/objects/types.rst:192 -msgid "" -"Zammad sends a query with a search string (free text from agent or based on " -"a variable) in a pre-defined format (\"Search URL\") to an external system." +#: ../system/integrations/ldap/index.rst:None +msgid "Zammands LDAP management page" msgstr "" -#: ../system/objects/types.rst:195 -msgid "" -"This external system searches for matches and provides a response as a JSON " -"structure to Zammad." +#: ../system/integrations/ldap/index.rst:25 +msgid "📝 :doc:`manage`" msgstr "" -#: ../system/objects/types.rst:197 -msgid "" -"Zammad just looks for the defined list and value keys, reads the content and " -"displays the value to the user. There is no search on Zammad side." +#: ../system/integrations/ldap/index.rst:25 +msgid "Add, modify, remove or re-arrange your LDAP-Sources as needed." msgstr "" -#: ../system/objects/types.rst:201 -msgid "" -"The usage of a PostgreSQL database for Zammad is required. In any other " -"case, Zammad will hide the external data source type and you are not able to " -"use it. If you want to use this feature, consider to :docs:`migrate your " -"database `." +#: ../system/integrations/ldap/index.rst:30 +msgid "Before you continue, please note the following limitations." msgstr "" -#: ../system/objects/types.rst:205 -msgid "Currently, only ``GET`` is supported as request method." +#: ../system/integrations/ldap/index.rst:32 +msgid "Mapping / Synchronizing organizations is not possible" msgstr "" -#: ../system/objects/types.rst:206 +#: ../system/integrations/ldap/index.rst:36 msgid "" -"The data structure must be in JSON format and provide the objects in an " -"array." +"You may want to consider using domain based assignments to overcome this " +"issue. Learn more on :doc:`/manage/organizations/index`." msgstr "" -#: ../system/objects/types.rst:208 +#: ../system/integrations/ldap/index.rst:39 msgid "" -"The endpoint for the external data source has to support search. On Zammad " -"side, there is no search/logic implemented; however, you can define the " -"output key and value based on the result(s) from the response (which " -"provides already filtered content based on the search)." +"Zammad's LDAP sync is one way. Editing user settings or permissions may be " +"overwritten upon the next sync depending on your configuration." msgstr "" -#: ../system/objects/types.rst:212 -msgid "" -"If you receive more results as expected, your external data source search " -"may not work properly or the structure of the URL is not correct. You should " -"get in touch with a responsible person from the external system." +#: ../system/integrations/ldap/index.rst:41 +msgid "Nested groups are not supported." msgstr "" -#: ../system/objects/types.rst:217 -msgid "" -"Please have a look :doc:`at our example `, where you can find a possible configuration for a public " -"dummy endpoint." +#: ../system/integrations/ldap/index.rst:42 +msgid "Synchronizing user avatars from LDAP is not supported." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for external data source fields" +#: ../system/integrations/ldap/index.rst:43 +msgid "Unlike user filters, group filters cannot be changed." msgstr "" -#: ../system/objects/types.rst:242 -msgid "Search URL" +#: ../system/integrations/ldap/index.rst:44 +msgid "" +"When a user originates from an LDAP server, Zammad will try to verify the " +"login credentials against LDAP first - if this fails Zammad will check its " +"local database." msgstr "" -#: ../system/objects/types.rst:227 +#: ../system/integrations/ldap/index.rst:50 msgid "" -"Set your endpoint where Zammad fetches the data. Please make sure to include " -"a valid search :doc:`variable <../variables>` as an URL parameter. Example " -"for a free text search at user input: ``#{search.term}``" +"Users can have local passwords even if they're LDAP users! You can learn " +"more about user accounts in general on :doc:`/manage/users/index`." msgstr "" -#: ../system/objects/types.rst:232 +#: ../system/integrations/ldap/index.rst:54 msgid "" -"If in doubt, ask the responsible person for the external data source how " -"they expect the strucuture of the URL." +"When several LDAP sources contain the same user (meaning the same email " +"address), the user in question will be updated with every source configured. " +"*The last LDAP source will win.*" msgstr "" -#: ../system/objects/types.rst:236 +#: ../system/integrations/ldap/index.rst:58 msgid "" -"Depending on your search variable, the preview might work or not. The reason " -"is that the context might not be available and it is no bug." +"This is subject to change with `Issue 4109 `_ in the future." msgstr "" -#: ../system/objects/types.rst:239 +#: ../system/integrations/ldap/index.rst:60 msgid "" -"Please also make sure to use a variable which is available in your object " -"context. For example you won't be able to search for a ticket in a user " -"object context." +"Synchronization statistics currently affect *all* configured LDAP sources. " +"This also applies for newly added or updated sources." msgstr "" -#: ../system/objects/types.rst:252 -msgid "SSL Verification" +#: ../system/integrations/ldap/index.rst:63 +msgid "" +"This is subject to change with `Issue 4108 `_ in the future." msgstr "" -#: ../system/objects/types.rst:245 -msgid "Here you can switch the SSL verification to no." +#: ../system/integrations/ldap/index.rst:65 +msgid "" +"Zammad currently has limited fallback server support. You can workaround " +"this by providing several sources - however, ensure to have the exact same " +"configuration on your fallback." msgstr "" -#: ../system/objects/types.rst:249 +#: ../system/integrations/ldap/index.rst:69 msgid "" -"If your external data source system is using self signed certificates, " -"please have a look :doc:`here ` for " -"further information about how to handle them in Zammad, so you can keep the " -"SSL verification activated." +"This is subject to improve with `Issue 4107 `_ in the future." msgstr "" -#: ../system/objects/types.rst:258 -msgid "HTTP Authentication" +#: ../system/integrations/ldap/index.rst:76 +msgid "" +"This section holds all requests Zammad handled for all LDAP sources. These " +"entries can either contain synchronization information or logins " +"(authentication attempts via Zammad's login interface)." msgstr "" -#: ../system/objects/types.rst:255 +#: ../system/integrations/ldap/index.rst:80 msgid "" -"If your external data source requires an authentication, you can set it " -"here. You can leave it empty or choose between *Basic Authentication* or " -"*Authentication Token* (selecting one of the two methods leads to additional " -"fields where you can enter your credentials/token)." +"By clicking on any request, Zammad will provide even more information. The " +"provided information can be useful when something does not work as expected." msgstr "" -#: ../system/objects/types.rst:265 -msgid "Search result list key" +#: ../system/integrations/ldap/index.rst:85 +msgid "" +"Especially a LDAP synchronization can cause many log entries. The web " +"interface will always limit the number of shown entries to the last 50 " +"entries." msgstr "" -#: ../system/objects/types.rst:261 +#: ../system/integrations/ldap/index.rst:None msgid "" -"Defines the level in the JSON structure which provides the list with search " -"results. You can leave it empty, if the data is already provided as an " -"array. If you have to go deeper in the structure, you can provide a path " -"with ``.`` as separators, e.g. ``key.subkey.sub-sub-key``." +"Screencast showing LDAP integration log entries and a detail view on\n" +"an entry." msgstr "" -#: ../system/objects/types.rst:271 -msgid "Search result value key" +#: ../system/integrations/ldap/manage.rst:2 +msgid "Manage LDAP-Sources" msgstr "" -#: ../system/objects/types.rst:268 +#: ../system/integrations/ldap/manage.rst:6 msgid "" -"Defines the attribute in the structure in which your external data source " -"provides the *value* for your data. An example would be a product *number*. " -"If you have to go deeper in the structure, you can provide a path with ``.`` " -"as separators, e.g. ``key.subkey.sub-sub-key``." +"Please keep in mind all current limitations for the LDAP synchronization. " +"This will help to understand scopes of the following operations better." msgstr "" -#: ../system/objects/types.rst:277 -msgid "Search result label key" +#: ../system/integrations/ldap/manage.rst:65 +msgid "Add new source" msgstr "" -#: ../system/objects/types.rst:274 +#: ../system/integrations/ldap/manage.rst:10 msgid "" -"Defines the attribute in the structure in which your external data source " -"provides the *label* for your data. An example would be a product *name*. If " -"you have to go deeper in the structure, you can provide a path with ``.`` as " -"separators, e.g. ``key.subkey.sub-sub-key``." +"Using the *New Source* button allows you to add new LDAP sources to your " +"installation. You're not limited in the number of sources, however, keep in " +"mind that many sources will also take more time to synchronize." msgstr "" -#: ../system/objects/types.rst:280 +#: ../system/integrations/ldap/manage.rst:14 msgid "" -"In the preview area, you can find the following items (depending on your " -"configuration above):" +"You can choose between different encryption types, namely *SSL* and " +"*STARTTLS* or none of them (\"*No SSL*\"). If you choose *SSL* or " +"*STARTTLS*, Zammad will display an additional *SSL verification* option that " +"allows you to disable the verification, e.g. for self-signed SSL " +"certificates. You can also tell Zammad to use a different port by appending " +"``:`` to your hostname/IP." msgstr "" -#: ../system/objects/types.rst:283 +#: ../system/integrations/ldap/manage.rst:0 msgid "" -"**Error/hint message** (only if configuration is not complete): Zammad tells " -"you, if there is a problem and what you should change in your configuration." +"Screenshot of configuring a new LDAP source with SSL encryption and SSL " +"verification" msgstr "" -#: ../system/objects/types.rst:286 +#: ../system/integrations/ldap/manage.rst:26 msgid "" -"**Search field**: search for an existing attribute in the data source to get " -"a preview. This is required for the fields below to show up." +"New Source with SSL transport security enabled and certificate verification" msgstr "" -#: ../system/objects/types.rst:288 +#: ../system/integrations/ldap/manage.rst:30 msgid "" -"**Search result response** (only if configuration is not complete): here you " -"can find a syntax highlighted JSON preview of the response, based on the " -"search term you entered." +"Using an user filter can be a good idea if you only require a small subset " +"of your LDAP users in Zammad." msgstr "" -#: ../system/objects/types.rst:291 -msgid "" -"**Search result list** (only if *search result list key* is properly set): " -"output of the structure under the configured *search result list key*." +#: ../system/integrations/ldap/manage.rst:42 +msgid "This especially affects inactive users" msgstr "" -#: ../system/objects/types.rst:294 +#: ../system/integrations/ldap/manage.rst:34 msgid "" -"**Preview table** (when fully configured): Zammad shows you a table which " -"includes the found items based on the search string (value, label and " -"optional link). You can use this preview if you don't have the complete data " -"structure of the external system in mind." +"As every LDAP behaves differently on which attributes and how they are set, " +"Zammad doesn't care about any flags." msgstr "" -#: ../system/objects/types.rst:299 +#: ../system/integrations/ldap/manage.rst:37 msgid "" -"An example of a configured external data source field from agent perspective:" +"Users that no longer are returned by your LDAP source will automatically be " +"set to inactive. Zammad assumes that the user was deactivated." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Screencast showing the search for a product in a ticket" +#: ../system/integrations/ldap/manage.rst:41 +msgid "" +"Users will never be removed automatically! If you want to remove obsolete " +"users, use :doc:`/system/data-privacy`." msgstr "" -#: ../system/objects/types.rst:307 -msgid "URL fields (Link-Template)" +#: ../system/integrations/ldap/manage.rst:46 +msgid "Active Directory admins" msgstr "" -#: ../system/objects/types.rst:311 +#: ../system/integrations/ldap/manage.rst:45 msgid "" -"This function is restricted to Text, Select and External data source types " -"only." +"Active Directories are quite specific on how to filter for active users only " +"- please see the `Microsoft documentation `_ for more " +"information." msgstr "" -#: ../system/objects/types.rst:314 +#: ../system/integrations/ldap/manage.rst:51 msgid "" -"Link-Templates are an amazing way to dynamically generate URLs. They allow " -"you to integrate other systems better without having to manually copy data " -"from Zammad if possible." +"*Do not* manually write pathes of either LDAP attributes or groups. If " +"Zammad does not display them, it either cannot find them or you have a lot " +"of users that don't have the attributes populated." msgstr "" -#: ../system/objects/types.rst:320 +#: ../system/integrations/ldap/manage.rst:55 msgid "" -"Another great way of communicating with another system may be Zammad's :doc:" -"`Webhooks `." +"Zammad will always only return attributes that are filled - this reduces the " +"returned list of attributes greatly." msgstr "" -#: ../system/objects/types.rst:323 -msgid "" -"After filling a link-template enabled field, an URL icon will appear on its " -"right. Clicking on the icon opens a new tab." +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing how to add a new LDAP source" msgstr "" -#: ../system/objects/types.rst:328 +#: ../system/integrations/ldap/manage.rst:63 msgid "" -"Even though Zammad displays the link template within object edit and create " -"screens, the function is optional. It's only active if you populate the " -"field." +"If your LDAP system doesn't allow anonymous bind, Zammad detects it and " +"provides you an editable \"Base DN\" *text* field instead of a prefilled " +"*select* field." msgstr "" -#: ../system/objects/types.rst:333 -msgid "" -"What's the difference between URL and text fields with link template...?!" +#: ../system/integrations/ldap/manage.rst:81 +msgid "Review or edit existing source" msgstr "" -#: ../system/objects/types.rst:335 +#: ../system/integrations/ldap/manage.rst:68 msgid "" -"Both fields have different use cases. Use ``text`` type text fields when " -"ever you have a *static* url that requires dynamic parameters. If you " -"require a drag & drop like field that you can put in any URL, use ``URL`` " -"type text fields." +"Clicking on a LDAP source will provide a configuration and mapping overview." msgstr "" -#: ../system/objects/types.rst:340 +#: ../system/integrations/ldap/manage.rst:70 msgid "" -"The difference is easier to spot when comparing the fields directly, below " -"screencast shows the result - the dynamic approach uses existing values in " -"the moment of updating to built the URL - e.g. ``https://google.com/search?" -"q=cookies`` - while the URL approach uses the actual URL of the field - e.g. " -"``https://zammad.com``." +"If needed you can then use the *Change* button to update either the name, " +"active state or the whole configuration. If you're changing the whole " +"configuration, the dialogue will be identical to the source creation." msgstr "" -#: ../system/objects/types.rst:None +#: ../system/integrations/ldap/manage.rst:76 msgid "" -"Screencast showing the differents in between URL and text type fields with " -"actual values" +"Did your LDAP server change? Different LDAP servers have different " +"structures and default attributes. This causes the LDAP synchronization to " +"likely fail. Consider removing the affected source and re-add it." msgstr "" -#: ../system/objects/types.rst:352 -msgid "How does this work...?!" +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing the update of the source name." msgstr "" -#: ../system/objects/types.rst:354 +#: ../system/integrations/ldap/manage.rst:89 +msgid "Re-arrange LDAP source's order" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:84 msgid "" -"As an example, let's say you have an attribute called ``amazing_attribute`` " -"and you want to open a google search directly with the input from that field." +"You can change the synchronization order for each source at any time. Zammad " +"will synchronize the sources from top to bottom." msgstr "" -#: ../system/objects/types.rst:357 +#: ../system/integrations/ldap/manage.rst:0 msgid "" -"Providing the link-template field below allows you to do so: ``https://www." -"google.com/search?q=#{ticket.amazing_attribute}``" +"Screencasting showing how to change the source order by using\n" +"drag and drop." msgstr "" -#: ../system/objects/types.rst:362 +#: ../system/integrations/ldap/manage.rst:101 +msgid "Remove a source" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:92 msgid "" -"You can use any :doc:`Zammad variable ` as long as it's " -"available in the moment you need it." +"If you no longer need the a LDAP source or simply want to start over, you " +"can remove them at any time. This will not remove synchronized users, data " +"synchronized or permissions." msgstr "" -#: ../system/objects/types.rst:365 +#: ../system/integrations/ldap/manage.rst:98 msgid "" -"As a result, you are redirected to Google with a search for the value of the " -"attribute, if you click on the button in the ticket (as you can see in the " -"screencast above)." +"Not sure if you'd need the source later on? Set the source to inactive " +"instead of removing it - see *Review or edit existing source* for more." msgstr "" -#: ../system/packages.rst:2 -msgid "Packages" +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing how to remove LDAP sources." msgstr "" -#: ../system/packages.rst:4 -msgid "That's the package management-area." +#: ../system/integrations/pgp/index.rst:2 +msgid "PGP" msgstr "" -#: ../system/packages.rst:6 -msgid "Individual add-ons for Zammad can be installed and managed here." +#: ../system/integrations/pgp/index.rst:7 +msgid "" +"Pretty Good Privacy (PGP) is another method for secure email communication. " +"With PGP, you can exchange **signed** and **encrypted** messages with others." msgstr "" -#: ../system/sessions.rst:2 -msgid "Sessions" +#: ../system/integrations/pgp/index.rst:13 +#: ../system/integrations/smime/index.rst:17 +msgid "Signing" msgstr "" -#: ../system/sessions.rst:4 +#: ../system/integrations/pgp/index.rst:11 +msgid "is a proof that a message hasn't been manipulated on its way." +msgstr "" + +#: ../system/integrations/pgp/index.rst:13 msgid "" -"Sessions management allows reviewing currently known user sessions and " -"allows to end these. The session timeout is affected by :ref:" -"`security_session_timeout` configurations from security settings." +"In other words, it guarantees message **integrity** and **authenticity**." msgstr "" -#: ../system/sessions.rst:None -msgid "Screenshot showing Zammad's session management" +#: ../system/integrations/pgp/index.rst:19 +#: ../system/integrations/smime/index.rst:22 +msgid "Encryption" msgstr "" -#: ../system/sessions.rst:13 -msgid "Zammad will provide the following information:" +#: ../system/integrations/pgp/index.rst:16 +#: ../system/integrations/smime/index.rst:20 +msgid "" +"scrambles a message so that it can only be unscrambled by the intended " +"recipient." msgstr "" -#: ../system/sessions.rst:16 +#: ../system/integrations/pgp/index.rst:19 msgid "" -"The user account this session entry belongs to. It can be normal if a user " -"has several sessions in the list. This can be due to changed browser " -"information or if you use e.g. single sign on methods where the user does " -"not use the log off button." +"In other words, it guarantees message **privacy** and **data security**." msgstr "" -#: ../system/sessions.rst:22 -msgid "Browser" +#: ../system/integrations/pgp/index.rst:25 +msgid "Screenshot of ticket creation with encrypt and sign buttons" msgstr "" -#: ../system/sessions.rst:22 -msgid "The browser agent communicated to Zammad." +#: ../system/integrations/pgp/index.rst:25 +msgid "" +"Once PGP has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " +"appear in the ticket composer." msgstr "" -#: ../system/sessions.rst:40 -msgid "Location" +#: ../system/integrations/pgp/index.rst:28 +msgid "**Sign button not visible?**" msgstr "" -#: ../system/sessions.rst:25 +#: ../system/integrations/pgp/index.rst:30 msgid "" -"The anticipated location based on the users IP address. Depending on the IP " -"address the result shown may differ. This option depends on :doc:`/settings/" -"system/services`." +"Please note that the signing of emails is based on the outgoing email " +"account. That means you have to choose a group with a sender email account, " +"which has a private key assigned." msgstr "" - -#: ../system/sessions.rst:29 -msgid "The following information can be shown:" + +#: ../system/integrations/pgp/index.rst:35 +msgid "Handling of Keys" msgstr "" -#: ../system/sessions.rst:33 -msgid "IP address" +#: ../system/integrations/pgp/index.rst:36 +msgid "" +"To use the PGP function, you have to enable the integration (PGP) by " +"switching the toggle to *enabled*." msgstr "" -#: ../system/sessions.rst:32 +#: ../system/integrations/pgp/index.rst:39 msgid "" -"Either if you set *Geo IP services* to inactive or you're using internal IP " -"address which do not provide location information." +"You can add keys by clicking the *add key* button. The keys can be imported " +"from a file or you can paste the content of the key in the text box." msgstr "" -#: ../system/sessions.rst:40 -msgid "Country (or Country + City)" +#: ../system/integrations/pgp/index.rst:42 +msgid "**Which keys do I have to import?**" msgstr "" -#: ../system/sessions.rst:36 +#: ../system/integrations/pgp/index.rst:44 msgid "" -"If *Geo IP services* is enabled only. Depends on how detailed the available " -"IP address information are." +"For **signing** *outgoing* emails, you have to import the private key of " +"your Zammad email account." msgstr "" -#: ../system/sessions.rst:39 +#: ../system/integrations/pgp/index.rst:47 msgid "" -"Be aware that results can be inaccurate - this technically is not an error." +"For **encrypting** *outgoing* emails, you have to import the public key of " +"the customer's email account." msgstr "" -#: ../system/sessions.rst:43 -msgid "Age" +#: ../system/integrations/pgp/index.rst:50 +msgid "" +"For **verifying the signature** of signed *incoming* emails, you have to " +"import the public key of the customer." msgstr "" -#: ../system/sessions.rst:43 -msgid "Provides the time when the session initially has been created." +#: ../system/integrations/pgp/index.rst:53 +msgid "" +"For **decrypting** of encrypted *incoming* emails, you have to import the " +"private key of your Zammad email account." msgstr "" -#: ../system/sessions.rst:50 -msgid "Update" +#: ../system/integrations/pgp/index.rst:57 +msgid "Import Keys From a File" msgstr "" -#: ../system/sessions.rst:46 -msgid "" -"Provides the time the user used this session to open Zammad. This timestamp " -"is only updated if the user e.g. reloads, not during normal work on tickets." +#: ../system/integrations/pgp/index.rst:58 +msgid "You can import keys from a file in the section **Upload key**:" msgstr "" -#: ../system/sessions.rst:50 -msgid "This timestamp is being used for the session timeout." +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of adding a key via file" msgstr "" -#: ../system/sessions.rst:53 +#: ../system/integrations/pgp/index.rst:64 msgid "" -"Use the delete button to remove a single session on behalf of your user." +"**Supported file formats:** ASCII-armor as well as binary GPG format " +"(basically any GPG supported key format) is supported here." msgstr "" -#: ../system/subscription/billing.rst:2 -msgid "Billing" +#: ../system/integrations/pgp/index.rst:68 +msgid "Import Keys by Pasting the Content" msgstr "" -#: ../system/subscription/billing.rst:4 -msgid "" -"Within the billing tab you can control all billing relevant information like " -"invoices, billing address and the option to cancel your subscription." +#: ../system/integrations/pgp/index.rst:69 +msgid "You can also paste the key's content in the section **paste key**:" msgstr "" -#: ../system/subscription/billing.rst:33 -msgid "Billing information" +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of adding a key via pasting" msgstr "" -#: ../system/subscription/billing.rst:8 +#: ../system/integrations/pgp/index.rst:75 msgid "" -"All adjusted billing information below only affect future invoices. If your " -"invoice was issued wrong, please contact `our sales team `_." +"**Supported format:** Please note that only ASCII-armor is supported here." msgstr "" -#: ../system/subscription/billing.rst:14 -msgid "Billing address" +#: ../system/integrations/pgp/index.rst:78 +msgid "Deleting Keys" msgstr "" -#: ../system/subscription/billing.rst:13 +#: ../system/integrations/pgp/index.rst:79 msgid "" -"Provide your company address here, make sure to include the companies name " -"in case required. This address will be referenced on your invoice." +"If you want to delete a specific key, you can do it by clicking on the menu " +"in the *actions* column and select **delete**:" msgstr "" -#: ../system/subscription/billing.rst:18 -msgid "VAT ID" +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of deleting a key" msgstr "" -#: ../system/subscription/billing.rst:17 -msgid "" -"Provide your VAT ID here. If applicable your invoice will not contain German " -"VAT. Please make sure to pay the VAT in your country as required." +#: ../system/integrations/pgp/index.rst:88 +msgid "Downloading Keys" msgstr "" -#: ../system/subscription/billing.rst:27 -msgid "Billing Email Address" +#: ../system/integrations/pgp/index.rst:89 +msgid "" +"If you want to download your keys, you can do this as well via corresponding " +"action buttons. Depending on the key, you can choose wether you want to " +"download the private or the public key." msgstr "" -#: ../system/subscription/billing.rst:21 -msgid "" -"Usually the instance owner (the person that registered the instance) will " -"receive all emails including the invoices. In case you have your own billing " -"department, you can provide their email address here." +#: ../system/integrations/pgp/index.rst:95 +#: ../system/integrations/smime/manage-certificates.rst:76 +msgid "Default Behavior" msgstr "" -#: ../system/subscription/billing.rst:25 +#: ../system/integrations/pgp/index.rst:96 msgid "" -"All billing relevant information will then be sent to this email address." +"Here you can adjust on per group basis, if *sign* and *encryption* is on or " +"off by default. Please be aware, that agents can always override the setting " +"for each individual article." msgstr "" -#: ../system/subscription/billing.rst:27 -msgid "Invoices are sent as attachment (PDF) to this email address." +#: ../system/integrations/pgp/index.rst:None +msgid "Adjusting default behavior on per group basis" msgstr "" -#: ../system/subscription/billing.rst:29 +#: ../system/integrations/pgp/index.rst:107 msgid "" -"Don't forget to press the *Submit* button after you changed above settings." +"Here you can see the last actions regarding signing and encryption and if " +"they were successful." msgstr "" -#: ../system/subscription/billing.rst:0 -msgid "" -"Screenshot showing options for billing information within the\n" -"subscription menu" +#: ../system/integrations/pgp/index.rst:117 +msgid "**Sign button is not visible, but keys are imported.**" msgstr "" -#: ../system/subscription/billing.rst:70 -msgid "Payment history" +#: ../system/integrations/pgp/index.rst:115 +msgid "Did you choose a group in the ticket?" msgstr "" -#: ../system/subscription/billing.rst:36 +#: ../system/integrations/pgp/index.rst:116 msgid "" -"The payment history will display a history of all paid invoices. At this " -"point you can also download these in case you need them again." +"Did you import a private key for the email adress, which is used for " +"outgoing emails in the group?" msgstr "" -#: ../system/subscription/billing.rst:41 -msgid "" -"You will only find *paid* invoices here. Invoices that are to be billed are " -"not available before the payment is completed." +#: ../system/integrations/pgp/index.rst:122 +msgid "**How to obtain keys?**" msgstr "" -#: ../system/subscription/billing.rst:46 -msgid "Date" +#: ../system/integrations/pgp/index.rst:120 +msgid "" +"You can create them yourself! There are some good tutorials on the web on " +"how to create them. Providing keys to Zammad is a prerequisite to use the " +"PGP feature." msgstr "" -#: ../system/subscription/billing.rst:46 -msgid "Date of the invoice creation." +#: ../system/integrations/pgp/index.rst:127 +msgid "**It says a passphrase is needed, but I haven't got one.**" msgstr "" -#: ../system/subscription/billing.rst:49 -msgid "Amount" +#: ../system/integrations/pgp/index.rst:125 +msgid "" +"If the key is secured with a passphrase, you have to provide it for the " +"import in Zammad. It is possible that keys may have an empty passphrase. " +"However, this is *not* recommended." msgstr "" -#: ../system/subscription/billing.rst:49 -msgid "Invoice total including VAT if applicable." +#: ../system/integrations/pgp/index.rst:132 +msgid "**How do my customers get my new key?**" msgstr "" -#: ../system/subscription/billing.rst:52 +#: ../system/integrations/pgp/index.rst:130 msgid "" -"Contains contract period (monthly or yearly) and hosted plan for the " -"subscription period in question." +"You have to provide your **public** key in advance. Your customer also has " +"to configure PGP in their email workflow and import your public key. The " +"other way round, you have to get the public key of your customer and have to " +"import it to Zammad." msgstr "" -#: ../system/subscription/billing.rst:63 -msgid "Payment method / Service period" +#: ../system/integrations/slack.rst:2 +msgid "Slack" msgstr "" -#: ../system/subscription/billing.rst:56 -msgid "" -"Used bank account or credit card as well as the subscription period the " -"invoice is about." +#: ../system/integrations/slack.rst:4 +msgid "**⚠️ Deprecation warning ⚠️**" msgstr "" -#: ../system/subscription/billing.rst:61 +#: ../system/integrations/slack.rst:6 msgid "" -"It might happen that the invoice date and subscription period differ. This " -"is nothing to worry about, the subscription periods will be accounted later " -"on." -msgstr "" - -#: ../system/subscription/billing.rst:67 -msgid "Receipt" +"Zammad 7 will no longer support this dedicated Slack integration. It is " +"recommended to switch to :doc:`pre-defined webhooks ` instead. Existing Slack integrations should " +"be migrated manually before this feature is dropped." msgstr "" -#: ../system/subscription/billing.rst:66 +#: ../system/integrations/slack.rst:14 msgid "" -"Use the arrow to download the invoice in question. You can download all " -"available invoices any time you need to here!" +"In order to use this feature, please add a new Slack app to your Workspace. " +"The App you need is called ``Incoming WebHooks`` ." msgstr "" -#: ../system/subscription/billing.rst:0 -msgid "Screenshot showing payment history of a hosted instance" +#: ../system/integrations/slack.rst:18 +msgid "Why Do I Need This Feature?" msgstr "" -#: ../system/subscription/billing.rst:94 -msgid "Do you want to cancel your subscription?" +#: ../system/integrations/slack.rst:20 +msgid "" +"If you're already using Slack for your team communication, you'll love this " +"feature! Our Slack integration can push ticket notifications about the last " +"ticket article based on the following events:" msgstr "" -#: ../system/subscription/billing.rst:73 -msgid "" -"In case you no longer want to use Zammad's SaaS, you can cancel your " -"subscription by using the red *Yes, please cancel my subscription* button." +#: ../system/integrations/slack.rst:24 +msgid "on Ticket creation" msgstr "" -#: ../system/subscription/billing.rst:76 -msgid "" -"Your subscription will end the day after your trial or billing period ends." +#: ../system/integrations/slack.rst:25 +msgid "on Ticket updates" msgstr "" -#: ../system/subscription/billing.rst:80 -msgid "" -"We will remind you about your cancelled subscription several times up front. " -"After the subscription ended all instance data will be removed. A restore " -"*is not* possible after that point!" +#: ../system/integrations/slack.rst:26 +msgid "on reached reminders" msgstr "" -#: ../system/subscription/billing.rst:0 -msgid "Screencast showing how to cancel a subscription" +#: ../system/integrations/slack.rst:27 +msgid "a Ticket has escalated" msgstr "" -#: ../system/subscription/billing.rst:87 -msgid "**😖 Cancelled by accident?**" +#: ../system/integrations/slack.rst:28 +msgid "a Ticket is going to escalate" msgstr "" -#: ../system/subscription/billing.rst:89 +#: ../system/integrations/slack.rst:30 msgid "" -"You can always undo the cancellation via the *Yes, undo the cancellation of " -"my subscription* button up to the last subscription day!" +"Zammad will provide the Ticket title, a direct link to the Ticket, the event " +"type (creation, updated, escalation), the customer, time and the last " +"article that has triggered the notification." msgstr "" -#: ../system/subscription/billing.rst:0 +#: ../system/integrations/slack.rst:34 msgid "" -"Screenshot showing a red button to cancel the subscription\n" -"cancellation" +"This will give you further options, as you can see e.g. escalating tickets " +"that are assigned to an agent that's e.g. absent. You can interact faster, " +"as you might see problems earlier (or even before the problem gets one)." msgstr "" -#: ../system/subscription/index.rst:2 -msgid "Subscription (SaaS)" +#: ../system/integrations/slack.rst:38 +msgid "" +"If needed and wanted, you can even discuss directly about the topic before " +"sending an answer to the customer. Another possible use case would be a " +"agent monitoring new agents and their answers to tickets." msgstr "" -#: ../system/subscription/index.rst:4 -msgid "" -"The subscription settings page allows you to configure your instances " -"package and number of agents required." +#: ../system/integrations/slack.rst:44 +msgid "Configure the Integration" msgstr "" -#: ../system/subscription/index.rst:9 +#: ../system/integrations/slack.rst:46 msgid "" -"This setting section is only available for Hosted setups. If you're looking " -"for on premise support contracts, please see the `Zammad pricing page " -"`_." +"First of all, please go to your slack workspace - go to administration => " +"Manage Apps. If you don't have an app yet, you can simply add a new one - " +"just search for ``Incoming WebHooks`` and customize the app to your needs." msgstr "" -#: ../system/subscription/index.rst:20 +#: ../system/integrations/slack.rst:50 msgid "" -"The subscription section currently consists of two tabs: Plan & Billing. For " -"your overview we've divided those two tabs into independent sub pages:" +"Choose (or create) the channel Zammad should post it's information to and " +"press on \"Add Incoming WebHooks integration\". If you're ready, copy the " +"provided WebHook URL and go to your Zammad installation." msgstr "" -#: ../system/subscription/index.rst:25 -msgid ":doc:`💰 Subscription plan `" +#: ../system/integrations/slack.rst:56 +msgid "" +"You need administrative rights on the Slack Workspace. The link to the app " +"directory is normally ``https://[workspace-name].slack.com/apps`` ." msgstr "" -#: ../system/subscription/index.rst:24 +#: ../system/integrations/slack.rst:63 msgid "" -"Everything affecting your instance subscription functions like number of " -"agents, package and payment method." +"To configure the slack integration, log in to Zammad and go to Integrations " +"(System) => Slack in the admin panel." msgstr "" -#: ../system/subscription/index.rst:28 -msgid ":doc:`🧾 Subscription billing `" +#: ../system/integrations/slack.rst:66 +msgid "" +"Here you can choose on what evens Zammad should post information about a " +"ticket to your Slack channel. Next you need to device what groups shall be " +"affected by this, as anybody with access to that specific Slack channel can " +"read at least parts of the ticket this might be a privacy issue, if you " +"select the wrong groups. The username is simply the name that Zammad uses as " +"display name inside the Slack chat. The channel defines the Slack channel " +"the information is being posted in. As last option, you can set a custom " +"icon for posting to slack." msgstr "" -#: ../system/subscription/index.rst:28 +#: ../system/integrations/slack.rst:74 msgid "" -"Everything regarding billing address, invoices and account cancellation." +"When you're ready, just hit \"Submit\" and enable the integration. Zammad " +"will now post new ticket information based on the trigger you chose. Below " +"the options you have the recent log that shows the latest requests to Slack " +"for debugging if needed." msgstr "" -#: ../system/subscription/index.rst:33 -msgid "FAQ" +#: ../system/integrations/slack.rst:81 +msgid "" +"If you leave the Icon URL empty, Zammad will use the Zammad logo instead. " +"The icon should be a square PNG file." msgstr "" -#: ../system/subscription/index.rst:37 -msgid "I set up a trial account but am missing functions to test" +#: ../system/integrations/slack.rst:90 +msgid "" +"The following figure shows how it will look if you choose to receive updates " +"on created and updated tickets. On every post Zammad sends to the Slack " +"channel, you can create new threads to discuss about the new article." msgstr "" -#: ../system/subscription/index.rst:36 +#: ../system/integrations/slack.rst:96 msgid "" -"The trial instance is running within the professional package allowing up to " -"three agents." +"If you just want to keep track of soon escalating or already escalated " +"tickets, it will look the the following figure. Zammad changes the color in " +"front of the post so you can easily see the state of the ticket." msgstr "" -#: ../system/subscription/index.rst:40 -msgid "Can I change package within the trial?" +#: ../system/integrations/slack.rst:102 +msgid "" +"If you change the state, Zammad will also put information on what state the " +"ticket gets and (if pending state) the date until it pends. You'll also " +"recognize the color codes in front of posts on slack, as they are exact the " +"same the ticket state colors you'll see in Zammad!" msgstr "" -#: ../system/subscription/index.rst:40 -msgid "No. As soon as the package is changed the subscription begins." +#: ../system/integrations/smime/index.rst:2 +msgid "S/MIME" msgstr "" -#: ../system/subscription/index.rst:45 -msgid "What happens to my trial instance after the trial period ended?" +#: ../system/integrations/smime/index.rst:11 +msgid "" +"S/MIME is the most widely-supported method for secure email communication. " +"With S/MIME, you can exchange **signed** and **encrypted** messages with " +"others." msgstr "" -#: ../system/subscription/index.rst:43 +#: ../system/integrations/smime/index.rst:15 msgid "" -"Your instance will automatically be canceled for you. Please see *What " -"happens to my instance after it has been canceled?* for more." +"is proof that a message hasn't been tampered with or sent by an impersonator." msgstr "" -#: ../system/subscription/index.rst:58 -msgid "What happens to my instance after it has been canceled?" +#: ../system/integrations/smime/index.rst:17 +msgid "" +"In other words, it guarantees a message's **integrity** and **authenticity**." msgstr "" -#: ../system/subscription/index.rst:48 -msgid "That depends slightly on your instance state:" +#: ../system/integrations/smime/index.rst:22 +msgid "In other words, it guarantees **privacy** and **data security**." msgstr "" -#: ../system/subscription/index.rst:54 -msgid "Trial instance" +#: ../system/integrations/smime/index.rst:28 +msgid "Screencast demo of S/MIME features for both new tickets and replies" msgstr "" -#: ../system/subscription/index.rst:51 +#: ../system/integrations/smime/index.rst:28 msgid "" -"If you're still on trial, we will ice your instance and remind you once " -"again about your instance. We then will wait some days and remove your " -"instance from our system. This is the last time we will inform you by Email." +"Once S/MIME has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " +"appear in the ticket composer." msgstr "" -#: ../system/subscription/index.rst:58 -msgid "Paid instance" +#: ../system/integrations/smime/index.rst:32 +msgid ":doc:`🔪 Prerequisites `" msgstr "" -#: ../system/subscription/index.rst:57 +#: ../system/integrations/smime/index.rst:31 msgid "" -"If you're a paying customer and canceled your subscription, the instance " -"removal will take place the day after your last subscription day." +"New to S/MIME? This section helps you to find certificate providers and " +"points out Limitations." msgstr "" -#: ../system/subscription/index.rst:60 -msgid "Can removed instances be restored?" +#: ../system/integrations/smime/index.rst:35 +msgid ":doc:`📝 Manage Certificates `" msgstr "" -#: ../system/subscription/index.rst:61 -msgid "No. Once your instance has been removed, a restoration is not possible." +#: ../system/integrations/smime/index.rst:35 +msgid "Add and download certificates; configure group default behaviors." msgstr "" -#: ../system/subscription/plan.rst:2 ../system/subscription/plan.rst:38 -msgid "Plan" +#: ../system/integrations/smime/index.rst:38 +msgid ":doc:`😦 Troubleshooting `" msgstr "" -#: ../system/subscription/plan.rst:16 -msgid "Subscription" +#: ../system/integrations/smime/index.rst:38 +msgid "Took a wrong turn? About recent logs and common issues." msgstr "" -#: ../system/subscription/plan.rst:5 +#: ../system/integrations/smime/index.rst:43 msgid "" -"On the top of the subscription summary you'll find the number of used and " -"available (booked) agent seats. By using the *see more* link you can also " -"expand an agent list to see the currently configured active agents. This " -"list *does not* count accounts with admin permissions only." +"For more details on how S/MIME integration works on the agent side, see the :" +"user-docs:`user docs `." msgstr "" -#: ../system/subscription/plan.rst:0 -msgid "" -"Within subscription you can always see how many agents are still\n" -"available to add and who uses the seats." +#: ../system/integrations/smime/manage-certificates.rst:2 +msgid "Manage Certificates" msgstr "" -#: ../system/subscription/plan.rst:14 +#: ../system/integrations/smime/manage-certificates.rst:4 msgid "" -"Learn more on how to manage your agents in general :doc:`here `." +"S/MIME is **disabled by default**. Enable it to start adding certificates." msgstr "" -#: ../system/subscription/plan.rst:19 -msgid "" -"This section gives you an overview of the available plans and their " -"functions / limits. If you require a more detailed table, check our " -"`detailed pricing table `_ for more." +#: ../system/integrations/smime/manage-certificates.rst:10 +msgid "Dialogue to add new certificates or private keys" msgstr "" -#: ../system/subscription/plan.rst:23 +#: ../system/integrations/smime/manage-certificates.rst:10 msgid "" -"Your selection in this step will decide on the base agent price and e.g. " -"agent limits that might apply in the summary step." +"Manage certificates in the Admin Panel under **System > Integrations > S/" +"MIME**. Certificates may be pasted in as plain text or uploaded from a file." msgstr "" -#: ../system/subscription/plan.rst:26 -msgid "" -"The green *Selected* button will also tell you what plan you're currently in." +#: ../system/integrations/smime/manage-certificates.rst:14 +msgid "Add Certificate Data" msgstr "" -#: ../system/subscription/plan.rst:30 -msgid "" -"Trial instances are running at Professional with 3 agents. The plan cannot " -"be changed during the trial for technical reasons, if you require more " -"agents for testing, please contact `our sales team `_ with a reason for the raise request." +#: ../system/integrations/smime/manage-certificates.rst:36 +msgid "Add Certificate" msgstr "" -#: ../system/subscription/plan.rst:0 +#: ../system/integrations/smime/manage-certificates.rst:17 msgid "" -"Screenshot showing three available packages for a hosted Zammad\n" -"instance" -msgstr "" - -#: ../system/subscription/plan.rst:83 -msgid "Summary" +"Import public-key certificates for both your own organization and your " +"contacts." msgstr "" -#: ../system/subscription/plan.rst:41 +#: ../system/integrations/smime/manage-certificates.rst:19 msgid "" -"In this section you can adjust the settings of the previous selected plan." +"You can also add a bunch of certificates in one go by providing a single " +"file with all relevant certificates." msgstr "" -#: ../system/subscription/plan.rst:45 -msgid "" -"Note that upgrading (more agents, higher package) is always possible, " -"however, downgrading will only happen when your billing period renews." +#: ../system/integrations/smime/manage-certificates.rst:22 +msgid "🕵️ **ALWAYS verify certificates in-person or over the phone!**" msgstr "" -#: ../system/subscription/plan.rst:49 +#: ../system/integrations/smime/manage-certificates.rst:24 msgid "" -"Upgrading resets your billing period and existing credit will be deducted " -"from the new total." +"The whole point of signatures is to alert you when someone is trying to " +"pretend to be someone they're not. Never accept a certificate from someone " +"online without verifying it first." msgstr "" -#: ../system/subscription/plan.rst:58 -msgid "Billing cycle" +#: ../system/integrations/smime/manage-certificates.rst:28 +msgid "📇 **What about trusted certificate authorities?**" msgstr "" -#: ../system/subscription/plan.rst:53 +#: ../system/integrations/smime/manage-certificates.rst:30 msgid "" -"You can choose between either monthly or yearly billing. The price per agent " -"will be cheaper if you decide for yearly billing." +"In some cases (e.g. when dealing with large enterprises), you may be given a " +"certificate for an entire CA, rather than a single contact. Add it here to " +"trust *all* certificates issued by that CA." msgstr "" -#: ../system/subscription/plan.rst:56 +#: ../system/integrations/smime/manage-certificates.rst:35 msgid "" -"If you're still trying out things and are unsure of the right package for " -"your instance, you may want to choose monthly first and then upgrade to " -"yearly when you're sure." -msgstr "" - -#: ../system/subscription/plan.rst:66 -msgid "Plan: (Starter|Professional|Plus) - Agents" +"Commercial CAs can usually be verified online. Zammad does not include a " +"list of built-in, trusted CAs." msgstr "" -#: ../system/subscription/plan.rst:61 -msgid "Choose the number of agents you require for your instance." +#: ../system/integrations/smime/manage-certificates.rst:57 +msgid "Add Private Key" msgstr "" -#: ../system/subscription/plan.rst:63 +#: ../system/integrations/smime/manage-certificates.rst:39 msgid "" -"Keep in mind that some packages may have agent limits. Depending on the " -"previous chosen package, you won't be able to exceed specific agent numbers. " -"Also note that setting less agents than currently configured is not possible." -msgstr "" - -#: ../system/subscription/plan.rst:69 -msgid "Total" -msgstr "" - -#: ../system/subscription/plan.rst:69 -msgid "This will be the net total you're going to be billed." +"Once you've added a public-key certificate, you can import its matching " +"private key." msgstr "" -#: ../system/subscription/plan.rst:71 +#: ../system/integrations/smime/manage-certificates.rst:42 msgid "" -"By using the *Update subscription* button, the instance package will be " -"adjusted immediately. If you didn't provide a payment method yet, Zammad " -"will request you to provide one at this point." +"Private keys are for **your own organization only**; never ask your contacts " +"for their private keys." msgstr "" -#: ../system/subscription/plan.rst:77 +#: ../system/integrations/smime/manage-certificates.rst:0 msgid "" -"In case you're still within the trial period, this means that the trial will " -"be over immediately!" -msgstr "" - -#: ../system/subscription/plan.rst:80 -msgid "Down- or upgrading during the trial period *is not* possible." -msgstr "" - -#: ../system/subscription/plan.rst:0 -msgid "Screenshot showing payment options and a pricing summary" -msgstr "" - -#: ../system/subscription/plan.rst:99 -msgid "Payment method" -msgstr "" - -#: ../system/subscription/plan.rst:86 -msgid "You can pay via credit card or SEPA mandate." -msgstr "" - -#: ../system/subscription/plan.rst:91 -msgid "Credit card" +"S/MIME integration showing configured certificates and possible issues with " +"Logging" msgstr "" -#: ../system/subscription/plan.rst:89 +#: ../system/integrations/smime/manage-certificates.rst:50 msgid "" -"Simply follow the dialogue by clicking *authorize* and confirm -if required " -"by your bank- your consent to Zammad using your card for the payments." +"A note is displayed on certificates with a matching private key (see line 2)." msgstr "" -#: ../system/subscription/plan.rst:95 -msgid "SEPA" +#: ../system/integrations/smime/manage-certificates.rst:52 +msgid "📤 **Certificates and private keys must be uploaded separately.**" msgstr "" -#: ../system/subscription/plan.rst:94 +#: ../system/integrations/smime/manage-certificates.rst:54 msgid "" -"Provide the requested information of the bank account holder and update if " -"you're ready. You'll then receive an email with the SEPA mandate." +"If your certificate and private key are bundled together in the same file or " +"PEM block, import it twice (once using each button)." msgstr "" -#: ../system/subscription/plan.rst:97 -msgid "" -"Technically there's also the possibility to pay via invoice, however - this " -"method only applies to a fairly low number of instances. Please contact `our " -"sales team `_ for more information." +#: ../system/integrations/smime/manage-certificates.rst:57 +msgid "Please note that bulk imports of private keys are not possible." msgstr "" -#: ../system/translations.rst:2 -msgid "Translations" +#: ../system/integrations/smime/manage-certificates.rst:60 +msgid "Download Certificate Data" msgstr "" -#: ../system/translations.rst:4 +#: ../system/integrations/smime/manage-certificates.rst:62 msgid "" -"Translations of Zammad are processed centrally in our `Weblate instance " -"`_. This allows non-developers to review " -"and update translation texts of the language they actually speak." +"You can download the earlier provided certificates and private keys at any " +"time from your Zammad instance." msgstr "" -"Tłumaczenia Zammada są przetwarzane centralnie w naszej instancji `Weblate " -"`_. Dzięki temu osoby niebędące " -"programistami mogą przeglądać i aktualizować teksty tłumaczeń na język, " -"którym faktycznie mówią." -#: ../system/translations.rst:9 +#: ../system/integrations/smime/manage-certificates.rst:65 msgid "" -"Your language is in an incomplete translation state or has typos? Please " -"consider helping us in sorting this out! All you need is either a GitHub " -"account or to register directly in our instance." +"Please note that passphrase-protected private keys stay protected and when " +"you download them, you have to know the passphrase to use them after " +"downloading." msgstr "" -"Twój język jest w niekompletnym tłumaczeniu lub zawiera literówki? Prosimy o " -"pomoc w rozwiązaniu tego problemu! Wszystko czego potrzebujesz to konto " -"GitHub lub zarejestrować się bezpośrednio w naszej instancji." - -#: ../system/translations.rst:13 -msgid "" -"Did you know? This is also where the documentation translations are handled. " -"🤓" -msgstr "Czy wiedziałeś? Tutaj również odbywa się tłumaczenie dokumentacji. 🤓" -#: ../system/translations.rst:15 -msgid "" -"Have a look in our :docs:`contribution section ` in the system documentation to get started!" +#: ../system/integrations/smime/manage-certificates.rst:73 +msgid "Dialogue to download certificates or private keys" msgstr "" -"Aby rozpocząć, zajrzyj do naszej :docs:`sekcji wkładu ` w dokumentacji systemu!" -#: ../system/translations.rst:20 -msgid "Local Translations" -msgstr "Tłumaczenia lokalne" +#: ../system/integrations/smime/manage-certificates.rst:73 +msgid "Download stored certificates and their keys" +msgstr "" -#: ../system/translations.rst:22 -msgid "" -"Apart from these system translations, there's still local translations you " -"can manage. This is relevant if you added custom objects that require " -"translations or even custom states and priorities." +#: ../system/integrations/smime/manage-certificates.rst:78 +msgid "" +"The ticket composer will set all outgoing messages to **signed and " +"encrypted** by default (assuming the required certificates exist)." msgstr "" -#: ../system/translations.rst:None -msgid "Translation management screen within the admin menu" +#: ../system/integrations/smime/manage-certificates.rst:82 +msgid "These defaults can be modified on a per-group basis:" msgstr "" -#: ../system/translations.rst:31 -msgid "Updating Translations" +#: ../system/integrations/smime/manage-certificates.rst:None +msgid "Zammad allowing to choose the default behavior on per group basis" msgstr "" -#: ../system/translations.rst:33 +#: ../system/integrations/smime/manage-certificates.rst:89 msgid "" -"Because of how Zammad ships translations, the only way to update the system " -"translations is to update your Zammad installation. The benefit of this is " -"that you no longer need internet access during a Zammad upgrade as the " -"package has everything it requires already." +"Of course, agents can always manually change these settings on each email " +"they send out." msgstr "" -#: ../system/translations.rst:39 -msgid "Translation of Custom Objects" +#: ../system/integrations/smime/prerequisites.rst:4 +msgid "A certificate *and* private key for your own organization" msgstr "" -#: ../system/translations.rst:41 +#: ../system/integrations/smime/prerequisites.rst:6 msgid "" -"No problem at all! You can customize any translation locally, even if it is " -"not initially provided by the system." +"(Use this to ✒️ **sign outgoing messages** and 🔓 **decrypt incoming " +"messages**.)" msgstr "" -#: ../system/translations.rst:44 +#: ../system/integrations/smime/prerequisites.rst:9 msgid "" -"Translation is supported for a broad number of features, including but not " -"limited to custom:" +"Certificates belonging your contacts, or their issuing certificate authority " +"(CA)" msgstr "" -#: ../system/translations.rst:47 -msgid "Object Attributes" +#: ../system/integrations/smime/prerequisites.rst:11 +msgid "" +"(Use these to ✅ **verify incoming message signatures** and 🔒 **encrypt " +"outgoing messages**.)" msgstr "" -#: ../system/translations.rst:48 -#, fuzzy -msgid "Ticket Macros" -msgstr "Makra" - -#: ../system/translations.rst:49 -msgid "Ticket Overviews" +#: ../system/integrations/smime/prerequisites.rst:14 +msgid "🙋 **I'm new to S/MIME. Where can I get a certificate?**" msgstr "" -#: ../system/translations.rst:50 -#, fuzzy -msgid "Ticket Priorities" -msgstr "priorytet" - -#: ../system/translations.rst:51 -msgid "Ticket States" +#: ../system/integrations/smime/prerequisites.rst:16 +msgid "" +"The easiest way to get certificates is to buy an annual subscription through " +"a commercial CA, such as:" msgstr "" -#: ../system/translations.rst:54 -msgid "Customizing Translations" +#: ../system/integrations/smime/prerequisites.rst:19 +msgid "" +"`Sectigo (formerly Comodo) `_" msgstr "" -#: ../system/translations.rst:56 -msgid "" -"Within the translation screen, simply click on the **New Translation** " -"button." +#: ../system/integrations/smime/prerequisites.rst:20 +msgid "`Secorio `_" msgstr "" -#: ../system/translations.rst:None -msgid "New translation dialog" +#: ../system/integrations/smime/prerequisites.rst:21 +msgid "`GlobalSign `_" msgstr "" -#: ../system/translations.rst:62 -msgid "" -"In the dialog you can immediately enter the exact translation source (if you " -"know it) and your custom translation text for it and click **Submit**." +#: ../system/integrations/smime/prerequisites.rst:23 +msgid "(Zammad is not affiliated with these CAs in any way.)" msgstr "" -#: ../system/translations.rst:65 +#: ../system/integrations/smime/prerequisites.rst:25 msgid "" -"Alternatively, try to search for translation suggestions in the list below. " -"Selecting an item from the list will pre-fill the translation source for you " -"and then you can just enter your custom translation." +"You can also generate your own self-signed certificates, but the process is " +"complicated and usually 🙅 **involves extra work for your contacts**." msgstr "" -#: ../system/translations.rst:69 +#: ../system/integrations/smime/prerequisites.rst:29 msgid "" -"The target language will always default to your current language selection. " -"If you need to translate for a different language, simply change the " -"selection before submitting." +"Bear in mind that 🤝 **S/MIME only works if the other party is using it, too." +"**" msgstr "" -#: ../system/translations.rst:73 -msgid "" -"All your custom translations will show up in the overview table when added. " -"And they will even persist across Zammad updates!" +#: ../system/integrations/smime/prerequisites.rst:32 +msgid "Certificate and Private Key Checks on Upload" msgstr "" -#: ../system/translations.rst:76 +#: ../system/integrations/smime/prerequisites.rst:34 msgid "" -"Make sure to reload your browser if a translated string is not displayed." +"The certificate and public key validation is based on the ``X509v3`` " +"extensions." msgstr "" -#: ../system/translations.rst:80 -msgid "Reverting to Original Translations" +#: ../system/integrations/smime/prerequisites.rst:49 +msgid "Uploading a *client certificate*?" msgstr "" -#: ../system/translations.rst:82 -msgid "" -"If you want to revert a custom translation to original text, simply use the " -"appropriate action within the row of the overview table." +#: ../system/integrations/smime/prerequisites.rst:41 +msgid "The following attributes are required then:" msgstr "" -#: ../system/translations.rst:85 -msgid "" -"Depending on the type of the translation source, the action has a slightly " -"different name:" +#: ../system/integrations/smime/prerequisites.rst:39 +msgid "Subject Alternative Name (at least one email address has to be present)" msgstr "" -#: ../system/translations.rst:88 -msgid "**Reset** for customized system translations" +#: ../system/integrations/smime/prerequisites.rst:40 +msgid "Key Usage (``Digital Signature`` and/or ``Key Encipherment``)" msgstr "" -#: ../system/translations.rst:89 -msgid "**Remove** for customized local translations" +#: ../system/integrations/smime/prerequisites.rst:41 +msgid "Public key algorithm (either ``RSA`` or ``EC``)" msgstr "" -#: ../system/translations.rst:91 +#: ../system/integrations/smime/prerequisites.rst:43 msgid "" -"In both cases, the action will remove the customized translation after a " -"confirmation." +"The Extended Key Usage attribute is optional. If the certificate provides " +"the named attribute, than it must contain the value ``E-mail Protection``." msgstr "" -#: ../system/translations.rst:None -msgid "Screenshot showing the location of the Remove action" +#: ../system/integrations/smime/prerequisites.rst:46 +msgid "" +"Please note that any usable email adress has to be prefixed with ``email:`` " +"or ``rfc822:``." msgstr "" -#: ../system/translations.rst:99 -msgid "Inline Translations" +#: ../system/integrations/smime/prerequisites.rst:49 +msgid "The named public key algorithms are mandatory for private keys as well." msgstr "" -#: ../system/translations.rst:101 -msgid "" -"If you prefer a more hands-on approach, you can activate the inline or on-" -"screen translation feature by pressing ``ctrl`` + ``alt`` + ``t`` at any " -"time and on any screen." +#: ../system/integrations/smime/prerequisites.rst:54 +msgid "Uploading a *CA certificate*?" msgstr "" -#: ../system/translations.rst:105 +#: ../system/integrations/smime/prerequisites.rst:52 msgid "" -"All customizable translation texts will be highlighted for you on the " -"screen. Just click into the highlighted area and update the text in place." +"In the case of an uploaded CA certificate, providing the value ``CA:TRUE`` " +"in the attribute *Basic Contstraints*, the previously mentioned attributes " +"are not verified." msgstr "" -#: ../system/translations.rst:None -msgid "Inline translation mode activated for the Overview screen" +#: ../system/integrations/smime/prerequisites.rst:56 +msgid "" +"In general, the usage of any expired (``Not After``) or not yet valid (``Not " +"Before``) certificate is denied for outgoing emails." msgstr "" -#: ../system/translations.rst:112 -msgid "" -"When finished editing, simply press ``ctrl`` + ``alt`` + ``t`` again to " -"deactivate." +#: ../system/integrations/smime/prerequisites.rst:59 +msgid "Example certificate:" msgstr "" -#: ../system/translations.rst:117 +#: ../system/integrations/smime/prerequisites.rst:85 msgid "" -"Even though it's available on any screen, the inline translation feature " -"requires admin permissions. It works only for the current language " -"selection. If you need to translate a different language, first change the " -"language in your :user-docs:`profile settings `." +"Please note that Zammad will distrust senders by default. This means that " +"you're always required to provide certificate data, no matter if for signing " +"or encrypting." msgstr "" -#: ../system/variables.rst:2 -msgid "Variables" +#: ../system/integrations/smime/prerequisites.rst:89 +msgid "This is by design and can't be adjusted." msgstr "" -#: ../system/variables.rst:4 +#: ../system/integrations/smime/troubleshooting.rst:4 msgid "" -"Please note that this is just an overview of available variables. It might " -"be incomplete or variables might not be available within some functions. If " -"you're missing variables or are not sure if something is not working as " -"expected, feel free to ask over at the `Community `_." +"All of the system's latest S/MIME activity is displayed in the **Recent " +"Logs** section." msgstr "" -#: ../system/variables.rst:10 -msgid "" -"Variables can be called by typing ``::`` (just like text modules in the " -"frontend), as long as you're in a supported text field within the backend. " -"Zammad will display all variables being available within this context and " -"replace it to the variable as soon as you selected an entry." +#: ../system/integrations/smime/troubleshooting.rst:11 +msgid "Sample entries of in- and outgoing S/MIME related emails." msgstr "" -#: ../system/variables.rst:15 +#: ../system/integrations/smime/troubleshooting.rst:11 msgid "" -"You have an empty field which you referenced and it appears as ``-``? That's " -"currently working as designed - you might want to ensure that these fields " -"always have a value." +"Logs report the status and details of all mail, both incoming and outgoing, " +"that used signing/verification or encryption/decryption." msgstr "" -#: ../system/variables.rst:20 -msgid "Variable Categories" +#: ../system/integrations/smime/troubleshooting.rst:14 +msgid "" +"This log does **not** include email sent by :doc:`triggers ` or the :doc:`scheduler `. For those, check your " +"``production.log``." msgstr "" -#: ../system/variables.rst:31 -msgid "Wait, What About Custom Objects?" +#: ../system/integrations/smime/troubleshooting.rst:20 +msgid "Common Issues" msgstr "" -#: ../system/variables.rst:33 -msgid "" -"Good point! Of course, we can't predict what objects you might create, but " -"we can give you a hint on how to put the puzzle together to get your custom " -"values." +#: ../system/integrations/smime/troubleshooting.rst:30 +msgid "I received a signed/encrypted email before I set up S/MIME integration" msgstr "" -#: ../system/variables.rst:36 +#: ../system/integrations/smime/troubleshooting.rst:23 msgid "" -"For this, we'll talk about the inner part of the variable (so everything " -"within ``#{}``), please put the outer part around to have a valid variable. " -"The first part of the variable name consist of the object type. Currently " -"these are:" +"No problem. Once S/MIME has been enabled and the appropriate certificates " +"have been added, agents will be prompted to retry verification/decryption on " +"matching emails." msgstr "" -#: ../system/variables.rst:41 -msgid "Ticket (``ticket``)" +#: ../system/integrations/smime/troubleshooting.rst:0 +msgid "Screenshot of user prompt to retry decryption" msgstr "" -#: ../system/variables.rst:42 -msgid "User (``user``)" +#: ../system/integrations/smime/troubleshooting.rst:38 +msgid "The 🔒 **Encrypt** button is disabled" msgstr "" -#: ../system/variables.rst:43 -msgid "Organization (``organization``)" +#: ../system/integrations/smime/troubleshooting.rst:33 +msgid "Have you added the recipient's certificate?" msgstr "" -#: ../system/variables.rst:44 -msgid "Group (``group``)" +#: ../system/integrations/smime/troubleshooting.rst:34 +msgid "Are you sure the recipient's certificate is valid?" msgstr "" -#: ../system/variables.rst:46 -msgid "" -"The second part is the name of the object. This is the name you define " -"during object creation and can be found within the object menu at any time. " -"The first and second part of a variable is divided by a point, e.g.: " -"``ticket.number`` which will in total be ``#{ticket.number}``." +#: ../system/integrations/smime/troubleshooting.rst:35 +msgid "Have you checked your ``production.log`` for more details?" msgstr "" -#: ../system/variables.rst:51 +#: ../system/integrations/smime/troubleshooting.rst:37 msgid "" -"Now, in some situations it's possible that you'll need to use a third part. " -"The best example for such a situation would be a ``select`` or ``tree-" -"select`` field which will by default return the key value, not it's display " -"name. For this, just extend your variable with ``.value``. This will result " -"in ``#{ticket.select.value}``." +"If encryption doesn't work in the composer, it won't work in :doc:`triggers " +"` or the :doc:`scheduler ` either!" msgstr "" -#: ../system/variables.rst:60 -msgid "Using Translated Variables" +#: ../system/integrations/smime/troubleshooting.rst:42 +msgid "The ✅ **Sign** button is disabled" msgstr "" -#: ../system/variables.rst:62 +#: ../system/integrations/smime/troubleshooting.rst:41 msgid "" -"If you want to use a translated variable in triggers or schedulers, you can " -"extend the placeholder like this: ``#{t(ticket.state.name)}``. The ``t`` " -"tells Zammad to search for fitting translated strings. The used output " -"language is based on the system language of Zammad which you can set in the " -"admin panel under :doc:`/settings/branding` or based on the selected locale " -"in the trigger/scheduler edit dialog." +"Have you added **both the certificate and private key** for your " +"organization?" msgstr "" -#: ../system/variables.rst:69 +#: ../system/integrations/smime/troubleshooting.rst:42 msgid "" -"A possible use-case: you want to send your customers updates on tickets via " -"trigger or scheduler which should include the state of the ticket. Using the " -"default ``#{ticket.state.name}`` (without the translation flag ``t()``) " -"would lead to the output of the original (english) name of the state." +"Does the email address on the certificate match the email address of the " +"agent/group composing the email?" msgstr "" -#: ../system/variables.rst:75 -msgid "Date and Time Formatting" +#: ../system/integrations/smime/troubleshooting.rst:45 +msgid "Error: “Fingerprint already taken”" msgstr "" -#: ../system/variables.rst:77 -msgid "" -"The system (trigger/scheduler selected) locale and timezone predefines a " -"default format of date and timestamp. This format is customizable by using " -"the ``dt()`` method." +#: ../system/integrations/smime/troubleshooting.rst:45 +msgid "Are you sure you haven't added this certificate already?" msgstr "" -#: ../system/variables.rst:79 -msgid "The method arguments are as follows:" +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Error: “❌ invalid byte sequence in UTF-8”" msgstr "" -#: ../system/variables.rst:81 -msgid "The date or timestamp variable you want to format." +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Please ensure to provide PEM formatted certificate and keys." msgstr "" -#: ../system/variables.rst:82 -msgid "The output format string." +#: ../system/integrations/smime/troubleshooting.rst:49 +msgid "Did you check if the provided file is a valid certificate or key?" msgstr "" -#: ../system/variables.rst:83 -msgid "The timezone to apply (optional)." +#: ../system/integrations/zabbix.rst:2 +msgid "Zabbix Integration" msgstr "" -#: ../system/variables.rst:86 +#: ../system/integrations/zabbix.rst:5 msgid "" -"``#{dt(ticket.updated_at, \"%A %Y-%m-%d %H:%M in the office\", \"Europe/" -"Berlin\")}``" +"This guide describes how to integrate your Zabbix 5.4 installation with " +"Zammad using the Zabbix webhook feature. This guide will provide " +"instructions on setting up a media type, a user and an action in Zabbix." msgstr "" -#: ../system/variables.rst:87 -msgid "Monday, 2024-03-18 15:31 in the office" +#: ../system/integrations/zabbix.rst:12 +msgid "Zammad with enabled HTTP Token Authentication" msgstr "" -#: ../system/variables.rst:89 -msgid "" -"If you want to use our example, make sure to paste the string above without " -"formatting (``CTRL+Shift+v``), otherwise it won't work." +#: ../system/integrations/zabbix.rst:13 +msgid "Zabbix version 5.4 or higher" msgstr "" -#: ../system/variables.rst:93 -msgid "The following table lists available format directives:" +#: ../system/integrations/zabbix.rst:16 +msgid "Setting up a Zammad" msgstr "" -#: ../system/variables.rst:99 -msgid "Parameter" +#: ../system/integrations/zabbix.rst:18 +msgid "Enable **API Token Access** in Settings > System > API." msgstr "" -#: ../system/variables.rst:102 -msgid "``%Y``" +#: ../system/integrations/zabbix.rst:20 +msgid "" +"Create a **new user** for a Zabbix alerter with an **email address** and " +"create a personal user token with **ticket.agent** permissions." msgstr "" -#: ../system/variables.rst:103 -msgid "Year with 4 digits" +#: ../system/integrations/zabbix.rst:24 +msgid "Zabbix Webhook Configuration" msgstr "" -#: ../system/variables.rst:104 -msgid "Use ``%y`` for year with 2 digits" +#: ../system/integrations/zabbix.rst:27 +#, fuzzy +msgid "Create a Global Macro" +msgstr "Makra" + +#: ../system/integrations/zabbix.rst:29 +msgid "" +"Before setting up the **Webhook**, you need to setup the global macro " +"**{$ZABBIX.URL}**, which must contain the **URL** to the **Zabbix frontend**." msgstr "" -#: ../system/variables.rst:105 -msgid "``%m``" +#: ../system/integrations/zabbix.rst:33 +msgid "" +"In the **Administration** > **Media types** section, import the `Template`_." msgstr "" -#: ../system/variables.rst:106 -msgid "Month of year (as number with zero-padding)" +#: ../system/integrations/zabbix.rst:38 +msgid "Open the added **Zammad** media type and set:" msgstr "" -#: ../system/variables.rst:107 -msgid "Use ``%-m`` for month without zero-padding" +#: ../system/integrations/zabbix.rst:40 +msgid "**zammad\\_access\\_token** to the your **Personal User Token**" msgstr "" -#: ../system/variables.rst:108 -msgid "``%d``" +#: ../system/integrations/zabbix.rst:41 +msgid "" +"**zammad\\_url** to the **frontend URL** of your **Zammad** installation" msgstr "" -#: ../system/variables.rst:109 -msgid "Day of month (as number with zero-padding)" +#: ../system/integrations/zabbix.rst:43 +msgid "**zammad\\_customer** to your **Zammad user email**." msgstr "" -#: ../system/variables.rst:110 -msgid "Use ``%e`` for day without zero-padding" +#: ../system/integrations/zabbix.rst:44 +msgid "" +"**zammad\\_enable\\_tags** to **true** or **false** to enable or disable " +"trigger tags. **Important**: if you enable tag support, each tag is set with " +"a separate request." msgstr "" -#: ../system/variables.rst:111 -msgid "``%H``" +#: ../system/integrations/zabbix.rst:48 +msgid "" +"If you want to prioritize issues according to **severity** values in Zabbix, " +"you can define mapping parameters:" msgstr "" -#: ../system/variables.rst:112 -msgid "Hour of day in 24h notation with zero-padding" +#: ../system/integrations/zabbix.rst:51 +msgid "**severity\\_**: Zammad priority ID" msgstr "" -#: ../system/variables.rst:113 -msgid "Use ``%k`` for hour without zero-padding" +#: ../system/integrations/zabbix.rst:53 +msgid "Click the **Update** button to save the **Webhook** settings." msgstr "" -#: ../system/variables.rst:114 -msgid "``%I``" +#: ../system/integrations/zabbix.rst:55 +msgid "" +"To receive notifications in **Zammad**, you need to create a **Zabbix user** " +"and add **Media** with the **Zammad** type." msgstr "" -#: ../system/variables.rst:115 -msgid "Hour of day in 12h notation with zero-padding" +#: ../system/integrations/zabbix.rst:58 +msgid "" +"For **Send to**: enter any text, as this value is not used, but is required." msgstr "" -#: ../system/variables.rst:116 +#: ../system/integrations/zabbix.rst:61 msgid "" -"Use ``%l`` for hour without zero-padding and ``%p`` / ``%P`` for meridian " -"indicator" +"For more information, use the `Zabbix documentation `_." msgstr "" -#: ../system/variables.rst:117 -msgid "``%M``" +#: ../system/maintenance.rst:2 +msgid "Maintenance" msgstr "" -#: ../system/variables.rst:118 -msgid "Minute of hour" +#: ../system/maintenance.rst:4 +msgid "" +"Zammad comes with a maintenance mode that you can use for e.g. updating the " +"instance or changing settings while restricting availability and functions." msgstr "" -#: ../system/variables.rst:120 -msgid "``%S``" +#: ../system/maintenance.rst:13 +msgid "Mode" msgstr "" -#: ../system/variables.rst:121 -msgid "Second of Minute" +#: ../system/maintenance.rst:8 +msgid "The mode setting allows you to enable or disable the maintenance mode." msgstr "" -#: ../system/variables.rst:123 -msgid "``%A``" +#: ../system/maintenance.rst:10 +msgid "Defaults to *off*." msgstr "" -#: ../system/variables.rst:124 -msgid "Weekday name" +#: ../system/maintenance.rst:12 +msgid "" +"The maintenance mode will restrict access to administrative roles only. This " +"means agents and customers are logged off." msgstr "" -#: ../system/variables.rst:125 -msgid "Use ``%a`` for abbreviated name or ``%^A`` for uppercase name" +#: ../system/maintenance.rst:23 +msgid "@Login" msgstr "" -#: ../system/variables.rst:126 -msgid "``%B``" +#: ../system/maintenance.rst:16 +msgid "" +"This setting allows you to provide a login message within a green banner " +"above the login screen. Click into the green banner in the settings page to " +"adjust your message. To activate the message, activate the *@Login* setting." msgstr "" -#: ../system/variables.rst:127 -msgid "Month name" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing the default login message within the\n" +"settings page" msgstr "" -#: ../system/variables.rst:128 -msgid "Use ``%b`` for abbreviated name" +#: ../system/maintenance.rst:26 +msgid "" +"Send an informative message to **all active sessions**. This comes handy to " +"inform your agents e.g. about mayor outages or to force reloads after " +"configuration changes." msgstr "" -#: ../system/variables.rst:129 -msgid "``%U``" +#: ../system/maintenance.rst:31 +msgid "This is the messages title (slightly bigger than the normal message)." msgstr "" -#: ../system/variables.rst:130 -msgid "Week number of current year" +#: ../system/maintenance.rst:34 +msgid "The text you want to provide to your logged in sessions." msgstr "" -#: ../system/variables.rst:131 -msgid "Use ``%W`` for a different calculation method" +#: ../system/maintenance.rst:39 +msgid "Reload application" msgstr "" -#: ../system/variables.rst:134 +#: ../system/maintenance.rst:37 msgid "" -"We support the known format directives for the Ruby built-in method " -"``strftime`` of the ``DateTime`` class. For more information, see `here " -"`_." +"Selecting this option will change the message acceptance button from *Close* " +"(with nothing happening) to *Continue session*, which forces the application " +"to reload." msgstr "" -#: ../system/variables/article.rst:2 -msgid "Articles" +#: ../system/maintenance.rst:43 +msgid "" +"If you have customers that are logged in to Zammad, they'll also be notified " +"if they're active in that moment." +msgstr "" + +#: ../system/maintenance.rst:48 +msgid "Example without reload application" msgstr "" -#: ../system/variables/article.rst:4 ../system/variables/config.rst:4 -#: ../system/variables/current-user.rst:4 ../system/variables/ticket.rst:4 +#: ../system/maintenance.rst:52 msgid "" -"If you're missing variables or are not sure if something is not working as " -"expected, feel free to ask over at the `Community `_." +"Message setting within Zammad's admin settings without ticket reload " +"application setting." msgstr "" -#: ../system/variables/article.rst:6 +#: ../system/maintenance.rst:0 msgid "" -"Below you can find all available ticket article-based variables within " -"Zammad. These can be called via Triggers for example. If you're unsure if " -"Zammad does support variables at the point you're at, you can try to type " -"``::`` to check." +"Screenshot showing the send message settings without ticket\n" +"reload application set" msgstr "" -#: ../system/variables/article.rst:9 ../system/variables/config.rst:9 -#: ../system/variables/ticket.rst:9 +#: ../system/maintenance.rst:61 ../system/maintenance.rst:85 msgid "" -"The below list gives you an example what kind of data you can expect, it's " -"not intended to explain the data itself." +"The modal all other active sessions will see upon pressing *Send to clients*." msgstr "" -#: ../system/variables/article.rst:11 -msgid "Article Variables" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing modal caused by maintenance's message\n" +"without reload application ticket" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "name" +#: ../system/maintenance.rst:72 +msgid "Example with reload application" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "variable" +#: ../system/maintenance.rst:76 +msgid "" +"Message setting within Zammad's admin settings with ticket reload " +"application setting." msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "example" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing the send message settings with ticket\n" +"reload application set" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Web" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing modal caused by maintenance's message\n" +"with reload application ticket" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.web}``" +#: ../system/monitoring.rst:2 +msgid "Monitoring" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``https://zammad.com`` or empty if not set in user object" +#: ../system/monitoring.rst:4 +msgid "" +"This function is only available in self hosted instances. If you use Zammad " +"in our cloud, we are monitoring the system on our own and take steps to fix " +"potential problems directly." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > VIP" +#: ../system/monitoring.rst:11 +msgid "" +"On the monitoring page, you can see the current health state of Zammad under " +"\"*Current Status*\" at the bottom. This can be useful if you want to have a " +"look if everything is up and running. As an example, you could have a look " +"in the monitoring when you assume that some emails aren't processed from " +"Zammad." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.vip}``" +#: ../system/monitoring.rst:17 +msgid "**Can't receive an email and the monitoring response is \"healthy\"?**" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -msgid "``true`` or ``false``" +#: ../system/monitoring.rst:19 +msgid "" +"Zammad will just inform you about unprocessable emails. This is not the case " +"for oversized emails. You can adjust the maximum email size in :doc:`../" +"channels/email/settings`." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Phone" +#: ../system/monitoring.rst:24 +msgid "Monitoring API" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.phone}``" +#: ../system/monitoring.rst:26 +msgid "" +"Beside the indication in the monitoring page, you can also use an external " +"monitoring tool to monitor Zammad's health. To request the health of Zammad, " +"you need to provide the API key (token) to the external monitoring tool. You " +"can copy the token from the \"*Current Token*\" field as well as the whole " +"API endpoint of your system (\"*Health Check*\" field), in which the API " +"token is already included." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``+4930123456789`` or empty if not set in user object" +#: ../system/monitoring.rst:37 +msgid "Screenshot showing Current Token and Health Check" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Note" +#: ../system/monitoring.rst:37 +msgid "Screenshot showing Token and Health Check" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.note}``" +#: ../system/monitoring.rst:39 +msgid "" +"In addition to that, you can reset the auto-generated token to make sure " +"that already configured monitoring systems won't work anymore. So, please " +"use this \"*Reset*\" button only if you know what you do!" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Some note about user`` or empty if not set in user object" -msgstr "" +#: ../system/monitoring.rst:44 +#, fuzzy +msgid "Example Output" +msgstr "Przykład" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Mobile" +#: ../system/monitoring.rst:0 +msgid "No issues found" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.mobile}``" +#: ../system/monitoring.rst:48 ../system/monitoring.rst:60 +msgid "**Indicator in Zammad**:" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Login" +#: ../system/monitoring.rst:0 +msgid "Screenshot showing monitoring with no issues" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.login}``" +#: ../system/monitoring.rst:54 ../system/monitoring.rst:66 +msgid "**API response**::" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -#: ../system/variables/ticket.rst:1 -msgid "``jdoe``" +#: ../system/monitoring.rst:0 +msgid "Issues were found" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Lastname" +#: ../system/monitoring.rst:0 +msgid "Screenshot showing monitoring with issues" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.lastname}``" +#: ../system/objects.rst:2 +msgid "Objects" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -#: ../system/variables/ticket.rst:1 -msgid "``Doe`` or empty if not set" +#: ../system/objects.rst:4 +msgid "" +"In Zammad you can add your own fields to tickets, users, organizations and " +"even groups (these are called \"objects\"). This can be useful if you need " +"to add further information to a ticket or any other object in Zammad and the " +"information doesn't fit in any existing field." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Firstname" +#: ../system/objects.rst:11 +msgid "" +"Try to avoid deleting attributes (and disable them instead) as Zammad might " +"run into unexpected conditions if they are referenced somewhere." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.firstname}``" +#: ../system/objects.rst:16 +msgid "" +"Here's an overview of object attributes. On the upper right you can add new " +"attributes. By default, there will be no custom fields - standard attributes " +"will be grayed out, you can't delete or change those. You can edit custom " +"attributes (they are displayed in black font and have a trash bin on the " +"right side) just by clicking on them." msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "``Joe`` or empty if not set" +#: ../system/objects.rst:24 +msgid "" +"Attributes you add to Zammad, no matter if they have default values or not, " +"will not update existing information. This means a new ticket field " +"technically will be empty unless you populate it." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Fax" +#: ../system/objects.rst:28 +msgid "" +"Especially in ticket scope this also means that newly added attributes will " +"be indicated as \"changed\" to agents that view the ticket. This may " +"interfere with Zammad's tabs behavior." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.fax}``" +#: ../system/objects.rst:40 +msgid "Ordering Attributes" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Email" +#: ../system/objects.rst:42 +msgid "" +"Since Zammad introduced :doc:`/system/core-workflows` the need to have a " +"custom positioning for attributes has become more important than ever." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.email}``" +#: ../system/objects.rst:45 +msgid "" +"To adjust the position of such an attribute, simply click on the attribute " +"entry in question, scroll down and adjust the position number. Please note " +"that you cannot change the positioning of default attributes." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``jdoe@example.com``" +#: ../system/objects.rst:49 +msgid "" +"In case two attributes have the same position value, Zammad will sort " +"alphabetically by name automatically." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Department" +#: ../system/objects.rst:None +msgid "" +"Screenshot showing custom attribute entries ordered in between default ones" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.department}``" +#: ../system/objects.rst:56 +msgid "Updating Database After Adding or Editing Attributes" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Sales`` or empty if not set in user object" +#: ../system/objects.rst:58 +msgid "" +"When adding or changing attributes, Zammad will not apply the changes " +"instantly, but instead shows you the changed attributes first. If you're " +"ready to go, just click on \"Update database\" to apply the changes to " +"Zammad. If you made a mistake or just want to discard your changes, click " +"\"Discard changes\"." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Address" +#: ../system/objects.rst:64 +msgid "" +"After applying the changes with \"Update Database\", a restart of Zammad is " +"**mandatory**. If you don't perform it, you may experience unexpected " +"behavior or even errors. You may want to do this kind of configuration " +"during maintenance windows." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.address}``" +#: ../system/objects.rst:72 +msgid "" +"Changes on objects require you to update the database to apply these changes." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Some street 1, 12345 Berlin`` or empty if not set in user object" +#: ../system/objects.rst:75 +msgid "**🤓 Service restarts can be automated**" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated" +#: ../system/objects.rst:0 +msgid "Hosted environments automatically restart for you." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_at}``" +#: ../system/objects.rst:0 +msgid "" +"If you're using a self-hosted installation you can use :docs:`environment " +"variables `" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``2019-10-08 15:24:47 UTC``" +#: ../system/objects.rst:82 +msgid "System Attributes" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Type > Name" +#: ../system/objects.rst:84 +msgid "" +"Zammad comes with pre-configured attributes. Some of them can't be edited " +"via UI (or at all). This is required for proper operation of Zammad and not " +"a bug." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.type.name}``" +#: ../system/objects.rst:90 +msgid "Ticket State" msgstr "" -#: ../system/variables/article.rst:1 +#: ../system/objects.rst:92 msgid "" -"``email`` (`list of article types `_)" +"If the pre-configured states aren't enough for you or you want to change " +"them, you can do so by clicking on the cogwheel icon in the state row in the " +"ticket tab. But you should be careful when changing pre-configured states. " +"This can lead to unwanted behavior in some cases." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > To" +#: ../system/objects.rst:None +msgid "Screenshot showing highlighted ticket state attribute" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.to}``" +#: ../system/objects.rst:122 +msgid "Handling of states" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``helpdesk@example.com``" +#: ../system/objects.rst:102 +msgid "" +"In the state configuration screen, you can add new states, disable states or " +"change states." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > TicketID" +#: ../system/objects.rst:0 +msgid "Screenshot showing table of default ticket states" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.ticket_id}``" +#: ../system/objects.rst:110 +msgid "" +"To add a new state, click on the \"New Ticket State\" button in the top " +"right corner. To change an existing state, simply click on the affected " +"state. This opens an edit dialog." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``1`` (not ticket number)" +#: ../system/objects.rst:114 +msgid "" +"You can also clone a state or set them to \"Default for new tickets\" or " +"\"Default for follow-ups\" by clicking on the ⁝ action button and select the " +"desired function." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Subject" +#: ../system/objects.rst:118 +msgid "" +"*Default for new tickets* means that this state is used for every newly " +"created ticket." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.subject}``" +#: ../system/objects.rst:121 +msgid "" +"*Default for follow-ups* means that this state is used if the ticket is re-" +"opened after it was closed." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``My amazing subject``" +#: ../system/objects.rst:171 +msgid "Ticket state in detail" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Sender > Name" +#: ../system/objects.rst:125 +msgid "" +"Below you can find a description for each field and option. Please head over " +"to the :ref:`example ` to see the edit dialog." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.sender.name}``" +#: ../system/objects.rst:129 +msgid "" +"This is the name of the state and what you and your agents are seeing when " +"choosing a state somewhere (e.g. in tickets, trigger configuration)." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Customer``, ``Agent`` or ``System``" +#: ../system/objects.rst:137 +msgid "" +"There are different state types you can choose from. By default, Zammad " +"comes with one state per state type." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Visibility" +#: ../system/objects.rst:140 +msgid "" +"**new**: for states for tickets that are new and it hasn't been worked on " +"them" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.internal}``" +#: ../system/objects.rst:142 +msgid "" +"**open**: for states for tickets that are in progress and agents are working " +"on them" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``false`` or ``true`` (false if not internal)" +#: ../system/objects.rst:144 +msgid "**merged**: for states for tickets that are merged with other tickets" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > From" +#: ../system/objects.rst:145 +msgid "" +"**pending reminder**: for states for tickets that are in progress and you " +"want to set a reminder. (default example: *pending reminder*)" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.from}``" +#: ../system/objects.rst:147 +msgid "" +"**pending action**: for states for tickets that are waiting for a specified " +"time and then change their state (default example: *pending close*)" msgstr "" -#: ../system/variables/article.rst:1 +#: ../system/objects.rst:150 msgid "" -"``Joe Doe `` may differ, depends on ``FROM`` of send mail" +"**closed**: for states for tickets that are finished and do not need to be " +"processed further" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Web" +#: ../system/objects.rst:153 +msgid "" +"⚠️ Choosing the correct state type is important! If you are in doubt, have a " +"look on the default states and their types!" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.web}``" +#: ../system/objects.rst:158 +msgid "Ignore escalation" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > VIP" +#: ../system/objects.rst:157 +msgid "" +"Here you can define whether tickets of this state will count to escalation " +"time or not." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.vip}``" +#: ../system/objects.rst:161 +msgid "" +"You can create a note for the state to inform other admins about the state. " +"This has no effect on tickets." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Phone" +#: ../system/objects.rst:165 +msgid "Set the state to *active* or *inactive*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.phone}``" +#: ../system/objects.rst:167 +msgid "" +"it is technically possible to set all states to inactive. To keep Zammad " +"working in such a case, the inactive flag of one of the states is ignored." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Note" +#: ../system/objects.rst:194 +msgid "Ticket state example" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.note}``" +#: ../system/objects.rst:174 +msgid "" +"Let's assume we want to create a new state which indicates that the ticket " +"has to wait for a response of a third party (e.g. service contractor or " +"manufacturer) and we want to to be able to set a reminder." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Mobile" +#: ../system/objects.rst:178 +msgid "" +"First we give the new state a proper name. In this example we call it " +"\"waiting for manufacturer\"." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.mobile}``" +#: ../system/objects.rst:181 +msgid "" +"As state type we choose \"pending reminder\". This indicates that the ticket " +"is still open and we can set a reminder. This reminder can be useful if our " +"manufacturer sometimes isn't responding or we want to remind him to give us " +"an answer." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Login" +#: ../system/objects.rst:186 +msgid "" +"We choose \"no\" for \"ignore escalation\" because we want to escalate the " +"tickets even if we are waiting on the manufacturer's feedback." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.login}``" +#: ../system/objects.rst:189 +msgid "The **result** in the creation dialog will look like this:" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Lastname" +#: ../system/objects.rst:0 +msgid "Screenshot showing ticket state creation dialog with example" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.lastname}``" -msgstr "" +#: ../system/objects.rst:199 +#, fuzzy +msgid "Ticket Priority" +msgstr "priorytet" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Firstname" +#: ../system/objects.rst:201 +msgid "" +"If the pre-configured priorities aren't enough for you or you want to change " +"them, you can do so by clicking on the cogwheel icon in the priority row in " +"the ticket tab:" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.firstname}``" +#: ../system/objects.rst:None +msgid "Screenshot showing highlighted ticket priority attribute" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Fax" +#: ../system/objects.rst:226 +msgid "Handling of priorities" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.fax}``" +#: ../system/objects.rst:210 +msgid "" +"In the priority configuration screen, you can add new priorities, disable " +"priorities or change priorities." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Email" +#: ../system/objects.rst:0 +msgid "Screenshot showing table of default ticket priorities" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.email}``" +#: ../system/objects.rst:218 +msgid "" +"To add a new priority, click on the \"New Priority\" button in the top right " +"corner. To change an existing priority, simply click on the affected " +"priority. This opens an edit dialog." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Department" +#: ../system/objects.rst:222 +msgid "" +"You can also clone a priority or set them to \"Default for new tickets\" by " +"clicking on the ⁝ action button and select the desired function." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.department}``" +#: ../system/objects.rst:225 +msgid "" +"*Default for new tickets* means that this priority is used for every newly " +"created ticket." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Address" +#: ../system/objects.rst:248 +msgid "Priorities in detail" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.address}``" +#: ../system/objects.rst:229 +msgid "Below you can find a description for each field and option." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created" +#: ../system/objects.rst:232 +msgid "" +"This is the name of the priority and what you and your agents are seeing " +"when choosing a priority somewhere (e.g. in tickets, trigger configuration)." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_at}``" +#: ../system/objects.rst:242 +msgid "Highlight color" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Cc" +#: ../system/objects.rst:237 +msgid "" +"Switch between *Low priority* (light blue), *High priority* (red) and - " +"(default). This affects the displayed color for ticket titles in overviews." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.cc}``" +#: ../system/objects.rst:241 +msgid "The color options are currently limited to the mentioned options." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``jdoe@example.com, company@example.com``" +#: ../system/objects.rst:245 +msgid "" +"You can create a note for the priority to inform other admins about the " +"priority. This has no effect on tickets." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Text" +#: ../system/objects.rst:249 +msgid "Set the priority to *active* or *inactive*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.body}``" +#: ../system/objects/external-data-source-example.rst:2 +msgid "External Data Source" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Test`` without formatting (plain)" +#: ../system/objects/external-data-source-example.rst:4 +msgid "" +"We assume you already had a look on :doc:`types` where you can find a " +"description of the individual fields." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article Text as HTML (not referenced)" +#: ../system/objects/external-data-source-example.rst:7 +msgid "" +"To reproduce this example, choose a category you want to add a custom field, " +"click on *New Attribute* and select *External data source field* under " +"*Format*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.body_as_html}``" +#: ../system/objects/external-data-source-example.rst:11 +msgid "" +"Our example story is to fetch data from an external product database. We " +"want to add our products to the tickets so that the products can be searched " +"and chosen from a list and also create a link to the product website." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Test`` with formatting" +#: ../system/objects/external-data-source-example.rst:16 +msgid "Base configuration" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "Ticket > Article#" +#: ../system/objects/external-data-source-example.rst:None +msgid "Initial steps to configure external data source object type" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "``#{ticket.article_count}``" +#: ../system/objects/external-data-source-example.rst:25 +msgid "Name: *product*" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``1`` number of ticket articles" +#: ../system/objects/external-data-source-example.rst:26 +msgid "Display: *Product*" msgstr "" -#: ../system/variables/config.rst:2 -msgid "Config" +#: ../system/objects/external-data-source-example.rst:29 +msgid "External data source configuration" msgstr "" -#: ../system/variables/config.rst:6 +#: ../system/objects/external-data-source-example.rst:31 msgid "" -"Below you'll find config related variables. These hold useful configuration " -"information that you can use within e.g. triggers to show necessary " -"information to your customer." +"First, enter the search URL making sure it contains ``#{search.term}`` as a " +"parameter:" msgstr "" -#: ../system/variables/config.rst:11 -msgid "Config Variables" +#: ../system/objects/external-data-source-example.rst:34 +msgid "**Example:** ``https://dummyjson.com/products/search?q=#{search.term}``" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Fully Qualified Domain Name" +#: ../system/objects/external-data-source-example.rst:36 +msgid "" +"After that, head down to the preview section and enter a search input for " +"the external data source." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.fqdn}``" +#: ../system/objects/external-data-source-example.rst:39 +msgid "**Example:** ``mac``" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``zammad.example.com``" +#: ../system/objects/external-data-source-example.rst:41 +msgid "Then you can find a preview of the response data below:" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Ticket Hook" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of JSON response based on search term" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.ticket_hook}``" +#: ../system/objects/external-data-source-example.rst:48 +msgid "" +"We recommend using the preview to have a look on the structure. There is a " +"top-level element called ``products``. One level below, you can find the " +"attributes ``id`` and ``title``." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``Ticket#``" +#: ../system/objects/external-data-source-example.rst:52 +msgid "**Search result response based on search from example:**" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > HTTP type" +#: ../system/objects/external-data-source-example.rst:119 +msgid "" +"To tell the remote system that the desired data is located below the " +"``products`` level, you have to put it in the field *Search result list key*." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.http_type}``" +#: ../system/objects/external-data-source-example.rst:122 +msgid "" +"After inserting ``products`` in the mentioned field, you get an extended " +"preview. You can find an additional box *Search result list* with a JSON " +"structure. This is the same response as before but stripped from the upper " +"``products`` element by the external data source." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``https`` or ``http``" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of JSON response search result list" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > SystemID" +#: ../system/objects/external-data-source-example.rst:132 +msgid "" +"Now you need to provide the keys for the search result values and labels. As " +"already mentioned, we are looking for the ``id`` and the ``title`` of our " +"products. If you haven't already, it is now a good time to look at the " +"preview of the *Search result list*." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.system_id}``" +#: ../system/objects/external-data-source-example.rst:197 +msgid "" +"After locating our two keys, we insert them in *search result value key* " +"(``id``) and in *Search result label key* (``title``)." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``31`` (value between 1 and 99)" +#: ../system/objects/external-data-source-example.rst:200 +msgid "" +"Basically, we configured the external data source already and we can see a " +"table in the preview section:" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Organization" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of product table based on search term" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.organization}``" +#: ../system/objects/external-data-source-example.rst:208 +msgid "" +"According to our example story, now just the *Link template* is missing." msgstr "" -#: ../system/variables/config.rst:1 +#: ../system/objects/external-data-source-example.rst:210 msgid "" -"``Zammad GmbH`` value set in `Branding `_" +"Please note that this is an optional feature. If you don't want to use such " +"links, of course you don't have to configure it." msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Product Name" +#: ../system/objects/external-data-source-example.rst:213 +msgid "" +"We can add now an address where additional product information can be found." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.product_name}``" +#: ../system/objects/external-data-source-example.rst:215 +msgid "Example: ``https://your_domain.com/q=#{ticket.product}``" msgstr "" -#: ../system/variables/config.rst:1 -msgid "" -"``Helpdesk`` value set in `Branding `_" +#: ../system/objects/external-data-source-example.rst:217 +msgid "In the example, the parameter means:" msgstr "" -#: ../system/variables/current-user.rst:2 -msgid "Current User" +#: ../system/objects/external-data-source-example.rst:219 +msgid "``#{}``: \"Frame\" for the insertion of information" msgstr "" -#: ../system/variables/current-user.rst:6 -msgid "" -"Current user variables always return values of the current user that caused " -"e.g. a trigger to run." +#: ../system/objects/external-data-source-example.rst:220 +msgid "``ticket``: object level, where you create your custom object" msgstr "" -#: ../system/variables/current-user.rst:8 -msgid "" -"Due to the above fact, these variables are often not (yet) set or available " -"for usage." +#: ../system/objects/external-data-source-example.rst:221 +msgid "``product``: name of the (custom) object" msgstr "" -#: ../system/variables/current-user.rst:10 +#: ../system/objects/external-data-source-example.rst:223 msgid "" -"In situations where e.g. schedulers or triggers run, this most likely is " -"nothing you want to use." -msgstr "" - -#: ../system/variables/current-user.rst:13 -msgid "Current User Variables" +"After configuring your *Link template*, there will be another column in the " +"preview. Hovering on the icons in the *Link* column will show you where it " +"forwards you." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Web" +#: ../system/objects/external-data-source-example.rst:232 +msgid "" +"In our example, one of the links looks like: https://your_domain.com/q=6, " +"where the 6 is the product id." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.web}``" +#: ../system/objects/external-data-source-example.rst:235 +msgid "You can find more information regarding the URL in :doc:`types`." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``https://zammad.org`` or empty if not set" +#: ../system/objects/includes/adding-values-hint.include.rst:3 +msgid "" +"Adding values can be tricky for first timers, don't forget to press \"➕ " +"Add\" after typing your values. Otherwise you may loose a value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > VIP" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:1 +#: ../system/objects/includes/reposition-values.include.rst:1 +msgid "**↕️ This field type allows the positioning of its values ↔️**" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.vip}``" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:3 +msgid "" +"In order to re-arrange the field values, first edit the field. Then you can " +"use ☰ to drag the values in question to the correct position. If you want to " +"change the layer depth, double click on ☰. With it you can cycle through the " +"available layers." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``false`` or ``true``" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:8 +msgid "When you're ready, submit your changes to save the object attribute." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Web" +#: :0 ../system/objects/types.rst:0 +msgid "" +"Screencast showing how to re-position values on tree select like\n" +"fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.web}``" +#: ../system/objects/includes/reposition-values.include.rst:3 +msgid "" +"In order to re-arrange the field values, edit the field and scroll below the " +"values. Make sure to tick the option \"Use custom option sort\"." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > VIP" +#: ../system/objects/includes/reposition-values.include.rst:8 +msgid "" +"If you do not tick this field, all manual positioning you did above will be " +"lost upon saving! ☠️" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.vip}``" +#: ../system/objects/includes/reposition-values.include.rst:11 +msgid "" +"Now use ☰ to drag the values in question to the correct position. When " +"you're ready, submit your changes to save the object attribute." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Phone" +#: :0 ../system/objects/types.rst:0 +msgid "Screencast showing how to re-position values" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.phone}``" +#: ../system/objects/includes/url-template-hint.include.rst:3 +msgid "" +"This field allows using :ref:`URL fields (Link Templates) `." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``004930123456789`` or empty if not set" +#: ../system/objects/permissions.rst:2 +msgid "Attribute Permissions" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Note" +#: ../system/objects/permissions.rst:7 +msgid "" +"In the object attributes configuration you can define if a field is shown " +"and if the input in the field is mandatory, separated by different screens " +"and for different :doc:`roles/permissions `." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.note}``" +#: ../system/objects/permissions.rst:17 +msgid "Screenshot shows object attribute permission table" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Some note to this user`` or empty if not set" +#: ../system/objects/permissions.rst:17 +msgid "" +"Some of the possible permissions and screen options for a user object " +"attribute." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Mobile" +#: ../system/objects/permissions.rst:19 +msgid "" +"Based on the object context (ticket, agent, organization, user), the " +"selectable roles (to be precise: the required permissions) and screens " +"differ. Be aware that these settings aren't affecting data creation via " +"other channels than the UI." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.mobile}``" +#: ../system/objects/permissions.rst:24 +msgid "" +"If you want to have further customization possibilities, you should have a " +"look at the :doc:`core workflows `." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``0049176123456789`` or empty if not set" +#: ../system/objects/permissions.rst:28 +msgid "Screens" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Login" +#: ../system/objects/permissions.rst:30 +msgid "" +"In the table below you can find an overview about the different permissions " +"and the available screens Zammad distinguishes between." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.login}``" +#: ../system/objects/permissions.rst:37 +msgid "Screen" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Lastname" +#: ../system/objects/permissions.rst:38 +msgid "Available for" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.lastname}``" +#: ../system/objects/permissions.rst:40 +msgid "create" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Firstname" +#: ../system/objects/permissions.rst:41 ../system/objects/permissions.rst:52 +#: ../system/objects/permissions.rst:59 ../system/objects/permissions.rst:73 +msgid "admin.user" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.firstname}``" +#: ../system/objects/permissions.rst:42 ../system/objects/permissions.rst:53 +#: ../system/objects/permissions.rst:60 +msgid "admin.organization" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``John`` or empty if not set" -msgstr "" +#: ../system/objects/permissions.rst:43 ../system/objects/permissions.rst:54 +#: ../system/objects/permissions.rst:61 +#, fuzzy +msgid "admin.group" +msgstr "grupa" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Fax" +#: ../system/objects/permissions.rst:44 +msgid "Creation dialog for not yet existing data" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.fax}``" +#: ../system/objects/permissions.rst:45 +msgid "create_middle" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``004930123464789`` or empty if not set" -msgstr "" +#: ../system/objects/permissions.rst:46 ../system/objects/permissions.rst:50 +#: ../system/objects/permissions.rst:57 ../system/objects/permissions.rst:66 +#: ../system/objects/permissions.rst:70 +#, fuzzy +msgid "ticket.customer" +msgstr "Makra" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Email" -msgstr "" +#: ../system/objects/permissions.rst:47 ../system/objects/permissions.rst:51 +#: ../system/objects/permissions.rst:58 ../system/objects/permissions.rst:69 +#, fuzzy +msgid "ticket.agent" +msgstr "Makra" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.email}``" +#: ../system/objects/permissions.rst:48 +msgid "Ticket create dialog (middle section)" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``jdoe@customer.tld``" +#: ../system/objects/permissions.rst:49 +msgid "edit" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Department" +#: ../system/objects/permissions.rst:55 +msgid "Editing dialog for already existing data" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.department}``" +#: ../system/objects/permissions.rst:56 +msgid "view" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Sales`` or empty if not set" +#: ../system/objects/permissions.rst:62 +msgid "View-only dialog for already existing data" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Avatar" +#: ../system/objects/permissions.rst:64 +msgid "(e.g. user or organization from search)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.avatar(60,60)}``" +#: ../system/objects/permissions.rst:65 +msgid "signup" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "avatar picture with width and height in pixel (e.g. 60,60)" +#: ../system/objects/permissions.rst:67 +msgid "Sign-up screen for new customers" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Address" +#: ../system/objects/permissions.rst:68 +msgid "invite_customer" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.address}``" +#: ../system/objects/permissions.rst:71 +msgid "" +"Customer invitation screen (from :doc:`First Steps ` area)" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Some street 1, 12345 Berlin`` or empty if not set" +#: ../system/objects/permissions.rst:72 +msgid "invite_agent" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated at" +#: ../system/objects/permissions.rst:74 +msgid "" +"Agent invitation screen (from :doc:`First Steps ` area)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_at}``" +#: ../system/objects/permissions.rst:78 +msgid "Screen Options" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC``" +#: ../system/objects/permissions.rst:80 +msgid "" +"For the different screens you can select \"show\" and \"required\" options." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Phone" +#: ../system/objects/permissions.rst:82 +msgid "**shown:** Show (check) or hide (uncheck) a field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.phone}``" +#: ../system/objects/permissions.rst:83 +msgid "" +"**required:** Set a field to mandatory (check). Forces users (via UI and " +"API) to populate the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Shared organization" +#: ../system/objects/types.rst:7 +msgid "Example external data source" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.shared}``" +#: ../system/objects/types.rst:2 +msgid "Attribute types" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Note" +#: ../system/objects/types.rst:4 +msgid "" +"When adding a new object attribute, you can choose between the following " +"attribute types." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.note}``" +#: ../system/objects/types.rst:14 +msgid "" +"You cannot change the attribute format / type as soon as it is applied. If " +"you no longer need an object attribute, consider disabling it instead of " +"removing." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``A note to the organization of the user`` or empty if not set" +#: ../system/objects/types.rst:18 +msgid "**What about the translation of my attributes?**" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Name" +#: ../system/objects/types.rst:20 +msgid "" +"For some attribute types you can decide if they should be translatable or " +"not. To be precise, it works only for the selectable fields because the " +"possible choices are known and limited. For the following attribute types, " +"you can set the translatable flag:" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.name}``" +#: ../system/objects/types.rst:25 +msgid "*Boolean field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``Zammad GmbH``" +#: ../system/objects/types.rst:26 +msgid "*Single selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Domain based assignment" +#: ../system/objects/types.rst:27 +msgid "*Multiple selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.domain_assignment}``" +#: ../system/objects/types.rst:28 +msgid "*Single tree selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Domain" +#: ../system/objects/types.rst:29 +msgid "*Multiple tree selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.domain}``" +#: ../system/objects/types.rst:31 +msgid "" +"For these types, you can find an additional field *Translate field contents*:" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``zammad.com`` or empty if not set" +#: ../system/objects/types.rst:0 +msgid "Screenshot showing translatable attribute types" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > VIP" +#: ../system/objects/types.rst:38 +msgid "Screenshot with example of translatable attribute type" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.vip}``" +#: ../system/objects/types.rst:45 +msgid "Boolean field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Note" +#: ../system/objects/types.rst:41 +msgid "" +"Provides a drop-down field with display values for ``true`` and ``false``. " +"Setting a default is mandatory." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.note}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Boolean fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Mobile" +#: ../system/objects/types.rst:55 +msgid "Date field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.mobile}``" +#: ../system/objects/types.rst:48 +msgid "Provides a date picker field and does not allow default values." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Login" +#: ../system/objects/types.rst:52 +msgid "Default time diff (hours)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.login}``" +#: ../system/objects/types.rst:51 +msgid "" +"This setting helps the user by highlighting the day from now plus the " +"provided value. It *does not* pre-fill the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Lastname" +#: ../system/objects/types.rst:0 +msgid "Available settings for Date fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.lastname}``" +#: ../system/objects/types.rst:73 +msgid "Date & time field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Firstname" +#: ../system/objects/types.rst:58 +msgid "Provides a date and time picker – does not allow default values" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.firstname}``" +#: ../system/objects/types.rst:62 +msgid "Allow future" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Fax" +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the future." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.fax}``" +#: ../system/objects/types.rst:66 +msgid "Allow past" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Email" +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the past." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.email}``" +#: ../system/objects/types.rst:70 +msgid "Default time diff (minutes)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Department" +#: ../system/objects/types.rst:69 +msgid "" +"This setting helps the user by highlighting the day from now plus the " +"provided value. It does not pre-fill the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.department}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Date & time fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Web" +#: ../system/objects/types.rst:86 +msgid "Integer field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.web}``" +#: ../system/objects/types.rst:76 +msgid "" +"Provides an input field that allows integer usage only. You may define a " +"default value. You cannot enforce comma separation." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > VIP" +#: ../system/objects/types.rst:80 +msgid "Minimal" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.vip}``" +#: ../system/objects/types.rst:80 +msgid "The minimal value the field accepts." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Phone" +#: ../system/objects/types.rst:83 +msgid "Maximal" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.phone}``" +#: ../system/objects/types.rst:83 +msgid "The maximum value the field accepts." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Note" +#: ../system/objects/types.rst:0 +msgid "Available settings for Integer fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.note}``" +#: ../system/objects/types.rst:99 +msgid "Multiple selection field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Mobile" +#: ../system/objects/types.rst:89 +msgid "" +"Provides a selection field that allows the selection of one or more out of " +"several. This field does allow setting a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.mobile}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Multiple selection fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Login" +#: ../system/objects/types.rst:112 +msgid "Single selection field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.login}``" +#: ../system/objects/types.rst:102 +msgid "" +"Provides a drop-down field that allows selection of one value out of " +"several. This field does allow setting a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Lastname" +#: ../system/objects/types.rst:0 +msgid "Available settings for Single selection fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.lastname}``" +#: ../system/objects/types.rst:142 +msgid "Textarea field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Firstname" +#: ../system/objects/types.rst:115 +msgid "" +"Provides a text area input field (multiple lines) and thus allows e.g. new " +"lines. You can set a default field value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.firstname}``" +#: ../system/objects/types.rst:120 +msgid "" +"Please note that this field *does not* support text formatting or HTML " +"content (rich text)." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Fax" +#: ../system/objects/types.rst:123 +msgid "**🥵 This field can consume a lot of visual space**" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.fax}``" +#: ../system/objects/types.rst:125 +msgid "" +"Depending on where you use this field type, it may use a lot of visual space " +"if you provide a lot of text. This may be an issue to work with." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Email" +#: ../system/objects/types.rst:130 +msgid "Default" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.email}``" +#: ../system/objects/types.rst:129 +msgid "" +"The here provided text will be shown within the text area field or new data " +"sets." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Department" +#: ../system/objects/types.rst:134 ../system/objects/types.rst:160 +msgid "Maxlength" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.department}``" +#: ../system/objects/types.rst:0 ../system/objects/types.rst:160 +msgid "You can pick the maximum length of the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Avatar" +#: ../system/objects/types.rst:0 +msgid "The default length of this object is ``500``." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.avatar(60,60)}``" +#: ../system/objects/types.rst:139 +msgid "Rows" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Address" +#: ../system/objects/types.rst:0 +msgid "" +"Change the number of rows to dislay so that you can use only the space you " +"really need." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.address}``" +#: ../system/objects/types.rst:0 +msgid "The default number of rows is ``4``." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created at" +#: ../system/objects/types.rst:0 +msgid "Available settings for Textarea fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_at}``" +#: ../system/objects/types.rst:165 +msgid "Text field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Avatar" +#: ../system/objects/types.rst:145 +msgid "Provides a text field (one line) and allows choosing a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.avatar(60,60)}``" +#: ../system/objects/types.rst:148 +msgid "" +"Defines the type of the input field. This allows e.g. your browser to ensure " +"that you provide the specific type." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Address" +#: ../system/objects/types.rst:152 +msgid "Currently available:" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.address}``" +#: ../system/objects/types.rst:155 +msgid "Phone" msgstr "" -#: ../system/variables/ticket.rst:6 -msgid "" -"Below you can find all available ticket-based variables within Zammad. These " -"can be called via Triggers for example. If you're unsure if Zammad does " -"support variables at the point you're at, you can try to type ``::`` to " -"check." +#: ../system/objects/types.rst:156 +msgid "Text" msgstr "" -#: ../system/variables/ticket.rst:12 -msgid "Ticket Variables" +#: ../system/objects/types.rst:157 +msgid "Url *(URL fields disable link-template availability)*" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Web" +#: ../system/objects/types.rst:0 +msgid "Available settings for Text fields" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.web}``" +#: ../system/objects/types.rst:174 +msgid "Single tree selection field" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > VIP" +#: ../system/objects/types.rst:168 +msgid "" +"Provides a select-like field with up to 6 layers of options. Does not allow " +"setting a default value." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.vip}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Tree Select fields" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Phone" +#: ../system/objects/types.rst:183 +msgid "Multiple tree selection field" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.phone}``" +#: ../system/objects/types.rst:177 +msgid "" +"Provides a select-like field with up to 6 layers of options allowing the " +"selection of multiple values. Does not allow setting a default value." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Note" +#: ../system/objects/types.rst:302 +msgid "External Data Source field" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.note}``" +#: ../system/objects/types.rst:186 +msgid "" +"Provides a searchable field which fetches data from an external system. This " +"can be useful if you have data outside of Zammad and don't want to maintain " +"both data sources." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Mobile" +#: ../system/objects/types.rst:190 +msgid "The feature works as follows:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.mobile}``" +#: ../system/objects/types.rst:192 +msgid "" +"Zammad sends a query with a search string (free text from agent or based on " +"a variable) in a pre-defined format (\"Search URL\") to an external system." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Login" +#: ../system/objects/types.rst:195 +msgid "" +"This external system searches for matches and provides a response as a JSON " +"structure to Zammad." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.login}``" +#: ../system/objects/types.rst:197 +msgid "" +"Zammad just looks for the defined list and value keys, reads the content and " +"displays the value to the user. There is no search on Zammad side." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Lastname" +#: ../system/objects/types.rst:201 +msgid "" +"The usage of a PostgreSQL database for Zammad is required. In any other " +"case, Zammad will hide the external data source type and you are not able to " +"use it. If you want to use this feature, consider to :docs:`migrate your " +"database `." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.lastname}``" +#: ../system/objects/types.rst:205 +msgid "Currently, only ``GET`` is supported as request method." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Firstname" +#: ../system/objects/types.rst:206 +msgid "" +"The data structure must be in JSON format and provide the objects in an " +"array." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.firstname}``" +#: ../system/objects/types.rst:208 +msgid "" +"The endpoint for the external data source has to support search. On Zammad " +"side, there is no search/logic implemented; however, you can define the " +"output key and value based on the result(s) from the response (which " +"provides already filtered content based on the search)." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Fax" +#: ../system/objects/types.rst:212 +msgid "" +"If you receive more results as expected, your external data source search " +"may not work properly or the structure of the URL is not correct. You should " +"get in touch with a responsible person from the external system." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.fax}``" +#: ../system/objects/types.rst:217 +msgid "" +"Please have a look :doc:`at our example `, where you can find a possible configuration for a public " +"dummy endpoint." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Email" +#: ../system/objects/types.rst:0 +msgid "Available settings for external data source fields" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.email}``" +#: ../system/objects/types.rst:242 +msgid "Search URL" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Department" +#: ../system/objects/types.rst:227 +msgid "" +"Set your endpoint where Zammad fetches the data. Please make sure to include " +"a valid search :doc:`variable ` as an URL parameter. " +"Example for a free text search at user input: ``#{search.term}``" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.department}``" +#: ../system/objects/types.rst:232 +msgid "" +"If in doubt, ask the responsible person for the external data source how " +"they expect the structure of the URL." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Avatar" +#: ../system/objects/types.rst:236 +msgid "" +"Depending on your search variable, the preview might work or not. The reason " +"is that the context might not be available and it is no bug." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.avatar(60,60)}``" +#: ../system/objects/types.rst:239 +msgid "" +"Please also make sure to use a variable which is available in your object " +"context. For example you won't be able to search for a ticket in a user " +"object context." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Address" +#: ../system/objects/types.rst:252 +msgid "SSL Verification" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.address}``" +#: ../system/objects/types.rst:245 +msgid "Here you can switch the SSL verification to no." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated at" +#: ../system/objects/types.rst:249 +msgid "" +"If your external data source system is using self signed certificates, " +"please have a look :doc:`here ` for " +"further information about how to handle them in Zammad, so you can keep the " +"SSL verification activated." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_at}``" +#: ../system/objects/types.rst:258 +msgid "HTTP Authentication" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Title" +#: ../system/objects/types.rst:255 +msgid "" +"If your external data source requires an authentication, you can set it " +"here. You can leave it empty or choose between *Basic Authentication* or " +"*Authentication Token* (selecting one of the two methods leads to additional " +"fields where you can enter your credentials/token)." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.title}``" +#: ../system/objects/types.rst:265 +msgid "Search result list key" msgstr "" -#: ../system/variables/ticket.rst:1 +#: ../system/objects/types.rst:261 msgid "" -"``My amazing Subject`` (normally subject, can be edited within Interface and " -"thus differ)" +"Defines the level in the JSON structure which provides the list with search " +"results. You can leave it empty, if the data is already provided as an " +"array. If you have to go deeper in the structure, you can provide a path " +"with ``.`` as separators, e.g. ``key.subkey.sub-sub-key``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Accounted Time" +#: ../system/objects/types.rst:271 +msgid "Search result value key" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.time_unit}``" +#: ../system/objects/types.rst:268 +msgid "" +"Defines the attribute in the structure in which your external data source " +"provides the *value* for your data. An example would be a product *number*. " +"If you have to go deeper in the structure, you can provide a path with ``.`` " +"as separators, e.g. ``key.subkey.sub-sub-key``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``1``, ``2.75`` or empty response" +#: ../system/objects/types.rst:277 +msgid "Search result label key" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Tags" +#: ../system/objects/types.rst:274 +msgid "" +"Defines the attribute in the structure in which your external data source " +"provides the *label* for your data. An example would be a product *name*. If " +"you have to go deeper in the structure, you can provide a path with ``.`` as " +"separators, e.g. ``key.subkey.sub-sub-key``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.tags}``" +#: ../system/objects/types.rst:280 +msgid "" +"In the preview area, you can find the following items (depending on your " +"configuration above):" msgstr "" -#: ../system/variables/ticket.rst:1 +#: ../system/objects/types.rst:283 msgid "" -"Currently not available, see `Issue 2769 `_" +"**Error/hint message** (only if configuration is not complete): Zammad tells " +"you, if there is a problem and what you should change in your configuration." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > State > Name" +#: ../system/objects/types.rst:286 +msgid "" +"**Search field**: search for an existing attribute in the data source to get " +"a preview. This is required for the fields below to show up." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.state.name}``" +#: ../system/objects/types.rst:288 +msgid "" +"**Search result response** (only if configuration is not complete): here you " +"can find a syntax highlighted JSON preview of the response, based on the " +"search term you entered." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``new``, ``open``, ..." +#: ../system/objects/types.rst:291 +msgid "" +"**Search result list** (only if *search result list key* is properly set): " +"output of the structure under the configured *search result list key*." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Priority > Name" +#: ../system/objects/types.rst:294 +msgid "" +"**Preview table** (when fully configured): Zammad shows you a table which " +"includes the found items based on the search string (value, label and " +"optional link). You can use this preview if you don't have the complete data " +"structure of the external system in mind." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.priority.name}``" +#: ../system/objects/types.rst:299 +msgid "" +"An example of a configured external data source field from agent perspective:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2 normal``" +#: ../system/objects/types.rst:0 +msgid "Screencast showing the search for a product in a ticket" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Pending till" +#: ../system/objects/types.rst:307 +msgid "URL fields (Link-Template)" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.pending_time}``" +#: ../system/objects/types.rst:311 +msgid "" +"This function is restricted to Text, Select and External data source types " +"only." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not set" +#: ../system/objects/types.rst:314 +msgid "" +"Link-Templates are an amazing way to dynamically generate URLs. They allow " +"you to integrate other systems better without having to manually copy data " +"from Zammad if possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Web" +#: ../system/objects/types.rst:320 +msgid "" +"Another great way of communicating with another system may be Zammad's :doc:" +"`Webhooks `." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.web}``" +#: ../system/objects/types.rst:323 +msgid "" +"After filling a link-template enabled field, an URL icon will appear on its " +"right. Clicking on the icon opens a new tab." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``https://zammad.com`` or empty if not set" +#: ../system/objects/types.rst:328 +msgid "" +"Even though Zammad displays the link template within object edit and create " +"screens, the function is optional. It's only active if you populate the " +"field." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > VIP" +#: ../system/objects/types.rst:333 +msgid "" +"What's the difference between URL and text fields with link template...?!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.vip}``" +#: ../system/objects/types.rst:335 +msgid "" +"Both fields have different use cases. Use ``text`` type text fields when " +"ever you have a *static* url that requires dynamic parameters. If you " +"require a drag & drop like field that you can put in any URL, use ``URL`` " +"type text fields." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Phone" +#: ../system/objects/types.rst:340 +msgid "" +"The difference is easier to spot when comparing the fields directly, below " +"screencast shows the result - the dynamic approach uses existing values in " +"the moment of updating to built the URL - e.g. ``https://google.com/search?" +"q=cookies`` - while the URL approach uses the actual URL of the field - e.g. " +"``https://zammad.com``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.phone}``" +#: ../system/objects/types.rst:None +msgid "" +"Screencast showing the differents in between URL and text type fields with " +"actual values" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Note" +#: ../system/objects/types.rst:352 +msgid "How does this work...?!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.note}``" +#: ../system/objects/types.rst:354 +msgid "" +"As an example, let's say you have an attribute called ``amazing_attribute`` " +"and you want to open a google search directly with the input from that field." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Mobile" +#: ../system/objects/types.rst:357 +msgid "" +"Providing the link-template field below allows you to do so: ``https://www." +"google.com/search?q=#{ticket.amazing_attribute}``" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.mobile}``" +#: ../system/objects/types.rst:362 +msgid "" +"You can use any :doc:`Zammad variable ` as long as it's " +"available in the moment you need it." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Login" +#: ../system/objects/types.rst:365 +msgid "" +"As a result, you are redirected to Google with a search for the value of the " +"attribute, if you click on the button in the ticket (as you can see in the " +"screencast above)." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.login}``" +#: ../system/packages.rst:2 +msgid "Packages" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``agent``" +#: ../system/packages.rst:4 +msgid "That's the package management-area." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Lastname" +#: ../system/packages.rst:6 +msgid "Individual add-ons for Zammad can be installed and managed here." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.lastname}``" +#: ../system/sessions.rst:2 +msgid "Sessions" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Mustermann`` or empty if not set" +#: ../system/sessions.rst:4 +msgid "" +"Sessions management allows reviewing currently known user sessions and " +"allows to end these. The session timeout is affected by :ref:" +"`security_session_timeout` configurations from security settings." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Firstname" +#: ../system/sessions.rst:None +msgid "Screenshot showing Zammad's session management" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.firstname}``" +#: ../system/sessions.rst:13 +msgid "Zammad will provide the following information:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Max`` or empty if not set" +#: ../system/sessions.rst:16 +msgid "" +"The user account this session entry belongs to. It can be normal if a user " +"has several sessions in the list. This can be due to changed browser " +"information or if you use e.g. single sign on methods where the user does " +"not use the log off button." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Fax" +#: ../system/sessions.rst:22 +msgid "Browser" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.fax}``" +#: ../system/sessions.rst:22 +msgid "The browser agent communicated to Zammad." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Email" +#: ../system/sessions.rst:40 +msgid "Location" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.email}``" +#: ../system/sessions.rst:25 +msgid "" +"The anticipated location based on the users IP address. Depending on the IP " +"address the result shown may differ. This option depends on :doc:`/settings/" +"system/services`." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``agent@company.tld`` or empty if not set" +#: ../system/sessions.rst:29 +msgid "The following information can be shown:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Department" +#: ../system/sessions.rst:33 +msgid "IP address" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.department}``" +#: ../system/sessions.rst:32 +msgid "" +"Either if you set *Geo IP services* to inactive or you're using internal IP " +"address which do not provide location information." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Support`` or empty if not set" +#: ../system/sessions.rst:40 +msgid "Country (or Country + City)" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Avatar" +#: ../system/sessions.rst:36 +msgid "" +"If *Geo IP services* is enabled only. Depends on how detailed the available " +"IP address information are." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.avatar(60,60)}``" +#: ../system/sessions.rst:39 +msgid "" +"Be aware that results can be inaccurate - this technically is not an error." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Address" +#: ../system/sessions.rst:43 +msgid "Age" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.address}``" +#: ../system/sessions.rst:43 +msgid "Provides the time when the session initially has been created." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Shared organization" +#: ../system/sessions.rst:50 +msgid "Update" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.shared}``" +#: ../system/sessions.rst:46 +msgid "" +"Provides the time the user used this session to open Zammad. This timestamp " +"is only updated if the user e.g. reloads, not during normal work on tickets." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Note" +#: ../system/sessions.rst:50 +msgid "This timestamp is being used for the session timeout." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.note}``" +#: ../system/sessions.rst:53 +msgid "" +"Use the delete button to remove a single session on behalf of your user." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Name" +#: ../system/subscription.rst:2 +msgid "Subscription (SaaS)" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.name}``" +#: ../system/subscription.rst:4 +msgid "" +"The subscription settings page allows you to configure your instances " +"package and number of agents required." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Zammad GmbH`` or empty if not set" +#: ../system/subscription.rst:9 +msgid "" +"This setting section is only available for Hosted setups. If you're looking " +"for on premise support contracts, please see the `Zammad pricing page " +"`_." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Domain based assignment" +#: ../system/subscription.rst:14 ../system/subscription.rst:34 +msgid "Plan" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.domain_assignment}``" +#: ../system/subscription.rst:16 +msgid "" +"Here you can set up everything affecting your instance subscription " +"functions like number of agents and package." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Domain" +#: ../system/subscription.rst:19 +msgid "" +"On top of the page you can find a subscription summary. You'll find the " +"number of used and available (booked) agent seats there. By using the *see " +"more* link you can also expand an agent list to see the currently configured " +"active agents. This list *does not* count accounts with admin permissions " +"only." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.domain}``" +#: ../system/subscription.rst:None +msgid "" +"Within subscription you can always see how many agents are still\n" +"available to add and who uses the seats." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``domain.tld`` or empty if not set" +#: ../system/subscription.rst:29 +msgid "" +"Learn more on how to manage your agents in general :doc:`here `." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > VIP" +#: ../system/subscription.rst:36 +msgid "" +"This section gives you an overview of the available plans and their " +"functions / limits. If you require a more detailed table, check our " +"`detailed pricing table `_ for more." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.vip}``" +#: ../system/subscription.rst:40 +msgid "" +"Your selection in this step will decide on the base agent price and e.g. " +"agent limits that might apply in the summary step." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Number" +#: ../system/subscription.rst:43 +msgid "" +"The green *Selected* button will also tell you what plan you're currently in." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.number}``" +#: ../system/subscription.rst:47 +msgid "" +"Trial instances are running at Professional with 3 agents. The plan cannot " +"be changed during the trial for technical reasons, if you require more " +"agents for testing, please contact `our sales team `_ with a reason for the raise request." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``31001``, ``201910731001``, ..." +#: ../system/subscription.rst:None +msgid "" +"Screenshot showing three available packages for a hosted Zammad\n" +"instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > ID" +#: ../system/subscription.rst:57 +msgid "" +"At the bottom of this block you can find a summary where you can adjust the " +"settings of the previous selected plan." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.id}``" +#: ../system/subscription.rst:62 +msgid "" +"Note that upgrading (more agents, higher package) is always possible, " +"however, downgrading will only happen when your billing period renews." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``17``, ``5281``, ..." +#: ../system/subscription.rst:66 +msgid "" +"Upgrading resets your billing period and existing credit will be deducted " +"from the new total." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact (customer)" +#: ../system/subscription.rst:75 +msgid "Billing cycle" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_customer_at}``" +#: ../system/subscription.rst:70 +msgid "" +"You can choose between either monthly or yearly billing. The price per agent " +"will be cheaper if you decide for yearly billing." msgstr "" -#: ../system/variables/ticket.rst:1 +#: ../system/subscription.rst:73 msgid "" -"``2019-10-07 16:25:00 UTC`` or empty if not applicable yet (Please note " -"`Ticket last contact behavior Settings `_ for this)" +"If you're still trying out things and are unsure of the right package for " +"your instance, you may want to choose monthly first and then upgrade to " +"yearly when you're sure." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact" +#: ../system/subscription.rst:83 +msgid "Plan: (Starter|Professional|Plus) - Agents" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_at}``" +#: ../system/subscription.rst:78 +msgid "Choose the number of agents you require for your instance." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact (agent)" +#: ../system/subscription.rst:80 +msgid "" +"Keep in mind that some packages may have agent limits. Depending on the " +"previous chosen package, you won't be able to exceed specific agent numbers. " +"Also note that setting less agents than currently configured is not possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_agent_at}``" +#: ../system/subscription.rst:86 +msgid "Total" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable yet" +#: ../system/subscription.rst:86 +msgid "This will be the net total you're going to be billed." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Note" +#: ../system/subscription.rst:88 +msgid "" +"By using the *Update subscription* button, the instance package will be " +"adjusted immediately. If you didn't provide a payment method yet, Zammad " +"will request you to provide one at this point." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.note}``" +#: ../system/subscription.rst:94 +msgid "" +"In case you're still within the trial period, this means that the trial will " +"be over immediately!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Note about this group``" +#: ../system/subscription.rst:97 +msgid "Down- or upgrading during the trial period *is not* possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Name" +#: ../system/subscription.rst:None +msgid "Screenshot showing payment options and a pricing summary" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.name}``" +#: ../system/subscription.rst:103 +msgid "Billing Information" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Sales``" +#: ../system/subscription.rst:105 +msgid "" +"You can control all billing relevant information like invoices, billing " +"address and the option to cancel your subscription." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Follow-up possible" +#: ../system/subscription.rst:108 +msgid "" +"All adjusted billing information below only affect future invoices. If your " +"invoice was issued wrong, please contact `our sales team `_." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.follow_up_possible}``" +#: ../system/subscription.rst:114 +msgid "Billing address" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``no`` or ``yes``" +#: ../system/subscription.rst:113 +msgid "" +"Provide your company address here, make sure to include the companies name " +"in case required. This address will be referenced on your invoice." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Assign Follow-Ups" +#: ../system/subscription.rst:118 +msgid "VAT ID" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.follow_up_assignment}``" +#: ../system/subscription.rst:117 +msgid "" +"Provide your VAT ID here. If applicable your invoice will not contain German " +"VAT. Please make sure to pay the VAT in your country as required." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Assignment Timeout" +#: ../system/subscription.rst:127 +msgid "Billing Email Address" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.assignment_timeout}``" +#: ../system/subscription.rst:121 +msgid "" +"Usually the instance owner (the person that registered the instance) will " +"receive all emails including the invoices. In case you have your own billing " +"department, you can provide their email address here." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``20`` or empty if not configured" +#: ../system/subscription.rst:125 +msgid "" +"All billing relevant information will then be sent to this email address." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > First response" +#: ../system/subscription.rst:127 +msgid "Invoices are sent as attachment (PDF) to this email address." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.first_response_at}``" +#: ../system/subscription.rst:129 +msgid "" +"Don't forget to press the *Update billing information* button after you " +"changed above settings." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Escalation at" +#: ../system/subscription.rst:None +msgid "" +"Screenshot showing options for billing information within the\n" +"subscription menu" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.escalation_at}``" +#: ../system/subscription.rst:137 +msgid "Payment Method" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable" +#: ../system/subscription.rst:139 +msgid "You can pay via credit card or SEPA mandate." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Web" +#: ../system/subscription.rst:144 +msgid "Credit card" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.web}``" +#: ../system/subscription.rst:142 +msgid "" +"Simply follow the dialogue by clicking *authorize credit card* and confirm -" +"if required by your bank- your consent to Zammad using your card for the " +"payments." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > VIP" +#: ../system/subscription.rst:148 +msgid "SEPA Direct Debit" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.vip}``" +#: ../system/subscription.rst:147 +msgid "" +"Provide the requested information of the bank account holder and update if " +"you're ready. You'll then receive an email with the SEPA mandate." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Phone" +#: ../system/subscription.rst:150 +msgid "" +"Technically there's also the possibility to pay via invoice, however - this " +"method only applies to a fairly low number of instances. Please contact `our " +"sales team `_ for more information." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.phone}``" -msgstr "" +#: ../system/subscription.rst:156 +#, fuzzy +msgid "Cancel Subscription" +msgstr "Opis" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Note" +#: ../system/subscription.rst:158 +msgid "" +"Do you want to cancel your subscription? In case you no longer want to use " +"Zammad's SaaS, you can cancel your subscription by using the red *Yes, " +"please cancel my subscription* button." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.note}``" +#: ../system/subscription.rst:162 +msgid "" +"To cancel the description, enter the FQDN of your Zammad instance and " +"provide a reason for your cancellation." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Mobile" +#: ../system/subscription.rst:165 +msgid "" +"Your subscription will end the day after your trial or billing period ends." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.mobile}``" +#: ../system/subscription.rst:None +msgid "Screenshot showing subscription cancellation dialog" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Login" +#: ../system/subscription.rst:174 +msgid "" +"We will remind you about your cancelled subscription several times up front. " +"After the subscription ended all instance data will be removed. A restore " +"*is not* possible after that point!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.login}``" +#: ../system/subscription.rst:178 +msgid "**😖 Cancelled by accident?**" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Lastname" +#: ../system/subscription.rst:180 +msgid "" +"You can always undo the cancellation via the *Yes, undo the cancellation of " +"my subscription* button up to the last subscription day!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.lastname}``" +#: ../system/subscription.rst:0 +msgid "" +"Screenshot showing a red button to cancel the subscription\n" +"cancellation" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Firstname" +#: ../system/subscription.rst:189 +msgid "Payment History" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.firstname}``" +#: ../system/subscription.rst:191 +msgid "" +"The payment history will display a history of all paid invoices. At this " +"point you can also download these in case you need them again." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Fax" +#: ../system/subscription.rst:196 +msgid "" +"You will only find *paid* invoices here. Invoices that are to be billed are " +"not available before the payment is completed." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.fax}``" +#: ../system/subscription.rst:201 +msgid "Date" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Email" +#: ../system/subscription.rst:201 +msgid "Date of the invoice creation." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.email}``" +#: ../system/subscription.rst:204 +msgid "Amount" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Department" +#: ../system/subscription.rst:204 +msgid "Invoice total including VAT if applicable." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.department}``" +#: ../system/subscription.rst:207 +msgid "" +"Contains contract period (monthly or yearly) and hosted plan for the " +"subscription period in question." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Avatar" +#: ../system/subscription.rst:218 +msgid "Payment method / Service period" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.avatar(60,60)}``" +#: ../system/subscription.rst:211 +msgid "" +"Used bank account or credit card as well as the subscription period the " +"invoice is about." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Address" +#: ../system/subscription.rst:216 +msgid "" +"It might happen that the invoice date and subscription period differ. This " +"is nothing to worry about, the subscription periods will be accounted later " +"on." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.address}``" +#: ../system/subscription.rst:222 +msgid "Receipt" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Web" +#: ../system/subscription.rst:221 +msgid "" +"Use the arrow to download the invoice in question. You can download all " +"available invoices any time you need to here!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.web}``" +#: ../system/subscription.rst:None +msgid "Screenshot showing payment history of a hosted instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > VIP" +#: ../system/subscription.rst:229 +msgid "FAQ" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.vip}``" +#: ../system/subscription.rst:233 +msgid "I set up a trial account but am missing functions to test" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Phone" +#: ../system/subscription.rst:232 +msgid "" +"The trial instance is running within the professional package allowing up to " +"three agents." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.phone}``" +#: ../system/subscription.rst:236 +msgid "Can I change package within the trial?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Note" +#: ../system/subscription.rst:236 +msgid "No. As soon as the package is changed the subscription begins." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.note}``" +#: ../system/subscription.rst:241 +msgid "What happens to my trial instance after the trial period ended?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Mobile" +#: ../system/subscription.rst:239 +msgid "" +"Your instance will automatically be canceled for you. Please see *What " +"happens to my instance after it has been canceled?* for more." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.mobile}``" +#: ../system/subscription.rst:254 +msgid "What happens to my instance after it has been canceled?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Login" +#: ../system/subscription.rst:244 +msgid "That depends slightly on your instance state:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.login}``" +#: ../system/subscription.rst:250 +msgid "Trial instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Lastname" +#: ../system/subscription.rst:247 +msgid "" +"If you're still on trial, we will ice your instance and remind you once " +"again about your instance. We then will wait some days and remove your " +"instance from our system. This is the last time we will inform you by Email." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.lastname}``" +#: ../system/subscription.rst:254 +msgid "Paid instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Firstname" +#: ../system/subscription.rst:253 +msgid "" +"If you're a paying customer and canceled your subscription, the instance " +"removal will take place the day after your last subscription day." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.firstname}``" +#: ../system/subscription.rst:256 +msgid "Can removed instances be restored?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Fax" +#: ../system/subscription.rst:257 +msgid "No. Once your instance has been removed, a restoration is not possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.fax}``" +#: ../system/system-report.rst:2 +msgid "System Report" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Email" +#: ../system/system-report.rst:4 +msgid "" +"In this place you can't configure Zammad. Instead you can obtain a system " +"report about Zammad and its configuration." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.email}``" +#: ../system/system-report.rst:7 +msgid "" +"See the description in Zammad for an explanation. You can even find a " +"preview of the included data below the **Download** button." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Department" +#: ../system/system-report.rst:10 +msgid "" +"Zammad never sends this automatically to anyone. It is a manual process only " +"to provide better support based on your configuration." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.department}``" +#: ../system/translations.rst:2 +msgid "Translations" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Avatar" +#: ../system/translations.rst:4 +msgid "" +"Translations of Zammad are processed centrally in our `Weblate instance " +"`_. This allows non-developers to review " +"and update translation texts of the language they actually speak." msgstr "" +"Tłumaczenia Zammada są przetwarzane centralnie w naszej instancji `Weblate " +"`_. Dzięki temu osoby niebędące " +"programistami mogą przeglądać i aktualizować teksty tłumaczeń na język, " +"którym faktycznie mówią." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.avatar(60,60)}``" +#: ../system/translations.rst:9 +msgid "" +"Your language is in an incomplete translation state or has typos? Please " +"consider helping us in sorting this out! All you need is either a GitHub " +"account or to register directly in our instance." msgstr "" +"Twój język jest w niekompletnym tłumaczeniu lub zawiera literówki? Prosimy o " +"pomoc w rozwiązaniu tego problemu! Wszystko czego potrzebujesz to konto " +"GitHub lub zarejestrować się bezpośrednio w naszej instancji." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Address" -msgstr "" +#: ../system/translations.rst:13 +msgid "" +"Did you know? This is also where the documentation translations are handled. " +"🤓" +msgstr "Czy wiedziałeś? Tutaj również odbywa się tłumaczenie dokumentacji. 🤓" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.address}``" +#: ../system/translations.rst:15 +msgid "" +"Have a look in our :docs:`contribution section ` in the system documentation to get started!" msgstr "" +"Aby rozpocząć, zajrzyj do naszej :docs:`sekcji wkładu ` w dokumentacji systemu!" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created at" -msgstr "" +#: ../system/translations.rst:20 +msgid "Local Translations" +msgstr "Tłumaczenia lokalne" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_at}``" +#: ../system/translations.rst:22 +msgid "" +"Apart from these system translations, there's still local translations you " +"can manage. This is relevant if you added custom objects that require " +"translations or even custom states and priorities." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "2019-10-07 16:25:00 UTC" +#: ../system/translations.rst:None +msgid "Translation management screen within the admin menu" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Closing time" +#: ../system/translations.rst:31 +msgid "Updating Translations" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.close_at}``" +#: ../system/translations.rst:33 +msgid "" +"Because of how Zammad ships translations, the only way to update the system " +"translations is to update your Zammad installation. The benefit of this is " +"that you no longer need internet access during a Zammad upgrade as the " +"package has everything it requires already." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "2019-10-07 17:25:00 UTC" +#: ../system/translations.rst:39 +msgid "Translation of Custom Objects" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``3``, any number of articles existing in the ticket right now" +#: ../system/translations.rst:41 +msgid "" +"No problem at all! You can customize any translation locally, even if it is " +"not initially provided by the system." msgstr "" -#: ../system/version.rst:2 -msgid "Version" +#: ../system/translations.rst:44 +msgid "" +"Translation is supported for a broad number of features, including but not " +"limited to custom:" msgstr "" -#: ../system/version.rst:4 -msgid "Shows which version is currently being used on your Zammad-instance." +#: ../system/translations.rst:47 +msgid "Object Attributes" msgstr "" -#: ../manage/roles/admin-permissions.rst:53 -msgid "``admin.checklist``" -msgstr "" +#: ../system/translations.rst:48 +#, fuzzy +msgid "Ticket Macros" +msgstr "Makra" -#: ../manage/roles/admin-permissions.rst:54 -msgid ":doc:`Manage > Checklist `" +#: ../system/translations.rst:49 +msgid "Ticket Overviews" msgstr "" -#: ../manage/roles/admin-permissions.rst:83 -msgid "``admin.channel_whatsapp``" -msgstr "" +#: ../system/translations.rst:50 +#, fuzzy +msgid "Ticket Priorities" +msgstr "priorytet" -#: ../manage/roles/admin-permissions.rst:84 -msgid ":doc:`Channels > Whatsapp `" +#: ../system/translations.rst:51 +msgid "Ticket States" msgstr "" -#: ../manage/roles/admin-permissions.rst:124 -msgid "``admin.public_links``" +#: ../system/translations.rst:54 +msgid "Customizing Translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:125 -msgid ":doc:`Manage > Public Links `" +#: ../system/translations.rst:56 +msgid "" +"Within the translation screen, simply click on the **New Translation** " +"button." msgstr "" -#: ../manage/roles/admin-permissions.rst:151 -msgid "``admin.system_report``" +#: ../system/translations.rst:None +msgid "New translation dialog" msgstr "" -#: ../manage/roles/admin-permissions.rst:152 -msgid ":doc:`System > System Report `" +#: ../system/translations.rst:62 +msgid "" +"In the dialog you can immediately enter the exact translation source (if you " +"know it) and your custom translation text for it and click **Submit**." msgstr "" -#: ../manage/roles/admin-permissions.rst:166 -msgid "``admin.ticket_auto_assignment``" +#: ../system/translations.rst:65 +msgid "" +"Alternatively, try to search for translation suggestions in the list below. " +"Selecting an item from the list will pre-fill the translation source for you " +"and then you can just enter your custom translation." msgstr "" -#: ../manage/roles/admin-permissions.rst:167 -msgid ":ref:`Settings > Ticket > Auto Assignment `" +#: ../system/translations.rst:69 +msgid "" +"The target language will always default to your current language selection. " +"If you need to translate for a different language, simply change the " +"selection before submitting." msgstr "" -#: ../manage/roles/admin-permissions.rst:169 -msgid "``admin.ticket_duplicate_detection``" +#: ../system/translations.rst:73 +msgid "" +"All your custom translations will show up in the overview table when added. " +"And they will even persist across Zammad updates!" msgstr "" -#: ../manage/roles/admin-permissions.rst:170 -msgid ":ref:`Settings > Ticket > Duplicate Detection `" +#: ../system/translations.rst:76 +msgid "" +"Make sure to reload your browser if a translated string is not displayed." msgstr "" -#: ../manage/roles/admin-permissions.rst:172 -#, fuzzy -msgid "``admin.ticket_priority``" -msgstr "priorytet" +#: ../system/translations.rst:80 +msgid "Reverting to Original Translations" +msgstr "" -#: ../manage/roles/admin-permissions.rst:173 -msgid ":ref:`System > Objects >Ticket Priority `" +#: ../system/translations.rst:82 +msgid "" +"If you want to revert a custom translation to original text, simply use the " +"appropriate action within the row of the overview table." msgstr "" -#: ../manage/roles/admin-permissions.rst:175 -msgid "``admin.ticket_state``" +#: ../system/translations.rst:85 +msgid "" +"Depending on the type of the translation source, the action has a slightly " +"different name:" msgstr "" -#: ../manage/roles/admin-permissions.rst:176 -msgid ":ref:`System > Objects >Ticket State `" +#: ../system/translations.rst:88 +msgid "**Reset** for customized system translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:193 -msgid "``admin.webhook``" +#: ../system/translations.rst:89 +msgid "**Remove** for customized local translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:194 -msgid ":doc:`Manage > Webhook `" +#: ../system/translations.rst:91 +msgid "" +"In both cases, the action will remove the customized translation after a " +"confirmation." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:43 -msgid "``user_preferences.appearance``" +#: ../system/translations.rst:None +msgid "Screenshot showing the location of the Remove action" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:44 -msgid "Appearance configuration" +#: ../system/translations.rst:99 +msgid "Inline Translations" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:0 -msgid "Users can switch between dark, light and" +#: ../system/translations.rst:101 +msgid "" +"If you prefer a more hands-on approach, you can activate the inline or on-" +"screen translation feature by pressing ``ctrl`` + ``alt`` + ``t`` at any " +"time and on any screen." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:0 -msgid "automatic mode." +#: ../system/translations.rst:105 +msgid "" +"All customizable translation texts will be highlighted for you on the " +"screen. Just click into the highlighted area and update the text in place." msgstr "" -#: ../system/system-report.rst:2 -msgid "System Report" +#: ../system/translations.rst:None +msgid "Inline translation mode activated for the Overview screen" msgstr "" -#: ../system/system-report.rst:4 +#: ../system/translations.rst:112 msgid "" -"In this place you can't configure Zammad. Instead you can obtain a system " -"report about Zammad and its configuration." +"When finished editing, simply press ``ctrl`` + ``alt`` + ``t`` again to " +"deactivate." msgstr "" -#: ../system/system-report.rst:7 +#: ../system/translations.rst:117 msgid "" -"See the description in Zammad for an explanation. You can even find a " -"preview of the included data below the **Download** button." +"Even though it's available on any screen, the inline translation feature " +"requires admin permissions. It works only for the current language " +"selection. If you need to translate a different language, first change the " +"language in your :user-docs:`profile settings `." msgstr "" -#: ../system/system-report.rst:10 -msgid "" -"Zammad never sends this automatically to anyone. It is a manual process only " -"to provide better support based on your configuration." +#: ../system/version.rst:2 +msgid "Version" +msgstr "" + +#: ../system/version.rst:4 +msgid "Shows which version is currently being used on your Zammad-instance." msgstr "" #, fuzzy diff --git a/locale/pt_BR/LC_MESSAGES/admin-docs.po b/locale/pt_BR/LC_MESSAGES/admin-docs.po index 783a887b..256e427c 100644 --- a/locale/pt_BR/LC_MESSAGES/admin-docs.po +++ b/locale/pt_BR/LC_MESSAGES/admin-docs.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Zammad\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-11-06 10:31+0100\n" +"POT-Creation-Date: 2024-11-12 16:31+0100\n" "PO-Revision-Date: 2024-03-10 08:00+0000\n" "Last-Translator: Glauber Daniel Ribeiro \n" "Language-Team: Portuguese (Brazil) Checklist `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:56 msgid "``admin.channel_email``" msgstr "" -#: ../manage/roles/admin-permissions.rst:54 #: ../manage/roles/admin-permissions.rst:57 msgid ":doc:`Channels > Email `" msgstr "" -#: ../manage/roles/admin-permissions.rst:56 #: ../manage/roles/admin-permissions.rst:59 msgid "``admin.channel_facebook``" msgstr "" -#: ../manage/roles/admin-permissions.rst:57 #: ../manage/roles/admin-permissions.rst:60 msgid ":doc:`Channels > Facebook `" msgstr "" -#: ../manage/roles/admin-permissions.rst:58 #: ../manage/roles/admin-permissions.rst:61 msgid "" "Accessing Facebook tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:59 #: ../manage/roles/admin-permissions.rst:62 msgid "``admin.channel_formular``" msgstr "" -#: ../manage/roles/admin-permissions.rst:60 #: ../manage/roles/admin-permissions.rst:63 msgid ":doc:`Channels > Form `" msgstr "" -#: ../manage/roles/admin-permissions.rst:62 #: ../manage/roles/admin-permissions.rst:65 msgid "``admin.channel_google``" msgstr "" -#: ../manage/roles/admin-permissions.rst:63 #: ../manage/roles/admin-permissions.rst:66 msgid ":doc:`Channels > Google `" msgstr "" -#: ../manage/roles/admin-permissions.rst:65 #: ../manage/roles/admin-permissions.rst:68 msgid "``admin.channel_microsoft365``" msgstr "" -#: ../manage/roles/admin-permissions.rst:66 #: ../manage/roles/admin-permissions.rst:69 msgid ":doc:`Channels > Microsoft 365 `" msgstr "" -#: ../manage/roles/admin-permissions.rst:68 #: ../manage/roles/admin-permissions.rst:71 msgid "``admin.channel_sms``" msgstr "" -#: ../manage/roles/admin-permissions.rst:69 #: ../manage/roles/admin-permissions.rst:72 msgid ":doc:`Channels > SMS `" msgstr "" -#: ../manage/roles/admin-permissions.rst:71 #: ../manage/roles/admin-permissions.rst:74 msgid "``admin.channel_telegram``" msgstr "" -#: ../manage/roles/admin-permissions.rst:72 #: ../manage/roles/admin-permissions.rst:75 msgid ":doc:`Channels > Telegram `" msgstr "" -#: ../manage/roles/admin-permissions.rst:73 #: ../manage/roles/admin-permissions.rst:76 msgid "" "Accessing Telegram tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:74 #: ../manage/roles/admin-permissions.rst:77 msgid "``admin.channel_twitter``" msgstr "" -#: ../manage/roles/admin-permissions.rst:75 #: ../manage/roles/admin-permissions.rst:78 msgid ":doc:`Channels > Twitter `" msgstr "" -#: ../manage/roles/admin-permissions.rst:76 #: ../manage/roles/admin-permissions.rst:79 msgid "" "Accessing Twitter/X tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:77 #: ../manage/roles/admin-permissions.rst:80 msgid "``admin.channel_web``" msgstr "" -#: ../manage/roles/admin-permissions.rst:78 #: ../manage/roles/admin-permissions.rst:81 msgid ":doc:`Channels > Web `" msgstr "" -#: ../manage/roles/admin-permissions.rst:80 +#: ../manage/roles/admin-permissions.rst:83 +msgid "``admin.channel_whatsapp``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:84 +msgid ":doc:`Channels > Whatsapp `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:86 msgid "``admin.core_workflows``" msgstr "" -#: ../manage/roles/admin-permissions.rst:81 #: ../manage/roles/admin-permissions.rst:87 msgid ":doc:`System > Core Workflows `" msgstr "" -#: ../manage/roles/admin-permissions.rst:83 #: ../manage/roles/admin-permissions.rst:89 msgid "``admin.data_privacy``" msgstr "" -#: ../manage/roles/admin-permissions.rst:84 #: ../manage/roles/admin-permissions.rst:90 msgid ":doc:`System > Data Privacy `" msgstr "" -#: ../manage/roles/admin-permissions.rst:85 #: ../manage/roles/admin-permissions.rst:91 msgid "" "🔥 Be careful, it allows users to permanently delete data on the system." msgstr "" -#: ../manage/roles/admin-permissions.rst:86 #: ../manage/roles/admin-permissions.rst:92 msgid "``admin.group``" msgstr "" -#: ../manage/roles/admin-permissions.rst:87 #: ../manage/roles/admin-permissions.rst:93 msgid ":doc:`Manage > Groups `" msgstr "" -#: ../manage/roles/admin-permissions.rst:89 #: ../manage/roles/admin-permissions.rst:95 msgid "``admin.integration``" msgstr "" -#: ../manage/roles/admin-permissions.rst:90 #: ../manage/roles/admin-permissions.rst:96 msgid ":doc:`System > Integrations `" msgstr "" -#: ../manage/roles/admin-permissions.rst:92 #: ../manage/roles/admin-permissions.rst:98 msgid "``admin.knowledge_base``" msgstr "" -#: ../manage/roles/admin-permissions.rst:93 #: ../manage/roles/admin-permissions.rst:99 msgid ":doc:`Manage > Knowledge Base `" msgstr "" @@ -8739,57 +8722,46 @@ msgid "" "knowledge-base.html#editing-answers>`." msgstr "" -#: ../manage/roles/admin-permissions.rst:98 #: ../manage/roles/admin-permissions.rst:104 msgid "``admin.macro``" msgstr "" -#: ../manage/roles/admin-permissions.rst:99 #: ../manage/roles/admin-permissions.rst:105 msgid ":doc:`Manage > Macros `" msgstr "" -#: ../manage/roles/admin-permissions.rst:100 #: ../manage/roles/admin-permissions.rst:106 msgid "In some cases, macros may also require ``admin.tag``" msgstr "" -#: ../manage/roles/admin-permissions.rst:101 #: ../manage/roles/admin-permissions.rst:107 msgid "``admin.maintenance``" msgstr "" -#: ../manage/roles/admin-permissions.rst:102 #: ../manage/roles/admin-permissions.rst:108 msgid ":doc:`System > Maintenance `" msgstr "" -#: ../manage/roles/admin-permissions.rst:104 #: ../manage/roles/admin-permissions.rst:110 msgid "``admin.monitoring``" msgstr "" -#: ../manage/roles/admin-permissions.rst:105 #: ../manage/roles/admin-permissions.rst:111 msgid ":doc:`System > Monitoring `" msgstr "" -#: ../manage/roles/admin-permissions.rst:107 #: ../manage/roles/admin-permissions.rst:113 msgid "``admin.object``" msgstr "" -#: ../manage/roles/admin-permissions.rst:108 #: ../manage/roles/admin-permissions.rst:114 msgid ":doc:`System > Objects `" msgstr "" -#: ../manage/roles/admin-permissions.rst:110 #: ../manage/roles/admin-permissions.rst:116 msgid "``admin.organization``" msgstr "" -#: ../manage/roles/admin-permissions.rst:111 #: ../manage/roles/admin-permissions.rst:117 msgid ":doc:`Manage > Organizations `" msgstr "" @@ -8806,203 +8778,213 @@ msgstr "" msgid "They can even edit an organization's name, domain, and notes!" msgstr "" -#: ../manage/roles/admin-permissions.rst:115 #: ../manage/roles/admin-permissions.rst:121 msgid "``admin.overview``" msgstr "" -#: ../manage/roles/admin-permissions.rst:116 #: ../manage/roles/admin-permissions.rst:122 msgid ":doc:`Manage > Overviews`" msgstr "" -#: ../manage/roles/admin-permissions.rst:118 +#: ../manage/roles/admin-permissions.rst:124 +msgid "``admin.public_links``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:125 +msgid ":doc:`Manage > Public Links `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:127 msgid "``admin.package``" msgstr "" -#: ../manage/roles/admin-permissions.rst:119 #: ../manage/roles/admin-permissions.rst:128 msgid ":doc:`System > Packages `" msgstr "" -#: ../manage/roles/admin-permissions.rst:121 #: ../manage/roles/admin-permissions.rst:130 msgid "``admin.report_profile``" msgstr "" -#: ../manage/roles/admin-permissions.rst:122 #: ../manage/roles/admin-permissions.rst:131 msgid ":doc:`Manage > Report Profiles `" msgstr "" -#: ../manage/roles/admin-permissions.rst:123 #: ../manage/roles/admin-permissions.rst:132 msgid "Access to view reports: ``report``" msgstr "" -#: ../manage/roles/admin-permissions.rst:124 #: ../manage/roles/admin-permissions.rst:133 msgid "``admin.role``" msgstr "" -#: ../manage/roles/admin-permissions.rst:125 #: ../manage/roles/admin-permissions.rst:134 msgid ":doc:`Manage > Roles `" msgstr "" -#: ../manage/roles/admin-permissions.rst:127 #: ../manage/roles/admin-permissions.rst:136 msgid "``admin.scheduler``" msgstr "" -#: ../manage/roles/admin-permissions.rst:128 #: ../manage/roles/admin-permissions.rst:137 msgid ":doc:`Manage > Scheduler `" msgstr "" -#: ../manage/roles/admin-permissions.rst:129 #: ../manage/roles/admin-permissions.rst:138 msgid "For automation on tickets" msgstr "" -#: ../manage/roles/admin-permissions.rst:130 #: ../manage/roles/admin-permissions.rst:139 msgid "``admin.security``" msgstr "" -#: ../manage/roles/admin-permissions.rst:131 #: ../manage/roles/admin-permissions.rst:140 msgid ":doc:`Settings > Security `" msgstr "" -#: ../manage/roles/admin-permissions.rst:132 #: ../manage/roles/admin-permissions.rst:141 msgid "Settings of Zammad. This also covers third party authentications." msgstr "" -#: ../manage/roles/admin-permissions.rst:133 #: ../manage/roles/admin-permissions.rst:142 msgid "``admin.session``" msgstr "" -#: ../manage/roles/admin-permissions.rst:134 #: ../manage/roles/admin-permissions.rst:143 msgid ":doc:`System > Sessions `" msgstr "" -#: ../manage/roles/admin-permissions.rst:136 #: ../manage/roles/admin-permissions.rst:145 msgid "``admin.setting_system``" msgstr "" -#: ../manage/roles/admin-permissions.rst:137 #: ../manage/roles/admin-permissions.rst:146 msgid ":doc:`Settings > System `" msgstr "" -#: ../manage/roles/admin-permissions.rst:139 #: ../manage/roles/admin-permissions.rst:148 msgid "``admin.sla``" msgstr "" -#: ../manage/roles/admin-permissions.rst:140 #: ../manage/roles/admin-permissions.rst:149 msgid ":doc:`Manage > SLAs `" msgstr "" -#: ../manage/roles/admin-permissions.rst:142 +#: ../manage/roles/admin-permissions.rst:151 +msgid "``admin.system_report``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:152 +msgid ":doc:`System > System Report `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:154 msgid "``admin.tag``" msgstr "" -#: ../manage/roles/admin-permissions.rst:143 #: ../manage/roles/admin-permissions.rst:155 msgid ":doc:`Manage > Tags `" msgstr "" -#: ../manage/roles/admin-permissions.rst:145 #: ../manage/roles/admin-permissions.rst:157 msgid "``admin.template``" msgstr "" -#: ../manage/roles/admin-permissions.rst:146 #: ../manage/roles/admin-permissions.rst:158 msgid ":doc:`Manage > Templates `" msgstr "" -#: ../manage/roles/admin-permissions.rst:148 #: ../manage/roles/admin-permissions.rst:160 msgid "``admin.text_module``" msgstr "" -#: ../manage/roles/admin-permissions.rst:149 #: ../manage/roles/admin-permissions.rst:161 msgid ":doc:`Manage > Text Modules `" msgstr "" -#: ../manage/roles/admin-permissions.rst:151 #: ../manage/roles/admin-permissions.rst:163 msgid "``admin.ticket``" msgstr "" -#: ../manage/roles/admin-permissions.rst:152 #: ../manage/roles/admin-permissions.rst:164 msgid ":doc:`Settings > Tickets `" msgstr "" -#: ../manage/roles/admin-permissions.rst:153 #: ../manage/roles/admin-permissions.rst:165 #, fuzzy msgid "Does not grant access to :doc:`/misc/composer`" msgstr "Dê uma olhada em ✍️ :doc:`/misc/composer`." -#: ../manage/roles/admin-permissions.rst:154 +#: ../manage/roles/admin-permissions.rst:166 +msgid "``admin.ticket_auto_assignment``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:167 +msgid ":ref:`Settings > Ticket > Auto Assignment `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:169 +msgid "``admin.ticket_duplicate_detection``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:170 +msgid ":ref:`Settings > Ticket > Duplicate Detection `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:172 +#, fuzzy +msgid "``admin.ticket_priority``" +msgstr "Prioridade" + +#: ../manage/roles/admin-permissions.rst:173 +msgid ":ref:`System > Objects >Ticket Priority `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:175 +#, fuzzy +msgid "``admin.ticket_state``" +msgstr "Atributos do ticket" + +#: ../manage/roles/admin-permissions.rst:176 +msgid ":ref:`System > Objects >Ticket State `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:178 msgid "``admin.time_accounting``" msgstr "" -#: ../manage/roles/admin-permissions.rst:155 #: ../manage/roles/admin-permissions.rst:179 msgid ":doc:`Manage > Time Accounting `" msgstr "" -#: ../manage/roles/admin-permissions.rst:156 #: ../manage/roles/admin-permissions.rst:180 msgid "Also allows the export of timekeeping records." msgstr "" -#: ../manage/roles/admin-permissions.rst:157 #: ../manage/roles/admin-permissions.rst:181 msgid "``admin.translation``" msgstr "" -#: ../manage/roles/admin-permissions.rst:158 #: ../manage/roles/admin-permissions.rst:182 msgid ":doc:`System > Translations `" msgstr "" -#: ../manage/roles/admin-permissions.rst:159 #: ../manage/roles/admin-permissions.rst:183 msgid "Also enables inline translation" msgstr "" -#: ../manage/roles/admin-permissions.rst:160 #: ../manage/roles/admin-permissions.rst:184 msgid "``admin.trigger``" msgstr "" -#: ../manage/roles/admin-permissions.rst:161 #: ../manage/roles/admin-permissions.rst:185 msgid ":doc:`Manage > Triggers `" msgstr "" -#: ../manage/roles/admin-permissions.rst:163 #: ../manage/roles/admin-permissions.rst:187 msgid "``admin.user``" msgstr "" -#: ../manage/roles/admin-permissions.rst:164 #: ../manage/roles/admin-permissions.rst:188 msgid ":doc:`Manage > Users `" msgstr "" @@ -9021,6 +9003,14 @@ msgid "" "from-users-perspective>` ." msgstr "" +#: ../manage/roles/admin-permissions.rst:193 +msgid "``admin.webhook``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:194 +msgid ":doc:`Manage > Webhook `" +msgstr "" + #: ../manage/roles/agent-permissions.rst:2 msgid "Agent Permissions" msgstr "" @@ -9441,37 +9431,47 @@ msgid "than the user that generated them." msgstr "" #: ../manage/roles/user-preferences-permissions.rst:43 +msgid "``user_preferences.appearance``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:44 +#, fuzzy +msgid "Appearance configuration" +msgstr "Configuração" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "Users can switch between dark, light and" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "automatic mode." +msgstr "" + #: ../manage/roles/user-preferences-permissions.rst:47 msgid "``user_preferences.avatar``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:44 #: ../manage/roles/user-preferences-permissions.rst:48 #, fuzzy msgid "Avatar settings" msgstr "Configurações" -#: ../manage/roles/user-preferences-permissions.rst:45 #: ../manage/roles/user-preferences-permissions.rst:49 msgid "Override the default Gravatar with a custom avatar" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:46 #: ../manage/roles/user-preferences-permissions.rst:50 msgid "``user_preferences.calendar``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:47 #: ../manage/roles/user-preferences-permissions.rst:51 msgid "Configure the calendar feed" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:49 #: ../manage/roles/user-preferences-permissions.rst:53 msgid "``user_preferences.device``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:50 #: ../manage/roles/user-preferences-permissions.rst:54 msgid "Manage device login sessions" msgstr "" @@ -9488,22 +9488,18 @@ msgstr "" msgid "To learn more, see :doc:`/manage/trigger/system-notifications`." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:54 #: ../manage/roles/user-preferences-permissions.rst:58 msgid "``user_preferences.language``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:55 #: ../manage/roles/user-preferences-permissions.rst:59 msgid "Configure the UI locale/language" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:57 #: ../manage/roles/user-preferences-permissions.rst:61 msgid "``user_preferences.linked_accounts``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:58 #: ../manage/roles/user-preferences-permissions.rst:62 #, fuzzy msgid "Account linking" @@ -9528,7 +9524,6 @@ msgstr "" msgid "is the only way users can utilize third-party logins." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:63 #: ../manage/roles/user-preferences-permissions.rst:67 msgid "``user_preferences.notifications``" msgstr "" @@ -9557,7 +9552,6 @@ msgstr "" msgid "Customers can't receive ticket notifications at all." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:69 #: ../manage/roles/user-preferences-permissions.rst:73 msgid "``user_preferences.out_of_office``" msgstr "" @@ -9582,7 +9576,6 @@ msgstr "" msgid "they're replacing." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:75 #: ../manage/roles/user-preferences-permissions.rst:79 msgid "``user_preferences.overview_sorting``" msgstr "" @@ -9611,12 +9604,10 @@ msgstr "" msgid "overviews has no effect on custom orders." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:82 #: ../manage/roles/user-preferences-permissions.rst:86 msgid "``user_preferences.password``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:83 #: ../manage/roles/user-preferences-permissions.rst:87 msgid "Change account password" msgstr "" @@ -9633,7 +9624,6 @@ msgstr "" msgid "your only allowed authentication method." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:87 #: ../manage/roles/user-preferences-permissions.rst:91 msgid "``user_preferences.two_factor_authentication``" msgstr "" @@ -9671,7 +9661,7 @@ msgstr "" #: ../manage/scheduler.rst:19 msgid "" -"Schedulers can be used to send periodic reminder emails. Use :doc:`/system/" +"Schedulers can be used to send periodic reminder emails. Use :doc:`/misc/" "variables` to build highly-customized email templates." msgstr "" @@ -10689,7 +10679,7 @@ msgstr "" #: ../manage/text-modules.rst:57 msgid "" -"The example text modules below use :doc:`/system/variables` to dynamically " +"The example text modules below use :doc:`/misc/variables` to dynamically " "insert information like the customer's or agent's names." msgstr "" @@ -11046,8 +11036,8 @@ msgstr "" #: ../misc/object-conditions/basics.rst:144 #: ../misc/object-conditions/basics.rst:160 #: ../misc/object-conditions/basics.rst:168 -#: ../misc/object-conditions/basics.rst:178 ../settings/ticket.rst:2 -#: ../system/variables/ticket.rst:2 +#: ../misc/object-conditions/basics.rst:178 ../misc/variables/ticket.rst:2 +#: ../settings/ticket.rst:2 msgid "Ticket" msgstr "" @@ -11293,7 +11283,7 @@ msgstr "" #: ../manage/trigger/how-do-they-work.rst:79 msgid "" -"Certain actions (such as *email*, *SMS* and *notes*) support :doc:`/system/" +"Certain actions (such as *email*, *SMS* and *notes*) support :doc:`/misc/" "variables`, which can be used to build highly-customized message templates." msgstr "" @@ -11322,7 +11312,7 @@ msgstr "" msgid "" "You can also combine static text with placeholders for text fields. Remember " "that the placeholders' values have to be known during trigger runtime. Learn " -"more about :doc:`/system/variables`." +"more about :doc:`/misc/variables`." msgstr "" #: ../manage/trigger/how-do-they-work.rst:105 @@ -12293,7 +12283,7 @@ msgstr "" msgid "" "When switched on, a code editor will be shown below, where you can configure " "custom payload for your webhook in JSON format. To insert supported :doc:`/" -"system/variables` use ``::`` or ``#{`` shortcuts for autocomplete." +"misc/variables` use ``::`` or ``#{`` shortcuts for autocomplete." msgstr "" #: ../manage/webhook/add.rst:103 @@ -14926,12099 +14916,11987 @@ msgid "" "powerful conditions with AND/OR relations." msgstr "" -#: ../settings/branding.rst:10 -msgid "Product Name" -msgstr "" +#: ../misc/variables.rst:2 +msgid "Variables" +msgstr "Variáveis" -#: ../settings/branding.rst:7 +#: ../misc/variables.rst:4 msgid "" -"Defines the name of the application, shown in the web interface, tabs and " -"title bar of the web browser." +"Please note that this is just an overview of available variables. It might " +"be incomplete or variables might not be available within some functions. If " +"you're missing variables or are not sure if something is not working as " +"expected, feel free to ask over at the `Community `_." msgstr "" -#: ../settings/branding.rst:10 -msgid "Default value: ``Zammad Helpdesk``" +#: ../misc/variables.rst:10 +msgid "" +"Variables can be called by typing ``::`` (just like text modules in the " +"frontend), as long as you're in a supported text field within the backend. " +"Zammad will display all variables being available within this context and " +"replace it to the variable as soon as you selected an entry." msgstr "" -#: ../settings/branding.rst:13 -msgid "Will be shown in the app and is included in email footers." +#: ../misc/variables.rst:15 +msgid "" +"You have an empty field which you referenced and it appears as ``-``? That's " +"currently working as designed - you might want to ensure that these fields " +"always have a value." msgstr "" -#: ../settings/branding.rst:19 -msgid "Logo" -msgstr "" +#: ../misc/variables.rst:20 +msgid "Variable Categories" +msgstr "Categorias de Variável" -#: ../settings/branding.rst:16 -msgid "Defines the logo of the application, shown in the login page of Zammad." +#: ../misc/variables.rst:31 +msgid "Wait, What About Custom Objects?" msgstr "" -#: ../settings/branding.rst:18 +#: ../misc/variables.rst:33 msgid "" -"Ensure to hit the \"Submit\" button after uploading the logo. Otherwise your " -"change will not be saved." +"Good point! Of course, we can't predict what objects you might create, but " +"we can give you a hint on how to put the puzzle together to get your custom " +"values." msgstr "" -#: ../settings/branding.rst:22 +#: ../misc/variables.rst:36 msgid "" -"Allows to set the default language of the Zammad instance. The here defined " -"locale mostly acts as a fallback for:" +"For this, we'll talk about the inner part of the variable (so everything " +"within ``#{}``), please put the outer part around to have a valid variable. " +"The first part of the variable name consist of the object type. Currently " +"these are:" msgstr "" -#: ../settings/branding.rst:25 -msgid "user preferences (if Zammad can't detect the users locale)" -msgstr "" +#: ../misc/variables.rst:41 +msgid "Ticket (``ticket``)" +msgstr "Chamado (``chamado``)" -#: ../settings/branding.rst:26 -msgid "CSV output (reporting, time accounting)" -msgstr "" +#: ../misc/variables.rst:42 +msgid "User (``user``)" +msgstr "Usuário (``usuário``)" -#: ../settings/branding.rst:30 -msgid "Define the timezone of your Zammad installation." -msgstr "" +#: ../misc/variables.rst:43 +msgid "Organization (``organization``)" +msgstr "Organização (``organização``)" -#: ../settings/branding.rst:32 +#: ../misc/variables.rst:44 +msgid "Group (``group``)" +msgstr "Grupo (``grupo``)" + +#: ../misc/variables.rst:46 msgid "" -"This does not have any effect on timings for your agents or how Zammad " -"stores date and time values." +"The second part is the name of the attribute. This is the name you define " +"during object creation and can be found within the object attribute menu at " +"any time. The first and second part of a variable is divided by a point, e." +"g.: ``ticket.number`` which will in total be ``#{ticket.number}``." msgstr "" -#: ../settings/branding.rst:35 -msgid "Changing this value has direct consequences on the following areas:" +#: ../misc/variables.rst:51 +msgid "" +"Now, in some situations it's possible that you'll need to use a third part. " +"The best example for such a situation would be a ``select`` or ``tree-" +"select`` field which will by default return the key value, not it's display " +"name. For this, just extend your variable with ``.value``. This will result " +"in ``#{ticket.select.value}``." msgstr "" -#: ../settings/branding.rst:37 -msgid ":doc:`/manage/scheduler` tasks" -msgstr "" +#: ../misc/variables.rst:60 +#, fuzzy +msgid "Using Translated Variables" +msgstr "Traduções" -#: ../settings/branding.rst:38 -msgid "search indexing (and thus reporting)" +#: ../misc/variables.rst:62 +msgid "" +"If you want to use a translated variable in triggers or schedulers, you can " +"extend the placeholder like this: ``#{t(ticket.state.name)}``. The ``t`` " +"tells Zammad to search for fitting translated strings. The used output " +"language is based on the system language of Zammad which you can set in the " +"admin panel under :doc:`/settings/branding` or based on the selected locale " +"in the trigger/scheduler edit dialog." msgstr "" -#: ../settings/branding.rst:40 -#, fuzzy -msgid "calendar subscriptions" -msgstr "Descrição" +#: ../misc/variables.rst:69 +msgid "" +"A possible use-case: you want to send your customers updates on tickets via " +"trigger or scheduler which should include the state of the ticket. Using the " +"default ``#{ticket.state.name}`` (without the translation flag ``t()``) " +"would lead to the output of the original (english) name of the state." +msgstr "" -#: ../settings/branding.rst:41 -msgid "browser printing" +#: ../misc/variables.rst:75 +msgid "Date and Time Formatting" msgstr "" -#: ../settings/branding.rst:43 +#: ../misc/variables.rst:77 msgid "" -"Please note that some of above are fallbacks in case Zammad could not detect " -"the agents timezone correctly." +"The system (trigger/scheduler selected) locale and timezone predefines a " +"default format of date and timestamp. This format is customizable by using " +"the ``dt()`` method." msgstr "" -#: ../settings/branding.rst:77 -msgid "Pretty Date" +#: ../misc/variables.rst:79 +msgid "The method arguments are as follows:" msgstr "" -#: ../settings/branding.rst:47 -msgid "" -"This setting allows you to define how Zammad should display time stamps " -"within the interface to all users." +#: ../misc/variables.rst:81 +msgid "The date or timestamp variable you want to format." msgstr "" -#: ../settings/branding.rst:50 -msgid "" -"This does not have any effect on how Zammad returns e.g. time values via " -"variables." +#: ../misc/variables.rst:82 +msgid "The output format string." msgstr "" -#: ../settings/branding.rst:77 +#: ../misc/variables.rst:83 +msgid "The timezone to apply (optional)." +msgstr "" + +#: ../misc/variables.rst:85 +#: ../system/objects/external-data-source-example.rst:23 #, fuzzy -msgid "Choose in between the following options:" -msgstr "Lá você poderá editar as seguintes configurações:" +msgid "**Example:**" +msgstr "**Por exemplo:**" -#: ../settings/branding.rst:64 -msgid "relative" +#: ../misc/variables.rst:86 +msgid "" +"``#{dt(ticket.updated_at, \"%A %Y-%m-%d %H:%M in the office\", \"Europe/" +"Berlin\")}``" msgstr "" -#: ../settings/branding.rst:55 +#: ../misc/variables.rst:87 +msgid "Monday, 2024-03-18 15:31 in the office" +msgstr "" + +#: ../misc/variables.rst:89 msgid "" -"This timestamp shows a relative time span until it switches to a date. Over " -"time, it will change as follows:" +"If you want to use our example, make sure to paste the string above without " +"formatting (``CTRL+Shift+v``), otherwise it won't work." msgstr "" -#: ../settings/branding.rst:58 -msgid "just now" +#: ../misc/variables.rst:93 +msgid "The following table lists available format directives:" msgstr "" -#: ../settings/branding.rst:59 -msgid "5 minutes ago" +#: ../misc/variables.rst:99 +msgid "Parameter" msgstr "" -#: ../settings/branding.rst:60 -msgid "3 days 1 hour ago" +#: ../misc/variables.rst:102 +msgid "``%Y``" msgstr "" -#: ../settings/branding.rst:61 -msgid "``03/04/2022``" +#: ../misc/variables.rst:103 +msgid "Year with 4 digits" msgstr "" -#: ../settings/branding.rst:63 -msgid "Hovering the timestamp helps, you'll always get a clean timestamp then." +#: ../misc/variables.rst:104 +msgid "Use ``%y`` for year with 2 digits" msgstr "" -#: ../settings/branding.rst:71 -msgid "absolute" +#: ../misc/variables.rst:105 +msgid "``%m``" msgstr "" -#: ../settings/branding.rst:67 -msgid "" -"This timestamp always includes the week day. For one week after creation, " -"the timestamp will not contain the date itself: Thursday 18:35." +#: ../misc/variables.rst:106 +msgid "Month of year (as number with zero-padding)" msgstr "" -#: ../settings/branding.rst:71 -msgid "After a week it will switch to: ``Friday 4. Mar 16:00``." +#: ../misc/variables.rst:107 +msgid "Use ``%-m`` for month without zero-padding" msgstr "" -#: ../settings/branding.rst:76 -msgid "timestamp" +#: ../misc/variables.rst:108 +msgid "``%d``" msgstr "" -#: ../settings/branding.rst:74 -msgid "" -"This will cause Zammad to show a complete timestamp according to your locale " -"defaults. For English this could be e.g. ``2022/12/03 2:40 pm`` or for " -"German e.g. ``12.03.2022 14:40``." +#: ../misc/variables.rst:109 +msgid "Day of month (as number with zero-padding)" msgstr "" -#: ../settings/branding.rst:78 -msgid "Default setting: ``relative``." +#: ../misc/variables.rst:110 +msgid "Use ``%e`` for day without zero-padding" msgstr "" -#: ../settings/security.rst:2 -msgid "Security" +#: ../misc/variables.rst:111 +msgid "``%H``" msgstr "" -#: ../settings/security.rst:4 -msgid "" -"For your overview we split each tab within security settings into its own " -"page:" +#: ../misc/variables.rst:112 +msgid "Hour of day in 24h notation with zero-padding" msgstr "" -#: ../settings/security/base.rst:2 ../settings/system/base.rst:2 -#: ../settings/ticket.rst:8 -msgid "Base" +#: ../misc/variables.rst:113 +msgid "Use ``%k`` for hour without zero-padding" msgstr "" -#: ../settings/security/base.rst:5 -msgid "New User Accounts" +#: ../misc/variables.rst:114 +msgid "``%I``" msgstr "" -#: ../settings/security/base.rst:9 +#: ../misc/variables.rst:115 +msgid "Hour of day in 12h notation with zero-padding" +msgstr "" + +#: ../misc/variables.rst:116 msgid "" -"Activates the `register as a new customer` function on the login page. If " -"set to ``no`` only administrators or agents can create new accounts manually." +"Use ``%l`` for hour without zero-padding and ``%p`` / ``%P`` for meridian " +"indicator" msgstr "" -#: ../settings/security/base.rst:13 ../settings/security/base.rst:38 -#: ../settings/security/base.rst:66 -msgid "Default setting: ``yes``" +#: ../misc/variables.rst:117 +msgid "``%M``" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing activated \"New User Accounts\" setting" +#: ../misc/variables.rst:118 +msgid "Minute of hour" msgstr "" -#: ../settings/security/base.rst:22 -msgid "" -"Deactivation of above function **does not** deactivate automatic account " -"creation! This means: If a user writes e.g. an email to Zammad and has no " -"account yet, Zammad will automatically create the account. User accounts are " -"a direct dependency of tickets and thus technically mandatory." +#: ../misc/variables.rst:120 +msgid "``%S``" msgstr "" -#: ../settings/security/base.rst:29 -msgid "Lost Password" +#: ../misc/variables.rst:121 +msgid "Second of Minute" msgstr "" -#: ../settings/security/base.rst:33 -msgid "" -"Activates the `lost password` function on the login page. If set to ``no`` " -"only administrators may change the user's password - users may update their " -"own password if they're still logged in and they have the required :doc:" -"`permission `." +#: ../misc/variables.rst:123 +msgid "``%A``" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing activated \"Lost Password\" setting" +#: ../misc/variables.rst:124 +msgid "Weekday name" msgstr "" -#: ../settings/security/base.rst:49 -msgid "" -"With third party authentications - but especially LDAP - you may want to " -"disable this function. Zammad **will not** change third party login " -"passwords and instead set or change the local password!" +#: ../misc/variables.rst:125 +msgid "Use ``%a`` for abbreviated name or ``%^A`` for uppercase name" msgstr "" -#: ../settings/security/base.rst:56 -#, fuzzy -msgid "Password Login" -msgstr "Senha" +#: ../misc/variables.rst:126 +msgid "``%B``" +msgstr "" -#: ../settings/security/base.rst:60 -msgid "" -"Activates the username & password login by default and if no third-party " -"login is activated. Disabling password login on the Zammad login page only " -"takes effect if you enable any :doc:`third-party`." +#: ../misc/variables.rst:127 +msgid "Month name" msgstr "" -#: ../settings/security/base.rst:64 -msgid "See :doc:`third-party` for supported third-party logins." +#: ../misc/variables.rst:128 +msgid "Use ``%b`` for abbreviated name" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing de-activated \"Password Login\" setting" +#: ../misc/variables.rst:129 +msgid "``%U``" msgstr "" -#: ../settings/security/base.rst:77 -msgid "" -"To help administrators to overcome \"login issues\", Zammad automatically " -"offers a password request for administrator users. This allows you to adjust " -"Third-Party applications even if the login does no longer work!" +#: ../misc/variables.rst:130 +msgid "Week number of current year" msgstr "" -#: ../settings/security/base.rst:84 -msgid "Session Timeout" +#: ../misc/variables.rst:131 +msgid "Use ``%W`` for a different calculation method" msgstr "" -#: ../settings/security/base.rst:86 +#: ../misc/variables.rst:134 msgid "" -"All settings below by default are set to ``4 weeks``. Session Timeout " -"defines the life time of a users session. As soon as it's reached, Zammad " -"will automatically log off the session in question." +"We support the known format directives for the Ruby built-in method " +"``strftime`` of the ``DateTime`` class. For more information, see `here " +"`_." msgstr "" -#: ../settings/security/base.rst:91 +#: ../misc/variables/article.rst:2 +msgid "Articles" +msgstr "Artigos" + +#: ../misc/variables/article.rst:4 ../misc/variables/config.rst:4 +#: ../misc/variables/current-user.rst:4 ../misc/variables/ticket.rst:4 msgid "" -"Zammad takes the highest value set assigned for the user based on the " -"permissions." +"If you're missing variables or are not sure if something is not working as " +"expected, feel free to ask over at the `Community `_." msgstr "" -#: ../settings/security/base.rst:94 -msgid "``admin``" +#: ../misc/variables/article.rst:6 +msgid "" +"Below you can find all available ticket article-based variables within " +"Zammad. These can be called via triggers for example. If you're unsure if " +"Zammad does support variables at the point you're at, you can try to type " +"``::`` to check." msgstr "" -#: ../settings/security/base.rst:96 -msgid "``ticket.customer``" +#: ../misc/variables/article.rst:9 ../misc/variables/config.rst:9 +#: ../misc/variables/ticket.rst:9 +msgid "" +"The below list gives you an example what kind of data you can expect, it's " +"not intended to explain the data itself." msgstr "" -#: ../settings/security/base.rst:97 -msgid "``default`` (fallback if user doesn't have above permissions set)" +#: ../misc/variables/article.rst:11 +msgid "Article Variables" msgstr "" -#: ../settings/security/base.rst:99 -msgid "" -"All settings act independently from each other allowing you to disable the " -"timeouts for e.g. admins, but not agents." +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "name" msgstr "" -#: ../settings/security/base.rst:115 -#: ../system/integrations/checkmk/api-reference.rst:13 -msgid "Example" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "variable" msgstr "" -#: ../settings/security/base.rst:107 -msgid "Let's suppose you configured the following session timeouts" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "example" +msgstr "exemplo" + +#: ../misc/variables/article.rst:1 +msgid "Article > Cc" msgstr "" -#: ../settings/security/base.rst:104 -msgid "default: 3 weeks" +#: ../misc/variables/article.rst:1 +msgid "``#{article.cc}``" msgstr "" -#: ../settings/security/base.rst:105 -msgid "admin: 2 weeks" +#: ../misc/variables/article.rst:1 +msgid "``jdoe@example.com, company@example.com``" msgstr "" -#: ../settings/security/base.rst:106 -msgid "ticket.agent: 4 weeks" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Address" msgstr "" -#: ../settings/security/base.rst:107 -msgid "ticket.customer: 1 week" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.address}``" msgstr "" -#: ../settings/security/base.rst:115 -msgid "This results in the following situations" +#: ../misc/variables/article.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set in user object" msgstr "" -#: ../settings/security/base.rst:110 -msgid "a user with ``admin`` permission will have a timeout of 2 weeks" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Department" msgstr "" -#: ../settings/security/base.rst:111 -msgid "" -"a user with ``admin`` and ``ticket.agent`` permissions will have a timeout " -"of 2 weeks" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.department}``" msgstr "" -#: ../settings/security/base.rst:113 -msgid "" -"a user with ``ticket.customer`` permission will have a timeout of 1 week" +#: ../misc/variables/article.rst:1 +msgid "``Sales`` or empty if not set in user object" msgstr "" -#: ../settings/security/base.rst:115 -msgid "" -"a user with neither ``admin``, ``ticket.agent`` nor ``ticket.customer`` " -"permissions will have a timeout of 3 weeks" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Email" msgstr "" -#: ../settings/security/password.rst:4 -msgid "" -"This section allows you to define password requirements for the local user " -"accounts." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.email}``" msgstr "" -#: ../settings/security/password.rst:9 -msgid "" -"Zammad does **not** allow you to change your LDAP password, instead, it will " -"set a password in its local database which might confuse your users. This " -"might be addressed in the future by `#1169 `_." -msgstr "" - -#: ../settings/security/password.rst:14 -msgid "**Exception for admins**" +#: ../misc/variables/article.rst:1 +msgid "``jdoe@example.com``" msgstr "" -#: ../settings/security/password.rst:16 -msgid "" -"Please note that below password policies *do not* affect administrators " -"setting passwords on user accounts. While this seems strange and not safe we " -"believe that an administrator knowing an user's password is insecure as well." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Fax" msgstr "" -#: ../settings/security/password.rst:21 -msgid "The suggested workflow is either:" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.fax}``" msgstr "" -#: ../settings/security/password.rst:23 -msgid "" -"to use third party logins to not require local passwords at all **- or -**" +#: ../misc/variables/article.rst:1 +msgid "``+4930123456789`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:25 -msgid "to require your *user to reset the password* upon first login." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Firstname" msgstr "" -#: ../settings/security/password.rst:27 -msgid "" -"This way administrators are not required to set a user's password at all!" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.firstname}``" msgstr "" -#: ../settings/security/password.rst:31 -msgid "Maximum Failed Logins" +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Joe`` or empty if not set" msgstr "" -#: ../settings/security/password.rst:33 -msgid "" -"You can choose a value between ``4`` and ``20``. This defines how often a " -"login to a user account may fail until Zammad will lock it. Your users can " -"always use the \"forgot password\" function to change their password and " -"unlock their account." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Lastname" msgstr "" -#: ../settings/security/password.rst:38 -msgid "The default value is ``10``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.lastname}``" msgstr "" -#: ../settings/security/password.rst:42 -msgid "Beside changing the user's password, you can also unlock accounts via" +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +#: ../misc/variables/ticket.rst:1 +msgid "``Doe`` or empty if not set" msgstr "" -#: ../settings/security/password.rst:44 -msgid ":ref:`user management list `" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Login" msgstr "" -#: ../settings/security/password.rst:45 -msgid ":docs:`console `" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.login}``" msgstr "" -#: ../settings/security/password.rst:46 -msgid ":docs:`API `" +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +#: ../misc/variables/ticket.rst:1 +msgid "``jdoe``" msgstr "" -#: ../settings/security/password.rst:50 -msgid "Failed logins via LDAP no longer lock accounts." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Mobile" msgstr "" -#: ../settings/security/password.rst:53 -msgid "2 Lower Case And 2 Upper Case Characters" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.mobile}``" msgstr "" -#: ../settings/security/password.rst:55 -msgid "" -"You can add complexity to passwords by enforcing at least 2 upper and lower " -"case characters." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Note" msgstr "" -#: ../settings/security/password.rst:58 ../settings/security/password.rst:83 -msgid "The default value is ``no``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.note}``" msgstr "" -#: ../settings/security/password.rst:62 -msgid "Minimum Length" +#: ../misc/variables/article.rst:1 +msgid "``Some note about user`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:64 -msgid "" -"This defines the minimum password length required for users to provide (from " -"``4`` to ``20``)." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Phone" msgstr "" -#: ../settings/security/password.rst:67 -msgid "The default value is ``6``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.phone}``" msgstr "" -#: ../settings/security/password.rst:71 -msgid "Digit Required" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > VIP" msgstr "" -#: ../settings/security/password.rst:73 -msgid "This enforces your users to use at least one digit within the password." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.vip}``" msgstr "" -#: ../settings/security/password.rst:75 -msgid "The default value is ``yes``." +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +msgid "``true`` or ``false``" msgstr "" -#: ../settings/security/password.rst:78 -msgid "Special Character Required" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Web" msgstr "" -#: ../settings/security/password.rst:80 -msgid "" -"This setting allows you to improve your password quality even more by " -"enforcing the password to contain at least one special character." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.web}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:2 -msgid "SSL Certificates" +#: ../misc/variables/article.rst:1 +msgid "``https://zammad.com`` or empty if not set in user object" msgstr "" -#: ../settings/security/ssl-certificates.rst:7 -msgid "" -"Zammad offers the possibility to upload custom certificates and custom " -"Certificate Authority (CA) certificates. This can be useful if you want to " -"connect Zammad the secure way to other systems which are using custom " -"certificates." +#: ../misc/variables/article.rst:1 +msgid "Article > Created" msgstr "" -#: ../settings/security/ssl-certificates.rst:12 -msgid "" -"An example usecase might be: You have an internal LDAP server that is not " -"accessible from the internet, and you want a SSL-encrypted connection, using " -"a custom certificate." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_at}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:19 -msgid "" -"You should have an existing custom certificate file and/or a custom CA " -"certificate file, which you want to add to Zammad. As filetype ``.crt`` is " -"supported and the certificate format has to be PEM (Base64 ASCII)." +#: ../misc/variables/article.rst:1 +msgid "``2019-10-08 15:24:47 UTC``" msgstr "" -#: ../settings/security/ssl-certificates.rst:25 -msgid "" -"When you import a custom CA certificate, all certificates generated with " -"this are trusted. This can be useful if you have more than one system/" -"certificate you want to connect to and the certificates are issued from the " -"same custom CA." +#: ../misc/variables/article.rst:1 +msgid "Article > From" msgstr "" -#: ../settings/security/ssl-certificates.rst:31 -msgid "Add a Certificate" +#: ../misc/variables/article.rst:1 +msgid "``#{article.from}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:33 +#: ../misc/variables/article.rst:1 msgid "" -"To add a custom certificate or a custom CA certificate, head over to the " -"Admin panel > Settings > Security > SSL Certificates. Here you can find a " -"\"Add SSL Certificate\" button. In the dialog you can either select a " -"certificate file or paste the content of the certificate:" +"``Joe Doe `` may differ, depends on ``FROM`` of send mail" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate adding dialog" +#: ../misc/variables/article.rst:1 +msgid "Article > Sender > Name" msgstr "" -#: ../settings/security/ssl-certificates.rst:43 -msgid "" -"After selecting a file or pasting the content of the certificate, click on " -"the \"Add\" button to finally upload it to Zammad. Then, the certificates " -"are immediately effective, no restart or similar required." +#: ../misc/variables/article.rst:1 +msgid "``#{article.sender.name}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:49 -msgid "" -"Please note that only single certificate files are supported. That means if " -"you want to import a certificate / CA certificate, it must contain **only " -"one** certificate." +#: ../misc/variables/article.rst:1 +msgid "``Customer``, ``Agent`` or ``System``" msgstr "" -#: ../settings/security/ssl-certificates.rst:54 -msgid "Certificate Overview" +#: ../misc/variables/article.rst:1 +msgid "Article > Subject" msgstr "" -#: ../settings/security/ssl-certificates.rst:56 -msgid "" -"After you added a certificate, you can see a table with information for each " -"added certificate:" +#: ../misc/variables/article.rst:1 +msgid "``#{article.subject}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing table of added certificates" +#: ../misc/variables/article.rst:1 +msgid "``My amazing subject``" msgstr "" -#: ../settings/security/ssl-certificates.rst:64 -msgid "" -"Here you can download the certificate or delete it, if you don't need it " -"anymore." +#: ../misc/variables/article.rst:1 +msgid "Article > Text" msgstr "" -#: ../settings/security/ssl-certificates.rst:68 -#, fuzzy -msgid "Deleting Certificates" -msgstr "Limitação" +#: ../misc/variables/article.rst:1 +msgid "``#{article.body}``" +msgstr "" -#: ../settings/security/ssl-certificates.rst:70 -msgid "" -"If you want to delete a specific certificate, you can do it by clicking on " -"the menu in the actions column and selecting delete:" +#: ../misc/variables/article.rst:1 +msgid "``Test`` without formatting (plain)" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate deletion button" +#: ../misc/variables/article.rst:1 +msgid "Article > TicketID" msgstr "" -#: ../settings/security/ssl-certificates.rst:79 -msgid "Downloading Certificates" +#: ../misc/variables/article.rst:1 +msgid "``#{article.ticket_id}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:81 -msgid "" -"If you want to download your certificates, you can do this as well via " -"corresponding action buttons." +#: ../misc/variables/article.rst:1 +msgid "``1`` (not ticket number)" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate download button" +#: ../misc/variables/article.rst:1 +msgid "Article > To" msgstr "" -#: ../settings/security/third-party.rst:13 -msgid "Login Providers" +#: ../misc/variables/article.rst:1 +msgid "``#{article.to}``" msgstr "" -#: ../settings/security/third-party.rst:2 -msgid "Third-Party Applications" +#: ../misc/variables/article.rst:1 +msgid "``helpdesk@example.com``" msgstr "" -#: ../settings/security/third-party.rst:4 -msgid "" -"Third party authentication is a great way to help your users to login to " -"Zammad more easily. If the account is yet unknown, Zammad will create a new " -"user automatically, without the user needed to interact (e.g. type in his " -"name). Another big advantage of this feature is that your user doesn't need " -"to remember another password." +#: ../misc/variables/article.rst:1 +msgid "Article > Type > Name" msgstr "" -#: ../settings/security/third-party.rst:10 -msgid "" -"You can deactivate logging in via :ref:`security_password_login` if any of " -"the mentioned authentication providers are enabled in your instance." +#: ../misc/variables/article.rst:1 +msgid "``#{article.type.name}``" msgstr "" -#: ../settings/security/third-party.rst:27 +#: ../misc/variables/article.rst:1 msgid "" -"We're currently missing documentation for the following login providers:" +"``email`` (`list of article types `_)" msgstr "" -#: ../settings/security/third-party.rst:29 -msgid "LinkedIn" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Address" msgstr "" -#: ../settings/security/third-party.rst:30 -msgid "Weibo" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.address}``" msgstr "" -#: ../settings/security/third-party.rst:35 -msgid "Automatic Account Link on Initial Logon" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Department" msgstr "" -#: ../settings/security/third-party.rst:37 -msgid "" -"In general there's two possible options for Zammad on how to deal with " -"already known users as they try to authenticate against a third-party " -"application. By default, Zammad will not automatically link \"unknown\" " -"authentication providers to existing accounts." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.department}``" msgstr "" -#: ../settings/security/third-party.rst:42 -msgid "" -"This means that the user has to manually link authentication providers to " -"their accounts (for more about this :user-docs:`consult the user " -"documentation `)." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Email" msgstr "" -#: ../settings/security/third-party.rst:46 -msgid "" -"Sometimes this doesn't come in handy as this also means you'll receive error " -"messages about \"email address being in use already\" for (yet) unknown " -"third-party authentication methods." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.email}``" msgstr "" -#: ../settings/security/third-party.rst:50 -msgid "" -"If you want to allow your users to always be able to log in, no matter what, " -"you may want to enable ``Automatic account link on initial logon``." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Fax" msgstr "" -#: ../settings/security/third-party.rst:None -msgid "" -"Screenshot highlighting the \"Automatic account link on initial logon\"\n" -"setting" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.fax}``" msgstr "" -#: ../settings/security/third-party.rst:60 -msgid "Automatic Account Linking Notification" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Firstname" msgstr "" -#: ../settings/security/third-party.rst:64 -msgid "" -"To improve security and your users awareness, you can enable Zammad to " -"notify your users when a new third-party application has been linked to " -"their account." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.firstname}``" msgstr "" -#: ../settings/security/third-party.rst:68 -msgid "" -"This notification is sent out once per third-party application. Zammad does " -"also mention the method used, e.g.: ``Microsoft``." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Lastname" msgstr "" -#: ../settings/security/third-party.rst:71 -msgid "By default this setting is not active (set to ``no``)." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.lastname}``" msgstr "" -#: ../settings/security/third-party.rst:0 -msgid "" -"Screenshot showing sample notification mail after initial\n" -"third-party linking" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Login" msgstr "" -#: ../settings/security/third-party.rst:85 -msgid "" -"This notification is only sent if the account in question already exists. If " -"the login via the third-party also creates the missing account, the " -"notification will be skipped." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.login}``" msgstr "" -#: ../settings/security/third-party.rst:89 -msgid "This means it only affects:" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Mobile" msgstr "" -#: ../settings/security/third-party.rst:91 -msgid "manual account linking within the third-party page of the users profile" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.mobile}``" msgstr "" -#: ../settings/security/third-party.rst:92 -msgid "" -"logging into an existing local account by utilizing the *automatic account " -"link on initial logon* functionality" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Note" msgstr "" -#: ../settings/security/third-party.rst:None -msgid "" -"Screenshot showing the \"automatic account linking notification\"\n" -"setting" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.note}``" msgstr "" -#: ../settings/security/third-party.rst:100 -msgid "No User Creation on Logon" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Phone" msgstr "" -#: ../settings/security/third-party.rst:102 -msgid "" -"By default, Zammad will create a new user account if the user logs in via a " -"third-party application and the account doesn't exist yet." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.phone}``" msgstr "" -#: ../settings/security/third-party.rst:105 -msgid "" -"If you want to prevent Zammad from creating new accounts on logon, you can " -"disable this feature by setting ``No user creation on logon`` to ``yes``." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > VIP" msgstr "" -#: ../settings/security/third-party.rst:None -msgid "Screenshot showing the \"no user creation on logon\" setting" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.vip}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via Facebook To do " -"so, you need to follow these steps:" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Web" msgstr "" -#: ../settings/security/third-party/facebook.rst:9 -#, fuzzy -msgid "Register Facebook App" -msgstr "Registrar uma aplicação de robô do Telegram" - -#: ../settings/security/third-party/facebook.rst:11 -msgid "" -"Visit [https://developers.facebook.com/apps/] and click on \"Add a new App\"" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.web}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "initial page" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated" msgstr "" -#: ../settings/security/third-party/facebook.rst:17 -msgid "After that enter the app settings" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_at}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "Create App" +#: ../misc/variables/article.rst:1 +msgid "Article > Visibility" msgstr "" -#: ../settings/security/third-party/facebook.rst:22 -msgid "Navigate to \"Settings\" and fill in this infromation" +#: ../misc/variables/article.rst:1 +msgid "``#{article.internal}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "App Settings" +#: ../misc/variables/article.rst:1 +msgid "``false`` or ``true`` (false if not internal)" msgstr "" -#: ../settings/security/third-party/facebook.rst:27 -msgid "Navigate to app review and Check \"Make [appname] public?\"" +#: ../misc/variables/article.rst:1 +msgid "Article Text as HTML (not referenced)" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "App Review" +#: ../misc/variables/article.rst:1 +msgid "``#{article.body_as_html}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:35 -#, fuzzy -msgid "Configure Zammad as Facebook App" -msgstr "Configure o Zammad como um robô do Telegram" +#: ../misc/variables/article.rst:1 +msgid "``Test`` with formatting" +msgstr "" -#: ../settings/security/third-party/facebook.rst:37 -msgid "" -"Navigate to \"Admin -> Security -> Third Party Applications\" and enter the " -"App ID and the App Secret. You can find this Key in the Dashbard of your " -"Facebok app." +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "Ticket > Article#" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "Zammad Configuration" +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "``#{ticket.article_count}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:44 -#: ../settings/security/third-party/github.rst:43 -#: ../settings/security/third-party/gitlab.rst:46 -msgid "" -"Now you can link accounts via \"Avatar -> Profile -> Link Accounts\" or " -"login via Zammad login page." +#: ../misc/variables/article.rst:1 +msgid "``1`` number of ticket articles" msgstr "" -#: ../settings/security/third-party/github.rst:2 -#: ../system/integrations/github.rst:2 -msgid "GitHub" +#: ../misc/variables/config.rst:2 +msgid "Config" msgstr "" -#: ../settings/security/third-party/github.rst:4 +#: ../misc/variables/config.rst:6 msgid "" -"It is possible to create a quick login for your helpdesk via GitHub. To " -"activate the quick login you need to enable OAuth for GitHub." +"Below you'll find config related variables. These hold useful configuration " +"information that you can use within e.g. triggers to show necessary " +"information to your customer." msgstr "" -#: ../settings/security/third-party/github.rst:8 -msgid "Register GitHub App" +#: ../misc/variables/config.rst:11 +msgid "Config Variables" msgstr "" -#: ../settings/security/third-party/github.rst:10 -msgid "" -"Visit https://www.github.com/settings/applications/new and enter the app " -"settings. As callback URL enter \"https://zammad_host/auth/github/callback\" " -"where zammad_host has to be replaced with your Zammad FQDN" +#: ../misc/variables/config.rst:1 +msgid "Config > Fully Qualified Domain Name" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "Register OAuth app on www.github.com" +#: ../misc/variables/config.rst:1 +msgid "``#{config.fqdn}``" msgstr "" -#: ../settings/security/third-party/github.rst:19 -#, fuzzy -msgid "Configure Zammad as GitHub App" -msgstr "Configure o Zammad como um robô do Telegram" - -#: ../settings/security/third-party/github.rst:21 -msgid "" -"Enter the \"APP ID\" and the \"APP SECRET\" from the GitHub OAUTH " -"Applications Dashboard" +#: ../misc/variables/config.rst:1 +msgid "``zammad.example.com``" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub config in Zammad admin interface" +#: ../misc/variables/config.rst:1 +msgid "Config > HTTP type" msgstr "" -#: ../settings/security/third-party/github.rst:28 -msgid "" -"After you configured the GitHub credentials and activated the login method, " -"you should see a new icon on the login page." +#: ../misc/variables/config.rst:1 +msgid "``#{config.http_type}``" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub logo on login page" +#: ../misc/variables/config.rst:1 +msgid "``https`` or ``http``" msgstr "" -#: ../settings/security/third-party/github.rst:34 -msgid "" -"If you click on the icon you will be redirected to GitHub and see something " -"similar to this:" +#: ../misc/variables/config.rst:1 +msgid "Config > Organization" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub oauth page" +#: ../misc/variables/config.rst:1 +msgid "``#{config.organization}``" msgstr "" -#: ../settings/security/third-party/github.rst:40 -#: ../settings/security/third-party/gitlab.rst:42 +#: ../misc/variables/config.rst:1 msgid "" -"When you grant the access you will be redirected to your Zammad instance and " -"logged in as a customer." +"``Zammad GmbH`` value set in `Branding `_" msgstr "" -#: ../settings/security/third-party/gitlab.rst:2 -msgid "Gitlab" +#: ../misc/variables/config.rst:1 +msgid "Config > Product Name" msgstr "" -#: ../settings/security/third-party/gitlab.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via Gitlab. To " -"activate the quick login you need to enable OAuth for Gitlab." +#: ../misc/variables/config.rst:1 +msgid "``#{config.product_name}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:8 -#, fuzzy -msgid "Register Gitlab App" -msgstr "Registrar uma aplicação de robô do Telegram" +#: ../misc/variables/config.rst:1 +msgid "" +"``Helpdesk`` value set in `Branding `_" +msgstr "" -#: ../settings/security/third-party/gitlab.rst:10 -msgid "To register an app in Gitlab open your profile and select applications." +#: ../misc/variables/config.rst:1 +msgid "Config > SystemID" msgstr "" -#: ../settings/security/third-party/gitlab.rst:12 -msgid "" -"As callback URL enter \"https://zammad-fqdn/auth/gitlab/callback\" where " -"zammad-fqdn has to be replaced with your Zammad FQDN" +#: ../misc/variables/config.rst:1 +msgid "``#{config.system_id}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Register OAuth app on gitlab instance" +#: ../misc/variables/config.rst:1 +msgid "``31`` (value between 1 and 99)" msgstr "" -#: ../settings/security/third-party/gitlab.rst:18 -msgid "Just select *read_user* under scopes as in the screenshot and save it." +#: ../misc/variables/config.rst:1 +msgid "Config > Ticket Hook" msgstr "" -#: ../settings/security/third-party/gitlab.rst:21 -#, fuzzy -msgid "Configure Zammad as Gitlab App" -msgstr "Configure o Zammad como um robô do Telegram" +#: ../misc/variables/config.rst:1 +msgid "``#{config.ticket_hook}``" +msgstr "" -#: ../settings/security/third-party/gitlab.rst:23 -msgid "" -"Enter the \"APP ID\" and the \"APP SECRET\" from the Gitlab OAUTH " -"Applications Dashboard and your Gitlab-URL in the \"SITE\" field." +#: ../misc/variables/config.rst:1 +msgid "``Ticket#``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab config in Zammad admin interface" +#: ../misc/variables/current-user.rst:2 +msgid "Current User" msgstr "" -#: ../settings/security/third-party/gitlab.rst:30 +#: ../misc/variables/current-user.rst:6 msgid "" -"After you configured the Gitlab credentials and activated the login method, " -"you should see a new icon on the login page." +"Current user variables always return values of the current user that caused " +"e.g. a trigger to run." msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab logo on login page" +#: ../misc/variables/current-user.rst:8 +msgid "" +"Due to the above fact, these variables are often not (yet) set or available " +"for usage." msgstr "" -#: ../settings/security/third-party/gitlab.rst:36 +#: ../misc/variables/current-user.rst:10 msgid "" -"If you click on the icon you will be redirected to Gitlab and see something " -"similar to this:" +"In situations where e.g. schedulers or triggers run, this most likely is " +"nothing you want to use." msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab oauth page" +#: ../misc/variables/current-user.rst:13 +msgid "Current User Variables" msgstr "" -#: ../settings/security/third-party/google.rst:4 -msgid "" -"With some easy and fast steps, you can enable Zammad to authenticate your " -"users via Google." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Address" msgstr "" -#: ../settings/security/third-party/google.rst:8 -#, fuzzy -msgid "Register a Google App" -msgstr "Registrar uma aplicação de robô do Telegram" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.address}``" +msgstr "" -#: ../settings/security/third-party/google.rst:10 -msgid "" -"First of all, we need to create a new project - you can skip this step if " -"you already have one." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set" msgstr "" -#: ../settings/security/third-party/google.rst:15 -msgid "" -"Use this link to create a new project: https://console.cloud.google.com/" -"projectcreate" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Avatar" msgstr "" -#: ../settings/security/third-party/google.rst:18 -msgid "" -"Now expand the menu, expand \"APIs & Services\" and select \"Credentials\". " -"Go to the tab \"OAuth consent screen\" first and ensure to fill in the " -"requested information - without doing so you can't create credentials!" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/google.rst:None -msgid "Creating a consent screen" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "avatar picture with width and height in pixel (e.g. 60,60)" msgstr "" -#: ../settings/security/third-party/google.rst:25 -msgid "" -"After filling in and saving the consent screen information, you can go to " -"the \"Credentials\" tab and create new \"OAuth client ID\"-Credentials." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created at" msgstr "" -#: ../settings/security/third-party/google.rst:28 -msgid "" -"Fill in the necessary information as follows and replace ``zammad_host`` " -"with your FQDN:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_at}``" msgstr "" -#: ../settings/security/third-party/google.rst:31 -msgid "**Application type** ``[x] Web application``" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC``" msgstr "" -#: ../settings/security/third-party/google.rst:34 -msgid "**Authorized JavaScript origins** ``https://zammad_host/``" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Address" msgstr "" -#: ../settings/security/third-party/google.rst:37 -msgid "" -"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" -"callback``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.address}``" msgstr "" -#: ../settings/security/third-party/google.rst:None -msgid "Adding a new OAuth client ID" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Avatar" msgstr "" -#: ../settings/security/third-party/google.rst:43 -msgid "" -"After creating the credentials, go to your Zammad installation and navigate " -"to \"Admin > Security > Third Party Applications\" > Google. Enter your " -"Client ID and Client secret here." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/google.rst:None -msgid "Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Department" msgstr "" -#: ../settings/security/third-party/google.rst:50 -msgid "After submitting, the login via Google can be used." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.department}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:2 -msgid "Microsoft" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Sales`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:4 -msgid "" -"Zammad's Microsoft connection allows your users with Microsoft accounts to " -"login. This works for Azure users as well and can be an alternative to :doc:" -"`/system/integrations/ldap/index`." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Email" msgstr "" -#: ../settings/security/third-party/microsoft.rst:10 -msgid "" -"This documentation part does not cover our :doc:`📧 Microsoft 365 email " -"channel `." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.email}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screenshot showing Microsoft login button on Zammad login screen." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``jdoe@customer.tld``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:30 -#: ../settings/security/third-party/microsoft.rst:53 -msgid "Supported account types:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Fax" msgstr "" -#: ../settings/security/third-party/microsoft.rst:22 -msgid "" -"Please note that Zammad only supports these account types (App dependent):" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.fax}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:35 -msgid "Avatars of signing in users:" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``004930123464789`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:33 -msgid "" -"Zammad currently ignores user avatars. If the user is registered with e.g. " -"Gravatar, Zammad will fetch the avatar from there if enabled. See :doc:" -"`Zammad Image Service ` for more." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Firstname" msgstr "" -#: ../settings/security/third-party/microsoft.rst:38 -msgid "Step 1 - Register a Microsoft App for Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.firstname}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:40 -msgid "" -"Login to the `Microsoft Azure Portal `_ and " -"navigate to App registrations to create a new app. Provide the requested " -"information as follows and register your app." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``John`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:46 -msgid "Name:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Lastname" msgstr "" -#: ../settings/security/third-party/microsoft.rst:45 -msgid "" -"Any meaningful name fitting, this name will be displayed to users trying to " -"authenticate with this app." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.lastname}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:49 -msgid "Choose one of the above mentioned account types (see Limitations)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Login" msgstr "" -#: ../settings/security/third-party/microsoft.rst:51 -msgid "" -"The correct account type depends on your use case. If you want to use the " -"authentication internal only, choose the first option. If you're unsure, use " -"the \"Help me choose...\" link." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.login}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:58 -msgid "Redirect URI (optional):" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Mobile" msgstr "" -#: ../settings/security/third-party/microsoft.rst:56 -msgid "" -"Select web and provide your callback URL. The callback URL looks like this: " -"``https://zammad.domain.tld/auth/microsoft_office365/callback``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.mobile}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to register a Microsoft app" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``0049176123456789`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "Within **API permissions** add the following permissions:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Note" msgstr "" -#: ../settings/security/third-party/microsoft.rst:69 -msgid "``User.Read``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.note}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "Contacts" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Some note to this user`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "``Contacts.Read``" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Phone" msgstr "" -#: ../settings/security/third-party/microsoft.rst:73 -msgid "" -"You can find these permissions within *Microsoft Graph → Delegated " -"permissions*." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.phone}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to add required API permissions" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``004930123456789`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:80 -msgid "" -"Within **Certificates & secrets** create a new client secret. Note down the " -"returned secret **value** for later. **Do not** use the secret ID!" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > VIP" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to create a new app secret" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.vip}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:88 -msgid "" -"From **Overview** copy your apps *Application (client) ID*. If you're using " -"a single tenant app, please also copy *Directory (tenant) ID*. You now have " -"all required information for Zammad." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Web" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to retreive application client and tenant IDs" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.web}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:98 -msgid "Step 2 - Add App Credentials to Zammad" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``https://zammad.org`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:100 -msgid "" -"Navigate to Security > Third-party Applications (Tab) within Zammad's admin " -"settings. Scroll down to the section *Authentication via Microsoft* and fill " -"in the required information." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Department" msgstr "" -#: ../settings/security/third-party/microsoft.rst:105 -msgid "App ID:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.department}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:105 -msgid "This is your *Application (client) ID*." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Email" msgstr "" -#: ../settings/security/third-party/microsoft.rst:108 -msgid "App secret:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.email}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:108 -msgid "This is your *client secret* (value)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Fax" msgstr "" -#: ../settings/security/third-party/microsoft.rst:113 -msgid "App Tenant ID:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.fax}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:111 -msgid "" -"**optional** only required for apps that use account type *Accounts in this " -"organizational directory only (Default Directory only - Single tenant).*" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Firstname" msgstr "" -#: ../settings/security/third-party/microsoft.rst:115 -msgid "" -"Apply your settings by pressing submit and activate *Authentication via " -"Microsoft*." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.firstname}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "" -"Screencast showing how to add app credentials and activating the\n" -"authentication method" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Lastname" msgstr "" -#: ../settings/security/third-party/saml.rst:2 -msgid "SAML" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.lastname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:4 -msgid "" -"Connect your SAML (Security Assertion Markup Language) identity provider as " -"a single sign-on (SSO) method." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Login" msgstr "" -#: ../settings/security/third-party/saml.rst:7 -msgid "" -"SAML is an open standard for SSO authentication (among other things). Sign-" -"ins are shared across multiple **service providers** and managed by a " -"central **identity provider** (IdP)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.login}``" msgstr "" -#: ../settings/security/third-party/saml.rst:11 -msgid "" -"In this case, the service provider is Zammad, and the IdP is a software " -"service that you either host or subscribe to (*e.g.,* `Keycloak `_, `Redhat SSO Server `_, `ADFS `_, or `Okta `_)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Mobile" msgstr "" -#: ../settings/security/third-party/saml.rst:18 -msgid "" -"This guide assumes you are already using SAML within your organization (i." -"e., that your IdP is fully set up)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.mobile}``" msgstr "" -#: ../settings/security/third-party/saml.rst:21 -msgid "" -"Please note: Our instructions are based on connecting Zammad with Keycloak." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Note" msgstr "" -#: ../settings/security/third-party/saml.rst:25 -msgid "Step 1: Configure Your IdP" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.note}``" msgstr "" -#: ../settings/security/third-party/saml.rst:28 -msgid "Add Zammad as a Client/App" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Domain based assignment" msgstr "" -#: ../settings/security/third-party/saml.rst:30 -msgid "" -"Import Zammad into your IdP using the XML configuration found at ``https://" -"your.zammad.domain/auth/saml/metadata``." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.domain_assignment}``" msgstr "" -#: ../settings/security/third-party/saml.rst:33 -msgid "" -"If your IdP doesn't support XML import, you will have to configure Zammad as " -"a new client/app manually using the above XML metadata file for reference." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Domain" msgstr "" -#: ../settings/security/third-party/saml.rst:36 -msgid "For instance, when you see this tag:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.domain}``" msgstr "" -#: ../settings/security/third-party/saml.rst:42 -msgid "" -"Set the **Assertion Consumer Service Binding URL** (sometimes also listed as " -"**Valid Redirect URIs**) to ``http://your.zammad.domain/auth/saml/callback``." +#: ../misc/variables/current-user.rst:1 +msgid "``zammad.com`` or empty if not set" msgstr "" -#: ../settings/security/third-party/saml.rst:47 -msgid "Set Up User Attribute Mapping" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Name" msgstr "" -#: ../settings/security/third-party/saml.rst:49 -msgid "" -"Zammad requests the following user attributes (or “properties”) from the IdP:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.name}``" msgstr "" -#: ../settings/security/third-party/saml.rst:51 -msgid "Email address (``email``)" +#: ../misc/variables/current-user.rst:1 +msgid "``Zammad GmbH``" msgstr "" -#: ../settings/security/third-party/saml.rst:52 -msgid "Full name (``name``)" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Note" msgstr "" -#: ../settings/security/third-party/saml.rst:53 -msgid "Given name (``first_name``)" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.note}``" msgstr "" -#: ../settings/security/third-party/saml.rst:54 -msgid "Family name (``last_name``)" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``A note to the organization of the user`` or empty if not set" msgstr "" -#: ../settings/security/third-party/saml.rst:56 -msgid "" -"You may need to set up “mappers” (or “mappings”) to tell your IdP how user " -"attributes in SAML correspond to those in Zammad. For a more detailed " -"breakdown, refer to the XML metadata file referenced in the previous section." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Shared organization" msgstr "" -#: ../settings/security/third-party/saml.rst:62 -msgid "Per-IdP Instructions" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.shared}``" msgstr "" -#: ../settings/security/third-party/saml.rst:102 -msgid "Keycloak" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > VIP" msgstr "" -#: ../settings/security/third-party/saml.rst:65 -msgid "" -"**To add Zammad as a client,** save the XML configuration to disk (``https://" -"your.zammad.domain/auth/saml/metadata``) and use **Clients > Clients list > " -"Import client** in the Keycloak admin panel." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.vip}``" msgstr "" -#: ../settings/security/third-party/saml.rst:70 -msgid "" -"To help Zammad **match its own user accounts to Keycloak users**, create a " -"user attribute (or “property”) mapper. In **Clients list**, click on your " -"newly created Client ID, choose the tab **Client scopes** and click on the " -"link which refers to your Zammad instance. Choose **Add mapper > By " -"configuration > User Property** and create a mapper with the following " -"entries:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Phone" msgstr "" -#: ../settings/security/third-party/saml.rst:78 -msgid "**Name**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.phone}``" msgstr "" -#: ../settings/security/third-party/saml.rst:80 -msgid "**Mapper Type**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated at" msgstr "" -#: ../settings/security/third-party/saml.rst:81 -msgid "``User Property``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_at}``" msgstr "" -#: ../settings/security/third-party/saml.rst:82 -msgid "**Property**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Address" msgstr "" -#: ../settings/security/third-party/saml.rst:83 -msgid "``emailAddress``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.address}``" msgstr "" -#: ../settings/security/third-party/saml.rst:84 -msgid "**SAML Attribute Name**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Avatar" msgstr "" -#: ../settings/security/third-party/saml.rst:86 -msgid "**SAML Attribute NameFormat**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/saml.rst:87 -msgid "``basic``" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Department" msgstr "" -#: ../settings/security/third-party/saml.rst:89 -msgid "" -"In the example above, we're telling Zammad that whenever it receives a SAML " -"login request, it should take the ``email`` property from Keycloak, look for " -"a Zammad user with the same ``email`` attribute, and create a new session " -"for that user." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.department}``" msgstr "" -#: ../settings/security/third-party/saml.rst:95 -msgid "" -"If your Keycloak users' email addresses are stored on another property (*e." -"g.,* ``username``), adjust accordingly." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Email" msgstr "" -#: ../settings/security/third-party/saml.rst:98 -msgid "" -"Back in **Settings**, enter the Client ID (``https://your.zammad.domain/auth/" -"saml/metadata``) in the field **Master SAML Processing URL**." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.email}``" msgstr "" -#: ../settings/security/third-party/saml.rst:101 -msgid "You also need to enable **Sign assertions**." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Fax" msgstr "" -#: ../settings/security/third-party/saml.rst:105 -msgid "Step 2: Configure Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.fax}``" msgstr "" -#: ../settings/security/third-party/saml.rst:107 -msgid "" -"Enable SAML and enter your IdP's details in the Admin Panel under **Settings " -"> Security > Third Party Applications > Authentication via SAML**:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Firstname" msgstr "" -#: ../settings/security/third-party/saml.rst:None -#, fuzzy -msgid "Example configuration of SAML part 1" -msgstr "Configuração" - -#: ../settings/security/third-party/saml.rst:119 -msgid "Display name" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.firstname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:116 -msgid "" -"Allows you to define a custom button name for SAML. This helps your users to " -"understand better what the button on the login page does." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Lastname" msgstr "" -#: ../settings/security/third-party/saml.rst:119 -msgid "Defaults to ``SAML``." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.lastname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:123 -msgid "IDP SSO target URL" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Login" msgstr "" -#: ../settings/security/third-party/saml.rst:122 -msgid "" -"This is the target URL Zammad shall redirect to when the user presses the " -"SAML button. For Keycloak, this needs to look like https://your.domain/" -"realms/your-realm/protocol/saml" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.login}``" msgstr "" -#: ../settings/security/third-party/saml.rst:127 -msgid "IDP single logout target URL" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Mobile" msgstr "" -#: ../settings/security/third-party/saml.rst:126 -msgid "" -"This is the URL to which the single logout request and response should be " -"sent." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.mobile}``" msgstr "" -#: ../settings/security/third-party/saml.rst:131 -#, fuzzy -msgid "IDP certificate" -msgstr "Limitação" - -#: ../settings/security/third-party/saml.rst:130 -msgid "" -"The public certificate of your IDP for Zammad to verify during the callback " -"phase." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Note" msgstr "" -#: ../settings/security/third-party/saml.rst:145 -msgid "IDP certificate fingerprint" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.note}``" msgstr "" -#: ../settings/security/third-party/saml.rst:134 -msgid "" -"The fingerprint of your IDPs public certificate to verify during callback " -"phase." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Phone" msgstr "" -#: ../settings/security/third-party/saml.rst:137 -msgid "🔏 **For the IdP certificate / certificate fingerprint:**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.phone}``" msgstr "" -#: ../settings/security/third-party/saml.rst:139 -msgid "" -"Provide **only one or the other**—do not provide both! (Between the two, we " -"recommend the signing certificate itself: fingerprints use SHA-1, which `has " -"been broken for a while now `_.)" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > VIP" msgstr "" -#: ../settings/security/third-party/saml.rst:144 -msgid "" -"**Keycloak users:** Find your certificate in the Keycloak admin panel under " -"**Realm Settings > Keys > Algorithm: RS256 > Certificate**." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.vip}``" msgstr "" -#: ../settings/security/third-party/saml.rst:151 -msgid "Name identifier format" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``false`` or ``true``" msgstr "" -#: ../settings/security/third-party/saml.rst:148 -msgid "" -"This is the unique identifiers field type. Usually it should be ``urn:oasis:" -"names:tc:SAML:1.1:nameid-format:emailAddress``." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Web" msgstr "" -#: ../settings/security/third-party/saml.rst:151 -msgid "Zammad **expects an email address as unique identifier**!" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.web}``" msgstr "" -#: ../settings/security/third-party/saml.rst:155 -#, fuzzy -msgid "UID attribute name" -msgstr "Atributos do artigo" - -#: ../settings/security/third-party/saml.rst:154 -msgid "" -"Here you can define an attribute that uniquely identifies the user. If " -"unset, the name identifier returned by the IDP is used." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > VIP" msgstr "" -#: ../settings/security/third-party/saml.rst:None -#, fuzzy -msgid "Example configuration of SAML part 2" -msgstr "Configuração" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.vip}``" +msgstr "" -#: ../settings/security/third-party/saml.rst:163 -msgid "" -"Decide if the certificate for the connection to the IdP service has to be " -"verified or not (default: ``yes``)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Web" msgstr "" -#: ../settings/security/third-party/saml.rst:169 -msgid "Signing & Encrypting" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.web}``" msgstr "" -#: ../settings/security/third-party/saml.rst:169 +#: ../misc/variables/ticket.rst:6 msgid "" -"Define if you want to sign, encrypt, do both or nothing for the requests." +"Below you can find all available ticket-based variables within Zammad. These " +"can be called via triggers for example. If you're unsure if Zammad does " +"support variables at the point you're at, you can try to type ``::`` to " +"check." msgstr "" -#: ../settings/security/third-party/saml.rst:179 -msgid "Certificate (PEM)" +#: ../misc/variables/ticket.rst:12 +msgid "Ticket Variables" msgstr "" -#: ../settings/security/third-party/saml.rst:172 -msgid "" -"Paste the public certificate of your Zammad SAML client, if you want to " -"encrypt the requests." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Accounted Time" msgstr "" -#: ../settings/security/third-party/saml.rst:175 -#, fuzzy -msgid "Make sure the certificate is:" -msgstr "Limitação" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.time_unit}``" +msgstr "" -#: ../settings/security/third-party/saml.rst:177 -msgid "already valid and not yet expired" +#: ../misc/variables/ticket.rst:1 +msgid "``1``, ``2.75`` or empty response" msgstr "" -#: ../settings/security/third-party/saml.rst:178 -#, fuzzy -msgid "no CA certificate" -msgstr "Limitação" +#: ../misc/variables/ticket.rst:1 +msgid "``3``, any number of articles existing in the ticket right now" +msgstr "" -#: ../settings/security/third-party/saml.rst:179 -msgid "valid for signing and encrypting" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Closing time" msgstr "" -#: ../settings/security/third-party/saml.rst:185 -msgid "Private key (PEM)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.close_at}``" msgstr "" -#: ../settings/security/third-party/saml.rst:182 -msgid "" -"Paste the private key of your Zammad SAML client here, if you want to sign " -"the requests." +#: ../misc/variables/ticket.rst:1 +msgid "2019-10-07 17:25:00 UTC" msgstr "" -#: ../settings/security/third-party/saml.rst:185 -msgid "Make sure the key is an RSA key with a length of at least 2048 bits." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created at" msgstr "" -#: ../settings/security/third-party/saml.rst:188 -msgid "Private key secret" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_at}``" msgstr "" -#: ../settings/security/third-party/saml.rst:188 -msgid "If your private key is secured with a secret, you can provide it here." +#: ../misc/variables/ticket.rst:1 +msgid "2019-10-07 16:25:00 UTC" msgstr "" -#: ../settings/security/third-party/saml.rst:192 -msgid "Your callback URL" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Address" msgstr "" -#: ../settings/security/third-party/saml.rst:191 -msgid "" -"This URL is needed for your IdP configuration so it knows where to redirect " -"to after successful authentication." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.address}``" msgstr "" -#: ../settings/security/third-party/saml.rst:194 -msgid "" -"After saving your input by clicking on the \"Submit\" button, Zammad " -"verifies the provided keys/certificates (e.g. if they are valid for signing/" -"encrypting and if they aren't expired)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Avatar" msgstr "" -#: ../settings/security/third-party/saml.rst:199 -msgid "" -"See :ref:`automatic account linking ` for details " -"on how to link existing Zammad accounts to IdP accounts." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/saml.rst:205 -msgid "Automatic account linking doesn't work" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Department" msgstr "" -#: ../settings/security/third-party/saml.rst:206 -msgid "" -"Have you double-checked your IdP's user attribute mapping configuration?" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.department}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:4 -#, fuzzy -msgid "" -"It is possible to create a quick login for your helpdesk via Twitter. To do " -"so, you need to follow these steps:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Email" msgstr "" -"É possível inserir seu robô do Telegram no Zammad. Para fazer isso, você " -"precisa seguir estes passos." - -#: ../settings/security/third-party/twitter.rst:8 -#, fuzzy -msgid "Register Twitter App" -msgstr "Registrar uma aplicação de robô do Telegram" -#: ../settings/security/third-party/twitter.rst:10 -msgid "Go to https://dev.twitter.com/apps and login with your account." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.email}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:15 -msgid "Click on \"Create App\"" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Fax" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "new app page" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.fax}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:20 -msgid "" -"Enter app settings. As \"Callback URL\" you need to enter ``https://" -"zammad_host/api/v1/external_credentials/twitter/callback``. You need to " -"replace ``zammad_host`` with the domain of your Zammad system." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Firstname" msgstr "" -#: ../settings/security/third-party/twitter.rst:24 -msgid "" -"After the app has been created, update the application icon and organization " -"attributes." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.firstname}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "set permissions to receive and send direct messages" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Lastname" msgstr "" -#: ../settings/security/third-party/twitter.rst:30 -msgid "" -"Next we need to set ``read, write and access direct messages`` permissions " -"for the app." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.lastname}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "click on Keys & Access Token, note them" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Login" msgstr "" -#: ../settings/security/third-party/twitter.rst:36 -msgid "" -"Go to \"Keys and Access Token\" tab and note the \"Consumer Key\" and " -"\"Consumer Secret\"." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.login}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:40 -#, fuzzy -msgid "Configure Zammad as Twitter App" -msgstr "Configure o Zammad como um robô do Telegram" - -#: ../settings/security/third-party/twitter.rst:42 -msgid "" -"Go to \"Admin > Security > Twitter > Third Party Applications > Twitter\" " -"Section." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Mobile" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "Admin > Security > Third Party Applications" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.mobile}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:48 -msgid "" -"Fill in the \"Twitter Key\" and the \"Twitter Secret\" and click the " -"\"Submit\" button." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Note" msgstr "" -#: ../settings/security/third-party/twitter.rst:51 -msgid "" -"Now you can link accounts via \"Avatar > Profile > Link Accounts\" or login " -"via Zammad login page." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.note}``" msgstr "" -#: ../settings/security/two-factor.rst:11 -msgid "Two-factor Authentication Methods" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Phone" msgstr "" -#: ../settings/security/two-factor.rst:2 -msgid "Two-Factor Authentication" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.phone}``" msgstr "" -#: ../settings/security/two-factor.rst:4 -msgid "" -"Two-factor authentication (2FA) enhances the security of Zammad accounts by " -"adding an extra layer of verification beyond a password. It requires users " -"to provide two different types of authentication factors, typically " -"something they know (like a password) and something they possess (like a " -"mobile device or a security token), to ensure that only authorized " -"individuals can access the account." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > VIP" msgstr "" -#: ../settings/security/two-factor.rst:19 -msgid "Enable Recovery Codes" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.vip}``" msgstr "" -#: ../settings/security/two-factor.rst:21 -msgid "" -"Recovery codes are one-time use security codes that can be used by the user " -"if they lose access to their other two-factor authentication methods. They " -"cannot be used on their own, they can only be activated if at least one two-" -"factor authentication method is enabled." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Web" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Enable Recovery Codes Setting" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.web}``" msgstr "" -#: ../settings/security/two-factor.rst:30 -msgid "" -"Recovery codes can only be used as a backup method. If enabled, they will be " -"automatically generated for the user once they set up their initial two-" -"factor authentication method." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Address" msgstr "" -#: ../settings/security/two-factor.rst:34 -msgid "" -"The user will be asked to print out or save the generated recovery codes in " -"a safe place. Once used, a recovery code cannot be reused." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.address}``" msgstr "" -#: ../settings/security/two-factor.rst:37 -msgid "" -"Users will also have an option to regenerate their recovery codes at any " -"time, which invalidates already existing recovery codes and provides them " -"with a list of fresh codes." +#: ../misc/variables/ticket.rst:1 +#, fuzzy +msgid "Ticket > Customer > Avatar" +msgstr "Árvore de Seleção" + +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.avatar(60,60)}``" msgstr "" -#: ../settings/security/two-factor.rst:41 -msgid "" -"After you enable this setting, when the user completes a setup of their " -"initial two-factor authentication method, they will be presented with a list " -"of recovery codes and instructed to save them for later use." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Department" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Recovery Codes Generation Modal Dialog" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.department}``" msgstr "" -#: ../settings/security/two-factor.rst:50 -msgid "Enforce the Set Up of the Two-Factor Authentication" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Email" msgstr "" -#: ../settings/security/two-factor.rst:52 -msgid "" -"In case you wish to require your users to set up at least one two-factor " -"authentication method for their account, you can do this by selecting " -"specific user roles the requirement applies to in **Enforced for user " -"roles** setting. Of course you must have at least one two-factor " -"authentication method enabled for this setting to take effect." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.email}``" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Enforced for User Roles Setting" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Fax" msgstr "" -#: ../settings/security/two-factor.rst:62 -msgid "" -"After you change this setting, if the user has one of the selected roles on " -"their account, they will be forced to set up the two-factor authentication " -"upon next sign in or application reload." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.fax}``" msgstr "" -#: ../settings/security/two-factor.rst:66 -msgid "" -"A modal dialog with instructions will be shown, and they will not be able to " -"do any work before they set up at least one two-factor method." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Firstname" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Modal Dialog for Enforcing Two-Factor Authentication Set Up" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.firstname}``" msgstr "" -#: ../settings/security/two-factor.rst:74 -msgid "Reset Two-Factor Authentication for a Specific User" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Lastname" msgstr "" -#: ../settings/security/two-factor.rst:76 -msgid "" -"In case an user isn't able to login anymore because of an inaccessible " -"second factor, you can reset the user's 2FA method." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.lastname}``" msgstr "" -#: ../settings/security/two-factor.rst:79 -msgid "" -"To do this, go to the user management and search for the relevant user. " -"After you found the account, click the button in the action column and " -"select \"Manage Two-Factor Authentication\":" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Login" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Context menu in action column in user management" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.login}``" msgstr "" -#: ../settings/security/two-factor.rst:87 -msgid "" -"After selecting this, you can see a dialog where you can either reset one " -"2FA method or reset all of the user's 2FA methods:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Mobile" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Dialog for resetting user's 2FA method" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.mobile}``" msgstr "" -#: ../settings/security/two-factor.rst:94 -msgid "" -"Choose the fitting one, click on the corresponding \"Remove ...\" button and " -"confirm your action. The user now has to setup a new 2FA method, depending " -"on your 2FA configuration." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Note" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:2 -msgid "Authenticator App" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.note}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:4 -msgid "" -"The authenticator app method is a type of two-factor authentication that " -"uses a mobile application to generate one-time codes for account " -"verification. After setting up the authenticator app on their device, the " -"user links it to their Zammad account." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Phone" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:12 -msgid "" -"When logging in, the user is prompted to enter a time-sensitive code " -"generated by the app, in addition to their password. This code acts as the " -"second factor of authentication, providing an extra layer of security as it " -"changes periodically and is unique to the user's device." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.phone}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:None -msgid "Security Code in Google Authenticator App" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > VIP" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:22 -msgid "" -"The app generates codes based on a shared secret key stored securely on both " -"the user's device and the server, ensuring a synchronized and secure " -"authentication process. The method of generating the codes is sometimes also " -"called TOTP (time-based one-time password)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.vip}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:28 -msgid "Enabling the Authenticator App Method" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Web" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:30 -#: ../settings/security/two-factor/security-keys.rst:28 -msgid "To enable the method, just toggle the switch on in the settings." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.web}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:None -msgid "Authenticator App Switch in Settings" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Escalation at" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:36 -msgid "" -"Now the users will be able to set up this two-factor authentication method " -"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " -"Once they do, on next sign-in with password, they will be asked to provide " -"an additional security code generated by their mobile device." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.escalation_at}``" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:2 -msgid "Security Keys" +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:4 -msgid "" -"The security keys method is a type of a two-factor authentication that uses " -"Web Authentication API in the browser for verifying user's identity. The " -"user can register multiple hardware or software security keys with their " -"Zammad account and then they can use it during the sign-in process." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > First response" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:12 -msgid "" -"When logging in, the user is prompted to provide the same security key they " -"registered with their account, in addition to their password. This key acts " -"as the second factor of authentication, providing an extra layer of security." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.first_response_at}``" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:None -msgid "Security Key dialog in Safari on macOS" +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable yet" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:21 -msgid "" -"The type of the key can range from hardware USB sticks to passkeys stored in " -"a device of user's choice. Which type can be used depends on the browser " -"flavor and the platform of the user." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Assign Follow-Ups" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:26 -msgid "Enabling the Security Keys Method" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_assignment}``" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:None -msgid "Security Keys Switch in Settings" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Assignment Timeout" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:34 -msgid "" -"Now the users will be able to set up this two-factor authentication method " -"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " -"Once they do, on next sign-in with password, they will be asked to provide " -"the same security key they registered during the setup." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.assignment_timeout}``" msgstr "" -#: ../settings/system/system-selfhosted.include.rst:3 -msgid "" -"Below settings are only available to self hosted users. In hosted " -"environments we're handling these settings for you to ensure service " -"stability." +#: ../misc/variables/ticket.rst:1 +msgid "``20`` or empty if not configured" msgstr "" -#: ../settings/system/base.rst:11 -msgid "Fully Qualified Domain Name" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Follow-up possible" msgstr "" -#: ../settings/system/base.rst:7 -msgid "The URL of your Zammad installation." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_possible}``" msgstr "" -#: ../settings/system/base.rst:9 ../settings/system/base.rst:17 -msgid "This setting is used within :doc:`/system/variables` and notifications." +#: ../misc/variables/ticket.rst:1 +msgid "``no`` or ``yes``" msgstr "" -#: ../settings/system/system-base.include.rst:1 -msgid "It is automatically set by the *Getting Started wizard*." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Name" msgstr "" -#: ../settings/system/system-base.include.rst:5 -msgid "Changing this setting also changes callback URLs for your channels etc." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.name}``" msgstr "" -#: ../settings/system/system-base.include.rst:6 -msgid "This setting can have negative affects on being able to login." +#: ../misc/variables/ticket.rst:1 +msgid "``Sales``" msgstr "" -#: ../settings/system/base.rst:19 -msgid "HTTP type" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Note" msgstr "" -#: ../settings/system/base.rst:14 -msgid "" -"The HTTP type tells your installation how your clients connect. This is " -"relevant for authentication and cookie security." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.note}``" msgstr "" -#: ../settings/system/base.rst:31 -msgid "SystemID" +#: ../misc/variables/ticket.rst:1 +msgid "``Note about this group``" msgstr "" -#: ../settings/system/base.rst:22 -msgid "" -"This ID is being used within your ticket number. In case you're " -"communicating with another ticket system with similar ticket number schemes " -"this ID greatly reduces the risk of false follow ups." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > ID" msgstr "" -#: ../settings/system/base.rst:26 -msgid "" -"The SystemID is randomly selected upon installation of Zammad (``1-99``)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.id}``" msgstr "" -#: ../settings/system/base.rst:30 -msgid "" -"**Do not** change this setting in a productive system! Your Zammad " -"installation may no longer recognize old ticket number based follow ups upon " -"change!" +#: ../misc/variables/ticket.rst:1 +msgid "``17``, ``5281``, ..." msgstr "" -#: ../settings/system/frontend.rst:2 -msgid "Frontend" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact (agent)" msgstr "" -#: ../settings/system/frontend.rst:22 -#, fuzzy -msgid "Core Workflow Ajax Mode" -msgstr "Fluxos de Trabalho" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_agent_at}``" +msgstr "" -#: ../settings/system/frontend.rst:6 -msgid "" -"This setting allows administrators to enforce :doc:`/system/core-workflows` " -"to use Ajax-Calls instead of web sockets. You'll usually only need this if " -"you experience serious issues as noted below." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact (customer)" msgstr "" -#: ../settings/system/frontend.rst:10 -msgid "**🤓 Possible (technical) reasons**" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_customer_at}``" msgstr "" -#: ../settings/system/frontend.rst:12 +#: ../misc/variables/ticket.rst:1 msgid "" -"In some cases, your network structure (e.g. firewalls, proxies) may " -"disconnect long web socket connections. This leads to select fields staying " -"empty (e.g. owner selection *after* selecting your group) or fields not " -"shown / hidden (e.g. when switching to or from pending states, the \"pending " -"till\" field not showing / hiding)." +"``2019-10-07 16:25:00 UTC`` or empty if not applicable yet (Please note " +"`Ticket last contact behavior Settings `_ for this)" msgstr "" -#: ../settings/system/frontend.rst:18 -msgid "" -"Please keep in mind that the Ajax fallback may cause serious pressure on " -"your application server. If you have the choice stick to web sockets." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact" msgstr "" -#: ../settings/system/frontend.rst:22 -msgid "Default: ``no`` (inactive)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_at}``" msgstr "" -#: ../settings/system/frontend.rst:53 -msgid "Show calendar weeks in the picker of date/datetime fields" +#: ../misc/variables/ticket.rst:1 +#, fuzzy +msgid "Ticket > Number" +msgstr "Árvore de Seleção" + +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.number}``" msgstr "" -#: ../settings/system/frontend.rst:25 -msgid "" -"With this setting you can instruct Zammad to provide week number display " -"globally for all users. Calendar with week number display are usually used " -"in business sectors and may not be relevant for everyone." +#: ../misc/variables/ticket.rst:1 +msgid "``31001``, ``201910731001``, ..." msgstr "" -#: ../settings/system/frontend.rst:29 -msgid "" -"This setting affects *all areas* - you'll also see week numbers in the admin " -"panel for e.g. triggers and macros." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain based assignment" msgstr "" -#: ../settings/system/frontend.rst:32 -msgid "Default: ``no`` (not shown)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain_assignment}``" msgstr "" -#: ../settings/system/frontend.rst:53 -msgid "Here's the difference:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain" msgstr "" -#: ../settings/system/frontend.rst:0 -msgid "Screenshot showing Zammad's date picker (in the default way)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain}``" msgstr "" -#: ../settings/system/frontend.rst:41 -msgid "Set to ``no``" +#: ../misc/variables/ticket.rst:1 +msgid "``domain.tld`` or empty if not set" msgstr "" -#: ../settings/system/frontend.rst:0 -msgid "" -"Screenshot showing Zammad's date picker with\n" -"week numbers enabled" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Name" msgstr "" -#: ../settings/system/frontend.rst:50 -msgid "Set to ``yes``" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.name}``" msgstr "" -#: ../settings/system/index.rst:4 -msgid "" -"For your overview we split each tab within system settings into its own page:" +#: ../misc/variables/ticket.rst:1 +msgid "``Zammad GmbH`` or empty if not set" msgstr "" -#: ../settings/system/index.rst:16 -#, fuzzy -msgid "Console Based Settings" -msgstr "Configurações" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Note" +msgstr "" -#: ../settings/system/index.rst:18 -msgid "" -"There's some console based settings we didn't put into the UI. However, you " -"may find them helpful - you can find them in our :docs:`hidden settings ` section." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.note}``" msgstr "" -#: ../settings/system/network.rst:2 -msgid "Network" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Shared organization" msgstr "" -#: ../settings/system/network.rst:8 -msgid "" -"The proxy settings can only be saved after successfully testing the proxy " -"connection." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.shared}``" msgstr "" -#: ../settings/system/network.rst:15 -msgid "Proxy Address." +#: ../misc/variables/ticket.rst:1 +#, fuzzy +msgid "Ticket > Organization > VIP" +msgstr "Organização" + +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.vip}``" msgstr "" -#: ../settings/system/network.rst:12 -msgid "" -"Allows you to provide a proxy server if needed. This is relevant for network " -"communication by Zammad." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Address" msgstr "" -#: ../settings/system/network.rst:15 -msgid "It **does not** affect the update process or Elasticsearch." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.address}``" msgstr "" -#: ../settings/system/network.rst:18 -msgid "Username for proxy connection." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Avatar" msgstr "" -#: ../settings/system/network.rst:18 -msgid "" -"If your proxy server requires authentication, provide the username here." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.avatar(60,60)}``" msgstr "" -#: ../settings/system/network.rst:21 -msgid "Password for proxy connection." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Department" msgstr "" -#: ../settings/system/network.rst:21 -msgid "" -"If your proxy server requires authentication, provide the password here." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.department}``" msgstr "" -#: ../settings/system/network.rst:26 -msgid "No proxy for the following hosts." +#: ../misc/variables/ticket.rst:1 +msgid "``Support`` or empty if not set" msgstr "" -#: ../settings/system/network.rst:24 -msgid "" -"Exception list for hosts you can't or don't want to reach via proxy server." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Email" msgstr "" -#: ../settings/system/network.rst:27 -msgid "Default: ``localhost,127.0.0.0,::1``" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.email}``" msgstr "" -#: ../settings/system/services.rst:2 -msgid "Services" +#: ../misc/variables/ticket.rst:1 +msgid "``agent@company.tld`` or empty if not set" msgstr "" -#: ../settings/system/services.rst:10 -msgid "Image Service" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Fax" msgstr "" -#: ../settings/system/services.rst:5 -msgid "Defines the backend for user and organization image lookups." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.fax}``" msgstr "" -#: ../settings/system/services.rst:7 -msgid "Default: ``Zammad Image Service`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Firstname" msgstr "" -#: ../settings/system/services.rst:9 -msgid "" -"Make sure your on premise installation has ``HTTPS`` access to ``images." -"zammad.com``." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.firstname}``" msgstr "" -#: ../settings/system/services.rst:18 -msgid "Geo Calendar Service" +#: ../misc/variables/ticket.rst:1 +msgid "``Max`` or empty if not set" msgstr "" -#: ../settings/system/services.rst:13 -msgid "" -"Defines the backend for geo calendar lookups. Used for initial calendar " -"setup." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Lastname" msgstr "" -#: ../settings/system/services.rst:16 -msgid "Default: ``Zammad GeoCalendar Service`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.lastname}``" msgstr "" -#: ../settings/system/services.include.rst:2 -msgid "" -"Make sure your on premise installation has ``HTTPS`` access to ``geo.zammad." -"com``." +#: ../misc/variables/ticket.rst:1 +msgid "``Mustermann`` or empty if not set" msgstr "" -#: ../settings/system/services.rst:26 -msgid "Geo IP Service" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Login" msgstr "" -#: ../settings/system/services.rst:21 -msgid "" -"Defines the backend for geo IP lookups. Shows also location of an IP address " -"if an IP address is shown." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.login}``" msgstr "" -#: ../settings/system/services.rst:24 -msgid "Default: ``Zammad GeoIP Service`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "``agent``" msgstr "" -#: ../settings/system/services.rst:32 -msgid "Geo Location Service" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Mobile" msgstr "" -#: ../settings/system/services.rst:29 -msgid "" -"Defines the backend for geo location lookups to store geo locations for " -"addresses." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.mobile}``" msgstr "" -#: ../settings/system/services.rst:32 -msgid "" -"Default: ``OpenStreetMap (ODbL 1.0, http://osm.org/copyright)`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Note" msgstr "" -#: ../settings/system/services.rst:36 -msgid "" -"You can find a detailed privacy information on what we store for how long on " -"our :docs:`Privacy Appendix ` inside of our System " -"Documentation." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.note}``" msgstr "" -#: ../settings/system/storage.rst:2 -msgid "Storage" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Phone" msgstr "" -#: ../settings/system/storage.rst:6 -msgid "" -"Here you can define where Zammad stores attachments for tickets and the " -"knowledge base. By default, we're writing to the ``Database`` - you can " -"switch to ``Filesystem`` or ``Simple Storage (S3)`` at any time. In this " -"case please have a look on the following instructions." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.phone}``" msgstr "" -#: ../settings/system/storage.rst:11 -msgid "" -"If you have a busy Zammad instance, we strongly encourage you to use " -"filesystem storage instead of \"Database\". This will greatly improve system " -"performance (de-crease database load and size)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > VIP" msgstr "" -#: ../settings/system/storage.rst:19 -msgid "Database" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.vip}``" msgstr "" -#: ../settings/system/storage.rst:17 -msgid "" -"This is the default storage method. The attachments are stored directly in " -"the database. If your Zammad instance grows, we recommend one of the other " -"methods to maintain performance." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Web" msgstr "" -#: ../settings/system/storage.rst:38 -#, fuzzy -msgid "Filesystem" -msgstr "Sistema" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.web}``" +msgstr "" -#: ../settings/system/storage.rst:22 -msgid "" -"This storage method is recommended for all Zammad instances, especially for " -"those with a higher load. If you choose filesystem, your files are written " -"to ``/opt/zammad/storage/``." +#: ../misc/variables/ticket.rst:1 +msgid "``https://zammad.com`` or empty if not set" msgstr "" -#: ../settings/system/storage.rst:26 -msgid "" -"Moving attachments from \"Database\" to \"Filesystem\" can be run during " -"production use. However, you should consider your framework conditions (e.g. " -"bandwidth, system load in production) to define the right moment." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Pending till" msgstr "" -#: ../settings/system/storage.rst:32 -msgid "**You noticed slow updates of Zammad?**" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.pending_time}``" msgstr "" -#: ../settings/system/storage.rst:34 -msgid "" -"While Zammad is beeing updated, it enforces a recursive \"change " -"owner\" (chown) for this directory. For instances with many files this can " -"be time consuming. To mitigate that you can move your files and create a " -"symlink in ``/opt/zammad/storage/`` to the new directory. Of course you have " -"to make sure on your own that the permissions are always correct." +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not set" msgstr "" -#: ../settings/system/storage.rst:95 -msgid "Simple Storage (S3)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Priority > Name" msgstr "" -#: ../settings/system/storage.rst:41 -msgid "" -"To use the Simple Storage (S3), you have to provide some settings, which " -"can't be accessed in the UI (see instructions below)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.priority.name}``" msgstr "" -#: ../settings/system/storage.rst:44 -msgid "" -"⚠️ Please note that the current implementation is in its early stages and can " -"be modified in the future." +#: ../misc/variables/ticket.rst:1 +msgid "``2 normal``" msgstr "" -#: ../settings/system/storage.rst:47 -msgid "" -"The prerequisite is to have access to a S3-compatible storage and to have " -"all necessary parameters available (which depends on your storage provider; " -"if in doubt, please ask there for help)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > State > Name" msgstr "" -#: ../settings/system/storage.rst:51 -msgid "Steps to configure S3:" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.state.name}``" msgstr "" -#: ../settings/system/storage.rst:53 -msgid "" -"Copy ``config/zammad/storage.yml.dist`` to ``config/zammad/storage.yml``" +#: ../misc/variables/ticket.rst:1 +msgid "``new``, ``open``, ..." msgstr "" -#: ../settings/system/storage.rst:54 -msgid "Edit the copied file in one of the following ways:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Tags" msgstr "" -#: ../settings/system/storage.rst:56 -msgid "" -"Either provide your S3 configuration with one attribute per line like in the " -"upper area of the file" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.tags}``" msgstr "" -#: ../settings/system/storage.rst:58 +#: ../misc/variables/ticket.rst:1 msgid "" -"Or provide your S3 configuration as an URL (which you can find at the end of " -"the file). Note: you can also provide this URL as environment variable (:" -"docs:`see system documentation `) without using this yml-file." +"Currently not available, see `Issue 2769 `_" msgstr "" -#: ../settings/system/storage.rst:62 -msgid "" -"We recommend the deletion of the not used configuration style to avoid " -"inconsistencies." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Title" msgstr "" -#: ../settings/system/storage.rst:65 -msgid "Restart Zammad so the config file / environment variable is loaded" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.title}``" msgstr "" -#: ../settings/system/storage.rst:66 +#: ../misc/variables/ticket.rst:1 msgid "" -"Set the \"Storage Method\" in Zammad to ``Simple Storage (S3)`` in Settings " -"> System > Storage and click on \"Submit\". After that, Zammad checks your " -"configuration and the connection to the service and will raise an error " -"message if something is wrong." +"``My amazing Subject`` (normally subject, can be edited within Interface and " +"thus differ)" msgstr "" -#: ../settings/system/storage.rst:72 -msgid "A very simple storage configuration could look like this:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated at" msgstr "" -#: ../settings/system/storage.rst:85 -msgid "" -"Before setting the storage method to ``Simple Storage (S3)`` (step 4), " -"please make sure to have a working setup." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_at}``" msgstr "" -#: ../settings/system/storage.rst:88 -msgid "" -"You can verify this by running ``rails r 'Rails.logger = Logger.new(STDOUT); " -"pp Store::Provider::S3.ping?'`` in your Zammad directory. If everything is " -"fine, you should see ``true``, else you should see ``false`` and a simple " -"error message." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Address" msgstr "" -#: ../settings/system/storage.rst:93 -msgid "" -"If you installed Zammad through a package manager (rather than from source), " -"replace ``rails r`` with ``zammad run rails r`` above. To learn more, see :" -"docs:`Administration via Console `." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.address}``" msgstr "" -#: ../settings/ticket.rst:4 -msgid "" -"Here you can adjust general ticket settings. Additional ones for the ticket " -"composer interface can be found in the :doc:`/misc/composer`." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Avatar" msgstr "" -#: ../settings/ticket.rst:11 -msgid "Ticket Hook (default: ``Ticket#``)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.avatar(60,60)}``" msgstr "" -#: ../settings/ticket.rst:11 -msgid "The identifier for a ticket; *e.g.,* Ticket#, Call#, MyTicket#." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Department" msgstr "" -#: ../settings/ticket.rst:38 -msgid "Ticket Hook Position (default: ``right``)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.department}``" msgstr "" -#: ../settings/ticket.rst:14 -msgid "" -"With this setting you can decide (if) where to insert the ticket number." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Email" msgstr "" -#: ../settings/ticket.rst:20 -msgid "*Right*" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.email}``" msgstr "" -#: ../settings/ticket.rst:17 -msgid "" -"This setting will add the ticket reference on the right site of the subject." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Fax" msgstr "" -#: ../settings/ticket.rst:20 -msgid "Example: ``Some Subject [Ticket#12345]``" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.fax}``" msgstr "" -#: ../settings/ticket.rst:26 -msgid "*Left*" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Firstname" msgstr "" -#: ../settings/ticket.rst:23 -msgid "" -"This setting will add the ticket reference on the left site of the subject." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.firstname}``" msgstr "" -#: ../settings/ticket.rst:26 -msgid "Example: ``[Ticket#12345] Some Subject``" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Lastname" msgstr "" -#: ../settings/ticket.rst:29 -msgid "*None*" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.lastname}``" msgstr "" -#: ../settings/ticket.rst:29 -msgid "This will completely remove ticket references from the subject." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Login" msgstr "" -#: ../settings/ticket.rst:33 -msgid "" -"Please ensure to take a look at :doc:`/channels/email/settings` within the " -"email channel to ensure you have at least one reference that helps Zammad to " -"assign follow-ups correctly." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.login}``" msgstr "" -#: ../settings/ticket.rst:37 -msgid "" -"Disabling this and not setting up any further follow up search will lead to " -"unexpected results!" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Mobile" msgstr "" -#: ../settings/ticket.rst:65 -msgid "" -"Ticket Last Contact Behaviour (default: ``Use the start time of the last " -"customer thread (which may consist of multiple articles).``)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.mobile}``" msgstr "" -#: ../settings/ticket.rst:41 -msgid "" -"This setting changes the way Zammad updates the ``Last Contact`` value of a " -"ticket. This is fairly important for overviews and what you expect upon " -"ticket updates of a customer." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Note" msgstr "" -#: ../settings/ticket.rst:52 -msgid "" -"Use the start time of the last customer thread (which may consist of " -"multiple articles)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.note}``" msgstr "" -#: ../settings/ticket.rst:46 -msgid "" -"If this option is chosen, Zammad will update the last updated value just " -"once if a customer replies. After that, Zammad will wait for an agent to " -"react." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Phone" msgstr "" -#: ../settings/ticket.rst:50 -msgid "" -"This comes in handy if you want to work tickets in the order of their first " -"update. This will not change ticket orders if customers decide to \"bump\" " -"the ticket affected." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.phone}``" msgstr "" -#: ../settings/ticket.rst:57 -msgid "Use the time of the very last customer article." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > VIP" msgstr "" -#: ../settings/ticket.rst:55 -msgid "" -"When setting this option, Zammad will always update the last updated value. " -"This means that if ordering by ``Last Update``, ticket orders will change if " -"customers \"bump\" the ticket." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.vip}``" msgstr "" -#: ../settings/ticket.rst:64 -msgid "Last contact value used on :doc:`/manage/overviews`" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Web" msgstr "" -#: ../settings/ticket.rst:65 -msgid "Last contact value used on :doc:`/manage/trigger`" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.web}``" msgstr "" -#: ../settings/ticket.rst:88 -msgid "" -"Ticket Organization Reassignment (default: ``Update the most recent tickets." -"``)" +#: ../settings/branding.rst:10 +msgid "Product Name" msgstr "" -#: ../settings/ticket.rst:68 +#: ../settings/branding.rst:7 msgid "" -"This setting changes the way Zammad updates the organization field of the " -"tickets whenever the primary organization of a user is changed." +"Defines the name of the application, shown in the web interface, tabs and " +"title bar of the web browser." msgstr "" -#: ../settings/ticket.rst:74 -msgid "Update the most recent tickets." +#: ../settings/branding.rst:10 +msgid "Default value: ``Zammad Helpdesk``" msgstr "" -#: ../settings/ticket.rst:72 -msgid "" -"If this option is chosen, Zammad will update the 100 most recent tickets " -"where the user is the ticket customer. The ticket organization field will be " -"automatically set to the new primary organization of the user." +#: ../settings/branding.rst:13 +msgid "Will be shown in the app and is included in email footers." msgstr "" -#: ../settings/ticket.rst:88 -msgid "Do not update any tickets." +#: ../settings/branding.rst:19 +msgid "Logo" msgstr "" -#: ../settings/ticket.rst:77 -msgid "" -"When choosing this option, Zammad will not update any tickets when the " -"user's primary organization is changed." +#: ../settings/branding.rst:16 +msgid "Defines the logo of the application, shown in the login page of Zammad." msgstr "" -#: ../settings/ticket.rst:80 -msgid "**Use with care!**" +#: ../settings/branding.rst:18 +msgid "" +"Ensure to hit the \"Submit\" button after uploading the logo. Otherwise your " +"change will not be saved." msgstr "" -#: ../settings/ticket.rst:82 +#: ../settings/branding.rst:22 msgid "" -"Using this option may lead to inconsistencies in the system as the ticket " -"organization may become decoupled from the ticket customer." +"Allows to set the default language of the Zammad instance. The here defined " +"locale mostly acts as a fallback for:" msgstr "" -#: ../settings/ticket.rst:85 -msgid "" -"However, you may use this option if you wish to maintain :ref:`the shared " -"access ` to the ticket for all organization " -"members of the original organization of the customer." +#: ../settings/branding.rst:25 +msgid "user preferences (if Zammad can't detect the users locale)" msgstr "" -#: ../settings/ticket.rst:110 -msgid "Ticket Number Format (default: ``Increment (SystemID.Counter)``)" +#: ../settings/branding.rst:26 +msgid "CSV output (reporting, time accounting)" msgstr "" -#: ../settings/ticket.rst:94 +#: ../settings/branding.rst:30 +msgid "Define the timezone of your Zammad installation." +msgstr "" + +#: ../settings/branding.rst:32 msgid "" -"This setting defines the way Zammad's ticket number will look. Changing this " -"setting in production will cause follow up detection to fail." +"This does not have any effect on timings for your agents or how Zammad " +"stores date and time values." msgstr "" -#: ../settings/ticket.rst:102 -msgid "Increment (SystemID.Counter)" +#: ../settings/branding.rst:35 +msgid "Changing this value has direct consequences on the following areas:" msgstr "" -#: ../settings/ticket.rst:98 -msgid "" -"The increment value contains the SystemID (automatically generated during " -"installation) and a increment which counts up with every new Ticket. The " -"increment will automatically get another digit if needed." +#: ../settings/branding.rst:37 +msgid ":doc:`/manage/scheduler` tasks" msgstr "" -#: ../settings/ticket.rst:102 -msgid "Examples: ``1010138``, ``1010139``" +#: ../settings/branding.rst:38 +msgid "search indexing (and thus reporting)" msgstr "" -#: ../settings/ticket.rst:110 -msgid "Date (Year.Month.Day.SystemID.Counter)" +#: ../settings/branding.rst:40 +#, fuzzy +msgid "calendar subscriptions" +msgstr "Descrição" + +#: ../settings/branding.rst:41 +msgid "browser printing" msgstr "" -#: ../settings/ticket.rst:105 +#: ../settings/branding.rst:43 msgid "" -"This version of the ticket number is fairly long. However, because it " -"contains the date of ticket creation, it also allows you to see when the " -"ticket has been created. You may feel familiar with this number format if " -"you've worked with OTRS already." +"Please note that some of above are fallbacks in case Zammad could not detect " +"the agents timezone correctly." msgstr "" -#: ../settings/ticket.rst:110 -msgid "Examples: ``201206231010138``, ``201206231010139``" +#: ../settings/branding.rst:77 +msgid "Pretty Date" msgstr "" -#: ../settings/ticket.rst:137 -msgid "OPTIONS" +#: ../settings/branding.rst:47 +msgid "" +"This setting allows you to define how Zammad should display time stamps " +"within the interface to all users." msgstr "" -#: ../settings/ticket.rst:113 +#: ../settings/branding.rst:50 msgid "" -"The below options allow you to further customize your ticket number. The " -"availability of options differ depending of the chosen ticket number format " -"above." +"This does not have any effect on how Zammad returns e.g. time values via " +"variables." msgstr "" -#: ../settings/ticket.rst:122 -msgid "Checksum (default: ``no``)" +#: ../settings/branding.rst:77 +#, fuzzy +msgid "Choose in between the following options:" +msgstr "Lá você poderá editar as seguintes configurações:" + +#: ../settings/branding.rst:64 +msgid "relative" msgstr "" -#: ../settings/ticket.rst:118 +#: ../settings/branding.rst:55 msgid "" -"If set to yes, we'll built a checksum to further \"unique\" the ticket " -"number of your system. If you're dealing with many other ticket systems this " -"might help to prevent false positive follow up detection on tickets." +"This timestamp shows a relative time span until it switches to a date. Over " +"time, it will change as follows:" msgstr "" -#: ../settings/ticket.rst:122 -msgid "This will also add another digit to the ticket number." +#: ../settings/branding.rst:58 +msgid "just now" msgstr "" -#: ../settings/ticket.rst:137 -msgid "Min. size of Number (default: ``5``)" +#: ../settings/branding.rst:59 +msgid "5 minutes ago" msgstr "" -#: ../settings/ticket.rst:125 -msgid "" -"This setting defines the minimum length of your ticket number. If your " -"counter is not yet high enough, Zammad will fill the number with zeros to " -"ensure the wanted length." +#: ../settings/branding.rst:60 +msgid "3 days 1 hour ago" msgstr "" -#: ../settings/ticket.rst:129 -msgid "" -"Please note that the minimum length is ``3`` (SystemID + at least one digit " -"if below 10). Also, if the length is no longer long enough, the number will " -"automatically get one digit longer. Ticket-Numbers **do not overflow**, thus " -"it's save to keep it at 5 or set it lower if wanted." +#: ../settings/branding.rst:61 +msgid "``03/04/2022``" msgstr "" -#: ../settings/ticket.rst:135 -msgid "" -"This option is only available if ticket number format is set to " -"``Increment``!" +#: ../settings/branding.rst:63 +msgid "Hovering the timestamp helps, you'll always get a clean timestamp then." msgstr "" -#: ../settings/ticket.rst:142 -msgid "Auto-Assignment" +#: ../settings/branding.rst:71 +msgid "absolute" msgstr "" -#: ../settings/ticket.rst:144 +#: ../settings/branding.rst:67 msgid "" -"In a larger Zammad environment, it happens that several agents open the same " -"ticket at the same time. Although collision detection is then effective, the " -"efficiency of processing can be increased by means of the automatic " -"assignment of tickets when a ticket is opened." +"This timestamp always includes the week day. For one week after creation, " +"the timestamp will not contain the date itself: Thursday 18:35." msgstr "" -#: ../settings/ticket.rst:149 -msgid "" -"The automatic assignment of tickets can be activated and configured in the " -"admin area under Settings > Ticket > Auto Assignment." +#: ../settings/branding.rst:71 +msgid "After a week it will switch to: ``Friday 4. Mar 16:00``." msgstr "" -#: ../settings/ticket.rst:152 -msgid "" -"The auto assignment only works if the ticket has no owner yet. By default, " -"the agent can always reset the ticket owner to ``-`` if needed." +#: ../settings/branding.rst:76 +msgid "timestamp" msgstr "" -#: ../settings/ticket.rst:155 +#: ../settings/branding.rst:74 msgid "" -"If you want to use this function for only specific tickets, you can " -"configure the conditions accordingly to meet your requirement. By default " -"the condition affects all tickets with the state ``open``." +"This will cause Zammad to show a complete timestamp according to your locale " +"defaults. For English this could be e.g. ``2022/12/03 2:40 pm`` or for " +"German e.g. ``12.03.2022 14:40``." msgstr "" -#: ../settings/ticket.rst:161 -msgid "" -"If you need to exclude users (e.g. a group leader), you can search and " -"select the desired agents in the ``Exception Users`` list. The search " -"function in this area is only effective, if you have too many agents to " -"display at once to help you with the configuration." +#: ../settings/branding.rst:78 +msgid "Default setting: ``relative``." msgstr "" -#: ../settings/ticket.rst:167 -#, fuzzy -msgid "Notifications" -msgstr "Limitação" - -#: ../settings/ticket.rst:191 -#, fuzzy -msgid "Default Notifications" -msgstr "Limitação" - -#: ../settings/ticket.rst:170 -msgid "" -"This setting allows you to configure the default ticket notifications that " -"will be applied to all new agent users (incl. users who were just assigned " -"agent role). Simply change the notification matrix to desired state and " -"press **Save**." +#: ../settings/security.rst:2 +msgid "Security" msgstr "" -#: ../settings/ticket.rst:175 +#: ../settings/security.rst:4 msgid "" -"In case an agent already exists, their ticket notification preferences will " -"be preserved. Optionally, you can also **Apply current defaults to all " -"agents**." +"For your overview we split each tab within security settings into its own " +"page:" msgstr "" -#: ../settings/ticket.rst:181 -msgid "" -"**Potential time-consuming action:** Applying default ticket notifications " -"to all agent users may take some time to complete, be patient! The exact " -"time will depend on the size of your system and the number of agents." +#: ../settings/security/base.rst:2 ../settings/system/base.rst:2 +#: ../settings/ticket.rst:8 +msgid "Base" msgstr "" -#: ../settings/ticket.rst:185 -msgid "" -"**Active agents only!** When current default ticket notifications are " -"applied, only active agent users are considered. In case an agent is re-" -"activated *after* this action, they will still have the old notification " -"configuration." +#: ../settings/security/base.rst:5 +msgid "New User Accounts" msgstr "" -#: ../settings/ticket.rst:190 +#: ../settings/security/base.rst:9 msgid "" -"In case you want to go back to the initial state of ticket notifications, " -"you can click on **Reset to default** button." +"Activates the `register as a new customer` function on the login page. If " +"set to ``no`` only administrators or agents can create new accounts manually." msgstr "" -#: ../settings/ticket.rst:194 ../settings/ticket.rst:196 -msgid "Duplicate Detection" +#: ../settings/security/base.rst:13 ../settings/security/base.rst:38 +#: ../settings/security/base.rst:66 +msgid "Default setting: ``yes``" msgstr "" -#: ../settings/ticket.rst:236 ../settings/ticket.rst:238 -#, fuzzy -msgid "Detect Duplicate Ticket Creation" -msgstr "na criação do Chamado" +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"New User Accounts\" setting" +msgstr "" -#: ../settings/ticket.rst:197 ../settings/ticket.rst:199 +#: ../settings/security/base.rst:22 msgid "" -"This setting turns on the duplicate ticket detection mechanism during ticket " -"creation. If similar tickets are found in the system, a suitable warning " -"will be shown to the user trying to create a ticket." +"Deactivation of above function **does not** deactivate automatic account " +"creation! This means: If a user writes e.g. an email to Zammad and has no " +"account yet, Zammad will automatically create the account. User accounts are " +"a direct dependency of tickets and thus technically mandatory." msgstr "" -#: ../settings/ticket.rst:204 ../settings/ticket.rst:206 -msgid "A Sample Duplicate Ticket Warning" +#: ../settings/security/base.rst:29 +msgid "Lost Password" msgstr "" -#: ../settings/ticket.rst:206 ../settings/ticket.rst:208 +#: ../settings/security/base.rst:33 msgid "" -"You can choose which ticket attributes will be matched by selecting them in " -"**Attributes to compare** field. Only if the ticket attribute value provided " -"by the user in the ticket create form is *equal* with the attribute in an " -"existing ticket, the warning will be shown." +"Activates the `lost password` function on the login page. If set to ``no`` " +"only administrators may change the user's password - users may update their " +"own password if they're still logged in and they have the required :doc:" +"`permission `." msgstr "" -#: ../settings/ticket.rst:211 ../settings/ticket.rst:213 -msgid "**Warning title** and **Warning message** are configurable as well." +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"Lost Password\" setting" msgstr "" -#: ../settings/ticket.rst:213 ../settings/ticket.rst:215 +#: ../settings/security/base.rst:49 msgid "" -"You can limit the detection only to certain user roles. By default, only " -"agents will see the warning." +"With third party authentications - but especially LDAP - you may want to " +"disable this function. Zammad **will not** change third party login " +"passwords and instead set or change the local password!" msgstr "" -#: ../settings/ticket.rst:216 ../settings/ticket.rst:218 +#: ../settings/security/base.rst:56 +#, fuzzy +msgid "Password Login" +msgstr "Senha" + +#: ../settings/security/base.rst:60 msgid "" -"If you don't want to show the matched tickets as part of the warning, you " -"can set **Show matching ticket(s) in the warning** setting to *no*." +"Activates the username & password login by default and if no third-party " +"login is activated. Disabling password login on the Zammad login page only " +"takes effect if you enable any :doc:`third-party`." msgstr "" -#: ../settings/ticket.rst:219 ../settings/ticket.rst:221 -msgid "" -"By default, **Permission level for looking up ticket** is set to *User*, " -"which means user permissions will be honored during sarch. The user will " -"see the warning only if tickets they have access to are matched. " -"Alternatively, you can set this setting to *System*, in which case the " -"search will happen within *all* tickets in the system, regardless of user " -"permissions." +#: ../settings/security/base.rst:64 +msgid "See :doc:`third-party` for supported third-party logins." msgstr "" -#: ../settings/ticket.rst:225 ../settings/ticket.rst:227 -msgid "**🦺 Safety first!**" +#: ../settings/security/base.rst:0 +msgid "Figure showing de-activated \"Password Login\" setting" msgstr "" -#: ../settings/ticket.rst:227 ../settings/ticket.rst:229 +#: ../settings/security/base.rst:77 msgid "" -"Even if the permission level is set to *System*, the user will not be shown " -"the tickets they don't have access to in the warning, even if they match." +"To help administrators to overcome \"login issues\", Zammad automatically " +"offers a password request for administrator users. This allows you to adjust " +"Third-Party applications even if the login does no longer work!" msgstr "" -#: ../settings/ticket.rst:231 ../settings/ticket.rst:233 -msgid "" -"However, just the confirmation about the existence of the tickets in the " -"system may be considered an unwanted information disclosure. Use this option " -"carefully!" +#: ../settings/security/base.rst:84 +msgid "Session Timeout" msgstr "" -#: ../settings/ticket.rst:235 ../settings/ticket.rst:237 +#: ../settings/security/base.rst:86 msgid "" -"Finally, you can configure between matching within **All tickets** or **Open " -"tickets** only by setting **Match tickets in following states**. Depending " -"on the current ticket state, a ticket may or not be matched." +"All settings below by default are set to ``4 weeks``. Session Timeout " +"defines the life time of a users session. As soon as it's reached, Zammad " +"will automatically log off the session in question." msgstr "" -#: ../system/core-workflows.rst:2 -msgid "Core Workflows" -msgstr "Fluxos de Trabalho" - -#: ../system/core-workflows.rst:4 +#: ../settings/security/base.rst:91 msgid "" -"Core Workflows allow you to adjust object attributes in many ways. For " -"example:" +"Zammad takes the highest value set assigned for the user based on the " +"permissions." msgstr "" -#: ../system/core-workflows.rst:7 -msgid "show / hide fields" +#: ../settings/security/base.rst:94 +msgid "``admin``" msgstr "" -#: ../system/core-workflows.rst:8 -msgid "adjust mandatory setting" +#: ../settings/security/base.rst:96 +msgid "``ticket.customer``" msgstr "" -#: ../system/core-workflows.rst:9 -msgid "manipulate available options" +#: ../settings/security/base.rst:97 +msgid "``default`` (fallback if user doesn't have above permissions set)" msgstr "" -#: ../system/core-workflows.rst:11 +#: ../settings/security/base.rst:99 msgid "" -"With this, you can provide exactly the information your users really need!" +"All settings act independently from each other allowing you to disable the " +"timeouts for e.g. admins, but not agents." msgstr "" -#: ../system/core-workflows.rst:15 -msgid "" -"If the pre-defined :doc:`/system/objects` are not enough, please add them " -"beforehand." +#: ../settings/security/base.rst:115 +#: ../system/integrations/checkmk/api-reference.rst:13 +msgid "Example" msgstr "" -#: ../system/core-workflows.rst:17 -msgid "" -"If you experience slow or unreliable field updates, please see :ref:`Core " -"Workflow Ajax Modus `" +#: ../settings/security/base.rst:107 +msgid "Let's suppose you configured the following session timeouts" msgstr "" -#: ../system/core-workflows.rst:22 -msgid "" -"This is a very enhanced functionality and can cause unexpected UI behavior. " -"Please ensure to test your use cases after configuration to reduce surprises." +#: ../settings/security/base.rst:104 +msgid "default: 3 weeks" msgstr "" -#: ../system/core-workflows.rst:None -msgid "Dialogue for adding a new workflow" +#: ../settings/security/base.rst:105 +msgid "admin: 2 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:2 -#, fuzzy -msgid "Core Workflow Condition Operators" -msgstr "Fluxos de Trabalho" - -#: ../system/core-workflows/condition-operators.rst:4 -msgid "" -"You might know that there is a separate section for explaining :doc:" -"`condition operators `. Head over there to " -"see a detailed explanation of many conditions and operators." +#: ../settings/security/base.rst:106 +msgid "ticket.agent: 4 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:8 -msgid "" -"Due to differences to other places in Zammad which are also using conditions " -"(e.g. triggers), you can find a dedicated description of operators for core " -"workflows below." +#: ../settings/security/base.rst:107 +msgid "ticket.customer: 1 week" msgstr "" -#: ../system/core-workflows/condition-operators.rst:12 -msgid "" -"Be aware that the availability of the operators depends on the selected " -"attribute and its field type. Some of the operators may only be available " -"for system attributes (e.g. for \"tags\", \"active\")." +#: ../settings/security/base.rst:115 +msgid "This results in the following situations" msgstr "" -#: ../system/core-workflows/condition-operators.rst:20 -msgid "Operator" +#: ../settings/security/base.rst:110 +msgid "a user with ``admin`` permission will have a timeout of 2 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:22 -msgid "after (absolute)" +#: ../settings/security/base.rst:111 +msgid "" +"a user with ``admin`` and ``ticket.agent`` permissions will have a timeout " +"of 2 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:23 -msgid "Matches if a date/time is after a specific point in time." +#: ../settings/security/base.rst:113 +msgid "" +"a user with ``ticket.customer`` permission will have a timeout of 1 week" msgstr "" -#: ../system/core-workflows/condition-operators.rst:24 -msgid "after (relative)" +#: ../settings/security/base.rst:115 +msgid "" +"a user with neither ``admin``, ``ticket.agent`` nor ``ticket.customer`` " +"permissions will have a timeout of 3 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:25 -msgid "Matches if a time span after a specified event has passed." +#: ../settings/security/password.rst:4 +msgid "" +"This section allows you to define password requirements for the local user " +"accounts." msgstr "" -#: ../system/core-workflows/condition-operators.rst:26 -msgid "before (absolute)" +#: ../settings/security/password.rst:9 +msgid "" +"Zammad does **not** allow you to change your LDAP password, instead, it will " +"set a password in its local database which might confuse your users. This " +"might be addressed in the future by `#1169 `_." msgstr "" -#: ../system/core-workflows/condition-operators.rst:27 -msgid "Matches if a date/time is before a specific point in time." +#: ../settings/security/password.rst:14 +msgid "**Exception for admins**" msgstr "" -#: ../system/core-workflows/condition-operators.rst:28 -msgid "before (relative)" +#: ../settings/security/password.rst:16 +msgid "" +"Please note that below password policies *do not* affect administrators " +"setting passwords on user accounts. While this seems strange and not safe we " +"believe that an administrator knowing an user's password is insecure as well." msgstr "" -#: ../system/core-workflows/condition-operators.rst:29 -msgid "Matches if a time span after a specified event has not passed." +#: ../settings/security/password.rst:21 +msgid "The suggested workflow is either:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:30 -msgid "contains" +#: ../settings/security/password.rst:23 +msgid "" +"to use third party logins to not require local passwords at all **- or -**" msgstr "" -#: ../system/core-workflows/condition-operators.rst:31 -msgid "Matches if a specified value is present." +#: ../settings/security/password.rst:25 +msgid "to require your *user to reset the password* upon first login." msgstr "" -#: ../system/core-workflows/condition-operators.rst:33 -msgid "Matches if all of the specified values are present." +#: ../settings/security/password.rst:27 +msgid "" +"This way administrators are not required to set a user's password at all!" msgstr "" -#: ../system/core-workflows/condition-operators.rst:35 -msgid "Matches if none of the specified values are present." +#: ../settings/security/password.rst:31 +msgid "Maximum Failed Logins" msgstr "" -#: ../system/core-workflows/condition-operators.rst:36 -msgid "contains not" +#: ../settings/security/password.rst:33 +msgid "" +"You can choose a value between ``4`` and ``20``. This defines how often a " +"login to a user account may fail until Zammad will lock it. Your users can " +"always use the \"forgot password\" function to change their password and " +"unlock their account." msgstr "" -#: ../system/core-workflows/condition-operators.rst:37 -msgid "Matches if a specified value is not present." +#: ../settings/security/password.rst:38 +msgid "The default value is ``10``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:39 -msgid "Matches if one specified value is present." +#: ../settings/security/password.rst:42 +msgid "Beside changing the user's password, you can also unlock accounts via" msgstr "" -#: ../system/core-workflows/condition-operators.rst:41 -msgid "Matches if one specified value is not present." +#: ../settings/security/password.rst:44 +msgid ":ref:`user management list `" msgstr "" -#: ../system/core-workflows/condition-operators.rst:42 -msgid "does not match regex" +#: ../settings/security/password.rst:45 +msgid ":docs:`console `" msgstr "" -#: ../system/core-workflows/condition-operators.rst:43 -msgid "Matches if content doesn't fit to regex rule." +#: ../settings/security/password.rst:46 +msgid ":docs:`API `" msgstr "" -#: ../system/core-workflows/condition-operators.rst:44 -msgid "ends with" +#: ../settings/security/password.rst:50 +msgid "Failed logins via LDAP no longer lock accounts." msgstr "" -#: ../system/core-workflows/condition-operators.rst:45 -msgid "Matches if content ends with specified value." +#: ../settings/security/password.rst:53 +msgid "2 Lower Case And 2 Upper Case Characters" msgstr "" -#: ../system/core-workflows/condition-operators.rst:46 -msgid "ends with one of" +#: ../settings/security/password.rst:55 +msgid "" +"You can add complexity to passwords by enforcing at least 2 upper and lower " +"case characters." msgstr "" -#: ../system/core-workflows/condition-operators.rst:47 -msgid "Matches if content ends with one of the specified values." +#: ../settings/security/password.rst:58 ../settings/security/password.rst:83 +msgid "The default value is ``no``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:48 -msgid "from (relative)" +#: ../settings/security/password.rst:62 +msgid "Minimum Length" msgstr "" -#: ../system/core-workflows/condition-operators.rst:49 -msgid "Matches if date/time is after a period of time after an event." -msgstr "" - -#: ../system/core-workflows/condition-operators.rst:51 -msgid "Matches if content is equal to a specified value." +#: ../settings/security/password.rst:64 +msgid "" +"This defines the minimum password length required for users to provide (from " +"``4`` to ``20``)." msgstr "" -#: ../system/core-workflows/condition-operators.rst:52 -msgid "is any of" +#: ../settings/security/password.rst:67 +msgid "The default value is ``6``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:53 -msgid "Matches if content is equal to any of specified values." +#: ../settings/security/password.rst:71 +msgid "Digit Required" msgstr "" -#: ../system/core-workflows/condition-operators.rst:54 -msgid "is modified" +#: ../settings/security/password.rst:73 +msgid "This enforces your users to use at least one digit within the password." msgstr "" -#: ../system/core-workflows/condition-operators.rst:55 -msgid "Matches if content is modified." +#: ../settings/security/password.rst:75 +msgid "The default value is ``yes``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:57 -#: ../system/core-workflows/condition-operators.rst:61 -msgid "True from the moment of changing content until form submit." +#: ../settings/security/password.rst:78 +msgid "Special Character Required" msgstr "" -#: ../system/core-workflows/condition-operators.rst:58 -msgid "is modified to" +#: ../settings/security/password.rst:80 +msgid "" +"This setting allows you to improve your password quality even more by " +"enforcing the password to contain at least one special character." msgstr "" -#: ../system/core-workflows/condition-operators.rst:59 -msgid "Matches if content is modified to a specific value." +#: ../settings/security/ssl-certificates.rst:2 +msgid "SSL Certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:62 -msgid "is none of" +#: ../settings/security/ssl-certificates.rst:7 +msgid "" +"Zammad offers the possibility to upload custom certificates and custom " +"Certificate Authority (CA) certificates. This can be useful if you want to " +"connect Zammad the secure way to other systems which are using custom " +"certificates." msgstr "" -#: ../system/core-workflows/condition-operators.rst:63 -msgid "Matches if content is none of any specified values." +#: ../settings/security/ssl-certificates.rst:12 +msgid "" +"An example usecase might be: You have an internal LDAP server that is not " +"accessible from the internet, and you want a SSL-encrypted connection, using " +"a custom certificate." msgstr "" -#: ../system/core-workflows/condition-operators.rst:65 -msgid "Matches if content is not equal to a specified value." +#: ../settings/security/ssl-certificates.rst:19 +msgid "" +"You should have an existing custom certificate file and/or a custom CA " +"certificate file, which you want to add to Zammad. As filetype ``.crt`` is " +"supported and the certificate format has to be PEM (Base64 ASCII)." msgstr "" -#: ../system/core-workflows/condition-operators.rst:67 -msgid "Matches if content is present." +#: ../settings/security/ssl-certificates.rst:25 +msgid "" +"When you import a custom CA certificate, all certificates generated with " +"this are trusted. This can be useful if you have more than one system/" +"certificate you want to connect to and the certificates are issued from the " +"same custom CA." msgstr "" -#: ../system/core-workflows/condition-operators.rst:68 -#, fuzzy -msgid "just changed" -msgstr "Exchange" - -#: ../system/core-workflows/condition-operators.rst:69 -msgid "Matches if content has changed." +#: ../settings/security/ssl-certificates.rst:31 +msgid "Add a Certificate" msgstr "" -#: ../system/core-workflows/condition-operators.rst:71 -#: ../system/core-workflows/condition-operators.rst:75 +#: ../settings/security/ssl-certificates.rst:33 msgid "" -"Only true for the moment of changing content until next form field action/" -"click." +"To add a custom certificate or a custom CA certificate, head over to the " +"Admin panel > Settings > Security > SSL Certificates. Here you can find a " +"\"Add SSL Certificate\" button. In the dialog you can either select a " +"certificate file or paste the content of the certificate:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:72 -msgid "just changed to" +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate adding dialog" msgstr "" -#: ../system/core-workflows/condition-operators.rst:73 -msgid "Matches if content has changed to a specified value." +#: ../settings/security/ssl-certificates.rst:43 +msgid "" +"After selecting a file or pasting the content of the certificate, click on " +"the \"Add\" button to finally upload it to Zammad. Then, the certificates " +"are immediately effective, no restart or similar required." msgstr "" -#: ../system/core-workflows/condition-operators.rst:76 -msgid "matches regex" +#: ../settings/security/ssl-certificates.rst:49 +msgid "" +"Please note that only single certificate files are supported. That means if " +"you want to import a certificate / CA certificate, it must contain **only " +"one** certificate." msgstr "" -#: ../system/core-workflows/condition-operators.rst:77 -msgid "Matches if value fits to regex rule." +#: ../settings/security/ssl-certificates.rst:54 +msgid "Certificate Overview" msgstr "" -#: ../system/core-workflows/condition-operators.rst:79 -msgid "Matches if no content is present." +#: ../settings/security/ssl-certificates.rst:56 +msgid "" +"After you added a certificate, you can see a table with information for each " +"added certificate:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:80 -msgid "starts with" +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing table of added certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:81 -msgid "Matches if content starts with specified value." +#: ../settings/security/ssl-certificates.rst:64 +msgid "" +"Here you can download the certificate or delete it, if you don't need it " +"anymore." msgstr "" -#: ../system/core-workflows/condition-operators.rst:82 -msgid "starts with one of" +#: ../settings/security/ssl-certificates.rst:68 +#, fuzzy +msgid "Deleting Certificates" +msgstr "Limitação" + +#: ../settings/security/ssl-certificates.rst:70 +msgid "" +"If you want to delete a specific certificate, you can do it by clicking on " +"the menu in the actions column and selecting delete:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:83 -msgid "Matches if content starts with one of the specified values." +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate deletion button" msgstr "" -#: ../system/core-workflows/condition-operators.rst:84 -msgid "till (relative)" +#: ../settings/security/ssl-certificates.rst:79 +msgid "Downloading Certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:85 -msgid "Matches if date/time is before a period of time before an event." +#: ../settings/security/ssl-certificates.rst:81 +msgid "" +"If you want to download your certificates, you can do this as well via " +"corresponding action buttons." msgstr "" -#: ../system/core-workflows/condition-operators.rst:86 -msgid "today" +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate download button" msgstr "" -#: ../system/core-workflows/condition-operators.rst:87 -msgid "Matches if date/time is today." +#: ../settings/security/third-party.rst:13 +msgid "Login Providers" msgstr "" -#: ../system/core-workflows/condition-operators.rst:88 -msgid "within last (relative)" +#: ../settings/security/third-party.rst:2 +msgid "Third-Party Applications" msgstr "" -#: ../system/core-workflows/condition-operators.rst:89 +#: ../settings/security/third-party.rst:4 msgid "" -"Matches if date/time content is within specified period of time before now." +"Third party authentication is a great way to help your users to login to " +"Zammad more easily. If the account is yet unknown, Zammad will create a new " +"user automatically, without the user needed to interact (e.g. type in his " +"name). Another big advantage of this feature is that your user doesn't need " +"to remember another password." msgstr "" -#: ../system/core-workflows/condition-operators.rst:91 -msgid "within next (relative)" +#: ../settings/security/third-party.rst:10 +msgid "" +"You can deactivate logging in via :ref:`security_password_login` if any of " +"the mentioned authentication providers are enabled in your instance." msgstr "" -#: ../system/core-workflows/condition-operators.rst:92 +#: ../settings/security/third-party.rst:27 msgid "" -"Matches if date/time content is within specified period of time after now." +"We're currently missing documentation for the following login providers:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:2 -msgid "How do they work?" +#: ../settings/security/third-party.rst:29 +msgid "LinkedIn" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:4 -msgid "" -"Core Workflows are executed according to their priority. If two workflows " -"have the same priority, they are executed in alphabetical order based on " -"their **name**." +#: ../settings/security/third-party.rst:30 +msgid "Weibo" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:8 -msgid "" -"Because of the way Core Workflows work, all changes to attributes are " -"checked with the application server - please see :doc:`limitations` for " -"possible issues." +#: ../settings/security/third-party.rst:35 +msgid "Automatic Account Link on Initial Logon" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:12 +#: ../settings/security/third-party.rst:37 msgid "" -"Below we're talking about settings that are important and not self-" -"explanatory." +"In general there's two possible options for Zammad on how to deal with " +"already known users as they try to authenticate against a third-party " +"application. By default, Zammad will not automatically link \"unknown\" " +"authentication providers to existing accounts." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:17 +#: ../settings/security/third-party.rst:42 msgid "" -"Choose the object context you want to run the workflow in. This will decide " -"on your available attributes and actions." -msgstr "" - -#: ../system/core-workflows/how-do-they-work.rst:20 -msgid "Ticket objects also have access to the ticket customer." +"This means that the user has to manually link authentication providers to " +"their accounts (for more about this :user-docs:`consult the user " +"documentation `)." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:25 +#: ../settings/security/third-party.rst:46 msgid "" -"Choose in which situation the workflow is applied. Contexts can be combined " -"to avoid duplicate workflows." +"Sometimes this doesn't come in handy as this also means you'll receive error " +"messages about \"email address being in use already\" for (yet) unknown " +"third-party authentication methods." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:30 -msgid "Creation mask" +#: ../settings/security/third-party.rst:50 +msgid "" +"If you want to allow your users to always be able to log in, no matter what, " +"you may want to enable ``Automatic account link on initial logon``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:29 +#: ../settings/security/third-party.rst:None msgid "" -"If selected, your conditions and actions will affect all applicable creation " -"masks." +"Screenshot highlighting the \"Automatic account link on initial logon\"\n" +"setting" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:34 -msgid "Edit mask" +#: ../settings/security/third-party.rst:60 +msgid "Automatic Account Linking Notification" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:33 +#: ../settings/security/third-party.rst:64 msgid "" -"If selected, your conditions and actions will affect all applicable edit " -"masks." +"To improve security and your users awareness, you can enable Zammad to " +"notify your users when a new third-party application has been linked to " +"their account." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:39 +#: ../settings/security/third-party.rst:68 msgid "" -"Zammad differentiates between selected and saved conditions. These can be " -"combined wherever needed." +"This notification is sent out once per third-party application. Zammad does " +"also mention the method used, e.g.: ``Microsoft``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:42 -msgid "**⚠️ Restrict workflows to specific roles if needed!**" +#: ../settings/security/third-party.rst:71 +msgid "By default this setting is not active (set to ``no``)." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:44 +#: ../settings/security/third-party.rst:0 msgid "" -"By default and unless configured in conditions, workflow rules are executed " -"for **all roles**. This also affects your customers!" +"Screenshot showing sample notification mail after initial\n" +"third-party linking" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:50 -msgid "Selected Conditions" +#: ../settings/security/third-party.rst:85 +msgid "" +"This notification is only sent if the account in question already exists. If " +"the login via the third-party also creates the missing account, the " +"notification will be skipped." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:48 -msgid "" -"These conditions are based on form values and match if an appropriate " -"selection is made (e.g. choosing another group in the ticket without " -"saving). This applies for drafts (active selection) and currently saved " -"values." +#: ../settings/security/third-party.rst:89 +msgid "This means it only affects:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:64 -msgid "Saved Conditions" +#: ../settings/security/third-party.rst:91 +msgid "manual account linking within the third-party page of the users profile" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:53 +#: ../settings/security/third-party.rst:92 msgid "" -"These conditions only match if the selected values are stored in the " -"database. It ignores the current value or selection of the field, as long as " -"the changes are not saved (e.g. performing field operations for an existing " -"ticket, which is viewed/opened by an agent)." +"logging into an existing local account by utilizing the *automatic account " +"link on initial logon* functionality" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:60 +#: ../settings/security/third-party.rst:None msgid "" -"Keep in mind that the value has to be available in the situation where you " -"need it. Otherwise the condition won't match." +"Screenshot showing the \"automatic account linking notification\"\n" +"setting" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:63 -msgid "" -"Example: you can't perform any actions with *saved condition* on a ticket in " -"creation, because there are no saved values at that time." +#: ../settings/security/third-party.rst:100 +msgid "No User Creation on Logon" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:66 +#: ../settings/security/third-party.rst:102 msgid "" -"You can find a description of the condition operators for core workflows :" -"doc:`here `." +"By default, Zammad will create a new user account if the user logs in via a " +"third-party application and the account doesn't exist yet." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:72 +#: ../settings/security/third-party.rst:105 msgid "" -"Which actions should we run on the relevant fields? The possible actions " -"depend on the object type. However, usually you can at least change the " -"visibility and whether the field is mandatory." +"If you want to prevent Zammad from creating new accounts on logon, you can " +"disable this feature by setting ``No user creation on logon`` to ``yes``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:76 -msgid "Be aware that actions are not available for **related** context." +#: ../settings/security/third-party.rst:None +msgid "Screenshot showing the \"no user creation on logon\" setting" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:78 +#: ../settings/security/third-party/facebook.rst:4 msgid "" -"**Example:** Let's assume you are working in the ticket context. While you " -"can have customer *conditions*, you *can't adjust* objects with actions in " -"that scope. That's because this wouldn't have any impact on the ticket " -"dialog. Of course all ticket attributes (state, owner, ...) are available." +"It is possible to create a quick login for your helpdesk via Facebook To do " +"so, you need to follow these steps:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:84 +#: ../settings/security/third-party/facebook.rst:9 +#, fuzzy +msgid "Register Facebook App" +msgstr "Registrar uma aplicação de robô do Telegram" + +#: ../settings/security/third-party/facebook.rst:11 msgid "" -"Please also have a look at our :doc:`limitations` to be safe from surprises." +"Visit [https://developers.facebook.com/apps/] and click on \"Add a new App\"" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:88 -msgid "Available Operators" +#: ../settings/security/third-party/facebook.rst:None +msgid "initial page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:90 -msgid "The availability of operators depends on the object type and scope." +#: ../settings/security/third-party/facebook.rst:17 +msgid "After that enter the app settings" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:94 -msgid "" -"Please note that actions may or may not restrict API based access to " -"attributes. We're displaying the following icons for your overview to " -"understand these limits better:" +#: ../settings/security/third-party/facebook.rst:None +msgid "Create App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:0 -msgid "|api| This icon indicates the action affects the API." +#: ../settings/security/third-party/facebook.rst:22 +msgid "Navigate to \"Settings\" and fill in this infromation" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:163 -msgid "api" +#: ../settings/security/third-party/facebook.rst:None +msgid "App Settings" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:0 -msgid "|ui| This icon indicates the action only affects the web interface." +#: ../settings/security/third-party/facebook.rst:27 +msgid "Navigate to app review and Check \"Make [appname] public?\"" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:167 -msgid "ui" +#: ../settings/security/third-party/facebook.rst:None +msgid "App Review" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:102 -msgid "show |ui|" -msgstr "" +#: ../settings/security/third-party/facebook.rst:35 +#, fuzzy +msgid "Configure Zammad as Facebook App" +msgstr "Configure o Zammad como um robô do Telegram" -#: ../system/core-workflows/how-do-they-work.rst:102 -msgid "Display the chosen field. Allows setting of values." +#: ../settings/security/third-party/facebook.rst:37 +msgid "" +"Navigate to \"Admin -> Security -> Third Party Applications\" and enter the " +"App ID and the App Secret. You can find this Key in the Dashbard of your " +"Facebok app." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:109 -msgid "hide |ui|" +#: ../settings/security/third-party/facebook.rst:None +msgid "Zammad Configuration" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:105 +#: ../settings/security/third-party/facebook.rst:44 +#: ../settings/security/third-party/github.rst:43 +#: ../settings/security/third-party/gitlab.rst:46 msgid "" -"Hide the chosen field. However, it technically still allows setting the " -"field." +"Now you can link accounts via \"Avatar -> Profile -> Link Accounts\" or " +"login via Zammad login page." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:108 -msgid "" -"Please note that the field is **not** gone and still contains an existing " -"value (if set)! Consider *remove* instead, if you want this field to be gone." +#: ../settings/security/third-party/github.rst:2 +#: ../system/integrations/github.rst:2 +msgid "GitHub" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:112 -msgid "remove |ui|" +#: ../settings/security/third-party/github.rst:4 +msgid "" +"It is possible to create a quick login for your helpdesk via GitHub. To " +"activate the quick login you need to enable OAuth for GitHub." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:112 -msgid "Entirely removes the field. The field value will not be evaluated." +#: ../settings/security/third-party/github.rst:8 +msgid "Register GitHub App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:115 -msgid "set mandatory |ui| |api|" +#: ../settings/security/third-party/github.rst:10 +msgid "" +"Visit https://www.github.com/settings/applications/new and enter the app " +"settings. As callback URL enter \"https://zammad_host/auth/github/callback\" " +"where zammad_host has to be replaced with your Zammad FQDN" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:115 -msgid "Sets the field to mandatory." +#: ../settings/security/third-party/github.rst:None +msgid "Register OAuth app on www.github.com" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:118 -msgid "set optional |ui| |api|" +#: ../settings/security/third-party/github.rst:19 +#, fuzzy +msgid "Configure Zammad as GitHub App" +msgstr "Configure o Zammad como um robô do Telegram" + +#: ../settings/security/third-party/github.rst:21 +msgid "" +"Enter the \"APP ID\" and the \"APP SECRET\" from the GitHub OAUTH " +"Applications Dashboard" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:118 -msgid "Sets the field to optional." +#: ../settings/security/third-party/github.rst:None +msgid "GitHub config in Zammad admin interface" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:124 -msgid "add option |ui| |api|" +#: ../settings/security/third-party/github.rst:28 +msgid "" +"After you configured the GitHub credentials and activated the login method, " +"you should see a new icon on the login page." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:121 -msgid "Allows adding options to tree selects or selects." +#: ../settings/security/third-party/github.rst:None +msgid "GitHub logo on login page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:123 +#: ../settings/security/third-party/github.rst:34 msgid "" -"You have to use the \"remove option\" before performing this action. It " -"allows you to use *existing* configured values." +"If you click on the icon you will be redirected to GitHub and see something " +"similar to this:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:128 -msgid "remove option |ui| |api|" +#: ../settings/security/third-party/github.rst:None +msgid "GitHub oauth page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:127 +#: ../settings/security/third-party/github.rst:40 +#: ../settings/security/third-party/gitlab.rst:42 msgid "" -"Allows removing options from tree selects or selects. It allows you to use " -"*existing* configured values." +"When you grant the access you will be redirected to your Zammad instance and " +"logged in as a customer." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:134 -msgid "set fixed to |ui| |api|" +#: ../settings/security/third-party/gitlab.rst:2 +msgid "Gitlab" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:131 -msgid "Reduces the available options by your selection." +#: ../settings/security/third-party/gitlab.rst:4 +msgid "" +"It is possible to create a quick login for your helpdesk via Gitlab. To " +"activate the quick login you need to enable OAuth for Gitlab." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:133 -msgid "" -"This reduces your workflows in terms of *add option* and *remove option*." +#: ../settings/security/third-party/gitlab.rst:8 +#, fuzzy +msgid "Register Gitlab App" +msgstr "Registrar uma aplicação de robô do Telegram" + +#: ../settings/security/third-party/gitlab.rst:10 +msgid "To register an app in Gitlab open your profile and select applications." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:137 -msgid "fill in |ui|" +#: ../settings/security/third-party/gitlab.rst:12 +msgid "" +"As callback URL enter \"https://zammad-fqdn/auth/gitlab/callback\" where " +"zammad-fqdn has to be replaced with your Zammad FQDN" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:137 -msgid "Allows filling in of string and integer fields with your values." +#: ../settings/security/third-party/gitlab.rst:None +msgid "Register OAuth app on gitlab instance" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:141 -msgid "fill in empty |ui|" +#: ../settings/security/third-party/gitlab.rst:18 +msgid "Just select *read_user* under scopes as in the screenshot and save it." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:140 +#: ../settings/security/third-party/gitlab.rst:21 +#, fuzzy +msgid "Configure Zammad as Gitlab App" +msgstr "Configure o Zammad como um robô do Telegram" + +#: ../settings/security/third-party/gitlab.rst:23 msgid "" -"Allows filling in of string and integer fields with your values **if the " -"field is empty**." +"Enter the \"APP ID\" and the \"APP SECRET\" from the Gitlab OAUTH " +"Applications Dashboard and your Gitlab-URL in the \"SITE\" field." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:144 -msgid "select |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab config in Zammad admin interface" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:144 -msgid "Select a specific value within a select, tree select or boolean field." +#: ../settings/security/third-party/gitlab.rst:30 +msgid "" +"After you configured the Gitlab credentials and activated the login method, " +"you should see a new icon on the login page." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:153 -msgid "auto select |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab logo on login page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:147 -msgid "Helps users with tree select and select fields:" +#: ../settings/security/third-party/gitlab.rst:36 +msgid "" +"If you click on the icon you will be redirected to Gitlab and see something " +"similar to this:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:149 -msgid "" -"If the field has only one option available for selection and no value yet, " -"the value will be automatically set." +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab oauth page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:152 +#: ../settings/security/third-party/google.rst:4 msgid "" -"This option only works if you have one value and doesn't work if there is " -"more than one option available." +"With some easy and fast steps, you can enable Zammad to authenticate your " +"users via Google." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:157 -msgid "set readonly |ui|" -msgstr "" +#: ../settings/security/third-party/google.rst:8 +#, fuzzy +msgid "Register a Google App" +msgstr "Registrar uma aplicação de robô do Telegram" -#: ../system/core-workflows/how-do-they-work.rst:156 +#: ../settings/security/third-party/google.rst:10 msgid "" -"Allows you to display an attribute as read only (which means no changes are " -"possible)." +"First of all, we need to create a new project - you can skip this step if " +"you already have one." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:161 -msgid "unset readonly |ui|" +#: ../settings/security/third-party/google.rst:15 +msgid "" +"Use this link to create a new project: https://console.cloud.google.com/" +"projectcreate" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:160 +#: ../settings/security/third-party/google.rst:18 msgid "" -"In case a workflow set the field in question to read only, you can undo this " -"with option above." +"Now expand the menu, expand \"APIs & Services\" and select \"Credentials\". " +"Go to the tab \"OAuth consent screen\" first and ensure to fill in the " +"requested information - without doing so you can't create credentials!" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:172 -msgid "Stop after match" +#: ../settings/security/third-party/google.rst:None +msgid "Creating a consent screen" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:174 +#: ../settings/security/third-party/google.rst:25 msgid "" -"Here you can decide if other workflows are executed after the current one." +"After filling in and saving the consent screen information, you can go to " +"the \"Credentials\" tab and create new \"OAuth client ID\"-Credentials." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:176 +#: ../settings/security/third-party/google.rst:28 msgid "" -"If set to ``no`` (default), further workflows will be executed if they match " -"the condition. In this case, it is possible that your actions from the " -"current workflow can be overwritten by another workflow." +"Fill in the necessary information as follows and replace ``zammad_host`` " +"with your FQDN:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:180 -msgid "" -"If set to ``yes``, no further worflows will be executed after the current " -"one." +#: ../settings/security/third-party/google.rst:31 +msgid "**Application type** ``[x] Web application``" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:184 -msgid "Priority" -msgstr "Prioridade" - -#: ../system/core-workflows/how-do-they-work.rst:186 -msgid "" -"You can define the sequence, in which the workflows are executed. The " -"default value is ``500``." +#: ../settings/security/third-party/google.rst:34 +msgid "**Authorized JavaScript origins** ``https://zammad_host/``" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:189 +#: ../settings/security/third-party/google.rst:37 msgid "" -"The workflows are executed in ascending order by their priority. That means " -"lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." +"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" +"callback``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:2 -#, fuzzy -msgid "Learn by Example" -msgstr "**Por exemplo:**" - -#: ../system/core-workflows/learn-by-example.rst:4 -msgid "" -"This page provides some basic examples for Core Workflows. Of course you can " -"build much more complex workflows if needed." +#: ../settings/security/third-party/google.rst:None +msgid "Adding a new OAuth client ID" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:7 +#: ../settings/security/third-party/google.rst:43 msgid "" -"To learn about Core Workflows in detail, first go to :doc:`how-do-they-work`." +"After creating the credentials, go to your Zammad installation and navigate " +"to \"Admin > Security > Third Party Applications\" > Google. Enter your " +"Client ID and Client secret here." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:10 -#, fuzzy -msgid "Group Based Examples" -msgstr "**Por exemplo:**" - -#: ../system/core-workflows/learn-by-example.rst:12 -msgid "" -"All following workflows have the same base configurations. The workflow may " -"not use them all." +#: ../settings/security/third-party/google.rst:None +msgid "Zammad" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:15 -#, fuzzy -msgid "Groups:" -msgstr "Grupos" - -#: ../system/core-workflows/learn-by-example.rst:20 -#, fuzzy -msgid "Attributes:" -msgstr "Atributos do artigo" +#: ../settings/security/third-party/google.rst:50 +msgid "After submitting, the login via Google can be used." +msgstr "" -#: ../system/core-workflows/learn-by-example.rst:22 -msgid "Category (Single tree selection field, not mandatory, agents only)" +#: ../settings/security/third-party/microsoft.rst:2 +msgid "Microsoft" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:23 +#: ../settings/security/third-party/microsoft.rst:4 msgid "" -"Approved (Boolean field, not mandatory, not shown, ``false`` as default)" +"Zammad's Microsoft connection allows your users with Microsoft accounts to " +"login. This works for Azure users as well and can be an alternative to :doc:" +"`/system/integrations/ldap/index`." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:24 -msgid "Operating System (Text field, not mandatory, not shown)" +#: ../settings/security/third-party/microsoft.rst:10 +msgid "" +"This documentation part does not cover our :doc:`📧 Microsoft 365 email " +"channel `." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:25 -msgid "Software used (Single selection field, not mandatory, not shown)" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screenshot showing Microsoft login button on Zammad login screen." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:68 -msgid "Group specific values and fields" +#: ../settings/security/third-party/microsoft.rst:30 +#: ../settings/security/third-party/microsoft.rst:53 +msgid "Supported account types:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:28 +#: ../settings/security/third-party/microsoft.rst:22 msgid "" -"This workflow set depends on the category field. It reduces the available " -"set of values based on the group selected." +"Please note that Zammad only supports these account types (App dependent):" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:33 -msgid "Workflow 2nd Level group" +#: ../settings/security/third-party/microsoft.rst:35 +msgid "Avatars of signing in users:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:35 +#: ../settings/security/third-party/microsoft.rst:33 msgid "" -"This reduces the category options to ``2nd Level/*``, ``Internal/*`` and " -"``Others``. It also sets further required fields to mandatory and visible." +"Zammad currently ignores user avatars. If the user is registered with e.g. " +"Gravatar, Zammad will fetch the avatar from there if enabled. See :doc:" +"`Zammad Image Service ` for more." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for 2nd level" +#: ../settings/security/third-party/microsoft.rst:38 +msgid "Step 1 - Register a Microsoft App for Zammad" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:43 -msgid "Workflow Support group" +#: ../settings/security/third-party/microsoft.rst:40 +msgid "" +"Login to the `Microsoft Azure Portal `_ and " +"navigate to App registrations to create a new app. Provide the requested " +"information as follows and register your app." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:45 -msgid "" -"This reduces the category options to ``Support/*``, ``Internal/*`` and " -"``Others``. It also sets further required fields to visible." +#: ../settings/security/third-party/microsoft.rst:46 +msgid "Name:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for support" +#: ../settings/security/third-party/microsoft.rst:45 +msgid "" +"Any meaningful name fitting, this name will be displayed to users trying to " +"authenticate with this app." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:53 -msgid "Workflow Sales group" +#: ../settings/security/third-party/microsoft.rst:49 +msgid "Choose one of the above mentioned account types (see Limitations)." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:55 +#: ../settings/security/third-party/microsoft.rst:51 msgid "" -"This reduces the category options to ``Sales/*``, ``Internal/*`` and " -"``Others``." +"The correct account type depends on your use case. If you want to use the " +"authentication internal only, choose the first option. If you're unsure, use " +"the \"Help me choose...\" link." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for sales" +#: ../settings/security/third-party/microsoft.rst:58 +msgid "Redirect URI (optional):" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:68 -#: ../system/integrations/slack.rst:88 -msgid "The Result" +#: ../settings/security/third-party/microsoft.rst:56 +msgid "" +"Select web and provide your callback URL. The callback URL looks like this: " +"``https://zammad.domain.tld/auth/microsoft_office365/callback``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:63 -msgid "" -"This is what the agent would experience with the above workflows in place." +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to register a Microsoft app" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "" -"Workflow shows objects and limits options based on selections on the group" +#: ../settings/security/third-party/microsoft.rst:71 +msgid "Within **API permissions** add the following permissions:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:90 -msgid "Approval process" +#: ../settings/security/third-party/microsoft.rst:69 +msgid "``User.Read``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:71 -msgid "" -"In this case ``approved`` is visible to agents by default. For this " -"workflow, an additional role ``Approval person`` is required (no further " -"permissions)." +#: ../settings/security/third-party/microsoft.rst:71 +msgid "Contacts" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that restricts an approval attribute to specific roles" +#: ../settings/security/third-party/microsoft.rst:71 +msgid "``Contacts.Read``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:81 +#: ../settings/security/third-party/microsoft.rst:73 msgid "" -"This workflow may work best in combination with a :doc:`trigger ` but technically, this is not required." +"You can find these permissions within *Microsoft Graph → Delegated " +"permissions*." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:84 -msgid "" -"Select fields may be a better approach because they allow more values than " -"just a simple ``true`` or ``false``." +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to add required API permissions" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 +#: ../settings/security/third-party/microsoft.rst:80 msgid "" -"Workflow fixes possible values of \"Approved ?\" to a specific selection " -"depending on the users role" +"Within **Certificates & secrets** create a new client secret. Note down the " +"returned secret **value** for later. **Do not** use the secret ID!" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:103 -msgid "State dependent mandatory fields" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to create a new app secret" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:93 +#: ../settings/security/third-party/microsoft.rst:88 msgid "" -"This workflow sets ``Category`` to mandatory if the agent wants to set the " -"states ``closed`` or ``pending close`` to enforce categorization." +"From **Overview** copy your apps *Application (client) ID*. If you're using " +"a single tenant app, please also copy *Directory (tenant) ID*. You now have " +"all required information for Zammad." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that sets fields to mandatory on specific states" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to retreive application client and tenant IDs" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 +#: ../settings/security/third-party/microsoft.rst:98 +msgid "Step 2 - Add App Credentials to Zammad" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:100 msgid "" -"Workflow sets category field to mandatory upon choosing closed or pending " -"close as state" +"Navigate to Security > Third-party Applications (Tab) within Zammad's admin " +"settings. Scroll down to the section *Authentication via Microsoft* and fill " +"in the required information." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:106 -msgid "Manual Ticket Handover Process" +#: ../settings/security/third-party/microsoft.rst:105 +msgid "App ID:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:108 -msgid "This example covers the handover of a ticket from one agent to another:" +#: ../settings/security/third-party/microsoft.rst:105 +msgid "This is your *Application (client) ID*." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:110 -msgid "" -"When the ticket owner is modified, a new text field (\"Handover\") shows up " -"for a comment" +#: ../settings/security/third-party/microsoft.rst:108 +msgid "App secret:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:112 -msgid "" -"This may only be visible when the owner is changed, therefore it has to be " -"hidden in general" +#: ../settings/security/third-party/microsoft.rst:108 +msgid "This is your *client secret* (value)." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:114 -msgid "The input in this handover text field is mandatory" +#: ../settings/security/third-party/microsoft.rst:113 +msgid "App Tenant ID:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:115 +#: ../settings/security/third-party/microsoft.rst:111 msgid "" -"After submitting changes, the value of the handover field must be added as " -"an note to the ticket (via trigger)" +"**optional** only required for apps that use account type *Accounts in this " +"organizational directory only (Default Directory only - Single tenant).*" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:121 -msgid "Hiding handover field" +#: ../settings/security/third-party/microsoft.rst:115 +msgid "" +"Apply your settings by pressing submit and activate *Authentication via " +"Microsoft*." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Hiding the handover field in core workflows" +#: ../settings/security/third-party/microsoft.rst:None +msgid "" +"Screencast showing how to add app credentials and activating the\n" +"authentication method" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:126 -msgid "Showing handover field and setting it to mandatory" +#: ../settings/security/third-party/saml.rst:2 +msgid "SAML" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Showing the handover field and set it as mandatory" +#: ../settings/security/third-party/saml.rst:4 +msgid "" +"Connect your SAML (Security Assertion Markup Language) identity provider as " +"a single sign-on (SSO) method." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:131 -msgid "Trigger writing handover input to a new article" +#: ../settings/security/third-party/saml.rst:7 +msgid "" +"SAML is an open standard for SSO authentication (among other things). Sign-" +"ins are shared across multiple **service providers** and managed by a " +"central **identity provider** (IdP)." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Write handover content to a new article" +#: ../settings/security/third-party/saml.rst:11 +msgid "" +"In this case, the service provider is Zammad, and the IdP is a software " +"service that you either host or subscribe to (*e.g.,* `Keycloak `_, `Redhat SSO Server `_, `ADFS `_, or `Okta `_)." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:133 +#: ../settings/security/third-party/saml.rst:18 msgid "" -"As a result, the ticket includes an article of the type note which includes " -"the predefined text and the handover comment." +"This guide assumes you are already using SAML within your organization (i." +"e., that your IdP is fully set up)." msgstr "" -#: ../system/core-workflows/limitations.rst:6 -msgid "Core Workflows do not replace Triggers" +#: ../settings/security/third-party/saml.rst:21 +msgid "" +"Please note: Our instructions are based on connecting Zammad with Keycloak." msgstr "" -#: ../system/core-workflows/limitations.rst:5 -msgid "" -"Workflows manipulate the behavior of fields. However, they do not set values " -"in fields because of actions." +#: ../settings/security/third-party/saml.rst:25 +msgid "Step 1: Configure Your IdP" msgstr "" -#: ../system/core-workflows/limitations.rst:16 -msgid "API calls are only partly affected" +#: ../settings/security/third-party/saml.rst:28 +msgid "Add Zammad as a Client/App" msgstr "" -#: ../system/core-workflows/limitations.rst:9 +#: ../settings/security/third-party/saml.rst:30 msgid "" -"Some options affect UI only and thus do not restrict responses and calls." +"Import Zammad into your IdP using the XML configuration found at ``https://" +"your.zammad.domain/auth/saml/metadata``." msgstr "" -#: ../system/core-workflows/limitations.rst:11 -msgid "This affects the following actions:" +#: ../settings/security/third-party/saml.rst:33 +msgid "" +"If your IdP doesn't support XML import, you will have to configure Zammad as " +"a new client/app manually using the above XML metadata file for reference." msgstr "" -#: ../system/core-workflows/limitations.rst:13 -msgid "select" +#: ../settings/security/third-party/saml.rst:36 +msgid "For instance, when you see this tag:" msgstr "" -#: ../system/core-workflows/limitations.rst:14 -msgid "auto select" +#: ../settings/security/third-party/saml.rst:42 +msgid "" +"Set the **Assertion Consumer Service Binding URL** (sometimes also listed as " +"**Valid Redirect URIs**) to ``http://your.zammad.domain/auth/saml/callback``." msgstr "" -#: ../system/core-workflows/limitations.rst:15 -msgid "show" +#: ../settings/security/third-party/saml.rst:47 +msgid "Set Up User Attribute Mapping" msgstr "" -#: ../system/core-workflows/limitations.rst:16 -msgid "hide" +#: ../settings/security/third-party/saml.rst:49 +msgid "" +"Zammad requests the following user attributes (or “properties”) from the IdP:" msgstr "" -#: ../system/core-workflows/limitations.rst:25 -msgid "Some fields stay unavailable to customers" +#: ../settings/security/third-party/saml.rst:51 +msgid "Email address (``email``)" msgstr "" -#: ../system/core-workflows/limitations.rst:19 -msgid "" -"For technical and security reasons, some default fields (the pale ones you " -"can't edit) stay unavailable for display and usage on customer permissions." +#: ../settings/security/third-party/saml.rst:52 +msgid "Full name (``name``)" msgstr "" -#: ../system/core-workflows/limitations.rst:23 -msgid "" -"If you require your customers to change e.g. priorities, please consider " -"using workarounds via :doc:`/system/objects` and :doc:`/manage/trigger`." +#: ../settings/security/third-party/saml.rst:53 +msgid "Given name (``first_name``)" msgstr "" -#: ../system/core-workflows/limitations.rst:29 -msgid "Ticket title changes not supported in edit mask" +#: ../settings/security/third-party/saml.rst:54 +msgid "Family name (``last_name``)" msgstr "" -#: ../system/core-workflows/limitations.rst:28 +#: ../settings/security/third-party/saml.rst:56 msgid "" -"It is currently not possible to perform changes of the ticket title in the " -"edit mask (e.g. renaming, set to read-only)." +"You may need to set up “mappers” (or “mappings”) to tell your IdP how user " +"attributes in SAML correspond to those in Zammad. For a more detailed " +"breakdown, refer to the XML metadata file referenced in the previous section." msgstr "" -#: ../system/core-workflows/limitations.rst:37 -msgid "What is out of scope of Core Workflows?" +#: ../settings/security/third-party/saml.rst:62 +msgid "Per-IdP Instructions" msgstr "" -#: ../system/core-workflows/limitations.rst:32 +#: ../settings/security/third-party/saml.rst:102 +msgid "Keycloak" +msgstr "" + +#: ../settings/security/third-party/saml.rst:65 msgid "" -"There are some things that would count as workflow but are either done via :" -"doc:`/manage/trigger` or :doc:`/manage/scheduler`." +"**To add Zammad as a client,** save the XML configuration to disk (``https://" +"your.zammad.domain/auth/saml/metadata``) and use **Clients > Clients list > " +"Import client** in the Keycloak admin panel." msgstr "" -#: ../system/core-workflows/limitations.rst:35 -msgid "Such as (but not limited to):" +#: ../settings/security/third-party/saml.rst:70 +msgid "" +"To help Zammad **match its own user accounts to Keycloak users**, create a " +"user attribute (or “property”) mapper. In **Clients list**, click on your " +"newly created Client ID, choose the tab **Client scopes** and click on the " +"link which refers to your Zammad instance. Choose **Add mapper > By " +"configuration > User Property** and create a mapper with the following " +"entries:" msgstr "" -#: ../system/core-workflows/limitations.rst:37 -msgid "up- or downgrade permissions of users" +#: ../settings/security/third-party/saml.rst:78 +msgid "**Name**" msgstr "" -#: ../system/core-workflows/limitations.rst:38 -msgid "affecting article creation or listing" +#: ../settings/security/third-party/saml.rst:80 +msgid "**Mapper Type**" msgstr "" -#: ../system/data-privacy.rst:2 -msgid "Data Privacy" +#: ../settings/security/third-party/saml.rst:81 +msgid "``User Property``" msgstr "" -#: ../system/data-privacy.rst:4 -msgid "" -"For compliance with GDPR and other data privacy laws, you may wish to " -"**permanently delete users from the system**, along with **all of their " -"associated tickets**." +#: ../settings/security/third-party/saml.rst:82 +msgid "**Property**" 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 `!" +#: ../settings/security/third-party/saml.rst:83 +msgid "``emailAddress``" msgstr "" -#: ../system/data-privacy.rst:12 -msgid "" -"Access to this panel requires ``admin.data_privacy`` permissions (introduced " -"in Zammad 3.5)." +#: ../settings/security/third-party/saml.rst:84 +msgid "**SAML Attribute Name**" msgstr "" -#: ../system/data-privacy.rst:15 -msgid "" -"On older systems that have not been updated yet, customers can also be :docs:" -"`deleted via the Zammad console `." +#: ../settings/security/third-party/saml.rst:86 +msgid "**SAML Attribute NameFormat**" msgstr "" -#: ../system/data-privacy.rst:22 -msgid "User deletion dialog in the Data Privacy panel" +#: ../settings/security/third-party/saml.rst:87 +msgid "``basic``" msgstr "" -#: ../system/data-privacy.rst:22 +#: ../settings/security/third-party/saml.rst:89 msgid "" -"The user deletion dialog lists some of the tickets that will be removed from " -"the system along with the user." +"In the example above, we're telling Zammad that whenever it receives a SAML " +"login request, it should take the ``email`` property from Keycloak, look for " +"a Zammad user with the same ``email`` attribute, and create a new session " +"for that user." msgstr "" -#: ../system/data-privacy.rst:27 -#, fuzzy -msgid "Deleting Users via GUI" -msgstr "Limitação" - -#: ../system/data-privacy.rst:29 -msgid "🔥 **All deletions are FINAL!**" -msgstr "" - -#: ../system/data-privacy.rst:31 -msgid "Once you click “Delete”, the action cannot be canceled or undone." +#: ../settings/security/third-party/saml.rst:95 +msgid "" +"If your Keycloak users' email addresses are stored on another property (*e." +"g.,* ``username``), adjust accordingly." msgstr "" -#: ../system/data-privacy.rst:33 +#: ../settings/security/third-party/saml.rst:98 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." +"Back in **Settings**, enter the Client ID (``https://your.zammad.domain/auth/" +"saml/metadata``) in the field **Master SAML Processing URL**." msgstr "" -#: ../system/data-privacy.rst:36 -msgid "**The following records cannot be deleted:**" +#: ../settings/security/third-party/saml.rst:101 +msgid "You also need to enable **Sign assertions**." msgstr "" -#: ../system/data-privacy.rst:38 -msgid "your own account" +#: ../settings/security/third-party/saml.rst:105 +msgid "Step 2: Configure Zammad" msgstr "" -#: ../system/data-privacy.rst:39 -msgid "the system's last remaining administrator account" +#: ../settings/security/third-party/saml.rst:107 +msgid "" +"Enable SAML and enter your IdP's details in the Admin Panel under **Settings " +"> Security > Third Party Applications > Authentication via SAML**:" msgstr "" -#: ../system/data-privacy.rst:42 -msgid "Step 1: Find a User / Confirm Deletion" +#: ../settings/security/third-party/saml.rst:None +#, fuzzy +msgid "Example configuration of SAML part 1" +msgstr "Configuração" + +#: ../settings/security/third-party/saml.rst:119 +msgid "Display name" msgstr "" -#: ../system/data-privacy.rst:44 -msgid "There are three ways to access the user deletion dialog:" +#: ../settings/security/third-party/saml.rst:116 +msgid "" +"Allows you to define a custom button name for SAML. This helps your users to " +"understand better what the button on the login page does." msgstr "" -#: ../system/data-privacy.rst:51 -msgid "**from the user's profile**" +#: ../settings/security/third-party/saml.rst:119 +msgid "Defaults to ``SAML``." msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Accessing the user deletion dialog in a user profile" +#: ../settings/security/third-party/saml.rst:123 +msgid "IDP SSO target URL" msgstr "" -#: ../system/data-privacy.rst:51 -msgid "Click **Action > Delete**." +#: ../settings/security/third-party/saml.rst:122 +msgid "" +"This is the target URL Zammad shall redirect to when the user presses the " +"SAML button. For Keycloak, this needs to look like https://your.domain/" +"realms/your-realm/protocol/saml" msgstr "" -#: ../system/data-privacy.rst:58 -msgid "**in the “Manage > Users” Admin Panel**" +#: ../settings/security/third-party/saml.rst:127 +msgid "IDP single logout target URL" msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Accessing the user deletion dialog under “Users” in the Admin Panel" +#: ../settings/security/third-party/saml.rst:126 +msgid "" +"This is the URL to which the single logout request and response should be " +"sent." msgstr "" -#: ../system/data-privacy.rst:58 -msgid "Use the **⋮ Actions** menu for the target user." +#: ../settings/security/third-party/saml.rst:131 +#, fuzzy +msgid "IDP certificate" +msgstr "Limitação" + +#: ../settings/security/third-party/saml.rst:130 +msgid "" +"The public certificate of your IDP for Zammad to verify during the callback " +"phase." msgstr "" -#: ../system/data-privacy.rst:66 ../system/data-privacy.rst:104 -msgid "**in the “System > Data Privacy” Admin Panel**" +#: ../settings/security/third-party/saml.rst:145 +msgid "IDP certificate fingerprint" msgstr "" -#: ../system/data-privacy.rst:0 +#: ../settings/security/third-party/saml.rst:134 msgid "" -"Accessing the user deletion dialog under “Data Privacy” in the Admin Panel" +"The fingerprint of your IDPs public certificate to verify during callback " +"phase." msgstr "" -#: ../system/data-privacy.rst:65 -msgid "" -"Use the **New Deletion Task** button. Search for users by name or email " -"address." +#: ../settings/security/third-party/saml.rst:137 +msgid "🔏 **For the IdP certificate / certificate fingerprint:**" msgstr "" -#: ../system/data-privacy.rst:79 -#, fuzzy -msgid "**Delete organizations**" -msgstr "Organizações" +#: ../settings/security/third-party/saml.rst:139 +msgid "" +"Provide **only one or the other**—do not provide both! (Between the two, we " +"recommend the signing certificate itself: fingerprints use SHA-1, which `has " +"been broken for a while now `_.)" +msgstr "" -#: ../system/data-privacy.rst:69 +#: ../settings/security/third-party/saml.rst:144 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:" +"**Keycloak users:** Find your certificate in the Keycloak admin panel under " +"**Realm Settings > Keys > Algorithm: RS256 > Certificate**." msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Deleting an organization via the user deletion dialog" +#: ../settings/security/third-party/saml.rst:151 +msgid "Name identifier format" msgstr "" -#: ../system/data-privacy.rst:78 +#: ../settings/security/third-party/saml.rst:148 msgid "" -"If this option does not appear, make sure there are no pending deletion " -"tasks for other customers from this organization." +"This is the unique identifiers field type. Usually it should be ``urn:oasis:" +"names:tc:SAML:1.1:nameid-format:emailAddress``." msgstr "" -#: ../system/data-privacy.rst:82 -msgid "Step 2: Monitor Deletion Job Status" +#: ../settings/security/third-party/saml.rst:151 +msgid "Zammad **expects an email address as unique identifier**!" msgstr "" -#: ../system/data-privacy.rst:84 +#: ../settings/security/third-party/saml.rst:155 +#, fuzzy +msgid "UID attribute name" +msgstr "Atributos do artigo" + +#: ../settings/security/third-party/saml.rst:154 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:" +"Here you can define an attribute that uniquely identifies the user. If " +"unset, the name identifier returned by the IDP is used." msgstr "" -#: ../system/data-privacy.rst:98 -msgid "**in the Activity Stream**" +#: ../settings/security/third-party/saml.rst:None +#, fuzzy +msgid "Example configuration of SAML part 2" +msgstr "Configuração" + +#: ../settings/security/third-party/saml.rst:163 +msgid "" +"Decide if the certificate for the connection to the IdP service has to be " +"verified or not (default: ``yes``)." msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Activity Stream showing data privacy tasks" +#: ../settings/security/third-party/saml.rst:169 +msgid "Signing & Encrypting" msgstr "" -#: ../system/data-privacy.rst:94 +#: ../settings/security/third-party/saml.rst:169 msgid "" -"For each deleted user, the Activity Stream will be updated twice—once when " -"the task is created, and once when it's complete." +"Define if you want to sign, encrypt, do both or nothing for the requests." msgstr "" -#: ../system/data-privacy.rst:97 -msgid "" -"These notifications are only visible to users with ``admin.data_privacy`` " -"permissions." +#: ../settings/security/third-party/saml.rst:179 +msgid "Certificate (PEM)" msgstr "" -#: ../system/data-privacy.rst:0 +#: ../settings/security/third-party/saml.rst:172 msgid "" -"The task list within Data Privacy shows removals being in progress and " -"completed." +"Paste the public certificate of your Zammad SAML client, if you want to " +"encrypt the requests." msgstr "" -#: ../system/data-privacy.rst:107 -msgid "Frequently Asked Questions" +#: ../settings/security/third-party/saml.rst:175 +#, fuzzy +msgid "Make sure the certificate is:" +msgstr "Limitação" + +#: ../settings/security/third-party/saml.rst:177 +msgid "already valid and not yet expired" msgstr "" -#: ../system/data-privacy.rst:121 -msgid "What happens if I receive an email from a deleted customer?" +#: ../settings/security/third-party/saml.rst:178 +#, fuzzy +msgid "no CA certificate" +msgstr "Limitação" + +#: ../settings/security/third-party/saml.rst:179 +msgid "valid for signing and encrypting" msgstr "" -#: ../system/data-privacy.rst:110 -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." +#: ../settings/security/third-party/saml.rst:185 +msgid "Private key (PEM)" msgstr "" -#: ../system/data-privacy.rst:115 +#: ../settings/security/third-party/saml.rst:182 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**." +"Paste the private key of your Zammad SAML client here, if you want to sign " +"the requests." msgstr "" -#: ../system/data-privacy.rst:130 -msgid "What about user information stored in internal notes or other messages?" +#: ../settings/security/third-party/saml.rst:185 +msgid "Make sure the key is an RSA key with a length of at least 2048 bits." msgstr "" -#: ../system/data-privacy.rst:124 -msgid "" -"The deletion process removes **user accounts and associated tickets only**." +#: ../settings/security/third-party/saml.rst:188 +msgid "Private key secret" msgstr "" -#: ../system/data-privacy.rst:126 -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." +#: ../settings/security/third-party/saml.rst:188 +msgid "If your private key is secured with a secret, you can provide it here." msgstr "" -#: ../system/data-privacy.rst:137 -msgid "I deleted an user and can still see a message they sent!" +#: ../settings/security/third-party/saml.rst:192 +msgid "Your callback URL" msgstr "" -#: ../system/data-privacy.rst:133 +#: ../settings/security/third-party/saml.rst:191 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." +"This URL is needed for your IdP configuration so it knows where to redirect " +"to after successful authentication." msgstr "" -#: ../system/data-privacy.rst:141 -msgid "I removed a customer, now my reporting is off!" +#: ../settings/security/third-party/saml.rst:194 +msgid "" +"After saving your input by clicking on the \"Submit\" button, Zammad " +"verifies the provided keys/certificates (e.g. if they are valid for signing/" +"encrypting and if they aren't expired)." msgstr "" -#: ../system/data-privacy.rst:140 +#: ../settings/security/third-party/saml.rst:199 msgid "" -"When removing users and their tickets, all references are removed. This also " -"affects e.g. Reporting - these information are lost." +"See :ref:`automatic account linking ` for details " +"on how to link existing Zammad accounts to IdP accounts." msgstr "" -#: ../system/data-privacy.rst:145 -msgid "How long does Zammad store created tasks?" +#: ../settings/security/third-party/saml.rst:205 +msgid "Automatic account linking doesn't work" msgstr "" -#: ../system/data-privacy.rst:144 +#: ../settings/security/third-party/saml.rst:206 msgid "" -"Please see the on-premise data section of the :docs:`data privacy ` chapter." -msgstr "" - -#: ../system/data-privacy.rst:150 -msgid "What about re-assigned tickets? I want to delete them, too." +"Have you double-checked your IdP's user attribute mapping configuration?" msgstr "" -#: ../system/data-privacy.rst:148 +#: ../settings/security/third-party/twitter.rst:4 +#, fuzzy 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." +"It is possible to create a quick login for your helpdesk via Twitter. To do " +"so, you need to follow these steps:" msgstr "" +"É possível inserir seu robô do Telegram no Zammad. Para fazer isso, você " +"precisa seguir estes passos." -#: ../system/data-privacy.rst:154 -msgid "Why are there so many deletion task entries, I didn't create them!" -msgstr "" +#: ../settings/security/third-party/twitter.rst:8 +#, fuzzy +msgid "Register Twitter App" +msgstr "Registrar uma aplicação de robô do Telegram" -#: ../system/data-privacy.rst:153 -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." +#: ../settings/security/third-party/twitter.rst:10 +msgid "Go to https://dev.twitter.com/apps and login with your account." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:2 -msgid "Admin Panel Reference" +#: ../settings/security/third-party/twitter.rst:15 +msgid "Click on \"Create App\"" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:None -msgid "Screenshot of Checkmk settings overview" +#: ../settings/security/third-party/twitter.rst:None +msgid "new app page" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:12 +#: ../settings/security/third-party/twitter.rst:20 msgid "" -"Which :doc:`group ` should Checkmk tickets be assigned " -"to as a default (*i.e.,* when none is specified)?" +"Enter app settings. As \"Callback URL\" you need to enter ``https://" +"zammad_host/api/v1/external_credentials/twitter/callback``. You need to " +"replace ``zammad_host`` with the domain of your Zammad system." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:15 -msgid "(Applies to :ref:`API alerts ` only.)" +#: ../settings/security/third-party/twitter.rst:24 +msgid "" +"After the app has been created, update the application icon and organization " +"attributes." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:21 -msgid "Auto close" +#: ../settings/security/third-party/twitter.rst:None +msgid "set permissions to receive and send direct messages" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:18 +#: ../settings/security/third-party/twitter.rst:30 msgid "" -"Should Zammad automatically close tickets if a service has recovered on its " -"own?" +"Next we need to set ``read, write and access direct messages`` permissions " +"for the app." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:21 -msgid "(Agents will receive notifications for such closures as appropriate.)" +#: ../settings/security/third-party/twitter.rst:None +msgid "click on Keys & Access Token, note them" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:30 -msgid "Auto-close state" +#: ../settings/security/third-party/twitter.rst:36 +msgid "" +"Go to \"Keys and Access Token\" tab and note the \"Consumer Key\" and " +"\"Consumer Secret\"." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:24 -msgid "What ticket state should be applied when “auto-closing” a ticket?" -msgstr "" +#: ../settings/security/third-party/twitter.rst:40 +#, fuzzy +msgid "Configure Zammad as Twitter App" +msgstr "Configure o Zammad como um robô do Telegram" -#: ../system/integrations/checkmk/admin-panel-reference.rst:26 +#: ../settings/security/third-party/twitter.rst:42 msgid "" -"You can choose from the seven built-in ticket states. If these states aren't " -"enough for you, you can :ref:`define a new ticket state ` for this purpose as well. This can be useful for tracking " -"tickets with :doc:`reports `, for example." -msgstr "" - -#: ../system/integrations/checkmk/admin-panel-reference.rst:35 -#: ../system/integrations/cti/includes/recent-logs.include.rst:2 -#: ../system/integrations/ldap/index.rst:74 -#: ../system/integrations/pgp/index.rst:106 -msgid "Recent Logs" +"Go to \"Admin > Security > Twitter > Third Party Applications > Twitter\" " +"Section." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:None -msgid "Screenshot of Checkmk \"Recent Logs\" section" +#: ../settings/security/third-party/twitter.rst:None +msgid "Admin > Security > Third Party Applications" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:41 +#: ../settings/security/third-party/twitter.rst:48 msgid "" -"If you're having trouble getting Zammad and Checkmk to play nicely together, " -"this section can help you troubleshoot." +"Fill in the \"Twitter Key\" and the \"Twitter Secret\" and click the " +"\"Submit\" button." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:44 +#: ../settings/security/third-party/twitter.rst:51 msgid "" -"It contains a record of the fifty most recent transactions that Zammad knows " -"about, including each one's request/response details and return status." +"Now you can link accounts via \"Avatar > Profile > Link Accounts\" or login " +"via Zammad login page." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:2 -msgid "API Reference" +#: ../settings/security/two-factor.rst:11 +msgid "Two-factor Authentication Methods" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:4 -msgid "" -"For most users, :ref:`the sample scripts from the Setup Guide ` will do the job just fine. But if you want more fine-grained control" -"—for instance, to create high- and low-priority tickets for different types " -"of system events—then you'll have to customize the data those scripts send " -"to Zammad." +#: ../settings/security/two-factor.rst:2 +msgid "Two-Factor Authentication" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:15 +#: ../settings/security/two-factor.rst:4 msgid "" -"This custom script will automatically set all tickets it creates to **high " -"priority** and **assign them to charlie@chrispresso.com**." +"Two-factor authentication (2FA) enhances the security of Zammad accounts by " +"adding an extra layer of verification beyond a password. It requires users " +"to provide two different types of authentication factors, typically " +"something they know (like a password) and something they possess (like a " +"mobile device or a security token), to ensure that only authorized " +"individuals can access the account." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:32 -#, fuzzy -msgid "How Does it Work?" -msgstr "Funciona desta forma:" +#: ../settings/security/two-factor.rst:19 +msgid "Enable Recovery Codes" +msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:34 +#: ../settings/security/two-factor.rst:21 msgid "" -"There are two kinds of data you can pass to the API, both in the form of key-" -"value pairs:" +"Recovery codes are one-time use security codes that can be used by the user " +"if they lose access to their other two-factor authentication methods. They " +"cannot be used on their own, they can only be activated if at least one two-" +"factor authentication method is enabled." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:44 -msgid "Checkmk parameters" +#: ../settings/security/two-factor.rst:None +msgid "Enable Recovery Codes Setting" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:38 +#: ../settings/security/two-factor.rst:30 msgid "" -"are required, and make up the **contents** of the resulting tickets/" -"articles. They also determine whether an event creates a new ticket or " -"updates/closes an existing one." +"Recovery codes can only be used as a backup method. If enabled, they will be " +"automatically generated for the user once they set up their initial two-" +"factor authentication method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:42 +#: ../settings/security/two-factor.rst:34 msgid "" -"These are the only values used in the sample scripts. **Use them as-is**; " -"technically, they can be customized, but it's hard to imagine a good reason " -"for it." +"The user will be asked to print out or save the generated recovery codes in " +"a safe place. Once used, a recovery code cannot be reused." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:52 -msgid "Ticket attributes" -msgstr "Atributos do ticket" - -#: ../system/integrations/checkmk/api-reference.rst:47 +#: ../settings/security/two-factor.rst:37 msgid "" -"are optional, and can be used to **adjust settings** on newly created " -"tickets (*e.g.,* set the owner, group, priority, or state)." +"Users will also have an option to regenerate their recovery codes at any " +"time, which invalidates already existing recovery codes and provides them " +"with a list of fresh codes." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:50 +#: ../settings/security/two-factor.rst:41 msgid "" -"If you want to customize your Checkmk alert script, do it with these. Simply " -"add an extra “form” option for each one (``-F \"key=value\"``) to your " -"script's ``curl`` command line, as in the example above." +"After you enable this setting, when the user completes a setup of their " +"initial two-factor authentication method, they will be presented with a list " +"of recovery codes and instructed to save them for later use." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:54 -msgid "💡 **It's just an API endpoint!**" +#: ../settings/security/two-factor.rst:None +msgid "Recovery Codes Generation Modal Dialog" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:56 -msgid "" -"When using Checkmk integration, messages need to be formatted in a certain " -"way, but that *doesn't mean the messages actually have to come from Checkmk*." +#: ../settings/security/two-factor.rst:50 +msgid "Enforce the Set Up of the Two-Factor Authentication" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:59 +#: ../settings/security/two-factor.rst:52 msgid "" -"If you use another monitoring tool that's not officially supported by " -"Zammad, there's probably a way to make it work with your Checkmk callback " -"URL." +"In case you wish to require your users to set up at least one two-factor " +"authentication method for their account, you can do this by selecting " +"specific user roles the requirement applies to in **Enforced for user " +"roles** setting. Of course you must have at least one two-factor " +"authentication method enabled for this setting to take effect." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:63 -msgid "Checkmk Parameters" +#: ../settings/security/two-factor.rst:None +msgid "Enforced for User Roles Setting" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:65 +#: ../settings/security/two-factor.rst:62 msgid "" -"When a notification is received, Zammad creates a new article containing the " -"details of the event that triggered it:" +"After you change this setting, if the user has one of the selected roles on " +"their account, they will be forced to set up the two-factor authentication " +"upon next sign in or application reload." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:None -msgid "Checkmk article body" +#: ../settings/security/two-factor.rst:66 +msgid "" +"A modal dialog with instructions will be shown, and they will not be able to " +"do any work before they set up at least one two-factor method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:72 -msgid "" -"These details come from the fields listed below, which correspond to " -"parameters provided by Checkmk (``$NOTIFY_*``)." +#: ../settings/security/two-factor.rst:None +msgid "Modal Dialog for Enforcing Two-Factor Authentication Set Up" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:75 -msgid "**Required fields are marked with an asterisk (\\*).**" +#: ../settings/security/two-factor.rst:74 +msgid "Reset Two-Factor Authentication for a Specific User" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:79 -msgid "event_id\\*" +#: ../settings/security/two-factor.rst:76 +msgid "" +"In case an user isn't able to login anymore because of an inaccessible " +"second factor, you can reset the user's 2FA method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:78 +#: ../settings/security/two-factor.rst:79 msgid "" -"A unique ID for the system event. (``$NOTIFY_SERVICEPROBLEMID`` / " -"``$NOTIFY_HOSTPROBLEMID``)" +"To do this, go to the user management and search for the relevant user. " +"After you found the account, click the button in the action column and " +"select \"Manage Two-Factor Authentication\":" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:86 -msgid "host\\*" +#: ../settings/security/two-factor.rst:None +msgid "Context menu in action column in user management" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:82 +#: ../settings/security/two-factor.rst:87 msgid "" -"The hostname of the system that the event originated from. " -"(``$NOTIFY_HOSTNAME``)" +"After selecting this, you can see a dialog where you can either reset one " +"2FA method or reset all of the user's 2FA methods:" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:85 -msgid "" -"Used to determine if a new event belongs to an existing ticket. Also used in " -"the subject line of the resulting article (“ is ”)." +#: ../settings/security/two-factor.rst:None +msgid "Dialog for resetting user's 2FA method" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:96 -msgid "service" +#: ../settings/security/two-factor.rst:94 +msgid "" +"Choose the fitting one, click on the corresponding \"Remove ...\" button and " +"confirm your action. The user now has to setup a new 2FA method, depending " +"on your 2FA configuration." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:89 -msgid "" -"The name of the service that the event originated from. " -"(``$NOTIFY_SERVICEDESC``)" +#: ../settings/security/two-factor/authenticator-app.rst:2 +msgid "Authenticator App" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:92 -msgid "Used to determine if a new event belongs to an existing ticket." +#: ../settings/security/two-factor/authenticator-app.rst:4 +msgid "" +"The authenticator app method is a type of two-factor authentication that " +"uses a mobile application to generate one-time codes for account " +"verification. After setting up the authenticator app on their device, the " +"user links it to their Zammad account." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:94 -#: ../system/integrations/checkmk/api-reference.rst:110 -msgid "Displayed as ``-`` when omitted." +#: ../settings/security/two-factor/authenticator-app.rst:12 +msgid "" +"When logging in, the user is prompted to enter a time-sensitive code " +"generated by the app, in addition to their password. This code acts as the " +"second factor of authentication, providing an extra layer of security as it " +"changes periodically and is unique to the user's device." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:104 -msgid "state\\*" +#: ../settings/security/two-factor/authenticator-app.rst:None +msgid "Security Code in Google Authenticator App" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:99 +#: ../settings/security/two-factor/authenticator-app.rst:22 msgid "" -"The current state of the service or host in question. " -"(``$NOTIFY_SERVICESTATE`` / ``$NOTIFY_HOSTSTATE``)" +"The app generates codes based on a shared secret key stored securely on both " +"the user's device and the server, ensuring a synchronized and secure " +"authentication process. The method of generating the codes is sometimes also " +"called TOTP (time-based one-time password)." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:102 -msgid "" -"Used to detect when a ticket should be auto-closed (*i.e.,* on ``OK``/" -"``UP``). Also used in the subject line of the resulting article (“ is " -"”)." +#: ../settings/security/two-factor/authenticator-app.rst:28 +msgid "Enabling the Authenticator App Method" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:110 -msgid "text" +#: ../settings/security/two-factor/authenticator-app.rst:30 +#: ../settings/security/two-factor/security-keys.rst:28 +msgid "To enable the method, just toggle the switch on in the settings." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:107 -msgid "" -"The output of the process that triggered the event. " -"(``$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" +#: ../settings/security/two-factor/authenticator-app.rst:None +msgid "Authenticator App Switch in Settings" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:121 +#: ../settings/security/two-factor/authenticator-app.rst:36 msgid "" -"The Object Manager attribute panel displays built-in and custom\n" -"attribute names." +"Now the users will be able to set up this two-factor authentication method " +"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " +"Once they do, on next sign-in with password, they will be asked to provide " +"an additional security code generated by their mobile device." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:121 -msgid "Find a complete list of ticket attributes in the Object Manager." +#: ../settings/security/two-factor/security-keys.rst:2 +msgid "Security Keys" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:123 +#: ../settings/security/two-factor/security-keys.rst:4 msgid "" -"Ticket attributes are entirely optional, and can be used to customize the " -"tickets that Checkmk creates. (Note that these attributes will be ignored if " -"a new event belongs to an existing ticket.)" +"The security keys method is a type of a two-factor authentication that uses " +"Web Authentication API in the browser for verifying user's identity. The " +"user can register multiple hardware or software security keys with their " +"Zammad account and then they can use it during the sign-in process." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:128 +#: ../settings/security/two-factor/security-keys.rst:12 msgid "" -"Why would you want to do this? Maybe you have only one IT guy, and all " -"system monitoring issues should be automatically assigned to him. Or, maybe " -"you're creating multiple notification rules so that database outages take " -"higher priority than disk space warnings." +"When logging in, the user is prompted to provide the same security key they " +"registered with their account, in addition to their password. This key acts " +"as the second factor of authentication, providing an extra layer of security." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:135 -msgid "In most cases, you'll probably want to set one of the following:" +#: ../settings/security/two-factor/security-keys.rst:None +msgid "Security Key dialog in Safari on macOS" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:137 -msgid "group" +#: ../settings/security/two-factor/security-keys.rst:21 +msgid "" +"The type of the key can range from hardware USB sticks to passkeys stored in " +"a device of user's choice. Which type can be used depends on the browser " +"flavor and the platform of the user." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:139 -msgid "state" -msgstr "estado" +#: ../settings/security/two-factor/security-keys.rst:26 +msgid "Enabling the Security Keys Method" +msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:140 -msgid "priority" +#: ../settings/security/two-factor/security-keys.rst:None +msgid "Security Keys Switch in Settings" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:142 +#: ../settings/security/two-factor/security-keys.rst:34 msgid "" -"but in practice, you can set almost any attribute, including :doc:`custom " -"ones you created through the Object Manager `." +"Now the users will be able to set up this two-factor authentication method " +"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " +"Once they do, on next sign-in with password, they will be asked to provide " +"the same security key they registered during the setup." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:145 -#, fuzzy -msgid "Please note that the following attributes are **not customizable**:" -msgstr "Lá você poderá editar as seguintes configurações:" +#: ../settings/system/system-selfhosted.include.rst:3 +msgid "" +"Below settings are only available to self hosted users. In hosted " +"environments we're handling these settings for you to ensure service " +"stability." +msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:147 -msgid "title" -msgstr "título" +#: ../settings/system/base.rst:11 +msgid "Fully Qualified Domain Name" +msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:148 -msgid "id" +#: ../settings/system/base.rst:7 +msgid "The URL of your Zammad installation." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:149 -msgid "ticket number" +#: ../settings/system/base.rst:9 ../settings/system/base.rst:17 +msgid "This setting is used within :doc:`/misc/variables` and notifications." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:151 -msgid "created_by_id" +#: ../settings/system/system-base.include.rst:1 +msgid "It is automatically set by the *Getting Started wizard*." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:152 -msgid "updated_by_id" +#: ../settings/system/system-base.include.rst:5 +msgid "Changing this setting also changes callback URLs for your channels etc." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:155 -msgid "Which Values Can Be Set?" +#: ../settings/system/system-base.include.rst:6 +msgid "This setting can have negative affects on being able to login." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:157 -msgid "😵 **Invalid values → unpredictable behavior**" +#: ../settings/system/base.rst:19 +msgid "HTTP type" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:159 +#: ../settings/system/base.rst:14 msgid "" -"If you provide a value that Zammad doesn't understand (*e.g.,* ``-F " -"\"priority=high\"``), it's not always clear what will happen. In some cases, " -"a ticket will be created with the default values instead - but in others, it " -"may not be created at all!" +"The HTTP type tells your installation how your clients connect. This is " +"relevant for authentication and cookie security." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:164 -msgid "So what values does Zammad understand, then? Well, it depends..." +#: ../settings/system/base.rst:31 +msgid "SystemID" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:168 -msgid "Use an email address or username:" +#: ../settings/system/base.rst:22 +msgid "" +"This ID is being used within your ticket number. In case you're " +"communicating with another ticket system with similar ticket number schemes " +"this ID greatly reduces the risk of false follow ups." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:190 -msgid "group & priority" +#: ../settings/system/base.rst:26 +msgid "" +"The SystemID is randomly selected upon installation of Zammad (``1-99``)." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:175 -msgid "Refer to the dropdown menus in the ticket pane:" +#: ../settings/system/base.rst:30 +msgid "" +"**Do not** change this setting in a productive system! Your Zammad " +"installation may no longer recognize old ticket number based follow ups upon " +"change!" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:0 -msgid "See possible values for certain attributes in the ticket pane." +#: ../settings/system/frontend.rst:2 +msgid "Frontend" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:187 -msgid "🙅 **Ticket state CANNOT be set this way!**" -msgstr "" +#: ../settings/system/frontend.rst:22 +#, fuzzy +msgid "Core Workflow Ajax Mode" +msgstr "Fluxos de Trabalho" -#: ../system/integrations/checkmk/api-reference.rst:189 +#: ../settings/system/frontend.rst:6 msgid "" -"Why? Because ``-F \"state=...\"`` is already used :ref:`as a Checkmk " -"parameter `." +"This setting allows administrators to enforce :doc:`/system/core-workflows` " +"to use Ajax-Calls instead of web sockets. You'll usually only need this if " +"you experience serious issues as noted below." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:222 -msgid "Everything Else" +#: ../settings/system/frontend.rst:10 +msgid "**🤓 Possible (technical) reasons**" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:193 +#: ../settings/system/frontend.rst:12 msgid "" -"To set any other attributes, it helps to know your way around the :docs:" -"`rails console `. Valid values are those that you can " -"set with a string:" +"In some cases, your network structure (e.g. firewalls, proxies) may " +"disconnect long web socket connections. This leads to select fields staying " +"empty (e.g. owner selection *after* selecting your group) or fields not " +"shown / hidden (e.g. when switching to or from pending states, the \"pending " +"till\" field not showing / hiding)." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:218 -msgid "These values can then be passed directly to the API:" +#: ../settings/system/frontend.rst:18 +msgid "" +"Please keep in mind that the Ajax fallback may cause serious pressure on " +"your application server. If you have the choice stick to web sockets." msgstr "" -#: ../system/integrations/checkmk/index.rst:16 -msgid "How does it work?" +#: ../settings/system/frontend.rst:22 +msgid "Default: ``no`` (inactive)" msgstr "" -#: ../system/integrations/checkmk/index.rst:2 -msgid "Checkmk" +#: ../settings/system/frontend.rst:53 +msgid "Show calendar weeks in the picker of date/datetime fields" msgstr "" -#: ../system/integrations/checkmk/index.rst:4 +#: ../settings/system/frontend.rst:25 msgid "" -"`Checkmk `_ is a powerful IT monitoring tool that can " -"send real-time status alerts to Zammad via email or REST API. Set these " -"alerts up in Checkmk, and Zammad will automatically create, update, and " -"close tickets based on the health of your system:" +"With this setting you can instruct Zammad to provide week number display " +"globally for all users. Calendar with week number display are usually used " +"in business sectors and may not be relevant for everyone." msgstr "" -#: ../system/integrations/checkmk/index.rst:14 -msgid "Screenshot of ticket created by Checkmk notifications" +#: ../settings/system/frontend.rst:29 +msgid "" +"This setting affects *all areas* - you'll also see week numbers in the admin " +"panel for e.g. triggers and macros." msgstr "" -#: ../system/integrations/checkmk/index.rst:14 -msgid "Multiple alerts, same ticket." +#: ../settings/system/frontend.rst:32 +msgid "Default: ``no`` (not shown)" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:2 -msgid "Setup Guide" +#: ../settings/system/frontend.rst:53 +msgid "Here's the difference:" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:4 -msgid "" -"Whenever the Checkmk integration is enabled, Zammad listens for messages on " -"its API and over email. As long as those messages follow the required " -"format, Zammad will create new tickets (or find and update existing ones) " -"based on the message contents." +#: ../settings/system/frontend.rst:0 +msgid "Screenshot showing Zammad's date picker (in the default way)" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:10 -msgid "" -"That means that “setting up Checkmk integration” is simply a matter of " -"**adding configuration to your Checkmk site**: telling it when to send these " -"messages and what to say. To do that, you'll need to create a new " -"**notification rule** (see `Checkmk's official docs `_ for help with that)." +#: ../settings/system/frontend.rst:41 +msgid "Set to ``no``" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:17 +#: ../settings/system/frontend.rst:0 msgid "" -"As part of this new rule, you'll have to choose a **notification method** " -"(*i.e.,* a script to execute whenever the rule is triggered). This script " -"will be written by you (samples below), and contain the logic for sending " -"API/email messages to Zammad:" +"Screenshot showing Zammad's date picker with\n" +"week numbers enabled" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:26 -msgid "Checkmk \"New Rule\" dialog" +#: ../settings/system/frontend.rst:50 +msgid "Set to ``yes``" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:26 +#: ../settings/system/index.rst:4 msgid "" -"Find your custom scripts in the Checkmk WATO under **Notifications > New " -"Rule > Notification Method**." +"For your overview we split each tab within system settings into its own page:" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:29 -msgid "" -"Once you're done setting up your new rule, you're all set! New tickets " -"should start coming in and auto-updating any time your rule is triggered." -msgstr "" +#: ../settings/system/index.rst:16 +#, fuzzy +msgid "Console Based Settings" +msgstr "Configurações" -#: ../system/integrations/checkmk/setup-guide.rst:33 +#: ../settings/system/index.rst:18 msgid "" -"(If you need help troubleshooting, be sure to check the :ref:`checkmk-recent-" -"logs`.)" +"There's some console based settings we didn't put into the UI. However, you " +"may find them helpful - you can find them in our :docs:`hidden settings ` section." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:38 -msgid "API Alerts" +#: ../settings/system/network.rst:2 +msgid "Network" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:40 +#: ../settings/system/network.rst:8 msgid "" -"To add these scripts in the Checkmk WATO, copy them into your Checkmk " -"installation directory and make them executable. (Be sure to replace the " -"``zammad.example.com`` callback URL with the one found in your admin panel.)" +"The proxy settings can only be saved after successfully testing the proxy " +"connection." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:60 -msgid "Service notification" +#: ../settings/system/network.rst:15 +msgid "Proxy Address." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:46 +#: ../settings/system/network.rst:12 msgid "" -"For updates on the status of the software running on your server (*e.g.,* " -"postgres)." +"Allows you to provide a proxy server if needed. This is relevant for network " +"communication by Zammad." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:75 -msgid "Host notification" +#: ../settings/system/network.rst:15 +msgid "It **does not** affect the update process or Elasticsearch." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:63 -msgid "For updates on the status of the server itself." +#: ../settings/system/network.rst:18 +msgid "Username for proxy connection." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:77 -msgid "🤔 **What's with all the env vars?**" +#: ../settings/system/network.rst:18 +msgid "" +"If your proxy server requires authentication, provide the username here." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:79 -msgid "" -"Whenever Checkmk runs these scripts, it needs to provide some information " -"about the event that triggered the notification. This information is passed " -"in the form of these ``$NOTIFY_*`` environment variables." +#: ../settings/system/network.rst:21 +msgid "Password for proxy connection." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:85 +#: ../settings/system/network.rst:21 msgid "" -"You can specify additional parameters to pass to the script when you're " -"setting up your notification rule, but the ones you see here are all " -"provided by default." +"If your proxy server requires authentication, provide the password here." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:90 -msgid "Email Alerts" +#: ../settings/system/network.rst:26 +msgid "No proxy for the following hosts." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:94 +#: ../settings/system/network.rst:24 msgid "" -"🐞 **There are known bugs** in Zammad's processing of email from Checkmk. " -"This section will be completed once they have been resolved. (Learn more at " -"GitHub issues `#2377 `_ & " -"`#2180 `_.)" +"Exception list for hosts you can't or don't want to reach via proxy server." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:100 -msgid "In the meantime, we encourage you to set up API alerts instead." +#: ../settings/system/network.rst:27 +msgid "Default: ``localhost,127.0.0.0,::1``" msgstr "" -#: ../system/integrations/clearbit.rst:2 -msgid "Clearbit" +#: ../settings/system/services.rst:2 +msgid "Services" msgstr "" -#: ../system/integrations/clearbit.rst:4 -msgid "" -"With our Clearbit integration, you can easily enrich the information " -"provided by Zammad. If the customers or agents email address is known to " -"Clearbit, it will share all information it has regarding the user with " -"Zammad. Those information can include the following:" +#: ../settings/system/services.rst:10 +msgid "Image Service" msgstr "" -#: ../system/integrations/clearbit.rst:9 -msgid "Avatar" -msgstr "Avatar" - -#: ../system/integrations/clearbit.rst:10 -msgid "Address information" +#: ../settings/system/services.rst:5 +msgid "Defines the backend for user and organization image lookups." msgstr "" -#: ../system/integrations/clearbit.rst:11 -msgid "Website information" +#: ../settings/system/services.rst:7 +msgid "Default: ``Zammad Image Service`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:12 -msgid "A BIO (as Note by default)" +#: ../settings/system/services.rst:9 +msgid "" +"Make sure your on premise installation has ``HTTPS`` access to ``images." +"zammad.com``." msgstr "" -#: ../system/integrations/clearbit.rst:14 -msgid "" -"If needed, you can add further custom objects and add mappings to them, so " -"the Clearbit information can be filled within the database. In general you " -"can get any information from Clearbit, as long as you have a mapping to an " -"Zammad object." +#: ../settings/system/services.rst:18 +msgid "Geo Calendar Service" msgstr "" -#: ../system/integrations/clearbit.rst:21 +#: ../settings/system/services.rst:13 msgid "" -"Clearbit does have a mapping of fields like LDAP and Exchange have, but does " -"not \"win\" against Zammad information. This means that if you have e.g. the " -"last name field filled in already and Clearbit has other information on " -"that, it will not be updated." +"Defines the backend for geo calendar lookups. Used for initial calendar " +"setup." msgstr "" -#: ../system/integrations/clearbit.rst:26 -msgid "" -"However: If let's say the last name has been set by Clearbit and Zammad " -"notices that the last name on the Clearbit source has changed, Zammad will " -"also update this value." +#: ../settings/system/services.rst:16 +msgid "Default: ``Zammad GeoCalendar Service`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:33 +#: ../settings/system/services.include.rst:2 msgid "" -"The configuration of Clearbit is really easy and done fast! Just login to " -"your Clearbit-Account, go to \"API\" and copy the secret-API-Key." +"Make sure your on premise installation has ``HTTPS`` access to ``geo.zammad." +"com``." msgstr "" -#: ../system/integrations/clearbit.rst:38 -msgid "" -"Now change to your Zammad instance, go to Integrations (System) -> Clearbit " -"in the admin panel. Paste your API-Key into the API-Key-Field and decide if " -"Zammad should create unknown Organizations automatically, if the user does " -"not have one yet (and Clearbit knows it). The shared option decides if the " -"new organizations Zammad creates with Clearbit should be shared ones." +#: ../settings/system/services.rst:26 +msgid "Geo IP Service" msgstr "" -#: ../system/integrations/clearbit.rst:47 +#: ../settings/system/services.rst:21 msgid "" -"If you're unsure what option to choose, better stick with \"no\". You can " -"also learn more about :doc:`/manage/organizations/index`." +"Defines the backend for geo IP lookups. Shows also location of an IP address " +"if an IP address is shown." msgstr "" -#: ../system/integrations/clearbit.rst:52 -msgid "" -"The Mapping option works similar to the mapping within the Exchange and LDAP " -"sync. You can add further mappings for e.g. custom fields if you need more " -"information that Clearbit can provide." +#: ../settings/system/services.rst:24 +msgid "Default: ``Zammad GeoIP Service`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:58 -msgid "" -"If you want to add more Clearbit fields and want to learn more about " -"available fields on their API, you can take a look at their `API " -"documentation `_." +#: ../settings/system/services.rst:32 +msgid "Geo Location Service" msgstr "" -#: ../system/integrations/clearbit.rst:62 +#: ../settings/system/services.rst:29 msgid "" -"If you're happy with the above chosen Settings and your mapping, just save " -"the changes and enable Clearbit integration. Zammad will now start polling " -"the Clearbit API as users contact you." +"Defines the backend for geo location lookups to store geo locations for " +"addresses." msgstr "" -#: ../system/integrations/clearbit.rst:68 +#: ../settings/system/services.rst:32 msgid "" -"Zammad does not synchronize with Clearbit on a regular basis, but on demand " -"if needed. This saves API calls." +"Default: ``OpenStreetMap (ODbL 1.0, http://osm.org/copyright)`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:73 +#: ../settings/system/services.rst:36 msgid "" -"Below the Settings and Mappings, you'll find our Integration log. You can " -"see what requests Zammad sent to Clearbit and also the APIs Response." +"You can find a detailed privacy information on what we store for how long on " +"our :docs:`Privacy Appendix ` inside of our System " +"Documentation." msgstr "" -#: ../system/integrations/clearbit.rst:78 -msgid "" -"By the way, you can also view the API log on the Clearbit website - the " -"information seen is basically the same." +#: ../settings/system/storage.rst:2 +msgid "Storage" msgstr "" -#: ../system/integrations/clearbit.rst:84 -msgid "Example When Adding a User" +#: ../settings/system/storage.rst:6 +msgid "" +"Here you can define where Zammad stores attachments for tickets and the " +"knowledge base. By default, we're writing to the ``Database`` - you can " +"switch to ``Filesystem`` or ``Simple Storage (S3)`` at any time. In this " +"case please have a look on the following instructions." msgstr "" -#: ../system/integrations/clearbit.rst:86 +#: ../settings/system/storage.rst:11 msgid "" -"To show you how fast information is added, we added a small Screencast " -"below. This shows the creation of the User Alex from Clearbit. As we already " -"set the last name of Alex to \"X\", Zammad did not update it. What Zammad " -"did was to add further information it received from Clearbit." +"If you have a busy Zammad instance, we strongly encourage you to use " +"filesystem storage instead of \"Database\". This will greatly improve system " +"performance (de-crease database load and size)." msgstr "" -#: ../system/integrations/cti/generic.rst:2 -msgid "CTI (generic)" +#: ../settings/system/storage.rst:19 +msgid "Database" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:1 +#: ../settings/system/storage.rst:17 msgid "" -"This integration enables Zammad to provide a caller log to your agents. With " -"this your agents can greet your customers by their name and are supported by " -"Zammad with automatically opening a new ticket dialog or the user profile." +"This is the default storage method. The attachments are stored directly in " +"the database. If your Zammad instance grows, we recommend one of the other " +"methods to maintain performance." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:6 +#: ../settings/system/storage.rst:38 +#, fuzzy +msgid "Filesystem" +msgstr "Sistema" + +#: ../settings/system/storage.rst:22 msgid "" -"Click the toggle next to the heading to activate or deactivate this " -"integration." +"This storage method is recommended for all Zammad instances, especially for " +"those with a higher load. If you choose filesystem, your files are written " +"to ``/opt/zammad/storage/``." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:9 +#: ../settings/system/storage.rst:26 msgid "" -"If you want to learn more on how your agents can use this function, please " -"refer the :user-docs:`user documentation `." +"Moving attachments from \"Database\" to \"Filesystem\" can be run during " +"production use. However, you should consider your framework conditions (e.g. " +"bandwidth, system load in production) to define the right moment." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:14 +#: ../settings/system/storage.rst:32 +msgid "**You noticed slow updates of Zammad?**" +msgstr "" + +#: ../settings/system/storage.rst:34 msgid "" -"Automatically opening new ticket dialogues or user profiles requires agent " -"to extension mapping - see more below." +"While Zammad is beeing updated, it enforces a recursive \"change " +"owner\" (chown) for this directory. For instances with many files this can " +"be time consuming. To mitigate that you can move your files and create a " +"symlink in ``/opt/zammad/storage/`` to the new directory. Of course you have " +"to make sure on your own that the permissions are always correct." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:20 -msgid "Please note the following limitations to reduce confusion later on:" +#: ../settings/system/storage.rst:95 +msgid "Simple Storage (S3)" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:22 -msgid "CTI integrations provide caller log functions only." +#: ../settings/system/storage.rst:41 +msgid "" +"To use the Simple Storage (S3), you have to provide some settings, which " +"can't be accessed in the UI (see instructions below)." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:23 +#: ../settings/system/storage.rst:44 msgid "" -"This integration does not provide any VoIP functionalities; you can't make " -"phone calls from within Zammad." +"⚠️ Please note that the current implementation is in its early stages and can " +"be modified in the future." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:25 +#: ../settings/system/storage.rst:47 msgid "" -"If your browser supports ``tel``-URLs, you can click on phone numbers for " -"automatic dialing. This requires additional software / configuration on your " -"agent's computers." +"The prerequisite is to have access to a S3-compatible storage and to have " +"all necessary parameters available (which depends on your storage provider; " +"if in doubt, please ask there for help)." msgstr "" -#: ../system/integrations/cti/generic.rst:9 -#: ../system/integrations/cti/placetel.rst:14 -#: ../system/integrations/cti/sipgate.rst:14 -msgid "Please provide the following requirements:" +#: ../settings/system/storage.rst:51 +msgid "Steps to configure S3:" msgstr "" -#: ../system/integrations/cti/generic.rst:11 +#: ../settings/system/storage.rst:53 msgid "" -"A telephone system that supports webhooks (outbound) (best option are those " -"that allow customizing the calls)." +"Copy ``config/zammad/storage.yml.dist`` to ``config/zammad/storage.yml``" msgstr "" -#: ../system/integrations/cti/generic.rst:13 -msgid "A unique Call-ID during the call session." +#: ../settings/system/storage.rst:54 +msgid "Edit the copied file in one of the following ways:" msgstr "" -#: ../system/integrations/cti/generic.rst:14 -msgid "Call event data (both numbers and direction)." +#: ../settings/system/storage.rst:56 +msgid "" +"Either provide your S3 configuration with one attribute per line like in the " +"upper area of the file" msgstr "" -#: ../system/integrations/cti/generic.rst:15 -msgid "Your Zammad instance must be reachable for your telephony system." +#: ../settings/system/storage.rst:58 +msgid "" +"Or provide your S3 configuration as an URL (which you can find at the end of " +"the file). Note: you can also provide this URL as environment variable (:" +"docs:`see system documentation `) without using this yml-file." msgstr "" -#: ../system/integrations/cti/generic.rst:17 +#: ../settings/system/storage.rst:62 msgid "" -"If you want to learn more on what kind of requests are supported by Zammad " -"and what it expects, please consult our :docs:`CTI-API documentation `." +"We recommend the deletion of the not used configuration style to avoid " +"inconsistencies." msgstr "" -#: ../system/integrations/cti/generic.rst:22 -#: ../system/integrations/cti/placetel.rst:27 -#: ../system/integrations/cti/sipgate.rst:30 -#, fuzzy -msgid "Available Settings" -msgstr "Configurações" - -#: ../system/integrations/cti/generic.rst:29 -#: ../system/integrations/cti/placetel.rst:41 -#: ../system/integrations/cti/sipgate.rst:40 -#, fuzzy -msgid "Endpoint Settings" -msgstr "Configurações" +#: ../settings/system/storage.rst:65 +msgid "Restart Zammad so the config file / environment variable is loaded" +msgstr "" -#: ../system/integrations/cti/generic.rst:25 +#: ../settings/system/storage.rst:66 msgid "" -"Zammad will list your generic CTI endpoint here. It contains a unique token " -"so ensure to keep this URL save." +"Set the \"Storage Method\" in Zammad to ``Simple Storage (S3)`` in Settings " +"> System > Storage and click on \"Submit\". After that, Zammad checks your " +"configuration and the connection to the service and will raise an error " +"message if something is wrong." msgstr "" -#: ../system/integrations/cti/generic.rst:28 -msgid "" -"You'll need this endpoint for your PBX to talk to Zammad, see :docs:`CTI-API " -"documentation `." +#: ../settings/system/storage.rst:72 +msgid "A very simple storage configuration could look like this:" msgstr "" -#: ../system/integrations/cti/includes/important-dont-forget-saving.include.rst:3 +#: ../settings/system/storage.rst:85 msgid "" -"All following options **do not save automatically**. Always use the Save " -"button on the lower end of the integration page!" +"Before setting the storage method to ``Simple Storage (S3)`` (step 4), " +"please make sure to have a working setup." msgstr "" -#: ../system/integrations/cti/generic.rst:43 -#: ../system/integrations/cti/placetel.rst:49 -#: ../system/integrations/cti/sipgate.rst:52 -#, fuzzy -msgid "Call Settings" -msgstr "Configurações" +#: ../settings/system/storage.rst:88 +msgid "" +"You can verify this by running ``rails r 'Rails.logger = Logger.new(STDOUT); " +"pp Store::Provider::S3.ping?'`` in your Zammad directory. If everything is " +"fine, you should see ``true``, else you should see ``false`` and a simple " +"error message." +msgstr "" -#: ../system/integrations/cti/generic.rst:39 -#: ../system/integrations/cti/placetel.rst:49 -#: ../system/integrations/cti/sipgate.rst:37 -#: ../system/integrations/cti/sipgate.rst:50 -msgid "Inbound" +#: ../settings/system/storage.rst:93 +msgid "" +"If you installed Zammad through a package manager (rather than from source), " +"replace ``rails r`` with ``zammad run rails r`` above. To learn more, see :" +"docs:`Administration via Console `." msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:1 +#: ../settings/ticket.rst:4 msgid "" -"This option allows you to block specific incoming caller IDs. It allows you " -"to temporarily reject e.g. spam callers without having to contact providers " -"or PBX administrators." +"Here you can adjust general ticket settings. Additional ones for the ticket " +"composer interface can be found in the :doc:`/misc/composer`." msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:11 -msgid "Caller ID to block" +#: ../settings/ticket.rst:11 +msgid "Ticket Hook (default: ``Ticket#``)" msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 -msgid "Provide caller IDs to block in ``E.164`` format." +#: ../settings/ticket.rst:11 +msgid "The identifier for a ticket; *e.g.,* Ticket#, Call#, MyTicket#." msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:8 -msgid "" -"Your telephony system has to support this function. Zammad will send a " -"``reject`` response which will cause your telephony system to hang up the " -"call. To callers this usually will feel like the line is busy." +#: ../settings/ticket.rst:38 +msgid "Ticket Hook Position (default: ``right``)" msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:14 +#: ../settings/ticket.rst:14 msgid "" -"Provide a meaningful note for your fellow administrators to remind yourself " -"why you've chosen to block the number." +"With this setting you can decide (if) where to insert the ticket number." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 -#: ../system/integrations/cti/includes/outbound-calls.include.rst:17 -#: ../system/integrations/cti/sipgate.rst:40 -msgid "Outbound" +#: ../settings/ticket.rst:20 +msgid "*Right*" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:1 +#: ../settings/ticket.rst:17 msgid "" -"In many cases you may want to use a different caller ID depending on the " -"destination you're calling. This may apply due to specific connection rates " -"to other countries or because you want your customer to feel you're calling " -"from the same country." +"This setting will add the ticket reference on the right site of the subject." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:6 -msgid "This option expects ``E.164`` number formats." +#: ../settings/ticket.rst:20 +msgid "Example: ``Some Subject [Ticket#12345]``" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 -msgid "Destination caller ID" +#: ../settings/ticket.rst:26 +msgid "*Left*" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:5 -msgid "The caller ID or number you're trying to call." +#: ../settings/ticket.rst:23 +msgid "" +"This setting will add the ticket reference on the left site of the subject." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:7 -msgid "You can use wildcards for e.g. country specific outbound numbers like:" +#: ../settings/ticket.rst:26 +msgid "Example: ``[Ticket#12345] Some Subject``" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:9 -msgid "``49*`` for Germany" +#: ../settings/ticket.rst:29 +msgid "*None*" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:10 -msgid "``4930*`` for Berlin / Germany landlines" +#: ../settings/ticket.rst:29 +msgid "This will completely remove ticket references from the subject." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 -msgid "``33*`` for France" +#: ../settings/ticket.rst:33 +msgid "" +"Please ensure to take a look at :doc:`/channels/email/settings` within the " +"email channel to ensure you have at least one reference that helps Zammad to " +"assign follow-ups correctly." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:15 -msgid "Set Outbound caller ID" +#: ../settings/ticket.rst:37 +msgid "" +"Disabling this and not setting up any further follow up search will lead to " +"unexpected results!" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:14 +#: ../settings/ticket.rst:65 msgid "" -"The outbound caller ID to set (the number your customer sees on his display) " -"in ``E.164`` number format." +"Ticket Last Contact Behaviour (default: ``Use the start time of the last " +"customer thread (which may consist of multiple articles).``)" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 -msgid "Provide a short description for fellow administrators." +#: ../settings/ticket.rst:41 +msgid "" +"This setting changes the way Zammad updates the ``Last Contact`` value of a " +"ticket. This is fairly important for overviews and what you expect upon " +"ticket updates of a customer." msgstr "" -#: ../system/integrations/cti/includes/generic-cti-support-note.includes.rst:3 +#: ../settings/ticket.rst:52 msgid "" -"This option requires your PBX to send a specific request to Zammad *before " -"dialing*. Please consult the :docs:`CTI API ` in case " -"you're not sure." +"Use the start time of the last customer thread (which may consist of " +"multiple articles)." msgstr "" -#: ../system/integrations/cti/generic.rst:52 -#: ../system/integrations/cti/placetel.rst:54 -#: ../system/integrations/cti/sipgate.rst:59 -#, fuzzy -msgid "Other Settings" -msgstr "Configurações" - -#: ../system/integrations/cti/includes/other-settings-intro.include.rst:1 +#: ../settings/ticket.rst:46 msgid "" -"Below you can find all available additional settings for this CTI " -"integration. For your overview we're sorting them by appearance and " -"reference their description first." +"If this option is chosen, Zammad will update the last updated value just " +"once if a customer replies. After that, Zammad will wait for an agent to " +"react." msgstr "" -#: ../system/integrations/cti/includes/default-caller-id.include.rst:2 -#: ../system/integrations/cti/includes/default-caller-id.include.rst:1 -msgid "Default caller ID for outbound calls" +#: ../settings/ticket.rst:50 +msgid "" +"This comes in handy if you want to work tickets in the order of their first " +"update. This will not change ticket orders if customers decide to \"bump\" " +"the ticket affected." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:16 -#: ../system/integrations/cti/includes/records-caller-log.include.rst:15 -msgid "Shown records in caller log" +#: ../settings/ticket.rst:57 +msgid "Use the time of the very last customer article." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:2 +#: ../settings/ticket.rst:55 msgid "" -"Allows you to set the number of shown caller log entries for all users. You " -"can choose from the following values:" +"When setting this option, Zammad will always update the last updated value. " +"This means that if ordering by ``Last Update``, ticket orders will change if " +"customers \"bump\" the ticket." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:5 -msgid "60 (default)" +#: ../settings/ticket.rst:64 +msgid "Last contact value used on :doc:`/manage/overviews`" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:6 -msgid "120" +#: ../settings/ticket.rst:65 +msgid "Last contact value used on :doc:`/manage/trigger`" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:7 -msgid "180" +#: ../settings/ticket.rst:88 +msgid "" +"Ticket Organization Reassignment (default: ``Update the most recent tickets." +"``)" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:8 -msgid "240" +#: ../settings/ticket.rst:68 +msgid "" +"This setting changes the way Zammad updates the organization field of the " +"tickets whenever the primary organization of a user is changed." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:9 -msgid "300" +#: ../settings/ticket.rst:74 +msgid "Update the most recent tickets." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:11 -msgid "**🥵 Potential performance issue**" +#: ../settings/ticket.rst:72 +msgid "" +"If this option is chosen, Zammad will update the 100 most recent tickets " +"where the user is the ticket customer. The ticket organization field will be " +"automatically set to the new primary organization of the user." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:13 +#: ../settings/ticket.rst:88 +msgid "Do not update any tickets." +msgstr "" + +#: ../settings/ticket.rst:77 msgid "" -"Setting this setting higher than 60 may cause serious performance issues on " -"very busy instances. Keep in mind that this setting causes Zammad to poll " -"and send up to 300 records to *all active agent sessions* in very short time " -"periods." +"When choosing this option, Zammad will not update any tickets when the " +"user's primary organization is changed." msgstr "" -#: ../system/integrations/cti/generic.rst:73 -msgid "Caller Log Filter" +#: ../settings/ticket.rst:80 +msgid "**Use with care!**" msgstr "" -#: ../system/integrations/cti/generic.rst:55 +#: ../settings/ticket.rst:82 msgid "" -"This function allows you to provide call information based on e.g. queues " -"only to agents that really need the information." +"Using this option may lead to inconsistencies in the system as the ticket " +"organization may become decoupled from the ticket customer." msgstr "" -#: ../system/integrations/cti/generic.rst:58 +#: ../settings/ticket.rst:85 msgid "" -"Why? If you have a team for several countries or departments, you don't want " -"to bug your agents from other departments. Leaving these options empty will " -"fallback to showing everything to everyone." +"However, you may use this option if you wish to maintain :ref:`the shared " +"access ` to the ticket for all organization " +"members of the original organization of the customer." msgstr "" -#: ../system/integrations/cti/generic.rst:64 -msgid "Destination caller ID or Queue" +#: ../settings/ticket.rst:110 +msgid "Ticket Number Format (default: ``Increment (SystemID.Counter)``)" msgstr "" -#: ../system/integrations/cti/generic.rst:63 +#: ../settings/ticket.rst:94 msgid "" -"This depends on your PBX and usually is either a queue ID, phone number or " -"extension." +"This setting defines the way Zammad's ticket number will look. Changing this " +"setting in production will cause follow up detection to fail." msgstr "" -#: ../system/integrations/cti/generic.rst:69 -msgid "Agents" +#: ../settings/ticket.rst:102 +msgid "Increment (SystemID.Counter)" msgstr "" -#: ../system/integrations/cti/generic.rst:67 +#: ../settings/ticket.rst:98 msgid "" -"Select the agents that are responsible for the group. These agents will then " -"see caller log entries and call notifications fitting to said queue." +"The increment value contains the SystemID (automatically generated during " +"installation) and a increment which counts up with every new Ticket. The " +"increment will automatically get another digit if needed." msgstr "" -#: ../system/integrations/cti/generic.rst:0 -msgid "" -"Screenshot showing the caller log filter table with pre filled sample data" +#: ../settings/ticket.rst:102 +msgid "Examples: ``1010138``, ``1010139``" msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:6 -msgid "" -"With recent logs Zammad allows you to view the latest calls for the CTI " -"functionality. This usually comes in handy, when you're looking for errors." +#: ../settings/ticket.rst:110 +msgid "Date (Year.Month.Day.SystemID.Counter)" msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:0 +#: ../settings/ticket.rst:105 msgid "" -"Screenshot showing several incoming requests within Recent logs section." +"This version of the ticket number is fairly long. However, because it " +"contains the date of ticket creation, it also allows you to see when the " +"ticket has been created. You may feel familiar with this number format if " +"you've worked with OTRS already." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:16 -msgid "I'm just here to clear floats up." +#: ../settings/ticket.rst:110 +msgid "Examples: ``201206231010138``, ``201206231010139``" msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:20 -msgid "" -"By clicking on the entry of interest, Zammad will provide more details on " -"the call in question. You'll see the payload it received and also the " -"response that was sent." +#: ../settings/ticket.rst:137 +msgid "OPTIONS" msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:0 +#: ../settings/ticket.rst:113 msgid "" -"Screenshot showing detailed information of a specific log entry of recent " -"logs" -msgstr "" - -#: ../system/integrations/cti/includes/recent-logs.include.rst:31 -msgid "x" +"The below options allow you to further customize your ticket number. The " +"availability of options differ depending of the chosen ticket number format " +"above." msgstr "" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 -#: ../system/integrations/cti/includes/troubleshooting.include.rst:9 -msgid "My Phone page stays blank, signalling does work..." +#: ../settings/ticket.rst:122 +msgid "Checksum (default: ``no``)" msgstr "" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:5 +#: ../settings/ticket.rst:118 msgid "" -"If you've made sure that signalling works (check Recent logs) and your " -"Caller Log still stays empty, please ensure that you only configured one CTI " -"integration version. Specifically defining more than one agent mapping on " -"the different integration variants will be the issue." +"If set to yes, we'll built a checksum to further \"unique\" the ticket " +"number of your system. If you're dealing with many other ticket systems this " +"might help to prevent false positive follow up detection on tickets." msgstr "" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 -msgid "Clear the not needed agent mapping and reload your browser page." +#: ../settings/ticket.rst:122 +msgid "This will also add another digit to the ticket number." msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:1 -msgid "" -"By mapping your agents extension to their existing Zammad users, Zammad can " -"provide a new ticket dialog or open the user profile for the agent that " -"picks up the call." +#: ../settings/ticket.rst:137 +msgid "Min. size of Number (default: ``5``)" msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:5 +#: ../settings/ticket.rst:125 msgid "" -"This speeds up ticket aiding, no matter if it's for existing tickets or new " -"ones!" +"This setting defines the minimum length of your ticket number. If your " +"counter is not yet high enough, Zammad will fill the number with zeros to " +"ensure the wanted length." msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:8 +#: ../settings/ticket.rst:129 msgid "" -"To see it work from the agent's perspective, have a look on :user-docs:`user " -"documentation `." +"Please note that the minimum length is ``3`` (SystemID + at least one digit " +"if below 10). Also, if the length is no longer long enough, the number will " +"automatically get one digit longer. Ticket-Numbers **do not overflow**, thus " +"it's save to keep it at 5 or set it lower if wanted." msgstr "" -#: ../system/integrations/cti/placetel.rst:2 -msgid "Placetel CTI" +#: ../settings/ticket.rst:135 +msgid "" +"This option is only available if ticket number format is set to " +"``Increment``!" msgstr "" -#: ../system/integrations/cti/placetel.rst:16 -msgid "You need an administrative Placetel account for your organization." +#: ../settings/ticket.rst:142 +msgid "Auto-Assignment" msgstr "" -#: ../system/integrations/cti/placetel.rst:17 -#: ../system/integrations/cti/sipgate.rst:20 +#: ../settings/ticket.rst:144 msgid "" -"Your Zammad instance must be allowed to communicate to external services." +"In a larger Zammad environment, it happens that several agents open the same " +"ticket at the same time. Although collision detection is then effective, the " +"efficiency of processing can be increased by means of the automatic " +"assignment of tickets when a ticket is opened." msgstr "" -#: ../system/integrations/cti/placetel.rst:18 -msgid "Placetel must be able to reach your Zammad instance." +#: ../settings/ticket.rst:149 +msgid "" +"The automatic assignment of tickets can be activated and configured in the " +"admin area under Settings > Ticket > Auto Assignment." msgstr "" -#: ../system/integrations/cti/placetel.rst:22 -msgid ":doc:`provider-configurations/placetel`" +#: ../settings/ticket.rst:152 +msgid "" +"The auto assignment only works if the ticket has no owner yet. By default, " +"the agent can always reset the ticket owner to ``-`` if needed." msgstr "" -#: ../system/integrations/cti/placetel.rst:21 +#: ../settings/ticket.rst:155 msgid "" -"Learn how to configure Placetel to enable Zammad and Placetel to communicate " -"with each other." +"If you want to use this function for only specific tickets, you can " +"configure the conditions accordingly to meet your requirement. By default " +"the condition affects all tickets with the state ``open``." msgstr "" -#: ../system/integrations/cti/placetel.rst:32 +#: ../settings/ticket.rst:161 msgid "" -"The here listed endpoint settings are relevant for the :doc:`integration " -"configuration with Placetel `." +"If you need to exclude users (e.g. a group leader), you can search and " +"select the desired agents in the ``Exception Users`` list. The search " +"function in this area is only effective, if you have too many agents to " +"display at once to help you with the configuration." msgstr "" -#: ../system/integrations/cti/placetel.rst:37 -#: ../system/integrations/i-doit.rst:53 -msgid "Endpoint" -msgstr "" +#: ../settings/ticket.rst:167 +#, fuzzy +msgid "Notifications" +msgstr "Limitação" -#: ../system/integrations/cti/placetel.rst:36 +#: ../settings/ticket.rst:191 +#, fuzzy +msgid "Default Notifications" +msgstr "Limitação" + +#: ../settings/ticket.rst:170 msgid "" -"This endpoint will be required for the Zammad integration within the " -"Placetel web interface." +"This setting allows you to configure the default ticket notifications that " +"will be applied to all new agent users (incl. users who were just assigned " +"agent role). Simply change the notification matrix to desired state and " +"press **Save**." msgstr "" -#: ../system/integrations/cti/placetel.rst:41 -msgid "API Token" +#: ../settings/ticket.rst:175 +msgid "" +"In case an agent already exists, their ticket notification preferences will " +"be preserved. Optionally, you can also **Apply current defaults to all " +"agents**." msgstr "" -#: ../system/integrations/cti/placetel.rst:40 +#: ../settings/ticket.rst:181 msgid "" -"You'll receive this token within the ``Web API`` menu. Make sure to copy " -"this value, it's only shown once!" +"**Potential time-consuming action:** Applying default ticket notifications " +"to all agent users may take some time to complete, be patient! The exact " +"time will depend on the size of your system and the number of agents." msgstr "" -#: ../system/integrations/cti/placetel.rst:71 -#: ../system/integrations/cti/sipgate.rst:77 -msgid "Phone Extension to Agent Mapping" +#: ../settings/ticket.rst:185 +msgid "" +"**Active agents only!** When current default ticket notifications are " +"applied, only active agent users are considered. In case an agent is re-" +"activated *after* this action, they will still have the old notification " +"configuration." msgstr "" -#: ../system/integrations/cti/placetel.rst:0 -msgid "Screenshot showing sample user mappings in between Placetel and Zammad" +#: ../settings/ticket.rst:190 +msgid "" +"In case you want to go back to the initial state of ticket notifications, " +"you can click on **Reset to default** button." msgstr "" -#: ../system/integrations/cti/placetel.rst:64 +#: ../settings/ticket.rst:196 +msgid "Duplicate Detection" +msgstr "" + +#: ../settings/ticket.rst:238 +#, fuzzy +msgid "Detect Duplicate Ticket Creation" +msgstr "na criação do Chamado" + +#: ../settings/ticket.rst:199 msgid "" -"You can find your agents Placetel username combination required within ⚙️ PBX " -"→ VoIP destinations. Within the \"Advanced settings\" section you're looking " -"for \"SIP user name\" and \"SIP server\"." +"This setting turns on the duplicate ticket detection mechanism during ticket " +"creation. If similar tickets are found in the system, a suitable warning " +"will be shown to the user trying to create a ticket." msgstr "" -#: ../system/integrations/cti/placetel.rst:68 -msgid "Combine these two like so: ``@``." +#: ../settings/ticket.rst:206 +msgid "A Sample Duplicate Ticket Warning" msgstr "" -#: ../system/integrations/cti/placetel.rst:0 -msgid "Sample VoIP credentials for a Placetel user" +#: ../settings/ticket.rst:208 +msgid "" +"You can choose which ticket attributes will be matched by selecting them in " +"**Attributes to compare** field. Only if the ticket attribute value provided " +"by the user in the ticket create form is *equal* with the attribute in an " +"existing ticket, the warning will be shown." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:2 -msgid "Setup Placetel connection for Zammad" +#: ../settings/ticket.rst:213 +msgid "**Warning title** and **Warning message** are configurable as well." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:6 +#: ../settings/ticket.rst:215 msgid "" -"This configuration step requires a *full* administrative Placetel account. " -"You may receive forbidden error messages with Placetel in case your " -"permissions are not high enough." +"You can limit the detection only to certain user roles. By default, only " +"agents will see the warning." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:10 +#: ../settings/ticket.rst:218 msgid "" -"The following actions can be configured via the `Placetel web interface " -"`_." +"If you don't want to show the matched tickets as part of the warning, you " +"can set **Show matching ticket(s) in the warning** setting to *no*." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:29 -msgid "Step 1: Activate Zammad integration" +#: ../settings/ticket.rst:221 +msgid "" +"By default, **Permission level for looking up ticket** is set to *User*, " +"which means user permissions will be honored during sarch. The user will " +"see the warning only if tickets they have access to are matched. " +"Alternatively, you can set this setting to *System*, in which case the " +"search will happen within *all* tickets in the system, regardless of user " +"permissions." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:14 -msgid "" -"Within Integrations, scroll down to Partner integrations and select Zammad." +#: ../settings/ticket.rst:227 +msgid "**🦺 Safety first!**" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:17 +#: ../settings/ticket.rst:229 msgid "" -"You can alternatively filter by \"Ticket Systems\" to reduce the number of " -"entries on the page. You'll still want to look for Partner integrations. 🤓" +"Even if the permission level is set to *System*, the user will not be shown " +"the tickets they don't have access to in the warning, even if they match." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:21 +#: ../settings/ticket.rst:233 msgid "" -"Within the Zammad integration now press \"Activate\". A new tab ``API`` " -"becomes available - open this tab." +"However, just the confirmation about the existence of the tickets in the " +"system may be considered an unwanted information disclosure. Use this option " +"carefully!" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:24 +#: ../settings/ticket.rst:237 msgid "" -"Now tick \"Enable Call Control / Notify API\" and paste the Placetel " -"endpoint from your Zammad instance into the field \"URL of your API " -"endpoint\". Save to apply the settings" +"Finally, you can configure between matching within **All tickets** or **Open " +"tickets** only by setting **Match tickets in following states**. Depending " +"on the current ticket state, a ticket may or not be matched." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 -msgid "Screencast showing how to activate the Zammad integration" +#: ../system/core-workflows.rst:2 +msgid "Core Workflows" +msgstr "Fluxos de Trabalho" + +#: ../system/core-workflows.rst:4 +msgid "" +"Core Workflows allow you to adjust object attributes in many ways. For " +"example:" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:51 -msgid "Step 2: Generate API Token for Placetel" +#: ../system/core-workflows.rst:7 +msgid "show / hide fields" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:32 -msgid "" -"Go back to the integrations page and scroll down to \"Web API\". Generate a " -"new API token by using the \"Create a new API token\" button." +#: ../system/core-workflows.rst:8 +msgid "adjust mandatory setting" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:37 -msgid "" -"If you already generated a token either use your existing token or reset it " -"by using above mentioned button. Placetel will ask you to conform this reset." +#: ../system/core-workflows.rst:9 +msgid "manipulate available options" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:41 +#: ../system/core-workflows.rst:11 msgid "" -"Please keep in mind that existing API scripts may no longer work due to " -"token resets!" +"With this, you can provide exactly the information your users really need!" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:44 +#: ../system/core-workflows.rst:15 msgid "" -"Copy the provided API token and insert it into the \"API Token\" field " -"within Zammad's Placetel integration." +"If the pre-defined :doc:`/system/objects` are not enough, please add them " +"beforehand." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:47 +#: ../system/core-workflows.rst:17 msgid "" -"Apply your changes by using the \"Save\" button on the bottom of the " -"Placetel integration page and activate the Placetel integration." +"If you experience slow or unreliable field updates, please see :ref:`Core " +"Workflow Ajax Modus `" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +#: ../system/core-workflows.rst:22 msgid "" -"Screencast showing how to retrieve an API token from Placetel for Zammad" +"This is a very enhanced functionality and can cause unexpected UI behavior. " +"Please ensure to test your use cases after configuration to reduce surprises." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:73 -#: ../system/integrations/cti/provider-configurations/sipgate.rst:77 -msgid "Step 3: Restrict the numbers to notify on" +#: ../system/core-workflows.rst:None +msgid "Dialogue for adding a new workflow" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:54 -msgid "" -"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " -"the the Integrations page of the Placetel web interface, go to \"Notify " -"API\"." -msgstr "" +#: ../system/core-workflows/condition-operators.rst:2 +#, fuzzy +msgid "Core Workflow Condition Operators" +msgstr "Fluxos de Trabalho" -#: ../system/integrations/cti/provider-configurations/placetel.rst:58 +#: ../system/core-workflows/condition-operators.rst:4 msgid "" -"Lower on the page Placetel allows you to restrict the numbers to notify on. " -"You'll find this within the \"External routing API\" part." +"You might know that there is a separate section for explaining :doc:" +"`condition operators `. Head over there to " +"see a detailed explanation of many conditions and operators." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +#: ../system/core-workflows/condition-operators.rst:8 msgid "" -"Screenshot showing a sample selection of phone numbers to use for the " -"Placetels notify API" +"Due to differences to other places in Zammad which are also using conditions " +"(e.g. triggers), you can find a dedicated description of operators for core " +"workflows below." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:66 +#: ../system/core-workflows/condition-operators.rst:12 msgid "" -"This menu point also provides a API request log from Placetel view. Just " -"open \"Recent responses of your API endpoint\" to learn more." +"Be aware that the availability of the operators depends on the selected " +"attribute and its field type. Some of the operators may only be available " +"for system attributes (e.g. for \"tags\", \"active\")." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:69 -msgid "" -"If you want to see Zammad's perspective, use the \"Recent Logs\" part from " -"within the Placetel integration page." +#: ../system/core-workflows/condition-operators.rst:20 +msgid "Operator" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 -msgid "Screenshot showing sample log entries for Placetels API calls to Zammad" +#: ../system/core-workflows/condition-operators.rst:22 +msgid "after (absolute)" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:77 -msgid "Step 4 (optional): Further configurations for Placetel" +#: ../system/core-workflows/condition-operators.rst:23 +msgid "Matches if a date/time is after a specific point in time." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:76 -msgid "" -"If needed, you can now configure Zammad's Placetel integration in more " -"detail. You can learn more about your options here: :ref:`Placetel " -"integration settings `." +#: ../system/core-workflows/condition-operators.rst:24 +msgid "after (relative)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:2 -msgid "Setup Sipgate connection for Zammad" +#: ../system/core-workflows/condition-operators.rst:25 +msgid "Matches if a time span after a specified event has passed." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Sipgate has no english web interface which is why this documentation page is " -"mixing up languages badly." +#: ../system/core-workflows/condition-operators.rst:26 +msgid "before (absolute)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Please also note that the availability of API addons highly depends on your " -"package trier. Usage of sipgate.io packages *is not free*, please check " -"their `pricing page `_ before!" +#: ../system/core-workflows/condition-operators.rst:27 +msgid "Matches if a date/time is before a specific point in time." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:35 -msgid "Step 1: Book sipgate.io package" +#: ../system/core-workflows/condition-operators.rst:28 +msgid "before (relative)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:13 -msgid "Skip to step 2 if you already have the package booked!" +#: ../system/core-workflows/condition-operators.rst:29 +msgid "Matches if a time span after a specified event has not passed." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:15 -msgid "" -"Login to an administrative Sipgate account and navigate to " -"``Accountverwaltung``. You'll see several different options depending on " -"your booked packages. Select ``Verträge & Produkte`` to continue." +#: ../system/core-workflows/condition-operators.rst:30 +msgid "contains" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:19 -msgid "" -"Scroll down to the section ``Zusätzliche Produkte buchen`` and look for " -"``sipgate.io`` - select this product by using the ``Produkte anzeigen``-" -"Button." +#: ../system/core-workflows/condition-operators.rst:31 +msgid "Matches if a specified value is present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:23 -msgid "" -"On the next page select either one of the ``sipgate.io`` packages or ``Push-" -"API Package Free``. Follow the dialogue by booking the addon. You'll be " -"returned to your contract overview and now should see the selected addon in " -"your list." +#: ../system/core-workflows/condition-operators.rst:33 +msgid "Matches if all of the specified values are present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:30 -msgid "" -"The availability for ``sipgate.io`` packages and their levels highly depends " -"on the overall account type and product you've booked with Sipgate." +#: ../system/core-workflows/condition-operators.rst:35 +msgid "Matches if none of the specified values are present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screencast showing the process on how to book the required sipgate.io addon" +#: ../system/core-workflows/condition-operators.rst:36 +msgid "contains not" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:52 -msgid "Step 2: Configure webhook for Zammad" +#: ../system/core-workflows/condition-operators.rst:37 +msgid "Matches if a specified value is not present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:38 -msgid "" -"Within your ``Accountverwaltung`` navicate to your product ``sipgate.io``. " -"In the newly opened tab, switch from \"Clients\" to \"Webhooks\" and paste " -"the endpoint URLs from your Zammad instance like so:" +#: ../system/core-workflows/condition-operators.rst:39 +msgid "Matches if one specified value is present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:42 -msgid "Inbound endpoint to \"Incoming\"" +#: ../system/core-workflows/condition-operators.rst:41 +msgid "Matches if one specified value is not present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:43 -msgid "Outbound endpoint to \"Outgoing\"" +#: ../system/core-workflows/condition-operators.rst:42 +msgid "does not match regex" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:47 -msgid "" -"Ensure to select at least one call group or phoneline within \"Sources\". " -"Other wise Sipgate will not indicate any incoming or outgoing calls to " -"Zammad." +#: ../system/core-workflows/condition-operators.rst:43 +msgid "Matches if content doesn't fit to regex rule." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screencast showing how to add Zammad's endpoint URLs to sipgate.ios webhook " -"configuration" +#: ../system/core-workflows/condition-operators.rst:44 +msgid "ends with" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:55 -msgid "" -"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " -"the Webhooks → URLs section of Sipgate you can select which *sources* " -"Sipgate should notify Zammad about in- and outgoing calls." +#: ../system/core-workflows/condition-operators.rst:45 +msgid "Matches if content ends with specified value." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:59 -msgid "" -"Use either specific phone lines or use the option \"Use for all phonelines " -"and groups\" to notify Zammad about all existing lines of your Sipgate " -"account." +#: ../system/core-workflows/condition-operators.rst:46 +msgid "ends with one of" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screenshot showing a sample selection of phone numbers to use for the " -"Sipgates webhooks API" +#: ../system/core-workflows/condition-operators.rst:47 +msgid "Matches if content ends with one of the specified values." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:68 -msgid "This section also allows you to enable a Debug log." +#: ../system/core-workflows/condition-operators.rst:48 +msgid "from (relative)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "Screenshot showing an enabled Debug log option" +#: ../system/core-workflows/condition-operators.rst:49 +msgid "Matches if date/time is after a period of time after an event." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:73 -msgid "" -"After enabling you can use the Debug log section to see all sent webhook " -"calls to Zammad. You'll also can see the response." +#: ../system/core-workflows/condition-operators.rst:51 +msgid "Matches if content is equal to a specified value." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screenshot showing sample log entries for Sipgates webhook calls to Zammad" +#: ../system/core-workflows/condition-operators.rst:52 +msgid "is any of" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:81 -msgid "Step 4 (optional): Further configurations for Sipgate" +#: ../system/core-workflows/condition-operators.rst:53 +msgid "Matches if content is equal to any of specified values." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:80 -msgid "" -"If needed, you can now configure Zammad's Sipgate integration in more " -"detail. You can learn more about your options here: :ref:`Sipgate " -"integration settings `." +#: ../system/core-workflows/condition-operators.rst:54 +msgid "is modified" msgstr "" -#: ../system/integrations/cti/sipgate.rst:2 -msgid "Sipgate (sipgate.io)" +#: ../system/core-workflows/condition-operators.rst:55 +msgid "Matches if content is modified." msgstr "" -#: ../system/integrations/cti/sipgate.rst:16 -msgid "You need an administrative Sipgate account for your organization." +#: ../system/core-workflows/condition-operators.rst:57 +#: ../system/core-workflows/condition-operators.rst:61 +msgid "True from the moment of changing content until form submit." msgstr "" -#: ../system/integrations/cti/sipgate.rst:17 -msgid "" -"Zammad requires a ``sipgate.io`` addon from the feature store (please note " -"that API calls are not free with Sipgate. Rates may apply and differ from " -"account to account)." +#: ../system/core-workflows/condition-operators.rst:58 +msgid "is modified to" msgstr "" -#: ../system/integrations/cti/sipgate.rst:21 -msgid "Sipgate must be able to reach your Zammad instance." +#: ../system/core-workflows/condition-operators.rst:59 +msgid "Matches if content is modified to a specific value." msgstr "" -#: ../system/integrations/cti/sipgate.rst:25 -msgid ":doc:`provider-configurations/sipgate`" +#: ../system/core-workflows/condition-operators.rst:62 +msgid "is none of" msgstr "" -#: ../system/integrations/cti/sipgate.rst:24 -msgid "" -"Learn how to configure Sipgate to enable Zammad and Sipgate to communicate " -"with each other." +#: ../system/core-workflows/condition-operators.rst:63 +msgid "Matches if content is none of any specified values." msgstr "" -#: ../system/integrations/cti/sipgate.rst:33 -msgid "" -"Below endpoint settings affect the :doc:`sipgate.io configuration `." +#: ../system/core-workflows/condition-operators.rst:65 +msgid "Matches if content is not equal to a specified value." msgstr "" -#: ../system/integrations/cti/sipgate.rst:37 -msgid "This endpoint is required for incoming call hooks." +#: ../system/core-workflows/condition-operators.rst:67 +msgid "Matches if content is present." msgstr "" -#: ../system/integrations/cti/sipgate.rst:40 -msgid "This endpoint is required for outgoing call hooks." -msgstr "" +#: ../system/core-workflows/condition-operators.rst:68 +#, fuzzy +msgid "just changed" +msgstr "Exchange" -#: ../system/integrations/cti/sipgate.rst:0 -msgid "Screenshot showing sample user mappings in between Sipgate and Zammad" +#: ../system/core-workflows/condition-operators.rst:69 +msgid "Matches if content has changed." msgstr "" -#: ../system/integrations/cti/sipgate.rst:69 +#: ../system/core-workflows/condition-operators.rst:71 +#: ../system/core-workflows/condition-operators.rst:75 msgid "" -"You can find your agent's Sipgate username within ``Accountverwaltung → " -"Benutzer``. You're looking for the SIP-ID." +"Only true for the moment of changing content until next form field action/" +"click." msgstr "" -#: ../system/integrations/cti/sipgate.rst:0 -msgid "Sample VoIP credentials for a Sipgate user" +#: ../system/core-workflows/condition-operators.rst:72 +msgid "just changed to" msgstr "" -#: ../system/integrations/cti/sipgate.rst:77 -msgid "Users with several devices also have several SIP-IDs." +#: ../system/core-workflows/condition-operators.rst:73 +msgid "Matches if content has changed to a specified value." msgstr "" -#: ../system/integrations/elasticsearch.rst:2 -msgid "Elasticsearch (SaaS)" +#: ../system/core-workflows/condition-operators.rst:76 +msgid "matches regex" msgstr "" -#: ../system/integrations/elasticsearch.rst:4 -msgid "" -"The Elasticsearch integration allows you to create a read-only user to use " -"with your favorite reporting tool (e.g. like Grafana)." +#: ../system/core-workflows/condition-operators.rst:77 +msgid "Matches if value fits to regex rule." msgstr "" -#: ../system/integrations/elasticsearch.rst:7 -msgid "" -"If you want to take full advantage of the Zammad reporting, have a look at " -"our :docs:`Grafana ` " -"setup page as well." +#: ../system/core-workflows/condition-operators.rst:79 +msgid "Matches if no content is present." msgstr "" -#: ../system/integrations/elasticsearch.rst:11 -#: ../system/subscription/index.rst:7 -msgid "**🚧 Hosted environment specific 🚧**" +#: ../system/core-workflows/condition-operators.rst:80 +msgid "starts with" msgstr "" -#: ../system/integrations/elasticsearch.rst:13 -msgid "" -"This integration is only available for Hosted setups. In order to use " -"Elasticsearch you'll need the **Plus** subscription." +#: ../system/core-workflows/condition-operators.rst:81 +msgid "Matches if content starts with specified value." msgstr "" -#: ../system/integrations/elasticsearch.rst:16 -msgid "" -"Self hosted users have all the control over their self hosted Elasticsearch " -"instances." +#: ../system/core-workflows/condition-operators.rst:82 +msgid "starts with one of" msgstr "" -#: ../system/integrations/elasticsearch.rst:None -msgid "Elasticsearch integration page on SaaS environments" +#: ../system/core-workflows/condition-operators.rst:83 +msgid "Matches if content starts with one of the specified values." msgstr "" -#: ../system/integrations/elasticsearch.rst:27 -msgid "" -"Please note the following limitations of Elasticsearch access on hosted " -"environments:" +#: ../system/core-workflows/condition-operators.rst:84 +msgid "till (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:30 -msgid "access to the Elasticsearch index is read-only access" +#: ../system/core-workflows/condition-operators.rst:85 +msgid "Matches if date/time is before a period of time before an event." msgstr "" -#: ../system/integrations/elasticsearch.rst:31 -msgid "currently you're limited to user only" +#: ../system/core-workflows/condition-operators.rst:86 +msgid "today" msgstr "" -#: ../system/integrations/elasticsearch.rst:32 -msgid "" -"Reporting tools that require to write into the indexes (like Kibana) are not " -"supported" +#: ../system/core-workflows/condition-operators.rst:87 +msgid "Matches if date/time is today." msgstr "" -#: ../system/integrations/elasticsearch.rst:34 -msgid "IP access restriction is currently not yet supported" +#: ../system/core-workflows/condition-operators.rst:88 +msgid "within last (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:37 -msgid "Activating Elasticsearch Access" +#: ../system/core-workflows/condition-operators.rst:89 +msgid "" +"Matches if date/time content is within specified period of time before now." msgstr "" -#: ../system/integrations/elasticsearch.rst:39 -msgid "" -"By default external access to your Elasticsearch index is not active. You " -"can enable the integration at any time if needed." +#: ../system/core-workflows/condition-operators.rst:91 +msgid "within next (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:42 +#: ../system/core-workflows/condition-operators.rst:92 msgid "" -"Please ensure to note down the password provided - you won't have access to " -"it afterwards." +"Matches if date/time content is within specified period of time after now." msgstr "" -#: ../system/integrations/elasticsearch.rst:None -msgid "Screencast showing activation of Elasticsearch integration" +#: ../system/core-workflows/how-do-they-work.rst:2 +msgid "How do they work?" msgstr "" -#: ../system/integrations/elasticsearch.rst:51 -msgid "Connection Settings" +#: ../system/core-workflows/how-do-they-work.rst:4 +msgid "" +"Core Workflows are executed according to their priority. If two workflows " +"have the same priority, they are executed in alphabetical order based on " +"their **name**." msgstr "" -#: ../system/integrations/elasticsearch.rst:53 +#: ../system/core-workflows/how-do-they-work.rst:8 msgid "" -"This section holds the most important general information for accessing your " -"Elasticsearch indexes - such as:" +"Because of the way Core Workflows work, all changes to attributes are " +"checked with the application server - please see :doc:`limitations` for " +"possible issues." msgstr "" -#: ../system/integrations/elasticsearch.rst:57 -msgid "A unique subdomain that does not tell your real instance URL." -msgstr "" - -#: ../system/integrations/elasticsearch.rst:61 -msgid "Software" +#: ../system/core-workflows/how-do-they-work.rst:12 +msgid "" +"Below we're talking about settings that are important and not self-" +"explanatory." msgstr "" -#: ../system/integrations/elasticsearch.rst:60 +#: ../system/core-workflows/how-do-they-work.rst:17 msgid "" -"The major version of the search index being used. This is required by some " -"Reporting tools like Grafana." +"Choose the object context you want to run the workflow in. This will decide " +"on your available attributes and actions." msgstr "" -#: ../system/integrations/elasticsearch.rst:64 -msgid "Authentication" +#: ../system/core-workflows/how-do-they-work.rst:20 +msgid "Ticket objects also have access to the ticket customer." msgstr "" -#: ../system/integrations/elasticsearch.rst:64 -msgid "The authentication type being supported. ``Basic Authentication``" +#: ../system/core-workflows/how-do-they-work.rst:25 +msgid "" +"Choose in which situation the workflow is applied. Contexts can be combined " +"to avoid duplicate workflows." msgstr "" -#: ../system/integrations/elasticsearch.rst:67 -msgid "Available Indexes" +#: ../system/core-workflows/how-do-they-work.rst:30 +msgid "Creation mask" msgstr "" -#: ../system/integrations/elasticsearch.rst:69 +#: ../system/core-workflows/how-do-they-work.rst:29 msgid "" -"Within this section we're displaying the -in our opinion- most important " -"indexes for a Zammad instance." +"If selected, your conditions and actions will affect all applicable creation " +"masks." msgstr "" -#: ../system/integrations/elasticsearch.rst:72 -msgid "" -"If you require all indexes or our listing is not good enough for you, point " -"your browser to the URL we're providing and append ``/_aliases?" -"pretty=true``. The result should look like this: ``https://.zammad.com/" -"_aliases?pretty=true``." +#: ../system/core-workflows/how-do-they-work.rst:34 +msgid "Edit mask" msgstr "" -#: ../system/integrations/elasticsearch.rst:77 +#: ../system/core-workflows/how-do-they-work.rst:33 msgid "" -"Your browser will automatically ask for your credentials - you'll then see " -"something like this:" +"If selected, your conditions and actions will affect all applicable edit " +"masks." msgstr "" -#: ../system/integrations/elasticsearch.rst:125 -msgid "Credentials" +#: ../system/core-workflows/how-do-they-work.rst:39 +msgid "" +"Zammad differentiates between selected and saved conditions. These can be " +"combined wherever needed." msgstr "" -#: ../system/integrations/elasticsearch.rst:127 -msgid "" -"Within this section Zammad displays your available users. The password is " -"provided once (upon activation) and cannot be retrieved after that." +#: ../system/core-workflows/how-do-they-work.rst:42 +msgid "**⚠️ Restrict workflows to specific roles if needed!**" msgstr "" -#: ../system/integrations/elasticsearch.rst:131 +#: ../system/core-workflows/how-do-they-work.rst:44 msgid "" -"If you need to change or reset your Elasticsearch user password, use the " -"\"Reset password\" button in the credentials table. Doing so creates a brand " -"new password for the account in question. This change is immediate, keep in " -"mind that this may affect third party tools connected to your instance." +"By default and unless configured in conditions, workflow rules are executed " +"for **all roles**. This also affects your customers!" msgstr "" -#: ../system/integrations/exchange.rst:2 -msgid "Exchange" -msgstr "Exchange" - -#: ../system/integrations/exchange.rst:4 -msgid "" -"With Zammad's Exchange integration, you can easily use existing address " -"books without having to update more than one source." +#: ../system/core-workflows/how-do-they-work.rst:50 +msgid "Selected Conditions" msgstr "" -#: ../system/integrations/exchange.rst:7 +#: ../system/core-workflows/how-do-they-work.rst:48 msgid "" -"However, you should refrain from syncing all addresses, as the results may " -"not be what you expect (Exchange collects huge amounts of addresses). A " -"central address book of your company to sync makes more sense, as you can " -"ensure that Zammad gets only the data you need and want. Apart from this, it " -"is even not possible to sync the Global Address List (GAL) of your Exchange " -"system with Zammad." +"These conditions are based on form values and match if an appropriate " +"selection is made (e.g. choosing another group in the ticket without " +"saving). This applies for drafts (active selection) and currently saved " +"values." msgstr "" -#: ../system/integrations/exchange.rst:16 -msgid "" -"**Exchange and LDAP:** The exchange sync can be overruled by Zammad's LDAP " -"integration. If you have the same users in both sources, the LDAP version " -"will always be Zammad's pick." +#: ../system/core-workflows/how-do-they-work.rst:64 +msgid "Saved Conditions" msgstr "" -#: ../system/integrations/exchange.rst:19 +#: ../system/core-workflows/how-do-they-work.rst:53 msgid "" -"**One way sync:** the Exchange sync is one way. Exchange => Zammad. Changes " -"to your users inside of Zammad might be overwritten by the Exchange sync." +"These conditions only match if the selected values are stored in the " +"database. It ignores the current value or selection of the field, as long as " +"the changes are not saved (e.g. performing field operations for an existing " +"ticket, which is viewed/opened by an agent)." msgstr "" -#: ../system/integrations/exchange.rst:24 +#: ../system/core-workflows/how-do-they-work.rst:60 msgid "" -"To configure Exchange integration, simply go to the System > Integrations > " -"Exchange in the admin panel. Press \"change\" and follow the wizard for " -"adding the needed Exchange information to Zammad. On the last two steps " -"Zammad will ask you for the address book(s) and your desired attribute " -"mapping. By default, Zammad only maps email address, first- and lastname. " -"Technically, you can map any Exchange object to a Zammad user object (this " -"also works for custom objects!)." +"Keep in mind that the value has to be available in the situation where you " +"need it. Otherwise the condition won't match." msgstr "" -#: ../system/integrations/exchange.rst:35 +#: ../system/core-workflows/how-do-they-work.rst:63 msgid "" -"If the SSL verification fails while connecting to Exchange, Zammad will ask " -"you to turn it off temporarily." +"Example: you can't perform any actions with *saved condition* on a ticket in " +"creation, because there are no saved values at that time." msgstr "" -#: ../system/integrations/exchange.rst:38 +#: ../system/core-workflows/how-do-they-work.rst:66 msgid "" -"Please be aware that **turning off SSL verification is a security risk**. It " -"should only be used temporarily or for testing purposes. If turned off, " -"there is no verification of the certificate, which means that every " -"presented certificate will be accepted." +"You can find a description of the condition operators for core workflows :" +"doc:`here `." msgstr "" -#: ../system/integrations/exchange.rst:43 +#: ../system/core-workflows/how-do-they-work.rst:72 msgid "" -"After pressing Continue, Zammad will check if the configuration is okay. You " -"can then enable Exchange and start your first sync. The sync will then run " -"hourly - if you need to change mappings or the address book(s), you can " -"change the configuration at any time." +"Which actions should we run on the relevant fields? The possible actions " +"depend on the object type. However, usually you can at least change the " +"visibility and whether the field is mandatory." msgstr "" -#: ../system/integrations/exchange.rst:50 -msgid "" -"After the sync has finished, you can find the new Exchange contacts under " -"\"Users\". Zammad integrates them just as normal users." +#: ../system/core-workflows/how-do-they-work.rst:76 +msgid "Be aware that actions are not available for **related** context." msgstr "" -#: ../system/integrations/exchange.rst:55 +#: ../system/core-workflows/how-do-they-work.rst:78 msgid "" -"In some cases you might see unique IDs as \"Login\" instead of the email " -"address. This is normal and doesn't affect the login or email mapping for " -"that entry." +"**Example:** Let's assume you are working in the ticket context. While you " +"can have customer *conditions*, you *can't adjust* objects with actions in " +"that scope. That's because this wouldn't have any impact on the ticket " +"dialog. Of course all ticket attributes (state, owner, ...) are available." msgstr "" -#: ../system/integrations/github.rst:4 +#: ../system/core-workflows/how-do-they-work.rst:84 msgid "" -"Use GitHub integration to track GitHub issues directly within Zammad " -"tickets. Add issue hyperlinks and get a live summary of metadata like status " -"(open/closed), assignee, labels, and more." +"Please also have a look at our :doc:`limitations` to be safe from surprises." msgstr "" -#: ../system/integrations/github.rst:8 -#, fuzzy -msgid "Please note that our GitHub integration does not support pull requests." +#: ../system/core-workflows/how-do-they-work.rst:88 +msgid "Available Operators" msgstr "" -"A integração do GitLab não oferece suporte a solicitações de mesclagem." -#: ../system/integrations/github.rst:None -msgid "Integration page for GitHub" +#: ../system/core-workflows/how-do-they-work.rst:90 +msgid "The availability of operators depends on the object type and scope." msgstr "" -#: ../system/integrations/github.rst:18 +#: ../system/core-workflows/how-do-they-work.rst:94 msgid "" -"In your GitHub settings, create a new API token under **Developer settings > " -"Personal access tokens > Generate new token**. Leave the **Scopes** section " -"empty." +"Please note that actions may or may not restrict API based access to " +"attributes. We're displaying the following icons for your overview to " +"understand these limits better:" msgstr "" -#: ../system/integrations/github.rst:0 ../system/integrations/gitlab.rst:0 -msgid "Screencast showing how to create a new API token" +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|api| This icon indicates the action affects the API." msgstr "" -#: ../system/integrations/github.rst:27 -msgid "Create a new API key with no scopes/privileges." +#: ../system/core-workflows/how-do-they-work.rst:163 +msgid "api" msgstr "" -#: ../system/integrations/github.rst:29 -msgid "🔒 **Will this work for private repos?**" +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|ui| This icon indicates the action only affects the web interface." msgstr "" -#: ../system/integrations/github.rst:31 -msgid "" -"No. To link private repo issues, **use the** ``repo`` **scope instead**. " -"Bear in mind that the resulting token will have `lots of permissions that it " -"doesn't actually need `_, which presents a security risk if your token ever falls into " -"the wrong hands." +#: ../system/core-workflows/how-do-they-work.rst:167 +msgid "ui" msgstr "" -#: ../system/integrations/github.rst:37 -msgid "" -"Unfortunately, because of how GitHub's OAuth token scopes are set up, this " -"is the only way to link issues on private repos." +#: ../system/core-workflows/how-do-they-work.rst:102 +msgid "show |ui|" msgstr "" -#: ../system/integrations/github.rst:40 -msgid "Enter your new API token in Zammad and enable GitHub integration." +#: ../system/core-workflows/how-do-they-work.rst:102 +msgid "Display the chosen field. Allows setting of values." msgstr "" -#: ../system/integrations/github.rst:0 -msgid "Screencast showing how to configure Zammad's GitHub integration" +#: ../system/core-workflows/how-do-they-work.rst:109 +msgid "hide |ui|" msgstr "" -#: ../system/integrations/github.rst:47 -#, fuzzy +#: ../system/core-workflows/how-do-they-work.rst:105 msgid "" -"Use the default API endpoint (``https://api.github.com/graphql``) unless " -"you're using GitHub Enterprise Server." +"Hide the chosen field. However, it technically still allows setting the " +"field." msgstr "" -"Deixe o endpoint padrão da API (``https://gitlab.com/api/graphql``) como " -"está, a menos que você seja um usuário Gitlab auto-hospedado." -#: ../system/integrations/github.rst:50 +#: ../system/core-workflows/how-do-they-work.rst:108 msgid "" -"Once completed, a new GitHub issues tab will appear in the ticket pane. 🎉" +"Please note that the field is **not** gone and still contains an existing " +"value (if set)! Consider *remove* instead, if you want this field to be gone." msgstr "" -#: ../system/integrations/github.rst:59 ../system/integrations/gitlab.rst:52 -msgid "Token verification is taking a long time" -msgstr "A verificação do token está demorando muito" +#: ../system/core-workflows/how-do-they-work.rst:112 +msgid "remove |ui|" +msgstr "" -#: ../system/integrations/github.rst:56 ../system/integrations/gitlab.rst:49 -msgid "" -"Slight delays are normal (<2 min.), especially for systems under heavy load." +#: ../system/core-workflows/how-do-they-work.rst:112 +msgid "Entirely removes the field. The field value will not be evaluated." msgstr "" -"Atrasos leves são normais (<2 min.), especialmente para sistemas sob carga " -"pesada." -#: ../system/integrations/github.rst:58 -#, fuzzy -msgid "" -"Self-hosted administrators, please check your network settings to ensure " -"that your Zammad server can reach ``api.github.com``." +#: ../system/core-workflows/how-do-they-work.rst:115 +msgid "set mandatory |ui| |api|" msgstr "" -"Administradores de ambientes auto-hospedados, verifique suas configurações " -"de rede para garantir que seu servidor Zammad pode acessar gitlab.com." -#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 -msgid "I reloaded the page and now the API token is gone" -msgstr "Eu recarreguei a página e agora o token de API se perdeu" +#: ../system/core-workflows/how-do-they-work.rst:115 +msgid "Sets the field to mandatory." +msgstr "" -#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 -msgid "" -"This may indicate that Zammad is still verifying your API token. Try " -"reloading the page again in a couple minutes." +#: ../system/core-workflows/how-do-they-work.rst:118 +msgid "set optional |ui| |api|" msgstr "" -"Isso pode indicar que Zammad ainda está verificando seu token de API. Tente " -"recarregar a página novamente em alguns minutos." - -#: ../system/integrations/gitlab.rst:2 -msgid "GitLab" -msgstr "GitLab" -#: ../system/integrations/gitlab.rst:4 -msgid "" -"Use GitLab integration to track GitLab issues directly within Zammad " -"tickets. Add issue hyperlinks and get a live summary of metadata like status " -"(open/closed), assignee, labels, and more." +#: ../system/core-workflows/how-do-they-work.rst:118 +msgid "Sets the field to optional." msgstr "" -"Use a integração do GitLab para rastrear problemas do GitLab diretamente nos " -"chamados do Zammad. Adicione hiperlinks de problemas e obtenha um resumo em " -"tempo real de metadados, como status (aberto/fechado), atribuição, etiquetas " -"e muito mais." -#: ../system/integrations/gitlab.rst:8 -#, fuzzy -msgid "" -"Please note that our GitLab integration does not support merge requests." +#: ../system/core-workflows/how-do-they-work.rst:124 +msgid "add option |ui| |api|" msgstr "" -"A integração do GitLab não oferece suporte a solicitações de mesclagem." -#: ../system/integrations/gitlab.rst:None -msgid "Integration page for GitLab" +#: ../system/core-workflows/how-do-they-work.rst:121 +msgid "Allows adding options to tree selects or selects." msgstr "" -#: ../system/integrations/gitlab.rst:18 -#, fuzzy +#: ../system/core-workflows/how-do-they-work.rst:123 msgid "" -"In your GitLab preferences, create a new API token under **Access Tokens**." +"You have to use the \"remove option\" before performing this action. It " +"allows you to use *existing* configured values." msgstr "" -"Nas preferências do GitLab, crie um novo token de API em **Tokens de " -"acesso**." -#: ../system/integrations/gitlab.rst:20 -#, fuzzy -msgid "Under **Select scopes**, choose ``read_api`` only." -msgstr "Em **Selecionar escopos**, escolha apenas ``read_api``." - -#: ../system/integrations/gitlab.rst:27 -msgid "🔒 **If you wish to link issues on any private repos...**" +#: ../system/core-workflows/how-do-they-work.rst:128 +msgid "remove option |ui| |api|" msgstr "" -"🔒 **Se você deseja vincular problemas em qualquer repositório privado...**" -#: ../system/integrations/gitlab.rst:29 -msgid "Your API token must belong to an account with access to those repos." +#: ../system/core-workflows/how-do-they-work.rst:127 +msgid "" +"Allows removing options from tree selects or selects. It allows you to use " +"*existing* configured values." msgstr "" -"Seu token de API deve pertencer a uma conta com acesso a esses repositórios." -#: ../system/integrations/gitlab.rst:31 -msgid "Enter your new API token in Zammad and enable GitLab integration." +#: ../system/core-workflows/how-do-they-work.rst:134 +msgid "set fixed to |ui| |api|" msgstr "" -"Insira seu novo token de API no Zammad e habilite a integração com o Gitlab." -#: ../system/integrations/gitlab.rst:0 -msgid "Screencast showing how to configure Zammad's GitLab integration" +#: ../system/core-workflows/how-do-they-work.rst:131 +msgid "Reduces the available options by your selection." msgstr "" -#: ../system/integrations/gitlab.rst:40 -#, fuzzy +#: ../system/core-workflows/how-do-they-work.rst:133 msgid "" -"Use the default API endpoint (``https://gitlab.com/api/graphql``) unless " -"you're a self-hosted GitLab user." +"This reduces your workflows in terms of *add option* and *remove option*." msgstr "" -"Deixe o endpoint padrão da API (``https://gitlab.com/api/graphql``) como " -"está, a menos que você seja um usuário Gitlab auto-hospedado." -#: ../system/integrations/gitlab.rst:43 -msgid "" -"Once completed, a new GitLab issues tab will appear in the ticket pane. 🎉" +#: ../system/core-workflows/how-do-they-work.rst:137 +msgid "fill in |ui|" msgstr "" -"Após concluído, uma nova guia de problemas do Gitlab aparecerá no painel do " -"chamado. 🎉" -#: ../system/integrations/gitlab.rst:51 -#, fuzzy -msgid "" -"Self-hosted administrators, please check your network settings to ensure " -"that your Zammad server can reach ``gitlab.com``." +#: ../system/core-workflows/how-do-they-work.rst:137 +msgid "Allows filling in of string and integer fields with your values." msgstr "" -"Administradores de ambientes auto-hospedados, verifique suas configurações " -"de rede para garantir que seu servidor Zammad pode acessar gitlab.com." -#: ../system/integrations/i-doit.rst:2 -msgid "i-doit" +#: ../system/core-workflows/how-do-they-work.rst:141 +msgid "fill in empty |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:4 +#: ../system/core-workflows/how-do-they-work.rst:140 msgid "" -"`i-doit `_ is an open-source **configuration " -"management database** - in other words, a tool for keeping tabs on every " -"single piece of your physical and digital infrastructure, from network " -"equipment to virtual machines on down to the faceplates on your rack shelves " -"and more." +"Allows filling in of string and integer fields with your values **if the " +"field is empty**." msgstr "" -#: ../system/integrations/i-doit.rst:10 -msgid "" -"What's that got to do with Zammad? Well, if you used tickets to track issues " -"with all that hardware, you might start wishing there was a way they could " -"talk to each other." +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "select |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:14 -msgid "Zammad gives you two:" +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "Select a specific value within a select, tree select or boolean field." msgstr "" -#: ../system/integrations/i-doit.rst:17 -msgid "1. Add i-doit Links to Zammad Tickets" +#: ../system/core-workflows/how-do-they-work.rst:153 +msgid "auto select |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:20 ../system/integrations/i-doit.rst:80 -msgid "What Users See" +#: ../system/core-workflows/how-do-they-work.rst:147 +msgid "Helps users with tree select and select fields:" msgstr "" -#: ../system/integrations/i-doit.rst:26 -msgid "i-doit integration in Zammad's ticket pane" +#: ../system/core-workflows/how-do-they-work.rst:149 +msgid "" +"If the field has only one option available for selection and no value yet, " +"the value will be automatically set." msgstr "" -#: ../system/integrations/i-doit.rst:26 +#: ../system/core-workflows/how-do-they-work.rst:152 msgid "" -"The i-doit integration will appear under a new 🖨 tab in the ticket pane." +"This option only works if you have one value and doesn't work if there is " +"more than one option available." msgstr "" -#: ../system/integrations/i-doit.rst:28 +#: ../system/core-workflows/how-do-they-work.rst:157 +msgid "set readonly |ui|" +msgstr "" + +#: ../system/core-workflows/how-do-they-work.rst:156 msgid "" -"i-doit integration puts a new tab in Zammad's ticket pane where you can add " -"links to existing i-doit devices for easy reference. (See our :user-docs:" -"`user documentation ` to learn " -"how it works in practice)." +"Allows you to display an attribute as read only (which means no changes are " +"possible)." msgstr "" -#: ../system/integrations/i-doit.rst:36 ../system/integrations/i-doit.rst:93 -msgid "How to Set it Up" +#: ../system/core-workflows/how-do-they-work.rst:161 +msgid "unset readonly |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:38 +#: ../system/core-workflows/how-do-they-work.rst:160 msgid "" -"It requires i-doit's `API Add-on `_. Make sure to have it properly set up. Use the following setting:" +"In case a workflow set the field in question to read only, you can undo this " +"with option above." msgstr "" -#: ../system/integrations/i-doit.rst:42 -msgid "Active: ``Yes``" +#: ../system/core-workflows/how-do-they-work.rst:172 +msgid "Stop after match" msgstr "" -#: ../system/integrations/i-doit.rst:43 -msgid "Enforce authentication by username and password: ``No``" +#: ../system/core-workflows/how-do-they-work.rst:174 +msgid "" +"Here you can decide if other workflows are executed after the current one." msgstr "" -#: ../system/integrations/i-doit.rst:45 +#: ../system/core-workflows/how-do-they-work.rst:176 msgid "" -"To set it up, enable the integration in the Zammad admin panel under " -"**System > Integrations > i-doit**:" +"If set to ``no`` (default), further workflows will be executed if they match " +"the condition. In this case, it is possible that your actions from the " +"current workflow can be overwritten by another workflow." msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "i-doit settings within the integration pages" +#: ../system/core-workflows/how-do-they-work.rst:180 +msgid "" +"If set to ``yes``, no further worflows will be executed after the current " +"one." msgstr "" -#: ../system/integrations/i-doit.rst:53 -msgid "The root URL of your i-doit installation." -msgstr "" +#: ../system/core-workflows/how-do-they-work.rst:184 +msgid "Priority" +msgstr "Prioridade" -#: ../system/integrations/i-doit.rst:62 -msgid "API token" +#: ../system/core-workflows/how-do-they-work.rst:186 +msgid "" +"You can define the sequence, in which the workflows are executed. The " +"default value is ``500``." msgstr "" -#: ../system/integrations/i-doit.rst:56 +#: ../system/core-workflows/how-do-they-work.rst:189 msgid "" -"Found in the i-doit admin panel under **Interfaces / external data > JSON-" -"RPC API > Common Settings**." +"The workflows are executed in ascending order by their priority. That means " +"lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." msgstr "" -#: ../system/integrations/i-doit.rst:0 -msgid "i-doit administration interface with API configuration" -msgstr "" +#: ../system/core-workflows/learn-by-example.rst:2 +#, fuzzy +msgid "Learn by Example" +msgstr "**Por exemplo:**" -#: ../system/integrations/i-doit.rst:67 -msgid "Client ID" +#: ../system/core-workflows/learn-by-example.rst:4 +msgid "" +"This page provides some basic examples for Core Workflows. Of course you can " +"build much more complex workflows if needed." msgstr "" -#: ../system/integrations/i-doit.rst:65 -msgid "A unique name to identify Zammad within i-doit." +#: ../system/core-workflows/learn-by-example.rst:7 +msgid "" +"To learn about Core Workflows in detail, first go to :doc:`how-do-they-work`." msgstr "" -#: ../system/integrations/i-doit.rst:67 -msgid "(Zammad does not require you to enter a value here, but i-doit might!)" -msgstr "" +#: ../system/core-workflows/learn-by-example.rst:10 +#, fuzzy +msgid "Group Based Examples" +msgstr "**Por exemplo:**" -#: ../system/integrations/i-doit.rst:70 +#: ../system/core-workflows/learn-by-example.rst:12 msgid "" -"Here you can decide if the certificate of your i-doit system has to be " -"verified or not. In case you are using custom certificates, please have a " -"look at :doc:`how to add them to Zammad `." +"All following workflows have the same base configurations. The workflow may " +"not use them all." msgstr "" -#: ../system/integrations/i-doit.rst:77 -msgid "2. List / Create Zammad Tickets in i-doit" -msgstr "" +#: ../system/core-workflows/learn-by-example.rst:15 +#, fuzzy +msgid "Groups:" +msgstr "Grupos" -#: ../system/integrations/i-doit.rst:None -msgid "Zammad integration in i-doit's device view" -msgstr "" +#: ../system/core-workflows/learn-by-example.rst:20 +#, fuzzy +msgid "Attributes:" +msgstr "Atributos do artigo" -#: ../system/integrations/i-doit.rst:86 -msgid "" -"i-doit's ticket system integration gives you a way to see all the tickets " -"for a given device without ever leaving i-doit. (See our :user-docs:`user " -"documentation ` to learn how it " -"works in practice)." +#: ../system/core-workflows/learn-by-example.rst:22 +msgid "Category (Single tree selection field, not mandatory, agents only)" msgstr "" -#: ../system/integrations/i-doit.rst:95 +#: ../system/core-workflows/learn-by-example.rst:23 msgid "" -"Enable this integration in the i-doit admin panel under **Interfaces / " -"external data > Trouble Ticket System (TTS) > Configuration**:" +"Approved (Boolean field, not mandatory, not shown, ``false`` as default)" msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "i-doit administration interface with TTS configuration" -msgstr "" - -#: ../system/integrations/i-doit.rst:104 -msgid "TTS-Type" +#: ../system/core-workflows/learn-by-example.rst:24 +msgid "Operating System (Text field, not mandatory, not shown)" msgstr "" -#: ../system/integrations/i-doit.rst:104 -msgid "``Zammad``" +#: ../system/core-workflows/learn-by-example.rst:25 +msgid "Software used (Single selection field, not mandatory, not shown)" msgstr "" -#: ../system/integrations/i-doit.rst:115 -msgid "Username / Password" +#: ../system/core-workflows/learn-by-example.rst:68 +msgid "Group specific values and fields" msgstr "" -#: ../system/integrations/i-doit.rst:107 -msgid "Login credentials for a Zammad agent." +#: ../system/core-workflows/learn-by-example.rst:28 +msgid "" +"This workflow set depends on the category field. It reduces the available " +"set of values based on the group selected." msgstr "" -#: ../system/integrations/i-doit.rst:109 -msgid "" -"This agent must have **read permission** for all :doc:`groups ` that plan on using the i-doit integration." +#: ../system/core-workflows/learn-by-example.rst:33 +msgid "Workflow 2nd Level group" msgstr "" -#: ../system/integrations/i-doit.rst:113 +#: ../system/core-workflows/learn-by-example.rst:35 msgid "" -"You may even wish to create a dedicated agent account just for this " -"integration (otherwise, if the agent ever changes her password, you will " -"have to remember to update it here)." +"This reduces the category options to ``2nd Level/*``, ``Internal/*`` and " +"``Others``. It also sets further required fields to mandatory and visible." msgstr "" -#: ../system/integrations/i-doit.rst:117 -msgid "URL incl. protocol" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for 2nd level" msgstr "" -#: ../system/integrations/i-doit.rst:118 -msgid "``https://your.zammad.domain``" +#: ../system/core-workflows/learn-by-example.rst:43 +msgid "Workflow Support group" msgstr "" -#: ../system/integrations/index.rst:2 -msgid "Integrations" -msgstr "Integrações" - -#: ../system/integrations/index.rst:4 +#: ../system/core-workflows/learn-by-example.rst:45 msgid "" -"Zammad offers numerous integrations that add rich features to your instance." +"This reduces the category options to ``Support/*``, ``Internal/*`` and " +"``Others``. It also sets further required fields to visible." msgstr "" -"Zammad oferece inúmeras integrações e funcionalidades para sua instância." -#: ../system/integrations/index.rst:6 -msgid "We're still working on this part of our documentation, stay tight!" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for support" msgstr "" -"Ainda estamos trabalhando nesta parte da nossa documentação, aguente firme!" - -#: ../system/integrations/index.rst:10 -#, fuzzy -msgid "Integrations for Phone Systems" -msgstr "Integrações para sistemas de telefonia" -#: ../system/integrations/index.rst:14 -msgid "" -"Your VoIP provider or telephony system is not listed? Possibly your provider " -"supports Zammad by using the generic CTI - if you're unsure ask your " -"provider." +#: ../system/core-workflows/learn-by-example.rst:53 +msgid "Workflow Sales group" msgstr "" -#: ../system/integrations/index.rst:18 +#: ../system/core-workflows/learn-by-example.rst:55 msgid "" -"Provider does not support Zammad? Consider creating a `feature request in " -"the Zammad Community `_." +"This reduces the category options to ``Sales/*``, ``Internal/*`` and " +"``Others``." msgstr "" -#: ../system/integrations/index.rst:31 -#, fuzzy -msgid "Integrations for Authentication and Customers" -msgstr "Integrações para autenticação e clientes" - -#: ../system/integrations/index.rst:44 -msgid "Integrations for Monitoring Systems" -msgstr "Integrações para Sistemas de Monitoramento" - -#: ../system/integrations/index.rst:46 -msgid "This section currently misses the following integrations:" -msgstr "Esta sessão atualmente carece das seguintes integrações:" - -#: ../system/integrations/index.rst:48 -msgid "Icinga" -msgstr "Icinga" - -#: ../system/integrations/index.rst:49 -msgid "Monit" -msgstr "Monit" - -#: ../system/integrations/index.rst:50 -msgid "Nagios" -msgstr "Nagios" - -#: ../system/integrations/index.rst:60 -msgid "Integrations for Issue Trackers" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for sales" msgstr "" -#: ../system/integrations/index.rst:70 -msgid "Other Integrations" -msgstr "Outras Integrações" - -#: ../system/integrations/index.rst:72 -msgid "" -"This section will hold any other integration that can't be grouped up (yet)." +#: ../system/core-workflows/learn-by-example.rst:68 +#: ../system/integrations/slack.rst:88 +msgid "The Result" msgstr "" -"Esta sessão armazenará todas as outras integrações que não puderam ser " -"agrupadas (ainda)." - -#: ../system/integrations/ldap/index.rst:2 -msgid "LDAP / Active Directory" -msgstr "LDAP / Active Directory" -#: ../system/integrations/ldap/index.rst:4 +#: ../system/core-workflows/learn-by-example.rst:63 msgid "" -"Zammad comes with a powerful LDAP integration that allows you to have a " -"single source of truth. By this you reduce the number of login credentials " -"your user has to remember." +"This is what the agent would experience with the above workflows in place." msgstr "" -#: ../system/integrations/ldap/index.rst:10 +#: ../system/core-workflows/learn-by-example.rst:0 msgid "" -"The LDAP source is also a perfect candidate for Zammad's :docs:`Kerberos " -"Single Sign-On ` but also works as addition " -"to other :doc:`/settings/security/third-party`." +"Workflow shows objects and limits options based on selections on the group" msgstr "" -#: ../system/integrations/ldap/index.rst:None -msgid "Zammands LDAP management page" +#: ../system/core-workflows/learn-by-example.rst:90 +msgid "Approval process" msgstr "" -#: ../system/integrations/ldap/index.rst:25 -msgid "📝 :doc:`manage`" +#: ../system/core-workflows/learn-by-example.rst:71 +msgid "" +"In this case ``approved`` is visible to agents by default. For this " +"workflow, an additional role ``Approval person`` is required (no further " +"permissions)." msgstr "" -#: ../system/integrations/ldap/index.rst:25 -msgid "Add, modify, remove or re-arrange your LDAP-Sources as needed." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that restricts an approval attribute to specific roles" msgstr "" -#: ../system/integrations/ldap/index.rst:30 -#, fuzzy -msgid "Before you continue, please note the following limitations." -msgstr "Lá você poderá editar as seguintes configurações:" - -#: ../system/integrations/ldap/index.rst:32 -msgid "Mapping / Synchronizing organizations is not possible" +#: ../system/core-workflows/learn-by-example.rst:81 +msgid "" +"This workflow may work best in combination with a :doc:`trigger ` but technically, this is not required." msgstr "" -#: ../system/integrations/ldap/index.rst:36 +#: ../system/core-workflows/learn-by-example.rst:84 msgid "" -"You may want to consider using domain based assignments to overcome this " -"issue. Learn more on :doc:`/manage/organizations/index`." +"Select fields may be a better approach because they allow more values than " +"just a simple ``true`` or ``false``." msgstr "" -#: ../system/integrations/ldap/index.rst:39 +#: ../system/core-workflows/learn-by-example.rst:0 msgid "" -"Zammad's LDAP sync is one way. Editing user settings or permissions may be " -"overwritten upon the next sync depending on your configuration." +"Workflow fixes possible values of \"Approved ?\" to a specific selection " +"depending on the users role" msgstr "" -#: ../system/integrations/ldap/index.rst:41 -msgid "Nested groups are not supported." +#: ../system/core-workflows/learn-by-example.rst:103 +msgid "State dependent mandatory fields" msgstr "" -#: ../system/integrations/ldap/index.rst:42 -msgid "Synchronizing user avatars from LDAP is not supported." +#: ../system/core-workflows/learn-by-example.rst:93 +msgid "" +"This workflow sets ``Category`` to mandatory if the agent wants to set the " +"states ``closed`` or ``pending close`` to enforce categorization." msgstr "" -#: ../system/integrations/ldap/index.rst:43 -msgid "Unlike user filters, group filters cannot be changed." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that sets fields to mandatory on specific states" msgstr "" -#: ../system/integrations/ldap/index.rst:44 +#: ../system/core-workflows/learn-by-example.rst:0 msgid "" -"When a user originates from an LDAP server, Zammad will try to verify the " -"login credentials against LDAP first - if this fails Zammad will check its " -"local database." +"Workflow sets category field to mandatory upon choosing closed or pending " +"close as state" msgstr "" -#: ../system/integrations/ldap/index.rst:50 -msgid "" -"Users can have local passwords even if they're LDAP users! You can learn " -"more about user accounts in general on :doc:`/manage/users/index`." +#: ../system/core-workflows/learn-by-example.rst:106 +msgid "Manual Ticket Handover Process" msgstr "" -#: ../system/integrations/ldap/index.rst:54 -msgid "" -"When several LDAP sources contain the same user (meaning the same email " -"address), the user in question will be updated with every source configured. " -"*The last LDAP source will win.*" +#: ../system/core-workflows/learn-by-example.rst:108 +msgid "This example covers the handover of a ticket from one agent to another:" msgstr "" -#: ../system/integrations/ldap/index.rst:58 +#: ../system/core-workflows/learn-by-example.rst:110 msgid "" -"This is subject to change with `Issue 4109 `_ in the future." +"When the ticket owner is modified, a new text field (\"Handover\") shows up " +"for a comment" msgstr "" -#: ../system/integrations/ldap/index.rst:60 +#: ../system/core-workflows/learn-by-example.rst:112 msgid "" -"Synchronization statistics currently affect *all* configured LDAP sources. " -"This also applies for newly added or updated sources." +"This may only be visible when the owner is changed, therefore it has to be " +"hidden in general" msgstr "" -#: ../system/integrations/ldap/index.rst:63 -msgid "" -"This is subject to change with `Issue 4108 `_ in the future." +#: ../system/core-workflows/learn-by-example.rst:114 +msgid "The input in this handover text field is mandatory" msgstr "" -#: ../system/integrations/ldap/index.rst:65 +#: ../system/core-workflows/learn-by-example.rst:115 msgid "" -"Zammad currently has limited fallback server support. You can workaround " -"this by providing several sources - however, ensure to have the exact same " -"configuration on your fallback." +"After submitting changes, the value of the handover field must be added as " +"an note to the ticket (via trigger)" msgstr "" -#: ../system/integrations/ldap/index.rst:69 -msgid "" -"This is subject to improve with `Issue 4107 `_ in the future." +#: ../system/core-workflows/learn-by-example.rst:121 +msgid "Hiding handover field" msgstr "" -#: ../system/integrations/ldap/index.rst:76 -msgid "" -"This section holds all requests Zammad handled for all LDAP sources. These " -"entries can either contain synchronization information or logins " -"(authentication attempts via Zammad's login interface)." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Hiding the handover field in core workflows" msgstr "" -#: ../system/integrations/ldap/index.rst:80 -msgid "" -"By clicking on any request, Zammad will provide even more information. The " -"provided information can be useful when something does not work as expected." +#: ../system/core-workflows/learn-by-example.rst:126 +msgid "Showing handover field and setting it to mandatory" msgstr "" -#: ../system/integrations/ldap/index.rst:85 -msgid "" -"Especially a LDAP synchronization can cause many log entries. The web " -"interface will always limit the number of shown entries to the last 50 " -"entries." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Showing the handover field and set it as mandatory" msgstr "" -#: ../system/integrations/ldap/index.rst:None -msgid "" -"Screencast showing LDAP integration log entries and a detail view on\n" -"an entry." +#: ../system/core-workflows/learn-by-example.rst:131 +msgid "Trigger writing handover input to a new article" msgstr "" -#: ../system/integrations/ldap/manage.rst:2 -msgid "Manage LDAP-Sources" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Write handover content to a new article" msgstr "" -#: ../system/integrations/ldap/manage.rst:6 +#: ../system/core-workflows/learn-by-example.rst:133 msgid "" -"Please keep in mind all current limitations for the LDAP synchronization. " -"This will help to understand scopes of the following operations better." +"As a result, the ticket includes an article of the type note which includes " +"the predefined text and the handover comment." msgstr "" -#: ../system/integrations/ldap/manage.rst:65 -msgid "Add new source" +#: ../system/core-workflows/limitations.rst:6 +msgid "Core Workflows do not replace Triggers" msgstr "" -#: ../system/integrations/ldap/manage.rst:10 +#: ../system/core-workflows/limitations.rst:5 msgid "" -"Using the *New Source* button allows you to add new LDAP sources to your " -"installation. You're not limited in the number of sources, however, keep in " -"mind that many sources will also take more time to synchronize." +"Workflows manipulate the behavior of fields. However, they do not set values " +"in fields because of actions." msgstr "" -#: ../system/integrations/ldap/manage.rst:14 -msgid "" -"You can choose between different encryption types, namely *SSL* and " -"*STARTTLS* or none of them (\"*No SSL*\"). If you choose *SSL* or " -"*STARTTLS*, Zammad will display an additional *SSL verification* option that " -"allows you to disable the verification, e.g. for self-signed SSL " -"certificates. You can also tell Zammad to use a different port by appending " -"``:`` to your hostname/IP." +#: ../system/core-workflows/limitations.rst:16 +msgid "API calls are only partly affected" msgstr "" -#: ../system/integrations/ldap/manage.rst:0 +#: ../system/core-workflows/limitations.rst:9 msgid "" -"Screenshot of configuring a new LDAP source with SSL encryption and SSL " -"verification" +"Some options affect UI only and thus do not restrict responses and calls." msgstr "" -#: ../system/integrations/ldap/manage.rst:26 -msgid "" -"New Source with SSL transport security enabled and certificate verification" +#: ../system/core-workflows/limitations.rst:11 +msgid "This affects the following actions:" msgstr "" -#: ../system/integrations/ldap/manage.rst:30 -msgid "" -"Using an user filter can be a good idea if you only require a small subset " -"of your LDAP users in Zammad." +#: ../system/core-workflows/limitations.rst:13 +msgid "select" msgstr "" -#: ../system/integrations/ldap/manage.rst:42 -msgid "This especially affects inactive users" +#: ../system/core-workflows/limitations.rst:14 +msgid "auto select" msgstr "" -#: ../system/integrations/ldap/manage.rst:34 -msgid "" -"As every LDAP behaves differently on which attributes and how they are set, " -"Zammad doesn't care about any flags." +#: ../system/core-workflows/limitations.rst:15 +msgid "show" msgstr "" -#: ../system/integrations/ldap/manage.rst:37 +#: ../system/core-workflows/limitations.rst:16 +msgid "hide" +msgstr "" + +#: ../system/core-workflows/limitations.rst:25 +msgid "Some fields stay unavailable to customers" +msgstr "" + +#: ../system/core-workflows/limitations.rst:19 msgid "" -"Users that no longer are returned by your LDAP source will automatically be " -"set to inactive. Zammad assumes that the user was deactivated." +"For technical and security reasons, some default fields (the pale ones you " +"can't edit) stay unavailable for display and usage on customer permissions." msgstr "" -#: ../system/integrations/ldap/manage.rst:41 +#: ../system/core-workflows/limitations.rst:23 msgid "" -"Users will never be removed automatically! If you want to remove obsolete " -"users, use :doc:`/system/data-privacy`." +"If you require your customers to change e.g. priorities, please consider " +"using workarounds via :doc:`/system/objects` and :doc:`/manage/trigger`." msgstr "" -#: ../system/integrations/ldap/manage.rst:46 -#, fuzzy -msgid "Active Directory admins" -msgstr "LDAP / Active Directory" +#: ../system/core-workflows/limitations.rst:29 +msgid "Ticket title changes not supported in edit mask" +msgstr "" -#: ../system/integrations/ldap/manage.rst:45 +#: ../system/core-workflows/limitations.rst:28 msgid "" -"Active Directories are quite specific on how to filter for active users only " -"- please see the `Microsoft documentation `_ for more " -"information." +"It is currently not possible to perform changes of the ticket title in the " +"edit mask (e.g. renaming, set to read-only)." msgstr "" -#: ../system/integrations/ldap/manage.rst:51 -msgid "" -"*Do not* manually write pathes of either LDAP attributes or groups. If " -"Zammad does not display them, it either cannot find them or you have a lot " -"of users that don't have the attributes populated." +#: ../system/core-workflows/limitations.rst:37 +msgid "What is out of scope of Core Workflows?" msgstr "" -#: ../system/integrations/ldap/manage.rst:55 +#: ../system/core-workflows/limitations.rst:32 msgid "" -"Zammad will always only return attributes that are filled - this reduces the " -"returned list of attributes greatly." +"There are some things that would count as workflow but are either done via :" +"doc:`/manage/trigger` or :doc:`/manage/scheduler`." msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing how to add a new LDAP source" +#: ../system/core-workflows/limitations.rst:35 +msgid "Such as (but not limited to):" msgstr "" -#: ../system/integrations/ldap/manage.rst:63 -msgid "" -"If your LDAP system doesn't allow anonymous bind, Zammad detects it and " -"provides you an editable \"Base DN\" *text* field instead of a prefilled " -"*select* field." +#: ../system/core-workflows/limitations.rst:37 +msgid "up- or downgrade permissions of users" msgstr "" -#: ../system/integrations/ldap/manage.rst:81 -msgid "Review or edit existing source" +#: ../system/core-workflows/limitations.rst:38 +msgid "affecting article creation or listing" msgstr "" -#: ../system/integrations/ldap/manage.rst:68 -msgid "" -"Clicking on a LDAP source will provide a configuration and mapping overview." +#: ../system/data-privacy.rst:2 +msgid "Data Privacy" msgstr "" -#: ../system/integrations/ldap/manage.rst:70 +#: ../system/data-privacy.rst:4 msgid "" -"If needed you can then use the *Change* button to update either the name, " -"active state or the whole configuration. If you're changing the whole " -"configuration, the dialogue will be identical to the source creation." +"For compliance with GDPR and other data privacy laws, you may wish to " +"**permanently delete users from the system**, along with **all of their " +"associated tickets**." msgstr "" -#: ../system/integrations/ldap/manage.rst:76 +#: ../system/data-privacy.rst:8 msgid "" -"Did your LDAP server change? Different LDAP servers have different " -"structures and default attributes. This causes the LDAP synchronization to " -"likely fail. Consider removing the affected source and re-add it." +"You can create manual deletion tasks or even automated deletion tasks for " +"tickets and users based on custom conditions via :doc:`scheduler `!" msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing the update of the source name." +#: ../system/data-privacy.rst:12 +msgid "" +"Access to this panel requires ``admin.data_privacy`` permissions (introduced " +"in Zammad 3.5)." msgstr "" -#: ../system/integrations/ldap/manage.rst:89 -msgid "Re-arrange LDAP source's order" +#: ../system/data-privacy.rst:15 +msgid "" +"On older systems that have not been updated yet, customers can also be :docs:" +"`deleted via the Zammad console `." msgstr "" -#: ../system/integrations/ldap/manage.rst:84 -msgid "" -"You can change the synchronization order for each source at any time. Zammad " -"will synchronize the sources from top to bottom." +#: ../system/data-privacy.rst:22 +msgid "User deletion dialog in the Data Privacy panel" msgstr "" -#: ../system/integrations/ldap/manage.rst:0 +#: ../system/data-privacy.rst:22 msgid "" -"Screencasting showing how to change the source order by using\n" -"drag and drop." +"The user deletion dialog lists some of the tickets that will be removed from " +"the system along with the user." msgstr "" -#: ../system/integrations/ldap/manage.rst:101 -msgid "Remove a source" +#: ../system/data-privacy.rst:27 +#, fuzzy +msgid "Deleting Users via GUI" +msgstr "Limitação" + +#: ../system/data-privacy.rst:29 +msgid "🔥 **All deletions are FINAL!**" msgstr "" -#: ../system/integrations/ldap/manage.rst:92 -msgid "" -"If you no longer need the a LDAP source or simply want to start over, you " -"can remove them at any time. This will not remove synchronized users, data " -"synchronized or permissions." +#: ../system/data-privacy.rst:31 +msgid "Once you click “Delete”, the action cannot be canceled or undone." msgstr "" -#: ../system/integrations/ldap/manage.rst:98 +#: ../system/data-privacy.rst:33 msgid "" -"Not sure if you'd need the source later on? Set the source to inactive " -"instead of removing it - see *Review or edit existing source* for more." +"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." msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing how to remove LDAP sources." +#: ../system/data-privacy.rst:36 +msgid "**The following records cannot be deleted:**" msgstr "" -#: ../system/integrations/pgp/index.rst:2 -msgid "PGP" +#: ../system/data-privacy.rst:38 +msgid "your own account" msgstr "" -#: ../system/integrations/pgp/index.rst:7 -msgid "" -"Pretty Good Privacy (PGP) is another method for secure email communication. " -"With PGP, you can exchange **signed** and **encrypted** messages with others." +#: ../system/data-privacy.rst:39 +msgid "the system's last remaining administrator account" msgstr "" -#: ../system/integrations/pgp/index.rst:13 -#: ../system/integrations/smime/index.rst:17 -msgid "Signing" +#: ../system/data-privacy.rst:42 +msgid "Step 1: Find a User / Confirm Deletion" msgstr "" -#: ../system/integrations/pgp/index.rst:11 -msgid "is a proof that a message hasn't been manipulated on its way." +#: ../system/data-privacy.rst:44 +msgid "There are three ways to access the user deletion dialog:" msgstr "" -#: ../system/integrations/pgp/index.rst:13 -msgid "" -"In other words, it guarantees message **integrity** and **authenticity**." +#: ../system/data-privacy.rst:51 +msgid "**from the user's profile**" msgstr "" -#: ../system/integrations/pgp/index.rst:19 -#: ../system/integrations/smime/index.rst:22 -msgid "Encryption" +#: ../system/data-privacy.rst:0 +msgid "Accessing the user deletion dialog in a user profile" msgstr "" -#: ../system/integrations/pgp/index.rst:16 -#: ../system/integrations/smime/index.rst:20 -msgid "" -"scrambles a message so that it can only be unscrambled by the intended " -"recipient." +#: ../system/data-privacy.rst:51 +msgid "Click **Action > Delete**." msgstr "" -#: ../system/integrations/pgp/index.rst:19 -msgid "" -"In other words, it guarantees message **privacy** and **data security**." +#: ../system/data-privacy.rst:58 +msgid "**in the “Manage > Users” Admin Panel**" msgstr "" -#: ../system/integrations/pgp/index.rst:25 -msgid "Screenshot of ticket creation with encrypt and sign buttons" +#: ../system/data-privacy.rst:0 +msgid "Accessing the user deletion dialog under “Users” in the Admin Panel" msgstr "" -#: ../system/integrations/pgp/index.rst:25 -msgid "" -"Once PGP has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " -"appear in the ticket composer." +#: ../system/data-privacy.rst:58 +msgid "Use the **⋮ Actions** menu for the target user." msgstr "" -#: ../system/integrations/pgp/index.rst:28 -msgid "**Sign button not visible?**" +#: ../system/data-privacy.rst:66 ../system/data-privacy.rst:104 +msgid "**in the “System > Data Privacy” Admin Panel**" msgstr "" -#: ../system/integrations/pgp/index.rst:30 +#: ../system/data-privacy.rst:0 msgid "" -"Please note that the signing of emails is based on the outgoing email " -"account. That means you have to choose a group with a sender email account, " -"which has a private key assigned." +"Accessing the user deletion dialog under “Data Privacy” in the Admin Panel" msgstr "" -#: ../system/integrations/pgp/index.rst:35 -msgid "Handling of Keys" +#: ../system/data-privacy.rst:65 +msgid "" +"Use the **New Deletion Task** button. Search for users by name or email " +"address." msgstr "" -#: ../system/integrations/pgp/index.rst:36 +#: ../system/data-privacy.rst:79 +#, fuzzy +msgid "**Delete organizations**" +msgstr "Organizações" + +#: ../system/data-privacy.rst:69 msgid "" -"To use the PGP function, you have to enable the integration (PGP) by " -"switching the toggle to *enabled*." +"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:" msgstr "" -#: ../system/integrations/pgp/index.rst:39 +#: ../system/data-privacy.rst:0 +msgid "Deleting an organization via the user deletion dialog" +msgstr "" + +#: ../system/data-privacy.rst:78 msgid "" -"You can add keys by clicking the *add key* button. The keys can be imported " -"from a file or you can paste the content of the key in the text box." +"If this option does not appear, make sure there are no pending deletion " +"tasks for other customers from this organization." msgstr "" -#: ../system/integrations/pgp/index.rst:42 -msgid "**Which keys do I have to import?**" +#: ../system/data-privacy.rst:82 +msgid "Step 2: Monitor Deletion Job Status" msgstr "" -#: ../system/integrations/pgp/index.rst:44 +#: ../system/data-privacy.rst:84 msgid "" -"For **signing** *outgoing* emails, you have to import the private key of " -"your Zammad email account." +"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:" msgstr "" -#: ../system/integrations/pgp/index.rst:47 -msgid "" -"For **encrypting** *outgoing* emails, you have to import the public key of " -"the customer's email account." +#: ../system/data-privacy.rst:98 +msgid "**in the Activity Stream**" msgstr "" -#: ../system/integrations/pgp/index.rst:50 +#: ../system/data-privacy.rst:0 +msgid "Activity Stream showing data privacy tasks" +msgstr "" + +#: ../system/data-privacy.rst:94 msgid "" -"For **verifying the signature** of signed *incoming* emails, you have to " -"import the public key of the customer." +"For each deleted user, the Activity Stream will be updated twice—once when " +"the task is created, and once when it's complete." msgstr "" -#: ../system/integrations/pgp/index.rst:53 +#: ../system/data-privacy.rst:97 msgid "" -"For **decrypting** of encrypted *incoming* emails, you have to import the " -"private key of your Zammad email account." +"These notifications are only visible to users with ``admin.data_privacy`` " +"permissions." msgstr "" -#: ../system/integrations/pgp/index.rst:57 -msgid "Import Keys From a File" +#: ../system/data-privacy.rst:0 +msgid "" +"The task list within Data Privacy shows removals being in progress and " +"completed." msgstr "" -#: ../system/integrations/pgp/index.rst:58 -msgid "You can import keys from a file in the section **Upload key**:" +#: ../system/data-privacy.rst:107 +msgid "Frequently Asked Questions" msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of adding a key via file" +#: ../system/data-privacy.rst:121 +msgid "What happens if I receive an email from a deleted customer?" msgstr "" -#: ../system/integrations/pgp/index.rst:64 +#: ../system/data-privacy.rst:110 msgid "" -"**Supported file formats:** ASCII-armor as well as binary GPG format " -"(basically any GPG supported key format) is supported here." +"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/integrations/pgp/index.rst:68 -msgid "Import Keys by Pasting the Content" +#: ../system/data-privacy.rst:115 +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**." msgstr "" -#: ../system/integrations/pgp/index.rst:69 -msgid "You can also paste the key's content in the section **paste key**:" +#: ../system/data-privacy.rst:130 +msgid "What about user information stored in internal notes or other messages?" msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of adding a key via pasting" +#: ../system/data-privacy.rst:124 +msgid "" +"The deletion process removes **user accounts and associated tickets only**." msgstr "" -#: ../system/integrations/pgp/index.rst:75 +#: ../system/data-privacy.rst:126 msgid "" -"**Supported format:** Please note that only ASCII-armor is supported here." +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:78 -#, fuzzy -msgid "Deleting Keys" -msgstr "Limitação" +#: ../system/data-privacy.rst:137 +msgid "I deleted an user and can still see a message they sent!" +msgstr "" -#: ../system/integrations/pgp/index.rst:79 +#: ../system/data-privacy.rst:133 msgid "" -"If you want to delete a specific key, you can do it by clicking on the menu " -"in the *actions* column and select **delete**:" +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of deleting a key" +#: ../system/data-privacy.rst:141 +msgid "I removed a customer, now my reporting is off!" msgstr "" -#: ../system/integrations/pgp/index.rst:88 -msgid "Downloading Keys" +#: ../system/data-privacy.rst:140 +msgid "" +"When removing users and their tickets, all references are removed. This also " +"affects e.g. Reporting - these information are lost." msgstr "" -#: ../system/integrations/pgp/index.rst:89 +#: ../system/data-privacy.rst:145 +msgid "How long does Zammad store created tasks?" +msgstr "" + +#: ../system/data-privacy.rst:144 msgid "" -"If you want to download your keys, you can do this as well via corresponding " -"action buttons. Depending on the key, you can choose wether you want to " -"download the private or the public key." +"Please see the on-premise data section of the :docs:`data privacy ` chapter." msgstr "" -#: ../system/integrations/pgp/index.rst:95 -#: ../system/integrations/smime/manage-certificates.rst:76 -msgid "Default Behavior" +#: ../system/data-privacy.rst:150 +msgid "What about re-assigned tickets? I want to delete them, too." msgstr "" -#: ../system/integrations/pgp/index.rst:96 +#: ../system/data-privacy.rst:148 msgid "" -"Here you can adjust on per group basis, if *sign* and *encryption* is on or " -"off by default. Please be aware, that agents can always override the setting " -"for each individual article." +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Adjusting default behavior on per group basis" +#: ../system/data-privacy.rst:154 +msgid "Why are there so many deletion task entries, I didn't create them!" msgstr "" -#: ../system/integrations/pgp/index.rst:107 +#: ../system/data-privacy.rst:153 msgid "" -"Here you can see the last actions regarding signing and encryption and if " -"they were successful." +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:117 -msgid "**Sign button is not visible, but keys are imported.**" +#: ../system/integrations/checkmk/admin-panel-reference.rst:2 +msgid "Admin Panel Reference" msgstr "" -#: ../system/integrations/pgp/index.rst:115 -msgid "Did you choose a group in the ticket?" +#: ../system/integrations/checkmk/admin-panel-reference.rst:None +msgid "Screenshot of Checkmk settings overview" msgstr "" -#: ../system/integrations/pgp/index.rst:116 +#: ../system/integrations/checkmk/admin-panel-reference.rst:12 msgid "" -"Did you import a private key for the email adress, which is used for " -"outgoing emails in the group?" +"Which :doc:`group ` should Checkmk tickets be assigned " +"to as a default (*i.e.,* when none is specified)?" msgstr "" -#: ../system/integrations/pgp/index.rst:122 -msgid "**How to obtain keys?**" +#: ../system/integrations/checkmk/admin-panel-reference.rst:15 +msgid "(Applies to :ref:`API alerts ` only.)" msgstr "" -#: ../system/integrations/pgp/index.rst:120 +#: ../system/integrations/checkmk/admin-panel-reference.rst:21 +msgid "Auto close" +msgstr "" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:18 msgid "" -"You can create them yourself! There are some good tutorials on the web on " -"how to create them. Providing keys to Zammad is a prerequisite to use the " -"PGP feature." +"Should Zammad automatically close tickets if a service has recovered on its " +"own?" msgstr "" -#: ../system/integrations/pgp/index.rst:127 -msgid "**It says a passphrase is needed, but I haven't got one.**" +#: ../system/integrations/checkmk/admin-panel-reference.rst:21 +msgid "(Agents will receive notifications for such closures as appropriate.)" msgstr "" -#: ../system/integrations/pgp/index.rst:125 -msgid "" -"If the key is secured with a passphrase, you have to provide it for the " -"import in Zammad. It is possible that keys may have an empty passphrase. " -"However, this is *not* recommended." +#: ../system/integrations/checkmk/admin-panel-reference.rst:30 +msgid "Auto-close state" msgstr "" -#: ../system/integrations/pgp/index.rst:132 -msgid "**How do my customers get my new key?**" +#: ../system/integrations/checkmk/admin-panel-reference.rst:24 +msgid "What ticket state should be applied when “auto-closing” a ticket?" msgstr "" -#: ../system/integrations/pgp/index.rst:130 +#: ../system/integrations/checkmk/admin-panel-reference.rst:26 msgid "" -"You have to provide your **public** key in advance. Your customer also has " -"to configure PGP in their email workflow and import your public key. The " -"other way round, you have to get the public key of your customer and have to " -"import it to Zammad." +"You can choose from the seven built-in ticket states. If these states aren't " +"enough for you, you can :ref:`define a new ticket state ` for this purpose as well. This can be useful for tracking " +"tickets with :doc:`reports `, for example." msgstr "" -#: ../system/integrations/slack.rst:2 -msgid "Slack" -msgstr "Slack" +#: ../system/integrations/checkmk/admin-panel-reference.rst:35 +#: ../system/integrations/cti/includes/recent-logs.include.rst:2 +#: ../system/integrations/ldap/index.rst:74 +#: ../system/integrations/pgp/index.rst:106 +msgid "Recent Logs" +msgstr "" -#: ../system/integrations/slack.rst:4 -msgid "**⚠️ Deprecation warning ⚠️**" +#: ../system/integrations/checkmk/admin-panel-reference.rst:None +msgid "Screenshot of Checkmk \"Recent Logs\" section" msgstr "" -#: ../system/integrations/slack.rst:6 +#: ../system/integrations/checkmk/admin-panel-reference.rst:41 msgid "" -"Zammad 7 will no longer support this dedicated Slack integration. It is " -"recommended to switch to :doc:`pre-defined webhooks ` instead. Existing Slack integrations should " -"be migrated manually before this feature is dropped." +"If you're having trouble getting Zammad and Checkmk to play nicely together, " +"this section can help you troubleshoot." msgstr "" -#: ../system/integrations/slack.rst:14 +#: ../system/integrations/checkmk/admin-panel-reference.rst:44 msgid "" -"In order to use this feature, please add a new Slack app to your Workspace. " -"The App you need is called ``Incoming WebHooks`` ." +"It contains a record of the fifty most recent transactions that Zammad knows " +"about, including each one's request/response details and return status." msgstr "" -#: ../system/integrations/slack.rst:18 -#, fuzzy -msgid "Why Do I Need This Feature?" -msgstr "Porque eu preciso desta funcionalidade?" - -#: ../system/integrations/slack.rst:20 -msgid "" -"If you're already using Slack for your team communication, you'll love this " -"feature! Our Slack integration can push ticket notifications about the last " -"ticket article based on the following events:" +#: ../system/integrations/checkmk/api-reference.rst:2 +msgid "API Reference" msgstr "" -#: ../system/integrations/slack.rst:24 -msgid "on Ticket creation" -msgstr "na criação do Chamado" - -#: ../system/integrations/slack.rst:25 -msgid "on Ticket updates" +#: ../system/integrations/checkmk/api-reference.rst:4 +msgid "" +"For most users, :ref:`the sample scripts from the Setup Guide ` will do the job just fine. But if you want more fine-grained control" +"—for instance, to create high- and low-priority tickets for different types " +"of system events—then you'll have to customize the data those scripts send " +"to Zammad." msgstr "" -#: ../system/integrations/slack.rst:26 -msgid "on reached reminders" +#: ../system/integrations/checkmk/api-reference.rst:15 +msgid "" +"This custom script will automatically set all tickets it creates to **high " +"priority** and **assign them to charlie@chrispresso.com**." msgstr "" -#: ../system/integrations/slack.rst:27 -msgid "a Ticket has escalated" -msgstr "o Chamado foi escalonado" +#: ../system/integrations/checkmk/api-reference.rst:32 +#, fuzzy +msgid "How Does it Work?" +msgstr "Funciona desta forma:" -#: ../system/integrations/slack.rst:28 -msgid "a Ticket is going to escalate" +#: ../system/integrations/checkmk/api-reference.rst:34 +msgid "" +"There are two kinds of data you can pass to the API, both in the form of key-" +"value pairs:" msgstr "" -#: ../system/integrations/slack.rst:30 -msgid "" -"Zammad will provide the Ticket title, a direct link to the Ticket, the event " -"type (creation, updated, escalation), the customer, time and the last " -"article that has triggered the notification." +#: ../system/integrations/checkmk/api-reference.rst:44 +msgid "Checkmk parameters" msgstr "" -#: ../system/integrations/slack.rst:34 +#: ../system/integrations/checkmk/api-reference.rst:38 msgid "" -"This will give you further options, as you can see e.g. escalating tickets " -"that are assigned to an agent that's e.g. absent. You can interact faster, " -"as you might see problems earlier (or even before the problem gets one)." +"are required, and make up the **contents** of the resulting tickets/" +"articles. They also determine whether an event creates a new ticket or " +"updates/closes an existing one." msgstr "" -#: ../system/integrations/slack.rst:38 +#: ../system/integrations/checkmk/api-reference.rst:42 msgid "" -"If needed and wanted, you can even discuss directly about the topic before " -"sending an answer to the customer. Another possible use case would be a " -"agent monitoring new agents and their answers to tickets." +"These are the only values used in the sample scripts. **Use them as-is**; " +"technically, they can be customized, but it's hard to imagine a good reason " +"for it." msgstr "" -#: ../system/integrations/slack.rst:44 -#, fuzzy -msgid "Configure the Integration" -msgstr "Configure a integração" +#: ../system/integrations/checkmk/api-reference.rst:52 +msgid "Ticket attributes" +msgstr "Atributos do ticket" -#: ../system/integrations/slack.rst:46 +#: ../system/integrations/checkmk/api-reference.rst:47 msgid "" -"First of all, please go to your slack workspace - go to administration => " -"Manage Apps. If you don't have an app yet, you can simply add a new one - " -"just search for ``Incoming WebHooks`` and customize the app to your needs." +"are optional, and can be used to **adjust settings** on newly created " +"tickets (*e.g.,* set the owner, group, priority, or state)." msgstr "" -#: ../system/integrations/slack.rst:50 +#: ../system/integrations/checkmk/api-reference.rst:50 msgid "" -"Choose (or create) the channel Zammad should post it's information to and " -"press on \"Add Incoming WebHooks integration\". If you're ready, copy the " -"provided WebHook URL and go to your Zammad installation." +"If you want to customize your Checkmk alert script, do it with these. Simply " +"add an extra “form” option for each one (``-F \"key=value\"``) to your " +"script's ``curl`` command line, as in the example above." msgstr "" -#: ../system/integrations/slack.rst:56 -msgid "" -"You need administrative rights on the Slack Workspace. The link to the app " -"directory is normally ``https://[workspace-name].slack.com/apps`` ." +#: ../system/integrations/checkmk/api-reference.rst:54 +msgid "💡 **It's just an API endpoint!**" msgstr "" -#: ../system/integrations/slack.rst:63 +#: ../system/integrations/checkmk/api-reference.rst:56 msgid "" -"To configure the slack integration, log in to Zammad and go to Integrations " -"(System) => Slack in the admin panel." +"When using Checkmk integration, messages need to be formatted in a certain " +"way, but that *doesn't mean the messages actually have to come from Checkmk*." msgstr "" -#: ../system/integrations/slack.rst:66 +#: ../system/integrations/checkmk/api-reference.rst:59 msgid "" -"Here you can choose on what evens Zammad should post information about a " -"ticket to your Slack channel. Next you need to device what groups shall be " -"affected by this, as anybody with access to that specific Slack channel can " -"read at least parts of the ticket this might be a privacy issue, if you " -"select the wrong groups. The username is simply the name that Zammad uses as " -"display name inside the Slack chat. The channel defines the Slack channel " -"the information is being posted in. As last option, you can set a custom " -"icon for posting to slack." +"If you use another monitoring tool that's not officially supported by " +"Zammad, there's probably a way to make it work with your Checkmk callback " +"URL." msgstr "" -#: ../system/integrations/slack.rst:74 -msgid "" -"When you're ready, just hit \"Submit\" and enable the integration. Zammad " -"will now post new ticket information based on the trigger you chose. Below " -"the options you have the recent log that shows the latest requests to Slack " -"for debugging if needed." +#: ../system/integrations/checkmk/api-reference.rst:63 +msgid "Checkmk Parameters" msgstr "" -#: ../system/integrations/slack.rst:81 +#: ../system/integrations/checkmk/api-reference.rst:65 msgid "" -"If you leave the Icon URL empty, Zammad will use the Zammad logo instead. " -"The icon should be a square PNG file." +"When a notification is received, Zammad creates a new article containing the " +"details of the event that triggered it:" msgstr "" -#: ../system/integrations/slack.rst:90 -msgid "" -"The following figure shows how it will look if you choose to receive updates " -"on created and updated tickets. On every post Zammad sends to the Slack " -"channel, you can create new threads to discuss about the new article." +#: ../system/integrations/checkmk/api-reference.rst:None +msgid "Checkmk article body" msgstr "" -#: ../system/integrations/slack.rst:96 +#: ../system/integrations/checkmk/api-reference.rst:72 msgid "" -"If you just want to keep track of soon escalating or already escalated " -"tickets, it will look the the following figure. Zammad changes the color in " -"front of the post so you can easily see the state of the ticket." +"These details come from the fields listed below, which correspond to " +"parameters provided by Checkmk (``$NOTIFY_*``)." msgstr "" -#: ../system/integrations/slack.rst:102 -msgid "" -"If you change the state, Zammad will also put information on what state the " -"ticket gets and (if pending state) the date until it pends. You'll also " -"recognize the color codes in front of posts on slack, as they are exact the " -"same the ticket state colors you'll see in Zammad!" +#: ../system/integrations/checkmk/api-reference.rst:75 +msgid "**Required fields are marked with an asterisk (\\*).**" msgstr "" -#: ../system/integrations/smime/index.rst:2 -msgid "S/MIME" +#: ../system/integrations/checkmk/api-reference.rst:79 +msgid "event_id\\*" msgstr "" -#: ../system/integrations/smime/index.rst:11 +#: ../system/integrations/checkmk/api-reference.rst:78 msgid "" -"S/MIME is the most widely-supported method for secure email communication. " -"With S/MIME, you can exchange **signed** and **encrypted** messages with " -"others." +"A unique ID for the system event. (``$NOTIFY_SERVICEPROBLEMID`` / " +"``$NOTIFY_HOSTPROBLEMID``)" msgstr "" -#: ../system/integrations/smime/index.rst:15 -msgid "" -"is proof that a message hasn't been tampered with or sent by an impersonator." +#: ../system/integrations/checkmk/api-reference.rst:86 +msgid "host\\*" msgstr "" -#: ../system/integrations/smime/index.rst:17 +#: ../system/integrations/checkmk/api-reference.rst:82 msgid "" -"In other words, it guarantees a message's **integrity** and **authenticity**." -msgstr "" - -#: ../system/integrations/smime/index.rst:22 -msgid "In other words, it guarantees **privacy** and **data security**." -msgstr "" - -#: ../system/integrations/smime/index.rst:28 -msgid "Screencast demo of S/MIME features for both new tickets and replies" +"The hostname of the system that the event originated from. " +"(``$NOTIFY_HOSTNAME``)" msgstr "" -#: ../system/integrations/smime/index.rst:28 +#: ../system/integrations/checkmk/api-reference.rst:85 msgid "" -"Once S/MIME has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " -"appear in the ticket composer." +"Used to determine if a new event belongs to an existing ticket. Also used in " +"the subject line of the resulting article (“ is ”)." msgstr "" -#: ../system/integrations/smime/index.rst:32 -msgid ":doc:`🔪 Prerequisites `" +#: ../system/integrations/checkmk/api-reference.rst:96 +msgid "service" msgstr "" -#: ../system/integrations/smime/index.rst:31 +#: ../system/integrations/checkmk/api-reference.rst:89 msgid "" -"New to S/MIME? This section helps you to find certificate providers and " -"points out Limitations." +"The name of the service that the event originated from. " +"(``$NOTIFY_SERVICEDESC``)" msgstr "" -#: ../system/integrations/smime/index.rst:35 -msgid ":doc:`📝 Manage Certificates `" +#: ../system/integrations/checkmk/api-reference.rst:92 +msgid "Used to determine if a new event belongs to an existing ticket." msgstr "" -#: ../system/integrations/smime/index.rst:35 -msgid "Add and download certificates; configure group default behaviors." +#: ../system/integrations/checkmk/api-reference.rst:94 +#: ../system/integrations/checkmk/api-reference.rst:110 +msgid "Displayed as ``-`` when omitted." msgstr "" -#: ../system/integrations/smime/index.rst:38 -msgid ":doc:`😦 Troubleshooting `" +#: ../system/integrations/checkmk/api-reference.rst:104 +msgid "state\\*" msgstr "" -#: ../system/integrations/smime/index.rst:38 -msgid "Took a wrong turn? About recent logs and common issues." +#: ../system/integrations/checkmk/api-reference.rst:99 +msgid "" +"The current state of the service or host in question. " +"(``$NOTIFY_SERVICESTATE`` / ``$NOTIFY_HOSTSTATE``)" msgstr "" -#: ../system/integrations/smime/index.rst:43 +#: ../system/integrations/checkmk/api-reference.rst:102 msgid "" -"For more details on how S/MIME integration works on the agent side, see the :" -"user-docs:`user docs `." +"Used to detect when a ticket should be auto-closed (*i.e.,* on ``OK``/" +"``UP``). Also used in the subject line of the resulting article (“ is " +"”)." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:2 -msgid "Manage Certificates" +#: ../system/integrations/checkmk/api-reference.rst:110 +msgid "text" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:4 +#: ../system/integrations/checkmk/api-reference.rst:107 msgid "" -"S/MIME is **disabled by default**. Enable it to start adding certificates." -msgstr "" - -#: ../system/integrations/smime/manage-certificates.rst:10 -msgid "Dialogue to add new certificates or private keys" +"The output of the process that triggered the event. " +"(``$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:10 +#: ../system/integrations/checkmk/api-reference.rst:121 msgid "" -"Manage certificates in the Admin Panel under **System > Integrations > S/" -"MIME**. Certificates may be pasted in as plain text or uploaded from a file." +"The Object Manager attribute panel displays built-in and custom\n" +"attribute names." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:14 -#, fuzzy -msgid "Add Certificate Data" -msgstr "Limitação" - -#: ../system/integrations/smime/manage-certificates.rst:36 -msgid "Add Certificate" +#: ../system/integrations/checkmk/api-reference.rst:121 +msgid "Find a complete list of ticket attributes in the Object Manager." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:17 +#: ../system/integrations/checkmk/api-reference.rst:123 msgid "" -"Import public-key certificates for both your own organization and your " -"contacts." +"Ticket attributes are entirely optional, and can be used to customize the " +"tickets that Checkmk creates. (Note that these attributes will be ignored if " +"a new event belongs to an existing ticket.)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:19 +#: ../system/integrations/checkmk/api-reference.rst:128 msgid "" -"You can also add a bunch of certificates in one go by providing a single " -"file with all relevant certificates." +"Why would you want to do this? Maybe you have only one IT guy, and all " +"system monitoring issues should be automatically assigned to him. Or, maybe " +"you're creating multiple notification rules so that database outages take " +"higher priority than disk space warnings." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:22 -msgid "🕵️ **ALWAYS verify certificates in-person or over the phone!**" +#: ../system/integrations/checkmk/api-reference.rst:135 +msgid "In most cases, you'll probably want to set one of the following:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:24 -msgid "" -"The whole point of signatures is to alert you when someone is trying to " -"pretend to be someone they're not. Never accept a certificate from someone " -"online without verifying it first." +#: ../system/integrations/checkmk/api-reference.rst:137 +msgid "group" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:28 -msgid "📇 **What about trusted certificate authorities?**" -msgstr "" +#: ../system/integrations/checkmk/api-reference.rst:139 +msgid "state" +msgstr "estado" -#: ../system/integrations/smime/manage-certificates.rst:30 -msgid "" -"In some cases (e.g. when dealing with large enterprises), you may be given a " -"certificate for an entire CA, rather than a single contact. Add it here to " -"trust *all* certificates issued by that CA." +#: ../system/integrations/checkmk/api-reference.rst:140 +msgid "priority" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:35 +#: ../system/integrations/checkmk/api-reference.rst:142 msgid "" -"Commercial CAs can usually be verified online. Zammad does not include a " -"list of built-in, trusted CAs." +"but in practice, you can set almost any attribute, including :doc:`custom " +"ones you created through the Object Manager `." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:57 -msgid "Add Private Key" -msgstr "" +#: ../system/integrations/checkmk/api-reference.rst:145 +#, fuzzy +msgid "Please note that the following attributes are **not customizable**:" +msgstr "Lá você poderá editar as seguintes configurações:" -#: ../system/integrations/smime/manage-certificates.rst:39 -msgid "" -"Once you've added a public-key certificate, you can import its matching " -"private key." -msgstr "" +#: ../system/integrations/checkmk/api-reference.rst:147 +msgid "title" +msgstr "título" -#: ../system/integrations/smime/manage-certificates.rst:42 -msgid "" -"Private keys are for **your own organization only**; never ask your contacts " -"for their private keys." +#: ../system/integrations/checkmk/api-reference.rst:148 +msgid "id" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:0 -msgid "" -"S/MIME integration showing configured certificates and possible issues with " -"Logging" +#: ../system/integrations/checkmk/api-reference.rst:149 +msgid "ticket number" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:50 -msgid "" -"A note is displayed on certificates with a matching private key (see line 2)." +#: ../system/integrations/checkmk/api-reference.rst:151 +msgid "created_by_id" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:52 -msgid "📤 **Certificates and private keys must be uploaded separately.**" +#: ../system/integrations/checkmk/api-reference.rst:152 +msgid "updated_by_id" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:54 -msgid "" -"If your certificate and private key are bundled together in the same file or " -"PEM block, import it twice (once using each button)." +#: ../system/integrations/checkmk/api-reference.rst:155 +msgid "Which Values Can Be Set?" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:57 -msgid "Please note that bulk imports of private keys are not possible." +#: ../system/integrations/checkmk/api-reference.rst:157 +msgid "😵 **Invalid values → unpredictable behavior**" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:60 -#, fuzzy -msgid "Download Certificate Data" -msgstr "Limitação" - -#: ../system/integrations/smime/manage-certificates.rst:62 +#: ../system/integrations/checkmk/api-reference.rst:159 msgid "" -"You can download the earlier provided certificates and private keys at any " -"time from your Zammad instance." +"If you provide a value that Zammad doesn't understand (*e.g.,* ``-F " +"\"priority=high\"``), it's not always clear what will happen. In some cases, " +"a ticket will be created with the default values instead - but in others, it " +"may not be created at all!" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:65 -msgid "" -"Please note that passphrase-protected private keys stay protected and when " -"you download them, you have to know the passphrase to use them after " -"downloading." +#: ../system/integrations/checkmk/api-reference.rst:164 +msgid "So what values does Zammad understand, then? Well, it depends..." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:73 -msgid "Dialogue to download certificates or private keys" +#: ../system/integrations/checkmk/api-reference.rst:168 +msgid "Use an email address or username:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:73 -msgid "Download stored certificates and their keys" +#: ../system/integrations/checkmk/api-reference.rst:190 +msgid "group & priority" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:78 -msgid "" -"The ticket composer will set all outgoing messages to **signed and " -"encrypted** by default (assuming the required certificates exist)." +#: ../system/integrations/checkmk/api-reference.rst:175 +msgid "Refer to the dropdown menus in the ticket pane:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:82 -msgid "These defaults can be modified on a per-group basis:" +#: ../system/integrations/checkmk/api-reference.rst:0 +msgid "See possible values for certain attributes in the ticket pane." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:None -msgid "Zammad allowing to choose the default behavior on per group basis" +#: ../system/integrations/checkmk/api-reference.rst:187 +msgid "🙅 **Ticket state CANNOT be set this way!**" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:89 +#: ../system/integrations/checkmk/api-reference.rst:189 msgid "" -"Of course, agents can always manually change these settings on each email " -"they send out." +"Why? Because ``-F \"state=...\"`` is already used :ref:`as a Checkmk " +"parameter `." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:4 -msgid "A certificate *and* private key for your own organization" +#: ../system/integrations/checkmk/api-reference.rst:222 +msgid "Everything Else" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:6 +#: ../system/integrations/checkmk/api-reference.rst:193 msgid "" -"(Use this to ✒️ **sign outgoing messages** and 🔓 **decrypt incoming " -"messages**.)" +"To set any other attributes, it helps to know your way around the :docs:" +"`rails console `. Valid values are those that you can " +"set with a string:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:9 -msgid "" -"Certificates belonging your contacts, or their issuing certificate authority " -"(CA)" +#: ../system/integrations/checkmk/api-reference.rst:218 +msgid "These values can then be passed directly to the API:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:11 -msgid "" -"(Use these to ✅ **verify incoming message signatures** and 🔒 **encrypt " -"outgoing messages**.)" +#: ../system/integrations/checkmk/index.rst:16 +msgid "How does it work?" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:14 -msgid "🙋 **I'm new to S/MIME. Where can I get a certificate?**" +#: ../system/integrations/checkmk/index.rst:2 +msgid "Checkmk" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:16 +#: ../system/integrations/checkmk/index.rst:4 msgid "" -"The easiest way to get certificates is to buy an annual subscription through " -"a commercial CA, such as:" +"`Checkmk `_ is a powerful IT monitoring tool that can " +"send real-time status alerts to Zammad via email or REST API. Set these " +"alerts up in Checkmk, and Zammad will automatically create, update, and " +"close tickets based on the health of your system:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:19 -msgid "" -"`Sectigo (formerly Comodo) `_" +#: ../system/integrations/checkmk/index.rst:14 +msgid "Screenshot of ticket created by Checkmk notifications" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:20 -msgid "`Secorio `_" +#: ../system/integrations/checkmk/index.rst:14 +msgid "Multiple alerts, same ticket." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:21 -msgid "`GlobalSign `_" +#: ../system/integrations/checkmk/setup-guide.rst:2 +msgid "Setup Guide" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:23 -msgid "(Zammad is not affiliated with these CAs in any way.)" +#: ../system/integrations/checkmk/setup-guide.rst:4 +msgid "" +"Whenever the Checkmk integration is enabled, Zammad listens for messages on " +"its API and over email. As long as those messages follow the required " +"format, Zammad will create new tickets (or find and update existing ones) " +"based on the message contents." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:25 +#: ../system/integrations/checkmk/setup-guide.rst:10 msgid "" -"You can also generate your own self-signed certificates, but the process is " -"complicated and usually 🙅 **involves extra work for your contacts**." +"That means that “setting up Checkmk integration” is simply a matter of " +"**adding configuration to your Checkmk site**: telling it when to send these " +"messages and what to say. To do that, you'll need to create a new " +"**notification rule** (see `Checkmk's official docs `_ for help with that)." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:29 +#: ../system/integrations/checkmk/setup-guide.rst:17 msgid "" -"Bear in mind that 🤝 **S/MIME only works if the other party is using it, too." -"**" +"As part of this new rule, you'll have to choose a **notification method** " +"(*i.e.,* a script to execute whenever the rule is triggered). This script " +"will be written by you (samples below), and contain the logic for sending " +"API/email messages to Zammad:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:32 -msgid "Certificate and Private Key Checks on Upload" +#: ../system/integrations/checkmk/setup-guide.rst:26 +msgid "Checkmk \"New Rule\" dialog" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:34 +#: ../system/integrations/checkmk/setup-guide.rst:26 msgid "" -"The certificate and public key validation is based on the ``X509v3`` " -"extensions." +"Find your custom scripts in the Checkmk WATO under **Notifications > New " +"Rule > Notification Method**." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:49 -msgid "Uploading a *client certificate*?" +#: ../system/integrations/checkmk/setup-guide.rst:29 +msgid "" +"Once you're done setting up your new rule, you're all set! New tickets " +"should start coming in and auto-updating any time your rule is triggered." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:41 -msgid "The following attributes are required then:" +#: ../system/integrations/checkmk/setup-guide.rst:33 +msgid "" +"(If you need help troubleshooting, be sure to check the :ref:`checkmk-recent-" +"logs`.)" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:39 -msgid "Subject Alternative Name (at least one email address has to be present)" +#: ../system/integrations/checkmk/setup-guide.rst:38 +msgid "API Alerts" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:40 -msgid "Key Usage (``Digital Signature`` and/or ``Key Encipherment``)" +#: ../system/integrations/checkmk/setup-guide.rst:40 +msgid "" +"To add these scripts in the Checkmk WATO, copy them into your Checkmk " +"installation directory and make them executable. (Be sure to replace the " +"``zammad.example.com`` callback URL with the one found in your admin panel.)" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:41 -msgid "Public key algorithm (either ``RSA`` or ``EC``)" +#: ../system/integrations/checkmk/setup-guide.rst:60 +msgid "Service notification" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:43 +#: ../system/integrations/checkmk/setup-guide.rst:46 msgid "" -"The Extended Key Usage attribute is optional. If the certificate provides " -"the named attribute, than it must contain the value ``E-mail Protection``." +"For updates on the status of the software running on your server (*e.g.,* " +"postgres)." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:46 -msgid "" -"Please note that any usable email adress has to be prefixed with ``email:`` " -"or ``rfc822:``." +#: ../system/integrations/checkmk/setup-guide.rst:75 +msgid "Host notification" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:49 -msgid "The named public key algorithms are mandatory for private keys as well." +#: ../system/integrations/checkmk/setup-guide.rst:63 +msgid "For updates on the status of the server itself." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:54 -msgid "Uploading a *CA certificate*?" +#: ../system/integrations/checkmk/setup-guide.rst:77 +msgid "🤔 **What's with all the env vars?**" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:52 +#: ../system/integrations/checkmk/setup-guide.rst:79 msgid "" -"In the case of an uploaded CA certificate, providing the value ``CA:TRUE`` " -"in the attribute *Basic Contstraints*, the previously mentioned attributes " -"are not verified." +"Whenever Checkmk runs these scripts, it needs to provide some information " +"about the event that triggered the notification. This information is passed " +"in the form of these ``$NOTIFY_*`` environment variables." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:56 +#: ../system/integrations/checkmk/setup-guide.rst:85 msgid "" -"In general, the usage of any expired (``Not After``) or not yet valid (``Not " -"Before``) certificate is denied for outgoing emails." +"You can specify additional parameters to pass to the script when you're " +"setting up your notification rule, but the ones you see here are all " +"provided by default." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:59 -msgid "Example certificate:" +#: ../system/integrations/checkmk/setup-guide.rst:90 +msgid "Email Alerts" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:85 +#: ../system/integrations/checkmk/setup-guide.rst:94 msgid "" -"Please note that Zammad will distrust senders by default. This means that " -"you're always required to provide certificate data, no matter if for signing " -"or encrypting." -msgstr "" - -#: ../system/integrations/smime/prerequisites.rst:89 -msgid "This is by design and can't be adjusted." +"🐞 **There are known bugs** in Zammad's processing of email from Checkmk. " +"This section will be completed once they have been resolved. (Learn more at " +"GitHub issues `#2377 `_ & " +"`#2180 `_.)" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:4 -msgid "" -"All of the system's latest S/MIME activity is displayed in the **Recent " -"Logs** section." +#: ../system/integrations/checkmk/setup-guide.rst:100 +msgid "In the meantime, we encourage you to set up API alerts instead." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:11 -msgid "Sample entries of in- and outgoing S/MIME related emails." +#: ../system/integrations/clearbit.rst:2 +msgid "Clearbit" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:11 +#: ../system/integrations/clearbit.rst:4 msgid "" -"Logs report the status and details of all mail, both incoming and outgoing, " -"that used signing/verification or encryption/decryption." +"With our Clearbit integration, you can easily enrich the information " +"provided by Zammad. If the customers or agents email address is known to " +"Clearbit, it will share all information it has regarding the user with " +"Zammad. Those information can include the following:" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:14 -msgid "" -"This log does **not** include email sent by :doc:`triggers ` or the :doc:`scheduler `. For those, check your " -"``production.log``." +#: ../system/integrations/clearbit.rst:9 +msgid "Avatar" +msgstr "Avatar" + +#: ../system/integrations/clearbit.rst:10 +msgid "Address information" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:20 -msgid "Common Issues" +#: ../system/integrations/clearbit.rst:11 +msgid "Website information" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:30 -msgid "I received a signed/encrypted email before I set up S/MIME integration" +#: ../system/integrations/clearbit.rst:12 +msgid "A BIO (as Note by default)" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:23 +#: ../system/integrations/clearbit.rst:14 msgid "" -"No problem. Once S/MIME has been enabled and the appropriate certificates " -"have been added, agents will be prompted to retry verification/decryption on " -"matching emails." +"If needed, you can add further custom objects and add mappings to them, so " +"the Clearbit information can be filled within the database. In general you " +"can get any information from Clearbit, as long as you have a mapping to an " +"Zammad object." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:0 -msgid "Screenshot of user prompt to retry decryption" +#: ../system/integrations/clearbit.rst:21 +msgid "" +"Clearbit does have a mapping of fields like LDAP and Exchange have, but does " +"not \"win\" against Zammad information. This means that if you have e.g. the " +"last name field filled in already and Clearbit has other information on " +"that, it will not be updated." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:38 -msgid "The 🔒 **Encrypt** button is disabled" +#: ../system/integrations/clearbit.rst:26 +msgid "" +"However: If let's say the last name has been set by Clearbit and Zammad " +"notices that the last name on the Clearbit source has changed, Zammad will " +"also update this value." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:33 -msgid "Have you added the recipient's certificate?" +#: ../system/integrations/clearbit.rst:33 +msgid "" +"The configuration of Clearbit is really easy and done fast! Just login to " +"your Clearbit-Account, go to \"API\" and copy the secret-API-Key." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:34 -msgid "Are you sure the recipient's certificate is valid?" +#: ../system/integrations/clearbit.rst:38 +msgid "" +"Now change to your Zammad instance, go to Integrations (System) -> Clearbit " +"in the admin panel. Paste your API-Key into the API-Key-Field and decide if " +"Zammad should create unknown Organizations automatically, if the user does " +"not have one yet (and Clearbit knows it). The shared option decides if the " +"new organizations Zammad creates with Clearbit should be shared ones." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:35 -msgid "Have you checked your ``production.log`` for more details?" +#: ../system/integrations/clearbit.rst:47 +msgid "" +"If you're unsure what option to choose, better stick with \"no\". You can " +"also learn more about :doc:`/manage/organizations/index`." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:37 +#: ../system/integrations/clearbit.rst:52 msgid "" -"If encryption doesn't work in the composer, it won't work in :doc:`triggers " -"` or the :doc:`scheduler ` either!" +"The Mapping option works similar to the mapping within the Exchange and LDAP " +"sync. You can add further mappings for e.g. custom fields if you need more " +"information that Clearbit can provide." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:42 -msgid "The ✅ **Sign** button is disabled" +#: ../system/integrations/clearbit.rst:58 +msgid "" +"If you want to add more Clearbit fields and want to learn more about " +"available fields on their API, you can take a look at their `API " +"documentation `_." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:41 +#: ../system/integrations/clearbit.rst:62 msgid "" -"Have you added **both the certificate and private key** for your " -"organization?" +"If you're happy with the above chosen Settings and your mapping, just save " +"the changes and enable Clearbit integration. Zammad will now start polling " +"the Clearbit API as users contact you." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:42 +#: ../system/integrations/clearbit.rst:68 msgid "" -"Does the email address on the certificate match the email address of the " -"agent/group composing the email?" +"Zammad does not synchronize with Clearbit on a regular basis, but on demand " +"if needed. This saves API calls." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:45 -msgid "Error: “Fingerprint already taken”" +#: ../system/integrations/clearbit.rst:73 +msgid "" +"Below the Settings and Mappings, you'll find our Integration log. You can " +"see what requests Zammad sent to Clearbit and also the APIs Response." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:45 -msgid "Are you sure you haven't added this certificate already?" +#: ../system/integrations/clearbit.rst:78 +msgid "" +"By the way, you can also view the API log on the Clearbit website - the " +"information seen is basically the same." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:48 -msgid "Error: “❌ invalid byte sequence in UTF-8”" +#: ../system/integrations/clearbit.rst:84 +msgid "Example When Adding a User" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:48 -msgid "Please ensure to provide PEM formatted certificate and keys." +#: ../system/integrations/clearbit.rst:86 +msgid "" +"To show you how fast information is added, we added a small Screencast " +"below. This shows the creation of the User Alex from Clearbit. As we already " +"set the last name of Alex to \"X\", Zammad did not update it. What Zammad " +"did was to add further information it received from Clearbit." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:49 -msgid "Did you check if the provided file is a valid certificate or key?" +#: ../system/integrations/cti/generic.rst:2 +msgid "CTI (generic)" msgstr "" -#: ../system/integrations/zabbix.rst:2 -msgid "Zabbix Integration" -msgstr "Integração com Zabbix" - -#: ../system/integrations/zabbix.rst:5 +#: ../system/integrations/cti/includes/introduction.include.rst:1 msgid "" -"This guide describes how to integrate your Zabbix 5.4 installation with " -"Zammad using the Zabbix webhook feature. This guide will provide " -"instructions on setting up a media type, a user and an action in Zabbix." +"This integration enables Zammad to provide a caller log to your agents. With " +"this your agents can greet your customers by their name and are supported by " +"Zammad with automatically opening a new ticket dialog or the user profile." msgstr "" -#: ../system/integrations/zabbix.rst:12 -msgid "Zammad with enabled HTTP Token Authentication" -msgstr "Zammad com autenticação de token HTTP ativada" - -#: ../system/integrations/zabbix.rst:13 -#, fuzzy -msgid "Zabbix version 5.4 or higher" -msgstr "Zabbix versão 5.0 ou superior" - -#: ../system/integrations/zabbix.rst:16 -msgid "Setting up a Zammad" -msgstr "Configurando o Zammad" - -#: ../system/integrations/zabbix.rst:18 -msgid "Enable **API Token Access** in Settings > System > API." -msgstr "Ative o **Token de acesso a API** em Configurações > Sistema > API." - -#: ../system/integrations/zabbix.rst:20 +#: ../system/integrations/cti/includes/introduction.include.rst:6 msgid "" -"Create a **new user** for a Zabbix alerter with an **email address** and " -"create a personal user token with **ticket.agent** permissions." +"Click the toggle next to the heading to activate or deactivate this " +"integration." msgstr "" -#: ../system/integrations/zabbix.rst:24 -#, fuzzy -msgid "Zabbix Webhook Configuration" -msgstr "Configuração de Webhook do Zabbix" - -#: ../system/integrations/zabbix.rst:27 -#, fuzzy -msgid "Create a Global Macro" -msgstr "Criar uma macro global" - -#: ../system/integrations/zabbix.rst:29 +#: ../system/integrations/cti/includes/introduction.include.rst:9 msgid "" -"Before setting up the **Webhook**, you need to setup the global macro " -"**{$ZABBIX.URL}**, which must contain the **URL** to the **Zabbix frontend**." +"If you want to learn more on how your agents can use this function, please " +"refer the :user-docs:`user documentation `." msgstr "" -#: ../system/integrations/zabbix.rst:33 +#: ../system/integrations/cti/includes/introduction.include.rst:14 msgid "" -"In the **Administration** > **Media types** section, import the `Template`_." +"Automatically opening new ticket dialogues or user profiles requires agent " +"to extension mapping - see more below." msgstr "" -#: ../system/integrations/zabbix.rst:38 -msgid "Open the added **Zammad** media type and set:" -msgstr "Abra o tipo de mídia **Zammad** adicionado e defina:" - -#: ../system/integrations/zabbix.rst:40 -msgid "**zammad\\_access\\_token** to the your **Personal User Token**" +#: ../system/integrations/cti/includes/introduction.include.rst:20 +msgid "Please note the following limitations to reduce confusion later on:" msgstr "" -#: ../system/integrations/zabbix.rst:41 -msgid "" -"**zammad\\_url** to the **frontend URL** of your **Zammad** installation" +#: ../system/integrations/cti/includes/introduction.include.rst:22 +msgid "CTI integrations provide caller log functions only." msgstr "" -#: ../system/integrations/zabbix.rst:43 -msgid "**zammad\\_customer** to your **Zammad user email**." +#: ../system/integrations/cti/includes/introduction.include.rst:23 +msgid "" +"This integration does not provide any VoIP functionalities; you can't make " +"phone calls from within Zammad." msgstr "" -#: ../system/integrations/zabbix.rst:44 +#: ../system/integrations/cti/includes/introduction.include.rst:25 msgid "" -"**zammad\\_enable\\_tags** to **true** or **false** to enable or disable " -"trigger tags. **Important**: if you enable tag support, each tag is set with " -"a separate request." +"If your browser supports ``tel``-URLs, you can click on phone numbers for " +"automatic dialing. This requires additional software / configuration on your " +"agent's computers." msgstr "" -#: ../system/integrations/zabbix.rst:48 +#: ../system/integrations/cti/generic.rst:9 +#: ../system/integrations/cti/placetel.rst:14 +#: ../system/integrations/cti/sipgate.rst:14 +msgid "Please provide the following requirements:" +msgstr "" + +#: ../system/integrations/cti/generic.rst:11 msgid "" -"If you want to prioritize issues according to **severity** values in Zabbix, " -"you can define mapping parameters:" +"A telephone system that supports webhooks (outbound) (best option are those " +"that allow customizing the calls)." msgstr "" -#: ../system/integrations/zabbix.rst:51 -msgid "**severity\\_**: Zammad priority ID" +#: ../system/integrations/cti/generic.rst:13 +msgid "A unique Call-ID during the call session." msgstr "" -#: ../system/integrations/zabbix.rst:53 -msgid "Click the **Update** button to save the **Webhook** settings." +#: ../system/integrations/cti/generic.rst:14 +msgid "Call event data (both numbers and direction)." msgstr "" -#: ../system/integrations/zabbix.rst:55 -msgid "" -"To receive notifications in **Zammad**, you need to create a **Zabbix user** " -"and add **Media** with the **Zammad** type." +#: ../system/integrations/cti/generic.rst:15 +msgid "Your Zammad instance must be reachable for your telephony system." msgstr "" -#: ../system/integrations/zabbix.rst:58 +#: ../system/integrations/cti/generic.rst:17 msgid "" -"For **Send to**: enter any text, as this value is not used, but is required." +"If you want to learn more on what kind of requests are supported by Zammad " +"and what it expects, please consult our :docs:`CTI-API documentation `." msgstr "" -#: ../system/integrations/zabbix.rst:61 +#: ../system/integrations/cti/generic.rst:22 +#: ../system/integrations/cti/placetel.rst:27 +#: ../system/integrations/cti/sipgate.rst:30 +#, fuzzy +msgid "Available Settings" +msgstr "Configurações" + +#: ../system/integrations/cti/generic.rst:29 +#: ../system/integrations/cti/placetel.rst:41 +#: ../system/integrations/cti/sipgate.rst:40 +#, fuzzy +msgid "Endpoint Settings" +msgstr "Configurações" + +#: ../system/integrations/cti/generic.rst:25 msgid "" -"For more information, use the `Zabbix documentation `_." +"Zammad will list your generic CTI endpoint here. It contains a unique token " +"so ensure to keep this URL save." msgstr "" -#: ../system/maintenance.rst:2 -msgid "Maintenance" -msgstr "Manutenção" +#: ../system/integrations/cti/generic.rst:28 +msgid "" +"You'll need this endpoint for your PBX to talk to Zammad, see :docs:`CTI-API " +"documentation `." +msgstr "" -#: ../system/maintenance.rst:4 +#: ../system/integrations/cti/includes/important-dont-forget-saving.include.rst:3 msgid "" -"Zammad comes with a maintenance mode that you can use for e.g. updating the " -"instance or changing settings while restricting availability and functions." +"All following options **do not save automatically**. Always use the Save " +"button on the lower end of the integration page!" msgstr "" -#: ../system/maintenance.rst:13 -msgid "Mode" -msgstr "Modo" +#: ../system/integrations/cti/generic.rst:43 +#: ../system/integrations/cti/placetel.rst:49 +#: ../system/integrations/cti/sipgate.rst:52 +#, fuzzy +msgid "Call Settings" +msgstr "Configurações" -#: ../system/maintenance.rst:8 -msgid "The mode setting allows you to enable or disable the maintenance mode." +#: ../system/integrations/cti/generic.rst:39 +#: ../system/integrations/cti/placetel.rst:49 +#: ../system/integrations/cti/sipgate.rst:37 +#: ../system/integrations/cti/sipgate.rst:50 +msgid "Inbound" msgstr "" -#: ../system/maintenance.rst:10 -msgid "Defaults to *off*." +#: ../system/integrations/cti/includes/inbound-calls.include.rst:1 +msgid "" +"This option allows you to block specific incoming caller IDs. It allows you " +"to temporarily reject e.g. spam callers without having to contact providers " +"or PBX administrators." msgstr "" -#: ../system/maintenance.rst:12 -msgid "" -"The maintenance mode will restrict access to administrative roles only. This " -"means agents and customers are logged off." +#: ../system/integrations/cti/includes/inbound-calls.include.rst:11 +msgid "Caller ID to block" msgstr "" -#: ../system/maintenance.rst:23 -msgid "@Login" +#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 +msgid "Provide caller IDs to block in ``E.164`` format." msgstr "" -#: ../system/maintenance.rst:16 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:8 msgid "" -"This setting allows you to provide a login message within a green banner " -"above the login screen. Click into the green banner in the settings page to " -"adjust your message. To activate the message, activate the *@Login* setting." +"Your telephony system has to support this function. Zammad will send a " +"``reject`` response which will cause your telephony system to hang up the " +"call. To callers this usually will feel like the line is busy." msgstr "" -#: ../system/maintenance.rst:0 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:14 msgid "" -"Screenshot showing the default login message within the\n" -"settings page" +"Provide a meaningful note for your fellow administrators to remind yourself " +"why you've chosen to block the number." msgstr "" -#: ../system/maintenance.rst:26 -msgid "" -"Send an informative message to **all active sessions**. This comes handy to " -"inform your agents e.g. about mayor outages or to force reloads after " -"configuration changes." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:17 +#: ../system/integrations/cti/sipgate.rst:40 +msgid "Outbound" msgstr "" -#: ../system/maintenance.rst:31 -msgid "This is the messages title (slightly bigger than the normal message)." +#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:1 +msgid "" +"In many cases you may want to use a different caller ID depending on the " +"destination you're calling. This may apply due to specific connection rates " +"to other countries or because you want your customer to feel you're calling " +"from the same country." msgstr "" -#: ../system/maintenance.rst:34 -msgid "The text you want to provide to your logged in sessions." +#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:6 +msgid "This option expects ``E.164`` number formats." msgstr "" -#: ../system/maintenance.rst:39 -msgid "Reload application" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 +msgid "Destination caller ID" msgstr "" -#: ../system/maintenance.rst:37 -msgid "" -"Selecting this option will change the message acceptance button from *Close* " -"(with nothing happening) to *Continue session*, which forces the application " -"to reload." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:5 +msgid "The caller ID or number you're trying to call." msgstr "" -#: ../system/maintenance.rst:43 -msgid "" -"If you have customers that are logged in to Zammad, they'll also be notified " -"if they're active in that moment." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:7 +msgid "You can use wildcards for e.g. country specific outbound numbers like:" msgstr "" -#: ../system/maintenance.rst:48 -msgid "Example without reload application" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:9 +msgid "``49*`` for Germany" msgstr "" -#: ../system/maintenance.rst:52 -msgid "" -"Message setting within Zammad's admin settings without ticket reload " -"application setting." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:10 +msgid "``4930*`` for Berlin / Germany landlines" msgstr "" -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing the send message settings without ticket\n" -"reload application set" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 +msgid "``33*`` for France" msgstr "" -#: ../system/maintenance.rst:61 ../system/maintenance.rst:85 -msgid "" -"The modal all other active sessions will see upon pressing *Send to clients*." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:15 +msgid "Set Outbound caller ID" msgstr "" -#: ../system/maintenance.rst:0 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:14 msgid "" -"Screenshot showing modal caused by maintenance's message\n" -"without reload application ticket" +"The outbound caller ID to set (the number your customer sees on his display) " +"in ``E.164`` number format." msgstr "" -#: ../system/maintenance.rst:72 -msgid "Example with reload application" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 +msgid "Provide a short description for fellow administrators." msgstr "" -#: ../system/maintenance.rst:76 +#: ../system/integrations/cti/includes/generic-cti-support-note.includes.rst:3 msgid "" -"Message setting within Zammad's admin settings with ticket reload " -"application setting." +"This option requires your PBX to send a specific request to Zammad *before " +"dialing*. Please consult the :docs:`CTI API ` in case " +"you're not sure." msgstr "" -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing the send message settings with ticket\n" -"reload application set" -msgstr "" +#: ../system/integrations/cti/generic.rst:52 +#: ../system/integrations/cti/placetel.rst:54 +#: ../system/integrations/cti/sipgate.rst:59 +#, fuzzy +msgid "Other Settings" +msgstr "Configurações" -#: ../system/maintenance.rst:0 +#: ../system/integrations/cti/includes/other-settings-intro.include.rst:1 msgid "" -"Screenshot showing modal caused by maintenance's message\n" -"with reload application ticket" +"Below you can find all available additional settings for this CTI " +"integration. For your overview we're sorting them by appearance and " +"reference their description first." msgstr "" -#: ../system/monitoring.rst:2 -msgid "Monitoring" -msgstr "Monitoramento" +#: ../system/integrations/cti/includes/default-caller-id.include.rst:2 +#: ../system/integrations/cti/includes/default-caller-id.include.rst:1 +msgid "Default caller ID for outbound calls" +msgstr "" -#: ../system/monitoring.rst:4 -#, fuzzy -msgid "" -"This function is only available in self hosted instances. If you use Zammad " -"in our cloud, we are monitoring the system on our own and take steps to fix " -"potential problems directly." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:16 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:15 +msgid "Shown records in caller log" msgstr "" -"**Nota:** Isto está disponível apenas na versão on-premises, já que estamos " -"monitorando instâncias e resolvendo problemas." -#: ../system/monitoring.rst:11 -#, fuzzy +#: ../system/integrations/cti/includes/records-caller-log.include.rst:2 msgid "" -"On the monitoring page, you can see the current health state of Zammad under " -"\"*Current Status*\" at the bottom. This can be useful if you want to have a " -"look if everything is up and running. As an example, you could have a look " -"in the monitoring when you assume that some emails aren't processed from " -"Zammad." +"Allows you to set the number of shown caller log entries for all users. You " +"can choose from the following values:" msgstr "" -"Na página de monitoramento você pode ver o estado de saúde atual do Zammad. " -"Isto pode ser útil por exemplo se você parou de receber emails. Você também " -"pode checar esta página antes mesmo de fazer login no seu servidor." -#: ../system/monitoring.rst:17 -msgid "**Can't receive an email and the monitoring response is \"healthy\"?**" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:5 +msgid "60 (default)" msgstr "" -#: ../system/monitoring.rst:19 -msgid "" -"Zammad will just inform you about unprocessable emails. This is not the case " -"for oversized emails. You can adjust the maximum email size in :doc:`../" -"channels/email/settings`." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:6 +msgid "120" msgstr "" -#: ../system/monitoring.rst:24 -#, fuzzy -msgid "Monitoring API" -msgstr "Monitoramento" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:7 +msgid "180" +msgstr "" -#: ../system/monitoring.rst:26 -msgid "" -"Beside the indication in the monitoring page, you can also use an external " -"monitoring tool to monitor Zammad's health. To request the health of Zammad, " -"you need to provide the API key (token) to the external monitoring tool. You " -"can copy the token from the \"*Current Token*\" field as well as the whole " -"API endpoint of your system (\"*Health Check*\" field), in which the API " -"token is already included." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:8 +msgid "240" msgstr "" -#: ../system/monitoring.rst:37 -msgid "Screenshot showing Current Token and Health Check" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:9 +msgid "300" msgstr "" -#: ../system/monitoring.rst:37 -msgid "Screenshot showing Token and Health Check" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:11 +msgid "**🥵 Potential performance issue**" msgstr "" -#: ../system/monitoring.rst:39 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:13 msgid "" -"In addition to that, you can reset the auto-generated token to make sure " -"that already configured monitoring systems won't work anymore. So, please " -"use this \"*Reset*\" button only if you know what you do!" +"Setting this setting higher than 60 may cause serious performance issues on " +"very busy instances. Keep in mind that this setting causes Zammad to poll " +"and send up to 300 records to *all active agent sessions* in very short time " +"periods." msgstr "" -#: ../system/monitoring.rst:44 -#, fuzzy -msgid "Example Output" -msgstr "Um exemplo de saída pode ser:" - -#: ../system/monitoring.rst:0 -msgid "No issues found" +#: ../system/integrations/cti/generic.rst:73 +msgid "Caller Log Filter" msgstr "" -#: ../system/monitoring.rst:48 ../system/monitoring.rst:60 -msgid "**Indicator in Zammad**:" +#: ../system/integrations/cti/generic.rst:55 +msgid "" +"This function allows you to provide call information based on e.g. queues " +"only to agents that really need the information." msgstr "" -#: ../system/monitoring.rst:0 -msgid "Screenshot showing monitoring with no issues" +#: ../system/integrations/cti/generic.rst:58 +msgid "" +"Why? If you have a team for several countries or departments, you don't want " +"to bug your agents from other departments. Leaving these options empty will " +"fallback to showing everything to everyone." msgstr "" -#: ../system/monitoring.rst:54 ../system/monitoring.rst:66 -msgid "**API response**::" +#: ../system/integrations/cti/generic.rst:64 +msgid "Destination caller ID or Queue" msgstr "" -#: ../system/monitoring.rst:0 -msgid "Issues were found" +#: ../system/integrations/cti/generic.rst:63 +msgid "" +"This depends on your PBX and usually is either a queue ID, phone number or " +"extension." msgstr "" -#: ../system/monitoring.rst:0 -msgid "Screenshot showing monitoring with issues" +#: ../system/integrations/cti/generic.rst:69 +msgid "Agents" msgstr "" -#: ../system/objects.rst:2 -msgid "Objects" -msgstr "Objetos" - -#: ../system/objects.rst:4 +#: ../system/integrations/cti/generic.rst:67 msgid "" -"In Zammad you can add your own fields to tickets, users, organizations and " -"even groups (these are called \"objects\"). This can be useful if you need " -"to add further information to a ticket or any other object in Zammad and the " -"information doesn't fit in any existing field." +"Select the agents that are responsible for the group. These agents will then " +"see caller log entries and call notifications fitting to said queue." msgstr "" -#: ../system/objects.rst:11 +#: ../system/integrations/cti/generic.rst:0 msgid "" -"Try to avoid deleting attributes (and disable them instead) as Zammad might " -"run into unexpected conditions if they are referenced somewhere." +"Screenshot showing the caller log filter table with pre filled sample data" msgstr "" -#: ../system/objects.rst:16 +#: ../system/integrations/cti/includes/recent-logs.include.rst:6 msgid "" -"Here's an overview of object attributes. On the upper right you can add new " -"attributes. By default, there will be no custom fields - standard attributes " -"will be grayed out, you can't delete or change those. You can edit custom " -"attributes (they are displayed in black font and have a trash bin on the " -"right side) just by clicking on them." +"With recent logs Zammad allows you to view the latest calls for the CTI " +"functionality. This usually comes in handy, when you're looking for errors." msgstr "" -#: ../system/objects.rst:24 +#: ../system/integrations/cti/includes/recent-logs.include.rst:0 msgid "" -"Attributes you add to Zammad, no matter if they have default values or not, " -"will not update existing information. This means a new ticket field " -"technically will be empty unless you populate it." +"Screenshot showing several incoming requests within Recent logs section." msgstr "" -#: ../system/objects.rst:28 -msgid "" -"Especially in ticket scope this also means that newly added attributes will " -"be indicated as \"changed\" to agents that view the ticket. This may " -"interfere with Zammad's tabs behavior." +#: ../system/integrations/cti/includes/recent-logs.include.rst:16 +msgid "I'm just here to clear floats up." msgstr "" -#: ../system/objects.rst:40 -#, fuzzy -msgid "Ordering Attributes" -msgstr "Atributos do ticket" - -#: ../system/objects.rst:42 +#: ../system/integrations/cti/includes/recent-logs.include.rst:20 msgid "" -"Since Zammad introduced :doc:`/system/core-workflows` the need to have a " -"custom positioning for attributes has become more important than ever." +"By clicking on the entry of interest, Zammad will provide more details on " +"the call in question. You'll see the payload it received and also the " +"response that was sent." msgstr "" -#: ../system/objects.rst:45 +#: ../system/integrations/cti/includes/recent-logs.include.rst:0 msgid "" -"To adjust the position of such an attribute, simply click on the attribute " -"entry in question, scroll down and adjust the position number. Please note " -"that you cannot change the positioning of default attributes." +"Screenshot showing detailed information of a specific log entry of recent " +"logs" msgstr "" -#: ../system/objects.rst:49 -msgid "" -"In case two attributes have the same position value, Zammad will sort " -"alphabetically by name automatically." +#: ../system/integrations/cti/includes/recent-logs.include.rst:31 +msgid "x" msgstr "" -#: ../system/objects.rst:None +#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 +#: ../system/integrations/cti/includes/troubleshooting.include.rst:9 +msgid "My Phone page stays blank, signalling does work..." +msgstr "" + +#: ../system/integrations/cti/includes/troubleshooting.include.rst:5 msgid "" -"Screenshot showing custom attribute entries ordered in between default ones" +"If you've made sure that signalling works (check Recent logs) and your " +"Caller Log still stays empty, please ensure that you only configured one CTI " +"integration version. Specifically defining more than one agent mapping on " +"the different integration variants will be the issue." msgstr "" -#: ../system/objects.rst:56 -msgid "Updating Database After Adding or Editing Attributes" +#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 +msgid "Clear the not needed agent mapping and reload your browser page." msgstr "" -#: ../system/objects.rst:58 +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:1 msgid "" -"When adding or changing attributes, Zammad will not apply the changes " -"instantly, but instead shows you the changed attributes first. If you're " -"ready to go, just click on \"Update database\" to apply the changes to " -"Zammad. If you made a mistake or just want to discard your changes, click " -"\"Discard changes\"." +"By mapping your agents extension to their existing Zammad users, Zammad can " +"provide a new ticket dialog or open the user profile for the agent that " +"picks up the call." msgstr "" -#: ../system/objects.rst:64 +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:5 msgid "" -"After applying the changes with \"Update Database\", a restart of Zammad is " -"**mandatory**. If you don't perform it, you may experience unexpected " -"behavior or even errors. You may want to do this kind of configuration " -"during maintenance windows." +"This speeds up ticket aiding, no matter if it's for existing tickets or new " +"ones!" msgstr "" -#: ../system/objects.rst:72 +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:8 msgid "" -"Changes on objects require you to update the database to apply these changes." +"To see it work from the agent's perspective, have a look on :user-docs:`user " +"documentation `." msgstr "" -#: ../system/objects.rst:75 -msgid "**🤓 Service restarts can be automated**" +#: ../system/integrations/cti/placetel.rst:2 +msgid "Placetel CTI" msgstr "" -#: ../system/objects.rst:0 -msgid "Hosted environments automatically restart for you." +#: ../system/integrations/cti/placetel.rst:16 +msgid "You need an administrative Placetel account for your organization." msgstr "" -#: ../system/objects.rst:0 +#: ../system/integrations/cti/placetel.rst:17 +#: ../system/integrations/cti/sipgate.rst:20 msgid "" -"If you're using a self-hosted installation you can use :docs:`environment " -"variables `" +"Your Zammad instance must be allowed to communicate to external services." msgstr "" -#: ../system/objects.rst:82 -#, fuzzy -msgid "System Attributes" -msgstr "Atributos do ticket" - -#: ../system/objects.rst:84 -msgid "" -"Zammad comes with pre-configured attributes. Some of them can't be edited " -"via UI (or at all). This is required for proper operation of Zammad and not " -"a bug." +#: ../system/integrations/cti/placetel.rst:18 +msgid "Placetel must be able to reach your Zammad instance." msgstr "" -#: ../system/objects.rst:90 -#, fuzzy -msgid "Ticket State" -msgstr "Atributos do ticket" +#: ../system/integrations/cti/placetel.rst:22 +msgid ":doc:`provider-configurations/placetel`" +msgstr "" -#: ../system/objects.rst:92 +#: ../system/integrations/cti/placetel.rst:21 msgid "" -"If the pre-configured states aren't enough for you or you want to change " -"them, you can do so by clicking on the cogwheel icon in the state row in the " -"ticket tab. But you should be careful when changing pre-configured states. " -"This can lead to unwanted behavior in some cases." +"Learn how to configure Placetel to enable Zammad and Placetel to communicate " +"with each other." msgstr "" -#: ../system/objects.rst:None -msgid "Screenshot showing highlighted ticket state attribute" +#: ../system/integrations/cti/placetel.rst:32 +msgid "" +"The here listed endpoint settings are relevant for the :doc:`integration " +"configuration with Placetel `." msgstr "" -#: ../system/objects.rst:122 -msgid "Handling of states" +#: ../system/integrations/cti/placetel.rst:37 +#: ../system/integrations/i-doit.rst:53 +msgid "Endpoint" msgstr "" -#: ../system/objects.rst:102 +#: ../system/integrations/cti/placetel.rst:36 msgid "" -"In the state configuration screen, you can add new states, disable states or " -"change states." +"This endpoint will be required for the Zammad integration within the " +"Placetel web interface." msgstr "" -#: ../system/objects.rst:0 -msgid "Screenshot showing table of default ticket states" +#: ../system/integrations/cti/placetel.rst:41 +msgid "API Token" msgstr "" -#: ../system/objects.rst:110 +#: ../system/integrations/cti/placetel.rst:40 msgid "" -"To add a new state, click on the \"New Ticket State\" button in the top " -"right corner. To change an existing state, simply click on the affected " -"state. This opens an edit dialog." +"You'll receive this token within the ``Web API`` menu. Make sure to copy " +"this value, it's only shown once!" msgstr "" -#: ../system/objects.rst:114 -msgid "" -"You can also clone a state or set them to \"Default for new tickets\" or " -"\"Default for follow-ups\" by clicking on the ⁝ action button and select the " -"desired function." +#: ../system/integrations/cti/placetel.rst:71 +#: ../system/integrations/cti/sipgate.rst:77 +msgid "Phone Extension to Agent Mapping" msgstr "" -#: ../system/objects.rst:118 -msgid "" -"*Default for new tickets* means that this state is used for every newly " -"created ticket." +#: ../system/integrations/cti/placetel.rst:0 +msgid "Screenshot showing sample user mappings in between Placetel and Zammad" msgstr "" -#: ../system/objects.rst:121 +#: ../system/integrations/cti/placetel.rst:64 msgid "" -"*Default for follow-ups* means that this state is used if the ticket is re-" -"opened after it was closed." +"You can find your agents Placetel username combination required within ⚙️ PBX " +"→ VoIP destinations. Within the \"Advanced settings\" section you're looking " +"for \"SIP user name\" and \"SIP server\"." msgstr "" -#: ../system/objects.rst:171 -msgid "Ticket state in detail" +#: ../system/integrations/cti/placetel.rst:68 +msgid "Combine these two like so: ``@``." msgstr "" -#: ../system/objects.rst:125 -msgid "" -"Below you can find a description for each field and option. Please head over " -"to the :ref:`example ` to see the edit dialog." +#: ../system/integrations/cti/placetel.rst:0 +msgid "Sample VoIP credentials for a Placetel user" msgstr "" -#: ../system/objects.rst:129 -msgid "" -"This is the name of the state and what you and your agents are seeing when " -"choosing a state somewhere (e.g. in tickets, trigger configuration)." +#: ../system/integrations/cti/provider-configurations/placetel.rst:2 +msgid "Setup Placetel connection for Zammad" msgstr "" -#: ../system/objects.rst:137 +#: ../system/integrations/cti/provider-configurations/placetel.rst:6 msgid "" -"There are different state types you can choose from. By default, Zammad " -"comes with one state per state type." +"This configuration step requires a *full* administrative Placetel account. " +"You may receive forbidden error messages with Placetel in case your " +"permissions are not high enough." msgstr "" -#: ../system/objects.rst:140 +#: ../system/integrations/cti/provider-configurations/placetel.rst:10 msgid "" -"**new**: for states for tickets that are new and it hasn't been worked on " -"them" +"The following actions can be configured via the `Placetel web interface " +"`_." msgstr "" -#: ../system/objects.rst:142 -msgid "" -"**open**: for states for tickets that are in progress and agents are working " -"on them" +#: ../system/integrations/cti/provider-configurations/placetel.rst:29 +msgid "Step 1: Activate Zammad integration" msgstr "" -#: ../system/objects.rst:144 -msgid "**merged**: for states for tickets that are merged with other tickets" +#: ../system/integrations/cti/provider-configurations/placetel.rst:14 +msgid "" +"Within Integrations, scroll down to Partner integrations and select Zammad." msgstr "" -#: ../system/objects.rst:145 +#: ../system/integrations/cti/provider-configurations/placetel.rst:17 msgid "" -"**pending reminder**: for states for tickets that are in progress and you " -"want to set a reminder. (default example: *pending reminder*)" +"You can alternatively filter by \"Ticket Systems\" to reduce the number of " +"entries on the page. You'll still want to look for Partner integrations. 🤓" msgstr "" -#: ../system/objects.rst:147 +#: ../system/integrations/cti/provider-configurations/placetel.rst:21 msgid "" -"**pending action**: for states for tickets that are waiting for a specified " -"time and then change their state (default example: *pending close*)" +"Within the Zammad integration now press \"Activate\". A new tab ``API`` " +"becomes available - open this tab." msgstr "" -#: ../system/objects.rst:150 +#: ../system/integrations/cti/provider-configurations/placetel.rst:24 msgid "" -"**closed**: for states for tickets that are finished and do not need to be " -"processed further" +"Now tick \"Enable Call Control / Notify API\" and paste the Placetel " +"endpoint from your Zammad instance into the field \"URL of your API " +"endpoint\". Save to apply the settings" msgstr "" -#: ../system/objects.rst:153 -msgid "" -"⚠️ Choosing the correct state type is important! If you are in doubt, have a " -"look on the default states and their types!" +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "Screencast showing how to activate the Zammad integration" msgstr "" -#: ../system/objects.rst:158 -msgid "Ignore escalation" +#: ../system/integrations/cti/provider-configurations/placetel.rst:51 +msgid "Step 2: Generate API Token for Placetel" msgstr "" -#: ../system/objects.rst:157 +#: ../system/integrations/cti/provider-configurations/placetel.rst:32 msgid "" -"Here you can define whether tickets of this state will count to escalation " -"time or not." +"Go back to the integrations page and scroll down to \"Web API\". Generate a " +"new API token by using the \"Create a new API token\" button." msgstr "" -#: ../system/objects.rst:161 +#: ../system/integrations/cti/provider-configurations/placetel.rst:37 msgid "" -"You can create a note for the state to inform other admins about the state. " -"This has no effect on tickets." +"If you already generated a token either use your existing token or reset it " +"by using above mentioned button. Placetel will ask you to conform this reset." msgstr "" -#: ../system/objects.rst:165 -#, fuzzy -msgid "Set the state to *active* or *inactive*." -msgstr "Se está ativo ou inativo" - -#: ../system/objects.rst:167 +#: ../system/integrations/cti/provider-configurations/placetel.rst:41 msgid "" -"it is technically possible to set all states to inactive. To keep Zammad " -"working in such a case, the inactive flag of one of the states is ignored." +"Please keep in mind that existing API scripts may no longer work due to " +"token resets!" msgstr "" -#: ../system/objects.rst:194 -#, fuzzy -msgid "Ticket state example" -msgstr "Árvore de Seleção" - -#: ../system/objects.rst:174 +#: ../system/integrations/cti/provider-configurations/placetel.rst:44 msgid "" -"Let's assume we want to create a new state which indicates that the ticket " -"has to wait for a response of a third party (e.g. service contractor or " -"manufacturer) and we want to to be able to set a reminder." +"Copy the provided API token and insert it into the \"API Token\" field " +"within Zammad's Placetel integration." msgstr "" -#: ../system/objects.rst:178 +#: ../system/integrations/cti/provider-configurations/placetel.rst:47 msgid "" -"First we give the new state a proper name. In this example we call it " -"\"waiting for manufacturer\"." +"Apply your changes by using the \"Save\" button on the bottom of the " +"Placetel integration page and activate the Placetel integration." msgstr "" -#: ../system/objects.rst:181 +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 msgid "" -"As state type we choose \"pending reminder\". This indicates that the ticket " -"is still open and we can set a reminder. This reminder can be useful if our " -"manufacturer sometimes isn't responding or we want to remind him to give us " -"an answer." +"Screencast showing how to retrieve an API token from Placetel for Zammad" msgstr "" -#: ../system/objects.rst:186 +#: ../system/integrations/cti/provider-configurations/placetel.rst:73 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:77 +msgid "Step 3: Restrict the numbers to notify on" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:54 msgid "" -"We choose \"no\" for \"ignore escalation\" because we want to escalate the " -"tickets even if we are waiting on the manufacturer's feedback." +"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " +"the the Integrations page of the Placetel web interface, go to \"Notify " +"API\"." msgstr "" -#: ../system/objects.rst:189 -#, fuzzy -msgid "The **result** in the creation dialog will look like this:" -msgstr "O resultado final parecerá como o seguinte:" +#: ../system/integrations/cti/provider-configurations/placetel.rst:58 +msgid "" +"Lower on the page Placetel allows you to restrict the numbers to notify on. " +"You'll find this within the \"External routing API\" part." +msgstr "" -#: ../system/objects.rst:0 -msgid "Screenshot showing ticket state creation dialog with example" +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "" +"Screenshot showing a sample selection of phone numbers to use for the " +"Placetels notify API" msgstr "" -#: ../system/objects.rst:197 ../system/objects.rst:199 -#, fuzzy -msgid "Ticket Priority" -msgstr "Prioridade" +#: ../system/integrations/cti/provider-configurations/placetel.rst:66 +msgid "" +"This menu point also provides a API request log from Placetel view. Just " +"open \"Recent responses of your API endpoint\" to learn more." +msgstr "" -#: ../system/objects.rst:199 ../system/objects.rst:201 +#: ../system/integrations/cti/provider-configurations/placetel.rst:69 msgid "" -"If the pre-configured priorities aren't enough for you or you want to change " -"them, you can do so by clicking on the cogwheel icon in the priority row in " -"the ticket tab:" +"If you want to see Zammad's perspective, use the \"Recent Logs\" part from " +"within the Placetel integration page." msgstr "" -#: ../system/objects.rst:None -msgid "Screenshot showing highlighted ticket priority attribute" +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "Screenshot showing sample log entries for Placetels API calls to Zammad" msgstr "" -#: ../system/objects.rst:224 ../system/objects.rst:226 -msgid "Handling of priorities" +#: ../system/integrations/cti/provider-configurations/placetel.rst:77 +msgid "Step 4 (optional): Further configurations for Placetel" msgstr "" -#: ../system/objects.rst:208 ../system/objects.rst:210 +#: ../system/integrations/cti/provider-configurations/placetel.rst:76 msgid "" -"In the priority configuration screen, you can add new priorities, disable " -"priorities or change priorities." +"If needed, you can now configure Zammad's Placetel integration in more " +"detail. You can learn more about your options here: :ref:`Placetel " +"integration settings `." msgstr "" -#: ../system/objects.rst:0 -msgid "Screenshot showing table of default ticket priorities" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:2 +msgid "Setup Sipgate connection for Zammad" msgstr "" -#: ../system/objects.rst:216 ../system/objects.rst:218 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"To add a new priority, click on the \"New Priority\" button in the top right " -"corner. To change an existing priority, simply click on the affected " -"priority. This opens an edit dialog." +"Sipgate has no english web interface which is why this documentation page is " +"mixing up languages badly." msgstr "" -#: ../system/objects.rst:220 ../system/objects.rst:222 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"You can also clone a priority or set them to \"Default for new tickets\" by " -"clicking on the ⁝ action button and select the desired function." +"Please also note that the availability of API addons highly depends on your " +"package trier. Usage of sipgate.io packages *is not free*, please check " +"their `pricing page `_ before!" msgstr "" -#: ../system/objects.rst:223 ../system/objects.rst:225 -msgid "" -"*Default for new tickets* means that this priority is used for every newly " -"created ticket." +#: ../system/integrations/cti/provider-configurations/sipgate.rst:35 +msgid "Step 1: Book sipgate.io package" msgstr "" -#: ../system/objects.rst:246 ../system/objects.rst:248 -msgid "Priorities in detail" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:13 +msgid "Skip to step 2 if you already have the package booked!" msgstr "" -#: ../system/objects.rst:227 ../system/objects.rst:229 -msgid "Below you can find a description for each field and option." +#: ../system/integrations/cti/provider-configurations/sipgate.rst:15 +msgid "" +"Login to an administrative Sipgate account and navigate to " +"``Accountverwaltung``. You'll see several different options depending on " +"your booked packages. Select ``Verträge & Produkte`` to continue." msgstr "" -#: ../system/objects.rst:230 ../system/objects.rst:232 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:19 msgid "" -"This is the name of the priority and what you and your agents are seeing " -"when choosing a priority somewhere (e.g. in tickets, trigger configuration)." +"Scroll down to the section ``Zusätzliche Produkte buchen`` and look for " +"``sipgate.io`` - select this product by using the ``Produkte anzeigen``-" +"Button." msgstr "" -#: ../system/objects.rst:240 ../system/objects.rst:242 -msgid "Highlight color" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:23 +msgid "" +"On the next page select either one of the ``sipgate.io`` packages or ``Push-" +"API Package Free``. Follow the dialogue by booking the addon. You'll be " +"returned to your contract overview and now should see the selected addon in " +"your list." msgstr "" -#: ../system/objects.rst:235 ../system/objects.rst:237 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:30 msgid "" -"Switch between *Low priority* (light blue), *High priority* (red) and - " -"(default). This affects the displayed color for ticket titles in overviews." +"The availability for ``sipgate.io`` packages and their levels highly depends " +"on the overall account type and product you've booked with Sipgate." msgstr "" -#: ../system/objects.rst:239 ../system/objects.rst:241 -msgid "The color options are currently limited to the mentioned options." +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "" +"Screencast showing the process on how to book the required sipgate.io addon" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:52 +msgid "Step 2: Configure webhook for Zammad" msgstr "" -#: ../system/objects.rst:243 ../system/objects.rst:245 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:38 msgid "" -"You can create a note for the priority to inform other admins about the " -"priority. This has no effect on tickets." +"Within your ``Accountverwaltung`` navicate to your product ``sipgate.io``. " +"In the newly opened tab, switch from \"Clients\" to \"Webhooks\" and paste " +"the endpoint URLs from your Zammad instance like so:" msgstr "" -#: ../system/objects.rst:247 ../system/objects.rst:249 -#, fuzzy -msgid "Set the priority to *active* or *inactive*." -msgstr "Se está ativo ou inativo" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:42 +msgid "Inbound endpoint to \"Incoming\"" +msgstr "" -#: ../system/objects/external-data-source-example.rst:2 -msgid "External Data Source" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:43 +msgid "Outbound endpoint to \"Outgoing\"" msgstr "" -#: ../system/objects/external-data-source-example.rst:4 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:47 msgid "" -"We assume you already had a look on :doc:`types` where you can find a " -"description of the individual fields." +"Ensure to select at least one call group or phoneline within \"Sources\". " +"Other wise Sipgate will not indicate any incoming or outgoing calls to " +"Zammad." msgstr "" -#: ../system/objects/external-data-source-example.rst:7 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"To reproduce this example, choose a category you want to add a custom field, " -"click on *New Attribute* and select *External data source field* under " -"*Format*." +"Screencast showing how to add Zammad's endpoint URLs to sipgate.ios webhook " +"configuration" msgstr "" -#: ../system/objects/external-data-source-example.rst:11 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:55 msgid "" -"Our example story is to fetch data from an external product database. We " -"want to add our products to the tickets so that the products can be searched " -"and chosen from a list and also create a link to the product website." +"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " +"the Webhooks → URLs section of Sipgate you can select which *sources* " +"Sipgate should notify Zammad about in- and outgoing calls." msgstr "" -#: ../system/objects/external-data-source-example.rst:16 -#, fuzzy -msgid "Base configuration" -msgstr "Configuração" - -#: ../system/objects/external-data-source-example.rst:None -msgid "Initial steps to configure external data source object type" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:59 +msgid "" +"Use either specific phone lines or use the option \"Use for all phonelines " +"and groups\" to notify Zammad about all existing lines of your Sipgate " +"account." msgstr "" -#: ../system/objects/external-data-source-example.rst:23 -#: ../system/variables.rst:85 -#, fuzzy -msgid "**Example:**" -msgstr "**Por exemplo:**" - -#: ../system/objects/external-data-source-example.rst:25 -msgid "Name: *product*" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "" +"Screenshot showing a sample selection of phone numbers to use for the " +"Sipgates webhooks API" msgstr "" -#: ../system/objects/external-data-source-example.rst:26 -msgid "Display: *Product*" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:68 +msgid "This section also allows you to enable a Debug log." msgstr "" -#: ../system/objects/external-data-source-example.rst:29 -#, fuzzy -msgid "External data source configuration" -msgstr "Configuração" - -#: ../system/objects/external-data-source-example.rst:31 -msgid "" -"First, enter the search URL making sure it contains ``#{search.term}`` as a " -"parameter:" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "Screenshot showing an enabled Debug log option" msgstr "" -#: ../system/objects/external-data-source-example.rst:34 -msgid "**Example:** ``https://dummyjson.com/products/search?q=#{search.term}``" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:73 +msgid "" +"After enabling you can use the Debug log section to see all sent webhook " +"calls to Zammad. You'll also can see the response." msgstr "" -#: ../system/objects/external-data-source-example.rst:36 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"After that, head down to the preview section and enter a search input for " -"the external data source." +"Screenshot showing sample log entries for Sipgates webhook calls to Zammad" msgstr "" -#: ../system/objects/external-data-source-example.rst:39 -#, fuzzy -msgid "**Example:** ``mac``" -msgstr "**Por exemplo:**" - -#: ../system/objects/external-data-source-example.rst:41 -msgid "Then you can find a preview of the response data below:" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:81 +msgid "Step 4 (optional): Further configurations for Sipgate" msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of JSON response based on search term" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:80 +msgid "" +"If needed, you can now configure Zammad's Sipgate integration in more " +"detail. You can learn more about your options here: :ref:`Sipgate " +"integration settings `." msgstr "" -#: ../system/objects/external-data-source-example.rst:48 -msgid "" -"We recommend using the preview to have a look on the structure. There is a " -"top-level element called ``products``. One level below, you can find the " -"attributes ``id`` and ``title``." +#: ../system/integrations/cti/sipgate.rst:2 +msgid "Sipgate (sipgate.io)" msgstr "" -#: ../system/objects/external-data-source-example.rst:52 -msgid "**Search result response based on search from example:**" +#: ../system/integrations/cti/sipgate.rst:16 +msgid "You need an administrative Sipgate account for your organization." msgstr "" -#: ../system/objects/external-data-source-example.rst:119 +#: ../system/integrations/cti/sipgate.rst:17 msgid "" -"To tell the remote system that the desired data is located below the " -"``products`` level, you have to put it in the field *Search result list key*." +"Zammad requires a ``sipgate.io`` addon from the feature store (please note " +"that API calls are not free with Sipgate. Rates may apply and differ from " +"account to account)." msgstr "" -#: ../system/objects/external-data-source-example.rst:122 -msgid "" -"After inserting ``products`` in the mentioned field, you get an extended " -"preview. You can find an additional box *Search result list* with a JSON " -"structure. This is the same response as before but stripped from the upper " -"``products`` element by the external data source." +#: ../system/integrations/cti/sipgate.rst:21 +msgid "Sipgate must be able to reach your Zammad instance." msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of JSON response search result list" +#: ../system/integrations/cti/sipgate.rst:25 +msgid ":doc:`provider-configurations/sipgate`" msgstr "" -#: ../system/objects/external-data-source-example.rst:132 +#: ../system/integrations/cti/sipgate.rst:24 msgid "" -"Now you need to provide the keys for the search result values and labels. As " -"already mentioned, we are looking for the ``id`` and the ``title`` of our " -"products. If you haven't already, it is now a good time to look at the " -"preview of the *Search result list*." +"Learn how to configure Sipgate to enable Zammad and Sipgate to communicate " +"with each other." msgstr "" -#: ../system/objects/external-data-source-example.rst:197 +#: ../system/integrations/cti/sipgate.rst:33 msgid "" -"After locating our two keys, we insert them in *search result value key* " -"(``id``) and in *Search result label key* (``title``)." +"Below endpoint settings affect the :doc:`sipgate.io configuration `." msgstr "" -#: ../system/objects/external-data-source-example.rst:200 -msgid "" -"Basically, we configured the external data source already and we can see a " -"table in the preview section:" +#: ../system/integrations/cti/sipgate.rst:37 +msgid "This endpoint is required for incoming call hooks." msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of product table based on search term" +#: ../system/integrations/cti/sipgate.rst:40 +msgid "This endpoint is required for outgoing call hooks." msgstr "" -#: ../system/objects/external-data-source-example.rst:208 -msgid "" -"According to our example story, now just the *Link template* is missing." +#: ../system/integrations/cti/sipgate.rst:0 +msgid "Screenshot showing sample user mappings in between Sipgate and Zammad" msgstr "" -#: ../system/objects/external-data-source-example.rst:210 +#: ../system/integrations/cti/sipgate.rst:69 msgid "" -"Please note that this is an optional feature. If you don't want to use such " -"links, of course you don't have to configure it." +"You can find your agent's Sipgate username within ``Accountverwaltung → " +"Benutzer``. You're looking for the SIP-ID." msgstr "" -#: ../system/objects/external-data-source-example.rst:213 -msgid "" -"We can add now an address where additional product information can be found." +#: ../system/integrations/cti/sipgate.rst:0 +msgid "Sample VoIP credentials for a Sipgate user" msgstr "" -#: ../system/objects/external-data-source-example.rst:215 -msgid "Example: ``https://your_domain.com/q=#{ticket.product}``" +#: ../system/integrations/cti/sipgate.rst:77 +msgid "Users with several devices also have several SIP-IDs." msgstr "" -#: ../system/objects/external-data-source-example.rst:217 -msgid "In the example, the parameter means:" +#: ../system/integrations/elasticsearch.rst:2 +msgid "Elasticsearch (SaaS)" msgstr "" -#: ../system/objects/external-data-source-example.rst:219 -msgid "``#{}``: \"Frame\" for the insertion of information" +#: ../system/integrations/elasticsearch.rst:4 +msgid "" +"The Elasticsearch integration allows you to create a read-only user to use " +"with your favorite reporting tool (e.g. like Grafana)." msgstr "" -#: ../system/objects/external-data-source-example.rst:220 -msgid "``ticket``: object level, where you create your custom object" +#: ../system/integrations/elasticsearch.rst:7 +msgid "" +"If you want to take full advantage of the Zammad reporting, have a look at " +"our :docs:`Grafana ` " +"setup page as well." msgstr "" -#: ../system/objects/external-data-source-example.rst:221 -msgid "``product``: name of the (custom) object" +#: ../system/integrations/elasticsearch.rst:11 ../system/subscription.rst:7 +msgid "**🚧 Hosted environment specific 🚧**" msgstr "" -#: ../system/objects/external-data-source-example.rst:223 +#: ../system/integrations/elasticsearch.rst:13 msgid "" -"After configuring your *Link template*, there will be another column in the " -"preview. Hovering on the icons in the *Link* column will show you where it " -"forwards you." +"This integration is only available for Hosted setups. In order to use " +"Elasticsearch you'll need the **Plus** subscription." msgstr "" -#: ../system/objects/external-data-source-example.rst:232 +#: ../system/integrations/elasticsearch.rst:16 msgid "" -"In our example, one of the links looks like: https://your_domain.com/q=6, " -"where the 6 is the product id." +"Self hosted users have all the control over their self hosted Elasticsearch " +"instances." msgstr "" -#: ../system/objects/external-data-source-example.rst:235 -msgid "You can find more information regarding the URL in :doc:`types`." +#: ../system/integrations/elasticsearch.rst:None +msgid "Elasticsearch integration page on SaaS environments" msgstr "" -#: ../system/objects/includes/adding-values-hint.include.rst:3 +#: ../system/integrations/elasticsearch.rst:27 msgid "" -"Adding values can be tricky for first timers, don't forget to press \"➕ " -"Add\" after typing your values. Otherwise you may loose a value." +"Please note the following limitations of Elasticsearch access on hosted " +"environments:" msgstr "" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:1 -#: ../system/objects/includes/reposition-values.include.rst:1 -msgid "**↕️ This field type allows the positioning of its values ↔️**" +#: ../system/integrations/elasticsearch.rst:30 +msgid "access to the Elasticsearch index is read-only access" msgstr "" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:3 +#: ../system/integrations/elasticsearch.rst:31 +msgid "currently you're limited to user only" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:32 msgid "" -"In order to re-arrange the field values, first edit the field. Then you can " -"use ☰ to drag the values in question to the correct position. If you want to " -"change the layer depth, double click on ☰. With it you can cycle through the " -"available layers." +"Reporting tools that require to write into the indexes (like Kibana) are not " +"supported" msgstr "" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:8 -msgid "When you're ready, submit your changes to save the object attribute." +#: ../system/integrations/elasticsearch.rst:34 +msgid "IP access restriction is currently not yet supported" msgstr "" -#: :0 ../system/objects/types.rst:0 -msgid "" -"Screencast showing how to re-position values on tree select like\n" -"fields" +#: ../system/integrations/elasticsearch.rst:37 +msgid "Activating Elasticsearch Access" msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:3 +#: ../system/integrations/elasticsearch.rst:39 msgid "" -"In order to re-arrange the field values, edit the field and scroll below the " -"values. Make sure to tick the option \"Use custom option sort\"." +"By default external access to your Elasticsearch index is not active. You " +"can enable the integration at any time if needed." msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:8 +#: ../system/integrations/elasticsearch.rst:42 msgid "" -"If you do not tick this field, all manual positioning you did above will be " -"lost upon saving! ☠️" +"Please ensure to note down the password provided - you won't have access to " +"it afterwards." msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:11 -msgid "" -"Now use ☰ to drag the values in question to the correct position. When " -"you're ready, submit your changes to save the object attribute." +#: ../system/integrations/elasticsearch.rst:None +msgid "Screencast showing activation of Elasticsearch integration" msgstr "" -#: :0 ../system/objects/types.rst:0 -msgid "Screencast showing how to re-position values" +#: ../system/integrations/elasticsearch.rst:51 +msgid "Connection Settings" msgstr "" -#: ../system/objects/includes/url-template-hint.include.rst:3 +#: ../system/integrations/elasticsearch.rst:53 msgid "" -"This field allows using :ref:`URL fields (Link Templates) `." +"This section holds the most important general information for accessing your " +"Elasticsearch indexes - such as:" msgstr "" -#: ../system/objects/permissions.rst:2 -#, fuzzy -msgid "Attribute Permissions" -msgstr "Atributos do artigo" - -#: ../system/objects/permissions.rst:7 -msgid "" -"In the object attributes configuration you can define if a field is shown " -"and if the input in the field is mandatory, separated by different screens " -"and for different :doc:`roles/permissions `." +#: ../system/integrations/elasticsearch.rst:57 +msgid "A unique subdomain that does not tell your real instance URL." msgstr "" -#: ../system/objects/permissions.rst:17 -msgid "Screenshot shows object attribute permission table" +#: ../system/integrations/elasticsearch.rst:61 +msgid "Software" msgstr "" -#: ../system/objects/permissions.rst:17 +#: ../system/integrations/elasticsearch.rst:60 msgid "" -"Some of the possible permissions and screen options for a user object " -"attribute." +"The major version of the search index being used. This is required by some " +"Reporting tools like Grafana." msgstr "" -#: ../system/objects/permissions.rst:19 -msgid "" -"Based on the object context (ticket, agent, organization, user), the " -"selectable roles (to be precise: the required permissions) and screens " -"differ. Be aware that these settings aren't affecting data creation via " -"other channels than the UI." +#: ../system/integrations/elasticsearch.rst:64 +msgid "Authentication" msgstr "" -#: ../system/objects/permissions.rst:24 -msgid "" -"If you want to have further customization possibilities, you should have a " -"look at the :doc:`core workflows `." +#: ../system/integrations/elasticsearch.rst:64 +msgid "The authentication type being supported. ``Basic Authentication``" msgstr "" -#: ../system/objects/permissions.rst:28 -#, fuzzy -msgid "Screens" -msgstr "Assinaturas" - -#: ../system/objects/permissions.rst:30 -msgid "" -"In the table below you can find an overview about the different permissions " -"and the available screens Zammad distinguishes between." +#: ../system/integrations/elasticsearch.rst:67 +msgid "Available Indexes" msgstr "" -#: ../system/objects/permissions.rst:37 -#, fuzzy -msgid "Screen" -msgstr "Assinaturas" - -#: ../system/objects/permissions.rst:38 -msgid "Available for" +#: ../system/integrations/elasticsearch.rst:69 +msgid "" +"Within this section we're displaying the -in our opinion- most important " +"indexes for a Zammad instance." msgstr "" -#: ../system/objects/permissions.rst:40 -msgid "create" +#: ../system/integrations/elasticsearch.rst:72 +msgid "" +"If you require all indexes or our listing is not good enough for you, point " +"your browser to the URL we're providing and append ``/_aliases?" +"pretty=true``. The result should look like this: ``https://.zammad.com/" +"_aliases?pretty=true``." msgstr "" -#: ../system/objects/permissions.rst:41 ../system/objects/permissions.rst:52 -#: ../system/objects/permissions.rst:59 ../system/objects/permissions.rst:73 -msgid "admin.user" +#: ../system/integrations/elasticsearch.rst:77 +msgid "" +"Your browser will automatically ask for your credentials - you'll then see " +"something like this:" msgstr "" -#: ../system/objects/permissions.rst:42 ../system/objects/permissions.rst:53 -#: ../system/objects/permissions.rst:60 -#, fuzzy -msgid "admin.organization" -msgstr "Organização" - -#: ../system/objects/permissions.rst:43 ../system/objects/permissions.rst:54 -#: ../system/objects/permissions.rst:61 -msgid "admin.group" +#: ../system/integrations/elasticsearch.rst:125 +msgid "Credentials" msgstr "" -#: ../system/objects/permissions.rst:44 -msgid "Creation dialog for not yet existing data" +#: ../system/integrations/elasticsearch.rst:127 +msgid "" +"Within this section Zammad displays your available users. The password is " +"provided once (upon activation) and cannot be retrieved after that." msgstr "" -#: ../system/objects/permissions.rst:45 -msgid "create_middle" +#: ../system/integrations/elasticsearch.rst:131 +msgid "" +"If you need to change or reset your Elasticsearch user password, use the " +"\"Reset password\" button in the credentials table. Doing so creates a brand " +"new password for the account in question. This change is immediate, keep in " +"mind that this may affect third party tools connected to your instance." msgstr "" -#: ../system/objects/permissions.rst:46 ../system/objects/permissions.rst:50 -#: ../system/objects/permissions.rst:57 ../system/objects/permissions.rst:66 -#: ../system/objects/permissions.rst:70 -#, fuzzy -msgid "ticket.customer" -msgstr "Criar uma macro global" - -#: ../system/objects/permissions.rst:47 ../system/objects/permissions.rst:51 -#: ../system/objects/permissions.rst:58 ../system/objects/permissions.rst:69 -#, fuzzy -msgid "ticket.agent" -msgstr "Criar uma macro global" - -#: ../system/objects/permissions.rst:48 -msgid "Ticket create dialog (middle section)" -msgstr "" +#: ../system/integrations/exchange.rst:2 +msgid "Exchange" +msgstr "Exchange" -#: ../system/objects/permissions.rst:49 -msgid "edit" +#: ../system/integrations/exchange.rst:4 +msgid "" +"With Zammad's Exchange integration, you can easily use existing address " +"books without having to update more than one source." msgstr "" -#: ../system/objects/permissions.rst:55 -msgid "Editing dialog for already existing data" +#: ../system/integrations/exchange.rst:7 +msgid "" +"However, you should refrain from syncing all addresses, as the results may " +"not be what you expect (Exchange collects huge amounts of addresses). A " +"central address book of your company to sync makes more sense, as you can " +"ensure that Zammad gets only the data you need and want. Apart from this, it " +"is even not possible to sync the Global Address List (GAL) of your Exchange " +"system with Zammad." msgstr "" -#: ../system/objects/permissions.rst:56 -msgid "view" +#: ../system/integrations/exchange.rst:16 +msgid "" +"**Exchange and LDAP:** The exchange sync can be overruled by Zammad's LDAP " +"integration. If you have the same users in both sources, the LDAP version " +"will always be Zammad's pick." msgstr "" -#: ../system/objects/permissions.rst:62 -msgid "View-only dialog for already existing data" +#: ../system/integrations/exchange.rst:19 +msgid "" +"**One way sync:** the Exchange sync is one way. Exchange => Zammad. Changes " +"to your users inside of Zammad might be overwritten by the Exchange sync." msgstr "" -#: ../system/objects/permissions.rst:64 -msgid "(e.g. user or organization from search)" +#: ../system/integrations/exchange.rst:24 +msgid "" +"To configure Exchange integration, simply go to the System > Integrations > " +"Exchange in the admin panel. Press \"change\" and follow the wizard for " +"adding the needed Exchange information to Zammad. On the last two steps " +"Zammad will ask you for the address book(s) and your desired attribute " +"mapping. By default, Zammad only maps email address, first- and lastname. " +"Technically, you can map any Exchange object to a Zammad user object (this " +"also works for custom objects!)." msgstr "" -#: ../system/objects/permissions.rst:65 -msgid "signup" +#: ../system/integrations/exchange.rst:35 +msgid "" +"If the SSL verification fails while connecting to Exchange, Zammad will ask " +"you to turn it off temporarily." msgstr "" -#: ../system/objects/permissions.rst:67 -msgid "Sign-up screen for new customers" +#: ../system/integrations/exchange.rst:38 +msgid "" +"Please be aware that **turning off SSL verification is a security risk**. It " +"should only be used temporarily or for testing purposes. If turned off, " +"there is no verification of the certificate, which means that every " +"presented certificate will be accepted." msgstr "" -#: ../system/objects/permissions.rst:68 -msgid "invite_customer" +#: ../system/integrations/exchange.rst:43 +msgid "" +"After pressing Continue, Zammad will check if the configuration is okay. You " +"can then enable Exchange and start your first sync. The sync will then run " +"hourly - if you need to change mappings or the address book(s), you can " +"change the configuration at any time." msgstr "" -#: ../system/objects/permissions.rst:71 +#: ../system/integrations/exchange.rst:50 msgid "" -"Customer invitation screen (from :doc:`First Steps ` area)" +"After the sync has finished, you can find the new Exchange contacts under " +"\"Users\". Zammad integrates them just as normal users." msgstr "" -#: ../system/objects/permissions.rst:72 -msgid "invite_agent" +#: ../system/integrations/exchange.rst:55 +msgid "" +"In some cases you might see unique IDs as \"Login\" instead of the email " +"address. This is normal and doesn't affect the login or email mapping for " +"that entry." msgstr "" -#: ../system/objects/permissions.rst:74 +#: ../system/integrations/github.rst:4 msgid "" -"Agent invitation screen (from :doc:`First Steps ` area)" +"Use GitHub integration to track GitHub issues directly within Zammad " +"tickets. Add issue hyperlinks and get a live summary of metadata like status " +"(open/closed), assignee, labels, and more." msgstr "" -#: ../system/objects/permissions.rst:78 +#: ../system/integrations/github.rst:8 #, fuzzy -msgid "Screen Options" -msgstr "Organizações" - -#: ../system/objects/permissions.rst:80 -msgid "" -"For the different screens you can select \"show\" and \"required\" options." +msgid "Please note that our GitHub integration does not support pull requests." msgstr "" +"A integração do GitLab não oferece suporte a solicitações de mesclagem." -#: ../system/objects/permissions.rst:82 -msgid "**shown:** Show (check) or hide (uncheck) a field." +#: ../system/integrations/github.rst:None +msgid "Integration page for GitHub" msgstr "" -#: ../system/objects/permissions.rst:83 +#: ../system/integrations/github.rst:18 msgid "" -"**required:** Set a field to mandatory (check). Forces users (via UI and " -"API) to populate the field." +"In your GitHub settings, create a new API token under **Developer settings > " +"Personal access tokens > Generate new token**. Leave the **Scopes** section " +"empty." msgstr "" -#: ../system/objects/types.rst:7 -#, fuzzy -msgid "Example external data source" -msgstr "Configuração" - -#: ../system/objects/types.rst:2 -#, fuzzy -msgid "Attribute types" -msgstr "Atributos do artigo" - -#: ../system/objects/types.rst:4 -msgid "" -"When adding a new object attribute, you can choose between the following " -"attribute types." +#: ../system/integrations/github.rst:0 ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to create a new API token" msgstr "" -#: ../system/objects/types.rst:14 -msgid "" -"You cannot change the attribute format / type as soon as it is applied. If " -"you no longer need an object attribute, consider disabling it instead of " -"removing." +#: ../system/integrations/github.rst:27 +msgid "Create a new API key with no scopes/privileges." msgstr "" -#: ../system/objects/types.rst:18 -msgid "**What about the translation of my attributes?**" +#: ../system/integrations/github.rst:29 +msgid "🔒 **Will this work for private repos?**" msgstr "" -#: ../system/objects/types.rst:20 +#: ../system/integrations/github.rst:31 msgid "" -"For some attribute types you can decide if they should be translatable or " -"not. To be precise, it works only for the selectable fields because the " -"possible choices are known and limited. For the following attribute types, " -"you can set the translatable flag:" -msgstr "" - -#: ../system/objects/types.rst:25 -#, fuzzy -msgid "*Boolean field*" -msgstr "Booleano" - -#: ../system/objects/types.rst:26 -msgid "*Single selection field*" +"No. To link private repo issues, **use the** ``repo`` **scope instead**. " +"Bear in mind that the resulting token will have `lots of permissions that it " +"doesn't actually need `_, which presents a security risk if your token ever falls into " +"the wrong hands." msgstr "" -#: ../system/objects/types.rst:27 -msgid "*Multiple selection field*" +#: ../system/integrations/github.rst:37 +msgid "" +"Unfortunately, because of how GitHub's OAuth token scopes are set up, this " +"is the only way to link issues on private repos." msgstr "" -#: ../system/objects/types.rst:28 -msgid "*Single tree selection field*" +#: ../system/integrations/github.rst:40 +msgid "Enter your new API token in Zammad and enable GitHub integration." msgstr "" -#: ../system/objects/types.rst:29 -msgid "*Multiple tree selection field*" +#: ../system/integrations/github.rst:0 +msgid "Screencast showing how to configure Zammad's GitHub integration" msgstr "" -#: ../system/objects/types.rst:31 +#: ../system/integrations/github.rst:47 +#, fuzzy msgid "" -"For these types, you can find an additional field *Translate field contents*:" -msgstr "" - -#: ../system/objects/types.rst:0 -msgid "Screenshot showing translatable attribute types" +"Use the default API endpoint (``https://api.github.com/graphql``) unless " +"you're using GitHub Enterprise Server." msgstr "" +"Deixe o endpoint padrão da API (``https://gitlab.com/api/graphql``) como " +"está, a menos que você seja um usuário Gitlab auto-hospedado." -#: ../system/objects/types.rst:38 -msgid "Screenshot with example of translatable attribute type" +#: ../system/integrations/github.rst:50 +msgid "" +"Once completed, a new GitHub issues tab will appear in the ticket pane. 🎉" msgstr "" -#: ../system/objects/types.rst:45 -#, fuzzy -msgid "Boolean field" -msgstr "Booleano" - -#: ../system/objects/types.rst:41 +#: ../system/integrations/github.rst:59 ../system/integrations/gitlab.rst:52 +msgid "Token verification is taking a long time" +msgstr "A verificação do token está demorando muito" + +#: ../system/integrations/github.rst:56 ../system/integrations/gitlab.rst:49 msgid "" -"Provides a drop-down field with display values for ``true`` and ``false``. " -"Setting a default is mandatory." +"Slight delays are normal (<2 min.), especially for systems under heavy load." msgstr "" +"Atrasos leves são normais (<2 min.), especialmente para sistemas sob carga " +"pesada." -#: ../system/objects/types.rst:0 -msgid "Available settings for Boolean fields" +#: ../system/integrations/github.rst:58 +#, fuzzy +msgid "" +"Self-hosted administrators, please check your network settings to ensure " +"that your Zammad server can reach ``api.github.com``." msgstr "" +"Administradores de ambientes auto-hospedados, verifique suas configurações " +"de rede para garantir que seu servidor Zammad pode acessar gitlab.com." -#: ../system/objects/types.rst:55 -msgid "Date field" -msgstr "" +#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 +msgid "I reloaded the page and now the API token is gone" +msgstr "Eu recarreguei a página e agora o token de API se perdeu" -#: ../system/objects/types.rst:48 -msgid "Provides a date picker field and does not allow default values." +#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 +msgid "" +"This may indicate that Zammad is still verifying your API token. Try " +"reloading the page again in a couple minutes." msgstr "" +"Isso pode indicar que Zammad ainda está verificando seu token de API. Tente " +"recarregar a página novamente em alguns minutos." -#: ../system/objects/types.rst:52 -msgid "Default time diff (hours)" -msgstr "" +#: ../system/integrations/gitlab.rst:2 +msgid "GitLab" +msgstr "GitLab" -#: ../system/objects/types.rst:51 +#: ../system/integrations/gitlab.rst:4 msgid "" -"This setting helps the user by highlighting the day from now plus the " -"provided value. It *does not* pre-fill the field." +"Use GitLab integration to track GitLab issues directly within Zammad " +"tickets. Add issue hyperlinks and get a live summary of metadata like status " +"(open/closed), assignee, labels, and more." msgstr "" +"Use a integração do GitLab para rastrear problemas do GitLab diretamente nos " +"chamados do Zammad. Adicione hiperlinks de problemas e obtenha um resumo em " +"tempo real de metadados, como status (aberto/fechado), atribuição, etiquetas " +"e muito mais." -#: ../system/objects/types.rst:0 -msgid "Available settings for Date fields" +#: ../system/integrations/gitlab.rst:8 +#, fuzzy +msgid "" +"Please note that our GitLab integration does not support merge requests." msgstr "" +"A integração do GitLab não oferece suporte a solicitações de mesclagem." -#: ../system/objects/types.rst:73 -msgid "Date & time field" +#: ../system/integrations/gitlab.rst:None +msgid "Integration page for GitLab" msgstr "" -#: ../system/objects/types.rst:58 -msgid "Provides a date and time picker – does not allow default values" +#: ../system/integrations/gitlab.rst:18 +#, fuzzy +msgid "" +"In your GitLab preferences, create a new API token under **Access Tokens**." msgstr "" +"Nas preferências do GitLab, crie um novo token de API em **Tokens de " +"acesso**." -#: ../system/objects/types.rst:62 -msgid "Allow future" -msgstr "" +#: ../system/integrations/gitlab.rst:20 +#, fuzzy +msgid "Under **Select scopes**, choose ``read_api`` only." +msgstr "Em **Selecionar escopos**, escolha apenas ``read_api``." -#: ../system/objects/types.rst:0 -msgid "Forbid dates and times in the future." +#: ../system/integrations/gitlab.rst:27 +msgid "🔒 **If you wish to link issues on any private repos...**" msgstr "" +"🔒 **Se você deseja vincular problemas em qualquer repositório privado...**" -#: ../system/objects/types.rst:66 -msgid "Allow past" +#: ../system/integrations/gitlab.rst:29 +msgid "Your API token must belong to an account with access to those repos." msgstr "" +"Seu token de API deve pertencer a uma conta com acesso a esses repositórios." -#: ../system/objects/types.rst:0 -msgid "Forbid dates and times in the past." +#: ../system/integrations/gitlab.rst:31 +msgid "Enter your new API token in Zammad and enable GitLab integration." msgstr "" +"Insira seu novo token de API no Zammad e habilite a integração com o Gitlab." -#: ../system/objects/types.rst:70 -msgid "Default time diff (minutes)" +#: ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to configure Zammad's GitLab integration" msgstr "" -#: ../system/objects/types.rst:69 +#: ../system/integrations/gitlab.rst:40 +#, fuzzy msgid "" -"This setting helps the user by highlighting the day from now plus the " -"provided value. It does not pre-fill the field." +"Use the default API endpoint (``https://gitlab.com/api/graphql``) unless " +"you're a self-hosted GitLab user." msgstr "" +"Deixe o endpoint padrão da API (``https://gitlab.com/api/graphql``) como " +"está, a menos que você seja um usuário Gitlab auto-hospedado." -#: ../system/objects/types.rst:0 -msgid "Available settings for Date & time fields" +#: ../system/integrations/gitlab.rst:43 +msgid "" +"Once completed, a new GitLab issues tab will appear in the ticket pane. 🎉" msgstr "" +"Após concluído, uma nova guia de problemas do Gitlab aparecerá no painel do " +"chamado. 🎉" -#: ../system/objects/types.rst:86 +#: ../system/integrations/gitlab.rst:51 #, fuzzy -msgid "Integer field" -msgstr "Inteiro" - -#: ../system/objects/types.rst:76 msgid "" -"Provides an input field that allows integer usage only. You may define a " -"default value. You cannot enforce comma separation." -msgstr "" - -#: ../system/objects/types.rst:80 -msgid "Minimal" +"Self-hosted administrators, please check your network settings to ensure " +"that your Zammad server can reach ``gitlab.com``." msgstr "" +"Administradores de ambientes auto-hospedados, verifique suas configurações " +"de rede para garantir que seu servidor Zammad pode acessar gitlab.com." -#: ../system/objects/types.rst:80 -msgid "The minimal value the field accepts." +#: ../system/integrations/i-doit.rst:2 +msgid "i-doit" msgstr "" -#: ../system/objects/types.rst:83 -msgid "Maximal" +#: ../system/integrations/i-doit.rst:4 +msgid "" +"`i-doit `_ is an open-source **configuration " +"management database** - in other words, a tool for keeping tabs on every " +"single piece of your physical and digital infrastructure, from network " +"equipment to virtual machines on down to the faceplates on your rack shelves " +"and more." msgstr "" -#: ../system/objects/types.rst:83 -msgid "The maximum value the field accepts." +#: ../system/integrations/i-doit.rst:10 +msgid "" +"What's that got to do with Zammad? Well, if you used tickets to track issues " +"with all that hardware, you might start wishing there was a way they could " +"talk to each other." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Integer fields" +#: ../system/integrations/i-doit.rst:14 +msgid "Zammad gives you two:" msgstr "" -#: ../system/objects/types.rst:99 -msgid "Multiple selection field" +#: ../system/integrations/i-doit.rst:17 +msgid "1. Add i-doit Links to Zammad Tickets" msgstr "" -#: ../system/objects/types.rst:89 -msgid "" -"Provides a selection field that allows the selection of one or more out of " -"several. This field does allow setting a default value." +#: ../system/integrations/i-doit.rst:20 ../system/integrations/i-doit.rst:80 +msgid "What Users See" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Multiple selection fields" +#: ../system/integrations/i-doit.rst:26 +msgid "i-doit integration in Zammad's ticket pane" msgstr "" -#: ../system/objects/types.rst:112 -msgid "Single selection field" +#: ../system/integrations/i-doit.rst:26 +msgid "" +"The i-doit integration will appear under a new 🖨 tab in the ticket pane." msgstr "" -#: ../system/objects/types.rst:102 +#: ../system/integrations/i-doit.rst:28 msgid "" -"Provides a drop-down field that allows selection of one value out of " -"several. This field does allow setting a default value." +"i-doit integration puts a new tab in Zammad's ticket pane where you can add " +"links to existing i-doit devices for easy reference. (See our :user-docs:" +"`user documentation ` to learn " +"how it works in practice)." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Single selection fields" +#: ../system/integrations/i-doit.rst:36 ../system/integrations/i-doit.rst:93 +msgid "How to Set it Up" msgstr "" -#: ../system/objects/types.rst:142 -#, fuzzy -msgid "Textarea field" -msgstr "Texto" - -#: ../system/objects/types.rst:115 +#: ../system/integrations/i-doit.rst:38 msgid "" -"Provides a text area input field (multiple lines) and thus allows e.g. new " -"lines. You can set a default field value." +"It requires i-doit's `API Add-on `_. Make sure to have it properly set up. Use the following setting:" msgstr "" -#: ../system/objects/types.rst:120 -msgid "" -"Please note that this field *does not* support text formatting or HTML " -"content (rich text)." +#: ../system/integrations/i-doit.rst:42 +msgid "Active: ``Yes``" msgstr "" -#: ../system/objects/types.rst:123 -msgid "**🥵 This field can consume a lot of visual space**" +#: ../system/integrations/i-doit.rst:43 +msgid "Enforce authentication by username and password: ``No``" msgstr "" -#: ../system/objects/types.rst:125 +#: ../system/integrations/i-doit.rst:45 msgid "" -"Depending on where you use this field type, it may use a lot of visual space " -"if you provide a lot of text. This may be an issue to work with." +"To set it up, enable the integration in the Zammad admin panel under " +"**System > Integrations > i-doit**:" msgstr "" -#: ../system/objects/types.rst:130 -msgid "Default" +#: ../system/integrations/i-doit.rst:None +msgid "i-doit settings within the integration pages" msgstr "" -#: ../system/objects/types.rst:129 -msgid "" -"The here provided text will be shown within the text area field or new data " -"sets." +#: ../system/integrations/i-doit.rst:53 +msgid "The root URL of your i-doit installation." msgstr "" -#: ../system/objects/types.rst:134 ../system/objects/types.rst:160 -msgid "Maxlength" +#: ../system/integrations/i-doit.rst:62 +msgid "API token" msgstr "" -#: ../system/objects/types.rst:0 ../system/objects/types.rst:160 -msgid "You can pick the maximum length of the field." +#: ../system/integrations/i-doit.rst:56 +msgid "" +"Found in the i-doit admin panel under **Interfaces / external data > JSON-" +"RPC API > Common Settings**." msgstr "" -#: ../system/objects/types.rst:0 -msgid "The default length of this object is ``500``." +#: ../system/integrations/i-doit.rst:0 +msgid "i-doit administration interface with API configuration" msgstr "" -#: ../system/objects/types.rst:139 -msgid "Rows" +#: ../system/integrations/i-doit.rst:67 +msgid "Client ID" msgstr "" -#: ../system/objects/types.rst:0 -msgid "" -"Change the number of rows to dislay so that you can use only the space you " -"really need." +#: ../system/integrations/i-doit.rst:65 +msgid "A unique name to identify Zammad within i-doit." msgstr "" -#: ../system/objects/types.rst:0 -msgid "The default number of rows is ``4``." +#: ../system/integrations/i-doit.rst:67 +msgid "(Zammad does not require you to enter a value here, but i-doit might!)" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Textarea fields" +#: ../system/integrations/i-doit.rst:70 +msgid "" +"Here you can decide if the certificate of your i-doit system has to be " +"verified or not. In case you are using custom certificates, please have a " +"look at :doc:`how to add them to Zammad `." msgstr "" -#: ../system/objects/types.rst:165 -msgid "Text field" +#: ../system/integrations/i-doit.rst:77 +msgid "2. List / Create Zammad Tickets in i-doit" msgstr "" -#: ../system/objects/types.rst:145 -msgid "Provides a text field (one line) and allows choosing a default value." +#: ../system/integrations/i-doit.rst:None +msgid "Zammad integration in i-doit's device view" msgstr "" -#: ../system/objects/types.rst:148 +#: ../system/integrations/i-doit.rst:86 msgid "" -"Defines the type of the input field. This allows e.g. your browser to ensure " -"that you provide the specific type." +"i-doit's ticket system integration gives you a way to see all the tickets " +"for a given device without ever leaving i-doit. (See our :user-docs:`user " +"documentation ` to learn how it " +"works in practice)." msgstr "" -#: ../system/objects/types.rst:152 -msgid "Currently available:" +#: ../system/integrations/i-doit.rst:95 +msgid "" +"Enable this integration in the i-doit admin panel under **Interfaces / " +"external data > Trouble Ticket System (TTS) > Configuration**:" msgstr "" -#: ../system/objects/types.rst:155 -msgid "Phone" +#: ../system/integrations/i-doit.rst:None +msgid "i-doit administration interface with TTS configuration" msgstr "" -#: ../system/objects/types.rst:156 -msgid "Text" -msgstr "Texto" +#: ../system/integrations/i-doit.rst:104 +msgid "TTS-Type" +msgstr "" -#: ../system/objects/types.rst:157 -msgid "Url *(URL fields disable link-template availability)*" +#: ../system/integrations/i-doit.rst:104 +msgid "``Zammad``" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Text fields" +#: ../system/integrations/i-doit.rst:115 +msgid "Username / Password" msgstr "" -#: ../system/objects/types.rst:174 -msgid "Single tree selection field" +#: ../system/integrations/i-doit.rst:107 +msgid "Login credentials for a Zammad agent." msgstr "" -#: ../system/objects/types.rst:168 +#: ../system/integrations/i-doit.rst:109 msgid "" -"Provides a select-like field with up to 6 layers of options. Does not allow " -"setting a default value." +"This agent must have **read permission** for all :doc:`groups ` that plan on using the i-doit integration." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Tree Select fields" +#: ../system/integrations/i-doit.rst:113 +msgid "" +"You may even wish to create a dedicated agent account just for this " +"integration (otherwise, if the agent ever changes her password, you will " +"have to remember to update it here)." msgstr "" -#: ../system/objects/types.rst:183 -msgid "Multiple tree selection field" +#: ../system/integrations/i-doit.rst:117 +msgid "URL incl. protocol" msgstr "" -#: ../system/objects/types.rst:177 -msgid "" -"Provides a select-like field with up to 6 layers of options allowing the " -"selection of multiple values. Does not allow setting a default value." +#: ../system/integrations/i-doit.rst:118 +msgid "``https://your.zammad.domain``" msgstr "" -#: ../system/objects/types.rst:302 -msgid "External Data Source field" -msgstr "" +#: ../system/integrations/index.rst:2 +msgid "Integrations" +msgstr "Integrações" -#: ../system/objects/types.rst:186 +#: ../system/integrations/index.rst:4 msgid "" -"Provides a searchable field which fetches data from an external system. This " -"can be useful if you have data outside of Zammad and don't want to maintain " -"both data sources." +"Zammad offers numerous integrations that add rich features to your instance." msgstr "" +"Zammad oferece inúmeras integrações e funcionalidades para sua instância." -#: ../system/objects/types.rst:190 -msgid "The feature works as follows:" +#: ../system/integrations/index.rst:6 +msgid "We're still working on this part of our documentation, stay tight!" msgstr "" +"Ainda estamos trabalhando nesta parte da nossa documentação, aguente firme!" -#: ../system/objects/types.rst:192 -msgid "" -"Zammad sends a query with a search string (free text from agent or based on " -"a variable) in a pre-defined format (\"Search URL\") to an external system." -msgstr "" +#: ../system/integrations/index.rst:10 +#, fuzzy +msgid "Integrations for Phone Systems" +msgstr "Integrações para sistemas de telefonia" -#: ../system/objects/types.rst:195 +#: ../system/integrations/index.rst:14 msgid "" -"This external system searches for matches and provides a response as a JSON " -"structure to Zammad." +"Your VoIP provider or telephony system is not listed? Possibly your provider " +"supports Zammad by using the generic CTI - if you're unsure ask your " +"provider." msgstr "" -#: ../system/objects/types.rst:197 +#: ../system/integrations/index.rst:18 msgid "" -"Zammad just looks for the defined list and value keys, reads the content and " -"displays the value to the user. There is no search on Zammad side." +"Provider does not support Zammad? Consider creating a `feature request in " +"the Zammad Community `_." msgstr "" -#: ../system/objects/types.rst:201 -msgid "" -"The usage of a PostgreSQL database for Zammad is required. In any other " -"case, Zammad will hide the external data source type and you are not able to " -"use it. If you want to use this feature, consider to :docs:`migrate your " -"database `." -msgstr "" +#: ../system/integrations/index.rst:31 +#, fuzzy +msgid "Integrations for Authentication and Customers" +msgstr "Integrações para autenticação e clientes" -#: ../system/objects/types.rst:205 -msgid "Currently, only ``GET`` is supported as request method." -msgstr "" +#: ../system/integrations/index.rst:44 +msgid "Integrations for Monitoring Systems" +msgstr "Integrações para Sistemas de Monitoramento" -#: ../system/objects/types.rst:206 -msgid "" -"The data structure must be in JSON format and provide the objects in an " -"array." -msgstr "" +#: ../system/integrations/index.rst:46 +msgid "This section currently misses the following integrations:" +msgstr "Esta sessão atualmente carece das seguintes integrações:" -#: ../system/objects/types.rst:208 -msgid "" -"The endpoint for the external data source has to support search. On Zammad " -"side, there is no search/logic implemented; however, you can define the " -"output key and value based on the result(s) from the response (which " -"provides already filtered content based on the search)." -msgstr "" +#: ../system/integrations/index.rst:48 +msgid "Icinga" +msgstr "Icinga" -#: ../system/objects/types.rst:212 -msgid "" -"If you receive more results as expected, your external data source search " -"may not work properly or the structure of the URL is not correct. You should " -"get in touch with a responsible person from the external system." +#: ../system/integrations/index.rst:49 +msgid "Monit" +msgstr "Monit" + +#: ../system/integrations/index.rst:50 +msgid "Nagios" +msgstr "Nagios" + +#: ../system/integrations/index.rst:60 +msgid "Integrations for Issue Trackers" msgstr "" -#: ../system/objects/types.rst:217 +#: ../system/integrations/index.rst:70 +msgid "Other Integrations" +msgstr "Outras Integrações" + +#: ../system/integrations/index.rst:72 msgid "" -"Please have a look :doc:`at our example `, where you can find a possible configuration for a public " -"dummy endpoint." +"This section will hold any other integration that can't be grouped up (yet)." msgstr "" +"Esta sessão armazenará todas as outras integrações que não puderam ser " +"agrupadas (ainda)." -#: ../system/objects/types.rst:0 -msgid "Available settings for external data source fields" -msgstr "" +#: ../system/integrations/ldap/index.rst:2 +msgid "LDAP / Active Directory" +msgstr "LDAP / Active Directory" -#: ../system/objects/types.rst:242 -msgid "Search URL" +#: ../system/integrations/ldap/index.rst:4 +msgid "" +"Zammad comes with a powerful LDAP integration that allows you to have a " +"single source of truth. By this you reduce the number of login credentials " +"your user has to remember." msgstr "" -#: ../system/objects/types.rst:227 +#: ../system/integrations/ldap/index.rst:10 msgid "" -"Set your endpoint where Zammad fetches the data. Please make sure to include " -"a valid search :doc:`variable <../variables>` as an URL parameter. Example " -"for a free text search at user input: ``#{search.term}``" +"The LDAP source is also a perfect candidate for Zammad's :docs:`Kerberos " +"Single Sign-On ` but also works as addition " +"to other :doc:`/settings/security/third-party`." msgstr "" -#: ../system/objects/types.rst:232 -msgid "" -"If in doubt, ask the responsible person for the external data source how " -"they expect the strucuture of the URL." +#: ../system/integrations/ldap/index.rst:None +msgid "Zammands LDAP management page" msgstr "" -#: ../system/objects/types.rst:236 -msgid "" -"Depending on your search variable, the preview might work or not. The reason " -"is that the context might not be available and it is no bug." +#: ../system/integrations/ldap/index.rst:25 +msgid "📝 :doc:`manage`" msgstr "" -#: ../system/objects/types.rst:239 -msgid "" -"Please also make sure to use a variable which is available in your object " -"context. For example you won't be able to search for a ticket in a user " -"object context." +#: ../system/integrations/ldap/index.rst:25 +msgid "Add, modify, remove or re-arrange your LDAP-Sources as needed." msgstr "" -#: ../system/objects/types.rst:252 +#: ../system/integrations/ldap/index.rst:30 #, fuzzy -msgid "SSL Verification" -msgstr "Limitação" +msgid "Before you continue, please note the following limitations." +msgstr "Lá você poderá editar as seguintes configurações:" -#: ../system/objects/types.rst:245 -msgid "Here you can switch the SSL verification to no." +#: ../system/integrations/ldap/index.rst:32 +msgid "Mapping / Synchronizing organizations is not possible" msgstr "" -#: ../system/objects/types.rst:249 +#: ../system/integrations/ldap/index.rst:36 msgid "" -"If your external data source system is using self signed certificates, " -"please have a look :doc:`here ` for " -"further information about how to handle them in Zammad, so you can keep the " -"SSL verification activated." +"You may want to consider using domain based assignments to overcome this " +"issue. Learn more on :doc:`/manage/organizations/index`." msgstr "" -#: ../system/objects/types.rst:258 -msgid "HTTP Authentication" +#: ../system/integrations/ldap/index.rst:39 +msgid "" +"Zammad's LDAP sync is one way. Editing user settings or permissions may be " +"overwritten upon the next sync depending on your configuration." msgstr "" -#: ../system/objects/types.rst:255 -msgid "" -"If your external data source requires an authentication, you can set it " -"here. You can leave it empty or choose between *Basic Authentication* or " -"*Authentication Token* (selecting one of the two methods leads to additional " -"fields where you can enter your credentials/token)." +#: ../system/integrations/ldap/index.rst:41 +msgid "Nested groups are not supported." msgstr "" -#: ../system/objects/types.rst:265 -msgid "Search result list key" +#: ../system/integrations/ldap/index.rst:42 +msgid "Synchronizing user avatars from LDAP is not supported." msgstr "" -#: ../system/objects/types.rst:261 +#: ../system/integrations/ldap/index.rst:43 +msgid "Unlike user filters, group filters cannot be changed." +msgstr "" + +#: ../system/integrations/ldap/index.rst:44 msgid "" -"Defines the level in the JSON structure which provides the list with search " -"results. You can leave it empty, if the data is already provided as an " -"array. If you have to go deeper in the structure, you can provide a path " -"with ``.`` as separators, e.g. ``key.subkey.sub-sub-key``." +"When a user originates from an LDAP server, Zammad will try to verify the " +"login credentials against LDAP first - if this fails Zammad will check its " +"local database." msgstr "" -#: ../system/objects/types.rst:271 -msgid "Search result value key" +#: ../system/integrations/ldap/index.rst:50 +msgid "" +"Users can have local passwords even if they're LDAP users! You can learn " +"more about user accounts in general on :doc:`/manage/users/index`." msgstr "" -#: ../system/objects/types.rst:268 +#: ../system/integrations/ldap/index.rst:54 msgid "" -"Defines the attribute in the structure in which your external data source " -"provides the *value* for your data. An example would be a product *number*. " -"If you have to go deeper in the structure, you can provide a path with ``.`` " -"as separators, e.g. ``key.subkey.sub-sub-key``." +"When several LDAP sources contain the same user (meaning the same email " +"address), the user in question will be updated with every source configured. " +"*The last LDAP source will win.*" msgstr "" -#: ../system/objects/types.rst:277 -msgid "Search result label key" +#: ../system/integrations/ldap/index.rst:58 +msgid "" +"This is subject to change with `Issue 4109 `_ in the future." msgstr "" -#: ../system/objects/types.rst:274 +#: ../system/integrations/ldap/index.rst:60 msgid "" -"Defines the attribute in the structure in which your external data source " -"provides the *label* for your data. An example would be a product *name*. If " -"you have to go deeper in the structure, you can provide a path with ``.`` as " -"separators, e.g. ``key.subkey.sub-sub-key``." +"Synchronization statistics currently affect *all* configured LDAP sources. " +"This also applies for newly added or updated sources." msgstr "" -#: ../system/objects/types.rst:280 +#: ../system/integrations/ldap/index.rst:63 msgid "" -"In the preview area, you can find the following items (depending on your " -"configuration above):" +"This is subject to change with `Issue 4108 `_ in the future." msgstr "" -#: ../system/objects/types.rst:283 +#: ../system/integrations/ldap/index.rst:65 msgid "" -"**Error/hint message** (only if configuration is not complete): Zammad tells " -"you, if there is a problem and what you should change in your configuration." +"Zammad currently has limited fallback server support. You can workaround " +"this by providing several sources - however, ensure to have the exact same " +"configuration on your fallback." msgstr "" -#: ../system/objects/types.rst:286 +#: ../system/integrations/ldap/index.rst:69 msgid "" -"**Search field**: search for an existing attribute in the data source to get " -"a preview. This is required for the fields below to show up." +"This is subject to improve with `Issue 4107 `_ in the future." msgstr "" -#: ../system/objects/types.rst:288 +#: ../system/integrations/ldap/index.rst:76 msgid "" -"**Search result response** (only if configuration is not complete): here you " -"can find a syntax highlighted JSON preview of the response, based on the " -"search term you entered." +"This section holds all requests Zammad handled for all LDAP sources. These " +"entries can either contain synchronization information or logins " +"(authentication attempts via Zammad's login interface)." msgstr "" -#: ../system/objects/types.rst:291 +#: ../system/integrations/ldap/index.rst:80 msgid "" -"**Search result list** (only if *search result list key* is properly set): " -"output of the structure under the configured *search result list key*." +"By clicking on any request, Zammad will provide even more information. The " +"provided information can be useful when something does not work as expected." msgstr "" -#: ../system/objects/types.rst:294 +#: ../system/integrations/ldap/index.rst:85 msgid "" -"**Preview table** (when fully configured): Zammad shows you a table which " -"includes the found items based on the search string (value, label and " -"optional link). You can use this preview if you don't have the complete data " -"structure of the external system in mind." +"Especially a LDAP synchronization can cause many log entries. The web " +"interface will always limit the number of shown entries to the last 50 " +"entries." msgstr "" -#: ../system/objects/types.rst:299 +#: ../system/integrations/ldap/index.rst:None msgid "" -"An example of a configured external data source field from agent perspective:" +"Screencast showing LDAP integration log entries and a detail view on\n" +"an entry." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Screencast showing the search for a product in a ticket" +#: ../system/integrations/ldap/manage.rst:2 +msgid "Manage LDAP-Sources" msgstr "" -#: ../system/objects/types.rst:307 -msgid "URL fields (Link-Template)" +#: ../system/integrations/ldap/manage.rst:6 +msgid "" +"Please keep in mind all current limitations for the LDAP synchronization. " +"This will help to understand scopes of the following operations better." msgstr "" -#: ../system/objects/types.rst:311 -msgid "" -"This function is restricted to Text, Select and External data source types " -"only." +#: ../system/integrations/ldap/manage.rst:65 +msgid "Add new source" msgstr "" -#: ../system/objects/types.rst:314 +#: ../system/integrations/ldap/manage.rst:10 msgid "" -"Link-Templates are an amazing way to dynamically generate URLs. They allow " -"you to integrate other systems better without having to manually copy data " -"from Zammad if possible." +"Using the *New Source* button allows you to add new LDAP sources to your " +"installation. You're not limited in the number of sources, however, keep in " +"mind that many sources will also take more time to synchronize." msgstr "" -#: ../system/objects/types.rst:320 +#: ../system/integrations/ldap/manage.rst:14 msgid "" -"Another great way of communicating with another system may be Zammad's :doc:" -"`Webhooks `." +"You can choose between different encryption types, namely *SSL* and " +"*STARTTLS* or none of them (\"*No SSL*\"). If you choose *SSL* or " +"*STARTTLS*, Zammad will display an additional *SSL verification* option that " +"allows you to disable the verification, e.g. for self-signed SSL " +"certificates. You can also tell Zammad to use a different port by appending " +"``:`` to your hostname/IP." msgstr "" -#: ../system/objects/types.rst:323 +#: ../system/integrations/ldap/manage.rst:0 msgid "" -"After filling a link-template enabled field, an URL icon will appear on its " -"right. Clicking on the icon opens a new tab." +"Screenshot of configuring a new LDAP source with SSL encryption and SSL " +"verification" msgstr "" -#: ../system/objects/types.rst:328 +#: ../system/integrations/ldap/manage.rst:26 msgid "" -"Even though Zammad displays the link template within object edit and create " -"screens, the function is optional. It's only active if you populate the " -"field." +"New Source with SSL transport security enabled and certificate verification" msgstr "" -#: ../system/objects/types.rst:333 +#: ../system/integrations/ldap/manage.rst:30 msgid "" -"What's the difference between URL and text fields with link template...?!" +"Using an user filter can be a good idea if you only require a small subset " +"of your LDAP users in Zammad." msgstr "" -#: ../system/objects/types.rst:335 -msgid "" -"Both fields have different use cases. Use ``text`` type text fields when " -"ever you have a *static* url that requires dynamic parameters. If you " -"require a drag & drop like field that you can put in any URL, use ``URL`` " -"type text fields." +#: ../system/integrations/ldap/manage.rst:42 +msgid "This especially affects inactive users" msgstr "" -#: ../system/objects/types.rst:340 +#: ../system/integrations/ldap/manage.rst:34 msgid "" -"The difference is easier to spot when comparing the fields directly, below " -"screencast shows the result - the dynamic approach uses existing values in " -"the moment of updating to built the URL - e.g. ``https://google.com/search?" -"q=cookies`` - while the URL approach uses the actual URL of the field - e.g. " -"``https://zammad.com``." +"As every LDAP behaves differently on which attributes and how they are set, " +"Zammad doesn't care about any flags." msgstr "" -#: ../system/objects/types.rst:None +#: ../system/integrations/ldap/manage.rst:37 msgid "" -"Screencast showing the differents in between URL and text type fields with " -"actual values" +"Users that no longer are returned by your LDAP source will automatically be " +"set to inactive. Zammad assumes that the user was deactivated." msgstr "" -#: ../system/objects/types.rst:352 -msgid "How does this work...?!" -msgstr "Como isso funciona...?!" - -#: ../system/objects/types.rst:354 +#: ../system/integrations/ldap/manage.rst:41 msgid "" -"As an example, let's say you have an attribute called ``amazing_attribute`` " -"and you want to open a google search directly with the input from that field." +"Users will never be removed automatically! If you want to remove obsolete " +"users, use :doc:`/system/data-privacy`." msgstr "" -#: ../system/objects/types.rst:357 +#: ../system/integrations/ldap/manage.rst:46 +#, fuzzy +msgid "Active Directory admins" +msgstr "LDAP / Active Directory" + +#: ../system/integrations/ldap/manage.rst:45 msgid "" -"Providing the link-template field below allows you to do so: ``https://www." -"google.com/search?q=#{ticket.amazing_attribute}``" +"Active Directories are quite specific on how to filter for active users only " +"- please see the `Microsoft documentation `_ for more " +"information." msgstr "" -#: ../system/objects/types.rst:362 +#: ../system/integrations/ldap/manage.rst:51 msgid "" -"You can use any :doc:`Zammad variable ` as long as it's " -"available in the moment you need it." +"*Do not* manually write pathes of either LDAP attributes or groups. If " +"Zammad does not display them, it either cannot find them or you have a lot " +"of users that don't have the attributes populated." msgstr "" -#: ../system/objects/types.rst:365 +#: ../system/integrations/ldap/manage.rst:55 msgid "" -"As a result, you are redirected to Google with a search for the value of the " -"attribute, if you click on the button in the ticket (as you can see in the " -"screencast above)." +"Zammad will always only return attributes that are filled - this reduces the " +"returned list of attributes greatly." msgstr "" -#: ../system/packages.rst:2 -msgid "Packages" -msgstr "Pacotes" - -#: ../system/packages.rst:4 -msgid "That's the package management-area." -msgstr "Esta é a área de gerenciamento de pacotes." - -#: ../system/packages.rst:6 -msgid "Individual add-ons for Zammad can be installed and managed here." +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing how to add a new LDAP source" msgstr "" -"Add-ons individuais para o Zammad podem ser instalados e gerenciados aqui." -#: ../system/sessions.rst:2 -msgid "Sessions" -msgstr "Sessões" - -#: ../system/sessions.rst:4 +#: ../system/integrations/ldap/manage.rst:63 msgid "" -"Sessions management allows reviewing currently known user sessions and " -"allows to end these. The session timeout is affected by :ref:" -"`security_session_timeout` configurations from security settings." +"If your LDAP system doesn't allow anonymous bind, Zammad detects it and " +"provides you an editable \"Base DN\" *text* field instead of a prefilled " +"*select* field." msgstr "" -#: ../system/sessions.rst:None -msgid "Screenshot showing Zammad's session management" +#: ../system/integrations/ldap/manage.rst:81 +msgid "Review or edit existing source" msgstr "" -#: ../system/sessions.rst:13 -#, fuzzy -msgid "Zammad will provide the following information:" -msgstr "Esta sessão atualmente carece das seguintes integrações:" - -#: ../system/sessions.rst:16 +#: ../system/integrations/ldap/manage.rst:68 msgid "" -"The user account this session entry belongs to. It can be normal if a user " -"has several sessions in the list. This can be due to changed browser " -"information or if you use e.g. single sign on methods where the user does " -"not use the log off button." +"Clicking on a LDAP source will provide a configuration and mapping overview." msgstr "" -#: ../system/sessions.rst:22 -msgid "Browser" +#: ../system/integrations/ldap/manage.rst:70 +msgid "" +"If needed you can then use the *Change* button to update either the name, " +"active state or the whole configuration. If you're changing the whole " +"configuration, the dialogue will be identical to the source creation." msgstr "" -#: ../system/sessions.rst:22 -msgid "The browser agent communicated to Zammad." +#: ../system/integrations/ldap/manage.rst:76 +msgid "" +"Did your LDAP server change? Different LDAP servers have different " +"structures and default attributes. This causes the LDAP synchronization to " +"likely fail. Consider removing the affected source and re-add it." msgstr "" -#: ../system/sessions.rst:40 -#, fuzzy -msgid "Location" -msgstr "Limitação" - -#: ../system/sessions.rst:25 -msgid "" -"The anticipated location based on the users IP address. Depending on the IP " -"address the result shown may differ. This option depends on :doc:`/settings/" -"system/services`." +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing the update of the source name." msgstr "" -#: ../system/sessions.rst:29 -msgid "The following information can be shown:" +#: ../system/integrations/ldap/manage.rst:89 +msgid "Re-arrange LDAP source's order" msgstr "" -#: ../system/sessions.rst:33 -msgid "IP address" +#: ../system/integrations/ldap/manage.rst:84 +msgid "" +"You can change the synchronization order for each source at any time. Zammad " +"will synchronize the sources from top to bottom." msgstr "" -#: ../system/sessions.rst:32 +#: ../system/integrations/ldap/manage.rst:0 msgid "" -"Either if you set *Geo IP services* to inactive or you're using internal IP " -"address which do not provide location information." +"Screencasting showing how to change the source order by using\n" +"drag and drop." msgstr "" -#: ../system/sessions.rst:40 -msgid "Country (or Country + City)" +#: ../system/integrations/ldap/manage.rst:101 +msgid "Remove a source" msgstr "" -#: ../system/sessions.rst:36 +#: ../system/integrations/ldap/manage.rst:92 msgid "" -"If *Geo IP services* is enabled only. Depends on how detailed the available " -"IP address information are." +"If you no longer need the a LDAP source or simply want to start over, you " +"can remove them at any time. This will not remove synchronized users, data " +"synchronized or permissions." msgstr "" -#: ../system/sessions.rst:39 +#: ../system/integrations/ldap/manage.rst:98 msgid "" -"Be aware that results can be inaccurate - this technically is not an error." +"Not sure if you'd need the source later on? Set the source to inactive " +"instead of removing it - see *Review or edit existing source* for more." msgstr "" -#: ../system/sessions.rst:43 -msgid "Age" +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing how to remove LDAP sources." msgstr "" -#: ../system/sessions.rst:43 -msgid "Provides the time when the session initially has been created." +#: ../system/integrations/pgp/index.rst:2 +msgid "PGP" msgstr "" -#: ../system/sessions.rst:50 -#, fuzzy -msgid "Update" -msgstr "Tempo de atualização" - -#: ../system/sessions.rst:46 +#: ../system/integrations/pgp/index.rst:7 msgid "" -"Provides the time the user used this session to open Zammad. This timestamp " -"is only updated if the user e.g. reloads, not during normal work on tickets." +"Pretty Good Privacy (PGP) is another method for secure email communication. " +"With PGP, you can exchange **signed** and **encrypted** messages with others." msgstr "" -#: ../system/sessions.rst:50 -msgid "This timestamp is being used for the session timeout." +#: ../system/integrations/pgp/index.rst:13 +#: ../system/integrations/smime/index.rst:17 +msgid "Signing" msgstr "" -#: ../system/sessions.rst:53 -msgid "" -"Use the delete button to remove a single session on behalf of your user." +#: ../system/integrations/pgp/index.rst:11 +msgid "is a proof that a message hasn't been manipulated on its way." msgstr "" -#: ../system/subscription/billing.rst:2 -msgid "Billing" +#: ../system/integrations/pgp/index.rst:13 +msgid "" +"In other words, it guarantees message **integrity** and **authenticity**." msgstr "" -#: ../system/subscription/billing.rst:4 -msgid "" -"Within the billing tab you can control all billing relevant information like " -"invoices, billing address and the option to cancel your subscription." +#: ../system/integrations/pgp/index.rst:19 +#: ../system/integrations/smime/index.rst:22 +msgid "Encryption" msgstr "" -#: ../system/subscription/billing.rst:33 -msgid "Billing information" +#: ../system/integrations/pgp/index.rst:16 +#: ../system/integrations/smime/index.rst:20 +msgid "" +"scrambles a message so that it can only be unscrambled by the intended " +"recipient." msgstr "" -#: ../system/subscription/billing.rst:8 +#: ../system/integrations/pgp/index.rst:19 msgid "" -"All adjusted billing information below only affect future invoices. If your " -"invoice was issued wrong, please contact `our sales team `_." +"In other words, it guarantees message **privacy** and **data security**." msgstr "" -#: ../system/subscription/billing.rst:14 -msgid "Billing address" +#: ../system/integrations/pgp/index.rst:25 +msgid "Screenshot of ticket creation with encrypt and sign buttons" msgstr "" -#: ../system/subscription/billing.rst:13 +#: ../system/integrations/pgp/index.rst:25 msgid "" -"Provide your company address here, make sure to include the companies name " -"in case required. This address will be referenced on your invoice." +"Once PGP has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " +"appear in the ticket composer." msgstr "" -#: ../system/subscription/billing.rst:18 -msgid "VAT ID" +#: ../system/integrations/pgp/index.rst:28 +msgid "**Sign button not visible?**" msgstr "" -#: ../system/subscription/billing.rst:17 +#: ../system/integrations/pgp/index.rst:30 msgid "" -"Provide your VAT ID here. If applicable your invoice will not contain German " -"VAT. Please make sure to pay the VAT in your country as required." +"Please note that the signing of emails is based on the outgoing email " +"account. That means you have to choose a group with a sender email account, " +"which has a private key assigned." msgstr "" -#: ../system/subscription/billing.rst:27 -msgid "Billing Email Address" +#: ../system/integrations/pgp/index.rst:35 +msgid "Handling of Keys" msgstr "" -#: ../system/subscription/billing.rst:21 +#: ../system/integrations/pgp/index.rst:36 msgid "" -"Usually the instance owner (the person that registered the instance) will " -"receive all emails including the invoices. In case you have your own billing " -"department, you can provide their email address here." +"To use the PGP function, you have to enable the integration (PGP) by " +"switching the toggle to *enabled*." msgstr "" -#: ../system/subscription/billing.rst:25 +#: ../system/integrations/pgp/index.rst:39 msgid "" -"All billing relevant information will then be sent to this email address." +"You can add keys by clicking the *add key* button. The keys can be imported " +"from a file or you can paste the content of the key in the text box." msgstr "" -#: ../system/subscription/billing.rst:27 -msgid "Invoices are sent as attachment (PDF) to this email address." +#: ../system/integrations/pgp/index.rst:42 +msgid "**Which keys do I have to import?**" msgstr "" -#: ../system/subscription/billing.rst:29 +#: ../system/integrations/pgp/index.rst:44 msgid "" -"Don't forget to press the *Submit* button after you changed above settings." +"For **signing** *outgoing* emails, you have to import the private key of " +"your Zammad email account." msgstr "" -#: ../system/subscription/billing.rst:0 +#: ../system/integrations/pgp/index.rst:47 msgid "" -"Screenshot showing options for billing information within the\n" -"subscription menu" +"For **encrypting** *outgoing* emails, you have to import the public key of " +"the customer's email account." msgstr "" -#: ../system/subscription/billing.rst:70 -msgid "Payment history" +#: ../system/integrations/pgp/index.rst:50 +msgid "" +"For **verifying the signature** of signed *incoming* emails, you have to " +"import the public key of the customer." msgstr "" -#: ../system/subscription/billing.rst:36 +#: ../system/integrations/pgp/index.rst:53 msgid "" -"The payment history will display a history of all paid invoices. At this " -"point you can also download these in case you need them again." +"For **decrypting** of encrypted *incoming* emails, you have to import the " +"private key of your Zammad email account." msgstr "" -#: ../system/subscription/billing.rst:41 -msgid "" -"You will only find *paid* invoices here. Invoices that are to be billed are " -"not available before the payment is completed." +#: ../system/integrations/pgp/index.rst:57 +msgid "Import Keys From a File" msgstr "" -#: ../system/subscription/billing.rst:46 -msgid "Date" -msgstr "Data" +#: ../system/integrations/pgp/index.rst:58 +msgid "You can import keys from a file in the section **Upload key**:" +msgstr "" -#: ../system/subscription/billing.rst:46 -msgid "Date of the invoice creation." +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of adding a key via file" msgstr "" -#: ../system/subscription/billing.rst:49 -#, fuzzy -msgid "Amount" -msgstr "Contas" +#: ../system/integrations/pgp/index.rst:64 +msgid "" +"**Supported file formats:** ASCII-armor as well as binary GPG format " +"(basically any GPG supported key format) is supported here." +msgstr "" -#: ../system/subscription/billing.rst:49 -msgid "Invoice total including VAT if applicable." +#: ../system/integrations/pgp/index.rst:68 +msgid "Import Keys by Pasting the Content" msgstr "" -#: ../system/subscription/billing.rst:52 -msgid "" -"Contains contract period (monthly or yearly) and hosted plan for the " -"subscription period in question." +#: ../system/integrations/pgp/index.rst:69 +msgid "You can also paste the key's content in the section **paste key**:" msgstr "" -#: ../system/subscription/billing.rst:63 -msgid "Payment method / Service period" +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of adding a key via pasting" msgstr "" -#: ../system/subscription/billing.rst:56 +#: ../system/integrations/pgp/index.rst:75 msgid "" -"Used bank account or credit card as well as the subscription period the " -"invoice is about." +"**Supported format:** Please note that only ASCII-armor is supported here." msgstr "" -#: ../system/subscription/billing.rst:61 +#: ../system/integrations/pgp/index.rst:78 +#, fuzzy +msgid "Deleting Keys" +msgstr "Limitação" + +#: ../system/integrations/pgp/index.rst:79 msgid "" -"It might happen that the invoice date and subscription period differ. This " -"is nothing to worry about, the subscription periods will be accounted later " -"on." +"If you want to delete a specific key, you can do it by clicking on the menu " +"in the *actions* column and select **delete**:" msgstr "" -#: ../system/subscription/billing.rst:67 -msgid "Receipt" +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of deleting a key" msgstr "" -#: ../system/subscription/billing.rst:66 -msgid "" -"Use the arrow to download the invoice in question. You can download all " -"available invoices any time you need to here!" +#: ../system/integrations/pgp/index.rst:88 +msgid "Downloading Keys" msgstr "" -#: ../system/subscription/billing.rst:0 -msgid "Screenshot showing payment history of a hosted instance" +#: ../system/integrations/pgp/index.rst:89 +msgid "" +"If you want to download your keys, you can do this as well via corresponding " +"action buttons. Depending on the key, you can choose wether you want to " +"download the private or the public key." msgstr "" -#: ../system/subscription/billing.rst:94 -msgid "Do you want to cancel your subscription?" +#: ../system/integrations/pgp/index.rst:95 +#: ../system/integrations/smime/manage-certificates.rst:76 +msgid "Default Behavior" msgstr "" -#: ../system/subscription/billing.rst:73 +#: ../system/integrations/pgp/index.rst:96 msgid "" -"In case you no longer want to use Zammad's SaaS, you can cancel your " -"subscription by using the red *Yes, please cancel my subscription* button." +"Here you can adjust on per group basis, if *sign* and *encryption* is on or " +"off by default. Please be aware, that agents can always override the setting " +"for each individual article." msgstr "" -#: ../system/subscription/billing.rst:76 -msgid "" -"Your subscription will end the day after your trial or billing period ends." +#: ../system/integrations/pgp/index.rst:None +msgid "Adjusting default behavior on per group basis" msgstr "" -#: ../system/subscription/billing.rst:80 +#: ../system/integrations/pgp/index.rst:107 msgid "" -"We will remind you about your cancelled subscription several times up front. " -"After the subscription ended all instance data will be removed. A restore " -"*is not* possible after that point!" +"Here you can see the last actions regarding signing and encryption and if " +"they were successful." msgstr "" -#: ../system/subscription/billing.rst:0 -msgid "Screencast showing how to cancel a subscription" +#: ../system/integrations/pgp/index.rst:117 +msgid "**Sign button is not visible, but keys are imported.**" msgstr "" -#: ../system/subscription/billing.rst:87 -msgid "**😖 Cancelled by accident?**" +#: ../system/integrations/pgp/index.rst:115 +msgid "Did you choose a group in the ticket?" msgstr "" -#: ../system/subscription/billing.rst:89 +#: ../system/integrations/pgp/index.rst:116 msgid "" -"You can always undo the cancellation via the *Yes, undo the cancellation of " -"my subscription* button up to the last subscription day!" +"Did you import a private key for the email adress, which is used for " +"outgoing emails in the group?" +msgstr "" + +#: ../system/integrations/pgp/index.rst:122 +msgid "**How to obtain keys?**" msgstr "" -#: ../system/subscription/billing.rst:0 +#: ../system/integrations/pgp/index.rst:120 msgid "" -"Screenshot showing a red button to cancel the subscription\n" -"cancellation" +"You can create them yourself! There are some good tutorials on the web on " +"how to create them. Providing keys to Zammad is a prerequisite to use the " +"PGP feature." msgstr "" -#: ../system/subscription/index.rst:2 -#, fuzzy -msgid "Subscription (SaaS)" -msgstr "Descrição" +#: ../system/integrations/pgp/index.rst:127 +msgid "**It says a passphrase is needed, but I haven't got one.**" +msgstr "" -#: ../system/subscription/index.rst:4 +#: ../system/integrations/pgp/index.rst:125 msgid "" -"The subscription settings page allows you to configure your instances " -"package and number of agents required." +"If the key is secured with a passphrase, you have to provide it for the " +"import in Zammad. It is possible that keys may have an empty passphrase. " +"However, this is *not* recommended." +msgstr "" + +#: ../system/integrations/pgp/index.rst:132 +msgid "**How do my customers get my new key?**" msgstr "" -#: ../system/subscription/index.rst:9 +#: ../system/integrations/pgp/index.rst:130 msgid "" -"This setting section is only available for Hosted setups. If you're looking " -"for on premise support contracts, please see the `Zammad pricing page " -"`_." +"You have to provide your **public** key in advance. Your customer also has " +"to configure PGP in their email workflow and import your public key. The " +"other way round, you have to get the public key of your customer and have to " +"import it to Zammad." +msgstr "" + +#: ../system/integrations/slack.rst:2 +msgid "Slack" +msgstr "Slack" + +#: ../system/integrations/slack.rst:4 +msgid "**⚠️ Deprecation warning ⚠️**" msgstr "" -#: ../system/subscription/index.rst:20 +#: ../system/integrations/slack.rst:6 msgid "" -"The subscription section currently consists of two tabs: Plan & Billing. For " -"your overview we've divided those two tabs into independent sub pages:" -msgstr "" - -#: ../system/subscription/index.rst:25 -msgid ":doc:`💰 Subscription plan `" +"Zammad 7 will no longer support this dedicated Slack integration. It is " +"recommended to switch to :doc:`pre-defined webhooks ` instead. Existing Slack integrations should " +"be migrated manually before this feature is dropped." msgstr "" -#: ../system/subscription/index.rst:24 +#: ../system/integrations/slack.rst:14 msgid "" -"Everything affecting your instance subscription functions like number of " -"agents, package and payment method." +"In order to use this feature, please add a new Slack app to your Workspace. " +"The App you need is called ``Incoming WebHooks`` ." msgstr "" -#: ../system/subscription/index.rst:28 -msgid ":doc:`🧾 Subscription billing `" -msgstr "" +#: ../system/integrations/slack.rst:18 +#, fuzzy +msgid "Why Do I Need This Feature?" +msgstr "Porque eu preciso desta funcionalidade?" -#: ../system/subscription/index.rst:28 +#: ../system/integrations/slack.rst:20 msgid "" -"Everything regarding billing address, invoices and account cancellation." -msgstr "" - -#: ../system/subscription/index.rst:33 -msgid "FAQ" +"If you're already using Slack for your team communication, you'll love this " +"feature! Our Slack integration can push ticket notifications about the last " +"ticket article based on the following events:" msgstr "" -#: ../system/subscription/index.rst:37 -msgid "I set up a trial account but am missing functions to test" -msgstr "" +#: ../system/integrations/slack.rst:24 +msgid "on Ticket creation" +msgstr "na criação do Chamado" -#: ../system/subscription/index.rst:36 -msgid "" -"The trial instance is running within the professional package allowing up to " -"three agents." +#: ../system/integrations/slack.rst:25 +msgid "on Ticket updates" msgstr "" -#: ../system/subscription/index.rst:40 -msgid "Can I change package within the trial?" +#: ../system/integrations/slack.rst:26 +msgid "on reached reminders" msgstr "" -#: ../system/subscription/index.rst:40 -msgid "No. As soon as the package is changed the subscription begins." -msgstr "" +#: ../system/integrations/slack.rst:27 +msgid "a Ticket has escalated" +msgstr "o Chamado foi escalonado" -#: ../system/subscription/index.rst:45 -msgid "What happens to my trial instance after the trial period ended?" +#: ../system/integrations/slack.rst:28 +msgid "a Ticket is going to escalate" msgstr "" -#: ../system/subscription/index.rst:43 +#: ../system/integrations/slack.rst:30 msgid "" -"Your instance will automatically be canceled for you. Please see *What " -"happens to my instance after it has been canceled?* for more." +"Zammad will provide the Ticket title, a direct link to the Ticket, the event " +"type (creation, updated, escalation), the customer, time and the last " +"article that has triggered the notification." msgstr "" -#: ../system/subscription/index.rst:58 -msgid "What happens to my instance after it has been canceled?" +#: ../system/integrations/slack.rst:34 +msgid "" +"This will give you further options, as you can see e.g. escalating tickets " +"that are assigned to an agent that's e.g. absent. You can interact faster, " +"as you might see problems earlier (or even before the problem gets one)." msgstr "" -#: ../system/subscription/index.rst:48 -msgid "That depends slightly on your instance state:" +#: ../system/integrations/slack.rst:38 +msgid "" +"If needed and wanted, you can even discuss directly about the topic before " +"sending an answer to the customer. Another possible use case would be a " +"agent monitoring new agents and their answers to tickets." msgstr "" -#: ../system/subscription/index.rst:54 +#: ../system/integrations/slack.rst:44 #, fuzzy -msgid "Trial instance" -msgstr "Manutenção" +msgid "Configure the Integration" +msgstr "Configure a integração" -#: ../system/subscription/index.rst:51 +#: ../system/integrations/slack.rst:46 msgid "" -"If you're still on trial, we will ice your instance and remind you once " -"again about your instance. We then will wait some days and remove your " -"instance from our system. This is the last time we will inform you by Email." +"First of all, please go to your slack workspace - go to administration => " +"Manage Apps. If you don't have an app yet, you can simply add a new one - " +"just search for ``Incoming WebHooks`` and customize the app to your needs." msgstr "" -#: ../system/subscription/index.rst:58 -#, fuzzy -msgid "Paid instance" -msgstr "Manutenção" - -#: ../system/subscription/index.rst:57 +#: ../system/integrations/slack.rst:50 msgid "" -"If you're a paying customer and canceled your subscription, the instance " -"removal will take place the day after your last subscription day." +"Choose (or create) the channel Zammad should post it's information to and " +"press on \"Add Incoming WebHooks integration\". If you're ready, copy the " +"provided WebHook URL and go to your Zammad installation." msgstr "" -#: ../system/subscription/index.rst:60 -msgid "Can removed instances be restored?" +#: ../system/integrations/slack.rst:56 +msgid "" +"You need administrative rights on the Slack Workspace. The link to the app " +"directory is normally ``https://[workspace-name].slack.com/apps`` ." msgstr "" -#: ../system/subscription/index.rst:61 -msgid "No. Once your instance has been removed, a restoration is not possible." +#: ../system/integrations/slack.rst:63 +msgid "" +"To configure the slack integration, log in to Zammad and go to Integrations " +"(System) => Slack in the admin panel." msgstr "" -#: ../system/subscription/plan.rst:2 ../system/subscription/plan.rst:38 -msgid "Plan" +#: ../system/integrations/slack.rst:66 +msgid "" +"Here you can choose on what evens Zammad should post information about a " +"ticket to your Slack channel. Next you need to device what groups shall be " +"affected by this, as anybody with access to that specific Slack channel can " +"read at least parts of the ticket this might be a privacy issue, if you " +"select the wrong groups. The username is simply the name that Zammad uses as " +"display name inside the Slack chat. The channel defines the Slack channel " +"the information is being posted in. As last option, you can set a custom " +"icon for posting to slack." msgstr "" -#: ../system/subscription/plan.rst:16 -#, fuzzy -msgid "Subscription" -msgstr "Descrição" - -#: ../system/subscription/plan.rst:5 +#: ../system/integrations/slack.rst:74 msgid "" -"On the top of the subscription summary you'll find the number of used and " -"available (booked) agent seats. By using the *see more* link you can also " -"expand an agent list to see the currently configured active agents. This " -"list *does not* count accounts with admin permissions only." +"When you're ready, just hit \"Submit\" and enable the integration. Zammad " +"will now post new ticket information based on the trigger you chose. Below " +"the options you have the recent log that shows the latest requests to Slack " +"for debugging if needed." msgstr "" -#: ../system/subscription/plan.rst:0 +#: ../system/integrations/slack.rst:81 msgid "" -"Within subscription you can always see how many agents are still\n" -"available to add and who uses the seats." +"If you leave the Icon URL empty, Zammad will use the Zammad logo instead. " +"The icon should be a square PNG file." msgstr "" -#: ../system/subscription/plan.rst:14 +#: ../system/integrations/slack.rst:90 msgid "" -"Learn more on how to manage your agents in general :doc:`here `." +"The following figure shows how it will look if you choose to receive updates " +"on created and updated tickets. On every post Zammad sends to the Slack " +"channel, you can create new threads to discuss about the new article." msgstr "" -#: ../system/subscription/plan.rst:19 +#: ../system/integrations/slack.rst:96 msgid "" -"This section gives you an overview of the available plans and their " -"functions / limits. If you require a more detailed table, check our " -"`detailed pricing table `_ for more." +"If you just want to keep track of soon escalating or already escalated " +"tickets, it will look the the following figure. Zammad changes the color in " +"front of the post so you can easily see the state of the ticket." msgstr "" -#: ../system/subscription/plan.rst:23 +#: ../system/integrations/slack.rst:102 msgid "" -"Your selection in this step will decide on the base agent price and e.g. " -"agent limits that might apply in the summary step." +"If you change the state, Zammad will also put information on what state the " +"ticket gets and (if pending state) the date until it pends. You'll also " +"recognize the color codes in front of posts on slack, as they are exact the " +"same the ticket state colors you'll see in Zammad!" msgstr "" -#: ../system/subscription/plan.rst:26 -msgid "" -"The green *Selected* button will also tell you what plan you're currently in." +#: ../system/integrations/smime/index.rst:2 +msgid "S/MIME" msgstr "" -#: ../system/subscription/plan.rst:30 +#: ../system/integrations/smime/index.rst:11 msgid "" -"Trial instances are running at Professional with 3 agents. The plan cannot " -"be changed during the trial for technical reasons, if you require more " -"agents for testing, please contact `our sales team `_ with a reason for the raise request." +"S/MIME is the most widely-supported method for secure email communication. " +"With S/MIME, you can exchange **signed** and **encrypted** messages with " +"others." msgstr "" -#: ../system/subscription/plan.rst:0 +#: ../system/integrations/smime/index.rst:15 msgid "" -"Screenshot showing three available packages for a hosted Zammad\n" -"instance" +"is proof that a message hasn't been tampered with or sent by an impersonator." msgstr "" -#: ../system/subscription/plan.rst:83 -msgid "Summary" +#: ../system/integrations/smime/index.rst:17 +msgid "" +"In other words, it guarantees a message's **integrity** and **authenticity**." msgstr "" -#: ../system/subscription/plan.rst:41 -msgid "" -"In this section you can adjust the settings of the previous selected plan." +#: ../system/integrations/smime/index.rst:22 +msgid "In other words, it guarantees **privacy** and **data security**." msgstr "" -#: ../system/subscription/plan.rst:45 -msgid "" -"Note that upgrading (more agents, higher package) is always possible, " -"however, downgrading will only happen when your billing period renews." +#: ../system/integrations/smime/index.rst:28 +msgid "Screencast demo of S/MIME features for both new tickets and replies" msgstr "" -#: ../system/subscription/plan.rst:49 +#: ../system/integrations/smime/index.rst:28 msgid "" -"Upgrading resets your billing period and existing credit will be deducted " -"from the new total." +"Once S/MIME has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " +"appear in the ticket composer." msgstr "" -#: ../system/subscription/plan.rst:58 -msgid "Billing cycle" +#: ../system/integrations/smime/index.rst:32 +msgid ":doc:`🔪 Prerequisites `" msgstr "" -#: ../system/subscription/plan.rst:53 +#: ../system/integrations/smime/index.rst:31 msgid "" -"You can choose between either monthly or yearly billing. The price per agent " -"will be cheaper if you decide for yearly billing." +"New to S/MIME? This section helps you to find certificate providers and " +"points out Limitations." msgstr "" -#: ../system/subscription/plan.rst:56 -msgid "" -"If you're still trying out things and are unsure of the right package for " -"your instance, you may want to choose monthly first and then upgrade to " -"yearly when you're sure." +#: ../system/integrations/smime/index.rst:35 +msgid ":doc:`📝 Manage Certificates `" msgstr "" -#: ../system/subscription/plan.rst:66 -msgid "Plan: (Starter|Professional|Plus) - Agents" +#: ../system/integrations/smime/index.rst:35 +msgid "Add and download certificates; configure group default behaviors." msgstr "" -#: ../system/subscription/plan.rst:61 -msgid "Choose the number of agents you require for your instance." +#: ../system/integrations/smime/index.rst:38 +msgid ":doc:`😦 Troubleshooting `" msgstr "" -#: ../system/subscription/plan.rst:63 -msgid "" -"Keep in mind that some packages may have agent limits. Depending on the " -"previous chosen package, you won't be able to exceed specific agent numbers. " -"Also note that setting less agents than currently configured is not possible." +#: ../system/integrations/smime/index.rst:38 +msgid "Took a wrong turn? About recent logs and common issues." msgstr "" -#: ../system/subscription/plan.rst:69 -msgid "Total" +#: ../system/integrations/smime/index.rst:43 +msgid "" +"For more details on how S/MIME integration works on the agent side, see the :" +"user-docs:`user docs `." msgstr "" -#: ../system/subscription/plan.rst:69 -msgid "This will be the net total you're going to be billed." +#: ../system/integrations/smime/manage-certificates.rst:2 +msgid "Manage Certificates" msgstr "" -#: ../system/subscription/plan.rst:71 +#: ../system/integrations/smime/manage-certificates.rst:4 msgid "" -"By using the *Update subscription* button, the instance package will be " -"adjusted immediately. If you didn't provide a payment method yet, Zammad " -"will request you to provide one at this point." +"S/MIME is **disabled by default**. Enable it to start adding certificates." msgstr "" -#: ../system/subscription/plan.rst:77 -msgid "" -"In case you're still within the trial period, this means that the trial will " -"be over immediately!" +#: ../system/integrations/smime/manage-certificates.rst:10 +msgid "Dialogue to add new certificates or private keys" msgstr "" -#: ../system/subscription/plan.rst:80 -msgid "Down- or upgrading during the trial period *is not* possible." +#: ../system/integrations/smime/manage-certificates.rst:10 +msgid "" +"Manage certificates in the Admin Panel under **System > Integrations > S/" +"MIME**. Certificates may be pasted in as plain text or uploaded from a file." msgstr "" -#: ../system/subscription/plan.rst:0 -msgid "Screenshot showing payment options and a pricing summary" +#: ../system/integrations/smime/manage-certificates.rst:14 +#, fuzzy +msgid "Add Certificate Data" +msgstr "Limitação" + +#: ../system/integrations/smime/manage-certificates.rst:36 +msgid "Add Certificate" msgstr "" -#: ../system/subscription/plan.rst:99 -msgid "Payment method" +#: ../system/integrations/smime/manage-certificates.rst:17 +msgid "" +"Import public-key certificates for both your own organization and your " +"contacts." msgstr "" -#: ../system/subscription/plan.rst:86 -msgid "You can pay via credit card or SEPA mandate." +#: ../system/integrations/smime/manage-certificates.rst:19 +msgid "" +"You can also add a bunch of certificates in one go by providing a single " +"file with all relevant certificates." msgstr "" -#: ../system/subscription/plan.rst:91 -msgid "Credit card" +#: ../system/integrations/smime/manage-certificates.rst:22 +msgid "🕵️ **ALWAYS verify certificates in-person or over the phone!**" msgstr "" -#: ../system/subscription/plan.rst:89 +#: ../system/integrations/smime/manage-certificates.rst:24 msgid "" -"Simply follow the dialogue by clicking *authorize* and confirm -if required " -"by your bank- your consent to Zammad using your card for the payments." +"The whole point of signatures is to alert you when someone is trying to " +"pretend to be someone they're not. Never accept a certificate from someone " +"online without verifying it first." msgstr "" -#: ../system/subscription/plan.rst:95 -msgid "SEPA" +#: ../system/integrations/smime/manage-certificates.rst:28 +msgid "📇 **What about trusted certificate authorities?**" msgstr "" -#: ../system/subscription/plan.rst:94 +#: ../system/integrations/smime/manage-certificates.rst:30 msgid "" -"Provide the requested information of the bank account holder and update if " -"you're ready. You'll then receive an email with the SEPA mandate." +"In some cases (e.g. when dealing with large enterprises), you may be given a " +"certificate for an entire CA, rather than a single contact. Add it here to " +"trust *all* certificates issued by that CA." msgstr "" -#: ../system/subscription/plan.rst:97 +#: ../system/integrations/smime/manage-certificates.rst:35 msgid "" -"Technically there's also the possibility to pay via invoice, however - this " -"method only applies to a fairly low number of instances. Please contact `our " -"sales team `_ for more information." +"Commercial CAs can usually be verified online. Zammad does not include a " +"list of built-in, trusted CAs." msgstr "" -#: ../system/translations.rst:2 -msgid "Translations" -msgstr "Traduções" +#: ../system/integrations/smime/manage-certificates.rst:57 +msgid "Add Private Key" +msgstr "" -#: ../system/translations.rst:4 +#: ../system/integrations/smime/manage-certificates.rst:39 msgid "" -"Translations of Zammad are processed centrally in our `Weblate instance " -"`_. This allows non-developers to review " -"and update translation texts of the language they actually speak." +"Once you've added a public-key certificate, you can import its matching " +"private key." msgstr "" -#: ../system/translations.rst:9 +#: ../system/integrations/smime/manage-certificates.rst:42 msgid "" -"Your language is in an incomplete translation state or has typos? Please " -"consider helping us in sorting this out! All you need is either a GitHub " -"account or to register directly in our instance." +"Private keys are for **your own organization only**; never ask your contacts " +"for their private keys." msgstr "" -#: ../system/translations.rst:13 +#: ../system/integrations/smime/manage-certificates.rst:0 msgid "" -"Did you know? This is also where the documentation translations are handled. " -"🤓" +"S/MIME integration showing configured certificates and possible issues with " +"Logging" msgstr "" -#: ../system/translations.rst:15 +#: ../system/integrations/smime/manage-certificates.rst:50 msgid "" -"Have a look in our :docs:`contribution section ` in the system documentation to get started!" +"A note is displayed on certificates with a matching private key (see line 2)." msgstr "" -#: ../system/translations.rst:20 -#, fuzzy -msgid "Local Translations" -msgstr "Traduções" +#: ../system/integrations/smime/manage-certificates.rst:52 +msgid "📤 **Certificates and private keys must be uploaded separately.**" +msgstr "" -#: ../system/translations.rst:22 +#: ../system/integrations/smime/manage-certificates.rst:54 msgid "" -"Apart from these system translations, there's still local translations you " -"can manage. This is relevant if you added custom objects that require " -"translations or even custom states and priorities." +"If your certificate and private key are bundled together in the same file or " +"PEM block, import it twice (once using each button)." msgstr "" -#: ../system/translations.rst:None -msgid "Translation management screen within the admin menu" +#: ../system/integrations/smime/manage-certificates.rst:57 +msgid "Please note that bulk imports of private keys are not possible." msgstr "" -#: ../system/translations.rst:31 +#: ../system/integrations/smime/manage-certificates.rst:60 #, fuzzy -msgid "Updating Translations" -msgstr "Traduções" +msgid "Download Certificate Data" +msgstr "Limitação" -#: ../system/translations.rst:33 +#: ../system/integrations/smime/manage-certificates.rst:62 msgid "" -"Because of how Zammad ships translations, the only way to update the system " -"translations is to update your Zammad installation. The benefit of this is " -"that you no longer need internet access during a Zammad upgrade as the " -"package has everything it requires already." -msgstr "" - -#: ../system/translations.rst:39 -msgid "Translation of Custom Objects" +"You can download the earlier provided certificates and private keys at any " +"time from your Zammad instance." msgstr "" -#: ../system/translations.rst:41 +#: ../system/integrations/smime/manage-certificates.rst:65 msgid "" -"No problem at all! You can customize any translation locally, even if it is " -"not initially provided by the system." +"Please note that passphrase-protected private keys stay protected and when " +"you download them, you have to know the passphrase to use them after " +"downloading." msgstr "" -#: ../system/translations.rst:44 -msgid "" -"Translation is supported for a broad number of features, including but not " -"limited to custom:" +#: ../system/integrations/smime/manage-certificates.rst:73 +msgid "Dialogue to download certificates or private keys" msgstr "" -#: ../system/translations.rst:47 -#, fuzzy -msgid "Object Attributes" -msgstr "Atributos do ticket" - -#: ../system/translations.rst:48 -#, fuzzy -msgid "Ticket Macros" -msgstr "Criar uma macro global" - -#: ../system/translations.rst:49 -#, fuzzy -msgid "Ticket Overviews" -msgstr "Atributos do ticket" - -#: ../system/translations.rst:50 -#, fuzzy -msgid "Ticket Priorities" -msgstr "Prioridade" - -#: ../system/translations.rst:51 -#, fuzzy -msgid "Ticket States" -msgstr "Atributos do ticket" - -#: ../system/translations.rst:54 -#, fuzzy -msgid "Customizing Translations" -msgstr "Traduções" +#: ../system/integrations/smime/manage-certificates.rst:73 +msgid "Download stored certificates and their keys" +msgstr "" -#: ../system/translations.rst:56 +#: ../system/integrations/smime/manage-certificates.rst:78 msgid "" -"Within the translation screen, simply click on the **New Translation** " -"button." +"The ticket composer will set all outgoing messages to **signed and " +"encrypted** by default (assuming the required certificates exist)." msgstr "" -#: ../system/translations.rst:None -#, fuzzy -msgid "New translation dialog" -msgstr "Caixa de diálogo Nova conta de e-mail" +#: ../system/integrations/smime/manage-certificates.rst:82 +msgid "These defaults can be modified on a per-group basis:" +msgstr "" -#: ../system/translations.rst:62 -msgid "" -"In the dialog you can immediately enter the exact translation source (if you " -"know it) and your custom translation text for it and click **Submit**." +#: ../system/integrations/smime/manage-certificates.rst:None +msgid "Zammad allowing to choose the default behavior on per group basis" msgstr "" -#: ../system/translations.rst:65 +#: ../system/integrations/smime/manage-certificates.rst:89 msgid "" -"Alternatively, try to search for translation suggestions in the list below. " -"Selecting an item from the list will pre-fill the translation source for you " -"and then you can just enter your custom translation." +"Of course, agents can always manually change these settings on each email " +"they send out." msgstr "" -#: ../system/translations.rst:69 +#: ../system/integrations/smime/prerequisites.rst:4 +msgid "A certificate *and* private key for your own organization" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:6 msgid "" -"The target language will always default to your current language selection. " -"If you need to translate for a different language, simply change the " -"selection before submitting." +"(Use this to ✒️ **sign outgoing messages** and 🔓 **decrypt incoming " +"messages**.)" msgstr "" -#: ../system/translations.rst:73 +#: ../system/integrations/smime/prerequisites.rst:9 msgid "" -"All your custom translations will show up in the overview table when added. " -"And they will even persist across Zammad updates!" +"Certificates belonging your contacts, or their issuing certificate authority " +"(CA)" msgstr "" -#: ../system/translations.rst:76 +#: ../system/integrations/smime/prerequisites.rst:11 msgid "" -"Make sure to reload your browser if a translated string is not displayed." +"(Use these to ✅ **verify incoming message signatures** and 🔒 **encrypt " +"outgoing messages**.)" msgstr "" -#: ../system/translations.rst:80 -msgid "Reverting to Original Translations" +#: ../system/integrations/smime/prerequisites.rst:14 +msgid "🙋 **I'm new to S/MIME. Where can I get a certificate?**" msgstr "" -#: ../system/translations.rst:82 +#: ../system/integrations/smime/prerequisites.rst:16 msgid "" -"If you want to revert a custom translation to original text, simply use the " -"appropriate action within the row of the overview table." +"The easiest way to get certificates is to buy an annual subscription through " +"a commercial CA, such as:" msgstr "" -#: ../system/translations.rst:85 +#: ../system/integrations/smime/prerequisites.rst:19 msgid "" -"Depending on the type of the translation source, the action has a slightly " -"different name:" +"`Sectigo (formerly Comodo) `_" msgstr "" -#: ../system/translations.rst:88 -msgid "**Reset** for customized system translations" +#: ../system/integrations/smime/prerequisites.rst:20 +msgid "`Secorio `_" msgstr "" -#: ../system/translations.rst:89 -msgid "**Remove** for customized local translations" +#: ../system/integrations/smime/prerequisites.rst:21 +msgid "`GlobalSign `_" msgstr "" -#: ../system/translations.rst:91 -msgid "" -"In both cases, the action will remove the customized translation after a " -"confirmation." +#: ../system/integrations/smime/prerequisites.rst:23 +msgid "(Zammad is not affiliated with these CAs in any way.)" msgstr "" -#: ../system/translations.rst:None -msgid "Screenshot showing the location of the Remove action" +#: ../system/integrations/smime/prerequisites.rst:25 +msgid "" +"You can also generate your own self-signed certificates, but the process is " +"complicated and usually 🙅 **involves extra work for your contacts**." msgstr "" -#: ../system/translations.rst:99 -#, fuzzy -msgid "Inline Translations" -msgstr "Traduções" - -#: ../system/translations.rst:101 +#: ../system/integrations/smime/prerequisites.rst:29 msgid "" -"If you prefer a more hands-on approach, you can activate the inline or on-" -"screen translation feature by pressing ``ctrl`` + ``alt`` + ``t`` at any " -"time and on any screen." +"Bear in mind that 🤝 **S/MIME only works if the other party is using it, too." +"**" msgstr "" -#: ../system/translations.rst:105 +#: ../system/integrations/smime/prerequisites.rst:32 +msgid "Certificate and Private Key Checks on Upload" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:34 msgid "" -"All customizable translation texts will be highlighted for you on the " -"screen. Just click into the highlighted area and update the text in place." +"The certificate and public key validation is based on the ``X509v3`` " +"extensions." msgstr "" -#: ../system/translations.rst:None -msgid "Inline translation mode activated for the Overview screen" +#: ../system/integrations/smime/prerequisites.rst:49 +msgid "Uploading a *client certificate*?" msgstr "" -#: ../system/translations.rst:112 -msgid "" -"When finished editing, simply press ``ctrl`` + ``alt`` + ``t`` again to " -"deactivate." +#: ../system/integrations/smime/prerequisites.rst:41 +msgid "The following attributes are required then:" msgstr "" -#: ../system/translations.rst:117 -msgid "" -"Even though it's available on any screen, the inline translation feature " -"requires admin permissions. It works only for the current language " -"selection. If you need to translate a different language, first change the " -"language in your :user-docs:`profile settings `." +#: ../system/integrations/smime/prerequisites.rst:39 +msgid "Subject Alternative Name (at least one email address has to be present)" msgstr "" -#: ../system/variables.rst:2 -msgid "Variables" -msgstr "Variáveis" +#: ../system/integrations/smime/prerequisites.rst:40 +msgid "Key Usage (``Digital Signature`` and/or ``Key Encipherment``)" +msgstr "" -#: ../system/variables.rst:4 -msgid "" -"Please note that this is just an overview of available variables. It might " -"be incomplete or variables might not be available within some functions. If " -"you're missing variables or are not sure if something is not working as " -"expected, feel free to ask over at the `Community `_." +#: ../system/integrations/smime/prerequisites.rst:41 +msgid "Public key algorithm (either ``RSA`` or ``EC``)" msgstr "" -#: ../system/variables.rst:10 -msgid "" -"Variables can be called by typing ``::`` (just like text modules in the " -"frontend), as long as you're in a supported text field within the backend. " -"Zammad will display all variables being available within this context and " -"replace it to the variable as soon as you selected an entry." +#: ../system/integrations/smime/prerequisites.rst:43 +msgid "" +"The Extended Key Usage attribute is optional. If the certificate provides " +"the named attribute, than it must contain the value ``E-mail Protection``." msgstr "" -#: ../system/variables.rst:15 +#: ../system/integrations/smime/prerequisites.rst:46 msgid "" -"You have an empty field which you referenced and it appears as ``-``? That's " -"currently working as designed - you might want to ensure that these fields " -"always have a value." +"Please note that any usable email adress has to be prefixed with ``email:`` " +"or ``rfc822:``." msgstr "" -#: ../system/variables.rst:20 -msgid "Variable Categories" -msgstr "Categorias de Variável" +#: ../system/integrations/smime/prerequisites.rst:49 +msgid "The named public key algorithms are mandatory for private keys as well." +msgstr "" -#: ../system/variables.rst:31 -msgid "Wait, What About Custom Objects?" +#: ../system/integrations/smime/prerequisites.rst:54 +msgid "Uploading a *CA certificate*?" msgstr "" -#: ../system/variables.rst:33 +#: ../system/integrations/smime/prerequisites.rst:52 msgid "" -"Good point! Of course, we can't predict what objects you might create, but " -"we can give you a hint on how to put the puzzle together to get your custom " -"values." +"In the case of an uploaded CA certificate, providing the value ``CA:TRUE`` " +"in the attribute *Basic Contstraints*, the previously mentioned attributes " +"are not verified." msgstr "" -#: ../system/variables.rst:36 +#: ../system/integrations/smime/prerequisites.rst:56 msgid "" -"For this, we'll talk about the inner part of the variable (so everything " -"within ``#{}``), please put the outer part around to have a valid variable. " -"The first part of the variable name consist of the object type. Currently " -"these are:" +"In general, the usage of any expired (``Not After``) or not yet valid (``Not " +"Before``) certificate is denied for outgoing emails." msgstr "" -#: ../system/variables.rst:41 -msgid "Ticket (``ticket``)" -msgstr "Chamado (``chamado``)" - -#: ../system/variables.rst:42 -msgid "User (``user``)" -msgstr "Usuário (``usuário``)" - -#: ../system/variables.rst:43 -msgid "Organization (``organization``)" -msgstr "Organização (``organização``)" - -#: ../system/variables.rst:44 -msgid "Group (``group``)" -msgstr "Grupo (``grupo``)" +#: ../system/integrations/smime/prerequisites.rst:59 +msgid "Example certificate:" +msgstr "" -#: ../system/variables.rst:46 +#: ../system/integrations/smime/prerequisites.rst:85 msgid "" -"The second part is the name of the object. This is the name you define " -"during object creation and can be found within the object menu at any time. " -"The first and second part of a variable is divided by a point, e.g.: " -"``ticket.number`` which will in total be ``#{ticket.number}``." +"Please note that Zammad will distrust senders by default. This means that " +"you're always required to provide certificate data, no matter if for signing " +"or encrypting." +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:89 +msgid "This is by design and can't be adjusted." msgstr "" -#: ../system/variables.rst:51 +#: ../system/integrations/smime/troubleshooting.rst:4 msgid "" -"Now, in some situations it's possible that you'll need to use a third part. " -"The best example for such a situation would be a ``select`` or ``tree-" -"select`` field which will by default return the key value, not it's display " -"name. For this, just extend your variable with ``.value``. This will result " -"in ``#{ticket.select.value}``." +"All of the system's latest S/MIME activity is displayed in the **Recent " +"Logs** section." msgstr "" -#: ../system/variables.rst:60 -#, fuzzy -msgid "Using Translated Variables" -msgstr "Traduções" +#: ../system/integrations/smime/troubleshooting.rst:11 +msgid "Sample entries of in- and outgoing S/MIME related emails." +msgstr "" -#: ../system/variables.rst:62 +#: ../system/integrations/smime/troubleshooting.rst:11 msgid "" -"If you want to use a translated variable in triggers or schedulers, you can " -"extend the placeholder like this: ``#{t(ticket.state.name)}``. The ``t`` " -"tells Zammad to search for fitting translated strings. The used output " -"language is based on the system language of Zammad which you can set in the " -"admin panel under :doc:`/settings/branding` or based on the selected locale " -"in the trigger/scheduler edit dialog." +"Logs report the status and details of all mail, both incoming and outgoing, " +"that used signing/verification or encryption/decryption." msgstr "" -#: ../system/variables.rst:69 +#: ../system/integrations/smime/troubleshooting.rst:14 msgid "" -"A possible use-case: you want to send your customers updates on tickets via " -"trigger or scheduler which should include the state of the ticket. Using the " -"default ``#{ticket.state.name}`` (without the translation flag ``t()``) " -"would lead to the output of the original (english) name of the state." +"This log does **not** include email sent by :doc:`triggers ` or the :doc:`scheduler `. For those, check your " +"``production.log``." msgstr "" -#: ../system/variables.rst:75 -msgid "Date and Time Formatting" +#: ../system/integrations/smime/troubleshooting.rst:20 +msgid "Common Issues" msgstr "" -#: ../system/variables.rst:77 -msgid "" -"The system (trigger/scheduler selected) locale and timezone predefines a " -"default format of date and timestamp. This format is customizable by using " -"the ``dt()`` method." +#: ../system/integrations/smime/troubleshooting.rst:30 +msgid "I received a signed/encrypted email before I set up S/MIME integration" msgstr "" -#: ../system/variables.rst:79 -msgid "The method arguments are as follows:" +#: ../system/integrations/smime/troubleshooting.rst:23 +msgid "" +"No problem. Once S/MIME has been enabled and the appropriate certificates " +"have been added, agents will be prompted to retry verification/decryption on " +"matching emails." msgstr "" -#: ../system/variables.rst:81 -msgid "The date or timestamp variable you want to format." +#: ../system/integrations/smime/troubleshooting.rst:0 +msgid "Screenshot of user prompt to retry decryption" msgstr "" -#: ../system/variables.rst:82 -msgid "The output format string." +#: ../system/integrations/smime/troubleshooting.rst:38 +msgid "The 🔒 **Encrypt** button is disabled" msgstr "" -#: ../system/variables.rst:83 -msgid "The timezone to apply (optional)." +#: ../system/integrations/smime/troubleshooting.rst:33 +msgid "Have you added the recipient's certificate?" msgstr "" -#: ../system/variables.rst:86 -msgid "" -"``#{dt(ticket.updated_at, \"%A %Y-%m-%d %H:%M in the office\", \"Europe/" -"Berlin\")}``" +#: ../system/integrations/smime/troubleshooting.rst:34 +msgid "Are you sure the recipient's certificate is valid?" msgstr "" -#: ../system/variables.rst:87 -msgid "Monday, 2024-03-18 15:31 in the office" +#: ../system/integrations/smime/troubleshooting.rst:35 +msgid "Have you checked your ``production.log`` for more details?" msgstr "" -#: ../system/variables.rst:89 +#: ../system/integrations/smime/troubleshooting.rst:37 msgid "" -"If you want to use our example, make sure to paste the string above without " -"formatting (``CTRL+Shift+v``), otherwise it won't work." +"If encryption doesn't work in the composer, it won't work in :doc:`triggers " +"` or the :doc:`scheduler ` either!" msgstr "" -#: ../system/variables.rst:93 -msgid "The following table lists available format directives:" +#: ../system/integrations/smime/troubleshooting.rst:42 +msgid "The ✅ **Sign** button is disabled" msgstr "" -#: ../system/variables.rst:99 -msgid "Parameter" +#: ../system/integrations/smime/troubleshooting.rst:41 +msgid "" +"Have you added **both the certificate and private key** for your " +"organization?" msgstr "" -#: ../system/variables.rst:102 -msgid "``%Y``" +#: ../system/integrations/smime/troubleshooting.rst:42 +msgid "" +"Does the email address on the certificate match the email address of the " +"agent/group composing the email?" msgstr "" -#: ../system/variables.rst:103 -msgid "Year with 4 digits" +#: ../system/integrations/smime/troubleshooting.rst:45 +msgid "Error: “Fingerprint already taken”" msgstr "" -#: ../system/variables.rst:104 -msgid "Use ``%y`` for year with 2 digits" +#: ../system/integrations/smime/troubleshooting.rst:45 +msgid "Are you sure you haven't added this certificate already?" msgstr "" -#: ../system/variables.rst:105 -msgid "``%m``" +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Error: “❌ invalid byte sequence in UTF-8”" msgstr "" -#: ../system/variables.rst:106 -msgid "Month of year (as number with zero-padding)" +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Please ensure to provide PEM formatted certificate and keys." msgstr "" -#: ../system/variables.rst:107 -msgid "Use ``%-m`` for month without zero-padding" +#: ../system/integrations/smime/troubleshooting.rst:49 +msgid "Did you check if the provided file is a valid certificate or key?" msgstr "" -#: ../system/variables.rst:108 -msgid "``%d``" -msgstr "" +#: ../system/integrations/zabbix.rst:2 +msgid "Zabbix Integration" +msgstr "Integração com Zabbix" -#: ../system/variables.rst:109 -msgid "Day of month (as number with zero-padding)" +#: ../system/integrations/zabbix.rst:5 +msgid "" +"This guide describes how to integrate your Zabbix 5.4 installation with " +"Zammad using the Zabbix webhook feature. This guide will provide " +"instructions on setting up a media type, a user and an action in Zabbix." msgstr "" -#: ../system/variables.rst:110 -msgid "Use ``%e`` for day without zero-padding" -msgstr "" +#: ../system/integrations/zabbix.rst:12 +msgid "Zammad with enabled HTTP Token Authentication" +msgstr "Zammad com autenticação de token HTTP ativada" -#: ../system/variables.rst:111 -msgid "``%H``" -msgstr "" +#: ../system/integrations/zabbix.rst:13 +#, fuzzy +msgid "Zabbix version 5.4 or higher" +msgstr "Zabbix versão 5.0 ou superior" -#: ../system/variables.rst:112 -msgid "Hour of day in 24h notation with zero-padding" +#: ../system/integrations/zabbix.rst:16 +msgid "Setting up a Zammad" +msgstr "Configurando o Zammad" + +#: ../system/integrations/zabbix.rst:18 +msgid "Enable **API Token Access** in Settings > System > API." +msgstr "Ative o **Token de acesso a API** em Configurações > Sistema > API." + +#: ../system/integrations/zabbix.rst:20 +msgid "" +"Create a **new user** for a Zabbix alerter with an **email address** and " +"create a personal user token with **ticket.agent** permissions." msgstr "" -#: ../system/variables.rst:113 -msgid "Use ``%k`` for hour without zero-padding" +#: ../system/integrations/zabbix.rst:24 +#, fuzzy +msgid "Zabbix Webhook Configuration" +msgstr "Configuração de Webhook do Zabbix" + +#: ../system/integrations/zabbix.rst:27 +#, fuzzy +msgid "Create a Global Macro" +msgstr "Criar uma macro global" + +#: ../system/integrations/zabbix.rst:29 +msgid "" +"Before setting up the **Webhook**, you need to setup the global macro " +"**{$ZABBIX.URL}**, which must contain the **URL** to the **Zabbix frontend**." msgstr "" -#: ../system/variables.rst:114 -msgid "``%I``" +#: ../system/integrations/zabbix.rst:33 +msgid "" +"In the **Administration** > **Media types** section, import the `Template`_." msgstr "" -#: ../system/variables.rst:115 -msgid "Hour of day in 12h notation with zero-padding" +#: ../system/integrations/zabbix.rst:38 +msgid "Open the added **Zammad** media type and set:" +msgstr "Abra o tipo de mídia **Zammad** adicionado e defina:" + +#: ../system/integrations/zabbix.rst:40 +msgid "**zammad\\_access\\_token** to the your **Personal User Token**" msgstr "" -#: ../system/variables.rst:116 +#: ../system/integrations/zabbix.rst:41 msgid "" -"Use ``%l`` for hour without zero-padding and ``%p`` / ``%P`` for meridian " -"indicator" +"**zammad\\_url** to the **frontend URL** of your **Zammad** installation" msgstr "" -#: ../system/variables.rst:117 -msgid "``%M``" +#: ../system/integrations/zabbix.rst:43 +msgid "**zammad\\_customer** to your **Zammad user email**." msgstr "" -#: ../system/variables.rst:118 -msgid "Minute of hour" +#: ../system/integrations/zabbix.rst:44 +msgid "" +"**zammad\\_enable\\_tags** to **true** or **false** to enable or disable " +"trigger tags. **Important**: if you enable tag support, each tag is set with " +"a separate request." msgstr "" -#: ../system/variables.rst:120 -msgid "``%S``" +#: ../system/integrations/zabbix.rst:48 +msgid "" +"If you want to prioritize issues according to **severity** values in Zabbix, " +"you can define mapping parameters:" msgstr "" -#: ../system/variables.rst:121 -msgid "Second of Minute" +#: ../system/integrations/zabbix.rst:51 +msgid "**severity\\_**: Zammad priority ID" msgstr "" -#: ../system/variables.rst:123 -msgid "``%A``" +#: ../system/integrations/zabbix.rst:53 +msgid "Click the **Update** button to save the **Webhook** settings." msgstr "" -#: ../system/variables.rst:124 -msgid "Weekday name" +#: ../system/integrations/zabbix.rst:55 +msgid "" +"To receive notifications in **Zammad**, you need to create a **Zabbix user** " +"and add **Media** with the **Zammad** type." msgstr "" -#: ../system/variables.rst:125 -msgid "Use ``%a`` for abbreviated name or ``%^A`` for uppercase name" +#: ../system/integrations/zabbix.rst:58 +msgid "" +"For **Send to**: enter any text, as this value is not used, but is required." msgstr "" -#: ../system/variables.rst:126 -msgid "``%B``" +#: ../system/integrations/zabbix.rst:61 +msgid "" +"For more information, use the `Zabbix documentation `_." msgstr "" -#: ../system/variables.rst:127 -msgid "Month name" -msgstr "" +#: ../system/maintenance.rst:2 +msgid "Maintenance" +msgstr "Manutenção" -#: ../system/variables.rst:128 -msgid "Use ``%b`` for abbreviated name" +#: ../system/maintenance.rst:4 +msgid "" +"Zammad comes with a maintenance mode that you can use for e.g. updating the " +"instance or changing settings while restricting availability and functions." msgstr "" -#: ../system/variables.rst:129 -msgid "``%U``" -msgstr "" +#: ../system/maintenance.rst:13 +msgid "Mode" +msgstr "Modo" -#: ../system/variables.rst:130 -msgid "Week number of current year" +#: ../system/maintenance.rst:8 +msgid "The mode setting allows you to enable or disable the maintenance mode." msgstr "" -#: ../system/variables.rst:131 -msgid "Use ``%W`` for a different calculation method" +#: ../system/maintenance.rst:10 +msgid "Defaults to *off*." msgstr "" -#: ../system/variables.rst:134 +#: ../system/maintenance.rst:12 msgid "" -"We support the known format directives for the Ruby built-in method " -"``strftime`` of the ``DateTime`` class. For more information, see `here " -"`_." +"The maintenance mode will restrict access to administrative roles only. This " +"means agents and customers are logged off." msgstr "" -#: ../system/variables/article.rst:2 -msgid "Articles" -msgstr "Artigos" +#: ../system/maintenance.rst:23 +msgid "@Login" +msgstr "" -#: ../system/variables/article.rst:4 ../system/variables/config.rst:4 -#: ../system/variables/current-user.rst:4 ../system/variables/ticket.rst:4 +#: ../system/maintenance.rst:16 msgid "" -"If you're missing variables or are not sure if something is not working as " -"expected, feel free to ask over at the `Community `_." +"This setting allows you to provide a login message within a green banner " +"above the login screen. Click into the green banner in the settings page to " +"adjust your message. To activate the message, activate the *@Login* setting." msgstr "" -#: ../system/variables/article.rst:6 +#: ../system/maintenance.rst:0 msgid "" -"Below you can find all available ticket article-based variables within " -"Zammad. These can be called via Triggers for example. If you're unsure if " -"Zammad does support variables at the point you're at, you can try to type " -"``::`` to check." +"Screenshot showing the default login message within the\n" +"settings page" msgstr "" -#: ../system/variables/article.rst:9 ../system/variables/config.rst:9 -#: ../system/variables/ticket.rst:9 +#: ../system/maintenance.rst:26 msgid "" -"The below list gives you an example what kind of data you can expect, it's " -"not intended to explain the data itself." +"Send an informative message to **all active sessions**. This comes handy to " +"inform your agents e.g. about mayor outages or to force reloads after " +"configuration changes." msgstr "" -#: ../system/variables/article.rst:11 -msgid "Article Variables" +#: ../system/maintenance.rst:31 +msgid "This is the messages title (slightly bigger than the normal message)." msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "name" +#: ../system/maintenance.rst:34 +msgid "The text you want to provide to your logged in sessions." msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "variable" +#: ../system/maintenance.rst:39 +msgid "Reload application" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "example" -msgstr "exemplo" - -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Web" +#: ../system/maintenance.rst:37 +msgid "" +"Selecting this option will change the message acceptance button from *Close* " +"(with nothing happening) to *Continue session*, which forces the application " +"to reload." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.web}``" +#: ../system/maintenance.rst:43 +msgid "" +"If you have customers that are logged in to Zammad, they'll also be notified " +"if they're active in that moment." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``https://zammad.com`` or empty if not set in user object" +#: ../system/maintenance.rst:48 +msgid "Example without reload application" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > VIP" +#: ../system/maintenance.rst:52 +msgid "" +"Message setting within Zammad's admin settings without ticket reload " +"application setting." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.vip}``" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing the send message settings without ticket\n" +"reload application set" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -msgid "``true`` or ``false``" +#: ../system/maintenance.rst:61 ../system/maintenance.rst:85 +msgid "" +"The modal all other active sessions will see upon pressing *Send to clients*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Phone" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing modal caused by maintenance's message\n" +"without reload application ticket" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.phone}``" +#: ../system/maintenance.rst:72 +msgid "Example with reload application" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``+4930123456789`` or empty if not set in user object" +#: ../system/maintenance.rst:76 +msgid "" +"Message setting within Zammad's admin settings with ticket reload " +"application setting." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Note" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing the send message settings with ticket\n" +"reload application set" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.note}``" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing modal caused by maintenance's message\n" +"with reload application ticket" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Some note about user`` or empty if not set in user object" -msgstr "" +#: ../system/monitoring.rst:2 +msgid "Monitoring" +msgstr "Monitoramento" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Mobile" +#: ../system/monitoring.rst:4 +#, fuzzy +msgid "" +"This function is only available in self hosted instances. If you use Zammad " +"in our cloud, we are monitoring the system on our own and take steps to fix " +"potential problems directly." msgstr "" +"**Nota:** Isto está disponível apenas na versão on-premises, já que estamos " +"monitorando instâncias e resolvendo problemas." -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.mobile}``" +#: ../system/monitoring.rst:11 +#, fuzzy +msgid "" +"On the monitoring page, you can see the current health state of Zammad under " +"\"*Current Status*\" at the bottom. This can be useful if you want to have a " +"look if everything is up and running. As an example, you could have a look " +"in the monitoring when you assume that some emails aren't processed from " +"Zammad." msgstr "" +"Na página de monitoramento você pode ver o estado de saúde atual do Zammad. " +"Isto pode ser útil por exemplo se você parou de receber emails. Você também " +"pode checar esta página antes mesmo de fazer login no seu servidor." -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Login" +#: ../system/monitoring.rst:17 +msgid "**Can't receive an email and the monitoring response is \"healthy\"?**" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.login}``" +#: ../system/monitoring.rst:19 +msgid "" +"Zammad will just inform you about unprocessable emails. This is not the case " +"for oversized emails. You can adjust the maximum email size in :doc:`../" +"channels/email/settings`." msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -#: ../system/variables/ticket.rst:1 -msgid "``jdoe``" -msgstr "" +#: ../system/monitoring.rst:24 +#, fuzzy +msgid "Monitoring API" +msgstr "Monitoramento" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Lastname" +#: ../system/monitoring.rst:26 +msgid "" +"Beside the indication in the monitoring page, you can also use an external " +"monitoring tool to monitor Zammad's health. To request the health of Zammad, " +"you need to provide the API key (token) to the external monitoring tool. You " +"can copy the token from the \"*Current Token*\" field as well as the whole " +"API endpoint of your system (\"*Health Check*\" field), in which the API " +"token is already included." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.lastname}``" +#: ../system/monitoring.rst:37 +msgid "Screenshot showing Current Token and Health Check" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -#: ../system/variables/ticket.rst:1 -msgid "``Doe`` or empty if not set" +#: ../system/monitoring.rst:37 +msgid "Screenshot showing Token and Health Check" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Firstname" +#: ../system/monitoring.rst:39 +msgid "" +"In addition to that, you can reset the auto-generated token to make sure " +"that already configured monitoring systems won't work anymore. So, please " +"use this \"*Reset*\" button only if you know what you do!" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.firstname}``" -msgstr "" +#: ../system/monitoring.rst:44 +#, fuzzy +msgid "Example Output" +msgstr "Um exemplo de saída pode ser:" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "``Joe`` or empty if not set" +#: ../system/monitoring.rst:0 +msgid "No issues found" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Fax" +#: ../system/monitoring.rst:48 ../system/monitoring.rst:60 +msgid "**Indicator in Zammad**:" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.fax}``" +#: ../system/monitoring.rst:0 +msgid "Screenshot showing monitoring with no issues" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Email" +#: ../system/monitoring.rst:54 ../system/monitoring.rst:66 +msgid "**API response**::" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.email}``" +#: ../system/monitoring.rst:0 +msgid "Issues were found" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``jdoe@example.com``" +#: ../system/monitoring.rst:0 +msgid "Screenshot showing monitoring with issues" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Department" +#: ../system/objects.rst:2 +msgid "Objects" +msgstr "Objetos" + +#: ../system/objects.rst:4 +msgid "" +"In Zammad you can add your own fields to tickets, users, organizations and " +"even groups (these are called \"objects\"). This can be useful if you need " +"to add further information to a ticket or any other object in Zammad and the " +"information doesn't fit in any existing field." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.department}``" +#: ../system/objects.rst:11 +msgid "" +"Try to avoid deleting attributes (and disable them instead) as Zammad might " +"run into unexpected conditions if they are referenced somewhere." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Sales`` or empty if not set in user object" +#: ../system/objects.rst:16 +msgid "" +"Here's an overview of object attributes. On the upper right you can add new " +"attributes. By default, there will be no custom fields - standard attributes " +"will be grayed out, you can't delete or change those. You can edit custom " +"attributes (they are displayed in black font and have a trash bin on the " +"right side) just by clicking on them." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Address" +#: ../system/objects.rst:24 +msgid "" +"Attributes you add to Zammad, no matter if they have default values or not, " +"will not update existing information. This means a new ticket field " +"technically will be empty unless you populate it." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.address}``" +#: ../system/objects.rst:28 +msgid "" +"Especially in ticket scope this also means that newly added attributes will " +"be indicated as \"changed\" to agents that view the ticket. This may " +"interfere with Zammad's tabs behavior." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Some street 1, 12345 Berlin`` or empty if not set in user object" +#: ../system/objects.rst:40 +#, fuzzy +msgid "Ordering Attributes" +msgstr "Atributos do ticket" + +#: ../system/objects.rst:42 +msgid "" +"Since Zammad introduced :doc:`/system/core-workflows` the need to have a " +"custom positioning for attributes has become more important than ever." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated" +#: ../system/objects.rst:45 +msgid "" +"To adjust the position of such an attribute, simply click on the attribute " +"entry in question, scroll down and adjust the position number. Please note " +"that you cannot change the positioning of default attributes." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_at}``" +#: ../system/objects.rst:49 +msgid "" +"In case two attributes have the same position value, Zammad will sort " +"alphabetically by name automatically." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``2019-10-08 15:24:47 UTC``" +#: ../system/objects.rst:None +msgid "" +"Screenshot showing custom attribute entries ordered in between default ones" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Type > Name" +#: ../system/objects.rst:56 +msgid "Updating Database After Adding or Editing Attributes" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.type.name}``" +#: ../system/objects.rst:58 +msgid "" +"When adding or changing attributes, Zammad will not apply the changes " +"instantly, but instead shows you the changed attributes first. If you're " +"ready to go, just click on \"Update database\" to apply the changes to " +"Zammad. If you made a mistake or just want to discard your changes, click " +"\"Discard changes\"." msgstr "" -#: ../system/variables/article.rst:1 +#: ../system/objects.rst:64 msgid "" -"``email`` (`list of article types `_)" +"After applying the changes with \"Update Database\", a restart of Zammad is " +"**mandatory**. If you don't perform it, you may experience unexpected " +"behavior or even errors. You may want to do this kind of configuration " +"during maintenance windows." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > To" +#: ../system/objects.rst:72 +msgid "" +"Changes on objects require you to update the database to apply these changes." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.to}``" +#: ../system/objects.rst:75 +msgid "**🤓 Service restarts can be automated**" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``helpdesk@example.com``" +#: ../system/objects.rst:0 +msgid "Hosted environments automatically restart for you." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > TicketID" +#: ../system/objects.rst:0 +msgid "" +"If you're using a self-hosted installation you can use :docs:`environment " +"variables `" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.ticket_id}``" -msgstr "" +#: ../system/objects.rst:82 +#, fuzzy +msgid "System Attributes" +msgstr "Atributos do ticket" -#: ../system/variables/article.rst:1 -msgid "``1`` (not ticket number)" +#: ../system/objects.rst:84 +msgid "" +"Zammad comes with pre-configured attributes. Some of them can't be edited " +"via UI (or at all). This is required for proper operation of Zammad and not " +"a bug." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Subject" -msgstr "" +#: ../system/objects.rst:90 +#, fuzzy +msgid "Ticket State" +msgstr "Atributos do ticket" -#: ../system/variables/article.rst:1 -msgid "``#{article.subject}``" +#: ../system/objects.rst:92 +msgid "" +"If the pre-configured states aren't enough for you or you want to change " +"them, you can do so by clicking on the cogwheel icon in the state row in the " +"ticket tab. But you should be careful when changing pre-configured states. " +"This can lead to unwanted behavior in some cases." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``My amazing subject``" +#: ../system/objects.rst:None +msgid "Screenshot showing highlighted ticket state attribute" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Sender > Name" +#: ../system/objects.rst:122 +msgid "Handling of states" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.sender.name}``" +#: ../system/objects.rst:102 +msgid "" +"In the state configuration screen, you can add new states, disable states or " +"change states." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Customer``, ``Agent`` or ``System``" +#: ../system/objects.rst:0 +msgid "Screenshot showing table of default ticket states" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Visibility" +#: ../system/objects.rst:110 +msgid "" +"To add a new state, click on the \"New Ticket State\" button in the top " +"right corner. To change an existing state, simply click on the affected " +"state. This opens an edit dialog." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.internal}``" +#: ../system/objects.rst:114 +msgid "" +"You can also clone a state or set them to \"Default for new tickets\" or " +"\"Default for follow-ups\" by clicking on the ⁝ action button and select the " +"desired function." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``false`` or ``true`` (false if not internal)" +#: ../system/objects.rst:118 +msgid "" +"*Default for new tickets* means that this state is used for every newly " +"created ticket." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > From" +#: ../system/objects.rst:121 +msgid "" +"*Default for follow-ups* means that this state is used if the ticket is re-" +"opened after it was closed." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.from}``" +#: ../system/objects.rst:171 +msgid "Ticket state in detail" msgstr "" -#: ../system/variables/article.rst:1 +#: ../system/objects.rst:125 msgid "" -"``Joe Doe `` may differ, depends on ``FROM`` of send mail" +"Below you can find a description for each field and option. Please head over " +"to the :ref:`example ` to see the edit dialog." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Web" +#: ../system/objects.rst:129 +msgid "" +"This is the name of the state and what you and your agents are seeing when " +"choosing a state somewhere (e.g. in tickets, trigger configuration)." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.web}``" +#: ../system/objects.rst:137 +msgid "" +"There are different state types you can choose from. By default, Zammad " +"comes with one state per state type." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > VIP" +#: ../system/objects.rst:140 +msgid "" +"**new**: for states for tickets that are new and it hasn't been worked on " +"them" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.vip}``" +#: ../system/objects.rst:142 +msgid "" +"**open**: for states for tickets that are in progress and agents are working " +"on them" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Phone" +#: ../system/objects.rst:144 +msgid "**merged**: for states for tickets that are merged with other tickets" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.phone}``" +#: ../system/objects.rst:145 +msgid "" +"**pending reminder**: for states for tickets that are in progress and you " +"want to set a reminder. (default example: *pending reminder*)" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Note" +#: ../system/objects.rst:147 +msgid "" +"**pending action**: for states for tickets that are waiting for a specified " +"time and then change their state (default example: *pending close*)" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.note}``" +#: ../system/objects.rst:150 +msgid "" +"**closed**: for states for tickets that are finished and do not need to be " +"processed further" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Mobile" +#: ../system/objects.rst:153 +msgid "" +"⚠️ Choosing the correct state type is important! If you are in doubt, have a " +"look on the default states and their types!" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.mobile}``" +#: ../system/objects.rst:158 +msgid "Ignore escalation" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Login" +#: ../system/objects.rst:157 +msgid "" +"Here you can define whether tickets of this state will count to escalation " +"time or not." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.login}``" +#: ../system/objects.rst:161 +msgid "" +"You can create a note for the state to inform other admins about the state. " +"This has no effect on tickets." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Lastname" -msgstr "" +#: ../system/objects.rst:165 +#, fuzzy +msgid "Set the state to *active* or *inactive*." +msgstr "Se está ativo ou inativo" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.lastname}``" +#: ../system/objects.rst:167 +msgid "" +"it is technically possible to set all states to inactive. To keep Zammad " +"working in such a case, the inactive flag of one of the states is ignored." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Firstname" -msgstr "" +#: ../system/objects.rst:194 +#, fuzzy +msgid "Ticket state example" +msgstr "Árvore de Seleção" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.firstname}``" +#: ../system/objects.rst:174 +msgid "" +"Let's assume we want to create a new state which indicates that the ticket " +"has to wait for a response of a third party (e.g. service contractor or " +"manufacturer) and we want to to be able to set a reminder." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Fax" +#: ../system/objects.rst:178 +msgid "" +"First we give the new state a proper name. In this example we call it " +"\"waiting for manufacturer\"." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.fax}``" +#: ../system/objects.rst:181 +msgid "" +"As state type we choose \"pending reminder\". This indicates that the ticket " +"is still open and we can set a reminder. This reminder can be useful if our " +"manufacturer sometimes isn't responding or we want to remind him to give us " +"an answer." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Email" +#: ../system/objects.rst:186 +msgid "" +"We choose \"no\" for \"ignore escalation\" because we want to escalate the " +"tickets even if we are waiting on the manufacturer's feedback." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.email}``" +#: ../system/objects.rst:189 +#, fuzzy +msgid "The **result** in the creation dialog will look like this:" +msgstr "O resultado final parecerá como o seguinte:" + +#: ../system/objects.rst:0 +msgid "Screenshot showing ticket state creation dialog with example" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Department" +#: ../system/objects.rst:199 +#, fuzzy +msgid "Ticket Priority" +msgstr "Prioridade" + +#: ../system/objects.rst:201 +msgid "" +"If the pre-configured priorities aren't enough for you or you want to change " +"them, you can do so by clicking on the cogwheel icon in the priority row in " +"the ticket tab:" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.department}``" +#: ../system/objects.rst:None +msgid "Screenshot showing highlighted ticket priority attribute" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Address" +#: ../system/objects.rst:226 +msgid "Handling of priorities" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.address}``" +#: ../system/objects.rst:210 +msgid "" +"In the priority configuration screen, you can add new priorities, disable " +"priorities or change priorities." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created" +#: ../system/objects.rst:0 +msgid "Screenshot showing table of default ticket priorities" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_at}``" +#: ../system/objects.rst:218 +msgid "" +"To add a new priority, click on the \"New Priority\" button in the top right " +"corner. To change an existing priority, simply click on the affected " +"priority. This opens an edit dialog." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Cc" +#: ../system/objects.rst:222 +msgid "" +"You can also clone a priority or set them to \"Default for new tickets\" by " +"clicking on the ⁝ action button and select the desired function." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.cc}``" +#: ../system/objects.rst:225 +msgid "" +"*Default for new tickets* means that this priority is used for every newly " +"created ticket." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``jdoe@example.com, company@example.com``" +#: ../system/objects.rst:248 +msgid "Priorities in detail" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Text" +#: ../system/objects.rst:229 +msgid "Below you can find a description for each field and option." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.body}``" +#: ../system/objects.rst:232 +msgid "" +"This is the name of the priority and what you and your agents are seeing " +"when choosing a priority somewhere (e.g. in tickets, trigger configuration)." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Test`` without formatting (plain)" +#: ../system/objects.rst:242 +msgid "Highlight color" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article Text as HTML (not referenced)" +#: ../system/objects.rst:237 +msgid "" +"Switch between *Low priority* (light blue), *High priority* (red) and - " +"(default). This affects the displayed color for ticket titles in overviews." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.body_as_html}``" +#: ../system/objects.rst:241 +msgid "The color options are currently limited to the mentioned options." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Test`` with formatting" +#: ../system/objects.rst:245 +msgid "" +"You can create a note for the priority to inform other admins about the " +"priority. This has no effect on tickets." msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "Ticket > Article#" -msgstr "" +#: ../system/objects.rst:249 +#, fuzzy +msgid "Set the priority to *active* or *inactive*." +msgstr "Se está ativo ou inativo" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "``#{ticket.article_count}``" +#: ../system/objects/external-data-source-example.rst:2 +msgid "External Data Source" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``1`` number of ticket articles" +#: ../system/objects/external-data-source-example.rst:4 +msgid "" +"We assume you already had a look on :doc:`types` where you can find a " +"description of the individual fields." msgstr "" -#: ../system/variables/config.rst:2 -msgid "Config" +#: ../system/objects/external-data-source-example.rst:7 +msgid "" +"To reproduce this example, choose a category you want to add a custom field, " +"click on *New Attribute* and select *External data source field* under " +"*Format*." msgstr "" -#: ../system/variables/config.rst:6 +#: ../system/objects/external-data-source-example.rst:11 msgid "" -"Below you'll find config related variables. These hold useful configuration " -"information that you can use within e.g. triggers to show necessary " -"information to your customer." +"Our example story is to fetch data from an external product database. We " +"want to add our products to the tickets so that the products can be searched " +"and chosen from a list and also create a link to the product website." msgstr "" -#: ../system/variables/config.rst:11 -msgid "Config Variables" -msgstr "" +#: ../system/objects/external-data-source-example.rst:16 +#, fuzzy +msgid "Base configuration" +msgstr "Configuração" -#: ../system/variables/config.rst:1 -msgid "Config > Fully Qualified Domain Name" +#: ../system/objects/external-data-source-example.rst:None +msgid "Initial steps to configure external data source object type" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.fqdn}``" +#: ../system/objects/external-data-source-example.rst:25 +msgid "Name: *product*" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``zammad.example.com``" +#: ../system/objects/external-data-source-example.rst:26 +msgid "Display: *Product*" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Ticket Hook" -msgstr "" +#: ../system/objects/external-data-source-example.rst:29 +#, fuzzy +msgid "External data source configuration" +msgstr "Configuração" -#: ../system/variables/config.rst:1 -msgid "``#{config.ticket_hook}``" +#: ../system/objects/external-data-source-example.rst:31 +msgid "" +"First, enter the search URL making sure it contains ``#{search.term}`` as a " +"parameter:" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``Ticket#``" +#: ../system/objects/external-data-source-example.rst:34 +msgid "**Example:** ``https://dummyjson.com/products/search?q=#{search.term}``" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > HTTP type" +#: ../system/objects/external-data-source-example.rst:36 +msgid "" +"After that, head down to the preview section and enter a search input for " +"the external data source." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.http_type}``" -msgstr "" +#: ../system/objects/external-data-source-example.rst:39 +#, fuzzy +msgid "**Example:** ``mac``" +msgstr "**Por exemplo:**" -#: ../system/variables/config.rst:1 -msgid "``https`` or ``http``" +#: ../system/objects/external-data-source-example.rst:41 +msgid "Then you can find a preview of the response data below:" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > SystemID" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of JSON response based on search term" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.system_id}``" +#: ../system/objects/external-data-source-example.rst:48 +msgid "" +"We recommend using the preview to have a look on the structure. There is a " +"top-level element called ``products``. One level below, you can find the " +"attributes ``id`` and ``title``." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``31`` (value between 1 and 99)" +#: ../system/objects/external-data-source-example.rst:52 +msgid "**Search result response based on search from example:**" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Organization" +#: ../system/objects/external-data-source-example.rst:119 +msgid "" +"To tell the remote system that the desired data is located below the " +"``products`` level, you have to put it in the field *Search result list key*." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.organization}``" +#: ../system/objects/external-data-source-example.rst:122 +msgid "" +"After inserting ``products`` in the mentioned field, you get an extended " +"preview. You can find an additional box *Search result list* with a JSON " +"structure. This is the same response as before but stripped from the upper " +"``products`` element by the external data source." msgstr "" -#: ../system/variables/config.rst:1 -msgid "" -"``Zammad GmbH`` value set in `Branding `_" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of JSON response search result list" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Product Name" +#: ../system/objects/external-data-source-example.rst:132 +msgid "" +"Now you need to provide the keys for the search result values and labels. As " +"already mentioned, we are looking for the ``id`` and the ``title`` of our " +"products. If you haven't already, it is now a good time to look at the " +"preview of the *Search result list*." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.product_name}``" +#: ../system/objects/external-data-source-example.rst:197 +msgid "" +"After locating our two keys, we insert them in *search result value key* " +"(``id``) and in *Search result label key* (``title``)." msgstr "" -#: ../system/variables/config.rst:1 +#: ../system/objects/external-data-source-example.rst:200 msgid "" -"``Helpdesk`` value set in `Branding `_" +"Basically, we configured the external data source already and we can see a " +"table in the preview section:" msgstr "" -#: ../system/variables/current-user.rst:2 -msgid "Current User" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of product table based on search term" msgstr "" -#: ../system/variables/current-user.rst:6 +#: ../system/objects/external-data-source-example.rst:208 msgid "" -"Current user variables always return values of the current user that caused " -"e.g. a trigger to run." +"According to our example story, now just the *Link template* is missing." msgstr "" -#: ../system/variables/current-user.rst:8 +#: ../system/objects/external-data-source-example.rst:210 msgid "" -"Due to the above fact, these variables are often not (yet) set or available " -"for usage." +"Please note that this is an optional feature. If you don't want to use such " +"links, of course you don't have to configure it." msgstr "" -#: ../system/variables/current-user.rst:10 +#: ../system/objects/external-data-source-example.rst:213 msgid "" -"In situations where e.g. schedulers or triggers run, this most likely is " -"nothing you want to use." +"We can add now an address where additional product information can be found." msgstr "" -#: ../system/variables/current-user.rst:13 -msgid "Current User Variables" +#: ../system/objects/external-data-source-example.rst:215 +msgid "Example: ``https://your_domain.com/q=#{ticket.product}``" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Web" +#: ../system/objects/external-data-source-example.rst:217 +msgid "In the example, the parameter means:" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.web}``" +#: ../system/objects/external-data-source-example.rst:219 +msgid "``#{}``: \"Frame\" for the insertion of information" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``https://zammad.org`` or empty if not set" +#: ../system/objects/external-data-source-example.rst:220 +msgid "``ticket``: object level, where you create your custom object" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > VIP" +#: ../system/objects/external-data-source-example.rst:221 +msgid "``product``: name of the (custom) object" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.vip}``" +#: ../system/objects/external-data-source-example.rst:223 +msgid "" +"After configuring your *Link template*, there will be another column in the " +"preview. Hovering on the icons in the *Link* column will show you where it " +"forwards you." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``false`` or ``true``" +#: ../system/objects/external-data-source-example.rst:232 +msgid "" +"In our example, one of the links looks like: https://your_domain.com/q=6, " +"where the 6 is the product id." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Web" +#: ../system/objects/external-data-source-example.rst:235 +msgid "You can find more information regarding the URL in :doc:`types`." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.web}``" +#: ../system/objects/includes/adding-values-hint.include.rst:3 +msgid "" +"Adding values can be tricky for first timers, don't forget to press \"➕ " +"Add\" after typing your values. Otherwise you may loose a value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > VIP" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:1 +#: ../system/objects/includes/reposition-values.include.rst:1 +msgid "**↕️ This field type allows the positioning of its values ↔️**" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.vip}``" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:3 +msgid "" +"In order to re-arrange the field values, first edit the field. Then you can " +"use ☰ to drag the values in question to the correct position. If you want to " +"change the layer depth, double click on ☰. With it you can cycle through the " +"available layers." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Phone" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:8 +msgid "When you're ready, submit your changes to save the object attribute." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.phone}``" +#: :0 ../system/objects/types.rst:0 +msgid "" +"Screencast showing how to re-position values on tree select like\n" +"fields" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``004930123456789`` or empty if not set" +#: ../system/objects/includes/reposition-values.include.rst:3 +msgid "" +"In order to re-arrange the field values, edit the field and scroll below the " +"values. Make sure to tick the option \"Use custom option sort\"." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Note" +#: ../system/objects/includes/reposition-values.include.rst:8 +msgid "" +"If you do not tick this field, all manual positioning you did above will be " +"lost upon saving! ☠️" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.note}``" +#: ../system/objects/includes/reposition-values.include.rst:11 +msgid "" +"Now use ☰ to drag the values in question to the correct position. When " +"you're ready, submit your changes to save the object attribute." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Some note to this user`` or empty if not set" +#: :0 ../system/objects/types.rst:0 +msgid "Screencast showing how to re-position values" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Mobile" +#: ../system/objects/includes/url-template-hint.include.rst:3 +msgid "" +"This field allows using :ref:`URL fields (Link Templates) `." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.mobile}``" -msgstr "" +#: ../system/objects/permissions.rst:2 +#, fuzzy +msgid "Attribute Permissions" +msgstr "Atributos do artigo" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``0049176123456789`` or empty if not set" +#: ../system/objects/permissions.rst:7 +msgid "" +"In the object attributes configuration you can define if a field is shown " +"and if the input in the field is mandatory, separated by different screens " +"and for different :doc:`roles/permissions `." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Login" +#: ../system/objects/permissions.rst:17 +msgid "Screenshot shows object attribute permission table" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.login}``" +#: ../system/objects/permissions.rst:17 +msgid "" +"Some of the possible permissions and screen options for a user object " +"attribute." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Lastname" +#: ../system/objects/permissions.rst:19 +msgid "" +"Based on the object context (ticket, agent, organization, user), the " +"selectable roles (to be precise: the required permissions) and screens " +"differ. Be aware that these settings aren't affecting data creation via " +"other channels than the UI." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.lastname}``" +#: ../system/objects/permissions.rst:24 +msgid "" +"If you want to have further customization possibilities, you should have a " +"look at the :doc:`core workflows `." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Firstname" +#: ../system/objects/permissions.rst:28 +#, fuzzy +msgid "Screens" +msgstr "Assinaturas" + +#: ../system/objects/permissions.rst:30 +msgid "" +"In the table below you can find an overview about the different permissions " +"and the available screens Zammad distinguishes between." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.firstname}``" +#: ../system/objects/permissions.rst:37 +#, fuzzy +msgid "Screen" +msgstr "Assinaturas" + +#: ../system/objects/permissions.rst:38 +msgid "Available for" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``John`` or empty if not set" +#: ../system/objects/permissions.rst:40 +msgid "create" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Fax" +#: ../system/objects/permissions.rst:41 ../system/objects/permissions.rst:52 +#: ../system/objects/permissions.rst:59 ../system/objects/permissions.rst:73 +msgid "admin.user" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.fax}``" -msgstr "" +#: ../system/objects/permissions.rst:42 ../system/objects/permissions.rst:53 +#: ../system/objects/permissions.rst:60 +#, fuzzy +msgid "admin.organization" +msgstr "Organização" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``004930123464789`` or empty if not set" +#: ../system/objects/permissions.rst:43 ../system/objects/permissions.rst:54 +#: ../system/objects/permissions.rst:61 +msgid "admin.group" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Email" +#: ../system/objects/permissions.rst:44 +msgid "Creation dialog for not yet existing data" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.email}``" +#: ../system/objects/permissions.rst:45 +msgid "create_middle" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``jdoe@customer.tld``" -msgstr "" +#: ../system/objects/permissions.rst:46 ../system/objects/permissions.rst:50 +#: ../system/objects/permissions.rst:57 ../system/objects/permissions.rst:66 +#: ../system/objects/permissions.rst:70 +#, fuzzy +msgid "ticket.customer" +msgstr "Criar uma macro global" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Department" -msgstr "" +#: ../system/objects/permissions.rst:47 ../system/objects/permissions.rst:51 +#: ../system/objects/permissions.rst:58 ../system/objects/permissions.rst:69 +#, fuzzy +msgid "ticket.agent" +msgstr "Criar uma macro global" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.department}``" +#: ../system/objects/permissions.rst:48 +msgid "Ticket create dialog (middle section)" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Sales`` or empty if not set" +#: ../system/objects/permissions.rst:49 +msgid "edit" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Avatar" +#: ../system/objects/permissions.rst:55 +msgid "Editing dialog for already existing data" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.avatar(60,60)}``" +#: ../system/objects/permissions.rst:56 +msgid "view" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "avatar picture with width and height in pixel (e.g. 60,60)" +#: ../system/objects/permissions.rst:62 +msgid "View-only dialog for already existing data" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Address" +#: ../system/objects/permissions.rst:64 +msgid "(e.g. user or organization from search)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.address}``" +#: ../system/objects/permissions.rst:65 +msgid "signup" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Some street 1, 12345 Berlin`` or empty if not set" +#: ../system/objects/permissions.rst:67 +msgid "Sign-up screen for new customers" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated at" +#: ../system/objects/permissions.rst:68 +msgid "invite_customer" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_at}``" +#: ../system/objects/permissions.rst:71 +msgid "" +"Customer invitation screen (from :doc:`First Steps ` area)" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC``" +#: ../system/objects/permissions.rst:72 +msgid "invite_agent" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Phone" +#: ../system/objects/permissions.rst:74 +msgid "" +"Agent invitation screen (from :doc:`First Steps ` area)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.phone}``" -msgstr "" +#: ../system/objects/permissions.rst:78 +#, fuzzy +msgid "Screen Options" +msgstr "Organizações" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Shared organization" +#: ../system/objects/permissions.rst:80 +msgid "" +"For the different screens you can select \"show\" and \"required\" options." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.shared}``" +#: ../system/objects/permissions.rst:82 +msgid "**shown:** Show (check) or hide (uncheck) a field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Note" +#: ../system/objects/permissions.rst:83 +msgid "" +"**required:** Set a field to mandatory (check). Forces users (via UI and " +"API) to populate the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.note}``" -msgstr "" +#: ../system/objects/types.rst:7 +#, fuzzy +msgid "Example external data source" +msgstr "Configuração" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``A note to the organization of the user`` or empty if not set" -msgstr "" +#: ../system/objects/types.rst:2 +#, fuzzy +msgid "Attribute types" +msgstr "Atributos do artigo" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Name" +#: ../system/objects/types.rst:4 +msgid "" +"When adding a new object attribute, you can choose between the following " +"attribute types." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.name}``" +#: ../system/objects/types.rst:14 +msgid "" +"You cannot change the attribute format / type as soon as it is applied. If " +"you no longer need an object attribute, consider disabling it instead of " +"removing." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``Zammad GmbH``" +#: ../system/objects/types.rst:18 +msgid "**What about the translation of my attributes?**" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Domain based assignment" +#: ../system/objects/types.rst:20 +msgid "" +"For some attribute types you can decide if they should be translatable or " +"not. To be precise, it works only for the selectable fields because the " +"possible choices are known and limited. For the following attribute types, " +"you can set the translatable flag:" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.domain_assignment}``" -msgstr "" +#: ../system/objects/types.rst:25 +#, fuzzy +msgid "*Boolean field*" +msgstr "Booleano" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Domain" +#: ../system/objects/types.rst:26 +msgid "*Single selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.domain}``" +#: ../system/objects/types.rst:27 +msgid "*Multiple selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``zammad.com`` or empty if not set" +#: ../system/objects/types.rst:28 +msgid "*Single tree selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > VIP" +#: ../system/objects/types.rst:29 +msgid "*Multiple tree selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.vip}``" +#: ../system/objects/types.rst:31 +msgid "" +"For these types, you can find an additional field *Translate field contents*:" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Note" +#: ../system/objects/types.rst:0 +msgid "Screenshot showing translatable attribute types" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.note}``" +#: ../system/objects/types.rst:38 +msgid "Screenshot with example of translatable attribute type" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Mobile" -msgstr "" +#: ../system/objects/types.rst:45 +#, fuzzy +msgid "Boolean field" +msgstr "Booleano" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.mobile}``" +#: ../system/objects/types.rst:41 +msgid "" +"Provides a drop-down field with display values for ``true`` and ``false``. " +"Setting a default is mandatory." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Login" +#: ../system/objects/types.rst:0 +msgid "Available settings for Boolean fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.login}``" +#: ../system/objects/types.rst:55 +msgid "Date field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Lastname" +#: ../system/objects/types.rst:48 +msgid "Provides a date picker field and does not allow default values." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.lastname}``" +#: ../system/objects/types.rst:52 +msgid "Default time diff (hours)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Firstname" +#: ../system/objects/types.rst:51 +msgid "" +"This setting helps the user by highlighting the day from now plus the " +"provided value. It *does not* pre-fill the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.firstname}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Date fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Fax" +#: ../system/objects/types.rst:73 +msgid "Date & time field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.fax}``" +#: ../system/objects/types.rst:58 +msgid "Provides a date and time picker – does not allow default values" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Email" +#: ../system/objects/types.rst:62 +msgid "Allow future" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.email}``" +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the future." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Department" +#: ../system/objects/types.rst:66 +msgid "Allow past" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.department}``" +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the past." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Web" +#: ../system/objects/types.rst:70 +msgid "Default time diff (minutes)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.web}``" +#: ../system/objects/types.rst:69 +msgid "" +"This setting helps the user by highlighting the day from now plus the " +"provided value. It does not pre-fill the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > VIP" +#: ../system/objects/types.rst:0 +msgid "Available settings for Date & time fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.vip}``" -msgstr "" +#: ../system/objects/types.rst:86 +#, fuzzy +msgid "Integer field" +msgstr "Inteiro" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Phone" +#: ../system/objects/types.rst:76 +msgid "" +"Provides an input field that allows integer usage only. You may define a " +"default value. You cannot enforce comma separation." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.phone}``" +#: ../system/objects/types.rst:80 +msgid "Minimal" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Note" +#: ../system/objects/types.rst:80 +msgid "The minimal value the field accepts." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.note}``" +#: ../system/objects/types.rst:83 +msgid "Maximal" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Mobile" +#: ../system/objects/types.rst:83 +msgid "The maximum value the field accepts." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.mobile}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Integer fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Login" +#: ../system/objects/types.rst:99 +msgid "Multiple selection field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.login}``" +#: ../system/objects/types.rst:89 +msgid "" +"Provides a selection field that allows the selection of one or more out of " +"several. This field does allow setting a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Lastname" +#: ../system/objects/types.rst:0 +msgid "Available settings for Multiple selection fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.lastname}``" +#: ../system/objects/types.rst:112 +msgid "Single selection field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Firstname" +#: ../system/objects/types.rst:102 +msgid "" +"Provides a drop-down field that allows selection of one value out of " +"several. This field does allow setting a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.firstname}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Single selection fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Fax" -msgstr "" +#: ../system/objects/types.rst:142 +#, fuzzy +msgid "Textarea field" +msgstr "Texto" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.fax}``" +#: ../system/objects/types.rst:115 +msgid "" +"Provides a text area input field (multiple lines) and thus allows e.g. new " +"lines. You can set a default field value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Email" +#: ../system/objects/types.rst:120 +msgid "" +"Please note that this field *does not* support text formatting or HTML " +"content (rich text)." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.email}``" +#: ../system/objects/types.rst:123 +msgid "**🥵 This field can consume a lot of visual space**" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Department" +#: ../system/objects/types.rst:125 +msgid "" +"Depending on where you use this field type, it may use a lot of visual space " +"if you provide a lot of text. This may be an issue to work with." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.department}``" +#: ../system/objects/types.rst:130 +msgid "Default" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Avatar" +#: ../system/objects/types.rst:129 +msgid "" +"The here provided text will be shown within the text area field or new data " +"sets." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.avatar(60,60)}``" +#: ../system/objects/types.rst:134 ../system/objects/types.rst:160 +msgid "Maxlength" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Address" +#: ../system/objects/types.rst:0 ../system/objects/types.rst:160 +msgid "You can pick the maximum length of the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.address}``" +#: ../system/objects/types.rst:0 +msgid "The default length of this object is ``500``." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created at" +#: ../system/objects/types.rst:139 +msgid "Rows" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_at}``" +#: ../system/objects/types.rst:0 +msgid "" +"Change the number of rows to dislay so that you can use only the space you " +"really need." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Avatar" +#: ../system/objects/types.rst:0 +msgid "The default number of rows is ``4``." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.avatar(60,60)}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Textarea fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Address" +#: ../system/objects/types.rst:165 +msgid "Text field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.address}``" +#: ../system/objects/types.rst:145 +msgid "Provides a text field (one line) and allows choosing a default value." msgstr "" -#: ../system/variables/ticket.rst:6 +#: ../system/objects/types.rst:148 msgid "" -"Below you can find all available ticket-based variables within Zammad. These " -"can be called via Triggers for example. If you're unsure if Zammad does " -"support variables at the point you're at, you can try to type ``::`` to " -"check." +"Defines the type of the input field. This allows e.g. your browser to ensure " +"that you provide the specific type." msgstr "" -#: ../system/variables/ticket.rst:12 -msgid "Ticket Variables" +#: ../system/objects/types.rst:152 +msgid "Currently available:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Web" +#: ../system/objects/types.rst:155 +msgid "Phone" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.web}``" -msgstr "" +#: ../system/objects/types.rst:156 +msgid "Text" +msgstr "Texto" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > VIP" +#: ../system/objects/types.rst:157 +msgid "Url *(URL fields disable link-template availability)*" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.vip}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Text fields" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Phone" +#: ../system/objects/types.rst:174 +msgid "Single tree selection field" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.phone}``" +#: ../system/objects/types.rst:168 +msgid "" +"Provides a select-like field with up to 6 layers of options. Does not allow " +"setting a default value." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Note" +#: ../system/objects/types.rst:0 +msgid "Available settings for Tree Select fields" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.note}``" +#: ../system/objects/types.rst:183 +msgid "Multiple tree selection field" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Mobile" +#: ../system/objects/types.rst:177 +msgid "" +"Provides a select-like field with up to 6 layers of options allowing the " +"selection of multiple values. Does not allow setting a default value." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.mobile}``" +#: ../system/objects/types.rst:302 +msgid "External Data Source field" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Login" +#: ../system/objects/types.rst:186 +msgid "" +"Provides a searchable field which fetches data from an external system. This " +"can be useful if you have data outside of Zammad and don't want to maintain " +"both data sources." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.login}``" +#: ../system/objects/types.rst:190 +msgid "The feature works as follows:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Lastname" +#: ../system/objects/types.rst:192 +msgid "" +"Zammad sends a query with a search string (free text from agent or based on " +"a variable) in a pre-defined format (\"Search URL\") to an external system." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.lastname}``" +#: ../system/objects/types.rst:195 +msgid "" +"This external system searches for matches and provides a response as a JSON " +"structure to Zammad." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Firstname" +#: ../system/objects/types.rst:197 +msgid "" +"Zammad just looks for the defined list and value keys, reads the content and " +"displays the value to the user. There is no search on Zammad side." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.firstname}``" +#: ../system/objects/types.rst:201 +msgid "" +"The usage of a PostgreSQL database for Zammad is required. In any other " +"case, Zammad will hide the external data source type and you are not able to " +"use it. If you want to use this feature, consider to :docs:`migrate your " +"database `." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Fax" +#: ../system/objects/types.rst:205 +msgid "Currently, only ``GET`` is supported as request method." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.fax}``" +#: ../system/objects/types.rst:206 +msgid "" +"The data structure must be in JSON format and provide the objects in an " +"array." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Email" +#: ../system/objects/types.rst:208 +msgid "" +"The endpoint for the external data source has to support search. On Zammad " +"side, there is no search/logic implemented; however, you can define the " +"output key and value based on the result(s) from the response (which " +"provides already filtered content based on the search)." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.email}``" +#: ../system/objects/types.rst:212 +msgid "" +"If you receive more results as expected, your external data source search " +"may not work properly or the structure of the URL is not correct. You should " +"get in touch with a responsible person from the external system." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Department" +#: ../system/objects/types.rst:217 +msgid "" +"Please have a look :doc:`at our example `, where you can find a possible configuration for a public " +"dummy endpoint." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.department}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for external data source fields" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Avatar" +#: ../system/objects/types.rst:242 +msgid "Search URL" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.avatar(60,60)}``" +#: ../system/objects/types.rst:227 +msgid "" +"Set your endpoint where Zammad fetches the data. Please make sure to include " +"a valid search :doc:`variable ` as an URL parameter. " +"Example for a free text search at user input: ``#{search.term}``" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Address" +#: ../system/objects/types.rst:232 +msgid "" +"If in doubt, ask the responsible person for the external data source how " +"they expect the structure of the URL." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.address}``" +#: ../system/objects/types.rst:236 +msgid "" +"Depending on your search variable, the preview might work or not. The reason " +"is that the context might not be available and it is no bug." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated at" +#: ../system/objects/types.rst:239 +msgid "" +"Please also make sure to use a variable which is available in your object " +"context. For example you won't be able to search for a ticket in a user " +"object context." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_at}``" +#: ../system/objects/types.rst:252 +#, fuzzy +msgid "SSL Verification" +msgstr "Limitação" + +#: ../system/objects/types.rst:245 +msgid "Here you can switch the SSL verification to no." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Title" +#: ../system/objects/types.rst:249 +msgid "" +"If your external data source system is using self signed certificates, " +"please have a look :doc:`here ` for " +"further information about how to handle them in Zammad, so you can keep the " +"SSL verification activated." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.title}``" +#: ../system/objects/types.rst:258 +msgid "HTTP Authentication" msgstr "" -#: ../system/variables/ticket.rst:1 +#: ../system/objects/types.rst:255 msgid "" -"``My amazing Subject`` (normally subject, can be edited within Interface and " -"thus differ)" +"If your external data source requires an authentication, you can set it " +"here. You can leave it empty or choose between *Basic Authentication* or " +"*Authentication Token* (selecting one of the two methods leads to additional " +"fields where you can enter your credentials/token)." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Accounted Time" +#: ../system/objects/types.rst:265 +msgid "Search result list key" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.time_unit}``" +#: ../system/objects/types.rst:261 +msgid "" +"Defines the level in the JSON structure which provides the list with search " +"results. You can leave it empty, if the data is already provided as an " +"array. If you have to go deeper in the structure, you can provide a path " +"with ``.`` as separators, e.g. ``key.subkey.sub-sub-key``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``1``, ``2.75`` or empty response" +#: ../system/objects/types.rst:271 +msgid "Search result value key" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Tags" +#: ../system/objects/types.rst:268 +msgid "" +"Defines the attribute in the structure in which your external data source " +"provides the *value* for your data. An example would be a product *number*. " +"If you have to go deeper in the structure, you can provide a path with ``.`` " +"as separators, e.g. ``key.subkey.sub-sub-key``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.tags}``" +#: ../system/objects/types.rst:277 +msgid "Search result label key" msgstr "" -#: ../system/variables/ticket.rst:1 +#: ../system/objects/types.rst:274 msgid "" -"Currently not available, see `Issue 2769 `_" +"Defines the attribute in the structure in which your external data source " +"provides the *label* for your data. An example would be a product *name*. If " +"you have to go deeper in the structure, you can provide a path with ``.`` as " +"separators, e.g. ``key.subkey.sub-sub-key``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > State > Name" +#: ../system/objects/types.rst:280 +msgid "" +"In the preview area, you can find the following items (depending on your " +"configuration above):" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.state.name}``" +#: ../system/objects/types.rst:283 +msgid "" +"**Error/hint message** (only if configuration is not complete): Zammad tells " +"you, if there is a problem and what you should change in your configuration." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``new``, ``open``, ..." +#: ../system/objects/types.rst:286 +msgid "" +"**Search field**: search for an existing attribute in the data source to get " +"a preview. This is required for the fields below to show up." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Priority > Name" +#: ../system/objects/types.rst:288 +msgid "" +"**Search result response** (only if configuration is not complete): here you " +"can find a syntax highlighted JSON preview of the response, based on the " +"search term you entered." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.priority.name}``" +#: ../system/objects/types.rst:291 +msgid "" +"**Search result list** (only if *search result list key* is properly set): " +"output of the structure under the configured *search result list key*." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2 normal``" +#: ../system/objects/types.rst:294 +msgid "" +"**Preview table** (when fully configured): Zammad shows you a table which " +"includes the found items based on the search string (value, label and " +"optional link). You can use this preview if you don't have the complete data " +"structure of the external system in mind." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Pending till" +#: ../system/objects/types.rst:299 +msgid "" +"An example of a configured external data source field from agent perspective:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.pending_time}``" +#: ../system/objects/types.rst:0 +msgid "Screencast showing the search for a product in a ticket" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not set" +#: ../system/objects/types.rst:307 +msgid "URL fields (Link-Template)" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Web" +#: ../system/objects/types.rst:311 +msgid "" +"This function is restricted to Text, Select and External data source types " +"only." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.web}``" +#: ../system/objects/types.rst:314 +msgid "" +"Link-Templates are an amazing way to dynamically generate URLs. They allow " +"you to integrate other systems better without having to manually copy data " +"from Zammad if possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``https://zammad.com`` or empty if not set" +#: ../system/objects/types.rst:320 +msgid "" +"Another great way of communicating with another system may be Zammad's :doc:" +"`Webhooks `." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > VIP" +#: ../system/objects/types.rst:323 +msgid "" +"After filling a link-template enabled field, an URL icon will appear on its " +"right. Clicking on the icon opens a new tab." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.vip}``" +#: ../system/objects/types.rst:328 +msgid "" +"Even though Zammad displays the link template within object edit and create " +"screens, the function is optional. It's only active if you populate the " +"field." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Phone" +#: ../system/objects/types.rst:333 +msgid "" +"What's the difference between URL and text fields with link template...?!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.phone}``" +#: ../system/objects/types.rst:335 +msgid "" +"Both fields have different use cases. Use ``text`` type text fields when " +"ever you have a *static* url that requires dynamic parameters. If you " +"require a drag & drop like field that you can put in any URL, use ``URL`` " +"type text fields." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Note" +#: ../system/objects/types.rst:340 +msgid "" +"The difference is easier to spot when comparing the fields directly, below " +"screencast shows the result - the dynamic approach uses existing values in " +"the moment of updating to built the URL - e.g. ``https://google.com/search?" +"q=cookies`` - while the URL approach uses the actual URL of the field - e.g. " +"``https://zammad.com``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.note}``" +#: ../system/objects/types.rst:None +msgid "" +"Screencast showing the differents in between URL and text type fields with " +"actual values" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Mobile" -msgstr "" +#: ../system/objects/types.rst:352 +msgid "How does this work...?!" +msgstr "Como isso funciona...?!" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.mobile}``" +#: ../system/objects/types.rst:354 +msgid "" +"As an example, let's say you have an attribute called ``amazing_attribute`` " +"and you want to open a google search directly with the input from that field." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Login" +#: ../system/objects/types.rst:357 +msgid "" +"Providing the link-template field below allows you to do so: ``https://www." +"google.com/search?q=#{ticket.amazing_attribute}``" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.login}``" +#: ../system/objects/types.rst:362 +msgid "" +"You can use any :doc:`Zammad variable ` as long as it's " +"available in the moment you need it." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``agent``" +#: ../system/objects/types.rst:365 +msgid "" +"As a result, you are redirected to Google with a search for the value of the " +"attribute, if you click on the button in the ticket (as you can see in the " +"screencast above)." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Lastname" -msgstr "" +#: ../system/packages.rst:2 +msgid "Packages" +msgstr "Pacotes" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.lastname}``" -msgstr "" +#: ../system/packages.rst:4 +msgid "That's the package management-area." +msgstr "Esta é a área de gerenciamento de pacotes." -#: ../system/variables/ticket.rst:1 -msgid "``Mustermann`` or empty if not set" +#: ../system/packages.rst:6 +msgid "Individual add-ons for Zammad can be installed and managed here." msgstr "" +"Add-ons individuais para o Zammad podem ser instalados e gerenciados aqui." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Firstname" -msgstr "" +#: ../system/sessions.rst:2 +msgid "Sessions" +msgstr "Sessões" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.firstname}``" +#: ../system/sessions.rst:4 +msgid "" +"Sessions management allows reviewing currently known user sessions and " +"allows to end these. The session timeout is affected by :ref:" +"`security_session_timeout` configurations from security settings." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Max`` or empty if not set" +#: ../system/sessions.rst:None +msgid "Screenshot showing Zammad's session management" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Fax" -msgstr "" +#: ../system/sessions.rst:13 +#, fuzzy +msgid "Zammad will provide the following information:" +msgstr "Esta sessão atualmente carece das seguintes integrações:" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.fax}``" +#: ../system/sessions.rst:16 +msgid "" +"The user account this session entry belongs to. It can be normal if a user " +"has several sessions in the list. This can be due to changed browser " +"information or if you use e.g. single sign on methods where the user does " +"not use the log off button." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Email" +#: ../system/sessions.rst:22 +msgid "Browser" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.email}``" +#: ../system/sessions.rst:22 +msgid "The browser agent communicated to Zammad." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``agent@company.tld`` or empty if not set" -msgstr "" +#: ../system/sessions.rst:40 +#, fuzzy +msgid "Location" +msgstr "Limitação" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Department" +#: ../system/sessions.rst:25 +msgid "" +"The anticipated location based on the users IP address. Depending on the IP " +"address the result shown may differ. This option depends on :doc:`/settings/" +"system/services`." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.department}``" +#: ../system/sessions.rst:29 +msgid "The following information can be shown:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Support`` or empty if not set" +#: ../system/sessions.rst:33 +msgid "IP address" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Avatar" +#: ../system/sessions.rst:32 +msgid "" +"Either if you set *Geo IP services* to inactive or you're using internal IP " +"address which do not provide location information." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.avatar(60,60)}``" +#: ../system/sessions.rst:40 +msgid "Country (or Country + City)" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Address" +#: ../system/sessions.rst:36 +msgid "" +"If *Geo IP services* is enabled only. Depends on how detailed the available " +"IP address information are." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.address}``" +#: ../system/sessions.rst:39 +msgid "" +"Be aware that results can be inaccurate - this technically is not an error." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Shared organization" +#: ../system/sessions.rst:43 +msgid "Age" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.shared}``" +#: ../system/sessions.rst:43 +msgid "Provides the time when the session initially has been created." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Note" -msgstr "" +#: ../system/sessions.rst:50 +#, fuzzy +msgid "Update" +msgstr "Tempo de atualização" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.note}``" +#: ../system/sessions.rst:46 +msgid "" +"Provides the time the user used this session to open Zammad. This timestamp " +"is only updated if the user e.g. reloads, not during normal work on tickets." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Name" +#: ../system/sessions.rst:50 +msgid "This timestamp is being used for the session timeout." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.name}``" +#: ../system/sessions.rst:53 +msgid "" +"Use the delete button to remove a single session on behalf of your user." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Zammad GmbH`` or empty if not set" -msgstr "" +#: ../system/subscription.rst:2 +#, fuzzy +msgid "Subscription (SaaS)" +msgstr "Descrição" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Domain based assignment" +#: ../system/subscription.rst:4 +msgid "" +"The subscription settings page allows you to configure your instances " +"package and number of agents required." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.domain_assignment}``" +#: ../system/subscription.rst:9 +msgid "" +"This setting section is only available for Hosted setups. If you're looking " +"for on premise support contracts, please see the `Zammad pricing page " +"`_." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Domain" +#: ../system/subscription.rst:14 ../system/subscription.rst:34 +msgid "Plan" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.domain}``" +#: ../system/subscription.rst:16 +msgid "" +"Here you can set up everything affecting your instance subscription " +"functions like number of agents and package." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``domain.tld`` or empty if not set" +#: ../system/subscription.rst:19 +msgid "" +"On top of the page you can find a subscription summary. You'll find the " +"number of used and available (booked) agent seats there. By using the *see " +"more* link you can also expand an agent list to see the currently configured " +"active agents. This list *does not* count accounts with admin permissions " +"only." msgstr "" -#: ../system/variables/ticket.rst:1 -#, fuzzy -msgid "Ticket > Organization > VIP" -msgstr "Organização" - -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.vip}``" +#: ../system/subscription.rst:None +msgid "" +"Within subscription you can always see how many agents are still\n" +"available to add and who uses the seats." msgstr "" -#: ../system/variables/ticket.rst:1 -#, fuzzy -msgid "Ticket > Number" -msgstr "Árvore de Seleção" - -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.number}``" +#: ../system/subscription.rst:29 +msgid "" +"Learn more on how to manage your agents in general :doc:`here `." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``31001``, ``201910731001``, ..." +#: ../system/subscription.rst:36 +msgid "" +"This section gives you an overview of the available plans and their " +"functions / limits. If you require a more detailed table, check our " +"`detailed pricing table `_ for more." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > ID" +#: ../system/subscription.rst:40 +msgid "" +"Your selection in this step will decide on the base agent price and e.g. " +"agent limits that might apply in the summary step." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.id}``" +#: ../system/subscription.rst:43 +msgid "" +"The green *Selected* button will also tell you what plan you're currently in." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``17``, ``5281``, ..." +#: ../system/subscription.rst:47 +msgid "" +"Trial instances are running at Professional with 3 agents. The plan cannot " +"be changed during the trial for technical reasons, if you require more " +"agents for testing, please contact `our sales team `_ with a reason for the raise request." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact (customer)" +#: ../system/subscription.rst:None +msgid "" +"Screenshot showing three available packages for a hosted Zammad\n" +"instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_customer_at}``" +#: ../system/subscription.rst:57 +msgid "" +"At the bottom of this block you can find a summary where you can adjust the " +"settings of the previous selected plan." msgstr "" -#: ../system/variables/ticket.rst:1 +#: ../system/subscription.rst:62 msgid "" -"``2019-10-07 16:25:00 UTC`` or empty if not applicable yet (Please note " -"`Ticket last contact behavior Settings `_ for this)" +"Note that upgrading (more agents, higher package) is always possible, " +"however, downgrading will only happen when your billing period renews." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact" +#: ../system/subscription.rst:66 +msgid "" +"Upgrading resets your billing period and existing credit will be deducted " +"from the new total." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_at}``" +#: ../system/subscription.rst:75 +msgid "Billing cycle" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact (agent)" +#: ../system/subscription.rst:70 +msgid "" +"You can choose between either monthly or yearly billing. The price per agent " +"will be cheaper if you decide for yearly billing." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_agent_at}``" +#: ../system/subscription.rst:73 +msgid "" +"If you're still trying out things and are unsure of the right package for " +"your instance, you may want to choose monthly first and then upgrade to " +"yearly when you're sure." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable yet" +#: ../system/subscription.rst:83 +msgid "Plan: (Starter|Professional|Plus) - Agents" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Note" +#: ../system/subscription.rst:78 +msgid "Choose the number of agents you require for your instance." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.note}``" +#: ../system/subscription.rst:80 +msgid "" +"Keep in mind that some packages may have agent limits. Depending on the " +"previous chosen package, you won't be able to exceed specific agent numbers. " +"Also note that setting less agents than currently configured is not possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Note about this group``" +#: ../system/subscription.rst:86 +msgid "Total" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Name" +#: ../system/subscription.rst:86 +msgid "This will be the net total you're going to be billed." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.name}``" +#: ../system/subscription.rst:88 +msgid "" +"By using the *Update subscription* button, the instance package will be " +"adjusted immediately. If you didn't provide a payment method yet, Zammad " +"will request you to provide one at this point." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Sales``" +#: ../system/subscription.rst:94 +msgid "" +"In case you're still within the trial period, this means that the trial will " +"be over immediately!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Follow-up possible" +#: ../system/subscription.rst:97 +msgid "Down- or upgrading during the trial period *is not* possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.follow_up_possible}``" +#: ../system/subscription.rst:None +msgid "Screenshot showing payment options and a pricing summary" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``no`` or ``yes``" +#: ../system/subscription.rst:103 +msgid "Billing Information" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Assign Follow-Ups" +#: ../system/subscription.rst:105 +msgid "" +"You can control all billing relevant information like invoices, billing " +"address and the option to cancel your subscription." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.follow_up_assignment}``" +#: ../system/subscription.rst:108 +msgid "" +"All adjusted billing information below only affect future invoices. If your " +"invoice was issued wrong, please contact `our sales team `_." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Assignment Timeout" +#: ../system/subscription.rst:114 +msgid "Billing address" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.assignment_timeout}``" +#: ../system/subscription.rst:113 +msgid "" +"Provide your company address here, make sure to include the companies name " +"in case required. This address will be referenced on your invoice." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``20`` or empty if not configured" +#: ../system/subscription.rst:118 +msgid "VAT ID" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > First response" +#: ../system/subscription.rst:117 +msgid "" +"Provide your VAT ID here. If applicable your invoice will not contain German " +"VAT. Please make sure to pay the VAT in your country as required." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.first_response_at}``" +#: ../system/subscription.rst:127 +msgid "Billing Email Address" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Escalation at" +#: ../system/subscription.rst:121 +msgid "" +"Usually the instance owner (the person that registered the instance) will " +"receive all emails including the invoices. In case you have your own billing " +"department, you can provide their email address here." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.escalation_at}``" +#: ../system/subscription.rst:125 +msgid "" +"All billing relevant information will then be sent to this email address." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable" +#: ../system/subscription.rst:127 +msgid "Invoices are sent as attachment (PDF) to this email address." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Web" +#: ../system/subscription.rst:129 +msgid "" +"Don't forget to press the *Update billing information* button after you " +"changed above settings." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.web}``" +#: ../system/subscription.rst:None +msgid "" +"Screenshot showing options for billing information within the\n" +"subscription menu" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > VIP" +#: ../system/subscription.rst:137 +msgid "Payment Method" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.vip}``" +#: ../system/subscription.rst:139 +msgid "You can pay via credit card or SEPA mandate." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Phone" +#: ../system/subscription.rst:144 +msgid "Credit card" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.phone}``" +#: ../system/subscription.rst:142 +msgid "" +"Simply follow the dialogue by clicking *authorize credit card* and confirm -" +"if required by your bank- your consent to Zammad using your card for the " +"payments." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Note" +#: ../system/subscription.rst:148 +msgid "SEPA Direct Debit" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.note}``" +#: ../system/subscription.rst:147 +msgid "" +"Provide the requested information of the bank account holder and update if " +"you're ready. You'll then receive an email with the SEPA mandate." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Mobile" +#: ../system/subscription.rst:150 +msgid "" +"Technically there's also the possibility to pay via invoice, however - this " +"method only applies to a fairly low number of instances. Please contact `our " +"sales team `_ for more information." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.mobile}``" -msgstr "" +#: ../system/subscription.rst:156 +#, fuzzy +msgid "Cancel Subscription" +msgstr "Descrição" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Login" +#: ../system/subscription.rst:158 +msgid "" +"Do you want to cancel your subscription? In case you no longer want to use " +"Zammad's SaaS, you can cancel your subscription by using the red *Yes, " +"please cancel my subscription* button." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.login}``" +#: ../system/subscription.rst:162 +msgid "" +"To cancel the description, enter the FQDN of your Zammad instance and " +"provide a reason for your cancellation." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Lastname" +#: ../system/subscription.rst:165 +msgid "" +"Your subscription will end the day after your trial or billing period ends." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.lastname}``" +#: ../system/subscription.rst:None +msgid "Screenshot showing subscription cancellation dialog" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Firstname" +#: ../system/subscription.rst:174 +msgid "" +"We will remind you about your cancelled subscription several times up front. " +"After the subscription ended all instance data will be removed. A restore " +"*is not* possible after that point!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.firstname}``" +#: ../system/subscription.rst:178 +msgid "**😖 Cancelled by accident?**" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Fax" +#: ../system/subscription.rst:180 +msgid "" +"You can always undo the cancellation via the *Yes, undo the cancellation of " +"my subscription* button up to the last subscription day!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.fax}``" +#: ../system/subscription.rst:0 +msgid "" +"Screenshot showing a red button to cancel the subscription\n" +"cancellation" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Email" +#: ../system/subscription.rst:189 +msgid "Payment History" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.email}``" +#: ../system/subscription.rst:191 +msgid "" +"The payment history will display a history of all paid invoices. At this " +"point you can also download these in case you need them again." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Department" +#: ../system/subscription.rst:196 +msgid "" +"You will only find *paid* invoices here. Invoices that are to be billed are " +"not available before the payment is completed." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.department}``" +#: ../system/subscription.rst:201 +msgid "Date" +msgstr "Data" + +#: ../system/subscription.rst:201 +msgid "Date of the invoice creation." msgstr "" -#: ../system/variables/ticket.rst:1 +#: ../system/subscription.rst:204 #, fuzzy -msgid "Ticket > Customer > Avatar" -msgstr "Árvore de Seleção" +msgid "Amount" +msgstr "Contas" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.avatar(60,60)}``" +#: ../system/subscription.rst:204 +msgid "Invoice total including VAT if applicable." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Address" +#: ../system/subscription.rst:207 +msgid "" +"Contains contract period (monthly or yearly) and hosted plan for the " +"subscription period in question." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.address}``" +#: ../system/subscription.rst:218 +msgid "Payment method / Service period" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Web" +#: ../system/subscription.rst:211 +msgid "" +"Used bank account or credit card as well as the subscription period the " +"invoice is about." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.web}``" +#: ../system/subscription.rst:216 +msgid "" +"It might happen that the invoice date and subscription period differ. This " +"is nothing to worry about, the subscription periods will be accounted later " +"on." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > VIP" +#: ../system/subscription.rst:222 +msgid "Receipt" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.vip}``" +#: ../system/subscription.rst:221 +msgid "" +"Use the arrow to download the invoice in question. You can download all " +"available invoices any time you need to here!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Phone" +#: ../system/subscription.rst:None +msgid "Screenshot showing payment history of a hosted instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.phone}``" +#: ../system/subscription.rst:229 +msgid "FAQ" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Note" +#: ../system/subscription.rst:233 +msgid "I set up a trial account but am missing functions to test" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.note}``" +#: ../system/subscription.rst:232 +msgid "" +"The trial instance is running within the professional package allowing up to " +"three agents." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Mobile" +#: ../system/subscription.rst:236 +msgid "Can I change package within the trial?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.mobile}``" +#: ../system/subscription.rst:236 +msgid "No. As soon as the package is changed the subscription begins." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Login" +#: ../system/subscription.rst:241 +msgid "What happens to my trial instance after the trial period ended?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.login}``" +#: ../system/subscription.rst:239 +msgid "" +"Your instance will automatically be canceled for you. Please see *What " +"happens to my instance after it has been canceled?* for more." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Lastname" +#: ../system/subscription.rst:254 +msgid "What happens to my instance after it has been canceled?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.lastname}``" +#: ../system/subscription.rst:244 +msgid "That depends slightly on your instance state:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Firstname" +#: ../system/subscription.rst:250 +#, fuzzy +msgid "Trial instance" +msgstr "Manutenção" + +#: ../system/subscription.rst:247 +msgid "" +"If you're still on trial, we will ice your instance and remind you once " +"again about your instance. We then will wait some days and remove your " +"instance from our system. This is the last time we will inform you by Email." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.firstname}``" +#: ../system/subscription.rst:254 +#, fuzzy +msgid "Paid instance" +msgstr "Manutenção" + +#: ../system/subscription.rst:253 +msgid "" +"If you're a paying customer and canceled your subscription, the instance " +"removal will take place the day after your last subscription day." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Fax" +#: ../system/subscription.rst:256 +msgid "Can removed instances be restored?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.fax}``" +#: ../system/subscription.rst:257 +msgid "No. Once your instance has been removed, a restoration is not possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Email" +#: ../system/system-report.rst:2 +#, fuzzy +msgid "System Report" +msgstr "Sistema" + +#: ../system/system-report.rst:4 +msgid "" +"In this place you can't configure Zammad. Instead you can obtain a system " +"report about Zammad and its configuration." +msgstr "" + +#: ../system/system-report.rst:7 +msgid "" +"See the description in Zammad for an explanation. You can even find a " +"preview of the included data below the **Download** button." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.email}``" +#: ../system/system-report.rst:10 +msgid "" +"Zammad never sends this automatically to anyone. It is a manual process only " +"to provide better support based on your configuration." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Department" -msgstr "" +#: ../system/translations.rst:2 +msgid "Translations" +msgstr "Traduções" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.department}``" +#: ../system/translations.rst:4 +msgid "" +"Translations of Zammad are processed centrally in our `Weblate instance " +"`_. This allows non-developers to review " +"and update translation texts of the language they actually speak." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Avatar" +#: ../system/translations.rst:9 +msgid "" +"Your language is in an incomplete translation state or has typos? Please " +"consider helping us in sorting this out! All you need is either a GitHub " +"account or to register directly in our instance." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.avatar(60,60)}``" +#: ../system/translations.rst:13 +msgid "" +"Did you know? This is also where the documentation translations are handled. " +"🤓" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Address" +#: ../system/translations.rst:15 +msgid "" +"Have a look in our :docs:`contribution section ` in the system documentation to get started!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.address}``" -msgstr "" +#: ../system/translations.rst:20 +#, fuzzy +msgid "Local Translations" +msgstr "Traduções" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created at" +#: ../system/translations.rst:22 +msgid "" +"Apart from these system translations, there's still local translations you " +"can manage. This is relevant if you added custom objects that require " +"translations or even custom states and priorities." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_at}``" +#: ../system/translations.rst:None +msgid "Translation management screen within the admin menu" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "2019-10-07 16:25:00 UTC" -msgstr "" +#: ../system/translations.rst:31 +#, fuzzy +msgid "Updating Translations" +msgstr "Traduções" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Closing time" +#: ../system/translations.rst:33 +msgid "" +"Because of how Zammad ships translations, the only way to update the system " +"translations is to update your Zammad installation. The benefit of this is " +"that you no longer need internet access during a Zammad upgrade as the " +"package has everything it requires already." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.close_at}``" +#: ../system/translations.rst:39 +msgid "Translation of Custom Objects" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "2019-10-07 17:25:00 UTC" +#: ../system/translations.rst:41 +msgid "" +"No problem at all! You can customize any translation locally, even if it is " +"not initially provided by the system." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``3``, any number of articles existing in the ticket right now" +#: ../system/translations.rst:44 +msgid "" +"Translation is supported for a broad number of features, including but not " +"limited to custom:" msgstr "" -#: ../system/version.rst:2 -msgid "Version" -msgstr "Versão" +#: ../system/translations.rst:47 +#, fuzzy +msgid "Object Attributes" +msgstr "Atributos do ticket" -#: ../system/version.rst:4 -msgid "Shows which version is currently being used on your Zammad-instance." -msgstr "" -"Mostra que versão está sendo atualmente utilizada pela sua instância do " -"Zammad." +#: ../system/translations.rst:48 +#, fuzzy +msgid "Ticket Macros" +msgstr "Criar uma macro global" -#: ../manage/roles/admin-permissions.rst:53 -msgid "``admin.checklist``" -msgstr "" +#: ../system/translations.rst:49 +#, fuzzy +msgid "Ticket Overviews" +msgstr "Atributos do ticket" -#: ../manage/roles/admin-permissions.rst:54 -msgid ":doc:`Manage > Checklist `" -msgstr "" +#: ../system/translations.rst:50 +#, fuzzy +msgid "Ticket Priorities" +msgstr "Prioridade" -#: ../manage/roles/admin-permissions.rst:83 -msgid "``admin.channel_whatsapp``" -msgstr "" +#: ../system/translations.rst:51 +#, fuzzy +msgid "Ticket States" +msgstr "Atributos do ticket" -#: ../manage/roles/admin-permissions.rst:84 -msgid ":doc:`Channels > Whatsapp `" -msgstr "" +#: ../system/translations.rst:54 +#, fuzzy +msgid "Customizing Translations" +msgstr "Traduções" -#: ../manage/roles/admin-permissions.rst:124 -msgid "``admin.public_links``" +#: ../system/translations.rst:56 +msgid "" +"Within the translation screen, simply click on the **New Translation** " +"button." msgstr "" -#: ../manage/roles/admin-permissions.rst:125 -msgid ":doc:`Manage > Public Links `" -msgstr "" +#: ../system/translations.rst:None +#, fuzzy +msgid "New translation dialog" +msgstr "Caixa de diálogo Nova conta de e-mail" -#: ../manage/roles/admin-permissions.rst:151 -msgid "``admin.system_report``" +#: ../system/translations.rst:62 +msgid "" +"In the dialog you can immediately enter the exact translation source (if you " +"know it) and your custom translation text for it and click **Submit**." msgstr "" -#: ../manage/roles/admin-permissions.rst:152 -msgid ":doc:`System > System Report `" +#: ../system/translations.rst:65 +msgid "" +"Alternatively, try to search for translation suggestions in the list below. " +"Selecting an item from the list will pre-fill the translation source for you " +"and then you can just enter your custom translation." msgstr "" -#: ../manage/roles/admin-permissions.rst:166 -msgid "``admin.ticket_auto_assignment``" +#: ../system/translations.rst:69 +msgid "" +"The target language will always default to your current language selection. " +"If you need to translate for a different language, simply change the " +"selection before submitting." msgstr "" -#: ../manage/roles/admin-permissions.rst:167 -msgid ":ref:`Settings > Ticket > Auto Assignment `" +#: ../system/translations.rst:73 +msgid "" +"All your custom translations will show up in the overview table when added. " +"And they will even persist across Zammad updates!" msgstr "" -#: ../manage/roles/admin-permissions.rst:169 -msgid "``admin.ticket_duplicate_detection``" +#: ../system/translations.rst:76 +msgid "" +"Make sure to reload your browser if a translated string is not displayed." msgstr "" -#: ../manage/roles/admin-permissions.rst:170 -msgid ":ref:`Settings > Ticket > Duplicate Detection `" +#: ../system/translations.rst:80 +msgid "Reverting to Original Translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:172 -#, fuzzy -msgid "``admin.ticket_priority``" -msgstr "Prioridade" - -#: ../manage/roles/admin-permissions.rst:173 -msgid ":ref:`System > Objects >Ticket Priority `" +#: ../system/translations.rst:82 +msgid "" +"If you want to revert a custom translation to original text, simply use the " +"appropriate action within the row of the overview table." msgstr "" -#: ../manage/roles/admin-permissions.rst:175 -#, fuzzy -msgid "``admin.ticket_state``" -msgstr "Atributos do ticket" +#: ../system/translations.rst:85 +msgid "" +"Depending on the type of the translation source, the action has a slightly " +"different name:" +msgstr "" -#: ../manage/roles/admin-permissions.rst:176 -msgid ":ref:`System > Objects >Ticket State `" +#: ../system/translations.rst:88 +msgid "**Reset** for customized system translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:193 -msgid "``admin.webhook``" +#: ../system/translations.rst:89 +msgid "**Remove** for customized local translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:194 -msgid ":doc:`Manage > Webhook `" +#: ../system/translations.rst:91 +msgid "" +"In both cases, the action will remove the customized translation after a " +"confirmation." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:43 -msgid "``user_preferences.appearance``" +#: ../system/translations.rst:None +msgid "Screenshot showing the location of the Remove action" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:44 +#: ../system/translations.rst:99 #, fuzzy -msgid "Appearance configuration" -msgstr "Configuração" +msgid "Inline Translations" +msgstr "Traduções" -#: ../manage/roles/user-preferences-permissions.rst:0 -msgid "Users can switch between dark, light and" +#: ../system/translations.rst:101 +msgid "" +"If you prefer a more hands-on approach, you can activate the inline or on-" +"screen translation feature by pressing ``ctrl`` + ``alt`` + ``t`` at any " +"time and on any screen." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:0 -msgid "automatic mode." +#: ../system/translations.rst:105 +msgid "" +"All customizable translation texts will be highlighted for you on the " +"screen. Just click into the highlighted area and update the text in place." msgstr "" -#: ../system/system-report.rst:2 -#, fuzzy -msgid "System Report" -msgstr "Sistema" +#: ../system/translations.rst:None +msgid "Inline translation mode activated for the Overview screen" +msgstr "" -#: ../system/system-report.rst:4 +#: ../system/translations.rst:112 msgid "" -"In this place you can't configure Zammad. Instead you can obtain a system " -"report about Zammad and its configuration." +"When finished editing, simply press ``ctrl`` + ``alt`` + ``t`` again to " +"deactivate." msgstr "" -#: ../system/system-report.rst:7 +#: ../system/translations.rst:117 msgid "" -"See the description in Zammad for an explanation. You can even find a " -"preview of the included data below the **Download** button." +"Even though it's available on any screen, the inline translation feature " +"requires admin permissions. It works only for the current language " +"selection. If you need to translate a different language, first change the " +"language in your :user-docs:`profile settings `." msgstr "" -#: ../system/system-report.rst:10 -msgid "" -"Zammad never sends this automatically to anyone. It is a manual process only " -"to provide better support based on your configuration." +#: ../system/version.rst:2 +msgid "Version" +msgstr "Versão" + +#: ../system/version.rst:4 +msgid "Shows which version is currently being used on your Zammad-instance." msgstr "" +"Mostra que versão está sendo atualmente utilizada pela sua instância do " +"Zammad." #, fuzzy #~ msgid "**Configure Zammad as Facebook app**" diff --git a/locale/ru/LC_MESSAGES/admin-docs.po b/locale/ru/LC_MESSAGES/admin-docs.po index ca85936d..b66ebd19 100644 --- a/locale/ru/LC_MESSAGES/admin-docs.po +++ b/locale/ru/LC_MESSAGES/admin-docs.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Zammad\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-11-06 10:31+0100\n" +"POT-Creation-Date: 2024-11-12 16:31+0100\n" "PO-Revision-Date: 2024-10-16 13:00+0000\n" "Last-Translator: Nikita \n" "Language-Team: Russian Checklist `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:56 msgid "``admin.channel_email``" msgstr "" -#: ../manage/roles/admin-permissions.rst:54 #: ../manage/roles/admin-permissions.rst:57 msgid ":doc:`Channels > Email `" msgstr "" -#: ../manage/roles/admin-permissions.rst:56 #: ../manage/roles/admin-permissions.rst:59 msgid "``admin.channel_facebook``" msgstr "" -#: ../manage/roles/admin-permissions.rst:57 #: ../manage/roles/admin-permissions.rst:60 msgid ":doc:`Channels > Facebook `" msgstr "" -#: ../manage/roles/admin-permissions.rst:58 #: ../manage/roles/admin-permissions.rst:61 msgid "" "Accessing Facebook tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:59 #: ../manage/roles/admin-permissions.rst:62 msgid "``admin.channel_formular``" msgstr "" -#: ../manage/roles/admin-permissions.rst:60 #: ../manage/roles/admin-permissions.rst:63 msgid ":doc:`Channels > Form `" msgstr "" -#: ../manage/roles/admin-permissions.rst:62 #: ../manage/roles/admin-permissions.rst:65 msgid "``admin.channel_google``" msgstr "" -#: ../manage/roles/admin-permissions.rst:63 #: ../manage/roles/admin-permissions.rst:66 msgid ":doc:`Channels > Google `" msgstr "" -#: ../manage/roles/admin-permissions.rst:65 #: ../manage/roles/admin-permissions.rst:68 msgid "``admin.channel_microsoft365``" msgstr "" -#: ../manage/roles/admin-permissions.rst:66 #: ../manage/roles/admin-permissions.rst:69 msgid ":doc:`Channels > Microsoft 365 `" msgstr "" -#: ../manage/roles/admin-permissions.rst:68 #: ../manage/roles/admin-permissions.rst:71 msgid "``admin.channel_sms``" msgstr "" -#: ../manage/roles/admin-permissions.rst:69 #: ../manage/roles/admin-permissions.rst:72 msgid ":doc:`Channels > SMS `" msgstr "" -#: ../manage/roles/admin-permissions.rst:71 #: ../manage/roles/admin-permissions.rst:74 msgid "``admin.channel_telegram``" msgstr "" -#: ../manage/roles/admin-permissions.rst:72 #: ../manage/roles/admin-permissions.rst:75 msgid ":doc:`Channels > Telegram `" msgstr "" -#: ../manage/roles/admin-permissions.rst:73 #: ../manage/roles/admin-permissions.rst:76 msgid "" "Accessing Telegram tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:74 #: ../manage/roles/admin-permissions.rst:77 msgid "``admin.channel_twitter``" msgstr "" -#: ../manage/roles/admin-permissions.rst:75 #: ../manage/roles/admin-permissions.rst:78 msgid ":doc:`Channels > Twitter `" msgstr "" -#: ../manage/roles/admin-permissions.rst:76 #: ../manage/roles/admin-permissions.rst:79 msgid "" "Accessing Twitter/X tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:77 #: ../manage/roles/admin-permissions.rst:80 msgid "``admin.channel_web``" msgstr "" -#: ../manage/roles/admin-permissions.rst:78 #: ../manage/roles/admin-permissions.rst:81 msgid ":doc:`Channels > Web `" msgstr "" -#: ../manage/roles/admin-permissions.rst:80 +#: ../manage/roles/admin-permissions.rst:83 +msgid "``admin.channel_whatsapp``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:84 +msgid ":doc:`Channels > Whatsapp `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:86 msgid "``admin.core_workflows``" msgstr "" -#: ../manage/roles/admin-permissions.rst:81 #: ../manage/roles/admin-permissions.rst:87 msgid ":doc:`System > Core Workflows `" msgstr "" -#: ../manage/roles/admin-permissions.rst:83 #: ../manage/roles/admin-permissions.rst:89 msgid "``admin.data_privacy``" msgstr "" -#: ../manage/roles/admin-permissions.rst:84 #: ../manage/roles/admin-permissions.rst:90 msgid ":doc:`System > Data Privacy `" msgstr "" -#: ../manage/roles/admin-permissions.rst:85 #: ../manage/roles/admin-permissions.rst:91 msgid "" "🔥 Be careful, it allows users to permanently delete data on the system." msgstr "" -#: ../manage/roles/admin-permissions.rst:86 #: ../manage/roles/admin-permissions.rst:92 msgid "``admin.group``" msgstr "" -#: ../manage/roles/admin-permissions.rst:87 #: ../manage/roles/admin-permissions.rst:93 msgid ":doc:`Manage > Groups `" msgstr "" -#: ../manage/roles/admin-permissions.rst:89 #: ../manage/roles/admin-permissions.rst:95 msgid "``admin.integration``" msgstr "" -#: ../manage/roles/admin-permissions.rst:90 #: ../manage/roles/admin-permissions.rst:96 msgid ":doc:`System > Integrations `" msgstr "" -#: ../manage/roles/admin-permissions.rst:92 #: ../manage/roles/admin-permissions.rst:98 msgid "``admin.knowledge_base``" msgstr "" -#: ../manage/roles/admin-permissions.rst:93 #: ../manage/roles/admin-permissions.rst:99 msgid ":doc:`Manage > Knowledge Base `" msgstr "" @@ -8568,57 +8551,46 @@ msgid "" "knowledge-base.html#editing-answers>`." msgstr "" -#: ../manage/roles/admin-permissions.rst:98 #: ../manage/roles/admin-permissions.rst:104 msgid "``admin.macro``" msgstr "" -#: ../manage/roles/admin-permissions.rst:99 #: ../manage/roles/admin-permissions.rst:105 msgid ":doc:`Manage > Macros `" msgstr "" -#: ../manage/roles/admin-permissions.rst:100 #: ../manage/roles/admin-permissions.rst:106 msgid "In some cases, macros may also require ``admin.tag``" msgstr "" -#: ../manage/roles/admin-permissions.rst:101 #: ../manage/roles/admin-permissions.rst:107 msgid "``admin.maintenance``" msgstr "" -#: ../manage/roles/admin-permissions.rst:102 #: ../manage/roles/admin-permissions.rst:108 msgid ":doc:`System > Maintenance `" msgstr "" -#: ../manage/roles/admin-permissions.rst:104 #: ../manage/roles/admin-permissions.rst:110 msgid "``admin.monitoring``" msgstr "" -#: ../manage/roles/admin-permissions.rst:105 #: ../manage/roles/admin-permissions.rst:111 msgid ":doc:`System > Monitoring `" msgstr "" -#: ../manage/roles/admin-permissions.rst:107 #: ../manage/roles/admin-permissions.rst:113 msgid "``admin.object``" msgstr "" -#: ../manage/roles/admin-permissions.rst:108 #: ../manage/roles/admin-permissions.rst:114 msgid ":doc:`System > Objects `" msgstr "" -#: ../manage/roles/admin-permissions.rst:110 #: ../manage/roles/admin-permissions.rst:116 msgid "``admin.organization``" msgstr "" -#: ../manage/roles/admin-permissions.rst:111 #: ../manage/roles/admin-permissions.rst:117 msgid ":doc:`Manage > Organizations `" msgstr "" @@ -8635,202 +8607,210 @@ msgstr "" msgid "They can even edit an organization's name, domain, and notes!" msgstr "" -#: ../manage/roles/admin-permissions.rst:115 #: ../manage/roles/admin-permissions.rst:121 msgid "``admin.overview``" msgstr "" -#: ../manage/roles/admin-permissions.rst:116 #: ../manage/roles/admin-permissions.rst:122 msgid ":doc:`Manage > Overviews`" msgstr "" -#: ../manage/roles/admin-permissions.rst:118 +#: ../manage/roles/admin-permissions.rst:124 +msgid "``admin.public_links``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:125 +msgid ":doc:`Manage > Public Links `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:127 msgid "``admin.package``" msgstr "" -#: ../manage/roles/admin-permissions.rst:119 #: ../manage/roles/admin-permissions.rst:128 msgid ":doc:`System > Packages `" msgstr "" -#: ../manage/roles/admin-permissions.rst:121 #: ../manage/roles/admin-permissions.rst:130 msgid "``admin.report_profile``" msgstr "" -#: ../manage/roles/admin-permissions.rst:122 #: ../manage/roles/admin-permissions.rst:131 msgid ":doc:`Manage > Report Profiles `" msgstr "" -#: ../manage/roles/admin-permissions.rst:123 #: ../manage/roles/admin-permissions.rst:132 msgid "Access to view reports: ``report``" msgstr "" -#: ../manage/roles/admin-permissions.rst:124 #: ../manage/roles/admin-permissions.rst:133 msgid "``admin.role``" msgstr "" -#: ../manage/roles/admin-permissions.rst:125 #: ../manage/roles/admin-permissions.rst:134 msgid ":doc:`Manage > Roles `" msgstr "" -#: ../manage/roles/admin-permissions.rst:127 #: ../manage/roles/admin-permissions.rst:136 msgid "``admin.scheduler``" msgstr "" -#: ../manage/roles/admin-permissions.rst:128 #: ../manage/roles/admin-permissions.rst:137 msgid ":doc:`Manage > Scheduler `" msgstr "" -#: ../manage/roles/admin-permissions.rst:129 #: ../manage/roles/admin-permissions.rst:138 msgid "For automation on tickets" msgstr "" -#: ../manage/roles/admin-permissions.rst:130 #: ../manage/roles/admin-permissions.rst:139 msgid "``admin.security``" msgstr "" -#: ../manage/roles/admin-permissions.rst:131 #: ../manage/roles/admin-permissions.rst:140 msgid ":doc:`Settings > Security `" msgstr "" -#: ../manage/roles/admin-permissions.rst:132 #: ../manage/roles/admin-permissions.rst:141 msgid "Settings of Zammad. This also covers third party authentications." msgstr "" -#: ../manage/roles/admin-permissions.rst:133 #: ../manage/roles/admin-permissions.rst:142 msgid "``admin.session``" msgstr "" -#: ../manage/roles/admin-permissions.rst:134 #: ../manage/roles/admin-permissions.rst:143 msgid ":doc:`System > Sessions `" msgstr "" -#: ../manage/roles/admin-permissions.rst:136 #: ../manage/roles/admin-permissions.rst:145 msgid "``admin.setting_system``" msgstr "" -#: ../manage/roles/admin-permissions.rst:137 #: ../manage/roles/admin-permissions.rst:146 msgid ":doc:`Settings > System `" msgstr "" -#: ../manage/roles/admin-permissions.rst:139 #: ../manage/roles/admin-permissions.rst:148 msgid "``admin.sla``" msgstr "" -#: ../manage/roles/admin-permissions.rst:140 #: ../manage/roles/admin-permissions.rst:149 msgid ":doc:`Manage > SLAs `" msgstr "" -#: ../manage/roles/admin-permissions.rst:142 +#: ../manage/roles/admin-permissions.rst:151 +msgid "``admin.system_report``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:152 +msgid ":doc:`System > System Report `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:154 msgid "``admin.tag``" msgstr "" -#: ../manage/roles/admin-permissions.rst:143 #: ../manage/roles/admin-permissions.rst:155 msgid ":doc:`Manage > Tags `" msgstr "" -#: ../manage/roles/admin-permissions.rst:145 #: ../manage/roles/admin-permissions.rst:157 msgid "``admin.template``" msgstr "" -#: ../manage/roles/admin-permissions.rst:146 #: ../manage/roles/admin-permissions.rst:158 msgid ":doc:`Manage > Templates `" msgstr "" -#: ../manage/roles/admin-permissions.rst:148 #: ../manage/roles/admin-permissions.rst:160 msgid "``admin.text_module``" msgstr "" -#: ../manage/roles/admin-permissions.rst:149 #: ../manage/roles/admin-permissions.rst:161 msgid ":doc:`Manage > Text Modules `" msgstr "" -#: ../manage/roles/admin-permissions.rst:151 #: ../manage/roles/admin-permissions.rst:163 msgid "``admin.ticket``" msgstr "" -#: ../manage/roles/admin-permissions.rst:152 #: ../manage/roles/admin-permissions.rst:164 msgid ":doc:`Settings > Tickets `" msgstr "" -#: ../manage/roles/admin-permissions.rst:153 #: ../manage/roles/admin-permissions.rst:165 msgid "Does not grant access to :doc:`/misc/composer`" msgstr "" -#: ../manage/roles/admin-permissions.rst:154 +#: ../manage/roles/admin-permissions.rst:166 +msgid "``admin.ticket_auto_assignment``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:167 +msgid ":ref:`Settings > Ticket > Auto Assignment `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:169 +msgid "``admin.ticket_duplicate_detection``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:170 +msgid ":ref:`Settings > Ticket > Duplicate Detection `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:172 +msgid "``admin.ticket_priority``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:173 +msgid ":ref:`System > Objects >Ticket Priority `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:175 +msgid "``admin.ticket_state``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:176 +msgid ":ref:`System > Objects >Ticket State `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:178 msgid "``admin.time_accounting``" msgstr "" -#: ../manage/roles/admin-permissions.rst:155 #: ../manage/roles/admin-permissions.rst:179 msgid ":doc:`Manage > Time Accounting `" msgstr "" -#: ../manage/roles/admin-permissions.rst:156 #: ../manage/roles/admin-permissions.rst:180 msgid "Also allows the export of timekeeping records." msgstr "" -#: ../manage/roles/admin-permissions.rst:157 #: ../manage/roles/admin-permissions.rst:181 msgid "``admin.translation``" msgstr "" -#: ../manage/roles/admin-permissions.rst:158 #: ../manage/roles/admin-permissions.rst:182 msgid ":doc:`System > Translations `" msgstr "" -#: ../manage/roles/admin-permissions.rst:159 #: ../manage/roles/admin-permissions.rst:183 msgid "Also enables inline translation" msgstr "" -#: ../manage/roles/admin-permissions.rst:160 #: ../manage/roles/admin-permissions.rst:184 msgid "``admin.trigger``" msgstr "" -#: ../manage/roles/admin-permissions.rst:161 #: ../manage/roles/admin-permissions.rst:185 msgid ":doc:`Manage > Triggers `" msgstr "" -#: ../manage/roles/admin-permissions.rst:163 #: ../manage/roles/admin-permissions.rst:187 msgid "``admin.user``" msgstr "" -#: ../manage/roles/admin-permissions.rst:164 #: ../manage/roles/admin-permissions.rst:188 msgid ":doc:`Manage > Users `" msgstr "" @@ -8849,6 +8829,14 @@ msgid "" "from-users-perspective>` ." msgstr "" +#: ../manage/roles/admin-permissions.rst:193 +msgid "``admin.webhook``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:194 +msgid ":doc:`Manage > Webhook `" +msgstr "" + #: ../manage/roles/agent-permissions.rst:2 msgid "Agent Permissions" msgstr "" @@ -9267,36 +9255,45 @@ msgid "than the user that generated them." msgstr "" #: ../manage/roles/user-preferences-permissions.rst:43 +msgid "``user_preferences.appearance``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:44 +msgid "Appearance configuration" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "Users can switch between dark, light and" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "automatic mode." +msgstr "" + #: ../manage/roles/user-preferences-permissions.rst:47 msgid "``user_preferences.avatar``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:44 #: ../manage/roles/user-preferences-permissions.rst:48 msgid "Avatar settings" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:45 #: ../manage/roles/user-preferences-permissions.rst:49 msgid "Override the default Gravatar with a custom avatar" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:46 #: ../manage/roles/user-preferences-permissions.rst:50 msgid "``user_preferences.calendar``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:47 #: ../manage/roles/user-preferences-permissions.rst:51 msgid "Configure the calendar feed" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:49 #: ../manage/roles/user-preferences-permissions.rst:53 msgid "``user_preferences.device``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:50 #: ../manage/roles/user-preferences-permissions.rst:54 msgid "Manage device login sessions" msgstr "" @@ -9313,22 +9310,18 @@ msgstr "" msgid "To learn more, see :doc:`/manage/trigger/system-notifications`." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:54 #: ../manage/roles/user-preferences-permissions.rst:58 msgid "``user_preferences.language``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:55 #: ../manage/roles/user-preferences-permissions.rst:59 msgid "Configure the UI locale/language" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:57 #: ../manage/roles/user-preferences-permissions.rst:61 msgid "``user_preferences.linked_accounts``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:58 #: ../manage/roles/user-preferences-permissions.rst:62 msgid "Account linking" msgstr "" @@ -9352,7 +9345,6 @@ msgstr "" msgid "is the only way users can utilize third-party logins." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:63 #: ../manage/roles/user-preferences-permissions.rst:67 msgid "``user_preferences.notifications``" msgstr "" @@ -9380,7 +9372,6 @@ msgstr "" msgid "Customers can't receive ticket notifications at all." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:69 #: ../manage/roles/user-preferences-permissions.rst:73 msgid "``user_preferences.out_of_office``" msgstr "" @@ -9405,7 +9396,6 @@ msgstr "" msgid "they're replacing." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:75 #: ../manage/roles/user-preferences-permissions.rst:79 msgid "``user_preferences.overview_sorting``" msgstr "" @@ -9434,12 +9424,10 @@ msgstr "" msgid "overviews has no effect on custom orders." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:82 #: ../manage/roles/user-preferences-permissions.rst:86 msgid "``user_preferences.password``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:83 #: ../manage/roles/user-preferences-permissions.rst:87 msgid "Change account password" msgstr "" @@ -9456,7 +9444,6 @@ msgstr "" msgid "your only allowed authentication method." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:87 #: ../manage/roles/user-preferences-permissions.rst:91 msgid "``user_preferences.two_factor_authentication``" msgstr "" @@ -9493,7 +9480,7 @@ msgstr "" #: ../manage/scheduler.rst:19 msgid "" -"Schedulers can be used to send periodic reminder emails. Use :doc:`/system/" +"Schedulers can be used to send periodic reminder emails. Use :doc:`/misc/" "variables` to build highly-customized email templates." msgstr "" @@ -10490,7 +10477,7 @@ msgstr "" #: ../manage/text-modules.rst:57 msgid "" -"The example text modules below use :doc:`/system/variables` to dynamically " +"The example text modules below use :doc:`/misc/variables` to dynamically " "insert information like the customer's or agent's names." msgstr "" @@ -10830,8 +10817,8 @@ msgstr "" #: ../misc/object-conditions/basics.rst:144 #: ../misc/object-conditions/basics.rst:160 #: ../misc/object-conditions/basics.rst:168 -#: ../misc/object-conditions/basics.rst:178 ../settings/ticket.rst:2 -#: ../system/variables/ticket.rst:2 +#: ../misc/object-conditions/basics.rst:178 ../misc/variables/ticket.rst:2 +#: ../settings/ticket.rst:2 msgid "Ticket" msgstr "" @@ -11065,7 +11052,7 @@ msgstr "" #: ../manage/trigger/how-do-they-work.rst:79 msgid "" -"Certain actions (such as *email*, *SMS* and *notes*) support :doc:`/system/" +"Certain actions (such as *email*, *SMS* and *notes*) support :doc:`/misc/" "variables`, which can be used to build highly-customized message templates." msgstr "" @@ -11094,7 +11081,7 @@ msgstr "" msgid "" "You can also combine static text with placeholders for text fields. Remember " "that the placeholders' values have to be known during trigger runtime. Learn " -"more about :doc:`/system/variables`." +"more about :doc:`/misc/variables`." msgstr "" #: ../manage/trigger/how-do-they-work.rst:105 @@ -12060,7 +12047,7 @@ msgstr "" msgid "" "When switched on, a code editor will be shown below, where you can configure " "custom payload for your webhook in JSON format. To insert supported :doc:`/" -"system/variables` use ``::`` or ``#{`` shortcuts for autocomplete." +"misc/variables` use ``::`` or ``#{`` shortcuts for autocomplete." msgstr "" #: ../manage/webhook/add.rst:103 @@ -14639,11949 +14626,11840 @@ msgid "" "powerful conditions with AND/OR relations." msgstr "" -#: ../settings/branding.rst:10 -msgid "Product Name" +#: ../misc/variables.rst:2 +msgid "Variables" msgstr "" -#: ../settings/branding.rst:7 +#: ../misc/variables.rst:4 msgid "" -"Defines the name of the application, shown in the web interface, tabs and " -"title bar of the web browser." +"Please note that this is just an overview of available variables. It might " +"be incomplete or variables might not be available within some functions. If " +"you're missing variables or are not sure if something is not working as " +"expected, feel free to ask over at the `Community `_." msgstr "" -#: ../settings/branding.rst:10 -msgid "Default value: ``Zammad Helpdesk``" +#: ../misc/variables.rst:10 +msgid "" +"Variables can be called by typing ``::`` (just like text modules in the " +"frontend), as long as you're in a supported text field within the backend. " +"Zammad will display all variables being available within this context and " +"replace it to the variable as soon as you selected an entry." msgstr "" -#: ../settings/branding.rst:13 -msgid "Will be shown in the app and is included in email footers." +#: ../misc/variables.rst:15 +msgid "" +"You have an empty field which you referenced and it appears as ``-``? That's " +"currently working as designed - you might want to ensure that these fields " +"always have a value." msgstr "" -#: ../settings/branding.rst:19 -msgid "Logo" +#: ../misc/variables.rst:20 +msgid "Variable Categories" msgstr "" -#: ../settings/branding.rst:16 -msgid "Defines the logo of the application, shown in the login page of Zammad." +#: ../misc/variables.rst:31 +msgid "Wait, What About Custom Objects?" msgstr "" -#: ../settings/branding.rst:18 +#: ../misc/variables.rst:33 msgid "" -"Ensure to hit the \"Submit\" button after uploading the logo. Otherwise your " -"change will not be saved." +"Good point! Of course, we can't predict what objects you might create, but " +"we can give you a hint on how to put the puzzle together to get your custom " +"values." msgstr "" -#: ../settings/branding.rst:22 +#: ../misc/variables.rst:36 msgid "" -"Allows to set the default language of the Zammad instance. The here defined " -"locale mostly acts as a fallback for:" -msgstr "" - -#: ../settings/branding.rst:25 -msgid "user preferences (if Zammad can't detect the users locale)" +"For this, we'll talk about the inner part of the variable (so everything " +"within ``#{}``), please put the outer part around to have a valid variable. " +"The first part of the variable name consist of the object type. Currently " +"these are:" msgstr "" -#: ../settings/branding.rst:26 -msgid "CSV output (reporting, time accounting)" +#: ../misc/variables.rst:41 +msgid "Ticket (``ticket``)" msgstr "" -#: ../settings/branding.rst:30 -msgid "Define the timezone of your Zammad installation." +#: ../misc/variables.rst:42 +msgid "User (``user``)" msgstr "" -#: ../settings/branding.rst:32 -msgid "" -"This does not have any effect on timings for your agents or how Zammad " -"stores date and time values." +#: ../misc/variables.rst:43 +msgid "Organization (``organization``)" msgstr "" -#: ../settings/branding.rst:35 -msgid "Changing this value has direct consequences on the following areas:" +#: ../misc/variables.rst:44 +msgid "Group (``group``)" msgstr "" -#: ../settings/branding.rst:37 -msgid ":doc:`/manage/scheduler` tasks" +#: ../misc/variables.rst:46 +msgid "" +"The second part is the name of the attribute. This is the name you define " +"during object creation and can be found within the object attribute menu at " +"any time. The first and second part of a variable is divided by a point, e." +"g.: ``ticket.number`` which will in total be ``#{ticket.number}``." msgstr "" -#: ../settings/branding.rst:38 -msgid "search indexing (and thus reporting)" +#: ../misc/variables.rst:51 +msgid "" +"Now, in some situations it's possible that you'll need to use a third part. " +"The best example for such a situation would be a ``select`` or ``tree-" +"select`` field which will by default return the key value, not it's display " +"name. For this, just extend your variable with ``.value``. This will result " +"in ``#{ticket.select.value}``." msgstr "" -#: ../settings/branding.rst:40 -msgid "calendar subscriptions" +#: ../misc/variables.rst:60 +msgid "Using Translated Variables" msgstr "" -#: ../settings/branding.rst:41 -msgid "browser printing" +#: ../misc/variables.rst:62 +msgid "" +"If you want to use a translated variable in triggers or schedulers, you can " +"extend the placeholder like this: ``#{t(ticket.state.name)}``. The ``t`` " +"tells Zammad to search for fitting translated strings. The used output " +"language is based on the system language of Zammad which you can set in the " +"admin panel under :doc:`/settings/branding` or based on the selected locale " +"in the trigger/scheduler edit dialog." msgstr "" -#: ../settings/branding.rst:43 +#: ../misc/variables.rst:69 msgid "" -"Please note that some of above are fallbacks in case Zammad could not detect " -"the agents timezone correctly." +"A possible use-case: you want to send your customers updates on tickets via " +"trigger or scheduler which should include the state of the ticket. Using the " +"default ``#{ticket.state.name}`` (without the translation flag ``t()``) " +"would lead to the output of the original (english) name of the state." msgstr "" -#: ../settings/branding.rst:77 -msgid "Pretty Date" +#: ../misc/variables.rst:75 +msgid "Date and Time Formatting" msgstr "" -#: ../settings/branding.rst:47 +#: ../misc/variables.rst:77 msgid "" -"This setting allows you to define how Zammad should display time stamps " -"within the interface to all users." +"The system (trigger/scheduler selected) locale and timezone predefines a " +"default format of date and timestamp. This format is customizable by using " +"the ``dt()`` method." msgstr "" -#: ../settings/branding.rst:50 -msgid "" -"This does not have any effect on how Zammad returns e.g. time values via " -"variables." +#: ../misc/variables.rst:79 +msgid "The method arguments are as follows:" msgstr "" -#: ../settings/branding.rst:77 -msgid "Choose in between the following options:" +#: ../misc/variables.rst:81 +msgid "The date or timestamp variable you want to format." msgstr "" -#: ../settings/branding.rst:64 -msgid "relative" +#: ../misc/variables.rst:82 +msgid "The output format string." msgstr "" -#: ../settings/branding.rst:55 -msgid "" -"This timestamp shows a relative time span until it switches to a date. Over " -"time, it will change as follows:" +#: ../misc/variables.rst:83 +msgid "The timezone to apply (optional)." msgstr "" -#: ../settings/branding.rst:58 -msgid "just now" +#: ../misc/variables.rst:85 +#: ../system/objects/external-data-source-example.rst:23 +msgid "**Example:**" msgstr "" -#: ../settings/branding.rst:59 -msgid "5 minutes ago" +#: ../misc/variables.rst:86 +msgid "" +"``#{dt(ticket.updated_at, \"%A %Y-%m-%d %H:%M in the office\", \"Europe/" +"Berlin\")}``" msgstr "" -#: ../settings/branding.rst:60 -msgid "3 days 1 hour ago" +#: ../misc/variables.rst:87 +msgid "Monday, 2024-03-18 15:31 in the office" msgstr "" -#: ../settings/branding.rst:61 -msgid "``03/04/2022``" +#: ../misc/variables.rst:89 +msgid "" +"If you want to use our example, make sure to paste the string above without " +"formatting (``CTRL+Shift+v``), otherwise it won't work." msgstr "" -#: ../settings/branding.rst:63 -msgid "Hovering the timestamp helps, you'll always get a clean timestamp then." +#: ../misc/variables.rst:93 +msgid "The following table lists available format directives:" msgstr "" -#: ../settings/branding.rst:71 -msgid "absolute" +#: ../misc/variables.rst:99 +msgid "Parameter" msgstr "" -#: ../settings/branding.rst:67 -msgid "" -"This timestamp always includes the week day. For one week after creation, " -"the timestamp will not contain the date itself: Thursday 18:35." +#: ../misc/variables.rst:102 +msgid "``%Y``" msgstr "" -#: ../settings/branding.rst:71 -msgid "After a week it will switch to: ``Friday 4. Mar 16:00``." +#: ../misc/variables.rst:103 +msgid "Year with 4 digits" msgstr "" -#: ../settings/branding.rst:76 -msgid "timestamp" +#: ../misc/variables.rst:104 +msgid "Use ``%y`` for year with 2 digits" msgstr "" -#: ../settings/branding.rst:74 -msgid "" -"This will cause Zammad to show a complete timestamp according to your locale " -"defaults. For English this could be e.g. ``2022/12/03 2:40 pm`` or for " -"German e.g. ``12.03.2022 14:40``." +#: ../misc/variables.rst:105 +msgid "``%m``" msgstr "" -#: ../settings/branding.rst:78 -msgid "Default setting: ``relative``." +#: ../misc/variables.rst:106 +msgid "Month of year (as number with zero-padding)" msgstr "" -#: ../settings/security.rst:2 -msgid "Security" +#: ../misc/variables.rst:107 +msgid "Use ``%-m`` for month without zero-padding" msgstr "" -#: ../settings/security.rst:4 -msgid "" -"For your overview we split each tab within security settings into its own " -"page:" +#: ../misc/variables.rst:108 +msgid "``%d``" msgstr "" -#: ../settings/security/base.rst:2 ../settings/system/base.rst:2 -#: ../settings/ticket.rst:8 -msgid "Base" +#: ../misc/variables.rst:109 +msgid "Day of month (as number with zero-padding)" msgstr "" -#: ../settings/security/base.rst:5 -msgid "New User Accounts" +#: ../misc/variables.rst:110 +msgid "Use ``%e`` for day without zero-padding" msgstr "" -#: ../settings/security/base.rst:9 -msgid "" -"Activates the `register as a new customer` function on the login page. If " -"set to ``no`` only administrators or agents can create new accounts manually." +#: ../misc/variables.rst:111 +msgid "``%H``" msgstr "" -#: ../settings/security/base.rst:13 ../settings/security/base.rst:38 -#: ../settings/security/base.rst:66 -msgid "Default setting: ``yes``" +#: ../misc/variables.rst:112 +msgid "Hour of day in 24h notation with zero-padding" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing activated \"New User Accounts\" setting" +#: ../misc/variables.rst:113 +msgid "Use ``%k`` for hour without zero-padding" msgstr "" -#: ../settings/security/base.rst:22 -msgid "" -"Deactivation of above function **does not** deactivate automatic account " -"creation! This means: If a user writes e.g. an email to Zammad and has no " -"account yet, Zammad will automatically create the account. User accounts are " -"a direct dependency of tickets and thus technically mandatory." +#: ../misc/variables.rst:114 +msgid "``%I``" msgstr "" -#: ../settings/security/base.rst:29 -msgid "Lost Password" +#: ../misc/variables.rst:115 +msgid "Hour of day in 12h notation with zero-padding" msgstr "" -#: ../settings/security/base.rst:33 +#: ../misc/variables.rst:116 msgid "" -"Activates the `lost password` function on the login page. If set to ``no`` " -"only administrators may change the user's password - users may update their " -"own password if they're still logged in and they have the required :doc:" -"`permission `." +"Use ``%l`` for hour without zero-padding and ``%p`` / ``%P`` for meridian " +"indicator" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing activated \"Lost Password\" setting" +#: ../misc/variables.rst:117 +msgid "``%M``" msgstr "" -#: ../settings/security/base.rst:49 -msgid "" -"With third party authentications - but especially LDAP - you may want to " -"disable this function. Zammad **will not** change third party login " -"passwords and instead set or change the local password!" +#: ../misc/variables.rst:118 +msgid "Minute of hour" msgstr "" -#: ../settings/security/base.rst:56 -msgid "Password Login" +#: ../misc/variables.rst:120 +msgid "``%S``" msgstr "" -#: ../settings/security/base.rst:60 -msgid "" -"Activates the username & password login by default and if no third-party " -"login is activated. Disabling password login on the Zammad login page only " -"takes effect if you enable any :doc:`third-party`." +#: ../misc/variables.rst:121 +msgid "Second of Minute" msgstr "" -#: ../settings/security/base.rst:64 -msgid "See :doc:`third-party` for supported third-party logins." +#: ../misc/variables.rst:123 +msgid "``%A``" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing de-activated \"Password Login\" setting" +#: ../misc/variables.rst:124 +msgid "Weekday name" msgstr "" -#: ../settings/security/base.rst:77 -msgid "" -"To help administrators to overcome \"login issues\", Zammad automatically " -"offers a password request for administrator users. This allows you to adjust " -"Third-Party applications even if the login does no longer work!" +#: ../misc/variables.rst:125 +msgid "Use ``%a`` for abbreviated name or ``%^A`` for uppercase name" msgstr "" -#: ../settings/security/base.rst:84 -msgid "Session Timeout" +#: ../misc/variables.rst:126 +msgid "``%B``" msgstr "" -#: ../settings/security/base.rst:86 -msgid "" -"All settings below by default are set to ``4 weeks``. Session Timeout " -"defines the life time of a users session. As soon as it's reached, Zammad " -"will automatically log off the session in question." +#: ../misc/variables.rst:127 +msgid "Month name" msgstr "" -#: ../settings/security/base.rst:91 -msgid "" -"Zammad takes the highest value set assigned for the user based on the " -"permissions." +#: ../misc/variables.rst:128 +msgid "Use ``%b`` for abbreviated name" msgstr "" -#: ../settings/security/base.rst:94 -msgid "``admin``" +#: ../misc/variables.rst:129 +msgid "``%U``" msgstr "" -#: ../settings/security/base.rst:96 -msgid "``ticket.customer``" +#: ../misc/variables.rst:130 +msgid "Week number of current year" msgstr "" -#: ../settings/security/base.rst:97 -msgid "``default`` (fallback if user doesn't have above permissions set)" +#: ../misc/variables.rst:131 +msgid "Use ``%W`` for a different calculation method" msgstr "" -#: ../settings/security/base.rst:99 +#: ../misc/variables.rst:134 msgid "" -"All settings act independently from each other allowing you to disable the " -"timeouts for e.g. admins, but not agents." +"We support the known format directives for the Ruby built-in method " +"``strftime`` of the ``DateTime`` class. For more information, see `here " +"`_." msgstr "" -#: ../settings/security/base.rst:115 -#: ../system/integrations/checkmk/api-reference.rst:13 -msgid "Example" -msgstr "Пример" +#: ../misc/variables/article.rst:2 +msgid "Articles" +msgstr "" -#: ../settings/security/base.rst:107 -msgid "Let's suppose you configured the following session timeouts" +#: ../misc/variables/article.rst:4 ../misc/variables/config.rst:4 +#: ../misc/variables/current-user.rst:4 ../misc/variables/ticket.rst:4 +msgid "" +"If you're missing variables or are not sure if something is not working as " +"expected, feel free to ask over at the `Community `_." msgstr "" -#: ../settings/security/base.rst:104 -msgid "default: 3 weeks" +#: ../misc/variables/article.rst:6 +msgid "" +"Below you can find all available ticket article-based variables within " +"Zammad. These can be called via triggers for example. If you're unsure if " +"Zammad does support variables at the point you're at, you can try to type " +"``::`` to check." msgstr "" -#: ../settings/security/base.rst:105 -msgid "admin: 2 weeks" +#: ../misc/variables/article.rst:9 ../misc/variables/config.rst:9 +#: ../misc/variables/ticket.rst:9 +msgid "" +"The below list gives you an example what kind of data you can expect, it's " +"not intended to explain the data itself." msgstr "" -#: ../settings/security/base.rst:106 -msgid "ticket.agent: 4 weeks" +#: ../misc/variables/article.rst:11 +msgid "Article Variables" msgstr "" -#: ../settings/security/base.rst:107 -msgid "ticket.customer: 1 week" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "name" msgstr "" -#: ../settings/security/base.rst:115 -msgid "This results in the following situations" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "variable" msgstr "" -#: ../settings/security/base.rst:110 -msgid "a user with ``admin`` permission will have a timeout of 2 weeks" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "example" msgstr "" -#: ../settings/security/base.rst:111 -msgid "" -"a user with ``admin`` and ``ticket.agent`` permissions will have a timeout " -"of 2 weeks" +#: ../misc/variables/article.rst:1 +msgid "Article > Cc" msgstr "" -#: ../settings/security/base.rst:113 -msgid "" -"a user with ``ticket.customer`` permission will have a timeout of 1 week" +#: ../misc/variables/article.rst:1 +msgid "``#{article.cc}``" msgstr "" -#: ../settings/security/base.rst:115 -msgid "" -"a user with neither ``admin``, ``ticket.agent`` nor ``ticket.customer`` " -"permissions will have a timeout of 3 weeks" +#: ../misc/variables/article.rst:1 +msgid "``jdoe@example.com, company@example.com``" msgstr "" -#: ../settings/security/password.rst:4 -msgid "" -"This section allows you to define password requirements for the local user " -"accounts." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Address" msgstr "" -#: ../settings/security/password.rst:9 -msgid "" -"Zammad does **not** allow you to change your LDAP password, instead, it will " -"set a password in its local database which might confuse your users. This " -"might be addressed in the future by `#1169 `_." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.address}``" msgstr "" -#: ../settings/security/password.rst:14 -msgid "**Exception for admins**" +#: ../misc/variables/article.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:16 -msgid "" -"Please note that below password policies *do not* affect administrators " -"setting passwords on user accounts. While this seems strange and not safe we " -"believe that an administrator knowing an user's password is insecure as well." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Department" msgstr "" -#: ../settings/security/password.rst:21 -msgid "The suggested workflow is either:" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.department}``" msgstr "" -#: ../settings/security/password.rst:23 -msgid "" -"to use third party logins to not require local passwords at all **- or -**" +#: ../misc/variables/article.rst:1 +msgid "``Sales`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:25 -msgid "to require your *user to reset the password* upon first login." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Email" msgstr "" -#: ../settings/security/password.rst:27 -msgid "" -"This way administrators are not required to set a user's password at all!" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.email}``" msgstr "" -#: ../settings/security/password.rst:31 -msgid "Maximum Failed Logins" +#: ../misc/variables/article.rst:1 +msgid "``jdoe@example.com``" msgstr "" -#: ../settings/security/password.rst:33 -msgid "" -"You can choose a value between ``4`` and ``20``. This defines how often a " -"login to a user account may fail until Zammad will lock it. Your users can " -"always use the \"forgot password\" function to change their password and " -"unlock their account." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Fax" msgstr "" -#: ../settings/security/password.rst:38 -msgid "The default value is ``10``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.fax}``" msgstr "" -#: ../settings/security/password.rst:42 -msgid "Beside changing the user's password, you can also unlock accounts via" +#: ../misc/variables/article.rst:1 +msgid "``+4930123456789`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:44 -msgid ":ref:`user management list `" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Firstname" msgstr "" -#: ../settings/security/password.rst:45 -msgid ":docs:`console `" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.firstname}``" msgstr "" -#: ../settings/security/password.rst:46 -msgid ":docs:`API `" +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Joe`` or empty if not set" msgstr "" -#: ../settings/security/password.rst:50 -msgid "Failed logins via LDAP no longer lock accounts." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Lastname" msgstr "" -#: ../settings/security/password.rst:53 -msgid "2 Lower Case And 2 Upper Case Characters" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.lastname}``" msgstr "" -#: ../settings/security/password.rst:55 -msgid "" -"You can add complexity to passwords by enforcing at least 2 upper and lower " -"case characters." +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +#: ../misc/variables/ticket.rst:1 +msgid "``Doe`` or empty if not set" msgstr "" -#: ../settings/security/password.rst:58 ../settings/security/password.rst:83 -msgid "The default value is ``no``." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Login" msgstr "" -#: ../settings/security/password.rst:62 -msgid "Minimum Length" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.login}``" msgstr "" -#: ../settings/security/password.rst:64 -msgid "" -"This defines the minimum password length required for users to provide (from " -"``4`` to ``20``)." +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +#: ../misc/variables/ticket.rst:1 +msgid "``jdoe``" msgstr "" -#: ../settings/security/password.rst:67 -msgid "The default value is ``6``." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Mobile" msgstr "" -#: ../settings/security/password.rst:71 -msgid "Digit Required" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.mobile}``" msgstr "" -#: ../settings/security/password.rst:73 -msgid "This enforces your users to use at least one digit within the password." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Note" msgstr "" -#: ../settings/security/password.rst:75 -msgid "The default value is ``yes``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.note}``" msgstr "" -#: ../settings/security/password.rst:78 -msgid "Special Character Required" +#: ../misc/variables/article.rst:1 +msgid "``Some note about user`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:80 -msgid "" -"This setting allows you to improve your password quality even more by " -"enforcing the password to contain at least one special character." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Phone" msgstr "" -#: ../settings/security/ssl-certificates.rst:2 -msgid "SSL Certificates" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.phone}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:7 -msgid "" -"Zammad offers the possibility to upload custom certificates and custom " -"Certificate Authority (CA) certificates. This can be useful if you want to " -"connect Zammad the secure way to other systems which are using custom " -"certificates." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > VIP" msgstr "" -#: ../settings/security/ssl-certificates.rst:12 -msgid "" -"An example usecase might be: You have an internal LDAP server that is not " -"accessible from the internet, and you want a SSL-encrypted connection, using " -"a custom certificate." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.vip}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:19 -msgid "" -"You should have an existing custom certificate file and/or a custom CA " -"certificate file, which you want to add to Zammad. As filetype ``.crt`` is " -"supported and the certificate format has to be PEM (Base64 ASCII)." +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +msgid "``true`` or ``false``" msgstr "" -#: ../settings/security/ssl-certificates.rst:25 -msgid "" -"When you import a custom CA certificate, all certificates generated with " -"this are trusted. This can be useful if you have more than one system/" -"certificate you want to connect to and the certificates are issued from the " -"same custom CA." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Web" msgstr "" -#: ../settings/security/ssl-certificates.rst:31 -msgid "Add a Certificate" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.web}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:33 -msgid "" -"To add a custom certificate or a custom CA certificate, head over to the " -"Admin panel > Settings > Security > SSL Certificates. Here you can find a " -"\"Add SSL Certificate\" button. In the dialog you can either select a " -"certificate file or paste the content of the certificate:" +#: ../misc/variables/article.rst:1 +msgid "``https://zammad.com`` or empty if not set in user object" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate adding dialog" +#: ../misc/variables/article.rst:1 +msgid "Article > Created" msgstr "" -#: ../settings/security/ssl-certificates.rst:43 -msgid "" -"After selecting a file or pasting the content of the certificate, click on " -"the \"Add\" button to finally upload it to Zammad. Then, the certificates " -"are immediately effective, no restart or similar required." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_at}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:49 -msgid "" -"Please note that only single certificate files are supported. That means if " -"you want to import a certificate / CA certificate, it must contain **only " -"one** certificate." +#: ../misc/variables/article.rst:1 +msgid "``2019-10-08 15:24:47 UTC``" msgstr "" -#: ../settings/security/ssl-certificates.rst:54 -msgid "Certificate Overview" +#: ../misc/variables/article.rst:1 +msgid "Article > From" msgstr "" -#: ../settings/security/ssl-certificates.rst:56 +#: ../misc/variables/article.rst:1 +msgid "``#{article.from}``" +msgstr "" + +#: ../misc/variables/article.rst:1 msgid "" -"After you added a certificate, you can see a table with information for each " -"added certificate:" +"``Joe Doe `` may differ, depends on ``FROM`` of send mail" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing table of added certificates" +#: ../misc/variables/article.rst:1 +msgid "Article > Sender > Name" msgstr "" -#: ../settings/security/ssl-certificates.rst:64 -msgid "" -"Here you can download the certificate or delete it, if you don't need it " -"anymore." +#: ../misc/variables/article.rst:1 +msgid "``#{article.sender.name}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:68 -msgid "Deleting Certificates" +#: ../misc/variables/article.rst:1 +msgid "``Customer``, ``Agent`` or ``System``" msgstr "" -#: ../settings/security/ssl-certificates.rst:70 -msgid "" -"If you want to delete a specific certificate, you can do it by clicking on " -"the menu in the actions column and selecting delete:" +#: ../misc/variables/article.rst:1 +msgid "Article > Subject" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate deletion button" +#: ../misc/variables/article.rst:1 +msgid "``#{article.subject}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:79 -msgid "Downloading Certificates" +#: ../misc/variables/article.rst:1 +msgid "``My amazing subject``" msgstr "" -#: ../settings/security/ssl-certificates.rst:81 -msgid "" -"If you want to download your certificates, you can do this as well via " -"corresponding action buttons." +#: ../misc/variables/article.rst:1 +msgid "Article > Text" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate download button" +#: ../misc/variables/article.rst:1 +msgid "``#{article.body}``" msgstr "" -#: ../settings/security/third-party.rst:13 -msgid "Login Providers" +#: ../misc/variables/article.rst:1 +msgid "``Test`` without formatting (plain)" msgstr "" -#: ../settings/security/third-party.rst:2 -msgid "Third-Party Applications" +#: ../misc/variables/article.rst:1 +msgid "Article > TicketID" msgstr "" -#: ../settings/security/third-party.rst:4 -msgid "" -"Third party authentication is a great way to help your users to login to " -"Zammad more easily. If the account is yet unknown, Zammad will create a new " -"user automatically, without the user needed to interact (e.g. type in his " -"name). Another big advantage of this feature is that your user doesn't need " -"to remember another password." +#: ../misc/variables/article.rst:1 +msgid "``#{article.ticket_id}``" msgstr "" -#: ../settings/security/third-party.rst:10 -msgid "" -"You can deactivate logging in via :ref:`security_password_login` if any of " -"the mentioned authentication providers are enabled in your instance." +#: ../misc/variables/article.rst:1 +msgid "``1`` (not ticket number)" msgstr "" -#: ../settings/security/third-party.rst:27 -msgid "" -"We're currently missing documentation for the following login providers:" +#: ../misc/variables/article.rst:1 +msgid "Article > To" msgstr "" -#: ../settings/security/third-party.rst:29 -msgid "LinkedIn" +#: ../misc/variables/article.rst:1 +msgid "``#{article.to}``" msgstr "" -#: ../settings/security/third-party.rst:30 -msgid "Weibo" +#: ../misc/variables/article.rst:1 +msgid "``helpdesk@example.com``" msgstr "" -#: ../settings/security/third-party.rst:35 -msgid "Automatic Account Link on Initial Logon" +#: ../misc/variables/article.rst:1 +msgid "Article > Type > Name" msgstr "" -#: ../settings/security/third-party.rst:37 -msgid "" -"In general there's two possible options for Zammad on how to deal with " -"already known users as they try to authenticate against a third-party " -"application. By default, Zammad will not automatically link \"unknown\" " -"authentication providers to existing accounts." +#: ../misc/variables/article.rst:1 +msgid "``#{article.type.name}``" msgstr "" -#: ../settings/security/third-party.rst:42 +#: ../misc/variables/article.rst:1 msgid "" -"This means that the user has to manually link authentication providers to " -"their accounts (for more about this :user-docs:`consult the user " -"documentation `)." +"``email`` (`list of article types `_)" msgstr "" -#: ../settings/security/third-party.rst:46 -msgid "" -"Sometimes this doesn't come in handy as this also means you'll receive error " -"messages about \"email address being in use already\" for (yet) unknown " -"third-party authentication methods." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Address" msgstr "" -#: ../settings/security/third-party.rst:50 -msgid "" -"If you want to allow your users to always be able to log in, no matter what, " -"you may want to enable ``Automatic account link on initial logon``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.address}``" msgstr "" -#: ../settings/security/third-party.rst:None -msgid "" -"Screenshot highlighting the \"Automatic account link on initial logon\"\n" -"setting" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Department" msgstr "" -#: ../settings/security/third-party.rst:60 -msgid "Automatic Account Linking Notification" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.department}``" msgstr "" -#: ../settings/security/third-party.rst:64 -msgid "" -"To improve security and your users awareness, you can enable Zammad to " -"notify your users when a new third-party application has been linked to " -"their account." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Email" msgstr "" -#: ../settings/security/third-party.rst:68 -msgid "" -"This notification is sent out once per third-party application. Zammad does " -"also mention the method used, e.g.: ``Microsoft``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.email}``" msgstr "" -#: ../settings/security/third-party.rst:71 -msgid "By default this setting is not active (set to ``no``)." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Fax" msgstr "" -#: ../settings/security/third-party.rst:0 -msgid "" -"Screenshot showing sample notification mail after initial\n" -"third-party linking" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.fax}``" msgstr "" -#: ../settings/security/third-party.rst:85 -msgid "" -"This notification is only sent if the account in question already exists. If " -"the login via the third-party also creates the missing account, the " -"notification will be skipped." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Firstname" msgstr "" -#: ../settings/security/third-party.rst:89 -msgid "This means it only affects:" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.firstname}``" msgstr "" -#: ../settings/security/third-party.rst:91 -msgid "manual account linking within the third-party page of the users profile" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Lastname" msgstr "" -#: ../settings/security/third-party.rst:92 -msgid "" -"logging into an existing local account by utilizing the *automatic account " -"link on initial logon* functionality" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.lastname}``" msgstr "" -#: ../settings/security/third-party.rst:None -msgid "" -"Screenshot showing the \"automatic account linking notification\"\n" -"setting" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Login" msgstr "" -#: ../settings/security/third-party.rst:100 -msgid "No User Creation on Logon" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.login}``" msgstr "" -#: ../settings/security/third-party.rst:102 -msgid "" -"By default, Zammad will create a new user account if the user logs in via a " -"third-party application and the account doesn't exist yet." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Mobile" msgstr "" -#: ../settings/security/third-party.rst:105 -msgid "" -"If you want to prevent Zammad from creating new accounts on logon, you can " -"disable this feature by setting ``No user creation on logon`` to ``yes``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.mobile}``" msgstr "" -#: ../settings/security/third-party.rst:None -msgid "Screenshot showing the \"no user creation on logon\" setting" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Note" msgstr "" -#: ../settings/security/third-party/facebook.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via Facebook To do " -"so, you need to follow these steps:" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.note}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:9 -msgid "Register Facebook App" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Phone" msgstr "" -#: ../settings/security/third-party/facebook.rst:11 -msgid "" -"Visit [https://developers.facebook.com/apps/] and click on \"Add a new App\"" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.phone}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "initial page" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > VIP" msgstr "" -#: ../settings/security/third-party/facebook.rst:17 -msgid "After that enter the app settings" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.vip}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "Create App" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Web" msgstr "" -#: ../settings/security/third-party/facebook.rst:22 -msgid "Navigate to \"Settings\" and fill in this infromation" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.web}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "App Settings" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated" msgstr "" -#: ../settings/security/third-party/facebook.rst:27 -msgid "Navigate to app review and Check \"Make [appname] public?\"" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_at}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "App Review" +#: ../misc/variables/article.rst:1 +msgid "Article > Visibility" msgstr "" -#: ../settings/security/third-party/facebook.rst:35 -msgid "Configure Zammad as Facebook App" +#: ../misc/variables/article.rst:1 +msgid "``#{article.internal}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:37 -msgid "" -"Navigate to \"Admin -> Security -> Third Party Applications\" and enter the " -"App ID and the App Secret. You can find this Key in the Dashbard of your " -"Facebok app." +#: ../misc/variables/article.rst:1 +msgid "``false`` or ``true`` (false if not internal)" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "Zammad Configuration" +#: ../misc/variables/article.rst:1 +msgid "Article Text as HTML (not referenced)" msgstr "" -#: ../settings/security/third-party/facebook.rst:44 -#: ../settings/security/third-party/github.rst:43 -#: ../settings/security/third-party/gitlab.rst:46 -msgid "" -"Now you can link accounts via \"Avatar -> Profile -> Link Accounts\" or " -"login via Zammad login page." +#: ../misc/variables/article.rst:1 +msgid "``#{article.body_as_html}``" msgstr "" -#: ../settings/security/third-party/github.rst:2 -#: ../system/integrations/github.rst:2 -msgid "GitHub" +#: ../misc/variables/article.rst:1 +msgid "``Test`` with formatting" msgstr "" -#: ../settings/security/third-party/github.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via GitHub. To " -"activate the quick login you need to enable OAuth for GitHub." +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "Ticket > Article#" msgstr "" -#: ../settings/security/third-party/github.rst:8 -msgid "Register GitHub App" +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "``#{ticket.article_count}``" msgstr "" -#: ../settings/security/third-party/github.rst:10 -msgid "" -"Visit https://www.github.com/settings/applications/new and enter the app " -"settings. As callback URL enter \"https://zammad_host/auth/github/callback\" " -"where zammad_host has to be replaced with your Zammad FQDN" +#: ../misc/variables/article.rst:1 +msgid "``1`` number of ticket articles" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "Register OAuth app on www.github.com" +#: ../misc/variables/config.rst:2 +msgid "Config" msgstr "" -#: ../settings/security/third-party/github.rst:19 -msgid "Configure Zammad as GitHub App" +#: ../misc/variables/config.rst:6 +msgid "" +"Below you'll find config related variables. These hold useful configuration " +"information that you can use within e.g. triggers to show necessary " +"information to your customer." msgstr "" -#: ../settings/security/third-party/github.rst:21 -msgid "" -"Enter the \"APP ID\" and the \"APP SECRET\" from the GitHub OAUTH " -"Applications Dashboard" +#: ../misc/variables/config.rst:11 +msgid "Config Variables" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub config in Zammad admin interface" +#: ../misc/variables/config.rst:1 +msgid "Config > Fully Qualified Domain Name" msgstr "" -#: ../settings/security/third-party/github.rst:28 -msgid "" -"After you configured the GitHub credentials and activated the login method, " -"you should see a new icon on the login page." +#: ../misc/variables/config.rst:1 +msgid "``#{config.fqdn}``" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub logo on login page" +#: ../misc/variables/config.rst:1 +msgid "``zammad.example.com``" msgstr "" -#: ../settings/security/third-party/github.rst:34 -msgid "" -"If you click on the icon you will be redirected to GitHub and see something " -"similar to this:" +#: ../misc/variables/config.rst:1 +msgid "Config > HTTP type" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub oauth page" +#: ../misc/variables/config.rst:1 +msgid "``#{config.http_type}``" msgstr "" -#: ../settings/security/third-party/github.rst:40 -#: ../settings/security/third-party/gitlab.rst:42 -msgid "" -"When you grant the access you will be redirected to your Zammad instance and " -"logged in as a customer." +#: ../misc/variables/config.rst:1 +msgid "``https`` or ``http``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:2 -msgid "Gitlab" +#: ../misc/variables/config.rst:1 +msgid "Config > Organization" msgstr "" -#: ../settings/security/third-party/gitlab.rst:4 +#: ../misc/variables/config.rst:1 +msgid "``#{config.organization}``" +msgstr "" + +#: ../misc/variables/config.rst:1 msgid "" -"It is possible to create a quick login for your helpdesk via Gitlab. To " -"activate the quick login you need to enable OAuth for Gitlab." +"``Zammad GmbH`` value set in `Branding `_" msgstr "" -#: ../settings/security/third-party/gitlab.rst:8 -msgid "Register Gitlab App" +#: ../misc/variables/config.rst:1 +msgid "Config > Product Name" msgstr "" -#: ../settings/security/third-party/gitlab.rst:10 -msgid "To register an app in Gitlab open your profile and select applications." +#: ../misc/variables/config.rst:1 +msgid "``#{config.product_name}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:12 +#: ../misc/variables/config.rst:1 msgid "" -"As callback URL enter \"https://zammad-fqdn/auth/gitlab/callback\" where " -"zammad-fqdn has to be replaced with your Zammad FQDN" +"``Helpdesk`` value set in `Branding `_" msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Register OAuth app on gitlab instance" +#: ../misc/variables/config.rst:1 +msgid "Config > SystemID" msgstr "" -#: ../settings/security/third-party/gitlab.rst:18 -msgid "Just select *read_user* under scopes as in the screenshot and save it." +#: ../misc/variables/config.rst:1 +msgid "``#{config.system_id}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:21 -msgid "Configure Zammad as Gitlab App" +#: ../misc/variables/config.rst:1 +msgid "``31`` (value between 1 and 99)" msgstr "" -#: ../settings/security/third-party/gitlab.rst:23 -msgid "" -"Enter the \"APP ID\" and the \"APP SECRET\" from the Gitlab OAUTH " -"Applications Dashboard and your Gitlab-URL in the \"SITE\" field." +#: ../misc/variables/config.rst:1 +msgid "Config > Ticket Hook" msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab config in Zammad admin interface" +#: ../misc/variables/config.rst:1 +msgid "``#{config.ticket_hook}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:30 -msgid "" -"After you configured the Gitlab credentials and activated the login method, " -"you should see a new icon on the login page." +#: ../misc/variables/config.rst:1 +msgid "``Ticket#``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab logo on login page" +#: ../misc/variables/current-user.rst:2 +msgid "Current User" msgstr "" -#: ../settings/security/third-party/gitlab.rst:36 +#: ../misc/variables/current-user.rst:6 msgid "" -"If you click on the icon you will be redirected to Gitlab and see something " -"similar to this:" +"Current user variables always return values of the current user that caused " +"e.g. a trigger to run." msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab oauth page" +#: ../misc/variables/current-user.rst:8 +msgid "" +"Due to the above fact, these variables are often not (yet) set or available " +"for usage." msgstr "" -#: ../settings/security/third-party/google.rst:4 +#: ../misc/variables/current-user.rst:10 msgid "" -"With some easy and fast steps, you can enable Zammad to authenticate your " -"users via Google." +"In situations where e.g. schedulers or triggers run, this most likely is " +"nothing you want to use." msgstr "" -#: ../settings/security/third-party/google.rst:8 -msgid "Register a Google App" +#: ../misc/variables/current-user.rst:13 +msgid "Current User Variables" msgstr "" -#: ../settings/security/third-party/google.rst:10 -msgid "" -"First of all, we need to create a new project - you can skip this step if " -"you already have one." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Address" msgstr "" -#: ../settings/security/third-party/google.rst:15 -msgid "" -"Use this link to create a new project: https://console.cloud.google.com/" -"projectcreate" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.address}``" msgstr "" -#: ../settings/security/third-party/google.rst:18 -msgid "" -"Now expand the menu, expand \"APIs & Services\" and select \"Credentials\". " -"Go to the tab \"OAuth consent screen\" first and ensure to fill in the " -"requested information - without doing so you can't create credentials!" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set" msgstr "" -#: ../settings/security/third-party/google.rst:None -msgid "Creating a consent screen" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Avatar" msgstr "" -#: ../settings/security/third-party/google.rst:25 -msgid "" -"After filling in and saving the consent screen information, you can go to " -"the \"Credentials\" tab and create new \"OAuth client ID\"-Credentials." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/google.rst:28 -msgid "" -"Fill in the necessary information as follows and replace ``zammad_host`` " -"with your FQDN:" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "avatar picture with width and height in pixel (e.g. 60,60)" msgstr "" -#: ../settings/security/third-party/google.rst:31 -msgid "**Application type** ``[x] Web application``" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created at" msgstr "" -#: ../settings/security/third-party/google.rst:34 -msgid "**Authorized JavaScript origins** ``https://zammad_host/``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_at}``" msgstr "" -#: ../settings/security/third-party/google.rst:37 -msgid "" -"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" -"callback``" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC``" msgstr "" -#: ../settings/security/third-party/google.rst:None -msgid "Adding a new OAuth client ID" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Address" msgstr "" -#: ../settings/security/third-party/google.rst:43 -msgid "" -"After creating the credentials, go to your Zammad installation and navigate " -"to \"Admin > Security > Third Party Applications\" > Google. Enter your " -"Client ID and Client secret here." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.address}``" msgstr "" -#: ../settings/security/third-party/google.rst:None -msgid "Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Avatar" msgstr "" -#: ../settings/security/third-party/google.rst:50 -msgid "After submitting, the login via Google can be used." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:2 -msgid "Microsoft" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Department" msgstr "" -#: ../settings/security/third-party/microsoft.rst:4 -msgid "" -"Zammad's Microsoft connection allows your users with Microsoft accounts to " -"login. This works for Azure users as well and can be an alternative to :doc:" -"`/system/integrations/ldap/index`." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.department}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:10 -msgid "" -"This documentation part does not cover our :doc:`📧 Microsoft 365 email " -"channel `." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Sales`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screenshot showing Microsoft login button on Zammad login screen." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Email" msgstr "" -#: ../settings/security/third-party/microsoft.rst:30 -#: ../settings/security/third-party/microsoft.rst:53 -msgid "Supported account types:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.email}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:22 -msgid "" -"Please note that Zammad only supports these account types (App dependent):" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``jdoe@customer.tld``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:35 -msgid "Avatars of signing in users:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Fax" msgstr "" -#: ../settings/security/third-party/microsoft.rst:33 -msgid "" -"Zammad currently ignores user avatars. If the user is registered with e.g. " -"Gravatar, Zammad will fetch the avatar from there if enabled. See :doc:" -"`Zammad Image Service ` for more." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.fax}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:38 -msgid "Step 1 - Register a Microsoft App for Zammad" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``004930123464789`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:40 -msgid "" -"Login to the `Microsoft Azure Portal `_ and " -"navigate to App registrations to create a new app. Provide the requested " -"information as follows and register your app." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Firstname" msgstr "" -#: ../settings/security/third-party/microsoft.rst:46 -msgid "Name:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.firstname}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:45 -msgid "" -"Any meaningful name fitting, this name will be displayed to users trying to " -"authenticate with this app." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``John`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:49 -msgid "Choose one of the above mentioned account types (see Limitations)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Lastname" msgstr "" -#: ../settings/security/third-party/microsoft.rst:51 -msgid "" -"The correct account type depends on your use case. If you want to use the " -"authentication internal only, choose the first option. If you're unsure, use " -"the \"Help me choose...\" link." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.lastname}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:58 -msgid "Redirect URI (optional):" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Login" msgstr "" -#: ../settings/security/third-party/microsoft.rst:56 -msgid "" -"Select web and provide your callback URL. The callback URL looks like this: " -"``https://zammad.domain.tld/auth/microsoft_office365/callback``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.login}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to register a Microsoft app" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Mobile" msgstr "" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "Within **API permissions** add the following permissions:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.mobile}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:69 -msgid "``User.Read``" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``0049176123456789`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "Contacts" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Note" msgstr "" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "``Contacts.Read``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.note}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:73 -msgid "" -"You can find these permissions within *Microsoft Graph → Delegated " -"permissions*." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Some note to this user`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to add required API permissions" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Phone" msgstr "" -#: ../settings/security/third-party/microsoft.rst:80 -msgid "" -"Within **Certificates & secrets** create a new client secret. Note down the " -"returned secret **value** for later. **Do not** use the secret ID!" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.phone}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to create a new app secret" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``004930123456789`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:88 -msgid "" -"From **Overview** copy your apps *Application (client) ID*. If you're using " -"a single tenant app, please also copy *Directory (tenant) ID*. You now have " -"all required information for Zammad." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > VIP" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to retreive application client and tenant IDs" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.vip}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:98 -msgid "Step 2 - Add App Credentials to Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Web" msgstr "" -#: ../settings/security/third-party/microsoft.rst:100 -msgid "" -"Navigate to Security > Third-party Applications (Tab) within Zammad's admin " -"settings. Scroll down to the section *Authentication via Microsoft* and fill " -"in the required information." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.web}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:105 -msgid "App ID:" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``https://zammad.org`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:105 -msgid "This is your *Application (client) ID*." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Department" msgstr "" -#: ../settings/security/third-party/microsoft.rst:108 -msgid "App secret:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.department}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:108 -msgid "This is your *client secret* (value)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Email" msgstr "" -#: ../settings/security/third-party/microsoft.rst:113 -msgid "App Tenant ID:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.email}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:111 -msgid "" -"**optional** only required for apps that use account type *Accounts in this " -"organizational directory only (Default Directory only - Single tenant).*" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Fax" msgstr "" -#: ../settings/security/third-party/microsoft.rst:115 -msgid "" -"Apply your settings by pressing submit and activate *Authentication via " -"Microsoft*." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.fax}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "" -"Screencast showing how to add app credentials and activating the\n" -"authentication method" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Firstname" msgstr "" -#: ../settings/security/third-party/saml.rst:2 -msgid "SAML" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.firstname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:4 -msgid "" -"Connect your SAML (Security Assertion Markup Language) identity provider as " -"a single sign-on (SSO) method." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Lastname" msgstr "" -#: ../settings/security/third-party/saml.rst:7 -msgid "" -"SAML is an open standard for SSO authentication (among other things). Sign-" -"ins are shared across multiple **service providers** and managed by a " -"central **identity provider** (IdP)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.lastname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:11 -msgid "" -"In this case, the service provider is Zammad, and the IdP is a software " -"service that you either host or subscribe to (*e.g.,* `Keycloak `_, `Redhat SSO Server `_, `ADFS `_, or `Okta `_)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Login" msgstr "" -#: ../settings/security/third-party/saml.rst:18 -msgid "" -"This guide assumes you are already using SAML within your organization (i." -"e., that your IdP is fully set up)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.login}``" msgstr "" -#: ../settings/security/third-party/saml.rst:21 -msgid "" -"Please note: Our instructions are based on connecting Zammad with Keycloak." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Mobile" msgstr "" -#: ../settings/security/third-party/saml.rst:25 -msgid "Step 1: Configure Your IdP" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.mobile}``" msgstr "" -#: ../settings/security/third-party/saml.rst:28 -msgid "Add Zammad as a Client/App" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Note" msgstr "" -#: ../settings/security/third-party/saml.rst:30 -msgid "" -"Import Zammad into your IdP using the XML configuration found at ``https://" -"your.zammad.domain/auth/saml/metadata``." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.note}``" msgstr "" -#: ../settings/security/third-party/saml.rst:33 -msgid "" -"If your IdP doesn't support XML import, you will have to configure Zammad as " -"a new client/app manually using the above XML metadata file for reference." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Domain based assignment" msgstr "" -#: ../settings/security/third-party/saml.rst:36 -msgid "For instance, when you see this tag:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.domain_assignment}``" msgstr "" -#: ../settings/security/third-party/saml.rst:42 -msgid "" -"Set the **Assertion Consumer Service Binding URL** (sometimes also listed as " -"**Valid Redirect URIs**) to ``http://your.zammad.domain/auth/saml/callback``." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Domain" msgstr "" -#: ../settings/security/third-party/saml.rst:47 -msgid "Set Up User Attribute Mapping" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.domain}``" msgstr "" -#: ../settings/security/third-party/saml.rst:49 -msgid "" -"Zammad requests the following user attributes (or “properties”) from the IdP:" +#: ../misc/variables/current-user.rst:1 +msgid "``zammad.com`` or empty if not set" msgstr "" -#: ../settings/security/third-party/saml.rst:51 -msgid "Email address (``email``)" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Name" msgstr "" -#: ../settings/security/third-party/saml.rst:52 -msgid "Full name (``name``)" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.name}``" msgstr "" -#: ../settings/security/third-party/saml.rst:53 -msgid "Given name (``first_name``)" +#: ../misc/variables/current-user.rst:1 +msgid "``Zammad GmbH``" msgstr "" -#: ../settings/security/third-party/saml.rst:54 -msgid "Family name (``last_name``)" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Note" msgstr "" -#: ../settings/security/third-party/saml.rst:56 -msgid "" -"You may need to set up “mappers” (or “mappings”) to tell your IdP how user " -"attributes in SAML correspond to those in Zammad. For a more detailed " -"breakdown, refer to the XML metadata file referenced in the previous section." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.note}``" msgstr "" -#: ../settings/security/third-party/saml.rst:62 -msgid "Per-IdP Instructions" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``A note to the organization of the user`` or empty if not set" msgstr "" -#: ../settings/security/third-party/saml.rst:102 -msgid "Keycloak" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Shared organization" msgstr "" -#: ../settings/security/third-party/saml.rst:65 -msgid "" -"**To add Zammad as a client,** save the XML configuration to disk (``https://" -"your.zammad.domain/auth/saml/metadata``) and use **Clients > Clients list > " -"Import client** in the Keycloak admin panel." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.shared}``" msgstr "" -#: ../settings/security/third-party/saml.rst:70 -msgid "" -"To help Zammad **match its own user accounts to Keycloak users**, create a " -"user attribute (or “property”) mapper. In **Clients list**, click on your " -"newly created Client ID, choose the tab **Client scopes** and click on the " -"link which refers to your Zammad instance. Choose **Add mapper > By " -"configuration > User Property** and create a mapper with the following " -"entries:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > VIP" msgstr "" -#: ../settings/security/third-party/saml.rst:78 -msgid "**Name**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.vip}``" msgstr "" -#: ../settings/security/third-party/saml.rst:80 -msgid "**Mapper Type**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Phone" msgstr "" -#: ../settings/security/third-party/saml.rst:81 -msgid "``User Property``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.phone}``" msgstr "" -#: ../settings/security/third-party/saml.rst:82 -msgid "**Property**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated at" msgstr "" -#: ../settings/security/third-party/saml.rst:83 -msgid "``emailAddress``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_at}``" msgstr "" -#: ../settings/security/third-party/saml.rst:84 -msgid "**SAML Attribute Name**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Address" msgstr "" -#: ../settings/security/third-party/saml.rst:86 -msgid "**SAML Attribute NameFormat**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.address}``" msgstr "" -#: ../settings/security/third-party/saml.rst:87 -msgid "``basic``" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Avatar" msgstr "" -#: ../settings/security/third-party/saml.rst:89 -msgid "" -"In the example above, we're telling Zammad that whenever it receives a SAML " -"login request, it should take the ``email`` property from Keycloak, look for " -"a Zammad user with the same ``email`` attribute, and create a new session " -"for that user." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/saml.rst:95 -msgid "" -"If your Keycloak users' email addresses are stored on another property (*e." -"g.,* ``username``), adjust accordingly." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Department" msgstr "" -#: ../settings/security/third-party/saml.rst:98 -msgid "" -"Back in **Settings**, enter the Client ID (``https://your.zammad.domain/auth/" -"saml/metadata``) in the field **Master SAML Processing URL**." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.department}``" msgstr "" -#: ../settings/security/third-party/saml.rst:101 -msgid "You also need to enable **Sign assertions**." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Email" msgstr "" -#: ../settings/security/third-party/saml.rst:105 -msgid "Step 2: Configure Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.email}``" msgstr "" -#: ../settings/security/third-party/saml.rst:107 -msgid "" -"Enable SAML and enter your IdP's details in the Admin Panel under **Settings " -"> Security > Third Party Applications > Authentication via SAML**:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Fax" msgstr "" -#: ../settings/security/third-party/saml.rst:None -msgid "Example configuration of SAML part 1" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.fax}``" msgstr "" -#: ../settings/security/third-party/saml.rst:119 -msgid "Display name" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Firstname" msgstr "" -#: ../settings/security/third-party/saml.rst:116 -msgid "" -"Allows you to define a custom button name for SAML. This helps your users to " -"understand better what the button on the login page does." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.firstname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:119 -msgid "Defaults to ``SAML``." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Lastname" msgstr "" -#: ../settings/security/third-party/saml.rst:123 -msgid "IDP SSO target URL" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.lastname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:122 -msgid "" -"This is the target URL Zammad shall redirect to when the user presses the " -"SAML button. For Keycloak, this needs to look like https://your.domain/" -"realms/your-realm/protocol/saml" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Login" msgstr "" -#: ../settings/security/third-party/saml.rst:127 -msgid "IDP single logout target URL" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.login}``" msgstr "" -#: ../settings/security/third-party/saml.rst:126 -msgid "" -"This is the URL to which the single logout request and response should be " -"sent." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Mobile" msgstr "" -#: ../settings/security/third-party/saml.rst:131 -msgid "IDP certificate" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.mobile}``" msgstr "" -#: ../settings/security/third-party/saml.rst:130 -msgid "" -"The public certificate of your IDP for Zammad to verify during the callback " -"phase." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Note" msgstr "" -#: ../settings/security/third-party/saml.rst:145 -msgid "IDP certificate fingerprint" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.note}``" msgstr "" -#: ../settings/security/third-party/saml.rst:134 -msgid "" -"The fingerprint of your IDPs public certificate to verify during callback " -"phase." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Phone" msgstr "" -#: ../settings/security/third-party/saml.rst:137 -msgid "🔏 **For the IdP certificate / certificate fingerprint:**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.phone}``" msgstr "" -#: ../settings/security/third-party/saml.rst:139 -msgid "" -"Provide **only one or the other**—do not provide both! (Between the two, we " -"recommend the signing certificate itself: fingerprints use SHA-1, which `has " -"been broken for a while now `_.)" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > VIP" msgstr "" -#: ../settings/security/third-party/saml.rst:144 -msgid "" -"**Keycloak users:** Find your certificate in the Keycloak admin panel under " -"**Realm Settings > Keys > Algorithm: RS256 > Certificate**." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.vip}``" msgstr "" -#: ../settings/security/third-party/saml.rst:151 -msgid "Name identifier format" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``false`` or ``true``" msgstr "" -#: ../settings/security/third-party/saml.rst:148 -msgid "" -"This is the unique identifiers field type. Usually it should be ``urn:oasis:" -"names:tc:SAML:1.1:nameid-format:emailAddress``." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Web" msgstr "" -#: ../settings/security/third-party/saml.rst:151 -msgid "Zammad **expects an email address as unique identifier**!" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.web}``" msgstr "" -#: ../settings/security/third-party/saml.rst:155 -msgid "UID attribute name" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > VIP" msgstr "" -#: ../settings/security/third-party/saml.rst:154 -msgid "" -"Here you can define an attribute that uniquely identifies the user. If " -"unset, the name identifier returned by the IDP is used." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.vip}``" msgstr "" -#: ../settings/security/third-party/saml.rst:None -msgid "Example configuration of SAML part 2" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Web" msgstr "" -#: ../settings/security/third-party/saml.rst:163 -msgid "" -"Decide if the certificate for the connection to the IdP service has to be " -"verified or not (default: ``yes``)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.web}``" msgstr "" -#: ../settings/security/third-party/saml.rst:169 -msgid "Signing & Encrypting" +#: ../misc/variables/ticket.rst:6 +msgid "" +"Below you can find all available ticket-based variables within Zammad. These " +"can be called via triggers for example. If you're unsure if Zammad does " +"support variables at the point you're at, you can try to type ``::`` to " +"check." msgstr "" -#: ../settings/security/third-party/saml.rst:169 -msgid "" -"Define if you want to sign, encrypt, do both or nothing for the requests." +#: ../misc/variables/ticket.rst:12 +msgid "Ticket Variables" msgstr "" -#: ../settings/security/third-party/saml.rst:179 -msgid "Certificate (PEM)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Accounted Time" msgstr "" -#: ../settings/security/third-party/saml.rst:172 -msgid "" -"Paste the public certificate of your Zammad SAML client, if you want to " -"encrypt the requests." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.time_unit}``" msgstr "" -#: ../settings/security/third-party/saml.rst:175 -msgid "Make sure the certificate is:" +#: ../misc/variables/ticket.rst:1 +msgid "``1``, ``2.75`` or empty response" msgstr "" -#: ../settings/security/third-party/saml.rst:177 -msgid "already valid and not yet expired" +#: ../misc/variables/ticket.rst:1 +msgid "``3``, any number of articles existing in the ticket right now" msgstr "" -#: ../settings/security/third-party/saml.rst:178 -msgid "no CA certificate" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Closing time" msgstr "" -#: ../settings/security/third-party/saml.rst:179 -msgid "valid for signing and encrypting" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.close_at}``" msgstr "" -#: ../settings/security/third-party/saml.rst:185 -msgid "Private key (PEM)" +#: ../misc/variables/ticket.rst:1 +msgid "2019-10-07 17:25:00 UTC" msgstr "" -#: ../settings/security/third-party/saml.rst:182 -msgid "" -"Paste the private key of your Zammad SAML client here, if you want to sign " -"the requests." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created at" msgstr "" -#: ../settings/security/third-party/saml.rst:185 -msgid "Make sure the key is an RSA key with a length of at least 2048 bits." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_at}``" msgstr "" -#: ../settings/security/third-party/saml.rst:188 -msgid "Private key secret" +#: ../misc/variables/ticket.rst:1 +msgid "2019-10-07 16:25:00 UTC" msgstr "" -#: ../settings/security/third-party/saml.rst:188 -msgid "If your private key is secured with a secret, you can provide it here." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Address" msgstr "" -#: ../settings/security/third-party/saml.rst:192 -msgid "Your callback URL" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.address}``" msgstr "" -#: ../settings/security/third-party/saml.rst:191 -msgid "" -"This URL is needed for your IdP configuration so it knows where to redirect " -"to after successful authentication." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Avatar" msgstr "" -#: ../settings/security/third-party/saml.rst:194 -msgid "" -"After saving your input by clicking on the \"Submit\" button, Zammad " -"verifies the provided keys/certificates (e.g. if they are valid for signing/" -"encrypting and if they aren't expired)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/saml.rst:199 -msgid "" -"See :ref:`automatic account linking ` for details " -"on how to link existing Zammad accounts to IdP accounts." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Department" msgstr "" -#: ../settings/security/third-party/saml.rst:205 -msgid "Automatic account linking doesn't work" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.department}``" msgstr "" -#: ../settings/security/third-party/saml.rst:206 -msgid "" -"Have you double-checked your IdP's user attribute mapping configuration?" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Email" msgstr "" -#: ../settings/security/third-party/twitter.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via Twitter. To do " -"so, you need to follow these steps:" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.email}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:8 -msgid "Register Twitter App" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Fax" msgstr "" -#: ../settings/security/third-party/twitter.rst:10 -msgid "Go to https://dev.twitter.com/apps and login with your account." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.fax}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:15 -msgid "Click on \"Create App\"" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Firstname" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "new app page" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.firstname}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:20 -msgid "" -"Enter app settings. As \"Callback URL\" you need to enter ``https://" -"zammad_host/api/v1/external_credentials/twitter/callback``. You need to " -"replace ``zammad_host`` with the domain of your Zammad system." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Lastname" msgstr "" -#: ../settings/security/third-party/twitter.rst:24 -msgid "" -"After the app has been created, update the application icon and organization " -"attributes." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.lastname}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "set permissions to receive and send direct messages" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Login" msgstr "" -#: ../settings/security/third-party/twitter.rst:30 -msgid "" -"Next we need to set ``read, write and access direct messages`` permissions " -"for the app." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.login}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "click on Keys & Access Token, note them" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Mobile" msgstr "" -#: ../settings/security/third-party/twitter.rst:36 -msgid "" -"Go to \"Keys and Access Token\" tab and note the \"Consumer Key\" and " -"\"Consumer Secret\"." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.mobile}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:40 -msgid "Configure Zammad as Twitter App" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Note" msgstr "" -#: ../settings/security/third-party/twitter.rst:42 -msgid "" -"Go to \"Admin > Security > Twitter > Third Party Applications > Twitter\" " -"Section." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.note}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "Admin > Security > Third Party Applications" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Phone" msgstr "" -#: ../settings/security/third-party/twitter.rst:48 -msgid "" -"Fill in the \"Twitter Key\" and the \"Twitter Secret\" and click the " -"\"Submit\" button." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.phone}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:51 -msgid "" -"Now you can link accounts via \"Avatar > Profile > Link Accounts\" or login " -"via Zammad login page." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > VIP" msgstr "" -#: ../settings/security/two-factor.rst:11 -msgid "Two-factor Authentication Methods" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.vip}``" msgstr "" -#: ../settings/security/two-factor.rst:2 -msgid "Two-Factor Authentication" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Web" msgstr "" -#: ../settings/security/two-factor.rst:4 -msgid "" -"Two-factor authentication (2FA) enhances the security of Zammad accounts by " -"adding an extra layer of verification beyond a password. It requires users " -"to provide two different types of authentication factors, typically " -"something they know (like a password) and something they possess (like a " -"mobile device or a security token), to ensure that only authorized " -"individuals can access the account." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.web}``" msgstr "" -#: ../settings/security/two-factor.rst:19 -msgid "Enable Recovery Codes" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Address" msgstr "" -#: ../settings/security/two-factor.rst:21 -msgid "" -"Recovery codes are one-time use security codes that can be used by the user " -"if they lose access to their other two-factor authentication methods. They " -"cannot be used on their own, they can only be activated if at least one two-" -"factor authentication method is enabled." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.address}``" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Enable Recovery Codes Setting" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Avatar" msgstr "" -#: ../settings/security/two-factor.rst:30 -msgid "" -"Recovery codes can only be used as a backup method. If enabled, they will be " -"automatically generated for the user once they set up their initial two-" -"factor authentication method." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.avatar(60,60)}``" msgstr "" -#: ../settings/security/two-factor.rst:34 -msgid "" -"The user will be asked to print out or save the generated recovery codes in " -"a safe place. Once used, a recovery code cannot be reused." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Department" msgstr "" -#: ../settings/security/two-factor.rst:37 -msgid "" -"Users will also have an option to regenerate their recovery codes at any " -"time, which invalidates already existing recovery codes and provides them " -"with a list of fresh codes." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.department}``" msgstr "" -#: ../settings/security/two-factor.rst:41 -msgid "" -"After you enable this setting, when the user completes a setup of their " -"initial two-factor authentication method, they will be presented with a list " -"of recovery codes and instructed to save them for later use." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Email" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Recovery Codes Generation Modal Dialog" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.email}``" msgstr "" -#: ../settings/security/two-factor.rst:50 -msgid "Enforce the Set Up of the Two-Factor Authentication" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Fax" msgstr "" -#: ../settings/security/two-factor.rst:52 -msgid "" -"In case you wish to require your users to set up at least one two-factor " -"authentication method for their account, you can do this by selecting " -"specific user roles the requirement applies to in **Enforced for user " -"roles** setting. Of course you must have at least one two-factor " -"authentication method enabled for this setting to take effect." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.fax}``" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Enforced for User Roles Setting" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Firstname" msgstr "" -#: ../settings/security/two-factor.rst:62 -msgid "" -"After you change this setting, if the user has one of the selected roles on " -"their account, they will be forced to set up the two-factor authentication " -"upon next sign in or application reload." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.firstname}``" msgstr "" -#: ../settings/security/two-factor.rst:66 -msgid "" -"A modal dialog with instructions will be shown, and they will not be able to " -"do any work before they set up at least one two-factor method." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Lastname" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Modal Dialog for Enforcing Two-Factor Authentication Set Up" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.lastname}``" msgstr "" -#: ../settings/security/two-factor.rst:74 -msgid "Reset Two-Factor Authentication for a Specific User" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Login" msgstr "" -#: ../settings/security/two-factor.rst:76 -msgid "" -"In case an user isn't able to login anymore because of an inaccessible " -"second factor, you can reset the user's 2FA method." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.login}``" msgstr "" -#: ../settings/security/two-factor.rst:79 -msgid "" -"To do this, go to the user management and search for the relevant user. " -"After you found the account, click the button in the action column and " -"select \"Manage Two-Factor Authentication\":" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Mobile" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Context menu in action column in user management" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.mobile}``" msgstr "" -#: ../settings/security/two-factor.rst:87 -msgid "" -"After selecting this, you can see a dialog where you can either reset one " -"2FA method or reset all of the user's 2FA methods:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Note" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Dialog for resetting user's 2FA method" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.note}``" msgstr "" -#: ../settings/security/two-factor.rst:94 -msgid "" -"Choose the fitting one, click on the corresponding \"Remove ...\" button and " -"confirm your action. The user now has to setup a new 2FA method, depending " -"on your 2FA configuration." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Phone" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:2 -msgid "Authenticator App" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.phone}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:4 -msgid "" -"The authenticator app method is a type of two-factor authentication that " -"uses a mobile application to generate one-time codes for account " -"verification. After setting up the authenticator app on their device, the " -"user links it to their Zammad account." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > VIP" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:12 -msgid "" -"When logging in, the user is prompted to enter a time-sensitive code " -"generated by the app, in addition to their password. This code acts as the " -"second factor of authentication, providing an extra layer of security as it " -"changes periodically and is unique to the user's device." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.vip}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:None -msgid "Security Code in Google Authenticator App" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Web" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:22 -msgid "" -"The app generates codes based on a shared secret key stored securely on both " -"the user's device and the server, ensuring a synchronized and secure " -"authentication process. The method of generating the codes is sometimes also " -"called TOTP (time-based one-time password)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.web}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:28 -msgid "Enabling the Authenticator App Method" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Escalation at" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:30 -#: ../settings/security/two-factor/security-keys.rst:28 -msgid "To enable the method, just toggle the switch on in the settings." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.escalation_at}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:None -msgid "Authenticator App Switch in Settings" +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:36 -msgid "" -"Now the users will be able to set up this two-factor authentication method " -"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " -"Once they do, on next sign-in with password, they will be asked to provide " -"an additional security code generated by their mobile device." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > First response" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:2 -msgid "Security Keys" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.first_response_at}``" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:4 -msgid "" -"The security keys method is a type of a two-factor authentication that uses " -"Web Authentication API in the browser for verifying user's identity. The " -"user can register multiple hardware or software security keys with their " -"Zammad account and then they can use it during the sign-in process." +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable yet" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:12 -msgid "" -"When logging in, the user is prompted to provide the same security key they " -"registered with their account, in addition to their password. This key acts " -"as the second factor of authentication, providing an extra layer of security." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Assign Follow-Ups" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:None -msgid "Security Key dialog in Safari on macOS" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_assignment}``" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:21 -msgid "" -"The type of the key can range from hardware USB sticks to passkeys stored in " -"a device of user's choice. Which type can be used depends on the browser " -"flavor and the platform of the user." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Assignment Timeout" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:26 -msgid "Enabling the Security Keys Method" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.assignment_timeout}``" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:None -msgid "Security Keys Switch in Settings" +#: ../misc/variables/ticket.rst:1 +msgid "``20`` or empty if not configured" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:34 -msgid "" -"Now the users will be able to set up this two-factor authentication method " -"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " -"Once they do, on next sign-in with password, they will be asked to provide " -"the same security key they registered during the setup." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Follow-up possible" msgstr "" -#: ../settings/system/system-selfhosted.include.rst:3 -msgid "" -"Below settings are only available to self hosted users. In hosted " -"environments we're handling these settings for you to ensure service " -"stability." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_possible}``" msgstr "" -#: ../settings/system/base.rst:11 -msgid "Fully Qualified Domain Name" +#: ../misc/variables/ticket.rst:1 +msgid "``no`` or ``yes``" msgstr "" -#: ../settings/system/base.rst:7 -msgid "The URL of your Zammad installation." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Name" msgstr "" -#: ../settings/system/base.rst:9 ../settings/system/base.rst:17 -msgid "This setting is used within :doc:`/system/variables` and notifications." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.name}``" msgstr "" -#: ../settings/system/system-base.include.rst:1 -msgid "It is automatically set by the *Getting Started wizard*." +#: ../misc/variables/ticket.rst:1 +msgid "``Sales``" msgstr "" -#: ../settings/system/system-base.include.rst:5 -msgid "Changing this setting also changes callback URLs for your channels etc." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Note" msgstr "" -#: ../settings/system/system-base.include.rst:6 -msgid "This setting can have negative affects on being able to login." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.note}``" msgstr "" -#: ../settings/system/base.rst:19 -msgid "HTTP type" +#: ../misc/variables/ticket.rst:1 +msgid "``Note about this group``" msgstr "" -#: ../settings/system/base.rst:14 -msgid "" -"The HTTP type tells your installation how your clients connect. This is " -"relevant for authentication and cookie security." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > ID" msgstr "" -#: ../settings/system/base.rst:31 -msgid "SystemID" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.id}``" msgstr "" -#: ../settings/system/base.rst:22 -msgid "" -"This ID is being used within your ticket number. In case you're " -"communicating with another ticket system with similar ticket number schemes " -"this ID greatly reduces the risk of false follow ups." +#: ../misc/variables/ticket.rst:1 +msgid "``17``, ``5281``, ..." msgstr "" -#: ../settings/system/base.rst:26 -msgid "" -"The SystemID is randomly selected upon installation of Zammad (``1-99``)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact (agent)" msgstr "" -#: ../settings/system/base.rst:30 -msgid "" -"**Do not** change this setting in a productive system! Your Zammad " -"installation may no longer recognize old ticket number based follow ups upon " -"change!" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_agent_at}``" msgstr "" -#: ../settings/system/frontend.rst:2 -msgid "Frontend" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact (customer)" msgstr "" -#: ../settings/system/frontend.rst:22 -msgid "Core Workflow Ajax Mode" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_customer_at}``" msgstr "" -#: ../settings/system/frontend.rst:6 +#: ../misc/variables/ticket.rst:1 msgid "" -"This setting allows administrators to enforce :doc:`/system/core-workflows` " -"to use Ajax-Calls instead of web sockets. You'll usually only need this if " -"you experience serious issues as noted below." +"``2019-10-07 16:25:00 UTC`` or empty if not applicable yet (Please note " +"`Ticket last contact behavior Settings `_ for this)" msgstr "" -#: ../settings/system/frontend.rst:10 -msgid "**🤓 Possible (technical) reasons**" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact" msgstr "" -#: ../settings/system/frontend.rst:12 -msgid "" -"In some cases, your network structure (e.g. firewalls, proxies) may " -"disconnect long web socket connections. This leads to select fields staying " -"empty (e.g. owner selection *after* selecting your group) or fields not " -"shown / hidden (e.g. when switching to or from pending states, the \"pending " -"till\" field not showing / hiding)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_at}``" msgstr "" -#: ../settings/system/frontend.rst:18 -msgid "" -"Please keep in mind that the Ajax fallback may cause serious pressure on " -"your application server. If you have the choice stick to web sockets." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Number" msgstr "" -#: ../settings/system/frontend.rst:22 -msgid "Default: ``no`` (inactive)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.number}``" msgstr "" -#: ../settings/system/frontend.rst:53 -msgid "Show calendar weeks in the picker of date/datetime fields" +#: ../misc/variables/ticket.rst:1 +msgid "``31001``, ``201910731001``, ..." msgstr "" -#: ../settings/system/frontend.rst:25 -msgid "" -"With this setting you can instruct Zammad to provide week number display " -"globally for all users. Calendar with week number display are usually used " -"in business sectors and may not be relevant for everyone." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain based assignment" msgstr "" -#: ../settings/system/frontend.rst:29 -msgid "" -"This setting affects *all areas* - you'll also see week numbers in the admin " -"panel for e.g. triggers and macros." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain_assignment}``" msgstr "" -#: ../settings/system/frontend.rst:32 -msgid "Default: ``no`` (not shown)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain" msgstr "" -#: ../settings/system/frontend.rst:53 -msgid "Here's the difference:" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain}``" msgstr "" -#: ../settings/system/frontend.rst:0 -msgid "Screenshot showing Zammad's date picker (in the default way)" +#: ../misc/variables/ticket.rst:1 +msgid "``domain.tld`` or empty if not set" msgstr "" -#: ../settings/system/frontend.rst:41 -msgid "Set to ``no``" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Name" msgstr "" -#: ../settings/system/frontend.rst:0 -msgid "" -"Screenshot showing Zammad's date picker with\n" -"week numbers enabled" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.name}``" msgstr "" -#: ../settings/system/frontend.rst:50 -msgid "Set to ``yes``" +#: ../misc/variables/ticket.rst:1 +msgid "``Zammad GmbH`` or empty if not set" msgstr "" -#: ../settings/system/index.rst:4 -msgid "" -"For your overview we split each tab within system settings into its own page:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Note" msgstr "" -#: ../settings/system/index.rst:16 -msgid "Console Based Settings" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.note}``" msgstr "" -#: ../settings/system/index.rst:18 -msgid "" -"There's some console based settings we didn't put into the UI. However, you " -"may find them helpful - you can find them in our :docs:`hidden settings ` section." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Shared organization" msgstr "" -#: ../settings/system/network.rst:2 -msgid "Network" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.shared}``" msgstr "" -#: ../settings/system/network.rst:8 -msgid "" -"The proxy settings can only be saved after successfully testing the proxy " -"connection." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > VIP" msgstr "" -#: ../settings/system/network.rst:15 -msgid "Proxy Address." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.vip}``" msgstr "" -#: ../settings/system/network.rst:12 -msgid "" -"Allows you to provide a proxy server if needed. This is relevant for network " -"communication by Zammad." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Address" msgstr "" -#: ../settings/system/network.rst:15 -msgid "It **does not** affect the update process or Elasticsearch." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.address}``" msgstr "" -#: ../settings/system/network.rst:18 -msgid "Username for proxy connection." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Avatar" msgstr "" -#: ../settings/system/network.rst:18 -msgid "" -"If your proxy server requires authentication, provide the username here." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.avatar(60,60)}``" msgstr "" -#: ../settings/system/network.rst:21 -msgid "Password for proxy connection." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Department" msgstr "" -#: ../settings/system/network.rst:21 -msgid "" -"If your proxy server requires authentication, provide the password here." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.department}``" msgstr "" -#: ../settings/system/network.rst:26 -msgid "No proxy for the following hosts." +#: ../misc/variables/ticket.rst:1 +msgid "``Support`` or empty if not set" msgstr "" -#: ../settings/system/network.rst:24 -msgid "" -"Exception list for hosts you can't or don't want to reach via proxy server." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Email" msgstr "" -#: ../settings/system/network.rst:27 -msgid "Default: ``localhost,127.0.0.0,::1``" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.email}``" msgstr "" -#: ../settings/system/services.rst:2 -msgid "Services" +#: ../misc/variables/ticket.rst:1 +msgid "``agent@company.tld`` or empty if not set" msgstr "" -#: ../settings/system/services.rst:10 -msgid "Image Service" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Fax" msgstr "" -#: ../settings/system/services.rst:5 -msgid "Defines the backend for user and organization image lookups." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.fax}``" msgstr "" -#: ../settings/system/services.rst:7 -msgid "Default: ``Zammad Image Service`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Firstname" msgstr "" -#: ../settings/system/services.rst:9 -msgid "" -"Make sure your on premise installation has ``HTTPS`` access to ``images." -"zammad.com``." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.firstname}``" msgstr "" -#: ../settings/system/services.rst:18 -msgid "Geo Calendar Service" +#: ../misc/variables/ticket.rst:1 +msgid "``Max`` or empty if not set" msgstr "" -#: ../settings/system/services.rst:13 -msgid "" -"Defines the backend for geo calendar lookups. Used for initial calendar " -"setup." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Lastname" msgstr "" -#: ../settings/system/services.rst:16 -msgid "Default: ``Zammad GeoCalendar Service`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.lastname}``" msgstr "" -#: ../settings/system/services.include.rst:2 -msgid "" -"Make sure your on premise installation has ``HTTPS`` access to ``geo.zammad." -"com``." +#: ../misc/variables/ticket.rst:1 +msgid "``Mustermann`` or empty if not set" msgstr "" -#: ../settings/system/services.rst:26 -msgid "Geo IP Service" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Login" msgstr "" -#: ../settings/system/services.rst:21 -msgid "" -"Defines the backend for geo IP lookups. Shows also location of an IP address " -"if an IP address is shown." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.login}``" msgstr "" -#: ../settings/system/services.rst:24 -msgid "Default: ``Zammad GeoIP Service`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "``agent``" msgstr "" -#: ../settings/system/services.rst:32 -msgid "Geo Location Service" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Mobile" msgstr "" -#: ../settings/system/services.rst:29 -msgid "" -"Defines the backend for geo location lookups to store geo locations for " -"addresses." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.mobile}``" msgstr "" -#: ../settings/system/services.rst:32 -msgid "" -"Default: ``OpenStreetMap (ODbL 1.0, http://osm.org/copyright)`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Note" msgstr "" -#: ../settings/system/services.rst:36 -msgid "" -"You can find a detailed privacy information on what we store for how long on " -"our :docs:`Privacy Appendix ` inside of our System " -"Documentation." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.note}``" msgstr "" -#: ../settings/system/storage.rst:2 -msgid "Storage" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Phone" msgstr "" -#: ../settings/system/storage.rst:6 -msgid "" -"Here you can define where Zammad stores attachments for tickets and the " -"knowledge base. By default, we're writing to the ``Database`` - you can " -"switch to ``Filesystem`` or ``Simple Storage (S3)`` at any time. In this " -"case please have a look on the following instructions." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.phone}``" msgstr "" -#: ../settings/system/storage.rst:11 -msgid "" -"If you have a busy Zammad instance, we strongly encourage you to use " -"filesystem storage instead of \"Database\". This will greatly improve system " -"performance (de-crease database load and size)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > VIP" msgstr "" -#: ../settings/system/storage.rst:19 -msgid "Database" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.vip}``" msgstr "" -#: ../settings/system/storage.rst:17 -msgid "" -"This is the default storage method. The attachments are stored directly in " -"the database. If your Zammad instance grows, we recommend one of the other " -"methods to maintain performance." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Web" msgstr "" -#: ../settings/system/storage.rst:38 -msgid "Filesystem" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.web}``" msgstr "" -#: ../settings/system/storage.rst:22 -msgid "" -"This storage method is recommended for all Zammad instances, especially for " -"those with a higher load. If you choose filesystem, your files are written " -"to ``/opt/zammad/storage/``." +#: ../misc/variables/ticket.rst:1 +msgid "``https://zammad.com`` or empty if not set" msgstr "" -#: ../settings/system/storage.rst:26 -msgid "" -"Moving attachments from \"Database\" to \"Filesystem\" can be run during " -"production use. However, you should consider your framework conditions (e.g. " -"bandwidth, system load in production) to define the right moment." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Pending till" msgstr "" -#: ../settings/system/storage.rst:32 -msgid "**You noticed slow updates of Zammad?**" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.pending_time}``" msgstr "" -#: ../settings/system/storage.rst:34 -msgid "" -"While Zammad is beeing updated, it enforces a recursive \"change " -"owner\" (chown) for this directory. For instances with many files this can " -"be time consuming. To mitigate that you can move your files and create a " -"symlink in ``/opt/zammad/storage/`` to the new directory. Of course you have " -"to make sure on your own that the permissions are always correct." +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not set" msgstr "" -#: ../settings/system/storage.rst:95 -msgid "Simple Storage (S3)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Priority > Name" msgstr "" -#: ../settings/system/storage.rst:41 -msgid "" -"To use the Simple Storage (S3), you have to provide some settings, which " -"can't be accessed in the UI (see instructions below)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.priority.name}``" msgstr "" -#: ../settings/system/storage.rst:44 -msgid "" -"⚠️ Please note that the current implementation is in its early stages and can " -"be modified in the future." +#: ../misc/variables/ticket.rst:1 +msgid "``2 normal``" msgstr "" -#: ../settings/system/storage.rst:47 -msgid "" -"The prerequisite is to have access to a S3-compatible storage and to have " -"all necessary parameters available (which depends on your storage provider; " -"if in doubt, please ask there for help)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > State > Name" msgstr "" -#: ../settings/system/storage.rst:51 -msgid "Steps to configure S3:" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.state.name}``" msgstr "" -#: ../settings/system/storage.rst:53 -msgid "" -"Copy ``config/zammad/storage.yml.dist`` to ``config/zammad/storage.yml``" +#: ../misc/variables/ticket.rst:1 +msgid "``new``, ``open``, ..." msgstr "" -#: ../settings/system/storage.rst:54 -msgid "Edit the copied file in one of the following ways:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Tags" msgstr "" -#: ../settings/system/storage.rst:56 -msgid "" -"Either provide your S3 configuration with one attribute per line like in the " -"upper area of the file" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.tags}``" msgstr "" -#: ../settings/system/storage.rst:58 +#: ../misc/variables/ticket.rst:1 msgid "" -"Or provide your S3 configuration as an URL (which you can find at the end of " -"the file). Note: you can also provide this URL as environment variable (:" -"docs:`see system documentation `) without using this yml-file." +"Currently not available, see `Issue 2769 `_" msgstr "" -#: ../settings/system/storage.rst:62 -msgid "" -"We recommend the deletion of the not used configuration style to avoid " -"inconsistencies." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Title" msgstr "" -#: ../settings/system/storage.rst:65 -msgid "Restart Zammad so the config file / environment variable is loaded" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.title}``" msgstr "" -#: ../settings/system/storage.rst:66 +#: ../misc/variables/ticket.rst:1 msgid "" -"Set the \"Storage Method\" in Zammad to ``Simple Storage (S3)`` in Settings " -"> System > Storage and click on \"Submit\". After that, Zammad checks your " -"configuration and the connection to the service and will raise an error " -"message if something is wrong." +"``My amazing Subject`` (normally subject, can be edited within Interface and " +"thus differ)" msgstr "" -#: ../settings/system/storage.rst:72 -msgid "A very simple storage configuration could look like this:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated at" msgstr "" -#: ../settings/system/storage.rst:85 -msgid "" -"Before setting the storage method to ``Simple Storage (S3)`` (step 4), " -"please make sure to have a working setup." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_at}``" msgstr "" -#: ../settings/system/storage.rst:88 -msgid "" -"You can verify this by running ``rails r 'Rails.logger = Logger.new(STDOUT); " -"pp Store::Provider::S3.ping?'`` in your Zammad directory. If everything is " -"fine, you should see ``true``, else you should see ``false`` and a simple " -"error message." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Address" msgstr "" -#: ../settings/system/storage.rst:93 -msgid "" -"If you installed Zammad through a package manager (rather than from source), " -"replace ``rails r`` with ``zammad run rails r`` above. To learn more, see :" -"docs:`Administration via Console `." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.address}``" msgstr "" -#: ../settings/ticket.rst:4 -msgid "" -"Here you can adjust general ticket settings. Additional ones for the ticket " -"composer interface can be found in the :doc:`/misc/composer`." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Avatar" msgstr "" -#: ../settings/ticket.rst:11 -msgid "Ticket Hook (default: ``Ticket#``)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.avatar(60,60)}``" msgstr "" -#: ../settings/ticket.rst:11 -msgid "The identifier for a ticket; *e.g.,* Ticket#, Call#, MyTicket#." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Department" msgstr "" -#: ../settings/ticket.rst:38 -msgid "Ticket Hook Position (default: ``right``)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.department}``" msgstr "" -#: ../settings/ticket.rst:14 -msgid "" -"With this setting you can decide (if) where to insert the ticket number." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Email" msgstr "" -#: ../settings/ticket.rst:20 -msgid "*Right*" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.email}``" msgstr "" -#: ../settings/ticket.rst:17 -msgid "" -"This setting will add the ticket reference on the right site of the subject." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Fax" msgstr "" -#: ../settings/ticket.rst:20 -msgid "Example: ``Some Subject [Ticket#12345]``" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.fax}``" msgstr "" -#: ../settings/ticket.rst:26 -msgid "*Left*" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Firstname" msgstr "" -#: ../settings/ticket.rst:23 -msgid "" -"This setting will add the ticket reference on the left site of the subject." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.firstname}``" msgstr "" -#: ../settings/ticket.rst:26 -msgid "Example: ``[Ticket#12345] Some Subject``" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Lastname" msgstr "" -#: ../settings/ticket.rst:29 -msgid "*None*" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.lastname}``" msgstr "" -#: ../settings/ticket.rst:29 -msgid "This will completely remove ticket references from the subject." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Login" msgstr "" -#: ../settings/ticket.rst:33 -msgid "" -"Please ensure to take a look at :doc:`/channels/email/settings` within the " -"email channel to ensure you have at least one reference that helps Zammad to " -"assign follow-ups correctly." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.login}``" msgstr "" -#: ../settings/ticket.rst:37 -msgid "" -"Disabling this and not setting up any further follow up search will lead to " -"unexpected results!" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Mobile" msgstr "" -#: ../settings/ticket.rst:65 -msgid "" -"Ticket Last Contact Behaviour (default: ``Use the start time of the last " -"customer thread (which may consist of multiple articles).``)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.mobile}``" msgstr "" -#: ../settings/ticket.rst:41 -msgid "" -"This setting changes the way Zammad updates the ``Last Contact`` value of a " -"ticket. This is fairly important for overviews and what you expect upon " -"ticket updates of a customer." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Note" msgstr "" -#: ../settings/ticket.rst:52 -msgid "" -"Use the start time of the last customer thread (which may consist of " -"multiple articles)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.note}``" msgstr "" -#: ../settings/ticket.rst:46 -msgid "" -"If this option is chosen, Zammad will update the last updated value just " -"once if a customer replies. After that, Zammad will wait for an agent to " -"react." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Phone" msgstr "" -#: ../settings/ticket.rst:50 -msgid "" -"This comes in handy if you want to work tickets in the order of their first " -"update. This will not change ticket orders if customers decide to \"bump\" " -"the ticket affected." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.phone}``" msgstr "" -#: ../settings/ticket.rst:57 -msgid "Use the time of the very last customer article." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > VIP" msgstr "" -#: ../settings/ticket.rst:55 -msgid "" -"When setting this option, Zammad will always update the last updated value. " -"This means that if ordering by ``Last Update``, ticket orders will change if " -"customers \"bump\" the ticket." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.vip}``" msgstr "" -#: ../settings/ticket.rst:64 -msgid "Last contact value used on :doc:`/manage/overviews`" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Web" msgstr "" -#: ../settings/ticket.rst:65 -msgid "Last contact value used on :doc:`/manage/trigger`" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.web}``" msgstr "" -#: ../settings/ticket.rst:88 -msgid "" -"Ticket Organization Reassignment (default: ``Update the most recent tickets." -"``)" +#: ../settings/branding.rst:10 +msgid "Product Name" msgstr "" -#: ../settings/ticket.rst:68 +#: ../settings/branding.rst:7 msgid "" -"This setting changes the way Zammad updates the organization field of the " -"tickets whenever the primary organization of a user is changed." -msgstr "" - -#: ../settings/ticket.rst:74 -msgid "Update the most recent tickets." +"Defines the name of the application, shown in the web interface, tabs and " +"title bar of the web browser." msgstr "" -#: ../settings/ticket.rst:72 -msgid "" -"If this option is chosen, Zammad will update the 100 most recent tickets " -"where the user is the ticket customer. The ticket organization field will be " -"automatically set to the new primary organization of the user." +#: ../settings/branding.rst:10 +msgid "Default value: ``Zammad Helpdesk``" msgstr "" -#: ../settings/ticket.rst:88 -msgid "Do not update any tickets." +#: ../settings/branding.rst:13 +msgid "Will be shown in the app and is included in email footers." msgstr "" -#: ../settings/ticket.rst:77 -msgid "" -"When choosing this option, Zammad will not update any tickets when the " -"user's primary organization is changed." +#: ../settings/branding.rst:19 +msgid "Logo" msgstr "" -#: ../settings/ticket.rst:80 -msgid "**Use with care!**" +#: ../settings/branding.rst:16 +msgid "Defines the logo of the application, shown in the login page of Zammad." msgstr "" -#: ../settings/ticket.rst:82 +#: ../settings/branding.rst:18 msgid "" -"Using this option may lead to inconsistencies in the system as the ticket " -"organization may become decoupled from the ticket customer." +"Ensure to hit the \"Submit\" button after uploading the logo. Otherwise your " +"change will not be saved." msgstr "" -#: ../settings/ticket.rst:85 +#: ../settings/branding.rst:22 msgid "" -"However, you may use this option if you wish to maintain :ref:`the shared " -"access ` to the ticket for all organization " -"members of the original organization of the customer." +"Allows to set the default language of the Zammad instance. The here defined " +"locale mostly acts as a fallback for:" msgstr "" -#: ../settings/ticket.rst:110 -msgid "Ticket Number Format (default: ``Increment (SystemID.Counter)``)" +#: ../settings/branding.rst:25 +msgid "user preferences (if Zammad can't detect the users locale)" msgstr "" -#: ../settings/ticket.rst:94 -msgid "" -"This setting defines the way Zammad's ticket number will look. Changing this " -"setting in production will cause follow up detection to fail." +#: ../settings/branding.rst:26 +msgid "CSV output (reporting, time accounting)" msgstr "" -#: ../settings/ticket.rst:102 -msgid "Increment (SystemID.Counter)" +#: ../settings/branding.rst:30 +msgid "Define the timezone of your Zammad installation." msgstr "" -#: ../settings/ticket.rst:98 +#: ../settings/branding.rst:32 msgid "" -"The increment value contains the SystemID (automatically generated during " -"installation) and a increment which counts up with every new Ticket. The " -"increment will automatically get another digit if needed." +"This does not have any effect on timings for your agents or how Zammad " +"stores date and time values." msgstr "" -#: ../settings/ticket.rst:102 -msgid "Examples: ``1010138``, ``1010139``" +#: ../settings/branding.rst:35 +msgid "Changing this value has direct consequences on the following areas:" msgstr "" -#: ../settings/ticket.rst:110 -msgid "Date (Year.Month.Day.SystemID.Counter)" +#: ../settings/branding.rst:37 +msgid ":doc:`/manage/scheduler` tasks" msgstr "" -#: ../settings/ticket.rst:105 -msgid "" -"This version of the ticket number is fairly long. However, because it " -"contains the date of ticket creation, it also allows you to see when the " -"ticket has been created. You may feel familiar with this number format if " -"you've worked with OTRS already." +#: ../settings/branding.rst:38 +msgid "search indexing (and thus reporting)" msgstr "" -#: ../settings/ticket.rst:110 -msgid "Examples: ``201206231010138``, ``201206231010139``" +#: ../settings/branding.rst:40 +msgid "calendar subscriptions" msgstr "" -#: ../settings/ticket.rst:137 -msgid "OPTIONS" +#: ../settings/branding.rst:41 +msgid "browser printing" msgstr "" -#: ../settings/ticket.rst:113 +#: ../settings/branding.rst:43 msgid "" -"The below options allow you to further customize your ticket number. The " -"availability of options differ depending of the chosen ticket number format " -"above." +"Please note that some of above are fallbacks in case Zammad could not detect " +"the agents timezone correctly." msgstr "" -#: ../settings/ticket.rst:122 -msgid "Checksum (default: ``no``)" +#: ../settings/branding.rst:77 +msgid "Pretty Date" msgstr "" -#: ../settings/ticket.rst:118 +#: ../settings/branding.rst:47 msgid "" -"If set to yes, we'll built a checksum to further \"unique\" the ticket " -"number of your system. If you're dealing with many other ticket systems this " -"might help to prevent false positive follow up detection on tickets." +"This setting allows you to define how Zammad should display time stamps " +"within the interface to all users." msgstr "" -#: ../settings/ticket.rst:122 -msgid "This will also add another digit to the ticket number." +#: ../settings/branding.rst:50 +msgid "" +"This does not have any effect on how Zammad returns e.g. time values via " +"variables." msgstr "" -#: ../settings/ticket.rst:137 -msgid "Min. size of Number (default: ``5``)" +#: ../settings/branding.rst:77 +msgid "Choose in between the following options:" msgstr "" -#: ../settings/ticket.rst:125 -msgid "" -"This setting defines the minimum length of your ticket number. If your " -"counter is not yet high enough, Zammad will fill the number with zeros to " -"ensure the wanted length." +#: ../settings/branding.rst:64 +msgid "relative" msgstr "" -#: ../settings/ticket.rst:129 +#: ../settings/branding.rst:55 msgid "" -"Please note that the minimum length is ``3`` (SystemID + at least one digit " -"if below 10). Also, if the length is no longer long enough, the number will " -"automatically get one digit longer. Ticket-Numbers **do not overflow**, thus " -"it's save to keep it at 5 or set it lower if wanted." +"This timestamp shows a relative time span until it switches to a date. Over " +"time, it will change as follows:" msgstr "" -#: ../settings/ticket.rst:135 -msgid "" -"This option is only available if ticket number format is set to " -"``Increment``!" +#: ../settings/branding.rst:58 +msgid "just now" msgstr "" -#: ../settings/ticket.rst:142 -msgid "Auto-Assignment" +#: ../settings/branding.rst:59 +msgid "5 minutes ago" msgstr "" -#: ../settings/ticket.rst:144 -msgid "" -"In a larger Zammad environment, it happens that several agents open the same " -"ticket at the same time. Although collision detection is then effective, the " -"efficiency of processing can be increased by means of the automatic " -"assignment of tickets when a ticket is opened." +#: ../settings/branding.rst:60 +msgid "3 days 1 hour ago" msgstr "" -#: ../settings/ticket.rst:149 -msgid "" -"The automatic assignment of tickets can be activated and configured in the " -"admin area under Settings > Ticket > Auto Assignment." +#: ../settings/branding.rst:61 +msgid "``03/04/2022``" msgstr "" -#: ../settings/ticket.rst:152 -msgid "" -"The auto assignment only works if the ticket has no owner yet. By default, " -"the agent can always reset the ticket owner to ``-`` if needed." +#: ../settings/branding.rst:63 +msgid "Hovering the timestamp helps, you'll always get a clean timestamp then." msgstr "" -#: ../settings/ticket.rst:155 -msgid "" -"If you want to use this function for only specific tickets, you can " -"configure the conditions accordingly to meet your requirement. By default " -"the condition affects all tickets with the state ``open``." +#: ../settings/branding.rst:71 +msgid "absolute" msgstr "" -#: ../settings/ticket.rst:161 +#: ../settings/branding.rst:67 msgid "" -"If you need to exclude users (e.g. a group leader), you can search and " -"select the desired agents in the ``Exception Users`` list. The search " -"function in this area is only effective, if you have too many agents to " -"display at once to help you with the configuration." +"This timestamp always includes the week day. For one week after creation, " +"the timestamp will not contain the date itself: Thursday 18:35." msgstr "" -#: ../settings/ticket.rst:167 -msgid "Notifications" +#: ../settings/branding.rst:71 +msgid "After a week it will switch to: ``Friday 4. Mar 16:00``." msgstr "" -#: ../settings/ticket.rst:191 -msgid "Default Notifications" +#: ../settings/branding.rst:76 +msgid "timestamp" msgstr "" -#: ../settings/ticket.rst:170 +#: ../settings/branding.rst:74 msgid "" -"This setting allows you to configure the default ticket notifications that " -"will be applied to all new agent users (incl. users who were just assigned " -"agent role). Simply change the notification matrix to desired state and " -"press **Save**." +"This will cause Zammad to show a complete timestamp according to your locale " +"defaults. For English this could be e.g. ``2022/12/03 2:40 pm`` or for " +"German e.g. ``12.03.2022 14:40``." msgstr "" -#: ../settings/ticket.rst:175 -msgid "" -"In case an agent already exists, their ticket notification preferences will " -"be preserved. Optionally, you can also **Apply current defaults to all " -"agents**." +#: ../settings/branding.rst:78 +msgid "Default setting: ``relative``." msgstr "" -#: ../settings/ticket.rst:181 -msgid "" -"**Potential time-consuming action:** Applying default ticket notifications " -"to all agent users may take some time to complete, be patient! The exact " -"time will depend on the size of your system and the number of agents." +#: ../settings/security.rst:2 +msgid "Security" msgstr "" -#: ../settings/ticket.rst:185 +#: ../settings/security.rst:4 msgid "" -"**Active agents only!** When current default ticket notifications are " -"applied, only active agent users are considered. In case an agent is re-" -"activated *after* this action, they will still have the old notification " -"configuration." +"For your overview we split each tab within security settings into its own " +"page:" msgstr "" -#: ../settings/ticket.rst:190 -msgid "" -"In case you want to go back to the initial state of ticket notifications, " -"you can click on **Reset to default** button." +#: ../settings/security/base.rst:2 ../settings/system/base.rst:2 +#: ../settings/ticket.rst:8 +msgid "Base" msgstr "" -#: ../settings/ticket.rst:194 ../settings/ticket.rst:196 -msgid "Duplicate Detection" +#: ../settings/security/base.rst:5 +msgid "New User Accounts" msgstr "" -#: ../settings/ticket.rst:236 ../settings/ticket.rst:238 -msgid "Detect Duplicate Ticket Creation" +#: ../settings/security/base.rst:9 +msgid "" +"Activates the `register as a new customer` function on the login page. If " +"set to ``no`` only administrators or agents can create new accounts manually." msgstr "" -#: ../settings/ticket.rst:197 ../settings/ticket.rst:199 -msgid "" -"This setting turns on the duplicate ticket detection mechanism during ticket " -"creation. If similar tickets are found in the system, a suitable warning " -"will be shown to the user trying to create a ticket." +#: ../settings/security/base.rst:13 ../settings/security/base.rst:38 +#: ../settings/security/base.rst:66 +msgid "Default setting: ``yes``" msgstr "" -#: ../settings/ticket.rst:204 ../settings/ticket.rst:206 -msgid "A Sample Duplicate Ticket Warning" +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"New User Accounts\" setting" msgstr "" -#: ../settings/ticket.rst:206 ../settings/ticket.rst:208 +#: ../settings/security/base.rst:22 msgid "" -"You can choose which ticket attributes will be matched by selecting them in " -"**Attributes to compare** field. Only if the ticket attribute value provided " -"by the user in the ticket create form is *equal* with the attribute in an " -"existing ticket, the warning will be shown." +"Deactivation of above function **does not** deactivate automatic account " +"creation! This means: If a user writes e.g. an email to Zammad and has no " +"account yet, Zammad will automatically create the account. User accounts are " +"a direct dependency of tickets and thus technically mandatory." msgstr "" -#: ../settings/ticket.rst:211 ../settings/ticket.rst:213 -msgid "**Warning title** and **Warning message** are configurable as well." +#: ../settings/security/base.rst:29 +msgid "Lost Password" msgstr "" -#: ../settings/ticket.rst:213 ../settings/ticket.rst:215 +#: ../settings/security/base.rst:33 msgid "" -"You can limit the detection only to certain user roles. By default, only " -"agents will see the warning." +"Activates the `lost password` function on the login page. If set to ``no`` " +"only administrators may change the user's password - users may update their " +"own password if they're still logged in and they have the required :doc:" +"`permission `." msgstr "" -#: ../settings/ticket.rst:216 ../settings/ticket.rst:218 -msgid "" -"If you don't want to show the matched tickets as part of the warning, you " -"can set **Show matching ticket(s) in the warning** setting to *no*." +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"Lost Password\" setting" msgstr "" -#: ../settings/ticket.rst:219 ../settings/ticket.rst:221 +#: ../settings/security/base.rst:49 msgid "" -"By default, **Permission level for looking up ticket** is set to *User*, " -"which means user permissions will be honored during sarch. The user will " -"see the warning only if tickets they have access to are matched. " -"Alternatively, you can set this setting to *System*, in which case the " -"search will happen within *all* tickets in the system, regardless of user " -"permissions." +"With third party authentications - but especially LDAP - you may want to " +"disable this function. Zammad **will not** change third party login " +"passwords and instead set or change the local password!" msgstr "" -#: ../settings/ticket.rst:225 ../settings/ticket.rst:227 -msgid "**🦺 Safety first!**" +#: ../settings/security/base.rst:56 +msgid "Password Login" msgstr "" -#: ../settings/ticket.rst:227 ../settings/ticket.rst:229 +#: ../settings/security/base.rst:60 msgid "" -"Even if the permission level is set to *System*, the user will not be shown " -"the tickets they don't have access to in the warning, even if they match." +"Activates the username & password login by default and if no third-party " +"login is activated. Disabling password login on the Zammad login page only " +"takes effect if you enable any :doc:`third-party`." msgstr "" -#: ../settings/ticket.rst:231 ../settings/ticket.rst:233 -msgid "" -"However, just the confirmation about the existence of the tickets in the " -"system may be considered an unwanted information disclosure. Use this option " -"carefully!" +#: ../settings/security/base.rst:64 +msgid "See :doc:`third-party` for supported third-party logins." +msgstr "" + +#: ../settings/security/base.rst:0 +msgid "Figure showing de-activated \"Password Login\" setting" msgstr "" -#: ../settings/ticket.rst:235 ../settings/ticket.rst:237 +#: ../settings/security/base.rst:77 msgid "" -"Finally, you can configure between matching within **All tickets** or **Open " -"tickets** only by setting **Match tickets in following states**. Depending " -"on the current ticket state, a ticket may or not be matched." +"To help administrators to overcome \"login issues\", Zammad automatically " +"offers a password request for administrator users. This allows you to adjust " +"Third-Party applications even if the login does no longer work!" msgstr "" -#: ../system/core-workflows.rst:2 -msgid "Core Workflows" +#: ../settings/security/base.rst:84 +msgid "Session Timeout" msgstr "" -#: ../system/core-workflows.rst:4 +#: ../settings/security/base.rst:86 msgid "" -"Core Workflows allow you to adjust object attributes in many ways. For " -"example:" +"All settings below by default are set to ``4 weeks``. Session Timeout " +"defines the life time of a users session. As soon as it's reached, Zammad " +"will automatically log off the session in question." msgstr "" -#: ../system/core-workflows.rst:7 -msgid "show / hide fields" +#: ../settings/security/base.rst:91 +msgid "" +"Zammad takes the highest value set assigned for the user based on the " +"permissions." msgstr "" -#: ../system/core-workflows.rst:8 -msgid "adjust mandatory setting" +#: ../settings/security/base.rst:94 +msgid "``admin``" msgstr "" -#: ../system/core-workflows.rst:9 -msgid "manipulate available options" +#: ../settings/security/base.rst:96 +msgid "``ticket.customer``" msgstr "" -#: ../system/core-workflows.rst:11 -msgid "" -"With this, you can provide exactly the information your users really need!" +#: ../settings/security/base.rst:97 +msgid "``default`` (fallback if user doesn't have above permissions set)" msgstr "" -#: ../system/core-workflows.rst:15 +#: ../settings/security/base.rst:99 msgid "" -"If the pre-defined :doc:`/system/objects` are not enough, please add them " -"beforehand." +"All settings act independently from each other allowing you to disable the " +"timeouts for e.g. admins, but not agents." msgstr "" -#: ../system/core-workflows.rst:17 -msgid "" -"If you experience slow or unreliable field updates, please see :ref:`Core " -"Workflow Ajax Modus `" -msgstr "" +#: ../settings/security/base.rst:115 +#: ../system/integrations/checkmk/api-reference.rst:13 +msgid "Example" +msgstr "Пример" -#: ../system/core-workflows.rst:22 -msgid "" -"This is a very enhanced functionality and can cause unexpected UI behavior. " -"Please ensure to test your use cases after configuration to reduce surprises." +#: ../settings/security/base.rst:107 +msgid "Let's suppose you configured the following session timeouts" msgstr "" -#: ../system/core-workflows.rst:None -msgid "Dialogue for adding a new workflow" +#: ../settings/security/base.rst:104 +msgid "default: 3 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:2 -msgid "Core Workflow Condition Operators" +#: ../settings/security/base.rst:105 +msgid "admin: 2 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:4 -msgid "" -"You might know that there is a separate section for explaining :doc:" -"`condition operators `. Head over there to " -"see a detailed explanation of many conditions and operators." +#: ../settings/security/base.rst:106 +msgid "ticket.agent: 4 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:8 -msgid "" -"Due to differences to other places in Zammad which are also using conditions " -"(e.g. triggers), you can find a dedicated description of operators for core " -"workflows below." +#: ../settings/security/base.rst:107 +msgid "ticket.customer: 1 week" msgstr "" -#: ../system/core-workflows/condition-operators.rst:12 -msgid "" -"Be aware that the availability of the operators depends on the selected " -"attribute and its field type. Some of the operators may only be available " -"for system attributes (e.g. for \"tags\", \"active\")." +#: ../settings/security/base.rst:115 +msgid "This results in the following situations" msgstr "" -#: ../system/core-workflows/condition-operators.rst:20 -msgid "Operator" +#: ../settings/security/base.rst:110 +msgid "a user with ``admin`` permission will have a timeout of 2 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:22 -msgid "after (absolute)" +#: ../settings/security/base.rst:111 +msgid "" +"a user with ``admin`` and ``ticket.agent`` permissions will have a timeout " +"of 2 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:23 -msgid "Matches if a date/time is after a specific point in time." +#: ../settings/security/base.rst:113 +msgid "" +"a user with ``ticket.customer`` permission will have a timeout of 1 week" msgstr "" -#: ../system/core-workflows/condition-operators.rst:24 -msgid "after (relative)" +#: ../settings/security/base.rst:115 +msgid "" +"a user with neither ``admin``, ``ticket.agent`` nor ``ticket.customer`` " +"permissions will have a timeout of 3 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:25 -msgid "Matches if a time span after a specified event has passed." +#: ../settings/security/password.rst:4 +msgid "" +"This section allows you to define password requirements for the local user " +"accounts." msgstr "" -#: ../system/core-workflows/condition-operators.rst:26 -msgid "before (absolute)" +#: ../settings/security/password.rst:9 +msgid "" +"Zammad does **not** allow you to change your LDAP password, instead, it will " +"set a password in its local database which might confuse your users. This " +"might be addressed in the future by `#1169 `_." msgstr "" -#: ../system/core-workflows/condition-operators.rst:27 -msgid "Matches if a date/time is before a specific point in time." +#: ../settings/security/password.rst:14 +msgid "**Exception for admins**" msgstr "" -#: ../system/core-workflows/condition-operators.rst:28 -msgid "before (relative)" +#: ../settings/security/password.rst:16 +msgid "" +"Please note that below password policies *do not* affect administrators " +"setting passwords on user accounts. While this seems strange and not safe we " +"believe that an administrator knowing an user's password is insecure as well." msgstr "" -#: ../system/core-workflows/condition-operators.rst:29 -msgid "Matches if a time span after a specified event has not passed." +#: ../settings/security/password.rst:21 +msgid "The suggested workflow is either:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:30 -msgid "contains" +#: ../settings/security/password.rst:23 +msgid "" +"to use third party logins to not require local passwords at all **- or -**" msgstr "" -#: ../system/core-workflows/condition-operators.rst:31 -msgid "Matches if a specified value is present." +#: ../settings/security/password.rst:25 +msgid "to require your *user to reset the password* upon first login." msgstr "" -#: ../system/core-workflows/condition-operators.rst:33 -msgid "Matches if all of the specified values are present." +#: ../settings/security/password.rst:27 +msgid "" +"This way administrators are not required to set a user's password at all!" msgstr "" -#: ../system/core-workflows/condition-operators.rst:35 -msgid "Matches if none of the specified values are present." +#: ../settings/security/password.rst:31 +msgid "Maximum Failed Logins" msgstr "" -#: ../system/core-workflows/condition-operators.rst:36 -msgid "contains not" +#: ../settings/security/password.rst:33 +msgid "" +"You can choose a value between ``4`` and ``20``. This defines how often a " +"login to a user account may fail until Zammad will lock it. Your users can " +"always use the \"forgot password\" function to change their password and " +"unlock their account." msgstr "" -#: ../system/core-workflows/condition-operators.rst:37 -msgid "Matches if a specified value is not present." +#: ../settings/security/password.rst:38 +msgid "The default value is ``10``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:39 -msgid "Matches if one specified value is present." +#: ../settings/security/password.rst:42 +msgid "Beside changing the user's password, you can also unlock accounts via" msgstr "" -#: ../system/core-workflows/condition-operators.rst:41 -msgid "Matches if one specified value is not present." +#: ../settings/security/password.rst:44 +msgid ":ref:`user management list `" msgstr "" -#: ../system/core-workflows/condition-operators.rst:42 -msgid "does not match regex" +#: ../settings/security/password.rst:45 +msgid ":docs:`console `" msgstr "" -#: ../system/core-workflows/condition-operators.rst:43 -msgid "Matches if content doesn't fit to regex rule." +#: ../settings/security/password.rst:46 +msgid ":docs:`API `" msgstr "" -#: ../system/core-workflows/condition-operators.rst:44 -msgid "ends with" +#: ../settings/security/password.rst:50 +msgid "Failed logins via LDAP no longer lock accounts." msgstr "" -#: ../system/core-workflows/condition-operators.rst:45 -msgid "Matches if content ends with specified value." +#: ../settings/security/password.rst:53 +msgid "2 Lower Case And 2 Upper Case Characters" msgstr "" -#: ../system/core-workflows/condition-operators.rst:46 -msgid "ends with one of" +#: ../settings/security/password.rst:55 +msgid "" +"You can add complexity to passwords by enforcing at least 2 upper and lower " +"case characters." msgstr "" -#: ../system/core-workflows/condition-operators.rst:47 -msgid "Matches if content ends with one of the specified values." +#: ../settings/security/password.rst:58 ../settings/security/password.rst:83 +msgid "The default value is ``no``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:48 -msgid "from (relative)" +#: ../settings/security/password.rst:62 +msgid "Minimum Length" msgstr "" -#: ../system/core-workflows/condition-operators.rst:49 -msgid "Matches if date/time is after a period of time after an event." +#: ../settings/security/password.rst:64 +msgid "" +"This defines the minimum password length required for users to provide (from " +"``4`` to ``20``)." msgstr "" -#: ../system/core-workflows/condition-operators.rst:51 -msgid "Matches if content is equal to a specified value." +#: ../settings/security/password.rst:67 +msgid "The default value is ``6``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:52 -msgid "is any of" +#: ../settings/security/password.rst:71 +msgid "Digit Required" msgstr "" -#: ../system/core-workflows/condition-operators.rst:53 -msgid "Matches if content is equal to any of specified values." +#: ../settings/security/password.rst:73 +msgid "This enforces your users to use at least one digit within the password." msgstr "" -#: ../system/core-workflows/condition-operators.rst:54 -msgid "is modified" +#: ../settings/security/password.rst:75 +msgid "The default value is ``yes``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:55 -msgid "Matches if content is modified." +#: ../settings/security/password.rst:78 +msgid "Special Character Required" msgstr "" -#: ../system/core-workflows/condition-operators.rst:57 -#: ../system/core-workflows/condition-operators.rst:61 -msgid "True from the moment of changing content until form submit." +#: ../settings/security/password.rst:80 +msgid "" +"This setting allows you to improve your password quality even more by " +"enforcing the password to contain at least one special character." msgstr "" -#: ../system/core-workflows/condition-operators.rst:58 -msgid "is modified to" +#: ../settings/security/ssl-certificates.rst:2 +msgid "SSL Certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:59 -msgid "Matches if content is modified to a specific value." +#: ../settings/security/ssl-certificates.rst:7 +msgid "" +"Zammad offers the possibility to upload custom certificates and custom " +"Certificate Authority (CA) certificates. This can be useful if you want to " +"connect Zammad the secure way to other systems which are using custom " +"certificates." msgstr "" -#: ../system/core-workflows/condition-operators.rst:62 -msgid "is none of" +#: ../settings/security/ssl-certificates.rst:12 +msgid "" +"An example usecase might be: You have an internal LDAP server that is not " +"accessible from the internet, and you want a SSL-encrypted connection, using " +"a custom certificate." msgstr "" -#: ../system/core-workflows/condition-operators.rst:63 -msgid "Matches if content is none of any specified values." +#: ../settings/security/ssl-certificates.rst:19 +msgid "" +"You should have an existing custom certificate file and/or a custom CA " +"certificate file, which you want to add to Zammad. As filetype ``.crt`` is " +"supported and the certificate format has to be PEM (Base64 ASCII)." msgstr "" -#: ../system/core-workflows/condition-operators.rst:65 -msgid "Matches if content is not equal to a specified value." +#: ../settings/security/ssl-certificates.rst:25 +msgid "" +"When you import a custom CA certificate, all certificates generated with " +"this are trusted. This can be useful if you have more than one system/" +"certificate you want to connect to and the certificates are issued from the " +"same custom CA." msgstr "" -#: ../system/core-workflows/condition-operators.rst:67 -msgid "Matches if content is present." +#: ../settings/security/ssl-certificates.rst:31 +msgid "Add a Certificate" msgstr "" -#: ../system/core-workflows/condition-operators.rst:68 -msgid "just changed" +#: ../settings/security/ssl-certificates.rst:33 +msgid "" +"To add a custom certificate or a custom CA certificate, head over to the " +"Admin panel > Settings > Security > SSL Certificates. Here you can find a " +"\"Add SSL Certificate\" button. In the dialog you can either select a " +"certificate file or paste the content of the certificate:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:69 -msgid "Matches if content has changed." +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate adding dialog" msgstr "" -#: ../system/core-workflows/condition-operators.rst:71 -#: ../system/core-workflows/condition-operators.rst:75 +#: ../settings/security/ssl-certificates.rst:43 msgid "" -"Only true for the moment of changing content until next form field action/" -"click." +"After selecting a file or pasting the content of the certificate, click on " +"the \"Add\" button to finally upload it to Zammad. Then, the certificates " +"are immediately effective, no restart or similar required." msgstr "" -#: ../system/core-workflows/condition-operators.rst:72 -msgid "just changed to" +#: ../settings/security/ssl-certificates.rst:49 +msgid "" +"Please note that only single certificate files are supported. That means if " +"you want to import a certificate / CA certificate, it must contain **only " +"one** certificate." msgstr "" -#: ../system/core-workflows/condition-operators.rst:73 -msgid "Matches if content has changed to a specified value." +#: ../settings/security/ssl-certificates.rst:54 +msgid "Certificate Overview" msgstr "" -#: ../system/core-workflows/condition-operators.rst:76 -msgid "matches regex" +#: ../settings/security/ssl-certificates.rst:56 +msgid "" +"After you added a certificate, you can see a table with information for each " +"added certificate:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:77 -msgid "Matches if value fits to regex rule." -msgstr "" - -#: ../system/core-workflows/condition-operators.rst:79 -msgid "Matches if no content is present." +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing table of added certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:80 -msgid "starts with" +#: ../settings/security/ssl-certificates.rst:64 +msgid "" +"Here you can download the certificate or delete it, if you don't need it " +"anymore." msgstr "" -#: ../system/core-workflows/condition-operators.rst:81 -msgid "Matches if content starts with specified value." +#: ../settings/security/ssl-certificates.rst:68 +msgid "Deleting Certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:82 -msgid "starts with one of" +#: ../settings/security/ssl-certificates.rst:70 +msgid "" +"If you want to delete a specific certificate, you can do it by clicking on " +"the menu in the actions column and selecting delete:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:83 -msgid "Matches if content starts with one of the specified values." +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate deletion button" msgstr "" -#: ../system/core-workflows/condition-operators.rst:84 -msgid "till (relative)" +#: ../settings/security/ssl-certificates.rst:79 +msgid "Downloading Certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:85 -msgid "Matches if date/time is before a period of time before an event." +#: ../settings/security/ssl-certificates.rst:81 +msgid "" +"If you want to download your certificates, you can do this as well via " +"corresponding action buttons." msgstr "" -#: ../system/core-workflows/condition-operators.rst:86 -msgid "today" +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate download button" msgstr "" -#: ../system/core-workflows/condition-operators.rst:87 -msgid "Matches if date/time is today." +#: ../settings/security/third-party.rst:13 +msgid "Login Providers" msgstr "" -#: ../system/core-workflows/condition-operators.rst:88 -msgid "within last (relative)" +#: ../settings/security/third-party.rst:2 +msgid "Third-Party Applications" msgstr "" -#: ../system/core-workflows/condition-operators.rst:89 +#: ../settings/security/third-party.rst:4 msgid "" -"Matches if date/time content is within specified period of time before now." +"Third party authentication is a great way to help your users to login to " +"Zammad more easily. If the account is yet unknown, Zammad will create a new " +"user automatically, without the user needed to interact (e.g. type in his " +"name). Another big advantage of this feature is that your user doesn't need " +"to remember another password." msgstr "" -#: ../system/core-workflows/condition-operators.rst:91 -msgid "within next (relative)" +#: ../settings/security/third-party.rst:10 +msgid "" +"You can deactivate logging in via :ref:`security_password_login` if any of " +"the mentioned authentication providers are enabled in your instance." msgstr "" -#: ../system/core-workflows/condition-operators.rst:92 +#: ../settings/security/third-party.rst:27 msgid "" -"Matches if date/time content is within specified period of time after now." +"We're currently missing documentation for the following login providers:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:2 -msgid "How do they work?" +#: ../settings/security/third-party.rst:29 +msgid "LinkedIn" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:4 -msgid "" -"Core Workflows are executed according to their priority. If two workflows " -"have the same priority, they are executed in alphabetical order based on " -"their **name**." +#: ../settings/security/third-party.rst:30 +msgid "Weibo" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:8 -msgid "" -"Because of the way Core Workflows work, all changes to attributes are " -"checked with the application server - please see :doc:`limitations` for " -"possible issues." +#: ../settings/security/third-party.rst:35 +msgid "Automatic Account Link on Initial Logon" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:12 +#: ../settings/security/third-party.rst:37 msgid "" -"Below we're talking about settings that are important and not self-" -"explanatory." +"In general there's two possible options for Zammad on how to deal with " +"already known users as they try to authenticate against a third-party " +"application. By default, Zammad will not automatically link \"unknown\" " +"authentication providers to existing accounts." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:17 +#: ../settings/security/third-party.rst:42 msgid "" -"Choose the object context you want to run the workflow in. This will decide " -"on your available attributes and actions." -msgstr "" - -#: ../system/core-workflows/how-do-they-work.rst:20 -msgid "Ticket objects also have access to the ticket customer." +"This means that the user has to manually link authentication providers to " +"their accounts (for more about this :user-docs:`consult the user " +"documentation `)." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:25 +#: ../settings/security/third-party.rst:46 msgid "" -"Choose in which situation the workflow is applied. Contexts can be combined " -"to avoid duplicate workflows." +"Sometimes this doesn't come in handy as this also means you'll receive error " +"messages about \"email address being in use already\" for (yet) unknown " +"third-party authentication methods." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:30 -msgid "Creation mask" +#: ../settings/security/third-party.rst:50 +msgid "" +"If you want to allow your users to always be able to log in, no matter what, " +"you may want to enable ``Automatic account link on initial logon``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:29 +#: ../settings/security/third-party.rst:None msgid "" -"If selected, your conditions and actions will affect all applicable creation " -"masks." +"Screenshot highlighting the \"Automatic account link on initial logon\"\n" +"setting" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:34 -msgid "Edit mask" +#: ../settings/security/third-party.rst:60 +msgid "Automatic Account Linking Notification" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:33 +#: ../settings/security/third-party.rst:64 msgid "" -"If selected, your conditions and actions will affect all applicable edit " -"masks." +"To improve security and your users awareness, you can enable Zammad to " +"notify your users when a new third-party application has been linked to " +"their account." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:39 +#: ../settings/security/third-party.rst:68 msgid "" -"Zammad differentiates between selected and saved conditions. These can be " -"combined wherever needed." +"This notification is sent out once per third-party application. Zammad does " +"also mention the method used, e.g.: ``Microsoft``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:42 -msgid "**⚠️ Restrict workflows to specific roles if needed!**" +#: ../settings/security/third-party.rst:71 +msgid "By default this setting is not active (set to ``no``)." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:44 +#: ../settings/security/third-party.rst:0 msgid "" -"By default and unless configured in conditions, workflow rules are executed " -"for **all roles**. This also affects your customers!" +"Screenshot showing sample notification mail after initial\n" +"third-party linking" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:50 -msgid "Selected Conditions" +#: ../settings/security/third-party.rst:85 +msgid "" +"This notification is only sent if the account in question already exists. If " +"the login via the third-party also creates the missing account, the " +"notification will be skipped." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:48 -msgid "" -"These conditions are based on form values and match if an appropriate " -"selection is made (e.g. choosing another group in the ticket without " -"saving). This applies for drafts (active selection) and currently saved " -"values." +#: ../settings/security/third-party.rst:89 +msgid "This means it only affects:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:64 -msgid "Saved Conditions" +#: ../settings/security/third-party.rst:91 +msgid "manual account linking within the third-party page of the users profile" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:53 +#: ../settings/security/third-party.rst:92 msgid "" -"These conditions only match if the selected values are stored in the " -"database. It ignores the current value or selection of the field, as long as " -"the changes are not saved (e.g. performing field operations for an existing " -"ticket, which is viewed/opened by an agent)." +"logging into an existing local account by utilizing the *automatic account " +"link on initial logon* functionality" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:60 +#: ../settings/security/third-party.rst:None msgid "" -"Keep in mind that the value has to be available in the situation where you " -"need it. Otherwise the condition won't match." +"Screenshot showing the \"automatic account linking notification\"\n" +"setting" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:63 -msgid "" -"Example: you can't perform any actions with *saved condition* on a ticket in " -"creation, because there are no saved values at that time." +#: ../settings/security/third-party.rst:100 +msgid "No User Creation on Logon" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:66 +#: ../settings/security/third-party.rst:102 msgid "" -"You can find a description of the condition operators for core workflows :" -"doc:`here `." +"By default, Zammad will create a new user account if the user logs in via a " +"third-party application and the account doesn't exist yet." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:72 +#: ../settings/security/third-party.rst:105 msgid "" -"Which actions should we run on the relevant fields? The possible actions " -"depend on the object type. However, usually you can at least change the " -"visibility and whether the field is mandatory." +"If you want to prevent Zammad from creating new accounts on logon, you can " +"disable this feature by setting ``No user creation on logon`` to ``yes``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:76 -msgid "Be aware that actions are not available for **related** context." +#: ../settings/security/third-party.rst:None +msgid "Screenshot showing the \"no user creation on logon\" setting" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:78 +#: ../settings/security/third-party/facebook.rst:4 msgid "" -"**Example:** Let's assume you are working in the ticket context. While you " -"can have customer *conditions*, you *can't adjust* objects with actions in " -"that scope. That's because this wouldn't have any impact on the ticket " -"dialog. Of course all ticket attributes (state, owner, ...) are available." +"It is possible to create a quick login for your helpdesk via Facebook To do " +"so, you need to follow these steps:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:84 +#: ../settings/security/third-party/facebook.rst:9 +msgid "Register Facebook App" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:11 msgid "" -"Please also have a look at our :doc:`limitations` to be safe from surprises." +"Visit [https://developers.facebook.com/apps/] and click on \"Add a new App\"" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:88 -msgid "Available Operators" +#: ../settings/security/third-party/facebook.rst:None +msgid "initial page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:90 -msgid "The availability of operators depends on the object type and scope." +#: ../settings/security/third-party/facebook.rst:17 +msgid "After that enter the app settings" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:94 -msgid "" -"Please note that actions may or may not restrict API based access to " -"attributes. We're displaying the following icons for your overview to " -"understand these limits better:" +#: ../settings/security/third-party/facebook.rst:None +msgid "Create App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:0 -msgid "|api| This icon indicates the action affects the API." +#: ../settings/security/third-party/facebook.rst:22 +msgid "Navigate to \"Settings\" and fill in this infromation" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:163 -msgid "api" +#: ../settings/security/third-party/facebook.rst:None +msgid "App Settings" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:0 -msgid "|ui| This icon indicates the action only affects the web interface." +#: ../settings/security/third-party/facebook.rst:27 +msgid "Navigate to app review and Check \"Make [appname] public?\"" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:167 -msgid "ui" +#: ../settings/security/third-party/facebook.rst:None +msgid "App Review" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:102 -msgid "show |ui|" +#: ../settings/security/third-party/facebook.rst:35 +msgid "Configure Zammad as Facebook App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:102 -msgid "Display the chosen field. Allows setting of values." -msgstr "" - -#: ../system/core-workflows/how-do-they-work.rst:109 -msgid "hide |ui|" +#: ../settings/security/third-party/facebook.rst:37 +msgid "" +"Navigate to \"Admin -> Security -> Third Party Applications\" and enter the " +"App ID and the App Secret. You can find this Key in the Dashbard of your " +"Facebok app." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:105 -msgid "" -"Hide the chosen field. However, it technically still allows setting the " -"field." +#: ../settings/security/third-party/facebook.rst:None +msgid "Zammad Configuration" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:108 +#: ../settings/security/third-party/facebook.rst:44 +#: ../settings/security/third-party/github.rst:43 +#: ../settings/security/third-party/gitlab.rst:46 msgid "" -"Please note that the field is **not** gone and still contains an existing " -"value (if set)! Consider *remove* instead, if you want this field to be gone." +"Now you can link accounts via \"Avatar -> Profile -> Link Accounts\" or " +"login via Zammad login page." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:112 -msgid "remove |ui|" +#: ../settings/security/third-party/github.rst:2 +#: ../system/integrations/github.rst:2 +msgid "GitHub" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:112 -msgid "Entirely removes the field. The field value will not be evaluated." +#: ../settings/security/third-party/github.rst:4 +msgid "" +"It is possible to create a quick login for your helpdesk via GitHub. To " +"activate the quick login you need to enable OAuth for GitHub." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:115 -msgid "set mandatory |ui| |api|" +#: ../settings/security/third-party/github.rst:8 +msgid "Register GitHub App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:115 -msgid "Sets the field to mandatory." +#: ../settings/security/third-party/github.rst:10 +msgid "" +"Visit https://www.github.com/settings/applications/new and enter the app " +"settings. As callback URL enter \"https://zammad_host/auth/github/callback\" " +"where zammad_host has to be replaced with your Zammad FQDN" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:118 -msgid "set optional |ui| |api|" +#: ../settings/security/third-party/github.rst:None +msgid "Register OAuth app on www.github.com" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:118 -msgid "Sets the field to optional." +#: ../settings/security/third-party/github.rst:19 +msgid "Configure Zammad as GitHub App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:124 -msgid "add option |ui| |api|" +#: ../settings/security/third-party/github.rst:21 +msgid "" +"Enter the \"APP ID\" and the \"APP SECRET\" from the GitHub OAUTH " +"Applications Dashboard" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:121 -msgid "Allows adding options to tree selects or selects." +#: ../settings/security/third-party/github.rst:None +msgid "GitHub config in Zammad admin interface" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:123 +#: ../settings/security/third-party/github.rst:28 msgid "" -"You have to use the \"remove option\" before performing this action. It " -"allows you to use *existing* configured values." +"After you configured the GitHub credentials and activated the login method, " +"you should see a new icon on the login page." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:128 -msgid "remove option |ui| |api|" +#: ../settings/security/third-party/github.rst:None +msgid "GitHub logo on login page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:127 +#: ../settings/security/third-party/github.rst:34 msgid "" -"Allows removing options from tree selects or selects. It allows you to use " -"*existing* configured values." +"If you click on the icon you will be redirected to GitHub and see something " +"similar to this:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:134 -msgid "set fixed to |ui| |api|" +#: ../settings/security/third-party/github.rst:None +msgid "GitHub oauth page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:131 -msgid "Reduces the available options by your selection." +#: ../settings/security/third-party/github.rst:40 +#: ../settings/security/third-party/gitlab.rst:42 +msgid "" +"When you grant the access you will be redirected to your Zammad instance and " +"logged in as a customer." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:133 -msgid "" -"This reduces your workflows in terms of *add option* and *remove option*." +#: ../settings/security/third-party/gitlab.rst:2 +msgid "Gitlab" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:137 -msgid "fill in |ui|" +#: ../settings/security/third-party/gitlab.rst:4 +msgid "" +"It is possible to create a quick login for your helpdesk via Gitlab. To " +"activate the quick login you need to enable OAuth for Gitlab." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:137 -msgid "Allows filling in of string and integer fields with your values." +#: ../settings/security/third-party/gitlab.rst:8 +msgid "Register Gitlab App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:141 -msgid "fill in empty |ui|" +#: ../settings/security/third-party/gitlab.rst:10 +msgid "To register an app in Gitlab open your profile and select applications." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:140 +#: ../settings/security/third-party/gitlab.rst:12 msgid "" -"Allows filling in of string and integer fields with your values **if the " -"field is empty**." +"As callback URL enter \"https://zammad-fqdn/auth/gitlab/callback\" where " +"zammad-fqdn has to be replaced with your Zammad FQDN" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:144 -msgid "select |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Register OAuth app on gitlab instance" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:144 -msgid "Select a specific value within a select, tree select or boolean field." +#: ../settings/security/third-party/gitlab.rst:18 +msgid "Just select *read_user* under scopes as in the screenshot and save it." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:153 -msgid "auto select |ui|" +#: ../settings/security/third-party/gitlab.rst:21 +msgid "Configure Zammad as Gitlab App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:147 -msgid "Helps users with tree select and select fields:" +#: ../settings/security/third-party/gitlab.rst:23 +msgid "" +"Enter the \"APP ID\" and the \"APP SECRET\" from the Gitlab OAUTH " +"Applications Dashboard and your Gitlab-URL in the \"SITE\" field." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:149 -msgid "" -"If the field has only one option available for selection and no value yet, " -"the value will be automatically set." +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab config in Zammad admin interface" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:152 +#: ../settings/security/third-party/gitlab.rst:30 msgid "" -"This option only works if you have one value and doesn't work if there is " -"more than one option available." +"After you configured the Gitlab credentials and activated the login method, " +"you should see a new icon on the login page." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:157 -msgid "set readonly |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab logo on login page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:156 +#: ../settings/security/third-party/gitlab.rst:36 msgid "" -"Allows you to display an attribute as read only (which means no changes are " -"possible)." +"If you click on the icon you will be redirected to Gitlab and see something " +"similar to this:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:161 -msgid "unset readonly |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab oauth page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:160 +#: ../settings/security/third-party/google.rst:4 msgid "" -"In case a workflow set the field in question to read only, you can undo this " -"with option above." +"With some easy and fast steps, you can enable Zammad to authenticate your " +"users via Google." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:172 -msgid "Stop after match" +#: ../settings/security/third-party/google.rst:8 +msgid "Register a Google App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:174 +#: ../settings/security/third-party/google.rst:10 msgid "" -"Here you can decide if other workflows are executed after the current one." +"First of all, we need to create a new project - you can skip this step if " +"you already have one." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:176 +#: ../settings/security/third-party/google.rst:15 msgid "" -"If set to ``no`` (default), further workflows will be executed if they match " -"the condition. In this case, it is possible that your actions from the " -"current workflow can be overwritten by another workflow." +"Use this link to create a new project: https://console.cloud.google.com/" +"projectcreate" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:180 +#: ../settings/security/third-party/google.rst:18 msgid "" -"If set to ``yes``, no further worflows will be executed after the current " -"one." +"Now expand the menu, expand \"APIs & Services\" and select \"Credentials\". " +"Go to the tab \"OAuth consent screen\" first and ensure to fill in the " +"requested information - without doing so you can't create credentials!" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:184 -msgid "Priority" -msgstr "Приоритет" +#: ../settings/security/third-party/google.rst:None +msgid "Creating a consent screen" +msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:186 +#: ../settings/security/third-party/google.rst:25 msgid "" -"You can define the sequence, in which the workflows are executed. The " -"default value is ``500``." +"After filling in and saving the consent screen information, you can go to " +"the \"Credentials\" tab and create new \"OAuth client ID\"-Credentials." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:189 +#: ../settings/security/third-party/google.rst:28 msgid "" -"The workflows are executed in ascending order by their priority. That means " -"lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." +"Fill in the necessary information as follows and replace ``zammad_host`` " +"with your FQDN:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:2 -#, fuzzy -msgid "Learn by Example" -msgstr "Пример" +#: ../settings/security/third-party/google.rst:31 +msgid "**Application type** ``[x] Web application``" +msgstr "" -#: ../system/core-workflows/learn-by-example.rst:4 -msgid "" -"This page provides some basic examples for Core Workflows. Of course you can " -"build much more complex workflows if needed." +#: ../settings/security/third-party/google.rst:34 +msgid "**Authorized JavaScript origins** ``https://zammad_host/``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:7 +#: ../settings/security/third-party/google.rst:37 msgid "" -"To learn about Core Workflows in detail, first go to :doc:`how-do-they-work`." +"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" +"callback``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:10 -msgid "Group Based Examples" +#: ../settings/security/third-party/google.rst:None +msgid "Adding a new OAuth client ID" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:12 +#: ../settings/security/third-party/google.rst:43 msgid "" -"All following workflows have the same base configurations. The workflow may " -"not use them all." +"After creating the credentials, go to your Zammad installation and navigate " +"to \"Admin > Security > Third Party Applications\" > Google. Enter your " +"Client ID and Client secret here." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:15 -msgid "Groups:" +#: ../settings/security/third-party/google.rst:None +msgid "Zammad" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:20 -msgid "Attributes:" +#: ../settings/security/third-party/google.rst:50 +msgid "After submitting, the login via Google can be used." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:22 -msgid "Category (Single tree selection field, not mandatory, agents only)" +#: ../settings/security/third-party/microsoft.rst:2 +msgid "Microsoft" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:23 +#: ../settings/security/third-party/microsoft.rst:4 msgid "" -"Approved (Boolean field, not mandatory, not shown, ``false`` as default)" +"Zammad's Microsoft connection allows your users with Microsoft accounts to " +"login. This works for Azure users as well and can be an alternative to :doc:" +"`/system/integrations/ldap/index`." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:24 -msgid "Operating System (Text field, not mandatory, not shown)" +#: ../settings/security/third-party/microsoft.rst:10 +msgid "" +"This documentation part does not cover our :doc:`📧 Microsoft 365 email " +"channel `." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:25 -msgid "Software used (Single selection field, not mandatory, not shown)" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screenshot showing Microsoft login button on Zammad login screen." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:68 -msgid "Group specific values and fields" +#: ../settings/security/third-party/microsoft.rst:30 +#: ../settings/security/third-party/microsoft.rst:53 +msgid "Supported account types:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:28 +#: ../settings/security/third-party/microsoft.rst:22 msgid "" -"This workflow set depends on the category field. It reduces the available " -"set of values based on the group selected." +"Please note that Zammad only supports these account types (App dependent):" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:33 -msgid "Workflow 2nd Level group" +#: ../settings/security/third-party/microsoft.rst:35 +msgid "Avatars of signing in users:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:35 +#: ../settings/security/third-party/microsoft.rst:33 msgid "" -"This reduces the category options to ``2nd Level/*``, ``Internal/*`` and " -"``Others``. It also sets further required fields to mandatory and visible." -msgstr "" - -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for 2nd level" +"Zammad currently ignores user avatars. If the user is registered with e.g. " +"Gravatar, Zammad will fetch the avatar from there if enabled. See :doc:" +"`Zammad Image Service ` for more." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:43 -msgid "Workflow Support group" +#: ../settings/security/third-party/microsoft.rst:38 +msgid "Step 1 - Register a Microsoft App for Zammad" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:45 +#: ../settings/security/third-party/microsoft.rst:40 msgid "" -"This reduces the category options to ``Support/*``, ``Internal/*`` and " -"``Others``. It also sets further required fields to visible." -msgstr "" - -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for support" +"Login to the `Microsoft Azure Portal `_ and " +"navigate to App registrations to create a new app. Provide the requested " +"information as follows and register your app." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:53 -msgid "Workflow Sales group" +#: ../settings/security/third-party/microsoft.rst:46 +msgid "Name:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:55 +#: ../settings/security/third-party/microsoft.rst:45 msgid "" -"This reduces the category options to ``Sales/*``, ``Internal/*`` and " -"``Others``." +"Any meaningful name fitting, this name will be displayed to users trying to " +"authenticate with this app." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for sales" +#: ../settings/security/third-party/microsoft.rst:49 +msgid "Choose one of the above mentioned account types (see Limitations)." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:68 -#: ../system/integrations/slack.rst:88 -msgid "The Result" +#: ../settings/security/third-party/microsoft.rst:51 +msgid "" +"The correct account type depends on your use case. If you want to use the " +"authentication internal only, choose the first option. If you're unsure, use " +"the \"Help me choose...\" link." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:63 -msgid "" -"This is what the agent would experience with the above workflows in place." +#: ../settings/security/third-party/microsoft.rst:58 +msgid "Redirect URI (optional):" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 +#: ../settings/security/third-party/microsoft.rst:56 msgid "" -"Workflow shows objects and limits options based on selections on the group" +"Select web and provide your callback URL. The callback URL looks like this: " +"``https://zammad.domain.tld/auth/microsoft_office365/callback``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:90 -msgid "Approval process" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to register a Microsoft app" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:71 -msgid "" -"In this case ``approved`` is visible to agents by default. For this " -"workflow, an additional role ``Approval person`` is required (no further " -"permissions)." +#: ../settings/security/third-party/microsoft.rst:71 +msgid "Within **API permissions** add the following permissions:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that restricts an approval attribute to specific roles" +#: ../settings/security/third-party/microsoft.rst:69 +msgid "``User.Read``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:81 -msgid "" -"This workflow may work best in combination with a :doc:`trigger ` but technically, this is not required." +#: ../settings/security/third-party/microsoft.rst:71 +msgid "Contacts" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:84 -msgid "" -"Select fields may be a better approach because they allow more values than " -"just a simple ``true`` or ``false``." +#: ../settings/security/third-party/microsoft.rst:71 +msgid "``Contacts.Read``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 +#: ../settings/security/third-party/microsoft.rst:73 msgid "" -"Workflow fixes possible values of \"Approved ?\" to a specific selection " -"depending on the users role" +"You can find these permissions within *Microsoft Graph → Delegated " +"permissions*." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:103 -msgid "State dependent mandatory fields" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to add required API permissions" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:93 +#: ../settings/security/third-party/microsoft.rst:80 msgid "" -"This workflow sets ``Category`` to mandatory if the agent wants to set the " -"states ``closed`` or ``pending close`` to enforce categorization." +"Within **Certificates & secrets** create a new client secret. Note down the " +"returned secret **value** for later. **Do not** use the secret ID!" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that sets fields to mandatory on specific states" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to create a new app secret" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 +#: ../settings/security/third-party/microsoft.rst:88 msgid "" -"Workflow sets category field to mandatory upon choosing closed or pending " -"close as state" +"From **Overview** copy your apps *Application (client) ID*. If you're using " +"a single tenant app, please also copy *Directory (tenant) ID*. You now have " +"all required information for Zammad." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:106 -msgid "Manual Ticket Handover Process" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to retreive application client and tenant IDs" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:108 -msgid "This example covers the handover of a ticket from one agent to another:" +#: ../settings/security/third-party/microsoft.rst:98 +msgid "Step 2 - Add App Credentials to Zammad" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:110 +#: ../settings/security/third-party/microsoft.rst:100 msgid "" -"When the ticket owner is modified, a new text field (\"Handover\") shows up " -"for a comment" +"Navigate to Security > Third-party Applications (Tab) within Zammad's admin " +"settings. Scroll down to the section *Authentication via Microsoft* and fill " +"in the required information." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:112 -msgid "" -"This may only be visible when the owner is changed, therefore it has to be " -"hidden in general" +#: ../settings/security/third-party/microsoft.rst:105 +msgid "App ID:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:114 -msgid "The input in this handover text field is mandatory" +#: ../settings/security/third-party/microsoft.rst:105 +msgid "This is your *Application (client) ID*." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:115 -msgid "" -"After submitting changes, the value of the handover field must be added as " -"an note to the ticket (via trigger)" +#: ../settings/security/third-party/microsoft.rst:108 +msgid "App secret:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:121 -msgid "Hiding handover field" +#: ../settings/security/third-party/microsoft.rst:108 +msgid "This is your *client secret* (value)." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Hiding the handover field in core workflows" +#: ../settings/security/third-party/microsoft.rst:113 +msgid "App Tenant ID:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:126 -msgid "Showing handover field and setting it to mandatory" +#: ../settings/security/third-party/microsoft.rst:111 +msgid "" +"**optional** only required for apps that use account type *Accounts in this " +"organizational directory only (Default Directory only - Single tenant).*" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Showing the handover field and set it as mandatory" +#: ../settings/security/third-party/microsoft.rst:115 +msgid "" +"Apply your settings by pressing submit and activate *Authentication via " +"Microsoft*." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:131 -msgid "Trigger writing handover input to a new article" +#: ../settings/security/third-party/microsoft.rst:None +msgid "" +"Screencast showing how to add app credentials and activating the\n" +"authentication method" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Write handover content to a new article" +#: ../settings/security/third-party/saml.rst:2 +msgid "SAML" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:133 +#: ../settings/security/third-party/saml.rst:4 msgid "" -"As a result, the ticket includes an article of the type note which includes " -"the predefined text and the handover comment." +"Connect your SAML (Security Assertion Markup Language) identity provider as " +"a single sign-on (SSO) method." msgstr "" -#: ../system/core-workflows/limitations.rst:6 -msgid "Core Workflows do not replace Triggers" +#: ../settings/security/third-party/saml.rst:7 +msgid "" +"SAML is an open standard for SSO authentication (among other things). Sign-" +"ins are shared across multiple **service providers** and managed by a " +"central **identity provider** (IdP)." msgstr "" -#: ../system/core-workflows/limitations.rst:5 +#: ../settings/security/third-party/saml.rst:11 msgid "" -"Workflows manipulate the behavior of fields. However, they do not set values " -"in fields because of actions." +"In this case, the service provider is Zammad, and the IdP is a software " +"service that you either host or subscribe to (*e.g.,* `Keycloak `_, `Redhat SSO Server `_, `ADFS `_, or `Okta `_)." msgstr "" -#: ../system/core-workflows/limitations.rst:16 -msgid "API calls are only partly affected" +#: ../settings/security/third-party/saml.rst:18 +msgid "" +"This guide assumes you are already using SAML within your organization (i." +"e., that your IdP is fully set up)." msgstr "" -#: ../system/core-workflows/limitations.rst:9 +#: ../settings/security/third-party/saml.rst:21 msgid "" -"Some options affect UI only and thus do not restrict responses and calls." +"Please note: Our instructions are based on connecting Zammad with Keycloak." msgstr "" -#: ../system/core-workflows/limitations.rst:11 -msgid "This affects the following actions:" +#: ../settings/security/third-party/saml.rst:25 +msgid "Step 1: Configure Your IdP" msgstr "" -#: ../system/core-workflows/limitations.rst:13 -msgid "select" +#: ../settings/security/third-party/saml.rst:28 +msgid "Add Zammad as a Client/App" msgstr "" -#: ../system/core-workflows/limitations.rst:14 -msgid "auto select" +#: ../settings/security/third-party/saml.rst:30 +msgid "" +"Import Zammad into your IdP using the XML configuration found at ``https://" +"your.zammad.domain/auth/saml/metadata``." msgstr "" -#: ../system/core-workflows/limitations.rst:15 -msgid "show" +#: ../settings/security/third-party/saml.rst:33 +msgid "" +"If your IdP doesn't support XML import, you will have to configure Zammad as " +"a new client/app manually using the above XML metadata file for reference." msgstr "" -#: ../system/core-workflows/limitations.rst:16 -msgid "hide" +#: ../settings/security/third-party/saml.rst:36 +msgid "For instance, when you see this tag:" msgstr "" -#: ../system/core-workflows/limitations.rst:25 -msgid "Some fields stay unavailable to customers" -msgstr "" - -#: ../system/core-workflows/limitations.rst:19 -msgid "" -"For technical and security reasons, some default fields (the pale ones you " -"can't edit) stay unavailable for display and usage on customer permissions." -msgstr "" - -#: ../system/core-workflows/limitations.rst:23 +#: ../settings/security/third-party/saml.rst:42 msgid "" -"If you require your customers to change e.g. priorities, please consider " -"using workarounds via :doc:`/system/objects` and :doc:`/manage/trigger`." +"Set the **Assertion Consumer Service Binding URL** (sometimes also listed as " +"**Valid Redirect URIs**) to ``http://your.zammad.domain/auth/saml/callback``." msgstr "" -#: ../system/core-workflows/limitations.rst:29 -msgid "Ticket title changes not supported in edit mask" +#: ../settings/security/third-party/saml.rst:47 +msgid "Set Up User Attribute Mapping" msgstr "" -#: ../system/core-workflows/limitations.rst:28 +#: ../settings/security/third-party/saml.rst:49 msgid "" -"It is currently not possible to perform changes of the ticket title in the " -"edit mask (e.g. renaming, set to read-only)." -msgstr "" - -#: ../system/core-workflows/limitations.rst:37 -msgid "What is out of scope of Core Workflows?" +"Zammad requests the following user attributes (or “properties”) from the IdP:" msgstr "" -#: ../system/core-workflows/limitations.rst:32 -msgid "" -"There are some things that would count as workflow but are either done via :" -"doc:`/manage/trigger` or :doc:`/manage/scheduler`." +#: ../settings/security/third-party/saml.rst:51 +msgid "Email address (``email``)" msgstr "" -#: ../system/core-workflows/limitations.rst:35 -msgid "Such as (but not limited to):" +#: ../settings/security/third-party/saml.rst:52 +msgid "Full name (``name``)" msgstr "" -#: ../system/core-workflows/limitations.rst:37 -msgid "up- or downgrade permissions of users" +#: ../settings/security/third-party/saml.rst:53 +msgid "Given name (``first_name``)" msgstr "" -#: ../system/core-workflows/limitations.rst:38 -msgid "affecting article creation or listing" +#: ../settings/security/third-party/saml.rst:54 +msgid "Family name (``last_name``)" msgstr "" -#: ../system/data-privacy.rst:2 -msgid "Data Privacy" +#: ../settings/security/third-party/saml.rst:56 +msgid "" +"You may need to set up “mappers” (or “mappings”) to tell your IdP how user " +"attributes in SAML correspond to those in Zammad. For a more detailed " +"breakdown, refer to the XML metadata file referenced in the previous section." msgstr "" -#: ../system/data-privacy.rst:4 -msgid "" -"For compliance with GDPR and other data privacy laws, you may wish to " -"**permanently delete users from the system**, along with **all of their " -"associated tickets**." +#: ../settings/security/third-party/saml.rst:62 +msgid "Per-IdP Instructions" 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 `!" +#: ../settings/security/third-party/saml.rst:102 +msgid "Keycloak" msgstr "" -#: ../system/data-privacy.rst:12 +#: ../settings/security/third-party/saml.rst:65 msgid "" -"Access to this panel requires ``admin.data_privacy`` permissions (introduced " -"in Zammad 3.5)." +"**To add Zammad as a client,** save the XML configuration to disk (``https://" +"your.zammad.domain/auth/saml/metadata``) and use **Clients > Clients list > " +"Import client** in the Keycloak admin panel." msgstr "" -#: ../system/data-privacy.rst:15 +#: ../settings/security/third-party/saml.rst:70 msgid "" -"On older systems that have not been updated yet, customers can also be :docs:" -"`deleted via the Zammad console `." +"To help Zammad **match its own user accounts to Keycloak users**, create a " +"user attribute (or “property”) mapper. In **Clients list**, click on your " +"newly created Client ID, choose the tab **Client scopes** and click on the " +"link which refers to your Zammad instance. Choose **Add mapper > By " +"configuration > User Property** and create a mapper with the following " +"entries:" msgstr "" -#: ../system/data-privacy.rst:22 -msgid "User deletion dialog in the Data Privacy panel" +#: ../settings/security/third-party/saml.rst:78 +msgid "**Name**" msgstr "" -#: ../system/data-privacy.rst:22 -msgid "" -"The user deletion dialog lists some of the tickets that will be removed from " -"the system along with the user." +#: ../settings/security/third-party/saml.rst:80 +msgid "**Mapper Type**" msgstr "" -#: ../system/data-privacy.rst:27 -msgid "Deleting Users via GUI" +#: ../settings/security/third-party/saml.rst:81 +msgid "``User Property``" msgstr "" -#: ../system/data-privacy.rst:29 -msgid "🔥 **All deletions are FINAL!**" +#: ../settings/security/third-party/saml.rst:82 +msgid "**Property**" msgstr "" -#: ../system/data-privacy.rst:31 -msgid "Once you click “Delete”, the action cannot be canceled or undone." +#: ../settings/security/third-party/saml.rst:83 +msgid "``emailAddress``" msgstr "" -#: ../system/data-privacy.rst:33 -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." +#: ../settings/security/third-party/saml.rst:84 +msgid "**SAML Attribute Name**" msgstr "" -#: ../system/data-privacy.rst:36 -msgid "**The following records cannot be deleted:**" +#: ../settings/security/third-party/saml.rst:86 +msgid "**SAML Attribute NameFormat**" msgstr "" -#: ../system/data-privacy.rst:38 -msgid "your own account" +#: ../settings/security/third-party/saml.rst:87 +msgid "``basic``" msgstr "" -#: ../system/data-privacy.rst:39 -msgid "the system's last remaining administrator account" +#: ../settings/security/third-party/saml.rst:89 +msgid "" +"In the example above, we're telling Zammad that whenever it receives a SAML " +"login request, it should take the ``email`` property from Keycloak, look for " +"a Zammad user with the same ``email`` attribute, and create a new session " +"for that user." msgstr "" -#: ../system/data-privacy.rst:42 -msgid "Step 1: Find a User / Confirm Deletion" +#: ../settings/security/third-party/saml.rst:95 +msgid "" +"If your Keycloak users' email addresses are stored on another property (*e." +"g.,* ``username``), adjust accordingly." msgstr "" -#: ../system/data-privacy.rst:44 -msgid "There are three ways to access the user deletion dialog:" +#: ../settings/security/third-party/saml.rst:98 +msgid "" +"Back in **Settings**, enter the Client ID (``https://your.zammad.domain/auth/" +"saml/metadata``) in the field **Master SAML Processing URL**." msgstr "" -#: ../system/data-privacy.rst:51 -msgid "**from the user's profile**" +#: ../settings/security/third-party/saml.rst:101 +msgid "You also need to enable **Sign assertions**." msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Accessing the user deletion dialog in a user profile" +#: ../settings/security/third-party/saml.rst:105 +msgid "Step 2: Configure Zammad" msgstr "" -#: ../system/data-privacy.rst:51 -msgid "Click **Action > Delete**." +#: ../settings/security/third-party/saml.rst:107 +msgid "" +"Enable SAML and enter your IdP's details in the Admin Panel under **Settings " +"> Security > Third Party Applications > Authentication via SAML**:" msgstr "" -#: ../system/data-privacy.rst:58 -msgid "**in the “Manage > Users” Admin Panel**" +#: ../settings/security/third-party/saml.rst:None +msgid "Example configuration of SAML part 1" msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Accessing the user deletion dialog under “Users” in the Admin Panel" +#: ../settings/security/third-party/saml.rst:119 +msgid "Display name" msgstr "" -#: ../system/data-privacy.rst:58 -msgid "Use the **⋮ Actions** menu for the target user." +#: ../settings/security/third-party/saml.rst:116 +msgid "" +"Allows you to define a custom button name for SAML. This helps your users to " +"understand better what the button on the login page does." msgstr "" -#: ../system/data-privacy.rst:66 ../system/data-privacy.rst:104 -msgid "**in the “System > Data Privacy” Admin Panel**" +#: ../settings/security/third-party/saml.rst:119 +msgid "Defaults to ``SAML``." msgstr "" -#: ../system/data-privacy.rst:0 -msgid "" -"Accessing the user deletion dialog under “Data Privacy” in the Admin Panel" +#: ../settings/security/third-party/saml.rst:123 +msgid "IDP SSO target URL" msgstr "" -#: ../system/data-privacy.rst:65 +#: ../settings/security/third-party/saml.rst:122 msgid "" -"Use the **New Deletion Task** button. Search for users by name or email " -"address." +"This is the target URL Zammad shall redirect to when the user presses the " +"SAML button. For Keycloak, this needs to look like https://your.domain/" +"realms/your-realm/protocol/saml" msgstr "" -#: ../system/data-privacy.rst:79 -msgid "**Delete organizations**" +#: ../settings/security/third-party/saml.rst:127 +msgid "IDP single logout target URL" msgstr "" -#: ../system/data-privacy.rst:69 +#: ../settings/security/third-party/saml.rst:126 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:" +"This is the URL to which the single logout request and response should be " +"sent." msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Deleting an organization via the user deletion dialog" +#: ../settings/security/third-party/saml.rst:131 +msgid "IDP certificate" msgstr "" -#: ../system/data-privacy.rst:78 +#: ../settings/security/third-party/saml.rst:130 msgid "" -"If this option does not appear, make sure there are no pending deletion " -"tasks for other customers from this organization." +"The public certificate of your IDP for Zammad to verify during the callback " +"phase." msgstr "" -#: ../system/data-privacy.rst:82 -msgid "Step 2: Monitor Deletion Job Status" +#: ../settings/security/third-party/saml.rst:145 +msgid "IDP certificate fingerprint" msgstr "" -#: ../system/data-privacy.rst:84 +#: ../settings/security/third-party/saml.rst:134 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:" +"The fingerprint of your IDPs public certificate to verify during callback " +"phase." msgstr "" -#: ../system/data-privacy.rst:98 -msgid "**in the Activity Stream**" +#: ../settings/security/third-party/saml.rst:137 +msgid "🔏 **For the IdP certificate / certificate fingerprint:**" msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Activity Stream showing data privacy tasks" +#: ../settings/security/third-party/saml.rst:139 +msgid "" +"Provide **only one or the other**—do not provide both! (Between the two, we " +"recommend the signing certificate itself: fingerprints use SHA-1, which `has " +"been broken for a while now `_.)" msgstr "" -#: ../system/data-privacy.rst:94 +#: ../settings/security/third-party/saml.rst:144 msgid "" -"For each deleted user, the Activity Stream will be updated twice—once when " -"the task is created, and once when it's complete." +"**Keycloak users:** Find your certificate in the Keycloak admin panel under " +"**Realm Settings > Keys > Algorithm: RS256 > Certificate**." msgstr "" -#: ../system/data-privacy.rst:97 -msgid "" -"These notifications are only visible to users with ``admin.data_privacy`` " -"permissions." +#: ../settings/security/third-party/saml.rst:151 +msgid "Name identifier format" msgstr "" -#: ../system/data-privacy.rst:0 +#: ../settings/security/third-party/saml.rst:148 msgid "" -"The task list within Data Privacy shows removals being in progress and " -"completed." +"This is the unique identifiers field type. Usually it should be ``urn:oasis:" +"names:tc:SAML:1.1:nameid-format:emailAddress``." msgstr "" -#: ../system/data-privacy.rst:107 -msgid "Frequently Asked Questions" +#: ../settings/security/third-party/saml.rst:151 +msgid "Zammad **expects an email address as unique identifier**!" msgstr "" -#: ../system/data-privacy.rst:121 -msgid "What happens if I receive an email from a deleted customer?" +#: ../settings/security/third-party/saml.rst:155 +msgid "UID attribute name" msgstr "" -#: ../system/data-privacy.rst:110 +#: ../settings/security/third-party/saml.rst:154 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." +"Here you can define an attribute that uniquely identifies the user. If " +"unset, the name identifier returned by the IDP is used." msgstr "" -#: ../system/data-privacy.rst:115 -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**." +#: ../settings/security/third-party/saml.rst:None +msgid "Example configuration of SAML part 2" msgstr "" -#: ../system/data-privacy.rst:130 -msgid "What about user information stored in internal notes or other messages?" +#: ../settings/security/third-party/saml.rst:163 +msgid "" +"Decide if the certificate for the connection to the IdP service has to be " +"verified or not (default: ``yes``)." msgstr "" -#: ../system/data-privacy.rst:124 -msgid "" -"The deletion process removes **user accounts and associated tickets only**." +#: ../settings/security/third-party/saml.rst:169 +msgid "Signing & Encrypting" msgstr "" -#: ../system/data-privacy.rst:126 +#: ../settings/security/third-party/saml.rst:169 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." +"Define if you want to sign, encrypt, do both or nothing for the requests." msgstr "" -#: ../system/data-privacy.rst:137 -msgid "I deleted an user and can still see a message they sent!" +#: ../settings/security/third-party/saml.rst:179 +msgid "Certificate (PEM)" msgstr "" -#: ../system/data-privacy.rst:133 +#: ../settings/security/third-party/saml.rst:172 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." +"Paste the public certificate of your Zammad SAML client, if you want to " +"encrypt the requests." msgstr "" -#: ../system/data-privacy.rst:141 -msgid "I removed a customer, now my reporting is off!" +#: ../settings/security/third-party/saml.rst:175 +msgid "Make sure the certificate is:" msgstr "" -#: ../system/data-privacy.rst:140 -msgid "" -"When removing users and their tickets, all references are removed. This also " -"affects e.g. Reporting - these information are lost." +#: ../settings/security/third-party/saml.rst:177 +msgid "already valid and not yet expired" msgstr "" -#: ../system/data-privacy.rst:145 -msgid "How long does Zammad store created tasks?" +#: ../settings/security/third-party/saml.rst:178 +msgid "no CA certificate" msgstr "" -#: ../system/data-privacy.rst:144 -msgid "" -"Please see the on-premise data section of the :docs:`data privacy ` chapter." +#: ../settings/security/third-party/saml.rst:179 +msgid "valid for signing and encrypting" msgstr "" -#: ../system/data-privacy.rst:150 -msgid "What about re-assigned tickets? I want to delete them, too." +#: ../settings/security/third-party/saml.rst:185 +msgid "Private key (PEM)" msgstr "" -#: ../system/data-privacy.rst:148 +#: ../settings/security/third-party/saml.rst:182 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." +"Paste the private key of your Zammad SAML client here, if you want to sign " +"the requests." msgstr "" -#: ../system/data-privacy.rst:154 -msgid "Why are there so many deletion task entries, I didn't create them!" +#: ../settings/security/third-party/saml.rst:185 +msgid "Make sure the key is an RSA key with a length of at least 2048 bits." msgstr "" -#: ../system/data-privacy.rst:153 -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." +#: ../settings/security/third-party/saml.rst:188 +msgid "Private key secret" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:2 -msgid "Admin Panel Reference" +#: ../settings/security/third-party/saml.rst:188 +msgid "If your private key is secured with a secret, you can provide it here." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:None -msgid "Screenshot of Checkmk settings overview" +#: ../settings/security/third-party/saml.rst:192 +msgid "Your callback URL" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:12 +#: ../settings/security/third-party/saml.rst:191 msgid "" -"Which :doc:`group ` should Checkmk tickets be assigned " -"to as a default (*i.e.,* when none is specified)?" +"This URL is needed for your IdP configuration so it knows where to redirect " +"to after successful authentication." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:15 -msgid "(Applies to :ref:`API alerts ` only.)" +#: ../settings/security/third-party/saml.rst:194 +msgid "" +"After saving your input by clicking on the \"Submit\" button, Zammad " +"verifies the provided keys/certificates (e.g. if they are valid for signing/" +"encrypting and if they aren't expired)." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:21 -msgid "Auto close" +#: ../settings/security/third-party/saml.rst:199 +msgid "" +"See :ref:`automatic account linking ` for details " +"on how to link existing Zammad accounts to IdP accounts." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:18 -msgid "" -"Should Zammad automatically close tickets if a service has recovered on its " -"own?" +#: ../settings/security/third-party/saml.rst:205 +msgid "Automatic account linking doesn't work" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:21 -msgid "(Agents will receive notifications for such closures as appropriate.)" +#: ../settings/security/third-party/saml.rst:206 +msgid "" +"Have you double-checked your IdP's user attribute mapping configuration?" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:30 -msgid "Auto-close state" +#: ../settings/security/third-party/twitter.rst:4 +msgid "" +"It is possible to create a quick login for your helpdesk via Twitter. To do " +"so, you need to follow these steps:" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:24 -msgid "What ticket state should be applied when “auto-closing” a ticket?" +#: ../settings/security/third-party/twitter.rst:8 +msgid "Register Twitter App" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:26 -msgid "" -"You can choose from the seven built-in ticket states. If these states aren't " -"enough for you, you can :ref:`define a new ticket state ` for this purpose as well. This can be useful for tracking " -"tickets with :doc:`reports `, for example." +#: ../settings/security/third-party/twitter.rst:10 +msgid "Go to https://dev.twitter.com/apps and login with your account." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:35 -#: ../system/integrations/cti/includes/recent-logs.include.rst:2 -#: ../system/integrations/ldap/index.rst:74 -#: ../system/integrations/pgp/index.rst:106 -msgid "Recent Logs" +#: ../settings/security/third-party/twitter.rst:15 +msgid "Click on \"Create App\"" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:None -msgid "Screenshot of Checkmk \"Recent Logs\" section" +#: ../settings/security/third-party/twitter.rst:None +msgid "new app page" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:41 +#: ../settings/security/third-party/twitter.rst:20 msgid "" -"If you're having trouble getting Zammad and Checkmk to play nicely together, " -"this section can help you troubleshoot." +"Enter app settings. As \"Callback URL\" you need to enter ``https://" +"zammad_host/api/v1/external_credentials/twitter/callback``. You need to " +"replace ``zammad_host`` with the domain of your Zammad system." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:44 +#: ../settings/security/third-party/twitter.rst:24 msgid "" -"It contains a record of the fifty most recent transactions that Zammad knows " -"about, including each one's request/response details and return status." +"After the app has been created, update the application icon and organization " +"attributes." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:2 -msgid "API Reference" +#: ../settings/security/third-party/twitter.rst:None +msgid "set permissions to receive and send direct messages" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:4 +#: ../settings/security/third-party/twitter.rst:30 msgid "" -"For most users, :ref:`the sample scripts from the Setup Guide ` will do the job just fine. But if you want more fine-grained control" -"—for instance, to create high- and low-priority tickets for different types " -"of system events—then you'll have to customize the data those scripts send " -"to Zammad." +"Next we need to set ``read, write and access direct messages`` permissions " +"for the app." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:15 +#: ../settings/security/third-party/twitter.rst:None +msgid "click on Keys & Access Token, note them" +msgstr "" + +#: ../settings/security/third-party/twitter.rst:36 msgid "" -"This custom script will automatically set all tickets it creates to **high " -"priority** and **assign them to charlie@chrispresso.com**." +"Go to \"Keys and Access Token\" tab and note the \"Consumer Key\" and " +"\"Consumer Secret\"." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:32 -msgid "How Does it Work?" +#: ../settings/security/third-party/twitter.rst:40 +msgid "Configure Zammad as Twitter App" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:34 +#: ../settings/security/third-party/twitter.rst:42 msgid "" -"There are two kinds of data you can pass to the API, both in the form of key-" -"value pairs:" +"Go to \"Admin > Security > Twitter > Third Party Applications > Twitter\" " +"Section." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:44 -msgid "Checkmk parameters" +#: ../settings/security/third-party/twitter.rst:None +msgid "Admin > Security > Third Party Applications" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:38 +#: ../settings/security/third-party/twitter.rst:48 msgid "" -"are required, and make up the **contents** of the resulting tickets/" -"articles. They also determine whether an event creates a new ticket or " -"updates/closes an existing one." +"Fill in the \"Twitter Key\" and the \"Twitter Secret\" and click the " +"\"Submit\" button." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:42 +#: ../settings/security/third-party/twitter.rst:51 msgid "" -"These are the only values used in the sample scripts. **Use them as-is**; " -"technically, they can be customized, but it's hard to imagine a good reason " -"for it." +"Now you can link accounts via \"Avatar > Profile > Link Accounts\" or login " +"via Zammad login page." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:52 -msgid "Ticket attributes" +#: ../settings/security/two-factor.rst:11 +msgid "Two-factor Authentication Methods" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:47 -msgid "" -"are optional, and can be used to **adjust settings** on newly created " -"tickets (*e.g.,* set the owner, group, priority, or state)." +#: ../settings/security/two-factor.rst:2 +msgid "Two-Factor Authentication" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:50 +#: ../settings/security/two-factor.rst:4 msgid "" -"If you want to customize your Checkmk alert script, do it with these. Simply " -"add an extra “form” option for each one (``-F \"key=value\"``) to your " -"script's ``curl`` command line, as in the example above." +"Two-factor authentication (2FA) enhances the security of Zammad accounts by " +"adding an extra layer of verification beyond a password. It requires users " +"to provide two different types of authentication factors, typically " +"something they know (like a password) and something they possess (like a " +"mobile device or a security token), to ensure that only authorized " +"individuals can access the account." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:54 -msgid "💡 **It's just an API endpoint!**" +#: ../settings/security/two-factor.rst:19 +msgid "Enable Recovery Codes" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:56 +#: ../settings/security/two-factor.rst:21 msgid "" -"When using Checkmk integration, messages need to be formatted in a certain " -"way, but that *doesn't mean the messages actually have to come from Checkmk*." +"Recovery codes are one-time use security codes that can be used by the user " +"if they lose access to their other two-factor authentication methods. They " +"cannot be used on their own, they can only be activated if at least one two-" +"factor authentication method is enabled." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:59 -msgid "" -"If you use another monitoring tool that's not officially supported by " -"Zammad, there's probably a way to make it work with your Checkmk callback " -"URL." +#: ../settings/security/two-factor.rst:None +msgid "Enable Recovery Codes Setting" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:63 -msgid "Checkmk Parameters" +#: ../settings/security/two-factor.rst:30 +msgid "" +"Recovery codes can only be used as a backup method. If enabled, they will be " +"automatically generated for the user once they set up their initial two-" +"factor authentication method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:65 +#: ../settings/security/two-factor.rst:34 msgid "" -"When a notification is received, Zammad creates a new article containing the " -"details of the event that triggered it:" +"The user will be asked to print out or save the generated recovery codes in " +"a safe place. Once used, a recovery code cannot be reused." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:None -msgid "Checkmk article body" +#: ../settings/security/two-factor.rst:37 +msgid "" +"Users will also have an option to regenerate their recovery codes at any " +"time, which invalidates already existing recovery codes and provides them " +"with a list of fresh codes." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:72 +#: ../settings/security/two-factor.rst:41 msgid "" -"These details come from the fields listed below, which correspond to " -"parameters provided by Checkmk (``$NOTIFY_*``)." +"After you enable this setting, when the user completes a setup of their " +"initial two-factor authentication method, they will be presented with a list " +"of recovery codes and instructed to save them for later use." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:75 -msgid "**Required fields are marked with an asterisk (\\*).**" +#: ../settings/security/two-factor.rst:None +msgid "Recovery Codes Generation Modal Dialog" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:79 -msgid "event_id\\*" +#: ../settings/security/two-factor.rst:50 +msgid "Enforce the Set Up of the Two-Factor Authentication" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:78 +#: ../settings/security/two-factor.rst:52 msgid "" -"A unique ID for the system event. (``$NOTIFY_SERVICEPROBLEMID`` / " -"``$NOTIFY_HOSTPROBLEMID``)" +"In case you wish to require your users to set up at least one two-factor " +"authentication method for their account, you can do this by selecting " +"specific user roles the requirement applies to in **Enforced for user " +"roles** setting. Of course you must have at least one two-factor " +"authentication method enabled for this setting to take effect." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:86 -msgid "host\\*" +#: ../settings/security/two-factor.rst:None +msgid "Enforced for User Roles Setting" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:82 +#: ../settings/security/two-factor.rst:62 msgid "" -"The hostname of the system that the event originated from. " -"(``$NOTIFY_HOSTNAME``)" +"After you change this setting, if the user has one of the selected roles on " +"their account, they will be forced to set up the two-factor authentication " +"upon next sign in or application reload." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:85 +#: ../settings/security/two-factor.rst:66 msgid "" -"Used to determine if a new event belongs to an existing ticket. Also used in " -"the subject line of the resulting article (“ is ”)." +"A modal dialog with instructions will be shown, and they will not be able to " +"do any work before they set up at least one two-factor method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:96 -msgid "service" +#: ../settings/security/two-factor.rst:None +msgid "Modal Dialog for Enforcing Two-Factor Authentication Set Up" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:89 -msgid "" -"The name of the service that the event originated from. " -"(``$NOTIFY_SERVICEDESC``)" +#: ../settings/security/two-factor.rst:74 +msgid "Reset Two-Factor Authentication for a Specific User" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:92 -msgid "Used to determine if a new event belongs to an existing ticket." +#: ../settings/security/two-factor.rst:76 +msgid "" +"In case an user isn't able to login anymore because of an inaccessible " +"second factor, you can reset the user's 2FA method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:94 -#: ../system/integrations/checkmk/api-reference.rst:110 -msgid "Displayed as ``-`` when omitted." +#: ../settings/security/two-factor.rst:79 +msgid "" +"To do this, go to the user management and search for the relevant user. " +"After you found the account, click the button in the action column and " +"select \"Manage Two-Factor Authentication\":" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:104 -msgid "state\\*" +#: ../settings/security/two-factor.rst:None +msgid "Context menu in action column in user management" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:99 +#: ../settings/security/two-factor.rst:87 msgid "" -"The current state of the service or host in question. " -"(``$NOTIFY_SERVICESTATE`` / ``$NOTIFY_HOSTSTATE``)" +"After selecting this, you can see a dialog where you can either reset one " +"2FA method or reset all of the user's 2FA methods:" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:102 +#: ../settings/security/two-factor.rst:None +msgid "Dialog for resetting user's 2FA method" +msgstr "" + +#: ../settings/security/two-factor.rst:94 msgid "" -"Used to detect when a ticket should be auto-closed (*i.e.,* on ``OK``/" -"``UP``). Also used in the subject line of the resulting article (“ is " -"”)." +"Choose the fitting one, click on the corresponding \"Remove ...\" button and " +"confirm your action. The user now has to setup a new 2FA method, depending " +"on your 2FA configuration." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:110 -msgid "text" +#: ../settings/security/two-factor/authenticator-app.rst:2 +msgid "Authenticator App" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:107 +#: ../settings/security/two-factor/authenticator-app.rst:4 msgid "" -"The output of the process that triggered the event. " -"(``$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" +"The authenticator app method is a type of two-factor authentication that " +"uses a mobile application to generate one-time codes for account " +"verification. After setting up the authenticator app on their device, the " +"user links it to their Zammad account." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:121 +#: ../settings/security/two-factor/authenticator-app.rst:12 msgid "" -"The Object Manager attribute panel displays built-in and custom\n" -"attribute names." +"When logging in, the user is prompted to enter a time-sensitive code " +"generated by the app, in addition to their password. This code acts as the " +"second factor of authentication, providing an extra layer of security as it " +"changes periodically and is unique to the user's device." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:121 -msgid "Find a complete list of ticket attributes in the Object Manager." +#: ../settings/security/two-factor/authenticator-app.rst:None +msgid "Security Code in Google Authenticator App" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:123 +#: ../settings/security/two-factor/authenticator-app.rst:22 msgid "" -"Ticket attributes are entirely optional, and can be used to customize the " -"tickets that Checkmk creates. (Note that these attributes will be ignored if " -"a new event belongs to an existing ticket.)" +"The app generates codes based on a shared secret key stored securely on both " +"the user's device and the server, ensuring a synchronized and secure " +"authentication process. The method of generating the codes is sometimes also " +"called TOTP (time-based one-time password)." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:128 -msgid "" -"Why would you want to do this? Maybe you have only one IT guy, and all " -"system monitoring issues should be automatically assigned to him. Or, maybe " -"you're creating multiple notification rules so that database outages take " -"higher priority than disk space warnings." +#: ../settings/security/two-factor/authenticator-app.rst:28 +msgid "Enabling the Authenticator App Method" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:135 -msgid "In most cases, you'll probably want to set one of the following:" +#: ../settings/security/two-factor/authenticator-app.rst:30 +#: ../settings/security/two-factor/security-keys.rst:28 +msgid "To enable the method, just toggle the switch on in the settings." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:137 -msgid "group" -msgstr "группа" - -#: ../system/integrations/checkmk/api-reference.rst:139 -msgid "state" +#: ../settings/security/two-factor/authenticator-app.rst:None +msgid "Authenticator App Switch in Settings" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:140 -msgid "priority" -msgstr "приоритет" - -#: ../system/integrations/checkmk/api-reference.rst:142 +#: ../settings/security/two-factor/authenticator-app.rst:36 msgid "" -"but in practice, you can set almost any attribute, including :doc:`custom " -"ones you created through the Object Manager `." +"Now the users will be able to set up this two-factor authentication method " +"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " +"Once they do, on next sign-in with password, they will be asked to provide " +"an additional security code generated by their mobile device." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:145 -msgid "Please note that the following attributes are **not customizable**:" +#: ../settings/security/two-factor/security-keys.rst:2 +msgid "Security Keys" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:147 -msgid "title" -msgstr "заголовок" +#: ../settings/security/two-factor/security-keys.rst:4 +msgid "" +"The security keys method is a type of a two-factor authentication that uses " +"Web Authentication API in the browser for verifying user's identity. The " +"user can register multiple hardware or software security keys with their " +"Zammad account and then they can use it during the sign-in process." +msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:148 -msgid "id" +#: ../settings/security/two-factor/security-keys.rst:12 +msgid "" +"When logging in, the user is prompted to provide the same security key they " +"registered with their account, in addition to their password. This key acts " +"as the second factor of authentication, providing an extra layer of security." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:149 -msgid "ticket number" +#: ../settings/security/two-factor/security-keys.rst:None +msgid "Security Key dialog in Safari on macOS" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:151 -msgid "created_by_id" +#: ../settings/security/two-factor/security-keys.rst:21 +msgid "" +"The type of the key can range from hardware USB sticks to passkeys stored in " +"a device of user's choice. Which type can be used depends on the browser " +"flavor and the platform of the user." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:152 -msgid "updated_by_id" +#: ../settings/security/two-factor/security-keys.rst:26 +msgid "Enabling the Security Keys Method" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:155 -msgid "Which Values Can Be Set?" +#: ../settings/security/two-factor/security-keys.rst:None +msgid "Security Keys Switch in Settings" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:157 -msgid "😵 **Invalid values → unpredictable behavior**" +#: ../settings/security/two-factor/security-keys.rst:34 +msgid "" +"Now the users will be able to set up this two-factor authentication method " +"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " +"Once they do, on next sign-in with password, they will be asked to provide " +"the same security key they registered during the setup." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:159 +#: ../settings/system/system-selfhosted.include.rst:3 msgid "" -"If you provide a value that Zammad doesn't understand (*e.g.,* ``-F " -"\"priority=high\"``), it's not always clear what will happen. In some cases, " -"a ticket will be created with the default values instead - but in others, it " -"may not be created at all!" +"Below settings are only available to self hosted users. In hosted " +"environments we're handling these settings for you to ensure service " +"stability." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:164 -msgid "So what values does Zammad understand, then? Well, it depends..." +#: ../settings/system/base.rst:11 +msgid "Fully Qualified Domain Name" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:168 -msgid "Use an email address or username:" +#: ../settings/system/base.rst:7 +msgid "The URL of your Zammad installation." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:190 -msgid "group & priority" +#: ../settings/system/base.rst:9 ../settings/system/base.rst:17 +msgid "This setting is used within :doc:`/misc/variables` and notifications." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:175 -msgid "Refer to the dropdown menus in the ticket pane:" +#: ../settings/system/system-base.include.rst:1 +msgid "It is automatically set by the *Getting Started wizard*." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:0 -msgid "See possible values for certain attributes in the ticket pane." +#: ../settings/system/system-base.include.rst:5 +msgid "Changing this setting also changes callback URLs for your channels etc." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:187 -msgid "🙅 **Ticket state CANNOT be set this way!**" +#: ../settings/system/system-base.include.rst:6 +msgid "This setting can have negative affects on being able to login." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:189 -msgid "" -"Why? Because ``-F \"state=...\"`` is already used :ref:`as a Checkmk " -"parameter `." -msgstr "" - -#: ../system/integrations/checkmk/api-reference.rst:222 -msgid "Everything Else" +#: ../settings/system/base.rst:19 +msgid "HTTP type" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:193 +#: ../settings/system/base.rst:14 msgid "" -"To set any other attributes, it helps to know your way around the :docs:" -"`rails console `. Valid values are those that you can " -"set with a string:" +"The HTTP type tells your installation how your clients connect. This is " +"relevant for authentication and cookie security." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:218 -msgid "These values can then be passed directly to the API:" +#: ../settings/system/base.rst:31 +msgid "SystemID" msgstr "" -#: ../system/integrations/checkmk/index.rst:16 -msgid "How does it work?" +#: ../settings/system/base.rst:22 +msgid "" +"This ID is being used within your ticket number. In case you're " +"communicating with another ticket system with similar ticket number schemes " +"this ID greatly reduces the risk of false follow ups." msgstr "" -#: ../system/integrations/checkmk/index.rst:2 -msgid "Checkmk" +#: ../settings/system/base.rst:26 +msgid "" +"The SystemID is randomly selected upon installation of Zammad (``1-99``)." msgstr "" -#: ../system/integrations/checkmk/index.rst:4 +#: ../settings/system/base.rst:30 msgid "" -"`Checkmk `_ is a powerful IT monitoring tool that can " -"send real-time status alerts to Zammad via email or REST API. Set these " -"alerts up in Checkmk, and Zammad will automatically create, update, and " -"close tickets based on the health of your system:" +"**Do not** change this setting in a productive system! Your Zammad " +"installation may no longer recognize old ticket number based follow ups upon " +"change!" msgstr "" -#: ../system/integrations/checkmk/index.rst:14 -msgid "Screenshot of ticket created by Checkmk notifications" +#: ../settings/system/frontend.rst:2 +msgid "Frontend" msgstr "" -#: ../system/integrations/checkmk/index.rst:14 -msgid "Multiple alerts, same ticket." +#: ../settings/system/frontend.rst:22 +msgid "Core Workflow Ajax Mode" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:2 -msgid "Setup Guide" +#: ../settings/system/frontend.rst:6 +msgid "" +"This setting allows administrators to enforce :doc:`/system/core-workflows` " +"to use Ajax-Calls instead of web sockets. You'll usually only need this if " +"you experience serious issues as noted below." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:4 -msgid "" -"Whenever the Checkmk integration is enabled, Zammad listens for messages on " -"its API and over email. As long as those messages follow the required " -"format, Zammad will create new tickets (or find and update existing ones) " -"based on the message contents." +#: ../settings/system/frontend.rst:10 +msgid "**🤓 Possible (technical) reasons**" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:10 +#: ../settings/system/frontend.rst:12 msgid "" -"That means that “setting up Checkmk integration” is simply a matter of " -"**adding configuration to your Checkmk site**: telling it when to send these " -"messages and what to say. To do that, you'll need to create a new " -"**notification rule** (see `Checkmk's official docs `_ for help with that)." +"In some cases, your network structure (e.g. firewalls, proxies) may " +"disconnect long web socket connections. This leads to select fields staying " +"empty (e.g. owner selection *after* selecting your group) or fields not " +"shown / hidden (e.g. when switching to or from pending states, the \"pending " +"till\" field not showing / hiding)." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:17 +#: ../settings/system/frontend.rst:18 msgid "" -"As part of this new rule, you'll have to choose a **notification method** " -"(*i.e.,* a script to execute whenever the rule is triggered). This script " -"will be written by you (samples below), and contain the logic for sending " -"API/email messages to Zammad:" +"Please keep in mind that the Ajax fallback may cause serious pressure on " +"your application server. If you have the choice stick to web sockets." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:26 -msgid "Checkmk \"New Rule\" dialog" +#: ../settings/system/frontend.rst:22 +msgid "Default: ``no`` (inactive)" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:26 -msgid "" -"Find your custom scripts in the Checkmk WATO under **Notifications > New " -"Rule > Notification Method**." +#: ../settings/system/frontend.rst:53 +msgid "Show calendar weeks in the picker of date/datetime fields" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:29 +#: ../settings/system/frontend.rst:25 msgid "" -"Once you're done setting up your new rule, you're all set! New tickets " -"should start coming in and auto-updating any time your rule is triggered." +"With this setting you can instruct Zammad to provide week number display " +"globally for all users. Calendar with week number display are usually used " +"in business sectors and may not be relevant for everyone." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:33 +#: ../settings/system/frontend.rst:29 msgid "" -"(If you need help troubleshooting, be sure to check the :ref:`checkmk-recent-" -"logs`.)" +"This setting affects *all areas* - you'll also see week numbers in the admin " +"panel for e.g. triggers and macros." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:38 -msgid "API Alerts" +#: ../settings/system/frontend.rst:32 +msgid "Default: ``no`` (not shown)" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:40 -msgid "" -"To add these scripts in the Checkmk WATO, copy them into your Checkmk " -"installation directory and make them executable. (Be sure to replace the " -"``zammad.example.com`` callback URL with the one found in your admin panel.)" +#: ../settings/system/frontend.rst:53 +msgid "Here's the difference:" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:60 -msgid "Service notification" +#: ../settings/system/frontend.rst:0 +msgid "Screenshot showing Zammad's date picker (in the default way)" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:46 +#: ../settings/system/frontend.rst:41 +msgid "Set to ``no``" +msgstr "" + +#: ../settings/system/frontend.rst:0 msgid "" -"For updates on the status of the software running on your server (*e.g.,* " -"postgres)." +"Screenshot showing Zammad's date picker with\n" +"week numbers enabled" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:75 -msgid "Host notification" +#: ../settings/system/frontend.rst:50 +msgid "Set to ``yes``" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:63 -msgid "For updates on the status of the server itself." +#: ../settings/system/index.rst:4 +msgid "" +"For your overview we split each tab within system settings into its own page:" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:77 -msgid "🤔 **What's with all the env vars?**" +#: ../settings/system/index.rst:16 +msgid "Console Based Settings" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:79 +#: ../settings/system/index.rst:18 msgid "" -"Whenever Checkmk runs these scripts, it needs to provide some information " -"about the event that triggered the notification. This information is passed " -"in the form of these ``$NOTIFY_*`` environment variables." +"There's some console based settings we didn't put into the UI. However, you " +"may find them helpful - you can find them in our :docs:`hidden settings ` section." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:85 +#: ../settings/system/network.rst:2 +msgid "Network" +msgstr "" + +#: ../settings/system/network.rst:8 msgid "" -"You can specify additional parameters to pass to the script when you're " -"setting up your notification rule, but the ones you see here are all " -"provided by default." +"The proxy settings can only be saved after successfully testing the proxy " +"connection." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:90 -msgid "Email Alerts" +#: ../settings/system/network.rst:15 +msgid "Proxy Address." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:94 +#: ../settings/system/network.rst:12 msgid "" -"🐞 **There are known bugs** in Zammad's processing of email from Checkmk. " -"This section will be completed once they have been resolved. (Learn more at " -"GitHub issues `#2377 `_ & " -"`#2180 `_.)" +"Allows you to provide a proxy server if needed. This is relevant for network " +"communication by Zammad." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:100 -msgid "In the meantime, we encourage you to set up API alerts instead." +#: ../settings/system/network.rst:15 +msgid "It **does not** affect the update process or Elasticsearch." msgstr "" -#: ../system/integrations/clearbit.rst:2 -msgid "Clearbit" +#: ../settings/system/network.rst:18 +msgid "Username for proxy connection." msgstr "" -#: ../system/integrations/clearbit.rst:4 +#: ../settings/system/network.rst:18 msgid "" -"With our Clearbit integration, you can easily enrich the information " -"provided by Zammad. If the customers or agents email address is known to " -"Clearbit, it will share all information it has regarding the user with " -"Zammad. Those information can include the following:" -msgstr "" - -#: ../system/integrations/clearbit.rst:9 -msgid "Avatar" +"If your proxy server requires authentication, provide the username here." msgstr "" -#: ../system/integrations/clearbit.rst:10 -msgid "Address information" +#: ../settings/system/network.rst:21 +msgid "Password for proxy connection." msgstr "" -#: ../system/integrations/clearbit.rst:11 -msgid "Website information" +#: ../settings/system/network.rst:21 +msgid "" +"If your proxy server requires authentication, provide the password here." msgstr "" -#: ../system/integrations/clearbit.rst:12 -msgid "A BIO (as Note by default)" +#: ../settings/system/network.rst:26 +msgid "No proxy for the following hosts." msgstr "" -#: ../system/integrations/clearbit.rst:14 +#: ../settings/system/network.rst:24 msgid "" -"If needed, you can add further custom objects and add mappings to them, so " -"the Clearbit information can be filled within the database. In general you " -"can get any information from Clearbit, as long as you have a mapping to an " -"Zammad object." +"Exception list for hosts you can't or don't want to reach via proxy server." msgstr "" -#: ../system/integrations/clearbit.rst:21 -msgid "" -"Clearbit does have a mapping of fields like LDAP and Exchange have, but does " -"not \"win\" against Zammad information. This means that if you have e.g. the " -"last name field filled in already and Clearbit has other information on " -"that, it will not be updated." +#: ../settings/system/network.rst:27 +msgid "Default: ``localhost,127.0.0.0,::1``" msgstr "" -#: ../system/integrations/clearbit.rst:26 -msgid "" -"However: If let's say the last name has been set by Clearbit and Zammad " -"notices that the last name on the Clearbit source has changed, Zammad will " -"also update this value." +#: ../settings/system/services.rst:2 +msgid "Services" msgstr "" -#: ../system/integrations/clearbit.rst:33 -msgid "" -"The configuration of Clearbit is really easy and done fast! Just login to " -"your Clearbit-Account, go to \"API\" and copy the secret-API-Key." +#: ../settings/system/services.rst:10 +msgid "Image Service" msgstr "" -#: ../system/integrations/clearbit.rst:38 -msgid "" -"Now change to your Zammad instance, go to Integrations (System) -> Clearbit " -"in the admin panel. Paste your API-Key into the API-Key-Field and decide if " -"Zammad should create unknown Organizations automatically, if the user does " -"not have one yet (and Clearbit knows it). The shared option decides if the " -"new organizations Zammad creates with Clearbit should be shared ones." +#: ../settings/system/services.rst:5 +msgid "Defines the backend for user and organization image lookups." msgstr "" -#: ../system/integrations/clearbit.rst:47 -msgid "" -"If you're unsure what option to choose, better stick with \"no\". You can " -"also learn more about :doc:`/manage/organizations/index`." +#: ../settings/system/services.rst:7 +msgid "Default: ``Zammad Image Service`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:52 +#: ../settings/system/services.rst:9 msgid "" -"The Mapping option works similar to the mapping within the Exchange and LDAP " -"sync. You can add further mappings for e.g. custom fields if you need more " -"information that Clearbit can provide." +"Make sure your on premise installation has ``HTTPS`` access to ``images." +"zammad.com``." msgstr "" -#: ../system/integrations/clearbit.rst:58 -msgid "" -"If you want to add more Clearbit fields and want to learn more about " -"available fields on their API, you can take a look at their `API " -"documentation `_." -msgstr "" - -#: ../system/integrations/clearbit.rst:62 -msgid "" -"If you're happy with the above chosen Settings and your mapping, just save " -"the changes and enable Clearbit integration. Zammad will now start polling " -"the Clearbit API as users contact you." +#: ../settings/system/services.rst:18 +msgid "Geo Calendar Service" msgstr "" -#: ../system/integrations/clearbit.rst:68 +#: ../settings/system/services.rst:13 msgid "" -"Zammad does not synchronize with Clearbit on a regular basis, but on demand " -"if needed. This saves API calls." +"Defines the backend for geo calendar lookups. Used for initial calendar " +"setup." msgstr "" -#: ../system/integrations/clearbit.rst:73 -msgid "" -"Below the Settings and Mappings, you'll find our Integration log. You can " -"see what requests Zammad sent to Clearbit and also the APIs Response." +#: ../settings/system/services.rst:16 +msgid "Default: ``Zammad GeoCalendar Service`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:78 +#: ../settings/system/services.include.rst:2 msgid "" -"By the way, you can also view the API log on the Clearbit website - the " -"information seen is basically the same." +"Make sure your on premise installation has ``HTTPS`` access to ``geo.zammad." +"com``." msgstr "" -#: ../system/integrations/clearbit.rst:84 -msgid "Example When Adding a User" +#: ../settings/system/services.rst:26 +msgid "Geo IP Service" msgstr "" -#: ../system/integrations/clearbit.rst:86 +#: ../settings/system/services.rst:21 msgid "" -"To show you how fast information is added, we added a small Screencast " -"below. This shows the creation of the User Alex from Clearbit. As we already " -"set the last name of Alex to \"X\", Zammad did not update it. What Zammad " -"did was to add further information it received from Clearbit." +"Defines the backend for geo IP lookups. Shows also location of an IP address " +"if an IP address is shown." msgstr "" -#: ../system/integrations/cti/generic.rst:2 -msgid "CTI (generic)" +#: ../settings/system/services.rst:24 +msgid "Default: ``Zammad GeoIP Service`` (active)" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:1 -msgid "" -"This integration enables Zammad to provide a caller log to your agents. With " -"this your agents can greet your customers by their name and are supported by " -"Zammad with automatically opening a new ticket dialog or the user profile." +#: ../settings/system/services.rst:32 +msgid "Geo Location Service" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:6 +#: ../settings/system/services.rst:29 msgid "" -"Click the toggle next to the heading to activate or deactivate this " -"integration." +"Defines the backend for geo location lookups to store geo locations for " +"addresses." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:9 +#: ../settings/system/services.rst:32 msgid "" -"If you want to learn more on how your agents can use this function, please " -"refer the :user-docs:`user documentation `." +"Default: ``OpenStreetMap (ODbL 1.0, http://osm.org/copyright)`` (active)" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:14 +#: ../settings/system/services.rst:36 msgid "" -"Automatically opening new ticket dialogues or user profiles requires agent " -"to extension mapping - see more below." -msgstr "" - -#: ../system/integrations/cti/includes/introduction.include.rst:20 -msgid "Please note the following limitations to reduce confusion later on:" +"You can find a detailed privacy information on what we store for how long on " +"our :docs:`Privacy Appendix ` inside of our System " +"Documentation." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:22 -msgid "CTI integrations provide caller log functions only." +#: ../settings/system/storage.rst:2 +msgid "Storage" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:23 +#: ../settings/system/storage.rst:6 msgid "" -"This integration does not provide any VoIP functionalities; you can't make " -"phone calls from within Zammad." +"Here you can define where Zammad stores attachments for tickets and the " +"knowledge base. By default, we're writing to the ``Database`` - you can " +"switch to ``Filesystem`` or ``Simple Storage (S3)`` at any time. In this " +"case please have a look on the following instructions." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:25 +#: ../settings/system/storage.rst:11 msgid "" -"If your browser supports ``tel``-URLs, you can click on phone numbers for " -"automatic dialing. This requires additional software / configuration on your " -"agent's computers." +"If you have a busy Zammad instance, we strongly encourage you to use " +"filesystem storage instead of \"Database\". This will greatly improve system " +"performance (de-crease database load and size)." msgstr "" -#: ../system/integrations/cti/generic.rst:9 -#: ../system/integrations/cti/placetel.rst:14 -#: ../system/integrations/cti/sipgate.rst:14 -msgid "Please provide the following requirements:" +#: ../settings/system/storage.rst:19 +msgid "Database" msgstr "" -#: ../system/integrations/cti/generic.rst:11 +#: ../settings/system/storage.rst:17 msgid "" -"A telephone system that supports webhooks (outbound) (best option are those " -"that allow customizing the calls)." -msgstr "" - -#: ../system/integrations/cti/generic.rst:13 -msgid "A unique Call-ID during the call session." +"This is the default storage method. The attachments are stored directly in " +"the database. If your Zammad instance grows, we recommend one of the other " +"methods to maintain performance." msgstr "" -#: ../system/integrations/cti/generic.rst:14 -msgid "Call event data (both numbers and direction)." +#: ../settings/system/storage.rst:38 +msgid "Filesystem" msgstr "" -#: ../system/integrations/cti/generic.rst:15 -msgid "Your Zammad instance must be reachable for your telephony system." +#: ../settings/system/storage.rst:22 +msgid "" +"This storage method is recommended for all Zammad instances, especially for " +"those with a higher load. If you choose filesystem, your files are written " +"to ``/opt/zammad/storage/``." msgstr "" -#: ../system/integrations/cti/generic.rst:17 +#: ../settings/system/storage.rst:26 msgid "" -"If you want to learn more on what kind of requests are supported by Zammad " -"and what it expects, please consult our :docs:`CTI-API documentation `." +"Moving attachments from \"Database\" to \"Filesystem\" can be run during " +"production use. However, you should consider your framework conditions (e.g. " +"bandwidth, system load in production) to define the right moment." msgstr "" -#: ../system/integrations/cti/generic.rst:22 -#: ../system/integrations/cti/placetel.rst:27 -#: ../system/integrations/cti/sipgate.rst:30 -msgid "Available Settings" +#: ../settings/system/storage.rst:32 +msgid "**You noticed slow updates of Zammad?**" msgstr "" -#: ../system/integrations/cti/generic.rst:29 -#: ../system/integrations/cti/placetel.rst:41 -#: ../system/integrations/cti/sipgate.rst:40 -msgid "Endpoint Settings" +#: ../settings/system/storage.rst:34 +msgid "" +"While Zammad is beeing updated, it enforces a recursive \"change " +"owner\" (chown) for this directory. For instances with many files this can " +"be time consuming. To mitigate that you can move your files and create a " +"symlink in ``/opt/zammad/storage/`` to the new directory. Of course you have " +"to make sure on your own that the permissions are always correct." msgstr "" -#: ../system/integrations/cti/generic.rst:25 -msgid "" -"Zammad will list your generic CTI endpoint here. It contains a unique token " -"so ensure to keep this URL save." +#: ../settings/system/storage.rst:95 +msgid "Simple Storage (S3)" msgstr "" -#: ../system/integrations/cti/generic.rst:28 +#: ../settings/system/storage.rst:41 msgid "" -"You'll need this endpoint for your PBX to talk to Zammad, see :docs:`CTI-API " -"documentation `." +"To use the Simple Storage (S3), you have to provide some settings, which " +"can't be accessed in the UI (see instructions below)." msgstr "" -#: ../system/integrations/cti/includes/important-dont-forget-saving.include.rst:3 +#: ../settings/system/storage.rst:44 msgid "" -"All following options **do not save automatically**. Always use the Save " -"button on the lower end of the integration page!" +"⚠️ Please note that the current implementation is in its early stages and can " +"be modified in the future." msgstr "" -#: ../system/integrations/cti/generic.rst:43 -#: ../system/integrations/cti/placetel.rst:49 -#: ../system/integrations/cti/sipgate.rst:52 -msgid "Call Settings" +#: ../settings/system/storage.rst:47 +msgid "" +"The prerequisite is to have access to a S3-compatible storage and to have " +"all necessary parameters available (which depends on your storage provider; " +"if in doubt, please ask there for help)." msgstr "" -#: ../system/integrations/cti/generic.rst:39 -#: ../system/integrations/cti/placetel.rst:49 -#: ../system/integrations/cti/sipgate.rst:37 -#: ../system/integrations/cti/sipgate.rst:50 -msgid "Inbound" +#: ../settings/system/storage.rst:51 +msgid "Steps to configure S3:" msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:1 +#: ../settings/system/storage.rst:53 msgid "" -"This option allows you to block specific incoming caller IDs. It allows you " -"to temporarily reject e.g. spam callers without having to contact providers " -"or PBX administrators." +"Copy ``config/zammad/storage.yml.dist`` to ``config/zammad/storage.yml``" msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:11 -msgid "Caller ID to block" +#: ../settings/system/storage.rst:54 +msgid "Edit the copied file in one of the following ways:" msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 -msgid "Provide caller IDs to block in ``E.164`` format." +#: ../settings/system/storage.rst:56 +msgid "" +"Either provide your S3 configuration with one attribute per line like in the " +"upper area of the file" msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:8 +#: ../settings/system/storage.rst:58 msgid "" -"Your telephony system has to support this function. Zammad will send a " -"``reject`` response which will cause your telephony system to hang up the " -"call. To callers this usually will feel like the line is busy." +"Or provide your S3 configuration as an URL (which you can find at the end of " +"the file). Note: you can also provide this URL as environment variable (:" +"docs:`see system documentation `) without using this yml-file." msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:14 +#: ../settings/system/storage.rst:62 msgid "" -"Provide a meaningful note for your fellow administrators to remind yourself " -"why you've chosen to block the number." +"We recommend the deletion of the not used configuration style to avoid " +"inconsistencies." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 -#: ../system/integrations/cti/includes/outbound-calls.include.rst:17 -#: ../system/integrations/cti/sipgate.rst:40 -msgid "Outbound" +#: ../settings/system/storage.rst:65 +msgid "Restart Zammad so the config file / environment variable is loaded" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:1 +#: ../settings/system/storage.rst:66 msgid "" -"In many cases you may want to use a different caller ID depending on the " -"destination you're calling. This may apply due to specific connection rates " -"to other countries or because you want your customer to feel you're calling " -"from the same country." +"Set the \"Storage Method\" in Zammad to ``Simple Storage (S3)`` in Settings " +"> System > Storage and click on \"Submit\". After that, Zammad checks your " +"configuration and the connection to the service and will raise an error " +"message if something is wrong." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:6 -msgid "This option expects ``E.164`` number formats." +#: ../settings/system/storage.rst:72 +msgid "A very simple storage configuration could look like this:" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 -msgid "Destination caller ID" +#: ../settings/system/storage.rst:85 +msgid "" +"Before setting the storage method to ``Simple Storage (S3)`` (step 4), " +"please make sure to have a working setup." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:5 -msgid "The caller ID or number you're trying to call." +#: ../settings/system/storage.rst:88 +msgid "" +"You can verify this by running ``rails r 'Rails.logger = Logger.new(STDOUT); " +"pp Store::Provider::S3.ping?'`` in your Zammad directory. If everything is " +"fine, you should see ``true``, else you should see ``false`` and a simple " +"error message." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:7 -msgid "You can use wildcards for e.g. country specific outbound numbers like:" +#: ../settings/system/storage.rst:93 +msgid "" +"If you installed Zammad through a package manager (rather than from source), " +"replace ``rails r`` with ``zammad run rails r`` above. To learn more, see :" +"docs:`Administration via Console `." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:9 -msgid "``49*`` for Germany" -msgstr "" - -#: ../system/integrations/cti/includes/outbound-calls.include.rst:10 -msgid "``4930*`` for Berlin / Germany landlines" -msgstr "" - -#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 -msgid "``33*`` for France" +#: ../settings/ticket.rst:4 +msgid "" +"Here you can adjust general ticket settings. Additional ones for the ticket " +"composer interface can be found in the :doc:`/misc/composer`." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:15 -msgid "Set Outbound caller ID" +#: ../settings/ticket.rst:11 +msgid "Ticket Hook (default: ``Ticket#``)" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:14 -msgid "" -"The outbound caller ID to set (the number your customer sees on his display) " -"in ``E.164`` number format." +#: ../settings/ticket.rst:11 +msgid "The identifier for a ticket; *e.g.,* Ticket#, Call#, MyTicket#." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 -msgid "Provide a short description for fellow administrators." +#: ../settings/ticket.rst:38 +msgid "Ticket Hook Position (default: ``right``)" msgstr "" -#: ../system/integrations/cti/includes/generic-cti-support-note.includes.rst:3 +#: ../settings/ticket.rst:14 msgid "" -"This option requires your PBX to send a specific request to Zammad *before " -"dialing*. Please consult the :docs:`CTI API ` in case " -"you're not sure." +"With this setting you can decide (if) where to insert the ticket number." msgstr "" -#: ../system/integrations/cti/generic.rst:52 -#: ../system/integrations/cti/placetel.rst:54 -#: ../system/integrations/cti/sipgate.rst:59 -msgid "Other Settings" +#: ../settings/ticket.rst:20 +msgid "*Right*" msgstr "" -#: ../system/integrations/cti/includes/other-settings-intro.include.rst:1 +#: ../settings/ticket.rst:17 msgid "" -"Below you can find all available additional settings for this CTI " -"integration. For your overview we're sorting them by appearance and " -"reference their description first." +"This setting will add the ticket reference on the right site of the subject." msgstr "" -#: ../system/integrations/cti/includes/default-caller-id.include.rst:2 -#: ../system/integrations/cti/includes/default-caller-id.include.rst:1 -msgid "Default caller ID for outbound calls" +#: ../settings/ticket.rst:20 +msgid "Example: ``Some Subject [Ticket#12345]``" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:16 -#: ../system/integrations/cti/includes/records-caller-log.include.rst:15 -msgid "Shown records in caller log" +#: ../settings/ticket.rst:26 +msgid "*Left*" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:2 +#: ../settings/ticket.rst:23 msgid "" -"Allows you to set the number of shown caller log entries for all users. You " -"can choose from the following values:" +"This setting will add the ticket reference on the left site of the subject." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:5 -msgid "60 (default)" +#: ../settings/ticket.rst:26 +msgid "Example: ``[Ticket#12345] Some Subject``" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:6 -msgid "120" +#: ../settings/ticket.rst:29 +msgid "*None*" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:7 -msgid "180" +#: ../settings/ticket.rst:29 +msgid "This will completely remove ticket references from the subject." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:8 -msgid "240" +#: ../settings/ticket.rst:33 +msgid "" +"Please ensure to take a look at :doc:`/channels/email/settings` within the " +"email channel to ensure you have at least one reference that helps Zammad to " +"assign follow-ups correctly." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:9 -msgid "300" +#: ../settings/ticket.rst:37 +msgid "" +"Disabling this and not setting up any further follow up search will lead to " +"unexpected results!" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:11 -msgid "**🥵 Potential performance issue**" +#: ../settings/ticket.rst:65 +msgid "" +"Ticket Last Contact Behaviour (default: ``Use the start time of the last " +"customer thread (which may consist of multiple articles).``)" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:13 +#: ../settings/ticket.rst:41 msgid "" -"Setting this setting higher than 60 may cause serious performance issues on " -"very busy instances. Keep in mind that this setting causes Zammad to poll " -"and send up to 300 records to *all active agent sessions* in very short time " -"periods." +"This setting changes the way Zammad updates the ``Last Contact`` value of a " +"ticket. This is fairly important for overviews and what you expect upon " +"ticket updates of a customer." msgstr "" -#: ../system/integrations/cti/generic.rst:73 -msgid "Caller Log Filter" +#: ../settings/ticket.rst:52 +msgid "" +"Use the start time of the last customer thread (which may consist of " +"multiple articles)." msgstr "" -#: ../system/integrations/cti/generic.rst:55 +#: ../settings/ticket.rst:46 msgid "" -"This function allows you to provide call information based on e.g. queues " -"only to agents that really need the information." +"If this option is chosen, Zammad will update the last updated value just " +"once if a customer replies. After that, Zammad will wait for an agent to " +"react." msgstr "" -#: ../system/integrations/cti/generic.rst:58 +#: ../settings/ticket.rst:50 msgid "" -"Why? If you have a team for several countries or departments, you don't want " -"to bug your agents from other departments. Leaving these options empty will " -"fallback to showing everything to everyone." +"This comes in handy if you want to work tickets in the order of their first " +"update. This will not change ticket orders if customers decide to \"bump\" " +"the ticket affected." msgstr "" -#: ../system/integrations/cti/generic.rst:64 -msgid "Destination caller ID or Queue" +#: ../settings/ticket.rst:57 +msgid "Use the time of the very last customer article." msgstr "" -#: ../system/integrations/cti/generic.rst:63 +#: ../settings/ticket.rst:55 msgid "" -"This depends on your PBX and usually is either a queue ID, phone number or " -"extension." +"When setting this option, Zammad will always update the last updated value. " +"This means that if ordering by ``Last Update``, ticket orders will change if " +"customers \"bump\" the ticket." msgstr "" -#: ../system/integrations/cti/generic.rst:69 -msgid "Agents" +#: ../settings/ticket.rst:64 +msgid "Last contact value used on :doc:`/manage/overviews`" msgstr "" -#: ../system/integrations/cti/generic.rst:67 -msgid "" -"Select the agents that are responsible for the group. These agents will then " -"see caller log entries and call notifications fitting to said queue." +#: ../settings/ticket.rst:65 +msgid "Last contact value used on :doc:`/manage/trigger`" msgstr "" -#: ../system/integrations/cti/generic.rst:0 +#: ../settings/ticket.rst:88 msgid "" -"Screenshot showing the caller log filter table with pre filled sample data" +"Ticket Organization Reassignment (default: ``Update the most recent tickets." +"``)" msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:6 +#: ../settings/ticket.rst:68 msgid "" -"With recent logs Zammad allows you to view the latest calls for the CTI " -"functionality. This usually comes in handy, when you're looking for errors." +"This setting changes the way Zammad updates the organization field of the " +"tickets whenever the primary organization of a user is changed." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:0 -msgid "" -"Screenshot showing several incoming requests within Recent logs section." +#: ../settings/ticket.rst:74 +msgid "Update the most recent tickets." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:16 -msgid "I'm just here to clear floats up." +#: ../settings/ticket.rst:72 +msgid "" +"If this option is chosen, Zammad will update the 100 most recent tickets " +"where the user is the ticket customer. The ticket organization field will be " +"automatically set to the new primary organization of the user." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:20 -msgid "" -"By clicking on the entry of interest, Zammad will provide more details on " -"the call in question. You'll see the payload it received and also the " -"response that was sent." +#: ../settings/ticket.rst:88 +msgid "Do not update any tickets." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:0 +#: ../settings/ticket.rst:77 msgid "" -"Screenshot showing detailed information of a specific log entry of recent " -"logs" +"When choosing this option, Zammad will not update any tickets when the " +"user's primary organization is changed." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:31 -msgid "x" +#: ../settings/ticket.rst:80 +msgid "**Use with care!**" msgstr "" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 -#: ../system/integrations/cti/includes/troubleshooting.include.rst:9 -msgid "My Phone page stays blank, signalling does work..." +#: ../settings/ticket.rst:82 +msgid "" +"Using this option may lead to inconsistencies in the system as the ticket " +"organization may become decoupled from the ticket customer." msgstr "" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:5 +#: ../settings/ticket.rst:85 msgid "" -"If you've made sure that signalling works (check Recent logs) and your " -"Caller Log still stays empty, please ensure that you only configured one CTI " -"integration version. Specifically defining more than one agent mapping on " -"the different integration variants will be the issue." +"However, you may use this option if you wish to maintain :ref:`the shared " +"access ` to the ticket for all organization " +"members of the original organization of the customer." msgstr "" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 -msgid "Clear the not needed agent mapping and reload your browser page." +#: ../settings/ticket.rst:110 +msgid "Ticket Number Format (default: ``Increment (SystemID.Counter)``)" msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:1 +#: ../settings/ticket.rst:94 msgid "" -"By mapping your agents extension to their existing Zammad users, Zammad can " -"provide a new ticket dialog or open the user profile for the agent that " -"picks up the call." +"This setting defines the way Zammad's ticket number will look. Changing this " +"setting in production will cause follow up detection to fail." msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:5 -msgid "" -"This speeds up ticket aiding, no matter if it's for existing tickets or new " -"ones!" +#: ../settings/ticket.rst:102 +msgid "Increment (SystemID.Counter)" msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:8 +#: ../settings/ticket.rst:98 msgid "" -"To see it work from the agent's perspective, have a look on :user-docs:`user " -"documentation `." +"The increment value contains the SystemID (automatically generated during " +"installation) and a increment which counts up with every new Ticket. The " +"increment will automatically get another digit if needed." msgstr "" -#: ../system/integrations/cti/placetel.rst:2 -msgid "Placetel CTI" +#: ../settings/ticket.rst:102 +msgid "Examples: ``1010138``, ``1010139``" msgstr "" -#: ../system/integrations/cti/placetel.rst:16 -msgid "You need an administrative Placetel account for your organization." +#: ../settings/ticket.rst:110 +msgid "Date (Year.Month.Day.SystemID.Counter)" msgstr "" -#: ../system/integrations/cti/placetel.rst:17 -#: ../system/integrations/cti/sipgate.rst:20 +#: ../settings/ticket.rst:105 msgid "" -"Your Zammad instance must be allowed to communicate to external services." +"This version of the ticket number is fairly long. However, because it " +"contains the date of ticket creation, it also allows you to see when the " +"ticket has been created. You may feel familiar with this number format if " +"you've worked with OTRS already." msgstr "" -#: ../system/integrations/cti/placetel.rst:18 -msgid "Placetel must be able to reach your Zammad instance." +#: ../settings/ticket.rst:110 +msgid "Examples: ``201206231010138``, ``201206231010139``" msgstr "" -#: ../system/integrations/cti/placetel.rst:22 -msgid ":doc:`provider-configurations/placetel`" +#: ../settings/ticket.rst:137 +msgid "OPTIONS" msgstr "" -#: ../system/integrations/cti/placetel.rst:21 +#: ../settings/ticket.rst:113 msgid "" -"Learn how to configure Placetel to enable Zammad and Placetel to communicate " -"with each other." +"The below options allow you to further customize your ticket number. The " +"availability of options differ depending of the chosen ticket number format " +"above." msgstr "" -#: ../system/integrations/cti/placetel.rst:32 -msgid "" -"The here listed endpoint settings are relevant for the :doc:`integration " -"configuration with Placetel `." +#: ../settings/ticket.rst:122 +msgid "Checksum (default: ``no``)" msgstr "" -#: ../system/integrations/cti/placetel.rst:37 -#: ../system/integrations/i-doit.rst:53 -msgid "Endpoint" +#: ../settings/ticket.rst:118 +msgid "" +"If set to yes, we'll built a checksum to further \"unique\" the ticket " +"number of your system. If you're dealing with many other ticket systems this " +"might help to prevent false positive follow up detection on tickets." msgstr "" -#: ../system/integrations/cti/placetel.rst:36 -msgid "" -"This endpoint will be required for the Zammad integration within the " -"Placetel web interface." +#: ../settings/ticket.rst:122 +msgid "This will also add another digit to the ticket number." msgstr "" -#: ../system/integrations/cti/placetel.rst:41 -msgid "API Token" +#: ../settings/ticket.rst:137 +msgid "Min. size of Number (default: ``5``)" msgstr "" -#: ../system/integrations/cti/placetel.rst:40 +#: ../settings/ticket.rst:125 msgid "" -"You'll receive this token within the ``Web API`` menu. Make sure to copy " -"this value, it's only shown once!" +"This setting defines the minimum length of your ticket number. If your " +"counter is not yet high enough, Zammad will fill the number with zeros to " +"ensure the wanted length." msgstr "" -#: ../system/integrations/cti/placetel.rst:71 -#: ../system/integrations/cti/sipgate.rst:77 -msgid "Phone Extension to Agent Mapping" +#: ../settings/ticket.rst:129 +msgid "" +"Please note that the minimum length is ``3`` (SystemID + at least one digit " +"if below 10). Also, if the length is no longer long enough, the number will " +"automatically get one digit longer. Ticket-Numbers **do not overflow**, thus " +"it's save to keep it at 5 or set it lower if wanted." msgstr "" -#: ../system/integrations/cti/placetel.rst:0 -msgid "Screenshot showing sample user mappings in between Placetel and Zammad" +#: ../settings/ticket.rst:135 +msgid "" +"This option is only available if ticket number format is set to " +"``Increment``!" msgstr "" -#: ../system/integrations/cti/placetel.rst:64 -msgid "" -"You can find your agents Placetel username combination required within ⚙️ PBX " -"→ VoIP destinations. Within the \"Advanced settings\" section you're looking " -"for \"SIP user name\" and \"SIP server\"." +#: ../settings/ticket.rst:142 +msgid "Auto-Assignment" msgstr "" -#: ../system/integrations/cti/placetel.rst:68 -msgid "Combine these two like so: ``@``." +#: ../settings/ticket.rst:144 +msgid "" +"In a larger Zammad environment, it happens that several agents open the same " +"ticket at the same time. Although collision detection is then effective, the " +"efficiency of processing can be increased by means of the automatic " +"assignment of tickets when a ticket is opened." msgstr "" -#: ../system/integrations/cti/placetel.rst:0 -msgid "Sample VoIP credentials for a Placetel user" +#: ../settings/ticket.rst:149 +msgid "" +"The automatic assignment of tickets can be activated and configured in the " +"admin area under Settings > Ticket > Auto Assignment." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:2 -msgid "Setup Placetel connection for Zammad" +#: ../settings/ticket.rst:152 +msgid "" +"The auto assignment only works if the ticket has no owner yet. By default, " +"the agent can always reset the ticket owner to ``-`` if needed." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:6 +#: ../settings/ticket.rst:155 msgid "" -"This configuration step requires a *full* administrative Placetel account. " -"You may receive forbidden error messages with Placetel in case your " -"permissions are not high enough." +"If you want to use this function for only specific tickets, you can " +"configure the conditions accordingly to meet your requirement. By default " +"the condition affects all tickets with the state ``open``." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:10 +#: ../settings/ticket.rst:161 msgid "" -"The following actions can be configured via the `Placetel web interface " -"`_." +"If you need to exclude users (e.g. a group leader), you can search and " +"select the desired agents in the ``Exception Users`` list. The search " +"function in this area is only effective, if you have too many agents to " +"display at once to help you with the configuration." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:29 -msgid "Step 1: Activate Zammad integration" +#: ../settings/ticket.rst:167 +msgid "Notifications" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:14 +#: ../settings/ticket.rst:191 +msgid "Default Notifications" +msgstr "" + +#: ../settings/ticket.rst:170 msgid "" -"Within Integrations, scroll down to Partner integrations and select Zammad." +"This setting allows you to configure the default ticket notifications that " +"will be applied to all new agent users (incl. users who were just assigned " +"agent role). Simply change the notification matrix to desired state and " +"press **Save**." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:17 +#: ../settings/ticket.rst:175 msgid "" -"You can alternatively filter by \"Ticket Systems\" to reduce the number of " -"entries on the page. You'll still want to look for Partner integrations. 🤓" +"In case an agent already exists, their ticket notification preferences will " +"be preserved. Optionally, you can also **Apply current defaults to all " +"agents**." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:21 +#: ../settings/ticket.rst:181 msgid "" -"Within the Zammad integration now press \"Activate\". A new tab ``API`` " -"becomes available - open this tab." +"**Potential time-consuming action:** Applying default ticket notifications " +"to all agent users may take some time to complete, be patient! The exact " +"time will depend on the size of your system and the number of agents." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:24 +#: ../settings/ticket.rst:185 msgid "" -"Now tick \"Enable Call Control / Notify API\" and paste the Placetel " -"endpoint from your Zammad instance into the field \"URL of your API " -"endpoint\". Save to apply the settings" +"**Active agents only!** When current default ticket notifications are " +"applied, only active agent users are considered. In case an agent is re-" +"activated *after* this action, they will still have the old notification " +"configuration." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 -msgid "Screencast showing how to activate the Zammad integration" +#: ../settings/ticket.rst:190 +msgid "" +"In case you want to go back to the initial state of ticket notifications, " +"you can click on **Reset to default** button." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:51 -msgid "Step 2: Generate API Token for Placetel" +#: ../settings/ticket.rst:196 +msgid "Duplicate Detection" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:32 -msgid "" -"Go back to the integrations page and scroll down to \"Web API\". Generate a " -"new API token by using the \"Create a new API token\" button." +#: ../settings/ticket.rst:238 +msgid "Detect Duplicate Ticket Creation" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:37 +#: ../settings/ticket.rst:199 msgid "" -"If you already generated a token either use your existing token or reset it " -"by using above mentioned button. Placetel will ask you to conform this reset." +"This setting turns on the duplicate ticket detection mechanism during ticket " +"creation. If similar tickets are found in the system, a suitable warning " +"will be shown to the user trying to create a ticket." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:41 +#: ../settings/ticket.rst:206 +msgid "A Sample Duplicate Ticket Warning" +msgstr "" + +#: ../settings/ticket.rst:208 msgid "" -"Please keep in mind that existing API scripts may no longer work due to " -"token resets!" +"You can choose which ticket attributes will be matched by selecting them in " +"**Attributes to compare** field. Only if the ticket attribute value provided " +"by the user in the ticket create form is *equal* with the attribute in an " +"existing ticket, the warning will be shown." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:44 +#: ../settings/ticket.rst:213 +msgid "**Warning title** and **Warning message** are configurable as well." +msgstr "" + +#: ../settings/ticket.rst:215 msgid "" -"Copy the provided API token and insert it into the \"API Token\" field " -"within Zammad's Placetel integration." +"You can limit the detection only to certain user roles. By default, only " +"agents will see the warning." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:47 +#: ../settings/ticket.rst:218 msgid "" -"Apply your changes by using the \"Save\" button on the bottom of the " -"Placetel integration page and activate the Placetel integration." +"If you don't want to show the matched tickets as part of the warning, you " +"can set **Show matching ticket(s) in the warning** setting to *no*." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +#: ../settings/ticket.rst:221 msgid "" -"Screencast showing how to retrieve an API token from Placetel for Zammad" +"By default, **Permission level for looking up ticket** is set to *User*, " +"which means user permissions will be honored during sarch. The user will " +"see the warning only if tickets they have access to are matched. " +"Alternatively, you can set this setting to *System*, in which case the " +"search will happen within *all* tickets in the system, regardless of user " +"permissions." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:73 -#: ../system/integrations/cti/provider-configurations/sipgate.rst:77 -msgid "Step 3: Restrict the numbers to notify on" +#: ../settings/ticket.rst:227 +msgid "**🦺 Safety first!**" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:54 +#: ../settings/ticket.rst:229 msgid "" -"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " -"the the Integrations page of the Placetel web interface, go to \"Notify " -"API\"." +"Even if the permission level is set to *System*, the user will not be shown " +"the tickets they don't have access to in the warning, even if they match." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:58 +#: ../settings/ticket.rst:233 msgid "" -"Lower on the page Placetel allows you to restrict the numbers to notify on. " -"You'll find this within the \"External routing API\" part." +"However, just the confirmation about the existence of the tickets in the " +"system may be considered an unwanted information disclosure. Use this option " +"carefully!" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +#: ../settings/ticket.rst:237 msgid "" -"Screenshot showing a sample selection of phone numbers to use for the " -"Placetels notify API" +"Finally, you can configure between matching within **All tickets** or **Open " +"tickets** only by setting **Match tickets in following states**. Depending " +"on the current ticket state, a ticket may or not be matched." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:66 -msgid "" -"This menu point also provides a API request log from Placetel view. Just " -"open \"Recent responses of your API endpoint\" to learn more." +#: ../system/core-workflows.rst:2 +msgid "Core Workflows" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:69 +#: ../system/core-workflows.rst:4 msgid "" -"If you want to see Zammad's perspective, use the \"Recent Logs\" part from " -"within the Placetel integration page." +"Core Workflows allow you to adjust object attributes in many ways. For " +"example:" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 -msgid "Screenshot showing sample log entries for Placetels API calls to Zammad" +#: ../system/core-workflows.rst:7 +msgid "show / hide fields" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:77 -msgid "Step 4 (optional): Further configurations for Placetel" +#: ../system/core-workflows.rst:8 +msgid "adjust mandatory setting" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:76 +#: ../system/core-workflows.rst:9 +msgid "manipulate available options" +msgstr "" + +#: ../system/core-workflows.rst:11 msgid "" -"If needed, you can now configure Zammad's Placetel integration in more " -"detail. You can learn more about your options here: :ref:`Placetel " -"integration settings `." +"With this, you can provide exactly the information your users really need!" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:2 -msgid "Setup Sipgate connection for Zammad" +#: ../system/core-workflows.rst:15 +msgid "" +"If the pre-defined :doc:`/system/objects` are not enough, please add them " +"beforehand." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +#: ../system/core-workflows.rst:17 msgid "" -"Sipgate has no english web interface which is why this documentation page is " -"mixing up languages badly." +"If you experience slow or unreliable field updates, please see :ref:`Core " +"Workflow Ajax Modus `" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +#: ../system/core-workflows.rst:22 msgid "" -"Please also note that the availability of API addons highly depends on your " -"package trier. Usage of sipgate.io packages *is not free*, please check " -"their `pricing page `_ before!" +"This is a very enhanced functionality and can cause unexpected UI behavior. " +"Please ensure to test your use cases after configuration to reduce surprises." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:35 -msgid "Step 1: Book sipgate.io package" +#: ../system/core-workflows.rst:None +msgid "Dialogue for adding a new workflow" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:13 -msgid "Skip to step 2 if you already have the package booked!" +#: ../system/core-workflows/condition-operators.rst:2 +msgid "Core Workflow Condition Operators" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:15 -msgid "" -"Login to an administrative Sipgate account and navigate to " -"``Accountverwaltung``. You'll see several different options depending on " -"your booked packages. Select ``Verträge & Produkte`` to continue." -msgstr "" - -#: ../system/integrations/cti/provider-configurations/sipgate.rst:19 +#: ../system/core-workflows/condition-operators.rst:4 msgid "" -"Scroll down to the section ``Zusätzliche Produkte buchen`` and look for " -"``sipgate.io`` - select this product by using the ``Produkte anzeigen``-" -"Button." +"You might know that there is a separate section for explaining :doc:" +"`condition operators `. Head over there to " +"see a detailed explanation of many conditions and operators." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:23 +#: ../system/core-workflows/condition-operators.rst:8 msgid "" -"On the next page select either one of the ``sipgate.io`` packages or ``Push-" -"API Package Free``. Follow the dialogue by booking the addon. You'll be " -"returned to your contract overview and now should see the selected addon in " -"your list." +"Due to differences to other places in Zammad which are also using conditions " +"(e.g. triggers), you can find a dedicated description of operators for core " +"workflows below." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:30 +#: ../system/core-workflows/condition-operators.rst:12 msgid "" -"The availability for ``sipgate.io`` packages and their levels highly depends " -"on the overall account type and product you've booked with Sipgate." +"Be aware that the availability of the operators depends on the selected " +"attribute and its field type. Some of the operators may only be available " +"for system attributes (e.g. for \"tags\", \"active\")." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screencast showing the process on how to book the required sipgate.io addon" +#: ../system/core-workflows/condition-operators.rst:20 +msgid "Operator" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:52 -msgid "Step 2: Configure webhook for Zammad" +#: ../system/core-workflows/condition-operators.rst:22 +msgid "after (absolute)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:38 -msgid "" -"Within your ``Accountverwaltung`` navicate to your product ``sipgate.io``. " -"In the newly opened tab, switch from \"Clients\" to \"Webhooks\" and paste " -"the endpoint URLs from your Zammad instance like so:" +#: ../system/core-workflows/condition-operators.rst:23 +msgid "Matches if a date/time is after a specific point in time." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:42 -msgid "Inbound endpoint to \"Incoming\"" +#: ../system/core-workflows/condition-operators.rst:24 +msgid "after (relative)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:43 -msgid "Outbound endpoint to \"Outgoing\"" +#: ../system/core-workflows/condition-operators.rst:25 +msgid "Matches if a time span after a specified event has passed." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:47 -msgid "" -"Ensure to select at least one call group or phoneline within \"Sources\". " -"Other wise Sipgate will not indicate any incoming or outgoing calls to " -"Zammad." +#: ../system/core-workflows/condition-operators.rst:26 +msgid "before (absolute)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screencast showing how to add Zammad's endpoint URLs to sipgate.ios webhook " -"configuration" +#: ../system/core-workflows/condition-operators.rst:27 +msgid "Matches if a date/time is before a specific point in time." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:55 -msgid "" -"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " -"the Webhooks → URLs section of Sipgate you can select which *sources* " -"Sipgate should notify Zammad about in- and outgoing calls." +#: ../system/core-workflows/condition-operators.rst:28 +msgid "before (relative)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:59 -msgid "" -"Use either specific phone lines or use the option \"Use for all phonelines " -"and groups\" to notify Zammad about all existing lines of your Sipgate " -"account." +#: ../system/core-workflows/condition-operators.rst:29 +msgid "Matches if a time span after a specified event has not passed." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screenshot showing a sample selection of phone numbers to use for the " -"Sipgates webhooks API" +#: ../system/core-workflows/condition-operators.rst:30 +msgid "contains" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:68 -msgid "This section also allows you to enable a Debug log." +#: ../system/core-workflows/condition-operators.rst:31 +msgid "Matches if a specified value is present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "Screenshot showing an enabled Debug log option" +#: ../system/core-workflows/condition-operators.rst:33 +msgid "Matches if all of the specified values are present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:73 -msgid "" -"After enabling you can use the Debug log section to see all sent webhook " -"calls to Zammad. You'll also can see the response." +#: ../system/core-workflows/condition-operators.rst:35 +msgid "Matches if none of the specified values are present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screenshot showing sample log entries for Sipgates webhook calls to Zammad" +#: ../system/core-workflows/condition-operators.rst:36 +msgid "contains not" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:81 -msgid "Step 4 (optional): Further configurations for Sipgate" +#: ../system/core-workflows/condition-operators.rst:37 +msgid "Matches if a specified value is not present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:80 -msgid "" -"If needed, you can now configure Zammad's Sipgate integration in more " -"detail. You can learn more about your options here: :ref:`Sipgate " -"integration settings `." +#: ../system/core-workflows/condition-operators.rst:39 +msgid "Matches if one specified value is present." msgstr "" -#: ../system/integrations/cti/sipgate.rst:2 -msgid "Sipgate (sipgate.io)" +#: ../system/core-workflows/condition-operators.rst:41 +msgid "Matches if one specified value is not present." msgstr "" -#: ../system/integrations/cti/sipgate.rst:16 -msgid "You need an administrative Sipgate account for your organization." +#: ../system/core-workflows/condition-operators.rst:42 +msgid "does not match regex" msgstr "" -#: ../system/integrations/cti/sipgate.rst:17 -msgid "" -"Zammad requires a ``sipgate.io`` addon from the feature store (please note " -"that API calls are not free with Sipgate. Rates may apply and differ from " -"account to account)." +#: ../system/core-workflows/condition-operators.rst:43 +msgid "Matches if content doesn't fit to regex rule." msgstr "" -#: ../system/integrations/cti/sipgate.rst:21 -msgid "Sipgate must be able to reach your Zammad instance." +#: ../system/core-workflows/condition-operators.rst:44 +msgid "ends with" msgstr "" -#: ../system/integrations/cti/sipgate.rst:25 -msgid ":doc:`provider-configurations/sipgate`" +#: ../system/core-workflows/condition-operators.rst:45 +msgid "Matches if content ends with specified value." msgstr "" -#: ../system/integrations/cti/sipgate.rst:24 -msgid "" -"Learn how to configure Sipgate to enable Zammad and Sipgate to communicate " -"with each other." +#: ../system/core-workflows/condition-operators.rst:46 +msgid "ends with one of" msgstr "" -#: ../system/integrations/cti/sipgate.rst:33 -msgid "" -"Below endpoint settings affect the :doc:`sipgate.io configuration `." +#: ../system/core-workflows/condition-operators.rst:47 +msgid "Matches if content ends with one of the specified values." msgstr "" -#: ../system/integrations/cti/sipgate.rst:37 -msgid "This endpoint is required for incoming call hooks." +#: ../system/core-workflows/condition-operators.rst:48 +msgid "from (relative)" msgstr "" -#: ../system/integrations/cti/sipgate.rst:40 -msgid "This endpoint is required for outgoing call hooks." +#: ../system/core-workflows/condition-operators.rst:49 +msgid "Matches if date/time is after a period of time after an event." msgstr "" -#: ../system/integrations/cti/sipgate.rst:0 -msgid "Screenshot showing sample user mappings in between Sipgate and Zammad" +#: ../system/core-workflows/condition-operators.rst:51 +msgid "Matches if content is equal to a specified value." msgstr "" -#: ../system/integrations/cti/sipgate.rst:69 -msgid "" -"You can find your agent's Sipgate username within ``Accountverwaltung → " -"Benutzer``. You're looking for the SIP-ID." +#: ../system/core-workflows/condition-operators.rst:52 +msgid "is any of" msgstr "" -#: ../system/integrations/cti/sipgate.rst:0 -msgid "Sample VoIP credentials for a Sipgate user" +#: ../system/core-workflows/condition-operators.rst:53 +msgid "Matches if content is equal to any of specified values." msgstr "" -#: ../system/integrations/cti/sipgate.rst:77 -msgid "Users with several devices also have several SIP-IDs." +#: ../system/core-workflows/condition-operators.rst:54 +msgid "is modified" msgstr "" -#: ../system/integrations/elasticsearch.rst:2 -msgid "Elasticsearch (SaaS)" +#: ../system/core-workflows/condition-operators.rst:55 +msgid "Matches if content is modified." msgstr "" -#: ../system/integrations/elasticsearch.rst:4 -msgid "" -"The Elasticsearch integration allows you to create a read-only user to use " -"with your favorite reporting tool (e.g. like Grafana)." +#: ../system/core-workflows/condition-operators.rst:57 +#: ../system/core-workflows/condition-operators.rst:61 +msgid "True from the moment of changing content until form submit." msgstr "" -#: ../system/integrations/elasticsearch.rst:7 -msgid "" -"If you want to take full advantage of the Zammad reporting, have a look at " -"our :docs:`Grafana ` " -"setup page as well." +#: ../system/core-workflows/condition-operators.rst:58 +msgid "is modified to" msgstr "" -#: ../system/integrations/elasticsearch.rst:11 -#: ../system/subscription/index.rst:7 -msgid "**🚧 Hosted environment specific 🚧**" +#: ../system/core-workflows/condition-operators.rst:59 +msgid "Matches if content is modified to a specific value." msgstr "" -#: ../system/integrations/elasticsearch.rst:13 -msgid "" -"This integration is only available for Hosted setups. In order to use " -"Elasticsearch you'll need the **Plus** subscription." +#: ../system/core-workflows/condition-operators.rst:62 +msgid "is none of" msgstr "" -#: ../system/integrations/elasticsearch.rst:16 -msgid "" -"Self hosted users have all the control over their self hosted Elasticsearch " -"instances." +#: ../system/core-workflows/condition-operators.rst:63 +msgid "Matches if content is none of any specified values." msgstr "" -#: ../system/integrations/elasticsearch.rst:None -msgid "Elasticsearch integration page on SaaS environments" +#: ../system/core-workflows/condition-operators.rst:65 +msgid "Matches if content is not equal to a specified value." msgstr "" -#: ../system/integrations/elasticsearch.rst:27 -msgid "" -"Please note the following limitations of Elasticsearch access on hosted " -"environments:" +#: ../system/core-workflows/condition-operators.rst:67 +msgid "Matches if content is present." msgstr "" -#: ../system/integrations/elasticsearch.rst:30 -msgid "access to the Elasticsearch index is read-only access" +#: ../system/core-workflows/condition-operators.rst:68 +msgid "just changed" msgstr "" -#: ../system/integrations/elasticsearch.rst:31 -msgid "currently you're limited to user only" +#: ../system/core-workflows/condition-operators.rst:69 +msgid "Matches if content has changed." msgstr "" -#: ../system/integrations/elasticsearch.rst:32 +#: ../system/core-workflows/condition-operators.rst:71 +#: ../system/core-workflows/condition-operators.rst:75 msgid "" -"Reporting tools that require to write into the indexes (like Kibana) are not " -"supported" +"Only true for the moment of changing content until next form field action/" +"click." msgstr "" -#: ../system/integrations/elasticsearch.rst:34 -msgid "IP access restriction is currently not yet supported" +#: ../system/core-workflows/condition-operators.rst:72 +msgid "just changed to" msgstr "" -#: ../system/integrations/elasticsearch.rst:37 -msgid "Activating Elasticsearch Access" +#: ../system/core-workflows/condition-operators.rst:73 +msgid "Matches if content has changed to a specified value." msgstr "" -#: ../system/integrations/elasticsearch.rst:39 -msgid "" -"By default external access to your Elasticsearch index is not active. You " -"can enable the integration at any time if needed." +#: ../system/core-workflows/condition-operators.rst:76 +msgid "matches regex" msgstr "" -#: ../system/integrations/elasticsearch.rst:42 -msgid "" -"Please ensure to note down the password provided - you won't have access to " -"it afterwards." +#: ../system/core-workflows/condition-operators.rst:77 +msgid "Matches if value fits to regex rule." msgstr "" -#: ../system/integrations/elasticsearch.rst:None -msgid "Screencast showing activation of Elasticsearch integration" -msgstr "" - -#: ../system/integrations/elasticsearch.rst:51 -msgid "Connection Settings" +#: ../system/core-workflows/condition-operators.rst:79 +msgid "Matches if no content is present." msgstr "" -#: ../system/integrations/elasticsearch.rst:53 -msgid "" -"This section holds the most important general information for accessing your " -"Elasticsearch indexes - such as:" +#: ../system/core-workflows/condition-operators.rst:80 +msgid "starts with" msgstr "" -#: ../system/integrations/elasticsearch.rst:57 -msgid "A unique subdomain that does not tell your real instance URL." +#: ../system/core-workflows/condition-operators.rst:81 +msgid "Matches if content starts with specified value." msgstr "" -#: ../system/integrations/elasticsearch.rst:61 -msgid "Software" +#: ../system/core-workflows/condition-operators.rst:82 +msgid "starts with one of" msgstr "" -#: ../system/integrations/elasticsearch.rst:60 -msgid "" -"The major version of the search index being used. This is required by some " -"Reporting tools like Grafana." +#: ../system/core-workflows/condition-operators.rst:83 +msgid "Matches if content starts with one of the specified values." msgstr "" -#: ../system/integrations/elasticsearch.rst:64 -msgid "Authentication" +#: ../system/core-workflows/condition-operators.rst:84 +msgid "till (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:64 -msgid "The authentication type being supported. ``Basic Authentication``" +#: ../system/core-workflows/condition-operators.rst:85 +msgid "Matches if date/time is before a period of time before an event." msgstr "" -#: ../system/integrations/elasticsearch.rst:67 -msgid "Available Indexes" +#: ../system/core-workflows/condition-operators.rst:86 +msgid "today" msgstr "" -#: ../system/integrations/elasticsearch.rst:69 -msgid "" -"Within this section we're displaying the -in our opinion- most important " -"indexes for a Zammad instance." +#: ../system/core-workflows/condition-operators.rst:87 +msgid "Matches if date/time is today." msgstr "" -#: ../system/integrations/elasticsearch.rst:72 -msgid "" -"If you require all indexes or our listing is not good enough for you, point " -"your browser to the URL we're providing and append ``/_aliases?" -"pretty=true``. The result should look like this: ``https://.zammad.com/" -"_aliases?pretty=true``." +#: ../system/core-workflows/condition-operators.rst:88 +msgid "within last (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:77 +#: ../system/core-workflows/condition-operators.rst:89 msgid "" -"Your browser will automatically ask for your credentials - you'll then see " -"something like this:" -msgstr "" - -#: ../system/integrations/elasticsearch.rst:125 -msgid "Credentials" +"Matches if date/time content is within specified period of time before now." msgstr "" -#: ../system/integrations/elasticsearch.rst:127 -msgid "" -"Within this section Zammad displays your available users. The password is " -"provided once (upon activation) and cannot be retrieved after that." +#: ../system/core-workflows/condition-operators.rst:91 +msgid "within next (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:131 +#: ../system/core-workflows/condition-operators.rst:92 msgid "" -"If you need to change or reset your Elasticsearch user password, use the " -"\"Reset password\" button in the credentials table. Doing so creates a brand " -"new password for the account in question. This change is immediate, keep in " -"mind that this may affect third party tools connected to your instance." +"Matches if date/time content is within specified period of time after now." msgstr "" -#: ../system/integrations/exchange.rst:2 -msgid "Exchange" +#: ../system/core-workflows/how-do-they-work.rst:2 +msgid "How do they work?" msgstr "" -#: ../system/integrations/exchange.rst:4 +#: ../system/core-workflows/how-do-they-work.rst:4 msgid "" -"With Zammad's Exchange integration, you can easily use existing address " -"books without having to update more than one source." +"Core Workflows are executed according to their priority. If two workflows " +"have the same priority, they are executed in alphabetical order based on " +"their **name**." msgstr "" -#: ../system/integrations/exchange.rst:7 +#: ../system/core-workflows/how-do-they-work.rst:8 msgid "" -"However, you should refrain from syncing all addresses, as the results may " -"not be what you expect (Exchange collects huge amounts of addresses). A " -"central address book of your company to sync makes more sense, as you can " -"ensure that Zammad gets only the data you need and want. Apart from this, it " -"is even not possible to sync the Global Address List (GAL) of your Exchange " -"system with Zammad." +"Because of the way Core Workflows work, all changes to attributes are " +"checked with the application server - please see :doc:`limitations` for " +"possible issues." msgstr "" -#: ../system/integrations/exchange.rst:16 +#: ../system/core-workflows/how-do-they-work.rst:12 msgid "" -"**Exchange and LDAP:** The exchange sync can be overruled by Zammad's LDAP " -"integration. If you have the same users in both sources, the LDAP version " -"will always be Zammad's pick." +"Below we're talking about settings that are important and not self-" +"explanatory." msgstr "" -#: ../system/integrations/exchange.rst:19 +#: ../system/core-workflows/how-do-they-work.rst:17 msgid "" -"**One way sync:** the Exchange sync is one way. Exchange => Zammad. Changes " -"to your users inside of Zammad might be overwritten by the Exchange sync." +"Choose the object context you want to run the workflow in. This will decide " +"on your available attributes and actions." msgstr "" -#: ../system/integrations/exchange.rst:24 -msgid "" -"To configure Exchange integration, simply go to the System > Integrations > " -"Exchange in the admin panel. Press \"change\" and follow the wizard for " -"adding the needed Exchange information to Zammad. On the last two steps " -"Zammad will ask you for the address book(s) and your desired attribute " -"mapping. By default, Zammad only maps email address, first- and lastname. " -"Technically, you can map any Exchange object to a Zammad user object (this " -"also works for custom objects!)." +#: ../system/core-workflows/how-do-they-work.rst:20 +msgid "Ticket objects also have access to the ticket customer." msgstr "" -#: ../system/integrations/exchange.rst:35 +#: ../system/core-workflows/how-do-they-work.rst:25 msgid "" -"If the SSL verification fails while connecting to Exchange, Zammad will ask " -"you to turn it off temporarily." +"Choose in which situation the workflow is applied. Contexts can be combined " +"to avoid duplicate workflows." msgstr "" -#: ../system/integrations/exchange.rst:38 -msgid "" -"Please be aware that **turning off SSL verification is a security risk**. It " -"should only be used temporarily or for testing purposes. If turned off, " -"there is no verification of the certificate, which means that every " -"presented certificate will be accepted." +#: ../system/core-workflows/how-do-they-work.rst:30 +msgid "Creation mask" msgstr "" -#: ../system/integrations/exchange.rst:43 +#: ../system/core-workflows/how-do-they-work.rst:29 msgid "" -"After pressing Continue, Zammad will check if the configuration is okay. You " -"can then enable Exchange and start your first sync. The sync will then run " -"hourly - if you need to change mappings or the address book(s), you can " -"change the configuration at any time." +"If selected, your conditions and actions will affect all applicable creation " +"masks." msgstr "" -#: ../system/integrations/exchange.rst:50 -msgid "" -"After the sync has finished, you can find the new Exchange contacts under " -"\"Users\". Zammad integrates them just as normal users." +#: ../system/core-workflows/how-do-they-work.rst:34 +msgid "Edit mask" msgstr "" -#: ../system/integrations/exchange.rst:55 +#: ../system/core-workflows/how-do-they-work.rst:33 msgid "" -"In some cases you might see unique IDs as \"Login\" instead of the email " -"address. This is normal and doesn't affect the login or email mapping for " -"that entry." +"If selected, your conditions and actions will affect all applicable edit " +"masks." msgstr "" -#: ../system/integrations/github.rst:4 +#: ../system/core-workflows/how-do-they-work.rst:39 msgid "" -"Use GitHub integration to track GitHub issues directly within Zammad " -"tickets. Add issue hyperlinks and get a live summary of metadata like status " -"(open/closed), assignee, labels, and more." -msgstr "" - -#: ../system/integrations/github.rst:8 -msgid "Please note that our GitHub integration does not support pull requests." +"Zammad differentiates between selected and saved conditions. These can be " +"combined wherever needed." msgstr "" -#: ../system/integrations/github.rst:None -msgid "Integration page for GitHub" +#: ../system/core-workflows/how-do-they-work.rst:42 +msgid "**⚠️ Restrict workflows to specific roles if needed!**" msgstr "" -#: ../system/integrations/github.rst:18 +#: ../system/core-workflows/how-do-they-work.rst:44 msgid "" -"In your GitHub settings, create a new API token under **Developer settings > " -"Personal access tokens > Generate new token**. Leave the **Scopes** section " -"empty." +"By default and unless configured in conditions, workflow rules are executed " +"for **all roles**. This also affects your customers!" msgstr "" -#: ../system/integrations/github.rst:0 ../system/integrations/gitlab.rst:0 -msgid "Screencast showing how to create a new API token" +#: ../system/core-workflows/how-do-they-work.rst:50 +msgid "Selected Conditions" msgstr "" -#: ../system/integrations/github.rst:27 -msgid "Create a new API key with no scopes/privileges." +#: ../system/core-workflows/how-do-they-work.rst:48 +msgid "" +"These conditions are based on form values and match if an appropriate " +"selection is made (e.g. choosing another group in the ticket without " +"saving). This applies for drafts (active selection) and currently saved " +"values." msgstr "" -#: ../system/integrations/github.rst:29 -msgid "🔒 **Will this work for private repos?**" +#: ../system/core-workflows/how-do-they-work.rst:64 +msgid "Saved Conditions" msgstr "" -#: ../system/integrations/github.rst:31 +#: ../system/core-workflows/how-do-they-work.rst:53 msgid "" -"No. To link private repo issues, **use the** ``repo`` **scope instead**. " -"Bear in mind that the resulting token will have `lots of permissions that it " -"doesn't actually need `_, which presents a security risk if your token ever falls into " -"the wrong hands." +"These conditions only match if the selected values are stored in the " +"database. It ignores the current value or selection of the field, as long as " +"the changes are not saved (e.g. performing field operations for an existing " +"ticket, which is viewed/opened by an agent)." msgstr "" -#: ../system/integrations/github.rst:37 +#: ../system/core-workflows/how-do-they-work.rst:60 msgid "" -"Unfortunately, because of how GitHub's OAuth token scopes are set up, this " -"is the only way to link issues on private repos." -msgstr "" - -#: ../system/integrations/github.rst:40 -msgid "Enter your new API token in Zammad and enable GitHub integration." +"Keep in mind that the value has to be available in the situation where you " +"need it. Otherwise the condition won't match." msgstr "" -#: ../system/integrations/github.rst:0 -msgid "Screencast showing how to configure Zammad's GitHub integration" +#: ../system/core-workflows/how-do-they-work.rst:63 +msgid "" +"Example: you can't perform any actions with *saved condition* on a ticket in " +"creation, because there are no saved values at that time." msgstr "" -#: ../system/integrations/github.rst:47 +#: ../system/core-workflows/how-do-they-work.rst:66 msgid "" -"Use the default API endpoint (``https://api.github.com/graphql``) unless " -"you're using GitHub Enterprise Server." +"You can find a description of the condition operators for core workflows :" +"doc:`here `." msgstr "" -#: ../system/integrations/github.rst:50 +#: ../system/core-workflows/how-do-they-work.rst:72 msgid "" -"Once completed, a new GitHub issues tab will appear in the ticket pane. 🎉" +"Which actions should we run on the relevant fields? The possible actions " +"depend on the object type. However, usually you can at least change the " +"visibility and whether the field is mandatory." msgstr "" -#: ../system/integrations/github.rst:59 ../system/integrations/gitlab.rst:52 -msgid "Token verification is taking a long time" +#: ../system/core-workflows/how-do-they-work.rst:76 +msgid "Be aware that actions are not available for **related** context." msgstr "" -#: ../system/integrations/github.rst:56 ../system/integrations/gitlab.rst:49 +#: ../system/core-workflows/how-do-they-work.rst:78 msgid "" -"Slight delays are normal (<2 min.), especially for systems under heavy load." +"**Example:** Let's assume you are working in the ticket context. While you " +"can have customer *conditions*, you *can't adjust* objects with actions in " +"that scope. That's because this wouldn't have any impact on the ticket " +"dialog. Of course all ticket attributes (state, owner, ...) are available." msgstr "" -#: ../system/integrations/github.rst:58 +#: ../system/core-workflows/how-do-they-work.rst:84 msgid "" -"Self-hosted administrators, please check your network settings to ensure " -"that your Zammad server can reach ``api.github.com``." +"Please also have a look at our :doc:`limitations` to be safe from surprises." msgstr "" -#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 -msgid "I reloaded the page and now the API token is gone" +#: ../system/core-workflows/how-do-they-work.rst:88 +msgid "Available Operators" msgstr "" -#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 -msgid "" -"This may indicate that Zammad is still verifying your API token. Try " -"reloading the page again in a couple minutes." -msgstr "" - -#: ../system/integrations/gitlab.rst:2 -msgid "GitLab" -msgstr "" - -#: ../system/integrations/gitlab.rst:4 -msgid "" -"Use GitLab integration to track GitLab issues directly within Zammad " -"tickets. Add issue hyperlinks and get a live summary of metadata like status " -"(open/closed), assignee, labels, and more." +#: ../system/core-workflows/how-do-they-work.rst:90 +msgid "The availability of operators depends on the object type and scope." msgstr "" -#: ../system/integrations/gitlab.rst:8 +#: ../system/core-workflows/how-do-they-work.rst:94 msgid "" -"Please note that our GitLab integration does not support merge requests." -msgstr "" - -#: ../system/integrations/gitlab.rst:None -msgid "Integration page for GitLab" +"Please note that actions may or may not restrict API based access to " +"attributes. We're displaying the following icons for your overview to " +"understand these limits better:" msgstr "" -#: ../system/integrations/gitlab.rst:18 -msgid "" -"In your GitLab preferences, create a new API token under **Access Tokens**." +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|api| This icon indicates the action affects the API." msgstr "" -#: ../system/integrations/gitlab.rst:20 -msgid "Under **Select scopes**, choose ``read_api`` only." +#: ../system/core-workflows/how-do-they-work.rst:163 +msgid "api" msgstr "" -#: ../system/integrations/gitlab.rst:27 -msgid "🔒 **If you wish to link issues on any private repos...**" +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|ui| This icon indicates the action only affects the web interface." msgstr "" -#: ../system/integrations/gitlab.rst:29 -msgid "Your API token must belong to an account with access to those repos." +#: ../system/core-workflows/how-do-they-work.rst:167 +msgid "ui" msgstr "" -#: ../system/integrations/gitlab.rst:31 -msgid "Enter your new API token in Zammad and enable GitLab integration." +#: ../system/core-workflows/how-do-they-work.rst:102 +msgid "show |ui|" msgstr "" -#: ../system/integrations/gitlab.rst:0 -msgid "Screencast showing how to configure Zammad's GitLab integration" +#: ../system/core-workflows/how-do-they-work.rst:102 +msgid "Display the chosen field. Allows setting of values." msgstr "" -#: ../system/integrations/gitlab.rst:40 -msgid "" -"Use the default API endpoint (``https://gitlab.com/api/graphql``) unless " -"you're a self-hosted GitLab user." +#: ../system/core-workflows/how-do-they-work.rst:109 +msgid "hide |ui|" msgstr "" -#: ../system/integrations/gitlab.rst:43 +#: ../system/core-workflows/how-do-they-work.rst:105 msgid "" -"Once completed, a new GitLab issues tab will appear in the ticket pane. 🎉" +"Hide the chosen field. However, it technically still allows setting the " +"field." msgstr "" -#: ../system/integrations/gitlab.rst:51 +#: ../system/core-workflows/how-do-they-work.rst:108 msgid "" -"Self-hosted administrators, please check your network settings to ensure " -"that your Zammad server can reach ``gitlab.com``." +"Please note that the field is **not** gone and still contains an existing " +"value (if set)! Consider *remove* instead, if you want this field to be gone." msgstr "" -#: ../system/integrations/i-doit.rst:2 -msgid "i-doit" +#: ../system/core-workflows/how-do-they-work.rst:112 +msgid "remove |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:4 -msgid "" -"`i-doit `_ is an open-source **configuration " -"management database** - in other words, a tool for keeping tabs on every " -"single piece of your physical and digital infrastructure, from network " -"equipment to virtual machines on down to the faceplates on your rack shelves " -"and more." +#: ../system/core-workflows/how-do-they-work.rst:112 +msgid "Entirely removes the field. The field value will not be evaluated." msgstr "" -#: ../system/integrations/i-doit.rst:10 -msgid "" -"What's that got to do with Zammad? Well, if you used tickets to track issues " -"with all that hardware, you might start wishing there was a way they could " -"talk to each other." +#: ../system/core-workflows/how-do-they-work.rst:115 +msgid "set mandatory |ui| |api|" msgstr "" -#: ../system/integrations/i-doit.rst:14 -msgid "Zammad gives you two:" +#: ../system/core-workflows/how-do-they-work.rst:115 +msgid "Sets the field to mandatory." msgstr "" -#: ../system/integrations/i-doit.rst:17 -msgid "1. Add i-doit Links to Zammad Tickets" +#: ../system/core-workflows/how-do-they-work.rst:118 +msgid "set optional |ui| |api|" msgstr "" -#: ../system/integrations/i-doit.rst:20 ../system/integrations/i-doit.rst:80 -msgid "What Users See" +#: ../system/core-workflows/how-do-they-work.rst:118 +msgid "Sets the field to optional." msgstr "" -#: ../system/integrations/i-doit.rst:26 -msgid "i-doit integration in Zammad's ticket pane" +#: ../system/core-workflows/how-do-they-work.rst:124 +msgid "add option |ui| |api|" msgstr "" -#: ../system/integrations/i-doit.rst:26 -msgid "" -"The i-doit integration will appear under a new 🖨 tab in the ticket pane." +#: ../system/core-workflows/how-do-they-work.rst:121 +msgid "Allows adding options to tree selects or selects." msgstr "" -#: ../system/integrations/i-doit.rst:28 +#: ../system/core-workflows/how-do-they-work.rst:123 msgid "" -"i-doit integration puts a new tab in Zammad's ticket pane where you can add " -"links to existing i-doit devices for easy reference. (See our :user-docs:" -"`user documentation ` to learn " -"how it works in practice)." +"You have to use the \"remove option\" before performing this action. It " +"allows you to use *existing* configured values." msgstr "" -#: ../system/integrations/i-doit.rst:36 ../system/integrations/i-doit.rst:93 -msgid "How to Set it Up" +#: ../system/core-workflows/how-do-they-work.rst:128 +msgid "remove option |ui| |api|" msgstr "" -#: ../system/integrations/i-doit.rst:38 +#: ../system/core-workflows/how-do-they-work.rst:127 msgid "" -"It requires i-doit's `API Add-on `_. Make sure to have it properly set up. Use the following setting:" +"Allows removing options from tree selects or selects. It allows you to use " +"*existing* configured values." msgstr "" -#: ../system/integrations/i-doit.rst:42 -msgid "Active: ``Yes``" +#: ../system/core-workflows/how-do-they-work.rst:134 +msgid "set fixed to |ui| |api|" msgstr "" -#: ../system/integrations/i-doit.rst:43 -msgid "Enforce authentication by username and password: ``No``" +#: ../system/core-workflows/how-do-they-work.rst:131 +msgid "Reduces the available options by your selection." msgstr "" -#: ../system/integrations/i-doit.rst:45 +#: ../system/core-workflows/how-do-they-work.rst:133 msgid "" -"To set it up, enable the integration in the Zammad admin panel under " -"**System > Integrations > i-doit**:" +"This reduces your workflows in terms of *add option* and *remove option*." msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "i-doit settings within the integration pages" +#: ../system/core-workflows/how-do-they-work.rst:137 +msgid "fill in |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:53 -msgid "The root URL of your i-doit installation." +#: ../system/core-workflows/how-do-they-work.rst:137 +msgid "Allows filling in of string and integer fields with your values." msgstr "" -#: ../system/integrations/i-doit.rst:62 -msgid "API token" +#: ../system/core-workflows/how-do-they-work.rst:141 +msgid "fill in empty |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:56 +#: ../system/core-workflows/how-do-they-work.rst:140 msgid "" -"Found in the i-doit admin panel under **Interfaces / external data > JSON-" -"RPC API > Common Settings**." +"Allows filling in of string and integer fields with your values **if the " +"field is empty**." msgstr "" -#: ../system/integrations/i-doit.rst:0 -msgid "i-doit administration interface with API configuration" +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "select |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:67 -msgid "Client ID" +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "Select a specific value within a select, tree select or boolean field." msgstr "" -#: ../system/integrations/i-doit.rst:65 -msgid "A unique name to identify Zammad within i-doit." +#: ../system/core-workflows/how-do-they-work.rst:153 +msgid "auto select |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:67 -msgid "(Zammad does not require you to enter a value here, but i-doit might!)" +#: ../system/core-workflows/how-do-they-work.rst:147 +msgid "Helps users with tree select and select fields:" msgstr "" -#: ../system/integrations/i-doit.rst:70 +#: ../system/core-workflows/how-do-they-work.rst:149 msgid "" -"Here you can decide if the certificate of your i-doit system has to be " -"verified or not. In case you are using custom certificates, please have a " -"look at :doc:`how to add them to Zammad `." -msgstr "" - -#: ../system/integrations/i-doit.rst:77 -msgid "2. List / Create Zammad Tickets in i-doit" +"If the field has only one option available for selection and no value yet, " +"the value will be automatically set." msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "Zammad integration in i-doit's device view" +#: ../system/core-workflows/how-do-they-work.rst:152 +msgid "" +"This option only works if you have one value and doesn't work if there is " +"more than one option available." msgstr "" -#: ../system/integrations/i-doit.rst:86 -msgid "" -"i-doit's ticket system integration gives you a way to see all the tickets " -"for a given device without ever leaving i-doit. (See our :user-docs:`user " -"documentation ` to learn how it " -"works in practice)." +#: ../system/core-workflows/how-do-they-work.rst:157 +msgid "set readonly |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:95 +#: ../system/core-workflows/how-do-they-work.rst:156 msgid "" -"Enable this integration in the i-doit admin panel under **Interfaces / " -"external data > Trouble Ticket System (TTS) > Configuration**:" +"Allows you to display an attribute as read only (which means no changes are " +"possible)." msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "i-doit administration interface with TTS configuration" +#: ../system/core-workflows/how-do-they-work.rst:161 +msgid "unset readonly |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:104 -msgid "TTS-Type" +#: ../system/core-workflows/how-do-they-work.rst:160 +msgid "" +"In case a workflow set the field in question to read only, you can undo this " +"with option above." msgstr "" -#: ../system/integrations/i-doit.rst:104 -msgid "``Zammad``" +#: ../system/core-workflows/how-do-they-work.rst:172 +msgid "Stop after match" msgstr "" -#: ../system/integrations/i-doit.rst:115 -msgid "Username / Password" +#: ../system/core-workflows/how-do-they-work.rst:174 +msgid "" +"Here you can decide if other workflows are executed after the current one." msgstr "" -#: ../system/integrations/i-doit.rst:107 -msgid "Login credentials for a Zammad agent." +#: ../system/core-workflows/how-do-they-work.rst:176 +msgid "" +"If set to ``no`` (default), further workflows will be executed if they match " +"the condition. In this case, it is possible that your actions from the " +"current workflow can be overwritten by another workflow." msgstr "" -#: ../system/integrations/i-doit.rst:109 +#: ../system/core-workflows/how-do-they-work.rst:180 msgid "" -"This agent must have **read permission** for all :doc:`groups ` that plan on using the i-doit integration." +"If set to ``yes``, no further worflows will be executed after the current " +"one." msgstr "" -#: ../system/integrations/i-doit.rst:113 +#: ../system/core-workflows/how-do-they-work.rst:184 +msgid "Priority" +msgstr "Приоритет" + +#: ../system/core-workflows/how-do-they-work.rst:186 msgid "" -"You may even wish to create a dedicated agent account just for this " -"integration (otherwise, if the agent ever changes her password, you will " -"have to remember to update it here)." +"You can define the sequence, in which the workflows are executed. The " +"default value is ``500``." msgstr "" -#: ../system/integrations/i-doit.rst:117 -msgid "URL incl. protocol" +#: ../system/core-workflows/how-do-they-work.rst:189 +msgid "" +"The workflows are executed in ascending order by their priority. That means " +"lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." msgstr "" -#: ../system/integrations/i-doit.rst:118 -msgid "``https://your.zammad.domain``" -msgstr "" - -#: ../system/integrations/index.rst:2 -msgid "Integrations" -msgstr "" +#: ../system/core-workflows/learn-by-example.rst:2 +#, fuzzy +msgid "Learn by Example" +msgstr "Пример" -#: ../system/integrations/index.rst:4 +#: ../system/core-workflows/learn-by-example.rst:4 msgid "" -"Zammad offers numerous integrations that add rich features to your instance." +"This page provides some basic examples for Core Workflows. Of course you can " +"build much more complex workflows if needed." msgstr "" -#: ../system/integrations/index.rst:6 -msgid "We're still working on this part of our documentation, stay tight!" +#: ../system/core-workflows/learn-by-example.rst:7 +msgid "" +"To learn about Core Workflows in detail, first go to :doc:`how-do-they-work`." msgstr "" -#: ../system/integrations/index.rst:10 -msgid "Integrations for Phone Systems" +#: ../system/core-workflows/learn-by-example.rst:10 +msgid "Group Based Examples" msgstr "" -#: ../system/integrations/index.rst:14 +#: ../system/core-workflows/learn-by-example.rst:12 msgid "" -"Your VoIP provider or telephony system is not listed? Possibly your provider " -"supports Zammad by using the generic CTI - if you're unsure ask your " -"provider." +"All following workflows have the same base configurations. The workflow may " +"not use them all." msgstr "" -#: ../system/integrations/index.rst:18 -msgid "" -"Provider does not support Zammad? Consider creating a `feature request in " -"the Zammad Community `_." +#: ../system/core-workflows/learn-by-example.rst:15 +msgid "Groups:" msgstr "" -#: ../system/integrations/index.rst:31 -msgid "Integrations for Authentication and Customers" +#: ../system/core-workflows/learn-by-example.rst:20 +msgid "Attributes:" msgstr "" -#: ../system/integrations/index.rst:44 -msgid "Integrations for Monitoring Systems" +#: ../system/core-workflows/learn-by-example.rst:22 +msgid "Category (Single tree selection field, not mandatory, agents only)" msgstr "" -#: ../system/integrations/index.rst:46 -msgid "This section currently misses the following integrations:" +#: ../system/core-workflows/learn-by-example.rst:23 +msgid "" +"Approved (Boolean field, not mandatory, not shown, ``false`` as default)" msgstr "" -#: ../system/integrations/index.rst:48 -msgid "Icinga" +#: ../system/core-workflows/learn-by-example.rst:24 +msgid "Operating System (Text field, not mandatory, not shown)" msgstr "" -#: ../system/integrations/index.rst:49 -msgid "Monit" +#: ../system/core-workflows/learn-by-example.rst:25 +msgid "Software used (Single selection field, not mandatory, not shown)" msgstr "" -#: ../system/integrations/index.rst:50 -msgid "Nagios" +#: ../system/core-workflows/learn-by-example.rst:68 +msgid "Group specific values and fields" msgstr "" -#: ../system/integrations/index.rst:60 -msgid "Integrations for Issue Trackers" +#: ../system/core-workflows/learn-by-example.rst:28 +msgid "" +"This workflow set depends on the category field. It reduces the available " +"set of values based on the group selected." msgstr "" -#: ../system/integrations/index.rst:70 -msgid "Other Integrations" +#: ../system/core-workflows/learn-by-example.rst:33 +msgid "Workflow 2nd Level group" msgstr "" -#: ../system/integrations/index.rst:72 +#: ../system/core-workflows/learn-by-example.rst:35 msgid "" -"This section will hold any other integration that can't be grouped up (yet)." +"This reduces the category options to ``2nd Level/*``, ``Internal/*`` and " +"``Others``. It also sets further required fields to mandatory and visible." msgstr "" -#: ../system/integrations/ldap/index.rst:2 -msgid "LDAP / Active Directory" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for 2nd level" msgstr "" -#: ../system/integrations/ldap/index.rst:4 -msgid "" -"Zammad comes with a powerful LDAP integration that allows you to have a " -"single source of truth. By this you reduce the number of login credentials " -"your user has to remember." +#: ../system/core-workflows/learn-by-example.rst:43 +msgid "Workflow Support group" msgstr "" -#: ../system/integrations/ldap/index.rst:10 +#: ../system/core-workflows/learn-by-example.rst:45 msgid "" -"The LDAP source is also a perfect candidate for Zammad's :docs:`Kerberos " -"Single Sign-On ` but also works as addition " -"to other :doc:`/settings/security/third-party`." +"This reduces the category options to ``Support/*``, ``Internal/*`` and " +"``Others``. It also sets further required fields to visible." msgstr "" -#: ../system/integrations/ldap/index.rst:None -msgid "Zammands LDAP management page" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for support" msgstr "" -#: ../system/integrations/ldap/index.rst:25 -msgid "📝 :doc:`manage`" +#: ../system/core-workflows/learn-by-example.rst:53 +msgid "Workflow Sales group" msgstr "" -#: ../system/integrations/ldap/index.rst:25 -msgid "Add, modify, remove or re-arrange your LDAP-Sources as needed." +#: ../system/core-workflows/learn-by-example.rst:55 +msgid "" +"This reduces the category options to ``Sales/*``, ``Internal/*`` and " +"``Others``." msgstr "" -#: ../system/integrations/ldap/index.rst:30 -msgid "Before you continue, please note the following limitations." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for sales" msgstr "" -#: ../system/integrations/ldap/index.rst:32 -msgid "Mapping / Synchronizing organizations is not possible" +#: ../system/core-workflows/learn-by-example.rst:68 +#: ../system/integrations/slack.rst:88 +msgid "The Result" msgstr "" -#: ../system/integrations/ldap/index.rst:36 +#: ../system/core-workflows/learn-by-example.rst:63 msgid "" -"You may want to consider using domain based assignments to overcome this " -"issue. Learn more on :doc:`/manage/organizations/index`." +"This is what the agent would experience with the above workflows in place." msgstr "" -#: ../system/integrations/ldap/index.rst:39 +#: ../system/core-workflows/learn-by-example.rst:0 msgid "" -"Zammad's LDAP sync is one way. Editing user settings or permissions may be " -"overwritten upon the next sync depending on your configuration." +"Workflow shows objects and limits options based on selections on the group" msgstr "" -#: ../system/integrations/ldap/index.rst:41 -msgid "Nested groups are not supported." +#: ../system/core-workflows/learn-by-example.rst:90 +msgid "Approval process" msgstr "" -#: ../system/integrations/ldap/index.rst:42 -msgid "Synchronizing user avatars from LDAP is not supported." +#: ../system/core-workflows/learn-by-example.rst:71 +msgid "" +"In this case ``approved`` is visible to agents by default. For this " +"workflow, an additional role ``Approval person`` is required (no further " +"permissions)." msgstr "" -#: ../system/integrations/ldap/index.rst:43 -msgid "Unlike user filters, group filters cannot be changed." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that restricts an approval attribute to specific roles" msgstr "" -#: ../system/integrations/ldap/index.rst:44 +#: ../system/core-workflows/learn-by-example.rst:81 msgid "" -"When a user originates from an LDAP server, Zammad will try to verify the " -"login credentials against LDAP first - if this fails Zammad will check its " -"local database." +"This workflow may work best in combination with a :doc:`trigger ` but technically, this is not required." msgstr "" -#: ../system/integrations/ldap/index.rst:50 +#: ../system/core-workflows/learn-by-example.rst:84 msgid "" -"Users can have local passwords even if they're LDAP users! You can learn " -"more about user accounts in general on :doc:`/manage/users/index`." +"Select fields may be a better approach because they allow more values than " +"just a simple ``true`` or ``false``." msgstr "" -#: ../system/integrations/ldap/index.rst:54 +#: ../system/core-workflows/learn-by-example.rst:0 msgid "" -"When several LDAP sources contain the same user (meaning the same email " -"address), the user in question will be updated with every source configured. " -"*The last LDAP source will win.*" +"Workflow fixes possible values of \"Approved ?\" to a specific selection " +"depending on the users role" msgstr "" -#: ../system/integrations/ldap/index.rst:58 -msgid "" -"This is subject to change with `Issue 4109 `_ in the future." +#: ../system/core-workflows/learn-by-example.rst:103 +msgid "State dependent mandatory fields" msgstr "" -#: ../system/integrations/ldap/index.rst:60 +#: ../system/core-workflows/learn-by-example.rst:93 msgid "" -"Synchronization statistics currently affect *all* configured LDAP sources. " -"This also applies for newly added or updated sources." +"This workflow sets ``Category`` to mandatory if the agent wants to set the " +"states ``closed`` or ``pending close`` to enforce categorization." msgstr "" -#: ../system/integrations/ldap/index.rst:63 -msgid "" -"This is subject to change with `Issue 4108 `_ in the future." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that sets fields to mandatory on specific states" msgstr "" -#: ../system/integrations/ldap/index.rst:65 +#: ../system/core-workflows/learn-by-example.rst:0 msgid "" -"Zammad currently has limited fallback server support. You can workaround " -"this by providing several sources - however, ensure to have the exact same " -"configuration on your fallback." +"Workflow sets category field to mandatory upon choosing closed or pending " +"close as state" msgstr "" -#: ../system/integrations/ldap/index.rst:69 -msgid "" -"This is subject to improve with `Issue 4107 `_ in the future." +#: ../system/core-workflows/learn-by-example.rst:106 +msgid "Manual Ticket Handover Process" msgstr "" -#: ../system/integrations/ldap/index.rst:76 -msgid "" -"This section holds all requests Zammad handled for all LDAP sources. These " -"entries can either contain synchronization information or logins " -"(authentication attempts via Zammad's login interface)." +#: ../system/core-workflows/learn-by-example.rst:108 +msgid "This example covers the handover of a ticket from one agent to another:" msgstr "" -#: ../system/integrations/ldap/index.rst:80 +#: ../system/core-workflows/learn-by-example.rst:110 msgid "" -"By clicking on any request, Zammad will provide even more information. The " -"provided information can be useful when something does not work as expected." +"When the ticket owner is modified, a new text field (\"Handover\") shows up " +"for a comment" msgstr "" -#: ../system/integrations/ldap/index.rst:85 +#: ../system/core-workflows/learn-by-example.rst:112 msgid "" -"Especially a LDAP synchronization can cause many log entries. The web " -"interface will always limit the number of shown entries to the last 50 " -"entries." +"This may only be visible when the owner is changed, therefore it has to be " +"hidden in general" msgstr "" -#: ../system/integrations/ldap/index.rst:None +#: ../system/core-workflows/learn-by-example.rst:114 +msgid "The input in this handover text field is mandatory" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:115 msgid "" -"Screencast showing LDAP integration log entries and a detail view on\n" -"an entry." +"After submitting changes, the value of the handover field must be added as " +"an note to the ticket (via trigger)" msgstr "" -#: ../system/integrations/ldap/manage.rst:2 -msgid "Manage LDAP-Sources" +#: ../system/core-workflows/learn-by-example.rst:121 +msgid "Hiding handover field" msgstr "" -#: ../system/integrations/ldap/manage.rst:6 -msgid "" -"Please keep in mind all current limitations for the LDAP synchronization. " -"This will help to understand scopes of the following operations better." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Hiding the handover field in core workflows" msgstr "" -#: ../system/integrations/ldap/manage.rst:65 -msgid "Add new source" +#: ../system/core-workflows/learn-by-example.rst:126 +msgid "Showing handover field and setting it to mandatory" msgstr "" -#: ../system/integrations/ldap/manage.rst:10 -msgid "" -"Using the *New Source* button allows you to add new LDAP sources to your " -"installation. You're not limited in the number of sources, however, keep in " -"mind that many sources will also take more time to synchronize." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Showing the handover field and set it as mandatory" msgstr "" -#: ../system/integrations/ldap/manage.rst:14 -msgid "" -"You can choose between different encryption types, namely *SSL* and " -"*STARTTLS* or none of them (\"*No SSL*\"). If you choose *SSL* or " -"*STARTTLS*, Zammad will display an additional *SSL verification* option that " -"allows you to disable the verification, e.g. for self-signed SSL " -"certificates. You can also tell Zammad to use a different port by appending " -"``:`` to your hostname/IP." +#: ../system/core-workflows/learn-by-example.rst:131 +msgid "Trigger writing handover input to a new article" msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "" -"Screenshot of configuring a new LDAP source with SSL encryption and SSL " -"verification" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Write handover content to a new article" msgstr "" -#: ../system/integrations/ldap/manage.rst:26 +#: ../system/core-workflows/learn-by-example.rst:133 msgid "" -"New Source with SSL transport security enabled and certificate verification" +"As a result, the ticket includes an article of the type note which includes " +"the predefined text and the handover comment." msgstr "" -#: ../system/integrations/ldap/manage.rst:30 +#: ../system/core-workflows/limitations.rst:6 +msgid "Core Workflows do not replace Triggers" +msgstr "" + +#: ../system/core-workflows/limitations.rst:5 msgid "" -"Using an user filter can be a good idea if you only require a small subset " -"of your LDAP users in Zammad." +"Workflows manipulate the behavior of fields. However, they do not set values " +"in fields because of actions." msgstr "" -#: ../system/integrations/ldap/manage.rst:42 -msgid "This especially affects inactive users" +#: ../system/core-workflows/limitations.rst:16 +msgid "API calls are only partly affected" msgstr "" -#: ../system/integrations/ldap/manage.rst:34 +#: ../system/core-workflows/limitations.rst:9 msgid "" -"As every LDAP behaves differently on which attributes and how they are set, " -"Zammad doesn't care about any flags." +"Some options affect UI only and thus do not restrict responses and calls." msgstr "" -#: ../system/integrations/ldap/manage.rst:37 -msgid "" -"Users that no longer are returned by your LDAP source will automatically be " -"set to inactive. Zammad assumes that the user was deactivated." +#: ../system/core-workflows/limitations.rst:11 +msgid "This affects the following actions:" msgstr "" -#: ../system/integrations/ldap/manage.rst:41 -msgid "" -"Users will never be removed automatically! If you want to remove obsolete " -"users, use :doc:`/system/data-privacy`." +#: ../system/core-workflows/limitations.rst:13 +msgid "select" msgstr "" -#: ../system/integrations/ldap/manage.rst:46 -msgid "Active Directory admins" +#: ../system/core-workflows/limitations.rst:14 +msgid "auto select" msgstr "" -#: ../system/integrations/ldap/manage.rst:45 -msgid "" -"Active Directories are quite specific on how to filter for active users only " -"- please see the `Microsoft documentation `_ for more " -"information." +#: ../system/core-workflows/limitations.rst:15 +msgid "show" msgstr "" -#: ../system/integrations/ldap/manage.rst:51 -msgid "" -"*Do not* manually write pathes of either LDAP attributes or groups. If " -"Zammad does not display them, it either cannot find them or you have a lot " -"of users that don't have the attributes populated." +#: ../system/core-workflows/limitations.rst:16 +msgid "hide" msgstr "" -#: ../system/integrations/ldap/manage.rst:55 -msgid "" -"Zammad will always only return attributes that are filled - this reduces the " -"returned list of attributes greatly." +#: ../system/core-workflows/limitations.rst:25 +msgid "Some fields stay unavailable to customers" msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing how to add a new LDAP source" +#: ../system/core-workflows/limitations.rst:19 +msgid "" +"For technical and security reasons, some default fields (the pale ones you " +"can't edit) stay unavailable for display and usage on customer permissions." msgstr "" -#: ../system/integrations/ldap/manage.rst:63 +#: ../system/core-workflows/limitations.rst:23 msgid "" -"If your LDAP system doesn't allow anonymous bind, Zammad detects it and " -"provides you an editable \"Base DN\" *text* field instead of a prefilled " -"*select* field." +"If you require your customers to change e.g. priorities, please consider " +"using workarounds via :doc:`/system/objects` and :doc:`/manage/trigger`." msgstr "" -#: ../system/integrations/ldap/manage.rst:81 -msgid "Review or edit existing source" +#: ../system/core-workflows/limitations.rst:29 +msgid "Ticket title changes not supported in edit mask" msgstr "" -#: ../system/integrations/ldap/manage.rst:68 +#: ../system/core-workflows/limitations.rst:28 msgid "" -"Clicking on a LDAP source will provide a configuration and mapping overview." +"It is currently not possible to perform changes of the ticket title in the " +"edit mask (e.g. renaming, set to read-only)." msgstr "" -#: ../system/integrations/ldap/manage.rst:70 -msgid "" -"If needed you can then use the *Change* button to update either the name, " -"active state or the whole configuration. If you're changing the whole " -"configuration, the dialogue will be identical to the source creation." +#: ../system/core-workflows/limitations.rst:37 +msgid "What is out of scope of Core Workflows?" msgstr "" -#: ../system/integrations/ldap/manage.rst:76 +#: ../system/core-workflows/limitations.rst:32 msgid "" -"Did your LDAP server change? Different LDAP servers have different " -"structures and default attributes. This causes the LDAP synchronization to " -"likely fail. Consider removing the affected source and re-add it." +"There are some things that would count as workflow but are either done via :" +"doc:`/manage/trigger` or :doc:`/manage/scheduler`." msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing the update of the source name." +#: ../system/core-workflows/limitations.rst:35 +msgid "Such as (but not limited to):" msgstr "" -#: ../system/integrations/ldap/manage.rst:89 -msgid "Re-arrange LDAP source's order" +#: ../system/core-workflows/limitations.rst:37 +msgid "up- or downgrade permissions of users" msgstr "" -#: ../system/integrations/ldap/manage.rst:84 -msgid "" -"You can change the synchronization order for each source at any time. Zammad " -"will synchronize the sources from top to bottom." +#: ../system/core-workflows/limitations.rst:38 +msgid "affecting article creation or listing" msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "" -"Screencasting showing how to change the source order by using\n" -"drag and drop." +#: ../system/data-privacy.rst:2 +msgid "Data Privacy" msgstr "" -#: ../system/integrations/ldap/manage.rst:101 -msgid "Remove a source" +#: ../system/data-privacy.rst:4 +msgid "" +"For compliance with GDPR and other data privacy laws, you may wish to " +"**permanently delete users from the system**, along with **all of their " +"associated tickets**." msgstr "" -#: ../system/integrations/ldap/manage.rst:92 +#: ../system/data-privacy.rst:8 msgid "" -"If you no longer need the a LDAP source or simply want to start over, you " -"can remove them at any time. This will not remove synchronized users, data " -"synchronized or permissions." +"You can create manual deletion tasks or even automated deletion tasks for " +"tickets and users based on custom conditions via :doc:`scheduler `!" msgstr "" -#: ../system/integrations/ldap/manage.rst:98 +#: ../system/data-privacy.rst:12 msgid "" -"Not sure if you'd need the source later on? Set the source to inactive " -"instead of removing it - see *Review or edit existing source* for more." +"Access to this panel requires ``admin.data_privacy`` permissions (introduced " +"in Zammad 3.5)." msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing how to remove LDAP sources." +#: ../system/data-privacy.rst:15 +msgid "" +"On older systems that have not been updated yet, customers can also be :docs:" +"`deleted via the Zammad console `." msgstr "" -#: ../system/integrations/pgp/index.rst:2 -msgid "PGP" +#: ../system/data-privacy.rst:22 +msgid "User deletion dialog in the Data Privacy panel" msgstr "" -#: ../system/integrations/pgp/index.rst:7 +#: ../system/data-privacy.rst:22 msgid "" -"Pretty Good Privacy (PGP) is another method for secure email communication. " -"With PGP, you can exchange **signed** and **encrypted** messages with others." +"The user deletion dialog lists some of the tickets that will be removed from " +"the system along with the user." msgstr "" -#: ../system/integrations/pgp/index.rst:13 -#: ../system/integrations/smime/index.rst:17 -msgid "Signing" +#: ../system/data-privacy.rst:27 +msgid "Deleting Users via GUI" msgstr "" -#: ../system/integrations/pgp/index.rst:11 -msgid "is a proof that a message hasn't been manipulated on its way." +#: ../system/data-privacy.rst:29 +msgid "🔥 **All deletions are FINAL!**" msgstr "" -#: ../system/integrations/pgp/index.rst:13 +#: ../system/data-privacy.rst:31 +msgid "Once you click “Delete”, the action cannot be canceled or undone." +msgstr "" + +#: ../system/data-privacy.rst:33 msgid "" -"In other words, it guarantees message **integrity** and **authenticity**." +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:19 -#: ../system/integrations/smime/index.rst:22 -msgid "Encryption" +#: ../system/data-privacy.rst:36 +msgid "**The following records cannot be deleted:**" msgstr "" -#: ../system/integrations/pgp/index.rst:16 -#: ../system/integrations/smime/index.rst:20 -msgid "" -"scrambles a message so that it can only be unscrambled by the intended " -"recipient." +#: ../system/data-privacy.rst:38 +msgid "your own account" msgstr "" -#: ../system/integrations/pgp/index.rst:19 -msgid "" -"In other words, it guarantees message **privacy** and **data security**." +#: ../system/data-privacy.rst:39 +msgid "the system's last remaining administrator account" msgstr "" -#: ../system/integrations/pgp/index.rst:25 -msgid "Screenshot of ticket creation with encrypt and sign buttons" +#: ../system/data-privacy.rst:42 +msgid "Step 1: Find a User / Confirm Deletion" msgstr "" -#: ../system/integrations/pgp/index.rst:25 -msgid "" -"Once PGP has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " -"appear in the ticket composer." +#: ../system/data-privacy.rst:44 +msgid "There are three ways to access the user deletion dialog:" msgstr "" -#: ../system/integrations/pgp/index.rst:28 -msgid "**Sign button not visible?**" +#: ../system/data-privacy.rst:51 +msgid "**from the user's profile**" msgstr "" -#: ../system/integrations/pgp/index.rst:30 -msgid "" -"Please note that the signing of emails is based on the outgoing email " -"account. That means you have to choose a group with a sender email account, " -"which has a private key assigned." +#: ../system/data-privacy.rst:0 +msgid "Accessing the user deletion dialog in a user profile" msgstr "" -#: ../system/integrations/pgp/index.rst:35 -msgid "Handling of Keys" +#: ../system/data-privacy.rst:51 +msgid "Click **Action > Delete**." msgstr "" -#: ../system/integrations/pgp/index.rst:36 -msgid "" -"To use the PGP function, you have to enable the integration (PGP) by " -"switching the toggle to *enabled*." +#: ../system/data-privacy.rst:58 +msgid "**in the “Manage > Users” Admin Panel**" msgstr "" -#: ../system/integrations/pgp/index.rst:39 -msgid "" -"You can add keys by clicking the *add key* button. The keys can be imported " -"from a file or you can paste the content of the key in the text box." +#: ../system/data-privacy.rst:0 +msgid "Accessing the user deletion dialog under “Users” in the Admin Panel" msgstr "" -#: ../system/integrations/pgp/index.rst:42 -msgid "**Which keys do I have to import?**" +#: ../system/data-privacy.rst:58 +msgid "Use the **⋮ Actions** menu for the target user." msgstr "" -#: ../system/integrations/pgp/index.rst:44 -msgid "" -"For **signing** *outgoing* emails, you have to import the private key of " -"your Zammad email account." +#: ../system/data-privacy.rst:66 ../system/data-privacy.rst:104 +msgid "**in the “System > Data Privacy” Admin Panel**" msgstr "" -#: ../system/integrations/pgp/index.rst:47 +#: ../system/data-privacy.rst:0 msgid "" -"For **encrypting** *outgoing* emails, you have to import the public key of " -"the customer's email account." +"Accessing the user deletion dialog under “Data Privacy” in the Admin Panel" msgstr "" -#: ../system/integrations/pgp/index.rst:50 +#: ../system/data-privacy.rst:65 msgid "" -"For **verifying the signature** of signed *incoming* emails, you have to " -"import the public key of the customer." +"Use the **New Deletion Task** button. Search for users by name or email " +"address." msgstr "" -#: ../system/integrations/pgp/index.rst:53 -msgid "" -"For **decrypting** of encrypted *incoming* emails, you have to import the " -"private key of your Zammad email account." +#: ../system/data-privacy.rst:79 +msgid "**Delete organizations**" msgstr "" -#: ../system/integrations/pgp/index.rst:57 -msgid "Import Keys From a File" +#: ../system/data-privacy.rst:69 +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:" msgstr "" -#: ../system/integrations/pgp/index.rst:58 -msgid "You can import keys from a file in the section **Upload key**:" +#: ../system/data-privacy.rst:0 +msgid "Deleting an organization via the user deletion dialog" msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of adding a key via file" +#: ../system/data-privacy.rst:78 +msgid "" +"If this option does not appear, make sure there are no pending deletion " +"tasks for other customers from this organization." msgstr "" -#: ../system/integrations/pgp/index.rst:64 -msgid "" -"**Supported file formats:** ASCII-armor as well as binary GPG format " -"(basically any GPG supported key format) is supported here." +#: ../system/data-privacy.rst:82 +msgid "Step 2: Monitor Deletion Job Status" msgstr "" -#: ../system/integrations/pgp/index.rst:68 -msgid "Import Keys by Pasting the Content" +#: ../system/data-privacy.rst:84 +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:" msgstr "" -#: ../system/integrations/pgp/index.rst:69 -msgid "You can also paste the key's content in the section **paste key**:" +#: ../system/data-privacy.rst:98 +msgid "**in the Activity Stream**" msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of adding a key via pasting" +#: ../system/data-privacy.rst:0 +msgid "Activity Stream showing data privacy tasks" msgstr "" -#: ../system/integrations/pgp/index.rst:75 +#: ../system/data-privacy.rst:94 msgid "" -"**Supported format:** Please note that only ASCII-armor is supported here." +"For each deleted user, the Activity Stream will be updated twice—once when " +"the task is created, and once when it's complete." msgstr "" -#: ../system/integrations/pgp/index.rst:78 -msgid "Deleting Keys" +#: ../system/data-privacy.rst:97 +msgid "" +"These notifications are only visible to users with ``admin.data_privacy`` " +"permissions." msgstr "" -#: ../system/integrations/pgp/index.rst:79 +#: ../system/data-privacy.rst:0 msgid "" -"If you want to delete a specific key, you can do it by clicking on the menu " -"in the *actions* column and select **delete**:" +"The task list within Data Privacy shows removals being in progress and " +"completed." msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of deleting a key" +#: ../system/data-privacy.rst:107 +msgid "Frequently Asked Questions" msgstr "" -#: ../system/integrations/pgp/index.rst:88 -msgid "Downloading Keys" +#: ../system/data-privacy.rst:121 +msgid "What happens if I receive an email from a deleted customer?" msgstr "" -#: ../system/integrations/pgp/index.rst:89 +#: ../system/data-privacy.rst:110 msgid "" -"If you want to download your keys, you can do this as well via corresponding " -"action buttons. Depending on the key, you can choose wether you want to " -"download the private or the public key." -msgstr "" - -#: ../system/integrations/pgp/index.rst:95 -#: ../system/integrations/smime/manage-certificates.rst:76 -msgid "Default Behavior" +"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/integrations/pgp/index.rst:96 +#: ../system/data-privacy.rst:115 msgid "" -"Here you can adjust on per group basis, if *sign* and *encryption* is on or " -"off by default. Please be aware, that agents can always override the setting " -"for each individual article." +"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**." msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Adjusting default behavior on per group basis" +#: ../system/data-privacy.rst:130 +msgid "What about user information stored in internal notes or other messages?" msgstr "" -#: ../system/integrations/pgp/index.rst:107 +#: ../system/data-privacy.rst:124 msgid "" -"Here you can see the last actions regarding signing and encryption and if " -"they were successful." +"The deletion process removes **user accounts and associated tickets only**." msgstr "" -#: ../system/integrations/pgp/index.rst:117 -msgid "**Sign button is not visible, but keys are imported.**" +#: ../system/data-privacy.rst:126 +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." msgstr "" -#: ../system/integrations/pgp/index.rst:115 -msgid "Did you choose a group in the ticket?" +#: ../system/data-privacy.rst:137 +msgid "I deleted an user and can still see a message they sent!" msgstr "" -#: ../system/integrations/pgp/index.rst:116 +#: ../system/data-privacy.rst:133 msgid "" -"Did you import a private key for the email adress, which is used for " -"outgoing emails in the group?" +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:122 -msgid "**How to obtain keys?**" +#: ../system/data-privacy.rst:141 +msgid "I removed a customer, now my reporting is off!" msgstr "" -#: ../system/integrations/pgp/index.rst:120 +#: ../system/data-privacy.rst:140 msgid "" -"You can create them yourself! There are some good tutorials on the web on " -"how to create them. Providing keys to Zammad is a prerequisite to use the " -"PGP feature." +"When removing users and their tickets, all references are removed. This also " +"affects e.g. Reporting - these information are lost." msgstr "" -#: ../system/integrations/pgp/index.rst:127 -msgid "**It says a passphrase is needed, but I haven't got one.**" +#: ../system/data-privacy.rst:145 +msgid "How long does Zammad store created tasks?" msgstr "" -#: ../system/integrations/pgp/index.rst:125 +#: ../system/data-privacy.rst:144 msgid "" -"If the key is secured with a passphrase, you have to provide it for the " -"import in Zammad. It is possible that keys may have an empty passphrase. " -"However, this is *not* recommended." +"Please see the on-premise data section of the :docs:`data privacy ` chapter." msgstr "" -#: ../system/integrations/pgp/index.rst:132 -msgid "**How do my customers get my new key?**" +#: ../system/data-privacy.rst:150 +msgid "What about re-assigned tickets? I want to delete them, too." msgstr "" -#: ../system/integrations/pgp/index.rst:130 +#: ../system/data-privacy.rst:148 msgid "" -"You have to provide your **public** key in advance. Your customer also has " -"to configure PGP in their email workflow and import your public key. The " -"other way round, you have to get the public key of your customer and have to " -"import it to Zammad." -msgstr "" - -#: ../system/integrations/slack.rst:2 -msgid "Slack" +"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." msgstr "" -#: ../system/integrations/slack.rst:4 -msgid "**⚠️ Deprecation warning ⚠️**" +#: ../system/data-privacy.rst:154 +msgid "Why are there so many deletion task entries, I didn't create them!" msgstr "" -#: ../system/integrations/slack.rst:6 +#: ../system/data-privacy.rst:153 msgid "" -"Zammad 7 will no longer support this dedicated Slack integration. It is " -"recommended to switch to :doc:`pre-defined webhooks ` instead. Existing Slack integrations should " -"be migrated manually before this feature is dropped." +"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." msgstr "" -#: ../system/integrations/slack.rst:14 -msgid "" -"In order to use this feature, please add a new Slack app to your Workspace. " -"The App you need is called ``Incoming WebHooks`` ." +#: ../system/integrations/checkmk/admin-panel-reference.rst:2 +msgid "Admin Panel Reference" msgstr "" -#: ../system/integrations/slack.rst:18 -msgid "Why Do I Need This Feature?" +#: ../system/integrations/checkmk/admin-panel-reference.rst:None +msgid "Screenshot of Checkmk settings overview" msgstr "" -#: ../system/integrations/slack.rst:20 +#: ../system/integrations/checkmk/admin-panel-reference.rst:12 msgid "" -"If you're already using Slack for your team communication, you'll love this " -"feature! Our Slack integration can push ticket notifications about the last " -"ticket article based on the following events:" +"Which :doc:`group ` should Checkmk tickets be assigned " +"to as a default (*i.e.,* when none is specified)?" msgstr "" -#: ../system/integrations/slack.rst:24 -msgid "on Ticket creation" +#: ../system/integrations/checkmk/admin-panel-reference.rst:15 +msgid "(Applies to :ref:`API alerts ` only.)" msgstr "" -#: ../system/integrations/slack.rst:25 -msgid "on Ticket updates" +#: ../system/integrations/checkmk/admin-panel-reference.rst:21 +msgid "Auto close" msgstr "" -#: ../system/integrations/slack.rst:26 -msgid "on reached reminders" +#: ../system/integrations/checkmk/admin-panel-reference.rst:18 +msgid "" +"Should Zammad automatically close tickets if a service has recovered on its " +"own?" msgstr "" -#: ../system/integrations/slack.rst:27 -msgid "a Ticket has escalated" +#: ../system/integrations/checkmk/admin-panel-reference.rst:21 +msgid "(Agents will receive notifications for such closures as appropriate.)" msgstr "" -#: ../system/integrations/slack.rst:28 -msgid "a Ticket is going to escalate" +#: ../system/integrations/checkmk/admin-panel-reference.rst:30 +msgid "Auto-close state" msgstr "" -#: ../system/integrations/slack.rst:30 -msgid "" -"Zammad will provide the Ticket title, a direct link to the Ticket, the event " -"type (creation, updated, escalation), the customer, time and the last " -"article that has triggered the notification." +#: ../system/integrations/checkmk/admin-panel-reference.rst:24 +msgid "What ticket state should be applied when “auto-closing” a ticket?" msgstr "" -#: ../system/integrations/slack.rst:34 +#: ../system/integrations/checkmk/admin-panel-reference.rst:26 msgid "" -"This will give you further options, as you can see e.g. escalating tickets " -"that are assigned to an agent that's e.g. absent. You can interact faster, " -"as you might see problems earlier (or even before the problem gets one)." +"You can choose from the seven built-in ticket states. If these states aren't " +"enough for you, you can :ref:`define a new ticket state ` for this purpose as well. This can be useful for tracking " +"tickets with :doc:`reports `, for example." msgstr "" -#: ../system/integrations/slack.rst:38 -msgid "" -"If needed and wanted, you can even discuss directly about the topic before " -"sending an answer to the customer. Another possible use case would be a " -"agent monitoring new agents and their answers to tickets." +#: ../system/integrations/checkmk/admin-panel-reference.rst:35 +#: ../system/integrations/cti/includes/recent-logs.include.rst:2 +#: ../system/integrations/ldap/index.rst:74 +#: ../system/integrations/pgp/index.rst:106 +msgid "Recent Logs" msgstr "" -#: ../system/integrations/slack.rst:44 -msgid "Configure the Integration" +#: ../system/integrations/checkmk/admin-panel-reference.rst:None +msgid "Screenshot of Checkmk \"Recent Logs\" section" msgstr "" -#: ../system/integrations/slack.rst:46 +#: ../system/integrations/checkmk/admin-panel-reference.rst:41 msgid "" -"First of all, please go to your slack workspace - go to administration => " -"Manage Apps. If you don't have an app yet, you can simply add a new one - " -"just search for ``Incoming WebHooks`` and customize the app to your needs." +"If you're having trouble getting Zammad and Checkmk to play nicely together, " +"this section can help you troubleshoot." msgstr "" -#: ../system/integrations/slack.rst:50 +#: ../system/integrations/checkmk/admin-panel-reference.rst:44 msgid "" -"Choose (or create) the channel Zammad should post it's information to and " -"press on \"Add Incoming WebHooks integration\". If you're ready, copy the " -"provided WebHook URL and go to your Zammad installation." +"It contains a record of the fifty most recent transactions that Zammad knows " +"about, including each one's request/response details and return status." msgstr "" -#: ../system/integrations/slack.rst:56 -msgid "" -"You need administrative rights on the Slack Workspace. The link to the app " -"directory is normally ``https://[workspace-name].slack.com/apps`` ." +#: ../system/integrations/checkmk/api-reference.rst:2 +msgid "API Reference" msgstr "" -#: ../system/integrations/slack.rst:63 +#: ../system/integrations/checkmk/api-reference.rst:4 msgid "" -"To configure the slack integration, log in to Zammad and go to Integrations " -"(System) => Slack in the admin panel." +"For most users, :ref:`the sample scripts from the Setup Guide ` will do the job just fine. But if you want more fine-grained control" +"—for instance, to create high- and low-priority tickets for different types " +"of system events—then you'll have to customize the data those scripts send " +"to Zammad." msgstr "" -#: ../system/integrations/slack.rst:66 +#: ../system/integrations/checkmk/api-reference.rst:15 msgid "" -"Here you can choose on what evens Zammad should post information about a " -"ticket to your Slack channel. Next you need to device what groups shall be " -"affected by this, as anybody with access to that specific Slack channel can " -"read at least parts of the ticket this might be a privacy issue, if you " -"select the wrong groups. The username is simply the name that Zammad uses as " -"display name inside the Slack chat. The channel defines the Slack channel " -"the information is being posted in. As last option, you can set a custom " -"icon for posting to slack." +"This custom script will automatically set all tickets it creates to **high " +"priority** and **assign them to charlie@chrispresso.com**." msgstr "" -#: ../system/integrations/slack.rst:74 -msgid "" -"When you're ready, just hit \"Submit\" and enable the integration. Zammad " -"will now post new ticket information based on the trigger you chose. Below " -"the options you have the recent log that shows the latest requests to Slack " -"for debugging if needed." +#: ../system/integrations/checkmk/api-reference.rst:32 +msgid "How Does it Work?" msgstr "" -#: ../system/integrations/slack.rst:81 +#: ../system/integrations/checkmk/api-reference.rst:34 msgid "" -"If you leave the Icon URL empty, Zammad will use the Zammad logo instead. " -"The icon should be a square PNG file." +"There are two kinds of data you can pass to the API, both in the form of key-" +"value pairs:" msgstr "" -#: ../system/integrations/slack.rst:90 -msgid "" -"The following figure shows how it will look if you choose to receive updates " -"on created and updated tickets. On every post Zammad sends to the Slack " -"channel, you can create new threads to discuss about the new article." +#: ../system/integrations/checkmk/api-reference.rst:44 +msgid "Checkmk parameters" msgstr "" -#: ../system/integrations/slack.rst:96 +#: ../system/integrations/checkmk/api-reference.rst:38 msgid "" -"If you just want to keep track of soon escalating or already escalated " -"tickets, it will look the the following figure. Zammad changes the color in " -"front of the post so you can easily see the state of the ticket." +"are required, and make up the **contents** of the resulting tickets/" +"articles. They also determine whether an event creates a new ticket or " +"updates/closes an existing one." msgstr "" -#: ../system/integrations/slack.rst:102 +#: ../system/integrations/checkmk/api-reference.rst:42 msgid "" -"If you change the state, Zammad will also put information on what state the " -"ticket gets and (if pending state) the date until it pends. You'll also " -"recognize the color codes in front of posts on slack, as they are exact the " -"same the ticket state colors you'll see in Zammad!" +"These are the only values used in the sample scripts. **Use them as-is**; " +"technically, they can be customized, but it's hard to imagine a good reason " +"for it." msgstr "" -#: ../system/integrations/smime/index.rst:2 -msgid "S/MIME" +#: ../system/integrations/checkmk/api-reference.rst:52 +msgid "Ticket attributes" msgstr "" -#: ../system/integrations/smime/index.rst:11 +#: ../system/integrations/checkmk/api-reference.rst:47 msgid "" -"S/MIME is the most widely-supported method for secure email communication. " -"With S/MIME, you can exchange **signed** and **encrypted** messages with " -"others." +"are optional, and can be used to **adjust settings** on newly created " +"tickets (*e.g.,* set the owner, group, priority, or state)." msgstr "" -#: ../system/integrations/smime/index.rst:15 +#: ../system/integrations/checkmk/api-reference.rst:50 msgid "" -"is proof that a message hasn't been tampered with or sent by an impersonator." +"If you want to customize your Checkmk alert script, do it with these. Simply " +"add an extra “form” option for each one (``-F \"key=value\"``) to your " +"script's ``curl`` command line, as in the example above." msgstr "" -#: ../system/integrations/smime/index.rst:17 +#: ../system/integrations/checkmk/api-reference.rst:54 +msgid "💡 **It's just an API endpoint!**" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:56 msgid "" -"In other words, it guarantees a message's **integrity** and **authenticity**." +"When using Checkmk integration, messages need to be formatted in a certain " +"way, but that *doesn't mean the messages actually have to come from Checkmk*." msgstr "" -#: ../system/integrations/smime/index.rst:22 -msgid "In other words, it guarantees **privacy** and **data security**." +#: ../system/integrations/checkmk/api-reference.rst:59 +msgid "" +"If you use another monitoring tool that's not officially supported by " +"Zammad, there's probably a way to make it work with your Checkmk callback " +"URL." msgstr "" -#: ../system/integrations/smime/index.rst:28 -msgid "Screencast demo of S/MIME features for both new tickets and replies" +#: ../system/integrations/checkmk/api-reference.rst:63 +msgid "Checkmk Parameters" msgstr "" -#: ../system/integrations/smime/index.rst:28 +#: ../system/integrations/checkmk/api-reference.rst:65 msgid "" -"Once S/MIME has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " -"appear in the ticket composer." +"When a notification is received, Zammad creates a new article containing the " +"details of the event that triggered it:" msgstr "" -#: ../system/integrations/smime/index.rst:32 -msgid ":doc:`🔪 Prerequisites `" +#: ../system/integrations/checkmk/api-reference.rst:None +msgid "Checkmk article body" msgstr "" -#: ../system/integrations/smime/index.rst:31 +#: ../system/integrations/checkmk/api-reference.rst:72 msgid "" -"New to S/MIME? This section helps you to find certificate providers and " -"points out Limitations." +"These details come from the fields listed below, which correspond to " +"parameters provided by Checkmk (``$NOTIFY_*``)." msgstr "" -#: ../system/integrations/smime/index.rst:35 -msgid ":doc:`📝 Manage Certificates `" +#: ../system/integrations/checkmk/api-reference.rst:75 +msgid "**Required fields are marked with an asterisk (\\*).**" msgstr "" -#: ../system/integrations/smime/index.rst:35 -msgid "Add and download certificates; configure group default behaviors." +#: ../system/integrations/checkmk/api-reference.rst:79 +msgid "event_id\\*" msgstr "" -#: ../system/integrations/smime/index.rst:38 -msgid ":doc:`😦 Troubleshooting `" +#: ../system/integrations/checkmk/api-reference.rst:78 +msgid "" +"A unique ID for the system event. (``$NOTIFY_SERVICEPROBLEMID`` / " +"``$NOTIFY_HOSTPROBLEMID``)" msgstr "" -#: ../system/integrations/smime/index.rst:38 -msgid "Took a wrong turn? About recent logs and common issues." +#: ../system/integrations/checkmk/api-reference.rst:86 +msgid "host\\*" msgstr "" -#: ../system/integrations/smime/index.rst:43 +#: ../system/integrations/checkmk/api-reference.rst:82 msgid "" -"For more details on how S/MIME integration works on the agent side, see the :" -"user-docs:`user docs `." -msgstr "" - -#: ../system/integrations/smime/manage-certificates.rst:2 -msgid "Manage Certificates" +"The hostname of the system that the event originated from. " +"(``$NOTIFY_HOSTNAME``)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:4 +#: ../system/integrations/checkmk/api-reference.rst:85 msgid "" -"S/MIME is **disabled by default**. Enable it to start adding certificates." +"Used to determine if a new event belongs to an existing ticket. Also used in " +"the subject line of the resulting article (“ is ”)." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:10 -msgid "Dialogue to add new certificates or private keys" +#: ../system/integrations/checkmk/api-reference.rst:96 +msgid "service" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:10 +#: ../system/integrations/checkmk/api-reference.rst:89 msgid "" -"Manage certificates in the Admin Panel under **System > Integrations > S/" -"MIME**. Certificates may be pasted in as plain text or uploaded from a file." +"The name of the service that the event originated from. " +"(``$NOTIFY_SERVICEDESC``)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:14 -msgid "Add Certificate Data" +#: ../system/integrations/checkmk/api-reference.rst:92 +msgid "Used to determine if a new event belongs to an existing ticket." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:36 -msgid "Add Certificate" +#: ../system/integrations/checkmk/api-reference.rst:94 +#: ../system/integrations/checkmk/api-reference.rst:110 +msgid "Displayed as ``-`` when omitted." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:17 -msgid "" -"Import public-key certificates for both your own organization and your " -"contacts." +#: ../system/integrations/checkmk/api-reference.rst:104 +msgid "state\\*" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:19 +#: ../system/integrations/checkmk/api-reference.rst:99 msgid "" -"You can also add a bunch of certificates in one go by providing a single " -"file with all relevant certificates." -msgstr "" - -#: ../system/integrations/smime/manage-certificates.rst:22 -msgid "🕵️ **ALWAYS verify certificates in-person or over the phone!**" +"The current state of the service or host in question. " +"(``$NOTIFY_SERVICESTATE`` / ``$NOTIFY_HOSTSTATE``)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:24 +#: ../system/integrations/checkmk/api-reference.rst:102 msgid "" -"The whole point of signatures is to alert you when someone is trying to " -"pretend to be someone they're not. Never accept a certificate from someone " -"online without verifying it first." +"Used to detect when a ticket should be auto-closed (*i.e.,* on ``OK``/" +"``UP``). Also used in the subject line of the resulting article (“ is " +"”)." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:28 -msgid "📇 **What about trusted certificate authorities?**" +#: ../system/integrations/checkmk/api-reference.rst:110 +msgid "text" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:30 +#: ../system/integrations/checkmk/api-reference.rst:107 msgid "" -"In some cases (e.g. when dealing with large enterprises), you may be given a " -"certificate for an entire CA, rather than a single contact. Add it here to " -"trust *all* certificates issued by that CA." +"The output of the process that triggered the event. " +"(``$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:35 +#: ../system/integrations/checkmk/api-reference.rst:121 msgid "" -"Commercial CAs can usually be verified online. Zammad does not include a " -"list of built-in, trusted CAs." +"The Object Manager attribute panel displays built-in and custom\n" +"attribute names." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:57 -msgid "Add Private Key" +#: ../system/integrations/checkmk/api-reference.rst:121 +msgid "Find a complete list of ticket attributes in the Object Manager." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:39 +#: ../system/integrations/checkmk/api-reference.rst:123 msgid "" -"Once you've added a public-key certificate, you can import its matching " -"private key." +"Ticket attributes are entirely optional, and can be used to customize the " +"tickets that Checkmk creates. (Note that these attributes will be ignored if " +"a new event belongs to an existing ticket.)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:42 +#: ../system/integrations/checkmk/api-reference.rst:128 msgid "" -"Private keys are for **your own organization only**; never ask your contacts " -"for their private keys." +"Why would you want to do this? Maybe you have only one IT guy, and all " +"system monitoring issues should be automatically assigned to him. Or, maybe " +"you're creating multiple notification rules so that database outages take " +"higher priority than disk space warnings." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:0 -msgid "" -"S/MIME integration showing configured certificates and possible issues with " -"Logging" +#: ../system/integrations/checkmk/api-reference.rst:135 +msgid "In most cases, you'll probably want to set one of the following:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:50 -msgid "" -"A note is displayed on certificates with a matching private key (see line 2)." -msgstr "" +#: ../system/integrations/checkmk/api-reference.rst:137 +msgid "group" +msgstr "группа" -#: ../system/integrations/smime/manage-certificates.rst:52 -msgid "📤 **Certificates and private keys must be uploaded separately.**" +#: ../system/integrations/checkmk/api-reference.rst:139 +msgid "state" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:54 +#: ../system/integrations/checkmk/api-reference.rst:140 +msgid "priority" +msgstr "приоритет" + +#: ../system/integrations/checkmk/api-reference.rst:142 msgid "" -"If your certificate and private key are bundled together in the same file or " -"PEM block, import it twice (once using each button)." +"but in practice, you can set almost any attribute, including :doc:`custom " +"ones you created through the Object Manager `." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:57 -msgid "Please note that bulk imports of private keys are not possible." +#: ../system/integrations/checkmk/api-reference.rst:145 +msgid "Please note that the following attributes are **not customizable**:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:60 -msgid "Download Certificate Data" -msgstr "" +#: ../system/integrations/checkmk/api-reference.rst:147 +msgid "title" +msgstr "заголовок" -#: ../system/integrations/smime/manage-certificates.rst:62 -msgid "" -"You can download the earlier provided certificates and private keys at any " -"time from your Zammad instance." +#: ../system/integrations/checkmk/api-reference.rst:148 +msgid "id" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:65 -msgid "" -"Please note that passphrase-protected private keys stay protected and when " -"you download them, you have to know the passphrase to use them after " -"downloading." +#: ../system/integrations/checkmk/api-reference.rst:149 +msgid "ticket number" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:73 -msgid "Dialogue to download certificates or private keys" +#: ../system/integrations/checkmk/api-reference.rst:151 +msgid "created_by_id" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:73 -msgid "Download stored certificates and their keys" +#: ../system/integrations/checkmk/api-reference.rst:152 +msgid "updated_by_id" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:78 -msgid "" -"The ticket composer will set all outgoing messages to **signed and " -"encrypted** by default (assuming the required certificates exist)." +#: ../system/integrations/checkmk/api-reference.rst:155 +msgid "Which Values Can Be Set?" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:82 -msgid "These defaults can be modified on a per-group basis:" +#: ../system/integrations/checkmk/api-reference.rst:157 +msgid "😵 **Invalid values → unpredictable behavior**" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:None -msgid "Zammad allowing to choose the default behavior on per group basis" +#: ../system/integrations/checkmk/api-reference.rst:159 +msgid "" +"If you provide a value that Zammad doesn't understand (*e.g.,* ``-F " +"\"priority=high\"``), it's not always clear what will happen. In some cases, " +"a ticket will be created with the default values instead - but in others, it " +"may not be created at all!" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:89 -msgid "" -"Of course, agents can always manually change these settings on each email " -"they send out." +#: ../system/integrations/checkmk/api-reference.rst:164 +msgid "So what values does Zammad understand, then? Well, it depends..." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:4 -msgid "A certificate *and* private key for your own organization" +#: ../system/integrations/checkmk/api-reference.rst:168 +msgid "Use an email address or username:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:6 -msgid "" -"(Use this to ✒️ **sign outgoing messages** and 🔓 **decrypt incoming " -"messages**.)" +#: ../system/integrations/checkmk/api-reference.rst:190 +msgid "group & priority" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:9 -msgid "" -"Certificates belonging your contacts, or their issuing certificate authority " -"(CA)" +#: ../system/integrations/checkmk/api-reference.rst:175 +msgid "Refer to the dropdown menus in the ticket pane:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:11 -msgid "" -"(Use these to ✅ **verify incoming message signatures** and 🔒 **encrypt " -"outgoing messages**.)" +#: ../system/integrations/checkmk/api-reference.rst:0 +msgid "See possible values for certain attributes in the ticket pane." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:14 -msgid "🙋 **I'm new to S/MIME. Where can I get a certificate?**" +#: ../system/integrations/checkmk/api-reference.rst:187 +msgid "🙅 **Ticket state CANNOT be set this way!**" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:16 +#: ../system/integrations/checkmk/api-reference.rst:189 msgid "" -"The easiest way to get certificates is to buy an annual subscription through " -"a commercial CA, such as:" +"Why? Because ``-F \"state=...\"`` is already used :ref:`as a Checkmk " +"parameter `." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:19 -msgid "" -"`Sectigo (formerly Comodo) `_" +#: ../system/integrations/checkmk/api-reference.rst:222 +msgid "Everything Else" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:20 -msgid "`Secorio `_" +#: ../system/integrations/checkmk/api-reference.rst:193 +msgid "" +"To set any other attributes, it helps to know your way around the :docs:" +"`rails console `. Valid values are those that you can " +"set with a string:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:21 -msgid "`GlobalSign `_" +#: ../system/integrations/checkmk/api-reference.rst:218 +msgid "These values can then be passed directly to the API:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:23 -msgid "(Zammad is not affiliated with these CAs in any way.)" +#: ../system/integrations/checkmk/index.rst:16 +msgid "How does it work?" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:25 -msgid "" -"You can also generate your own self-signed certificates, but the process is " -"complicated and usually 🙅 **involves extra work for your contacts**." +#: ../system/integrations/checkmk/index.rst:2 +msgid "Checkmk" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:29 +#: ../system/integrations/checkmk/index.rst:4 msgid "" -"Bear in mind that 🤝 **S/MIME only works if the other party is using it, too." -"**" +"`Checkmk `_ is a powerful IT monitoring tool that can " +"send real-time status alerts to Zammad via email or REST API. Set these " +"alerts up in Checkmk, and Zammad will automatically create, update, and " +"close tickets based on the health of your system:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:32 -msgid "Certificate and Private Key Checks on Upload" +#: ../system/integrations/checkmk/index.rst:14 +msgid "Screenshot of ticket created by Checkmk notifications" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:34 -msgid "" -"The certificate and public key validation is based on the ``X509v3`` " -"extensions." +#: ../system/integrations/checkmk/index.rst:14 +msgid "Multiple alerts, same ticket." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:49 -msgid "Uploading a *client certificate*?" +#: ../system/integrations/checkmk/setup-guide.rst:2 +msgid "Setup Guide" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:41 -msgid "The following attributes are required then:" +#: ../system/integrations/checkmk/setup-guide.rst:4 +msgid "" +"Whenever the Checkmk integration is enabled, Zammad listens for messages on " +"its API and over email. As long as those messages follow the required " +"format, Zammad will create new tickets (or find and update existing ones) " +"based on the message contents." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:39 -msgid "Subject Alternative Name (at least one email address has to be present)" +#: ../system/integrations/checkmk/setup-guide.rst:10 +msgid "" +"That means that “setting up Checkmk integration” is simply a matter of " +"**adding configuration to your Checkmk site**: telling it when to send these " +"messages and what to say. To do that, you'll need to create a new " +"**notification rule** (see `Checkmk's official docs `_ for help with that)." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:40 -msgid "Key Usage (``Digital Signature`` and/or ``Key Encipherment``)" +#: ../system/integrations/checkmk/setup-guide.rst:17 +msgid "" +"As part of this new rule, you'll have to choose a **notification method** " +"(*i.e.,* a script to execute whenever the rule is triggered). This script " +"will be written by you (samples below), and contain the logic for sending " +"API/email messages to Zammad:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:41 -msgid "Public key algorithm (either ``RSA`` or ``EC``)" +#: ../system/integrations/checkmk/setup-guide.rst:26 +msgid "Checkmk \"New Rule\" dialog" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:43 +#: ../system/integrations/checkmk/setup-guide.rst:26 msgid "" -"The Extended Key Usage attribute is optional. If the certificate provides " -"the named attribute, than it must contain the value ``E-mail Protection``." +"Find your custom scripts in the Checkmk WATO under **Notifications > New " +"Rule > Notification Method**." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:46 +#: ../system/integrations/checkmk/setup-guide.rst:29 msgid "" -"Please note that any usable email adress has to be prefixed with ``email:`` " -"or ``rfc822:``." +"Once you're done setting up your new rule, you're all set! New tickets " +"should start coming in and auto-updating any time your rule is triggered." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:49 -msgid "The named public key algorithms are mandatory for private keys as well." +#: ../system/integrations/checkmk/setup-guide.rst:33 +msgid "" +"(If you need help troubleshooting, be sure to check the :ref:`checkmk-recent-" +"logs`.)" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:54 -msgid "Uploading a *CA certificate*?" +#: ../system/integrations/checkmk/setup-guide.rst:38 +msgid "API Alerts" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:52 +#: ../system/integrations/checkmk/setup-guide.rst:40 msgid "" -"In the case of an uploaded CA certificate, providing the value ``CA:TRUE`` " -"in the attribute *Basic Contstraints*, the previously mentioned attributes " -"are not verified." +"To add these scripts in the Checkmk WATO, copy them into your Checkmk " +"installation directory and make them executable. (Be sure to replace the " +"``zammad.example.com`` callback URL with the one found in your admin panel.)" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:56 +#: ../system/integrations/checkmk/setup-guide.rst:60 +msgid "Service notification" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:46 msgid "" -"In general, the usage of any expired (``Not After``) or not yet valid (``Not " -"Before``) certificate is denied for outgoing emails." +"For updates on the status of the software running on your server (*e.g.,* " +"postgres)." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:59 -msgid "Example certificate:" +#: ../system/integrations/checkmk/setup-guide.rst:75 +msgid "Host notification" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:85 -msgid "" -"Please note that Zammad will distrust senders by default. This means that " -"you're always required to provide certificate data, no matter if for signing " -"or encrypting." +#: ../system/integrations/checkmk/setup-guide.rst:63 +msgid "For updates on the status of the server itself." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:89 -msgid "This is by design and can't be adjusted." +#: ../system/integrations/checkmk/setup-guide.rst:77 +msgid "🤔 **What's with all the env vars?**" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:4 +#: ../system/integrations/checkmk/setup-guide.rst:79 msgid "" -"All of the system's latest S/MIME activity is displayed in the **Recent " -"Logs** section." +"Whenever Checkmk runs these scripts, it needs to provide some information " +"about the event that triggered the notification. This information is passed " +"in the form of these ``$NOTIFY_*`` environment variables." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:11 -msgid "Sample entries of in- and outgoing S/MIME related emails." +#: ../system/integrations/checkmk/setup-guide.rst:85 +msgid "" +"You can specify additional parameters to pass to the script when you're " +"setting up your notification rule, but the ones you see here are all " +"provided by default." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:11 -msgid "" -"Logs report the status and details of all mail, both incoming and outgoing, " -"that used signing/verification or encryption/decryption." +#: ../system/integrations/checkmk/setup-guide.rst:90 +msgid "Email Alerts" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:14 +#: ../system/integrations/checkmk/setup-guide.rst:94 msgid "" -"This log does **not** include email sent by :doc:`triggers ` or the :doc:`scheduler `. For those, check your " -"``production.log``." +"🐞 **There are known bugs** in Zammad's processing of email from Checkmk. " +"This section will be completed once they have been resolved. (Learn more at " +"GitHub issues `#2377 `_ & " +"`#2180 `_.)" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:20 -msgid "Common Issues" +#: ../system/integrations/checkmk/setup-guide.rst:100 +msgid "In the meantime, we encourage you to set up API alerts instead." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:30 -msgid "I received a signed/encrypted email before I set up S/MIME integration" +#: ../system/integrations/clearbit.rst:2 +msgid "Clearbit" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:23 +#: ../system/integrations/clearbit.rst:4 msgid "" -"No problem. Once S/MIME has been enabled and the appropriate certificates " -"have been added, agents will be prompted to retry verification/decryption on " -"matching emails." +"With our Clearbit integration, you can easily enrich the information " +"provided by Zammad. If the customers or agents email address is known to " +"Clearbit, it will share all information it has regarding the user with " +"Zammad. Those information can include the following:" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:0 -msgid "Screenshot of user prompt to retry decryption" +#: ../system/integrations/clearbit.rst:9 +msgid "Avatar" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:38 -msgid "The 🔒 **Encrypt** button is disabled" +#: ../system/integrations/clearbit.rst:10 +msgid "Address information" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:33 -msgid "Have you added the recipient's certificate?" +#: ../system/integrations/clearbit.rst:11 +msgid "Website information" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:34 -msgid "Are you sure the recipient's certificate is valid?" +#: ../system/integrations/clearbit.rst:12 +msgid "A BIO (as Note by default)" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:35 -msgid "Have you checked your ``production.log`` for more details?" +#: ../system/integrations/clearbit.rst:14 +msgid "" +"If needed, you can add further custom objects and add mappings to them, so " +"the Clearbit information can be filled within the database. In general you " +"can get any information from Clearbit, as long as you have a mapping to an " +"Zammad object." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:37 +#: ../system/integrations/clearbit.rst:21 msgid "" -"If encryption doesn't work in the composer, it won't work in :doc:`triggers " -"` or the :doc:`scheduler ` either!" +"Clearbit does have a mapping of fields like LDAP and Exchange have, but does " +"not \"win\" against Zammad information. This means that if you have e.g. the " +"last name field filled in already and Clearbit has other information on " +"that, it will not be updated." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:42 -msgid "The ✅ **Sign** button is disabled" +#: ../system/integrations/clearbit.rst:26 +msgid "" +"However: If let's say the last name has been set by Clearbit and Zammad " +"notices that the last name on the Clearbit source has changed, Zammad will " +"also update this value." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:41 +#: ../system/integrations/clearbit.rst:33 msgid "" -"Have you added **both the certificate and private key** for your " -"organization?" +"The configuration of Clearbit is really easy and done fast! Just login to " +"your Clearbit-Account, go to \"API\" and copy the secret-API-Key." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:42 +#: ../system/integrations/clearbit.rst:38 msgid "" -"Does the email address on the certificate match the email address of the " -"agent/group composing the email?" +"Now change to your Zammad instance, go to Integrations (System) -> Clearbit " +"in the admin panel. Paste your API-Key into the API-Key-Field and decide if " +"Zammad should create unknown Organizations automatically, if the user does " +"not have one yet (and Clearbit knows it). The shared option decides if the " +"new organizations Zammad creates with Clearbit should be shared ones." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:45 -msgid "Error: “Fingerprint already taken”" +#: ../system/integrations/clearbit.rst:47 +msgid "" +"If you're unsure what option to choose, better stick with \"no\". You can " +"also learn more about :doc:`/manage/organizations/index`." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:45 -msgid "Are you sure you haven't added this certificate already?" +#: ../system/integrations/clearbit.rst:52 +msgid "" +"The Mapping option works similar to the mapping within the Exchange and LDAP " +"sync. You can add further mappings for e.g. custom fields if you need more " +"information that Clearbit can provide." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:48 -msgid "Error: “❌ invalid byte sequence in UTF-8”" +#: ../system/integrations/clearbit.rst:58 +msgid "" +"If you want to add more Clearbit fields and want to learn more about " +"available fields on their API, you can take a look at their `API " +"documentation `_." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:48 -msgid "Please ensure to provide PEM formatted certificate and keys." +#: ../system/integrations/clearbit.rst:62 +msgid "" +"If you're happy with the above chosen Settings and your mapping, just save " +"the changes and enable Clearbit integration. Zammad will now start polling " +"the Clearbit API as users contact you." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:49 -msgid "Did you check if the provided file is a valid certificate or key?" +#: ../system/integrations/clearbit.rst:68 +msgid "" +"Zammad does not synchronize with Clearbit on a regular basis, but on demand " +"if needed. This saves API calls." msgstr "" -#: ../system/integrations/zabbix.rst:2 -msgid "Zabbix Integration" +#: ../system/integrations/clearbit.rst:73 +msgid "" +"Below the Settings and Mappings, you'll find our Integration log. You can " +"see what requests Zammad sent to Clearbit and also the APIs Response." msgstr "" -#: ../system/integrations/zabbix.rst:5 +#: ../system/integrations/clearbit.rst:78 msgid "" -"This guide describes how to integrate your Zabbix 5.4 installation with " -"Zammad using the Zabbix webhook feature. This guide will provide " -"instructions on setting up a media type, a user and an action in Zabbix." +"By the way, you can also view the API log on the Clearbit website - the " +"information seen is basically the same." msgstr "" -#: ../system/integrations/zabbix.rst:12 -msgid "Zammad with enabled HTTP Token Authentication" +#: ../system/integrations/clearbit.rst:84 +msgid "Example When Adding a User" msgstr "" -#: ../system/integrations/zabbix.rst:13 -msgid "Zabbix version 5.4 or higher" +#: ../system/integrations/clearbit.rst:86 +msgid "" +"To show you how fast information is added, we added a small Screencast " +"below. This shows the creation of the User Alex from Clearbit. As we already " +"set the last name of Alex to \"X\", Zammad did not update it. What Zammad " +"did was to add further information it received from Clearbit." msgstr "" -#: ../system/integrations/zabbix.rst:16 -msgid "Setting up a Zammad" +#: ../system/integrations/cti/generic.rst:2 +msgid "CTI (generic)" msgstr "" -#: ../system/integrations/zabbix.rst:18 -msgid "Enable **API Token Access** in Settings > System > API." +#: ../system/integrations/cti/includes/introduction.include.rst:1 +msgid "" +"This integration enables Zammad to provide a caller log to your agents. With " +"this your agents can greet your customers by their name and are supported by " +"Zammad with automatically opening a new ticket dialog or the user profile." msgstr "" -#: ../system/integrations/zabbix.rst:20 +#: ../system/integrations/cti/includes/introduction.include.rst:6 msgid "" -"Create a **new user** for a Zabbix alerter with an **email address** and " -"create a personal user token with **ticket.agent** permissions." +"Click the toggle next to the heading to activate or deactivate this " +"integration." msgstr "" -#: ../system/integrations/zabbix.rst:24 -msgid "Zabbix Webhook Configuration" +#: ../system/integrations/cti/includes/introduction.include.rst:9 +msgid "" +"If you want to learn more on how your agents can use this function, please " +"refer the :user-docs:`user documentation `." msgstr "" -#: ../system/integrations/zabbix.rst:27 -#, fuzzy -msgid "Create a Global Macro" -msgstr "Создать Макрос" - -#: ../system/integrations/zabbix.rst:29 +#: ../system/integrations/cti/includes/introduction.include.rst:14 msgid "" -"Before setting up the **Webhook**, you need to setup the global macro " -"**{$ZABBIX.URL}**, which must contain the **URL** to the **Zabbix frontend**." +"Automatically opening new ticket dialogues or user profiles requires agent " +"to extension mapping - see more below." msgstr "" -#: ../system/integrations/zabbix.rst:33 -msgid "" -"In the **Administration** > **Media types** section, import the `Template`_." +#: ../system/integrations/cti/includes/introduction.include.rst:20 +msgid "Please note the following limitations to reduce confusion later on:" msgstr "" -#: ../system/integrations/zabbix.rst:38 -msgid "Open the added **Zammad** media type and set:" +#: ../system/integrations/cti/includes/introduction.include.rst:22 +msgid "CTI integrations provide caller log functions only." msgstr "" -#: ../system/integrations/zabbix.rst:40 -msgid "**zammad\\_access\\_token** to the your **Personal User Token**" +#: ../system/integrations/cti/includes/introduction.include.rst:23 +msgid "" +"This integration does not provide any VoIP functionalities; you can't make " +"phone calls from within Zammad." msgstr "" -#: ../system/integrations/zabbix.rst:41 +#: ../system/integrations/cti/includes/introduction.include.rst:25 msgid "" -"**zammad\\_url** to the **frontend URL** of your **Zammad** installation" +"If your browser supports ``tel``-URLs, you can click on phone numbers for " +"automatic dialing. This requires additional software / configuration on your " +"agent's computers." msgstr "" -#: ../system/integrations/zabbix.rst:43 -msgid "**zammad\\_customer** to your **Zammad user email**." +#: ../system/integrations/cti/generic.rst:9 +#: ../system/integrations/cti/placetel.rst:14 +#: ../system/integrations/cti/sipgate.rst:14 +msgid "Please provide the following requirements:" msgstr "" -#: ../system/integrations/zabbix.rst:44 +#: ../system/integrations/cti/generic.rst:11 msgid "" -"**zammad\\_enable\\_tags** to **true** or **false** to enable or disable " -"trigger tags. **Important**: if you enable tag support, each tag is set with " -"a separate request." +"A telephone system that supports webhooks (outbound) (best option are those " +"that allow customizing the calls)." msgstr "" -#: ../system/integrations/zabbix.rst:48 -msgid "" -"If you want to prioritize issues according to **severity** values in Zabbix, " -"you can define mapping parameters:" +#: ../system/integrations/cti/generic.rst:13 +msgid "A unique Call-ID during the call session." msgstr "" -#: ../system/integrations/zabbix.rst:51 -msgid "**severity\\_**: Zammad priority ID" +#: ../system/integrations/cti/generic.rst:14 +msgid "Call event data (both numbers and direction)." msgstr "" -#: ../system/integrations/zabbix.rst:53 -msgid "Click the **Update** button to save the **Webhook** settings." +#: ../system/integrations/cti/generic.rst:15 +msgid "Your Zammad instance must be reachable for your telephony system." msgstr "" -#: ../system/integrations/zabbix.rst:55 +#: ../system/integrations/cti/generic.rst:17 msgid "" -"To receive notifications in **Zammad**, you need to create a **Zabbix user** " -"and add **Media** with the **Zammad** type." +"If you want to learn more on what kind of requests are supported by Zammad " +"and what it expects, please consult our :docs:`CTI-API documentation `." msgstr "" -#: ../system/integrations/zabbix.rst:58 -msgid "" -"For **Send to**: enter any text, as this value is not used, but is required." +#: ../system/integrations/cti/generic.rst:22 +#: ../system/integrations/cti/placetel.rst:27 +#: ../system/integrations/cti/sipgate.rst:30 +msgid "Available Settings" msgstr "" -#: ../system/integrations/zabbix.rst:61 -msgid "" -"For more information, use the `Zabbix documentation `_." +#: ../system/integrations/cti/generic.rst:29 +#: ../system/integrations/cti/placetel.rst:41 +#: ../system/integrations/cti/sipgate.rst:40 +msgid "Endpoint Settings" msgstr "" -#: ../system/maintenance.rst:2 -msgid "Maintenance" +#: ../system/integrations/cti/generic.rst:25 +msgid "" +"Zammad will list your generic CTI endpoint here. It contains a unique token " +"so ensure to keep this URL save." msgstr "" -#: ../system/maintenance.rst:4 +#: ../system/integrations/cti/generic.rst:28 msgid "" -"Zammad comes with a maintenance mode that you can use for e.g. updating the " -"instance or changing settings while restricting availability and functions." +"You'll need this endpoint for your PBX to talk to Zammad, see :docs:`CTI-API " +"documentation `." msgstr "" -#: ../system/maintenance.rst:13 -msgid "Mode" +#: ../system/integrations/cti/includes/important-dont-forget-saving.include.rst:3 +msgid "" +"All following options **do not save automatically**. Always use the Save " +"button on the lower end of the integration page!" msgstr "" -#: ../system/maintenance.rst:8 -msgid "The mode setting allows you to enable or disable the maintenance mode." +#: ../system/integrations/cti/generic.rst:43 +#: ../system/integrations/cti/placetel.rst:49 +#: ../system/integrations/cti/sipgate.rst:52 +msgid "Call Settings" msgstr "" -#: ../system/maintenance.rst:10 -msgid "Defaults to *off*." +#: ../system/integrations/cti/generic.rst:39 +#: ../system/integrations/cti/placetel.rst:49 +#: ../system/integrations/cti/sipgate.rst:37 +#: ../system/integrations/cti/sipgate.rst:50 +msgid "Inbound" msgstr "" -#: ../system/maintenance.rst:12 -msgid "" -"The maintenance mode will restrict access to administrative roles only. This " -"means agents and customers are logged off." -msgstr "" - -#: ../system/maintenance.rst:23 -msgid "@Login" -msgstr "" - -#: ../system/maintenance.rst:16 -msgid "" -"This setting allows you to provide a login message within a green banner " -"above the login screen. Click into the green banner in the settings page to " -"adjust your message. To activate the message, activate the *@Login* setting." -msgstr "" - -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing the default login message within the\n" -"settings page" -msgstr "" - -#: ../system/maintenance.rst:26 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:1 msgid "" -"Send an informative message to **all active sessions**. This comes handy to " -"inform your agents e.g. about mayor outages or to force reloads after " -"configuration changes." -msgstr "" - -#: ../system/maintenance.rst:31 -msgid "This is the messages title (slightly bigger than the normal message)." +"This option allows you to block specific incoming caller IDs. It allows you " +"to temporarily reject e.g. spam callers without having to contact providers " +"or PBX administrators." msgstr "" -#: ../system/maintenance.rst:34 -msgid "The text you want to provide to your logged in sessions." +#: ../system/integrations/cti/includes/inbound-calls.include.rst:11 +msgid "Caller ID to block" msgstr "" -#: ../system/maintenance.rst:39 -msgid "Reload application" +#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 +msgid "Provide caller IDs to block in ``E.164`` format." msgstr "" -#: ../system/maintenance.rst:37 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:8 msgid "" -"Selecting this option will change the message acceptance button from *Close* " -"(with nothing happening) to *Continue session*, which forces the application " -"to reload." +"Your telephony system has to support this function. Zammad will send a " +"``reject`` response which will cause your telephony system to hang up the " +"call. To callers this usually will feel like the line is busy." msgstr "" -#: ../system/maintenance.rst:43 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:14 msgid "" -"If you have customers that are logged in to Zammad, they'll also be notified " -"if they're active in that moment." -msgstr "" - -#: ../system/maintenance.rst:48 -msgid "Example without reload application" +"Provide a meaningful note for your fellow administrators to remind yourself " +"why you've chosen to block the number." msgstr "" -#: ../system/maintenance.rst:52 -msgid "" -"Message setting within Zammad's admin settings without ticket reload " -"application setting." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:17 +#: ../system/integrations/cti/sipgate.rst:40 +msgid "Outbound" msgstr "" -#: ../system/maintenance.rst:0 +#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:1 msgid "" -"Screenshot showing the send message settings without ticket\n" -"reload application set" +"In many cases you may want to use a different caller ID depending on the " +"destination you're calling. This may apply due to specific connection rates " +"to other countries or because you want your customer to feel you're calling " +"from the same country." msgstr "" -#: ../system/maintenance.rst:61 ../system/maintenance.rst:85 -msgid "" -"The modal all other active sessions will see upon pressing *Send to clients*." +#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:6 +msgid "This option expects ``E.164`` number formats." msgstr "" -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing modal caused by maintenance's message\n" -"without reload application ticket" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 +msgid "Destination caller ID" msgstr "" -#: ../system/maintenance.rst:72 -msgid "Example with reload application" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:5 +msgid "The caller ID or number you're trying to call." msgstr "" -#: ../system/maintenance.rst:76 -msgid "" -"Message setting within Zammad's admin settings with ticket reload " -"application setting." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:7 +msgid "You can use wildcards for e.g. country specific outbound numbers like:" msgstr "" -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing the send message settings with ticket\n" -"reload application set" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:9 +msgid "``49*`` for Germany" msgstr "" -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing modal caused by maintenance's message\n" -"with reload application ticket" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:10 +msgid "``4930*`` for Berlin / Germany landlines" msgstr "" -#: ../system/monitoring.rst:2 -msgid "Monitoring" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 +msgid "``33*`` for France" msgstr "" -#: ../system/monitoring.rst:4 -msgid "" -"This function is only available in self hosted instances. If you use Zammad " -"in our cloud, we are monitoring the system on our own and take steps to fix " -"potential problems directly." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:15 +msgid "Set Outbound caller ID" msgstr "" -#: ../system/monitoring.rst:11 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:14 msgid "" -"On the monitoring page, you can see the current health state of Zammad under " -"\"*Current Status*\" at the bottom. This can be useful if you want to have a " -"look if everything is up and running. As an example, you could have a look " -"in the monitoring when you assume that some emails aren't processed from " -"Zammad." +"The outbound caller ID to set (the number your customer sees on his display) " +"in ``E.164`` number format." msgstr "" -#: ../system/monitoring.rst:17 -msgid "**Can't receive an email and the monitoring response is \"healthy\"?**" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 +msgid "Provide a short description for fellow administrators." msgstr "" -#: ../system/monitoring.rst:19 +#: ../system/integrations/cti/includes/generic-cti-support-note.includes.rst:3 msgid "" -"Zammad will just inform you about unprocessable emails. This is not the case " -"for oversized emails. You can adjust the maximum email size in :doc:`../" -"channels/email/settings`." +"This option requires your PBX to send a specific request to Zammad *before " +"dialing*. Please consult the :docs:`CTI API ` in case " +"you're not sure." msgstr "" -#: ../system/monitoring.rst:24 -msgid "Monitoring API" +#: ../system/integrations/cti/generic.rst:52 +#: ../system/integrations/cti/placetel.rst:54 +#: ../system/integrations/cti/sipgate.rst:59 +msgid "Other Settings" msgstr "" -#: ../system/monitoring.rst:26 +#: ../system/integrations/cti/includes/other-settings-intro.include.rst:1 msgid "" -"Beside the indication in the monitoring page, you can also use an external " -"monitoring tool to monitor Zammad's health. To request the health of Zammad, " -"you need to provide the API key (token) to the external monitoring tool. You " -"can copy the token from the \"*Current Token*\" field as well as the whole " -"API endpoint of your system (\"*Health Check*\" field), in which the API " -"token is already included." +"Below you can find all available additional settings for this CTI " +"integration. For your overview we're sorting them by appearance and " +"reference their description first." msgstr "" -#: ../system/monitoring.rst:37 -msgid "Screenshot showing Current Token and Health Check" +#: ../system/integrations/cti/includes/default-caller-id.include.rst:2 +#: ../system/integrations/cti/includes/default-caller-id.include.rst:1 +msgid "Default caller ID for outbound calls" msgstr "" -#: ../system/monitoring.rst:37 -msgid "Screenshot showing Token and Health Check" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:16 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:15 +msgid "Shown records in caller log" msgstr "" -#: ../system/monitoring.rst:39 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:2 msgid "" -"In addition to that, you can reset the auto-generated token to make sure " -"that already configured monitoring systems won't work anymore. So, please " -"use this \"*Reset*\" button only if you know what you do!" -msgstr "" - -#: ../system/monitoring.rst:44 -#, fuzzy -msgid "Example Output" -msgstr "Пример" - -#: ../system/monitoring.rst:0 -msgid "No issues found" -msgstr "" - -#: ../system/monitoring.rst:48 ../system/monitoring.rst:60 -msgid "**Indicator in Zammad**:" -msgstr "" - -#: ../system/monitoring.rst:0 -msgid "Screenshot showing monitoring with no issues" -msgstr "" - -#: ../system/monitoring.rst:54 ../system/monitoring.rst:66 -msgid "**API response**::" -msgstr "" - -#: ../system/monitoring.rst:0 -msgid "Issues were found" +"Allows you to set the number of shown caller log entries for all users. You " +"can choose from the following values:" msgstr "" -#: ../system/monitoring.rst:0 -msgid "Screenshot showing monitoring with issues" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:5 +msgid "60 (default)" msgstr "" -#: ../system/objects.rst:2 -msgid "Objects" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:6 +msgid "120" msgstr "" -#: ../system/objects.rst:4 -msgid "" -"In Zammad you can add your own fields to tickets, users, organizations and " -"even groups (these are called \"objects\"). This can be useful if you need " -"to add further information to a ticket or any other object in Zammad and the " -"information doesn't fit in any existing field." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:7 +msgid "180" msgstr "" -#: ../system/objects.rst:11 -msgid "" -"Try to avoid deleting attributes (and disable them instead) as Zammad might " -"run into unexpected conditions if they are referenced somewhere." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:8 +msgid "240" msgstr "" -#: ../system/objects.rst:16 -msgid "" -"Here's an overview of object attributes. On the upper right you can add new " -"attributes. By default, there will be no custom fields - standard attributes " -"will be grayed out, you can't delete or change those. You can edit custom " -"attributes (they are displayed in black font and have a trash bin on the " -"right side) just by clicking on them." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:9 +msgid "300" msgstr "" -#: ../system/objects.rst:24 -msgid "" -"Attributes you add to Zammad, no matter if they have default values or not, " -"will not update existing information. This means a new ticket field " -"technically will be empty unless you populate it." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:11 +msgid "**🥵 Potential performance issue**" msgstr "" -#: ../system/objects.rst:28 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:13 msgid "" -"Especially in ticket scope this also means that newly added attributes will " -"be indicated as \"changed\" to agents that view the ticket. This may " -"interfere with Zammad's tabs behavior." +"Setting this setting higher than 60 may cause serious performance issues on " +"very busy instances. Keep in mind that this setting causes Zammad to poll " +"and send up to 300 records to *all active agent sessions* in very short time " +"periods." msgstr "" -#: ../system/objects.rst:40 -msgid "Ordering Attributes" +#: ../system/integrations/cti/generic.rst:73 +msgid "Caller Log Filter" msgstr "" -#: ../system/objects.rst:42 +#: ../system/integrations/cti/generic.rst:55 msgid "" -"Since Zammad introduced :doc:`/system/core-workflows` the need to have a " -"custom positioning for attributes has become more important than ever." +"This function allows you to provide call information based on e.g. queues " +"only to agents that really need the information." msgstr "" -#: ../system/objects.rst:45 +#: ../system/integrations/cti/generic.rst:58 msgid "" -"To adjust the position of such an attribute, simply click on the attribute " -"entry in question, scroll down and adjust the position number. Please note " -"that you cannot change the positioning of default attributes." +"Why? If you have a team for several countries or departments, you don't want " +"to bug your agents from other departments. Leaving these options empty will " +"fallback to showing everything to everyone." msgstr "" -#: ../system/objects.rst:49 -msgid "" -"In case two attributes have the same position value, Zammad will sort " -"alphabetically by name automatically." +#: ../system/integrations/cti/generic.rst:64 +msgid "Destination caller ID or Queue" msgstr "" -#: ../system/objects.rst:None +#: ../system/integrations/cti/generic.rst:63 msgid "" -"Screenshot showing custom attribute entries ordered in between default ones" +"This depends on your PBX and usually is either a queue ID, phone number or " +"extension." msgstr "" -#: ../system/objects.rst:56 -msgid "Updating Database After Adding or Editing Attributes" +#: ../system/integrations/cti/generic.rst:69 +msgid "Agents" msgstr "" -#: ../system/objects.rst:58 +#: ../system/integrations/cti/generic.rst:67 msgid "" -"When adding or changing attributes, Zammad will not apply the changes " -"instantly, but instead shows you the changed attributes first. If you're " -"ready to go, just click on \"Update database\" to apply the changes to " -"Zammad. If you made a mistake or just want to discard your changes, click " -"\"Discard changes\"." +"Select the agents that are responsible for the group. These agents will then " +"see caller log entries and call notifications fitting to said queue." msgstr "" -#: ../system/objects.rst:64 +#: ../system/integrations/cti/generic.rst:0 msgid "" -"After applying the changes with \"Update Database\", a restart of Zammad is " -"**mandatory**. If you don't perform it, you may experience unexpected " -"behavior or even errors. You may want to do this kind of configuration " -"during maintenance windows." +"Screenshot showing the caller log filter table with pre filled sample data" msgstr "" -#: ../system/objects.rst:72 +#: ../system/integrations/cti/includes/recent-logs.include.rst:6 msgid "" -"Changes on objects require you to update the database to apply these changes." -msgstr "" - -#: ../system/objects.rst:75 -msgid "**🤓 Service restarts can be automated**" -msgstr "" - -#: ../system/objects.rst:0 -msgid "Hosted environments automatically restart for you." +"With recent logs Zammad allows you to view the latest calls for the CTI " +"functionality. This usually comes in handy, when you're looking for errors." msgstr "" -#: ../system/objects.rst:0 +#: ../system/integrations/cti/includes/recent-logs.include.rst:0 msgid "" -"If you're using a self-hosted installation you can use :docs:`environment " -"variables `" -msgstr "" - -#: ../system/objects.rst:82 -msgid "System Attributes" +"Screenshot showing several incoming requests within Recent logs section." msgstr "" - -#: ../system/objects.rst:84 -msgid "" -"Zammad comes with pre-configured attributes. Some of them can't be edited " -"via UI (or at all). This is required for proper operation of Zammad and not " -"a bug." + +#: ../system/integrations/cti/includes/recent-logs.include.rst:16 +msgid "I'm just here to clear floats up." msgstr "" -#: ../system/objects.rst:90 -msgid "Ticket State" +#: ../system/integrations/cti/includes/recent-logs.include.rst:20 +msgid "" +"By clicking on the entry of interest, Zammad will provide more details on " +"the call in question. You'll see the payload it received and also the " +"response that was sent." msgstr "" -#: ../system/objects.rst:92 +#: ../system/integrations/cti/includes/recent-logs.include.rst:0 msgid "" -"If the pre-configured states aren't enough for you or you want to change " -"them, you can do so by clicking on the cogwheel icon in the state row in the " -"ticket tab. But you should be careful when changing pre-configured states. " -"This can lead to unwanted behavior in some cases." +"Screenshot showing detailed information of a specific log entry of recent " +"logs" msgstr "" -#: ../system/objects.rst:None -msgid "Screenshot showing highlighted ticket state attribute" +#: ../system/integrations/cti/includes/recent-logs.include.rst:31 +msgid "x" msgstr "" -#: ../system/objects.rst:122 -msgid "Handling of states" +#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 +#: ../system/integrations/cti/includes/troubleshooting.include.rst:9 +msgid "My Phone page stays blank, signalling does work..." msgstr "" -#: ../system/objects.rst:102 +#: ../system/integrations/cti/includes/troubleshooting.include.rst:5 msgid "" -"In the state configuration screen, you can add new states, disable states or " -"change states." +"If you've made sure that signalling works (check Recent logs) and your " +"Caller Log still stays empty, please ensure that you only configured one CTI " +"integration version. Specifically defining more than one agent mapping on " +"the different integration variants will be the issue." msgstr "" -#: ../system/objects.rst:0 -msgid "Screenshot showing table of default ticket states" +#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 +msgid "Clear the not needed agent mapping and reload your browser page." msgstr "" -#: ../system/objects.rst:110 +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:1 msgid "" -"To add a new state, click on the \"New Ticket State\" button in the top " -"right corner. To change an existing state, simply click on the affected " -"state. This opens an edit dialog." +"By mapping your agents extension to their existing Zammad users, Zammad can " +"provide a new ticket dialog or open the user profile for the agent that " +"picks up the call." msgstr "" -#: ../system/objects.rst:114 +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:5 msgid "" -"You can also clone a state or set them to \"Default for new tickets\" or " -"\"Default for follow-ups\" by clicking on the ⁝ action button and select the " -"desired function." +"This speeds up ticket aiding, no matter if it's for existing tickets or new " +"ones!" msgstr "" -#: ../system/objects.rst:118 +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:8 msgid "" -"*Default for new tickets* means that this state is used for every newly " -"created ticket." +"To see it work from the agent's perspective, have a look on :user-docs:`user " +"documentation `." msgstr "" -#: ../system/objects.rst:121 -msgid "" -"*Default for follow-ups* means that this state is used if the ticket is re-" -"opened after it was closed." +#: ../system/integrations/cti/placetel.rst:2 +msgid "Placetel CTI" msgstr "" -#: ../system/objects.rst:171 -msgid "Ticket state in detail" +#: ../system/integrations/cti/placetel.rst:16 +msgid "You need an administrative Placetel account for your organization." msgstr "" -#: ../system/objects.rst:125 +#: ../system/integrations/cti/placetel.rst:17 +#: ../system/integrations/cti/sipgate.rst:20 msgid "" -"Below you can find a description for each field and option. Please head over " -"to the :ref:`example ` to see the edit dialog." +"Your Zammad instance must be allowed to communicate to external services." msgstr "" -#: ../system/objects.rst:129 -msgid "" -"This is the name of the state and what you and your agents are seeing when " -"choosing a state somewhere (e.g. in tickets, trigger configuration)." +#: ../system/integrations/cti/placetel.rst:18 +msgid "Placetel must be able to reach your Zammad instance." msgstr "" -#: ../system/objects.rst:137 -msgid "" -"There are different state types you can choose from. By default, Zammad " -"comes with one state per state type." +#: ../system/integrations/cti/placetel.rst:22 +msgid ":doc:`provider-configurations/placetel`" msgstr "" -#: ../system/objects.rst:140 +#: ../system/integrations/cti/placetel.rst:21 msgid "" -"**new**: for states for tickets that are new and it hasn't been worked on " -"them" +"Learn how to configure Placetel to enable Zammad and Placetel to communicate " +"with each other." msgstr "" -#: ../system/objects.rst:142 +#: ../system/integrations/cti/placetel.rst:32 msgid "" -"**open**: for states for tickets that are in progress and agents are working " -"on them" -msgstr "" - -#: ../system/objects.rst:144 -msgid "**merged**: for states for tickets that are merged with other tickets" +"The here listed endpoint settings are relevant for the :doc:`integration " +"configuration with Placetel `." msgstr "" -#: ../system/objects.rst:145 -msgid "" -"**pending reminder**: for states for tickets that are in progress and you " -"want to set a reminder. (default example: *pending reminder*)" +#: ../system/integrations/cti/placetel.rst:37 +#: ../system/integrations/i-doit.rst:53 +msgid "Endpoint" msgstr "" -#: ../system/objects.rst:147 +#: ../system/integrations/cti/placetel.rst:36 msgid "" -"**pending action**: for states for tickets that are waiting for a specified " -"time and then change their state (default example: *pending close*)" +"This endpoint will be required for the Zammad integration within the " +"Placetel web interface." msgstr "" -#: ../system/objects.rst:150 -msgid "" -"**closed**: for states for tickets that are finished and do not need to be " -"processed further" +#: ../system/integrations/cti/placetel.rst:41 +msgid "API Token" msgstr "" -#: ../system/objects.rst:153 +#: ../system/integrations/cti/placetel.rst:40 msgid "" -"⚠️ Choosing the correct state type is important! If you are in doubt, have a " -"look on the default states and their types!" +"You'll receive this token within the ``Web API`` menu. Make sure to copy " +"this value, it's only shown once!" msgstr "" -#: ../system/objects.rst:158 -msgid "Ignore escalation" +#: ../system/integrations/cti/placetel.rst:71 +#: ../system/integrations/cti/sipgate.rst:77 +msgid "Phone Extension to Agent Mapping" msgstr "" -#: ../system/objects.rst:157 -msgid "" -"Here you can define whether tickets of this state will count to escalation " -"time or not." +#: ../system/integrations/cti/placetel.rst:0 +msgid "Screenshot showing sample user mappings in between Placetel and Zammad" msgstr "" -#: ../system/objects.rst:161 +#: ../system/integrations/cti/placetel.rst:64 msgid "" -"You can create a note for the state to inform other admins about the state. " -"This has no effect on tickets." +"You can find your agents Placetel username combination required within ⚙️ PBX " +"→ VoIP destinations. Within the \"Advanced settings\" section you're looking " +"for \"SIP user name\" and \"SIP server\"." msgstr "" -#: ../system/objects.rst:165 -msgid "Set the state to *active* or *inactive*." +#: ../system/integrations/cti/placetel.rst:68 +msgid "Combine these two like so: ``@``." msgstr "" -#: ../system/objects.rst:167 -msgid "" -"it is technically possible to set all states to inactive. To keep Zammad " -"working in such a case, the inactive flag of one of the states is ignored." +#: ../system/integrations/cti/placetel.rst:0 +msgid "Sample VoIP credentials for a Placetel user" msgstr "" -#: ../system/objects.rst:194 -msgid "Ticket state example" +#: ../system/integrations/cti/provider-configurations/placetel.rst:2 +msgid "Setup Placetel connection for Zammad" msgstr "" -#: ../system/objects.rst:174 +#: ../system/integrations/cti/provider-configurations/placetel.rst:6 msgid "" -"Let's assume we want to create a new state which indicates that the ticket " -"has to wait for a response of a third party (e.g. service contractor or " -"manufacturer) and we want to to be able to set a reminder." +"This configuration step requires a *full* administrative Placetel account. " +"You may receive forbidden error messages with Placetel in case your " +"permissions are not high enough." msgstr "" -#: ../system/objects.rst:178 +#: ../system/integrations/cti/provider-configurations/placetel.rst:10 msgid "" -"First we give the new state a proper name. In this example we call it " -"\"waiting for manufacturer\"." +"The following actions can be configured via the `Placetel web interface " +"`_." msgstr "" -#: ../system/objects.rst:181 -msgid "" -"As state type we choose \"pending reminder\". This indicates that the ticket " -"is still open and we can set a reminder. This reminder can be useful if our " -"manufacturer sometimes isn't responding or we want to remind him to give us " -"an answer." +#: ../system/integrations/cti/provider-configurations/placetel.rst:29 +msgid "Step 1: Activate Zammad integration" msgstr "" -#: ../system/objects.rst:186 +#: ../system/integrations/cti/provider-configurations/placetel.rst:14 msgid "" -"We choose \"no\" for \"ignore escalation\" because we want to escalate the " -"tickets even if we are waiting on the manufacturer's feedback." +"Within Integrations, scroll down to Partner integrations and select Zammad." msgstr "" -#: ../system/objects.rst:189 -msgid "The **result** in the creation dialog will look like this:" +#: ../system/integrations/cti/provider-configurations/placetel.rst:17 +msgid "" +"You can alternatively filter by \"Ticket Systems\" to reduce the number of " +"entries on the page. You'll still want to look for Partner integrations. 🤓" msgstr "" -#: ../system/objects.rst:0 -msgid "Screenshot showing ticket state creation dialog with example" +#: ../system/integrations/cti/provider-configurations/placetel.rst:21 +msgid "" +"Within the Zammad integration now press \"Activate\". A new tab ``API`` " +"becomes available - open this tab." msgstr "" -#: ../system/objects.rst:197 ../system/objects.rst:199 -msgid "Ticket Priority" +#: ../system/integrations/cti/provider-configurations/placetel.rst:24 +msgid "" +"Now tick \"Enable Call Control / Notify API\" and paste the Placetel " +"endpoint from your Zammad instance into the field \"URL of your API " +"endpoint\". Save to apply the settings" msgstr "" -#: ../system/objects.rst:199 ../system/objects.rst:201 -msgid "" -"If the pre-configured priorities aren't enough for you or you want to change " -"them, you can do so by clicking on the cogwheel icon in the priority row in " -"the ticket tab:" +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "Screencast showing how to activate the Zammad integration" msgstr "" -#: ../system/objects.rst:None -msgid "Screenshot showing highlighted ticket priority attribute" +#: ../system/integrations/cti/provider-configurations/placetel.rst:51 +msgid "Step 2: Generate API Token for Placetel" msgstr "" -#: ../system/objects.rst:224 ../system/objects.rst:226 -msgid "Handling of priorities" +#: ../system/integrations/cti/provider-configurations/placetel.rst:32 +msgid "" +"Go back to the integrations page and scroll down to \"Web API\". Generate a " +"new API token by using the \"Create a new API token\" button." msgstr "" -#: ../system/objects.rst:208 ../system/objects.rst:210 +#: ../system/integrations/cti/provider-configurations/placetel.rst:37 msgid "" -"In the priority configuration screen, you can add new priorities, disable " -"priorities or change priorities." +"If you already generated a token either use your existing token or reset it " +"by using above mentioned button. Placetel will ask you to conform this reset." msgstr "" -#: ../system/objects.rst:0 -msgid "Screenshot showing table of default ticket priorities" +#: ../system/integrations/cti/provider-configurations/placetel.rst:41 +msgid "" +"Please keep in mind that existing API scripts may no longer work due to " +"token resets!" msgstr "" -#: ../system/objects.rst:216 ../system/objects.rst:218 +#: ../system/integrations/cti/provider-configurations/placetel.rst:44 msgid "" -"To add a new priority, click on the \"New Priority\" button in the top right " -"corner. To change an existing priority, simply click on the affected " -"priority. This opens an edit dialog." +"Copy the provided API token and insert it into the \"API Token\" field " +"within Zammad's Placetel integration." msgstr "" -#: ../system/objects.rst:220 ../system/objects.rst:222 +#: ../system/integrations/cti/provider-configurations/placetel.rst:47 msgid "" -"You can also clone a priority or set them to \"Default for new tickets\" by " -"clicking on the ⁝ action button and select the desired function." +"Apply your changes by using the \"Save\" button on the bottom of the " +"Placetel integration page and activate the Placetel integration." msgstr "" -#: ../system/objects.rst:223 ../system/objects.rst:225 +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 msgid "" -"*Default for new tickets* means that this priority is used for every newly " -"created ticket." +"Screencast showing how to retrieve an API token from Placetel for Zammad" msgstr "" -#: ../system/objects.rst:246 ../system/objects.rst:248 -msgid "Priorities in detail" +#: ../system/integrations/cti/provider-configurations/placetel.rst:73 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:77 +msgid "Step 3: Restrict the numbers to notify on" msgstr "" -#: ../system/objects.rst:227 ../system/objects.rst:229 -msgid "Below you can find a description for each field and option." +#: ../system/integrations/cti/provider-configurations/placetel.rst:54 +msgid "" +"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " +"the the Integrations page of the Placetel web interface, go to \"Notify " +"API\"." msgstr "" -#: ../system/objects.rst:230 ../system/objects.rst:232 +#: ../system/integrations/cti/provider-configurations/placetel.rst:58 msgid "" -"This is the name of the priority and what you and your agents are seeing " -"when choosing a priority somewhere (e.g. in tickets, trigger configuration)." -msgstr "" - -#: ../system/objects.rst:240 ../system/objects.rst:242 -msgid "Highlight color" +"Lower on the page Placetel allows you to restrict the numbers to notify on. " +"You'll find this within the \"External routing API\" part." msgstr "" -#: ../system/objects.rst:235 ../system/objects.rst:237 +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 msgid "" -"Switch between *Low priority* (light blue), *High priority* (red) and - " -"(default). This affects the displayed color for ticket titles in overviews." +"Screenshot showing a sample selection of phone numbers to use for the " +"Placetels notify API" msgstr "" -#: ../system/objects.rst:239 ../system/objects.rst:241 -msgid "The color options are currently limited to the mentioned options." +#: ../system/integrations/cti/provider-configurations/placetel.rst:66 +msgid "" +"This menu point also provides a API request log from Placetel view. Just " +"open \"Recent responses of your API endpoint\" to learn more." msgstr "" -#: ../system/objects.rst:243 ../system/objects.rst:245 +#: ../system/integrations/cti/provider-configurations/placetel.rst:69 msgid "" -"You can create a note for the priority to inform other admins about the " -"priority. This has no effect on tickets." +"If you want to see Zammad's perspective, use the \"Recent Logs\" part from " +"within the Placetel integration page." msgstr "" -#: ../system/objects.rst:247 ../system/objects.rst:249 -msgid "Set the priority to *active* or *inactive*." +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "Screenshot showing sample log entries for Placetels API calls to Zammad" msgstr "" -#: ../system/objects/external-data-source-example.rst:2 -msgid "External Data Source" +#: ../system/integrations/cti/provider-configurations/placetel.rst:77 +msgid "Step 4 (optional): Further configurations for Placetel" msgstr "" -#: ../system/objects/external-data-source-example.rst:4 +#: ../system/integrations/cti/provider-configurations/placetel.rst:76 msgid "" -"We assume you already had a look on :doc:`types` where you can find a " -"description of the individual fields." +"If needed, you can now configure Zammad's Placetel integration in more " +"detail. You can learn more about your options here: :ref:`Placetel " +"integration settings `." msgstr "" -#: ../system/objects/external-data-source-example.rst:7 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:2 +msgid "Setup Sipgate connection for Zammad" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"To reproduce this example, choose a category you want to add a custom field, " -"click on *New Attribute* and select *External data source field* under " -"*Format*." +"Sipgate has no english web interface which is why this documentation page is " +"mixing up languages badly." msgstr "" -#: ../system/objects/external-data-source-example.rst:11 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"Our example story is to fetch data from an external product database. We " -"want to add our products to the tickets so that the products can be searched " -"and chosen from a list and also create a link to the product website." +"Please also note that the availability of API addons highly depends on your " +"package trier. Usage of sipgate.io packages *is not free*, please check " +"their `pricing page `_ before!" msgstr "" -#: ../system/objects/external-data-source-example.rst:16 -msgid "Base configuration" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:35 +msgid "Step 1: Book sipgate.io package" msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Initial steps to configure external data source object type" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:13 +msgid "Skip to step 2 if you already have the package booked!" msgstr "" -#: ../system/objects/external-data-source-example.rst:23 -#: ../system/variables.rst:85 -msgid "**Example:**" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:15 +msgid "" +"Login to an administrative Sipgate account and navigate to " +"``Accountverwaltung``. You'll see several different options depending on " +"your booked packages. Select ``Verträge & Produkte`` to continue." msgstr "" -#: ../system/objects/external-data-source-example.rst:25 -msgid "Name: *product*" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:19 +msgid "" +"Scroll down to the section ``Zusätzliche Produkte buchen`` and look for " +"``sipgate.io`` - select this product by using the ``Produkte anzeigen``-" +"Button." msgstr "" -#: ../system/objects/external-data-source-example.rst:26 -msgid "Display: *Product*" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:23 +msgid "" +"On the next page select either one of the ``sipgate.io`` packages or ``Push-" +"API Package Free``. Follow the dialogue by booking the addon. You'll be " +"returned to your contract overview and now should see the selected addon in " +"your list." msgstr "" -#: ../system/objects/external-data-source-example.rst:29 -msgid "External data source configuration" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:30 +msgid "" +"The availability for ``sipgate.io`` packages and their levels highly depends " +"on the overall account type and product you've booked with Sipgate." msgstr "" -#: ../system/objects/external-data-source-example.rst:31 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"First, enter the search URL making sure it contains ``#{search.term}`` as a " -"parameter:" +"Screencast showing the process on how to book the required sipgate.io addon" msgstr "" -#: ../system/objects/external-data-source-example.rst:34 -msgid "**Example:** ``https://dummyjson.com/products/search?q=#{search.term}``" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:52 +msgid "Step 2: Configure webhook for Zammad" msgstr "" -#: ../system/objects/external-data-source-example.rst:36 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:38 msgid "" -"After that, head down to the preview section and enter a search input for " -"the external data source." +"Within your ``Accountverwaltung`` navicate to your product ``sipgate.io``. " +"In the newly opened tab, switch from \"Clients\" to \"Webhooks\" and paste " +"the endpoint URLs from your Zammad instance like so:" msgstr "" -#: ../system/objects/external-data-source-example.rst:39 -msgid "**Example:** ``mac``" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:42 +msgid "Inbound endpoint to \"Incoming\"" msgstr "" -#: ../system/objects/external-data-source-example.rst:41 -msgid "Then you can find a preview of the response data below:" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:43 +msgid "Outbound endpoint to \"Outgoing\"" msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of JSON response based on search term" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:47 +msgid "" +"Ensure to select at least one call group or phoneline within \"Sources\". " +"Other wise Sipgate will not indicate any incoming or outgoing calls to " +"Zammad." msgstr "" -#: ../system/objects/external-data-source-example.rst:48 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"We recommend using the preview to have a look on the structure. There is a " -"top-level element called ``products``. One level below, you can find the " -"attributes ``id`` and ``title``." +"Screencast showing how to add Zammad's endpoint URLs to sipgate.ios webhook " +"configuration" msgstr "" -#: ../system/objects/external-data-source-example.rst:52 -msgid "**Search result response based on search from example:**" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:55 +msgid "" +"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " +"the Webhooks → URLs section of Sipgate you can select which *sources* " +"Sipgate should notify Zammad about in- and outgoing calls." msgstr "" -#: ../system/objects/external-data-source-example.rst:119 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:59 msgid "" -"To tell the remote system that the desired data is located below the " -"``products`` level, you have to put it in the field *Search result list key*." +"Use either specific phone lines or use the option \"Use for all phonelines " +"and groups\" to notify Zammad about all existing lines of your Sipgate " +"account." msgstr "" -#: ../system/objects/external-data-source-example.rst:122 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"After inserting ``products`` in the mentioned field, you get an extended " -"preview. You can find an additional box *Search result list* with a JSON " -"structure. This is the same response as before but stripped from the upper " -"``products`` element by the external data source." +"Screenshot showing a sample selection of phone numbers to use for the " +"Sipgates webhooks API" msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of JSON response search result list" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:68 +msgid "This section also allows you to enable a Debug log." msgstr "" -#: ../system/objects/external-data-source-example.rst:132 -msgid "" -"Now you need to provide the keys for the search result values and labels. As " -"already mentioned, we are looking for the ``id`` and the ``title`` of our " -"products. If you haven't already, it is now a good time to look at the " -"preview of the *Search result list*." +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "Screenshot showing an enabled Debug log option" msgstr "" -#: ../system/objects/external-data-source-example.rst:197 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:73 msgid "" -"After locating our two keys, we insert them in *search result value key* " -"(``id``) and in *Search result label key* (``title``)." +"After enabling you can use the Debug log section to see all sent webhook " +"calls to Zammad. You'll also can see the response." msgstr "" -#: ../system/objects/external-data-source-example.rst:200 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"Basically, we configured the external data source already and we can see a " -"table in the preview section:" +"Screenshot showing sample log entries for Sipgates webhook calls to Zammad" msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of product table based on search term" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:81 +msgid "Step 4 (optional): Further configurations for Sipgate" msgstr "" -#: ../system/objects/external-data-source-example.rst:208 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:80 msgid "" -"According to our example story, now just the *Link template* is missing." +"If needed, you can now configure Zammad's Sipgate integration in more " +"detail. You can learn more about your options here: :ref:`Sipgate " +"integration settings `." msgstr "" -#: ../system/objects/external-data-source-example.rst:210 -msgid "" -"Please note that this is an optional feature. If you don't want to use such " -"links, of course you don't have to configure it." +#: ../system/integrations/cti/sipgate.rst:2 +msgid "Sipgate (sipgate.io)" msgstr "" -#: ../system/objects/external-data-source-example.rst:213 -msgid "" -"We can add now an address where additional product information can be found." +#: ../system/integrations/cti/sipgate.rst:16 +msgid "You need an administrative Sipgate account for your organization." msgstr "" -#: ../system/objects/external-data-source-example.rst:215 -msgid "Example: ``https://your_domain.com/q=#{ticket.product}``" +#: ../system/integrations/cti/sipgate.rst:17 +msgid "" +"Zammad requires a ``sipgate.io`` addon from the feature store (please note " +"that API calls are not free with Sipgate. Rates may apply and differ from " +"account to account)." msgstr "" -#: ../system/objects/external-data-source-example.rst:217 -msgid "In the example, the parameter means:" +#: ../system/integrations/cti/sipgate.rst:21 +msgid "Sipgate must be able to reach your Zammad instance." msgstr "" -#: ../system/objects/external-data-source-example.rst:219 -msgid "``#{}``: \"Frame\" for the insertion of information" +#: ../system/integrations/cti/sipgate.rst:25 +msgid ":doc:`provider-configurations/sipgate`" msgstr "" -#: ../system/objects/external-data-source-example.rst:220 -msgid "``ticket``: object level, where you create your custom object" +#: ../system/integrations/cti/sipgate.rst:24 +msgid "" +"Learn how to configure Sipgate to enable Zammad and Sipgate to communicate " +"with each other." msgstr "" -#: ../system/objects/external-data-source-example.rst:221 -msgid "``product``: name of the (custom) object" +#: ../system/integrations/cti/sipgate.rst:33 +msgid "" +"Below endpoint settings affect the :doc:`sipgate.io configuration `." msgstr "" -#: ../system/objects/external-data-source-example.rst:223 -msgid "" -"After configuring your *Link template*, there will be another column in the " -"preview. Hovering on the icons in the *Link* column will show you where it " -"forwards you." +#: ../system/integrations/cti/sipgate.rst:37 +msgid "This endpoint is required for incoming call hooks." msgstr "" -#: ../system/objects/external-data-source-example.rst:232 -msgid "" -"In our example, one of the links looks like: https://your_domain.com/q=6, " -"where the 6 is the product id." +#: ../system/integrations/cti/sipgate.rst:40 +msgid "This endpoint is required for outgoing call hooks." msgstr "" -#: ../system/objects/external-data-source-example.rst:235 -msgid "You can find more information regarding the URL in :doc:`types`." +#: ../system/integrations/cti/sipgate.rst:0 +msgid "Screenshot showing sample user mappings in between Sipgate and Zammad" msgstr "" -#: ../system/objects/includes/adding-values-hint.include.rst:3 +#: ../system/integrations/cti/sipgate.rst:69 msgid "" -"Adding values can be tricky for first timers, don't forget to press \"➕ " -"Add\" after typing your values. Otherwise you may loose a value." +"You can find your agent's Sipgate username within ``Accountverwaltung → " +"Benutzer``. You're looking for the SIP-ID." msgstr "" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:1 -#: ../system/objects/includes/reposition-values.include.rst:1 -msgid "**↕️ This field type allows the positioning of its values ↔️**" +#: ../system/integrations/cti/sipgate.rst:0 +msgid "Sample VoIP credentials for a Sipgate user" +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:77 +msgid "Users with several devices also have several SIP-IDs." msgstr "" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:3 -msgid "" -"In order to re-arrange the field values, first edit the field. Then you can " -"use ☰ to drag the values in question to the correct position. If you want to " -"change the layer depth, double click on ☰. With it you can cycle through the " -"available layers." +#: ../system/integrations/elasticsearch.rst:2 +msgid "Elasticsearch (SaaS)" msgstr "" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:8 -msgid "When you're ready, submit your changes to save the object attribute." +#: ../system/integrations/elasticsearch.rst:4 +msgid "" +"The Elasticsearch integration allows you to create a read-only user to use " +"with your favorite reporting tool (e.g. like Grafana)." msgstr "" -#: :0 ../system/objects/types.rst:0 +#: ../system/integrations/elasticsearch.rst:7 msgid "" -"Screencast showing how to re-position values on tree select like\n" -"fields" +"If you want to take full advantage of the Zammad reporting, have a look at " +"our :docs:`Grafana ` " +"setup page as well." msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:3 -msgid "" -"In order to re-arrange the field values, edit the field and scroll below the " -"values. Make sure to tick the option \"Use custom option sort\"." +#: ../system/integrations/elasticsearch.rst:11 ../system/subscription.rst:7 +msgid "**🚧 Hosted environment specific 🚧**" msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:8 +#: ../system/integrations/elasticsearch.rst:13 msgid "" -"If you do not tick this field, all manual positioning you did above will be " -"lost upon saving! ☠️" +"This integration is only available for Hosted setups. In order to use " +"Elasticsearch you'll need the **Plus** subscription." msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:11 +#: ../system/integrations/elasticsearch.rst:16 msgid "" -"Now use ☰ to drag the values in question to the correct position. When " -"you're ready, submit your changes to save the object attribute." +"Self hosted users have all the control over their self hosted Elasticsearch " +"instances." msgstr "" -#: :0 ../system/objects/types.rst:0 -msgid "Screencast showing how to re-position values" +#: ../system/integrations/elasticsearch.rst:None +msgid "Elasticsearch integration page on SaaS environments" msgstr "" -#: ../system/objects/includes/url-template-hint.include.rst:3 +#: ../system/integrations/elasticsearch.rst:27 msgid "" -"This field allows using :ref:`URL fields (Link Templates) `." +"Please note the following limitations of Elasticsearch access on hosted " +"environments:" msgstr "" -#: ../system/objects/permissions.rst:2 -msgid "Attribute Permissions" +#: ../system/integrations/elasticsearch.rst:30 +msgid "access to the Elasticsearch index is read-only access" msgstr "" -#: ../system/objects/permissions.rst:7 +#: ../system/integrations/elasticsearch.rst:31 +msgid "currently you're limited to user only" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:32 msgid "" -"In the object attributes configuration you can define if a field is shown " -"and if the input in the field is mandatory, separated by different screens " -"and for different :doc:`roles/permissions `." +"Reporting tools that require to write into the indexes (like Kibana) are not " +"supported" msgstr "" -#: ../system/objects/permissions.rst:17 -msgid "Screenshot shows object attribute permission table" +#: ../system/integrations/elasticsearch.rst:34 +msgid "IP access restriction is currently not yet supported" msgstr "" -#: ../system/objects/permissions.rst:17 -msgid "" -"Some of the possible permissions and screen options for a user object " -"attribute." +#: ../system/integrations/elasticsearch.rst:37 +msgid "Activating Elasticsearch Access" msgstr "" -#: ../system/objects/permissions.rst:19 +#: ../system/integrations/elasticsearch.rst:39 msgid "" -"Based on the object context (ticket, agent, organization, user), the " -"selectable roles (to be precise: the required permissions) and screens " -"differ. Be aware that these settings aren't affecting data creation via " -"other channels than the UI." +"By default external access to your Elasticsearch index is not active. You " +"can enable the integration at any time if needed." msgstr "" -#: ../system/objects/permissions.rst:24 +#: ../system/integrations/elasticsearch.rst:42 msgid "" -"If you want to have further customization possibilities, you should have a " -"look at the :doc:`core workflows `." +"Please ensure to note down the password provided - you won't have access to " +"it afterwards." msgstr "" -#: ../system/objects/permissions.rst:28 -msgid "Screens" +#: ../system/integrations/elasticsearch.rst:None +msgid "Screencast showing activation of Elasticsearch integration" msgstr "" -#: ../system/objects/permissions.rst:30 -msgid "" -"In the table below you can find an overview about the different permissions " -"and the available screens Zammad distinguishes between." +#: ../system/integrations/elasticsearch.rst:51 +msgid "Connection Settings" msgstr "" -#: ../system/objects/permissions.rst:37 -msgid "Screen" +#: ../system/integrations/elasticsearch.rst:53 +msgid "" +"This section holds the most important general information for accessing your " +"Elasticsearch indexes - such as:" msgstr "" -#: ../system/objects/permissions.rst:38 -msgid "Available for" +#: ../system/integrations/elasticsearch.rst:57 +msgid "A unique subdomain that does not tell your real instance URL." msgstr "" -#: ../system/objects/permissions.rst:40 -msgid "create" +#: ../system/integrations/elasticsearch.rst:61 +msgid "Software" msgstr "" -#: ../system/objects/permissions.rst:41 ../system/objects/permissions.rst:52 -#: ../system/objects/permissions.rst:59 ../system/objects/permissions.rst:73 -msgid "admin.user" +#: ../system/integrations/elasticsearch.rst:60 +msgid "" +"The major version of the search index being used. This is required by some " +"Reporting tools like Grafana." msgstr "" -#: ../system/objects/permissions.rst:42 ../system/objects/permissions.rst:53 -#: ../system/objects/permissions.rst:60 -msgid "admin.organization" +#: ../system/integrations/elasticsearch.rst:64 +msgid "Authentication" msgstr "" -#: ../system/objects/permissions.rst:43 ../system/objects/permissions.rst:54 -#: ../system/objects/permissions.rst:61 -msgid "admin.group" +#: ../system/integrations/elasticsearch.rst:64 +msgid "The authentication type being supported. ``Basic Authentication``" msgstr "" -#: ../system/objects/permissions.rst:44 -msgid "Creation dialog for not yet existing data" +#: ../system/integrations/elasticsearch.rst:67 +msgid "Available Indexes" msgstr "" -#: ../system/objects/permissions.rst:45 -msgid "create_middle" +#: ../system/integrations/elasticsearch.rst:69 +msgid "" +"Within this section we're displaying the -in our opinion- most important " +"indexes for a Zammad instance." msgstr "" -#: ../system/objects/permissions.rst:46 ../system/objects/permissions.rst:50 -#: ../system/objects/permissions.rst:57 ../system/objects/permissions.rst:66 -#: ../system/objects/permissions.rst:70 -#, fuzzy -msgid "ticket.customer" -msgstr "Макрос заявки" - -#: ../system/objects/permissions.rst:47 ../system/objects/permissions.rst:51 -#: ../system/objects/permissions.rst:58 ../system/objects/permissions.rst:69 -#, fuzzy -msgid "ticket.agent" -msgstr "Макрос заявки" - -#: ../system/objects/permissions.rst:48 -msgid "Ticket create dialog (middle section)" +#: ../system/integrations/elasticsearch.rst:72 +msgid "" +"If you require all indexes or our listing is not good enough for you, point " +"your browser to the URL we're providing and append ``/_aliases?" +"pretty=true``. The result should look like this: ``https://.zammad.com/" +"_aliases?pretty=true``." msgstr "" -#: ../system/objects/permissions.rst:49 -msgid "edit" +#: ../system/integrations/elasticsearch.rst:77 +msgid "" +"Your browser will automatically ask for your credentials - you'll then see " +"something like this:" msgstr "" -#: ../system/objects/permissions.rst:55 -msgid "Editing dialog for already existing data" +#: ../system/integrations/elasticsearch.rst:125 +msgid "Credentials" msgstr "" -#: ../system/objects/permissions.rst:56 -msgid "view" +#: ../system/integrations/elasticsearch.rst:127 +msgid "" +"Within this section Zammad displays your available users. The password is " +"provided once (upon activation) and cannot be retrieved after that." msgstr "" -#: ../system/objects/permissions.rst:62 -msgid "View-only dialog for already existing data" +#: ../system/integrations/elasticsearch.rst:131 +msgid "" +"If you need to change or reset your Elasticsearch user password, use the " +"\"Reset password\" button in the credentials table. Doing so creates a brand " +"new password for the account in question. This change is immediate, keep in " +"mind that this may affect third party tools connected to your instance." msgstr "" -#: ../system/objects/permissions.rst:64 -msgid "(e.g. user or organization from search)" +#: ../system/integrations/exchange.rst:2 +msgid "Exchange" msgstr "" -#: ../system/objects/permissions.rst:65 -msgid "signup" +#: ../system/integrations/exchange.rst:4 +msgid "" +"With Zammad's Exchange integration, you can easily use existing address " +"books without having to update more than one source." msgstr "" -#: ../system/objects/permissions.rst:67 -msgid "Sign-up screen for new customers" +#: ../system/integrations/exchange.rst:7 +msgid "" +"However, you should refrain from syncing all addresses, as the results may " +"not be what you expect (Exchange collects huge amounts of addresses). A " +"central address book of your company to sync makes more sense, as you can " +"ensure that Zammad gets only the data you need and want. Apart from this, it " +"is even not possible to sync the Global Address List (GAL) of your Exchange " +"system with Zammad." msgstr "" -#: ../system/objects/permissions.rst:68 -msgid "invite_customer" +#: ../system/integrations/exchange.rst:16 +msgid "" +"**Exchange and LDAP:** The exchange sync can be overruled by Zammad's LDAP " +"integration. If you have the same users in both sources, the LDAP version " +"will always be Zammad's pick." msgstr "" -#: ../system/objects/permissions.rst:71 +#: ../system/integrations/exchange.rst:19 msgid "" -"Customer invitation screen (from :doc:`First Steps ` area)" +"**One way sync:** the Exchange sync is one way. Exchange => Zammad. Changes " +"to your users inside of Zammad might be overwritten by the Exchange sync." msgstr "" -#: ../system/objects/permissions.rst:72 -msgid "invite_agent" +#: ../system/integrations/exchange.rst:24 +msgid "" +"To configure Exchange integration, simply go to the System > Integrations > " +"Exchange in the admin panel. Press \"change\" and follow the wizard for " +"adding the needed Exchange information to Zammad. On the last two steps " +"Zammad will ask you for the address book(s) and your desired attribute " +"mapping. By default, Zammad only maps email address, first- and lastname. " +"Technically, you can map any Exchange object to a Zammad user object (this " +"also works for custom objects!)." msgstr "" -#: ../system/objects/permissions.rst:74 +#: ../system/integrations/exchange.rst:35 msgid "" -"Agent invitation screen (from :doc:`First Steps ` area)" +"If the SSL verification fails while connecting to Exchange, Zammad will ask " +"you to turn it off temporarily." msgstr "" -#: ../system/objects/permissions.rst:78 -msgid "Screen Options" +#: ../system/integrations/exchange.rst:38 +msgid "" +"Please be aware that **turning off SSL verification is a security risk**. It " +"should only be used temporarily or for testing purposes. If turned off, " +"there is no verification of the certificate, which means that every " +"presented certificate will be accepted." msgstr "" -#: ../system/objects/permissions.rst:80 +#: ../system/integrations/exchange.rst:43 msgid "" -"For the different screens you can select \"show\" and \"required\" options." +"After pressing Continue, Zammad will check if the configuration is okay. You " +"can then enable Exchange and start your first sync. The sync will then run " +"hourly - if you need to change mappings or the address book(s), you can " +"change the configuration at any time." msgstr "" -#: ../system/objects/permissions.rst:82 -msgid "**shown:** Show (check) or hide (uncheck) a field." +#: ../system/integrations/exchange.rst:50 +msgid "" +"After the sync has finished, you can find the new Exchange contacts under " +"\"Users\". Zammad integrates them just as normal users." msgstr "" -#: ../system/objects/permissions.rst:83 +#: ../system/integrations/exchange.rst:55 msgid "" -"**required:** Set a field to mandatory (check). Forces users (via UI and " -"API) to populate the field." +"In some cases you might see unique IDs as \"Login\" instead of the email " +"address. This is normal and doesn't affect the login or email mapping for " +"that entry." msgstr "" -#: ../system/objects/types.rst:7 -msgid "Example external data source" +#: ../system/integrations/github.rst:4 +msgid "" +"Use GitHub integration to track GitHub issues directly within Zammad " +"tickets. Add issue hyperlinks and get a live summary of metadata like status " +"(open/closed), assignee, labels, and more." msgstr "" -#: ../system/objects/types.rst:2 -msgid "Attribute types" +#: ../system/integrations/github.rst:8 +msgid "Please note that our GitHub integration does not support pull requests." msgstr "" -#: ../system/objects/types.rst:4 -msgid "" -"When adding a new object attribute, you can choose between the following " -"attribute types." +#: ../system/integrations/github.rst:None +msgid "Integration page for GitHub" msgstr "" -#: ../system/objects/types.rst:14 +#: ../system/integrations/github.rst:18 msgid "" -"You cannot change the attribute format / type as soon as it is applied. If " -"you no longer need an object attribute, consider disabling it instead of " -"removing." +"In your GitHub settings, create a new API token under **Developer settings > " +"Personal access tokens > Generate new token**. Leave the **Scopes** section " +"empty." msgstr "" -#: ../system/objects/types.rst:18 -msgid "**What about the translation of my attributes?**" +#: ../system/integrations/github.rst:0 ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to create a new API token" msgstr "" -#: ../system/objects/types.rst:20 -msgid "" -"For some attribute types you can decide if they should be translatable or " -"not. To be precise, it works only for the selectable fields because the " -"possible choices are known and limited. For the following attribute types, " -"you can set the translatable flag:" +#: ../system/integrations/github.rst:27 +msgid "Create a new API key with no scopes/privileges." msgstr "" -#: ../system/objects/types.rst:25 -msgid "*Boolean field*" +#: ../system/integrations/github.rst:29 +msgid "🔒 **Will this work for private repos?**" msgstr "" -#: ../system/objects/types.rst:26 -msgid "*Single selection field*" +#: ../system/integrations/github.rst:31 +msgid "" +"No. To link private repo issues, **use the** ``repo`` **scope instead**. " +"Bear in mind that the resulting token will have `lots of permissions that it " +"doesn't actually need `_, which presents a security risk if your token ever falls into " +"the wrong hands." msgstr "" -#: ../system/objects/types.rst:27 -msgid "*Multiple selection field*" +#: ../system/integrations/github.rst:37 +msgid "" +"Unfortunately, because of how GitHub's OAuth token scopes are set up, this " +"is the only way to link issues on private repos." msgstr "" -#: ../system/objects/types.rst:28 -msgid "*Single tree selection field*" +#: ../system/integrations/github.rst:40 +msgid "Enter your new API token in Zammad and enable GitHub integration." msgstr "" -#: ../system/objects/types.rst:29 -msgid "*Multiple tree selection field*" +#: ../system/integrations/github.rst:0 +msgid "Screencast showing how to configure Zammad's GitHub integration" msgstr "" -#: ../system/objects/types.rst:31 +#: ../system/integrations/github.rst:47 msgid "" -"For these types, you can find an additional field *Translate field contents*:" +"Use the default API endpoint (``https://api.github.com/graphql``) unless " +"you're using GitHub Enterprise Server." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Screenshot showing translatable attribute types" +#: ../system/integrations/github.rst:50 +msgid "" +"Once completed, a new GitHub issues tab will appear in the ticket pane. 🎉" msgstr "" -#: ../system/objects/types.rst:38 -msgid "Screenshot with example of translatable attribute type" +#: ../system/integrations/github.rst:59 ../system/integrations/gitlab.rst:52 +msgid "Token verification is taking a long time" msgstr "" -#: ../system/objects/types.rst:45 -msgid "Boolean field" +#: ../system/integrations/github.rst:56 ../system/integrations/gitlab.rst:49 +msgid "" +"Slight delays are normal (<2 min.), especially for systems under heavy load." msgstr "" -#: ../system/objects/types.rst:41 +#: ../system/integrations/github.rst:58 msgid "" -"Provides a drop-down field with display values for ``true`` and ``false``. " -"Setting a default is mandatory." +"Self-hosted administrators, please check your network settings to ensure " +"that your Zammad server can reach ``api.github.com``." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Boolean fields" +#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 +msgid "I reloaded the page and now the API token is gone" msgstr "" -#: ../system/objects/types.rst:55 -msgid "Date field" +#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 +msgid "" +"This may indicate that Zammad is still verifying your API token. Try " +"reloading the page again in a couple minutes." msgstr "" -#: ../system/objects/types.rst:48 -msgid "Provides a date picker field and does not allow default values." +#: ../system/integrations/gitlab.rst:2 +msgid "GitLab" msgstr "" -#: ../system/objects/types.rst:52 -msgid "Default time diff (hours)" +#: ../system/integrations/gitlab.rst:4 +msgid "" +"Use GitLab integration to track GitLab issues directly within Zammad " +"tickets. Add issue hyperlinks and get a live summary of metadata like status " +"(open/closed), assignee, labels, and more." msgstr "" -#: ../system/objects/types.rst:51 +#: ../system/integrations/gitlab.rst:8 msgid "" -"This setting helps the user by highlighting the day from now plus the " -"provided value. It *does not* pre-fill the field." +"Please note that our GitLab integration does not support merge requests." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Date fields" +#: ../system/integrations/gitlab.rst:None +msgid "Integration page for GitLab" msgstr "" -#: ../system/objects/types.rst:73 -msgid "Date & time field" +#: ../system/integrations/gitlab.rst:18 +msgid "" +"In your GitLab preferences, create a new API token under **Access Tokens**." msgstr "" -#: ../system/objects/types.rst:58 -msgid "Provides a date and time picker – does not allow default values" +#: ../system/integrations/gitlab.rst:20 +msgid "Under **Select scopes**, choose ``read_api`` only." msgstr "" -#: ../system/objects/types.rst:62 -msgid "Allow future" +#: ../system/integrations/gitlab.rst:27 +msgid "🔒 **If you wish to link issues on any private repos...**" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Forbid dates and times in the future." +#: ../system/integrations/gitlab.rst:29 +msgid "Your API token must belong to an account with access to those repos." msgstr "" -#: ../system/objects/types.rst:66 -msgid "Allow past" +#: ../system/integrations/gitlab.rst:31 +msgid "Enter your new API token in Zammad and enable GitLab integration." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Forbid dates and times in the past." +#: ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to configure Zammad's GitLab integration" msgstr "" -#: ../system/objects/types.rst:70 -msgid "Default time diff (minutes)" +#: ../system/integrations/gitlab.rst:40 +msgid "" +"Use the default API endpoint (``https://gitlab.com/api/graphql``) unless " +"you're a self-hosted GitLab user." msgstr "" -#: ../system/objects/types.rst:69 +#: ../system/integrations/gitlab.rst:43 msgid "" -"This setting helps the user by highlighting the day from now plus the " -"provided value. It does not pre-fill the field." +"Once completed, a new GitLab issues tab will appear in the ticket pane. 🎉" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Date & time fields" +#: ../system/integrations/gitlab.rst:51 +msgid "" +"Self-hosted administrators, please check your network settings to ensure " +"that your Zammad server can reach ``gitlab.com``." msgstr "" -#: ../system/objects/types.rst:86 -msgid "Integer field" +#: ../system/integrations/i-doit.rst:2 +msgid "i-doit" msgstr "" -#: ../system/objects/types.rst:76 +#: ../system/integrations/i-doit.rst:4 msgid "" -"Provides an input field that allows integer usage only. You may define a " -"default value. You cannot enforce comma separation." -msgstr "" - -#: ../system/objects/types.rst:80 -msgid "Minimal" +"`i-doit `_ is an open-source **configuration " +"management database** - in other words, a tool for keeping tabs on every " +"single piece of your physical and digital infrastructure, from network " +"equipment to virtual machines on down to the faceplates on your rack shelves " +"and more." msgstr "" -#: ../system/objects/types.rst:80 -msgid "The minimal value the field accepts." +#: ../system/integrations/i-doit.rst:10 +msgid "" +"What's that got to do with Zammad? Well, if you used tickets to track issues " +"with all that hardware, you might start wishing there was a way they could " +"talk to each other." msgstr "" -#: ../system/objects/types.rst:83 -msgid "Maximal" +#: ../system/integrations/i-doit.rst:14 +msgid "Zammad gives you two:" msgstr "" -#: ../system/objects/types.rst:83 -msgid "The maximum value the field accepts." +#: ../system/integrations/i-doit.rst:17 +msgid "1. Add i-doit Links to Zammad Tickets" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Integer fields" +#: ../system/integrations/i-doit.rst:20 ../system/integrations/i-doit.rst:80 +msgid "What Users See" msgstr "" -#: ../system/objects/types.rst:99 -msgid "Multiple selection field" +#: ../system/integrations/i-doit.rst:26 +msgid "i-doit integration in Zammad's ticket pane" msgstr "" -#: ../system/objects/types.rst:89 +#: ../system/integrations/i-doit.rst:26 msgid "" -"Provides a selection field that allows the selection of one or more out of " -"several. This field does allow setting a default value." +"The i-doit integration will appear under a new 🖨 tab in the ticket pane." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Multiple selection fields" +#: ../system/integrations/i-doit.rst:28 +msgid "" +"i-doit integration puts a new tab in Zammad's ticket pane where you can add " +"links to existing i-doit devices for easy reference. (See our :user-docs:" +"`user documentation ` to learn " +"how it works in practice)." msgstr "" -#: ../system/objects/types.rst:112 -msgid "Single selection field" +#: ../system/integrations/i-doit.rst:36 ../system/integrations/i-doit.rst:93 +msgid "How to Set it Up" msgstr "" -#: ../system/objects/types.rst:102 +#: ../system/integrations/i-doit.rst:38 msgid "" -"Provides a drop-down field that allows selection of one value out of " -"several. This field does allow setting a default value." -msgstr "" - -#: ../system/objects/types.rst:0 -msgid "Available settings for Single selection fields" +"It requires i-doit's `API Add-on `_. Make sure to have it properly set up. Use the following setting:" msgstr "" -#: ../system/objects/types.rst:142 -msgid "Textarea field" +#: ../system/integrations/i-doit.rst:42 +msgid "Active: ``Yes``" msgstr "" -#: ../system/objects/types.rst:115 -msgid "" -"Provides a text area input field (multiple lines) and thus allows e.g. new " -"lines. You can set a default field value." +#: ../system/integrations/i-doit.rst:43 +msgid "Enforce authentication by username and password: ``No``" msgstr "" -#: ../system/objects/types.rst:120 +#: ../system/integrations/i-doit.rst:45 msgid "" -"Please note that this field *does not* support text formatting or HTML " -"content (rich text)." +"To set it up, enable the integration in the Zammad admin panel under " +"**System > Integrations > i-doit**:" msgstr "" -#: ../system/objects/types.rst:123 -msgid "**🥵 This field can consume a lot of visual space**" +#: ../system/integrations/i-doit.rst:None +msgid "i-doit settings within the integration pages" msgstr "" -#: ../system/objects/types.rst:125 -msgid "" -"Depending on where you use this field type, it may use a lot of visual space " -"if you provide a lot of text. This may be an issue to work with." +#: ../system/integrations/i-doit.rst:53 +msgid "The root URL of your i-doit installation." msgstr "" -#: ../system/objects/types.rst:130 -msgid "Default" +#: ../system/integrations/i-doit.rst:62 +msgid "API token" msgstr "" -#: ../system/objects/types.rst:129 +#: ../system/integrations/i-doit.rst:56 msgid "" -"The here provided text will be shown within the text area field or new data " -"sets." +"Found in the i-doit admin panel under **Interfaces / external data > JSON-" +"RPC API > Common Settings**." msgstr "" -#: ../system/objects/types.rst:134 ../system/objects/types.rst:160 -msgid "Maxlength" +#: ../system/integrations/i-doit.rst:0 +msgid "i-doit administration interface with API configuration" msgstr "" -#: ../system/objects/types.rst:0 ../system/objects/types.rst:160 -msgid "You can pick the maximum length of the field." +#: ../system/integrations/i-doit.rst:67 +msgid "Client ID" msgstr "" -#: ../system/objects/types.rst:0 -msgid "The default length of this object is ``500``." +#: ../system/integrations/i-doit.rst:65 +msgid "A unique name to identify Zammad within i-doit." msgstr "" -#: ../system/objects/types.rst:139 -msgid "Rows" +#: ../system/integrations/i-doit.rst:67 +msgid "(Zammad does not require you to enter a value here, but i-doit might!)" msgstr "" -#: ../system/objects/types.rst:0 +#: ../system/integrations/i-doit.rst:70 msgid "" -"Change the number of rows to dislay so that you can use only the space you " -"really need." -msgstr "" - -#: ../system/objects/types.rst:0 -msgid "The default number of rows is ``4``." +"Here you can decide if the certificate of your i-doit system has to be " +"verified or not. In case you are using custom certificates, please have a " +"look at :doc:`how to add them to Zammad `." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Textarea fields" +#: ../system/integrations/i-doit.rst:77 +msgid "2. List / Create Zammad Tickets in i-doit" msgstr "" -#: ../system/objects/types.rst:165 -msgid "Text field" +#: ../system/integrations/i-doit.rst:None +msgid "Zammad integration in i-doit's device view" msgstr "" -#: ../system/objects/types.rst:145 -msgid "Provides a text field (one line) and allows choosing a default value." +#: ../system/integrations/i-doit.rst:86 +msgid "" +"i-doit's ticket system integration gives you a way to see all the tickets " +"for a given device without ever leaving i-doit. (See our :user-docs:`user " +"documentation ` to learn how it " +"works in practice)." msgstr "" -#: ../system/objects/types.rst:148 +#: ../system/integrations/i-doit.rst:95 msgid "" -"Defines the type of the input field. This allows e.g. your browser to ensure " -"that you provide the specific type." +"Enable this integration in the i-doit admin panel under **Interfaces / " +"external data > Trouble Ticket System (TTS) > Configuration**:" msgstr "" -#: ../system/objects/types.rst:152 -msgid "Currently available:" +#: ../system/integrations/i-doit.rst:None +msgid "i-doit administration interface with TTS configuration" msgstr "" -#: ../system/objects/types.rst:155 -msgid "Phone" +#: ../system/integrations/i-doit.rst:104 +msgid "TTS-Type" msgstr "" -#: ../system/objects/types.rst:156 -msgid "Text" -msgstr "Текст" - -#: ../system/objects/types.rst:157 -msgid "Url *(URL fields disable link-template availability)*" +#: ../system/integrations/i-doit.rst:104 +msgid "``Zammad``" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Text fields" +#: ../system/integrations/i-doit.rst:115 +msgid "Username / Password" msgstr "" -#: ../system/objects/types.rst:174 -msgid "Single tree selection field" +#: ../system/integrations/i-doit.rst:107 +msgid "Login credentials for a Zammad agent." msgstr "" -#: ../system/objects/types.rst:168 +#: ../system/integrations/i-doit.rst:109 msgid "" -"Provides a select-like field with up to 6 layers of options. Does not allow " -"setting a default value." +"This agent must have **read permission** for all :doc:`groups ` that plan on using the i-doit integration." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Tree Select fields" +#: ../system/integrations/i-doit.rst:113 +msgid "" +"You may even wish to create a dedicated agent account just for this " +"integration (otherwise, if the agent ever changes her password, you will " +"have to remember to update it here)." msgstr "" -#: ../system/objects/types.rst:183 -msgid "Multiple tree selection field" +#: ../system/integrations/i-doit.rst:117 +msgid "URL incl. protocol" msgstr "" -#: ../system/objects/types.rst:177 -msgid "" -"Provides a select-like field with up to 6 layers of options allowing the " -"selection of multiple values. Does not allow setting a default value." +#: ../system/integrations/i-doit.rst:118 +msgid "``https://your.zammad.domain``" msgstr "" -#: ../system/objects/types.rst:302 -msgid "External Data Source field" +#: ../system/integrations/index.rst:2 +msgid "Integrations" msgstr "" -#: ../system/objects/types.rst:186 +#: ../system/integrations/index.rst:4 msgid "" -"Provides a searchable field which fetches data from an external system. This " -"can be useful if you have data outside of Zammad and don't want to maintain " -"both data sources." +"Zammad offers numerous integrations that add rich features to your instance." msgstr "" -#: ../system/objects/types.rst:190 -msgid "The feature works as follows:" +#: ../system/integrations/index.rst:6 +msgid "We're still working on this part of our documentation, stay tight!" msgstr "" -#: ../system/objects/types.rst:192 -msgid "" -"Zammad sends a query with a search string (free text from agent or based on " -"a variable) in a pre-defined format (\"Search URL\") to an external system." +#: ../system/integrations/index.rst:10 +msgid "Integrations for Phone Systems" msgstr "" -#: ../system/objects/types.rst:195 +#: ../system/integrations/index.rst:14 msgid "" -"This external system searches for matches and provides a response as a JSON " -"structure to Zammad." +"Your VoIP provider or telephony system is not listed? Possibly your provider " +"supports Zammad by using the generic CTI - if you're unsure ask your " +"provider." msgstr "" -#: ../system/objects/types.rst:197 +#: ../system/integrations/index.rst:18 msgid "" -"Zammad just looks for the defined list and value keys, reads the content and " -"displays the value to the user. There is no search on Zammad side." +"Provider does not support Zammad? Consider creating a `feature request in " +"the Zammad Community `_." msgstr "" -#: ../system/objects/types.rst:201 -msgid "" -"The usage of a PostgreSQL database for Zammad is required. In any other " -"case, Zammad will hide the external data source type and you are not able to " -"use it. If you want to use this feature, consider to :docs:`migrate your " -"database `." +#: ../system/integrations/index.rst:31 +msgid "Integrations for Authentication and Customers" msgstr "" -#: ../system/objects/types.rst:205 -msgid "Currently, only ``GET`` is supported as request method." +#: ../system/integrations/index.rst:44 +msgid "Integrations for Monitoring Systems" msgstr "" -#: ../system/objects/types.rst:206 -msgid "" -"The data structure must be in JSON format and provide the objects in an " -"array." +#: ../system/integrations/index.rst:46 +msgid "This section currently misses the following integrations:" msgstr "" -#: ../system/objects/types.rst:208 -msgid "" -"The endpoint for the external data source has to support search. On Zammad " -"side, there is no search/logic implemented; however, you can define the " -"output key and value based on the result(s) from the response (which " -"provides already filtered content based on the search)." +#: ../system/integrations/index.rst:48 +msgid "Icinga" msgstr "" -#: ../system/objects/types.rst:212 -msgid "" -"If you receive more results as expected, your external data source search " -"may not work properly or the structure of the URL is not correct. You should " -"get in touch with a responsible person from the external system." +#: ../system/integrations/index.rst:49 +msgid "Monit" msgstr "" -#: ../system/objects/types.rst:217 -msgid "" -"Please have a look :doc:`at our example `, where you can find a possible configuration for a public " -"dummy endpoint." +#: ../system/integrations/index.rst:50 +msgid "Nagios" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for external data source fields" +#: ../system/integrations/index.rst:60 +msgid "Integrations for Issue Trackers" msgstr "" -#: ../system/objects/types.rst:242 -msgid "Search URL" +#: ../system/integrations/index.rst:70 +msgid "Other Integrations" msgstr "" -#: ../system/objects/types.rst:227 +#: ../system/integrations/index.rst:72 msgid "" -"Set your endpoint where Zammad fetches the data. Please make sure to include " -"a valid search :doc:`variable <../variables>` as an URL parameter. Example " -"for a free text search at user input: ``#{search.term}``" +"This section will hold any other integration that can't be grouped up (yet)." msgstr "" -#: ../system/objects/types.rst:232 -msgid "" -"If in doubt, ask the responsible person for the external data source how " -"they expect the strucuture of the URL." +#: ../system/integrations/ldap/index.rst:2 +msgid "LDAP / Active Directory" msgstr "" -#: ../system/objects/types.rst:236 +#: ../system/integrations/ldap/index.rst:4 msgid "" -"Depending on your search variable, the preview might work or not. The reason " -"is that the context might not be available and it is no bug." +"Zammad comes with a powerful LDAP integration that allows you to have a " +"single source of truth. By this you reduce the number of login credentials " +"your user has to remember." msgstr "" -#: ../system/objects/types.rst:239 +#: ../system/integrations/ldap/index.rst:10 msgid "" -"Please also make sure to use a variable which is available in your object " -"context. For example you won't be able to search for a ticket in a user " -"object context." -msgstr "" - -#: ../system/objects/types.rst:252 -msgid "SSL Verification" -msgstr "" - -#: ../system/objects/types.rst:245 -msgid "Here you can switch the SSL verification to no." +"The LDAP source is also a perfect candidate for Zammad's :docs:`Kerberos " +"Single Sign-On ` but also works as addition " +"to other :doc:`/settings/security/third-party`." msgstr "" -#: ../system/objects/types.rst:249 -msgid "" -"If your external data source system is using self signed certificates, " -"please have a look :doc:`here ` for " -"further information about how to handle them in Zammad, so you can keep the " -"SSL verification activated." +#: ../system/integrations/ldap/index.rst:None +msgid "Zammands LDAP management page" msgstr "" -#: ../system/objects/types.rst:258 -msgid "HTTP Authentication" +#: ../system/integrations/ldap/index.rst:25 +msgid "📝 :doc:`manage`" msgstr "" -#: ../system/objects/types.rst:255 -msgid "" -"If your external data source requires an authentication, you can set it " -"here. You can leave it empty or choose between *Basic Authentication* or " -"*Authentication Token* (selecting one of the two methods leads to additional " -"fields where you can enter your credentials/token)." +#: ../system/integrations/ldap/index.rst:25 +msgid "Add, modify, remove or re-arrange your LDAP-Sources as needed." msgstr "" -#: ../system/objects/types.rst:265 -msgid "Search result list key" +#: ../system/integrations/ldap/index.rst:30 +msgid "Before you continue, please note the following limitations." msgstr "" -#: ../system/objects/types.rst:261 -msgid "" -"Defines the level in the JSON structure which provides the list with search " -"results. You can leave it empty, if the data is already provided as an " -"array. If you have to go deeper in the structure, you can provide a path " -"with ``.`` as separators, e.g. ``key.subkey.sub-sub-key``." +#: ../system/integrations/ldap/index.rst:32 +msgid "Mapping / Synchronizing organizations is not possible" msgstr "" -#: ../system/objects/types.rst:271 -msgid "Search result value key" +#: ../system/integrations/ldap/index.rst:36 +msgid "" +"You may want to consider using domain based assignments to overcome this " +"issue. Learn more on :doc:`/manage/organizations/index`." msgstr "" -#: ../system/objects/types.rst:268 +#: ../system/integrations/ldap/index.rst:39 msgid "" -"Defines the attribute in the structure in which your external data source " -"provides the *value* for your data. An example would be a product *number*. " -"If you have to go deeper in the structure, you can provide a path with ``.`` " -"as separators, e.g. ``key.subkey.sub-sub-key``." +"Zammad's LDAP sync is one way. Editing user settings or permissions may be " +"overwritten upon the next sync depending on your configuration." msgstr "" -#: ../system/objects/types.rst:277 -msgid "Search result label key" +#: ../system/integrations/ldap/index.rst:41 +msgid "Nested groups are not supported." msgstr "" -#: ../system/objects/types.rst:274 -msgid "" -"Defines the attribute in the structure in which your external data source " -"provides the *label* for your data. An example would be a product *name*. If " -"you have to go deeper in the structure, you can provide a path with ``.`` as " -"separators, e.g. ``key.subkey.sub-sub-key``." +#: ../system/integrations/ldap/index.rst:42 +msgid "Synchronizing user avatars from LDAP is not supported." msgstr "" -#: ../system/objects/types.rst:280 -msgid "" -"In the preview area, you can find the following items (depending on your " -"configuration above):" +#: ../system/integrations/ldap/index.rst:43 +msgid "Unlike user filters, group filters cannot be changed." msgstr "" -#: ../system/objects/types.rst:283 +#: ../system/integrations/ldap/index.rst:44 msgid "" -"**Error/hint message** (only if configuration is not complete): Zammad tells " -"you, if there is a problem and what you should change in your configuration." +"When a user originates from an LDAP server, Zammad will try to verify the " +"login credentials against LDAP first - if this fails Zammad will check its " +"local database." msgstr "" -#: ../system/objects/types.rst:286 +#: ../system/integrations/ldap/index.rst:50 msgid "" -"**Search field**: search for an existing attribute in the data source to get " -"a preview. This is required for the fields below to show up." +"Users can have local passwords even if they're LDAP users! You can learn " +"more about user accounts in general on :doc:`/manage/users/index`." msgstr "" -#: ../system/objects/types.rst:288 +#: ../system/integrations/ldap/index.rst:54 msgid "" -"**Search result response** (only if configuration is not complete): here you " -"can find a syntax highlighted JSON preview of the response, based on the " -"search term you entered." +"When several LDAP sources contain the same user (meaning the same email " +"address), the user in question will be updated with every source configured. " +"*The last LDAP source will win.*" msgstr "" -#: ../system/objects/types.rst:291 +#: ../system/integrations/ldap/index.rst:58 msgid "" -"**Search result list** (only if *search result list key* is properly set): " -"output of the structure under the configured *search result list key*." +"This is subject to change with `Issue 4109 `_ in the future." msgstr "" -#: ../system/objects/types.rst:294 +#: ../system/integrations/ldap/index.rst:60 msgid "" -"**Preview table** (when fully configured): Zammad shows you a table which " -"includes the found items based on the search string (value, label and " -"optional link). You can use this preview if you don't have the complete data " -"structure of the external system in mind." +"Synchronization statistics currently affect *all* configured LDAP sources. " +"This also applies for newly added or updated sources." msgstr "" -#: ../system/objects/types.rst:299 +#: ../system/integrations/ldap/index.rst:63 msgid "" -"An example of a configured external data source field from agent perspective:" +"This is subject to change with `Issue 4108 `_ in the future." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Screencast showing the search for a product in a ticket" +#: ../system/integrations/ldap/index.rst:65 +msgid "" +"Zammad currently has limited fallback server support. You can workaround " +"this by providing several sources - however, ensure to have the exact same " +"configuration on your fallback." msgstr "" -#: ../system/objects/types.rst:307 -msgid "URL fields (Link-Template)" +#: ../system/integrations/ldap/index.rst:69 +msgid "" +"This is subject to improve with `Issue 4107 `_ in the future." msgstr "" -#: ../system/objects/types.rst:311 +#: ../system/integrations/ldap/index.rst:76 msgid "" -"This function is restricted to Text, Select and External data source types " -"only." +"This section holds all requests Zammad handled for all LDAP sources. These " +"entries can either contain synchronization information or logins " +"(authentication attempts via Zammad's login interface)." msgstr "" -#: ../system/objects/types.rst:314 +#: ../system/integrations/ldap/index.rst:80 msgid "" -"Link-Templates are an amazing way to dynamically generate URLs. They allow " -"you to integrate other systems better without having to manually copy data " -"from Zammad if possible." +"By clicking on any request, Zammad will provide even more information. The " +"provided information can be useful when something does not work as expected." msgstr "" -#: ../system/objects/types.rst:320 +#: ../system/integrations/ldap/index.rst:85 msgid "" -"Another great way of communicating with another system may be Zammad's :doc:" -"`Webhooks `." +"Especially a LDAP synchronization can cause many log entries. The web " +"interface will always limit the number of shown entries to the last 50 " +"entries." msgstr "" -#: ../system/objects/types.rst:323 +#: ../system/integrations/ldap/index.rst:None msgid "" -"After filling a link-template enabled field, an URL icon will appear on its " -"right. Clicking on the icon opens a new tab." +"Screencast showing LDAP integration log entries and a detail view on\n" +"an entry." msgstr "" -#: ../system/objects/types.rst:328 -msgid "" -"Even though Zammad displays the link template within object edit and create " -"screens, the function is optional. It's only active if you populate the " -"field." +#: ../system/integrations/ldap/manage.rst:2 +msgid "Manage LDAP-Sources" msgstr "" -#: ../system/objects/types.rst:333 +#: ../system/integrations/ldap/manage.rst:6 msgid "" -"What's the difference between URL and text fields with link template...?!" +"Please keep in mind all current limitations for the LDAP synchronization. " +"This will help to understand scopes of the following operations better." msgstr "" -#: ../system/objects/types.rst:335 -msgid "" -"Both fields have different use cases. Use ``text`` type text fields when " -"ever you have a *static* url that requires dynamic parameters. If you " -"require a drag & drop like field that you can put in any URL, use ``URL`` " -"type text fields." +#: ../system/integrations/ldap/manage.rst:65 +msgid "Add new source" msgstr "" -#: ../system/objects/types.rst:340 +#: ../system/integrations/ldap/manage.rst:10 msgid "" -"The difference is easier to spot when comparing the fields directly, below " -"screencast shows the result - the dynamic approach uses existing values in " -"the moment of updating to built the URL - e.g. ``https://google.com/search?" -"q=cookies`` - while the URL approach uses the actual URL of the field - e.g. " -"``https://zammad.com``." +"Using the *New Source* button allows you to add new LDAP sources to your " +"installation. You're not limited in the number of sources, however, keep in " +"mind that many sources will also take more time to synchronize." msgstr "" -#: ../system/objects/types.rst:None +#: ../system/integrations/ldap/manage.rst:14 msgid "" -"Screencast showing the differents in between URL and text type fields with " -"actual values" +"You can choose between different encryption types, namely *SSL* and " +"*STARTTLS* or none of them (\"*No SSL*\"). If you choose *SSL* or " +"*STARTTLS*, Zammad will display an additional *SSL verification* option that " +"allows you to disable the verification, e.g. for self-signed SSL " +"certificates. You can also tell Zammad to use a different port by appending " +"``:`` to your hostname/IP." msgstr "" -#: ../system/objects/types.rst:352 -msgid "How does this work...?!" +#: ../system/integrations/ldap/manage.rst:0 +msgid "" +"Screenshot of configuring a new LDAP source with SSL encryption and SSL " +"verification" msgstr "" -#: ../system/objects/types.rst:354 +#: ../system/integrations/ldap/manage.rst:26 msgid "" -"As an example, let's say you have an attribute called ``amazing_attribute`` " -"and you want to open a google search directly with the input from that field." +"New Source with SSL transport security enabled and certificate verification" msgstr "" -#: ../system/objects/types.rst:357 +#: ../system/integrations/ldap/manage.rst:30 msgid "" -"Providing the link-template field below allows you to do so: ``https://www." -"google.com/search?q=#{ticket.amazing_attribute}``" +"Using an user filter can be a good idea if you only require a small subset " +"of your LDAP users in Zammad." msgstr "" -#: ../system/objects/types.rst:362 -msgid "" -"You can use any :doc:`Zammad variable ` as long as it's " -"available in the moment you need it." +#: ../system/integrations/ldap/manage.rst:42 +msgid "This especially affects inactive users" msgstr "" -#: ../system/objects/types.rst:365 +#: ../system/integrations/ldap/manage.rst:34 msgid "" -"As a result, you are redirected to Google with a search for the value of the " -"attribute, if you click on the button in the ticket (as you can see in the " -"screencast above)." +"As every LDAP behaves differently on which attributes and how they are set, " +"Zammad doesn't care about any flags." msgstr "" -#: ../system/packages.rst:2 -msgid "Packages" +#: ../system/integrations/ldap/manage.rst:37 +msgid "" +"Users that no longer are returned by your LDAP source will automatically be " +"set to inactive. Zammad assumes that the user was deactivated." msgstr "" -#: ../system/packages.rst:4 -msgid "That's the package management-area." +#: ../system/integrations/ldap/manage.rst:41 +msgid "" +"Users will never be removed automatically! If you want to remove obsolete " +"users, use :doc:`/system/data-privacy`." msgstr "" -#: ../system/packages.rst:6 -msgid "Individual add-ons for Zammad can be installed and managed here." +#: ../system/integrations/ldap/manage.rst:46 +msgid "Active Directory admins" msgstr "" -#: ../system/sessions.rst:2 -msgid "Sessions" +#: ../system/integrations/ldap/manage.rst:45 +msgid "" +"Active Directories are quite specific on how to filter for active users only " +"- please see the `Microsoft documentation `_ for more " +"information." msgstr "" -#: ../system/sessions.rst:4 +#: ../system/integrations/ldap/manage.rst:51 msgid "" -"Sessions management allows reviewing currently known user sessions and " -"allows to end these. The session timeout is affected by :ref:" -"`security_session_timeout` configurations from security settings." +"*Do not* manually write pathes of either LDAP attributes or groups. If " +"Zammad does not display them, it either cannot find them or you have a lot " +"of users that don't have the attributes populated." msgstr "" -#: ../system/sessions.rst:None -msgid "Screenshot showing Zammad's session management" +#: ../system/integrations/ldap/manage.rst:55 +msgid "" +"Zammad will always only return attributes that are filled - this reduces the " +"returned list of attributes greatly." msgstr "" -#: ../system/sessions.rst:13 -msgid "Zammad will provide the following information:" +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing how to add a new LDAP source" msgstr "" -#: ../system/sessions.rst:16 +#: ../system/integrations/ldap/manage.rst:63 msgid "" -"The user account this session entry belongs to. It can be normal if a user " -"has several sessions in the list. This can be due to changed browser " -"information or if you use e.g. single sign on methods where the user does " -"not use the log off button." +"If your LDAP system doesn't allow anonymous bind, Zammad detects it and " +"provides you an editable \"Base DN\" *text* field instead of a prefilled " +"*select* field." msgstr "" -#: ../system/sessions.rst:22 -msgid "Browser" +#: ../system/integrations/ldap/manage.rst:81 +msgid "Review or edit existing source" msgstr "" -#: ../system/sessions.rst:22 -msgid "The browser agent communicated to Zammad." +#: ../system/integrations/ldap/manage.rst:68 +msgid "" +"Clicking on a LDAP source will provide a configuration and mapping overview." msgstr "" -#: ../system/sessions.rst:40 -msgid "Location" +#: ../system/integrations/ldap/manage.rst:70 +msgid "" +"If needed you can then use the *Change* button to update either the name, " +"active state or the whole configuration. If you're changing the whole " +"configuration, the dialogue will be identical to the source creation." msgstr "" -#: ../system/sessions.rst:25 +#: ../system/integrations/ldap/manage.rst:76 msgid "" -"The anticipated location based on the users IP address. Depending on the IP " -"address the result shown may differ. This option depends on :doc:`/settings/" -"system/services`." +"Did your LDAP server change? Different LDAP servers have different " +"structures and default attributes. This causes the LDAP synchronization to " +"likely fail. Consider removing the affected source and re-add it." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing the update of the source name." msgstr "" -#: ../system/sessions.rst:29 -msgid "The following information can be shown:" +#: ../system/integrations/ldap/manage.rst:89 +msgid "Re-arrange LDAP source's order" msgstr "" -#: ../system/sessions.rst:33 -msgid "IP address" +#: ../system/integrations/ldap/manage.rst:84 +msgid "" +"You can change the synchronization order for each source at any time. Zammad " +"will synchronize the sources from top to bottom." msgstr "" -#: ../system/sessions.rst:32 +#: ../system/integrations/ldap/manage.rst:0 msgid "" -"Either if you set *Geo IP services* to inactive or you're using internal IP " -"address which do not provide location information." +"Screencasting showing how to change the source order by using\n" +"drag and drop." msgstr "" -#: ../system/sessions.rst:40 -msgid "Country (or Country + City)" +#: ../system/integrations/ldap/manage.rst:101 +msgid "Remove a source" msgstr "" -#: ../system/sessions.rst:36 +#: ../system/integrations/ldap/manage.rst:92 msgid "" -"If *Geo IP services* is enabled only. Depends on how detailed the available " -"IP address information are." +"If you no longer need the a LDAP source or simply want to start over, you " +"can remove them at any time. This will not remove synchronized users, data " +"synchronized or permissions." msgstr "" -#: ../system/sessions.rst:39 +#: ../system/integrations/ldap/manage.rst:98 msgid "" -"Be aware that results can be inaccurate - this technically is not an error." +"Not sure if you'd need the source later on? Set the source to inactive " +"instead of removing it - see *Review or edit existing source* for more." msgstr "" -#: ../system/sessions.rst:43 -msgid "Age" +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing how to remove LDAP sources." msgstr "" -#: ../system/sessions.rst:43 -msgid "Provides the time when the session initially has been created." +#: ../system/integrations/pgp/index.rst:2 +msgid "PGP" msgstr "" -#: ../system/sessions.rst:50 -msgid "Update" +#: ../system/integrations/pgp/index.rst:7 +msgid "" +"Pretty Good Privacy (PGP) is another method for secure email communication. " +"With PGP, you can exchange **signed** and **encrypted** messages with others." msgstr "" -#: ../system/sessions.rst:46 -msgid "" -"Provides the time the user used this session to open Zammad. This timestamp " -"is only updated if the user e.g. reloads, not during normal work on tickets." +#: ../system/integrations/pgp/index.rst:13 +#: ../system/integrations/smime/index.rst:17 +msgid "Signing" msgstr "" -#: ../system/sessions.rst:50 -msgid "This timestamp is being used for the session timeout." +#: ../system/integrations/pgp/index.rst:11 +msgid "is a proof that a message hasn't been manipulated on its way." msgstr "" -#: ../system/sessions.rst:53 +#: ../system/integrations/pgp/index.rst:13 msgid "" -"Use the delete button to remove a single session on behalf of your user." +"In other words, it guarantees message **integrity** and **authenticity**." msgstr "" -#: ../system/subscription/billing.rst:2 -msgid "Billing" +#: ../system/integrations/pgp/index.rst:19 +#: ../system/integrations/smime/index.rst:22 +msgid "Encryption" msgstr "" -#: ../system/subscription/billing.rst:4 +#: ../system/integrations/pgp/index.rst:16 +#: ../system/integrations/smime/index.rst:20 msgid "" -"Within the billing tab you can control all billing relevant information like " -"invoices, billing address and the option to cancel your subscription." -msgstr "" - -#: ../system/subscription/billing.rst:33 -msgid "Billing information" +"scrambles a message so that it can only be unscrambled by the intended " +"recipient." msgstr "" -#: ../system/subscription/billing.rst:8 +#: ../system/integrations/pgp/index.rst:19 msgid "" -"All adjusted billing information below only affect future invoices. If your " -"invoice was issued wrong, please contact `our sales team `_." +"In other words, it guarantees message **privacy** and **data security**." msgstr "" -#: ../system/subscription/billing.rst:14 -msgid "Billing address" +#: ../system/integrations/pgp/index.rst:25 +msgid "Screenshot of ticket creation with encrypt and sign buttons" msgstr "" -#: ../system/subscription/billing.rst:13 +#: ../system/integrations/pgp/index.rst:25 msgid "" -"Provide your company address here, make sure to include the companies name " -"in case required. This address will be referenced on your invoice." +"Once PGP has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " +"appear in the ticket composer." msgstr "" -#: ../system/subscription/billing.rst:18 -msgid "VAT ID" +#: ../system/integrations/pgp/index.rst:28 +msgid "**Sign button not visible?**" msgstr "" -#: ../system/subscription/billing.rst:17 +#: ../system/integrations/pgp/index.rst:30 msgid "" -"Provide your VAT ID here. If applicable your invoice will not contain German " -"VAT. Please make sure to pay the VAT in your country as required." +"Please note that the signing of emails is based on the outgoing email " +"account. That means you have to choose a group with a sender email account, " +"which has a private key assigned." msgstr "" -#: ../system/subscription/billing.rst:27 -msgid "Billing Email Address" +#: ../system/integrations/pgp/index.rst:35 +msgid "Handling of Keys" msgstr "" -#: ../system/subscription/billing.rst:21 +#: ../system/integrations/pgp/index.rst:36 msgid "" -"Usually the instance owner (the person that registered the instance) will " -"receive all emails including the invoices. In case you have your own billing " -"department, you can provide their email address here." +"To use the PGP function, you have to enable the integration (PGP) by " +"switching the toggle to *enabled*." msgstr "" -#: ../system/subscription/billing.rst:25 +#: ../system/integrations/pgp/index.rst:39 msgid "" -"All billing relevant information will then be sent to this email address." +"You can add keys by clicking the *add key* button. The keys can be imported " +"from a file or you can paste the content of the key in the text box." msgstr "" -#: ../system/subscription/billing.rst:27 -msgid "Invoices are sent as attachment (PDF) to this email address." +#: ../system/integrations/pgp/index.rst:42 +msgid "**Which keys do I have to import?**" msgstr "" -#: ../system/subscription/billing.rst:29 +#: ../system/integrations/pgp/index.rst:44 msgid "" -"Don't forget to press the *Submit* button after you changed above settings." +"For **signing** *outgoing* emails, you have to import the private key of " +"your Zammad email account." msgstr "" -#: ../system/subscription/billing.rst:0 +#: ../system/integrations/pgp/index.rst:47 msgid "" -"Screenshot showing options for billing information within the\n" -"subscription menu" -msgstr "" - -#: ../system/subscription/billing.rst:70 -msgid "Payment history" +"For **encrypting** *outgoing* emails, you have to import the public key of " +"the customer's email account." msgstr "" -#: ../system/subscription/billing.rst:36 +#: ../system/integrations/pgp/index.rst:50 msgid "" -"The payment history will display a history of all paid invoices. At this " -"point you can also download these in case you need them again." +"For **verifying the signature** of signed *incoming* emails, you have to " +"import the public key of the customer." msgstr "" -#: ../system/subscription/billing.rst:41 +#: ../system/integrations/pgp/index.rst:53 msgid "" -"You will only find *paid* invoices here. Invoices that are to be billed are " -"not available before the payment is completed." +"For **decrypting** of encrypted *incoming* emails, you have to import the " +"private key of your Zammad email account." msgstr "" -#: ../system/subscription/billing.rst:46 -msgid "Date" +#: ../system/integrations/pgp/index.rst:57 +msgid "Import Keys From a File" msgstr "" -#: ../system/subscription/billing.rst:46 -msgid "Date of the invoice creation." +#: ../system/integrations/pgp/index.rst:58 +msgid "You can import keys from a file in the section **Upload key**:" msgstr "" -#: ../system/subscription/billing.rst:49 -msgid "Amount" +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of adding a key via file" msgstr "" -#: ../system/subscription/billing.rst:49 -msgid "Invoice total including VAT if applicable." +#: ../system/integrations/pgp/index.rst:64 +msgid "" +"**Supported file formats:** ASCII-armor as well as binary GPG format " +"(basically any GPG supported key format) is supported here." msgstr "" -#: ../system/subscription/billing.rst:52 -msgid "" -"Contains contract period (monthly or yearly) and hosted plan for the " -"subscription period in question." +#: ../system/integrations/pgp/index.rst:68 +msgid "Import Keys by Pasting the Content" msgstr "" -#: ../system/subscription/billing.rst:63 -msgid "Payment method / Service period" +#: ../system/integrations/pgp/index.rst:69 +msgid "You can also paste the key's content in the section **paste key**:" msgstr "" -#: ../system/subscription/billing.rst:56 -msgid "" -"Used bank account or credit card as well as the subscription period the " -"invoice is about." +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of adding a key via pasting" msgstr "" -#: ../system/subscription/billing.rst:61 +#: ../system/integrations/pgp/index.rst:75 msgid "" -"It might happen that the invoice date and subscription period differ. This " -"is nothing to worry about, the subscription periods will be accounted later " -"on." +"**Supported format:** Please note that only ASCII-armor is supported here." msgstr "" -#: ../system/subscription/billing.rst:67 -msgid "Receipt" +#: ../system/integrations/pgp/index.rst:78 +msgid "Deleting Keys" msgstr "" -#: ../system/subscription/billing.rst:66 +#: ../system/integrations/pgp/index.rst:79 msgid "" -"Use the arrow to download the invoice in question. You can download all " -"available invoices any time you need to here!" +"If you want to delete a specific key, you can do it by clicking on the menu " +"in the *actions* column and select **delete**:" msgstr "" -#: ../system/subscription/billing.rst:0 -msgid "Screenshot showing payment history of a hosted instance" +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of deleting a key" msgstr "" -#: ../system/subscription/billing.rst:94 -msgid "Do you want to cancel your subscription?" +#: ../system/integrations/pgp/index.rst:88 +msgid "Downloading Keys" msgstr "" -#: ../system/subscription/billing.rst:73 +#: ../system/integrations/pgp/index.rst:89 msgid "" -"In case you no longer want to use Zammad's SaaS, you can cancel your " -"subscription by using the red *Yes, please cancel my subscription* button." +"If you want to download your keys, you can do this as well via corresponding " +"action buttons. Depending on the key, you can choose wether you want to " +"download the private or the public key." msgstr "" -#: ../system/subscription/billing.rst:76 -msgid "" -"Your subscription will end the day after your trial or billing period ends." +#: ../system/integrations/pgp/index.rst:95 +#: ../system/integrations/smime/manage-certificates.rst:76 +msgid "Default Behavior" msgstr "" -#: ../system/subscription/billing.rst:80 +#: ../system/integrations/pgp/index.rst:96 msgid "" -"We will remind you about your cancelled subscription several times up front. " -"After the subscription ended all instance data will be removed. A restore " -"*is not* possible after that point!" -msgstr "" - -#: ../system/subscription/billing.rst:0 -msgid "Screencast showing how to cancel a subscription" +"Here you can adjust on per group basis, if *sign* and *encryption* is on or " +"off by default. Please be aware, that agents can always override the setting " +"for each individual article." msgstr "" -#: ../system/subscription/billing.rst:87 -msgid "**😖 Cancelled by accident?**" +#: ../system/integrations/pgp/index.rst:None +msgid "Adjusting default behavior on per group basis" msgstr "" -#: ../system/subscription/billing.rst:89 +#: ../system/integrations/pgp/index.rst:107 msgid "" -"You can always undo the cancellation via the *Yes, undo the cancellation of " -"my subscription* button up to the last subscription day!" +"Here you can see the last actions regarding signing and encryption and if " +"they were successful." msgstr "" -#: ../system/subscription/billing.rst:0 -msgid "" -"Screenshot showing a red button to cancel the subscription\n" -"cancellation" +#: ../system/integrations/pgp/index.rst:117 +msgid "**Sign button is not visible, but keys are imported.**" msgstr "" -#: ../system/subscription/index.rst:2 -msgid "Subscription (SaaS)" +#: ../system/integrations/pgp/index.rst:115 +msgid "Did you choose a group in the ticket?" msgstr "" -#: ../system/subscription/index.rst:4 +#: ../system/integrations/pgp/index.rst:116 msgid "" -"The subscription settings page allows you to configure your instances " -"package and number of agents required." +"Did you import a private key for the email adress, which is used for " +"outgoing emails in the group?" msgstr "" -#: ../system/subscription/index.rst:9 -msgid "" -"This setting section is only available for Hosted setups. If you're looking " -"for on premise support contracts, please see the `Zammad pricing page " -"`_." +#: ../system/integrations/pgp/index.rst:122 +msgid "**How to obtain keys?**" msgstr "" -#: ../system/subscription/index.rst:20 +#: ../system/integrations/pgp/index.rst:120 msgid "" -"The subscription section currently consists of two tabs: Plan & Billing. For " -"your overview we've divided those two tabs into independent sub pages:" +"You can create them yourself! There are some good tutorials on the web on " +"how to create them. Providing keys to Zammad is a prerequisite to use the " +"PGP feature." msgstr "" -#: ../system/subscription/index.rst:25 -msgid ":doc:`💰 Subscription plan `" +#: ../system/integrations/pgp/index.rst:127 +msgid "**It says a passphrase is needed, but I haven't got one.**" msgstr "" -#: ../system/subscription/index.rst:24 +#: ../system/integrations/pgp/index.rst:125 msgid "" -"Everything affecting your instance subscription functions like number of " -"agents, package and payment method." +"If the key is secured with a passphrase, you have to provide it for the " +"import in Zammad. It is possible that keys may have an empty passphrase. " +"However, this is *not* recommended." msgstr "" -#: ../system/subscription/index.rst:28 -msgid ":doc:`🧾 Subscription billing `" +#: ../system/integrations/pgp/index.rst:132 +msgid "**How do my customers get my new key?**" msgstr "" -#: ../system/subscription/index.rst:28 +#: ../system/integrations/pgp/index.rst:130 msgid "" -"Everything regarding billing address, invoices and account cancellation." +"You have to provide your **public** key in advance. Your customer also has " +"to configure PGP in their email workflow and import your public key. The " +"other way round, you have to get the public key of your customer and have to " +"import it to Zammad." msgstr "" -#: ../system/subscription/index.rst:33 -msgid "FAQ" +#: ../system/integrations/slack.rst:2 +msgid "Slack" msgstr "" -#: ../system/subscription/index.rst:37 -msgid "I set up a trial account but am missing functions to test" +#: ../system/integrations/slack.rst:4 +msgid "**⚠️ Deprecation warning ⚠️**" msgstr "" -#: ../system/subscription/index.rst:36 +#: ../system/integrations/slack.rst:6 msgid "" -"The trial instance is running within the professional package allowing up to " -"three agents." +"Zammad 7 will no longer support this dedicated Slack integration. It is " +"recommended to switch to :doc:`pre-defined webhooks ` instead. Existing Slack integrations should " +"be migrated manually before this feature is dropped." +msgstr "" + +#: ../system/integrations/slack.rst:14 +msgid "" +"In order to use this feature, please add a new Slack app to your Workspace. " +"The App you need is called ``Incoming WebHooks`` ." msgstr "" -#: ../system/subscription/index.rst:40 -msgid "Can I change package within the trial?" +#: ../system/integrations/slack.rst:18 +msgid "Why Do I Need This Feature?" msgstr "" -#: ../system/subscription/index.rst:40 -msgid "No. As soon as the package is changed the subscription begins." +#: ../system/integrations/slack.rst:20 +msgid "" +"If you're already using Slack for your team communication, you'll love this " +"feature! Our Slack integration can push ticket notifications about the last " +"ticket article based on the following events:" msgstr "" -#: ../system/subscription/index.rst:45 -msgid "What happens to my trial instance after the trial period ended?" +#: ../system/integrations/slack.rst:24 +msgid "on Ticket creation" msgstr "" -#: ../system/subscription/index.rst:43 -msgid "" -"Your instance will automatically be canceled for you. Please see *What " -"happens to my instance after it has been canceled?* for more." +#: ../system/integrations/slack.rst:25 +msgid "on Ticket updates" msgstr "" -#: ../system/subscription/index.rst:58 -msgid "What happens to my instance after it has been canceled?" +#: ../system/integrations/slack.rst:26 +msgid "on reached reminders" msgstr "" -#: ../system/subscription/index.rst:48 -msgid "That depends slightly on your instance state:" +#: ../system/integrations/slack.rst:27 +msgid "a Ticket has escalated" msgstr "" -#: ../system/subscription/index.rst:54 -msgid "Trial instance" +#: ../system/integrations/slack.rst:28 +msgid "a Ticket is going to escalate" msgstr "" -#: ../system/subscription/index.rst:51 +#: ../system/integrations/slack.rst:30 msgid "" -"If you're still on trial, we will ice your instance and remind you once " -"again about your instance. We then will wait some days and remove your " -"instance from our system. This is the last time we will inform you by Email." -msgstr "" - -#: ../system/subscription/index.rst:58 -msgid "Paid instance" +"Zammad will provide the Ticket title, a direct link to the Ticket, the event " +"type (creation, updated, escalation), the customer, time and the last " +"article that has triggered the notification." msgstr "" -#: ../system/subscription/index.rst:57 +#: ../system/integrations/slack.rst:34 msgid "" -"If you're a paying customer and canceled your subscription, the instance " -"removal will take place the day after your last subscription day." +"This will give you further options, as you can see e.g. escalating tickets " +"that are assigned to an agent that's e.g. absent. You can interact faster, " +"as you might see problems earlier (or even before the problem gets one)." msgstr "" -#: ../system/subscription/index.rst:60 -msgid "Can removed instances be restored?" +#: ../system/integrations/slack.rst:38 +msgid "" +"If needed and wanted, you can even discuss directly about the topic before " +"sending an answer to the customer. Another possible use case would be a " +"agent monitoring new agents and their answers to tickets." msgstr "" -#: ../system/subscription/index.rst:61 -msgid "No. Once your instance has been removed, a restoration is not possible." +#: ../system/integrations/slack.rst:44 +msgid "Configure the Integration" msgstr "" -#: ../system/subscription/plan.rst:2 ../system/subscription/plan.rst:38 -msgid "Plan" +#: ../system/integrations/slack.rst:46 +msgid "" +"First of all, please go to your slack workspace - go to administration => " +"Manage Apps. If you don't have an app yet, you can simply add a new one - " +"just search for ``Incoming WebHooks`` and customize the app to your needs." msgstr "" -#: ../system/subscription/plan.rst:16 -msgid "Subscription" +#: ../system/integrations/slack.rst:50 +msgid "" +"Choose (or create) the channel Zammad should post it's information to and " +"press on \"Add Incoming WebHooks integration\". If you're ready, copy the " +"provided WebHook URL and go to your Zammad installation." msgstr "" -#: ../system/subscription/plan.rst:5 +#: ../system/integrations/slack.rst:56 msgid "" -"On the top of the subscription summary you'll find the number of used and " -"available (booked) agent seats. By using the *see more* link you can also " -"expand an agent list to see the currently configured active agents. This " -"list *does not* count accounts with admin permissions only." +"You need administrative rights on the Slack Workspace. The link to the app " +"directory is normally ``https://[workspace-name].slack.com/apps`` ." msgstr "" -#: ../system/subscription/plan.rst:0 +#: ../system/integrations/slack.rst:63 msgid "" -"Within subscription you can always see how many agents are still\n" -"available to add and who uses the seats." +"To configure the slack integration, log in to Zammad and go to Integrations " +"(System) => Slack in the admin panel." msgstr "" -#: ../system/subscription/plan.rst:14 +#: ../system/integrations/slack.rst:66 msgid "" -"Learn more on how to manage your agents in general :doc:`here `." +"Here you can choose on what evens Zammad should post information about a " +"ticket to your Slack channel. Next you need to device what groups shall be " +"affected by this, as anybody with access to that specific Slack channel can " +"read at least parts of the ticket this might be a privacy issue, if you " +"select the wrong groups. The username is simply the name that Zammad uses as " +"display name inside the Slack chat. The channel defines the Slack channel " +"the information is being posted in. As last option, you can set a custom " +"icon for posting to slack." msgstr "" -#: ../system/subscription/plan.rst:19 +#: ../system/integrations/slack.rst:74 msgid "" -"This section gives you an overview of the available plans and their " -"functions / limits. If you require a more detailed table, check our " -"`detailed pricing table `_ for more." +"When you're ready, just hit \"Submit\" and enable the integration. Zammad " +"will now post new ticket information based on the trigger you chose. Below " +"the options you have the recent log that shows the latest requests to Slack " +"for debugging if needed." msgstr "" -#: ../system/subscription/plan.rst:23 +#: ../system/integrations/slack.rst:81 msgid "" -"Your selection in this step will decide on the base agent price and e.g. " -"agent limits that might apply in the summary step." +"If you leave the Icon URL empty, Zammad will use the Zammad logo instead. " +"The icon should be a square PNG file." msgstr "" -#: ../system/subscription/plan.rst:26 +#: ../system/integrations/slack.rst:90 msgid "" -"The green *Selected* button will also tell you what plan you're currently in." +"The following figure shows how it will look if you choose to receive updates " +"on created and updated tickets. On every post Zammad sends to the Slack " +"channel, you can create new threads to discuss about the new article." msgstr "" -#: ../system/subscription/plan.rst:30 +#: ../system/integrations/slack.rst:96 msgid "" -"Trial instances are running at Professional with 3 agents. The plan cannot " -"be changed during the trial for technical reasons, if you require more " -"agents for testing, please contact `our sales team `_ with a reason for the raise request." +"If you just want to keep track of soon escalating or already escalated " +"tickets, it will look the the following figure. Zammad changes the color in " +"front of the post so you can easily see the state of the ticket." msgstr "" -#: ../system/subscription/plan.rst:0 +#: ../system/integrations/slack.rst:102 msgid "" -"Screenshot showing three available packages for a hosted Zammad\n" -"instance" +"If you change the state, Zammad will also put information on what state the " +"ticket gets and (if pending state) the date until it pends. You'll also " +"recognize the color codes in front of posts on slack, as they are exact the " +"same the ticket state colors you'll see in Zammad!" msgstr "" -#: ../system/subscription/plan.rst:83 -msgid "Summary" +#: ../system/integrations/smime/index.rst:2 +msgid "S/MIME" msgstr "" -#: ../system/subscription/plan.rst:41 +#: ../system/integrations/smime/index.rst:11 msgid "" -"In this section you can adjust the settings of the previous selected plan." +"S/MIME is the most widely-supported method for secure email communication. " +"With S/MIME, you can exchange **signed** and **encrypted** messages with " +"others." msgstr "" -#: ../system/subscription/plan.rst:45 +#: ../system/integrations/smime/index.rst:15 msgid "" -"Note that upgrading (more agents, higher package) is always possible, " -"however, downgrading will only happen when your billing period renews." +"is proof that a message hasn't been tampered with or sent by an impersonator." msgstr "" -#: ../system/subscription/plan.rst:49 +#: ../system/integrations/smime/index.rst:17 msgid "" -"Upgrading resets your billing period and existing credit will be deducted " -"from the new total." +"In other words, it guarantees a message's **integrity** and **authenticity**." msgstr "" -#: ../system/subscription/plan.rst:58 -msgid "Billing cycle" +#: ../system/integrations/smime/index.rst:22 +msgid "In other words, it guarantees **privacy** and **data security**." msgstr "" -#: ../system/subscription/plan.rst:53 -msgid "" -"You can choose between either monthly or yearly billing. The price per agent " -"will be cheaper if you decide for yearly billing." +#: ../system/integrations/smime/index.rst:28 +msgid "Screencast demo of S/MIME features for both new tickets and replies" msgstr "" -#: ../system/subscription/plan.rst:56 +#: ../system/integrations/smime/index.rst:28 msgid "" -"If you're still trying out things and are unsure of the right package for " -"your instance, you may want to choose monthly first and then upgrade to " -"yearly when you're sure." +"Once S/MIME has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " +"appear in the ticket composer." msgstr "" -#: ../system/subscription/plan.rst:66 -msgid "Plan: (Starter|Professional|Plus) - Agents" +#: ../system/integrations/smime/index.rst:32 +msgid ":doc:`🔪 Prerequisites `" msgstr "" -#: ../system/subscription/plan.rst:61 -msgid "Choose the number of agents you require for your instance." +#: ../system/integrations/smime/index.rst:31 +msgid "" +"New to S/MIME? This section helps you to find certificate providers and " +"points out Limitations." msgstr "" -#: ../system/subscription/plan.rst:63 -msgid "" -"Keep in mind that some packages may have agent limits. Depending on the " -"previous chosen package, you won't be able to exceed specific agent numbers. " -"Also note that setting less agents than currently configured is not possible." +#: ../system/integrations/smime/index.rst:35 +msgid ":doc:`📝 Manage Certificates `" msgstr "" -#: ../system/subscription/plan.rst:69 -msgid "Total" +#: ../system/integrations/smime/index.rst:35 +msgid "Add and download certificates; configure group default behaviors." msgstr "" -#: ../system/subscription/plan.rst:69 -msgid "This will be the net total you're going to be billed." +#: ../system/integrations/smime/index.rst:38 +msgid ":doc:`😦 Troubleshooting `" msgstr "" -#: ../system/subscription/plan.rst:71 -msgid "" -"By using the *Update subscription* button, the instance package will be " -"adjusted immediately. If you didn't provide a payment method yet, Zammad " -"will request you to provide one at this point." +#: ../system/integrations/smime/index.rst:38 +msgid "Took a wrong turn? About recent logs and common issues." msgstr "" -#: ../system/subscription/plan.rst:77 +#: ../system/integrations/smime/index.rst:43 msgid "" -"In case you're still within the trial period, this means that the trial will " -"be over immediately!" +"For more details on how S/MIME integration works on the agent side, see the :" +"user-docs:`user docs `." msgstr "" -#: ../system/subscription/plan.rst:80 -msgid "Down- or upgrading during the trial period *is not* possible." +#: ../system/integrations/smime/manage-certificates.rst:2 +msgid "Manage Certificates" msgstr "" -#: ../system/subscription/plan.rst:0 -msgid "Screenshot showing payment options and a pricing summary" +#: ../system/integrations/smime/manage-certificates.rst:4 +msgid "" +"S/MIME is **disabled by default**. Enable it to start adding certificates." msgstr "" -#: ../system/subscription/plan.rst:99 -msgid "Payment method" +#: ../system/integrations/smime/manage-certificates.rst:10 +msgid "Dialogue to add new certificates or private keys" msgstr "" -#: ../system/subscription/plan.rst:86 -msgid "You can pay via credit card or SEPA mandate." +#: ../system/integrations/smime/manage-certificates.rst:10 +msgid "" +"Manage certificates in the Admin Panel under **System > Integrations > S/" +"MIME**. Certificates may be pasted in as plain text or uploaded from a file." msgstr "" -#: ../system/subscription/plan.rst:91 -msgid "Credit card" +#: ../system/integrations/smime/manage-certificates.rst:14 +msgid "Add Certificate Data" msgstr "" -#: ../system/subscription/plan.rst:89 -msgid "" -"Simply follow the dialogue by clicking *authorize* and confirm -if required " -"by your bank- your consent to Zammad using your card for the payments." +#: ../system/integrations/smime/manage-certificates.rst:36 +msgid "Add Certificate" msgstr "" -#: ../system/subscription/plan.rst:95 -msgid "SEPA" +#: ../system/integrations/smime/manage-certificates.rst:17 +msgid "" +"Import public-key certificates for both your own organization and your " +"contacts." msgstr "" -#: ../system/subscription/plan.rst:94 +#: ../system/integrations/smime/manage-certificates.rst:19 msgid "" -"Provide the requested information of the bank account holder and update if " -"you're ready. You'll then receive an email with the SEPA mandate." +"You can also add a bunch of certificates in one go by providing a single " +"file with all relevant certificates." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:22 +msgid "🕵️ **ALWAYS verify certificates in-person or over the phone!**" msgstr "" -#: ../system/subscription/plan.rst:97 +#: ../system/integrations/smime/manage-certificates.rst:24 msgid "" -"Technically there's also the possibility to pay via invoice, however - this " -"method only applies to a fairly low number of instances. Please contact `our " -"sales team `_ for more information." +"The whole point of signatures is to alert you when someone is trying to " +"pretend to be someone they're not. Never accept a certificate from someone " +"online without verifying it first." msgstr "" -#: ../system/translations.rst:2 -msgid "Translations" -msgstr "Переводы" +#: ../system/integrations/smime/manage-certificates.rst:28 +msgid "📇 **What about trusted certificate authorities?**" +msgstr "" -#: ../system/translations.rst:4 +#: ../system/integrations/smime/manage-certificates.rst:30 msgid "" -"Translations of Zammad are processed centrally in our `Weblate instance " -"`_. This allows non-developers to review " -"and update translation texts of the language they actually speak." +"In some cases (e.g. when dealing with large enterprises), you may be given a " +"certificate for an entire CA, rather than a single contact. Add it here to " +"trust *all* certificates issued by that CA." msgstr "" -#: ../system/translations.rst:9 +#: ../system/integrations/smime/manage-certificates.rst:35 msgid "" -"Your language is in an incomplete translation state or has typos? Please " -"consider helping us in sorting this out! All you need is either a GitHub " -"account or to register directly in our instance." +"Commercial CAs can usually be verified online. Zammad does not include a " +"list of built-in, trusted CAs." msgstr "" -#: ../system/translations.rst:13 +#: ../system/integrations/smime/manage-certificates.rst:57 +msgid "Add Private Key" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:39 msgid "" -"Did you know? This is also where the documentation translations are handled. " -"🤓" +"Once you've added a public-key certificate, you can import its matching " +"private key." msgstr "" -#: ../system/translations.rst:15 +#: ../system/integrations/smime/manage-certificates.rst:42 msgid "" -"Have a look in our :docs:`contribution section ` in the system documentation to get started!" +"Private keys are for **your own organization only**; never ask your contacts " +"for their private keys." msgstr "" -#: ../system/translations.rst:20 -msgid "Local Translations" +#: ../system/integrations/smime/manage-certificates.rst:0 +msgid "" +"S/MIME integration showing configured certificates and possible issues with " +"Logging" msgstr "" -#: ../system/translations.rst:22 +#: ../system/integrations/smime/manage-certificates.rst:50 msgid "" -"Apart from these system translations, there's still local translations you " -"can manage. This is relevant if you added custom objects that require " -"translations or even custom states and priorities." +"A note is displayed on certificates with a matching private key (see line 2)." msgstr "" -#: ../system/translations.rst:None -msgid "Translation management screen within the admin menu" +#: ../system/integrations/smime/manage-certificates.rst:52 +msgid "📤 **Certificates and private keys must be uploaded separately.**" msgstr "" -#: ../system/translations.rst:31 -msgid "Updating Translations" +#: ../system/integrations/smime/manage-certificates.rst:54 +msgid "" +"If your certificate and private key are bundled together in the same file or " +"PEM block, import it twice (once using each button)." msgstr "" -#: ../system/translations.rst:33 -msgid "" -"Because of how Zammad ships translations, the only way to update the system " -"translations is to update your Zammad installation. The benefit of this is " -"that you no longer need internet access during a Zammad upgrade as the " -"package has everything it requires already." +#: ../system/integrations/smime/manage-certificates.rst:57 +msgid "Please note that bulk imports of private keys are not possible." msgstr "" -#: ../system/translations.rst:39 -msgid "Translation of Custom Objects" +#: ../system/integrations/smime/manage-certificates.rst:60 +msgid "Download Certificate Data" msgstr "" -#: ../system/translations.rst:41 +#: ../system/integrations/smime/manage-certificates.rst:62 msgid "" -"No problem at all! You can customize any translation locally, even if it is " -"not initially provided by the system." +"You can download the earlier provided certificates and private keys at any " +"time from your Zammad instance." msgstr "" -#: ../system/translations.rst:44 +#: ../system/integrations/smime/manage-certificates.rst:65 msgid "" -"Translation is supported for a broad number of features, including but not " -"limited to custom:" +"Please note that passphrase-protected private keys stay protected and when " +"you download them, you have to know the passphrase to use them after " +"downloading." msgstr "" -#: ../system/translations.rst:47 -msgid "Object Attributes" +#: ../system/integrations/smime/manage-certificates.rst:73 +msgid "Dialogue to download certificates or private keys" msgstr "" -#: ../system/translations.rst:48 -msgid "Ticket Macros" -msgstr "Макрос заявки" - -#: ../system/translations.rst:49 -msgid "Ticket Overviews" +#: ../system/integrations/smime/manage-certificates.rst:73 +msgid "Download stored certificates and their keys" msgstr "" -#: ../system/translations.rst:50 -msgid "Ticket Priorities" +#: ../system/integrations/smime/manage-certificates.rst:78 +msgid "" +"The ticket composer will set all outgoing messages to **signed and " +"encrypted** by default (assuming the required certificates exist)." msgstr "" -#: ../system/translations.rst:51 -msgid "Ticket States" +#: ../system/integrations/smime/manage-certificates.rst:82 +msgid "These defaults can be modified on a per-group basis:" msgstr "" -#: ../system/translations.rst:54 -msgid "Customizing Translations" +#: ../system/integrations/smime/manage-certificates.rst:None +msgid "Zammad allowing to choose the default behavior on per group basis" msgstr "" -#: ../system/translations.rst:56 +#: ../system/integrations/smime/manage-certificates.rst:89 msgid "" -"Within the translation screen, simply click on the **New Translation** " -"button." +"Of course, agents can always manually change these settings on each email " +"they send out." msgstr "" -#: ../system/translations.rst:None -msgid "New translation dialog" +#: ../system/integrations/smime/prerequisites.rst:4 +msgid "A certificate *and* private key for your own organization" msgstr "" -#: ../system/translations.rst:62 +#: ../system/integrations/smime/prerequisites.rst:6 msgid "" -"In the dialog you can immediately enter the exact translation source (if you " -"know it) and your custom translation text for it and click **Submit**." +"(Use this to ✒️ **sign outgoing messages** and 🔓 **decrypt incoming " +"messages**.)" msgstr "" -#: ../system/translations.rst:65 +#: ../system/integrations/smime/prerequisites.rst:9 msgid "" -"Alternatively, try to search for translation suggestions in the list below. " -"Selecting an item from the list will pre-fill the translation source for you " -"and then you can just enter your custom translation." +"Certificates belonging your contacts, or their issuing certificate authority " +"(CA)" msgstr "" -#: ../system/translations.rst:69 +#: ../system/integrations/smime/prerequisites.rst:11 msgid "" -"The target language will always default to your current language selection. " -"If you need to translate for a different language, simply change the " -"selection before submitting." +"(Use these to ✅ **verify incoming message signatures** and 🔒 **encrypt " +"outgoing messages**.)" msgstr "" -#: ../system/translations.rst:73 -msgid "" -"All your custom translations will show up in the overview table when added. " -"And they will even persist across Zammad updates!" +#: ../system/integrations/smime/prerequisites.rst:14 +msgid "🙋 **I'm new to S/MIME. Where can I get a certificate?**" msgstr "" -#: ../system/translations.rst:76 +#: ../system/integrations/smime/prerequisites.rst:16 msgid "" -"Make sure to reload your browser if a translated string is not displayed." -msgstr "" - -#: ../system/translations.rst:80 -msgid "Reverting to Original Translations" +"The easiest way to get certificates is to buy an annual subscription through " +"a commercial CA, such as:" msgstr "" -#: ../system/translations.rst:82 +#: ../system/integrations/smime/prerequisites.rst:19 msgid "" -"If you want to revert a custom translation to original text, simply use the " -"appropriate action within the row of the overview table." +"`Sectigo (formerly Comodo) `_" msgstr "" -#: ../system/translations.rst:85 -msgid "" -"Depending on the type of the translation source, the action has a slightly " -"different name:" +#: ../system/integrations/smime/prerequisites.rst:20 +msgid "`Secorio `_" msgstr "" -#: ../system/translations.rst:88 -msgid "**Reset** for customized system translations" +#: ../system/integrations/smime/prerequisites.rst:21 +msgid "`GlobalSign `_" msgstr "" -#: ../system/translations.rst:89 -msgid "**Remove** for customized local translations" +#: ../system/integrations/smime/prerequisites.rst:23 +msgid "(Zammad is not affiliated with these CAs in any way.)" msgstr "" -#: ../system/translations.rst:91 +#: ../system/integrations/smime/prerequisites.rst:25 msgid "" -"In both cases, the action will remove the customized translation after a " -"confirmation." +"You can also generate your own self-signed certificates, but the process is " +"complicated and usually 🙅 **involves extra work for your contacts**." msgstr "" -#: ../system/translations.rst:None -msgid "Screenshot showing the location of the Remove action" +#: ../system/integrations/smime/prerequisites.rst:29 +msgid "" +"Bear in mind that 🤝 **S/MIME only works if the other party is using it, too." +"**" msgstr "" -#: ../system/translations.rst:99 -msgid "Inline Translations" +#: ../system/integrations/smime/prerequisites.rst:32 +msgid "Certificate and Private Key Checks on Upload" msgstr "" -#: ../system/translations.rst:101 +#: ../system/integrations/smime/prerequisites.rst:34 msgid "" -"If you prefer a more hands-on approach, you can activate the inline or on-" -"screen translation feature by pressing ``ctrl`` + ``alt`` + ``t`` at any " -"time and on any screen." +"The certificate and public key validation is based on the ``X509v3`` " +"extensions." msgstr "" -#: ../system/translations.rst:105 -msgid "" -"All customizable translation texts will be highlighted for you on the " -"screen. Just click into the highlighted area and update the text in place." +#: ../system/integrations/smime/prerequisites.rst:49 +msgid "Uploading a *client certificate*?" msgstr "" -#: ../system/translations.rst:None -msgid "Inline translation mode activated for the Overview screen" +#: ../system/integrations/smime/prerequisites.rst:41 +msgid "The following attributes are required then:" msgstr "" -#: ../system/translations.rst:112 -msgid "" -"When finished editing, simply press ``ctrl`` + ``alt`` + ``t`` again to " -"deactivate." +#: ../system/integrations/smime/prerequisites.rst:39 +msgid "Subject Alternative Name (at least one email address has to be present)" msgstr "" -#: ../system/translations.rst:117 -msgid "" -"Even though it's available on any screen, the inline translation feature " -"requires admin permissions. It works only for the current language " -"selection. If you need to translate a different language, first change the " -"language in your :user-docs:`profile settings `." +#: ../system/integrations/smime/prerequisites.rst:40 +msgid "Key Usage (``Digital Signature`` and/or ``Key Encipherment``)" msgstr "" -#: ../system/variables.rst:2 -msgid "Variables" +#: ../system/integrations/smime/prerequisites.rst:41 +msgid "Public key algorithm (either ``RSA`` or ``EC``)" msgstr "" -#: ../system/variables.rst:4 +#: ../system/integrations/smime/prerequisites.rst:43 msgid "" -"Please note that this is just an overview of available variables. It might " -"be incomplete or variables might not be available within some functions. If " -"you're missing variables or are not sure if something is not working as " -"expected, feel free to ask over at the `Community `_." +"The Extended Key Usage attribute is optional. If the certificate provides " +"the named attribute, than it must contain the value ``E-mail Protection``." msgstr "" -#: ../system/variables.rst:10 +#: ../system/integrations/smime/prerequisites.rst:46 msgid "" -"Variables can be called by typing ``::`` (just like text modules in the " -"frontend), as long as you're in a supported text field within the backend. " -"Zammad will display all variables being available within this context and " -"replace it to the variable as soon as you selected an entry." +"Please note that any usable email adress has to be prefixed with ``email:`` " +"or ``rfc822:``." msgstr "" -#: ../system/variables.rst:15 -msgid "" -"You have an empty field which you referenced and it appears as ``-``? That's " -"currently working as designed - you might want to ensure that these fields " -"always have a value." +#: ../system/integrations/smime/prerequisites.rst:49 +msgid "The named public key algorithms are mandatory for private keys as well." msgstr "" -#: ../system/variables.rst:20 -msgid "Variable Categories" +#: ../system/integrations/smime/prerequisites.rst:54 +msgid "Uploading a *CA certificate*?" msgstr "" -#: ../system/variables.rst:31 -msgid "Wait, What About Custom Objects?" +#: ../system/integrations/smime/prerequisites.rst:52 +msgid "" +"In the case of an uploaded CA certificate, providing the value ``CA:TRUE`` " +"in the attribute *Basic Contstraints*, the previously mentioned attributes " +"are not verified." msgstr "" -#: ../system/variables.rst:33 +#: ../system/integrations/smime/prerequisites.rst:56 msgid "" -"Good point! Of course, we can't predict what objects you might create, but " -"we can give you a hint on how to put the puzzle together to get your custom " -"values." +"In general, the usage of any expired (``Not After``) or not yet valid (``Not " +"Before``) certificate is denied for outgoing emails." msgstr "" -#: ../system/variables.rst:36 -msgid "" -"For this, we'll talk about the inner part of the variable (so everything " -"within ``#{}``), please put the outer part around to have a valid variable. " -"The first part of the variable name consist of the object type. Currently " -"these are:" +#: ../system/integrations/smime/prerequisites.rst:59 +msgid "Example certificate:" msgstr "" -#: ../system/variables.rst:41 -msgid "Ticket (``ticket``)" +#: ../system/integrations/smime/prerequisites.rst:85 +msgid "" +"Please note that Zammad will distrust senders by default. This means that " +"you're always required to provide certificate data, no matter if for signing " +"or encrypting." msgstr "" -#: ../system/variables.rst:42 -msgid "User (``user``)" +#: ../system/integrations/smime/prerequisites.rst:89 +msgid "This is by design and can't be adjusted." msgstr "" -#: ../system/variables.rst:43 -msgid "Organization (``organization``)" +#: ../system/integrations/smime/troubleshooting.rst:4 +msgid "" +"All of the system's latest S/MIME activity is displayed in the **Recent " +"Logs** section." msgstr "" -#: ../system/variables.rst:44 -msgid "Group (``group``)" +#: ../system/integrations/smime/troubleshooting.rst:11 +msgid "Sample entries of in- and outgoing S/MIME related emails." msgstr "" -#: ../system/variables.rst:46 +#: ../system/integrations/smime/troubleshooting.rst:11 msgid "" -"The second part is the name of the object. This is the name you define " -"during object creation and can be found within the object menu at any time. " -"The first and second part of a variable is divided by a point, e.g.: " -"``ticket.number`` which will in total be ``#{ticket.number}``." +"Logs report the status and details of all mail, both incoming and outgoing, " +"that used signing/verification or encryption/decryption." msgstr "" -#: ../system/variables.rst:51 +#: ../system/integrations/smime/troubleshooting.rst:14 msgid "" -"Now, in some situations it's possible that you'll need to use a third part. " -"The best example for such a situation would be a ``select`` or ``tree-" -"select`` field which will by default return the key value, not it's display " -"name. For this, just extend your variable with ``.value``. This will result " -"in ``#{ticket.select.value}``." +"This log does **not** include email sent by :doc:`triggers ` or the :doc:`scheduler `. For those, check your " +"``production.log``." +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:20 +msgid "Common Issues" msgstr "" -#: ../system/variables.rst:60 -msgid "Using Translated Variables" +#: ../system/integrations/smime/troubleshooting.rst:30 +msgid "I received a signed/encrypted email before I set up S/MIME integration" msgstr "" -#: ../system/variables.rst:62 +#: ../system/integrations/smime/troubleshooting.rst:23 msgid "" -"If you want to use a translated variable in triggers or schedulers, you can " -"extend the placeholder like this: ``#{t(ticket.state.name)}``. The ``t`` " -"tells Zammad to search for fitting translated strings. The used output " -"language is based on the system language of Zammad which you can set in the " -"admin panel under :doc:`/settings/branding` or based on the selected locale " -"in the trigger/scheduler edit dialog." +"No problem. Once S/MIME has been enabled and the appropriate certificates " +"have been added, agents will be prompted to retry verification/decryption on " +"matching emails." msgstr "" -#: ../system/variables.rst:69 -msgid "" -"A possible use-case: you want to send your customers updates on tickets via " -"trigger or scheduler which should include the state of the ticket. Using the " -"default ``#{ticket.state.name}`` (without the translation flag ``t()``) " -"would lead to the output of the original (english) name of the state." +#: ../system/integrations/smime/troubleshooting.rst:0 +msgid "Screenshot of user prompt to retry decryption" msgstr "" -#: ../system/variables.rst:75 -msgid "Date and Time Formatting" +#: ../system/integrations/smime/troubleshooting.rst:38 +msgid "The 🔒 **Encrypt** button is disabled" msgstr "" -#: ../system/variables.rst:77 -msgid "" -"The system (trigger/scheduler selected) locale and timezone predefines a " -"default format of date and timestamp. This format is customizable by using " -"the ``dt()`` method." +#: ../system/integrations/smime/troubleshooting.rst:33 +msgid "Have you added the recipient's certificate?" msgstr "" -#: ../system/variables.rst:79 -msgid "The method arguments are as follows:" +#: ../system/integrations/smime/troubleshooting.rst:34 +msgid "Are you sure the recipient's certificate is valid?" msgstr "" -#: ../system/variables.rst:81 -msgid "The date or timestamp variable you want to format." +#: ../system/integrations/smime/troubleshooting.rst:35 +msgid "Have you checked your ``production.log`` for more details?" msgstr "" -#: ../system/variables.rst:82 -msgid "The output format string." +#: ../system/integrations/smime/troubleshooting.rst:37 +msgid "" +"If encryption doesn't work in the composer, it won't work in :doc:`triggers " +"` or the :doc:`scheduler ` either!" msgstr "" -#: ../system/variables.rst:83 -msgid "The timezone to apply (optional)." +#: ../system/integrations/smime/troubleshooting.rst:42 +msgid "The ✅ **Sign** button is disabled" msgstr "" -#: ../system/variables.rst:86 +#: ../system/integrations/smime/troubleshooting.rst:41 msgid "" -"``#{dt(ticket.updated_at, \"%A %Y-%m-%d %H:%M in the office\", \"Europe/" -"Berlin\")}``" +"Have you added **both the certificate and private key** for your " +"organization?" msgstr "" -#: ../system/variables.rst:87 -msgid "Monday, 2024-03-18 15:31 in the office" +#: ../system/integrations/smime/troubleshooting.rst:42 +msgid "" +"Does the email address on the certificate match the email address of the " +"agent/group composing the email?" msgstr "" -#: ../system/variables.rst:89 -msgid "" -"If you want to use our example, make sure to paste the string above without " -"formatting (``CTRL+Shift+v``), otherwise it won't work." +#: ../system/integrations/smime/troubleshooting.rst:45 +msgid "Error: “Fingerprint already taken”" msgstr "" -#: ../system/variables.rst:93 -msgid "The following table lists available format directives:" +#: ../system/integrations/smime/troubleshooting.rst:45 +msgid "Are you sure you haven't added this certificate already?" msgstr "" -#: ../system/variables.rst:99 -msgid "Parameter" +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Error: “❌ invalid byte sequence in UTF-8”" msgstr "" -#: ../system/variables.rst:102 -msgid "``%Y``" +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Please ensure to provide PEM formatted certificate and keys." msgstr "" -#: ../system/variables.rst:103 -msgid "Year with 4 digits" +#: ../system/integrations/smime/troubleshooting.rst:49 +msgid "Did you check if the provided file is a valid certificate or key?" msgstr "" -#: ../system/variables.rst:104 -msgid "Use ``%y`` for year with 2 digits" +#: ../system/integrations/zabbix.rst:2 +msgid "Zabbix Integration" msgstr "" -#: ../system/variables.rst:105 -msgid "``%m``" +#: ../system/integrations/zabbix.rst:5 +msgid "" +"This guide describes how to integrate your Zabbix 5.4 installation with " +"Zammad using the Zabbix webhook feature. This guide will provide " +"instructions on setting up a media type, a user and an action in Zabbix." msgstr "" -#: ../system/variables.rst:106 -msgid "Month of year (as number with zero-padding)" +#: ../system/integrations/zabbix.rst:12 +msgid "Zammad with enabled HTTP Token Authentication" msgstr "" -#: ../system/variables.rst:107 -msgid "Use ``%-m`` for month without zero-padding" +#: ../system/integrations/zabbix.rst:13 +msgid "Zabbix version 5.4 or higher" msgstr "" -#: ../system/variables.rst:108 -msgid "``%d``" +#: ../system/integrations/zabbix.rst:16 +msgid "Setting up a Zammad" msgstr "" -#: ../system/variables.rst:109 -msgid "Day of month (as number with zero-padding)" +#: ../system/integrations/zabbix.rst:18 +msgid "Enable **API Token Access** in Settings > System > API." msgstr "" -#: ../system/variables.rst:110 -msgid "Use ``%e`` for day without zero-padding" +#: ../system/integrations/zabbix.rst:20 +msgid "" +"Create a **new user** for a Zabbix alerter with an **email address** and " +"create a personal user token with **ticket.agent** permissions." msgstr "" -#: ../system/variables.rst:111 -msgid "``%H``" +#: ../system/integrations/zabbix.rst:24 +msgid "Zabbix Webhook Configuration" msgstr "" -#: ../system/variables.rst:112 -msgid "Hour of day in 24h notation with zero-padding" +#: ../system/integrations/zabbix.rst:27 +#, fuzzy +msgid "Create a Global Macro" +msgstr "Создать Макрос" + +#: ../system/integrations/zabbix.rst:29 +msgid "" +"Before setting up the **Webhook**, you need to setup the global macro " +"**{$ZABBIX.URL}**, which must contain the **URL** to the **Zabbix frontend**." msgstr "" -#: ../system/variables.rst:113 -msgid "Use ``%k`` for hour without zero-padding" +#: ../system/integrations/zabbix.rst:33 +msgid "" +"In the **Administration** > **Media types** section, import the `Template`_." msgstr "" -#: ../system/variables.rst:114 -msgid "``%I``" +#: ../system/integrations/zabbix.rst:38 +msgid "Open the added **Zammad** media type and set:" msgstr "" -#: ../system/variables.rst:115 -msgid "Hour of day in 12h notation with zero-padding" +#: ../system/integrations/zabbix.rst:40 +msgid "**zammad\\_access\\_token** to the your **Personal User Token**" msgstr "" -#: ../system/variables.rst:116 +#: ../system/integrations/zabbix.rst:41 msgid "" -"Use ``%l`` for hour without zero-padding and ``%p`` / ``%P`` for meridian " -"indicator" +"**zammad\\_url** to the **frontend URL** of your **Zammad** installation" msgstr "" -#: ../system/variables.rst:117 -msgid "``%M``" +#: ../system/integrations/zabbix.rst:43 +msgid "**zammad\\_customer** to your **Zammad user email**." msgstr "" -#: ../system/variables.rst:118 -msgid "Minute of hour" +#: ../system/integrations/zabbix.rst:44 +msgid "" +"**zammad\\_enable\\_tags** to **true** or **false** to enable or disable " +"trigger tags. **Important**: if you enable tag support, each tag is set with " +"a separate request." msgstr "" -#: ../system/variables.rst:120 -msgid "``%S``" +#: ../system/integrations/zabbix.rst:48 +msgid "" +"If you want to prioritize issues according to **severity** values in Zabbix, " +"you can define mapping parameters:" msgstr "" -#: ../system/variables.rst:121 -msgid "Second of Minute" +#: ../system/integrations/zabbix.rst:51 +msgid "**severity\\_**: Zammad priority ID" msgstr "" -#: ../system/variables.rst:123 -msgid "``%A``" +#: ../system/integrations/zabbix.rst:53 +msgid "Click the **Update** button to save the **Webhook** settings." msgstr "" -#: ../system/variables.rst:124 -msgid "Weekday name" +#: ../system/integrations/zabbix.rst:55 +msgid "" +"To receive notifications in **Zammad**, you need to create a **Zabbix user** " +"and add **Media** with the **Zammad** type." msgstr "" -#: ../system/variables.rst:125 -msgid "Use ``%a`` for abbreviated name or ``%^A`` for uppercase name" +#: ../system/integrations/zabbix.rst:58 +msgid "" +"For **Send to**: enter any text, as this value is not used, but is required." msgstr "" -#: ../system/variables.rst:126 -msgid "``%B``" +#: ../system/integrations/zabbix.rst:61 +msgid "" +"For more information, use the `Zabbix documentation `_." msgstr "" -#: ../system/variables.rst:127 -msgid "Month name" +#: ../system/maintenance.rst:2 +msgid "Maintenance" msgstr "" -#: ../system/variables.rst:128 -msgid "Use ``%b`` for abbreviated name" +#: ../system/maintenance.rst:4 +msgid "" +"Zammad comes with a maintenance mode that you can use for e.g. updating the " +"instance or changing settings while restricting availability and functions." msgstr "" -#: ../system/variables.rst:129 -msgid "``%U``" +#: ../system/maintenance.rst:13 +msgid "Mode" msgstr "" -#: ../system/variables.rst:130 -msgid "Week number of current year" +#: ../system/maintenance.rst:8 +msgid "The mode setting allows you to enable or disable the maintenance mode." msgstr "" -#: ../system/variables.rst:131 -msgid "Use ``%W`` for a different calculation method" +#: ../system/maintenance.rst:10 +msgid "Defaults to *off*." msgstr "" -#: ../system/variables.rst:134 +#: ../system/maintenance.rst:12 msgid "" -"We support the known format directives for the Ruby built-in method " -"``strftime`` of the ``DateTime`` class. For more information, see `here " -"`_." +"The maintenance mode will restrict access to administrative roles only. This " +"means agents and customers are logged off." msgstr "" -#: ../system/variables/article.rst:2 -msgid "Articles" +#: ../system/maintenance.rst:23 +msgid "@Login" msgstr "" -#: ../system/variables/article.rst:4 ../system/variables/config.rst:4 -#: ../system/variables/current-user.rst:4 ../system/variables/ticket.rst:4 +#: ../system/maintenance.rst:16 msgid "" -"If you're missing variables or are not sure if something is not working as " -"expected, feel free to ask over at the `Community `_." +"This setting allows you to provide a login message within a green banner " +"above the login screen. Click into the green banner in the settings page to " +"adjust your message. To activate the message, activate the *@Login* setting." msgstr "" -#: ../system/variables/article.rst:6 +#: ../system/maintenance.rst:0 msgid "" -"Below you can find all available ticket article-based variables within " -"Zammad. These can be called via Triggers for example. If you're unsure if " -"Zammad does support variables at the point you're at, you can try to type " -"``::`` to check." +"Screenshot showing the default login message within the\n" +"settings page" msgstr "" -#: ../system/variables/article.rst:9 ../system/variables/config.rst:9 -#: ../system/variables/ticket.rst:9 +#: ../system/maintenance.rst:26 msgid "" -"The below list gives you an example what kind of data you can expect, it's " -"not intended to explain the data itself." +"Send an informative message to **all active sessions**. This comes handy to " +"inform your agents e.g. about mayor outages or to force reloads after " +"configuration changes." msgstr "" -#: ../system/variables/article.rst:11 -msgid "Article Variables" +#: ../system/maintenance.rst:31 +msgid "This is the messages title (slightly bigger than the normal message)." msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "name" +#: ../system/maintenance.rst:34 +msgid "The text you want to provide to your logged in sessions." msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "variable" +#: ../system/maintenance.rst:39 +msgid "Reload application" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "example" +#: ../system/maintenance.rst:37 +msgid "" +"Selecting this option will change the message acceptance button from *Close* " +"(with nothing happening) to *Continue session*, which forces the application " +"to reload." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Web" +#: ../system/maintenance.rst:43 +msgid "" +"If you have customers that are logged in to Zammad, they'll also be notified " +"if they're active in that moment." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.web}``" +#: ../system/maintenance.rst:48 +msgid "Example without reload application" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``https://zammad.com`` or empty if not set in user object" +#: ../system/maintenance.rst:52 +msgid "" +"Message setting within Zammad's admin settings without ticket reload " +"application setting." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > VIP" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing the send message settings without ticket\n" +"reload application set" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.vip}``" +#: ../system/maintenance.rst:61 ../system/maintenance.rst:85 +msgid "" +"The modal all other active sessions will see upon pressing *Send to clients*." msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -msgid "``true`` or ``false``" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing modal caused by maintenance's message\n" +"without reload application ticket" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Phone" +#: ../system/maintenance.rst:72 +msgid "Example with reload application" +msgstr "" + +#: ../system/maintenance.rst:76 +msgid "" +"Message setting within Zammad's admin settings with ticket reload " +"application setting." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.phone}``" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing the send message settings with ticket\n" +"reload application set" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``+4930123456789`` or empty if not set in user object" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing modal caused by maintenance's message\n" +"with reload application ticket" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Note" +#: ../system/monitoring.rst:2 +msgid "Monitoring" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.note}``" +#: ../system/monitoring.rst:4 +msgid "" +"This function is only available in self hosted instances. If you use Zammad " +"in our cloud, we are monitoring the system on our own and take steps to fix " +"potential problems directly." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Some note about user`` or empty if not set in user object" +#: ../system/monitoring.rst:11 +msgid "" +"On the monitoring page, you can see the current health state of Zammad under " +"\"*Current Status*\" at the bottom. This can be useful if you want to have a " +"look if everything is up and running. As an example, you could have a look " +"in the monitoring when you assume that some emails aren't processed from " +"Zammad." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Mobile" +#: ../system/monitoring.rst:17 +msgid "**Can't receive an email and the monitoring response is \"healthy\"?**" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.mobile}``" +#: ../system/monitoring.rst:19 +msgid "" +"Zammad will just inform you about unprocessable emails. This is not the case " +"for oversized emails. You can adjust the maximum email size in :doc:`../" +"channels/email/settings`." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Login" +#: ../system/monitoring.rst:24 +msgid "Monitoring API" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.login}``" +#: ../system/monitoring.rst:26 +msgid "" +"Beside the indication in the monitoring page, you can also use an external " +"monitoring tool to monitor Zammad's health. To request the health of Zammad, " +"you need to provide the API key (token) to the external monitoring tool. You " +"can copy the token from the \"*Current Token*\" field as well as the whole " +"API endpoint of your system (\"*Health Check*\" field), in which the API " +"token is already included." msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -#: ../system/variables/ticket.rst:1 -msgid "``jdoe``" +#: ../system/monitoring.rst:37 +msgid "Screenshot showing Current Token and Health Check" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Lastname" +#: ../system/monitoring.rst:37 +msgid "Screenshot showing Token and Health Check" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.lastname}``" +#: ../system/monitoring.rst:39 +msgid "" +"In addition to that, you can reset the auto-generated token to make sure " +"that already configured monitoring systems won't work anymore. So, please " +"use this \"*Reset*\" button only if you know what you do!" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -#: ../system/variables/ticket.rst:1 -msgid "``Doe`` or empty if not set" +#: ../system/monitoring.rst:44 +#, fuzzy +msgid "Example Output" +msgstr "Пример" + +#: ../system/monitoring.rst:0 +msgid "No issues found" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Firstname" +#: ../system/monitoring.rst:48 ../system/monitoring.rst:60 +msgid "**Indicator in Zammad**:" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.firstname}``" +#: ../system/monitoring.rst:0 +msgid "Screenshot showing monitoring with no issues" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "``Joe`` or empty if not set" +#: ../system/monitoring.rst:54 ../system/monitoring.rst:66 +msgid "**API response**::" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Fax" +#: ../system/monitoring.rst:0 +msgid "Issues were found" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.fax}``" +#: ../system/monitoring.rst:0 +msgid "Screenshot showing monitoring with issues" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Email" +#: ../system/objects.rst:2 +msgid "Objects" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.email}``" +#: ../system/objects.rst:4 +msgid "" +"In Zammad you can add your own fields to tickets, users, organizations and " +"even groups (these are called \"objects\"). This can be useful if you need " +"to add further information to a ticket or any other object in Zammad and the " +"information doesn't fit in any existing field." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``jdoe@example.com``" +#: ../system/objects.rst:11 +msgid "" +"Try to avoid deleting attributes (and disable them instead) as Zammad might " +"run into unexpected conditions if they are referenced somewhere." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Department" +#: ../system/objects.rst:16 +msgid "" +"Here's an overview of object attributes. On the upper right you can add new " +"attributes. By default, there will be no custom fields - standard attributes " +"will be grayed out, you can't delete or change those. You can edit custom " +"attributes (they are displayed in black font and have a trash bin on the " +"right side) just by clicking on them." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.department}``" +#: ../system/objects.rst:24 +msgid "" +"Attributes you add to Zammad, no matter if they have default values or not, " +"will not update existing information. This means a new ticket field " +"technically will be empty unless you populate it." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Sales`` or empty if not set in user object" +#: ../system/objects.rst:28 +msgid "" +"Especially in ticket scope this also means that newly added attributes will " +"be indicated as \"changed\" to agents that view the ticket. This may " +"interfere with Zammad's tabs behavior." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Address" +#: ../system/objects.rst:40 +msgid "Ordering Attributes" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.address}``" +#: ../system/objects.rst:42 +msgid "" +"Since Zammad introduced :doc:`/system/core-workflows` the need to have a " +"custom positioning for attributes has become more important than ever." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Some street 1, 12345 Berlin`` or empty if not set in user object" +#: ../system/objects.rst:45 +msgid "" +"To adjust the position of such an attribute, simply click on the attribute " +"entry in question, scroll down and adjust the position number. Please note " +"that you cannot change the positioning of default attributes." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated" +#: ../system/objects.rst:49 +msgid "" +"In case two attributes have the same position value, Zammad will sort " +"alphabetically by name automatically." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_at}``" +#: ../system/objects.rst:None +msgid "" +"Screenshot showing custom attribute entries ordered in between default ones" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``2019-10-08 15:24:47 UTC``" +#: ../system/objects.rst:56 +msgid "Updating Database After Adding or Editing Attributes" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Type > Name" +#: ../system/objects.rst:58 +msgid "" +"When adding or changing attributes, Zammad will not apply the changes " +"instantly, but instead shows you the changed attributes first. If you're " +"ready to go, just click on \"Update database\" to apply the changes to " +"Zammad. If you made a mistake or just want to discard your changes, click " +"\"Discard changes\"." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.type.name}``" +#: ../system/objects.rst:64 +msgid "" +"After applying the changes with \"Update Database\", a restart of Zammad is " +"**mandatory**. If you don't perform it, you may experience unexpected " +"behavior or even errors. You may want to do this kind of configuration " +"during maintenance windows." msgstr "" -#: ../system/variables/article.rst:1 +#: ../system/objects.rst:72 msgid "" -"``email`` (`list of article types `_)" +"Changes on objects require you to update the database to apply these changes." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > To" +#: ../system/objects.rst:75 +msgid "**🤓 Service restarts can be automated**" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.to}``" +#: ../system/objects.rst:0 +msgid "Hosted environments automatically restart for you." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``helpdesk@example.com``" +#: ../system/objects.rst:0 +msgid "" +"If you're using a self-hosted installation you can use :docs:`environment " +"variables `" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > TicketID" +#: ../system/objects.rst:82 +msgid "System Attributes" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.ticket_id}``" +#: ../system/objects.rst:84 +msgid "" +"Zammad comes with pre-configured attributes. Some of them can't be edited " +"via UI (or at all). This is required for proper operation of Zammad and not " +"a bug." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``1`` (not ticket number)" +#: ../system/objects.rst:90 +msgid "Ticket State" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Subject" +#: ../system/objects.rst:92 +msgid "" +"If the pre-configured states aren't enough for you or you want to change " +"them, you can do so by clicking on the cogwheel icon in the state row in the " +"ticket tab. But you should be careful when changing pre-configured states. " +"This can lead to unwanted behavior in some cases." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.subject}``" +#: ../system/objects.rst:None +msgid "Screenshot showing highlighted ticket state attribute" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``My amazing subject``" +#: ../system/objects.rst:122 +msgid "Handling of states" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Sender > Name" +#: ../system/objects.rst:102 +msgid "" +"In the state configuration screen, you can add new states, disable states or " +"change states." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.sender.name}``" +#: ../system/objects.rst:0 +msgid "Screenshot showing table of default ticket states" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Customer``, ``Agent`` or ``System``" +#: ../system/objects.rst:110 +msgid "" +"To add a new state, click on the \"New Ticket State\" button in the top " +"right corner. To change an existing state, simply click on the affected " +"state. This opens an edit dialog." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Visibility" +#: ../system/objects.rst:114 +msgid "" +"You can also clone a state or set them to \"Default for new tickets\" or " +"\"Default for follow-ups\" by clicking on the ⁝ action button and select the " +"desired function." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.internal}``" +#: ../system/objects.rst:118 +msgid "" +"*Default for new tickets* means that this state is used for every newly " +"created ticket." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``false`` or ``true`` (false if not internal)" +#: ../system/objects.rst:121 +msgid "" +"*Default for follow-ups* means that this state is used if the ticket is re-" +"opened after it was closed." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > From" +#: ../system/objects.rst:171 +msgid "Ticket state in detail" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.from}``" +#: ../system/objects.rst:125 +msgid "" +"Below you can find a description for each field and option. Please head over " +"to the :ref:`example ` to see the edit dialog." msgstr "" -#: ../system/variables/article.rst:1 +#: ../system/objects.rst:129 msgid "" -"``Joe Doe `` may differ, depends on ``FROM`` of send mail" +"This is the name of the state and what you and your agents are seeing when " +"choosing a state somewhere (e.g. in tickets, trigger configuration)." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Web" +#: ../system/objects.rst:137 +msgid "" +"There are different state types you can choose from. By default, Zammad " +"comes with one state per state type." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.web}``" +#: ../system/objects.rst:140 +msgid "" +"**new**: for states for tickets that are new and it hasn't been worked on " +"them" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > VIP" +#: ../system/objects.rst:142 +msgid "" +"**open**: for states for tickets that are in progress and agents are working " +"on them" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.vip}``" +#: ../system/objects.rst:144 +msgid "**merged**: for states for tickets that are merged with other tickets" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Phone" +#: ../system/objects.rst:145 +msgid "" +"**pending reminder**: for states for tickets that are in progress and you " +"want to set a reminder. (default example: *pending reminder*)" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.phone}``" +#: ../system/objects.rst:147 +msgid "" +"**pending action**: for states for tickets that are waiting for a specified " +"time and then change their state (default example: *pending close*)" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Note" +#: ../system/objects.rst:150 +msgid "" +"**closed**: for states for tickets that are finished and do not need to be " +"processed further" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.note}``" +#: ../system/objects.rst:153 +msgid "" +"⚠️ Choosing the correct state type is important! If you are in doubt, have a " +"look on the default states and their types!" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Mobile" +#: ../system/objects.rst:158 +msgid "Ignore escalation" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.mobile}``" +#: ../system/objects.rst:157 +msgid "" +"Here you can define whether tickets of this state will count to escalation " +"time or not." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Login" +#: ../system/objects.rst:161 +msgid "" +"You can create a note for the state to inform other admins about the state. " +"This has no effect on tickets." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.login}``" +#: ../system/objects.rst:165 +msgid "Set the state to *active* or *inactive*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Lastname" +#: ../system/objects.rst:167 +msgid "" +"it is technically possible to set all states to inactive. To keep Zammad " +"working in such a case, the inactive flag of one of the states is ignored." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.lastname}``" +#: ../system/objects.rst:194 +msgid "Ticket state example" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Firstname" +#: ../system/objects.rst:174 +msgid "" +"Let's assume we want to create a new state which indicates that the ticket " +"has to wait for a response of a third party (e.g. service contractor or " +"manufacturer) and we want to to be able to set a reminder." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.firstname}``" +#: ../system/objects.rst:178 +msgid "" +"First we give the new state a proper name. In this example we call it " +"\"waiting for manufacturer\"." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Fax" +#: ../system/objects.rst:181 +msgid "" +"As state type we choose \"pending reminder\". This indicates that the ticket " +"is still open and we can set a reminder. This reminder can be useful if our " +"manufacturer sometimes isn't responding or we want to remind him to give us " +"an answer." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.fax}``" +#: ../system/objects.rst:186 +msgid "" +"We choose \"no\" for \"ignore escalation\" because we want to escalate the " +"tickets even if we are waiting on the manufacturer's feedback." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Email" +#: ../system/objects.rst:189 +msgid "The **result** in the creation dialog will look like this:" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.email}``" +#: ../system/objects.rst:0 +msgid "Screenshot showing ticket state creation dialog with example" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Department" +#: ../system/objects.rst:199 +msgid "Ticket Priority" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.department}``" +#: ../system/objects.rst:201 +msgid "" +"If the pre-configured priorities aren't enough for you or you want to change " +"them, you can do so by clicking on the cogwheel icon in the priority row in " +"the ticket tab:" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Address" +#: ../system/objects.rst:None +msgid "Screenshot showing highlighted ticket priority attribute" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.address}``" +#: ../system/objects.rst:226 +msgid "Handling of priorities" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created" +#: ../system/objects.rst:210 +msgid "" +"In the priority configuration screen, you can add new priorities, disable " +"priorities or change priorities." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_at}``" +#: ../system/objects.rst:0 +msgid "Screenshot showing table of default ticket priorities" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Cc" +#: ../system/objects.rst:218 +msgid "" +"To add a new priority, click on the \"New Priority\" button in the top right " +"corner. To change an existing priority, simply click on the affected " +"priority. This opens an edit dialog." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.cc}``" +#: ../system/objects.rst:222 +msgid "" +"You can also clone a priority or set them to \"Default for new tickets\" by " +"clicking on the ⁝ action button and select the desired function." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``jdoe@example.com, company@example.com``" +#: ../system/objects.rst:225 +msgid "" +"*Default for new tickets* means that this priority is used for every newly " +"created ticket." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Text" +#: ../system/objects.rst:248 +msgid "Priorities in detail" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.body}``" +#: ../system/objects.rst:229 +msgid "Below you can find a description for each field and option." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Test`` without formatting (plain)" +#: ../system/objects.rst:232 +msgid "" +"This is the name of the priority and what you and your agents are seeing " +"when choosing a priority somewhere (e.g. in tickets, trigger configuration)." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article Text as HTML (not referenced)" +#: ../system/objects.rst:242 +msgid "Highlight color" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.body_as_html}``" +#: ../system/objects.rst:237 +msgid "" +"Switch between *Low priority* (light blue), *High priority* (red) and - " +"(default). This affects the displayed color for ticket titles in overviews." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Test`` with formatting" +#: ../system/objects.rst:241 +msgid "The color options are currently limited to the mentioned options." msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "Ticket > Article#" +#: ../system/objects.rst:245 +msgid "" +"You can create a note for the priority to inform other admins about the " +"priority. This has no effect on tickets." msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "``#{ticket.article_count}``" +#: ../system/objects.rst:249 +msgid "Set the priority to *active* or *inactive*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``1`` number of ticket articles" +#: ../system/objects/external-data-source-example.rst:2 +msgid "External Data Source" msgstr "" -#: ../system/variables/config.rst:2 -msgid "Config" +#: ../system/objects/external-data-source-example.rst:4 +msgid "" +"We assume you already had a look on :doc:`types` where you can find a " +"description of the individual fields." msgstr "" -#: ../system/variables/config.rst:6 +#: ../system/objects/external-data-source-example.rst:7 msgid "" -"Below you'll find config related variables. These hold useful configuration " -"information that you can use within e.g. triggers to show necessary " -"information to your customer." +"To reproduce this example, choose a category you want to add a custom field, " +"click on *New Attribute* and select *External data source field* under " +"*Format*." msgstr "" -#: ../system/variables/config.rst:11 -msgid "Config Variables" +#: ../system/objects/external-data-source-example.rst:11 +msgid "" +"Our example story is to fetch data from an external product database. We " +"want to add our products to the tickets so that the products can be searched " +"and chosen from a list and also create a link to the product website." msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Fully Qualified Domain Name" +#: ../system/objects/external-data-source-example.rst:16 +msgid "Base configuration" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.fqdn}``" +#: ../system/objects/external-data-source-example.rst:None +msgid "Initial steps to configure external data source object type" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``zammad.example.com``" +#: ../system/objects/external-data-source-example.rst:25 +msgid "Name: *product*" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Ticket Hook" +#: ../system/objects/external-data-source-example.rst:26 +msgid "Display: *Product*" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.ticket_hook}``" +#: ../system/objects/external-data-source-example.rst:29 +msgid "External data source configuration" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``Ticket#``" +#: ../system/objects/external-data-source-example.rst:31 +msgid "" +"First, enter the search URL making sure it contains ``#{search.term}`` as a " +"parameter:" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > HTTP type" +#: ../system/objects/external-data-source-example.rst:34 +msgid "**Example:** ``https://dummyjson.com/products/search?q=#{search.term}``" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.http_type}``" +#: ../system/objects/external-data-source-example.rst:36 +msgid "" +"After that, head down to the preview section and enter a search input for " +"the external data source." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``https`` or ``http``" +#: ../system/objects/external-data-source-example.rst:39 +msgid "**Example:** ``mac``" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > SystemID" +#: ../system/objects/external-data-source-example.rst:41 +msgid "Then you can find a preview of the response data below:" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.system_id}``" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of JSON response based on search term" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``31`` (value between 1 and 99)" +#: ../system/objects/external-data-source-example.rst:48 +msgid "" +"We recommend using the preview to have a look on the structure. There is a " +"top-level element called ``products``. One level below, you can find the " +"attributes ``id`` and ``title``." msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Organization" +#: ../system/objects/external-data-source-example.rst:52 +msgid "**Search result response based on search from example:**" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.organization}``" +#: ../system/objects/external-data-source-example.rst:119 +msgid "" +"To tell the remote system that the desired data is located below the " +"``products`` level, you have to put it in the field *Search result list key*." msgstr "" -#: ../system/variables/config.rst:1 +#: ../system/objects/external-data-source-example.rst:122 msgid "" -"``Zammad GmbH`` value set in `Branding `_" +"After inserting ``products`` in the mentioned field, you get an extended " +"preview. You can find an additional box *Search result list* with a JSON " +"structure. This is the same response as before but stripped from the upper " +"``products`` element by the external data source." msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Product Name" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of JSON response search result list" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.product_name}``" +#: ../system/objects/external-data-source-example.rst:132 +msgid "" +"Now you need to provide the keys for the search result values and labels. As " +"already mentioned, we are looking for the ``id`` and the ``title`` of our " +"products. If you haven't already, it is now a good time to look at the " +"preview of the *Search result list*." msgstr "" -#: ../system/variables/config.rst:1 +#: ../system/objects/external-data-source-example.rst:197 msgid "" -"``Helpdesk`` value set in `Branding `_" +"After locating our two keys, we insert them in *search result value key* " +"(``id``) and in *Search result label key* (``title``)." msgstr "" -#: ../system/variables/current-user.rst:2 -msgid "Current User" +#: ../system/objects/external-data-source-example.rst:200 +msgid "" +"Basically, we configured the external data source already and we can see a " +"table in the preview section:" +msgstr "" + +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of product table based on search term" msgstr "" -#: ../system/variables/current-user.rst:6 +#: ../system/objects/external-data-source-example.rst:208 msgid "" -"Current user variables always return values of the current user that caused " -"e.g. a trigger to run." +"According to our example story, now just the *Link template* is missing." msgstr "" -#: ../system/variables/current-user.rst:8 +#: ../system/objects/external-data-source-example.rst:210 msgid "" -"Due to the above fact, these variables are often not (yet) set or available " -"for usage." +"Please note that this is an optional feature. If you don't want to use such " +"links, of course you don't have to configure it." msgstr "" -#: ../system/variables/current-user.rst:10 +#: ../system/objects/external-data-source-example.rst:213 msgid "" -"In situations where e.g. schedulers or triggers run, this most likely is " -"nothing you want to use." +"We can add now an address where additional product information can be found." msgstr "" -#: ../system/variables/current-user.rst:13 -msgid "Current User Variables" +#: ../system/objects/external-data-source-example.rst:215 +msgid "Example: ``https://your_domain.com/q=#{ticket.product}``" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Web" +#: ../system/objects/external-data-source-example.rst:217 +msgid "In the example, the parameter means:" +msgstr "" + +#: ../system/objects/external-data-source-example.rst:219 +msgid "``#{}``: \"Frame\" for the insertion of information" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.web}``" +#: ../system/objects/external-data-source-example.rst:220 +msgid "``ticket``: object level, where you create your custom object" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``https://zammad.org`` or empty if not set" +#: ../system/objects/external-data-source-example.rst:221 +msgid "``product``: name of the (custom) object" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > VIP" +#: ../system/objects/external-data-source-example.rst:223 +msgid "" +"After configuring your *Link template*, there will be another column in the " +"preview. Hovering on the icons in the *Link* column will show you where it " +"forwards you." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.vip}``" +#: ../system/objects/external-data-source-example.rst:232 +msgid "" +"In our example, one of the links looks like: https://your_domain.com/q=6, " +"where the 6 is the product id." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``false`` or ``true``" +#: ../system/objects/external-data-source-example.rst:235 +msgid "You can find more information regarding the URL in :doc:`types`." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Web" +#: ../system/objects/includes/adding-values-hint.include.rst:3 +msgid "" +"Adding values can be tricky for first timers, don't forget to press \"➕ " +"Add\" after typing your values. Otherwise you may loose a value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.web}``" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:1 +#: ../system/objects/includes/reposition-values.include.rst:1 +msgid "**↕️ This field type allows the positioning of its values ↔️**" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > VIP" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:3 +msgid "" +"In order to re-arrange the field values, first edit the field. Then you can " +"use ☰ to drag the values in question to the correct position. If you want to " +"change the layer depth, double click on ☰. With it you can cycle through the " +"available layers." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.vip}``" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:8 +msgid "When you're ready, submit your changes to save the object attribute." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Phone" +#: :0 ../system/objects/types.rst:0 +msgid "" +"Screencast showing how to re-position values on tree select like\n" +"fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.phone}``" +#: ../system/objects/includes/reposition-values.include.rst:3 +msgid "" +"In order to re-arrange the field values, edit the field and scroll below the " +"values. Make sure to tick the option \"Use custom option sort\"." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``004930123456789`` or empty if not set" +#: ../system/objects/includes/reposition-values.include.rst:8 +msgid "" +"If you do not tick this field, all manual positioning you did above will be " +"lost upon saving! ☠️" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Note" +#: ../system/objects/includes/reposition-values.include.rst:11 +msgid "" +"Now use ☰ to drag the values in question to the correct position. When " +"you're ready, submit your changes to save the object attribute." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.note}``" +#: :0 ../system/objects/types.rst:0 +msgid "Screencast showing how to re-position values" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Some note to this user`` or empty if not set" +#: ../system/objects/includes/url-template-hint.include.rst:3 +msgid "" +"This field allows using :ref:`URL fields (Link Templates) `." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Mobile" +#: ../system/objects/permissions.rst:2 +msgid "Attribute Permissions" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.mobile}``" +#: ../system/objects/permissions.rst:7 +msgid "" +"In the object attributes configuration you can define if a field is shown " +"and if the input in the field is mandatory, separated by different screens " +"and for different :doc:`roles/permissions `." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``0049176123456789`` or empty if not set" +#: ../system/objects/permissions.rst:17 +msgid "Screenshot shows object attribute permission table" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Login" +#: ../system/objects/permissions.rst:17 +msgid "" +"Some of the possible permissions and screen options for a user object " +"attribute." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.login}``" +#: ../system/objects/permissions.rst:19 +msgid "" +"Based on the object context (ticket, agent, organization, user), the " +"selectable roles (to be precise: the required permissions) and screens " +"differ. Be aware that these settings aren't affecting data creation via " +"other channels than the UI." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Lastname" +#: ../system/objects/permissions.rst:24 +msgid "" +"If you want to have further customization possibilities, you should have a " +"look at the :doc:`core workflows `." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.lastname}``" +#: ../system/objects/permissions.rst:28 +msgid "Screens" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Firstname" +#: ../system/objects/permissions.rst:30 +msgid "" +"In the table below you can find an overview about the different permissions " +"and the available screens Zammad distinguishes between." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.firstname}``" +#: ../system/objects/permissions.rst:37 +msgid "Screen" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``John`` or empty if not set" +#: ../system/objects/permissions.rst:38 +msgid "Available for" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Fax" +#: ../system/objects/permissions.rst:40 +msgid "create" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.fax}``" +#: ../system/objects/permissions.rst:41 ../system/objects/permissions.rst:52 +#: ../system/objects/permissions.rst:59 ../system/objects/permissions.rst:73 +msgid "admin.user" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``004930123464789`` or empty if not set" +#: ../system/objects/permissions.rst:42 ../system/objects/permissions.rst:53 +#: ../system/objects/permissions.rst:60 +msgid "admin.organization" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Email" +#: ../system/objects/permissions.rst:43 ../system/objects/permissions.rst:54 +#: ../system/objects/permissions.rst:61 +msgid "admin.group" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.email}``" +#: ../system/objects/permissions.rst:44 +msgid "Creation dialog for not yet existing data" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``jdoe@customer.tld``" +#: ../system/objects/permissions.rst:45 +msgid "create_middle" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Department" +#: ../system/objects/permissions.rst:46 ../system/objects/permissions.rst:50 +#: ../system/objects/permissions.rst:57 ../system/objects/permissions.rst:66 +#: ../system/objects/permissions.rst:70 +#, fuzzy +msgid "ticket.customer" +msgstr "Макрос заявки" + +#: ../system/objects/permissions.rst:47 ../system/objects/permissions.rst:51 +#: ../system/objects/permissions.rst:58 ../system/objects/permissions.rst:69 +#, fuzzy +msgid "ticket.agent" +msgstr "Макрос заявки" + +#: ../system/objects/permissions.rst:48 +msgid "Ticket create dialog (middle section)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.department}``" +#: ../system/objects/permissions.rst:49 +msgid "edit" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Sales`` or empty if not set" +#: ../system/objects/permissions.rst:55 +msgid "Editing dialog for already existing data" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Avatar" +#: ../system/objects/permissions.rst:56 +msgid "view" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.avatar(60,60)}``" +#: ../system/objects/permissions.rst:62 +msgid "View-only dialog for already existing data" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "avatar picture with width and height in pixel (e.g. 60,60)" +#: ../system/objects/permissions.rst:64 +msgid "(e.g. user or organization from search)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Address" +#: ../system/objects/permissions.rst:65 +msgid "signup" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.address}``" +#: ../system/objects/permissions.rst:67 +msgid "Sign-up screen for new customers" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Some street 1, 12345 Berlin`` or empty if not set" +#: ../system/objects/permissions.rst:68 +msgid "invite_customer" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated at" +#: ../system/objects/permissions.rst:71 +msgid "" +"Customer invitation screen (from :doc:`First Steps ` area)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_at}``" +#: ../system/objects/permissions.rst:72 +msgid "invite_agent" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC``" +#: ../system/objects/permissions.rst:74 +msgid "" +"Agent invitation screen (from :doc:`First Steps ` area)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Phone" +#: ../system/objects/permissions.rst:78 +msgid "Screen Options" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.phone}``" +#: ../system/objects/permissions.rst:80 +msgid "" +"For the different screens you can select \"show\" and \"required\" options." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Shared organization" +#: ../system/objects/permissions.rst:82 +msgid "**shown:** Show (check) or hide (uncheck) a field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.shared}``" +#: ../system/objects/permissions.rst:83 +msgid "" +"**required:** Set a field to mandatory (check). Forces users (via UI and " +"API) to populate the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Note" +#: ../system/objects/types.rst:7 +msgid "Example external data source" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.note}``" +#: ../system/objects/types.rst:2 +msgid "Attribute types" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``A note to the organization of the user`` or empty if not set" +#: ../system/objects/types.rst:4 +msgid "" +"When adding a new object attribute, you can choose between the following " +"attribute types." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Name" +#: ../system/objects/types.rst:14 +msgid "" +"You cannot change the attribute format / type as soon as it is applied. If " +"you no longer need an object attribute, consider disabling it instead of " +"removing." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.name}``" +#: ../system/objects/types.rst:18 +msgid "**What about the translation of my attributes?**" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``Zammad GmbH``" +#: ../system/objects/types.rst:20 +msgid "" +"For some attribute types you can decide if they should be translatable or " +"not. To be precise, it works only for the selectable fields because the " +"possible choices are known and limited. For the following attribute types, " +"you can set the translatable flag:" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Domain based assignment" +#: ../system/objects/types.rst:25 +msgid "*Boolean field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.domain_assignment}``" +#: ../system/objects/types.rst:26 +msgid "*Single selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Domain" +#: ../system/objects/types.rst:27 +msgid "*Multiple selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.domain}``" +#: ../system/objects/types.rst:28 +msgid "*Single tree selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``zammad.com`` or empty if not set" +#: ../system/objects/types.rst:29 +msgid "*Multiple tree selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > VIP" +#: ../system/objects/types.rst:31 +msgid "" +"For these types, you can find an additional field *Translate field contents*:" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.vip}``" +#: ../system/objects/types.rst:0 +msgid "Screenshot showing translatable attribute types" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Note" +#: ../system/objects/types.rst:38 +msgid "Screenshot with example of translatable attribute type" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.note}``" +#: ../system/objects/types.rst:45 +msgid "Boolean field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Mobile" +#: ../system/objects/types.rst:41 +msgid "" +"Provides a drop-down field with display values for ``true`` and ``false``. " +"Setting a default is mandatory." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.mobile}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Boolean fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Login" +#: ../system/objects/types.rst:55 +msgid "Date field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.login}``" +#: ../system/objects/types.rst:48 +msgid "Provides a date picker field and does not allow default values." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Lastname" +#: ../system/objects/types.rst:52 +msgid "Default time diff (hours)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.lastname}``" +#: ../system/objects/types.rst:51 +msgid "" +"This setting helps the user by highlighting the day from now plus the " +"provided value. It *does not* pre-fill the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Firstname" +#: ../system/objects/types.rst:0 +msgid "Available settings for Date fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.firstname}``" +#: ../system/objects/types.rst:73 +msgid "Date & time field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Fax" +#: ../system/objects/types.rst:58 +msgid "Provides a date and time picker – does not allow default values" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.fax}``" +#: ../system/objects/types.rst:62 +msgid "Allow future" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Email" +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the future." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.email}``" +#: ../system/objects/types.rst:66 +msgid "Allow past" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Department" +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the past." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.department}``" +#: ../system/objects/types.rst:70 +msgid "Default time diff (minutes)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Web" +#: ../system/objects/types.rst:69 +msgid "" +"This setting helps the user by highlighting the day from now plus the " +"provided value. It does not pre-fill the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.web}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Date & time fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > VIP" +#: ../system/objects/types.rst:86 +msgid "Integer field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.vip}``" +#: ../system/objects/types.rst:76 +msgid "" +"Provides an input field that allows integer usage only. You may define a " +"default value. You cannot enforce comma separation." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Phone" +#: ../system/objects/types.rst:80 +msgid "Minimal" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.phone}``" +#: ../system/objects/types.rst:80 +msgid "The minimal value the field accepts." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Note" +#: ../system/objects/types.rst:83 +msgid "Maximal" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.note}``" +#: ../system/objects/types.rst:83 +msgid "The maximum value the field accepts." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Mobile" +#: ../system/objects/types.rst:0 +msgid "Available settings for Integer fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.mobile}``" +#: ../system/objects/types.rst:99 +msgid "Multiple selection field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Login" +#: ../system/objects/types.rst:89 +msgid "" +"Provides a selection field that allows the selection of one or more out of " +"several. This field does allow setting a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.login}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Multiple selection fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Lastname" +#: ../system/objects/types.rst:112 +msgid "Single selection field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.lastname}``" +#: ../system/objects/types.rst:102 +msgid "" +"Provides a drop-down field that allows selection of one value out of " +"several. This field does allow setting a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Firstname" +#: ../system/objects/types.rst:0 +msgid "Available settings for Single selection fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.firstname}``" +#: ../system/objects/types.rst:142 +msgid "Textarea field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Fax" +#: ../system/objects/types.rst:115 +msgid "" +"Provides a text area input field (multiple lines) and thus allows e.g. new " +"lines. You can set a default field value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.fax}``" +#: ../system/objects/types.rst:120 +msgid "" +"Please note that this field *does not* support text formatting or HTML " +"content (rich text)." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Email" +#: ../system/objects/types.rst:123 +msgid "**🥵 This field can consume a lot of visual space**" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.email}``" +#: ../system/objects/types.rst:125 +msgid "" +"Depending on where you use this field type, it may use a lot of visual space " +"if you provide a lot of text. This may be an issue to work with." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Department" +#: ../system/objects/types.rst:130 +msgid "Default" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.department}``" +#: ../system/objects/types.rst:129 +msgid "" +"The here provided text will be shown within the text area field or new data " +"sets." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Avatar" +#: ../system/objects/types.rst:134 ../system/objects/types.rst:160 +msgid "Maxlength" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.avatar(60,60)}``" +#: ../system/objects/types.rst:0 ../system/objects/types.rst:160 +msgid "You can pick the maximum length of the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Address" +#: ../system/objects/types.rst:0 +msgid "The default length of this object is ``500``." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.address}``" +#: ../system/objects/types.rst:139 +msgid "Rows" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created at" +#: ../system/objects/types.rst:0 +msgid "" +"Change the number of rows to dislay so that you can use only the space you " +"really need." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_at}``" +#: ../system/objects/types.rst:0 +msgid "The default number of rows is ``4``." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Avatar" +#: ../system/objects/types.rst:0 +msgid "Available settings for Textarea fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.avatar(60,60)}``" +#: ../system/objects/types.rst:165 +msgid "Text field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Address" +#: ../system/objects/types.rst:145 +msgid "Provides a text field (one line) and allows choosing a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.address}``" +#: ../system/objects/types.rst:148 +msgid "" +"Defines the type of the input field. This allows e.g. your browser to ensure " +"that you provide the specific type." msgstr "" -#: ../system/variables/ticket.rst:6 -msgid "" -"Below you can find all available ticket-based variables within Zammad. These " -"can be called via Triggers for example. If you're unsure if Zammad does " -"support variables at the point you're at, you can try to type ``::`` to " -"check." +#: ../system/objects/types.rst:152 +msgid "Currently available:" msgstr "" -#: ../system/variables/ticket.rst:12 -msgid "Ticket Variables" +#: ../system/objects/types.rst:155 +msgid "Phone" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Web" +#: ../system/objects/types.rst:156 +msgid "Text" +msgstr "Текст" + +#: ../system/objects/types.rst:157 +msgid "Url *(URL fields disable link-template availability)*" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.web}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Text fields" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > VIP" +#: ../system/objects/types.rst:174 +msgid "Single tree selection field" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.vip}``" +#: ../system/objects/types.rst:168 +msgid "" +"Provides a select-like field with up to 6 layers of options. Does not allow " +"setting a default value." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Phone" +#: ../system/objects/types.rst:0 +msgid "Available settings for Tree Select fields" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.phone}``" +#: ../system/objects/types.rst:183 +msgid "Multiple tree selection field" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Note" +#: ../system/objects/types.rst:177 +msgid "" +"Provides a select-like field with up to 6 layers of options allowing the " +"selection of multiple values. Does not allow setting a default value." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.note}``" +#: ../system/objects/types.rst:302 +msgid "External Data Source field" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Mobile" +#: ../system/objects/types.rst:186 +msgid "" +"Provides a searchable field which fetches data from an external system. This " +"can be useful if you have data outside of Zammad and don't want to maintain " +"both data sources." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.mobile}``" +#: ../system/objects/types.rst:190 +msgid "The feature works as follows:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Login" +#: ../system/objects/types.rst:192 +msgid "" +"Zammad sends a query with a search string (free text from agent or based on " +"a variable) in a pre-defined format (\"Search URL\") to an external system." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.login}``" +#: ../system/objects/types.rst:195 +msgid "" +"This external system searches for matches and provides a response as a JSON " +"structure to Zammad." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Lastname" +#: ../system/objects/types.rst:197 +msgid "" +"Zammad just looks for the defined list and value keys, reads the content and " +"displays the value to the user. There is no search on Zammad side." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.lastname}``" +#: ../system/objects/types.rst:201 +msgid "" +"The usage of a PostgreSQL database for Zammad is required. In any other " +"case, Zammad will hide the external data source type and you are not able to " +"use it. If you want to use this feature, consider to :docs:`migrate your " +"database `." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Firstname" +#: ../system/objects/types.rst:205 +msgid "Currently, only ``GET`` is supported as request method." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.firstname}``" +#: ../system/objects/types.rst:206 +msgid "" +"The data structure must be in JSON format and provide the objects in an " +"array." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Fax" +#: ../system/objects/types.rst:208 +msgid "" +"The endpoint for the external data source has to support search. On Zammad " +"side, there is no search/logic implemented; however, you can define the " +"output key and value based on the result(s) from the response (which " +"provides already filtered content based on the search)." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.fax}``" +#: ../system/objects/types.rst:212 +msgid "" +"If you receive more results as expected, your external data source search " +"may not work properly or the structure of the URL is not correct. You should " +"get in touch with a responsible person from the external system." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Email" +#: ../system/objects/types.rst:217 +msgid "" +"Please have a look :doc:`at our example `, where you can find a possible configuration for a public " +"dummy endpoint." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.email}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for external data source fields" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Department" +#: ../system/objects/types.rst:242 +msgid "Search URL" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.department}``" +#: ../system/objects/types.rst:227 +msgid "" +"Set your endpoint where Zammad fetches the data. Please make sure to include " +"a valid search :doc:`variable ` as an URL parameter. " +"Example for a free text search at user input: ``#{search.term}``" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Avatar" +#: ../system/objects/types.rst:232 +msgid "" +"If in doubt, ask the responsible person for the external data source how " +"they expect the structure of the URL." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.avatar(60,60)}``" +#: ../system/objects/types.rst:236 +msgid "" +"Depending on your search variable, the preview might work or not. The reason " +"is that the context might not be available and it is no bug." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Address" +#: ../system/objects/types.rst:239 +msgid "" +"Please also make sure to use a variable which is available in your object " +"context. For example you won't be able to search for a ticket in a user " +"object context." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.address}``" +#: ../system/objects/types.rst:252 +msgid "SSL Verification" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated at" +#: ../system/objects/types.rst:245 +msgid "Here you can switch the SSL verification to no." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_at}``" +#: ../system/objects/types.rst:249 +msgid "" +"If your external data source system is using self signed certificates, " +"please have a look :doc:`here ` for " +"further information about how to handle them in Zammad, so you can keep the " +"SSL verification activated." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Title" +#: ../system/objects/types.rst:258 +msgid "HTTP Authentication" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.title}``" +#: ../system/objects/types.rst:255 +msgid "" +"If your external data source requires an authentication, you can set it " +"here. You can leave it empty or choose between *Basic Authentication* or " +"*Authentication Token* (selecting one of the two methods leads to additional " +"fields where you can enter your credentials/token)." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "" -"``My amazing Subject`` (normally subject, can be edited within Interface and " -"thus differ)" +#: ../system/objects/types.rst:265 +msgid "Search result list key" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Accounted Time" +#: ../system/objects/types.rst:261 +msgid "" +"Defines the level in the JSON structure which provides the list with search " +"results. You can leave it empty, if the data is already provided as an " +"array. If you have to go deeper in the structure, you can provide a path " +"with ``.`` as separators, e.g. ``key.subkey.sub-sub-key``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.time_unit}``" +#: ../system/objects/types.rst:271 +msgid "Search result value key" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``1``, ``2.75`` or empty response" +#: ../system/objects/types.rst:268 +msgid "" +"Defines the attribute in the structure in which your external data source " +"provides the *value* for your data. An example would be a product *number*. " +"If you have to go deeper in the structure, you can provide a path with ``.`` " +"as separators, e.g. ``key.subkey.sub-sub-key``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Tags" +#: ../system/objects/types.rst:277 +msgid "Search result label key" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.tags}``" +#: ../system/objects/types.rst:274 +msgid "" +"Defines the attribute in the structure in which your external data source " +"provides the *label* for your data. An example would be a product *name*. If " +"you have to go deeper in the structure, you can provide a path with ``.`` as " +"separators, e.g. ``key.subkey.sub-sub-key``." msgstr "" -#: ../system/variables/ticket.rst:1 +#: ../system/objects/types.rst:280 msgid "" -"Currently not available, see `Issue 2769 `_" +"In the preview area, you can find the following items (depending on your " +"configuration above):" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > State > Name" +#: ../system/objects/types.rst:283 +msgid "" +"**Error/hint message** (only if configuration is not complete): Zammad tells " +"you, if there is a problem and what you should change in your configuration." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.state.name}``" +#: ../system/objects/types.rst:286 +msgid "" +"**Search field**: search for an existing attribute in the data source to get " +"a preview. This is required for the fields below to show up." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``new``, ``open``, ..." +#: ../system/objects/types.rst:288 +msgid "" +"**Search result response** (only if configuration is not complete): here you " +"can find a syntax highlighted JSON preview of the response, based on the " +"search term you entered." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Priority > Name" +#: ../system/objects/types.rst:291 +msgid "" +"**Search result list** (only if *search result list key* is properly set): " +"output of the structure under the configured *search result list key*." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.priority.name}``" +#: ../system/objects/types.rst:294 +msgid "" +"**Preview table** (when fully configured): Zammad shows you a table which " +"includes the found items based on the search string (value, label and " +"optional link). You can use this preview if you don't have the complete data " +"structure of the external system in mind." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2 normal``" +#: ../system/objects/types.rst:299 +msgid "" +"An example of a configured external data source field from agent perspective:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Pending till" +#: ../system/objects/types.rst:0 +msgid "Screencast showing the search for a product in a ticket" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.pending_time}``" +#: ../system/objects/types.rst:307 +msgid "URL fields (Link-Template)" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not set" +#: ../system/objects/types.rst:311 +msgid "" +"This function is restricted to Text, Select and External data source types " +"only." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Web" +#: ../system/objects/types.rst:314 +msgid "" +"Link-Templates are an amazing way to dynamically generate URLs. They allow " +"you to integrate other systems better without having to manually copy data " +"from Zammad if possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.web}``" +#: ../system/objects/types.rst:320 +msgid "" +"Another great way of communicating with another system may be Zammad's :doc:" +"`Webhooks `." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``https://zammad.com`` or empty if not set" +#: ../system/objects/types.rst:323 +msgid "" +"After filling a link-template enabled field, an URL icon will appear on its " +"right. Clicking on the icon opens a new tab." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > VIP" +#: ../system/objects/types.rst:328 +msgid "" +"Even though Zammad displays the link template within object edit and create " +"screens, the function is optional. It's only active if you populate the " +"field." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.vip}``" +#: ../system/objects/types.rst:333 +msgid "" +"What's the difference between URL and text fields with link template...?!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Phone" +#: ../system/objects/types.rst:335 +msgid "" +"Both fields have different use cases. Use ``text`` type text fields when " +"ever you have a *static* url that requires dynamic parameters. If you " +"require a drag & drop like field that you can put in any URL, use ``URL`` " +"type text fields." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.phone}``" +#: ../system/objects/types.rst:340 +msgid "" +"The difference is easier to spot when comparing the fields directly, below " +"screencast shows the result - the dynamic approach uses existing values in " +"the moment of updating to built the URL - e.g. ``https://google.com/search?" +"q=cookies`` - while the URL approach uses the actual URL of the field - e.g. " +"``https://zammad.com``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Note" +#: ../system/objects/types.rst:None +msgid "" +"Screencast showing the differents in between URL and text type fields with " +"actual values" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.note}``" +#: ../system/objects/types.rst:352 +msgid "How does this work...?!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Mobile" +#: ../system/objects/types.rst:354 +msgid "" +"As an example, let's say you have an attribute called ``amazing_attribute`` " +"and you want to open a google search directly with the input from that field." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.mobile}``" +#: ../system/objects/types.rst:357 +msgid "" +"Providing the link-template field below allows you to do so: ``https://www." +"google.com/search?q=#{ticket.amazing_attribute}``" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Login" +#: ../system/objects/types.rst:362 +msgid "" +"You can use any :doc:`Zammad variable ` as long as it's " +"available in the moment you need it." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.login}``" +#: ../system/objects/types.rst:365 +msgid "" +"As a result, you are redirected to Google with a search for the value of the " +"attribute, if you click on the button in the ticket (as you can see in the " +"screencast above)." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``agent``" +#: ../system/packages.rst:2 +msgid "Packages" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Lastname" +#: ../system/packages.rst:4 +msgid "That's the package management-area." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.lastname}``" +#: ../system/packages.rst:6 +msgid "Individual add-ons for Zammad can be installed and managed here." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Mustermann`` or empty if not set" +#: ../system/sessions.rst:2 +msgid "Sessions" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Firstname" +#: ../system/sessions.rst:4 +msgid "" +"Sessions management allows reviewing currently known user sessions and " +"allows to end these. The session timeout is affected by :ref:" +"`security_session_timeout` configurations from security settings." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.firstname}``" +#: ../system/sessions.rst:None +msgid "Screenshot showing Zammad's session management" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Max`` or empty if not set" +#: ../system/sessions.rst:13 +msgid "Zammad will provide the following information:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Fax" +#: ../system/sessions.rst:16 +msgid "" +"The user account this session entry belongs to. It can be normal if a user " +"has several sessions in the list. This can be due to changed browser " +"information or if you use e.g. single sign on methods where the user does " +"not use the log off button." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.fax}``" +#: ../system/sessions.rst:22 +msgid "Browser" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Email" +#: ../system/sessions.rst:22 +msgid "The browser agent communicated to Zammad." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.email}``" +#: ../system/sessions.rst:40 +msgid "Location" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``agent@company.tld`` or empty if not set" +#: ../system/sessions.rst:25 +msgid "" +"The anticipated location based on the users IP address. Depending on the IP " +"address the result shown may differ. This option depends on :doc:`/settings/" +"system/services`." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Department" +#: ../system/sessions.rst:29 +msgid "The following information can be shown:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.department}``" +#: ../system/sessions.rst:33 +msgid "IP address" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Support`` or empty if not set" +#: ../system/sessions.rst:32 +msgid "" +"Either if you set *Geo IP services* to inactive or you're using internal IP " +"address which do not provide location information." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Avatar" +#: ../system/sessions.rst:40 +msgid "Country (or Country + City)" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.avatar(60,60)}``" +#: ../system/sessions.rst:36 +msgid "" +"If *Geo IP services* is enabled only. Depends on how detailed the available " +"IP address information are." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Address" +#: ../system/sessions.rst:39 +msgid "" +"Be aware that results can be inaccurate - this technically is not an error." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.address}``" +#: ../system/sessions.rst:43 +msgid "Age" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Shared organization" +#: ../system/sessions.rst:43 +msgid "Provides the time when the session initially has been created." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.shared}``" +#: ../system/sessions.rst:50 +msgid "Update" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Note" +#: ../system/sessions.rst:46 +msgid "" +"Provides the time the user used this session to open Zammad. This timestamp " +"is only updated if the user e.g. reloads, not during normal work on tickets." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.note}``" +#: ../system/sessions.rst:50 +msgid "This timestamp is being used for the session timeout." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Name" +#: ../system/sessions.rst:53 +msgid "" +"Use the delete button to remove a single session on behalf of your user." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.name}``" +#: ../system/subscription.rst:2 +msgid "Subscription (SaaS)" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Zammad GmbH`` or empty if not set" +#: ../system/subscription.rst:4 +msgid "" +"The subscription settings page allows you to configure your instances " +"package and number of agents required." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Domain based assignment" +#: ../system/subscription.rst:9 +msgid "" +"This setting section is only available for Hosted setups. If you're looking " +"for on premise support contracts, please see the `Zammad pricing page " +"`_." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.domain_assignment}``" +#: ../system/subscription.rst:14 ../system/subscription.rst:34 +msgid "Plan" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Domain" +#: ../system/subscription.rst:16 +msgid "" +"Here you can set up everything affecting your instance subscription " +"functions like number of agents and package." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.domain}``" +#: ../system/subscription.rst:19 +msgid "" +"On top of the page you can find a subscription summary. You'll find the " +"number of used and available (booked) agent seats there. By using the *see " +"more* link you can also expand an agent list to see the currently configured " +"active agents. This list *does not* count accounts with admin permissions " +"only." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``domain.tld`` or empty if not set" +#: ../system/subscription.rst:None +msgid "" +"Within subscription you can always see how many agents are still\n" +"available to add and who uses the seats." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > VIP" +#: ../system/subscription.rst:29 +msgid "" +"Learn more on how to manage your agents in general :doc:`here `." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.vip}``" +#: ../system/subscription.rst:36 +msgid "" +"This section gives you an overview of the available plans and their " +"functions / limits. If you require a more detailed table, check our " +"`detailed pricing table `_ for more." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Number" +#: ../system/subscription.rst:40 +msgid "" +"Your selection in this step will decide on the base agent price and e.g. " +"agent limits that might apply in the summary step." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.number}``" +#: ../system/subscription.rst:43 +msgid "" +"The green *Selected* button will also tell you what plan you're currently in." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``31001``, ``201910731001``, ..." +#: ../system/subscription.rst:47 +msgid "" +"Trial instances are running at Professional with 3 agents. The plan cannot " +"be changed during the trial for technical reasons, if you require more " +"agents for testing, please contact `our sales team `_ with a reason for the raise request." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > ID" +#: ../system/subscription.rst:None +msgid "" +"Screenshot showing three available packages for a hosted Zammad\n" +"instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.id}``" +#: ../system/subscription.rst:57 +msgid "" +"At the bottom of this block you can find a summary where you can adjust the " +"settings of the previous selected plan." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``17``, ``5281``, ..." +#: ../system/subscription.rst:62 +msgid "" +"Note that upgrading (more agents, higher package) is always possible, " +"however, downgrading will only happen when your billing period renews." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact (customer)" +#: ../system/subscription.rst:66 +msgid "" +"Upgrading resets your billing period and existing credit will be deducted " +"from the new total." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_customer_at}``" +#: ../system/subscription.rst:75 +msgid "Billing cycle" msgstr "" -#: ../system/variables/ticket.rst:1 +#: ../system/subscription.rst:70 msgid "" -"``2019-10-07 16:25:00 UTC`` or empty if not applicable yet (Please note " -"`Ticket last contact behavior Settings `_ for this)" +"You can choose between either monthly or yearly billing. The price per agent " +"will be cheaper if you decide for yearly billing." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact" +#: ../system/subscription.rst:73 +msgid "" +"If you're still trying out things and are unsure of the right package for " +"your instance, you may want to choose monthly first and then upgrade to " +"yearly when you're sure." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_at}``" +#: ../system/subscription.rst:83 +msgid "Plan: (Starter|Professional|Plus) - Agents" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact (agent)" +#: ../system/subscription.rst:78 +msgid "Choose the number of agents you require for your instance." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_agent_at}``" +#: ../system/subscription.rst:80 +msgid "" +"Keep in mind that some packages may have agent limits. Depending on the " +"previous chosen package, you won't be able to exceed specific agent numbers. " +"Also note that setting less agents than currently configured is not possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable yet" +#: ../system/subscription.rst:86 +msgid "Total" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Note" +#: ../system/subscription.rst:86 +msgid "This will be the net total you're going to be billed." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.note}``" +#: ../system/subscription.rst:88 +msgid "" +"By using the *Update subscription* button, the instance package will be " +"adjusted immediately. If you didn't provide a payment method yet, Zammad " +"will request you to provide one at this point." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Note about this group``" +#: ../system/subscription.rst:94 +msgid "" +"In case you're still within the trial period, this means that the trial will " +"be over immediately!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Name" +#: ../system/subscription.rst:97 +msgid "Down- or upgrading during the trial period *is not* possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.name}``" +#: ../system/subscription.rst:None +msgid "Screenshot showing payment options and a pricing summary" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Sales``" +#: ../system/subscription.rst:103 +msgid "Billing Information" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Follow-up possible" +#: ../system/subscription.rst:105 +msgid "" +"You can control all billing relevant information like invoices, billing " +"address and the option to cancel your subscription." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.follow_up_possible}``" +#: ../system/subscription.rst:108 +msgid "" +"All adjusted billing information below only affect future invoices. If your " +"invoice was issued wrong, please contact `our sales team `_." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``no`` or ``yes``" +#: ../system/subscription.rst:114 +msgid "Billing address" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Assign Follow-Ups" +#: ../system/subscription.rst:113 +msgid "" +"Provide your company address here, make sure to include the companies name " +"in case required. This address will be referenced on your invoice." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.follow_up_assignment}``" +#: ../system/subscription.rst:118 +msgid "VAT ID" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Assignment Timeout" +#: ../system/subscription.rst:117 +msgid "" +"Provide your VAT ID here. If applicable your invoice will not contain German " +"VAT. Please make sure to pay the VAT in your country as required." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.assignment_timeout}``" +#: ../system/subscription.rst:127 +msgid "Billing Email Address" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``20`` or empty if not configured" +#: ../system/subscription.rst:121 +msgid "" +"Usually the instance owner (the person that registered the instance) will " +"receive all emails including the invoices. In case you have your own billing " +"department, you can provide their email address here." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > First response" +#: ../system/subscription.rst:125 +msgid "" +"All billing relevant information will then be sent to this email address." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.first_response_at}``" +#: ../system/subscription.rst:127 +msgid "Invoices are sent as attachment (PDF) to this email address." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Escalation at" +#: ../system/subscription.rst:129 +msgid "" +"Don't forget to press the *Update billing information* button after you " +"changed above settings." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.escalation_at}``" +#: ../system/subscription.rst:None +msgid "" +"Screenshot showing options for billing information within the\n" +"subscription menu" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable" +#: ../system/subscription.rst:137 +msgid "Payment Method" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Web" +#: ../system/subscription.rst:139 +msgid "You can pay via credit card or SEPA mandate." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.web}``" +#: ../system/subscription.rst:144 +msgid "Credit card" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > VIP" +#: ../system/subscription.rst:142 +msgid "" +"Simply follow the dialogue by clicking *authorize credit card* and confirm -" +"if required by your bank- your consent to Zammad using your card for the " +"payments." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.vip}``" +#: ../system/subscription.rst:148 +msgid "SEPA Direct Debit" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Phone" +#: ../system/subscription.rst:147 +msgid "" +"Provide the requested information of the bank account holder and update if " +"you're ready. You'll then receive an email with the SEPA mandate." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.phone}``" +#: ../system/subscription.rst:150 +msgid "" +"Technically there's also the possibility to pay via invoice, however - this " +"method only applies to a fairly low number of instances. Please contact `our " +"sales team `_ for more information." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Note" +#: ../system/subscription.rst:156 +msgid "Cancel Subscription" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.note}``" +#: ../system/subscription.rst:158 +msgid "" +"Do you want to cancel your subscription? In case you no longer want to use " +"Zammad's SaaS, you can cancel your subscription by using the red *Yes, " +"please cancel my subscription* button." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Mobile" +#: ../system/subscription.rst:162 +msgid "" +"To cancel the description, enter the FQDN of your Zammad instance and " +"provide a reason for your cancellation." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.mobile}``" +#: ../system/subscription.rst:165 +msgid "" +"Your subscription will end the day after your trial or billing period ends." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Login" +#: ../system/subscription.rst:None +msgid "Screenshot showing subscription cancellation dialog" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.login}``" +#: ../system/subscription.rst:174 +msgid "" +"We will remind you about your cancelled subscription several times up front. " +"After the subscription ended all instance data will be removed. A restore " +"*is not* possible after that point!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Lastname" +#: ../system/subscription.rst:178 +msgid "**😖 Cancelled by accident?**" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.lastname}``" +#: ../system/subscription.rst:180 +msgid "" +"You can always undo the cancellation via the *Yes, undo the cancellation of " +"my subscription* button up to the last subscription day!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Firstname" +#: ../system/subscription.rst:0 +msgid "" +"Screenshot showing a red button to cancel the subscription\n" +"cancellation" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.firstname}``" +#: ../system/subscription.rst:189 +msgid "Payment History" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Fax" +#: ../system/subscription.rst:191 +msgid "" +"The payment history will display a history of all paid invoices. At this " +"point you can also download these in case you need them again." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.fax}``" +#: ../system/subscription.rst:196 +msgid "" +"You will only find *paid* invoices here. Invoices that are to be billed are " +"not available before the payment is completed." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Email" +#: ../system/subscription.rst:201 +msgid "Date" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.email}``" +#: ../system/subscription.rst:201 +msgid "Date of the invoice creation." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Department" +#: ../system/subscription.rst:204 +msgid "Amount" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.department}``" +#: ../system/subscription.rst:204 +msgid "Invoice total including VAT if applicable." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Avatar" +#: ../system/subscription.rst:207 +msgid "" +"Contains contract period (monthly or yearly) and hosted plan for the " +"subscription period in question." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.avatar(60,60)}``" +#: ../system/subscription.rst:218 +msgid "Payment method / Service period" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Address" +#: ../system/subscription.rst:211 +msgid "" +"Used bank account or credit card as well as the subscription period the " +"invoice is about." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.address}``" +#: ../system/subscription.rst:216 +msgid "" +"It might happen that the invoice date and subscription period differ. This " +"is nothing to worry about, the subscription periods will be accounted later " +"on." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Web" +#: ../system/subscription.rst:222 +msgid "Receipt" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.web}``" +#: ../system/subscription.rst:221 +msgid "" +"Use the arrow to download the invoice in question. You can download all " +"available invoices any time you need to here!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > VIP" +#: ../system/subscription.rst:None +msgid "Screenshot showing payment history of a hosted instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.vip}``" +#: ../system/subscription.rst:229 +msgid "FAQ" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Phone" +#: ../system/subscription.rst:233 +msgid "I set up a trial account but am missing functions to test" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.phone}``" +#: ../system/subscription.rst:232 +msgid "" +"The trial instance is running within the professional package allowing up to " +"three agents." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Note" +#: ../system/subscription.rst:236 +msgid "Can I change package within the trial?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.note}``" +#: ../system/subscription.rst:236 +msgid "No. As soon as the package is changed the subscription begins." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Mobile" +#: ../system/subscription.rst:241 +msgid "What happens to my trial instance after the trial period ended?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.mobile}``" +#: ../system/subscription.rst:239 +msgid "" +"Your instance will automatically be canceled for you. Please see *What " +"happens to my instance after it has been canceled?* for more." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Login" +#: ../system/subscription.rst:254 +msgid "What happens to my instance after it has been canceled?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.login}``" +#: ../system/subscription.rst:244 +msgid "That depends slightly on your instance state:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Lastname" +#: ../system/subscription.rst:250 +msgid "Trial instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.lastname}``" +#: ../system/subscription.rst:247 +msgid "" +"If you're still on trial, we will ice your instance and remind you once " +"again about your instance. We then will wait some days and remove your " +"instance from our system. This is the last time we will inform you by Email." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Firstname" +#: ../system/subscription.rst:254 +msgid "Paid instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.firstname}``" +#: ../system/subscription.rst:253 +msgid "" +"If you're a paying customer and canceled your subscription, the instance " +"removal will take place the day after your last subscription day." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Fax" +#: ../system/subscription.rst:256 +msgid "Can removed instances be restored?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.fax}``" +#: ../system/subscription.rst:257 +msgid "No. Once your instance has been removed, a restoration is not possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Email" +#: ../system/system-report.rst:2 +msgid "System Report" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.email}``" +#: ../system/system-report.rst:4 +msgid "" +"In this place you can't configure Zammad. Instead you can obtain a system " +"report about Zammad and its configuration." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Department" +#: ../system/system-report.rst:7 +msgid "" +"See the description in Zammad for an explanation. You can even find a " +"preview of the included data below the **Download** button." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.department}``" +#: ../system/system-report.rst:10 +msgid "" +"Zammad never sends this automatically to anyone. It is a manual process only " +"to provide better support based on your configuration." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Avatar" -msgstr "" +#: ../system/translations.rst:2 +msgid "Translations" +msgstr "Переводы" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.avatar(60,60)}``" +#: ../system/translations.rst:4 +msgid "" +"Translations of Zammad are processed centrally in our `Weblate instance " +"`_. This allows non-developers to review " +"and update translation texts of the language they actually speak." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Address" +#: ../system/translations.rst:9 +msgid "" +"Your language is in an incomplete translation state or has typos? Please " +"consider helping us in sorting this out! All you need is either a GitHub " +"account or to register directly in our instance." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.address}``" +#: ../system/translations.rst:13 +msgid "" +"Did you know? This is also where the documentation translations are handled. " +"🤓" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created at" +#: ../system/translations.rst:15 +msgid "" +"Have a look in our :docs:`contribution section ` in the system documentation to get started!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_at}``" +#: ../system/translations.rst:20 +msgid "Local Translations" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "2019-10-07 16:25:00 UTC" +#: ../system/translations.rst:22 +msgid "" +"Apart from these system translations, there's still local translations you " +"can manage. This is relevant if you added custom objects that require " +"translations or even custom states and priorities." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Closing time" +#: ../system/translations.rst:None +msgid "Translation management screen within the admin menu" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.close_at}``" +#: ../system/translations.rst:31 +msgid "Updating Translations" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "2019-10-07 17:25:00 UTC" +#: ../system/translations.rst:33 +msgid "" +"Because of how Zammad ships translations, the only way to update the system " +"translations is to update your Zammad installation. The benefit of this is " +"that you no longer need internet access during a Zammad upgrade as the " +"package has everything it requires already." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``3``, any number of articles existing in the ticket right now" +#: ../system/translations.rst:39 +msgid "Translation of Custom Objects" msgstr "" -#: ../system/version.rst:2 -msgid "Version" +#: ../system/translations.rst:41 +msgid "" +"No problem at all! You can customize any translation locally, even if it is " +"not initially provided by the system." msgstr "" -#: ../system/version.rst:4 -msgid "Shows which version is currently being used on your Zammad-instance." +#: ../system/translations.rst:44 +msgid "" +"Translation is supported for a broad number of features, including but not " +"limited to custom:" msgstr "" -#: ../manage/roles/admin-permissions.rst:53 -msgid "``admin.checklist``" +#: ../system/translations.rst:47 +msgid "Object Attributes" msgstr "" -#: ../manage/roles/admin-permissions.rst:54 -msgid ":doc:`Manage > Checklist `" +#: ../system/translations.rst:48 +msgid "Ticket Macros" +msgstr "Макрос заявки" + +#: ../system/translations.rst:49 +msgid "Ticket Overviews" msgstr "" -#: ../manage/roles/admin-permissions.rst:83 -msgid "``admin.channel_whatsapp``" +#: ../system/translations.rst:50 +msgid "Ticket Priorities" msgstr "" -#: ../manage/roles/admin-permissions.rst:84 -msgid ":doc:`Channels > Whatsapp `" +#: ../system/translations.rst:51 +msgid "Ticket States" msgstr "" -#: ../manage/roles/admin-permissions.rst:124 -msgid "``admin.public_links``" +#: ../system/translations.rst:54 +msgid "Customizing Translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:125 -msgid ":doc:`Manage > Public Links `" +#: ../system/translations.rst:56 +msgid "" +"Within the translation screen, simply click on the **New Translation** " +"button." msgstr "" -#: ../manage/roles/admin-permissions.rst:151 -msgid "``admin.system_report``" +#: ../system/translations.rst:None +msgid "New translation dialog" msgstr "" -#: ../manage/roles/admin-permissions.rst:152 -msgid ":doc:`System > System Report `" +#: ../system/translations.rst:62 +msgid "" +"In the dialog you can immediately enter the exact translation source (if you " +"know it) and your custom translation text for it and click **Submit**." msgstr "" -#: ../manage/roles/admin-permissions.rst:166 -msgid "``admin.ticket_auto_assignment``" +#: ../system/translations.rst:65 +msgid "" +"Alternatively, try to search for translation suggestions in the list below. " +"Selecting an item from the list will pre-fill the translation source for you " +"and then you can just enter your custom translation." msgstr "" -#: ../manage/roles/admin-permissions.rst:167 -msgid ":ref:`Settings > Ticket > Auto Assignment `" +#: ../system/translations.rst:69 +msgid "" +"The target language will always default to your current language selection. " +"If you need to translate for a different language, simply change the " +"selection before submitting." msgstr "" -#: ../manage/roles/admin-permissions.rst:169 -msgid "``admin.ticket_duplicate_detection``" +#: ../system/translations.rst:73 +msgid "" +"All your custom translations will show up in the overview table when added. " +"And they will even persist across Zammad updates!" msgstr "" -#: ../manage/roles/admin-permissions.rst:170 -msgid ":ref:`Settings > Ticket > Duplicate Detection `" +#: ../system/translations.rst:76 +msgid "" +"Make sure to reload your browser if a translated string is not displayed." msgstr "" -#: ../manage/roles/admin-permissions.rst:172 -msgid "``admin.ticket_priority``" +#: ../system/translations.rst:80 +msgid "Reverting to Original Translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:173 -msgid ":ref:`System > Objects >Ticket Priority `" +#: ../system/translations.rst:82 +msgid "" +"If you want to revert a custom translation to original text, simply use the " +"appropriate action within the row of the overview table." msgstr "" -#: ../manage/roles/admin-permissions.rst:175 -msgid "``admin.ticket_state``" +#: ../system/translations.rst:85 +msgid "" +"Depending on the type of the translation source, the action has a slightly " +"different name:" msgstr "" -#: ../manage/roles/admin-permissions.rst:176 -msgid ":ref:`System > Objects >Ticket State `" +#: ../system/translations.rst:88 +msgid "**Reset** for customized system translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:193 -msgid "``admin.webhook``" +#: ../system/translations.rst:89 +msgid "**Remove** for customized local translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:194 -msgid ":doc:`Manage > Webhook `" +#: ../system/translations.rst:91 +msgid "" +"In both cases, the action will remove the customized translation after a " +"confirmation." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:43 -msgid "``user_preferences.appearance``" +#: ../system/translations.rst:None +msgid "Screenshot showing the location of the Remove action" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:44 -msgid "Appearance configuration" +#: ../system/translations.rst:99 +msgid "Inline Translations" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:0 -msgid "Users can switch between dark, light and" +#: ../system/translations.rst:101 +msgid "" +"If you prefer a more hands-on approach, you can activate the inline or on-" +"screen translation feature by pressing ``ctrl`` + ``alt`` + ``t`` at any " +"time and on any screen." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:0 -msgid "automatic mode." +#: ../system/translations.rst:105 +msgid "" +"All customizable translation texts will be highlighted for you on the " +"screen. Just click into the highlighted area and update the text in place." msgstr "" -#: ../system/system-report.rst:2 -msgid "System Report" +#: ../system/translations.rst:None +msgid "Inline translation mode activated for the Overview screen" msgstr "" -#: ../system/system-report.rst:4 +#: ../system/translations.rst:112 msgid "" -"In this place you can't configure Zammad. Instead you can obtain a system " -"report about Zammad and its configuration." +"When finished editing, simply press ``ctrl`` + ``alt`` + ``t`` again to " +"deactivate." msgstr "" -#: ../system/system-report.rst:7 +#: ../system/translations.rst:117 msgid "" -"See the description in Zammad for an explanation. You can even find a " -"preview of the included data below the **Download** button." +"Even though it's available on any screen, the inline translation feature " +"requires admin permissions. It works only for the current language " +"selection. If you need to translate a different language, first change the " +"language in your :user-docs:`profile settings `." msgstr "" -#: ../system/system-report.rst:10 -msgid "" -"Zammad never sends this automatically to anyone. It is a manual process only " -"to provide better support based on your configuration." +#: ../system/version.rst:2 +msgid "Version" +msgstr "" + +#: ../system/version.rst:4 +msgid "Shows which version is currently being used on your Zammad-instance." msgstr "" #~ msgid "" diff --git a/locale/sr/LC_MESSAGES/admin-docs.po b/locale/sr/LC_MESSAGES/admin-docs.po index 20908f74..71023942 100644 --- a/locale/sr/LC_MESSAGES/admin-docs.po +++ b/locale/sr/LC_MESSAGES/admin-docs.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Zammad Admin Documentation pre-release\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-11-06 10:31+0100\n" +"POT-Creation-Date: 2024-11-12 16:31+0100\n" "PO-Revision-Date: 2024-11-12 09:00+0000\n" "Last-Translator: Dusan Vuckovic \n" "Language-Team: Serbian Checklist `" +msgstr ":doc:`Управљање > Списак задатака `" + #: ../manage/roles/admin-permissions.rst:56 msgid "``admin.channel_email``" msgstr "``admin.channel_email``" -#: ../manage/roles/admin-permissions.rst:54 #: ../manage/roles/admin-permissions.rst:57 msgid ":doc:`Channels > Email `" msgstr ":doc:`Канали > Имејл `" -#: ../manage/roles/admin-permissions.rst:56 #: ../manage/roles/admin-permissions.rst:59 msgid "``admin.channel_facebook``" msgstr "``admin.channel_facebook``" -#: ../manage/roles/admin-permissions.rst:57 #: ../manage/roles/admin-permissions.rst:60 msgid ":doc:`Channels > Facebook `" msgstr ":doc:`Канали > Facebook `" -#: ../manage/roles/admin-permissions.rst:58 #: ../manage/roles/admin-permissions.rst:61 msgid "" "Accessing Facebook tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" "Приступ Facebook тикетима за оператере: :doc:`/manage/groups/access-levels`" -#: ../manage/roles/admin-permissions.rst:59 #: ../manage/roles/admin-permissions.rst:62 msgid "``admin.channel_formular``" msgstr "``admin.channel_formular``" -#: ../manage/roles/admin-permissions.rst:60 #: ../manage/roles/admin-permissions.rst:63 msgid ":doc:`Channels > Form `" msgstr ":doc:`Канали > Форма `" -#: ../manage/roles/admin-permissions.rst:62 #: ../manage/roles/admin-permissions.rst:65 msgid "``admin.channel_google``" msgstr "``admin.channel_google``" -#: ../manage/roles/admin-permissions.rst:63 #: ../manage/roles/admin-permissions.rst:66 msgid ":doc:`Channels > Google `" msgstr ":doc:`Канали > Google `" -#: ../manage/roles/admin-permissions.rst:65 #: ../manage/roles/admin-permissions.rst:68 msgid "``admin.channel_microsoft365``" msgstr "``admin.channel_microsoft365``" -#: ../manage/roles/admin-permissions.rst:66 #: ../manage/roles/admin-permissions.rst:69 msgid ":doc:`Channels > Microsoft 365 `" msgstr ":doc:`Канали > Microsoft 365 `" -#: ../manage/roles/admin-permissions.rst:68 #: ../manage/roles/admin-permissions.rst:71 msgid "``admin.channel_sms``" msgstr "``admin.channel_sms``" -#: ../manage/roles/admin-permissions.rst:69 #: ../manage/roles/admin-permissions.rst:72 msgid ":doc:`Channels > SMS `" msgstr ":doc:`Канали > SMS `" -#: ../manage/roles/admin-permissions.rst:71 #: ../manage/roles/admin-permissions.rst:74 msgid "``admin.channel_telegram``" msgstr "``admin.channel_telegram``" -#: ../manage/roles/admin-permissions.rst:72 #: ../manage/roles/admin-permissions.rst:75 msgid ":doc:`Channels > Telegram `" msgstr ":doc:`Канали > Telegram `" -#: ../manage/roles/admin-permissions.rst:73 #: ../manage/roles/admin-permissions.rst:76 msgid "" "Accessing Telegram tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" "Приступ Telegram тикетима за оператере: :doc:`/manage/groups/access-levels`" -#: ../manage/roles/admin-permissions.rst:74 #: ../manage/roles/admin-permissions.rst:77 msgid "``admin.channel_twitter``" msgstr "``admin.channel_twitter``" -#: ../manage/roles/admin-permissions.rst:75 #: ../manage/roles/admin-permissions.rst:78 msgid ":doc:`Channels > Twitter `" msgstr ":doc:`Канали > Twitter `" -#: ../manage/roles/admin-permissions.rst:76 #: ../manage/roles/admin-permissions.rst:79 msgid "" "Accessing Twitter/X tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" "Приступ Twitter/X тикетима за оператере: :doc:`/manage/groups/access-levels`" -#: ../manage/roles/admin-permissions.rst:77 #: ../manage/roles/admin-permissions.rst:80 msgid "``admin.channel_web``" msgstr "``admin.channel_web``" -#: ../manage/roles/admin-permissions.rst:78 #: ../manage/roles/admin-permissions.rst:81 msgid ":doc:`Channels > Web `" msgstr ":doc:`Канали > Веб `" -#: ../manage/roles/admin-permissions.rst:80 +#: ../manage/roles/admin-permissions.rst:83 +msgid "``admin.channel_whatsapp``" +msgstr "``admin.channel_whatsapp``" + +#: ../manage/roles/admin-permissions.rst:84 +msgid ":doc:`Channels > Whatsapp `" +msgstr ":doc:`Канали > Whatsapp `" + #: ../manage/roles/admin-permissions.rst:86 msgid "``admin.core_workflows``" msgstr "``admin.core_workflows``" -#: ../manage/roles/admin-permissions.rst:81 #: ../manage/roles/admin-permissions.rst:87 msgid ":doc:`System > Core Workflows `" msgstr ":doc:`Систем > Радни токови `" -#: ../manage/roles/admin-permissions.rst:83 #: ../manage/roles/admin-permissions.rst:89 msgid "``admin.data_privacy``" msgstr "``admin.data_privacy``" -#: ../manage/roles/admin-permissions.rst:84 #: ../manage/roles/admin-permissions.rst:90 msgid ":doc:`System > Data Privacy `" msgstr ":doc:`Систем > Приватност података `" -#: ../manage/roles/admin-permissions.rst:85 #: ../manage/roles/admin-permissions.rst:91 msgid "" "🔥 Be careful, it allows users to permanently delete data on the system." msgstr "" "🔥 Будите опрезни, омогућава корисницима да трајно бришу податке на систему." -#: ../manage/roles/admin-permissions.rst:86 #: ../manage/roles/admin-permissions.rst:92 msgid "``admin.group``" msgstr "``admin.group``" -#: ../manage/roles/admin-permissions.rst:87 #: ../manage/roles/admin-permissions.rst:93 msgid ":doc:`Manage > Groups `" msgstr ":doc:`Управљање > Групе `" -#: ../manage/roles/admin-permissions.rst:89 #: ../manage/roles/admin-permissions.rst:95 msgid "``admin.integration``" msgstr "``admin.integration``" -#: ../manage/roles/admin-permissions.rst:90 #: ../manage/roles/admin-permissions.rst:96 msgid ":doc:`System > Integrations `" msgstr ":doc:`Систем > Интеграције `" -#: ../manage/roles/admin-permissions.rst:92 #: ../manage/roles/admin-permissions.rst:98 msgid "``admin.knowledge_base``" msgstr "``admin.knowledge_base``" -#: ../manage/roles/admin-permissions.rst:93 #: ../manage/roles/admin-permissions.rst:99 msgid ":doc:`Manage > Knowledge Base `" msgstr ":doc:`Управљање > База знања `" @@ -10457,57 +10452,46 @@ msgstr "" "Проверите још једном :user-docs:`видљивост чланака `." -#: ../manage/roles/admin-permissions.rst:98 #: ../manage/roles/admin-permissions.rst:104 msgid "``admin.macro``" msgstr "``admin.macro``" -#: ../manage/roles/admin-permissions.rst:99 #: ../manage/roles/admin-permissions.rst:105 msgid ":doc:`Manage > Macros `" msgstr ":doc:`Управљање > Макрои `" -#: ../manage/roles/admin-permissions.rst:100 #: ../manage/roles/admin-permissions.rst:106 msgid "In some cases, macros may also require ``admin.tag``" msgstr "У неким случајевима, макрои могу такође захтевати ``admin.tag``" -#: ../manage/roles/admin-permissions.rst:101 #: ../manage/roles/admin-permissions.rst:107 msgid "``admin.maintenance``" msgstr "``admin.maintenance``" -#: ../manage/roles/admin-permissions.rst:102 #: ../manage/roles/admin-permissions.rst:108 msgid ":doc:`System > Maintenance `" msgstr ":doc:`Систем > Одржавање `" -#: ../manage/roles/admin-permissions.rst:104 #: ../manage/roles/admin-permissions.rst:110 msgid "``admin.monitoring``" msgstr "``admin.monitoring``" -#: ../manage/roles/admin-permissions.rst:105 #: ../manage/roles/admin-permissions.rst:111 msgid ":doc:`System > Monitoring `" msgstr ":doc:`Систем > Надгледање `" -#: ../manage/roles/admin-permissions.rst:107 #: ../manage/roles/admin-permissions.rst:113 msgid "``admin.object``" msgstr "``admin.object``" -#: ../manage/roles/admin-permissions.rst:108 #: ../manage/roles/admin-permissions.rst:114 msgid ":doc:`System > Objects `" msgstr ":doc:`Систем > Објекти `" -#: ../manage/roles/admin-permissions.rst:110 #: ../manage/roles/admin-permissions.rst:116 msgid "``admin.organization``" msgstr "``admin.organization``" -#: ../manage/roles/admin-permissions.rst:111 #: ../manage/roles/admin-permissions.rst:117 msgid ":doc:`Manage > Organizations `" msgstr ":doc:`Управљање > Организације `" @@ -10524,203 +10508,211 @@ msgstr "из траке за претрагу, чак и без ове дозв msgid "They can even edit an organization's name, domain, and notes!" msgstr "Могу чак изменити назив, домен и напомену организације!" -#: ../manage/roles/admin-permissions.rst:115 #: ../manage/roles/admin-permissions.rst:121 msgid "``admin.overview``" msgstr "``admin.overview``" -#: ../manage/roles/admin-permissions.rst:116 #: ../manage/roles/admin-permissions.rst:122 msgid ":doc:`Manage > Overviews`" msgstr ":doc:`Управљање > Прегледи `" -#: ../manage/roles/admin-permissions.rst:118 +#: ../manage/roles/admin-permissions.rst:124 +msgid "``admin.public_links``" +msgstr "``admin.public_links``" + +#: ../manage/roles/admin-permissions.rst:125 +msgid ":doc:`Manage > Public Links `" +msgstr ":doc:`Управљање > Јавни линкови `" + #: ../manage/roles/admin-permissions.rst:127 msgid "``admin.package``" msgstr "``admin.package``" -#: ../manage/roles/admin-permissions.rst:119 #: ../manage/roles/admin-permissions.rst:128 msgid ":doc:`System > Packages `" msgstr ":doc:`Систем > Пакети `" -#: ../manage/roles/admin-permissions.rst:121 #: ../manage/roles/admin-permissions.rst:130 msgid "``admin.report_profile``" msgstr "``admin.report_profile``" -#: ../manage/roles/admin-permissions.rst:122 #: ../manage/roles/admin-permissions.rst:131 msgid ":doc:`Manage > Report Profiles `" msgstr ":doc:`Управљање > Профили извештаја `" -#: ../manage/roles/admin-permissions.rst:123 #: ../manage/roles/admin-permissions.rst:132 msgid "Access to view reports: ``report``" msgstr "Приступ за преглед извештаја: ``report``" -#: ../manage/roles/admin-permissions.rst:124 #: ../manage/roles/admin-permissions.rst:133 msgid "``admin.role``" msgstr "``admin.role``" -#: ../manage/roles/admin-permissions.rst:125 #: ../manage/roles/admin-permissions.rst:134 msgid ":doc:`Manage > Roles `" msgstr ":doc:`Управљање > Улоге `" -#: ../manage/roles/admin-permissions.rst:127 #: ../manage/roles/admin-permissions.rst:136 msgid "``admin.scheduler``" msgstr "``admin.scheduler``" -#: ../manage/roles/admin-permissions.rst:128 #: ../manage/roles/admin-permissions.rst:137 msgid ":doc:`Manage > Scheduler `" msgstr ":doc:`Управљање > Планер `" -#: ../manage/roles/admin-permissions.rst:129 #: ../manage/roles/admin-permissions.rst:138 msgid "For automation on tickets" msgstr "За аутоматизацију тикета" -#: ../manage/roles/admin-permissions.rst:130 #: ../manage/roles/admin-permissions.rst:139 msgid "``admin.security``" msgstr "``admin.security``" -#: ../manage/roles/admin-permissions.rst:131 #: ../manage/roles/admin-permissions.rst:140 msgid ":doc:`Settings > Security `" msgstr ":doc:`Подешавања > Безбедност `" -#: ../manage/roles/admin-permissions.rst:132 #: ../manage/roles/admin-permissions.rst:141 msgid "Settings of Zammad. This also covers third party authentications." msgstr "" "подешавања Zammad-а. Ово такође покрива аутентификацију преко трећег лица." -#: ../manage/roles/admin-permissions.rst:133 #: ../manage/roles/admin-permissions.rst:142 msgid "``admin.session``" msgstr "``admin.session``" -#: ../manage/roles/admin-permissions.rst:134 #: ../manage/roles/admin-permissions.rst:143 msgid ":doc:`System > Sessions `" msgstr ":doc:`Систем > Сесије `" -#: ../manage/roles/admin-permissions.rst:136 #: ../manage/roles/admin-permissions.rst:145 msgid "``admin.setting_system``" msgstr "``admin.setting_system``" -#: ../manage/roles/admin-permissions.rst:137 #: ../manage/roles/admin-permissions.rst:146 msgid ":doc:`Settings > System `" msgstr ":doc:`Подешавања > Систем `" -#: ../manage/roles/admin-permissions.rst:139 #: ../manage/roles/admin-permissions.rst:148 msgid "``admin.sla``" msgstr "``admin.sla``" -#: ../manage/roles/admin-permissions.rst:140 #: ../manage/roles/admin-permissions.rst:149 msgid ":doc:`Manage > SLAs `" msgstr ":doc:`Управљање > SLA `" -#: ../manage/roles/admin-permissions.rst:142 +#: ../manage/roles/admin-permissions.rst:151 +msgid "``admin.system_report``" +msgstr "``admin.system_report``" + +#: ../manage/roles/admin-permissions.rst:152 +msgid ":doc:`System > System Report `" +msgstr ":doc:`Систем > Системски извештај `" + #: ../manage/roles/admin-permissions.rst:154 msgid "``admin.tag``" msgstr "``admin.tag``" -#: ../manage/roles/admin-permissions.rst:143 #: ../manage/roles/admin-permissions.rst:155 msgid ":doc:`Manage > Tags `" msgstr ":doc:`Управљање > Ознаке `" -#: ../manage/roles/admin-permissions.rst:145 #: ../manage/roles/admin-permissions.rst:157 msgid "``admin.template``" msgstr "``admin.template``" -#: ../manage/roles/admin-permissions.rst:146 #: ../manage/roles/admin-permissions.rst:158 msgid ":doc:`Manage > Templates `" msgstr ":doc:`Управљање > Шаблони `" -#: ../manage/roles/admin-permissions.rst:148 #: ../manage/roles/admin-permissions.rst:160 msgid "``admin.text_module``" msgstr "``admin.text_module``" -#: ../manage/roles/admin-permissions.rst:149 #: ../manage/roles/admin-permissions.rst:161 msgid ":doc:`Manage > Text Modules `" msgstr ":doc:`Управљање > Текстуални исечци `" -#: ../manage/roles/admin-permissions.rst:151 #: ../manage/roles/admin-permissions.rst:163 msgid "``admin.ticket``" msgstr "``admin.ticket``" -#: ../manage/roles/admin-permissions.rst:152 #: ../manage/roles/admin-permissions.rst:164 msgid ":doc:`Settings > Tickets `" msgstr ":doc:`Подешавања > Тикети `" -#: ../manage/roles/admin-permissions.rst:153 #: ../manage/roles/admin-permissions.rst:165 msgid "Does not grant access to :doc:`/misc/composer`" msgstr "Не дозвољава приступ :doc:`/misc/composer`" -#: ../manage/roles/admin-permissions.rst:154 +#: ../manage/roles/admin-permissions.rst:166 +msgid "``admin.ticket_auto_assignment``" +msgstr "``admin.ticket_auto_assignment``" + +#: ../manage/roles/admin-permissions.rst:167 +msgid ":ref:`Settings > Ticket > Auto Assignment `" +msgstr ":ref:`Подешавања > Тикет > Аутоматска додела тикета `" + +#: ../manage/roles/admin-permissions.rst:169 +msgid "``admin.ticket_duplicate_detection``" +msgstr "``admin.ticket_duplicate_detection``" + +#: ../manage/roles/admin-permissions.rst:170 +msgid ":ref:`Settings > Ticket > Duplicate Detection `" +msgstr ":ref:`Подешавања > Тикет > Откривање дупликата `" + +#: ../manage/roles/admin-permissions.rst:172 +msgid "``admin.ticket_priority``" +msgstr "``admin.ticket_priority``" + +#: ../manage/roles/admin-permissions.rst:173 +msgid ":ref:`System > Objects >Ticket Priority `" +msgstr ":ref:`Систем > Објекти >Приоритет тикета `" + +#: ../manage/roles/admin-permissions.rst:175 +msgid "``admin.ticket_state``" +msgstr "``admin.ticket_state``" + +#: ../manage/roles/admin-permissions.rst:176 +msgid ":ref:`System > Objects >Ticket State `" +msgstr ":ref:`Систем > Објекти > Стање тикета `" + #: ../manage/roles/admin-permissions.rst:178 msgid "``admin.time_accounting``" msgstr "``admin.time_accounting``" -#: ../manage/roles/admin-permissions.rst:155 #: ../manage/roles/admin-permissions.rst:179 msgid ":doc:`Manage > Time Accounting `" msgstr ":doc:`Управљање > Обрачун времена `" -#: ../manage/roles/admin-permissions.rst:156 #: ../manage/roles/admin-permissions.rst:180 msgid "Also allows the export of timekeeping records." msgstr "Такоће омогућује извоз уноса обрачуна времена." -#: ../manage/roles/admin-permissions.rst:157 #: ../manage/roles/admin-permissions.rst:181 msgid "``admin.translation``" msgstr "``admin.translation``" -#: ../manage/roles/admin-permissions.rst:158 #: ../manage/roles/admin-permissions.rst:182 msgid ":doc:`System > Translations `" msgstr ":doc:`Систем > Преводи `" -#: ../manage/roles/admin-permissions.rst:159 #: ../manage/roles/admin-permissions.rst:183 msgid "Also enables inline translation" msgstr "Такође омогућује непосредне преводе" -#: ../manage/roles/admin-permissions.rst:160 #: ../manage/roles/admin-permissions.rst:184 msgid "``admin.trigger``" msgstr "``admin.trigger``" -#: ../manage/roles/admin-permissions.rst:161 #: ../manage/roles/admin-permissions.rst:185 msgid ":doc:`Manage > Triggers `" msgstr ":doc:`Управљање > Окидачи `" -#: ../manage/roles/admin-permissions.rst:163 #: ../manage/roles/admin-permissions.rst:187 msgid "``admin.user``" msgstr "``admin.user``" -#: ../manage/roles/admin-permissions.rst:164 #: ../manage/roles/admin-permissions.rst:188 msgid ":doc:`Manage > Users `" msgstr ":doc:`Управљање > Корисници `" @@ -10741,6 +10733,14 @@ msgstr "" "🏴‍☠ Ова дозвола омогућава корисницима :ref:`преотму сесије других корисника " "`." +#: ../manage/roles/admin-permissions.rst:193 +msgid "``admin.webhook``" +msgstr "``admin.webhook``" + +#: ../manage/roles/admin-permissions.rst:194 +msgid ":doc:`Manage > Webhook `" +msgstr ":doc:`Управљање > Повратни позив `" + #: ../manage/roles/agent-permissions.rst:2 msgid "Agent Permissions" msgstr "Дозволе оператера" @@ -11230,36 +11230,45 @@ msgid "than the user that generated them." msgstr "од корисника који их је генерисао." #: ../manage/roles/user-preferences-permissions.rst:43 +msgid "``user_preferences.appearance``" +msgstr "``user_preferences.appearance``" + +#: ../manage/roles/user-preferences-permissions.rst:44 +msgid "Appearance configuration" +msgstr "Подешавање изгледа" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "Users can switch between dark, light and" +msgstr "Корисници могу да изаберу између тамног, светлог и" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "automatic mode." +msgstr "аутоматског мода." + #: ../manage/roles/user-preferences-permissions.rst:47 msgid "``user_preferences.avatar``" msgstr "``user_preferences.avatar``" -#: ../manage/roles/user-preferences-permissions.rst:44 #: ../manage/roles/user-preferences-permissions.rst:48 msgid "Avatar settings" msgstr "Подешавања аватара" -#: ../manage/roles/user-preferences-permissions.rst:45 #: ../manage/roles/user-preferences-permissions.rst:49 msgid "Override the default Gravatar with a custom avatar" msgstr "Замена подразумеваног Gravatar-а са прилагођеним аватаром" -#: ../manage/roles/user-preferences-permissions.rst:46 #: ../manage/roles/user-preferences-permissions.rst:50 msgid "``user_preferences.calendar``" msgstr "``user_preferences.calendar``" -#: ../manage/roles/user-preferences-permissions.rst:47 #: ../manage/roles/user-preferences-permissions.rst:51 msgid "Configure the calendar feed" msgstr "Подешавање извора календара" -#: ../manage/roles/user-preferences-permissions.rst:49 #: ../manage/roles/user-preferences-permissions.rst:53 msgid "``user_preferences.device``" msgstr "``user_preferences.device``" -#: ../manage/roles/user-preferences-permissions.rst:50 #: ../manage/roles/user-preferences-permissions.rst:54 msgid "Manage device login sessions" msgstr "Управљање сесијама пријаве преко уређаја" @@ -11278,22 +11287,18 @@ msgstr "" "Да бисте сазнали више, погледајте :doc:`/manage/trigger/system-" "notifications`." -#: ../manage/roles/user-preferences-permissions.rst:54 #: ../manage/roles/user-preferences-permissions.rst:58 msgid "``user_preferences.language``" msgstr "``user_preferences.language``" -#: ../manage/roles/user-preferences-permissions.rst:55 #: ../manage/roles/user-preferences-permissions.rst:59 msgid "Configure the UI locale/language" msgstr "Подешавање језика корисничког интерфејса" -#: ../manage/roles/user-preferences-permissions.rst:57 #: ../manage/roles/user-preferences-permissions.rst:61 msgid "``user_preferences.linked_accounts``" msgstr "``user_preferences.linked_accounts``" -#: ../manage/roles/user-preferences-permissions.rst:58 #: ../manage/roles/user-preferences-permissions.rst:62 msgid "Account linking" msgstr "Повезивање налога" @@ -11322,7 +11327,6 @@ msgid "is the only way users can utilize third-party logins." msgstr "" "је једини начин на који ваши корисници могу да се пријаве преко трећег лица." -#: ../manage/roles/user-preferences-permissions.rst:63 #: ../manage/roles/user-preferences-permissions.rst:67 msgid "``user_preferences.notifications``" msgstr "``user_preferences.notifications``" @@ -11350,7 +11354,6 @@ msgstr "" msgid "Customers can't receive ticket notifications at all." msgstr "Клијенти уопште не могу да примају обавештења о тикетима." -#: ../manage/roles/user-preferences-permissions.rst:69 #: ../manage/roles/user-preferences-permissions.rst:73 msgid "``user_preferences.out_of_office``" msgstr "``user_preferences.out_of_office``" @@ -11375,7 +11378,6 @@ msgstr ":doc:`ниова групних дозвола `." #: ../manage/text-modules.rst:57 +#, fuzzy +#| msgid "" +#| "The example text modules below use :doc:`/system/variables` to " +#| "dynamically insert information like the customer's or agent's names." msgid "" -"The example text modules below use :doc:`/system/variables` to dynamically " +"The example text modules below use :doc:`/misc/variables` to dynamically " "insert information like the customer's or agent's names." msgstr "" "Примери текстуалних исечака у наставку користе :doc:`променљиве ` циљној путањи." #: ../manage/webhook/add.rst:98 +#, fuzzy +#| msgid "" +#| "When switched on, a code editor will be shown below, where you can " +#| "configure custom payload for your webhook in JSON format. To insert " +#| "supported :doc:`/system/variables` use ``::`` or ``#{`` shortcuts for " +#| "autocomplete." msgid "" "When switched on, a code editor will be shown below, where you can configure " "custom payload for your webhook in JSON format. To insert supported :doc:`/" -"system/variables` use ``::`` or ``#{`` shortcuts for autocomplete." +"misc/variables` use ``::`` or ``#{`` shortcuts for autocomplete." msgstr "" "Када је укључено, испод ће бити приказан уредник кода, где можете да " "подесите прилагођене податке за свој повратни позив у JSON формату. Да бисте " @@ -17614,14314 +17637,14310 @@ msgstr "" "Сазнајте како вам Zammad-ов стручни режим за услове омогућава да дефинишете " "још моћније услове са AND/OR клаузулама." -#: ../settings/branding.rst:10 -msgid "Product Name" -msgstr "Назив производа" +#: ../misc/variables.rst:2 +msgid "Variables" +msgstr "Променљиве" -#: ../settings/branding.rst:7 +#: ../misc/variables.rst:4 msgid "" -"Defines the name of the application, shown in the web interface, tabs and " -"title bar of the web browser." +"Please note that this is just an overview of available variables. It might " +"be incomplete or variables might not be available within some functions. If " +"you're missing variables or are not sure if something is not working as " +"expected, feel free to ask over at the `Community `_." msgstr "" -"Одређује назив апликације, који се приказује у веб интерфејсу, прозорима и " -"наслову интернет претраживача." +"ОБратите пажњу да је ово само преглед доступних променљивих. Може бити " +"некомплетан или променљиве можда нису доступне унутар неких функција. Ако " +"вам зафале променљиве или нисте сигурни да ли раде на очекиван начин, " +"слободно питајте на `Community форуму `_." -#: ../settings/branding.rst:10 -msgid "Default value: ``Zammad Helpdesk``" -msgstr "Подразумевана вредност: ``Zammad Helpdesk``" +#: ../misc/variables.rst:10 +msgid "" +"Variables can be called by typing ``::`` (just like text modules in the " +"frontend), as long as you're in a supported text field within the backend. " +"Zammad will display all variables being available within this context and " +"replace it to the variable as soon as you selected an entry." +msgstr "" +"Променљиве могу бити излистане уносом ``::`` (баш као и текстуални исечци у " +"корисничком интерфејсу), све док сте у оквиру подржаног поља уноса. Zammad " +"ће приказати све доступне променљиве у овом контексту и заменити у тексту " +"чим их одаберете." -#: ../settings/branding.rst:13 -msgid "Will be shown in the app and is included in email footers." -msgstr "Биће приказано у апликацији и убачено при дну имејл порука." +#: ../misc/variables.rst:15 +msgid "" +"You have an empty field which you referenced and it appears as ``-``? That's " +"currently working as designed - you might want to ensure that these fields " +"always have a value." +msgstr "" +"Референцирате на празно поље и приказује се као ``-``? Ово је очекивано " +"понашање – пробајте да обезбедите да ова поља увек имају вредност." -#: ../settings/branding.rst:19 -msgid "Logo" -msgstr "Лого" +#: ../misc/variables.rst:20 +msgid "Variable Categories" +msgstr "Категорије променљивих" -#: ../settings/branding.rst:16 -msgid "Defines the logo of the application, shown in the login page of Zammad." -msgstr "Одређује лого апликације, приказан на страници за пријаву у Zammad." +#: ../misc/variables.rst:31 +msgid "Wait, What About Custom Objects?" +msgstr "Чекај, а шта са прилагођеним објектима?" -#: ../settings/branding.rst:18 +#: ../misc/variables.rst:33 msgid "" -"Ensure to hit the \"Submit\" button after uploading the logo. Otherwise your " -"change will not be saved." +"Good point! Of course, we can't predict what objects you might create, but " +"we can give you a hint on how to put the puzzle together to get your custom " +"values." msgstr "" -"Обавезно притисните дугме „Пошаљи“ након што отпремите логотип. У супротном, " -"ваша промена неће бити сачувана." +"У праву сте! Наравно, не можемо предвидети које објекте ћете користити, али " +"можемо вам указати на то како да их уклопите и дођете до својих прилагођених " +"вредности." -#: ../settings/branding.rst:22 +#: ../misc/variables.rst:36 msgid "" -"Allows to set the default language of the Zammad instance. The here defined " -"locale mostly acts as a fallback for:" +"For this, we'll talk about the inner part of the variable (so everything " +"within ``#{}``), please put the outer part around to have a valid variable. " +"The first part of the variable name consist of the object type. Currently " +"these are:" msgstr "" -"Омогућава постављање подразумеваног језика инстанце Zammad. Овде дефинисани " -"језик углавном делује као резервни за:" +"У ову сврху, образложићемо унутрашњи део променљиве (значи све у оквиру ``#{}" +"``), молимо заградите их да бисте добили исправну променљиву. Први део " +"назива променљиве се састоји од типа објекта. Тренутно, ово укључује:" -#: ../settings/branding.rst:25 -msgid "user preferences (if Zammad can't detect the users locale)" -msgstr "" -"корисничка подешавања (ако Zammad не може да открије корисникову локацију)" +#: ../misc/variables.rst:41 +msgid "Ticket (``ticket``)" +msgstr "Тикет (``ticket``)" -#: ../settings/branding.rst:26 -msgid "CSV output (reporting, time accounting)" -msgstr "CSV излаз (извештавање, обрачунато време)" +#: ../misc/variables.rst:42 +msgid "User (``user``)" +msgstr "Корисник (``user``)" -#: ../settings/branding.rst:30 -msgid "Define the timezone of your Zammad installation." -msgstr "Дефинишите временску зону ваше инсталације Zammad-а." +#: ../misc/variables.rst:43 +msgid "Organization (``organization``)" +msgstr "Организација (``organization``)" -#: ../settings/branding.rst:32 +#: ../misc/variables.rst:44 +msgid "Group (``group``)" +msgstr "Група (``group``)" + +#: ../misc/variables.rst:46 +#, fuzzy +#| msgid "" +#| "The second part is the name of the object. This is the name you define " +#| "during object creation and can be found within the object menu at any " +#| "time. The first and second part of a variable is divided by a point, e." +#| "g.: ``ticket.number`` which will in total be ``#{ticket.number}``." msgid "" -"This does not have any effect on timings for your agents or how Zammad " -"stores date and time values." +"The second part is the name of the attribute. This is the name you define " +"during object creation and can be found within the object attribute menu at " +"any time. The first and second part of a variable is divided by a point, e." +"g.: ``ticket.number`` which will in total be ``#{ticket.number}``." msgstr "" -"Ово нема никаквог утицаја на мерење учинка ваших оператера или начин на који " -"Zammad чува вредности датума и времена." - -#: ../settings/branding.rst:35 -msgid "Changing this value has direct consequences on the following areas:" -msgstr "Промена ове вредности има директне последице на следеће области:" - -#: ../settings/branding.rst:37 -msgid ":doc:`/manage/scheduler` tasks" -msgstr "послове :doc:`планера `" - -#: ../settings/branding.rst:38 -msgid "search indexing (and thus reporting)" -msgstr "индексирање претраге (а самим тим и извештавање)" - -#: ../settings/branding.rst:40 -msgid "calendar subscriptions" -msgstr "претплате на календаре" - -#: ../settings/branding.rst:41 -msgid "browser printing" -msgstr "штампу из претраживача" +"Други део је назив објекта. Ово је назив који одређујете током додавања " +"објекта и можете га видети у било ком тренутку унутар панела објекта. Први и " +"други део променљиве су одвојени тачком, нпр.: ``ticket.number`` што на " +"крају резултује у ``#{ticket.number}``." -#: ../settings/branding.rst:43 +#: ../misc/variables.rst:51 msgid "" -"Please note that some of above are fallbacks in case Zammad could not detect " -"the agents timezone correctly." +"Now, in some situations it's possible that you'll need to use a third part. " +"The best example for such a situation would be a ``select`` or ``tree-" +"select`` field which will by default return the key value, not it's display " +"name. For this, just extend your variable with ``.value``. This will result " +"in ``#{ticket.select.value}``." msgstr "" -"Имајте на уму да су неке ставке изнад резервне опције у случају да Zammad не " -"може да прецизно открије временску зону оператера." +"У неким ситуацијама, можда ће вам бити неопходан и трећи део. Најбољи пример " +"за ову ситацију је ``select`` или ``tree-select`` поље које подразумевано " +"враћа вредност кључа, а не назив за приказ. Да бисте приступили овој " +"вредности, само продужите вашу променљиву са ``.value``. Ово ће резултовати " +"у ``#{ticket.select.value}``." -#: ../settings/branding.rst:77 -msgid "Pretty Date" -msgstr "Лепши формат датума" +#: ../misc/variables.rst:60 +msgid "Using Translated Variables" +msgstr "Коришћење преведених променљивих" -#: ../settings/branding.rst:47 +#: ../misc/variables.rst:62 msgid "" -"This setting allows you to define how Zammad should display time stamps " -"within the interface to all users." +"If you want to use a translated variable in triggers or schedulers, you can " +"extend the placeholder like this: ``#{t(ticket.state.name)}``. The ``t`` " +"tells Zammad to search for fitting translated strings. The used output " +"language is based on the system language of Zammad which you can set in the " +"admin panel under :doc:`/settings/branding` or based on the selected locale " +"in the trigger/scheduler edit dialog." msgstr "" -"Ова поставка вам омогућава да одредите како Zammad треба да приказује " -"временске ознаке унутар интерфејса за све кориснике." +"Ако желите да користите преведене променљиве у окидачима или планеерима, " +"можете проширити поље променљиве на следећи начин: ``#{t(ticket.state.name)}" +"``. Функција ``t`` ће потражити међу одговарајућим преводима. Циљни језик је " +"базиран на основу системског језика Zammad-а који можете подесити у панелу " +"администратора под :doc:`брендингом ` или на основу " +"одабраног језика у дијалогу окидача/планера." -#: ../settings/branding.rst:50 +#: ../misc/variables.rst:69 msgid "" -"This does not have any effect on how Zammad returns e.g. time values via " -"variables." +"A possible use-case: you want to send your customers updates on tickets via " +"trigger or scheduler which should include the state of the ticket. Using the " +"default ``#{ticket.state.name}`` (without the translation flag ``t()``) " +"would lead to the output of the original (english) name of the state." msgstr "" -"Ово нема никаквог утицаја на то како се Zammad враћа нпр. временске " -"вредности путем променљивих." - -#: ../settings/branding.rst:77 -msgid "Choose in between the following options:" -msgstr "Изаберите између следећих опција:" +"Могући случај употребе: ако желите да пошаљете својим клијентима обавештења " +"о тикетима путем окидача или планера која укључују и стање тикета. Коришћење " +"подразумеване променљиве `#{ticket.state.name}`` (без функције превода " +"``t()``) ће резултовати у вредности назива стања на оригиналном (енглеском) " +"језику." -#: ../settings/branding.rst:64 -msgid "relative" -msgstr "релативно" +#: ../misc/variables.rst:75 +msgid "Date and Time Formatting" +msgstr "Форматирање датума и времена" -#: ../settings/branding.rst:55 +#: ../misc/variables.rst:77 msgid "" -"This timestamp shows a relative time span until it switches to a date. Over " -"time, it will change as follows:" +"The system (trigger/scheduler selected) locale and timezone predefines a " +"default format of date and timestamp. This format is customizable by using " +"the ``dt()`` method." msgstr "" -"Ова временска ознака приказује релативни период до достизања датума. " -"Временом ће се мењати на следећи начин:" - -#: ../settings/branding.rst:58 -msgid "just now" -msgstr "малопре" +"Језик и временска зона система одређују подразумевани формат датума и " +"времена. Овај формат може бити прилагођен коришћењем ``dt()``функције." -#: ../settings/branding.rst:59 -msgid "5 minutes ago" -msgstr "пре 5 минута" +#: ../misc/variables.rst:79 +msgid "The method arguments are as follows:" +msgstr "Параметри функције су следећи:" -#: ../settings/branding.rst:60 -msgid "3 days 1 hour ago" -msgstr "пре 3 дана 1 сат" +#: ../misc/variables.rst:81 +msgid "The date or timestamp variable you want to format." +msgstr "Променљива датума или временске ознаке коју желите да форматирате." -#: ../settings/branding.rst:61 -msgid "``03/04/2022``" -msgstr "``03/04/2022``" +#: ../misc/variables.rst:82 +msgid "The output format string." +msgstr "Формаз излазног низа текста." -#: ../settings/branding.rst:63 -msgid "Hovering the timestamp helps, you'll always get a clean timestamp then." -msgstr "" -"Преласком курсора преко временске ознаке увек ћете добити прецизну временску " -"ознаку." +#: ../misc/variables.rst:83 +msgid "The timezone to apply (optional)." +msgstr "Временска зона за примену (необавезно)." -#: ../settings/branding.rst:71 -msgid "absolute" -msgstr "апсолутно" +#: ../misc/variables.rst:85 +#: ../system/objects/external-data-source-example.rst:23 +msgid "**Example:**" +msgstr "**Пример:**" -#: ../settings/branding.rst:67 +#: ../misc/variables.rst:86 msgid "" -"This timestamp always includes the week day. For one week after creation, " -"the timestamp will not contain the date itself: Thursday 18:35." +"``#{dt(ticket.updated_at, \"%A %Y-%m-%d %H:%M in the office\", \"Europe/" +"Berlin\")}``" msgstr "" -"Ова временска ознака увек укључује дан у недељи. Недељу дана након додавања " -"временска ознака неће садржати сам датум: четвртак 18:35." - -#: ../settings/branding.rst:71 -msgid "After a week it will switch to: ``Friday 4. Mar 16:00``." -msgstr "После недељу дана прелази на следеће: петак 4. март 16:00." +"``#{dt(ticket.updated_at, \"%A %Y-%m-%d %H:%M у канцеларији\", \"Europe/" +"Berlin\")}``" -#: ../settings/branding.rst:76 -msgid "timestamp" -msgstr "временска ознака" +#: ../misc/variables.rst:87 +msgid "Monday, 2024-03-18 15:31 in the office" +msgstr "Понедељак, 2024-03-18 15:31 у канцеларији" -#: ../settings/branding.rst:74 +#: ../misc/variables.rst:89 msgid "" -"This will cause Zammad to show a complete timestamp according to your locale " -"defaults. For English this could be e.g. ``2022/12/03 2:40 pm`` or for " -"German e.g. ``12.03.2022 14:40``." +"If you want to use our example, make sure to paste the string above without " +"formatting (``CTRL+Shift+v``), otherwise it won't work." msgstr "" -"Ово ће довести до тога да Zammad прикаже комплетну временску ознаку у складу " -"са вашом подразумеваном локацијом. За енглески ово би значило нпр. " -"``2022/12/03 2:40 pm`` или за немачки нпр. ``12.03.2022 14:40``." +"Уколико желите да користите наш пример, обавезно налепите текст изнад без " +"формата (``Ctrl+Shift+v``), у супротном неће успети." -#: ../settings/branding.rst:78 -msgid "Default setting: ``relative``." -msgstr "Подразумевана поставка: ``релативно``." +#: ../misc/variables.rst:93 +msgid "The following table lists available format directives:" +msgstr "Следећа табела приказује доступне директиве формата:" -#: ../settings/security.rst:2 -msgid "Security" -msgstr "Безбедност" +#: ../misc/variables.rst:99 +msgid "Parameter" +msgstr "Параметар" -#: ../settings/security.rst:4 -msgid "" -"For your overview we split each tab within security settings into its own " -"page:" -msgstr "" -"Ради бољег прегледа поделили смо сваки језичак унутар безбедносних " -"подешавања на сопствену страницу:" +#: ../misc/variables.rst:102 +msgid "``%Y``" +msgstr "``%Y``" -#: ../settings/security/base.rst:2 ../settings/system/base.rst:2 -#: ../settings/ticket.rst:8 -msgid "Base" -msgstr "Основе" +#: ../misc/variables.rst:103 +msgid "Year with 4 digits" +msgstr "Година са 4 цифре" -#: ../settings/security/base.rst:5 -msgid "New User Accounts" -msgstr "Нови кориснички налози" +#: ../misc/variables.rst:104 +msgid "Use ``%y`` for year with 2 digits" +msgstr "Користите ``%y`` за годину са 2 цифре" -#: ../settings/security/base.rst:9 -msgid "" -"Activates the `register as a new customer` function on the login page. If " -"set to ``no`` only administrators or agents can create new accounts manually." -msgstr "" -"Активира функцију `Региструј се као нови клијент` на страници за пријаву. " -"Ако је подешено на ``не`` само администратори или оператер могу ручно да " -"додају нове налоге." +#: ../misc/variables.rst:105 +msgid "``%m``" +msgstr "``%m``" -#: ../settings/security/base.rst:13 ../settings/security/base.rst:38 -#: ../settings/security/base.rst:66 -msgid "Default setting: ``yes``" -msgstr "Подразумевано подешавање: ``да``" +#: ../misc/variables.rst:106 +msgid "Month of year (as number with zero-padding)" +msgstr "Месец године (као број са допуном нула)" -#: ../settings/security/base.rst:0 -msgid "Figure showing activated \"New User Accounts\" setting" -msgstr "Слика која приказује укључено подешавање „Нови кориснички налози“" +#: ../misc/variables.rst:107 +msgid "Use ``%-m`` for month without zero-padding" +msgstr "Користите ``%-m`` за месец без допуне нула" -#: ../settings/security/base.rst:22 -msgid "" -"Deactivation of above function **does not** deactivate automatic account " -"creation! This means: If a user writes e.g. an email to Zammad and has no " -"account yet, Zammad will automatically create the account. User accounts are " -"a direct dependency of tickets and thus technically mandatory." -msgstr "" -"Искључивање горње функције **не** деактивира аутоматско додавање налога! То " -"значи: ако корисник нпр. пошаље имејл поруку Zammad-у и још увек нема налог, " -"Zammad ће аутоматски додати нови налог." +#: ../misc/variables.rst:108 +msgid "``%d``" +msgstr "``%d``" -#: ../settings/security/base.rst:29 -msgid "Lost Password" -msgstr "Изгубљена лозинка" +#: ../misc/variables.rst:109 +msgid "Day of month (as number with zero-padding)" +msgstr "Дан месеца (као број са допуном нула)" -#: ../settings/security/base.rst:33 -msgid "" -"Activates the `lost password` function on the login page. If set to ``no`` " -"only administrators may change the user's password - users may update their " -"own password if they're still logged in and they have the required :doc:" -"`permission `." -msgstr "" -"Активира функцију `Изгубљена лозинка` на страници за пријаву. Ако је " -"подешено на ``не`` само администратори могу да промене корисничку лозинку - " -"корисници могу да промене сопствену лозинку ако су још увек пријављени и " -"имају потребну :doc:`дозволу `." +#: ../misc/variables.rst:110 +msgid "Use ``%e`` for day without zero-padding" +msgstr "Користите ``%e`` за дан без допуне нула" -#: ../settings/security/base.rst:0 -msgid "Figure showing activated \"Lost Password\" setting" -msgstr "Слика која приказује укључено подешавање „Изгубљена лозинка“" +#: ../misc/variables.rst:111 +msgid "``%H``" +msgstr "``%H``" -#: ../settings/security/base.rst:49 -msgid "" -"With third party authentications - but especially LDAP - you may want to " -"disable this function. Zammad **will not** change third party login " -"passwords and instead set or change the local password!" -msgstr "" -"Уз аутентификацију преко трећег лица – али посебно LDAP – можда ћете " -"пожелети да искључите ову функцију. Zammad **неће** променити лозинке за " -"пријављивање преко трећих лица и уместо тога ће поставити или променити " -"локалну лозинку!" - -#: ../settings/security/base.rst:56 -msgid "Password Login" -msgstr "Пријављивање путем лозинке" - -#: ../settings/security/base.rst:60 -msgid "" -"Activates the username & password login by default and if no third-party " -"login is activated. Disabling password login on the Zammad login page only " -"takes effect if you enable any :doc:`third-party`." -msgstr "" -"Омогућује пријаву путем корисничког имена и лозинке уколико нема укључених " -"пријава преко трећег лица. Искључивање пријављивања путем лозинке на Zammad " -"страници за пријаву ступа на снагу само ако омогућите било коју пријаву " -"преко :doc:`трећег лица `." - -#: ../settings/security/base.rst:64 -msgid "See :doc:`third-party` for supported third-party logins." -msgstr "" -"Погледајте :doc:`овде ` за подржане опције пријаве преко трећих " -"лица." +#: ../misc/variables.rst:112 +msgid "Hour of day in 24h notation with zero-padding" +msgstr "Час дана у 24-часовном формату са допуном нула" -#: ../settings/security/base.rst:0 -msgid "Figure showing de-activated \"Password Login\" setting" -msgstr "Слика која приказује искључено подешавање „Пријављивање путем лозинке“" +#: ../misc/variables.rst:113 +msgid "Use ``%k`` for hour without zero-padding" +msgstr "Користите ``%k`` за час без допуне нула" -#: ../settings/security/base.rst:77 -msgid "" -"To help administrators to overcome \"login issues\", Zammad automatically " -"offers a password request for administrator users. This allows you to adjust " -"Third-Party applications even if the login does no longer work!" -msgstr "" -"Да би помогао администраторима да превазиђу „проблеме са пријављивањем“, " -"Zammad аутоматски нуди пријаву привременом лозинком администраторе. Ово вам " -"омогућава да подесите апликације трећег лица чак и ако пријава уопште не " -"функционише!" +#: ../misc/variables.rst:114 +msgid "``%I``" +msgstr "``%I``" -#: ../settings/security/base.rst:84 -msgid "Session Timeout" -msgstr "Време истека сесије" +#: ../misc/variables.rst:115 +msgid "Hour of day in 12h notation with zero-padding" +msgstr "Час дана у 12-часовном формату са допуном нула" -#: ../settings/security/base.rst:86 +#: ../misc/variables.rst:116 msgid "" -"All settings below by default are set to ``4 weeks``. Session Timeout " -"defines the life time of a users session. As soon as it's reached, Zammad " -"will automatically log off the session in question." +"Use ``%l`` for hour without zero-padding and ``%p`` / ``%P`` for meridian " +"indicator" msgstr "" -"Сва подешавања испод су подразумевано подешена на ``4 недеље``. Временско " -"ограничење сесије дефинише време трајања сесије корисника. Чим се достигне, " -"Zammad ће аутоматски одјавити дотичну сесију." +"Користите ``%l`` за час без допуне нула и ``%p`` / ``%P`` за индикатор " +"меридијана" -#: ../settings/security/base.rst:91 -msgid "" -"Zammad takes the highest value set assigned for the user based on the " -"permissions." -msgstr "" -"Zammad узима највишу вредност која је додељена кориснику на основу дозвола." +#: ../misc/variables.rst:117 +msgid "``%M``" +msgstr "``%M``" -#: ../settings/security/base.rst:94 -msgid "``admin``" -msgstr "``admin``" +#: ../misc/variables.rst:118 +msgid "Minute of hour" +msgstr "Минут часа" -#: ../settings/security/base.rst:96 -msgid "``ticket.customer``" -msgstr "``ticket.customer``" +#: ../misc/variables.rst:120 +msgid "``%S``" +msgstr "``%S``" -#: ../settings/security/base.rst:97 -msgid "``default`` (fallback if user doesn't have above permissions set)" -msgstr "``подразумевано`` (замена ако корисник нема постављене дозволе изнад)" +#: ../misc/variables.rst:121 +msgid "Second of Minute" +msgstr "Секунда минута" -#: ../settings/security/base.rst:99 -msgid "" -"All settings act independently from each other allowing you to disable the " -"timeouts for e.g. admins, but not agents." -msgstr "" -"Сва подешавања делују независно једно од другог омогућавајући вам да " -"искључите временска ограничења за нпр. администраторе, али не и оператере." +#: ../misc/variables.rst:123 +msgid "``%A``" +msgstr "``%A``" -#: ../settings/security/base.rst:115 -#: ../system/integrations/checkmk/api-reference.rst:13 -msgid "Example" -msgstr "Пример" +#: ../misc/variables.rst:124 +msgid "Weekday name" +msgstr "Назив дана у недељи" -#: ../settings/security/base.rst:107 -msgid "Let's suppose you configured the following session timeouts" -msgstr "Претпоставимо да сте подесили следећа временска ограничења сесије" +#: ../misc/variables.rst:125 +msgid "Use ``%a`` for abbreviated name or ``%^A`` for uppercase name" +msgstr "Користите ``%a`` за скраћеницу или ``%^A`` за велика слова" -#: ../settings/security/base.rst:104 -msgid "default: 3 weeks" -msgstr "подразумевано: 3 недеље" +#: ../misc/variables.rst:126 +msgid "``%B``" +msgstr "``%B``" -#: ../settings/security/base.rst:105 -msgid "admin: 2 weeks" -msgstr "admin: 2 недеље" +#: ../misc/variables.rst:127 +msgid "Month name" +msgstr "Назив месеца" -#: ../settings/security/base.rst:106 -msgid "ticket.agent: 4 weeks" -msgstr "ticket.agent: 4 недеље" +#: ../misc/variables.rst:128 +msgid "Use ``%b`` for abbreviated name" +msgstr "Користите ``%b`` за скраћеницу" -#: ../settings/security/base.rst:107 -msgid "ticket.customer: 1 week" -msgstr "ticket.customer: 1 недеља" +#: ../misc/variables.rst:129 +msgid "``%U``" +msgstr "``%U``" -#: ../settings/security/base.rst:115 -msgid "This results in the following situations" -msgstr "Ово резултира следећим ситуацијама" +#: ../misc/variables.rst:130 +msgid "Week number of current year" +msgstr "Број недеље у текућој години" -#: ../settings/security/base.rst:110 -msgid "a user with ``admin`` permission will have a timeout of 2 weeks" -msgstr "корисник са дозволом ``admin`` имаће временско ограничење од 2 недеље" +#: ../misc/variables.rst:131 +msgid "Use ``%W`` for a different calculation method" +msgstr "Користите ``%W`` за другачији обрачун" -#: ../settings/security/base.rst:111 +#: ../misc/variables.rst:134 msgid "" -"a user with ``admin`` and ``ticket.agent`` permissions will have a timeout " -"of 2 weeks" +"We support the known format directives for the Ruby built-in method " +"``strftime`` of the ``DateTime`` class. For more information, see `here " +"`_." msgstr "" -"корисник са дозволама ``admin`` и ``ticket.agent`` имаће временско " -"ограничење од 2 недеље" +"Подржане су све директиве Ruby метода ``strftime`` из DateTime`` класе. За " +"више информације, погледајте `овде `_." -#: ../settings/security/base.rst:113 -msgid "" -"a user with ``ticket.customer`` permission will have a timeout of 1 week" -msgstr "" -"корисник са дозволом ``ticket.customer`` имаће временско ограничење од 1 " -"недеље" +#: ../misc/variables/article.rst:2 +msgid "Articles" +msgstr "Чланци" -#: ../settings/security/base.rst:115 +#: ../misc/variables/article.rst:4 ../misc/variables/config.rst:4 +#: ../misc/variables/current-user.rst:4 ../misc/variables/ticket.rst:4 msgid "" -"a user with neither ``admin``, ``ticket.agent`` nor ``ticket.customer`` " -"permissions will have a timeout of 3 weeks" +"If you're missing variables or are not sure if something is not working as " +"expected, feel free to ask over at the `Community `_." msgstr "" -"корисник који нема дозволе ни за ``admin``, ``ticket.agent`` ни за ``ticket." -"customer`` имаће временско ограничење од 3 недеље" +"Ако вам недостају променљиве или нисте сигурни да ли нешто функционише на " +"очелован начин, слободно питајте у `Community форуму `_." -#: ../settings/security/password.rst:4 +#: ../misc/variables/article.rst:6 +#, fuzzy +#| msgid "" +#| "Below you can find all available ticket article-based variables within " +#| "Zammad. These can be called via Triggers for example. If you're unsure if " +#| "Zammad does support variables at the point you're at, you can try to type " +#| "``::`` to check." msgid "" -"This section allows you to define password requirements for the local user " -"accounts." +"Below you can find all available ticket article-based variables within " +"Zammad. These can be called via triggers for example. If you're unsure if " +"Zammad does support variables at the point you're at, you can try to type " +"``::`` to check." msgstr "" -"Овај одељак вам омогућава да подесите понашање лозинке за локалне корисничке " -"налоге." +"Испод можете пронажи све доступне променљиве чланака тикета у оквиру Zammad-" +"а. Могу се користити унутар нпр. окидача. Ако нисте сигурни да ли Zammad " +"подржава променљиве у делу у коме се налазите, пробајте да откуцате ``::``да " +"бисте проверили." -#: ../settings/security/password.rst:9 +#: ../misc/variables/article.rst:9 ../misc/variables/config.rst:9 +#: ../misc/variables/ticket.rst:9 msgid "" -"Zammad does **not** allow you to change your LDAP password, instead, it will " -"set a password in its local database which might confuse your users. This " -"might be addressed in the future by `#1169 `_." +"The below list gives you an example what kind of data you can expect, it's " +"not intended to explain the data itself." msgstr "" -"Zammad вам **не** дозвољава да промените своју LDAP лозинку, већ ће " -"поставити лозинку у својој локалној бази података која би могла збунити ваше " -"кориснике. Овим ће се убудуће бавити `#1169 `_." +"Листа испод вам пружа пример какав тип података можете очекивати, није јој " +"циљ да објасни саме податке." -#: ../settings/security/password.rst:14 -msgid "**Exception for admins**" -msgstr "**Изузетак за администраторе**" +#: ../misc/variables/article.rst:11 +msgid "Article Variables" +msgstr "Променљиве чланка" -#: ../settings/security/password.rst:16 -msgid "" -"Please note that below password policies *do not* affect administrators " -"setting passwords on user accounts. While this seems strange and not safe we " -"believe that an administrator knowing an user's password is insecure as well." -msgstr "" -"Имајте на уму да доле наведени захтеви за јачину лозинке *не* утичу на " -"администраторе који постављају лозинке на корисничким налозима. Иако ово " -"изгледа чудно и небезбедно, верујемо да је и администратор који зна лозинку " -"корисника такође небезбедан." +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "name" +msgstr "назив" -#: ../settings/security/password.rst:21 -msgid "The suggested workflow is either:" -msgstr "Предложени радни ток је или:" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "variable" +msgstr "променљива" -#: ../settings/security/password.rst:23 -msgid "" -"to use third party logins to not require local passwords at all **- or -**" -msgstr "" -"да користите пријаве преко трећег лица тако да уопште не захтевате локалне " -"лозинке **- или -**" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "example" +msgstr "пример" -#: ../settings/security/password.rst:25 -msgid "to require your *user to reset the password* upon first login." -msgstr "" -"да захтевате од *корисника да поништи лозинку* приликом првог пријављивања." +#: ../misc/variables/article.rst:1 +msgid "Article > Cc" +msgstr "Чланак > Cc" -#: ../settings/security/password.rst:27 -msgid "" -"This way administrators are not required to set a user's password at all!" -msgstr "" -"На овај начин администратори уопште нису обавезни да постављају корисничку " -"лозинку!" +#: ../misc/variables/article.rst:1 +msgid "``#{article.cc}``" +msgstr "``#{article.cc}``" -#: ../settings/security/password.rst:31 -msgid "Maximum Failed Logins" -msgstr "Максимални број неуспешних пријава" +#: ../misc/variables/article.rst:1 +msgid "``jdoe@example.com, company@example.com``" +msgstr "``jdoe@example.com, company@example.com``" -#: ../settings/security/password.rst:33 -msgid "" -"You can choose a value between ``4`` and ``20``. This defines how often a " -"login to a user account may fail until Zammad will lock it. Your users can " -"always use the \"forgot password\" function to change their password and " -"unlock their account." -msgstr "" -"Можете да изаберете вредност између ``4`` и ``20``. Ово одређује колико " -"често пријављивање на кориснички налог може бити неуспешно док га Zammad не " -"закључа. Ваши корисници увек могу да користе функцију „изгубљена лозинка“ да " -"промене своју лозинку и откључају свој налог." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Address" +msgstr "Чланак > Додато од стране > Адреса" -#: ../settings/security/password.rst:38 -msgid "The default value is ``10``." -msgstr "Подразумевана вредност је ``10``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.address}``" +msgstr "``#{article.created_by.address}``" -#: ../settings/security/password.rst:42 -msgid "Beside changing the user's password, you can also unlock accounts via" -msgstr "Поред промене корисничке лозинке, налоге можете откључати и преко" +#: ../misc/variables/article.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set in user object" +msgstr "" +"``Назив неке улице 1, 12345 Берлин`` или празно ако није постављено у " +"објекту корисника" -#: ../settings/security/password.rst:44 -msgid ":ref:`user management list `" -msgstr ":ref:`листе за управљање корисницима `" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Department" +msgstr "Чланак > Додато од стране > Одељење" -#: ../settings/security/password.rst:45 -msgid ":docs:`console `" -msgstr ":docs:`конзоле `" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.department}``" +msgstr "``#{article.created_by.department}``" -#: ../settings/security/password.rst:46 -msgid ":docs:`API `" -msgstr ":docs:`API-ја `" +#: ../misc/variables/article.rst:1 +msgid "``Sales`` or empty if not set in user object" +msgstr "``Sales`` или празно ако није постављено у објекту корисника" -#: ../settings/security/password.rst:50 -msgid "Failed logins via LDAP no longer lock accounts." -msgstr "Неуспеле пријаве преко LDAP-а више не закључавају налоге." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Email" +msgstr "Чланак > Додато од стране > Имејл" -#: ../settings/security/password.rst:53 -msgid "2 Lower Case And 2 Upper Case Characters" -msgstr "2 мала и 2 велика слова" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.email}``" +msgstr "``#{article.created_by.email}``" -#: ../settings/security/password.rst:55 -msgid "" -"You can add complexity to passwords by enforcing at least 2 upper and lower " -"case characters." -msgstr "" -"Лозинкама можете додати сложеност тако што ћете применити најмање 2 велика и " -"мала слова." +#: ../misc/variables/article.rst:1 +msgid "``jdoe@example.com``" +msgstr "``jdoe@example.com``" -#: ../settings/security/password.rst:58 ../settings/security/password.rst:83 -msgid "The default value is ``no``." -msgstr "Подразумевана вредност је ``не``." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Fax" +msgstr "Чланак > Додато од стране > Факс" -#: ../settings/security/password.rst:62 -msgid "Minimum Length" -msgstr "Минимална дужина" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.fax}``" +msgstr "``#{article.created_by.fax}``" -#: ../settings/security/password.rst:64 -msgid "" -"This defines the minimum password length required for users to provide (from " -"``4`` to ``20``)." -msgstr "" -"Ово одређује минималну дужину лозинке коју корисници морају дати (од ``4`` " -"до ``20``)." +#: ../misc/variables/article.rst:1 +msgid "``+4930123456789`` or empty if not set in user object" +msgstr "``+4930123456789`` или празно ако није постављено у објекту корисника" -#: ../settings/security/password.rst:67 -msgid "The default value is ``6``." -msgstr "Подразумевана вредност је ``6``." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Firstname" +msgstr "Чланак > Додато од стране > Име" -#: ../settings/security/password.rst:71 -msgid "Digit Required" -msgstr "Неопходна цифра" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.firstname}``" +msgstr "``#{article.created_by.firstname}``" -#: ../settings/security/password.rst:73 -msgid "This enforces your users to use at least one digit within the password." -msgstr "" -"Ово приморава ваше кориснике да користе најмање једну цифру унутар лозинке." +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Joe`` or empty if not set" +msgstr "``Joe`` или празно ако није постављено" -#: ../settings/security/password.rst:75 -msgid "The default value is ``yes``." -msgstr "Подразумевана вредност је ``да``." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Lastname" +msgstr "Чланак > Додато од стране > Презиме" -#: ../settings/security/password.rst:78 -msgid "Special Character Required" -msgstr "Неопходан специјални знак" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.lastname}``" +msgstr "``#{article.created_by.lastname}``" -#: ../settings/security/password.rst:80 -msgid "" -"This setting allows you to improve your password quality even more by " -"enforcing the password to contain at least one special character." -msgstr "" -"Ово подешавање вам омогућава да још више побољшате квалитет својих лозинки " -"тако што ћете захтевати да лозинка садржи најмање један посебан знак." +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +#: ../misc/variables/ticket.rst:1 +msgid "``Doe`` or empty if not set" +msgstr "``Doe`` или празно ако није постављено" -#: ../settings/security/ssl-certificates.rst:2 -msgid "SSL Certificates" -msgstr "SSL сертификати" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Login" +msgstr "Чланак > Додато од стране > Пријава" -#: ../settings/security/ssl-certificates.rst:7 -msgid "" -"Zammad offers the possibility to upload custom certificates and custom " -"Certificate Authority (CA) certificates. This can be useful if you want to " -"connect Zammad the secure way to other systems which are using custom " -"certificates." -msgstr "" -"Zammad вам омогућава да отпремите прилагођене сертификате и сертификате " -"органа за сертификацију (CA). Ово може бити корисно ако желите да повежете " -"Zammad на безбедан начин са другим системима који користе прилагођене " -"сертификате." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.login}``" +msgstr "``#{article.created_by.login}``" -#: ../settings/security/ssl-certificates.rst:12 -msgid "" -"An example usecase might be: You have an internal LDAP server that is not " -"accessible from the internet, and you want a SSL-encrypted connection, using " -"a custom certificate." -msgstr "" -"Пример употребе би могао бити: имате интерни LDAP сервер који није видљив на " -"интернту, и желите да се повежете путем шифроване SSL конекције, користећи " -"прилагођени сертификат." +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +#: ../misc/variables/ticket.rst:1 +msgid "``jdoe``" +msgstr "``jdoe``" -#: ../settings/security/ssl-certificates.rst:19 -msgid "" -"You should have an existing custom certificate file and/or a custom CA " -"certificate file, which you want to add to Zammad. As filetype ``.crt`` is " -"supported and the certificate format has to be PEM (Base64 ASCII)." -msgstr "" -"Требаже вам постојећи прилагођени сертификат и прилагођени CA сертификат " -"које желите да додате у Zammad. Подрђан формат датотеке је ``.crt`` и формат " -"сертификата мора бити PEM (Base64 ASCII)." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Mobile" +msgstr "Чланак > Додато од стране > Мобилни" -#: ../settings/security/ssl-certificates.rst:25 -msgid "" -"When you import a custom CA certificate, all certificates generated with " -"this are trusted. This can be useful if you have more than one system/" -"certificate you want to connect to and the certificates are issued from the " -"same custom CA." -msgstr "" -"Када увезете прилагођени CA сертификат, сви сертификати генерисани путем " -"њега биће признати. Ово може бити корисно ако имате више од једног система " -"које желите да повежете и сертификати су издати одстране истог прилагођеног " -"CA." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.mobile}``" +msgstr "``#{article.created_by.mobile}``" -#: ../settings/security/ssl-certificates.rst:31 -msgid "Add a Certificate" -msgstr "Додавање сертификата" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Note" +msgstr "Чланак > Додато од стране > Напомена" -#: ../settings/security/ssl-certificates.rst:33 -msgid "" -"To add a custom certificate or a custom CA certificate, head over to the " -"Admin panel > Settings > Security > SSL Certificates. Here you can find a " -"\"Add SSL Certificate\" button. In the dialog you can either select a " -"certificate file or paste the content of the certificate:" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.note}``" +msgstr "``#{article.created_by.note}``" + +#: ../misc/variables/article.rst:1 +msgid "``Some note about user`` or empty if not set in user object" msgstr "" -"За додавање прилагођеног сертификата или прилагођеног CA сертификата, " -"упутите се на панел Администрација > Подешавања > Безбедност > SSL " -"сертификати. Тамо можете пронађи дугме „Додај SSL сертификат”. У дијалогу " -"можете одабрати или да отпремите датотеку сертификата или да налепите " -"садржај сертификата:" +"``Нека напомена о кориснику`` или празно ако није постављено у објекту " +"корисника" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate adding dialog" -msgstr "Снимак екрана који приказује дијалог за додавање сертификата" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Phone" +msgstr "Чланак > Додато од стране > Телефон" -#: ../settings/security/ssl-certificates.rst:43 -msgid "" -"After selecting a file or pasting the content of the certificate, click on " -"the \"Add\" button to finally upload it to Zammad. Then, the certificates " -"are immediately effective, no restart or similar required." -msgstr "" -"По одабиру датотеке или налепљивању садржаја сертификата, кликните на дугме " -"„Додај” да бисте га отпремили у Zammad. Након тога, сертификати се одмах " -"користе, није неопходно рестартовање или слично." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.phone}``" +msgstr "``#{article.created_by.phone}``" -#: ../settings/security/ssl-certificates.rst:49 -msgid "" -"Please note that only single certificate files are supported. That means if " -"you want to import a certificate / CA certificate, it must contain **only " -"one** certificate." -msgstr "" -"Обратите пажњу да су подржане само датотеке са појединачним сертификатима. " -"Ово значи да ако желите да увезете сертификат / CA сертификат путем " -"датотеке, мора садржати *само један** сертификат." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > VIP" +msgstr "Чланак > Додато од стране > VIP" -#: ../settings/security/ssl-certificates.rst:54 -msgid "Certificate Overview" -msgstr "Преглед сертификата" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.vip}``" +msgstr "``#{article.created_by.vip}``" -#: ../settings/security/ssl-certificates.rst:56 -msgid "" -"After you added a certificate, you can see a table with information for each " -"added certificate:" -msgstr "" -"По додавању сертификата, можете видети табелу са информацијама за сваки " -"додати сертификат:" +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +msgid "``true`` or ``false``" +msgstr "``true`` или ``false``" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing table of added certificates" -msgstr "Снимак екрана који приказује табелу додатих сертификата" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Web" +msgstr "Чланак > Додато од стране > Веб" -#: ../settings/security/ssl-certificates.rst:64 -msgid "" -"Here you can download the certificate or delete it, if you don't need it " -"anymore." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.web}``" +msgstr "``#{article.created_by.web}``" + +#: ../misc/variables/article.rst:1 +msgid "``https://zammad.com`` or empty if not set in user object" msgstr "" -"Овде можете преузети и обрисати сертификате, ако вам више нису потребни." +"``https://zammad.com`` или празно ако није постављено у објекту корисника" -#: ../settings/security/ssl-certificates.rst:68 -msgid "Deleting Certificates" -msgstr "Брисање сертификата" +#: ../misc/variables/article.rst:1 +msgid "Article > Created" +msgstr "Article > Додато у" -#: ../settings/security/ssl-certificates.rst:70 -msgid "" -"If you want to delete a specific certificate, you can do it by clicking on " -"the menu in the actions column and selecting delete:" -msgstr "" -"Ако желите да обришете сертификат, то можете учинити кликом на мени у колони " -"радњи и избором брисања:" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_at}``" +msgstr "``#{article.created_at}``" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate deletion button" -msgstr "СНимак екрана који приказује дугме за брисање сертификата" +#: ../misc/variables/article.rst:1 +msgid "``2019-10-08 15:24:47 UTC``" +msgstr "``2019-10-08 15:24:47 UTC``" -#: ../settings/security/ssl-certificates.rst:79 -msgid "Downloading Certificates" -msgstr "Преузимање сертификата" +#: ../misc/variables/article.rst:1 +msgid "Article > From" +msgstr "Чланак > Од" -#: ../settings/security/ssl-certificates.rst:81 -msgid "" -"If you want to download your certificates, you can do this as well via " -"corresponding action buttons." -msgstr "" -"Ако желите да преузмете ваше сертификате, то можете урадити путем " -"одговарајућих дугмића радњи." +#: ../misc/variables/article.rst:1 +msgid "``#{article.from}``" +msgstr "``#{article.from}``" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate download button" -msgstr "Снимак екрана који приказује дугме за преузимање сертификата" +#: ../misc/variables/article.rst:1 +msgid "" +"``Joe Doe `` may differ, depends on ``FROM`` of send mail" +msgstr "" +"``Joe Doe `` може бити различито, зависи од ``FROM`` " +"атрибута имејл поруке" -#: ../settings/security/third-party.rst:13 -msgid "Login Providers" -msgstr "Провајдери за пријављивање" +#: ../misc/variables/article.rst:1 +msgid "Article > Sender > Name" +msgstr "Чланак > Пошиљалац > Назив" -#: ../settings/security/third-party.rst:2 -msgid "Third-Party Applications" -msgstr "Апликације трећег лица" +#: ../misc/variables/article.rst:1 +msgid "``#{article.sender.name}``" +msgstr "``#{article.sender.name}``" -#: ../settings/security/third-party.rst:4 -msgid "" -"Third party authentication is a great way to help your users to login to " -"Zammad more easily. If the account is yet unknown, Zammad will create a new " -"user automatically, without the user needed to interact (e.g. type in his " -"name). Another big advantage of this feature is that your user doesn't need " -"to remember another password." -msgstr "" -"Провера аутентичности преко трећег лица је одличан начин да помогнете својим " -"корисницима да се лакше пријаве на Zammad. Ако налог још увек није познат, " -"Zammad ће аутоматски додати новог корисника, без потребе за интеракцијом " -"корисника (нпр. укуцавањем њиховог имена). Још једна велика предност ове " -"функције је да ваш корисник не мора да памти додатну лозинку." +#: ../misc/variables/article.rst:1 +msgid "``Customer``, ``Agent`` or ``System``" +msgstr "``Customer``, ``Agent`` или ``System``" -#: ../settings/security/third-party.rst:10 -msgid "" -"You can deactivate logging in via :ref:`security_password_login` if any of " -"the mentioned authentication providers are enabled in your instance." -msgstr "" -"Можете искључити :ref:`пријављивање путем лозинке ` " -"ако је било који од наведених провајдера аутентификације омогућен у вашој " -"инстанци." +#: ../misc/variables/article.rst:1 +msgid "Article > Subject" +msgstr "Чланак > Предмет" -#: ../settings/security/third-party.rst:27 -msgid "" -"We're currently missing documentation for the following login providers:" -msgstr "" -"Тренутно нам недостаје документација за следеће провајдере за пријављивање:" +#: ../misc/variables/article.rst:1 +msgid "``#{article.subject}``" +msgstr "``#{article.subject}``" -#: ../settings/security/third-party.rst:29 -msgid "LinkedIn" -msgstr "LinkedIn" +#: ../misc/variables/article.rst:1 +msgid "``My amazing subject``" +msgstr "``Мој екстра предмет`" -#: ../settings/security/third-party.rst:30 -msgid "Weibo" -msgstr "Weibo" +#: ../misc/variables/article.rst:1 +msgid "Article > Text" +msgstr "Чланак > Текст" -#: ../settings/security/third-party.rst:35 -msgid "Automatic Account Link on Initial Logon" -msgstr "Аутоматско повезивање налога приликом иницијалне пријаве" +#: ../misc/variables/article.rst:1 +msgid "``#{article.body}``" +msgstr "``#{article.body}``" -#: ../settings/security/third-party.rst:37 -msgid "" -"In general there's two possible options for Zammad on how to deal with " -"already known users as they try to authenticate against a third-party " -"application. By default, Zammad will not automatically link \"unknown\" " -"authentication providers to existing accounts." -msgstr "" -"Уопштено говорећи, постоје две могуће опције за Zammad о томе како да се " -"носи са већ познатим корисницима док покушавају да се пријаве преко " -"апликације трећег лица. Подразумевано, Zammad неће аутоматски повезати " -"„непознате“ провајдере за пријављивање са постојећим налозима." +#: ../misc/variables/article.rst:1 +msgid "``Test`` without formatting (plain)" +msgstr "``Test`` без форматираног текста (обичан)" -#: ../settings/security/third-party.rst:42 -msgid "" -"This means that the user has to manually link authentication providers to " -"their accounts (for more about this :user-docs:`consult the user " -"documentation `)." -msgstr "" -"То значи да корисник мора ручно да повеже провајдере за пријављивање са " -"својим налогом (за више о овоме :user-docs:`погледајте корисничку " -"документацију `)." +#: ../misc/variables/article.rst:1 +msgid "Article > TicketID" +msgstr "Чланак > TicketID" -#: ../settings/security/third-party.rst:46 -msgid "" -"Sometimes this doesn't come in handy as this also means you'll receive error " -"messages about \"email address being in use already\" for (yet) unknown " -"third-party authentication methods." -msgstr "" -"Понекад ово није згодно јер то такође значи да ћете добијати поруке о грешци " -"да се „имејл адреса већ користи“ за (још) непознате методе аутентификације " -"преко трећег лица." +#: ../misc/variables/article.rst:1 +msgid "``#{article.ticket_id}``" +msgstr "``#{article.ticket_id}``" -#: ../settings/security/third-party.rst:50 -msgid "" -"If you want to allow your users to always be able to log in, no matter what, " -"you may want to enable ``Automatic account link on initial logon``." -msgstr "" -"Ако желите да омогућите својим корисницима да увек могу да се пријаве, без " -"обзира на све, можда ћете желети да укључите ``Аутоматско повезивање налога " -"приликом иницијалне пријаве``." +#: ../misc/variables/article.rst:1 +msgid "``1`` (not ticket number)" +msgstr "``1`` (не представља број тикета)" -#: ../settings/security/third-party.rst:None -msgid "" -"Screenshot highlighting the \"Automatic account link on initial logon\"\n" -"setting" -msgstr "" -"Снимак екрана који истиче подешавање „Аутоматско повезивање\n" -"налога приликом иницијалне пријаве“" +#: ../misc/variables/article.rst:1 +msgid "Article > To" +msgstr "Чланак > За" -#: ../settings/security/third-party.rst:60 -msgid "Automatic Account Linking Notification" -msgstr "Обавештавање о аутоматском повезивању налога" +#: ../misc/variables/article.rst:1 +msgid "``#{article.to}``" +msgstr "``#{article.to}``" -#: ../settings/security/third-party.rst:64 -msgid "" -"To improve security and your users awareness, you can enable Zammad to " -"notify your users when a new third-party application has been linked to " -"their account." -msgstr "" -"Да бисте побољшали безбедност и свест корисника, можете омогућити Zammad-у " -"да обавести ваше кориснике када је нова апликација трећег лица повезана са " -"њиховим налогом." +#: ../misc/variables/article.rst:1 +msgid "``helpdesk@example.com``" +msgstr "``helpdesk@example.com``" -#: ../settings/security/third-party.rst:68 -msgid "" -"This notification is sent out once per third-party application. Zammad does " -"also mention the method used, e.g.: ``Microsoft``." -msgstr "" -"Ово обавештење се шаље једном по апликацији трећег лица. Zammad такође " -"помиње коришћени метод, на пример: ``Microsoft``." +#: ../misc/variables/article.rst:1 +msgid "Article > Type > Name" +msgstr "Чланак > Тип > Назив" -#: ../settings/security/third-party.rst:71 -msgid "By default this setting is not active (set to ``no``)." -msgstr "Подразумевано ово подешавање није укључено (подешено је на ``не``)." +#: ../misc/variables/article.rst:1 +msgid "``#{article.type.name}``" +msgstr "``#{article.type.name}``" -#: ../settings/security/third-party.rst:0 +#: ../misc/variables/article.rst:1 msgid "" -"Screenshot showing sample notification mail after initial\n" -"third-party linking" +"``email`` (`list of article types `_)" msgstr "" -"Снимак екрана који приказује пример имејл обавештења након иницијалног\n" -"повезивање преко трећег лица" +"``email`` (`листа типова чланака `_)" -#: ../settings/security/third-party.rst:85 -msgid "" -"This notification is only sent if the account in question already exists. If " -"the login via the third-party also creates the missing account, the " -"notification will be skipped." -msgstr "" -"Ово обавештење се шаље само ако дотични налог већ постоји. Ако пријављивање " -"преко трећег лица такође додаје нови налог, обавештење ће бити прескочено." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Address" +msgstr "Чланак > Освежено од стране > Адреса" -#: ../settings/security/third-party.rst:89 -msgid "This means it only affects:" -msgstr "То значи да утиче само на:" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.address}``" +msgstr "``#{article.updated_by.address}``" -#: ../settings/security/third-party.rst:91 -msgid "manual account linking within the third-party page of the users profile" -msgstr "" -"ручно повезивање налога у оквиру странице трећег лица корисничког профила" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Department" +msgstr "Чланак > Освежено од стране > Одељење" -#: ../settings/security/third-party.rst:92 -msgid "" -"logging into an existing local account by utilizing the *automatic account " -"link on initial logon* functionality" -msgstr "" -"пријављивање на постојећи локални налог коришћењем функције *Аутоматско " -"повезивање налога приликом иницијалне пријаве*" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.department}``" +msgstr "``#{article.updated_by.department}``" -#: ../settings/security/third-party.rst:None -msgid "" -"Screenshot showing the \"automatic account linking notification\"\n" -"setting" -msgstr "" -"Снимак екрана који приказује подешавање „Обавештавање о\n" -"аутоматском повезивању налога“" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Email" +msgstr "Чланак > Освежено од стране > Имејл" -#: ../settings/security/third-party.rst:100 -msgid "No User Creation on Logon" -msgstr "Без отварања налога по пријави" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.email}``" +msgstr "``#{article.updated_by.email}``" -#: ../settings/security/third-party.rst:102 -msgid "" -"By default, Zammad will create a new user account if the user logs in via a " -"third-party application and the account doesn't exist yet." -msgstr "" -"Подразумевано, Zammad ће отворити нови кориснички налог ако се корисник " -"пријављује преко апликације трећег лица и налог још увек не постоји." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Fax" +msgstr "Чланак > Освежено од стране > Факс" -#: ../settings/security/third-party.rst:105 -msgid "" -"If you want to prevent Zammad from creating new accounts on logon, you can " -"disable this feature by setting ``No user creation on logon`` to ``yes``." -msgstr "" -"Уколико желите да спречите Zammad да отвара нове налоге по пријави, можете " -"искључити ову функцију постављањем ``Без отварања налога по пријави``на " -"``да``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.fax}``" +msgstr "``#{article.updated_by.fax}``" -#: ../settings/security/third-party.rst:None -msgid "Screenshot showing the \"no user creation on logon\" setting" -msgstr "" -"Снимак екрана који приказује подешавање „Без отварања налога по пријави”" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Firstname" +msgstr "Чланак > Освежено од стране > Име" -#: ../settings/security/third-party/facebook.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via Facebook To do " -"so, you need to follow these steps:" -msgstr "" -"Могуће је подесити брзо пријављивање у Zammad преко Facebook-а. Да бисте то " -"урадили, потребно је да пратите следеће кораке:" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.firstname}``" +msgstr "``#{article.updated_by.firstname}``" -#: ../settings/security/third-party/facebook.rst:9 -msgid "Register Facebook App" -msgstr "Региструјте Facebook апликацију" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Lastname" +msgstr "Чланак > Освежено од стране > Презиме" -#: ../settings/security/third-party/facebook.rst:11 -msgid "" -"Visit [https://developers.facebook.com/apps/] and click on \"Add a new App\"" -msgstr "" -"Посетите [https://developers.facebook.com/apps/] и кликните на „Add a new " -"App“" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.lastname}``" +msgstr "``#{article.updated_by.lastname}``" -#: ../settings/security/third-party/facebook.rst:None -msgid "initial page" -msgstr "почетна страница" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Login" +msgstr "Чланак > Освежено од стране > Пријава" -#: ../settings/security/third-party/facebook.rst:17 -msgid "After that enter the app settings" -msgstr "Након тога унесите подешавања апликације" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.login}``" +msgstr "``#{article.updated_by.login}``" -#: ../settings/security/third-party/facebook.rst:None -msgid "Create App" -msgstr "Create App" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Mobile" +msgstr "Чланак > Освежено од стране > Мобилни" -#: ../settings/security/third-party/facebook.rst:22 -msgid "Navigate to \"Settings\" and fill in this infromation" -msgstr "Идите на „Settings“ и попуните ове информације" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.mobile}``" +msgstr "``#{article.updated_by.mobile}``" -#: ../settings/security/third-party/facebook.rst:None -msgid "App Settings" -msgstr "App Settings" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Note" +msgstr "Чланак > Освежено од стране > Напомена" -#: ../settings/security/third-party/facebook.rst:27 -msgid "Navigate to app review and Check \"Make [appname] public?\"" -msgstr "" -"Идите на рецензију апликације и означите „Make [назив апликације] public?“" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.note}``" +msgstr "``#{article.updated_by.note}``" -#: ../settings/security/third-party/facebook.rst:None -msgid "App Review" -msgstr "App Review" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Phone" +msgstr "Чланак > Освежено од стране > Телефон" -#: ../settings/security/third-party/facebook.rst:35 -msgid "Configure Zammad as Facebook App" -msgstr "Подесите Zammad као Facebook апликацију" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.phone}``" +msgstr "``#{article.updated_by.phone}``" -#: ../settings/security/third-party/facebook.rst:37 -msgid "" -"Navigate to \"Admin -> Security -> Third Party Applications\" and enter the " -"App ID and the App Secret. You can find this Key in the Dashbard of your " -"Facebok app." -msgstr "" -"Идите на „Администрација -> Безбедност -> Апликације трећег лица“ и унесите " -"ID апликације и шифру апликације. Овај кључ можете пронаћи у контролној " -"табли ваше Facebook апликације." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > VIP" +msgstr "Чланак > Освежено од стране > VIP" -#: ../settings/security/third-party/facebook.rst:None -msgid "Zammad Configuration" -msgstr "Zammad подешавања" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.vip}``" +msgstr "``#{article.updated_by.vip}``" -#: ../settings/security/third-party/facebook.rst:44 -#: ../settings/security/third-party/github.rst:43 -#: ../settings/security/third-party/gitlab.rst:46 -msgid "" -"Now you can link accounts via \"Avatar -> Profile -> Link Accounts\" or " -"login via Zammad login page." -msgstr "" -"Сада можете повезати налоге преко „Аватар -> Профил -> Повезани налози” или " -"се пријавити преко Zammad странице за пријаву." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Web" +msgstr "Чланак > Освежено од стране > Веб" -#: ../settings/security/third-party/github.rst:2 -#: ../system/integrations/github.rst:2 -msgid "GitHub" -msgstr "GitHub" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.web}``" +msgstr "``#{article.updated_by.web}``" -#: ../settings/security/third-party/github.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via GitHub. To " -"activate the quick login you need to enable OAuth for GitHub." -msgstr "" -"Могуће је подесити брзо пријављивање у Zammad преко GitHub-а. Да бисте то " -"урадили, потребно је да омогућите OAuth за GitHub." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated" +msgstr "Чланак > Освежено у" -#: ../settings/security/third-party/github.rst:8 -msgid "Register GitHub App" -msgstr "Регистрација GitHub апликације" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_at}``" +msgstr "``#{article.updated_at}``" -#: ../settings/security/third-party/github.rst:10 -msgid "" -"Visit https://www.github.com/settings/applications/new and enter the app " -"settings. As callback URL enter \"https://zammad_host/auth/github/callback\" " -"where zammad_host has to be replaced with your Zammad FQDN" -msgstr "" -"Посетите https://www.github.com/settings/applications/new и унесите " -"подешавања апликације. Као URL адресу повратног позива унесите „https://" -"zammad_host/auth/github/callback“ где zammad_host треба да буде замењено " -"вашом Zammad FQDN адресом." +#: ../misc/variables/article.rst:1 +msgid "Article > Visibility" +msgstr "Чланак > Видљивост" -#: ../settings/security/third-party/github.rst:None -msgid "Register OAuth app on www.github.com" -msgstr "Региструјте OAuth апликацију на www.github.com" +#: ../misc/variables/article.rst:1 +msgid "``#{article.internal}``" +msgstr "``#{article.internal}``" -#: ../settings/security/third-party/github.rst:19 -msgid "Configure Zammad as GitHub App" -msgstr "Подесите Zammad као GitHub апликацију" +#: ../misc/variables/article.rst:1 +msgid "``false`` or ``true`` (false if not internal)" +msgstr "``false`` или ``true`` (false ако није интерни)" -#: ../settings/security/third-party/github.rst:21 -msgid "" -"Enter the \"APP ID\" and the \"APP SECRET\" from the GitHub OAUTH " -"Applications Dashboard" -msgstr "" -"Унесите „ID апликације“ и „Шифру апликације“ са контролне табле GitHub OAuth " -"апликација" +#: ../misc/variables/article.rst:1 +msgid "Article Text as HTML (not referenced)" +msgstr "Текст чланка у HTML формату (без референцирања)" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub config in Zammad admin interface" -msgstr "GitHub конфигурација у администраторском интерфејсу Zammad-а" +#: ../misc/variables/article.rst:1 +msgid "``#{article.body_as_html}``" +msgstr "``#{article.body_as_html}``" -#: ../settings/security/third-party/github.rst:28 -msgid "" -"After you configured the GitHub credentials and activated the login method, " -"you should see a new icon on the login page." -msgstr "" -"Након што сте подесили GitHub акредитиве и укључили метод пријављивања, " -"требало би да видите нову иконицу на страници за пријаву." +#: ../misc/variables/article.rst:1 +msgid "``Test`` with formatting" +msgstr "``Тест`` са форматираним текстом" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub logo on login page" -msgstr "GitHub логотип на страници за пријаву" +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "Ticket > Article#" +msgstr "Чланак > Број" -#: ../settings/security/third-party/github.rst:34 -msgid "" -"If you click on the icon you will be redirected to GitHub and see something " -"similar to this:" -msgstr "" -"Ако кликнете на иконицу, бићете преусмерени на GitHub и видећете нешто " -"слично следећем:" +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "``#{ticket.article_count}``" +msgstr "``#{ticket.article_count}``" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub oauth page" -msgstr "GitHub OAuth страница" +#: ../misc/variables/article.rst:1 +msgid "``1`` number of ticket articles" +msgstr "``1`` број чланака тикета" -#: ../settings/security/third-party/github.rst:40 -#: ../settings/security/third-party/gitlab.rst:42 +#: ../misc/variables/config.rst:2 +msgid "Config" +msgstr "Конфигурација" + +#: ../misc/variables/config.rst:6 msgid "" -"When you grant the access you will be redirected to your Zammad instance and " -"logged in as a customer." +"Below you'll find config related variables. These hold useful configuration " +"information that you can use within e.g. triggers to show necessary " +"information to your customer." msgstr "" -"Када одобрите приступ, бићете преусмерени на своју Zammad инстанцу и " -"пријављени као корисник." +"Испод ћете пронаћу променљиве које се односе на конфигурацију. Могу садржати " +"корисне податке које бисте желели да користите унутар нпр. окидача за приказ " +"потребних информација вашим клијентима." -#: ../settings/security/third-party/gitlab.rst:2 -msgid "Gitlab" -msgstr "Gitlab" +#: ../misc/variables/config.rst:11 +msgid "Config Variables" +msgstr "Променљиве конфигурације" -#: ../settings/security/third-party/gitlab.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via Gitlab. To " -"activate the quick login you need to enable OAuth for Gitlab." -msgstr "" -"Могуће је подесити брзо пријављивање у Zammad преко GitLab-а. Да бисте то " -"урадили, потребно је да омогућите OAuth за GitHub." +#: ../misc/variables/config.rst:1 +msgid "Config > Fully Qualified Domain Name" +msgstr "Конфигурација > Квалификовани назив домена" -#: ../settings/security/third-party/gitlab.rst:8 -msgid "Register Gitlab App" -msgstr "Регистрација Gitlab апликације" +#: ../misc/variables/config.rst:1 +msgid "``#{config.fqdn}``" +msgstr "``#{config.fqdn}``" -#: ../settings/security/third-party/gitlab.rst:10 -msgid "To register an app in Gitlab open your profile and select applications." -msgstr "" -"Да бисте регистровали апликацију у Gitlab-у, отворите свој профил и " -"изаберите апликације." +#: ../misc/variables/config.rst:1 +msgid "``zammad.example.com``" +msgstr "``zammad.example.com``" -#: ../settings/security/third-party/gitlab.rst:12 -msgid "" -"As callback URL enter \"https://zammad-fqdn/auth/gitlab/callback\" where " -"zammad-fqdn has to be replaced with your Zammad FQDN" -msgstr "" -"Као URL адресу повратног позива унесите „https://zammad-fqdn/auth/gitlab/" -"callback“ где zammad-fqdn мора бити замењено вашом Zammad FQDN адресом." +#: ../misc/variables/config.rst:1 +msgid "Config > HTTP type" +msgstr "Конфигурација > HTTP протокол" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Register OAuth app on gitlab instance" -msgstr "Региструјте OAuth апликацију на Gitlab инстанци" +#: ../misc/variables/config.rst:1 +msgid "``#{config.http_type}``" +msgstr "``#{config.http_type}``" -#: ../settings/security/third-party/gitlab.rst:18 -msgid "Just select *read_user* under scopes as in the screenshot and save it." -msgstr "" -"Само изаберите *read_user* за опсег дозвола као на снимку екрана и сачувајте " -"је." +#: ../misc/variables/config.rst:1 +msgid "``https`` or ``http``" +msgstr "``https`` или ``http``" -#: ../settings/security/third-party/gitlab.rst:21 -msgid "Configure Zammad as Gitlab App" -msgstr "Подесите Zammad као Gitlab апликацију" +#: ../misc/variables/config.rst:1 +msgid "Config > Organization" +msgstr "Конфигурација > Организација" -#: ../settings/security/third-party/gitlab.rst:23 +#: ../misc/variables/config.rst:1 +msgid "``#{config.organization}``" +msgstr "``#{config.organization}``" + +#: ../misc/variables/config.rst:1 msgid "" -"Enter the \"APP ID\" and the \"APP SECRET\" from the Gitlab OAUTH " -"Applications Dashboard and your Gitlab-URL in the \"SITE\" field." +"``Zammad GmbH`` value set in `Branding `_" msgstr "" -"Унесите „ID апликације“ и „Шифру апликације“ са контролне табле Gitlab OAuth " -"апликација и своју Gitlab URL адресу у поље „Путања“." +"Вредност организације постављене у `брендингу `_" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab config in Zammad admin interface" -msgstr "Gitlab конфигурација у администраторском интерфејсу Zammad-а" +#: ../misc/variables/config.rst:1 +msgid "Config > Product Name" +msgstr "Конфигурација > Назив производа" -#: ../settings/security/third-party/gitlab.rst:30 +#: ../misc/variables/config.rst:1 +msgid "``#{config.product_name}``" +msgstr "``#{config.product_name}``" + +#: ../misc/variables/config.rst:1 msgid "" -"After you configured the Gitlab credentials and activated the login method, " -"you should see a new icon on the login page." +"``Helpdesk`` value set in `Branding `_" msgstr "" -"Након што сте подесили Gitlab акредитиве и активирали метод пријављивања, " -"требало би да видите нову иконицу на страници за пријаву." +"Вредност назива производа постављене у `брендингу `_" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab logo on login page" -msgstr "Gitlab логотип на страници за пријаву" +#: ../misc/variables/config.rst:1 +msgid "Config > SystemID" +msgstr "Конфигурација > SystemID" -#: ../settings/security/third-party/gitlab.rst:36 -msgid "" -"If you click on the icon you will be redirected to Gitlab and see something " -"similar to this:" -msgstr "" -"Ако кликнете на иконицу, бићете преусмерени на Gitlab и видећете нешто " -"слично следећем:" +#: ../misc/variables/config.rst:1 +msgid "``#{config.system_id}``" +msgstr "``#{config.system_id}``" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab oauth page" -msgstr "Gitlab OAuth страница" +#: ../misc/variables/config.rst:1 +msgid "``31`` (value between 1 and 99)" +msgstr "``31`` (вредност између 1 и 99)" -#: ../settings/security/third-party/google.rst:4 -msgid "" -"With some easy and fast steps, you can enable Zammad to authenticate your " -"users via Google." -msgstr "" -"Уз неколико лаких и брзих корака, можете омогућити Zammad-у да аутентификује " -"ваше кориснике преко Google-а." +#: ../misc/variables/config.rst:1 +msgid "Config > Ticket Hook" +msgstr "Конфигурација > Прикључак тикета" -#: ../settings/security/third-party/google.rst:8 -msgid "Register a Google App" -msgstr "Регистрација Google апликације" +#: ../misc/variables/config.rst:1 +msgid "``#{config.ticket_hook}``" +msgstr "``#{config.ticket_hook}``" -#: ../settings/security/third-party/google.rst:10 -msgid "" -"First of all, we need to create a new project - you can skip this step if " -"you already have one." -msgstr "" -"Пре свега, морате да креирате нови пројекат - овај корак можете прескочити " -"ако га већ имате." +#: ../misc/variables/config.rst:1 +msgid "``Ticket#``" +msgstr "``Ticket#``" -#: ../settings/security/third-party/google.rst:15 -msgid "" -"Use this link to create a new project: https://console.cloud.google.com/" -"projectcreate" -msgstr "" -"Користите следећи линк да направите нови пројекат: https://console.cloud." -"google.com/projectcreate" +#: ../misc/variables/current-user.rst:2 +msgid "Current User" +msgstr "Тренутни корисник" -#: ../settings/security/third-party/google.rst:18 +#: ../misc/variables/current-user.rst:6 msgid "" -"Now expand the menu, expand \"APIs & Services\" and select \"Credentials\". " -"Go to the tab \"OAuth consent screen\" first and ensure to fill in the " -"requested information - without doing so you can't create credentials!" +"Current user variables always return values of the current user that caused " +"e.g. a trigger to run." msgstr "" -"Сада проширите мени, проширите „APIs & Services“ и изаберите „Credentials“. " -"Прво идите на језичак „OAuth consent screen“ и уверите се да сте попунили " -"тражене информације – без тога не можете да креирате акредитиве!" - -#: ../settings/security/third-party/google.rst:None -msgid "Creating a consent screen" -msgstr "Подешавање екрана за сагласност" +"Променљиве тренутног корисника увек враћају вредности корисника који је " +"покренуо нпр. окидач." -#: ../settings/security/third-party/google.rst:25 +#: ../misc/variables/current-user.rst:8 msgid "" -"After filling in and saving the consent screen information, you can go to " -"the \"Credentials\" tab and create new \"OAuth client ID\"-Credentials." +"Due to the above fact, these variables are often not (yet) set or available " +"for usage." msgstr "" -"Након што попуните и сачувате информације на екрану за сагласност, можете да " -"пређете на језичак „Credentials“ и креирате нови „OAuth client ID“ – тј. " -"акредитиве." +"С обзиром на горњу чињеницу, ове променљиве често немају (још увек) вредност " +"или нису доступне." -#: ../settings/security/third-party/google.rst:28 +#: ../misc/variables/current-user.rst:10 msgid "" -"Fill in the necessary information as follows and replace ``zammad_host`` " -"with your FQDN:" +"In situations where e.g. schedulers or triggers run, this most likely is " +"nothing you want to use." msgstr "" -"Попуните неопходне информације на следећи начин и замените ``zammad_host`` " -"својом FQDN адресом:" +"У ситуацијама када се извршавају нпр. планери или окидачи, ово није нешто на " +"шта бисте желели да се ослоните." -#: ../settings/security/third-party/google.rst:31 -msgid "**Application type** ``[x] Web application``" -msgstr "**Aplication type** ``[x] Web application``" +#: ../misc/variables/current-user.rst:13 +msgid "Current User Variables" +msgstr "Променљиве тренутног корисника" -#: ../settings/security/third-party/google.rst:34 -msgid "**Authorized JavaScript origins** ``https://zammad_host/``" -msgstr "**Authorized JavaScript origins** ``https://zammad_host/``" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Address" +msgstr "Тренутни корисник > Адреса" -#: ../settings/security/third-party/google.rst:37 -msgid "" -"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" -"callback``" -msgstr "" -"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" -"callback``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.address}``" +msgstr "``#{user.address}``" -#: ../settings/security/third-party/google.rst:None -msgid "Adding a new OAuth client ID" -msgstr "Додавање новог OAuth клијент ID" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set" +msgstr "``Назив неке улице 1, 12345 Берлин`` или празно ако није постављено" -#: ../settings/security/third-party/google.rst:43 -msgid "" -"After creating the credentials, go to your Zammad installation and navigate " -"to \"Admin > Security > Third Party Applications\" > Google. Enter your " -"Client ID and Client secret here." -msgstr "" -"Након што креирате акредитиве, пређите на инсталацију Zammad-а и идите на " -"„Администрација > Безбедност > Апликације трећег лица” > Google. Овде " -"унесите свој ID клијента и шифру клијента." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Avatar" +msgstr "Тренутни корисник > Аватар" -#: ../settings/security/third-party/google.rst:None -msgid "Zammad" -msgstr "Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.avatar(60,60)}``" +msgstr "``#{user.avatar(60,60)}``" -#: ../settings/security/third-party/google.rst:50 -msgid "After submitting, the login via Google can be used." -msgstr "Након снимања, пријављивање преко Google-а се може користити." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "avatar picture with width and height in pixel (e.g. 60,60)" +msgstr "аватар сличица ширине и висине у пикселима (нпр. 60,60)" -#: ../settings/security/third-party/microsoft.rst:2 -msgid "Microsoft" -msgstr "Microsoft" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created at" +msgstr "Тренутни корисник > Додато од стране" -#: ../settings/security/third-party/microsoft.rst:4 -msgid "" -"Zammad's Microsoft connection allows your users with Microsoft accounts to " -"login. This works for Azure users as well and can be an alternative to :doc:" -"`/system/integrations/ldap/index`." -msgstr "" -"Zammad-ова Microsoft интеграција омогућава вашим корисницима са Microsoft " -"налозима да се пријаве. Ово функционише и за Azure кориснике и може бити " -"алтернатива :doc:`/system/integrations/ldap/index`." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_at}``" +msgstr "``#{user.created_at}``" -#: ../settings/security/third-party/microsoft.rst:10 -msgid "" -"This documentation part does not cover our :doc:`📧 Microsoft 365 email " -"channel `." -msgstr "" -"Овај део документације не покрива наш :doc:`📧 Microsoft 365 имејл канал `." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC``" +msgstr "``2019-10-07 16:25:00 UTC``" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screenshot showing Microsoft login button on Zammad login screen." -msgstr "" -"Снимак екрана који приказује дугме за пријаву на Microsoft на екрану пријаве " -"у Zammad." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Address" +msgstr "Тренутни корисник > Додато од стране > Адреса" -#: ../settings/security/third-party/microsoft.rst:30 -#: ../settings/security/third-party/microsoft.rst:53 -msgid "Supported account types:" -msgstr "Подржани типови налога:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.address}``" +msgstr "``#{user.created_by.address}``" -#: ../settings/security/third-party/microsoft.rst:22 -msgid "" -"Please note that Zammad only supports these account types (App dependent):" -msgstr "" -"Имајте на уму да Zammad подржава само следеће типове налога (зависно од " -"апликације):" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Avatar" +msgstr "Тренутни корисник > Додато од стране > Аватар" -#: ../settings/security/third-party/microsoft.rst:35 -msgid "Avatars of signing in users:" -msgstr "Аватари пријављених корисника:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.avatar(60,60)}``" +msgstr "``#{user.created_by.avatar(60,60)}``" -#: ../settings/security/third-party/microsoft.rst:33 -msgid "" -"Zammad currently ignores user avatars. If the user is registered with e.g. " -"Gravatar, Zammad will fetch the avatar from there if enabled. See :doc:" -"`Zammad Image Service ` for more." -msgstr "" -"Zammad тренутно игнорише аватаре корисника. Уколико је корисник регистрован " -"код нпр. Gravatar сервиса, Zammad ће преузети аватар одатле ако је укључено. " -"Погледајте :doc:`Zammad услуга за слике ` за више " -"детаља." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Department" +msgstr "Тренутни корисник > Додато од стране > Одељење" -#: ../settings/security/third-party/microsoft.rst:38 -msgid "Step 1 - Register a Microsoft App for Zammad" -msgstr "Корак 1 - Региструјте Microsoft апликацију за Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.department}``" +msgstr "``#{user.created_by.department}``" -#: ../settings/security/third-party/microsoft.rst:40 -msgid "" -"Login to the `Microsoft Azure Portal `_ and " -"navigate to App registrations to create a new app. Provide the requested " -"information as follows and register your app." -msgstr "" -"Пријавите се на `Microsoft Azure портал `_ и " -"идите на App registrations да бисте додали нову апликацију. Наведите тражене " -"информације на следећи начин и региструјте своју апликацију." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Sales`` or empty if not set" +msgstr "``Sales`` или празно ако није подешено" -#: ../settings/security/third-party/microsoft.rst:46 -msgid "Name:" -msgstr "Назив:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Email" +msgstr "Тренутни корисник > Додато од стране > Имејл" -#: ../settings/security/third-party/microsoft.rst:45 -msgid "" -"Any meaningful name fitting, this name will be displayed to users trying to " -"authenticate with this app." -msgstr "" -"Било који назив који има смисла је дозвољен, име ће бити приказано " -"корисницима који покушавају да се аутентификују помоћу ове апликације." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.email}``" +msgstr "``#{user.created_by.email}``" -#: ../settings/security/third-party/microsoft.rst:49 -msgid "Choose one of the above mentioned account types (see Limitations)." -msgstr "" -"Изаберите један од горе наведених типова налога (погледајте ограничења)." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``jdoe@customer.tld``" +msgstr "``jdoe@customer.tld``" -#: ../settings/security/third-party/microsoft.rst:51 -msgid "" -"The correct account type depends on your use case. If you want to use the " -"authentication internal only, choose the first option. If you're unsure, use " -"the \"Help me choose...\" link." -msgstr "" -"Тачан тип налога зависи од вашег случаја коришћења. Ако желите да користите " -"само интерну аутентификацију, изаберите прву опцију. Ако нисте сигурни, " -"користите линк „Help me choose…“." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Fax" +msgstr "Тренутни корисник > Додато од стране > Факс" -#: ../settings/security/third-party/microsoft.rst:58 -msgid "Redirect URI (optional):" -msgstr "URI адреса преусмерења (опционо):" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.fax}``" +msgstr "``#{user.created_by.fax}``" -#: ../settings/security/third-party/microsoft.rst:56 -msgid "" -"Select web and provide your callback URL. The callback URL looks like this: " -"``https://zammad.domain.tld/auth/microsoft_office365/callback``" -msgstr "" -"Изаберите веб и наведите URL адресу повратног позива. Ваш URL повратног " -"позива изгледа овако: ``https://zammad.domain.tld/auth/microsoft_office365/" -"callback``" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``004930123464789`` or empty if not set" +msgstr "``004930123464789`` или празно ако није постављено" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to register a Microsoft app" -msgstr "Снимак екрана који показује како да региструјете Microsoft апликацију" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Firstname" +msgstr "Тренутни корисник > Додато од стране > Име" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "Within **API permissions** add the following permissions:" -msgstr "У оквиру **API permissions** додајте следеће дозволе:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.firstname}``" +msgstr "``#{user.created_by.firstname}``" -#: ../settings/security/third-party/microsoft.rst:69 -msgid "``User.Read``" -msgstr "``User.Read``" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``John`` or empty if not set" +msgstr "``John`` или празно ако није постављено" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "Contacts" -msgstr "Контакти" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Lastname" +msgstr "Тренутни корисник > Додато од стране > Презиме" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "``Contacts.Read``" -msgstr "``Contacts.Read``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.lastname}``" +msgstr "``#{user.created_by.lastname}``" -#: ../settings/security/third-party/microsoft.rst:73 -msgid "" -"You can find these permissions within *Microsoft Graph → Delegated " -"permissions*." -msgstr "" -"Ове дозволе можете пронаћи у оквиру *Microsoft Graph → Delegated " -"permissions*." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Login" +msgstr "Тренутни корисник > Додато од стране > Пријава" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to add required API permissions" -msgstr "Снимак екрана који показује како да додате потребне API дозволе" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.login}``" +msgstr "``#{user.created_by.login}``" -#: ../settings/security/third-party/microsoft.rst:80 -msgid "" -"Within **Certificates & secrets** create a new client secret. Note down the " -"returned secret **value** for later. **Do not** use the secret ID!" -msgstr "" -"У оквиру **Certificates & secrets** креирајте нови client secret. Забележите " -"добијену **вредност** шифре за касније. **Немојте** користити тајни ID!" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Mobile" +msgstr "Тренутни корисник > Додато од стране > Мобилни" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to create a new app secret" -msgstr "Снимак екрана који показује како да направите нову шифру апликације" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.mobile}``" +msgstr "``#{user.created_by.mobile}``" -#: ../settings/security/third-party/microsoft.rst:88 -msgid "" -"From **Overview** copy your apps *Application (client) ID*. If you're using " -"a single tenant app, please also copy *Directory (tenant) ID*. You now have " -"all required information for Zammad." -msgstr "" -"Из **Overview** копирајте своје *Application (client) ID*. Ако користите " -"апликацију само једног корисника, копирајте и *Directory (tenant) ID*. Сада " -"имате све потребне информације за Zammad." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``0049176123456789`` or empty if not set" +msgstr "``0049176123456789`` или празно ако није постављено" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to retreive application client and tenant IDs" -msgstr "" -"Снимак екрана који показује како да преузмете ID клијента и корисника " -"апликације" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Note" +msgstr "Тренутни корисник > Додато од стране > Напомена" -#: ../settings/security/third-party/microsoft.rst:98 -msgid "Step 2 - Add App Credentials to Zammad" -msgstr "Корак 2 - Додајте акредитиве апликације у Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.note}``" +msgstr "``#{user.created_by.note}``" -#: ../settings/security/third-party/microsoft.rst:100 -msgid "" -"Navigate to Security > Third-party Applications (Tab) within Zammad's admin " -"settings. Scroll down to the section *Authentication via Microsoft* and fill " -"in the required information." -msgstr "" -"Идите на Безбедност > Апликације трећег лица (језичак) у оквиру Zammad-ових " -"администраторских подешавања. Померите се надоле до одељка *Аутентификација " -"путем Microsoft* и попуните потребне информације." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Some note to this user`` or empty if not set" +msgstr "``Нека напомена за овог корисника`` или празно ако није постављено" -#: ../settings/security/third-party/microsoft.rst:105 -msgid "App ID:" -msgstr "ID апликације:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Phone" +msgstr "Тренутни корисник > Додато од стране > Телефон" -#: ../settings/security/third-party/microsoft.rst:105 -msgid "This is your *Application (client) ID*." -msgstr "Ово је ваш *Application (client) ID*." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.phone}``" +msgstr "``#{user.created_by.phone}``" -#: ../settings/security/third-party/microsoft.rst:108 -msgid "App secret:" -msgstr "Шифра апликације:" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``004930123456789`` or empty if not set" +msgstr "``004930123456789`` или празно ако није постављено" -#: ../settings/security/third-party/microsoft.rst:108 -msgid "This is your *client secret* (value)." -msgstr "Ово је ваш *client secret* (вредност)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > VIP" +msgstr "Тренутни корисник > Додато од стране > VIP" -#: ../settings/security/third-party/microsoft.rst:113 -msgid "App Tenant ID:" -msgstr "ID корисника апликације:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.vip}``" +msgstr "``#{user.created_by.vip}``" -#: ../settings/security/third-party/microsoft.rst:111 -msgid "" -"**optional** only required for apps that use account type *Accounts in this " -"organizational directory only (Default Directory only - Single tenant).*" -msgstr "" -"**необавезно** потребно само за апликације које користе тип налога *Accounts " -"in this organizational directory only (Default Directory only - Single " -"tenant).*" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Web" +msgstr "Тренутни корисник > Додато од стране > Веб" -#: ../settings/security/third-party/microsoft.rst:115 -msgid "" -"Apply your settings by pressing submit and activate *Authentication via " -"Microsoft*." -msgstr "" -"Примените подешавања притиском на пошаљи и активирајте *Аутентификација " -"преко Microsoft*." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.web}``" +msgstr "``#{user.created_by.web}``" -#: ../settings/security/third-party/microsoft.rst:None -msgid "" -"Screencast showing how to add app credentials and activating the\n" -"authentication method" -msgstr "" -"Снимак екрана који показује како додати акредитиве апликације и активирати\n" -"метод аутентификације" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``https://zammad.org`` or empty if not set" +msgstr "``https://zammad.org`` или празно ако није постављено" -#: ../settings/security/third-party/saml.rst:2 -msgid "SAML" -msgstr "SAML" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Department" +msgstr "Тренутни корисник > Одељење" -#: ../settings/security/third-party/saml.rst:4 -msgid "" -"Connect your SAML (Security Assertion Markup Language) identity provider as " -"a single sign-on (SSO) method." -msgstr "" -"Повежите свог SAML (Security Assertion Markup Language) сервис провајдера " -"као метод јединствене пријаве (SSO)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.department}``" +msgstr "``#{user.department}``" -#: ../settings/security/third-party/saml.rst:7 -msgid "" -"SAML is an open standard for SSO authentication (among other things). Sign-" -"ins are shared across multiple **service providers** and managed by a " -"central **identity provider** (IdP)." -msgstr "" -"SAML је отворени стандард за SSO аутентификацију (између осталог). Пријаве " -"су подељене на више **сервисних провајдера** и њима управља централни " -"**провајдер идентитета** (IdP)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Email" +msgstr "Тренутни корисник > Имејл" -#: ../settings/security/third-party/saml.rst:11 -msgid "" -"In this case, the service provider is Zammad, and the IdP is a software " -"service that you either host or subscribe to (*e.g.,* `Keycloak `_, `Redhat SSO Server `_, `ADFS `_, or `Okta `_)." -msgstr "" -"У овом случају, сервисни провајдер је Zammad, а IddP је софтверски сервис " -"који или хостујете сами или се претплатите на њега (*нпр.* `Keycloak " -"`_, `Redhat SSO Server `_, `ADFS `_ или `Okta " -"` _)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.email}``" +msgstr "``#{user.email}``" -#: ../settings/security/third-party/saml.rst:18 -msgid "" -"This guide assumes you are already using SAML within your organization (i." -"e., that your IdP is fully set up)." -msgstr "" -"Овај водич претпоставља да већ користите SAML у својој организацији (тј. да " -"је ваш IdP у потпуности подешен)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Fax" +msgstr "Тренутни корисник > Факс" -#: ../settings/security/third-party/saml.rst:21 -msgid "" -"Please note: Our instructions are based on connecting Zammad with Keycloak." -msgstr "" -"Обратите пажњу: наша упутства су базирана на повезивању Zammad-а са Keycloak-" -"ом." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.fax}``" +msgstr "``#{user.fax}``" -#: ../settings/security/third-party/saml.rst:25 -msgid "Step 1: Configure Your IdP" -msgstr "Корак 1: Подесите свој IdP" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Firstname" +msgstr "Тренутни корисник > Име" -#: ../settings/security/third-party/saml.rst:28 -msgid "Add Zammad as a Client/App" -msgstr "Додајте Zammad као клијента/апликацију" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.firstname}``" +msgstr "``#{user.firstname}``" -#: ../settings/security/third-party/saml.rst:30 -msgid "" -"Import Zammad into your IdP using the XML configuration found at ``https://" -"your.zammad.domain/auth/saml/metadata``." -msgstr "" -"Увезите Zammad у свој IdP користећи XML конфигурацију која се налази на " -"``https://your.zammad.domain/auth/saml/metadata``." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Lastname" +msgstr "Тренутни корисник > Презиме" -#: ../settings/security/third-party/saml.rst:33 -msgid "" -"If your IdP doesn't support XML import, you will have to configure Zammad as " -"a new client/app manually using the above XML metadata file for reference." -msgstr "" -"Уколико ваш IdP не подржава XML увоз, мораћете да подесите Zammad као новог " -"клијента/апликацију ручно, користећи горњу XML датотеку мета података као " -"референцу." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.lastname}``" +msgstr "``#{user.lastname}``" -#: ../settings/security/third-party/saml.rst:36 -msgid "For instance, when you see this tag:" -msgstr "На пример, када видите ову ознаку:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Login" +msgstr "Тренутни корисник > Пријава" -#: ../settings/security/third-party/saml.rst:42 -msgid "" -"Set the **Assertion Consumer Service Binding URL** (sometimes also listed as " -"**Valid Redirect URIs**) to ``http://your.zammad.domain/auth/saml/callback``." -msgstr "" -"Подесите **Assertion Consumer Service Binding URL** (понекад је наведен и " -"као **Valid Redirect URIs**) на ``http://your.zammad.domain/auth/saml/" -"callback``." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.login}``" +msgstr "``#{user.login}``" -#: ../settings/security/third-party/saml.rst:47 -msgid "Set Up User Attribute Mapping" -msgstr "Подесите мапирање корисничких атрибута" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Mobile" +msgstr "Тренутни корисник > Мобилни" -#: ../settings/security/third-party/saml.rst:49 -msgid "" -"Zammad requests the following user attributes (or “properties”) from the IdP:" -msgstr "" -"Zammad захтева следеће корисничке атрибуте (или „properties“) од IdP-а:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.mobile}``" +msgstr "``#{user.mobile}``" -#: ../settings/security/third-party/saml.rst:51 -msgid "Email address (``email``)" -msgstr "Имејл адреса (``email``)" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Note" +msgstr "Тренутни корисник > Напомена" -#: ../settings/security/third-party/saml.rst:52 -msgid "Full name (``name``)" -msgstr "Пуно име и презиме (``name``)" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.note}``" +msgstr "``#{user.note}``" -#: ../settings/security/third-party/saml.rst:53 -msgid "Given name (``first_name``)" -msgstr "Име (``first_name``)" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Domain based assignment" +msgstr "Тренутни корисник > Организација > Додела на основу домен" -#: ../settings/security/third-party/saml.rst:54 -msgid "Family name (``last_name``)" -msgstr "Презиме (``last_name``)" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.domain_assignment}``" +msgstr "``#{user.organization.domain_assignment}``" -#: ../settings/security/third-party/saml.rst:56 -msgid "" -"You may need to set up “mappers” (or “mappings”) to tell your IdP how user " -"attributes in SAML correspond to those in Zammad. For a more detailed " -"breakdown, refer to the XML metadata file referenced in the previous section." -msgstr "" -"Можда ћете морати да подесите „mappers“ (или „mappings“) да бисте свом IdP-у " -"рекли како кориснички атрибути у SAML-у одговарају онима у Zammad-у. За " -"детаљнију анализу погледајте XML датотеку мета података наведену у " -"претходном одељку." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Domain" +msgstr "Тренутни корисник > Организација > Домен" -#: ../settings/security/third-party/saml.rst:62 -msgid "Per-IdP Instructions" -msgstr "Упутства за IdP" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.domain}``" +msgstr "``#{user.organization.domain}``" -#: ../settings/security/third-party/saml.rst:102 -msgid "Keycloak" -msgstr "Keycloak" +#: ../misc/variables/current-user.rst:1 +msgid "``zammad.com`` or empty if not set" +msgstr "``zammad.com`` или празно ако није постављено" -#: ../settings/security/third-party/saml.rst:65 -msgid "" -"**To add Zammad as a client,** save the XML configuration to disk (``https://" -"your.zammad.domain/auth/saml/metadata``) and use **Clients > Clients list > " -"Import client** in the Keycloak admin panel." -msgstr "" -"**Да бисте додали Zammad као клијента,** сачувајте XML конфигурацију на диск " -"(``https://your.zammad.domain/auth/saml/metadata``) и користите **Clients > " -"Clients list > Import client* * у Keycloak админ панелу." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Name" +msgstr "Тренутни корисник > Организација > Назив" -#: ../settings/security/third-party/saml.rst:70 -msgid "" -"To help Zammad **match its own user accounts to Keycloak users**, create a " -"user attribute (or “property”) mapper. In **Clients list**, click on your " -"newly created Client ID, choose the tab **Client scopes** and click on the " -"link which refers to your Zammad instance. Choose **Add mapper > By " -"configuration > User Property** and create a mapper with the following " -"entries:" -msgstr "" -"Да бисте помогли Zammad-у да **повеже сопствене корисничке налоге са " -"Keycloak корисницима**, креирајте мапирање атрибута корисника (или " -"„property“). У **Clients list** кликните на ваш новокреирани ID клијента, " -"изаберите језичак **Client scopes** и кликните на линк који се односи на " -"вашу Zammad инстанцу. Изаберите **Add mapper > By configuration > User " -"Property** и додајте мапирање са следећим уносима:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.name}``" +msgstr "``#{user.organization.name}``" -#: ../settings/security/third-party/saml.rst:78 -msgid "**Name**" -msgstr "**Name**" +#: ../misc/variables/current-user.rst:1 +msgid "``Zammad GmbH``" +msgstr "``Zammad GmbH``" -#: ../settings/security/third-party/saml.rst:80 -msgid "**Mapper Type**" -msgstr "**Mapper Type**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Note" +msgstr "Тренутни корисник > Организација > Напомена" -#: ../settings/security/third-party/saml.rst:81 -msgid "``User Property``" -msgstr "``User Property``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.note}``" +msgstr "``#{user.organization.note}``" -#: ../settings/security/third-party/saml.rst:82 -msgid "**Property**" -msgstr "**Property**" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``A note to the organization of the user`` or empty if not set" +msgstr "``Напомена организације корисника`` или празно ако није постављено" -#: ../settings/security/third-party/saml.rst:83 -msgid "``emailAddress``" -msgstr "``emailAddress``" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Shared organization" +msgstr "Тренутни корисник > Организација > Заједничка организације" -#: ../settings/security/third-party/saml.rst:84 -msgid "**SAML Attribute Name**" -msgstr "**Назив SAML атрибута**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.shared}``" +msgstr "``#{user.organization.shared}``" -#: ../settings/security/third-party/saml.rst:86 -msgid "**SAML Attribute NameFormat**" -msgstr "**Формат назива SAML атрибута**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > VIP" +msgstr "Тренутни корисник > Организација > VIP" -#: ../settings/security/third-party/saml.rst:87 -msgid "``basic``" -msgstr "``basic``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.vip}``" +msgstr "``#{user.organization.vip}``" -#: ../settings/security/third-party/saml.rst:89 -msgid "" -"In the example above, we're telling Zammad that whenever it receives a SAML " -"login request, it should take the ``email`` property from Keycloak, look for " -"a Zammad user with the same ``email`` attribute, and create a new session " -"for that user." -msgstr "" -"У горњем примеру, кажемо Zammad-у да кад год прими SAML захтев за пријаву, " -"треба да узме атрибут ``email`` од Keycloak-а, потражи Zammad корисника са " -"истим атрибутом ``email`` и креира нову сесију за тог корисника." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Phone" +msgstr "Тренутни корисник > Телефон" -#: ../settings/security/third-party/saml.rst:95 -msgid "" -"If your Keycloak users' email addresses are stored on another property (*e." -"g.,* ``username``), adjust accordingly." -msgstr "" -"Ако су имејл адресе ваших Keycloak корисника ускладиштене у другом атрибуту " -"(*нпр.* ``username``), прилагодите мапирање у складу са тим." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.phone}``" +msgstr "``#{user.phone}``" -#: ../settings/security/third-party/saml.rst:98 -msgid "" -"Back in **Settings**, enter the Client ID (``https://your.zammad.domain/auth/" -"saml/metadata``) in the field **Master SAML Processing URL**." -msgstr "" -"Вратите се у **Settings**, унесите Client ID (``https://your.zammad.domain/" -"auth/saml/metadata``) у поље **Master SAML Processing URL**." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated at" +msgstr "Current User > Освежено у" -#: ../settings/security/third-party/saml.rst:101 -msgid "You also need to enable **Sign assertions**." -msgstr "Такође морате да укључите **Sign assertions**." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_at}``" +msgstr "``#{user.updated_at}``" -#: ../settings/security/third-party/saml.rst:105 -msgid "Step 2: Configure Zammad" -msgstr "Корак 2: Подесите Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Address" +msgstr "Тренутни корисник > Освежено од стране > Адреса" -#: ../settings/security/third-party/saml.rst:107 -msgid "" -"Enable SAML and enter your IdP's details in the Admin Panel under **Settings " -"> Security > Third Party Applications > Authentication via SAML**:" -msgstr "" -"Укључите SAML и унесите детаље свог IdP-а у администраторском панелу под " -"**Подешавања > Безбедност > Апликације трећег лица > Аутентификација путем " -"SAML**:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.address}``" +msgstr "``#{user.updated_by.address}``" -#: ../settings/security/third-party/saml.rst:None -msgid "Example configuration of SAML part 1" -msgstr "Пример подешавања SAML део 1" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Avatar" +msgstr "Тренутни корисник > Освежено од стране > Аватар" -#: ../settings/security/third-party/saml.rst:119 -msgid "Display name" -msgstr "Назив за приказ" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.avatar(60,60)}``" +msgstr "``#{user.updated_by.avatar(60,60)}``" -#: ../settings/security/third-party/saml.rst:116 -msgid "" -"Allows you to define a custom button name for SAML. This helps your users to " -"understand better what the button on the login page does." -msgstr "" -"Омогућава вам да одредите прилагођени назив дугмета за SAML. Ово помаже " -"вашим корисницима да боље разумеју шта ради дугме на страници за пријаву." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Department" +msgstr "Тренутни корисник > Освежено од стране > Одељење" -#: ../settings/security/third-party/saml.rst:119 -msgid "Defaults to ``SAML``." -msgstr "Подразумевано је ``SAML``." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.department}``" +msgstr "``#{user.updated_by.department}``" -#: ../settings/security/third-party/saml.rst:123 -msgid "IDP SSO target URL" -msgstr "IDP SSO URL путања" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Email" +msgstr "Тренутни корисник > Освежено од стране > Имејл" -#: ../settings/security/third-party/saml.rst:122 -msgid "" -"This is the target URL Zammad shall redirect to when the user presses the " -"SAML button. For Keycloak, this needs to look like https://your.domain/" -"realms/your-realm/protocol/saml" -msgstr "" -"Ово је циљна URL адреса на коју ће Zammad преусмерити када корисник притисне " -"SAML дугме. За Keycloak, ово треба да изгледа као https://your.domain/realms/" -"your-realm/protocol/saml" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.email}``" +msgstr "``#{user.updated_by.email}``" -#: ../settings/security/third-party/saml.rst:127 -msgid "IDP single logout target URL" -msgstr "IDP URL путања јединствене одјаве" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Fax" +msgstr "Тренутни корисник > Освежено од стране > Факс" -#: ../settings/security/third-party/saml.rst:126 -msgid "" -"This is the URL to which the single logout request and response should be " -"sent." -msgstr "" -"Ово је URL путања на коју треба преусмерити захтеве и одговоре за " -"јединствену одјаву." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.fax}``" +msgstr "``#{user.updated_by.fax}``" -#: ../settings/security/third-party/saml.rst:131 -msgid "IDP certificate" -msgstr "IDP сертификат" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Firstname" +msgstr "Тренутни корисник > Освежено од стране > Име" -#: ../settings/security/third-party/saml.rst:130 -msgid "" -"The public certificate of your IDP for Zammad to verify during the callback " -"phase." -msgstr "" -"Јавни сертификат вашег IDP-а који Zammad треба да провери током фазе " -"повратног позива." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.firstname}``" +msgstr "``#{user.updated_by.firstname}``" -#: ../settings/security/third-party/saml.rst:145 -msgid "IDP certificate fingerprint" -msgstr "IDP отисак сертификата" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Lastname" +msgstr "Тренутни корисник > Освежено од стране > Презиме" -#: ../settings/security/third-party/saml.rst:134 -msgid "" -"The fingerprint of your IDPs public certificate to verify during callback " -"phase." -msgstr "" -"Отисак вашег јавног IDP сертификата за верификацију током фазе повратног " -"позива." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.lastname}``" +msgstr "``#{user.updated_by.lastname}``" -#: ../settings/security/third-party/saml.rst:137 -msgid "🔏 **For the IdP certificate / certificate fingerprint:**" -msgstr "🔏 **За IdP сертификат / отисак сертификата:**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Login" +msgstr "Тренутни корисник > Освежено од стране > Пријава" -#: ../settings/security/third-party/saml.rst:139 -msgid "" -"Provide **only one or the other**—do not provide both! (Between the two, we " -"recommend the signing certificate itself: fingerprints use SHA-1, which `has " -"been broken for a while now `_.)" -msgstr "" -"Обезбедите **или једно или друго**—никако обе вредности! (Између ове две, " -"препоручујемо сам сертификат за потписивање: отисци сертификата користе " -"SHA-1 алгоритам, који је већ неко време покварен `_.)" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.login}``" +msgstr "``#{user.updated_by.login}``" -#: ../settings/security/third-party/saml.rst:144 -msgid "" -"**Keycloak users:** Find your certificate in the Keycloak admin panel under " -"**Realm Settings > Keys > Algorithm: RS256 > Certificate**." -msgstr "" -"**Keycloak корисници:** Пронађите свој сертификат у Keycloak " -"административном панелу под **Realm Settings > Keys > Algorithm: RS256 > " -"Certificate**." - -#: ../settings/security/third-party/saml.rst:151 -msgid "Name identifier format" -msgstr "Формат идентификатора назива" - -#: ../settings/security/third-party/saml.rst:148 -msgid "" -"This is the unique identifiers field type. Usually it should be ``urn:oasis:" -"names:tc:SAML:1.1:nameid-format:emailAddress``." -msgstr "" -"Ово је типа идентификатора јединствених поља. Обично би требало да буде " -"``urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress``." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Mobile" +msgstr "Тренутни корисник > Освежено од стране > Мобилни" -#: ../settings/security/third-party/saml.rst:151 -msgid "Zammad **expects an email address as unique identifier**!" -msgstr "Zammad **очекује имејл адресу као јединствени идентификатор**!" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.mobile}``" +msgstr "``#{user.updated_by.mobile}``" -#: ../settings/security/third-party/saml.rst:155 -msgid "UID attribute name" -msgstr "Назив UID атрибута" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Note" +msgstr "Тренутни корисник > Освежено од стране > Напомена" -#: ../settings/security/third-party/saml.rst:154 -msgid "" -"Here you can define an attribute that uniquely identifies the user. If " -"unset, the name identifier returned by the IDP is used." -msgstr "" -"Овде можете одредити назив атрибута који јединствено идентификује корисника. " -"Уколико није подешено, биће коришћен индентификатор назива који враћа IDP." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.note}``" +msgstr "``#{user.updated_by.note}``" -#: ../settings/security/third-party/saml.rst:None -msgid "Example configuration of SAML part 2" -msgstr "Пример подешавања SAML део 2" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Phone" +msgstr "Тренутни корисник > Освежено од стране > Телефон" -#: ../settings/security/third-party/saml.rst:163 -msgid "" -"Decide if the certificate for the connection to the IdP service has to be " -"verified or not (default: ``yes``)." -msgstr "" -"Одређује да ли ће сертификат за конекцију до IdP сервиса бити проверен или " -"не (подразумевано: ``да``)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.phone}``" +msgstr "``#{user.updated_by.phone}``" -#: ../settings/security/third-party/saml.rst:169 -msgid "Signing & Encrypting" -msgstr "Потписивање и шифровање" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > VIP" +msgstr "Тренутни корисник > Освежено од стране > VIP" -#: ../settings/security/third-party/saml.rst:169 -msgid "" -"Define if you want to sign, encrypt, do both or nothing for the requests." -msgstr "Одређује да ли желите потписивање и шифровање захтева." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.vip}``" +msgstr "``#{user.updated_by.vip}``" -#: ../settings/security/third-party/saml.rst:179 -msgid "Certificate (PEM)" -msgstr "Сертификат (PEM)" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``false`` or ``true``" +msgstr "``false`` или ``true``" -#: ../settings/security/third-party/saml.rst:172 -msgid "" -"Paste the public certificate of your Zammad SAML client, if you want to " -"encrypt the requests." -msgstr "" -"Налепите јавни сертификат вашег Zammad SAML клијента, уколико желите " -"шифровање захтева." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Web" +msgstr "Тренутни корисник > Освежено од стране > Веб" -#: ../settings/security/third-party/saml.rst:175 -msgid "Make sure the certificate is:" -msgstr "Уверите се да је сертификат:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.web}``" +msgstr "``#{user.updated_by.web}``" -#: ../settings/security/third-party/saml.rst:177 -msgid "already valid and not yet expired" -msgstr "већ важећи и није још истекао" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > VIP" +msgstr "Тренутни корисник > VIP" -#: ../settings/security/third-party/saml.rst:178 -msgid "no CA certificate" -msgstr "није CA сертификат" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.vip}``" +msgstr "``#{user.vip}``" -#: ../settings/security/third-party/saml.rst:179 -msgid "valid for signing and encrypting" -msgstr "важећи за потписивање и шифровање" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Web" +msgstr "Тренутни корисник > Веб" -#: ../settings/security/third-party/saml.rst:185 -msgid "Private key (PEM)" -msgstr "Тајни кључ (PEM)" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.web}``" +msgstr "``#{user.web}``" -#: ../settings/security/third-party/saml.rst:182 +#: ../misc/variables/ticket.rst:6 +#, fuzzy +#| msgid "" +#| "Below you can find all available ticket-based variables within Zammad. " +#| "These can be called via Triggers for example. If you're unsure if Zammad " +#| "does support variables at the point you're at, you can try to type ``::`` " +#| "to check." msgid "" -"Paste the private key of your Zammad SAML client here, if you want to sign " -"the requests." +"Below you can find all available ticket-based variables within Zammad. These " +"can be called via triggers for example. If you're unsure if Zammad does " +"support variables at the point you're at, you can try to type ``::`` to " +"check." msgstr "" -"Налепите тајни кључ вашег Zammad SAML клијента, уколико желите потписивање " -"захтева." +"Испод можете пронаћи све доступне променљиве тикета унутар Zammad-а. Могуће " +"их је користити у окидачима, на пример. Ако нисте сигурни да ли Zammad " +"подржава променљиве у неком делу, можете откуцати ``::`` да бисте проверили." -#: ../settings/security/third-party/saml.rst:185 -msgid "Make sure the key is an RSA key with a length of at least 2048 bits." -msgstr "Уверите се да је тајни кључ RSA дужине од најмање 2048 бита." +#: ../misc/variables/ticket.rst:12 +msgid "Ticket Variables" +msgstr "Променљиве тикета" -#: ../settings/security/third-party/saml.rst:188 -msgid "Private key secret" -msgstr "Лозинка тајног кључа" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Accounted Time" +msgstr "Тикет > Обрачунато време" -#: ../settings/security/third-party/saml.rst:188 -msgid "If your private key is secured with a secret, you can provide it here." -msgstr "Уколико је ваш тајни кључ обезбеђен лозинком, можете је унети овде." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.time_unit}``" +msgstr "``#{ticket.time_unit}``" -#: ../settings/security/third-party/saml.rst:192 -msgid "Your callback URL" -msgstr "Ваш URL повратног позива" +#: ../misc/variables/ticket.rst:1 +msgid "``1``, ``2.75`` or empty response" +msgstr "``1``, ``2.75`` или празно" -#: ../settings/security/third-party/saml.rst:191 -msgid "" -"This URL is needed for your IdP configuration so it knows where to redirect " -"to after successful authentication." -msgstr "" -"Ова URL адреса је потребна за вашу IDP конфигурацију како би знала где да " -"преусмери корисника након успешне аутентификације." +#: ../misc/variables/ticket.rst:1 +msgid "``3``, any number of articles existing in the ticket right now" +msgstr "``3``, број чланака који тренутно постоје у тикету" -#: ../settings/security/third-party/saml.rst:194 -msgid "" -"After saving your input by clicking on the \"Submit\" button, Zammad " -"verifies the provided keys/certificates (e.g. if they are valid for signing/" -"encrypting and if they aren't expired)." -msgstr "" -"По снимању вашег уноса кликом на дугме „Пошаљи”, Zammad ће проверити " -"достављене кључеве/сертификате (нпр. да ли су важећи за потписивање/" -"шифровање и да нису истекли." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Closing time" +msgstr "Тикет > Време затварања" -#: ../settings/security/third-party/saml.rst:199 -msgid "" -"See :ref:`automatic account linking ` for details " -"on how to link existing Zammad accounts to IdP accounts." -msgstr "" -"Погледајте :ref:`аутоматско повезивање налога ` " -"за детаље о томе како да повежете постојеће Zammad налоге са IdP налозима." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.close_at}``" +msgstr "``#{ticket.close_at}``" -#: ../settings/security/third-party/saml.rst:205 -msgid "Automatic account linking doesn't work" -msgstr "Аутоматско повезивање налога не функционише" +#: ../misc/variables/ticket.rst:1 +msgid "2019-10-07 17:25:00 UTC" +msgstr "2019-10-07 17:25:00 UTC" -#: ../settings/security/third-party/saml.rst:206 -msgid "" -"Have you double-checked your IdP's user attribute mapping configuration?" -msgstr "" -"Да ли сте још једном проверили подешавање мапирања корисничких атрибута " -"вашег IdP-а?" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created at" +msgstr "Тикет > Додато у" -#: ../settings/security/third-party/twitter.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via Twitter. To do " -"so, you need to follow these steps:" -msgstr "" -"Могуће је подесити брзо пријављивање у Zammad преко Twitter-а. Да бисте то " -"урадили, потребно је да пратите следеће кораке:" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_at}``" +msgstr "``#{ticket.created_at}``" -#: ../settings/security/third-party/twitter.rst:8 -msgid "Register Twitter App" -msgstr "Регистрација Twitter апликације" +#: ../misc/variables/ticket.rst:1 +msgid "2019-10-07 16:25:00 UTC" +msgstr "2019-10-07 16:25:00 UTC" -#: ../settings/security/third-party/twitter.rst:10 -msgid "Go to https://dev.twitter.com/apps and login with your account." -msgstr "" -"Идите на https://dev.twitter.com/apps и пријавите се са својим налогом." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Address" +msgstr "Тикет > Додато од стране > Адреса" -#: ../settings/security/third-party/twitter.rst:15 -msgid "Click on \"Create App\"" -msgstr "Кликните на „Create App”" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.address}``" +msgstr "``#{ticket.created_by.address}``" -#: ../settings/security/third-party/twitter.rst:None -msgid "new app page" -msgstr "Страница нове апликације" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Avatar" +msgstr "Тикет > Додато од стране > Аватар" -#: ../settings/security/third-party/twitter.rst:20 -msgid "" -"Enter app settings. As \"Callback URL\" you need to enter ``https://" -"zammad_host/api/v1/external_credentials/twitter/callback``. You need to " -"replace ``zammad_host`` with the domain of your Zammad system." -msgstr "" -"Унесите подешавања апликације. Као „Callback URL“ треба да унесете ``https://" -"zammad_host/api/v1/external_credentials/twitter/callback``. Морате заменити " -"``zammad_host`` са доменом вашег Zammad система." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.avatar(60,60)}``" +msgstr "``#{ticket.created_by.avatar(60,60)}``" -#: ../settings/security/third-party/twitter.rst:24 -msgid "" -"After the app has been created, update the application icon and organization " -"attributes." -msgstr "" -"Након што је апликација направљена, подесите иконицу апликације и атрибуте " -"организације." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Department" +msgstr "Тикет > Додато од стране > Одељење" -#: ../settings/security/third-party/twitter.rst:None -msgid "set permissions to receive and send direct messages" -msgstr "подесите дозволе за примање и слање директних порука" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.department}``" +msgstr "``#{ticket.created_by.department}``" -#: ../settings/security/third-party/twitter.rst:30 -msgid "" -"Next we need to set ``read, write and access direct messages`` permissions " -"for the app." -msgstr "" -"Затим морамо да подесимо дозволе за ``read, write and access direct " -"messages`` за апликацију." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Email" +msgstr "Тикет > Додато од стране > Имејл" -#: ../settings/security/third-party/twitter.rst:None -msgid "click on Keys & Access Token, note them" -msgstr "кликните на Keys & Access Token, забележите их" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.email}``" +msgstr "``#{ticket.created_by.email}``" -#: ../settings/security/third-party/twitter.rst:36 -msgid "" -"Go to \"Keys and Access Token\" tab and note the \"Consumer Key\" and " -"\"Consumer Secret\"." -msgstr "" -"Идите на језичал „Keys and Access Toke“ и забележите „Consumer Key“ и " -"„Consumer Secret“." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Fax" +msgstr "Тикет > Додато од стране > Факс" -#: ../settings/security/third-party/twitter.rst:40 -msgid "Configure Zammad as Twitter App" -msgstr "Подесите Zammad као Twitter апликацију" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.fax}``" +msgstr "``#{ticket.created_by.fax}``" -#: ../settings/security/third-party/twitter.rst:42 -msgid "" -"Go to \"Admin > Security > Twitter > Third Party Applications > Twitter\" " -"Section." -msgstr "" -"Идите на одељак „Администрација > Безбедност > Апликације трећег лица > " -"Twitter“." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Firstname" +msgstr "Тикет > Додато од стране > Име" -#: ../settings/security/third-party/twitter.rst:None -msgid "Admin > Security > Third Party Applications" -msgstr "Администрација > Безбедност > Апликације трећег лица" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.firstname}``" +msgstr "``#{ticket.created_by.firstname}``" -#: ../settings/security/third-party/twitter.rst:48 -msgid "" -"Fill in the \"Twitter Key\" and the \"Twitter Secret\" and click the " -"\"Submit\" button." -msgstr "" -"Попуните „Twitter кључ“ и „Twitter шифра“ и кликните на дугме „Пошаљи“." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Lastname" +msgstr "Тикет > Додато од стране > Презиме" -#: ../settings/security/third-party/twitter.rst:51 -msgid "" -"Now you can link accounts via \"Avatar > Profile > Link Accounts\" or login " -"via Zammad login page." -msgstr "" -"Сада можете повезати налоге преко „Аватар > Профил > Повезани налози” или се " -"пријавити преко Zammad странице за пријаву." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.lastname}``" +msgstr "``#{ticket.created_by.lastname}``" -#: ../settings/security/two-factor.rst:11 -msgid "Two-factor Authentication Methods" -msgstr "Методи двофакторске аутентификације" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Login" +msgstr "Тикет > Додато од стране > Пријава" -#: ../settings/security/two-factor.rst:2 -msgid "Two-Factor Authentication" -msgstr "Двофакторска аутентификација" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.login}``" +msgstr "``#{ticket.created_by.login}``" -#: ../settings/security/two-factor.rst:4 -msgid "" -"Two-factor authentication (2FA) enhances the security of Zammad accounts by " -"adding an extra layer of verification beyond a password. It requires users " -"to provide two different types of authentication factors, typically " -"something they know (like a password) and something they possess (like a " -"mobile device or a security token), to ensure that only authorized " -"individuals can access the account." -msgstr "" -"Двофакторска аутентикација (2FA) појачава безбедност Zammad налога додавањем " -"додатног нивоа верификације поред лозинке. Захтева од корисника да обезбеде " -"два различита типа фактора аутентификације, обично нешто што знају (попут " -"лозинке) и нешто што поседују (као што је мобилни уређај или безбедносни " -"кључ), како би се осигурало да само овлашћене особе могу да приступе налогу." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Mobile" +msgstr "Тикет > Додато од стране > Мобилни" -#: ../settings/security/two-factor.rst:19 -msgid "Enable Recovery Codes" -msgstr "Укључивање шифри за опоравак" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.mobile}``" +msgstr "``#{ticket.created_by.mobile}``" -#: ../settings/security/two-factor.rst:21 -msgid "" -"Recovery codes are one-time use security codes that can be used by the user " -"if they lose access to their other two-factor authentication methods. They " -"cannot be used on their own, they can only be activated if at least one two-" -"factor authentication method is enabled." -msgstr "" -"Шифре за опоравак су једнократни сигурносни кодови које корисник може " -"користити ако изгуби приступ својим другим методама двофакторске " -"аутентификације. Не могу се користити самостално, могуће их је укључити само " -"ако је укључен још бар један метод двофакторске аутентификације." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Note" +msgstr "Тикет > Додато од стране > Напомена" -#: ../settings/security/two-factor.rst:None -msgid "Enable Recovery Codes Setting" -msgstr "Укључивање подешавања шифри за опоравак" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.note}``" +msgstr "``#{ticket.created_by.note}``" -#: ../settings/security/two-factor.rst:30 -msgid "" -"Recovery codes can only be used as a backup method. If enabled, they will be " -"automatically generated for the user once they set up their initial two-" -"factor authentication method." -msgstr "" -"Шифре за опоравак могу се користити само као резервни метод. Ако су " -"укључене, аутоматски ће се генерисати за корисника када подесе свој почетни " -"метод двофакторске аутентификације." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Phone" +msgstr "Тикет > Додато од стране > Телефон" -#: ../settings/security/two-factor.rst:34 -msgid "" -"The user will be asked to print out or save the generated recovery codes in " -"a safe place. Once used, a recovery code cannot be reused." -msgstr "" -"Од корисника ће бити затражено да одштампа или сачува генерисане шифре за " -"опоравак на безбедном месту. Једном употребљена, шифра за опоравак се не " -"може поново користити." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.phone}``" +msgstr "``#{ticket.created_by.phone}``" -#: ../settings/security/two-factor.rst:37 -msgid "" -"Users will also have an option to regenerate their recovery codes at any " -"time, which invalidates already existing recovery codes and provides them " -"with a list of fresh codes." -msgstr "" -"Корисници ће такође имати опцију да регенеришу своје шифре за опоравак у " -"било ком тренутку, што поништава већ постојеће и пружа им листу свежих " -"кодова." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > VIP" +msgstr "Тикет > Додато од стране > VIP" -#: ../settings/security/two-factor.rst:41 -msgid "" -"After you enable this setting, when the user completes a setup of their " -"initial two-factor authentication method, they will be presented with a list " -"of recovery codes and instructed to save them for later use." -msgstr "" -"Након што укључите ово подешавање, када корисник заврши поставку свог " -"почетног метода двофакторске аутентификације, биће му представљена листа " -"шифри за опоравак и упутство да их сачува за каснију употребу." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.vip}``" +msgstr "``#{ticket.created_by.vip}``" -#: ../settings/security/two-factor.rst:None -msgid "Recovery Codes Generation Modal Dialog" -msgstr "Модални дијалог за генерисање шифри за опоравак" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Web" +msgstr "Тикет > Додато од стране > Веб" -#: ../settings/security/two-factor.rst:50 -msgid "Enforce the Set Up of the Two-Factor Authentication" -msgstr "Захтевање поставке двофакторске аутентификације" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.web}``" +msgstr "``#{ticket.created_by.web}``" -#: ../settings/security/two-factor.rst:52 -msgid "" -"In case you wish to require your users to set up at least one two-factor " -"authentication method for their account, you can do this by selecting " -"specific user roles the requirement applies to in **Enforced for user " -"roles** setting. Of course you must have at least one two-factor " -"authentication method enabled for this setting to take effect." -msgstr "" -"У случају да желите да од својих корисника захтевате да за свој налог подесе " -"бар један метод двофакторске аутентификације, то можете урадити тако што " -"ћете изабрати одређене корисничке улоге на које се захтев примењује у " -"подешавању **Захтевано за корисничке улоге**. Наравно морате имати укључен " -"најмање један метход двофакторске аутентификације да би ово подешавање " -"ступило на снагу." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Address" +msgstr "Тикет > Клијент > Адреса" -#: ../settings/security/two-factor.rst:None -msgid "Enforced for User Roles Setting" -msgstr "Подешавање захтевано за корисничке улоге" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.address}``" +msgstr "``#{ticket.customer.address}``" -#: ../settings/security/two-factor.rst:62 -msgid "" -"After you change this setting, if the user has one of the selected roles on " -"their account, they will be forced to set up the two-factor authentication " -"upon next sign in or application reload." -msgstr "" -"Након што промените ово подешавање, ако корисник има једну од изабраних " -"улога на свом налогу, биће захтевано од њих да поставе двофакторску " -"аутентификацију приликом следећег пријављивања или поновног учитавања " -"апликације." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Avatar" +msgstr "Тикет > Клијент > Аватар" -#: ../settings/security/two-factor.rst:66 -msgid "" -"A modal dialog with instructions will be shown, and they will not be able to " -"do any work before they set up at least one two-factor method." -msgstr "" -"Биће приказан модални дијалог са упутствима и корисник неће моћи да ради са " -"системом пре него што постави бар један метод двофакторске аутентификације." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.avatar(60,60)}``" +msgstr "``#{ticket.customer.avatar(60,60)}``" -#: ../settings/security/two-factor.rst:None -msgid "Modal Dialog for Enforcing Two-Factor Authentication Set Up" -msgstr "Модални дијалог за захтевање поставке двофакторске аутентификације" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Department" +msgstr "Тикет > Клијент > Одељење" -#: ../settings/security/two-factor.rst:74 -msgid "Reset Two-Factor Authentication for a Specific User" -msgstr "Поништавање двофакторске аутентификација за конкретног корисника" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.department}``" +msgstr "``#{ticket.customer.department}``" -#: ../settings/security/two-factor.rst:76 -msgid "" -"In case an user isn't able to login anymore because of an inaccessible " -"second factor, you can reset the user's 2FA method." -msgstr "" -"У случају да корисник више није у могућности да се пријави због " -"недоступности другог фактора, можете поништити кориснички метод двофакторске " -"аутентификације." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Email" +msgstr "Тикет > Клијент > Имејл" -#: ../settings/security/two-factor.rst:79 -msgid "" -"To do this, go to the user management and search for the relevant user. " -"After you found the account, click the button in the action column and " -"select \"Manage Two-Factor Authentication\":" -msgstr "" -"Да бисте ово урадили, идите на уређивање корисника и претражите за " -"одговарајућег корисника. Након што пронађете налог, кликните на дугме у " -"колони радње и изаберите „Управљање двофакторском аутентификацијом”:" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.email}``" +msgstr "``#{ticket.customer.email}``" -#: ../settings/security/two-factor.rst:None -msgid "Context menu in action column in user management" -msgstr "Контекстни мени у колони радње у екрану уређивања корисника" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Fax" +msgstr "Тикет > Клијент > Факс" -#: ../settings/security/two-factor.rst:87 -msgid "" -"After selecting this, you can see a dialog where you can either reset one " -"2FA method or reset all of the user's 2FA methods:" -msgstr "" -"По одабиру, добићете дијалог где можете поништити или један или све методе " -"двофакторске аутентификације:" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.fax}``" +msgstr "``#{ticket.customer.fax}``" -#: ../settings/security/two-factor.rst:None -msgid "Dialog for resetting user's 2FA method" -msgstr "Дијалог за поништавање корисничких метода двофакторске аутентификације" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Firstname" +msgstr "Тикет > Клијент > Име" -#: ../settings/security/two-factor.rst:94 -msgid "" -"Choose the fitting one, click on the corresponding \"Remove ...\" button and " -"confirm your action. The user now has to setup a new 2FA method, depending " -"on your 2FA configuration." -msgstr "" -"Изаберите одговарујућу опцију, кликните на дугме „Уклони” и потврдите своју " -"радњу. Корисник ће сада морати да постави нови метод двофакторске " -"аутентификације, у зависности од ваше конфигурације." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.firstname}``" +msgstr "``#{ticket.customer.firstname}``" -#: ../settings/security/two-factor/authenticator-app.rst:2 -msgid "Authenticator App" -msgstr "Апликација за аутентификацију" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Lastname" +msgstr "Тикет > Клијент > Презиме" -#: ../settings/security/two-factor/authenticator-app.rst:4 -msgid "" -"The authenticator app method is a type of two-factor authentication that " -"uses a mobile application to generate one-time codes for account " -"verification. After setting up the authenticator app on their device, the " -"user links it to their Zammad account." -msgstr "" -"Метод апликације за аутентификацију је врста двофакторске аутентификације " -"која користи мобилну апликацију за генерисање једнократних кодова за " -"верификацију налога. Након подешавања апликације за аутентификацију на свом " -"уређају, корисник је повезује са својим Zammad налогом." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.lastname}``" +msgstr "``#{ticket.customer.lastname}``" -#: ../settings/security/two-factor/authenticator-app.rst:12 -msgid "" -"When logging in, the user is prompted to enter a time-sensitive code " -"generated by the app, in addition to their password. This code acts as the " -"second factor of authentication, providing an extra layer of security as it " -"changes periodically and is unique to the user's device." -msgstr "" -"Приликом пријављивања, од корисника се тражи да унесе временски осетљив код " -"који генерише апликација, поред своје лозинке. Овај код се примењује као " -"други фактор аутентификације, пружајући додатни ниво заштите пошто се " -"периодично мења и јединствен је за уређај корисника." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Login" +msgstr "Тикет > Клијент > Пријава" -#: ../settings/security/two-factor/authenticator-app.rst:None -msgid "Security Code in Google Authenticator App" -msgstr "Сигурносни код у апликацији Google Authenticator" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.login}``" +msgstr "``#{ticket.customer.login}``" -#: ../settings/security/two-factor/authenticator-app.rst:22 -msgid "" -"The app generates codes based on a shared secret key stored securely on both " -"the user's device and the server, ensuring a synchronized and secure " -"authentication process. The method of generating the codes is sometimes also " -"called TOTP (time-based one-time password)." -msgstr "" -"Апликација генерише кодове на основу дељеног тајног кључа који је безбедно " -"ускладиштен и на корисниковом уређају и на серверу, обезбеђујући " -"синхронизован и сигуран процес аутентификације. Метода генерисања кодова се " -"понекад назива и TOTP (једнократна лозинка заснована на времену)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Mobile" +msgstr "Тикет > Клијент > Мобилни" -#: ../settings/security/two-factor/authenticator-app.rst:28 -msgid "Enabling the Authenticator App Method" -msgstr "Укључивање метода апликације за аутентификацију" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.mobile}``" +msgstr "``#{ticket.customer.mobile}``" -#: ../settings/security/two-factor/authenticator-app.rst:30 -#: ../settings/security/two-factor/security-keys.rst:28 -msgid "To enable the method, just toggle the switch on in the settings." -msgstr "Да бисте укључили метод, само притисните прекидач у подешавањима." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Note" +msgstr "Тикет > Клијент > Напомена" -#: ../settings/security/two-factor/authenticator-app.rst:None -msgid "Authenticator App Switch in Settings" -msgstr "Прекидач апликације за аутентификацију у подешавањима" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.note}``" +msgstr "``#{ticket.customer.note}``" -#: ../settings/security/two-factor/authenticator-app.rst:36 -msgid "" -"Now the users will be able to set up this two-factor authentication method " -"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " -"Once they do, on next sign-in with password, they will be asked to provide " -"an additional security code generated by their mobile device." -msgstr "" -"Сада ће корисници моћи да подесе овај метод двофакторске аутентификације за " -"своје налоге преко „Аватар -> Профил -> Лозинка и аутентификација\". Када то " -"ураде, приликом следећег пријављивања путем лозинке, од њих ће се тражити да " -"приложе и додатни безбедносни код који генерише њихов мобилни уређај." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Phone" +msgstr "Тикет > Клијент > Телефон" -#: ../settings/security/two-factor/security-keys.rst:2 -msgid "Security Keys" -msgstr "Безбедносни кључеви" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.phone}``" +msgstr "``#{ticket.customer.phone}``" -#: ../settings/security/two-factor/security-keys.rst:4 -msgid "" -"The security keys method is a type of a two-factor authentication that uses " -"Web Authentication API in the browser for verifying user's identity. The " -"user can register multiple hardware or software security keys with their " -"Zammad account and then they can use it during the sign-in process." -msgstr "" -"Метод безбедносних кључева је врста двофакторске аутентификације која " -"користи Web Authentication API у претраживачу за верификацију идентитета " -"корисника. Корисник може да региструје више хардверских или софтверских " -"безбедносних кључева са својим Zammad налогом, а затим га може користити " -"током процеса пријављивања." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > VIP" +msgstr "Тикет > Клијент > VIP" -#: ../settings/security/two-factor/security-keys.rst:12 -msgid "" -"When logging in, the user is prompted to provide the same security key they " -"registered with their account, in addition to their password. This key acts " -"as the second factor of authentication, providing an extra layer of security." -msgstr "" -"Приликом пријављивања, од корисника се тражи да приложи исти сигурносни кључ " -"који је регистровао са својим налогом, поред своје лозинке. Овај кључ се " -"примењује као други фактор аутентификације, пружајући додатни ниво " -"безбедности." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.vip}``" +msgstr "``#{ticket.customer.vip}``" -#: ../settings/security/two-factor/security-keys.rst:None -msgid "Security Key dialog in Safari on macOS" -msgstr "" -"Дијалог за поставку безбедносног кључа у Safari претраживачу на macOS-у" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Web" +msgstr "Тикет > Клијент > Веб" -#: ../settings/security/two-factor/security-keys.rst:21 -msgid "" -"The type of the key can range from hardware USB sticks to passkeys stored in " -"a device of user's choice. Which type can be used depends on the browser " -"flavor and the platform of the user." -msgstr "" -"Тип кључа може се креће од хардверских USB флешева до приступних кључева " -"ускладиштених у уређају по избору корисника. Који тип се може користити " -"зависи од врсте претраживача и платформе корисника." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.web}``" +msgstr "``#{ticket.customer.web}``" -#: ../settings/security/two-factor/security-keys.rst:26 -msgid "Enabling the Security Keys Method" -msgstr "Укључивање метода безбедносних кључева" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Escalation at" +msgstr "Тикет > Ескалација у" -#: ../settings/security/two-factor/security-keys.rst:None -msgid "Security Keys Switch in Settings" -msgstr "Прекидач безбедносних кључева у подешавањима" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.escalation_at}``" +msgstr "``#{ticket.escalation_at}``" -#: ../settings/security/two-factor/security-keys.rst:34 -msgid "" -"Now the users will be able to set up this two-factor authentication method " -"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " -"Once they do, on next sign-in with password, they will be asked to provide " -"the same security key they registered during the setup." -msgstr "" -"Сада ће корисници моћи да подесе овај метод двофакторске аутентификације за " -"своје налоге преко „Аватар -> Профил -> Лозинка и аутентификација\". Када то " -"ураде, приликом следећег пријављивања путем лозинке, од њих ће се тражити да " -"приложе исти безбедносни кључ који су регистровали прликом поставке." +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable" +msgstr "``2019-10-07 16:25:00 UTC`` или празно ако не постоји" -#: ../settings/system/system-selfhosted.include.rst:3 -msgid "" -"Below settings are only available to self hosted users. In hosted " -"environments we're handling these settings for you to ensure service " -"stability." -msgstr "" -"Подешавања у наставку су доступна само корисницима који хостују сами. У " -"хостованом окружењу ми рукујемо овим подешавањима за вас да бисмо обезбедили " -"стабилност сервиса." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > First response" +msgstr "Тикет > Први одговор" -#: ../settings/system/base.rst:11 -msgid "Fully Qualified Domain Name" -msgstr "Квалификовани назив домена" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.first_response_at}``" +msgstr "``#{ticket.first_response_at}``" -#: ../settings/system/base.rst:7 -msgid "The URL of your Zammad installation." -msgstr "URL ваше инсталације Zammad-а." +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable yet" +msgstr "``2019-10-07 16:25:00 UTC`` или празно ако не постоји" -#: ../settings/system/base.rst:9 ../settings/system/base.rst:17 -msgid "This setting is used within :doc:`/system/variables` and notifications." -msgstr "" -"Ово подешавање се користи у оквиру :doc:`/system/variables` и обавештења." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Assign Follow-Ups" +msgstr "Тикет > Група > Додели наставке" -#: ../settings/system/system-base.include.rst:1 -msgid "It is automatically set by the *Getting Started wizard*." -msgstr "Аутоматски се поставља приликом *почетне поставке система*." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_assignment}``" +msgstr "``#{ticket.group.follow_up_assignment}``" -#: ../settings/system/system-base.include.rst:5 -msgid "Changing this setting also changes callback URLs for your channels etc." -msgstr "" -"Промена овог подешавања такође мења URL адресе за повратне позиве ваших " -"канала итд." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Assignment Timeout" +msgstr "Тикет > Група > Време истека доделе" -#: ../settings/system/system-base.include.rst:6 -msgid "This setting can have negative affects on being able to login." -msgstr "Ово подешавање може негативно утицати на могућност пријављивања." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.assignment_timeout}``" +msgstr "``#{ticket.group.assignment_timeout}``" -#: ../settings/system/base.rst:19 -msgid "HTTP type" -msgstr "HTTP протокол" +#: ../misc/variables/ticket.rst:1 +msgid "``20`` or empty if not configured" +msgstr "``20`` или празно ако није постављено" -#: ../settings/system/base.rst:14 -msgid "" -"The HTTP type tells your installation how your clients connect. This is " -"relevant for authentication and cookie security." -msgstr "" -"HTTP протокол одређује како се ваши клијенти повезују са вашом инсталацијом. " -"Ово је релевантно за аутентификацију и безбедност." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Follow-up possible" +msgstr "Тикет > Група > Могућ наставак" -#: ../settings/system/base.rst:31 -msgid "SystemID" -msgstr "SystemID" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_possible}``" +msgstr "``#{ticket.group.follow_up_possible}``" -#: ../settings/system/base.rst:22 -msgid "" -"This ID is being used within your ticket number. In case you're " -"communicating with another ticket system with similar ticket number schemes " -"this ID greatly reduces the risk of false follow ups." -msgstr "" -"Овај ID се користи у оквиру броја вашег тикета. У случају да комуницирате са " -"другим системом тикета са сличним шемама броја тикета, овај ID у великој " -"мери смањује ризик од лажних наставака." +#: ../misc/variables/ticket.rst:1 +msgid "``no`` or ``yes``" +msgstr "``no`` или ``yes``" -#: ../settings/system/base.rst:26 -msgid "" -"The SystemID is randomly selected upon installation of Zammad (``1-99``)." -msgstr "SystemID се насумично бира приликом инсталације Zammad-а (``1-99``)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Name" +msgstr "Тикет > Група > Назив" -#: ../settings/system/base.rst:30 -msgid "" -"**Do not** change this setting in a productive system! Your Zammad " -"installation may no longer recognize old ticket number based follow ups upon " -"change!" -msgstr "" -"**Не** мењајте ово подешавање на систему у продукцији! Ваша Zammad " -"инсталација можда више неће препознати старе наставке на основу броја тикета " -"након измене!" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.name}``" +msgstr "``#{ticket.group.name}``" -#: ../settings/system/frontend.rst:2 -msgid "Frontend" -msgstr "Интерфејс" +#: ../misc/variables/ticket.rst:1 +msgid "``Sales``" +msgstr "``Sales``" -#: ../settings/system/frontend.rst:22 -msgid "Core Workflow Ajax Mode" -msgstr "Ajax режим радног тока" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Note" +msgstr "Тикет > Група > Напомена" -#: ../settings/system/frontend.rst:6 -msgid "" -"This setting allows administrators to enforce :doc:`/system/core-workflows` " -"to use Ajax-Calls instead of web sockets. You'll usually only need this if " -"you experience serious issues as noted below." -msgstr "" -"Ово подешавање омогућава администраторима да наметну :doc:`радним токовима ` да користе Ajax позиве уместо web socket-а. Ово ће " -"вам бити неопходно само ако имате озбиљне проблеме као што је наведено у " -"наставку." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.note}``" +msgstr "``#{ticket.group.note}``" -#: ../settings/system/frontend.rst:10 -msgid "**🤓 Possible (technical) reasons**" -msgstr "**🤓 Могући (технички) разлози**" +#: ../misc/variables/ticket.rst:1 +msgid "``Note about this group``" +msgstr "``Напомена о овој групи`" -#: ../settings/system/frontend.rst:12 -msgid "" -"In some cases, your network structure (e.g. firewalls, proxies) may " -"disconnect long web socket connections. This leads to select fields staying " -"empty (e.g. owner selection *after* selecting your group) or fields not " -"shown / hidden (e.g. when switching to or from pending states, the \"pending " -"till\" field not showing / hiding)." -msgstr "" -"У неким случајевима, ваша мрежна инфраструктура (нпр. firewall, прокси " -"сервери) може да прекине дуге конекције путем web socket-а. Ово доводи до " -"тога да одабрана поља остају празна (нпр. избор власника *након* одабира " -"ваше групе) или поља која нису приказана/сакривена (нпр. када се прелази у " -"или из стања на чекању, поље „На чекању до“ се не приказује/сакрива)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > ID" +msgstr "Тикет > ID" -#: ../settings/system/frontend.rst:18 -msgid "" -"Please keep in mind that the Ajax fallback may cause serious pressure on " -"your application server. If you have the choice stick to web sockets." -msgstr "" -"Имајте на уму да Ajax режим може изазвати озбиљан притисак на апликативни " -"сервер. Ако имате избор, држите се web socket-а." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.id}``" +msgstr "``#{ticket.id}``" -#: ../settings/system/frontend.rst:22 -msgid "Default: ``no`` (inactive)" -msgstr "Подразумевано: ``не`` (искључено)" +#: ../misc/variables/ticket.rst:1 +msgid "``17``, ``5281``, ..." +msgstr "``17``, ``5281``, ..." -#: ../settings/system/frontend.rst:53 -msgid "Show calendar weeks in the picker of date/datetime fields" -msgstr "Приказ календарске недеље у бирачу поља датума и времена" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact (agent)" +msgstr "Тикет > Последњи одговор (оператер)" -#: ../settings/system/frontend.rst:25 -msgid "" -"With this setting you can instruct Zammad to provide week number display " -"globally for all users. Calendar with week number display are usually used " -"in business sectors and may not be relevant for everyone." -msgstr "" -"Са овим подешавањем можете наложити Zammad-у да обезбеди приказ броја недеље " -"на глобалном нивоу за све кориснике. Календар са приказом броја седмица се " -"обично користи у пословним секторима и можда није релевантан за све." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_agent_at}``" +msgstr "``#{ticket.last_contact_agent_at}``" -#: ../settings/system/frontend.rst:29 +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact (customer)" +msgstr "Тикет > Последњи одговор (клијент)" + +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_customer_at}``" +msgstr "``#{ticket.last_contact_customer_at}``" + +#: ../misc/variables/ticket.rst:1 msgid "" -"This setting affects *all areas* - you'll also see week numbers in the admin " -"panel for e.g. triggers and macros." +"``2019-10-07 16:25:00 UTC`` or empty if not applicable yet (Please note " +"`Ticket last contact behavior Settings `_ for this)" msgstr "" -"Ово подешавање утиче на *све области* - такође ћете видети бројеве недеља у " -"административном панелу за нпр. окидаче и макрои." +"``2019-10-07 16:25:00 UTC`` или празно ако не постоји (Обратите пажњу на " +"`подешавање понашања последњег одговора тикета `_)" -#: ../settings/system/frontend.rst:32 -msgid "Default: ``no`` (not shown)" -msgstr "Подразумевано: ``не`` (није приказано)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact" +msgstr "Тикет > Последњи одговор" -#: ../settings/system/frontend.rst:53 -msgid "Here's the difference:" -msgstr "Ево разлике:" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_at}``" +msgstr "``#{ticket.last_contact_at}``" -#: ../settings/system/frontend.rst:0 -msgid "Screenshot showing Zammad's date picker (in the default way)" -msgstr "" -"Снимак екрана који приказује Zammad-ов бирач датума (на подразумевани начин)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Number" +msgstr "Тикет > Број" -#: ../settings/system/frontend.rst:41 -msgid "Set to ``no``" -msgstr "Постављено на ``не``" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.number}``" +msgstr "``#{ticket.number}``" -#: ../settings/system/frontend.rst:0 -msgid "" -"Screenshot showing Zammad's date picker with\n" -"week numbers enabled" -msgstr "" -"Снимак екрана који приказује Zammad-ов бирач датума са\n" -"укљученим бројевима недеља" +#: ../misc/variables/ticket.rst:1 +msgid "``31001``, ``201910731001``, ..." +msgstr "``31001``, ``201910731001``, ..." -#: ../settings/system/frontend.rst:50 -msgid "Set to ``yes``" -msgstr "Постављено на ``да``" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain based assignment" +msgstr "Тикет > Организација > Додела на основу домена" -#: ../settings/system/index.rst:4 -msgid "" -"For your overview we split each tab within system settings into its own page:" -msgstr "" -"За бољи преглед поделили смо сваки језичак у системским подешавањима на " -"посебну страницу:" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain_assignment}``" +msgstr "``#{ticket.organization.domain_assignment}``" -#: ../settings/system/index.rst:16 -msgid "Console Based Settings" -msgstr "Подешавања путем конзоле" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain" +msgstr "Тикет > Организација > Домен" -#: ../settings/system/index.rst:18 -msgid "" -"There's some console based settings we didn't put into the UI. However, you " -"may find them helpful - you can find them in our :docs:`hidden settings ` section." -msgstr "" -"Постоје нека подешавања могућа само путем конзоле која нисмо ставили у " -"кориснички интерфејс. Међутим, можда вам могу бити од помоћи - можете их " -"пронаћи у нашем одељку за :docs:`скривена подешавања `." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain}``" +msgstr "``#{ticket.organization.domain}``" -#: ../settings/system/network.rst:2 -msgid "Network" -msgstr "Мрежа" +#: ../misc/variables/ticket.rst:1 +msgid "``domain.tld`` or empty if not set" +msgstr "``domain.tld`` или празно ако није постављено" -#: ../settings/system/network.rst:8 -msgid "" -"The proxy settings can only be saved after successfully testing the proxy " -"connection." -msgstr "" -"Подешавања проксија могу се сачувати само након успешног тестирања прокси " -"конекције." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Name" +msgstr "Тикет > Организација > Назив" -#: ../settings/system/network.rst:15 -msgid "Proxy Address." -msgstr "Прокси адреса" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.name}``" +msgstr "``#{ticket.organization.name}``" -#: ../settings/system/network.rst:12 -msgid "" -"Allows you to provide a proxy server if needed. This is relevant for network " -"communication by Zammad." -msgstr "" -"Омогућава вам да подесите прокси сервер ако је потребно. Ово је релевантно " -"за мрежну комуникацију од стране Zammad-а." +#: ../misc/variables/ticket.rst:1 +msgid "``Zammad GmbH`` or empty if not set" +msgstr "``Zammad GmbH`` или празно ако није постављено" -#: ../settings/system/network.rst:15 -msgid "It **does not** affect the update process or Elasticsearch." -msgstr "Ово **не** утиче на процес освежавања или Elasticsearch." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Note" +msgstr "Тикет > Организација > Напомена" -#: ../settings/system/network.rst:18 -msgid "Username for proxy connection." -msgstr "Корисничко име за прокси конекцију." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.note}``" +msgstr "``#{ticket.organization.note}``" -#: ../settings/system/network.rst:18 -msgid "" -"If your proxy server requires authentication, provide the username here." -msgstr "" -"Ако ваш прокси сервер захтева аутентификацију, овде унесите корисничко име." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Shared organization" +msgstr "Тикет > Организација > Заједничка организација" -#: ../settings/system/network.rst:21 -msgid "Password for proxy connection." -msgstr "Лозинка за прокси конекцију." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.shared}``" +msgstr "``#{ticket.organization.shared}``" -#: ../settings/system/network.rst:21 -msgid "" -"If your proxy server requires authentication, provide the password here." -msgstr "Ако ваш прокси сервер захтева аутентификацију, овде унесите лозинку." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > VIP" +msgstr "Тикет > Организација > VIP" -#: ../settings/system/network.rst:26 -msgid "No proxy for the following hosts." -msgstr "Без проксија за следеће сервере." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.vip}``" +msgstr "``#{ticket.organization.vip}``" -#: ../settings/system/network.rst:24 -msgid "" -"Exception list for hosts you can't or don't want to reach via proxy server." -msgstr "" -"Листа изузетака за хостове којима не можете или не желите да приступите " -"преко прокси сервера." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Address" +msgstr "Тикет > Власник > Адреса" -#: ../settings/system/network.rst:27 -msgid "Default: ``localhost,127.0.0.0,::1``" -msgstr "Подразумевано: ``localhost,127.0.0.0,::1``" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.address}``" +msgstr "``#{ticket.owner.address}``" -#: ../settings/system/services.rst:2 -msgid "Services" -msgstr "Услуге" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Avatar" +msgstr "Тикет > Власник > Аватар" -#: ../settings/system/services.rst:10 -msgid "Image Service" -msgstr "Услуга за слике" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.avatar(60,60)}``" +msgstr "``#{ticket.owner.avatar(60,60)}``" -#: ../settings/system/services.rst:5 -msgid "Defines the backend for user and organization image lookups." -msgstr "Одређује позадински модул за тражење сличица корисника и организација." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Department" +msgstr "Тикет > Власник > Одељење" -#: ../settings/system/services.rst:7 -msgid "Default: ``Zammad Image Service`` (active)" -msgstr "Подразумевано: ``Zammad сервис за слике`` (укључено)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.department}``" +msgstr "``#{ticket.owner.department}``" -#: ../settings/system/services.rst:9 -msgid "" -"Make sure your on premise installation has ``HTTPS`` access to ``images." -"zammad.com``." -msgstr "" -"Проверите да ваша локална инстанца има ``HTTPS`` приступ ``images.zammad." -"com``." +#: ../misc/variables/ticket.rst:1 +msgid "``Support`` or empty if not set" +msgstr "``Support`` или празно ако није постављено" -#: ../settings/system/services.rst:18 -msgid "Geo Calendar Service" -msgstr "Услуга географског календара" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Email" +msgstr "Тикет > Власник > Имејл" -#: ../settings/system/services.rst:13 -msgid "" -"Defines the backend for geo calendar lookups. Used for initial calendar " -"setup." -msgstr "" -"Одређује позадински модул за географско тражење календара. Користи се за " -"иницијалан одабир календара." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.email}``" +msgstr "``#{ticket.owner.email}``" -#: ../settings/system/services.rst:16 -msgid "Default: ``Zammad GeoCalendar Service`` (active)" -msgstr "Подразумевано: ``Zammad GeoCalendar сервис`` (укључено)" +#: ../misc/variables/ticket.rst:1 +msgid "``agent@company.tld`` or empty if not set" +msgstr "``agent@company.tld`` или празно ако није постављено" -#: ../settings/system/services.include.rst:2 -msgid "" -"Make sure your on premise installation has ``HTTPS`` access to ``geo.zammad." -"com``." -msgstr "" -"Проверите да ваша локална инстанца има ``HTTPS`` приступ ``geo.zammad.com``." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Fax" +msgstr "Тикет > Власник > Факс" -#: ../settings/system/services.rst:26 -msgid "Geo IP Service" -msgstr "Услуга географског IP" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.fax}``" +msgstr "``#{ticket.owner.fax}``" -#: ../settings/system/services.rst:21 -msgid "" -"Defines the backend for geo IP lookups. Shows also location of an IP address " -"if an IP address is shown." -msgstr "" -"Дефинише позадински модул за географске IP упите. Приказује и локацију IP " -"адресе ако је IP адреса приказана." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Firstname" +msgstr "Тикет > Власник > Име" -#: ../settings/system/services.rst:24 -msgid "Default: ``Zammad GeoIP Service`` (active)" -msgstr "Подразумевано: ``Zammad GeoIP сервис`` (укључено)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.firstname}``" +msgstr "``#{ticket.owner.firstname}``" -#: ../settings/system/services.rst:32 -msgid "Geo Location Service" -msgstr "Услуга географске локације" +#: ../misc/variables/ticket.rst:1 +msgid "``Max`` or empty if not set" +msgstr "``Max`` или празно ако није постављено" -#: ../settings/system/services.rst:29 -msgid "" -"Defines the backend for geo location lookups to store geo locations for " -"addresses." -msgstr "" -"Одређује позадински модул за географско тражење локација ради чувања " -"географских локација адреса." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Lastname" +msgstr "Тикет > Власник > Презиме" -#: ../settings/system/services.rst:32 -msgid "" -"Default: ``OpenStreetMap (ODbL 1.0, http://osm.org/copyright)`` (active)" -msgstr "" -"Подразумевано: ``OpenStreetMap (ODbL 1.0, http://osm.org/copyright)`` " -"(укључено)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.lastname}``" +msgstr "``#{ticket.owner.lastname}``" -#: ../settings/system/services.rst:36 -msgid "" -"You can find a detailed privacy information on what we store for how long on " -"our :docs:`Privacy Appendix ` inside of our System " -"Documentation." -msgstr "" -"Детаљне информације о приватности података и о томе шта чувамо и колико дуго " -"можете пронаћи у нашем :docs:`додатку о приватности ` унутар наше системске документације." +#: ../misc/variables/ticket.rst:1 +msgid "``Mustermann`` or empty if not set" +msgstr "``Mustermann`` или празно ако није постављено" -#: ../settings/system/storage.rst:2 -msgid "Storage" -msgstr "Складиштење" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Login" +msgstr "Тикет > Власник > Пријава" -#: ../settings/system/storage.rst:6 -msgid "" -"Here you can define where Zammad stores attachments for tickets and the " -"knowledge base. By default, we're writing to the ``Database`` - you can " -"switch to ``Filesystem`` or ``Simple Storage (S3)`` at any time. In this " -"case please have a look on the following instructions." -msgstr "" -"Овде можете одредити где Zammad складишти прилоге тикета и базе знања. " -"Подразумевано снима се у ``Базу података`` - можете да пређете на ``Систем " -"датотека`` или ``Simple Storage (S3)`` у било ком тренутку. У овом случају, " -"погледајте испод за упутство." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.login}``" +msgstr "``#{ticket.owner.login}``" -#: ../settings/system/storage.rst:11 -msgid "" -"If you have a busy Zammad instance, we strongly encourage you to use " -"filesystem storage instead of \"Database\". This will greatly improve system " -"performance (de-crease database load and size)." -msgstr "" -"Уколико имате Zammad инстанцу под већим оптерећењем, топло препоручујемо да " -"користите складиштење путем система датотека уместо „базе података”. Ово ће " -"убрзати перформансе система (и смањити оптерећење и величину базе података)." +#: ../misc/variables/ticket.rst:1 +msgid "``agent``" +msgstr "``agent``" -#: ../settings/system/storage.rst:19 -msgid "Database" -msgstr "База података" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Mobile" +msgstr "Тикет > Власник > Мобилни" -#: ../settings/system/storage.rst:17 -msgid "" -"This is the default storage method. The attachments are stored directly in " -"the database. If your Zammad instance grows, we recommend one of the other " -"methods to maintain performance." -msgstr "" -"Ово је подразумевани метод складиштења. Прилоги се чувају директно у бази " -"података. Ако ваша Zammad инстанца расте, препоручујемо прелазак на други " -"метод да бисте очували перформансе." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.mobile}``" +msgstr "``#{ticket.owner.mobile}``" -#: ../settings/system/storage.rst:38 -msgid "Filesystem" -msgstr "Систем датотека" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Note" +msgstr "Тикет > Власник > Напомена" -#: ../settings/system/storage.rst:22 -msgid "" -"This storage method is recommended for all Zammad instances, especially for " -"those with a higher load. If you choose filesystem, your files are written " -"to ``/opt/zammad/storage/``." -msgstr "" -"Овај метод складиштења је препоручен за све Zammad инстанце, поготову за оне " -"са већим оптерећењем. Ако сте изабрали метод датотека, ваше датотеке се " -"снимају у ``/opt/zammad/storage/``." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.note}``" +msgstr "``#{ticket.owner.note}``" -#: ../settings/system/storage.rst:26 -msgid "" -"Moving attachments from \"Database\" to \"Filesystem\" can be run during " -"production use. However, you should consider your framework conditions (e.g. " -"bandwidth, system load in production) to define the right moment." -msgstr "" -"Премештање прилога из „базе података” у „систем датотека” може се покренути " -"чак и на систему у продукцији. Међутим, треба имати на уму ваше услове " -"система (нпр. брзину магистрале, оптерећење система) да бисте одредили прави " -"тренутак за извршавање." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Phone" +msgstr "Тикет > Власник > Телефон" -#: ../settings/system/storage.rst:32 -msgid "**You noticed slow updates of Zammad?**" -msgstr "**Приметили сте спор одзив у Zammad-у?**" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.phone}``" +msgstr "``#{ticket.owner.phone}``" -#: ../settings/system/storage.rst:34 -msgid "" -"While Zammad is beeing updated, it enforces a recursive \"change " -"owner\" (chown) for this directory. For instances with many files this can " -"be time consuming. To mitigate that you can move your files and create a " -"symlink in ``/opt/zammad/storage/`` to the new directory. Of course you have " -"to make sure on your own that the permissions are always correct." -msgstr "" -"Приликом ажурирања, Zammad ће извршити „промену власника” (chown) за овај " -"директоријум. За инстанце са великим бројем датотека ово може потрајати. Да " -"бисте предупредили ово понашање можете преместити ваше датотеке и креирати " -"симболични линк у ``/opt/zammad/storage/`` на нови директоријум. Наравно " -"морате обезбедити да су дозволе новог директоријума увек исправне." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > VIP" +msgstr "Тикет > Власник > VIP" -#: ../settings/system/storage.rst:95 -msgid "Simple Storage (S3)" -msgstr "Simple Storage (S3)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.vip}``" +msgstr "``#{ticket.owner.vip}``" -#: ../settings/system/storage.rst:41 -msgid "" -"To use the Simple Storage (S3), you have to provide some settings, which " -"can't be accessed in the UI (see instructions below)." -msgstr "" -"Да бисте користили Simple Storage (S3) морате обезбедити нека подешавања, " -"којима не можете приступити путем корисничког интерфејса (погледајте " -"упутства испод)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Web" +msgstr "Тикет > Власник > Веб" -#: ../settings/system/storage.rst:44 -msgid "" -"⚠️ Please note that the current implementation is in its early stages and can " -"be modified in the future." -msgstr "" -"⚠️ Упозоравамо вас да је тренутна имплементација у раном стадијуму и да може " -"бити промењена у будућности." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.web}``" +msgstr "``#{ticket.owner.web}``" -#: ../settings/system/storage.rst:47 -msgid "" -"The prerequisite is to have access to a S3-compatible storage and to have " -"all necessary parameters available (which depends on your storage provider; " -"if in doubt, please ask there for help)." -msgstr "" -"Услов је да имате приступ S3 компатибилном складишту и да имате доступне све " -"захтеване параметере (који зависе од вашег провајдера складишта; ако нисте " -"сигурни, замолите их за помоћ)." +#: ../misc/variables/ticket.rst:1 +msgid "``https://zammad.com`` or empty if not set" +msgstr "``https://zammad.com`` или празно ако није постављено" -#: ../settings/system/storage.rst:51 -msgid "Steps to configure S3:" -msgstr "Кораци за подешавање S3:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Pending till" +msgstr "Тикет > На чекању до" -#: ../settings/system/storage.rst:53 -msgid "" -"Copy ``config/zammad/storage.yml.dist`` to ``config/zammad/storage.yml``" -msgstr "" -"Ископирајте ``config/zammad/storage.yml.dist`` у ``config/zammad/storage." -"yml``" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.pending_time}``" +msgstr "``#{ticket.pending_time}``" -#: ../settings/system/storage.rst:54 -msgid "Edit the copied file in one of the following ways:" -msgstr "Измените копирану датотеку на један од следећих начина:" +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not set" +msgstr "``2019-10-07 16:25:00 UTC`` или празно ако није постављено" -#: ../settings/system/storage.rst:56 -msgid "" -"Either provide your S3 configuration with one attribute per line like in the " -"upper area of the file" -msgstr "" -"Или обезбедите вашу S3 конфигурацију са једним атрибутом по линији на начин " -"како је то урађено на почетку датотеке" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Priority > Name" +msgstr "Тикет > Приоритет > Назив" -#: ../settings/system/storage.rst:58 -msgid "" -"Or provide your S3 configuration as an URL (which you can find at the end of " -"the file). Note: you can also provide this URL as environment variable (:" -"docs:`see system documentation `) without using this yml-file." -msgstr "" -"Или обезбедите вашу S3 конфигурацију као URL адресу (чији пример можете наћи " -"при крају датотеке). Напомена: такође можете обезбедити ову URL адресу као " -"променљиву окружења (:docs:`погледајте системску документацију `) без коришћења ове YML датотеке." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.priority.name}``" +msgstr "``#{ticket.priority.name}``" -#: ../settings/system/storage.rst:62 -msgid "" -"We recommend the deletion of the not used configuration style to avoid " -"inconsistencies." -msgstr "" -"Предлажемо брисање свих конфигурација које не користите да бисте избегли " -"недоследности." +#: ../misc/variables/ticket.rst:1 +msgid "``2 normal``" +msgstr "``2 normal``" -#: ../settings/system/storage.rst:65 -msgid "Restart Zammad so the config file / environment variable is loaded" -msgstr "" -"Рестартујте Zammad ради поновног учитавања конфигурационе датотеке / " -"променљиве окружења" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > State > Name" +msgstr "Тикет > Стање > Назив" -#: ../settings/system/storage.rst:66 -msgid "" -"Set the \"Storage Method\" in Zammad to ``Simple Storage (S3)`` in Settings " -"> System > Storage and click on \"Submit\". After that, Zammad checks your " -"configuration and the connection to the service and will raise an error " -"message if something is wrong." -msgstr "" -"Подесите „Метод складиштењa” у Zammad-у на ``Simple Storage (S3)`` преко " -"Подешавања > Систем > Складиште и кликните на „Пошаљи”. Након тога, Zammad " -"ће проверити вашу конфигурацију успостављајући конекцију са сервисом и " -"приказаће поруку грешке ако нешто пође наопако." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.state.name}``" +msgstr "``#{ticket.state.name}``" -#: ../settings/system/storage.rst:72 -msgid "A very simple storage configuration could look like this:" -msgstr "Врло једноставна конфигурација складишта би могла личити на следеће:" +#: ../misc/variables/ticket.rst:1 +msgid "``new``, ``open``, ..." +msgstr "``new``, ``open``, ..." -#: ../settings/system/storage.rst:85 +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Tags" +msgstr "Тикет > Ознаке" + +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.tags}``" +msgstr "``#{ticket.tags}``" + +#: ../misc/variables/ticket.rst:1 msgid "" -"Before setting the storage method to ``Simple Storage (S3)`` (step 4), " -"please make sure to have a working setup." +"Currently not available, see `Issue 2769 `_" msgstr "" -"Пре постављања метода складиштења на ``Simple Storage (S3)`` (корак 4), " -"молимо проверите да ли ваш сервис функционише." +"Тренутно није доступно, погледајте `извештај 2769 `_" -#: ../settings/system/storage.rst:88 -msgid "" -"You can verify this by running ``rails r 'Rails.logger = Logger.new(STDOUT); " -"pp Store::Provider::S3.ping?'`` in your Zammad directory. If everything is " -"fine, you should see ``true``, else you should see ``false`` and a simple " -"error message." -msgstr "" -"Ово можете проверити извршавањем команде ``rails r ‘Rails.logger = Logger." -"new(STDOUT); pp Store::Provider::S3.ping?’`` у вашем Zammad директоријуму. " -"Уколико је све у реду, требало би да видите ``true``, у супротном биће " -"приказано ``false` са кратком поруком о грешци." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Title" +msgstr "Тикет > Наслов" -#: ../settings/system/storage.rst:93 -msgid "" -"If you installed Zammad through a package manager (rather than from source), " -"replace ``rails r`` with ``zammad run rails r`` above. To learn more, see :" -"docs:`Administration via Console `." -msgstr "" -"Ако сте инсталирали Zammad путем менаџера пакета (а не преко изворне " -"архиве), замените ``rails r`` са ``zammad run rails r`` изнад. За више " -"детаља, погледајте :docs:`администрацију путем конзоле `." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.title}``" +msgstr "``#{ticket.title}``" -#: ../settings/ticket.rst:4 +#: ../misc/variables/ticket.rst:1 msgid "" -"Here you can adjust general ticket settings. Additional ones for the ticket " -"composer interface can be found in the :doc:`/misc/composer`." +"``My amazing Subject`` (normally subject, can be edited within Interface and " +"thus differ)" msgstr "" -"Овде можете подесити општа подешавања тикета. Додатна подешавања за " -"интерфејс уредника текста могу се наћи у :doc:`/misc/composer`." +"``Мој екстра наслов`` (обично предмет поруке, може се изменити унутар " +"корисничког интерфејса)" -#: ../settings/ticket.rst:11 -msgid "Ticket Hook (default: ``Ticket#``)" -msgstr "Прикључак тикета (подразумевано: ``Ticket#``)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated at" +msgstr "Тикет > Освежено у" -#: ../settings/ticket.rst:11 -msgid "The identifier for a ticket; *e.g.,* Ticket#, Call#, MyTicket#." -msgstr "Идентификатор тикета, нпр. Ticket#, Call#, MyTicket#." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_at}``" +msgstr "``#{ticket.updated_at}``" -#: ../settings/ticket.rst:38 -msgid "Ticket Hook Position (default: ``right``)" -msgstr "Положај прикључка тикета (подразумевано: ``десно``)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Address" +msgstr "Тикет > Освежено од стране > Адреса" -#: ../settings/ticket.rst:14 -msgid "" -"With this setting you can decide (if) where to insert the ticket number." -msgstr "" -"Са овим подешавањем можете одлучити (да ли и) где се налази број тикета." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.address}``" +msgstr "``#{ticket.updated_by.address}``" -#: ../settings/ticket.rst:20 -msgid "*Right*" -msgstr "*десно*" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Avatar" +msgstr "Тикет > Освежено од стране > Аватар" -#: ../settings/ticket.rst:17 -msgid "" -"This setting will add the ticket reference on the right site of the subject." -msgstr "Ово подешавање ће додати референцу тикета на десној страни предмета." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.avatar(60,60)}``" +msgstr "``#{ticket.updated_by.avatar(60,60)}``" -#: ../settings/ticket.rst:20 -msgid "Example: ``Some Subject [Ticket#12345]``" -msgstr "Пример: ``Неки предмет [Ticket#12345]``" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Department" +msgstr "Тикет > Освежено од стране > Одељење" -#: ../settings/ticket.rst:26 -msgid "*Left*" -msgstr "*лево*" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.department}``" +msgstr "``#{ticket.updated_by.department}``" -#: ../settings/ticket.rst:23 -msgid "" -"This setting will add the ticket reference on the left site of the subject." -msgstr "Ово подешавање ће додати референцу тикета на десној страни предмета." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Email" +msgstr "Тикет > Освежено од стране > Имејл" -#: ../settings/ticket.rst:26 -msgid "Example: ``[Ticket#12345] Some Subject``" -msgstr "Пример: ``[Ticket#12345] Неки предмет``" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.email}``" +msgstr "``#{ticket.updated_by.email}``" -#: ../settings/ticket.rst:29 -msgid "*None*" -msgstr "*празно*" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Fax" +msgstr "Тикет > Освежено од стране > Факс" -#: ../settings/ticket.rst:29 -msgid "This will completely remove ticket references from the subject." -msgstr "Ово ће у потпуности уклонити референце тикета из предмета." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.fax}``" +msgstr "``#{ticket.updated_by.fax}``" -#: ../settings/ticket.rst:33 -msgid "" -"Please ensure to take a look at :doc:`/channels/email/settings` within the " -"email channel to ensure you have at least one reference that helps Zammad to " -"assign follow-ups correctly." -msgstr "" -"Обавезно погледајте :doc:`подешавања ` у оквиру " -"имејл канала да бисте били сигурни да имате бар једну референцу која помаже " -"Zammad-у да правилно додели наставке." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Firstname" +msgstr "Тикет > Освежено од стране > Име" -#: ../settings/ticket.rst:37 -msgid "" -"Disabling this and not setting up any further follow up search will lead to " -"unexpected results!" -msgstr "" -"Онемогућавање овога и неподешавање даље претраге наставака ће довести до " -"неочекиваних резултата!" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.firstname}``" +msgstr "``#{ticket.updated_by.firstname}``" -#: ../settings/ticket.rst:65 -msgid "" -"Ticket Last Contact Behaviour (default: ``Use the start time of the last " -"customer thread (which may consist of multiple articles).``)" -msgstr "" -"Понашање последњег одговора тикета (подразумевано: ``Користи време почетка " -"последње конверзације клијента (која се може састојати од више чланака).``)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Lastname" +msgstr "Тикет > Освежено од стране > Презиме" -#: ../settings/ticket.rst:41 -msgid "" -"This setting changes the way Zammad updates the ``Last Contact`` value of a " -"ticket. This is fairly important for overviews and what you expect upon " -"ticket updates of a customer." -msgstr "" -"Ово подешавање мења начин на који Zammad освежава атрибут тикета „Последњи " -"одговор“. Ово је прилично важно за прегледе и оно што очекујете након " -"освежавања тикета од стране корисника." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.lastname}``" +msgstr "``#{ticket.updated_by.lastname}``" -#: ../settings/ticket.rst:52 -msgid "" -"Use the start time of the last customer thread (which may consist of " -"multiple articles)." -msgstr "" -"Користи време почетка последње конверзације клијента (која се може састојати " -"од више чланака)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Login" +msgstr "Тикет > Освежено од стране > Пријава" -#: ../settings/ticket.rst:46 -msgid "" -"If this option is chosen, Zammad will update the last updated value just " -"once if a customer replies. After that, Zammad will wait for an agent to " -"react." -msgstr "" -"Ако се изабере ова опција, Zammad ће освежити вредност атрибута само једном " -"приликом одговора клијента. Након тога, Zammad ће сачекати да оператер " -"реагује." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.login}``" +msgstr "``#{ticket.updated_by.login}``" -#: ../settings/ticket.rst:50 -msgid "" -"This comes in handy if you want to work tickets in the order of their first " -"update. This will not change ticket orders if customers decide to \"bump\" " -"the ticket affected." -msgstr "" -"Ово је згодно ако желите да радите на тикетима према редоследу њиховог првог " -"освежавања. Ово неће променити редослед тикета ако клијенти одлуче да само " -"„чукну” своје тикете." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Mobile" +msgstr "Тикет > Освежено од стране > Мобилни" -#: ../settings/ticket.rst:57 -msgid "Use the time of the very last customer article." -msgstr "Користи време последњег чланка клијента." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.mobile}``" +msgstr "``#{ticket.updated_by.mobile}``" -#: ../settings/ticket.rst:55 -msgid "" -"When setting this option, Zammad will always update the last updated value. " -"This means that if ordering by ``Last Update``, ticket orders will change if " -"customers \"bump\" the ticket." -msgstr "" -"Када одаберете ову опцију, Zammad ће увек освежити вредност атрибута. То " -"значи да ако сортирате према ``последњем одговору``, редослед тикета ће се " -"променити ако клијенти само „чукну” тикет." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Note" +msgstr "Тикет > Освежено од стране > Напомена" -#: ../settings/ticket.rst:64 -msgid "Last contact value used on :doc:`/manage/overviews`" -msgstr "" -"Вредност последњег одговора коришћена у :doc:`прегледима `" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.note}``" +msgstr "``#{ticket.updated_by.note}``" -#: ../settings/ticket.rst:65 -msgid "Last contact value used on :doc:`/manage/trigger`" -msgstr "" -"Вредност последњег одговора коришћена у :doc:`окидачима `" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Phone" +msgstr "Тикет > Освежено од стране > Телефон" -#: ../settings/ticket.rst:88 -msgid "" -"Ticket Organization Reassignment (default: ``Update the most recent tickets." -"``)" -msgstr "" -"Пребацивање тикета организације (подразумевано: ``Освежи недавне тикете.``)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.phone}``" +msgstr "``#{ticket.updated_by.phone}``" -#: ../settings/ticket.rst:68 -msgid "" -"This setting changes the way Zammad updates the organization field of the " -"tickets whenever the primary organization of a user is changed." -msgstr "" -"Ово подешавање мења начин на који Zammad освежава поље организације тикета " -"кад год се промени примарна организација корисника." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > VIP" +msgstr "Тикет > Освежено од стране > VIP" -#: ../settings/ticket.rst:74 -msgid "Update the most recent tickets." -msgstr "Освежи недавне тикете." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.vip}``" +msgstr "``#{ticket.updated_by.vip}``" -#: ../settings/ticket.rst:72 -msgid "" -"If this option is chosen, Zammad will update the 100 most recent tickets " -"where the user is the ticket customer. The ticket organization field will be " -"automatically set to the new primary organization of the user." -msgstr "" -"Ако се изабере ова опција, Zammad ће освежити 100 најновијих тикета где је " -"корисник клијент тикета. Поље организације тикета ће аутоматски бити " -"постављено на нову примарну организацију корисника." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Web" +msgstr "Тикет > Освежено од стране > Веб" -#: ../settings/ticket.rst:88 -msgid "Do not update any tickets." -msgstr "Без освежавања тикета." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.web}``" +msgstr "``#{ticket.updated_by.web}``" -#: ../settings/ticket.rst:77 +#: ../settings/branding.rst:10 +msgid "Product Name" +msgstr "Назив производа" + +#: ../settings/branding.rst:7 msgid "" -"When choosing this option, Zammad will not update any tickets when the " -"user's primary organization is changed." +"Defines the name of the application, shown in the web interface, tabs and " +"title bar of the web browser." msgstr "" -"Када изаберете ову опцију, Zammad неће освежити ниједан тикет када се " -"промени примарна организација корисника." +"Одређује назив апликације, који се приказује у веб интерфејсу, прозорима и " +"наслову интернет претраживача." -#: ../settings/ticket.rst:80 -msgid "**Use with care!**" -msgstr "**Користите пажљиво!**" +#: ../settings/branding.rst:10 +msgid "Default value: ``Zammad Helpdesk``" +msgstr "Подразумевана вредност: ``Zammad Helpdesk``" -#: ../settings/ticket.rst:82 -msgid "" -"Using this option may lead to inconsistencies in the system as the ticket " -"organization may become decoupled from the ticket customer." -msgstr "" -"Коришћење ове опције може довести до недоследности у систему јер се " -"организација тикета може одвојити од клијента тикета." +#: ../settings/branding.rst:13 +msgid "Will be shown in the app and is included in email footers." +msgstr "Биће приказано у апликацији и убачено при дну имејл порука." -#: ../settings/ticket.rst:85 -msgid "" -"However, you may use this option if you wish to maintain :ref:`the shared " -"access ` to the ticket for all organization " -"members of the original organization of the customer." -msgstr "" -"Међутим, можете користити ову опцију ако желите да задржите :ref:`дељени " -"приступ ` на тикету за све чланове " -"организације првобитне организације корисника." +#: ../settings/branding.rst:19 +msgid "Logo" +msgstr "Лого" -#: ../settings/ticket.rst:110 -msgid "Ticket Number Format (default: ``Increment (SystemID.Counter)``)" -msgstr "Формат броја тикета (подразумевано: ``Увећање (SystemID.бројач)``)" +#: ../settings/branding.rst:16 +msgid "Defines the logo of the application, shown in the login page of Zammad." +msgstr "Одређује лого апликације, приказан на страници за пријаву у Zammad." -#: ../settings/ticket.rst:94 +#: ../settings/branding.rst:18 msgid "" -"This setting defines the way Zammad's ticket number will look. Changing this " -"setting in production will cause follow up detection to fail." +"Ensure to hit the \"Submit\" button after uploading the logo. Otherwise your " +"change will not be saved." msgstr "" -"Ово подешавање одређује изглед Zammad-овог броја тикета. Промена овог " -"подешавања на системима у продукцији ће довести до неуспешног откривања " -"наставака." - -#: ../settings/ticket.rst:102 -msgid "Increment (SystemID.Counter)" -msgstr "Увећање (SystemID.бројач)" +"Обавезно притисните дугме „Пошаљи“ након што отпремите логотип. У супротном, " +"ваша промена неће бити сачувана." -#: ../settings/ticket.rst:98 +#: ../settings/branding.rst:22 msgid "" -"The increment value contains the SystemID (automatically generated during " -"installation) and a increment which counts up with every new Ticket. The " -"increment will automatically get another digit if needed." +"Allows to set the default language of the Zammad instance. The here defined " +"locale mostly acts as a fallback for:" msgstr "" -"Вредност бројача садржи SystemID (аутоматски генерисан током инсталације) и " -"бројач који се рачуна са сваким новом тикетом. Увећање ће аутоматски вратити " -"другу вредност ако је потребно." - -#: ../settings/ticket.rst:102 -msgid "Examples: ``1010138``, ``1010139``" -msgstr "Примери: ``1010138``, ``1010139``" - -#: ../settings/ticket.rst:110 -msgid "Date (Year.Month.Day.SystemID.Counter)" -msgstr "Датум (година.месец.дан.системID.бројач)" +"Омогућава постављање подразумеваног језика инстанце Zammad. Овде дефинисани " +"језик углавном делује као резервни за:" -#: ../settings/ticket.rst:105 -msgid "" -"This version of the ticket number is fairly long. However, because it " -"contains the date of ticket creation, it also allows you to see when the " -"ticket has been created. You may feel familiar with this number format if " -"you've worked with OTRS already." +#: ../settings/branding.rst:25 +msgid "user preferences (if Zammad can't detect the users locale)" msgstr "" -"Овај облик броја тикета је прилично дугачак. Међутим, пошто садржи датум " -"отварања тикета, такође вам омогућава да видите када је тикет отворен. Можда " -"вам је познат овај формат броја ако сте већ радили са OTRS-ом." +"корисничка подешавања (ако Zammad не може да открије корисникову локацију)" -#: ../settings/ticket.rst:110 -msgid "Examples: ``201206231010138``, ``201206231010139``" -msgstr "Примери: ``201206231010138``, ``201206231010139``" +#: ../settings/branding.rst:26 +msgid "CSV output (reporting, time accounting)" +msgstr "CSV излаз (извештавање, обрачунато време)" -#: ../settings/ticket.rst:137 -msgid "OPTIONS" -msgstr "Опције" +#: ../settings/branding.rst:30 +msgid "Define the timezone of your Zammad installation." +msgstr "Дефинишите временску зону ваше инсталације Zammad-а." -#: ../settings/ticket.rst:113 +#: ../settings/branding.rst:32 msgid "" -"The below options allow you to further customize your ticket number. The " -"availability of options differ depending of the chosen ticket number format " -"above." +"This does not have any effect on timings for your agents or how Zammad " +"stores date and time values." msgstr "" -"Опције у наставку вам омогућавају да додатно прилагодите број својих тикета. " -"Доступност опција се разликује у зависности од изабраног формата броја " -"тикета изнад." +"Ово нема никаквог утицаја на мерење учинка ваших оператера или начин на који " +"Zammad чува вредности датума и времена." -#: ../settings/ticket.rst:122 -msgid "Checksum (default: ``no``)" -msgstr "Контролни збир (подразумевано: ``не``)" +#: ../settings/branding.rst:35 +msgid "Changing this value has direct consequences on the following areas:" +msgstr "Промена ове вредности има директне последице на следеће области:" -#: ../settings/ticket.rst:118 -msgid "" -"If set to yes, we'll built a checksum to further \"unique\" the ticket " -"number of your system. If you're dealing with many other ticket systems this " -"might help to prevent false positive follow up detection on tickets." -msgstr "" -"Ако је постављено на да, биће израчунат контролни збир да би број тикета " -"вашег система остао „јединствен”. Ако се повезујете са другим системима " -"тикета, ово би могло помоћи да спречите откривање лажних наставака тикета." +#: ../settings/branding.rst:37 +msgid ":doc:`/manage/scheduler` tasks" +msgstr "послове :doc:`планера `" -#: ../settings/ticket.rst:122 -msgid "This will also add another digit to the ticket number." -msgstr "Ово ће такође додати још једну цифру броју тикета." +#: ../settings/branding.rst:38 +msgid "search indexing (and thus reporting)" +msgstr "индексирање претраге (а самим тим и извештавање)" -#: ../settings/ticket.rst:137 -msgid "Min. size of Number (default: ``5``)" -msgstr "Минимална величина броја (подразумевано: ``5``)" +#: ../settings/branding.rst:40 +msgid "calendar subscriptions" +msgstr "претплате на календаре" -#: ../settings/ticket.rst:125 +#: ../settings/branding.rst:41 +msgid "browser printing" +msgstr "штампу из претраживача" + +#: ../settings/branding.rst:43 msgid "" -"This setting defines the minimum length of your ticket number. If your " -"counter is not yet high enough, Zammad will fill the number with zeros to " -"ensure the wanted length." +"Please note that some of above are fallbacks in case Zammad could not detect " +"the agents timezone correctly." msgstr "" -"Ово подешавање одређује минималну дужину броја ваших тикета. Ако ваш бројач " -"још увек није довољно висок, Zammad ће попунити број нулама да би обезбедио " -"жељену дужину." +"Имајте на уму да су неке ставке изнад резервне опције у случају да Zammad не " +"може да прецизно открије временску зону оператера." -#: ../settings/ticket.rst:129 +#: ../settings/branding.rst:77 +msgid "Pretty Date" +msgstr "Лепши формат датума" + +#: ../settings/branding.rst:47 msgid "" -"Please note that the minimum length is ``3`` (SystemID + at least one digit " -"if below 10). Also, if the length is no longer long enough, the number will " -"automatically get one digit longer. Ticket-Numbers **do not overflow**, thus " -"it's save to keep it at 5 or set it lower if wanted." +"This setting allows you to define how Zammad should display time stamps " +"within the interface to all users." msgstr "" -"Имајте на уму да је минимална дужина ``3`` (ID система + најмање једна цифра " -"ако је испод 10). Такође, ако дужина више није довољна, број ће аутоматски " -"добити додатну цифру. Бројеви тикета се **не обрћу**, тако да је безбедно да " -"дужину задржите на 5 или је смањите ако желите." +"Ова поставка вам омогућава да одредите како Zammad треба да приказује " +"временске ознаке унутар интерфејса за све кориснике." -#: ../settings/ticket.rst:135 +#: ../settings/branding.rst:50 msgid "" -"This option is only available if ticket number format is set to " -"``Increment``!" +"This does not have any effect on how Zammad returns e.g. time values via " +"variables." msgstr "" -"Ова опција је доступна само ако је формат броја тикета подешен на " -"``Увећање``!" +"Ово нема никаквог утицаја на то како се Zammad враћа нпр. временске " +"вредности путем променљивих." -#: ../settings/ticket.rst:142 -msgid "Auto-Assignment" -msgstr "Аутоматска додела" +#: ../settings/branding.rst:77 +msgid "Choose in between the following options:" +msgstr "Изаберите између следећих опција:" -#: ../settings/ticket.rst:144 +#: ../settings/branding.rst:64 +msgid "relative" +msgstr "релативно" + +#: ../settings/branding.rst:55 msgid "" -"In a larger Zammad environment, it happens that several agents open the same " -"ticket at the same time. Although collision detection is then effective, the " -"efficiency of processing can be increased by means of the automatic " -"assignment of tickets when a ticket is opened." +"This timestamp shows a relative time span until it switches to a date. Over " +"time, it will change as follows:" msgstr "" -"У већем Zammad окружењу дешава се да неколико оператера отвори исти тикет у " -"исто време. Иако је детекција колизије тада у игри, ефикасност обраде се " -"може повећати аутоматском доделом тикета по отварању тикета." +"Ова временска ознака приказује релативни период до достизања датума. " +"Временом ће се мењати на следећи начин:" -#: ../settings/ticket.rst:149 -msgid "" -"The automatic assignment of tickets can be activated and configured in the " -"admin area under Settings > Ticket > Auto Assignment." +#: ../settings/branding.rst:58 +msgid "just now" +msgstr "малопре" + +#: ../settings/branding.rst:59 +msgid "5 minutes ago" +msgstr "пре 5 минута" + +#: ../settings/branding.rst:60 +msgid "3 days 1 hour ago" +msgstr "пре 3 дана 1 сат" + +#: ../settings/branding.rst:61 +msgid "``03/04/2022``" +msgstr "``03/04/2022``" + +#: ../settings/branding.rst:63 +msgid "Hovering the timestamp helps, you'll always get a clean timestamp then." msgstr "" -"Аутоматска додела тикета се може активирати и подесити у области " -"администрације у одељку Подешавања > Тикет > Аутоматска додела." +"Преласком курсора преко временске ознаке увек ћете добити прецизну временску " +"ознаку." -#: ../settings/ticket.rst:152 +#: ../settings/branding.rst:71 +msgid "absolute" +msgstr "апсолутно" + +#: ../settings/branding.rst:67 msgid "" -"The auto assignment only works if the ticket has no owner yet. By default, " -"the agent can always reset the ticket owner to ``-`` if needed." +"This timestamp always includes the week day. For one week after creation, " +"the timestamp will not contain the date itself: Thursday 18:35." msgstr "" -"Аутоматска додела се извршава само ако тикет још увек нема власника. " -"Подразумевано, оператер увек може да врати власника тикета на ``-`` ако је " -"потребно." +"Ова временска ознака увек укључује дан у недељи. Недељу дана након додавања " +"временска ознака неће садржати сам датум: четвртак 18:35." -#: ../settings/ticket.rst:155 +#: ../settings/branding.rst:71 +msgid "After a week it will switch to: ``Friday 4. Mar 16:00``." +msgstr "После недељу дана прелази на следеће: петак 4. март 16:00." + +#: ../settings/branding.rst:76 +msgid "timestamp" +msgstr "временска ознака" + +#: ../settings/branding.rst:74 msgid "" -"If you want to use this function for only specific tickets, you can " -"configure the conditions accordingly to meet your requirement. By default " -"the condition affects all tickets with the state ``open``." +"This will cause Zammad to show a complete timestamp according to your locale " +"defaults. For English this could be e.g. ``2022/12/03 2:40 pm`` or for " +"German e.g. ``12.03.2022 14:40``." msgstr "" -"Ако желите да користите ову функцију само за одређене тикете, можете да " -"подесите услове у складу са вашим захтевима. Подразумевано услов утиче на " -"све тикете са стањем ``отворено``." +"Ово ће довести до тога да Zammad прикаже комплетну временску ознаку у складу " +"са вашом подразумеваном локацијом. За енглески ово би значило нпр. " +"``2022/12/03 2:40 pm`` или за немачки нпр. ``12.03.2022 14:40``." -#: ../settings/ticket.rst:161 -msgid "" -"If you need to exclude users (e.g. a group leader), you can search and " -"select the desired agents in the ``Exception Users`` list. The search " -"function in this area is only effective, if you have too many agents to " -"display at once to help you with the configuration." -msgstr "" -"Уколико је потребно да изфилтрирате кориснике (нпр. тим лидера), можете " -"претраживати по оператерима у листи ``Изузети корисници``. Функција претраге " -"у овој области има ефекта само ако имате превише оператера за приказ " -"одједном, да би вам помогла при подешавању." - -#: ../settings/ticket.rst:167 -msgid "Notifications" -msgstr "Обавештења" - -#: ../settings/ticket.rst:191 -msgid "Default Notifications" -msgstr "Подразумевана обавештења" +#: ../settings/branding.rst:78 +msgid "Default setting: ``relative``." +msgstr "Подразумевана поставка: ``релативно``." -#: ../settings/ticket.rst:170 -msgid "" -"This setting allows you to configure the default ticket notifications that " -"will be applied to all new agent users (incl. users who were just assigned " -"agent role). Simply change the notification matrix to desired state and " -"press **Save**." -msgstr "" -"Ово подешавање вам омогућава да одредите подразумевана обавештења о тикету " -"која ће бити примењена на све нове кориснике оператере (укључујући и " -"кориснике којима је управо додељена улога оператера). Једноставно измените " -"матрицу обавештења у жељено стање и притисните **Сачувај**." +#: ../settings/security.rst:2 +msgid "Security" +msgstr "Безбедност" -#: ../settings/ticket.rst:175 +#: ../settings/security.rst:4 msgid "" -"In case an agent already exists, their ticket notification preferences will " -"be preserved. Optionally, you can also **Apply current defaults to all " -"agents**." +"For your overview we split each tab within security settings into its own " +"page:" msgstr "" -"У случају да оператер већ постоји, њихова подешавања обавештења о тикетима " -"ће бити сачувана. Опционо, такође можете **Применити подешавања свим " -"оператерима** и тада ће нова подразумевана подешавања бити примењена на све " -"оператере." +"Ради бољег прегледа поделили смо сваки језичак унутар безбедносних " +"подешавања на сопствену страницу:" -#: ../settings/ticket.rst:181 -msgid "" -"**Potential time-consuming action:** Applying default ticket notifications " -"to all agent users may take some time to complete, be patient! The exact " -"time will depend on the size of your system and the number of agents." -msgstr "" -"**Потенцијално дугачка радња:** примена подразумеваних обавештења о тикетима " -"на све кориснике оператере може потрајати, будите стрпљиви! Тачно време ће " -"зависити од величине вашег система и броја оператера." +#: ../settings/security/base.rst:2 ../settings/system/base.rst:2 +#: ../settings/ticket.rst:8 +msgid "Base" +msgstr "Основе" -#: ../settings/ticket.rst:185 -msgid "" -"**Active agents only!** When current default ticket notifications are " -"applied, only active agent users are considered. In case an agent is re-" -"activated *after* this action, they will still have the old notification " -"configuration." -msgstr "" -"**Само активни оператери!** Када се примењују тренутна подразумевана " -"обавештења о тикетима, узимају се у обзир само активни корисници оператери. " -"У случају да се оператер поново активира *после* ове акције, он ће и даље " -"имати стара подешавања обавештења." +#: ../settings/security/base.rst:5 +msgid "New User Accounts" +msgstr "Нови кориснички налози" -#: ../settings/ticket.rst:190 +#: ../settings/security/base.rst:9 msgid "" -"In case you want to go back to the initial state of ticket notifications, " -"you can click on **Reset to default** button." +"Activates the `register as a new customer` function on the login page. If " +"set to ``no`` only administrators or agents can create new accounts manually." msgstr "" -"У случају да желите да се вратите на почетно стање обавештења о тикету, " -"можете да кликнете на дугме **Поништи вредности**." +"Активира функцију `Региструј се као нови клијент` на страници за пријаву. " +"Ако је подешено на ``не`` само администратори или оператер могу ручно да " +"додају нове налоге." -#: ../settings/ticket.rst:194 ../settings/ticket.rst:196 -msgid "Duplicate Detection" -msgstr "Откривање дупликата" +#: ../settings/security/base.rst:13 ../settings/security/base.rst:38 +#: ../settings/security/base.rst:66 +msgid "Default setting: ``yes``" +msgstr "Подразумевано подешавање: ``да``" -#: ../settings/ticket.rst:236 ../settings/ticket.rst:238 -msgid "Detect Duplicate Ticket Creation" -msgstr "Откривање дупликата тикета приликом отварања" +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"New User Accounts\" setting" +msgstr "Слика која приказује укључено подешавање „Нови кориснички налози“" -#: ../settings/ticket.rst:197 ../settings/ticket.rst:199 +#: ../settings/security/base.rst:22 msgid "" -"This setting turns on the duplicate ticket detection mechanism during ticket " -"creation. If similar tickets are found in the system, a suitable warning " -"will be shown to the user trying to create a ticket." +"Deactivation of above function **does not** deactivate automatic account " +"creation! This means: If a user writes e.g. an email to Zammad and has no " +"account yet, Zammad will automatically create the account. User accounts are " +"a direct dependency of tickets and thus technically mandatory." msgstr "" -"Ово подешавање укључује механизам за откривање дупликата тикета током " -"отварања тикета. Ако се пронађу слични тикети у систему, кориснику који " -"покушава да отвори нови тикет биће приказано одговарајуће упозорење." +"Искључивање горње функције **не** деактивира аутоматско додавање налога! То " +"значи: ако корисник нпр. пошаље имејл поруку Zammad-у и још увек нема налог, " +"Zammad ће аутоматски додати нови налог." -#: ../settings/ticket.rst:204 ../settings/ticket.rst:206 -msgid "A Sample Duplicate Ticket Warning" -msgstr "Пример упозорења о дупликату тикета" +#: ../settings/security/base.rst:29 +msgid "Lost Password" +msgstr "Изгубљена лозинка" -#: ../settings/ticket.rst:206 ../settings/ticket.rst:208 +#: ../settings/security/base.rst:33 msgid "" -"You can choose which ticket attributes will be matched by selecting them in " -"**Attributes to compare** field. Only if the ticket attribute value provided " -"by the user in the ticket create form is *equal* with the attribute in an " -"existing ticket, the warning will be shown." +"Activates the `lost password` function on the login page. If set to ``no`` " +"only administrators may change the user's password - users may update their " +"own password if they're still logged in and they have the required :doc:" +"`permission `." msgstr "" -"Можете да изаберете који атрибути тикета треба да се подударају тако што " -"ћете их изабрати у пољу **Атрибути за поређење**. Само ако је вредност " -"атрибута тикета које је корисник навео у обрасцу за отварање новог тикета " -"*једнака* са атрибутом постојећег тикета, упозорење ће бити приказано." +"Активира функцију `Изгубљена лозинка` на страници за пријаву. Ако је " +"подешено на ``не`` само администратори могу да промене корисничку лозинку - " +"корисници могу да промене сопствену лозинку ако су још увек пријављени и " +"имају потребну :doc:`дозволу `." -#: ../settings/ticket.rst:211 ../settings/ticket.rst:213 -msgid "**Warning title** and **Warning message** are configurable as well." -msgstr "**Наслов упозорења** и **Порука упозорења** се такође могу подесити." +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"Lost Password\" setting" +msgstr "Слика која приказује укључено подешавање „Изгубљена лозинка“" -#: ../settings/ticket.rst:213 ../settings/ticket.rst:215 +#: ../settings/security/base.rst:49 msgid "" -"You can limit the detection only to certain user roles. By default, only " -"agents will see the warning." +"With third party authentications - but especially LDAP - you may want to " +"disable this function. Zammad **will not** change third party login " +"passwords and instead set or change the local password!" msgstr "" -"Откривање можете ограничити само на одређене корисничке улоге. " -"Подразумевано, само оператери ће видети упозорење." +"Уз аутентификацију преко трећег лица – али посебно LDAP – можда ћете " +"пожелети да искључите ову функцију. Zammad **неће** променити лозинке за " +"пријављивање преко трећих лица и уместо тога ће поставити или променити " +"локалну лозинку!" + +#: ../settings/security/base.rst:56 +msgid "Password Login" +msgstr "Пријављивање путем лозинке" -#: ../settings/ticket.rst:216 ../settings/ticket.rst:218 +#: ../settings/security/base.rst:60 msgid "" -"If you don't want to show the matched tickets as part of the warning, you " -"can set **Show matching ticket(s) in the warning** setting to *no*." +"Activates the username & password login by default and if no third-party " +"login is activated. Disabling password login on the Zammad login page only " +"takes effect if you enable any :doc:`third-party`." msgstr "" -"Ако не желите да прикажете пронађене тикете као део упозорења, можете да " -"подесите **Прикажи сличне тикете као део упозорења** на *не*." +"Омогућује пријаву путем корисничког имена и лозинке уколико нема укључених " +"пријава преко трећег лица. Искључивање пријављивања путем лозинке на Zammad " +"страници за пријаву ступа на снагу само ако омогућите било коју пријаву " +"преко :doc:`трећег лица `." -#: ../settings/ticket.rst:219 ../settings/ticket.rst:221 -msgid "" -"By default, **Permission level for looking up ticket** is set to *User*, " -"which means user permissions will be honored during sarch. The user will " -"see the warning only if tickets they have access to are matched. " -"Alternatively, you can set this setting to *System*, in which case the " -"search will happen within *all* tickets in the system, regardless of user " -"permissions." +#: ../settings/security/base.rst:64 +msgid "See :doc:`third-party` for supported third-party logins." msgstr "" -"Подразумевано, **Ниво дозвола при претраживању тикета** је подешен на " -"*Корисник*, што значи да ће се корисничке дозволе поштовати током претраге. " -"Корисник ће видети упозорење само ако се подударају тикети којима има " -"приступ. Алтернативно, можете поставити ово подешавање на *Систем*, у ком " -"случају ће се претрага одвијати унутар *свих* тикета у систему, без обзира " -"на корисничке дозволе." +"Погледајте :doc:`овде ` за подржане опције пријаве преко трећих " +"лица." -#: ../settings/ticket.rst:225 ../settings/ticket.rst:227 -msgid "**🦺 Safety first!**" -msgstr "**🦺 Безбедност на првом месту!**" +#: ../settings/security/base.rst:0 +msgid "Figure showing de-activated \"Password Login\" setting" +msgstr "Слика која приказује искључено подешавање „Пријављивање путем лозинке“" -#: ../settings/ticket.rst:227 ../settings/ticket.rst:229 +#: ../settings/security/base.rst:77 msgid "" -"Even if the permission level is set to *System*, the user will not be shown " -"the tickets they don't have access to in the warning, even if they match." +"To help administrators to overcome \"login issues\", Zammad automatically " +"offers a password request for administrator users. This allows you to adjust " +"Third-Party applications even if the login does no longer work!" msgstr "" -"Чак и ако је ниво дозволе постављен на *Систем*, кориснику неће бити " -"приказани тикети којима нема приступ у упозорењу, чак и ако се подударају." +"Да би помогао администраторима да превазиђу „проблеме са пријављивањем“, " +"Zammad аутоматски нуди пријаву привременом лозинком администраторе. Ово вам " +"омогућава да подесите апликације трећег лица чак и ако пријава уопште не " +"функционише!" -#: ../settings/ticket.rst:231 ../settings/ticket.rst:233 -msgid "" -"However, just the confirmation about the existence of the tickets in the " -"system may be considered an unwanted information disclosure. Use this option " -"carefully!" -msgstr "" -"Међутим, сама потврда о постојању тикета у систему може се сматрати " -"нежељеном информацијом. Користите ову опцију пажљиво!" +#: ../settings/security/base.rst:84 +msgid "Session Timeout" +msgstr "Време истека сесије" -#: ../settings/ticket.rst:235 ../settings/ticket.rst:237 +#: ../settings/security/base.rst:86 msgid "" -"Finally, you can configure between matching within **All tickets** or **Open " -"tickets** only by setting **Match tickets in following states**. Depending " -"on the current ticket state, a ticket may or not be matched." +"All settings below by default are set to ``4 weeks``. Session Timeout " +"defines the life time of a users session. As soon as it's reached, Zammad " +"will automatically log off the session in question." msgstr "" -"Коначно, можете да подесите **Претражи тикете у следећим стањима** на **Сви " -"тикети** или **Отворени тикети**. У зависности од тренутног стања тикета, " -"тикет ће бити узет у обзир." - -#: ../system/core-workflows.rst:2 -msgid "Core Workflows" -msgstr "Радни токови" +"Сва подешавања испод су подразумевано подешена на ``4 недеље``. Временско " +"ограничење сесије дефинише време трајања сесије корисника. Чим се достигне, " +"Zammad ће аутоматски одјавити дотичну сесију." -#: ../system/core-workflows.rst:4 +#: ../settings/security/base.rst:91 msgid "" -"Core Workflows allow you to adjust object attributes in many ways. For " -"example:" +"Zammad takes the highest value set assigned for the user based on the " +"permissions." msgstr "" -"Радни токови вам омогућавају да подесите атрибуте објекта на различите " -"начине. На пример:" +"Zammad узима највишу вредност која је додељена кориснику на основу дозвола." -#: ../system/core-workflows.rst:7 -msgid "show / hide fields" -msgstr "прикажете / сакријете поља" +#: ../settings/security/base.rst:94 +msgid "``admin``" +msgstr "``admin``" -#: ../system/core-workflows.rst:8 -msgid "adjust mandatory setting" -msgstr "подесите обавезност поља" +#: ../settings/security/base.rst:96 +msgid "``ticket.customer``" +msgstr "``ticket.customer``" -#: ../system/core-workflows.rst:9 -msgid "manipulate available options" -msgstr "манипулишете доступним опцијама" +#: ../settings/security/base.rst:97 +msgid "``default`` (fallback if user doesn't have above permissions set)" +msgstr "``подразумевано`` (замена ако корисник нема постављене дозволе изнад)" -#: ../system/core-workflows.rst:11 +#: ../settings/security/base.rst:99 msgid "" -"With this, you can provide exactly the information your users really need!" +"All settings act independently from each other allowing you to disable the " +"timeouts for e.g. admins, but not agents." msgstr "" -"Са овим алаткама, спремни сте да обезбедите управо оне информације које су " -"заиста потребне!" +"Сва подешавања делују независно једно од другог омогућавајући вам да " +"искључите временска ограничења за нпр. администраторе, али не и оператере." -#: ../system/core-workflows.rst:15 +#: ../settings/security/base.rst:115 +#: ../system/integrations/checkmk/api-reference.rst:13 +msgid "Example" +msgstr "Пример" + +#: ../settings/security/base.rst:107 +msgid "Let's suppose you configured the following session timeouts" +msgstr "Претпоставимо да сте подесили следећа временска ограничења сесије" + +#: ../settings/security/base.rst:104 +msgid "default: 3 weeks" +msgstr "подразумевано: 3 недеље" + +#: ../settings/security/base.rst:105 +msgid "admin: 2 weeks" +msgstr "admin: 2 недеље" + +#: ../settings/security/base.rst:106 +msgid "ticket.agent: 4 weeks" +msgstr "ticket.agent: 4 недеље" + +#: ../settings/security/base.rst:107 +msgid "ticket.customer: 1 week" +msgstr "ticket.customer: 1 недеља" + +#: ../settings/security/base.rst:115 +msgid "This results in the following situations" +msgstr "Ово резултира следећим ситуацијама" + +#: ../settings/security/base.rst:110 +msgid "a user with ``admin`` permission will have a timeout of 2 weeks" +msgstr "корисник са дозволом ``admin`` имаће временско ограничење од 2 недеље" + +#: ../settings/security/base.rst:111 msgid "" -"If the pre-defined :doc:`/system/objects` are not enough, please add them " -"beforehand." +"a user with ``admin`` and ``ticket.agent`` permissions will have a timeout " +"of 2 weeks" msgstr "" -"Ако вам унапред дефинисани :doc:`објекти ` нису довољни, " -"додајте их унапред." +"корисник са дозволама ``admin`` и ``ticket.agent`` имаће временско " +"ограничење од 2 недеље" -#: ../system/core-workflows.rst:17 +#: ../settings/security/base.rst:113 msgid "" -"If you experience slow or unreliable field updates, please see :ref:`Core " -"Workflow Ajax Modus `" +"a user with ``ticket.customer`` permission will have a timeout of 1 week" msgstr "" -"Ако имате спора или непоуздана освежавања на терену, погледајте :ref:`Ajax " -"режим радног тока `." +"корисник са дозволом ``ticket.customer`` имаће временско ограничење од 1 " +"недеље" -#: ../system/core-workflows.rst:22 +#: ../settings/security/base.rst:115 msgid "" -"This is a very enhanced functionality and can cause unexpected UI behavior. " -"Please ensure to test your use cases after configuration to reduce surprises." +"a user with neither ``admin``, ``ticket.agent`` nor ``ticket.customer`` " +"permissions will have a timeout of 3 weeks" msgstr "" -"Ово је напредна функција и може изазвати неочекивано понашање корисничког " -"интерфејса. Обавезно тестирајте своје случајеве коришћења након подешавања " -"да бисте смањили изненађења." - -#: ../system/core-workflows.rst:None -msgid "Dialogue for adding a new workflow" -msgstr "Дијалог за додавање новог радног тока" - -#: ../system/core-workflows/condition-operators.rst:2 -msgid "Core Workflow Condition Operators" -msgstr "Оператори услова радних токова" +"корисник који нема дозволе ни за ``admin``, ``ticket.agent`` ни за ``ticket." +"customer`` имаће временско ограничење од 3 недеље" -#: ../system/core-workflows/condition-operators.rst:4 +#: ../settings/security/password.rst:4 msgid "" -"You might know that there is a separate section for explaining :doc:" -"`condition operators `. Head over there to " -"see a detailed explanation of many conditions and operators." +"This section allows you to define password requirements for the local user " +"accounts." msgstr "" -"Можда сте свесни да постоји посебан одељак који објашњава :doc:`операторе " -"услова `. Тамо можете пронаћи детаљна " -"објашњења за многе услове и операторе." +"Овај одељак вам омогућава да подесите понашање лозинке за локалне корисничке " +"налоге." -#: ../system/core-workflows/condition-operators.rst:8 +#: ../settings/security/password.rst:9 msgid "" -"Due to differences to other places in Zammad which are also using conditions " -"(e.g. triggers), you can find a dedicated description of operators for core " -"workflows below." +"Zammad does **not** allow you to change your LDAP password, instead, it will " +"set a password in its local database which might confuse your users. This " +"might be addressed in the future by `#1169 `_." msgstr "" -"Услед разлика са другим областима Zammad-а које такође користи услове (нпр. " -"окидачи), испод можете пронаћи објашњење посвећено операторима радних токова." +"Zammad вам **не** дозвољава да промените своју LDAP лозинку, већ ће " +"поставити лозинку у својој локалној бази података која би могла збунити ваше " +"кориснике. Овим ће се убудуће бавити `#1169 `_." -#: ../system/core-workflows/condition-operators.rst:12 +#: ../settings/security/password.rst:14 +msgid "**Exception for admins**" +msgstr "**Изузетак за администраторе**" + +#: ../settings/security/password.rst:16 msgid "" -"Be aware that the availability of the operators depends on the selected " -"attribute and its field type. Some of the operators may only be available " -"for system attributes (e.g. for \"tags\", \"active\")." +"Please note that below password policies *do not* affect administrators " +"setting passwords on user accounts. While this seems strange and not safe we " +"believe that an administrator knowing an user's password is insecure as well." msgstr "" -"Обратите пажњу да доступност оператора зависи од одабраних атрибута и типа " -"поља. Неки од оператора могу бити доступни само за системске атрибуте (нпр. " -"за „Ознаке”, „Активно”)." +"Имајте на уму да доле наведени захтеви за јачину лозинке *не* утичу на " +"администраторе који постављају лозинке на корисничким налозима. Иако ово " +"изгледа чудно и небезбедно, верујемо да је и администратор који зна лозинку " +"корисника такође небезбедан." -#: ../system/core-workflows/condition-operators.rst:20 -msgid "Operator" -msgstr "Оператор" +#: ../settings/security/password.rst:21 +msgid "The suggested workflow is either:" +msgstr "Предложени радни ток је или:" -#: ../system/core-workflows/condition-operators.rst:22 -msgid "after (absolute)" -msgstr "након (апсолутно)" +#: ../settings/security/password.rst:23 +msgid "" +"to use third party logins to not require local passwords at all **- or -**" +msgstr "" +"да користите пријаве преко трећег лица тако да уопште не захтевате локалне " +"лозинке **- или -**" -#: ../system/core-workflows/condition-operators.rst:23 -msgid "Matches if a date/time is after a specific point in time." -msgstr "Подудара се ако је датум/време након одређеног тренутка." +#: ../settings/security/password.rst:25 +msgid "to require your *user to reset the password* upon first login." +msgstr "" +"да захтевате од *корисника да поништи лозинку* приликом првог пријављивања." -#: ../system/core-workflows/condition-operators.rst:24 -msgid "after (relative)" -msgstr "након (релативно)" +#: ../settings/security/password.rst:27 +msgid "" +"This way administrators are not required to set a user's password at all!" +msgstr "" +"На овај начин администратори уопште нису обавезни да постављају корисничку " +"лозинку!" -#: ../system/core-workflows/condition-operators.rst:25 -msgid "Matches if a time span after a specified event has passed." -msgstr "Подудара се ако је временски оквир прошао након одређеног догађаја." +#: ../settings/security/password.rst:31 +msgid "Maximum Failed Logins" +msgstr "Максимални број неуспешних пријава" -#: ../system/core-workflows/condition-operators.rst:26 -msgid "before (absolute)" -msgstr "пре (апсолутно)" +#: ../settings/security/password.rst:33 +msgid "" +"You can choose a value between ``4`` and ``20``. This defines how often a " +"login to a user account may fail until Zammad will lock it. Your users can " +"always use the \"forgot password\" function to change their password and " +"unlock their account." +msgstr "" +"Можете да изаберете вредност између ``4`` и ``20``. Ово одређује колико " +"често пријављивање на кориснички налог може бити неуспешно док га Zammad не " +"закључа. Ваши корисници увек могу да користе функцију „изгубљена лозинка“ да " +"промене своју лозинку и откључају свој налог." -#: ../system/core-workflows/condition-operators.rst:27 -msgid "Matches if a date/time is before a specific point in time." -msgstr "Подудара се ако је време/датум пре одређеног тренутка." +#: ../settings/security/password.rst:38 +msgid "The default value is ``10``." +msgstr "Подразумевана вредност је ``10``." -#: ../system/core-workflows/condition-operators.rst:28 -msgid "before (relative)" -msgstr "пре (релативно)" +#: ../settings/security/password.rst:42 +msgid "Beside changing the user's password, you can also unlock accounts via" +msgstr "Поред промене корисничке лозинке, налоге можете откључати и преко" -#: ../system/core-workflows/condition-operators.rst:29 -msgid "Matches if a time span after a specified event has not passed." -msgstr "Подудара се ако временски оквир након одређеног догађаја није прошао." +#: ../settings/security/password.rst:44 +msgid ":ref:`user management list `" +msgstr ":ref:`листе за управљање корисницима `" -#: ../system/core-workflows/condition-operators.rst:30 -msgid "contains" -msgstr "садржи" +#: ../settings/security/password.rst:45 +msgid ":docs:`console `" +msgstr ":docs:`конзоле `" -#: ../system/core-workflows/condition-operators.rst:31 -msgid "Matches if a specified value is present." -msgstr "Подудара се ако одређена вредност постоји." +#: ../settings/security/password.rst:46 +msgid ":docs:`API `" +msgstr ":docs:`API-ја `" -#: ../system/core-workflows/condition-operators.rst:33 -msgid "Matches if all of the specified values are present." -msgstr "Подудара се ако све дате вредности постоје." +#: ../settings/security/password.rst:50 +msgid "Failed logins via LDAP no longer lock accounts." +msgstr "Неуспеле пријаве преко LDAP-а више не закључавају налоге." -#: ../system/core-workflows/condition-operators.rst:35 -msgid "Matches if none of the specified values are present." -msgstr "Подудара се ако ниједна од датих вредности не постоји." +#: ../settings/security/password.rst:53 +msgid "2 Lower Case And 2 Upper Case Characters" +msgstr "2 мала и 2 велика слова" -#: ../system/core-workflows/condition-operators.rst:36 -msgid "contains not" -msgstr "не садржи" +#: ../settings/security/password.rst:55 +msgid "" +"You can add complexity to passwords by enforcing at least 2 upper and lower " +"case characters." +msgstr "" +"Лозинкама можете додати сложеност тако што ћете применити најмање 2 велика и " +"мала слова." -#: ../system/core-workflows/condition-operators.rst:37 -msgid "Matches if a specified value is not present." -msgstr "Подудара се ако дата вредност не постоји." +#: ../settings/security/password.rst:58 ../settings/security/password.rst:83 +msgid "The default value is ``no``." +msgstr "Подразумевана вредност је ``не``." -#: ../system/core-workflows/condition-operators.rst:39 -msgid "Matches if one specified value is present." -msgstr "Подудара се ако једна дата вредност постоји." +#: ../settings/security/password.rst:62 +msgid "Minimum Length" +msgstr "Минимална дужина" -#: ../system/core-workflows/condition-operators.rst:41 -msgid "Matches if one specified value is not present." -msgstr "Подудара се ако једна дата вредност не постоји." +#: ../settings/security/password.rst:64 +msgid "" +"This defines the minimum password length required for users to provide (from " +"``4`` to ``20``)." +msgstr "" +"Ово одређује минималну дужину лозинке коју корисници морају дати (од ``4`` " +"до ``20``)." -#: ../system/core-workflows/condition-operators.rst:42 -msgid "does not match regex" -msgstr "не задовољава регуларни израз" +#: ../settings/security/password.rst:67 +msgid "The default value is ``6``." +msgstr "Подразумевана вредност је ``6``." -#: ../system/core-workflows/condition-operators.rst:43 -msgid "Matches if content doesn't fit to regex rule." -msgstr "Подудара се ако се садржај не поклапа са регуларним изразом." - -#: ../system/core-workflows/condition-operators.rst:44 -msgid "ends with" -msgstr "завршава се са" +#: ../settings/security/password.rst:71 +msgid "Digit Required" +msgstr "Неопходна цифра" -#: ../system/core-workflows/condition-operators.rst:45 -msgid "Matches if content ends with specified value." -msgstr "Подудара се ако се садржај завршава са датом вредности." +#: ../settings/security/password.rst:73 +msgid "This enforces your users to use at least one digit within the password." +msgstr "" +"Ово приморава ваше кориснике да користе најмање једну цифру унутар лозинке." -#: ../system/core-workflows/condition-operators.rst:46 -msgid "ends with one of" -msgstr "завршава се са једним од" +#: ../settings/security/password.rst:75 +msgid "The default value is ``yes``." +msgstr "Подразумевана вредност је ``да``." -#: ../system/core-workflows/condition-operators.rst:47 -msgid "Matches if content ends with one of the specified values." -msgstr "Подудара се ако се садржај завршава са једном од датих вредности." +#: ../settings/security/password.rst:78 +msgid "Special Character Required" +msgstr "Неопходан специјални знак" -#: ../system/core-workflows/condition-operators.rst:48 -msgid "from (relative)" -msgstr "од (релативно)" +#: ../settings/security/password.rst:80 +msgid "" +"This setting allows you to improve your password quality even more by " +"enforcing the password to contain at least one special character." +msgstr "" +"Ово подешавање вам омогућава да још више побољшате квалитет својих лозинки " +"тако што ћете захтевати да лозинка садржи најмање један посебан знак." -#: ../system/core-workflows/condition-operators.rst:49 -msgid "Matches if date/time is after a period of time after an event." -msgstr "Подудара се ако је датум/време након датог периода после догађаја." +#: ../settings/security/ssl-certificates.rst:2 +msgid "SSL Certificates" +msgstr "SSL сертификати" -#: ../system/core-workflows/condition-operators.rst:51 -msgid "Matches if content is equal to a specified value." -msgstr "Подудара се ако је садржај једнак датој вредности." +#: ../settings/security/ssl-certificates.rst:7 +msgid "" +"Zammad offers the possibility to upload custom certificates and custom " +"Certificate Authority (CA) certificates. This can be useful if you want to " +"connect Zammad the secure way to other systems which are using custom " +"certificates." +msgstr "" +"Zammad вам омогућава да отпремите прилагођене сертификате и сертификате " +"органа за сертификацију (CA). Ово може бити корисно ако желите да повежете " +"Zammad на безбедан начин са другим системима који користе прилагођене " +"сертификате." -#: ../system/core-workflows/condition-operators.rst:52 -msgid "is any of" -msgstr "је један од" +#: ../settings/security/ssl-certificates.rst:12 +msgid "" +"An example usecase might be: You have an internal LDAP server that is not " +"accessible from the internet, and you want a SSL-encrypted connection, using " +"a custom certificate." +msgstr "" +"Пример употребе би могао бити: имате интерни LDAP сервер који није видљив на " +"интернту, и желите да се повежете путем шифроване SSL конекције, користећи " +"прилагођени сертификат." -#: ../system/core-workflows/condition-operators.rst:53 -msgid "Matches if content is equal to any of specified values." -msgstr "Подудара се ако је садржај једнак једној од датих вредности." +#: ../settings/security/ssl-certificates.rst:19 +msgid "" +"You should have an existing custom certificate file and/or a custom CA " +"certificate file, which you want to add to Zammad. As filetype ``.crt`` is " +"supported and the certificate format has to be PEM (Base64 ASCII)." +msgstr "" +"Требаже вам постојећи прилагођени сертификат и прилагођени CA сертификат " +"које желите да додате у Zammad. Подрђан формат датотеке је ``.crt`` и формат " +"сертификата мора бити PEM (Base64 ASCII)." -#: ../system/core-workflows/condition-operators.rst:54 -msgid "is modified" -msgstr "је измењено" +#: ../settings/security/ssl-certificates.rst:25 +msgid "" +"When you import a custom CA certificate, all certificates generated with " +"this are trusted. This can be useful if you have more than one system/" +"certificate you want to connect to and the certificates are issued from the " +"same custom CA." +msgstr "" +"Када увезете прилагођени CA сертификат, сви сертификати генерисани путем " +"њега биће признати. Ово може бити корисно ако имате више од једног система " +"које желите да повежете и сертификати су издати одстране истог прилагођеног " +"CA." -#: ../system/core-workflows/condition-operators.rst:55 -msgid "Matches if content is modified." -msgstr "Подудара се ако је садржај промењен." +#: ../settings/security/ssl-certificates.rst:31 +msgid "Add a Certificate" +msgstr "Додавање сертификата" -#: ../system/core-workflows/condition-operators.rst:57 -#: ../system/core-workflows/condition-operators.rst:61 -msgid "True from the moment of changing content until form submit." -msgstr "Тачно од тренутка промене садржаја до слања форме." +#: ../settings/security/ssl-certificates.rst:33 +msgid "" +"To add a custom certificate or a custom CA certificate, head over to the " +"Admin panel > Settings > Security > SSL Certificates. Here you can find a " +"\"Add SSL Certificate\" button. In the dialog you can either select a " +"certificate file or paste the content of the certificate:" +msgstr "" +"За додавање прилагођеног сертификата или прилагођеног CA сертификата, " +"упутите се на панел Администрација > Подешавања > Безбедност > SSL " +"сертификати. Тамо можете пронађи дугме „Додај SSL сертификат”. У дијалогу " +"можете одабрати или да отпремите датотеку сертификата или да налепите " +"садржај сертификата:" -#: ../system/core-workflows/condition-operators.rst:58 -msgid "is modified to" -msgstr "је промењено на" +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate adding dialog" +msgstr "Снимак екрана који приказује дијалог за додавање сертификата" -#: ../system/core-workflows/condition-operators.rst:59 -msgid "Matches if content is modified to a specific value." -msgstr "Подудара се ако је садржај промењен на дату вредност." +#: ../settings/security/ssl-certificates.rst:43 +msgid "" +"After selecting a file or pasting the content of the certificate, click on " +"the \"Add\" button to finally upload it to Zammad. Then, the certificates " +"are immediately effective, no restart or similar required." +msgstr "" +"По одабиру датотеке или налепљивању садржаја сертификата, кликните на дугме " +"„Додај” да бисте га отпремили у Zammad. Након тога, сертификати се одмах " +"користе, није неопходно рестартовање или слично." -#: ../system/core-workflows/condition-operators.rst:62 -msgid "is none of" -msgstr "није ниједан од" +#: ../settings/security/ssl-certificates.rst:49 +msgid "" +"Please note that only single certificate files are supported. That means if " +"you want to import a certificate / CA certificate, it must contain **only " +"one** certificate." +msgstr "" +"Обратите пажњу да су подржане само датотеке са појединачним сертификатима. " +"Ово значи да ако желите да увезете сертификат / CA сертификат путем " +"датотеке, мора садржати *само један** сертификат." -#: ../system/core-workflows/condition-operators.rst:63 -msgid "Matches if content is none of any specified values." -msgstr "Подудара се ако садржај није једнак ниједног од датих вредности." +#: ../settings/security/ssl-certificates.rst:54 +msgid "Certificate Overview" +msgstr "Преглед сертификата" -#: ../system/core-workflows/condition-operators.rst:65 -msgid "Matches if content is not equal to a specified value." -msgstr "Подудара се ако садржај није једнак датој вредности." +#: ../settings/security/ssl-certificates.rst:56 +msgid "" +"After you added a certificate, you can see a table with information for each " +"added certificate:" +msgstr "" +"По додавању сертификата, можете видети табелу са информацијама за сваки " +"додати сертификат:" -#: ../system/core-workflows/condition-operators.rst:67 -msgid "Matches if content is present." -msgstr "Подудара се ако садржај постоји." +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing table of added certificates" +msgstr "Снимак екрана који приказује табелу додатих сертификата" -#: ../system/core-workflows/condition-operators.rst:68 -msgid "just changed" -msgstr "управо измењено" +#: ../settings/security/ssl-certificates.rst:64 +msgid "" +"Here you can download the certificate or delete it, if you don't need it " +"anymore." +msgstr "" +"Овде можете преузети и обрисати сертификате, ако вам више нису потребни." -#: ../system/core-workflows/condition-operators.rst:69 -msgid "Matches if content has changed." -msgstr "Подудара се ако је садржај измењен." +#: ../settings/security/ssl-certificates.rst:68 +msgid "Deleting Certificates" +msgstr "Брисање сертификата" -#: ../system/core-workflows/condition-operators.rst:71 -#: ../system/core-workflows/condition-operators.rst:75 +#: ../settings/security/ssl-certificates.rst:70 msgid "" -"Only true for the moment of changing content until next form field action/" -"click." +"If you want to delete a specific certificate, you can do it by clicking on " +"the menu in the actions column and selecting delete:" msgstr "" -"Тачно само од тренутка измене садржаја до следеће акције/клика поља форме." - -#: ../system/core-workflows/condition-operators.rst:72 -msgid "just changed to" -msgstr "је управо измењено на" +"Ако желите да обришете сертификат, то можете учинити кликом на мени у колони " +"радњи и избором брисања:" -#: ../system/core-workflows/condition-operators.rst:73 -msgid "Matches if content has changed to a specified value." -msgstr "Подудара се ако је садржај измењен на дату вредност." +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate deletion button" +msgstr "СНимак екрана који приказује дугме за брисање сертификата" -#: ../system/core-workflows/condition-operators.rst:76 -msgid "matches regex" -msgstr "задовољава регуларни израз" +#: ../settings/security/ssl-certificates.rst:79 +msgid "Downloading Certificates" +msgstr "Преузимање сертификата" -#: ../system/core-workflows/condition-operators.rst:77 -msgid "Matches if value fits to regex rule." -msgstr "Подудара се ако се садржај поклапа са регуларним изразом." +#: ../settings/security/ssl-certificates.rst:81 +msgid "" +"If you want to download your certificates, you can do this as well via " +"corresponding action buttons." +msgstr "" +"Ако желите да преузмете ваше сертификате, то можете урадити путем " +"одговарајућих дугмића радњи." -#: ../system/core-workflows/condition-operators.rst:79 -msgid "Matches if no content is present." -msgstr "Подудара се ако садржај не постоји." +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate download button" +msgstr "Снимак екрана који приказује дугме за преузимање сертификата" -#: ../system/core-workflows/condition-operators.rst:80 -msgid "starts with" -msgstr "почиње са" +#: ../settings/security/third-party.rst:13 +msgid "Login Providers" +msgstr "Провајдери за пријављивање" -#: ../system/core-workflows/condition-operators.rst:81 -msgid "Matches if content starts with specified value." -msgstr "Подудара се ако садржај почиње са датом вредности." +#: ../settings/security/third-party.rst:2 +msgid "Third-Party Applications" +msgstr "Апликације трећег лица" -#: ../system/core-workflows/condition-operators.rst:82 -msgid "starts with one of" -msgstr "почиње са једним од" +#: ../settings/security/third-party.rst:4 +msgid "" +"Third party authentication is a great way to help your users to login to " +"Zammad more easily. If the account is yet unknown, Zammad will create a new " +"user automatically, without the user needed to interact (e.g. type in his " +"name). Another big advantage of this feature is that your user doesn't need " +"to remember another password." +msgstr "" +"Провера аутентичности преко трећег лица је одличан начин да помогнете својим " +"корисницима да се лакше пријаве на Zammad. Ако налог још увек није познат, " +"Zammad ће аутоматски додати новог корисника, без потребе за интеракцијом " +"корисника (нпр. укуцавањем њиховог имена). Још једна велика предност ове " +"функције је да ваш корисник не мора да памти додатну лозинку." -#: ../system/core-workflows/condition-operators.rst:83 -msgid "Matches if content starts with one of the specified values." -msgstr "Подудара се ако садржај почиње са једном од датих вредности." - -#: ../system/core-workflows/condition-operators.rst:84 -msgid "till (relative)" -msgstr "до (релативно)" - -#: ../system/core-workflows/condition-operators.rst:85 -msgid "Matches if date/time is before a period of time before an event." -msgstr "Подудара се ако је датум/време пре датог периода пре догађаја." - -#: ../system/core-workflows/condition-operators.rst:86 -msgid "today" -msgstr "данас" +#: ../settings/security/third-party.rst:10 +msgid "" +"You can deactivate logging in via :ref:`security_password_login` if any of " +"the mentioned authentication providers are enabled in your instance." +msgstr "" +"Можете искључити :ref:`пријављивање путем лозинке ` " +"ако је било који од наведених провајдера аутентификације омогућен у вашој " +"инстанци." -#: ../system/core-workflows/condition-operators.rst:87 -msgid "Matches if date/time is today." -msgstr "Подудара се ако је датум/време у току данашњег дана." +#: ../settings/security/third-party.rst:27 +msgid "" +"We're currently missing documentation for the following login providers:" +msgstr "" +"Тренутно нам недостаје документација за следеће провајдере за пријављивање:" -#: ../system/core-workflows/condition-operators.rst:88 -msgid "within last (relative)" -msgstr "у последњих (релативно)" +#: ../settings/security/third-party.rst:29 +msgid "LinkedIn" +msgstr "LinkedIn" -#: ../system/core-workflows/condition-operators.rst:89 -msgid "" -"Matches if date/time content is within specified period of time before now." -msgstr "Подудара се ако је датум/време унутар датог периода у прошлости." +#: ../settings/security/third-party.rst:30 +msgid "Weibo" +msgstr "Weibo" -#: ../system/core-workflows/condition-operators.rst:91 -msgid "within next (relative)" -msgstr "у следећих (релативно)" +#: ../settings/security/third-party.rst:35 +msgid "Automatic Account Link on Initial Logon" +msgstr "Аутоматско повезивање налога приликом иницијалне пријаве" -#: ../system/core-workflows/condition-operators.rst:92 +#: ../settings/security/third-party.rst:37 msgid "" -"Matches if date/time content is within specified period of time after now." -msgstr "Подудара се ако је датум/време унутар датог периода у будућности." - -#: ../system/core-workflows/how-do-they-work.rst:2 -msgid "How do they work?" -msgstr "Како то уствари функционише?" +"In general there's two possible options for Zammad on how to deal with " +"already known users as they try to authenticate against a third-party " +"application. By default, Zammad will not automatically link \"unknown\" " +"authentication providers to existing accounts." +msgstr "" +"Уопштено говорећи, постоје две могуће опције за Zammad о томе како да се " +"носи са већ познатим корисницима док покушавају да се пријаве преко " +"апликације трећег лица. Подразумевано, Zammad неће аутоматски повезати " +"„непознате“ провајдере за пријављивање са постојећим налозима." -#: ../system/core-workflows/how-do-they-work.rst:4 +#: ../settings/security/third-party.rst:42 msgid "" -"Core Workflows are executed according to their priority. If two workflows " -"have the same priority, they are executed in alphabetical order based on " -"their **name**." +"This means that the user has to manually link authentication providers to " +"their accounts (for more about this :user-docs:`consult the user " +"documentation `)." msgstr "" -"Радни токови се процењују по приоритету. Ако два радна тока имају исти " -"приоритет, онда се процењују по абецедном реду према свом **називу**." +"То значи да корисник мора ручно да повеже провајдере за пријављивање са " +"својим налогом (за више о овоме :user-docs:`погледајте корисничку " +"документацију `)." -#: ../system/core-workflows/how-do-they-work.rst:8 +#: ../settings/security/third-party.rst:46 msgid "" -"Because of the way Core Workflows work, all changes to attributes are " -"checked with the application server - please see :doc:`limitations` for " -"possible issues." +"Sometimes this doesn't come in handy as this also means you'll receive error " +"messages about \"email address being in use already\" for (yet) unknown " +"third-party authentication methods." msgstr "" -"Због начина на који радни токови функционишу, све измене атрибута се " -"проверавају на серверу апликације – погледајте :doc:`ограничења " -"` за могуће проблеме." +"Понекад ово није згодно јер то такође значи да ћете добијати поруке о грешци " +"да се „имејл адреса већ користи“ за (још) непознате методе аутентификације " +"преко трећег лица." -#: ../system/core-workflows/how-do-they-work.rst:12 +#: ../settings/security/third-party.rst:50 msgid "" -"Below we're talking about settings that are important and not self-" -"explanatory." +"If you want to allow your users to always be able to log in, no matter what, " +"you may want to enable ``Automatic account link on initial logon``." msgstr "" -"У наставку говоримо о подешавањима која имају утицај и нису сама по себи " -"разумљива." +"Ако желите да омогућите својим корисницима да увек могу да се пријаве, без " +"обзира на све, можда ћете желети да укључите ``Аутоматско повезивање налога " +"приликом иницијалне пријаве``." -#: ../system/core-workflows/how-do-they-work.rst:17 +#: ../settings/security/third-party.rst:None msgid "" -"Choose the object context you want to run the workflow in. This will decide " -"on your available attributes and actions." +"Screenshot highlighting the \"Automatic account link on initial logon\"\n" +"setting" msgstr "" -"Изаберите контекст објекта у којем желите да покренете радни ток. Ово ће " -"утицати на доступне атрибуте и радње." +"Снимак екрана који истиче подешавање „Аутоматско повезивање\n" +"налога приликом иницијалне пријаве“" -#: ../system/core-workflows/how-do-they-work.rst:20 -msgid "Ticket objects also have access to the ticket customer." -msgstr "Објекти тикета такође имају приступ клијенту тикета." +#: ../settings/security/third-party.rst:60 +msgid "Automatic Account Linking Notification" +msgstr "Обавештавање о аутоматском повезивању налога" -#: ../system/core-workflows/how-do-they-work.rst:25 +#: ../settings/security/third-party.rst:64 msgid "" -"Choose in which situation the workflow is applied. Contexts can be combined " -"to avoid duplicate workflows." +"To improve security and your users awareness, you can enable Zammad to " +"notify your users when a new third-party application has been linked to " +"their account." msgstr "" -"Изаберите у којој ситуацији се примењује радни ток. Контексти се могу " -"комбиновати да би се смањио број токова." - -#: ../system/core-workflows/how-do-they-work.rst:30 -msgid "Creation mask" -msgstr "Форма за отварање" +"Да бисте побољшали безбедност и свест корисника, можете омогућити Zammad-у " +"да обавести ваше кориснике када је нова апликација трећег лица повезана са " +"њиховим налогом." -#: ../system/core-workflows/how-do-they-work.rst:29 +#: ../settings/security/third-party.rst:68 msgid "" -"If selected, your conditions and actions will affect all applicable creation " -"masks." +"This notification is sent out once per third-party application. Zammad does " +"also mention the method used, e.g.: ``Microsoft``." msgstr "" -"По избору, ваши услови и радње ће утицати на све доступне форме додавања." +"Ово обавештење се шаље једном по апликацији трећег лица. Zammad такође " +"помиње коришћени метод, на пример: ``Microsoft``." -#: ../system/core-workflows/how-do-they-work.rst:34 -msgid "Edit mask" -msgstr "Форма за измену" +#: ../settings/security/third-party.rst:71 +msgid "By default this setting is not active (set to ``no``)." +msgstr "Подразумевано ово подешавање није укључено (подешено је на ``не``)." -#: ../system/core-workflows/how-do-they-work.rst:33 +#: ../settings/security/third-party.rst:0 msgid "" -"If selected, your conditions and actions will affect all applicable edit " -"masks." +"Screenshot showing sample notification mail after initial\n" +"third-party linking" msgstr "" -"По избору, ваши услови и радње ће утицати на све доступне форме за уређивање." +"Снимак екрана који приказује пример имејл обавештења након иницијалног\n" +"повезивање преко трећег лица" -#: ../system/core-workflows/how-do-they-work.rst:39 +#: ../settings/security/third-party.rst:85 msgid "" -"Zammad differentiates between selected and saved conditions. These can be " -"combined wherever needed." +"This notification is only sent if the account in question already exists. If " +"the login via the third-party also creates the missing account, the " +"notification will be skipped." msgstr "" -"Zammad прави разлику између одабраних и сачуваних услова. Они се могу " -"комбиновати где год је то потребно." +"Ово обавештење се шаље само ако дотични налог већ постоји. Ако пријављивање " +"преко трећег лица такође додаје нови налог, обавештење ће бити прескочено." -#: ../system/core-workflows/how-do-they-work.rst:42 -msgid "**⚠️ Restrict workflows to specific roles if needed!**" -msgstr "**⚠️ Ограничите токове на одговарајуће улоге ако је потребно!**" +#: ../settings/security/third-party.rst:89 +msgid "This means it only affects:" +msgstr "То значи да утиче само на:" -#: ../system/core-workflows/how-do-they-work.rst:44 -msgid "" -"By default and unless configured in conditions, workflow rules are executed " -"for **all roles**. This also affects your customers!" +#: ../settings/security/third-party.rst:91 +msgid "manual account linking within the third-party page of the users profile" msgstr "" -"Подразумевано, осим ако нису подешене у условима, правила радног тока се " -"процењују за **све улоге**. Ово такође утиче на ваше клијенте!" +"ручно повезивање налога у оквиру странице трећег лица корисничког профила" -#: ../system/core-workflows/how-do-they-work.rst:50 -msgid "Selected Conditions" -msgstr "Одабрани услови" +#: ../settings/security/third-party.rst:92 +msgid "" +"logging into an existing local account by utilizing the *automatic account " +"link on initial logon* functionality" +msgstr "" +"пријављивање на постојећи локални налог коришћењем функције *Аутоматско " +"повезивање налога приликом иницијалне пријаве*" -#: ../system/core-workflows/how-do-they-work.rst:48 +#: ../settings/security/third-party.rst:None msgid "" -"These conditions are based on form values and match if an appropriate " -"selection is made (e.g. choosing another group in the ticket without " -"saving). This applies for drafts (active selection) and currently saved " -"values." +"Screenshot showing the \"automatic account linking notification\"\n" +"setting" msgstr "" -"Ови услови су базирани на вредностима форме и поклапају се ако је направљен " -"одговарајући избор (нпр. избор друге групе у тикету без снимања). Ово важи " -"за нацрте (активан избор) и тренутно сачуване вредности." +"Снимак екрана који приказује подешавање „Обавештавање о\n" +"аутоматском повезивању налога“" -#: ../system/core-workflows/how-do-they-work.rst:64 -msgid "Saved Conditions" -msgstr "Сачувани услови" +#: ../settings/security/third-party.rst:100 +msgid "No User Creation on Logon" +msgstr "Без отварања налога по пријави" -#: ../system/core-workflows/how-do-they-work.rst:53 +#: ../settings/security/third-party.rst:102 msgid "" -"These conditions only match if the selected values are stored in the " -"database. It ignores the current value or selection of the field, as long as " -"the changes are not saved (e.g. performing field operations for an existing " -"ticket, which is viewed/opened by an agent)." +"By default, Zammad will create a new user account if the user logs in via a " +"third-party application and the account doesn't exist yet." msgstr "" -"Ови услови се поклапају само ако изабране вредности сачуване у бази " -"података. Игноришу тренутну вредност или избор поља, све док измене нису " -"снимљене (нпр. управљањем пољима постојећег тикета, који је у прегледу " -"оператера)." +"Подразумевано, Zammad ће отворити нови кориснички налог ако се корисник " +"пријављује преко апликације трећег лица и налог још увек не постоји." -#: ../system/core-workflows/how-do-they-work.rst:60 +#: ../settings/security/third-party.rst:105 msgid "" -"Keep in mind that the value has to be available in the situation where you " -"need it. Otherwise the condition won't match." +"If you want to prevent Zammad from creating new accounts on logon, you can " +"disable this feature by setting ``No user creation on logon`` to ``yes``." msgstr "" -"Имајте на уму да вредност мора бити доступна у ситуацији у којој вам је " -"потребна. У супротном, услов се неће подударати." +"Уколико желите да спречите Zammad да отвара нове налоге по пријави, можете " +"искључити ову функцију постављањем ``Без отварања налога по пријави``на " +"``да``." -#: ../system/core-workflows/how-do-they-work.rst:63 -msgid "" -"Example: you can't perform any actions with *saved condition* on a ticket in " -"creation, because there are no saved values at that time." +#: ../settings/security/third-party.rst:None +msgid "Screenshot showing the \"no user creation on logon\" setting" msgstr "" -"Пример: не можете извршити акције са *сачуваним условима* при отварању " -"тикета, јер нема снимљених вредности у том тренутку." +"Снимак екрана који приказује подешавање „Без отварања налога по пријави”" -#: ../system/core-workflows/how-do-they-work.rst:66 +#: ../settings/security/third-party/facebook.rst:4 msgid "" -"You can find a description of the condition operators for core workflows :" -"doc:`here `." +"It is possible to create a quick login for your helpdesk via Facebook To do " +"so, you need to follow these steps:" msgstr "" -"Опис оператора услова за радне токове можете пронаћи :doc:`овде `." - -#: ../system/core-workflows/how-do-they-work.rst:72 -msgid "" -"Which actions should we run on the relevant fields? The possible actions " -"depend on the object type. However, usually you can at least change the " -"visibility and whether the field is mandatory." -msgstr "" -"Које радње треба да спроводимо на релевантним пољима? Могуће радње зависе од " -"типа објекта, међутим, обично можете барем променити видљивост или то да ли " -"је поље обавезно." - -#: ../system/core-workflows/how-do-they-work.rst:76 -msgid "Be aware that actions are not available for **related** context." -msgstr "Обратите пажњу да радње нису доступне за **повезане** објекте." +"Могуће је подесити брзо пријављивање у Zammad преко Facebook-а. Да бисте то " +"урадили, потребно је да пратите следеће кораке:" -#: ../system/core-workflows/how-do-they-work.rst:78 -msgid "" -"**Example:** Let's assume you are working in the ticket context. While you " -"can have customer *conditions*, you *can't adjust* objects with actions in " -"that scope. That's because this wouldn't have any impact on the ticket " -"dialog. Of course all ticket attributes (state, owner, ...) are available." -msgstr "" -"**Пример:** Рецимо да радите у контексту тикета. Иако можете имати " -"корисничке услове, не можете да прилагођавате објекте са радњама у том " -"обиму. Ово је из разлога што неће имати било каквог утицаја на дијалог " -"тикета. Наравно, сви атрибути тикета (стање, власник, ...) биће доступни." +#: ../settings/security/third-party/facebook.rst:9 +msgid "Register Facebook App" +msgstr "Региструјте Facebook апликацију" -#: ../system/core-workflows/how-do-they-work.rst:84 +#: ../settings/security/third-party/facebook.rst:11 msgid "" -"Please also have a look at our :doc:`limitations` to be safe from surprises." +"Visit [https://developers.facebook.com/apps/] and click on \"Add a new App\"" msgstr "" -"Погледајте и наша :doc:`ограничења ` да не би било непријатних " -"изненађења." - -#: ../system/core-workflows/how-do-they-work.rst:88 -msgid "Available Operators" -msgstr "Доступни оператори" - -#: ../system/core-workflows/how-do-they-work.rst:90 -msgid "The availability of operators depends on the object type and scope." -msgstr "Доступност оператора зависи од типа објекта и обима." +"Посетите [https://developers.facebook.com/apps/] и кликните на „Add a new " +"App“" -#: ../system/core-workflows/how-do-they-work.rst:94 -msgid "" -"Please note that actions may or may not restrict API based access to " -"attributes. We're displaying the following icons for your overview to " -"understand these limits better:" -msgstr "" -"Имајте на уму да радње могу али и не морају ограничити приступ атрибутима " -"преко API-ја. За бољи преглед, приказујемо следеће иконице да бисте боље " -"разумели ова ограничења:" +#: ../settings/security/third-party/facebook.rst:None +msgid "initial page" +msgstr "почетна страница" -#: ../system/core-workflows/how-do-they-work.rst:0 -msgid "|api| This icon indicates the action affects the API." -msgstr "|api| Ова иконица означава да радња утиче на API." +#: ../settings/security/third-party/facebook.rst:17 +msgid "After that enter the app settings" +msgstr "Након тога унесите подешавања апликације" -#: ../system/core-workflows/how-do-they-work.rst:163 -msgid "api" -msgstr "api" +#: ../settings/security/third-party/facebook.rst:None +msgid "Create App" +msgstr "Create App" -#: ../system/core-workflows/how-do-they-work.rst:0 -msgid "|ui| This icon indicates the action only affects the web interface." -msgstr "|ui| Ова иконица означава да радња утиче само на кориснички интерфејс." +#: ../settings/security/third-party/facebook.rst:22 +msgid "Navigate to \"Settings\" and fill in this infromation" +msgstr "Идите на „Settings“ и попуните ове информације" -#: ../system/core-workflows/how-do-they-work.rst:167 -msgid "ui" -msgstr "ui" +#: ../settings/security/third-party/facebook.rst:None +msgid "App Settings" +msgstr "App Settings" -#: ../system/core-workflows/how-do-they-work.rst:102 -msgid "show |ui|" -msgstr "прикажи |ui|" +#: ../settings/security/third-party/facebook.rst:27 +msgid "Navigate to app review and Check \"Make [appname] public?\"" +msgstr "" +"Идите на рецензију апликације и означите „Make [назив апликације] public?“" -#: ../system/core-workflows/how-do-they-work.rst:102 -msgid "Display the chosen field. Allows setting of values." -msgstr "Прикажи дотично поље. Омогућава подешавање вредности." +#: ../settings/security/third-party/facebook.rst:None +msgid "App Review" +msgstr "App Review" -#: ../system/core-workflows/how-do-they-work.rst:109 -msgid "hide |ui|" -msgstr "сакриј |ui|" +#: ../settings/security/third-party/facebook.rst:35 +msgid "Configure Zammad as Facebook App" +msgstr "Подесите Zammad као Facebook апликацију" -#: ../system/core-workflows/how-do-they-work.rst:105 +#: ../settings/security/third-party/facebook.rst:37 msgid "" -"Hide the chosen field. However, it technically still allows setting the " -"field." +"Navigate to \"Admin -> Security -> Third Party Applications\" and enter the " +"App ID and the App Secret. You can find this Key in the Dashbard of your " +"Facebok app." msgstr "" -"Сакриј дотично поље. Међутим, технички и даље дозвољава подешавање вредности " -"поља." +"Идите на „Администрација -> Безбедност -> Апликације трећег лица“ и унесите " +"ID апликације и шифру апликације. Овај кључ можете пронаћи у контролној " +"табли ваше Facebook апликације." -#: ../system/core-workflows/how-do-they-work.rst:108 +#: ../settings/security/third-party/facebook.rst:None +msgid "Zammad Configuration" +msgstr "Zammad подешавања" + +#: ../settings/security/third-party/facebook.rst:44 +#: ../settings/security/third-party/github.rst:43 +#: ../settings/security/third-party/gitlab.rst:46 msgid "" -"Please note that the field is **not** gone and still contains an existing " -"value (if set)! Consider *remove* instead, if you want this field to be gone." +"Now you can link accounts via \"Avatar -> Profile -> Link Accounts\" or " +"login via Zammad login page." msgstr "" -"Имајте на уму да поље **неће** нестати и још увек садржи вредност коју " -"пружа! Можда бисте желели да размислите о oператору *уклони* уместо њега." - -#: ../system/core-workflows/how-do-they-work.rst:112 -msgid "remove |ui|" -msgstr "уклони |ui|" - -#: ../system/core-workflows/how-do-they-work.rst:112 -msgid "Entirely removes the field. The field value will not be evaluated." -msgstr "Потпуно уклања поље. Вредност поља неће бити пружена." +"Сада можете повезати налоге преко „Аватар -> Профил -> Повезани налози” или " +"се пријавити преко Zammad странице за пријаву." -#: ../system/core-workflows/how-do-they-work.rst:115 -msgid "set mandatory |ui| |api|" -msgstr "постави обавезно |ui| |api|" +#: ../settings/security/third-party/github.rst:2 +#: ../system/integrations/github.rst:2 +msgid "GitHub" +msgstr "GitHub" -#: ../system/core-workflows/how-do-they-work.rst:115 -msgid "Sets the field to mandatory." -msgstr "Поставља поље на обавезно." +#: ../settings/security/third-party/github.rst:4 +msgid "" +"It is possible to create a quick login for your helpdesk via GitHub. To " +"activate the quick login you need to enable OAuth for GitHub." +msgstr "" +"Могуће је подесити брзо пријављивање у Zammad преко GitHub-а. Да бисте то " +"урадили, потребно је да омогућите OAuth за GitHub." -#: ../system/core-workflows/how-do-they-work.rst:118 -msgid "set optional |ui| |api|" -msgstr "постави необавезно |ui| |api|" +#: ../settings/security/third-party/github.rst:8 +msgid "Register GitHub App" +msgstr "Регистрација GitHub апликације" -#: ../system/core-workflows/how-do-they-work.rst:118 -msgid "Sets the field to optional." -msgstr "Поставља поље на опционо." +#: ../settings/security/third-party/github.rst:10 +msgid "" +"Visit https://www.github.com/settings/applications/new and enter the app " +"settings. As callback URL enter \"https://zammad_host/auth/github/callback\" " +"where zammad_host has to be replaced with your Zammad FQDN" +msgstr "" +"Посетите https://www.github.com/settings/applications/new и унесите " +"подешавања апликације. Као URL адресу повратног позива унесите „https://" +"zammad_host/auth/github/callback“ где zammad_host треба да буде замењено " +"вашом Zammad FQDN адресом." -#: ../system/core-workflows/how-do-they-work.rst:124 -msgid "add option |ui| |api|" -msgstr "додај опцију |ui| |api|" +#: ../settings/security/third-party/github.rst:None +msgid "Register OAuth app on www.github.com" +msgstr "Региструјте OAuth апликацију на www.github.com" -#: ../system/core-workflows/how-do-they-work.rst:121 -msgid "Allows adding options to tree selects or selects." -msgstr "Омогућава додавање опција у пољa за избор (стабла)." +#: ../settings/security/third-party/github.rst:19 +msgid "Configure Zammad as GitHub App" +msgstr "Подесите Zammad као GitHub апликацију" -#: ../system/core-workflows/how-do-they-work.rst:123 +#: ../settings/security/third-party/github.rst:21 msgid "" -"You have to use the \"remove option\" before performing this action. It " -"allows you to use *existing* configured values." +"Enter the \"APP ID\" and the \"APP SECRET\" from the GitHub OAUTH " +"Applications Dashboard" msgstr "" -"Ово захтева да се опције претходно сакрију (уклони опцију). Омогућава " -"коришћење *постојећих* вредности." +"Унесите „ID апликације“ и „Шифру апликације“ са контролне табле GitHub OAuth " +"апликација" -#: ../system/core-workflows/how-do-they-work.rst:128 -msgid "remove option |ui| |api|" -msgstr "уклони опцију |ui| |api|" +#: ../settings/security/third-party/github.rst:None +msgid "GitHub config in Zammad admin interface" +msgstr "GitHub конфигурација у администраторском интерфејсу Zammad-а" -#: ../system/core-workflows/how-do-they-work.rst:127 +#: ../settings/security/third-party/github.rst:28 msgid "" -"Allows removing options from tree selects or selects. It allows you to use " -"*existing* configured values." +"After you configured the GitHub credentials and activated the login method, " +"you should see a new icon on the login page." msgstr "" -"Омогућава уклањање опција из поља једноструког и вишеструког избора. " -"Омогућава коришћење *постојећих* вредности." - -#: ../system/core-workflows/how-do-they-work.rst:134 -msgid "set fixed to |ui| |api|" -msgstr "постави на вредност |ui| |api|" +"Након што сте подесили GitHub акредитиве и укључили метод пријављивања, " +"требало би да видите нову иконицу на страници за пријаву." -#: ../system/core-workflows/how-do-they-work.rst:131 -msgid "Reduces the available options by your selection." -msgstr "Ограничава доступне опције по вашем избору." +#: ../settings/security/third-party/github.rst:None +msgid "GitHub logo on login page" +msgstr "GitHub логотип на страници за пријаву" -#: ../system/core-workflows/how-do-they-work.rst:133 +#: ../settings/security/third-party/github.rst:34 msgid "" -"This reduces your workflows in terms of *add option* and *remove option*." +"If you click on the icon you will be redirected to GitHub and see something " +"similar to this:" msgstr "" -"Ово може смањити број ваших радних токова који користе *додај опцију* и " -"*уклони опцију*." +"Ако кликнете на иконицу, бићете преусмерени на GitHub и видећете нешто " +"слично следећем:" -#: ../system/core-workflows/how-do-they-work.rst:137 -msgid "fill in |ui|" -msgstr "попуни |ui|" +#: ../settings/security/third-party/github.rst:None +msgid "GitHub oauth page" +msgstr "GitHub OAuth страница" -#: ../system/core-workflows/how-do-they-work.rst:137 -msgid "Allows filling in of string and integer fields with your values." +#: ../settings/security/third-party/github.rst:40 +#: ../settings/security/third-party/gitlab.rst:42 +msgid "" +"When you grant the access you will be redirected to your Zammad instance and " +"logged in as a customer." msgstr "" -"Омогућава попуњавање поља текста и целобројних поља са вашим вредностима." +"Када одобрите приступ, бићете преусмерени на своју Zammad инстанцу и " +"пријављени као корисник." -#: ../system/core-workflows/how-do-they-work.rst:141 -msgid "fill in empty |ui|" -msgstr "попуни празно |ui|" +#: ../settings/security/third-party/gitlab.rst:2 +msgid "Gitlab" +msgstr "Gitlab" -#: ../system/core-workflows/how-do-they-work.rst:140 +#: ../settings/security/third-party/gitlab.rst:4 msgid "" -"Allows filling in of string and integer fields with your values **if the " -"field is empty**." +"It is possible to create a quick login for your helpdesk via Gitlab. To " +"activate the quick login you need to enable OAuth for Gitlab." msgstr "" -"Омогућава попуњавање поља текста и целобројних поља са вашим вредностима " -"**ако су поља празна**." +"Могуће је подесити брзо пријављивање у Zammad преко GitLab-а. Да бисте то " +"урадили, потребно је да омогућите OAuth за GitHub." -#: ../system/core-workflows/how-do-they-work.rst:144 -msgid "select |ui|" -msgstr "изабери |ui|" +#: ../settings/security/third-party/gitlab.rst:8 +msgid "Register Gitlab App" +msgstr "Регистрација Gitlab апликације" -#: ../system/core-workflows/how-do-they-work.rst:144 -msgid "Select a specific value within a select, tree select or boolean field." +#: ../settings/security/third-party/gitlab.rst:10 +msgid "To register an app in Gitlab open your profile and select applications." msgstr "" -"Изабери одређену вредност унутар поља за избор, избор стабла или логичког " -"поља." +"Да бисте регистровали апликацију у Gitlab-у, отворите свој профил и " +"изаберите апликације." -#: ../system/core-workflows/how-do-they-work.rst:153 -msgid "auto select |ui|" -msgstr "аутоматски избор |ui|" +#: ../settings/security/third-party/gitlab.rst:12 +msgid "" +"As callback URL enter \"https://zammad-fqdn/auth/gitlab/callback\" where " +"zammad-fqdn has to be replaced with your Zammad FQDN" +msgstr "" +"Као URL адресу повратног позива унесите „https://zammad-fqdn/auth/gitlab/" +"callback“ где zammad-fqdn мора бити замењено вашом Zammad FQDN адресом." -#: ../system/core-workflows/how-do-they-work.rst:147 -msgid "Helps users with tree select and select fields:" -msgstr "Помаже кориснику са пољима избора (стабла):" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Register OAuth app on gitlab instance" +msgstr "Региструјте OAuth апликацију на Gitlab инстанци" -#: ../system/core-workflows/how-do-they-work.rst:149 +#: ../settings/security/third-party/gitlab.rst:18 +msgid "Just select *read_user* under scopes as in the screenshot and save it." +msgstr "" +"Само изаберите *read_user* за опсег дозвола као на снимку екрана и сачувајте " +"је." + +#: ../settings/security/third-party/gitlab.rst:21 +msgid "Configure Zammad as Gitlab App" +msgstr "Подесите Zammad као Gitlab апликацију" + +#: ../settings/security/third-party/gitlab.rst:23 msgid "" -"If the field has only one option available for selection and no value yet, " -"the value will be automatically set." +"Enter the \"APP ID\" and the \"APP SECRET\" from the Gitlab OAUTH " +"Applications Dashboard and your Gitlab-URL in the \"SITE\" field." msgstr "" -"Ако поље има само једну опцију за избор и још увек нема вредност, вредност " -"се аутоматски поставља." +"Унесите „ID апликације“ и „Шифру апликације“ са контролне табле Gitlab OAuth " +"апликација и своју Gitlab URL адресу у поље „Путања“." -#: ../system/core-workflows/how-do-they-work.rst:152 +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab config in Zammad admin interface" +msgstr "Gitlab конфигурација у администраторском интерфејсу Zammad-а" + +#: ../settings/security/third-party/gitlab.rst:30 msgid "" -"This option only works if you have one value and doesn't work if there is " -"more than one option available." +"After you configured the Gitlab credentials and activated the login method, " +"you should see a new icon on the login page." msgstr "" -"Овај оператор функционише само ако имате једну вредност и не делује ако има " -"више од једне опције." +"Након што сте подесили Gitlab акредитиве и активирали метод пријављивања, " +"требало би да видите нову иконицу на страници за пријаву." -#: ../system/core-workflows/how-do-they-work.rst:157 -msgid "set readonly |ui|" -msgstr "укључи само за преглед |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab logo on login page" +msgstr "Gitlab логотип на страници за пријаву" -#: ../system/core-workflows/how-do-they-work.rst:156 +#: ../settings/security/third-party/gitlab.rst:36 msgid "" -"Allows you to display an attribute as read only (which means no changes are " -"possible)." +"If you click on the icon you will be redirected to Gitlab and see something " +"similar to this:" msgstr "" -"Омогућава вам да прикажете атрибут само за читање (readonly), што значи да " -"измене неће бити могуће." +"Ако кликнете на иконицу, бићете преусмерени на Gitlab и видећете нешто " +"слично следећем:" -#: ../system/core-workflows/how-do-they-work.rst:161 -msgid "unset readonly |ui|" -msgstr "искључи само за преглед |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab oauth page" +msgstr "Gitlab OAuth страница" -#: ../system/core-workflows/how-do-they-work.rst:160 +#: ../settings/security/third-party/google.rst:4 msgid "" -"In case a workflow set the field in question to read only, you can undo this " -"with option above." +"With some easy and fast steps, you can enable Zammad to authenticate your " +"users via Google." msgstr "" -"У случају да је радни ток поставио поље на само за преглед (readonly), ово " -"можете поништити уз помоћ горњег оператора." +"Уз неколико лаких и брзих корака, можете омогућити Zammad-у да аутентификује " +"ваше кориснике преко Google-а." -#: ../system/core-workflows/how-do-they-work.rst:172 -msgid "Stop after match" -msgstr "Заустави после поклапања" +#: ../settings/security/third-party/google.rst:8 +msgid "Register a Google App" +msgstr "Регистрација Google апликације" -#: ../system/core-workflows/how-do-they-work.rst:174 +#: ../settings/security/third-party/google.rst:10 msgid "" -"Here you can decide if other workflows are executed after the current one." +"First of all, we need to create a new project - you can skip this step if " +"you already have one." msgstr "" -"Овим можете зауставити процену накнадних радних токова после тренутног." +"Пре свега, морате да креирате нови пројекат - овај корак можете прескочити " +"ако га већ имате." -#: ../system/core-workflows/how-do-they-work.rst:176 +#: ../settings/security/third-party/google.rst:15 msgid "" -"If set to ``no`` (default), further workflows will be executed if they match " -"the condition. In this case, it is possible that your actions from the " -"current workflow can be overwritten by another workflow." +"Use this link to create a new project: https://console.cloud.google.com/" +"projectcreate" msgstr "" -"Ако је подешено на ``не`` (подразумевано), накнадни радни токови ће бити " -"процењени ако се поклапају услови. У овом случају, могуће да ће радње из " -"тренутног радног тока бити поништене неким другим током." +"Користите следећи линк да направите нови пројекат: https://console.cloud." +"google.com/projectcreate" -#: ../system/core-workflows/how-do-they-work.rst:180 +#: ../settings/security/third-party/google.rst:18 msgid "" -"If set to ``yes``, no further worflows will be executed after the current " -"one." +"Now expand the menu, expand \"APIs & Services\" and select \"Credentials\". " +"Go to the tab \"OAuth consent screen\" first and ensure to fill in the " +"requested information - without doing so you can't create credentials!" msgstr "" -"Ако је подешено на ``да``, накнадни радни токови неће бити процењени након " -"овога." +"Сада проширите мени, проширите „APIs & Services“ и изаберите „Credentials“. " +"Прво идите на језичак „OAuth consent screen“ и уверите се да сте попунили " +"тражене информације – без тога не можете да креирате акредитиве!" -#: ../system/core-workflows/how-do-they-work.rst:184 -msgid "Priority" -msgstr "Приоритет" +#: ../settings/security/third-party/google.rst:None +msgid "Creating a consent screen" +msgstr "Подешавање екрана за сагласност" -#: ../system/core-workflows/how-do-they-work.rst:186 +#: ../settings/security/third-party/google.rst:25 msgid "" -"You can define the sequence, in which the workflows are executed. The " -"default value is ``500``." +"After filling in and saving the consent screen information, you can go to " +"the \"Credentials\" tab and create new \"OAuth client ID\"-Credentials." msgstr "" -"Можете одредити редослед у којима ће радни токови бити процењени. " -"Подразумевана вредност је ``500``." +"Након што попуните и сачувате информације на екрану за сагласност, можете да " +"пређете на језичак „Credentials“ и креирате нови „OAuth client ID“ – тј. " +"акредитиве." -#: ../system/core-workflows/how-do-they-work.rst:189 +#: ../settings/security/third-party/google.rst:28 msgid "" -"The workflows are executed in ascending order by their priority. That means " -"lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." +"Fill in the necessary information as follows and replace ``zammad_host`` " +"with your FQDN:" msgstr "" -"Радни токови се процењују у узлазном редоследу према приоритету. Ово ѕначи " -"да се ниже вредности (нпр. ``100``) процењују пре виших (нпр. ``999``)." +"Попуните неопходне информације на следећи начин и замените ``zammad_host`` " +"својом FQDN адресом:" -#: ../system/core-workflows/learn-by-example.rst:2 -msgid "Learn by Example" -msgstr "Учите на примеру" +#: ../settings/security/third-party/google.rst:31 +msgid "**Application type** ``[x] Web application``" +msgstr "**Aplication type** ``[x] Web application``" -#: ../system/core-workflows/learn-by-example.rst:4 -msgid "" -"This page provides some basic examples for Core Workflows. Of course you can " -"build much more complex workflows if needed." -msgstr "" -"Ова страна обезбеђује неке основне примере за радне токове. Наравно могуће " -"је направити много сложеније токове ако је то потребно." +#: ../settings/security/third-party/google.rst:34 +msgid "**Authorized JavaScript origins** ``https://zammad_host/``" +msgstr "**Authorized JavaScript origins** ``https://zammad_host/``" -#: ../system/core-workflows/learn-by-example.rst:7 +#: ../settings/security/third-party/google.rst:37 msgid "" -"To learn about Core Workflows in detail, first go to :doc:`how-do-they-work`." +"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" +"callback``" msgstr "" -"Да бисте сазнали више о радним токовима, прво посетите :doc:`how-do-they-" -"work`." +"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" +"callback``" -#: ../system/core-workflows/learn-by-example.rst:10 -msgid "Group Based Examples" -msgstr "Примери на основу група" +#: ../settings/security/third-party/google.rst:None +msgid "Adding a new OAuth client ID" +msgstr "Додавање новог OAuth клијент ID" -#: ../system/core-workflows/learn-by-example.rst:12 +#: ../settings/security/third-party/google.rst:43 msgid "" -"All following workflows have the same base configurations. The workflow may " -"not use them all." +"After creating the credentials, go to your Zammad installation and navigate " +"to \"Admin > Security > Third Party Applications\" > Google. Enter your " +"Client ID and Client secret here." msgstr "" -"Сви следећи радни токови имају исту основну конфигурацију. Радни ток је " -"можда неће користити целу." +"Након што креирате акредитиве, пређите на инсталацију Zammad-а и идите на " +"„Администрација > Безбедност > Апликације трећег лица” > Google. Овде " +"унесите свој ID клијента и шифру клијента." -#: ../system/core-workflows/learn-by-example.rst:15 -msgid "Groups:" -msgstr "Групе:" +#: ../settings/security/third-party/google.rst:None +msgid "Zammad" +msgstr "Zammad" -#: ../system/core-workflows/learn-by-example.rst:20 -msgid "Attributes:" -msgstr "Атрибути:" +#: ../settings/security/third-party/google.rst:50 +msgid "After submitting, the login via Google can be used." +msgstr "Након снимања, пријављивање преко Google-а се може користити." -#: ../system/core-workflows/learn-by-example.rst:22 -msgid "Category (Single tree selection field, not mandatory, agents only)" +#: ../settings/security/third-party/microsoft.rst:2 +msgid "Microsoft" +msgstr "Microsoft" + +#: ../settings/security/third-party/microsoft.rst:4 +msgid "" +"Zammad's Microsoft connection allows your users with Microsoft accounts to " +"login. This works for Azure users as well and can be an alternative to :doc:" +"`/system/integrations/ldap/index`." msgstr "" -"Category (поље за једноструки избор стабла, необавезно, само оператери)" +"Zammad-ова Microsoft интеграција омогућава вашим корисницима са Microsoft " +"налозима да се пријаве. Ово функционише и за Azure кориснике и може бити " +"алтернатива :doc:`/system/integrations/ldap/index`." -#: ../system/core-workflows/learn-by-example.rst:23 +#: ../settings/security/third-party/microsoft.rst:10 msgid "" -"Approved (Boolean field, not mandatory, not shown, ``false`` as default)" +"This documentation part does not cover our :doc:`📧 Microsoft 365 email " +"channel `." msgstr "" -"Approved (логичко поље, необавезно, сакривено, ``false`` као подразумевана " -"вредност)" +"Овај део документације не покрива наш :doc:`📧 Microsoft 365 имејл канал `." -#: ../system/core-workflows/learn-by-example.rst:24 -msgid "Operating System (Text field, not mandatory, not shown)" -msgstr "Operating System (поље текста, необавезно, сакривено)" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screenshot showing Microsoft login button on Zammad login screen." +msgstr "" +"Снимак екрана који приказује дугме за пријаву на Microsoft на екрану пријаве " +"у Zammad." -#: ../system/core-workflows/learn-by-example.rst:25 -msgid "Software used (Single selection field, not mandatory, not shown)" -msgstr "Software used (поље једноструког избора, необавезно, сакривено)" - -#: ../system/core-workflows/learn-by-example.rst:68 -msgid "Group specific values and fields" -msgstr "Груписање специфичних вредности и поља" +#: ../settings/security/third-party/microsoft.rst:30 +#: ../settings/security/third-party/microsoft.rst:53 +msgid "Supported account types:" +msgstr "Подржани типови налога:" -#: ../system/core-workflows/learn-by-example.rst:28 +#: ../settings/security/third-party/microsoft.rst:22 msgid "" -"This workflow set depends on the category field. It reduces the available " -"set of values based on the group selected." +"Please note that Zammad only supports these account types (App dependent):" msgstr "" -"Овај колекција радних токова зависи од поља категорије. Смањује доступни " -"скуп вредности на основу изабране групе." +"Имајте на уму да Zammad подржава само следеће типове налога (зависно од " +"апликације):" -#: ../system/core-workflows/learn-by-example.rst:33 -msgid "Workflow 2nd Level group" -msgstr "Радни ток 2nd Level групе" +#: ../settings/security/third-party/microsoft.rst:35 +msgid "Avatars of signing in users:" +msgstr "Аватари пријављених корисника:" -#: ../system/core-workflows/learn-by-example.rst:35 +#: ../settings/security/third-party/microsoft.rst:33 msgid "" -"This reduces the category options to ``2nd Level/*``, ``Internal/*`` and " -"``Others``. It also sets further required fields to mandatory and visible." +"Zammad currently ignores user avatars. If the user is registered with e.g. " +"Gravatar, Zammad will fetch the avatar from there if enabled. See :doc:" +"`Zammad Image Service ` for more." msgstr "" -"Смањује број опција Category поља на ``2nd Level/*``, ``Internal/*`` и " -"``Others``. Такође поставља даља обавезна поља на обавезна и као видљива." +"Zammad тренутно игнорише аватаре корисника. Уколико је корисник регистрован " +"код нпр. Gravatar сервиса, Zammad ће преузети аватар одатле ако је укључено. " +"Погледајте :doc:`Zammad услуга за слике ` за више " +"детаља." -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for 2nd level" +#: ../settings/security/third-party/microsoft.rst:38 +msgid "Step 1 - Register a Microsoft App for Zammad" +msgstr "Корак 1 - Региструјте Microsoft апликацију за Zammad" + +#: ../settings/security/third-party/microsoft.rst:40 +msgid "" +"Login to the `Microsoft Azure Portal `_ and " +"navigate to App registrations to create a new app. Provide the requested " +"information as follows and register your app." msgstr "" -"Пример радног тока који приказује одређене вредности и поља за 2nd Level" +"Пријавите се на `Microsoft Azure портал `_ и " +"идите на App registrations да бисте додали нову апликацију. Наведите тражене " +"информације на следећи начин и региструјте своју апликацију." -#: ../system/core-workflows/learn-by-example.rst:43 -msgid "Workflow Support group" -msgstr "Радни ток Support групе" +#: ../settings/security/third-party/microsoft.rst:46 +msgid "Name:" +msgstr "Назив:" -#: ../system/core-workflows/learn-by-example.rst:45 +#: ../settings/security/third-party/microsoft.rst:45 msgid "" -"This reduces the category options to ``Support/*``, ``Internal/*`` and " -"``Others``. It also sets further required fields to visible." +"Any meaningful name fitting, this name will be displayed to users trying to " +"authenticate with this app." msgstr "" -"Смањује број опција Category поља на ``Support/*``, ``Internal/*`` и " -"``Others``. Такође поставља додатна обавезна поља као видљива." +"Било који назив који има смисла је дозвољен, име ће бити приказано " +"корисницима који покушавају да се аутентификују помоћу ове апликације." -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for support" -msgstr "Пример радног тока који приказује одређене вредности и поља за Support" +#: ../settings/security/third-party/microsoft.rst:49 +msgid "Choose one of the above mentioned account types (see Limitations)." +msgstr "" +"Изаберите један од горе наведених типова налога (погледајте ограничења)." -#: ../system/core-workflows/learn-by-example.rst:53 -msgid "Workflow Sales group" -msgstr "Радни ток Sales групе" +#: ../settings/security/third-party/microsoft.rst:51 +msgid "" +"The correct account type depends on your use case. If you want to use the " +"authentication internal only, choose the first option. If you're unsure, use " +"the \"Help me choose...\" link." +msgstr "" +"Тачан тип налога зависи од вашег случаја коришћења. Ако желите да користите " +"само интерну аутентификацију, изаберите прву опцију. Ако нисте сигурни, " +"користите линк „Help me choose…“." -#: ../system/core-workflows/learn-by-example.rst:55 +#: ../settings/security/third-party/microsoft.rst:58 +msgid "Redirect URI (optional):" +msgstr "URI адреса преусмерења (опционо):" + +#: ../settings/security/third-party/microsoft.rst:56 msgid "" -"This reduces the category options to ``Sales/*``, ``Internal/*`` and " -"``Others``." +"Select web and provide your callback URL. The callback URL looks like this: " +"``https://zammad.domain.tld/auth/microsoft_office365/callback``" msgstr "" -"Смањује број опција Category поља на ``Sales/*``, ``Internal/*`` и " -"``Others``." +"Изаберите веб и наведите URL адресу повратног позива. Ваш URL повратног " +"позива изгледа овако: ``https://zammad.domain.tld/auth/microsoft_office365/" +"callback``" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for sales" -msgstr "Пример радног тока који приказује одређене вредности и поља за Sales" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to register a Microsoft app" +msgstr "Снимак екрана који показује како да региструјете Microsoft апликацију" -#: ../system/core-workflows/learn-by-example.rst:68 -#: ../system/integrations/slack.rst:88 -msgid "The Result" -msgstr "Резултат" +#: ../settings/security/third-party/microsoft.rst:71 +msgid "Within **API permissions** add the following permissions:" +msgstr "У оквиру **API permissions** додајте следеће дозволе:" -#: ../system/core-workflows/learn-by-example.rst:63 -msgid "" -"This is what the agent would experience with the above workflows in place." -msgstr "Ово је оно што би оператер видео са горе наведеним радним токовима." +#: ../settings/security/third-party/microsoft.rst:69 +msgid "``User.Read``" +msgstr "``User.Read``" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "" -"Workflow shows objects and limits options based on selections on the group" -msgstr "Радни ток приказује објекте и ограничава опције на основу избора групе" +#: ../settings/security/third-party/microsoft.rst:71 +msgid "Contacts" +msgstr "Контакти" -#: ../system/core-workflows/learn-by-example.rst:90 -msgid "Approval process" -msgstr "Approval процес" +#: ../settings/security/third-party/microsoft.rst:71 +msgid "``Contacts.Read``" +msgstr "``Contacts.Read``" -#: ../system/core-workflows/learn-by-example.rst:71 +#: ../settings/security/third-party/microsoft.rst:73 msgid "" -"In this case ``approved`` is visible to agents by default. For this " -"workflow, an additional role ``Approval person`` is required (no further " -"permissions)." +"You can find these permissions within *Microsoft Graph → Delegated " +"permissions*." msgstr "" -"У овом случају ``approved`` је подразумевано видљиво оператерима. За овај " -"радни ток посла потребна је додатна улога ``Approval person`` (без додатних " -"дозвола)." +"Ове дозволе можете пронаћи у оквиру *Microsoft Graph → Delegated " +"permissions*." -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that restricts an approval attribute to specific roles" -msgstr "Пример радног тока који ограничава атрибут Approval на одређене улоге" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to add required API permissions" +msgstr "Снимак екрана који показује како да додате потребне API дозволе" -#: ../system/core-workflows/learn-by-example.rst:81 +#: ../settings/security/third-party/microsoft.rst:80 msgid "" -"This workflow may work best in combination with a :doc:`trigger ` but technically, this is not required." +"Within **Certificates & secrets** create a new client secret. Note down the " +"returned secret **value** for later. **Do not** use the secret ID!" msgstr "" -"Овај радни ток можда најбоље функционише у комбинацији са :doc:`окидачем `, али технички није неопходан." +"У оквиру **Certificates & secrets** креирајте нови client secret. Забележите " +"добијену **вредност** шифре за касније. **Немојте** користити тајни ID!" -#: ../system/core-workflows/learn-by-example.rst:84 +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to create a new app secret" +msgstr "Снимак екрана који показује како да направите нову шифру апликације" + +#: ../settings/security/third-party/microsoft.rst:88 msgid "" -"Select fields may be a better approach because they allow more values than " -"just a simple ``true`` or ``false``." +"From **Overview** copy your apps *Application (client) ID*. If you're using " +"a single tenant app, please also copy *Directory (tenant) ID*. You now have " +"all required information for Zammad." msgstr "" -"Поља избора могу представљати бољи приступ јер дозвољавају више вредности од " -"једноставног ``true`` или ``false``." +"Из **Overview** копирајте своје *Application (client) ID*. Ако користите " +"апликацију само једног корисника, копирајте и *Directory (tenant) ID*. Сада " +"имате све потребне информације за Zammad." -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "" -"Workflow fixes possible values of \"Approved ?\" to a specific selection " -"depending on the users role" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to retreive application client and tenant IDs" msgstr "" -"Радни ток мења могуће вредности „Approved ?“ поља у зависности од улоге " -"корисника" +"Снимак екрана који показује како да преузмете ID клијента и корисника " +"апликације" -#: ../system/core-workflows/learn-by-example.rst:103 -msgid "State dependent mandatory fields" -msgstr "Обавезна поља зависна од стања" +#: ../settings/security/third-party/microsoft.rst:98 +msgid "Step 2 - Add App Credentials to Zammad" +msgstr "Корак 2 - Додајте акредитиве апликације у Zammad" -#: ../system/core-workflows/learn-by-example.rst:93 +#: ../settings/security/third-party/microsoft.rst:100 msgid "" -"This workflow sets ``Category`` to mandatory if the agent wants to set the " -"states ``closed`` or ``pending close`` to enforce categorization." +"Navigate to Security > Third-party Applications (Tab) within Zammad's admin " +"settings. Scroll down to the section *Authentication via Microsoft* and fill " +"in the required information." msgstr "" -"Овај радни ток поставља ``Category`` поље на обавезно ако оператер жели да " -"подеси стања ``затворено`` или ``чека на затварање`` ради примене " -"категоризације." +"Идите на Безбедност > Апликације трећег лица (језичак) у оквиру Zammad-ових " +"администраторских подешавања. Померите се надоле до одељка *Аутентификација " +"путем Microsoft* и попуните потребне информације." -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that sets fields to mandatory on specific states" -msgstr "Пример радног тока који поставља поља на обавезна за одређена стања" +#: ../settings/security/third-party/microsoft.rst:105 +msgid "App ID:" +msgstr "ID апликације:" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "" -"Workflow sets category field to mandatory upon choosing closed or pending " -"close as state" -msgstr "" -"Радни ток поставља Category поље на обавезно након одабира затворено или на " -"чека на затварање за стање" +#: ../settings/security/third-party/microsoft.rst:105 +msgid "This is your *Application (client) ID*." +msgstr "Ово је ваш *Application (client) ID*." -#: ../system/core-workflows/learn-by-example.rst:106 -msgid "Manual Ticket Handover Process" -msgstr "Процес ручног пребацивања тикета" +#: ../settings/security/third-party/microsoft.rst:108 +msgid "App secret:" +msgstr "Шифра апликације:" -#: ../system/core-workflows/learn-by-example.rst:108 -msgid "This example covers the handover of a ticket from one agent to another:" -msgstr "Овај пример осликава пренос тикета са једног оператера на другог:" +#: ../settings/security/third-party/microsoft.rst:108 +msgid "This is your *client secret* (value)." +msgstr "Ово је ваш *client secret* (вредност)." -#: ../system/core-workflows/learn-by-example.rst:110 +#: ../settings/security/third-party/microsoft.rst:113 +msgid "App Tenant ID:" +msgstr "ID корисника апликације:" + +#: ../settings/security/third-party/microsoft.rst:111 msgid "" -"When the ticket owner is modified, a new text field (\"Handover\") shows up " -"for a comment" +"**optional** only required for apps that use account type *Accounts in this " +"organizational directory only (Default Directory only - Single tenant).*" msgstr "" -"Када је власник тикета промењен, ново поље уноса текста („Примопредаја”) ће " -"се приказати за унос коментара" +"**необавезно** потребно само за апликације које користе тип налога *Accounts " +"in this organizational directory only (Default Directory only - Single " +"tenant).*" -#: ../system/core-workflows/learn-by-example.rst:112 +#: ../settings/security/third-party/microsoft.rst:115 msgid "" -"This may only be visible when the owner is changed, therefore it has to be " -"hidden in general" +"Apply your settings by pressing submit and activate *Authentication via " +"Microsoft*." msgstr "" -"Ово поље може постати видљиво само када се власник измени, у супротном мора " -"остати сакривено" - -#: ../system/core-workflows/learn-by-example.rst:114 -msgid "The input in this handover text field is mandatory" -msgstr "Унос овог поља за примопредају је обавезан" +"Примените подешавања притиском на пошаљи и активирајте *Аутентификација " +"преко Microsoft*." -#: ../system/core-workflows/learn-by-example.rst:115 +#: ../settings/security/third-party/microsoft.rst:None msgid "" -"After submitting changes, the value of the handover field must be added as " -"an note to the ticket (via trigger)" +"Screencast showing how to add app credentials and activating the\n" +"authentication method" msgstr "" -"По слању измена, вредност поља за примопредају мора бити додат као напомена " -"тикета (преко окидача)" - -#: ../system/core-workflows/learn-by-example.rst:121 -msgid "Hiding handover field" -msgstr "Скривање поља за примопредају" - -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Hiding the handover field in core workflows" -msgstr "Скривање поља за примопредају у радним токовима" - -#: ../system/core-workflows/learn-by-example.rst:126 -msgid "Showing handover field and setting it to mandatory" -msgstr "Приказ поља за примопредају и постављање на обавезно" - -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Showing the handover field and set it as mandatory" -msgstr "Приказ поља за примопредају и постављање на обавезно" - -#: ../system/core-workflows/learn-by-example.rst:131 -msgid "Trigger writing handover input to a new article" -msgstr "Окидач за претварање уноса примопредају у нови чланак" +"Снимак екрана који показује како додати акредитиве апликације и активирати\n" +"метод аутентификације" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Write handover content to a new article" -msgstr "Снимање садржаја примопредаје као нови чланак" +#: ../settings/security/third-party/saml.rst:2 +msgid "SAML" +msgstr "SAML" -#: ../system/core-workflows/learn-by-example.rst:133 +#: ../settings/security/third-party/saml.rst:4 msgid "" -"As a result, the ticket includes an article of the type note which includes " -"the predefined text and the handover comment." +"Connect your SAML (Security Assertion Markup Language) identity provider as " +"a single sign-on (SSO) method." msgstr "" -"Као резултат, тикет сада укључује чланак напомене који садржи предефинисани " -"текст и коментар примопредаје." - -#: ../system/core-workflows/limitations.rst:6 -msgid "Core Workflows do not replace Triggers" -msgstr "Радни токови не замењују окидаче" +"Повежите свог SAML (Security Assertion Markup Language) сервис провајдера " +"као метод јединствене пријаве (SSO)." -#: ../system/core-workflows/limitations.rst:5 +#: ../settings/security/third-party/saml.rst:7 msgid "" -"Workflows manipulate the behavior of fields. However, they do not set values " -"in fields because of actions." +"SAML is an open standard for SSO authentication (among other things). Sign-" +"ins are shared across multiple **service providers** and managed by a " +"central **identity provider** (IdP)." msgstr "" -"Радни токови манипулишу понашање поља. Међутим, они не постављају вредности " -"у поља због радњи." - -#: ../system/core-workflows/limitations.rst:16 -msgid "API calls are only partly affected" -msgstr "API позиви су само делимично захваћени" +"SAML је отворени стандард за SSO аутентификацију (између осталог). Пријаве " +"су подељене на више **сервисних провајдера** и њима управља централни " +"**провајдер идентитета** (IdP)." -#: ../system/core-workflows/limitations.rst:9 +#: ../settings/security/third-party/saml.rst:11 msgid "" -"Some options affect UI only and thus do not restrict responses and calls." +"In this case, the service provider is Zammad, and the IdP is a software " +"service that you either host or subscribe to (*e.g.,* `Keycloak `_, `Redhat SSO Server `_, `ADFS `_, or `Okta `_)." msgstr "" -"Неке опције утичу само на кориснички интерфејс и стога не ограничавају API " -"захтеве." - -#: ../system/core-workflows/limitations.rst:11 -msgid "This affects the following actions:" -msgstr "Ово утиче на следеће радње:" - -#: ../system/core-workflows/limitations.rst:13 -msgid "select" -msgstr "изабери" +"У овом случају, сервисни провајдер је Zammad, а IddP је софтверски сервис " +"који или хостујете сами или се претплатите на њега (*нпр.* `Keycloak " +"`_, `Redhat SSO Server `_, `ADFS `_ или `Okta " +"` _)." -#: ../system/core-workflows/limitations.rst:14 -msgid "auto select" -msgstr "аутоматски избор" +#: ../settings/security/third-party/saml.rst:18 +msgid "" +"This guide assumes you are already using SAML within your organization (i." +"e., that your IdP is fully set up)." +msgstr "" +"Овај водич претпоставља да већ користите SAML у својој организацији (тј. да " +"је ваш IdP у потпуности подешен)." -#: ../system/core-workflows/limitations.rst:15 -msgid "show" -msgstr "прикажи" +#: ../settings/security/third-party/saml.rst:21 +msgid "" +"Please note: Our instructions are based on connecting Zammad with Keycloak." +msgstr "" +"Обратите пажњу: наша упутства су базирана на повезивању Zammad-а са Keycloak-" +"ом." -#: ../system/core-workflows/limitations.rst:16 -msgid "hide" -msgstr "сакриј" +#: ../settings/security/third-party/saml.rst:25 +msgid "Step 1: Configure Your IdP" +msgstr "Корак 1: Подесите свој IdP" -#: ../system/core-workflows/limitations.rst:25 -msgid "Some fields stay unavailable to customers" -msgstr "Нека поља остају недоступна клијентима" +#: ../settings/security/third-party/saml.rst:28 +msgid "Add Zammad as a Client/App" +msgstr "Додајте Zammad као клијента/апликацију" -#: ../system/core-workflows/limitations.rst:19 +#: ../settings/security/third-party/saml.rst:30 msgid "" -"For technical and security reasons, some default fields (the pale ones you " -"can't edit) stay unavailable for display and usage on customer permissions." +"Import Zammad into your IdP using the XML configuration found at ``https://" +"your.zammad.domain/auth/saml/metadata``." msgstr "" -"Из техничких и безбедносних разлога, нека подразумевана поља (нпр. она бледа " -"која не можете да мењате) остају недоступна за приказ и коришћење за дозволе " -"клијента." +"Увезите Zammad у свој IdP користећи XML конфигурацију која се налази на " +"``https://your.zammad.domain/auth/saml/metadata``." -#: ../system/core-workflows/limitations.rst:23 +#: ../settings/security/third-party/saml.rst:33 msgid "" -"If you require your customers to change e.g. priorities, please consider " -"using workarounds via :doc:`/system/objects` and :doc:`/manage/trigger`." +"If your IdP doesn't support XML import, you will have to configure Zammad as " +"a new client/app manually using the above XML metadata file for reference." msgstr "" -"Ако желите да ваши клијенти промене нпр. приоритете, размислите о коришћењу " -"алтернативних решења преко :doc:`објеката ` и :doc:`окидача " -"`." +"Уколико ваш IdP не подржава XML увоз, мораћете да подесите Zammad као новог " +"клијента/апликацију ручно, користећи горњу XML датотеку мета података као " +"референцу." -#: ../system/core-workflows/limitations.rst:29 -msgid "Ticket title changes not supported in edit mask" -msgstr "Измена наслова тикета није подржана у форми уређивања" +#: ../settings/security/third-party/saml.rst:36 +msgid "For instance, when you see this tag:" +msgstr "На пример, када видите ову ознаку:" -#: ../system/core-workflows/limitations.rst:28 +#: ../settings/security/third-party/saml.rst:42 msgid "" -"It is currently not possible to perform changes of the ticket title in the " -"edit mask (e.g. renaming, set to read-only)." +"Set the **Assertion Consumer Service Binding URL** (sometimes also listed as " +"**Valid Redirect URIs**) to ``http://your.zammad.domain/auth/saml/callback``." msgstr "" -"Тренутно није могуће изменити наслов тикета у форми уређивања (нпр. промена " -"наслова, постављање само на читање)." +"Подесите **Assertion Consumer Service Binding URL** (понекад је наведен и " +"као **Valid Redirect URIs**) на ``http://your.zammad.domain/auth/saml/" +"callback``." -#: ../system/core-workflows/limitations.rst:37 -msgid "What is out of scope of Core Workflows?" -msgstr "Шта је то изван опсега радних токова?" +#: ../settings/security/third-party/saml.rst:47 +msgid "Set Up User Attribute Mapping" +msgstr "Подесите мапирање корисничких атрибута" -#: ../system/core-workflows/limitations.rst:32 +#: ../settings/security/third-party/saml.rst:49 msgid "" -"There are some things that would count as workflow but are either done via :" -"doc:`/manage/trigger` or :doc:`/manage/scheduler`." +"Zammad requests the following user attributes (or “properties”) from the IdP:" msgstr "" -"Постоје неке ствари које би се рачунале као радни ток, али се извршавају или " -"преко :doc:`окидача ` и :doc:`планера `." +"Zammad захтева следеће корисничке атрибуте (или „properties“) од IdP-а:" -#: ../system/core-workflows/limitations.rst:35 -msgid "Such as (but not limited to):" -msgstr "Као што су (али не ограничавајући се на):" +#: ../settings/security/third-party/saml.rst:51 +msgid "Email address (``email``)" +msgstr "Имејл адреса (``email``)" -#: ../system/core-workflows/limitations.rst:37 -msgid "up- or downgrade permissions of users" -msgstr "промоција или скидање дозвола корисника" +#: ../settings/security/third-party/saml.rst:52 +msgid "Full name (``name``)" +msgstr "Пуно име и презиме (``name``)" -#: ../system/core-workflows/limitations.rst:38 -msgid "affecting article creation or listing" -msgstr "утицај на додавање или листање чланака" +#: ../settings/security/third-party/saml.rst:53 +msgid "Given name (``first_name``)" +msgstr "Име (``first_name``)" -#: ../system/data-privacy.rst:2 -msgid "Data Privacy" -msgstr "Приватност података" +#: ../settings/security/third-party/saml.rst:54 +msgid "Family name (``last_name``)" +msgstr "Презиме (``last_name``)" -#: ../system/data-privacy.rst:4 +#: ../settings/security/third-party/saml.rst:56 msgid "" -"For compliance with GDPR and other data privacy laws, you may wish to " -"**permanently delete users from the system**, along with **all of their " -"associated tickets**." +"You may need to set up “mappers” (or “mappings”) to tell your IdP how user " +"attributes in SAML correspond to those in Zammad. For a more detailed " +"breakdown, refer to the XML metadata file referenced in the previous section." msgstr "" -"Да бисте били усклађени са GDPR-ом и другим законима о приватности података, " -"можда ћете пожелети да будете у могућности да **трајно избришете кориснике " -"из система**, заједно са **свим повезаним тикетима**." +"Можда ћете морати да подесите „mappers“ (или „mappings“) да бисте свом IdP-у " +"рекли како кориснички атрибути у SAML-у одговарају онима у Zammad-у. За " +"детаљнију анализу погледајте XML датотеку мета података наведену у " +"претходном одељку." -#: ../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 `!" -msgstr "" -"Можете дефинисати ручне задатке или чак аутоматизоване захтеве за брисање " -"тикета и корисника на основу прилагођених услова путем :doc:`планера `!" +#: ../settings/security/third-party/saml.rst:62 +msgid "Per-IdP Instructions" +msgstr "Упутства за IdP" -#: ../system/data-privacy.rst:12 +#: ../settings/security/third-party/saml.rst:102 +msgid "Keycloak" +msgstr "Keycloak" + +#: ../settings/security/third-party/saml.rst:65 msgid "" -"Access to this panel requires ``admin.data_privacy`` permissions (introduced " -"in Zammad 3.5)." +"**To add Zammad as a client,** save the XML configuration to disk (``https://" +"your.zammad.domain/auth/saml/metadata``) and use **Clients > Clients list > " +"Import client** in the Keycloak admin panel." msgstr "" -"Приступ овом панелу захтева дозволу ``admin.data_privacy`` (уведена у Zammad " -"верзији 3.5)." +"**Да бисте додали Zammad као клијента,** сачувајте XML конфигурацију на диск " +"(``https://your.zammad.domain/auth/saml/metadata``) и користите **Clients > " +"Clients list > Import client* * у Keycloak админ панелу." -#: ../system/data-privacy.rst:15 +#: ../settings/security/third-party/saml.rst:70 msgid "" -"On older systems that have not been updated yet, customers can also be :docs:" -"`deleted via the Zammad console `." -msgstr "" -"На старијим системима који још нису ажурирани, клијенти се такође могу :docs:" -"`обрисати преко Zammad конзоле `." - -#: ../system/data-privacy.rst:22 -msgid "User deletion dialog in the Data Privacy panel" -msgstr "Дијалог за брисање корисника у панелу приватности података" - -#: ../system/data-privacy.rst:22 -msgid "" -"The user deletion dialog lists some of the tickets that will be removed from " -"the system along with the user." +"To help Zammad **match its own user accounts to Keycloak users**, create a " +"user attribute (or “property”) mapper. In **Clients list**, click on your " +"newly created Client ID, choose the tab **Client scopes** and click on the " +"link which refers to your Zammad instance. Choose **Add mapper > By " +"configuration > User Property** and create a mapper with the following " +"entries:" msgstr "" -"Дијалог за брисање корисника приказује неке од тикета који ће бити уклоњени " -"из система заједно са корисником." +"Да бисте помогли Zammad-у да **повеже сопствене корисничке налоге са " +"Keycloak корисницима**, креирајте мапирање атрибута корисника (или " +"„property“). У **Clients list** кликните на ваш новокреирани ID клијента, " +"изаберите језичак **Client scopes** и кликните на линк који се односи на " +"вашу Zammad инстанцу. Изаберите **Add mapper > By configuration > User " +"Property** и додајте мапирање са следећим уносима:" -#: ../system/data-privacy.rst:27 -msgid "Deleting Users via GUI" -msgstr "Брисање корисника путем корисничког интерфејса" +#: ../settings/security/third-party/saml.rst:78 +msgid "**Name**" +msgstr "**Name**" -#: ../system/data-privacy.rst:29 -msgid "🔥 **All deletions are FINAL!**" -msgstr "🔥 **Сва брисања су КОНАЧНА!**" +#: ../settings/security/third-party/saml.rst:80 +msgid "**Mapper Type**" +msgstr "**Mapper Type**" -#: ../system/data-privacy.rst:31 -msgid "Once you click “Delete”, the action cannot be canceled or undone." -msgstr "Када кликнете на „Избриши“, радња се не може отказати или опозвати." +#: ../settings/security/third-party/saml.rst:81 +msgid "``User Property``" +msgstr "``User Property``" -#: ../system/data-privacy.rst:33 -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." -msgstr "" -"Сваки пут када избришете корисника, сви њихови тикети ће такође бити " -"избрисани. Није могуће избрисати корисника и задржати њихове тикете." +#: ../settings/security/third-party/saml.rst:82 +msgid "**Property**" +msgstr "**Property**" -#: ../system/data-privacy.rst:36 -msgid "**The following records cannot be deleted:**" -msgstr "**Следећи налози се не могу избрисати:**" +#: ../settings/security/third-party/saml.rst:83 +msgid "``emailAddress``" +msgstr "``emailAddress``" -#: ../system/data-privacy.rst:38 -msgid "your own account" -msgstr "ваш тренутни налог" +#: ../settings/security/third-party/saml.rst:84 +msgid "**SAML Attribute Name**" +msgstr "**Назив SAML атрибута**" -#: ../system/data-privacy.rst:39 -msgid "the system's last remaining administrator account" -msgstr "последњи налог администратора у систему" +#: ../settings/security/third-party/saml.rst:86 +msgid "**SAML Attribute NameFormat**" +msgstr "**Формат назива SAML атрибута**" -#: ../system/data-privacy.rst:42 -msgid "Step 1: Find a User / Confirm Deletion" -msgstr "Корак 1: Пронађите корисника / потврдите брисање" +#: ../settings/security/third-party/saml.rst:87 +msgid "``basic``" +msgstr "``basic``" -#: ../system/data-privacy.rst:44 -msgid "There are three ways to access the user deletion dialog:" -msgstr "Постоје три начина за приступ дијалогу за брисање корисника:" +#: ../settings/security/third-party/saml.rst:89 +msgid "" +"In the example above, we're telling Zammad that whenever it receives a SAML " +"login request, it should take the ``email`` property from Keycloak, look for " +"a Zammad user with the same ``email`` attribute, and create a new session " +"for that user." +msgstr "" +"У горњем примеру, кажемо Zammad-у да кад год прими SAML захтев за пријаву, " +"треба да узме атрибут ``email`` од Keycloak-а, потражи Zammad корисника са " +"истим атрибутом ``email`` и креира нову сесију за тог корисника." -#: ../system/data-privacy.rst:51 -msgid "**from the user's profile**" -msgstr "**из корисничког профила**" +#: ../settings/security/third-party/saml.rst:95 +msgid "" +"If your Keycloak users' email addresses are stored on another property (*e." +"g.,* ``username``), adjust accordingly." +msgstr "" +"Ако су имејл адресе ваших Keycloak корисника ускладиштене у другом атрибуту " +"(*нпр.* ``username``), прилагодите мапирање у складу са тим." -#: ../system/data-privacy.rst:0 -msgid "Accessing the user deletion dialog in a user profile" -msgstr "Приступ дијалогу за брисање корисника из корисничког профила" +#: ../settings/security/third-party/saml.rst:98 +msgid "" +"Back in **Settings**, enter the Client ID (``https://your.zammad.domain/auth/" +"saml/metadata``) in the field **Master SAML Processing URL**." +msgstr "" +"Вратите се у **Settings**, унесите Client ID (``https://your.zammad.domain/" +"auth/saml/metadata``) у поље **Master SAML Processing URL**." -#: ../system/data-privacy.rst:51 -msgid "Click **Action > Delete**." -msgstr "Кликните на **Радња > Избриши**." +#: ../settings/security/third-party/saml.rst:101 +msgid "You also need to enable **Sign assertions**." +msgstr "Такође морате да укључите **Sign assertions**." -#: ../system/data-privacy.rst:58 -msgid "**in the “Manage > Users” Admin Panel**" -msgstr "**из администраторског панела „Управљање > Корисници“**" +#: ../settings/security/third-party/saml.rst:105 +msgid "Step 2: Configure Zammad" +msgstr "Корак 2: Подесите Zammad" -#: ../system/data-privacy.rst:0 -msgid "Accessing the user deletion dialog under “Users” in the Admin Panel" +#: ../settings/security/third-party/saml.rst:107 +msgid "" +"Enable SAML and enter your IdP's details in the Admin Panel under **Settings " +"> Security > Third Party Applications > Authentication via SAML**:" msgstr "" -"Приступ дијалогу за брисање корисника под „Корисници“ у администраторском " -"панелу" +"Укључите SAML и унесите детаље свог IdP-а у администраторском панелу под " +"**Подешавања > Безбедност > Апликације трећег лица > Аутентификација путем " +"SAML**:" -#: ../system/data-privacy.rst:58 -msgid "Use the **⋮ Actions** menu for the target user." -msgstr "Користите мени **⋮ Радње** за циљног корисника." +#: ../settings/security/third-party/saml.rst:None +msgid "Example configuration of SAML part 1" +msgstr "Пример подешавања SAML део 1" -#: ../system/data-privacy.rst:66 ../system/data-privacy.rst:104 -msgid "**in the “System > Data Privacy” Admin Panel**" -msgstr "**из администраторског панела „Систем > Приватност података“**" +#: ../settings/security/third-party/saml.rst:119 +msgid "Display name" +msgstr "Назив за приказ" -#: ../system/data-privacy.rst:0 +#: ../settings/security/third-party/saml.rst:116 msgid "" -"Accessing the user deletion dialog under “Data Privacy” in the Admin Panel" +"Allows you to define a custom button name for SAML. This helps your users to " +"understand better what the button on the login page does." msgstr "" -"Приступ дијалогу за брисање корисника под „Приватност података“ у " -"административном панелу" +"Омогућава вам да одредите прилагођени назив дугмета за SAML. Ово помаже " +"вашим корисницима да боље разумеју шта ради дугме на страници за пријаву." -#: ../system/data-privacy.rst:65 +#: ../settings/security/third-party/saml.rst:119 +msgid "Defaults to ``SAML``." +msgstr "Подразумевано је ``SAML``." + +#: ../settings/security/third-party/saml.rst:123 +msgid "IDP SSO target URL" +msgstr "IDP SSO URL путања" + +#: ../settings/security/third-party/saml.rst:122 msgid "" -"Use the **New Deletion Task** button. Search for users by name or email " -"address." +"This is the target URL Zammad shall redirect to when the user presses the " +"SAML button. For Keycloak, this needs to look like https://your.domain/" +"realms/your-realm/protocol/saml" msgstr "" -"Користите дугме **Нови захтев за брисање**. Претражите кориснике по имену " -"или имејл адреси." +"Ово је циљна URL адреса на коју ће Zammad преусмерити када корисник притисне " +"SAML дугме. За Keycloak, ово треба да изгледа као https://your.domain/realms/" +"your-realm/protocol/saml" -#: ../system/data-privacy.rst:79 -msgid "**Delete organizations**" -msgstr "**Брисање организација**" +#: ../settings/security/third-party/saml.rst:127 +msgid "IDP single logout target URL" +msgstr "IDP URL путања јединствене одјаве" -#: ../system/data-privacy.rst:69 +#: ../settings/security/third-party/saml.rst:126 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:" +"This is the URL to which the single logout request and response should be " +"sent." msgstr "" -"Ако је клијент кога бришете последњи корисник у својој организацији, опција " -"**Избриши организацију?** биће приказана у дијалогу за брисање корисника:" +"Ово је URL путања на коју треба преусмерити захтеве и одговоре за " +"јединствену одјаву." -#: ../system/data-privacy.rst:0 -msgid "Deleting an organization via the user deletion dialog" -msgstr "Брисање организације преко дијалога за брисање корисника" +#: ../settings/security/third-party/saml.rst:131 +msgid "IDP certificate" +msgstr "IDP сертификат" -#: ../system/data-privacy.rst:78 +#: ../settings/security/third-party/saml.rst:130 msgid "" -"If this option does not appear, make sure there are no pending deletion " -"tasks for other customers from this organization." +"The public certificate of your IDP for Zammad to verify during the callback " +"phase." msgstr "" -"Ако се ова опција не појави, проверите да нема заказаних брисања за друге " -"клијенте из ове организације." +"Јавни сертификат вашег IDP-а који Zammad треба да провери током фазе " +"повратног позива." -#: ../system/data-privacy.rst:82 -msgid "Step 2: Monitor Deletion Job Status" -msgstr "Корак 2: Пратите статус заказаног захтева за брисање" +#: ../settings/security/third-party/saml.rst:145 +msgid "IDP certificate fingerprint" +msgstr "IDP отисак сертификата" -#: ../system/data-privacy.rst:84 +#: ../settings/security/third-party/saml.rst:134 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:" +"The fingerprint of your IDPs public certificate to verify during callback " +"phase." msgstr "" -"Систему може бити потребно до десет минута да обради ваш захтев, тако да се " -"за сваког корисника којег избришете прво заказује „захтев за брисање“. " -"Статус ових захтева можете пратити на два места:" - -#: ../system/data-privacy.rst:98 -msgid "**in the Activity Stream**" -msgstr "**у току активности**" +"Отисак вашег јавног IDP сертификата за верификацију током фазе повратног " +"позива." -#: ../system/data-privacy.rst:0 -msgid "Activity Stream showing data privacy tasks" -msgstr "Ток активности који приказује захтеве приватности података" +#: ../settings/security/third-party/saml.rst:137 +msgid "🔏 **For the IdP certificate / certificate fingerprint:**" +msgstr "🔏 **За IdP сертификат / отисак сертификата:**" -#: ../system/data-privacy.rst:94 +#: ../settings/security/third-party/saml.rst:139 msgid "" -"For each deleted user, the Activity Stream will be updated twice—once when " -"the task is created, and once when it's complete." +"Provide **only one or the other**—do not provide both! (Between the two, we " +"recommend the signing certificate itself: fingerprints use SHA-1, which `has " +"been broken for a while now `_.)" msgstr "" -"За сваког избрисаног корисника, ток активности ће се ажурирати два пута — " -"једном када се задатак закаже и једном када се заврши." +"Обезбедите **или једно или друго**—никако обе вредности! (Између ове две, " +"препоручујемо сам сертификат за потписивање: отисци сертификата користе " +"SHA-1 алгоритам, који је већ неко време покварен `_.)" -#: ../system/data-privacy.rst:97 +#: ../settings/security/third-party/saml.rst:144 msgid "" -"These notifications are only visible to users with ``admin.data_privacy`` " -"permissions." +"**Keycloak users:** Find your certificate in the Keycloak admin panel under " +"**Realm Settings > Keys > Algorithm: RS256 > Certificate**." msgstr "" -"Ова обавештења су видљива само корисницима са дозволама ``admin." -"data_privacy``." +"**Keycloak корисници:** Пронађите свој сертификат у Keycloak " +"административном панелу под **Realm Settings > Keys > Algorithm: RS256 > " +"Certificate**." -#: ../system/data-privacy.rst:0 +#: ../settings/security/third-party/saml.rst:151 +msgid "Name identifier format" +msgstr "Формат идентификатора назива" + +#: ../settings/security/third-party/saml.rst:148 msgid "" -"The task list within Data Privacy shows removals being in progress and " -"completed." +"This is the unique identifiers field type. Usually it should be ``urn:oasis:" +"names:tc:SAML:1.1:nameid-format:emailAddress``." msgstr "" -"Листа захтева у оквиру приватности података показује да је брисања у току " -"или извршена." +"Ово је типа идентификатора јединствених поља. Обично би требало да буде " +"``urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress``." -#: ../system/data-privacy.rst:107 -msgid "Frequently Asked Questions" -msgstr "Често постављана питања" +#: ../settings/security/third-party/saml.rst:151 +msgid "Zammad **expects an email address as unique identifier**!" +msgstr "Zammad **очекује имејл адресу као јединствени идентификатор**!" -#: ../system/data-privacy.rst:121 -msgid "What happens if I receive an email from a deleted customer?" -msgstr "Шта се дешава ако добијем имејл од избрисаног клијента?" +#: ../settings/security/third-party/saml.rst:155 +msgid "UID attribute name" +msgstr "Назив UID атрибута" -#: ../system/data-privacy.rst:110 +#: ../settings/security/third-party/saml.rst:154 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." +"Here you can define an attribute that uniquely identifies the user. If " +"unset, the name identifier returned by the IDP is used." msgstr "" -"Zammad аутоматски додаје нови кориснички налог сваки пут када прими поруку " -"са непознате имејл адресе, укључујући и избрисане кориснике. Избрисаним " -"корисницима никада није онемогућено отварање нових тикета." +"Овде можете одредити назив атрибута који јединствено идентификује корисника. " +"Уколико није подешено, биће коришћен индентификатор назива који враћа IDP." -#: ../system/data-privacy.rst:115 +#: ../settings/security/third-party/saml.rst:None +msgid "Example configuration of SAML part 2" +msgstr "Пример подешавања SAML део 2" + +#: ../settings/security/third-party/saml.rst:163 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**." +"Decide if the certificate for the connection to the IdP service has to be " +"verified or not (default: ``yes``)." msgstr "" -"У мало вероватном случају да добијете имејл поруку између тренутка када " -"кликнете на „Избриши“ и када систем обради ваш захтев, **тај тикет ће бити " -"аутоматски избрисан**. Број тикета за изгубљени тикет ће бити приказан у " -"администраторском панелу под **Систем > Приватност података > Извршени " -"захтеви > Брисање корисника > Обрисани тикети**." +"Одређује да ли ће сертификат за конекцију до IdP сервиса бити проверен или " +"не (подразумевано: ``да``)." -#: ../system/data-privacy.rst:130 -msgid "What about user information stored in internal notes or other messages?" -msgstr "" -"А шта је са корисничким информацијама сачуваним у интерним напоменама или " -"другим порукама?" +#: ../settings/security/third-party/saml.rst:169 +msgid "Signing & Encrypting" +msgstr "Потписивање и шифровање" -#: ../system/data-privacy.rst:124 +#: ../settings/security/third-party/saml.rst:169 msgid "" -"The deletion process removes **user accounts and associated tickets only**." -msgstr "Процес брисања уклања **само корисничке налоге и повезане тикете**." +"Define if you want to sign, encrypt, do both or nothing for the requests." +msgstr "Одређује да ли желите потписивање и шифровање захтева." -#: ../system/data-privacy.rst:126 +#: ../settings/security/third-party/saml.rst:179 +msgid "Certificate (PEM)" +msgstr "Сертификат (PEM)" + +#: ../settings/security/third-party/saml.rst:172 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." +"Paste the public certificate of your Zammad SAML client, if you want to " +"encrypt the requests." msgstr "" -"Ако постоје референце на име корисника или информације ускладиштене негде " -"другде у систему, те информације **неће бити уклоњене** јер не постоји начин " -"да се безбедно утврди да ли заиста описују дотичног корисника." +"Налепите јавни сертификат вашег Zammad SAML клијента, уколико желите " +"шифровање захтева." -#: ../system/data-privacy.rst:137 -msgid "I deleted an user and can still see a message they sent!" -msgstr "Избрисао сам корисника и још увек видим поруку коју је послао!" +#: ../settings/security/third-party/saml.rst:175 +msgid "Make sure the certificate is:" +msgstr "Уверите се да је сертификат:" -#: ../system/data-privacy.rst:133 -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." -msgstr "" -"Тикети могу припадати само једном клијенту, али могу садржати поруке " -"(„чланке“) од великог броја људи. Ако сте избрисали корисника, али и даље " -"видите чланке које је он послао, не брините – ти чланци су за тикет који " -"припада неком другом кориснику и више не садрже никакву референцу на " -"идентитет пошиљаоца." +#: ../settings/security/third-party/saml.rst:177 +msgid "already valid and not yet expired" +msgstr "већ важећи и није још истекао" -#: ../system/data-privacy.rst:141 -msgid "I removed a customer, now my reporting is off!" -msgstr "Уклонио сам клијента, сада су моји извештаји погрешни!" +#: ../settings/security/third-party/saml.rst:178 +msgid "no CA certificate" +msgstr "није CA сертификат" -#: ../system/data-privacy.rst:140 +#: ../settings/security/third-party/saml.rst:179 +msgid "valid for signing and encrypting" +msgstr "важећи за потписивање и шифровање" + +#: ../settings/security/third-party/saml.rst:185 +msgid "Private key (PEM)" +msgstr "Тајни кључ (PEM)" + +#: ../settings/security/third-party/saml.rst:182 msgid "" -"When removing users and their tickets, all references are removed. This also " -"affects e.g. Reporting - these information are lost." +"Paste the private key of your Zammad SAML client here, if you want to sign " +"the requests." msgstr "" -"Приликом уклањања корисника и њихових тикета, све референце се уклањају. Ово " -"утиче и на нпр. извештавање - ове информације су трајно изгубљене." +"Налепите тајни кључ вашег Zammad SAML клијента, уколико желите потписивање " +"захтева." -#: ../system/data-privacy.rst:145 -msgid "How long does Zammad store created tasks?" -msgstr "Колико дуго Zammad чува заказане захтеве?" +#: ../settings/security/third-party/saml.rst:185 +msgid "Make sure the key is an RSA key with a length of at least 2048 bits." +msgstr "Уверите се да је тајни кључ RSA дужине од најмање 2048 бита." -#: ../system/data-privacy.rst:144 +#: ../settings/security/third-party/saml.rst:188 +msgid "Private key secret" +msgstr "Лозинка тајног кључа" + +#: ../settings/security/third-party/saml.rst:188 +msgid "If your private key is secured with a secret, you can provide it here." +msgstr "Уколико је ваш тајни кључ обезбеђен лозинком, можете је унети овде." + +#: ../settings/security/third-party/saml.rst:192 +msgid "Your callback URL" +msgstr "Ваш URL повратног позива" + +#: ../settings/security/third-party/saml.rst:191 msgid "" -"Please see the on-premise data section of the :docs:`data privacy ` chapter." +"This URL is needed for your IdP configuration so it knows where to redirect " +"to after successful authentication." msgstr "" -"Погледајте одељак о локалним подацима у поглављу :docs:`приватност података " -"`." +"Ова URL адреса је потребна за вашу IDP конфигурацију како би знала где да " +"преусмери корисника након успешне аутентификације." -#: ../system/data-privacy.rst:150 -msgid "What about re-assigned tickets? I want to delete them, too." -msgstr "А шта је са поново додељеним тикетима? Желим да избришем и њих." +#: ../settings/security/third-party/saml.rst:194 +msgid "" +"After saving your input by clicking on the \"Submit\" button, Zammad " +"verifies the provided keys/certificates (e.g. if they are valid for signing/" +"encrypting and if they aren't expired)." +msgstr "" +"По снимању вашег уноса кликом на дугме „Пошаљи”, Zammad ће проверити " +"достављене кључеве/сертификате (нпр. да ли су важећи за потписивање/" +"шифровање и да нису истекли." -#: ../system/data-privacy.rst:148 +#: ../settings/security/third-party/saml.rst:199 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." +"See :ref:`automatic account linking ` for details " +"on how to link existing Zammad accounts to IdP accounts." msgstr "" -"Само тикети додељени дотичном клијенту у тренутну извршавања захтева за " -"брисање података ће бити обрисани. Брисање неће узети у обзир историјат " -"доделе." +"Погледајте :ref:`аутоматско повезивање налога ` " +"за детаље о томе како да повежете постојеће Zammad налоге са IdP налозима." -#: ../system/data-privacy.rst:154 -msgid "Why are there so many deletion task entries, I didn't create them!" -msgstr "Одакле сви ови захтеви за брисање, ја их нисам додао!" +#: ../settings/security/third-party/saml.rst:205 +msgid "Automatic account linking doesn't work" +msgstr "Аутоматско повезивање налога не функционише" -#: ../system/data-privacy.rst:153 +#: ../settings/security/third-party/saml.rst:206 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." +"Have you double-checked your IdP's user attribute mapping configuration?" msgstr "" -"Захтеви за брисање могу бити додати и од стране :doc:`планера `. Радња под називом *„Закажи захтев за брисање приватних " -"података”* је извор ових захтева." +"Да ли сте још једном проверили подешавање мапирања корисничких атрибута " +"вашег IdP-а?" -#: ../system/integrations/checkmk/admin-panel-reference.rst:2 -msgid "Admin Panel Reference" -msgstr "Референца администраторског панела" +#: ../settings/security/third-party/twitter.rst:4 +msgid "" +"It is possible to create a quick login for your helpdesk via Twitter. To do " +"so, you need to follow these steps:" +msgstr "" +"Могуће је подесити брзо пријављивање у Zammad преко Twitter-а. Да бисте то " +"урадили, потребно је да пратите следеће кораке:" -#: ../system/integrations/checkmk/admin-panel-reference.rst:None -msgid "Screenshot of Checkmk settings overview" -msgstr "Снимак екрана изгледа Checkmk подешавања" +#: ../settings/security/third-party/twitter.rst:8 +msgid "Register Twitter App" +msgstr "Регистрација Twitter апликације" -#: ../system/integrations/checkmk/admin-panel-reference.rst:12 -msgid "" -"Which :doc:`group ` should Checkmk tickets be assigned " -"to as a default (*i.e.,* when none is specified)?" +#: ../settings/security/third-party/twitter.rst:10 +msgid "Go to https://dev.twitter.com/apps and login with your account." msgstr "" -"Којој :doc:`групи ` треба да буду подразумевано " -"додељени Checkmk тикети (*тј.* када ниједна није наведена)?" +"Идите на https://dev.twitter.com/apps и пријавите се са својим налогом." -#: ../system/integrations/checkmk/admin-panel-reference.rst:15 -msgid "(Applies to :ref:`API alerts ` only.)" -msgstr "(Односи се само на :ref:`API упозорења `.)" +#: ../settings/security/third-party/twitter.rst:15 +msgid "Click on \"Create App\"" +msgstr "Кликните на „Create App”" -#: ../system/integrations/checkmk/admin-panel-reference.rst:21 -msgid "Auto close" -msgstr "Аутоматско затварање" +#: ../settings/security/third-party/twitter.rst:None +msgid "new app page" +msgstr "Страница нове апликације" -#: ../system/integrations/checkmk/admin-panel-reference.rst:18 +#: ../settings/security/third-party/twitter.rst:20 msgid "" -"Should Zammad automatically close tickets if a service has recovered on its " -"own?" -msgstr "Да ли Zammad треба да аутоматски затвори тикете ако се сервис опорави?" - -#: ../system/integrations/checkmk/admin-panel-reference.rst:21 -msgid "(Agents will receive notifications for such closures as appropriate.)" -msgstr "(Оператери ће примати обавештења о затварањима тикета по потреби.)" - -#: ../system/integrations/checkmk/admin-panel-reference.rst:30 -msgid "Auto-close state" -msgstr "Стање аутоматског затварања" - -#: ../system/integrations/checkmk/admin-panel-reference.rst:24 -msgid "What ticket state should be applied when “auto-closing” a ticket?" +"Enter app settings. As \"Callback URL\" you need to enter ``https://" +"zammad_host/api/v1/external_credentials/twitter/callback``. You need to " +"replace ``zammad_host`` with the domain of your Zammad system." msgstr "" -"Које стање тикета треба применити приликом „аутоматског затварања“ тикета?" +"Унесите подешавања апликације. Као „Callback URL“ треба да унесете ``https://" +"zammad_host/api/v1/external_credentials/twitter/callback``. Морате заменити " +"``zammad_host`` са доменом вашег Zammad система." -#: ../system/integrations/checkmk/admin-panel-reference.rst:26 +#: ../settings/security/third-party/twitter.rst:24 msgid "" -"You can choose from the seven built-in ticket states. If these states aren't " -"enough for you, you can :ref:`define a new ticket state ` for this purpose as well. This can be useful for tracking " -"tickets with :doc:`reports `, for example." +"After the app has been created, update the application icon and organization " +"attributes." msgstr "" -"Можете бирати између седам уграђених стања тикета. Ако вам ова стања нису " -"довољна, можете :docs:`дефинисати ново стање тикета `. На пример, ово може бити посебно корисно за праћење тикета " -"помоћу :doc:`извештаја `." - -#: ../system/integrations/checkmk/admin-panel-reference.rst:35 -#: ../system/integrations/cti/includes/recent-logs.include.rst:2 -#: ../system/integrations/ldap/index.rst:74 -#: ../system/integrations/pgp/index.rst:106 -msgid "Recent Logs" -msgstr "Недавни уноси евиденције" +"Након што је апликација направљена, подесите иконицу апликације и атрибуте " +"организације." -#: ../system/integrations/checkmk/admin-panel-reference.rst:None -msgid "Screenshot of Checkmk \"Recent Logs\" section" -msgstr "Снимак екрана одељка „Недавни уноси евиденције“ за Checkmk." +#: ../settings/security/third-party/twitter.rst:None +msgid "set permissions to receive and send direct messages" +msgstr "подесите дозволе за примање и слање директних порука" -#: ../system/integrations/checkmk/admin-panel-reference.rst:41 +#: ../settings/security/third-party/twitter.rst:30 msgid "" -"If you're having trouble getting Zammad and Checkmk to play nicely together, " -"this section can help you troubleshoot." +"Next we need to set ``read, write and access direct messages`` permissions " +"for the app." msgstr "" -"Ако имате проблема да натерате Zammad и Checkmk да лепо сарађују, овај " -"одељак вам може помоћи да решите проблеме." +"Затим морамо да подесимо дозволе за ``read, write and access direct " +"messages`` за апликацију." -#: ../system/integrations/checkmk/admin-panel-reference.rst:44 +#: ../settings/security/third-party/twitter.rst:None +msgid "click on Keys & Access Token, note them" +msgstr "кликните на Keys & Access Token, забележите их" + +#: ../settings/security/third-party/twitter.rst:36 msgid "" -"It contains a record of the fifty most recent transactions that Zammad knows " -"about, including each one's request/response details and return status." +"Go to \"Keys and Access Token\" tab and note the \"Consumer Key\" and " +"\"Consumer Secret\"." msgstr "" -"Садржи записе о педесет најновијих трансакција за које Zammad зна, " -"укључујући детаље захтева/одговора и статус одговора." +"Идите на језичал „Keys and Access Toke“ и забележите „Consumer Key“ и " +"„Consumer Secret“." -#: ../system/integrations/checkmk/api-reference.rst:2 -msgid "API Reference" -msgstr "API референца" +#: ../settings/security/third-party/twitter.rst:40 +msgid "Configure Zammad as Twitter App" +msgstr "Подесите Zammad као Twitter апликацију" -#: ../system/integrations/checkmk/api-reference.rst:4 +#: ../settings/security/third-party/twitter.rst:42 msgid "" -"For most users, :ref:`the sample scripts from the Setup Guide ` will do the job just fine. But if you want more fine-grained control" -"—for instance, to create high- and low-priority tickets for different types " -"of system events—then you'll have to customize the data those scripts send " -"to Zammad." +"Go to \"Admin > Security > Twitter > Third Party Applications > Twitter\" " +"Section." msgstr "" -"За већину корисника, :ref:`пример скрипти из водича кроз подешавање ` ће бити сасвим довољан. Али ако желите прецизнију контролу—на " -"пример, да отварате тикете високог и ниског приоритета за различите типове " -"системских догађаја—онда ћете морати да прилагодите податке које те скрипте " -"шаљу Zammad-у." +"Идите на одељак „Администрација > Безбедност > Апликације трећег лица > " +"Twitter“." -#: ../system/integrations/checkmk/api-reference.rst:15 +#: ../settings/security/third-party/twitter.rst:None +msgid "Admin > Security > Third Party Applications" +msgstr "Администрација > Безбедност > Апликације трећег лица" + +#: ../settings/security/third-party/twitter.rst:48 msgid "" -"This custom script will automatically set all tickets it creates to **high " -"priority** and **assign them to charlie@chrispresso.com**." +"Fill in the \"Twitter Key\" and the \"Twitter Secret\" and click the " +"\"Submit\" button." msgstr "" -"Ова прилагођена скрипта ће аутоматски поставити све тикете које отвара на " -"**високи приоритет** и **доделити их на charlie@chrispresso.com**." - -#: ../system/integrations/checkmk/api-reference.rst:32 -msgid "How Does it Work?" -msgstr "Како то уствари функционише?" +"Попуните „Twitter кључ“ и „Twitter шифра“ и кликните на дугме „Пошаљи“." -#: ../system/integrations/checkmk/api-reference.rst:34 +#: ../settings/security/third-party/twitter.rst:51 msgid "" -"There are two kinds of data you can pass to the API, both in the form of key-" -"value pairs:" +"Now you can link accounts via \"Avatar > Profile > Link Accounts\" or login " +"via Zammad login page." msgstr "" -"Постоје две врсте података које можете да проследите API-ју, обе у облику " -"парова кључ/вредност:" +"Сада можете повезати налоге преко „Аватар > Профил > Повезани налози” или се " +"пријавити преко Zammad странице за пријаву." -#: ../system/integrations/checkmk/api-reference.rst:44 -msgid "Checkmk parameters" -msgstr "Checkmk параметри" +#: ../settings/security/two-factor.rst:11 +msgid "Two-factor Authentication Methods" +msgstr "Методи двофакторске аутентификације" -#: ../system/integrations/checkmk/api-reference.rst:38 +#: ../settings/security/two-factor.rst:2 +msgid "Two-Factor Authentication" +msgstr "Двофакторска аутентификација" + +#: ../settings/security/two-factor.rst:4 msgid "" -"are required, and make up the **contents** of the resulting tickets/" -"articles. They also determine whether an event creates a new ticket or " -"updates/closes an existing one." +"Two-factor authentication (2FA) enhances the security of Zammad accounts by " +"adding an extra layer of verification beyond a password. It requires users " +"to provide two different types of authentication factors, typically " +"something they know (like a password) and something they possess (like a " +"mobile device or a security token), to ensure that only authorized " +"individuals can access the account." msgstr "" -"су обавезни и чине **садржај** примљених тикета/чланака. Они такође одређују " -"да ли догађај отвара нов тикет или освежава/затвара постојећи." +"Двофакторска аутентикација (2FA) појачава безбедност Zammad налога додавањем " +"додатног нивоа верификације поред лозинке. Захтева од корисника да обезбеде " +"два различита типа фактора аутентификације, обично нешто што знају (попут " +"лозинке) и нешто што поседују (као што је мобилни уређај или безбедносни " +"кључ), како би се осигурало да само овлашћене особе могу да приступе налогу." -#: ../system/integrations/checkmk/api-reference.rst:42 +#: ../settings/security/two-factor.rst:19 +msgid "Enable Recovery Codes" +msgstr "Укључивање шифри за опоравак" + +#: ../settings/security/two-factor.rst:21 msgid "" -"These are the only values used in the sample scripts. **Use them as-is**; " -"technically, they can be customized, but it's hard to imagine a good reason " -"for it." +"Recovery codes are one-time use security codes that can be used by the user " +"if they lose access to their other two-factor authentication methods. They " +"cannot be used on their own, they can only be activated if at least one two-" +"factor authentication method is enabled." msgstr "" -"Ово су једине вредности које се користе у примерима скрипти. **Користите их " -"баш овако**; технички, могу се прилагодити, али је тешко замислити добар " -"разлог за то." +"Шифре за опоравак су једнократни сигурносни кодови које корисник може " +"користити ако изгуби приступ својим другим методама двофакторске " +"аутентификације. Не могу се користити самостално, могуће их је укључити само " +"ако је укључен још бар један метод двофакторске аутентификације." -#: ../system/integrations/checkmk/api-reference.rst:52 -msgid "Ticket attributes" -msgstr "Атрибути тикета" +#: ../settings/security/two-factor.rst:None +msgid "Enable Recovery Codes Setting" +msgstr "Укључивање подешавања шифри за опоравак" -#: ../system/integrations/checkmk/api-reference.rst:47 +#: ../settings/security/two-factor.rst:30 msgid "" -"are optional, and can be used to **adjust settings** on newly created " -"tickets (*e.g.,* set the owner, group, priority, or state)." +"Recovery codes can only be used as a backup method. If enabled, they will be " +"automatically generated for the user once they set up their initial two-" +"factor authentication method." msgstr "" -"су опциони и могу се користити за **прилагођавање подешавања** за " -"новоотворене тикете (*нпр.* постављање власника, групе, приоритета или " -"стања)." +"Шифре за опоравак могу се користити само као резервни метод. Ако су " +"укључене, аутоматски ће се генерисати за корисника када подесе свој почетни " +"метод двофакторске аутентификације." -#: ../system/integrations/checkmk/api-reference.rst:50 +#: ../settings/security/two-factor.rst:34 msgid "" -"If you want to customize your Checkmk alert script, do it with these. Simply " -"add an extra “form” option for each one (``-F \"key=value\"``) to your " -"script's ``curl`` command line, as in the example above." +"The user will be asked to print out or save the generated recovery codes in " +"a safe place. Once used, a recovery code cannot be reused." msgstr "" -"Ако желите да прилагодите своју Checkmk скрипту упозорења, урадите то на " -"овај начин. Једноставно додајте опцију „form“ за сваку (``-F " -"\"кључ=вредност\"``) групу у командној ``curl`` линији ваше скрипте, као у " -"примеру изнад." - -#: ../system/integrations/checkmk/api-reference.rst:54 -msgid "💡 **It's just an API endpoint!**" -msgstr "💡 **То је само API путања!**" +"Од корисника ће бити затражено да одштампа или сачува генерисане шифре за " +"опоравак на безбедном месту. Једном употребљена, шифра за опоравак се не " +"може поново користити." -#: ../system/integrations/checkmk/api-reference.rst:56 +#: ../settings/security/two-factor.rst:37 msgid "" -"When using Checkmk integration, messages need to be formatted in a certain " -"way, but that *doesn't mean the messages actually have to come from Checkmk*." +"Users will also have an option to regenerate their recovery codes at any " +"time, which invalidates already existing recovery codes and provides them " +"with a list of fresh codes." msgstr "" -"Када користите Checkmk интеграцију, поруке морају бити форматиране на " -"одређени начин, али то *не значи да поруке заправо морају да долазе од " -"Checkmk*." +"Корисници ће такође имати опцију да регенеришу своје шифре за опоравак у " +"било ком тренутку, што поништава већ постојеће и пружа им листу свежих " +"кодова." -#: ../system/integrations/checkmk/api-reference.rst:59 +#: ../settings/security/two-factor.rst:41 msgid "" -"If you use another monitoring tool that's not officially supported by " -"Zammad, there's probably a way to make it work with your Checkmk callback " -"URL." +"After you enable this setting, when the user completes a setup of their " +"initial two-factor authentication method, they will be presented with a list " +"of recovery codes and instructed to save them for later use." msgstr "" -"Ако користите други алат за праћење који Zammad званично не подржава, " -"вероватно постоји начин да га натерате да ради са вашом Checkmk URL адресом " -"повратног позива." +"Након што укључите ово подешавање, када корисник заврши поставку свог " +"почетног метода двофакторске аутентификације, биће му представљена листа " +"шифри за опоравак и упутство да их сачува за каснију употребу." -#: ../system/integrations/checkmk/api-reference.rst:63 -msgid "Checkmk Parameters" -msgstr "Checkmk параметери" +#: ../settings/security/two-factor.rst:None +msgid "Recovery Codes Generation Modal Dialog" +msgstr "Модални дијалог за генерисање шифри за опоравак" -#: ../system/integrations/checkmk/api-reference.rst:65 +#: ../settings/security/two-factor.rst:50 +msgid "Enforce the Set Up of the Two-Factor Authentication" +msgstr "Захтевање поставке двофакторске аутентификације" + +#: ../settings/security/two-factor.rst:52 msgid "" -"When a notification is received, Zammad creates a new article containing the " -"details of the event that triggered it:" +"In case you wish to require your users to set up at least one two-factor " +"authentication method for their account, you can do this by selecting " +"specific user roles the requirement applies to in **Enforced for user " +"roles** setting. Of course you must have at least one two-factor " +"authentication method enabled for this setting to take effect." msgstr "" -"По примању упозорења, Zammad додаје нови чланак који садржи детаље догађаја " -"који га је покренуо:" +"У случају да желите да од својих корисника захтевате да за свој налог подесе " +"бар један метод двофакторске аутентификације, то можете урадити тако што " +"ћете изабрати одређене корисничке улоге на које се захтев примењује у " +"подешавању **Захтевано за корисничке улоге**. Наравно морате имати укључен " +"најмање један метход двофакторске аутентификације да би ово подешавање " +"ступило на снагу." -#: ../system/integrations/checkmk/api-reference.rst:None -msgid "Checkmk article body" -msgstr "Checkmk текст чланка" +#: ../settings/security/two-factor.rst:None +msgid "Enforced for User Roles Setting" +msgstr "Подешавање захтевано за корисничке улоге" -#: ../system/integrations/checkmk/api-reference.rst:72 +#: ../settings/security/two-factor.rst:62 msgid "" -"These details come from the fields listed below, which correspond to " -"parameters provided by Checkmk (``$NOTIFY_*``)." +"After you change this setting, if the user has one of the selected roles on " +"their account, they will be forced to set up the two-factor authentication " +"upon next sign in or application reload." msgstr "" -"Ови детаљи потичу из поља наведених у наставку, која одговарају параметрима " -"које обезбеђује Checkmk (``$NOTIFY_*``)." - -#: ../system/integrations/checkmk/api-reference.rst:75 -msgid "**Required fields are marked with an asterisk (\\*).**" -msgstr "**Обавезна поља су означена звездицом (\\*).**" - -#: ../system/integrations/checkmk/api-reference.rst:79 -msgid "event_id\\*" -msgstr "event_id\\*" +"Након што промените ово подешавање, ако корисник има једну од изабраних " +"улога на свом налогу, биће захтевано од њих да поставе двофакторску " +"аутентификацију приликом следећег пријављивања или поновног учитавања " +"апликације." -#: ../system/integrations/checkmk/api-reference.rst:78 +#: ../settings/security/two-factor.rst:66 msgid "" -"A unique ID for the system event. (``$NOTIFY_SERVICEPROBLEMID`` / " -"``$NOTIFY_HOSTPROBLEMID``)" +"A modal dialog with instructions will be shown, and they will not be able to " +"do any work before they set up at least one two-factor method." msgstr "" -"Јединствени ID за системски догађај. (``$NOTIFY_SERVICEPROBLEMID`` / " -"``$NOTIFY_HOSTPROBLEMID``)" +"Биће приказан модални дијалог са упутствима и корисник неће моћи да ради са " +"системом пре него што постави бар један метод двофакторске аутентификације." -#: ../system/integrations/checkmk/api-reference.rst:86 -msgid "host\\*" -msgstr "host\\*" +#: ../settings/security/two-factor.rst:None +msgid "Modal Dialog for Enforcing Two-Factor Authentication Set Up" +msgstr "Модални дијалог за захтевање поставке двофакторске аутентификације" -#: ../system/integrations/checkmk/api-reference.rst:82 +#: ../settings/security/two-factor.rst:74 +msgid "Reset Two-Factor Authentication for a Specific User" +msgstr "Поништавање двофакторске аутентификација за конкретног корисника" + +#: ../settings/security/two-factor.rst:76 msgid "" -"The hostname of the system that the event originated from. " -"(``$NOTIFY_HOSTNAME``)" -msgstr "Назив хоста система из којег је настао догађај. (``$NOTIFY_HOSTNAME``)" +"In case an user isn't able to login anymore because of an inaccessible " +"second factor, you can reset the user's 2FA method." +msgstr "" +"У случају да корисник више није у могућности да се пријави због " +"недоступности другог фактора, можете поништити кориснички метод двофакторске " +"аутентификације." -#: ../system/integrations/checkmk/api-reference.rst:85 +#: ../settings/security/two-factor.rst:79 msgid "" -"Used to determine if a new event belongs to an existing ticket. Also used in " -"the subject line of the resulting article (“ is ”)." +"To do this, go to the user management and search for the relevant user. " +"After you found the account, click the button in the action column and " +"select \"Manage Two-Factor Authentication\":" msgstr "" -"Користи се за одређивање да ли нови догађај припада постојећем тикету. " -"Такође се користи у предмету новонасталог чланка („ is ”)." +"Да бисте ово урадили, идите на уређивање корисника и претражите за " +"одговарајућег корисника. Након што пронађете налог, кликните на дугме у " +"колони радње и изаберите „Управљање двофакторском аутентификацијом”:" -#: ../system/integrations/checkmk/api-reference.rst:96 -msgid "service" -msgstr "service" +#: ../settings/security/two-factor.rst:None +msgid "Context menu in action column in user management" +msgstr "Контекстни мени у колони радње у екрану уређивања корисника" -#: ../system/integrations/checkmk/api-reference.rst:89 +#: ../settings/security/two-factor.rst:87 msgid "" -"The name of the service that the event originated from. " -"(``$NOTIFY_SERVICEDESC``)" -msgstr "Назив сервиса из кога је догађај настао. (``$NOTIFY_SERVICEDESC``)" +"After selecting this, you can see a dialog where you can either reset one " +"2FA method or reset all of the user's 2FA methods:" +msgstr "" +"По одабиру, добићете дијалог где можете поништити или један или све методе " +"двофакторске аутентификације:" -#: ../system/integrations/checkmk/api-reference.rst:92 -msgid "Used to determine if a new event belongs to an existing ticket." -msgstr "Користи се за одређивање да ли нови догађај припада постојећем тикету." +#: ../settings/security/two-factor.rst:None +msgid "Dialog for resetting user's 2FA method" +msgstr "Дијалог за поништавање корисничких метода двофакторске аутентификације" -#: ../system/integrations/checkmk/api-reference.rst:94 -#: ../system/integrations/checkmk/api-reference.rst:110 -msgid "Displayed as ``-`` when omitted." -msgstr "Приказује се као ``-`` када се изостави." +#: ../settings/security/two-factor.rst:94 +msgid "" +"Choose the fitting one, click on the corresponding \"Remove ...\" button and " +"confirm your action. The user now has to setup a new 2FA method, depending " +"on your 2FA configuration." +msgstr "" +"Изаберите одговарујућу опцију, кликните на дугме „Уклони” и потврдите своју " +"радњу. Корисник ће сада морати да постави нови метод двофакторске " +"аутентификације, у зависности од ваше конфигурације." -#: ../system/integrations/checkmk/api-reference.rst:104 -msgid "state\\*" -msgstr "state\\*" +#: ../settings/security/two-factor/authenticator-app.rst:2 +msgid "Authenticator App" +msgstr "Апликација за аутентификацију" -#: ../system/integrations/checkmk/api-reference.rst:99 +#: ../settings/security/two-factor/authenticator-app.rst:4 msgid "" -"The current state of the service or host in question. " -"(``$NOTIFY_SERVICESTATE`` / ``$NOTIFY_HOSTSTATE``)" +"The authenticator app method is a type of two-factor authentication that " +"uses a mobile application to generate one-time codes for account " +"verification. After setting up the authenticator app on their device, the " +"user links it to their Zammad account." msgstr "" -"Тренутно стање дотичног сервиса или хоста. (``$NOTIFY_SERVICESTATE`` / " -"``$NOTIFY_HOSTSTATE``)" +"Метод апликације за аутентификацију је врста двофакторске аутентификације " +"која користи мобилну апликацију за генерисање једнократних кодова за " +"верификацију налога. Након подешавања апликације за аутентификацију на свом " +"уређају, корисник је повезује са својим Zammad налогом." -#: ../system/integrations/checkmk/api-reference.rst:102 +#: ../settings/security/two-factor/authenticator-app.rst:12 msgid "" -"Used to detect when a ticket should be auto-closed (*i.e.,* on ``OK``/" -"``UP``). Also used in the subject line of the resulting article (“ is " -"”)." +"When logging in, the user is prompted to enter a time-sensitive code " +"generated by the app, in addition to their password. This code acts as the " +"second factor of authentication, providing an extra layer of security as it " +"changes periodically and is unique to the user's device." msgstr "" -"Користи се за откривање када би тикет требало да се аутоматски затвори (*тј." -"* на ``OK``/``UP``). Такође се користи у предмету новонасталог чланка " -"(„ is ”)." +"Приликом пријављивања, од корисника се тражи да унесе временски осетљив код " +"који генерише апликација, поред своје лозинке. Овај код се примењује као " +"други фактор аутентификације, пружајући додатни ниво заштите пошто се " +"периодично мења и јединствен је за уређај корисника." -#: ../system/integrations/checkmk/api-reference.rst:110 -msgid "text" -msgstr "text" +#: ../settings/security/two-factor/authenticator-app.rst:None +msgid "Security Code in Google Authenticator App" +msgstr "Сигурносни код у апликацији Google Authenticator" -#: ../system/integrations/checkmk/api-reference.rst:107 +#: ../settings/security/two-factor/authenticator-app.rst:22 msgid "" -"The output of the process that triggered the event. " -"(``$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" +"The app generates codes based on a shared secret key stored securely on both " +"the user's device and the server, ensuring a synchronized and secure " +"authentication process. The method of generating the codes is sometimes also " +"called TOTP (time-based one-time password)." msgstr "" -"Излазни подаци процеса који је покренуо догађај. " -"(``$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" +"Апликација генерише кодове на основу дељеног тајног кључа који је безбедно " +"ускладиштен и на корисниковом уређају и на серверу, обезбеђујући " +"синхронизован и сигуран процес аутентификације. Метода генерисања кодова се " +"понекад назива и TOTP (једнократна лозинка заснована на времену)." -#: ../system/integrations/checkmk/api-reference.rst:121 +#: ../settings/security/two-factor/authenticator-app.rst:28 +msgid "Enabling the Authenticator App Method" +msgstr "Укључивање метода апликације за аутентификацију" + +#: ../settings/security/two-factor/authenticator-app.rst:30 +#: ../settings/security/two-factor/security-keys.rst:28 +msgid "To enable the method, just toggle the switch on in the settings." +msgstr "Да бисте укључили метод, само притисните прекидач у подешавањима." + +#: ../settings/security/two-factor/authenticator-app.rst:None +msgid "Authenticator App Switch in Settings" +msgstr "Прекидач апликације за аутентификацију у подешавањима" + +#: ../settings/security/two-factor/authenticator-app.rst:36 msgid "" -"The Object Manager attribute panel displays built-in and custom\n" -"attribute names." +"Now the users will be able to set up this two-factor authentication method " +"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " +"Once they do, on next sign-in with password, they will be asked to provide " +"an additional security code generated by their mobile device." msgstr "" -"Панел управљања атрибутима објекта приказује уграђене и прилагођене\n" -"називе атрибута." +"Сада ће корисници моћи да подесе овај метод двофакторске аутентификације за " +"своје налоге преко „Аватар -> Профил -> Лозинка и аутентификација\". Када то " +"ураде, приликом следећег пријављивања путем лозинке, од њих ће се тражити да " +"приложе и додатни безбедносни код који генерише њихов мобилни уређај." -#: ../system/integrations/checkmk/api-reference.rst:121 -msgid "Find a complete list of ticket attributes in the Object Manager." -msgstr "Пронађите комплетну листу атрибута тикета у управљању објектима." +#: ../settings/security/two-factor/security-keys.rst:2 +msgid "Security Keys" +msgstr "Безбедносни кључеви" -#: ../system/integrations/checkmk/api-reference.rst:123 +#: ../settings/security/two-factor/security-keys.rst:4 msgid "" -"Ticket attributes are entirely optional, and can be used to customize the " -"tickets that Checkmk creates. (Note that these attributes will be ignored if " -"a new event belongs to an existing ticket.)" +"The security keys method is a type of a two-factor authentication that uses " +"Web Authentication API in the browser for verifying user's identity. The " +"user can register multiple hardware or software security keys with their " +"Zammad account and then they can use it during the sign-in process." msgstr "" -"Атрибути тикета су потпуно опциони и могу се користити за прилагођавање " -"тикета које Checkmk креира. (Имајте на уму да ће ови атрибути бити " -"занемарени ако нови догађај припада постојећем тикету.)" +"Метод безбедносних кључева је врста двофакторске аутентификације која " +"користи Web Authentication API у претраживачу за верификацију идентитета " +"корисника. Корисник може да региструје више хардверских или софтверских " +"безбедносних кључева са својим Zammad налогом, а затим га може користити " +"током процеса пријављивања." -#: ../system/integrations/checkmk/api-reference.rst:128 +#: ../settings/security/two-factor/security-keys.rst:12 msgid "" -"Why would you want to do this? Maybe you have only one IT guy, and all " -"system monitoring issues should be automatically assigned to him. Or, maybe " -"you're creating multiple notification rules so that database outages take " -"higher priority than disk space warnings." +"When logging in, the user is prompted to provide the same security key they " +"registered with their account, in addition to their password. This key acts " +"as the second factor of authentication, providing an extra layer of security." msgstr "" -"Зашто бисте желели ово да урадите? Можда имате само једног IT момка и сви " -"проблеми праћења система би требали бити аутоматски додељени баш њему. Или, " -"можда одређујете више правила за упозорења тако да прекиди у доступности " -"базе података имају већи приоритет од упозорења о преосталом простору на " -"диску." +"Приликом пријављивања, од корисника се тражи да приложи исти сигурносни кључ " +"који је регистровао са својим налогом, поред своје лозинке. Овај кључ се " +"примењује као други фактор аутентификације, пружајући додатни ниво " +"безбедности." -#: ../system/integrations/checkmk/api-reference.rst:135 -msgid "In most cases, you'll probably want to set one of the following:" +#: ../settings/security/two-factor/security-keys.rst:None +msgid "Security Key dialog in Safari on macOS" msgstr "" -"У већини случајева, вероватно ћете желети да подесите бар једно од следећег:" - -#: ../system/integrations/checkmk/api-reference.rst:137 -msgid "group" -msgstr "group" - -#: ../system/integrations/checkmk/api-reference.rst:139 -msgid "state" -msgstr "state" - -#: ../system/integrations/checkmk/api-reference.rst:140 -msgid "priority" -msgstr "priority" +"Дијалог за поставку безбедносног кључа у Safari претраживачу на macOS-у" -#: ../system/integrations/checkmk/api-reference.rst:142 +#: ../settings/security/two-factor/security-keys.rst:21 msgid "" -"but in practice, you can set almost any attribute, including :doc:`custom " -"ones you created through the Object Manager `." +"The type of the key can range from hardware USB sticks to passkeys stored in " +"a device of user's choice. Which type can be used depends on the browser " +"flavor and the platform of the user." msgstr "" -"али у пракси, можете подесити скоро све атрибуте, укључујући :doc:" -"`прилагођене атрибуте које сте додали преко панела за управљање објектима `." - -#: ../system/integrations/checkmk/api-reference.rst:145 -msgid "Please note that the following attributes are **not customizable**:" -msgstr "Имајте на уму да се следећи атрибути се **не могу прилагодити**:" - -#: ../system/integrations/checkmk/api-reference.rst:147 -msgid "title" -msgstr "title" - -#: ../system/integrations/checkmk/api-reference.rst:148 -msgid "id" -msgstr "id" - -#: ../system/integrations/checkmk/api-reference.rst:149 -msgid "ticket number" -msgstr "ticket number" - -#: ../system/integrations/checkmk/api-reference.rst:151 -msgid "created_by_id" -msgstr "created_by_id" +"Тип кључа може се креће од хардверских USB флешева до приступних кључева " +"ускладиштених у уређају по избору корисника. Који тип се може користити " +"зависи од врсте претраживача и платформе корисника." -#: ../system/integrations/checkmk/api-reference.rst:152 -msgid "updated_by_id" -msgstr "updated_by_id" +#: ../settings/security/two-factor/security-keys.rst:26 +msgid "Enabling the Security Keys Method" +msgstr "Укључивање метода безбедносних кључева" -#: ../system/integrations/checkmk/api-reference.rst:155 -msgid "Which Values Can Be Set?" -msgstr "Које вредности је могуће поставити?" +#: ../settings/security/two-factor/security-keys.rst:None +msgid "Security Keys Switch in Settings" +msgstr "Прекидач безбедносних кључева у подешавањима" -#: ../system/integrations/checkmk/api-reference.rst:157 -msgid "😵 **Invalid values → unpredictable behavior**" -msgstr "😵 **Неисправне вредности → непредвидљиво понашање**" +#: ../settings/security/two-factor/security-keys.rst:34 +msgid "" +"Now the users will be able to set up this two-factor authentication method " +"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " +"Once they do, on next sign-in with password, they will be asked to provide " +"the same security key they registered during the setup." +msgstr "" +"Сада ће корисници моћи да подесе овај метод двофакторске аутентификације за " +"своје налоге преко „Аватар -> Профил -> Лозинка и аутентификација\". Када то " +"ураде, приликом следећег пријављивања путем лозинке, од њих ће се тражити да " +"приложе исти безбедносни кључ који су регистровали прликом поставке." -#: ../system/integrations/checkmk/api-reference.rst:159 +#: ../settings/system/system-selfhosted.include.rst:3 msgid "" -"If you provide a value that Zammad doesn't understand (*e.g.,* ``-F " -"\"priority=high\"``), it's not always clear what will happen. In some cases, " -"a ticket will be created with the default values instead - but in others, it " -"may not be created at all!" +"Below settings are only available to self hosted users. In hosted " +"environments we're handling these settings for you to ensure service " +"stability." msgstr "" -"Ако наведете вредност коју Zammad не разуме (*нпр.* ``-F " -"\"priority=high\"``), није увек сасвим јасно шта ће се догодити. У неким " -"случајевима ће се уместо тога отворити тикет са подразумеваним вредностима — " -"али у другим, можда неће бити уопште отворен!" +"Подешавања у наставку су доступна само корисницима који хостују сами. У " +"хостованом окружењу ми рукујемо овим подешавањима за вас да бисмо обезбедили " +"стабилност сервиса." -#: ../system/integrations/checkmk/api-reference.rst:164 -msgid "So what values does Zammad understand, then? Well, it depends..." -msgstr "Дакле, које вредности Zammad разуме? Па, зависи..." +#: ../settings/system/base.rst:11 +msgid "Fully Qualified Domain Name" +msgstr "Квалификовани назив домена" -#: ../system/integrations/checkmk/api-reference.rst:168 -msgid "Use an email address or username:" -msgstr "Користите имејл адресу или корисничко име:" +#: ../settings/system/base.rst:7 +msgid "The URL of your Zammad installation." +msgstr "URL ваше инсталације Zammad-а." -#: ../system/integrations/checkmk/api-reference.rst:190 -msgid "group & priority" -msgstr "group & priority" +#: ../settings/system/base.rst:9 ../settings/system/base.rst:17 +#, fuzzy +#| msgid "" +#| "This setting is used within :doc:`/system/variables` and notifications." +msgid "This setting is used within :doc:`/misc/variables` and notifications." +msgstr "" +"Ово подешавање се користи у оквиру :doc:`/system/variables` и обавештења." -#: ../system/integrations/checkmk/api-reference.rst:175 -msgid "Refer to the dropdown menus in the ticket pane:" -msgstr "Погледајте падајуће меније у панелу тикета:" +#: ../settings/system/system-base.include.rst:1 +msgid "It is automatically set by the *Getting Started wizard*." +msgstr "Аутоматски се поставља приликом *почетне поставке система*." -#: ../system/integrations/checkmk/api-reference.rst:0 -msgid "See possible values for certain attributes in the ticket pane." -msgstr "Погледајте могуће вредности за одређене атрибуте у панелу тикета." +#: ../settings/system/system-base.include.rst:5 +msgid "Changing this setting also changes callback URLs for your channels etc." +msgstr "" +"Промена овог подешавања такође мења URL адресе за повратне позиве ваших " +"канала итд." -#: ../system/integrations/checkmk/api-reference.rst:187 -msgid "🙅 **Ticket state CANNOT be set this way!**" -msgstr "🙅 **Стање тикета НЕ МОЖЕ да се подеси на овај начин!**" +#: ../settings/system/system-base.include.rst:6 +msgid "This setting can have negative affects on being able to login." +msgstr "Ово подешавање може негативно утицати на могућност пријављивања." -#: ../system/integrations/checkmk/api-reference.rst:189 +#: ../settings/system/base.rst:19 +msgid "HTTP type" +msgstr "HTTP протокол" + +#: ../settings/system/base.rst:14 msgid "" -"Why? Because ``-F \"state=...\"`` is already used :ref:`as a Checkmk " -"parameter `." +"The HTTP type tells your installation how your clients connect. This is " +"relevant for authentication and cookie security." msgstr "" -"Зашто? Зато што се ``-F \"state=...\"`` већ користи :ref:`као Checkmk " -"параметар `." +"HTTP протокол одређује како се ваши клијенти повезују са вашом инсталацијом. " +"Ово је релевантно за аутентификацију и безбедност." -#: ../system/integrations/checkmk/api-reference.rst:222 -msgid "Everything Else" -msgstr "Све остало" +#: ../settings/system/base.rst:31 +msgid "SystemID" +msgstr "SystemID" -#: ../system/integrations/checkmk/api-reference.rst:193 +#: ../settings/system/base.rst:22 msgid "" -"To set any other attributes, it helps to know your way around the :docs:" -"`rails console `. Valid values are those that you can " -"set with a string:" +"This ID is being used within your ticket number. In case you're " +"communicating with another ticket system with similar ticket number schemes " +"this ID greatly reduces the risk of false follow ups." msgstr "" -"Да бисте подесили било које друге атрибуте, помоћи ће вам да знате да се " -"снађете у :docs:`rails конзоли `. Важеће вредности су " -"оне које можете поставити текстуалним низом:" - -#: ../system/integrations/checkmk/api-reference.rst:218 -msgid "These values can then be passed directly to the API:" -msgstr "Ове вредности се затим могу пренети директно у API:" - -#: ../system/integrations/checkmk/index.rst:16 -msgid "How does it work?" -msgstr "Како то уствари функционише?" +"Овај ID се користи у оквиру броја вашег тикета. У случају да комуницирате са " +"другим системом тикета са сличним шемама броја тикета, овај ID у великој " +"мери смањује ризик од лажних наставака." -#: ../system/integrations/checkmk/index.rst:2 -msgid "Checkmk" -msgstr "Checkmk" +#: ../settings/system/base.rst:26 +msgid "" +"The SystemID is randomly selected upon installation of Zammad (``1-99``)." +msgstr "SystemID се насумично бира приликом инсталације Zammad-а (``1-99``)." -#: ../system/integrations/checkmk/index.rst:4 +#: ../settings/system/base.rst:30 msgid "" -"`Checkmk `_ is a powerful IT monitoring tool that can " -"send real-time status alerts to Zammad via email or REST API. Set these " -"alerts up in Checkmk, and Zammad will automatically create, update, and " -"close tickets based on the health of your system:" +"**Do not** change this setting in a productive system! Your Zammad " +"installation may no longer recognize old ticket number based follow ups upon " +"change!" msgstr "" -"`Checkmk `_ је моћан алат за IT праћење који може да " -"шаље обавештења о статусу Zammad-а у реалном времену путем имејла или REST " -"API. Подесите ова упозорења у Checkmk и Zammad ће аутоматски отварати, " -"освежавати и затварати тикете на основу здравља вашег система:" - -#: ../system/integrations/checkmk/index.rst:14 -msgid "Screenshot of ticket created by Checkmk notifications" -msgstr "Снимак екрана тикета отвореног на основу Checkmk упозорења" +"**Не** мењајте ово подешавање на систему у продукцији! Ваша Zammad " +"инсталација можда више неће препознати старе наставке на основу броја тикета " +"након измене!" -#: ../system/integrations/checkmk/index.rst:14 -msgid "Multiple alerts, same ticket." -msgstr "Више упозорења, исти тикет." +#: ../settings/system/frontend.rst:2 +msgid "Frontend" +msgstr "Интерфејс" -#: ../system/integrations/checkmk/setup-guide.rst:2 -msgid "Setup Guide" -msgstr "Водич кроз подешавање" +#: ../settings/system/frontend.rst:22 +msgid "Core Workflow Ajax Mode" +msgstr "Ajax режим радног тока" -#: ../system/integrations/checkmk/setup-guide.rst:4 +#: ../settings/system/frontend.rst:6 msgid "" -"Whenever the Checkmk integration is enabled, Zammad listens for messages on " -"its API and over email. As long as those messages follow the required " -"format, Zammad will create new tickets (or find and update existing ones) " -"based on the message contents." +"This setting allows administrators to enforce :doc:`/system/core-workflows` " +"to use Ajax-Calls instead of web sockets. You'll usually only need this if " +"you experience serious issues as noted below." msgstr "" -"Кад год је Checkmk интеграција укључена, Zammad ослушкује захтеве на свом " -"API-ју и путем имејла. Све док те поруке прате очекивани формат, Zammad ће " -"отварати нове тикете (или пронаћи и освежити постојеће) на основу садржаја " -"поруке." +"Ово подешавање омогућава администраторима да наметну :doc:`радним токовима ` да користе Ajax позиве уместо web socket-а. Ово ће " +"вам бити неопходно само ако имате озбиљне проблеме као што је наведено у " +"наставку." -#: ../system/integrations/checkmk/setup-guide.rst:10 +#: ../settings/system/frontend.rst:10 +msgid "**🤓 Possible (technical) reasons**" +msgstr "**🤓 Могући (технички) разлози**" + +#: ../settings/system/frontend.rst:12 msgid "" -"That means that “setting up Checkmk integration” is simply a matter of " -"**adding configuration to your Checkmk site**: telling it when to send these " -"messages and what to say. To do that, you'll need to create a new " -"**notification rule** (see `Checkmk's official docs `_ for help with that)." +"In some cases, your network structure (e.g. firewalls, proxies) may " +"disconnect long web socket connections. This leads to select fields staying " +"empty (e.g. owner selection *after* selecting your group) or fields not " +"shown / hidden (e.g. when switching to or from pending states, the \"pending " +"till\" field not showing / hiding)." msgstr "" -"То значи да је „подешавање Checkmk интеграције“ једноставно питање " -"**додавања конфигурације вашој Checkmk инстанци**: да јој кажете када да " -"пошаље ове поруке и шта у њима да каже. Да бисте то урадили, мораћете да " -"дефинишете нови **notification rule** (погледајте `Checkmk званичну " -"документацију `_ за додатну " -"помоћ)." +"У неким случајевима, ваша мрежна инфраструктура (нпр. firewall, прокси " +"сервери) може да прекине дуге конекције путем web socket-а. Ово доводи до " +"тога да одабрана поља остају празна (нпр. избор власника *након* одабира " +"ваше групе) или поља која нису приказана/сакривена (нпр. када се прелази у " +"или из стања на чекању, поље „На чекању до“ се не приказује/сакрива)." -#: ../system/integrations/checkmk/setup-guide.rst:17 +#: ../settings/system/frontend.rst:18 msgid "" -"As part of this new rule, you'll have to choose a **notification method** " -"(*i.e.,* a script to execute whenever the rule is triggered). This script " -"will be written by you (samples below), and contain the logic for sending " -"API/email messages to Zammad:" +"Please keep in mind that the Ajax fallback may cause serious pressure on " +"your application server. If you have the choice stick to web sockets." msgstr "" -"Као део овог новог правила, мораћете да изаберете **notification method** " -"(*тј.* скрипту која ће се извршити кад год се правило покрене). Ову скрипту " -"ћете доставити ви (примери су испод) и она ће садржати логику за слање API/" -"имејл порука Zammad-у:" +"Имајте на уму да Ajax режим може изазвати озбиљан притисак на апликативни " +"сервер. Ако имате избор, држите се web socket-а." -#: ../system/integrations/checkmk/setup-guide.rst:26 -msgid "Checkmk \"New Rule\" dialog" -msgstr "Checkmk дијалог за „New Rule“" +#: ../settings/system/frontend.rst:22 +msgid "Default: ``no`` (inactive)" +msgstr "Подразумевано: ``не`` (искључено)" -#: ../system/integrations/checkmk/setup-guide.rst:26 +#: ../settings/system/frontend.rst:53 +msgid "Show calendar weeks in the picker of date/datetime fields" +msgstr "Приказ календарске недеље у бирачу поља датума и времена" + +#: ../settings/system/frontend.rst:25 msgid "" -"Find your custom scripts in the Checkmk WATO under **Notifications > New " -"Rule > Notification Method**." +"With this setting you can instruct Zammad to provide week number display " +"globally for all users. Calendar with week number display are usually used " +"in business sectors and may not be relevant for everyone." msgstr "" -"Пронађите своје прилагођене скрипте у Checkmk WATO под **Notifications > New " -"Rule > Notification Method**." +"Са овим подешавањем можете наложити Zammad-у да обезбеди приказ броја недеље " +"на глобалном нивоу за све кориснике. Календар са приказом броја седмица се " +"обично користи у пословним секторима и можда није релевантан за све." -#: ../system/integrations/checkmk/setup-guide.rst:29 +#: ../settings/system/frontend.rst:29 msgid "" -"Once you're done setting up your new rule, you're all set! New tickets " -"should start coming in and auto-updating any time your rule is triggered." +"This setting affects *all areas* - you'll also see week numbers in the admin " +"panel for e.g. triggers and macros." msgstr "" -"Када завршите са подешавањем новог правила, све је спремно! Нови тикети би " -"требало да почну да стижу и аутоматски се освежавају сваки пут када се ваше " -"правило окине." +"Ово подешавање утиче на *све области* - такође ћете видети бројеве недеља у " +"административном панелу за нпр. окидаче и макрои." -#: ../system/integrations/checkmk/setup-guide.rst:33 -msgid "" -"(If you need help troubleshooting, be sure to check the :ref:`checkmk-recent-" -"logs`.)" +#: ../settings/system/frontend.rst:32 +msgid "Default: ``no`` (not shown)" +msgstr "Подразумевано: ``не`` (није приказано)" + +#: ../settings/system/frontend.rst:53 +msgid "Here's the difference:" +msgstr "Ево разлике:" + +#: ../settings/system/frontend.rst:0 +msgid "Screenshot showing Zammad's date picker (in the default way)" msgstr "" -"(Ако вам је потребна помоћ у решавању проблема, обавезно проверите :ref:" -"`checkmk-recent-logs`.)" +"Снимак екрана који приказује Zammad-ов бирач датума (на подразумевани начин)" -#: ../system/integrations/checkmk/setup-guide.rst:38 -msgid "API Alerts" -msgstr "API упозорења" +#: ../settings/system/frontend.rst:41 +msgid "Set to ``no``" +msgstr "Постављено на ``не``" -#: ../system/integrations/checkmk/setup-guide.rst:40 +#: ../settings/system/frontend.rst:0 msgid "" -"To add these scripts in the Checkmk WATO, copy them into your Checkmk " -"installation directory and make them executable. (Be sure to replace the " -"``zammad.example.com`` callback URL with the one found in your admin panel.)" +"Screenshot showing Zammad's date picker with\n" +"week numbers enabled" msgstr "" -"Да бисте додали ове скрипте у Checkmk WATO, копирајте их у свој Checkmk " -"инсталациони директоријум и учините их извршним. (Обавезно замените ``zammad." -"example.com`` URL адресу повратног позива оном која се налази у вашем " -"администраторском панелу.)" +"Снимак екрана који приказује Zammad-ов бирач датума са\n" +"укљученим бројевима недеља" -#: ../system/integrations/checkmk/setup-guide.rst:60 -msgid "Service notification" -msgstr "Сервисна упозорења" +#: ../settings/system/frontend.rst:50 +msgid "Set to ``yes``" +msgstr "Постављено на ``да``" -#: ../system/integrations/checkmk/setup-guide.rst:46 +#: ../settings/system/index.rst:4 msgid "" -"For updates on the status of the software running on your server (*e.g.,* " -"postgres)." +"For your overview we split each tab within system settings into its own page:" msgstr "" -"За свежавање статуса софтвера који ради на вашем серверу (*нпр.* postgres)." +"За бољи преглед поделили смо сваки језичак у системским подешавањима на " +"посебну страницу:" -#: ../system/integrations/checkmk/setup-guide.rst:75 -msgid "Host notification" -msgstr "Упозорења о серверу" +#: ../settings/system/index.rst:16 +msgid "Console Based Settings" +msgstr "Подешавања путем конзоле" -#: ../system/integrations/checkmk/setup-guide.rst:63 -msgid "For updates on the status of the server itself." -msgstr "За освежавање статуса самог сервера." +#: ../settings/system/index.rst:18 +msgid "" +"There's some console based settings we didn't put into the UI. However, you " +"may find them helpful - you can find them in our :docs:`hidden settings ` section." +msgstr "" +"Постоје нека подешавања могућа само путем конзоле која нисмо ставили у " +"кориснички интерфејс. Међутим, можда вам могу бити од помоћи - можете их " +"пронаћи у нашем одељку за :docs:`скривена подешавања `." -#: ../system/integrations/checkmk/setup-guide.rst:77 -msgid "🤔 **What's with all the env vars?**" -msgstr "🤔 **Чему служе све ове променљиве окружења?**" +#: ../settings/system/network.rst:2 +msgid "Network" +msgstr "Мрежа" -#: ../system/integrations/checkmk/setup-guide.rst:79 +#: ../settings/system/network.rst:8 msgid "" -"Whenever Checkmk runs these scripts, it needs to provide some information " -"about the event that triggered the notification. This information is passed " -"in the form of these ``$NOTIFY_*`` environment variables." +"The proxy settings can only be saved after successfully testing the proxy " +"connection." msgstr "" -"Кад год Checkmk покрене ове скрипте, мора да пружи неке информације о " -"догађају који је окинуо упозорење. Ове информације се прослеђују у облику " -"ових ``$NOTIFY_*`` променљивих из окружења." +"Подешавања проксија могу се сачувати само након успешног тестирања прокси " +"конекције." -#: ../system/integrations/checkmk/setup-guide.rst:85 +#: ../settings/system/network.rst:15 +msgid "Proxy Address." +msgstr "Прокси адреса" + +#: ../settings/system/network.rst:12 msgid "" -"You can specify additional parameters to pass to the script when you're " -"setting up your notification rule, but the ones you see here are all " -"provided by default." +"Allows you to provide a proxy server if needed. This is relevant for network " +"communication by Zammad." msgstr "" -"Можете да наведете додатне параметре које ћете проследити скрипти када " -"прилагођавате своје правило упозорења, али они које видите овде су " -"подразумевано обезбеђени." +"Омогућава вам да подесите прокси сервер ако је потребно. Ово је релевантно " +"за мрежну комуникацију од стране Zammad-а." -#: ../system/integrations/checkmk/setup-guide.rst:90 -msgid "Email Alerts" -msgstr "Имејл упозорења" +#: ../settings/system/network.rst:15 +msgid "It **does not** affect the update process or Elasticsearch." +msgstr "Ово **не** утиче на процес освежавања или Elasticsearch." -#: ../system/integrations/checkmk/setup-guide.rst:94 +#: ../settings/system/network.rst:18 +msgid "Username for proxy connection." +msgstr "Корисничко име за прокси конекцију." + +#: ../settings/system/network.rst:18 msgid "" -"🐞 **There are known bugs** in Zammad's processing of email from Checkmk. " -"This section will be completed once they have been resolved. (Learn more at " -"GitHub issues `#2377 `_ & " -"`#2180 `_.)" +"If your proxy server requires authentication, provide the username here." msgstr "" -"🐞 **Постоје познате грешке** у Zammad-овој обради Checkmk имејл порука. " -"Овај одељак ће бити комплетиран када буду решене. (Сазнајте више у GitHub " -"извештајима `#2377 `_ и `#2180 " -"`_.)" +"Ако ваш прокси сервер захтева аутентификацију, овде унесите корисничко име." -#: ../system/integrations/checkmk/setup-guide.rst:100 -msgid "In the meantime, we encourage you to set up API alerts instead." -msgstr "" -"У међувремену, препоручујемо вам да уместо тога подесите API упозорења." +#: ../settings/system/network.rst:21 +msgid "Password for proxy connection." +msgstr "Лозинка за прокси конекцију." -#: ../system/integrations/clearbit.rst:2 -msgid "Clearbit" -msgstr "Clearbit" +#: ../settings/system/network.rst:21 +msgid "" +"If your proxy server requires authentication, provide the password here." +msgstr "Ако ваш прокси сервер захтева аутентификацију, овде унесите лозинку." -#: ../system/integrations/clearbit.rst:4 +#: ../settings/system/network.rst:26 +msgid "No proxy for the following hosts." +msgstr "Без проксија за следеће сервере." + +#: ../settings/system/network.rst:24 msgid "" -"With our Clearbit integration, you can easily enrich the information " -"provided by Zammad. If the customers or agents email address is known to " -"Clearbit, it will share all information it has regarding the user with " -"Zammad. Those information can include the following:" +"Exception list for hosts you can't or don't want to reach via proxy server." msgstr "" -"Уз нашу Clearbit интеграцију, лако можете обогатити информације које пружа " -"Zammad. Ако је имејл адреса клијената или оператера позната Clearbit " -"сервису, он ће поделити све информације које има у вези са корисником са " -"Zammad-ом. Те информације могу укључивати следеће:" +"Листа изузетака за хостове којима не можете или не желите да приступите " +"преко прокси сервера." -#: ../system/integrations/clearbit.rst:9 -msgid "Avatar" -msgstr "Аватар" +#: ../settings/system/network.rst:27 +msgid "Default: ``localhost,127.0.0.0,::1``" +msgstr "Подразумевано: ``localhost,127.0.0.0,::1``" -#: ../system/integrations/clearbit.rst:10 -msgid "Address information" -msgstr "Информације о адреси" +#: ../settings/system/services.rst:2 +msgid "Services" +msgstr "Услуге" -#: ../system/integrations/clearbit.rst:11 -msgid "Website information" -msgstr "Информације о сајту" +#: ../settings/system/services.rst:10 +msgid "Image Service" +msgstr "Услуга за слике" -#: ../system/integrations/clearbit.rst:12 -msgid "A BIO (as Note by default)" -msgstr "BIO (подразумевано као напомена)" +#: ../settings/system/services.rst:5 +msgid "Defines the backend for user and organization image lookups." +msgstr "Одређује позадински модул за тражење сличица корисника и организација." -#: ../system/integrations/clearbit.rst:14 -msgid "" -"If needed, you can add further custom objects and add mappings to them, so " -"the Clearbit information can be filled within the database. In general you " -"can get any information from Clearbit, as long as you have a mapping to an " -"Zammad object." -msgstr "" -"Ако је потребно, можете додати додатне прилагођене објекте и додати им " -"мапирања, тако да се Clearbit информације могу снимити унутар базе података. " -"Генерално говорећи, можете добити било коју информацију од Clearbit-а, све " -"док имате мапирање на одговарајући Zammad објекат." +#: ../settings/system/services.rst:7 +msgid "Default: ``Zammad Image Service`` (active)" +msgstr "Подразумевано: ``Zammad сервис за слике`` (укључено)" -#: ../system/integrations/clearbit.rst:21 +#: ../settings/system/services.rst:9 msgid "" -"Clearbit does have a mapping of fields like LDAP and Exchange have, but does " -"not \"win\" against Zammad information. This means that if you have e.g. the " -"last name field filled in already and Clearbit has other information on " -"that, it will not be updated." +"Make sure your on premise installation has ``HTTPS`` access to ``images." +"zammad.com``." msgstr "" -"Clearbit поседује мапирање поља као што то раде LDAP и Exchange, али не " -"\"побеђује\" у сукобу са Zammad подацима. То значи да ако имате нпр. поље за " -"презиме је већ попуњено и Clearbit има друге информације о томе, поље неће " -"бити освежено." +"Проверите да ваша локална инстанца има ``HTTPS`` приступ ``images.zammad." +"com``." -#: ../system/integrations/clearbit.rst:26 +#: ../settings/system/services.rst:18 +msgid "Geo Calendar Service" +msgstr "Услуга географског календара" + +#: ../settings/system/services.rst:13 msgid "" -"However: If let's say the last name has been set by Clearbit and Zammad " -"notices that the last name on the Clearbit source has changed, Zammad will " -"also update this value." +"Defines the backend for geo calendar lookups. Used for initial calendar " +"setup." msgstr "" -"Међутим: ако је рецимо презиме подесио Clearbit и Zammad примети да се " -"презиме на Clearbit-у променило, Zammad ће такође освежити своју вредност." +"Одређује позадински модул за географско тражење календара. Користи се за " +"иницијалан одабир календара." -#: ../system/integrations/clearbit.rst:33 +#: ../settings/system/services.rst:16 +msgid "Default: ``Zammad GeoCalendar Service`` (active)" +msgstr "Подразумевано: ``Zammad GeoCalendar сервис`` (укључено)" + +#: ../settings/system/services.include.rst:2 msgid "" -"The configuration of Clearbit is really easy and done fast! Just login to " -"your Clearbit-Account, go to \"API\" and copy the secret-API-Key." +"Make sure your on premise installation has ``HTTPS`` access to ``geo.zammad." +"com``." msgstr "" -"Подешавање Clearbit-а је заиста једноставно и брзо! Само се пријавите на " -"свој Clearbit налог, идите на „API” и копирајте тајни API кључ." +"Проверите да ваша локална инстанца има ``HTTPS`` приступ ``geo.zammad.com``." -#: ../system/integrations/clearbit.rst:38 -msgid "" -"Now change to your Zammad instance, go to Integrations (System) -> Clearbit " -"in the admin panel. Paste your API-Key into the API-Key-Field and decide if " -"Zammad should create unknown Organizations automatically, if the user does " -"not have one yet (and Clearbit knows it). The shared option decides if the " -"new organizations Zammad creates with Clearbit should be shared ones." -msgstr "" -"Сада пређите на своју Zammad инстанцу, идите на Интеграције (Систем) -> " -"Clearbit у панелу администратора. Налепите свој API кључ у одговарајуће поље " -"и одлучите да ли Zammad треба аутоматски да додаје непознате организације, " -"ако их корисник још увек нема (а Clearbit зна за њих). Опција заједничке " -"организације одлучује да ли нове организације које Zammad додаје преко " -"Clearbit треба да буду дељене међу члановима исте организације." +#: ../settings/system/services.rst:26 +msgid "Geo IP Service" +msgstr "Услуга географског IP" -#: ../system/integrations/clearbit.rst:47 +#: ../settings/system/services.rst:21 msgid "" -"If you're unsure what option to choose, better stick with \"no\". You can " -"also learn more about :doc:`/manage/organizations/index`." +"Defines the backend for geo IP lookups. Shows also location of an IP address " +"if an IP address is shown." msgstr "" -"Ако нисте сигурни коју опцију да одаберете, боље се држите „не”. Такође " -"можете сазнати више о организацијама :doc:`овде `." +"Дефинише позадински модул за географске IP упите. Приказује и локацију IP " +"адресе ако је IP адреса приказана." -#: ../system/integrations/clearbit.rst:52 -msgid "" -"The Mapping option works similar to the mapping within the Exchange and LDAP " -"sync. You can add further mappings for e.g. custom fields if you need more " -"information that Clearbit can provide." -msgstr "" -"Опција мапирања функционише слично мапирању унутар Exchange и LDAP " -"синхронизације. Можете додати још мапирања за нпр. прилагођена поља ако вам " -"треба више информација које Clearbit може да пружи." +#: ../settings/system/services.rst:24 +msgid "Default: ``Zammad GeoIP Service`` (active)" +msgstr "Подразумевано: ``Zammad GeoIP сервис`` (укључено)" -#: ../system/integrations/clearbit.rst:58 +#: ../settings/system/services.rst:32 +msgid "Geo Location Service" +msgstr "Услуга географске локације" + +#: ../settings/system/services.rst:29 msgid "" -"If you want to add more Clearbit fields and want to learn more about " -"available fields on their API, you can take a look at their `API " -"documentation `_." +"Defines the backend for geo location lookups to store geo locations for " +"addresses." msgstr "" -"Ако желите да додате још Clearbit пољa и желите да сазнате више о доступним " -"пољима на њиховом API-ју, можете погледати и њихову `API документацију " -"`_." +"Одређује позадински модул за географско тражење локација ради чувања " +"географских локација адреса." -#: ../system/integrations/clearbit.rst:62 +#: ../settings/system/services.rst:32 msgid "" -"If you're happy with the above chosen Settings and your mapping, just save " -"the changes and enable Clearbit integration. Zammad will now start polling " -"the Clearbit API as users contact you." +"Default: ``OpenStreetMap (ODbL 1.0, http://osm.org/copyright)`` (active)" msgstr "" -"Ако сте задовољни са горе одабраним подешавањима и вашим мапирањем, само " -"сачувајте промене и укључите Clearbit интеграцију. Zammad ће сада почети да " -"испитује Clearbit API чим вас корисници контактирају." +"Подразумевано: ``OpenStreetMap (ODbL 1.0, http://osm.org/copyright)`` " +"(укључено)" -#: ../system/integrations/clearbit.rst:68 +#: ../settings/system/services.rst:36 msgid "" -"Zammad does not synchronize with Clearbit on a regular basis, but on demand " -"if needed. This saves API calls." +"You can find a detailed privacy information on what we store for how long on " +"our :docs:`Privacy Appendix ` inside of our System " +"Documentation." msgstr "" -"Zammad се не синхронизује са Clearbit-ом редовно, већ на захтев ако је " -"потребно. Ово понашање штеди у броју API позива." +"Детаљне информације о приватности података и о томе шта чувамо и колико дуго " +"можете пронаћи у нашем :docs:`додатку о приватности ` унутар наше системске документације." -#: ../system/integrations/clearbit.rst:73 +#: ../settings/system/storage.rst:2 +msgid "Storage" +msgstr "Складиштење" + +#: ../settings/system/storage.rst:6 msgid "" -"Below the Settings and Mappings, you'll find our Integration log. You can " -"see what requests Zammad sent to Clearbit and also the APIs Response." +"Here you can define where Zammad stores attachments for tickets and the " +"knowledge base. By default, we're writing to the ``Database`` - you can " +"switch to ``Filesystem`` or ``Simple Storage (S3)`` at any time. In this " +"case please have a look on the following instructions." msgstr "" -"Испод подешавања и мапирања, наћи ћете нашу евиденцију захтева. Можете " -"видети које је захтеве Zammad послао Clearbit-у, као и одговоре преко API-ја." +"Овде можете одредити где Zammad складишти прилоге тикета и базе знања. " +"Подразумевано снима се у ``Базу података`` - можете да пређете на ``Систем " +"датотека`` или ``Simple Storage (S3)`` у било ком тренутку. У овом случају, " +"погледајте испод за упутство." -#: ../system/integrations/clearbit.rst:78 +#: ../settings/system/storage.rst:11 msgid "" -"By the way, you can also view the API log on the Clearbit website - the " -"information seen is basically the same." +"If you have a busy Zammad instance, we strongly encourage you to use " +"filesystem storage instead of \"Database\". This will greatly improve system " +"performance (de-crease database load and size)." msgstr "" -"Узгред, можете погледати и API евиденцију на Clearbit сајту - информације " -"које су доступне су у основи исте." +"Уколико имате Zammad инстанцу под већим оптерећењем, топло препоручујемо да " +"користите складиштење путем система датотека уместо „базе података”. Ово ће " +"убрзати перформансе система (и смањити оптерећење и величину базе података)." -#: ../system/integrations/clearbit.rst:84 -msgid "Example When Adding a User" -msgstr "Пример приликом додавања корисника" +#: ../settings/system/storage.rst:19 +msgid "Database" +msgstr "База података" -#: ../system/integrations/clearbit.rst:86 +#: ../settings/system/storage.rst:17 msgid "" -"To show you how fast information is added, we added a small Screencast " -"below. This shows the creation of the User Alex from Clearbit. As we already " -"set the last name of Alex to \"X\", Zammad did not update it. What Zammad " -"did was to add further information it received from Clearbit." +"This is the default storage method. The attachments are stored directly in " +"the database. If your Zammad instance grows, we recommend one of the other " +"methods to maintain performance." msgstr "" -"Да бисмо вам показали колико брзо се приказују информације, додали смо мали " -"снимак екрана испод. Ово показује додавање корисника Alex путем Clearbit-а. " -"Пошто смо већ поставили презиме Alex на „X“, Zammad га није освежио. Оно што " -"је Zammad урадио је да је додао додатне информације које је добио од " -"Clearbit-а." +"Ово је подразумевани метод складиштења. Прилоги се чувају директно у бази " +"података. Ако ваша Zammad инстанца расте, препоручујемо прелазак на други " +"метод да бисте очували перформансе." -#: ../system/integrations/cti/generic.rst:2 -msgid "CTI (generic)" -msgstr "CTI (генерички)" +#: ../settings/system/storage.rst:38 +msgid "Filesystem" +msgstr "Систем датотека" -#: ../system/integrations/cti/includes/introduction.include.rst:1 +#: ../settings/system/storage.rst:22 msgid "" -"This integration enables Zammad to provide a caller log to your agents. With " -"this your agents can greet your customers by their name and are supported by " -"Zammad with automatically opening a new ticket dialog or the user profile." +"This storage method is recommended for all Zammad instances, especially for " +"those with a higher load. If you choose filesystem, your files are written " +"to ``/opt/zammad/storage/``." msgstr "" -"Ова интеграција омогућава Zammad-у да обезбеди евиденцију позива вашим " -"оператерима. Са њом ваши оператери могу поздравити ваше клијенте њиховим " -"именом, а Zammad им обезбеђује и аутоматски приказ дијалога новог тикета или " -"корисничког профила." +"Овај метод складиштења је препоручен за све Zammad инстанце, поготову за оне " +"са већим оптерећењем. Ако сте изабрали метод датотека, ваше датотеке се " +"снимају у ``/opt/zammad/storage/``." -#: ../system/integrations/cti/includes/introduction.include.rst:6 +#: ../settings/system/storage.rst:26 msgid "" -"Click the toggle next to the heading to activate or deactivate this " -"integration." +"Moving attachments from \"Database\" to \"Filesystem\" can be run during " +"production use. However, you should consider your framework conditions (e.g. " +"bandwidth, system load in production) to define the right moment." msgstr "" -"Кликните на дугме поред наслова да бисте укључили или искључили ову " -"интеграцију." +"Премештање прилога из „базе података” у „систем датотека” може се покренути " +"чак и на систему у продукцији. Међутим, треба имати на уму ваше услове " +"система (нпр. брзину магистрале, оптерећење система) да бисте одредили прави " +"тренутак за извршавање." -#: ../system/integrations/cti/includes/introduction.include.rst:9 -msgid "" -"If you want to learn more on how your agents can use this function, please " -"refer the :user-docs:`user documentation `." -msgstr "" -"Ако желите да сазнате више о томе како ваши оператери могу да користе ову " -"функцију, погледајте :user-docs:`корисничку документацију `." +#: ../settings/system/storage.rst:32 +msgid "**You noticed slow updates of Zammad?**" +msgstr "**Приметили сте спор одзив у Zammad-у?**" -#: ../system/integrations/cti/includes/introduction.include.rst:14 +#: ../settings/system/storage.rst:34 msgid "" -"Automatically opening new ticket dialogues or user profiles requires agent " -"to extension mapping - see more below." +"While Zammad is beeing updated, it enforces a recursive \"change " +"owner\" (chown) for this directory. For instances with many files this can " +"be time consuming. To mitigate that you can move your files and create a " +"symlink in ``/opt/zammad/storage/`` to the new directory. Of course you have " +"to make sure on your own that the permissions are always correct." msgstr "" -"За аутоматски приказ дијалога нових тикета или корисничких профила потребно " -"је мапирање оператера на локале – погледајте више у наставку." +"Приликом ажурирања, Zammad ће извршити „промену власника” (chown) за овај " +"директоријум. За инстанце са великим бројем датотека ово може потрајати. Да " +"бисте предупредили ово понашање можете преместити ваше датотеке и креирати " +"симболични линк у ``/opt/zammad/storage/`` на нови директоријум. Наравно " +"морате обезбедити да су дозволе новог директоријума увек исправне." -#: ../system/integrations/cti/includes/introduction.include.rst:20 -msgid "Please note the following limitations to reduce confusion later on:" -msgstr "Имајте на уму следећа ограничења да бисте касније смањили забуну:" +#: ../settings/system/storage.rst:95 +msgid "Simple Storage (S3)" +msgstr "Simple Storage (S3)" -#: ../system/integrations/cti/includes/introduction.include.rst:22 -msgid "CTI integrations provide caller log functions only." -msgstr "CTI интеграције пружају само функције евиденције позива." +#: ../settings/system/storage.rst:41 +msgid "" +"To use the Simple Storage (S3), you have to provide some settings, which " +"can't be accessed in the UI (see instructions below)." +msgstr "" +"Да бисте користили Simple Storage (S3) морате обезбедити нека подешавања, " +"којима не можете приступити путем корисничког интерфејса (погледајте " +"упутства испод)." -#: ../system/integrations/cti/includes/introduction.include.rst:23 +#: ../settings/system/storage.rst:44 msgid "" -"This integration does not provide any VoIP functionalities; you can't make " -"phone calls from within Zammad." +"⚠️ Please note that the current implementation is in its early stages and can " +"be modified in the future." msgstr "" -"Ова интеграција не пружа никакве VoIP функционалности; не можете да " -"упућујете телефонске позиве из Zammad-а." +"⚠️ Упозоравамо вас да је тренутна имплементација у раном стадијуму и да може " +"бити промењена у будућности." -#: ../system/integrations/cti/includes/introduction.include.rst:25 +#: ../settings/system/storage.rst:47 msgid "" -"If your browser supports ``tel``-URLs, you can click on phone numbers for " -"automatic dialing. This requires additional software / configuration on your " -"agent's computers." +"The prerequisite is to have access to a S3-compatible storage and to have " +"all necessary parameters available (which depends on your storage provider; " +"if in doubt, please ask there for help)." msgstr "" -"Ако ваш претраживач подржава ``tel`` URL адресе, можете кликнути на бројеве " -"телефона за аутоматско бирање. Ово захтева додатни софтвер/конфигурацију на " -"рачунарима вашег оператера." +"Услов је да имате приступ S3 компатибилном складишту и да имате доступне све " +"захтеване параметере (који зависе од вашег провајдера складишта; ако нисте " +"сигурни, замолите их за помоћ)." -#: ../system/integrations/cti/generic.rst:9 -#: ../system/integrations/cti/placetel.rst:14 -#: ../system/integrations/cti/sipgate.rst:14 -msgid "Please provide the following requirements:" -msgstr "Наведите следеће услове:" +#: ../settings/system/storage.rst:51 +msgid "Steps to configure S3:" +msgstr "Кораци за подешавање S3:" -#: ../system/integrations/cti/generic.rst:11 +#: ../settings/system/storage.rst:53 msgid "" -"A telephone system that supports webhooks (outbound) (best option are those " -"that allow customizing the calls)." +"Copy ``config/zammad/storage.yml.dist`` to ``config/zammad/storage.yml``" msgstr "" -"Телефонска централа која подржава повратне позиве (одлазне) (најбоља опција " -"су оне који омогућавају прилагођавање позива)." - -#: ../system/integrations/cti/generic.rst:13 -msgid "A unique Call-ID during the call session." -msgstr "Јединствени ID позива током сесије позива." +"Ископирајте ``config/zammad/storage.yml.dist`` у ``config/zammad/storage." +"yml``" -#: ../system/integrations/cti/generic.rst:14 -msgid "Call event data (both numbers and direction)." -msgstr "Подаци о догађају позива (и бројеви и правац)." - -#: ../system/integrations/cti/generic.rst:15 -msgid "Your Zammad instance must be reachable for your telephony system." -msgstr "Ваша Zammad инстанца мора бити доступна вашој телефонској централи." +#: ../settings/system/storage.rst:54 +msgid "Edit the copied file in one of the following ways:" +msgstr "Измените копирану датотеку на један од следећих начина:" -#: ../system/integrations/cti/generic.rst:17 +#: ../settings/system/storage.rst:56 msgid "" -"If you want to learn more on what kind of requests are supported by Zammad " -"and what it expects, please consult our :docs:`CTI-API documentation `." +"Either provide your S3 configuration with one attribute per line like in the " +"upper area of the file" msgstr "" -"Ако желите да сазнате више о томе које врсте захтева Zammad подржава и шта " -"очекује, погледајте нашу :docs:`CTI-API документацију `." - -#: ../system/integrations/cti/generic.rst:22 -#: ../system/integrations/cti/placetel.rst:27 -#: ../system/integrations/cti/sipgate.rst:30 -msgid "Available Settings" -msgstr "Доступна подешавања" - -#: ../system/integrations/cti/generic.rst:29 -#: ../system/integrations/cti/placetel.rst:41 -#: ../system/integrations/cti/sipgate.rst:40 -msgid "Endpoint Settings" -msgstr "Подешавања путање" +"Или обезбедите вашу S3 конфигурацију са једним атрибутом по линији на начин " +"како је то урађено на почетку датотеке" -#: ../system/integrations/cti/generic.rst:25 +#: ../settings/system/storage.rst:58 msgid "" -"Zammad will list your generic CTI endpoint here. It contains a unique token " -"so ensure to keep this URL save." +"Or provide your S3 configuration as an URL (which you can find at the end of " +"the file). Note: you can also provide this URL as environment variable (:" +"docs:`see system documentation `) without using this yml-file." msgstr "" -"Zammad ће овде навести вашу генеричку CTI путању. Садржи јединствени кључ, " -"па се побрините да сачувате ову URL адресу." +"Или обезбедите вашу S3 конфигурацију као URL адресу (чији пример можете наћи " +"при крају датотеке). Напомена: такође можете обезбедити ову URL адресу као " +"променљиву окружења (:docs:`погледајте системску документацију `) без коришћења ове YML датотеке." -#: ../system/integrations/cti/generic.rst:28 +#: ../settings/system/storage.rst:62 msgid "" -"You'll need this endpoint for your PBX to talk to Zammad, see :docs:`CTI-API " -"documentation `." +"We recommend the deletion of the not used configuration style to avoid " +"inconsistencies." msgstr "" -"Ова путања је неопходна да би ваша PBX центеала комуницирала са Zammad-ом, " -"за детаље погледајте :docs:`CTI API документацију `." +"Предлажемо брисање свих конфигурација које не користите да бисте избегли " +"недоследности." -#: ../system/integrations/cti/includes/important-dont-forget-saving.include.rst:3 -msgid "" -"All following options **do not save automatically**. Always use the Save " -"button on the lower end of the integration page!" +#: ../settings/system/storage.rst:65 +msgid "Restart Zammad so the config file / environment variable is loaded" msgstr "" -"Све следеће опције се **не чувају аутоматски**. Увек користите дугме Сачувај " -"у доњем углу екрана за интеграцију!" - -#: ../system/integrations/cti/generic.rst:43 -#: ../system/integrations/cti/placetel.rst:49 -#: ../system/integrations/cti/sipgate.rst:52 -msgid "Call Settings" -msgstr "Подешавање позива" - -#: ../system/integrations/cti/generic.rst:39 -#: ../system/integrations/cti/placetel.rst:49 -#: ../system/integrations/cti/sipgate.rst:37 -#: ../system/integrations/cti/sipgate.rst:50 -msgid "Inbound" -msgstr "Долазнo" +"Рестартујте Zammad ради поновног учитавања конфигурационе датотеке / " +"променљиве окружења" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:1 +#: ../settings/system/storage.rst:66 msgid "" -"This option allows you to block specific incoming caller IDs. It allows you " -"to temporarily reject e.g. spam callers without having to contact providers " -"or PBX administrators." +"Set the \"Storage Method\" in Zammad to ``Simple Storage (S3)`` in Settings " +"> System > Storage and click on \"Submit\". After that, Zammad checks your " +"configuration and the connection to the service and will raise an error " +"message if something is wrong." msgstr "" -"Ова опција вам омогућава да блокирате одређене долазне ID позиваоца. " -"Омогућава вам да привремено одбијете нпр. spam позиваоцe без потребе да " -"контактирате провајдере или PBX администратора." - -#: ../system/integrations/cti/includes/inbound-calls.include.rst:11 -msgid "Caller ID to block" -msgstr "ID позиваоца за блокирање" +"Подесите „Метод складиштењa” у Zammad-у на ``Simple Storage (S3)`` преко " +"Подешавања > Систем > Складиште и кликните на „Пошаљи”. Након тога, Zammad " +"ће проверити вашу конфигурацију успостављајући конекцију са сервисом и " +"приказаће поруку грешке ако нешто пође наопако." -#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 -msgid "Provide caller IDs to block in ``E.164`` format." -msgstr "Наведите ID позиваоца за блокирање у ``Е.164`` формату." +#: ../settings/system/storage.rst:72 +msgid "A very simple storage configuration could look like this:" +msgstr "Врло једноставна конфигурација складишта би могла личити на следеће:" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:8 +#: ../settings/system/storage.rst:85 msgid "" -"Your telephony system has to support this function. Zammad will send a " -"``reject`` response which will cause your telephony system to hang up the " -"call. To callers this usually will feel like the line is busy." +"Before setting the storage method to ``Simple Storage (S3)`` (step 4), " +"please make sure to have a working setup." msgstr "" -"Ваша телефонска централа мора да подржава ову функцију. Zammad ће послати " -"``reject`` одговор који ће узроковати да ваша централа прекине позив. " -"Позиваоцима ово се обично манифестује као заузета линија." +"Пре постављања метода складиштења на ``Simple Storage (S3)`` (корак 4), " +"молимо проверите да ли ваш сервис функционише." -#: ../system/integrations/cti/includes/inbound-calls.include.rst:14 +#: ../settings/system/storage.rst:88 msgid "" -"Provide a meaningful note for your fellow administrators to remind yourself " -"why you've chosen to block the number." +"You can verify this by running ``rails r 'Rails.logger = Logger.new(STDOUT); " +"pp Store::Provider::S3.ping?'`` in your Zammad directory. If everything is " +"fine, you should see ``true``, else you should see ``false`` and a simple " +"error message." msgstr "" -"Унесите смислену напомену за своје колеге администраторе да бисте се их " -"подсетили зашто сте изабрали да блокирате број." +"Ово можете проверити извршавањем команде ``rails r ‘Rails.logger = Logger." +"new(STDOUT); pp Store::Provider::S3.ping?’`` у вашем Zammad директоријуму. " +"Уколико је све у реду, требало би да видите ``true``, у супротном биће " +"приказано ``false` са кратком поруком о грешци." -#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 -#: ../system/integrations/cti/includes/outbound-calls.include.rst:17 -#: ../system/integrations/cti/sipgate.rst:40 -msgid "Outbound" -msgstr "Одлазнo" +#: ../settings/system/storage.rst:93 +msgid "" +"If you installed Zammad through a package manager (rather than from source), " +"replace ``rails r`` with ``zammad run rails r`` above. To learn more, see :" +"docs:`Administration via Console `." +msgstr "" +"Ако сте инсталирали Zammad путем менаџера пакета (а не преко изворне " +"архиве), замените ``rails r`` са ``zammad run rails r`` изнад. За више " +"детаља, погледајте :docs:`администрацију путем конзоле `." -#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:1 +#: ../settings/ticket.rst:4 msgid "" -"In many cases you may want to use a different caller ID depending on the " -"destination you're calling. This may apply due to specific connection rates " -"to other countries or because you want your customer to feel you're calling " -"from the same country." +"Here you can adjust general ticket settings. Additional ones for the ticket " +"composer interface can be found in the :doc:`/misc/composer`." msgstr "" -"У многим случајевима можда ћете желети да користите другачији ID позиваоца у " -"зависности од дестинације коју позивате. Ово се може применити због " -"специфичних стопа везе са другим земљама или зато што желите да ваш клијент " -"примети да зовете из исте земље." +"Овде можете подесити општа подешавања тикета. Додатна подешавања за " +"интерфејс уредника текста могу се наћи у :doc:`/misc/composer`." -#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:6 -msgid "This option expects ``E.164`` number formats." -msgstr "Ова опција очекује бројеве у ``Е.164`` формату." +#: ../settings/ticket.rst:11 +msgid "Ticket Hook (default: ``Ticket#``)" +msgstr "Прикључак тикета (подразумевано: ``Ticket#``)" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 -msgid "Destination caller ID" -msgstr "Одредишни ID позиваоца" +#: ../settings/ticket.rst:11 +msgid "The identifier for a ticket; *e.g.,* Ticket#, Call#, MyTicket#." +msgstr "Идентификатор тикета, нпр. Ticket#, Call#, MyTicket#." -#: ../system/integrations/cti/includes/outbound-calls.include.rst:5 -msgid "The caller ID or number you're trying to call." -msgstr "ID позиваоца или број који покушавате да позовете." +#: ../settings/ticket.rst:38 +msgid "Ticket Hook Position (default: ``right``)" +msgstr "Положај прикључка тикета (подразумевано: ``десно``)" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:7 -msgid "You can use wildcards for e.g. country specific outbound numbers like:" +#: ../settings/ticket.rst:14 +msgid "" +"With this setting you can decide (if) where to insert the ticket number." msgstr "" -"Можете користити џокер знакове за нпр. одлазне бројеве специфичне за земљу " -"као што су:" +"Са овим подешавањем можете одлучити (да ли и) где се налази број тикета." -#: ../system/integrations/cti/includes/outbound-calls.include.rst:9 -msgid "``49*`` for Germany" -msgstr "``49*`` за Немачку" +#: ../settings/ticket.rst:20 +msgid "*Right*" +msgstr "*десно*" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:10 -msgid "``4930*`` for Berlin / Germany landlines" -msgstr "``4930*`` за фиксне телефоне из Берлина, Немачка" +#: ../settings/ticket.rst:17 +msgid "" +"This setting will add the ticket reference on the right site of the subject." +msgstr "Ово подешавање ће додати референцу тикета на десној страни предмета." -#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 -msgid "``33*`` for France" -msgstr "``33*`` за Француску" +#: ../settings/ticket.rst:20 +msgid "Example: ``Some Subject [Ticket#12345]``" +msgstr "Пример: ``Неки предмет [Ticket#12345]``" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:15 -msgid "Set Outbound caller ID" -msgstr "Подеси одлазећи ID позиваоца" +#: ../settings/ticket.rst:26 +msgid "*Left*" +msgstr "*лево*" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:14 +#: ../settings/ticket.rst:23 msgid "" -"The outbound caller ID to set (the number your customer sees on his display) " -"in ``E.164`` number format." -msgstr "" -"Подешавањен одлазног ID позиваоца (број који ваш клијент види на свом " -"екрану) у ``Е.164`` формату." +"This setting will add the ticket reference on the left site of the subject." +msgstr "Ово подешавање ће додати референцу тикета на десној страни предмета." -#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 -msgid "Provide a short description for fellow administrators." -msgstr "Унесите кратак опис за колеге администраторе." +#: ../settings/ticket.rst:26 +msgid "Example: ``[Ticket#12345] Some Subject``" +msgstr "Пример: ``[Ticket#12345] Неки предмет``" -#: ../system/integrations/cti/includes/generic-cti-support-note.includes.rst:3 -msgid "" -"This option requires your PBX to send a specific request to Zammad *before " -"dialing*. Please consult the :docs:`CTI API ` in case " -"you're not sure." -msgstr "" -"Ова опција захтева да ваша PBX централа пошаље посебан захтев Zammad-у *пре " -"бирања* броја. Молимо погледајте :docs:`CTI API документацију ` у случају да нисте сигурни." +#: ../settings/ticket.rst:29 +msgid "*None*" +msgstr "*празно*" -#: ../system/integrations/cti/generic.rst:52 -#: ../system/integrations/cti/placetel.rst:54 -#: ../system/integrations/cti/sipgate.rst:59 -msgid "Other Settings" -msgstr "Додатна подешавања" +#: ../settings/ticket.rst:29 +msgid "This will completely remove ticket references from the subject." +msgstr "Ово ће у потпуности уклонити референце тикета из предмета." -#: ../system/integrations/cti/includes/other-settings-intro.include.rst:1 +#: ../settings/ticket.rst:33 msgid "" -"Below you can find all available additional settings for this CTI " -"integration. For your overview we're sorting them by appearance and " -"reference their description first." +"Please ensure to take a look at :doc:`/channels/email/settings` within the " +"email channel to ensure you have at least one reference that helps Zammad to " +"assign follow-ups correctly." msgstr "" -"Испод можете пронаћи сва доступна додатна подешавања за ову CTI интеграцију. " -"Ради бољег прегледа сортирамо их по реду и прво указујемо на њихов опис." - -#: ../system/integrations/cti/includes/default-caller-id.include.rst:2 -#: ../system/integrations/cti/includes/default-caller-id.include.rst:1 -msgid "Default caller ID for outbound calls" -msgstr "Подразумевани ID позиваоца за одлазеће позиве" - -#: ../system/integrations/cti/includes/records-caller-log.include.rst:16 -#: ../system/integrations/cti/includes/records-caller-log.include.rst:15 -msgid "Shown records in caller log" -msgstr "Приказани записи евиденције позива" +"Обавезно погледајте :doc:`подешавања ` у оквиру " +"имејл канала да бисте били сигурни да имате бар једну референцу која помаже " +"Zammad-у да правилно додели наставке." -#: ../system/integrations/cti/includes/records-caller-log.include.rst:2 +#: ../settings/ticket.rst:37 msgid "" -"Allows you to set the number of shown caller log entries for all users. You " -"can choose from the following values:" +"Disabling this and not setting up any further follow up search will lead to " +"unexpected results!" msgstr "" -"Омогућава вам да подесите број приказаних записа у евиденцији позива за све " -"кориснике. Можете бирати између следећих вредности:" - -#: ../system/integrations/cti/includes/records-caller-log.include.rst:5 -msgid "60 (default)" -msgstr "60 (подразумевано)" - -#: ../system/integrations/cti/includes/records-caller-log.include.rst:6 -msgid "120" -msgstr "120" - -#: ../system/integrations/cti/includes/records-caller-log.include.rst:7 -msgid "180" -msgstr "180" - -#: ../system/integrations/cti/includes/records-caller-log.include.rst:8 -msgid "240" -msgstr "240" - -#: ../system/integrations/cti/includes/records-caller-log.include.rst:9 -msgid "300" -msgstr "300" - -#: ../system/integrations/cti/includes/records-caller-log.include.rst:11 -msgid "**🥵 Potential performance issue**" -msgstr "**🥵 Потенцијални проблем са перформансама**" +"Онемогућавање овога и неподешавање даље претраге наставака ће довести до " +"неочекиваних резултата!" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:13 +#: ../settings/ticket.rst:65 msgid "" -"Setting this setting higher than 60 may cause serious performance issues on " -"very busy instances. Keep in mind that this setting causes Zammad to poll " -"and send up to 300 records to *all active agent sessions* in very short time " -"periods." +"Ticket Last Contact Behaviour (default: ``Use the start time of the last " +"customer thread (which may consist of multiple articles).``)" msgstr "" -"Подешавање ове поставке на више од 60 може изазвати озбиљне проблеме са " -"перформансама у веома заузетим системима. Имајте на уму да ово подешавање " -"доводи до тога да Zammad редовно шаље захтеве и доставља до 300 уноса *свим " -"активним сесијама оператера* у веома кратким временским интервалима." - -#: ../system/integrations/cti/generic.rst:73 -msgid "Caller Log Filter" -msgstr "Филтер евиденције позива" +"Понашање последњег одговора тикета (подразумевано: ``Користи време почетка " +"последње конверзације клијента (која се може састојати од више чланака).``)" -#: ../system/integrations/cti/generic.rst:55 +#: ../settings/ticket.rst:41 msgid "" -"This function allows you to provide call information based on e.g. queues " -"only to agents that really need the information." +"This setting changes the way Zammad updates the ``Last Contact`` value of a " +"ticket. This is fairly important for overviews and what you expect upon " +"ticket updates of a customer." msgstr "" -"Ова функција вам омогућава да пружите информације о позиву на основу нпр. " -"редова само оператерима којима су информације заиста потребне." +"Ово подешавање мења начин на који Zammad освежава атрибут тикета „Последњи " +"одговор“. Ово је прилично важно за прегледе и оно што очекујете након " +"освежавања тикета од стране корисника." -#: ../system/integrations/cti/generic.rst:58 +#: ../settings/ticket.rst:52 msgid "" -"Why? If you have a team for several countries or departments, you don't want " -"to bug your agents from other departments. Leaving these options empty will " -"fallback to showing everything to everyone." +"Use the start time of the last customer thread (which may consist of " +"multiple articles)." msgstr "" -"Зашто? Ако имате тим за неколико земаља или одељења, не желите да гњавите " -"своје оператере из других одељења. Ако ове опције оставите празне, вратићете " -"се на приказивање свега свима." - -#: ../system/integrations/cti/generic.rst:64 -msgid "Destination caller ID or Queue" -msgstr "Одредишни ID позиваоца или ред" +"Користи време почетка последње конверзације клијента (која се може састојати " +"од више чланака)." -#: ../system/integrations/cti/generic.rst:63 +#: ../settings/ticket.rst:46 msgid "" -"This depends on your PBX and usually is either a queue ID, phone number or " -"extension." +"If this option is chosen, Zammad will update the last updated value just " +"once if a customer replies. After that, Zammad will wait for an agent to " +"react." msgstr "" -"Ово зависи од ваше PBX централе и обично је или ID реда, број телефона или " -"локал." - -#: ../system/integrations/cti/generic.rst:69 -msgid "Agents" -msgstr "Оператери" +"Ако се изабере ова опција, Zammad ће освежити вредност атрибута само једном " +"приликом одговора клијента. Након тога, Zammad ће сачекати да оператер " +"реагује." -#: ../system/integrations/cti/generic.rst:67 +#: ../settings/ticket.rst:50 msgid "" -"Select the agents that are responsible for the group. These agents will then " -"see caller log entries and call notifications fitting to said queue." +"This comes in handy if you want to work tickets in the order of their first " +"update. This will not change ticket orders if customers decide to \"bump\" " +"the ticket affected." msgstr "" -"Изаберите оператере који су одговорни за групу. Ови оператери ће тада видети " -"записе евиденције позива и обавештења о позивима која се уклапају у наведени " -"ред." +"Ово је згодно ако желите да радите на тикетима према редоследу њиховог првог " +"освежавања. Ово неће променити редослед тикета ако клијенти одлуче да само " +"„чукну” своје тикете." -#: ../system/integrations/cti/generic.rst:0 -msgid "" -"Screenshot showing the caller log filter table with pre filled sample data" -msgstr "" -"Снимак екрана који приказује табелу филтера евиденције позиваоца са унапред " -"попуњеним примером" +#: ../settings/ticket.rst:57 +msgid "Use the time of the very last customer article." +msgstr "Користи време последњег чланка клијента." -#: ../system/integrations/cti/includes/recent-logs.include.rst:6 +#: ../settings/ticket.rst:55 msgid "" -"With recent logs Zammad allows you to view the latest calls for the CTI " -"functionality. This usually comes in handy, when you're looking for errors." +"When setting this option, Zammad will always update the last updated value. " +"This means that if ordering by ``Last Update``, ticket orders will change if " +"customers \"bump\" the ticket." msgstr "" -"Са недавним евиденцијама Zammad вам омогућава да видите најновије позиве за " -"CTI функцију. Ово обично добро дође када исправљате грешке." +"Када одаберете ову опцију, Zammad ће увек освежити вредност атрибута. То " +"значи да ако сортирате према ``последњем одговору``, редослед тикета ће се " +"променити ако клијенти само „чукну” тикет." -#: ../system/integrations/cti/includes/recent-logs.include.rst:0 -msgid "" -"Screenshot showing several incoming requests within Recent logs section." +#: ../settings/ticket.rst:64 +msgid "Last contact value used on :doc:`/manage/overviews`" msgstr "" -"Снимак екрана који приказује неколико долазних позива у одељку Недавни уноси " -"евиденције." +"Вредност последњег одговора коришћена у :doc:`прегледима `" -#: ../system/integrations/cti/includes/recent-logs.include.rst:16 -msgid "I'm just here to clear floats up." -msgstr "Овде сам само да помогнем." +#: ../settings/ticket.rst:65 +msgid "Last contact value used on :doc:`/manage/trigger`" +msgstr "" +"Вредност последњег одговора коришћена у :doc:`окидачима `" -#: ../system/integrations/cti/includes/recent-logs.include.rst:20 +#: ../settings/ticket.rst:88 msgid "" -"By clicking on the entry of interest, Zammad will provide more details on " -"the call in question. You'll see the payload it received and also the " -"response that was sent." +"Ticket Organization Reassignment (default: ``Update the most recent tickets." +"``)" msgstr "" -"Кликом на одговарајући унос, Zammad ће дати више детаља о позиву у питању. " -"Видећете податке који су примљени, као и одговор који је послат." +"Пребацивање тикета организације (подразумевано: ``Освежи недавне тикете.``)" -#: ../system/integrations/cti/includes/recent-logs.include.rst:0 +#: ../settings/ticket.rst:68 msgid "" -"Screenshot showing detailed information of a specific log entry of recent " -"logs" +"This setting changes the way Zammad updates the organization field of the " +"tickets whenever the primary organization of a user is changed." msgstr "" -"Снимак екрана који приказује детаљне информације о одређеном уносу евиденције" - -#: ../system/integrations/cti/includes/recent-logs.include.rst:31 -msgid "x" -msgstr "x" +"Ово подешавање мења начин на који Zammad освежава поље организације тикета " +"кад год се промени примарна организација корисника." -#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 -#: ../system/integrations/cti/includes/troubleshooting.include.rst:9 -msgid "My Phone page stays blank, signalling does work..." -msgstr "Преглед позива је празан, сигнализација ради..." +#: ../settings/ticket.rst:74 +msgid "Update the most recent tickets." +msgstr "Освежи недавне тикете." -#: ../system/integrations/cti/includes/troubleshooting.include.rst:5 +#: ../settings/ticket.rst:72 msgid "" -"If you've made sure that signalling works (check Recent logs) and your " -"Caller Log still stays empty, please ensure that you only configured one CTI " -"integration version. Specifically defining more than one agent mapping on " -"the different integration variants will be the issue." +"If this option is chosen, Zammad will update the 100 most recent tickets " +"where the user is the ticket customer. The ticket organization field will be " +"automatically set to the new primary organization of the user." msgstr "" -"Ако сте се уверили да сигнализација функционише (проверите Недавне уносе " -"евиденције) и да ваша евиденција позива и даље остаје празна, проверите да " -"ли сте подесили само једну верзију CTI интеграције. Дефинисање више од " -"једног оператера на различите варијанте интеграције може представљати " -"проблем." +"Ако се изабере ова опција, Zammad ће освежити 100 најновијих тикета где је " +"корисник клијент тикета. Поље организације тикета ће аутоматски бити " +"постављено на нову примарну организацију корисника." -#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 -msgid "Clear the not needed agent mapping and reload your browser page." -msgstr "" -"Обришите мапирање оператера који вам није потребан и поново учитајте " -"страницу претраживача." +#: ../settings/ticket.rst:88 +msgid "Do not update any tickets." +msgstr "Без освежавања тикета." -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:1 +#: ../settings/ticket.rst:77 msgid "" -"By mapping your agents extension to their existing Zammad users, Zammad can " -"provide a new ticket dialog or open the user profile for the agent that " -"picks up the call." +"When choosing this option, Zammad will not update any tickets when the " +"user's primary organization is changed." msgstr "" -"Мапирањем локала ваших оператера на њихове постојеће Zammad кориснике, " -"Zammad може да обезбеди дијалог новог тикета или да отвори кориснички профил " -"за оператера који преузима позив." +"Када изаберете ову опцију, Zammad неће освежити ниједан тикет када се " +"промени примарна организација корисника." -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:5 +#: ../settings/ticket.rst:80 +msgid "**Use with care!**" +msgstr "**Користите пажљиво!**" + +#: ../settings/ticket.rst:82 msgid "" -"This speeds up ticket aiding, no matter if it's for existing tickets or new " -"ones!" +"Using this option may lead to inconsistencies in the system as the ticket " +"organization may become decoupled from the ticket customer." msgstr "" -"Ово убрзава обраду тикета, без обзира да ли се ради о постојећим или новим " -"тикетима!" +"Коришћење ове опције може довести до недоследности у систему јер се " +"организација тикета може одвојити од клијента тикета." -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:8 +#: ../settings/ticket.rst:85 msgid "" -"To see it work from the agent's perspective, have a look on :user-docs:`user " -"documentation `." +"However, you may use this option if you wish to maintain :ref:`the shared " +"access ` to the ticket for all organization " +"members of the original organization of the customer." msgstr "" -"Да бисте видели како функционише из перспективе оператера, погледајте :user-" -"docs:`корисничку документацију `." +"Међутим, можете користити ову опцију ако желите да задржите :ref:`дељени " +"приступ ` на тикету за све чланове " +"организације првобитне организације корисника." -#: ../system/integrations/cti/placetel.rst:2 -msgid "Placetel CTI" -msgstr "Placetel CTI" - -#: ../system/integrations/cti/placetel.rst:16 -msgid "You need an administrative Placetel account for your organization." -msgstr "Потребан вам је администраторски Placetel налог за вашу организацију." +#: ../settings/ticket.rst:110 +msgid "Ticket Number Format (default: ``Increment (SystemID.Counter)``)" +msgstr "Формат броја тикета (подразумевано: ``Увећање (SystemID.бројач)``)" -#: ../system/integrations/cti/placetel.rst:17 -#: ../system/integrations/cti/sipgate.rst:20 +#: ../settings/ticket.rst:94 msgid "" -"Your Zammad instance must be allowed to communicate to external services." +"This setting defines the way Zammad's ticket number will look. Changing this " +"setting in production will cause follow up detection to fail." msgstr "" -"Вашој Zammad инстанци мора бити дозвољено да комуницира са удаљеним " -"сервисима." - -#: ../system/integrations/cti/placetel.rst:18 -msgid "Placetel must be able to reach your Zammad instance." -msgstr "Placetel мора бити у могућности да приступи вашој Zammad инстанци." +"Ово подешавање одређује изглед Zammad-овог броја тикета. Промена овог " +"подешавања на системима у продукцији ће довести до неуспешног откривања " +"наставака." -#: ../system/integrations/cti/placetel.rst:22 -msgid ":doc:`provider-configurations/placetel`" -msgstr ":doc:`provider-configurations/placetel`" +#: ../settings/ticket.rst:102 +msgid "Increment (SystemID.Counter)" +msgstr "Увећање (SystemID.бројач)" -#: ../system/integrations/cti/placetel.rst:21 +#: ../settings/ticket.rst:98 msgid "" -"Learn how to configure Placetel to enable Zammad and Placetel to communicate " -"with each other." +"The increment value contains the SystemID (automatically generated during " +"installation) and a increment which counts up with every new Ticket. The " +"increment will automatically get another digit if needed." msgstr "" -"Научите како да подесите Placetel да бисте омогућили Zammad-у и Placetel-у " -"да међусобно комуницирају." +"Вредност бројача садржи SystemID (аутоматски генерисан током инсталације) и " +"бројач који се рачуна са сваким новом тикетом. Увећање ће аутоматски вратити " +"другу вредност ако је потребно." -#: ../system/integrations/cti/placetel.rst:32 +#: ../settings/ticket.rst:102 +msgid "Examples: ``1010138``, ``1010139``" +msgstr "Примери: ``1010138``, ``1010139``" + +#: ../settings/ticket.rst:110 +msgid "Date (Year.Month.Day.SystemID.Counter)" +msgstr "Датум (година.месец.дан.системID.бројач)" + +#: ../settings/ticket.rst:105 msgid "" -"The here listed endpoint settings are relevant for the :doc:`integration " -"configuration with Placetel `." +"This version of the ticket number is fairly long. However, because it " +"contains the date of ticket creation, it also allows you to see when the " +"ticket has been created. You may feel familiar with this number format if " +"you've worked with OTRS already." msgstr "" -"Овде наведена подешавања путање су релевантна за :doc:`подешавање Placetel " -"интеграције `." +"Овај облик броја тикета је прилично дугачак. Међутим, пошто садржи датум " +"отварања тикета, такође вам омогућава да видите када је тикет отворен. Можда " +"вам је познат овај формат броја ако сте већ радили са OTRS-ом." -#: ../system/integrations/cti/placetel.rst:37 -#: ../system/integrations/i-doit.rst:53 -msgid "Endpoint" -msgstr "Путања" +#: ../settings/ticket.rst:110 +msgid "Examples: ``201206231010138``, ``201206231010139``" +msgstr "Примери: ``201206231010138``, ``201206231010139``" -#: ../system/integrations/cti/placetel.rst:36 +#: ../settings/ticket.rst:137 +msgid "OPTIONS" +msgstr "Опције" + +#: ../settings/ticket.rst:113 msgid "" -"This endpoint will be required for the Zammad integration within the " -"Placetel web interface." +"The below options allow you to further customize your ticket number. The " +"availability of options differ depending of the chosen ticket number format " +"above." msgstr "" -"Ова путања ће бити потребна за Zammad интеграцију у Placetel корисничком " -"интерфејсу." +"Опције у наставку вам омогућавају да додатно прилагодите број својих тикета. " +"Доступност опција се разликује у зависности од изабраног формата броја " +"тикета изнад." -#: ../system/integrations/cti/placetel.rst:41 -msgid "API Token" -msgstr "API кључ" +#: ../settings/ticket.rst:122 +msgid "Checksum (default: ``no``)" +msgstr "Контролни збир (подразумевано: ``не``)" -#: ../system/integrations/cti/placetel.rst:40 +#: ../settings/ticket.rst:118 msgid "" -"You'll receive this token within the ``Web API`` menu. Make sure to copy " -"this value, it's only shown once!" +"If set to yes, we'll built a checksum to further \"unique\" the ticket " +"number of your system. If you're dealing with many other ticket systems this " +"might help to prevent false positive follow up detection on tickets." msgstr "" -"Добићете овај кључ у оквиру менија ``Web API``. Обавезно копирајте ову " -"вредност, она се приказује само једном!" +"Ако је постављено на да, биће израчунат контролни збир да би број тикета " +"вашег система остао „јединствен”. Ако се повезујете са другим системима " +"тикета, ово би могло помоћи да спречите откривање лажних наставака тикета." -#: ../system/integrations/cti/placetel.rst:71 -#: ../system/integrations/cti/sipgate.rst:77 -msgid "Phone Extension to Agent Mapping" -msgstr "Мапирање локала на оператере" +#: ../settings/ticket.rst:122 +msgid "This will also add another digit to the ticket number." +msgstr "Ово ће такође додати још једну цифру броју тикета." -#: ../system/integrations/cti/placetel.rst:0 -msgid "Screenshot showing sample user mappings in between Placetel and Zammad" -msgstr "" -"Снимак екрана који приказује примере мапирања корисника између Placetel-а и " -"Zammad-а" +#: ../settings/ticket.rst:137 +msgid "Min. size of Number (default: ``5``)" +msgstr "Минимална величина броја (подразумевано: ``5``)" -#: ../system/integrations/cti/placetel.rst:64 +#: ../settings/ticket.rst:125 msgid "" -"You can find your agents Placetel username combination required within ⚙️ PBX " -"→ VoIP destinations. Within the \"Advanced settings\" section you're looking " -"for \"SIP user name\" and \"SIP server\"." +"This setting defines the minimum length of your ticket number. If your " +"counter is not yet high enough, Zammad will fill the number with zeros to " +"ensure the wanted length." msgstr "" -"Неопходну комбинацију корисничког имена за своје оператере можете пронаћи у " -"оквиру ⚙️ PBX → VoIP destinations. У одељку „Advanced settings“ тражите „SIP " -"user name“ и „SIP server“." +"Ово подешавање одређује минималну дужину броја ваших тикета. Ако ваш бројач " +"још увек није довољно висок, Zammad ће попунити број нулама да би обезбедио " +"жељену дужину." -#: ../system/integrations/cti/placetel.rst:68 -msgid "Combine these two like so: ``@``." +#: ../settings/ticket.rst:129 +msgid "" +"Please note that the minimum length is ``3`` (SystemID + at least one digit " +"if below 10). Also, if the length is no longer long enough, the number will " +"automatically get one digit longer. Ticket-Numbers **do not overflow**, thus " +"it's save to keep it at 5 or set it lower if wanted." msgstr "" -"Комбинујте ово две вредности на следећи начин: ``@``." - -#: ../system/integrations/cti/placetel.rst:0 -msgid "Sample VoIP credentials for a Placetel user" -msgstr "Пример VoIP креденцијала за Placetel корисника" - -#: ../system/integrations/cti/provider-configurations/placetel.rst:2 -msgid "Setup Placetel connection for Zammad" -msgstr "Подесите Placetel везу за Zammad" +"Имајте на уму да је минимална дужина ``3`` (ID система + најмање једна цифра " +"ако је испод 10). Такође, ако дужина више није довољна, број ће аутоматски " +"добити додатну цифру. Бројеви тикета се **не обрћу**, тако да је безбедно да " +"дужину задржите на 5 или је смањите ако желите." -#: ../system/integrations/cti/provider-configurations/placetel.rst:6 +#: ../settings/ticket.rst:135 msgid "" -"This configuration step requires a *full* administrative Placetel account. " -"You may receive forbidden error messages with Placetel in case your " -"permissions are not high enough." +"This option is only available if ticket number format is set to " +"``Increment``!" msgstr "" -"Овај корак подешавања захтева администраторски Placetel налог *пуног " -"приступа*. Могуће је да ћете добити поруке о грешкама забране од Placetel-а " -"у случају да ваше дозволе нису довољно високе." +"Ова опција је доступна само ако је формат броја тикета подешен на " +"``Увећање``!" -#: ../system/integrations/cti/provider-configurations/placetel.rst:10 +#: ../settings/ticket.rst:142 +msgid "Auto-Assignment" +msgstr "Аутоматска додела" + +#: ../settings/ticket.rst:144 msgid "" -"The following actions can be configured via the `Placetel web interface " -"`_." +"In a larger Zammad environment, it happens that several agents open the same " +"ticket at the same time. Although collision detection is then effective, the " +"efficiency of processing can be increased by means of the automatic " +"assignment of tickets when a ticket is opened." msgstr "" -"Следеће радње се могу подесити преко `Placetel корисничког интерфејса " -"`_." - -#: ../system/integrations/cti/provider-configurations/placetel.rst:29 -msgid "Step 1: Activate Zammad integration" -msgstr "Корак 1: Активирајте Zammad интеграцију" +"У већем Zammad окружењу дешава се да неколико оператера отвори исти тикет у " +"исто време. Иако је детекција колизије тада у игри, ефикасност обраде се " +"може повећати аутоматском доделом тикета по отварању тикета." -#: ../system/integrations/cti/provider-configurations/placetel.rst:14 +#: ../settings/ticket.rst:149 msgid "" -"Within Integrations, scroll down to Partner integrations and select Zammad." +"The automatic assignment of tickets can be activated and configured in the " +"admin area under Settings > Ticket > Auto Assignment." msgstr "" -"У оквиру Integrations, скролујте надоле до Partner integrations и изаберите " -"Zammad." +"Аутоматска додела тикета се може активирати и подесити у области " +"администрације у одељку Подешавања > Тикет > Аутоматска додела." -#: ../system/integrations/cti/provider-configurations/placetel.rst:17 +#: ../settings/ticket.rst:152 msgid "" -"You can alternatively filter by \"Ticket Systems\" to reduce the number of " -"entries on the page. You'll still want to look for Partner integrations. 🤓" +"The auto assignment only works if the ticket has no owner yet. By default, " +"the agent can always reset the ticket owner to ``-`` if needed." msgstr "" -"Алтернативно, можете филтрирати према „Ticket Systems“ да бисте смањили број " -"уноса на страници. И даље ћете желети да потражите Partner integrations. 🤓" +"Аутоматска додела се извршава само ако тикет још увек нема власника. " +"Подразумевано, оператер увек може да врати власника тикета на ``-`` ако је " +"потребно." -#: ../system/integrations/cti/provider-configurations/placetel.rst:21 +#: ../settings/ticket.rst:155 msgid "" -"Within the Zammad integration now press \"Activate\". A new tab ``API`` " -"becomes available - open this tab." +"If you want to use this function for only specific tickets, you can " +"configure the conditions accordingly to meet your requirement. By default " +"the condition affects all tickets with the state ``open``." msgstr "" -"У оквиру Zammad интеграције сада притисните „Activate“. Нов језичак ``API`` " -"постаје доступан - отворите га." +"Ако желите да користите ову функцију само за одређене тикете, можете да " +"подесите услове у складу са вашим захтевима. Подразумевано услов утиче на " +"све тикете са стањем ``отворено``." -#: ../system/integrations/cti/provider-configurations/placetel.rst:24 +#: ../settings/ticket.rst:161 msgid "" -"Now tick \"Enable Call Control / Notify API\" and paste the Placetel " -"endpoint from your Zammad instance into the field \"URL of your API " -"endpoint\". Save to apply the settings" +"If you need to exclude users (e.g. a group leader), you can search and " +"select the desired agents in the ``Exception Users`` list. The search " +"function in this area is only effective, if you have too many agents to " +"display at once to help you with the configuration." msgstr "" -"Сада означите „Enable Call Control / Notify API“ и налепите Placetel путању " -"из ваше Zammad инстанце у поље „URL of your API endpoint“. Сачувајте да " -"бисте применили подешавања." +"Уколико је потребно да изфилтрирате кориснике (нпр. тим лидера), можете " +"претраживати по оператерима у листи ``Изузети корисници``. Функција претраге " +"у овој области има ефекта само ако имате превише оператера за приказ " +"одједном, да би вам помогла при подешавању." -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 -msgid "Screencast showing how to activate the Zammad integration" -msgstr "Снимак екрана који показује како да укључите Zammad интеграцију" +#: ../settings/ticket.rst:167 +msgid "Notifications" +msgstr "Обавештења" -#: ../system/integrations/cti/provider-configurations/placetel.rst:51 -msgid "Step 2: Generate API Token for Placetel" -msgstr "Корак 2: Генеришите API кључ за Placetel" +#: ../settings/ticket.rst:191 +msgid "Default Notifications" +msgstr "Подразумевана обавештења" -#: ../system/integrations/cti/provider-configurations/placetel.rst:32 +#: ../settings/ticket.rst:170 msgid "" -"Go back to the integrations page and scroll down to \"Web API\". Generate a " -"new API token by using the \"Create a new API token\" button." +"This setting allows you to configure the default ticket notifications that " +"will be applied to all new agent users (incl. users who were just assigned " +"agent role). Simply change the notification matrix to desired state and " +"press **Save**." msgstr "" -"Вратите се на страницу интеграције и померите се надоле до „Web API“. " -"Генеришите нови API кључ помоћу дугмета „Create a new API token“." +"Ово подешавање вам омогућава да одредите подразумевана обавештења о тикету " +"која ће бити примењена на све нове кориснике оператере (укључујући и " +"кориснике којима је управо додељена улога оператера). Једноставно измените " +"матрицу обавештења у жељено стање и притисните **Сачувај**." -#: ../system/integrations/cti/provider-configurations/placetel.rst:37 +#: ../settings/ticket.rst:175 msgid "" -"If you already generated a token either use your existing token or reset it " -"by using above mentioned button. Placetel will ask you to conform this reset." +"In case an agent already exists, their ticket notification preferences will " +"be preserved. Optionally, you can also **Apply current defaults to all " +"agents**." msgstr "" -"Ако сте већ генерисали кључ или користите свој постојећи кључ или га " -"ресетујте користећи горе поменуто дугме. Placetel ће од вас тражити да " -"потврдите ово ресетовање." +"У случају да оператер већ постоји, њихова подешавања обавештења о тикетима " +"ће бити сачувана. Опционо, такође можете **Применити подешавања свим " +"оператерима** и тада ће нова подразумевана подешавања бити примењена на све " +"оператере." -#: ../system/integrations/cti/provider-configurations/placetel.rst:41 +#: ../settings/ticket.rst:181 msgid "" -"Please keep in mind that existing API scripts may no longer work due to " -"token resets!" +"**Potential time-consuming action:** Applying default ticket notifications " +"to all agent users may take some time to complete, be patient! The exact " +"time will depend on the size of your system and the number of agents." msgstr "" -"Имајте на уму да постојеће API скрипте можда више неће радити због " -"ресетовања кључа!" +"**Потенцијално дугачка радња:** примена подразумеваних обавештења о тикетима " +"на све кориснике оператере може потрајати, будите стрпљиви! Тачно време ће " +"зависити од величине вашег система и броја оператера." -#: ../system/integrations/cti/provider-configurations/placetel.rst:44 +#: ../settings/ticket.rst:185 msgid "" -"Copy the provided API token and insert it into the \"API Token\" field " -"within Zammad's Placetel integration." +"**Active agents only!** When current default ticket notifications are " +"applied, only active agent users are considered. In case an agent is re-" +"activated *after* this action, they will still have the old notification " +"configuration." msgstr "" -"Копирајте наведени API кључ и налепите га у поље „API кључ“ у оквиру Zammad-" -"ове Placetel интеграције." +"**Само активни оператери!** Када се примењују тренутна подразумевана " +"обавештења о тикетима, узимају се у обзир само активни корисници оператери. " +"У случају да се оператер поново активира *после* ове акције, он ће и даље " +"имати стара подешавања обавештења." -#: ../system/integrations/cti/provider-configurations/placetel.rst:47 +#: ../settings/ticket.rst:190 msgid "" -"Apply your changes by using the \"Save\" button on the bottom of the " -"Placetel integration page and activate the Placetel integration." +"In case you want to go back to the initial state of ticket notifications, " +"you can click on **Reset to default** button." msgstr "" -"Примените своје промене помоћу дугмета „Сачувај“ при дну странице и укључите " -"Placetel интеграцију." +"У случају да желите да се вратите на почетно стање обавештења о тикету, " +"можете да кликнете на дугме **Поништи вредности**." -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +#: ../settings/ticket.rst:196 +msgid "Duplicate Detection" +msgstr "Откривање дупликата" + +#: ../settings/ticket.rst:238 +msgid "Detect Duplicate Ticket Creation" +msgstr "Откривање дупликата тикета приликом отварања" + +#: ../settings/ticket.rst:199 msgid "" -"Screencast showing how to retrieve an API token from Placetel for Zammad" +"This setting turns on the duplicate ticket detection mechanism during ticket " +"creation. If similar tickets are found in the system, a suitable warning " +"will be shown to the user trying to create a ticket." msgstr "" -"Снимак екрана који показује како да преузмете API кључ са Placetel-а за " -"Zammad" +"Ово подешавање укључује механизам за откривање дупликата тикета током " +"отварања тикета. Ако се пронађу слични тикети у систему, кориснику који " +"покушава да отвори нови тикет биће приказано одговарајуће упозорење." -#: ../system/integrations/cti/provider-configurations/placetel.rst:73 -#: ../system/integrations/cti/provider-configurations/sipgate.rst:77 -msgid "Step 3: Restrict the numbers to notify on" -msgstr "Корак 3: Ограничите бројеве за обавештавање" +#: ../settings/ticket.rst:206 +msgid "A Sample Duplicate Ticket Warning" +msgstr "Пример упозорења о дупликату тикета" -#: ../system/integrations/cti/provider-configurations/placetel.rst:54 +#: ../settings/ticket.rst:208 msgid "" -"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " -"the the Integrations page of the Placetel web interface, go to \"Notify " -"API\"." +"You can choose which ticket attributes will be matched by selecting them in " +"**Attributes to compare** field. Only if the ticket attribute value provided " +"by the user in the ticket create form is *equal* with the attribute in an " +"existing ticket, the warning will be shown." msgstr "" -"Имате много бројева које не би требало користити за обавештавање Zammad-а? " -"На страници Integrations корисничког интерфејса Placetel-а идите на „Notify " -"API“." +"Можете да изаберете који атрибути тикета треба да се подударају тако што " +"ћете их изабрати у пољу **Атрибути за поређење**. Само ако је вредност " +"атрибута тикета које је корисник навео у обрасцу за отварање новог тикета " +"*једнака* са атрибутом постојећег тикета, упозорење ће бити приказано." -#: ../system/integrations/cti/provider-configurations/placetel.rst:58 +#: ../settings/ticket.rst:213 +msgid "**Warning title** and **Warning message** are configurable as well." +msgstr "**Наслов упозорења** и **Порука упозорења** се такође могу подесити." + +#: ../settings/ticket.rst:215 msgid "" -"Lower on the page Placetel allows you to restrict the numbers to notify on. " -"You'll find this within the \"External routing API\" part." +"You can limit the detection only to certain user roles. By default, only " +"agents will see the warning." msgstr "" -"При дну на странице Placetel вам омогућава да ограничите бројеве за " -"обавештавање. Ово ћете пронаћи у делу „External routing API“." +"Откривање можете ограничити само на одређене корисничке улоге. " +"Подразумевано, само оператери ће видети упозорење." -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +#: ../settings/ticket.rst:218 msgid "" -"Screenshot showing a sample selection of phone numbers to use for the " -"Placetels notify API" +"If you don't want to show the matched tickets as part of the warning, you " +"can set **Show matching ticket(s) in the warning** setting to *no*." msgstr "" -"Снимак екрана који приказује пример избора телефонских бројева који ће се " -"користити за Placetel notify API" +"Ако не желите да прикажете пронађене тикете као део упозорења, можете да " +"подесите **Прикажи сличне тикете као део упозорења** на *не*." -#: ../system/integrations/cti/provider-configurations/placetel.rst:66 +#: ../settings/ticket.rst:221 msgid "" -"This menu point also provides a API request log from Placetel view. Just " -"open \"Recent responses of your API endpoint\" to learn more." +"By default, **Permission level for looking up ticket** is set to *User*, " +"which means user permissions will be honored during sarch. The user will " +"see the warning only if tickets they have access to are matched. " +"Alternatively, you can set this setting to *System*, in which case the " +"search will happen within *all* tickets in the system, regardless of user " +"permissions." msgstr "" -"Ова ставка менија такође пружа евиденцију API захтева из Placatel " -"перспективе. Отворите „Recent responses of your API endpoint“ да бисте " -"сазнали више." +"Подразумевано, **Ниво дозвола при претраживању тикета** је подешен на " +"*Корисник*, што значи да ће се корисничке дозволе поштовати током претраге. " +"Корисник ће видети упозорење само ако се подударају тикети којима има " +"приступ. Алтернативно, можете поставити ово подешавање на *Систем*, у ком " +"случају ће се претрага одвијати унутар *свих* тикета у систему, без обзира " +"на корисничке дозволе." -#: ../system/integrations/cti/provider-configurations/placetel.rst:69 +#: ../settings/ticket.rst:227 +msgid "**🦺 Safety first!**" +msgstr "**🦺 Безбедност на првом месту!**" + +#: ../settings/ticket.rst:229 msgid "" -"If you want to see Zammad's perspective, use the \"Recent Logs\" part from " -"within the Placetel integration page." +"Even if the permission level is set to *System*, the user will not be shown " +"the tickets they don't have access to in the warning, even if they match." msgstr "" -"Ако желите да видите Zammad-ову перспективу, користите део „Недавни уноси " -"евиденције“ на страници за Placetel интеграцију." +"Чак и ако је ниво дозволе постављен на *Систем*, кориснику неће бити " +"приказани тикети којима нема приступ у упозорењу, чак и ако се подударају." -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 -msgid "Screenshot showing sample log entries for Placetels API calls to Zammad" +#: ../settings/ticket.rst:233 +msgid "" +"However, just the confirmation about the existence of the tickets in the " +"system may be considered an unwanted information disclosure. Use this option " +"carefully!" msgstr "" -"Снимак екрана који приказује уносе евиденција за Placetel API позиве за " -"Zammad" - -#: ../system/integrations/cti/provider-configurations/placetel.rst:77 -msgid "Step 4 (optional): Further configurations for Placetel" -msgstr "Корак 4 (опционо): Даља подешавања за Placetel" +"Међутим, сама потврда о постојању тикета у систему може се сматрати " +"нежељеном информацијом. Користите ову опцију пажљиво!" -#: ../system/integrations/cti/provider-configurations/placetel.rst:76 +#: ../settings/ticket.rst:237 msgid "" -"If needed, you can now configure Zammad's Placetel integration in more " -"detail. You can learn more about your options here: :ref:`Placetel " -"integration settings `." +"Finally, you can configure between matching within **All tickets** or **Open " +"tickets** only by setting **Match tickets in following states**. Depending " +"on the current ticket state, a ticket may or not be matched." msgstr "" -"Ако је потребно, сада можете детаљније да подесите Zammad-ову Placetel " -"интеграцију. Можете сазнати више о опцијама у :ref:`подешавању Placetel " -"интеграције `." +"Коначно, можете да подесите **Претражи тикете у следећим стањима** на **Сви " +"тикети** или **Отворени тикети**. У зависности од тренутног стања тикета, " +"тикет ће бити узет у обзир." -#: ../system/integrations/cti/provider-configurations/sipgate.rst:2 -msgid "Setup Sipgate connection for Zammad" -msgstr "Повежите Sipgate за Zammad–ом" +#: ../system/core-workflows.rst:2 +msgid "Core Workflows" +msgstr "Радни токови" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +#: ../system/core-workflows.rst:4 msgid "" -"Sipgate has no english web interface which is why this documentation page is " -"mixing up languages badly." +"Core Workflows allow you to adjust object attributes in many ways. For " +"example:" msgstr "" -"Sipgate нема кориснички интерфејс на енглеском језику због чега ова страница " -"лоше меша језике." +"Радни токови вам омогућавају да подесите атрибуте објекта на различите " +"начине. На пример:" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Please also note that the availability of API addons highly depends on your " -"package trier. Usage of sipgate.io packages *is not free*, please check " -"their `pricing page `_ before!" -msgstr "" -"Такође имајте на уму да доступност API додатака у великој мери зависи од " -"вашег пакета услуга. Коришћење sipgate.io пакета *није бесплатно*, молимо " -"проверите њихову `страницу са ценама `_ пре " -"него што наставите!" +#: ../system/core-workflows.rst:7 +msgid "show / hide fields" +msgstr "прикажете / сакријете поља" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:35 -msgid "Step 1: Book sipgate.io package" -msgstr "Корак 1: Купите sipgate.io пакет" +#: ../system/core-workflows.rst:8 +msgid "adjust mandatory setting" +msgstr "подесите обавезност поља" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:13 -msgid "Skip to step 2 if you already have the package booked!" -msgstr "Пређите на корак 2 ако већ имате купљен пакет!" +#: ../system/core-workflows.rst:9 +msgid "manipulate available options" +msgstr "манипулишете доступним опцијама" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:15 +#: ../system/core-workflows.rst:11 msgid "" -"Login to an administrative Sipgate account and navigate to " -"``Accountverwaltung``. You'll see several different options depending on " -"your booked packages. Select ``Verträge & Produkte`` to continue." +"With this, you can provide exactly the information your users really need!" msgstr "" -"Пријавите се на администраторски Sipgate налог и идите на " -"``Accountverwaltung``. Видећете неколико различитих опција у зависности од " -"купљног пакета. Изаберите ``Verträge & Produkte`` да бисте наставили." +"Са овим алаткама, спремни сте да обезбедите управо оне информације које су " +"заиста потребне!" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:19 +#: ../system/core-workflows.rst:15 msgid "" -"Scroll down to the section ``Zusätzliche Produkte buchen`` and look for " -"``sipgate.io`` - select this product by using the ``Produkte anzeigen``-" -"Button." +"If the pre-defined :doc:`/system/objects` are not enough, please add them " +"beforehand." msgstr "" -"Скролујте надоле до одељка ``Zusätzliche Produkte buchen`` и потражите " -"``sipgate.io`` - изаберите овај производ помоћу дугмета ``Produkte " -"anzeigen``." +"Ако вам унапред дефинисани :doc:`објекти ` нису довољни, " +"додајте их унапред." -#: ../system/integrations/cti/provider-configurations/sipgate.rst:23 +#: ../system/core-workflows.rst:17 msgid "" -"On the next page select either one of the ``sipgate.io`` packages or ``Push-" -"API Package Free``. Follow the dialogue by booking the addon. You'll be " -"returned to your contract overview and now should see the selected addon in " -"your list." +"If you experience slow or unreliable field updates, please see :ref:`Core " +"Workflow Ajax Modus `" msgstr "" -"На следећој страници изаберите било који од ``sipgate.io`` пакета или ``Push-" -"API Package Free``. Пратите дијалог тако што ћете купити додатак. Бићете " -"враћени на преглед вашег уговора и сада би требало да видите изабрани " -"додатак на вашој листи." +"Ако имате спора или непоуздана освежавања на терену, погледајте :ref:`Ajax " +"режим радног тока `." -#: ../system/integrations/cti/provider-configurations/sipgate.rst:30 +#: ../system/core-workflows.rst:22 msgid "" -"The availability for ``sipgate.io`` packages and their levels highly depends " -"on the overall account type and product you've booked with Sipgate." +"This is a very enhanced functionality and can cause unexpected UI behavior. " +"Please ensure to test your use cases after configuration to reduce surprises." msgstr "" -"Доступност пакета ``sipgate.io`` и њихови нивои у великој мери зависе од " -"укупног типа налога и производа који сте резервисали код Sipgate-а." - -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screencast showing the process on how to book the required sipgate.io addon" -msgstr "" -"Снимак екрана који приказује процес како да купите потребан sipgate.io " -"додатак" - -#: ../system/integrations/cti/provider-configurations/sipgate.rst:52 -msgid "Step 2: Configure webhook for Zammad" -msgstr "Корак 2: Подесите повратни позив за Zammad" - -#: ../system/integrations/cti/provider-configurations/sipgate.rst:38 -msgid "" -"Within your ``Accountverwaltung`` navicate to your product ``sipgate.io``. " -"In the newly opened tab, switch from \"Clients\" to \"Webhooks\" and paste " -"the endpoint URLs from your Zammad instance like so:" -msgstr "" -"У оквиру вашег ``Accountverwaltung`` одељка идите на свој ``sipgate.io`` " -"производ. У новоотвореном језичку, пребаците се са „Clients“ на „Webhooks“ и " -"налепите URL адресе путањи са ваше Zammad инстанце на следећи начин:" +"Ово је напредна функција и може изазвати неочекивано понашање корисничког " +"интерфејса. Обавезно тестирајте своје случајеве коришћења након подешавања " +"да бисте смањили изненађења." -#: ../system/integrations/cti/provider-configurations/sipgate.rst:42 -msgid "Inbound endpoint to \"Incoming\"" -msgstr "Долазна путања за „Incoming“" +#: ../system/core-workflows.rst:None +msgid "Dialogue for adding a new workflow" +msgstr "Дијалог за додавање новог радног тока" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:43 -msgid "Outbound endpoint to \"Outgoing\"" -msgstr "Одлазна путања за „Outgoing“" +#: ../system/core-workflows/condition-operators.rst:2 +msgid "Core Workflow Condition Operators" +msgstr "Оператори услова радних токова" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:47 +#: ../system/core-workflows/condition-operators.rst:4 msgid "" -"Ensure to select at least one call group or phoneline within \"Sources\". " -"Other wise Sipgate will not indicate any incoming or outgoing calls to " -"Zammad." +"You might know that there is a separate section for explaining :doc:" +"`condition operators `. Head over there to " +"see a detailed explanation of many conditions and operators." msgstr "" -"Обавезно изаберите најмање једну групу позива или телефонску линију у оквиру " -"„Sources“. Иначе, Sipgate неће назначити никакве долазне или одлазне позиве " -"Zammad-у." +"Можда сте свесни да постоји посебан одељак који објашњава :doc:`операторе " +"услова `. Тамо можете пронаћи детаљна " +"објашњења за многе услове и операторе." -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +#: ../system/core-workflows/condition-operators.rst:8 msgid "" -"Screencast showing how to add Zammad's endpoint URLs to sipgate.ios webhook " -"configuration" +"Due to differences to other places in Zammad which are also using conditions " +"(e.g. triggers), you can find a dedicated description of operators for core " +"workflows below." msgstr "" -"Снимак екрана који показује како да додате URL адресе путања Zammad-а у " -"подешавање sipgate.io повратних позива" +"Услед разлика са другим областима Zammad-а које такође користи услове (нпр. " +"окидачи), испод можете пронаћи објашњење посвећено операторима радних токова." -#: ../system/integrations/cti/provider-configurations/sipgate.rst:55 +#: ../system/core-workflows/condition-operators.rst:12 msgid "" -"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " -"the Webhooks → URLs section of Sipgate you can select which *sources* " -"Sipgate should notify Zammad about in- and outgoing calls." +"Be aware that the availability of the operators depends on the selected " +"attribute and its field type. Some of the operators may only be available " +"for system attributes (e.g. for \"tags\", \"active\")." msgstr "" -"Имате много бројева које не би требало користити за обавештавање Zammad-а? У " -"одељку Webhooks → URLs Sipgate-а можете да изаберете које *изворе* Sipgate " -"треба да обавести Zammad о долазним и одлазним позивима." +"Обратите пажњу да доступност оператора зависи од одабраних атрибута и типа " +"поља. Неки од оператора могу бити доступни само за системске атрибуте (нпр. " +"за „Ознаке”, „Активно”)." -#: ../system/integrations/cti/provider-configurations/sipgate.rst:59 -msgid "" -"Use either specific phone lines or use the option \"Use for all phonelines " -"and groups\" to notify Zammad about all existing lines of your Sipgate " -"account." -msgstr "" -"Користите или одређене телефонске линије или користите опцију „Use for all " -"phonelines and groups“ да обавестите Zammad о свим постојећим линијама вашег " -"Sipgate налога." +#: ../system/core-workflows/condition-operators.rst:20 +msgid "Operator" +msgstr "Оператор" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screenshot showing a sample selection of phone numbers to use for the " -"Sipgates webhooks API" -msgstr "" -"Снимак екрана који приказује пример избора телефонских бројева за употребу " -"за Sipgate API повратних позива" +#: ../system/core-workflows/condition-operators.rst:22 +msgid "after (absolute)" +msgstr "након (апсолутно)" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:68 -msgid "This section also allows you to enable a Debug log." -msgstr "" -"Овај одељак вам такође омогућава да омогућите евиденцију уноса за отклањање " -"грешака." +#: ../system/core-workflows/condition-operators.rst:23 +msgid "Matches if a date/time is after a specific point in time." +msgstr "Подудара се ако је датум/време након одређеног тренутка." -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "Screenshot showing an enabled Debug log option" -msgstr "" -"Снимак екрана који приказује омогућену опцију евиденције уноса за отклањање " -"грешака" +#: ../system/core-workflows/condition-operators.rst:24 +msgid "after (relative)" +msgstr "након (релативно)" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:73 -msgid "" -"After enabling you can use the Debug log section to see all sent webhook " -"calls to Zammad. You'll also can see the response." -msgstr "" -"Након укључивања, можете користити одељак евиденције за отклањање грешака да " -"бисте видели све позиве упућене Zammad повратном позиву. Такође ћете видети " -"и све одговоре." +#: ../system/core-workflows/condition-operators.rst:25 +msgid "Matches if a time span after a specified event has passed." +msgstr "Подудара се ако је временски оквир прошао након одређеног догађаја." -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screenshot showing sample log entries for Sipgates webhook calls to Zammad" -msgstr "" -"Снимак екрана који приказује примере уноса евиденције за Sipgate повратне " -"позиве Zammad-у" +#: ../system/core-workflows/condition-operators.rst:26 +msgid "before (absolute)" +msgstr "пре (апсолутно)" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:81 -msgid "Step 4 (optional): Further configurations for Sipgate" -msgstr "Корак 4 (опционо): Даља подешавања за Sipgate" +#: ../system/core-workflows/condition-operators.rst:27 +msgid "Matches if a date/time is before a specific point in time." +msgstr "Подудара се ако је време/датум пре одређеног тренутка." -#: ../system/integrations/cti/provider-configurations/sipgate.rst:80 -msgid "" -"If needed, you can now configure Zammad's Sipgate integration in more " -"detail. You can learn more about your options here: :ref:`Sipgate " -"integration settings `." -msgstr "" -"Ако је потребно, сада можете детаљније да подесите Zammad-ову Sipgate " -"интеграцију. Можете сазнати више о опцијама у :ref:`подешавањима Sipgate " -"интеграције `." +#: ../system/core-workflows/condition-operators.rst:28 +msgid "before (relative)" +msgstr "пре (релативно)" -#: ../system/integrations/cti/sipgate.rst:2 -msgid "Sipgate (sipgate.io)" -msgstr "Sipgate (sipgate.io)" +#: ../system/core-workflows/condition-operators.rst:29 +msgid "Matches if a time span after a specified event has not passed." +msgstr "Подудара се ако временски оквир након одређеног догађаја није прошао." -#: ../system/integrations/cti/sipgate.rst:16 -msgid "You need an administrative Sipgate account for your organization." -msgstr "Потребан вам је администраторски Sipgate налог за вашу организацију." +#: ../system/core-workflows/condition-operators.rst:30 +msgid "contains" +msgstr "садржи" -#: ../system/integrations/cti/sipgate.rst:17 -msgid "" -"Zammad requires a ``sipgate.io`` addon from the feature store (please note " -"that API calls are not free with Sipgate. Rates may apply and differ from " -"account to account)." -msgstr "" -"Zammad захтева ``sipgate.io`` додатак са маркета апликација. (Имајте на уму " -"да API позиви нису бесплатни. Цене могу да се разликују од налога до налога.)" +#: ../system/core-workflows/condition-operators.rst:31 +msgid "Matches if a specified value is present." +msgstr "Подудара се ако одређена вредност постоји." -#: ../system/integrations/cti/sipgate.rst:21 -msgid "Sipgate must be able to reach your Zammad instance." -msgstr "Sipgate мора бити у могућности да приступи вашој Zammad инстанци." +#: ../system/core-workflows/condition-operators.rst:33 +msgid "Matches if all of the specified values are present." +msgstr "Подудара се ако све дате вредности постоје." -#: ../system/integrations/cti/sipgate.rst:25 -msgid ":doc:`provider-configurations/sipgate`" -msgstr ":doc:`provider-configurations/sipgate`" +#: ../system/core-workflows/condition-operators.rst:35 +msgid "Matches if none of the specified values are present." +msgstr "Подудара се ако ниједна од датих вредности не постоји." -#: ../system/integrations/cti/sipgate.rst:24 -msgid "" -"Learn how to configure Sipgate to enable Zammad and Sipgate to communicate " -"with each other." -msgstr "" -"Научите како да подесите Sipgate да бисте омогућили Zammad-у и Sipgate-у да " -"међусобно комуницирају." +#: ../system/core-workflows/condition-operators.rst:36 +msgid "contains not" +msgstr "не садржи" -#: ../system/integrations/cti/sipgate.rst:33 -msgid "" -"Below endpoint settings affect the :doc:`sipgate.io configuration `." -msgstr "" -"Подешавања путање испод утичу на :doc:`sipgate.io подешавања `." +#: ../system/core-workflows/condition-operators.rst:37 +msgid "Matches if a specified value is not present." +msgstr "Подудара се ако дата вредност не постоји." -#: ../system/integrations/cti/sipgate.rst:37 -msgid "This endpoint is required for incoming call hooks." -msgstr "Ова путања је потребна за регистрацију долазних позиве." +#: ../system/core-workflows/condition-operators.rst:39 +msgid "Matches if one specified value is present." +msgstr "Подудара се ако једна дата вредност постоји." -#: ../system/integrations/cti/sipgate.rst:40 -msgid "This endpoint is required for outgoing call hooks." -msgstr "Ова путања је потребна за регистрацију одлазних позива." +#: ../system/core-workflows/condition-operators.rst:41 +msgid "Matches if one specified value is not present." +msgstr "Подудара се ако једна дата вредност не постоји." -#: ../system/integrations/cti/sipgate.rst:0 -msgid "Screenshot showing sample user mappings in between Sipgate and Zammad" -msgstr "" -"Снимак екрана који приказује примере мапирања корисника између Sipgate-а и " -"Zammad-а" +#: ../system/core-workflows/condition-operators.rst:42 +msgid "does not match regex" +msgstr "не задовољава регуларни израз" -#: ../system/integrations/cti/sipgate.rst:69 -msgid "" -"You can find your agent's Sipgate username within ``Accountverwaltung → " -"Benutzer``. You're looking for the SIP-ID." -msgstr "" -"Sipgate корисничко име вашег оператера можете пронаћи у оквиру " -"``Accountverwaltung → Benutzer``. Тражите SIP-ID." +#: ../system/core-workflows/condition-operators.rst:43 +msgid "Matches if content doesn't fit to regex rule." +msgstr "Подудара се ако се садржај не поклапа са регуларним изразом." -#: ../system/integrations/cti/sipgate.rst:0 -msgid "Sample VoIP credentials for a Sipgate user" -msgstr "Пример VoIP креденцијала за Sipgate корисника" +#: ../system/core-workflows/condition-operators.rst:44 +msgid "ends with" +msgstr "завршава се са" -#: ../system/integrations/cti/sipgate.rst:77 -msgid "Users with several devices also have several SIP-IDs." -msgstr "Корисници са више уређаја такође имају неколико SIP-ID-ова." +#: ../system/core-workflows/condition-operators.rst:45 +msgid "Matches if content ends with specified value." +msgstr "Подудара се ако се садржај завршава са датом вредности." -#: ../system/integrations/elasticsearch.rst:2 -msgid "Elasticsearch (SaaS)" -msgstr "Elasticsearch (SaaS)" +#: ../system/core-workflows/condition-operators.rst:46 +msgid "ends with one of" +msgstr "завршава се са једним од" -#: ../system/integrations/elasticsearch.rst:4 -msgid "" -"The Elasticsearch integration allows you to create a read-only user to use " -"with your favorite reporting tool (e.g. like Grafana)." -msgstr "" -"Elasticsearch интеграција вам омогућава да додате корисника само за читање " -"кога ћете користити са вашим омиљеним алатом за извештавање (нпр. као што је " -"Grafana)." - -#: ../system/integrations/elasticsearch.rst:7 -msgid "" -"If you want to take full advantage of the Zammad reporting, have a look at " -"our :docs:`Grafana ` " -"setup page as well." -msgstr "" -"Ако желите да у потпуности искористите Zammad извештавање, погледајте и нашу " -"страницу за подешавање :docs:`Grafana-е `." - -#: ../system/integrations/elasticsearch.rst:11 -#: ../system/subscription/index.rst:7 -msgid "**🚧 Hosted environment specific 🚧**" -msgstr "**🚧 Oкружење специфичхо за хостоване иснтанце 🚧**" - -#: ../system/integrations/elasticsearch.rst:13 -msgid "" -"This integration is only available for Hosted setups. In order to use " -"Elasticsearch you'll need the **Plus** subscription." -msgstr "" -"Ова интеграција је доступна само за хостоване системе. Да бисте користили " -"Elasticsearch, биће вам потребна **Plus** претплата." - -#: ../system/integrations/elasticsearch.rst:16 -msgid "" -"Self hosted users have all the control over their self hosted Elasticsearch " -"instances." -msgstr "" -"Корисници који сами хостују имају сву контролу над својим Elasticsearch " -"инстанцама које сами хостују." - -#: ../system/integrations/elasticsearch.rst:None -msgid "Elasticsearch integration page on SaaS environments" -msgstr "Страница за Elasticsearch интеграцију у SaaS окружењима" - -#: ../system/integrations/elasticsearch.rst:27 -msgid "" -"Please note the following limitations of Elasticsearch access on hosted " -"environments:" -msgstr "" -"Имајте на уму следећа ограничења приступа Elasticsearch у хостованим " -"окружењима:" - -#: ../system/integrations/elasticsearch.rst:30 -msgid "access to the Elasticsearch index is read-only access" -msgstr "приступ Elasticsearch индексу је омогућен само за читање" - -#: ../system/integrations/elasticsearch.rst:31 -msgid "currently you're limited to user only" -msgstr "тренутно сте ограничени само на кориснике" - -#: ../system/integrations/elasticsearch.rst:32 -msgid "" -"Reporting tools that require to write into the indexes (like Kibana) are not " -"supported" -msgstr "" -"Алати за извештавање који захтевају писање у индексе (као што је Kibana) " -"нису подржани" - -#: ../system/integrations/elasticsearch.rst:34 -msgid "IP access restriction is currently not yet supported" -msgstr "Ограничење приступа на основу IP адресе још увек није подржано" - -#: ../system/integrations/elasticsearch.rst:37 -msgid "Activating Elasticsearch Access" -msgstr "Укључивање Elasticsearch приступа" - -#: ../system/integrations/elasticsearch.rst:39 -msgid "" -"By default external access to your Elasticsearch index is not active. You " -"can enable the integration at any time if needed." -msgstr "" -"Подразумевано, спољни приступ вашем Elasticsearch индексу није омогућен. " -"Можете укључити интеграцију у било ком тренутку ако је потребно." - -#: ../system/integrations/elasticsearch.rst:42 -msgid "" -"Please ensure to note down the password provided - you won't have access to " -"it afterwards." -msgstr "" -"Обавезно забележите достављену лозинку - касније јој нећете имати приступ." - -#: ../system/integrations/elasticsearch.rst:None -msgid "Screencast showing activation of Elasticsearch integration" -msgstr "Снимак екрана који приказује укључивање Elasticsearch интеграције" - -#: ../system/integrations/elasticsearch.rst:51 -msgid "Connection Settings" -msgstr "Подешавања везе" - -#: ../system/integrations/elasticsearch.rst:53 -msgid "" -"This section holds the most important general information for accessing your " -"Elasticsearch indexes - such as:" -msgstr "" -"Овај одељак садржи најважније опште информације за приступ вашим " -"Elasticsearch индексима – као што су:" - -#: ../system/integrations/elasticsearch.rst:57 -msgid "A unique subdomain that does not tell your real instance URL." -msgstr "Јединствени поддомен који не садржи URL адресу ваше праве инстанце." - -#: ../system/integrations/elasticsearch.rst:61 -msgid "Software" -msgstr "Софтвер" - -#: ../system/integrations/elasticsearch.rst:60 -msgid "" -"The major version of the search index being used. This is required by some " -"Reporting tools like Grafana." -msgstr "" -"Major верзија индекса претраге која се користи. Ово захтевају неки алати за " -"извештавање као што је Grafana." - -#: ../system/integrations/elasticsearch.rst:64 -msgid "Authentication" -msgstr "Аутентификација" - -#: ../system/integrations/elasticsearch.rst:64 -msgid "The authentication type being supported. ``Basic Authentication``" -msgstr "Тип аутентификације који је подржан. ``Basic Authentication``" - -#: ../system/integrations/elasticsearch.rst:67 -msgid "Available Indexes" -msgstr "Доступни индекси" - -#: ../system/integrations/elasticsearch.rst:69 -msgid "" -"Within this section we're displaying the -in our opinion- most important " -"indexes for a Zammad instance." -msgstr "" -"У оквиру овог одељка приказујемо - по нашем мишљењу - најважније индексе за " -"Zammad инстанцу." - -#: ../system/integrations/elasticsearch.rst:72 -msgid "" -"If you require all indexes or our listing is not good enough for you, point " -"your browser to the URL we're providing and append ``/_aliases?" -"pretty=true``. The result should look like this: ``https://.zammad.com/" -"_aliases?pretty=true``." -msgstr "" -"Ако су вам потребни сви индекси или наш списак није довољно детаљан, " -"усмерите свој претраживач на следећу URL адресу ``/_aliases?pretty=true``. " -"Резултат би требало да изгледа овако: ``https://.zammad.com/_aliases?" -"pretty=true``." - -#: ../system/integrations/elasticsearch.rst:77 -msgid "" -"Your browser will automatically ask for your credentials - you'll then see " -"something like this:" -msgstr "" -"Ваш претраживач ће аутоматски затражити да се аутентификујете - тада ћете " -"видети нешто овако:" - -#: ../system/integrations/elasticsearch.rst:125 -msgid "Credentials" -msgstr "Креденцијали" - -#: ../system/integrations/elasticsearch.rst:127 -msgid "" -"Within this section Zammad displays your available users. The password is " -"provided once (upon activation) and cannot be retrieved after that." -msgstr "" -"У оквиру овог одељка Zammad приказује ваше доступне кориснике. Лозинка се " -"даје једном (по активацији) и након тога се не може преузети." - -#: ../system/integrations/elasticsearch.rst:131 -msgid "" -"If you need to change or reset your Elasticsearch user password, use the " -"\"Reset password\" button in the credentials table. Doing so creates a brand " -"new password for the account in question. This change is immediate, keep in " -"mind that this may affect third party tools connected to your instance." -msgstr "" -"Ако желите да промените или поништите вашу Elasticsearch корисничку лозинку, " -"користите дугме „Reset password“ у табели са креденцијалима. Овиме ћете " -"добити потпуно нову лозинку за дотични налог. Ова промена је тренутна, " -"имајте на уму да то може да утиче на алате трећег лица повезане са вашом " -"инстанцом." - -#: ../system/integrations/exchange.rst:2 -msgid "Exchange" -msgstr "Exchange" - -#: ../system/integrations/exchange.rst:4 -msgid "" -"With Zammad's Exchange integration, you can easily use existing address " -"books without having to update more than one source." -msgstr "" -"Уз Zammad-ову Exchange интеграцију, можете лако да користите постојеће " -"адресаре без потребе да ажурирате више од једног извора." +#: ../system/core-workflows/condition-operators.rst:47 +msgid "Matches if content ends with one of the specified values." +msgstr "Подудара се ако се садржај завршава са једном од датих вредности." -#: ../system/integrations/exchange.rst:7 -msgid "" -"However, you should refrain from syncing all addresses, as the results may " -"not be what you expect (Exchange collects huge amounts of addresses). A " -"central address book of your company to sync makes more sense, as you can " -"ensure that Zammad gets only the data you need and want. Apart from this, it " -"is even not possible to sync the Global Address List (GAL) of your Exchange " -"system with Zammad." -msgstr "" -"Међутим, требало би да се уздржите од синхронизације свих адреса, јер " -"резултати можда неће бити оно што очекујете (Exchange прикупља огромне " -"количине адреса). Централни адресар ваше фирме за синхронизацију има више " -"смисла, јер можете осигурати да Zammad добија само податке који су вам " -"потребни и који желите. Поред овога, чак није ни могуће синхронизовати " -"Global Addres List (GAL) вашег Exchange система са Zammad-ом." +#: ../system/core-workflows/condition-operators.rst:48 +msgid "from (relative)" +msgstr "од (релативно)" -#: ../system/integrations/exchange.rst:16 -msgid "" -"**Exchange and LDAP:** The exchange sync can be overruled by Zammad's LDAP " -"integration. If you have the same users in both sources, the LDAP version " -"will always be Zammad's pick." -msgstr "" -"**Exchange и LDAP:** Exchange синхронизација може бити поништена Zammad-овом " -"LDAP интеграцијом. Ако имате исте кориснике у оба извора, LDAP верзија ће " -"увек бити Zammad-ов избор." +#: ../system/core-workflows/condition-operators.rst:49 +msgid "Matches if date/time is after a period of time after an event." +msgstr "Подудара се ако је датум/време након датог периода после догађаја." -#: ../system/integrations/exchange.rst:19 -msgid "" -"**One way sync:** the Exchange sync is one way. Exchange => Zammad. Changes " -"to your users inside of Zammad might be overwritten by the Exchange sync." -msgstr "" -"**Синхронизација у једном смеру:** Exchange синхронизација је једносмерна: " -"Exchange => Zammad. Може преписати ваше измене корисника унутар Zammad-а." +#: ../system/core-workflows/condition-operators.rst:51 +msgid "Matches if content is equal to a specified value." +msgstr "Подудара се ако је садржај једнак датој вредности." -#: ../system/integrations/exchange.rst:24 -msgid "" -"To configure Exchange integration, simply go to the System > Integrations > " -"Exchange in the admin panel. Press \"change\" and follow the wizard for " -"adding the needed Exchange information to Zammad. On the last two steps " -"Zammad will ask you for the address book(s) and your desired attribute " -"mapping. By default, Zammad only maps email address, first- and lastname. " -"Technically, you can map any Exchange object to a Zammad user object (this " -"also works for custom objects!)." -msgstr "" -"Да бисте подесили Exchange интеграцију, једноставно идите на Систем -> " -"Интеграције -> Exchange на административној табли. Притисните „Измена“ и " -"пратите чаробњак за додавање потребних Exchange информација у Zammad. У " -"последња два корака Zammad ће вас питати за адресар(е) и мапирање жељених " -"атрибута. Подразумевано, Zammad мапира само имејл адресу, име и презиме. " -"Технички, можете мапирати било који Exchange објекат у Zammad кориснички " -"објекат (ово такође функционише и за прилагођене објекте!)." +#: ../system/core-workflows/condition-operators.rst:52 +msgid "is any of" +msgstr "је један од" -#: ../system/integrations/exchange.rst:35 -msgid "" -"If the SSL verification fails while connecting to Exchange, Zammad will ask " -"you to turn it off temporarily." -msgstr "" -"Уколико SSL провера не успе током остваривања везе са Exchange-ом, Zammad ће " -"вас питати да је привремено искључите." +#: ../system/core-workflows/condition-operators.rst:53 +msgid "Matches if content is equal to any of specified values." +msgstr "Подудара се ако је садржај једнак једној од датих вредности." -#: ../system/integrations/exchange.rst:38 -msgid "" -"Please be aware that **turning off SSL verification is a security risk**. It " -"should only be used temporarily or for testing purposes. If turned off, " -"there is no verification of the certificate, which means that every " -"presented certificate will be accepted." -msgstr "" -"Имајте на уму да **искључивање SSL провере носи безбедносни ризик**. Требало " -"би је искључити само привремено или ради тестирања. Уколико је искључена, " -"сертификати неће бити верификовани, што значи да ће било који достављени " -"сертификат бити признат." +#: ../system/core-workflows/condition-operators.rst:54 +msgid "is modified" +msgstr "је измењено" -#: ../system/integrations/exchange.rst:43 -msgid "" -"After pressing Continue, Zammad will check if the configuration is okay. You " -"can then enable Exchange and start your first sync. The sync will then run " -"hourly - if you need to change mappings or the address book(s), you can " -"change the configuration at any time." -msgstr "" -"Након што кликнете на Настави, Zammad ће проверити да ли је конфигурација у " -"реду. Затим можете омогућити Exchange и започети своју прву синхронизацију. " -"Синхронизација ће се тада одвијати сваки сат - ако треба да промените " -"мапирања или адресаре, можете променити подешавања у било ком тренутку." +#: ../system/core-workflows/condition-operators.rst:55 +msgid "Matches if content is modified." +msgstr "Подудара се ако је садржај промењен." -#: ../system/integrations/exchange.rst:50 -msgid "" -"After the sync has finished, you can find the new Exchange contacts under " -"\"Users\". Zammad integrates them just as normal users." -msgstr "" -"Када се синхронизација заврши, нове Exchange контакте можете пронаћи у " -"одељку „Корисници“. Zammad их приказује баш као и обичне кориснике." +#: ../system/core-workflows/condition-operators.rst:57 +#: ../system/core-workflows/condition-operators.rst:61 +msgid "True from the moment of changing content until form submit." +msgstr "Тачно од тренутка промене садржаја до слања форме." -#: ../system/integrations/exchange.rst:55 -msgid "" -"In some cases you might see unique IDs as \"Login\" instead of the email " -"address. This is normal and doesn't affect the login or email mapping for " -"that entry." -msgstr "" -"У неким случајевима можда ћете видети јединствене ID корисника као -ове као " -"„Пријава“ уместо имејл адресе. Ово је очекивано и не утиче на пријављивање " -"или мапирање имејл адреса за тај унос." +#: ../system/core-workflows/condition-operators.rst:58 +msgid "is modified to" +msgstr "је промењено на" -#: ../system/integrations/github.rst:4 -msgid "" -"Use GitHub integration to track GitHub issues directly within Zammad " -"tickets. Add issue hyperlinks and get a live summary of metadata like status " -"(open/closed), assignee, labels, and more." -msgstr "" -"Користите GitHub интеграцију да бисте пратили извештаје на GitHub-у директно " -"у оквиру Zammad тикета. Додајте линкове на извештаје и добијте директан " -"резиме мета података као што су статус (отворен/затворен), прималац, ознаке " -"и још много тога." +#: ../system/core-workflows/condition-operators.rst:59 +msgid "Matches if content is modified to a specific value." +msgstr "Подудара се ако је садржај промењен на дату вредност." -#: ../system/integrations/github.rst:8 -msgid "Please note that our GitHub integration does not support pull requests." -msgstr "" -"Обратите пажњу да наша GitHub интеграција не подржава pull request-ове." +#: ../system/core-workflows/condition-operators.rst:62 +msgid "is none of" +msgstr "није ниједан од" -#: ../system/integrations/github.rst:None -msgid "Integration page for GitHub" -msgstr "Страница GitHub интеграције" +#: ../system/core-workflows/condition-operators.rst:63 +msgid "Matches if content is none of any specified values." +msgstr "Подудара се ако садржај није једнак ниједног од датих вредности." -#: ../system/integrations/github.rst:18 -msgid "" -"In your GitHub settings, create a new API token under **Developer settings > " -"Personal access tokens > Generate new token**. Leave the **Scopes** section " -"empty." -msgstr "" -"У GitHub подешавањима направите нови API кључ под **Developer settings > " -"Personal access tokens > Generate new token**. Оставите одељак **Scopes** " -"празан." +#: ../system/core-workflows/condition-operators.rst:65 +msgid "Matches if content is not equal to a specified value." +msgstr "Подудара се ако садржај није једнак датој вредности." -#: ../system/integrations/github.rst:0 ../system/integrations/gitlab.rst:0 -msgid "Screencast showing how to create a new API token" -msgstr "Снимак екрана који показује како да направите нови API кључ" +#: ../system/core-workflows/condition-operators.rst:67 +msgid "Matches if content is present." +msgstr "Подудара се ако садржај постоји." -#: ../system/integrations/github.rst:27 -msgid "Create a new API key with no scopes/privileges." -msgstr "Направите нови API кључ без привилегија." +#: ../system/core-workflows/condition-operators.rst:68 +msgid "just changed" +msgstr "управо измењено" -#: ../system/integrations/github.rst:29 -msgid "🔒 **Will this work for private repos?**" -msgstr "🔒 **Да ли ће ово радити за приватне репозиторије?**" +#: ../system/core-workflows/condition-operators.rst:69 +msgid "Matches if content has changed." +msgstr "Подудара се ако је садржај измењен." -#: ../system/integrations/github.rst:31 +#: ../system/core-workflows/condition-operators.rst:71 +#: ../system/core-workflows/condition-operators.rst:75 msgid "" -"No. To link private repo issues, **use the** ``repo`` **scope instead**. " -"Bear in mind that the resulting token will have `lots of permissions that it " -"doesn't actually need `_, which presents a security risk if your token ever falls into " -"the wrong hands." +"Only true for the moment of changing content until next form field action/" +"click." msgstr "" -"Не. Да бисте повезали извештаје у приватним репозиторијима, **користите** " -"**scope** ``repo``. Имајте на уму да ће резултујући кључ имати `доста " -"дозвола које му заправо нису потребне `_, што може представљати безбедносни ризик ако " -"ваш кључ икада падне у погрешне руке." +"Тачно само од тренутка измене садржаја до следеће акције/клика поља форме." -#: ../system/integrations/github.rst:37 -msgid "" -"Unfortunately, because of how GitHub's OAuth token scopes are set up, this " -"is the only way to link issues on private repos." -msgstr "" -"Нажалост, због начина на који се GitHub OAuth кључеви генеришу, ово је " -"једини начин да повежете извештаје у приватним репозиторијумима." +#: ../system/core-workflows/condition-operators.rst:72 +msgid "just changed to" +msgstr "је управо измењено на" -#: ../system/integrations/github.rst:40 -msgid "Enter your new API token in Zammad and enable GitHub integration." -msgstr "Унесите свој нови API кључ у Zammad и укључите GitHub интеграцију." +#: ../system/core-workflows/condition-operators.rst:73 +msgid "Matches if content has changed to a specified value." +msgstr "Подудара се ако је садржај измењен на дату вредност." -#: ../system/integrations/github.rst:0 -msgid "Screencast showing how to configure Zammad's GitHub integration" -msgstr "Снимак екрана како подесити Zammad-ову GitHub интеграцију" +#: ../system/core-workflows/condition-operators.rst:76 +msgid "matches regex" +msgstr "задовољава регуларни израз" -#: ../system/integrations/github.rst:47 -msgid "" -"Use the default API endpoint (``https://api.github.com/graphql``) unless " -"you're using GitHub Enterprise Server." -msgstr "" -"Користите подразумевану API путању (``https://api.github.com/graphql``) осим " -"ако не користите GitHub Enterprise Server." +#: ../system/core-workflows/condition-operators.rst:77 +msgid "Matches if value fits to regex rule." +msgstr "Подудара се ако се садржај поклапа са регуларним изразом." -#: ../system/integrations/github.rst:50 -msgid "" -"Once completed, a new GitHub issues tab will appear in the ticket pane. 🎉" -msgstr "" -"По завршетку, нови језичак са GitHub извештајима ће се појавити у панелу " -"тикета. 🎉" +#: ../system/core-workflows/condition-operators.rst:79 +msgid "Matches if no content is present." +msgstr "Подудара се ако садржај не постоји." -#: ../system/integrations/github.rst:59 ../system/integrations/gitlab.rst:52 -msgid "Token verification is taking a long time" -msgstr "Провера кључа траје дуго" +#: ../system/core-workflows/condition-operators.rst:80 +msgid "starts with" +msgstr "почиње са" -#: ../system/integrations/github.rst:56 ../system/integrations/gitlab.rst:49 -msgid "" -"Slight delays are normal (<2 min.), especially for systems under heavy load." -msgstr "" -"Мала кашњења су очекивана (<2 мин.), посебно за системе под великим " -"оптерећењем." +#: ../system/core-workflows/condition-operators.rst:81 +msgid "Matches if content starts with specified value." +msgstr "Подудара се ако садржај почиње са датом вредности." -#: ../system/integrations/github.rst:58 -msgid "" -"Self-hosted administrators, please check your network settings to ensure " -"that your Zammad server can reach ``api.github.com``." -msgstr "" -"Администратори који сами хостујете, проверите мрежна подешавања да бисте " -"били сигурни да ваш Zammad сервер може да приступи ``api.github.com``." +#: ../system/core-workflows/condition-operators.rst:82 +msgid "starts with one of" +msgstr "почиње са једним од" -#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 -msgid "I reloaded the page and now the API token is gone" -msgstr "АПИ кључ је нестао по поновном учитавању странице" +#: ../system/core-workflows/condition-operators.rst:83 +msgid "Matches if content starts with one of the specified values." +msgstr "Подудара се ако садржај почиње са једном од датих вредности." -#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 -msgid "" -"This may indicate that Zammad is still verifying your API token. Try " -"reloading the page again in a couple minutes." -msgstr "" -"Ово може да се деси док Zammad још увек проверава ваш API кључ. Покушајте " -"поново да учитате страницу за неколико минута." +#: ../system/core-workflows/condition-operators.rst:84 +msgid "till (relative)" +msgstr "до (релативно)" -#: ../system/integrations/gitlab.rst:2 -msgid "GitLab" -msgstr "GitLab" +#: ../system/core-workflows/condition-operators.rst:85 +msgid "Matches if date/time is before a period of time before an event." +msgstr "Подудара се ако је датум/време пре датог периода пре догађаја." -#: ../system/integrations/gitlab.rst:4 -msgid "" -"Use GitLab integration to track GitLab issues directly within Zammad " -"tickets. Add issue hyperlinks and get a live summary of metadata like status " -"(open/closed), assignee, labels, and more." -msgstr "" -"Користите GitLab интеграцију да бисте пратили GitLab извештаје директно у " -"оквиру Zammad тикета. Додајте линкове на извештаје и добијте директан резиме " -"мета података као што су статус (отворен/затворен), прималац, ознаке и још " -"много тога." +#: ../system/core-workflows/condition-operators.rst:86 +msgid "today" +msgstr "данас" -#: ../system/integrations/gitlab.rst:8 -msgid "" -"Please note that our GitLab integration does not support merge requests." -msgstr "" -"Обратите пажњу да наша GitLab интеграција не подржава merge request-ове." +#: ../system/core-workflows/condition-operators.rst:87 +msgid "Matches if date/time is today." +msgstr "Подудара се ако је датум/време у току данашњег дана." -#: ../system/integrations/gitlab.rst:None -msgid "Integration page for GitLab" -msgstr "Страница GitLab интеграције" +#: ../system/core-workflows/condition-operators.rst:88 +msgid "within last (relative)" +msgstr "у последњих (релативно)" -#: ../system/integrations/gitlab.rst:18 +#: ../system/core-workflows/condition-operators.rst:89 msgid "" -"In your GitLab preferences, create a new API token under **Access Tokens**." -msgstr "У GitLab подешавањима, направите нови API кључ под **Access Tokens**." - -#: ../system/integrations/gitlab.rst:20 -msgid "Under **Select scopes**, choose ``read_api`` only." -msgstr "У одељку **Select scopes** изаберите само ``read_api``." +"Matches if date/time content is within specified period of time before now." +msgstr "Подудара се ако је датум/време унутар датог периода у прошлости." -#: ../system/integrations/gitlab.rst:27 -msgid "🔒 **If you wish to link issues on any private repos...**" -msgstr "" -"🔒 **Ако желите да повежете извештаје из било ког приватног репозиторија...**" +#: ../system/core-workflows/condition-operators.rst:91 +msgid "within next (relative)" +msgstr "у следећих (релативно)" -#: ../system/integrations/gitlab.rst:29 -msgid "Your API token must belong to an account with access to those repos." -msgstr "Ваш API кључ мора припадати налогу са приступом тим репозиторијумима." +#: ../system/core-workflows/condition-operators.rst:92 +msgid "" +"Matches if date/time content is within specified period of time after now." +msgstr "Подудара се ако је датум/време унутар датог периода у будућности." -#: ../system/integrations/gitlab.rst:31 -msgid "Enter your new API token in Zammad and enable GitLab integration." -msgstr "Унесите свој нови API кључ у Zammad и укључите GitLab интеграцију." +#: ../system/core-workflows/how-do-they-work.rst:2 +msgid "How do they work?" +msgstr "Како то уствари функционише?" -#: ../system/integrations/gitlab.rst:0 -msgid "Screencast showing how to configure Zammad's GitLab integration" +#: ../system/core-workflows/how-do-they-work.rst:4 +msgid "" +"Core Workflows are executed according to their priority. If two workflows " +"have the same priority, they are executed in alphabetical order based on " +"their **name**." msgstr "" -"Снимак екрана који показује како да подесите Zammad-ову GitLab интеграцију" +"Радни токови се процењују по приоритету. Ако два радна тока имају исти " +"приоритет, онда се процењују по абецедном реду према свом **називу**." -#: ../system/integrations/gitlab.rst:40 +#: ../system/core-workflows/how-do-they-work.rst:8 msgid "" -"Use the default API endpoint (``https://gitlab.com/api/graphql``) unless " -"you're a self-hosted GitLab user." +"Because of the way Core Workflows work, all changes to attributes are " +"checked with the application server - please see :doc:`limitations` for " +"possible issues." msgstr "" -"Користите подразумевану API путању (``https://gitlab.com/api/graphql``) осим " -"ако хостујете GitLab сами." +"Због начина на који радни токови функционишу, све измене атрибута се " +"проверавају на серверу апликације – погледајте :doc:`ограничења " +"` за могуће проблеме." -#: ../system/integrations/gitlab.rst:43 +#: ../system/core-workflows/how-do-they-work.rst:12 msgid "" -"Once completed, a new GitLab issues tab will appear in the ticket pane. 🎉" +"Below we're talking about settings that are important and not self-" +"explanatory." msgstr "" -"По завршетку, нови језичак са GitLab исвештајима ће се појавити у панелу " -"тикета. 🎉" +"У наставку говоримо о подешавањима која имају утицај и нису сама по себи " +"разумљива." -#: ../system/integrations/gitlab.rst:51 +#: ../system/core-workflows/how-do-they-work.rst:17 msgid "" -"Self-hosted administrators, please check your network settings to ensure " -"that your Zammad server can reach ``gitlab.com``." +"Choose the object context you want to run the workflow in. This will decide " +"on your available attributes and actions." msgstr "" -"Администратори који сами хостујете, проверите мрежна подешавања да бисте " -"били сигурни да ваш Zammad сервер може да приступи ``gitlab.com``." +"Изаберите контекст објекта у којем желите да покренете радни ток. Ово ће " +"утицати на доступне атрибуте и радње." -#: ../system/integrations/i-doit.rst:2 -msgid "i-doit" -msgstr "i-doit" +#: ../system/core-workflows/how-do-they-work.rst:20 +msgid "Ticket objects also have access to the ticket customer." +msgstr "Објекти тикета такође имају приступ клијенту тикета." -#: ../system/integrations/i-doit.rst:4 +#: ../system/core-workflows/how-do-they-work.rst:25 msgid "" -"`i-doit `_ is an open-source **configuration " -"management database** - in other words, a tool for keeping tabs on every " -"single piece of your physical and digital infrastructure, from network " -"equipment to virtual machines on down to the faceplates on your rack shelves " -"and more." +"Choose in which situation the workflow is applied. Contexts can be combined " +"to avoid duplicate workflows." msgstr "" -"`i-doit `_ је **база података за управљање " -"конфигурацијом** отвореног кода — другим речима, алатка за праћење сваког " -"појединачног дела ваше физичке и дигиталне инфраструктуре, од мрежне опреме " -"до виртуелних машина све до контролних табли на вашим серверима и још много " -"тога." +"Изаберите у којој ситуацији се примењује радни ток. Контексти се могу " +"комбиновати да би се смањио број токова." -#: ../system/integrations/i-doit.rst:10 +#: ../system/core-workflows/how-do-they-work.rst:30 +msgid "Creation mask" +msgstr "Форма за отварање" + +#: ../system/core-workflows/how-do-they-work.rst:29 msgid "" -"What's that got to do with Zammad? Well, if you used tickets to track issues " -"with all that hardware, you might start wishing there was a way they could " -"talk to each other." +"If selected, your conditions and actions will affect all applicable creation " +"masks." msgstr "" -"Какве то везе има са Zammad-ом? Па, ако бисте користили тикете за праћење " -"проблема са свим тим хардвером, можда бисте желели да постоји начин да " -"комуницирају једни са другима." - -#: ../system/integrations/i-doit.rst:14 -msgid "Zammad gives you two:" -msgstr "Zammad вам даје два:" - -#: ../system/integrations/i-doit.rst:17 -msgid "1. Add i-doit Links to Zammad Tickets" -msgstr "1. Додавање i-doit веза ка Zammad тикетима" - -#: ../system/integrations/i-doit.rst:20 ../system/integrations/i-doit.rst:80 -msgid "What Users See" -msgstr "Шта корисници виде" +"По избору, ваши услови и радње ће утицати на све доступне форме додавања." -#: ../system/integrations/i-doit.rst:26 -msgid "i-doit integration in Zammad's ticket pane" -msgstr "i-doit интеграција у Zammad-овом панелу тикета" +#: ../system/core-workflows/how-do-they-work.rst:34 +msgid "Edit mask" +msgstr "Форма за измену" -#: ../system/integrations/i-doit.rst:26 +#: ../system/core-workflows/how-do-they-work.rst:33 msgid "" -"The i-doit integration will appear under a new 🖨 tab in the ticket pane." +"If selected, your conditions and actions will affect all applicable edit " +"masks." msgstr "" -"i-doit интеграција ће се појавити под новим 🖨 језичком у панелу тикета." +"По избору, ваши услови и радње ће утицати на све доступне форме за уређивање." -#: ../system/integrations/i-doit.rst:28 +#: ../system/core-workflows/how-do-they-work.rst:39 msgid "" -"i-doit integration puts a new tab in Zammad's ticket pane where you can add " -"links to existing i-doit devices for easy reference. (See our :user-docs:" -"`user documentation ` to learn " -"how it works in practice)." +"Zammad differentiates between selected and saved conditions. These can be " +"combined wherever needed." msgstr "" -"i-doit интеграција омогућава нов језичак у Zammad-овом панелу тикета где " -"можете додати везе на постојеће i-doit уређаје ради лакшег референцирања. " -"(Погледајте нашу :user-docs:`корисничку документацију ` да бисте сазнали како то функционише у пракси)." +"Zammad прави разлику између одабраних и сачуваних услова. Они се могу " +"комбиновати где год је то потребно." -#: ../system/integrations/i-doit.rst:36 ../system/integrations/i-doit.rst:93 -msgid "How to Set it Up" -msgstr "Како подесити" +#: ../system/core-workflows/how-do-they-work.rst:42 +msgid "**⚠️ Restrict workflows to specific roles if needed!**" +msgstr "**⚠️ Ограничите токове на одговарајуће улоге ако је потребно!**" -#: ../system/integrations/i-doit.rst:38 +#: ../system/core-workflows/how-do-they-work.rst:44 msgid "" -"It requires i-doit's `API Add-on `_. Make sure to have it properly set up. Use the following setting:" +"By default and unless configured in conditions, workflow rules are executed " +"for **all roles**. This also affects your customers!" msgstr "" -"Захтева i-doit `API додатак `_. Обавезно проверите да ли је исправно подешен. Користите следећа " -"подешавања:" - -#: ../system/integrations/i-doit.rst:42 -msgid "Active: ``Yes``" -msgstr "Active: ``Yes``" +"Подразумевано, осим ако нису подешене у условима, правила радног тока се " +"процењују за **све улоге**. Ово такође утиче на ваше клијенте!" -#: ../system/integrations/i-doit.rst:43 -msgid "Enforce authentication by username and password: ``No``" -msgstr "Enforce authentication by username and password: ``No``" +#: ../system/core-workflows/how-do-they-work.rst:50 +msgid "Selected Conditions" +msgstr "Одабрани услови" -#: ../system/integrations/i-doit.rst:45 +#: ../system/core-workflows/how-do-they-work.rst:48 msgid "" -"To set it up, enable the integration in the Zammad admin panel under " -"**System > Integrations > i-doit**:" +"These conditions are based on form values and match if an appropriate " +"selection is made (e.g. choosing another group in the ticket without " +"saving). This applies for drafts (active selection) and currently saved " +"values." msgstr "" -"Да бисте је подесили, прво укључите интеграцију у Zammad администраторском " -"интерфејсу под **Систем > Интеграције > i-doit**:" +"Ови услови су базирани на вредностима форме и поклапају се ако је направљен " +"одговарајући избор (нпр. избор друге групе у тикету без снимања). Ово важи " +"за нацрте (активан избор) и тренутно сачуване вредности." -#: ../system/integrations/i-doit.rst:None -msgid "i-doit settings within the integration pages" -msgstr "i-doit подешавања у оквиру страница за интеграцију" +#: ../system/core-workflows/how-do-they-work.rst:64 +msgid "Saved Conditions" +msgstr "Сачувани услови" -#: ../system/integrations/i-doit.rst:53 -msgid "The root URL of your i-doit installation." -msgstr "Основни URL ваше i-doit инсталације." +#: ../system/core-workflows/how-do-they-work.rst:53 +msgid "" +"These conditions only match if the selected values are stored in the " +"database. It ignores the current value or selection of the field, as long as " +"the changes are not saved (e.g. performing field operations for an existing " +"ticket, which is viewed/opened by an agent)." +msgstr "" +"Ови услови се поклапају само ако изабране вредности сачуване у бази " +"података. Игноришу тренутну вредност или избор поља, све док измене нису " +"снимљене (нпр. управљањем пољима постојећег тикета, који је у прегледу " +"оператера)." -#: ../system/integrations/i-doit.rst:62 -msgid "API token" -msgstr "API кључ" +#: ../system/core-workflows/how-do-they-work.rst:60 +msgid "" +"Keep in mind that the value has to be available in the situation where you " +"need it. Otherwise the condition won't match." +msgstr "" +"Имајте на уму да вредност мора бити доступна у ситуацији у којој вам је " +"потребна. У супротном, услов се неће подударати." -#: ../system/integrations/i-doit.rst:56 +#: ../system/core-workflows/how-do-they-work.rst:63 msgid "" -"Found in the i-doit admin panel under **Interfaces / external data > JSON-" -"RPC API > Common Settings**." +"Example: you can't perform any actions with *saved condition* on a ticket in " +"creation, because there are no saved values at that time." msgstr "" -"Налази се у i-doit административном панелу под **Interfaces / external data " -"> JSON-RPC API > Common Settings**." +"Пример: не можете извршити акције са *сачуваним условима* при отварању " +"тикета, јер нема снимљених вредности у том тренутку." -#: ../system/integrations/i-doit.rst:0 -msgid "i-doit administration interface with API configuration" -msgstr "i-doit административни интерфејс са API конфигурацијом" +#: ../system/core-workflows/how-do-they-work.rst:66 +msgid "" +"You can find a description of the condition operators for core workflows :" +"doc:`here `." +msgstr "" +"Опис оператора услова за радне токове можете пронаћи :doc:`овде `." -#: ../system/integrations/i-doit.rst:67 -msgid "Client ID" -msgstr "Клијент ID" +#: ../system/core-workflows/how-do-they-work.rst:72 +msgid "" +"Which actions should we run on the relevant fields? The possible actions " +"depend on the object type. However, usually you can at least change the " +"visibility and whether the field is mandatory." +msgstr "" +"Које радње треба да спроводимо на релевантним пољима? Могуће радње зависе од " +"типа објекта, међутим, обично можете барем променити видљивост или то да ли " +"је поље обавезно." -#: ../system/integrations/i-doit.rst:65 -msgid "A unique name to identify Zammad within i-doit." -msgstr "Јединствени назив за идентификацију Zammad-а унутар i-doit-а." +#: ../system/core-workflows/how-do-they-work.rst:76 +msgid "Be aware that actions are not available for **related** context." +msgstr "Обратите пажњу да радње нису доступне за **повезане** објекте." -#: ../system/integrations/i-doit.rst:67 -msgid "(Zammad does not require you to enter a value here, but i-doit might!)" +#: ../system/core-workflows/how-do-they-work.rst:78 +msgid "" +"**Example:** Let's assume you are working in the ticket context. While you " +"can have customer *conditions*, you *can't adjust* objects with actions in " +"that scope. That's because this wouldn't have any impact on the ticket " +"dialog. Of course all ticket attributes (state, owner, ...) are available." msgstr "" -"(Zammad не захтева од вас да унесете вредност овде, али i-doit би могао!)" +"**Пример:** Рецимо да радите у контексту тикета. Иако можете имати " +"корисничке услове, не можете да прилагођавате објекте са радњама у том " +"обиму. Ово је из разлога што неће имати било каквог утицаја на дијалог " +"тикета. Наравно, сви атрибути тикета (стање, власник, ...) биће доступни." -#: ../system/integrations/i-doit.rst:70 +#: ../system/core-workflows/how-do-they-work.rst:84 msgid "" -"Here you can decide if the certificate of your i-doit system has to be " -"verified or not. In case you are using custom certificates, please have a " -"look at :doc:`how to add them to Zammad `." +"Please also have a look at our :doc:`limitations` to be safe from surprises." msgstr "" -"Овде можете одлучити да ли ће сертификат вашег i-doit система бити проверен " -"или не. У случају да користите прилагођене сертификате, молимо погледајте и :" -"doc:`како да их додате у Zammad `." +"Погледајте и наша :doc:`ограничења ` да не би било непријатних " +"изненађења." -#: ../system/integrations/i-doit.rst:77 -msgid "2. List / Create Zammad Tickets in i-doit" -msgstr "2. Излистајте / Додајте Zammad тикете у i-doit" +#: ../system/core-workflows/how-do-they-work.rst:88 +msgid "Available Operators" +msgstr "Доступни оператори" -#: ../system/integrations/i-doit.rst:None -msgid "Zammad integration in i-doit's device view" -msgstr "Zammad интеграција у приказу уређаја i-doit-а" +#: ../system/core-workflows/how-do-they-work.rst:90 +msgid "The availability of operators depends on the object type and scope." +msgstr "Доступност оператора зависи од типа објекта и обима." -#: ../system/integrations/i-doit.rst:86 +#: ../system/core-workflows/how-do-they-work.rst:94 msgid "" -"i-doit's ticket system integration gives you a way to see all the tickets " -"for a given device without ever leaving i-doit. (See our :user-docs:`user " -"documentation ` to learn how it " -"works in practice)." +"Please note that actions may or may not restrict API based access to " +"attributes. We're displaying the following icons for your overview to " +"understand these limits better:" msgstr "" -"Интеграција i-doit система тикета даје вам начин да видите све тикете за " -"дати уређај без напуштања i-doit-а. (Погледајте нашу :user-docs:`корисничку " -"документацију ` да бисте сазнали " -"како то функционише у пракси)." +"Имајте на уму да радње могу али и не морају ограничити приступ атрибутима " +"преко API-ја. За бољи преглед, приказујемо следеће иконице да бисте боље " +"разумели ова ограничења:" -#: ../system/integrations/i-doit.rst:95 -msgid "" -"Enable this integration in the i-doit admin panel under **Interfaces / " -"external data > Trouble Ticket System (TTS) > Configuration**:" -msgstr "" -"Укључите ову интеграцију у i-doit административном панелу под **Interfaces / " -"external data > Trouble Ticket System (TTS) > Configuration**:" +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|api| This icon indicates the action affects the API." +msgstr "|api| Ова иконица означава да радња утиче на API." -#: ../system/integrations/i-doit.rst:None -msgid "i-doit administration interface with TTS configuration" -msgstr "i-doit административни интерфејс са TTS конфигурацијом" +#: ../system/core-workflows/how-do-they-work.rst:163 +msgid "api" +msgstr "api" -#: ../system/integrations/i-doit.rst:104 -msgid "TTS-Type" -msgstr "TTS-Type" +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|ui| This icon indicates the action only affects the web interface." +msgstr "|ui| Ова иконица означава да радња утиче само на кориснички интерфејс." -#: ../system/integrations/i-doit.rst:104 -msgid "``Zammad``" -msgstr "``Zammad``" +#: ../system/core-workflows/how-do-they-work.rst:167 +msgid "ui" +msgstr "ui" -#: ../system/integrations/i-doit.rst:115 -msgid "Username / Password" -msgstr "Корисничко име / лозинка" +#: ../system/core-workflows/how-do-they-work.rst:102 +msgid "show |ui|" +msgstr "прикажи |ui|" -#: ../system/integrations/i-doit.rst:107 -msgid "Login credentials for a Zammad agent." -msgstr "Креденцијали за пријаву Zammad оператера." +#: ../system/core-workflows/how-do-they-work.rst:102 +msgid "Display the chosen field. Allows setting of values." +msgstr "Прикажи дотично поље. Омогућава подешавање вредности." -#: ../system/integrations/i-doit.rst:109 +#: ../system/core-workflows/how-do-they-work.rst:109 +msgid "hide |ui|" +msgstr "сакриј |ui|" + +#: ../system/core-workflows/how-do-they-work.rst:105 msgid "" -"This agent must have **read permission** for all :doc:`groups ` that plan on using the i-doit integration." +"Hide the chosen field. However, it technically still allows setting the " +"field." msgstr "" -"Овај оператер мора имати **дозволу за читање** за све :doc:`групе ` које планирају да користе i-doit интеграцију." +"Сакриј дотично поље. Међутим, технички и даље дозвољава подешавање вредности " +"поља." -#: ../system/integrations/i-doit.rst:113 +#: ../system/core-workflows/how-do-they-work.rst:108 msgid "" -"You may even wish to create a dedicated agent account just for this " -"integration (otherwise, if the agent ever changes her password, you will " -"have to remember to update it here)." +"Please note that the field is **not** gone and still contains an existing " +"value (if set)! Consider *remove* instead, if you want this field to be gone." msgstr "" -"Можда ћете чак желети да направите наменски налог оператера само за ову " -"интеграцију (у супротном, ако оператер икада промени своју лозинку, мораћете " -"да се сетите да је освежите и овде)." +"Имајте на уму да поље **неће** нестати и још увек садржи вредност коју " +"пружа! Можда бисте желели да размислите о oператору *уклони* уместо њега." -#: ../system/integrations/i-doit.rst:117 -msgid "URL incl. protocol" -msgstr "URL адреса укључујући и протокол" +#: ../system/core-workflows/how-do-they-work.rst:112 +msgid "remove |ui|" +msgstr "уклони |ui|" -#: ../system/integrations/i-doit.rst:118 -msgid "``https://your.zammad.domain``" -msgstr "``https://your.zammad.domain``" +#: ../system/core-workflows/how-do-they-work.rst:112 +msgid "Entirely removes the field. The field value will not be evaluated." +msgstr "Потпуно уклања поље. Вредност поља неће бити пружена." -#: ../system/integrations/index.rst:2 -msgid "Integrations" -msgstr "Интеграције" +#: ../system/core-workflows/how-do-they-work.rst:115 +msgid "set mandatory |ui| |api|" +msgstr "постави обавезно |ui| |api|" -#: ../system/integrations/index.rst:4 -msgid "" -"Zammad offers numerous integrations that add rich features to your instance." -msgstr "" -"Zammad нуди бројне интеграције које додају богате функције вашој инстанци." +#: ../system/core-workflows/how-do-they-work.rst:115 +msgid "Sets the field to mandatory." +msgstr "Поставља поље на обавезно." -#: ../system/integrations/index.rst:6 -msgid "We're still working on this part of our documentation, stay tight!" -msgstr "Још увек радимо на овом делу наше документације, само што није готово!" +#: ../system/core-workflows/how-do-they-work.rst:118 +msgid "set optional |ui| |api|" +msgstr "постави необавезно |ui| |api|" -#: ../system/integrations/index.rst:10 -msgid "Integrations for Phone Systems" -msgstr "Интеграције за телефонске централе" +#: ../system/core-workflows/how-do-they-work.rst:118 +msgid "Sets the field to optional." +msgstr "Поставља поље на опционо." -#: ../system/integrations/index.rst:14 -msgid "" -"Your VoIP provider or telephony system is not listed? Possibly your provider " -"supports Zammad by using the generic CTI - if you're unsure ask your " -"provider." -msgstr "" -"Ваш VoIP провајдер или телефонски систем није наведен? Можда ваш провајдер " -"подржава Zammad користећи генерички CTI - ако нисте сигурни питајте свог " -"провајдера." +#: ../system/core-workflows/how-do-they-work.rst:124 +msgid "add option |ui| |api|" +msgstr "додај опцију |ui| |api|" -#: ../system/integrations/index.rst:18 +#: ../system/core-workflows/how-do-they-work.rst:121 +msgid "Allows adding options to tree selects or selects." +msgstr "Омогућава додавање опција у пољa за избор (стабла)." + +#: ../system/core-workflows/how-do-they-work.rst:123 msgid "" -"Provider does not support Zammad? Consider creating a `feature request in " -"the Zammad Community `_." +"You have to use the \"remove option\" before performing this action. It " +"allows you to use *existing* configured values." msgstr "" -"Провајдер не подржава Zammad? Размислите о слању `захтева за нову функцију " -"на Zammad Community форуму `_." - -#: ../system/integrations/index.rst:31 -msgid "Integrations for Authentication and Customers" -msgstr "Интеграције за аутентификацију и клијенте" - -#: ../system/integrations/index.rst:44 -msgid "Integrations for Monitoring Systems" -msgstr "Интеграције за системе за надзор" - -#: ../system/integrations/index.rst:46 -msgid "This section currently misses the following integrations:" -msgstr "У овом одељку тренутно недостају следеће интеграције:" - -#: ../system/integrations/index.rst:48 -msgid "Icinga" -msgstr "Icinga" +"Ово захтева да се опције претходно сакрију (уклони опцију). Омогућава " +"коришћење *постојећих* вредности." -#: ../system/integrations/index.rst:49 -msgid "Monit" -msgstr "Monit" +#: ../system/core-workflows/how-do-they-work.rst:128 +msgid "remove option |ui| |api|" +msgstr "уклони опцију |ui| |api|" -#: ../system/integrations/index.rst:50 -msgid "Nagios" -msgstr "Nagios" +#: ../system/core-workflows/how-do-they-work.rst:127 +msgid "" +"Allows removing options from tree selects or selects. It allows you to use " +"*existing* configured values." +msgstr "" +"Омогућава уклањање опција из поља једноструког и вишеструког избора. " +"Омогућава коришћење *постојећих* вредности." -#: ../system/integrations/index.rst:60 -msgid "Integrations for Issue Trackers" -msgstr "Интеграције за праћење проблема" +#: ../system/core-workflows/how-do-they-work.rst:134 +msgid "set fixed to |ui| |api|" +msgstr "постави на вредност |ui| |api|" -#: ../system/integrations/index.rst:70 -msgid "Other Integrations" -msgstr "Додатне интеграције" +#: ../system/core-workflows/how-do-they-work.rst:131 +msgid "Reduces the available options by your selection." +msgstr "Ограничава доступне опције по вашем избору." -#: ../system/integrations/index.rst:72 +#: ../system/core-workflows/how-do-they-work.rst:133 msgid "" -"This section will hold any other integration that can't be grouped up (yet)." +"This reduces your workflows in terms of *add option* and *remove option*." msgstr "" -"Овај одељак садржи све додатне интеграције које се (још увек) не могу " -"груписати заједно." +"Ово може смањити број ваших радних токова који користе *додај опцију* и " +"*уклони опцију*." -#: ../system/integrations/ldap/index.rst:2 -msgid "LDAP / Active Directory" -msgstr "LDAP / Active Directory" +#: ../system/core-workflows/how-do-they-work.rst:137 +msgid "fill in |ui|" +msgstr "попуни |ui|" -#: ../system/integrations/ldap/index.rst:4 -msgid "" -"Zammad comes with a powerful LDAP integration that allows you to have a " -"single source of truth. By this you reduce the number of login credentials " -"your user has to remember." +#: ../system/core-workflows/how-do-they-work.rst:137 +msgid "Allows filling in of string and integer fields with your values." msgstr "" -"Zammad долази са моћном LDAP интеграцијом која вам омогућава да имате " -"јединствени извор корисника. Тиме смањујете број креденцијала за пријаву " -"које ваш корисник мора да запамти." +"Омогућава попуњавање поља текста и целобројних поља са вашим вредностима." -#: ../system/integrations/ldap/index.rst:10 +#: ../system/core-workflows/how-do-they-work.rst:141 +msgid "fill in empty |ui|" +msgstr "попуни празно |ui|" + +#: ../system/core-workflows/how-do-they-work.rst:140 msgid "" -"The LDAP source is also a perfect candidate for Zammad's :docs:`Kerberos " -"Single Sign-On ` but also works as addition " -"to other :doc:`/settings/security/third-party`." +"Allows filling in of string and integer fields with your values **if the " +"field is empty**." msgstr "" -"LDAP извор је такође савршен кандидат за Zammad-ову :docs:`јединствену " -"пријаву путем Kerberos `, али такође " -"функционише и као додатак другим :doc:`аутентификацијама путем трећег лица `." - -#: ../system/integrations/ldap/index.rst:None -msgid "Zammands LDAP management page" -msgstr "Страница за подешавање LDAP интеграције" +"Омогућава попуњавање поља текста и целобројних поља са вашим вредностима " +"**ако су поља празна**." -#: ../system/integrations/ldap/index.rst:25 -msgid "📝 :doc:`manage`" -msgstr "📝 :doc:`подешавање `" +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "select |ui|" +msgstr "изабери |ui|" -#: ../system/integrations/ldap/index.rst:25 -msgid "Add, modify, remove or re-arrange your LDAP-Sources as needed." +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "Select a specific value within a select, tree select or boolean field." msgstr "" -"Додајте, измените, уклоните или преуредите своје LDAP изворе по потреби." +"Изабери одређену вредност унутар поља за избор, избор стабла или логичког " +"поља." -#: ../system/integrations/ldap/index.rst:30 -msgid "Before you continue, please note the following limitations." -msgstr "Пре него што наставите, имајте на уму следећа ограничења." +#: ../system/core-workflows/how-do-they-work.rst:153 +msgid "auto select |ui|" +msgstr "аутоматски избор |ui|" -#: ../system/integrations/ldap/index.rst:32 -msgid "Mapping / Synchronizing organizations is not possible" -msgstr "Мапирање / синхронизација организација није могућа" +#: ../system/core-workflows/how-do-they-work.rst:147 +msgid "Helps users with tree select and select fields:" +msgstr "Помаже кориснику са пољима избора (стабла):" -#: ../system/integrations/ldap/index.rst:36 +#: ../system/core-workflows/how-do-they-work.rst:149 msgid "" -"You may want to consider using domain based assignments to overcome this " -"issue. Learn more on :doc:`/manage/organizations/index`." +"If the field has only one option available for selection and no value yet, " +"the value will be automatically set." msgstr "" -"Можда бисте желели да размислите о коришћењу доделе на основу домена да " -"бисте превазишли овај проблем. Сазнајте више у одељку о :doc:`организацијама " -"`." +"Ако поље има само једну опцију за избор и још увек нема вредност, вредност " +"се аутоматски поставља." -#: ../system/integrations/ldap/index.rst:39 +#: ../system/core-workflows/how-do-they-work.rst:152 msgid "" -"Zammad's LDAP sync is one way. Editing user settings or permissions may be " -"overwritten upon the next sync depending on your configuration." +"This option only works if you have one value and doesn't work if there is " +"more than one option available." msgstr "" -"Zammad-ова LDAP синхронизација је један од начина. Уређивање корисничких " -"подешавања или дозвола може бити преписано приликом следеће синхронизације у " -"зависности од ваше конфигурације." +"Овај оператор функционише само ако имате једну вредност и не делује ако има " +"више од једне опције." -#: ../system/integrations/ldap/index.rst:41 -msgid "Nested groups are not supported." -msgstr "Угнежђене групе нису подржане." +#: ../system/core-workflows/how-do-they-work.rst:157 +msgid "set readonly |ui|" +msgstr "укључи само за преглед |ui|" -#: ../system/integrations/ldap/index.rst:42 -msgid "Synchronizing user avatars from LDAP is not supported." -msgstr "Синхронизовање аватар сличица корисника путем LDAP-а није подржано." +#: ../system/core-workflows/how-do-they-work.rst:156 +msgid "" +"Allows you to display an attribute as read only (which means no changes are " +"possible)." +msgstr "" +"Омогућава вам да прикажете атрибут само за читање (readonly), што значи да " +"измене неће бити могуће." -#: ../system/integrations/ldap/index.rst:43 -msgid "Unlike user filters, group filters cannot be changed." -msgstr "За разлику од корисничких филтера, групни филтери се не могу мењати." +#: ../system/core-workflows/how-do-they-work.rst:161 +msgid "unset readonly |ui|" +msgstr "искључи само за преглед |ui|" -#: ../system/integrations/ldap/index.rst:44 +#: ../system/core-workflows/how-do-they-work.rst:160 msgid "" -"When a user originates from an LDAP server, Zammad will try to verify the " -"login credentials against LDAP first - if this fails Zammad will check its " -"local database." +"In case a workflow set the field in question to read only, you can undo this " +"with option above." msgstr "" -"Када корисник долази са LDAP сервера, Zammad ће прво покушати да провери " -"креденцијале за пријаву путем LDAP - ако ово не успе, Zammad ће проверити и " -"своју локалну базу података." +"У случају да је радни ток поставио поље на само за преглед (readonly), ово " +"можете поништити уз помоћ горњег оператора." -#: ../system/integrations/ldap/index.rst:50 +#: ../system/core-workflows/how-do-they-work.rst:172 +msgid "Stop after match" +msgstr "Заустави после поклапања" + +#: ../system/core-workflows/how-do-they-work.rst:174 msgid "" -"Users can have local passwords even if they're LDAP users! You can learn " -"more about user accounts in general on :doc:`/manage/users/index`." +"Here you can decide if other workflows are executed after the current one." msgstr "" -"Корисници могу имати локалне лозинке чак и ако су LDAP корисници! Можете " -"сазнати више о корисничким налозима уопште у одељку о :doc:`корисницима `." +"Овим можете зауставити процену накнадних радних токова после тренутног." -#: ../system/integrations/ldap/index.rst:54 +#: ../system/core-workflows/how-do-they-work.rst:176 msgid "" -"When several LDAP sources contain the same user (meaning the same email " -"address), the user in question will be updated with every source configured. " -"*The last LDAP source will win.*" +"If set to ``no`` (default), further workflows will be executed if they match " +"the condition. In this case, it is possible that your actions from the " +"current workflow can be overwritten by another workflow." msgstr "" -"Када неколико LDAP извора садржи истог корисника (што значи исту имејл " -"адресу), дотични корисник ће бити освежен из сваког подешеног извором. " -"*Последњи LDAP извор ће победити.*" +"Ако је подешено на ``не`` (подразумевано), накнадни радни токови ће бити " +"процењени ако се поклапају услови. У овом случају, могуће да ће радње из " +"тренутног радног тока бити поништене неким другим током." -#: ../system/integrations/ldap/index.rst:58 +#: ../system/core-workflows/how-do-they-work.rst:180 msgid "" -"This is subject to change with `Issue 4109 `_ in the future." +"If set to ``yes``, no further worflows will be executed after the current " +"one." msgstr "" -"Ово је подложно променама са `извештајем 4109 `_ у будућности." +"Ако је подешено на ``да``, накнадни радни токови неће бити процењени након " +"овога." -#: ../system/integrations/ldap/index.rst:60 +#: ../system/core-workflows/how-do-they-work.rst:184 +msgid "Priority" +msgstr "Приоритет" + +#: ../system/core-workflows/how-do-they-work.rst:186 msgid "" -"Synchronization statistics currently affect *all* configured LDAP sources. " -"This also applies for newly added or updated sources." +"You can define the sequence, in which the workflows are executed. The " +"default value is ``500``." msgstr "" -"Статистика синхронизације тренутно утиче на *све* подешена LDAP изворе. Ово " -"такође важи за новододате или освежене изворе." +"Можете одредити редослед у којима ће радни токови бити процењени. " +"Подразумевана вредност је ``500``." -#: ../system/integrations/ldap/index.rst:63 +#: ../system/core-workflows/how-do-they-work.rst:189 msgid "" -"This is subject to change with `Issue 4108 `_ in the future." +"The workflows are executed in ascending order by their priority. That means " +"lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." msgstr "" -"Ово је подложно променама са `извештајем 4108 `_ у будућности." +"Радни токови се процењују у узлазном редоследу према приоритету. Ово ѕначи " +"да се ниже вредности (нпр. ``100``) процењују пре виших (нпр. ``999``)." -#: ../system/integrations/ldap/index.rst:65 +#: ../system/core-workflows/learn-by-example.rst:2 +msgid "Learn by Example" +msgstr "Учите на примеру" + +#: ../system/core-workflows/learn-by-example.rst:4 msgid "" -"Zammad currently has limited fallback server support. You can workaround " -"this by providing several sources - however, ensure to have the exact same " -"configuration on your fallback." +"This page provides some basic examples for Core Workflows. Of course you can " +"build much more complex workflows if needed." msgstr "" -"Zammad тренутно има ограничену подршку за резервни сервер. Ово можете " -"заобићи тако што ћете обезбедити неколико извора - међутим, уверите се да " -"имате потпуно исту конфигурацију на резервном серверу." +"Ова страна обезбеђује неке основне примере за радне токове. Наравно могуће " +"је направити много сложеније токове ако је то потребно." -#: ../system/integrations/ldap/index.rst:69 +#: ../system/core-workflows/learn-by-example.rst:7 msgid "" -"This is subject to improve with `Issue 4107 `_ in the future." +"To learn about Core Workflows in detail, first go to :doc:`how-do-they-work`." msgstr "" -"Ово је предмет побољшања у `извештају 4107 `_ у будућности." +"Да бисте сазнали више о радним токовима, прво посетите :doc:`how-do-they-" +"work`." + +#: ../system/core-workflows/learn-by-example.rst:10 +msgid "Group Based Examples" +msgstr "Примери на основу група" + +#: ../system/core-workflows/learn-by-example.rst:12 +msgid "" +"All following workflows have the same base configurations. The workflow may " +"not use them all." +msgstr "" +"Сви следећи радни токови имају исту основну конфигурацију. Радни ток је " +"можда неће користити целу." + +#: ../system/core-workflows/learn-by-example.rst:15 +msgid "Groups:" +msgstr "Групе:" + +#: ../system/core-workflows/learn-by-example.rst:20 +msgid "Attributes:" +msgstr "Атрибути:" -#: ../system/integrations/ldap/index.rst:76 -msgid "" -"This section holds all requests Zammad handled for all LDAP sources. These " -"entries can either contain synchronization information or logins " -"(authentication attempts via Zammad's login interface)." +#: ../system/core-workflows/learn-by-example.rst:22 +msgid "Category (Single tree selection field, not mandatory, agents only)" msgstr "" -"Овај одељак садржи све захтеве које је Zammad обрадио за све LDAP изворе. " -"Ови уноси могу да садрже информације о синхронизацији или пријави (покушаји " -"аутентификације преко Zammad-овог интерфејса за пријаву)." +"Category (поље за једноструки избор стабла, необавезно, само оператери)" -#: ../system/integrations/ldap/index.rst:80 +#: ../system/core-workflows/learn-by-example.rst:23 msgid "" -"By clicking on any request, Zammad will provide even more information. The " -"provided information can be useful when something does not work as expected." +"Approved (Boolean field, not mandatory, not shown, ``false`` as default)" msgstr "" -"Кликом на било који захтев, Zammad ће пружити још више информација. " -"Представљене информације могу бити корисне када нешто не функционише на " -"начин како се очекује." +"Approved (логичко поље, необавезно, сакривено, ``false`` као подразумевана " +"вредност)" -#: ../system/integrations/ldap/index.rst:85 -msgid "" -"Especially a LDAP synchronization can cause many log entries. The web " -"interface will always limit the number of shown entries to the last 50 " -"entries." -msgstr "" -"Нарочито LDAP синхронизација може проузроковати много уноса евиденције. " -"Кориснички интерфејс ће увек ограничити број приказаних уноса на последњих " -"50." +#: ../system/core-workflows/learn-by-example.rst:24 +msgid "Operating System (Text field, not mandatory, not shown)" +msgstr "Operating System (поље текста, необавезно, сакривено)" -#: ../system/integrations/ldap/index.rst:None -msgid "" -"Screencast showing LDAP integration log entries and a detail view on\n" -"an entry." -msgstr "" -"Снимак екрана који приказује уносе евиденције LDAP интеграције и детаљан " -"приказ\n" -"уноса." +#: ../system/core-workflows/learn-by-example.rst:25 +msgid "Software used (Single selection field, not mandatory, not shown)" +msgstr "Software used (поље једноструког избора, необавезно, сакривено)" -#: ../system/integrations/ldap/manage.rst:2 -msgid "Manage LDAP-Sources" -msgstr "Подешавање LDAP извора" +#: ../system/core-workflows/learn-by-example.rst:68 +msgid "Group specific values and fields" +msgstr "Груписање специфичних вредности и поља" -#: ../system/integrations/ldap/manage.rst:6 +#: ../system/core-workflows/learn-by-example.rst:28 msgid "" -"Please keep in mind all current limitations for the LDAP synchronization. " -"This will help to understand scopes of the following operations better." +"This workflow set depends on the category field. It reduces the available " +"set of values based on the group selected." msgstr "" -"Имајте на уму сва тренутна ограничења за LDAP синхронизацију. Ово ће вам " -"помоћи да боље разумете обим следећих операција." +"Овај колекција радних токова зависи од поља категорије. Смањује доступни " +"скуп вредности на основу изабране групе." -#: ../system/integrations/ldap/manage.rst:65 -msgid "Add new source" -msgstr "Додавање новог извора" +#: ../system/core-workflows/learn-by-example.rst:33 +msgid "Workflow 2nd Level group" +msgstr "Радни ток 2nd Level групе" -#: ../system/integrations/ldap/manage.rst:10 +#: ../system/core-workflows/learn-by-example.rst:35 msgid "" -"Using the *New Source* button allows you to add new LDAP sources to your " -"installation. You're not limited in the number of sources, however, keep in " -"mind that many sources will also take more time to synchronize." +"This reduces the category options to ``2nd Level/*``, ``Internal/*`` and " +"``Others``. It also sets further required fields to mandatory and visible." msgstr "" -"Коришћење дугмета *Нови извор* омогућава вам да додате нове LDAP изворе у " -"вашим инсталацијама. Нисте ограничени у броју извора, међутим, имајте на уму " -"да ће великом броју извора такође бити потребно више времена за " -"синхронизацију." +"Смањује број опција Category поља на ``2nd Level/*``, ``Internal/*`` и " +"``Others``. Такође поставља даља обавезна поља на обавезна и као видљива." -#: ../system/integrations/ldap/manage.rst:14 -msgid "" -"You can choose between different encryption types, namely *SSL* and " -"*STARTTLS* or none of them (\"*No SSL*\"). If you choose *SSL* or " -"*STARTTLS*, Zammad will display an additional *SSL verification* option that " -"allows you to disable the verification, e.g. for self-signed SSL " -"certificates. You can also tell Zammad to use a different port by appending " -"``:`` to your hostname/IP." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for 2nd level" msgstr "" -"Можете одабрати између различитих типова шифровања, тј. *SSL* и *STARTTLS* " -"или ниједан („*No SSL*”). Ако изаберете *SSL* или *STARTTLS*, Zammad ће " -"приказати додатну опцију *SSL провера* која вам омогућава да искључите " -"верификацију, нпр. за прилагођене SSL сертификате. Такође можете рећи Zammad-" -"у да користи другачији порт додатком ``:<број порта>`` вашем називу сервера/" -"IP-у." +"Пример радног тока који приказује одређене вредности и поља за 2nd Level" -#: ../system/integrations/ldap/manage.rst:0 +#: ../system/core-workflows/learn-by-example.rst:43 +msgid "Workflow Support group" +msgstr "Радни ток Support групе" + +#: ../system/core-workflows/learn-by-example.rst:45 msgid "" -"Screenshot of configuring a new LDAP source with SSL encryption and SSL " -"verification" +"This reduces the category options to ``Support/*``, ``Internal/*`` and " +"``Others``. It also sets further required fields to visible." msgstr "" -"Снимак екрана подешавања новог LDAP извора са SSL шифровањем и SSL провером" +"Смањује број опција Category поља на ``Support/*``, ``Internal/*`` и " +"``Others``. Такође поставља додатна обавезна поља као видљива." -#: ../system/integrations/ldap/manage.rst:26 -msgid "" -"New Source with SSL transport security enabled and certificate verification" -msgstr "Нови извор са SSL укљученим протоколом и провером сертификата" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for support" +msgstr "Пример радног тока који приказује одређене вредности и поља за Support" -#: ../system/integrations/ldap/manage.rst:30 +#: ../system/core-workflows/learn-by-example.rst:53 +msgid "Workflow Sales group" +msgstr "Радни ток Sales групе" + +#: ../system/core-workflows/learn-by-example.rst:55 msgid "" -"Using an user filter can be a good idea if you only require a small subset " -"of your LDAP users in Zammad." +"This reduces the category options to ``Sales/*``, ``Internal/*`` and " +"``Others``." msgstr "" -"Коришћење филтера корисника може бити добра идеја ако вам је потребан само " -"мали подскуп ваших LDAP корисника у Zammad-у." +"Смањује број опција Category поља на ``Sales/*``, ``Internal/*`` и " +"``Others``." -#: ../system/integrations/ldap/manage.rst:42 -msgid "This especially affects inactive users" -msgstr "Ово посебно утиче на неактивне кориснике" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for sales" +msgstr "Пример радног тока који приказује одређене вредности и поља за Sales" -#: ../system/integrations/ldap/manage.rst:34 -msgid "" -"As every LDAP behaves differently on which attributes and how they are set, " -"Zammad doesn't care about any flags." -msgstr "" -"Како се сваки LDAP понаша другачије на основу тога који атрибути се користе " -"и како су подешени, Zammad неће уважити било какве ознаке." +#: ../system/core-workflows/learn-by-example.rst:68 +#: ../system/integrations/slack.rst:88 +msgid "The Result" +msgstr "Резултат" -#: ../system/integrations/ldap/manage.rst:37 +#: ../system/core-workflows/learn-by-example.rst:63 msgid "" -"Users that no longer are returned by your LDAP source will automatically be " -"set to inactive. Zammad assumes that the user was deactivated." -msgstr "" -"Корисници које ваш LDAP извор више не враћа аутоматски ће бити подешени на " -"неактивне. Zammad претпоставља да је корисник деактивиран." +"This is what the agent would experience with the above workflows in place." +msgstr "Ово је оно што би оператер видео са горе наведеним радним токовима." -#: ../system/integrations/ldap/manage.rst:41 +#: ../system/core-workflows/learn-by-example.rst:0 msgid "" -"Users will never be removed automatically! If you want to remove obsolete " -"users, use :doc:`/system/data-privacy`." -msgstr "" -"Корисници никада неће бити аутоматски уклоњени! Ако желите да уклоните " -"застареле кориснике, користите :doc:`захтеве приватности података `." +"Workflow shows objects and limits options based on selections on the group" +msgstr "Радни ток приказује објекте и ограничава опције на основу избора групе" -#: ../system/integrations/ldap/manage.rst:46 -msgid "Active Directory admins" -msgstr "Active Directory администратори" +#: ../system/core-workflows/learn-by-example.rst:90 +msgid "Approval process" +msgstr "Approval процес" -#: ../system/integrations/ldap/manage.rst:45 +#: ../system/core-workflows/learn-by-example.rst:71 msgid "" -"Active Directories are quite specific on how to filter for active users only " -"- please see the `Microsoft documentation `_ for more " -"information." +"In this case ``approved`` is visible to agents by default. For this " +"workflow, an additional role ``Approval person`` is required (no further " +"permissions)." msgstr "" -"Active Directories су прилично специфични у погледу филтрирања само за " -"активне кориснике - за више информација погледајте `Microsoft документацију " -"`_." +"У овом случају ``approved`` је подразумевано видљиво оператерима. За овај " +"радни ток посла потребна је додатна улога ``Approval person`` (без додатних " +"дозвола)." -#: ../system/integrations/ldap/manage.rst:51 +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that restricts an approval attribute to specific roles" +msgstr "Пример радног тока који ограничава атрибут Approval на одређене улоге" + +#: ../system/core-workflows/learn-by-example.rst:81 msgid "" -"*Do not* manually write pathes of either LDAP attributes or groups. If " -"Zammad does not display them, it either cannot find them or you have a lot " -"of users that don't have the attributes populated." +"This workflow may work best in combination with a :doc:`trigger ` but technically, this is not required." msgstr "" -"*Немојте* ручно писати путање било LDAP атрибута или група. Ако их Zammad не " -"прикаже, или не може да их пронађе или имате много корисника који немају " -"попуњене атрибуте." +"Овај радни ток можда најбоље функционише у комбинацији са :doc:`окидачем `, али технички није неопходан." -#: ../system/integrations/ldap/manage.rst:55 +#: ../system/core-workflows/learn-by-example.rst:84 msgid "" -"Zammad will always only return attributes that are filled - this reduces the " -"returned list of attributes greatly." +"Select fields may be a better approach because they allow more values than " +"just a simple ``true`` or ``false``." msgstr "" -"Zammad ће увек враћати само попуњене атрибуте - ово у великој мери смањује " -"враћену листу атрибута." - -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing how to add a new LDAP source" -msgstr "Снимак екрана који показује како да додате нови LDAP извор" +"Поља избора могу представљати бољи приступ јер дозвољавају више вредности од " +"једноставног ``true`` или ``false``." -#: ../system/integrations/ldap/manage.rst:63 +#: ../system/core-workflows/learn-by-example.rst:0 msgid "" -"If your LDAP system doesn't allow anonymous bind, Zammad detects it and " -"provides you an editable \"Base DN\" *text* field instead of a prefilled " -"*select* field." +"Workflow fixes possible values of \"Approved ?\" to a specific selection " +"depending on the users role" msgstr "" -"Ако ваш LDAP систем не подржава анонимни приступ, Zammad ће то детектовати и " -"омогућити вам поље *текста* „Основни DN” уместо попуњеног поља *избора*." - -#: ../system/integrations/ldap/manage.rst:81 -msgid "Review or edit existing source" -msgstr "Прегледајте или уредите постојећи извор" +"Радни ток мења могуће вредности „Approved ?“ поља у зависности од улоге " +"корисника" -#: ../system/integrations/ldap/manage.rst:68 -msgid "" -"Clicking on a LDAP source will provide a configuration and mapping overview." -msgstr "Кликом на LDAP извор добићете преглед конфигурације и мапирања." +#: ../system/core-workflows/learn-by-example.rst:103 +msgid "State dependent mandatory fields" +msgstr "Обавезна поља зависна од стања" -#: ../system/integrations/ldap/manage.rst:70 +#: ../system/core-workflows/learn-by-example.rst:93 msgid "" -"If needed you can then use the *Change* button to update either the name, " -"active state or the whole configuration. If you're changing the whole " -"configuration, the dialogue will be identical to the source creation." +"This workflow sets ``Category`` to mandatory if the agent wants to set the " +"states ``closed`` or ``pending close`` to enforce categorization." msgstr "" -"Ако је потребно, можете користити дугме *Измени* да освежите назив, активно " -"стање или целу конфигурацију. Ако мењате целу конфигурацију, дијалог ће бити " -"идентичан оном приликом додавања извора." +"Овај радни ток поставља ``Category`` поље на обавезно ако оператер жели да " +"подеси стања ``затворено`` или ``чека на затварање`` ради примене " +"категоризације." -#: ../system/integrations/ldap/manage.rst:76 +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that sets fields to mandatory on specific states" +msgstr "Пример радног тока који поставља поља на обавезна за одређена стања" + +#: ../system/core-workflows/learn-by-example.rst:0 msgid "" -"Did your LDAP server change? Different LDAP servers have different " -"structures and default attributes. This causes the LDAP synchronization to " -"likely fail. Consider removing the affected source and re-add it." +"Workflow sets category field to mandatory upon choosing closed or pending " +"close as state" msgstr "" -"Да ли се ваш LDAP сервер променио? Различити LDAP сервери имају различите " -"структуре и подразумеване атрибуте. Ово може узроковати да LDAP " -"синхронизација не успе. Размислите о брисању дотичног извора и поново га " -"додајте." +"Радни ток поставља Category поље на обавезно након одабира затворено или на " +"чека на затварање за стање" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing the update of the source name." -msgstr "Снимак екрана који приказује освежавање назива извора." +#: ../system/core-workflows/learn-by-example.rst:106 +msgid "Manual Ticket Handover Process" +msgstr "Процес ручног пребацивања тикета" -#: ../system/integrations/ldap/manage.rst:89 -msgid "Re-arrange LDAP source's order" -msgstr "Измените редослед LDAP извора" +#: ../system/core-workflows/learn-by-example.rst:108 +msgid "This example covers the handover of a ticket from one agent to another:" +msgstr "Овај пример осликава пренос тикета са једног оператера на другог:" -#: ../system/integrations/ldap/manage.rst:84 +#: ../system/core-workflows/learn-by-example.rst:110 msgid "" -"You can change the synchronization order for each source at any time. Zammad " -"will synchronize the sources from top to bottom." +"When the ticket owner is modified, a new text field (\"Handover\") shows up " +"for a comment" msgstr "" -"Редослед синхронизације за сваки извор можете променити у било ком тренутку. " -"Zammad ће синхронизовати изворе одозго на доле." +"Када је власник тикета промењен, ново поље уноса текста („Примопредаја”) ће " +"се приказати за унос коментара" -#: ../system/integrations/ldap/manage.rst:0 +#: ../system/core-workflows/learn-by-example.rst:112 msgid "" -"Screencasting showing how to change the source order by using\n" -"drag and drop." +"This may only be visible when the owner is changed, therefore it has to be " +"hidden in general" msgstr "" -"Снимак екрана показује како да промените редослед извора коришћењем\n" -"радње превуци и пусти." +"Ово поље може постати видљиво само када се власник измени, у супротном мора " +"остати сакривено" -#: ../system/integrations/ldap/manage.rst:101 -msgid "Remove a source" -msgstr "Брисање извора" +#: ../system/core-workflows/learn-by-example.rst:114 +msgid "The input in this handover text field is mandatory" +msgstr "Унос овог поља за примопредају је обавезан" -#: ../system/integrations/ldap/manage.rst:92 +#: ../system/core-workflows/learn-by-example.rst:115 msgid "" -"If you no longer need the a LDAP source or simply want to start over, you " -"can remove them at any time. This will not remove synchronized users, data " -"synchronized or permissions." +"After submitting changes, the value of the handover field must be added as " +"an note to the ticket (via trigger)" msgstr "" -"Ако вам више није потребан LDAP извор или једноставно желите да почнете " -"изнова, можете их обрисати у било ком тренутку. Ова радња неће уклонити " -"синхронизоване кориснике, њихове податке или дозволе." +"По слању измена, вредност поља за примопредају мора бити додат као напомена " +"тикета (преко окидача)" -#: ../system/integrations/ldap/manage.rst:98 -msgid "" -"Not sure if you'd need the source later on? Set the source to inactive " -"instead of removing it - see *Review or edit existing source* for more." -msgstr "" -"Нисте сигурни да ли ће вам извор требати за касније? Искључите извор уместо " -"да га обришете - погледајте одељак *Прегледајте или уредите постојећи извор* " -"за детаље." +#: ../system/core-workflows/learn-by-example.rst:121 +msgid "Hiding handover field" +msgstr "Скривање поља за примопредају" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing how to remove LDAP sources." -msgstr "Снимак екрана који показује како обрисати LDAP изворе." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Hiding the handover field in core workflows" +msgstr "Скривање поља за примопредају у радним токовима" -#: ../system/integrations/pgp/index.rst:2 -msgid "PGP" -msgstr "PGP" +#: ../system/core-workflows/learn-by-example.rst:126 +msgid "Showing handover field and setting it to mandatory" +msgstr "Приказ поља за примопредају и постављање на обавезно" -#: ../system/integrations/pgp/index.rst:7 -msgid "" -"Pretty Good Privacy (PGP) is another method for secure email communication. " -"With PGP, you can exchange **signed** and **encrypted** messages with others." -msgstr "" -"Pretty Good Privacy (PGP) је још један метод за безбедну комуникацију путем " -"имејла. Са PGP, можете да размењујете **потписане** и **шифроване** поруке " -"са другима." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Showing the handover field and set it as mandatory" +msgstr "Приказ поља за примопредају и постављање на обавезно" -#: ../system/integrations/pgp/index.rst:13 -#: ../system/integrations/smime/index.rst:17 -msgid "Signing" -msgstr "Потписивање" +#: ../system/core-workflows/learn-by-example.rst:131 +msgid "Trigger writing handover input to a new article" +msgstr "Окидач за претварање уноса примопредају у нови чланак" -#: ../system/integrations/pgp/index.rst:11 -msgid "is a proof that a message hasn't been manipulated on its way." -msgstr "је доказ да порука није мењана на свом путу." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Write handover content to a new article" +msgstr "Снимање садржаја примопредаје као нови чланак" -#: ../system/integrations/pgp/index.rst:13 +#: ../system/core-workflows/learn-by-example.rst:133 msgid "" -"In other words, it guarantees message **integrity** and **authenticity**." -msgstr "Другим речима, гарантује **интегритет** и **аутентичност** поруке." +"As a result, the ticket includes an article of the type note which includes " +"the predefined text and the handover comment." +msgstr "" +"Као резултат, тикет сада укључује чланак напомене који садржи предефинисани " +"текст и коментар примопредаје." -#: ../system/integrations/pgp/index.rst:19 -#: ../system/integrations/smime/index.rst:22 -msgid "Encryption" -msgstr "Шифровање" +#: ../system/core-workflows/limitations.rst:6 +msgid "Core Workflows do not replace Triggers" +msgstr "Радни токови не замењују окидаче" -#: ../system/integrations/pgp/index.rst:16 -#: ../system/integrations/smime/index.rst:20 +#: ../system/core-workflows/limitations.rst:5 msgid "" -"scrambles a message so that it can only be unscrambled by the intended " -"recipient." +"Workflows manipulate the behavior of fields. However, they do not set values " +"in fields because of actions." msgstr "" -"шифрује поруку тако да може да је дешифрује само прималац коме је намењена." +"Радни токови манипулишу понашање поља. Међутим, они не постављају вредности " +"у поља због радњи." -#: ../system/integrations/pgp/index.rst:19 -msgid "" -"In other words, it guarantees message **privacy** and **data security**." -msgstr "Другим речима, гарантује **приватност** и **безбедност података**." +#: ../system/core-workflows/limitations.rst:16 +msgid "API calls are only partly affected" +msgstr "API позиви су само делимично захваћени" -#: ../system/integrations/pgp/index.rst:25 -msgid "Screenshot of ticket creation with encrypt and sign buttons" +#: ../system/core-workflows/limitations.rst:9 +msgid "" +"Some options affect UI only and thus do not restrict responses and calls." msgstr "" -"Снимак екрана за отварање тикета са дугмићима за шифровање и потписивање" +"Неке опције утичу само на кориснички интерфејс и стога не ограничавају API " +"захтеве." -#: ../system/integrations/pgp/index.rst:25 +#: ../system/core-workflows/limitations.rst:11 +msgid "This affects the following actions:" +msgstr "Ово утиче на следеће радње:" + +#: ../system/core-workflows/limitations.rst:13 +msgid "select" +msgstr "изабери" + +#: ../system/core-workflows/limitations.rst:14 +msgid "auto select" +msgstr "аутоматски избор" + +#: ../system/core-workflows/limitations.rst:15 +msgid "show" +msgstr "прикажи" + +#: ../system/core-workflows/limitations.rst:16 +msgid "hide" +msgstr "сакриј" + +#: ../system/core-workflows/limitations.rst:25 +msgid "Some fields stay unavailable to customers" +msgstr "Нека поља остају недоступна клијентима" + +#: ../system/core-workflows/limitations.rst:19 msgid "" -"Once PGP has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " -"appear in the ticket composer." +"For technical and security reasons, some default fields (the pale ones you " +"can't edit) stay unavailable for display and usage on customer permissions." msgstr "" -"Када је PGP укључен, дугмићи 🔒 **Шифровање** и ✅ **Потписивање** појавиће " -"се у дијалогу новог тикета." - -#: ../system/integrations/pgp/index.rst:28 -msgid "**Sign button not visible?**" -msgstr "**Дугме за потписивање није видљиво?**" +"Из техничких и безбедносних разлога, нека подразумевана поља (нпр. она бледа " +"која не можете да мењате) остају недоступна за приказ и коришћење за дозволе " +"клијента." -#: ../system/integrations/pgp/index.rst:30 +#: ../system/core-workflows/limitations.rst:23 msgid "" -"Please note that the signing of emails is based on the outgoing email " -"account. That means you have to choose a group with a sender email account, " -"which has a private key assigned." +"If you require your customers to change e.g. priorities, please consider " +"using workarounds via :doc:`/system/objects` and :doc:`/manage/trigger`." msgstr "" -"Имајте на уму да се потписивање имејл порука заснива на налогу одлазне " -"поште. То значи да морате да изаберете групу повезану са имејл адресом " -"пошиљаоца, којој је додељен приватни кључ." +"Ако желите да ваши клијенти промене нпр. приоритете, размислите о коришћењу " +"алтернативних решења преко :doc:`објеката ` и :doc:`окидача " +"`." -#: ../system/integrations/pgp/index.rst:35 -msgid "Handling of Keys" -msgstr "Руковање кључевима" +#: ../system/core-workflows/limitations.rst:29 +msgid "Ticket title changes not supported in edit mask" +msgstr "Измена наслова тикета није подржана у форми уређивања" -#: ../system/integrations/pgp/index.rst:36 +#: ../system/core-workflows/limitations.rst:28 msgid "" -"To use the PGP function, you have to enable the integration (PGP) by " -"switching the toggle to *enabled*." +"It is currently not possible to perform changes of the ticket title in the " +"edit mask (e.g. renaming, set to read-only)." msgstr "" -"Да бисте користили PGP функцију, морате да укључите PGP интеграцију " -"пребацивањем прекидача на *укључено*." +"Тренутно није могуће изменити наслов тикета у форми уређивања (нпр. промена " +"наслова, постављање само на читање)." -#: ../system/integrations/pgp/index.rst:39 +#: ../system/core-workflows/limitations.rst:37 +msgid "What is out of scope of Core Workflows?" +msgstr "Шта је то изван опсега радних токова?" + +#: ../system/core-workflows/limitations.rst:32 msgid "" -"You can add keys by clicking the *add key* button. The keys can be imported " -"from a file or you can paste the content of the key in the text box." +"There are some things that would count as workflow but are either done via :" +"doc:`/manage/trigger` or :doc:`/manage/scheduler`." msgstr "" -"Можете додати кључеве кликом на дугме *додај кључ*. Кључеви се могу увести " -"из датотеке или можете налепити садржај кључа у поље текста." +"Постоје неке ствари које би се рачунале као радни ток, али се извршавају или " +"преко :doc:`окидача ` и :doc:`планера `." -#: ../system/integrations/pgp/index.rst:42 -msgid "**Which keys do I have to import?**" -msgstr "**Које кључеве треба да увезем?**" +#: ../system/core-workflows/limitations.rst:35 +msgid "Such as (but not limited to):" +msgstr "Као што су (али не ограничавајући се на):" -#: ../system/integrations/pgp/index.rst:44 +#: ../system/core-workflows/limitations.rst:37 +msgid "up- or downgrade permissions of users" +msgstr "промоција или скидање дозвола корисника" + +#: ../system/core-workflows/limitations.rst:38 +msgid "affecting article creation or listing" +msgstr "утицај на додавање или листање чланака" + +#: ../system/data-privacy.rst:2 +msgid "Data Privacy" +msgstr "Приватност података" + +#: ../system/data-privacy.rst:4 msgid "" -"For **signing** *outgoing* emails, you have to import the private key of " -"your Zammad email account." +"For compliance with GDPR and other data privacy laws, you may wish to " +"**permanently delete users from the system**, along with **all of their " +"associated tickets**." msgstr "" -"За **потписивање** *одлазних* порука, морате да увезете приватни кључ ваше " -"Zammad имејл адресе." +"Да бисте били усклађени са GDPR-ом и другим законима о приватности података, " +"можда ћете пожелети да будете у могућности да **трајно избришете кориснике " +"из система**, заједно са **свим повезаним тикетима**." -#: ../system/integrations/pgp/index.rst:47 +#: ../system/data-privacy.rst:8 msgid "" -"For **encrypting** *outgoing* emails, you have to import the public key of " -"the customer's email account." +"You can create manual deletion tasks or even automated deletion tasks for " +"tickets and users based on custom conditions via :doc:`scheduler `!" msgstr "" -"За **шифровање** *одлазних* порука, морате да увезете јавни кључ имејл " -"адресе клијента." +"Можете дефинисати ручне задатке или чак аутоматизоване захтеве за брисање " +"тикета и корисника на основу прилагођених услова путем :doc:`планера `!" -#: ../system/integrations/pgp/index.rst:50 +#: ../system/data-privacy.rst:12 msgid "" -"For **verifying the signature** of signed *incoming* emails, you have to " -"import the public key of the customer." +"Access to this panel requires ``admin.data_privacy`` permissions (introduced " +"in Zammad 3.5)." msgstr "" -"За **верификацију потписа** потписаних *долазних* порука, морате да увезете " -"јавни кључ имејл адресе клијента." +"Приступ овом панелу захтева дозволу ``admin.data_privacy`` (уведена у Zammad " +"верзији 3.5)." -#: ../system/integrations/pgp/index.rst:53 +#: ../system/data-privacy.rst:15 msgid "" -"For **decrypting** of encrypted *incoming* emails, you have to import the " -"private key of your Zammad email account." +"On older systems that have not been updated yet, customers can also be :docs:" +"`deleted via the Zammad console `." msgstr "" -"За **дешифровање** шифрованих *долазних* порука, морате да увезете приватни " -"кључ ваше Zammad имејл адресе." - -#: ../system/integrations/pgp/index.rst:57 -msgid "Import Keys From a File" -msgstr "Увоз кључева из датотеке" - -#: ../system/integrations/pgp/index.rst:58 -msgid "You can import keys from a file in the section **Upload key**:" -msgstr "Можете да увезете кључ из датотеке у одељку **Отпреми кључ**:" +"На старијим системима који још нису ажурирани, клијенти се такође могу :docs:" +"`обрисати преко Zammad конзоле `." -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of adding a key via file" -msgstr "Снимак екрана додавања кључа путем датотеке" +#: ../system/data-privacy.rst:22 +msgid "User deletion dialog in the Data Privacy panel" +msgstr "Дијалог за брисање корисника у панелу приватности података" -#: ../system/integrations/pgp/index.rst:64 +#: ../system/data-privacy.rst:22 msgid "" -"**Supported file formats:** ASCII-armor as well as binary GPG format " -"(basically any GPG supported key format) is supported here." +"The user deletion dialog lists some of the tickets that will be removed from " +"the system along with the user." msgstr "" -"**Подржани формати кључева:** овде је подржан ASCII armor као и бинарни GPG " -"формат (у основи било који формат кључа који подржава GPG)." +"Дијалог за брисање корисника приказује неке од тикета који ће бити уклоњени " +"из система заједно са корисником." -#: ../system/integrations/pgp/index.rst:68 -msgid "Import Keys by Pasting the Content" -msgstr "Увоз кључева налепљивањем текста" +#: ../system/data-privacy.rst:27 +msgid "Deleting Users via GUI" +msgstr "Брисање корисника путем корисничког интерфејса" -#: ../system/integrations/pgp/index.rst:69 -msgid "You can also paste the key's content in the section **paste key**:" -msgstr "Такође можете да налепите садржај кључа у одељак **Налепи кључ**:" +#: ../system/data-privacy.rst:29 +msgid "🔥 **All deletions are FINAL!**" +msgstr "🔥 **Сва брисања су КОНАЧНА!**" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of adding a key via pasting" -msgstr "Снимак екрана додавања кључа путем налепљивања текста" +#: ../system/data-privacy.rst:31 +msgid "Once you click “Delete”, the action cannot be canceled or undone." +msgstr "Када кликнете на „Избриши“, радња се не може отказати или опозвати." -#: ../system/integrations/pgp/index.rst:75 +#: ../system/data-privacy.rst:33 msgid "" -"**Supported format:** Please note that only ASCII-armor is supported here." +"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." msgstr "" -"**Подржани формат кључа:** Имајте на уму да је овде подржан само ASCII armor " -"формат." +"Сваки пут када избришете корисника, сви њихови тикети ће такође бити " +"избрисани. Није могуће избрисати корисника и задржати њихове тикете." -#: ../system/integrations/pgp/index.rst:78 -msgid "Deleting Keys" -msgstr "Брисање кључева" +#: ../system/data-privacy.rst:36 +msgid "**The following records cannot be deleted:**" +msgstr "**Следећи налози се не могу избрисати:**" -#: ../system/integrations/pgp/index.rst:79 -msgid "" -"If you want to delete a specific key, you can do it by clicking on the menu " -"in the *actions* column and select **delete**:" -msgstr "" -"Ако желите да избришете одређени кључ, то можете учинити тако што ћете " -"кликнути на мени у колони *радње* и изабрати **избриши**:" +#: ../system/data-privacy.rst:38 +msgid "your own account" +msgstr "ваш тренутни налог" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of deleting a key" -msgstr "Снимак екрана брисања кључа" +#: ../system/data-privacy.rst:39 +msgid "the system's last remaining administrator account" +msgstr "последњи налог администратора у систему" -#: ../system/integrations/pgp/index.rst:88 -msgid "Downloading Keys" -msgstr "Преузимање кључева" +#: ../system/data-privacy.rst:42 +msgid "Step 1: Find a User / Confirm Deletion" +msgstr "Корак 1: Пронађите корисника / потврдите брисање" -#: ../system/integrations/pgp/index.rst:89 -msgid "" -"If you want to download your keys, you can do this as well via corresponding " -"action buttons. Depending on the key, you can choose wether you want to " -"download the private or the public key." -msgstr "" -"Ако желите да преузмете своје кључеве, то можете учинити и путем " -"одговарајућих дугмића за радњу. У зависности од врсте кључа, можете изабрати " -"да ли желите да преузмете приватни или јавни кључ." +#: ../system/data-privacy.rst:44 +msgid "There are three ways to access the user deletion dialog:" +msgstr "Постоје три начина за приступ дијалогу за брисање корисника:" -#: ../system/integrations/pgp/index.rst:95 -#: ../system/integrations/smime/manage-certificates.rst:76 -msgid "Default Behavior" -msgstr "Подразумевано понашање" +#: ../system/data-privacy.rst:51 +msgid "**from the user's profile**" +msgstr "**из корисничког профила**" -#: ../system/integrations/pgp/index.rst:96 -msgid "" -"Here you can adjust on per group basis, if *sign* and *encryption* is on or " -"off by default. Please be aware, that agents can always override the setting " -"for each individual article." -msgstr "" -"Овде можете да прилагодите по групама, ако су *потписивање* и *шифровање* " -"подразумевано укључени или искључени. Имајте на уму да оператери увек могу " -"преиначити подешавање за сваки појединачни чланак." +#: ../system/data-privacy.rst:0 +msgid "Accessing the user deletion dialog in a user profile" +msgstr "Приступ дијалогу за брисање корисника из корисничког профила" -#: ../system/integrations/pgp/index.rst:None -msgid "Adjusting default behavior on per group basis" -msgstr "Прилагођавање подразумеваног понашања по групи" +#: ../system/data-privacy.rst:51 +msgid "Click **Action > Delete**." +msgstr "Кликните на **Радња > Избриши**." -#: ../system/integrations/pgp/index.rst:107 -msgid "" -"Here you can see the last actions regarding signing and encryption and if " -"they were successful." +#: ../system/data-privacy.rst:58 +msgid "**in the “Manage > Users” Admin Panel**" +msgstr "**из администраторског панела „Управљање > Корисници“**" + +#: ../system/data-privacy.rst:0 +msgid "Accessing the user deletion dialog under “Users” in the Admin Panel" msgstr "" -"Овде можете видети последње радње у вези са потписивањем и шифровањем и да " -"ли су биле успешне." +"Приступ дијалогу за брисање корисника под „Корисници“ у администраторском " +"панелу" -#: ../system/integrations/pgp/index.rst:117 -msgid "**Sign button is not visible, but keys are imported.**" -msgstr "**Дугме за потписивање није видљиво, али су кључеви увезени.**" +#: ../system/data-privacy.rst:58 +msgid "Use the **⋮ Actions** menu for the target user." +msgstr "Користите мени **⋮ Радње** за циљног корисника." -#: ../system/integrations/pgp/index.rst:115 -msgid "Did you choose a group in the ticket?" -msgstr "Да ли сте одабрали групу тикета?" +#: ../system/data-privacy.rst:66 ../system/data-privacy.rst:104 +msgid "**in the “System > Data Privacy” Admin Panel**" +msgstr "**из администраторског панела „Систем > Приватност података“**" -#: ../system/integrations/pgp/index.rst:116 +#: ../system/data-privacy.rst:0 msgid "" -"Did you import a private key for the email adress, which is used for " -"outgoing emails in the group?" +"Accessing the user deletion dialog under “Data Privacy” in the Admin Panel" msgstr "" -"Да ли сте увезли приватни кључ за имејл адресу која се користи за одлазне " -"поруке у групи?" +"Приступ дијалогу за брисање корисника под „Приватност података“ у " +"административном панелу" -#: ../system/integrations/pgp/index.rst:122 -msgid "**How to obtain keys?**" -msgstr "**Како доћи до кључева?**" +#: ../system/data-privacy.rst:65 +msgid "" +"Use the **New Deletion Task** button. Search for users by name or email " +"address." +msgstr "" +"Користите дугме **Нови захтев за брисање**. Претражите кориснике по имену " +"или имејл адреси." -#: ../system/integrations/pgp/index.rst:120 +#: ../system/data-privacy.rst:79 +msgid "**Delete organizations**" +msgstr "**Брисање организација**" + +#: ../system/data-privacy.rst:69 msgid "" -"You can create them yourself! There are some good tutorials on the web on " -"how to create them. Providing keys to Zammad is a prerequisite to use the " -"PGP feature." +"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:" msgstr "" -"Можете их генерисати сами! Постоји неколико добрих упутстава на интернету о " -"томе како да их креирате. Достава кључева у Zammad је предуслов за коришћење " -"PGP функције." +"Ако је клијент кога бришете последњи корисник у својој организацији, опција " +"**Избриши организацију?** биће приказана у дијалогу за брисање корисника:" -#: ../system/integrations/pgp/index.rst:127 -msgid "**It says a passphrase is needed, but I haven't got one.**" -msgstr "**Каже да је потребна лозинка, али ја је немам.**" +#: ../system/data-privacy.rst:0 +msgid "Deleting an organization via the user deletion dialog" +msgstr "Брисање организације преко дијалога за брисање корисника" -#: ../system/integrations/pgp/index.rst:125 +#: ../system/data-privacy.rst:78 msgid "" -"If the key is secured with a passphrase, you have to provide it for the " -"import in Zammad. It is possible that keys may have an empty passphrase. " -"However, this is *not* recommended." +"If this option does not appear, make sure there are no pending deletion " +"tasks for other customers from this organization." msgstr "" -"Ако је кључ обезбеђен лозинком, морате је обезбедити приликом увоза у " -"Zammad. Могуће је да кључеви имају и празну лозинку. Међутим, ово се *не* " -"препоручује." +"Ако се ова опција не појави, проверите да нема заказаних брисања за друге " +"клијенте из ове организације." -#: ../system/integrations/pgp/index.rst:132 -msgid "**How do my customers get my new key?**" -msgstr "**Како моји клијенти добављају мој нови кључ?**" +#: ../system/data-privacy.rst:82 +msgid "Step 2: Monitor Deletion Job Status" +msgstr "Корак 2: Пратите статус заказаног захтева за брисање" -#: ../system/integrations/pgp/index.rst:130 +#: ../system/data-privacy.rst:84 msgid "" -"You have to provide your **public** key in advance. Your customer also has " -"to configure PGP in their email workflow and import your public key. The " -"other way round, you have to get the public key of your customer and have to " -"import it to Zammad." +"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:" msgstr "" -"Морате унапред да им доставите свој **јавни** кључ. Ваш клијент такође мора " -"да подеси PGP у свом имејл окружењу и увезе ваш јавни кључ. Обрнуто, морате " -"да добавите јавни кључ вашег клијента и да га увезете у Zammad." +"Систему може бити потребно до десет минута да обради ваш захтев, тако да се " +"за сваког корисника којег избришете прво заказује „захтев за брисање“. " +"Статус ових захтева можете пратити на два места:" -#: ../system/integrations/slack.rst:2 -msgid "Slack" -msgstr "Slack" +#: ../system/data-privacy.rst:98 +msgid "**in the Activity Stream**" +msgstr "**у току активности**" -#: ../system/integrations/slack.rst:4 -msgid "**⚠️ Deprecation warning ⚠️**" -msgstr "**⚠️ Упозорење о застаревању ⚠️**" +#: ../system/data-privacy.rst:0 +msgid "Activity Stream showing data privacy tasks" +msgstr "Ток активности који приказује захтеве приватности података" -#: ../system/integrations/slack.rst:6 +#: ../system/data-privacy.rst:94 msgid "" -"Zammad 7 will no longer support this dedicated Slack integration. It is " -"recommended to switch to :doc:`pre-defined webhooks ` instead. Existing Slack integrations should " -"be migrated manually before this feature is dropped." +"For each deleted user, the Activity Stream will be updated twice—once when " +"the task is created, and once when it's complete." msgstr "" -"Zammad 7 више неће подржавати ову наменску Slack интеграцију. Препоручује се " -"да се уместо тога пребаците на :doc:`повратне позиве по шаблону `. Постојеће Slack интеграције је " -"потребно ручно мигрирати пре него што се ова функција укине." +"За сваког избрисаног корисника, ток активности ће се ажурирати два пута — " +"једном када се задатак закаже и једном када се заврши." -#: ../system/integrations/slack.rst:14 +#: ../system/data-privacy.rst:97 msgid "" -"In order to use this feature, please add a new Slack app to your Workspace. " -"The App you need is called ``Incoming WebHooks`` ." +"These notifications are only visible to users with ``admin.data_privacy`` " +"permissions." msgstr "" -"Да бисте користили ову функцију, додајте нову Slack апликацију у своје " -"окружење. Апликација која вам је потребна зове се ``Incoming WebHooks``." - -#: ../system/integrations/slack.rst:18 -msgid "Why Do I Need This Feature?" -msgstr "Зашто ми треба ова функција?" +"Ова обавештења су видљива само корисницима са дозволама ``admin." +"data_privacy``." -#: ../system/integrations/slack.rst:20 +#: ../system/data-privacy.rst:0 msgid "" -"If you're already using Slack for your team communication, you'll love this " -"feature! Our Slack integration can push ticket notifications about the last " -"ticket article based on the following events:" +"The task list within Data Privacy shows removals being in progress and " +"completed." msgstr "" -"Ако већ користите Slack за комуникацију у оквиру вашег тима, свидеће вам се " -"ова функција! Наша Slack интеграција може да објави обавештења о последњем " -"чланку тикета на основу следећих догађаја:" +"Листа захтева у оквиру приватности података показује да је брисања у току " +"или извршена." -#: ../system/integrations/slack.rst:24 -msgid "on Ticket creation" -msgstr "при отварању тикета" +#: ../system/data-privacy.rst:107 +msgid "Frequently Asked Questions" +msgstr "Често постављана питања" -#: ../system/integrations/slack.rst:25 -msgid "on Ticket updates" -msgstr "при освежавању тикета" +#: ../system/data-privacy.rst:121 +msgid "What happens if I receive an email from a deleted customer?" +msgstr "Шта се дешава ако добијем имејл од избрисаног клијента?" -#: ../system/integrations/slack.rst:26 -msgid "on reached reminders" -msgstr "по достигнутим подсетницима" +#: ../system/data-privacy.rst:110 +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 "" +"Zammad аутоматски додаје нови кориснички налог сваки пут када прими поруку " +"са непознате имејл адресе, укључујући и избрисане кориснике. Избрисаним " +"корисницима никада није онемогућено отварање нових тикета." -#: ../system/integrations/slack.rst:27 -msgid "a Ticket has escalated" -msgstr "по ескалирању тикета" +#: ../system/data-privacy.rst:115 +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**." +msgstr "" +"У мало вероватном случају да добијете имејл поруку између тренутка када " +"кликнете на „Избриши“ и када систем обради ваш захтев, **тај тикет ће бити " +"аутоматски избрисан**. Број тикета за изгубљени тикет ће бити приказан у " +"администраторском панелу под **Систем > Приватност података > Извршени " +"захтеви > Брисање корисника > Обрисани тикети**." -#: ../system/integrations/slack.rst:28 -msgid "a Ticket is going to escalate" -msgstr "пре ескалације тикета" +#: ../system/data-privacy.rst:130 +msgid "What about user information stored in internal notes or other messages?" +msgstr "" +"А шта је са корисничким информацијама сачуваним у интерним напоменама или " +"другим порукама?" -#: ../system/integrations/slack.rst:30 +#: ../system/data-privacy.rst:124 msgid "" -"Zammad will provide the Ticket title, a direct link to the Ticket, the event " -"type (creation, updated, escalation), the customer, time and the last " -"article that has triggered the notification." +"The deletion process removes **user accounts and associated tickets only**." +msgstr "Процес брисања уклања **само корисничке налоге и повезане тикете**." + +#: ../system/data-privacy.rst:126 +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." msgstr "" -"Zammad ће обезбедити наслов тикета, директан линк до тикета, тип догађаја " -"(отварање, освежавање, ескалација), клијента, време и последњи чланак који " -"је окинуо обавештење." +"Ако постоје референце на име корисника или информације ускладиштене негде " +"другде у систему, те информације **неће бити уклоњене** јер не постоји начин " +"да се безбедно утврди да ли заиста описују дотичног корисника." -#: ../system/integrations/slack.rst:34 +#: ../system/data-privacy.rst:137 +msgid "I deleted an user and can still see a message they sent!" +msgstr "Избрисао сам корисника и још увек видим поруку коју је послао!" + +#: ../system/data-privacy.rst:133 msgid "" -"This will give you further options, as you can see e.g. escalating tickets " -"that are assigned to an agent that's e.g. absent. You can interact faster, " -"as you might see problems earlier (or even before the problem gets one)." +"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." msgstr "" -"Ово ће вам пружити додатне опције, као што су ескалације тикета које су " -"додељене оператеру који је нпр. одсутан. Можете да комуницирате брже, јер " -"ћете можда раније уочити проблеме (или чак и пре него што се проблем појави)." +"Тикети могу припадати само једном клијенту, али могу садржати поруке " +"(„чланке“) од великог броја људи. Ако сте избрисали корисника, али и даље " +"видите чланке које је он послао, не брините – ти чланци су за тикет који " +"припада неком другом кориснику и више не садрже никакву референцу на " +"идентитет пошиљаоца." -#: ../system/integrations/slack.rst:38 +#: ../system/data-privacy.rst:141 +msgid "I removed a customer, now my reporting is off!" +msgstr "Уклонио сам клијента, сада су моји извештаји погрешни!" + +#: ../system/data-privacy.rst:140 msgid "" -"If needed and wanted, you can even discuss directly about the topic before " -"sending an answer to the customer. Another possible use case would be a " -"agent monitoring new agents and their answers to tickets." +"When removing users and their tickets, all references are removed. This also " +"affects e.g. Reporting - these information are lost." msgstr "" -"Ако је потребно и желите, можете чак и директно да разговарате о теми пре " -"него што пошаљете одговор клијенту. Други могући случај употребе би био да " -"оператер надгледа нове оператере и њихове одговоре на тикете." +"Приликом уклањања корисника и њихових тикета, све референце се уклањају. Ово " +"утиче и на нпр. извештавање - ове информације су трајно изгубљене." -#: ../system/integrations/slack.rst:44 -msgid "Configure the Integration" -msgstr "Конфигуришите интеграцију" +#: ../system/data-privacy.rst:145 +msgid "How long does Zammad store created tasks?" +msgstr "Колико дуго Zammad чува заказане захтеве?" -#: ../system/integrations/slack.rst:46 +#: ../system/data-privacy.rst:144 msgid "" -"First of all, please go to your slack workspace - go to administration => " -"Manage Apps. If you don't have an app yet, you can simply add a new one - " -"just search for ``Incoming WebHooks`` and customize the app to your needs." +"Please see the on-premise data section of the :docs:`data privacy ` chapter." msgstr "" -"Пре свега, у административном панелу вашег окружења идите на Manage Apps. " -"Ако још увек немате апликацију, можете једноставно да додате нову - само " -"потражите ``Incoming WebHooks`` и прилагодите апликацију својим потребама." +"Погледајте одељак о локалним подацима у поглављу :docs:`приватност података " +"`." -#: ../system/integrations/slack.rst:50 +#: ../system/data-privacy.rst:150 +msgid "What about re-assigned tickets? I want to delete them, too." +msgstr "А шта је са поново додељеним тикетима? Желим да избришем и њих." + +#: ../system/data-privacy.rst:148 msgid "" -"Choose (or create) the channel Zammad should post it's information to and " -"press on \"Add Incoming WebHooks integration\". If you're ready, copy the " -"provided WebHook URL and go to your Zammad installation." +"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." msgstr "" -"Изаберите (или додајте) канал у ком Zammad треба да објави своје информације " -"и притисните „Add Incoming WebHooks integration“. Ако сте спремни, копирајте " -"наведени WebHook URL и идите на своју Zammad инсталацију." +"Само тикети додељени дотичном клијенту у тренутну извршавања захтева за " +"брисање података ће бити обрисани. Брисање неће узети у обзир историјат " +"доделе." -#: ../system/integrations/slack.rst:56 +#: ../system/data-privacy.rst:154 +msgid "Why are there so many deletion task entries, I didn't create them!" +msgstr "Одакле сви ови захтеви за брисање, ја их нисам додао!" + +#: ../system/data-privacy.rst:153 msgid "" -"You need administrative rights on the Slack Workspace. The link to the app " -"directory is normally ``https://[workspace-name].slack.com/apps`` ." +"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." msgstr "" -"Потребна су вам административна права за ваше Slack окружење. Линк на " -"директоријум апликација је обично ``https://[назив-окружења].slack.com/" -"apps``." +"Захтеви за брисање могу бити додати и од стране :doc:`планера `. Радња под називом *„Закажи захтев за брисање приватних " +"података”* је извор ових захтева." -#: ../system/integrations/slack.rst:63 +#: ../system/integrations/checkmk/admin-panel-reference.rst:2 +msgid "Admin Panel Reference" +msgstr "Референца администраторског панела" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:None +msgid "Screenshot of Checkmk settings overview" +msgstr "Снимак екрана изгледа Checkmk подешавања" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:12 msgid "" -"To configure the slack integration, log in to Zammad and go to Integrations " -"(System) => Slack in the admin panel." +"Which :doc:`group ` should Checkmk tickets be assigned " +"to as a default (*i.e.,* when none is specified)?" msgstr "" -"Да бисте подесили Slack интеграцију, пријавите се у Zammad и идите на " -"Интеграције (Систем) => Slack у панелу администратора." +"Којој :doc:`групи ` треба да буду подразумевано " +"додељени Checkmk тикети (*тј.* када ниједна није наведена)?" -#: ../system/integrations/slack.rst:66 +#: ../system/integrations/checkmk/admin-panel-reference.rst:15 +msgid "(Applies to :ref:`API alerts ` only.)" +msgstr "(Односи се само на :ref:`API упозорења `.)" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:21 +msgid "Auto close" +msgstr "Аутоматско затварање" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:18 msgid "" -"Here you can choose on what evens Zammad should post information about a " -"ticket to your Slack channel. Next you need to device what groups shall be " -"affected by this, as anybody with access to that specific Slack channel can " -"read at least parts of the ticket this might be a privacy issue, if you " -"select the wrong groups. The username is simply the name that Zammad uses as " -"display name inside the Slack chat. The channel defines the Slack channel " -"the information is being posted in. As last option, you can set a custom " -"icon for posting to slack." +"Should Zammad automatically close tickets if a service has recovered on its " +"own?" +msgstr "Да ли Zammad треба да аутоматски затвори тикете ако се сервис опорави?" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:21 +msgid "(Agents will receive notifications for such closures as appropriate.)" +msgstr "(Оператери ће примати обавештења о затварањима тикета по потреби.)" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:30 +msgid "Auto-close state" +msgstr "Стање аутоматског затварања" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:24 +msgid "What ticket state should be applied when “auto-closing” a ticket?" msgstr "" -"Овде можете да изаберете у ком периоду Zammad треба да објави информације о " -"тикету у вашем Slack каналу. Затим, морате одредити на које групе ће ово " -"утицати, јер свако ко има приступ дотичном Slack каналу може да прочита бар " -"делове тикета, што може представљати проблем приватности ако изаберете " -"погрешне групе. Корисничко име је једноставно назив који Zammad користи као " -"име за приказ у Slack порукама. Канал одређује Slack канал у ком ће бити " -"објављене информације. Као последња опција, можете поставити прилагођену " -"иконицу за слање у Slack." +"Које стање тикета треба применити приликом „аутоматског затварања“ тикета?" -#: ../system/integrations/slack.rst:74 +#: ../system/integrations/checkmk/admin-panel-reference.rst:26 msgid "" -"When you're ready, just hit \"Submit\" and enable the integration. Zammad " -"will now post new ticket information based on the trigger you chose. Below " -"the options you have the recent log that shows the latest requests to Slack " -"for debugging if needed." +"You can choose from the seven built-in ticket states. If these states aren't " +"enough for you, you can :ref:`define a new ticket state ` for this purpose as well. This can be useful for tracking " +"tickets with :doc:`reports `, for example." msgstr "" -"Када будете спремни, само притисните „Пошаљи“ и укључите интеграцију. Zammad " -"ће од сада објављивати нове информације о тикету на основу окидача који сте " -"изабрали. Испод опција имате недавне уносе евиденције који приказује " -"најновије захтеве упућене Slack-у за помоћ приликом отклањања грешака." +"Можете бирати између седам уграђених стања тикета. Ако вам ова стања нису " +"довољна, можете :docs:`дефинисати ново стање тикета `. На пример, ово може бити посебно корисно за праћење тикета " +"помоћу :doc:`извештаја `." -#: ../system/integrations/slack.rst:81 +#: ../system/integrations/checkmk/admin-panel-reference.rst:35 +#: ../system/integrations/cti/includes/recent-logs.include.rst:2 +#: ../system/integrations/ldap/index.rst:74 +#: ../system/integrations/pgp/index.rst:106 +msgid "Recent Logs" +msgstr "Недавни уноси евиденције" + +#: ../system/integrations/checkmk/admin-panel-reference.rst:None +msgid "Screenshot of Checkmk \"Recent Logs\" section" +msgstr "Снимак екрана одељка „Недавни уноси евиденције“ за Checkmk." + +#: ../system/integrations/checkmk/admin-panel-reference.rst:41 msgid "" -"If you leave the Icon URL empty, Zammad will use the Zammad logo instead. " -"The icon should be a square PNG file." +"If you're having trouble getting Zammad and Checkmk to play nicely together, " +"this section can help you troubleshoot." msgstr "" -"Ако оставите URL иконице празан, Zammad ће уместо ње користити Zammad лого. " -"Иконица треба да буде квадратна PNG сличица." +"Ако имате проблема да натерате Zammad и Checkmk да лепо сарађују, овај " +"одељак вам може помоћи да решите проблеме." -#: ../system/integrations/slack.rst:90 +#: ../system/integrations/checkmk/admin-panel-reference.rst:44 msgid "" -"The following figure shows how it will look if you choose to receive updates " -"on created and updated tickets. On every post Zammad sends to the Slack " -"channel, you can create new threads to discuss about the new article." +"It contains a record of the fifty most recent transactions that Zammad knows " +"about, including each one's request/response details and return status." msgstr "" -"Следећа слика приказује како изгледа ако одаберете да примате обавештења о " -"отвореним и освеженим тикетима. На сваки пост који Zammad пошаље у Slack " -"канал, можете отворити тему за дискусију о новом чланку." +"Садржи записе о педесет најновијих трансакција за које Zammad зна, " +"укључујући детаље захтева/одговора и статус одговора." -#: ../system/integrations/slack.rst:96 +#: ../system/integrations/checkmk/api-reference.rst:2 +msgid "API Reference" +msgstr "API референца" + +#: ../system/integrations/checkmk/api-reference.rst:4 msgid "" -"If you just want to keep track of soon escalating or already escalated " -"tickets, it will look the the following figure. Zammad changes the color in " -"front of the post so you can easily see the state of the ticket." +"For most users, :ref:`the sample scripts from the Setup Guide ` will do the job just fine. But if you want more fine-grained control" +"—for instance, to create high- and low-priority tickets for different types " +"of system events—then you'll have to customize the data those scripts send " +"to Zammad." msgstr "" -"Ако само желите да пратите тикете који скоро ескалирају или су већ " -"ескалирали, то ће изгледати као на следећој слици. Zammad мења боју испред " -"поста тако да можете лако да процените стање тикета." +"За већину корисника, :ref:`пример скрипти из водича кроз подешавање ` ће бити сасвим довољан. Али ако желите прецизнију контролу—на " +"пример, да отварате тикете високог и ниског приоритета за различите типове " +"системских догађаја—онда ћете морати да прилагодите податке које те скрипте " +"шаљу Zammad-у." -#: ../system/integrations/slack.rst:102 +#: ../system/integrations/checkmk/api-reference.rst:15 msgid "" -"If you change the state, Zammad will also put information on what state the " -"ticket gets and (if pending state) the date until it pends. You'll also " -"recognize the color codes in front of posts on slack, as they are exact the " -"same the ticket state colors you'll see in Zammad!" +"This custom script will automatically set all tickets it creates to **high " +"priority** and **assign them to charlie@chrispresso.com**." msgstr "" -"Ако промените стање, Zammad ће такође ставити информацију о томе у ком стању " -"је тикет и (ако је на чекању) време чекања тикета. Такође ћете препознати " -"боју стања испред Slack постова, јер су потпуности исте које моћете видети у " -"Zammad-у!" +"Ова прилагођена скрипта ће аутоматски поставити све тикете које отвара на " +"**високи приоритет** и **доделити их на charlie@chrispresso.com**." -#: ../system/integrations/smime/index.rst:2 -msgid "S/MIME" -msgstr "S/MIME" +#: ../system/integrations/checkmk/api-reference.rst:32 +msgid "How Does it Work?" +msgstr "Како то уствари функционише?" -#: ../system/integrations/smime/index.rst:11 +#: ../system/integrations/checkmk/api-reference.rst:34 msgid "" -"S/MIME is the most widely-supported method for secure email communication. " -"With S/MIME, you can exchange **signed** and **encrypted** messages with " -"others." +"There are two kinds of data you can pass to the API, both in the form of key-" +"value pairs:" msgstr "" -"S/MIME је најшире подржани метод за безбедну комуникацију путем имејла. Са S/" -"MIME, можете да размењујете **потписане** и **шифроване** поруке са другима." +"Постоје две врсте података које можете да проследите API-ју, обе у облику " +"парова кључ/вредност:" -#: ../system/integrations/smime/index.rst:15 -msgid "" -"is proof that a message hasn't been tampered with or sent by an impersonator." -msgstr "је доказ да порука није мењана или послата од стране имитатора." +#: ../system/integrations/checkmk/api-reference.rst:44 +msgid "Checkmk parameters" +msgstr "Checkmk параметри" -#: ../system/integrations/smime/index.rst:17 +#: ../system/integrations/checkmk/api-reference.rst:38 msgid "" -"In other words, it guarantees a message's **integrity** and **authenticity**." -msgstr "Другим речима, гарантује **интегритет** и **аутентичност** поруке." +"are required, and make up the **contents** of the resulting tickets/" +"articles. They also determine whether an event creates a new ticket or " +"updates/closes an existing one." +msgstr "" +"су обавезни и чине **садржај** примљених тикета/чланака. Они такође одређују " +"да ли догађај отвара нов тикет или освежава/затвара постојећи." -#: ../system/integrations/smime/index.rst:22 -msgid "In other words, it guarantees **privacy** and **data security**." -msgstr "Другим речима, гарантује **приватност** и **безбедност података**." +#: ../system/integrations/checkmk/api-reference.rst:42 +msgid "" +"These are the only values used in the sample scripts. **Use them as-is**; " +"technically, they can be customized, but it's hard to imagine a good reason " +"for it." +msgstr "" +"Ово су једине вредности које се користе у примерима скрипти. **Користите их " +"баш овако**; технички, могу се прилагодити, али је тешко замислити добар " +"разлог за то." -#: ../system/integrations/smime/index.rst:28 -msgid "Screencast demo of S/MIME features for both new tickets and replies" -msgstr "Снимак екрана са S/MIME функцијом за нове тикете и одговоре" +#: ../system/integrations/checkmk/api-reference.rst:52 +msgid "Ticket attributes" +msgstr "Атрибути тикета" -#: ../system/integrations/smime/index.rst:28 +#: ../system/integrations/checkmk/api-reference.rst:47 msgid "" -"Once S/MIME has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " -"appear in the ticket composer." +"are optional, and can be used to **adjust settings** on newly created " +"tickets (*e.g.,* set the owner, group, priority, or state)." msgstr "" -"Када се S/MIME укључи, дугмићи 🔒 **Шифровање** и ✅ **Потписивање** " -"појавиће се у дијалогу новог тикета." - -#: ../system/integrations/smime/index.rst:32 -msgid ":doc:`🔪 Prerequisites `" -msgstr ":doc:`🔪 Предуслови `" +"су опциони и могу се користити за **прилагођавање подешавања** за " +"новоотворене тикете (*нпр.* постављање власника, групе, приоритета или " +"стања)." -#: ../system/integrations/smime/index.rst:31 +#: ../system/integrations/checkmk/api-reference.rst:50 msgid "" -"New to S/MIME? This section helps you to find certificate providers and " -"points out Limitations." +"If you want to customize your Checkmk alert script, do it with these. Simply " +"add an extra “form” option for each one (``-F \"key=value\"``) to your " +"script's ``curl`` command line, as in the example above." msgstr "" -"Нови сте у S/MIME свету? Овај одељак вам помаже да пронађете провајдере " -"сертификата и указује на постојећа ограничења." +"Ако желите да прилагодите своју Checkmk скрипту упозорења, урадите то на " +"овај начин. Једноставно додајте опцију „form“ за сваку (``-F " +"\"кључ=вредност\"``) групу у командној ``curl`` линији ваше скрипте, као у " +"примеру изнад." -#: ../system/integrations/smime/index.rst:35 -msgid ":doc:`📝 Manage Certificates `" -msgstr ":doc:`📝 Управљање сертификатима `" +#: ../system/integrations/checkmk/api-reference.rst:54 +msgid "💡 **It's just an API endpoint!**" +msgstr "💡 **То је само API путања!**" -#: ../system/integrations/smime/index.rst:35 -msgid "Add and download certificates; configure group default behaviors." +#: ../system/integrations/checkmk/api-reference.rst:56 +msgid "" +"When using Checkmk integration, messages need to be formatted in a certain " +"way, but that *doesn't mean the messages actually have to come from Checkmk*." msgstr "" -"Додајте и преузмите сертификате; подесите подразумевано понашање група." - -#: ../system/integrations/smime/index.rst:38 -msgid ":doc:`😦 Troubleshooting `" -msgstr ":doc:`😦 Решавање проблема `" +"Када користите Checkmk интеграцију, поруке морају бити форматиране на " +"одређени начин, али то *не значи да поруке заправо морају да долазе од " +"Checkmk*." -#: ../system/integrations/smime/index.rst:38 -msgid "Took a wrong turn? About recent logs and common issues." +#: ../system/integrations/checkmk/api-reference.rst:59 +msgid "" +"If you use another monitoring tool that's not officially supported by " +"Zammad, there's probably a way to make it work with your Checkmk callback " +"URL." msgstr "" -"Погрешно сте скренули код Албукеркија? О недавним уносима евиденције и " -"уобичајеним проблемима." +"Ако користите други алат за праћење који Zammad званично не подржава, " +"вероватно постоји начин да га натерате да ради са вашом Checkmk URL адресом " +"повратног позива." -#: ../system/integrations/smime/index.rst:43 +#: ../system/integrations/checkmk/api-reference.rst:63 +msgid "Checkmk Parameters" +msgstr "Checkmk параметери" + +#: ../system/integrations/checkmk/api-reference.rst:65 msgid "" -"For more details on how S/MIME integration works on the agent side, see the :" -"user-docs:`user docs `." +"When a notification is received, Zammad creates a new article containing the " +"details of the event that triggered it:" msgstr "" -"За више детаља о томе како S/MIME интеграција функционише на страни " -"оператера, погледајте :user-docs:`корисничку документацију `." +"По примању упозорења, Zammad додаје нови чланак који садржи детаље догађаја " +"који га је покренуо:" -#: ../system/integrations/smime/manage-certificates.rst:2 -msgid "Manage Certificates" -msgstr "Управљање сертификатима" +#: ../system/integrations/checkmk/api-reference.rst:None +msgid "Checkmk article body" +msgstr "Checkmk текст чланка" -#: ../system/integrations/smime/manage-certificates.rst:4 +#: ../system/integrations/checkmk/api-reference.rst:72 msgid "" -"S/MIME is **disabled by default**. Enable it to start adding certificates." +"These details come from the fields listed below, which correspond to " +"parameters provided by Checkmk (``$NOTIFY_*``)." msgstr "" -"S/MIME је **подразумевано искључен**. Укључите га да бисте почели да " -"додајете сертификате." +"Ови детаљи потичу из поља наведених у наставку, која одговарају параметрима " +"које обезбеђује Checkmk (``$NOTIFY_*``)." -#: ../system/integrations/smime/manage-certificates.rst:10 -msgid "Dialogue to add new certificates or private keys" -msgstr "Дијалог за додавање нових сертификата или тајних кључева" +#: ../system/integrations/checkmk/api-reference.rst:75 +msgid "**Required fields are marked with an asterisk (\\*).**" +msgstr "**Обавезна поља су означена звездицом (\\*).**" + +#: ../system/integrations/checkmk/api-reference.rst:79 +msgid "event_id\\*" +msgstr "event_id\\*" -#: ../system/integrations/smime/manage-certificates.rst:10 +#: ../system/integrations/checkmk/api-reference.rst:78 msgid "" -"Manage certificates in the Admin Panel under **System > Integrations > S/" -"MIME**. Certificates may be pasted in as plain text or uploaded from a file." +"A unique ID for the system event. (``$NOTIFY_SERVICEPROBLEMID`` / " +"``$NOTIFY_HOSTPROBLEMID``)" msgstr "" -"Управљање сертификатима се обавља у административном панелу под **Систем > " -"Интеграције > S/MIME**. Сертификати се могу налепити као обичан текст или " -"отпремити из датотеке." - -#: ../system/integrations/smime/manage-certificates.rst:14 -msgid "Add Certificate Data" -msgstr "Додавање података о сертификату" +"Јединствени ID за системски догађај. (``$NOTIFY_SERVICEPROBLEMID`` / " +"``$NOTIFY_HOSTPROBLEMID``)" -#: ../system/integrations/smime/manage-certificates.rst:36 -msgid "Add Certificate" -msgstr "Додај сертификат" +#: ../system/integrations/checkmk/api-reference.rst:86 +msgid "host\\*" +msgstr "host\\*" -#: ../system/integrations/smime/manage-certificates.rst:17 +#: ../system/integrations/checkmk/api-reference.rst:82 msgid "" -"Import public-key certificates for both your own organization and your " -"contacts." -msgstr "Увезите јавни сертификат и за своју организацију и за своје контакте." +"The hostname of the system that the event originated from. " +"(``$NOTIFY_HOSTNAME``)" +msgstr "Назив хоста система из којег је настао догађај. (``$NOTIFY_HOSTNAME``)" -#: ../system/integrations/smime/manage-certificates.rst:19 +#: ../system/integrations/checkmk/api-reference.rst:85 msgid "" -"You can also add a bunch of certificates in one go by providing a single " -"file with all relevant certificates." +"Used to determine if a new event belongs to an existing ticket. Also used in " +"the subject line of the resulting article (“ is ”)." msgstr "" -"Такође можете додати више сертификата одједном тако што ћете обезбедити " -"једну датотеку са свим релевантним сертификатима." +"Користи се за одређивање да ли нови догађај припада постојећем тикету. " +"Такође се користи у предмету новонасталог чланка („ is ”)." -#: ../system/integrations/smime/manage-certificates.rst:22 -msgid "🕵️ **ALWAYS verify certificates in-person or over the phone!**" -msgstr "🕵 ** УВЕК проверите добијене сертификате лично или телефоном!**" +#: ../system/integrations/checkmk/api-reference.rst:96 +msgid "service" +msgstr "service" -#: ../system/integrations/smime/manage-certificates.rst:24 +#: ../system/integrations/checkmk/api-reference.rst:89 msgid "" -"The whole point of signatures is to alert you when someone is trying to " -"pretend to be someone they're not. Never accept a certificate from someone " -"online without verifying it first." -msgstr "" -"Читава поента потписа је да вас упозори ако неко покушава да се преставља " -"као нека друга особа. Никада не прихватајте сертификат од некога на мрежи, а " -"да га претходно нисте проверили." +"The name of the service that the event originated from. " +"(``$NOTIFY_SERVICEDESC``)" +msgstr "Назив сервиса из кога је догађај настао. (``$NOTIFY_SERVICEDESC``)" -#: ../system/integrations/smime/manage-certificates.rst:28 -msgid "📇 **What about trusted certificate authorities?**" -msgstr "📇 **А шта са поузданим органима за сертификацију?**" +#: ../system/integrations/checkmk/api-reference.rst:92 +msgid "Used to determine if a new event belongs to an existing ticket." +msgstr "Користи се за одређивање да ли нови догађај припада постојећем тикету." -#: ../system/integrations/smime/manage-certificates.rst:30 +#: ../system/integrations/checkmk/api-reference.rst:94 +#: ../system/integrations/checkmk/api-reference.rst:110 +msgid "Displayed as ``-`` when omitted." +msgstr "Приказује се као ``-`` када се изостави." + +#: ../system/integrations/checkmk/api-reference.rst:104 +msgid "state\\*" +msgstr "state\\*" + +#: ../system/integrations/checkmk/api-reference.rst:99 msgid "" -"In some cases (e.g. when dealing with large enterprises), you may be given a " -"certificate for an entire CA, rather than a single contact. Add it here to " -"trust *all* certificates issued by that CA." +"The current state of the service or host in question. " +"(``$NOTIFY_SERVICESTATE`` / ``$NOTIFY_HOSTSTATE``)" msgstr "" -"У неким случајевима (нпр. када имате посла са великим предузећима), можда " -"ћете добити CA сертификат, а не само за један контакт. Додајте га овде да " -"бисте убудуће веровали *свим* сертификатима које је издао тај CA." +"Тренутно стање дотичног сервиса или хоста. (``$NOTIFY_SERVICESTATE`` / " +"``$NOTIFY_HOSTSTATE``)" -#: ../system/integrations/smime/manage-certificates.rst:35 +#: ../system/integrations/checkmk/api-reference.rst:102 msgid "" -"Commercial CAs can usually be verified online. Zammad does not include a " -"list of built-in, trusted CAs." +"Used to detect when a ticket should be auto-closed (*i.e.,* on ``OK``/" +"``UP``). Also used in the subject line of the resulting article (“ is " +"”)." msgstr "" -"Комерцијални CA се обично могу проверити путем мреже. Zammad не садржи " -"уграђене CA сертификате." +"Користи се за откривање када би тикет требало да се аутоматски затвори (*тј." +"* на ``OK``/``UP``). Такође се користи у предмету новонасталог чланка " +"(„ is ”)." -#: ../system/integrations/smime/manage-certificates.rst:57 -msgid "Add Private Key" -msgstr "Додавање тајног кључа" +#: ../system/integrations/checkmk/api-reference.rst:110 +msgid "text" +msgstr "text" -#: ../system/integrations/smime/manage-certificates.rst:39 +#: ../system/integrations/checkmk/api-reference.rst:107 msgid "" -"Once you've added a public-key certificate, you can import its matching " -"private key." +"The output of the process that triggered the event. " +"(``$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" msgstr "" -"Када додате јавни сертификат, можете да увезете и његов одговарајући тајни " -"кључ." +"Излазни подаци процеса који је покренуо догађај. " +"(``$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" -#: ../system/integrations/smime/manage-certificates.rst:42 +#: ../system/integrations/checkmk/api-reference.rst:121 msgid "" -"Private keys are for **your own organization only**; never ask your contacts " -"for their private keys." +"The Object Manager attribute panel displays built-in and custom\n" +"attribute names." msgstr "" -"Тајни кључеви су за **само вашу организацију**; никада не питајте своје " -"контакте за њихове приватне кључеве." +"Панел управљања атрибутима објекта приказује уграђене и прилагођене\n" +"називе атрибута." -#: ../system/integrations/smime/manage-certificates.rst:0 +#: ../system/integrations/checkmk/api-reference.rst:121 +msgid "Find a complete list of ticket attributes in the Object Manager." +msgstr "Пронађите комплетну листу атрибута тикета у управљању објектима." + +#: ../system/integrations/checkmk/api-reference.rst:123 msgid "" -"S/MIME integration showing configured certificates and possible issues with " -"Logging" +"Ticket attributes are entirely optional, and can be used to customize the " +"tickets that Checkmk creates. (Note that these attributes will be ignored if " +"a new event belongs to an existing ticket.)" msgstr "" -"S/MIME интеграција која приказује подешене сертификате и могуће проблеме у " -"евиденцији" +"Атрибути тикета су потпуно опциони и могу се користити за прилагођавање " +"тикета које Checkmk креира. (Имајте на уму да ће ови атрибути бити " +"занемарени ако нови догађај припада постојећем тикету.)" -#: ../system/integrations/smime/manage-certificates.rst:50 +#: ../system/integrations/checkmk/api-reference.rst:128 msgid "" -"A note is displayed on certificates with a matching private key (see line 2)." +"Why would you want to do this? Maybe you have only one IT guy, and all " +"system monitoring issues should be automatically assigned to him. Or, maybe " +"you're creating multiple notification rules so that database outages take " +"higher priority than disk space warnings." msgstr "" -"На сертификатима са одговарајућим тајним кључем приказана је напомена " -"(погледајте други ред)." +"Зашто бисте желели ово да урадите? Можда имате само једног IT момка и сви " +"проблеми праћења система би требали бити аутоматски додељени баш њему. Или, " +"можда одређујете више правила за упозорења тако да прекиди у доступности " +"базе података имају већи приоритет од упозорења о преосталом простору на " +"диску." -#: ../system/integrations/smime/manage-certificates.rst:52 -msgid "📤 **Certificates and private keys must be uploaded separately.**" +#: ../system/integrations/checkmk/api-reference.rst:135 +msgid "In most cases, you'll probably want to set one of the following:" msgstr "" -"📤 **Сертификати и тајни кључеви морају да се увезу одвојено једни од других." -"**" +"У већини случајева, вероватно ћете желети да подесите бар једно од следећег:" -#: ../system/integrations/smime/manage-certificates.rst:54 -msgid "" -"If your certificate and private key are bundled together in the same file or " -"PEM block, import it twice (once using each button)." -msgstr "" -"Ако су ваш сертификат и тајни кључ комбиновани у исту датотеку или PEM " -"блоку, увезите их два пута (по једном користећи свако дугме)." +#: ../system/integrations/checkmk/api-reference.rst:137 +msgid "group" +msgstr "group" -#: ../system/integrations/smime/manage-certificates.rst:57 -msgid "Please note that bulk imports of private keys are not possible." -msgstr "Имајте на уму да масовна радња увоза тајних кључева није могућа." +#: ../system/integrations/checkmk/api-reference.rst:139 +msgid "state" +msgstr "state" -#: ../system/integrations/smime/manage-certificates.rst:60 -msgid "Download Certificate Data" -msgstr "Преузмите податке о сертификату" +#: ../system/integrations/checkmk/api-reference.rst:140 +msgid "priority" +msgstr "priority" -#: ../system/integrations/smime/manage-certificates.rst:62 +#: ../system/integrations/checkmk/api-reference.rst:142 msgid "" -"You can download the earlier provided certificates and private keys at any " -"time from your Zammad instance." +"but in practice, you can set almost any attribute, including :doc:`custom " +"ones you created through the Object Manager `." msgstr "" -"Можете преузети раније достављене сертификате и тајне кључеве у било ком " -"тренутку из своје Zammad инстанце." +"али у пракси, можете подесити скоро све атрибуте, укључујући :doc:" +"`прилагођене атрибуте које сте додали преко панела за управљање објектима `." -#: ../system/integrations/smime/manage-certificates.rst:65 -msgid "" -"Please note that passphrase-protected private keys stay protected and when " -"you download them, you have to know the passphrase to use them after " -"downloading." -msgstr "" -"Обратите пажњу да тајни кључеви заштићени лозинком остају заштићени и када " -"их преузмете, мораћете да знате лозинку да бисте их користили по преузимању." +#: ../system/integrations/checkmk/api-reference.rst:145 +msgid "Please note that the following attributes are **not customizable**:" +msgstr "Имајте на уму да се следећи атрибути се **не могу прилагодити**:" -#: ../system/integrations/smime/manage-certificates.rst:73 -msgid "Dialogue to download certificates or private keys" -msgstr "Дијалог за преузимање сертификата или тајних кључева" +#: ../system/integrations/checkmk/api-reference.rst:147 +msgid "title" +msgstr "title" -#: ../system/integrations/smime/manage-certificates.rst:73 -msgid "Download stored certificates and their keys" -msgstr "Преузмите сачуване сертификате и њихове кључеве" +#: ../system/integrations/checkmk/api-reference.rst:148 +msgid "id" +msgstr "id" -#: ../system/integrations/smime/manage-certificates.rst:78 +#: ../system/integrations/checkmk/api-reference.rst:149 +msgid "ticket number" +msgstr "ticket number" + +#: ../system/integrations/checkmk/api-reference.rst:151 +msgid "created_by_id" +msgstr "created_by_id" + +#: ../system/integrations/checkmk/api-reference.rst:152 +msgid "updated_by_id" +msgstr "updated_by_id" + +#: ../system/integrations/checkmk/api-reference.rst:155 +msgid "Which Values Can Be Set?" +msgstr "Које вредности је могуће поставити?" + +#: ../system/integrations/checkmk/api-reference.rst:157 +msgid "😵 **Invalid values → unpredictable behavior**" +msgstr "😵 **Неисправне вредности → непредвидљиво понашање**" + +#: ../system/integrations/checkmk/api-reference.rst:159 msgid "" -"The ticket composer will set all outgoing messages to **signed and " -"encrypted** by default (assuming the required certificates exist)." +"If you provide a value that Zammad doesn't understand (*e.g.,* ``-F " +"\"priority=high\"``), it's not always clear what will happen. In some cases, " +"a ticket will be created with the default values instead - but in others, it " +"may not be created at all!" msgstr "" -"Дијалог новог тикета ће укључити **потписивање и шифровање** за све одлазне " -"поруке по подразумеваној вредности (под претпоставком да одговарајући " -"сертификати постоје)." +"Ако наведете вредност коју Zammad не разуме (*нпр.* ``-F " +"\"priority=high\"``), није увек сасвим јасно шта ће се догодити. У неким " +"случајевима ће се уместо тога отворити тикет са подразумеваним вредностима — " +"али у другим, можда неће бити уопште отворен!" + +#: ../system/integrations/checkmk/api-reference.rst:164 +msgid "So what values does Zammad understand, then? Well, it depends..." +msgstr "Дакле, које вредности Zammad разуме? Па, зависи..." -#: ../system/integrations/smime/manage-certificates.rst:82 -msgid "These defaults can be modified on a per-group basis:" -msgstr "Ове подразумеване вредности могу да се мењају на основу групе:" +#: ../system/integrations/checkmk/api-reference.rst:168 +msgid "Use an email address or username:" +msgstr "Користите имејл адресу или корисничко име:" -#: ../system/integrations/smime/manage-certificates.rst:None -msgid "Zammad allowing to choose the default behavior on per group basis" -msgstr "Zammad омогућава подешавање подразумеваног понашања по одабраној групи" +#: ../system/integrations/checkmk/api-reference.rst:190 +msgid "group & priority" +msgstr "group & priority" -#: ../system/integrations/smime/manage-certificates.rst:89 -msgid "" -"Of course, agents can always manually change these settings on each email " -"they send out." -msgstr "" -"Наравно, оператери увек могу ручно да преиначе ова подешавања за сваку имејл " -"поруку коју пошаљу." +#: ../system/integrations/checkmk/api-reference.rst:175 +msgid "Refer to the dropdown menus in the ticket pane:" +msgstr "Погледајте падајуће меније у панелу тикета:" -#: ../system/integrations/smime/prerequisites.rst:4 -msgid "A certificate *and* private key for your own organization" -msgstr "Сертификат *и* тајни кључ за вашу организацију" +#: ../system/integrations/checkmk/api-reference.rst:0 +msgid "See possible values for certain attributes in the ticket pane." +msgstr "Погледајте могуће вредности за одређене атрибуте у панелу тикета." -#: ../system/integrations/smime/prerequisites.rst:6 -msgid "" -"(Use this to ✒️ **sign outgoing messages** and 🔓 **decrypt incoming " -"messages**.)" -msgstr "" -"(Користите опцију ✒ за **потписивање одлазних порука** и 🔓за **дешифровање " -"долазних порука**.)" +#: ../system/integrations/checkmk/api-reference.rst:187 +msgid "🙅 **Ticket state CANNOT be set this way!**" +msgstr "🙅 **Стање тикета НЕ МОЖЕ да се подеси на овај начин!**" -#: ../system/integrations/smime/prerequisites.rst:9 +#: ../system/integrations/checkmk/api-reference.rst:189 msgid "" -"Certificates belonging your contacts, or their issuing certificate authority " -"(CA)" +"Why? Because ``-F \"state=...\"`` is already used :ref:`as a Checkmk " +"parameter `." msgstr "" -"Сертификати који припадају вашим контактима или њиховим органима за издавање " -"сертификата (CA)" +"Зашто? Зато што се ``-F \"state=...\"`` већ користи :ref:`као Checkmk " +"параметар `." -#: ../system/integrations/smime/prerequisites.rst:11 +#: ../system/integrations/checkmk/api-reference.rst:222 +msgid "Everything Else" +msgstr "Све остало" + +#: ../system/integrations/checkmk/api-reference.rst:193 msgid "" -"(Use these to ✅ **verify incoming message signatures** and 🔒 **encrypt " -"outgoing messages**.)" +"To set any other attributes, it helps to know your way around the :docs:" +"`rails console `. Valid values are those that you can " +"set with a string:" msgstr "" -"(Користите опцију ✅ да **верификујете потписе долазних порука** и 🔒 да " -"**шифрујете одлазне поруке**.)" +"Да бисте подесили било које друге атрибуте, помоћи ће вам да знате да се " +"снађете у :docs:`rails конзоли `. Важеће вредности су " +"оне које можете поставити текстуалним низом:" -#: ../system/integrations/smime/prerequisites.rst:14 -msgid "🙋 **I'm new to S/MIME. Where can I get a certificate?**" -msgstr "🙋 **Нов сам у S/MIME свету. Где могу набавити сертификат?**" +#: ../system/integrations/checkmk/api-reference.rst:218 +msgid "These values can then be passed directly to the API:" +msgstr "Ове вредности се затим могу пренети директно у API:" -#: ../system/integrations/smime/prerequisites.rst:16 -msgid "" -"The easiest way to get certificates is to buy an annual subscription through " -"a commercial CA, such as:" -msgstr "" -"Најлакши начин да набавите сертификате је да купите годишњу претплату преко " -"комерцијалног CA, као што су:" +#: ../system/integrations/checkmk/index.rst:16 +msgid "How does it work?" +msgstr "Како то уствари функционише?" -#: ../system/integrations/smime/prerequisites.rst:19 +#: ../system/integrations/checkmk/index.rst:2 +msgid "Checkmk" +msgstr "Checkmk" + +#: ../system/integrations/checkmk/index.rst:4 msgid "" -"`Sectigo (formerly Comodo) `_" +"`Checkmk `_ is a powerful IT monitoring tool that can " +"send real-time status alerts to Zammad via email or REST API. Set these " +"alerts up in Checkmk, and Zammad will automatically create, update, and " +"close tickets based on the health of your system:" msgstr "" -"`Sectigo (раније Comodo) `_" +"`Checkmk `_ је моћан алат за IT праћење који може да " +"шаље обавештења о статусу Zammad-а у реалном времену путем имејла или REST " +"API. Подесите ова упозорења у Checkmk и Zammad ће аутоматски отварати, " +"освежавати и затварати тикете на основу здравља вашег система:" -#: ../system/integrations/smime/prerequisites.rst:20 -msgid "`Secorio `_" -msgstr "`Secorio `_" +#: ../system/integrations/checkmk/index.rst:14 +msgid "Screenshot of ticket created by Checkmk notifications" +msgstr "Снимак екрана тикета отвореног на основу Checkmk упозорења" -#: ../system/integrations/smime/prerequisites.rst:21 -msgid "`GlobalSign `_" -msgstr "`GlobalSign `_" +#: ../system/integrations/checkmk/index.rst:14 +msgid "Multiple alerts, same ticket." +msgstr "Више упозорења, исти тикет." -#: ../system/integrations/smime/prerequisites.rst:23 -msgid "(Zammad is not affiliated with these CAs in any way.)" -msgstr "(Zammad није ни на који начин повезан са овим CA органима.)" +#: ../system/integrations/checkmk/setup-guide.rst:2 +msgid "Setup Guide" +msgstr "Водич кроз подешавање" -#: ../system/integrations/smime/prerequisites.rst:25 +#: ../system/integrations/checkmk/setup-guide.rst:4 msgid "" -"You can also generate your own self-signed certificates, but the process is " -"complicated and usually 🙅 **involves extra work for your contacts**." +"Whenever the Checkmk integration is enabled, Zammad listens for messages on " +"its API and over email. As long as those messages follow the required " +"format, Zammad will create new tickets (or find and update existing ones) " +"based on the message contents." msgstr "" -"Такође можете да генеришете сопствене самопотписане сертификате, али процес " -"је компликован и обично 🙅 **укључује додатни посао за ваше контакте**." +"Кад год је Checkmk интеграција укључена, Zammad ослушкује захтеве на свом " +"API-ју и путем имејла. Све док те поруке прате очекивани формат, Zammad ће " +"отварати нове тикете (или пронаћи и освежити постојеће) на основу садржаја " +"поруке." -#: ../system/integrations/smime/prerequisites.rst:29 +#: ../system/integrations/checkmk/setup-guide.rst:10 msgid "" -"Bear in mind that 🤝 **S/MIME only works if the other party is using it, too." -"**" +"That means that “setting up Checkmk integration” is simply a matter of " +"**adding configuration to your Checkmk site**: telling it when to send these " +"messages and what to say. To do that, you'll need to create a new " +"**notification rule** (see `Checkmk's official docs `_ for help with that)." msgstr "" -"Имајте на уму да 🤝 **S/MIME функционише само ако га користи и друга страна." -"**" - -#: ../system/integrations/smime/prerequisites.rst:32 -msgid "Certificate and Private Key Checks on Upload" -msgstr "Провере сертификата и тајног кључа при отпремању" +"То значи да је „подешавање Checkmk интеграције“ једноставно питање " +"**додавања конфигурације вашој Checkmk инстанци**: да јој кажете када да " +"пошаље ове поруке и шта у њима да каже. Да бисте то урадили, мораћете да " +"дефинишете нови **notification rule** (погледајте `Checkmk званичну " +"документацију `_ за додатну " +"помоћ)." -#: ../system/integrations/smime/prerequisites.rst:34 +#: ../system/integrations/checkmk/setup-guide.rst:17 msgid "" -"The certificate and public key validation is based on the ``X509v3`` " -"extensions." +"As part of this new rule, you'll have to choose a **notification method** " +"(*i.e.,* a script to execute whenever the rule is triggered). This script " +"will be written by you (samples below), and contain the logic for sending " +"API/email messages to Zammad:" msgstr "" -"Провера сертификата и јавног кључа је заснована на ``X509v3`` екстензијама." - -#: ../system/integrations/smime/prerequisites.rst:49 -msgid "Uploading a *client certificate*?" -msgstr "Отпремате *сертификат клијента*?" +"Као део овог новог правила, мораћете да изаберете **notification method** " +"(*тј.* скрипту која ће се извршити кад год се правило покрене). Ову скрипту " +"ћете доставити ви (примери су испод) и она ће садржати логику за слање API/" +"имејл порука Zammad-у:" -#: ../system/integrations/smime/prerequisites.rst:41 -msgid "The following attributes are required then:" -msgstr "Следећи атрибути су тада обавезни:" +#: ../system/integrations/checkmk/setup-guide.rst:26 +msgid "Checkmk \"New Rule\" dialog" +msgstr "Checkmk дијалог за „New Rule“" -#: ../system/integrations/smime/prerequisites.rst:39 -msgid "Subject Alternative Name (at least one email address has to be present)" +#: ../system/integrations/checkmk/setup-guide.rst:26 +msgid "" +"Find your custom scripts in the Checkmk WATO under **Notifications > New " +"Rule > Notification Method**." msgstr "" -"Subject Alternative Name (мора бити присутна најмање једна имејл адреса)" - -#: ../system/integrations/smime/prerequisites.rst:40 -msgid "Key Usage (``Digital Signature`` and/or ``Key Encipherment``)" -msgstr "Key Usage (``Digital Signature`` и/или ``Key Encipherment``)" - -#: ../system/integrations/smime/prerequisites.rst:41 -msgid "Public key algorithm (either ``RSA`` or ``EC``)" -msgstr "Public key algorithm (или ``RSA`` или ``EC``)" +"Пронађите своје прилагођене скрипте у Checkmk WATO под **Notifications > New " +"Rule > Notification Method**." -#: ../system/integrations/smime/prerequisites.rst:43 +#: ../system/integrations/checkmk/setup-guide.rst:29 msgid "" -"The Extended Key Usage attribute is optional. If the certificate provides " -"the named attribute, than it must contain the value ``E-mail Protection``." +"Once you're done setting up your new rule, you're all set! New tickets " +"should start coming in and auto-updating any time your rule is triggered." msgstr "" -"Атрибут Extended Key Usage је опционалан. Ако сертификат садржи дотични " -"атрибут, онда мора да садржи вредност ``E-mail Protection``." +"Када завршите са подешавањем новог правила, све је спремно! Нови тикети би " +"требало да почну да стижу и аутоматски се освежавају сваки пут када се ваше " +"правило окине." -#: ../system/integrations/smime/prerequisites.rst:46 +#: ../system/integrations/checkmk/setup-guide.rst:33 msgid "" -"Please note that any usable email adress has to be prefixed with ``email:`` " -"or ``rfc822:``." +"(If you need help troubleshooting, be sure to check the :ref:`checkmk-recent-" +"logs`.)" msgstr "" -"Имајте на уму да свака употребљива имејл адреса мора имати префикс ``email:" -"`` или ``rfc822:``." - -#: ../system/integrations/smime/prerequisites.rst:49 -msgid "The named public key algorithms are mandatory for private keys as well." -msgstr "Именовани алгоритми јавног кључа су обавезни и за тајне кључеве." +"(Ако вам је потребна помоћ у решавању проблема, обавезно проверите :ref:" +"`checkmk-recent-logs`.)" -#: ../system/integrations/smime/prerequisites.rst:54 -msgid "Uploading a *CA certificate*?" -msgstr "Отпремате *CA сертификат*?" +#: ../system/integrations/checkmk/setup-guide.rst:38 +msgid "API Alerts" +msgstr "API упозорења" -#: ../system/integrations/smime/prerequisites.rst:52 +#: ../system/integrations/checkmk/setup-guide.rst:40 msgid "" -"In the case of an uploaded CA certificate, providing the value ``CA:TRUE`` " -"in the attribute *Basic Contstraints*, the previously mentioned attributes " -"are not verified." +"To add these scripts in the Checkmk WATO, copy them into your Checkmk " +"installation directory and make them executable. (Be sure to replace the " +"``zammad.example.com`` callback URL with the one found in your admin panel.)" msgstr "" -"У случају када отпремљени CA сертификат има вредност ``CA:TRUE`` за *Basic " -"Contstraints* атрибут, претходно излистани атрибути неће бити проверени." +"Да бисте додали ове скрипте у Checkmk WATO, копирајте их у свој Checkmk " +"инсталациони директоријум и учините их извршним. (Обавезно замените ``zammad." +"example.com`` URL адресу повратног позива оном која се налази у вашем " +"администраторском панелу.)" -#: ../system/integrations/smime/prerequisites.rst:56 +#: ../system/integrations/checkmk/setup-guide.rst:60 +msgid "Service notification" +msgstr "Сервисна упозорења" + +#: ../system/integrations/checkmk/setup-guide.rst:46 msgid "" -"In general, the usage of any expired (``Not After``) or not yet valid (``Not " -"Before``) certificate is denied for outgoing emails." +"For updates on the status of the software running on your server (*e.g.,* " +"postgres)." msgstr "" -"Уопштено говорећи, употреба сертификата који је истекао (``Not After``) или " -"још увек није важећи (``Not Before``) биће онемогућена за одлазне имејл " -"поруке." +"За свежавање статуса софтвера који ради на вашем серверу (*нпр.* postgres)." + +#: ../system/integrations/checkmk/setup-guide.rst:75 +msgid "Host notification" +msgstr "Упозорења о серверу" + +#: ../system/integrations/checkmk/setup-guide.rst:63 +msgid "For updates on the status of the server itself." +msgstr "За освежавање статуса самог сервера." -#: ../system/integrations/smime/prerequisites.rst:59 -msgid "Example certificate:" -msgstr "Пример сертификата:" +#: ../system/integrations/checkmk/setup-guide.rst:77 +msgid "🤔 **What's with all the env vars?**" +msgstr "🤔 **Чему служе све ове променљиве окружења?**" -#: ../system/integrations/smime/prerequisites.rst:85 +#: ../system/integrations/checkmk/setup-guide.rst:79 msgid "" -"Please note that Zammad will distrust senders by default. This means that " -"you're always required to provide certificate data, no matter if for signing " -"or encrypting." +"Whenever Checkmk runs these scripts, it needs to provide some information " +"about the event that triggered the notification. This information is passed " +"in the form of these ``$NOTIFY_*`` environment variables." msgstr "" -"Имајте на уму да Zammad подразумевано неће веровати пошиљаоцима. То значи да " -"се од вас увек тражи да обезбедите податке сертификата, без обзира да ли за " -"потписивање или шифровање." - -#: ../system/integrations/smime/prerequisites.rst:89 -msgid "This is by design and can't be adjusted." -msgstr "Ово је по пројекту и не може се променити." +"Кад год Checkmk покрене ове скрипте, мора да пружи неке информације о " +"догађају који је окинуо упозорење. Ове информације се прослеђују у облику " +"ових ``$NOTIFY_*`` променљивих из окружења." -#: ../system/integrations/smime/troubleshooting.rst:4 +#: ../system/integrations/checkmk/setup-guide.rst:85 msgid "" -"All of the system's latest S/MIME activity is displayed in the **Recent " -"Logs** section." +"You can specify additional parameters to pass to the script when you're " +"setting up your notification rule, but the ones you see here are all " +"provided by default." msgstr "" -"Све најновије S/MIME активности система су приказане у одељку **Недавни " -"уноси евиденције**." +"Можете да наведете додатне параметре које ћете проследити скрипти када " +"прилагођавате своје правило упозорења, али они које видите овде су " +"подразумевано обезбеђени." -#: ../system/integrations/smime/troubleshooting.rst:11 -msgid "Sample entries of in- and outgoing S/MIME related emails." -msgstr "Примери уноса долазних и одлазних S/MIME имејл порука." +#: ../system/integrations/checkmk/setup-guide.rst:90 +msgid "Email Alerts" +msgstr "Имејл упозорења" -#: ../system/integrations/smime/troubleshooting.rst:11 +#: ../system/integrations/checkmk/setup-guide.rst:94 msgid "" -"Logs report the status and details of all mail, both incoming and outgoing, " -"that used signing/verification or encryption/decryption." +"🐞 **There are known bugs** in Zammad's processing of email from Checkmk. " +"This section will be completed once they have been resolved. (Learn more at " +"GitHub issues `#2377 `_ & " +"`#2180 `_.)" msgstr "" -"Евиденција извештава о статусу и детаљима свих порука, како долазних тако и " -"одлазних, које су користиле функције потписивања/верификације или шифровања/" -"дешифровања." +"🐞 **Постоје познате грешке** у Zammad-овој обради Checkmk имејл порука. " +"Овај одељак ће бити комплетиран када буду решене. (Сазнајте више у GitHub " +"извештајима `#2377 `_ и `#2180 " +"`_.)" -#: ../system/integrations/smime/troubleshooting.rst:14 -msgid "" -"This log does **not** include email sent by :doc:`triggers ` or the :doc:`scheduler `. For those, check your " -"``production.log``." +#: ../system/integrations/checkmk/setup-guide.rst:100 +msgid "In the meantime, we encourage you to set up API alerts instead." msgstr "" -"Ова евиденција **не** укључује имејл поруке које шаљу :doc:`окидачи ` и :doc:`планери `. За њих, проверите своју " -"``production.log`` датотеку." - -#: ../system/integrations/smime/troubleshooting.rst:20 -msgid "Common Issues" -msgstr "Уобичајени проблеми" +"У међувремену, препоручујемо вам да уместо тога подесите API упозорења." -#: ../system/integrations/smime/troubleshooting.rst:30 -msgid "I received a signed/encrypted email before I set up S/MIME integration" -msgstr "" -"Добио сам потписану/шифровану имејл поруку пре него што је подешена S/MIME " -"интеграција" +#: ../system/integrations/clearbit.rst:2 +msgid "Clearbit" +msgstr "Clearbit" -#: ../system/integrations/smime/troubleshooting.rst:23 +#: ../system/integrations/clearbit.rst:4 msgid "" -"No problem. Once S/MIME has been enabled and the appropriate certificates " -"have been added, agents will be prompted to retry verification/decryption on " -"matching emails." +"With our Clearbit integration, you can easily enrich the information " +"provided by Zammad. If the customers or agents email address is known to " +"Clearbit, it will share all information it has regarding the user with " +"Zammad. Those information can include the following:" msgstr "" -"Нема проблема. Када се S/MIME укључи и додају одговарајући сертификати, " -"оператерима ће бити пружена опција да поново покушају верификују/дешифрују " -"одговарајуће поруке." +"Уз нашу Clearbit интеграцију, лако можете обогатити информације које пружа " +"Zammad. Ако је имејл адреса клијената или оператера позната Clearbit " +"сервису, он ће поделити све информације које има у вези са корисником са " +"Zammad-ом. Те информације могу укључивати следеће:" -#: ../system/integrations/smime/troubleshooting.rst:0 -msgid "Screenshot of user prompt to retry decryption" -msgstr "Снимак екрана корисничке функције за поновни покушај дешифровања" +#: ../system/integrations/clearbit.rst:9 +msgid "Avatar" +msgstr "Аватар" -#: ../system/integrations/smime/troubleshooting.rst:38 -msgid "The 🔒 **Encrypt** button is disabled" -msgstr "Дугме 🔒 **Шифровање** је онемогућено" +#: ../system/integrations/clearbit.rst:10 +msgid "Address information" +msgstr "Информације о адреси" -#: ../system/integrations/smime/troubleshooting.rst:33 -msgid "Have you added the recipient's certificate?" -msgstr "Да ли сте додали сертификат примаоца?" +#: ../system/integrations/clearbit.rst:11 +msgid "Website information" +msgstr "Информације о сајту" -#: ../system/integrations/smime/troubleshooting.rst:34 -msgid "Are you sure the recipient's certificate is valid?" -msgstr "Да ли сте сигурни да је сертификат примаоца важећи?" +#: ../system/integrations/clearbit.rst:12 +msgid "A BIO (as Note by default)" +msgstr "BIO (подразумевано као напомена)" -#: ../system/integrations/smime/troubleshooting.rst:35 -msgid "Have you checked your ``production.log`` for more details?" -msgstr "Да ли сте проверили своју ``production.log`` датотеку за више детаља?" +#: ../system/integrations/clearbit.rst:14 +msgid "" +"If needed, you can add further custom objects and add mappings to them, so " +"the Clearbit information can be filled within the database. In general you " +"can get any information from Clearbit, as long as you have a mapping to an " +"Zammad object." +msgstr "" +"Ако је потребно, можете додати додатне прилагођене објекте и додати им " +"мапирања, тако да се Clearbit информације могу снимити унутар базе података. " +"Генерално говорећи, можете добити било коју информацију од Clearbit-а, све " +"док имате мапирање на одговарајући Zammad објекат." -#: ../system/integrations/smime/troubleshooting.rst:37 +#: ../system/integrations/clearbit.rst:21 msgid "" -"If encryption doesn't work in the composer, it won't work in :doc:`triggers " -"` or the :doc:`scheduler ` either!" +"Clearbit does have a mapping of fields like LDAP and Exchange have, but does " +"not \"win\" against Zammad information. This means that if you have e.g. the " +"last name field filled in already and Clearbit has other information on " +"that, it will not be updated." msgstr "" -"Ако шифровање не функционише приликом слања, неће радити ни у :doc:" -"`окидачима ` и :doc:`планерима `!" +"Clearbit поседује мапирање поља као што то раде LDAP и Exchange, али не " +"\"побеђује\" у сукобу са Zammad подацима. То значи да ако имате нпр. поље за " +"презиме је већ попуњено и Clearbit има друге информације о томе, поље неће " +"бити освежено." -#: ../system/integrations/smime/troubleshooting.rst:42 -msgid "The ✅ **Sign** button is disabled" -msgstr "Дугме ✅ **Потписивање** је онемогућено" +#: ../system/integrations/clearbit.rst:26 +msgid "" +"However: If let's say the last name has been set by Clearbit and Zammad " +"notices that the last name on the Clearbit source has changed, Zammad will " +"also update this value." +msgstr "" +"Међутим: ако је рецимо презиме подесио Clearbit и Zammad примети да се " +"презиме на Clearbit-у променило, Zammad ће такође освежити своју вредност." -#: ../system/integrations/smime/troubleshooting.rst:41 +#: ../system/integrations/clearbit.rst:33 msgid "" -"Have you added **both the certificate and private key** for your " -"organization?" -msgstr "Да ли сте додали **и сертификат и тајни кључ** за своју организацију?" +"The configuration of Clearbit is really easy and done fast! Just login to " +"your Clearbit-Account, go to \"API\" and copy the secret-API-Key." +msgstr "" +"Подешавање Clearbit-а је заиста једноставно и брзо! Само се пријавите на " +"свој Clearbit налог, идите на „API” и копирајте тајни API кључ." -#: ../system/integrations/smime/troubleshooting.rst:42 +#: ../system/integrations/clearbit.rst:38 msgid "" -"Does the email address on the certificate match the email address of the " -"agent/group composing the email?" +"Now change to your Zammad instance, go to Integrations (System) -> Clearbit " +"in the admin panel. Paste your API-Key into the API-Key-Field and decide if " +"Zammad should create unknown Organizations automatically, if the user does " +"not have one yet (and Clearbit knows it). The shared option decides if the " +"new organizations Zammad creates with Clearbit should be shared ones." msgstr "" -"Да ли се имејл адреса сертификата подудара са имејл адресом оператера/групе " -"која саставља поруку?" +"Сада пређите на своју Zammad инстанцу, идите на Интеграције (Систем) -> " +"Clearbit у панелу администратора. Налепите свој API кључ у одговарајуће поље " +"и одлучите да ли Zammad треба аутоматски да додаје непознате организације, " +"ако их корисник још увек нема (а Clearbit зна за њих). Опција заједничке " +"организације одлучује да ли нове организације које Zammad додаје преко " +"Clearbit треба да буду дељене међу члановима исте организације." -#: ../system/integrations/smime/troubleshooting.rst:45 -msgid "Error: “Fingerprint already taken”" -msgstr "Грешка: „Fingerprint already taken“" +#: ../system/integrations/clearbit.rst:47 +msgid "" +"If you're unsure what option to choose, better stick with \"no\". You can " +"also learn more about :doc:`/manage/organizations/index`." +msgstr "" +"Ако нисте сигурни коју опцију да одаберете, боље се држите „не”. Такође " +"можете сазнати више о организацијама :doc:`овде `." -#: ../system/integrations/smime/troubleshooting.rst:45 -msgid "Are you sure you haven't added this certificate already?" -msgstr "Јесте ли сигурни да већ нисте додали овај сертификат?" +#: ../system/integrations/clearbit.rst:52 +msgid "" +"The Mapping option works similar to the mapping within the Exchange and LDAP " +"sync. You can add further mappings for e.g. custom fields if you need more " +"information that Clearbit can provide." +msgstr "" +"Опција мапирања функционише слично мапирању унутар Exchange и LDAP " +"синхронизације. Можете додати још мапирања за нпр. прилагођена поља ако вам " +"треба више информација које Clearbit може да пружи." -#: ../system/integrations/smime/troubleshooting.rst:48 -msgid "Error: “❌ invalid byte sequence in UTF-8”" -msgstr "Грешка: „❌ invalid byte sequence in UTF-8“" +#: ../system/integrations/clearbit.rst:58 +msgid "" +"If you want to add more Clearbit fields and want to learn more about " +"available fields on their API, you can take a look at their `API " +"documentation `_." +msgstr "" +"Ако желите да додате још Clearbit пољa и желите да сазнате више о доступним " +"пољима на њиховом API-ју, можете погледати и њихову `API документацију " +"`_." -#: ../system/integrations/smime/troubleshooting.rst:48 -msgid "Please ensure to provide PEM formatted certificate and keys." -msgstr "Обавезно обезбедите сертификат и кључеве у PEM формату." +#: ../system/integrations/clearbit.rst:62 +msgid "" +"If you're happy with the above chosen Settings and your mapping, just save " +"the changes and enable Clearbit integration. Zammad will now start polling " +"the Clearbit API as users contact you." +msgstr "" +"Ако сте задовољни са горе одабраним подешавањима и вашим мапирањем, само " +"сачувајте промене и укључите Clearbit интеграцију. Zammad ће сада почети да " +"испитује Clearbit API чим вас корисници контактирају." -#: ../system/integrations/smime/troubleshooting.rst:49 -msgid "Did you check if the provided file is a valid certificate or key?" +#: ../system/integrations/clearbit.rst:68 +msgid "" +"Zammad does not synchronize with Clearbit on a regular basis, but on demand " +"if needed. This saves API calls." msgstr "" -"Да ли сте проверили да ли дата датотека садржи важећи сертификат или кључ?" +"Zammad се не синхронизује са Clearbit-ом редовно, већ на захтев ако је " +"потребно. Ово понашање штеди у броју API позива." -#: ../system/integrations/zabbix.rst:2 -msgid "Zabbix Integration" -msgstr "Zabbix интеграција" +#: ../system/integrations/clearbit.rst:73 +msgid "" +"Below the Settings and Mappings, you'll find our Integration log. You can " +"see what requests Zammad sent to Clearbit and also the APIs Response." +msgstr "" +"Испод подешавања и мапирања, наћи ћете нашу евиденцију захтева. Можете " +"видети које је захтеве Zammad послао Clearbit-у, као и одговоре преко API-ја." -#: ../system/integrations/zabbix.rst:5 +#: ../system/integrations/clearbit.rst:78 msgid "" -"This guide describes how to integrate your Zabbix 5.4 installation with " -"Zammad using the Zabbix webhook feature. This guide will provide " -"instructions on setting up a media type, a user and an action in Zabbix." +"By the way, you can also view the API log on the Clearbit website - the " +"information seen is basically the same." msgstr "" -"Овај водич описује како да интегришете своју Zabbix 5.4 инсталацију са " -"Zammad-ом користећи Zabbix повратне позиве. Овај водич ће пружити упутства " -"за подешавање врсте медија, корисника и радње у Zabbix-у." - -#: ../system/integrations/zabbix.rst:12 -msgid "Zammad with enabled HTTP Token Authentication" -msgstr "Zammad са укљученом аутентификацијом путем HTTP кључа" +"Узгред, можете погледати и API евиденцију на Clearbit сајту - информације " +"које су доступне су у основи исте." -#: ../system/integrations/zabbix.rst:13 -msgid "Zabbix version 5.4 or higher" -msgstr "Zabbix верзија 5.4 или новија" +#: ../system/integrations/clearbit.rst:84 +msgid "Example When Adding a User" +msgstr "Пример приликом додавања корисника" -#: ../system/integrations/zabbix.rst:16 -msgid "Setting up a Zammad" -msgstr "Подешавање Zammad-а" +#: ../system/integrations/clearbit.rst:86 +msgid "" +"To show you how fast information is added, we added a small Screencast " +"below. This shows the creation of the User Alex from Clearbit. As we already " +"set the last name of Alex to \"X\", Zammad did not update it. What Zammad " +"did was to add further information it received from Clearbit." +msgstr "" +"Да бисмо вам показали колико брзо се приказују информације, додали смо мали " +"снимак екрана испод. Ово показује додавање корисника Alex путем Clearbit-а. " +"Пошто смо већ поставили презиме Alex на „X“, Zammad га није освежио. Оно што " +"је Zammad урадио је да је додао додатне информације које је добио од " +"Clearbit-а." -#: ../system/integrations/zabbix.rst:18 -msgid "Enable **API Token Access** in Settings > System > API." -msgstr "Омогућите **Приступ API путем кључа** у Подешавања > Систем > API." +#: ../system/integrations/cti/generic.rst:2 +msgid "CTI (generic)" +msgstr "CTI (генерички)" -#: ../system/integrations/zabbix.rst:20 +#: ../system/integrations/cti/includes/introduction.include.rst:1 msgid "" -"Create a **new user** for a Zabbix alerter with an **email address** and " -"create a personal user token with **ticket.agent** permissions." +"This integration enables Zammad to provide a caller log to your agents. With " +"this your agents can greet your customers by their name and are supported by " +"Zammad with automatically opening a new ticket dialog or the user profile." msgstr "" -"Направите **новог корисника** за Zabbix упозорења са **имејл адресом** и " -"додајте лични кључ за приступ са дозволом **ticket.agent**." - -#: ../system/integrations/zabbix.rst:24 -msgid "Zabbix Webhook Configuration" -msgstr "Конфигурација повратног позива за Zabbix" +"Ова интеграција омогућава Zammad-у да обезбеди евиденцију позива вашим " +"оператерима. Са њом ваши оператери могу поздравити ваше клијенте њиховим " +"именом, а Zammad им обезбеђује и аутоматски приказ дијалога новог тикета или " +"корисничког профила." -#: ../system/integrations/zabbix.rst:27 -msgid "Create a Global Macro" -msgstr "Направите глобални макро" +#: ../system/integrations/cti/includes/introduction.include.rst:6 +msgid "" +"Click the toggle next to the heading to activate or deactivate this " +"integration." +msgstr "" +"Кликните на дугме поред наслова да бисте укључили или искључили ову " +"интеграцију." -#: ../system/integrations/zabbix.rst:29 +#: ../system/integrations/cti/includes/introduction.include.rst:9 msgid "" -"Before setting up the **Webhook**, you need to setup the global macro " -"**{$ZABBIX.URL}**, which must contain the **URL** to the **Zabbix frontend**." +"If you want to learn more on how your agents can use this function, please " +"refer the :user-docs:`user documentation `." msgstr "" -"Пре него што подесите **Webhook**, морате да подесите глобални макро " -"**{$ZABBIX.URL}**, који мора да садржи **URL адресу** на **Zabbix кориснички " -"интерфејс**." +"Ако желите да сазнате више о томе како ваши оператери могу да користе ову " +"функцију, погледајте :user-docs:`корисничку документацију `." -#: ../system/integrations/zabbix.rst:33 +#: ../system/integrations/cti/includes/introduction.include.rst:14 msgid "" -"In the **Administration** > **Media types** section, import the `Template`_." -msgstr "У одељку **Administration** > **Media types** увезите `Template`_." +"Automatically opening new ticket dialogues or user profiles requires agent " +"to extension mapping - see more below." +msgstr "" +"За аутоматски приказ дијалога нових тикета или корисничких профила потребно " +"је мапирање оператера на локале – погледајте више у наставку." -#: ../system/integrations/zabbix.rst:38 -msgid "Open the added **Zammad** media type and set:" -msgstr "Отворите додату врсту медија **Zammad-** и подесите:" +#: ../system/integrations/cti/includes/introduction.include.rst:20 +msgid "Please note the following limitations to reduce confusion later on:" +msgstr "Имајте на уму следећа ограничења да бисте касније смањили забуну:" -#: ../system/integrations/zabbix.rst:40 -msgid "**zammad\\_access\\_token** to the your **Personal User Token**" -msgstr "**zammad\\_access\\_token** на ваш **лични кључ за приступ**" +#: ../system/integrations/cti/includes/introduction.include.rst:22 +msgid "CTI integrations provide caller log functions only." +msgstr "CTI интеграције пружају само функције евиденције позива." -#: ../system/integrations/zabbix.rst:41 +#: ../system/integrations/cti/includes/introduction.include.rst:23 msgid "" -"**zammad\\_url** to the **frontend URL** of your **Zammad** installation" +"This integration does not provide any VoIP functionalities; you can't make " +"phone calls from within Zammad." msgstr "" -"**zammad\\_url** на **URL адресу корисничког интерфејса** ваше инсталације " -"**Zammad-а**" - -#: ../system/integrations/zabbix.rst:43 -msgid "**zammad\\_customer** to your **Zammad user email**." -msgstr "**zammad\\_customer** на вашу **Zammad корисничку имејл адресу**." +"Ова интеграција не пружа никакве VoIP функционалности; не можете да " +"упућујете телефонске позиве из Zammad-а." -#: ../system/integrations/zabbix.rst:44 +#: ../system/integrations/cti/includes/introduction.include.rst:25 msgid "" -"**zammad\\_enable\\_tags** to **true** or **false** to enable or disable " -"trigger tags. **Important**: if you enable tag support, each tag is set with " -"a separate request." +"If your browser supports ``tel``-URLs, you can click on phone numbers for " +"automatic dialing. This requires additional software / configuration on your " +"agent's computers." msgstr "" -"**zammad\\_enable\\_tags** на **true** или **false** да бисте укључили или " -"искључили ознаке окидача. **Важно**: ако укључите подршку за ознаке, свака " -"ознака се поставља посебним захтевом." +"Ако ваш претраживач подржава ``tel`` URL адресе, можете кликнути на бројеве " +"телефона за аутоматско бирање. Ово захтева додатни софтвер/конфигурацију на " +"рачунарима вашег оператера." -#: ../system/integrations/zabbix.rst:48 +#: ../system/integrations/cti/generic.rst:9 +#: ../system/integrations/cti/placetel.rst:14 +#: ../system/integrations/cti/sipgate.rst:14 +msgid "Please provide the following requirements:" +msgstr "Наведите следеће услове:" + +#: ../system/integrations/cti/generic.rst:11 msgid "" -"If you want to prioritize issues according to **severity** values in Zabbix, " -"you can define mapping parameters:" +"A telephone system that supports webhooks (outbound) (best option are those " +"that allow customizing the calls)." msgstr "" -"Ако желите да дате приоритет проблемима према вредностима **severity** " -"атрибута у Zabbix-у, можете да дефинишете параметре мапирања:" +"Телефонска централа која подржава повратне позиве (одлазне) (најбоља опција " +"су оне који омогућавају прилагођавање позива)." -#: ../system/integrations/zabbix.rst:51 -msgid "**severity\\_**: Zammad priority ID" -msgstr "**severity\\_<назив>**: ID Zammad приоритета" +#: ../system/integrations/cti/generic.rst:13 +msgid "A unique Call-ID during the call session." +msgstr "Јединствени ID позива током сесије позива." -#: ../system/integrations/zabbix.rst:53 -msgid "Click the **Update** button to save the **Webhook** settings." -msgstr "Кликните на дугме **Update** да бисте сачували **Webhook** подешавања." +#: ../system/integrations/cti/generic.rst:14 +msgid "Call event data (both numbers and direction)." +msgstr "Подаци о догађају позива (и бројеви и правац)." -#: ../system/integrations/zabbix.rst:55 +#: ../system/integrations/cti/generic.rst:15 +msgid "Your Zammad instance must be reachable for your telephony system." +msgstr "Ваша Zammad инстанца мора бити доступна вашој телефонској централи." + +#: ../system/integrations/cti/generic.rst:17 msgid "" -"To receive notifications in **Zammad**, you need to create a **Zabbix user** " -"and add **Media** with the **Zammad** type." +"If you want to learn more on what kind of requests are supported by Zammad " +"and what it expects, please consult our :docs:`CTI-API documentation `." msgstr "" -"Да бисте примали обавештења у **Zammad-у**, потребно је да направите " -"**Zabbix корисника** и додате **Media** са типом **Zammad**." +"Ако желите да сазнате више о томе које врсте захтева Zammad подржава и шта " +"очекује, погледајте нашу :docs:`CTI-API документацију `." -#: ../system/integrations/zabbix.rst:58 +#: ../system/integrations/cti/generic.rst:22 +#: ../system/integrations/cti/placetel.rst:27 +#: ../system/integrations/cti/sipgate.rst:30 +msgid "Available Settings" +msgstr "Доступна подешавања" + +#: ../system/integrations/cti/generic.rst:29 +#: ../system/integrations/cti/placetel.rst:41 +#: ../system/integrations/cti/sipgate.rst:40 +msgid "Endpoint Settings" +msgstr "Подешавања путање" + +#: ../system/integrations/cti/generic.rst:25 msgid "" -"For **Send to**: enter any text, as this value is not used, but is required." +"Zammad will list your generic CTI endpoint here. It contains a unique token " +"so ensure to keep this URL save." msgstr "" -"За **Send to**: унесите било који текст, јер се ова вредност не користи, али " -"је обавезна." +"Zammad ће овде навести вашу генеричку CTI путању. Садржи јединствени кључ, " +"па се побрините да сачувате ову URL адресу." -#: ../system/integrations/zabbix.rst:61 +#: ../system/integrations/cti/generic.rst:28 msgid "" -"For more information, use the `Zabbix documentation `_." +"You'll need this endpoint for your PBX to talk to Zammad, see :docs:`CTI-API " +"documentation `." msgstr "" -"За више информација, погледајте `Zabbix документацију `_." - -#: ../system/maintenance.rst:2 -msgid "Maintenance" -msgstr "Одржавање" +"Ова путања је неопходна да би ваша PBX центеала комуницирала са Zammad-ом, " +"за детаље погледајте :docs:`CTI API документацију `." -#: ../system/maintenance.rst:4 +#: ../system/integrations/cti/includes/important-dont-forget-saving.include.rst:3 msgid "" -"Zammad comes with a maintenance mode that you can use for e.g. updating the " -"instance or changing settings while restricting availability and functions." +"All following options **do not save automatically**. Always use the Save " +"button on the lower end of the integration page!" msgstr "" -"Zammad долази са режимом одржавања који можете користити за нпр. ажурирање " -"инстанце или промену подешавања уз ограничавање доступности функција." - -#: ../system/maintenance.rst:13 -msgid "Mode" -msgstr "Режим" +"Све следеће опције се **не чувају аутоматски**. Увек користите дугме Сачувај " +"у доњем углу екрана за интеграцију!" -#: ../system/maintenance.rst:8 -msgid "The mode setting allows you to enable or disable the maintenance mode." -msgstr "" -"Подешавање режима вам омогућава да укључите или искључите режим одржавања." +#: ../system/integrations/cti/generic.rst:43 +#: ../system/integrations/cti/placetel.rst:49 +#: ../system/integrations/cti/sipgate.rst:52 +msgid "Call Settings" +msgstr "Подешавање позива" -#: ../system/maintenance.rst:10 -msgid "Defaults to *off*." -msgstr "Подразумевано је *искључено*." +#: ../system/integrations/cti/generic.rst:39 +#: ../system/integrations/cti/placetel.rst:49 +#: ../system/integrations/cti/sipgate.rst:37 +#: ../system/integrations/cti/sipgate.rst:50 +msgid "Inbound" +msgstr "Долазнo" -#: ../system/maintenance.rst:12 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:1 msgid "" -"The maintenance mode will restrict access to administrative roles only. This " -"means agents and customers are logged off." +"This option allows you to block specific incoming caller IDs. It allows you " +"to temporarily reject e.g. spam callers without having to contact providers " +"or PBX administrators." msgstr "" -"Режим одржавања ће ограничити приступ само улози администратора. То значи да " -"су оператери и клијенти одјављени." +"Ова опција вам омогућава да блокирате одређене долазне ID позиваоца. " +"Омогућава вам да привремено одбијете нпр. spam позиваоцe без потребе да " +"контактирате провајдере или PBX администратора." + +#: ../system/integrations/cti/includes/inbound-calls.include.rst:11 +msgid "Caller ID to block" +msgstr "ID позиваоца за блокирање" -#: ../system/maintenance.rst:23 -msgid "@Login" -msgstr "@Пријави се" +#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 +msgid "Provide caller IDs to block in ``E.164`` format." +msgstr "Наведите ID позиваоца за блокирање у ``Е.164`` формату." -#: ../system/maintenance.rst:16 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:8 msgid "" -"This setting allows you to provide a login message within a green banner " -"above the login screen. Click into the green banner in the settings page to " -"adjust your message. To activate the message, activate the *@Login* setting." +"Your telephony system has to support this function. Zammad will send a " +"``reject`` response which will cause your telephony system to hang up the " +"call. To callers this usually will feel like the line is busy." msgstr "" -"Ово подешавање вам омогућава да одредите пријавну поруку у оквиру зеленог " -"банера изнад екрана за пријаву. Кликните на зелени банер на страници са " -"подешавањима да бисте прилагодили своју поруку. Да бисте активирали поруку, " -"укључите подешавање *@Пријави се*." +"Ваша телефонска централа мора да подржава ову функцију. Zammad ће послати " +"``reject`` одговор који ће узроковати да ваша централа прекине позив. " +"Позиваоцима ово се обично манифестује као заузета линија." -#: ../system/maintenance.rst:0 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:14 msgid "" -"Screenshot showing the default login message within the\n" -"settings page" +"Provide a meaningful note for your fellow administrators to remind yourself " +"why you've chosen to block the number." msgstr "" -"Снимак екрана који приказује подразумевану пријавну поруку у оквиру\n" -"странице са подешавањима" +"Унесите смислену напомену за своје колеге администраторе да бисте се их " +"подсетили зашто сте изабрали да блокирате број." -#: ../system/maintenance.rst:26 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:17 +#: ../system/integrations/cti/sipgate.rst:40 +msgid "Outbound" +msgstr "Одлазнo" + +#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:1 msgid "" -"Send an informative message to **all active sessions**. This comes handy to " -"inform your agents e.g. about mayor outages or to force reloads after " -"configuration changes." +"In many cases you may want to use a different caller ID depending on the " +"destination you're calling. This may apply due to specific connection rates " +"to other countries or because you want your customer to feel you're calling " +"from the same country." msgstr "" -"Пошаљите информативну поруку **свим активним сесијама**. Ово је згодно да " -"обавестите своје оператере, нпр. о дужим прекидима рада или о обавезном " -"поновном учитавању апликације након измена конфигурације." +"У многим случајевима можда ћете желети да користите другачији ID позиваоца у " +"зависности од дестинације коју позивате. Ово се може применити због " +"специфичних стопа везе са другим земљама или зато што желите да ваш клијент " +"примети да зовете из исте земље." -#: ../system/maintenance.rst:31 -msgid "This is the messages title (slightly bigger than the normal message)." -msgstr "Ово је наслов поруке (мало већи фонт од остатка текста)." +#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:6 +msgid "This option expects ``E.164`` number formats." +msgstr "Ова опција очекује бројеве у ``Е.164`` формату." -#: ../system/maintenance.rst:34 -msgid "The text you want to provide to your logged in sessions." -msgstr "Текст који желите да пошаљете својим пријављеним сесијама." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 +msgid "Destination caller ID" +msgstr "Одредишни ID позиваоца" -#: ../system/maintenance.rst:39 -msgid "Reload application" -msgstr "Освежи апликацију" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:5 +msgid "The caller ID or number you're trying to call." +msgstr "ID позиваоца или број који покушавате да позовете." -#: ../system/maintenance.rst:37 -msgid "" -"Selecting this option will change the message acceptance button from *Close* " -"(with nothing happening) to *Continue session*, which forces the application " -"to reload." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:7 +msgid "You can use wildcards for e.g. country specific outbound numbers like:" msgstr "" -"Избор ове опције промениће дугме за прихватање поруке из *Затвори* (без " -"икакве функције) у *Настави сесију*, што приморава апликацију да се поново " -"учита." +"Можете користити џокер знакове за нпр. одлазне бројеве специфичне за земљу " +"као што су:" -#: ../system/maintenance.rst:43 -msgid "" -"If you have customers that are logged in to Zammad, they'll also be notified " -"if they're active in that moment." -msgstr "" -"Ако имате клијенте који су пријављени у Zammad, они ће такође бити " -"обавештени уколико су активни у том тренутку." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:9 +msgid "``49*`` for Germany" +msgstr "``49*`` за Немачку" -#: ../system/maintenance.rst:48 -msgid "Example without reload application" -msgstr "Пример без поновног учитавања апликације" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:10 +msgid "``4930*`` for Berlin / Germany landlines" +msgstr "``4930*`` за фиксне телефоне из Берлина, Немачка" -#: ../system/maintenance.rst:52 -msgid "" -"Message setting within Zammad's admin settings without ticket reload " -"application setting." -msgstr "" -"Подешавање поруке у оквиру Zammad-ових подешавања администратора без " -"поновног учитавања апликације." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 +msgid "``33*`` for France" +msgstr "``33*`` за Француску" -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing the send message settings without ticket\n" -"reload application set" -msgstr "" -"Снимак екрана који приказује подешавање слања поруке без\n" -"поновног учитавања апликације" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:15 +msgid "Set Outbound caller ID" +msgstr "Подеси одлазећи ID позиваоца" -#: ../system/maintenance.rst:61 ../system/maintenance.rst:85 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:14 msgid "" -"The modal all other active sessions will see upon pressing *Send to clients*." +"The outbound caller ID to set (the number your customer sees on his display) " +"in ``E.164`` number format." msgstr "" -"Дијалог ће све остале активне сесије видети чим притиснете *Пошаљи " -"клијентима*." +"Подешавањен одлазног ID позиваоца (број који ваш клијент види на свом " +"екрану) у ``Е.164`` формату." -#: ../system/maintenance.rst:0 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 +msgid "Provide a short description for fellow administrators." +msgstr "Унесите кратак опис за колеге администраторе." + +#: ../system/integrations/cti/includes/generic-cti-support-note.includes.rst:3 msgid "" -"Screenshot showing modal caused by maintenance's message\n" -"without reload application ticket" +"This option requires your PBX to send a specific request to Zammad *before " +"dialing*. Please consult the :docs:`CTI API ` in case " +"you're not sure." msgstr "" -"Снимак екрана који приказује дијалог изазван поруком одржавања\n" -"без поновног учитавања апликације" +"Ова опција захтева да ваша PBX централа пошаље посебан захтев Zammad-у *пре " +"бирања* броја. Молимо погледајте :docs:`CTI API документацију ` у случају да нисте сигурни." -#: ../system/maintenance.rst:72 -msgid "Example with reload application" -msgstr "Пример са поновним учитавањем апликације" +#: ../system/integrations/cti/generic.rst:52 +#: ../system/integrations/cti/placetel.rst:54 +#: ../system/integrations/cti/sipgate.rst:59 +msgid "Other Settings" +msgstr "Додатна подешавања" -#: ../system/maintenance.rst:76 +#: ../system/integrations/cti/includes/other-settings-intro.include.rst:1 msgid "" -"Message setting within Zammad's admin settings with ticket reload " -"application setting." +"Below you can find all available additional settings for this CTI " +"integration. For your overview we're sorting them by appearance and " +"reference their description first." msgstr "" -"Подешавање поруке у оквиру Zammad-ових подешавања администратора са поновним " -"учитавањем апликације." +"Испод можете пронаћи сва доступна додатна подешавања за ову CTI интеграцију. " +"Ради бољег прегледа сортирамо их по реду и прво указујемо на њихов опис." -#: ../system/maintenance.rst:0 +#: ../system/integrations/cti/includes/default-caller-id.include.rst:2 +#: ../system/integrations/cti/includes/default-caller-id.include.rst:1 +msgid "Default caller ID for outbound calls" +msgstr "Подразумевани ID позиваоца за одлазеће позиве" + +#: ../system/integrations/cti/includes/records-caller-log.include.rst:16 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:15 +msgid "Shown records in caller log" +msgstr "Приказани записи евиденције позива" + +#: ../system/integrations/cti/includes/records-caller-log.include.rst:2 msgid "" -"Screenshot showing the send message settings with ticket\n" -"reload application set" +"Allows you to set the number of shown caller log entries for all users. You " +"can choose from the following values:" msgstr "" -"Снимак екрана који приказује подешавање слања поруке са\n" -"поновним учитавањем апликације" +"Омогућава вам да подесите број приказаних записа у евиденцији позива за све " +"кориснике. Можете бирати између следећих вредности:" -#: ../system/maintenance.rst:0 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:5 +msgid "60 (default)" +msgstr "60 (подразумевано)" + +#: ../system/integrations/cti/includes/records-caller-log.include.rst:6 +msgid "120" +msgstr "120" + +#: ../system/integrations/cti/includes/records-caller-log.include.rst:7 +msgid "180" +msgstr "180" + +#: ../system/integrations/cti/includes/records-caller-log.include.rst:8 +msgid "240" +msgstr "240" + +#: ../system/integrations/cti/includes/records-caller-log.include.rst:9 +msgid "300" +msgstr "300" + +#: ../system/integrations/cti/includes/records-caller-log.include.rst:11 +msgid "**🥵 Potential performance issue**" +msgstr "**🥵 Потенцијални проблем са перформансама**" + +#: ../system/integrations/cti/includes/records-caller-log.include.rst:13 msgid "" -"Screenshot showing modal caused by maintenance's message\n" -"with reload application ticket" +"Setting this setting higher than 60 may cause serious performance issues on " +"very busy instances. Keep in mind that this setting causes Zammad to poll " +"and send up to 300 records to *all active agent sessions* in very short time " +"periods." msgstr "" -"Снимак екрана који приказује дијалог изазван поруком одржавања\n" -"са поновним учитавањем апликације" +"Подешавање ове поставке на више од 60 може изазвати озбиљне проблеме са " +"перформансама у веома заузетим системима. Имајте на уму да ово подешавање " +"доводи до тога да Zammad редовно шаље захтеве и доставља до 300 уноса *свим " +"активним сесијама оператера* у веома кратким временским интервалима." -#: ../system/monitoring.rst:2 -msgid "Monitoring" -msgstr "Надгледање" +#: ../system/integrations/cti/generic.rst:73 +msgid "Caller Log Filter" +msgstr "Филтер евиденције позива" -#: ../system/monitoring.rst:4 +#: ../system/integrations/cti/generic.rst:55 msgid "" -"This function is only available in self hosted instances. If you use Zammad " -"in our cloud, we are monitoring the system on our own and take steps to fix " -"potential problems directly." +"This function allows you to provide call information based on e.g. queues " +"only to agents that really need the information." msgstr "" -"Ова функција је доступна само у инстанцама које сами хостујете. Ако " -"користите Zammad у нашем окружењу, ми сами надгледамо систем и предузимамо " -"кораке да директно решимо потенцијалне проблеме." +"Ова функција вам омогућава да пружите информације о позиву на основу нпр. " +"редова само оператерима којима су информације заиста потребне." -#: ../system/monitoring.rst:11 +#: ../system/integrations/cti/generic.rst:58 msgid "" -"On the monitoring page, you can see the current health state of Zammad under " -"\"*Current Status*\" at the bottom. This can be useful if you want to have a " -"look if everything is up and running. As an example, you could have a look " -"in the monitoring when you assume that some emails aren't processed from " -"Zammad." +"Why? If you have a team for several countries or departments, you don't want " +"to bug your agents from other departments. Leaving these options empty will " +"fallback to showing everything to everyone." msgstr "" -"На страници за надгледање можете видети тренутно стање Zammad-а под " -"„*Тренутно стање*“ при дну. Ово може бити корисно ако желите да проверите да " -"ли је све у реду. Као пример, могли бисте да провериде у надгледању када " -"претпоставите да се неке имејл поруке не обрађују од стране Zammad-а." +"Зашто? Ако имате тим за неколико земаља или одељења, не желите да гњавите " +"своје оператере из других одељења. Ако ове опције оставите празне, вратићете " +"се на приказивање свега свима." -#: ../system/monitoring.rst:17 -msgid "**Can't receive an email and the monitoring response is \"healthy\"?**" -msgstr "" -"**Не можете да примите имејл поруке и стање надгледања је „без проблема“?**" +#: ../system/integrations/cti/generic.rst:64 +msgid "Destination caller ID or Queue" +msgstr "Одредишни ID позиваоца или ред" -#: ../system/monitoring.rst:19 +#: ../system/integrations/cti/generic.rst:63 msgid "" -"Zammad will just inform you about unprocessable emails. This is not the case " -"for oversized emails. You can adjust the maximum email size in :doc:`../" -"channels/email/settings`." +"This depends on your PBX and usually is either a queue ID, phone number or " +"extension." msgstr "" -"Zammad ће вас само обавестити о необрађеним имејл порукама. Ово није случај " -"са превеликим имејл порукама. Можете подесити максималну величину имејл " -"порука путем :doc:`../channels/email/settings`." +"Ово зависи од ваше PBX централе и обично је или ID реда, број телефона или " +"локал." -#: ../system/monitoring.rst:24 -msgid "Monitoring API" -msgstr "API надгледања" +#: ../system/integrations/cti/generic.rst:69 +msgid "Agents" +msgstr "Оператери" -#: ../system/monitoring.rst:26 +#: ../system/integrations/cti/generic.rst:67 msgid "" -"Beside the indication in the monitoring page, you can also use an external " -"monitoring tool to monitor Zammad's health. To request the health of Zammad, " -"you need to provide the API key (token) to the external monitoring tool. You " -"can copy the token from the \"*Current Token*\" field as well as the whole " -"API endpoint of your system (\"*Health Check*\" field), in which the API " -"token is already included." +"Select the agents that are responsible for the group. These agents will then " +"see caller log entries and call notifications fitting to said queue." msgstr "" -"Поред индикације на страници за надгледање, можете користити и спољни алат " -"за надгледање статуса Zammad-а. Да бисте надгледали Zammad, потребно је да " -"доставите API кључ (токен) спољном алату за надгледање. Можете копирати кључ " -"из поља „*Тренутни кључ*“, као и комплетну API путању вашег система (поље " -"„*Провера доступности*“), у коју је API кључ већ укључен." - -#: ../system/monitoring.rst:37 -msgid "Screenshot showing Current Token and Health Check" -msgstr "Снимак екрана који приказује тренутни кључ и проверу доступности" - -#: ../system/monitoring.rst:37 -msgid "Screenshot showing Token and Health Check" -msgstr "Снимак екрана који приказује кључ и проверу доступности" +"Изаберите оператере који су одговорни за групу. Ови оператери ће тада видети " +"записе евиденције позива и обавештења о позивима која се уклапају у наведени " +"ред." -#: ../system/monitoring.rst:39 +#: ../system/integrations/cti/generic.rst:0 msgid "" -"In addition to that, you can reset the auto-generated token to make sure " -"that already configured monitoring systems won't work anymore. So, please " -"use this \"*Reset*\" button only if you know what you do!" +"Screenshot showing the caller log filter table with pre filled sample data" msgstr "" -"Поред тога, можете ресетовати аутоматски генерисани кључ да бисте били " -"сигурни да већ конфигурисани системи за надгледање више неће радити. Дакле, " -"користите дугме „*Поништи*” само ако знате шта радите!" - -#: ../system/monitoring.rst:44 -msgid "Example Output" -msgstr "Пример резултата" +"Снимак екрана који приказује табелу филтера евиденције позиваоца са унапред " +"попуњеним примером" -#: ../system/monitoring.rst:0 -msgid "No issues found" -msgstr "Није пронађен ниједан проблем" +#: ../system/integrations/cti/includes/recent-logs.include.rst:6 +msgid "" +"With recent logs Zammad allows you to view the latest calls for the CTI " +"functionality. This usually comes in handy, when you're looking for errors." +msgstr "" +"Са недавним евиденцијама Zammad вам омогућава да видите најновије позиве за " +"CTI функцију. Ово обично добро дође када исправљате грешке." -#: ../system/monitoring.rst:48 ../system/monitoring.rst:60 -msgid "**Indicator in Zammad**:" -msgstr "**Индикатор у Zammad-у**:" +#: ../system/integrations/cti/includes/recent-logs.include.rst:0 +msgid "" +"Screenshot showing several incoming requests within Recent logs section." +msgstr "" +"Снимак екрана који приказује неколико долазних позива у одељку Недавни уноси " +"евиденције." -#: ../system/monitoring.rst:0 -msgid "Screenshot showing monitoring with no issues" -msgstr "Снимак екрана који приказује преглед надгледања без проблема" +#: ../system/integrations/cti/includes/recent-logs.include.rst:16 +msgid "I'm just here to clear floats up." +msgstr "Овде сам само да помогнем." -#: ../system/monitoring.rst:54 ../system/monitoring.rst:66 -msgid "**API response**::" -msgstr "**API одговор**::" +#: ../system/integrations/cti/includes/recent-logs.include.rst:20 +msgid "" +"By clicking on the entry of interest, Zammad will provide more details on " +"the call in question. You'll see the payload it received and also the " +"response that was sent." +msgstr "" +"Кликом на одговарајући унос, Zammad ће дати више детаља о позиву у питању. " +"Видећете податке који су примљени, као и одговор који је послат." -#: ../system/monitoring.rst:0 -msgid "Issues were found" -msgstr "Проблеми су пронађени" +#: ../system/integrations/cti/includes/recent-logs.include.rst:0 +msgid "" +"Screenshot showing detailed information of a specific log entry of recent " +"logs" +msgstr "" +"Снимак екрана који приказује детаљне информације о одређеном уносу евиденције" -#: ../system/monitoring.rst:0 -msgid "Screenshot showing monitoring with issues" -msgstr "Снимак екрана који приказује преглед надгледања са проблемима" +#: ../system/integrations/cti/includes/recent-logs.include.rst:31 +msgid "x" +msgstr "x" -#: ../system/objects.rst:2 -msgid "Objects" -msgstr "Објекти" +#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 +#: ../system/integrations/cti/includes/troubleshooting.include.rst:9 +msgid "My Phone page stays blank, signalling does work..." +msgstr "Преглед позива је празан, сигнализација ради..." -#: ../system/objects.rst:4 +#: ../system/integrations/cti/includes/troubleshooting.include.rst:5 msgid "" -"In Zammad you can add your own fields to tickets, users, organizations and " -"even groups (these are called \"objects\"). This can be useful if you need " -"to add further information to a ticket or any other object in Zammad and the " -"information doesn't fit in any existing field." +"If you've made sure that signalling works (check Recent logs) and your " +"Caller Log still stays empty, please ensure that you only configured one CTI " +"integration version. Specifically defining more than one agent mapping on " +"the different integration variants will be the issue." msgstr "" -"У Zammad-у можете додати сопствена поља тикетима, корисницима, " -"организацијама, па чак и групама (тзв. „објектима”). Ово може бити корисно " -"ако тикету треба да додате додатне информације које не припадају ни једном " -"постојећем пољу." +"Ако сте се уверили да сигнализација функционише (проверите Недавне уносе " +"евиденције) и да ваша евиденција позива и даље остаје празна, проверите да " +"ли сте подесили само једну верзију CTI интеграције. Дефинисање више од " +"једног оператера на различите варијанте интеграције може представљати " +"проблем." -#: ../system/objects.rst:11 -msgid "" -"Try to avoid deleting attributes (and disable them instead) as Zammad might " -"run into unexpected conditions if they are referenced somewhere." +#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 +msgid "Clear the not needed agent mapping and reload your browser page." msgstr "" -"Покушајте да избегнете брисање атрибута (и уместо тога их само искључите) " -"јер Zammad може наићи на неочекиване услове ако се поља још увек помињу " -"негде." +"Обришите мапирање оператера који вам није потребан и поново учитајте " +"страницу претраживача." -#: ../system/objects.rst:16 +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:1 msgid "" -"Here's an overview of object attributes. On the upper right you can add new " -"attributes. By default, there will be no custom fields - standard attributes " -"will be grayed out, you can't delete or change those. You can edit custom " -"attributes (they are displayed in black font and have a trash bin on the " -"right side) just by clicking on them." +"By mapping your agents extension to their existing Zammad users, Zammad can " +"provide a new ticket dialog or open the user profile for the agent that " +"picks up the call." msgstr "" -"Ево прегледа атрибута. У горњем десном углу можете додати нове атрибуте. " -"Подразумевано, нема прилагођених поља – стандардни атрибути ће бити " -"засивљени, не можете их избрисати или изменити. Кликом на прилагођене " -"атрибуте (биће приказани регуларном бојом и имаће иконицу канте за отпатке " -"са десне стране) можете их уредити." +"Мапирањем локала ваших оператера на њихове постојеће Zammad кориснике, " +"Zammad може да обезбеди дијалог новог тикета или да отвори кориснички профил " +"за оператера који преузима позив." -#: ../system/objects.rst:24 +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:5 msgid "" -"Attributes you add to Zammad, no matter if they have default values or not, " -"will not update existing information. This means a new ticket field " -"technically will be empty unless you populate it." +"This speeds up ticket aiding, no matter if it's for existing tickets or new " +"ones!" msgstr "" -"Атрибути које додате у Zammad, без обзира да ли имају подразумеване " -"вредности или не, неће утицати на постојеће информације. То значи да ће ново " -"поље за тикет технички бити празно све док га не попуните." +"Ово убрзава обраду тикета, без обзира да ли се ради о постојећим или новим " +"тикетима!" -#: ../system/objects.rst:28 +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:8 msgid "" -"Especially in ticket scope this also means that newly added attributes will " -"be indicated as \"changed\" to agents that view the ticket. This may " -"interfere with Zammad's tabs behavior." +"To see it work from the agent's perspective, have a look on :user-docs:`user " +"documentation `." msgstr "" -"Посебно у оквиру тикета, ово такође значи да ће новододати атрибути бити " -"означени као „измењени“ оператерима који прегледају тикет. Ово може да омета " -"понашање језичака у Zammad-у." +"Да бисте видели како функционише из перспективе оператера, погледајте :user-" +"docs:`корисничку документацију `." -#: ../system/objects.rst:40 -msgid "Ordering Attributes" -msgstr "Промена редоследа атрибута" +#: ../system/integrations/cti/placetel.rst:2 +msgid "Placetel CTI" +msgstr "Placetel CTI" -#: ../system/objects.rst:42 +#: ../system/integrations/cti/placetel.rst:16 +msgid "You need an administrative Placetel account for your organization." +msgstr "Потребан вам је администраторски Placetel налог за вашу организацију." + +#: ../system/integrations/cti/placetel.rst:17 +#: ../system/integrations/cti/sipgate.rst:20 msgid "" -"Since Zammad introduced :doc:`/system/core-workflows` the need to have a " -"custom positioning for attributes has become more important than ever." +"Your Zammad instance must be allowed to communicate to external services." msgstr "" -"Откако је Zammad увео :doc:`радне токове `, потреба " -"за прилагођеним редоследом атрибута постала је важнија него икад." +"Вашој Zammad инстанци мора бити дозвољено да комуницира са удаљеним " +"сервисима." -#: ../system/objects.rst:45 +#: ../system/integrations/cti/placetel.rst:18 +msgid "Placetel must be able to reach your Zammad instance." +msgstr "Placetel мора бити у могућности да приступи вашој Zammad инстанци." + +#: ../system/integrations/cti/placetel.rst:22 +msgid ":doc:`provider-configurations/placetel`" +msgstr ":doc:`provider-configurations/placetel`" + +#: ../system/integrations/cti/placetel.rst:21 msgid "" -"To adjust the position of such an attribute, simply click on the attribute " -"entry in question, scroll down and adjust the position number. Please note " -"that you cannot change the positioning of default attributes." +"Learn how to configure Placetel to enable Zammad and Placetel to communicate " +"with each other." msgstr "" -"Да бисте подесили положај оваквог атрибута, једноставно кликните на њега, " -"скролујте на доле и подесите поље положаја. Обратите пажњу да не можете " -"променити положај подразумеваних атрибута." +"Научите како да подесите Placetel да бисте омогућили Zammad-у и Placetel-у " +"да међусобно комуницирају." -#: ../system/objects.rst:49 +#: ../system/integrations/cti/placetel.rst:32 msgid "" -"In case two attributes have the same position value, Zammad will sort " -"alphabetically by name automatically." +"The here listed endpoint settings are relevant for the :doc:`integration " +"configuration with Placetel `." msgstr "" -"У случају да два атрибута имају исту вредност положаја, Zammad ће их " -"аутоматски сортирати по абецедном реду по називу." +"Овде наведена подешавања путање су релевантна за :doc:`подешавање Placetel " +"интеграције `." + +#: ../system/integrations/cti/placetel.rst:37 +#: ../system/integrations/i-doit.rst:53 +msgid "Endpoint" +msgstr "Путања" + +#: ../system/integrations/cti/placetel.rst:36 +msgid "" +"This endpoint will be required for the Zammad integration within the " +"Placetel web interface." +msgstr "" +"Ова путања ће бити потребна за Zammad интеграцију у Placetel корисничком " +"интерфејсу." -#: ../system/objects.rst:None +#: ../system/integrations/cti/placetel.rst:41 +msgid "API Token" +msgstr "API кључ" + +#: ../system/integrations/cti/placetel.rst:40 msgid "" -"Screenshot showing custom attribute entries ordered in between default ones" +"You'll receive this token within the ``Web API`` menu. Make sure to copy " +"this value, it's only shown once!" msgstr "" -"Снимак екрана који приказује уносе прилагођених атрибута са положајем између " -"подразумеваних атрибута" +"Добићете овај кључ у оквиру менија ``Web API``. Обавезно копирајте ову " +"вредност, она се приказује само једном!" -#: ../system/objects.rst:56 -msgid "Updating Database After Adding or Editing Attributes" -msgstr "Освежавање базе података након додавања или уређивања атрибута" +#: ../system/integrations/cti/placetel.rst:71 +#: ../system/integrations/cti/sipgate.rst:77 +msgid "Phone Extension to Agent Mapping" +msgstr "Мапирање локала на оператере" -#: ../system/objects.rst:58 -msgid "" -"When adding or changing attributes, Zammad will not apply the changes " -"instantly, but instead shows you the changed attributes first. If you're " -"ready to go, just click on \"Update database\" to apply the changes to " -"Zammad. If you made a mistake or just want to discard your changes, click " -"\"Discard changes\"." +#: ../system/integrations/cti/placetel.rst:0 +msgid "Screenshot showing sample user mappings in between Placetel and Zammad" msgstr "" -"Када додајете или мењате атрибуте, Zammad неће одмах применити измене, већ " -"вам прво показује измењене атрибуте. Ако сте спремни да наставите, само " -"кликните на „Освежи базу података“ да бисте применили промене. Ако сте " -"погрешили или само желите да одбаците промене, кликните на „Откажи промене“." +"Снимак екрана који приказује примере мапирања корисника између Placetel-а и " +"Zammad-а" -#: ../system/objects.rst:64 +#: ../system/integrations/cti/placetel.rst:64 msgid "" -"After applying the changes with \"Update Database\", a restart of Zammad is " -"**mandatory**. If you don't perform it, you may experience unexpected " -"behavior or even errors. You may want to do this kind of configuration " -"during maintenance windows." +"You can find your agents Placetel username combination required within ⚙️ PBX " +"→ VoIP destinations. Within the \"Advanced settings\" section you're looking " +"for \"SIP user name\" and \"SIP server\"." msgstr "" -"Након примене измена путем „Освежи базу података“, поновно покретање Zammad-" -"ових сервиса је **обавезно**. Ако то не урадите, можете доћи у неочекивану " -"ситуацију или чак узроковати грешке. Можда ћете желети да одрадите оваква " -"подешавања током режима одржавања." +"Неопходну комбинацију корисничког имена за своје оператере можете пронаћи у " +"оквиру ⚙️ PBX → VoIP destinations. У одељку „Advanced settings“ тражите „SIP " +"user name“ и „SIP server“." -#: ../system/objects.rst:72 -msgid "" -"Changes on objects require you to update the database to apply these changes." +#: ../system/integrations/cti/placetel.rst:68 +msgid "Combine these two like so: ``@``." msgstr "" -"Измене на објектима захтевају да освежите базу података да бисте применили " -"ове измене." +"Комбинујте ово две вредности на следећи начин: ``@``." -#: ../system/objects.rst:75 -msgid "**🤓 Service restarts can be automated**" -msgstr "**🤓 Поновно покретање сервиса се може аутоматизовати**" +#: ../system/integrations/cti/placetel.rst:0 +msgid "Sample VoIP credentials for a Placetel user" +msgstr "Пример VoIP креденцијала за Placetel корисника" -#: ../system/objects.rst:0 -msgid "Hosted environments automatically restart for you." -msgstr "Хостована окружења се аутоматски рестартују за вас." +#: ../system/integrations/cti/provider-configurations/placetel.rst:2 +msgid "Setup Placetel connection for Zammad" +msgstr "Подесите Placetel везу за Zammad" -#: ../system/objects.rst:0 +#: ../system/integrations/cti/provider-configurations/placetel.rst:6 msgid "" -"If you're using a self-hosted installation you can use :docs:`environment " -"variables `" +"This configuration step requires a *full* administrative Placetel account. " +"You may receive forbidden error messages with Placetel in case your " +"permissions are not high enough." msgstr "" -"Ако користите инсталацију коју сами хостујете, можете користити :docs:" -"`променљиве окружења `." - -#: ../system/objects.rst:82 -msgid "System Attributes" -msgstr "Системски атрибути" +"Овај корак подешавања захтева администраторски Placetel налог *пуног " +"приступа*. Могуће је да ћете добити поруке о грешкама забране од Placetel-а " +"у случају да ваше дозволе нису довољно високе." -#: ../system/objects.rst:84 +#: ../system/integrations/cti/provider-configurations/placetel.rst:10 msgid "" -"Zammad comes with pre-configured attributes. Some of them can't be edited " -"via UI (or at all). This is required for proper operation of Zammad and not " -"a bug." +"The following actions can be configured via the `Placetel web interface " +"`_." msgstr "" -"Zammad долази са унапред конфигурисаним атрибутима. Неки од њих тренутно не " -"пружају могућност уређивања путем корисничког интерфејса (или уопште). Ови " -"атрибути су обавезни за исправно функционисање Zammad-а и није у питању " -"грешка." +"Следеће радње се могу подесити преко `Placetel корисничког интерфејса " +"`_." -#: ../system/objects.rst:90 -msgid "Ticket State" -msgstr "Стање тикета" +#: ../system/integrations/cti/provider-configurations/placetel.rst:29 +msgid "Step 1: Activate Zammad integration" +msgstr "Корак 1: Активирајте Zammad интеграцију" -#: ../system/objects.rst:92 +#: ../system/integrations/cti/provider-configurations/placetel.rst:14 msgid "" -"If the pre-configured states aren't enough for you or you want to change " -"them, you can do so by clicking on the cogwheel icon in the state row in the " -"ticket tab. But you should be careful when changing pre-configured states. " -"This can lead to unwanted behavior in some cases." +"Within Integrations, scroll down to Partner integrations and select Zammad." msgstr "" -"Уколико вам предефинисана стања нису довољна или желите да их измените, то " -"можете урадити кликом на иконицу зупчаника у реду са атрибутом стања у " -"језичку тикета. Али будите пажљиви кад мењате предефинисана стања. У неким " -"случајевима ово може довести до нежељеног понашања." - -#: ../system/objects.rst:None -msgid "Screenshot showing highlighted ticket state attribute" -msgstr "Снимак екрана који приказује наглашен атрибут стања тикета" - -#: ../system/objects.rst:122 -msgid "Handling of states" -msgstr "Руковање стањима" +"У оквиру Integrations, скролујте надоле до Partner integrations и изаберите " +"Zammad." -#: ../system/objects.rst:102 +#: ../system/integrations/cti/provider-configurations/placetel.rst:17 msgid "" -"In the state configuration screen, you can add new states, disable states or " -"change states." +"You can alternatively filter by \"Ticket Systems\" to reduce the number of " +"entries on the page. You'll still want to look for Partner integrations. 🤓" msgstr "" -"У екрану подешавања стања можете додати нова стања, искључити постојећа или " -"их изменити." - -#: ../system/objects.rst:0 -msgid "Screenshot showing table of default ticket states" -msgstr "Снимак екрана који приказује табелу подразумеваних стања тикета" +"Алтернативно, можете филтрирати према „Ticket Systems“ да бисте смањили број " +"уноса на страници. И даље ћете желети да потражите Partner integrations. 🤓" -#: ../system/objects.rst:110 +#: ../system/integrations/cti/provider-configurations/placetel.rst:21 msgid "" -"To add a new state, click on the \"New Ticket State\" button in the top " -"right corner. To change an existing state, simply click on the affected " -"state. This opens an edit dialog." +"Within the Zammad integration now press \"Activate\". A new tab ``API`` " +"becomes available - open this tab." msgstr "" -"Да бисте додали стање, кликните на дугме „Ново стање тикета” у горњем десном " -"углу. За измену постојећег стања, једноставно кликните на дотично стање. Ово " -"ће отворити дијалог за уређивање." +"У оквиру Zammad интеграције сада притисните „Activate“. Нов језичак ``API`` " +"постаје доступан - отворите га." -#: ../system/objects.rst:114 +#: ../system/integrations/cti/provider-configurations/placetel.rst:24 msgid "" -"You can also clone a state or set them to \"Default for new tickets\" or " -"\"Default for follow-ups\" by clicking on the ⁝ action button and select the " -"desired function." +"Now tick \"Enable Call Control / Notify API\" and paste the Placetel " +"endpoint from your Zammad instance into the field \"URL of your API " +"endpoint\". Save to apply the settings" msgstr "" -"Такође можете клонирати стање или га поставити на „подразумевано за нове " -"тикете” или „подразумевано за наставке” кликом на ⁝ дугме радњи и одабиром " -"жељене функције." +"Сада означите „Enable Call Control / Notify API“ и налепите Placetel путању " +"из ваше Zammad инстанце у поље „URL of your API endpoint“. Сачувајте да " +"бисте применили подешавања." -#: ../system/objects.rst:118 +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "Screencast showing how to activate the Zammad integration" +msgstr "Снимак екрана који показује како да укључите Zammad интеграцију" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:51 +msgid "Step 2: Generate API Token for Placetel" +msgstr "Корак 2: Генеришите API кључ за Placetel" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:32 msgid "" -"*Default for new tickets* means that this state is used for every newly " -"created ticket." +"Go back to the integrations page and scroll down to \"Web API\". Generate a " +"new API token by using the \"Create a new API token\" button." msgstr "" -"*Подразумевано за нове тикете* значи да ће ово стање бити коришћено за све " -"новоотворене тикете." +"Вратите се на страницу интеграције и померите се надоле до „Web API“. " +"Генеришите нови API кључ помоћу дугмета „Create a new API token“." -#: ../system/objects.rst:121 +#: ../system/integrations/cti/provider-configurations/placetel.rst:37 msgid "" -"*Default for follow-ups* means that this state is used if the ticket is re-" -"opened after it was closed." +"If you already generated a token either use your existing token or reset it " +"by using above mentioned button. Placetel will ask you to conform this reset." msgstr "" -"*Подразумевано за наставке* значи да ће ово стање бити коришћено уколико се " -"тикет поново отвори након што је био затворен." +"Ако сте већ генерисали кључ или користите свој постојећи кључ или га " +"ресетујте користећи горе поменуто дугме. Placetel ће од вас тражити да " +"потврдите ово ресетовање." -#: ../system/objects.rst:171 -msgid "Ticket state in detail" -msgstr "Детаљније о стању тикета" +#: ../system/integrations/cti/provider-configurations/placetel.rst:41 +msgid "" +"Please keep in mind that existing API scripts may no longer work due to " +"token resets!" +msgstr "" +"Имајте на уму да постојеће API скрипте можда више неће радити због " +"ресетовања кључа!" -#: ../system/objects.rst:125 +#: ../system/integrations/cti/provider-configurations/placetel.rst:44 msgid "" -"Below you can find a description for each field and option. Please head over " -"to the :ref:`example ` to see the edit dialog." +"Copy the provided API token and insert it into the \"API Token\" field " +"within Zammad's Placetel integration." msgstr "" -"Испод можете пронаћи опис сваког поља и опције. Идите на :ref:`пример " -"` да бисте видели како изгледа дијалог за уређивање." +"Копирајте наведени API кључ и налепите га у поље „API кључ“ у оквиру Zammad-" +"ове Placetel интеграције." -#: ../system/objects.rst:129 +#: ../system/integrations/cti/provider-configurations/placetel.rst:47 msgid "" -"This is the name of the state and what you and your agents are seeing when " -"choosing a state somewhere (e.g. in tickets, trigger configuration)." +"Apply your changes by using the \"Save\" button on the bottom of the " +"Placetel integration page and activate the Placetel integration." msgstr "" -"Ово је назив стања и шта ви и ваши оператери видите када негде бирате стање " -"(нпр. у тикетима, подешавању окидача)." +"Примените своје промене помоћу дугмета „Сачувај“ при дну странице и укључите " +"Placetel интеграцију." -#: ../system/objects.rst:137 +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 msgid "" -"There are different state types you can choose from. By default, Zammad " -"comes with one state per state type." +"Screencast showing how to retrieve an API token from Placetel for Zammad" msgstr "" -"Има више различитих типова стања које можете одабрати. Подразумевано, Zammad " -"долази са једним стањем по сваком типу стања." +"Снимак екрана који показује како да преузмете API кључ са Placetel-а за " +"Zammad" -#: ../system/objects.rst:140 +#: ../system/integrations/cti/provider-configurations/placetel.rst:73 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:77 +msgid "Step 3: Restrict the numbers to notify on" +msgstr "Корак 3: Ограничите бројеве за обавештавање" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:54 msgid "" -"**new**: for states for tickets that are new and it hasn't been worked on " -"them" -msgstr "**ново**: за стања тикета који су нови и који још увек нису обрађени" +"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " +"the the Integrations page of the Placetel web interface, go to \"Notify " +"API\"." +msgstr "" +"Имате много бројева које не би требало користити за обавештавање Zammad-а? " +"На страници Integrations корисничког интерфејса Placetel-а идите на „Notify " +"API“." -#: ../system/objects.rst:142 +#: ../system/integrations/cti/provider-configurations/placetel.rst:58 msgid "" -"**open**: for states for tickets that are in progress and agents are working " -"on them" +"Lower on the page Placetel allows you to restrict the numbers to notify on. " +"You'll find this within the \"External routing API\" part." msgstr "" -"**отворено**: за стања тикета који су у процесу и оператери раде на њима" - -#: ../system/objects.rst:144 -msgid "**merged**: for states for tickets that are merged with other tickets" -msgstr "**спојено**: за стања тикета који су спојени са другим тикетима" +"При дну на странице Placetel вам омогућава да ограничите бројеве за " +"обавештавање. Ово ћете пронаћи у делу „External routing API“." -#: ../system/objects.rst:145 +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 msgid "" -"**pending reminder**: for states for tickets that are in progress and you " -"want to set a reminder. (default example: *pending reminder*)" +"Screenshot showing a sample selection of phone numbers to use for the " +"Placetels notify API" msgstr "" -"**чека на подсетник**: за стања тикета који су у процесу и за које желите да " -"поставите подсетник. (подразумевани пример: *чека на подсетник*)" +"Снимак екрана који приказује пример избора телефонских бројева који ће се " +"користити за Placetel notify API" -#: ../system/objects.rst:147 +#: ../system/integrations/cti/provider-configurations/placetel.rst:66 msgid "" -"**pending action**: for states for tickets that are waiting for a specified " -"time and then change their state (default example: *pending close*)" +"This menu point also provides a API request log from Placetel view. Just " +"open \"Recent responses of your API endpoint\" to learn more." msgstr "" -"**радња на чекању**: за стања тикета који чекају на одређено време и тада " -"мењају своје стање (подразумевани пример: *чека на затварање*)" +"Ова ставка менија такође пружа евиденцију API захтева из Placatel " +"перспективе. Отворите „Recent responses of your API endpoint“ да бисте " +"сазнали више." -#: ../system/objects.rst:150 +#: ../system/integrations/cti/provider-configurations/placetel.rst:69 msgid "" -"**closed**: for states for tickets that are finished and do not need to be " -"processed further" +"If you want to see Zammad's perspective, use the \"Recent Logs\" part from " +"within the Placetel integration page." msgstr "" -"**затворено**: за стања тикета који су обрађени и које више није неопходно " -"процесуирати" +"Ако желите да видите Zammad-ову перспективу, користите део „Недавни уноси " +"евиденције“ на страници за Placetel интеграцију." -#: ../system/objects.rst:153 -msgid "" -"⚠️ Choosing the correct state type is important! If you are in doubt, have a " -"look on the default states and their types!" +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "Screenshot showing sample log entries for Placetels API calls to Zammad" msgstr "" -"⚠️ Важно је одабрати исправан тип стања! Ако сумњате у свој избор, погледајте " -"подразумевана стања и њихове типове!" +"Снимак екрана који приказује уносе евиденција за Placetel API позиве за " +"Zammad" -#: ../system/objects.rst:158 -msgid "Ignore escalation" -msgstr "Игнориши ескалације" +#: ../system/integrations/cti/provider-configurations/placetel.rst:77 +msgid "Step 4 (optional): Further configurations for Placetel" +msgstr "Корак 4 (опционо): Даља подешавања за Placetel" -#: ../system/objects.rst:157 +#: ../system/integrations/cti/provider-configurations/placetel.rst:76 msgid "" -"Here you can define whether tickets of this state will count to escalation " -"time or not." +"If needed, you can now configure Zammad's Placetel integration in more " +"detail. You can learn more about your options here: :ref:`Placetel " +"integration settings `." msgstr "" -"Овде можете одредити да ли ће се тикети у овом стању рачунати за време " -"ескалације." +"Ако је потребно, сада можете детаљније да подесите Zammad-ову Placetel " +"интеграцију. Можете сазнати више о опцијама у :ref:`подешавању Placetel " +"интеграције `." -#: ../system/objects.rst:161 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:2 +msgid "Setup Sipgate connection for Zammad" +msgstr "Повежите Sipgate за Zammad–ом" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"You can create a note for the state to inform other admins about the state. " -"This has no effect on tickets." +"Sipgate has no english web interface which is why this documentation page is " +"mixing up languages badly." msgstr "" -"Можете додати напомену за стање да бисте обавестили друге администраторе о " -"овом стању. Ово нема ефекта на тикете." - -#: ../system/objects.rst:165 -msgid "Set the state to *active* or *inactive*." -msgstr "Поставите стање на *укључено* или *искључено*." +"Sipgate нема кориснички интерфејс на енглеском језику због чега ова страница " +"лоше меша језике." -#: ../system/objects.rst:167 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"it is technically possible to set all states to inactive. To keep Zammad " -"working in such a case, the inactive flag of one of the states is ignored." +"Please also note that the availability of API addons highly depends on your " +"package trier. Usage of sipgate.io packages *is not free*, please check " +"their `pricing page `_ before!" msgstr "" -"Технички је могуће искључити сва стања. Да бисте обезбедили да Zammad " -"настави да функционише, једно од искључених стања ће бити аутоматски " -"активирано." +"Такође имајте на уму да доступност API додатака у великој мери зависи од " +"вашег пакета услуга. Коришћење sipgate.io пакета *није бесплатно*, молимо " +"проверите њихову `страницу са ценама `_ пре " +"него што наставите!" -#: ../system/objects.rst:194 -msgid "Ticket state example" -msgstr "Пример стања тикета" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:35 +msgid "Step 1: Book sipgate.io package" +msgstr "Корак 1: Купите sipgate.io пакет" -#: ../system/objects.rst:174 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:13 +msgid "Skip to step 2 if you already have the package booked!" +msgstr "Пређите на корак 2 ако већ имате купљен пакет!" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:15 msgid "" -"Let's assume we want to create a new state which indicates that the ticket " -"has to wait for a response of a third party (e.g. service contractor or " -"manufacturer) and we want to to be able to set a reminder." +"Login to an administrative Sipgate account and navigate to " +"``Accountverwaltung``. You'll see several different options depending on " +"your booked packages. Select ``Verträge & Produkte`` to continue." msgstr "" -"Хајде да претпоставимо да желимо да додамо ново стање који означава да тикет " -"чека на одговор трећег лица (нпр. подизвођача или произвођача) и желимо да " -"поставимо подсетник." +"Пријавите се на администраторски Sipgate налог и идите на " +"``Accountverwaltung``. Видећете неколико различитих опција у зависности од " +"купљног пакета. Изаберите ``Verträge & Produkte`` да бисте наставили." -#: ../system/objects.rst:178 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:19 msgid "" -"First we give the new state a proper name. In this example we call it " -"\"waiting for manufacturer\"." +"Scroll down to the section ``Zusätzliche Produkte buchen`` and look for " +"``sipgate.io`` - select this product by using the ``Produkte anzeigen``-" +"Button." msgstr "" -"Прво дајемо назив новом стању. У овом примеру називамо га „чека на " -"произвођача”." +"Скролујте надоле до одељка ``Zusätzliche Produkte buchen`` и потражите " +"``sipgate.io`` - изаберите овај производ помоћу дугмета ``Produkte " +"anzeigen``." -#: ../system/objects.rst:181 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:23 msgid "" -"As state type we choose \"pending reminder\". This indicates that the ticket " -"is still open and we can set a reminder. This reminder can be useful if our " -"manufacturer sometimes isn't responding or we want to remind him to give us " -"an answer." +"On the next page select either one of the ``sipgate.io`` packages or ``Push-" +"API Package Free``. Follow the dialogue by booking the addon. You'll be " +"returned to your contract overview and now should see the selected addon in " +"your list." msgstr "" -"Као тип стања одабиремо „чека на подсетник”. Ово означава да је тикет и даље " -"отворен и можемо поставити подсетник. Овај подсетник може бити користан " -"уколико наш произвођач понекад не реагује или желимо да их подсетимо за нам " -"доставе одговор." +"На следећој страници изаберите било који од ``sipgate.io`` пакета или ``Push-" +"API Package Free``. Пратите дијалог тако што ћете купити додатак. Бићете " +"враћени на преглед вашег уговора и сада би требало да видите изабрани " +"додатак на вашој листи." -#: ../system/objects.rst:186 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:30 msgid "" -"We choose \"no\" for \"ignore escalation\" because we want to escalate the " -"tickets even if we are waiting on the manufacturer's feedback." +"The availability for ``sipgate.io`` packages and their levels highly depends " +"on the overall account type and product you've booked with Sipgate." msgstr "" -"Одабиремо „не” за „игнориши ескалације” зато што желимо да ескалирамо тикете " -"чак иако чекамо на одговор произвођача." - -#: ../system/objects.rst:189 -msgid "The **result** in the creation dialog will look like this:" -msgstr "**Резултат** у дијалогу новог тикета ће изгледати овако:" +"Доступност пакета ``sipgate.io`` и њихови нивои у великој мери зависе од " +"укупног типа налога и производа који сте резервисали код Sipgate-а." -#: ../system/objects.rst:0 -msgid "Screenshot showing ticket state creation dialog with example" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "" +"Screencast showing the process on how to book the required sipgate.io addon" msgstr "" -"Снимак екрана који приказује дијалог за додавање новог стања тикета са " -"примером" +"Снимак екрана који приказује процес како да купите потребан sipgate.io " +"додатак" -#: ../system/objects.rst:197 ../system/objects.rst:199 -msgid "Ticket Priority" -msgstr "Приоритет тикета" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:52 +msgid "Step 2: Configure webhook for Zammad" +msgstr "Корак 2: Подесите повратни позив за Zammad" -#: ../system/objects.rst:199 ../system/objects.rst:201 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:38 msgid "" -"If the pre-configured priorities aren't enough for you or you want to change " -"them, you can do so by clicking on the cogwheel icon in the priority row in " -"the ticket tab:" +"Within your ``Accountverwaltung`` navicate to your product ``sipgate.io``. " +"In the newly opened tab, switch from \"Clients\" to \"Webhooks\" and paste " +"the endpoint URLs from your Zammad instance like so:" msgstr "" -"Уколико вам предефинисани приоритети нису довољни или желите да их измените, " -"то можете урадити кликом на иконицу зупчаника у реду са атрибутом приоритета " -"у језичку тикета:" +"У оквиру вашег ``Accountverwaltung`` одељка идите на свој ``sipgate.io`` " +"производ. У новоотвореном језичку, пребаците се са „Clients“ на „Webhooks“ и " +"налепите URL адресе путањи са ваше Zammad инстанце на следећи начин:" -#: ../system/objects.rst:None -msgid "Screenshot showing highlighted ticket priority attribute" -msgstr "Снимак екрана који приказује наглашен атрибут приоритета тикета" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:42 +msgid "Inbound endpoint to \"Incoming\"" +msgstr "Долазна путања за „Incoming“" -#: ../system/objects.rst:224 ../system/objects.rst:226 -msgid "Handling of priorities" -msgstr "Руковање приоритетима" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:43 +msgid "Outbound endpoint to \"Outgoing\"" +msgstr "Одлазна путања за „Outgoing“" -#: ../system/objects.rst:208 ../system/objects.rst:210 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:47 msgid "" -"In the priority configuration screen, you can add new priorities, disable " -"priorities or change priorities." +"Ensure to select at least one call group or phoneline within \"Sources\". " +"Other wise Sipgate will not indicate any incoming or outgoing calls to " +"Zammad." msgstr "" -"У екрану подешавања приоритета можете додати нове приоритете, искључити " -"постојеће или их изменити." +"Обавезно изаберите најмање једну групу позива или телефонску линију у оквиру " +"„Sources“. Иначе, Sipgate неће назначити никакве долазне или одлазне позиве " +"Zammad-у." -#: ../system/objects.rst:0 -msgid "Screenshot showing table of default ticket priorities" -msgstr "Снимак екрана који приказује табелу подразумеваних приоритета тикета" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "" +"Screencast showing how to add Zammad's endpoint URLs to sipgate.ios webhook " +"configuration" +msgstr "" +"Снимак екрана који показује како да додате URL адресе путања Zammad-а у " +"подешавање sipgate.io повратних позива" -#: ../system/objects.rst:216 ../system/objects.rst:218 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:55 msgid "" -"To add a new priority, click on the \"New Priority\" button in the top right " -"corner. To change an existing priority, simply click on the affected " -"priority. This opens an edit dialog." +"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " +"the Webhooks → URLs section of Sipgate you can select which *sources* " +"Sipgate should notify Zammad about in- and outgoing calls." msgstr "" -"Да бисте додали нови приоритет, кликните на дугме „Нови приоритет” у горњем " -"десном углу. За измену постојећег приоритета, једноставно кликните на " -"дотични приоритет. Ово ће отворити дијалог за уређивање." +"Имате много бројева које не би требало користити за обавештавање Zammad-а? У " +"одељку Webhooks → URLs Sipgate-а можете да изаберете које *изворе* Sipgate " +"треба да обавести Zammad о долазним и одлазним позивима." -#: ../system/objects.rst:220 ../system/objects.rst:222 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:59 msgid "" -"You can also clone a priority or set them to \"Default for new tickets\" by " -"clicking on the ⁝ action button and select the desired function." +"Use either specific phone lines or use the option \"Use for all phonelines " +"and groups\" to notify Zammad about all existing lines of your Sipgate " +"account." msgstr "" -"Такође можете клонирати приоритет или га поставити на „подразумевано за нове " -"тикете” кликом на ⁝ дугме радњи и одабиром жељене функције." +"Користите или одређене телефонске линије или користите опцију „Use for all " +"phonelines and groups“ да обавестите Zammad о свим постојећим линијама вашег " +"Sipgate налога." -#: ../system/objects.rst:223 ../system/objects.rst:225 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"*Default for new tickets* means that this priority is used for every newly " -"created ticket." +"Screenshot showing a sample selection of phone numbers to use for the " +"Sipgates webhooks API" msgstr "" -"*Подразумевано за нове тикете* значи да ће овај приоритет бити коришћен за " -"све новоотворене тикете." +"Снимак екрана који приказује пример избора телефонских бројева за употребу " +"за Sipgate API повратних позива" -#: ../system/objects.rst:246 ../system/objects.rst:248 -msgid "Priorities in detail" -msgstr "Детаљније о приоритетима" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:68 +msgid "This section also allows you to enable a Debug log." +msgstr "" +"Овај одељак вам такође омогућава да омогућите евиденцију уноса за отклањање " +"грешака." -#: ../system/objects.rst:227 ../system/objects.rst:229 -msgid "Below you can find a description for each field and option." -msgstr "Испод можете наћи опис сваког поља и опције." +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "Screenshot showing an enabled Debug log option" +msgstr "" +"Снимак екрана који приказује омогућену опцију евиденције уноса за отклањање " +"грешака" -#: ../system/objects.rst:230 ../system/objects.rst:232 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:73 msgid "" -"This is the name of the priority and what you and your agents are seeing " -"when choosing a priority somewhere (e.g. in tickets, trigger configuration)." +"After enabling you can use the Debug log section to see all sent webhook " +"calls to Zammad. You'll also can see the response." msgstr "" -"Ово је назив приоритета и шта ви и ваши оператери видите када негде бирате " -"приоритет (нпр. у тикетима, подешавању окидача)." - -#: ../system/objects.rst:240 ../system/objects.rst:242 -msgid "Highlight color" -msgstr "Боја истицања" +"Након укључивања, можете користити одељак евиденције за отклањање грешака да " +"бисте видели све позиве упућене Zammad повратном позиву. Такође ћете видети " +"и све одговоре." -#: ../system/objects.rst:235 ../system/objects.rst:237 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"Switch between *Low priority* (light blue), *High priority* (red) and - " -"(default). This affects the displayed color for ticket titles in overviews." +"Screenshot showing sample log entries for Sipgates webhook calls to Zammad" msgstr "" -"Изаберите између *Низак приоритет* (светло плава), *Висок приоритет* " -"(црвена) и - (подразумевано). Ово утиче на боју приказа наслова тикета у " -"прегледима." +"Снимак екрана који приказује примере уноса евиденције за Sipgate повратне " +"позиве Zammad-у" -#: ../system/objects.rst:239 ../system/objects.rst:241 -msgid "The color options are currently limited to the mentioned options." -msgstr "Доступне боје су тренутно ограничене на поменуте опције." +#: ../system/integrations/cti/provider-configurations/sipgate.rst:81 +msgid "Step 4 (optional): Further configurations for Sipgate" +msgstr "Корак 4 (опционо): Даља подешавања за Sipgate" -#: ../system/objects.rst:243 ../system/objects.rst:245 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:80 msgid "" -"You can create a note for the priority to inform other admins about the " -"priority. This has no effect on tickets." +"If needed, you can now configure Zammad's Sipgate integration in more " +"detail. You can learn more about your options here: :ref:`Sipgate " +"integration settings `." msgstr "" -"Можете додати напомену за приоритет да бисте обавестили друге администраторе " -"о овом приоритету. Ово нема ефекта на тикете." +"Ако је потребно, сада можете детаљније да подесите Zammad-ову Sipgate " +"интеграцију. Можете сазнати више о опцијама у :ref:`подешавањима Sipgate " +"интеграције `." -#: ../system/objects.rst:247 ../system/objects.rst:249 -msgid "Set the priority to *active* or *inactive*." -msgstr "Поставите приоритет на *укључено* или *искључено*." +#: ../system/integrations/cti/sipgate.rst:2 +msgid "Sipgate (sipgate.io)" +msgstr "Sipgate (sipgate.io)" -#: ../system/objects/external-data-source-example.rst:2 -msgid "External Data Source" -msgstr "Удаљени извор података" +#: ../system/integrations/cti/sipgate.rst:16 +msgid "You need an administrative Sipgate account for your organization." +msgstr "Потребан вам је администраторски Sipgate налог за вашу организацију." -#: ../system/objects/external-data-source-example.rst:4 +#: ../system/integrations/cti/sipgate.rst:17 msgid "" -"We assume you already had a look on :doc:`types` where you can find a " -"description of the individual fields." +"Zammad requires a ``sipgate.io`` addon from the feature store (please note " +"that API calls are not free with Sipgate. Rates may apply and differ from " +"account to account)." msgstr "" -"Претпостављамо да сте већ погледали :doc:`типове ` где можете пронаћи " -"опис појединачних поља." +"Zammad захтева ``sipgate.io`` додатак са маркета апликација. (Имајте на уму " +"да API позиви нису бесплатни. Цене могу да се разликују од налога до налога.)" -#: ../system/objects/external-data-source-example.rst:7 +#: ../system/integrations/cti/sipgate.rst:21 +msgid "Sipgate must be able to reach your Zammad instance." +msgstr "Sipgate мора бити у могућности да приступи вашој Zammad инстанци." + +#: ../system/integrations/cti/sipgate.rst:25 +msgid ":doc:`provider-configurations/sipgate`" +msgstr ":doc:`provider-configurations/sipgate`" + +#: ../system/integrations/cti/sipgate.rst:24 msgid "" -"To reproduce this example, choose a category you want to add a custom field, " -"click on *New Attribute* and select *External data source field* under " -"*Format*." +"Learn how to configure Sipgate to enable Zammad and Sipgate to communicate " +"with each other." msgstr "" -"Да бисте репродуковали овај пример, одаберите категорију коју желите да " -"додате прилагођеном пољу, клините на *Нови атрибут* и изаберите *Поље " -"удаљеног извора података* за *Формат*." +"Научите како да подесите Sipgate да бисте омогућили Zammad-у и Sipgate-у да " +"међусобно комуницирају." -#: ../system/objects/external-data-source-example.rst:11 +#: ../system/integrations/cti/sipgate.rst:33 msgid "" -"Our example story is to fetch data from an external product database. We " -"want to add our products to the tickets so that the products can be searched " -"and chosen from a list and also create a link to the product website." +"Below endpoint settings affect the :doc:`sipgate.io configuration `." msgstr "" -"Наш пример преузима податке из удаљене базе података са производима. Желимо " -"да додамо наше производе тикетима тако да је могуће претражити производе и " -"изабрати их са листе и приказати линк на страну производа." +"Подешавања путање испод утичу на :doc:`sipgate.io подешавања `." -#: ../system/objects/external-data-source-example.rst:16 -msgid "Base configuration" -msgstr "Основна подешавања" +#: ../system/integrations/cti/sipgate.rst:37 +msgid "This endpoint is required for incoming call hooks." +msgstr "Ова путања је потребна за регистрацију долазних позиве." -#: ../system/objects/external-data-source-example.rst:None -msgid "Initial steps to configure external data source object type" -msgstr "Први кораци за подешавање удаљеног извора података" +#: ../system/integrations/cti/sipgate.rst:40 +msgid "This endpoint is required for outgoing call hooks." +msgstr "Ова путања је потребна за регистрацију одлазних позива." -#: ../system/objects/external-data-source-example.rst:23 -#: ../system/variables.rst:85 -msgid "**Example:**" -msgstr "**Пример:**" +#: ../system/integrations/cti/sipgate.rst:0 +msgid "Screenshot showing sample user mappings in between Sipgate and Zammad" +msgstr "" +"Снимак екрана који приказује примере мапирања корисника између Sipgate-а и " +"Zammad-а" -#: ../system/objects/external-data-source-example.rst:25 -msgid "Name: *product*" -msgstr "Назив: *product*" +#: ../system/integrations/cti/sipgate.rst:69 +msgid "" +"You can find your agent's Sipgate username within ``Accountverwaltung → " +"Benutzer``. You're looking for the SIP-ID." +msgstr "" +"Sipgate корисничко име вашег оператера можете пронаћи у оквиру " +"``Accountverwaltung → Benutzer``. Тражите SIP-ID." -#: ../system/objects/external-data-source-example.rst:26 -msgid "Display: *Product*" -msgstr "Прикажи: *Производ*" +#: ../system/integrations/cti/sipgate.rst:0 +msgid "Sample VoIP credentials for a Sipgate user" +msgstr "Пример VoIP креденцијала за Sipgate корисника" -#: ../system/objects/external-data-source-example.rst:29 -msgid "External data source configuration" -msgstr "Подешавање удаљеног извора података" +#: ../system/integrations/cti/sipgate.rst:77 +msgid "Users with several devices also have several SIP-IDs." +msgstr "Корисници са више уређаја такође имају неколико SIP-ID-ова." -#: ../system/objects/external-data-source-example.rst:31 +#: ../system/integrations/elasticsearch.rst:2 +msgid "Elasticsearch (SaaS)" +msgstr "Elasticsearch (SaaS)" + +#: ../system/integrations/elasticsearch.rst:4 msgid "" -"First, enter the search URL making sure it contains ``#{search.term}`` as a " -"parameter:" +"The Elasticsearch integration allows you to create a read-only user to use " +"with your favorite reporting tool (e.g. like Grafana)." msgstr "" -"Прво, унесите URL адресу претраге и уверите се да садржи ``#{search.term}`` " -"као параметар:" - -#: ../system/objects/external-data-source-example.rst:34 -msgid "**Example:** ``https://dummyjson.com/products/search?q=#{search.term}``" -msgstr "**Пример:** ``https://dummyjson.com/products/search?q=#{search.term}``" +"Elasticsearch интеграција вам омогућава да додате корисника само за читање " +"кога ћете користити са вашим омиљеним алатом за извештавање (нпр. као што је " +"Grafana)." -#: ../system/objects/external-data-source-example.rst:36 +#: ../system/integrations/elasticsearch.rst:7 msgid "" -"After that, head down to the preview section and enter a search input for " -"the external data source." +"If you want to take full advantage of the Zammad reporting, have a look at " +"our :docs:`Grafana ` " +"setup page as well." msgstr "" -"Након тога, скролујте на доле до одељка приказа и унесите кључну реч за " -"претрагу удаљеног извора података." - -#: ../system/objects/external-data-source-example.rst:39 -msgid "**Example:** ``mac``" -msgstr "**Пример:** ``mac``" - -#: ../system/objects/external-data-source-example.rst:41 -msgid "Then you can find a preview of the response data below:" -msgstr "Након тога можете видети следећи приказ одговора испод:" +"Ако желите да у потпуности искористите Zammad извештавање, погледајте и нашу " +"страницу за подешавање :docs:`Grafana-е `." -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of JSON response based on search term" -msgstr "Приказ JSON одговора на основу уноса претраге" +#: ../system/integrations/elasticsearch.rst:11 ../system/subscription.rst:7 +msgid "**🚧 Hosted environment specific 🚧**" +msgstr "**🚧 Oкружење специфичхо за хостоване иснтанце 🚧**" -#: ../system/objects/external-data-source-example.rst:48 +#: ../system/integrations/elasticsearch.rst:13 msgid "" -"We recommend using the preview to have a look on the structure. There is a " -"top-level element called ``products``. One level below, you can find the " -"attributes ``id`` and ``title``." -msgstr "" -"Препоручујемо да користите приказ за преглед структуре података. Постоји " -"кључ на основном нивоу под називом ``products``. Један ниво испод, можете " -"наћи атрибуте ``id`` и ``title``." - -#: ../system/objects/external-data-source-example.rst:52 -msgid "**Search result response based on search from example:**" +"This integration is only available for Hosted setups. In order to use " +"Elasticsearch you'll need the **Plus** subscription." msgstr "" -"**Одговор резултата претраге на основу унетих кључних речи из примера:**" +"Ова интеграција је доступна само за хостоване системе. Да бисте користили " +"Elasticsearch, биће вам потребна **Plus** претплата." -#: ../system/objects/external-data-source-example.rst:119 +#: ../system/integrations/elasticsearch.rst:16 msgid "" -"To tell the remote system that the desired data is located below the " -"``products`` level, you have to put it in the field *Search result list key*." +"Self hosted users have all the control over their self hosted Elasticsearch " +"instances." msgstr "" -"Да бисте рекли удаљеном систему да се подаци налазе испод нивоа " -"``products``, неопходно га је унети у поље *Кључ листе резулата претраге*." +"Корисници који сами хостују имају сву контролу над својим Elasticsearch " +"инстанцама које сами хостују." -#: ../system/objects/external-data-source-example.rst:122 +#: ../system/integrations/elasticsearch.rst:None +msgid "Elasticsearch integration page on SaaS environments" +msgstr "Страница за Elasticsearch интеграцију у SaaS окружењима" + +#: ../system/integrations/elasticsearch.rst:27 msgid "" -"After inserting ``products`` in the mentioned field, you get an extended " -"preview. You can find an additional box *Search result list* with a JSON " -"structure. This is the same response as before but stripped from the upper " -"``products`` element by the external data source." +"Please note the following limitations of Elasticsearch access on hosted " +"environments:" msgstr "" -"По уносу ``products`` у одговарајуће поље, добићете освежен приказ. Можете " -"наћи додатан оквир *Листа резултата претрага* са JSON структуром. Ово је део " -"истог одговора удаљеног извора података као изнад али без спољног " -"``products``кључа." +"Имајте на уму следећа ограничења приступа Elasticsearch у хостованим " +"окружењима:" -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of JSON response search result list" -msgstr "Приказ JSON одговора листе резултата претраге" +#: ../system/integrations/elasticsearch.rst:30 +msgid "access to the Elasticsearch index is read-only access" +msgstr "приступ Elasticsearch индексу је омогућен само за читање" -#: ../system/objects/external-data-source-example.rst:132 +#: ../system/integrations/elasticsearch.rst:31 +msgid "currently you're limited to user only" +msgstr "тренутно сте ограничени само на кориснике" + +#: ../system/integrations/elasticsearch.rst:32 msgid "" -"Now you need to provide the keys for the search result values and labels. As " -"already mentioned, we are looking for the ``id`` and the ``title`` of our " -"products. If you haven't already, it is now a good time to look at the " -"preview of the *Search result list*." +"Reporting tools that require to write into the indexes (like Kibana) are not " +"supported" msgstr "" -"Сада је неопходно да обезбедите кључеве за вредности и ознаке резултата " -"претраге. Као што је напоменуто, тражимо ``id`` и ``title`` наших производа. " -"Ако већ нисте, сада је добар тренутак да погледате приказ *Листе резултата " -"претраге*." +"Алати за извештавање који захтевају писање у индексе (као што је Kibana) " +"нису подржани" -#: ../system/objects/external-data-source-example.rst:197 +#: ../system/integrations/elasticsearch.rst:34 +msgid "IP access restriction is currently not yet supported" +msgstr "Ограничење приступа на основу IP адресе још увек није подржано" + +#: ../system/integrations/elasticsearch.rst:37 +msgid "Activating Elasticsearch Access" +msgstr "Укључивање Elasticsearch приступа" + +#: ../system/integrations/elasticsearch.rst:39 msgid "" -"After locating our two keys, we insert them in *search result value key* " -"(``id``) and in *Search result label key* (``title``)." +"By default external access to your Elasticsearch index is not active. You " +"can enable the integration at any time if needed." msgstr "" -"Након лоцирања наша два кључа, унећемо их у *Кључ вредности резулата " -"претраге* (``id``) и у *Кључ ознаке резулата претраге* (``title``)." +"Подразумевано, спољни приступ вашем Elasticsearch индексу није омогућен. " +"Можете укључити интеграцију у било ком тренутку ако је потребно." -#: ../system/objects/external-data-source-example.rst:200 +#: ../system/integrations/elasticsearch.rst:42 msgid "" -"Basically, we configured the external data source already and we can see a " -"table in the preview section:" +"Please ensure to note down the password provided - you won't have access to " +"it afterwards." msgstr "" -"У принципу већ смо подесили удаљни извор података и сада можемо видети " -"табелу у одељку приказа:" +"Обавезно забележите достављену лозинку - касније јој нећете имати приступ." -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of product table based on search term" -msgstr "Приказ табеле производа на основу унетих кључних речи претраге" +#: ../system/integrations/elasticsearch.rst:None +msgid "Screencast showing activation of Elasticsearch integration" +msgstr "Снимак екрана који приказује укључивање Elasticsearch интеграције" -#: ../system/objects/external-data-source-example.rst:208 -msgid "" -"According to our example story, now just the *Link template* is missing." -msgstr "Даље пратећи наш пример, једино недостсаје још *Шаблон везе*." +#: ../system/integrations/elasticsearch.rst:51 +msgid "Connection Settings" +msgstr "Подешавања везе" -#: ../system/objects/external-data-source-example.rst:210 +#: ../system/integrations/elasticsearch.rst:53 msgid "" -"Please note that this is an optional feature. If you don't want to use such " -"links, of course you don't have to configure it." +"This section holds the most important general information for accessing your " +"Elasticsearch indexes - such as:" msgstr "" -"Напомињемо да је ово опциона функција. Ако не желите да користите овакве " -"линкове, наравно не морате да их подесите." +"Овај одељак садржи најважније опште информације за приступ вашим " +"Elasticsearch индексима – као што су:" -#: ../system/objects/external-data-source-example.rst:213 -msgid "" -"We can add now an address where additional product information can be found." -msgstr "" -"Сада можемо додати адресу где се додатне информације о производу могу " -"пронаћи." +#: ../system/integrations/elasticsearch.rst:57 +msgid "A unique subdomain that does not tell your real instance URL." +msgstr "Јединствени поддомен који не садржи URL адресу ваше праве инстанце." -#: ../system/objects/external-data-source-example.rst:215 -msgid "Example: ``https://your_domain.com/q=#{ticket.product}``" -msgstr "Пример: ``https://your_domain.com/q=#{ticket.product}``" +#: ../system/integrations/elasticsearch.rst:61 +msgid "Software" +msgstr "Софтвер" -#: ../system/objects/external-data-source-example.rst:217 -msgid "In the example, the parameter means:" -msgstr "У примеру, параметар има следеће значење:" +#: ../system/integrations/elasticsearch.rst:60 +msgid "" +"The major version of the search index being used. This is required by some " +"Reporting tools like Grafana." +msgstr "" +"Major верзија индекса претраге која се користи. Ово захтевају неки алати за " +"извештавање као што је Grafana." -#: ../system/objects/external-data-source-example.rst:219 -msgid "``#{}``: \"Frame\" for the insertion of information" -msgstr "``#{}``: Поље за убацивање података" +#: ../system/integrations/elasticsearch.rst:64 +msgid "Authentication" +msgstr "Аутентификација" -#: ../system/objects/external-data-source-example.rst:220 -msgid "``ticket``: object level, where you create your custom object" -msgstr "``ticket``: ниво објекта, где додајете свој прилагођени атрибут" +#: ../system/integrations/elasticsearch.rst:64 +msgid "The authentication type being supported. ``Basic Authentication``" +msgstr "Тип аутентификације који је подржан. ``Basic Authentication``" -#: ../system/objects/external-data-source-example.rst:221 -msgid "``product``: name of the (custom) object" -msgstr "``product``: назив (прилагођеног) атрибута" +#: ../system/integrations/elasticsearch.rst:67 +msgid "Available Indexes" +msgstr "Доступни индекси" -#: ../system/objects/external-data-source-example.rst:223 +#: ../system/integrations/elasticsearch.rst:69 msgid "" -"After configuring your *Link template*, there will be another column in the " -"preview. Hovering on the icons in the *Link* column will show you where it " -"forwards you." +"Within this section we're displaying the -in our opinion- most important " +"indexes for a Zammad instance." msgstr "" -"По подешавању *Шаблона везе*, биће приказана још једна колона у приказу. " -"Преласком курсора преко иконице у колони *Повежи* биће приказана адреса " -"преусмерења." +"У оквиру овог одељка приказујемо - по нашем мишљењу - најважније индексе за " +"Zammad инстанцу." -#: ../system/objects/external-data-source-example.rst:232 +#: ../system/integrations/elasticsearch.rst:72 msgid "" -"In our example, one of the links looks like: https://your_domain.com/q=6, " -"where the 6 is the product id." +"If you require all indexes or our listing is not good enough for you, point " +"your browser to the URL we're providing and append ``/_aliases?" +"pretty=true``. The result should look like this: ``https://.zammad.com/" +"_aliases?pretty=true``." msgstr "" -"У нашем примеру, један од линкова личи на: https://your_domain.com/q=6, где " -"је 6 ID вредност производа." - -#: ../system/objects/external-data-source-example.rst:235 -msgid "You can find more information regarding the URL in :doc:`types`." -msgstr "Mожете пронаћи више информација о URL адресама у :doc:`types`." +"Ако су вам потребни сви индекси или наш списак није довољно детаљан, " +"усмерите свој претраживач на следећу URL адресу ``/_aliases?pretty=true``. " +"Резултат би требало да изгледа овако: ``https://.zammad.com/_aliases?" +"pretty=true``." -#: ../system/objects/includes/adding-values-hint.include.rst:3 +#: ../system/integrations/elasticsearch.rst:77 msgid "" -"Adding values can be tricky for first timers, don't forget to press \"➕ " -"Add\" after typing your values. Otherwise you may loose a value." +"Your browser will automatically ask for your credentials - you'll then see " +"something like this:" msgstr "" -"Додавање вредности може бити незгодно за почетнике, не заборавите да " -"притиснете „➕ Додај“ након што унесете вредности. У супротном можете " -"изгубити унос." +"Ваш претраживач ће аутоматски затражити да се аутентификујете - тада ћете " +"видети нешто овако:" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:1 -#: ../system/objects/includes/reposition-values.include.rst:1 -msgid "**↕️ This field type allows the positioning of its values ↔️**" -msgstr "**↕️ Овај тип поља омогућава промену редоследа својих вредности ↔️**" +#: ../system/integrations/elasticsearch.rst:125 +msgid "Credentials" +msgstr "Креденцијали" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:3 +#: ../system/integrations/elasticsearch.rst:127 msgid "" -"In order to re-arrange the field values, first edit the field. Then you can " -"use ☰ to drag the values in question to the correct position. If you want to " -"change the layer depth, double click on ☰. With it you can cycle through the " -"available layers." +"Within this section Zammad displays your available users. The password is " +"provided once (upon activation) and cannot be retrieved after that." msgstr "" -"Да бисте изменили опције поља, прво уредите поље. Након тога можете " -"користити ☰ да бисте превукли вредност у питању на одговарајућу позицију. " -"Уколико желите да измените дубину слоја, кликните двапут на ☰. Овом радњом " -"можете и да циклично мењате дубину слоја." +"У оквиру овог одељка Zammad приказује ваше доступне кориснике. Лозинка се " +"даје једном (по активацији) и након тога се не може преузети." -#: ../system/objects/includes/reposition-treeselect-values.include.rst:8 -msgid "When you're ready, submit your changes to save the object attribute." +#: ../system/integrations/elasticsearch.rst:131 +msgid "" +"If you need to change or reset your Elasticsearch user password, use the " +"\"Reset password\" button in the credentials table. Doing so creates a brand " +"new password for the account in question. This change is immediate, keep in " +"mind that this may affect third party tools connected to your instance." msgstr "" -"Када сте спремни, пошаљите своје измене да бисте сачували атрибут објекта." +"Ако желите да промените или поништите вашу Elasticsearch корисничку лозинку, " +"користите дугме „Reset password“ у табели са креденцијалима. Овиме ћете " +"добити потпуно нову лозинку за дотични налог. Ова промена је тренутна, " +"имајте на уму да то може да утиче на алате трећег лица повезане са вашом " +"инстанцом." -#: :0 ../system/objects/types.rst:0 +#: ../system/integrations/exchange.rst:2 +msgid "Exchange" +msgstr "Exchange" + +#: ../system/integrations/exchange.rst:4 msgid "" -"Screencast showing how to re-position values on tree select like\n" -"fields" +"With Zammad's Exchange integration, you can easily use existing address " +"books without having to update more than one source." msgstr "" -"Снимак екрана који показује како да измените положај вредности\n" -"у пољима избора стабла" +"Уз Zammad-ову Exchange интеграцију, можете лако да користите постојеће " +"адресаре без потребе да ажурирате више од једног извора." -#: ../system/objects/includes/reposition-values.include.rst:3 +#: ../system/integrations/exchange.rst:7 msgid "" -"In order to re-arrange the field values, edit the field and scroll below the " -"values. Make sure to tick the option \"Use custom option sort\"." +"However, you should refrain from syncing all addresses, as the results may " +"not be what you expect (Exchange collects huge amounts of addresses). A " +"central address book of your company to sync makes more sense, as you can " +"ensure that Zammad gets only the data you need and want. Apart from this, it " +"is even not possible to sync the Global Address List (GAL) of your Exchange " +"system with Zammad." msgstr "" -"Да бисте изменили редослед опција поља, уредите поље и скролујте на доле до " -"вредности. Обратите пажњу да укључите опцију „Користи прилагођен редослед " -"опција”." +"Међутим, требало би да се уздржите од синхронизације свих адреса, јер " +"резултати можда неће бити оно што очекујете (Exchange прикупља огромне " +"количине адреса). Централни адресар ваше фирме за синхронизацију има више " +"смисла, јер можете осигурати да Zammad добија само податке који су вам " +"потребни и који желите. Поред овога, чак није ни могуће синхронизовати " +"Global Addres List (GAL) вашег Exchange система са Zammad-ом." -#: ../system/objects/includes/reposition-values.include.rst:8 +#: ../system/integrations/exchange.rst:16 msgid "" -"If you do not tick this field, all manual positioning you did above will be " -"lost upon saving! ☠️" +"**Exchange and LDAP:** The exchange sync can be overruled by Zammad's LDAP " +"integration. If you have the same users in both sources, the LDAP version " +"will always be Zammad's pick." msgstr "" -"Уколико не укључите ово поље, сав ручно одређен редослед који сте обавили " -"изнад ће бити изгубљен по снимању! ☠️" +"**Exchange и LDAP:** Exchange синхронизација може бити поништена Zammad-овом " +"LDAP интеграцијом. Ако имате исте кориснике у оба извора, LDAP верзија ће " +"увек бити Zammad-ов избор." -#: ../system/objects/includes/reposition-values.include.rst:11 +#: ../system/integrations/exchange.rst:19 msgid "" -"Now use ☰ to drag the values in question to the correct position. When " -"you're ready, submit your changes to save the object attribute." +"**One way sync:** the Exchange sync is one way. Exchange => Zammad. Changes " +"to your users inside of Zammad might be overwritten by the Exchange sync." msgstr "" -"Користите ☰ да превучете и испустите дотичне вредности на нову жељену " -"позицију. Када будете спремни, снимите ваше измене да бисте сачували атрибут " -"објекта." +"**Синхронизација у једном смеру:** Exchange синхронизација је једносмерна: " +"Exchange => Zammad. Може преписати ваше измене корисника унутар Zammad-а." -#: :0 ../system/objects/types.rst:0 -msgid "Screencast showing how to re-position values" -msgstr "Снимак екрана који приказује како да промените редослед вредности" +#: ../system/integrations/exchange.rst:24 +msgid "" +"To configure Exchange integration, simply go to the System > Integrations > " +"Exchange in the admin panel. Press \"change\" and follow the wizard for " +"adding the needed Exchange information to Zammad. On the last two steps " +"Zammad will ask you for the address book(s) and your desired attribute " +"mapping. By default, Zammad only maps email address, first- and lastname. " +"Technically, you can map any Exchange object to a Zammad user object (this " +"also works for custom objects!)." +msgstr "" +"Да бисте подесили Exchange интеграцију, једноставно идите на Систем -> " +"Интеграције -> Exchange на административној табли. Притисните „Измена“ и " +"пратите чаробњак за додавање потребних Exchange информација у Zammad. У " +"последња два корака Zammad ће вас питати за адресар(е) и мапирање жељених " +"атрибута. Подразумевано, Zammad мапира само имејл адресу, име и презиме. " +"Технички, можете мапирати било који Exchange објекат у Zammad кориснички " +"објекат (ово такође функционише и за прилагођене објекте!)." -#: ../system/objects/includes/url-template-hint.include.rst:3 +#: ../system/integrations/exchange.rst:35 msgid "" -"This field allows using :ref:`URL fields (Link Templates) `." +"If the SSL verification fails while connecting to Exchange, Zammad will ask " +"you to turn it off temporarily." msgstr "" -"Ово поље омогућава коришћење :ref:`URL адреса (шаблон везе) `." - -#: ../system/objects/permissions.rst:2 -msgid "Attribute Permissions" -msgstr "Дозволе атрибута" +"Уколико SSL провера не успе током остваривања везе са Exchange-ом, Zammad ће " +"вас питати да је привремено искључите." -#: ../system/objects/permissions.rst:7 +#: ../system/integrations/exchange.rst:38 msgid "" -"In the object attributes configuration you can define if a field is shown " -"and if the input in the field is mandatory, separated by different screens " -"and for different :doc:`roles/permissions `." +"Please be aware that **turning off SSL verification is a security risk**. It " +"should only be used temporarily or for testing purposes. If turned off, " +"there is no verification of the certificate, which means that every " +"presented certificate will be accepted." msgstr "" -"У конфигурацији атрибута објекта можете одредити да ли поље приказано и да " -"ли је унос поља обавезан, за различите екране и :doc:`корисничке улоге/" -"дозволе `." - -#: ../system/objects/permissions.rst:17 -msgid "Screenshot shows object attribute permission table" -msgstr "Снимак екрана приказује табелу дозвола за атрибут објекта" +"Имајте на уму да **искључивање SSL провере носи безбедносни ризик**. Требало " +"би је искључити само привремено или ради тестирања. Уколико је искључена, " +"сертификати неће бити верификовани, што значи да ће било који достављени " +"сертификат бити признат." -#: ../system/objects/permissions.rst:17 +#: ../system/integrations/exchange.rst:43 msgid "" -"Some of the possible permissions and screen options for a user object " -"attribute." -msgstr "Неке од могућих дозвола и опција екрана за атрибуте објекта корисника." +"After pressing Continue, Zammad will check if the configuration is okay. You " +"can then enable Exchange and start your first sync. The sync will then run " +"hourly - if you need to change mappings or the address book(s), you can " +"change the configuration at any time." +msgstr "" +"Након што кликнете на Настави, Zammad ће проверити да ли је конфигурација у " +"реду. Затим можете омогућити Exchange и започети своју прву синхронизацију. " +"Синхронизација ће се тада одвијати сваки сат - ако треба да промените " +"мапирања или адресаре, можете променити подешавања у било ком тренутку." -#: ../system/objects/permissions.rst:19 +#: ../system/integrations/exchange.rst:50 msgid "" -"Based on the object context (ticket, agent, organization, user), the " -"selectable roles (to be precise: the required permissions) and screens " -"differ. Be aware that these settings aren't affecting data creation via " -"other channels than the UI." +"After the sync has finished, you can find the new Exchange contacts under " +"\"Users\". Zammad integrates them just as normal users." msgstr "" -"На основу контекста објекта (тикет, група, организација, корисник), " -"омогућене улоге (прецизније: захтеване дозволе) и екрани се разликују. " -"Обратите пажњу да ова подешавања не управљају додавањем садржаја преко " -"других канала, ван корисничког интерфејса." +"Када се синхронизација заврши, нове Exchange контакте можете пронаћи у " +"одељку „Корисници“. Zammad их приказује баш као и обичне кориснике." -#: ../system/objects/permissions.rst:24 +#: ../system/integrations/exchange.rst:55 msgid "" -"If you want to have further customization possibilities, you should have a " -"look at the :doc:`core workflows `." +"In some cases you might see unique IDs as \"Login\" instead of the email " +"address. This is normal and doesn't affect the login or email mapping for " +"that entry." msgstr "" -"Уколико желите додатне могућности прилагођавања, погледајте документацију :" -"doc:`радних токова `." - -#: ../system/objects/permissions.rst:28 -msgid "Screens" -msgstr "Екрани" +"У неким случајевима можда ћете видети јединствене ID корисника као -ове као " +"„Пријава“ уместо имејл адресе. Ово је очекивано и не утиче на пријављивање " +"или мапирање имејл адреса за тај унос." -#: ../system/objects/permissions.rst:30 +#: ../system/integrations/github.rst:4 msgid "" -"In the table below you can find an overview about the different permissions " -"and the available screens Zammad distinguishes between." +"Use GitHub integration to track GitHub issues directly within Zammad " +"tickets. Add issue hyperlinks and get a live summary of metadata like status " +"(open/closed), assignee, labels, and more." msgstr "" -"У табели испод можете наћи преглед различитих дозвола и досступних екрана " -"које Zammad подржава." +"Користите GitHub интеграцију да бисте пратили извештаје на GitHub-у директно " +"у оквиру Zammad тикета. Додајте линкове на извештаје и добијте директан " +"резиме мета података као што су статус (отворен/затворен), прималац, ознаке " +"и још много тога." -#: ../system/objects/permissions.rst:37 -msgid "Screen" -msgstr "Екран" +#: ../system/integrations/github.rst:8 +msgid "Please note that our GitHub integration does not support pull requests." +msgstr "" +"Обратите пажњу да наша GitHub интеграција не подржава pull request-ове." -#: ../system/objects/permissions.rst:38 -msgid "Available for" -msgstr "Доступно за" +#: ../system/integrations/github.rst:None +msgid "Integration page for GitHub" +msgstr "Страница GitHub интеграције" -#: ../system/objects/permissions.rst:40 -msgid "create" -msgstr "create" +#: ../system/integrations/github.rst:18 +msgid "" +"In your GitHub settings, create a new API token under **Developer settings > " +"Personal access tokens > Generate new token**. Leave the **Scopes** section " +"empty." +msgstr "" +"У GitHub подешавањима направите нови API кључ под **Developer settings > " +"Personal access tokens > Generate new token**. Оставите одељак **Scopes** " +"празан." -#: ../system/objects/permissions.rst:41 ../system/objects/permissions.rst:52 -#: ../system/objects/permissions.rst:59 ../system/objects/permissions.rst:73 -msgid "admin.user" -msgstr "admin.user" +#: ../system/integrations/github.rst:0 ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to create a new API token" +msgstr "Снимак екрана који показује како да направите нови API кључ" -#: ../system/objects/permissions.rst:42 ../system/objects/permissions.rst:53 -#: ../system/objects/permissions.rst:60 -msgid "admin.organization" -msgstr "admin.organization" +#: ../system/integrations/github.rst:27 +msgid "Create a new API key with no scopes/privileges." +msgstr "Направите нови API кључ без привилегија." -#: ../system/objects/permissions.rst:43 ../system/objects/permissions.rst:54 -#: ../system/objects/permissions.rst:61 -msgid "admin.group" -msgstr "admin.group" +#: ../system/integrations/github.rst:29 +msgid "🔒 **Will this work for private repos?**" +msgstr "🔒 **Да ли ће ово радити за приватне репозиторије?**" -#: ../system/objects/permissions.rst:44 -msgid "Creation dialog for not yet existing data" -msgstr "Дијалог за додавање новог садржаја" +#: ../system/integrations/github.rst:31 +msgid "" +"No. To link private repo issues, **use the** ``repo`` **scope instead**. " +"Bear in mind that the resulting token will have `lots of permissions that it " +"doesn't actually need `_, which presents a security risk if your token ever falls into " +"the wrong hands." +msgstr "" +"Не. Да бисте повезали извештаје у приватним репозиторијима, **користите** " +"**scope** ``repo``. Имајте на уму да ће резултујући кључ имати `доста " +"дозвола које му заправо нису потребне `_, што може представљати безбедносни ризик ако " +"ваш кључ икада падне у погрешне руке." -#: ../system/objects/permissions.rst:45 -msgid "create_middle" -msgstr "create_middle" +#: ../system/integrations/github.rst:37 +msgid "" +"Unfortunately, because of how GitHub's OAuth token scopes are set up, this " +"is the only way to link issues on private repos." +msgstr "" +"Нажалост, због начина на који се GitHub OAuth кључеви генеришу, ово је " +"једини начин да повежете извештаје у приватним репозиторијумима." -#: ../system/objects/permissions.rst:46 ../system/objects/permissions.rst:50 -#: ../system/objects/permissions.rst:57 ../system/objects/permissions.rst:66 -#: ../system/objects/permissions.rst:70 -msgid "ticket.customer" -msgstr "ticket.customer" +#: ../system/integrations/github.rst:40 +msgid "Enter your new API token in Zammad and enable GitHub integration." +msgstr "Унесите свој нови API кључ у Zammad и укључите GitHub интеграцију." -#: ../system/objects/permissions.rst:47 ../system/objects/permissions.rst:51 -#: ../system/objects/permissions.rst:58 ../system/objects/permissions.rst:69 -msgid "ticket.agent" -msgstr "ticket.agent" +#: ../system/integrations/github.rst:0 +msgid "Screencast showing how to configure Zammad's GitHub integration" +msgstr "Снимак екрана како подесити Zammad-ову GitHub интеграцију" -#: ../system/objects/permissions.rst:48 -msgid "Ticket create dialog (middle section)" -msgstr "Дијалог отварања тикета (средњи део)" +#: ../system/integrations/github.rst:47 +msgid "" +"Use the default API endpoint (``https://api.github.com/graphql``) unless " +"you're using GitHub Enterprise Server." +msgstr "" +"Користите подразумевану API путању (``https://api.github.com/graphql``) осим " +"ако не користите GitHub Enterprise Server." -#: ../system/objects/permissions.rst:49 -msgid "edit" -msgstr "edit" +#: ../system/integrations/github.rst:50 +msgid "" +"Once completed, a new GitHub issues tab will appear in the ticket pane. 🎉" +msgstr "" +"По завршетку, нови језичак са GitHub извештајима ће се појавити у панелу " +"тикета. 🎉" -#: ../system/objects/permissions.rst:55 -msgid "Editing dialog for already existing data" -msgstr "Дијалог за уређивање постојећег садржаја" +#: ../system/integrations/github.rst:59 ../system/integrations/gitlab.rst:52 +msgid "Token verification is taking a long time" +msgstr "Провера кључа траје дуго" -#: ../system/objects/permissions.rst:56 -msgid "view" -msgstr "view" +#: ../system/integrations/github.rst:56 ../system/integrations/gitlab.rst:49 +msgid "" +"Slight delays are normal (<2 min.), especially for systems under heavy load." +msgstr "" +"Мала кашњења су очекивана (<2 мин.), посебно за системе под великим " +"оптерећењем." -#: ../system/objects/permissions.rst:62 -msgid "View-only dialog for already existing data" -msgstr "Дијалог за приказ постојећег садржаја без измена" +#: ../system/integrations/github.rst:58 +msgid "" +"Self-hosted administrators, please check your network settings to ensure " +"that your Zammad server can reach ``api.github.com``." +msgstr "" +"Администратори који сами хостујете, проверите мрежна подешавања да бисте " +"били сигурни да ваш Zammad сервер може да приступи ``api.github.com``." -#: ../system/objects/permissions.rst:64 -msgid "(e.g. user or organization from search)" -msgstr "(нпр. корисник или организација кроз претрагу)" +#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 +msgid "I reloaded the page and now the API token is gone" +msgstr "АПИ кључ је нестао по поновном учитавању странице" -#: ../system/objects/permissions.rst:65 -msgid "signup" -msgstr "signup" +#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 +msgid "" +"This may indicate that Zammad is still verifying your API token. Try " +"reloading the page again in a couple minutes." +msgstr "" +"Ово може да се деси док Zammad још увек проверава ваш API кључ. Покушајте " +"поново да учитате страницу за неколико минута." -#: ../system/objects/permissions.rst:67 -msgid "Sign-up screen for new customers" -msgstr "Екран отварања налога за нове клијенте" +#: ../system/integrations/gitlab.rst:2 +msgid "GitLab" +msgstr "GitLab" -#: ../system/objects/permissions.rst:68 -msgid "invite_customer" -msgstr "invite_customer" +#: ../system/integrations/gitlab.rst:4 +msgid "" +"Use GitLab integration to track GitLab issues directly within Zammad " +"tickets. Add issue hyperlinks and get a live summary of metadata like status " +"(open/closed), assignee, labels, and more." +msgstr "" +"Користите GitLab интеграцију да бисте пратили GitLab извештаје директно у " +"оквиру Zammad тикета. Додајте линкове на извештаје и добијте директан резиме " +"мета података као што су статус (отворен/затворен), прималац, ознаке и још " +"много тога." -#: ../system/objects/permissions.rst:71 +#: ../system/integrations/gitlab.rst:8 msgid "" -"Customer invitation screen (from :doc:`First Steps ` area)" +"Please note that our GitLab integration does not support merge requests." msgstr "" -"Екран за слање позивнице клијенту (из одељка :doc:`првих корака `)" +"Обратите пажњу да наша GitLab интеграција не подржава merge request-ове." -#: ../system/objects/permissions.rst:72 -msgid "invite_agent" -msgstr "invite_agent" +#: ../system/integrations/gitlab.rst:None +msgid "Integration page for GitLab" +msgstr "Страница GitLab интеграције" -#: ../system/objects/permissions.rst:74 +#: ../system/integrations/gitlab.rst:18 msgid "" -"Agent invitation screen (from :doc:`First Steps ` area)" +"In your GitLab preferences, create a new API token under **Access Tokens**." +msgstr "У GitLab подешавањима, направите нови API кључ под **Access Tokens**." + +#: ../system/integrations/gitlab.rst:20 +msgid "Under **Select scopes**, choose ``read_api`` only." +msgstr "У одељку **Select scopes** изаберите само ``read_api``." + +#: ../system/integrations/gitlab.rst:27 +msgid "🔒 **If you wish to link issues on any private repos...**" msgstr "" -"Екран за слање позивнице оператеру (из одељка :doc:`првих корака `)" +"🔒 **Ако желите да повежете извештаје из било ког приватног репозиторија...**" -#: ../system/objects/permissions.rst:78 -msgid "Screen Options" -msgstr "Опције екрана" +#: ../system/integrations/gitlab.rst:29 +msgid "Your API token must belong to an account with access to those repos." +msgstr "Ваш API кључ мора припадати налогу са приступом тим репозиторијумима." -#: ../system/objects/permissions.rst:80 -msgid "" -"For the different screens you can select \"show\" and \"required\" options." -msgstr "За различите екране можете одбрати опције „shown” и „required”." +#: ../system/integrations/gitlab.rst:31 +msgid "Enter your new API token in Zammad and enable GitLab integration." +msgstr "Унесите свој нови API кључ у Zammad и укључите GitLab интеграцију." -#: ../system/objects/permissions.rst:82 -msgid "**shown:** Show (check) or hide (uncheck) a field." -msgstr "**shown:** Прикажи (означено) или сакриј (одзначено) поље." +#: ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to configure Zammad's GitLab integration" +msgstr "" +"Снимак екрана који показује како да подесите Zammad-ову GitLab интеграцију" -#: ../system/objects/permissions.rst:83 +#: ../system/integrations/gitlab.rst:40 msgid "" -"**required:** Set a field to mandatory (check). Forces users (via UI and " -"API) to populate the field." +"Use the default API endpoint (``https://gitlab.com/api/graphql``) unless " +"you're a self-hosted GitLab user." msgstr "" -"**required:** Постављање поља на обавезно (означено). Очекује од корисника " -"да попуне поље (путем корисничког интерфејса и API)." - -#: ../system/objects/types.rst:7 -msgid "Example external data source" -msgstr "Пример удаљеног извора података" - -#: ../system/objects/types.rst:2 -msgid "Attribute types" -msgstr "Типови атрибута" +"Користите подразумевану API путању (``https://gitlab.com/api/graphql``) осим " +"ако хостујете GitLab сами." -#: ../system/objects/types.rst:4 +#: ../system/integrations/gitlab.rst:43 msgid "" -"When adding a new object attribute, you can choose between the following " -"attribute types." +"Once completed, a new GitLab issues tab will appear in the ticket pane. 🎉" msgstr "" -"Када додајете нови атрибут објекта, можете изабрати између следећих типова " -"атрибута." +"По завршетку, нови језичак са GitLab исвештајима ће се појавити у панелу " +"тикета. 🎉" -#: ../system/objects/types.rst:14 +#: ../system/integrations/gitlab.rst:51 msgid "" -"You cannot change the attribute format / type as soon as it is applied. If " -"you no longer need an object attribute, consider disabling it instead of " -"removing." +"Self-hosted administrators, please check your network settings to ensure " +"that your Zammad server can reach ``gitlab.com``." msgstr "" -"Не можете променити тип / формат атрибута након додавања. Уколико вам више " -"не треба атрибут, узмите у обзир да га искључите уместо да га обришете." +"Администратори који сами хостујете, проверите мрежна подешавања да бисте " +"били сигурни да ваш Zammad сервер може да приступи ``gitlab.com``." -#: ../system/objects/types.rst:18 -msgid "**What about the translation of my attributes?**" -msgstr "**А шта да радим за превод мојих атрибута?**" +#: ../system/integrations/i-doit.rst:2 +msgid "i-doit" +msgstr "i-doit" -#: ../system/objects/types.rst:20 +#: ../system/integrations/i-doit.rst:4 msgid "" -"For some attribute types you can decide if they should be translatable or " -"not. To be precise, it works only for the selectable fields because the " -"possible choices are known and limited. For the following attribute types, " -"you can set the translatable flag:" +"`i-doit `_ is an open-source **configuration " +"management database** - in other words, a tool for keeping tabs on every " +"single piece of your physical and digital infrastructure, from network " +"equipment to virtual machines on down to the faceplates on your rack shelves " +"and more." msgstr "" -"За неке типове атрибута можете одлучити да ли се могу превести или не. Мало " -"прецизније, функционише само за поља избора зато што су могуће опције " -"познате и ограничене. За следеће типове атрибута можете поставити подешавање " -"превода:" +"`i-doit `_ је **база података за управљање " +"конфигурацијом** отвореног кода — другим речима, алатка за праћење сваког " +"појединачног дела ваше физичке и дигиталне инфраструктуре, од мрежне опреме " +"до виртуелних машина све до контролних табли на вашим серверима и још много " +"тога." -#: ../system/objects/types.rst:25 -msgid "*Boolean field*" -msgstr "*Логичко поље*" +#: ../system/integrations/i-doit.rst:10 +msgid "" +"What's that got to do with Zammad? Well, if you used tickets to track issues " +"with all that hardware, you might start wishing there was a way they could " +"talk to each other." +msgstr "" +"Какве то везе има са Zammad-ом? Па, ако бисте користили тикете за праћење " +"проблема са свим тим хардвером, можда бисте желели да постоји начин да " +"комуницирају једни са другима." -#: ../system/objects/types.rst:26 -msgid "*Single selection field*" -msgstr "*Поље за једноструки избор*" +#: ../system/integrations/i-doit.rst:14 +msgid "Zammad gives you two:" +msgstr "Zammad вам даје два:" -#: ../system/objects/types.rst:27 -msgid "*Multiple selection field*" -msgstr "*Поље за вишеструки избор*" +#: ../system/integrations/i-doit.rst:17 +msgid "1. Add i-doit Links to Zammad Tickets" +msgstr "1. Додавање i-doit веза ка Zammad тикетима" -#: ../system/objects/types.rst:28 -msgid "*Single tree selection field*" -msgstr "*Поље за једноструки избор стабла*" +#: ../system/integrations/i-doit.rst:20 ../system/integrations/i-doit.rst:80 +msgid "What Users See" +msgstr "Шта корисници виде" -#: ../system/objects/types.rst:29 -msgid "*Multiple tree selection field*" -msgstr "*Поље за вишеструки избор стабла*" +#: ../system/integrations/i-doit.rst:26 +msgid "i-doit integration in Zammad's ticket pane" +msgstr "i-doit интеграција у Zammad-овом панелу тикета" -#: ../system/objects/types.rst:31 +#: ../system/integrations/i-doit.rst:26 msgid "" -"For these types, you can find an additional field *Translate field contents*:" -msgstr "За ове типове пронаћи ћете додатну опцију *Преведи садржај поља*:" - -#: ../system/objects/types.rst:0 -msgid "Screenshot showing translatable attribute types" -msgstr "Снимак екрана који приказује типове атрибута који се могу превести" - -#: ../system/objects/types.rst:38 -msgid "Screenshot with example of translatable attribute type" -msgstr "Снимак екрана са примером типа атрибута који се може превести" - -#: ../system/objects/types.rst:45 -msgid "Boolean field" -msgstr "Логичко поље" +"The i-doit integration will appear under a new 🖨 tab in the ticket pane." +msgstr "" +"i-doit интеграција ће се појавити под новим 🖨 језичком у панелу тикета." -#: ../system/objects/types.rst:41 +#: ../system/integrations/i-doit.rst:28 msgid "" -"Provides a drop-down field with display values for ``true`` and ``false``. " -"Setting a default is mandatory." +"i-doit integration puts a new tab in Zammad's ticket pane where you can add " +"links to existing i-doit devices for easy reference. (See our :user-docs:" +"`user documentation ` to learn " +"how it works in practice)." msgstr "" -"Приказује поље за избор са вредностима за ``true``и ``false``. Постављање " -"подразумеване вредности је обавезно." +"i-doit интеграција омогућава нов језичак у Zammad-овом панелу тикета где " +"можете додати везе на постојеће i-doit уређаје ради лакшег референцирања. " +"(Погледајте нашу :user-docs:`корисничку документацију ` да бисте сазнали како то функционише у пракси)." -#: ../system/objects/types.rst:0 -msgid "Available settings for Boolean fields" -msgstr "Доступна подешавања за логичка поља" +#: ../system/integrations/i-doit.rst:36 ../system/integrations/i-doit.rst:93 +msgid "How to Set it Up" +msgstr "Како подесити" -#: ../system/objects/types.rst:55 -msgid "Date field" -msgstr "Поље датума" +#: ../system/integrations/i-doit.rst:38 +msgid "" +"It requires i-doit's `API Add-on `_. Make sure to have it properly set up. Use the following setting:" +msgstr "" +"Захтева i-doit `API додатак `_. Обавезно проверите да ли је исправно подешен. Користите следећа " +"подешавања:" -#: ../system/objects/types.rst:48 -msgid "Provides a date picker field and does not allow default values." -msgstr "Приказује поље бирача датума и не подржава подразумеване вредности." +#: ../system/integrations/i-doit.rst:42 +msgid "Active: ``Yes``" +msgstr "Active: ``Yes``" -#: ../system/objects/types.rst:52 -msgid "Default time diff (hours)" -msgstr "Подразумевана временска разлика (сати)" +#: ../system/integrations/i-doit.rst:43 +msgid "Enforce authentication by username and password: ``No``" +msgstr "Enforce authentication by username and password: ``No``" -#: ../system/objects/types.rst:51 +#: ../system/integrations/i-doit.rst:45 msgid "" -"This setting helps the user by highlighting the day from now plus the " -"provided value. It *does not* pre-fill the field." +"To set it up, enable the integration in the Zammad admin panel under " +"**System > Integrations > i-doit**:" msgstr "" -"Ово подешавање помаже кориснику означавањем датума унете временске разлике " -"од сада. *Неће* аутоматски попунити вредност поља." +"Да бисте је подесили, прво укључите интеграцију у Zammad администраторском " +"интерфејсу под **Систем > Интеграције > i-doit**:" -#: ../system/objects/types.rst:0 -msgid "Available settings for Date fields" -msgstr "Доступна подешавања поља датума" +#: ../system/integrations/i-doit.rst:None +msgid "i-doit settings within the integration pages" +msgstr "i-doit подешавања у оквиру страница за интеграцију" -#: ../system/objects/types.rst:73 -msgid "Date & time field" -msgstr "Поље датума и времена" +#: ../system/integrations/i-doit.rst:53 +msgid "The root URL of your i-doit installation." +msgstr "Основни URL ваше i-doit инсталације." -#: ../system/objects/types.rst:58 -msgid "Provides a date and time picker – does not allow default values" -msgstr "Приказује бирач датума и времена – не подржава подразумеване врености" +#: ../system/integrations/i-doit.rst:62 +msgid "API token" +msgstr "API кључ" -#: ../system/objects/types.rst:62 -msgid "Allow future" -msgstr "Дозволи у будућности" +#: ../system/integrations/i-doit.rst:56 +msgid "" +"Found in the i-doit admin panel under **Interfaces / external data > JSON-" +"RPC API > Common Settings**." +msgstr "" +"Налази се у i-doit административном панелу под **Interfaces / external data " +"> JSON-RPC API > Common Settings**." -#: ../system/objects/types.rst:0 -msgid "Forbid dates and times in the future." -msgstr "Контролише могућност уноса датума и времена у будућности." +#: ../system/integrations/i-doit.rst:0 +msgid "i-doit administration interface with API configuration" +msgstr "i-doit административни интерфејс са API конфигурацијом" -#: ../system/objects/types.rst:66 -msgid "Allow past" -msgstr "Дозволи у прошлости" +#: ../system/integrations/i-doit.rst:67 +msgid "Client ID" +msgstr "Клијент ID" -#: ../system/objects/types.rst:0 -msgid "Forbid dates and times in the past." -msgstr "Контролише могућност уноса датума и времена у прошлости." +#: ../system/integrations/i-doit.rst:65 +msgid "A unique name to identify Zammad within i-doit." +msgstr "Јединствени назив за идентификацију Zammad-а унутар i-doit-а." -#: ../system/objects/types.rst:70 -msgid "Default time diff (minutes)" -msgstr "Подразумевана временска разлика (минути)" +#: ../system/integrations/i-doit.rst:67 +msgid "(Zammad does not require you to enter a value here, but i-doit might!)" +msgstr "" +"(Zammad не захтева од вас да унесете вредност овде, али i-doit би могао!)" -#: ../system/objects/types.rst:69 +#: ../system/integrations/i-doit.rst:70 msgid "" -"This setting helps the user by highlighting the day from now plus the " -"provided value. It does not pre-fill the field." +"Here you can decide if the certificate of your i-doit system has to be " +"verified or not. In case you are using custom certificates, please have a " +"look at :doc:`how to add them to Zammad `." msgstr "" -"Ово подешавање помаже кориснику означавањем датума унете временсе разлике од " -"сада. *Неће* аутоматски попунити вредност поља." +"Овде можете одлучити да ли ће сертификат вашег i-doit система бити проверен " +"или не. У случају да користите прилагођене сертификате, молимо погледајте и :" +"doc:`како да их додате у Zammad `." -#: ../system/objects/types.rst:0 -msgid "Available settings for Date & time fields" -msgstr "Доступна подешавања за поља датуме и времена" +#: ../system/integrations/i-doit.rst:77 +msgid "2. List / Create Zammad Tickets in i-doit" +msgstr "2. Излистајте / Додајте Zammad тикете у i-doit" -#: ../system/objects/types.rst:86 -msgid "Integer field" -msgstr "Целобројно поље" +#: ../system/integrations/i-doit.rst:None +msgid "Zammad integration in i-doit's device view" +msgstr "Zammad интеграција у приказу уређаја i-doit-а" -#: ../system/objects/types.rst:76 +#: ../system/integrations/i-doit.rst:86 msgid "" -"Provides an input field that allows integer usage only. You may define a " -"default value. You cannot enforce comma separation." +"i-doit's ticket system integration gives you a way to see all the tickets " +"for a given device without ever leaving i-doit. (See our :user-docs:`user " +"documentation ` to learn how it " +"works in practice)." msgstr "" -"Приказује поље уноса које дозвољава унос само целобројних вредности. Могуће " -"је дефинисати подразумевану вредност. Није могуће захтевати децималну поделу." +"Интеграција i-doit система тикета даје вам начин да видите све тикете за " +"дати уређај без напуштања i-doit-а. (Погледајте нашу :user-docs:`корисничку " +"документацију ` да бисте сазнали " +"како то функционише у пракси)." -#: ../system/objects/types.rst:80 -msgid "Minimal" -msgstr "Минимални" +#: ../system/integrations/i-doit.rst:95 +msgid "" +"Enable this integration in the i-doit admin panel under **Interfaces / " +"external data > Trouble Ticket System (TTS) > Configuration**:" +msgstr "" +"Укључите ову интеграцију у i-doit административном панелу под **Interfaces / " +"external data > Trouble Ticket System (TTS) > Configuration**:" -#: ../system/objects/types.rst:80 -msgid "The minimal value the field accepts." -msgstr "Минимална вредност коју поље прихвата." +#: ../system/integrations/i-doit.rst:None +msgid "i-doit administration interface with TTS configuration" +msgstr "i-doit административни интерфејс са TTS конфигурацијом" -#: ../system/objects/types.rst:83 -msgid "Maximal" -msgstr "Максимални" +#: ../system/integrations/i-doit.rst:104 +msgid "TTS-Type" +msgstr "TTS-Type" -#: ../system/objects/types.rst:83 -msgid "The maximum value the field accepts." -msgstr "Максимална вредност коју поље прихвата." +#: ../system/integrations/i-doit.rst:104 +msgid "``Zammad``" +msgstr "``Zammad``" -#: ../system/objects/types.rst:0 -msgid "Available settings for Integer fields" -msgstr "Доступна подешавања целобројних поља" +#: ../system/integrations/i-doit.rst:115 +msgid "Username / Password" +msgstr "Корисничко име / лозинка" -#: ../system/objects/types.rst:99 -msgid "Multiple selection field" -msgstr "Поље за вишеструки избор" +#: ../system/integrations/i-doit.rst:107 +msgid "Login credentials for a Zammad agent." +msgstr "Креденцијали за пријаву Zammad оператера." -#: ../system/objects/types.rst:89 +#: ../system/integrations/i-doit.rst:109 msgid "" -"Provides a selection field that allows the selection of one or more out of " -"several. This field does allow setting a default value." +"This agent must have **read permission** for all :doc:`groups ` that plan on using the i-doit integration." msgstr "" -"Приказује поље падајућег менија које омогућава избор једне или више опција " -"од понуђених. Ово поље дозвољава подешавање подразумеване вредности." +"Овај оператер мора имати **дозволу за читање** за све :doc:`групе ` које планирају да користе i-doit интеграцију." -#: ../system/objects/types.rst:0 -msgid "Available settings for Multiple selection fields" -msgstr "Доступна подешавања поља вишеструког избора" +#: ../system/integrations/i-doit.rst:113 +msgid "" +"You may even wish to create a dedicated agent account just for this " +"integration (otherwise, if the agent ever changes her password, you will " +"have to remember to update it here)." +msgstr "" +"Можда ћете чак желети да направите наменски налог оператера само за ову " +"интеграцију (у супротном, ако оператер икада промени своју лозинку, мораћете " +"да се сетите да је освежите и овде)." -#: ../system/objects/types.rst:112 -msgid "Single selection field" -msgstr "Поље за једноструки избор" +#: ../system/integrations/i-doit.rst:117 +msgid "URL incl. protocol" +msgstr "URL адреса укључујући и протокол" -#: ../system/objects/types.rst:102 +#: ../system/integrations/i-doit.rst:118 +msgid "``https://your.zammad.domain``" +msgstr "``https://your.zammad.domain``" + +#: ../system/integrations/index.rst:2 +msgid "Integrations" +msgstr "Интеграције" + +#: ../system/integrations/index.rst:4 msgid "" -"Provides a drop-down field that allows selection of one value out of " -"several. This field does allow setting a default value." +"Zammad offers numerous integrations that add rich features to your instance." msgstr "" -"Приказује поље падајућег менија које омогућава избор једне опције од " -"понуђених. Ово поље дозвољава подешавање подразумеване вредности." +"Zammad нуди бројне интеграције које додају богате функције вашој инстанци." -#: ../system/objects/types.rst:0 -msgid "Available settings for Single selection fields" -msgstr "Доступна подешавања поља једноструког избора" +#: ../system/integrations/index.rst:6 +msgid "We're still working on this part of our documentation, stay tight!" +msgstr "Још увек радимо на овом делу наше документације, само што није готово!" -#: ../system/objects/types.rst:142 -msgid "Textarea field" -msgstr "Текстуално поље" +#: ../system/integrations/index.rst:10 +msgid "Integrations for Phone Systems" +msgstr "Интеграције за телефонске централе" -#: ../system/objects/types.rst:115 +#: ../system/integrations/index.rst:14 msgid "" -"Provides a text area input field (multiple lines) and thus allows e.g. new " -"lines. You can set a default field value." +"Your VoIP provider or telephony system is not listed? Possibly your provider " +"supports Zammad by using the generic CTI - if you're unsure ask your " +"provider." msgstr "" -"Приказује поље текстуалног уноса (од више линија) и дозвољава унос нпр. " -"ентера. Можете подесити подразумевану вредност поља." +"Ваш VoIP провајдер или телефонски систем није наведен? Можда ваш провајдер " +"подржава Zammad користећи генерички CTI - ако нисте сигурни питајте свог " +"провајдера." -#: ../system/objects/types.rst:120 +#: ../system/integrations/index.rst:18 msgid "" -"Please note that this field *does not* support text formatting or HTML " -"content (rich text)." +"Provider does not support Zammad? Consider creating a `feature request in " +"the Zammad Community `_." msgstr "" -"Обратите пажњу да ово поље *не* подржава форматирање текста или HTML садржај " -"(обогаћен текст)." +"Провајдер не подржава Zammad? Размислите о слању `захтева за нову функцију " +"на Zammad Community форуму `_." -#: ../system/objects/types.rst:123 -msgid "**🥵 This field can consume a lot of visual space**" -msgstr "**🥵 Ово поље може заузети доста визуелног простора**" +#: ../system/integrations/index.rst:31 +msgid "Integrations for Authentication and Customers" +msgstr "Интеграције за аутентификацију и клијенте" -#: ../system/objects/types.rst:125 -msgid "" -"Depending on where you use this field type, it may use a lot of visual space " -"if you provide a lot of text. This may be an issue to work with." -msgstr "" -"У зависности од тога где користите овај тип поља, могуће је да ће заузети " -"доста визуелног простора по уносу веће количине текста. Ово може " -"представљати проблем при раду." +#: ../system/integrations/index.rst:44 +msgid "Integrations for Monitoring Systems" +msgstr "Интеграције за системе за надзор" -#: ../system/objects/types.rst:130 -msgid "Default" -msgstr "Подразумевано" +#: ../system/integrations/index.rst:46 +msgid "This section currently misses the following integrations:" +msgstr "У овом одељку тренутно недостају следеће интеграције:" -#: ../system/objects/types.rst:129 -msgid "" -"The here provided text will be shown within the text area field or new data " -"sets." -msgstr "" -"Унешен текст овде биће приказан у оквиру текстуалног поља или нових скупова " -"података." +#: ../system/integrations/index.rst:48 +msgid "Icinga" +msgstr "Icinga" -#: ../system/objects/types.rst:134 ../system/objects/types.rst:160 -msgid "Maxlength" -msgstr "Максимална дужина" +#: ../system/integrations/index.rst:49 +msgid "Monit" +msgstr "Monit" -#: ../system/objects/types.rst:0 ../system/objects/types.rst:160 -msgid "You can pick the maximum length of the field." -msgstr "Можете одредити максималну дозвољену дужину поља." +#: ../system/integrations/index.rst:50 +msgid "Nagios" +msgstr "Nagios" -#: ../system/objects/types.rst:0 -msgid "The default length of this object is ``500``." -msgstr "Подразумевана дужина за овај објекат је ``500`` карактера." +#: ../system/integrations/index.rst:60 +msgid "Integrations for Issue Trackers" +msgstr "Интеграције за праћење проблема" -#: ../system/objects/types.rst:139 -msgid "Rows" -msgstr "Редови" +#: ../system/integrations/index.rst:70 +msgid "Other Integrations" +msgstr "Додатне интеграције" -#: ../system/objects/types.rst:0 +#: ../system/integrations/index.rst:72 msgid "" -"Change the number of rows to dislay so that you can use only the space you " -"really need." +"This section will hold any other integration that can't be grouped up (yet)." msgstr "" -"Промените број редова за приказ тако да заузмете само простор који вам је " -"заиста неопходан." - -#: ../system/objects/types.rst:0 -msgid "The default number of rows is ``4``." -msgstr "Подразумеван број редова је ``4``." - -#: ../system/objects/types.rst:0 -msgid "Available settings for Textarea fields" -msgstr "Доступна подешавања текстуалних поља" +"Овај одељак садржи све додатне интеграције које се (још увек) не могу " +"груписати заједно." -#: ../system/objects/types.rst:165 -msgid "Text field" -msgstr "Поље текста" +#: ../system/integrations/ldap/index.rst:2 +msgid "LDAP / Active Directory" +msgstr "LDAP / Active Directory" -#: ../system/objects/types.rst:145 -msgid "Provides a text field (one line) and allows choosing a default value." +#: ../system/integrations/ldap/index.rst:4 +msgid "" +"Zammad comes with a powerful LDAP integration that allows you to have a " +"single source of truth. By this you reduce the number of login credentials " +"your user has to remember." msgstr "" -"Приказује поље текста (у једној линији) и омогућава избор подразумеване " -"вредности." +"Zammad долази са моћном LDAP интеграцијом која вам омогућава да имате " +"јединствени извор корисника. Тиме смањујете број креденцијала за пријаву " +"које ваш корисник мора да запамти." -#: ../system/objects/types.rst:148 +#: ../system/integrations/ldap/index.rst:10 msgid "" -"Defines the type of the input field. This allows e.g. your browser to ensure " -"that you provide the specific type." +"The LDAP source is also a perfect candidate for Zammad's :docs:`Kerberos " +"Single Sign-On ` but also works as addition " +"to other :doc:`/settings/security/third-party`." msgstr "" -"Одређује тип уноса поља. Ово омогућава нпр. вашем претраживачу да ограничи " -"унос само одговарајућег типа." +"LDAP извор је такође савршен кандидат за Zammad-ову :docs:`јединствену " +"пријаву путем Kerberos `, али такође " +"функционише и као додатак другим :doc:`аутентификацијама путем трећег лица `." -#: ../system/objects/types.rst:152 -msgid "Currently available:" -msgstr "Тренутно доступно:" +#: ../system/integrations/ldap/index.rst:None +msgid "Zammands LDAP management page" +msgstr "Страница за подешавање LDAP интеграције" -#: ../system/objects/types.rst:155 -msgid "Phone" -msgstr "Позив" +#: ../system/integrations/ldap/index.rst:25 +msgid "📝 :doc:`manage`" +msgstr "📝 :doc:`подешавање `" -#: ../system/objects/types.rst:156 -msgid "Text" -msgstr "Текст" +#: ../system/integrations/ldap/index.rst:25 +msgid "Add, modify, remove or re-arrange your LDAP-Sources as needed." +msgstr "" +"Додајте, измените, уклоните или преуредите своје LDAP изворе по потреби." -#: ../system/objects/types.rst:157 -msgid "Url *(URL fields disable link-template availability)*" -msgstr "URL *(URL поља онемогућавају шаблоне везе)*" +#: ../system/integrations/ldap/index.rst:30 +msgid "Before you continue, please note the following limitations." +msgstr "Пре него што наставите, имајте на уму следећа ограничења." -#: ../system/objects/types.rst:0 -msgid "Available settings for Text fields" -msgstr "Доступна подешавања поља текста" +#: ../system/integrations/ldap/index.rst:32 +msgid "Mapping / Synchronizing organizations is not possible" +msgstr "Мапирање / синхронизација организација није могућа" -#: ../system/objects/types.rst:174 -msgid "Single tree selection field" -msgstr "Поље за једноструки избор стабла" +#: ../system/integrations/ldap/index.rst:36 +msgid "" +"You may want to consider using domain based assignments to overcome this " +"issue. Learn more on :doc:`/manage/organizations/index`." +msgstr "" +"Можда бисте желели да размислите о коришћењу доделе на основу домена да " +"бисте превазишли овај проблем. Сазнајте више у одељку о :doc:`организацијама " +"`." -#: ../system/objects/types.rst:168 +#: ../system/integrations/ldap/index.rst:39 msgid "" -"Provides a select-like field with up to 6 layers of options. Does not allow " -"setting a default value." +"Zammad's LDAP sync is one way. Editing user settings or permissions may be " +"overwritten upon the next sync depending on your configuration." msgstr "" -"Приказује поље избора са до 6 нивоа опција. Не омогућава постављање " -"подразумеване вредности." +"Zammad-ова LDAP синхронизација је један од начина. Уређивање корисничких " +"подешавања или дозвола може бити преписано приликом следеће синхронизације у " +"зависности од ваше конфигурације." -#: ../system/objects/types.rst:0 -msgid "Available settings for Tree Select fields" -msgstr "Доступна подешавања поља за избора стабла" +#: ../system/integrations/ldap/index.rst:41 +msgid "Nested groups are not supported." +msgstr "Угнежђене групе нису подржане." -#: ../system/objects/types.rst:183 -msgid "Multiple tree selection field" -msgstr "Поље за вишеструки избор стабла" +#: ../system/integrations/ldap/index.rst:42 +msgid "Synchronizing user avatars from LDAP is not supported." +msgstr "Синхронизовање аватар сличица корисника путем LDAP-а није подржано." -#: ../system/objects/types.rst:177 +#: ../system/integrations/ldap/index.rst:43 +msgid "Unlike user filters, group filters cannot be changed." +msgstr "За разлику од корисничких филтера, групни филтери се не могу мењати." + +#: ../system/integrations/ldap/index.rst:44 msgid "" -"Provides a select-like field with up to 6 layers of options allowing the " -"selection of multiple values. Does not allow setting a default value." +"When a user originates from an LDAP server, Zammad will try to verify the " +"login credentials against LDAP first - if this fails Zammad will check its " +"local database." msgstr "" -"Приказује поље избора са до 6 нивоа опција омогућавајући избор вишеструких " -"вредности. Не омогућава постављање подразумеване вредности." - -#: ../system/objects/types.rst:302 -msgid "External Data Source field" -msgstr "Поље удаљеног извора података" +"Када корисник долази са LDAP сервера, Zammad ће прво покушати да провери " +"креденцијале за пријаву путем LDAP - ако ово не успе, Zammad ће проверити и " +"своју локалну базу података." -#: ../system/objects/types.rst:186 +#: ../system/integrations/ldap/index.rst:50 msgid "" -"Provides a searchable field which fetches data from an external system. This " -"can be useful if you have data outside of Zammad and don't want to maintain " -"both data sources." +"Users can have local passwords even if they're LDAP users! You can learn " +"more about user accounts in general on :doc:`/manage/users/index`." msgstr "" -"Омогућава поље са функцијом претраживања која учитава податке са удаљеног " -"система. Ово може бити корисно ако имате податке изван Zammad-а и не желите " -"да уређујете оба извора података." - -#: ../system/objects/types.rst:190 -msgid "The feature works as follows:" -msgstr "Функција ради на следећи начин:" +"Корисници могу имати локалне лозинке чак и ако су LDAP корисници! Можете " +"сазнати више о корисничким налозима уопште у одељку о :doc:`корисницима `." -#: ../system/objects/types.rst:192 +#: ../system/integrations/ldap/index.rst:54 msgid "" -"Zammad sends a query with a search string (free text from agent or based on " -"a variable) in a pre-defined format (\"Search URL\") to an external system." +"When several LDAP sources contain the same user (meaning the same email " +"address), the user in question will be updated with every source configured. " +"*The last LDAP source will win.*" msgstr "" -"Zammad шаље упит са кључним речима а претрагу (слободан унос текста од " -"стране оператера или на основу променљиве) у предефинисаном формату („URL за " -"претрагу”) удаљеном систему." +"Када неколико LDAP извора садржи истог корисника (што значи исту имејл " +"адресу), дотични корисник ће бити освежен из сваког подешеног извором. " +"*Последњи LDAP извор ће победити.*" -#: ../system/objects/types.rst:195 +#: ../system/integrations/ldap/index.rst:58 msgid "" -"This external system searches for matches and provides a response as a JSON " -"structure to Zammad." +"This is subject to change with `Issue 4109 `_ in the future." msgstr "" -"Удаљени систем претражује податке и обезбељује одговор као JSON структуру за " -"Zammad." +"Ово је подложно променама са `извештајем 4109 `_ у будућности." -#: ../system/objects/types.rst:197 +#: ../system/integrations/ldap/index.rst:60 msgid "" -"Zammad just looks for the defined list and value keys, reads the content and " -"displays the value to the user. There is no search on Zammad side." +"Synchronization statistics currently affect *all* configured LDAP sources. " +"This also applies for newly added or updated sources." msgstr "" -"Zammad онда обрађује податке на основу дефинисаних кључева листе и " -"вредности, и приказује садржај кориснику. Претрага се не врши на страни " -"Zammad-а." +"Статистика синхронизације тренутно утиче на *све* подешена LDAP изворе. Ово " +"такође важи за новододате или освежене изворе." -#: ../system/objects/types.rst:201 +#: ../system/integrations/ldap/index.rst:63 msgid "" -"The usage of a PostgreSQL database for Zammad is required. In any other " -"case, Zammad will hide the external data source type and you are not able to " -"use it. If you want to use this feature, consider to :docs:`migrate your " -"database `." +"This is subject to change with `Issue 4108 `_ in the future." msgstr "" -"Коришћење PostgreSQL базе података је захтевано за ову функцију. У сваком " -"другом случају, Zammad ће сакрити избор овог поља и нећете моћи да га " -"користите. Ако желите да користите ову функцију, размотрите и :docs:" -"`миграцију ваше базе података `." +"Ово је подложно променама са `извештајем 4108 `_ у будућности." -#: ../system/objects/types.rst:205 -msgid "Currently, only ``GET`` is supported as request method." -msgstr "Тренутно, подржани су само захтеви путем ``GET`` методе." +#: ../system/integrations/ldap/index.rst:65 +msgid "" +"Zammad currently has limited fallback server support. You can workaround " +"this by providing several sources - however, ensure to have the exact same " +"configuration on your fallback." +msgstr "" +"Zammad тренутно има ограничену подршку за резервни сервер. Ово можете " +"заобићи тако што ћете обезбедити неколико извора - међутим, уверите се да " +"имате потпуно исту конфигурацију на резервном серверу." -#: ../system/objects/types.rst:206 +#: ../system/integrations/ldap/index.rst:69 msgid "" -"The data structure must be in JSON format and provide the objects in an " -"array." +"This is subject to improve with `Issue 4107 `_ in the future." msgstr "" -"Структура података мора бити у JSON формату и враћени објекти морају бити " -"ускладиштени као низ." +"Ово је предмет побољшања у `извештају 4107 `_ у будућности." -#: ../system/objects/types.rst:208 +#: ../system/integrations/ldap/index.rst:76 msgid "" -"The endpoint for the external data source has to support search. On Zammad " -"side, there is no search/logic implemented; however, you can define the " -"output key and value based on the result(s) from the response (which " -"provides already filtered content based on the search)." +"This section holds all requests Zammad handled for all LDAP sources. These " +"entries can either contain synchronization information or logins " +"(authentication attempts via Zammad's login interface)." msgstr "" -"Путања за удаљени извор података мора да подржава претрагу. Са Zammad стране " -"није имплементирана било каква логика претраге; међутим можете дефинисати " -"изворни кључ и вредност на основу резултата одговора (који обезбеђује већ " -"изфилтриран садржај на основу кључних речи)." +"Овај одељак садржи све захтеве које је Zammad обрадио за све LDAP изворе. " +"Ови уноси могу да садрже информације о синхронизацији или пријави (покушаји " +"аутентификације преко Zammad-овог интерфејса за пријаву)." -#: ../system/objects/types.rst:212 +#: ../system/integrations/ldap/index.rst:80 msgid "" -"If you receive more results as expected, your external data source search " -"may not work properly or the structure of the URL is not correct. You should " -"get in touch with a responsible person from the external system." +"By clicking on any request, Zammad will provide even more information. The " +"provided information can be useful when something does not work as expected." msgstr "" -"Уколико примите више резултата од очекиваних, претрага вашег удаљеног извора " -"података можда не ради како треба или структура URL путање није исправна. " -"Ступите у контакт са одговорном особом удаљеног система." +"Кликом на било који захтев, Zammad ће пружити још више информација. " +"Представљене информације могу бити корисне када нешто не функционише на " +"начин како се очекује." -#: ../system/objects/types.rst:217 +#: ../system/integrations/ldap/index.rst:85 msgid "" -"Please have a look :doc:`at our example `, where you can find a possible configuration for a public " -"dummy endpoint." +"Especially a LDAP synchronization can cause many log entries. The web " +"interface will always limit the number of shown entries to the last 50 " +"entries." msgstr "" -"Погледајте :doc:`наш пример ` " -"са описом могућих подешавања за јавно доступну путању са лажним подацима." +"Нарочито LDAP синхронизација може проузроковати много уноса евиденције. " +"Кориснички интерфејс ће увек ограничити број приказаних уноса на последњих " +"50." -#: ../system/objects/types.rst:0 -msgid "Available settings for external data source fields" -msgstr "Доступна подешавања за поља удаљеног извора података" +#: ../system/integrations/ldap/index.rst:None +msgid "" +"Screencast showing LDAP integration log entries and a detail view on\n" +"an entry." +msgstr "" +"Снимак екрана који приказује уносе евиденције LDAP интеграције и детаљан " +"приказ\n" +"уноса." -#: ../system/objects/types.rst:242 -msgid "Search URL" -msgstr "URL за претрагу" +#: ../system/integrations/ldap/manage.rst:2 +msgid "Manage LDAP-Sources" +msgstr "Подешавање LDAP извора" -#: ../system/objects/types.rst:227 +#: ../system/integrations/ldap/manage.rst:6 msgid "" -"Set your endpoint where Zammad fetches the data. Please make sure to include " -"a valid search :doc:`variable <../variables>` as an URL parameter. Example " -"for a free text search at user input: ``#{search.term}``" +"Please keep in mind all current limitations for the LDAP synchronization. " +"This will help to understand scopes of the following operations better." msgstr "" -"Одређује путању одакле Zammad преузима податке. Молимо обезбедите исправну :" -"doc:`променљиву <../variables>` претраге као URL параметар. Пример за " -"текстуалну претрагу на основу корисничког уноса: ``#{search.term}``" +"Имајте на уму сва тренутна ограничења за LDAP синхронизацију. Ово ће вам " +"помоћи да боље разумете обим следећих операција." -#: ../system/objects/types.rst:232 +#: ../system/integrations/ldap/manage.rst:65 +msgid "Add new source" +msgstr "Додавање новог извора" + +#: ../system/integrations/ldap/manage.rst:10 msgid "" -"If in doubt, ask the responsible person for the external data source how " -"they expect the strucuture of the URL." +"Using the *New Source* button allows you to add new LDAP sources to your " +"installation. You're not limited in the number of sources, however, keep in " +"mind that many sources will also take more time to synchronize." msgstr "" -"Уколико нисте сигурни, приупитајте особу одговорну за удаљени извор података " -"какву структуру URL адресе очекују." +"Коришћење дугмета *Нови извор* омогућава вам да додате нове LDAP изворе у " +"вашим инсталацијама. Нисте ограничени у броју извора, међутим, имајте на уму " +"да ће великом броју извора такође бити потребно више времена за " +"синхронизацију." -#: ../system/objects/types.rst:236 +#: ../system/integrations/ldap/manage.rst:14 msgid "" -"Depending on your search variable, the preview might work or not. The reason " -"is that the context might not be available and it is no bug." +"You can choose between different encryption types, namely *SSL* and " +"*STARTTLS* or none of them (\"*No SSL*\"). If you choose *SSL* or " +"*STARTTLS*, Zammad will display an additional *SSL verification* option that " +"allows you to disable the verification, e.g. for self-signed SSL " +"certificates. You can also tell Zammad to use a different port by appending " +"``:`` to your hostname/IP." msgstr "" -"У зависности од ваше променљиве претраге, приказ може али и не мора " -"функционисати. Разлог је да контекст претраге можда није доступан и ово " -"технички није грешка." +"Можете одабрати између различитих типова шифровања, тј. *SSL* и *STARTTLS* " +"или ниједан („*No SSL*”). Ако изаберете *SSL* или *STARTTLS*, Zammad ће " +"приказати додатну опцију *SSL провера* која вам омогућава да искључите " +"верификацију, нпр. за прилагођене SSL сертификате. Такође можете рећи Zammad-" +"у да користи другачији порт додатком ``:<број порта>`` вашем називу сервера/" +"IP-у." -#: ../system/objects/types.rst:239 +#: ../system/integrations/ldap/manage.rst:0 msgid "" -"Please also make sure to use a variable which is available in your object " -"context. For example you won't be able to search for a ticket in a user " -"object context." +"Screenshot of configuring a new LDAP source with SSL encryption and SSL " +"verification" msgstr "" -"Такође морате обезбедити да користите променљиве које су доступне у " -"контексту вашег објекта. На пример нећете моћи да претражујете за тикете у " -"контексту објекта корисника." - -#: ../system/objects/types.rst:252 -msgid "SSL Verification" -msgstr "SSL провера" +"Снимак екрана подешавања новог LDAP извора са SSL шифровањем и SSL провером" -#: ../system/objects/types.rst:245 -msgid "Here you can switch the SSL verification to no." -msgstr "Овде можете поставити SSL проверу на не." +#: ../system/integrations/ldap/manage.rst:26 +msgid "" +"New Source with SSL transport security enabled and certificate verification" +msgstr "Нови извор са SSL укљученим протоколом и провером сертификата" -#: ../system/objects/types.rst:249 +#: ../system/integrations/ldap/manage.rst:30 msgid "" -"If your external data source system is using self signed certificates, " -"please have a look :doc:`here ` for " -"further information about how to handle them in Zammad, so you can keep the " -"SSL verification activated." +"Using an user filter can be a good idea if you only require a small subset " +"of your LDAP users in Zammad." msgstr "" -"Уколико ваш удаљени извор података користи прилагођени сертификат, молимо " -"погледајте :doc:`овде ` за више детаља " -"како да их увезете у Zammad, тако да можете да оставите укључену SSL проверу." +"Коришћење филтера корисника може бити добра идеја ако вам је потребан само " +"мали подскуп ваших LDAP корисника у Zammad-у." -#: ../system/objects/types.rst:258 -msgid "HTTP Authentication" -msgstr "HTTP аутентификација" +#: ../system/integrations/ldap/manage.rst:42 +msgid "This especially affects inactive users" +msgstr "Ово посебно утиче на неактивне кориснике" -#: ../system/objects/types.rst:255 +#: ../system/integrations/ldap/manage.rst:34 msgid "" -"If your external data source requires an authentication, you can set it " -"here. You can leave it empty or choose between *Basic Authentication* or " -"*Authentication Token* (selecting one of the two methods leads to additional " -"fields where you can enter your credentials/token)." +"As every LDAP behaves differently on which attributes and how they are set, " +"Zammad doesn't care about any flags." msgstr "" -"Уколико ваш удаљени извор података захтева аутентификацију, можете је " -"подесити овде. Можете је оставити празном или изабрати између *Basic " -"Authentication* или *Аутентификациони кључ* (одабиром једног од два метода " -"биће приказана додатна поља где можете унети ваше креденцијале/кључ)." - -#: ../system/objects/types.rst:265 -msgid "Search result list key" -msgstr "Кључ листе резулата претраге" +"Како се сваки LDAP понаша другачије на основу тога који атрибути се користе " +"и како су подешени, Zammad неће уважити било какве ознаке." -#: ../system/objects/types.rst:261 +#: ../system/integrations/ldap/manage.rst:37 msgid "" -"Defines the level in the JSON structure which provides the list with search " -"results. You can leave it empty, if the data is already provided as an " -"array. If you have to go deeper in the structure, you can provide a path " -"with ``.`` as separators, e.g. ``key.subkey.sub-sub-key``." +"Users that no longer are returned by your LDAP source will automatically be " +"set to inactive. Zammad assumes that the user was deactivated." msgstr "" -"Одређује ниво у JSON структури који обезбеђује листу резултата претраге. " -"Можете га оставити празним, уколико су подаци већ доступни као низ. Ако " -"желите да идете дубље по структури, можете обезбедити путању са ``.`` као " -"сепаратором, нпр. ``key.subkey.sub-sub-key``." - -#: ../system/objects/types.rst:271 -msgid "Search result value key" -msgstr "Кључ вредности резулата претраге" +"Корисници које ваш LDAP извор више не враћа аутоматски ће бити подешени на " +"неактивне. Zammad претпоставља да је корисник деактивиран." -#: ../system/objects/types.rst:268 +#: ../system/integrations/ldap/manage.rst:41 msgid "" -"Defines the attribute in the structure in which your external data source " -"provides the *value* for your data. An example would be a product *number*. " -"If you have to go deeper in the structure, you can provide a path with ``.`` " -"as separators, e.g. ``key.subkey.sub-sub-key``." +"Users will never be removed automatically! If you want to remove obsolete " +"users, use :doc:`/system/data-privacy`." msgstr "" -"Одређује атрибут у структури у ком ваш удаљени извор података обезбеђује " -"*вредност*. Пример би представљао *број* производа. Уколико желите да идете " -"дубље по структури, можете обезбедити путању са ``.`` као сепаратором, нпр. " -"``key.subkey.sub-sub-key``." +"Корисници никада неће бити аутоматски уклоњени! Ако желите да уклоните " +"застареле кориснике, користите :doc:`захтеве приватности података `." -#: ../system/objects/types.rst:277 -msgid "Search result label key" -msgstr "Кључ ознаке резулата претраге" +#: ../system/integrations/ldap/manage.rst:46 +msgid "Active Directory admins" +msgstr "Active Directory администратори" -#: ../system/objects/types.rst:274 +#: ../system/integrations/ldap/manage.rst:45 msgid "" -"Defines the attribute in the structure in which your external data source " -"provides the *label* for your data. An example would be a product *name*. If " -"you have to go deeper in the structure, you can provide a path with ``.`` as " -"separators, e.g. ``key.subkey.sub-sub-key``." +"Active Directories are quite specific on how to filter for active users only " +"- please see the `Microsoft documentation `_ for more " +"information." msgstr "" -"Одређује атрибут у структури у ком ваш удаљени извор података обезбеђује " -"*ознакз*. Пример би представљао *назив* производа. Уколико желите да идете " -"дубље по структури, можете обезбедити путању са ``.`` као сепаратором, нпр. " -"``key.subkey.sub-sub-key``." +"Active Directories су прилично специфични у погледу филтрирања само за " +"активне кориснике - за више информација погледајте `Microsoft документацију " +"`_." -#: ../system/objects/types.rst:280 +#: ../system/integrations/ldap/manage.rst:51 msgid "" -"In the preview area, you can find the following items (depending on your " -"configuration above):" +"*Do not* manually write pathes of either LDAP attributes or groups. If " +"Zammad does not display them, it either cannot find them or you have a lot " +"of users that don't have the attributes populated." msgstr "" -"У одељку приказа, можете наћи следеће ставке (у зависности од ваших " -"подешавања изнад):" +"*Немојте* ручно писати путање било LDAP атрибута или група. Ако их Zammad не " +"прикаже, или не може да их пронађе или имате много корисника који немају " +"попуњене атрибуте." -#: ../system/objects/types.rst:283 +#: ../system/integrations/ldap/manage.rst:55 msgid "" -"**Error/hint message** (only if configuration is not complete): Zammad tells " -"you, if there is a problem and what you should change in your configuration." +"Zammad will always only return attributes that are filled - this reduces the " +"returned list of attributes greatly." msgstr "" -"**Порука са грешком/упутством** (само ако подешавање није комплетно): Zammad " -"ће вас упутити на то ако постоји проблем и шта треба да промените у вашим " -"подешавањима." +"Zammad ће увек враћати само попуњене атрибуте - ово у великој мери смањује " +"враћену листу атрибута." -#: ../system/objects/types.rst:286 +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing how to add a new LDAP source" +msgstr "Снимак екрана који показује како да додате нови LDAP извор" + +#: ../system/integrations/ldap/manage.rst:63 msgid "" -"**Search field**: search for an existing attribute in the data source to get " -"a preview. This is required for the fields below to show up." +"If your LDAP system doesn't allow anonymous bind, Zammad detects it and " +"provides you an editable \"Base DN\" *text* field instead of a prefilled " +"*select* field." msgstr "" -"**Поље претраге**: претрага за постојећи унос у удаљеном извору у сврху " -"приказа. Ово поље је обавезно да би се поља испод приказала." +"Ако ваш LDAP систем не подржава анонимни приступ, Zammad ће то детектовати и " +"омогућити вам поље *текста* „Основни DN” уместо попуњеног поља *избора*." -#: ../system/objects/types.rst:288 +#: ../system/integrations/ldap/manage.rst:81 +msgid "Review or edit existing source" +msgstr "Прегледајте или уредите постојећи извор" + +#: ../system/integrations/ldap/manage.rst:68 msgid "" -"**Search result response** (only if configuration is not complete): here you " -"can find a syntax highlighted JSON preview of the response, based on the " -"search term you entered." -msgstr "" -"**Одговор резултата претраге** (само ако подешавање није комплетно): овде " -"можете пронаћи JSON приказ одговора у боји, на основу унетих кључних речи за " -"претрагу." +"Clicking on a LDAP source will provide a configuration and mapping overview." +msgstr "Кликом на LDAP извор добићете преглед конфигурације и мапирања." -#: ../system/objects/types.rst:291 +#: ../system/integrations/ldap/manage.rst:70 msgid "" -"**Search result list** (only if *search result list key* is properly set): " -"output of the structure under the configured *search result list key*." +"If needed you can then use the *Change* button to update either the name, " +"active state or the whole configuration. If you're changing the whole " +"configuration, the dialogue will be identical to the source creation." msgstr "" -"**Листа резултата претраге** (само ако *кључ листе резултата претраге* није " -"исправно подешен): део структуре испод подешеног *кључа листе резултата " -"претраге*." +"Ако је потребно, можете користити дугме *Измени* да освежите назив, активно " +"стање или целу конфигурацију. Ако мењате целу конфигурацију, дијалог ће бити " +"идентичан оном приликом додавања извора." -#: ../system/objects/types.rst:294 +#: ../system/integrations/ldap/manage.rst:76 msgid "" -"**Preview table** (when fully configured): Zammad shows you a table which " -"includes the found items based on the search string (value, label and " -"optional link). You can use this preview if you don't have the complete data " -"structure of the external system in mind." +"Did your LDAP server change? Different LDAP servers have different " +"structures and default attributes. This causes the LDAP synchronization to " +"likely fail. Consider removing the affected source and re-add it." msgstr "" -"**Табела приказа** (када је комплетно подешено): Zammad ће вам приказати " -"табелу која укључује нађене уносе на основу кључних речи (вредност, ознаку и " -"опционо линк). Можете користити приказ и када немате потпуну слику о " -"структури података удаљеног система." +"Да ли се ваш LDAP сервер променио? Различити LDAP сервери имају различите " +"структуре и подразумеване атрибуте. Ово може узроковати да LDAP " +"синхронизација не успе. Размислите о брисању дотичног извора и поново га " +"додајте." + +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing the update of the source name." +msgstr "Снимак екрана који приказује освежавање назива извора." + +#: ../system/integrations/ldap/manage.rst:89 +msgid "Re-arrange LDAP source's order" +msgstr "Измените редослед LDAP извора" -#: ../system/objects/types.rst:299 +#: ../system/integrations/ldap/manage.rst:84 msgid "" -"An example of a configured external data source field from agent perspective:" +"You can change the synchronization order for each source at any time. Zammad " +"will synchronize the sources from top to bottom." msgstr "" -"Пример подешеног поља удаљеног извора података из перспективе оператера:" +"Редослед синхронизације за сваки извор можете променити у било ком тренутку. " +"Zammad ће синхронизовати изворе одозго на доле." -#: ../system/objects/types.rst:0 -msgid "Screencast showing the search for a product in a ticket" -msgstr "Снимак екрана који приказује претрагу производа у тикету" +#: ../system/integrations/ldap/manage.rst:0 +msgid "" +"Screencasting showing how to change the source order by using\n" +"drag and drop." +msgstr "" +"Снимак екрана показује како да промените редослед извора коришћењем\n" +"радње превуци и пусти." -#: ../system/objects/types.rst:307 -msgid "URL fields (Link-Template)" -msgstr "URL адреса поља (шаблон везе)" +#: ../system/integrations/ldap/manage.rst:101 +msgid "Remove a source" +msgstr "Брисање извора" -#: ../system/objects/types.rst:311 +#: ../system/integrations/ldap/manage.rst:92 msgid "" -"This function is restricted to Text, Select and External data source types " -"only." +"If you no longer need the a LDAP source or simply want to start over, you " +"can remove them at any time. This will not remove synchronized users, data " +"synchronized or permissions." msgstr "" -"Ова функција је ограничена само на поља текста, избора и удаљеног извора " -"података." +"Ако вам више није потребан LDAP извор или једноставно желите да почнете " +"изнова, можете их обрисати у било ком тренутку. Ова радња неће уклонити " +"синхронизоване кориснике, њихове податке или дозволе." -#: ../system/objects/types.rst:314 +#: ../system/integrations/ldap/manage.rst:98 msgid "" -"Link-Templates are an amazing way to dynamically generate URLs. They allow " -"you to integrate other systems better without having to manually copy data " -"from Zammad if possible." +"Not sure if you'd need the source later on? Set the source to inactive " +"instead of removing it - see *Review or edit existing source* for more." msgstr "" -"Шаблони везе су сјајан начин за динамичко генерисање URL адреса. Омогућавају " -"вам да боље интегришете удаљене системе без да ручно копирате податке из " -"Zammad-а." +"Нисте сигурни да ли ће вам извор требати за касније? Искључите извор уместо " +"да га обришете - погледајте одељак *Прегледајте или уредите постојећи извор* " +"за детаље." -#: ../system/objects/types.rst:320 +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing how to remove LDAP sources." +msgstr "Снимак екрана који показује како обрисати LDAP изворе." + +#: ../system/integrations/pgp/index.rst:2 +msgid "PGP" +msgstr "PGP" + +#: ../system/integrations/pgp/index.rst:7 msgid "" -"Another great way of communicating with another system may be Zammad's :doc:" -"`Webhooks `." +"Pretty Good Privacy (PGP) is another method for secure email communication. " +"With PGP, you can exchange **signed** and **encrypted** messages with others." msgstr "" -"Још један сјајан начин за комуникацију са удаљеним системима могу бити и " -"Zammad-ови :doc:`повратни позиви `." +"Pretty Good Privacy (PGP) је још један метод за безбедну комуникацију путем " +"имејла. Са PGP, можете да размењујете **потписане** и **шифроване** поруке " +"са другима." -#: ../system/objects/types.rst:323 +#: ../system/integrations/pgp/index.rst:13 +#: ../system/integrations/smime/index.rst:17 +msgid "Signing" +msgstr "Потписивање" + +#: ../system/integrations/pgp/index.rst:11 +msgid "is a proof that a message hasn't been manipulated on its way." +msgstr "је доказ да порука није мењана на свом путу." + +#: ../system/integrations/pgp/index.rst:13 msgid "" -"After filling a link-template enabled field, an URL icon will appear on its " -"right. Clicking on the icon opens a new tab." -msgstr "" -"По уносу поља са подешеним шаблоном везе, URL иконица ће се појавити са " -"његове десне стране. Клик на иконицу ће отворити нови језичак." +"In other words, it guarantees message **integrity** and **authenticity**." +msgstr "Другим речима, гарантује **интегритет** и **аутентичност** поруке." -#: ../system/objects/types.rst:328 +#: ../system/integrations/pgp/index.rst:19 +#: ../system/integrations/smime/index.rst:22 +msgid "Encryption" +msgstr "Шифровање" + +#: ../system/integrations/pgp/index.rst:16 +#: ../system/integrations/smime/index.rst:20 msgid "" -"Even though Zammad displays the link template within object edit and create " -"screens, the function is optional. It's only active if you populate the " -"field." +"scrambles a message so that it can only be unscrambled by the intended " +"recipient." msgstr "" -"Иако Zammad приказује подешавање шаблона везе у оквиру дијалога додавања и " -"уређивања објекта, функција је опциона. Биће активна само ако га подесите." +"шифрује поруку тако да може да је дешифрује само прималац коме је намењена." -#: ../system/objects/types.rst:333 +#: ../system/integrations/pgp/index.rst:19 msgid "" -"What's the difference between URL and text fields with link template...?!" -msgstr "Која је разлика између URL и поља текста са шаблоном везе…?!" +"In other words, it guarantees message **privacy** and **data security**." +msgstr "Другим речима, гарантује **приватност** и **безбедност података**." -#: ../system/objects/types.rst:335 -msgid "" -"Both fields have different use cases. Use ``text`` type text fields when " -"ever you have a *static* url that requires dynamic parameters. If you " -"require a drag & drop like field that you can put in any URL, use ``URL`` " -"type text fields." +#: ../system/integrations/pgp/index.rst:25 +msgid "Screenshot of ticket creation with encrypt and sign buttons" msgstr "" -"Оба типа поља имају различите употребну вредност. Користите поље текста типа " -"``text`` кад год имате *статичку* URL адресу која захтева динамичке " -"параметре. Ако захтевате поље у које желите да унесете било коју URL адресу, " -"користите поље текста типа ``URL``." +"Снимак екрана за отварање тикета са дугмићима за шифровање и потписивање" -#: ../system/objects/types.rst:340 +#: ../system/integrations/pgp/index.rst:25 msgid "" -"The difference is easier to spot when comparing the fields directly, below " -"screencast shows the result - the dynamic approach uses existing values in " -"the moment of updating to built the URL - e.g. ``https://google.com/search?" -"q=cookies`` - while the URL approach uses the actual URL of the field - e.g. " -"``https://zammad.com``." +"Once PGP has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " +"appear in the ticket composer." msgstr "" -"Разлика је лакша за приметити када поредите поља једно поред другог, снимак " -"екрана испод приказује резултат – динамички приступ користи постојеће " -"вредности у тренутку освежавања да би генерисао URL – нпр. ``https://google." -"com/search?q=cookies`` – док URL приступ користи дотичну URL адресу поља – " -"нпр. ``https://zammad.com``." +"Када је PGP укључен, дугмићи 🔒 **Шифровање** и ✅ **Потписивање** појавиће " +"се у дијалогу новог тикета." -#: ../system/objects/types.rst:None +#: ../system/integrations/pgp/index.rst:28 +msgid "**Sign button not visible?**" +msgstr "**Дугме за потписивање није видљиво?**" + +#: ../system/integrations/pgp/index.rst:30 msgid "" -"Screencast showing the differents in between URL and text type fields with " -"actual values" +"Please note that the signing of emails is based on the outgoing email " +"account. That means you have to choose a group with a sender email account, " +"which has a private key assigned." msgstr "" -"Снимак екрана који приказује разлику између URL и поља текста са стварним " -"вредностима" +"Имајте на уму да се потписивање имејл порука заснива на налогу одлазне " +"поште. То значи да морате да изаберете групу повезану са имејл адресом " +"пошиљаоца, којој је додељен приватни кључ." -#: ../system/objects/types.rst:352 -msgid "How does this work...?!" -msgstr "Како то уствари функционише?!" +#: ../system/integrations/pgp/index.rst:35 +msgid "Handling of Keys" +msgstr "Руковање кључевима" -#: ../system/objects/types.rst:354 +#: ../system/integrations/pgp/index.rst:36 msgid "" -"As an example, let's say you have an attribute called ``amazing_attribute`` " -"and you want to open a google search directly with the input from that field." +"To use the PGP function, you have to enable the integration (PGP) by " +"switching the toggle to *enabled*." msgstr "" -"Као пример, рецимо да имате објекат под називом ``amazing_attribute`` и " -"желите да отворите страну претраге директно на основу уноса тог поља." +"Да бисте користили PGP функцију, морате да укључите PGP интеграцију " +"пребацивањем прекидача на *укључено*." -#: ../system/objects/types.rst:357 +#: ../system/integrations/pgp/index.rst:39 msgid "" -"Providing the link-template field below allows you to do so: ``https://www." -"google.com/search?q=#{ticket.amazing_attribute}``" +"You can add keys by clicking the *add key* button. The keys can be imported " +"from a file or you can paste the content of the key in the text box." msgstr "" -"Следећа вредност за шаблон везе вам омогућује баш то: ``https://www.google." -"com/search?q=#{ticket.amazing_attribute}``" +"Можете додати кључеве кликом на дугме *додај кључ*. Кључеви се могу увести " +"из датотеке или можете налепити садржај кључа у поље текста." -#: ../system/objects/types.rst:362 +#: ../system/integrations/pgp/index.rst:42 +msgid "**Which keys do I have to import?**" +msgstr "**Које кључеве треба да увезем?**" + +#: ../system/integrations/pgp/index.rst:44 msgid "" -"You can use any :doc:`Zammad variable ` as long as it's " -"available in the moment you need it." +"For **signing** *outgoing* emails, you have to import the private key of " +"your Zammad email account." msgstr "" -"Можете користити било коју :doc:`Zammad променљиву ` све " -"док је доступна у тренутку када вам је неопходна." +"За **потписивање** *одлазних* порука, морате да увезете приватни кључ ваше " +"Zammad имејл адресе." -#: ../system/objects/types.rst:365 +#: ../system/integrations/pgp/index.rst:47 msgid "" -"As a result, you are redirected to Google with a search for the value of the " -"attribute, if you click on the button in the ticket (as you can see in the " -"screencast above)." +"For **encrypting** *outgoing* emails, you have to import the public key of " +"the customer's email account." msgstr "" -"Као резултат, ако кликнете на дугме у тикету (као на снимку екрана изнад) " -"бићете преусмерени на страну претраге за вредност атрибута." - -#: ../system/packages.rst:2 -msgid "Packages" -msgstr "Пакети" - -#: ../system/packages.rst:4 -msgid "That's the package management-area." -msgstr "Ово је одељак за уређивање пакета." - -#: ../system/packages.rst:6 -msgid "Individual add-ons for Zammad can be installed and managed here." -msgstr "Појединални додаци за Zammad се могу инсталирати и уређивати одавде." - -#: ../system/sessions.rst:2 -msgid "Sessions" -msgstr "Сесије" +"За **шифровање** *одлазних* порука, морате да увезете јавни кључ имејл " +"адресе клијента." -#: ../system/sessions.rst:4 +#: ../system/integrations/pgp/index.rst:50 msgid "" -"Sessions management allows reviewing currently known user sessions and " -"allows to end these. The session timeout is affected by :ref:" -"`security_session_timeout` configurations from security settings." +"For **verifying the signature** of signed *incoming* emails, you have to " +"import the public key of the customer." msgstr "" -"Управљање сесијама омогућава преглед тренутно активних корисничких сесија и " -"њихово уклањање. Време истека сесије је под утицајем :ref:" -"`security_session_timeout` подешавања из одељка безбедности." - -#: ../system/sessions.rst:None -msgid "Screenshot showing Zammad's session management" -msgstr "Снимак екрана који приказује уређивање сесија у Zammad-у" - -#: ../system/sessions.rst:13 -msgid "Zammad will provide the following information:" -msgstr "Zammad обезбеђује следеће информације:" +"За **верификацију потписа** потписаних *долазних* порука, морате да увезете " +"јавни кључ имејл адресе клијента." -#: ../system/sessions.rst:16 +#: ../system/integrations/pgp/index.rst:53 msgid "" -"The user account this session entry belongs to. It can be normal if a user " -"has several sessions in the list. This can be due to changed browser " -"information or if you use e.g. single sign on methods where the user does " -"not use the log off button." +"For **decrypting** of encrypted *incoming* emails, you have to import the " +"private key of your Zammad email account." msgstr "" -"Кориснички налог коме припада дотична сесија. Сасвим је нормално да корисник " -"има неколико сесија у листи. До овога може доћи услед промене претраживача " -"или уколико се користи нпр. метод јединствене пријаве и корисник не користи " -"дугме за одјаву." +"За **дешифровање** шифрованих *долазних* порука, морате да увезете приватни " +"кључ ваше Zammad имејл адресе." -#: ../system/sessions.rst:22 -msgid "Browser" -msgstr "Претраживач" +#: ../system/integrations/pgp/index.rst:57 +msgid "Import Keys From a File" +msgstr "Увоз кључева из датотеке" -#: ../system/sessions.rst:22 -msgid "The browser agent communicated to Zammad." -msgstr "Агент претраживача који је пријављен Zammad-у." +#: ../system/integrations/pgp/index.rst:58 +msgid "You can import keys from a file in the section **Upload key**:" +msgstr "Можете да увезете кључ из датотеке у одељку **Отпреми кључ**:" -#: ../system/sessions.rst:40 -msgid "Location" -msgstr "Локација" +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of adding a key via file" +msgstr "Снимак екрана додавања кључа путем датотеке" -#: ../system/sessions.rst:25 +#: ../system/integrations/pgp/index.rst:64 msgid "" -"The anticipated location based on the users IP address. Depending on the IP " -"address the result shown may differ. This option depends on :doc:`/settings/" -"system/services`." +"**Supported file formats:** ASCII-armor as well as binary GPG format " +"(basically any GPG supported key format) is supported here." msgstr "" -"Локација на основу корисничке IP адресе. У зависности од IP адресе резултат " -"се може разликовати. Ова опција зависи од :doc:`/settings/system/services`." +"**Подржани формати кључева:** овде је подржан ASCII armor као и бинарни GPG " +"формат (у основи било који формат кључа који подржава GPG)." -#: ../system/sessions.rst:29 -msgid "The following information can be shown:" -msgstr "Следеће информације могу бити приказане:" +#: ../system/integrations/pgp/index.rst:68 +msgid "Import Keys by Pasting the Content" +msgstr "Увоз кључева налепљивањем текста" -#: ../system/sessions.rst:33 -msgid "IP address" -msgstr "IP адреса" +#: ../system/integrations/pgp/index.rst:69 +msgid "You can also paste the key's content in the section **paste key**:" +msgstr "Такође можете да налепите садржај кључа у одељак **Налепи кључ**:" -#: ../system/sessions.rst:32 +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of adding a key via pasting" +msgstr "Снимак екрана додавања кључа путем налепљивања текста" + +#: ../system/integrations/pgp/index.rst:75 msgid "" -"Either if you set *Geo IP services* to inactive or you're using internal IP " -"address which do not provide location information." +"**Supported format:** Please note that only ASCII-armor is supported here." msgstr "" -"Уколико искључите *сервис географског IP* или ако користите интерну IP " -"адресу која не открива локацију." +"**Подржани формат кључа:** Имајте на уму да је овде подржан само ASCII armor " +"формат." -#: ../system/sessions.rst:40 -msgid "Country (or Country + City)" -msgstr "Држава (или држава + град)" +#: ../system/integrations/pgp/index.rst:78 +msgid "Deleting Keys" +msgstr "Брисање кључева" -#: ../system/sessions.rst:36 +#: ../system/integrations/pgp/index.rst:79 msgid "" -"If *Geo IP services* is enabled only. Depends on how detailed the available " -"IP address information are." +"If you want to delete a specific key, you can do it by clicking on the menu " +"in the *actions* column and select **delete**:" msgstr "" -"Само уколико је *сервис географског IP* укључен. Зависи од тога колико су " -"детаљне доступне информације о IP адреси." - -#: ../system/sessions.rst:39 -msgid "" -"Be aware that results can be inaccurate - this technically is not an error." -msgstr "Обратите пажњу да подаци могу бити нетачни – технички ово није грешка." - -#: ../system/sessions.rst:43 -msgid "Age" -msgstr "Старост" +"Ако желите да избришете одређени кључ, то можете учинити тако што ћете " +"кликнути на мени у колони *радње* и изабрати **избриши**:" -#: ../system/sessions.rst:43 -msgid "Provides the time when the session initially has been created." -msgstr "Обезбеђује време од када је сесија иницијално креирана." +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of deleting a key" +msgstr "Снимак екрана брисања кључа" -#: ../system/sessions.rst:50 -msgid "Update" -msgstr "Освежавање" +#: ../system/integrations/pgp/index.rst:88 +msgid "Downloading Keys" +msgstr "Преузимање кључева" -#: ../system/sessions.rst:46 +#: ../system/integrations/pgp/index.rst:89 msgid "" -"Provides the time the user used this session to open Zammad. This timestamp " -"is only updated if the user e.g. reloads, not during normal work on tickets." +"If you want to download your keys, you can do this as well via corresponding " +"action buttons. Depending on the key, you can choose wether you want to " +"download the private or the public key." msgstr "" -"Обезбеђује време када је корисник користио сесију да приступи Zammad-у. Ова " -"временска вредност ће бити освежена само ако корисник нпр. поново учита " -"апликацију, али не и при стандардном раду на тикетима." +"Ако желите да преузмете своје кључеве, то можете учинити и путем " +"одговарајућих дугмића за радњу. У зависности од врсте кључа, можете изабрати " +"да ли желите да преузмете приватни или јавни кључ." -#: ../system/sessions.rst:50 -msgid "This timestamp is being used for the session timeout." -msgstr "Ова временска вредност се користи за обрачун времена истека сесије." +#: ../system/integrations/pgp/index.rst:95 +#: ../system/integrations/smime/manage-certificates.rst:76 +msgid "Default Behavior" +msgstr "Подразумевано понашање" -#: ../system/sessions.rst:53 +#: ../system/integrations/pgp/index.rst:96 msgid "" -"Use the delete button to remove a single session on behalf of your user." +"Here you can adjust on per group basis, if *sign* and *encryption* is on or " +"off by default. Please be aware, that agents can always override the setting " +"for each individual article." msgstr "" -"Користите дугме за брисање да бисте одјавили појединачну сесију вашег " -"корисника." +"Овде можете да прилагодите по групама, ако су *потписивање* и *шифровање* " +"подразумевано укључени или искључени. Имајте на уму да оператери увек могу " +"преиначити подешавање за сваки појединачни чланак." -#: ../system/subscription/billing.rst:2 -msgid "Billing" -msgstr "Наплата" +#: ../system/integrations/pgp/index.rst:None +msgid "Adjusting default behavior on per group basis" +msgstr "Прилагођавање подразумеваног понашања по групи" -#: ../system/subscription/billing.rst:4 +#: ../system/integrations/pgp/index.rst:107 msgid "" -"Within the billing tab you can control all billing relevant information like " -"invoices, billing address and the option to cancel your subscription." +"Here you can see the last actions regarding signing and encryption and if " +"they were successful." msgstr "" -"У оквиру језичка наплате можете прегледати све релевантне податке као што су " -"рачуни, адреса за наплату и опција за прекид претплате." +"Овде можете видети последње радње у вези са потписивањем и шифровањем и да " +"ли су биле успешне." -#: ../system/subscription/billing.rst:33 -msgid "Billing information" -msgstr "Информације о наплати" +#: ../system/integrations/pgp/index.rst:117 +msgid "**Sign button is not visible, but keys are imported.**" +msgstr "**Дугме за потписивање није видљиво, али су кључеви увезени.**" + +#: ../system/integrations/pgp/index.rst:115 +msgid "Did you choose a group in the ticket?" +msgstr "Да ли сте одабрали групу тикета?" -#: ../system/subscription/billing.rst:8 +#: ../system/integrations/pgp/index.rst:116 msgid "" -"All adjusted billing information below only affect future invoices. If your " -"invoice was issued wrong, please contact `our sales team `_." +"Did you import a private key for the email adress, which is used for " +"outgoing emails in the group?" msgstr "" -"Све измене података наплате испод ће утицати само на будуће рачуне. Ако је " -"издати рачун погрешан, молимо контактирајте `наш тим продаје `_." +"Да ли сте увезли приватни кључ за имејл адресу која се користи за одлазне " +"поруке у групи?" -#: ../system/subscription/billing.rst:14 -msgid "Billing address" -msgstr "Адреса за наплату" +#: ../system/integrations/pgp/index.rst:122 +msgid "**How to obtain keys?**" +msgstr "**Како доћи до кључева?**" -#: ../system/subscription/billing.rst:13 +#: ../system/integrations/pgp/index.rst:120 msgid "" -"Provide your company address here, make sure to include the companies name " -"in case required. This address will be referenced on your invoice." +"You can create them yourself! There are some good tutorials on the web on " +"how to create them. Providing keys to Zammad is a prerequisite to use the " +"PGP feature." msgstr "" -"Овде унесите адресу ваше фирме, али водите рачуна да укључите и назив фирме " -"у случају да је потребно. Ова адреса ће бити укључена у ваш рачун." +"Можете их генерисати сами! Постоји неколико добрих упутстава на интернету о " +"томе како да их креирате. Достава кључева у Zammad је предуслов за коришћење " +"PGP функције." -#: ../system/subscription/billing.rst:18 -msgid "VAT ID" -msgstr "ПДВ број" +#: ../system/integrations/pgp/index.rst:127 +msgid "**It says a passphrase is needed, but I haven't got one.**" +msgstr "**Каже да је потребна лозинка, али ја је немам.**" -#: ../system/subscription/billing.rst:17 +#: ../system/integrations/pgp/index.rst:125 msgid "" -"Provide your VAT ID here. If applicable your invoice will not contain German " -"VAT. Please make sure to pay the VAT in your country as required." +"If the key is secured with a passphrase, you have to provide it for the " +"import in Zammad. It is possible that keys may have an empty passphrase. " +"However, this is *not* recommended." msgstr "" -"Овде унесите ваш ПДВ број (ПИБ). Ако се не односи на вас, рачун неће " -"обрачунати немачки ПДВ. Водите рачуна да платите ПДВ у вашој земљи ако је " -"потребно." +"Ако је кључ обезбеђен лозинком, морате је обезбедити приликом увоза у " +"Zammad. Могуће је да кључеви имају и празну лозинку. Међутим, ово се *не* " +"препоручује." -#: ../system/subscription/billing.rst:27 -msgid "Billing Email Address" -msgstr "Имејл адреса за наплату" +#: ../system/integrations/pgp/index.rst:132 +msgid "**How do my customers get my new key?**" +msgstr "**Како моји клијенти добављају мој нови кључ?**" -#: ../system/subscription/billing.rst:21 +#: ../system/integrations/pgp/index.rst:130 msgid "" -"Usually the instance owner (the person that registered the instance) will " -"receive all emails including the invoices. In case you have your own billing " -"department, you can provide their email address here." +"You have to provide your **public** key in advance. Your customer also has " +"to configure PGP in their email workflow and import your public key. The " +"other way round, you have to get the public key of your customer and have to " +"import it to Zammad." msgstr "" -"Обично ће власник инстанце (особа која је регистровала инстанцу) примити све " -"имејл поруке укључујући и рачуне. У случају да имате посебно одељење за " -"наплату, овде можете унети њихову имејл адресу." +"Морате унапред да им доставите свој **јавни** кључ. Ваш клијент такође мора " +"да подеси PGP у свом имејл окружењу и увезе ваш јавни кључ. Обрнуто, морате " +"да добавите јавни кључ вашег клијента и да га увезете у Zammad." -#: ../system/subscription/billing.rst:25 -msgid "" -"All billing relevant information will then be sent to this email address." -msgstr "" -"Све информације у вези наплате ће убудуће бити послате на ову имејл адресу." +#: ../system/integrations/slack.rst:2 +msgid "Slack" +msgstr "Slack" -#: ../system/subscription/billing.rst:27 -msgid "Invoices are sent as attachment (PDF) to this email address." -msgstr "Рачун се шаљу као прилози (PDF) на ову имејл адресу." +#: ../system/integrations/slack.rst:4 +msgid "**⚠️ Deprecation warning ⚠️**" +msgstr "**⚠️ Упозорење о застаревању ⚠️**" -#: ../system/subscription/billing.rst:29 +#: ../system/integrations/slack.rst:6 msgid "" -"Don't forget to press the *Submit* button after you changed above settings." -msgstr "Не заборавите да кликнете на *Пошаљи* по изменама подешавања изнад." +"Zammad 7 will no longer support this dedicated Slack integration. It is " +"recommended to switch to :doc:`pre-defined webhooks ` instead. Existing Slack integrations should " +"be migrated manually before this feature is dropped." +msgstr "" +"Zammad 7 више неће подржавати ову наменску Slack интеграцију. Препоручује се " +"да се уместо тога пребаците на :doc:`повратне позиве по шаблону `. Постојеће Slack интеграције је " +"потребно ручно мигрирати пре него што се ова функција укине." -#: ../system/subscription/billing.rst:0 +#: ../system/integrations/slack.rst:14 msgid "" -"Screenshot showing options for billing information within the\n" -"subscription menu" +"In order to use this feature, please add a new Slack app to your Workspace. " +"The App you need is called ``Incoming WebHooks`` ." msgstr "" -"Снимак екрана који приказује опције наплате у оквиру\n" -"менија претплате" +"Да бисте користили ову функцију, додајте нову Slack апликацију у своје " +"окружење. Апликација која вам је потребна зове се ``Incoming WebHooks``." -#: ../system/subscription/billing.rst:70 -msgid "Payment history" -msgstr "Историјат плаћања" +#: ../system/integrations/slack.rst:18 +msgid "Why Do I Need This Feature?" +msgstr "Зашто ми треба ова функција?" -#: ../system/subscription/billing.rst:36 +#: ../system/integrations/slack.rst:20 msgid "" -"The payment history will display a history of all paid invoices. At this " -"point you can also download these in case you need them again." +"If you're already using Slack for your team communication, you'll love this " +"feature! Our Slack integration can push ticket notifications about the last " +"ticket article based on the following events:" msgstr "" -"Историјат плаћања приказује евиденцију свих плаћених рачуна. Овде можете " -"преузети рачуне у случају да су вам поново потребни." +"Ако већ користите Slack за комуникацију у оквиру вашег тима, свидеће вам се " +"ова функција! Наша Slack интеграција може да објави обавештења о последњем " +"чланку тикета на основу следећих догађаја:" -#: ../system/subscription/billing.rst:41 -msgid "" -"You will only find *paid* invoices here. Invoices that are to be billed are " -"not available before the payment is completed." -msgstr "" -"Овде ћете наћи само *плаћене* рачуне. Рачуни који још нису плаћени нису " -"доступни." +#: ../system/integrations/slack.rst:24 +msgid "on Ticket creation" +msgstr "при отварању тикета" -#: ../system/subscription/billing.rst:46 -msgid "Date" -msgstr "Датум" +#: ../system/integrations/slack.rst:25 +msgid "on Ticket updates" +msgstr "при освежавању тикета" -#: ../system/subscription/billing.rst:46 -msgid "Date of the invoice creation." -msgstr "Датум издавања рачуна." +#: ../system/integrations/slack.rst:26 +msgid "on reached reminders" +msgstr "по достигнутим подсетницима" -#: ../system/subscription/billing.rst:49 -msgid "Amount" -msgstr "Износ" +#: ../system/integrations/slack.rst:27 +msgid "a Ticket has escalated" +msgstr "по ескалирању тикета" -#: ../system/subscription/billing.rst:49 -msgid "Invoice total including VAT if applicable." -msgstr "Износ рачуна укључујући и ПДВ ако се обрачунава." +#: ../system/integrations/slack.rst:28 +msgid "a Ticket is going to escalate" +msgstr "пре ескалације тикета" -#: ../system/subscription/billing.rst:52 +#: ../system/integrations/slack.rst:30 msgid "" -"Contains contract period (monthly or yearly) and hosted plan for the " -"subscription period in question." +"Zammad will provide the Ticket title, a direct link to the Ticket, the event " +"type (creation, updated, escalation), the customer, time and the last " +"article that has triggered the notification." msgstr "" -"Садржи уговорни период (месечни или годишњи) и хостинг план за дотични " -"период претплате." - -#: ../system/subscription/billing.rst:63 -msgid "Payment method / Service period" -msgstr "Начин плаћања / Уговорни период" +"Zammad ће обезбедити наслов тикета, директан линк до тикета, тип догађаја " +"(отварање, освежавање, ескалација), клијента, време и последњи чланак који " +"је окинуо обавештење." -#: ../system/subscription/billing.rst:56 +#: ../system/integrations/slack.rst:34 msgid "" -"Used bank account or credit card as well as the subscription period the " -"invoice is about." +"This will give you further options, as you can see e.g. escalating tickets " +"that are assigned to an agent that's e.g. absent. You can interact faster, " +"as you might see problems earlier (or even before the problem gets one)." msgstr "" -"Коришћен рачун банке или кредитна картица као и уговорни период рачуна." +"Ово ће вам пружити додатне опције, као што су ескалације тикета које су " +"додељене оператеру који је нпр. одсутан. Можете да комуницирате брже, јер " +"ћете можда раније уочити проблеме (или чак и пре него што се проблем појави)." -#: ../system/subscription/billing.rst:61 +#: ../system/integrations/slack.rst:38 msgid "" -"It might happen that the invoice date and subscription period differ. This " -"is nothing to worry about, the subscription periods will be accounted later " -"on." +"If needed and wanted, you can even discuss directly about the topic before " +"sending an answer to the customer. Another possible use case would be a " +"agent monitoring new agents and their answers to tickets." msgstr "" -"Може се догодити да се датум издавања рачуна и уговорни период разликују. Не " -"брините око овога, уговорни период ће бити обрачунат накнадно." +"Ако је потребно и желите, можете чак и директно да разговарате о теми пре " +"него што пошаљете одговор клијенту. Други могући случај употребе би био да " +"оператер надгледа нове оператере и њихове одговоре на тикете." -#: ../system/subscription/billing.rst:67 -msgid "Receipt" -msgstr "Признаница" +#: ../system/integrations/slack.rst:44 +msgid "Configure the Integration" +msgstr "Конфигуришите интеграцију" -#: ../system/subscription/billing.rst:66 +#: ../system/integrations/slack.rst:46 msgid "" -"Use the arrow to download the invoice in question. You can download all " -"available invoices any time you need to here!" +"First of all, please go to your slack workspace - go to administration => " +"Manage Apps. If you don't have an app yet, you can simply add a new one - " +"just search for ``Incoming WebHooks`` and customize the app to your needs." msgstr "" -"Користите иконицу стрелице за преузимање рачуна. Овде можете преузети све " -"доступне рачуне у било ком тренутку!" - -#: ../system/subscription/billing.rst:0 -msgid "Screenshot showing payment history of a hosted instance" -msgstr "Снимак екрана који приказује историјат плаћања хостоване инстанце" - -#: ../system/subscription/billing.rst:94 -msgid "Do you want to cancel your subscription?" -msgstr "Да ли желите да откажете вашу претплату?" +"Пре свега, у административном панелу вашег окружења идите на Manage Apps. " +"Ако још увек немате апликацију, можете једноставно да додате нову - само " +"потражите ``Incoming WebHooks`` и прилагодите апликацију својим потребама." -#: ../system/subscription/billing.rst:73 +#: ../system/integrations/slack.rst:50 msgid "" -"In case you no longer want to use Zammad's SaaS, you can cancel your " -"subscription by using the red *Yes, please cancel my subscription* button." +"Choose (or create) the channel Zammad should post it's information to and " +"press on \"Add Incoming WebHooks integration\". If you're ready, copy the " +"provided WebHook URL and go to your Zammad installation." msgstr "" -"У случају да не желите више да користите Zammad SaaS, можете отказати своју " -"претплату коришћењем црвеног дугмета *Да, откажите моју претплату*." +"Изаберите (или додајте) канал у ком Zammad треба да објави своје информације " +"и притисните „Add Incoming WebHooks integration“. Ако сте спремни, копирајте " +"наведени WebHook URL и идите на своју Zammad инсталацију." -#: ../system/subscription/billing.rst:76 +#: ../system/integrations/slack.rst:56 msgid "" -"Your subscription will end the day after your trial or billing period ends." +"You need administrative rights on the Slack Workspace. The link to the app " +"directory is normally ``https://[workspace-name].slack.com/apps`` ." msgstr "" -"Ваша претплата ће истећи дан након што се заврше ваш пробни или период " -"наплате." +"Потребна су вам административна права за ваше Slack окружење. Линк на " +"директоријум апликација је обично ``https://[назив-окружења].slack.com/" +"apps``." -#: ../system/subscription/billing.rst:80 +#: ../system/integrations/slack.rst:63 msgid "" -"We will remind you about your cancelled subscription several times up front. " -"After the subscription ended all instance data will be removed. A restore " -"*is not* possible after that point!" +"To configure the slack integration, log in to Zammad and go to Integrations " +"(System) => Slack in the admin panel." msgstr "" -"Обавестићемо вас о отказаној претплати неколико пута. Након престанка " -"претплате сви подаци ваше инстанце ће бити уклоњени. Након овог тренутка " -"*није могуће* вратити податке!" - -#: ../system/subscription/billing.rst:0 -msgid "Screencast showing how to cancel a subscription" -msgstr "Снимак екрана који приказује како отказати претплату" - -#: ../system/subscription/billing.rst:87 -msgid "**😖 Cancelled by accident?**" -msgstr "**😖 Отказали сте грешком?**" +"Да бисте подесили Slack интеграцију, пријавите се у Zammad и идите на " +"Интеграције (Систем) => Slack у панелу администратора." -#: ../system/subscription/billing.rst:89 +#: ../system/integrations/slack.rst:66 msgid "" -"You can always undo the cancellation via the *Yes, undo the cancellation of " -"my subscription* button up to the last subscription day!" +"Here you can choose on what evens Zammad should post information about a " +"ticket to your Slack channel. Next you need to device what groups shall be " +"affected by this, as anybody with access to that specific Slack channel can " +"read at least parts of the ticket this might be a privacy issue, if you " +"select the wrong groups. The username is simply the name that Zammad uses as " +"display name inside the Slack chat. The channel defines the Slack channel " +"the information is being posted in. As last option, you can set a custom " +"icon for posting to slack." msgstr "" -"Увек можете одустати од отказивања путем дугмета *Да, одустани од отказивања " -"моје претплате* све до последњег дана пре истека претплате!" +"Овде можете да изаберете у ком периоду Zammad треба да објави информације о " +"тикету у вашем Slack каналу. Затим, морате одредити на које групе ће ово " +"утицати, јер свако ко има приступ дотичном Slack каналу може да прочита бар " +"делове тикета, што може представљати проблем приватности ако изаберете " +"погрешне групе. Корисничко име је једноставно назив који Zammad користи као " +"име за приказ у Slack порукама. Канал одређује Slack канал у ком ће бити " +"објављене информације. Као последња опција, можете поставити прилагођену " +"иконицу за слање у Slack." -#: ../system/subscription/billing.rst:0 +#: ../system/integrations/slack.rst:74 msgid "" -"Screenshot showing a red button to cancel the subscription\n" -"cancellation" +"When you're ready, just hit \"Submit\" and enable the integration. Zammad " +"will now post new ticket information based on the trigger you chose. Below " +"the options you have the recent log that shows the latest requests to Slack " +"for debugging if needed." msgstr "" -"Снимак екрана који приказује црвено дугме за одустајање од\n" -"отказивања претплате" - -#: ../system/subscription/index.rst:2 -msgid "Subscription (SaaS)" -msgstr "Претплата (SaaS)" +"Када будете спремни, само притисните „Пошаљи“ и укључите интеграцију. Zammad " +"ће од сада објављивати нове информације о тикету на основу окидача који сте " +"изабрали. Испод опција имате недавне уносе евиденције који приказује " +"најновије захтеве упућене Slack-у за помоћ приликом отклањања грешака." -#: ../system/subscription/index.rst:4 +#: ../system/integrations/slack.rst:81 msgid "" -"The subscription settings page allows you to configure your instances " -"package and number of agents required." +"If you leave the Icon URL empty, Zammad will use the Zammad logo instead. " +"The icon should be a square PNG file." msgstr "" -"Страна подешавање претплате вам омогућава да подесите пакет ваше инстанце и " -"неопходан број оператера." +"Ако оставите URL иконице празан, Zammad ће уместо ње користити Zammad лого. " +"Иконица треба да буде квадратна PNG сличица." -#: ../system/subscription/index.rst:9 +#: ../system/integrations/slack.rst:90 msgid "" -"This setting section is only available for Hosted setups. If you're looking " -"for on premise support contracts, please see the `Zammad pricing page " -"`_." +"The following figure shows how it will look if you choose to receive updates " +"on created and updated tickets. On every post Zammad sends to the Slack " +"channel, you can create new threads to discuss about the new article." msgstr "" -"Овај одељак подешавања је доступан само у хостованим инстанцама. Ако тражите " -"уговор за подршку, молимо погледајте `Zammad ценовник `_." +"Следећа слика приказује како изгледа ако одаберете да примате обавештења о " +"отвореним и освеженим тикетима. На сваки пост који Zammad пошаље у Slack " +"канал, можете отворити тему за дискусију о новом чланку." -#: ../system/subscription/index.rst:20 +#: ../system/integrations/slack.rst:96 msgid "" -"The subscription section currently consists of two tabs: Plan & Billing. For " -"your overview we've divided those two tabs into independent sub pages:" +"If you just want to keep track of soon escalating or already escalated " +"tickets, it will look the the following figure. Zammad changes the color in " +"front of the post so you can easily see the state of the ticket." msgstr "" -"Одељак претплате се тренутно састоји од два језичка: План и Наплата. Ради " -"бољег прегледа моделили смо ова два језичка у самосталне странице:" - -#: ../system/subscription/index.rst:25 -msgid ":doc:`💰 Subscription plan `" -msgstr ":doc:`💰 План претплате `" +"Ако само желите да пратите тикете који скоро ескалирају или су већ " +"ескалирали, то ће изгледати као на следећој слици. Zammad мења боју испред " +"поста тако да можете лако да процените стање тикета." -#: ../system/subscription/index.rst:24 +#: ../system/integrations/slack.rst:102 msgid "" -"Everything affecting your instance subscription functions like number of " -"agents, package and payment method." +"If you change the state, Zammad will also put information on what state the " +"ticket gets and (if pending state) the date until it pends. You'll also " +"recognize the color codes in front of posts on slack, as they are exact the " +"same the ticket state colors you'll see in Zammad!" msgstr "" -"Све у вези претплате ваше инстанце као што су број оператера, пакет и начин " -"плаћања." +"Ако промените стање, Zammad ће такође ставити информацију о томе у ком стању " +"је тикет и (ако је на чекању) време чекања тикета. Такође ћете препознати " +"боју стања испред Slack постова, јер су потпуности исте које моћете видети у " +"Zammad-у!" -#: ../system/subscription/index.rst:28 -msgid ":doc:`🧾 Subscription billing `" -msgstr ":doc:`🧾 Наплата претплате `" +#: ../system/integrations/smime/index.rst:2 +msgid "S/MIME" +msgstr "S/MIME" -#: ../system/subscription/index.rst:28 +#: ../system/integrations/smime/index.rst:11 msgid "" -"Everything regarding billing address, invoices and account cancellation." -msgstr "Све у вези адресе за наплату, рачуна и отказивања претплате." - -#: ../system/subscription/index.rst:33 -msgid "FAQ" -msgstr "Често постављана питања" - -#: ../system/subscription/index.rst:37 -msgid "I set up a trial account but am missing functions to test" +"S/MIME is the most widely-supported method for secure email communication. " +"With S/MIME, you can exchange **signed** and **encrypted** messages with " +"others." msgstr "" -"Регистровао сам пробни налог али немам приступ неким функцијама за тестирање" +"S/MIME је најшире подржани метод за безбедну комуникацију путем имејла. Са S/" +"MIME, можете да размењујете **потписане** и **шифроване** поруке са другима." -#: ../system/subscription/index.rst:36 +#: ../system/integrations/smime/index.rst:15 msgid "" -"The trial instance is running within the professional package allowing up to " -"three agents." -msgstr "" -"Пробна инстанца ради у оквиру Professional пакета и дозвољава до три " -"оператера." - -#: ../system/subscription/index.rst:40 -msgid "Can I change package within the trial?" -msgstr "Да ли могу да променим пакет у оквиру пробног периода?" - -#: ../system/subscription/index.rst:40 -msgid "No. As soon as the package is changed the subscription begins." -msgstr "Не. По промени пакета започеће претплата." - -#: ../system/subscription/index.rst:45 -msgid "What happens to my trial instance after the trial period ended?" -msgstr "Шта се дешава са мојом пробном инстанцом након пробног периода?" +"is proof that a message hasn't been tampered with or sent by an impersonator." +msgstr "је доказ да порука није мењана или послата од стране имитатора." -#: ../system/subscription/index.rst:43 +#: ../system/integrations/smime/index.rst:17 msgid "" -"Your instance will automatically be canceled for you. Please see *What " -"happens to my instance after it has been canceled?* for more." -msgstr "" -"Ваша инстанца ће бити аутоматски отказана. Молимо погледајте *Шта се дешава " -"са мојом инстанцом по отказивању?* за више детаља." - -#: ../system/subscription/index.rst:58 -msgid "What happens to my instance after it has been canceled?" -msgstr "Шта се дешава са мојом инстанцом по отказивању?" +"In other words, it guarantees a message's **integrity** and **authenticity**." +msgstr "Другим речима, гарантује **интегритет** и **аутентичност** поруке." -#: ../system/subscription/index.rst:48 -msgid "That depends slightly on your instance state:" -msgstr "Ово зависи од стања ваше инстанце:" +#: ../system/integrations/smime/index.rst:22 +msgid "In other words, it guarantees **privacy** and **data security**." +msgstr "Другим речима, гарантује **приватност** и **безбедност података**." -#: ../system/subscription/index.rst:54 -msgid "Trial instance" -msgstr "Пробна инстанца" +#: ../system/integrations/smime/index.rst:28 +msgid "Screencast demo of S/MIME features for both new tickets and replies" +msgstr "Снимак екрана са S/MIME функцијом за нове тикете и одговоре" -#: ../system/subscription/index.rst:51 +#: ../system/integrations/smime/index.rst:28 msgid "" -"If you're still on trial, we will ice your instance and remind you once " -"again about your instance. We then will wait some days and remove your " -"instance from our system. This is the last time we will inform you by Email." +"Once S/MIME has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " +"appear in the ticket composer." msgstr "" -"Ако сте још увек у пробном периоду, замрзнућемо вашу инстанцу и подсетити " -"вас још једанпут. Онда ћемо сачекати пар дана и уклонити вашу инстанцу из " -"нашег система. Након овога ћемо вас обавестити путем имејла последњи пут." +"Када се S/MIME укључи, дугмићи 🔒 **Шифровање** и ✅ **Потписивање** " +"појавиће се у дијалогу новог тикета." -#: ../system/subscription/index.rst:58 -msgid "Paid instance" -msgstr "Плаћена инстанца" +#: ../system/integrations/smime/index.rst:32 +msgid ":doc:`🔪 Prerequisites `" +msgstr ":doc:`🔪 Предуслови `" -#: ../system/subscription/index.rst:57 +#: ../system/integrations/smime/index.rst:31 msgid "" -"If you're a paying customer and canceled your subscription, the instance " -"removal will take place the day after your last subscription day." +"New to S/MIME? This section helps you to find certificate providers and " +"points out Limitations." msgstr "" -"Ако сте плаћали и откажете вашу претплату, уклањање инстанце ће започети " -"један дан након истека ваше претплате." - -#: ../system/subscription/index.rst:60 -msgid "Can removed instances be restored?" -msgstr "Да ли се уклоњене инстанце могу вратити?" +"Нови сте у S/MIME свету? Овај одељак вам помаже да пронађете провајдере " +"сертификата и указује на постојећа ограничења." -#: ../system/subscription/index.rst:61 -msgid "No. Once your instance has been removed, a restoration is not possible." -msgstr "Не. По уклањању ваше инстанце, враћање података више није могуће." +#: ../system/integrations/smime/index.rst:35 +msgid ":doc:`📝 Manage Certificates `" +msgstr ":doc:`📝 Управљање сертификатима `" -#: ../system/subscription/plan.rst:2 ../system/subscription/plan.rst:38 -msgid "Plan" -msgstr "План" +#: ../system/integrations/smime/index.rst:35 +msgid "Add and download certificates; configure group default behaviors." +msgstr "" +"Додајте и преузмите сертификате; подесите подразумевано понашање група." -#: ../system/subscription/plan.rst:16 -msgid "Subscription" -msgstr "Претплата" +#: ../system/integrations/smime/index.rst:38 +msgid ":doc:`😦 Troubleshooting `" +msgstr ":doc:`😦 Решавање проблема `" -#: ../system/subscription/plan.rst:5 -msgid "" -"On the top of the subscription summary you'll find the number of used and " -"available (booked) agent seats. By using the *see more* link you can also " -"expand an agent list to see the currently configured active agents. This " -"list *does not* count accounts with admin permissions only." +#: ../system/integrations/smime/index.rst:38 +msgid "Took a wrong turn? About recent logs and common issues." msgstr "" -"Изнад прегледа претплате наћи ћете број коришћених и доступних (купљених) " -"налога оператера. Коришћењем линка *прикажи више* такође можете увећати " -"листу оператера да видите тренутно подешене, активне оператере. Ова листа " -"*не укључује* налоге само са дозволама администратора." +"Погрешно сте скренули код Албукеркија? О недавним уносима евиденције и " +"уобичајеним проблемима." -#: ../system/subscription/plan.rst:0 +#: ../system/integrations/smime/index.rst:43 msgid "" -"Within subscription you can always see how many agents are still\n" -"available to add and who uses the seats." +"For more details on how S/MIME integration works on the agent side, see the :" +"user-docs:`user docs `." msgstr "" -"У оквиру претплате увек можете проверити колико оператера је још\n" -"увек достпуно и ко користи налоге." +"За више детаља о томе како S/MIME интеграција функционише на страни " +"оператера, погледајте :user-docs:`корисничку документацију `." -#: ../system/subscription/plan.rst:14 -msgid "" -"Learn more on how to manage your agents in general :doc:`here `." -msgstr "" -"Сазнајте више о начину управљања вашим оператерима :doc:`овде `." +#: ../system/integrations/smime/manage-certificates.rst:2 +msgid "Manage Certificates" +msgstr "Управљање сертификатима" -#: ../system/subscription/plan.rst:19 +#: ../system/integrations/smime/manage-certificates.rst:4 msgid "" -"This section gives you an overview of the available plans and their " -"functions / limits. If you require a more detailed table, check our " -"`detailed pricing table `_ for more." +"S/MIME is **disabled by default**. Enable it to start adding certificates." msgstr "" -"Овај одељак вам даје преглед доступним планова и њихових функција / " -"ограничења. Уколико су вам потребне детаљније информације, погледајте наш " -"`детаљну табелу ценовника `." +"S/MIME је **подразумевано искључен**. Укључите га да бисте почели да " +"додајете сертификате." + +#: ../system/integrations/smime/manage-certificates.rst:10 +msgid "Dialogue to add new certificates or private keys" +msgstr "Дијалог за додавање нових сертификата или тајних кључева" -#: ../system/subscription/plan.rst:23 +#: ../system/integrations/smime/manage-certificates.rst:10 msgid "" -"Your selection in this step will decide on the base agent price and e.g. " -"agent limits that might apply in the summary step." +"Manage certificates in the Admin Panel under **System > Integrations > S/" +"MIME**. Certificates may be pasted in as plain text or uploaded from a file." msgstr "" -"Ваш избор у овом кораку ће одредити основну цену оператера и нпр. ограничења " -"оператера која су приказана у прегледу." +"Управљање сертификатима се обавља у административном панелу под **Систем > " +"Интеграције > S/MIME**. Сертификати се могу налепити као обичан текст или " +"отпремити из датотеке." + +#: ../system/integrations/smime/manage-certificates.rst:14 +msgid "Add Certificate Data" +msgstr "Додавање података о сертификату" + +#: ../system/integrations/smime/manage-certificates.rst:36 +msgid "Add Certificate" +msgstr "Додај сертификат" -#: ../system/subscription/plan.rst:26 +#: ../system/integrations/smime/manage-certificates.rst:17 msgid "" -"The green *Selected* button will also tell you what plan you're currently in." -msgstr "Зелено дугме *изабрано* ће вам такође рећи на ком сте тренутно плану." +"Import public-key certificates for both your own organization and your " +"contacts." +msgstr "Увезите јавни сертификат и за своју организацију и за своје контакте." -#: ../system/subscription/plan.rst:30 +#: ../system/integrations/smime/manage-certificates.rst:19 msgid "" -"Trial instances are running at Professional with 3 agents. The plan cannot " -"be changed during the trial for technical reasons, if you require more " -"agents for testing, please contact `our sales team `_ with a reason for the raise request." +"You can also add a bunch of certificates in one go by providing a single " +"file with all relevant certificates." msgstr "" -"Пробне инстанце раде под Professional пакетом са 3 оператера. План није " -"могуће променити током пробног периода из техничких разлога, ако вам је " -"неопходно више оператера за тестирање, молимо контактирајте `наш тим продаје " -"`_ са разлогом за увећање." +"Такође можете додати више сертификата одједном тако што ћете обезбедити " +"једну датотеку са свим релевантним сертификатима." + +#: ../system/integrations/smime/manage-certificates.rst:22 +msgid "🕵️ **ALWAYS verify certificates in-person or over the phone!**" +msgstr "🕵 ** УВЕК проверите добијене сертификате лично или телефоном!**" -#: ../system/subscription/plan.rst:0 +#: ../system/integrations/smime/manage-certificates.rst:24 msgid "" -"Screenshot showing three available packages for a hosted Zammad\n" -"instance" +"The whole point of signatures is to alert you when someone is trying to " +"pretend to be someone they're not. Never accept a certificate from someone " +"online without verifying it first." msgstr "" -"Снимак екрана приказује три доступна пакета хостованих Zammad\n" -"инстанци" +"Читава поента потписа је да вас упозори ако неко покушава да се преставља " +"као нека друга особа. Никада не прихватајте сертификат од некога на мрежи, а " +"да га претходно нисте проверили." -#: ../system/subscription/plan.rst:83 -msgid "Summary" -msgstr "Преглед" +#: ../system/integrations/smime/manage-certificates.rst:28 +msgid "📇 **What about trusted certificate authorities?**" +msgstr "📇 **А шта са поузданим органима за сертификацију?**" -#: ../system/subscription/plan.rst:41 +#: ../system/integrations/smime/manage-certificates.rst:30 msgid "" -"In this section you can adjust the settings of the previous selected plan." -msgstr "У овом одељку можете подесити подешавања претходно изабраног плана." +"In some cases (e.g. when dealing with large enterprises), you may be given a " +"certificate for an entire CA, rather than a single contact. Add it here to " +"trust *all* certificates issued by that CA." +msgstr "" +"У неким случајевима (нпр. када имате посла са великим предузећима), можда " +"ћете добити CA сертификат, а не само за један контакт. Додајте га овде да " +"бисте убудуће веровали *свим* сертификатима које је издао тај CA." -#: ../system/subscription/plan.rst:45 +#: ../system/integrations/smime/manage-certificates.rst:35 msgid "" -"Note that upgrading (more agents, higher package) is always possible, " -"however, downgrading will only happen when your billing period renews." +"Commercial CAs can usually be verified online. Zammad does not include a " +"list of built-in, trusted CAs." msgstr "" -"Обратите пажњу да је унапређење (више оператера, скупљи пакет) увек могуће, " -"док је повратак назад могућ само при обнављању вашег уговорног периода." +"Комерцијални CA се обично могу проверити путем мреже. Zammad не садржи " +"уграђене CA сертификате." + +#: ../system/integrations/smime/manage-certificates.rst:57 +msgid "Add Private Key" +msgstr "Додавање тајног кључа" -#: ../system/subscription/plan.rst:49 +#: ../system/integrations/smime/manage-certificates.rst:39 msgid "" -"Upgrading resets your billing period and existing credit will be deducted " -"from the new total." +"Once you've added a public-key certificate, you can import its matching " +"private key." msgstr "" -"Унапређење ће ресетовати ваш уговорни период и цена ће бити умањена за " -"тренутни износ." - -#: ../system/subscription/plan.rst:58 -msgid "Billing cycle" -msgstr "Обрачунски период" +"Када додате јавни сертификат, можете да увезете и његов одговарајући тајни " +"кључ." -#: ../system/subscription/plan.rst:53 +#: ../system/integrations/smime/manage-certificates.rst:42 msgid "" -"You can choose between either monthly or yearly billing. The price per agent " -"will be cheaper if you decide for yearly billing." +"Private keys are for **your own organization only**; never ask your contacts " +"for their private keys." msgstr "" -"Увек можете одабрати између месечне и годишње наплате. Цена по оператеру је " -"нижа ако се одлучите за годишњу наплату." +"Тајни кључеви су за **само вашу организацију**; никада не питајте своје " +"контакте за њихове приватне кључеве." -#: ../system/subscription/plan.rst:56 +#: ../system/integrations/smime/manage-certificates.rst:0 msgid "" -"If you're still trying out things and are unsure of the right package for " -"your instance, you may want to choose monthly first and then upgrade to " -"yearly when you're sure." +"S/MIME integration showing configured certificates and possible issues with " +"Logging" msgstr "" -"Ако још увек испробавате ствари и нисте сигурни који је пакет најбољи за " -"вашу инстанцу, можда ћете желети да прво одаберете месечну наплату и после " -"унапредите на годишњу када будете сигурни." +"S/MIME интеграција која приказује подешене сертификате и могуће проблеме у " +"евиденцији" -#: ../system/subscription/plan.rst:66 -msgid "Plan: (Starter|Professional|Plus) - Agents" -msgstr "План: (Starter|Professional|Plus) - Оператери" +#: ../system/integrations/smime/manage-certificates.rst:50 +msgid "" +"A note is displayed on certificates with a matching private key (see line 2)." +msgstr "" +"На сертификатима са одговарајућим тајним кључем приказана је напомена " +"(погледајте други ред)." -#: ../system/subscription/plan.rst:61 -msgid "Choose the number of agents you require for your instance." -msgstr "Одаберите број оператера који су вам неопходни у вашој инстанци." +#: ../system/integrations/smime/manage-certificates.rst:52 +msgid "📤 **Certificates and private keys must be uploaded separately.**" +msgstr "" +"📤 **Сертификати и тајни кључеви морају да се увезу одвојено једни од других." +"**" -#: ../system/subscription/plan.rst:63 +#: ../system/integrations/smime/manage-certificates.rst:54 msgid "" -"Keep in mind that some packages may have agent limits. Depending on the " -"previous chosen package, you won't be able to exceed specific agent numbers. " -"Also note that setting less agents than currently configured is not possible." +"If your certificate and private key are bundled together in the same file or " +"PEM block, import it twice (once using each button)." msgstr "" -"Обратите пажњу да неки пакети имају ограничење у броју оператера. У " -"зависности од претходно одабраног пакета, нећете бити у могућности да " -"прекорачите одређени број оператера. Такође имајте на уму да избор броја " -"оператера нижи од подешеног није могућ." +"Ако су ваш сертификат и тајни кључ комбиновани у исту датотеку или PEM " +"блоку, увезите их два пута (по једном користећи свако дугме)." -#: ../system/subscription/plan.rst:69 -msgid "Total" -msgstr "Укупно" +#: ../system/integrations/smime/manage-certificates.rst:57 +msgid "Please note that bulk imports of private keys are not possible." +msgstr "Имајте на уму да масовна радња увоза тајних кључева није могућа." -#: ../system/subscription/plan.rst:69 -msgid "This will be the net total you're going to be billed." -msgstr "Ово представља укупну нето цифру која ће вам бити наплаћена." +#: ../system/integrations/smime/manage-certificates.rst:60 +msgid "Download Certificate Data" +msgstr "Преузмите податке о сертификату" -#: ../system/subscription/plan.rst:71 +#: ../system/integrations/smime/manage-certificates.rst:62 msgid "" -"By using the *Update subscription* button, the instance package will be " -"adjusted immediately. If you didn't provide a payment method yet, Zammad " -"will request you to provide one at this point." +"You can download the earlier provided certificates and private keys at any " +"time from your Zammad instance." msgstr "" -"Коришћењем дугмета *Освежите претплату*, пакет инстанце ће бити моментално " -"измењен. Уколико још увек нисте додали начин плаћања, Zammad ће захтевати да " -"га обезбедите у овом тренутку." +"Можете преузети раније достављене сертификате и тајне кључеве у било ком " +"тренутку из своје Zammad инстанце." -#: ../system/subscription/plan.rst:77 +#: ../system/integrations/smime/manage-certificates.rst:65 msgid "" -"In case you're still within the trial period, this means that the trial will " -"be over immediately!" -msgstr "" -"У случају да сте још увек у оквиру пробног периода, ово значи да ће пробни " -"период одмах бити завршен!" - -#: ../system/subscription/plan.rst:80 -msgid "Down- or upgrading during the trial period *is not* possible." +"Please note that passphrase-protected private keys stay protected and when " +"you download them, you have to know the passphrase to use them after " +"downloading." msgstr "" -"Враћање на претходни пакет или унапређење пакета током пробном периода *није " -"могуће*." - -#: ../system/subscription/plan.rst:0 -msgid "Screenshot showing payment options and a pricing summary" -msgstr "Снимак екрана који приказује начине плаћања и преглед цена" - -#: ../system/subscription/plan.rst:99 -msgid "Payment method" -msgstr "Начин плаћања" +"Обратите пажњу да тајни кључеви заштићени лозинком остају заштићени и када " +"их преузмете, мораћете да знате лозинку да бисте их користили по преузимању." -#: ../system/subscription/plan.rst:86 -msgid "You can pay via credit card or SEPA mandate." -msgstr "Моћете платити уз помоћ кредитне картице или SEPA налога." +#: ../system/integrations/smime/manage-certificates.rst:73 +msgid "Dialogue to download certificates or private keys" +msgstr "Дијалог за преузимање сертификата или тајних кључева" -#: ../system/subscription/plan.rst:91 -msgid "Credit card" -msgstr "Кредитна картица" +#: ../system/integrations/smime/manage-certificates.rst:73 +msgid "Download stored certificates and their keys" +msgstr "Преузмите сачуване сертификате и њихове кључеве" -#: ../system/subscription/plan.rst:89 +#: ../system/integrations/smime/manage-certificates.rst:78 msgid "" -"Simply follow the dialogue by clicking *authorize* and confirm -if required " -"by your bank- your consent to Zammad using your card for the payments." +"The ticket composer will set all outgoing messages to **signed and " +"encrypted** by default (assuming the required certificates exist)." msgstr "" -"Једноставно пратите упутства кликом на *ауторизуј* и потврдите – уколико је " -"неопходно преко ваше банке – вашу сагласност са тим да Zammad користи вашу " -"картицу за наплату." +"Дијалог новог тикета ће укључити **потписивање и шифровање** за све одлазне " +"поруке по подразумеваној вредности (под претпоставком да одговарајући " +"сертификати постоје)." -#: ../system/subscription/plan.rst:95 -msgid "SEPA" -msgstr "SEPA" +#: ../system/integrations/smime/manage-certificates.rst:82 +msgid "These defaults can be modified on a per-group basis:" +msgstr "Ове подразумеване вредности могу да се мењају на основу групе:" -#: ../system/subscription/plan.rst:94 -msgid "" -"Provide the requested information of the bank account holder and update if " -"you're ready. You'll then receive an email with the SEPA mandate." -msgstr "" -"Обезбедите захтеване податке о држаоцу рачуна и освежите их ако сте спремни. " -"Након тога примићете имејл са SEPA налогом." +#: ../system/integrations/smime/manage-certificates.rst:None +msgid "Zammad allowing to choose the default behavior on per group basis" +msgstr "Zammad омогућава подешавање подразумеваног понашања по одабраној групи" -#: ../system/subscription/plan.rst:97 +#: ../system/integrations/smime/manage-certificates.rst:89 msgid "" -"Technically there's also the possibility to pay via invoice, however - this " -"method only applies to a fairly low number of instances. Please contact `our " -"sales team `_ for more information." +"Of course, agents can always manually change these settings on each email " +"they send out." msgstr "" -"Технички гледано постоји и могућност наплате путем фактуре, међутим – овај " -"начин се односи само на мали број инстанци. Молимо контактирајте `наш тим " -"продаје `_ за више информација." +"Наравно, оператери увек могу ручно да преиначе ова подешавања за сваку имејл " +"поруку коју пошаљу." -#: ../system/translations.rst:2 -msgid "Translations" -msgstr "Преводи" +#: ../system/integrations/smime/prerequisites.rst:4 +msgid "A certificate *and* private key for your own organization" +msgstr "Сертификат *и* тајни кључ за вашу организацију" -#: ../system/translations.rst:4 +#: ../system/integrations/smime/prerequisites.rst:6 msgid "" -"Translations of Zammad are processed centrally in our `Weblate instance " -"`_. This allows non-developers to review " -"and update translation texts of the language they actually speak." +"(Use this to ✒️ **sign outgoing messages** and 🔓 **decrypt incoming " +"messages**.)" msgstr "" -"Преводи за Zammad се прикупљају централно путем наше `Weblate инстанце " -"`_. Ово омогућава и особама које нису " -"вичне програмирању да прегледају и освеже текстове превода за језик којим " -"говоре." +"(Користите опцију ✒ за **потписивање одлазних порука** и 🔓за **дешифровање " +"долазних порука**.)" -#: ../system/translations.rst:9 +#: ../system/integrations/smime/prerequisites.rst:9 msgid "" -"Your language is in an incomplete translation state or has typos? Please " -"consider helping us in sorting this out! All you need is either a GitHub " -"account or to register directly in our instance." +"Certificates belonging your contacts, or their issuing certificate authority " +"(CA)" msgstr "" -"Ваш језик има некомплетан превод или има грешке? Молимо узмите у обзир да " -"нам помогнете са овим! Све што вам је неопходно је или GitHub налог или " -"директна регистрација на нашој инстанци." +"Сертификати који припадају вашим контактима или њиховим органима за издавање " +"сертификата (CA)" -#: ../system/translations.rst:13 +#: ../system/integrations/smime/prerequisites.rst:11 msgid "" -"Did you know? This is also where the documentation translations are handled. " -"🤓" +"(Use these to ✅ **verify incoming message signatures** and 🔒 **encrypt " +"outgoing messages**.)" msgstr "" -"Да ли сте знали? Ово је место где се прикупљају и преводи за документацију. " -"🤓" +"(Користите опцију ✅ да **верификујете потписе долазних порука** и 🔒 да " +"**шифрујете одлазне поруке**.)" -#: ../system/translations.rst:15 +#: ../system/integrations/smime/prerequisites.rst:14 +msgid "🙋 **I'm new to S/MIME. Where can I get a certificate?**" +msgstr "🙋 **Нов сам у S/MIME свету. Где могу набавити сертификат?**" + +#: ../system/integrations/smime/prerequisites.rst:16 msgid "" -"Have a look in our :docs:`contribution section ` in the system documentation to get started!" +"The easiest way to get certificates is to buy an annual subscription through " +"a commercial CA, such as:" msgstr "" -"Погледајте наш :docs:`одељак о преводима ` у системској документацији за прве кораке!" - -#: ../system/translations.rst:20 -msgid "Local Translations" -msgstr "Локални преводи" +"Најлакши начин да набавите сертификате је да купите годишњу претплату преко " +"комерцијалног CA, као што су:" -#: ../system/translations.rst:22 +#: ../system/integrations/smime/prerequisites.rst:19 msgid "" -"Apart from these system translations, there's still local translations you " -"can manage. This is relevant if you added custom objects that require " -"translations or even custom states and priorities." +"`Sectigo (formerly Comodo) `_" msgstr "" -"Осим ових системских превода, постоје и локални преводи којима можете " -"управљати. Ово се односи и ако сте додали прилагођене објекте који захтевају " -"преводе па чак и прилагођена стања и приоритети." - -#: ../system/translations.rst:None -msgid "Translation management screen within the admin menu" -msgstr "Страна управљања преводима у оквиру администраторског панела" +"`Sectigo (раније Comodo) `_" -#: ../system/translations.rst:31 -msgid "Updating Translations" -msgstr "Освежавање превода" +#: ../system/integrations/smime/prerequisites.rst:20 +msgid "`Secorio `_" +msgstr "`Secorio `_" -#: ../system/translations.rst:33 -msgid "" -"Because of how Zammad ships translations, the only way to update the system " -"translations is to update your Zammad installation. The benefit of this is " -"that you no longer need internet access during a Zammad upgrade as the " -"package has everything it requires already." -msgstr "" -"С обзиром на начин на који Zammad обезбеђује преводе, једини начин да " -"освежите системске преводе је да ажурирате вашу Zammad инсталацију. Једна од " -"користи овог приступа да вам више није неопходан приступ интернету током " -"ажурирању Zammad-а јер пакет садржи све што је потребно." +#: ../system/integrations/smime/prerequisites.rst:21 +msgid "`GlobalSign `_" +msgstr "`GlobalSign `_" -#: ../system/translations.rst:39 -msgid "Translation of Custom Objects" -msgstr "Превод прилагођених објеката" +#: ../system/integrations/smime/prerequisites.rst:23 +msgid "(Zammad is not affiliated with these CAs in any way.)" +msgstr "(Zammad није ни на који начин повезан са овим CA органима.)" -#: ../system/translations.rst:41 +#: ../system/integrations/smime/prerequisites.rst:25 msgid "" -"No problem at all! You can customize any translation locally, even if it is " -"not initially provided by the system." +"You can also generate your own self-signed certificates, but the process is " +"complicated and usually 🙅 **involves extra work for your contacts**." msgstr "" -"Нема проблема! Можете прилагодити било који локални превод, чак иако " -"иницијално није дошао са системом." +"Такође можете да генеришете сопствене самопотписане сертификате, али процес " +"је компликован и обично 🙅 **укључује додатни посао за ваше контакте**." -#: ../system/translations.rst:44 +#: ../system/integrations/smime/prerequisites.rst:29 msgid "" -"Translation is supported for a broad number of features, including but not " -"limited to custom:" -msgstr "Преводи су подржани у већем броју функција, укључујући и:" - -#: ../system/translations.rst:47 -msgid "Object Attributes" -msgstr "Атрибути објеката" - -#: ../system/translations.rst:48 -msgid "Ticket Macros" -msgstr "Макрои тикета" - -#: ../system/translations.rst:49 -msgid "Ticket Overviews" -msgstr "Прегледи тикета" - -#: ../system/translations.rst:50 -msgid "Ticket Priorities" -msgstr "Приоритети тикета" - -#: ../system/translations.rst:51 -msgid "Ticket States" -msgstr "Стања тикета" +"Bear in mind that 🤝 **S/MIME only works if the other party is using it, too." +"**" +msgstr "" +"Имајте на уму да 🤝 **S/MIME функционише само ако га користи и друга страна." +"**" -#: ../system/translations.rst:54 -msgid "Customizing Translations" -msgstr "Прилагођавање превода" +#: ../system/integrations/smime/prerequisites.rst:32 +msgid "Certificate and Private Key Checks on Upload" +msgstr "Провере сертификата и тајног кључа при отпремању" -#: ../system/translations.rst:56 +#: ../system/integrations/smime/prerequisites.rst:34 msgid "" -"Within the translation screen, simply click on the **New Translation** " -"button." +"The certificate and public key validation is based on the ``X509v3`` " +"extensions." msgstr "" -"На страници за управљање превода, једноставно кликните на зелено дугме " -"**Нови превод**." +"Провера сертификата и јавног кључа је заснована на ``X509v3`` екстензијама." -#: ../system/translations.rst:None -msgid "New translation dialog" -msgstr "Дијалог новог превода" +#: ../system/integrations/smime/prerequisites.rst:49 +msgid "Uploading a *client certificate*?" +msgstr "Отпремате *сертификат клијента*?" -#: ../system/translations.rst:62 -msgid "" -"In the dialog you can immediately enter the exact translation source (if you " -"know it) and your custom translation text for it and click **Submit**." -msgstr "" -"У дијалогу можете директно унети тачан изворни превод (ако га знате) и ваш " -"прилагођени текст превода за њега а потом кликните на **Пошаљи**." +#: ../system/integrations/smime/prerequisites.rst:41 +msgid "The following attributes are required then:" +msgstr "Следећи атрибути су тада обавезни:" -#: ../system/translations.rst:65 -msgid "" -"Alternatively, try to search for translation suggestions in the list below. " -"Selecting an item from the list will pre-fill the translation source for you " -"and then you can just enter your custom translation." +#: ../system/integrations/smime/prerequisites.rst:39 +msgid "Subject Alternative Name (at least one email address has to be present)" msgstr "" -"Алтернативно, покушајте да претражујете листу предлога за превод испод. " -"Одабир ставке са листе ће попунити изворни превод за вас и онда можете унети " -"само ваш прилагођени превод." +"Subject Alternative Name (мора бити присутна најмање једна имејл адреса)" -#: ../system/translations.rst:69 -msgid "" -"The target language will always default to your current language selection. " -"If you need to translate for a different language, simply change the " -"selection before submitting." -msgstr "" -"Циљни језик ће увек подразумевано бити постављен на ваш тренутни језик " -"провила. Уколико вам треба превод за други језик, једноставно га одаберите " -"из селекције пре слања." +#: ../system/integrations/smime/prerequisites.rst:40 +msgid "Key Usage (``Digital Signature`` and/or ``Key Encipherment``)" +msgstr "Key Usage (``Digital Signature`` и/или ``Key Encipherment``)" -#: ../system/translations.rst:73 +#: ../system/integrations/smime/prerequisites.rst:41 +msgid "Public key algorithm (either ``RSA`` or ``EC``)" +msgstr "Public key algorithm (или ``RSA`` или ``EC``)" + +#: ../system/integrations/smime/prerequisites.rst:43 msgid "" -"All your custom translations will show up in the overview table when added. " -"And they will even persist across Zammad updates!" +"The Extended Key Usage attribute is optional. If the certificate provides " +"the named attribute, than it must contain the value ``E-mail Protection``." msgstr "" -"Сви ваши прилагођени преводи ће бити приказани у табели прегледа по " -"додавању. Чак ће преживети и ажурирање Zammad-а!" +"Атрибут Extended Key Usage је опционалан. Ако сертификат садржи дотични " +"атрибут, онда мора да садржи вредност ``E-mail Protection``." -#: ../system/translations.rst:76 +#: ../system/integrations/smime/prerequisites.rst:46 msgid "" -"Make sure to reload your browser if a translated string is not displayed." -msgstr "Уколико текст превода не буде приказан, освежите ваш претраживач." +"Please note that any usable email adress has to be prefixed with ``email:`` " +"or ``rfc822:``." +msgstr "" +"Имајте на уму да свака употребљива имејл адреса мора имати префикс ``email:" +"`` или ``rfc822:``." -#: ../system/translations.rst:80 -msgid "Reverting to Original Translations" -msgstr "Повратак на оригиналне преводе" +#: ../system/integrations/smime/prerequisites.rst:49 +msgid "The named public key algorithms are mandatory for private keys as well." +msgstr "Именовани алгоритми јавног кључа су обавезни и за тајне кључеве." -#: ../system/translations.rst:82 +#: ../system/integrations/smime/prerequisites.rst:54 +msgid "Uploading a *CA certificate*?" +msgstr "Отпремате *CA сертификат*?" + +#: ../system/integrations/smime/prerequisites.rst:52 msgid "" -"If you want to revert a custom translation to original text, simply use the " -"appropriate action within the row of the overview table." +"In the case of an uploaded CA certificate, providing the value ``CA:TRUE`` " +"in the attribute *Basic Contstraints*, the previously mentioned attributes " +"are not verified." msgstr "" -"Уколико желите да се вратите прилагођени превод на оригинални текст, " -"једноставно користите одговарајућу акцију из реда табеле прегледа." +"У случају када отпремљени CA сертификат има вредност ``CA:TRUE`` за *Basic " +"Contstraints* атрибут, претходно излистани атрибути неће бити проверени." -#: ../system/translations.rst:85 +#: ../system/integrations/smime/prerequisites.rst:56 msgid "" -"Depending on the type of the translation source, the action has a slightly " -"different name:" +"In general, the usage of any expired (``Not After``) or not yet valid (``Not " +"Before``) certificate is denied for outgoing emails." msgstr "" -"Зависно од типа изворног превода, радња може имати мало другачији назив:" - -#: ../system/translations.rst:88 -msgid "**Reset** for customized system translations" -msgstr "**Поништи** за прилагођене системске преводе" +"Уопштено говорећи, употреба сертификата који је истекао (``Not After``) или " +"још увек није важећи (``Not Before``) биће онемогућена за одлазне имејл " +"поруке." -#: ../system/translations.rst:89 -msgid "**Remove** for customized local translations" -msgstr "**Уклони** за прилагођене локалне преводе" +#: ../system/integrations/smime/prerequisites.rst:59 +msgid "Example certificate:" +msgstr "Пример сертификата:" -#: ../system/translations.rst:91 +#: ../system/integrations/smime/prerequisites.rst:85 msgid "" -"In both cases, the action will remove the customized translation after a " -"confirmation." -msgstr "У сваком случају, радња ће избрисати прилагођени превод по потврди." +"Please note that Zammad will distrust senders by default. This means that " +"you're always required to provide certificate data, no matter if for signing " +"or encrypting." +msgstr "" +"Имајте на уму да Zammad подразумевано неће веровати пошиљаоцима. То значи да " +"се од вас увек тражи да обезбедите податке сертификата, без обзира да ли за " +"потписивање или шифровање." -#: ../system/translations.rst:None -msgid "Screenshot showing the location of the Remove action" -msgstr "Снимак екрана који приказује позицију радње Уклони" +#: ../system/integrations/smime/prerequisites.rst:89 +msgid "This is by design and can't be adjusted." +msgstr "Ово је по пројекту и не може се променити." -#: ../system/translations.rst:99 -msgid "Inline Translations" -msgstr "Непосредни преводи" +#: ../system/integrations/smime/troubleshooting.rst:4 +msgid "" +"All of the system's latest S/MIME activity is displayed in the **Recent " +"Logs** section." +msgstr "" +"Све најновије S/MIME активности система су приказане у одељку **Недавни " +"уноси евиденције**." -#: ../system/translations.rst:101 +#: ../system/integrations/smime/troubleshooting.rst:11 +msgid "Sample entries of in- and outgoing S/MIME related emails." +msgstr "Примери уноса долазних и одлазних S/MIME имејл порука." + +#: ../system/integrations/smime/troubleshooting.rst:11 msgid "" -"If you prefer a more hands-on approach, you can activate the inline or on-" -"screen translation feature by pressing ``ctrl`` + ``alt`` + ``t`` at any " -"time and on any screen." +"Logs report the status and details of all mail, both incoming and outgoing, " +"that used signing/verification or encryption/decryption." msgstr "" -"Уколико вам је дражи практичнији приступ, можете укључити непосредне преводе " -"односно функцију превода на екрану притиском на ``ctrl`` + ``alt`` + ``t`` у " -"било ком тренутку и на било којој страници." +"Евиденција извештава о статусу и детаљима свих порука, како долазних тако и " +"одлазних, које су користиле функције потписивања/верификације или шифровања/" +"дешифровања." -#: ../system/translations.rst:105 +#: ../system/integrations/smime/troubleshooting.rst:14 msgid "" -"All customizable translation texts will be highlighted for you on the " -"screen. Just click into the highlighted area and update the text in place." +"This log does **not** include email sent by :doc:`triggers ` or the :doc:`scheduler `. For those, check your " +"``production.log``." msgstr "" -"Сви преводи који се могу прилагодити ће бити означени на екрану. Само " -"кликните на означену површину и освежите текст на жељену вредност." +"Ова евиденција **не** укључује имејл поруке које шаљу :doc:`окидачи ` и :doc:`планери `. За њих, проверите своју " +"``production.log`` датотеку." -#: ../system/translations.rst:None -msgid "Inline translation mode activated for the Overview screen" -msgstr "Непосредни преводи укључени на екрану прегледа" +#: ../system/integrations/smime/troubleshooting.rst:20 +msgid "Common Issues" +msgstr "Уобичајени проблеми" -#: ../system/translations.rst:112 -msgid "" -"When finished editing, simply press ``ctrl`` + ``alt`` + ``t`` again to " -"deactivate." +#: ../system/integrations/smime/troubleshooting.rst:30 +msgid "I received a signed/encrypted email before I set up S/MIME integration" msgstr "" -"По завршетку уређивања, једноставно притисните ``ctrl`` + ``alt`` + ``t`` " -"поново за искључивање." +"Добио сам потписану/шифровану имејл поруку пре него што је подешена S/MIME " +"интеграција" -#: ../system/translations.rst:117 +#: ../system/integrations/smime/troubleshooting.rst:23 msgid "" -"Even though it's available on any screen, the inline translation feature " -"requires admin permissions. It works only for the current language " -"selection. If you need to translate a different language, first change the " -"language in your :user-docs:`profile settings `." +"No problem. Once S/MIME has been enabled and the appropriate certificates " +"have been added, agents will be prompted to retry verification/decryption on " +"matching emails." msgstr "" -"Иако су доступни за сваку страницу, непосредни преводи захтевају " -"администраторске дозволе. Функционишу само за тренутни одабир језика. Ако " -"желите да преведете на други језик, прво промените језик у вашим :user-docs:" -"`подешавањима профила ." +"Нема проблема. Када се S/MIME укључи и додају одговарајући сертификати, " +"оператерима ће бити пружена опција да поново покушају верификују/дешифрују " +"одговарајуће поруке." -#: ../system/variables.rst:2 -msgid "Variables" -msgstr "Променљиве" +#: ../system/integrations/smime/troubleshooting.rst:0 +msgid "Screenshot of user prompt to retry decryption" +msgstr "Снимак екрана корисничке функције за поновни покушај дешифровања" + +#: ../system/integrations/smime/troubleshooting.rst:38 +msgid "The 🔒 **Encrypt** button is disabled" +msgstr "Дугме 🔒 **Шифровање** је онемогућено" + +#: ../system/integrations/smime/troubleshooting.rst:33 +msgid "Have you added the recipient's certificate?" +msgstr "Да ли сте додали сертификат примаоца?" + +#: ../system/integrations/smime/troubleshooting.rst:34 +msgid "Are you sure the recipient's certificate is valid?" +msgstr "Да ли сте сигурни да је сертификат примаоца важећи?" + +#: ../system/integrations/smime/troubleshooting.rst:35 +msgid "Have you checked your ``production.log`` for more details?" +msgstr "Да ли сте проверили своју ``production.log`` датотеку за више детаља?" -#: ../system/variables.rst:4 +#: ../system/integrations/smime/troubleshooting.rst:37 msgid "" -"Please note that this is just an overview of available variables. It might " -"be incomplete or variables might not be available within some functions. If " -"you're missing variables or are not sure if something is not working as " -"expected, feel free to ask over at the `Community `_." +"If encryption doesn't work in the composer, it won't work in :doc:`triggers " +"` or the :doc:`scheduler ` either!" msgstr "" -"ОБратите пажњу да је ово само преглед доступних променљивих. Може бити " -"некомплетан или променљиве можда нису доступне унутар неких функција. Ако " -"вам зафале променљиве или нисте сигурни да ли раде на очекиван начин, " -"слободно питајте на `Community форуму `_." +"Ако шифровање не функционише приликом слања, неће радити ни у :doc:" +"`окидачима ` и :doc:`планерима `!" + +#: ../system/integrations/smime/troubleshooting.rst:42 +msgid "The ✅ **Sign** button is disabled" +msgstr "Дугме ✅ **Потписивање** је онемогућено" -#: ../system/variables.rst:10 +#: ../system/integrations/smime/troubleshooting.rst:41 msgid "" -"Variables can be called by typing ``::`` (just like text modules in the " -"frontend), as long as you're in a supported text field within the backend. " -"Zammad will display all variables being available within this context and " -"replace it to the variable as soon as you selected an entry." -msgstr "" -"Променљиве могу бити излистане уносом ``::`` (баш као и текстуални исечци у " -"корисничком интерфејсу), све док сте у оквиру подржаног поља уноса. Zammad " -"ће приказати све доступне променљиве у овом контексту и заменити у тексту " -"чим их одаберете." +"Have you added **both the certificate and private key** for your " +"organization?" +msgstr "Да ли сте додали **и сертификат и тајни кључ** за своју организацију?" -#: ../system/variables.rst:15 +#: ../system/integrations/smime/troubleshooting.rst:42 msgid "" -"You have an empty field which you referenced and it appears as ``-``? That's " -"currently working as designed - you might want to ensure that these fields " -"always have a value." +"Does the email address on the certificate match the email address of the " +"agent/group composing the email?" msgstr "" -"Референцирате на празно поље и приказује се као ``-``? Ово је очекивано " -"понашање – пробајте да обезбедите да ова поља увек имају вредност." +"Да ли се имејл адреса сертификата подудара са имејл адресом оператера/групе " +"која саставља поруку?" -#: ../system/variables.rst:20 -msgid "Variable Categories" -msgstr "Категорије променљивих" +#: ../system/integrations/smime/troubleshooting.rst:45 +msgid "Error: “Fingerprint already taken”" +msgstr "Грешка: „Fingerprint already taken“" -#: ../system/variables.rst:31 -msgid "Wait, What About Custom Objects?" -msgstr "Чекај, а шта са прилагођеним објектима?" +#: ../system/integrations/smime/troubleshooting.rst:45 +msgid "Are you sure you haven't added this certificate already?" +msgstr "Јесте ли сигурни да већ нисте додали овај сертификат?" -#: ../system/variables.rst:33 -msgid "" -"Good point! Of course, we can't predict what objects you might create, but " -"we can give you a hint on how to put the puzzle together to get your custom " -"values." +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Error: “❌ invalid byte sequence in UTF-8”" +msgstr "Грешка: „❌ invalid byte sequence in UTF-8“" + +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Please ensure to provide PEM formatted certificate and keys." +msgstr "Обавезно обезбедите сертификат и кључеве у PEM формату." + +#: ../system/integrations/smime/troubleshooting.rst:49 +msgid "Did you check if the provided file is a valid certificate or key?" msgstr "" -"У праву сте! Наравно, не можемо предвидети које објекте ћете користити, али " -"можемо вам указати на то како да их уклопите и дођете до својих прилагођених " -"вредности." +"Да ли сте проверили да ли дата датотека садржи важећи сертификат или кључ?" -#: ../system/variables.rst:36 +#: ../system/integrations/zabbix.rst:2 +msgid "Zabbix Integration" +msgstr "Zabbix интеграција" + +#: ../system/integrations/zabbix.rst:5 msgid "" -"For this, we'll talk about the inner part of the variable (so everything " -"within ``#{}``), please put the outer part around to have a valid variable. " -"The first part of the variable name consist of the object type. Currently " -"these are:" +"This guide describes how to integrate your Zabbix 5.4 installation with " +"Zammad using the Zabbix webhook feature. This guide will provide " +"instructions on setting up a media type, a user and an action in Zabbix." msgstr "" -"У ову сврху, образложићемо унутрашњи део променљиве (значи све у оквиру ``#{}" -"``), молимо заградите их да бисте добили исправну променљиву. Први део " -"назива променљиве се састоји од типа објекта. Тренутно, ово укључује:" +"Овај водич описује како да интегришете своју Zabbix 5.4 инсталацију са " +"Zammad-ом користећи Zabbix повратне позиве. Овај водич ће пружити упутства " +"за подешавање врсте медија, корисника и радње у Zabbix-у." -#: ../system/variables.rst:41 -msgid "Ticket (``ticket``)" -msgstr "Тикет (``ticket``)" +#: ../system/integrations/zabbix.rst:12 +msgid "Zammad with enabled HTTP Token Authentication" +msgstr "Zammad са укљученом аутентификацијом путем HTTP кључа" -#: ../system/variables.rst:42 -msgid "User (``user``)" -msgstr "Корисник (``user``)" +#: ../system/integrations/zabbix.rst:13 +msgid "Zabbix version 5.4 or higher" +msgstr "Zabbix верзија 5.4 или новија" + +#: ../system/integrations/zabbix.rst:16 +msgid "Setting up a Zammad" +msgstr "Подешавање Zammad-а" + +#: ../system/integrations/zabbix.rst:18 +msgid "Enable **API Token Access** in Settings > System > API." +msgstr "Омогућите **Приступ API путем кључа** у Подешавања > Систем > API." + +#: ../system/integrations/zabbix.rst:20 +msgid "" +"Create a **new user** for a Zabbix alerter with an **email address** and " +"create a personal user token with **ticket.agent** permissions." +msgstr "" +"Направите **новог корисника** за Zabbix упозорења са **имејл адресом** и " +"додајте лични кључ за приступ са дозволом **ticket.agent**." -#: ../system/variables.rst:43 -msgid "Organization (``organization``)" -msgstr "Организација (``organization``)" +#: ../system/integrations/zabbix.rst:24 +msgid "Zabbix Webhook Configuration" +msgstr "Конфигурација повратног позива за Zabbix" -#: ../system/variables.rst:44 -msgid "Group (``group``)" -msgstr "Група (``group``)" +#: ../system/integrations/zabbix.rst:27 +msgid "Create a Global Macro" +msgstr "Направите глобални макро" -#: ../system/variables.rst:46 +#: ../system/integrations/zabbix.rst:29 msgid "" -"The second part is the name of the object. This is the name you define " -"during object creation and can be found within the object menu at any time. " -"The first and second part of a variable is divided by a point, e.g.: " -"``ticket.number`` which will in total be ``#{ticket.number}``." +"Before setting up the **Webhook**, you need to setup the global macro " +"**{$ZABBIX.URL}**, which must contain the **URL** to the **Zabbix frontend**." msgstr "" -"Други део је назив објекта. Ово је назив који одређујете током додавања " -"објекта и можете га видети у било ком тренутку унутар панела објекта. Први и " -"други део променљиве су одвојени тачком, нпр.: ``ticket.number`` што на " -"крају резултује у ``#{ticket.number}``." +"Пре него што подесите **Webhook**, морате да подесите глобални макро " +"**{$ZABBIX.URL}**, који мора да садржи **URL адресу** на **Zabbix кориснички " +"интерфејс**." -#: ../system/variables.rst:51 +#: ../system/integrations/zabbix.rst:33 msgid "" -"Now, in some situations it's possible that you'll need to use a third part. " -"The best example for such a situation would be a ``select`` or ``tree-" -"select`` field which will by default return the key value, not it's display " -"name. For this, just extend your variable with ``.value``. This will result " -"in ``#{ticket.select.value}``." -msgstr "" -"У неким ситуацијама, можда ће вам бити неопходан и трећи део. Најбољи пример " -"за ову ситацију је ``select`` или ``tree-select`` поље које подразумевано " -"враћа вредност кључа, а не назив за приказ. Да бисте приступили овој " -"вредности, само продужите вашу променљиву са ``.value``. Ово ће резултовати " -"у ``#{ticket.select.value}``." +"In the **Administration** > **Media types** section, import the `Template`_." +msgstr "У одељку **Administration** > **Media types** увезите `Template`_." -#: ../system/variables.rst:60 -msgid "Using Translated Variables" -msgstr "Коришћење преведених променљивих" +#: ../system/integrations/zabbix.rst:38 +msgid "Open the added **Zammad** media type and set:" +msgstr "Отворите додату врсту медија **Zammad-** и подесите:" -#: ../system/variables.rst:62 -msgid "" -"If you want to use a translated variable in triggers or schedulers, you can " -"extend the placeholder like this: ``#{t(ticket.state.name)}``. The ``t`` " -"tells Zammad to search for fitting translated strings. The used output " -"language is based on the system language of Zammad which you can set in the " -"admin panel under :doc:`/settings/branding` or based on the selected locale " -"in the trigger/scheduler edit dialog." -msgstr "" -"Ако желите да користите преведене променљиве у окидачима или планеерима, " -"можете проширити поље променљиве на следећи начин: ``#{t(ticket.state.name)}" -"``. Функција ``t`` ће потражити међу одговарајућим преводима. Циљни језик је " -"базиран на основу системског језика Zammad-а који можете подесити у панелу " -"администратора под :doc:`брендингом ` или на основу " -"одабраног језика у дијалогу окидача/планера." +#: ../system/integrations/zabbix.rst:40 +msgid "**zammad\\_access\\_token** to the your **Personal User Token**" +msgstr "**zammad\\_access\\_token** на ваш **лични кључ за приступ**" -#: ../system/variables.rst:69 +#: ../system/integrations/zabbix.rst:41 msgid "" -"A possible use-case: you want to send your customers updates on tickets via " -"trigger or scheduler which should include the state of the ticket. Using the " -"default ``#{ticket.state.name}`` (without the translation flag ``t()``) " -"would lead to the output of the original (english) name of the state." +"**zammad\\_url** to the **frontend URL** of your **Zammad** installation" msgstr "" -"Могући случај употребе: ако желите да пошаљете својим клијентима обавештења " -"о тикетима путем окидача или планера која укључују и стање тикета. Коришћење " -"подразумеване променљиве `#{ticket.state.name}`` (без функције превода " -"``t()``) ће резултовати у вредности назива стања на оригиналном (енглеском) " -"језику." +"**zammad\\_url** на **URL адресу корисничког интерфејса** ваше инсталације " +"**Zammad-а**" -#: ../system/variables.rst:75 -msgid "Date and Time Formatting" -msgstr "Форматирање датума и времена" +#: ../system/integrations/zabbix.rst:43 +msgid "**zammad\\_customer** to your **Zammad user email**." +msgstr "**zammad\\_customer** на вашу **Zammad корисничку имејл адресу**." -#: ../system/variables.rst:77 +#: ../system/integrations/zabbix.rst:44 msgid "" -"The system (trigger/scheduler selected) locale and timezone predefines a " -"default format of date and timestamp. This format is customizable by using " -"the ``dt()`` method." +"**zammad\\_enable\\_tags** to **true** or **false** to enable or disable " +"trigger tags. **Important**: if you enable tag support, each tag is set with " +"a separate request." msgstr "" -"Језик и временска зона система одређују подразумевани формат датума и " -"времена. Овај формат може бити прилагођен коришћењем ``dt()``функције." - -#: ../system/variables.rst:79 -msgid "The method arguments are as follows:" -msgstr "Параметри функције су следећи:" +"**zammad\\_enable\\_tags** на **true** или **false** да бисте укључили или " +"искључили ознаке окидача. **Важно**: ако укључите подршку за ознаке, свака " +"ознака се поставља посебним захтевом." -#: ../system/variables.rst:81 -msgid "The date or timestamp variable you want to format." -msgstr "Променљива датума или временске ознаке коју желите да форматирате." +#: ../system/integrations/zabbix.rst:48 +msgid "" +"If you want to prioritize issues according to **severity** values in Zabbix, " +"you can define mapping parameters:" +msgstr "" +"Ако желите да дате приоритет проблемима према вредностима **severity** " +"атрибута у Zabbix-у, можете да дефинишете параметре мапирања:" -#: ../system/variables.rst:82 -msgid "The output format string." -msgstr "Формаз излазног низа текста." +#: ../system/integrations/zabbix.rst:51 +msgid "**severity\\_**: Zammad priority ID" +msgstr "**severity\\_<назив>**: ID Zammad приоритета" -#: ../system/variables.rst:83 -msgid "The timezone to apply (optional)." -msgstr "Временска зона за примену (необавезно)." +#: ../system/integrations/zabbix.rst:53 +msgid "Click the **Update** button to save the **Webhook** settings." +msgstr "Кликните на дугме **Update** да бисте сачували **Webhook** подешавања." -#: ../system/variables.rst:86 +#: ../system/integrations/zabbix.rst:55 msgid "" -"``#{dt(ticket.updated_at, \"%A %Y-%m-%d %H:%M in the office\", \"Europe/" -"Berlin\")}``" +"To receive notifications in **Zammad**, you need to create a **Zabbix user** " +"and add **Media** with the **Zammad** type." msgstr "" -"``#{dt(ticket.updated_at, \"%A %Y-%m-%d %H:%M у канцеларији\", \"Europe/" -"Berlin\")}``" - -#: ../system/variables.rst:87 -msgid "Monday, 2024-03-18 15:31 in the office" -msgstr "Понедељак, 2024-03-18 15:31 у канцеларији" +"Да бисте примали обавештења у **Zammad-у**, потребно је да направите " +"**Zabbix корисника** и додате **Media** са типом **Zammad**." -#: ../system/variables.rst:89 +#: ../system/integrations/zabbix.rst:58 msgid "" -"If you want to use our example, make sure to paste the string above without " -"formatting (``CTRL+Shift+v``), otherwise it won't work." +"For **Send to**: enter any text, as this value is not used, but is required." msgstr "" -"Уколико желите да користите наш пример, обавезно налепите текст изнад без " -"формата (``Ctrl+Shift+v``), у супротном неће успети." - -#: ../system/variables.rst:93 -msgid "The following table lists available format directives:" -msgstr "Следећа табела приказује доступне директиве формата:" - -#: ../system/variables.rst:99 -msgid "Parameter" -msgstr "Параметар" +"За **Send to**: унесите било који текст, јер се ова вредност не користи, али " +"је обавезна." -#: ../system/variables.rst:102 -msgid "``%Y``" -msgstr "``%Y``" +#: ../system/integrations/zabbix.rst:61 +msgid "" +"For more information, use the `Zabbix documentation `_." +msgstr "" +"За више информација, погледајте `Zabbix документацију `_." -#: ../system/variables.rst:103 -msgid "Year with 4 digits" -msgstr "Година са 4 цифре" +#: ../system/maintenance.rst:2 +msgid "Maintenance" +msgstr "Одржавање" -#: ../system/variables.rst:104 -msgid "Use ``%y`` for year with 2 digits" -msgstr "Користите ``%y`` за годину са 2 цифре" +#: ../system/maintenance.rst:4 +msgid "" +"Zammad comes with a maintenance mode that you can use for e.g. updating the " +"instance or changing settings while restricting availability and functions." +msgstr "" +"Zammad долази са режимом одржавања који можете користити за нпр. ажурирање " +"инстанце или промену подешавања уз ограничавање доступности функција." -#: ../system/variables.rst:105 -msgid "``%m``" -msgstr "``%m``" +#: ../system/maintenance.rst:13 +msgid "Mode" +msgstr "Режим" -#: ../system/variables.rst:106 -msgid "Month of year (as number with zero-padding)" -msgstr "Месец године (као број са допуном нула)" +#: ../system/maintenance.rst:8 +msgid "The mode setting allows you to enable or disable the maintenance mode." +msgstr "" +"Подешавање режима вам омогућава да укључите или искључите режим одржавања." -#: ../system/variables.rst:107 -msgid "Use ``%-m`` for month without zero-padding" -msgstr "Користите ``%-m`` за месец без допуне нула" +#: ../system/maintenance.rst:10 +msgid "Defaults to *off*." +msgstr "Подразумевано је *искључено*." -#: ../system/variables.rst:108 -msgid "``%d``" -msgstr "``%d``" +#: ../system/maintenance.rst:12 +msgid "" +"The maintenance mode will restrict access to administrative roles only. This " +"means agents and customers are logged off." +msgstr "" +"Режим одржавања ће ограничити приступ само улози администратора. То значи да " +"су оператери и клијенти одјављени." -#: ../system/variables.rst:109 -msgid "Day of month (as number with zero-padding)" -msgstr "Дан месеца (као број са допуном нула)" +#: ../system/maintenance.rst:23 +msgid "@Login" +msgstr "@Пријави се" -#: ../system/variables.rst:110 -msgid "Use ``%e`` for day without zero-padding" -msgstr "Користите ``%e`` за дан без допуне нула" +#: ../system/maintenance.rst:16 +msgid "" +"This setting allows you to provide a login message within a green banner " +"above the login screen. Click into the green banner in the settings page to " +"adjust your message. To activate the message, activate the *@Login* setting." +msgstr "" +"Ово подешавање вам омогућава да одредите пријавну поруку у оквиру зеленог " +"банера изнад екрана за пријаву. Кликните на зелени банер на страници са " +"подешавањима да бисте прилагодили своју поруку. Да бисте активирали поруку, " +"укључите подешавање *@Пријави се*." -#: ../system/variables.rst:111 -msgid "``%H``" -msgstr "``%H``" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing the default login message within the\n" +"settings page" +msgstr "" +"Снимак екрана који приказује подразумевану пријавну поруку у оквиру\n" +"странице са подешавањима" -#: ../system/variables.rst:112 -msgid "Hour of day in 24h notation with zero-padding" -msgstr "Час дана у 24-часовном формату са допуном нула" +#: ../system/maintenance.rst:26 +msgid "" +"Send an informative message to **all active sessions**. This comes handy to " +"inform your agents e.g. about mayor outages or to force reloads after " +"configuration changes." +msgstr "" +"Пошаљите информативну поруку **свим активним сесијама**. Ово је згодно да " +"обавестите своје оператере, нпр. о дужим прекидима рада или о обавезном " +"поновном учитавању апликације након измена конфигурације." -#: ../system/variables.rst:113 -msgid "Use ``%k`` for hour without zero-padding" -msgstr "Користите ``%k`` за час без допуне нула" +#: ../system/maintenance.rst:31 +msgid "This is the messages title (slightly bigger than the normal message)." +msgstr "Ово је наслов поруке (мало већи фонт од остатка текста)." -#: ../system/variables.rst:114 -msgid "``%I``" -msgstr "``%I``" +#: ../system/maintenance.rst:34 +msgid "The text you want to provide to your logged in sessions." +msgstr "Текст који желите да пошаљете својим пријављеним сесијама." -#: ../system/variables.rst:115 -msgid "Hour of day in 12h notation with zero-padding" -msgstr "Час дана у 12-часовном формату са допуном нула" +#: ../system/maintenance.rst:39 +msgid "Reload application" +msgstr "Освежи апликацију" -#: ../system/variables.rst:116 +#: ../system/maintenance.rst:37 msgid "" -"Use ``%l`` for hour without zero-padding and ``%p`` / ``%P`` for meridian " -"indicator" +"Selecting this option will change the message acceptance button from *Close* " +"(with nothing happening) to *Continue session*, which forces the application " +"to reload." msgstr "" -"Користите ``%l`` за час без допуне нула и ``%p`` / ``%P`` за индикатор " -"меридијана" - -#: ../system/variables.rst:117 -msgid "``%M``" -msgstr "``%M``" +"Избор ове опције промениће дугме за прихватање поруке из *Затвори* (без " +"икакве функције) у *Настави сесију*, што приморава апликацију да се поново " +"учита." -#: ../system/variables.rst:118 -msgid "Minute of hour" -msgstr "Минут часа" +#: ../system/maintenance.rst:43 +msgid "" +"If you have customers that are logged in to Zammad, they'll also be notified " +"if they're active in that moment." +msgstr "" +"Ако имате клијенте који су пријављени у Zammad, они ће такође бити " +"обавештени уколико су активни у том тренутку." -#: ../system/variables.rst:120 -msgid "``%S``" -msgstr "``%S``" +#: ../system/maintenance.rst:48 +msgid "Example without reload application" +msgstr "Пример без поновног учитавања апликације" -#: ../system/variables.rst:121 -msgid "Second of Minute" -msgstr "Секунда минута" +#: ../system/maintenance.rst:52 +msgid "" +"Message setting within Zammad's admin settings without ticket reload " +"application setting." +msgstr "" +"Подешавање поруке у оквиру Zammad-ових подешавања администратора без " +"поновног учитавања апликације." -#: ../system/variables.rst:123 -msgid "``%A``" -msgstr "``%A``" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing the send message settings without ticket\n" +"reload application set" +msgstr "" +"Снимак екрана који приказује подешавање слања поруке без\n" +"поновног учитавања апликације" -#: ../system/variables.rst:124 -msgid "Weekday name" -msgstr "Назив дана у недељи" +#: ../system/maintenance.rst:61 ../system/maintenance.rst:85 +msgid "" +"The modal all other active sessions will see upon pressing *Send to clients*." +msgstr "" +"Дијалог ће све остале активне сесије видети чим притиснете *Пошаљи " +"клијентима*." -#: ../system/variables.rst:125 -msgid "Use ``%a`` for abbreviated name or ``%^A`` for uppercase name" -msgstr "Користите ``%a`` за скраћеницу или ``%^A`` за велика слова" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing modal caused by maintenance's message\n" +"without reload application ticket" +msgstr "" +"Снимак екрана који приказује дијалог изазван поруком одржавања\n" +"без поновног учитавања апликације" -#: ../system/variables.rst:126 -msgid "``%B``" -msgstr "``%B``" +#: ../system/maintenance.rst:72 +msgid "Example with reload application" +msgstr "Пример са поновним учитавањем апликације" -#: ../system/variables.rst:127 -msgid "Month name" -msgstr "Назив месеца" +#: ../system/maintenance.rst:76 +msgid "" +"Message setting within Zammad's admin settings with ticket reload " +"application setting." +msgstr "" +"Подешавање поруке у оквиру Zammad-ових подешавања администратора са поновним " +"учитавањем апликације." -#: ../system/variables.rst:128 -msgid "Use ``%b`` for abbreviated name" -msgstr "Користите ``%b`` за скраћеницу" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing the send message settings with ticket\n" +"reload application set" +msgstr "" +"Снимак екрана који приказује подешавање слања поруке са\n" +"поновним учитавањем апликације" -#: ../system/variables.rst:129 -msgid "``%U``" -msgstr "``%U``" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing modal caused by maintenance's message\n" +"with reload application ticket" +msgstr "" +"Снимак екрана који приказује дијалог изазван поруком одржавања\n" +"са поновним учитавањем апликације" -#: ../system/variables.rst:130 -msgid "Week number of current year" -msgstr "Број недеље у текућој години" +#: ../system/monitoring.rst:2 +msgid "Monitoring" +msgstr "Надгледање" -#: ../system/variables.rst:131 -msgid "Use ``%W`` for a different calculation method" -msgstr "Користите ``%W`` за другачији обрачун" +#: ../system/monitoring.rst:4 +msgid "" +"This function is only available in self hosted instances. If you use Zammad " +"in our cloud, we are monitoring the system on our own and take steps to fix " +"potential problems directly." +msgstr "" +"Ова функција је доступна само у инстанцама које сами хостујете. Ако " +"користите Zammad у нашем окружењу, ми сами надгледамо систем и предузимамо " +"кораке да директно решимо потенцијалне проблеме." -#: ../system/variables.rst:134 +#: ../system/monitoring.rst:11 msgid "" -"We support the known format directives for the Ruby built-in method " -"``strftime`` of the ``DateTime`` class. For more information, see `here " -"`_." +"On the monitoring page, you can see the current health state of Zammad under " +"\"*Current Status*\" at the bottom. This can be useful if you want to have a " +"look if everything is up and running. As an example, you could have a look " +"in the monitoring when you assume that some emails aren't processed from " +"Zammad." msgstr "" -"Подржане су све директиве Ruby метода ``strftime`` из DateTime`` класе. За " -"више информације, погледајте `овде `_." +"На страници за надгледање можете видети тренутно стање Zammad-а под " +"„*Тренутно стање*“ при дну. Ово може бити корисно ако желите да проверите да " +"ли је све у реду. Као пример, могли бисте да провериде у надгледању када " +"претпоставите да се неке имејл поруке не обрађују од стране Zammad-а." -#: ../system/variables/article.rst:2 -msgid "Articles" -msgstr "Чланци" +#: ../system/monitoring.rst:17 +msgid "**Can't receive an email and the monitoring response is \"healthy\"?**" +msgstr "" +"**Не можете да примите имејл поруке и стање надгледања је „без проблема“?**" -#: ../system/variables/article.rst:4 ../system/variables/config.rst:4 -#: ../system/variables/current-user.rst:4 ../system/variables/ticket.rst:4 +#: ../system/monitoring.rst:19 msgid "" -"If you're missing variables or are not sure if something is not working as " -"expected, feel free to ask over at the `Community `_." +"Zammad will just inform you about unprocessable emails. This is not the case " +"for oversized emails. You can adjust the maximum email size in :doc:`../" +"channels/email/settings`." msgstr "" -"Ако вам недостају променљиве или нисте сигурни да ли нешто функционише на " -"очелован начин, слободно питајте у `Community форуму `_." +"Zammad ће вас само обавестити о необрађеним имејл порукама. Ово није случај " +"са превеликим имејл порукама. Можете подесити максималну величину имејл " +"порука путем :doc:`../channels/email/settings`." -#: ../system/variables/article.rst:6 +#: ../system/monitoring.rst:24 +msgid "Monitoring API" +msgstr "API надгледања" + +#: ../system/monitoring.rst:26 msgid "" -"Below you can find all available ticket article-based variables within " -"Zammad. These can be called via Triggers for example. If you're unsure if " -"Zammad does support variables at the point you're at, you can try to type " -"``::`` to check." +"Beside the indication in the monitoring page, you can also use an external " +"monitoring tool to monitor Zammad's health. To request the health of Zammad, " +"you need to provide the API key (token) to the external monitoring tool. You " +"can copy the token from the \"*Current Token*\" field as well as the whole " +"API endpoint of your system (\"*Health Check*\" field), in which the API " +"token is already included." msgstr "" -"Испод можете пронажи све доступне променљиве чланака тикета у оквиру Zammad-" -"а. Могу се користити унутар нпр. окидача. Ако нисте сигурни да ли Zammad " -"подржава променљиве у делу у коме се налазите, пробајте да откуцате ``::``да " -"бисте проверили." +"Поред индикације на страници за надгледање, можете користити и спољни алат " +"за надгледање статуса Zammad-а. Да бисте надгледали Zammad, потребно је да " +"доставите API кључ (токен) спољном алату за надгледање. Можете копирати кључ " +"из поља „*Тренутни кључ*“, као и комплетну API путању вашег система (поље " +"„*Провера доступности*“), у коју је API кључ већ укључен." + +#: ../system/monitoring.rst:37 +msgid "Screenshot showing Current Token and Health Check" +msgstr "Снимак екрана који приказује тренутни кључ и проверу доступности" + +#: ../system/monitoring.rst:37 +msgid "Screenshot showing Token and Health Check" +msgstr "Снимак екрана који приказује кључ и проверу доступности" -#: ../system/variables/article.rst:9 ../system/variables/config.rst:9 -#: ../system/variables/ticket.rst:9 +#: ../system/monitoring.rst:39 msgid "" -"The below list gives you an example what kind of data you can expect, it's " -"not intended to explain the data itself." +"In addition to that, you can reset the auto-generated token to make sure " +"that already configured monitoring systems won't work anymore. So, please " +"use this \"*Reset*\" button only if you know what you do!" msgstr "" -"Листа испод вам пружа пример какав тип података можете очекивати, није јој " -"циљ да објасни саме податке." - -#: ../system/variables/article.rst:11 -msgid "Article Variables" -msgstr "Променљиве чланка" +"Поред тога, можете ресетовати аутоматски генерисани кључ да бисте били " +"сигурни да већ конфигурисани системи за надгледање више неће радити. Дакле, " +"користите дугме „*Поништи*” само ако знате шта радите!" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "name" -msgstr "назив" +#: ../system/monitoring.rst:44 +msgid "Example Output" +msgstr "Пример резултата" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "variable" -msgstr "променљива" +#: ../system/monitoring.rst:0 +msgid "No issues found" +msgstr "Није пронађен ниједан проблем" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "example" -msgstr "пример" +#: ../system/monitoring.rst:48 ../system/monitoring.rst:60 +msgid "**Indicator in Zammad**:" +msgstr "**Индикатор у Zammad-у**:" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Web" -msgstr "Чланак > Освежено од стране > Веб" +#: ../system/monitoring.rst:0 +msgid "Screenshot showing monitoring with no issues" +msgstr "Снимак екрана који приказује преглед надгледања без проблема" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.web}``" -msgstr "``#{article.updated_by.web}``" +#: ../system/monitoring.rst:54 ../system/monitoring.rst:66 +msgid "**API response**::" +msgstr "**API одговор**::" -#: ../system/variables/article.rst:1 -msgid "``https://zammad.com`` or empty if not set in user object" -msgstr "" -"``https://zammad.com`` или празно ако није постављено у објекту корисника" +#: ../system/monitoring.rst:0 +msgid "Issues were found" +msgstr "Проблеми су пронађени" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > VIP" -msgstr "Чланак > Освежено од стране > VIP" +#: ../system/monitoring.rst:0 +msgid "Screenshot showing monitoring with issues" +msgstr "Снимак екрана који приказује преглед надгледања са проблемима" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.vip}``" -msgstr "``#{article.updated_by.vip}``" +#: ../system/objects.rst:2 +msgid "Objects" +msgstr "Објекти" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -msgid "``true`` or ``false``" -msgstr "``true`` или ``false``" +#: ../system/objects.rst:4 +msgid "" +"In Zammad you can add your own fields to tickets, users, organizations and " +"even groups (these are called \"objects\"). This can be useful if you need " +"to add further information to a ticket or any other object in Zammad and the " +"information doesn't fit in any existing field." +msgstr "" +"У Zammad-у можете додати сопствена поља тикетима, корисницима, " +"организацијама, па чак и групама (тзв. „објектима”). Ово може бити корисно " +"ако тикету треба да додате додатне информације које не припадају ни једном " +"постојећем пољу." -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Phone" -msgstr "Чланак > Освежено од стране > Телефон" +#: ../system/objects.rst:11 +msgid "" +"Try to avoid deleting attributes (and disable them instead) as Zammad might " +"run into unexpected conditions if they are referenced somewhere." +msgstr "" +"Покушајте да избегнете брисање атрибута (и уместо тога их само искључите) " +"јер Zammad може наићи на неочекиване услове ако се поља још увек помињу " +"негде." -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.phone}``" -msgstr "``#{article.updated_by.phone}``" +#: ../system/objects.rst:16 +msgid "" +"Here's an overview of object attributes. On the upper right you can add new " +"attributes. By default, there will be no custom fields - standard attributes " +"will be grayed out, you can't delete or change those. You can edit custom " +"attributes (they are displayed in black font and have a trash bin on the " +"right side) just by clicking on them." +msgstr "" +"Ево прегледа атрибута. У горњем десном углу можете додати нове атрибуте. " +"Подразумевано, нема прилагођених поља – стандардни атрибути ће бити " +"засивљени, не можете их избрисати или изменити. Кликом на прилагођене " +"атрибуте (биће приказани регуларном бојом и имаће иконицу канте за отпатке " +"са десне стране) можете их уредити." -#: ../system/variables/article.rst:1 -msgid "``+4930123456789`` or empty if not set in user object" -msgstr "``+4930123456789`` или празно ако није постављено у објекту корисника" +#: ../system/objects.rst:24 +msgid "" +"Attributes you add to Zammad, no matter if they have default values or not, " +"will not update existing information. This means a new ticket field " +"technically will be empty unless you populate it." +msgstr "" +"Атрибути које додате у Zammad, без обзира да ли имају подразумеване " +"вредности или не, неће утицати на постојеће информације. То значи да ће ново " +"поље за тикет технички бити празно све док га не попуните." -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Note" -msgstr "Чланак > Освежено од стране > Напомена" +#: ../system/objects.rst:28 +msgid "" +"Especially in ticket scope this also means that newly added attributes will " +"be indicated as \"changed\" to agents that view the ticket. This may " +"interfere with Zammad's tabs behavior." +msgstr "" +"Посебно у оквиру тикета, ово такође значи да ће новододати атрибути бити " +"означени као „измењени“ оператерима који прегледају тикет. Ово може да омета " +"понашање језичака у Zammad-у." -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.note}``" -msgstr "``#{article.updated_by.note}``" +#: ../system/objects.rst:40 +msgid "Ordering Attributes" +msgstr "Промена редоследа атрибута" -#: ../system/variables/article.rst:1 -msgid "``Some note about user`` or empty if not set in user object" +#: ../system/objects.rst:42 +msgid "" +"Since Zammad introduced :doc:`/system/core-workflows` the need to have a " +"custom positioning for attributes has become more important than ever." msgstr "" -"``Нека напомена о кориснику`` или празно ако није постављено у објекту " -"корисника" +"Откако је Zammad увео :doc:`радне токове `, потреба " +"за прилагођеним редоследом атрибута постала је важнија него икад." -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Mobile" -msgstr "Чланак > Освежено од стране > Мобилни" +#: ../system/objects.rst:45 +msgid "" +"To adjust the position of such an attribute, simply click on the attribute " +"entry in question, scroll down and adjust the position number. Please note " +"that you cannot change the positioning of default attributes." +msgstr "" +"Да бисте подесили положај оваквог атрибута, једноставно кликните на њега, " +"скролујте на доле и подесите поље положаја. Обратите пажњу да не можете " +"променити положај подразумеваних атрибута." -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.mobile}``" -msgstr "``#{article.updated_by.mobile}``" +#: ../system/objects.rst:49 +msgid "" +"In case two attributes have the same position value, Zammad will sort " +"alphabetically by name automatically." +msgstr "" +"У случају да два атрибута имају исту вредност положаја, Zammad ће их " +"аутоматски сортирати по абецедном реду по називу." -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Login" -msgstr "Чланак > Освежено од стране > Пријава" +#: ../system/objects.rst:None +msgid "" +"Screenshot showing custom attribute entries ordered in between default ones" +msgstr "" +"Снимак екрана који приказује уносе прилагођених атрибута са положајем између " +"подразумеваних атрибута" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.login}``" -msgstr "``#{article.updated_by.login}``" +#: ../system/objects.rst:56 +msgid "Updating Database After Adding or Editing Attributes" +msgstr "Освежавање базе података након додавања или уређивања атрибута" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -#: ../system/variables/ticket.rst:1 -msgid "``jdoe``" -msgstr "``jdoe``" +#: ../system/objects.rst:58 +msgid "" +"When adding or changing attributes, Zammad will not apply the changes " +"instantly, but instead shows you the changed attributes first. If you're " +"ready to go, just click on \"Update database\" to apply the changes to " +"Zammad. If you made a mistake or just want to discard your changes, click " +"\"Discard changes\"." +msgstr "" +"Када додајете или мењате атрибуте, Zammad неће одмах применити измене, већ " +"вам прво показује измењене атрибуте. Ако сте спремни да наставите, само " +"кликните на „Освежи базу података“ да бисте применили промене. Ако сте " +"погрешили или само желите да одбаците промене, кликните на „Откажи промене“." -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Lastname" -msgstr "Чланак > Освежено од стране > Презиме" +#: ../system/objects.rst:64 +msgid "" +"After applying the changes with \"Update Database\", a restart of Zammad is " +"**mandatory**. If you don't perform it, you may experience unexpected " +"behavior or even errors. You may want to do this kind of configuration " +"during maintenance windows." +msgstr "" +"Након примене измена путем „Освежи базу података“, поновно покретање Zammad-" +"ових сервиса је **обавезно**. Ако то не урадите, можете доћи у неочекивану " +"ситуацију или чак узроковати грешке. Можда ћете желети да одрадите оваква " +"подешавања током режима одржавања." -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.lastname}``" -msgstr "``#{article.updated_by.lastname}``" +#: ../system/objects.rst:72 +msgid "" +"Changes on objects require you to update the database to apply these changes." +msgstr "" +"Измене на објектима захтевају да освежите базу података да бисте применили " +"ове измене." -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -#: ../system/variables/ticket.rst:1 -msgid "``Doe`` or empty if not set" -msgstr "``Doe`` или празно ако није постављено" +#: ../system/objects.rst:75 +msgid "**🤓 Service restarts can be automated**" +msgstr "**🤓 Поновно покретање сервиса се може аутоматизовати**" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Firstname" -msgstr "Чланак > Освежено од стране > Име" +#: ../system/objects.rst:0 +msgid "Hosted environments automatically restart for you." +msgstr "Хостована окружења се аутоматски рестартују за вас." -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.firstname}``" -msgstr "``#{article.updated_by.firstname}``" +#: ../system/objects.rst:0 +msgid "" +"If you're using a self-hosted installation you can use :docs:`environment " +"variables `" +msgstr "" +"Ако користите инсталацију коју сами хостујете, можете користити :docs:" +"`променљиве окружења `." -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "``Joe`` or empty if not set" -msgstr "``Joe`` или празно ако није постављено" +#: ../system/objects.rst:82 +msgid "System Attributes" +msgstr "Системски атрибути" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Fax" -msgstr "Чланак > Освежено од стране > Факс" +#: ../system/objects.rst:84 +msgid "" +"Zammad comes with pre-configured attributes. Some of them can't be edited " +"via UI (or at all). This is required for proper operation of Zammad and not " +"a bug." +msgstr "" +"Zammad долази са унапред конфигурисаним атрибутима. Неки од њих тренутно не " +"пружају могућност уређивања путем корисничког интерфејса (или уопште). Ови " +"атрибути су обавезни за исправно функционисање Zammad-а и није у питању " +"грешка." -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.fax}``" -msgstr "``#{article.updated_by.fax}``" +#: ../system/objects.rst:90 +msgid "Ticket State" +msgstr "Стање тикета" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Email" -msgstr "Чланак > Освежено од стране > Имејл" +#: ../system/objects.rst:92 +msgid "" +"If the pre-configured states aren't enough for you or you want to change " +"them, you can do so by clicking on the cogwheel icon in the state row in the " +"ticket tab. But you should be careful when changing pre-configured states. " +"This can lead to unwanted behavior in some cases." +msgstr "" +"Уколико вам предефинисана стања нису довољна или желите да их измените, то " +"можете урадити кликом на иконицу зупчаника у реду са атрибутом стања у " +"језичку тикета. Али будите пажљиви кад мењате предефинисана стања. У неким " +"случајевима ово може довести до нежељеног понашања." -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.email}``" -msgstr "``#{article.updated_by.email}``" +#: ../system/objects.rst:None +msgid "Screenshot showing highlighted ticket state attribute" +msgstr "Снимак екрана који приказује наглашен атрибут стања тикета" -#: ../system/variables/article.rst:1 -msgid "``jdoe@example.com``" -msgstr "``jdoe@example.com``" +#: ../system/objects.rst:122 +msgid "Handling of states" +msgstr "Руковање стањима" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Department" -msgstr "Чланак > Освежено од стране > Одељење" +#: ../system/objects.rst:102 +msgid "" +"In the state configuration screen, you can add new states, disable states or " +"change states." +msgstr "" +"У екрану подешавања стања можете додати нова стања, искључити постојећа или " +"их изменити." -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.department}``" -msgstr "``#{article.updated_by.department}``" +#: ../system/objects.rst:0 +msgid "Screenshot showing table of default ticket states" +msgstr "Снимак екрана који приказује табелу подразумеваних стања тикета" -#: ../system/variables/article.rst:1 -msgid "``Sales`` or empty if not set in user object" -msgstr "``Sales`` или празно ако није постављено у објекту корисника" +#: ../system/objects.rst:110 +msgid "" +"To add a new state, click on the \"New Ticket State\" button in the top " +"right corner. To change an existing state, simply click on the affected " +"state. This opens an edit dialog." +msgstr "" +"Да бисте додали стање, кликните на дугме „Ново стање тикета” у горњем десном " +"углу. За измену постојећег стања, једноставно кликните на дотично стање. Ово " +"ће отворити дијалог за уређивање." -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Address" -msgstr "Чланак > Освежено од стране > Адреса" +#: ../system/objects.rst:114 +msgid "" +"You can also clone a state or set them to \"Default for new tickets\" or " +"\"Default for follow-ups\" by clicking on the ⁝ action button and select the " +"desired function." +msgstr "" +"Такође можете клонирати стање или га поставити на „подразумевано за нове " +"тикете” или „подразумевано за наставке” кликом на ⁝ дугме радњи и одабиром " +"жељене функције." -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.address}``" -msgstr "``#{article.updated_by.address}``" +#: ../system/objects.rst:118 +msgid "" +"*Default for new tickets* means that this state is used for every newly " +"created ticket." +msgstr "" +"*Подразумевано за нове тикете* значи да ће ово стање бити коришћено за све " +"новоотворене тикете." -#: ../system/variables/article.rst:1 -msgid "``Some street 1, 12345 Berlin`` or empty if not set in user object" +#: ../system/objects.rst:121 +msgid "" +"*Default for follow-ups* means that this state is used if the ticket is re-" +"opened after it was closed." msgstr "" -"``Назив неке улице 1, 12345 Берлин`` или празно ако није постављено у " -"објекту корисника" +"*Подразумевано за наставке* значи да ће ово стање бити коришћено уколико се " +"тикет поново отвори након што је био затворен." -#: ../system/variables/article.rst:1 -msgid "Article > Updated" -msgstr "Чланак > Освежено у" +#: ../system/objects.rst:171 +msgid "Ticket state in detail" +msgstr "Детаљније о стању тикета" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_at}``" -msgstr "``#{article.updated_at}``" +#: ../system/objects.rst:125 +msgid "" +"Below you can find a description for each field and option. Please head over " +"to the :ref:`example ` to see the edit dialog." +msgstr "" +"Испод можете пронаћи опис сваког поља и опције. Идите на :ref:`пример " +"` да бисте видели како изгледа дијалог за уређивање." -#: ../system/variables/article.rst:1 -msgid "``2019-10-08 15:24:47 UTC``" -msgstr "``2019-10-08 15:24:47 UTC``" +#: ../system/objects.rst:129 +msgid "" +"This is the name of the state and what you and your agents are seeing when " +"choosing a state somewhere (e.g. in tickets, trigger configuration)." +msgstr "" +"Ово је назив стања и шта ви и ваши оператери видите када негде бирате стање " +"(нпр. у тикетима, подешавању окидача)." -#: ../system/variables/article.rst:1 -msgid "Article > Type > Name" -msgstr "Чланак > Тип > Назив" +#: ../system/objects.rst:137 +msgid "" +"There are different state types you can choose from. By default, Zammad " +"comes with one state per state type." +msgstr "" +"Има више различитих типова стања које можете одабрати. Подразумевано, Zammad " +"долази са једним стањем по сваком типу стања." -#: ../system/variables/article.rst:1 -msgid "``#{article.type.name}``" -msgstr "``#{article.type.name}``" +#: ../system/objects.rst:140 +msgid "" +"**new**: for states for tickets that are new and it hasn't been worked on " +"them" +msgstr "**ново**: за стања тикета који су нови и који још увек нису обрађени" -#: ../system/variables/article.rst:1 +#: ../system/objects.rst:142 msgid "" -"``email`` (`list of article types `_)" +"**open**: for states for tickets that are in progress and agents are working " +"on them" msgstr "" -"``email`` (`листа типова чланака `_)" - -#: ../system/variables/article.rst:1 -msgid "Article > To" -msgstr "Чланак > За" - -#: ../system/variables/article.rst:1 -msgid "``#{article.to}``" -msgstr "``#{article.to}``" - -#: ../system/variables/article.rst:1 -msgid "``helpdesk@example.com``" -msgstr "``helpdesk@example.com``" +"**отворено**: за стања тикета који су у процесу и оператери раде на њима" -#: ../system/variables/article.rst:1 -msgid "Article > TicketID" -msgstr "Чланак > TicketID" +#: ../system/objects.rst:144 +msgid "**merged**: for states for tickets that are merged with other tickets" +msgstr "**спојено**: за стања тикета који су спојени са другим тикетима" -#: ../system/variables/article.rst:1 -msgid "``#{article.ticket_id}``" -msgstr "``#{article.ticket_id}``" +#: ../system/objects.rst:145 +msgid "" +"**pending reminder**: for states for tickets that are in progress and you " +"want to set a reminder. (default example: *pending reminder*)" +msgstr "" +"**чека на подсетник**: за стања тикета који су у процесу и за које желите да " +"поставите подсетник. (подразумевани пример: *чека на подсетник*)" -#: ../system/variables/article.rst:1 -msgid "``1`` (not ticket number)" -msgstr "``1`` (не представља број тикета)" +#: ../system/objects.rst:147 +msgid "" +"**pending action**: for states for tickets that are waiting for a specified " +"time and then change their state (default example: *pending close*)" +msgstr "" +"**радња на чекању**: за стања тикета који чекају на одређено време и тада " +"мењају своје стање (подразумевани пример: *чека на затварање*)" -#: ../system/variables/article.rst:1 -msgid "Article > Subject" -msgstr "Чланак > Предмет" +#: ../system/objects.rst:150 +msgid "" +"**closed**: for states for tickets that are finished and do not need to be " +"processed further" +msgstr "" +"**затворено**: за стања тикета који су обрађени и које више није неопходно " +"процесуирати" -#: ../system/variables/article.rst:1 -msgid "``#{article.subject}``" -msgstr "``#{article.subject}``" +#: ../system/objects.rst:153 +msgid "" +"⚠️ Choosing the correct state type is important! If you are in doubt, have a " +"look on the default states and their types!" +msgstr "" +"⚠️ Важно је одабрати исправан тип стања! Ако сумњате у свој избор, погледајте " +"подразумевана стања и њихове типове!" -#: ../system/variables/article.rst:1 -msgid "``My amazing subject``" -msgstr "``Мој екстра предмет`" +#: ../system/objects.rst:158 +msgid "Ignore escalation" +msgstr "Игнориши ескалације" -#: ../system/variables/article.rst:1 -msgid "Article > Sender > Name" -msgstr "Чланак > Пошиљалац > Назив" +#: ../system/objects.rst:157 +msgid "" +"Here you can define whether tickets of this state will count to escalation " +"time or not." +msgstr "" +"Овде можете одредити да ли ће се тикети у овом стању рачунати за време " +"ескалације." -#: ../system/variables/article.rst:1 -msgid "``#{article.sender.name}``" -msgstr "``#{article.sender.name}``" +#: ../system/objects.rst:161 +msgid "" +"You can create a note for the state to inform other admins about the state. " +"This has no effect on tickets." +msgstr "" +"Можете додати напомену за стање да бисте обавестили друге администраторе о " +"овом стању. Ово нема ефекта на тикете." -#: ../system/variables/article.rst:1 -msgid "``Customer``, ``Agent`` or ``System``" -msgstr "``Customer``, ``Agent`` или ``System``" +#: ../system/objects.rst:165 +msgid "Set the state to *active* or *inactive*." +msgstr "Поставите стање на *укључено* или *искључено*." -#: ../system/variables/article.rst:1 -msgid "Article > Visibility" -msgstr "Чланак > Видљивост" +#: ../system/objects.rst:167 +msgid "" +"it is technically possible to set all states to inactive. To keep Zammad " +"working in such a case, the inactive flag of one of the states is ignored." +msgstr "" +"Технички је могуће искључити сва стања. Да бисте обезбедили да Zammad " +"настави да функционише, једно од искључених стања ће бити аутоматски " +"активирано." -#: ../system/variables/article.rst:1 -msgid "``#{article.internal}``" -msgstr "``#{article.internal}``" +#: ../system/objects.rst:194 +msgid "Ticket state example" +msgstr "Пример стања тикета" -#: ../system/variables/article.rst:1 -msgid "``false`` or ``true`` (false if not internal)" -msgstr "``false`` или ``true`` (false ако није интерни)" +#: ../system/objects.rst:174 +msgid "" +"Let's assume we want to create a new state which indicates that the ticket " +"has to wait for a response of a third party (e.g. service contractor or " +"manufacturer) and we want to to be able to set a reminder." +msgstr "" +"Хајде да претпоставимо да желимо да додамо ново стање који означава да тикет " +"чека на одговор трећег лица (нпр. подизвођача или произвођача) и желимо да " +"поставимо подсетник." -#: ../system/variables/article.rst:1 -msgid "Article > From" -msgstr "Чланак > Од" +#: ../system/objects.rst:178 +msgid "" +"First we give the new state a proper name. In this example we call it " +"\"waiting for manufacturer\"." +msgstr "" +"Прво дајемо назив новом стању. У овом примеру називамо га „чека на " +"произвођача”." -#: ../system/variables/article.rst:1 -msgid "``#{article.from}``" -msgstr "``#{article.from}``" +#: ../system/objects.rst:181 +msgid "" +"As state type we choose \"pending reminder\". This indicates that the ticket " +"is still open and we can set a reminder. This reminder can be useful if our " +"manufacturer sometimes isn't responding or we want to remind him to give us " +"an answer." +msgstr "" +"Као тип стања одабиремо „чека на подсетник”. Ово означава да је тикет и даље " +"отворен и можемо поставити подсетник. Овај подсетник може бити користан " +"уколико наш произвођач понекад не реагује или желимо да их подсетимо за нам " +"доставе одговор." -#: ../system/variables/article.rst:1 +#: ../system/objects.rst:186 msgid "" -"``Joe Doe `` may differ, depends on ``FROM`` of send mail" +"We choose \"no\" for \"ignore escalation\" because we want to escalate the " +"tickets even if we are waiting on the manufacturer's feedback." msgstr "" -"``Joe Doe `` може бити различито, зависи од ``FROM`` " -"атрибута имејл поруке" +"Одабиремо „не” за „игнориши ескалације” зато што желимо да ескалирамо тикете " +"чак иако чекамо на одговор произвођача." -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Web" -msgstr "Чланак > Додато од стране > Веб" +#: ../system/objects.rst:189 +msgid "The **result** in the creation dialog will look like this:" +msgstr "**Резултат** у дијалогу новог тикета ће изгледати овако:" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.web}``" -msgstr "``#{article.created_by.web}``" +#: ../system/objects.rst:0 +msgid "Screenshot showing ticket state creation dialog with example" +msgstr "" +"Снимак екрана који приказује дијалог за додавање новог стања тикета са " +"примером" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > VIP" -msgstr "Чланак > Додато од стране > VIP" +#: ../system/objects.rst:199 +msgid "Ticket Priority" +msgstr "Приоритет тикета" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.vip}``" -msgstr "``#{article.created_by.vip}``" +#: ../system/objects.rst:201 +msgid "" +"If the pre-configured priorities aren't enough for you or you want to change " +"them, you can do so by clicking on the cogwheel icon in the priority row in " +"the ticket tab:" +msgstr "" +"Уколико вам предефинисани приоритети нису довољни или желите да их измените, " +"то можете урадити кликом на иконицу зупчаника у реду са атрибутом приоритета " +"у језичку тикета:" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Phone" -msgstr "Чланак > Додато од стране > Телефон" +#: ../system/objects.rst:None +msgid "Screenshot showing highlighted ticket priority attribute" +msgstr "Снимак екрана који приказује наглашен атрибут приоритета тикета" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.phone}``" -msgstr "``#{article.created_by.phone}``" +#: ../system/objects.rst:226 +msgid "Handling of priorities" +msgstr "Руковање приоритетима" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Note" -msgstr "Чланак > Додато од стране > Напомена" +#: ../system/objects.rst:210 +msgid "" +"In the priority configuration screen, you can add new priorities, disable " +"priorities or change priorities." +msgstr "" +"У екрану подешавања приоритета можете додати нове приоритете, искључити " +"постојеће или их изменити." -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.note}``" -msgstr "``#{article.created_by.note}``" +#: ../system/objects.rst:0 +msgid "Screenshot showing table of default ticket priorities" +msgstr "Снимак екрана који приказује табелу подразумеваних приоритета тикета" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Mobile" -msgstr "Чланак > Додато од стране > Мобилни" +#: ../system/objects.rst:218 +msgid "" +"To add a new priority, click on the \"New Priority\" button in the top right " +"corner. To change an existing priority, simply click on the affected " +"priority. This opens an edit dialog." +msgstr "" +"Да бисте додали нови приоритет, кликните на дугме „Нови приоритет” у горњем " +"десном углу. За измену постојећег приоритета, једноставно кликните на " +"дотични приоритет. Ово ће отворити дијалог за уређивање." -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.mobile}``" -msgstr "``#{article.created_by.mobile}``" +#: ../system/objects.rst:222 +msgid "" +"You can also clone a priority or set them to \"Default for new tickets\" by " +"clicking on the ⁝ action button and select the desired function." +msgstr "" +"Такође можете клонирати приоритет или га поставити на „подразумевано за нове " +"тикете” кликом на ⁝ дугме радњи и одабиром жељене функције." -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Login" -msgstr "Чланак > Додато од стране > Пријава" +#: ../system/objects.rst:225 +msgid "" +"*Default for new tickets* means that this priority is used for every newly " +"created ticket." +msgstr "" +"*Подразумевано за нове тикете* значи да ће овај приоритет бити коришћен за " +"све новоотворене тикете." -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.login}``" -msgstr "``#{article.created_by.login}``" +#: ../system/objects.rst:248 +msgid "Priorities in detail" +msgstr "Детаљније о приоритетима" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Lastname" -msgstr "Чланак > Додато од стране > Презиме" +#: ../system/objects.rst:229 +msgid "Below you can find a description for each field and option." +msgstr "Испод можете наћи опис сваког поља и опције." -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.lastname}``" -msgstr "``#{article.created_by.lastname}``" +#: ../system/objects.rst:232 +msgid "" +"This is the name of the priority and what you and your agents are seeing " +"when choosing a priority somewhere (e.g. in tickets, trigger configuration)." +msgstr "" +"Ово је назив приоритета и шта ви и ваши оператери видите када негде бирате " +"приоритет (нпр. у тикетима, подешавању окидача)." -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Firstname" -msgstr "Чланак > Додато од стране > Име" +#: ../system/objects.rst:242 +msgid "Highlight color" +msgstr "Боја истицања" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.firstname}``" -msgstr "``#{article.created_by.firstname}``" +#: ../system/objects.rst:237 +msgid "" +"Switch between *Low priority* (light blue), *High priority* (red) and - " +"(default). This affects the displayed color for ticket titles in overviews." +msgstr "" +"Изаберите између *Низак приоритет* (светло плава), *Висок приоритет* " +"(црвена) и - (подразумевано). Ово утиче на боју приказа наслова тикета у " +"прегледима." -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Fax" -msgstr "Чланак > Додато од стране > Факс" +#: ../system/objects.rst:241 +msgid "The color options are currently limited to the mentioned options." +msgstr "Доступне боје су тренутно ограничене на поменуте опције." -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.fax}``" -msgstr "``#{article.created_by.fax}``" +#: ../system/objects.rst:245 +msgid "" +"You can create a note for the priority to inform other admins about the " +"priority. This has no effect on tickets." +msgstr "" +"Можете додати напомену за приоритет да бисте обавестили друге администраторе " +"о овом приоритету. Ово нема ефекта на тикете." -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Email" -msgstr "Чланак > Додато од стране > Имејл" +#: ../system/objects.rst:249 +msgid "Set the priority to *active* or *inactive*." +msgstr "Поставите приоритет на *укључено* или *искључено*." -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.email}``" -msgstr "``#{article.created_by.email}``" +#: ../system/objects/external-data-source-example.rst:2 +msgid "External Data Source" +msgstr "Удаљени извор података" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Department" -msgstr "Чланак > Додато од стране > Одељење" +#: ../system/objects/external-data-source-example.rst:4 +msgid "" +"We assume you already had a look on :doc:`types` where you can find a " +"description of the individual fields." +msgstr "" +"Претпостављамо да сте већ погледали :doc:`типове ` где можете пронаћи " +"опис појединачних поља." -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.department}``" -msgstr "``#{article.created_by.department}``" +#: ../system/objects/external-data-source-example.rst:7 +msgid "" +"To reproduce this example, choose a category you want to add a custom field, " +"click on *New Attribute* and select *External data source field* under " +"*Format*." +msgstr "" +"Да бисте репродуковали овај пример, одаберите категорију коју желите да " +"додате прилагођеном пољу, клините на *Нови атрибут* и изаберите *Поље " +"удаљеног извора података* за *Формат*." -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Address" -msgstr "Чланак > Додато од стране > Адреса" +#: ../system/objects/external-data-source-example.rst:11 +msgid "" +"Our example story is to fetch data from an external product database. We " +"want to add our products to the tickets so that the products can be searched " +"and chosen from a list and also create a link to the product website." +msgstr "" +"Наш пример преузима податке из удаљене базе података са производима. Желимо " +"да додамо наше производе тикетима тако да је могуће претражити производе и " +"изабрати их са листе и приказати линк на страну производа." -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.address}``" -msgstr "``#{article.created_by.address}``" +#: ../system/objects/external-data-source-example.rst:16 +msgid "Base configuration" +msgstr "Основна подешавања" -#: ../system/variables/article.rst:1 -msgid "Article > Created" -msgstr "Article > Додато у" +#: ../system/objects/external-data-source-example.rst:None +msgid "Initial steps to configure external data source object type" +msgstr "Први кораци за подешавање удаљеног извора података" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_at}``" -msgstr "``#{article.created_at}``" +#: ../system/objects/external-data-source-example.rst:25 +msgid "Name: *product*" +msgstr "Назив: *product*" -#: ../system/variables/article.rst:1 -msgid "Article > Cc" -msgstr "Чланак > Cc" +#: ../system/objects/external-data-source-example.rst:26 +msgid "Display: *Product*" +msgstr "Прикажи: *Производ*" -#: ../system/variables/article.rst:1 -msgid "``#{article.cc}``" -msgstr "``#{article.cc}``" +#: ../system/objects/external-data-source-example.rst:29 +msgid "External data source configuration" +msgstr "Подешавање удаљеног извора података" -#: ../system/variables/article.rst:1 -msgid "``jdoe@example.com, company@example.com``" -msgstr "``jdoe@example.com, company@example.com``" +#: ../system/objects/external-data-source-example.rst:31 +msgid "" +"First, enter the search URL making sure it contains ``#{search.term}`` as a " +"parameter:" +msgstr "" +"Прво, унесите URL адресу претраге и уверите се да садржи ``#{search.term}`` " +"као параметар:" -#: ../system/variables/article.rst:1 -msgid "Article > Text" -msgstr "Чланак > Текст" +#: ../system/objects/external-data-source-example.rst:34 +msgid "**Example:** ``https://dummyjson.com/products/search?q=#{search.term}``" +msgstr "**Пример:** ``https://dummyjson.com/products/search?q=#{search.term}``" -#: ../system/variables/article.rst:1 -msgid "``#{article.body}``" -msgstr "``#{article.body}``" +#: ../system/objects/external-data-source-example.rst:36 +msgid "" +"After that, head down to the preview section and enter a search input for " +"the external data source." +msgstr "" +"Након тога, скролујте на доле до одељка приказа и унесите кључну реч за " +"претрагу удаљеног извора података." -#: ../system/variables/article.rst:1 -msgid "``Test`` without formatting (plain)" -msgstr "``Test`` без форматираног текста (обичан)" +#: ../system/objects/external-data-source-example.rst:39 +msgid "**Example:** ``mac``" +msgstr "**Пример:** ``mac``" -#: ../system/variables/article.rst:1 -msgid "Article Text as HTML (not referenced)" -msgstr "Текст чланка у HTML формату (без референцирања)" +#: ../system/objects/external-data-source-example.rst:41 +msgid "Then you can find a preview of the response data below:" +msgstr "Након тога можете видети следећи приказ одговора испод:" -#: ../system/variables/article.rst:1 -msgid "``#{article.body_as_html}``" -msgstr "``#{article.body_as_html}``" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of JSON response based on search term" +msgstr "Приказ JSON одговора на основу уноса претраге" -#: ../system/variables/article.rst:1 -msgid "``Test`` with formatting" -msgstr "``Тест`` са форматираним текстом" +#: ../system/objects/external-data-source-example.rst:48 +msgid "" +"We recommend using the preview to have a look on the structure. There is a " +"top-level element called ``products``. One level below, you can find the " +"attributes ``id`` and ``title``." +msgstr "" +"Препоручујемо да користите приказ за преглед структуре података. Постоји " +"кључ на основном нивоу под називом ``products``. Један ниво испод, можете " +"наћи атрибуте ``id`` и ``title``." -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "Ticket > Article#" -msgstr "Чланак > Број" +#: ../system/objects/external-data-source-example.rst:52 +msgid "**Search result response based on search from example:**" +msgstr "" +"**Одговор резултата претраге на основу унетих кључних речи из примера:**" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "``#{ticket.article_count}``" -msgstr "``#{ticket.article_count}``" +#: ../system/objects/external-data-source-example.rst:119 +msgid "" +"To tell the remote system that the desired data is located below the " +"``products`` level, you have to put it in the field *Search result list key*." +msgstr "" +"Да бисте рекли удаљеном систему да се подаци налазе испод нивоа " +"``products``, неопходно га је унети у поље *Кључ листе резулата претраге*." -#: ../system/variables/article.rst:1 -msgid "``1`` number of ticket articles" -msgstr "``1`` број чланака тикета" +#: ../system/objects/external-data-source-example.rst:122 +msgid "" +"After inserting ``products`` in the mentioned field, you get an extended " +"preview. You can find an additional box *Search result list* with a JSON " +"structure. This is the same response as before but stripped from the upper " +"``products`` element by the external data source." +msgstr "" +"По уносу ``products`` у одговарајуће поље, добићете освежен приказ. Можете " +"наћи додатан оквир *Листа резултата претрага* са JSON структуром. Ово је део " +"истог одговора удаљеног извора података као изнад али без спољног " +"``products``кључа." -#: ../system/variables/config.rst:2 -msgid "Config" -msgstr "Конфигурација" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of JSON response search result list" +msgstr "Приказ JSON одговора листе резултата претраге" -#: ../system/variables/config.rst:6 +#: ../system/objects/external-data-source-example.rst:132 msgid "" -"Below you'll find config related variables. These hold useful configuration " -"information that you can use within e.g. triggers to show necessary " -"information to your customer." +"Now you need to provide the keys for the search result values and labels. As " +"already mentioned, we are looking for the ``id`` and the ``title`` of our " +"products. If you haven't already, it is now a good time to look at the " +"preview of the *Search result list*." msgstr "" -"Испод ћете пронаћу променљиве које се односе на конфигурацију. Могу садржати " -"корисне податке које бисте желели да користите унутар нпр. окидача за приказ " -"потребних информација вашим клијентима." - -#: ../system/variables/config.rst:11 -msgid "Config Variables" -msgstr "Променљиве конфигурације" +"Сада је неопходно да обезбедите кључеве за вредности и ознаке резултата " +"претраге. Као што је напоменуто, тражимо ``id`` и ``title`` наших производа. " +"Ако већ нисте, сада је добар тренутак да погледате приказ *Листе резултата " +"претраге*." -#: ../system/variables/config.rst:1 -msgid "Config > Fully Qualified Domain Name" -msgstr "Конфигурација > Квалификовани назив домена" +#: ../system/objects/external-data-source-example.rst:197 +msgid "" +"After locating our two keys, we insert them in *search result value key* " +"(``id``) and in *Search result label key* (``title``)." +msgstr "" +"Након лоцирања наша два кључа, унећемо их у *Кључ вредности резулата " +"претраге* (``id``) и у *Кључ ознаке резулата претраге* (``title``)." -#: ../system/variables/config.rst:1 -msgid "``#{config.fqdn}``" -msgstr "``#{config.fqdn}``" +#: ../system/objects/external-data-source-example.rst:200 +msgid "" +"Basically, we configured the external data source already and we can see a " +"table in the preview section:" +msgstr "" +"У принципу већ смо подесили удаљни извор података и сада можемо видети " +"табелу у одељку приказа:" -#: ../system/variables/config.rst:1 -msgid "``zammad.example.com``" -msgstr "``zammad.example.com``" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of product table based on search term" +msgstr "Приказ табеле производа на основу унетих кључних речи претраге" -#: ../system/variables/config.rst:1 -msgid "Config > Ticket Hook" -msgstr "Конфигурација > Прикључак тикета" +#: ../system/objects/external-data-source-example.rst:208 +msgid "" +"According to our example story, now just the *Link template* is missing." +msgstr "Даље пратећи наш пример, једино недостсаје још *Шаблон везе*." -#: ../system/variables/config.rst:1 -msgid "``#{config.ticket_hook}``" -msgstr "``#{config.ticket_hook}``" +#: ../system/objects/external-data-source-example.rst:210 +msgid "" +"Please note that this is an optional feature. If you don't want to use such " +"links, of course you don't have to configure it." +msgstr "" +"Напомињемо да је ово опциона функција. Ако не желите да користите овакве " +"линкове, наравно не морате да их подесите." -#: ../system/variables/config.rst:1 -msgid "``Ticket#``" -msgstr "``Ticket#``" +#: ../system/objects/external-data-source-example.rst:213 +msgid "" +"We can add now an address where additional product information can be found." +msgstr "" +"Сада можемо додати адресу где се додатне информације о производу могу " +"пронаћи." -#: ../system/variables/config.rst:1 -msgid "Config > HTTP type" -msgstr "Конфигурација > HTTP протокол" +#: ../system/objects/external-data-source-example.rst:215 +msgid "Example: ``https://your_domain.com/q=#{ticket.product}``" +msgstr "Пример: ``https://your_domain.com/q=#{ticket.product}``" -#: ../system/variables/config.rst:1 -msgid "``#{config.http_type}``" -msgstr "``#{config.http_type}``" +#: ../system/objects/external-data-source-example.rst:217 +msgid "In the example, the parameter means:" +msgstr "У примеру, параметар има следеће значење:" -#: ../system/variables/config.rst:1 -msgid "``https`` or ``http``" -msgstr "``https`` или ``http``" +#: ../system/objects/external-data-source-example.rst:219 +msgid "``#{}``: \"Frame\" for the insertion of information" +msgstr "``#{}``: Поље за убацивање података" -#: ../system/variables/config.rst:1 -msgid "Config > SystemID" -msgstr "Конфигурација > SystemID" +#: ../system/objects/external-data-source-example.rst:220 +msgid "``ticket``: object level, where you create your custom object" +msgstr "``ticket``: ниво објекта, где додајете свој прилагођени атрибут" -#: ../system/variables/config.rst:1 -msgid "``#{config.system_id}``" -msgstr "``#{config.system_id}``" +#: ../system/objects/external-data-source-example.rst:221 +msgid "``product``: name of the (custom) object" +msgstr "``product``: назив (прилагођеног) атрибута" -#: ../system/variables/config.rst:1 -msgid "``31`` (value between 1 and 99)" -msgstr "``31`` (вредност између 1 и 99)" +#: ../system/objects/external-data-source-example.rst:223 +msgid "" +"After configuring your *Link template*, there will be another column in the " +"preview. Hovering on the icons in the *Link* column will show you where it " +"forwards you." +msgstr "" +"По подешавању *Шаблона везе*, биће приказана још једна колона у приказу. " +"Преласком курсора преко иконице у колони *Повежи* биће приказана адреса " +"преусмерења." -#: ../system/variables/config.rst:1 -msgid "Config > Organization" -msgstr "Конфигурација > Организација" +#: ../system/objects/external-data-source-example.rst:232 +msgid "" +"In our example, one of the links looks like: https://your_domain.com/q=6, " +"where the 6 is the product id." +msgstr "" +"У нашем примеру, један од линкова личи на: https://your_domain.com/q=6, где " +"је 6 ID вредност производа." -#: ../system/variables/config.rst:1 -msgid "``#{config.organization}``" -msgstr "``#{config.organization}``" +#: ../system/objects/external-data-source-example.rst:235 +msgid "You can find more information regarding the URL in :doc:`types`." +msgstr "Mожете пронаћи више информација о URL адресама у :doc:`types`." -#: ../system/variables/config.rst:1 +#: ../system/objects/includes/adding-values-hint.include.rst:3 msgid "" -"``Zammad GmbH`` value set in `Branding `_" +"Adding values can be tricky for first timers, don't forget to press \"➕ " +"Add\" after typing your values. Otherwise you may loose a value." msgstr "" -"Вредност организације постављене у `брендингу `_" - -#: ../system/variables/config.rst:1 -msgid "Config > Product Name" -msgstr "Конфигурација > Назив производа" +"Додавање вредности може бити незгодно за почетнике, не заборавите да " +"притиснете „➕ Додај“ након што унесете вредности. У супротном можете " +"изгубити унос." -#: ../system/variables/config.rst:1 -msgid "``#{config.product_name}``" -msgstr "``#{config.product_name}``" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:1 +#: ../system/objects/includes/reposition-values.include.rst:1 +msgid "**↕️ This field type allows the positioning of its values ↔️**" +msgstr "**↕️ Овај тип поља омогућава промену редоследа својих вредности ↔️**" -#: ../system/variables/config.rst:1 +#: ../system/objects/includes/reposition-treeselect-values.include.rst:3 msgid "" -"``Helpdesk`` value set in `Branding `_" +"In order to re-arrange the field values, first edit the field. Then you can " +"use ☰ to drag the values in question to the correct position. If you want to " +"change the layer depth, double click on ☰. With it you can cycle through the " +"available layers." msgstr "" -"Вредност назива производа постављене у `брендингу `_" +"Да бисте изменили опције поља, прво уредите поље. Након тога можете " +"користити ☰ да бисте превукли вредност у питању на одговарајућу позицију. " +"Уколико желите да измените дубину слоја, кликните двапут на ☰. Овом радњом " +"можете и да циклично мењате дубину слоја." -#: ../system/variables/current-user.rst:2 -msgid "Current User" -msgstr "Тренутни корисник" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:8 +msgid "When you're ready, submit your changes to save the object attribute." +msgstr "" +"Када сте спремни, пошаљите своје измене да бисте сачували атрибут објекта." -#: ../system/variables/current-user.rst:6 +#: :0 ../system/objects/types.rst:0 msgid "" -"Current user variables always return values of the current user that caused " -"e.g. a trigger to run." +"Screencast showing how to re-position values on tree select like\n" +"fields" msgstr "" -"Променљиве тренутног корисника увек враћају вредности корисника који је " -"покренуо нпр. окидач." +"Снимак екрана који показује како да измените положај вредности\n" +"у пољима избора стабла" -#: ../system/variables/current-user.rst:8 +#: ../system/objects/includes/reposition-values.include.rst:3 msgid "" -"Due to the above fact, these variables are often not (yet) set or available " -"for usage." +"In order to re-arrange the field values, edit the field and scroll below the " +"values. Make sure to tick the option \"Use custom option sort\"." msgstr "" -"С обзиром на горњу чињеницу, ове променљиве често немају (још увек) вредност " -"или нису доступне." +"Да бисте изменили редослед опција поља, уредите поље и скролујте на доле до " +"вредности. Обратите пажњу да укључите опцију „Користи прилагођен редослед " +"опција”." -#: ../system/variables/current-user.rst:10 +#: ../system/objects/includes/reposition-values.include.rst:8 msgid "" -"In situations where e.g. schedulers or triggers run, this most likely is " -"nothing you want to use." +"If you do not tick this field, all manual positioning you did above will be " +"lost upon saving! ☠️" msgstr "" -"У ситуацијама када се извршавају нпр. планери или окидачи, ово није нешто на " -"шта бисте желели да се ослоните." +"Уколико не укључите ово поље, сав ручно одређен редослед који сте обавили " +"изнад ће бити изгубљен по снимању! ☠️" -#: ../system/variables/current-user.rst:13 -msgid "Current User Variables" -msgstr "Променљиве тренутног корисника" +#: ../system/objects/includes/reposition-values.include.rst:11 +msgid "" +"Now use ☰ to drag the values in question to the correct position. When " +"you're ready, submit your changes to save the object attribute." +msgstr "" +"Користите ☰ да превучете и испустите дотичне вредности на нову жељену " +"позицију. Када будете спремни, снимите ваше измене да бисте сачували атрибут " +"објекта." -#: ../system/variables/current-user.rst:1 -msgid "Current User > Web" -msgstr "Тренутни корисник > Веб" +#: :0 ../system/objects/types.rst:0 +msgid "Screencast showing how to re-position values" +msgstr "Снимак екрана који приказује како да промените редослед вредности" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.web}``" -msgstr "``#{user.web}``" +#: ../system/objects/includes/url-template-hint.include.rst:3 +msgid "" +"This field allows using :ref:`URL fields (Link Templates) `." +msgstr "" +"Ово поље омогућава коришћење :ref:`URL адреса (шаблон везе) `." -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``https://zammad.org`` or empty if not set" -msgstr "``https://zammad.org`` или празно ако није постављено" +#: ../system/objects/permissions.rst:2 +msgid "Attribute Permissions" +msgstr "Дозволе атрибута" -#: ../system/variables/current-user.rst:1 -msgid "Current User > VIP" -msgstr "Тренутни корисник > VIP" +#: ../system/objects/permissions.rst:7 +msgid "" +"In the object attributes configuration you can define if a field is shown " +"and if the input in the field is mandatory, separated by different screens " +"and for different :doc:`roles/permissions `." +msgstr "" +"У конфигурацији атрибута објекта можете одредити да ли поље приказано и да " +"ли је унос поља обавезан, за различите екране и :doc:`корисничке улоге/" +"дозволе `." -#: ../system/variables/current-user.rst:1 -msgid "``#{user.vip}``" -msgstr "``#{user.vip}``" +#: ../system/objects/permissions.rst:17 +msgid "Screenshot shows object attribute permission table" +msgstr "Снимак екрана приказује табелу дозвола за атрибут објекта" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``false`` or ``true``" -msgstr "``false`` или ``true``" +#: ../system/objects/permissions.rst:17 +msgid "" +"Some of the possible permissions and screen options for a user object " +"attribute." +msgstr "Неке од могућих дозвола и опција екрана за атрибуте објекта корисника." -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Web" -msgstr "Тренутни корисник > Освежено од стране > Веб" +#: ../system/objects/permissions.rst:19 +msgid "" +"Based on the object context (ticket, agent, organization, user), the " +"selectable roles (to be precise: the required permissions) and screens " +"differ. Be aware that these settings aren't affecting data creation via " +"other channels than the UI." +msgstr "" +"На основу контекста објекта (тикет, група, организација, корисник), " +"омогућене улоге (прецизније: захтеване дозволе) и екрани се разликују. " +"Обратите пажњу да ова подешавања не управљају додавањем садржаја преко " +"других канала, ван корисничког интерфејса." -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.web}``" -msgstr "``#{user.updated_by.web}``" +#: ../system/objects/permissions.rst:24 +msgid "" +"If you want to have further customization possibilities, you should have a " +"look at the :doc:`core workflows `." +msgstr "" +"Уколико желите додатне могућности прилагођавања, погледајте документацију :" +"doc:`радних токова `." -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > VIP" -msgstr "Тренутни корисник > Освежено од стране > VIP" +#: ../system/objects/permissions.rst:28 +msgid "Screens" +msgstr "Екрани" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.vip}``" -msgstr "``#{user.updated_by.vip}``" +#: ../system/objects/permissions.rst:30 +msgid "" +"In the table below you can find an overview about the different permissions " +"and the available screens Zammad distinguishes between." +msgstr "" +"У табели испод можете наћи преглед различитих дозвола и досступних екрана " +"које Zammad подржава." -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Phone" -msgstr "Тренутни корисник > Освежено од стране > Телефон" +#: ../system/objects/permissions.rst:37 +msgid "Screen" +msgstr "Екран" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.phone}``" -msgstr "``#{user.updated_by.phone}``" +#: ../system/objects/permissions.rst:38 +msgid "Available for" +msgstr "Доступно за" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``004930123456789`` or empty if not set" -msgstr "``004930123456789`` или празно ако није постављено" +#: ../system/objects/permissions.rst:40 +msgid "create" +msgstr "create" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Note" -msgstr "Тренутни корисник > Освежено од стране > Напомена" +#: ../system/objects/permissions.rst:41 ../system/objects/permissions.rst:52 +#: ../system/objects/permissions.rst:59 ../system/objects/permissions.rst:73 +msgid "admin.user" +msgstr "admin.user" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.note}``" -msgstr "``#{user.updated_by.note}``" +#: ../system/objects/permissions.rst:42 ../system/objects/permissions.rst:53 +#: ../system/objects/permissions.rst:60 +msgid "admin.organization" +msgstr "admin.organization" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Some note to this user`` or empty if not set" -msgstr "``Нека напомена за овог корисника`` или празно ако није постављено" +#: ../system/objects/permissions.rst:43 ../system/objects/permissions.rst:54 +#: ../system/objects/permissions.rst:61 +msgid "admin.group" +msgstr "admin.group" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Mobile" -msgstr "Тренутни корисник > Освежено од стране > Мобилни" +#: ../system/objects/permissions.rst:44 +msgid "Creation dialog for not yet existing data" +msgstr "Дијалог за додавање новог садржаја" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.mobile}``" -msgstr "``#{user.updated_by.mobile}``" +#: ../system/objects/permissions.rst:45 +msgid "create_middle" +msgstr "create_middle" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``0049176123456789`` or empty if not set" -msgstr "``0049176123456789`` или празно ако није постављено" +#: ../system/objects/permissions.rst:46 ../system/objects/permissions.rst:50 +#: ../system/objects/permissions.rst:57 ../system/objects/permissions.rst:66 +#: ../system/objects/permissions.rst:70 +msgid "ticket.customer" +msgstr "ticket.customer" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Login" -msgstr "Тренутни корисник > Освежено од стране > Пријава" +#: ../system/objects/permissions.rst:47 ../system/objects/permissions.rst:51 +#: ../system/objects/permissions.rst:58 ../system/objects/permissions.rst:69 +msgid "ticket.agent" +msgstr "ticket.agent" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.login}``" -msgstr "``#{user.updated_by.login}``" +#: ../system/objects/permissions.rst:48 +msgid "Ticket create dialog (middle section)" +msgstr "Дијалог отварања тикета (средњи део)" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Lastname" -msgstr "Тренутни корисник > Освежено од стране > Презиме" +#: ../system/objects/permissions.rst:49 +msgid "edit" +msgstr "edit" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.lastname}``" -msgstr "``#{user.updated_by.lastname}``" +#: ../system/objects/permissions.rst:55 +msgid "Editing dialog for already existing data" +msgstr "Дијалог за уређивање постојећег садржаја" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Firstname" -msgstr "Тренутни корисник > Освежено од стране > Име" +#: ../system/objects/permissions.rst:56 +msgid "view" +msgstr "view" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.firstname}``" -msgstr "``#{user.updated_by.firstname}``" +#: ../system/objects/permissions.rst:62 +msgid "View-only dialog for already existing data" +msgstr "Дијалог за приказ постојећег садржаја без измена" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``John`` or empty if not set" -msgstr "``John`` или празно ако није постављено" +#: ../system/objects/permissions.rst:64 +msgid "(e.g. user or organization from search)" +msgstr "(нпр. корисник или организација кроз претрагу)" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Fax" -msgstr "Тренутни корисник > Освежено од стране > Факс" +#: ../system/objects/permissions.rst:65 +msgid "signup" +msgstr "signup" + +#: ../system/objects/permissions.rst:67 +msgid "Sign-up screen for new customers" +msgstr "Екран отварања налога за нове клијенте" + +#: ../system/objects/permissions.rst:68 +msgid "invite_customer" +msgstr "invite_customer" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.fax}``" -msgstr "``#{user.updated_by.fax}``" +#: ../system/objects/permissions.rst:71 +msgid "" +"Customer invitation screen (from :doc:`First Steps ` area)" +msgstr "" +"Екран за слање позивнице клијенту (из одељка :doc:`првих корака `)" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``004930123464789`` or empty if not set" -msgstr "``004930123464789`` или празно ако није постављено" +#: ../system/objects/permissions.rst:72 +msgid "invite_agent" +msgstr "invite_agent" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Email" -msgstr "Тренутни корисник > Освежено од стране > Имејл" +#: ../system/objects/permissions.rst:74 +msgid "" +"Agent invitation screen (from :doc:`First Steps ` area)" +msgstr "" +"Екран за слање позивнице оператеру (из одељка :doc:`првих корака `)" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.email}``" -msgstr "``#{user.updated_by.email}``" +#: ../system/objects/permissions.rst:78 +msgid "Screen Options" +msgstr "Опције екрана" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``jdoe@customer.tld``" -msgstr "``jdoe@customer.tld``" +#: ../system/objects/permissions.rst:80 +msgid "" +"For the different screens you can select \"show\" and \"required\" options." +msgstr "За различите екране можете одбрати опције „shown” и „required”." -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Department" -msgstr "Тренутни корисник > Освежено од стране > Одељење" +#: ../system/objects/permissions.rst:82 +msgid "**shown:** Show (check) or hide (uncheck) a field." +msgstr "**shown:** Прикажи (означено) или сакриј (одзначено) поље." -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.department}``" -msgstr "``#{user.updated_by.department}``" +#: ../system/objects/permissions.rst:83 +msgid "" +"**required:** Set a field to mandatory (check). Forces users (via UI and " +"API) to populate the field." +msgstr "" +"**required:** Постављање поља на обавезно (означено). Очекује од корисника " +"да попуне поље (путем корисничког интерфејса и API)." -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Sales`` or empty if not set" -msgstr "``Sales`` или празно ако није подешено" +#: ../system/objects/types.rst:7 +msgid "Example external data source" +msgstr "Пример удаљеног извора података" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Avatar" -msgstr "Тренутни корисник > Освежено од стране > Аватар" +#: ../system/objects/types.rst:2 +msgid "Attribute types" +msgstr "Типови атрибута" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.avatar(60,60)}``" -msgstr "``#{user.updated_by.avatar(60,60)}``" +#: ../system/objects/types.rst:4 +msgid "" +"When adding a new object attribute, you can choose between the following " +"attribute types." +msgstr "" +"Када додајете нови атрибут објекта, можете изабрати између следећих типова " +"атрибута." -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "avatar picture with width and height in pixel (e.g. 60,60)" -msgstr "аватар сличица ширине и висине у пикселима (нпр. 60,60)" +#: ../system/objects/types.rst:14 +msgid "" +"You cannot change the attribute format / type as soon as it is applied. If " +"you no longer need an object attribute, consider disabling it instead of " +"removing." +msgstr "" +"Не можете променити тип / формат атрибута након додавања. Уколико вам више " +"не треба атрибут, узмите у обзир да га искључите уместо да га обришете." -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Address" -msgstr "Тренутни корисник > Освежено од стране > Адреса" +#: ../system/objects/types.rst:18 +msgid "**What about the translation of my attributes?**" +msgstr "**А шта да радим за превод мојих атрибута?**" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.address}``" -msgstr "``#{user.updated_by.address}``" +#: ../system/objects/types.rst:20 +msgid "" +"For some attribute types you can decide if they should be translatable or " +"not. To be precise, it works only for the selectable fields because the " +"possible choices are known and limited. For the following attribute types, " +"you can set the translatable flag:" +msgstr "" +"За неке типове атрибута можете одлучити да ли се могу превести или не. Мало " +"прецизније, функционише само за поља избора зато што су могуће опције " +"познате и ограничене. За следеће типове атрибута можете поставити подешавање " +"превода:" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Some street 1, 12345 Berlin`` or empty if not set" -msgstr "``Назив неке улице 1, 12345 Берлин`` или празно ако није постављено" +#: ../system/objects/types.rst:25 +msgid "*Boolean field*" +msgstr "*Логичко поље*" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated at" -msgstr "Current User > Освежено у" +#: ../system/objects/types.rst:26 +msgid "*Single selection field*" +msgstr "*Поље за једноструки избор*" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_at}``" -msgstr "``#{user.updated_at}``" +#: ../system/objects/types.rst:27 +msgid "*Multiple selection field*" +msgstr "*Поље за вишеструки избор*" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC``" -msgstr "``2019-10-07 16:25:00 UTC``" +#: ../system/objects/types.rst:28 +msgid "*Single tree selection field*" +msgstr "*Поље за једноструки избор стабла*" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Phone" -msgstr "Тренутни корисник > Телефон" +#: ../system/objects/types.rst:29 +msgid "*Multiple tree selection field*" +msgstr "*Поље за вишеструки избор стабла*" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.phone}``" -msgstr "``#{user.phone}``" +#: ../system/objects/types.rst:31 +msgid "" +"For these types, you can find an additional field *Translate field contents*:" +msgstr "За ове типове пронаћи ћете додатну опцију *Преведи садржај поља*:" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Shared organization" -msgstr "Тренутни корисник > Организација > Заједничка организације" +#: ../system/objects/types.rst:0 +msgid "Screenshot showing translatable attribute types" +msgstr "Снимак екрана који приказује типове атрибута који се могу превести" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.shared}``" -msgstr "``#{user.organization.shared}``" +#: ../system/objects/types.rst:38 +msgid "Screenshot with example of translatable attribute type" +msgstr "Снимак екрана са примером типа атрибута који се може превести" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Note" -msgstr "Тренутни корисник > Организација > Напомена" +#: ../system/objects/types.rst:45 +msgid "Boolean field" +msgstr "Логичко поље" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.note}``" -msgstr "``#{user.organization.note}``" +#: ../system/objects/types.rst:41 +msgid "" +"Provides a drop-down field with display values for ``true`` and ``false``. " +"Setting a default is mandatory." +msgstr "" +"Приказује поље за избор са вредностима за ``true``и ``false``. Постављање " +"подразумеване вредности је обавезно." -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``A note to the organization of the user`` or empty if not set" -msgstr "``Напомена организације корисника`` или празно ако није постављено" +#: ../system/objects/types.rst:0 +msgid "Available settings for Boolean fields" +msgstr "Доступна подешавања за логичка поља" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Name" -msgstr "Тренутни корисник > Организација > Назив" +#: ../system/objects/types.rst:55 +msgid "Date field" +msgstr "Поље датума" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.name}``" -msgstr "``#{user.organization.name}``" +#: ../system/objects/types.rst:48 +msgid "Provides a date picker field and does not allow default values." +msgstr "Приказује поље бирача датума и не подржава подразумеване вредности." -#: ../system/variables/current-user.rst:1 -msgid "``Zammad GmbH``" -msgstr "``Zammad GmbH``" +#: ../system/objects/types.rst:52 +msgid "Default time diff (hours)" +msgstr "Подразумевана временска разлика (сати)" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Domain based assignment" -msgstr "Тренутни корисник > Организација > Додела на основу домен" +#: ../system/objects/types.rst:51 +msgid "" +"This setting helps the user by highlighting the day from now plus the " +"provided value. It *does not* pre-fill the field." +msgstr "" +"Ово подешавање помаже кориснику означавањем датума унете временске разлике " +"од сада. *Неће* аутоматски попунити вредност поља." -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.domain_assignment}``" -msgstr "``#{user.organization.domain_assignment}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Date fields" +msgstr "Доступна подешавања поља датума" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Domain" -msgstr "Тренутни корисник > Организација > Домен" +#: ../system/objects/types.rst:73 +msgid "Date & time field" +msgstr "Поље датума и времена" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.domain}``" -msgstr "``#{user.organization.domain}``" +#: ../system/objects/types.rst:58 +msgid "Provides a date and time picker – does not allow default values" +msgstr "Приказује бирач датума и времена – не подржава подразумеване врености" -#: ../system/variables/current-user.rst:1 -msgid "``zammad.com`` or empty if not set" -msgstr "``zammad.com`` или празно ако није постављено" +#: ../system/objects/types.rst:62 +msgid "Allow future" +msgstr "Дозволи у будућности" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > VIP" -msgstr "Тренутни корисник > Организација > VIP" +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the future." +msgstr "Контролише могућност уноса датума и времена у будућности." -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.vip}``" -msgstr "``#{user.organization.vip}``" +#: ../system/objects/types.rst:66 +msgid "Allow past" +msgstr "Дозволи у прошлости" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Note" -msgstr "Тренутни корисник > Напомена" +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the past." +msgstr "Контролише могућност уноса датума и времена у прошлости." -#: ../system/variables/current-user.rst:1 -msgid "``#{user.note}``" -msgstr "``#{user.note}``" +#: ../system/objects/types.rst:70 +msgid "Default time diff (minutes)" +msgstr "Подразумевана временска разлика (минути)" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Mobile" -msgstr "Тренутни корисник > Мобилни" +#: ../system/objects/types.rst:69 +msgid "" +"This setting helps the user by highlighting the day from now plus the " +"provided value. It does not pre-fill the field." +msgstr "" +"Ово подешавање помаже кориснику означавањем датума унете временсе разлике од " +"сада. *Неће* аутоматски попунити вредност поља." -#: ../system/variables/current-user.rst:1 -msgid "``#{user.mobile}``" -msgstr "``#{user.mobile}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Date & time fields" +msgstr "Доступна подешавања за поља датуме и времена" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Login" -msgstr "Тренутни корисник > Пријава" +#: ../system/objects/types.rst:86 +msgid "Integer field" +msgstr "Целобројно поље" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.login}``" -msgstr "``#{user.login}``" +#: ../system/objects/types.rst:76 +msgid "" +"Provides an input field that allows integer usage only. You may define a " +"default value. You cannot enforce comma separation." +msgstr "" +"Приказује поље уноса које дозвољава унос само целобројних вредности. Могуће " +"је дефинисати подразумевану вредност. Није могуће захтевати децималну поделу." -#: ../system/variables/current-user.rst:1 -msgid "Current User > Lastname" -msgstr "Тренутни корисник > Презиме" +#: ../system/objects/types.rst:80 +msgid "Minimal" +msgstr "Минимални" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.lastname}``" -msgstr "``#{user.lastname}``" +#: ../system/objects/types.rst:80 +msgid "The minimal value the field accepts." +msgstr "Минимална вредност коју поље прихвата." -#: ../system/variables/current-user.rst:1 -msgid "Current User > Firstname" -msgstr "Тренутни корисник > Име" +#: ../system/objects/types.rst:83 +msgid "Maximal" +msgstr "Максимални" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.firstname}``" -msgstr "``#{user.firstname}``" +#: ../system/objects/types.rst:83 +msgid "The maximum value the field accepts." +msgstr "Максимална вредност коју поље прихвата." -#: ../system/variables/current-user.rst:1 -msgid "Current User > Fax" -msgstr "Тренутни корисник > Факс" +#: ../system/objects/types.rst:0 +msgid "Available settings for Integer fields" +msgstr "Доступна подешавања целобројних поља" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.fax}``" -msgstr "``#{user.fax}``" +#: ../system/objects/types.rst:99 +msgid "Multiple selection field" +msgstr "Поље за вишеструки избор" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Email" -msgstr "Тренутни корисник > Имејл" +#: ../system/objects/types.rst:89 +msgid "" +"Provides a selection field that allows the selection of one or more out of " +"several. This field does allow setting a default value." +msgstr "" +"Приказује поље падајућег менија које омогућава избор једне или више опција " +"од понуђених. Ово поље дозвољава подешавање подразумеване вредности." -#: ../system/variables/current-user.rst:1 -msgid "``#{user.email}``" -msgstr "``#{user.email}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Multiple selection fields" +msgstr "Доступна подешавања поља вишеструког избора" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Department" -msgstr "Тренутни корисник > Одељење" +#: ../system/objects/types.rst:112 +msgid "Single selection field" +msgstr "Поље за једноструки избор" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.department}``" -msgstr "``#{user.department}``" +#: ../system/objects/types.rst:102 +msgid "" +"Provides a drop-down field that allows selection of one value out of " +"several. This field does allow setting a default value." +msgstr "" +"Приказује поље падајућег менија које омогућава избор једне опције од " +"понуђених. Ово поље дозвољава подешавање подразумеване вредности." -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Web" -msgstr "Тренутни корисник > Додато од стране > Веб" +#: ../system/objects/types.rst:0 +msgid "Available settings for Single selection fields" +msgstr "Доступна подешавања поља једноструког избора" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.web}``" -msgstr "``#{user.created_by.web}``" +#: ../system/objects/types.rst:142 +msgid "Textarea field" +msgstr "Текстуално поље" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > VIP" -msgstr "Тренутни корисник > Додато од стране > VIP" +#: ../system/objects/types.rst:115 +msgid "" +"Provides a text area input field (multiple lines) and thus allows e.g. new " +"lines. You can set a default field value." +msgstr "" +"Приказује поље текстуалног уноса (од више линија) и дозвољава унос нпр. " +"ентера. Можете подесити подразумевану вредност поља." -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.vip}``" -msgstr "``#{user.created_by.vip}``" +#: ../system/objects/types.rst:120 +msgid "" +"Please note that this field *does not* support text formatting or HTML " +"content (rich text)." +msgstr "" +"Обратите пажњу да ово поље *не* подржава форматирање текста или HTML садржај " +"(обогаћен текст)." -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Phone" -msgstr "Тренутни корисник > Додато од стране > Телефон" +#: ../system/objects/types.rst:123 +msgid "**🥵 This field can consume a lot of visual space**" +msgstr "**🥵 Ово поље може заузети доста визуелног простора**" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.phone}``" -msgstr "``#{user.created_by.phone}``" +#: ../system/objects/types.rst:125 +msgid "" +"Depending on where you use this field type, it may use a lot of visual space " +"if you provide a lot of text. This may be an issue to work with." +msgstr "" +"У зависности од тога где користите овај тип поља, могуће је да ће заузети " +"доста визуелног простора по уносу веће количине текста. Ово може " +"представљати проблем при раду." -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Note" -msgstr "Тренутни корисник > Додато од стране > Напомена" +#: ../system/objects/types.rst:130 +msgid "Default" +msgstr "Подразумевано" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.note}``" -msgstr "``#{user.created_by.note}``" +#: ../system/objects/types.rst:129 +msgid "" +"The here provided text will be shown within the text area field or new data " +"sets." +msgstr "" +"Унешен текст овде биће приказан у оквиру текстуалног поља или нових скупова " +"података." -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Mobile" -msgstr "Тренутни корисник > Додато од стране > Мобилни" +#: ../system/objects/types.rst:134 ../system/objects/types.rst:160 +msgid "Maxlength" +msgstr "Максимална дужина" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.mobile}``" -msgstr "``#{user.created_by.mobile}``" +#: ../system/objects/types.rst:0 ../system/objects/types.rst:160 +msgid "You can pick the maximum length of the field." +msgstr "Можете одредити максималну дозвољену дужину поља." -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Login" -msgstr "Тренутни корисник > Додато од стране > Пријава" +#: ../system/objects/types.rst:0 +msgid "The default length of this object is ``500``." +msgstr "Подразумевана дужина за овај објекат је ``500`` карактера." -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.login}``" -msgstr "``#{user.created_by.login}``" +#: ../system/objects/types.rst:139 +msgid "Rows" +msgstr "Редови" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Lastname" -msgstr "Тренутни корисник > Додато од стране > Презиме" +#: ../system/objects/types.rst:0 +msgid "" +"Change the number of rows to dislay so that you can use only the space you " +"really need." +msgstr "" +"Промените број редова за приказ тако да заузмете само простор који вам је " +"заиста неопходан." -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.lastname}``" -msgstr "``#{user.created_by.lastname}``" +#: ../system/objects/types.rst:0 +msgid "The default number of rows is ``4``." +msgstr "Подразумеван број редова је ``4``." -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Firstname" -msgstr "Тренутни корисник > Додато од стране > Име" +#: ../system/objects/types.rst:0 +msgid "Available settings for Textarea fields" +msgstr "Доступна подешавања текстуалних поља" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.firstname}``" -msgstr "``#{user.created_by.firstname}``" +#: ../system/objects/types.rst:165 +msgid "Text field" +msgstr "Поље текста" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Fax" -msgstr "Тренутни корисник > Додато од стране > Факс" +#: ../system/objects/types.rst:145 +msgid "Provides a text field (one line) and allows choosing a default value." +msgstr "" +"Приказује поље текста (у једној линији) и омогућава избор подразумеване " +"вредности." -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.fax}``" -msgstr "``#{user.created_by.fax}``" +#: ../system/objects/types.rst:148 +msgid "" +"Defines the type of the input field. This allows e.g. your browser to ensure " +"that you provide the specific type." +msgstr "" +"Одређује тип уноса поља. Ово омогућава нпр. вашем претраживачу да ограничи " +"унос само одговарајућег типа." -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Email" -msgstr "Тренутни корисник > Додато од стране > Имејл" +#: ../system/objects/types.rst:152 +msgid "Currently available:" +msgstr "Тренутно доступно:" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.email}``" -msgstr "``#{user.created_by.email}``" +#: ../system/objects/types.rst:155 +msgid "Phone" +msgstr "Позив" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Department" -msgstr "Тренутни корисник > Додато од стране > Одељење" +#: ../system/objects/types.rst:156 +msgid "Text" +msgstr "Текст" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.department}``" -msgstr "``#{user.created_by.department}``" +#: ../system/objects/types.rst:157 +msgid "Url *(URL fields disable link-template availability)*" +msgstr "URL *(URL поља онемогућавају шаблоне везе)*" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Avatar" -msgstr "Тренутни корисник > Додато од стране > Аватар" +#: ../system/objects/types.rst:0 +msgid "Available settings for Text fields" +msgstr "Доступна подешавања поља текста" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.avatar(60,60)}``" -msgstr "``#{user.created_by.avatar(60,60)}``" +#: ../system/objects/types.rst:174 +msgid "Single tree selection field" +msgstr "Поље за једноструки избор стабла" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Address" -msgstr "Тренутни корисник > Додато од стране > Адреса" +#: ../system/objects/types.rst:168 +msgid "" +"Provides a select-like field with up to 6 layers of options. Does not allow " +"setting a default value." +msgstr "" +"Приказује поље избора са до 6 нивоа опција. Не омогућава постављање " +"подразумеване вредности." -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.address}``" -msgstr "``#{user.created_by.address}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Tree Select fields" +msgstr "Доступна подешавања поља за избора стабла" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created at" -msgstr "Тренутни корисник > Додато од стране" +#: ../system/objects/types.rst:183 +msgid "Multiple tree selection field" +msgstr "Поље за вишеструки избор стабла" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_at}``" -msgstr "``#{user.created_at}``" +#: ../system/objects/types.rst:177 +msgid "" +"Provides a select-like field with up to 6 layers of options allowing the " +"selection of multiple values. Does not allow setting a default value." +msgstr "" +"Приказује поље избора са до 6 нивоа опција омогућавајући избор вишеструких " +"вредности. Не омогућава постављање подразумеване вредности." -#: ../system/variables/current-user.rst:1 -msgid "Current User > Avatar" -msgstr "Тренутни корисник > Аватар" +#: ../system/objects/types.rst:302 +msgid "External Data Source field" +msgstr "Поље удаљеног извора података" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.avatar(60,60)}``" -msgstr "``#{user.avatar(60,60)}``" +#: ../system/objects/types.rst:186 +msgid "" +"Provides a searchable field which fetches data from an external system. This " +"can be useful if you have data outside of Zammad and don't want to maintain " +"both data sources." +msgstr "" +"Омогућава поље са функцијом претраживања која учитава податке са удаљеног " +"система. Ово може бити корисно ако имате податке изван Zammad-а и не желите " +"да уређујете оба извора података." -#: ../system/variables/current-user.rst:1 -msgid "Current User > Address" -msgstr "Тренутни корисник > Адреса" +#: ../system/objects/types.rst:190 +msgid "The feature works as follows:" +msgstr "Функција ради на следећи начин:" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.address}``" -msgstr "``#{user.address}``" +#: ../system/objects/types.rst:192 +msgid "" +"Zammad sends a query with a search string (free text from agent or based on " +"a variable) in a pre-defined format (\"Search URL\") to an external system." +msgstr "" +"Zammad шаље упит са кључним речима а претрагу (слободан унос текста од " +"стране оператера или на основу променљиве) у предефинисаном формату („URL за " +"претрагу”) удаљеном систему." -#: ../system/variables/ticket.rst:6 +#: ../system/objects/types.rst:195 msgid "" -"Below you can find all available ticket-based variables within Zammad. These " -"can be called via Triggers for example. If you're unsure if Zammad does " -"support variables at the point you're at, you can try to type ``::`` to " -"check." +"This external system searches for matches and provides a response as a JSON " +"structure to Zammad." msgstr "" -"Испод можете пронаћи све доступне променљиве тикета унутар Zammad-а. Могуће " -"их је користити у окидачима, на пример. Ако нисте сигурни да ли Zammad " -"подржава променљиве у неком делу, можете откуцати ``::`` да бисте проверили." - -#: ../system/variables/ticket.rst:12 -msgid "Ticket Variables" -msgstr "Променљиве тикета" +"Удаљени систем претражује податке и обезбељује одговор као JSON структуру за " +"Zammad." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Web" -msgstr "Тикет > Освежено од стране > Веб" +#: ../system/objects/types.rst:197 +msgid "" +"Zammad just looks for the defined list and value keys, reads the content and " +"displays the value to the user. There is no search on Zammad side." +msgstr "" +"Zammad онда обрађује податке на основу дефинисаних кључева листе и " +"вредности, и приказује садржај кориснику. Претрага се не врши на страни " +"Zammad-а." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.web}``" -msgstr "``#{ticket.updated_by.web}``" +#: ../system/objects/types.rst:201 +msgid "" +"The usage of a PostgreSQL database for Zammad is required. In any other " +"case, Zammad will hide the external data source type and you are not able to " +"use it. If you want to use this feature, consider to :docs:`migrate your " +"database `." +msgstr "" +"Коришћење PostgreSQL базе података је захтевано за ову функцију. У сваком " +"другом случају, Zammad ће сакрити избор овог поља и нећете моћи да га " +"користите. Ако желите да користите ову функцију, размотрите и :docs:" +"`миграцију ваше базе података `." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > VIP" -msgstr "Тикет > Освежено од стране > VIP" +#: ../system/objects/types.rst:205 +msgid "Currently, only ``GET`` is supported as request method." +msgstr "Тренутно, подржани су само захтеви путем ``GET`` методе." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.vip}``" -msgstr "``#{ticket.updated_by.vip}``" +#: ../system/objects/types.rst:206 +msgid "" +"The data structure must be in JSON format and provide the objects in an " +"array." +msgstr "" +"Структура података мора бити у JSON формату и враћени објекти морају бити " +"ускладиштени као низ." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Phone" -msgstr "Тикет > Освежено од стране > Телефон" +#: ../system/objects/types.rst:208 +msgid "" +"The endpoint for the external data source has to support search. On Zammad " +"side, there is no search/logic implemented; however, you can define the " +"output key and value based on the result(s) from the response (which " +"provides already filtered content based on the search)." +msgstr "" +"Путања за удаљени извор података мора да подржава претрагу. Са Zammad стране " +"није имплементирана било каква логика претраге; међутим можете дефинисати " +"изворни кључ и вредност на основу резултата одговора (који обезбеђује већ " +"изфилтриран садржај на основу кључних речи)." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.phone}``" -msgstr "``#{ticket.updated_by.phone}``" +#: ../system/objects/types.rst:212 +msgid "" +"If you receive more results as expected, your external data source search " +"may not work properly or the structure of the URL is not correct. You should " +"get in touch with a responsible person from the external system." +msgstr "" +"Уколико примите више резултата од очекиваних, претрага вашег удаљеног извора " +"података можда не ради како треба или структура URL путање није исправна. " +"Ступите у контакт са одговорном особом удаљеног система." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Note" -msgstr "Тикет > Освежено од стране > Напомена" +#: ../system/objects/types.rst:217 +msgid "" +"Please have a look :doc:`at our example `, where you can find a possible configuration for a public " +"dummy endpoint." +msgstr "" +"Погледајте :doc:`наш пример ` " +"са описом могућих подешавања за јавно доступну путању са лажним подацима." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.note}``" -msgstr "``#{ticket.updated_by.note}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for external data source fields" +msgstr "Доступна подешавања за поља удаљеног извора података" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Mobile" -msgstr "Тикет > Освежено од стране > Мобилни" +#: ../system/objects/types.rst:242 +msgid "Search URL" +msgstr "URL за претрагу" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.mobile}``" -msgstr "``#{ticket.updated_by.mobile}``" +#: ../system/objects/types.rst:227 +#, fuzzy +#| msgid "" +#| "Set your endpoint where Zammad fetches the data. Please make sure to " +#| "include a valid search :doc:`variable <../variables>` as an URL " +#| "parameter. Example for a free text search at user input: ``#{search.term}" +#| "``" +msgid "" +"Set your endpoint where Zammad fetches the data. Please make sure to include " +"a valid search :doc:`variable ` as an URL parameter. " +"Example for a free text search at user input: ``#{search.term}``" +msgstr "" +"Одређује путању одакле Zammad преузима податке. Молимо обезбедите исправну :" +"doc:`променљиву <../variables>` претраге као URL параметар. Пример за " +"текстуалну претрагу на основу корисничког уноса: ``#{search.term}``" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Login" -msgstr "Тикет > Освежено од стране > Пријава" +#: ../system/objects/types.rst:232 +#, fuzzy +#| msgid "" +#| "If in doubt, ask the responsible person for the external data source how " +#| "they expect the strucuture of the URL." +msgid "" +"If in doubt, ask the responsible person for the external data source how " +"they expect the structure of the URL." +msgstr "" +"Уколико нисте сигурни, приупитајте особу одговорну за удаљени извор података " +"какву структуру URL адресе очекују." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.login}``" -msgstr "``#{ticket.updated_by.login}``" +#: ../system/objects/types.rst:236 +msgid "" +"Depending on your search variable, the preview might work or not. The reason " +"is that the context might not be available and it is no bug." +msgstr "" +"У зависности од ваше променљиве претраге, приказ може али и не мора " +"функционисати. Разлог је да контекст претраге можда није доступан и ово " +"технички није грешка." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Lastname" -msgstr "Тикет > Освежено од стране > Презиме" +#: ../system/objects/types.rst:239 +msgid "" +"Please also make sure to use a variable which is available in your object " +"context. For example you won't be able to search for a ticket in a user " +"object context." +msgstr "" +"Такође морате обезбедити да користите променљиве које су доступне у " +"контексту вашег објекта. На пример нећете моћи да претражујете за тикете у " +"контексту објекта корисника." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.lastname}``" -msgstr "``#{ticket.updated_by.lastname}``" +#: ../system/objects/types.rst:252 +msgid "SSL Verification" +msgstr "SSL провера" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Firstname" -msgstr "Тикет > Освежено од стране > Име" +#: ../system/objects/types.rst:245 +msgid "Here you can switch the SSL verification to no." +msgstr "Овде можете поставити SSL проверу на не." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.firstname}``" -msgstr "``#{ticket.updated_by.firstname}``" +#: ../system/objects/types.rst:249 +msgid "" +"If your external data source system is using self signed certificates, " +"please have a look :doc:`here ` for " +"further information about how to handle them in Zammad, so you can keep the " +"SSL verification activated." +msgstr "" +"Уколико ваш удаљени извор података користи прилагођени сертификат, молимо " +"погледајте :doc:`овде ` за више детаља " +"како да их увезете у Zammad, тако да можете да оставите укључену SSL проверу." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Fax" -msgstr "Тикет > Освежено од стране > Факс" +#: ../system/objects/types.rst:258 +msgid "HTTP Authentication" +msgstr "HTTP аутентификација" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.fax}``" -msgstr "``#{ticket.updated_by.fax}``" +#: ../system/objects/types.rst:255 +msgid "" +"If your external data source requires an authentication, you can set it " +"here. You can leave it empty or choose between *Basic Authentication* or " +"*Authentication Token* (selecting one of the two methods leads to additional " +"fields where you can enter your credentials/token)." +msgstr "" +"Уколико ваш удаљени извор података захтева аутентификацију, можете је " +"подесити овде. Можете је оставити празном или изабрати између *Basic " +"Authentication* или *Аутентификациони кључ* (одабиром једног од два метода " +"биће приказана додатна поља где можете унети ваше креденцијале/кључ)." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Email" -msgstr "Тикет > Освежено од стране > Имејл" +#: ../system/objects/types.rst:265 +msgid "Search result list key" +msgstr "Кључ листе резулата претраге" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.email}``" -msgstr "``#{ticket.updated_by.email}``" +#: ../system/objects/types.rst:261 +msgid "" +"Defines the level in the JSON structure which provides the list with search " +"results. You can leave it empty, if the data is already provided as an " +"array. If you have to go deeper in the structure, you can provide a path " +"with ``.`` as separators, e.g. ``key.subkey.sub-sub-key``." +msgstr "" +"Одређује ниво у JSON структури који обезбеђује листу резултата претраге. " +"Можете га оставити празним, уколико су подаци већ доступни као низ. Ако " +"желите да идете дубље по структури, можете обезбедити путању са ``.`` као " +"сепаратором, нпр. ``key.subkey.sub-sub-key``." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Department" -msgstr "Тикет > Освежено од стране > Одељење" +#: ../system/objects/types.rst:271 +msgid "Search result value key" +msgstr "Кључ вредности резулата претраге" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.department}``" -msgstr "``#{ticket.updated_by.department}``" +#: ../system/objects/types.rst:268 +msgid "" +"Defines the attribute in the structure in which your external data source " +"provides the *value* for your data. An example would be a product *number*. " +"If you have to go deeper in the structure, you can provide a path with ``.`` " +"as separators, e.g. ``key.subkey.sub-sub-key``." +msgstr "" +"Одређује атрибут у структури у ком ваш удаљени извор података обезбеђује " +"*вредност*. Пример би представљао *број* производа. Уколико желите да идете " +"дубље по структури, можете обезбедити путању са ``.`` као сепаратором, нпр. " +"``key.subkey.sub-sub-key``." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Avatar" -msgstr "Тикет > Освежено од стране > Аватар" +#: ../system/objects/types.rst:277 +msgid "Search result label key" +msgstr "Кључ ознаке резулата претраге" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.avatar(60,60)}``" -msgstr "``#{ticket.updated_by.avatar(60,60)}``" +#: ../system/objects/types.rst:274 +msgid "" +"Defines the attribute in the structure in which your external data source " +"provides the *label* for your data. An example would be a product *name*. If " +"you have to go deeper in the structure, you can provide a path with ``.`` as " +"separators, e.g. ``key.subkey.sub-sub-key``." +msgstr "" +"Одређује атрибут у структури у ком ваш удаљени извор података обезбеђује " +"*ознакз*. Пример би представљао *назив* производа. Уколико желите да идете " +"дубље по структури, можете обезбедити путању са ``.`` као сепаратором, нпр. " +"``key.subkey.sub-sub-key``." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Address" -msgstr "Тикет > Освежено од стране > Адреса" +#: ../system/objects/types.rst:280 +msgid "" +"In the preview area, you can find the following items (depending on your " +"configuration above):" +msgstr "" +"У одељку приказа, можете наћи следеће ставке (у зависности од ваших " +"подешавања изнад):" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.address}``" -msgstr "``#{ticket.updated_by.address}``" +#: ../system/objects/types.rst:283 +msgid "" +"**Error/hint message** (only if configuration is not complete): Zammad tells " +"you, if there is a problem and what you should change in your configuration." +msgstr "" +"**Порука са грешком/упутством** (само ако подешавање није комплетно): Zammad " +"ће вас упутити на то ако постоји проблем и шта треба да промените у вашим " +"подешавањима." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated at" -msgstr "Тикет > Освежено у" +#: ../system/objects/types.rst:286 +msgid "" +"**Search field**: search for an existing attribute in the data source to get " +"a preview. This is required for the fields below to show up." +msgstr "" +"**Поље претраге**: претрага за постојећи унос у удаљеном извору у сврху " +"приказа. Ово поље је обавезно да би се поља испод приказала." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_at}``" -msgstr "``#{ticket.updated_at}``" +#: ../system/objects/types.rst:288 +msgid "" +"**Search result response** (only if configuration is not complete): here you " +"can find a syntax highlighted JSON preview of the response, based on the " +"search term you entered." +msgstr "" +"**Одговор резултата претраге** (само ако подешавање није комплетно): овде " +"можете пронаћи JSON приказ одговора у боји, на основу унетих кључних речи за " +"претрагу." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Title" -msgstr "Тикет > Наслов" +#: ../system/objects/types.rst:291 +msgid "" +"**Search result list** (only if *search result list key* is properly set): " +"output of the structure under the configured *search result list key*." +msgstr "" +"**Листа резултата претраге** (само ако *кључ листе резултата претраге* није " +"исправно подешен): део структуре испод подешеног *кључа листе резултата " +"претраге*." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.title}``" -msgstr "``#{ticket.title}``" +#: ../system/objects/types.rst:294 +msgid "" +"**Preview table** (when fully configured): Zammad shows you a table which " +"includes the found items based on the search string (value, label and " +"optional link). You can use this preview if you don't have the complete data " +"structure of the external system in mind." +msgstr "" +"**Табела приказа** (када је комплетно подешено): Zammad ће вам приказати " +"табелу која укључује нађене уносе на основу кључних речи (вредност, ознаку и " +"опционо линк). Можете користити приказ и када немате потпуну слику о " +"структури података удаљеног система." -#: ../system/variables/ticket.rst:1 +#: ../system/objects/types.rst:299 msgid "" -"``My amazing Subject`` (normally subject, can be edited within Interface and " -"thus differ)" +"An example of a configured external data source field from agent perspective:" msgstr "" -"``Мој екстра наслов`` (обично предмет поруке, може се изменити унутар " -"корисничког интерфејса)" +"Пример подешеног поља удаљеног извора података из перспективе оператера:" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Accounted Time" -msgstr "Тикет > Обрачунато време" +#: ../system/objects/types.rst:0 +msgid "Screencast showing the search for a product in a ticket" +msgstr "Снимак екрана који приказује претрагу производа у тикету" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.time_unit}``" -msgstr "``#{ticket.time_unit}``" +#: ../system/objects/types.rst:307 +msgid "URL fields (Link-Template)" +msgstr "URL адреса поља (шаблон везе)" -#: ../system/variables/ticket.rst:1 -msgid "``1``, ``2.75`` or empty response" -msgstr "``1``, ``2.75`` или празно" +#: ../system/objects/types.rst:311 +msgid "" +"This function is restricted to Text, Select and External data source types " +"only." +msgstr "" +"Ова функција је ограничена само на поља текста, избора и удаљеног извора " +"података." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Tags" -msgstr "Тикет > Ознаке" +#: ../system/objects/types.rst:314 +msgid "" +"Link-Templates are an amazing way to dynamically generate URLs. They allow " +"you to integrate other systems better without having to manually copy data " +"from Zammad if possible." +msgstr "" +"Шаблони везе су сјајан начин за динамичко генерисање URL адреса. Омогућавају " +"вам да боље интегришете удаљене системе без да ручно копирате податке из " +"Zammad-а." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.tags}``" -msgstr "``#{ticket.tags}``" +#: ../system/objects/types.rst:320 +msgid "" +"Another great way of communicating with another system may be Zammad's :doc:" +"`Webhooks `." +msgstr "" +"Још један сјајан начин за комуникацију са удаљеним системима могу бити и " +"Zammad-ови :doc:`повратни позиви `." -#: ../system/variables/ticket.rst:1 +#: ../system/objects/types.rst:323 msgid "" -"Currently not available, see `Issue 2769 `_" +"After filling a link-template enabled field, an URL icon will appear on its " +"right. Clicking on the icon opens a new tab." msgstr "" -"Тренутно није доступно, погледајте `извештај 2769 `_" +"По уносу поља са подешеним шаблоном везе, URL иконица ће се појавити са " +"његове десне стране. Клик на иконицу ће отворити нови језичак." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > State > Name" -msgstr "Тикет > Стање > Назив" +#: ../system/objects/types.rst:328 +msgid "" +"Even though Zammad displays the link template within object edit and create " +"screens, the function is optional. It's only active if you populate the " +"field." +msgstr "" +"Иако Zammad приказује подешавање шаблона везе у оквиру дијалога додавања и " +"уређивања објекта, функција је опциона. Биће активна само ако га подесите." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.state.name}``" -msgstr "``#{ticket.state.name}``" +#: ../system/objects/types.rst:333 +msgid "" +"What's the difference between URL and text fields with link template...?!" +msgstr "Која је разлика између URL и поља текста са шаблоном везе…?!" -#: ../system/variables/ticket.rst:1 -msgid "``new``, ``open``, ..." -msgstr "``new``, ``open``, ..." +#: ../system/objects/types.rst:335 +msgid "" +"Both fields have different use cases. Use ``text`` type text fields when " +"ever you have a *static* url that requires dynamic parameters. If you " +"require a drag & drop like field that you can put in any URL, use ``URL`` " +"type text fields." +msgstr "" +"Оба типа поља имају различите употребну вредност. Користите поље текста типа " +"``text`` кад год имате *статичку* URL адресу која захтева динамичке " +"параметре. Ако захтевате поље у које желите да унесете било коју URL адресу, " +"користите поље текста типа ``URL``." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Priority > Name" -msgstr "Тикет > Приоритет > Назив" +#: ../system/objects/types.rst:340 +msgid "" +"The difference is easier to spot when comparing the fields directly, below " +"screencast shows the result - the dynamic approach uses existing values in " +"the moment of updating to built the URL - e.g. ``https://google.com/search?" +"q=cookies`` - while the URL approach uses the actual URL of the field - e.g. " +"``https://zammad.com``." +msgstr "" +"Разлика је лакша за приметити када поредите поља једно поред другог, снимак " +"екрана испод приказује резултат – динамички приступ користи постојеће " +"вредности у тренутку освежавања да би генерисао URL – нпр. ``https://google." +"com/search?q=cookies`` – док URL приступ користи дотичну URL адресу поља – " +"нпр. ``https://zammad.com``." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.priority.name}``" -msgstr "``#{ticket.priority.name}``" +#: ../system/objects/types.rst:None +msgid "" +"Screencast showing the differents in between URL and text type fields with " +"actual values" +msgstr "" +"Снимак екрана који приказује разлику између URL и поља текста са стварним " +"вредностима" -#: ../system/variables/ticket.rst:1 -msgid "``2 normal``" -msgstr "``2 normal``" +#: ../system/objects/types.rst:352 +msgid "How does this work...?!" +msgstr "Како то уствари функционише?!" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Pending till" -msgstr "Тикет > На чекању до" +#: ../system/objects/types.rst:354 +msgid "" +"As an example, let's say you have an attribute called ``amazing_attribute`` " +"and you want to open a google search directly with the input from that field." +msgstr "" +"Као пример, рецимо да имате објекат под називом ``amazing_attribute`` и " +"желите да отворите страну претраге директно на основу уноса тог поља." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.pending_time}``" -msgstr "``#{ticket.pending_time}``" +#: ../system/objects/types.rst:357 +msgid "" +"Providing the link-template field below allows you to do so: ``https://www." +"google.com/search?q=#{ticket.amazing_attribute}``" +msgstr "" +"Следећа вредност за шаблон везе вам омогућује баш то: ``https://www.google." +"com/search?q=#{ticket.amazing_attribute}``" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not set" -msgstr "``2019-10-07 16:25:00 UTC`` или празно ако није постављено" +#: ../system/objects/types.rst:362 +#, fuzzy +#| msgid "" +#| "You can use any :doc:`Zammad variable ` as long as " +#| "it's available in the moment you need it." +msgid "" +"You can use any :doc:`Zammad variable ` as long as it's " +"available in the moment you need it." +msgstr "" +"Можете користити било коју :doc:`Zammad променљиву ` све " +"док је доступна у тренутку када вам је неопходна." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Web" -msgstr "Тикет > Власник > Веб" +#: ../system/objects/types.rst:365 +msgid "" +"As a result, you are redirected to Google with a search for the value of the " +"attribute, if you click on the button in the ticket (as you can see in the " +"screencast above)." +msgstr "" +"Као резултат, ако кликнете на дугме у тикету (као на снимку екрана изнад) " +"бићете преусмерени на страну претраге за вредност атрибута." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.web}``" -msgstr "``#{ticket.owner.web}``" +#: ../system/packages.rst:2 +msgid "Packages" +msgstr "Пакети" -#: ../system/variables/ticket.rst:1 -msgid "``https://zammad.com`` or empty if not set" -msgstr "``https://zammad.com`` или празно ако није постављено" +#: ../system/packages.rst:4 +msgid "That's the package management-area." +msgstr "Ово је одељак за уређивање пакета." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > VIP" -msgstr "Тикет > Власник > VIP" +#: ../system/packages.rst:6 +msgid "Individual add-ons for Zammad can be installed and managed here." +msgstr "Појединални додаци за Zammad се могу инсталирати и уређивати одавде." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.vip}``" -msgstr "``#{ticket.owner.vip}``" +#: ../system/sessions.rst:2 +msgid "Sessions" +msgstr "Сесије" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Phone" -msgstr "Тикет > Власник > Телефон" +#: ../system/sessions.rst:4 +msgid "" +"Sessions management allows reviewing currently known user sessions and " +"allows to end these. The session timeout is affected by :ref:" +"`security_session_timeout` configurations from security settings." +msgstr "" +"Управљање сесијама омогућава преглед тренутно активних корисничких сесија и " +"њихово уклањање. Време истека сесије је под утицајем :ref:" +"`security_session_timeout` подешавања из одељка безбедности." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.phone}``" -msgstr "``#{ticket.owner.phone}``" +#: ../system/sessions.rst:None +msgid "Screenshot showing Zammad's session management" +msgstr "Снимак екрана који приказује уређивање сесија у Zammad-у" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Note" -msgstr "Тикет > Власник > Напомена" +#: ../system/sessions.rst:13 +msgid "Zammad will provide the following information:" +msgstr "Zammad обезбеђује следеће информације:" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.note}``" -msgstr "``#{ticket.owner.note}``" +#: ../system/sessions.rst:16 +msgid "" +"The user account this session entry belongs to. It can be normal if a user " +"has several sessions in the list. This can be due to changed browser " +"information or if you use e.g. single sign on methods where the user does " +"not use the log off button." +msgstr "" +"Кориснички налог коме припада дотична сесија. Сасвим је нормално да корисник " +"има неколико сесија у листи. До овога може доћи услед промене претраживача " +"или уколико се користи нпр. метод јединствене пријаве и корисник не користи " +"дугме за одјаву." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Mobile" -msgstr "Тикет > Власник > Мобилни" +#: ../system/sessions.rst:22 +msgid "Browser" +msgstr "Претраживач" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.mobile}``" -msgstr "``#{ticket.owner.mobile}``" +#: ../system/sessions.rst:22 +msgid "The browser agent communicated to Zammad." +msgstr "Агент претраживача који је пријављен Zammad-у." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Login" -msgstr "Тикет > Власник > Пријава" +#: ../system/sessions.rst:40 +msgid "Location" +msgstr "Локација" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.login}``" -msgstr "``#{ticket.owner.login}``" +#: ../system/sessions.rst:25 +msgid "" +"The anticipated location based on the users IP address. Depending on the IP " +"address the result shown may differ. This option depends on :doc:`/settings/" +"system/services`." +msgstr "" +"Локација на основу корисничке IP адресе. У зависности од IP адресе резултат " +"се може разликовати. Ова опција зависи од :doc:`/settings/system/services`." -#: ../system/variables/ticket.rst:1 -msgid "``agent``" -msgstr "``agent``" +#: ../system/sessions.rst:29 +msgid "The following information can be shown:" +msgstr "Следеће информације могу бити приказане:" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Lastname" -msgstr "Тикет > Власник > Презиме" +#: ../system/sessions.rst:33 +msgid "IP address" +msgstr "IP адреса" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.lastname}``" -msgstr "``#{ticket.owner.lastname}``" +#: ../system/sessions.rst:32 +msgid "" +"Either if you set *Geo IP services* to inactive or you're using internal IP " +"address which do not provide location information." +msgstr "" +"Уколико искључите *сервис географског IP* или ако користите интерну IP " +"адресу која не открива локацију." -#: ../system/variables/ticket.rst:1 -msgid "``Mustermann`` or empty if not set" -msgstr "``Mustermann`` или празно ако није постављено" +#: ../system/sessions.rst:40 +msgid "Country (or Country + City)" +msgstr "Држава (или држава + град)" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Firstname" -msgstr "Тикет > Власник > Име" +#: ../system/sessions.rst:36 +msgid "" +"If *Geo IP services* is enabled only. Depends on how detailed the available " +"IP address information are." +msgstr "" +"Само уколико је *сервис географског IP* укључен. Зависи од тога колико су " +"детаљне доступне информације о IP адреси." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.firstname}``" -msgstr "``#{ticket.owner.firstname}``" +#: ../system/sessions.rst:39 +msgid "" +"Be aware that results can be inaccurate - this technically is not an error." +msgstr "Обратите пажњу да подаци могу бити нетачни – технички ово није грешка." -#: ../system/variables/ticket.rst:1 -msgid "``Max`` or empty if not set" -msgstr "``Max`` или празно ако није постављено" +#: ../system/sessions.rst:43 +msgid "Age" +msgstr "Старост" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Fax" -msgstr "Тикет > Власник > Факс" +#: ../system/sessions.rst:43 +msgid "Provides the time when the session initially has been created." +msgstr "Обезбеђује време од када је сесија иницијално креирана." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.fax}``" -msgstr "``#{ticket.owner.fax}``" +#: ../system/sessions.rst:50 +msgid "Update" +msgstr "Освежавање" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Email" -msgstr "Тикет > Власник > Имејл" +#: ../system/sessions.rst:46 +msgid "" +"Provides the time the user used this session to open Zammad. This timestamp " +"is only updated if the user e.g. reloads, not during normal work on tickets." +msgstr "" +"Обезбеђује време када је корисник користио сесију да приступи Zammad-у. Ова " +"временска вредност ће бити освежена само ако корисник нпр. поново учита " +"апликацију, али не и при стандардном раду на тикетима." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.email}``" -msgstr "``#{ticket.owner.email}``" +#: ../system/sessions.rst:50 +msgid "This timestamp is being used for the session timeout." +msgstr "Ова временска вредност се користи за обрачун времена истека сесије." -#: ../system/variables/ticket.rst:1 -msgid "``agent@company.tld`` or empty if not set" -msgstr "``agent@company.tld`` или празно ако није постављено" +#: ../system/sessions.rst:53 +msgid "" +"Use the delete button to remove a single session on behalf of your user." +msgstr "" +"Користите дугме за брисање да бисте одјавили појединачну сесију вашег " +"корисника." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Department" -msgstr "Тикет > Власник > Одељење" +#: ../system/subscription.rst:2 +msgid "Subscription (SaaS)" +msgstr "Претплата (SaaS)" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.department}``" -msgstr "``#{ticket.owner.department}``" +#: ../system/subscription.rst:4 +msgid "" +"The subscription settings page allows you to configure your instances " +"package and number of agents required." +msgstr "" +"Страна подешавање претплате вам омогућава да подесите пакет ваше инстанце и " +"неопходан број оператера." -#: ../system/variables/ticket.rst:1 -msgid "``Support`` or empty if not set" -msgstr "``Support`` или празно ако није постављено" +#: ../system/subscription.rst:9 +msgid "" +"This setting section is only available for Hosted setups. If you're looking " +"for on premise support contracts, please see the `Zammad pricing page " +"`_." +msgstr "" +"Овај одељак подешавања је доступан само у хостованим инстанцама. Ако тражите " +"уговор за подршку, молимо погледајте `Zammad ценовник `_." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Avatar" -msgstr "Тикет > Власник > Аватар" +#: ../system/subscription.rst:14 ../system/subscription.rst:34 +msgid "Plan" +msgstr "План" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.avatar(60,60)}``" -msgstr "``#{ticket.owner.avatar(60,60)}``" +#: ../system/subscription.rst:16 +#, fuzzy +#| msgid "" +#| "Everything affecting your instance subscription functions like number of " +#| "agents, package and payment method." +msgid "" +"Here you can set up everything affecting your instance subscription " +"functions like number of agents and package." +msgstr "" +"Све у вези претплате ваше инстанце као што су број оператера, пакет и начин " +"плаћања." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Address" -msgstr "Тикет > Власник > Адреса" +#: ../system/subscription.rst:19 +#, fuzzy +#| msgid "" +#| "On the top of the subscription summary you'll find the number of used and " +#| "available (booked) agent seats. By using the *see more* link you can also " +#| "expand an agent list to see the currently configured active agents. This " +#| "list *does not* count accounts with admin permissions only." +msgid "" +"On top of the page you can find a subscription summary. You'll find the " +"number of used and available (booked) agent seats there. By using the *see " +"more* link you can also expand an agent list to see the currently configured " +"active agents. This list *does not* count accounts with admin permissions " +"only." +msgstr "" +"Изнад прегледа претплате наћи ћете број коришћених и доступних (купљених) " +"налога оператера. Коришћењем линка *прикажи више* такође можете увећати " +"листу оператера да видите тренутно подешене, активне оператере. Ова листа " +"*не укључује* налоге само са дозволама администратора." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.address}``" -msgstr "``#{ticket.owner.address}``" +#: ../system/subscription.rst:None +msgid "" +"Within subscription you can always see how many agents are still\n" +"available to add and who uses the seats." +msgstr "" +"У оквиру претплате увек можете проверити колико оператера је још\n" +"увек достпуно и ко користи налоге." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Shared organization" -msgstr "Тикет > Организација > Заједничка организација" +#: ../system/subscription.rst:29 +msgid "" +"Learn more on how to manage your agents in general :doc:`here `." +msgstr "" +"Сазнајте више о начину управљања вашим оператерима :doc:`овде `." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.shared}``" -msgstr "``#{ticket.organization.shared}``" +#: ../system/subscription.rst:36 +msgid "" +"This section gives you an overview of the available plans and their " +"functions / limits. If you require a more detailed table, check our " +"`detailed pricing table `_ for more." +msgstr "" +"Овај одељак вам даје преглед доступним планова и њихових функција / " +"ограничења. Уколико су вам потребне детаљније информације, погледајте наш " +"`детаљну табелу ценовника `." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Note" -msgstr "Тикет > Организација > Напомена" +#: ../system/subscription.rst:40 +msgid "" +"Your selection in this step will decide on the base agent price and e.g. " +"agent limits that might apply in the summary step." +msgstr "" +"Ваш избор у овом кораку ће одредити основну цену оператера и нпр. ограничења " +"оператера која су приказана у прегледу." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.note}``" -msgstr "``#{ticket.organization.note}``" +#: ../system/subscription.rst:43 +msgid "" +"The green *Selected* button will also tell you what plan you're currently in." +msgstr "Зелено дугме *изабрано* ће вам такође рећи на ком сте тренутно плану." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Name" -msgstr "Тикет > Организација > Назив" +#: ../system/subscription.rst:47 +msgid "" +"Trial instances are running at Professional with 3 agents. The plan cannot " +"be changed during the trial for technical reasons, if you require more " +"agents for testing, please contact `our sales team `_ with a reason for the raise request." +msgstr "" +"Пробне инстанце раде под Professional пакетом са 3 оператера. План није " +"могуће променити током пробног периода из техничких разлога, ако вам је " +"неопходно више оператера за тестирање, молимо контактирајте `наш тим продаје " +"`_ са разлогом за увећање." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.name}``" -msgstr "``#{ticket.organization.name}``" +#: ../system/subscription.rst:None +msgid "" +"Screenshot showing three available packages for a hosted Zammad\n" +"instance" +msgstr "" +"Снимак екрана приказује три доступна пакета хостованих Zammad\n" +"инстанци" -#: ../system/variables/ticket.rst:1 -msgid "``Zammad GmbH`` or empty if not set" -msgstr "``Zammad GmbH`` или празно ако није постављено" +#: ../system/subscription.rst:57 +#, fuzzy +#| msgid "" +#| "In this section you can adjust the settings of the previous selected plan." +msgid "" +"At the bottom of this block you can find a summary where you can adjust the " +"settings of the previous selected plan." +msgstr "У овом одељку можете подесити подешавања претходно изабраног плана." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Domain based assignment" -msgstr "Тикет > Организација > Додела на основу домена" +#: ../system/subscription.rst:62 +msgid "" +"Note that upgrading (more agents, higher package) is always possible, " +"however, downgrading will only happen when your billing period renews." +msgstr "" +"Обратите пажњу да је унапређење (више оператера, скупљи пакет) увек могуће, " +"док је повратак назад могућ само при обнављању вашег уговорног периода." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.domain_assignment}``" -msgstr "``#{ticket.organization.domain_assignment}``" +#: ../system/subscription.rst:66 +msgid "" +"Upgrading resets your billing period and existing credit will be deducted " +"from the new total." +msgstr "" +"Унапређење ће ресетовати ваш уговорни период и цена ће бити умањена за " +"тренутни износ." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Domain" -msgstr "Тикет > Организација > Домен" +#: ../system/subscription.rst:75 +msgid "Billing cycle" +msgstr "Обрачунски период" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.domain}``" -msgstr "``#{ticket.organization.domain}``" +#: ../system/subscription.rst:70 +msgid "" +"You can choose between either monthly or yearly billing. The price per agent " +"will be cheaper if you decide for yearly billing." +msgstr "" +"Увек можете одабрати између месечне и годишње наплате. Цена по оператеру је " +"нижа ако се одлучите за годишњу наплату." -#: ../system/variables/ticket.rst:1 -msgid "``domain.tld`` or empty if not set" -msgstr "``domain.tld`` или празно ако није постављено" +#: ../system/subscription.rst:73 +msgid "" +"If you're still trying out things and are unsure of the right package for " +"your instance, you may want to choose monthly first and then upgrade to " +"yearly when you're sure." +msgstr "" +"Ако још увек испробавате ствари и нисте сигурни који је пакет најбољи за " +"вашу инстанцу, можда ћете желети да прво одаберете месечну наплату и после " +"унапредите на годишњу када будете сигурни." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > VIP" -msgstr "Тикет > Организација > VIP" +#: ../system/subscription.rst:83 +msgid "Plan: (Starter|Professional|Plus) - Agents" +msgstr "План: (Starter|Professional|Plus) - Оператери" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.vip}``" -msgstr "``#{ticket.organization.vip}``" +#: ../system/subscription.rst:78 +msgid "Choose the number of agents you require for your instance." +msgstr "Одаберите број оператера који су вам неопходни у вашој инстанци." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Number" -msgstr "Тикет > Број" +#: ../system/subscription.rst:80 +msgid "" +"Keep in mind that some packages may have agent limits. Depending on the " +"previous chosen package, you won't be able to exceed specific agent numbers. " +"Also note that setting less agents than currently configured is not possible." +msgstr "" +"Обратите пажњу да неки пакети имају ограничење у броју оператера. У " +"зависности од претходно одабраног пакета, нећете бити у могућности да " +"прекорачите одређени број оператера. Такође имајте на уму да избор броја " +"оператера нижи од подешеног није могућ." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.number}``" -msgstr "``#{ticket.number}``" +#: ../system/subscription.rst:86 +msgid "Total" +msgstr "Укупно" -#: ../system/variables/ticket.rst:1 -msgid "``31001``, ``201910731001``, ..." -msgstr "``31001``, ``201910731001``, ..." +#: ../system/subscription.rst:86 +msgid "This will be the net total you're going to be billed." +msgstr "Ово представља укупну нето цифру која ће вам бити наплаћена." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > ID" -msgstr "Тикет > ID" +#: ../system/subscription.rst:88 +msgid "" +"By using the *Update subscription* button, the instance package will be " +"adjusted immediately. If you didn't provide a payment method yet, Zammad " +"will request you to provide one at this point." +msgstr "" +"Коришћењем дугмета *Освежите претплату*, пакет инстанце ће бити моментално " +"измењен. Уколико још увек нисте додали начин плаћања, Zammad ће захтевати да " +"га обезбедите у овом тренутку." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.id}``" -msgstr "``#{ticket.id}``" +#: ../system/subscription.rst:94 +msgid "" +"In case you're still within the trial period, this means that the trial will " +"be over immediately!" +msgstr "" +"У случају да сте још увек у оквиру пробног периода, ово значи да ће пробни " +"период одмах бити завршен!" -#: ../system/variables/ticket.rst:1 -msgid "``17``, ``5281``, ..." -msgstr "``17``, ``5281``, ..." +#: ../system/subscription.rst:97 +msgid "Down- or upgrading during the trial period *is not* possible." +msgstr "" +"Враћање на претходни пакет или унапређење пакета током пробном периода *није " +"могуће*." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact (customer)" -msgstr "Тикет > Последњи одговор (клијент)" +#: ../system/subscription.rst:None +msgid "Screenshot showing payment options and a pricing summary" +msgstr "Снимак екрана који приказује начине плаћања и преглед цена" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_customer_at}``" -msgstr "``#{ticket.last_contact_customer_at}``" +#: ../system/subscription.rst:103 +#, fuzzy +#| msgid "Billing information" +msgid "Billing Information" +msgstr "Информације о наплати" -#: ../system/variables/ticket.rst:1 +#: ../system/subscription.rst:105 +#, fuzzy +#| msgid "" +#| "Within the billing tab you can control all billing relevant information " +#| "like invoices, billing address and the option to cancel your subscription." msgid "" -"``2019-10-07 16:25:00 UTC`` or empty if not applicable yet (Please note " -"`Ticket last contact behavior Settings `_ for this)" +"You can control all billing relevant information like invoices, billing " +"address and the option to cancel your subscription." msgstr "" -"``2019-10-07 16:25:00 UTC`` или празно ако не постоји (Обратите пажњу на " -"`подешавање понашања последњег одговора тикета `_)" - -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact" -msgstr "Тикет > Последњи одговор" +"У оквиру језичка наплате можете прегледати све релевантне податке као што су " +"рачуни, адреса за наплату и опција за прекид претплате." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_at}``" -msgstr "``#{ticket.last_contact_at}``" +#: ../system/subscription.rst:108 +msgid "" +"All adjusted billing information below only affect future invoices. If your " +"invoice was issued wrong, please contact `our sales team `_." +msgstr "" +"Све измене података наплате испод ће утицати само на будуће рачуне. Ако је " +"издати рачун погрешан, молимо контактирајте `наш тим продаје `_." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact (agent)" -msgstr "Тикет > Последњи одговор (оператер)" +#: ../system/subscription.rst:114 +msgid "Billing address" +msgstr "Адреса за наплату" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_agent_at}``" -msgstr "``#{ticket.last_contact_agent_at}``" +#: ../system/subscription.rst:113 +msgid "" +"Provide your company address here, make sure to include the companies name " +"in case required. This address will be referenced on your invoice." +msgstr "" +"Овде унесите адресу ваше фирме, али водите рачуна да укључите и назив фирме " +"у случају да је потребно. Ова адреса ће бити укључена у ваш рачун." -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable yet" -msgstr "``2019-10-07 16:25:00 UTC`` или празно ако не постоји" +#: ../system/subscription.rst:118 +msgid "VAT ID" +msgstr "ПДВ број" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Note" -msgstr "Тикет > Група > Напомена" +#: ../system/subscription.rst:117 +msgid "" +"Provide your VAT ID here. If applicable your invoice will not contain German " +"VAT. Please make sure to pay the VAT in your country as required." +msgstr "" +"Овде унесите ваш ПДВ број (ПИБ). Ако се не односи на вас, рачун неће " +"обрачунати немачки ПДВ. Водите рачуна да платите ПДВ у вашој земљи ако је " +"потребно." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.note}``" -msgstr "``#{ticket.group.note}``" +#: ../system/subscription.rst:127 +msgid "Billing Email Address" +msgstr "Имејл адреса за наплату" -#: ../system/variables/ticket.rst:1 -msgid "``Note about this group``" -msgstr "``Напомена о овој групи`" +#: ../system/subscription.rst:121 +msgid "" +"Usually the instance owner (the person that registered the instance) will " +"receive all emails including the invoices. In case you have your own billing " +"department, you can provide their email address here." +msgstr "" +"Обично ће власник инстанце (особа која је регистровала инстанцу) примити све " +"имејл поруке укључујући и рачуне. У случају да имате посебно одељење за " +"наплату, овде можете унети њихову имејл адресу." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Name" -msgstr "Тикет > Група > Назив" +#: ../system/subscription.rst:125 +msgid "" +"All billing relevant information will then be sent to this email address." +msgstr "" +"Све информације у вези наплате ће убудуће бити послате на ову имејл адресу." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.name}``" -msgstr "``#{ticket.group.name}``" +#: ../system/subscription.rst:127 +msgid "Invoices are sent as attachment (PDF) to this email address." +msgstr "Рачун се шаљу као прилози (PDF) на ову имејл адресу." -#: ../system/variables/ticket.rst:1 -msgid "``Sales``" -msgstr "``Sales``" +#: ../system/subscription.rst:129 +#, fuzzy +#| msgid "" +#| "Don't forget to press the *Submit* button after you changed above " +#| "settings." +msgid "" +"Don't forget to press the *Update billing information* button after you " +"changed above settings." +msgstr "Не заборавите да кликнете на *Пошаљи* по изменама подешавања изнад." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Follow-up possible" -msgstr "Тикет > Група > Могућ наставак" +#: ../system/subscription.rst:None +msgid "" +"Screenshot showing options for billing information within the\n" +"subscription menu" +msgstr "" +"Снимак екрана који приказује опције наплате у оквиру\n" +"менија претплате" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.follow_up_possible}``" -msgstr "``#{ticket.group.follow_up_possible}``" +#: ../system/subscription.rst:137 +#, fuzzy +#| msgid "Payment method" +msgid "Payment Method" +msgstr "Начин плаћања" -#: ../system/variables/ticket.rst:1 -msgid "``no`` or ``yes``" -msgstr "``no`` или ``yes``" +#: ../system/subscription.rst:139 +msgid "You can pay via credit card or SEPA mandate." +msgstr "Моћете платити уз помоћ кредитне картице или SEPA налога." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Assign Follow-Ups" -msgstr "Тикет > Група > Додели наставке" +#: ../system/subscription.rst:144 +msgid "Credit card" +msgstr "Кредитна картица" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.follow_up_assignment}``" -msgstr "``#{ticket.group.follow_up_assignment}``" +#: ../system/subscription.rst:142 +#, fuzzy +#| msgid "" +#| "Simply follow the dialogue by clicking *authorize* and confirm -if " +#| "required by your bank- your consent to Zammad using your card for the " +#| "payments." +msgid "" +"Simply follow the dialogue by clicking *authorize credit card* and confirm -" +"if required by your bank- your consent to Zammad using your card for the " +"payments." +msgstr "" +"Једноставно пратите упутства кликом на *ауторизуј* и потврдите – уколико је " +"неопходно преко ваше банке – вашу сагласност са тим да Zammad користи вашу " +"картицу за наплату." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Assignment Timeout" -msgstr "Тикет > Група > Време истека доделе" +#: ../system/subscription.rst:148 +msgid "SEPA Direct Debit" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.assignment_timeout}``" -msgstr "``#{ticket.group.assignment_timeout}``" +#: ../system/subscription.rst:147 +msgid "" +"Provide the requested information of the bank account holder and update if " +"you're ready. You'll then receive an email with the SEPA mandate." +msgstr "" +"Обезбедите захтеване податке о држаоцу рачуна и освежите их ако сте спремни. " +"Након тога примићете имејл са SEPA налогом." -#: ../system/variables/ticket.rst:1 -msgid "``20`` or empty if not configured" -msgstr "``20`` или празно ако није постављено" +#: ../system/subscription.rst:150 +msgid "" +"Technically there's also the possibility to pay via invoice, however - this " +"method only applies to a fairly low number of instances. Please contact `our " +"sales team `_ for more information." +msgstr "" +"Технички гледано постоји и могућност наплате путем фактуре, међутим – овај " +"начин се односи само на мали број инстанци. Молимо контактирајте `наш тим " +"продаје `_ за више информација." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > First response" -msgstr "Тикет > Први одговор" +#: ../system/subscription.rst:156 +#, fuzzy +#| msgid "Subscription" +msgid "Cancel Subscription" +msgstr "Претплата" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.first_response_at}``" -msgstr "``#{ticket.first_response_at}``" +#: ../system/subscription.rst:158 +#, fuzzy +#| msgid "" +#| "In case you no longer want to use Zammad's SaaS, you can cancel your " +#| "subscription by using the red *Yes, please cancel my subscription* button." +msgid "" +"Do you want to cancel your subscription? In case you no longer want to use " +"Zammad's SaaS, you can cancel your subscription by using the red *Yes, " +"please cancel my subscription* button." +msgstr "" +"У случају да не желите више да користите Zammad SaaS, можете отказати своју " +"претплату коришћењем црвеног дугмета *Да, откажите моју претплату*." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Escalation at" -msgstr "Тикет > Ескалација у" +#: ../system/subscription.rst:162 +msgid "" +"To cancel the description, enter the FQDN of your Zammad instance and " +"provide a reason for your cancellation." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.escalation_at}``" -msgstr "``#{ticket.escalation_at}``" +#: ../system/subscription.rst:165 +msgid "" +"Your subscription will end the day after your trial or billing period ends." +msgstr "" +"Ваша претплата ће истећи дан након што се заврше ваш пробни или период " +"наплате." -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable" -msgstr "``2019-10-07 16:25:00 UTC`` или празно ако не постоји" +#: ../system/subscription.rst:None +#, fuzzy +#| msgid "Screenshot showing certificate adding dialog" +msgid "Screenshot showing subscription cancellation dialog" +msgstr "Снимак екрана који приказује дијалог за додавање сертификата" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Web" -msgstr "Тикет > Клијент > Веб" +#: ../system/subscription.rst:174 +msgid "" +"We will remind you about your cancelled subscription several times up front. " +"After the subscription ended all instance data will be removed. A restore " +"*is not* possible after that point!" +msgstr "" +"Обавестићемо вас о отказаној претплати неколико пута. Након престанка " +"претплате сви подаци ваше инстанце ће бити уклоњени. Након овог тренутка " +"*није могуће* вратити податке!" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.web}``" -msgstr "``#{ticket.customer.web}``" +#: ../system/subscription.rst:178 +msgid "**😖 Cancelled by accident?**" +msgstr "**😖 Отказали сте грешком?**" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > VIP" -msgstr "Тикет > Клијент > VIP" +#: ../system/subscription.rst:180 +msgid "" +"You can always undo the cancellation via the *Yes, undo the cancellation of " +"my subscription* button up to the last subscription day!" +msgstr "" +"Увек можете одустати од отказивања путем дугмета *Да, одустани од отказивања " +"моје претплате* све до последњег дана пре истека претплате!" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.vip}``" -msgstr "``#{ticket.customer.vip}``" +#: ../system/subscription.rst:0 +msgid "" +"Screenshot showing a red button to cancel the subscription\n" +"cancellation" +msgstr "" +"Снимак екрана који приказује црвено дугме за одустајање од\n" +"отказивања претплате" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Phone" -msgstr "Тикет > Клијент > Телефон" +#: ../system/subscription.rst:189 +#, fuzzy +#| msgid "Payment history" +msgid "Payment History" +msgstr "Историјат плаћања" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.phone}``" -msgstr "``#{ticket.customer.phone}``" +#: ../system/subscription.rst:191 +msgid "" +"The payment history will display a history of all paid invoices. At this " +"point you can also download these in case you need them again." +msgstr "" +"Историјат плаћања приказује евиденцију свих плаћених рачуна. Овде можете " +"преузети рачуне у случају да су вам поново потребни." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Note" -msgstr "Тикет > Клијент > Напомена" +#: ../system/subscription.rst:196 +msgid "" +"You will only find *paid* invoices here. Invoices that are to be billed are " +"not available before the payment is completed." +msgstr "" +"Овде ћете наћи само *плаћене* рачуне. Рачуни који још нису плаћени нису " +"доступни." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.note}``" -msgstr "``#{ticket.customer.note}``" +#: ../system/subscription.rst:201 +msgid "Date" +msgstr "Датум" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Mobile" -msgstr "Тикет > Клијент > Мобилни" +#: ../system/subscription.rst:201 +msgid "Date of the invoice creation." +msgstr "Датум издавања рачуна." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.mobile}``" -msgstr "``#{ticket.customer.mobile}``" +#: ../system/subscription.rst:204 +msgid "Amount" +msgstr "Износ" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Login" -msgstr "Тикет > Клијент > Пријава" +#: ../system/subscription.rst:204 +msgid "Invoice total including VAT if applicable." +msgstr "Износ рачуна укључујући и ПДВ ако се обрачунава." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.login}``" -msgstr "``#{ticket.customer.login}``" +#: ../system/subscription.rst:207 +msgid "" +"Contains contract period (monthly or yearly) and hosted plan for the " +"subscription period in question." +msgstr "" +"Садржи уговорни период (месечни или годишњи) и хостинг план за дотични " +"период претплате." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Lastname" -msgstr "Тикет > Клијент > Презиме" +#: ../system/subscription.rst:218 +msgid "Payment method / Service period" +msgstr "Начин плаћања / Уговорни период" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.lastname}``" -msgstr "``#{ticket.customer.lastname}``" +#: ../system/subscription.rst:211 +msgid "" +"Used bank account or credit card as well as the subscription period the " +"invoice is about." +msgstr "" +"Коришћен рачун банке или кредитна картица као и уговорни период рачуна." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Firstname" -msgstr "Тикет > Клијент > Име" +#: ../system/subscription.rst:216 +msgid "" +"It might happen that the invoice date and subscription period differ. This " +"is nothing to worry about, the subscription periods will be accounted later " +"on." +msgstr "" +"Може се догодити да се датум издавања рачуна и уговорни период разликују. Не " +"брините око овога, уговорни период ће бити обрачунат накнадно." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.firstname}``" -msgstr "``#{ticket.customer.firstname}``" +#: ../system/subscription.rst:222 +msgid "Receipt" +msgstr "Признаница" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Fax" -msgstr "Тикет > Клијент > Факс" +#: ../system/subscription.rst:221 +msgid "" +"Use the arrow to download the invoice in question. You can download all " +"available invoices any time you need to here!" +msgstr "" +"Користите иконицу стрелице за преузимање рачуна. Овде можете преузети све " +"доступне рачуне у било ком тренутку!" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.fax}``" -msgstr "``#{ticket.customer.fax}``" +#: ../system/subscription.rst:None +msgid "Screenshot showing payment history of a hosted instance" +msgstr "Снимак екрана који приказује историјат плаћања хостоване инстанце" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Email" -msgstr "Тикет > Клијент > Имејл" +#: ../system/subscription.rst:229 +msgid "FAQ" +msgstr "Често постављана питања" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.email}``" -msgstr "``#{ticket.customer.email}``" +#: ../system/subscription.rst:233 +msgid "I set up a trial account but am missing functions to test" +msgstr "" +"Регистровао сам пробни налог али немам приступ неким функцијама за тестирање" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Department" -msgstr "Тикет > Клијент > Одељење" +#: ../system/subscription.rst:232 +msgid "" +"The trial instance is running within the professional package allowing up to " +"three agents." +msgstr "" +"Пробна инстанца ради у оквиру Professional пакета и дозвољава до три " +"оператера." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.department}``" -msgstr "``#{ticket.customer.department}``" +#: ../system/subscription.rst:236 +msgid "Can I change package within the trial?" +msgstr "Да ли могу да променим пакет у оквиру пробног периода?" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Avatar" -msgstr "Тикет > Клијент > Аватар" +#: ../system/subscription.rst:236 +msgid "No. As soon as the package is changed the subscription begins." +msgstr "Не. По промени пакета започеће претплата." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.avatar(60,60)}``" -msgstr "``#{ticket.customer.avatar(60,60)}``" +#: ../system/subscription.rst:241 +msgid "What happens to my trial instance after the trial period ended?" +msgstr "Шта се дешава са мојом пробном инстанцом након пробног периода?" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Address" -msgstr "Тикет > Клијент > Адреса" +#: ../system/subscription.rst:239 +msgid "" +"Your instance will automatically be canceled for you. Please see *What " +"happens to my instance after it has been canceled?* for more." +msgstr "" +"Ваша инстанца ће бити аутоматски отказана. Молимо погледајте *Шта се дешава " +"са мојом инстанцом по отказивању?* за више детаља." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.address}``" -msgstr "``#{ticket.customer.address}``" +#: ../system/subscription.rst:254 +msgid "What happens to my instance after it has been canceled?" +msgstr "Шта се дешава са мојом инстанцом по отказивању?" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Web" -msgstr "Тикет > Додато од стране > Веб" +#: ../system/subscription.rst:244 +msgid "That depends slightly on your instance state:" +msgstr "Ово зависи од стања ваше инстанце:" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.web}``" -msgstr "``#{ticket.created_by.web}``" +#: ../system/subscription.rst:250 +msgid "Trial instance" +msgstr "Пробна инстанца" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > VIP" -msgstr "Тикет > Додато од стране > VIP" +#: ../system/subscription.rst:247 +msgid "" +"If you're still on trial, we will ice your instance and remind you once " +"again about your instance. We then will wait some days and remove your " +"instance from our system. This is the last time we will inform you by Email." +msgstr "" +"Ако сте још увек у пробном периоду, замрзнућемо вашу инстанцу и подсетити " +"вас још једанпут. Онда ћемо сачекати пар дана и уклонити вашу инстанцу из " +"нашег система. Након овога ћемо вас обавестити путем имејла последњи пут." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.vip}``" -msgstr "``#{ticket.created_by.vip}``" +#: ../system/subscription.rst:254 +msgid "Paid instance" +msgstr "Плаћена инстанца" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Phone" -msgstr "Тикет > Додато од стране > Телефон" +#: ../system/subscription.rst:253 +msgid "" +"If you're a paying customer and canceled your subscription, the instance " +"removal will take place the day after your last subscription day." +msgstr "" +"Ако сте плаћали и откажете вашу претплату, уклањање инстанце ће започети " +"један дан након истека ваше претплате." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.phone}``" -msgstr "``#{ticket.created_by.phone}``" +#: ../system/subscription.rst:256 +msgid "Can removed instances be restored?" +msgstr "Да ли се уклоњене инстанце могу вратити?" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Note" -msgstr "Тикет > Додато од стране > Напомена" +#: ../system/subscription.rst:257 +msgid "No. Once your instance has been removed, a restoration is not possible." +msgstr "Не. По уклањању ваше инстанце, враћање података више није могуће." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.note}``" -msgstr "``#{ticket.created_by.note}``" +#: ../system/system-report.rst:2 +msgid "System Report" +msgstr "Системски извештај" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Mobile" -msgstr "Тикет > Додато од стране > Мобилни" +#: ../system/system-report.rst:4 +msgid "" +"In this place you can't configure Zammad. Instead you can obtain a system " +"report about Zammad and its configuration." +msgstr "" +"Овде не можете подесити ваш Zammad. Уместо тога можете преузети системски " +"извештај о Zammad-у и његовој конфигурацији." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.mobile}``" -msgstr "``#{ticket.created_by.mobile}``" +#: ../system/system-report.rst:7 +msgid "" +"See the description in Zammad for an explanation. You can even find a " +"preview of the included data below the **Download** button." +msgstr "" +"Погледајте опис у Zammad-у за објашњење. Можете чак видети и приказ " +"укључених података испод дугмета **Преузми**." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Login" -msgstr "Тикет > Додато од стране > Пријава" +#: ../system/system-report.rst:10 +msgid "" +"Zammad never sends this automatically to anyone. It is a manual process only " +"to provide better support based on your configuration." +msgstr "" +"Zammad никада неће аутоматски послати овај извештај икоме. У питању је " +"мануелни процес само у сврху унапређења подршке на основу ваше конфигурације." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.login}``" -msgstr "``#{ticket.created_by.login}``" +#: ../system/translations.rst:2 +msgid "Translations" +msgstr "Преводи" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Lastname" -msgstr "Тикет > Додато од стране > Презиме" +#: ../system/translations.rst:4 +msgid "" +"Translations of Zammad are processed centrally in our `Weblate instance " +"`_. This allows non-developers to review " +"and update translation texts of the language they actually speak." +msgstr "" +"Преводи за Zammad се прикупљају централно путем наше `Weblate инстанце " +"`_. Ово омогућава и особама које нису " +"вичне програмирању да прегледају и освеже текстове превода за језик којим " +"говоре." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.lastname}``" -msgstr "``#{ticket.created_by.lastname}``" +#: ../system/translations.rst:9 +msgid "" +"Your language is in an incomplete translation state or has typos? Please " +"consider helping us in sorting this out! All you need is either a GitHub " +"account or to register directly in our instance." +msgstr "" +"Ваш језик има некомплетан превод или има грешке? Молимо узмите у обзир да " +"нам помогнете са овим! Све што вам је неопходно је или GitHub налог или " +"директна регистрација на нашој инстанци." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Firstname" -msgstr "Тикет > Додато од стране > Име" +#: ../system/translations.rst:13 +msgid "" +"Did you know? This is also where the documentation translations are handled. " +"🤓" +msgstr "" +"Да ли сте знали? Ово је место где се прикупљају и преводи за документацију. " +"🤓" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.firstname}``" -msgstr "``#{ticket.created_by.firstname}``" +#: ../system/translations.rst:15 +msgid "" +"Have a look in our :docs:`contribution section ` in the system documentation to get started!" +msgstr "" +"Погледајте наш :docs:`одељак о преводима ` у системској документацији за прве кораке!" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Fax" -msgstr "Тикет > Додато од стране > Факс" +#: ../system/translations.rst:20 +msgid "Local Translations" +msgstr "Локални преводи" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.fax}``" -msgstr "``#{ticket.created_by.fax}``" +#: ../system/translations.rst:22 +msgid "" +"Apart from these system translations, there's still local translations you " +"can manage. This is relevant if you added custom objects that require " +"translations or even custom states and priorities." +msgstr "" +"Осим ових системских превода, постоје и локални преводи којима можете " +"управљати. Ово се односи и ако сте додали прилагођене објекте који захтевају " +"преводе па чак и прилагођена стања и приоритети." -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Email" -msgstr "Тикет > Додато од стране > Имејл" +#: ../system/translations.rst:None +msgid "Translation management screen within the admin menu" +msgstr "Страна управљања преводима у оквиру администраторског панела" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.email}``" -msgstr "``#{ticket.created_by.email}``" +#: ../system/translations.rst:31 +msgid "Updating Translations" +msgstr "Освежавање превода" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Department" -msgstr "Тикет > Додато од стране > Одељење" +#: ../system/translations.rst:33 +msgid "" +"Because of how Zammad ships translations, the only way to update the system " +"translations is to update your Zammad installation. The benefit of this is " +"that you no longer need internet access during a Zammad upgrade as the " +"package has everything it requires already." +msgstr "" +"С обзиром на начин на који Zammad обезбеђује преводе, једини начин да " +"освежите системске преводе је да ажурирате вашу Zammad инсталацију. Једна од " +"користи овог приступа да вам више није неопходан приступ интернету током " +"ажурирању Zammad-а јер пакет садржи све што је потребно." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.department}``" -msgstr "``#{ticket.created_by.department}``" +#: ../system/translations.rst:39 +msgid "Translation of Custom Objects" +msgstr "Превод прилагођених објеката" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Avatar" -msgstr "Тикет > Додато од стране > Аватар" +#: ../system/translations.rst:41 +msgid "" +"No problem at all! You can customize any translation locally, even if it is " +"not initially provided by the system." +msgstr "" +"Нема проблема! Можете прилагодити било који локални превод, чак иако " +"иницијално није дошао са системом." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.avatar(60,60)}``" -msgstr "``#{ticket.created_by.avatar(60,60)}``" +#: ../system/translations.rst:44 +msgid "" +"Translation is supported for a broad number of features, including but not " +"limited to custom:" +msgstr "Преводи су подржани у већем броју функција, укључујући и:" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Address" -msgstr "Тикет > Додато од стране > Адреса" +#: ../system/translations.rst:47 +msgid "Object Attributes" +msgstr "Атрибути објеката" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.address}``" -msgstr "``#{ticket.created_by.address}``" +#: ../system/translations.rst:48 +msgid "Ticket Macros" +msgstr "Макрои тикета" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created at" -msgstr "Тикет > Додато у" +#: ../system/translations.rst:49 +msgid "Ticket Overviews" +msgstr "Прегледи тикета" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_at}``" -msgstr "``#{ticket.created_at}``" +#: ../system/translations.rst:50 +msgid "Ticket Priorities" +msgstr "Приоритети тикета" -#: ../system/variables/ticket.rst:1 -msgid "2019-10-07 16:25:00 UTC" -msgstr "2019-10-07 16:25:00 UTC" +#: ../system/translations.rst:51 +msgid "Ticket States" +msgstr "Стања тикета" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Closing time" -msgstr "Тикет > Време затварања" +#: ../system/translations.rst:54 +msgid "Customizing Translations" +msgstr "Прилагођавање превода" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.close_at}``" -msgstr "``#{ticket.close_at}``" +#: ../system/translations.rst:56 +msgid "" +"Within the translation screen, simply click on the **New Translation** " +"button." +msgstr "" +"На страници за управљање превода, једноставно кликните на зелено дугме " +"**Нови превод**." -#: ../system/variables/ticket.rst:1 -msgid "2019-10-07 17:25:00 UTC" -msgstr "2019-10-07 17:25:00 UTC" +#: ../system/translations.rst:None +msgid "New translation dialog" +msgstr "Дијалог новог превода" -#: ../system/variables/ticket.rst:1 -msgid "``3``, any number of articles existing in the ticket right now" -msgstr "``3``, број чланака који тренутно постоје у тикету" +#: ../system/translations.rst:62 +msgid "" +"In the dialog you can immediately enter the exact translation source (if you " +"know it) and your custom translation text for it and click **Submit**." +msgstr "" +"У дијалогу можете директно унети тачан изворни превод (ако га знате) и ваш " +"прилагођени текст превода за њега а потом кликните на **Пошаљи**." -#: ../system/version.rst:2 -msgid "Version" -msgstr "Верзија" +#: ../system/translations.rst:65 +msgid "" +"Alternatively, try to search for translation suggestions in the list below. " +"Selecting an item from the list will pre-fill the translation source for you " +"and then you can just enter your custom translation." +msgstr "" +"Алтернативно, покушајте да претражујете листу предлога за превод испод. " +"Одабир ставке са листе ће попунити изворни превод за вас и онда можете унети " +"само ваш прилагођени превод." -#: ../system/version.rst:4 -msgid "Shows which version is currently being used on your Zammad-instance." -msgstr "Приказује која верзија се користи тренутно на вашој Zammad инстанци." +#: ../system/translations.rst:69 +msgid "" +"The target language will always default to your current language selection. " +"If you need to translate for a different language, simply change the " +"selection before submitting." +msgstr "" +"Циљни језик ће увек подразумевано бити постављен на ваш тренутни језик " +"провила. Уколико вам треба превод за други језик, једноставно га одаберите " +"из селекције пре слања." -#: ../manage/roles/admin-permissions.rst:53 -msgid "``admin.checklist``" -msgstr "``admin.checklist``" +#: ../system/translations.rst:73 +msgid "" +"All your custom translations will show up in the overview table when added. " +"And they will even persist across Zammad updates!" +msgstr "" +"Сви ваши прилагођени преводи ће бити приказани у табели прегледа по " +"додавању. Чак ће преживети и ажурирање Zammad-а!" -#: ../manage/roles/admin-permissions.rst:54 -msgid ":doc:`Manage > Checklist `" -msgstr ":doc:`Управљање > Списак задатака `" +#: ../system/translations.rst:76 +msgid "" +"Make sure to reload your browser if a translated string is not displayed." +msgstr "Уколико текст превода не буде приказан, освежите ваш претраживач." -#: ../manage/roles/admin-permissions.rst:83 -msgid "``admin.channel_whatsapp``" -msgstr "``admin.channel_whatsapp``" +#: ../system/translations.rst:80 +msgid "Reverting to Original Translations" +msgstr "Повратак на оригиналне преводе" -#: ../manage/roles/admin-permissions.rst:84 -msgid ":doc:`Channels > Whatsapp `" -msgstr ":doc:`Канали > Whatsapp `" +#: ../system/translations.rst:82 +msgid "" +"If you want to revert a custom translation to original text, simply use the " +"appropriate action within the row of the overview table." +msgstr "" +"Уколико желите да се вратите прилагођени превод на оригинални текст, " +"једноставно користите одговарајућу акцију из реда табеле прегледа." -#: ../manage/roles/admin-permissions.rst:124 -msgid "``admin.public_links``" -msgstr "``admin.public_links``" +#: ../system/translations.rst:85 +msgid "" +"Depending on the type of the translation source, the action has a slightly " +"different name:" +msgstr "" +"Зависно од типа изворног превода, радња може имати мало другачији назив:" -#: ../manage/roles/admin-permissions.rst:125 -msgid ":doc:`Manage > Public Links `" -msgstr ":doc:`Управљање > Јавни линкови `" +#: ../system/translations.rst:88 +msgid "**Reset** for customized system translations" +msgstr "**Поништи** за прилагођене системске преводе" -#: ../manage/roles/admin-permissions.rst:151 -msgid "``admin.system_report``" -msgstr "``admin.system_report``" +#: ../system/translations.rst:89 +msgid "**Remove** for customized local translations" +msgstr "**Уклони** за прилагођене локалне преводе" -#: ../manage/roles/admin-permissions.rst:152 -msgid ":doc:`System > System Report `" -msgstr ":doc:`Систем > Системски извештај `" +#: ../system/translations.rst:91 +msgid "" +"In both cases, the action will remove the customized translation after a " +"confirmation." +msgstr "У сваком случају, радња ће избрисати прилагођени превод по потврди." -#: ../manage/roles/admin-permissions.rst:166 -msgid "``admin.ticket_auto_assignment``" -msgstr "``admin.ticket_auto_assignment``" +#: ../system/translations.rst:None +msgid "Screenshot showing the location of the Remove action" +msgstr "Снимак екрана који приказује позицију радње Уклони" -#: ../manage/roles/admin-permissions.rst:167 -msgid ":ref:`Settings > Ticket > Auto Assignment `" -msgstr ":ref:`Подешавања > Тикет > Аутоматска додела тикета `" +#: ../system/translations.rst:99 +msgid "Inline Translations" +msgstr "Непосредни преводи" -#: ../manage/roles/admin-permissions.rst:169 -msgid "``admin.ticket_duplicate_detection``" -msgstr "``admin.ticket_duplicate_detection``" +#: ../system/translations.rst:101 +msgid "" +"If you prefer a more hands-on approach, you can activate the inline or on-" +"screen translation feature by pressing ``ctrl`` + ``alt`` + ``t`` at any " +"time and on any screen." +msgstr "" +"Уколико вам је дражи практичнији приступ, можете укључити непосредне преводе " +"односно функцију превода на екрану притиском на ``ctrl`` + ``alt`` + ``t`` у " +"било ком тренутку и на било којој страници." -#: ../manage/roles/admin-permissions.rst:170 -msgid ":ref:`Settings > Ticket > Duplicate Detection `" -msgstr ":ref:`Подешавања > Тикет > Откривање дупликата `" +#: ../system/translations.rst:105 +msgid "" +"All customizable translation texts will be highlighted for you on the " +"screen. Just click into the highlighted area and update the text in place." +msgstr "" +"Сви преводи који се могу прилагодити ће бити означени на екрану. Само " +"кликните на означену површину и освежите текст на жељену вредност." -#: ../manage/roles/admin-permissions.rst:172 -msgid "``admin.ticket_priority``" -msgstr "``admin.ticket_priority``" +#: ../system/translations.rst:None +msgid "Inline translation mode activated for the Overview screen" +msgstr "Непосредни преводи укључени на екрану прегледа" -#: ../manage/roles/admin-permissions.rst:173 -msgid ":ref:`System > Objects >Ticket Priority `" -msgstr ":ref:`Систем > Објекти >Приоритет тикета `" +#: ../system/translations.rst:112 +msgid "" +"When finished editing, simply press ``ctrl`` + ``alt`` + ``t`` again to " +"deactivate." +msgstr "" +"По завршетку уређивања, једноставно притисните ``ctrl`` + ``alt`` + ``t`` " +"поново за искључивање." -#: ../manage/roles/admin-permissions.rst:175 -msgid "``admin.ticket_state``" -msgstr "``admin.ticket_state``" +#: ../system/translations.rst:117 +msgid "" +"Even though it's available on any screen, the inline translation feature " +"requires admin permissions. It works only for the current language " +"selection. If you need to translate a different language, first change the " +"language in your :user-docs:`profile settings `." +msgstr "" +"Иако су доступни за сваку страницу, непосредни преводи захтевају " +"администраторске дозволе. Функционишу само за тренутни одабир језика. Ако " +"желите да преведете на други језик, прво промените језик у вашим :user-docs:" +"`подешавањима профила ." -#: ../manage/roles/admin-permissions.rst:176 -msgid ":ref:`System > Objects >Ticket State `" -msgstr ":ref:`Систем > Објекти > Стање тикета `" +#: ../system/version.rst:2 +msgid "Version" +msgstr "Верзија" -#: ../manage/roles/admin-permissions.rst:193 -msgid "``admin.webhook``" -msgstr "``admin.webhook``" +#: ../system/version.rst:4 +msgid "Shows which version is currently being used on your Zammad-instance." +msgstr "Приказује која верзија се користи тренутно на вашој Zammad инстанци." -#: ../manage/roles/admin-permissions.rst:194 -msgid ":doc:`Manage > Webhook `" -msgstr ":doc:`Управљање > Повратни позив `" +#~ msgid "Billing" +#~ msgstr "Наплата" -#: ../manage/roles/user-preferences-permissions.rst:43 -msgid "``user_preferences.appearance``" -msgstr "``user_preferences.appearance``" +#~ msgid "Do you want to cancel your subscription?" +#~ msgstr "Да ли желите да откажете вашу претплату?" -#: ../manage/roles/user-preferences-permissions.rst:44 -msgid "Appearance configuration" -msgstr "Подешавање изгледа" +#~ msgid "Screencast showing how to cancel a subscription" +#~ msgstr "Снимак екрана који приказује како отказати претплату" -#: ../manage/roles/user-preferences-permissions.rst:0 -msgid "Users can switch between dark, light and" -msgstr "Корисници могу да изаберу између тамног, светлог и" +#~ msgid "" +#~ "The subscription section currently consists of two tabs: Plan & Billing. " +#~ "For your overview we've divided those two tabs into independent sub pages:" +#~ msgstr "" +#~ "Одељак претплате се тренутно састоји од два језичка: План и Наплата. Ради " +#~ "бољег прегледа моделили смо ова два језичка у самосталне странице:" -#: ../manage/roles/user-preferences-permissions.rst:0 -msgid "automatic mode." -msgstr "аутоматског мода." +#~ msgid ":doc:`💰 Subscription plan `" +#~ msgstr ":doc:`💰 План претплате `" -#: ../system/system-report.rst:2 -msgid "System Report" -msgstr "Системски извештај" +#~ msgid ":doc:`🧾 Subscription billing `" +#~ msgstr ":doc:`🧾 Наплата претплате `" -#: ../system/system-report.rst:4 -msgid "" -"In this place you can't configure Zammad. Instead you can obtain a system " -"report about Zammad and its configuration." -msgstr "" -"Овде не можете подесити ваш Zammad. Уместо тога можете преузети системски " -"извештај о Zammad-у и његовој конфигурацији." +#~ msgid "" +#~ "Everything regarding billing address, invoices and account cancellation." +#~ msgstr "Све у вези адресе за наплату, рачуна и отказивања претплате." -#: ../system/system-report.rst:7 -msgid "" -"See the description in Zammad for an explanation. You can even find a " -"preview of the included data below the **Download** button." -msgstr "" -"Погледајте опис у Zammad-у за објашњење. Можете чак видети и приказ " -"укључених података испод дугмета **Преузми**." +#~ msgid "Summary" +#~ msgstr "Преглед" -#: ../system/system-report.rst:10 -msgid "" -"Zammad never sends this automatically to anyone. It is a manual process only " -"to provide better support based on your configuration." -msgstr "" -"Zammad никада неће аутоматски послати овај извештај икоме. У питању је " -"мануелни процес само у сврху унапређења подршке на основу ваше конфигурације." +#~ msgid "SEPA" +#~ msgstr "SEPA" #~ msgid "" #~ "Please note that this part of our documentation currently is outdated. We " diff --git a/locale/sv/LC_MESSAGES/admin-docs.po b/locale/sv/LC_MESSAGES/admin-docs.po index d0f29a74..bd809719 100644 --- a/locale/sv/LC_MESSAGES/admin-docs.po +++ b/locale/sv/LC_MESSAGES/admin-docs.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Zammad\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-11-06 10:31+0100\n" +"POT-Creation-Date: 2024-11-12 16:31+0100\n" "PO-Revision-Date: 2024-10-25 11:00+0000\n" "Last-Translator: chrand818 \n" "Language-Team: Swedish Checklist `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:56 msgid "``admin.channel_email``" msgstr "" -#: ../manage/roles/admin-permissions.rst:54 #: ../manage/roles/admin-permissions.rst:57 msgid ":doc:`Channels > Email `" msgstr "" -#: ../manage/roles/admin-permissions.rst:56 #: ../manage/roles/admin-permissions.rst:59 msgid "``admin.channel_facebook``" msgstr "" -#: ../manage/roles/admin-permissions.rst:57 #: ../manage/roles/admin-permissions.rst:60 msgid ":doc:`Channels > Facebook `" msgstr "" -#: ../manage/roles/admin-permissions.rst:58 #: ../manage/roles/admin-permissions.rst:61 msgid "" "Accessing Facebook tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:59 #: ../manage/roles/admin-permissions.rst:62 msgid "``admin.channel_formular``" msgstr "" -#: ../manage/roles/admin-permissions.rst:60 #: ../manage/roles/admin-permissions.rst:63 msgid ":doc:`Channels > Form `" msgstr "" -#: ../manage/roles/admin-permissions.rst:62 #: ../manage/roles/admin-permissions.rst:65 msgid "``admin.channel_google``" msgstr "" -#: ../manage/roles/admin-permissions.rst:63 #: ../manage/roles/admin-permissions.rst:66 msgid ":doc:`Channels > Google `" msgstr "" -#: ../manage/roles/admin-permissions.rst:65 #: ../manage/roles/admin-permissions.rst:68 msgid "``admin.channel_microsoft365``" msgstr "" -#: ../manage/roles/admin-permissions.rst:66 #: ../manage/roles/admin-permissions.rst:69 msgid ":doc:`Channels > Microsoft 365 `" msgstr "" -#: ../manage/roles/admin-permissions.rst:68 #: ../manage/roles/admin-permissions.rst:71 msgid "``admin.channel_sms``" msgstr "" -#: ../manage/roles/admin-permissions.rst:69 #: ../manage/roles/admin-permissions.rst:72 msgid ":doc:`Channels > SMS `" msgstr "" -#: ../manage/roles/admin-permissions.rst:71 #: ../manage/roles/admin-permissions.rst:74 msgid "``admin.channel_telegram``" msgstr "" -#: ../manage/roles/admin-permissions.rst:72 #: ../manage/roles/admin-permissions.rst:75 msgid ":doc:`Channels > Telegram `" msgstr "" -#: ../manage/roles/admin-permissions.rst:73 #: ../manage/roles/admin-permissions.rst:76 msgid "" "Accessing Telegram tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:74 #: ../manage/roles/admin-permissions.rst:77 msgid "``admin.channel_twitter``" msgstr "" -#: ../manage/roles/admin-permissions.rst:75 #: ../manage/roles/admin-permissions.rst:78 msgid ":doc:`Channels > Twitter `" msgstr "" -#: ../manage/roles/admin-permissions.rst:76 #: ../manage/roles/admin-permissions.rst:79 msgid "" "Accessing Twitter/X tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:77 #: ../manage/roles/admin-permissions.rst:80 msgid "``admin.channel_web``" msgstr "" -#: ../manage/roles/admin-permissions.rst:78 #: ../manage/roles/admin-permissions.rst:81 msgid ":doc:`Channels > Web `" msgstr "" -#: ../manage/roles/admin-permissions.rst:80 +#: ../manage/roles/admin-permissions.rst:83 +msgid "``admin.channel_whatsapp``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:84 +msgid ":doc:`Channels > Whatsapp `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:86 msgid "``admin.core_workflows``" msgstr "" -#: ../manage/roles/admin-permissions.rst:81 #: ../manage/roles/admin-permissions.rst:87 msgid ":doc:`System > Core Workflows `" msgstr "" -#: ../manage/roles/admin-permissions.rst:83 #: ../manage/roles/admin-permissions.rst:89 msgid "``admin.data_privacy``" msgstr "" -#: ../manage/roles/admin-permissions.rst:84 #: ../manage/roles/admin-permissions.rst:90 msgid ":doc:`System > Data Privacy `" msgstr "" -#: ../manage/roles/admin-permissions.rst:85 #: ../manage/roles/admin-permissions.rst:91 msgid "" "🔥 Be careful, it allows users to permanently delete data on the system." msgstr "" -#: ../manage/roles/admin-permissions.rst:86 #: ../manage/roles/admin-permissions.rst:92 msgid "``admin.group``" msgstr "" -#: ../manage/roles/admin-permissions.rst:87 #: ../manage/roles/admin-permissions.rst:93 msgid ":doc:`Manage > Groups `" msgstr "" -#: ../manage/roles/admin-permissions.rst:89 #: ../manage/roles/admin-permissions.rst:95 msgid "``admin.integration``" msgstr "" -#: ../manage/roles/admin-permissions.rst:90 #: ../manage/roles/admin-permissions.rst:96 msgid ":doc:`System > Integrations `" msgstr "" -#: ../manage/roles/admin-permissions.rst:92 #: ../manage/roles/admin-permissions.rst:98 msgid "``admin.knowledge_base``" msgstr "" -#: ../manage/roles/admin-permissions.rst:93 #: ../manage/roles/admin-permissions.rst:99 msgid ":doc:`Manage > Knowledge Base `" msgstr "" @@ -8555,57 +8538,46 @@ msgid "" "knowledge-base.html#editing-answers>`." msgstr "" -#: ../manage/roles/admin-permissions.rst:98 #: ../manage/roles/admin-permissions.rst:104 msgid "``admin.macro``" msgstr "" -#: ../manage/roles/admin-permissions.rst:99 #: ../manage/roles/admin-permissions.rst:105 msgid ":doc:`Manage > Macros `" msgstr "" -#: ../manage/roles/admin-permissions.rst:100 #: ../manage/roles/admin-permissions.rst:106 msgid "In some cases, macros may also require ``admin.tag``" msgstr "" -#: ../manage/roles/admin-permissions.rst:101 #: ../manage/roles/admin-permissions.rst:107 msgid "``admin.maintenance``" msgstr "" -#: ../manage/roles/admin-permissions.rst:102 #: ../manage/roles/admin-permissions.rst:108 msgid ":doc:`System > Maintenance `" msgstr "" -#: ../manage/roles/admin-permissions.rst:104 #: ../manage/roles/admin-permissions.rst:110 msgid "``admin.monitoring``" msgstr "" -#: ../manage/roles/admin-permissions.rst:105 #: ../manage/roles/admin-permissions.rst:111 msgid ":doc:`System > Monitoring `" msgstr "" -#: ../manage/roles/admin-permissions.rst:107 #: ../manage/roles/admin-permissions.rst:113 msgid "``admin.object``" msgstr "" -#: ../manage/roles/admin-permissions.rst:108 #: ../manage/roles/admin-permissions.rst:114 msgid ":doc:`System > Objects `" msgstr "" -#: ../manage/roles/admin-permissions.rst:110 #: ../manage/roles/admin-permissions.rst:116 msgid "``admin.organization``" msgstr "" -#: ../manage/roles/admin-permissions.rst:111 #: ../manage/roles/admin-permissions.rst:117 msgid ":doc:`Manage > Organizations `" msgstr "" @@ -8622,202 +8594,210 @@ msgstr "" msgid "They can even edit an organization's name, domain, and notes!" msgstr "" -#: ../manage/roles/admin-permissions.rst:115 #: ../manage/roles/admin-permissions.rst:121 msgid "``admin.overview``" msgstr "" -#: ../manage/roles/admin-permissions.rst:116 #: ../manage/roles/admin-permissions.rst:122 msgid ":doc:`Manage > Overviews`" msgstr "" -#: ../manage/roles/admin-permissions.rst:118 +#: ../manage/roles/admin-permissions.rst:124 +msgid "``admin.public_links``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:125 +msgid ":doc:`Manage > Public Links `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:127 msgid "``admin.package``" msgstr "" -#: ../manage/roles/admin-permissions.rst:119 #: ../manage/roles/admin-permissions.rst:128 msgid ":doc:`System > Packages `" msgstr "" -#: ../manage/roles/admin-permissions.rst:121 #: ../manage/roles/admin-permissions.rst:130 msgid "``admin.report_profile``" msgstr "" -#: ../manage/roles/admin-permissions.rst:122 #: ../manage/roles/admin-permissions.rst:131 msgid ":doc:`Manage > Report Profiles `" msgstr "" -#: ../manage/roles/admin-permissions.rst:123 #: ../manage/roles/admin-permissions.rst:132 msgid "Access to view reports: ``report``" msgstr "" -#: ../manage/roles/admin-permissions.rst:124 #: ../manage/roles/admin-permissions.rst:133 msgid "``admin.role``" msgstr "" -#: ../manage/roles/admin-permissions.rst:125 #: ../manage/roles/admin-permissions.rst:134 msgid ":doc:`Manage > Roles `" msgstr "" -#: ../manage/roles/admin-permissions.rst:127 #: ../manage/roles/admin-permissions.rst:136 msgid "``admin.scheduler``" msgstr "" -#: ../manage/roles/admin-permissions.rst:128 #: ../manage/roles/admin-permissions.rst:137 msgid ":doc:`Manage > Scheduler `" msgstr "" -#: ../manage/roles/admin-permissions.rst:129 #: ../manage/roles/admin-permissions.rst:138 msgid "For automation on tickets" msgstr "" -#: ../manage/roles/admin-permissions.rst:130 #: ../manage/roles/admin-permissions.rst:139 msgid "``admin.security``" msgstr "" -#: ../manage/roles/admin-permissions.rst:131 #: ../manage/roles/admin-permissions.rst:140 msgid ":doc:`Settings > Security `" msgstr "" -#: ../manage/roles/admin-permissions.rst:132 #: ../manage/roles/admin-permissions.rst:141 msgid "Settings of Zammad. This also covers third party authentications." msgstr "" -#: ../manage/roles/admin-permissions.rst:133 #: ../manage/roles/admin-permissions.rst:142 msgid "``admin.session``" msgstr "" -#: ../manage/roles/admin-permissions.rst:134 #: ../manage/roles/admin-permissions.rst:143 msgid ":doc:`System > Sessions `" msgstr "" -#: ../manage/roles/admin-permissions.rst:136 #: ../manage/roles/admin-permissions.rst:145 msgid "``admin.setting_system``" msgstr "" -#: ../manage/roles/admin-permissions.rst:137 #: ../manage/roles/admin-permissions.rst:146 msgid ":doc:`Settings > System `" msgstr "" -#: ../manage/roles/admin-permissions.rst:139 #: ../manage/roles/admin-permissions.rst:148 msgid "``admin.sla``" msgstr "" -#: ../manage/roles/admin-permissions.rst:140 #: ../manage/roles/admin-permissions.rst:149 msgid ":doc:`Manage > SLAs `" msgstr "" -#: ../manage/roles/admin-permissions.rst:142 +#: ../manage/roles/admin-permissions.rst:151 +msgid "``admin.system_report``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:152 +msgid ":doc:`System > System Report `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:154 msgid "``admin.tag``" msgstr "" -#: ../manage/roles/admin-permissions.rst:143 #: ../manage/roles/admin-permissions.rst:155 msgid ":doc:`Manage > Tags `" msgstr "" -#: ../manage/roles/admin-permissions.rst:145 #: ../manage/roles/admin-permissions.rst:157 msgid "``admin.template``" msgstr "" -#: ../manage/roles/admin-permissions.rst:146 #: ../manage/roles/admin-permissions.rst:158 msgid ":doc:`Manage > Templates `" msgstr "" -#: ../manage/roles/admin-permissions.rst:148 #: ../manage/roles/admin-permissions.rst:160 msgid "``admin.text_module``" msgstr "" -#: ../manage/roles/admin-permissions.rst:149 #: ../manage/roles/admin-permissions.rst:161 msgid ":doc:`Manage > Text Modules `" msgstr "" -#: ../manage/roles/admin-permissions.rst:151 #: ../manage/roles/admin-permissions.rst:163 msgid "``admin.ticket``" msgstr "" -#: ../manage/roles/admin-permissions.rst:152 #: ../manage/roles/admin-permissions.rst:164 msgid ":doc:`Settings > Tickets `" msgstr "" -#: ../manage/roles/admin-permissions.rst:153 #: ../manage/roles/admin-permissions.rst:165 msgid "Does not grant access to :doc:`/misc/composer`" msgstr "" -#: ../manage/roles/admin-permissions.rst:154 +#: ../manage/roles/admin-permissions.rst:166 +msgid "``admin.ticket_auto_assignment``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:167 +msgid ":ref:`Settings > Ticket > Auto Assignment `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:169 +msgid "``admin.ticket_duplicate_detection``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:170 +msgid ":ref:`Settings > Ticket > Duplicate Detection `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:172 +msgid "``admin.ticket_priority``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:173 +msgid ":ref:`System > Objects >Ticket Priority `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:175 +msgid "``admin.ticket_state``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:176 +msgid ":ref:`System > Objects >Ticket State `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:178 msgid "``admin.time_accounting``" msgstr "" -#: ../manage/roles/admin-permissions.rst:155 #: ../manage/roles/admin-permissions.rst:179 msgid ":doc:`Manage > Time Accounting `" msgstr "" -#: ../manage/roles/admin-permissions.rst:156 #: ../manage/roles/admin-permissions.rst:180 msgid "Also allows the export of timekeeping records." msgstr "" -#: ../manage/roles/admin-permissions.rst:157 #: ../manage/roles/admin-permissions.rst:181 msgid "``admin.translation``" msgstr "" -#: ../manage/roles/admin-permissions.rst:158 #: ../manage/roles/admin-permissions.rst:182 msgid ":doc:`System > Translations `" msgstr "" -#: ../manage/roles/admin-permissions.rst:159 #: ../manage/roles/admin-permissions.rst:183 msgid "Also enables inline translation" msgstr "" -#: ../manage/roles/admin-permissions.rst:160 #: ../manage/roles/admin-permissions.rst:184 msgid "``admin.trigger``" msgstr "" -#: ../manage/roles/admin-permissions.rst:161 #: ../manage/roles/admin-permissions.rst:185 msgid ":doc:`Manage > Triggers `" msgstr "" -#: ../manage/roles/admin-permissions.rst:163 #: ../manage/roles/admin-permissions.rst:187 msgid "``admin.user``" msgstr "" -#: ../manage/roles/admin-permissions.rst:164 #: ../manage/roles/admin-permissions.rst:188 msgid ":doc:`Manage > Users `" msgstr "" @@ -8836,6 +8816,14 @@ msgid "" "from-users-perspective>` ." msgstr "" +#: ../manage/roles/admin-permissions.rst:193 +msgid "``admin.webhook``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:194 +msgid ":doc:`Manage > Webhook `" +msgstr "" + #: ../manage/roles/agent-permissions.rst:2 msgid "Agent Permissions" msgstr "" @@ -9254,36 +9242,46 @@ msgid "than the user that generated them." msgstr "" #: ../manage/roles/user-preferences-permissions.rst:43 +msgid "``user_preferences.appearance``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:44 +#, fuzzy +msgid "Appearance configuration" +msgstr "Konfiguration" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "Users can switch between dark, light and" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "automatic mode." +msgstr "" + #: ../manage/roles/user-preferences-permissions.rst:47 msgid "``user_preferences.avatar``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:44 #: ../manage/roles/user-preferences-permissions.rst:48 msgid "Avatar settings" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:45 #: ../manage/roles/user-preferences-permissions.rst:49 msgid "Override the default Gravatar with a custom avatar" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:46 #: ../manage/roles/user-preferences-permissions.rst:50 msgid "``user_preferences.calendar``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:47 #: ../manage/roles/user-preferences-permissions.rst:51 msgid "Configure the calendar feed" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:49 #: ../manage/roles/user-preferences-permissions.rst:53 msgid "``user_preferences.device``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:50 #: ../manage/roles/user-preferences-permissions.rst:54 msgid "Manage device login sessions" msgstr "" @@ -9300,22 +9298,18 @@ msgstr "" msgid "To learn more, see :doc:`/manage/trigger/system-notifications`." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:54 #: ../manage/roles/user-preferences-permissions.rst:58 msgid "``user_preferences.language``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:55 #: ../manage/roles/user-preferences-permissions.rst:59 msgid "Configure the UI locale/language" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:57 #: ../manage/roles/user-preferences-permissions.rst:61 msgid "``user_preferences.linked_accounts``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:58 #: ../manage/roles/user-preferences-permissions.rst:62 msgid "Account linking" msgstr "" @@ -9339,7 +9333,6 @@ msgstr "" msgid "is the only way users can utilize third-party logins." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:63 #: ../manage/roles/user-preferences-permissions.rst:67 msgid "``user_preferences.notifications``" msgstr "" @@ -9367,7 +9360,6 @@ msgstr "" msgid "Customers can't receive ticket notifications at all." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:69 #: ../manage/roles/user-preferences-permissions.rst:73 msgid "``user_preferences.out_of_office``" msgstr "" @@ -9392,7 +9384,6 @@ msgstr "" msgid "they're replacing." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:75 #: ../manage/roles/user-preferences-permissions.rst:79 msgid "``user_preferences.overview_sorting``" msgstr "" @@ -9421,12 +9412,10 @@ msgstr "" msgid "overviews has no effect on custom orders." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:82 #: ../manage/roles/user-preferences-permissions.rst:86 msgid "``user_preferences.password``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:83 #: ../manage/roles/user-preferences-permissions.rst:87 msgid "Change account password" msgstr "" @@ -9443,7 +9432,6 @@ msgstr "" msgid "your only allowed authentication method." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:87 #: ../manage/roles/user-preferences-permissions.rst:91 msgid "``user_preferences.two_factor_authentication``" msgstr "" @@ -9480,7 +9468,7 @@ msgstr "" #: ../manage/scheduler.rst:19 msgid "" -"Schedulers can be used to send periodic reminder emails. Use :doc:`/system/" +"Schedulers can be used to send periodic reminder emails. Use :doc:`/misc/" "variables` to build highly-customized email templates." msgstr "" @@ -10476,7 +10464,7 @@ msgstr "" #: ../manage/text-modules.rst:57 msgid "" -"The example text modules below use :doc:`/system/variables` to dynamically " +"The example text modules below use :doc:`/misc/variables` to dynamically " "insert information like the customer's or agent's names." msgstr "" @@ -10816,8 +10804,8 @@ msgstr "" #: ../misc/object-conditions/basics.rst:144 #: ../misc/object-conditions/basics.rst:160 #: ../misc/object-conditions/basics.rst:168 -#: ../misc/object-conditions/basics.rst:178 ../settings/ticket.rst:2 -#: ../system/variables/ticket.rst:2 +#: ../misc/object-conditions/basics.rst:178 ../misc/variables/ticket.rst:2 +#: ../settings/ticket.rst:2 msgid "Ticket" msgstr "" @@ -11051,7 +11039,7 @@ msgstr "" #: ../manage/trigger/how-do-they-work.rst:79 msgid "" -"Certain actions (such as *email*, *SMS* and *notes*) support :doc:`/system/" +"Certain actions (such as *email*, *SMS* and *notes*) support :doc:`/misc/" "variables`, which can be used to build highly-customized message templates." msgstr "" @@ -11080,7 +11068,7 @@ msgstr "" msgid "" "You can also combine static text with placeholders for text fields. Remember " "that the placeholders' values have to be known during trigger runtime. Learn " -"more about :doc:`/system/variables`." +"more about :doc:`/misc/variables`." msgstr "" #: ../manage/trigger/how-do-they-work.rst:105 @@ -12045,7 +12033,7 @@ msgstr "" msgid "" "When switched on, a code editor will be shown below, where you can configure " "custom payload for your webhook in JSON format. To insert supported :doc:`/" -"system/variables` use ``::`` or ``#{`` shortcuts for autocomplete." +"misc/variables` use ``::`` or ``#{`` shortcuts for autocomplete." msgstr "" #: ../manage/webhook/add.rst:103 @@ -14622,11943 +14610,11835 @@ msgid "" "powerful conditions with AND/OR relations." msgstr "" -#: ../settings/branding.rst:10 -msgid "Product Name" +#: ../misc/variables.rst:2 +msgid "Variables" msgstr "" -#: ../settings/branding.rst:7 +#: ../misc/variables.rst:4 msgid "" -"Defines the name of the application, shown in the web interface, tabs and " -"title bar of the web browser." +"Please note that this is just an overview of available variables. It might " +"be incomplete or variables might not be available within some functions. If " +"you're missing variables or are not sure if something is not working as " +"expected, feel free to ask over at the `Community `_." msgstr "" -#: ../settings/branding.rst:10 -msgid "Default value: ``Zammad Helpdesk``" +#: ../misc/variables.rst:10 +msgid "" +"Variables can be called by typing ``::`` (just like text modules in the " +"frontend), as long as you're in a supported text field within the backend. " +"Zammad will display all variables being available within this context and " +"replace it to the variable as soon as you selected an entry." msgstr "" -#: ../settings/branding.rst:13 -msgid "Will be shown in the app and is included in email footers." +#: ../misc/variables.rst:15 +msgid "" +"You have an empty field which you referenced and it appears as ``-``? That's " +"currently working as designed - you might want to ensure that these fields " +"always have a value." msgstr "" -#: ../settings/branding.rst:19 -msgid "Logo" +#: ../misc/variables.rst:20 +msgid "Variable Categories" msgstr "" -#: ../settings/branding.rst:16 -msgid "Defines the logo of the application, shown in the login page of Zammad." +#: ../misc/variables.rst:31 +msgid "Wait, What About Custom Objects?" msgstr "" -#: ../settings/branding.rst:18 +#: ../misc/variables.rst:33 msgid "" -"Ensure to hit the \"Submit\" button after uploading the logo. Otherwise your " -"change will not be saved." +"Good point! Of course, we can't predict what objects you might create, but " +"we can give you a hint on how to put the puzzle together to get your custom " +"values." msgstr "" -#: ../settings/branding.rst:22 +#: ../misc/variables.rst:36 msgid "" -"Allows to set the default language of the Zammad instance. The here defined " -"locale mostly acts as a fallback for:" +"For this, we'll talk about the inner part of the variable (so everything " +"within ``#{}``), please put the outer part around to have a valid variable. " +"The first part of the variable name consist of the object type. Currently " +"these are:" msgstr "" -#: ../settings/branding.rst:25 -msgid "user preferences (if Zammad can't detect the users locale)" +#: ../misc/variables.rst:41 +msgid "Ticket (``ticket``)" msgstr "" -#: ../settings/branding.rst:26 -msgid "CSV output (reporting, time accounting)" +#: ../misc/variables.rst:42 +msgid "User (``user``)" msgstr "" -#: ../settings/branding.rst:30 -msgid "Define the timezone of your Zammad installation." +#: ../misc/variables.rst:43 +msgid "Organization (``organization``)" msgstr "" -#: ../settings/branding.rst:32 +#: ../misc/variables.rst:44 +msgid "Group (``group``)" +msgstr "" + +#: ../misc/variables.rst:46 msgid "" -"This does not have any effect on timings for your agents or how Zammad " -"stores date and time values." +"The second part is the name of the attribute. This is the name you define " +"during object creation and can be found within the object attribute menu at " +"any time. The first and second part of a variable is divided by a point, e." +"g.: ``ticket.number`` which will in total be ``#{ticket.number}``." msgstr "" -#: ../settings/branding.rst:35 -msgid "Changing this value has direct consequences on the following areas:" +#: ../misc/variables.rst:51 +msgid "" +"Now, in some situations it's possible that you'll need to use a third part. " +"The best example for such a situation would be a ``select`` or ``tree-" +"select`` field which will by default return the key value, not it's display " +"name. For this, just extend your variable with ``.value``. This will result " +"in ``#{ticket.select.value}``." msgstr "" -#: ../settings/branding.rst:37 -msgid ":doc:`/manage/scheduler` tasks" +#: ../misc/variables.rst:60 +msgid "Using Translated Variables" msgstr "" -#: ../settings/branding.rst:38 -msgid "search indexing (and thus reporting)" +#: ../misc/variables.rst:62 +msgid "" +"If you want to use a translated variable in triggers or schedulers, you can " +"extend the placeholder like this: ``#{t(ticket.state.name)}``. The ``t`` " +"tells Zammad to search for fitting translated strings. The used output " +"language is based on the system language of Zammad which you can set in the " +"admin panel under :doc:`/settings/branding` or based on the selected locale " +"in the trigger/scheduler edit dialog." msgstr "" -#: ../settings/branding.rst:40 -msgid "calendar subscriptions" +#: ../misc/variables.rst:69 +msgid "" +"A possible use-case: you want to send your customers updates on tickets via " +"trigger or scheduler which should include the state of the ticket. Using the " +"default ``#{ticket.state.name}`` (without the translation flag ``t()``) " +"would lead to the output of the original (english) name of the state." msgstr "" -#: ../settings/branding.rst:41 -msgid "browser printing" +#: ../misc/variables.rst:75 +msgid "Date and Time Formatting" msgstr "" -#: ../settings/branding.rst:43 +#: ../misc/variables.rst:77 msgid "" -"Please note that some of above are fallbacks in case Zammad could not detect " -"the agents timezone correctly." +"The system (trigger/scheduler selected) locale and timezone predefines a " +"default format of date and timestamp. This format is customizable by using " +"the ``dt()`` method." msgstr "" -#: ../settings/branding.rst:77 -msgid "Pretty Date" +#: ../misc/variables.rst:79 +msgid "The method arguments are as follows:" msgstr "" -#: ../settings/branding.rst:47 -msgid "" -"This setting allows you to define how Zammad should display time stamps " -"within the interface to all users." +#: ../misc/variables.rst:81 +msgid "The date or timestamp variable you want to format." msgstr "" -#: ../settings/branding.rst:50 -msgid "" -"This does not have any effect on how Zammad returns e.g. time values via " -"variables." +#: ../misc/variables.rst:82 +msgid "The output format string." msgstr "" -#: ../settings/branding.rst:77 -msgid "Choose in between the following options:" +#: ../misc/variables.rst:83 +msgid "The timezone to apply (optional)." msgstr "" -#: ../settings/branding.rst:64 -msgid "relative" +#: ../misc/variables.rst:85 +#: ../system/objects/external-data-source-example.rst:23 +msgid "**Example:**" msgstr "" -#: ../settings/branding.rst:55 +#: ../misc/variables.rst:86 msgid "" -"This timestamp shows a relative time span until it switches to a date. Over " -"time, it will change as follows:" +"``#{dt(ticket.updated_at, \"%A %Y-%m-%d %H:%M in the office\", \"Europe/" +"Berlin\")}``" msgstr "" -#: ../settings/branding.rst:58 -msgid "just now" +#: ../misc/variables.rst:87 +msgid "Monday, 2024-03-18 15:31 in the office" msgstr "" -#: ../settings/branding.rst:59 -msgid "5 minutes ago" +#: ../misc/variables.rst:89 +msgid "" +"If you want to use our example, make sure to paste the string above without " +"formatting (``CTRL+Shift+v``), otherwise it won't work." msgstr "" -#: ../settings/branding.rst:60 -msgid "3 days 1 hour ago" +#: ../misc/variables.rst:93 +msgid "The following table lists available format directives:" msgstr "" -#: ../settings/branding.rst:61 -msgid "``03/04/2022``" +#: ../misc/variables.rst:99 +msgid "Parameter" msgstr "" -#: ../settings/branding.rst:63 -msgid "Hovering the timestamp helps, you'll always get a clean timestamp then." +#: ../misc/variables.rst:102 +msgid "``%Y``" msgstr "" -#: ../settings/branding.rst:71 -msgid "absolute" +#: ../misc/variables.rst:103 +msgid "Year with 4 digits" msgstr "" -#: ../settings/branding.rst:67 -msgid "" -"This timestamp always includes the week day. For one week after creation, " -"the timestamp will not contain the date itself: Thursday 18:35." +#: ../misc/variables.rst:104 +msgid "Use ``%y`` for year with 2 digits" msgstr "" -#: ../settings/branding.rst:71 -msgid "After a week it will switch to: ``Friday 4. Mar 16:00``." +#: ../misc/variables.rst:105 +msgid "``%m``" msgstr "" -#: ../settings/branding.rst:76 -msgid "timestamp" +#: ../misc/variables.rst:106 +msgid "Month of year (as number with zero-padding)" msgstr "" -#: ../settings/branding.rst:74 -msgid "" -"This will cause Zammad to show a complete timestamp according to your locale " -"defaults. For English this could be e.g. ``2022/12/03 2:40 pm`` or for " -"German e.g. ``12.03.2022 14:40``." +#: ../misc/variables.rst:107 +msgid "Use ``%-m`` for month without zero-padding" msgstr "" -#: ../settings/branding.rst:78 -msgid "Default setting: ``relative``." +#: ../misc/variables.rst:108 +msgid "``%d``" msgstr "" -#: ../settings/security.rst:2 -msgid "Security" +#: ../misc/variables.rst:109 +msgid "Day of month (as number with zero-padding)" msgstr "" -#: ../settings/security.rst:4 -msgid "" -"For your overview we split each tab within security settings into its own " -"page:" +#: ../misc/variables.rst:110 +msgid "Use ``%e`` for day without zero-padding" msgstr "" -#: ../settings/security/base.rst:2 ../settings/system/base.rst:2 -#: ../settings/ticket.rst:8 -msgid "Base" +#: ../misc/variables.rst:111 +msgid "``%H``" msgstr "" -#: ../settings/security/base.rst:5 -msgid "New User Accounts" +#: ../misc/variables.rst:112 +msgid "Hour of day in 24h notation with zero-padding" msgstr "" -#: ../settings/security/base.rst:9 -msgid "" -"Activates the `register as a new customer` function on the login page. If " -"set to ``no`` only administrators or agents can create new accounts manually." +#: ../misc/variables.rst:113 +msgid "Use ``%k`` for hour without zero-padding" msgstr "" -#: ../settings/security/base.rst:13 ../settings/security/base.rst:38 -#: ../settings/security/base.rst:66 -msgid "Default setting: ``yes``" +#: ../misc/variables.rst:114 +msgid "``%I``" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing activated \"New User Accounts\" setting" +#: ../misc/variables.rst:115 +msgid "Hour of day in 12h notation with zero-padding" msgstr "" -#: ../settings/security/base.rst:22 +#: ../misc/variables.rst:116 msgid "" -"Deactivation of above function **does not** deactivate automatic account " -"creation! This means: If a user writes e.g. an email to Zammad and has no " -"account yet, Zammad will automatically create the account. User accounts are " -"a direct dependency of tickets and thus technically mandatory." +"Use ``%l`` for hour without zero-padding and ``%p`` / ``%P`` for meridian " +"indicator" msgstr "" -#: ../settings/security/base.rst:29 -msgid "Lost Password" +#: ../misc/variables.rst:117 +msgid "``%M``" msgstr "" -#: ../settings/security/base.rst:33 -msgid "" -"Activates the `lost password` function on the login page. If set to ``no`` " -"only administrators may change the user's password - users may update their " -"own password if they're still logged in and they have the required :doc:" -"`permission `." +#: ../misc/variables.rst:118 +msgid "Minute of hour" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing activated \"Lost Password\" setting" +#: ../misc/variables.rst:120 +msgid "``%S``" msgstr "" -#: ../settings/security/base.rst:49 -msgid "" -"With third party authentications - but especially LDAP - you may want to " -"disable this function. Zammad **will not** change third party login " -"passwords and instead set or change the local password!" +#: ../misc/variables.rst:121 +msgid "Second of Minute" msgstr "" -#: ../settings/security/base.rst:56 -msgid "Password Login" +#: ../misc/variables.rst:123 +msgid "``%A``" msgstr "" -#: ../settings/security/base.rst:60 -msgid "" -"Activates the username & password login by default and if no third-party " -"login is activated. Disabling password login on the Zammad login page only " -"takes effect if you enable any :doc:`third-party`." +#: ../misc/variables.rst:124 +msgid "Weekday name" msgstr "" -#: ../settings/security/base.rst:64 -msgid "See :doc:`third-party` for supported third-party logins." +#: ../misc/variables.rst:125 +msgid "Use ``%a`` for abbreviated name or ``%^A`` for uppercase name" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing de-activated \"Password Login\" setting" +#: ../misc/variables.rst:126 +msgid "``%B``" msgstr "" -#: ../settings/security/base.rst:77 -msgid "" -"To help administrators to overcome \"login issues\", Zammad automatically " -"offers a password request for administrator users. This allows you to adjust " -"Third-Party applications even if the login does no longer work!" +#: ../misc/variables.rst:127 +msgid "Month name" msgstr "" -#: ../settings/security/base.rst:84 -msgid "Session Timeout" +#: ../misc/variables.rst:128 +msgid "Use ``%b`` for abbreviated name" msgstr "" -#: ../settings/security/base.rst:86 -msgid "" -"All settings below by default are set to ``4 weeks``. Session Timeout " -"defines the life time of a users session. As soon as it's reached, Zammad " -"will automatically log off the session in question." +#: ../misc/variables.rst:129 +msgid "``%U``" msgstr "" -#: ../settings/security/base.rst:91 -msgid "" -"Zammad takes the highest value set assigned for the user based on the " -"permissions." +#: ../misc/variables.rst:130 +msgid "Week number of current year" msgstr "" -#: ../settings/security/base.rst:94 -msgid "``admin``" +#: ../misc/variables.rst:131 +msgid "Use ``%W`` for a different calculation method" msgstr "" -#: ../settings/security/base.rst:96 -msgid "``ticket.customer``" +#: ../misc/variables.rst:134 +msgid "" +"We support the known format directives for the Ruby built-in method " +"``strftime`` of the ``DateTime`` class. For more information, see `here " +"`_." msgstr "" -#: ../settings/security/base.rst:97 -msgid "``default`` (fallback if user doesn't have above permissions set)" +#: ../misc/variables/article.rst:2 +msgid "Articles" msgstr "" -#: ../settings/security/base.rst:99 +#: ../misc/variables/article.rst:4 ../misc/variables/config.rst:4 +#: ../misc/variables/current-user.rst:4 ../misc/variables/ticket.rst:4 msgid "" -"All settings act independently from each other allowing you to disable the " -"timeouts for e.g. admins, but not agents." +"If you're missing variables or are not sure if something is not working as " +"expected, feel free to ask over at the `Community `_." msgstr "" -#: ../settings/security/base.rst:115 -#: ../system/integrations/checkmk/api-reference.rst:13 -msgid "Example" -msgstr "Exempel" +#: ../misc/variables/article.rst:6 +msgid "" +"Below you can find all available ticket article-based variables within " +"Zammad. These can be called via triggers for example. If you're unsure if " +"Zammad does support variables at the point you're at, you can try to type " +"``::`` to check." +msgstr "" -#: ../settings/security/base.rst:107 -msgid "Let's suppose you configured the following session timeouts" +#: ../misc/variables/article.rst:9 ../misc/variables/config.rst:9 +#: ../misc/variables/ticket.rst:9 +msgid "" +"The below list gives you an example what kind of data you can expect, it's " +"not intended to explain the data itself." msgstr "" -#: ../settings/security/base.rst:104 -msgid "default: 3 weeks" +#: ../misc/variables/article.rst:11 +msgid "Article Variables" msgstr "" -#: ../settings/security/base.rst:105 -msgid "admin: 2 weeks" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "name" msgstr "" -#: ../settings/security/base.rst:106 -msgid "ticket.agent: 4 weeks" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "variable" msgstr "" -#: ../settings/security/base.rst:107 -msgid "ticket.customer: 1 week" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "example" msgstr "" -#: ../settings/security/base.rst:115 -msgid "This results in the following situations" +#: ../misc/variables/article.rst:1 +msgid "Article > Cc" msgstr "" -#: ../settings/security/base.rst:110 -msgid "a user with ``admin`` permission will have a timeout of 2 weeks" +#: ../misc/variables/article.rst:1 +msgid "``#{article.cc}``" msgstr "" -#: ../settings/security/base.rst:111 -msgid "" -"a user with ``admin`` and ``ticket.agent`` permissions will have a timeout " -"of 2 weeks" +#: ../misc/variables/article.rst:1 +msgid "``jdoe@example.com, company@example.com``" msgstr "" -#: ../settings/security/base.rst:113 -msgid "" -"a user with ``ticket.customer`` permission will have a timeout of 1 week" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Address" msgstr "" -#: ../settings/security/base.rst:115 -msgid "" -"a user with neither ``admin``, ``ticket.agent`` nor ``ticket.customer`` " -"permissions will have a timeout of 3 weeks" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.address}``" msgstr "" -#: ../settings/security/password.rst:4 -msgid "" -"This section allows you to define password requirements for the local user " -"accounts." +#: ../misc/variables/article.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:9 -msgid "" -"Zammad does **not** allow you to change your LDAP password, instead, it will " -"set a password in its local database which might confuse your users. This " -"might be addressed in the future by `#1169 `_." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Department" msgstr "" -#: ../settings/security/password.rst:14 -msgid "**Exception for admins**" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.department}``" msgstr "" -#: ../settings/security/password.rst:16 -msgid "" -"Please note that below password policies *do not* affect administrators " -"setting passwords on user accounts. While this seems strange and not safe we " -"believe that an administrator knowing an user's password is insecure as well." +#: ../misc/variables/article.rst:1 +msgid "``Sales`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:21 -msgid "The suggested workflow is either:" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Email" msgstr "" -#: ../settings/security/password.rst:23 -msgid "" -"to use third party logins to not require local passwords at all **- or -**" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.email}``" msgstr "" -#: ../settings/security/password.rst:25 -msgid "to require your *user to reset the password* upon first login." +#: ../misc/variables/article.rst:1 +msgid "``jdoe@example.com``" msgstr "" -#: ../settings/security/password.rst:27 -msgid "" -"This way administrators are not required to set a user's password at all!" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Fax" msgstr "" -#: ../settings/security/password.rst:31 -msgid "Maximum Failed Logins" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.fax}``" msgstr "" -#: ../settings/security/password.rst:33 -msgid "" -"You can choose a value between ``4`` and ``20``. This defines how often a " -"login to a user account may fail until Zammad will lock it. Your users can " -"always use the \"forgot password\" function to change their password and " -"unlock their account." +#: ../misc/variables/article.rst:1 +msgid "``+4930123456789`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:38 -msgid "The default value is ``10``." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Firstname" msgstr "" -#: ../settings/security/password.rst:42 -msgid "Beside changing the user's password, you can also unlock accounts via" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.firstname}``" msgstr "" -#: ../settings/security/password.rst:44 -msgid ":ref:`user management list `" +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Joe`` or empty if not set" msgstr "" -#: ../settings/security/password.rst:45 -msgid ":docs:`console `" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Lastname" msgstr "" -#: ../settings/security/password.rst:46 -msgid ":docs:`API `" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.lastname}``" msgstr "" -#: ../settings/security/password.rst:50 -msgid "Failed logins via LDAP no longer lock accounts." +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +#: ../misc/variables/ticket.rst:1 +msgid "``Doe`` or empty if not set" msgstr "" -#: ../settings/security/password.rst:53 -msgid "2 Lower Case And 2 Upper Case Characters" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Login" msgstr "" -#: ../settings/security/password.rst:55 -msgid "" -"You can add complexity to passwords by enforcing at least 2 upper and lower " -"case characters." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.login}``" msgstr "" -#: ../settings/security/password.rst:58 ../settings/security/password.rst:83 -msgid "The default value is ``no``." +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +#: ../misc/variables/ticket.rst:1 +msgid "``jdoe``" msgstr "" -#: ../settings/security/password.rst:62 -msgid "Minimum Length" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Mobile" msgstr "" -#: ../settings/security/password.rst:64 -msgid "" -"This defines the minimum password length required for users to provide (from " -"``4`` to ``20``)." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.mobile}``" msgstr "" -#: ../settings/security/password.rst:67 -msgid "The default value is ``6``." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Note" msgstr "" -#: ../settings/security/password.rst:71 -msgid "Digit Required" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.note}``" msgstr "" -#: ../settings/security/password.rst:73 -msgid "This enforces your users to use at least one digit within the password." +#: ../misc/variables/article.rst:1 +msgid "``Some note about user`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:75 -msgid "The default value is ``yes``." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Phone" msgstr "" -#: ../settings/security/password.rst:78 -msgid "Special Character Required" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.phone}``" msgstr "" -#: ../settings/security/password.rst:80 -msgid "" -"This setting allows you to improve your password quality even more by " -"enforcing the password to contain at least one special character." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > VIP" msgstr "" -#: ../settings/security/ssl-certificates.rst:2 -msgid "SSL Certificates" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.vip}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:7 -msgid "" -"Zammad offers the possibility to upload custom certificates and custom " -"Certificate Authority (CA) certificates. This can be useful if you want to " -"connect Zammad the secure way to other systems which are using custom " -"certificates." +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +msgid "``true`` or ``false``" msgstr "" -#: ../settings/security/ssl-certificates.rst:12 -msgid "" -"An example usecase might be: You have an internal LDAP server that is not " -"accessible from the internet, and you want a SSL-encrypted connection, using " -"a custom certificate." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Web" msgstr "" -#: ../settings/security/ssl-certificates.rst:19 -msgid "" -"You should have an existing custom certificate file and/or a custom CA " -"certificate file, which you want to add to Zammad. As filetype ``.crt`` is " -"supported and the certificate format has to be PEM (Base64 ASCII)." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.web}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:25 -msgid "" -"When you import a custom CA certificate, all certificates generated with " -"this are trusted. This can be useful if you have more than one system/" -"certificate you want to connect to and the certificates are issued from the " -"same custom CA." +#: ../misc/variables/article.rst:1 +msgid "``https://zammad.com`` or empty if not set in user object" msgstr "" -#: ../settings/security/ssl-certificates.rst:31 -msgid "Add a Certificate" +#: ../misc/variables/article.rst:1 +msgid "Article > Created" msgstr "" -#: ../settings/security/ssl-certificates.rst:33 -msgid "" -"To add a custom certificate or a custom CA certificate, head over to the " -"Admin panel > Settings > Security > SSL Certificates. Here you can find a " -"\"Add SSL Certificate\" button. In the dialog you can either select a " -"certificate file or paste the content of the certificate:" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_at}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate adding dialog" +#: ../misc/variables/article.rst:1 +msgid "``2019-10-08 15:24:47 UTC``" msgstr "" -#: ../settings/security/ssl-certificates.rst:43 -msgid "" -"After selecting a file or pasting the content of the certificate, click on " -"the \"Add\" button to finally upload it to Zammad. Then, the certificates " -"are immediately effective, no restart or similar required." +#: ../misc/variables/article.rst:1 +msgid "Article > From" msgstr "" -#: ../settings/security/ssl-certificates.rst:49 -msgid "" -"Please note that only single certificate files are supported. That means if " -"you want to import a certificate / CA certificate, it must contain **only " -"one** certificate." +#: ../misc/variables/article.rst:1 +msgid "``#{article.from}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:54 -msgid "Certificate Overview" +#: ../misc/variables/article.rst:1 +msgid "" +"``Joe Doe `` may differ, depends on ``FROM`` of send mail" msgstr "" -#: ../settings/security/ssl-certificates.rst:56 -msgid "" -"After you added a certificate, you can see a table with information for each " -"added certificate:" +#: ../misc/variables/article.rst:1 +msgid "Article > Sender > Name" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing table of added certificates" +#: ../misc/variables/article.rst:1 +msgid "``#{article.sender.name}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:64 -msgid "" -"Here you can download the certificate or delete it, if you don't need it " -"anymore." +#: ../misc/variables/article.rst:1 +msgid "``Customer``, ``Agent`` or ``System``" msgstr "" -#: ../settings/security/ssl-certificates.rst:68 -msgid "Deleting Certificates" +#: ../misc/variables/article.rst:1 +msgid "Article > Subject" msgstr "" -#: ../settings/security/ssl-certificates.rst:70 -msgid "" -"If you want to delete a specific certificate, you can do it by clicking on " -"the menu in the actions column and selecting delete:" +#: ../misc/variables/article.rst:1 +msgid "``#{article.subject}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate deletion button" +#: ../misc/variables/article.rst:1 +msgid "``My amazing subject``" msgstr "" -#: ../settings/security/ssl-certificates.rst:79 -msgid "Downloading Certificates" +#: ../misc/variables/article.rst:1 +msgid "Article > Text" msgstr "" -#: ../settings/security/ssl-certificates.rst:81 -msgid "" -"If you want to download your certificates, you can do this as well via " -"corresponding action buttons." +#: ../misc/variables/article.rst:1 +msgid "``#{article.body}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate download button" +#: ../misc/variables/article.rst:1 +msgid "``Test`` without formatting (plain)" msgstr "" -#: ../settings/security/third-party.rst:13 -msgid "Login Providers" +#: ../misc/variables/article.rst:1 +msgid "Article > TicketID" msgstr "" -#: ../settings/security/third-party.rst:2 -msgid "Third-Party Applications" +#: ../misc/variables/article.rst:1 +msgid "``#{article.ticket_id}``" msgstr "" -#: ../settings/security/third-party.rst:4 -msgid "" -"Third party authentication is a great way to help your users to login to " -"Zammad more easily. If the account is yet unknown, Zammad will create a new " -"user automatically, without the user needed to interact (e.g. type in his " -"name). Another big advantage of this feature is that your user doesn't need " -"to remember another password." +#: ../misc/variables/article.rst:1 +msgid "``1`` (not ticket number)" msgstr "" -#: ../settings/security/third-party.rst:10 -msgid "" -"You can deactivate logging in via :ref:`security_password_login` if any of " -"the mentioned authentication providers are enabled in your instance." +#: ../misc/variables/article.rst:1 +msgid "Article > To" msgstr "" -#: ../settings/security/third-party.rst:27 -msgid "" -"We're currently missing documentation for the following login providers:" +#: ../misc/variables/article.rst:1 +msgid "``#{article.to}``" msgstr "" -#: ../settings/security/third-party.rst:29 -msgid "LinkedIn" +#: ../misc/variables/article.rst:1 +msgid "``helpdesk@example.com``" msgstr "" -#: ../settings/security/third-party.rst:30 -msgid "Weibo" +#: ../misc/variables/article.rst:1 +msgid "Article > Type > Name" msgstr "" -#: ../settings/security/third-party.rst:35 -msgid "Automatic Account Link on Initial Logon" +#: ../misc/variables/article.rst:1 +msgid "``#{article.type.name}``" msgstr "" -#: ../settings/security/third-party.rst:37 +#: ../misc/variables/article.rst:1 msgid "" -"In general there's two possible options for Zammad on how to deal with " -"already known users as they try to authenticate against a third-party " -"application. By default, Zammad will not automatically link \"unknown\" " -"authentication providers to existing accounts." +"``email`` (`list of article types `_)" msgstr "" -#: ../settings/security/third-party.rst:42 -msgid "" -"This means that the user has to manually link authentication providers to " -"their accounts (for more about this :user-docs:`consult the user " -"documentation `)." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Address" msgstr "" -#: ../settings/security/third-party.rst:46 -msgid "" -"Sometimes this doesn't come in handy as this also means you'll receive error " -"messages about \"email address being in use already\" for (yet) unknown " -"third-party authentication methods." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.address}``" msgstr "" -#: ../settings/security/third-party.rst:50 -msgid "" -"If you want to allow your users to always be able to log in, no matter what, " -"you may want to enable ``Automatic account link on initial logon``." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Department" msgstr "" -#: ../settings/security/third-party.rst:None -msgid "" -"Screenshot highlighting the \"Automatic account link on initial logon\"\n" -"setting" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.department}``" msgstr "" -#: ../settings/security/third-party.rst:60 -msgid "Automatic Account Linking Notification" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Email" msgstr "" -#: ../settings/security/third-party.rst:64 -msgid "" -"To improve security and your users awareness, you can enable Zammad to " -"notify your users when a new third-party application has been linked to " -"their account." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.email}``" msgstr "" -#: ../settings/security/third-party.rst:68 -msgid "" -"This notification is sent out once per third-party application. Zammad does " -"also mention the method used, e.g.: ``Microsoft``." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Fax" msgstr "" -#: ../settings/security/third-party.rst:71 -msgid "By default this setting is not active (set to ``no``)." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.fax}``" msgstr "" -#: ../settings/security/third-party.rst:0 -msgid "" -"Screenshot showing sample notification mail after initial\n" -"third-party linking" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Firstname" msgstr "" -#: ../settings/security/third-party.rst:85 -msgid "" -"This notification is only sent if the account in question already exists. If " -"the login via the third-party also creates the missing account, the " -"notification will be skipped." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.firstname}``" msgstr "" -#: ../settings/security/third-party.rst:89 -msgid "This means it only affects:" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Lastname" msgstr "" -#: ../settings/security/third-party.rst:91 -msgid "manual account linking within the third-party page of the users profile" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.lastname}``" msgstr "" -#: ../settings/security/third-party.rst:92 -msgid "" -"logging into an existing local account by utilizing the *automatic account " -"link on initial logon* functionality" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Login" msgstr "" -#: ../settings/security/third-party.rst:None -msgid "" -"Screenshot showing the \"automatic account linking notification\"\n" -"setting" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.login}``" msgstr "" -#: ../settings/security/third-party.rst:100 -msgid "No User Creation on Logon" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Mobile" msgstr "" -#: ../settings/security/third-party.rst:102 -msgid "" -"By default, Zammad will create a new user account if the user logs in via a " -"third-party application and the account doesn't exist yet." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.mobile}``" msgstr "" -#: ../settings/security/third-party.rst:105 -msgid "" -"If you want to prevent Zammad from creating new accounts on logon, you can " -"disable this feature by setting ``No user creation on logon`` to ``yes``." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Note" msgstr "" -#: ../settings/security/third-party.rst:None -msgid "Screenshot showing the \"no user creation on logon\" setting" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.note}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via Facebook To do " -"so, you need to follow these steps:" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Phone" msgstr "" -#: ../settings/security/third-party/facebook.rst:9 -msgid "Register Facebook App" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.phone}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:11 -msgid "" -"Visit [https://developers.facebook.com/apps/] and click on \"Add a new App\"" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > VIP" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "initial page" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.vip}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:17 -msgid "After that enter the app settings" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Web" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "Create App" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.web}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:22 -msgid "Navigate to \"Settings\" and fill in this infromation" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "App Settings" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_at}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:27 -msgid "Navigate to app review and Check \"Make [appname] public?\"" +#: ../misc/variables/article.rst:1 +msgid "Article > Visibility" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "App Review" +#: ../misc/variables/article.rst:1 +msgid "``#{article.internal}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:35 -msgid "Configure Zammad as Facebook App" +#: ../misc/variables/article.rst:1 +msgid "``false`` or ``true`` (false if not internal)" msgstr "" -#: ../settings/security/third-party/facebook.rst:37 -msgid "" -"Navigate to \"Admin -> Security -> Third Party Applications\" and enter the " -"App ID and the App Secret. You can find this Key in the Dashbard of your " -"Facebok app." +#: ../misc/variables/article.rst:1 +msgid "Article Text as HTML (not referenced)" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "Zammad Configuration" +#: ../misc/variables/article.rst:1 +msgid "``#{article.body_as_html}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:44 -#: ../settings/security/third-party/github.rst:43 -#: ../settings/security/third-party/gitlab.rst:46 -msgid "" -"Now you can link accounts via \"Avatar -> Profile -> Link Accounts\" or " -"login via Zammad login page." +#: ../misc/variables/article.rst:1 +msgid "``Test`` with formatting" msgstr "" -#: ../settings/security/third-party/github.rst:2 -#: ../system/integrations/github.rst:2 -msgid "GitHub" +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "Ticket > Article#" msgstr "" -#: ../settings/security/third-party/github.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via GitHub. To " -"activate the quick login you need to enable OAuth for GitHub." +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "``#{ticket.article_count}``" msgstr "" -#: ../settings/security/third-party/github.rst:8 -msgid "Register GitHub App" +#: ../misc/variables/article.rst:1 +msgid "``1`` number of ticket articles" msgstr "" -#: ../settings/security/third-party/github.rst:10 -msgid "" -"Visit https://www.github.com/settings/applications/new and enter the app " -"settings. As callback URL enter \"https://zammad_host/auth/github/callback\" " -"where zammad_host has to be replaced with your Zammad FQDN" +#: ../misc/variables/config.rst:2 +msgid "Config" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "Register OAuth app on www.github.com" +#: ../misc/variables/config.rst:6 +msgid "" +"Below you'll find config related variables. These hold useful configuration " +"information that you can use within e.g. triggers to show necessary " +"information to your customer." msgstr "" -#: ../settings/security/third-party/github.rst:19 -msgid "Configure Zammad as GitHub App" +#: ../misc/variables/config.rst:11 +msgid "Config Variables" msgstr "" -#: ../settings/security/third-party/github.rst:21 -msgid "" -"Enter the \"APP ID\" and the \"APP SECRET\" from the GitHub OAUTH " -"Applications Dashboard" +#: ../misc/variables/config.rst:1 +msgid "Config > Fully Qualified Domain Name" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub config in Zammad admin interface" +#: ../misc/variables/config.rst:1 +msgid "``#{config.fqdn}``" msgstr "" -#: ../settings/security/third-party/github.rst:28 -msgid "" -"After you configured the GitHub credentials and activated the login method, " -"you should see a new icon on the login page." +#: ../misc/variables/config.rst:1 +msgid "``zammad.example.com``" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub logo on login page" +#: ../misc/variables/config.rst:1 +msgid "Config > HTTP type" msgstr "" -#: ../settings/security/third-party/github.rst:34 -msgid "" -"If you click on the icon you will be redirected to GitHub and see something " -"similar to this:" +#: ../misc/variables/config.rst:1 +msgid "``#{config.http_type}``" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub oauth page" +#: ../misc/variables/config.rst:1 +msgid "``https`` or ``http``" msgstr "" -#: ../settings/security/third-party/github.rst:40 -#: ../settings/security/third-party/gitlab.rst:42 -msgid "" -"When you grant the access you will be redirected to your Zammad instance and " -"logged in as a customer." +#: ../misc/variables/config.rst:1 +msgid "Config > Organization" msgstr "" -#: ../settings/security/third-party/gitlab.rst:2 -msgid "Gitlab" +#: ../misc/variables/config.rst:1 +msgid "``#{config.organization}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:4 +#: ../misc/variables/config.rst:1 msgid "" -"It is possible to create a quick login for your helpdesk via Gitlab. To " -"activate the quick login you need to enable OAuth for Gitlab." +"``Zammad GmbH`` value set in `Branding `_" msgstr "" -#: ../settings/security/third-party/gitlab.rst:8 -msgid "Register Gitlab App" +#: ../misc/variables/config.rst:1 +msgid "Config > Product Name" msgstr "" -#: ../settings/security/third-party/gitlab.rst:10 -msgid "To register an app in Gitlab open your profile and select applications." +#: ../misc/variables/config.rst:1 +msgid "``#{config.product_name}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:12 +#: ../misc/variables/config.rst:1 msgid "" -"As callback URL enter \"https://zammad-fqdn/auth/gitlab/callback\" where " -"zammad-fqdn has to be replaced with your Zammad FQDN" +"``Helpdesk`` value set in `Branding `_" msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Register OAuth app on gitlab instance" +#: ../misc/variables/config.rst:1 +msgid "Config > SystemID" msgstr "" -#: ../settings/security/third-party/gitlab.rst:18 -msgid "Just select *read_user* under scopes as in the screenshot and save it." +#: ../misc/variables/config.rst:1 +msgid "``#{config.system_id}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:21 -msgid "Configure Zammad as Gitlab App" +#: ../misc/variables/config.rst:1 +msgid "``31`` (value between 1 and 99)" msgstr "" -#: ../settings/security/third-party/gitlab.rst:23 -msgid "" -"Enter the \"APP ID\" and the \"APP SECRET\" from the Gitlab OAUTH " -"Applications Dashboard and your Gitlab-URL in the \"SITE\" field." +#: ../misc/variables/config.rst:1 +msgid "Config > Ticket Hook" msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab config in Zammad admin interface" +#: ../misc/variables/config.rst:1 +msgid "``#{config.ticket_hook}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:30 -msgid "" -"After you configured the Gitlab credentials and activated the login method, " -"you should see a new icon on the login page." +#: ../misc/variables/config.rst:1 +msgid "``Ticket#``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab logo on login page" +#: ../misc/variables/current-user.rst:2 +msgid "Current User" msgstr "" -#: ../settings/security/third-party/gitlab.rst:36 +#: ../misc/variables/current-user.rst:6 msgid "" -"If you click on the icon you will be redirected to Gitlab and see something " -"similar to this:" +"Current user variables always return values of the current user that caused " +"e.g. a trigger to run." msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab oauth page" +#: ../misc/variables/current-user.rst:8 +msgid "" +"Due to the above fact, these variables are often not (yet) set or available " +"for usage." msgstr "" -#: ../settings/security/third-party/google.rst:4 +#: ../misc/variables/current-user.rst:10 msgid "" -"With some easy and fast steps, you can enable Zammad to authenticate your " -"users via Google." +"In situations where e.g. schedulers or triggers run, this most likely is " +"nothing you want to use." msgstr "" -#: ../settings/security/third-party/google.rst:8 -msgid "Register a Google App" +#: ../misc/variables/current-user.rst:13 +msgid "Current User Variables" msgstr "" -#: ../settings/security/third-party/google.rst:10 -msgid "" -"First of all, we need to create a new project - you can skip this step if " -"you already have one." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Address" msgstr "" -#: ../settings/security/third-party/google.rst:15 -msgid "" -"Use this link to create a new project: https://console.cloud.google.com/" -"projectcreate" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.address}``" msgstr "" -#: ../settings/security/third-party/google.rst:18 -msgid "" -"Now expand the menu, expand \"APIs & Services\" and select \"Credentials\". " -"Go to the tab \"OAuth consent screen\" first and ensure to fill in the " -"requested information - without doing so you can't create credentials!" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set" msgstr "" -#: ../settings/security/third-party/google.rst:None -msgid "Creating a consent screen" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Avatar" msgstr "" -#: ../settings/security/third-party/google.rst:25 -msgid "" -"After filling in and saving the consent screen information, you can go to " -"the \"Credentials\" tab and create new \"OAuth client ID\"-Credentials." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/google.rst:28 -msgid "" -"Fill in the necessary information as follows and replace ``zammad_host`` " -"with your FQDN:" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "avatar picture with width and height in pixel (e.g. 60,60)" msgstr "" -#: ../settings/security/third-party/google.rst:31 -msgid "**Application type** ``[x] Web application``" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created at" msgstr "" -#: ../settings/security/third-party/google.rst:34 -msgid "**Authorized JavaScript origins** ``https://zammad_host/``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_at}``" msgstr "" -#: ../settings/security/third-party/google.rst:37 -msgid "" -"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" -"callback``" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC``" msgstr "" -#: ../settings/security/third-party/google.rst:None -msgid "Adding a new OAuth client ID" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Address" msgstr "" -#: ../settings/security/third-party/google.rst:43 -msgid "" -"After creating the credentials, go to your Zammad installation and navigate " -"to \"Admin > Security > Third Party Applications\" > Google. Enter your " -"Client ID and Client secret here." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.address}``" msgstr "" -#: ../settings/security/third-party/google.rst:None -msgid "Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Avatar" msgstr "" -#: ../settings/security/third-party/google.rst:50 -msgid "After submitting, the login via Google can be used." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:2 -msgid "Microsoft" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Department" msgstr "" -#: ../settings/security/third-party/microsoft.rst:4 -msgid "" -"Zammad's Microsoft connection allows your users with Microsoft accounts to " -"login. This works for Azure users as well and can be an alternative to :doc:" -"`/system/integrations/ldap/index`." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.department}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:10 -msgid "" -"This documentation part does not cover our :doc:`📧 Microsoft 365 email " -"channel `." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Sales`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screenshot showing Microsoft login button on Zammad login screen." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Email" msgstr "" -#: ../settings/security/third-party/microsoft.rst:30 -#: ../settings/security/third-party/microsoft.rst:53 -msgid "Supported account types:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.email}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:22 -msgid "" -"Please note that Zammad only supports these account types (App dependent):" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``jdoe@customer.tld``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:35 -msgid "Avatars of signing in users:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Fax" msgstr "" -#: ../settings/security/third-party/microsoft.rst:33 -msgid "" -"Zammad currently ignores user avatars. If the user is registered with e.g. " -"Gravatar, Zammad will fetch the avatar from there if enabled. See :doc:" -"`Zammad Image Service ` for more." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.fax}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:38 -msgid "Step 1 - Register a Microsoft App for Zammad" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``004930123464789`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:40 -msgid "" -"Login to the `Microsoft Azure Portal `_ and " -"navigate to App registrations to create a new app. Provide the requested " -"information as follows and register your app." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Firstname" msgstr "" -#: ../settings/security/third-party/microsoft.rst:46 -msgid "Name:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.firstname}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:45 -msgid "" -"Any meaningful name fitting, this name will be displayed to users trying to " -"authenticate with this app." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``John`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:49 -msgid "Choose one of the above mentioned account types (see Limitations)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Lastname" msgstr "" -#: ../settings/security/third-party/microsoft.rst:51 -msgid "" -"The correct account type depends on your use case. If you want to use the " -"authentication internal only, choose the first option. If you're unsure, use " -"the \"Help me choose...\" link." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.lastname}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:58 -msgid "Redirect URI (optional):" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Login" msgstr "" -#: ../settings/security/third-party/microsoft.rst:56 -msgid "" -"Select web and provide your callback URL. The callback URL looks like this: " -"``https://zammad.domain.tld/auth/microsoft_office365/callback``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.login}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to register a Microsoft app" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Mobile" msgstr "" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "Within **API permissions** add the following permissions:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.mobile}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:69 -msgid "``User.Read``" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``0049176123456789`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "Contacts" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Note" msgstr "" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "``Contacts.Read``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.note}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:73 -msgid "" -"You can find these permissions within *Microsoft Graph → Delegated " -"permissions*." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Some note to this user`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to add required API permissions" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Phone" msgstr "" -#: ../settings/security/third-party/microsoft.rst:80 -msgid "" -"Within **Certificates & secrets** create a new client secret. Note down the " -"returned secret **value** for later. **Do not** use the secret ID!" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.phone}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to create a new app secret" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``004930123456789`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:88 -msgid "" -"From **Overview** copy your apps *Application (client) ID*. If you're using " -"a single tenant app, please also copy *Directory (tenant) ID*. You now have " -"all required information for Zammad." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > VIP" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to retreive application client and tenant IDs" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.vip}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:98 -msgid "Step 2 - Add App Credentials to Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Web" msgstr "" -#: ../settings/security/third-party/microsoft.rst:100 -msgid "" -"Navigate to Security > Third-party Applications (Tab) within Zammad's admin " -"settings. Scroll down to the section *Authentication via Microsoft* and fill " -"in the required information." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.web}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:105 -msgid "App ID:" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``https://zammad.org`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:105 -msgid "This is your *Application (client) ID*." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Department" msgstr "" -#: ../settings/security/third-party/microsoft.rst:108 -msgid "App secret:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.department}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:108 -msgid "This is your *client secret* (value)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Email" msgstr "" -#: ../settings/security/third-party/microsoft.rst:113 -msgid "App Tenant ID:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.email}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:111 -msgid "" -"**optional** only required for apps that use account type *Accounts in this " -"organizational directory only (Default Directory only - Single tenant).*" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Fax" msgstr "" -#: ../settings/security/third-party/microsoft.rst:115 -msgid "" -"Apply your settings by pressing submit and activate *Authentication via " -"Microsoft*." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.fax}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "" -"Screencast showing how to add app credentials and activating the\n" -"authentication method" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Firstname" msgstr "" -#: ../settings/security/third-party/saml.rst:2 -msgid "SAML" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.firstname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:4 -msgid "" -"Connect your SAML (Security Assertion Markup Language) identity provider as " -"a single sign-on (SSO) method." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Lastname" msgstr "" -#: ../settings/security/third-party/saml.rst:7 -msgid "" -"SAML is an open standard for SSO authentication (among other things). Sign-" -"ins are shared across multiple **service providers** and managed by a " -"central **identity provider** (IdP)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.lastname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:11 -msgid "" -"In this case, the service provider is Zammad, and the IdP is a software " -"service that you either host or subscribe to (*e.g.,* `Keycloak `_, `Redhat SSO Server `_, `ADFS `_, or `Okta `_)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Login" msgstr "" -#: ../settings/security/third-party/saml.rst:18 -msgid "" -"This guide assumes you are already using SAML within your organization (i." -"e., that your IdP is fully set up)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.login}``" msgstr "" -#: ../settings/security/third-party/saml.rst:21 -msgid "" -"Please note: Our instructions are based on connecting Zammad with Keycloak." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Mobile" msgstr "" -#: ../settings/security/third-party/saml.rst:25 -msgid "Step 1: Configure Your IdP" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.mobile}``" msgstr "" -#: ../settings/security/third-party/saml.rst:28 -msgid "Add Zammad as a Client/App" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Note" msgstr "" -#: ../settings/security/third-party/saml.rst:30 -msgid "" -"Import Zammad into your IdP using the XML configuration found at ``https://" -"your.zammad.domain/auth/saml/metadata``." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.note}``" msgstr "" -#: ../settings/security/third-party/saml.rst:33 -msgid "" -"If your IdP doesn't support XML import, you will have to configure Zammad as " -"a new client/app manually using the above XML metadata file for reference." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Domain based assignment" msgstr "" -#: ../settings/security/third-party/saml.rst:36 -msgid "For instance, when you see this tag:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.domain_assignment}``" msgstr "" -#: ../settings/security/third-party/saml.rst:42 -msgid "" -"Set the **Assertion Consumer Service Binding URL** (sometimes also listed as " -"**Valid Redirect URIs**) to ``http://your.zammad.domain/auth/saml/callback``." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Domain" msgstr "" -#: ../settings/security/third-party/saml.rst:47 -msgid "Set Up User Attribute Mapping" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.domain}``" msgstr "" -#: ../settings/security/third-party/saml.rst:49 -msgid "" -"Zammad requests the following user attributes (or “properties”) from the IdP:" +#: ../misc/variables/current-user.rst:1 +msgid "``zammad.com`` or empty if not set" msgstr "" -#: ../settings/security/third-party/saml.rst:51 -msgid "Email address (``email``)" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Name" msgstr "" -#: ../settings/security/third-party/saml.rst:52 -msgid "Full name (``name``)" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.name}``" msgstr "" -#: ../settings/security/third-party/saml.rst:53 -msgid "Given name (``first_name``)" +#: ../misc/variables/current-user.rst:1 +msgid "``Zammad GmbH``" msgstr "" -#: ../settings/security/third-party/saml.rst:54 -msgid "Family name (``last_name``)" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Note" msgstr "" -#: ../settings/security/third-party/saml.rst:56 -msgid "" -"You may need to set up “mappers” (or “mappings”) to tell your IdP how user " -"attributes in SAML correspond to those in Zammad. For a more detailed " -"breakdown, refer to the XML metadata file referenced in the previous section." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.note}``" msgstr "" -#: ../settings/security/third-party/saml.rst:62 -msgid "Per-IdP Instructions" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``A note to the organization of the user`` or empty if not set" msgstr "" -#: ../settings/security/third-party/saml.rst:102 -msgid "Keycloak" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Shared organization" msgstr "" -#: ../settings/security/third-party/saml.rst:65 -msgid "" -"**To add Zammad as a client,** save the XML configuration to disk (``https://" -"your.zammad.domain/auth/saml/metadata``) and use **Clients > Clients list > " -"Import client** in the Keycloak admin panel." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.shared}``" msgstr "" -#: ../settings/security/third-party/saml.rst:70 -msgid "" -"To help Zammad **match its own user accounts to Keycloak users**, create a " -"user attribute (or “property”) mapper. In **Clients list**, click on your " -"newly created Client ID, choose the tab **Client scopes** and click on the " -"link which refers to your Zammad instance. Choose **Add mapper > By " -"configuration > User Property** and create a mapper with the following " -"entries:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > VIP" msgstr "" -#: ../settings/security/third-party/saml.rst:78 -msgid "**Name**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.vip}``" msgstr "" -#: ../settings/security/third-party/saml.rst:80 -msgid "**Mapper Type**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Phone" msgstr "" -#: ../settings/security/third-party/saml.rst:81 -msgid "``User Property``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.phone}``" msgstr "" -#: ../settings/security/third-party/saml.rst:82 -msgid "**Property**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated at" msgstr "" -#: ../settings/security/third-party/saml.rst:83 -msgid "``emailAddress``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_at}``" msgstr "" -#: ../settings/security/third-party/saml.rst:84 -msgid "**SAML Attribute Name**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Address" msgstr "" -#: ../settings/security/third-party/saml.rst:86 -msgid "**SAML Attribute NameFormat**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.address}``" msgstr "" -#: ../settings/security/third-party/saml.rst:87 -msgid "``basic``" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Avatar" msgstr "" -#: ../settings/security/third-party/saml.rst:89 -msgid "" -"In the example above, we're telling Zammad that whenever it receives a SAML " -"login request, it should take the ``email`` property from Keycloak, look for " -"a Zammad user with the same ``email`` attribute, and create a new session " -"for that user." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/saml.rst:95 -msgid "" -"If your Keycloak users' email addresses are stored on another property (*e." -"g.,* ``username``), adjust accordingly." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Department" msgstr "" -#: ../settings/security/third-party/saml.rst:98 -msgid "" -"Back in **Settings**, enter the Client ID (``https://your.zammad.domain/auth/" -"saml/metadata``) in the field **Master SAML Processing URL**." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.department}``" msgstr "" -#: ../settings/security/third-party/saml.rst:101 -msgid "You also need to enable **Sign assertions**." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Email" msgstr "" -#: ../settings/security/third-party/saml.rst:105 -msgid "Step 2: Configure Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.email}``" msgstr "" -#: ../settings/security/third-party/saml.rst:107 -msgid "" -"Enable SAML and enter your IdP's details in the Admin Panel under **Settings " -"> Security > Third Party Applications > Authentication via SAML**:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Fax" msgstr "" -#: ../settings/security/third-party/saml.rst:None -msgid "Example configuration of SAML part 1" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.fax}``" msgstr "" -#: ../settings/security/third-party/saml.rst:119 -msgid "Display name" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Firstname" msgstr "" -#: ../settings/security/third-party/saml.rst:116 -msgid "" -"Allows you to define a custom button name for SAML. This helps your users to " -"understand better what the button on the login page does." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.firstname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:119 -msgid "Defaults to ``SAML``." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Lastname" msgstr "" -#: ../settings/security/third-party/saml.rst:123 -msgid "IDP SSO target URL" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.lastname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:122 -msgid "" -"This is the target URL Zammad shall redirect to when the user presses the " -"SAML button. For Keycloak, this needs to look like https://your.domain/" -"realms/your-realm/protocol/saml" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Login" msgstr "" -#: ../settings/security/third-party/saml.rst:127 -msgid "IDP single logout target URL" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.login}``" msgstr "" -#: ../settings/security/third-party/saml.rst:126 -msgid "" -"This is the URL to which the single logout request and response should be " -"sent." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Mobile" msgstr "" -#: ../settings/security/third-party/saml.rst:131 -msgid "IDP certificate" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.mobile}``" msgstr "" -#: ../settings/security/third-party/saml.rst:130 -msgid "" -"The public certificate of your IDP for Zammad to verify during the callback " -"phase." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Note" msgstr "" -#: ../settings/security/third-party/saml.rst:145 -msgid "IDP certificate fingerprint" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.note}``" msgstr "" -#: ../settings/security/third-party/saml.rst:134 -msgid "" -"The fingerprint of your IDPs public certificate to verify during callback " -"phase." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Phone" msgstr "" -#: ../settings/security/third-party/saml.rst:137 -msgid "🔏 **For the IdP certificate / certificate fingerprint:**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.phone}``" msgstr "" -#: ../settings/security/third-party/saml.rst:139 -msgid "" -"Provide **only one or the other**—do not provide both! (Between the two, we " -"recommend the signing certificate itself: fingerprints use SHA-1, which `has " -"been broken for a while now `_.)" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > VIP" msgstr "" -#: ../settings/security/third-party/saml.rst:144 -msgid "" -"**Keycloak users:** Find your certificate in the Keycloak admin panel under " -"**Realm Settings > Keys > Algorithm: RS256 > Certificate**." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.vip}``" msgstr "" -#: ../settings/security/third-party/saml.rst:151 -msgid "Name identifier format" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``false`` or ``true``" msgstr "" -#: ../settings/security/third-party/saml.rst:148 -msgid "" -"This is the unique identifiers field type. Usually it should be ``urn:oasis:" -"names:tc:SAML:1.1:nameid-format:emailAddress``." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Web" msgstr "" -#: ../settings/security/third-party/saml.rst:151 -msgid "Zammad **expects an email address as unique identifier**!" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.web}``" msgstr "" -#: ../settings/security/third-party/saml.rst:155 -msgid "UID attribute name" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > VIP" msgstr "" -#: ../settings/security/third-party/saml.rst:154 -msgid "" -"Here you can define an attribute that uniquely identifies the user. If " -"unset, the name identifier returned by the IDP is used." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.vip}``" msgstr "" -#: ../settings/security/third-party/saml.rst:None -msgid "Example configuration of SAML part 2" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Web" msgstr "" -#: ../settings/security/third-party/saml.rst:163 +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.web}``" +msgstr "" + +#: ../misc/variables/ticket.rst:6 msgid "" -"Decide if the certificate for the connection to the IdP service has to be " -"verified or not (default: ``yes``)." +"Below you can find all available ticket-based variables within Zammad. These " +"can be called via triggers for example. If you're unsure if Zammad does " +"support variables at the point you're at, you can try to type ``::`` to " +"check." msgstr "" -#: ../settings/security/third-party/saml.rst:169 -msgid "Signing & Encrypting" +#: ../misc/variables/ticket.rst:12 +msgid "Ticket Variables" msgstr "" -#: ../settings/security/third-party/saml.rst:169 -msgid "" -"Define if you want to sign, encrypt, do both or nothing for the requests." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Accounted Time" msgstr "" -#: ../settings/security/third-party/saml.rst:179 -msgid "Certificate (PEM)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.time_unit}``" msgstr "" -#: ../settings/security/third-party/saml.rst:172 -msgid "" -"Paste the public certificate of your Zammad SAML client, if you want to " -"encrypt the requests." +#: ../misc/variables/ticket.rst:1 +msgid "``1``, ``2.75`` or empty response" msgstr "" -#: ../settings/security/third-party/saml.rst:175 -msgid "Make sure the certificate is:" +#: ../misc/variables/ticket.rst:1 +msgid "``3``, any number of articles existing in the ticket right now" msgstr "" -#: ../settings/security/third-party/saml.rst:177 -msgid "already valid and not yet expired" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Closing time" msgstr "" -#: ../settings/security/third-party/saml.rst:178 -msgid "no CA certificate" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.close_at}``" msgstr "" -#: ../settings/security/third-party/saml.rst:179 -msgid "valid for signing and encrypting" +#: ../misc/variables/ticket.rst:1 +msgid "2019-10-07 17:25:00 UTC" msgstr "" -#: ../settings/security/third-party/saml.rst:185 -msgid "Private key (PEM)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created at" msgstr "" -#: ../settings/security/third-party/saml.rst:182 -msgid "" -"Paste the private key of your Zammad SAML client here, if you want to sign " -"the requests." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_at}``" msgstr "" -#: ../settings/security/third-party/saml.rst:185 -msgid "Make sure the key is an RSA key with a length of at least 2048 bits." +#: ../misc/variables/ticket.rst:1 +msgid "2019-10-07 16:25:00 UTC" msgstr "" -#: ../settings/security/third-party/saml.rst:188 -msgid "Private key secret" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Address" msgstr "" -#: ../settings/security/third-party/saml.rst:188 -msgid "If your private key is secured with a secret, you can provide it here." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.address}``" msgstr "" -#: ../settings/security/third-party/saml.rst:192 -msgid "Your callback URL" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Avatar" msgstr "" -#: ../settings/security/third-party/saml.rst:191 -msgid "" -"This URL is needed for your IdP configuration so it knows where to redirect " -"to after successful authentication." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/saml.rst:194 -msgid "" -"After saving your input by clicking on the \"Submit\" button, Zammad " -"verifies the provided keys/certificates (e.g. if they are valid for signing/" -"encrypting and if they aren't expired)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Department" msgstr "" -#: ../settings/security/third-party/saml.rst:199 -msgid "" -"See :ref:`automatic account linking ` for details " -"on how to link existing Zammad accounts to IdP accounts." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.department}``" msgstr "" -#: ../settings/security/third-party/saml.rst:205 -msgid "Automatic account linking doesn't work" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Email" msgstr "" -#: ../settings/security/third-party/saml.rst:206 -msgid "" -"Have you double-checked your IdP's user attribute mapping configuration?" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.email}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via Twitter. To do " -"so, you need to follow these steps:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Fax" msgstr "" -#: ../settings/security/third-party/twitter.rst:8 -msgid "Register Twitter App" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.fax}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:10 -msgid "Go to https://dev.twitter.com/apps and login with your account." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Firstname" msgstr "" -#: ../settings/security/third-party/twitter.rst:15 -msgid "Click on \"Create App\"" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.firstname}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "new app page" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Lastname" msgstr "" -#: ../settings/security/third-party/twitter.rst:20 -msgid "" -"Enter app settings. As \"Callback URL\" you need to enter ``https://" -"zammad_host/api/v1/external_credentials/twitter/callback``. You need to " -"replace ``zammad_host`` with the domain of your Zammad system." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.lastname}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:24 -msgid "" -"After the app has been created, update the application icon and organization " -"attributes." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Login" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "set permissions to receive and send direct messages" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.login}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:30 -msgid "" -"Next we need to set ``read, write and access direct messages`` permissions " -"for the app." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Mobile" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "click on Keys & Access Token, note them" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.mobile}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:36 -msgid "" -"Go to \"Keys and Access Token\" tab and note the \"Consumer Key\" and " -"\"Consumer Secret\"." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Note" msgstr "" -#: ../settings/security/third-party/twitter.rst:40 -msgid "Configure Zammad as Twitter App" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.note}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:42 -msgid "" -"Go to \"Admin > Security > Twitter > Third Party Applications > Twitter\" " -"Section." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Phone" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "Admin > Security > Third Party Applications" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.phone}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:48 -msgid "" -"Fill in the \"Twitter Key\" and the \"Twitter Secret\" and click the " -"\"Submit\" button." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > VIP" msgstr "" -#: ../settings/security/third-party/twitter.rst:51 -msgid "" -"Now you can link accounts via \"Avatar > Profile > Link Accounts\" or login " -"via Zammad login page." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.vip}``" msgstr "" -#: ../settings/security/two-factor.rst:11 -msgid "Two-factor Authentication Methods" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Web" msgstr "" -#: ../settings/security/two-factor.rst:2 -msgid "Two-Factor Authentication" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.web}``" msgstr "" -#: ../settings/security/two-factor.rst:4 -msgid "" -"Two-factor authentication (2FA) enhances the security of Zammad accounts by " -"adding an extra layer of verification beyond a password. It requires users " -"to provide two different types of authentication factors, typically " -"something they know (like a password) and something they possess (like a " -"mobile device or a security token), to ensure that only authorized " -"individuals can access the account." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Address" msgstr "" -#: ../settings/security/two-factor.rst:19 -msgid "Enable Recovery Codes" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.address}``" msgstr "" -#: ../settings/security/two-factor.rst:21 -msgid "" -"Recovery codes are one-time use security codes that can be used by the user " -"if they lose access to their other two-factor authentication methods. They " -"cannot be used on their own, they can only be activated if at least one two-" -"factor authentication method is enabled." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Avatar" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Enable Recovery Codes Setting" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.avatar(60,60)}``" msgstr "" -#: ../settings/security/two-factor.rst:30 -msgid "" -"Recovery codes can only be used as a backup method. If enabled, they will be " -"automatically generated for the user once they set up their initial two-" -"factor authentication method." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Department" msgstr "" -#: ../settings/security/two-factor.rst:34 -msgid "" -"The user will be asked to print out or save the generated recovery codes in " -"a safe place. Once used, a recovery code cannot be reused." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.department}``" msgstr "" -#: ../settings/security/two-factor.rst:37 -msgid "" -"Users will also have an option to regenerate their recovery codes at any " -"time, which invalidates already existing recovery codes and provides them " -"with a list of fresh codes." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Email" msgstr "" -#: ../settings/security/two-factor.rst:41 -msgid "" -"After you enable this setting, when the user completes a setup of their " -"initial two-factor authentication method, they will be presented with a list " -"of recovery codes and instructed to save them for later use." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.email}``" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Recovery Codes Generation Modal Dialog" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Fax" msgstr "" -#: ../settings/security/two-factor.rst:50 -msgid "Enforce the Set Up of the Two-Factor Authentication" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.fax}``" msgstr "" -#: ../settings/security/two-factor.rst:52 -msgid "" -"In case you wish to require your users to set up at least one two-factor " -"authentication method for their account, you can do this by selecting " -"specific user roles the requirement applies to in **Enforced for user " -"roles** setting. Of course you must have at least one two-factor " -"authentication method enabled for this setting to take effect." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Firstname" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Enforced for User Roles Setting" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.firstname}``" msgstr "" -#: ../settings/security/two-factor.rst:62 -msgid "" -"After you change this setting, if the user has one of the selected roles on " -"their account, they will be forced to set up the two-factor authentication " -"upon next sign in or application reload." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Lastname" msgstr "" -#: ../settings/security/two-factor.rst:66 -msgid "" -"A modal dialog with instructions will be shown, and they will not be able to " -"do any work before they set up at least one two-factor method." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.lastname}``" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Modal Dialog for Enforcing Two-Factor Authentication Set Up" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Login" msgstr "" -#: ../settings/security/two-factor.rst:74 -msgid "Reset Two-Factor Authentication for a Specific User" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.login}``" msgstr "" -#: ../settings/security/two-factor.rst:76 -msgid "" -"In case an user isn't able to login anymore because of an inaccessible " -"second factor, you can reset the user's 2FA method." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Mobile" msgstr "" -#: ../settings/security/two-factor.rst:79 -msgid "" -"To do this, go to the user management and search for the relevant user. " -"After you found the account, click the button in the action column and " -"select \"Manage Two-Factor Authentication\":" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.mobile}``" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Context menu in action column in user management" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Note" msgstr "" -#: ../settings/security/two-factor.rst:87 -msgid "" -"After selecting this, you can see a dialog where you can either reset one " -"2FA method or reset all of the user's 2FA methods:" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.note}``" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Dialog for resetting user's 2FA method" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Phone" msgstr "" -#: ../settings/security/two-factor.rst:94 -msgid "" -"Choose the fitting one, click on the corresponding \"Remove ...\" button and " -"confirm your action. The user now has to setup a new 2FA method, depending " -"on your 2FA configuration." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.phone}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:2 -msgid "Authenticator App" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > VIP" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:4 -msgid "" -"The authenticator app method is a type of two-factor authentication that " -"uses a mobile application to generate one-time codes for account " -"verification. After setting up the authenticator app on their device, the " -"user links it to their Zammad account." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.vip}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:12 -msgid "" -"When logging in, the user is prompted to enter a time-sensitive code " -"generated by the app, in addition to their password. This code acts as the " -"second factor of authentication, providing an extra layer of security as it " -"changes periodically and is unique to the user's device." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Web" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:None -msgid "Security Code in Google Authenticator App" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.web}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:22 -msgid "" -"The app generates codes based on a shared secret key stored securely on both " -"the user's device and the server, ensuring a synchronized and secure " -"authentication process. The method of generating the codes is sometimes also " -"called TOTP (time-based one-time password)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Escalation at" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:28 -msgid "Enabling the Authenticator App Method" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.escalation_at}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:30 -#: ../settings/security/two-factor/security-keys.rst:28 -msgid "To enable the method, just toggle the switch on in the settings." +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:None -msgid "Authenticator App Switch in Settings" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > First response" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:36 -msgid "" -"Now the users will be able to set up this two-factor authentication method " -"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " -"Once they do, on next sign-in with password, they will be asked to provide " -"an additional security code generated by their mobile device." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.first_response_at}``" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:2 -msgid "Security Keys" +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable yet" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:4 -msgid "" -"The security keys method is a type of a two-factor authentication that uses " -"Web Authentication API in the browser for verifying user's identity. The " -"user can register multiple hardware or software security keys with their " -"Zammad account and then they can use it during the sign-in process." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Assign Follow-Ups" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:12 -msgid "" -"When logging in, the user is prompted to provide the same security key they " -"registered with their account, in addition to their password. This key acts " -"as the second factor of authentication, providing an extra layer of security." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_assignment}``" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:None -msgid "Security Key dialog in Safari on macOS" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Assignment Timeout" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:21 -msgid "" -"The type of the key can range from hardware USB sticks to passkeys stored in " -"a device of user's choice. Which type can be used depends on the browser " -"flavor and the platform of the user." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.assignment_timeout}``" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:26 -msgid "Enabling the Security Keys Method" +#: ../misc/variables/ticket.rst:1 +msgid "``20`` or empty if not configured" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:None -msgid "Security Keys Switch in Settings" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Follow-up possible" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:34 -msgid "" -"Now the users will be able to set up this two-factor authentication method " -"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " -"Once they do, on next sign-in with password, they will be asked to provide " -"the same security key they registered during the setup." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_possible}``" msgstr "" -#: ../settings/system/system-selfhosted.include.rst:3 -msgid "" -"Below settings are only available to self hosted users. In hosted " -"environments we're handling these settings for you to ensure service " -"stability." +#: ../misc/variables/ticket.rst:1 +msgid "``no`` or ``yes``" msgstr "" -#: ../settings/system/base.rst:11 -msgid "Fully Qualified Domain Name" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Name" msgstr "" -#: ../settings/system/base.rst:7 -msgid "The URL of your Zammad installation." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.name}``" msgstr "" -#: ../settings/system/base.rst:9 ../settings/system/base.rst:17 -msgid "This setting is used within :doc:`/system/variables` and notifications." +#: ../misc/variables/ticket.rst:1 +msgid "``Sales``" msgstr "" -#: ../settings/system/system-base.include.rst:1 -msgid "It is automatically set by the *Getting Started wizard*." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Note" msgstr "" -#: ../settings/system/system-base.include.rst:5 -msgid "Changing this setting also changes callback URLs for your channels etc." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.note}``" msgstr "" -#: ../settings/system/system-base.include.rst:6 -msgid "This setting can have negative affects on being able to login." +#: ../misc/variables/ticket.rst:1 +msgid "``Note about this group``" msgstr "" -#: ../settings/system/base.rst:19 -msgid "HTTP type" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > ID" msgstr "" -#: ../settings/system/base.rst:14 -msgid "" -"The HTTP type tells your installation how your clients connect. This is " -"relevant for authentication and cookie security." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.id}``" msgstr "" -#: ../settings/system/base.rst:31 -msgid "SystemID" +#: ../misc/variables/ticket.rst:1 +msgid "``17``, ``5281``, ..." msgstr "" -#: ../settings/system/base.rst:22 -msgid "" -"This ID is being used within your ticket number. In case you're " -"communicating with another ticket system with similar ticket number schemes " -"this ID greatly reduces the risk of false follow ups." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact (agent)" msgstr "" -#: ../settings/system/base.rst:26 -msgid "" -"The SystemID is randomly selected upon installation of Zammad (``1-99``)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_agent_at}``" msgstr "" -#: ../settings/system/base.rst:30 -msgid "" -"**Do not** change this setting in a productive system! Your Zammad " -"installation may no longer recognize old ticket number based follow ups upon " -"change!" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact (customer)" msgstr "" -#: ../settings/system/frontend.rst:2 -msgid "Frontend" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_customer_at}``" msgstr "" -#: ../settings/system/frontend.rst:22 -msgid "Core Workflow Ajax Mode" +#: ../misc/variables/ticket.rst:1 +msgid "" +"``2019-10-07 16:25:00 UTC`` or empty if not applicable yet (Please note " +"`Ticket last contact behavior Settings `_ for this)" msgstr "" -#: ../settings/system/frontend.rst:6 -msgid "" -"This setting allows administrators to enforce :doc:`/system/core-workflows` " -"to use Ajax-Calls instead of web sockets. You'll usually only need this if " -"you experience serious issues as noted below." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact" msgstr "" -#: ../settings/system/frontend.rst:10 -msgid "**🤓 Possible (technical) reasons**" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_at}``" msgstr "" -#: ../settings/system/frontend.rst:12 -msgid "" -"In some cases, your network structure (e.g. firewalls, proxies) may " -"disconnect long web socket connections. This leads to select fields staying " -"empty (e.g. owner selection *after* selecting your group) or fields not " -"shown / hidden (e.g. when switching to or from pending states, the \"pending " -"till\" field not showing / hiding)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Number" msgstr "" -#: ../settings/system/frontend.rst:18 -msgid "" -"Please keep in mind that the Ajax fallback may cause serious pressure on " -"your application server. If you have the choice stick to web sockets." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.number}``" msgstr "" -#: ../settings/system/frontend.rst:22 -msgid "Default: ``no`` (inactive)" +#: ../misc/variables/ticket.rst:1 +msgid "``31001``, ``201910731001``, ..." msgstr "" -#: ../settings/system/frontend.rst:53 -msgid "Show calendar weeks in the picker of date/datetime fields" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain based assignment" msgstr "" -#: ../settings/system/frontend.rst:25 -msgid "" -"With this setting you can instruct Zammad to provide week number display " -"globally for all users. Calendar with week number display are usually used " -"in business sectors and may not be relevant for everyone." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain_assignment}``" msgstr "" -#: ../settings/system/frontend.rst:29 -msgid "" -"This setting affects *all areas* - you'll also see week numbers in the admin " -"panel for e.g. triggers and macros." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain" msgstr "" -#: ../settings/system/frontend.rst:32 -msgid "Default: ``no`` (not shown)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain}``" msgstr "" -#: ../settings/system/frontend.rst:53 -msgid "Here's the difference:" +#: ../misc/variables/ticket.rst:1 +msgid "``domain.tld`` or empty if not set" msgstr "" -#: ../settings/system/frontend.rst:0 -msgid "Screenshot showing Zammad's date picker (in the default way)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Name" msgstr "" -#: ../settings/system/frontend.rst:41 -msgid "Set to ``no``" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.name}``" msgstr "" -#: ../settings/system/frontend.rst:0 -msgid "" -"Screenshot showing Zammad's date picker with\n" -"week numbers enabled" +#: ../misc/variables/ticket.rst:1 +msgid "``Zammad GmbH`` or empty if not set" msgstr "" -#: ../settings/system/frontend.rst:50 -msgid "Set to ``yes``" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Note" msgstr "" -#: ../settings/system/index.rst:4 -msgid "" -"For your overview we split each tab within system settings into its own page:" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.note}``" msgstr "" -#: ../settings/system/index.rst:16 -msgid "Console Based Settings" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Shared organization" msgstr "" -#: ../settings/system/index.rst:18 -msgid "" -"There's some console based settings we didn't put into the UI. However, you " -"may find them helpful - you can find them in our :docs:`hidden settings ` section." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.shared}``" msgstr "" -#: ../settings/system/network.rst:2 -msgid "Network" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > VIP" msgstr "" -#: ../settings/system/network.rst:8 -msgid "" -"The proxy settings can only be saved after successfully testing the proxy " -"connection." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.vip}``" msgstr "" -#: ../settings/system/network.rst:15 -msgid "Proxy Address." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Address" msgstr "" -#: ../settings/system/network.rst:12 -msgid "" -"Allows you to provide a proxy server if needed. This is relevant for network " -"communication by Zammad." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.address}``" msgstr "" -#: ../settings/system/network.rst:15 -msgid "It **does not** affect the update process or Elasticsearch." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Avatar" msgstr "" -#: ../settings/system/network.rst:18 -msgid "Username for proxy connection." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.avatar(60,60)}``" msgstr "" -#: ../settings/system/network.rst:18 -msgid "" -"If your proxy server requires authentication, provide the username here." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Department" msgstr "" -#: ../settings/system/network.rst:21 -msgid "Password for proxy connection." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.department}``" msgstr "" -#: ../settings/system/network.rst:21 -msgid "" -"If your proxy server requires authentication, provide the password here." +#: ../misc/variables/ticket.rst:1 +msgid "``Support`` or empty if not set" msgstr "" -#: ../settings/system/network.rst:26 -msgid "No proxy for the following hosts." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Email" msgstr "" -#: ../settings/system/network.rst:24 -msgid "" -"Exception list for hosts you can't or don't want to reach via proxy server." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.email}``" msgstr "" -#: ../settings/system/network.rst:27 -msgid "Default: ``localhost,127.0.0.0,::1``" +#: ../misc/variables/ticket.rst:1 +msgid "``agent@company.tld`` or empty if not set" msgstr "" -#: ../settings/system/services.rst:2 -msgid "Services" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Fax" msgstr "" -#: ../settings/system/services.rst:10 -msgid "Image Service" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.fax}``" msgstr "" -#: ../settings/system/services.rst:5 -msgid "Defines the backend for user and organization image lookups." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Firstname" msgstr "" -#: ../settings/system/services.rst:7 -msgid "Default: ``Zammad Image Service`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.firstname}``" msgstr "" -#: ../settings/system/services.rst:9 -msgid "" -"Make sure your on premise installation has ``HTTPS`` access to ``images." -"zammad.com``." +#: ../misc/variables/ticket.rst:1 +msgid "``Max`` or empty if not set" msgstr "" -#: ../settings/system/services.rst:18 -msgid "Geo Calendar Service" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Lastname" msgstr "" -#: ../settings/system/services.rst:13 -msgid "" -"Defines the backend for geo calendar lookups. Used for initial calendar " -"setup." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.lastname}``" msgstr "" -#: ../settings/system/services.rst:16 -msgid "Default: ``Zammad GeoCalendar Service`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "``Mustermann`` or empty if not set" msgstr "" -#: ../settings/system/services.include.rst:2 -msgid "" -"Make sure your on premise installation has ``HTTPS`` access to ``geo.zammad." -"com``." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Login" msgstr "" -#: ../settings/system/services.rst:26 -msgid "Geo IP Service" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.login}``" msgstr "" -#: ../settings/system/services.rst:21 -msgid "" -"Defines the backend for geo IP lookups. Shows also location of an IP address " -"if an IP address is shown." +#: ../misc/variables/ticket.rst:1 +msgid "``agent``" msgstr "" -#: ../settings/system/services.rst:24 -msgid "Default: ``Zammad GeoIP Service`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Mobile" msgstr "" -#: ../settings/system/services.rst:32 -msgid "Geo Location Service" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.mobile}``" msgstr "" -#: ../settings/system/services.rst:29 -msgid "" -"Defines the backend for geo location lookups to store geo locations for " -"addresses." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Note" msgstr "" -#: ../settings/system/services.rst:32 -msgid "" -"Default: ``OpenStreetMap (ODbL 1.0, http://osm.org/copyright)`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.note}``" msgstr "" -#: ../settings/system/services.rst:36 -msgid "" -"You can find a detailed privacy information on what we store for how long on " -"our :docs:`Privacy Appendix ` inside of our System " -"Documentation." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Phone" msgstr "" -#: ../settings/system/storage.rst:2 -msgid "Storage" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.phone}``" msgstr "" -#: ../settings/system/storage.rst:6 -msgid "" -"Here you can define where Zammad stores attachments for tickets and the " -"knowledge base. By default, we're writing to the ``Database`` - you can " -"switch to ``Filesystem`` or ``Simple Storage (S3)`` at any time. In this " -"case please have a look on the following instructions." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > VIP" msgstr "" -#: ../settings/system/storage.rst:11 -msgid "" -"If you have a busy Zammad instance, we strongly encourage you to use " -"filesystem storage instead of \"Database\". This will greatly improve system " -"performance (de-crease database load and size)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.vip}``" msgstr "" -#: ../settings/system/storage.rst:19 -msgid "Database" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Web" msgstr "" -#: ../settings/system/storage.rst:17 -msgid "" -"This is the default storage method. The attachments are stored directly in " -"the database. If your Zammad instance grows, we recommend one of the other " -"methods to maintain performance." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.web}``" msgstr "" -#: ../settings/system/storage.rst:38 -msgid "Filesystem" +#: ../misc/variables/ticket.rst:1 +msgid "``https://zammad.com`` or empty if not set" msgstr "" -#: ../settings/system/storage.rst:22 -msgid "" -"This storage method is recommended for all Zammad instances, especially for " -"those with a higher load. If you choose filesystem, your files are written " -"to ``/opt/zammad/storage/``." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Pending till" msgstr "" -#: ../settings/system/storage.rst:26 -msgid "" -"Moving attachments from \"Database\" to \"Filesystem\" can be run during " -"production use. However, you should consider your framework conditions (e.g. " -"bandwidth, system load in production) to define the right moment." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.pending_time}``" msgstr "" -#: ../settings/system/storage.rst:32 -msgid "**You noticed slow updates of Zammad?**" +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not set" msgstr "" -#: ../settings/system/storage.rst:34 -msgid "" -"While Zammad is beeing updated, it enforces a recursive \"change " -"owner\" (chown) for this directory. For instances with many files this can " -"be time consuming. To mitigate that you can move your files and create a " -"symlink in ``/opt/zammad/storage/`` to the new directory. Of course you have " -"to make sure on your own that the permissions are always correct." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Priority > Name" msgstr "" -#: ../settings/system/storage.rst:95 -msgid "Simple Storage (S3)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.priority.name}``" msgstr "" -#: ../settings/system/storage.rst:41 -msgid "" -"To use the Simple Storage (S3), you have to provide some settings, which " -"can't be accessed in the UI (see instructions below)." +#: ../misc/variables/ticket.rst:1 +msgid "``2 normal``" msgstr "" -#: ../settings/system/storage.rst:44 -msgid "" -"⚠️ Please note that the current implementation is in its early stages and can " -"be modified in the future." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > State > Name" msgstr "" -#: ../settings/system/storage.rst:47 -msgid "" -"The prerequisite is to have access to a S3-compatible storage and to have " -"all necessary parameters available (which depends on your storage provider; " -"if in doubt, please ask there for help)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.state.name}``" msgstr "" -#: ../settings/system/storage.rst:51 -msgid "Steps to configure S3:" +#: ../misc/variables/ticket.rst:1 +msgid "``new``, ``open``, ..." msgstr "" -#: ../settings/system/storage.rst:53 -msgid "" -"Copy ``config/zammad/storage.yml.dist`` to ``config/zammad/storage.yml``" -msgstr "" - -#: ../settings/system/storage.rst:54 -msgid "Edit the copied file in one of the following ways:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Tags" msgstr "" -#: ../settings/system/storage.rst:56 -msgid "" -"Either provide your S3 configuration with one attribute per line like in the " -"upper area of the file" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.tags}``" msgstr "" -#: ../settings/system/storage.rst:58 +#: ../misc/variables/ticket.rst:1 msgid "" -"Or provide your S3 configuration as an URL (which you can find at the end of " -"the file). Note: you can also provide this URL as environment variable (:" -"docs:`see system documentation `) without using this yml-file." +"Currently not available, see `Issue 2769 `_" msgstr "" -#: ../settings/system/storage.rst:62 -msgid "" -"We recommend the deletion of the not used configuration style to avoid " -"inconsistencies." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Title" msgstr "" -#: ../settings/system/storage.rst:65 -msgid "Restart Zammad so the config file / environment variable is loaded" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.title}``" msgstr "" -#: ../settings/system/storage.rst:66 +#: ../misc/variables/ticket.rst:1 msgid "" -"Set the \"Storage Method\" in Zammad to ``Simple Storage (S3)`` in Settings " -"> System > Storage and click on \"Submit\". After that, Zammad checks your " -"configuration and the connection to the service and will raise an error " -"message if something is wrong." +"``My amazing Subject`` (normally subject, can be edited within Interface and " +"thus differ)" msgstr "" -#: ../settings/system/storage.rst:72 -msgid "A very simple storage configuration could look like this:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated at" msgstr "" -#: ../settings/system/storage.rst:85 -msgid "" -"Before setting the storage method to ``Simple Storage (S3)`` (step 4), " -"please make sure to have a working setup." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_at}``" msgstr "" -#: ../settings/system/storage.rst:88 -msgid "" -"You can verify this by running ``rails r 'Rails.logger = Logger.new(STDOUT); " -"pp Store::Provider::S3.ping?'`` in your Zammad directory. If everything is " -"fine, you should see ``true``, else you should see ``false`` and a simple " -"error message." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Address" msgstr "" -#: ../settings/system/storage.rst:93 -msgid "" -"If you installed Zammad through a package manager (rather than from source), " -"replace ``rails r`` with ``zammad run rails r`` above. To learn more, see :" -"docs:`Administration via Console `." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.address}``" msgstr "" -#: ../settings/ticket.rst:4 -msgid "" -"Here you can adjust general ticket settings. Additional ones for the ticket " -"composer interface can be found in the :doc:`/misc/composer`." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Avatar" msgstr "" -#: ../settings/ticket.rst:11 -msgid "Ticket Hook (default: ``Ticket#``)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.avatar(60,60)}``" msgstr "" -#: ../settings/ticket.rst:11 -msgid "The identifier for a ticket; *e.g.,* Ticket#, Call#, MyTicket#." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Department" msgstr "" -#: ../settings/ticket.rst:38 -msgid "Ticket Hook Position (default: ``right``)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.department}``" msgstr "" -#: ../settings/ticket.rst:14 -msgid "" -"With this setting you can decide (if) where to insert the ticket number." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Email" msgstr "" -#: ../settings/ticket.rst:20 -msgid "*Right*" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.email}``" msgstr "" -#: ../settings/ticket.rst:17 -msgid "" -"This setting will add the ticket reference on the right site of the subject." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Fax" msgstr "" -#: ../settings/ticket.rst:20 -msgid "Example: ``Some Subject [Ticket#12345]``" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.fax}``" msgstr "" -#: ../settings/ticket.rst:26 -msgid "*Left*" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Firstname" msgstr "" -#: ../settings/ticket.rst:23 -msgid "" -"This setting will add the ticket reference on the left site of the subject." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.firstname}``" msgstr "" -#: ../settings/ticket.rst:26 -msgid "Example: ``[Ticket#12345] Some Subject``" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Lastname" msgstr "" -#: ../settings/ticket.rst:29 -msgid "*None*" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.lastname}``" msgstr "" -#: ../settings/ticket.rst:29 -msgid "This will completely remove ticket references from the subject." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Login" msgstr "" -#: ../settings/ticket.rst:33 -msgid "" -"Please ensure to take a look at :doc:`/channels/email/settings` within the " -"email channel to ensure you have at least one reference that helps Zammad to " -"assign follow-ups correctly." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.login}``" msgstr "" -#: ../settings/ticket.rst:37 -msgid "" -"Disabling this and not setting up any further follow up search will lead to " -"unexpected results!" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Mobile" msgstr "" -#: ../settings/ticket.rst:65 -msgid "" -"Ticket Last Contact Behaviour (default: ``Use the start time of the last " -"customer thread (which may consist of multiple articles).``)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.mobile}``" msgstr "" -#: ../settings/ticket.rst:41 -msgid "" -"This setting changes the way Zammad updates the ``Last Contact`` value of a " -"ticket. This is fairly important for overviews and what you expect upon " -"ticket updates of a customer." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Note" msgstr "" -#: ../settings/ticket.rst:52 -msgid "" -"Use the start time of the last customer thread (which may consist of " -"multiple articles)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.note}``" msgstr "" -#: ../settings/ticket.rst:46 -msgid "" -"If this option is chosen, Zammad will update the last updated value just " -"once if a customer replies. After that, Zammad will wait for an agent to " -"react." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Phone" msgstr "" -#: ../settings/ticket.rst:50 -msgid "" -"This comes in handy if you want to work tickets in the order of their first " -"update. This will not change ticket orders if customers decide to \"bump\" " -"the ticket affected." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.phone}``" msgstr "" -#: ../settings/ticket.rst:57 -msgid "Use the time of the very last customer article." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > VIP" msgstr "" -#: ../settings/ticket.rst:55 -msgid "" -"When setting this option, Zammad will always update the last updated value. " -"This means that if ordering by ``Last Update``, ticket orders will change if " -"customers \"bump\" the ticket." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.vip}``" msgstr "" -#: ../settings/ticket.rst:64 -msgid "Last contact value used on :doc:`/manage/overviews`" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Web" msgstr "" -#: ../settings/ticket.rst:65 -msgid "Last contact value used on :doc:`/manage/trigger`" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.web}``" msgstr "" -#: ../settings/ticket.rst:88 -msgid "" -"Ticket Organization Reassignment (default: ``Update the most recent tickets." -"``)" +#: ../settings/branding.rst:10 +msgid "Product Name" msgstr "" -#: ../settings/ticket.rst:68 +#: ../settings/branding.rst:7 msgid "" -"This setting changes the way Zammad updates the organization field of the " -"tickets whenever the primary organization of a user is changed." -msgstr "" - -#: ../settings/ticket.rst:74 -msgid "Update the most recent tickets." +"Defines the name of the application, shown in the web interface, tabs and " +"title bar of the web browser." msgstr "" -#: ../settings/ticket.rst:72 -msgid "" -"If this option is chosen, Zammad will update the 100 most recent tickets " -"where the user is the ticket customer. The ticket organization field will be " -"automatically set to the new primary organization of the user." +#: ../settings/branding.rst:10 +msgid "Default value: ``Zammad Helpdesk``" msgstr "" -#: ../settings/ticket.rst:88 -msgid "Do not update any tickets." +#: ../settings/branding.rst:13 +msgid "Will be shown in the app and is included in email footers." msgstr "" -#: ../settings/ticket.rst:77 -msgid "" -"When choosing this option, Zammad will not update any tickets when the " -"user's primary organization is changed." +#: ../settings/branding.rst:19 +msgid "Logo" msgstr "" -#: ../settings/ticket.rst:80 -msgid "**Use with care!**" +#: ../settings/branding.rst:16 +msgid "Defines the logo of the application, shown in the login page of Zammad." msgstr "" -#: ../settings/ticket.rst:82 +#: ../settings/branding.rst:18 msgid "" -"Using this option may lead to inconsistencies in the system as the ticket " -"organization may become decoupled from the ticket customer." +"Ensure to hit the \"Submit\" button after uploading the logo. Otherwise your " +"change will not be saved." msgstr "" -#: ../settings/ticket.rst:85 +#: ../settings/branding.rst:22 msgid "" -"However, you may use this option if you wish to maintain :ref:`the shared " -"access ` to the ticket for all organization " -"members of the original organization of the customer." +"Allows to set the default language of the Zammad instance. The here defined " +"locale mostly acts as a fallback for:" msgstr "" -#: ../settings/ticket.rst:110 -msgid "Ticket Number Format (default: ``Increment (SystemID.Counter)``)" +#: ../settings/branding.rst:25 +msgid "user preferences (if Zammad can't detect the users locale)" msgstr "" -#: ../settings/ticket.rst:94 -msgid "" -"This setting defines the way Zammad's ticket number will look. Changing this " -"setting in production will cause follow up detection to fail." +#: ../settings/branding.rst:26 +msgid "CSV output (reporting, time accounting)" msgstr "" -#: ../settings/ticket.rst:102 -msgid "Increment (SystemID.Counter)" +#: ../settings/branding.rst:30 +msgid "Define the timezone of your Zammad installation." msgstr "" -#: ../settings/ticket.rst:98 +#: ../settings/branding.rst:32 msgid "" -"The increment value contains the SystemID (automatically generated during " -"installation) and a increment which counts up with every new Ticket. The " -"increment will automatically get another digit if needed." +"This does not have any effect on timings for your agents or how Zammad " +"stores date and time values." msgstr "" -#: ../settings/ticket.rst:102 -msgid "Examples: ``1010138``, ``1010139``" +#: ../settings/branding.rst:35 +msgid "Changing this value has direct consequences on the following areas:" msgstr "" -#: ../settings/ticket.rst:110 -msgid "Date (Year.Month.Day.SystemID.Counter)" +#: ../settings/branding.rst:37 +msgid ":doc:`/manage/scheduler` tasks" msgstr "" -#: ../settings/ticket.rst:105 -msgid "" -"This version of the ticket number is fairly long. However, because it " -"contains the date of ticket creation, it also allows you to see when the " -"ticket has been created. You may feel familiar with this number format if " -"you've worked with OTRS already." +#: ../settings/branding.rst:38 +msgid "search indexing (and thus reporting)" msgstr "" -#: ../settings/ticket.rst:110 -msgid "Examples: ``201206231010138``, ``201206231010139``" +#: ../settings/branding.rst:40 +msgid "calendar subscriptions" msgstr "" -#: ../settings/ticket.rst:137 -msgid "OPTIONS" +#: ../settings/branding.rst:41 +msgid "browser printing" msgstr "" -#: ../settings/ticket.rst:113 +#: ../settings/branding.rst:43 msgid "" -"The below options allow you to further customize your ticket number. The " -"availability of options differ depending of the chosen ticket number format " -"above." +"Please note that some of above are fallbacks in case Zammad could not detect " +"the agents timezone correctly." msgstr "" -#: ../settings/ticket.rst:122 -msgid "Checksum (default: ``no``)" +#: ../settings/branding.rst:77 +msgid "Pretty Date" msgstr "" -#: ../settings/ticket.rst:118 +#: ../settings/branding.rst:47 msgid "" -"If set to yes, we'll built a checksum to further \"unique\" the ticket " -"number of your system. If you're dealing with many other ticket systems this " -"might help to prevent false positive follow up detection on tickets." +"This setting allows you to define how Zammad should display time stamps " +"within the interface to all users." msgstr "" -#: ../settings/ticket.rst:122 -msgid "This will also add another digit to the ticket number." +#: ../settings/branding.rst:50 +msgid "" +"This does not have any effect on how Zammad returns e.g. time values via " +"variables." msgstr "" -#: ../settings/ticket.rst:137 -msgid "Min. size of Number (default: ``5``)" +#: ../settings/branding.rst:77 +msgid "Choose in between the following options:" msgstr "" -#: ../settings/ticket.rst:125 -msgid "" -"This setting defines the minimum length of your ticket number. If your " -"counter is not yet high enough, Zammad will fill the number with zeros to " -"ensure the wanted length." +#: ../settings/branding.rst:64 +msgid "relative" msgstr "" -#: ../settings/ticket.rst:129 +#: ../settings/branding.rst:55 msgid "" -"Please note that the minimum length is ``3`` (SystemID + at least one digit " -"if below 10). Also, if the length is no longer long enough, the number will " -"automatically get one digit longer. Ticket-Numbers **do not overflow**, thus " -"it's save to keep it at 5 or set it lower if wanted." +"This timestamp shows a relative time span until it switches to a date. Over " +"time, it will change as follows:" msgstr "" -#: ../settings/ticket.rst:135 -msgid "" -"This option is only available if ticket number format is set to " -"``Increment``!" +#: ../settings/branding.rst:58 +msgid "just now" msgstr "" -#: ../settings/ticket.rst:142 -msgid "Auto-Assignment" +#: ../settings/branding.rst:59 +msgid "5 minutes ago" msgstr "" -#: ../settings/ticket.rst:144 -msgid "" -"In a larger Zammad environment, it happens that several agents open the same " -"ticket at the same time. Although collision detection is then effective, the " -"efficiency of processing can be increased by means of the automatic " -"assignment of tickets when a ticket is opened." +#: ../settings/branding.rst:60 +msgid "3 days 1 hour ago" msgstr "" -#: ../settings/ticket.rst:149 -msgid "" -"The automatic assignment of tickets can be activated and configured in the " -"admin area under Settings > Ticket > Auto Assignment." +#: ../settings/branding.rst:61 +msgid "``03/04/2022``" msgstr "" -#: ../settings/ticket.rst:152 -msgid "" -"The auto assignment only works if the ticket has no owner yet. By default, " -"the agent can always reset the ticket owner to ``-`` if needed." +#: ../settings/branding.rst:63 +msgid "Hovering the timestamp helps, you'll always get a clean timestamp then." msgstr "" -#: ../settings/ticket.rst:155 -msgid "" -"If you want to use this function for only specific tickets, you can " -"configure the conditions accordingly to meet your requirement. By default " -"the condition affects all tickets with the state ``open``." +#: ../settings/branding.rst:71 +msgid "absolute" msgstr "" -#: ../settings/ticket.rst:161 +#: ../settings/branding.rst:67 msgid "" -"If you need to exclude users (e.g. a group leader), you can search and " -"select the desired agents in the ``Exception Users`` list. The search " -"function in this area is only effective, if you have too many agents to " -"display at once to help you with the configuration." +"This timestamp always includes the week day. For one week after creation, " +"the timestamp will not contain the date itself: Thursday 18:35." msgstr "" -#: ../settings/ticket.rst:167 -msgid "Notifications" +#: ../settings/branding.rst:71 +msgid "After a week it will switch to: ``Friday 4. Mar 16:00``." msgstr "" -#: ../settings/ticket.rst:191 -msgid "Default Notifications" +#: ../settings/branding.rst:76 +msgid "timestamp" msgstr "" -#: ../settings/ticket.rst:170 +#: ../settings/branding.rst:74 msgid "" -"This setting allows you to configure the default ticket notifications that " -"will be applied to all new agent users (incl. users who were just assigned " -"agent role). Simply change the notification matrix to desired state and " -"press **Save**." +"This will cause Zammad to show a complete timestamp according to your locale " +"defaults. For English this could be e.g. ``2022/12/03 2:40 pm`` or for " +"German e.g. ``12.03.2022 14:40``." msgstr "" -#: ../settings/ticket.rst:175 -msgid "" -"In case an agent already exists, their ticket notification preferences will " -"be preserved. Optionally, you can also **Apply current defaults to all " -"agents**." +#: ../settings/branding.rst:78 +msgid "Default setting: ``relative``." msgstr "" -#: ../settings/ticket.rst:181 -msgid "" -"**Potential time-consuming action:** Applying default ticket notifications " -"to all agent users may take some time to complete, be patient! The exact " -"time will depend on the size of your system and the number of agents." +#: ../settings/security.rst:2 +msgid "Security" msgstr "" -#: ../settings/ticket.rst:185 +#: ../settings/security.rst:4 msgid "" -"**Active agents only!** When current default ticket notifications are " -"applied, only active agent users are considered. In case an agent is re-" -"activated *after* this action, they will still have the old notification " -"configuration." +"For your overview we split each tab within security settings into its own " +"page:" msgstr "" -#: ../settings/ticket.rst:190 -msgid "" -"In case you want to go back to the initial state of ticket notifications, " -"you can click on **Reset to default** button." +#: ../settings/security/base.rst:2 ../settings/system/base.rst:2 +#: ../settings/ticket.rst:8 +msgid "Base" msgstr "" -#: ../settings/ticket.rst:194 ../settings/ticket.rst:196 -msgid "Duplicate Detection" +#: ../settings/security/base.rst:5 +msgid "New User Accounts" msgstr "" -#: ../settings/ticket.rst:236 ../settings/ticket.rst:238 -msgid "Detect Duplicate Ticket Creation" +#: ../settings/security/base.rst:9 +msgid "" +"Activates the `register as a new customer` function on the login page. If " +"set to ``no`` only administrators or agents can create new accounts manually." msgstr "" -#: ../settings/ticket.rst:197 ../settings/ticket.rst:199 -msgid "" -"This setting turns on the duplicate ticket detection mechanism during ticket " -"creation. If similar tickets are found in the system, a suitable warning " -"will be shown to the user trying to create a ticket." +#: ../settings/security/base.rst:13 ../settings/security/base.rst:38 +#: ../settings/security/base.rst:66 +msgid "Default setting: ``yes``" msgstr "" -#: ../settings/ticket.rst:204 ../settings/ticket.rst:206 -msgid "A Sample Duplicate Ticket Warning" +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"New User Accounts\" setting" msgstr "" -#: ../settings/ticket.rst:206 ../settings/ticket.rst:208 +#: ../settings/security/base.rst:22 msgid "" -"You can choose which ticket attributes will be matched by selecting them in " -"**Attributes to compare** field. Only if the ticket attribute value provided " -"by the user in the ticket create form is *equal* with the attribute in an " -"existing ticket, the warning will be shown." +"Deactivation of above function **does not** deactivate automatic account " +"creation! This means: If a user writes e.g. an email to Zammad and has no " +"account yet, Zammad will automatically create the account. User accounts are " +"a direct dependency of tickets and thus technically mandatory." msgstr "" -#: ../settings/ticket.rst:211 ../settings/ticket.rst:213 -msgid "**Warning title** and **Warning message** are configurable as well." +#: ../settings/security/base.rst:29 +msgid "Lost Password" msgstr "" -#: ../settings/ticket.rst:213 ../settings/ticket.rst:215 +#: ../settings/security/base.rst:33 msgid "" -"You can limit the detection only to certain user roles. By default, only " -"agents will see the warning." +"Activates the `lost password` function on the login page. If set to ``no`` " +"only administrators may change the user's password - users may update their " +"own password if they're still logged in and they have the required :doc:" +"`permission `." msgstr "" -#: ../settings/ticket.rst:216 ../settings/ticket.rst:218 -msgid "" -"If you don't want to show the matched tickets as part of the warning, you " -"can set **Show matching ticket(s) in the warning** setting to *no*." +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"Lost Password\" setting" msgstr "" -#: ../settings/ticket.rst:219 ../settings/ticket.rst:221 +#: ../settings/security/base.rst:49 msgid "" -"By default, **Permission level for looking up ticket** is set to *User*, " -"which means user permissions will be honored during sarch. The user will " -"see the warning only if tickets they have access to are matched. " -"Alternatively, you can set this setting to *System*, in which case the " -"search will happen within *all* tickets in the system, regardless of user " -"permissions." +"With third party authentications - but especially LDAP - you may want to " +"disable this function. Zammad **will not** change third party login " +"passwords and instead set or change the local password!" msgstr "" -#: ../settings/ticket.rst:225 ../settings/ticket.rst:227 -msgid "**🦺 Safety first!**" +#: ../settings/security/base.rst:56 +msgid "Password Login" msgstr "" -#: ../settings/ticket.rst:227 ../settings/ticket.rst:229 +#: ../settings/security/base.rst:60 msgid "" -"Even if the permission level is set to *System*, the user will not be shown " -"the tickets they don't have access to in the warning, even if they match." +"Activates the username & password login by default and if no third-party " +"login is activated. Disabling password login on the Zammad login page only " +"takes effect if you enable any :doc:`third-party`." msgstr "" -#: ../settings/ticket.rst:231 ../settings/ticket.rst:233 -msgid "" -"However, just the confirmation about the existence of the tickets in the " -"system may be considered an unwanted information disclosure. Use this option " -"carefully!" +#: ../settings/security/base.rst:64 +msgid "See :doc:`third-party` for supported third-party logins." +msgstr "" + +#: ../settings/security/base.rst:0 +msgid "Figure showing de-activated \"Password Login\" setting" msgstr "" -#: ../settings/ticket.rst:235 ../settings/ticket.rst:237 +#: ../settings/security/base.rst:77 msgid "" -"Finally, you can configure between matching within **All tickets** or **Open " -"tickets** only by setting **Match tickets in following states**. Depending " -"on the current ticket state, a ticket may or not be matched." +"To help administrators to overcome \"login issues\", Zammad automatically " +"offers a password request for administrator users. This allows you to adjust " +"Third-Party applications even if the login does no longer work!" msgstr "" -#: ../system/core-workflows.rst:2 -msgid "Core Workflows" +#: ../settings/security/base.rst:84 +msgid "Session Timeout" msgstr "" -#: ../system/core-workflows.rst:4 +#: ../settings/security/base.rst:86 msgid "" -"Core Workflows allow you to adjust object attributes in many ways. For " -"example:" +"All settings below by default are set to ``4 weeks``. Session Timeout " +"defines the life time of a users session. As soon as it's reached, Zammad " +"will automatically log off the session in question." msgstr "" -#: ../system/core-workflows.rst:7 -msgid "show / hide fields" +#: ../settings/security/base.rst:91 +msgid "" +"Zammad takes the highest value set assigned for the user based on the " +"permissions." msgstr "" -#: ../system/core-workflows.rst:8 -msgid "adjust mandatory setting" +#: ../settings/security/base.rst:94 +msgid "``admin``" msgstr "" -#: ../system/core-workflows.rst:9 -msgid "manipulate available options" +#: ../settings/security/base.rst:96 +msgid "``ticket.customer``" msgstr "" -#: ../system/core-workflows.rst:11 -msgid "" -"With this, you can provide exactly the information your users really need!" +#: ../settings/security/base.rst:97 +msgid "``default`` (fallback if user doesn't have above permissions set)" msgstr "" -#: ../system/core-workflows.rst:15 +#: ../settings/security/base.rst:99 msgid "" -"If the pre-defined :doc:`/system/objects` are not enough, please add them " -"beforehand." +"All settings act independently from each other allowing you to disable the " +"timeouts for e.g. admins, but not agents." msgstr "" -#: ../system/core-workflows.rst:17 -msgid "" -"If you experience slow or unreliable field updates, please see :ref:`Core " -"Workflow Ajax Modus `" -msgstr "" +#: ../settings/security/base.rst:115 +#: ../system/integrations/checkmk/api-reference.rst:13 +msgid "Example" +msgstr "Exempel" -#: ../system/core-workflows.rst:22 -msgid "" -"This is a very enhanced functionality and can cause unexpected UI behavior. " -"Please ensure to test your use cases after configuration to reduce surprises." +#: ../settings/security/base.rst:107 +msgid "Let's suppose you configured the following session timeouts" msgstr "" -#: ../system/core-workflows.rst:None -msgid "Dialogue for adding a new workflow" +#: ../settings/security/base.rst:104 +msgid "default: 3 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:2 -msgid "Core Workflow Condition Operators" +#: ../settings/security/base.rst:105 +msgid "admin: 2 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:4 -msgid "" -"You might know that there is a separate section for explaining :doc:" -"`condition operators `. Head over there to " -"see a detailed explanation of many conditions and operators." +#: ../settings/security/base.rst:106 +msgid "ticket.agent: 4 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:8 -msgid "" -"Due to differences to other places in Zammad which are also using conditions " -"(e.g. triggers), you can find a dedicated description of operators for core " -"workflows below." +#: ../settings/security/base.rst:107 +msgid "ticket.customer: 1 week" msgstr "" -#: ../system/core-workflows/condition-operators.rst:12 -msgid "" -"Be aware that the availability of the operators depends on the selected " -"attribute and its field type. Some of the operators may only be available " -"for system attributes (e.g. for \"tags\", \"active\")." +#: ../settings/security/base.rst:115 +msgid "This results in the following situations" msgstr "" -#: ../system/core-workflows/condition-operators.rst:20 -msgid "Operator" +#: ../settings/security/base.rst:110 +msgid "a user with ``admin`` permission will have a timeout of 2 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:22 -msgid "after (absolute)" +#: ../settings/security/base.rst:111 +msgid "" +"a user with ``admin`` and ``ticket.agent`` permissions will have a timeout " +"of 2 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:23 -msgid "Matches if a date/time is after a specific point in time." +#: ../settings/security/base.rst:113 +msgid "" +"a user with ``ticket.customer`` permission will have a timeout of 1 week" msgstr "" -#: ../system/core-workflows/condition-operators.rst:24 -msgid "after (relative)" +#: ../settings/security/base.rst:115 +msgid "" +"a user with neither ``admin``, ``ticket.agent`` nor ``ticket.customer`` " +"permissions will have a timeout of 3 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:25 -msgid "Matches if a time span after a specified event has passed." +#: ../settings/security/password.rst:4 +msgid "" +"This section allows you to define password requirements for the local user " +"accounts." msgstr "" -#: ../system/core-workflows/condition-operators.rst:26 -msgid "before (absolute)" +#: ../settings/security/password.rst:9 +msgid "" +"Zammad does **not** allow you to change your LDAP password, instead, it will " +"set a password in its local database which might confuse your users. This " +"might be addressed in the future by `#1169 `_." msgstr "" -#: ../system/core-workflows/condition-operators.rst:27 -msgid "Matches if a date/time is before a specific point in time." +#: ../settings/security/password.rst:14 +msgid "**Exception for admins**" msgstr "" -#: ../system/core-workflows/condition-operators.rst:28 -msgid "before (relative)" +#: ../settings/security/password.rst:16 +msgid "" +"Please note that below password policies *do not* affect administrators " +"setting passwords on user accounts. While this seems strange and not safe we " +"believe that an administrator knowing an user's password is insecure as well." msgstr "" -#: ../system/core-workflows/condition-operators.rst:29 -msgid "Matches if a time span after a specified event has not passed." +#: ../settings/security/password.rst:21 +msgid "The suggested workflow is either:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:30 -msgid "contains" +#: ../settings/security/password.rst:23 +msgid "" +"to use third party logins to not require local passwords at all **- or -**" msgstr "" -#: ../system/core-workflows/condition-operators.rst:31 -msgid "Matches if a specified value is present." +#: ../settings/security/password.rst:25 +msgid "to require your *user to reset the password* upon first login." msgstr "" -#: ../system/core-workflows/condition-operators.rst:33 -msgid "Matches if all of the specified values are present." +#: ../settings/security/password.rst:27 +msgid "" +"This way administrators are not required to set a user's password at all!" msgstr "" -#: ../system/core-workflows/condition-operators.rst:35 -msgid "Matches if none of the specified values are present." +#: ../settings/security/password.rst:31 +msgid "Maximum Failed Logins" msgstr "" -#: ../system/core-workflows/condition-operators.rst:36 -msgid "contains not" +#: ../settings/security/password.rst:33 +msgid "" +"You can choose a value between ``4`` and ``20``. This defines how often a " +"login to a user account may fail until Zammad will lock it. Your users can " +"always use the \"forgot password\" function to change their password and " +"unlock their account." msgstr "" -#: ../system/core-workflows/condition-operators.rst:37 -msgid "Matches if a specified value is not present." +#: ../settings/security/password.rst:38 +msgid "The default value is ``10``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:39 -msgid "Matches if one specified value is present." +#: ../settings/security/password.rst:42 +msgid "Beside changing the user's password, you can also unlock accounts via" msgstr "" -#: ../system/core-workflows/condition-operators.rst:41 -msgid "Matches if one specified value is not present." +#: ../settings/security/password.rst:44 +msgid ":ref:`user management list `" msgstr "" -#: ../system/core-workflows/condition-operators.rst:42 -msgid "does not match regex" +#: ../settings/security/password.rst:45 +msgid ":docs:`console `" msgstr "" -#: ../system/core-workflows/condition-operators.rst:43 -msgid "Matches if content doesn't fit to regex rule." +#: ../settings/security/password.rst:46 +msgid ":docs:`API `" msgstr "" -#: ../system/core-workflows/condition-operators.rst:44 -msgid "ends with" +#: ../settings/security/password.rst:50 +msgid "Failed logins via LDAP no longer lock accounts." msgstr "" -#: ../system/core-workflows/condition-operators.rst:45 -msgid "Matches if content ends with specified value." +#: ../settings/security/password.rst:53 +msgid "2 Lower Case And 2 Upper Case Characters" msgstr "" -#: ../system/core-workflows/condition-operators.rst:46 -msgid "ends with one of" +#: ../settings/security/password.rst:55 +msgid "" +"You can add complexity to passwords by enforcing at least 2 upper and lower " +"case characters." msgstr "" -#: ../system/core-workflows/condition-operators.rst:47 -msgid "Matches if content ends with one of the specified values." +#: ../settings/security/password.rst:58 ../settings/security/password.rst:83 +msgid "The default value is ``no``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:48 -msgid "from (relative)" +#: ../settings/security/password.rst:62 +msgid "Minimum Length" msgstr "" -#: ../system/core-workflows/condition-operators.rst:49 -msgid "Matches if date/time is after a period of time after an event." +#: ../settings/security/password.rst:64 +msgid "" +"This defines the minimum password length required for users to provide (from " +"``4`` to ``20``)." msgstr "" -#: ../system/core-workflows/condition-operators.rst:51 -msgid "Matches if content is equal to a specified value." +#: ../settings/security/password.rst:67 +msgid "The default value is ``6``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:52 -msgid "is any of" +#: ../settings/security/password.rst:71 +msgid "Digit Required" msgstr "" -#: ../system/core-workflows/condition-operators.rst:53 -msgid "Matches if content is equal to any of specified values." +#: ../settings/security/password.rst:73 +msgid "This enforces your users to use at least one digit within the password." msgstr "" -#: ../system/core-workflows/condition-operators.rst:54 -msgid "is modified" +#: ../settings/security/password.rst:75 +msgid "The default value is ``yes``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:55 -msgid "Matches if content is modified." +#: ../settings/security/password.rst:78 +msgid "Special Character Required" msgstr "" -#: ../system/core-workflows/condition-operators.rst:57 -#: ../system/core-workflows/condition-operators.rst:61 -msgid "True from the moment of changing content until form submit." +#: ../settings/security/password.rst:80 +msgid "" +"This setting allows you to improve your password quality even more by " +"enforcing the password to contain at least one special character." msgstr "" -#: ../system/core-workflows/condition-operators.rst:58 -msgid "is modified to" +#: ../settings/security/ssl-certificates.rst:2 +msgid "SSL Certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:59 -msgid "Matches if content is modified to a specific value." +#: ../settings/security/ssl-certificates.rst:7 +msgid "" +"Zammad offers the possibility to upload custom certificates and custom " +"Certificate Authority (CA) certificates. This can be useful if you want to " +"connect Zammad the secure way to other systems which are using custom " +"certificates." msgstr "" -#: ../system/core-workflows/condition-operators.rst:62 -msgid "is none of" +#: ../settings/security/ssl-certificates.rst:12 +msgid "" +"An example usecase might be: You have an internal LDAP server that is not " +"accessible from the internet, and you want a SSL-encrypted connection, using " +"a custom certificate." msgstr "" -#: ../system/core-workflows/condition-operators.rst:63 -msgid "Matches if content is none of any specified values." +#: ../settings/security/ssl-certificates.rst:19 +msgid "" +"You should have an existing custom certificate file and/or a custom CA " +"certificate file, which you want to add to Zammad. As filetype ``.crt`` is " +"supported and the certificate format has to be PEM (Base64 ASCII)." msgstr "" -#: ../system/core-workflows/condition-operators.rst:65 -msgid "Matches if content is not equal to a specified value." +#: ../settings/security/ssl-certificates.rst:25 +msgid "" +"When you import a custom CA certificate, all certificates generated with " +"this are trusted. This can be useful if you have more than one system/" +"certificate you want to connect to and the certificates are issued from the " +"same custom CA." msgstr "" -#: ../system/core-workflows/condition-operators.rst:67 -msgid "Matches if content is present." +#: ../settings/security/ssl-certificates.rst:31 +msgid "Add a Certificate" msgstr "" -#: ../system/core-workflows/condition-operators.rst:68 -msgid "just changed" +#: ../settings/security/ssl-certificates.rst:33 +msgid "" +"To add a custom certificate or a custom CA certificate, head over to the " +"Admin panel > Settings > Security > SSL Certificates. Here you can find a " +"\"Add SSL Certificate\" button. In the dialog you can either select a " +"certificate file or paste the content of the certificate:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:69 -msgid "Matches if content has changed." +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate adding dialog" msgstr "" -#: ../system/core-workflows/condition-operators.rst:71 -#: ../system/core-workflows/condition-operators.rst:75 +#: ../settings/security/ssl-certificates.rst:43 msgid "" -"Only true for the moment of changing content until next form field action/" -"click." +"After selecting a file or pasting the content of the certificate, click on " +"the \"Add\" button to finally upload it to Zammad. Then, the certificates " +"are immediately effective, no restart or similar required." msgstr "" -#: ../system/core-workflows/condition-operators.rst:72 -msgid "just changed to" +#: ../settings/security/ssl-certificates.rst:49 +msgid "" +"Please note that only single certificate files are supported. That means if " +"you want to import a certificate / CA certificate, it must contain **only " +"one** certificate." msgstr "" -#: ../system/core-workflows/condition-operators.rst:73 -msgid "Matches if content has changed to a specified value." +#: ../settings/security/ssl-certificates.rst:54 +msgid "Certificate Overview" msgstr "" -#: ../system/core-workflows/condition-operators.rst:76 -msgid "matches regex" +#: ../settings/security/ssl-certificates.rst:56 +msgid "" +"After you added a certificate, you can see a table with information for each " +"added certificate:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:77 -msgid "Matches if value fits to regex rule." -msgstr "" - -#: ../system/core-workflows/condition-operators.rst:79 -msgid "Matches if no content is present." +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing table of added certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:80 -msgid "starts with" +#: ../settings/security/ssl-certificates.rst:64 +msgid "" +"Here you can download the certificate or delete it, if you don't need it " +"anymore." msgstr "" -#: ../system/core-workflows/condition-operators.rst:81 -msgid "Matches if content starts with specified value." +#: ../settings/security/ssl-certificates.rst:68 +msgid "Deleting Certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:82 -msgid "starts with one of" +#: ../settings/security/ssl-certificates.rst:70 +msgid "" +"If you want to delete a specific certificate, you can do it by clicking on " +"the menu in the actions column and selecting delete:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:83 -msgid "Matches if content starts with one of the specified values." +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate deletion button" msgstr "" -#: ../system/core-workflows/condition-operators.rst:84 -msgid "till (relative)" +#: ../settings/security/ssl-certificates.rst:79 +msgid "Downloading Certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:85 -msgid "Matches if date/time is before a period of time before an event." +#: ../settings/security/ssl-certificates.rst:81 +msgid "" +"If you want to download your certificates, you can do this as well via " +"corresponding action buttons." msgstr "" -#: ../system/core-workflows/condition-operators.rst:86 -msgid "today" +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate download button" msgstr "" -#: ../system/core-workflows/condition-operators.rst:87 -msgid "Matches if date/time is today." +#: ../settings/security/third-party.rst:13 +msgid "Login Providers" msgstr "" -#: ../system/core-workflows/condition-operators.rst:88 -msgid "within last (relative)" +#: ../settings/security/third-party.rst:2 +msgid "Third-Party Applications" msgstr "" -#: ../system/core-workflows/condition-operators.rst:89 +#: ../settings/security/third-party.rst:4 msgid "" -"Matches if date/time content is within specified period of time before now." +"Third party authentication is a great way to help your users to login to " +"Zammad more easily. If the account is yet unknown, Zammad will create a new " +"user automatically, without the user needed to interact (e.g. type in his " +"name). Another big advantage of this feature is that your user doesn't need " +"to remember another password." msgstr "" -#: ../system/core-workflows/condition-operators.rst:91 -msgid "within next (relative)" +#: ../settings/security/third-party.rst:10 +msgid "" +"You can deactivate logging in via :ref:`security_password_login` if any of " +"the mentioned authentication providers are enabled in your instance." msgstr "" -#: ../system/core-workflows/condition-operators.rst:92 +#: ../settings/security/third-party.rst:27 msgid "" -"Matches if date/time content is within specified period of time after now." +"We're currently missing documentation for the following login providers:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:2 -msgid "How do they work?" +#: ../settings/security/third-party.rst:29 +msgid "LinkedIn" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:4 -msgid "" -"Core Workflows are executed according to their priority. If two workflows " -"have the same priority, they are executed in alphabetical order based on " -"their **name**." +#: ../settings/security/third-party.rst:30 +msgid "Weibo" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:8 -msgid "" -"Because of the way Core Workflows work, all changes to attributes are " -"checked with the application server - please see :doc:`limitations` for " -"possible issues." +#: ../settings/security/third-party.rst:35 +msgid "Automatic Account Link on Initial Logon" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:12 +#: ../settings/security/third-party.rst:37 msgid "" -"Below we're talking about settings that are important and not self-" -"explanatory." +"In general there's two possible options for Zammad on how to deal with " +"already known users as they try to authenticate against a third-party " +"application. By default, Zammad will not automatically link \"unknown\" " +"authentication providers to existing accounts." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:17 +#: ../settings/security/third-party.rst:42 msgid "" -"Choose the object context you want to run the workflow in. This will decide " -"on your available attributes and actions." -msgstr "" - -#: ../system/core-workflows/how-do-they-work.rst:20 -msgid "Ticket objects also have access to the ticket customer." +"This means that the user has to manually link authentication providers to " +"their accounts (for more about this :user-docs:`consult the user " +"documentation `)." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:25 +#: ../settings/security/third-party.rst:46 msgid "" -"Choose in which situation the workflow is applied. Contexts can be combined " -"to avoid duplicate workflows." +"Sometimes this doesn't come in handy as this also means you'll receive error " +"messages about \"email address being in use already\" for (yet) unknown " +"third-party authentication methods." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:30 -msgid "Creation mask" +#: ../settings/security/third-party.rst:50 +msgid "" +"If you want to allow your users to always be able to log in, no matter what, " +"you may want to enable ``Automatic account link on initial logon``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:29 +#: ../settings/security/third-party.rst:None msgid "" -"If selected, your conditions and actions will affect all applicable creation " -"masks." +"Screenshot highlighting the \"Automatic account link on initial logon\"\n" +"setting" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:34 -msgid "Edit mask" +#: ../settings/security/third-party.rst:60 +msgid "Automatic Account Linking Notification" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:33 +#: ../settings/security/third-party.rst:64 msgid "" -"If selected, your conditions and actions will affect all applicable edit " -"masks." +"To improve security and your users awareness, you can enable Zammad to " +"notify your users when a new third-party application has been linked to " +"their account." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:39 +#: ../settings/security/third-party.rst:68 msgid "" -"Zammad differentiates between selected and saved conditions. These can be " -"combined wherever needed." +"This notification is sent out once per third-party application. Zammad does " +"also mention the method used, e.g.: ``Microsoft``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:42 -msgid "**⚠️ Restrict workflows to specific roles if needed!**" +#: ../settings/security/third-party.rst:71 +msgid "By default this setting is not active (set to ``no``)." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:44 +#: ../settings/security/third-party.rst:0 msgid "" -"By default and unless configured in conditions, workflow rules are executed " -"for **all roles**. This also affects your customers!" +"Screenshot showing sample notification mail after initial\n" +"third-party linking" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:50 -msgid "Selected Conditions" +#: ../settings/security/third-party.rst:85 +msgid "" +"This notification is only sent if the account in question already exists. If " +"the login via the third-party also creates the missing account, the " +"notification will be skipped." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:48 -msgid "" -"These conditions are based on form values and match if an appropriate " -"selection is made (e.g. choosing another group in the ticket without " -"saving). This applies for drafts (active selection) and currently saved " -"values." +#: ../settings/security/third-party.rst:89 +msgid "This means it only affects:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:64 -msgid "Saved Conditions" +#: ../settings/security/third-party.rst:91 +msgid "manual account linking within the third-party page of the users profile" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:53 +#: ../settings/security/third-party.rst:92 msgid "" -"These conditions only match if the selected values are stored in the " -"database. It ignores the current value or selection of the field, as long as " -"the changes are not saved (e.g. performing field operations for an existing " -"ticket, which is viewed/opened by an agent)." +"logging into an existing local account by utilizing the *automatic account " +"link on initial logon* functionality" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:60 +#: ../settings/security/third-party.rst:None msgid "" -"Keep in mind that the value has to be available in the situation where you " -"need it. Otherwise the condition won't match." +"Screenshot showing the \"automatic account linking notification\"\n" +"setting" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:63 -msgid "" -"Example: you can't perform any actions with *saved condition* on a ticket in " -"creation, because there are no saved values at that time." +#: ../settings/security/third-party.rst:100 +msgid "No User Creation on Logon" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:66 +#: ../settings/security/third-party.rst:102 msgid "" -"You can find a description of the condition operators for core workflows :" -"doc:`here `." +"By default, Zammad will create a new user account if the user logs in via a " +"third-party application and the account doesn't exist yet." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:72 +#: ../settings/security/third-party.rst:105 msgid "" -"Which actions should we run on the relevant fields? The possible actions " -"depend on the object type. However, usually you can at least change the " -"visibility and whether the field is mandatory." +"If you want to prevent Zammad from creating new accounts on logon, you can " +"disable this feature by setting ``No user creation on logon`` to ``yes``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:76 -msgid "Be aware that actions are not available for **related** context." +#: ../settings/security/third-party.rst:None +msgid "Screenshot showing the \"no user creation on logon\" setting" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:78 +#: ../settings/security/third-party/facebook.rst:4 msgid "" -"**Example:** Let's assume you are working in the ticket context. While you " -"can have customer *conditions*, you *can't adjust* objects with actions in " -"that scope. That's because this wouldn't have any impact on the ticket " -"dialog. Of course all ticket attributes (state, owner, ...) are available." +"It is possible to create a quick login for your helpdesk via Facebook To do " +"so, you need to follow these steps:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:84 -msgid "" -"Please also have a look at our :doc:`limitations` to be safe from surprises." +#: ../settings/security/third-party/facebook.rst:9 +msgid "Register Facebook App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:88 -msgid "Available Operators" +#: ../settings/security/third-party/facebook.rst:11 +msgid "" +"Visit [https://developers.facebook.com/apps/] and click on \"Add a new App\"" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:90 -msgid "The availability of operators depends on the object type and scope." +#: ../settings/security/third-party/facebook.rst:None +msgid "initial page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:94 -msgid "" -"Please note that actions may or may not restrict API based access to " -"attributes. We're displaying the following icons for your overview to " -"understand these limits better:" +#: ../settings/security/third-party/facebook.rst:17 +msgid "After that enter the app settings" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:0 -msgid "|api| This icon indicates the action affects the API." +#: ../settings/security/third-party/facebook.rst:None +msgid "Create App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:163 -msgid "api" +#: ../settings/security/third-party/facebook.rst:22 +msgid "Navigate to \"Settings\" and fill in this infromation" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:0 -msgid "|ui| This icon indicates the action only affects the web interface." +#: ../settings/security/third-party/facebook.rst:None +msgid "App Settings" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:167 -msgid "ui" +#: ../settings/security/third-party/facebook.rst:27 +msgid "Navigate to app review and Check \"Make [appname] public?\"" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:102 -msgid "show |ui|" +#: ../settings/security/third-party/facebook.rst:None +msgid "App Review" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:102 -msgid "Display the chosen field. Allows setting of values." +#: ../settings/security/third-party/facebook.rst:35 +msgid "Configure Zammad as Facebook App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:109 -msgid "hide |ui|" +#: ../settings/security/third-party/facebook.rst:37 +msgid "" +"Navigate to \"Admin -> Security -> Third Party Applications\" and enter the " +"App ID and the App Secret. You can find this Key in the Dashbard of your " +"Facebok app." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:105 -msgid "" -"Hide the chosen field. However, it technically still allows setting the " -"field." +#: ../settings/security/third-party/facebook.rst:None +msgid "Zammad Configuration" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:108 +#: ../settings/security/third-party/facebook.rst:44 +#: ../settings/security/third-party/github.rst:43 +#: ../settings/security/third-party/gitlab.rst:46 msgid "" -"Please note that the field is **not** gone and still contains an existing " -"value (if set)! Consider *remove* instead, if you want this field to be gone." +"Now you can link accounts via \"Avatar -> Profile -> Link Accounts\" or " +"login via Zammad login page." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:112 -msgid "remove |ui|" +#: ../settings/security/third-party/github.rst:2 +#: ../system/integrations/github.rst:2 +msgid "GitHub" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:112 -msgid "Entirely removes the field. The field value will not be evaluated." +#: ../settings/security/third-party/github.rst:4 +msgid "" +"It is possible to create a quick login for your helpdesk via GitHub. To " +"activate the quick login you need to enable OAuth for GitHub." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:115 -msgid "set mandatory |ui| |api|" +#: ../settings/security/third-party/github.rst:8 +msgid "Register GitHub App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:115 -msgid "Sets the field to mandatory." +#: ../settings/security/third-party/github.rst:10 +msgid "" +"Visit https://www.github.com/settings/applications/new and enter the app " +"settings. As callback URL enter \"https://zammad_host/auth/github/callback\" " +"where zammad_host has to be replaced with your Zammad FQDN" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:118 -msgid "set optional |ui| |api|" +#: ../settings/security/third-party/github.rst:None +msgid "Register OAuth app on www.github.com" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:118 -msgid "Sets the field to optional." +#: ../settings/security/third-party/github.rst:19 +msgid "Configure Zammad as GitHub App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:124 -msgid "add option |ui| |api|" +#: ../settings/security/third-party/github.rst:21 +msgid "" +"Enter the \"APP ID\" and the \"APP SECRET\" from the GitHub OAUTH " +"Applications Dashboard" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:121 -msgid "Allows adding options to tree selects or selects." +#: ../settings/security/third-party/github.rst:None +msgid "GitHub config in Zammad admin interface" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:123 +#: ../settings/security/third-party/github.rst:28 msgid "" -"You have to use the \"remove option\" before performing this action. It " -"allows you to use *existing* configured values." +"After you configured the GitHub credentials and activated the login method, " +"you should see a new icon on the login page." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:128 -msgid "remove option |ui| |api|" +#: ../settings/security/third-party/github.rst:None +msgid "GitHub logo on login page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:127 +#: ../settings/security/third-party/github.rst:34 msgid "" -"Allows removing options from tree selects or selects. It allows you to use " -"*existing* configured values." +"If you click on the icon you will be redirected to GitHub and see something " +"similar to this:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:134 -msgid "set fixed to |ui| |api|" +#: ../settings/security/third-party/github.rst:None +msgid "GitHub oauth page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:131 -msgid "Reduces the available options by your selection." +#: ../settings/security/third-party/github.rst:40 +#: ../settings/security/third-party/gitlab.rst:42 +msgid "" +"When you grant the access you will be redirected to your Zammad instance and " +"logged in as a customer." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:133 -msgid "" -"This reduces your workflows in terms of *add option* and *remove option*." +#: ../settings/security/third-party/gitlab.rst:2 +msgid "Gitlab" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:137 -msgid "fill in |ui|" +#: ../settings/security/third-party/gitlab.rst:4 +msgid "" +"It is possible to create a quick login for your helpdesk via Gitlab. To " +"activate the quick login you need to enable OAuth for Gitlab." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:137 -msgid "Allows filling in of string and integer fields with your values." +#: ../settings/security/third-party/gitlab.rst:8 +msgid "Register Gitlab App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:141 -msgid "fill in empty |ui|" +#: ../settings/security/third-party/gitlab.rst:10 +msgid "To register an app in Gitlab open your profile and select applications." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:140 +#: ../settings/security/third-party/gitlab.rst:12 msgid "" -"Allows filling in of string and integer fields with your values **if the " -"field is empty**." +"As callback URL enter \"https://zammad-fqdn/auth/gitlab/callback\" where " +"zammad-fqdn has to be replaced with your Zammad FQDN" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:144 -msgid "select |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Register OAuth app on gitlab instance" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:144 -msgid "Select a specific value within a select, tree select or boolean field." +#: ../settings/security/third-party/gitlab.rst:18 +msgid "Just select *read_user* under scopes as in the screenshot and save it." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:153 -msgid "auto select |ui|" +#: ../settings/security/third-party/gitlab.rst:21 +msgid "Configure Zammad as Gitlab App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:147 -msgid "Helps users with tree select and select fields:" +#: ../settings/security/third-party/gitlab.rst:23 +msgid "" +"Enter the \"APP ID\" and the \"APP SECRET\" from the Gitlab OAUTH " +"Applications Dashboard and your Gitlab-URL in the \"SITE\" field." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:149 -msgid "" -"If the field has only one option available for selection and no value yet, " -"the value will be automatically set." +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab config in Zammad admin interface" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:152 +#: ../settings/security/third-party/gitlab.rst:30 msgid "" -"This option only works if you have one value and doesn't work if there is " -"more than one option available." +"After you configured the Gitlab credentials and activated the login method, " +"you should see a new icon on the login page." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:157 -msgid "set readonly |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab logo on login page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:156 +#: ../settings/security/third-party/gitlab.rst:36 msgid "" -"Allows you to display an attribute as read only (which means no changes are " -"possible)." +"If you click on the icon you will be redirected to Gitlab and see something " +"similar to this:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:161 -msgid "unset readonly |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab oauth page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:160 +#: ../settings/security/third-party/google.rst:4 msgid "" -"In case a workflow set the field in question to read only, you can undo this " -"with option above." +"With some easy and fast steps, you can enable Zammad to authenticate your " +"users via Google." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:172 -msgid "Stop after match" +#: ../settings/security/third-party/google.rst:8 +msgid "Register a Google App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:174 +#: ../settings/security/third-party/google.rst:10 msgid "" -"Here you can decide if other workflows are executed after the current one." +"First of all, we need to create a new project - you can skip this step if " +"you already have one." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:176 +#: ../settings/security/third-party/google.rst:15 msgid "" -"If set to ``no`` (default), further workflows will be executed if they match " -"the condition. In this case, it is possible that your actions from the " -"current workflow can be overwritten by another workflow." +"Use this link to create a new project: https://console.cloud.google.com/" +"projectcreate" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:180 +#: ../settings/security/third-party/google.rst:18 msgid "" -"If set to ``yes``, no further worflows will be executed after the current " -"one." +"Now expand the menu, expand \"APIs & Services\" and select \"Credentials\". " +"Go to the tab \"OAuth consent screen\" first and ensure to fill in the " +"requested information - without doing so you can't create credentials!" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:184 -msgid "Priority" +#: ../settings/security/third-party/google.rst:None +msgid "Creating a consent screen" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:186 +#: ../settings/security/third-party/google.rst:25 msgid "" -"You can define the sequence, in which the workflows are executed. The " -"default value is ``500``." +"After filling in and saving the consent screen information, you can go to " +"the \"Credentials\" tab and create new \"OAuth client ID\"-Credentials." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:189 +#: ../settings/security/third-party/google.rst:28 msgid "" -"The workflows are executed in ascending order by their priority. That means " -"lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." +"Fill in the necessary information as follows and replace ``zammad_host`` " +"with your FQDN:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:2 -msgid "Learn by Example" +#: ../settings/security/third-party/google.rst:31 +msgid "**Application type** ``[x] Web application``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:4 -msgid "" -"This page provides some basic examples for Core Workflows. Of course you can " -"build much more complex workflows if needed." +#: ../settings/security/third-party/google.rst:34 +msgid "**Authorized JavaScript origins** ``https://zammad_host/``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:7 +#: ../settings/security/third-party/google.rst:37 msgid "" -"To learn about Core Workflows in detail, first go to :doc:`how-do-they-work`." +"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" +"callback``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:10 -msgid "Group Based Examples" +#: ../settings/security/third-party/google.rst:None +msgid "Adding a new OAuth client ID" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:12 +#: ../settings/security/third-party/google.rst:43 msgid "" -"All following workflows have the same base configurations. The workflow may " -"not use them all." +"After creating the credentials, go to your Zammad installation and navigate " +"to \"Admin > Security > Third Party Applications\" > Google. Enter your " +"Client ID and Client secret here." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:15 -msgid "Groups:" +#: ../settings/security/third-party/google.rst:None +msgid "Zammad" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:20 -msgid "Attributes:" +#: ../settings/security/third-party/google.rst:50 +msgid "After submitting, the login via Google can be used." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:22 -msgid "Category (Single tree selection field, not mandatory, agents only)" +#: ../settings/security/third-party/microsoft.rst:2 +msgid "Microsoft" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:23 +#: ../settings/security/third-party/microsoft.rst:4 msgid "" -"Approved (Boolean field, not mandatory, not shown, ``false`` as default)" +"Zammad's Microsoft connection allows your users with Microsoft accounts to " +"login. This works for Azure users as well and can be an alternative to :doc:" +"`/system/integrations/ldap/index`." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:24 -msgid "Operating System (Text field, not mandatory, not shown)" +#: ../settings/security/third-party/microsoft.rst:10 +msgid "" +"This documentation part does not cover our :doc:`📧 Microsoft 365 email " +"channel `." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:25 -msgid "Software used (Single selection field, not mandatory, not shown)" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screenshot showing Microsoft login button on Zammad login screen." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:68 -msgid "Group specific values and fields" +#: ../settings/security/third-party/microsoft.rst:30 +#: ../settings/security/third-party/microsoft.rst:53 +msgid "Supported account types:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:28 +#: ../settings/security/third-party/microsoft.rst:22 msgid "" -"This workflow set depends on the category field. It reduces the available " -"set of values based on the group selected." +"Please note that Zammad only supports these account types (App dependent):" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:33 -msgid "Workflow 2nd Level group" +#: ../settings/security/third-party/microsoft.rst:35 +msgid "Avatars of signing in users:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:35 +#: ../settings/security/third-party/microsoft.rst:33 msgid "" -"This reduces the category options to ``2nd Level/*``, ``Internal/*`` and " -"``Others``. It also sets further required fields to mandatory and visible." -msgstr "" - -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for 2nd level" +"Zammad currently ignores user avatars. If the user is registered with e.g. " +"Gravatar, Zammad will fetch the avatar from there if enabled. See :doc:" +"`Zammad Image Service ` for more." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:43 -msgid "Workflow Support group" +#: ../settings/security/third-party/microsoft.rst:38 +msgid "Step 1 - Register a Microsoft App for Zammad" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:45 +#: ../settings/security/third-party/microsoft.rst:40 msgid "" -"This reduces the category options to ``Support/*``, ``Internal/*`` and " -"``Others``. It also sets further required fields to visible." -msgstr "" - -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for support" +"Login to the `Microsoft Azure Portal `_ and " +"navigate to App registrations to create a new app. Provide the requested " +"information as follows and register your app." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:53 -msgid "Workflow Sales group" +#: ../settings/security/third-party/microsoft.rst:46 +msgid "Name:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:55 +#: ../settings/security/third-party/microsoft.rst:45 msgid "" -"This reduces the category options to ``Sales/*``, ``Internal/*`` and " -"``Others``." +"Any meaningful name fitting, this name will be displayed to users trying to " +"authenticate with this app." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for sales" +#: ../settings/security/third-party/microsoft.rst:49 +msgid "Choose one of the above mentioned account types (see Limitations)." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:68 -#: ../system/integrations/slack.rst:88 -msgid "The Result" +#: ../settings/security/third-party/microsoft.rst:51 +msgid "" +"The correct account type depends on your use case. If you want to use the " +"authentication internal only, choose the first option. If you're unsure, use " +"the \"Help me choose...\" link." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:63 -msgid "" -"This is what the agent would experience with the above workflows in place." +#: ../settings/security/third-party/microsoft.rst:58 +msgid "Redirect URI (optional):" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 +#: ../settings/security/third-party/microsoft.rst:56 msgid "" -"Workflow shows objects and limits options based on selections on the group" +"Select web and provide your callback URL. The callback URL looks like this: " +"``https://zammad.domain.tld/auth/microsoft_office365/callback``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:90 -msgid "Approval process" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to register a Microsoft app" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:71 -msgid "" -"In this case ``approved`` is visible to agents by default. For this " -"workflow, an additional role ``Approval person`` is required (no further " -"permissions)." +#: ../settings/security/third-party/microsoft.rst:71 +msgid "Within **API permissions** add the following permissions:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that restricts an approval attribute to specific roles" +#: ../settings/security/third-party/microsoft.rst:69 +msgid "``User.Read``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:81 -msgid "" -"This workflow may work best in combination with a :doc:`trigger ` but technically, this is not required." +#: ../settings/security/third-party/microsoft.rst:71 +msgid "Contacts" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:84 -msgid "" -"Select fields may be a better approach because they allow more values than " -"just a simple ``true`` or ``false``." +#: ../settings/security/third-party/microsoft.rst:71 +msgid "``Contacts.Read``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 +#: ../settings/security/third-party/microsoft.rst:73 msgid "" -"Workflow fixes possible values of \"Approved ?\" to a specific selection " -"depending on the users role" +"You can find these permissions within *Microsoft Graph → Delegated " +"permissions*." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:103 -msgid "State dependent mandatory fields" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to add required API permissions" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:93 +#: ../settings/security/third-party/microsoft.rst:80 msgid "" -"This workflow sets ``Category`` to mandatory if the agent wants to set the " -"states ``closed`` or ``pending close`` to enforce categorization." +"Within **Certificates & secrets** create a new client secret. Note down the " +"returned secret **value** for later. **Do not** use the secret ID!" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that sets fields to mandatory on specific states" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to create a new app secret" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 +#: ../settings/security/third-party/microsoft.rst:88 msgid "" -"Workflow sets category field to mandatory upon choosing closed or pending " -"close as state" +"From **Overview** copy your apps *Application (client) ID*. If you're using " +"a single tenant app, please also copy *Directory (tenant) ID*. You now have " +"all required information for Zammad." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:106 -msgid "Manual Ticket Handover Process" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to retreive application client and tenant IDs" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:108 -msgid "This example covers the handover of a ticket from one agent to another:" +#: ../settings/security/third-party/microsoft.rst:98 +msgid "Step 2 - Add App Credentials to Zammad" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:110 +#: ../settings/security/third-party/microsoft.rst:100 msgid "" -"When the ticket owner is modified, a new text field (\"Handover\") shows up " -"for a comment" +"Navigate to Security > Third-party Applications (Tab) within Zammad's admin " +"settings. Scroll down to the section *Authentication via Microsoft* and fill " +"in the required information." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:112 -msgid "" -"This may only be visible when the owner is changed, therefore it has to be " -"hidden in general" +#: ../settings/security/third-party/microsoft.rst:105 +msgid "App ID:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:114 -msgid "The input in this handover text field is mandatory" +#: ../settings/security/third-party/microsoft.rst:105 +msgid "This is your *Application (client) ID*." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:115 -msgid "" -"After submitting changes, the value of the handover field must be added as " -"an note to the ticket (via trigger)" +#: ../settings/security/third-party/microsoft.rst:108 +msgid "App secret:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:121 -msgid "Hiding handover field" +#: ../settings/security/third-party/microsoft.rst:108 +msgid "This is your *client secret* (value)." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Hiding the handover field in core workflows" +#: ../settings/security/third-party/microsoft.rst:113 +msgid "App Tenant ID:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:126 -msgid "Showing handover field and setting it to mandatory" +#: ../settings/security/third-party/microsoft.rst:111 +msgid "" +"**optional** only required for apps that use account type *Accounts in this " +"organizational directory only (Default Directory only - Single tenant).*" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Showing the handover field and set it as mandatory" +#: ../settings/security/third-party/microsoft.rst:115 +msgid "" +"Apply your settings by pressing submit and activate *Authentication via " +"Microsoft*." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:131 -msgid "Trigger writing handover input to a new article" +#: ../settings/security/third-party/microsoft.rst:None +msgid "" +"Screencast showing how to add app credentials and activating the\n" +"authentication method" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Write handover content to a new article" +#: ../settings/security/third-party/saml.rst:2 +msgid "SAML" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:133 +#: ../settings/security/third-party/saml.rst:4 msgid "" -"As a result, the ticket includes an article of the type note which includes " -"the predefined text and the handover comment." +"Connect your SAML (Security Assertion Markup Language) identity provider as " +"a single sign-on (SSO) method." msgstr "" -#: ../system/core-workflows/limitations.rst:6 -msgid "Core Workflows do not replace Triggers" +#: ../settings/security/third-party/saml.rst:7 +msgid "" +"SAML is an open standard for SSO authentication (among other things). Sign-" +"ins are shared across multiple **service providers** and managed by a " +"central **identity provider** (IdP)." msgstr "" -#: ../system/core-workflows/limitations.rst:5 +#: ../settings/security/third-party/saml.rst:11 msgid "" -"Workflows manipulate the behavior of fields. However, they do not set values " -"in fields because of actions." +"In this case, the service provider is Zammad, and the IdP is a software " +"service that you either host or subscribe to (*e.g.,* `Keycloak `_, `Redhat SSO Server `_, `ADFS `_, or `Okta `_)." msgstr "" -#: ../system/core-workflows/limitations.rst:16 -msgid "API calls are only partly affected" +#: ../settings/security/third-party/saml.rst:18 +msgid "" +"This guide assumes you are already using SAML within your organization (i." +"e., that your IdP is fully set up)." msgstr "" -#: ../system/core-workflows/limitations.rst:9 +#: ../settings/security/third-party/saml.rst:21 msgid "" -"Some options affect UI only and thus do not restrict responses and calls." +"Please note: Our instructions are based on connecting Zammad with Keycloak." msgstr "" -#: ../system/core-workflows/limitations.rst:11 -msgid "This affects the following actions:" +#: ../settings/security/third-party/saml.rst:25 +msgid "Step 1: Configure Your IdP" msgstr "" -#: ../system/core-workflows/limitations.rst:13 -msgid "select" +#: ../settings/security/third-party/saml.rst:28 +msgid "Add Zammad as a Client/App" msgstr "" -#: ../system/core-workflows/limitations.rst:14 -msgid "auto select" +#: ../settings/security/third-party/saml.rst:30 +msgid "" +"Import Zammad into your IdP using the XML configuration found at ``https://" +"your.zammad.domain/auth/saml/metadata``." msgstr "" -#: ../system/core-workflows/limitations.rst:15 -msgid "show" +#: ../settings/security/third-party/saml.rst:33 +msgid "" +"If your IdP doesn't support XML import, you will have to configure Zammad as " +"a new client/app manually using the above XML metadata file for reference." msgstr "" -#: ../system/core-workflows/limitations.rst:16 -msgid "hide" +#: ../settings/security/third-party/saml.rst:36 +msgid "For instance, when you see this tag:" msgstr "" -#: ../system/core-workflows/limitations.rst:25 -msgid "Some fields stay unavailable to customers" +#: ../settings/security/third-party/saml.rst:42 +msgid "" +"Set the **Assertion Consumer Service Binding URL** (sometimes also listed as " +"**Valid Redirect URIs**) to ``http://your.zammad.domain/auth/saml/callback``." msgstr "" -#: ../system/core-workflows/limitations.rst:19 -msgid "" -"For technical and security reasons, some default fields (the pale ones you " -"can't edit) stay unavailable for display and usage on customer permissions." +#: ../settings/security/third-party/saml.rst:47 +msgid "Set Up User Attribute Mapping" msgstr "" -#: ../system/core-workflows/limitations.rst:23 +#: ../settings/security/third-party/saml.rst:49 msgid "" -"If you require your customers to change e.g. priorities, please consider " -"using workarounds via :doc:`/system/objects` and :doc:`/manage/trigger`." +"Zammad requests the following user attributes (or “properties”) from the IdP:" msgstr "" -#: ../system/core-workflows/limitations.rst:29 -msgid "Ticket title changes not supported in edit mask" +#: ../settings/security/third-party/saml.rst:51 +msgid "Email address (``email``)" msgstr "" -#: ../system/core-workflows/limitations.rst:28 -msgid "" -"It is currently not possible to perform changes of the ticket title in the " -"edit mask (e.g. renaming, set to read-only)." +#: ../settings/security/third-party/saml.rst:52 +msgid "Full name (``name``)" msgstr "" -#: ../system/core-workflows/limitations.rst:37 -msgid "What is out of scope of Core Workflows?" +#: ../settings/security/third-party/saml.rst:53 +msgid "Given name (``first_name``)" msgstr "" -#: ../system/core-workflows/limitations.rst:32 -msgid "" -"There are some things that would count as workflow but are either done via :" -"doc:`/manage/trigger` or :doc:`/manage/scheduler`." +#: ../settings/security/third-party/saml.rst:54 +msgid "Family name (``last_name``)" msgstr "" -#: ../system/core-workflows/limitations.rst:35 -msgid "Such as (but not limited to):" +#: ../settings/security/third-party/saml.rst:56 +msgid "" +"You may need to set up “mappers” (or “mappings”) to tell your IdP how user " +"attributes in SAML correspond to those in Zammad. For a more detailed " +"breakdown, refer to the XML metadata file referenced in the previous section." msgstr "" -#: ../system/core-workflows/limitations.rst:37 -msgid "up- or downgrade permissions of users" +#: ../settings/security/third-party/saml.rst:62 +msgid "Per-IdP Instructions" msgstr "" -#: ../system/core-workflows/limitations.rst:38 -msgid "affecting article creation or listing" +#: ../settings/security/third-party/saml.rst:102 +msgid "Keycloak" msgstr "" -#: ../system/data-privacy.rst:2 -msgid "Data Privacy" +#: ../settings/security/third-party/saml.rst:65 +msgid "" +"**To add Zammad as a client,** save the XML configuration to disk (``https://" +"your.zammad.domain/auth/saml/metadata``) and use **Clients > Clients list > " +"Import client** in the Keycloak admin panel." msgstr "" -#: ../system/data-privacy.rst:4 +#: ../settings/security/third-party/saml.rst:70 msgid "" -"For compliance with GDPR and other data privacy laws, you may wish to " -"**permanently delete users from the system**, along with **all of their " -"associated tickets**." +"To help Zammad **match its own user accounts to Keycloak users**, create a " +"user attribute (or “property”) mapper. In **Clients list**, click on your " +"newly created Client ID, choose the tab **Client scopes** and click on the " +"link which refers to your Zammad instance. Choose **Add mapper > By " +"configuration > User Property** and create a mapper with the following " +"entries:" 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 `!" +#: ../settings/security/third-party/saml.rst:78 +msgid "**Name**" msgstr "" -#: ../system/data-privacy.rst:12 -msgid "" -"Access to this panel requires ``admin.data_privacy`` permissions (introduced " -"in Zammad 3.5)." +#: ../settings/security/third-party/saml.rst:80 +msgid "**Mapper Type**" msgstr "" -#: ../system/data-privacy.rst:15 -msgid "" -"On older systems that have not been updated yet, customers can also be :docs:" -"`deleted via the Zammad console `." +#: ../settings/security/third-party/saml.rst:81 +msgid "``User Property``" msgstr "" -#: ../system/data-privacy.rst:22 -msgid "User deletion dialog in the Data Privacy panel" +#: ../settings/security/third-party/saml.rst:82 +msgid "**Property**" msgstr "" -#: ../system/data-privacy.rst:22 -msgid "" -"The user deletion dialog lists some of the tickets that will be removed from " -"the system along with the user." +#: ../settings/security/third-party/saml.rst:83 +msgid "``emailAddress``" msgstr "" -#: ../system/data-privacy.rst:27 -msgid "Deleting Users via GUI" +#: ../settings/security/third-party/saml.rst:84 +msgid "**SAML Attribute Name**" msgstr "" -#: ../system/data-privacy.rst:29 -msgid "🔥 **All deletions are FINAL!**" +#: ../settings/security/third-party/saml.rst:86 +msgid "**SAML Attribute NameFormat**" msgstr "" -#: ../system/data-privacy.rst:31 -msgid "Once you click “Delete”, the action cannot be canceled or undone." +#: ../settings/security/third-party/saml.rst:87 +msgid "``basic``" msgstr "" -#: ../system/data-privacy.rst:33 +#: ../settings/security/third-party/saml.rst:89 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." +"In the example above, we're telling Zammad that whenever it receives a SAML " +"login request, it should take the ``email`` property from Keycloak, look for " +"a Zammad user with the same ``email`` attribute, and create a new session " +"for that user." msgstr "" -#: ../system/data-privacy.rst:36 -msgid "**The following records cannot be deleted:**" +#: ../settings/security/third-party/saml.rst:95 +msgid "" +"If your Keycloak users' email addresses are stored on another property (*e." +"g.,* ``username``), adjust accordingly." msgstr "" -#: ../system/data-privacy.rst:38 -msgid "your own account" +#: ../settings/security/third-party/saml.rst:98 +msgid "" +"Back in **Settings**, enter the Client ID (``https://your.zammad.domain/auth/" +"saml/metadata``) in the field **Master SAML Processing URL**." msgstr "" -#: ../system/data-privacy.rst:39 -msgid "the system's last remaining administrator account" +#: ../settings/security/third-party/saml.rst:101 +msgid "You also need to enable **Sign assertions**." msgstr "" -#: ../system/data-privacy.rst:42 -msgid "Step 1: Find a User / Confirm Deletion" +#: ../settings/security/third-party/saml.rst:105 +msgid "Step 2: Configure Zammad" msgstr "" -#: ../system/data-privacy.rst:44 -msgid "There are three ways to access the user deletion dialog:" +#: ../settings/security/third-party/saml.rst:107 +msgid "" +"Enable SAML and enter your IdP's details in the Admin Panel under **Settings " +"> Security > Third Party Applications > Authentication via SAML**:" msgstr "" -#: ../system/data-privacy.rst:51 -msgid "**from the user's profile**" +#: ../settings/security/third-party/saml.rst:None +msgid "Example configuration of SAML part 1" msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Accessing the user deletion dialog in a user profile" +#: ../settings/security/third-party/saml.rst:119 +msgid "Display name" msgstr "" -#: ../system/data-privacy.rst:51 -msgid "Click **Action > Delete**." +#: ../settings/security/third-party/saml.rst:116 +msgid "" +"Allows you to define a custom button name for SAML. This helps your users to " +"understand better what the button on the login page does." msgstr "" -#: ../system/data-privacy.rst:58 -msgid "**in the “Manage > Users” Admin Panel**" +#: ../settings/security/third-party/saml.rst:119 +msgid "Defaults to ``SAML``." msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Accessing the user deletion dialog under “Users” in the Admin Panel" +#: ../settings/security/third-party/saml.rst:123 +msgid "IDP SSO target URL" msgstr "" -#: ../system/data-privacy.rst:58 -msgid "Use the **⋮ Actions** menu for the target user." +#: ../settings/security/third-party/saml.rst:122 +msgid "" +"This is the target URL Zammad shall redirect to when the user presses the " +"SAML button. For Keycloak, this needs to look like https://your.domain/" +"realms/your-realm/protocol/saml" msgstr "" -#: ../system/data-privacy.rst:66 ../system/data-privacy.rst:104 -msgid "**in the “System > Data Privacy” Admin Panel**" +#: ../settings/security/third-party/saml.rst:127 +msgid "IDP single logout target URL" msgstr "" -#: ../system/data-privacy.rst:0 +#: ../settings/security/third-party/saml.rst:126 msgid "" -"Accessing the user deletion dialog under “Data Privacy” in the Admin Panel" +"This is the URL to which the single logout request and response should be " +"sent." msgstr "" -#: ../system/data-privacy.rst:65 +#: ../settings/security/third-party/saml.rst:131 +msgid "IDP certificate" +msgstr "" + +#: ../settings/security/third-party/saml.rst:130 msgid "" -"Use the **New Deletion Task** button. Search for users by name or email " -"address." +"The public certificate of your IDP for Zammad to verify during the callback " +"phase." msgstr "" -#: ../system/data-privacy.rst:79 -msgid "**Delete organizations**" +#: ../settings/security/third-party/saml.rst:145 +msgid "IDP certificate fingerprint" msgstr "" -#: ../system/data-privacy.rst:69 +#: ../settings/security/third-party/saml.rst:134 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:" +"The fingerprint of your IDPs public certificate to verify during callback " +"phase." msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Deleting an organization via the user deletion dialog" +#: ../settings/security/third-party/saml.rst:137 +msgid "🔏 **For the IdP certificate / certificate fingerprint:**" msgstr "" -#: ../system/data-privacy.rst:78 +#: ../settings/security/third-party/saml.rst:139 msgid "" -"If this option does not appear, make sure there are no pending deletion " -"tasks for other customers from this organization." +"Provide **only one or the other**—do not provide both! (Between the two, we " +"recommend the signing certificate itself: fingerprints use SHA-1, which `has " +"been broken for a while now `_.)" msgstr "" -#: ../system/data-privacy.rst:82 -msgid "Step 2: Monitor Deletion Job Status" +#: ../settings/security/third-party/saml.rst:144 +msgid "" +"**Keycloak users:** Find your certificate in the Keycloak admin panel under " +"**Realm Settings > Keys > Algorithm: RS256 > Certificate**." msgstr "" -#: ../system/data-privacy.rst:84 +#: ../settings/security/third-party/saml.rst:151 +msgid "Name identifier format" +msgstr "" + +#: ../settings/security/third-party/saml.rst:148 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:" +"This is the unique identifiers field type. Usually it should be ``urn:oasis:" +"names:tc:SAML:1.1:nameid-format:emailAddress``." msgstr "" -#: ../system/data-privacy.rst:98 -msgid "**in the Activity Stream**" +#: ../settings/security/third-party/saml.rst:151 +msgid "Zammad **expects an email address as unique identifier**!" msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Activity Stream showing data privacy tasks" +#: ../settings/security/third-party/saml.rst:155 +msgid "UID attribute name" msgstr "" -#: ../system/data-privacy.rst:94 +#: ../settings/security/third-party/saml.rst:154 msgid "" -"For each deleted user, the Activity Stream will be updated twice—once when " -"the task is created, and once when it's complete." +"Here you can define an attribute that uniquely identifies the user. If " +"unset, the name identifier returned by the IDP is used." msgstr "" -#: ../system/data-privacy.rst:97 -msgid "" -"These notifications are only visible to users with ``admin.data_privacy`` " -"permissions." +#: ../settings/security/third-party/saml.rst:None +msgid "Example configuration of SAML part 2" msgstr "" -#: ../system/data-privacy.rst:0 +#: ../settings/security/third-party/saml.rst:163 msgid "" -"The task list within Data Privacy shows removals being in progress and " -"completed." +"Decide if the certificate for the connection to the IdP service has to be " +"verified or not (default: ``yes``)." msgstr "" -#: ../system/data-privacy.rst:107 -msgid "Frequently Asked Questions" +#: ../settings/security/third-party/saml.rst:169 +msgid "Signing & Encrypting" msgstr "" -#: ../system/data-privacy.rst:121 -msgid "What happens if I receive an email from a deleted customer?" -msgstr "" - -#: ../system/data-privacy.rst:110 +#: ../settings/security/third-party/saml.rst:169 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." +"Define if you want to sign, encrypt, do both or nothing for the requests." msgstr "" -#: ../system/data-privacy.rst:115 -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**." +#: ../settings/security/third-party/saml.rst:179 +msgid "Certificate (PEM)" msgstr "" -#: ../system/data-privacy.rst:130 -msgid "What about user information stored in internal notes or other messages?" +#: ../settings/security/third-party/saml.rst:172 +msgid "" +"Paste the public certificate of your Zammad SAML client, if you want to " +"encrypt the requests." msgstr "" -#: ../system/data-privacy.rst:124 -msgid "" -"The deletion process removes **user accounts and associated tickets only**." +#: ../settings/security/third-party/saml.rst:175 +msgid "Make sure the certificate is:" msgstr "" -#: ../system/data-privacy.rst:126 -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." +#: ../settings/security/third-party/saml.rst:177 +msgid "already valid and not yet expired" msgstr "" -#: ../system/data-privacy.rst:137 -msgid "I deleted an user and can still see a message they sent!" +#: ../settings/security/third-party/saml.rst:178 +msgid "no CA certificate" msgstr "" -#: ../system/data-privacy.rst:133 -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." +#: ../settings/security/third-party/saml.rst:179 +msgid "valid for signing and encrypting" msgstr "" -#: ../system/data-privacy.rst:141 -msgid "I removed a customer, now my reporting is off!" +#: ../settings/security/third-party/saml.rst:185 +msgid "Private key (PEM)" msgstr "" -#: ../system/data-privacy.rst:140 +#: ../settings/security/third-party/saml.rst:182 msgid "" -"When removing users and their tickets, all references are removed. This also " -"affects e.g. Reporting - these information are lost." +"Paste the private key of your Zammad SAML client here, if you want to sign " +"the requests." msgstr "" -#: ../system/data-privacy.rst:145 -msgid "How long does Zammad store created tasks?" +#: ../settings/security/third-party/saml.rst:185 +msgid "Make sure the key is an RSA key with a length of at least 2048 bits." msgstr "" -#: ../system/data-privacy.rst:144 -msgid "" -"Please see the on-premise data section of the :docs:`data privacy ` chapter." +#: ../settings/security/third-party/saml.rst:188 +msgid "Private key secret" msgstr "" -#: ../system/data-privacy.rst:150 -msgid "What about re-assigned tickets? I want to delete them, too." +#: ../settings/security/third-party/saml.rst:188 +msgid "If your private key is secured with a secret, you can provide it here." msgstr "" -#: ../system/data-privacy.rst:148 -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." +#: ../settings/security/third-party/saml.rst:192 +msgid "Your callback URL" msgstr "" -#: ../system/data-privacy.rst:154 -msgid "Why are there so many deletion task entries, I didn't create them!" +#: ../settings/security/third-party/saml.rst:191 +msgid "" +"This URL is needed for your IdP configuration so it knows where to redirect " +"to after successful authentication." msgstr "" -#: ../system/data-privacy.rst:153 +#: ../settings/security/third-party/saml.rst:194 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." +"After saving your input by clicking on the \"Submit\" button, Zammad " +"verifies the provided keys/certificates (e.g. if they are valid for signing/" +"encrypting and if they aren't expired)." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:2 -msgid "Admin Panel Reference" +#: ../settings/security/third-party/saml.rst:199 +msgid "" +"See :ref:`automatic account linking ` for details " +"on how to link existing Zammad accounts to IdP accounts." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:None -msgid "Screenshot of Checkmk settings overview" +#: ../settings/security/third-party/saml.rst:205 +msgid "Automatic account linking doesn't work" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:12 +#: ../settings/security/third-party/saml.rst:206 msgid "" -"Which :doc:`group ` should Checkmk tickets be assigned " -"to as a default (*i.e.,* when none is specified)?" +"Have you double-checked your IdP's user attribute mapping configuration?" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:15 -msgid "(Applies to :ref:`API alerts ` only.)" +#: ../settings/security/third-party/twitter.rst:4 +msgid "" +"It is possible to create a quick login for your helpdesk via Twitter. To do " +"so, you need to follow these steps:" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:21 -msgid "Auto close" +#: ../settings/security/third-party/twitter.rst:8 +msgid "Register Twitter App" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:18 -msgid "" -"Should Zammad automatically close tickets if a service has recovered on its " -"own?" +#: ../settings/security/third-party/twitter.rst:10 +msgid "Go to https://dev.twitter.com/apps and login with your account." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:21 -msgid "(Agents will receive notifications for such closures as appropriate.)" +#: ../settings/security/third-party/twitter.rst:15 +msgid "Click on \"Create App\"" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:30 -msgid "Auto-close state" +#: ../settings/security/third-party/twitter.rst:None +msgid "new app page" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:24 -msgid "What ticket state should be applied when “auto-closing” a ticket?" +#: ../settings/security/third-party/twitter.rst:20 +msgid "" +"Enter app settings. As \"Callback URL\" you need to enter ``https://" +"zammad_host/api/v1/external_credentials/twitter/callback``. You need to " +"replace ``zammad_host`` with the domain of your Zammad system." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:26 +#: ../settings/security/third-party/twitter.rst:24 msgid "" -"You can choose from the seven built-in ticket states. If these states aren't " -"enough for you, you can :ref:`define a new ticket state ` for this purpose as well. This can be useful for tracking " -"tickets with :doc:`reports `, for example." +"After the app has been created, update the application icon and organization " +"attributes." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:35 -#: ../system/integrations/cti/includes/recent-logs.include.rst:2 -#: ../system/integrations/ldap/index.rst:74 -#: ../system/integrations/pgp/index.rst:106 -msgid "Recent Logs" +#: ../settings/security/third-party/twitter.rst:None +msgid "set permissions to receive and send direct messages" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:None -msgid "Screenshot of Checkmk \"Recent Logs\" section" +#: ../settings/security/third-party/twitter.rst:30 +msgid "" +"Next we need to set ``read, write and access direct messages`` permissions " +"for the app." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:41 -msgid "" -"If you're having trouble getting Zammad and Checkmk to play nicely together, " -"this section can help you troubleshoot." +#: ../settings/security/third-party/twitter.rst:None +msgid "click on Keys & Access Token, note them" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:44 +#: ../settings/security/third-party/twitter.rst:36 msgid "" -"It contains a record of the fifty most recent transactions that Zammad knows " -"about, including each one's request/response details and return status." +"Go to \"Keys and Access Token\" tab and note the \"Consumer Key\" and " +"\"Consumer Secret\"." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:2 -msgid "API Reference" +#: ../settings/security/third-party/twitter.rst:40 +msgid "Configure Zammad as Twitter App" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:4 +#: ../settings/security/third-party/twitter.rst:42 msgid "" -"For most users, :ref:`the sample scripts from the Setup Guide ` will do the job just fine. But if you want more fine-grained control" -"—for instance, to create high- and low-priority tickets for different types " -"of system events—then you'll have to customize the data those scripts send " -"to Zammad." +"Go to \"Admin > Security > Twitter > Third Party Applications > Twitter\" " +"Section." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:15 -msgid "" -"This custom script will automatically set all tickets it creates to **high " -"priority** and **assign them to charlie@chrispresso.com**." +#: ../settings/security/third-party/twitter.rst:None +msgid "Admin > Security > Third Party Applications" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:32 -msgid "How Does it Work?" +#: ../settings/security/third-party/twitter.rst:48 +msgid "" +"Fill in the \"Twitter Key\" and the \"Twitter Secret\" and click the " +"\"Submit\" button." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:34 +#: ../settings/security/third-party/twitter.rst:51 msgid "" -"There are two kinds of data you can pass to the API, both in the form of key-" -"value pairs:" +"Now you can link accounts via \"Avatar > Profile > Link Accounts\" or login " +"via Zammad login page." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:44 -msgid "Checkmk parameters" +#: ../settings/security/two-factor.rst:11 +msgid "Two-factor Authentication Methods" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:38 -msgid "" -"are required, and make up the **contents** of the resulting tickets/" -"articles. They also determine whether an event creates a new ticket or " -"updates/closes an existing one." +#: ../settings/security/two-factor.rst:2 +msgid "Two-Factor Authentication" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:42 +#: ../settings/security/two-factor.rst:4 msgid "" -"These are the only values used in the sample scripts. **Use them as-is**; " -"technically, they can be customized, but it's hard to imagine a good reason " -"for it." -msgstr "" - -#: ../system/integrations/checkmk/api-reference.rst:52 -msgid "Ticket attributes" +"Two-factor authentication (2FA) enhances the security of Zammad accounts by " +"adding an extra layer of verification beyond a password. It requires users " +"to provide two different types of authentication factors, typically " +"something they know (like a password) and something they possess (like a " +"mobile device or a security token), to ensure that only authorized " +"individuals can access the account." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:47 -msgid "" -"are optional, and can be used to **adjust settings** on newly created " -"tickets (*e.g.,* set the owner, group, priority, or state)." +#: ../settings/security/two-factor.rst:19 +msgid "Enable Recovery Codes" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:50 +#: ../settings/security/two-factor.rst:21 msgid "" -"If you want to customize your Checkmk alert script, do it with these. Simply " -"add an extra “form” option for each one (``-F \"key=value\"``) to your " -"script's ``curl`` command line, as in the example above." +"Recovery codes are one-time use security codes that can be used by the user " +"if they lose access to their other two-factor authentication methods. They " +"cannot be used on their own, they can only be activated if at least one two-" +"factor authentication method is enabled." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:54 -msgid "💡 **It's just an API endpoint!**" +#: ../settings/security/two-factor.rst:None +msgid "Enable Recovery Codes Setting" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:56 +#: ../settings/security/two-factor.rst:30 msgid "" -"When using Checkmk integration, messages need to be formatted in a certain " -"way, but that *doesn't mean the messages actually have to come from Checkmk*." +"Recovery codes can only be used as a backup method. If enabled, they will be " +"automatically generated for the user once they set up their initial two-" +"factor authentication method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:59 +#: ../settings/security/two-factor.rst:34 msgid "" -"If you use another monitoring tool that's not officially supported by " -"Zammad, there's probably a way to make it work with your Checkmk callback " -"URL." -msgstr "" - -#: ../system/integrations/checkmk/api-reference.rst:63 -msgid "Checkmk Parameters" +"The user will be asked to print out or save the generated recovery codes in " +"a safe place. Once used, a recovery code cannot be reused." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:65 +#: ../settings/security/two-factor.rst:37 msgid "" -"When a notification is received, Zammad creates a new article containing the " -"details of the event that triggered it:" -msgstr "" - -#: ../system/integrations/checkmk/api-reference.rst:None -msgid "Checkmk article body" +"Users will also have an option to regenerate their recovery codes at any " +"time, which invalidates already existing recovery codes and provides them " +"with a list of fresh codes." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:72 +#: ../settings/security/two-factor.rst:41 msgid "" -"These details come from the fields listed below, which correspond to " -"parameters provided by Checkmk (``$NOTIFY_*``)." +"After you enable this setting, when the user completes a setup of their " +"initial two-factor authentication method, they will be presented with a list " +"of recovery codes and instructed to save them for later use." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:75 -msgid "**Required fields are marked with an asterisk (\\*).**" +#: ../settings/security/two-factor.rst:None +msgid "Recovery Codes Generation Modal Dialog" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:79 -msgid "event_id\\*" +#: ../settings/security/two-factor.rst:50 +msgid "Enforce the Set Up of the Two-Factor Authentication" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:78 +#: ../settings/security/two-factor.rst:52 msgid "" -"A unique ID for the system event. (``$NOTIFY_SERVICEPROBLEMID`` / " -"``$NOTIFY_HOSTPROBLEMID``)" +"In case you wish to require your users to set up at least one two-factor " +"authentication method for their account, you can do this by selecting " +"specific user roles the requirement applies to in **Enforced for user " +"roles** setting. Of course you must have at least one two-factor " +"authentication method enabled for this setting to take effect." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:86 -msgid "host\\*" +#: ../settings/security/two-factor.rst:None +msgid "Enforced for User Roles Setting" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:82 +#: ../settings/security/two-factor.rst:62 msgid "" -"The hostname of the system that the event originated from. " -"(``$NOTIFY_HOSTNAME``)" +"After you change this setting, if the user has one of the selected roles on " +"their account, they will be forced to set up the two-factor authentication " +"upon next sign in or application reload." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:85 +#: ../settings/security/two-factor.rst:66 msgid "" -"Used to determine if a new event belongs to an existing ticket. Also used in " -"the subject line of the resulting article (“ is ”)." +"A modal dialog with instructions will be shown, and they will not be able to " +"do any work before they set up at least one two-factor method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:96 -msgid "service" +#: ../settings/security/two-factor.rst:None +msgid "Modal Dialog for Enforcing Two-Factor Authentication Set Up" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:89 -msgid "" -"The name of the service that the event originated from. " -"(``$NOTIFY_SERVICEDESC``)" +#: ../settings/security/two-factor.rst:74 +msgid "Reset Two-Factor Authentication for a Specific User" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:92 -msgid "Used to determine if a new event belongs to an existing ticket." +#: ../settings/security/two-factor.rst:76 +msgid "" +"In case an user isn't able to login anymore because of an inaccessible " +"second factor, you can reset the user's 2FA method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:94 -#: ../system/integrations/checkmk/api-reference.rst:110 -msgid "Displayed as ``-`` when omitted." +#: ../settings/security/two-factor.rst:79 +msgid "" +"To do this, go to the user management and search for the relevant user. " +"After you found the account, click the button in the action column and " +"select \"Manage Two-Factor Authentication\":" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:104 -msgid "state\\*" +#: ../settings/security/two-factor.rst:None +msgid "Context menu in action column in user management" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:99 +#: ../settings/security/two-factor.rst:87 msgid "" -"The current state of the service or host in question. " -"(``$NOTIFY_SERVICESTATE`` / ``$NOTIFY_HOSTSTATE``)" +"After selecting this, you can see a dialog where you can either reset one " +"2FA method or reset all of the user's 2FA methods:" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:102 +#: ../settings/security/two-factor.rst:None +msgid "Dialog for resetting user's 2FA method" +msgstr "" + +#: ../settings/security/two-factor.rst:94 msgid "" -"Used to detect when a ticket should be auto-closed (*i.e.,* on ``OK``/" -"``UP``). Also used in the subject line of the resulting article (“ is " -"”)." +"Choose the fitting one, click on the corresponding \"Remove ...\" button and " +"confirm your action. The user now has to setup a new 2FA method, depending " +"on your 2FA configuration." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:110 -msgid "text" +#: ../settings/security/two-factor/authenticator-app.rst:2 +msgid "Authenticator App" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:107 +#: ../settings/security/two-factor/authenticator-app.rst:4 msgid "" -"The output of the process that triggered the event. " -"(``$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" +"The authenticator app method is a type of two-factor authentication that " +"uses a mobile application to generate one-time codes for account " +"verification. After setting up the authenticator app on their device, the " +"user links it to their Zammad account." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:121 +#: ../settings/security/two-factor/authenticator-app.rst:12 msgid "" -"The Object Manager attribute panel displays built-in and custom\n" -"attribute names." +"When logging in, the user is prompted to enter a time-sensitive code " +"generated by the app, in addition to their password. This code acts as the " +"second factor of authentication, providing an extra layer of security as it " +"changes periodically and is unique to the user's device." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:121 -msgid "Find a complete list of ticket attributes in the Object Manager." +#: ../settings/security/two-factor/authenticator-app.rst:None +msgid "Security Code in Google Authenticator App" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:123 +#: ../settings/security/two-factor/authenticator-app.rst:22 msgid "" -"Ticket attributes are entirely optional, and can be used to customize the " -"tickets that Checkmk creates. (Note that these attributes will be ignored if " -"a new event belongs to an existing ticket.)" +"The app generates codes based on a shared secret key stored securely on both " +"the user's device and the server, ensuring a synchronized and secure " +"authentication process. The method of generating the codes is sometimes also " +"called TOTP (time-based one-time password)." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:128 -msgid "" -"Why would you want to do this? Maybe you have only one IT guy, and all " -"system monitoring issues should be automatically assigned to him. Or, maybe " -"you're creating multiple notification rules so that database outages take " -"higher priority than disk space warnings." +#: ../settings/security/two-factor/authenticator-app.rst:28 +msgid "Enabling the Authenticator App Method" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:135 -msgid "In most cases, you'll probably want to set one of the following:" +#: ../settings/security/two-factor/authenticator-app.rst:30 +#: ../settings/security/two-factor/security-keys.rst:28 +msgid "To enable the method, just toggle the switch on in the settings." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:137 -msgid "group" -msgstr "grupp" - -#: ../system/integrations/checkmk/api-reference.rst:139 -msgid "state" +#: ../settings/security/two-factor/authenticator-app.rst:None +msgid "Authenticator App Switch in Settings" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:140 -msgid "priority" -msgstr "prioritet" - -#: ../system/integrations/checkmk/api-reference.rst:142 +#: ../settings/security/two-factor/authenticator-app.rst:36 msgid "" -"but in practice, you can set almost any attribute, including :doc:`custom " -"ones you created through the Object Manager `." +"Now the users will be able to set up this two-factor authentication method " +"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " +"Once they do, on next sign-in with password, they will be asked to provide " +"an additional security code generated by their mobile device." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:145 -msgid "Please note that the following attributes are **not customizable**:" +#: ../settings/security/two-factor/security-keys.rst:2 +msgid "Security Keys" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:147 -msgid "title" -msgstr "ämne" +#: ../settings/security/two-factor/security-keys.rst:4 +msgid "" +"The security keys method is a type of a two-factor authentication that uses " +"Web Authentication API in the browser for verifying user's identity. The " +"user can register multiple hardware or software security keys with their " +"Zammad account and then they can use it during the sign-in process." +msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:148 -msgid "id" +#: ../settings/security/two-factor/security-keys.rst:12 +msgid "" +"When logging in, the user is prompted to provide the same security key they " +"registered with their account, in addition to their password. This key acts " +"as the second factor of authentication, providing an extra layer of security." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:149 -msgid "ticket number" +#: ../settings/security/two-factor/security-keys.rst:None +msgid "Security Key dialog in Safari on macOS" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:151 -msgid "created_by_id" +#: ../settings/security/two-factor/security-keys.rst:21 +msgid "" +"The type of the key can range from hardware USB sticks to passkeys stored in " +"a device of user's choice. Which type can be used depends on the browser " +"flavor and the platform of the user." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:152 -msgid "updated_by_id" +#: ../settings/security/two-factor/security-keys.rst:26 +msgid "Enabling the Security Keys Method" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:155 -msgid "Which Values Can Be Set?" +#: ../settings/security/two-factor/security-keys.rst:None +msgid "Security Keys Switch in Settings" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:157 -msgid "😵 **Invalid values → unpredictable behavior**" +#: ../settings/security/two-factor/security-keys.rst:34 +msgid "" +"Now the users will be able to set up this two-factor authentication method " +"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " +"Once they do, on next sign-in with password, they will be asked to provide " +"the same security key they registered during the setup." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:159 +#: ../settings/system/system-selfhosted.include.rst:3 msgid "" -"If you provide a value that Zammad doesn't understand (*e.g.,* ``-F " -"\"priority=high\"``), it's not always clear what will happen. In some cases, " -"a ticket will be created with the default values instead - but in others, it " -"may not be created at all!" +"Below settings are only available to self hosted users. In hosted " +"environments we're handling these settings for you to ensure service " +"stability." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:164 -msgid "So what values does Zammad understand, then? Well, it depends..." +#: ../settings/system/base.rst:11 +msgid "Fully Qualified Domain Name" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:168 -msgid "Use an email address or username:" +#: ../settings/system/base.rst:7 +msgid "The URL of your Zammad installation." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:190 -msgid "group & priority" +#: ../settings/system/base.rst:9 ../settings/system/base.rst:17 +msgid "This setting is used within :doc:`/misc/variables` and notifications." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:175 -msgid "Refer to the dropdown menus in the ticket pane:" +#: ../settings/system/system-base.include.rst:1 +msgid "It is automatically set by the *Getting Started wizard*." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:0 -msgid "See possible values for certain attributes in the ticket pane." +#: ../settings/system/system-base.include.rst:5 +msgid "Changing this setting also changes callback URLs for your channels etc." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:187 -msgid "🙅 **Ticket state CANNOT be set this way!**" +#: ../settings/system/system-base.include.rst:6 +msgid "This setting can have negative affects on being able to login." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:189 -msgid "" -"Why? Because ``-F \"state=...\"`` is already used :ref:`as a Checkmk " -"parameter `." -msgstr "" - -#: ../system/integrations/checkmk/api-reference.rst:222 -msgid "Everything Else" +#: ../settings/system/base.rst:19 +msgid "HTTP type" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:193 +#: ../settings/system/base.rst:14 msgid "" -"To set any other attributes, it helps to know your way around the :docs:" -"`rails console `. Valid values are those that you can " -"set with a string:" +"The HTTP type tells your installation how your clients connect. This is " +"relevant for authentication and cookie security." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:218 -msgid "These values can then be passed directly to the API:" +#: ../settings/system/base.rst:31 +msgid "SystemID" msgstr "" -#: ../system/integrations/checkmk/index.rst:16 -msgid "How does it work?" +#: ../settings/system/base.rst:22 +msgid "" +"This ID is being used within your ticket number. In case you're " +"communicating with another ticket system with similar ticket number schemes " +"this ID greatly reduces the risk of false follow ups." msgstr "" -#: ../system/integrations/checkmk/index.rst:2 -msgid "Checkmk" +#: ../settings/system/base.rst:26 +msgid "" +"The SystemID is randomly selected upon installation of Zammad (``1-99``)." msgstr "" -#: ../system/integrations/checkmk/index.rst:4 +#: ../settings/system/base.rst:30 msgid "" -"`Checkmk `_ is a powerful IT monitoring tool that can " -"send real-time status alerts to Zammad via email or REST API. Set these " -"alerts up in Checkmk, and Zammad will automatically create, update, and " -"close tickets based on the health of your system:" +"**Do not** change this setting in a productive system! Your Zammad " +"installation may no longer recognize old ticket number based follow ups upon " +"change!" msgstr "" -#: ../system/integrations/checkmk/index.rst:14 -msgid "Screenshot of ticket created by Checkmk notifications" +#: ../settings/system/frontend.rst:2 +msgid "Frontend" msgstr "" -#: ../system/integrations/checkmk/index.rst:14 -msgid "Multiple alerts, same ticket." +#: ../settings/system/frontend.rst:22 +msgid "Core Workflow Ajax Mode" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:2 -msgid "Setup Guide" +#: ../settings/system/frontend.rst:6 +msgid "" +"This setting allows administrators to enforce :doc:`/system/core-workflows` " +"to use Ajax-Calls instead of web sockets. You'll usually only need this if " +"you experience serious issues as noted below." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:4 -msgid "" -"Whenever the Checkmk integration is enabled, Zammad listens for messages on " -"its API and over email. As long as those messages follow the required " -"format, Zammad will create new tickets (or find and update existing ones) " -"based on the message contents." +#: ../settings/system/frontend.rst:10 +msgid "**🤓 Possible (technical) reasons**" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:10 +#: ../settings/system/frontend.rst:12 msgid "" -"That means that “setting up Checkmk integration” is simply a matter of " -"**adding configuration to your Checkmk site**: telling it when to send these " -"messages and what to say. To do that, you'll need to create a new " -"**notification rule** (see `Checkmk's official docs `_ for help with that)." +"In some cases, your network structure (e.g. firewalls, proxies) may " +"disconnect long web socket connections. This leads to select fields staying " +"empty (e.g. owner selection *after* selecting your group) or fields not " +"shown / hidden (e.g. when switching to or from pending states, the \"pending " +"till\" field not showing / hiding)." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:17 +#: ../settings/system/frontend.rst:18 msgid "" -"As part of this new rule, you'll have to choose a **notification method** " -"(*i.e.,* a script to execute whenever the rule is triggered). This script " -"will be written by you (samples below), and contain the logic for sending " -"API/email messages to Zammad:" +"Please keep in mind that the Ajax fallback may cause serious pressure on " +"your application server. If you have the choice stick to web sockets." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:26 -msgid "Checkmk \"New Rule\" dialog" +#: ../settings/system/frontend.rst:22 +msgid "Default: ``no`` (inactive)" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:26 -msgid "" -"Find your custom scripts in the Checkmk WATO under **Notifications > New " -"Rule > Notification Method**." +#: ../settings/system/frontend.rst:53 +msgid "Show calendar weeks in the picker of date/datetime fields" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:29 +#: ../settings/system/frontend.rst:25 msgid "" -"Once you're done setting up your new rule, you're all set! New tickets " -"should start coming in and auto-updating any time your rule is triggered." +"With this setting you can instruct Zammad to provide week number display " +"globally for all users. Calendar with week number display are usually used " +"in business sectors and may not be relevant for everyone." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:33 +#: ../settings/system/frontend.rst:29 msgid "" -"(If you need help troubleshooting, be sure to check the :ref:`checkmk-recent-" -"logs`.)" +"This setting affects *all areas* - you'll also see week numbers in the admin " +"panel for e.g. triggers and macros." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:38 -msgid "API Alerts" +#: ../settings/system/frontend.rst:32 +msgid "Default: ``no`` (not shown)" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:40 -msgid "" -"To add these scripts in the Checkmk WATO, copy them into your Checkmk " -"installation directory and make them executable. (Be sure to replace the " -"``zammad.example.com`` callback URL with the one found in your admin panel.)" +#: ../settings/system/frontend.rst:53 +msgid "Here's the difference:" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:60 -msgid "Service notification" +#: ../settings/system/frontend.rst:0 +msgid "Screenshot showing Zammad's date picker (in the default way)" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:46 +#: ../settings/system/frontend.rst:41 +msgid "Set to ``no``" +msgstr "" + +#: ../settings/system/frontend.rst:0 msgid "" -"For updates on the status of the software running on your server (*e.g.,* " -"postgres)." +"Screenshot showing Zammad's date picker with\n" +"week numbers enabled" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:75 -msgid "Host notification" +#: ../settings/system/frontend.rst:50 +msgid "Set to ``yes``" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:63 -msgid "For updates on the status of the server itself." +#: ../settings/system/index.rst:4 +msgid "" +"For your overview we split each tab within system settings into its own page:" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:77 -msgid "🤔 **What's with all the env vars?**" +#: ../settings/system/index.rst:16 +msgid "Console Based Settings" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:79 +#: ../settings/system/index.rst:18 msgid "" -"Whenever Checkmk runs these scripts, it needs to provide some information " -"about the event that triggered the notification. This information is passed " -"in the form of these ``$NOTIFY_*`` environment variables." +"There's some console based settings we didn't put into the UI. However, you " +"may find them helpful - you can find them in our :docs:`hidden settings ` section." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:85 +#: ../settings/system/network.rst:2 +msgid "Network" +msgstr "" + +#: ../settings/system/network.rst:8 msgid "" -"You can specify additional parameters to pass to the script when you're " -"setting up your notification rule, but the ones you see here are all " -"provided by default." +"The proxy settings can only be saved after successfully testing the proxy " +"connection." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:90 -msgid "Email Alerts" +#: ../settings/system/network.rst:15 +msgid "Proxy Address." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:94 +#: ../settings/system/network.rst:12 msgid "" -"🐞 **There are known bugs** in Zammad's processing of email from Checkmk. " -"This section will be completed once they have been resolved. (Learn more at " -"GitHub issues `#2377 `_ & " -"`#2180 `_.)" +"Allows you to provide a proxy server if needed. This is relevant for network " +"communication by Zammad." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:100 -msgid "In the meantime, we encourage you to set up API alerts instead." +#: ../settings/system/network.rst:15 +msgid "It **does not** affect the update process or Elasticsearch." msgstr "" -#: ../system/integrations/clearbit.rst:2 -msgid "Clearbit" +#: ../settings/system/network.rst:18 +msgid "Username for proxy connection." msgstr "" -#: ../system/integrations/clearbit.rst:4 +#: ../settings/system/network.rst:18 msgid "" -"With our Clearbit integration, you can easily enrich the information " -"provided by Zammad. If the customers or agents email address is known to " -"Clearbit, it will share all information it has regarding the user with " -"Zammad. Those information can include the following:" +"If your proxy server requires authentication, provide the username here." msgstr "" -#: ../system/integrations/clearbit.rst:9 -msgid "Avatar" +#: ../settings/system/network.rst:21 +msgid "Password for proxy connection." msgstr "" -#: ../system/integrations/clearbit.rst:10 -msgid "Address information" +#: ../settings/system/network.rst:21 +msgid "" +"If your proxy server requires authentication, provide the password here." msgstr "" -#: ../system/integrations/clearbit.rst:11 -msgid "Website information" +#: ../settings/system/network.rst:26 +msgid "No proxy for the following hosts." msgstr "" -#: ../system/integrations/clearbit.rst:12 -msgid "A BIO (as Note by default)" +#: ../settings/system/network.rst:24 +msgid "" +"Exception list for hosts you can't or don't want to reach via proxy server." msgstr "" -#: ../system/integrations/clearbit.rst:14 -msgid "" -"If needed, you can add further custom objects and add mappings to them, so " -"the Clearbit information can be filled within the database. In general you " -"can get any information from Clearbit, as long as you have a mapping to an " -"Zammad object." +#: ../settings/system/network.rst:27 +msgid "Default: ``localhost,127.0.0.0,::1``" msgstr "" -#: ../system/integrations/clearbit.rst:21 -msgid "" -"Clearbit does have a mapping of fields like LDAP and Exchange have, but does " -"not \"win\" against Zammad information. This means that if you have e.g. the " -"last name field filled in already and Clearbit has other information on " -"that, it will not be updated." +#: ../settings/system/services.rst:2 +msgid "Services" msgstr "" -#: ../system/integrations/clearbit.rst:26 -msgid "" -"However: If let's say the last name has been set by Clearbit and Zammad " -"notices that the last name on the Clearbit source has changed, Zammad will " -"also update this value." +#: ../settings/system/services.rst:10 +msgid "Image Service" msgstr "" -#: ../system/integrations/clearbit.rst:33 -msgid "" -"The configuration of Clearbit is really easy and done fast! Just login to " -"your Clearbit-Account, go to \"API\" and copy the secret-API-Key." +#: ../settings/system/services.rst:5 +msgid "Defines the backend for user and organization image lookups." msgstr "" -#: ../system/integrations/clearbit.rst:38 -msgid "" -"Now change to your Zammad instance, go to Integrations (System) -> Clearbit " -"in the admin panel. Paste your API-Key into the API-Key-Field and decide if " -"Zammad should create unknown Organizations automatically, if the user does " -"not have one yet (and Clearbit knows it). The shared option decides if the " -"new organizations Zammad creates with Clearbit should be shared ones." +#: ../settings/system/services.rst:7 +msgid "Default: ``Zammad Image Service`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:47 +#: ../settings/system/services.rst:9 msgid "" -"If you're unsure what option to choose, better stick with \"no\". You can " -"also learn more about :doc:`/manage/organizations/index`." +"Make sure your on premise installation has ``HTTPS`` access to ``images." +"zammad.com``." msgstr "" -#: ../system/integrations/clearbit.rst:52 -msgid "" -"The Mapping option works similar to the mapping within the Exchange and LDAP " -"sync. You can add further mappings for e.g. custom fields if you need more " -"information that Clearbit can provide." +#: ../settings/system/services.rst:18 +msgid "Geo Calendar Service" msgstr "" -#: ../system/integrations/clearbit.rst:58 +#: ../settings/system/services.rst:13 msgid "" -"If you want to add more Clearbit fields and want to learn more about " -"available fields on their API, you can take a look at their `API " -"documentation `_." +"Defines the backend for geo calendar lookups. Used for initial calendar " +"setup." msgstr "" -#: ../system/integrations/clearbit.rst:62 -msgid "" -"If you're happy with the above chosen Settings and your mapping, just save " -"the changes and enable Clearbit integration. Zammad will now start polling " -"the Clearbit API as users contact you." +#: ../settings/system/services.rst:16 +msgid "Default: ``Zammad GeoCalendar Service`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:68 +#: ../settings/system/services.include.rst:2 msgid "" -"Zammad does not synchronize with Clearbit on a regular basis, but on demand " -"if needed. This saves API calls." +"Make sure your on premise installation has ``HTTPS`` access to ``geo.zammad." +"com``." msgstr "" -#: ../system/integrations/clearbit.rst:73 -msgid "" -"Below the Settings and Mappings, you'll find our Integration log. You can " -"see what requests Zammad sent to Clearbit and also the APIs Response." +#: ../settings/system/services.rst:26 +msgid "Geo IP Service" msgstr "" -#: ../system/integrations/clearbit.rst:78 +#: ../settings/system/services.rst:21 msgid "" -"By the way, you can also view the API log on the Clearbit website - the " -"information seen is basically the same." +"Defines the backend for geo IP lookups. Shows also location of an IP address " +"if an IP address is shown." msgstr "" -#: ../system/integrations/clearbit.rst:84 -msgid "Example When Adding a User" +#: ../settings/system/services.rst:24 +msgid "Default: ``Zammad GeoIP Service`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:86 -msgid "" -"To show you how fast information is added, we added a small Screencast " -"below. This shows the creation of the User Alex from Clearbit. As we already " -"set the last name of Alex to \"X\", Zammad did not update it. What Zammad " -"did was to add further information it received from Clearbit." +#: ../settings/system/services.rst:32 +msgid "Geo Location Service" msgstr "" -#: ../system/integrations/cti/generic.rst:2 -msgid "CTI (generic)" +#: ../settings/system/services.rst:29 +msgid "" +"Defines the backend for geo location lookups to store geo locations for " +"addresses." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:1 +#: ../settings/system/services.rst:32 msgid "" -"This integration enables Zammad to provide a caller log to your agents. With " -"this your agents can greet your customers by their name and are supported by " -"Zammad with automatically opening a new ticket dialog or the user profile." +"Default: ``OpenStreetMap (ODbL 1.0, http://osm.org/copyright)`` (active)" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:6 +#: ../settings/system/services.rst:36 msgid "" -"Click the toggle next to the heading to activate or deactivate this " -"integration." +"You can find a detailed privacy information on what we store for how long on " +"our :docs:`Privacy Appendix ` inside of our System " +"Documentation." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:9 +#: ../settings/system/storage.rst:2 +msgid "Storage" +msgstr "" + +#: ../settings/system/storage.rst:6 msgid "" -"If you want to learn more on how your agents can use this function, please " -"refer the :user-docs:`user documentation `." +"Here you can define where Zammad stores attachments for tickets and the " +"knowledge base. By default, we're writing to the ``Database`` - you can " +"switch to ``Filesystem`` or ``Simple Storage (S3)`` at any time. In this " +"case please have a look on the following instructions." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:14 +#: ../settings/system/storage.rst:11 msgid "" -"Automatically opening new ticket dialogues or user profiles requires agent " -"to extension mapping - see more below." +"If you have a busy Zammad instance, we strongly encourage you to use " +"filesystem storage instead of \"Database\". This will greatly improve system " +"performance (de-crease database load and size)." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:20 -msgid "Please note the following limitations to reduce confusion later on:" +#: ../settings/system/storage.rst:19 +msgid "Database" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:22 -msgid "CTI integrations provide caller log functions only." +#: ../settings/system/storage.rst:17 +msgid "" +"This is the default storage method. The attachments are stored directly in " +"the database. If your Zammad instance grows, we recommend one of the other " +"methods to maintain performance." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:23 +#: ../settings/system/storage.rst:38 +msgid "Filesystem" +msgstr "" + +#: ../settings/system/storage.rst:22 msgid "" -"This integration does not provide any VoIP functionalities; you can't make " -"phone calls from within Zammad." +"This storage method is recommended for all Zammad instances, especially for " +"those with a higher load. If you choose filesystem, your files are written " +"to ``/opt/zammad/storage/``." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:25 +#: ../settings/system/storage.rst:26 msgid "" -"If your browser supports ``tel``-URLs, you can click on phone numbers for " -"automatic dialing. This requires additional software / configuration on your " -"agent's computers." +"Moving attachments from \"Database\" to \"Filesystem\" can be run during " +"production use. However, you should consider your framework conditions (e.g. " +"bandwidth, system load in production) to define the right moment." msgstr "" -#: ../system/integrations/cti/generic.rst:9 -#: ../system/integrations/cti/placetel.rst:14 -#: ../system/integrations/cti/sipgate.rst:14 -msgid "Please provide the following requirements:" +#: ../settings/system/storage.rst:32 +msgid "**You noticed slow updates of Zammad?**" msgstr "" -#: ../system/integrations/cti/generic.rst:11 +#: ../settings/system/storage.rst:34 msgid "" -"A telephone system that supports webhooks (outbound) (best option are those " -"that allow customizing the calls)." +"While Zammad is beeing updated, it enforces a recursive \"change " +"owner\" (chown) for this directory. For instances with many files this can " +"be time consuming. To mitigate that you can move your files and create a " +"symlink in ``/opt/zammad/storage/`` to the new directory. Of course you have " +"to make sure on your own that the permissions are always correct." msgstr "" -#: ../system/integrations/cti/generic.rst:13 -msgid "A unique Call-ID during the call session." +#: ../settings/system/storage.rst:95 +msgid "Simple Storage (S3)" msgstr "" -#: ../system/integrations/cti/generic.rst:14 -msgid "Call event data (both numbers and direction)." +#: ../settings/system/storage.rst:41 +msgid "" +"To use the Simple Storage (S3), you have to provide some settings, which " +"can't be accessed in the UI (see instructions below)." msgstr "" -#: ../system/integrations/cti/generic.rst:15 -msgid "Your Zammad instance must be reachable for your telephony system." +#: ../settings/system/storage.rst:44 +msgid "" +"⚠️ Please note that the current implementation is in its early stages and can " +"be modified in the future." msgstr "" -#: ../system/integrations/cti/generic.rst:17 +#: ../settings/system/storage.rst:47 msgid "" -"If you want to learn more on what kind of requests are supported by Zammad " -"and what it expects, please consult our :docs:`CTI-API documentation `." +"The prerequisite is to have access to a S3-compatible storage and to have " +"all necessary parameters available (which depends on your storage provider; " +"if in doubt, please ask there for help)." msgstr "" -#: ../system/integrations/cti/generic.rst:22 -#: ../system/integrations/cti/placetel.rst:27 -#: ../system/integrations/cti/sipgate.rst:30 -msgid "Available Settings" +#: ../settings/system/storage.rst:51 +msgid "Steps to configure S3:" msgstr "" -#: ../system/integrations/cti/generic.rst:29 -#: ../system/integrations/cti/placetel.rst:41 -#: ../system/integrations/cti/sipgate.rst:40 -msgid "Endpoint Settings" +#: ../settings/system/storage.rst:53 +msgid "" +"Copy ``config/zammad/storage.yml.dist`` to ``config/zammad/storage.yml``" msgstr "" -#: ../system/integrations/cti/generic.rst:25 -msgid "" -"Zammad will list your generic CTI endpoint here. It contains a unique token " -"so ensure to keep this URL save." +#: ../settings/system/storage.rst:54 +msgid "Edit the copied file in one of the following ways:" msgstr "" -#: ../system/integrations/cti/generic.rst:28 +#: ../settings/system/storage.rst:56 msgid "" -"You'll need this endpoint for your PBX to talk to Zammad, see :docs:`CTI-API " -"documentation `." +"Either provide your S3 configuration with one attribute per line like in the " +"upper area of the file" msgstr "" -#: ../system/integrations/cti/includes/important-dont-forget-saving.include.rst:3 +#: ../settings/system/storage.rst:58 msgid "" -"All following options **do not save automatically**. Always use the Save " -"button on the lower end of the integration page!" +"Or provide your S3 configuration as an URL (which you can find at the end of " +"the file). Note: you can also provide this URL as environment variable (:" +"docs:`see system documentation `) without using this yml-file." msgstr "" -#: ../system/integrations/cti/generic.rst:43 -#: ../system/integrations/cti/placetel.rst:49 -#: ../system/integrations/cti/sipgate.rst:52 -msgid "Call Settings" +#: ../settings/system/storage.rst:62 +msgid "" +"We recommend the deletion of the not used configuration style to avoid " +"inconsistencies." msgstr "" -#: ../system/integrations/cti/generic.rst:39 -#: ../system/integrations/cti/placetel.rst:49 -#: ../system/integrations/cti/sipgate.rst:37 -#: ../system/integrations/cti/sipgate.rst:50 -msgid "Inbound" +#: ../settings/system/storage.rst:65 +msgid "Restart Zammad so the config file / environment variable is loaded" msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:1 +#: ../settings/system/storage.rst:66 msgid "" -"This option allows you to block specific incoming caller IDs. It allows you " -"to temporarily reject e.g. spam callers without having to contact providers " -"or PBX administrators." -msgstr "" - -#: ../system/integrations/cti/includes/inbound-calls.include.rst:11 -msgid "Caller ID to block" +"Set the \"Storage Method\" in Zammad to ``Simple Storage (S3)`` in Settings " +"> System > Storage and click on \"Submit\". After that, Zammad checks your " +"configuration and the connection to the service and will raise an error " +"message if something is wrong." msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 -msgid "Provide caller IDs to block in ``E.164`` format." +#: ../settings/system/storage.rst:72 +msgid "A very simple storage configuration could look like this:" msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:8 +#: ../settings/system/storage.rst:85 msgid "" -"Your telephony system has to support this function. Zammad will send a " -"``reject`` response which will cause your telephony system to hang up the " -"call. To callers this usually will feel like the line is busy." +"Before setting the storage method to ``Simple Storage (S3)`` (step 4), " +"please make sure to have a working setup." msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:14 +#: ../settings/system/storage.rst:88 msgid "" -"Provide a meaningful note for your fellow administrators to remind yourself " -"why you've chosen to block the number." +"You can verify this by running ``rails r 'Rails.logger = Logger.new(STDOUT); " +"pp Store::Provider::S3.ping?'`` in your Zammad directory. If everything is " +"fine, you should see ``true``, else you should see ``false`` and a simple " +"error message." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 -#: ../system/integrations/cti/includes/outbound-calls.include.rst:17 -#: ../system/integrations/cti/sipgate.rst:40 -msgid "Outbound" +#: ../settings/system/storage.rst:93 +msgid "" +"If you installed Zammad through a package manager (rather than from source), " +"replace ``rails r`` with ``zammad run rails r`` above. To learn more, see :" +"docs:`Administration via Console `." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:1 +#: ../settings/ticket.rst:4 msgid "" -"In many cases you may want to use a different caller ID depending on the " -"destination you're calling. This may apply due to specific connection rates " -"to other countries or because you want your customer to feel you're calling " -"from the same country." +"Here you can adjust general ticket settings. Additional ones for the ticket " +"composer interface can be found in the :doc:`/misc/composer`." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:6 -msgid "This option expects ``E.164`` number formats." +#: ../settings/ticket.rst:11 +msgid "Ticket Hook (default: ``Ticket#``)" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 -msgid "Destination caller ID" +#: ../settings/ticket.rst:11 +msgid "The identifier for a ticket; *e.g.,* Ticket#, Call#, MyTicket#." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:5 -msgid "The caller ID or number you're trying to call." +#: ../settings/ticket.rst:38 +msgid "Ticket Hook Position (default: ``right``)" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:7 -msgid "You can use wildcards for e.g. country specific outbound numbers like:" +#: ../settings/ticket.rst:14 +msgid "" +"With this setting you can decide (if) where to insert the ticket number." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:9 -msgid "``49*`` for Germany" +#: ../settings/ticket.rst:20 +msgid "*Right*" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:10 -msgid "``4930*`` for Berlin / Germany landlines" +#: ../settings/ticket.rst:17 +msgid "" +"This setting will add the ticket reference on the right site of the subject." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 -msgid "``33*`` for France" +#: ../settings/ticket.rst:20 +msgid "Example: ``Some Subject [Ticket#12345]``" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:15 -msgid "Set Outbound caller ID" +#: ../settings/ticket.rst:26 +msgid "*Left*" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:14 +#: ../settings/ticket.rst:23 msgid "" -"The outbound caller ID to set (the number your customer sees on his display) " -"in ``E.164`` number format." +"This setting will add the ticket reference on the left site of the subject." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 -msgid "Provide a short description for fellow administrators." +#: ../settings/ticket.rst:26 +msgid "Example: ``[Ticket#12345] Some Subject``" msgstr "" -#: ../system/integrations/cti/includes/generic-cti-support-note.includes.rst:3 -msgid "" -"This option requires your PBX to send a specific request to Zammad *before " -"dialing*. Please consult the :docs:`CTI API ` in case " -"you're not sure." +#: ../settings/ticket.rst:29 +msgid "*None*" msgstr "" -#: ../system/integrations/cti/generic.rst:52 -#: ../system/integrations/cti/placetel.rst:54 -#: ../system/integrations/cti/sipgate.rst:59 -msgid "Other Settings" +#: ../settings/ticket.rst:29 +msgid "This will completely remove ticket references from the subject." msgstr "" -#: ../system/integrations/cti/includes/other-settings-intro.include.rst:1 +#: ../settings/ticket.rst:33 msgid "" -"Below you can find all available additional settings for this CTI " -"integration. For your overview we're sorting them by appearance and " -"reference their description first." -msgstr "" - -#: ../system/integrations/cti/includes/default-caller-id.include.rst:2 -#: ../system/integrations/cti/includes/default-caller-id.include.rst:1 -msgid "Default caller ID for outbound calls" +"Please ensure to take a look at :doc:`/channels/email/settings` within the " +"email channel to ensure you have at least one reference that helps Zammad to " +"assign follow-ups correctly." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:16 -#: ../system/integrations/cti/includes/records-caller-log.include.rst:15 -msgid "Shown records in caller log" +#: ../settings/ticket.rst:37 +msgid "" +"Disabling this and not setting up any further follow up search will lead to " +"unexpected results!" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:2 +#: ../settings/ticket.rst:65 msgid "" -"Allows you to set the number of shown caller log entries for all users. You " -"can choose from the following values:" +"Ticket Last Contact Behaviour (default: ``Use the start time of the last " +"customer thread (which may consist of multiple articles).``)" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:5 -msgid "60 (default)" +#: ../settings/ticket.rst:41 +msgid "" +"This setting changes the way Zammad updates the ``Last Contact`` value of a " +"ticket. This is fairly important for overviews and what you expect upon " +"ticket updates of a customer." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:6 -msgid "120" +#: ../settings/ticket.rst:52 +msgid "" +"Use the start time of the last customer thread (which may consist of " +"multiple articles)." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:7 -msgid "180" +#: ../settings/ticket.rst:46 +msgid "" +"If this option is chosen, Zammad will update the last updated value just " +"once if a customer replies. After that, Zammad will wait for an agent to " +"react." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:8 -msgid "240" +#: ../settings/ticket.rst:50 +msgid "" +"This comes in handy if you want to work tickets in the order of their first " +"update. This will not change ticket orders if customers decide to \"bump\" " +"the ticket affected." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:9 -msgid "300" +#: ../settings/ticket.rst:57 +msgid "Use the time of the very last customer article." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:11 -msgid "**🥵 Potential performance issue**" +#: ../settings/ticket.rst:55 +msgid "" +"When setting this option, Zammad will always update the last updated value. " +"This means that if ordering by ``Last Update``, ticket orders will change if " +"customers \"bump\" the ticket." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:13 -msgid "" -"Setting this setting higher than 60 may cause serious performance issues on " -"very busy instances. Keep in mind that this setting causes Zammad to poll " -"and send up to 300 records to *all active agent sessions* in very short time " -"periods." +#: ../settings/ticket.rst:64 +msgid "Last contact value used on :doc:`/manage/overviews`" msgstr "" -#: ../system/integrations/cti/generic.rst:73 -msgid "Caller Log Filter" +#: ../settings/ticket.rst:65 +msgid "Last contact value used on :doc:`/manage/trigger`" msgstr "" -#: ../system/integrations/cti/generic.rst:55 +#: ../settings/ticket.rst:88 msgid "" -"This function allows you to provide call information based on e.g. queues " -"only to agents that really need the information." +"Ticket Organization Reassignment (default: ``Update the most recent tickets." +"``)" msgstr "" -#: ../system/integrations/cti/generic.rst:58 +#: ../settings/ticket.rst:68 msgid "" -"Why? If you have a team for several countries or departments, you don't want " -"to bug your agents from other departments. Leaving these options empty will " -"fallback to showing everything to everyone." +"This setting changes the way Zammad updates the organization field of the " +"tickets whenever the primary organization of a user is changed." msgstr "" -#: ../system/integrations/cti/generic.rst:64 -msgid "Destination caller ID or Queue" +#: ../settings/ticket.rst:74 +msgid "Update the most recent tickets." msgstr "" -#: ../system/integrations/cti/generic.rst:63 +#: ../settings/ticket.rst:72 msgid "" -"This depends on your PBX and usually is either a queue ID, phone number or " -"extension." +"If this option is chosen, Zammad will update the 100 most recent tickets " +"where the user is the ticket customer. The ticket organization field will be " +"automatically set to the new primary organization of the user." msgstr "" -#: ../system/integrations/cti/generic.rst:69 -msgid "Agents" +#: ../settings/ticket.rst:88 +msgid "Do not update any tickets." msgstr "" -#: ../system/integrations/cti/generic.rst:67 +#: ../settings/ticket.rst:77 msgid "" -"Select the agents that are responsible for the group. These agents will then " -"see caller log entries and call notifications fitting to said queue." +"When choosing this option, Zammad will not update any tickets when the " +"user's primary organization is changed." msgstr "" -#: ../system/integrations/cti/generic.rst:0 -msgid "" -"Screenshot showing the caller log filter table with pre filled sample data" +#: ../settings/ticket.rst:80 +msgid "**Use with care!**" msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:6 +#: ../settings/ticket.rst:82 msgid "" -"With recent logs Zammad allows you to view the latest calls for the CTI " -"functionality. This usually comes in handy, when you're looking for errors." +"Using this option may lead to inconsistencies in the system as the ticket " +"organization may become decoupled from the ticket customer." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:0 +#: ../settings/ticket.rst:85 msgid "" -"Screenshot showing several incoming requests within Recent logs section." +"However, you may use this option if you wish to maintain :ref:`the shared " +"access ` to the ticket for all organization " +"members of the original organization of the customer." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:16 -msgid "I'm just here to clear floats up." +#: ../settings/ticket.rst:110 +msgid "Ticket Number Format (default: ``Increment (SystemID.Counter)``)" msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:20 +#: ../settings/ticket.rst:94 msgid "" -"By clicking on the entry of interest, Zammad will provide more details on " -"the call in question. You'll see the payload it received and also the " -"response that was sent." +"This setting defines the way Zammad's ticket number will look. Changing this " +"setting in production will cause follow up detection to fail." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:0 +#: ../settings/ticket.rst:102 +msgid "Increment (SystemID.Counter)" +msgstr "" + +#: ../settings/ticket.rst:98 msgid "" -"Screenshot showing detailed information of a specific log entry of recent " -"logs" +"The increment value contains the SystemID (automatically generated during " +"installation) and a increment which counts up with every new Ticket. The " +"increment will automatically get another digit if needed." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:31 -msgid "x" +#: ../settings/ticket.rst:102 +msgid "Examples: ``1010138``, ``1010139``" msgstr "" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 -#: ../system/integrations/cti/includes/troubleshooting.include.rst:9 -msgid "My Phone page stays blank, signalling does work..." +#: ../settings/ticket.rst:110 +msgid "Date (Year.Month.Day.SystemID.Counter)" msgstr "" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:5 +#: ../settings/ticket.rst:105 msgid "" -"If you've made sure that signalling works (check Recent logs) and your " -"Caller Log still stays empty, please ensure that you only configured one CTI " -"integration version. Specifically defining more than one agent mapping on " -"the different integration variants will be the issue." +"This version of the ticket number is fairly long. However, because it " +"contains the date of ticket creation, it also allows you to see when the " +"ticket has been created. You may feel familiar with this number format if " +"you've worked with OTRS already." msgstr "" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 -msgid "Clear the not needed agent mapping and reload your browser page." +#: ../settings/ticket.rst:110 +msgid "Examples: ``201206231010138``, ``201206231010139``" msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:1 -msgid "" -"By mapping your agents extension to their existing Zammad users, Zammad can " -"provide a new ticket dialog or open the user profile for the agent that " -"picks up the call." +#: ../settings/ticket.rst:137 +msgid "OPTIONS" msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:5 +#: ../settings/ticket.rst:113 msgid "" -"This speeds up ticket aiding, no matter if it's for existing tickets or new " -"ones!" +"The below options allow you to further customize your ticket number. The " +"availability of options differ depending of the chosen ticket number format " +"above." msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:8 -msgid "" -"To see it work from the agent's perspective, have a look on :user-docs:`user " -"documentation `." +#: ../settings/ticket.rst:122 +msgid "Checksum (default: ``no``)" msgstr "" -#: ../system/integrations/cti/placetel.rst:2 -msgid "Placetel CTI" +#: ../settings/ticket.rst:118 +msgid "" +"If set to yes, we'll built a checksum to further \"unique\" the ticket " +"number of your system. If you're dealing with many other ticket systems this " +"might help to prevent false positive follow up detection on tickets." msgstr "" -#: ../system/integrations/cti/placetel.rst:16 -msgid "You need an administrative Placetel account for your organization." +#: ../settings/ticket.rst:122 +msgid "This will also add another digit to the ticket number." msgstr "" -#: ../system/integrations/cti/placetel.rst:17 -#: ../system/integrations/cti/sipgate.rst:20 -msgid "" -"Your Zammad instance must be allowed to communicate to external services." -msgstr "" - -#: ../system/integrations/cti/placetel.rst:18 -msgid "Placetel must be able to reach your Zammad instance." -msgstr "" - -#: ../system/integrations/cti/placetel.rst:22 -msgid ":doc:`provider-configurations/placetel`" +#: ../settings/ticket.rst:137 +msgid "Min. size of Number (default: ``5``)" msgstr "" -#: ../system/integrations/cti/placetel.rst:21 +#: ../settings/ticket.rst:125 msgid "" -"Learn how to configure Placetel to enable Zammad and Placetel to communicate " -"with each other." +"This setting defines the minimum length of your ticket number. If your " +"counter is not yet high enough, Zammad will fill the number with zeros to " +"ensure the wanted length." msgstr "" -#: ../system/integrations/cti/placetel.rst:32 +#: ../settings/ticket.rst:129 msgid "" -"The here listed endpoint settings are relevant for the :doc:`integration " -"configuration with Placetel `." -msgstr "" - -#: ../system/integrations/cti/placetel.rst:37 -#: ../system/integrations/i-doit.rst:53 -msgid "Endpoint" +"Please note that the minimum length is ``3`` (SystemID + at least one digit " +"if below 10). Also, if the length is no longer long enough, the number will " +"automatically get one digit longer. Ticket-Numbers **do not overflow**, thus " +"it's save to keep it at 5 or set it lower if wanted." msgstr "" -#: ../system/integrations/cti/placetel.rst:36 +#: ../settings/ticket.rst:135 msgid "" -"This endpoint will be required for the Zammad integration within the " -"Placetel web interface." +"This option is only available if ticket number format is set to " +"``Increment``!" msgstr "" -#: ../system/integrations/cti/placetel.rst:41 -msgid "API Token" +#: ../settings/ticket.rst:142 +msgid "Auto-Assignment" msgstr "" -#: ../system/integrations/cti/placetel.rst:40 +#: ../settings/ticket.rst:144 msgid "" -"You'll receive this token within the ``Web API`` menu. Make sure to copy " -"this value, it's only shown once!" +"In a larger Zammad environment, it happens that several agents open the same " +"ticket at the same time. Although collision detection is then effective, the " +"efficiency of processing can be increased by means of the automatic " +"assignment of tickets when a ticket is opened." msgstr "" -#: ../system/integrations/cti/placetel.rst:71 -#: ../system/integrations/cti/sipgate.rst:77 -msgid "Phone Extension to Agent Mapping" +#: ../settings/ticket.rst:149 +msgid "" +"The automatic assignment of tickets can be activated and configured in the " +"admin area under Settings > Ticket > Auto Assignment." msgstr "" -#: ../system/integrations/cti/placetel.rst:0 -msgid "Screenshot showing sample user mappings in between Placetel and Zammad" +#: ../settings/ticket.rst:152 +msgid "" +"The auto assignment only works if the ticket has no owner yet. By default, " +"the agent can always reset the ticket owner to ``-`` if needed." msgstr "" -#: ../system/integrations/cti/placetel.rst:64 +#: ../settings/ticket.rst:155 msgid "" -"You can find your agents Placetel username combination required within ⚙️ PBX " -"→ VoIP destinations. Within the \"Advanced settings\" section you're looking " -"for \"SIP user name\" and \"SIP server\"." +"If you want to use this function for only specific tickets, you can " +"configure the conditions accordingly to meet your requirement. By default " +"the condition affects all tickets with the state ``open``." msgstr "" -#: ../system/integrations/cti/placetel.rst:68 -msgid "Combine these two like so: ``@``." +#: ../settings/ticket.rst:161 +msgid "" +"If you need to exclude users (e.g. a group leader), you can search and " +"select the desired agents in the ``Exception Users`` list. The search " +"function in this area is only effective, if you have too many agents to " +"display at once to help you with the configuration." msgstr "" -#: ../system/integrations/cti/placetel.rst:0 -msgid "Sample VoIP credentials for a Placetel user" +#: ../settings/ticket.rst:167 +msgid "Notifications" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:2 -msgid "Setup Placetel connection for Zammad" +#: ../settings/ticket.rst:191 +msgid "Default Notifications" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:6 +#: ../settings/ticket.rst:170 msgid "" -"This configuration step requires a *full* administrative Placetel account. " -"You may receive forbidden error messages with Placetel in case your " -"permissions are not high enough." +"This setting allows you to configure the default ticket notifications that " +"will be applied to all new agent users (incl. users who were just assigned " +"agent role). Simply change the notification matrix to desired state and " +"press **Save**." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:10 +#: ../settings/ticket.rst:175 msgid "" -"The following actions can be configured via the `Placetel web interface " -"`_." -msgstr "" - -#: ../system/integrations/cti/provider-configurations/placetel.rst:29 -msgid "Step 1: Activate Zammad integration" +"In case an agent already exists, their ticket notification preferences will " +"be preserved. Optionally, you can also **Apply current defaults to all " +"agents**." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:14 +#: ../settings/ticket.rst:181 msgid "" -"Within Integrations, scroll down to Partner integrations and select Zammad." +"**Potential time-consuming action:** Applying default ticket notifications " +"to all agent users may take some time to complete, be patient! The exact " +"time will depend on the size of your system and the number of agents." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:17 +#: ../settings/ticket.rst:185 msgid "" -"You can alternatively filter by \"Ticket Systems\" to reduce the number of " -"entries on the page. You'll still want to look for Partner integrations. 🤓" +"**Active agents only!** When current default ticket notifications are " +"applied, only active agent users are considered. In case an agent is re-" +"activated *after* this action, they will still have the old notification " +"configuration." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:21 +#: ../settings/ticket.rst:190 msgid "" -"Within the Zammad integration now press \"Activate\". A new tab ``API`` " -"becomes available - open this tab." +"In case you want to go back to the initial state of ticket notifications, " +"you can click on **Reset to default** button." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:24 -msgid "" -"Now tick \"Enable Call Control / Notify API\" and paste the Placetel " -"endpoint from your Zammad instance into the field \"URL of your API " -"endpoint\". Save to apply the settings" +#: ../settings/ticket.rst:196 +msgid "Duplicate Detection" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 -msgid "Screencast showing how to activate the Zammad integration" +#: ../settings/ticket.rst:238 +msgid "Detect Duplicate Ticket Creation" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:51 -msgid "Step 2: Generate API Token for Placetel" +#: ../settings/ticket.rst:199 +msgid "" +"This setting turns on the duplicate ticket detection mechanism during ticket " +"creation. If similar tickets are found in the system, a suitable warning " +"will be shown to the user trying to create a ticket." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:32 -msgid "" -"Go back to the integrations page and scroll down to \"Web API\". Generate a " -"new API token by using the \"Create a new API token\" button." +#: ../settings/ticket.rst:206 +msgid "A Sample Duplicate Ticket Warning" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:37 +#: ../settings/ticket.rst:208 msgid "" -"If you already generated a token either use your existing token or reset it " -"by using above mentioned button. Placetel will ask you to conform this reset." +"You can choose which ticket attributes will be matched by selecting them in " +"**Attributes to compare** field. Only if the ticket attribute value provided " +"by the user in the ticket create form is *equal* with the attribute in an " +"existing ticket, the warning will be shown." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:41 -msgid "" -"Please keep in mind that existing API scripts may no longer work due to " -"token resets!" +#: ../settings/ticket.rst:213 +msgid "**Warning title** and **Warning message** are configurable as well." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:44 +#: ../settings/ticket.rst:215 msgid "" -"Copy the provided API token and insert it into the \"API Token\" field " -"within Zammad's Placetel integration." +"You can limit the detection only to certain user roles. By default, only " +"agents will see the warning." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:47 +#: ../settings/ticket.rst:218 msgid "" -"Apply your changes by using the \"Save\" button on the bottom of the " -"Placetel integration page and activate the Placetel integration." +"If you don't want to show the matched tickets as part of the warning, you " +"can set **Show matching ticket(s) in the warning** setting to *no*." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +#: ../settings/ticket.rst:221 msgid "" -"Screencast showing how to retrieve an API token from Placetel for Zammad" +"By default, **Permission level for looking up ticket** is set to *User*, " +"which means user permissions will be honored during sarch. The user will " +"see the warning only if tickets they have access to are matched. " +"Alternatively, you can set this setting to *System*, in which case the " +"search will happen within *all* tickets in the system, regardless of user " +"permissions." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:73 -#: ../system/integrations/cti/provider-configurations/sipgate.rst:77 -msgid "Step 3: Restrict the numbers to notify on" +#: ../settings/ticket.rst:227 +msgid "**🦺 Safety first!**" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:54 +#: ../settings/ticket.rst:229 msgid "" -"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " -"the the Integrations page of the Placetel web interface, go to \"Notify " -"API\"." +"Even if the permission level is set to *System*, the user will not be shown " +"the tickets they don't have access to in the warning, even if they match." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:58 +#: ../settings/ticket.rst:233 msgid "" -"Lower on the page Placetel allows you to restrict the numbers to notify on. " -"You'll find this within the \"External routing API\" part." +"However, just the confirmation about the existence of the tickets in the " +"system may be considered an unwanted information disclosure. Use this option " +"carefully!" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +#: ../settings/ticket.rst:237 msgid "" -"Screenshot showing a sample selection of phone numbers to use for the " -"Placetels notify API" +"Finally, you can configure between matching within **All tickets** or **Open " +"tickets** only by setting **Match tickets in following states**. Depending " +"on the current ticket state, a ticket may or not be matched." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:66 -msgid "" -"This menu point also provides a API request log from Placetel view. Just " -"open \"Recent responses of your API endpoint\" to learn more." +#: ../system/core-workflows.rst:2 +msgid "Core Workflows" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:69 +#: ../system/core-workflows.rst:4 msgid "" -"If you want to see Zammad's perspective, use the \"Recent Logs\" part from " -"within the Placetel integration page." +"Core Workflows allow you to adjust object attributes in many ways. For " +"example:" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 -msgid "Screenshot showing sample log entries for Placetels API calls to Zammad" +#: ../system/core-workflows.rst:7 +msgid "show / hide fields" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:77 -msgid "Step 4 (optional): Further configurations for Placetel" +#: ../system/core-workflows.rst:8 +msgid "adjust mandatory setting" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:76 -msgid "" -"If needed, you can now configure Zammad's Placetel integration in more " -"detail. You can learn more about your options here: :ref:`Placetel " -"integration settings `." +#: ../system/core-workflows.rst:9 +msgid "manipulate available options" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:2 -msgid "Setup Sipgate connection for Zammad" +#: ../system/core-workflows.rst:11 +msgid "" +"With this, you can provide exactly the information your users really need!" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +#: ../system/core-workflows.rst:15 msgid "" -"Sipgate has no english web interface which is why this documentation page is " -"mixing up languages badly." +"If the pre-defined :doc:`/system/objects` are not enough, please add them " +"beforehand." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +#: ../system/core-workflows.rst:17 msgid "" -"Please also note that the availability of API addons highly depends on your " -"package trier. Usage of sipgate.io packages *is not free*, please check " -"their `pricing page `_ before!" +"If you experience slow or unreliable field updates, please see :ref:`Core " +"Workflow Ajax Modus `" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:35 -msgid "Step 1: Book sipgate.io package" +#: ../system/core-workflows.rst:22 +msgid "" +"This is a very enhanced functionality and can cause unexpected UI behavior. " +"Please ensure to test your use cases after configuration to reduce surprises." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:13 -msgid "Skip to step 2 if you already have the package booked!" +#: ../system/core-workflows.rst:None +msgid "Dialogue for adding a new workflow" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:15 -msgid "" -"Login to an administrative Sipgate account and navigate to " -"``Accountverwaltung``. You'll see several different options depending on " -"your booked packages. Select ``Verträge & Produkte`` to continue." +#: ../system/core-workflows/condition-operators.rst:2 +msgid "Core Workflow Condition Operators" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:19 +#: ../system/core-workflows/condition-operators.rst:4 msgid "" -"Scroll down to the section ``Zusätzliche Produkte buchen`` and look for " -"``sipgate.io`` - select this product by using the ``Produkte anzeigen``-" -"Button." +"You might know that there is a separate section for explaining :doc:" +"`condition operators `. Head over there to " +"see a detailed explanation of many conditions and operators." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:23 +#: ../system/core-workflows/condition-operators.rst:8 msgid "" -"On the next page select either one of the ``sipgate.io`` packages or ``Push-" -"API Package Free``. Follow the dialogue by booking the addon. You'll be " -"returned to your contract overview and now should see the selected addon in " -"your list." +"Due to differences to other places in Zammad which are also using conditions " +"(e.g. triggers), you can find a dedicated description of operators for core " +"workflows below." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:30 +#: ../system/core-workflows/condition-operators.rst:12 msgid "" -"The availability for ``sipgate.io`` packages and their levels highly depends " -"on the overall account type and product you've booked with Sipgate." +"Be aware that the availability of the operators depends on the selected " +"attribute and its field type. Some of the operators may only be available " +"for system attributes (e.g. for \"tags\", \"active\")." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screencast showing the process on how to book the required sipgate.io addon" +#: ../system/core-workflows/condition-operators.rst:20 +msgid "Operator" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:52 -msgid "Step 2: Configure webhook for Zammad" +#: ../system/core-workflows/condition-operators.rst:22 +msgid "after (absolute)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:38 -msgid "" -"Within your ``Accountverwaltung`` navicate to your product ``sipgate.io``. " -"In the newly opened tab, switch from \"Clients\" to \"Webhooks\" and paste " -"the endpoint URLs from your Zammad instance like so:" +#: ../system/core-workflows/condition-operators.rst:23 +msgid "Matches if a date/time is after a specific point in time." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:42 -msgid "Inbound endpoint to \"Incoming\"" +#: ../system/core-workflows/condition-operators.rst:24 +msgid "after (relative)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:43 -msgid "Outbound endpoint to \"Outgoing\"" +#: ../system/core-workflows/condition-operators.rst:25 +msgid "Matches if a time span after a specified event has passed." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:47 -msgid "" -"Ensure to select at least one call group or phoneline within \"Sources\". " -"Other wise Sipgate will not indicate any incoming or outgoing calls to " -"Zammad." +#: ../system/core-workflows/condition-operators.rst:26 +msgid "before (absolute)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screencast showing how to add Zammad's endpoint URLs to sipgate.ios webhook " -"configuration" +#: ../system/core-workflows/condition-operators.rst:27 +msgid "Matches if a date/time is before a specific point in time." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:55 -msgid "" -"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " -"the Webhooks → URLs section of Sipgate you can select which *sources* " -"Sipgate should notify Zammad about in- and outgoing calls." +#: ../system/core-workflows/condition-operators.rst:28 +msgid "before (relative)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:59 -msgid "" -"Use either specific phone lines or use the option \"Use for all phonelines " -"and groups\" to notify Zammad about all existing lines of your Sipgate " -"account." +#: ../system/core-workflows/condition-operators.rst:29 +msgid "Matches if a time span after a specified event has not passed." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screenshot showing a sample selection of phone numbers to use for the " -"Sipgates webhooks API" +#: ../system/core-workflows/condition-operators.rst:30 +msgid "contains" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:68 -msgid "This section also allows you to enable a Debug log." +#: ../system/core-workflows/condition-operators.rst:31 +msgid "Matches if a specified value is present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "Screenshot showing an enabled Debug log option" +#: ../system/core-workflows/condition-operators.rst:33 +msgid "Matches if all of the specified values are present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:73 -msgid "" -"After enabling you can use the Debug log section to see all sent webhook " -"calls to Zammad. You'll also can see the response." +#: ../system/core-workflows/condition-operators.rst:35 +msgid "Matches if none of the specified values are present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screenshot showing sample log entries for Sipgates webhook calls to Zammad" +#: ../system/core-workflows/condition-operators.rst:36 +msgid "contains not" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:81 -msgid "Step 4 (optional): Further configurations for Sipgate" +#: ../system/core-workflows/condition-operators.rst:37 +msgid "Matches if a specified value is not present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:80 -msgid "" -"If needed, you can now configure Zammad's Sipgate integration in more " -"detail. You can learn more about your options here: :ref:`Sipgate " -"integration settings `." +#: ../system/core-workflows/condition-operators.rst:39 +msgid "Matches if one specified value is present." msgstr "" -#: ../system/integrations/cti/sipgate.rst:2 -msgid "Sipgate (sipgate.io)" +#: ../system/core-workflows/condition-operators.rst:41 +msgid "Matches if one specified value is not present." msgstr "" -#: ../system/integrations/cti/sipgate.rst:16 -msgid "You need an administrative Sipgate account for your organization." +#: ../system/core-workflows/condition-operators.rst:42 +msgid "does not match regex" msgstr "" -#: ../system/integrations/cti/sipgate.rst:17 -msgid "" -"Zammad requires a ``sipgate.io`` addon from the feature store (please note " -"that API calls are not free with Sipgate. Rates may apply and differ from " -"account to account)." +#: ../system/core-workflows/condition-operators.rst:43 +msgid "Matches if content doesn't fit to regex rule." msgstr "" -#: ../system/integrations/cti/sipgate.rst:21 -msgid "Sipgate must be able to reach your Zammad instance." +#: ../system/core-workflows/condition-operators.rst:44 +msgid "ends with" msgstr "" -#: ../system/integrations/cti/sipgate.rst:25 -msgid ":doc:`provider-configurations/sipgate`" +#: ../system/core-workflows/condition-operators.rst:45 +msgid "Matches if content ends with specified value." msgstr "" -#: ../system/integrations/cti/sipgate.rst:24 -msgid "" -"Learn how to configure Sipgate to enable Zammad and Sipgate to communicate " -"with each other." +#: ../system/core-workflows/condition-operators.rst:46 +msgid "ends with one of" msgstr "" -#: ../system/integrations/cti/sipgate.rst:33 -msgid "" -"Below endpoint settings affect the :doc:`sipgate.io configuration `." +#: ../system/core-workflows/condition-operators.rst:47 +msgid "Matches if content ends with one of the specified values." msgstr "" -#: ../system/integrations/cti/sipgate.rst:37 -msgid "This endpoint is required for incoming call hooks." +#: ../system/core-workflows/condition-operators.rst:48 +msgid "from (relative)" msgstr "" -#: ../system/integrations/cti/sipgate.rst:40 -msgid "This endpoint is required for outgoing call hooks." +#: ../system/core-workflows/condition-operators.rst:49 +msgid "Matches if date/time is after a period of time after an event." msgstr "" -#: ../system/integrations/cti/sipgate.rst:0 -msgid "Screenshot showing sample user mappings in between Sipgate and Zammad" +#: ../system/core-workflows/condition-operators.rst:51 +msgid "Matches if content is equal to a specified value." msgstr "" -#: ../system/integrations/cti/sipgate.rst:69 -msgid "" -"You can find your agent's Sipgate username within ``Accountverwaltung → " -"Benutzer``. You're looking for the SIP-ID." +#: ../system/core-workflows/condition-operators.rst:52 +msgid "is any of" msgstr "" -#: ../system/integrations/cti/sipgate.rst:0 -msgid "Sample VoIP credentials for a Sipgate user" +#: ../system/core-workflows/condition-operators.rst:53 +msgid "Matches if content is equal to any of specified values." msgstr "" -#: ../system/integrations/cti/sipgate.rst:77 -msgid "Users with several devices also have several SIP-IDs." +#: ../system/core-workflows/condition-operators.rst:54 +msgid "is modified" msgstr "" -#: ../system/integrations/elasticsearch.rst:2 -msgid "Elasticsearch (SaaS)" +#: ../system/core-workflows/condition-operators.rst:55 +msgid "Matches if content is modified." msgstr "" -#: ../system/integrations/elasticsearch.rst:4 -msgid "" -"The Elasticsearch integration allows you to create a read-only user to use " -"with your favorite reporting tool (e.g. like Grafana)." +#: ../system/core-workflows/condition-operators.rst:57 +#: ../system/core-workflows/condition-operators.rst:61 +msgid "True from the moment of changing content until form submit." msgstr "" -#: ../system/integrations/elasticsearch.rst:7 -msgid "" -"If you want to take full advantage of the Zammad reporting, have a look at " -"our :docs:`Grafana ` " -"setup page as well." +#: ../system/core-workflows/condition-operators.rst:58 +msgid "is modified to" msgstr "" -#: ../system/integrations/elasticsearch.rst:11 -#: ../system/subscription/index.rst:7 -msgid "**🚧 Hosted environment specific 🚧**" +#: ../system/core-workflows/condition-operators.rst:59 +msgid "Matches if content is modified to a specific value." msgstr "" -#: ../system/integrations/elasticsearch.rst:13 -msgid "" -"This integration is only available for Hosted setups. In order to use " -"Elasticsearch you'll need the **Plus** subscription." +#: ../system/core-workflows/condition-operators.rst:62 +msgid "is none of" msgstr "" -#: ../system/integrations/elasticsearch.rst:16 -msgid "" -"Self hosted users have all the control over their self hosted Elasticsearch " -"instances." +#: ../system/core-workflows/condition-operators.rst:63 +msgid "Matches if content is none of any specified values." msgstr "" -#: ../system/integrations/elasticsearch.rst:None -msgid "Elasticsearch integration page on SaaS environments" +#: ../system/core-workflows/condition-operators.rst:65 +msgid "Matches if content is not equal to a specified value." msgstr "" -#: ../system/integrations/elasticsearch.rst:27 -msgid "" -"Please note the following limitations of Elasticsearch access on hosted " -"environments:" +#: ../system/core-workflows/condition-operators.rst:67 +msgid "Matches if content is present." msgstr "" -#: ../system/integrations/elasticsearch.rst:30 -msgid "access to the Elasticsearch index is read-only access" +#: ../system/core-workflows/condition-operators.rst:68 +msgid "just changed" msgstr "" -#: ../system/integrations/elasticsearch.rst:31 -msgid "currently you're limited to user only" +#: ../system/core-workflows/condition-operators.rst:69 +msgid "Matches if content has changed." msgstr "" -#: ../system/integrations/elasticsearch.rst:32 +#: ../system/core-workflows/condition-operators.rst:71 +#: ../system/core-workflows/condition-operators.rst:75 msgid "" -"Reporting tools that require to write into the indexes (like Kibana) are not " -"supported" +"Only true for the moment of changing content until next form field action/" +"click." msgstr "" -#: ../system/integrations/elasticsearch.rst:34 -msgid "IP access restriction is currently not yet supported" +#: ../system/core-workflows/condition-operators.rst:72 +msgid "just changed to" msgstr "" -#: ../system/integrations/elasticsearch.rst:37 -msgid "Activating Elasticsearch Access" +#: ../system/core-workflows/condition-operators.rst:73 +msgid "Matches if content has changed to a specified value." msgstr "" -#: ../system/integrations/elasticsearch.rst:39 -msgid "" -"By default external access to your Elasticsearch index is not active. You " -"can enable the integration at any time if needed." +#: ../system/core-workflows/condition-operators.rst:76 +msgid "matches regex" msgstr "" -#: ../system/integrations/elasticsearch.rst:42 -msgid "" -"Please ensure to note down the password provided - you won't have access to " -"it afterwards." +#: ../system/core-workflows/condition-operators.rst:77 +msgid "Matches if value fits to regex rule." msgstr "" -#: ../system/integrations/elasticsearch.rst:None -msgid "Screencast showing activation of Elasticsearch integration" -msgstr "" - -#: ../system/integrations/elasticsearch.rst:51 -msgid "Connection Settings" +#: ../system/core-workflows/condition-operators.rst:79 +msgid "Matches if no content is present." msgstr "" -#: ../system/integrations/elasticsearch.rst:53 -msgid "" -"This section holds the most important general information for accessing your " -"Elasticsearch indexes - such as:" +#: ../system/core-workflows/condition-operators.rst:80 +msgid "starts with" msgstr "" -#: ../system/integrations/elasticsearch.rst:57 -msgid "A unique subdomain that does not tell your real instance URL." +#: ../system/core-workflows/condition-operators.rst:81 +msgid "Matches if content starts with specified value." msgstr "" -#: ../system/integrations/elasticsearch.rst:61 -msgid "Software" +#: ../system/core-workflows/condition-operators.rst:82 +msgid "starts with one of" msgstr "" -#: ../system/integrations/elasticsearch.rst:60 -msgid "" -"The major version of the search index being used. This is required by some " -"Reporting tools like Grafana." +#: ../system/core-workflows/condition-operators.rst:83 +msgid "Matches if content starts with one of the specified values." msgstr "" -#: ../system/integrations/elasticsearch.rst:64 -msgid "Authentication" +#: ../system/core-workflows/condition-operators.rst:84 +msgid "till (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:64 -msgid "The authentication type being supported. ``Basic Authentication``" +#: ../system/core-workflows/condition-operators.rst:85 +msgid "Matches if date/time is before a period of time before an event." msgstr "" -#: ../system/integrations/elasticsearch.rst:67 -msgid "Available Indexes" +#: ../system/core-workflows/condition-operators.rst:86 +msgid "today" msgstr "" -#: ../system/integrations/elasticsearch.rst:69 -msgid "" -"Within this section we're displaying the -in our opinion- most important " -"indexes for a Zammad instance." +#: ../system/core-workflows/condition-operators.rst:87 +msgid "Matches if date/time is today." msgstr "" -#: ../system/integrations/elasticsearch.rst:72 -msgid "" -"If you require all indexes or our listing is not good enough for you, point " -"your browser to the URL we're providing and append ``/_aliases?" -"pretty=true``. The result should look like this: ``https://.zammad.com/" -"_aliases?pretty=true``." +#: ../system/core-workflows/condition-operators.rst:88 +msgid "within last (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:77 +#: ../system/core-workflows/condition-operators.rst:89 msgid "" -"Your browser will automatically ask for your credentials - you'll then see " -"something like this:" -msgstr "" - -#: ../system/integrations/elasticsearch.rst:125 -msgid "Credentials" +"Matches if date/time content is within specified period of time before now." msgstr "" -#: ../system/integrations/elasticsearch.rst:127 -msgid "" -"Within this section Zammad displays your available users. The password is " -"provided once (upon activation) and cannot be retrieved after that." +#: ../system/core-workflows/condition-operators.rst:91 +msgid "within next (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:131 +#: ../system/core-workflows/condition-operators.rst:92 msgid "" -"If you need to change or reset your Elasticsearch user password, use the " -"\"Reset password\" button in the credentials table. Doing so creates a brand " -"new password for the account in question. This change is immediate, keep in " -"mind that this may affect third party tools connected to your instance." +"Matches if date/time content is within specified period of time after now." msgstr "" -#: ../system/integrations/exchange.rst:2 -msgid "Exchange" +#: ../system/core-workflows/how-do-they-work.rst:2 +msgid "How do they work?" msgstr "" -#: ../system/integrations/exchange.rst:4 +#: ../system/core-workflows/how-do-they-work.rst:4 msgid "" -"With Zammad's Exchange integration, you can easily use existing address " -"books without having to update more than one source." +"Core Workflows are executed according to their priority. If two workflows " +"have the same priority, they are executed in alphabetical order based on " +"their **name**." msgstr "" -#: ../system/integrations/exchange.rst:7 +#: ../system/core-workflows/how-do-they-work.rst:8 msgid "" -"However, you should refrain from syncing all addresses, as the results may " -"not be what you expect (Exchange collects huge amounts of addresses). A " -"central address book of your company to sync makes more sense, as you can " -"ensure that Zammad gets only the data you need and want. Apart from this, it " -"is even not possible to sync the Global Address List (GAL) of your Exchange " -"system with Zammad." +"Because of the way Core Workflows work, all changes to attributes are " +"checked with the application server - please see :doc:`limitations` for " +"possible issues." msgstr "" -#: ../system/integrations/exchange.rst:16 +#: ../system/core-workflows/how-do-they-work.rst:12 msgid "" -"**Exchange and LDAP:** The exchange sync can be overruled by Zammad's LDAP " -"integration. If you have the same users in both sources, the LDAP version " -"will always be Zammad's pick." +"Below we're talking about settings that are important and not self-" +"explanatory." msgstr "" -#: ../system/integrations/exchange.rst:19 +#: ../system/core-workflows/how-do-they-work.rst:17 msgid "" -"**One way sync:** the Exchange sync is one way. Exchange => Zammad. Changes " -"to your users inside of Zammad might be overwritten by the Exchange sync." +"Choose the object context you want to run the workflow in. This will decide " +"on your available attributes and actions." msgstr "" -#: ../system/integrations/exchange.rst:24 -msgid "" -"To configure Exchange integration, simply go to the System > Integrations > " -"Exchange in the admin panel. Press \"change\" and follow the wizard for " -"adding the needed Exchange information to Zammad. On the last two steps " -"Zammad will ask you for the address book(s) and your desired attribute " -"mapping. By default, Zammad only maps email address, first- and lastname. " -"Technically, you can map any Exchange object to a Zammad user object (this " -"also works for custom objects!)." +#: ../system/core-workflows/how-do-they-work.rst:20 +msgid "Ticket objects also have access to the ticket customer." msgstr "" -#: ../system/integrations/exchange.rst:35 +#: ../system/core-workflows/how-do-they-work.rst:25 msgid "" -"If the SSL verification fails while connecting to Exchange, Zammad will ask " -"you to turn it off temporarily." +"Choose in which situation the workflow is applied. Contexts can be combined " +"to avoid duplicate workflows." msgstr "" -#: ../system/integrations/exchange.rst:38 -msgid "" -"Please be aware that **turning off SSL verification is a security risk**. It " -"should only be used temporarily or for testing purposes. If turned off, " -"there is no verification of the certificate, which means that every " -"presented certificate will be accepted." +#: ../system/core-workflows/how-do-they-work.rst:30 +msgid "Creation mask" msgstr "" -#: ../system/integrations/exchange.rst:43 +#: ../system/core-workflows/how-do-they-work.rst:29 msgid "" -"After pressing Continue, Zammad will check if the configuration is okay. You " -"can then enable Exchange and start your first sync. The sync will then run " -"hourly - if you need to change mappings or the address book(s), you can " -"change the configuration at any time." +"If selected, your conditions and actions will affect all applicable creation " +"masks." msgstr "" -#: ../system/integrations/exchange.rst:50 -msgid "" -"After the sync has finished, you can find the new Exchange contacts under " -"\"Users\". Zammad integrates them just as normal users." +#: ../system/core-workflows/how-do-they-work.rst:34 +msgid "Edit mask" msgstr "" -#: ../system/integrations/exchange.rst:55 +#: ../system/core-workflows/how-do-they-work.rst:33 msgid "" -"In some cases you might see unique IDs as \"Login\" instead of the email " -"address. This is normal and doesn't affect the login or email mapping for " -"that entry." +"If selected, your conditions and actions will affect all applicable edit " +"masks." msgstr "" -#: ../system/integrations/github.rst:4 +#: ../system/core-workflows/how-do-they-work.rst:39 msgid "" -"Use GitHub integration to track GitHub issues directly within Zammad " -"tickets. Add issue hyperlinks and get a live summary of metadata like status " -"(open/closed), assignee, labels, and more." -msgstr "" - -#: ../system/integrations/github.rst:8 -msgid "Please note that our GitHub integration does not support pull requests." +"Zammad differentiates between selected and saved conditions. These can be " +"combined wherever needed." msgstr "" -#: ../system/integrations/github.rst:None -msgid "Integration page for GitHub" +#: ../system/core-workflows/how-do-they-work.rst:42 +msgid "**⚠️ Restrict workflows to specific roles if needed!**" msgstr "" -#: ../system/integrations/github.rst:18 +#: ../system/core-workflows/how-do-they-work.rst:44 msgid "" -"In your GitHub settings, create a new API token under **Developer settings > " -"Personal access tokens > Generate new token**. Leave the **Scopes** section " -"empty." +"By default and unless configured in conditions, workflow rules are executed " +"for **all roles**. This also affects your customers!" msgstr "" -#: ../system/integrations/github.rst:0 ../system/integrations/gitlab.rst:0 -msgid "Screencast showing how to create a new API token" +#: ../system/core-workflows/how-do-they-work.rst:50 +msgid "Selected Conditions" msgstr "" -#: ../system/integrations/github.rst:27 -msgid "Create a new API key with no scopes/privileges." +#: ../system/core-workflows/how-do-they-work.rst:48 +msgid "" +"These conditions are based on form values and match if an appropriate " +"selection is made (e.g. choosing another group in the ticket without " +"saving). This applies for drafts (active selection) and currently saved " +"values." msgstr "" -#: ../system/integrations/github.rst:29 -msgid "🔒 **Will this work for private repos?**" +#: ../system/core-workflows/how-do-they-work.rst:64 +msgid "Saved Conditions" msgstr "" -#: ../system/integrations/github.rst:31 +#: ../system/core-workflows/how-do-they-work.rst:53 msgid "" -"No. To link private repo issues, **use the** ``repo`` **scope instead**. " -"Bear in mind that the resulting token will have `lots of permissions that it " -"doesn't actually need `_, which presents a security risk if your token ever falls into " -"the wrong hands." +"These conditions only match if the selected values are stored in the " +"database. It ignores the current value or selection of the field, as long as " +"the changes are not saved (e.g. performing field operations for an existing " +"ticket, which is viewed/opened by an agent)." msgstr "" -#: ../system/integrations/github.rst:37 +#: ../system/core-workflows/how-do-they-work.rst:60 msgid "" -"Unfortunately, because of how GitHub's OAuth token scopes are set up, this " -"is the only way to link issues on private repos." -msgstr "" - -#: ../system/integrations/github.rst:40 -msgid "Enter your new API token in Zammad and enable GitHub integration." +"Keep in mind that the value has to be available in the situation where you " +"need it. Otherwise the condition won't match." msgstr "" -#: ../system/integrations/github.rst:0 -msgid "Screencast showing how to configure Zammad's GitHub integration" +#: ../system/core-workflows/how-do-they-work.rst:63 +msgid "" +"Example: you can't perform any actions with *saved condition* on a ticket in " +"creation, because there are no saved values at that time." msgstr "" -#: ../system/integrations/github.rst:47 +#: ../system/core-workflows/how-do-they-work.rst:66 msgid "" -"Use the default API endpoint (``https://api.github.com/graphql``) unless " -"you're using GitHub Enterprise Server." +"You can find a description of the condition operators for core workflows :" +"doc:`here `." msgstr "" -#: ../system/integrations/github.rst:50 +#: ../system/core-workflows/how-do-they-work.rst:72 msgid "" -"Once completed, a new GitHub issues tab will appear in the ticket pane. 🎉" +"Which actions should we run on the relevant fields? The possible actions " +"depend on the object type. However, usually you can at least change the " +"visibility and whether the field is mandatory." msgstr "" -#: ../system/integrations/github.rst:59 ../system/integrations/gitlab.rst:52 -msgid "Token verification is taking a long time" +#: ../system/core-workflows/how-do-they-work.rst:76 +msgid "Be aware that actions are not available for **related** context." msgstr "" -#: ../system/integrations/github.rst:56 ../system/integrations/gitlab.rst:49 +#: ../system/core-workflows/how-do-they-work.rst:78 msgid "" -"Slight delays are normal (<2 min.), especially for systems under heavy load." +"**Example:** Let's assume you are working in the ticket context. While you " +"can have customer *conditions*, you *can't adjust* objects with actions in " +"that scope. That's because this wouldn't have any impact on the ticket " +"dialog. Of course all ticket attributes (state, owner, ...) are available." msgstr "" -#: ../system/integrations/github.rst:58 +#: ../system/core-workflows/how-do-they-work.rst:84 msgid "" -"Self-hosted administrators, please check your network settings to ensure " -"that your Zammad server can reach ``api.github.com``." +"Please also have a look at our :doc:`limitations` to be safe from surprises." msgstr "" -#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 -msgid "I reloaded the page and now the API token is gone" +#: ../system/core-workflows/how-do-they-work.rst:88 +msgid "Available Operators" msgstr "" -#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 -msgid "" -"This may indicate that Zammad is still verifying your API token. Try " -"reloading the page again in a couple minutes." -msgstr "" - -#: ../system/integrations/gitlab.rst:2 -msgid "GitLab" -msgstr "" - -#: ../system/integrations/gitlab.rst:4 -msgid "" -"Use GitLab integration to track GitLab issues directly within Zammad " -"tickets. Add issue hyperlinks and get a live summary of metadata like status " -"(open/closed), assignee, labels, and more." +#: ../system/core-workflows/how-do-they-work.rst:90 +msgid "The availability of operators depends on the object type and scope." msgstr "" -#: ../system/integrations/gitlab.rst:8 +#: ../system/core-workflows/how-do-they-work.rst:94 msgid "" -"Please note that our GitLab integration does not support merge requests." -msgstr "" - -#: ../system/integrations/gitlab.rst:None -msgid "Integration page for GitLab" +"Please note that actions may or may not restrict API based access to " +"attributes. We're displaying the following icons for your overview to " +"understand these limits better:" msgstr "" -#: ../system/integrations/gitlab.rst:18 -msgid "" -"In your GitLab preferences, create a new API token under **Access Tokens**." +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|api| This icon indicates the action affects the API." msgstr "" -#: ../system/integrations/gitlab.rst:20 -msgid "Under **Select scopes**, choose ``read_api`` only." +#: ../system/core-workflows/how-do-they-work.rst:163 +msgid "api" msgstr "" -#: ../system/integrations/gitlab.rst:27 -msgid "🔒 **If you wish to link issues on any private repos...**" +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|ui| This icon indicates the action only affects the web interface." msgstr "" -#: ../system/integrations/gitlab.rst:29 -msgid "Your API token must belong to an account with access to those repos." +#: ../system/core-workflows/how-do-they-work.rst:167 +msgid "ui" msgstr "" -#: ../system/integrations/gitlab.rst:31 -msgid "Enter your new API token in Zammad and enable GitLab integration." +#: ../system/core-workflows/how-do-they-work.rst:102 +msgid "show |ui|" msgstr "" -#: ../system/integrations/gitlab.rst:0 -msgid "Screencast showing how to configure Zammad's GitLab integration" +#: ../system/core-workflows/how-do-they-work.rst:102 +msgid "Display the chosen field. Allows setting of values." msgstr "" -#: ../system/integrations/gitlab.rst:40 -msgid "" -"Use the default API endpoint (``https://gitlab.com/api/graphql``) unless " -"you're a self-hosted GitLab user." +#: ../system/core-workflows/how-do-they-work.rst:109 +msgid "hide |ui|" msgstr "" -#: ../system/integrations/gitlab.rst:43 +#: ../system/core-workflows/how-do-they-work.rst:105 msgid "" -"Once completed, a new GitLab issues tab will appear in the ticket pane. 🎉" +"Hide the chosen field. However, it technically still allows setting the " +"field." msgstr "" -#: ../system/integrations/gitlab.rst:51 +#: ../system/core-workflows/how-do-they-work.rst:108 msgid "" -"Self-hosted administrators, please check your network settings to ensure " -"that your Zammad server can reach ``gitlab.com``." +"Please note that the field is **not** gone and still contains an existing " +"value (if set)! Consider *remove* instead, if you want this field to be gone." msgstr "" -#: ../system/integrations/i-doit.rst:2 -msgid "i-doit" +#: ../system/core-workflows/how-do-they-work.rst:112 +msgid "remove |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:4 -msgid "" -"`i-doit `_ is an open-source **configuration " -"management database** - in other words, a tool for keeping tabs on every " -"single piece of your physical and digital infrastructure, from network " -"equipment to virtual machines on down to the faceplates on your rack shelves " -"and more." +#: ../system/core-workflows/how-do-they-work.rst:112 +msgid "Entirely removes the field. The field value will not be evaluated." msgstr "" -#: ../system/integrations/i-doit.rst:10 -msgid "" -"What's that got to do with Zammad? Well, if you used tickets to track issues " -"with all that hardware, you might start wishing there was a way they could " -"talk to each other." +#: ../system/core-workflows/how-do-they-work.rst:115 +msgid "set mandatory |ui| |api|" msgstr "" -#: ../system/integrations/i-doit.rst:14 -msgid "Zammad gives you two:" +#: ../system/core-workflows/how-do-they-work.rst:115 +msgid "Sets the field to mandatory." msgstr "" -#: ../system/integrations/i-doit.rst:17 -msgid "1. Add i-doit Links to Zammad Tickets" +#: ../system/core-workflows/how-do-they-work.rst:118 +msgid "set optional |ui| |api|" msgstr "" -#: ../system/integrations/i-doit.rst:20 ../system/integrations/i-doit.rst:80 -msgid "What Users See" +#: ../system/core-workflows/how-do-they-work.rst:118 +msgid "Sets the field to optional." msgstr "" -#: ../system/integrations/i-doit.rst:26 -msgid "i-doit integration in Zammad's ticket pane" +#: ../system/core-workflows/how-do-they-work.rst:124 +msgid "add option |ui| |api|" msgstr "" -#: ../system/integrations/i-doit.rst:26 -msgid "" -"The i-doit integration will appear under a new 🖨 tab in the ticket pane." +#: ../system/core-workflows/how-do-they-work.rst:121 +msgid "Allows adding options to tree selects or selects." msgstr "" -#: ../system/integrations/i-doit.rst:28 +#: ../system/core-workflows/how-do-they-work.rst:123 msgid "" -"i-doit integration puts a new tab in Zammad's ticket pane where you can add " -"links to existing i-doit devices for easy reference. (See our :user-docs:" -"`user documentation ` to learn " -"how it works in practice)." +"You have to use the \"remove option\" before performing this action. It " +"allows you to use *existing* configured values." msgstr "" -#: ../system/integrations/i-doit.rst:36 ../system/integrations/i-doit.rst:93 -msgid "How to Set it Up" +#: ../system/core-workflows/how-do-they-work.rst:128 +msgid "remove option |ui| |api|" msgstr "" -#: ../system/integrations/i-doit.rst:38 +#: ../system/core-workflows/how-do-they-work.rst:127 msgid "" -"It requires i-doit's `API Add-on `_. Make sure to have it properly set up. Use the following setting:" +"Allows removing options from tree selects or selects. It allows you to use " +"*existing* configured values." msgstr "" -#: ../system/integrations/i-doit.rst:42 -msgid "Active: ``Yes``" +#: ../system/core-workflows/how-do-they-work.rst:134 +msgid "set fixed to |ui| |api|" msgstr "" -#: ../system/integrations/i-doit.rst:43 -msgid "Enforce authentication by username and password: ``No``" +#: ../system/core-workflows/how-do-they-work.rst:131 +msgid "Reduces the available options by your selection." msgstr "" -#: ../system/integrations/i-doit.rst:45 +#: ../system/core-workflows/how-do-they-work.rst:133 msgid "" -"To set it up, enable the integration in the Zammad admin panel under " -"**System > Integrations > i-doit**:" +"This reduces your workflows in terms of *add option* and *remove option*." msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "i-doit settings within the integration pages" +#: ../system/core-workflows/how-do-they-work.rst:137 +msgid "fill in |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:53 -msgid "The root URL of your i-doit installation." +#: ../system/core-workflows/how-do-they-work.rst:137 +msgid "Allows filling in of string and integer fields with your values." msgstr "" -#: ../system/integrations/i-doit.rst:62 -msgid "API token" +#: ../system/core-workflows/how-do-they-work.rst:141 +msgid "fill in empty |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:56 +#: ../system/core-workflows/how-do-they-work.rst:140 msgid "" -"Found in the i-doit admin panel under **Interfaces / external data > JSON-" -"RPC API > Common Settings**." +"Allows filling in of string and integer fields with your values **if the " +"field is empty**." msgstr "" -#: ../system/integrations/i-doit.rst:0 -msgid "i-doit administration interface with API configuration" +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "select |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:67 -msgid "Client ID" +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "Select a specific value within a select, tree select or boolean field." msgstr "" -#: ../system/integrations/i-doit.rst:65 -msgid "A unique name to identify Zammad within i-doit." +#: ../system/core-workflows/how-do-they-work.rst:153 +msgid "auto select |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:67 -msgid "(Zammad does not require you to enter a value here, but i-doit might!)" +#: ../system/core-workflows/how-do-they-work.rst:147 +msgid "Helps users with tree select and select fields:" msgstr "" -#: ../system/integrations/i-doit.rst:70 +#: ../system/core-workflows/how-do-they-work.rst:149 msgid "" -"Here you can decide if the certificate of your i-doit system has to be " -"verified or not. In case you are using custom certificates, please have a " -"look at :doc:`how to add them to Zammad `." +"If the field has only one option available for selection and no value yet, " +"the value will be automatically set." msgstr "" -#: ../system/integrations/i-doit.rst:77 -msgid "2. List / Create Zammad Tickets in i-doit" +#: ../system/core-workflows/how-do-they-work.rst:152 +msgid "" +"This option only works if you have one value and doesn't work if there is " +"more than one option available." msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "Zammad integration in i-doit's device view" +#: ../system/core-workflows/how-do-they-work.rst:157 +msgid "set readonly |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:86 +#: ../system/core-workflows/how-do-they-work.rst:156 msgid "" -"i-doit's ticket system integration gives you a way to see all the tickets " -"for a given device without ever leaving i-doit. (See our :user-docs:`user " -"documentation ` to learn how it " -"works in practice)." +"Allows you to display an attribute as read only (which means no changes are " +"possible)." msgstr "" -#: ../system/integrations/i-doit.rst:95 -msgid "" -"Enable this integration in the i-doit admin panel under **Interfaces / " -"external data > Trouble Ticket System (TTS) > Configuration**:" +#: ../system/core-workflows/how-do-they-work.rst:161 +msgid "unset readonly |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "i-doit administration interface with TTS configuration" +#: ../system/core-workflows/how-do-they-work.rst:160 +msgid "" +"In case a workflow set the field in question to read only, you can undo this " +"with option above." msgstr "" -#: ../system/integrations/i-doit.rst:104 -msgid "TTS-Type" +#: ../system/core-workflows/how-do-they-work.rst:172 +msgid "Stop after match" msgstr "" -#: ../system/integrations/i-doit.rst:104 -msgid "``Zammad``" +#: ../system/core-workflows/how-do-they-work.rst:174 +msgid "" +"Here you can decide if other workflows are executed after the current one." msgstr "" -#: ../system/integrations/i-doit.rst:115 -msgid "Username / Password" +#: ../system/core-workflows/how-do-they-work.rst:176 +msgid "" +"If set to ``no`` (default), further workflows will be executed if they match " +"the condition. In this case, it is possible that your actions from the " +"current workflow can be overwritten by another workflow." msgstr "" -#: ../system/integrations/i-doit.rst:107 -msgid "Login credentials for a Zammad agent." +#: ../system/core-workflows/how-do-they-work.rst:180 +msgid "" +"If set to ``yes``, no further worflows will be executed after the current " +"one." msgstr "" -#: ../system/integrations/i-doit.rst:109 -msgid "" -"This agent must have **read permission** for all :doc:`groups ` that plan on using the i-doit integration." +#: ../system/core-workflows/how-do-they-work.rst:184 +msgid "Priority" msgstr "" -#: ../system/integrations/i-doit.rst:113 +#: ../system/core-workflows/how-do-they-work.rst:186 msgid "" -"You may even wish to create a dedicated agent account just for this " -"integration (otherwise, if the agent ever changes her password, you will " -"have to remember to update it here)." +"You can define the sequence, in which the workflows are executed. The " +"default value is ``500``." msgstr "" -#: ../system/integrations/i-doit.rst:117 -msgid "URL incl. protocol" +#: ../system/core-workflows/how-do-they-work.rst:189 +msgid "" +"The workflows are executed in ascending order by their priority. That means " +"lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." msgstr "" -#: ../system/integrations/i-doit.rst:118 -msgid "``https://your.zammad.domain``" +#: ../system/core-workflows/learn-by-example.rst:2 +msgid "Learn by Example" msgstr "" -#: ../system/integrations/index.rst:2 -msgid "Integrations" -msgstr "" - -#: ../system/integrations/index.rst:4 +#: ../system/core-workflows/learn-by-example.rst:4 msgid "" -"Zammad offers numerous integrations that add rich features to your instance." +"This page provides some basic examples for Core Workflows. Of course you can " +"build much more complex workflows if needed." msgstr "" -#: ../system/integrations/index.rst:6 -msgid "We're still working on this part of our documentation, stay tight!" +#: ../system/core-workflows/learn-by-example.rst:7 +msgid "" +"To learn about Core Workflows in detail, first go to :doc:`how-do-they-work`." msgstr "" -#: ../system/integrations/index.rst:10 -msgid "Integrations for Phone Systems" +#: ../system/core-workflows/learn-by-example.rst:10 +msgid "Group Based Examples" msgstr "" -#: ../system/integrations/index.rst:14 +#: ../system/core-workflows/learn-by-example.rst:12 msgid "" -"Your VoIP provider or telephony system is not listed? Possibly your provider " -"supports Zammad by using the generic CTI - if you're unsure ask your " -"provider." +"All following workflows have the same base configurations. The workflow may " +"not use them all." msgstr "" -#: ../system/integrations/index.rst:18 -msgid "" -"Provider does not support Zammad? Consider creating a `feature request in " -"the Zammad Community `_." +#: ../system/core-workflows/learn-by-example.rst:15 +msgid "Groups:" msgstr "" -#: ../system/integrations/index.rst:31 -msgid "Integrations for Authentication and Customers" +#: ../system/core-workflows/learn-by-example.rst:20 +msgid "Attributes:" msgstr "" -#: ../system/integrations/index.rst:44 -msgid "Integrations for Monitoring Systems" +#: ../system/core-workflows/learn-by-example.rst:22 +msgid "Category (Single tree selection field, not mandatory, agents only)" msgstr "" -#: ../system/integrations/index.rst:46 -msgid "This section currently misses the following integrations:" +#: ../system/core-workflows/learn-by-example.rst:23 +msgid "" +"Approved (Boolean field, not mandatory, not shown, ``false`` as default)" msgstr "" -#: ../system/integrations/index.rst:48 -msgid "Icinga" +#: ../system/core-workflows/learn-by-example.rst:24 +msgid "Operating System (Text field, not mandatory, not shown)" msgstr "" -#: ../system/integrations/index.rst:49 -msgid "Monit" +#: ../system/core-workflows/learn-by-example.rst:25 +msgid "Software used (Single selection field, not mandatory, not shown)" msgstr "" -#: ../system/integrations/index.rst:50 -msgid "Nagios" +#: ../system/core-workflows/learn-by-example.rst:68 +msgid "Group specific values and fields" msgstr "" -#: ../system/integrations/index.rst:60 -msgid "Integrations for Issue Trackers" +#: ../system/core-workflows/learn-by-example.rst:28 +msgid "" +"This workflow set depends on the category field. It reduces the available " +"set of values based on the group selected." msgstr "" -#: ../system/integrations/index.rst:70 -msgid "Other Integrations" +#: ../system/core-workflows/learn-by-example.rst:33 +msgid "Workflow 2nd Level group" msgstr "" -#: ../system/integrations/index.rst:72 +#: ../system/core-workflows/learn-by-example.rst:35 msgid "" -"This section will hold any other integration that can't be grouped up (yet)." +"This reduces the category options to ``2nd Level/*``, ``Internal/*`` and " +"``Others``. It also sets further required fields to mandatory and visible." msgstr "" -#: ../system/integrations/ldap/index.rst:2 -msgid "LDAP / Active Directory" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for 2nd level" msgstr "" -#: ../system/integrations/ldap/index.rst:4 -msgid "" -"Zammad comes with a powerful LDAP integration that allows you to have a " -"single source of truth. By this you reduce the number of login credentials " -"your user has to remember." +#: ../system/core-workflows/learn-by-example.rst:43 +msgid "Workflow Support group" msgstr "" -#: ../system/integrations/ldap/index.rst:10 +#: ../system/core-workflows/learn-by-example.rst:45 msgid "" -"The LDAP source is also a perfect candidate for Zammad's :docs:`Kerberos " -"Single Sign-On ` but also works as addition " -"to other :doc:`/settings/security/third-party`." +"This reduces the category options to ``Support/*``, ``Internal/*`` and " +"``Others``. It also sets further required fields to visible." msgstr "" -#: ../system/integrations/ldap/index.rst:None -msgid "Zammands LDAP management page" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for support" msgstr "" -#: ../system/integrations/ldap/index.rst:25 -msgid "📝 :doc:`manage`" +#: ../system/core-workflows/learn-by-example.rst:53 +msgid "Workflow Sales group" msgstr "" -#: ../system/integrations/ldap/index.rst:25 -msgid "Add, modify, remove or re-arrange your LDAP-Sources as needed." +#: ../system/core-workflows/learn-by-example.rst:55 +msgid "" +"This reduces the category options to ``Sales/*``, ``Internal/*`` and " +"``Others``." msgstr "" -#: ../system/integrations/ldap/index.rst:30 -msgid "Before you continue, please note the following limitations." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for sales" msgstr "" -#: ../system/integrations/ldap/index.rst:32 -msgid "Mapping / Synchronizing organizations is not possible" +#: ../system/core-workflows/learn-by-example.rst:68 +#: ../system/integrations/slack.rst:88 +msgid "The Result" msgstr "" -#: ../system/integrations/ldap/index.rst:36 +#: ../system/core-workflows/learn-by-example.rst:63 msgid "" -"You may want to consider using domain based assignments to overcome this " -"issue. Learn more on :doc:`/manage/organizations/index`." +"This is what the agent would experience with the above workflows in place." msgstr "" -#: ../system/integrations/ldap/index.rst:39 +#: ../system/core-workflows/learn-by-example.rst:0 msgid "" -"Zammad's LDAP sync is one way. Editing user settings or permissions may be " -"overwritten upon the next sync depending on your configuration." +"Workflow shows objects and limits options based on selections on the group" msgstr "" -#: ../system/integrations/ldap/index.rst:41 -msgid "Nested groups are not supported." +#: ../system/core-workflows/learn-by-example.rst:90 +msgid "Approval process" msgstr "" -#: ../system/integrations/ldap/index.rst:42 -msgid "Synchronizing user avatars from LDAP is not supported." +#: ../system/core-workflows/learn-by-example.rst:71 +msgid "" +"In this case ``approved`` is visible to agents by default. For this " +"workflow, an additional role ``Approval person`` is required (no further " +"permissions)." msgstr "" -#: ../system/integrations/ldap/index.rst:43 -msgid "Unlike user filters, group filters cannot be changed." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that restricts an approval attribute to specific roles" msgstr "" -#: ../system/integrations/ldap/index.rst:44 +#: ../system/core-workflows/learn-by-example.rst:81 msgid "" -"When a user originates from an LDAP server, Zammad will try to verify the " -"login credentials against LDAP first - if this fails Zammad will check its " -"local database." +"This workflow may work best in combination with a :doc:`trigger ` but technically, this is not required." msgstr "" -#: ../system/integrations/ldap/index.rst:50 +#: ../system/core-workflows/learn-by-example.rst:84 msgid "" -"Users can have local passwords even if they're LDAP users! You can learn " -"more about user accounts in general on :doc:`/manage/users/index`." +"Select fields may be a better approach because they allow more values than " +"just a simple ``true`` or ``false``." msgstr "" -#: ../system/integrations/ldap/index.rst:54 +#: ../system/core-workflows/learn-by-example.rst:0 msgid "" -"When several LDAP sources contain the same user (meaning the same email " -"address), the user in question will be updated with every source configured. " -"*The last LDAP source will win.*" +"Workflow fixes possible values of \"Approved ?\" to a specific selection " +"depending on the users role" msgstr "" -#: ../system/integrations/ldap/index.rst:58 -msgid "" -"This is subject to change with `Issue 4109 `_ in the future." +#: ../system/core-workflows/learn-by-example.rst:103 +msgid "State dependent mandatory fields" msgstr "" -#: ../system/integrations/ldap/index.rst:60 +#: ../system/core-workflows/learn-by-example.rst:93 msgid "" -"Synchronization statistics currently affect *all* configured LDAP sources. " -"This also applies for newly added or updated sources." +"This workflow sets ``Category`` to mandatory if the agent wants to set the " +"states ``closed`` or ``pending close`` to enforce categorization." msgstr "" -#: ../system/integrations/ldap/index.rst:63 -msgid "" -"This is subject to change with `Issue 4108 `_ in the future." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that sets fields to mandatory on specific states" msgstr "" -#: ../system/integrations/ldap/index.rst:65 +#: ../system/core-workflows/learn-by-example.rst:0 msgid "" -"Zammad currently has limited fallback server support. You can workaround " -"this by providing several sources - however, ensure to have the exact same " -"configuration on your fallback." +"Workflow sets category field to mandatory upon choosing closed or pending " +"close as state" msgstr "" -#: ../system/integrations/ldap/index.rst:69 -msgid "" -"This is subject to improve with `Issue 4107 `_ in the future." +#: ../system/core-workflows/learn-by-example.rst:106 +msgid "Manual Ticket Handover Process" msgstr "" -#: ../system/integrations/ldap/index.rst:76 -msgid "" -"This section holds all requests Zammad handled for all LDAP sources. These " -"entries can either contain synchronization information or logins " -"(authentication attempts via Zammad's login interface)." +#: ../system/core-workflows/learn-by-example.rst:108 +msgid "This example covers the handover of a ticket from one agent to another:" msgstr "" -#: ../system/integrations/ldap/index.rst:80 +#: ../system/core-workflows/learn-by-example.rst:110 msgid "" -"By clicking on any request, Zammad will provide even more information. The " -"provided information can be useful when something does not work as expected." +"When the ticket owner is modified, a new text field (\"Handover\") shows up " +"for a comment" msgstr "" -#: ../system/integrations/ldap/index.rst:85 +#: ../system/core-workflows/learn-by-example.rst:112 msgid "" -"Especially a LDAP synchronization can cause many log entries. The web " -"interface will always limit the number of shown entries to the last 50 " -"entries." +"This may only be visible when the owner is changed, therefore it has to be " +"hidden in general" msgstr "" -#: ../system/integrations/ldap/index.rst:None +#: ../system/core-workflows/learn-by-example.rst:114 +msgid "The input in this handover text field is mandatory" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:115 msgid "" -"Screencast showing LDAP integration log entries and a detail view on\n" -"an entry." +"After submitting changes, the value of the handover field must be added as " +"an note to the ticket (via trigger)" msgstr "" -#: ../system/integrations/ldap/manage.rst:2 -msgid "Manage LDAP-Sources" +#: ../system/core-workflows/learn-by-example.rst:121 +msgid "Hiding handover field" msgstr "" -#: ../system/integrations/ldap/manage.rst:6 -msgid "" -"Please keep in mind all current limitations for the LDAP synchronization. " -"This will help to understand scopes of the following operations better." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Hiding the handover field in core workflows" msgstr "" -#: ../system/integrations/ldap/manage.rst:65 -msgid "Add new source" +#: ../system/core-workflows/learn-by-example.rst:126 +msgid "Showing handover field and setting it to mandatory" msgstr "" -#: ../system/integrations/ldap/manage.rst:10 -msgid "" -"Using the *New Source* button allows you to add new LDAP sources to your " -"installation. You're not limited in the number of sources, however, keep in " -"mind that many sources will also take more time to synchronize." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Showing the handover field and set it as mandatory" msgstr "" -#: ../system/integrations/ldap/manage.rst:14 -msgid "" -"You can choose between different encryption types, namely *SSL* and " -"*STARTTLS* or none of them (\"*No SSL*\"). If you choose *SSL* or " -"*STARTTLS*, Zammad will display an additional *SSL verification* option that " -"allows you to disable the verification, e.g. for self-signed SSL " -"certificates. You can also tell Zammad to use a different port by appending " -"``:`` to your hostname/IP." +#: ../system/core-workflows/learn-by-example.rst:131 +msgid "Trigger writing handover input to a new article" msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "" -"Screenshot of configuring a new LDAP source with SSL encryption and SSL " -"verification" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Write handover content to a new article" msgstr "" -#: ../system/integrations/ldap/manage.rst:26 +#: ../system/core-workflows/learn-by-example.rst:133 msgid "" -"New Source with SSL transport security enabled and certificate verification" +"As a result, the ticket includes an article of the type note which includes " +"the predefined text and the handover comment." msgstr "" -#: ../system/integrations/ldap/manage.rst:30 +#: ../system/core-workflows/limitations.rst:6 +msgid "Core Workflows do not replace Triggers" +msgstr "" + +#: ../system/core-workflows/limitations.rst:5 msgid "" -"Using an user filter can be a good idea if you only require a small subset " -"of your LDAP users in Zammad." +"Workflows manipulate the behavior of fields. However, they do not set values " +"in fields because of actions." msgstr "" -#: ../system/integrations/ldap/manage.rst:42 -msgid "This especially affects inactive users" +#: ../system/core-workflows/limitations.rst:16 +msgid "API calls are only partly affected" msgstr "" -#: ../system/integrations/ldap/manage.rst:34 +#: ../system/core-workflows/limitations.rst:9 msgid "" -"As every LDAP behaves differently on which attributes and how they are set, " -"Zammad doesn't care about any flags." +"Some options affect UI only and thus do not restrict responses and calls." msgstr "" -#: ../system/integrations/ldap/manage.rst:37 -msgid "" -"Users that no longer are returned by your LDAP source will automatically be " -"set to inactive. Zammad assumes that the user was deactivated." +#: ../system/core-workflows/limitations.rst:11 +msgid "This affects the following actions:" msgstr "" -#: ../system/integrations/ldap/manage.rst:41 -msgid "" -"Users will never be removed automatically! If you want to remove obsolete " -"users, use :doc:`/system/data-privacy`." +#: ../system/core-workflows/limitations.rst:13 +msgid "select" msgstr "" -#: ../system/integrations/ldap/manage.rst:46 -msgid "Active Directory admins" +#: ../system/core-workflows/limitations.rst:14 +msgid "auto select" msgstr "" -#: ../system/integrations/ldap/manage.rst:45 -msgid "" -"Active Directories are quite specific on how to filter for active users only " -"- please see the `Microsoft documentation `_ for more " -"information." +#: ../system/core-workflows/limitations.rst:15 +msgid "show" msgstr "" -#: ../system/integrations/ldap/manage.rst:51 -msgid "" -"*Do not* manually write pathes of either LDAP attributes or groups. If " -"Zammad does not display them, it either cannot find them or you have a lot " -"of users that don't have the attributes populated." +#: ../system/core-workflows/limitations.rst:16 +msgid "hide" msgstr "" -#: ../system/integrations/ldap/manage.rst:55 -msgid "" -"Zammad will always only return attributes that are filled - this reduces the " -"returned list of attributes greatly." +#: ../system/core-workflows/limitations.rst:25 +msgid "Some fields stay unavailable to customers" msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing how to add a new LDAP source" +#: ../system/core-workflows/limitations.rst:19 +msgid "" +"For technical and security reasons, some default fields (the pale ones you " +"can't edit) stay unavailable for display and usage on customer permissions." msgstr "" -#: ../system/integrations/ldap/manage.rst:63 +#: ../system/core-workflows/limitations.rst:23 msgid "" -"If your LDAP system doesn't allow anonymous bind, Zammad detects it and " -"provides you an editable \"Base DN\" *text* field instead of a prefilled " -"*select* field." +"If you require your customers to change e.g. priorities, please consider " +"using workarounds via :doc:`/system/objects` and :doc:`/manage/trigger`." msgstr "" -#: ../system/integrations/ldap/manage.rst:81 -msgid "Review or edit existing source" +#: ../system/core-workflows/limitations.rst:29 +msgid "Ticket title changes not supported in edit mask" msgstr "" -#: ../system/integrations/ldap/manage.rst:68 +#: ../system/core-workflows/limitations.rst:28 msgid "" -"Clicking on a LDAP source will provide a configuration and mapping overview." +"It is currently not possible to perform changes of the ticket title in the " +"edit mask (e.g. renaming, set to read-only)." msgstr "" -#: ../system/integrations/ldap/manage.rst:70 -msgid "" -"If needed you can then use the *Change* button to update either the name, " -"active state or the whole configuration. If you're changing the whole " -"configuration, the dialogue will be identical to the source creation." +#: ../system/core-workflows/limitations.rst:37 +msgid "What is out of scope of Core Workflows?" msgstr "" -#: ../system/integrations/ldap/manage.rst:76 +#: ../system/core-workflows/limitations.rst:32 msgid "" -"Did your LDAP server change? Different LDAP servers have different " -"structures and default attributes. This causes the LDAP synchronization to " -"likely fail. Consider removing the affected source and re-add it." +"There are some things that would count as workflow but are either done via :" +"doc:`/manage/trigger` or :doc:`/manage/scheduler`." msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing the update of the source name." +#: ../system/core-workflows/limitations.rst:35 +msgid "Such as (but not limited to):" msgstr "" -#: ../system/integrations/ldap/manage.rst:89 -msgid "Re-arrange LDAP source's order" +#: ../system/core-workflows/limitations.rst:37 +msgid "up- or downgrade permissions of users" msgstr "" -#: ../system/integrations/ldap/manage.rst:84 -msgid "" -"You can change the synchronization order for each source at any time. Zammad " -"will synchronize the sources from top to bottom." +#: ../system/core-workflows/limitations.rst:38 +msgid "affecting article creation or listing" msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "" -"Screencasting showing how to change the source order by using\n" -"drag and drop." +#: ../system/data-privacy.rst:2 +msgid "Data Privacy" msgstr "" -#: ../system/integrations/ldap/manage.rst:101 -msgid "Remove a source" +#: ../system/data-privacy.rst:4 +msgid "" +"For compliance with GDPR and other data privacy laws, you may wish to " +"**permanently delete users from the system**, along with **all of their " +"associated tickets**." msgstr "" -#: ../system/integrations/ldap/manage.rst:92 +#: ../system/data-privacy.rst:8 msgid "" -"If you no longer need the a LDAP source or simply want to start over, you " -"can remove them at any time. This will not remove synchronized users, data " -"synchronized or permissions." +"You can create manual deletion tasks or even automated deletion tasks for " +"tickets and users based on custom conditions via :doc:`scheduler `!" msgstr "" -#: ../system/integrations/ldap/manage.rst:98 +#: ../system/data-privacy.rst:12 msgid "" -"Not sure if you'd need the source later on? Set the source to inactive " -"instead of removing it - see *Review or edit existing source* for more." +"Access to this panel requires ``admin.data_privacy`` permissions (introduced " +"in Zammad 3.5)." msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing how to remove LDAP sources." +#: ../system/data-privacy.rst:15 +msgid "" +"On older systems that have not been updated yet, customers can also be :docs:" +"`deleted via the Zammad console `." msgstr "" -#: ../system/integrations/pgp/index.rst:2 -msgid "PGP" +#: ../system/data-privacy.rst:22 +msgid "User deletion dialog in the Data Privacy panel" msgstr "" -#: ../system/integrations/pgp/index.rst:7 +#: ../system/data-privacy.rst:22 msgid "" -"Pretty Good Privacy (PGP) is another method for secure email communication. " -"With PGP, you can exchange **signed** and **encrypted** messages with others." +"The user deletion dialog lists some of the tickets that will be removed from " +"the system along with the user." msgstr "" -#: ../system/integrations/pgp/index.rst:13 -#: ../system/integrations/smime/index.rst:17 -msgid "Signing" +#: ../system/data-privacy.rst:27 +msgid "Deleting Users via GUI" msgstr "" -#: ../system/integrations/pgp/index.rst:11 -msgid "is a proof that a message hasn't been manipulated on its way." +#: ../system/data-privacy.rst:29 +msgid "🔥 **All deletions are FINAL!**" msgstr "" -#: ../system/integrations/pgp/index.rst:13 +#: ../system/data-privacy.rst:31 +msgid "Once you click “Delete”, the action cannot be canceled or undone." +msgstr "" + +#: ../system/data-privacy.rst:33 msgid "" -"In other words, it guarantees message **integrity** and **authenticity**." +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:19 -#: ../system/integrations/smime/index.rst:22 -msgid "Encryption" +#: ../system/data-privacy.rst:36 +msgid "**The following records cannot be deleted:**" msgstr "" -#: ../system/integrations/pgp/index.rst:16 -#: ../system/integrations/smime/index.rst:20 -msgid "" -"scrambles a message so that it can only be unscrambled by the intended " -"recipient." +#: ../system/data-privacy.rst:38 +msgid "your own account" msgstr "" -#: ../system/integrations/pgp/index.rst:19 -msgid "" -"In other words, it guarantees message **privacy** and **data security**." +#: ../system/data-privacy.rst:39 +msgid "the system's last remaining administrator account" msgstr "" -#: ../system/integrations/pgp/index.rst:25 -msgid "Screenshot of ticket creation with encrypt and sign buttons" +#: ../system/data-privacy.rst:42 +msgid "Step 1: Find a User / Confirm Deletion" msgstr "" -#: ../system/integrations/pgp/index.rst:25 -msgid "" -"Once PGP has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " -"appear in the ticket composer." +#: ../system/data-privacy.rst:44 +msgid "There are three ways to access the user deletion dialog:" msgstr "" -#: ../system/integrations/pgp/index.rst:28 -msgid "**Sign button not visible?**" +#: ../system/data-privacy.rst:51 +msgid "**from the user's profile**" msgstr "" -#: ../system/integrations/pgp/index.rst:30 -msgid "" -"Please note that the signing of emails is based on the outgoing email " -"account. That means you have to choose a group with a sender email account, " -"which has a private key assigned." +#: ../system/data-privacy.rst:0 +msgid "Accessing the user deletion dialog in a user profile" msgstr "" -#: ../system/integrations/pgp/index.rst:35 -msgid "Handling of Keys" +#: ../system/data-privacy.rst:51 +msgid "Click **Action > Delete**." msgstr "" -#: ../system/integrations/pgp/index.rst:36 -msgid "" -"To use the PGP function, you have to enable the integration (PGP) by " -"switching the toggle to *enabled*." +#: ../system/data-privacy.rst:58 +msgid "**in the “Manage > Users” Admin Panel**" msgstr "" -#: ../system/integrations/pgp/index.rst:39 -msgid "" -"You can add keys by clicking the *add key* button. The keys can be imported " -"from a file or you can paste the content of the key in the text box." +#: ../system/data-privacy.rst:0 +msgid "Accessing the user deletion dialog under “Users” in the Admin Panel" msgstr "" -#: ../system/integrations/pgp/index.rst:42 -msgid "**Which keys do I have to import?**" +#: ../system/data-privacy.rst:58 +msgid "Use the **⋮ Actions** menu for the target user." msgstr "" -#: ../system/integrations/pgp/index.rst:44 -msgid "" -"For **signing** *outgoing* emails, you have to import the private key of " -"your Zammad email account." +#: ../system/data-privacy.rst:66 ../system/data-privacy.rst:104 +msgid "**in the “System > Data Privacy” Admin Panel**" msgstr "" -#: ../system/integrations/pgp/index.rst:47 +#: ../system/data-privacy.rst:0 msgid "" -"For **encrypting** *outgoing* emails, you have to import the public key of " -"the customer's email account." +"Accessing the user deletion dialog under “Data Privacy” in the Admin Panel" msgstr "" -#: ../system/integrations/pgp/index.rst:50 +#: ../system/data-privacy.rst:65 msgid "" -"For **verifying the signature** of signed *incoming* emails, you have to " -"import the public key of the customer." +"Use the **New Deletion Task** button. Search for users by name or email " +"address." msgstr "" -#: ../system/integrations/pgp/index.rst:53 -msgid "" -"For **decrypting** of encrypted *incoming* emails, you have to import the " -"private key of your Zammad email account." +#: ../system/data-privacy.rst:79 +msgid "**Delete organizations**" msgstr "" -#: ../system/integrations/pgp/index.rst:57 -msgid "Import Keys From a File" +#: ../system/data-privacy.rst:69 +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:" msgstr "" -#: ../system/integrations/pgp/index.rst:58 -msgid "You can import keys from a file in the section **Upload key**:" +#: ../system/data-privacy.rst:0 +msgid "Deleting an organization via the user deletion dialog" msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of adding a key via file" +#: ../system/data-privacy.rst:78 +msgid "" +"If this option does not appear, make sure there are no pending deletion " +"tasks for other customers from this organization." msgstr "" -#: ../system/integrations/pgp/index.rst:64 -msgid "" -"**Supported file formats:** ASCII-armor as well as binary GPG format " -"(basically any GPG supported key format) is supported here." +#: ../system/data-privacy.rst:82 +msgid "Step 2: Monitor Deletion Job Status" msgstr "" -#: ../system/integrations/pgp/index.rst:68 -msgid "Import Keys by Pasting the Content" +#: ../system/data-privacy.rst:84 +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:" msgstr "" -#: ../system/integrations/pgp/index.rst:69 -msgid "You can also paste the key's content in the section **paste key**:" +#: ../system/data-privacy.rst:98 +msgid "**in the Activity Stream**" msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of adding a key via pasting" +#: ../system/data-privacy.rst:0 +msgid "Activity Stream showing data privacy tasks" msgstr "" -#: ../system/integrations/pgp/index.rst:75 +#: ../system/data-privacy.rst:94 msgid "" -"**Supported format:** Please note that only ASCII-armor is supported here." +"For each deleted user, the Activity Stream will be updated twice—once when " +"the task is created, and once when it's complete." msgstr "" -#: ../system/integrations/pgp/index.rst:78 -msgid "Deleting Keys" +#: ../system/data-privacy.rst:97 +msgid "" +"These notifications are only visible to users with ``admin.data_privacy`` " +"permissions." msgstr "" -#: ../system/integrations/pgp/index.rst:79 +#: ../system/data-privacy.rst:0 msgid "" -"If you want to delete a specific key, you can do it by clicking on the menu " -"in the *actions* column and select **delete**:" +"The task list within Data Privacy shows removals being in progress and " +"completed." msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of deleting a key" +#: ../system/data-privacy.rst:107 +msgid "Frequently Asked Questions" msgstr "" -#: ../system/integrations/pgp/index.rst:88 -msgid "Downloading Keys" +#: ../system/data-privacy.rst:121 +msgid "What happens if I receive an email from a deleted customer?" msgstr "" -#: ../system/integrations/pgp/index.rst:89 +#: ../system/data-privacy.rst:110 msgid "" -"If you want to download your keys, you can do this as well via corresponding " -"action buttons. Depending on the key, you can choose wether you want to " -"download the private or the public key." -msgstr "" - -#: ../system/integrations/pgp/index.rst:95 -#: ../system/integrations/smime/manage-certificates.rst:76 -msgid "Default Behavior" +"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/integrations/pgp/index.rst:96 +#: ../system/data-privacy.rst:115 msgid "" -"Here you can adjust on per group basis, if *sign* and *encryption* is on or " -"off by default. Please be aware, that agents can always override the setting " -"for each individual article." +"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**." msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Adjusting default behavior on per group basis" +#: ../system/data-privacy.rst:130 +msgid "What about user information stored in internal notes or other messages?" msgstr "" -#: ../system/integrations/pgp/index.rst:107 +#: ../system/data-privacy.rst:124 msgid "" -"Here you can see the last actions regarding signing and encryption and if " -"they were successful." +"The deletion process removes **user accounts and associated tickets only**." msgstr "" -#: ../system/integrations/pgp/index.rst:117 -msgid "**Sign button is not visible, but keys are imported.**" +#: ../system/data-privacy.rst:126 +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." msgstr "" -#: ../system/integrations/pgp/index.rst:115 -msgid "Did you choose a group in the ticket?" +#: ../system/data-privacy.rst:137 +msgid "I deleted an user and can still see a message they sent!" msgstr "" -#: ../system/integrations/pgp/index.rst:116 +#: ../system/data-privacy.rst:133 msgid "" -"Did you import a private key for the email adress, which is used for " -"outgoing emails in the group?" +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:122 -msgid "**How to obtain keys?**" +#: ../system/data-privacy.rst:141 +msgid "I removed a customer, now my reporting is off!" msgstr "" -#: ../system/integrations/pgp/index.rst:120 +#: ../system/data-privacy.rst:140 msgid "" -"You can create them yourself! There are some good tutorials on the web on " -"how to create them. Providing keys to Zammad is a prerequisite to use the " -"PGP feature." +"When removing users and their tickets, all references are removed. This also " +"affects e.g. Reporting - these information are lost." msgstr "" -#: ../system/integrations/pgp/index.rst:127 -msgid "**It says a passphrase is needed, but I haven't got one.**" +#: ../system/data-privacy.rst:145 +msgid "How long does Zammad store created tasks?" msgstr "" -#: ../system/integrations/pgp/index.rst:125 +#: ../system/data-privacy.rst:144 msgid "" -"If the key is secured with a passphrase, you have to provide it for the " -"import in Zammad. It is possible that keys may have an empty passphrase. " -"However, this is *not* recommended." +"Please see the on-premise data section of the :docs:`data privacy ` chapter." msgstr "" -#: ../system/integrations/pgp/index.rst:132 -msgid "**How do my customers get my new key?**" +#: ../system/data-privacy.rst:150 +msgid "What about re-assigned tickets? I want to delete them, too." msgstr "" -#: ../system/integrations/pgp/index.rst:130 +#: ../system/data-privacy.rst:148 msgid "" -"You have to provide your **public** key in advance. Your customer also has " -"to configure PGP in their email workflow and import your public key. The " -"other way round, you have to get the public key of your customer and have to " -"import it to Zammad." -msgstr "" - -#: ../system/integrations/slack.rst:2 -msgid "Slack" +"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." msgstr "" -#: ../system/integrations/slack.rst:4 -msgid "**⚠️ Deprecation warning ⚠️**" +#: ../system/data-privacy.rst:154 +msgid "Why are there so many deletion task entries, I didn't create them!" msgstr "" -#: ../system/integrations/slack.rst:6 +#: ../system/data-privacy.rst:153 msgid "" -"Zammad 7 will no longer support this dedicated Slack integration. It is " -"recommended to switch to :doc:`pre-defined webhooks ` instead. Existing Slack integrations should " -"be migrated manually before this feature is dropped." +"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." msgstr "" -#: ../system/integrations/slack.rst:14 -msgid "" -"In order to use this feature, please add a new Slack app to your Workspace. " -"The App you need is called ``Incoming WebHooks`` ." +#: ../system/integrations/checkmk/admin-panel-reference.rst:2 +msgid "Admin Panel Reference" msgstr "" -#: ../system/integrations/slack.rst:18 -msgid "Why Do I Need This Feature?" +#: ../system/integrations/checkmk/admin-panel-reference.rst:None +msgid "Screenshot of Checkmk settings overview" msgstr "" -#: ../system/integrations/slack.rst:20 +#: ../system/integrations/checkmk/admin-panel-reference.rst:12 msgid "" -"If you're already using Slack for your team communication, you'll love this " -"feature! Our Slack integration can push ticket notifications about the last " -"ticket article based on the following events:" +"Which :doc:`group ` should Checkmk tickets be assigned " +"to as a default (*i.e.,* when none is specified)?" msgstr "" -#: ../system/integrations/slack.rst:24 -msgid "on Ticket creation" +#: ../system/integrations/checkmk/admin-panel-reference.rst:15 +msgid "(Applies to :ref:`API alerts ` only.)" msgstr "" -#: ../system/integrations/slack.rst:25 -msgid "on Ticket updates" +#: ../system/integrations/checkmk/admin-panel-reference.rst:21 +msgid "Auto close" msgstr "" -#: ../system/integrations/slack.rst:26 -msgid "on reached reminders" +#: ../system/integrations/checkmk/admin-panel-reference.rst:18 +msgid "" +"Should Zammad automatically close tickets if a service has recovered on its " +"own?" msgstr "" -#: ../system/integrations/slack.rst:27 -msgid "a Ticket has escalated" +#: ../system/integrations/checkmk/admin-panel-reference.rst:21 +msgid "(Agents will receive notifications for such closures as appropriate.)" msgstr "" -#: ../system/integrations/slack.rst:28 -msgid "a Ticket is going to escalate" +#: ../system/integrations/checkmk/admin-panel-reference.rst:30 +msgid "Auto-close state" msgstr "" -#: ../system/integrations/slack.rst:30 -msgid "" -"Zammad will provide the Ticket title, a direct link to the Ticket, the event " -"type (creation, updated, escalation), the customer, time and the last " -"article that has triggered the notification." +#: ../system/integrations/checkmk/admin-panel-reference.rst:24 +msgid "What ticket state should be applied when “auto-closing” a ticket?" msgstr "" -#: ../system/integrations/slack.rst:34 +#: ../system/integrations/checkmk/admin-panel-reference.rst:26 msgid "" -"This will give you further options, as you can see e.g. escalating tickets " -"that are assigned to an agent that's e.g. absent. You can interact faster, " -"as you might see problems earlier (or even before the problem gets one)." +"You can choose from the seven built-in ticket states. If these states aren't " +"enough for you, you can :ref:`define a new ticket state ` for this purpose as well. This can be useful for tracking " +"tickets with :doc:`reports `, for example." msgstr "" -#: ../system/integrations/slack.rst:38 -msgid "" -"If needed and wanted, you can even discuss directly about the topic before " -"sending an answer to the customer. Another possible use case would be a " -"agent monitoring new agents and their answers to tickets." +#: ../system/integrations/checkmk/admin-panel-reference.rst:35 +#: ../system/integrations/cti/includes/recent-logs.include.rst:2 +#: ../system/integrations/ldap/index.rst:74 +#: ../system/integrations/pgp/index.rst:106 +msgid "Recent Logs" msgstr "" -#: ../system/integrations/slack.rst:44 -msgid "Configure the Integration" +#: ../system/integrations/checkmk/admin-panel-reference.rst:None +msgid "Screenshot of Checkmk \"Recent Logs\" section" msgstr "" -#: ../system/integrations/slack.rst:46 +#: ../system/integrations/checkmk/admin-panel-reference.rst:41 msgid "" -"First of all, please go to your slack workspace - go to administration => " -"Manage Apps. If you don't have an app yet, you can simply add a new one - " -"just search for ``Incoming WebHooks`` and customize the app to your needs." +"If you're having trouble getting Zammad and Checkmk to play nicely together, " +"this section can help you troubleshoot." msgstr "" -#: ../system/integrations/slack.rst:50 +#: ../system/integrations/checkmk/admin-panel-reference.rst:44 msgid "" -"Choose (or create) the channel Zammad should post it's information to and " -"press on \"Add Incoming WebHooks integration\". If you're ready, copy the " -"provided WebHook URL and go to your Zammad installation." +"It contains a record of the fifty most recent transactions that Zammad knows " +"about, including each one's request/response details and return status." msgstr "" -#: ../system/integrations/slack.rst:56 -msgid "" -"You need administrative rights on the Slack Workspace. The link to the app " -"directory is normally ``https://[workspace-name].slack.com/apps`` ." +#: ../system/integrations/checkmk/api-reference.rst:2 +msgid "API Reference" msgstr "" -#: ../system/integrations/slack.rst:63 +#: ../system/integrations/checkmk/api-reference.rst:4 msgid "" -"To configure the slack integration, log in to Zammad and go to Integrations " -"(System) => Slack in the admin panel." +"For most users, :ref:`the sample scripts from the Setup Guide ` will do the job just fine. But if you want more fine-grained control" +"—for instance, to create high- and low-priority tickets for different types " +"of system events—then you'll have to customize the data those scripts send " +"to Zammad." msgstr "" -#: ../system/integrations/slack.rst:66 +#: ../system/integrations/checkmk/api-reference.rst:15 msgid "" -"Here you can choose on what evens Zammad should post information about a " -"ticket to your Slack channel. Next you need to device what groups shall be " -"affected by this, as anybody with access to that specific Slack channel can " -"read at least parts of the ticket this might be a privacy issue, if you " -"select the wrong groups. The username is simply the name that Zammad uses as " -"display name inside the Slack chat. The channel defines the Slack channel " -"the information is being posted in. As last option, you can set a custom " -"icon for posting to slack." +"This custom script will automatically set all tickets it creates to **high " +"priority** and **assign them to charlie@chrispresso.com**." msgstr "" -#: ../system/integrations/slack.rst:74 -msgid "" -"When you're ready, just hit \"Submit\" and enable the integration. Zammad " -"will now post new ticket information based on the trigger you chose. Below " -"the options you have the recent log that shows the latest requests to Slack " -"for debugging if needed." +#: ../system/integrations/checkmk/api-reference.rst:32 +msgid "How Does it Work?" msgstr "" -#: ../system/integrations/slack.rst:81 +#: ../system/integrations/checkmk/api-reference.rst:34 msgid "" -"If you leave the Icon URL empty, Zammad will use the Zammad logo instead. " -"The icon should be a square PNG file." +"There are two kinds of data you can pass to the API, both in the form of key-" +"value pairs:" msgstr "" -#: ../system/integrations/slack.rst:90 -msgid "" -"The following figure shows how it will look if you choose to receive updates " -"on created and updated tickets. On every post Zammad sends to the Slack " -"channel, you can create new threads to discuss about the new article." +#: ../system/integrations/checkmk/api-reference.rst:44 +msgid "Checkmk parameters" msgstr "" -#: ../system/integrations/slack.rst:96 +#: ../system/integrations/checkmk/api-reference.rst:38 msgid "" -"If you just want to keep track of soon escalating or already escalated " -"tickets, it will look the the following figure. Zammad changes the color in " -"front of the post so you can easily see the state of the ticket." +"are required, and make up the **contents** of the resulting tickets/" +"articles. They also determine whether an event creates a new ticket or " +"updates/closes an existing one." msgstr "" -#: ../system/integrations/slack.rst:102 +#: ../system/integrations/checkmk/api-reference.rst:42 msgid "" -"If you change the state, Zammad will also put information on what state the " -"ticket gets and (if pending state) the date until it pends. You'll also " -"recognize the color codes in front of posts on slack, as they are exact the " -"same the ticket state colors you'll see in Zammad!" +"These are the only values used in the sample scripts. **Use them as-is**; " +"technically, they can be customized, but it's hard to imagine a good reason " +"for it." msgstr "" -#: ../system/integrations/smime/index.rst:2 -msgid "S/MIME" +#: ../system/integrations/checkmk/api-reference.rst:52 +msgid "Ticket attributes" msgstr "" -#: ../system/integrations/smime/index.rst:11 +#: ../system/integrations/checkmk/api-reference.rst:47 msgid "" -"S/MIME is the most widely-supported method for secure email communication. " -"With S/MIME, you can exchange **signed** and **encrypted** messages with " -"others." +"are optional, and can be used to **adjust settings** on newly created " +"tickets (*e.g.,* set the owner, group, priority, or state)." msgstr "" -#: ../system/integrations/smime/index.rst:15 +#: ../system/integrations/checkmk/api-reference.rst:50 msgid "" -"is proof that a message hasn't been tampered with or sent by an impersonator." +"If you want to customize your Checkmk alert script, do it with these. Simply " +"add an extra “form” option for each one (``-F \"key=value\"``) to your " +"script's ``curl`` command line, as in the example above." msgstr "" -#: ../system/integrations/smime/index.rst:17 +#: ../system/integrations/checkmk/api-reference.rst:54 +msgid "💡 **It's just an API endpoint!**" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:56 msgid "" -"In other words, it guarantees a message's **integrity** and **authenticity**." +"When using Checkmk integration, messages need to be formatted in a certain " +"way, but that *doesn't mean the messages actually have to come from Checkmk*." msgstr "" -#: ../system/integrations/smime/index.rst:22 -msgid "In other words, it guarantees **privacy** and **data security**." +#: ../system/integrations/checkmk/api-reference.rst:59 +msgid "" +"If you use another monitoring tool that's not officially supported by " +"Zammad, there's probably a way to make it work with your Checkmk callback " +"URL." msgstr "" -#: ../system/integrations/smime/index.rst:28 -msgid "Screencast demo of S/MIME features for both new tickets and replies" +#: ../system/integrations/checkmk/api-reference.rst:63 +msgid "Checkmk Parameters" msgstr "" -#: ../system/integrations/smime/index.rst:28 +#: ../system/integrations/checkmk/api-reference.rst:65 msgid "" -"Once S/MIME has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " -"appear in the ticket composer." +"When a notification is received, Zammad creates a new article containing the " +"details of the event that triggered it:" msgstr "" -#: ../system/integrations/smime/index.rst:32 -msgid ":doc:`🔪 Prerequisites `" +#: ../system/integrations/checkmk/api-reference.rst:None +msgid "Checkmk article body" msgstr "" -#: ../system/integrations/smime/index.rst:31 +#: ../system/integrations/checkmk/api-reference.rst:72 msgid "" -"New to S/MIME? This section helps you to find certificate providers and " -"points out Limitations." +"These details come from the fields listed below, which correspond to " +"parameters provided by Checkmk (``$NOTIFY_*``)." msgstr "" -#: ../system/integrations/smime/index.rst:35 -msgid ":doc:`📝 Manage Certificates `" +#: ../system/integrations/checkmk/api-reference.rst:75 +msgid "**Required fields are marked with an asterisk (\\*).**" msgstr "" -#: ../system/integrations/smime/index.rst:35 -msgid "Add and download certificates; configure group default behaviors." +#: ../system/integrations/checkmk/api-reference.rst:79 +msgid "event_id\\*" msgstr "" -#: ../system/integrations/smime/index.rst:38 -msgid ":doc:`😦 Troubleshooting `" +#: ../system/integrations/checkmk/api-reference.rst:78 +msgid "" +"A unique ID for the system event. (``$NOTIFY_SERVICEPROBLEMID`` / " +"``$NOTIFY_HOSTPROBLEMID``)" msgstr "" -#: ../system/integrations/smime/index.rst:38 -msgid "Took a wrong turn? About recent logs and common issues." +#: ../system/integrations/checkmk/api-reference.rst:86 +msgid "host\\*" msgstr "" -#: ../system/integrations/smime/index.rst:43 +#: ../system/integrations/checkmk/api-reference.rst:82 msgid "" -"For more details on how S/MIME integration works on the agent side, see the :" -"user-docs:`user docs `." -msgstr "" - -#: ../system/integrations/smime/manage-certificates.rst:2 -msgid "Manage Certificates" +"The hostname of the system that the event originated from. " +"(``$NOTIFY_HOSTNAME``)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:4 +#: ../system/integrations/checkmk/api-reference.rst:85 msgid "" -"S/MIME is **disabled by default**. Enable it to start adding certificates." +"Used to determine if a new event belongs to an existing ticket. Also used in " +"the subject line of the resulting article (“ is ”)." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:10 -msgid "Dialogue to add new certificates or private keys" +#: ../system/integrations/checkmk/api-reference.rst:96 +msgid "service" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:10 +#: ../system/integrations/checkmk/api-reference.rst:89 msgid "" -"Manage certificates in the Admin Panel under **System > Integrations > S/" -"MIME**. Certificates may be pasted in as plain text or uploaded from a file." +"The name of the service that the event originated from. " +"(``$NOTIFY_SERVICEDESC``)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:14 -msgid "Add Certificate Data" +#: ../system/integrations/checkmk/api-reference.rst:92 +msgid "Used to determine if a new event belongs to an existing ticket." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:36 -msgid "Add Certificate" +#: ../system/integrations/checkmk/api-reference.rst:94 +#: ../system/integrations/checkmk/api-reference.rst:110 +msgid "Displayed as ``-`` when omitted." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:17 -msgid "" -"Import public-key certificates for both your own organization and your " -"contacts." +#: ../system/integrations/checkmk/api-reference.rst:104 +msgid "state\\*" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:19 +#: ../system/integrations/checkmk/api-reference.rst:99 msgid "" -"You can also add a bunch of certificates in one go by providing a single " -"file with all relevant certificates." -msgstr "" - -#: ../system/integrations/smime/manage-certificates.rst:22 -msgid "🕵️ **ALWAYS verify certificates in-person or over the phone!**" +"The current state of the service or host in question. " +"(``$NOTIFY_SERVICESTATE`` / ``$NOTIFY_HOSTSTATE``)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:24 +#: ../system/integrations/checkmk/api-reference.rst:102 msgid "" -"The whole point of signatures is to alert you when someone is trying to " -"pretend to be someone they're not. Never accept a certificate from someone " -"online without verifying it first." +"Used to detect when a ticket should be auto-closed (*i.e.,* on ``OK``/" +"``UP``). Also used in the subject line of the resulting article (“ is " +"”)." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:28 -msgid "📇 **What about trusted certificate authorities?**" +#: ../system/integrations/checkmk/api-reference.rst:110 +msgid "text" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:30 +#: ../system/integrations/checkmk/api-reference.rst:107 msgid "" -"In some cases (e.g. when dealing with large enterprises), you may be given a " -"certificate for an entire CA, rather than a single contact. Add it here to " -"trust *all* certificates issued by that CA." +"The output of the process that triggered the event. " +"(``$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:35 +#: ../system/integrations/checkmk/api-reference.rst:121 msgid "" -"Commercial CAs can usually be verified online. Zammad does not include a " -"list of built-in, trusted CAs." +"The Object Manager attribute panel displays built-in and custom\n" +"attribute names." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:57 -msgid "Add Private Key" +#: ../system/integrations/checkmk/api-reference.rst:121 +msgid "Find a complete list of ticket attributes in the Object Manager." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:39 +#: ../system/integrations/checkmk/api-reference.rst:123 msgid "" -"Once you've added a public-key certificate, you can import its matching " -"private key." +"Ticket attributes are entirely optional, and can be used to customize the " +"tickets that Checkmk creates. (Note that these attributes will be ignored if " +"a new event belongs to an existing ticket.)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:42 +#: ../system/integrations/checkmk/api-reference.rst:128 msgid "" -"Private keys are for **your own organization only**; never ask your contacts " -"for their private keys." +"Why would you want to do this? Maybe you have only one IT guy, and all " +"system monitoring issues should be automatically assigned to him. Or, maybe " +"you're creating multiple notification rules so that database outages take " +"higher priority than disk space warnings." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:0 -msgid "" -"S/MIME integration showing configured certificates and possible issues with " -"Logging" +#: ../system/integrations/checkmk/api-reference.rst:135 +msgid "In most cases, you'll probably want to set one of the following:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:50 -msgid "" -"A note is displayed on certificates with a matching private key (see line 2)." -msgstr "" +#: ../system/integrations/checkmk/api-reference.rst:137 +msgid "group" +msgstr "grupp" -#: ../system/integrations/smime/manage-certificates.rst:52 -msgid "📤 **Certificates and private keys must be uploaded separately.**" +#: ../system/integrations/checkmk/api-reference.rst:139 +msgid "state" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:54 +#: ../system/integrations/checkmk/api-reference.rst:140 +msgid "priority" +msgstr "prioritet" + +#: ../system/integrations/checkmk/api-reference.rst:142 msgid "" -"If your certificate and private key are bundled together in the same file or " -"PEM block, import it twice (once using each button)." +"but in practice, you can set almost any attribute, including :doc:`custom " +"ones you created through the Object Manager `." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:57 -msgid "Please note that bulk imports of private keys are not possible." +#: ../system/integrations/checkmk/api-reference.rst:145 +msgid "Please note that the following attributes are **not customizable**:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:60 -msgid "Download Certificate Data" -msgstr "" - -#: ../system/integrations/smime/manage-certificates.rst:62 -msgid "" -"You can download the earlier provided certificates and private keys at any " -"time from your Zammad instance." -msgstr "" +#: ../system/integrations/checkmk/api-reference.rst:147 +msgid "title" +msgstr "ämne" -#: ../system/integrations/smime/manage-certificates.rst:65 -msgid "" -"Please note that passphrase-protected private keys stay protected and when " -"you download them, you have to know the passphrase to use them after " -"downloading." +#: ../system/integrations/checkmk/api-reference.rst:148 +msgid "id" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:73 -msgid "Dialogue to download certificates or private keys" +#: ../system/integrations/checkmk/api-reference.rst:149 +msgid "ticket number" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:73 -msgid "Download stored certificates and their keys" +#: ../system/integrations/checkmk/api-reference.rst:151 +msgid "created_by_id" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:78 -msgid "" -"The ticket composer will set all outgoing messages to **signed and " -"encrypted** by default (assuming the required certificates exist)." +#: ../system/integrations/checkmk/api-reference.rst:152 +msgid "updated_by_id" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:82 -msgid "These defaults can be modified on a per-group basis:" +#: ../system/integrations/checkmk/api-reference.rst:155 +msgid "Which Values Can Be Set?" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:None -msgid "Zammad allowing to choose the default behavior on per group basis" +#: ../system/integrations/checkmk/api-reference.rst:157 +msgid "😵 **Invalid values → unpredictable behavior**" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:89 +#: ../system/integrations/checkmk/api-reference.rst:159 msgid "" -"Of course, agents can always manually change these settings on each email " -"they send out." +"If you provide a value that Zammad doesn't understand (*e.g.,* ``-F " +"\"priority=high\"``), it's not always clear what will happen. In some cases, " +"a ticket will be created with the default values instead - but in others, it " +"may not be created at all!" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:4 -msgid "A certificate *and* private key for your own organization" +#: ../system/integrations/checkmk/api-reference.rst:164 +msgid "So what values does Zammad understand, then? Well, it depends..." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:6 -msgid "" -"(Use this to ✒️ **sign outgoing messages** and 🔓 **decrypt incoming " -"messages**.)" +#: ../system/integrations/checkmk/api-reference.rst:168 +msgid "Use an email address or username:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:9 -msgid "" -"Certificates belonging your contacts, or their issuing certificate authority " -"(CA)" +#: ../system/integrations/checkmk/api-reference.rst:190 +msgid "group & priority" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:11 -msgid "" -"(Use these to ✅ **verify incoming message signatures** and 🔒 **encrypt " -"outgoing messages**.)" +#: ../system/integrations/checkmk/api-reference.rst:175 +msgid "Refer to the dropdown menus in the ticket pane:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:14 -msgid "🙋 **I'm new to S/MIME. Where can I get a certificate?**" +#: ../system/integrations/checkmk/api-reference.rst:0 +msgid "See possible values for certain attributes in the ticket pane." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:16 -msgid "" -"The easiest way to get certificates is to buy an annual subscription through " -"a commercial CA, such as:" +#: ../system/integrations/checkmk/api-reference.rst:187 +msgid "🙅 **Ticket state CANNOT be set this way!**" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:19 +#: ../system/integrations/checkmk/api-reference.rst:189 msgid "" -"`Sectigo (formerly Comodo) `_" -msgstr "" - -#: ../system/integrations/smime/prerequisites.rst:20 -msgid "`Secorio `_" -msgstr "" - -#: ../system/integrations/smime/prerequisites.rst:21 -msgid "`GlobalSign `_" +"Why? Because ``-F \"state=...\"`` is already used :ref:`as a Checkmk " +"parameter `." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:23 -msgid "(Zammad is not affiliated with these CAs in any way.)" +#: ../system/integrations/checkmk/api-reference.rst:222 +msgid "Everything Else" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:25 +#: ../system/integrations/checkmk/api-reference.rst:193 msgid "" -"You can also generate your own self-signed certificates, but the process is " -"complicated and usually 🙅 **involves extra work for your contacts**." +"To set any other attributes, it helps to know your way around the :docs:" +"`rails console `. Valid values are those that you can " +"set with a string:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:29 -msgid "" -"Bear in mind that 🤝 **S/MIME only works if the other party is using it, too." -"**" +#: ../system/integrations/checkmk/api-reference.rst:218 +msgid "These values can then be passed directly to the API:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:32 -msgid "Certificate and Private Key Checks on Upload" +#: ../system/integrations/checkmk/index.rst:16 +msgid "How does it work?" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:34 -msgid "" -"The certificate and public key validation is based on the ``X509v3`` " -"extensions." +#: ../system/integrations/checkmk/index.rst:2 +msgid "Checkmk" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:49 -msgid "Uploading a *client certificate*?" +#: ../system/integrations/checkmk/index.rst:4 +msgid "" +"`Checkmk `_ is a powerful IT monitoring tool that can " +"send real-time status alerts to Zammad via email or REST API. Set these " +"alerts up in Checkmk, and Zammad will automatically create, update, and " +"close tickets based on the health of your system:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:41 -msgid "The following attributes are required then:" +#: ../system/integrations/checkmk/index.rst:14 +msgid "Screenshot of ticket created by Checkmk notifications" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:39 -msgid "Subject Alternative Name (at least one email address has to be present)" +#: ../system/integrations/checkmk/index.rst:14 +msgid "Multiple alerts, same ticket." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:40 -msgid "Key Usage (``Digital Signature`` and/or ``Key Encipherment``)" +#: ../system/integrations/checkmk/setup-guide.rst:2 +msgid "Setup Guide" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:41 -msgid "Public key algorithm (either ``RSA`` or ``EC``)" +#: ../system/integrations/checkmk/setup-guide.rst:4 +msgid "" +"Whenever the Checkmk integration is enabled, Zammad listens for messages on " +"its API and over email. As long as those messages follow the required " +"format, Zammad will create new tickets (or find and update existing ones) " +"based on the message contents." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:43 +#: ../system/integrations/checkmk/setup-guide.rst:10 msgid "" -"The Extended Key Usage attribute is optional. If the certificate provides " -"the named attribute, than it must contain the value ``E-mail Protection``." +"That means that “setting up Checkmk integration” is simply a matter of " +"**adding configuration to your Checkmk site**: telling it when to send these " +"messages and what to say. To do that, you'll need to create a new " +"**notification rule** (see `Checkmk's official docs `_ for help with that)." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:46 +#: ../system/integrations/checkmk/setup-guide.rst:17 msgid "" -"Please note that any usable email adress has to be prefixed with ``email:`` " -"or ``rfc822:``." +"As part of this new rule, you'll have to choose a **notification method** " +"(*i.e.,* a script to execute whenever the rule is triggered). This script " +"will be written by you (samples below), and contain the logic for sending " +"API/email messages to Zammad:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:49 -msgid "The named public key algorithms are mandatory for private keys as well." +#: ../system/integrations/checkmk/setup-guide.rst:26 +msgid "Checkmk \"New Rule\" dialog" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:54 -msgid "Uploading a *CA certificate*?" +#: ../system/integrations/checkmk/setup-guide.rst:26 +msgid "" +"Find your custom scripts in the Checkmk WATO under **Notifications > New " +"Rule > Notification Method**." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:52 +#: ../system/integrations/checkmk/setup-guide.rst:29 msgid "" -"In the case of an uploaded CA certificate, providing the value ``CA:TRUE`` " -"in the attribute *Basic Contstraints*, the previously mentioned attributes " -"are not verified." +"Once you're done setting up your new rule, you're all set! New tickets " +"should start coming in and auto-updating any time your rule is triggered." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:56 +#: ../system/integrations/checkmk/setup-guide.rst:33 msgid "" -"In general, the usage of any expired (``Not After``) or not yet valid (``Not " -"Before``) certificate is denied for outgoing emails." +"(If you need help troubleshooting, be sure to check the :ref:`checkmk-recent-" +"logs`.)" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:59 -msgid "Example certificate:" +#: ../system/integrations/checkmk/setup-guide.rst:38 +msgid "API Alerts" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:85 +#: ../system/integrations/checkmk/setup-guide.rst:40 msgid "" -"Please note that Zammad will distrust senders by default. This means that " -"you're always required to provide certificate data, no matter if for signing " -"or encrypting." +"To add these scripts in the Checkmk WATO, copy them into your Checkmk " +"installation directory and make them executable. (Be sure to replace the " +"``zammad.example.com`` callback URL with the one found in your admin panel.)" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:89 -msgid "This is by design and can't be adjusted." +#: ../system/integrations/checkmk/setup-guide.rst:60 +msgid "Service notification" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:4 +#: ../system/integrations/checkmk/setup-guide.rst:46 msgid "" -"All of the system's latest S/MIME activity is displayed in the **Recent " -"Logs** section." +"For updates on the status of the software running on your server (*e.g.,* " +"postgres)." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:11 -msgid "Sample entries of in- and outgoing S/MIME related emails." +#: ../system/integrations/checkmk/setup-guide.rst:75 +msgid "Host notification" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:11 -msgid "" -"Logs report the status and details of all mail, both incoming and outgoing, " -"that used signing/verification or encryption/decryption." +#: ../system/integrations/checkmk/setup-guide.rst:63 +msgid "For updates on the status of the server itself." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:14 +#: ../system/integrations/checkmk/setup-guide.rst:77 +msgid "🤔 **What's with all the env vars?**" +msgstr "" + +#: ../system/integrations/checkmk/setup-guide.rst:79 msgid "" -"This log does **not** include email sent by :doc:`triggers ` or the :doc:`scheduler `. For those, check your " -"``production.log``." +"Whenever Checkmk runs these scripts, it needs to provide some information " +"about the event that triggered the notification. This information is passed " +"in the form of these ``$NOTIFY_*`` environment variables." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:20 -msgid "Common Issues" +#: ../system/integrations/checkmk/setup-guide.rst:85 +msgid "" +"You can specify additional parameters to pass to the script when you're " +"setting up your notification rule, but the ones you see here are all " +"provided by default." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:30 -msgid "I received a signed/encrypted email before I set up S/MIME integration" +#: ../system/integrations/checkmk/setup-guide.rst:90 +msgid "Email Alerts" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:23 +#: ../system/integrations/checkmk/setup-guide.rst:94 msgid "" -"No problem. Once S/MIME has been enabled and the appropriate certificates " -"have been added, agents will be prompted to retry verification/decryption on " -"matching emails." +"🐞 **There are known bugs** in Zammad's processing of email from Checkmk. " +"This section will be completed once they have been resolved. (Learn more at " +"GitHub issues `#2377 `_ & " +"`#2180 `_.)" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:0 -msgid "Screenshot of user prompt to retry decryption" +#: ../system/integrations/checkmk/setup-guide.rst:100 +msgid "In the meantime, we encourage you to set up API alerts instead." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:38 -msgid "The 🔒 **Encrypt** button is disabled" +#: ../system/integrations/clearbit.rst:2 +msgid "Clearbit" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:33 -msgid "Have you added the recipient's certificate?" +#: ../system/integrations/clearbit.rst:4 +msgid "" +"With our Clearbit integration, you can easily enrich the information " +"provided by Zammad. If the customers or agents email address is known to " +"Clearbit, it will share all information it has regarding the user with " +"Zammad. Those information can include the following:" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:34 -msgid "Are you sure the recipient's certificate is valid?" +#: ../system/integrations/clearbit.rst:9 +msgid "Avatar" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:35 -msgid "Have you checked your ``production.log`` for more details?" +#: ../system/integrations/clearbit.rst:10 +msgid "Address information" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:37 -msgid "" -"If encryption doesn't work in the composer, it won't work in :doc:`triggers " -"` or the :doc:`scheduler ` either!" +#: ../system/integrations/clearbit.rst:11 +msgid "Website information" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:42 -msgid "The ✅ **Sign** button is disabled" +#: ../system/integrations/clearbit.rst:12 +msgid "A BIO (as Note by default)" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:41 +#: ../system/integrations/clearbit.rst:14 msgid "" -"Have you added **both the certificate and private key** for your " -"organization?" +"If needed, you can add further custom objects and add mappings to them, so " +"the Clearbit information can be filled within the database. In general you " +"can get any information from Clearbit, as long as you have a mapping to an " +"Zammad object." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:42 +#: ../system/integrations/clearbit.rst:21 msgid "" -"Does the email address on the certificate match the email address of the " -"agent/group composing the email?" +"Clearbit does have a mapping of fields like LDAP and Exchange have, but does " +"not \"win\" against Zammad information. This means that if you have e.g. the " +"last name field filled in already and Clearbit has other information on " +"that, it will not be updated." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:45 -msgid "Error: “Fingerprint already taken”" +#: ../system/integrations/clearbit.rst:26 +msgid "" +"However: If let's say the last name has been set by Clearbit and Zammad " +"notices that the last name on the Clearbit source has changed, Zammad will " +"also update this value." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:45 -msgid "Are you sure you haven't added this certificate already?" +#: ../system/integrations/clearbit.rst:33 +msgid "" +"The configuration of Clearbit is really easy and done fast! Just login to " +"your Clearbit-Account, go to \"API\" and copy the secret-API-Key." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:48 -msgid "Error: “❌ invalid byte sequence in UTF-8”" +#: ../system/integrations/clearbit.rst:38 +msgid "" +"Now change to your Zammad instance, go to Integrations (System) -> Clearbit " +"in the admin panel. Paste your API-Key into the API-Key-Field and decide if " +"Zammad should create unknown Organizations automatically, if the user does " +"not have one yet (and Clearbit knows it). The shared option decides if the " +"new organizations Zammad creates with Clearbit should be shared ones." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:48 -msgid "Please ensure to provide PEM formatted certificate and keys." +#: ../system/integrations/clearbit.rst:47 +msgid "" +"If you're unsure what option to choose, better stick with \"no\". You can " +"also learn more about :doc:`/manage/organizations/index`." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:49 -msgid "Did you check if the provided file is a valid certificate or key?" +#: ../system/integrations/clearbit.rst:52 +msgid "" +"The Mapping option works similar to the mapping within the Exchange and LDAP " +"sync. You can add further mappings for e.g. custom fields if you need more " +"information that Clearbit can provide." msgstr "" -#: ../system/integrations/zabbix.rst:2 -msgid "Zabbix Integration" +#: ../system/integrations/clearbit.rst:58 +msgid "" +"If you want to add more Clearbit fields and want to learn more about " +"available fields on their API, you can take a look at their `API " +"documentation `_." msgstr "" -#: ../system/integrations/zabbix.rst:5 +#: ../system/integrations/clearbit.rst:62 msgid "" -"This guide describes how to integrate your Zabbix 5.4 installation with " -"Zammad using the Zabbix webhook feature. This guide will provide " -"instructions on setting up a media type, a user and an action in Zabbix." +"If you're happy with the above chosen Settings and your mapping, just save " +"the changes and enable Clearbit integration. Zammad will now start polling " +"the Clearbit API as users contact you." msgstr "" -#: ../system/integrations/zabbix.rst:12 -msgid "Zammad with enabled HTTP Token Authentication" +#: ../system/integrations/clearbit.rst:68 +msgid "" +"Zammad does not synchronize with Clearbit on a regular basis, but on demand " +"if needed. This saves API calls." msgstr "" -#: ../system/integrations/zabbix.rst:13 -msgid "Zabbix version 5.4 or higher" +#: ../system/integrations/clearbit.rst:73 +msgid "" +"Below the Settings and Mappings, you'll find our Integration log. You can " +"see what requests Zammad sent to Clearbit and also the APIs Response." msgstr "" -#: ../system/integrations/zabbix.rst:16 -msgid "Setting up a Zammad" +#: ../system/integrations/clearbit.rst:78 +msgid "" +"By the way, you can also view the API log on the Clearbit website - the " +"information seen is basically the same." msgstr "" -#: ../system/integrations/zabbix.rst:18 -msgid "Enable **API Token Access** in Settings > System > API." +#: ../system/integrations/clearbit.rst:84 +msgid "Example When Adding a User" msgstr "" -#: ../system/integrations/zabbix.rst:20 +#: ../system/integrations/clearbit.rst:86 msgid "" -"Create a **new user** for a Zabbix alerter with an **email address** and " -"create a personal user token with **ticket.agent** permissions." -msgstr "" - -#: ../system/integrations/zabbix.rst:24 -msgid "Zabbix Webhook Configuration" +"To show you how fast information is added, we added a small Screencast " +"below. This shows the creation of the User Alex from Clearbit. As we already " +"set the last name of Alex to \"X\", Zammad did not update it. What Zammad " +"did was to add further information it received from Clearbit." msgstr "" -#: ../system/integrations/zabbix.rst:27 -msgid "Create a Global Macro" +#: ../system/integrations/cti/generic.rst:2 +msgid "CTI (generic)" msgstr "" -#: ../system/integrations/zabbix.rst:29 +#: ../system/integrations/cti/includes/introduction.include.rst:1 msgid "" -"Before setting up the **Webhook**, you need to setup the global macro " -"**{$ZABBIX.URL}**, which must contain the **URL** to the **Zabbix frontend**." +"This integration enables Zammad to provide a caller log to your agents. With " +"this your agents can greet your customers by their name and are supported by " +"Zammad with automatically opening a new ticket dialog or the user profile." msgstr "" -#: ../system/integrations/zabbix.rst:33 +#: ../system/integrations/cti/includes/introduction.include.rst:6 msgid "" -"In the **Administration** > **Media types** section, import the `Template`_." -msgstr "" - -#: ../system/integrations/zabbix.rst:38 -msgid "Open the added **Zammad** media type and set:" +"Click the toggle next to the heading to activate or deactivate this " +"integration." msgstr "" -#: ../system/integrations/zabbix.rst:40 -msgid "**zammad\\_access\\_token** to the your **Personal User Token**" +#: ../system/integrations/cti/includes/introduction.include.rst:9 +msgid "" +"If you want to learn more on how your agents can use this function, please " +"refer the :user-docs:`user documentation `." msgstr "" -#: ../system/integrations/zabbix.rst:41 +#: ../system/integrations/cti/includes/introduction.include.rst:14 msgid "" -"**zammad\\_url** to the **frontend URL** of your **Zammad** installation" +"Automatically opening new ticket dialogues or user profiles requires agent " +"to extension mapping - see more below." msgstr "" -#: ../system/integrations/zabbix.rst:43 -msgid "**zammad\\_customer** to your **Zammad user email**." +#: ../system/integrations/cti/includes/introduction.include.rst:20 +msgid "Please note the following limitations to reduce confusion later on:" msgstr "" -#: ../system/integrations/zabbix.rst:44 -msgid "" -"**zammad\\_enable\\_tags** to **true** or **false** to enable or disable " -"trigger tags. **Important**: if you enable tag support, each tag is set with " -"a separate request." +#: ../system/integrations/cti/includes/introduction.include.rst:22 +msgid "CTI integrations provide caller log functions only." msgstr "" -#: ../system/integrations/zabbix.rst:48 +#: ../system/integrations/cti/includes/introduction.include.rst:23 msgid "" -"If you want to prioritize issues according to **severity** values in Zabbix, " -"you can define mapping parameters:" +"This integration does not provide any VoIP functionalities; you can't make " +"phone calls from within Zammad." msgstr "" -#: ../system/integrations/zabbix.rst:51 -msgid "**severity\\_**: Zammad priority ID" +#: ../system/integrations/cti/includes/introduction.include.rst:25 +msgid "" +"If your browser supports ``tel``-URLs, you can click on phone numbers for " +"automatic dialing. This requires additional software / configuration on your " +"agent's computers." msgstr "" -#: ../system/integrations/zabbix.rst:53 -msgid "Click the **Update** button to save the **Webhook** settings." +#: ../system/integrations/cti/generic.rst:9 +#: ../system/integrations/cti/placetel.rst:14 +#: ../system/integrations/cti/sipgate.rst:14 +msgid "Please provide the following requirements:" msgstr "" -#: ../system/integrations/zabbix.rst:55 +#: ../system/integrations/cti/generic.rst:11 msgid "" -"To receive notifications in **Zammad**, you need to create a **Zabbix user** " -"and add **Media** with the **Zammad** type." +"A telephone system that supports webhooks (outbound) (best option are those " +"that allow customizing the calls)." msgstr "" -#: ../system/integrations/zabbix.rst:58 -msgid "" -"For **Send to**: enter any text, as this value is not used, but is required." +#: ../system/integrations/cti/generic.rst:13 +msgid "A unique Call-ID during the call session." msgstr "" -#: ../system/integrations/zabbix.rst:61 -msgid "" -"For more information, use the `Zabbix documentation `_." +#: ../system/integrations/cti/generic.rst:14 +msgid "Call event data (both numbers and direction)." msgstr "" -#: ../system/maintenance.rst:2 -msgid "Maintenance" +#: ../system/integrations/cti/generic.rst:15 +msgid "Your Zammad instance must be reachable for your telephony system." msgstr "" -#: ../system/maintenance.rst:4 +#: ../system/integrations/cti/generic.rst:17 msgid "" -"Zammad comes with a maintenance mode that you can use for e.g. updating the " -"instance or changing settings while restricting availability and functions." -msgstr "" - -#: ../system/maintenance.rst:13 -msgid "Mode" +"If you want to learn more on what kind of requests are supported by Zammad " +"and what it expects, please consult our :docs:`CTI-API documentation `." msgstr "" -#: ../system/maintenance.rst:8 -msgid "The mode setting allows you to enable or disable the maintenance mode." +#: ../system/integrations/cti/generic.rst:22 +#: ../system/integrations/cti/placetel.rst:27 +#: ../system/integrations/cti/sipgate.rst:30 +msgid "Available Settings" msgstr "" -#: ../system/maintenance.rst:10 -msgid "Defaults to *off*." +#: ../system/integrations/cti/generic.rst:29 +#: ../system/integrations/cti/placetel.rst:41 +#: ../system/integrations/cti/sipgate.rst:40 +msgid "Endpoint Settings" msgstr "" -#: ../system/maintenance.rst:12 +#: ../system/integrations/cti/generic.rst:25 msgid "" -"The maintenance mode will restrict access to administrative roles only. This " -"means agents and customers are logged off." +"Zammad will list your generic CTI endpoint here. It contains a unique token " +"so ensure to keep this URL save." msgstr "" -#: ../system/maintenance.rst:23 -msgid "@Login" +#: ../system/integrations/cti/generic.rst:28 +msgid "" +"You'll need this endpoint for your PBX to talk to Zammad, see :docs:`CTI-API " +"documentation `." msgstr "" -#: ../system/maintenance.rst:16 +#: ../system/integrations/cti/includes/important-dont-forget-saving.include.rst:3 msgid "" -"This setting allows you to provide a login message within a green banner " -"above the login screen. Click into the green banner in the settings page to " -"adjust your message. To activate the message, activate the *@Login* setting." +"All following options **do not save automatically**. Always use the Save " +"button on the lower end of the integration page!" msgstr "" -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing the default login message within the\n" -"settings page" -msgstr "" - -#: ../system/maintenance.rst:26 -msgid "" -"Send an informative message to **all active sessions**. This comes handy to " -"inform your agents e.g. about mayor outages or to force reloads after " -"configuration changes." -msgstr "" - -#: ../system/maintenance.rst:31 -msgid "This is the messages title (slightly bigger than the normal message)." -msgstr "" - -#: ../system/maintenance.rst:34 -msgid "The text you want to provide to your logged in sessions." -msgstr "" - -#: ../system/maintenance.rst:39 -msgid "Reload application" -msgstr "" - -#: ../system/maintenance.rst:37 -msgid "" -"Selecting this option will change the message acceptance button from *Close* " -"(with nothing happening) to *Continue session*, which forces the application " -"to reload." -msgstr "" - -#: ../system/maintenance.rst:43 -msgid "" -"If you have customers that are logged in to Zammad, they'll also be notified " -"if they're active in that moment." -msgstr "" - -#: ../system/maintenance.rst:48 -msgid "Example without reload application" -msgstr "" - -#: ../system/maintenance.rst:52 -msgid "" -"Message setting within Zammad's admin settings without ticket reload " -"application setting." -msgstr "" - -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing the send message settings without ticket\n" -"reload application set" -msgstr "" - -#: ../system/maintenance.rst:61 ../system/maintenance.rst:85 -msgid "" -"The modal all other active sessions will see upon pressing *Send to clients*." -msgstr "" - -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing modal caused by maintenance's message\n" -"without reload application ticket" -msgstr "" - -#: ../system/maintenance.rst:72 -msgid "Example with reload application" -msgstr "" - -#: ../system/maintenance.rst:76 -msgid "" -"Message setting within Zammad's admin settings with ticket reload " -"application setting." -msgstr "" - -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing the send message settings with ticket\n" -"reload application set" -msgstr "" - -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing modal caused by maintenance's message\n" -"with reload application ticket" +#: ../system/integrations/cti/generic.rst:43 +#: ../system/integrations/cti/placetel.rst:49 +#: ../system/integrations/cti/sipgate.rst:52 +msgid "Call Settings" msgstr "" -#: ../system/monitoring.rst:2 -msgid "Monitoring" +#: ../system/integrations/cti/generic.rst:39 +#: ../system/integrations/cti/placetel.rst:49 +#: ../system/integrations/cti/sipgate.rst:37 +#: ../system/integrations/cti/sipgate.rst:50 +msgid "Inbound" msgstr "" -#: ../system/monitoring.rst:4 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:1 msgid "" -"This function is only available in self hosted instances. If you use Zammad " -"in our cloud, we are monitoring the system on our own and take steps to fix " -"potential problems directly." +"This option allows you to block specific incoming caller IDs. It allows you " +"to temporarily reject e.g. spam callers without having to contact providers " +"or PBX administrators." msgstr "" -#: ../system/monitoring.rst:11 -msgid "" -"On the monitoring page, you can see the current health state of Zammad under " -"\"*Current Status*\" at the bottom. This can be useful if you want to have a " -"look if everything is up and running. As an example, you could have a look " -"in the monitoring when you assume that some emails aren't processed from " -"Zammad." +#: ../system/integrations/cti/includes/inbound-calls.include.rst:11 +msgid "Caller ID to block" msgstr "" -#: ../system/monitoring.rst:17 -msgid "**Can't receive an email and the monitoring response is \"healthy\"?**" +#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 +msgid "Provide caller IDs to block in ``E.164`` format." msgstr "" -#: ../system/monitoring.rst:19 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:8 msgid "" -"Zammad will just inform you about unprocessable emails. This is not the case " -"for oversized emails. You can adjust the maximum email size in :doc:`../" -"channels/email/settings`." -msgstr "" - -#: ../system/monitoring.rst:24 -msgid "Monitoring API" +"Your telephony system has to support this function. Zammad will send a " +"``reject`` response which will cause your telephony system to hang up the " +"call. To callers this usually will feel like the line is busy." msgstr "" -#: ../system/monitoring.rst:26 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:14 msgid "" -"Beside the indication in the monitoring page, you can also use an external " -"monitoring tool to monitor Zammad's health. To request the health of Zammad, " -"you need to provide the API key (token) to the external monitoring tool. You " -"can copy the token from the \"*Current Token*\" field as well as the whole " -"API endpoint of your system (\"*Health Check*\" field), in which the API " -"token is already included." -msgstr "" - -#: ../system/monitoring.rst:37 -msgid "Screenshot showing Current Token and Health Check" +"Provide a meaningful note for your fellow administrators to remind yourself " +"why you've chosen to block the number." msgstr "" -#: ../system/monitoring.rst:37 -msgid "Screenshot showing Token and Health Check" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:17 +#: ../system/integrations/cti/sipgate.rst:40 +msgid "Outbound" msgstr "" -#: ../system/monitoring.rst:39 +#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:1 msgid "" -"In addition to that, you can reset the auto-generated token to make sure " -"that already configured monitoring systems won't work anymore. So, please " -"use this \"*Reset*\" button only if you know what you do!" -msgstr "" - -#: ../system/monitoring.rst:44 -msgid "Example Output" -msgstr "" - -#: ../system/monitoring.rst:0 -msgid "No issues found" +"In many cases you may want to use a different caller ID depending on the " +"destination you're calling. This may apply due to specific connection rates " +"to other countries or because you want your customer to feel you're calling " +"from the same country." msgstr "" -#: ../system/monitoring.rst:48 ../system/monitoring.rst:60 -msgid "**Indicator in Zammad**:" +#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:6 +msgid "This option expects ``E.164`` number formats." msgstr "" -#: ../system/monitoring.rst:0 -msgid "Screenshot showing monitoring with no issues" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 +msgid "Destination caller ID" msgstr "" -#: ../system/monitoring.rst:54 ../system/monitoring.rst:66 -msgid "**API response**::" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:5 +msgid "The caller ID or number you're trying to call." msgstr "" -#: ../system/monitoring.rst:0 -msgid "Issues were found" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:7 +msgid "You can use wildcards for e.g. country specific outbound numbers like:" msgstr "" -#: ../system/monitoring.rst:0 -msgid "Screenshot showing monitoring with issues" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:9 +msgid "``49*`` for Germany" msgstr "" -#: ../system/objects.rst:2 -msgid "Objects" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:10 +msgid "``4930*`` for Berlin / Germany landlines" msgstr "" -#: ../system/objects.rst:4 -msgid "" -"In Zammad you can add your own fields to tickets, users, organizations and " -"even groups (these are called \"objects\"). This can be useful if you need " -"to add further information to a ticket or any other object in Zammad and the " -"information doesn't fit in any existing field." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 +msgid "``33*`` for France" msgstr "" -#: ../system/objects.rst:11 -msgid "" -"Try to avoid deleting attributes (and disable them instead) as Zammad might " -"run into unexpected conditions if they are referenced somewhere." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:15 +msgid "Set Outbound caller ID" msgstr "" -#: ../system/objects.rst:16 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:14 msgid "" -"Here's an overview of object attributes. On the upper right you can add new " -"attributes. By default, there will be no custom fields - standard attributes " -"will be grayed out, you can't delete or change those. You can edit custom " -"attributes (they are displayed in black font and have a trash bin on the " -"right side) just by clicking on them." +"The outbound caller ID to set (the number your customer sees on his display) " +"in ``E.164`` number format." msgstr "" -#: ../system/objects.rst:24 -msgid "" -"Attributes you add to Zammad, no matter if they have default values or not, " -"will not update existing information. This means a new ticket field " -"technically will be empty unless you populate it." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 +msgid "Provide a short description for fellow administrators." msgstr "" -#: ../system/objects.rst:28 +#: ../system/integrations/cti/includes/generic-cti-support-note.includes.rst:3 msgid "" -"Especially in ticket scope this also means that newly added attributes will " -"be indicated as \"changed\" to agents that view the ticket. This may " -"interfere with Zammad's tabs behavior." +"This option requires your PBX to send a specific request to Zammad *before " +"dialing*. Please consult the :docs:`CTI API ` in case " +"you're not sure." msgstr "" -#: ../system/objects.rst:40 -msgid "Ordering Attributes" +#: ../system/integrations/cti/generic.rst:52 +#: ../system/integrations/cti/placetel.rst:54 +#: ../system/integrations/cti/sipgate.rst:59 +msgid "Other Settings" msgstr "" -#: ../system/objects.rst:42 +#: ../system/integrations/cti/includes/other-settings-intro.include.rst:1 msgid "" -"Since Zammad introduced :doc:`/system/core-workflows` the need to have a " -"custom positioning for attributes has become more important than ever." +"Below you can find all available additional settings for this CTI " +"integration. For your overview we're sorting them by appearance and " +"reference their description first." msgstr "" -#: ../system/objects.rst:45 -msgid "" -"To adjust the position of such an attribute, simply click on the attribute " -"entry in question, scroll down and adjust the position number. Please note " -"that you cannot change the positioning of default attributes." +#: ../system/integrations/cti/includes/default-caller-id.include.rst:2 +#: ../system/integrations/cti/includes/default-caller-id.include.rst:1 +msgid "Default caller ID for outbound calls" msgstr "" -#: ../system/objects.rst:49 -msgid "" -"In case two attributes have the same position value, Zammad will sort " -"alphabetically by name automatically." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:16 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:15 +msgid "Shown records in caller log" msgstr "" -#: ../system/objects.rst:None +#: ../system/integrations/cti/includes/records-caller-log.include.rst:2 msgid "" -"Screenshot showing custom attribute entries ordered in between default ones" +"Allows you to set the number of shown caller log entries for all users. You " +"can choose from the following values:" msgstr "" -#: ../system/objects.rst:56 -msgid "Updating Database After Adding or Editing Attributes" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:5 +msgid "60 (default)" msgstr "" -#: ../system/objects.rst:58 -msgid "" -"When adding or changing attributes, Zammad will not apply the changes " -"instantly, but instead shows you the changed attributes first. If you're " -"ready to go, just click on \"Update database\" to apply the changes to " -"Zammad. If you made a mistake or just want to discard your changes, click " -"\"Discard changes\"." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:6 +msgid "120" msgstr "" -#: ../system/objects.rst:64 -msgid "" -"After applying the changes with \"Update Database\", a restart of Zammad is " -"**mandatory**. If you don't perform it, you may experience unexpected " -"behavior or even errors. You may want to do this kind of configuration " -"during maintenance windows." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:7 +msgid "180" msgstr "" -#: ../system/objects.rst:72 -msgid "" -"Changes on objects require you to update the database to apply these changes." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:8 +msgid "240" msgstr "" -#: ../system/objects.rst:75 -msgid "**🤓 Service restarts can be automated**" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:9 +msgid "300" msgstr "" -#: ../system/objects.rst:0 -msgid "Hosted environments automatically restart for you." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:11 +msgid "**🥵 Potential performance issue**" msgstr "" -#: ../system/objects.rst:0 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:13 msgid "" -"If you're using a self-hosted installation you can use :docs:`environment " -"variables `" +"Setting this setting higher than 60 may cause serious performance issues on " +"very busy instances. Keep in mind that this setting causes Zammad to poll " +"and send up to 300 records to *all active agent sessions* in very short time " +"periods." msgstr "" -#: ../system/objects.rst:82 -msgid "System Attributes" +#: ../system/integrations/cti/generic.rst:73 +msgid "Caller Log Filter" msgstr "" -#: ../system/objects.rst:84 +#: ../system/integrations/cti/generic.rst:55 msgid "" -"Zammad comes with pre-configured attributes. Some of them can't be edited " -"via UI (or at all). This is required for proper operation of Zammad and not " -"a bug." -msgstr "" - -#: ../system/objects.rst:90 -msgid "Ticket State" +"This function allows you to provide call information based on e.g. queues " +"only to agents that really need the information." msgstr "" -#: ../system/objects.rst:92 +#: ../system/integrations/cti/generic.rst:58 msgid "" -"If the pre-configured states aren't enough for you or you want to change " -"them, you can do so by clicking on the cogwheel icon in the state row in the " -"ticket tab. But you should be careful when changing pre-configured states. " -"This can lead to unwanted behavior in some cases." -msgstr "" - -#: ../system/objects.rst:None -msgid "Screenshot showing highlighted ticket state attribute" +"Why? If you have a team for several countries or departments, you don't want " +"to bug your agents from other departments. Leaving these options empty will " +"fallback to showing everything to everyone." msgstr "" -#: ../system/objects.rst:122 -msgid "Handling of states" +#: ../system/integrations/cti/generic.rst:64 +msgid "Destination caller ID or Queue" msgstr "" -#: ../system/objects.rst:102 +#: ../system/integrations/cti/generic.rst:63 msgid "" -"In the state configuration screen, you can add new states, disable states or " -"change states." +"This depends on your PBX and usually is either a queue ID, phone number or " +"extension." msgstr "" -#: ../system/objects.rst:0 -msgid "Screenshot showing table of default ticket states" +#: ../system/integrations/cti/generic.rst:69 +msgid "Agents" msgstr "" -#: ../system/objects.rst:110 +#: ../system/integrations/cti/generic.rst:67 msgid "" -"To add a new state, click on the \"New Ticket State\" button in the top " -"right corner. To change an existing state, simply click on the affected " -"state. This opens an edit dialog." +"Select the agents that are responsible for the group. These agents will then " +"see caller log entries and call notifications fitting to said queue." msgstr "" -#: ../system/objects.rst:114 +#: ../system/integrations/cti/generic.rst:0 msgid "" -"You can also clone a state or set them to \"Default for new tickets\" or " -"\"Default for follow-ups\" by clicking on the ⁝ action button and select the " -"desired function." +"Screenshot showing the caller log filter table with pre filled sample data" msgstr "" -#: ../system/objects.rst:118 +#: ../system/integrations/cti/includes/recent-logs.include.rst:6 msgid "" -"*Default for new tickets* means that this state is used for every newly " -"created ticket." +"With recent logs Zammad allows you to view the latest calls for the CTI " +"functionality. This usually comes in handy, when you're looking for errors." msgstr "" -#: ../system/objects.rst:121 +#: ../system/integrations/cti/includes/recent-logs.include.rst:0 msgid "" -"*Default for follow-ups* means that this state is used if the ticket is re-" -"opened after it was closed." +"Screenshot showing several incoming requests within Recent logs section." msgstr "" -#: ../system/objects.rst:171 -msgid "Ticket state in detail" +#: ../system/integrations/cti/includes/recent-logs.include.rst:16 +msgid "I'm just here to clear floats up." msgstr "" -#: ../system/objects.rst:125 +#: ../system/integrations/cti/includes/recent-logs.include.rst:20 msgid "" -"Below you can find a description for each field and option. Please head over " -"to the :ref:`example ` to see the edit dialog." +"By clicking on the entry of interest, Zammad will provide more details on " +"the call in question. You'll see the payload it received and also the " +"response that was sent." msgstr "" -#: ../system/objects.rst:129 +#: ../system/integrations/cti/includes/recent-logs.include.rst:0 msgid "" -"This is the name of the state and what you and your agents are seeing when " -"choosing a state somewhere (e.g. in tickets, trigger configuration)." +"Screenshot showing detailed information of a specific log entry of recent " +"logs" msgstr "" -#: ../system/objects.rst:137 -msgid "" -"There are different state types you can choose from. By default, Zammad " -"comes with one state per state type." +#: ../system/integrations/cti/includes/recent-logs.include.rst:31 +msgid "x" msgstr "" -#: ../system/objects.rst:140 -msgid "" -"**new**: for states for tickets that are new and it hasn't been worked on " -"them" +#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 +#: ../system/integrations/cti/includes/troubleshooting.include.rst:9 +msgid "My Phone page stays blank, signalling does work..." msgstr "" -#: ../system/objects.rst:142 +#: ../system/integrations/cti/includes/troubleshooting.include.rst:5 msgid "" -"**open**: for states for tickets that are in progress and agents are working " -"on them" +"If you've made sure that signalling works (check Recent logs) and your " +"Caller Log still stays empty, please ensure that you only configured one CTI " +"integration version. Specifically defining more than one agent mapping on " +"the different integration variants will be the issue." msgstr "" -#: ../system/objects.rst:144 -msgid "**merged**: for states for tickets that are merged with other tickets" +#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 +msgid "Clear the not needed agent mapping and reload your browser page." msgstr "" -#: ../system/objects.rst:145 +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:1 msgid "" -"**pending reminder**: for states for tickets that are in progress and you " -"want to set a reminder. (default example: *pending reminder*)" +"By mapping your agents extension to their existing Zammad users, Zammad can " +"provide a new ticket dialog or open the user profile for the agent that " +"picks up the call." msgstr "" -#: ../system/objects.rst:147 +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:5 msgid "" -"**pending action**: for states for tickets that are waiting for a specified " -"time and then change their state (default example: *pending close*)" +"This speeds up ticket aiding, no matter if it's for existing tickets or new " +"ones!" msgstr "" -#: ../system/objects.rst:150 +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:8 msgid "" -"**closed**: for states for tickets that are finished and do not need to be " -"processed further" +"To see it work from the agent's perspective, have a look on :user-docs:`user " +"documentation `." msgstr "" -#: ../system/objects.rst:153 +#: ../system/integrations/cti/placetel.rst:2 +msgid "Placetel CTI" +msgstr "" + +#: ../system/integrations/cti/placetel.rst:16 +msgid "You need an administrative Placetel account for your organization." +msgstr "" + +#: ../system/integrations/cti/placetel.rst:17 +#: ../system/integrations/cti/sipgate.rst:20 msgid "" -"⚠️ Choosing the correct state type is important! If you are in doubt, have a " -"look on the default states and their types!" +"Your Zammad instance must be allowed to communicate to external services." msgstr "" -#: ../system/objects.rst:158 -msgid "Ignore escalation" +#: ../system/integrations/cti/placetel.rst:18 +msgid "Placetel must be able to reach your Zammad instance." msgstr "" -#: ../system/objects.rst:157 +#: ../system/integrations/cti/placetel.rst:22 +msgid ":doc:`provider-configurations/placetel`" +msgstr "" + +#: ../system/integrations/cti/placetel.rst:21 msgid "" -"Here you can define whether tickets of this state will count to escalation " -"time or not." +"Learn how to configure Placetel to enable Zammad and Placetel to communicate " +"with each other." msgstr "" -#: ../system/objects.rst:161 +#: ../system/integrations/cti/placetel.rst:32 msgid "" -"You can create a note for the state to inform other admins about the state. " -"This has no effect on tickets." +"The here listed endpoint settings are relevant for the :doc:`integration " +"configuration with Placetel `." msgstr "" -#: ../system/objects.rst:165 -msgid "Set the state to *active* or *inactive*." +#: ../system/integrations/cti/placetel.rst:37 +#: ../system/integrations/i-doit.rst:53 +msgid "Endpoint" msgstr "" -#: ../system/objects.rst:167 +#: ../system/integrations/cti/placetel.rst:36 msgid "" -"it is technically possible to set all states to inactive. To keep Zammad " -"working in such a case, the inactive flag of one of the states is ignored." +"This endpoint will be required for the Zammad integration within the " +"Placetel web interface." msgstr "" -#: ../system/objects.rst:194 -msgid "Ticket state example" +#: ../system/integrations/cti/placetel.rst:41 +msgid "API Token" msgstr "" -#: ../system/objects.rst:174 +#: ../system/integrations/cti/placetel.rst:40 msgid "" -"Let's assume we want to create a new state which indicates that the ticket " -"has to wait for a response of a third party (e.g. service contractor or " -"manufacturer) and we want to to be able to set a reminder." +"You'll receive this token within the ``Web API`` menu. Make sure to copy " +"this value, it's only shown once!" msgstr "" -#: ../system/objects.rst:178 -msgid "" -"First we give the new state a proper name. In this example we call it " -"\"waiting for manufacturer\"." +#: ../system/integrations/cti/placetel.rst:71 +#: ../system/integrations/cti/sipgate.rst:77 +msgid "Phone Extension to Agent Mapping" msgstr "" -#: ../system/objects.rst:181 -msgid "" -"As state type we choose \"pending reminder\". This indicates that the ticket " -"is still open and we can set a reminder. This reminder can be useful if our " -"manufacturer sometimes isn't responding or we want to remind him to give us " -"an answer." +#: ../system/integrations/cti/placetel.rst:0 +msgid "Screenshot showing sample user mappings in between Placetel and Zammad" msgstr "" -#: ../system/objects.rst:186 +#: ../system/integrations/cti/placetel.rst:64 msgid "" -"We choose \"no\" for \"ignore escalation\" because we want to escalate the " -"tickets even if we are waiting on the manufacturer's feedback." +"You can find your agents Placetel username combination required within ⚙️ PBX " +"→ VoIP destinations. Within the \"Advanced settings\" section you're looking " +"for \"SIP user name\" and \"SIP server\"." msgstr "" -#: ../system/objects.rst:189 -msgid "The **result** in the creation dialog will look like this:" +#: ../system/integrations/cti/placetel.rst:68 +msgid "Combine these two like so: ``@``." msgstr "" -#: ../system/objects.rst:0 -msgid "Screenshot showing ticket state creation dialog with example" +#: ../system/integrations/cti/placetel.rst:0 +msgid "Sample VoIP credentials for a Placetel user" msgstr "" -#: ../system/objects.rst:197 ../system/objects.rst:199 -msgid "Ticket Priority" +#: ../system/integrations/cti/provider-configurations/placetel.rst:2 +msgid "Setup Placetel connection for Zammad" msgstr "" -#: ../system/objects.rst:199 ../system/objects.rst:201 +#: ../system/integrations/cti/provider-configurations/placetel.rst:6 msgid "" -"If the pre-configured priorities aren't enough for you or you want to change " -"them, you can do so by clicking on the cogwheel icon in the priority row in " -"the ticket tab:" +"This configuration step requires a *full* administrative Placetel account. " +"You may receive forbidden error messages with Placetel in case your " +"permissions are not high enough." msgstr "" -#: ../system/objects.rst:None -msgid "Screenshot showing highlighted ticket priority attribute" +#: ../system/integrations/cti/provider-configurations/placetel.rst:10 +msgid "" +"The following actions can be configured via the `Placetel web interface " +"`_." msgstr "" -#: ../system/objects.rst:224 ../system/objects.rst:226 -msgid "Handling of priorities" +#: ../system/integrations/cti/provider-configurations/placetel.rst:29 +msgid "Step 1: Activate Zammad integration" msgstr "" -#: ../system/objects.rst:208 ../system/objects.rst:210 +#: ../system/integrations/cti/provider-configurations/placetel.rst:14 msgid "" -"In the priority configuration screen, you can add new priorities, disable " -"priorities or change priorities." +"Within Integrations, scroll down to Partner integrations and select Zammad." msgstr "" -#: ../system/objects.rst:0 -msgid "Screenshot showing table of default ticket priorities" +#: ../system/integrations/cti/provider-configurations/placetel.rst:17 +msgid "" +"You can alternatively filter by \"Ticket Systems\" to reduce the number of " +"entries on the page. You'll still want to look for Partner integrations. 🤓" msgstr "" -#: ../system/objects.rst:216 ../system/objects.rst:218 +#: ../system/integrations/cti/provider-configurations/placetel.rst:21 msgid "" -"To add a new priority, click on the \"New Priority\" button in the top right " -"corner. To change an existing priority, simply click on the affected " -"priority. This opens an edit dialog." +"Within the Zammad integration now press \"Activate\". A new tab ``API`` " +"becomes available - open this tab." msgstr "" -#: ../system/objects.rst:220 ../system/objects.rst:222 +#: ../system/integrations/cti/provider-configurations/placetel.rst:24 msgid "" -"You can also clone a priority or set them to \"Default for new tickets\" by " -"clicking on the ⁝ action button and select the desired function." +"Now tick \"Enable Call Control / Notify API\" and paste the Placetel " +"endpoint from your Zammad instance into the field \"URL of your API " +"endpoint\". Save to apply the settings" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "Screencast showing how to activate the Zammad integration" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:51 +msgid "Step 2: Generate API Token for Placetel" msgstr "" -#: ../system/objects.rst:223 ../system/objects.rst:225 +#: ../system/integrations/cti/provider-configurations/placetel.rst:32 msgid "" -"*Default for new tickets* means that this priority is used for every newly " -"created ticket." +"Go back to the integrations page and scroll down to \"Web API\". Generate a " +"new API token by using the \"Create a new API token\" button." msgstr "" -#: ../system/objects.rst:246 ../system/objects.rst:248 -msgid "Priorities in detail" +#: ../system/integrations/cti/provider-configurations/placetel.rst:37 +msgid "" +"If you already generated a token either use your existing token or reset it " +"by using above mentioned button. Placetel will ask you to conform this reset." msgstr "" -#: ../system/objects.rst:227 ../system/objects.rst:229 -msgid "Below you can find a description for each field and option." +#: ../system/integrations/cti/provider-configurations/placetel.rst:41 +msgid "" +"Please keep in mind that existing API scripts may no longer work due to " +"token resets!" msgstr "" -#: ../system/objects.rst:230 ../system/objects.rst:232 +#: ../system/integrations/cti/provider-configurations/placetel.rst:44 msgid "" -"This is the name of the priority and what you and your agents are seeing " -"when choosing a priority somewhere (e.g. in tickets, trigger configuration)." +"Copy the provided API token and insert it into the \"API Token\" field " +"within Zammad's Placetel integration." msgstr "" -#: ../system/objects.rst:240 ../system/objects.rst:242 -msgid "Highlight color" +#: ../system/integrations/cti/provider-configurations/placetel.rst:47 +msgid "" +"Apply your changes by using the \"Save\" button on the bottom of the " +"Placetel integration page and activate the Placetel integration." msgstr "" -#: ../system/objects.rst:235 ../system/objects.rst:237 +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 msgid "" -"Switch between *Low priority* (light blue), *High priority* (red) and - " -"(default). This affects the displayed color for ticket titles in overviews." +"Screencast showing how to retrieve an API token from Placetel for Zammad" msgstr "" -#: ../system/objects.rst:239 ../system/objects.rst:241 -msgid "The color options are currently limited to the mentioned options." +#: ../system/integrations/cti/provider-configurations/placetel.rst:73 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:77 +msgid "Step 3: Restrict the numbers to notify on" msgstr "" -#: ../system/objects.rst:243 ../system/objects.rst:245 +#: ../system/integrations/cti/provider-configurations/placetel.rst:54 msgid "" -"You can create a note for the priority to inform other admins about the " -"priority. This has no effect on tickets." +"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " +"the the Integrations page of the Placetel web interface, go to \"Notify " +"API\"." msgstr "" -#: ../system/objects.rst:247 ../system/objects.rst:249 -msgid "Set the priority to *active* or *inactive*." +#: ../system/integrations/cti/provider-configurations/placetel.rst:58 +msgid "" +"Lower on the page Placetel allows you to restrict the numbers to notify on. " +"You'll find this within the \"External routing API\" part." msgstr "" -#: ../system/objects/external-data-source-example.rst:2 -msgid "External Data Source" +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "" +"Screenshot showing a sample selection of phone numbers to use for the " +"Placetels notify API" msgstr "" -#: ../system/objects/external-data-source-example.rst:4 +#: ../system/integrations/cti/provider-configurations/placetel.rst:66 msgid "" -"We assume you already had a look on :doc:`types` where you can find a " -"description of the individual fields." +"This menu point also provides a API request log from Placetel view. Just " +"open \"Recent responses of your API endpoint\" to learn more." msgstr "" -#: ../system/objects/external-data-source-example.rst:7 +#: ../system/integrations/cti/provider-configurations/placetel.rst:69 msgid "" -"To reproduce this example, choose a category you want to add a custom field, " -"click on *New Attribute* and select *External data source field* under " -"*Format*." +"If you want to see Zammad's perspective, use the \"Recent Logs\" part from " +"within the Placetel integration page." msgstr "" -#: ../system/objects/external-data-source-example.rst:11 -msgid "" -"Our example story is to fetch data from an external product database. We " -"want to add our products to the tickets so that the products can be searched " -"and chosen from a list and also create a link to the product website." +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "Screenshot showing sample log entries for Placetels API calls to Zammad" msgstr "" -#: ../system/objects/external-data-source-example.rst:16 -msgid "Base configuration" +#: ../system/integrations/cti/provider-configurations/placetel.rst:77 +msgid "Step 4 (optional): Further configurations for Placetel" msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Initial steps to configure external data source object type" +#: ../system/integrations/cti/provider-configurations/placetel.rst:76 +msgid "" +"If needed, you can now configure Zammad's Placetel integration in more " +"detail. You can learn more about your options here: :ref:`Placetel " +"integration settings `." msgstr "" -#: ../system/objects/external-data-source-example.rst:23 -#: ../system/variables.rst:85 -msgid "**Example:**" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:2 +msgid "Setup Sipgate connection for Zammad" msgstr "" -#: ../system/objects/external-data-source-example.rst:25 -msgid "Name: *product*" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "" +"Sipgate has no english web interface which is why this documentation page is " +"mixing up languages badly." msgstr "" -#: ../system/objects/external-data-source-example.rst:26 -msgid "Display: *Product*" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "" +"Please also note that the availability of API addons highly depends on your " +"package trier. Usage of sipgate.io packages *is not free*, please check " +"their `pricing page `_ before!" msgstr "" -#: ../system/objects/external-data-source-example.rst:29 -msgid "External data source configuration" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:35 +msgid "Step 1: Book sipgate.io package" msgstr "" -#: ../system/objects/external-data-source-example.rst:31 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:13 +msgid "Skip to step 2 if you already have the package booked!" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:15 msgid "" -"First, enter the search URL making sure it contains ``#{search.term}`` as a " -"parameter:" +"Login to an administrative Sipgate account and navigate to " +"``Accountverwaltung``. You'll see several different options depending on " +"your booked packages. Select ``Verträge & Produkte`` to continue." msgstr "" -#: ../system/objects/external-data-source-example.rst:34 -msgid "**Example:** ``https://dummyjson.com/products/search?q=#{search.term}``" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:19 +msgid "" +"Scroll down to the section ``Zusätzliche Produkte buchen`` and look for " +"``sipgate.io`` - select this product by using the ``Produkte anzeigen``-" +"Button." msgstr "" -#: ../system/objects/external-data-source-example.rst:36 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:23 msgid "" -"After that, head down to the preview section and enter a search input for " -"the external data source." +"On the next page select either one of the ``sipgate.io`` packages or ``Push-" +"API Package Free``. Follow the dialogue by booking the addon. You'll be " +"returned to your contract overview and now should see the selected addon in " +"your list." msgstr "" -#: ../system/objects/external-data-source-example.rst:39 -msgid "**Example:** ``mac``" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:30 +msgid "" +"The availability for ``sipgate.io`` packages and their levels highly depends " +"on the overall account type and product you've booked with Sipgate." msgstr "" -#: ../system/objects/external-data-source-example.rst:41 -msgid "Then you can find a preview of the response data below:" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "" +"Screencast showing the process on how to book the required sipgate.io addon" msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of JSON response based on search term" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:52 +msgid "Step 2: Configure webhook for Zammad" msgstr "" -#: ../system/objects/external-data-source-example.rst:48 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:38 msgid "" -"We recommend using the preview to have a look on the structure. There is a " -"top-level element called ``products``. One level below, you can find the " -"attributes ``id`` and ``title``." +"Within your ``Accountverwaltung`` navicate to your product ``sipgate.io``. " +"In the newly opened tab, switch from \"Clients\" to \"Webhooks\" and paste " +"the endpoint URLs from your Zammad instance like so:" msgstr "" -#: ../system/objects/external-data-source-example.rst:52 -msgid "**Search result response based on search from example:**" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:42 +msgid "Inbound endpoint to \"Incoming\"" msgstr "" -#: ../system/objects/external-data-source-example.rst:119 -msgid "" -"To tell the remote system that the desired data is located below the " -"``products`` level, you have to put it in the field *Search result list key*." +#: ../system/integrations/cti/provider-configurations/sipgate.rst:43 +msgid "Outbound endpoint to \"Outgoing\"" msgstr "" -#: ../system/objects/external-data-source-example.rst:122 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:47 msgid "" -"After inserting ``products`` in the mentioned field, you get an extended " -"preview. You can find an additional box *Search result list* with a JSON " -"structure. This is the same response as before but stripped from the upper " -"``products`` element by the external data source." +"Ensure to select at least one call group or phoneline within \"Sources\". " +"Other wise Sipgate will not indicate any incoming or outgoing calls to " +"Zammad." msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of JSON response search result list" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "" +"Screencast showing how to add Zammad's endpoint URLs to sipgate.ios webhook " +"configuration" msgstr "" -#: ../system/objects/external-data-source-example.rst:132 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:55 msgid "" -"Now you need to provide the keys for the search result values and labels. As " -"already mentioned, we are looking for the ``id`` and the ``title`` of our " -"products. If you haven't already, it is now a good time to look at the " -"preview of the *Search result list*." +"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " +"the Webhooks → URLs section of Sipgate you can select which *sources* " +"Sipgate should notify Zammad about in- and outgoing calls." msgstr "" -#: ../system/objects/external-data-source-example.rst:197 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:59 msgid "" -"After locating our two keys, we insert them in *search result value key* " -"(``id``) and in *Search result label key* (``title``)." +"Use either specific phone lines or use the option \"Use for all phonelines " +"and groups\" to notify Zammad about all existing lines of your Sipgate " +"account." msgstr "" -#: ../system/objects/external-data-source-example.rst:200 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"Basically, we configured the external data source already and we can see a " -"table in the preview section:" +"Screenshot showing a sample selection of phone numbers to use for the " +"Sipgates webhooks API" msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of product table based on search term" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:68 +msgid "This section also allows you to enable a Debug log." msgstr "" -#: ../system/objects/external-data-source-example.rst:208 -msgid "" -"According to our example story, now just the *Link template* is missing." +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "Screenshot showing an enabled Debug log option" msgstr "" -#: ../system/objects/external-data-source-example.rst:210 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:73 msgid "" -"Please note that this is an optional feature. If you don't want to use such " -"links, of course you don't have to configure it." +"After enabling you can use the Debug log section to see all sent webhook " +"calls to Zammad. You'll also can see the response." msgstr "" -#: ../system/objects/external-data-source-example.rst:213 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"We can add now an address where additional product information can be found." +"Screenshot showing sample log entries for Sipgates webhook calls to Zammad" msgstr "" -#: ../system/objects/external-data-source-example.rst:215 -msgid "Example: ``https://your_domain.com/q=#{ticket.product}``" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:81 +msgid "Step 4 (optional): Further configurations for Sipgate" msgstr "" -#: ../system/objects/external-data-source-example.rst:217 -msgid "In the example, the parameter means:" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:80 +msgid "" +"If needed, you can now configure Zammad's Sipgate integration in more " +"detail. You can learn more about your options here: :ref:`Sipgate " +"integration settings `." msgstr "" -#: ../system/objects/external-data-source-example.rst:219 -msgid "``#{}``: \"Frame\" for the insertion of information" +#: ../system/integrations/cti/sipgate.rst:2 +msgid "Sipgate (sipgate.io)" msgstr "" -#: ../system/objects/external-data-source-example.rst:220 -msgid "``ticket``: object level, where you create your custom object" +#: ../system/integrations/cti/sipgate.rst:16 +msgid "You need an administrative Sipgate account for your organization." msgstr "" -#: ../system/objects/external-data-source-example.rst:221 -msgid "``product``: name of the (custom) object" +#: ../system/integrations/cti/sipgate.rst:17 +msgid "" +"Zammad requires a ``sipgate.io`` addon from the feature store (please note " +"that API calls are not free with Sipgate. Rates may apply and differ from " +"account to account)." msgstr "" -#: ../system/objects/external-data-source-example.rst:223 -msgid "" -"After configuring your *Link template*, there will be another column in the " -"preview. Hovering on the icons in the *Link* column will show you where it " -"forwards you." +#: ../system/integrations/cti/sipgate.rst:21 +msgid "Sipgate must be able to reach your Zammad instance." msgstr "" -#: ../system/objects/external-data-source-example.rst:232 -msgid "" -"In our example, one of the links looks like: https://your_domain.com/q=6, " -"where the 6 is the product id." +#: ../system/integrations/cti/sipgate.rst:25 +msgid ":doc:`provider-configurations/sipgate`" msgstr "" -#: ../system/objects/external-data-source-example.rst:235 -msgid "You can find more information regarding the URL in :doc:`types`." +#: ../system/integrations/cti/sipgate.rst:24 +msgid "" +"Learn how to configure Sipgate to enable Zammad and Sipgate to communicate " +"with each other." msgstr "" -#: ../system/objects/includes/adding-values-hint.include.rst:3 +#: ../system/integrations/cti/sipgate.rst:33 msgid "" -"Adding values can be tricky for first timers, don't forget to press \"➕ " -"Add\" after typing your values. Otherwise you may loose a value." +"Below endpoint settings affect the :doc:`sipgate.io configuration `." msgstr "" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:1 -#: ../system/objects/includes/reposition-values.include.rst:1 -msgid "**↕️ This field type allows the positioning of its values ↔️**" +#: ../system/integrations/cti/sipgate.rst:37 +msgid "This endpoint is required for incoming call hooks." msgstr "" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:3 -msgid "" -"In order to re-arrange the field values, first edit the field. Then you can " -"use ☰ to drag the values in question to the correct position. If you want to " -"change the layer depth, double click on ☰. With it you can cycle through the " -"available layers." +#: ../system/integrations/cti/sipgate.rst:40 +msgid "This endpoint is required for outgoing call hooks." msgstr "" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:8 -msgid "When you're ready, submit your changes to save the object attribute." +#: ../system/integrations/cti/sipgate.rst:0 +msgid "Screenshot showing sample user mappings in between Sipgate and Zammad" msgstr "" -#: :0 ../system/objects/types.rst:0 +#: ../system/integrations/cti/sipgate.rst:69 msgid "" -"Screencast showing how to re-position values on tree select like\n" -"fields" +"You can find your agent's Sipgate username within ``Accountverwaltung → " +"Benutzer``. You're looking for the SIP-ID." msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:3 -msgid "" -"In order to re-arrange the field values, edit the field and scroll below the " -"values. Make sure to tick the option \"Use custom option sort\"." +#: ../system/integrations/cti/sipgate.rst:0 +msgid "Sample VoIP credentials for a Sipgate user" msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:8 -msgid "" -"If you do not tick this field, all manual positioning you did above will be " -"lost upon saving! ☠️" +#: ../system/integrations/cti/sipgate.rst:77 +msgid "Users with several devices also have several SIP-IDs." msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:11 -msgid "" -"Now use ☰ to drag the values in question to the correct position. When " -"you're ready, submit your changes to save the object attribute." +#: ../system/integrations/elasticsearch.rst:2 +msgid "Elasticsearch (SaaS)" msgstr "" -#: :0 ../system/objects/types.rst:0 -msgid "Screencast showing how to re-position values" +#: ../system/integrations/elasticsearch.rst:4 +msgid "" +"The Elasticsearch integration allows you to create a read-only user to use " +"with your favorite reporting tool (e.g. like Grafana)." msgstr "" -#: ../system/objects/includes/url-template-hint.include.rst:3 +#: ../system/integrations/elasticsearch.rst:7 msgid "" -"This field allows using :ref:`URL fields (Link Templates) `." +"If you want to take full advantage of the Zammad reporting, have a look at " +"our :docs:`Grafana ` " +"setup page as well." msgstr "" -#: ../system/objects/permissions.rst:2 -msgid "Attribute Permissions" +#: ../system/integrations/elasticsearch.rst:11 ../system/subscription.rst:7 +msgid "**🚧 Hosted environment specific 🚧**" msgstr "" -#: ../system/objects/permissions.rst:7 +#: ../system/integrations/elasticsearch.rst:13 msgid "" -"In the object attributes configuration you can define if a field is shown " -"and if the input in the field is mandatory, separated by different screens " -"and for different :doc:`roles/permissions `." +"This integration is only available for Hosted setups. In order to use " +"Elasticsearch you'll need the **Plus** subscription." msgstr "" -#: ../system/objects/permissions.rst:17 -msgid "Screenshot shows object attribute permission table" +#: ../system/integrations/elasticsearch.rst:16 +msgid "" +"Self hosted users have all the control over their self hosted Elasticsearch " +"instances." msgstr "" -#: ../system/objects/permissions.rst:17 -msgid "" -"Some of the possible permissions and screen options for a user object " -"attribute." +#: ../system/integrations/elasticsearch.rst:None +msgid "Elasticsearch integration page on SaaS environments" msgstr "" -#: ../system/objects/permissions.rst:19 +#: ../system/integrations/elasticsearch.rst:27 msgid "" -"Based on the object context (ticket, agent, organization, user), the " -"selectable roles (to be precise: the required permissions) and screens " -"differ. Be aware that these settings aren't affecting data creation via " -"other channels than the UI." +"Please note the following limitations of Elasticsearch access on hosted " +"environments:" msgstr "" -#: ../system/objects/permissions.rst:24 -msgid "" -"If you want to have further customization possibilities, you should have a " -"look at the :doc:`core workflows `." +#: ../system/integrations/elasticsearch.rst:30 +msgid "access to the Elasticsearch index is read-only access" msgstr "" -#: ../system/objects/permissions.rst:28 -msgid "Screens" +#: ../system/integrations/elasticsearch.rst:31 +msgid "currently you're limited to user only" msgstr "" -#: ../system/objects/permissions.rst:30 +#: ../system/integrations/elasticsearch.rst:32 msgid "" -"In the table below you can find an overview about the different permissions " -"and the available screens Zammad distinguishes between." +"Reporting tools that require to write into the indexes (like Kibana) are not " +"supported" msgstr "" -#: ../system/objects/permissions.rst:37 -msgid "Screen" +#: ../system/integrations/elasticsearch.rst:34 +msgid "IP access restriction is currently not yet supported" msgstr "" -#: ../system/objects/permissions.rst:38 -msgid "Available for" +#: ../system/integrations/elasticsearch.rst:37 +msgid "Activating Elasticsearch Access" msgstr "" -#: ../system/objects/permissions.rst:40 -msgid "create" +#: ../system/integrations/elasticsearch.rst:39 +msgid "" +"By default external access to your Elasticsearch index is not active. You " +"can enable the integration at any time if needed." msgstr "" -#: ../system/objects/permissions.rst:41 ../system/objects/permissions.rst:52 -#: ../system/objects/permissions.rst:59 ../system/objects/permissions.rst:73 -msgid "admin.user" +#: ../system/integrations/elasticsearch.rst:42 +msgid "" +"Please ensure to note down the password provided - you won't have access to " +"it afterwards." msgstr "" -#: ../system/objects/permissions.rst:42 ../system/objects/permissions.rst:53 -#: ../system/objects/permissions.rst:60 -msgid "admin.organization" +#: ../system/integrations/elasticsearch.rst:None +msgid "Screencast showing activation of Elasticsearch integration" msgstr "" -#: ../system/objects/permissions.rst:43 ../system/objects/permissions.rst:54 -#: ../system/objects/permissions.rst:61 -msgid "admin.group" +#: ../system/integrations/elasticsearch.rst:51 +msgid "Connection Settings" msgstr "" -#: ../system/objects/permissions.rst:44 -msgid "Creation dialog for not yet existing data" +#: ../system/integrations/elasticsearch.rst:53 +msgid "" +"This section holds the most important general information for accessing your " +"Elasticsearch indexes - such as:" msgstr "" -#: ../system/objects/permissions.rst:45 -msgid "create_middle" +#: ../system/integrations/elasticsearch.rst:57 +msgid "A unique subdomain that does not tell your real instance URL." msgstr "" -#: ../system/objects/permissions.rst:46 ../system/objects/permissions.rst:50 -#: ../system/objects/permissions.rst:57 ../system/objects/permissions.rst:66 -#: ../system/objects/permissions.rst:70 -msgid "ticket.customer" +#: ../system/integrations/elasticsearch.rst:61 +msgid "Software" msgstr "" -#: ../system/objects/permissions.rst:47 ../system/objects/permissions.rst:51 -#: ../system/objects/permissions.rst:58 ../system/objects/permissions.rst:69 -msgid "ticket.agent" +#: ../system/integrations/elasticsearch.rst:60 +msgid "" +"The major version of the search index being used. This is required by some " +"Reporting tools like Grafana." msgstr "" -#: ../system/objects/permissions.rst:48 -msgid "Ticket create dialog (middle section)" +#: ../system/integrations/elasticsearch.rst:64 +msgid "Authentication" msgstr "" -#: ../system/objects/permissions.rst:49 -msgid "edit" +#: ../system/integrations/elasticsearch.rst:64 +msgid "The authentication type being supported. ``Basic Authentication``" msgstr "" -#: ../system/objects/permissions.rst:55 -msgid "Editing dialog for already existing data" +#: ../system/integrations/elasticsearch.rst:67 +msgid "Available Indexes" msgstr "" -#: ../system/objects/permissions.rst:56 -msgid "view" +#: ../system/integrations/elasticsearch.rst:69 +msgid "" +"Within this section we're displaying the -in our opinion- most important " +"indexes for a Zammad instance." msgstr "" -#: ../system/objects/permissions.rst:62 -msgid "View-only dialog for already existing data" +#: ../system/integrations/elasticsearch.rst:72 +msgid "" +"If you require all indexes or our listing is not good enough for you, point " +"your browser to the URL we're providing and append ``/_aliases?" +"pretty=true``. The result should look like this: ``https://.zammad.com/" +"_aliases?pretty=true``." msgstr "" -#: ../system/objects/permissions.rst:64 -msgid "(e.g. user or organization from search)" +#: ../system/integrations/elasticsearch.rst:77 +msgid "" +"Your browser will automatically ask for your credentials - you'll then see " +"something like this:" msgstr "" -#: ../system/objects/permissions.rst:65 -msgid "signup" +#: ../system/integrations/elasticsearch.rst:125 +msgid "Credentials" msgstr "" -#: ../system/objects/permissions.rst:67 -msgid "Sign-up screen for new customers" +#: ../system/integrations/elasticsearch.rst:127 +msgid "" +"Within this section Zammad displays your available users. The password is " +"provided once (upon activation) and cannot be retrieved after that." msgstr "" -#: ../system/objects/permissions.rst:68 -msgid "invite_customer" +#: ../system/integrations/elasticsearch.rst:131 +msgid "" +"If you need to change or reset your Elasticsearch user password, use the " +"\"Reset password\" button in the credentials table. Doing so creates a brand " +"new password for the account in question. This change is immediate, keep in " +"mind that this may affect third party tools connected to your instance." msgstr "" -#: ../system/objects/permissions.rst:71 +#: ../system/integrations/exchange.rst:2 +msgid "Exchange" +msgstr "" + +#: ../system/integrations/exchange.rst:4 msgid "" -"Customer invitation screen (from :doc:`First Steps ` area)" +"With Zammad's Exchange integration, you can easily use existing address " +"books without having to update more than one source." msgstr "" -#: ../system/objects/permissions.rst:72 -msgid "invite_agent" +#: ../system/integrations/exchange.rst:7 +msgid "" +"However, you should refrain from syncing all addresses, as the results may " +"not be what you expect (Exchange collects huge amounts of addresses). A " +"central address book of your company to sync makes more sense, as you can " +"ensure that Zammad gets only the data you need and want. Apart from this, it " +"is even not possible to sync the Global Address List (GAL) of your Exchange " +"system with Zammad." msgstr "" -#: ../system/objects/permissions.rst:74 +#: ../system/integrations/exchange.rst:16 msgid "" -"Agent invitation screen (from :doc:`First Steps ` area)" +"**Exchange and LDAP:** The exchange sync can be overruled by Zammad's LDAP " +"integration. If you have the same users in both sources, the LDAP version " +"will always be Zammad's pick." msgstr "" -#: ../system/objects/permissions.rst:78 -msgid "Screen Options" +#: ../system/integrations/exchange.rst:19 +msgid "" +"**One way sync:** the Exchange sync is one way. Exchange => Zammad. Changes " +"to your users inside of Zammad might be overwritten by the Exchange sync." msgstr "" -#: ../system/objects/permissions.rst:80 +#: ../system/integrations/exchange.rst:24 msgid "" -"For the different screens you can select \"show\" and \"required\" options." +"To configure Exchange integration, simply go to the System > Integrations > " +"Exchange in the admin panel. Press \"change\" and follow the wizard for " +"adding the needed Exchange information to Zammad. On the last two steps " +"Zammad will ask you for the address book(s) and your desired attribute " +"mapping. By default, Zammad only maps email address, first- and lastname. " +"Technically, you can map any Exchange object to a Zammad user object (this " +"also works for custom objects!)." msgstr "" -#: ../system/objects/permissions.rst:82 -msgid "**shown:** Show (check) or hide (uncheck) a field." +#: ../system/integrations/exchange.rst:35 +msgid "" +"If the SSL verification fails while connecting to Exchange, Zammad will ask " +"you to turn it off temporarily." msgstr "" -#: ../system/objects/permissions.rst:83 +#: ../system/integrations/exchange.rst:38 msgid "" -"**required:** Set a field to mandatory (check). Forces users (via UI and " -"API) to populate the field." +"Please be aware that **turning off SSL verification is a security risk**. It " +"should only be used temporarily or for testing purposes. If turned off, " +"there is no verification of the certificate, which means that every " +"presented certificate will be accepted." msgstr "" -#: ../system/objects/types.rst:7 -msgid "Example external data source" +#: ../system/integrations/exchange.rst:43 +msgid "" +"After pressing Continue, Zammad will check if the configuration is okay. You " +"can then enable Exchange and start your first sync. The sync will then run " +"hourly - if you need to change mappings or the address book(s), you can " +"change the configuration at any time." msgstr "" -#: ../system/objects/types.rst:2 -msgid "Attribute types" +#: ../system/integrations/exchange.rst:50 +msgid "" +"After the sync has finished, you can find the new Exchange contacts under " +"\"Users\". Zammad integrates them just as normal users." msgstr "" -#: ../system/objects/types.rst:4 +#: ../system/integrations/exchange.rst:55 msgid "" -"When adding a new object attribute, you can choose between the following " -"attribute types." +"In some cases you might see unique IDs as \"Login\" instead of the email " +"address. This is normal and doesn't affect the login or email mapping for " +"that entry." msgstr "" -#: ../system/objects/types.rst:14 +#: ../system/integrations/github.rst:4 msgid "" -"You cannot change the attribute format / type as soon as it is applied. If " -"you no longer need an object attribute, consider disabling it instead of " -"removing." +"Use GitHub integration to track GitHub issues directly within Zammad " +"tickets. Add issue hyperlinks and get a live summary of metadata like status " +"(open/closed), assignee, labels, and more." msgstr "" -#: ../system/objects/types.rst:18 -msgid "**What about the translation of my attributes?**" +#: ../system/integrations/github.rst:8 +msgid "Please note that our GitHub integration does not support pull requests." msgstr "" -#: ../system/objects/types.rst:20 -msgid "" -"For some attribute types you can decide if they should be translatable or " -"not. To be precise, it works only for the selectable fields because the " -"possible choices are known and limited. For the following attribute types, " -"you can set the translatable flag:" +#: ../system/integrations/github.rst:None +msgid "Integration page for GitHub" msgstr "" -#: ../system/objects/types.rst:25 -msgid "*Boolean field*" +#: ../system/integrations/github.rst:18 +msgid "" +"In your GitHub settings, create a new API token under **Developer settings > " +"Personal access tokens > Generate new token**. Leave the **Scopes** section " +"empty." msgstr "" -#: ../system/objects/types.rst:26 -msgid "*Single selection field*" +#: ../system/integrations/github.rst:0 ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to create a new API token" msgstr "" -#: ../system/objects/types.rst:27 -msgid "*Multiple selection field*" +#: ../system/integrations/github.rst:27 +msgid "Create a new API key with no scopes/privileges." msgstr "" -#: ../system/objects/types.rst:28 -msgid "*Single tree selection field*" +#: ../system/integrations/github.rst:29 +msgid "🔒 **Will this work for private repos?**" msgstr "" -#: ../system/objects/types.rst:29 -msgid "*Multiple tree selection field*" +#: ../system/integrations/github.rst:31 +msgid "" +"No. To link private repo issues, **use the** ``repo`` **scope instead**. " +"Bear in mind that the resulting token will have `lots of permissions that it " +"doesn't actually need `_, which presents a security risk if your token ever falls into " +"the wrong hands." msgstr "" -#: ../system/objects/types.rst:31 +#: ../system/integrations/github.rst:37 msgid "" -"For these types, you can find an additional field *Translate field contents*:" +"Unfortunately, because of how GitHub's OAuth token scopes are set up, this " +"is the only way to link issues on private repos." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Screenshot showing translatable attribute types" +#: ../system/integrations/github.rst:40 +msgid "Enter your new API token in Zammad and enable GitHub integration." msgstr "" -#: ../system/objects/types.rst:38 -msgid "Screenshot with example of translatable attribute type" +#: ../system/integrations/github.rst:0 +msgid "Screencast showing how to configure Zammad's GitHub integration" msgstr "" -#: ../system/objects/types.rst:45 -msgid "Boolean field" +#: ../system/integrations/github.rst:47 +msgid "" +"Use the default API endpoint (``https://api.github.com/graphql``) unless " +"you're using GitHub Enterprise Server." msgstr "" -#: ../system/objects/types.rst:41 +#: ../system/integrations/github.rst:50 msgid "" -"Provides a drop-down field with display values for ``true`` and ``false``. " -"Setting a default is mandatory." +"Once completed, a new GitHub issues tab will appear in the ticket pane. 🎉" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Boolean fields" +#: ../system/integrations/github.rst:59 ../system/integrations/gitlab.rst:52 +msgid "Token verification is taking a long time" msgstr "" -#: ../system/objects/types.rst:55 -msgid "Date field" +#: ../system/integrations/github.rst:56 ../system/integrations/gitlab.rst:49 +msgid "" +"Slight delays are normal (<2 min.), especially for systems under heavy load." msgstr "" -#: ../system/objects/types.rst:48 -msgid "Provides a date picker field and does not allow default values." +#: ../system/integrations/github.rst:58 +msgid "" +"Self-hosted administrators, please check your network settings to ensure " +"that your Zammad server can reach ``api.github.com``." msgstr "" -#: ../system/objects/types.rst:52 -msgid "Default time diff (hours)" +#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 +msgid "I reloaded the page and now the API token is gone" msgstr "" -#: ../system/objects/types.rst:51 +#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 msgid "" -"This setting helps the user by highlighting the day from now plus the " -"provided value. It *does not* pre-fill the field." -msgstr "" - -#: ../system/objects/types.rst:0 -msgid "Available settings for Date fields" +"This may indicate that Zammad is still verifying your API token. Try " +"reloading the page again in a couple minutes." msgstr "" -#: ../system/objects/types.rst:73 -msgid "Date & time field" +#: ../system/integrations/gitlab.rst:2 +msgid "GitLab" msgstr "" -#: ../system/objects/types.rst:58 -msgid "Provides a date and time picker – does not allow default values" +#: ../system/integrations/gitlab.rst:4 +msgid "" +"Use GitLab integration to track GitLab issues directly within Zammad " +"tickets. Add issue hyperlinks and get a live summary of metadata like status " +"(open/closed), assignee, labels, and more." msgstr "" -#: ../system/objects/types.rst:62 -msgid "Allow future" +#: ../system/integrations/gitlab.rst:8 +msgid "" +"Please note that our GitLab integration does not support merge requests." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Forbid dates and times in the future." +#: ../system/integrations/gitlab.rst:None +msgid "Integration page for GitLab" msgstr "" -#: ../system/objects/types.rst:66 -msgid "Allow past" +#: ../system/integrations/gitlab.rst:18 +msgid "" +"In your GitLab preferences, create a new API token under **Access Tokens**." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Forbid dates and times in the past." +#: ../system/integrations/gitlab.rst:20 +msgid "Under **Select scopes**, choose ``read_api`` only." msgstr "" -#: ../system/objects/types.rst:70 -msgid "Default time diff (minutes)" +#: ../system/integrations/gitlab.rst:27 +msgid "🔒 **If you wish to link issues on any private repos...**" msgstr "" -#: ../system/objects/types.rst:69 -msgid "" -"This setting helps the user by highlighting the day from now plus the " -"provided value. It does not pre-fill the field." +#: ../system/integrations/gitlab.rst:29 +msgid "Your API token must belong to an account with access to those repos." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Date & time fields" +#: ../system/integrations/gitlab.rst:31 +msgid "Enter your new API token in Zammad and enable GitLab integration." msgstr "" -#: ../system/objects/types.rst:86 -msgid "Integer field" +#: ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to configure Zammad's GitLab integration" msgstr "" -#: ../system/objects/types.rst:76 +#: ../system/integrations/gitlab.rst:40 msgid "" -"Provides an input field that allows integer usage only. You may define a " -"default value. You cannot enforce comma separation." +"Use the default API endpoint (``https://gitlab.com/api/graphql``) unless " +"you're a self-hosted GitLab user." msgstr "" -#: ../system/objects/types.rst:80 -msgid "Minimal" +#: ../system/integrations/gitlab.rst:43 +msgid "" +"Once completed, a new GitLab issues tab will appear in the ticket pane. 🎉" msgstr "" -#: ../system/objects/types.rst:80 -msgid "The minimal value the field accepts." +#: ../system/integrations/gitlab.rst:51 +msgid "" +"Self-hosted administrators, please check your network settings to ensure " +"that your Zammad server can reach ``gitlab.com``." msgstr "" -#: ../system/objects/types.rst:83 -msgid "Maximal" +#: ../system/integrations/i-doit.rst:2 +msgid "i-doit" msgstr "" -#: ../system/objects/types.rst:83 -msgid "The maximum value the field accepts." +#: ../system/integrations/i-doit.rst:4 +msgid "" +"`i-doit `_ is an open-source **configuration " +"management database** - in other words, a tool for keeping tabs on every " +"single piece of your physical and digital infrastructure, from network " +"equipment to virtual machines on down to the faceplates on your rack shelves " +"and more." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Integer fields" +#: ../system/integrations/i-doit.rst:10 +msgid "" +"What's that got to do with Zammad? Well, if you used tickets to track issues " +"with all that hardware, you might start wishing there was a way they could " +"talk to each other." msgstr "" -#: ../system/objects/types.rst:99 -msgid "Multiple selection field" +#: ../system/integrations/i-doit.rst:14 +msgid "Zammad gives you two:" msgstr "" -#: ../system/objects/types.rst:89 -msgid "" -"Provides a selection field that allows the selection of one or more out of " -"several. This field does allow setting a default value." +#: ../system/integrations/i-doit.rst:17 +msgid "1. Add i-doit Links to Zammad Tickets" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Multiple selection fields" +#: ../system/integrations/i-doit.rst:20 ../system/integrations/i-doit.rst:80 +msgid "What Users See" msgstr "" -#: ../system/objects/types.rst:112 -msgid "Single selection field" +#: ../system/integrations/i-doit.rst:26 +msgid "i-doit integration in Zammad's ticket pane" msgstr "" -#: ../system/objects/types.rst:102 +#: ../system/integrations/i-doit.rst:26 msgid "" -"Provides a drop-down field that allows selection of one value out of " -"several. This field does allow setting a default value." +"The i-doit integration will appear under a new 🖨 tab in the ticket pane." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Single selection fields" +#: ../system/integrations/i-doit.rst:28 +msgid "" +"i-doit integration puts a new tab in Zammad's ticket pane where you can add " +"links to existing i-doit devices for easy reference. (See our :user-docs:" +"`user documentation ` to learn " +"how it works in practice)." msgstr "" -#: ../system/objects/types.rst:142 -msgid "Textarea field" +#: ../system/integrations/i-doit.rst:36 ../system/integrations/i-doit.rst:93 +msgid "How to Set it Up" msgstr "" -#: ../system/objects/types.rst:115 +#: ../system/integrations/i-doit.rst:38 msgid "" -"Provides a text area input field (multiple lines) and thus allows e.g. new " -"lines. You can set a default field value." +"It requires i-doit's `API Add-on `_. Make sure to have it properly set up. Use the following setting:" msgstr "" -#: ../system/objects/types.rst:120 -msgid "" -"Please note that this field *does not* support text formatting or HTML " -"content (rich text)." +#: ../system/integrations/i-doit.rst:42 +msgid "Active: ``Yes``" msgstr "" -#: ../system/objects/types.rst:123 -msgid "**🥵 This field can consume a lot of visual space**" +#: ../system/integrations/i-doit.rst:43 +msgid "Enforce authentication by username and password: ``No``" msgstr "" -#: ../system/objects/types.rst:125 +#: ../system/integrations/i-doit.rst:45 msgid "" -"Depending on where you use this field type, it may use a lot of visual space " -"if you provide a lot of text. This may be an issue to work with." +"To set it up, enable the integration in the Zammad admin panel under " +"**System > Integrations > i-doit**:" msgstr "" -#: ../system/objects/types.rst:130 -msgid "Default" +#: ../system/integrations/i-doit.rst:None +msgid "i-doit settings within the integration pages" msgstr "" -#: ../system/objects/types.rst:129 -msgid "" -"The here provided text will be shown within the text area field or new data " -"sets." +#: ../system/integrations/i-doit.rst:53 +msgid "The root URL of your i-doit installation." msgstr "" -#: ../system/objects/types.rst:134 ../system/objects/types.rst:160 -msgid "Maxlength" +#: ../system/integrations/i-doit.rst:62 +msgid "API token" msgstr "" -#: ../system/objects/types.rst:0 ../system/objects/types.rst:160 -msgid "You can pick the maximum length of the field." +#: ../system/integrations/i-doit.rst:56 +msgid "" +"Found in the i-doit admin panel under **Interfaces / external data > JSON-" +"RPC API > Common Settings**." msgstr "" -#: ../system/objects/types.rst:0 -msgid "The default length of this object is ``500``." +#: ../system/integrations/i-doit.rst:0 +msgid "i-doit administration interface with API configuration" msgstr "" -#: ../system/objects/types.rst:139 -msgid "Rows" +#: ../system/integrations/i-doit.rst:67 +msgid "Client ID" msgstr "" -#: ../system/objects/types.rst:0 -msgid "" -"Change the number of rows to dislay so that you can use only the space you " -"really need." +#: ../system/integrations/i-doit.rst:65 +msgid "A unique name to identify Zammad within i-doit." msgstr "" -#: ../system/objects/types.rst:0 -msgid "The default number of rows is ``4``." +#: ../system/integrations/i-doit.rst:67 +msgid "(Zammad does not require you to enter a value here, but i-doit might!)" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Textarea fields" +#: ../system/integrations/i-doit.rst:70 +msgid "" +"Here you can decide if the certificate of your i-doit system has to be " +"verified or not. In case you are using custom certificates, please have a " +"look at :doc:`how to add them to Zammad `." msgstr "" -#: ../system/objects/types.rst:165 -msgid "Text field" +#: ../system/integrations/i-doit.rst:77 +msgid "2. List / Create Zammad Tickets in i-doit" msgstr "" -#: ../system/objects/types.rst:145 -msgid "Provides a text field (one line) and allows choosing a default value." +#: ../system/integrations/i-doit.rst:None +msgid "Zammad integration in i-doit's device view" msgstr "" -#: ../system/objects/types.rst:148 +#: ../system/integrations/i-doit.rst:86 msgid "" -"Defines the type of the input field. This allows e.g. your browser to ensure " -"that you provide the specific type." +"i-doit's ticket system integration gives you a way to see all the tickets " +"for a given device without ever leaving i-doit. (See our :user-docs:`user " +"documentation ` to learn how it " +"works in practice)." msgstr "" -#: ../system/objects/types.rst:152 -msgid "Currently available:" +#: ../system/integrations/i-doit.rst:95 +msgid "" +"Enable this integration in the i-doit admin panel under **Interfaces / " +"external data > Trouble Ticket System (TTS) > Configuration**:" msgstr "" -#: ../system/objects/types.rst:155 -msgid "Phone" +#: ../system/integrations/i-doit.rst:None +msgid "i-doit administration interface with TTS configuration" msgstr "" -#: ../system/objects/types.rst:156 -msgid "Text" +#: ../system/integrations/i-doit.rst:104 +msgid "TTS-Type" msgstr "" -#: ../system/objects/types.rst:157 -msgid "Url *(URL fields disable link-template availability)*" +#: ../system/integrations/i-doit.rst:104 +msgid "``Zammad``" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Text fields" +#: ../system/integrations/i-doit.rst:115 +msgid "Username / Password" msgstr "" -#: ../system/objects/types.rst:174 -msgid "Single tree selection field" +#: ../system/integrations/i-doit.rst:107 +msgid "Login credentials for a Zammad agent." msgstr "" -#: ../system/objects/types.rst:168 +#: ../system/integrations/i-doit.rst:109 msgid "" -"Provides a select-like field with up to 6 layers of options. Does not allow " -"setting a default value." +"This agent must have **read permission** for all :doc:`groups ` that plan on using the i-doit integration." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Tree Select fields" +#: ../system/integrations/i-doit.rst:113 +msgid "" +"You may even wish to create a dedicated agent account just for this " +"integration (otherwise, if the agent ever changes her password, you will " +"have to remember to update it here)." msgstr "" -#: ../system/objects/types.rst:183 -msgid "Multiple tree selection field" +#: ../system/integrations/i-doit.rst:117 +msgid "URL incl. protocol" msgstr "" -#: ../system/objects/types.rst:177 -msgid "" -"Provides a select-like field with up to 6 layers of options allowing the " -"selection of multiple values. Does not allow setting a default value." +#: ../system/integrations/i-doit.rst:118 +msgid "``https://your.zammad.domain``" msgstr "" -#: ../system/objects/types.rst:302 -msgid "External Data Source field" +#: ../system/integrations/index.rst:2 +msgid "Integrations" msgstr "" -#: ../system/objects/types.rst:186 +#: ../system/integrations/index.rst:4 msgid "" -"Provides a searchable field which fetches data from an external system. This " -"can be useful if you have data outside of Zammad and don't want to maintain " -"both data sources." +"Zammad offers numerous integrations that add rich features to your instance." msgstr "" -#: ../system/objects/types.rst:190 -msgid "The feature works as follows:" +#: ../system/integrations/index.rst:6 +msgid "We're still working on this part of our documentation, stay tight!" msgstr "" -#: ../system/objects/types.rst:192 -msgid "" -"Zammad sends a query with a search string (free text from agent or based on " -"a variable) in a pre-defined format (\"Search URL\") to an external system." +#: ../system/integrations/index.rst:10 +msgid "Integrations for Phone Systems" msgstr "" -#: ../system/objects/types.rst:195 +#: ../system/integrations/index.rst:14 msgid "" -"This external system searches for matches and provides a response as a JSON " -"structure to Zammad." +"Your VoIP provider or telephony system is not listed? Possibly your provider " +"supports Zammad by using the generic CTI - if you're unsure ask your " +"provider." msgstr "" -#: ../system/objects/types.rst:197 +#: ../system/integrations/index.rst:18 msgid "" -"Zammad just looks for the defined list and value keys, reads the content and " -"displays the value to the user. There is no search on Zammad side." +"Provider does not support Zammad? Consider creating a `feature request in " +"the Zammad Community `_." msgstr "" -#: ../system/objects/types.rst:201 -msgid "" -"The usage of a PostgreSQL database for Zammad is required. In any other " -"case, Zammad will hide the external data source type and you are not able to " -"use it. If you want to use this feature, consider to :docs:`migrate your " -"database `." +#: ../system/integrations/index.rst:31 +msgid "Integrations for Authentication and Customers" msgstr "" -#: ../system/objects/types.rst:205 -msgid "Currently, only ``GET`` is supported as request method." +#: ../system/integrations/index.rst:44 +msgid "Integrations for Monitoring Systems" msgstr "" -#: ../system/objects/types.rst:206 -msgid "" -"The data structure must be in JSON format and provide the objects in an " -"array." +#: ../system/integrations/index.rst:46 +msgid "This section currently misses the following integrations:" msgstr "" -#: ../system/objects/types.rst:208 -msgid "" -"The endpoint for the external data source has to support search. On Zammad " -"side, there is no search/logic implemented; however, you can define the " -"output key and value based on the result(s) from the response (which " -"provides already filtered content based on the search)." +#: ../system/integrations/index.rst:48 +msgid "Icinga" msgstr "" -#: ../system/objects/types.rst:212 -msgid "" -"If you receive more results as expected, your external data source search " -"may not work properly or the structure of the URL is not correct. You should " -"get in touch with a responsible person from the external system." +#: ../system/integrations/index.rst:49 +msgid "Monit" msgstr "" -#: ../system/objects/types.rst:217 -msgid "" -"Please have a look :doc:`at our example `, where you can find a possible configuration for a public " -"dummy endpoint." +#: ../system/integrations/index.rst:50 +msgid "Nagios" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for external data source fields" +#: ../system/integrations/index.rst:60 +msgid "Integrations for Issue Trackers" msgstr "" -#: ../system/objects/types.rst:242 -msgid "Search URL" +#: ../system/integrations/index.rst:70 +msgid "Other Integrations" msgstr "" -#: ../system/objects/types.rst:227 +#: ../system/integrations/index.rst:72 msgid "" -"Set your endpoint where Zammad fetches the data. Please make sure to include " -"a valid search :doc:`variable <../variables>` as an URL parameter. Example " -"for a free text search at user input: ``#{search.term}``" +"This section will hold any other integration that can't be grouped up (yet)." msgstr "" -#: ../system/objects/types.rst:232 -msgid "" -"If in doubt, ask the responsible person for the external data source how " -"they expect the strucuture of the URL." +#: ../system/integrations/ldap/index.rst:2 +msgid "LDAP / Active Directory" msgstr "" -#: ../system/objects/types.rst:236 +#: ../system/integrations/ldap/index.rst:4 msgid "" -"Depending on your search variable, the preview might work or not. The reason " -"is that the context might not be available and it is no bug." +"Zammad comes with a powerful LDAP integration that allows you to have a " +"single source of truth. By this you reduce the number of login credentials " +"your user has to remember." msgstr "" -#: ../system/objects/types.rst:239 +#: ../system/integrations/ldap/index.rst:10 msgid "" -"Please also make sure to use a variable which is available in your object " -"context. For example you won't be able to search for a ticket in a user " -"object context." -msgstr "" - -#: ../system/objects/types.rst:252 -msgid "SSL Verification" +"The LDAP source is also a perfect candidate for Zammad's :docs:`Kerberos " +"Single Sign-On ` but also works as addition " +"to other :doc:`/settings/security/third-party`." msgstr "" -#: ../system/objects/types.rst:245 -msgid "Here you can switch the SSL verification to no." +#: ../system/integrations/ldap/index.rst:None +msgid "Zammands LDAP management page" msgstr "" -#: ../system/objects/types.rst:249 -msgid "" -"If your external data source system is using self signed certificates, " -"please have a look :doc:`here ` for " -"further information about how to handle them in Zammad, so you can keep the " -"SSL verification activated." +#: ../system/integrations/ldap/index.rst:25 +msgid "📝 :doc:`manage`" msgstr "" -#: ../system/objects/types.rst:258 -msgid "HTTP Authentication" +#: ../system/integrations/ldap/index.rst:25 +msgid "Add, modify, remove or re-arrange your LDAP-Sources as needed." msgstr "" -#: ../system/objects/types.rst:255 -msgid "" -"If your external data source requires an authentication, you can set it " -"here. You can leave it empty or choose between *Basic Authentication* or " -"*Authentication Token* (selecting one of the two methods leads to additional " -"fields where you can enter your credentials/token)." +#: ../system/integrations/ldap/index.rst:30 +msgid "Before you continue, please note the following limitations." msgstr "" -#: ../system/objects/types.rst:265 -msgid "Search result list key" +#: ../system/integrations/ldap/index.rst:32 +msgid "Mapping / Synchronizing organizations is not possible" msgstr "" -#: ../system/objects/types.rst:261 +#: ../system/integrations/ldap/index.rst:36 msgid "" -"Defines the level in the JSON structure which provides the list with search " -"results. You can leave it empty, if the data is already provided as an " -"array. If you have to go deeper in the structure, you can provide a path " -"with ``.`` as separators, e.g. ``key.subkey.sub-sub-key``." -msgstr "" - -#: ../system/objects/types.rst:271 -msgid "Search result value key" +"You may want to consider using domain based assignments to overcome this " +"issue. Learn more on :doc:`/manage/organizations/index`." msgstr "" -#: ../system/objects/types.rst:268 +#: ../system/integrations/ldap/index.rst:39 msgid "" -"Defines the attribute in the structure in which your external data source " -"provides the *value* for your data. An example would be a product *number*. " -"If you have to go deeper in the structure, you can provide a path with ``.`` " -"as separators, e.g. ``key.subkey.sub-sub-key``." +"Zammad's LDAP sync is one way. Editing user settings or permissions may be " +"overwritten upon the next sync depending on your configuration." msgstr "" -#: ../system/objects/types.rst:277 -msgid "Search result label key" +#: ../system/integrations/ldap/index.rst:41 +msgid "Nested groups are not supported." msgstr "" -#: ../system/objects/types.rst:274 -msgid "" -"Defines the attribute in the structure in which your external data source " -"provides the *label* for your data. An example would be a product *name*. If " -"you have to go deeper in the structure, you can provide a path with ``.`` as " -"separators, e.g. ``key.subkey.sub-sub-key``." +#: ../system/integrations/ldap/index.rst:42 +msgid "Synchronizing user avatars from LDAP is not supported." msgstr "" -#: ../system/objects/types.rst:280 -msgid "" -"In the preview area, you can find the following items (depending on your " -"configuration above):" +#: ../system/integrations/ldap/index.rst:43 +msgid "Unlike user filters, group filters cannot be changed." msgstr "" -#: ../system/objects/types.rst:283 +#: ../system/integrations/ldap/index.rst:44 msgid "" -"**Error/hint message** (only if configuration is not complete): Zammad tells " -"you, if there is a problem and what you should change in your configuration." +"When a user originates from an LDAP server, Zammad will try to verify the " +"login credentials against LDAP first - if this fails Zammad will check its " +"local database." msgstr "" -#: ../system/objects/types.rst:286 +#: ../system/integrations/ldap/index.rst:50 msgid "" -"**Search field**: search for an existing attribute in the data source to get " -"a preview. This is required for the fields below to show up." +"Users can have local passwords even if they're LDAP users! You can learn " +"more about user accounts in general on :doc:`/manage/users/index`." msgstr "" -#: ../system/objects/types.rst:288 +#: ../system/integrations/ldap/index.rst:54 msgid "" -"**Search result response** (only if configuration is not complete): here you " -"can find a syntax highlighted JSON preview of the response, based on the " -"search term you entered." +"When several LDAP sources contain the same user (meaning the same email " +"address), the user in question will be updated with every source configured. " +"*The last LDAP source will win.*" msgstr "" -#: ../system/objects/types.rst:291 +#: ../system/integrations/ldap/index.rst:58 msgid "" -"**Search result list** (only if *search result list key* is properly set): " -"output of the structure under the configured *search result list key*." +"This is subject to change with `Issue 4109 `_ in the future." msgstr "" -#: ../system/objects/types.rst:294 +#: ../system/integrations/ldap/index.rst:60 msgid "" -"**Preview table** (when fully configured): Zammad shows you a table which " -"includes the found items based on the search string (value, label and " -"optional link). You can use this preview if you don't have the complete data " -"structure of the external system in mind." +"Synchronization statistics currently affect *all* configured LDAP sources. " +"This also applies for newly added or updated sources." msgstr "" -#: ../system/objects/types.rst:299 +#: ../system/integrations/ldap/index.rst:63 msgid "" -"An example of a configured external data source field from agent perspective:" +"This is subject to change with `Issue 4108 `_ in the future." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Screencast showing the search for a product in a ticket" +#: ../system/integrations/ldap/index.rst:65 +msgid "" +"Zammad currently has limited fallback server support. You can workaround " +"this by providing several sources - however, ensure to have the exact same " +"configuration on your fallback." msgstr "" -#: ../system/objects/types.rst:307 -msgid "URL fields (Link-Template)" +#: ../system/integrations/ldap/index.rst:69 +msgid "" +"This is subject to improve with `Issue 4107 `_ in the future." msgstr "" -#: ../system/objects/types.rst:311 +#: ../system/integrations/ldap/index.rst:76 msgid "" -"This function is restricted to Text, Select and External data source types " -"only." +"This section holds all requests Zammad handled for all LDAP sources. These " +"entries can either contain synchronization information or logins " +"(authentication attempts via Zammad's login interface)." msgstr "" -#: ../system/objects/types.rst:314 +#: ../system/integrations/ldap/index.rst:80 msgid "" -"Link-Templates are an amazing way to dynamically generate URLs. They allow " -"you to integrate other systems better without having to manually copy data " -"from Zammad if possible." +"By clicking on any request, Zammad will provide even more information. The " +"provided information can be useful when something does not work as expected." msgstr "" -#: ../system/objects/types.rst:320 +#: ../system/integrations/ldap/index.rst:85 msgid "" -"Another great way of communicating with another system may be Zammad's :doc:" -"`Webhooks `." +"Especially a LDAP synchronization can cause many log entries. The web " +"interface will always limit the number of shown entries to the last 50 " +"entries." msgstr "" -#: ../system/objects/types.rst:323 +#: ../system/integrations/ldap/index.rst:None msgid "" -"After filling a link-template enabled field, an URL icon will appear on its " -"right. Clicking on the icon opens a new tab." +"Screencast showing LDAP integration log entries and a detail view on\n" +"an entry." msgstr "" -#: ../system/objects/types.rst:328 -msgid "" -"Even though Zammad displays the link template within object edit and create " -"screens, the function is optional. It's only active if you populate the " -"field." +#: ../system/integrations/ldap/manage.rst:2 +msgid "Manage LDAP-Sources" msgstr "" -#: ../system/objects/types.rst:333 +#: ../system/integrations/ldap/manage.rst:6 msgid "" -"What's the difference between URL and text fields with link template...?!" +"Please keep in mind all current limitations for the LDAP synchronization. " +"This will help to understand scopes of the following operations better." msgstr "" -#: ../system/objects/types.rst:335 -msgid "" -"Both fields have different use cases. Use ``text`` type text fields when " -"ever you have a *static* url that requires dynamic parameters. If you " -"require a drag & drop like field that you can put in any URL, use ``URL`` " -"type text fields." +#: ../system/integrations/ldap/manage.rst:65 +msgid "Add new source" msgstr "" -#: ../system/objects/types.rst:340 +#: ../system/integrations/ldap/manage.rst:10 msgid "" -"The difference is easier to spot when comparing the fields directly, below " -"screencast shows the result - the dynamic approach uses existing values in " -"the moment of updating to built the URL - e.g. ``https://google.com/search?" -"q=cookies`` - while the URL approach uses the actual URL of the field - e.g. " -"``https://zammad.com``." +"Using the *New Source* button allows you to add new LDAP sources to your " +"installation. You're not limited in the number of sources, however, keep in " +"mind that many sources will also take more time to synchronize." msgstr "" -#: ../system/objects/types.rst:None +#: ../system/integrations/ldap/manage.rst:14 msgid "" -"Screencast showing the differents in between URL and text type fields with " -"actual values" +"You can choose between different encryption types, namely *SSL* and " +"*STARTTLS* or none of them (\"*No SSL*\"). If you choose *SSL* or " +"*STARTTLS*, Zammad will display an additional *SSL verification* option that " +"allows you to disable the verification, e.g. for self-signed SSL " +"certificates. You can also tell Zammad to use a different port by appending " +"``:`` to your hostname/IP." msgstr "" -#: ../system/objects/types.rst:352 -msgid "How does this work...?!" +#: ../system/integrations/ldap/manage.rst:0 +msgid "" +"Screenshot of configuring a new LDAP source with SSL encryption and SSL " +"verification" msgstr "" -#: ../system/objects/types.rst:354 +#: ../system/integrations/ldap/manage.rst:26 msgid "" -"As an example, let's say you have an attribute called ``amazing_attribute`` " -"and you want to open a google search directly with the input from that field." +"New Source with SSL transport security enabled and certificate verification" msgstr "" -#: ../system/objects/types.rst:357 +#: ../system/integrations/ldap/manage.rst:30 msgid "" -"Providing the link-template field below allows you to do so: ``https://www." -"google.com/search?q=#{ticket.amazing_attribute}``" +"Using an user filter can be a good idea if you only require a small subset " +"of your LDAP users in Zammad." msgstr "" -#: ../system/objects/types.rst:362 -msgid "" -"You can use any :doc:`Zammad variable ` as long as it's " -"available in the moment you need it." +#: ../system/integrations/ldap/manage.rst:42 +msgid "This especially affects inactive users" msgstr "" -#: ../system/objects/types.rst:365 +#: ../system/integrations/ldap/manage.rst:34 msgid "" -"As a result, you are redirected to Google with a search for the value of the " -"attribute, if you click on the button in the ticket (as you can see in the " -"screencast above)." +"As every LDAP behaves differently on which attributes and how they are set, " +"Zammad doesn't care about any flags." msgstr "" -#: ../system/packages.rst:2 -msgid "Packages" +#: ../system/integrations/ldap/manage.rst:37 +msgid "" +"Users that no longer are returned by your LDAP source will automatically be " +"set to inactive. Zammad assumes that the user was deactivated." msgstr "" -#: ../system/packages.rst:4 -msgid "That's the package management-area." +#: ../system/integrations/ldap/manage.rst:41 +msgid "" +"Users will never be removed automatically! If you want to remove obsolete " +"users, use :doc:`/system/data-privacy`." msgstr "" -#: ../system/packages.rst:6 -msgid "Individual add-ons for Zammad can be installed and managed here." +#: ../system/integrations/ldap/manage.rst:46 +msgid "Active Directory admins" msgstr "" -#: ../system/sessions.rst:2 -msgid "Sessions" +#: ../system/integrations/ldap/manage.rst:45 +msgid "" +"Active Directories are quite specific on how to filter for active users only " +"- please see the `Microsoft documentation `_ for more " +"information." msgstr "" -#: ../system/sessions.rst:4 +#: ../system/integrations/ldap/manage.rst:51 msgid "" -"Sessions management allows reviewing currently known user sessions and " -"allows to end these. The session timeout is affected by :ref:" -"`security_session_timeout` configurations from security settings." +"*Do not* manually write pathes of either LDAP attributes or groups. If " +"Zammad does not display them, it either cannot find them or you have a lot " +"of users that don't have the attributes populated." msgstr "" -#: ../system/sessions.rst:None -msgid "Screenshot showing Zammad's session management" +#: ../system/integrations/ldap/manage.rst:55 +msgid "" +"Zammad will always only return attributes that are filled - this reduces the " +"returned list of attributes greatly." msgstr "" -#: ../system/sessions.rst:13 -msgid "Zammad will provide the following information:" +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing how to add a new LDAP source" msgstr "" -#: ../system/sessions.rst:16 +#: ../system/integrations/ldap/manage.rst:63 msgid "" -"The user account this session entry belongs to. It can be normal if a user " -"has several sessions in the list. This can be due to changed browser " -"information or if you use e.g. single sign on methods where the user does " -"not use the log off button." +"If your LDAP system doesn't allow anonymous bind, Zammad detects it and " +"provides you an editable \"Base DN\" *text* field instead of a prefilled " +"*select* field." msgstr "" -#: ../system/sessions.rst:22 -msgid "Browser" +#: ../system/integrations/ldap/manage.rst:81 +msgid "Review or edit existing source" msgstr "" -#: ../system/sessions.rst:22 -msgid "The browser agent communicated to Zammad." +#: ../system/integrations/ldap/manage.rst:68 +msgid "" +"Clicking on a LDAP source will provide a configuration and mapping overview." msgstr "" -#: ../system/sessions.rst:40 -msgid "Location" +#: ../system/integrations/ldap/manage.rst:70 +msgid "" +"If needed you can then use the *Change* button to update either the name, " +"active state or the whole configuration. If you're changing the whole " +"configuration, the dialogue will be identical to the source creation." msgstr "" -#: ../system/sessions.rst:25 +#: ../system/integrations/ldap/manage.rst:76 msgid "" -"The anticipated location based on the users IP address. Depending on the IP " -"address the result shown may differ. This option depends on :doc:`/settings/" -"system/services`." +"Did your LDAP server change? Different LDAP servers have different " +"structures and default attributes. This causes the LDAP synchronization to " +"likely fail. Consider removing the affected source and re-add it." +msgstr "" + +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing the update of the source name." msgstr "" -#: ../system/sessions.rst:29 -msgid "The following information can be shown:" +#: ../system/integrations/ldap/manage.rst:89 +msgid "Re-arrange LDAP source's order" msgstr "" -#: ../system/sessions.rst:33 -msgid "IP address" +#: ../system/integrations/ldap/manage.rst:84 +msgid "" +"You can change the synchronization order for each source at any time. Zammad " +"will synchronize the sources from top to bottom." msgstr "" -#: ../system/sessions.rst:32 +#: ../system/integrations/ldap/manage.rst:0 msgid "" -"Either if you set *Geo IP services* to inactive or you're using internal IP " -"address which do not provide location information." +"Screencasting showing how to change the source order by using\n" +"drag and drop." msgstr "" -#: ../system/sessions.rst:40 -msgid "Country (or Country + City)" +#: ../system/integrations/ldap/manage.rst:101 +msgid "Remove a source" msgstr "" -#: ../system/sessions.rst:36 +#: ../system/integrations/ldap/manage.rst:92 msgid "" -"If *Geo IP services* is enabled only. Depends on how detailed the available " -"IP address information are." +"If you no longer need the a LDAP source or simply want to start over, you " +"can remove them at any time. This will not remove synchronized users, data " +"synchronized or permissions." msgstr "" -#: ../system/sessions.rst:39 +#: ../system/integrations/ldap/manage.rst:98 msgid "" -"Be aware that results can be inaccurate - this technically is not an error." +"Not sure if you'd need the source later on? Set the source to inactive " +"instead of removing it - see *Review or edit existing source* for more." msgstr "" -#: ../system/sessions.rst:43 -msgid "Age" +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing how to remove LDAP sources." msgstr "" -#: ../system/sessions.rst:43 -msgid "Provides the time when the session initially has been created." +#: ../system/integrations/pgp/index.rst:2 +msgid "PGP" msgstr "" -#: ../system/sessions.rst:50 -msgid "Update" +#: ../system/integrations/pgp/index.rst:7 +msgid "" +"Pretty Good Privacy (PGP) is another method for secure email communication. " +"With PGP, you can exchange **signed** and **encrypted** messages with others." msgstr "" -#: ../system/sessions.rst:46 -msgid "" -"Provides the time the user used this session to open Zammad. This timestamp " -"is only updated if the user e.g. reloads, not during normal work on tickets." +#: ../system/integrations/pgp/index.rst:13 +#: ../system/integrations/smime/index.rst:17 +msgid "Signing" msgstr "" -#: ../system/sessions.rst:50 -msgid "This timestamp is being used for the session timeout." +#: ../system/integrations/pgp/index.rst:11 +msgid "is a proof that a message hasn't been manipulated on its way." msgstr "" -#: ../system/sessions.rst:53 +#: ../system/integrations/pgp/index.rst:13 msgid "" -"Use the delete button to remove a single session on behalf of your user." +"In other words, it guarantees message **integrity** and **authenticity**." msgstr "" -#: ../system/subscription/billing.rst:2 -msgid "Billing" +#: ../system/integrations/pgp/index.rst:19 +#: ../system/integrations/smime/index.rst:22 +msgid "Encryption" msgstr "" -#: ../system/subscription/billing.rst:4 +#: ../system/integrations/pgp/index.rst:16 +#: ../system/integrations/smime/index.rst:20 msgid "" -"Within the billing tab you can control all billing relevant information like " -"invoices, billing address and the option to cancel your subscription." -msgstr "" - -#: ../system/subscription/billing.rst:33 -msgid "Billing information" +"scrambles a message so that it can only be unscrambled by the intended " +"recipient." msgstr "" -#: ../system/subscription/billing.rst:8 +#: ../system/integrations/pgp/index.rst:19 msgid "" -"All adjusted billing information below only affect future invoices. If your " -"invoice was issued wrong, please contact `our sales team `_." +"In other words, it guarantees message **privacy** and **data security**." msgstr "" -#: ../system/subscription/billing.rst:14 -msgid "Billing address" +#: ../system/integrations/pgp/index.rst:25 +msgid "Screenshot of ticket creation with encrypt and sign buttons" msgstr "" -#: ../system/subscription/billing.rst:13 +#: ../system/integrations/pgp/index.rst:25 msgid "" -"Provide your company address here, make sure to include the companies name " -"in case required. This address will be referenced on your invoice." +"Once PGP has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " +"appear in the ticket composer." msgstr "" -#: ../system/subscription/billing.rst:18 -msgid "VAT ID" +#: ../system/integrations/pgp/index.rst:28 +msgid "**Sign button not visible?**" msgstr "" -#: ../system/subscription/billing.rst:17 +#: ../system/integrations/pgp/index.rst:30 msgid "" -"Provide your VAT ID here. If applicable your invoice will not contain German " -"VAT. Please make sure to pay the VAT in your country as required." +"Please note that the signing of emails is based on the outgoing email " +"account. That means you have to choose a group with a sender email account, " +"which has a private key assigned." msgstr "" -#: ../system/subscription/billing.rst:27 -msgid "Billing Email Address" +#: ../system/integrations/pgp/index.rst:35 +msgid "Handling of Keys" msgstr "" -#: ../system/subscription/billing.rst:21 +#: ../system/integrations/pgp/index.rst:36 msgid "" -"Usually the instance owner (the person that registered the instance) will " -"receive all emails including the invoices. In case you have your own billing " -"department, you can provide their email address here." +"To use the PGP function, you have to enable the integration (PGP) by " +"switching the toggle to *enabled*." msgstr "" -#: ../system/subscription/billing.rst:25 +#: ../system/integrations/pgp/index.rst:39 msgid "" -"All billing relevant information will then be sent to this email address." +"You can add keys by clicking the *add key* button. The keys can be imported " +"from a file or you can paste the content of the key in the text box." msgstr "" -#: ../system/subscription/billing.rst:27 -msgid "Invoices are sent as attachment (PDF) to this email address." +#: ../system/integrations/pgp/index.rst:42 +msgid "**Which keys do I have to import?**" msgstr "" -#: ../system/subscription/billing.rst:29 +#: ../system/integrations/pgp/index.rst:44 msgid "" -"Don't forget to press the *Submit* button after you changed above settings." +"For **signing** *outgoing* emails, you have to import the private key of " +"your Zammad email account." msgstr "" -#: ../system/subscription/billing.rst:0 +#: ../system/integrations/pgp/index.rst:47 msgid "" -"Screenshot showing options for billing information within the\n" -"subscription menu" -msgstr "" - -#: ../system/subscription/billing.rst:70 -msgid "Payment history" +"For **encrypting** *outgoing* emails, you have to import the public key of " +"the customer's email account." msgstr "" -#: ../system/subscription/billing.rst:36 +#: ../system/integrations/pgp/index.rst:50 msgid "" -"The payment history will display a history of all paid invoices. At this " -"point you can also download these in case you need them again." +"For **verifying the signature** of signed *incoming* emails, you have to " +"import the public key of the customer." msgstr "" -#: ../system/subscription/billing.rst:41 +#: ../system/integrations/pgp/index.rst:53 msgid "" -"You will only find *paid* invoices here. Invoices that are to be billed are " -"not available before the payment is completed." +"For **decrypting** of encrypted *incoming* emails, you have to import the " +"private key of your Zammad email account." msgstr "" -#: ../system/subscription/billing.rst:46 -msgid "Date" +#: ../system/integrations/pgp/index.rst:57 +msgid "Import Keys From a File" msgstr "" -#: ../system/subscription/billing.rst:46 -msgid "Date of the invoice creation." +#: ../system/integrations/pgp/index.rst:58 +msgid "You can import keys from a file in the section **Upload key**:" msgstr "" -#: ../system/subscription/billing.rst:49 -msgid "Amount" +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of adding a key via file" msgstr "" -#: ../system/subscription/billing.rst:49 -msgid "Invoice total including VAT if applicable." +#: ../system/integrations/pgp/index.rst:64 +msgid "" +"**Supported file formats:** ASCII-armor as well as binary GPG format " +"(basically any GPG supported key format) is supported here." msgstr "" -#: ../system/subscription/billing.rst:52 -msgid "" -"Contains contract period (monthly or yearly) and hosted plan for the " -"subscription period in question." +#: ../system/integrations/pgp/index.rst:68 +msgid "Import Keys by Pasting the Content" msgstr "" -#: ../system/subscription/billing.rst:63 -msgid "Payment method / Service period" +#: ../system/integrations/pgp/index.rst:69 +msgid "You can also paste the key's content in the section **paste key**:" msgstr "" -#: ../system/subscription/billing.rst:56 -msgid "" -"Used bank account or credit card as well as the subscription period the " -"invoice is about." +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of adding a key via pasting" msgstr "" -#: ../system/subscription/billing.rst:61 +#: ../system/integrations/pgp/index.rst:75 msgid "" -"It might happen that the invoice date and subscription period differ. This " -"is nothing to worry about, the subscription periods will be accounted later " -"on." +"**Supported format:** Please note that only ASCII-armor is supported here." msgstr "" -#: ../system/subscription/billing.rst:67 -msgid "Receipt" +#: ../system/integrations/pgp/index.rst:78 +msgid "Deleting Keys" msgstr "" -#: ../system/subscription/billing.rst:66 +#: ../system/integrations/pgp/index.rst:79 msgid "" -"Use the arrow to download the invoice in question. You can download all " -"available invoices any time you need to here!" +"If you want to delete a specific key, you can do it by clicking on the menu " +"in the *actions* column and select **delete**:" msgstr "" -#: ../system/subscription/billing.rst:0 -msgid "Screenshot showing payment history of a hosted instance" +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of deleting a key" msgstr "" -#: ../system/subscription/billing.rst:94 -msgid "Do you want to cancel your subscription?" +#: ../system/integrations/pgp/index.rst:88 +msgid "Downloading Keys" msgstr "" -#: ../system/subscription/billing.rst:73 +#: ../system/integrations/pgp/index.rst:89 msgid "" -"In case you no longer want to use Zammad's SaaS, you can cancel your " -"subscription by using the red *Yes, please cancel my subscription* button." +"If you want to download your keys, you can do this as well via corresponding " +"action buttons. Depending on the key, you can choose wether you want to " +"download the private or the public key." +msgstr "" + +#: ../system/integrations/pgp/index.rst:95 +#: ../system/integrations/smime/manage-certificates.rst:76 +msgid "Default Behavior" msgstr "" -#: ../system/subscription/billing.rst:76 +#: ../system/integrations/pgp/index.rst:96 msgid "" -"Your subscription will end the day after your trial or billing period ends." +"Here you can adjust on per group basis, if *sign* and *encryption* is on or " +"off by default. Please be aware, that agents can always override the setting " +"for each individual article." +msgstr "" + +#: ../system/integrations/pgp/index.rst:None +msgid "Adjusting default behavior on per group basis" msgstr "" -#: ../system/subscription/billing.rst:80 +#: ../system/integrations/pgp/index.rst:107 msgid "" -"We will remind you about your cancelled subscription several times up front. " -"After the subscription ended all instance data will be removed. A restore " -"*is not* possible after that point!" +"Here you can see the last actions regarding signing and encryption and if " +"they were successful." msgstr "" -#: ../system/subscription/billing.rst:0 -msgid "Screencast showing how to cancel a subscription" +#: ../system/integrations/pgp/index.rst:117 +msgid "**Sign button is not visible, but keys are imported.**" msgstr "" -#: ../system/subscription/billing.rst:87 -msgid "**😖 Cancelled by accident?**" +#: ../system/integrations/pgp/index.rst:115 +msgid "Did you choose a group in the ticket?" msgstr "" -#: ../system/subscription/billing.rst:89 +#: ../system/integrations/pgp/index.rst:116 msgid "" -"You can always undo the cancellation via the *Yes, undo the cancellation of " -"my subscription* button up to the last subscription day!" +"Did you import a private key for the email adress, which is used for " +"outgoing emails in the group?" +msgstr "" + +#: ../system/integrations/pgp/index.rst:122 +msgid "**How to obtain keys?**" msgstr "" -#: ../system/subscription/billing.rst:0 +#: ../system/integrations/pgp/index.rst:120 msgid "" -"Screenshot showing a red button to cancel the subscription\n" -"cancellation" +"You can create them yourself! There are some good tutorials on the web on " +"how to create them. Providing keys to Zammad is a prerequisite to use the " +"PGP feature." msgstr "" -#: ../system/subscription/index.rst:2 -msgid "Subscription (SaaS)" +#: ../system/integrations/pgp/index.rst:127 +msgid "**It says a passphrase is needed, but I haven't got one.**" msgstr "" -#: ../system/subscription/index.rst:4 +#: ../system/integrations/pgp/index.rst:125 msgid "" -"The subscription settings page allows you to configure your instances " -"package and number of agents required." +"If the key is secured with a passphrase, you have to provide it for the " +"import in Zammad. It is possible that keys may have an empty passphrase. " +"However, this is *not* recommended." msgstr "" -#: ../system/subscription/index.rst:9 -msgid "" -"This setting section is only available for Hosted setups. If you're looking " -"for on premise support contracts, please see the `Zammad pricing page " -"`_." +#: ../system/integrations/pgp/index.rst:132 +msgid "**How do my customers get my new key?**" msgstr "" -#: ../system/subscription/index.rst:20 +#: ../system/integrations/pgp/index.rst:130 msgid "" -"The subscription section currently consists of two tabs: Plan & Billing. For " -"your overview we've divided those two tabs into independent sub pages:" +"You have to provide your **public** key in advance. Your customer also has " +"to configure PGP in their email workflow and import your public key. The " +"other way round, you have to get the public key of your customer and have to " +"import it to Zammad." +msgstr "" + +#: ../system/integrations/slack.rst:2 +msgid "Slack" +msgstr "" + +#: ../system/integrations/slack.rst:4 +msgid "**⚠️ Deprecation warning ⚠️**" msgstr "" -#: ../system/subscription/index.rst:25 -msgid ":doc:`💰 Subscription plan `" +#: ../system/integrations/slack.rst:6 +msgid "" +"Zammad 7 will no longer support this dedicated Slack integration. It is " +"recommended to switch to :doc:`pre-defined webhooks ` instead. Existing Slack integrations should " +"be migrated manually before this feature is dropped." msgstr "" -#: ../system/subscription/index.rst:24 +#: ../system/integrations/slack.rst:14 msgid "" -"Everything affecting your instance subscription functions like number of " -"agents, package and payment method." +"In order to use this feature, please add a new Slack app to your Workspace. " +"The App you need is called ``Incoming WebHooks`` ." msgstr "" -#: ../system/subscription/index.rst:28 -msgid ":doc:`🧾 Subscription billing `" +#: ../system/integrations/slack.rst:18 +msgid "Why Do I Need This Feature?" msgstr "" -#: ../system/subscription/index.rst:28 +#: ../system/integrations/slack.rst:20 msgid "" -"Everything regarding billing address, invoices and account cancellation." +"If you're already using Slack for your team communication, you'll love this " +"feature! Our Slack integration can push ticket notifications about the last " +"ticket article based on the following events:" msgstr "" -#: ../system/subscription/index.rst:33 -msgid "FAQ" +#: ../system/integrations/slack.rst:24 +msgid "on Ticket creation" msgstr "" -#: ../system/subscription/index.rst:37 -msgid "I set up a trial account but am missing functions to test" +#: ../system/integrations/slack.rst:25 +msgid "on Ticket updates" msgstr "" -#: ../system/subscription/index.rst:36 -msgid "" -"The trial instance is running within the professional package allowing up to " -"three agents." +#: ../system/integrations/slack.rst:26 +msgid "on reached reminders" msgstr "" -#: ../system/subscription/index.rst:40 -msgid "Can I change package within the trial?" +#: ../system/integrations/slack.rst:27 +msgid "a Ticket has escalated" msgstr "" -#: ../system/subscription/index.rst:40 -msgid "No. As soon as the package is changed the subscription begins." +#: ../system/integrations/slack.rst:28 +msgid "a Ticket is going to escalate" msgstr "" -#: ../system/subscription/index.rst:45 -msgid "What happens to my trial instance after the trial period ended?" +#: ../system/integrations/slack.rst:30 +msgid "" +"Zammad will provide the Ticket title, a direct link to the Ticket, the event " +"type (creation, updated, escalation), the customer, time and the last " +"article that has triggered the notification." msgstr "" -#: ../system/subscription/index.rst:43 +#: ../system/integrations/slack.rst:34 msgid "" -"Your instance will automatically be canceled for you. Please see *What " -"happens to my instance after it has been canceled?* for more." +"This will give you further options, as you can see e.g. escalating tickets " +"that are assigned to an agent that's e.g. absent. You can interact faster, " +"as you might see problems earlier (or even before the problem gets one)." msgstr "" -#: ../system/subscription/index.rst:58 -msgid "What happens to my instance after it has been canceled?" +#: ../system/integrations/slack.rst:38 +msgid "" +"If needed and wanted, you can even discuss directly about the topic before " +"sending an answer to the customer. Another possible use case would be a " +"agent monitoring new agents and their answers to tickets." msgstr "" -#: ../system/subscription/index.rst:48 -msgid "That depends slightly on your instance state:" +#: ../system/integrations/slack.rst:44 +msgid "Configure the Integration" msgstr "" -#: ../system/subscription/index.rst:54 -msgid "Trial instance" +#: ../system/integrations/slack.rst:46 +msgid "" +"First of all, please go to your slack workspace - go to administration => " +"Manage Apps. If you don't have an app yet, you can simply add a new one - " +"just search for ``Incoming WebHooks`` and customize the app to your needs." msgstr "" -#: ../system/subscription/index.rst:51 +#: ../system/integrations/slack.rst:50 msgid "" -"If you're still on trial, we will ice your instance and remind you once " -"again about your instance. We then will wait some days and remove your " -"instance from our system. This is the last time we will inform you by Email." +"Choose (or create) the channel Zammad should post it's information to and " +"press on \"Add Incoming WebHooks integration\". If you're ready, copy the " +"provided WebHook URL and go to your Zammad installation." msgstr "" -#: ../system/subscription/index.rst:58 -msgid "Paid instance" +#: ../system/integrations/slack.rst:56 +msgid "" +"You need administrative rights on the Slack Workspace. The link to the app " +"directory is normally ``https://[workspace-name].slack.com/apps`` ." msgstr "" -#: ../system/subscription/index.rst:57 +#: ../system/integrations/slack.rst:63 msgid "" -"If you're a paying customer and canceled your subscription, the instance " -"removal will take place the day after your last subscription day." +"To configure the slack integration, log in to Zammad and go to Integrations " +"(System) => Slack in the admin panel." msgstr "" -#: ../system/subscription/index.rst:60 -msgid "Can removed instances be restored?" +#: ../system/integrations/slack.rst:66 +msgid "" +"Here you can choose on what evens Zammad should post information about a " +"ticket to your Slack channel. Next you need to device what groups shall be " +"affected by this, as anybody with access to that specific Slack channel can " +"read at least parts of the ticket this might be a privacy issue, if you " +"select the wrong groups. The username is simply the name that Zammad uses as " +"display name inside the Slack chat. The channel defines the Slack channel " +"the information is being posted in. As last option, you can set a custom " +"icon for posting to slack." msgstr "" -#: ../system/subscription/index.rst:61 -msgid "No. Once your instance has been removed, a restoration is not possible." +#: ../system/integrations/slack.rst:74 +msgid "" +"When you're ready, just hit \"Submit\" and enable the integration. Zammad " +"will now post new ticket information based on the trigger you chose. Below " +"the options you have the recent log that shows the latest requests to Slack " +"for debugging if needed." msgstr "" -#: ../system/subscription/plan.rst:2 ../system/subscription/plan.rst:38 -msgid "Plan" +#: ../system/integrations/slack.rst:81 +msgid "" +"If you leave the Icon URL empty, Zammad will use the Zammad logo instead. " +"The icon should be a square PNG file." msgstr "" -#: ../system/subscription/plan.rst:16 -msgid "Subscription" +#: ../system/integrations/slack.rst:90 +msgid "" +"The following figure shows how it will look if you choose to receive updates " +"on created and updated tickets. On every post Zammad sends to the Slack " +"channel, you can create new threads to discuss about the new article." msgstr "" -#: ../system/subscription/plan.rst:5 +#: ../system/integrations/slack.rst:96 msgid "" -"On the top of the subscription summary you'll find the number of used and " -"available (booked) agent seats. By using the *see more* link you can also " -"expand an agent list to see the currently configured active agents. This " -"list *does not* count accounts with admin permissions only." +"If you just want to keep track of soon escalating or already escalated " +"tickets, it will look the the following figure. Zammad changes the color in " +"front of the post so you can easily see the state of the ticket." msgstr "" -#: ../system/subscription/plan.rst:0 +#: ../system/integrations/slack.rst:102 msgid "" -"Within subscription you can always see how many agents are still\n" -"available to add and who uses the seats." +"If you change the state, Zammad will also put information on what state the " +"ticket gets and (if pending state) the date until it pends. You'll also " +"recognize the color codes in front of posts on slack, as they are exact the " +"same the ticket state colors you'll see in Zammad!" msgstr "" -#: ../system/subscription/plan.rst:14 -msgid "" -"Learn more on how to manage your agents in general :doc:`here `." +#: ../system/integrations/smime/index.rst:2 +msgid "S/MIME" msgstr "" -#: ../system/subscription/plan.rst:19 +#: ../system/integrations/smime/index.rst:11 msgid "" -"This section gives you an overview of the available plans and their " -"functions / limits. If you require a more detailed table, check our " -"`detailed pricing table `_ for more." +"S/MIME is the most widely-supported method for secure email communication. " +"With S/MIME, you can exchange **signed** and **encrypted** messages with " +"others." msgstr "" -#: ../system/subscription/plan.rst:23 +#: ../system/integrations/smime/index.rst:15 msgid "" -"Your selection in this step will decide on the base agent price and e.g. " -"agent limits that might apply in the summary step." +"is proof that a message hasn't been tampered with or sent by an impersonator." msgstr "" -#: ../system/subscription/plan.rst:26 +#: ../system/integrations/smime/index.rst:17 msgid "" -"The green *Selected* button will also tell you what plan you're currently in." +"In other words, it guarantees a message's **integrity** and **authenticity**." msgstr "" -#: ../system/subscription/plan.rst:30 -msgid "" -"Trial instances are running at Professional with 3 agents. The plan cannot " -"be changed during the trial for technical reasons, if you require more " -"agents for testing, please contact `our sales team `_ with a reason for the raise request." +#: ../system/integrations/smime/index.rst:22 +msgid "In other words, it guarantees **privacy** and **data security**." +msgstr "" + +#: ../system/integrations/smime/index.rst:28 +msgid "Screencast demo of S/MIME features for both new tickets and replies" msgstr "" -#: ../system/subscription/plan.rst:0 +#: ../system/integrations/smime/index.rst:28 msgid "" -"Screenshot showing three available packages for a hosted Zammad\n" -"instance" +"Once S/MIME has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " +"appear in the ticket composer." msgstr "" -#: ../system/subscription/plan.rst:83 -msgid "Summary" +#: ../system/integrations/smime/index.rst:32 +msgid ":doc:`🔪 Prerequisites `" msgstr "" -#: ../system/subscription/plan.rst:41 +#: ../system/integrations/smime/index.rst:31 msgid "" -"In this section you can adjust the settings of the previous selected plan." +"New to S/MIME? This section helps you to find certificate providers and " +"points out Limitations." msgstr "" -#: ../system/subscription/plan.rst:45 -msgid "" -"Note that upgrading (more agents, higher package) is always possible, " -"however, downgrading will only happen when your billing period renews." +#: ../system/integrations/smime/index.rst:35 +msgid ":doc:`📝 Manage Certificates `" msgstr "" -#: ../system/subscription/plan.rst:49 -msgid "" -"Upgrading resets your billing period and existing credit will be deducted " -"from the new total." +#: ../system/integrations/smime/index.rst:35 +msgid "Add and download certificates; configure group default behaviors." msgstr "" -#: ../system/subscription/plan.rst:58 -msgid "Billing cycle" +#: ../system/integrations/smime/index.rst:38 +msgid ":doc:`😦 Troubleshooting `" msgstr "" -#: ../system/subscription/plan.rst:53 -msgid "" -"You can choose between either monthly or yearly billing. The price per agent " -"will be cheaper if you decide for yearly billing." +#: ../system/integrations/smime/index.rst:38 +msgid "Took a wrong turn? About recent logs and common issues." msgstr "" -#: ../system/subscription/plan.rst:56 +#: ../system/integrations/smime/index.rst:43 msgid "" -"If you're still trying out things and are unsure of the right package for " -"your instance, you may want to choose monthly first and then upgrade to " -"yearly when you're sure." +"For more details on how S/MIME integration works on the agent side, see the :" +"user-docs:`user docs `." msgstr "" -#: ../system/subscription/plan.rst:66 -msgid "Plan: (Starter|Professional|Plus) - Agents" +#: ../system/integrations/smime/manage-certificates.rst:2 +msgid "Manage Certificates" msgstr "" -#: ../system/subscription/plan.rst:61 -msgid "Choose the number of agents you require for your instance." +#: ../system/integrations/smime/manage-certificates.rst:4 +msgid "" +"S/MIME is **disabled by default**. Enable it to start adding certificates." msgstr "" -#: ../system/subscription/plan.rst:63 -msgid "" -"Keep in mind that some packages may have agent limits. Depending on the " -"previous chosen package, you won't be able to exceed specific agent numbers. " -"Also note that setting less agents than currently configured is not possible." +#: ../system/integrations/smime/manage-certificates.rst:10 +msgid "Dialogue to add new certificates or private keys" msgstr "" -#: ../system/subscription/plan.rst:69 -msgid "Total" +#: ../system/integrations/smime/manage-certificates.rst:10 +msgid "" +"Manage certificates in the Admin Panel under **System > Integrations > S/" +"MIME**. Certificates may be pasted in as plain text or uploaded from a file." msgstr "" -#: ../system/subscription/plan.rst:69 -msgid "This will be the net total you're going to be billed." +#: ../system/integrations/smime/manage-certificates.rst:14 +msgid "Add Certificate Data" msgstr "" -#: ../system/subscription/plan.rst:71 -msgid "" -"By using the *Update subscription* button, the instance package will be " -"adjusted immediately. If you didn't provide a payment method yet, Zammad " -"will request you to provide one at this point." +#: ../system/integrations/smime/manage-certificates.rst:36 +msgid "Add Certificate" msgstr "" -#: ../system/subscription/plan.rst:77 +#: ../system/integrations/smime/manage-certificates.rst:17 msgid "" -"In case you're still within the trial period, this means that the trial will " -"be over immediately!" +"Import public-key certificates for both your own organization and your " +"contacts." msgstr "" -#: ../system/subscription/plan.rst:80 -msgid "Down- or upgrading during the trial period *is not* possible." +#: ../system/integrations/smime/manage-certificates.rst:19 +msgid "" +"You can also add a bunch of certificates in one go by providing a single " +"file with all relevant certificates." msgstr "" -#: ../system/subscription/plan.rst:0 -msgid "Screenshot showing payment options and a pricing summary" +#: ../system/integrations/smime/manage-certificates.rst:22 +msgid "🕵️ **ALWAYS verify certificates in-person or over the phone!**" msgstr "" -#: ../system/subscription/plan.rst:99 -msgid "Payment method" +#: ../system/integrations/smime/manage-certificates.rst:24 +msgid "" +"The whole point of signatures is to alert you when someone is trying to " +"pretend to be someone they're not. Never accept a certificate from someone " +"online without verifying it first." msgstr "" -#: ../system/subscription/plan.rst:86 -msgid "You can pay via credit card or SEPA mandate." +#: ../system/integrations/smime/manage-certificates.rst:28 +msgid "📇 **What about trusted certificate authorities?**" msgstr "" -#: ../system/subscription/plan.rst:91 -msgid "Credit card" +#: ../system/integrations/smime/manage-certificates.rst:30 +msgid "" +"In some cases (e.g. when dealing with large enterprises), you may be given a " +"certificate for an entire CA, rather than a single contact. Add it here to " +"trust *all* certificates issued by that CA." msgstr "" -#: ../system/subscription/plan.rst:89 +#: ../system/integrations/smime/manage-certificates.rst:35 msgid "" -"Simply follow the dialogue by clicking *authorize* and confirm -if required " -"by your bank- your consent to Zammad using your card for the payments." +"Commercial CAs can usually be verified online. Zammad does not include a " +"list of built-in, trusted CAs." msgstr "" -#: ../system/subscription/plan.rst:95 -msgid "SEPA" +#: ../system/integrations/smime/manage-certificates.rst:57 +msgid "Add Private Key" msgstr "" -#: ../system/subscription/plan.rst:94 +#: ../system/integrations/smime/manage-certificates.rst:39 msgid "" -"Provide the requested information of the bank account holder and update if " -"you're ready. You'll then receive an email with the SEPA mandate." +"Once you've added a public-key certificate, you can import its matching " +"private key." msgstr "" -#: ../system/subscription/plan.rst:97 +#: ../system/integrations/smime/manage-certificates.rst:42 msgid "" -"Technically there's also the possibility to pay via invoice, however - this " -"method only applies to a fairly low number of instances. Please contact `our " -"sales team `_ for more information." +"Private keys are for **your own organization only**; never ask your contacts " +"for their private keys." msgstr "" -#: ../system/translations.rst:2 -msgid "Translations" -msgstr "Översättningar" +#: ../system/integrations/smime/manage-certificates.rst:0 +msgid "" +"S/MIME integration showing configured certificates and possible issues with " +"Logging" +msgstr "" -#: ../system/translations.rst:4 +#: ../system/integrations/smime/manage-certificates.rst:50 msgid "" -"Translations of Zammad are processed centrally in our `Weblate instance " -"`_. This allows non-developers to review " -"and update translation texts of the language they actually speak." +"A note is displayed on certificates with a matching private key (see line 2)." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:52 +msgid "📤 **Certificates and private keys must be uploaded separately.**" msgstr "" -#: ../system/translations.rst:9 +#: ../system/integrations/smime/manage-certificates.rst:54 msgid "" -"Your language is in an incomplete translation state or has typos? Please " -"consider helping us in sorting this out! All you need is either a GitHub " -"account or to register directly in our instance." +"If your certificate and private key are bundled together in the same file or " +"PEM block, import it twice (once using each button)." msgstr "" -#: ../system/translations.rst:13 -msgid "" -"Did you know? This is also where the documentation translations are handled. " -"🤓" +#: ../system/integrations/smime/manage-certificates.rst:57 +msgid "Please note that bulk imports of private keys are not possible." msgstr "" -#: ../system/translations.rst:15 -msgid "" -"Have a look in our :docs:`contribution section ` in the system documentation to get started!" +#: ../system/integrations/smime/manage-certificates.rst:60 +msgid "Download Certificate Data" msgstr "" -#: ../system/translations.rst:20 -msgid "Local Translations" +#: ../system/integrations/smime/manage-certificates.rst:62 +msgid "" +"You can download the earlier provided certificates and private keys at any " +"time from your Zammad instance." msgstr "" -#: ../system/translations.rst:22 +#: ../system/integrations/smime/manage-certificates.rst:65 msgid "" -"Apart from these system translations, there's still local translations you " -"can manage. This is relevant if you added custom objects that require " -"translations or even custom states and priorities." +"Please note that passphrase-protected private keys stay protected and when " +"you download them, you have to know the passphrase to use them after " +"downloading." msgstr "" -#: ../system/translations.rst:None -msgid "Translation management screen within the admin menu" +#: ../system/integrations/smime/manage-certificates.rst:73 +msgid "Dialogue to download certificates or private keys" msgstr "" -#: ../system/translations.rst:31 -msgid "Updating Translations" +#: ../system/integrations/smime/manage-certificates.rst:73 +msgid "Download stored certificates and their keys" msgstr "" -#: ../system/translations.rst:33 +#: ../system/integrations/smime/manage-certificates.rst:78 msgid "" -"Because of how Zammad ships translations, the only way to update the system " -"translations is to update your Zammad installation. The benefit of this is " -"that you no longer need internet access during a Zammad upgrade as the " -"package has everything it requires already." +"The ticket composer will set all outgoing messages to **signed and " +"encrypted** by default (assuming the required certificates exist)." msgstr "" -#: ../system/translations.rst:39 -msgid "Translation of Custom Objects" +#: ../system/integrations/smime/manage-certificates.rst:82 +msgid "These defaults can be modified on a per-group basis:" msgstr "" -#: ../system/translations.rst:41 -msgid "" -"No problem at all! You can customize any translation locally, even if it is " -"not initially provided by the system." +#: ../system/integrations/smime/manage-certificates.rst:None +msgid "Zammad allowing to choose the default behavior on per group basis" msgstr "" -#: ../system/translations.rst:44 +#: ../system/integrations/smime/manage-certificates.rst:89 msgid "" -"Translation is supported for a broad number of features, including but not " -"limited to custom:" +"Of course, agents can always manually change these settings on each email " +"they send out." msgstr "" -#: ../system/translations.rst:47 -msgid "Object Attributes" +#: ../system/integrations/smime/prerequisites.rst:4 +msgid "A certificate *and* private key for your own organization" msgstr "" -#: ../system/translations.rst:48 -msgid "Ticket Macros" +#: ../system/integrations/smime/prerequisites.rst:6 +msgid "" +"(Use this to ✒️ **sign outgoing messages** and 🔓 **decrypt incoming " +"messages**.)" msgstr "" -#: ../system/translations.rst:49 -msgid "Ticket Overviews" +#: ../system/integrations/smime/prerequisites.rst:9 +msgid "" +"Certificates belonging your contacts, or their issuing certificate authority " +"(CA)" msgstr "" -#: ../system/translations.rst:50 -msgid "Ticket Priorities" +#: ../system/integrations/smime/prerequisites.rst:11 +msgid "" +"(Use these to ✅ **verify incoming message signatures** and 🔒 **encrypt " +"outgoing messages**.)" msgstr "" -#: ../system/translations.rst:51 -msgid "Ticket States" +#: ../system/integrations/smime/prerequisites.rst:14 +msgid "🙋 **I'm new to S/MIME. Where can I get a certificate?**" msgstr "" -#: ../system/translations.rst:54 -msgid "Customizing Translations" +#: ../system/integrations/smime/prerequisites.rst:16 +msgid "" +"The easiest way to get certificates is to buy an annual subscription through " +"a commercial CA, such as:" msgstr "" -#: ../system/translations.rst:56 +#: ../system/integrations/smime/prerequisites.rst:19 msgid "" -"Within the translation screen, simply click on the **New Translation** " -"button." +"`Sectigo (formerly Comodo) `_" msgstr "" -#: ../system/translations.rst:None -msgid "New translation dialog" +#: ../system/integrations/smime/prerequisites.rst:20 +msgid "`Secorio `_" msgstr "" -#: ../system/translations.rst:62 -msgid "" -"In the dialog you can immediately enter the exact translation source (if you " -"know it) and your custom translation text for it and click **Submit**." +#: ../system/integrations/smime/prerequisites.rst:21 +msgid "`GlobalSign `_" msgstr "" -#: ../system/translations.rst:65 -msgid "" -"Alternatively, try to search for translation suggestions in the list below. " -"Selecting an item from the list will pre-fill the translation source for you " -"and then you can just enter your custom translation." +#: ../system/integrations/smime/prerequisites.rst:23 +msgid "(Zammad is not affiliated with these CAs in any way.)" msgstr "" -#: ../system/translations.rst:69 +#: ../system/integrations/smime/prerequisites.rst:25 msgid "" -"The target language will always default to your current language selection. " -"If you need to translate for a different language, simply change the " -"selection before submitting." +"You can also generate your own self-signed certificates, but the process is " +"complicated and usually 🙅 **involves extra work for your contacts**." msgstr "" -#: ../system/translations.rst:73 +#: ../system/integrations/smime/prerequisites.rst:29 msgid "" -"All your custom translations will show up in the overview table when added. " -"And they will even persist across Zammad updates!" +"Bear in mind that 🤝 **S/MIME only works if the other party is using it, too." +"**" msgstr "" -#: ../system/translations.rst:76 +#: ../system/integrations/smime/prerequisites.rst:32 +msgid "Certificate and Private Key Checks on Upload" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:34 msgid "" -"Make sure to reload your browser if a translated string is not displayed." +"The certificate and public key validation is based on the ``X509v3`` " +"extensions." msgstr "" -#: ../system/translations.rst:80 -msgid "Reverting to Original Translations" +#: ../system/integrations/smime/prerequisites.rst:49 +msgid "Uploading a *client certificate*?" msgstr "" -#: ../system/translations.rst:82 -msgid "" -"If you want to revert a custom translation to original text, simply use the " -"appropriate action within the row of the overview table." +#: ../system/integrations/smime/prerequisites.rst:41 +msgid "The following attributes are required then:" msgstr "" -#: ../system/translations.rst:85 -msgid "" -"Depending on the type of the translation source, the action has a slightly " -"different name:" +#: ../system/integrations/smime/prerequisites.rst:39 +msgid "Subject Alternative Name (at least one email address has to be present)" msgstr "" -#: ../system/translations.rst:88 -msgid "**Reset** for customized system translations" +#: ../system/integrations/smime/prerequisites.rst:40 +msgid "Key Usage (``Digital Signature`` and/or ``Key Encipherment``)" msgstr "" -#: ../system/translations.rst:89 -msgid "**Remove** for customized local translations" +#: ../system/integrations/smime/prerequisites.rst:41 +msgid "Public key algorithm (either ``RSA`` or ``EC``)" msgstr "" -#: ../system/translations.rst:91 +#: ../system/integrations/smime/prerequisites.rst:43 msgid "" -"In both cases, the action will remove the customized translation after a " -"confirmation." +"The Extended Key Usage attribute is optional. If the certificate provides " +"the named attribute, than it must contain the value ``E-mail Protection``." msgstr "" -#: ../system/translations.rst:None -msgid "Screenshot showing the location of the Remove action" +#: ../system/integrations/smime/prerequisites.rst:46 +msgid "" +"Please note that any usable email adress has to be prefixed with ``email:`` " +"or ``rfc822:``." msgstr "" -#: ../system/translations.rst:99 -msgid "Inline Translations" +#: ../system/integrations/smime/prerequisites.rst:49 +msgid "The named public key algorithms are mandatory for private keys as well." msgstr "" -#: ../system/translations.rst:101 -msgid "" -"If you prefer a more hands-on approach, you can activate the inline or on-" -"screen translation feature by pressing ``ctrl`` + ``alt`` + ``t`` at any " -"time and on any screen." +#: ../system/integrations/smime/prerequisites.rst:54 +msgid "Uploading a *CA certificate*?" msgstr "" -#: ../system/translations.rst:105 +#: ../system/integrations/smime/prerequisites.rst:52 msgid "" -"All customizable translation texts will be highlighted for you on the " -"screen. Just click into the highlighted area and update the text in place." +"In the case of an uploaded CA certificate, providing the value ``CA:TRUE`` " +"in the attribute *Basic Contstraints*, the previously mentioned attributes " +"are not verified." msgstr "" -#: ../system/translations.rst:None -msgid "Inline translation mode activated for the Overview screen" +#: ../system/integrations/smime/prerequisites.rst:56 +msgid "" +"In general, the usage of any expired (``Not After``) or not yet valid (``Not " +"Before``) certificate is denied for outgoing emails." msgstr "" -#: ../system/translations.rst:112 -msgid "" -"When finished editing, simply press ``ctrl`` + ``alt`` + ``t`` again to " -"deactivate." +#: ../system/integrations/smime/prerequisites.rst:59 +msgid "Example certificate:" msgstr "" -#: ../system/translations.rst:117 +#: ../system/integrations/smime/prerequisites.rst:85 msgid "" -"Even though it's available on any screen, the inline translation feature " -"requires admin permissions. It works only for the current language " -"selection. If you need to translate a different language, first change the " -"language in your :user-docs:`profile settings `." +"Please note that Zammad will distrust senders by default. This means that " +"you're always required to provide certificate data, no matter if for signing " +"or encrypting." msgstr "" -#: ../system/variables.rst:2 -msgid "Variables" +#: ../system/integrations/smime/prerequisites.rst:89 +msgid "This is by design and can't be adjusted." msgstr "" -#: ../system/variables.rst:4 +#: ../system/integrations/smime/troubleshooting.rst:4 msgid "" -"Please note that this is just an overview of available variables. It might " -"be incomplete or variables might not be available within some functions. If " -"you're missing variables or are not sure if something is not working as " -"expected, feel free to ask over at the `Community `_." +"All of the system's latest S/MIME activity is displayed in the **Recent " +"Logs** section." msgstr "" -#: ../system/variables.rst:10 -msgid "" -"Variables can be called by typing ``::`` (just like text modules in the " -"frontend), as long as you're in a supported text field within the backend. " -"Zammad will display all variables being available within this context and " -"replace it to the variable as soon as you selected an entry." +#: ../system/integrations/smime/troubleshooting.rst:11 +msgid "Sample entries of in- and outgoing S/MIME related emails." msgstr "" -#: ../system/variables.rst:15 +#: ../system/integrations/smime/troubleshooting.rst:11 msgid "" -"You have an empty field which you referenced and it appears as ``-``? That's " -"currently working as designed - you might want to ensure that these fields " -"always have a value." +"Logs report the status and details of all mail, both incoming and outgoing, " +"that used signing/verification or encryption/decryption." msgstr "" -#: ../system/variables.rst:20 -msgid "Variable Categories" +#: ../system/integrations/smime/troubleshooting.rst:14 +msgid "" +"This log does **not** include email sent by :doc:`triggers ` or the :doc:`scheduler `. For those, check your " +"``production.log``." msgstr "" -#: ../system/variables.rst:31 -msgid "Wait, What About Custom Objects?" +#: ../system/integrations/smime/troubleshooting.rst:20 +msgid "Common Issues" msgstr "" -#: ../system/variables.rst:33 -msgid "" -"Good point! Of course, we can't predict what objects you might create, but " -"we can give you a hint on how to put the puzzle together to get your custom " -"values." +#: ../system/integrations/smime/troubleshooting.rst:30 +msgid "I received a signed/encrypted email before I set up S/MIME integration" msgstr "" -#: ../system/variables.rst:36 +#: ../system/integrations/smime/troubleshooting.rst:23 msgid "" -"For this, we'll talk about the inner part of the variable (so everything " -"within ``#{}``), please put the outer part around to have a valid variable. " -"The first part of the variable name consist of the object type. Currently " -"these are:" +"No problem. Once S/MIME has been enabled and the appropriate certificates " +"have been added, agents will be prompted to retry verification/decryption on " +"matching emails." msgstr "" -#: ../system/variables.rst:41 -msgid "Ticket (``ticket``)" +#: ../system/integrations/smime/troubleshooting.rst:0 +msgid "Screenshot of user prompt to retry decryption" msgstr "" -#: ../system/variables.rst:42 -msgid "User (``user``)" +#: ../system/integrations/smime/troubleshooting.rst:38 +msgid "The 🔒 **Encrypt** button is disabled" msgstr "" -#: ../system/variables.rst:43 -msgid "Organization (``organization``)" +#: ../system/integrations/smime/troubleshooting.rst:33 +msgid "Have you added the recipient's certificate?" msgstr "" -#: ../system/variables.rst:44 -msgid "Group (``group``)" +#: ../system/integrations/smime/troubleshooting.rst:34 +msgid "Are you sure the recipient's certificate is valid?" msgstr "" -#: ../system/variables.rst:46 -msgid "" -"The second part is the name of the object. This is the name you define " -"during object creation and can be found within the object menu at any time. " -"The first and second part of a variable is divided by a point, e.g.: " -"``ticket.number`` which will in total be ``#{ticket.number}``." +#: ../system/integrations/smime/troubleshooting.rst:35 +msgid "Have you checked your ``production.log`` for more details?" msgstr "" -#: ../system/variables.rst:51 +#: ../system/integrations/smime/troubleshooting.rst:37 msgid "" -"Now, in some situations it's possible that you'll need to use a third part. " -"The best example for such a situation would be a ``select`` or ``tree-" -"select`` field which will by default return the key value, not it's display " -"name. For this, just extend your variable with ``.value``. This will result " -"in ``#{ticket.select.value}``." +"If encryption doesn't work in the composer, it won't work in :doc:`triggers " +"` or the :doc:`scheduler ` either!" msgstr "" -#: ../system/variables.rst:60 -msgid "Using Translated Variables" +#: ../system/integrations/smime/troubleshooting.rst:42 +msgid "The ✅ **Sign** button is disabled" msgstr "" -#: ../system/variables.rst:62 +#: ../system/integrations/smime/troubleshooting.rst:41 msgid "" -"If you want to use a translated variable in triggers or schedulers, you can " -"extend the placeholder like this: ``#{t(ticket.state.name)}``. The ``t`` " -"tells Zammad to search for fitting translated strings. The used output " -"language is based on the system language of Zammad which you can set in the " -"admin panel under :doc:`/settings/branding` or based on the selected locale " -"in the trigger/scheduler edit dialog." +"Have you added **both the certificate and private key** for your " +"organization?" msgstr "" -#: ../system/variables.rst:69 +#: ../system/integrations/smime/troubleshooting.rst:42 msgid "" -"A possible use-case: you want to send your customers updates on tickets via " -"trigger or scheduler which should include the state of the ticket. Using the " -"default ``#{ticket.state.name}`` (without the translation flag ``t()``) " -"would lead to the output of the original (english) name of the state." +"Does the email address on the certificate match the email address of the " +"agent/group composing the email?" msgstr "" -#: ../system/variables.rst:75 -msgid "Date and Time Formatting" +#: ../system/integrations/smime/troubleshooting.rst:45 +msgid "Error: “Fingerprint already taken”" msgstr "" -#: ../system/variables.rst:77 -msgid "" -"The system (trigger/scheduler selected) locale and timezone predefines a " -"default format of date and timestamp. This format is customizable by using " -"the ``dt()`` method." +#: ../system/integrations/smime/troubleshooting.rst:45 +msgid "Are you sure you haven't added this certificate already?" msgstr "" -#: ../system/variables.rst:79 -msgid "The method arguments are as follows:" +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Error: “❌ invalid byte sequence in UTF-8”" msgstr "" -#: ../system/variables.rst:81 -msgid "The date or timestamp variable you want to format." +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Please ensure to provide PEM formatted certificate and keys." msgstr "" -#: ../system/variables.rst:82 -msgid "The output format string." +#: ../system/integrations/smime/troubleshooting.rst:49 +msgid "Did you check if the provided file is a valid certificate or key?" msgstr "" -#: ../system/variables.rst:83 -msgid "The timezone to apply (optional)." +#: ../system/integrations/zabbix.rst:2 +msgid "Zabbix Integration" msgstr "" -#: ../system/variables.rst:86 +#: ../system/integrations/zabbix.rst:5 msgid "" -"``#{dt(ticket.updated_at, \"%A %Y-%m-%d %H:%M in the office\", \"Europe/" -"Berlin\")}``" +"This guide describes how to integrate your Zabbix 5.4 installation with " +"Zammad using the Zabbix webhook feature. This guide will provide " +"instructions on setting up a media type, a user and an action in Zabbix." msgstr "" -#: ../system/variables.rst:87 -msgid "Monday, 2024-03-18 15:31 in the office" +#: ../system/integrations/zabbix.rst:12 +msgid "Zammad with enabled HTTP Token Authentication" msgstr "" -#: ../system/variables.rst:89 -msgid "" -"If you want to use our example, make sure to paste the string above without " -"formatting (``CTRL+Shift+v``), otherwise it won't work." +#: ../system/integrations/zabbix.rst:13 +msgid "Zabbix version 5.4 or higher" msgstr "" -#: ../system/variables.rst:93 -msgid "The following table lists available format directives:" +#: ../system/integrations/zabbix.rst:16 +msgid "Setting up a Zammad" msgstr "" -#: ../system/variables.rst:99 -msgid "Parameter" +#: ../system/integrations/zabbix.rst:18 +msgid "Enable **API Token Access** in Settings > System > API." msgstr "" -#: ../system/variables.rst:102 -msgid "``%Y``" +#: ../system/integrations/zabbix.rst:20 +msgid "" +"Create a **new user** for a Zabbix alerter with an **email address** and " +"create a personal user token with **ticket.agent** permissions." msgstr "" -#: ../system/variables.rst:103 -msgid "Year with 4 digits" +#: ../system/integrations/zabbix.rst:24 +msgid "Zabbix Webhook Configuration" msgstr "" -#: ../system/variables.rst:104 -msgid "Use ``%y`` for year with 2 digits" +#: ../system/integrations/zabbix.rst:27 +msgid "Create a Global Macro" msgstr "" -#: ../system/variables.rst:105 -msgid "``%m``" +#: ../system/integrations/zabbix.rst:29 +msgid "" +"Before setting up the **Webhook**, you need to setup the global macro " +"**{$ZABBIX.URL}**, which must contain the **URL** to the **Zabbix frontend**." msgstr "" -#: ../system/variables.rst:106 -msgid "Month of year (as number with zero-padding)" +#: ../system/integrations/zabbix.rst:33 +msgid "" +"In the **Administration** > **Media types** section, import the `Template`_." msgstr "" -#: ../system/variables.rst:107 -msgid "Use ``%-m`` for month without zero-padding" +#: ../system/integrations/zabbix.rst:38 +msgid "Open the added **Zammad** media type and set:" msgstr "" -#: ../system/variables.rst:108 -msgid "``%d``" +#: ../system/integrations/zabbix.rst:40 +msgid "**zammad\\_access\\_token** to the your **Personal User Token**" msgstr "" -#: ../system/variables.rst:109 -msgid "Day of month (as number with zero-padding)" +#: ../system/integrations/zabbix.rst:41 +msgid "" +"**zammad\\_url** to the **frontend URL** of your **Zammad** installation" msgstr "" -#: ../system/variables.rst:110 -msgid "Use ``%e`` for day without zero-padding" +#: ../system/integrations/zabbix.rst:43 +msgid "**zammad\\_customer** to your **Zammad user email**." msgstr "" -#: ../system/variables.rst:111 -msgid "``%H``" +#: ../system/integrations/zabbix.rst:44 +msgid "" +"**zammad\\_enable\\_tags** to **true** or **false** to enable or disable " +"trigger tags. **Important**: if you enable tag support, each tag is set with " +"a separate request." msgstr "" -#: ../system/variables.rst:112 -msgid "Hour of day in 24h notation with zero-padding" +#: ../system/integrations/zabbix.rst:48 +msgid "" +"If you want to prioritize issues according to **severity** values in Zabbix, " +"you can define mapping parameters:" msgstr "" -#: ../system/variables.rst:113 -msgid "Use ``%k`` for hour without zero-padding" +#: ../system/integrations/zabbix.rst:51 +msgid "**severity\\_**: Zammad priority ID" msgstr "" -#: ../system/variables.rst:114 -msgid "``%I``" +#: ../system/integrations/zabbix.rst:53 +msgid "Click the **Update** button to save the **Webhook** settings." msgstr "" -#: ../system/variables.rst:115 -msgid "Hour of day in 12h notation with zero-padding" +#: ../system/integrations/zabbix.rst:55 +msgid "" +"To receive notifications in **Zammad**, you need to create a **Zabbix user** " +"and add **Media** with the **Zammad** type." msgstr "" -#: ../system/variables.rst:116 +#: ../system/integrations/zabbix.rst:58 msgid "" -"Use ``%l`` for hour without zero-padding and ``%p`` / ``%P`` for meridian " -"indicator" +"For **Send to**: enter any text, as this value is not used, but is required." msgstr "" -#: ../system/variables.rst:117 -msgid "``%M``" +#: ../system/integrations/zabbix.rst:61 +msgid "" +"For more information, use the `Zabbix documentation `_." msgstr "" -#: ../system/variables.rst:118 -msgid "Minute of hour" +#: ../system/maintenance.rst:2 +msgid "Maintenance" msgstr "" -#: ../system/variables.rst:120 -msgid "``%S``" +#: ../system/maintenance.rst:4 +msgid "" +"Zammad comes with a maintenance mode that you can use for e.g. updating the " +"instance or changing settings while restricting availability and functions." msgstr "" -#: ../system/variables.rst:121 -msgid "Second of Minute" +#: ../system/maintenance.rst:13 +msgid "Mode" msgstr "" -#: ../system/variables.rst:123 -msgid "``%A``" +#: ../system/maintenance.rst:8 +msgid "The mode setting allows you to enable or disable the maintenance mode." msgstr "" -#: ../system/variables.rst:124 -msgid "Weekday name" +#: ../system/maintenance.rst:10 +msgid "Defaults to *off*." msgstr "" -#: ../system/variables.rst:125 -msgid "Use ``%a`` for abbreviated name or ``%^A`` for uppercase name" +#: ../system/maintenance.rst:12 +msgid "" +"The maintenance mode will restrict access to administrative roles only. This " +"means agents and customers are logged off." msgstr "" -#: ../system/variables.rst:126 -msgid "``%B``" +#: ../system/maintenance.rst:23 +msgid "@Login" msgstr "" -#: ../system/variables.rst:127 -msgid "Month name" +#: ../system/maintenance.rst:16 +msgid "" +"This setting allows you to provide a login message within a green banner " +"above the login screen. Click into the green banner in the settings page to " +"adjust your message. To activate the message, activate the *@Login* setting." msgstr "" -#: ../system/variables.rst:128 -msgid "Use ``%b`` for abbreviated name" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing the default login message within the\n" +"settings page" msgstr "" -#: ../system/variables.rst:129 -msgid "``%U``" +#: ../system/maintenance.rst:26 +msgid "" +"Send an informative message to **all active sessions**. This comes handy to " +"inform your agents e.g. about mayor outages or to force reloads after " +"configuration changes." msgstr "" -#: ../system/variables.rst:130 -msgid "Week number of current year" +#: ../system/maintenance.rst:31 +msgid "This is the messages title (slightly bigger than the normal message)." msgstr "" -#: ../system/variables.rst:131 -msgid "Use ``%W`` for a different calculation method" +#: ../system/maintenance.rst:34 +msgid "The text you want to provide to your logged in sessions." +msgstr "" + +#: ../system/maintenance.rst:39 +msgid "Reload application" msgstr "" -#: ../system/variables.rst:134 +#: ../system/maintenance.rst:37 msgid "" -"We support the known format directives for the Ruby built-in method " -"``strftime`` of the ``DateTime`` class. For more information, see `here " -"`_." +"Selecting this option will change the message acceptance button from *Close* " +"(with nothing happening) to *Continue session*, which forces the application " +"to reload." msgstr "" -#: ../system/variables/article.rst:2 -msgid "Articles" +#: ../system/maintenance.rst:43 +msgid "" +"If you have customers that are logged in to Zammad, they'll also be notified " +"if they're active in that moment." +msgstr "" + +#: ../system/maintenance.rst:48 +msgid "Example without reload application" msgstr "" -#: ../system/variables/article.rst:4 ../system/variables/config.rst:4 -#: ../system/variables/current-user.rst:4 ../system/variables/ticket.rst:4 +#: ../system/maintenance.rst:52 msgid "" -"If you're missing variables or are not sure if something is not working as " -"expected, feel free to ask over at the `Community `_." +"Message setting within Zammad's admin settings without ticket reload " +"application setting." msgstr "" -#: ../system/variables/article.rst:6 +#: ../system/maintenance.rst:0 msgid "" -"Below you can find all available ticket article-based variables within " -"Zammad. These can be called via Triggers for example. If you're unsure if " -"Zammad does support variables at the point you're at, you can try to type " -"``::`` to check." +"Screenshot showing the send message settings without ticket\n" +"reload application set" msgstr "" -#: ../system/variables/article.rst:9 ../system/variables/config.rst:9 -#: ../system/variables/ticket.rst:9 +#: ../system/maintenance.rst:61 ../system/maintenance.rst:85 msgid "" -"The below list gives you an example what kind of data you can expect, it's " -"not intended to explain the data itself." +"The modal all other active sessions will see upon pressing *Send to clients*." msgstr "" -#: ../system/variables/article.rst:11 -msgid "Article Variables" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing modal caused by maintenance's message\n" +"without reload application ticket" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "name" +#: ../system/maintenance.rst:72 +msgid "Example with reload application" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "variable" +#: ../system/maintenance.rst:76 +msgid "" +"Message setting within Zammad's admin settings with ticket reload " +"application setting." msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "example" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing the send message settings with ticket\n" +"reload application set" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Web" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing modal caused by maintenance's message\n" +"with reload application ticket" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.web}``" +#: ../system/monitoring.rst:2 +msgid "Monitoring" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``https://zammad.com`` or empty if not set in user object" +#: ../system/monitoring.rst:4 +msgid "" +"This function is only available in self hosted instances. If you use Zammad " +"in our cloud, we are monitoring the system on our own and take steps to fix " +"potential problems directly." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > VIP" +#: ../system/monitoring.rst:11 +msgid "" +"On the monitoring page, you can see the current health state of Zammad under " +"\"*Current Status*\" at the bottom. This can be useful if you want to have a " +"look if everything is up and running. As an example, you could have a look " +"in the monitoring when you assume that some emails aren't processed from " +"Zammad." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.vip}``" +#: ../system/monitoring.rst:17 +msgid "**Can't receive an email and the monitoring response is \"healthy\"?**" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -msgid "``true`` or ``false``" +#: ../system/monitoring.rst:19 +msgid "" +"Zammad will just inform you about unprocessable emails. This is not the case " +"for oversized emails. You can adjust the maximum email size in :doc:`../" +"channels/email/settings`." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Phone" +#: ../system/monitoring.rst:24 +msgid "Monitoring API" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.phone}``" +#: ../system/monitoring.rst:26 +msgid "" +"Beside the indication in the monitoring page, you can also use an external " +"monitoring tool to monitor Zammad's health. To request the health of Zammad, " +"you need to provide the API key (token) to the external monitoring tool. You " +"can copy the token from the \"*Current Token*\" field as well as the whole " +"API endpoint of your system (\"*Health Check*\" field), in which the API " +"token is already included." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``+4930123456789`` or empty if not set in user object" +#: ../system/monitoring.rst:37 +msgid "Screenshot showing Current Token and Health Check" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Note" +#: ../system/monitoring.rst:37 +msgid "Screenshot showing Token and Health Check" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.note}``" +#: ../system/monitoring.rst:39 +msgid "" +"In addition to that, you can reset the auto-generated token to make sure " +"that already configured monitoring systems won't work anymore. So, please " +"use this \"*Reset*\" button only if you know what you do!" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Some note about user`` or empty if not set in user object" +#: ../system/monitoring.rst:44 +msgid "Example Output" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Mobile" +#: ../system/monitoring.rst:0 +msgid "No issues found" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.mobile}``" +#: ../system/monitoring.rst:48 ../system/monitoring.rst:60 +msgid "**Indicator in Zammad**:" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Login" +#: ../system/monitoring.rst:0 +msgid "Screenshot showing monitoring with no issues" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.login}``" +#: ../system/monitoring.rst:54 ../system/monitoring.rst:66 +msgid "**API response**::" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -#: ../system/variables/ticket.rst:1 -msgid "``jdoe``" +#: ../system/monitoring.rst:0 +msgid "Issues were found" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Lastname" +#: ../system/monitoring.rst:0 +msgid "Screenshot showing monitoring with issues" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.lastname}``" +#: ../system/objects.rst:2 +msgid "Objects" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -#: ../system/variables/ticket.rst:1 -msgid "``Doe`` or empty if not set" +#: ../system/objects.rst:4 +msgid "" +"In Zammad you can add your own fields to tickets, users, organizations and " +"even groups (these are called \"objects\"). This can be useful if you need " +"to add further information to a ticket or any other object in Zammad and the " +"information doesn't fit in any existing field." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Firstname" +#: ../system/objects.rst:11 +msgid "" +"Try to avoid deleting attributes (and disable them instead) as Zammad might " +"run into unexpected conditions if they are referenced somewhere." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.firstname}``" +#: ../system/objects.rst:16 +msgid "" +"Here's an overview of object attributes. On the upper right you can add new " +"attributes. By default, there will be no custom fields - standard attributes " +"will be grayed out, you can't delete or change those. You can edit custom " +"attributes (they are displayed in black font and have a trash bin on the " +"right side) just by clicking on them." msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "``Joe`` or empty if not set" +#: ../system/objects.rst:24 +msgid "" +"Attributes you add to Zammad, no matter if they have default values or not, " +"will not update existing information. This means a new ticket field " +"technically will be empty unless you populate it." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Fax" +#: ../system/objects.rst:28 +msgid "" +"Especially in ticket scope this also means that newly added attributes will " +"be indicated as \"changed\" to agents that view the ticket. This may " +"interfere with Zammad's tabs behavior." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.fax}``" +#: ../system/objects.rst:40 +msgid "Ordering Attributes" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Email" +#: ../system/objects.rst:42 +msgid "" +"Since Zammad introduced :doc:`/system/core-workflows` the need to have a " +"custom positioning for attributes has become more important than ever." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.email}``" +#: ../system/objects.rst:45 +msgid "" +"To adjust the position of such an attribute, simply click on the attribute " +"entry in question, scroll down and adjust the position number. Please note " +"that you cannot change the positioning of default attributes." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``jdoe@example.com``" +#: ../system/objects.rst:49 +msgid "" +"In case two attributes have the same position value, Zammad will sort " +"alphabetically by name automatically." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Department" +#: ../system/objects.rst:None +msgid "" +"Screenshot showing custom attribute entries ordered in between default ones" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.department}``" +#: ../system/objects.rst:56 +msgid "Updating Database After Adding or Editing Attributes" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Sales`` or empty if not set in user object" +#: ../system/objects.rst:58 +msgid "" +"When adding or changing attributes, Zammad will not apply the changes " +"instantly, but instead shows you the changed attributes first. If you're " +"ready to go, just click on \"Update database\" to apply the changes to " +"Zammad. If you made a mistake or just want to discard your changes, click " +"\"Discard changes\"." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Address" +#: ../system/objects.rst:64 +msgid "" +"After applying the changes with \"Update Database\", a restart of Zammad is " +"**mandatory**. If you don't perform it, you may experience unexpected " +"behavior or even errors. You may want to do this kind of configuration " +"during maintenance windows." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.address}``" +#: ../system/objects.rst:72 +msgid "" +"Changes on objects require you to update the database to apply these changes." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Some street 1, 12345 Berlin`` or empty if not set in user object" +#: ../system/objects.rst:75 +msgid "**🤓 Service restarts can be automated**" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated" +#: ../system/objects.rst:0 +msgid "Hosted environments automatically restart for you." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_at}``" +#: ../system/objects.rst:0 +msgid "" +"If you're using a self-hosted installation you can use :docs:`environment " +"variables `" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``2019-10-08 15:24:47 UTC``" +#: ../system/objects.rst:82 +msgid "System Attributes" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Type > Name" +#: ../system/objects.rst:84 +msgid "" +"Zammad comes with pre-configured attributes. Some of them can't be edited " +"via UI (or at all). This is required for proper operation of Zammad and not " +"a bug." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.type.name}``" +#: ../system/objects.rst:90 +msgid "Ticket State" msgstr "" -#: ../system/variables/article.rst:1 +#: ../system/objects.rst:92 msgid "" -"``email`` (`list of article types `_)" +"If the pre-configured states aren't enough for you or you want to change " +"them, you can do so by clicking on the cogwheel icon in the state row in the " +"ticket tab. But you should be careful when changing pre-configured states. " +"This can lead to unwanted behavior in some cases." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > To" +#: ../system/objects.rst:None +msgid "Screenshot showing highlighted ticket state attribute" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.to}``" +#: ../system/objects.rst:122 +msgid "Handling of states" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``helpdesk@example.com``" +#: ../system/objects.rst:102 +msgid "" +"In the state configuration screen, you can add new states, disable states or " +"change states." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > TicketID" +#: ../system/objects.rst:0 +msgid "Screenshot showing table of default ticket states" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.ticket_id}``" +#: ../system/objects.rst:110 +msgid "" +"To add a new state, click on the \"New Ticket State\" button in the top " +"right corner. To change an existing state, simply click on the affected " +"state. This opens an edit dialog." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``1`` (not ticket number)" +#: ../system/objects.rst:114 +msgid "" +"You can also clone a state or set them to \"Default for new tickets\" or " +"\"Default for follow-ups\" by clicking on the ⁝ action button and select the " +"desired function." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Subject" +#: ../system/objects.rst:118 +msgid "" +"*Default for new tickets* means that this state is used for every newly " +"created ticket." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.subject}``" +#: ../system/objects.rst:121 +msgid "" +"*Default for follow-ups* means that this state is used if the ticket is re-" +"opened after it was closed." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``My amazing subject``" +#: ../system/objects.rst:171 +msgid "Ticket state in detail" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Sender > Name" +#: ../system/objects.rst:125 +msgid "" +"Below you can find a description for each field and option. Please head over " +"to the :ref:`example ` to see the edit dialog." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.sender.name}``" +#: ../system/objects.rst:129 +msgid "" +"This is the name of the state and what you and your agents are seeing when " +"choosing a state somewhere (e.g. in tickets, trigger configuration)." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Customer``, ``Agent`` or ``System``" +#: ../system/objects.rst:137 +msgid "" +"There are different state types you can choose from. By default, Zammad " +"comes with one state per state type." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Visibility" +#: ../system/objects.rst:140 +msgid "" +"**new**: for states for tickets that are new and it hasn't been worked on " +"them" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.internal}``" +#: ../system/objects.rst:142 +msgid "" +"**open**: for states for tickets that are in progress and agents are working " +"on them" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``false`` or ``true`` (false if not internal)" +#: ../system/objects.rst:144 +msgid "**merged**: for states for tickets that are merged with other tickets" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > From" +#: ../system/objects.rst:145 +msgid "" +"**pending reminder**: for states for tickets that are in progress and you " +"want to set a reminder. (default example: *pending reminder*)" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.from}``" +#: ../system/objects.rst:147 +msgid "" +"**pending action**: for states for tickets that are waiting for a specified " +"time and then change their state (default example: *pending close*)" msgstr "" -#: ../system/variables/article.rst:1 +#: ../system/objects.rst:150 msgid "" -"``Joe Doe `` may differ, depends on ``FROM`` of send mail" +"**closed**: for states for tickets that are finished and do not need to be " +"processed further" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Web" +#: ../system/objects.rst:153 +msgid "" +"⚠️ Choosing the correct state type is important! If you are in doubt, have a " +"look on the default states and their types!" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.web}``" +#: ../system/objects.rst:158 +msgid "Ignore escalation" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > VIP" +#: ../system/objects.rst:157 +msgid "" +"Here you can define whether tickets of this state will count to escalation " +"time or not." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.vip}``" +#: ../system/objects.rst:161 +msgid "" +"You can create a note for the state to inform other admins about the state. " +"This has no effect on tickets." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Phone" +#: ../system/objects.rst:165 +msgid "Set the state to *active* or *inactive*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.phone}``" +#: ../system/objects.rst:167 +msgid "" +"it is technically possible to set all states to inactive. To keep Zammad " +"working in such a case, the inactive flag of one of the states is ignored." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Note" +#: ../system/objects.rst:194 +msgid "Ticket state example" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.note}``" +#: ../system/objects.rst:174 +msgid "" +"Let's assume we want to create a new state which indicates that the ticket " +"has to wait for a response of a third party (e.g. service contractor or " +"manufacturer) and we want to to be able to set a reminder." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Mobile" +#: ../system/objects.rst:178 +msgid "" +"First we give the new state a proper name. In this example we call it " +"\"waiting for manufacturer\"." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.mobile}``" +#: ../system/objects.rst:181 +msgid "" +"As state type we choose \"pending reminder\". This indicates that the ticket " +"is still open and we can set a reminder. This reminder can be useful if our " +"manufacturer sometimes isn't responding or we want to remind him to give us " +"an answer." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Login" +#: ../system/objects.rst:186 +msgid "" +"We choose \"no\" for \"ignore escalation\" because we want to escalate the " +"tickets even if we are waiting on the manufacturer's feedback." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.login}``" +#: ../system/objects.rst:189 +msgid "The **result** in the creation dialog will look like this:" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Lastname" +#: ../system/objects.rst:0 +msgid "Screenshot showing ticket state creation dialog with example" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.lastname}``" +#: ../system/objects.rst:199 +msgid "Ticket Priority" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Firstname" +#: ../system/objects.rst:201 +msgid "" +"If the pre-configured priorities aren't enough for you or you want to change " +"them, you can do so by clicking on the cogwheel icon in the priority row in " +"the ticket tab:" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.firstname}``" +#: ../system/objects.rst:None +msgid "Screenshot showing highlighted ticket priority attribute" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Fax" +#: ../system/objects.rst:226 +msgid "Handling of priorities" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.fax}``" +#: ../system/objects.rst:210 +msgid "" +"In the priority configuration screen, you can add new priorities, disable " +"priorities or change priorities." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Email" +#: ../system/objects.rst:0 +msgid "Screenshot showing table of default ticket priorities" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.email}``" +#: ../system/objects.rst:218 +msgid "" +"To add a new priority, click on the \"New Priority\" button in the top right " +"corner. To change an existing priority, simply click on the affected " +"priority. This opens an edit dialog." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Department" +#: ../system/objects.rst:222 +msgid "" +"You can also clone a priority or set them to \"Default for new tickets\" by " +"clicking on the ⁝ action button and select the desired function." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.department}``" +#: ../system/objects.rst:225 +msgid "" +"*Default for new tickets* means that this priority is used for every newly " +"created ticket." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Address" +#: ../system/objects.rst:248 +msgid "Priorities in detail" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.address}``" +#: ../system/objects.rst:229 +msgid "Below you can find a description for each field and option." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created" +#: ../system/objects.rst:232 +msgid "" +"This is the name of the priority and what you and your agents are seeing " +"when choosing a priority somewhere (e.g. in tickets, trigger configuration)." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_at}``" +#: ../system/objects.rst:242 +msgid "Highlight color" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Cc" +#: ../system/objects.rst:237 +msgid "" +"Switch between *Low priority* (light blue), *High priority* (red) and - " +"(default). This affects the displayed color for ticket titles in overviews." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.cc}``" +#: ../system/objects.rst:241 +msgid "The color options are currently limited to the mentioned options." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``jdoe@example.com, company@example.com``" +#: ../system/objects.rst:245 +msgid "" +"You can create a note for the priority to inform other admins about the " +"priority. This has no effect on tickets." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Text" +#: ../system/objects.rst:249 +msgid "Set the priority to *active* or *inactive*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.body}``" +#: ../system/objects/external-data-source-example.rst:2 +msgid "External Data Source" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Test`` without formatting (plain)" +#: ../system/objects/external-data-source-example.rst:4 +msgid "" +"We assume you already had a look on :doc:`types` where you can find a " +"description of the individual fields." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article Text as HTML (not referenced)" +#: ../system/objects/external-data-source-example.rst:7 +msgid "" +"To reproduce this example, choose a category you want to add a custom field, " +"click on *New Attribute* and select *External data source field* under " +"*Format*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.body_as_html}``" +#: ../system/objects/external-data-source-example.rst:11 +msgid "" +"Our example story is to fetch data from an external product database. We " +"want to add our products to the tickets so that the products can be searched " +"and chosen from a list and also create a link to the product website." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Test`` with formatting" +#: ../system/objects/external-data-source-example.rst:16 +msgid "Base configuration" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "Ticket > Article#" +#: ../system/objects/external-data-source-example.rst:None +msgid "Initial steps to configure external data source object type" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "``#{ticket.article_count}``" +#: ../system/objects/external-data-source-example.rst:25 +msgid "Name: *product*" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``1`` number of ticket articles" +#: ../system/objects/external-data-source-example.rst:26 +msgid "Display: *Product*" msgstr "" -#: ../system/variables/config.rst:2 -msgid "Config" +#: ../system/objects/external-data-source-example.rst:29 +msgid "External data source configuration" msgstr "" -#: ../system/variables/config.rst:6 +#: ../system/objects/external-data-source-example.rst:31 msgid "" -"Below you'll find config related variables. These hold useful configuration " -"information that you can use within e.g. triggers to show necessary " -"information to your customer." +"First, enter the search URL making sure it contains ``#{search.term}`` as a " +"parameter:" msgstr "" -#: ../system/variables/config.rst:11 -msgid "Config Variables" +#: ../system/objects/external-data-source-example.rst:34 +msgid "**Example:** ``https://dummyjson.com/products/search?q=#{search.term}``" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Fully Qualified Domain Name" +#: ../system/objects/external-data-source-example.rst:36 +msgid "" +"After that, head down to the preview section and enter a search input for " +"the external data source." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.fqdn}``" +#: ../system/objects/external-data-source-example.rst:39 +msgid "**Example:** ``mac``" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``zammad.example.com``" +#: ../system/objects/external-data-source-example.rst:41 +msgid "Then you can find a preview of the response data below:" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Ticket Hook" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of JSON response based on search term" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.ticket_hook}``" +#: ../system/objects/external-data-source-example.rst:48 +msgid "" +"We recommend using the preview to have a look on the structure. There is a " +"top-level element called ``products``. One level below, you can find the " +"attributes ``id`` and ``title``." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``Ticket#``" +#: ../system/objects/external-data-source-example.rst:52 +msgid "**Search result response based on search from example:**" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > HTTP type" +#: ../system/objects/external-data-source-example.rst:119 +msgid "" +"To tell the remote system that the desired data is located below the " +"``products`` level, you have to put it in the field *Search result list key*." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.http_type}``" +#: ../system/objects/external-data-source-example.rst:122 +msgid "" +"After inserting ``products`` in the mentioned field, you get an extended " +"preview. You can find an additional box *Search result list* with a JSON " +"structure. This is the same response as before but stripped from the upper " +"``products`` element by the external data source." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``https`` or ``http``" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of JSON response search result list" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > SystemID" +#: ../system/objects/external-data-source-example.rst:132 +msgid "" +"Now you need to provide the keys for the search result values and labels. As " +"already mentioned, we are looking for the ``id`` and the ``title`` of our " +"products. If you haven't already, it is now a good time to look at the " +"preview of the *Search result list*." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.system_id}``" +#: ../system/objects/external-data-source-example.rst:197 +msgid "" +"After locating our two keys, we insert them in *search result value key* " +"(``id``) and in *Search result label key* (``title``)." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``31`` (value between 1 and 99)" +#: ../system/objects/external-data-source-example.rst:200 +msgid "" +"Basically, we configured the external data source already and we can see a " +"table in the preview section:" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Organization" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of product table based on search term" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.organization}``" +#: ../system/objects/external-data-source-example.rst:208 +msgid "" +"According to our example story, now just the *Link template* is missing." msgstr "" -#: ../system/variables/config.rst:1 +#: ../system/objects/external-data-source-example.rst:210 msgid "" -"``Zammad GmbH`` value set in `Branding `_" +"Please note that this is an optional feature. If you don't want to use such " +"links, of course you don't have to configure it." msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Product Name" +#: ../system/objects/external-data-source-example.rst:213 +msgid "" +"We can add now an address where additional product information can be found." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.product_name}``" +#: ../system/objects/external-data-source-example.rst:215 +msgid "Example: ``https://your_domain.com/q=#{ticket.product}``" msgstr "" -#: ../system/variables/config.rst:1 -msgid "" -"``Helpdesk`` value set in `Branding `_" +#: ../system/objects/external-data-source-example.rst:217 +msgid "In the example, the parameter means:" msgstr "" -#: ../system/variables/current-user.rst:2 -msgid "Current User" +#: ../system/objects/external-data-source-example.rst:219 +msgid "``#{}``: \"Frame\" for the insertion of information" msgstr "" -#: ../system/variables/current-user.rst:6 -msgid "" -"Current user variables always return values of the current user that caused " -"e.g. a trigger to run." +#: ../system/objects/external-data-source-example.rst:220 +msgid "``ticket``: object level, where you create your custom object" msgstr "" -#: ../system/variables/current-user.rst:8 -msgid "" -"Due to the above fact, these variables are often not (yet) set or available " -"for usage." +#: ../system/objects/external-data-source-example.rst:221 +msgid "``product``: name of the (custom) object" msgstr "" -#: ../system/variables/current-user.rst:10 +#: ../system/objects/external-data-source-example.rst:223 msgid "" -"In situations where e.g. schedulers or triggers run, this most likely is " -"nothing you want to use." -msgstr "" - -#: ../system/variables/current-user.rst:13 -msgid "Current User Variables" +"After configuring your *Link template*, there will be another column in the " +"preview. Hovering on the icons in the *Link* column will show you where it " +"forwards you." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Web" +#: ../system/objects/external-data-source-example.rst:232 +msgid "" +"In our example, one of the links looks like: https://your_domain.com/q=6, " +"where the 6 is the product id." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.web}``" +#: ../system/objects/external-data-source-example.rst:235 +msgid "You can find more information regarding the URL in :doc:`types`." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``https://zammad.org`` or empty if not set" +#: ../system/objects/includes/adding-values-hint.include.rst:3 +msgid "" +"Adding values can be tricky for first timers, don't forget to press \"➕ " +"Add\" after typing your values. Otherwise you may loose a value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > VIP" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:1 +#: ../system/objects/includes/reposition-values.include.rst:1 +msgid "**↕️ This field type allows the positioning of its values ↔️**" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.vip}``" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:3 +msgid "" +"In order to re-arrange the field values, first edit the field. Then you can " +"use ☰ to drag the values in question to the correct position. If you want to " +"change the layer depth, double click on ☰. With it you can cycle through the " +"available layers." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``false`` or ``true``" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:8 +msgid "When you're ready, submit your changes to save the object attribute." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Web" +#: :0 ../system/objects/types.rst:0 +msgid "" +"Screencast showing how to re-position values on tree select like\n" +"fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.web}``" +#: ../system/objects/includes/reposition-values.include.rst:3 +msgid "" +"In order to re-arrange the field values, edit the field and scroll below the " +"values. Make sure to tick the option \"Use custom option sort\"." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > VIP" +#: ../system/objects/includes/reposition-values.include.rst:8 +msgid "" +"If you do not tick this field, all manual positioning you did above will be " +"lost upon saving! ☠️" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.vip}``" +#: ../system/objects/includes/reposition-values.include.rst:11 +msgid "" +"Now use ☰ to drag the values in question to the correct position. When " +"you're ready, submit your changes to save the object attribute." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Phone" +#: :0 ../system/objects/types.rst:0 +msgid "Screencast showing how to re-position values" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.phone}``" +#: ../system/objects/includes/url-template-hint.include.rst:3 +msgid "" +"This field allows using :ref:`URL fields (Link Templates) `." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``004930123456789`` or empty if not set" +#: ../system/objects/permissions.rst:2 +msgid "Attribute Permissions" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Note" +#: ../system/objects/permissions.rst:7 +msgid "" +"In the object attributes configuration you can define if a field is shown " +"and if the input in the field is mandatory, separated by different screens " +"and for different :doc:`roles/permissions `." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.note}``" +#: ../system/objects/permissions.rst:17 +msgid "Screenshot shows object attribute permission table" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Some note to this user`` or empty if not set" +#: ../system/objects/permissions.rst:17 +msgid "" +"Some of the possible permissions and screen options for a user object " +"attribute." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Mobile" +#: ../system/objects/permissions.rst:19 +msgid "" +"Based on the object context (ticket, agent, organization, user), the " +"selectable roles (to be precise: the required permissions) and screens " +"differ. Be aware that these settings aren't affecting data creation via " +"other channels than the UI." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.mobile}``" +#: ../system/objects/permissions.rst:24 +msgid "" +"If you want to have further customization possibilities, you should have a " +"look at the :doc:`core workflows `." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``0049176123456789`` or empty if not set" +#: ../system/objects/permissions.rst:28 +msgid "Screens" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Login" +#: ../system/objects/permissions.rst:30 +msgid "" +"In the table below you can find an overview about the different permissions " +"and the available screens Zammad distinguishes between." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.login}``" +#: ../system/objects/permissions.rst:37 +msgid "Screen" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Lastname" +#: ../system/objects/permissions.rst:38 +msgid "Available for" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.lastname}``" +#: ../system/objects/permissions.rst:40 +msgid "create" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Firstname" +#: ../system/objects/permissions.rst:41 ../system/objects/permissions.rst:52 +#: ../system/objects/permissions.rst:59 ../system/objects/permissions.rst:73 +msgid "admin.user" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.firstname}``" +#: ../system/objects/permissions.rst:42 ../system/objects/permissions.rst:53 +#: ../system/objects/permissions.rst:60 +msgid "admin.organization" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``John`` or empty if not set" +#: ../system/objects/permissions.rst:43 ../system/objects/permissions.rst:54 +#: ../system/objects/permissions.rst:61 +msgid "admin.group" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Fax" +#: ../system/objects/permissions.rst:44 +msgid "Creation dialog for not yet existing data" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.fax}``" +#: ../system/objects/permissions.rst:45 +msgid "create_middle" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``004930123464789`` or empty if not set" +#: ../system/objects/permissions.rst:46 ../system/objects/permissions.rst:50 +#: ../system/objects/permissions.rst:57 ../system/objects/permissions.rst:66 +#: ../system/objects/permissions.rst:70 +msgid "ticket.customer" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Email" +#: ../system/objects/permissions.rst:47 ../system/objects/permissions.rst:51 +#: ../system/objects/permissions.rst:58 ../system/objects/permissions.rst:69 +msgid "ticket.agent" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.email}``" +#: ../system/objects/permissions.rst:48 +msgid "Ticket create dialog (middle section)" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``jdoe@customer.tld``" +#: ../system/objects/permissions.rst:49 +msgid "edit" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Department" +#: ../system/objects/permissions.rst:55 +msgid "Editing dialog for already existing data" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.department}``" +#: ../system/objects/permissions.rst:56 +msgid "view" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Sales`` or empty if not set" +#: ../system/objects/permissions.rst:62 +msgid "View-only dialog for already existing data" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Avatar" +#: ../system/objects/permissions.rst:64 +msgid "(e.g. user or organization from search)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.avatar(60,60)}``" +#: ../system/objects/permissions.rst:65 +msgid "signup" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "avatar picture with width and height in pixel (e.g. 60,60)" +#: ../system/objects/permissions.rst:67 +msgid "Sign-up screen for new customers" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Address" +#: ../system/objects/permissions.rst:68 +msgid "invite_customer" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.address}``" +#: ../system/objects/permissions.rst:71 +msgid "" +"Customer invitation screen (from :doc:`First Steps ` area)" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Some street 1, 12345 Berlin`` or empty if not set" +#: ../system/objects/permissions.rst:72 +msgid "invite_agent" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated at" +#: ../system/objects/permissions.rst:74 +msgid "" +"Agent invitation screen (from :doc:`First Steps ` area)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_at}``" +#: ../system/objects/permissions.rst:78 +msgid "Screen Options" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC``" +#: ../system/objects/permissions.rst:80 +msgid "" +"For the different screens you can select \"show\" and \"required\" options." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Phone" +#: ../system/objects/permissions.rst:82 +msgid "**shown:** Show (check) or hide (uncheck) a field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.phone}``" +#: ../system/objects/permissions.rst:83 +msgid "" +"**required:** Set a field to mandatory (check). Forces users (via UI and " +"API) to populate the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Shared organization" +#: ../system/objects/types.rst:7 +msgid "Example external data source" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.shared}``" +#: ../system/objects/types.rst:2 +msgid "Attribute types" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Note" +#: ../system/objects/types.rst:4 +msgid "" +"When adding a new object attribute, you can choose between the following " +"attribute types." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.note}``" +#: ../system/objects/types.rst:14 +msgid "" +"You cannot change the attribute format / type as soon as it is applied. If " +"you no longer need an object attribute, consider disabling it instead of " +"removing." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``A note to the organization of the user`` or empty if not set" +#: ../system/objects/types.rst:18 +msgid "**What about the translation of my attributes?**" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Name" +#: ../system/objects/types.rst:20 +msgid "" +"For some attribute types you can decide if they should be translatable or " +"not. To be precise, it works only for the selectable fields because the " +"possible choices are known and limited. For the following attribute types, " +"you can set the translatable flag:" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.name}``" +#: ../system/objects/types.rst:25 +msgid "*Boolean field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``Zammad GmbH``" +#: ../system/objects/types.rst:26 +msgid "*Single selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Domain based assignment" +#: ../system/objects/types.rst:27 +msgid "*Multiple selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.domain_assignment}``" +#: ../system/objects/types.rst:28 +msgid "*Single tree selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Domain" +#: ../system/objects/types.rst:29 +msgid "*Multiple tree selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.domain}``" +#: ../system/objects/types.rst:31 +msgid "" +"For these types, you can find an additional field *Translate field contents*:" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``zammad.com`` or empty if not set" +#: ../system/objects/types.rst:0 +msgid "Screenshot showing translatable attribute types" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > VIP" +#: ../system/objects/types.rst:38 +msgid "Screenshot with example of translatable attribute type" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.vip}``" +#: ../system/objects/types.rst:45 +msgid "Boolean field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Note" +#: ../system/objects/types.rst:41 +msgid "" +"Provides a drop-down field with display values for ``true`` and ``false``. " +"Setting a default is mandatory." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.note}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Boolean fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Mobile" +#: ../system/objects/types.rst:55 +msgid "Date field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.mobile}``" +#: ../system/objects/types.rst:48 +msgid "Provides a date picker field and does not allow default values." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Login" +#: ../system/objects/types.rst:52 +msgid "Default time diff (hours)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.login}``" +#: ../system/objects/types.rst:51 +msgid "" +"This setting helps the user by highlighting the day from now plus the " +"provided value. It *does not* pre-fill the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Lastname" +#: ../system/objects/types.rst:0 +msgid "Available settings for Date fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.lastname}``" +#: ../system/objects/types.rst:73 +msgid "Date & time field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Firstname" +#: ../system/objects/types.rst:58 +msgid "Provides a date and time picker – does not allow default values" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.firstname}``" +#: ../system/objects/types.rst:62 +msgid "Allow future" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Fax" +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the future." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.fax}``" +#: ../system/objects/types.rst:66 +msgid "Allow past" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Email" +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the past." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.email}``" +#: ../system/objects/types.rst:70 +msgid "Default time diff (minutes)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Department" +#: ../system/objects/types.rst:69 +msgid "" +"This setting helps the user by highlighting the day from now plus the " +"provided value. It does not pre-fill the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.department}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Date & time fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Web" +#: ../system/objects/types.rst:86 +msgid "Integer field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.web}``" +#: ../system/objects/types.rst:76 +msgid "" +"Provides an input field that allows integer usage only. You may define a " +"default value. You cannot enforce comma separation." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > VIP" +#: ../system/objects/types.rst:80 +msgid "Minimal" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.vip}``" +#: ../system/objects/types.rst:80 +msgid "The minimal value the field accepts." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Phone" +#: ../system/objects/types.rst:83 +msgid "Maximal" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.phone}``" +#: ../system/objects/types.rst:83 +msgid "The maximum value the field accepts." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Note" +#: ../system/objects/types.rst:0 +msgid "Available settings for Integer fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.note}``" +#: ../system/objects/types.rst:99 +msgid "Multiple selection field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Mobile" +#: ../system/objects/types.rst:89 +msgid "" +"Provides a selection field that allows the selection of one or more out of " +"several. This field does allow setting a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.mobile}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Multiple selection fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Login" +#: ../system/objects/types.rst:112 +msgid "Single selection field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.login}``" +#: ../system/objects/types.rst:102 +msgid "" +"Provides a drop-down field that allows selection of one value out of " +"several. This field does allow setting a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Lastname" +#: ../system/objects/types.rst:0 +msgid "Available settings for Single selection fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.lastname}``" +#: ../system/objects/types.rst:142 +msgid "Textarea field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Firstname" +#: ../system/objects/types.rst:115 +msgid "" +"Provides a text area input field (multiple lines) and thus allows e.g. new " +"lines. You can set a default field value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.firstname}``" +#: ../system/objects/types.rst:120 +msgid "" +"Please note that this field *does not* support text formatting or HTML " +"content (rich text)." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Fax" +#: ../system/objects/types.rst:123 +msgid "**🥵 This field can consume a lot of visual space**" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.fax}``" +#: ../system/objects/types.rst:125 +msgid "" +"Depending on where you use this field type, it may use a lot of visual space " +"if you provide a lot of text. This may be an issue to work with." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Email" +#: ../system/objects/types.rst:130 +msgid "Default" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.email}``" +#: ../system/objects/types.rst:129 +msgid "" +"The here provided text will be shown within the text area field or new data " +"sets." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Department" +#: ../system/objects/types.rst:134 ../system/objects/types.rst:160 +msgid "Maxlength" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.department}``" +#: ../system/objects/types.rst:0 ../system/objects/types.rst:160 +msgid "You can pick the maximum length of the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Avatar" +#: ../system/objects/types.rst:0 +msgid "The default length of this object is ``500``." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.avatar(60,60)}``" +#: ../system/objects/types.rst:139 +msgid "Rows" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Address" +#: ../system/objects/types.rst:0 +msgid "" +"Change the number of rows to dislay so that you can use only the space you " +"really need." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.address}``" +#: ../system/objects/types.rst:0 +msgid "The default number of rows is ``4``." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created at" +#: ../system/objects/types.rst:0 +msgid "Available settings for Textarea fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_at}``" +#: ../system/objects/types.rst:165 +msgid "Text field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Avatar" +#: ../system/objects/types.rst:145 +msgid "Provides a text field (one line) and allows choosing a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.avatar(60,60)}``" +#: ../system/objects/types.rst:148 +msgid "" +"Defines the type of the input field. This allows e.g. your browser to ensure " +"that you provide the specific type." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Address" +#: ../system/objects/types.rst:152 +msgid "Currently available:" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.address}``" +#: ../system/objects/types.rst:155 +msgid "Phone" msgstr "" -#: ../system/variables/ticket.rst:6 -msgid "" -"Below you can find all available ticket-based variables within Zammad. These " -"can be called via Triggers for example. If you're unsure if Zammad does " -"support variables at the point you're at, you can try to type ``::`` to " -"check." +#: ../system/objects/types.rst:156 +msgid "Text" msgstr "" -#: ../system/variables/ticket.rst:12 -msgid "Ticket Variables" +#: ../system/objects/types.rst:157 +msgid "Url *(URL fields disable link-template availability)*" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Web" +#: ../system/objects/types.rst:0 +msgid "Available settings for Text fields" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.web}``" +#: ../system/objects/types.rst:174 +msgid "Single tree selection field" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > VIP" +#: ../system/objects/types.rst:168 +msgid "" +"Provides a select-like field with up to 6 layers of options. Does not allow " +"setting a default value." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.vip}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Tree Select fields" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Phone" +#: ../system/objects/types.rst:183 +msgid "Multiple tree selection field" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.phone}``" +#: ../system/objects/types.rst:177 +msgid "" +"Provides a select-like field with up to 6 layers of options allowing the " +"selection of multiple values. Does not allow setting a default value." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Note" +#: ../system/objects/types.rst:302 +msgid "External Data Source field" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.note}``" +#: ../system/objects/types.rst:186 +msgid "" +"Provides a searchable field which fetches data from an external system. This " +"can be useful if you have data outside of Zammad and don't want to maintain " +"both data sources." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Mobile" +#: ../system/objects/types.rst:190 +msgid "The feature works as follows:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.mobile}``" +#: ../system/objects/types.rst:192 +msgid "" +"Zammad sends a query with a search string (free text from agent or based on " +"a variable) in a pre-defined format (\"Search URL\") to an external system." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Login" +#: ../system/objects/types.rst:195 +msgid "" +"This external system searches for matches and provides a response as a JSON " +"structure to Zammad." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.login}``" +#: ../system/objects/types.rst:197 +msgid "" +"Zammad just looks for the defined list and value keys, reads the content and " +"displays the value to the user. There is no search on Zammad side." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Lastname" +#: ../system/objects/types.rst:201 +msgid "" +"The usage of a PostgreSQL database for Zammad is required. In any other " +"case, Zammad will hide the external data source type and you are not able to " +"use it. If you want to use this feature, consider to :docs:`migrate your " +"database `." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.lastname}``" +#: ../system/objects/types.rst:205 +msgid "Currently, only ``GET`` is supported as request method." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Firstname" +#: ../system/objects/types.rst:206 +msgid "" +"The data structure must be in JSON format and provide the objects in an " +"array." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.firstname}``" +#: ../system/objects/types.rst:208 +msgid "" +"The endpoint for the external data source has to support search. On Zammad " +"side, there is no search/logic implemented; however, you can define the " +"output key and value based on the result(s) from the response (which " +"provides already filtered content based on the search)." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Fax" +#: ../system/objects/types.rst:212 +msgid "" +"If you receive more results as expected, your external data source search " +"may not work properly or the structure of the URL is not correct. You should " +"get in touch with a responsible person from the external system." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.fax}``" +#: ../system/objects/types.rst:217 +msgid "" +"Please have a look :doc:`at our example `, where you can find a possible configuration for a public " +"dummy endpoint." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Email" +#: ../system/objects/types.rst:0 +msgid "Available settings for external data source fields" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.email}``" +#: ../system/objects/types.rst:242 +msgid "Search URL" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Department" +#: ../system/objects/types.rst:227 +msgid "" +"Set your endpoint where Zammad fetches the data. Please make sure to include " +"a valid search :doc:`variable ` as an URL parameter. " +"Example for a free text search at user input: ``#{search.term}``" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.department}``" +#: ../system/objects/types.rst:232 +msgid "" +"If in doubt, ask the responsible person for the external data source how " +"they expect the structure of the URL." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Avatar" +#: ../system/objects/types.rst:236 +msgid "" +"Depending on your search variable, the preview might work or not. The reason " +"is that the context might not be available and it is no bug." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.avatar(60,60)}``" +#: ../system/objects/types.rst:239 +msgid "" +"Please also make sure to use a variable which is available in your object " +"context. For example you won't be able to search for a ticket in a user " +"object context." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Address" +#: ../system/objects/types.rst:252 +msgid "SSL Verification" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.address}``" +#: ../system/objects/types.rst:245 +msgid "Here you can switch the SSL verification to no." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated at" +#: ../system/objects/types.rst:249 +msgid "" +"If your external data source system is using self signed certificates, " +"please have a look :doc:`here ` for " +"further information about how to handle them in Zammad, so you can keep the " +"SSL verification activated." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_at}``" +#: ../system/objects/types.rst:258 +msgid "HTTP Authentication" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Title" +#: ../system/objects/types.rst:255 +msgid "" +"If your external data source requires an authentication, you can set it " +"here. You can leave it empty or choose between *Basic Authentication* or " +"*Authentication Token* (selecting one of the two methods leads to additional " +"fields where you can enter your credentials/token)." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.title}``" +#: ../system/objects/types.rst:265 +msgid "Search result list key" msgstr "" -#: ../system/variables/ticket.rst:1 +#: ../system/objects/types.rst:261 msgid "" -"``My amazing Subject`` (normally subject, can be edited within Interface and " -"thus differ)" +"Defines the level in the JSON structure which provides the list with search " +"results. You can leave it empty, if the data is already provided as an " +"array. If you have to go deeper in the structure, you can provide a path " +"with ``.`` as separators, e.g. ``key.subkey.sub-sub-key``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Accounted Time" +#: ../system/objects/types.rst:271 +msgid "Search result value key" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.time_unit}``" +#: ../system/objects/types.rst:268 +msgid "" +"Defines the attribute in the structure in which your external data source " +"provides the *value* for your data. An example would be a product *number*. " +"If you have to go deeper in the structure, you can provide a path with ``.`` " +"as separators, e.g. ``key.subkey.sub-sub-key``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``1``, ``2.75`` or empty response" +#: ../system/objects/types.rst:277 +msgid "Search result label key" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Tags" +#: ../system/objects/types.rst:274 +msgid "" +"Defines the attribute in the structure in which your external data source " +"provides the *label* for your data. An example would be a product *name*. If " +"you have to go deeper in the structure, you can provide a path with ``.`` as " +"separators, e.g. ``key.subkey.sub-sub-key``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.tags}``" +#: ../system/objects/types.rst:280 +msgid "" +"In the preview area, you can find the following items (depending on your " +"configuration above):" msgstr "" -#: ../system/variables/ticket.rst:1 +#: ../system/objects/types.rst:283 msgid "" -"Currently not available, see `Issue 2769 `_" +"**Error/hint message** (only if configuration is not complete): Zammad tells " +"you, if there is a problem and what you should change in your configuration." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > State > Name" +#: ../system/objects/types.rst:286 +msgid "" +"**Search field**: search for an existing attribute in the data source to get " +"a preview. This is required for the fields below to show up." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.state.name}``" +#: ../system/objects/types.rst:288 +msgid "" +"**Search result response** (only if configuration is not complete): here you " +"can find a syntax highlighted JSON preview of the response, based on the " +"search term you entered." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``new``, ``open``, ..." +#: ../system/objects/types.rst:291 +msgid "" +"**Search result list** (only if *search result list key* is properly set): " +"output of the structure under the configured *search result list key*." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Priority > Name" +#: ../system/objects/types.rst:294 +msgid "" +"**Preview table** (when fully configured): Zammad shows you a table which " +"includes the found items based on the search string (value, label and " +"optional link). You can use this preview if you don't have the complete data " +"structure of the external system in mind." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.priority.name}``" +#: ../system/objects/types.rst:299 +msgid "" +"An example of a configured external data source field from agent perspective:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2 normal``" +#: ../system/objects/types.rst:0 +msgid "Screencast showing the search for a product in a ticket" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Pending till" +#: ../system/objects/types.rst:307 +msgid "URL fields (Link-Template)" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.pending_time}``" +#: ../system/objects/types.rst:311 +msgid "" +"This function is restricted to Text, Select and External data source types " +"only." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not set" +#: ../system/objects/types.rst:314 +msgid "" +"Link-Templates are an amazing way to dynamically generate URLs. They allow " +"you to integrate other systems better without having to manually copy data " +"from Zammad if possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Web" +#: ../system/objects/types.rst:320 +msgid "" +"Another great way of communicating with another system may be Zammad's :doc:" +"`Webhooks `." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.web}``" +#: ../system/objects/types.rst:323 +msgid "" +"After filling a link-template enabled field, an URL icon will appear on its " +"right. Clicking on the icon opens a new tab." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``https://zammad.com`` or empty if not set" +#: ../system/objects/types.rst:328 +msgid "" +"Even though Zammad displays the link template within object edit and create " +"screens, the function is optional. It's only active if you populate the " +"field." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > VIP" +#: ../system/objects/types.rst:333 +msgid "" +"What's the difference between URL and text fields with link template...?!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.vip}``" +#: ../system/objects/types.rst:335 +msgid "" +"Both fields have different use cases. Use ``text`` type text fields when " +"ever you have a *static* url that requires dynamic parameters. If you " +"require a drag & drop like field that you can put in any URL, use ``URL`` " +"type text fields." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Phone" +#: ../system/objects/types.rst:340 +msgid "" +"The difference is easier to spot when comparing the fields directly, below " +"screencast shows the result - the dynamic approach uses existing values in " +"the moment of updating to built the URL - e.g. ``https://google.com/search?" +"q=cookies`` - while the URL approach uses the actual URL of the field - e.g. " +"``https://zammad.com``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.phone}``" +#: ../system/objects/types.rst:None +msgid "" +"Screencast showing the differents in between URL and text type fields with " +"actual values" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Note" +#: ../system/objects/types.rst:352 +msgid "How does this work...?!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.note}``" +#: ../system/objects/types.rst:354 +msgid "" +"As an example, let's say you have an attribute called ``amazing_attribute`` " +"and you want to open a google search directly with the input from that field." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Mobile" +#: ../system/objects/types.rst:357 +msgid "" +"Providing the link-template field below allows you to do so: ``https://www." +"google.com/search?q=#{ticket.amazing_attribute}``" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.mobile}``" +#: ../system/objects/types.rst:362 +msgid "" +"You can use any :doc:`Zammad variable ` as long as it's " +"available in the moment you need it." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Login" +#: ../system/objects/types.rst:365 +msgid "" +"As a result, you are redirected to Google with a search for the value of the " +"attribute, if you click on the button in the ticket (as you can see in the " +"screencast above)." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.login}``" +#: ../system/packages.rst:2 +msgid "Packages" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``agent``" +#: ../system/packages.rst:4 +msgid "That's the package management-area." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Lastname" +#: ../system/packages.rst:6 +msgid "Individual add-ons for Zammad can be installed and managed here." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.lastname}``" +#: ../system/sessions.rst:2 +msgid "Sessions" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Mustermann`` or empty if not set" +#: ../system/sessions.rst:4 +msgid "" +"Sessions management allows reviewing currently known user sessions and " +"allows to end these. The session timeout is affected by :ref:" +"`security_session_timeout` configurations from security settings." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Firstname" +#: ../system/sessions.rst:None +msgid "Screenshot showing Zammad's session management" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.firstname}``" +#: ../system/sessions.rst:13 +msgid "Zammad will provide the following information:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Max`` or empty if not set" +#: ../system/sessions.rst:16 +msgid "" +"The user account this session entry belongs to. It can be normal if a user " +"has several sessions in the list. This can be due to changed browser " +"information or if you use e.g. single sign on methods where the user does " +"not use the log off button." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Fax" +#: ../system/sessions.rst:22 +msgid "Browser" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.fax}``" +#: ../system/sessions.rst:22 +msgid "The browser agent communicated to Zammad." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Email" +#: ../system/sessions.rst:40 +msgid "Location" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.email}``" +#: ../system/sessions.rst:25 +msgid "" +"The anticipated location based on the users IP address. Depending on the IP " +"address the result shown may differ. This option depends on :doc:`/settings/" +"system/services`." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``agent@company.tld`` or empty if not set" +#: ../system/sessions.rst:29 +msgid "The following information can be shown:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Department" +#: ../system/sessions.rst:33 +msgid "IP address" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.department}``" +#: ../system/sessions.rst:32 +msgid "" +"Either if you set *Geo IP services* to inactive or you're using internal IP " +"address which do not provide location information." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Support`` or empty if not set" +#: ../system/sessions.rst:40 +msgid "Country (or Country + City)" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Avatar" +#: ../system/sessions.rst:36 +msgid "" +"If *Geo IP services* is enabled only. Depends on how detailed the available " +"IP address information are." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.avatar(60,60)}``" +#: ../system/sessions.rst:39 +msgid "" +"Be aware that results can be inaccurate - this technically is not an error." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Address" +#: ../system/sessions.rst:43 +msgid "Age" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.address}``" +#: ../system/sessions.rst:43 +msgid "Provides the time when the session initially has been created." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Shared organization" +#: ../system/sessions.rst:50 +msgid "Update" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.shared}``" +#: ../system/sessions.rst:46 +msgid "" +"Provides the time the user used this session to open Zammad. This timestamp " +"is only updated if the user e.g. reloads, not during normal work on tickets." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Note" +#: ../system/sessions.rst:50 +msgid "This timestamp is being used for the session timeout." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.note}``" +#: ../system/sessions.rst:53 +msgid "" +"Use the delete button to remove a single session on behalf of your user." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Name" +#: ../system/subscription.rst:2 +msgid "Subscription (SaaS)" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.name}``" +#: ../system/subscription.rst:4 +msgid "" +"The subscription settings page allows you to configure your instances " +"package and number of agents required." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Zammad GmbH`` or empty if not set" +#: ../system/subscription.rst:9 +msgid "" +"This setting section is only available for Hosted setups. If you're looking " +"for on premise support contracts, please see the `Zammad pricing page " +"`_." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Domain based assignment" +#: ../system/subscription.rst:14 ../system/subscription.rst:34 +msgid "Plan" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.domain_assignment}``" +#: ../system/subscription.rst:16 +msgid "" +"Here you can set up everything affecting your instance subscription " +"functions like number of agents and package." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Domain" +#: ../system/subscription.rst:19 +msgid "" +"On top of the page you can find a subscription summary. You'll find the " +"number of used and available (booked) agent seats there. By using the *see " +"more* link you can also expand an agent list to see the currently configured " +"active agents. This list *does not* count accounts with admin permissions " +"only." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.domain}``" +#: ../system/subscription.rst:None +msgid "" +"Within subscription you can always see how many agents are still\n" +"available to add and who uses the seats." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``domain.tld`` or empty if not set" +#: ../system/subscription.rst:29 +msgid "" +"Learn more on how to manage your agents in general :doc:`here `." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > VIP" +#: ../system/subscription.rst:36 +msgid "" +"This section gives you an overview of the available plans and their " +"functions / limits. If you require a more detailed table, check our " +"`detailed pricing table `_ for more." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.vip}``" +#: ../system/subscription.rst:40 +msgid "" +"Your selection in this step will decide on the base agent price and e.g. " +"agent limits that might apply in the summary step." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Number" +#: ../system/subscription.rst:43 +msgid "" +"The green *Selected* button will also tell you what plan you're currently in." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.number}``" +#: ../system/subscription.rst:47 +msgid "" +"Trial instances are running at Professional with 3 agents. The plan cannot " +"be changed during the trial for technical reasons, if you require more " +"agents for testing, please contact `our sales team `_ with a reason for the raise request." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``31001``, ``201910731001``, ..." +#: ../system/subscription.rst:None +msgid "" +"Screenshot showing three available packages for a hosted Zammad\n" +"instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > ID" +#: ../system/subscription.rst:57 +msgid "" +"At the bottom of this block you can find a summary where you can adjust the " +"settings of the previous selected plan." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.id}``" +#: ../system/subscription.rst:62 +msgid "" +"Note that upgrading (more agents, higher package) is always possible, " +"however, downgrading will only happen when your billing period renews." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``17``, ``5281``, ..." +#: ../system/subscription.rst:66 +msgid "" +"Upgrading resets your billing period and existing credit will be deducted " +"from the new total." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact (customer)" +#: ../system/subscription.rst:75 +msgid "Billing cycle" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_customer_at}``" +#: ../system/subscription.rst:70 +msgid "" +"You can choose between either monthly or yearly billing. The price per agent " +"will be cheaper if you decide for yearly billing." msgstr "" -#: ../system/variables/ticket.rst:1 +#: ../system/subscription.rst:73 msgid "" -"``2019-10-07 16:25:00 UTC`` or empty if not applicable yet (Please note " -"`Ticket last contact behavior Settings `_ for this)" +"If you're still trying out things and are unsure of the right package for " +"your instance, you may want to choose monthly first and then upgrade to " +"yearly when you're sure." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact" +#: ../system/subscription.rst:83 +msgid "Plan: (Starter|Professional|Plus) - Agents" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_at}``" +#: ../system/subscription.rst:78 +msgid "Choose the number of agents you require for your instance." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact (agent)" +#: ../system/subscription.rst:80 +msgid "" +"Keep in mind that some packages may have agent limits. Depending on the " +"previous chosen package, you won't be able to exceed specific agent numbers. " +"Also note that setting less agents than currently configured is not possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_agent_at}``" +#: ../system/subscription.rst:86 +msgid "Total" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable yet" +#: ../system/subscription.rst:86 +msgid "This will be the net total you're going to be billed." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Note" +#: ../system/subscription.rst:88 +msgid "" +"By using the *Update subscription* button, the instance package will be " +"adjusted immediately. If you didn't provide a payment method yet, Zammad " +"will request you to provide one at this point." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.note}``" +#: ../system/subscription.rst:94 +msgid "" +"In case you're still within the trial period, this means that the trial will " +"be over immediately!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Note about this group``" +#: ../system/subscription.rst:97 +msgid "Down- or upgrading during the trial period *is not* possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Name" +#: ../system/subscription.rst:None +msgid "Screenshot showing payment options and a pricing summary" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.name}``" +#: ../system/subscription.rst:103 +msgid "Billing Information" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Sales``" +#: ../system/subscription.rst:105 +msgid "" +"You can control all billing relevant information like invoices, billing " +"address and the option to cancel your subscription." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Follow-up possible" +#: ../system/subscription.rst:108 +msgid "" +"All adjusted billing information below only affect future invoices. If your " +"invoice was issued wrong, please contact `our sales team `_." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.follow_up_possible}``" +#: ../system/subscription.rst:114 +msgid "Billing address" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``no`` or ``yes``" +#: ../system/subscription.rst:113 +msgid "" +"Provide your company address here, make sure to include the companies name " +"in case required. This address will be referenced on your invoice." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Assign Follow-Ups" +#: ../system/subscription.rst:118 +msgid "VAT ID" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.follow_up_assignment}``" +#: ../system/subscription.rst:117 +msgid "" +"Provide your VAT ID here. If applicable your invoice will not contain German " +"VAT. Please make sure to pay the VAT in your country as required." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Assignment Timeout" +#: ../system/subscription.rst:127 +msgid "Billing Email Address" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.assignment_timeout}``" +#: ../system/subscription.rst:121 +msgid "" +"Usually the instance owner (the person that registered the instance) will " +"receive all emails including the invoices. In case you have your own billing " +"department, you can provide their email address here." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``20`` or empty if not configured" +#: ../system/subscription.rst:125 +msgid "" +"All billing relevant information will then be sent to this email address." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > First response" +#: ../system/subscription.rst:127 +msgid "Invoices are sent as attachment (PDF) to this email address." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.first_response_at}``" +#: ../system/subscription.rst:129 +msgid "" +"Don't forget to press the *Update billing information* button after you " +"changed above settings." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Escalation at" +#: ../system/subscription.rst:None +msgid "" +"Screenshot showing options for billing information within the\n" +"subscription menu" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.escalation_at}``" +#: ../system/subscription.rst:137 +msgid "Payment Method" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable" +#: ../system/subscription.rst:139 +msgid "You can pay via credit card or SEPA mandate." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Web" +#: ../system/subscription.rst:144 +msgid "Credit card" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.web}``" +#: ../system/subscription.rst:142 +msgid "" +"Simply follow the dialogue by clicking *authorize credit card* and confirm -" +"if required by your bank- your consent to Zammad using your card for the " +"payments." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > VIP" +#: ../system/subscription.rst:148 +msgid "SEPA Direct Debit" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.vip}``" +#: ../system/subscription.rst:147 +msgid "" +"Provide the requested information of the bank account holder and update if " +"you're ready. You'll then receive an email with the SEPA mandate." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Phone" +#: ../system/subscription.rst:150 +msgid "" +"Technically there's also the possibility to pay via invoice, however - this " +"method only applies to a fairly low number of instances. Please contact `our " +"sales team `_ for more information." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.phone}``" -msgstr "" +#: ../system/subscription.rst:156 +#, fuzzy +#| msgid "Description" +msgid "Cancel Subscription" +msgstr "Förklaring" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Note" +#: ../system/subscription.rst:158 +msgid "" +"Do you want to cancel your subscription? In case you no longer want to use " +"Zammad's SaaS, you can cancel your subscription by using the red *Yes, " +"please cancel my subscription* button." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.note}``" +#: ../system/subscription.rst:162 +msgid "" +"To cancel the description, enter the FQDN of your Zammad instance and " +"provide a reason for your cancellation." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Mobile" +#: ../system/subscription.rst:165 +msgid "" +"Your subscription will end the day after your trial or billing period ends." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.mobile}``" +#: ../system/subscription.rst:None +msgid "Screenshot showing subscription cancellation dialog" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Login" +#: ../system/subscription.rst:174 +msgid "" +"We will remind you about your cancelled subscription several times up front. " +"After the subscription ended all instance data will be removed. A restore " +"*is not* possible after that point!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.login}``" +#: ../system/subscription.rst:178 +msgid "**😖 Cancelled by accident?**" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Lastname" +#: ../system/subscription.rst:180 +msgid "" +"You can always undo the cancellation via the *Yes, undo the cancellation of " +"my subscription* button up to the last subscription day!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.lastname}``" +#: ../system/subscription.rst:0 +msgid "" +"Screenshot showing a red button to cancel the subscription\n" +"cancellation" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Firstname" +#: ../system/subscription.rst:189 +msgid "Payment History" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.firstname}``" +#: ../system/subscription.rst:191 +msgid "" +"The payment history will display a history of all paid invoices. At this " +"point you can also download these in case you need them again." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Fax" +#: ../system/subscription.rst:196 +msgid "" +"You will only find *paid* invoices here. Invoices that are to be billed are " +"not available before the payment is completed." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.fax}``" +#: ../system/subscription.rst:201 +msgid "Date" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Email" +#: ../system/subscription.rst:201 +msgid "Date of the invoice creation." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.email}``" +#: ../system/subscription.rst:204 +msgid "Amount" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Department" +#: ../system/subscription.rst:204 +msgid "Invoice total including VAT if applicable." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.department}``" +#: ../system/subscription.rst:207 +msgid "" +"Contains contract period (monthly or yearly) and hosted plan for the " +"subscription period in question." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Avatar" +#: ../system/subscription.rst:218 +msgid "Payment method / Service period" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.avatar(60,60)}``" +#: ../system/subscription.rst:211 +msgid "" +"Used bank account or credit card as well as the subscription period the " +"invoice is about." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Address" +#: ../system/subscription.rst:216 +msgid "" +"It might happen that the invoice date and subscription period differ. This " +"is nothing to worry about, the subscription periods will be accounted later " +"on." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.address}``" +#: ../system/subscription.rst:222 +msgid "Receipt" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Web" +#: ../system/subscription.rst:221 +msgid "" +"Use the arrow to download the invoice in question. You can download all " +"available invoices any time you need to here!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.web}``" +#: ../system/subscription.rst:None +msgid "Screenshot showing payment history of a hosted instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > VIP" +#: ../system/subscription.rst:229 +msgid "FAQ" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.vip}``" +#: ../system/subscription.rst:233 +msgid "I set up a trial account but am missing functions to test" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Phone" +#: ../system/subscription.rst:232 +msgid "" +"The trial instance is running within the professional package allowing up to " +"three agents." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.phone}``" +#: ../system/subscription.rst:236 +msgid "Can I change package within the trial?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Note" +#: ../system/subscription.rst:236 +msgid "No. As soon as the package is changed the subscription begins." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.note}``" +#: ../system/subscription.rst:241 +msgid "What happens to my trial instance after the trial period ended?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Mobile" +#: ../system/subscription.rst:239 +msgid "" +"Your instance will automatically be canceled for you. Please see *What " +"happens to my instance after it has been canceled?* for more." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.mobile}``" +#: ../system/subscription.rst:254 +msgid "What happens to my instance after it has been canceled?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Login" +#: ../system/subscription.rst:244 +msgid "That depends slightly on your instance state:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.login}``" +#: ../system/subscription.rst:250 +msgid "Trial instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Lastname" +#: ../system/subscription.rst:247 +msgid "" +"If you're still on trial, we will ice your instance and remind you once " +"again about your instance. We then will wait some days and remove your " +"instance from our system. This is the last time we will inform you by Email." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.lastname}``" +#: ../system/subscription.rst:254 +msgid "Paid instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Firstname" +#: ../system/subscription.rst:253 +msgid "" +"If you're a paying customer and canceled your subscription, the instance " +"removal will take place the day after your last subscription day." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.firstname}``" +#: ../system/subscription.rst:256 +msgid "Can removed instances be restored?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Fax" +#: ../system/subscription.rst:257 +msgid "No. Once your instance has been removed, a restoration is not possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.fax}``" +#: ../system/system-report.rst:2 +msgid "System Report" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Email" +#: ../system/system-report.rst:4 +msgid "" +"In this place you can't configure Zammad. Instead you can obtain a system " +"report about Zammad and its configuration." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.email}``" +#: ../system/system-report.rst:7 +msgid "" +"See the description in Zammad for an explanation. You can even find a " +"preview of the included data below the **Download** button." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Department" +#: ../system/system-report.rst:10 +msgid "" +"Zammad never sends this automatically to anyone. It is a manual process only " +"to provide better support based on your configuration." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.department}``" -msgstr "" +#: ../system/translations.rst:2 +msgid "Translations" +msgstr "Översättningar" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Avatar" +#: ../system/translations.rst:4 +msgid "" +"Translations of Zammad are processed centrally in our `Weblate instance " +"`_. This allows non-developers to review " +"and update translation texts of the language they actually speak." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.avatar(60,60)}``" +#: ../system/translations.rst:9 +msgid "" +"Your language is in an incomplete translation state or has typos? Please " +"consider helping us in sorting this out! All you need is either a GitHub " +"account or to register directly in our instance." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Address" +#: ../system/translations.rst:13 +msgid "" +"Did you know? This is also where the documentation translations are handled. " +"🤓" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.address}``" +#: ../system/translations.rst:15 +msgid "" +"Have a look in our :docs:`contribution section ` in the system documentation to get started!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created at" +#: ../system/translations.rst:20 +msgid "Local Translations" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_at}``" +#: ../system/translations.rst:22 +msgid "" +"Apart from these system translations, there's still local translations you " +"can manage. This is relevant if you added custom objects that require " +"translations or even custom states and priorities." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "2019-10-07 16:25:00 UTC" +#: ../system/translations.rst:None +msgid "Translation management screen within the admin menu" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Closing time" +#: ../system/translations.rst:31 +msgid "Updating Translations" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.close_at}``" +#: ../system/translations.rst:33 +msgid "" +"Because of how Zammad ships translations, the only way to update the system " +"translations is to update your Zammad installation. The benefit of this is " +"that you no longer need internet access during a Zammad upgrade as the " +"package has everything it requires already." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "2019-10-07 17:25:00 UTC" +#: ../system/translations.rst:39 +msgid "Translation of Custom Objects" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``3``, any number of articles existing in the ticket right now" +#: ../system/translations.rst:41 +msgid "" +"No problem at all! You can customize any translation locally, even if it is " +"not initially provided by the system." msgstr "" -#: ../system/version.rst:2 -msgid "Version" +#: ../system/translations.rst:44 +msgid "" +"Translation is supported for a broad number of features, including but not " +"limited to custom:" msgstr "" -#: ../system/version.rst:4 -msgid "Shows which version is currently being used on your Zammad-instance." +#: ../system/translations.rst:47 +msgid "Object Attributes" msgstr "" -#: ../manage/roles/admin-permissions.rst:53 -msgid "``admin.checklist``" +#: ../system/translations.rst:48 +msgid "Ticket Macros" msgstr "" -#: ../manage/roles/admin-permissions.rst:54 -msgid ":doc:`Manage > Checklist `" +#: ../system/translations.rst:49 +msgid "Ticket Overviews" msgstr "" -#: ../manage/roles/admin-permissions.rst:83 -msgid "``admin.channel_whatsapp``" +#: ../system/translations.rst:50 +msgid "Ticket Priorities" msgstr "" -#: ../manage/roles/admin-permissions.rst:84 -msgid ":doc:`Channels > Whatsapp `" +#: ../system/translations.rst:51 +msgid "Ticket States" msgstr "" -#: ../manage/roles/admin-permissions.rst:124 -msgid "``admin.public_links``" +#: ../system/translations.rst:54 +msgid "Customizing Translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:125 -msgid ":doc:`Manage > Public Links `" +#: ../system/translations.rst:56 +msgid "" +"Within the translation screen, simply click on the **New Translation** " +"button." msgstr "" -#: ../manage/roles/admin-permissions.rst:151 -msgid "``admin.system_report``" +#: ../system/translations.rst:None +msgid "New translation dialog" msgstr "" -#: ../manage/roles/admin-permissions.rst:152 -msgid ":doc:`System > System Report `" +#: ../system/translations.rst:62 +msgid "" +"In the dialog you can immediately enter the exact translation source (if you " +"know it) and your custom translation text for it and click **Submit**." msgstr "" -#: ../manage/roles/admin-permissions.rst:166 -msgid "``admin.ticket_auto_assignment``" +#: ../system/translations.rst:65 +msgid "" +"Alternatively, try to search for translation suggestions in the list below. " +"Selecting an item from the list will pre-fill the translation source for you " +"and then you can just enter your custom translation." msgstr "" -#: ../manage/roles/admin-permissions.rst:167 -msgid ":ref:`Settings > Ticket > Auto Assignment `" +#: ../system/translations.rst:69 +msgid "" +"The target language will always default to your current language selection. " +"If you need to translate for a different language, simply change the " +"selection before submitting." msgstr "" -#: ../manage/roles/admin-permissions.rst:169 -msgid "``admin.ticket_duplicate_detection``" +#: ../system/translations.rst:73 +msgid "" +"All your custom translations will show up in the overview table when added. " +"And they will even persist across Zammad updates!" msgstr "" -#: ../manage/roles/admin-permissions.rst:170 -msgid ":ref:`Settings > Ticket > Duplicate Detection `" +#: ../system/translations.rst:76 +msgid "" +"Make sure to reload your browser if a translated string is not displayed." msgstr "" -#: ../manage/roles/admin-permissions.rst:172 -msgid "``admin.ticket_priority``" +#: ../system/translations.rst:80 +msgid "Reverting to Original Translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:173 -msgid ":ref:`System > Objects >Ticket Priority `" +#: ../system/translations.rst:82 +msgid "" +"If you want to revert a custom translation to original text, simply use the " +"appropriate action within the row of the overview table." msgstr "" -#: ../manage/roles/admin-permissions.rst:175 -msgid "``admin.ticket_state``" +#: ../system/translations.rst:85 +msgid "" +"Depending on the type of the translation source, the action has a slightly " +"different name:" msgstr "" -#: ../manage/roles/admin-permissions.rst:176 -msgid ":ref:`System > Objects >Ticket State `" +#: ../system/translations.rst:88 +msgid "**Reset** for customized system translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:193 -msgid "``admin.webhook``" +#: ../system/translations.rst:89 +msgid "**Remove** for customized local translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:194 -msgid ":doc:`Manage > Webhook `" +#: ../system/translations.rst:91 +msgid "" +"In both cases, the action will remove the customized translation after a " +"confirmation." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:43 -msgid "``user_preferences.appearance``" +#: ../system/translations.rst:None +msgid "Screenshot showing the location of the Remove action" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:44 -#, fuzzy -msgid "Appearance configuration" -msgstr "Konfiguration" +#: ../system/translations.rst:99 +msgid "Inline Translations" +msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:0 -msgid "Users can switch between dark, light and" +#: ../system/translations.rst:101 +msgid "" +"If you prefer a more hands-on approach, you can activate the inline or on-" +"screen translation feature by pressing ``ctrl`` + ``alt`` + ``t`` at any " +"time and on any screen." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:0 -msgid "automatic mode." +#: ../system/translations.rst:105 +msgid "" +"All customizable translation texts will be highlighted for you on the " +"screen. Just click into the highlighted area and update the text in place." msgstr "" -#: ../system/system-report.rst:2 -msgid "System Report" +#: ../system/translations.rst:None +msgid "Inline translation mode activated for the Overview screen" msgstr "" -#: ../system/system-report.rst:4 +#: ../system/translations.rst:112 msgid "" -"In this place you can't configure Zammad. Instead you can obtain a system " -"report about Zammad and its configuration." +"When finished editing, simply press ``ctrl`` + ``alt`` + ``t`` again to " +"deactivate." msgstr "" -#: ../system/system-report.rst:7 +#: ../system/translations.rst:117 msgid "" -"See the description in Zammad for an explanation. You can even find a " -"preview of the included data below the **Download** button." +"Even though it's available on any screen, the inline translation feature " +"requires admin permissions. It works only for the current language " +"selection. If you need to translate a different language, first change the " +"language in your :user-docs:`profile settings `." msgstr "" -#: ../system/system-report.rst:10 -msgid "" -"Zammad never sends this automatically to anyone. It is a manual process only " -"to provide better support based on your configuration." +#: ../system/version.rst:2 +msgid "Version" +msgstr "" + +#: ../system/version.rst:4 +msgid "Shows which version is currently being used on your Zammad-instance." msgstr "" diff --git a/locale/th/LC_MESSAGES/admin-docs.po b/locale/th/LC_MESSAGES/admin-docs.po index fd397f23..92828353 100644 --- a/locale/th/LC_MESSAGES/admin-docs.po +++ b/locale/th/LC_MESSAGES/admin-docs.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Zammad\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-11-06 10:31+0100\n" +"POT-Creation-Date: 2024-11-12 16:31+0100\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -1040,12 +1040,12 @@ msgstr "" #: ../manage/roles/agent-permissions.rst:31 #: ../manage/roles/user-preferences-permissions.rst:37 #: ../manage/scheduler.rst:108 ../manage/webhook/add.rst:116 +#: ../misc/variables.rst:101 #: ../system/integrations/cti/includes/inbound-calls.include.rst:15 #: ../system/integrations/cti/includes/outbound-calls.include.rst:18 #: ../system/integrations/cti/includes/inbound-calls.include.rst:14 #: ../system/integrations/cti/includes/outbound-calls.include.rst:17 -#: ../system/objects.rst:162 ../system/objects.rst:244 -#: ../system/variables.rst:101 ../system/objects.rst:246 +#: ../system/objects.rst:162 ../system/objects.rst:246 msgid "Note" msgstr "" @@ -2257,7 +2257,7 @@ msgstr "" #: ../channels/email/signatures.rst:22 msgid "" "To individualize the signatures, it is possible to automatically load " -"specific information into a signature via :doc:`/system/variables`. All " +"specific information into a signature via :doc:`/misc/variables`. All " "information stored on the ticket, assigned customers or agents can be " "inserted. This makes it possible to design the signature individually. To " "load a list of available variables, enter two colons (``::``) into the " @@ -2550,7 +2550,7 @@ msgstr "" #: ../channels/form.rst:19 ../manage/groups/settings.rst:14 #: ../manage/scheduler.rst:39 ../manage/slas/how-do-they-work.rst:26 #: ../manage/templates.rst:33 ../system/objects.rst:130 -#: ../system/objects.rst:232 ../system/objects.rst:234 +#: ../system/objects.rst:234 msgid "Name" msgstr "" @@ -2579,7 +2579,7 @@ msgstr "" #: ../manage/macros/how-do-they-work.rst:0 ../manage/overviews.rst:0 #: ../manage/scheduler.rst:111 ../manage/templates.rst:43 #: ../manage/webhook/add.rst:123 ../system/objects.rst:169 -#: ../system/objects.rst:246 ../system/objects.rst:248 +#: ../system/objects.rst:248 msgid "Active" msgstr "" @@ -2921,10 +2921,9 @@ msgid "Default value" msgstr "" #: ../channels/form.rst:219 ../manage/public-links.rst:47 -#: ../misc/object-conditions/basics.rst:64 +#: ../misc/object-conditions/basics.rst:64 ../misc/variables.rst:100 #: ../system/core-workflows/condition-operators.rst:21 -#: ../system/objects/permissions.rst:39 ../system/subscription/billing.rst:53 -#: ../system/variables.rst:100 +#: ../system/objects/permissions.rst:39 ../system/subscription.rst:208 msgid "Description" msgstr "" @@ -5908,7 +5907,7 @@ msgstr "" msgid "System" msgstr "" -#: ../index.rst:87 ../index.rst:88 +#: ../index.rst:87 msgid "Misc" msgstr "" @@ -7142,7 +7141,7 @@ msgstr "" #: ../manage/macros/how-do-they-work.rst:28 msgid "" "Unlike triggers, the scheduler, and text modules, macro actions do **not** " -"support the use of :doc:`/system/variables`." +"support the use of :doc:`/misc/variables`." msgstr "" #: ../manage/macros/how-do-they-work.rst:32 @@ -8370,165 +8369,149 @@ msgid "Accessing chat for agents: ``chat.agent``" msgstr "" #: ../manage/roles/admin-permissions.rst:53 +msgid "``admin.checklist``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:54 +msgid ":doc:`Manage > Checklist `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:56 msgid "``admin.channel_email``" msgstr "" -#: ../manage/roles/admin-permissions.rst:54 #: ../manage/roles/admin-permissions.rst:57 msgid ":doc:`Channels > Email `" msgstr "" -#: ../manage/roles/admin-permissions.rst:56 #: ../manage/roles/admin-permissions.rst:59 msgid "``admin.channel_facebook``" msgstr "" -#: ../manage/roles/admin-permissions.rst:57 #: ../manage/roles/admin-permissions.rst:60 msgid ":doc:`Channels > Facebook `" msgstr "" -#: ../manage/roles/admin-permissions.rst:58 #: ../manage/roles/admin-permissions.rst:61 msgid "" "Accessing Facebook tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:59 #: ../manage/roles/admin-permissions.rst:62 msgid "``admin.channel_formular``" msgstr "" -#: ../manage/roles/admin-permissions.rst:60 #: ../manage/roles/admin-permissions.rst:63 msgid ":doc:`Channels > Form `" msgstr "" -#: ../manage/roles/admin-permissions.rst:62 #: ../manage/roles/admin-permissions.rst:65 msgid "``admin.channel_google``" msgstr "" -#: ../manage/roles/admin-permissions.rst:63 #: ../manage/roles/admin-permissions.rst:66 msgid ":doc:`Channels > Google `" msgstr "" -#: ../manage/roles/admin-permissions.rst:65 #: ../manage/roles/admin-permissions.rst:68 msgid "``admin.channel_microsoft365``" msgstr "" -#: ../manage/roles/admin-permissions.rst:66 #: ../manage/roles/admin-permissions.rst:69 msgid ":doc:`Channels > Microsoft 365 `" msgstr "" -#: ../manage/roles/admin-permissions.rst:68 #: ../manage/roles/admin-permissions.rst:71 msgid "``admin.channel_sms``" msgstr "" -#: ../manage/roles/admin-permissions.rst:69 #: ../manage/roles/admin-permissions.rst:72 msgid ":doc:`Channels > SMS `" msgstr "" -#: ../manage/roles/admin-permissions.rst:71 #: ../manage/roles/admin-permissions.rst:74 msgid "``admin.channel_telegram``" msgstr "" -#: ../manage/roles/admin-permissions.rst:72 #: ../manage/roles/admin-permissions.rst:75 msgid ":doc:`Channels > Telegram `" msgstr "" -#: ../manage/roles/admin-permissions.rst:73 #: ../manage/roles/admin-permissions.rst:76 msgid "" "Accessing Telegram tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:74 #: ../manage/roles/admin-permissions.rst:77 msgid "``admin.channel_twitter``" msgstr "" -#: ../manage/roles/admin-permissions.rst:75 #: ../manage/roles/admin-permissions.rst:78 msgid ":doc:`Channels > Twitter `" msgstr "" -#: ../manage/roles/admin-permissions.rst:76 #: ../manage/roles/admin-permissions.rst:79 msgid "" "Accessing Twitter/X tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:77 #: ../manage/roles/admin-permissions.rst:80 msgid "``admin.channel_web``" msgstr "" -#: ../manage/roles/admin-permissions.rst:78 #: ../manage/roles/admin-permissions.rst:81 msgid ":doc:`Channels > Web `" msgstr "" -#: ../manage/roles/admin-permissions.rst:80 +#: ../manage/roles/admin-permissions.rst:83 +msgid "``admin.channel_whatsapp``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:84 +msgid ":doc:`Channels > Whatsapp `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:86 msgid "``admin.core_workflows``" msgstr "" -#: ../manage/roles/admin-permissions.rst:81 #: ../manage/roles/admin-permissions.rst:87 msgid ":doc:`System > Core Workflows `" msgstr "" -#: ../manage/roles/admin-permissions.rst:83 #: ../manage/roles/admin-permissions.rst:89 msgid "``admin.data_privacy``" msgstr "" -#: ../manage/roles/admin-permissions.rst:84 #: ../manage/roles/admin-permissions.rst:90 msgid ":doc:`System > Data Privacy `" msgstr "" -#: ../manage/roles/admin-permissions.rst:85 #: ../manage/roles/admin-permissions.rst:91 msgid "" "🔥 Be careful, it allows users to permanently delete data on the system." msgstr "" -#: ../manage/roles/admin-permissions.rst:86 #: ../manage/roles/admin-permissions.rst:92 msgid "``admin.group``" msgstr "" -#: ../manage/roles/admin-permissions.rst:87 #: ../manage/roles/admin-permissions.rst:93 msgid ":doc:`Manage > Groups `" msgstr "" -#: ../manage/roles/admin-permissions.rst:89 #: ../manage/roles/admin-permissions.rst:95 msgid "``admin.integration``" msgstr "" -#: ../manage/roles/admin-permissions.rst:90 #: ../manage/roles/admin-permissions.rst:96 msgid ":doc:`System > Integrations `" msgstr "" -#: ../manage/roles/admin-permissions.rst:92 #: ../manage/roles/admin-permissions.rst:98 msgid "``admin.knowledge_base``" msgstr "" -#: ../manage/roles/admin-permissions.rst:93 #: ../manage/roles/admin-permissions.rst:99 msgid ":doc:`Manage > Knowledge Base `" msgstr "" @@ -8548,57 +8531,46 @@ msgid "" "knowledge-base.html#editing-answers>`." msgstr "" -#: ../manage/roles/admin-permissions.rst:98 #: ../manage/roles/admin-permissions.rst:104 msgid "``admin.macro``" msgstr "" -#: ../manage/roles/admin-permissions.rst:99 #: ../manage/roles/admin-permissions.rst:105 msgid ":doc:`Manage > Macros `" msgstr "" -#: ../manage/roles/admin-permissions.rst:100 #: ../manage/roles/admin-permissions.rst:106 msgid "In some cases, macros may also require ``admin.tag``" msgstr "" -#: ../manage/roles/admin-permissions.rst:101 #: ../manage/roles/admin-permissions.rst:107 msgid "``admin.maintenance``" msgstr "" -#: ../manage/roles/admin-permissions.rst:102 #: ../manage/roles/admin-permissions.rst:108 msgid ":doc:`System > Maintenance `" msgstr "" -#: ../manage/roles/admin-permissions.rst:104 #: ../manage/roles/admin-permissions.rst:110 msgid "``admin.monitoring``" msgstr "" -#: ../manage/roles/admin-permissions.rst:105 #: ../manage/roles/admin-permissions.rst:111 msgid ":doc:`System > Monitoring `" msgstr "" -#: ../manage/roles/admin-permissions.rst:107 #: ../manage/roles/admin-permissions.rst:113 msgid "``admin.object``" msgstr "" -#: ../manage/roles/admin-permissions.rst:108 #: ../manage/roles/admin-permissions.rst:114 msgid ":doc:`System > Objects `" msgstr "" -#: ../manage/roles/admin-permissions.rst:110 #: ../manage/roles/admin-permissions.rst:116 msgid "``admin.organization``" msgstr "" -#: ../manage/roles/admin-permissions.rst:111 #: ../manage/roles/admin-permissions.rst:117 msgid ":doc:`Manage > Organizations `" msgstr "" @@ -8615,202 +8587,210 @@ msgstr "" msgid "They can even edit an organization's name, domain, and notes!" msgstr "" -#: ../manage/roles/admin-permissions.rst:115 #: ../manage/roles/admin-permissions.rst:121 msgid "``admin.overview``" msgstr "" -#: ../manage/roles/admin-permissions.rst:116 #: ../manage/roles/admin-permissions.rst:122 msgid ":doc:`Manage > Overviews`" msgstr "" -#: ../manage/roles/admin-permissions.rst:118 +#: ../manage/roles/admin-permissions.rst:124 +msgid "``admin.public_links``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:125 +msgid ":doc:`Manage > Public Links `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:127 msgid "``admin.package``" msgstr "" -#: ../manage/roles/admin-permissions.rst:119 #: ../manage/roles/admin-permissions.rst:128 msgid ":doc:`System > Packages `" msgstr "" -#: ../manage/roles/admin-permissions.rst:121 #: ../manage/roles/admin-permissions.rst:130 msgid "``admin.report_profile``" msgstr "" -#: ../manage/roles/admin-permissions.rst:122 #: ../manage/roles/admin-permissions.rst:131 msgid ":doc:`Manage > Report Profiles `" msgstr "" -#: ../manage/roles/admin-permissions.rst:123 #: ../manage/roles/admin-permissions.rst:132 msgid "Access to view reports: ``report``" msgstr "" -#: ../manage/roles/admin-permissions.rst:124 #: ../manage/roles/admin-permissions.rst:133 msgid "``admin.role``" msgstr "" -#: ../manage/roles/admin-permissions.rst:125 #: ../manage/roles/admin-permissions.rst:134 msgid ":doc:`Manage > Roles `" msgstr "" -#: ../manage/roles/admin-permissions.rst:127 #: ../manage/roles/admin-permissions.rst:136 msgid "``admin.scheduler``" msgstr "" -#: ../manage/roles/admin-permissions.rst:128 #: ../manage/roles/admin-permissions.rst:137 msgid ":doc:`Manage > Scheduler `" msgstr "" -#: ../manage/roles/admin-permissions.rst:129 #: ../manage/roles/admin-permissions.rst:138 msgid "For automation on tickets" msgstr "" -#: ../manage/roles/admin-permissions.rst:130 #: ../manage/roles/admin-permissions.rst:139 msgid "``admin.security``" msgstr "" -#: ../manage/roles/admin-permissions.rst:131 #: ../manage/roles/admin-permissions.rst:140 msgid ":doc:`Settings > Security `" msgstr "" -#: ../manage/roles/admin-permissions.rst:132 #: ../manage/roles/admin-permissions.rst:141 msgid "Settings of Zammad. This also covers third party authentications." msgstr "" -#: ../manage/roles/admin-permissions.rst:133 #: ../manage/roles/admin-permissions.rst:142 msgid "``admin.session``" msgstr "" -#: ../manage/roles/admin-permissions.rst:134 #: ../manage/roles/admin-permissions.rst:143 msgid ":doc:`System > Sessions `" msgstr "" -#: ../manage/roles/admin-permissions.rst:136 #: ../manage/roles/admin-permissions.rst:145 msgid "``admin.setting_system``" msgstr "" -#: ../manage/roles/admin-permissions.rst:137 #: ../manage/roles/admin-permissions.rst:146 msgid ":doc:`Settings > System `" msgstr "" -#: ../manage/roles/admin-permissions.rst:139 #: ../manage/roles/admin-permissions.rst:148 msgid "``admin.sla``" msgstr "" -#: ../manage/roles/admin-permissions.rst:140 #: ../manage/roles/admin-permissions.rst:149 msgid ":doc:`Manage > SLAs `" msgstr "" -#: ../manage/roles/admin-permissions.rst:142 +#: ../manage/roles/admin-permissions.rst:151 +msgid "``admin.system_report``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:152 +msgid ":doc:`System > System Report `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:154 msgid "``admin.tag``" msgstr "" -#: ../manage/roles/admin-permissions.rst:143 #: ../manage/roles/admin-permissions.rst:155 msgid ":doc:`Manage > Tags `" msgstr "" -#: ../manage/roles/admin-permissions.rst:145 #: ../manage/roles/admin-permissions.rst:157 msgid "``admin.template``" msgstr "" -#: ../manage/roles/admin-permissions.rst:146 #: ../manage/roles/admin-permissions.rst:158 msgid ":doc:`Manage > Templates `" msgstr "" -#: ../manage/roles/admin-permissions.rst:148 #: ../manage/roles/admin-permissions.rst:160 msgid "``admin.text_module``" msgstr "" -#: ../manage/roles/admin-permissions.rst:149 #: ../manage/roles/admin-permissions.rst:161 msgid ":doc:`Manage > Text Modules `" msgstr "" -#: ../manage/roles/admin-permissions.rst:151 #: ../manage/roles/admin-permissions.rst:163 msgid "``admin.ticket``" msgstr "" -#: ../manage/roles/admin-permissions.rst:152 #: ../manage/roles/admin-permissions.rst:164 msgid ":doc:`Settings > Tickets `" msgstr "" -#: ../manage/roles/admin-permissions.rst:153 #: ../manage/roles/admin-permissions.rst:165 msgid "Does not grant access to :doc:`/misc/composer`" msgstr "" -#: ../manage/roles/admin-permissions.rst:154 +#: ../manage/roles/admin-permissions.rst:166 +msgid "``admin.ticket_auto_assignment``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:167 +msgid ":ref:`Settings > Ticket > Auto Assignment `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:169 +msgid "``admin.ticket_duplicate_detection``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:170 +msgid ":ref:`Settings > Ticket > Duplicate Detection `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:172 +msgid "``admin.ticket_priority``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:173 +msgid ":ref:`System > Objects >Ticket Priority `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:175 +msgid "``admin.ticket_state``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:176 +msgid ":ref:`System > Objects >Ticket State `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:178 msgid "``admin.time_accounting``" msgstr "" -#: ../manage/roles/admin-permissions.rst:155 #: ../manage/roles/admin-permissions.rst:179 msgid ":doc:`Manage > Time Accounting `" msgstr "" -#: ../manage/roles/admin-permissions.rst:156 #: ../manage/roles/admin-permissions.rst:180 msgid "Also allows the export of timekeeping records." msgstr "" -#: ../manage/roles/admin-permissions.rst:157 #: ../manage/roles/admin-permissions.rst:181 msgid "``admin.translation``" msgstr "" -#: ../manage/roles/admin-permissions.rst:158 #: ../manage/roles/admin-permissions.rst:182 msgid ":doc:`System > Translations `" msgstr "" -#: ../manage/roles/admin-permissions.rst:159 #: ../manage/roles/admin-permissions.rst:183 msgid "Also enables inline translation" msgstr "" -#: ../manage/roles/admin-permissions.rst:160 #: ../manage/roles/admin-permissions.rst:184 msgid "``admin.trigger``" msgstr "" -#: ../manage/roles/admin-permissions.rst:161 #: ../manage/roles/admin-permissions.rst:185 msgid ":doc:`Manage > Triggers `" msgstr "" -#: ../manage/roles/admin-permissions.rst:163 #: ../manage/roles/admin-permissions.rst:187 msgid "``admin.user``" msgstr "" -#: ../manage/roles/admin-permissions.rst:164 #: ../manage/roles/admin-permissions.rst:188 msgid ":doc:`Manage > Users `" msgstr "" @@ -8829,6 +8809,14 @@ msgid "" "from-users-perspective>` ." msgstr "" +#: ../manage/roles/admin-permissions.rst:193 +msgid "``admin.webhook``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:194 +msgid ":doc:`Manage > Webhook `" +msgstr "" + #: ../manage/roles/agent-permissions.rst:2 msgid "Agent Permissions" msgstr "" @@ -9247,36 +9235,45 @@ msgid "than the user that generated them." msgstr "" #: ../manage/roles/user-preferences-permissions.rst:43 +msgid "``user_preferences.appearance``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:44 +msgid "Appearance configuration" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "Users can switch between dark, light and" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "automatic mode." +msgstr "" + #: ../manage/roles/user-preferences-permissions.rst:47 msgid "``user_preferences.avatar``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:44 #: ../manage/roles/user-preferences-permissions.rst:48 msgid "Avatar settings" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:45 #: ../manage/roles/user-preferences-permissions.rst:49 msgid "Override the default Gravatar with a custom avatar" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:46 #: ../manage/roles/user-preferences-permissions.rst:50 msgid "``user_preferences.calendar``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:47 #: ../manage/roles/user-preferences-permissions.rst:51 msgid "Configure the calendar feed" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:49 #: ../manage/roles/user-preferences-permissions.rst:53 msgid "``user_preferences.device``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:50 #: ../manage/roles/user-preferences-permissions.rst:54 msgid "Manage device login sessions" msgstr "" @@ -9293,22 +9290,18 @@ msgstr "" msgid "To learn more, see :doc:`/manage/trigger/system-notifications`." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:54 #: ../manage/roles/user-preferences-permissions.rst:58 msgid "``user_preferences.language``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:55 #: ../manage/roles/user-preferences-permissions.rst:59 msgid "Configure the UI locale/language" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:57 #: ../manage/roles/user-preferences-permissions.rst:61 msgid "``user_preferences.linked_accounts``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:58 #: ../manage/roles/user-preferences-permissions.rst:62 msgid "Account linking" msgstr "" @@ -9332,7 +9325,6 @@ msgstr "" msgid "is the only way users can utilize third-party logins." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:63 #: ../manage/roles/user-preferences-permissions.rst:67 msgid "``user_preferences.notifications``" msgstr "" @@ -9359,7 +9351,6 @@ msgstr "" msgid "Customers can't receive ticket notifications at all." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:69 #: ../manage/roles/user-preferences-permissions.rst:73 msgid "``user_preferences.out_of_office``" msgstr "" @@ -9384,7 +9375,6 @@ msgstr "" msgid "they're replacing." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:75 #: ../manage/roles/user-preferences-permissions.rst:79 msgid "``user_preferences.overview_sorting``" msgstr "" @@ -9413,12 +9403,10 @@ msgstr "" msgid "overviews has no effect on custom orders." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:82 #: ../manage/roles/user-preferences-permissions.rst:86 msgid "``user_preferences.password``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:83 #: ../manage/roles/user-preferences-permissions.rst:87 msgid "Change account password" msgstr "" @@ -9435,7 +9423,6 @@ msgstr "" msgid "your only allowed authentication method." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:87 #: ../manage/roles/user-preferences-permissions.rst:91 msgid "``user_preferences.two_factor_authentication``" msgstr "" @@ -9472,7 +9459,7 @@ msgstr "" #: ../manage/scheduler.rst:19 msgid "" -"Schedulers can be used to send periodic reminder emails. Use :doc:`/system/" +"Schedulers can be used to send periodic reminder emails. Use :doc:`/misc/" "variables` to build highly-customized email templates." msgstr "" @@ -10468,7 +10455,7 @@ msgstr "" #: ../manage/text-modules.rst:57 msgid "" -"The example text modules below use :doc:`/system/variables` to dynamically " +"The example text modules below use :doc:`/misc/variables` to dynamically " "insert information like the customer's or agent's names." msgstr "" @@ -10808,8 +10795,8 @@ msgstr "" #: ../misc/object-conditions/basics.rst:144 #: ../misc/object-conditions/basics.rst:160 #: ../misc/object-conditions/basics.rst:168 -#: ../misc/object-conditions/basics.rst:178 ../settings/ticket.rst:2 -#: ../system/variables/ticket.rst:2 +#: ../misc/object-conditions/basics.rst:178 ../misc/variables/ticket.rst:2 +#: ../settings/ticket.rst:2 msgid "Ticket" msgstr "" @@ -11043,7 +11030,7 @@ msgstr "" #: ../manage/trigger/how-do-they-work.rst:79 msgid "" -"Certain actions (such as *email*, *SMS* and *notes*) support :doc:`/system/" +"Certain actions (such as *email*, *SMS* and *notes*) support :doc:`/misc/" "variables`, which can be used to build highly-customized message templates." msgstr "" @@ -11072,7 +11059,7 @@ msgstr "" msgid "" "You can also combine static text with placeholders for text fields. Remember " "that the placeholders' values have to be known during trigger runtime. Learn " -"more about :doc:`/system/variables`." +"more about :doc:`/misc/variables`." msgstr "" #: ../manage/trigger/how-do-they-work.rst:105 @@ -12037,7 +12024,7 @@ msgstr "" msgid "" "When switched on, a code editor will be shown below, where you can configure " "custom payload for your webhook in JSON format. To insert supported :doc:`/" -"system/variables` use ``::`` or ``#{`` shortcuts for autocomplete." +"misc/variables` use ``::`` or ``#{`` shortcuts for autocomplete." msgstr "" #: ../manage/webhook/add.rst:103 @@ -14614,11942 +14601,11833 @@ msgid "" "powerful conditions with AND/OR relations." msgstr "" -#: ../settings/branding.rst:10 -msgid "Product Name" +#: ../misc/variables.rst:2 +msgid "Variables" msgstr "" -#: ../settings/branding.rst:7 +#: ../misc/variables.rst:4 msgid "" -"Defines the name of the application, shown in the web interface, tabs and " -"title bar of the web browser." +"Please note that this is just an overview of available variables. It might " +"be incomplete or variables might not be available within some functions. If " +"you're missing variables or are not sure if something is not working as " +"expected, feel free to ask over at the `Community `_." msgstr "" -#: ../settings/branding.rst:10 -msgid "Default value: ``Zammad Helpdesk``" +#: ../misc/variables.rst:10 +msgid "" +"Variables can be called by typing ``::`` (just like text modules in the " +"frontend), as long as you're in a supported text field within the backend. " +"Zammad will display all variables being available within this context and " +"replace it to the variable as soon as you selected an entry." msgstr "" -#: ../settings/branding.rst:13 -msgid "Will be shown in the app and is included in email footers." +#: ../misc/variables.rst:15 +msgid "" +"You have an empty field which you referenced and it appears as ``-``? That's " +"currently working as designed - you might want to ensure that these fields " +"always have a value." msgstr "" -#: ../settings/branding.rst:19 -msgid "Logo" +#: ../misc/variables.rst:20 +msgid "Variable Categories" msgstr "" -#: ../settings/branding.rst:16 -msgid "Defines the logo of the application, shown in the login page of Zammad." +#: ../misc/variables.rst:31 +msgid "Wait, What About Custom Objects?" msgstr "" -#: ../settings/branding.rst:18 +#: ../misc/variables.rst:33 msgid "" -"Ensure to hit the \"Submit\" button after uploading the logo. Otherwise your " -"change will not be saved." +"Good point! Of course, we can't predict what objects you might create, but " +"we can give you a hint on how to put the puzzle together to get your custom " +"values." msgstr "" -#: ../settings/branding.rst:22 +#: ../misc/variables.rst:36 msgid "" -"Allows to set the default language of the Zammad instance. The here defined " -"locale mostly acts as a fallback for:" -msgstr "" - -#: ../settings/branding.rst:25 -msgid "user preferences (if Zammad can't detect the users locale)" +"For this, we'll talk about the inner part of the variable (so everything " +"within ``#{}``), please put the outer part around to have a valid variable. " +"The first part of the variable name consist of the object type. Currently " +"these are:" msgstr "" -#: ../settings/branding.rst:26 -msgid "CSV output (reporting, time accounting)" +#: ../misc/variables.rst:41 +msgid "Ticket (``ticket``)" msgstr "" -#: ../settings/branding.rst:30 -msgid "Define the timezone of your Zammad installation." +#: ../misc/variables.rst:42 +msgid "User (``user``)" msgstr "" -#: ../settings/branding.rst:32 -msgid "" -"This does not have any effect on timings for your agents or how Zammad " -"stores date and time values." +#: ../misc/variables.rst:43 +msgid "Organization (``organization``)" msgstr "" -#: ../settings/branding.rst:35 -msgid "Changing this value has direct consequences on the following areas:" +#: ../misc/variables.rst:44 +msgid "Group (``group``)" msgstr "" -#: ../settings/branding.rst:37 -msgid ":doc:`/manage/scheduler` tasks" +#: ../misc/variables.rst:46 +msgid "" +"The second part is the name of the attribute. This is the name you define " +"during object creation and can be found within the object attribute menu at " +"any time. The first and second part of a variable is divided by a point, e." +"g.: ``ticket.number`` which will in total be ``#{ticket.number}``." msgstr "" -#: ../settings/branding.rst:38 -msgid "search indexing (and thus reporting)" +#: ../misc/variables.rst:51 +msgid "" +"Now, in some situations it's possible that you'll need to use a third part. " +"The best example for such a situation would be a ``select`` or ``tree-" +"select`` field which will by default return the key value, not it's display " +"name. For this, just extend your variable with ``.value``. This will result " +"in ``#{ticket.select.value}``." msgstr "" -#: ../settings/branding.rst:40 -msgid "calendar subscriptions" +#: ../misc/variables.rst:60 +msgid "Using Translated Variables" msgstr "" -#: ../settings/branding.rst:41 -msgid "browser printing" +#: ../misc/variables.rst:62 +msgid "" +"If you want to use a translated variable in triggers or schedulers, you can " +"extend the placeholder like this: ``#{t(ticket.state.name)}``. The ``t`` " +"tells Zammad to search for fitting translated strings. The used output " +"language is based on the system language of Zammad which you can set in the " +"admin panel under :doc:`/settings/branding` or based on the selected locale " +"in the trigger/scheduler edit dialog." msgstr "" -#: ../settings/branding.rst:43 +#: ../misc/variables.rst:69 msgid "" -"Please note that some of above are fallbacks in case Zammad could not detect " -"the agents timezone correctly." +"A possible use-case: you want to send your customers updates on tickets via " +"trigger or scheduler which should include the state of the ticket. Using the " +"default ``#{ticket.state.name}`` (without the translation flag ``t()``) " +"would lead to the output of the original (english) name of the state." msgstr "" -#: ../settings/branding.rst:77 -msgid "Pretty Date" +#: ../misc/variables.rst:75 +msgid "Date and Time Formatting" msgstr "" -#: ../settings/branding.rst:47 +#: ../misc/variables.rst:77 msgid "" -"This setting allows you to define how Zammad should display time stamps " -"within the interface to all users." +"The system (trigger/scheduler selected) locale and timezone predefines a " +"default format of date and timestamp. This format is customizable by using " +"the ``dt()`` method." msgstr "" -#: ../settings/branding.rst:50 -msgid "" -"This does not have any effect on how Zammad returns e.g. time values via " -"variables." +#: ../misc/variables.rst:79 +msgid "The method arguments are as follows:" msgstr "" -#: ../settings/branding.rst:77 -msgid "Choose in between the following options:" +#: ../misc/variables.rst:81 +msgid "The date or timestamp variable you want to format." msgstr "" -#: ../settings/branding.rst:64 -msgid "relative" +#: ../misc/variables.rst:82 +msgid "The output format string." msgstr "" -#: ../settings/branding.rst:55 +#: ../misc/variables.rst:83 +msgid "The timezone to apply (optional)." +msgstr "" + +#: ../misc/variables.rst:85 +#: ../system/objects/external-data-source-example.rst:23 +msgid "**Example:**" +msgstr "" + +#: ../misc/variables.rst:86 msgid "" -"This timestamp shows a relative time span until it switches to a date. Over " -"time, it will change as follows:" +"``#{dt(ticket.updated_at, \"%A %Y-%m-%d %H:%M in the office\", \"Europe/" +"Berlin\")}``" msgstr "" -#: ../settings/branding.rst:58 -msgid "just now" +#: ../misc/variables.rst:87 +msgid "Monday, 2024-03-18 15:31 in the office" msgstr "" -#: ../settings/branding.rst:59 -msgid "5 minutes ago" +#: ../misc/variables.rst:89 +msgid "" +"If you want to use our example, make sure to paste the string above without " +"formatting (``CTRL+Shift+v``), otherwise it won't work." msgstr "" -#: ../settings/branding.rst:60 -msgid "3 days 1 hour ago" +#: ../misc/variables.rst:93 +msgid "The following table lists available format directives:" msgstr "" -#: ../settings/branding.rst:61 -msgid "``03/04/2022``" +#: ../misc/variables.rst:99 +msgid "Parameter" msgstr "" -#: ../settings/branding.rst:63 -msgid "Hovering the timestamp helps, you'll always get a clean timestamp then." +#: ../misc/variables.rst:102 +msgid "``%Y``" msgstr "" -#: ../settings/branding.rst:71 -msgid "absolute" +#: ../misc/variables.rst:103 +msgid "Year with 4 digits" msgstr "" -#: ../settings/branding.rst:67 -msgid "" -"This timestamp always includes the week day. For one week after creation, " -"the timestamp will not contain the date itself: Thursday 18:35." +#: ../misc/variables.rst:104 +msgid "Use ``%y`` for year with 2 digits" msgstr "" -#: ../settings/branding.rst:71 -msgid "After a week it will switch to: ``Friday 4. Mar 16:00``." +#: ../misc/variables.rst:105 +msgid "``%m``" msgstr "" -#: ../settings/branding.rst:76 -msgid "timestamp" +#: ../misc/variables.rst:106 +msgid "Month of year (as number with zero-padding)" msgstr "" -#: ../settings/branding.rst:74 -msgid "" -"This will cause Zammad to show a complete timestamp according to your locale " -"defaults. For English this could be e.g. ``2022/12/03 2:40 pm`` or for " -"German e.g. ``12.03.2022 14:40``." +#: ../misc/variables.rst:107 +msgid "Use ``%-m`` for month without zero-padding" msgstr "" -#: ../settings/branding.rst:78 -msgid "Default setting: ``relative``." +#: ../misc/variables.rst:108 +msgid "``%d``" msgstr "" -#: ../settings/security.rst:2 -msgid "Security" +#: ../misc/variables.rst:109 +msgid "Day of month (as number with zero-padding)" msgstr "" -#: ../settings/security.rst:4 -msgid "" -"For your overview we split each tab within security settings into its own " -"page:" +#: ../misc/variables.rst:110 +msgid "Use ``%e`` for day without zero-padding" msgstr "" -#: ../settings/security/base.rst:2 ../settings/system/base.rst:2 -#: ../settings/ticket.rst:8 -msgid "Base" +#: ../misc/variables.rst:111 +msgid "``%H``" msgstr "" -#: ../settings/security/base.rst:5 -msgid "New User Accounts" +#: ../misc/variables.rst:112 +msgid "Hour of day in 24h notation with zero-padding" msgstr "" -#: ../settings/security/base.rst:9 -msgid "" -"Activates the `register as a new customer` function on the login page. If " -"set to ``no`` only administrators or agents can create new accounts manually." +#: ../misc/variables.rst:113 +msgid "Use ``%k`` for hour without zero-padding" msgstr "" -#: ../settings/security/base.rst:13 ../settings/security/base.rst:38 -#: ../settings/security/base.rst:66 -msgid "Default setting: ``yes``" +#: ../misc/variables.rst:114 +msgid "``%I``" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing activated \"New User Accounts\" setting" +#: ../misc/variables.rst:115 +msgid "Hour of day in 12h notation with zero-padding" msgstr "" -#: ../settings/security/base.rst:22 +#: ../misc/variables.rst:116 msgid "" -"Deactivation of above function **does not** deactivate automatic account " -"creation! This means: If a user writes e.g. an email to Zammad and has no " -"account yet, Zammad will automatically create the account. User accounts are " -"a direct dependency of tickets and thus technically mandatory." +"Use ``%l`` for hour without zero-padding and ``%p`` / ``%P`` for meridian " +"indicator" msgstr "" -#: ../settings/security/base.rst:29 -msgid "Lost Password" +#: ../misc/variables.rst:117 +msgid "``%M``" msgstr "" -#: ../settings/security/base.rst:33 -msgid "" -"Activates the `lost password` function on the login page. If set to ``no`` " -"only administrators may change the user's password - users may update their " -"own password if they're still logged in and they have the required :doc:" -"`permission `." +#: ../misc/variables.rst:118 +msgid "Minute of hour" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing activated \"Lost Password\" setting" +#: ../misc/variables.rst:120 +msgid "``%S``" msgstr "" -#: ../settings/security/base.rst:49 -msgid "" -"With third party authentications - but especially LDAP - you may want to " -"disable this function. Zammad **will not** change third party login " -"passwords and instead set or change the local password!" +#: ../misc/variables.rst:121 +msgid "Second of Minute" msgstr "" -#: ../settings/security/base.rst:56 -msgid "Password Login" +#: ../misc/variables.rst:123 +msgid "``%A``" msgstr "" -#: ../settings/security/base.rst:60 -msgid "" -"Activates the username & password login by default and if no third-party " -"login is activated. Disabling password login on the Zammad login page only " -"takes effect if you enable any :doc:`third-party`." +#: ../misc/variables.rst:124 +msgid "Weekday name" msgstr "" -#: ../settings/security/base.rst:64 -msgid "See :doc:`third-party` for supported third-party logins." +#: ../misc/variables.rst:125 +msgid "Use ``%a`` for abbreviated name or ``%^A`` for uppercase name" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing de-activated \"Password Login\" setting" +#: ../misc/variables.rst:126 +msgid "``%B``" msgstr "" -#: ../settings/security/base.rst:77 -msgid "" -"To help administrators to overcome \"login issues\", Zammad automatically " -"offers a password request for administrator users. This allows you to adjust " -"Third-Party applications even if the login does no longer work!" +#: ../misc/variables.rst:127 +msgid "Month name" msgstr "" -#: ../settings/security/base.rst:84 -msgid "Session Timeout" +#: ../misc/variables.rst:128 +msgid "Use ``%b`` for abbreviated name" msgstr "" -#: ../settings/security/base.rst:86 -msgid "" -"All settings below by default are set to ``4 weeks``. Session Timeout " -"defines the life time of a users session. As soon as it's reached, Zammad " -"will automatically log off the session in question." +#: ../misc/variables.rst:129 +msgid "``%U``" msgstr "" -#: ../settings/security/base.rst:91 -msgid "" -"Zammad takes the highest value set assigned for the user based on the " -"permissions." +#: ../misc/variables.rst:130 +msgid "Week number of current year" msgstr "" -#: ../settings/security/base.rst:94 -msgid "``admin``" +#: ../misc/variables.rst:131 +msgid "Use ``%W`` for a different calculation method" msgstr "" -#: ../settings/security/base.rst:96 -msgid "``ticket.customer``" +#: ../misc/variables.rst:134 +msgid "" +"We support the known format directives for the Ruby built-in method " +"``strftime`` of the ``DateTime`` class. For more information, see `here " +"`_." msgstr "" -#: ../settings/security/base.rst:97 -msgid "``default`` (fallback if user doesn't have above permissions set)" +#: ../misc/variables/article.rst:2 +msgid "Articles" msgstr "" -#: ../settings/security/base.rst:99 +#: ../misc/variables/article.rst:4 ../misc/variables/config.rst:4 +#: ../misc/variables/current-user.rst:4 ../misc/variables/ticket.rst:4 msgid "" -"All settings act independently from each other allowing you to disable the " -"timeouts for e.g. admins, but not agents." +"If you're missing variables or are not sure if something is not working as " +"expected, feel free to ask over at the `Community `_." msgstr "" -#: ../settings/security/base.rst:115 -#: ../system/integrations/checkmk/api-reference.rst:13 -msgid "Example" +#: ../misc/variables/article.rst:6 +msgid "" +"Below you can find all available ticket article-based variables within " +"Zammad. These can be called via triggers for example. If you're unsure if " +"Zammad does support variables at the point you're at, you can try to type " +"``::`` to check." msgstr "" -#: ../settings/security/base.rst:107 -msgid "Let's suppose you configured the following session timeouts" +#: ../misc/variables/article.rst:9 ../misc/variables/config.rst:9 +#: ../misc/variables/ticket.rst:9 +msgid "" +"The below list gives you an example what kind of data you can expect, it's " +"not intended to explain the data itself." msgstr "" -#: ../settings/security/base.rst:104 -msgid "default: 3 weeks" +#: ../misc/variables/article.rst:11 +msgid "Article Variables" msgstr "" -#: ../settings/security/base.rst:105 -msgid "admin: 2 weeks" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "name" msgstr "" -#: ../settings/security/base.rst:106 -msgid "ticket.agent: 4 weeks" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "variable" msgstr "" -#: ../settings/security/base.rst:107 -msgid "ticket.customer: 1 week" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "example" msgstr "" -#: ../settings/security/base.rst:115 -msgid "This results in the following situations" +#: ../misc/variables/article.rst:1 +msgid "Article > Cc" msgstr "" -#: ../settings/security/base.rst:110 -msgid "a user with ``admin`` permission will have a timeout of 2 weeks" +#: ../misc/variables/article.rst:1 +msgid "``#{article.cc}``" msgstr "" -#: ../settings/security/base.rst:111 -msgid "" -"a user with ``admin`` and ``ticket.agent`` permissions will have a timeout " -"of 2 weeks" +#: ../misc/variables/article.rst:1 +msgid "``jdoe@example.com, company@example.com``" msgstr "" -#: ../settings/security/base.rst:113 -msgid "" -"a user with ``ticket.customer`` permission will have a timeout of 1 week" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Address" msgstr "" -#: ../settings/security/base.rst:115 -msgid "" -"a user with neither ``admin``, ``ticket.agent`` nor ``ticket.customer`` " -"permissions will have a timeout of 3 weeks" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.address}``" msgstr "" -#: ../settings/security/password.rst:4 -msgid "" -"This section allows you to define password requirements for the local user " -"accounts." +#: ../misc/variables/article.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:9 -msgid "" -"Zammad does **not** allow you to change your LDAP password, instead, it will " -"set a password in its local database which might confuse your users. This " -"might be addressed in the future by `#1169 `_." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Department" msgstr "" -#: ../settings/security/password.rst:14 -msgid "**Exception for admins**" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.department}``" msgstr "" -#: ../settings/security/password.rst:16 -msgid "" -"Please note that below password policies *do not* affect administrators " -"setting passwords on user accounts. While this seems strange and not safe we " -"believe that an administrator knowing an user's password is insecure as well." +#: ../misc/variables/article.rst:1 +msgid "``Sales`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:21 -msgid "The suggested workflow is either:" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Email" msgstr "" -#: ../settings/security/password.rst:23 -msgid "" -"to use third party logins to not require local passwords at all **- or -**" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.email}``" msgstr "" -#: ../settings/security/password.rst:25 -msgid "to require your *user to reset the password* upon first login." +#: ../misc/variables/article.rst:1 +msgid "``jdoe@example.com``" msgstr "" -#: ../settings/security/password.rst:27 -msgid "" -"This way administrators are not required to set a user's password at all!" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Fax" msgstr "" -#: ../settings/security/password.rst:31 -msgid "Maximum Failed Logins" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.fax}``" msgstr "" -#: ../settings/security/password.rst:33 -msgid "" -"You can choose a value between ``4`` and ``20``. This defines how often a " -"login to a user account may fail until Zammad will lock it. Your users can " -"always use the \"forgot password\" function to change their password and " -"unlock their account." -msgstr "" - -#: ../settings/security/password.rst:38 -msgid "The default value is ``10``." +#: ../misc/variables/article.rst:1 +msgid "``+4930123456789`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:42 -msgid "Beside changing the user's password, you can also unlock accounts via" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Firstname" msgstr "" -#: ../settings/security/password.rst:44 -msgid ":ref:`user management list `" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.firstname}``" msgstr "" -#: ../settings/security/password.rst:45 -msgid ":docs:`console `" +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Joe`` or empty if not set" msgstr "" -#: ../settings/security/password.rst:46 -msgid ":docs:`API `" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Lastname" msgstr "" -#: ../settings/security/password.rst:50 -msgid "Failed logins via LDAP no longer lock accounts." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.lastname}``" msgstr "" -#: ../settings/security/password.rst:53 -msgid "2 Lower Case And 2 Upper Case Characters" +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +#: ../misc/variables/ticket.rst:1 +msgid "``Doe`` or empty if not set" msgstr "" -#: ../settings/security/password.rst:55 -msgid "" -"You can add complexity to passwords by enforcing at least 2 upper and lower " -"case characters." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Login" msgstr "" -#: ../settings/security/password.rst:58 ../settings/security/password.rst:83 -msgid "The default value is ``no``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.login}``" msgstr "" -#: ../settings/security/password.rst:62 -msgid "Minimum Length" +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +#: ../misc/variables/ticket.rst:1 +msgid "``jdoe``" msgstr "" -#: ../settings/security/password.rst:64 -msgid "" -"This defines the minimum password length required for users to provide (from " -"``4`` to ``20``)." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Mobile" msgstr "" -#: ../settings/security/password.rst:67 -msgid "The default value is ``6``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.mobile}``" msgstr "" -#: ../settings/security/password.rst:71 -msgid "Digit Required" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Note" msgstr "" -#: ../settings/security/password.rst:73 -msgid "This enforces your users to use at least one digit within the password." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.note}``" msgstr "" -#: ../settings/security/password.rst:75 -msgid "The default value is ``yes``." +#: ../misc/variables/article.rst:1 +msgid "``Some note about user`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:78 -msgid "Special Character Required" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Phone" msgstr "" -#: ../settings/security/password.rst:80 -msgid "" -"This setting allows you to improve your password quality even more by " -"enforcing the password to contain at least one special character." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.phone}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:2 -msgid "SSL Certificates" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > VIP" msgstr "" -#: ../settings/security/ssl-certificates.rst:7 -msgid "" -"Zammad offers the possibility to upload custom certificates and custom " -"Certificate Authority (CA) certificates. This can be useful if you want to " -"connect Zammad the secure way to other systems which are using custom " -"certificates." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.vip}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:12 -msgid "" -"An example usecase might be: You have an internal LDAP server that is not " -"accessible from the internet, and you want a SSL-encrypted connection, using " -"a custom certificate." +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +msgid "``true`` or ``false``" msgstr "" -#: ../settings/security/ssl-certificates.rst:19 -msgid "" -"You should have an existing custom certificate file and/or a custom CA " -"certificate file, which you want to add to Zammad. As filetype ``.crt`` is " -"supported and the certificate format has to be PEM (Base64 ASCII)." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Web" msgstr "" -#: ../settings/security/ssl-certificates.rst:25 -msgid "" -"When you import a custom CA certificate, all certificates generated with " -"this are trusted. This can be useful if you have more than one system/" -"certificate you want to connect to and the certificates are issued from the " -"same custom CA." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.web}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:31 -msgid "Add a Certificate" +#: ../misc/variables/article.rst:1 +msgid "``https://zammad.com`` or empty if not set in user object" msgstr "" -#: ../settings/security/ssl-certificates.rst:33 -msgid "" -"To add a custom certificate or a custom CA certificate, head over to the " -"Admin panel > Settings > Security > SSL Certificates. Here you can find a " -"\"Add SSL Certificate\" button. In the dialog you can either select a " -"certificate file or paste the content of the certificate:" +#: ../misc/variables/article.rst:1 +msgid "Article > Created" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate adding dialog" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_at}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:43 -msgid "" -"After selecting a file or pasting the content of the certificate, click on " -"the \"Add\" button to finally upload it to Zammad. Then, the certificates " -"are immediately effective, no restart or similar required." +#: ../misc/variables/article.rst:1 +msgid "``2019-10-08 15:24:47 UTC``" msgstr "" -#: ../settings/security/ssl-certificates.rst:49 -msgid "" -"Please note that only single certificate files are supported. That means if " -"you want to import a certificate / CA certificate, it must contain **only " -"one** certificate." +#: ../misc/variables/article.rst:1 +msgid "Article > From" msgstr "" -#: ../settings/security/ssl-certificates.rst:54 -msgid "Certificate Overview" +#: ../misc/variables/article.rst:1 +msgid "``#{article.from}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:56 +#: ../misc/variables/article.rst:1 msgid "" -"After you added a certificate, you can see a table with information for each " -"added certificate:" +"``Joe Doe `` may differ, depends on ``FROM`` of send mail" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing table of added certificates" +#: ../misc/variables/article.rst:1 +msgid "Article > Sender > Name" msgstr "" -#: ../settings/security/ssl-certificates.rst:64 -msgid "" -"Here you can download the certificate or delete it, if you don't need it " -"anymore." +#: ../misc/variables/article.rst:1 +msgid "``#{article.sender.name}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:68 -msgid "Deleting Certificates" +#: ../misc/variables/article.rst:1 +msgid "``Customer``, ``Agent`` or ``System``" msgstr "" -#: ../settings/security/ssl-certificates.rst:70 -msgid "" -"If you want to delete a specific certificate, you can do it by clicking on " -"the menu in the actions column and selecting delete:" +#: ../misc/variables/article.rst:1 +msgid "Article > Subject" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate deletion button" +#: ../misc/variables/article.rst:1 +msgid "``#{article.subject}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:79 -msgid "Downloading Certificates" +#: ../misc/variables/article.rst:1 +msgid "``My amazing subject``" msgstr "" -#: ../settings/security/ssl-certificates.rst:81 -msgid "" -"If you want to download your certificates, you can do this as well via " -"corresponding action buttons." +#: ../misc/variables/article.rst:1 +msgid "Article > Text" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate download button" +#: ../misc/variables/article.rst:1 +msgid "``#{article.body}``" msgstr "" -#: ../settings/security/third-party.rst:13 -msgid "Login Providers" +#: ../misc/variables/article.rst:1 +msgid "``Test`` without formatting (plain)" msgstr "" -#: ../settings/security/third-party.rst:2 -msgid "Third-Party Applications" +#: ../misc/variables/article.rst:1 +msgid "Article > TicketID" msgstr "" -#: ../settings/security/third-party.rst:4 -msgid "" -"Third party authentication is a great way to help your users to login to " -"Zammad more easily. If the account is yet unknown, Zammad will create a new " -"user automatically, without the user needed to interact (e.g. type in his " -"name). Another big advantage of this feature is that your user doesn't need " -"to remember another password." +#: ../misc/variables/article.rst:1 +msgid "``#{article.ticket_id}``" msgstr "" -#: ../settings/security/third-party.rst:10 -msgid "" -"You can deactivate logging in via :ref:`security_password_login` if any of " -"the mentioned authentication providers are enabled in your instance." +#: ../misc/variables/article.rst:1 +msgid "``1`` (not ticket number)" msgstr "" -#: ../settings/security/third-party.rst:27 -msgid "" -"We're currently missing documentation for the following login providers:" +#: ../misc/variables/article.rst:1 +msgid "Article > To" msgstr "" -#: ../settings/security/third-party.rst:29 -msgid "LinkedIn" +#: ../misc/variables/article.rst:1 +msgid "``#{article.to}``" msgstr "" -#: ../settings/security/third-party.rst:30 -msgid "Weibo" +#: ../misc/variables/article.rst:1 +msgid "``helpdesk@example.com``" msgstr "" -#: ../settings/security/third-party.rst:35 -msgid "Automatic Account Link on Initial Logon" +#: ../misc/variables/article.rst:1 +msgid "Article > Type > Name" msgstr "" -#: ../settings/security/third-party.rst:37 -msgid "" -"In general there's two possible options for Zammad on how to deal with " -"already known users as they try to authenticate against a third-party " -"application. By default, Zammad will not automatically link \"unknown\" " -"authentication providers to existing accounts." +#: ../misc/variables/article.rst:1 +msgid "``#{article.type.name}``" msgstr "" -#: ../settings/security/third-party.rst:42 +#: ../misc/variables/article.rst:1 msgid "" -"This means that the user has to manually link authentication providers to " -"their accounts (for more about this :user-docs:`consult the user " -"documentation `)." +"``email`` (`list of article types `_)" msgstr "" -#: ../settings/security/third-party.rst:46 -msgid "" -"Sometimes this doesn't come in handy as this also means you'll receive error " -"messages about \"email address being in use already\" for (yet) unknown " -"third-party authentication methods." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Address" msgstr "" -#: ../settings/security/third-party.rst:50 -msgid "" -"If you want to allow your users to always be able to log in, no matter what, " -"you may want to enable ``Automatic account link on initial logon``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.address}``" msgstr "" -#: ../settings/security/third-party.rst:None -msgid "" -"Screenshot highlighting the \"Automatic account link on initial logon\"\n" -"setting" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Department" msgstr "" -#: ../settings/security/third-party.rst:60 -msgid "Automatic Account Linking Notification" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.department}``" msgstr "" -#: ../settings/security/third-party.rst:64 -msgid "" -"To improve security and your users awareness, you can enable Zammad to " -"notify your users when a new third-party application has been linked to " -"their account." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Email" msgstr "" -#: ../settings/security/third-party.rst:68 -msgid "" -"This notification is sent out once per third-party application. Zammad does " -"also mention the method used, e.g.: ``Microsoft``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.email}``" msgstr "" -#: ../settings/security/third-party.rst:71 -msgid "By default this setting is not active (set to ``no``)." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Fax" msgstr "" -#: ../settings/security/third-party.rst:0 -msgid "" -"Screenshot showing sample notification mail after initial\n" -"third-party linking" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.fax}``" msgstr "" -#: ../settings/security/third-party.rst:85 -msgid "" -"This notification is only sent if the account in question already exists. If " -"the login via the third-party also creates the missing account, the " -"notification will be skipped." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Firstname" msgstr "" -#: ../settings/security/third-party.rst:89 -msgid "This means it only affects:" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.firstname}``" msgstr "" -#: ../settings/security/third-party.rst:91 -msgid "manual account linking within the third-party page of the users profile" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Lastname" msgstr "" -#: ../settings/security/third-party.rst:92 -msgid "" -"logging into an existing local account by utilizing the *automatic account " -"link on initial logon* functionality" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.lastname}``" msgstr "" -#: ../settings/security/third-party.rst:None -msgid "" -"Screenshot showing the \"automatic account linking notification\"\n" -"setting" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Login" msgstr "" -#: ../settings/security/third-party.rst:100 -msgid "No User Creation on Logon" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.login}``" msgstr "" -#: ../settings/security/third-party.rst:102 -msgid "" -"By default, Zammad will create a new user account if the user logs in via a " -"third-party application and the account doesn't exist yet." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Mobile" msgstr "" -#: ../settings/security/third-party.rst:105 -msgid "" -"If you want to prevent Zammad from creating new accounts on logon, you can " -"disable this feature by setting ``No user creation on logon`` to ``yes``." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.mobile}``" msgstr "" -#: ../settings/security/third-party.rst:None -msgid "Screenshot showing the \"no user creation on logon\" setting" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Note" msgstr "" -#: ../settings/security/third-party/facebook.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via Facebook To do " -"so, you need to follow these steps:" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.note}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:9 -msgid "Register Facebook App" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Phone" msgstr "" -#: ../settings/security/third-party/facebook.rst:11 -msgid "" -"Visit [https://developers.facebook.com/apps/] and click on \"Add a new App\"" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.phone}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "initial page" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > VIP" msgstr "" -#: ../settings/security/third-party/facebook.rst:17 -msgid "After that enter the app settings" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.vip}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "Create App" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Web" msgstr "" -#: ../settings/security/third-party/facebook.rst:22 -msgid "Navigate to \"Settings\" and fill in this infromation" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.web}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "App Settings" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated" msgstr "" -#: ../settings/security/third-party/facebook.rst:27 -msgid "Navigate to app review and Check \"Make [appname] public?\"" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_at}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "App Review" +#: ../misc/variables/article.rst:1 +msgid "Article > Visibility" msgstr "" -#: ../settings/security/third-party/facebook.rst:35 -msgid "Configure Zammad as Facebook App" +#: ../misc/variables/article.rst:1 +msgid "``#{article.internal}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:37 -msgid "" -"Navigate to \"Admin -> Security -> Third Party Applications\" and enter the " -"App ID and the App Secret. You can find this Key in the Dashbard of your " -"Facebok app." +#: ../misc/variables/article.rst:1 +msgid "``false`` or ``true`` (false if not internal)" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "Zammad Configuration" +#: ../misc/variables/article.rst:1 +msgid "Article Text as HTML (not referenced)" msgstr "" -#: ../settings/security/third-party/facebook.rst:44 -#: ../settings/security/third-party/github.rst:43 -#: ../settings/security/third-party/gitlab.rst:46 -msgid "" -"Now you can link accounts via \"Avatar -> Profile -> Link Accounts\" or " -"login via Zammad login page." +#: ../misc/variables/article.rst:1 +msgid "``#{article.body_as_html}``" msgstr "" -#: ../settings/security/third-party/github.rst:2 -#: ../system/integrations/github.rst:2 -msgid "GitHub" +#: ../misc/variables/article.rst:1 +msgid "``Test`` with formatting" msgstr "" -#: ../settings/security/third-party/github.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via GitHub. To " -"activate the quick login you need to enable OAuth for GitHub." +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "Ticket > Article#" msgstr "" -#: ../settings/security/third-party/github.rst:8 -msgid "Register GitHub App" +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "``#{ticket.article_count}``" msgstr "" -#: ../settings/security/third-party/github.rst:10 -msgid "" -"Visit https://www.github.com/settings/applications/new and enter the app " -"settings. As callback URL enter \"https://zammad_host/auth/github/callback\" " -"where zammad_host has to be replaced with your Zammad FQDN" +#: ../misc/variables/article.rst:1 +msgid "``1`` number of ticket articles" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "Register OAuth app on www.github.com" +#: ../misc/variables/config.rst:2 +msgid "Config" msgstr "" -#: ../settings/security/third-party/github.rst:19 -msgid "Configure Zammad as GitHub App" +#: ../misc/variables/config.rst:6 +msgid "" +"Below you'll find config related variables. These hold useful configuration " +"information that you can use within e.g. triggers to show necessary " +"information to your customer." msgstr "" -#: ../settings/security/third-party/github.rst:21 -msgid "" -"Enter the \"APP ID\" and the \"APP SECRET\" from the GitHub OAUTH " -"Applications Dashboard" +#: ../misc/variables/config.rst:11 +msgid "Config Variables" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub config in Zammad admin interface" +#: ../misc/variables/config.rst:1 +msgid "Config > Fully Qualified Domain Name" msgstr "" -#: ../settings/security/third-party/github.rst:28 -msgid "" -"After you configured the GitHub credentials and activated the login method, " -"you should see a new icon on the login page." +#: ../misc/variables/config.rst:1 +msgid "``#{config.fqdn}``" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub logo on login page" +#: ../misc/variables/config.rst:1 +msgid "``zammad.example.com``" msgstr "" -#: ../settings/security/third-party/github.rst:34 -msgid "" -"If you click on the icon you will be redirected to GitHub and see something " -"similar to this:" +#: ../misc/variables/config.rst:1 +msgid "Config > HTTP type" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub oauth page" +#: ../misc/variables/config.rst:1 +msgid "``#{config.http_type}``" msgstr "" -#: ../settings/security/third-party/github.rst:40 -#: ../settings/security/third-party/gitlab.rst:42 -msgid "" -"When you grant the access you will be redirected to your Zammad instance and " -"logged in as a customer." +#: ../misc/variables/config.rst:1 +msgid "``https`` or ``http``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:2 -msgid "Gitlab" +#: ../misc/variables/config.rst:1 +msgid "Config > Organization" msgstr "" -#: ../settings/security/third-party/gitlab.rst:4 +#: ../misc/variables/config.rst:1 +msgid "``#{config.organization}``" +msgstr "" + +#: ../misc/variables/config.rst:1 msgid "" -"It is possible to create a quick login for your helpdesk via Gitlab. To " -"activate the quick login you need to enable OAuth for Gitlab." +"``Zammad GmbH`` value set in `Branding `_" msgstr "" -#: ../settings/security/third-party/gitlab.rst:8 -msgid "Register Gitlab App" +#: ../misc/variables/config.rst:1 +msgid "Config > Product Name" msgstr "" -#: ../settings/security/third-party/gitlab.rst:10 -msgid "To register an app in Gitlab open your profile and select applications." +#: ../misc/variables/config.rst:1 +msgid "``#{config.product_name}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:12 +#: ../misc/variables/config.rst:1 msgid "" -"As callback URL enter \"https://zammad-fqdn/auth/gitlab/callback\" where " -"zammad-fqdn has to be replaced with your Zammad FQDN" +"``Helpdesk`` value set in `Branding `_" msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Register OAuth app on gitlab instance" +#: ../misc/variables/config.rst:1 +msgid "Config > SystemID" msgstr "" -#: ../settings/security/third-party/gitlab.rst:18 -msgid "Just select *read_user* under scopes as in the screenshot and save it." +#: ../misc/variables/config.rst:1 +msgid "``#{config.system_id}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:21 -msgid "Configure Zammad as Gitlab App" +#: ../misc/variables/config.rst:1 +msgid "``31`` (value between 1 and 99)" msgstr "" -#: ../settings/security/third-party/gitlab.rst:23 -msgid "" -"Enter the \"APP ID\" and the \"APP SECRET\" from the Gitlab OAUTH " -"Applications Dashboard and your Gitlab-URL in the \"SITE\" field." +#: ../misc/variables/config.rst:1 +msgid "Config > Ticket Hook" msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab config in Zammad admin interface" +#: ../misc/variables/config.rst:1 +msgid "``#{config.ticket_hook}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:30 -msgid "" -"After you configured the Gitlab credentials and activated the login method, " -"you should see a new icon on the login page." +#: ../misc/variables/config.rst:1 +msgid "``Ticket#``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab logo on login page" +#: ../misc/variables/current-user.rst:2 +msgid "Current User" msgstr "" -#: ../settings/security/third-party/gitlab.rst:36 +#: ../misc/variables/current-user.rst:6 msgid "" -"If you click on the icon you will be redirected to Gitlab and see something " -"similar to this:" +"Current user variables always return values of the current user that caused " +"e.g. a trigger to run." msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab oauth page" +#: ../misc/variables/current-user.rst:8 +msgid "" +"Due to the above fact, these variables are often not (yet) set or available " +"for usage." msgstr "" -#: ../settings/security/third-party/google.rst:4 +#: ../misc/variables/current-user.rst:10 msgid "" -"With some easy and fast steps, you can enable Zammad to authenticate your " -"users via Google." +"In situations where e.g. schedulers or triggers run, this most likely is " +"nothing you want to use." msgstr "" -#: ../settings/security/third-party/google.rst:8 -msgid "Register a Google App" +#: ../misc/variables/current-user.rst:13 +msgid "Current User Variables" msgstr "" -#: ../settings/security/third-party/google.rst:10 -msgid "" -"First of all, we need to create a new project - you can skip this step if " -"you already have one." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Address" msgstr "" -#: ../settings/security/third-party/google.rst:15 -msgid "" -"Use this link to create a new project: https://console.cloud.google.com/" -"projectcreate" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.address}``" msgstr "" -#: ../settings/security/third-party/google.rst:18 -msgid "" -"Now expand the menu, expand \"APIs & Services\" and select \"Credentials\". " -"Go to the tab \"OAuth consent screen\" first and ensure to fill in the " -"requested information - without doing so you can't create credentials!" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set" msgstr "" -#: ../settings/security/third-party/google.rst:None -msgid "Creating a consent screen" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Avatar" msgstr "" -#: ../settings/security/third-party/google.rst:25 -msgid "" -"After filling in and saving the consent screen information, you can go to " -"the \"Credentials\" tab and create new \"OAuth client ID\"-Credentials." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/google.rst:28 -msgid "" -"Fill in the necessary information as follows and replace ``zammad_host`` " -"with your FQDN:" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "avatar picture with width and height in pixel (e.g. 60,60)" msgstr "" -#: ../settings/security/third-party/google.rst:31 -msgid "**Application type** ``[x] Web application``" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created at" msgstr "" -#: ../settings/security/third-party/google.rst:34 -msgid "**Authorized JavaScript origins** ``https://zammad_host/``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_at}``" msgstr "" -#: ../settings/security/third-party/google.rst:37 -msgid "" -"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" -"callback``" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC``" msgstr "" -#: ../settings/security/third-party/google.rst:None -msgid "Adding a new OAuth client ID" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Address" msgstr "" -#: ../settings/security/third-party/google.rst:43 -msgid "" -"After creating the credentials, go to your Zammad installation and navigate " -"to \"Admin > Security > Third Party Applications\" > Google. Enter your " -"Client ID and Client secret here." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.address}``" msgstr "" -#: ../settings/security/third-party/google.rst:None -msgid "Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Avatar" msgstr "" -#: ../settings/security/third-party/google.rst:50 -msgid "After submitting, the login via Google can be used." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:2 -msgid "Microsoft" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Department" msgstr "" -#: ../settings/security/third-party/microsoft.rst:4 -msgid "" -"Zammad's Microsoft connection allows your users with Microsoft accounts to " -"login. This works for Azure users as well and can be an alternative to :doc:" -"`/system/integrations/ldap/index`." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.department}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:10 -msgid "" -"This documentation part does not cover our :doc:`📧 Microsoft 365 email " -"channel `." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Sales`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screenshot showing Microsoft login button on Zammad login screen." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Email" msgstr "" -#: ../settings/security/third-party/microsoft.rst:30 -#: ../settings/security/third-party/microsoft.rst:53 -msgid "Supported account types:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.email}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:22 -msgid "" -"Please note that Zammad only supports these account types (App dependent):" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``jdoe@customer.tld``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:35 -msgid "Avatars of signing in users:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Fax" msgstr "" -#: ../settings/security/third-party/microsoft.rst:33 -msgid "" -"Zammad currently ignores user avatars. If the user is registered with e.g. " -"Gravatar, Zammad will fetch the avatar from there if enabled. See :doc:" -"`Zammad Image Service ` for more." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.fax}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:38 -msgid "Step 1 - Register a Microsoft App for Zammad" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``004930123464789`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:40 -msgid "" -"Login to the `Microsoft Azure Portal `_ and " -"navigate to App registrations to create a new app. Provide the requested " -"information as follows and register your app." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Firstname" msgstr "" -#: ../settings/security/third-party/microsoft.rst:46 -msgid "Name:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.firstname}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:45 -msgid "" -"Any meaningful name fitting, this name will be displayed to users trying to " -"authenticate with this app." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``John`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:49 -msgid "Choose one of the above mentioned account types (see Limitations)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Lastname" msgstr "" -#: ../settings/security/third-party/microsoft.rst:51 -msgid "" -"The correct account type depends on your use case. If you want to use the " -"authentication internal only, choose the first option. If you're unsure, use " -"the \"Help me choose...\" link." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.lastname}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:58 -msgid "Redirect URI (optional):" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Login" msgstr "" -#: ../settings/security/third-party/microsoft.rst:56 -msgid "" -"Select web and provide your callback URL. The callback URL looks like this: " -"``https://zammad.domain.tld/auth/microsoft_office365/callback``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.login}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to register a Microsoft app" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Mobile" msgstr "" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "Within **API permissions** add the following permissions:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.mobile}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:69 -msgid "``User.Read``" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``0049176123456789`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "Contacts" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Note" msgstr "" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "``Contacts.Read``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.note}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:73 -msgid "" -"You can find these permissions within *Microsoft Graph → Delegated " -"permissions*." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Some note to this user`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to add required API permissions" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Phone" msgstr "" -#: ../settings/security/third-party/microsoft.rst:80 -msgid "" -"Within **Certificates & secrets** create a new client secret. Note down the " -"returned secret **value** for later. **Do not** use the secret ID!" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.phone}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to create a new app secret" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``004930123456789`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:88 -msgid "" -"From **Overview** copy your apps *Application (client) ID*. If you're using " -"a single tenant app, please also copy *Directory (tenant) ID*. You now have " -"all required information for Zammad." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > VIP" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to retreive application client and tenant IDs" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.vip}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:98 -msgid "Step 2 - Add App Credentials to Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Web" msgstr "" -#: ../settings/security/third-party/microsoft.rst:100 -msgid "" -"Navigate to Security > Third-party Applications (Tab) within Zammad's admin " -"settings. Scroll down to the section *Authentication via Microsoft* and fill " -"in the required information." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.web}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:105 -msgid "App ID:" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``https://zammad.org`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:105 -msgid "This is your *Application (client) ID*." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Department" msgstr "" -#: ../settings/security/third-party/microsoft.rst:108 -msgid "App secret:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.department}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:108 -msgid "This is your *client secret* (value)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Email" msgstr "" -#: ../settings/security/third-party/microsoft.rst:113 -msgid "App Tenant ID:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.email}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:111 -msgid "" -"**optional** only required for apps that use account type *Accounts in this " -"organizational directory only (Default Directory only - Single tenant).*" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Fax" msgstr "" -#: ../settings/security/third-party/microsoft.rst:115 -msgid "" -"Apply your settings by pressing submit and activate *Authentication via " -"Microsoft*." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.fax}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "" -"Screencast showing how to add app credentials and activating the\n" -"authentication method" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Firstname" msgstr "" -#: ../settings/security/third-party/saml.rst:2 -msgid "SAML" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.firstname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:4 -msgid "" -"Connect your SAML (Security Assertion Markup Language) identity provider as " -"a single sign-on (SSO) method." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Lastname" msgstr "" -#: ../settings/security/third-party/saml.rst:7 -msgid "" -"SAML is an open standard for SSO authentication (among other things). Sign-" -"ins are shared across multiple **service providers** and managed by a " -"central **identity provider** (IdP)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.lastname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:11 -msgid "" -"In this case, the service provider is Zammad, and the IdP is a software " -"service that you either host or subscribe to (*e.g.,* `Keycloak `_, `Redhat SSO Server `_, `ADFS `_, or `Okta `_)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Login" msgstr "" -#: ../settings/security/third-party/saml.rst:18 -msgid "" -"This guide assumes you are already using SAML within your organization (i." -"e., that your IdP is fully set up)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.login}``" msgstr "" -#: ../settings/security/third-party/saml.rst:21 -msgid "" -"Please note: Our instructions are based on connecting Zammad with Keycloak." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Mobile" msgstr "" -#: ../settings/security/third-party/saml.rst:25 -msgid "Step 1: Configure Your IdP" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.mobile}``" msgstr "" -#: ../settings/security/third-party/saml.rst:28 -msgid "Add Zammad as a Client/App" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Note" msgstr "" -#: ../settings/security/third-party/saml.rst:30 -msgid "" -"Import Zammad into your IdP using the XML configuration found at ``https://" -"your.zammad.domain/auth/saml/metadata``." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.note}``" msgstr "" -#: ../settings/security/third-party/saml.rst:33 -msgid "" -"If your IdP doesn't support XML import, you will have to configure Zammad as " -"a new client/app manually using the above XML metadata file for reference." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Domain based assignment" msgstr "" -#: ../settings/security/third-party/saml.rst:36 -msgid "For instance, when you see this tag:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.domain_assignment}``" msgstr "" -#: ../settings/security/third-party/saml.rst:42 -msgid "" -"Set the **Assertion Consumer Service Binding URL** (sometimes also listed as " -"**Valid Redirect URIs**) to ``http://your.zammad.domain/auth/saml/callback``." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Domain" msgstr "" -#: ../settings/security/third-party/saml.rst:47 -msgid "Set Up User Attribute Mapping" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.domain}``" msgstr "" -#: ../settings/security/third-party/saml.rst:49 -msgid "" -"Zammad requests the following user attributes (or “properties”) from the IdP:" +#: ../misc/variables/current-user.rst:1 +msgid "``zammad.com`` or empty if not set" msgstr "" -#: ../settings/security/third-party/saml.rst:51 -msgid "Email address (``email``)" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Name" msgstr "" -#: ../settings/security/third-party/saml.rst:52 -msgid "Full name (``name``)" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.name}``" msgstr "" -#: ../settings/security/third-party/saml.rst:53 -msgid "Given name (``first_name``)" +#: ../misc/variables/current-user.rst:1 +msgid "``Zammad GmbH``" msgstr "" -#: ../settings/security/third-party/saml.rst:54 -msgid "Family name (``last_name``)" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Note" msgstr "" -#: ../settings/security/third-party/saml.rst:56 -msgid "" -"You may need to set up “mappers” (or “mappings”) to tell your IdP how user " -"attributes in SAML correspond to those in Zammad. For a more detailed " -"breakdown, refer to the XML metadata file referenced in the previous section." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.note}``" msgstr "" -#: ../settings/security/third-party/saml.rst:62 -msgid "Per-IdP Instructions" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``A note to the organization of the user`` or empty if not set" msgstr "" -#: ../settings/security/third-party/saml.rst:102 -msgid "Keycloak" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Shared organization" msgstr "" -#: ../settings/security/third-party/saml.rst:65 -msgid "" -"**To add Zammad as a client,** save the XML configuration to disk (``https://" -"your.zammad.domain/auth/saml/metadata``) and use **Clients > Clients list > " -"Import client** in the Keycloak admin panel." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.shared}``" msgstr "" -#: ../settings/security/third-party/saml.rst:70 -msgid "" -"To help Zammad **match its own user accounts to Keycloak users**, create a " -"user attribute (or “property”) mapper. In **Clients list**, click on your " -"newly created Client ID, choose the tab **Client scopes** and click on the " -"link which refers to your Zammad instance. Choose **Add mapper > By " -"configuration > User Property** and create a mapper with the following " -"entries:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > VIP" msgstr "" -#: ../settings/security/third-party/saml.rst:78 -msgid "**Name**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.vip}``" msgstr "" -#: ../settings/security/third-party/saml.rst:80 -msgid "**Mapper Type**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Phone" msgstr "" -#: ../settings/security/third-party/saml.rst:81 -msgid "``User Property``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.phone}``" msgstr "" -#: ../settings/security/third-party/saml.rst:82 -msgid "**Property**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated at" msgstr "" -#: ../settings/security/third-party/saml.rst:83 -msgid "``emailAddress``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_at}``" msgstr "" -#: ../settings/security/third-party/saml.rst:84 -msgid "**SAML Attribute Name**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Address" msgstr "" -#: ../settings/security/third-party/saml.rst:86 -msgid "**SAML Attribute NameFormat**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.address}``" msgstr "" -#: ../settings/security/third-party/saml.rst:87 -msgid "``basic``" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Avatar" msgstr "" -#: ../settings/security/third-party/saml.rst:89 -msgid "" -"In the example above, we're telling Zammad that whenever it receives a SAML " -"login request, it should take the ``email`` property from Keycloak, look for " -"a Zammad user with the same ``email`` attribute, and create a new session " -"for that user." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/saml.rst:95 -msgid "" -"If your Keycloak users' email addresses are stored on another property (*e." -"g.,* ``username``), adjust accordingly." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Department" msgstr "" -#: ../settings/security/third-party/saml.rst:98 -msgid "" -"Back in **Settings**, enter the Client ID (``https://your.zammad.domain/auth/" -"saml/metadata``) in the field **Master SAML Processing URL**." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.department}``" msgstr "" -#: ../settings/security/third-party/saml.rst:101 -msgid "You also need to enable **Sign assertions**." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Email" msgstr "" -#: ../settings/security/third-party/saml.rst:105 -msgid "Step 2: Configure Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.email}``" msgstr "" -#: ../settings/security/third-party/saml.rst:107 -msgid "" -"Enable SAML and enter your IdP's details in the Admin Panel under **Settings " -"> Security > Third Party Applications > Authentication via SAML**:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Fax" msgstr "" -#: ../settings/security/third-party/saml.rst:None -msgid "Example configuration of SAML part 1" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.fax}``" msgstr "" -#: ../settings/security/third-party/saml.rst:119 -msgid "Display name" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Firstname" msgstr "" -#: ../settings/security/third-party/saml.rst:116 -msgid "" -"Allows you to define a custom button name for SAML. This helps your users to " -"understand better what the button on the login page does." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.firstname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:119 -msgid "Defaults to ``SAML``." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Lastname" msgstr "" -#: ../settings/security/third-party/saml.rst:123 -msgid "IDP SSO target URL" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.lastname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:122 -msgid "" -"This is the target URL Zammad shall redirect to when the user presses the " -"SAML button. For Keycloak, this needs to look like https://your.domain/" -"realms/your-realm/protocol/saml" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Login" msgstr "" -#: ../settings/security/third-party/saml.rst:127 -msgid "IDP single logout target URL" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.login}``" msgstr "" -#: ../settings/security/third-party/saml.rst:126 -msgid "" -"This is the URL to which the single logout request and response should be " -"sent." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Mobile" msgstr "" -#: ../settings/security/third-party/saml.rst:131 -msgid "IDP certificate" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.mobile}``" msgstr "" -#: ../settings/security/third-party/saml.rst:130 -msgid "" -"The public certificate of your IDP for Zammad to verify during the callback " -"phase." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Note" msgstr "" -#: ../settings/security/third-party/saml.rst:145 -msgid "IDP certificate fingerprint" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.note}``" msgstr "" -#: ../settings/security/third-party/saml.rst:134 -msgid "" -"The fingerprint of your IDPs public certificate to verify during callback " -"phase." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Phone" msgstr "" -#: ../settings/security/third-party/saml.rst:137 -msgid "🔏 **For the IdP certificate / certificate fingerprint:**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.phone}``" msgstr "" -#: ../settings/security/third-party/saml.rst:139 -msgid "" -"Provide **only one or the other**—do not provide both! (Between the two, we " -"recommend the signing certificate itself: fingerprints use SHA-1, which `has " -"been broken for a while now `_.)" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > VIP" msgstr "" -#: ../settings/security/third-party/saml.rst:144 -msgid "" -"**Keycloak users:** Find your certificate in the Keycloak admin panel under " -"**Realm Settings > Keys > Algorithm: RS256 > Certificate**." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.vip}``" msgstr "" -#: ../settings/security/third-party/saml.rst:151 -msgid "Name identifier format" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``false`` or ``true``" msgstr "" -#: ../settings/security/third-party/saml.rst:148 -msgid "" -"This is the unique identifiers field type. Usually it should be ``urn:oasis:" -"names:tc:SAML:1.1:nameid-format:emailAddress``." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Web" msgstr "" -#: ../settings/security/third-party/saml.rst:151 -msgid "Zammad **expects an email address as unique identifier**!" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.web}``" msgstr "" -#: ../settings/security/third-party/saml.rst:155 -msgid "UID attribute name" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > VIP" msgstr "" -#: ../settings/security/third-party/saml.rst:154 -msgid "" -"Here you can define an attribute that uniquely identifies the user. If " -"unset, the name identifier returned by the IDP is used." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.vip}``" msgstr "" -#: ../settings/security/third-party/saml.rst:None -msgid "Example configuration of SAML part 2" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Web" msgstr "" -#: ../settings/security/third-party/saml.rst:163 -msgid "" -"Decide if the certificate for the connection to the IdP service has to be " -"verified or not (default: ``yes``)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.web}``" msgstr "" -#: ../settings/security/third-party/saml.rst:169 -msgid "Signing & Encrypting" +#: ../misc/variables/ticket.rst:6 +msgid "" +"Below you can find all available ticket-based variables within Zammad. These " +"can be called via triggers for example. If you're unsure if Zammad does " +"support variables at the point you're at, you can try to type ``::`` to " +"check." msgstr "" -#: ../settings/security/third-party/saml.rst:169 -msgid "" -"Define if you want to sign, encrypt, do both or nothing for the requests." +#: ../misc/variables/ticket.rst:12 +msgid "Ticket Variables" msgstr "" -#: ../settings/security/third-party/saml.rst:179 -msgid "Certificate (PEM)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Accounted Time" msgstr "" -#: ../settings/security/third-party/saml.rst:172 -msgid "" -"Paste the public certificate of your Zammad SAML client, if you want to " -"encrypt the requests." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.time_unit}``" msgstr "" -#: ../settings/security/third-party/saml.rst:175 -msgid "Make sure the certificate is:" +#: ../misc/variables/ticket.rst:1 +msgid "``1``, ``2.75`` or empty response" msgstr "" -#: ../settings/security/third-party/saml.rst:177 -msgid "already valid and not yet expired" +#: ../misc/variables/ticket.rst:1 +msgid "``3``, any number of articles existing in the ticket right now" msgstr "" -#: ../settings/security/third-party/saml.rst:178 -msgid "no CA certificate" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Closing time" msgstr "" -#: ../settings/security/third-party/saml.rst:179 -msgid "valid for signing and encrypting" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.close_at}``" msgstr "" -#: ../settings/security/third-party/saml.rst:185 -msgid "Private key (PEM)" +#: ../misc/variables/ticket.rst:1 +msgid "2019-10-07 17:25:00 UTC" msgstr "" -#: ../settings/security/third-party/saml.rst:182 -msgid "" -"Paste the private key of your Zammad SAML client here, if you want to sign " -"the requests." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created at" msgstr "" -#: ../settings/security/third-party/saml.rst:185 -msgid "Make sure the key is an RSA key with a length of at least 2048 bits." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_at}``" msgstr "" -#: ../settings/security/third-party/saml.rst:188 -msgid "Private key secret" +#: ../misc/variables/ticket.rst:1 +msgid "2019-10-07 16:25:00 UTC" msgstr "" -#: ../settings/security/third-party/saml.rst:188 -msgid "If your private key is secured with a secret, you can provide it here." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Address" msgstr "" -#: ../settings/security/third-party/saml.rst:192 -msgid "Your callback URL" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.address}``" msgstr "" -#: ../settings/security/third-party/saml.rst:191 -msgid "" -"This URL is needed for your IdP configuration so it knows where to redirect " -"to after successful authentication." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Avatar" msgstr "" -#: ../settings/security/third-party/saml.rst:194 -msgid "" -"After saving your input by clicking on the \"Submit\" button, Zammad " -"verifies the provided keys/certificates (e.g. if they are valid for signing/" -"encrypting and if they aren't expired)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/saml.rst:199 -msgid "" -"See :ref:`automatic account linking ` for details " -"on how to link existing Zammad accounts to IdP accounts." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Department" msgstr "" -#: ../settings/security/third-party/saml.rst:205 -msgid "Automatic account linking doesn't work" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.department}``" msgstr "" -#: ../settings/security/third-party/saml.rst:206 -msgid "" -"Have you double-checked your IdP's user attribute mapping configuration?" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Email" msgstr "" -#: ../settings/security/third-party/twitter.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via Twitter. To do " -"so, you need to follow these steps:" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.email}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:8 -msgid "Register Twitter App" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Fax" msgstr "" -#: ../settings/security/third-party/twitter.rst:10 -msgid "Go to https://dev.twitter.com/apps and login with your account." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.fax}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:15 -msgid "Click on \"Create App\"" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Firstname" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "new app page" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.firstname}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:20 -msgid "" -"Enter app settings. As \"Callback URL\" you need to enter ``https://" -"zammad_host/api/v1/external_credentials/twitter/callback``. You need to " -"replace ``zammad_host`` with the domain of your Zammad system." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Lastname" msgstr "" -#: ../settings/security/third-party/twitter.rst:24 -msgid "" -"After the app has been created, update the application icon and organization " -"attributes." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.lastname}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "set permissions to receive and send direct messages" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Login" msgstr "" -#: ../settings/security/third-party/twitter.rst:30 -msgid "" -"Next we need to set ``read, write and access direct messages`` permissions " -"for the app." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.login}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "click on Keys & Access Token, note them" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Mobile" msgstr "" -#: ../settings/security/third-party/twitter.rst:36 -msgid "" -"Go to \"Keys and Access Token\" tab and note the \"Consumer Key\" and " -"\"Consumer Secret\"." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.mobile}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:40 -msgid "Configure Zammad as Twitter App" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Note" msgstr "" -#: ../settings/security/third-party/twitter.rst:42 -msgid "" -"Go to \"Admin > Security > Twitter > Third Party Applications > Twitter\" " -"Section." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.note}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "Admin > Security > Third Party Applications" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Phone" msgstr "" -#: ../settings/security/third-party/twitter.rst:48 -msgid "" -"Fill in the \"Twitter Key\" and the \"Twitter Secret\" and click the " -"\"Submit\" button." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.phone}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:51 -msgid "" -"Now you can link accounts via \"Avatar > Profile > Link Accounts\" or login " -"via Zammad login page." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > VIP" msgstr "" -#: ../settings/security/two-factor.rst:11 -msgid "Two-factor Authentication Methods" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.vip}``" msgstr "" -#: ../settings/security/two-factor.rst:2 -msgid "Two-Factor Authentication" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Web" msgstr "" -#: ../settings/security/two-factor.rst:4 -msgid "" -"Two-factor authentication (2FA) enhances the security of Zammad accounts by " -"adding an extra layer of verification beyond a password. It requires users " -"to provide two different types of authentication factors, typically " -"something they know (like a password) and something they possess (like a " -"mobile device or a security token), to ensure that only authorized " -"individuals can access the account." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.web}``" msgstr "" -#: ../settings/security/two-factor.rst:19 -msgid "Enable Recovery Codes" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Address" msgstr "" -#: ../settings/security/two-factor.rst:21 -msgid "" -"Recovery codes are one-time use security codes that can be used by the user " -"if they lose access to their other two-factor authentication methods. They " -"cannot be used on their own, they can only be activated if at least one two-" -"factor authentication method is enabled." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.address}``" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Enable Recovery Codes Setting" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Avatar" msgstr "" -#: ../settings/security/two-factor.rst:30 -msgid "" -"Recovery codes can only be used as a backup method. If enabled, they will be " -"automatically generated for the user once they set up their initial two-" -"factor authentication method." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.avatar(60,60)}``" msgstr "" -#: ../settings/security/two-factor.rst:34 -msgid "" -"The user will be asked to print out or save the generated recovery codes in " -"a safe place. Once used, a recovery code cannot be reused." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Department" msgstr "" -#: ../settings/security/two-factor.rst:37 -msgid "" -"Users will also have an option to regenerate their recovery codes at any " -"time, which invalidates already existing recovery codes and provides them " -"with a list of fresh codes." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.department}``" msgstr "" -#: ../settings/security/two-factor.rst:41 -msgid "" -"After you enable this setting, when the user completes a setup of their " -"initial two-factor authentication method, they will be presented with a list " -"of recovery codes and instructed to save them for later use." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Email" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Recovery Codes Generation Modal Dialog" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.email}``" msgstr "" -#: ../settings/security/two-factor.rst:50 -msgid "Enforce the Set Up of the Two-Factor Authentication" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Fax" msgstr "" -#: ../settings/security/two-factor.rst:52 -msgid "" -"In case you wish to require your users to set up at least one two-factor " -"authentication method for their account, you can do this by selecting " -"specific user roles the requirement applies to in **Enforced for user " -"roles** setting. Of course you must have at least one two-factor " -"authentication method enabled for this setting to take effect." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.fax}``" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Enforced for User Roles Setting" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Firstname" msgstr "" -#: ../settings/security/two-factor.rst:62 -msgid "" -"After you change this setting, if the user has one of the selected roles on " -"their account, they will be forced to set up the two-factor authentication " -"upon next sign in or application reload." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.firstname}``" msgstr "" -#: ../settings/security/two-factor.rst:66 -msgid "" -"A modal dialog with instructions will be shown, and they will not be able to " -"do any work before they set up at least one two-factor method." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Lastname" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Modal Dialog for Enforcing Two-Factor Authentication Set Up" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.lastname}``" msgstr "" -#: ../settings/security/two-factor.rst:74 -msgid "Reset Two-Factor Authentication for a Specific User" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Login" msgstr "" -#: ../settings/security/two-factor.rst:76 -msgid "" -"In case an user isn't able to login anymore because of an inaccessible " -"second factor, you can reset the user's 2FA method." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.login}``" msgstr "" -#: ../settings/security/two-factor.rst:79 -msgid "" -"To do this, go to the user management and search for the relevant user. " -"After you found the account, click the button in the action column and " -"select \"Manage Two-Factor Authentication\":" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Mobile" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Context menu in action column in user management" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.mobile}``" msgstr "" -#: ../settings/security/two-factor.rst:87 -msgid "" -"After selecting this, you can see a dialog where you can either reset one " -"2FA method or reset all of the user's 2FA methods:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Note" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Dialog for resetting user's 2FA method" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.note}``" msgstr "" -#: ../settings/security/two-factor.rst:94 -msgid "" -"Choose the fitting one, click on the corresponding \"Remove ...\" button and " -"confirm your action. The user now has to setup a new 2FA method, depending " -"on your 2FA configuration." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Phone" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:2 -msgid "Authenticator App" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.phone}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:4 -msgid "" -"The authenticator app method is a type of two-factor authentication that " -"uses a mobile application to generate one-time codes for account " -"verification. After setting up the authenticator app on their device, the " -"user links it to their Zammad account." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > VIP" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:12 -msgid "" -"When logging in, the user is prompted to enter a time-sensitive code " -"generated by the app, in addition to their password. This code acts as the " -"second factor of authentication, providing an extra layer of security as it " -"changes periodically and is unique to the user's device." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.vip}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:None -msgid "Security Code in Google Authenticator App" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Web" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:22 -msgid "" -"The app generates codes based on a shared secret key stored securely on both " -"the user's device and the server, ensuring a synchronized and secure " -"authentication process. The method of generating the codes is sometimes also " -"called TOTP (time-based one-time password)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.web}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:28 -msgid "Enabling the Authenticator App Method" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Escalation at" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:30 -#: ../settings/security/two-factor/security-keys.rst:28 -msgid "To enable the method, just toggle the switch on in the settings." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.escalation_at}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:None -msgid "Authenticator App Switch in Settings" +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:36 -msgid "" -"Now the users will be able to set up this two-factor authentication method " -"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " -"Once they do, on next sign-in with password, they will be asked to provide " -"an additional security code generated by their mobile device." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > First response" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:2 -msgid "Security Keys" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.first_response_at}``" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:4 -msgid "" -"The security keys method is a type of a two-factor authentication that uses " -"Web Authentication API in the browser for verifying user's identity. The " -"user can register multiple hardware or software security keys with their " -"Zammad account and then they can use it during the sign-in process." +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable yet" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:12 -msgid "" -"When logging in, the user is prompted to provide the same security key they " -"registered with their account, in addition to their password. This key acts " -"as the second factor of authentication, providing an extra layer of security." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Assign Follow-Ups" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:None -msgid "Security Key dialog in Safari on macOS" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_assignment}``" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:21 -msgid "" -"The type of the key can range from hardware USB sticks to passkeys stored in " -"a device of user's choice. Which type can be used depends on the browser " -"flavor and the platform of the user." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Assignment Timeout" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:26 -msgid "Enabling the Security Keys Method" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.assignment_timeout}``" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:None -msgid "Security Keys Switch in Settings" +#: ../misc/variables/ticket.rst:1 +msgid "``20`` or empty if not configured" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:34 -msgid "" -"Now the users will be able to set up this two-factor authentication method " -"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " -"Once they do, on next sign-in with password, they will be asked to provide " -"the same security key they registered during the setup." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Follow-up possible" msgstr "" -#: ../settings/system/system-selfhosted.include.rst:3 -msgid "" -"Below settings are only available to self hosted users. In hosted " -"environments we're handling these settings for you to ensure service " -"stability." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_possible}``" msgstr "" -#: ../settings/system/base.rst:11 -msgid "Fully Qualified Domain Name" +#: ../misc/variables/ticket.rst:1 +msgid "``no`` or ``yes``" msgstr "" -#: ../settings/system/base.rst:7 -msgid "The URL of your Zammad installation." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Name" msgstr "" -#: ../settings/system/base.rst:9 ../settings/system/base.rst:17 -msgid "This setting is used within :doc:`/system/variables` and notifications." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.name}``" msgstr "" -#: ../settings/system/system-base.include.rst:1 -msgid "It is automatically set by the *Getting Started wizard*." +#: ../misc/variables/ticket.rst:1 +msgid "``Sales``" msgstr "" -#: ../settings/system/system-base.include.rst:5 -msgid "Changing this setting also changes callback URLs for your channels etc." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Note" msgstr "" -#: ../settings/system/system-base.include.rst:6 -msgid "This setting can have negative affects on being able to login." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.note}``" msgstr "" -#: ../settings/system/base.rst:19 -msgid "HTTP type" +#: ../misc/variables/ticket.rst:1 +msgid "``Note about this group``" msgstr "" -#: ../settings/system/base.rst:14 -msgid "" -"The HTTP type tells your installation how your clients connect. This is " -"relevant for authentication and cookie security." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > ID" msgstr "" -#: ../settings/system/base.rst:31 -msgid "SystemID" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.id}``" msgstr "" -#: ../settings/system/base.rst:22 -msgid "" -"This ID is being used within your ticket number. In case you're " -"communicating with another ticket system with similar ticket number schemes " -"this ID greatly reduces the risk of false follow ups." +#: ../misc/variables/ticket.rst:1 +msgid "``17``, ``5281``, ..." msgstr "" -#: ../settings/system/base.rst:26 -msgid "" -"The SystemID is randomly selected upon installation of Zammad (``1-99``)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact (agent)" msgstr "" -#: ../settings/system/base.rst:30 -msgid "" -"**Do not** change this setting in a productive system! Your Zammad " -"installation may no longer recognize old ticket number based follow ups upon " -"change!" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_agent_at}``" msgstr "" -#: ../settings/system/frontend.rst:2 -msgid "Frontend" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact (customer)" msgstr "" -#: ../settings/system/frontend.rst:22 -msgid "Core Workflow Ajax Mode" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_customer_at}``" msgstr "" -#: ../settings/system/frontend.rst:6 +#: ../misc/variables/ticket.rst:1 msgid "" -"This setting allows administrators to enforce :doc:`/system/core-workflows` " -"to use Ajax-Calls instead of web sockets. You'll usually only need this if " -"you experience serious issues as noted below." +"``2019-10-07 16:25:00 UTC`` or empty if not applicable yet (Please note " +"`Ticket last contact behavior Settings `_ for this)" msgstr "" -#: ../settings/system/frontend.rst:10 -msgid "**🤓 Possible (technical) reasons**" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact" msgstr "" -#: ../settings/system/frontend.rst:12 -msgid "" -"In some cases, your network structure (e.g. firewalls, proxies) may " -"disconnect long web socket connections. This leads to select fields staying " -"empty (e.g. owner selection *after* selecting your group) or fields not " -"shown / hidden (e.g. when switching to or from pending states, the \"pending " -"till\" field not showing / hiding)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_at}``" msgstr "" -#: ../settings/system/frontend.rst:18 -msgid "" -"Please keep in mind that the Ajax fallback may cause serious pressure on " -"your application server. If you have the choice stick to web sockets." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Number" msgstr "" -#: ../settings/system/frontend.rst:22 -msgid "Default: ``no`` (inactive)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.number}``" msgstr "" -#: ../settings/system/frontend.rst:53 -msgid "Show calendar weeks in the picker of date/datetime fields" +#: ../misc/variables/ticket.rst:1 +msgid "``31001``, ``201910731001``, ..." msgstr "" -#: ../settings/system/frontend.rst:25 -msgid "" -"With this setting you can instruct Zammad to provide week number display " -"globally for all users. Calendar with week number display are usually used " -"in business sectors and may not be relevant for everyone." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain based assignment" msgstr "" -#: ../settings/system/frontend.rst:29 -msgid "" -"This setting affects *all areas* - you'll also see week numbers in the admin " -"panel for e.g. triggers and macros." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain_assignment}``" msgstr "" -#: ../settings/system/frontend.rst:32 -msgid "Default: ``no`` (not shown)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain" msgstr "" -#: ../settings/system/frontend.rst:53 -msgid "Here's the difference:" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain}``" msgstr "" -#: ../settings/system/frontend.rst:0 -msgid "Screenshot showing Zammad's date picker (in the default way)" +#: ../misc/variables/ticket.rst:1 +msgid "``domain.tld`` or empty if not set" msgstr "" -#: ../settings/system/frontend.rst:41 -msgid "Set to ``no``" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Name" msgstr "" -#: ../settings/system/frontend.rst:0 -msgid "" -"Screenshot showing Zammad's date picker with\n" -"week numbers enabled" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.name}``" msgstr "" -#: ../settings/system/frontend.rst:50 -msgid "Set to ``yes``" +#: ../misc/variables/ticket.rst:1 +msgid "``Zammad GmbH`` or empty if not set" msgstr "" -#: ../settings/system/index.rst:4 -msgid "" -"For your overview we split each tab within system settings into its own page:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Note" msgstr "" -#: ../settings/system/index.rst:16 -msgid "Console Based Settings" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.note}``" msgstr "" -#: ../settings/system/index.rst:18 -msgid "" -"There's some console based settings we didn't put into the UI. However, you " -"may find them helpful - you can find them in our :docs:`hidden settings ` section." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Shared organization" msgstr "" -#: ../settings/system/network.rst:2 -msgid "Network" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.shared}``" msgstr "" -#: ../settings/system/network.rst:8 -msgid "" -"The proxy settings can only be saved after successfully testing the proxy " -"connection." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > VIP" msgstr "" -#: ../settings/system/network.rst:15 -msgid "Proxy Address." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.vip}``" msgstr "" -#: ../settings/system/network.rst:12 -msgid "" -"Allows you to provide a proxy server if needed. This is relevant for network " -"communication by Zammad." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Address" msgstr "" -#: ../settings/system/network.rst:15 -msgid "It **does not** affect the update process or Elasticsearch." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.address}``" msgstr "" -#: ../settings/system/network.rst:18 -msgid "Username for proxy connection." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Avatar" msgstr "" -#: ../settings/system/network.rst:18 -msgid "" -"If your proxy server requires authentication, provide the username here." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.avatar(60,60)}``" msgstr "" -#: ../settings/system/network.rst:21 -msgid "Password for proxy connection." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Department" msgstr "" -#: ../settings/system/network.rst:21 -msgid "" -"If your proxy server requires authentication, provide the password here." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.department}``" msgstr "" -#: ../settings/system/network.rst:26 -msgid "No proxy for the following hosts." +#: ../misc/variables/ticket.rst:1 +msgid "``Support`` or empty if not set" msgstr "" -#: ../settings/system/network.rst:24 -msgid "" -"Exception list for hosts you can't or don't want to reach via proxy server." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Email" msgstr "" -#: ../settings/system/network.rst:27 -msgid "Default: ``localhost,127.0.0.0,::1``" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.email}``" msgstr "" -#: ../settings/system/services.rst:2 -msgid "Services" +#: ../misc/variables/ticket.rst:1 +msgid "``agent@company.tld`` or empty if not set" msgstr "" -#: ../settings/system/services.rst:10 -msgid "Image Service" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Fax" msgstr "" -#: ../settings/system/services.rst:5 -msgid "Defines the backend for user and organization image lookups." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.fax}``" msgstr "" -#: ../settings/system/services.rst:7 -msgid "Default: ``Zammad Image Service`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Firstname" msgstr "" -#: ../settings/system/services.rst:9 -msgid "" -"Make sure your on premise installation has ``HTTPS`` access to ``images." -"zammad.com``." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.firstname}``" msgstr "" -#: ../settings/system/services.rst:18 -msgid "Geo Calendar Service" +#: ../misc/variables/ticket.rst:1 +msgid "``Max`` or empty if not set" msgstr "" -#: ../settings/system/services.rst:13 -msgid "" -"Defines the backend for geo calendar lookups. Used for initial calendar " -"setup." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Lastname" msgstr "" -#: ../settings/system/services.rst:16 -msgid "Default: ``Zammad GeoCalendar Service`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.lastname}``" msgstr "" -#: ../settings/system/services.include.rst:2 -msgid "" -"Make sure your on premise installation has ``HTTPS`` access to ``geo.zammad." -"com``." +#: ../misc/variables/ticket.rst:1 +msgid "``Mustermann`` or empty if not set" msgstr "" -#: ../settings/system/services.rst:26 -msgid "Geo IP Service" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Login" msgstr "" -#: ../settings/system/services.rst:21 -msgid "" -"Defines the backend for geo IP lookups. Shows also location of an IP address " -"if an IP address is shown." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.login}``" msgstr "" -#: ../settings/system/services.rst:24 -msgid "Default: ``Zammad GeoIP Service`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "``agent``" msgstr "" -#: ../settings/system/services.rst:32 -msgid "Geo Location Service" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Mobile" msgstr "" -#: ../settings/system/services.rst:29 -msgid "" -"Defines the backend for geo location lookups to store geo locations for " -"addresses." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.mobile}``" msgstr "" -#: ../settings/system/services.rst:32 -msgid "" -"Default: ``OpenStreetMap (ODbL 1.0, http://osm.org/copyright)`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Note" msgstr "" -#: ../settings/system/services.rst:36 -msgid "" -"You can find a detailed privacy information on what we store for how long on " -"our :docs:`Privacy Appendix ` inside of our System " -"Documentation." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.note}``" msgstr "" -#: ../settings/system/storage.rst:2 -msgid "Storage" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Phone" msgstr "" -#: ../settings/system/storage.rst:6 -msgid "" -"Here you can define where Zammad stores attachments for tickets and the " -"knowledge base. By default, we're writing to the ``Database`` - you can " -"switch to ``Filesystem`` or ``Simple Storage (S3)`` at any time. In this " -"case please have a look on the following instructions." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.phone}``" msgstr "" -#: ../settings/system/storage.rst:11 -msgid "" -"If you have a busy Zammad instance, we strongly encourage you to use " -"filesystem storage instead of \"Database\". This will greatly improve system " -"performance (de-crease database load and size)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > VIP" msgstr "" -#: ../settings/system/storage.rst:19 -msgid "Database" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.vip}``" msgstr "" -#: ../settings/system/storage.rst:17 -msgid "" -"This is the default storage method. The attachments are stored directly in " -"the database. If your Zammad instance grows, we recommend one of the other " -"methods to maintain performance." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Web" msgstr "" -#: ../settings/system/storage.rst:38 -msgid "Filesystem" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.web}``" msgstr "" -#: ../settings/system/storage.rst:22 -msgid "" -"This storage method is recommended for all Zammad instances, especially for " -"those with a higher load. If you choose filesystem, your files are written " -"to ``/opt/zammad/storage/``." +#: ../misc/variables/ticket.rst:1 +msgid "``https://zammad.com`` or empty if not set" msgstr "" -#: ../settings/system/storage.rst:26 -msgid "" -"Moving attachments from \"Database\" to \"Filesystem\" can be run during " -"production use. However, you should consider your framework conditions (e.g. " -"bandwidth, system load in production) to define the right moment." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Pending till" msgstr "" -#: ../settings/system/storage.rst:32 -msgid "**You noticed slow updates of Zammad?**" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.pending_time}``" msgstr "" -#: ../settings/system/storage.rst:34 -msgid "" -"While Zammad is beeing updated, it enforces a recursive \"change " -"owner\" (chown) for this directory. For instances with many files this can " -"be time consuming. To mitigate that you can move your files and create a " -"symlink in ``/opt/zammad/storage/`` to the new directory. Of course you have " -"to make sure on your own that the permissions are always correct." +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not set" msgstr "" -#: ../settings/system/storage.rst:95 -msgid "Simple Storage (S3)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Priority > Name" msgstr "" -#: ../settings/system/storage.rst:41 -msgid "" -"To use the Simple Storage (S3), you have to provide some settings, which " -"can't be accessed in the UI (see instructions below)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.priority.name}``" msgstr "" -#: ../settings/system/storage.rst:44 -msgid "" -"⚠️ Please note that the current implementation is in its early stages and can " -"be modified in the future." +#: ../misc/variables/ticket.rst:1 +msgid "``2 normal``" msgstr "" -#: ../settings/system/storage.rst:47 -msgid "" -"The prerequisite is to have access to a S3-compatible storage and to have " -"all necessary parameters available (which depends on your storage provider; " -"if in doubt, please ask there for help)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > State > Name" msgstr "" -#: ../settings/system/storage.rst:51 -msgid "Steps to configure S3:" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.state.name}``" msgstr "" -#: ../settings/system/storage.rst:53 -msgid "" -"Copy ``config/zammad/storage.yml.dist`` to ``config/zammad/storage.yml``" +#: ../misc/variables/ticket.rst:1 +msgid "``new``, ``open``, ..." msgstr "" -#: ../settings/system/storage.rst:54 -msgid "Edit the copied file in one of the following ways:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Tags" msgstr "" -#: ../settings/system/storage.rst:56 -msgid "" -"Either provide your S3 configuration with one attribute per line like in the " -"upper area of the file" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.tags}``" msgstr "" -#: ../settings/system/storage.rst:58 +#: ../misc/variables/ticket.rst:1 msgid "" -"Or provide your S3 configuration as an URL (which you can find at the end of " -"the file). Note: you can also provide this URL as environment variable (:" -"docs:`see system documentation `) without using this yml-file." +"Currently not available, see `Issue 2769 `_" msgstr "" -#: ../settings/system/storage.rst:62 -msgid "" -"We recommend the deletion of the not used configuration style to avoid " -"inconsistencies." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Title" msgstr "" -#: ../settings/system/storage.rst:65 -msgid "Restart Zammad so the config file / environment variable is loaded" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.title}``" msgstr "" -#: ../settings/system/storage.rst:66 +#: ../misc/variables/ticket.rst:1 msgid "" -"Set the \"Storage Method\" in Zammad to ``Simple Storage (S3)`` in Settings " -"> System > Storage and click on \"Submit\". After that, Zammad checks your " -"configuration and the connection to the service and will raise an error " -"message if something is wrong." +"``My amazing Subject`` (normally subject, can be edited within Interface and " +"thus differ)" msgstr "" -#: ../settings/system/storage.rst:72 -msgid "A very simple storage configuration could look like this:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated at" msgstr "" -#: ../settings/system/storage.rst:85 -msgid "" -"Before setting the storage method to ``Simple Storage (S3)`` (step 4), " -"please make sure to have a working setup." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_at}``" msgstr "" -#: ../settings/system/storage.rst:88 -msgid "" -"You can verify this by running ``rails r 'Rails.logger = Logger.new(STDOUT); " -"pp Store::Provider::S3.ping?'`` in your Zammad directory. If everything is " -"fine, you should see ``true``, else you should see ``false`` and a simple " -"error message." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Address" msgstr "" -#: ../settings/system/storage.rst:93 -msgid "" -"If you installed Zammad through a package manager (rather than from source), " -"replace ``rails r`` with ``zammad run rails r`` above. To learn more, see :" -"docs:`Administration via Console `." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.address}``" msgstr "" -#: ../settings/ticket.rst:4 -msgid "" -"Here you can adjust general ticket settings. Additional ones for the ticket " -"composer interface can be found in the :doc:`/misc/composer`." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Avatar" msgstr "" -#: ../settings/ticket.rst:11 -msgid "Ticket Hook (default: ``Ticket#``)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.avatar(60,60)}``" msgstr "" -#: ../settings/ticket.rst:11 -msgid "The identifier for a ticket; *e.g.,* Ticket#, Call#, MyTicket#." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Department" msgstr "" -#: ../settings/ticket.rst:38 -msgid "Ticket Hook Position (default: ``right``)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.department}``" msgstr "" -#: ../settings/ticket.rst:14 -msgid "" -"With this setting you can decide (if) where to insert the ticket number." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Email" msgstr "" -#: ../settings/ticket.rst:20 -msgid "*Right*" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.email}``" msgstr "" -#: ../settings/ticket.rst:17 -msgid "" -"This setting will add the ticket reference on the right site of the subject." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Fax" msgstr "" -#: ../settings/ticket.rst:20 -msgid "Example: ``Some Subject [Ticket#12345]``" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.fax}``" msgstr "" -#: ../settings/ticket.rst:26 -msgid "*Left*" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Firstname" msgstr "" -#: ../settings/ticket.rst:23 -msgid "" -"This setting will add the ticket reference on the left site of the subject." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.firstname}``" msgstr "" -#: ../settings/ticket.rst:26 -msgid "Example: ``[Ticket#12345] Some Subject``" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Lastname" msgstr "" -#: ../settings/ticket.rst:29 -msgid "*None*" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.lastname}``" msgstr "" -#: ../settings/ticket.rst:29 -msgid "This will completely remove ticket references from the subject." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Login" msgstr "" -#: ../settings/ticket.rst:33 -msgid "" -"Please ensure to take a look at :doc:`/channels/email/settings` within the " -"email channel to ensure you have at least one reference that helps Zammad to " -"assign follow-ups correctly." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.login}``" msgstr "" -#: ../settings/ticket.rst:37 -msgid "" -"Disabling this and not setting up any further follow up search will lead to " -"unexpected results!" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Mobile" msgstr "" -#: ../settings/ticket.rst:65 -msgid "" -"Ticket Last Contact Behaviour (default: ``Use the start time of the last " -"customer thread (which may consist of multiple articles).``)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.mobile}``" msgstr "" -#: ../settings/ticket.rst:41 -msgid "" -"This setting changes the way Zammad updates the ``Last Contact`` value of a " -"ticket. This is fairly important for overviews and what you expect upon " -"ticket updates of a customer." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Note" msgstr "" -#: ../settings/ticket.rst:52 -msgid "" -"Use the start time of the last customer thread (which may consist of " -"multiple articles)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.note}``" msgstr "" -#: ../settings/ticket.rst:46 -msgid "" -"If this option is chosen, Zammad will update the last updated value just " -"once if a customer replies. After that, Zammad will wait for an agent to " -"react." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Phone" msgstr "" -#: ../settings/ticket.rst:50 -msgid "" -"This comes in handy if you want to work tickets in the order of their first " -"update. This will not change ticket orders if customers decide to \"bump\" " -"the ticket affected." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.phone}``" msgstr "" -#: ../settings/ticket.rst:57 -msgid "Use the time of the very last customer article." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > VIP" msgstr "" -#: ../settings/ticket.rst:55 -msgid "" -"When setting this option, Zammad will always update the last updated value. " -"This means that if ordering by ``Last Update``, ticket orders will change if " -"customers \"bump\" the ticket." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.vip}``" msgstr "" -#: ../settings/ticket.rst:64 -msgid "Last contact value used on :doc:`/manage/overviews`" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Web" msgstr "" -#: ../settings/ticket.rst:65 -msgid "Last contact value used on :doc:`/manage/trigger`" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.web}``" msgstr "" -#: ../settings/ticket.rst:88 -msgid "" -"Ticket Organization Reassignment (default: ``Update the most recent tickets." -"``)" +#: ../settings/branding.rst:10 +msgid "Product Name" msgstr "" -#: ../settings/ticket.rst:68 +#: ../settings/branding.rst:7 msgid "" -"This setting changes the way Zammad updates the organization field of the " -"tickets whenever the primary organization of a user is changed." -msgstr "" - -#: ../settings/ticket.rst:74 -msgid "Update the most recent tickets." +"Defines the name of the application, shown in the web interface, tabs and " +"title bar of the web browser." msgstr "" -#: ../settings/ticket.rst:72 -msgid "" -"If this option is chosen, Zammad will update the 100 most recent tickets " -"where the user is the ticket customer. The ticket organization field will be " -"automatically set to the new primary organization of the user." +#: ../settings/branding.rst:10 +msgid "Default value: ``Zammad Helpdesk``" msgstr "" -#: ../settings/ticket.rst:88 -msgid "Do not update any tickets." +#: ../settings/branding.rst:13 +msgid "Will be shown in the app and is included in email footers." msgstr "" -#: ../settings/ticket.rst:77 -msgid "" -"When choosing this option, Zammad will not update any tickets when the " -"user's primary organization is changed." +#: ../settings/branding.rst:19 +msgid "Logo" msgstr "" -#: ../settings/ticket.rst:80 -msgid "**Use with care!**" +#: ../settings/branding.rst:16 +msgid "Defines the logo of the application, shown in the login page of Zammad." msgstr "" -#: ../settings/ticket.rst:82 +#: ../settings/branding.rst:18 msgid "" -"Using this option may lead to inconsistencies in the system as the ticket " -"organization may become decoupled from the ticket customer." +"Ensure to hit the \"Submit\" button after uploading the logo. Otherwise your " +"change will not be saved." msgstr "" -#: ../settings/ticket.rst:85 +#: ../settings/branding.rst:22 msgid "" -"However, you may use this option if you wish to maintain :ref:`the shared " -"access ` to the ticket for all organization " -"members of the original organization of the customer." +"Allows to set the default language of the Zammad instance. The here defined " +"locale mostly acts as a fallback for:" msgstr "" -#: ../settings/ticket.rst:110 -msgid "Ticket Number Format (default: ``Increment (SystemID.Counter)``)" +#: ../settings/branding.rst:25 +msgid "user preferences (if Zammad can't detect the users locale)" msgstr "" -#: ../settings/ticket.rst:94 -msgid "" -"This setting defines the way Zammad's ticket number will look. Changing this " -"setting in production will cause follow up detection to fail." +#: ../settings/branding.rst:26 +msgid "CSV output (reporting, time accounting)" msgstr "" -#: ../settings/ticket.rst:102 -msgid "Increment (SystemID.Counter)" +#: ../settings/branding.rst:30 +msgid "Define the timezone of your Zammad installation." msgstr "" -#: ../settings/ticket.rst:98 +#: ../settings/branding.rst:32 msgid "" -"The increment value contains the SystemID (automatically generated during " -"installation) and a increment which counts up with every new Ticket. The " -"increment will automatically get another digit if needed." +"This does not have any effect on timings for your agents or how Zammad " +"stores date and time values." msgstr "" -#: ../settings/ticket.rst:102 -msgid "Examples: ``1010138``, ``1010139``" +#: ../settings/branding.rst:35 +msgid "Changing this value has direct consequences on the following areas:" msgstr "" -#: ../settings/ticket.rst:110 -msgid "Date (Year.Month.Day.SystemID.Counter)" +#: ../settings/branding.rst:37 +msgid ":doc:`/manage/scheduler` tasks" msgstr "" -#: ../settings/ticket.rst:105 -msgid "" -"This version of the ticket number is fairly long. However, because it " -"contains the date of ticket creation, it also allows you to see when the " -"ticket has been created. You may feel familiar with this number format if " -"you've worked with OTRS already." +#: ../settings/branding.rst:38 +msgid "search indexing (and thus reporting)" msgstr "" -#: ../settings/ticket.rst:110 -msgid "Examples: ``201206231010138``, ``201206231010139``" +#: ../settings/branding.rst:40 +msgid "calendar subscriptions" msgstr "" -#: ../settings/ticket.rst:137 -msgid "OPTIONS" +#: ../settings/branding.rst:41 +msgid "browser printing" msgstr "" -#: ../settings/ticket.rst:113 +#: ../settings/branding.rst:43 msgid "" -"The below options allow you to further customize your ticket number. The " -"availability of options differ depending of the chosen ticket number format " -"above." +"Please note that some of above are fallbacks in case Zammad could not detect " +"the agents timezone correctly." msgstr "" -#: ../settings/ticket.rst:122 -msgid "Checksum (default: ``no``)" +#: ../settings/branding.rst:77 +msgid "Pretty Date" msgstr "" -#: ../settings/ticket.rst:118 +#: ../settings/branding.rst:47 msgid "" -"If set to yes, we'll built a checksum to further \"unique\" the ticket " -"number of your system. If you're dealing with many other ticket systems this " -"might help to prevent false positive follow up detection on tickets." +"This setting allows you to define how Zammad should display time stamps " +"within the interface to all users." msgstr "" -#: ../settings/ticket.rst:122 -msgid "This will also add another digit to the ticket number." +#: ../settings/branding.rst:50 +msgid "" +"This does not have any effect on how Zammad returns e.g. time values via " +"variables." msgstr "" -#: ../settings/ticket.rst:137 -msgid "Min. size of Number (default: ``5``)" +#: ../settings/branding.rst:77 +msgid "Choose in between the following options:" msgstr "" -#: ../settings/ticket.rst:125 -msgid "" -"This setting defines the minimum length of your ticket number. If your " -"counter is not yet high enough, Zammad will fill the number with zeros to " -"ensure the wanted length." +#: ../settings/branding.rst:64 +msgid "relative" msgstr "" -#: ../settings/ticket.rst:129 +#: ../settings/branding.rst:55 msgid "" -"Please note that the minimum length is ``3`` (SystemID + at least one digit " -"if below 10). Also, if the length is no longer long enough, the number will " -"automatically get one digit longer. Ticket-Numbers **do not overflow**, thus " -"it's save to keep it at 5 or set it lower if wanted." +"This timestamp shows a relative time span until it switches to a date. Over " +"time, it will change as follows:" msgstr "" -#: ../settings/ticket.rst:135 -msgid "" -"This option is only available if ticket number format is set to " -"``Increment``!" +#: ../settings/branding.rst:58 +msgid "just now" msgstr "" -#: ../settings/ticket.rst:142 -msgid "Auto-Assignment" +#: ../settings/branding.rst:59 +msgid "5 minutes ago" msgstr "" -#: ../settings/ticket.rst:144 -msgid "" -"In a larger Zammad environment, it happens that several agents open the same " -"ticket at the same time. Although collision detection is then effective, the " -"efficiency of processing can be increased by means of the automatic " -"assignment of tickets when a ticket is opened." +#: ../settings/branding.rst:60 +msgid "3 days 1 hour ago" msgstr "" -#: ../settings/ticket.rst:149 -msgid "" -"The automatic assignment of tickets can be activated and configured in the " -"admin area under Settings > Ticket > Auto Assignment." +#: ../settings/branding.rst:61 +msgid "``03/04/2022``" msgstr "" -#: ../settings/ticket.rst:152 -msgid "" -"The auto assignment only works if the ticket has no owner yet. By default, " -"the agent can always reset the ticket owner to ``-`` if needed." +#: ../settings/branding.rst:63 +msgid "Hovering the timestamp helps, you'll always get a clean timestamp then." msgstr "" -#: ../settings/ticket.rst:155 -msgid "" -"If you want to use this function for only specific tickets, you can " -"configure the conditions accordingly to meet your requirement. By default " -"the condition affects all tickets with the state ``open``." +#: ../settings/branding.rst:71 +msgid "absolute" msgstr "" -#: ../settings/ticket.rst:161 +#: ../settings/branding.rst:67 msgid "" -"If you need to exclude users (e.g. a group leader), you can search and " -"select the desired agents in the ``Exception Users`` list. The search " -"function in this area is only effective, if you have too many agents to " -"display at once to help you with the configuration." +"This timestamp always includes the week day. For one week after creation, " +"the timestamp will not contain the date itself: Thursday 18:35." msgstr "" -#: ../settings/ticket.rst:167 -msgid "Notifications" +#: ../settings/branding.rst:71 +msgid "After a week it will switch to: ``Friday 4. Mar 16:00``." msgstr "" -#: ../settings/ticket.rst:191 -msgid "Default Notifications" +#: ../settings/branding.rst:76 +msgid "timestamp" msgstr "" -#: ../settings/ticket.rst:170 +#: ../settings/branding.rst:74 msgid "" -"This setting allows you to configure the default ticket notifications that " -"will be applied to all new agent users (incl. users who were just assigned " -"agent role). Simply change the notification matrix to desired state and " -"press **Save**." +"This will cause Zammad to show a complete timestamp according to your locale " +"defaults. For English this could be e.g. ``2022/12/03 2:40 pm`` or for " +"German e.g. ``12.03.2022 14:40``." msgstr "" -#: ../settings/ticket.rst:175 -msgid "" -"In case an agent already exists, their ticket notification preferences will " -"be preserved. Optionally, you can also **Apply current defaults to all " -"agents**." +#: ../settings/branding.rst:78 +msgid "Default setting: ``relative``." msgstr "" -#: ../settings/ticket.rst:181 -msgid "" -"**Potential time-consuming action:** Applying default ticket notifications " -"to all agent users may take some time to complete, be patient! The exact " -"time will depend on the size of your system and the number of agents." +#: ../settings/security.rst:2 +msgid "Security" msgstr "" -#: ../settings/ticket.rst:185 +#: ../settings/security.rst:4 msgid "" -"**Active agents only!** When current default ticket notifications are " -"applied, only active agent users are considered. In case an agent is re-" -"activated *after* this action, they will still have the old notification " -"configuration." +"For your overview we split each tab within security settings into its own " +"page:" msgstr "" -#: ../settings/ticket.rst:190 +#: ../settings/security/base.rst:2 ../settings/system/base.rst:2 +#: ../settings/ticket.rst:8 +msgid "Base" +msgstr "" + +#: ../settings/security/base.rst:5 +msgid "New User Accounts" +msgstr "" + +#: ../settings/security/base.rst:9 msgid "" -"In case you want to go back to the initial state of ticket notifications, " -"you can click on **Reset to default** button." +"Activates the `register as a new customer` function on the login page. If " +"set to ``no`` only administrators or agents can create new accounts manually." msgstr "" -#: ../settings/ticket.rst:194 ../settings/ticket.rst:196 -msgid "Duplicate Detection" +#: ../settings/security/base.rst:13 ../settings/security/base.rst:38 +#: ../settings/security/base.rst:66 +msgid "Default setting: ``yes``" msgstr "" -#: ../settings/ticket.rst:236 ../settings/ticket.rst:238 -msgid "Detect Duplicate Ticket Creation" +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"New User Accounts\" setting" msgstr "" -#: ../settings/ticket.rst:197 ../settings/ticket.rst:199 +#: ../settings/security/base.rst:22 msgid "" -"This setting turns on the duplicate ticket detection mechanism during ticket " -"creation. If similar tickets are found in the system, a suitable warning " -"will be shown to the user trying to create a ticket." +"Deactivation of above function **does not** deactivate automatic account " +"creation! This means: If a user writes e.g. an email to Zammad and has no " +"account yet, Zammad will automatically create the account. User accounts are " +"a direct dependency of tickets and thus technically mandatory." msgstr "" -#: ../settings/ticket.rst:204 ../settings/ticket.rst:206 -msgid "A Sample Duplicate Ticket Warning" +#: ../settings/security/base.rst:29 +msgid "Lost Password" msgstr "" -#: ../settings/ticket.rst:206 ../settings/ticket.rst:208 +#: ../settings/security/base.rst:33 msgid "" -"You can choose which ticket attributes will be matched by selecting them in " -"**Attributes to compare** field. Only if the ticket attribute value provided " -"by the user in the ticket create form is *equal* with the attribute in an " -"existing ticket, the warning will be shown." +"Activates the `lost password` function on the login page. If set to ``no`` " +"only administrators may change the user's password - users may update their " +"own password if they're still logged in and they have the required :doc:" +"`permission `." msgstr "" -#: ../settings/ticket.rst:211 ../settings/ticket.rst:213 -msgid "**Warning title** and **Warning message** are configurable as well." +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"Lost Password\" setting" msgstr "" -#: ../settings/ticket.rst:213 ../settings/ticket.rst:215 +#: ../settings/security/base.rst:49 msgid "" -"You can limit the detection only to certain user roles. By default, only " -"agents will see the warning." +"With third party authentications - but especially LDAP - you may want to " +"disable this function. Zammad **will not** change third party login " +"passwords and instead set or change the local password!" msgstr "" -#: ../settings/ticket.rst:216 ../settings/ticket.rst:218 -msgid "" -"If you don't want to show the matched tickets as part of the warning, you " -"can set **Show matching ticket(s) in the warning** setting to *no*." +#: ../settings/security/base.rst:56 +msgid "Password Login" msgstr "" -#: ../settings/ticket.rst:219 ../settings/ticket.rst:221 +#: ../settings/security/base.rst:60 msgid "" -"By default, **Permission level for looking up ticket** is set to *User*, " -"which means user permissions will be honored during sarch. The user will " -"see the warning only if tickets they have access to are matched. " -"Alternatively, you can set this setting to *System*, in which case the " -"search will happen within *all* tickets in the system, regardless of user " -"permissions." +"Activates the username & password login by default and if no third-party " +"login is activated. Disabling password login on the Zammad login page only " +"takes effect if you enable any :doc:`third-party`." msgstr "" -#: ../settings/ticket.rst:225 ../settings/ticket.rst:227 -msgid "**🦺 Safety first!**" +#: ../settings/security/base.rst:64 +msgid "See :doc:`third-party` for supported third-party logins." msgstr "" -#: ../settings/ticket.rst:227 ../settings/ticket.rst:229 -msgid "" -"Even if the permission level is set to *System*, the user will not be shown " -"the tickets they don't have access to in the warning, even if they match." +#: ../settings/security/base.rst:0 +msgid "Figure showing de-activated \"Password Login\" setting" msgstr "" -#: ../settings/ticket.rst:231 ../settings/ticket.rst:233 +#: ../settings/security/base.rst:77 msgid "" -"However, just the confirmation about the existence of the tickets in the " -"system may be considered an unwanted information disclosure. Use this option " -"carefully!" +"To help administrators to overcome \"login issues\", Zammad automatically " +"offers a password request for administrator users. This allows you to adjust " +"Third-Party applications even if the login does no longer work!" msgstr "" -#: ../settings/ticket.rst:235 ../settings/ticket.rst:237 -msgid "" -"Finally, you can configure between matching within **All tickets** or **Open " -"tickets** only by setting **Match tickets in following states**. Depending " -"on the current ticket state, a ticket may or not be matched." +#: ../settings/security/base.rst:84 +msgid "Session Timeout" msgstr "" -#: ../system/core-workflows.rst:2 -msgid "Core Workflows" +#: ../settings/security/base.rst:86 +msgid "" +"All settings below by default are set to ``4 weeks``. Session Timeout " +"defines the life time of a users session. As soon as it's reached, Zammad " +"will automatically log off the session in question." msgstr "" -#: ../system/core-workflows.rst:4 +#: ../settings/security/base.rst:91 msgid "" -"Core Workflows allow you to adjust object attributes in many ways. For " -"example:" +"Zammad takes the highest value set assigned for the user based on the " +"permissions." msgstr "" -#: ../system/core-workflows.rst:7 -msgid "show / hide fields" +#: ../settings/security/base.rst:94 +msgid "``admin``" msgstr "" -#: ../system/core-workflows.rst:8 -msgid "adjust mandatory setting" +#: ../settings/security/base.rst:96 +msgid "``ticket.customer``" msgstr "" -#: ../system/core-workflows.rst:9 -msgid "manipulate available options" +#: ../settings/security/base.rst:97 +msgid "``default`` (fallback if user doesn't have above permissions set)" msgstr "" -#: ../system/core-workflows.rst:11 +#: ../settings/security/base.rst:99 msgid "" -"With this, you can provide exactly the information your users really need!" +"All settings act independently from each other allowing you to disable the " +"timeouts for e.g. admins, but not agents." msgstr "" -#: ../system/core-workflows.rst:15 -msgid "" -"If the pre-defined :doc:`/system/objects` are not enough, please add them " -"beforehand." +#: ../settings/security/base.rst:115 +#: ../system/integrations/checkmk/api-reference.rst:13 +msgid "Example" msgstr "" -#: ../system/core-workflows.rst:17 -msgid "" -"If you experience slow or unreliable field updates, please see :ref:`Core " -"Workflow Ajax Modus `" +#: ../settings/security/base.rst:107 +msgid "Let's suppose you configured the following session timeouts" msgstr "" -#: ../system/core-workflows.rst:22 -msgid "" -"This is a very enhanced functionality and can cause unexpected UI behavior. " -"Please ensure to test your use cases after configuration to reduce surprises." +#: ../settings/security/base.rst:104 +msgid "default: 3 weeks" msgstr "" -#: ../system/core-workflows.rst:None -msgid "Dialogue for adding a new workflow" +#: ../settings/security/base.rst:105 +msgid "admin: 2 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:2 -msgid "Core Workflow Condition Operators" +#: ../settings/security/base.rst:106 +msgid "ticket.agent: 4 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:4 -msgid "" -"You might know that there is a separate section for explaining :doc:" -"`condition operators `. Head over there to " -"see a detailed explanation of many conditions and operators." +#: ../settings/security/base.rst:107 +msgid "ticket.customer: 1 week" msgstr "" -#: ../system/core-workflows/condition-operators.rst:8 -msgid "" -"Due to differences to other places in Zammad which are also using conditions " -"(e.g. triggers), you can find a dedicated description of operators for core " -"workflows below." +#: ../settings/security/base.rst:115 +msgid "This results in the following situations" msgstr "" -#: ../system/core-workflows/condition-operators.rst:12 -msgid "" -"Be aware that the availability of the operators depends on the selected " -"attribute and its field type. Some of the operators may only be available " -"for system attributes (e.g. for \"tags\", \"active\")." +#: ../settings/security/base.rst:110 +msgid "a user with ``admin`` permission will have a timeout of 2 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:20 -msgid "Operator" +#: ../settings/security/base.rst:111 +msgid "" +"a user with ``admin`` and ``ticket.agent`` permissions will have a timeout " +"of 2 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:22 -msgid "after (absolute)" +#: ../settings/security/base.rst:113 +msgid "" +"a user with ``ticket.customer`` permission will have a timeout of 1 week" msgstr "" -#: ../system/core-workflows/condition-operators.rst:23 -msgid "Matches if a date/time is after a specific point in time." +#: ../settings/security/base.rst:115 +msgid "" +"a user with neither ``admin``, ``ticket.agent`` nor ``ticket.customer`` " +"permissions will have a timeout of 3 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:24 -msgid "after (relative)" +#: ../settings/security/password.rst:4 +msgid "" +"This section allows you to define password requirements for the local user " +"accounts." msgstr "" -#: ../system/core-workflows/condition-operators.rst:25 -msgid "Matches if a time span after a specified event has passed." +#: ../settings/security/password.rst:9 +msgid "" +"Zammad does **not** allow you to change your LDAP password, instead, it will " +"set a password in its local database which might confuse your users. This " +"might be addressed in the future by `#1169 `_." msgstr "" -#: ../system/core-workflows/condition-operators.rst:26 -msgid "before (absolute)" +#: ../settings/security/password.rst:14 +msgid "**Exception for admins**" msgstr "" -#: ../system/core-workflows/condition-operators.rst:27 -msgid "Matches if a date/time is before a specific point in time." +#: ../settings/security/password.rst:16 +msgid "" +"Please note that below password policies *do not* affect administrators " +"setting passwords on user accounts. While this seems strange and not safe we " +"believe that an administrator knowing an user's password is insecure as well." msgstr "" -#: ../system/core-workflows/condition-operators.rst:28 -msgid "before (relative)" +#: ../settings/security/password.rst:21 +msgid "The suggested workflow is either:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:29 -msgid "Matches if a time span after a specified event has not passed." +#: ../settings/security/password.rst:23 +msgid "" +"to use third party logins to not require local passwords at all **- or -**" msgstr "" -#: ../system/core-workflows/condition-operators.rst:30 -msgid "contains" +#: ../settings/security/password.rst:25 +msgid "to require your *user to reset the password* upon first login." msgstr "" -#: ../system/core-workflows/condition-operators.rst:31 -msgid "Matches if a specified value is present." +#: ../settings/security/password.rst:27 +msgid "" +"This way administrators are not required to set a user's password at all!" msgstr "" -#: ../system/core-workflows/condition-operators.rst:33 -msgid "Matches if all of the specified values are present." +#: ../settings/security/password.rst:31 +msgid "Maximum Failed Logins" msgstr "" -#: ../system/core-workflows/condition-operators.rst:35 -msgid "Matches if none of the specified values are present." +#: ../settings/security/password.rst:33 +msgid "" +"You can choose a value between ``4`` and ``20``. This defines how often a " +"login to a user account may fail until Zammad will lock it. Your users can " +"always use the \"forgot password\" function to change their password and " +"unlock their account." msgstr "" -#: ../system/core-workflows/condition-operators.rst:36 -msgid "contains not" +#: ../settings/security/password.rst:38 +msgid "The default value is ``10``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:37 -msgid "Matches if a specified value is not present." +#: ../settings/security/password.rst:42 +msgid "Beside changing the user's password, you can also unlock accounts via" msgstr "" -#: ../system/core-workflows/condition-operators.rst:39 -msgid "Matches if one specified value is present." +#: ../settings/security/password.rst:44 +msgid ":ref:`user management list `" msgstr "" -#: ../system/core-workflows/condition-operators.rst:41 -msgid "Matches if one specified value is not present." +#: ../settings/security/password.rst:45 +msgid ":docs:`console `" msgstr "" -#: ../system/core-workflows/condition-operators.rst:42 -msgid "does not match regex" +#: ../settings/security/password.rst:46 +msgid ":docs:`API `" msgstr "" -#: ../system/core-workflows/condition-operators.rst:43 -msgid "Matches if content doesn't fit to regex rule." +#: ../settings/security/password.rst:50 +msgid "Failed logins via LDAP no longer lock accounts." msgstr "" -#: ../system/core-workflows/condition-operators.rst:44 -msgid "ends with" +#: ../settings/security/password.rst:53 +msgid "2 Lower Case And 2 Upper Case Characters" msgstr "" -#: ../system/core-workflows/condition-operators.rst:45 -msgid "Matches if content ends with specified value." +#: ../settings/security/password.rst:55 +msgid "" +"You can add complexity to passwords by enforcing at least 2 upper and lower " +"case characters." msgstr "" -#: ../system/core-workflows/condition-operators.rst:46 -msgid "ends with one of" +#: ../settings/security/password.rst:58 ../settings/security/password.rst:83 +msgid "The default value is ``no``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:47 -msgid "Matches if content ends with one of the specified values." +#: ../settings/security/password.rst:62 +msgid "Minimum Length" msgstr "" -#: ../system/core-workflows/condition-operators.rst:48 -msgid "from (relative)" +#: ../settings/security/password.rst:64 +msgid "" +"This defines the minimum password length required for users to provide (from " +"``4`` to ``20``)." msgstr "" -#: ../system/core-workflows/condition-operators.rst:49 -msgid "Matches if date/time is after a period of time after an event." +#: ../settings/security/password.rst:67 +msgid "The default value is ``6``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:51 -msgid "Matches if content is equal to a specified value." +#: ../settings/security/password.rst:71 +msgid "Digit Required" msgstr "" -#: ../system/core-workflows/condition-operators.rst:52 -msgid "is any of" +#: ../settings/security/password.rst:73 +msgid "This enforces your users to use at least one digit within the password." msgstr "" -#: ../system/core-workflows/condition-operators.rst:53 -msgid "Matches if content is equal to any of specified values." +#: ../settings/security/password.rst:75 +msgid "The default value is ``yes``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:54 -msgid "is modified" +#: ../settings/security/password.rst:78 +msgid "Special Character Required" msgstr "" -#: ../system/core-workflows/condition-operators.rst:55 -msgid "Matches if content is modified." +#: ../settings/security/password.rst:80 +msgid "" +"This setting allows you to improve your password quality even more by " +"enforcing the password to contain at least one special character." msgstr "" -#: ../system/core-workflows/condition-operators.rst:57 -#: ../system/core-workflows/condition-operators.rst:61 -msgid "True from the moment of changing content until form submit." +#: ../settings/security/ssl-certificates.rst:2 +msgid "SSL Certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:58 -msgid "is modified to" +#: ../settings/security/ssl-certificates.rst:7 +msgid "" +"Zammad offers the possibility to upload custom certificates and custom " +"Certificate Authority (CA) certificates. This can be useful if you want to " +"connect Zammad the secure way to other systems which are using custom " +"certificates." msgstr "" -#: ../system/core-workflows/condition-operators.rst:59 -msgid "Matches if content is modified to a specific value." +#: ../settings/security/ssl-certificates.rst:12 +msgid "" +"An example usecase might be: You have an internal LDAP server that is not " +"accessible from the internet, and you want a SSL-encrypted connection, using " +"a custom certificate." msgstr "" -#: ../system/core-workflows/condition-operators.rst:62 -msgid "is none of" +#: ../settings/security/ssl-certificates.rst:19 +msgid "" +"You should have an existing custom certificate file and/or a custom CA " +"certificate file, which you want to add to Zammad. As filetype ``.crt`` is " +"supported and the certificate format has to be PEM (Base64 ASCII)." msgstr "" -#: ../system/core-workflows/condition-operators.rst:63 -msgid "Matches if content is none of any specified values." +#: ../settings/security/ssl-certificates.rst:25 +msgid "" +"When you import a custom CA certificate, all certificates generated with " +"this are trusted. This can be useful if you have more than one system/" +"certificate you want to connect to and the certificates are issued from the " +"same custom CA." msgstr "" -#: ../system/core-workflows/condition-operators.rst:65 -msgid "Matches if content is not equal to a specified value." +#: ../settings/security/ssl-certificates.rst:31 +msgid "Add a Certificate" msgstr "" -#: ../system/core-workflows/condition-operators.rst:67 -msgid "Matches if content is present." +#: ../settings/security/ssl-certificates.rst:33 +msgid "" +"To add a custom certificate or a custom CA certificate, head over to the " +"Admin panel > Settings > Security > SSL Certificates. Here you can find a " +"\"Add SSL Certificate\" button. In the dialog you can either select a " +"certificate file or paste the content of the certificate:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:68 -msgid "just changed" +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate adding dialog" msgstr "" -#: ../system/core-workflows/condition-operators.rst:69 -msgid "Matches if content has changed." +#: ../settings/security/ssl-certificates.rst:43 +msgid "" +"After selecting a file or pasting the content of the certificate, click on " +"the \"Add\" button to finally upload it to Zammad. Then, the certificates " +"are immediately effective, no restart or similar required." msgstr "" -#: ../system/core-workflows/condition-operators.rst:71 -#: ../system/core-workflows/condition-operators.rst:75 +#: ../settings/security/ssl-certificates.rst:49 msgid "" -"Only true for the moment of changing content until next form field action/" -"click." +"Please note that only single certificate files are supported. That means if " +"you want to import a certificate / CA certificate, it must contain **only " +"one** certificate." msgstr "" -#: ../system/core-workflows/condition-operators.rst:72 -msgid "just changed to" +#: ../settings/security/ssl-certificates.rst:54 +msgid "Certificate Overview" msgstr "" -#: ../system/core-workflows/condition-operators.rst:73 -msgid "Matches if content has changed to a specified value." +#: ../settings/security/ssl-certificates.rst:56 +msgid "" +"After you added a certificate, you can see a table with information for each " +"added certificate:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:76 -msgid "matches regex" +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing table of added certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:77 -msgid "Matches if value fits to regex rule." -msgstr "" - -#: ../system/core-workflows/condition-operators.rst:79 -msgid "Matches if no content is present." -msgstr "" - -#: ../system/core-workflows/condition-operators.rst:80 -msgid "starts with" +#: ../settings/security/ssl-certificates.rst:64 +msgid "" +"Here you can download the certificate or delete it, if you don't need it " +"anymore." msgstr "" -#: ../system/core-workflows/condition-operators.rst:81 -msgid "Matches if content starts with specified value." +#: ../settings/security/ssl-certificates.rst:68 +msgid "Deleting Certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:82 -msgid "starts with one of" +#: ../settings/security/ssl-certificates.rst:70 +msgid "" +"If you want to delete a specific certificate, you can do it by clicking on " +"the menu in the actions column and selecting delete:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:83 -msgid "Matches if content starts with one of the specified values." +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate deletion button" msgstr "" -#: ../system/core-workflows/condition-operators.rst:84 -msgid "till (relative)" +#: ../settings/security/ssl-certificates.rst:79 +msgid "Downloading Certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:85 -msgid "Matches if date/time is before a period of time before an event." +#: ../settings/security/ssl-certificates.rst:81 +msgid "" +"If you want to download your certificates, you can do this as well via " +"corresponding action buttons." msgstr "" -#: ../system/core-workflows/condition-operators.rst:86 -msgid "today" +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate download button" msgstr "" -#: ../system/core-workflows/condition-operators.rst:87 -msgid "Matches if date/time is today." +#: ../settings/security/third-party.rst:13 +msgid "Login Providers" msgstr "" -#: ../system/core-workflows/condition-operators.rst:88 -msgid "within last (relative)" +#: ../settings/security/third-party.rst:2 +msgid "Third-Party Applications" msgstr "" -#: ../system/core-workflows/condition-operators.rst:89 +#: ../settings/security/third-party.rst:4 msgid "" -"Matches if date/time content is within specified period of time before now." +"Third party authentication is a great way to help your users to login to " +"Zammad more easily. If the account is yet unknown, Zammad will create a new " +"user automatically, without the user needed to interact (e.g. type in his " +"name). Another big advantage of this feature is that your user doesn't need " +"to remember another password." msgstr "" -#: ../system/core-workflows/condition-operators.rst:91 -msgid "within next (relative)" +#: ../settings/security/third-party.rst:10 +msgid "" +"You can deactivate logging in via :ref:`security_password_login` if any of " +"the mentioned authentication providers are enabled in your instance." msgstr "" -#: ../system/core-workflows/condition-operators.rst:92 +#: ../settings/security/third-party.rst:27 msgid "" -"Matches if date/time content is within specified period of time after now." +"We're currently missing documentation for the following login providers:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:2 -msgid "How do they work?" +#: ../settings/security/third-party.rst:29 +msgid "LinkedIn" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:4 -msgid "" -"Core Workflows are executed according to their priority. If two workflows " -"have the same priority, they are executed in alphabetical order based on " -"their **name**." +#: ../settings/security/third-party.rst:30 +msgid "Weibo" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:8 -msgid "" -"Because of the way Core Workflows work, all changes to attributes are " -"checked with the application server - please see :doc:`limitations` for " -"possible issues." +#: ../settings/security/third-party.rst:35 +msgid "Automatic Account Link on Initial Logon" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:12 +#: ../settings/security/third-party.rst:37 msgid "" -"Below we're talking about settings that are important and not self-" -"explanatory." +"In general there's two possible options for Zammad on how to deal with " +"already known users as they try to authenticate against a third-party " +"application. By default, Zammad will not automatically link \"unknown\" " +"authentication providers to existing accounts." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:17 +#: ../settings/security/third-party.rst:42 msgid "" -"Choose the object context you want to run the workflow in. This will decide " -"on your available attributes and actions." -msgstr "" - -#: ../system/core-workflows/how-do-they-work.rst:20 -msgid "Ticket objects also have access to the ticket customer." +"This means that the user has to manually link authentication providers to " +"their accounts (for more about this :user-docs:`consult the user " +"documentation `)." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:25 +#: ../settings/security/third-party.rst:46 msgid "" -"Choose in which situation the workflow is applied. Contexts can be combined " -"to avoid duplicate workflows." +"Sometimes this doesn't come in handy as this also means you'll receive error " +"messages about \"email address being in use already\" for (yet) unknown " +"third-party authentication methods." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:30 -msgid "Creation mask" +#: ../settings/security/third-party.rst:50 +msgid "" +"If you want to allow your users to always be able to log in, no matter what, " +"you may want to enable ``Automatic account link on initial logon``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:29 +#: ../settings/security/third-party.rst:None msgid "" -"If selected, your conditions and actions will affect all applicable creation " -"masks." +"Screenshot highlighting the \"Automatic account link on initial logon\"\n" +"setting" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:34 -msgid "Edit mask" +#: ../settings/security/third-party.rst:60 +msgid "Automatic Account Linking Notification" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:33 +#: ../settings/security/third-party.rst:64 msgid "" -"If selected, your conditions and actions will affect all applicable edit " -"masks." +"To improve security and your users awareness, you can enable Zammad to " +"notify your users when a new third-party application has been linked to " +"their account." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:39 +#: ../settings/security/third-party.rst:68 msgid "" -"Zammad differentiates between selected and saved conditions. These can be " -"combined wherever needed." +"This notification is sent out once per third-party application. Zammad does " +"also mention the method used, e.g.: ``Microsoft``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:42 -msgid "**⚠️ Restrict workflows to specific roles if needed!**" +#: ../settings/security/third-party.rst:71 +msgid "By default this setting is not active (set to ``no``)." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:44 +#: ../settings/security/third-party.rst:0 msgid "" -"By default and unless configured in conditions, workflow rules are executed " -"for **all roles**. This also affects your customers!" +"Screenshot showing sample notification mail after initial\n" +"third-party linking" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:50 -msgid "Selected Conditions" +#: ../settings/security/third-party.rst:85 +msgid "" +"This notification is only sent if the account in question already exists. If " +"the login via the third-party also creates the missing account, the " +"notification will be skipped." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:48 -msgid "" -"These conditions are based on form values and match if an appropriate " -"selection is made (e.g. choosing another group in the ticket without " -"saving). This applies for drafts (active selection) and currently saved " -"values." +#: ../settings/security/third-party.rst:89 +msgid "This means it only affects:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:64 -msgid "Saved Conditions" +#: ../settings/security/third-party.rst:91 +msgid "manual account linking within the third-party page of the users profile" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:53 +#: ../settings/security/third-party.rst:92 msgid "" -"These conditions only match if the selected values are stored in the " -"database. It ignores the current value or selection of the field, as long as " -"the changes are not saved (e.g. performing field operations for an existing " -"ticket, which is viewed/opened by an agent)." +"logging into an existing local account by utilizing the *automatic account " +"link on initial logon* functionality" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:60 +#: ../settings/security/third-party.rst:None msgid "" -"Keep in mind that the value has to be available in the situation where you " -"need it. Otherwise the condition won't match." +"Screenshot showing the \"automatic account linking notification\"\n" +"setting" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:63 -msgid "" -"Example: you can't perform any actions with *saved condition* on a ticket in " -"creation, because there are no saved values at that time." +#: ../settings/security/third-party.rst:100 +msgid "No User Creation on Logon" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:66 +#: ../settings/security/third-party.rst:102 msgid "" -"You can find a description of the condition operators for core workflows :" -"doc:`here `." +"By default, Zammad will create a new user account if the user logs in via a " +"third-party application and the account doesn't exist yet." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:72 +#: ../settings/security/third-party.rst:105 msgid "" -"Which actions should we run on the relevant fields? The possible actions " -"depend on the object type. However, usually you can at least change the " -"visibility and whether the field is mandatory." +"If you want to prevent Zammad from creating new accounts on logon, you can " +"disable this feature by setting ``No user creation on logon`` to ``yes``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:76 -msgid "Be aware that actions are not available for **related** context." +#: ../settings/security/third-party.rst:None +msgid "Screenshot showing the \"no user creation on logon\" setting" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:78 +#: ../settings/security/third-party/facebook.rst:4 msgid "" -"**Example:** Let's assume you are working in the ticket context. While you " -"can have customer *conditions*, you *can't adjust* objects with actions in " -"that scope. That's because this wouldn't have any impact on the ticket " -"dialog. Of course all ticket attributes (state, owner, ...) are available." +"It is possible to create a quick login for your helpdesk via Facebook To do " +"so, you need to follow these steps:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:84 +#: ../settings/security/third-party/facebook.rst:9 +msgid "Register Facebook App" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:11 msgid "" -"Please also have a look at our :doc:`limitations` to be safe from surprises." +"Visit [https://developers.facebook.com/apps/] and click on \"Add a new App\"" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:88 -msgid "Available Operators" +#: ../settings/security/third-party/facebook.rst:None +msgid "initial page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:90 -msgid "The availability of operators depends on the object type and scope." +#: ../settings/security/third-party/facebook.rst:17 +msgid "After that enter the app settings" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:94 -msgid "" -"Please note that actions may or may not restrict API based access to " -"attributes. We're displaying the following icons for your overview to " -"understand these limits better:" +#: ../settings/security/third-party/facebook.rst:None +msgid "Create App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:0 -msgid "|api| This icon indicates the action affects the API." +#: ../settings/security/third-party/facebook.rst:22 +msgid "Navigate to \"Settings\" and fill in this infromation" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:163 -msgid "api" +#: ../settings/security/third-party/facebook.rst:None +msgid "App Settings" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:0 -msgid "|ui| This icon indicates the action only affects the web interface." +#: ../settings/security/third-party/facebook.rst:27 +msgid "Navigate to app review and Check \"Make [appname] public?\"" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:167 -msgid "ui" +#: ../settings/security/third-party/facebook.rst:None +msgid "App Review" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:102 -msgid "show |ui|" +#: ../settings/security/third-party/facebook.rst:35 +msgid "Configure Zammad as Facebook App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:102 -msgid "Display the chosen field. Allows setting of values." -msgstr "" - -#: ../system/core-workflows/how-do-they-work.rst:109 -msgid "hide |ui|" +#: ../settings/security/third-party/facebook.rst:37 +msgid "" +"Navigate to \"Admin -> Security -> Third Party Applications\" and enter the " +"App ID and the App Secret. You can find this Key in the Dashbard of your " +"Facebok app." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:105 -msgid "" -"Hide the chosen field. However, it technically still allows setting the " -"field." +#: ../settings/security/third-party/facebook.rst:None +msgid "Zammad Configuration" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:108 +#: ../settings/security/third-party/facebook.rst:44 +#: ../settings/security/third-party/github.rst:43 +#: ../settings/security/third-party/gitlab.rst:46 msgid "" -"Please note that the field is **not** gone and still contains an existing " -"value (if set)! Consider *remove* instead, if you want this field to be gone." +"Now you can link accounts via \"Avatar -> Profile -> Link Accounts\" or " +"login via Zammad login page." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:112 -msgid "remove |ui|" +#: ../settings/security/third-party/github.rst:2 +#: ../system/integrations/github.rst:2 +msgid "GitHub" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:112 -msgid "Entirely removes the field. The field value will not be evaluated." +#: ../settings/security/third-party/github.rst:4 +msgid "" +"It is possible to create a quick login for your helpdesk via GitHub. To " +"activate the quick login you need to enable OAuth for GitHub." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:115 -msgid "set mandatory |ui| |api|" +#: ../settings/security/third-party/github.rst:8 +msgid "Register GitHub App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:115 -msgid "Sets the field to mandatory." +#: ../settings/security/third-party/github.rst:10 +msgid "" +"Visit https://www.github.com/settings/applications/new and enter the app " +"settings. As callback URL enter \"https://zammad_host/auth/github/callback\" " +"where zammad_host has to be replaced with your Zammad FQDN" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:118 -msgid "set optional |ui| |api|" +#: ../settings/security/third-party/github.rst:None +msgid "Register OAuth app on www.github.com" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:118 -msgid "Sets the field to optional." +#: ../settings/security/third-party/github.rst:19 +msgid "Configure Zammad as GitHub App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:124 -msgid "add option |ui| |api|" +#: ../settings/security/third-party/github.rst:21 +msgid "" +"Enter the \"APP ID\" and the \"APP SECRET\" from the GitHub OAUTH " +"Applications Dashboard" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:121 -msgid "Allows adding options to tree selects or selects." +#: ../settings/security/third-party/github.rst:None +msgid "GitHub config in Zammad admin interface" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:123 +#: ../settings/security/third-party/github.rst:28 msgid "" -"You have to use the \"remove option\" before performing this action. It " -"allows you to use *existing* configured values." +"After you configured the GitHub credentials and activated the login method, " +"you should see a new icon on the login page." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:128 -msgid "remove option |ui| |api|" +#: ../settings/security/third-party/github.rst:None +msgid "GitHub logo on login page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:127 +#: ../settings/security/third-party/github.rst:34 msgid "" -"Allows removing options from tree selects or selects. It allows you to use " -"*existing* configured values." +"If you click on the icon you will be redirected to GitHub and see something " +"similar to this:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:134 -msgid "set fixed to |ui| |api|" +#: ../settings/security/third-party/github.rst:None +msgid "GitHub oauth page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:131 -msgid "Reduces the available options by your selection." +#: ../settings/security/third-party/github.rst:40 +#: ../settings/security/third-party/gitlab.rst:42 +msgid "" +"When you grant the access you will be redirected to your Zammad instance and " +"logged in as a customer." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:133 -msgid "" -"This reduces your workflows in terms of *add option* and *remove option*." +#: ../settings/security/third-party/gitlab.rst:2 +msgid "Gitlab" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:137 -msgid "fill in |ui|" +#: ../settings/security/third-party/gitlab.rst:4 +msgid "" +"It is possible to create a quick login for your helpdesk via Gitlab. To " +"activate the quick login you need to enable OAuth for Gitlab." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:137 -msgid "Allows filling in of string and integer fields with your values." +#: ../settings/security/third-party/gitlab.rst:8 +msgid "Register Gitlab App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:141 -msgid "fill in empty |ui|" +#: ../settings/security/third-party/gitlab.rst:10 +msgid "To register an app in Gitlab open your profile and select applications." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:140 +#: ../settings/security/third-party/gitlab.rst:12 msgid "" -"Allows filling in of string and integer fields with your values **if the " -"field is empty**." +"As callback URL enter \"https://zammad-fqdn/auth/gitlab/callback\" where " +"zammad-fqdn has to be replaced with your Zammad FQDN" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:144 -msgid "select |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Register OAuth app on gitlab instance" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:144 -msgid "Select a specific value within a select, tree select or boolean field." +#: ../settings/security/third-party/gitlab.rst:18 +msgid "Just select *read_user* under scopes as in the screenshot and save it." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:153 -msgid "auto select |ui|" +#: ../settings/security/third-party/gitlab.rst:21 +msgid "Configure Zammad as Gitlab App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:147 -msgid "Helps users with tree select and select fields:" +#: ../settings/security/third-party/gitlab.rst:23 +msgid "" +"Enter the \"APP ID\" and the \"APP SECRET\" from the Gitlab OAUTH " +"Applications Dashboard and your Gitlab-URL in the \"SITE\" field." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:149 -msgid "" -"If the field has only one option available for selection and no value yet, " -"the value will be automatically set." +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab config in Zammad admin interface" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:152 +#: ../settings/security/third-party/gitlab.rst:30 msgid "" -"This option only works if you have one value and doesn't work if there is " -"more than one option available." +"After you configured the Gitlab credentials and activated the login method, " +"you should see a new icon on the login page." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:157 -msgid "set readonly |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab logo on login page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:156 +#: ../settings/security/third-party/gitlab.rst:36 msgid "" -"Allows you to display an attribute as read only (which means no changes are " -"possible)." +"If you click on the icon you will be redirected to Gitlab and see something " +"similar to this:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:161 -msgid "unset readonly |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab oauth page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:160 +#: ../settings/security/third-party/google.rst:4 msgid "" -"In case a workflow set the field in question to read only, you can undo this " -"with option above." +"With some easy and fast steps, you can enable Zammad to authenticate your " +"users via Google." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:172 -msgid "Stop after match" +#: ../settings/security/third-party/google.rst:8 +msgid "Register a Google App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:174 +#: ../settings/security/third-party/google.rst:10 msgid "" -"Here you can decide if other workflows are executed after the current one." +"First of all, we need to create a new project - you can skip this step if " +"you already have one." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:176 +#: ../settings/security/third-party/google.rst:15 msgid "" -"If set to ``no`` (default), further workflows will be executed if they match " -"the condition. In this case, it is possible that your actions from the " -"current workflow can be overwritten by another workflow." +"Use this link to create a new project: https://console.cloud.google.com/" +"projectcreate" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:180 +#: ../settings/security/third-party/google.rst:18 msgid "" -"If set to ``yes``, no further worflows will be executed after the current " -"one." +"Now expand the menu, expand \"APIs & Services\" and select \"Credentials\". " +"Go to the tab \"OAuth consent screen\" first and ensure to fill in the " +"requested information - without doing so you can't create credentials!" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:184 -msgid "Priority" +#: ../settings/security/third-party/google.rst:None +msgid "Creating a consent screen" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:186 +#: ../settings/security/third-party/google.rst:25 msgid "" -"You can define the sequence, in which the workflows are executed. The " -"default value is ``500``." +"After filling in and saving the consent screen information, you can go to " +"the \"Credentials\" tab and create new \"OAuth client ID\"-Credentials." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:189 +#: ../settings/security/third-party/google.rst:28 msgid "" -"The workflows are executed in ascending order by their priority. That means " -"lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." +"Fill in the necessary information as follows and replace ``zammad_host`` " +"with your FQDN:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:2 -msgid "Learn by Example" +#: ../settings/security/third-party/google.rst:31 +msgid "**Application type** ``[x] Web application``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:4 -msgid "" -"This page provides some basic examples for Core Workflows. Of course you can " -"build much more complex workflows if needed." +#: ../settings/security/third-party/google.rst:34 +msgid "**Authorized JavaScript origins** ``https://zammad_host/``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:7 +#: ../settings/security/third-party/google.rst:37 msgid "" -"To learn about Core Workflows in detail, first go to :doc:`how-do-they-work`." +"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" +"callback``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:10 -msgid "Group Based Examples" +#: ../settings/security/third-party/google.rst:None +msgid "Adding a new OAuth client ID" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:12 +#: ../settings/security/third-party/google.rst:43 msgid "" -"All following workflows have the same base configurations. The workflow may " -"not use them all." +"After creating the credentials, go to your Zammad installation and navigate " +"to \"Admin > Security > Third Party Applications\" > Google. Enter your " +"Client ID and Client secret here." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:15 -msgid "Groups:" +#: ../settings/security/third-party/google.rst:None +msgid "Zammad" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:20 -msgid "Attributes:" +#: ../settings/security/third-party/google.rst:50 +msgid "After submitting, the login via Google can be used." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:22 -msgid "Category (Single tree selection field, not mandatory, agents only)" +#: ../settings/security/third-party/microsoft.rst:2 +msgid "Microsoft" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:23 +#: ../settings/security/third-party/microsoft.rst:4 msgid "" -"Approved (Boolean field, not mandatory, not shown, ``false`` as default)" +"Zammad's Microsoft connection allows your users with Microsoft accounts to " +"login. This works for Azure users as well and can be an alternative to :doc:" +"`/system/integrations/ldap/index`." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:24 -msgid "Operating System (Text field, not mandatory, not shown)" +#: ../settings/security/third-party/microsoft.rst:10 +msgid "" +"This documentation part does not cover our :doc:`📧 Microsoft 365 email " +"channel `." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:25 -msgid "Software used (Single selection field, not mandatory, not shown)" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screenshot showing Microsoft login button on Zammad login screen." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:68 -msgid "Group specific values and fields" +#: ../settings/security/third-party/microsoft.rst:30 +#: ../settings/security/third-party/microsoft.rst:53 +msgid "Supported account types:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:28 +#: ../settings/security/third-party/microsoft.rst:22 msgid "" -"This workflow set depends on the category field. It reduces the available " -"set of values based on the group selected." +"Please note that Zammad only supports these account types (App dependent):" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:33 -msgid "Workflow 2nd Level group" +#: ../settings/security/third-party/microsoft.rst:35 +msgid "Avatars of signing in users:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:35 +#: ../settings/security/third-party/microsoft.rst:33 msgid "" -"This reduces the category options to ``2nd Level/*``, ``Internal/*`` and " -"``Others``. It also sets further required fields to mandatory and visible." -msgstr "" - -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for 2nd level" +"Zammad currently ignores user avatars. If the user is registered with e.g. " +"Gravatar, Zammad will fetch the avatar from there if enabled. See :doc:" +"`Zammad Image Service ` for more." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:43 -msgid "Workflow Support group" +#: ../settings/security/third-party/microsoft.rst:38 +msgid "Step 1 - Register a Microsoft App for Zammad" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:45 +#: ../settings/security/third-party/microsoft.rst:40 msgid "" -"This reduces the category options to ``Support/*``, ``Internal/*`` and " -"``Others``. It also sets further required fields to visible." -msgstr "" - -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for support" +"Login to the `Microsoft Azure Portal `_ and " +"navigate to App registrations to create a new app. Provide the requested " +"information as follows and register your app." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:53 -msgid "Workflow Sales group" +#: ../settings/security/third-party/microsoft.rst:46 +msgid "Name:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:55 +#: ../settings/security/third-party/microsoft.rst:45 msgid "" -"This reduces the category options to ``Sales/*``, ``Internal/*`` and " -"``Others``." +"Any meaningful name fitting, this name will be displayed to users trying to " +"authenticate with this app." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for sales" +#: ../settings/security/third-party/microsoft.rst:49 +msgid "Choose one of the above mentioned account types (see Limitations)." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:68 -#: ../system/integrations/slack.rst:88 -msgid "The Result" +#: ../settings/security/third-party/microsoft.rst:51 +msgid "" +"The correct account type depends on your use case. If you want to use the " +"authentication internal only, choose the first option. If you're unsure, use " +"the \"Help me choose...\" link." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:63 -msgid "" -"This is what the agent would experience with the above workflows in place." +#: ../settings/security/third-party/microsoft.rst:58 +msgid "Redirect URI (optional):" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 +#: ../settings/security/third-party/microsoft.rst:56 msgid "" -"Workflow shows objects and limits options based on selections on the group" +"Select web and provide your callback URL. The callback URL looks like this: " +"``https://zammad.domain.tld/auth/microsoft_office365/callback``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:90 -msgid "Approval process" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to register a Microsoft app" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:71 -msgid "" -"In this case ``approved`` is visible to agents by default. For this " -"workflow, an additional role ``Approval person`` is required (no further " -"permissions)." +#: ../settings/security/third-party/microsoft.rst:71 +msgid "Within **API permissions** add the following permissions:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that restricts an approval attribute to specific roles" +#: ../settings/security/third-party/microsoft.rst:69 +msgid "``User.Read``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:81 -msgid "" -"This workflow may work best in combination with a :doc:`trigger ` but technically, this is not required." +#: ../settings/security/third-party/microsoft.rst:71 +msgid "Contacts" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:84 -msgid "" -"Select fields may be a better approach because they allow more values than " -"just a simple ``true`` or ``false``." +#: ../settings/security/third-party/microsoft.rst:71 +msgid "``Contacts.Read``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 +#: ../settings/security/third-party/microsoft.rst:73 msgid "" -"Workflow fixes possible values of \"Approved ?\" to a specific selection " -"depending on the users role" +"You can find these permissions within *Microsoft Graph → Delegated " +"permissions*." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:103 -msgid "State dependent mandatory fields" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to add required API permissions" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:93 +#: ../settings/security/third-party/microsoft.rst:80 msgid "" -"This workflow sets ``Category`` to mandatory if the agent wants to set the " -"states ``closed`` or ``pending close`` to enforce categorization." +"Within **Certificates & secrets** create a new client secret. Note down the " +"returned secret **value** for later. **Do not** use the secret ID!" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that sets fields to mandatory on specific states" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to create a new app secret" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 +#: ../settings/security/third-party/microsoft.rst:88 msgid "" -"Workflow sets category field to mandatory upon choosing closed or pending " -"close as state" +"From **Overview** copy your apps *Application (client) ID*. If you're using " +"a single tenant app, please also copy *Directory (tenant) ID*. You now have " +"all required information for Zammad." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:106 -msgid "Manual Ticket Handover Process" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to retreive application client and tenant IDs" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:108 -msgid "This example covers the handover of a ticket from one agent to another:" +#: ../settings/security/third-party/microsoft.rst:98 +msgid "Step 2 - Add App Credentials to Zammad" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:110 +#: ../settings/security/third-party/microsoft.rst:100 msgid "" -"When the ticket owner is modified, a new text field (\"Handover\") shows up " -"for a comment" +"Navigate to Security > Third-party Applications (Tab) within Zammad's admin " +"settings. Scroll down to the section *Authentication via Microsoft* and fill " +"in the required information." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:112 -msgid "" -"This may only be visible when the owner is changed, therefore it has to be " -"hidden in general" +#: ../settings/security/third-party/microsoft.rst:105 +msgid "App ID:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:114 -msgid "The input in this handover text field is mandatory" +#: ../settings/security/third-party/microsoft.rst:105 +msgid "This is your *Application (client) ID*." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:115 -msgid "" -"After submitting changes, the value of the handover field must be added as " -"an note to the ticket (via trigger)" +#: ../settings/security/third-party/microsoft.rst:108 +msgid "App secret:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:121 -msgid "Hiding handover field" +#: ../settings/security/third-party/microsoft.rst:108 +msgid "This is your *client secret* (value)." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Hiding the handover field in core workflows" +#: ../settings/security/third-party/microsoft.rst:113 +msgid "App Tenant ID:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:126 -msgid "Showing handover field and setting it to mandatory" +#: ../settings/security/third-party/microsoft.rst:111 +msgid "" +"**optional** only required for apps that use account type *Accounts in this " +"organizational directory only (Default Directory only - Single tenant).*" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Showing the handover field and set it as mandatory" +#: ../settings/security/third-party/microsoft.rst:115 +msgid "" +"Apply your settings by pressing submit and activate *Authentication via " +"Microsoft*." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:131 -msgid "Trigger writing handover input to a new article" +#: ../settings/security/third-party/microsoft.rst:None +msgid "" +"Screencast showing how to add app credentials and activating the\n" +"authentication method" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Write handover content to a new article" +#: ../settings/security/third-party/saml.rst:2 +msgid "SAML" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:133 +#: ../settings/security/third-party/saml.rst:4 msgid "" -"As a result, the ticket includes an article of the type note which includes " -"the predefined text and the handover comment." +"Connect your SAML (Security Assertion Markup Language) identity provider as " +"a single sign-on (SSO) method." msgstr "" -#: ../system/core-workflows/limitations.rst:6 -msgid "Core Workflows do not replace Triggers" +#: ../settings/security/third-party/saml.rst:7 +msgid "" +"SAML is an open standard for SSO authentication (among other things). Sign-" +"ins are shared across multiple **service providers** and managed by a " +"central **identity provider** (IdP)." msgstr "" -#: ../system/core-workflows/limitations.rst:5 +#: ../settings/security/third-party/saml.rst:11 msgid "" -"Workflows manipulate the behavior of fields. However, they do not set values " -"in fields because of actions." +"In this case, the service provider is Zammad, and the IdP is a software " +"service that you either host or subscribe to (*e.g.,* `Keycloak `_, `Redhat SSO Server `_, `ADFS `_, or `Okta `_)." msgstr "" -#: ../system/core-workflows/limitations.rst:16 -msgid "API calls are only partly affected" +#: ../settings/security/third-party/saml.rst:18 +msgid "" +"This guide assumes you are already using SAML within your organization (i." +"e., that your IdP is fully set up)." msgstr "" -#: ../system/core-workflows/limitations.rst:9 +#: ../settings/security/third-party/saml.rst:21 msgid "" -"Some options affect UI only and thus do not restrict responses and calls." +"Please note: Our instructions are based on connecting Zammad with Keycloak." msgstr "" -#: ../system/core-workflows/limitations.rst:11 -msgid "This affects the following actions:" +#: ../settings/security/third-party/saml.rst:25 +msgid "Step 1: Configure Your IdP" msgstr "" -#: ../system/core-workflows/limitations.rst:13 -msgid "select" +#: ../settings/security/third-party/saml.rst:28 +msgid "Add Zammad as a Client/App" msgstr "" -#: ../system/core-workflows/limitations.rst:14 -msgid "auto select" +#: ../settings/security/third-party/saml.rst:30 +msgid "" +"Import Zammad into your IdP using the XML configuration found at ``https://" +"your.zammad.domain/auth/saml/metadata``." msgstr "" -#: ../system/core-workflows/limitations.rst:15 -msgid "show" +#: ../settings/security/third-party/saml.rst:33 +msgid "" +"If your IdP doesn't support XML import, you will have to configure Zammad as " +"a new client/app manually using the above XML metadata file for reference." msgstr "" -#: ../system/core-workflows/limitations.rst:16 -msgid "hide" +#: ../settings/security/third-party/saml.rst:36 +msgid "For instance, when you see this tag:" msgstr "" -#: ../system/core-workflows/limitations.rst:25 -msgid "Some fields stay unavailable to customers" +#: ../settings/security/third-party/saml.rst:42 +msgid "" +"Set the **Assertion Consumer Service Binding URL** (sometimes also listed as " +"**Valid Redirect URIs**) to ``http://your.zammad.domain/auth/saml/callback``." msgstr "" -#: ../system/core-workflows/limitations.rst:19 -msgid "" -"For technical and security reasons, some default fields (the pale ones you " -"can't edit) stay unavailable for display and usage on customer permissions." +#: ../settings/security/third-party/saml.rst:47 +msgid "Set Up User Attribute Mapping" msgstr "" -#: ../system/core-workflows/limitations.rst:23 +#: ../settings/security/third-party/saml.rst:49 msgid "" -"If you require your customers to change e.g. priorities, please consider " -"using workarounds via :doc:`/system/objects` and :doc:`/manage/trigger`." +"Zammad requests the following user attributes (or “properties”) from the IdP:" msgstr "" -#: ../system/core-workflows/limitations.rst:29 -msgid "Ticket title changes not supported in edit mask" +#: ../settings/security/third-party/saml.rst:51 +msgid "Email address (``email``)" msgstr "" -#: ../system/core-workflows/limitations.rst:28 -msgid "" -"It is currently not possible to perform changes of the ticket title in the " -"edit mask (e.g. renaming, set to read-only)." +#: ../settings/security/third-party/saml.rst:52 +msgid "Full name (``name``)" msgstr "" -#: ../system/core-workflows/limitations.rst:37 -msgid "What is out of scope of Core Workflows?" +#: ../settings/security/third-party/saml.rst:53 +msgid "Given name (``first_name``)" msgstr "" -#: ../system/core-workflows/limitations.rst:32 -msgid "" -"There are some things that would count as workflow but are either done via :" -"doc:`/manage/trigger` or :doc:`/manage/scheduler`." +#: ../settings/security/third-party/saml.rst:54 +msgid "Family name (``last_name``)" msgstr "" -#: ../system/core-workflows/limitations.rst:35 -msgid "Such as (but not limited to):" +#: ../settings/security/third-party/saml.rst:56 +msgid "" +"You may need to set up “mappers” (or “mappings”) to tell your IdP how user " +"attributes in SAML correspond to those in Zammad. For a more detailed " +"breakdown, refer to the XML metadata file referenced in the previous section." msgstr "" -#: ../system/core-workflows/limitations.rst:37 -msgid "up- or downgrade permissions of users" +#: ../settings/security/third-party/saml.rst:62 +msgid "Per-IdP Instructions" msgstr "" -#: ../system/core-workflows/limitations.rst:38 -msgid "affecting article creation or listing" +#: ../settings/security/third-party/saml.rst:102 +msgid "Keycloak" msgstr "" -#: ../system/data-privacy.rst:2 -msgid "Data Privacy" +#: ../settings/security/third-party/saml.rst:65 +msgid "" +"**To add Zammad as a client,** save the XML configuration to disk (``https://" +"your.zammad.domain/auth/saml/metadata``) and use **Clients > Clients list > " +"Import client** in the Keycloak admin panel." msgstr "" -#: ../system/data-privacy.rst:4 +#: ../settings/security/third-party/saml.rst:70 msgid "" -"For compliance with GDPR and other data privacy laws, you may wish to " -"**permanently delete users from the system**, along with **all of their " -"associated tickets**." +"To help Zammad **match its own user accounts to Keycloak users**, create a " +"user attribute (or “property”) mapper. In **Clients list**, click on your " +"newly created Client ID, choose the tab **Client scopes** and click on the " +"link which refers to your Zammad instance. Choose **Add mapper > By " +"configuration > User Property** and create a mapper with the following " +"entries:" 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 `!" +#: ../settings/security/third-party/saml.rst:78 +msgid "**Name**" msgstr "" -#: ../system/data-privacy.rst:12 -msgid "" -"Access to this panel requires ``admin.data_privacy`` permissions (introduced " -"in Zammad 3.5)." +#: ../settings/security/third-party/saml.rst:80 +msgid "**Mapper Type**" msgstr "" -#: ../system/data-privacy.rst:15 -msgid "" -"On older systems that have not been updated yet, customers can also be :docs:" -"`deleted via the Zammad console `." +#: ../settings/security/third-party/saml.rst:81 +msgid "``User Property``" msgstr "" -#: ../system/data-privacy.rst:22 -msgid "User deletion dialog in the Data Privacy panel" +#: ../settings/security/third-party/saml.rst:82 +msgid "**Property**" msgstr "" -#: ../system/data-privacy.rst:22 -msgid "" -"The user deletion dialog lists some of the tickets that will be removed from " -"the system along with the user." +#: ../settings/security/third-party/saml.rst:83 +msgid "``emailAddress``" msgstr "" -#: ../system/data-privacy.rst:27 -msgid "Deleting Users via GUI" +#: ../settings/security/third-party/saml.rst:84 +msgid "**SAML Attribute Name**" msgstr "" -#: ../system/data-privacy.rst:29 -msgid "🔥 **All deletions are FINAL!**" +#: ../settings/security/third-party/saml.rst:86 +msgid "**SAML Attribute NameFormat**" msgstr "" -#: ../system/data-privacy.rst:31 -msgid "Once you click “Delete”, the action cannot be canceled or undone." +#: ../settings/security/third-party/saml.rst:87 +msgid "``basic``" msgstr "" -#: ../system/data-privacy.rst:33 +#: ../settings/security/third-party/saml.rst:89 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." +"In the example above, we're telling Zammad that whenever it receives a SAML " +"login request, it should take the ``email`` property from Keycloak, look for " +"a Zammad user with the same ``email`` attribute, and create a new session " +"for that user." msgstr "" -#: ../system/data-privacy.rst:36 -msgid "**The following records cannot be deleted:**" +#: ../settings/security/third-party/saml.rst:95 +msgid "" +"If your Keycloak users' email addresses are stored on another property (*e." +"g.,* ``username``), adjust accordingly." msgstr "" -#: ../system/data-privacy.rst:38 -msgid "your own account" +#: ../settings/security/third-party/saml.rst:98 +msgid "" +"Back in **Settings**, enter the Client ID (``https://your.zammad.domain/auth/" +"saml/metadata``) in the field **Master SAML Processing URL**." msgstr "" -#: ../system/data-privacy.rst:39 -msgid "the system's last remaining administrator account" +#: ../settings/security/third-party/saml.rst:101 +msgid "You also need to enable **Sign assertions**." msgstr "" -#: ../system/data-privacy.rst:42 -msgid "Step 1: Find a User / Confirm Deletion" +#: ../settings/security/third-party/saml.rst:105 +msgid "Step 2: Configure Zammad" msgstr "" -#: ../system/data-privacy.rst:44 -msgid "There are three ways to access the user deletion dialog:" +#: ../settings/security/third-party/saml.rst:107 +msgid "" +"Enable SAML and enter your IdP's details in the Admin Panel under **Settings " +"> Security > Third Party Applications > Authentication via SAML**:" msgstr "" -#: ../system/data-privacy.rst:51 -msgid "**from the user's profile**" +#: ../settings/security/third-party/saml.rst:None +msgid "Example configuration of SAML part 1" msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Accessing the user deletion dialog in a user profile" +#: ../settings/security/third-party/saml.rst:119 +msgid "Display name" msgstr "" -#: ../system/data-privacy.rst:51 -msgid "Click **Action > Delete**." +#: ../settings/security/third-party/saml.rst:116 +msgid "" +"Allows you to define a custom button name for SAML. This helps your users to " +"understand better what the button on the login page does." msgstr "" -#: ../system/data-privacy.rst:58 -msgid "**in the “Manage > Users” Admin Panel**" +#: ../settings/security/third-party/saml.rst:119 +msgid "Defaults to ``SAML``." msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Accessing the user deletion dialog under “Users” in the Admin Panel" +#: ../settings/security/third-party/saml.rst:123 +msgid "IDP SSO target URL" msgstr "" -#: ../system/data-privacy.rst:58 -msgid "Use the **⋮ Actions** menu for the target user." +#: ../settings/security/third-party/saml.rst:122 +msgid "" +"This is the target URL Zammad shall redirect to when the user presses the " +"SAML button. For Keycloak, this needs to look like https://your.domain/" +"realms/your-realm/protocol/saml" msgstr "" -#: ../system/data-privacy.rst:66 ../system/data-privacy.rst:104 -msgid "**in the “System > Data Privacy” Admin Panel**" +#: ../settings/security/third-party/saml.rst:127 +msgid "IDP single logout target URL" msgstr "" -#: ../system/data-privacy.rst:0 +#: ../settings/security/third-party/saml.rst:126 msgid "" -"Accessing the user deletion dialog under “Data Privacy” in the Admin Panel" +"This is the URL to which the single logout request and response should be " +"sent." msgstr "" -#: ../system/data-privacy.rst:65 +#: ../settings/security/third-party/saml.rst:131 +msgid "IDP certificate" +msgstr "" + +#: ../settings/security/third-party/saml.rst:130 msgid "" -"Use the **New Deletion Task** button. Search for users by name or email " -"address." +"The public certificate of your IDP for Zammad to verify during the callback " +"phase." msgstr "" -#: ../system/data-privacy.rst:79 -msgid "**Delete organizations**" +#: ../settings/security/third-party/saml.rst:145 +msgid "IDP certificate fingerprint" msgstr "" -#: ../system/data-privacy.rst:69 +#: ../settings/security/third-party/saml.rst:134 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:" +"The fingerprint of your IDPs public certificate to verify during callback " +"phase." msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Deleting an organization via the user deletion dialog" +#: ../settings/security/third-party/saml.rst:137 +msgid "🔏 **For the IdP certificate / certificate fingerprint:**" msgstr "" -#: ../system/data-privacy.rst:78 +#: ../settings/security/third-party/saml.rst:139 msgid "" -"If this option does not appear, make sure there are no pending deletion " -"tasks for other customers from this organization." +"Provide **only one or the other**—do not provide both! (Between the two, we " +"recommend the signing certificate itself: fingerprints use SHA-1, which `has " +"been broken for a while now `_.)" msgstr "" -#: ../system/data-privacy.rst:82 -msgid "Step 2: Monitor Deletion Job Status" +#: ../settings/security/third-party/saml.rst:144 +msgid "" +"**Keycloak users:** Find your certificate in the Keycloak admin panel under " +"**Realm Settings > Keys > Algorithm: RS256 > Certificate**." msgstr "" -#: ../system/data-privacy.rst:84 +#: ../settings/security/third-party/saml.rst:151 +msgid "Name identifier format" +msgstr "" + +#: ../settings/security/third-party/saml.rst:148 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:" +"This is the unique identifiers field type. Usually it should be ``urn:oasis:" +"names:tc:SAML:1.1:nameid-format:emailAddress``." msgstr "" -#: ../system/data-privacy.rst:98 -msgid "**in the Activity Stream**" +#: ../settings/security/third-party/saml.rst:151 +msgid "Zammad **expects an email address as unique identifier**!" msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Activity Stream showing data privacy tasks" +#: ../settings/security/third-party/saml.rst:155 +msgid "UID attribute name" msgstr "" -#: ../system/data-privacy.rst:94 +#: ../settings/security/third-party/saml.rst:154 msgid "" -"For each deleted user, the Activity Stream will be updated twice—once when " -"the task is created, and once when it's complete." +"Here you can define an attribute that uniquely identifies the user. If " +"unset, the name identifier returned by the IDP is used." msgstr "" -#: ../system/data-privacy.rst:97 -msgid "" -"These notifications are only visible to users with ``admin.data_privacy`` " -"permissions." +#: ../settings/security/third-party/saml.rst:None +msgid "Example configuration of SAML part 2" msgstr "" -#: ../system/data-privacy.rst:0 +#: ../settings/security/third-party/saml.rst:163 msgid "" -"The task list within Data Privacy shows removals being in progress and " -"completed." +"Decide if the certificate for the connection to the IdP service has to be " +"verified or not (default: ``yes``)." msgstr "" -#: ../system/data-privacy.rst:107 -msgid "Frequently Asked Questions" +#: ../settings/security/third-party/saml.rst:169 +msgid "Signing & Encrypting" msgstr "" -#: ../system/data-privacy.rst:121 -msgid "What happens if I receive an email from a deleted customer?" -msgstr "" - -#: ../system/data-privacy.rst:110 +#: ../settings/security/third-party/saml.rst:169 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." +"Define if you want to sign, encrypt, do both or nothing for the requests." msgstr "" -#: ../system/data-privacy.rst:115 -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**." +#: ../settings/security/third-party/saml.rst:179 +msgid "Certificate (PEM)" msgstr "" -#: ../system/data-privacy.rst:130 -msgid "What about user information stored in internal notes or other messages?" +#: ../settings/security/third-party/saml.rst:172 +msgid "" +"Paste the public certificate of your Zammad SAML client, if you want to " +"encrypt the requests." msgstr "" -#: ../system/data-privacy.rst:124 -msgid "" -"The deletion process removes **user accounts and associated tickets only**." +#: ../settings/security/third-party/saml.rst:175 +msgid "Make sure the certificate is:" msgstr "" -#: ../system/data-privacy.rst:126 -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." +#: ../settings/security/third-party/saml.rst:177 +msgid "already valid and not yet expired" msgstr "" -#: ../system/data-privacy.rst:137 -msgid "I deleted an user and can still see a message they sent!" +#: ../settings/security/third-party/saml.rst:178 +msgid "no CA certificate" msgstr "" -#: ../system/data-privacy.rst:133 -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." +#: ../settings/security/third-party/saml.rst:179 +msgid "valid for signing and encrypting" msgstr "" -#: ../system/data-privacy.rst:141 -msgid "I removed a customer, now my reporting is off!" +#: ../settings/security/third-party/saml.rst:185 +msgid "Private key (PEM)" msgstr "" -#: ../system/data-privacy.rst:140 +#: ../settings/security/third-party/saml.rst:182 msgid "" -"When removing users and their tickets, all references are removed. This also " -"affects e.g. Reporting - these information are lost." +"Paste the private key of your Zammad SAML client here, if you want to sign " +"the requests." msgstr "" -#: ../system/data-privacy.rst:145 -msgid "How long does Zammad store created tasks?" +#: ../settings/security/third-party/saml.rst:185 +msgid "Make sure the key is an RSA key with a length of at least 2048 bits." msgstr "" -#: ../system/data-privacy.rst:144 -msgid "" -"Please see the on-premise data section of the :docs:`data privacy ` chapter." +#: ../settings/security/third-party/saml.rst:188 +msgid "Private key secret" msgstr "" -#: ../system/data-privacy.rst:150 -msgid "What about re-assigned tickets? I want to delete them, too." +#: ../settings/security/third-party/saml.rst:188 +msgid "If your private key is secured with a secret, you can provide it here." msgstr "" -#: ../system/data-privacy.rst:148 -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." +#: ../settings/security/third-party/saml.rst:192 +msgid "Your callback URL" msgstr "" -#: ../system/data-privacy.rst:154 -msgid "Why are there so many deletion task entries, I didn't create them!" +#: ../settings/security/third-party/saml.rst:191 +msgid "" +"This URL is needed for your IdP configuration so it knows where to redirect " +"to after successful authentication." msgstr "" -#: ../system/data-privacy.rst:153 +#: ../settings/security/third-party/saml.rst:194 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." +"After saving your input by clicking on the \"Submit\" button, Zammad " +"verifies the provided keys/certificates (e.g. if they are valid for signing/" +"encrypting and if they aren't expired)." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:2 -msgid "Admin Panel Reference" +#: ../settings/security/third-party/saml.rst:199 +msgid "" +"See :ref:`automatic account linking ` for details " +"on how to link existing Zammad accounts to IdP accounts." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:None -msgid "Screenshot of Checkmk settings overview" +#: ../settings/security/third-party/saml.rst:205 +msgid "Automatic account linking doesn't work" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:12 +#: ../settings/security/third-party/saml.rst:206 msgid "" -"Which :doc:`group ` should Checkmk tickets be assigned " -"to as a default (*i.e.,* when none is specified)?" +"Have you double-checked your IdP's user attribute mapping configuration?" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:15 -msgid "(Applies to :ref:`API alerts ` only.)" +#: ../settings/security/third-party/twitter.rst:4 +msgid "" +"It is possible to create a quick login for your helpdesk via Twitter. To do " +"so, you need to follow these steps:" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:21 -msgid "Auto close" +#: ../settings/security/third-party/twitter.rst:8 +msgid "Register Twitter App" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:18 -msgid "" -"Should Zammad automatically close tickets if a service has recovered on its " -"own?" +#: ../settings/security/third-party/twitter.rst:10 +msgid "Go to https://dev.twitter.com/apps and login with your account." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:21 -msgid "(Agents will receive notifications for such closures as appropriate.)" +#: ../settings/security/third-party/twitter.rst:15 +msgid "Click on \"Create App\"" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:30 -msgid "Auto-close state" +#: ../settings/security/third-party/twitter.rst:None +msgid "new app page" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:24 -msgid "What ticket state should be applied when “auto-closing” a ticket?" +#: ../settings/security/third-party/twitter.rst:20 +msgid "" +"Enter app settings. As \"Callback URL\" you need to enter ``https://" +"zammad_host/api/v1/external_credentials/twitter/callback``. You need to " +"replace ``zammad_host`` with the domain of your Zammad system." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:26 +#: ../settings/security/third-party/twitter.rst:24 msgid "" -"You can choose from the seven built-in ticket states. If these states aren't " -"enough for you, you can :ref:`define a new ticket state ` for this purpose as well. This can be useful for tracking " -"tickets with :doc:`reports `, for example." +"After the app has been created, update the application icon and organization " +"attributes." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:35 -#: ../system/integrations/cti/includes/recent-logs.include.rst:2 -#: ../system/integrations/ldap/index.rst:74 -#: ../system/integrations/pgp/index.rst:106 -msgid "Recent Logs" +#: ../settings/security/third-party/twitter.rst:None +msgid "set permissions to receive and send direct messages" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:None -msgid "Screenshot of Checkmk \"Recent Logs\" section" +#: ../settings/security/third-party/twitter.rst:30 +msgid "" +"Next we need to set ``read, write and access direct messages`` permissions " +"for the app." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:41 -msgid "" -"If you're having trouble getting Zammad and Checkmk to play nicely together, " -"this section can help you troubleshoot." +#: ../settings/security/third-party/twitter.rst:None +msgid "click on Keys & Access Token, note them" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:44 +#: ../settings/security/third-party/twitter.rst:36 msgid "" -"It contains a record of the fifty most recent transactions that Zammad knows " -"about, including each one's request/response details and return status." +"Go to \"Keys and Access Token\" tab and note the \"Consumer Key\" and " +"\"Consumer Secret\"." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:2 -msgid "API Reference" +#: ../settings/security/third-party/twitter.rst:40 +msgid "Configure Zammad as Twitter App" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:4 +#: ../settings/security/third-party/twitter.rst:42 msgid "" -"For most users, :ref:`the sample scripts from the Setup Guide ` will do the job just fine. But if you want more fine-grained control" -"—for instance, to create high- and low-priority tickets for different types " -"of system events—then you'll have to customize the data those scripts send " -"to Zammad." +"Go to \"Admin > Security > Twitter > Third Party Applications > Twitter\" " +"Section." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:15 -msgid "" -"This custom script will automatically set all tickets it creates to **high " -"priority** and **assign them to charlie@chrispresso.com**." +#: ../settings/security/third-party/twitter.rst:None +msgid "Admin > Security > Third Party Applications" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:32 -msgid "How Does it Work?" +#: ../settings/security/third-party/twitter.rst:48 +msgid "" +"Fill in the \"Twitter Key\" and the \"Twitter Secret\" and click the " +"\"Submit\" button." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:34 +#: ../settings/security/third-party/twitter.rst:51 msgid "" -"There are two kinds of data you can pass to the API, both in the form of key-" -"value pairs:" +"Now you can link accounts via \"Avatar > Profile > Link Accounts\" or login " +"via Zammad login page." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:44 -msgid "Checkmk parameters" +#: ../settings/security/two-factor.rst:11 +msgid "Two-factor Authentication Methods" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:38 -msgid "" -"are required, and make up the **contents** of the resulting tickets/" -"articles. They also determine whether an event creates a new ticket or " -"updates/closes an existing one." +#: ../settings/security/two-factor.rst:2 +msgid "Two-Factor Authentication" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:42 +#: ../settings/security/two-factor.rst:4 msgid "" -"These are the only values used in the sample scripts. **Use them as-is**; " -"technically, they can be customized, but it's hard to imagine a good reason " -"for it." +"Two-factor authentication (2FA) enhances the security of Zammad accounts by " +"adding an extra layer of verification beyond a password. It requires users " +"to provide two different types of authentication factors, typically " +"something they know (like a password) and something they possess (like a " +"mobile device or a security token), to ensure that only authorized " +"individuals can access the account." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:52 -msgid "Ticket attributes" +#: ../settings/security/two-factor.rst:19 +msgid "Enable Recovery Codes" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:47 +#: ../settings/security/two-factor.rst:21 msgid "" -"are optional, and can be used to **adjust settings** on newly created " -"tickets (*e.g.,* set the owner, group, priority, or state)." +"Recovery codes are one-time use security codes that can be used by the user " +"if they lose access to their other two-factor authentication methods. They " +"cannot be used on their own, they can only be activated if at least one two-" +"factor authentication method is enabled." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:50 -msgid "" -"If you want to customize your Checkmk alert script, do it with these. Simply " -"add an extra “form” option for each one (``-F \"key=value\"``) to your " -"script's ``curl`` command line, as in the example above." +#: ../settings/security/two-factor.rst:None +msgid "Enable Recovery Codes Setting" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:54 -msgid "💡 **It's just an API endpoint!**" +#: ../settings/security/two-factor.rst:30 +msgid "" +"Recovery codes can only be used as a backup method. If enabled, they will be " +"automatically generated for the user once they set up their initial two-" +"factor authentication method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:56 +#: ../settings/security/two-factor.rst:34 msgid "" -"When using Checkmk integration, messages need to be formatted in a certain " -"way, but that *doesn't mean the messages actually have to come from Checkmk*." +"The user will be asked to print out or save the generated recovery codes in " +"a safe place. Once used, a recovery code cannot be reused." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:59 +#: ../settings/security/two-factor.rst:37 msgid "" -"If you use another monitoring tool that's not officially supported by " -"Zammad, there's probably a way to make it work with your Checkmk callback " -"URL." +"Users will also have an option to regenerate their recovery codes at any " +"time, which invalidates already existing recovery codes and provides them " +"with a list of fresh codes." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:63 -msgid "Checkmk Parameters" +#: ../settings/security/two-factor.rst:41 +msgid "" +"After you enable this setting, when the user completes a setup of their " +"initial two-factor authentication method, they will be presented with a list " +"of recovery codes and instructed to save them for later use." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:65 -msgid "" -"When a notification is received, Zammad creates a new article containing the " -"details of the event that triggered it:" +#: ../settings/security/two-factor.rst:None +msgid "Recovery Codes Generation Modal Dialog" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:None -msgid "Checkmk article body" +#: ../settings/security/two-factor.rst:50 +msgid "Enforce the Set Up of the Two-Factor Authentication" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:72 +#: ../settings/security/two-factor.rst:52 msgid "" -"These details come from the fields listed below, which correspond to " -"parameters provided by Checkmk (``$NOTIFY_*``)." +"In case you wish to require your users to set up at least one two-factor " +"authentication method for their account, you can do this by selecting " +"specific user roles the requirement applies to in **Enforced for user " +"roles** setting. Of course you must have at least one two-factor " +"authentication method enabled for this setting to take effect." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:75 -msgid "**Required fields are marked with an asterisk (\\*).**" +#: ../settings/security/two-factor.rst:None +msgid "Enforced for User Roles Setting" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:79 -msgid "event_id\\*" +#: ../settings/security/two-factor.rst:62 +msgid "" +"After you change this setting, if the user has one of the selected roles on " +"their account, they will be forced to set up the two-factor authentication " +"upon next sign in or application reload." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:78 +#: ../settings/security/two-factor.rst:66 msgid "" -"A unique ID for the system event. (``$NOTIFY_SERVICEPROBLEMID`` / " -"``$NOTIFY_HOSTPROBLEMID``)" +"A modal dialog with instructions will be shown, and they will not be able to " +"do any work before they set up at least one two-factor method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:86 -msgid "host\\*" +#: ../settings/security/two-factor.rst:None +msgid "Modal Dialog for Enforcing Two-Factor Authentication Set Up" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:82 +#: ../settings/security/two-factor.rst:74 +msgid "Reset Two-Factor Authentication for a Specific User" +msgstr "" + +#: ../settings/security/two-factor.rst:76 msgid "" -"The hostname of the system that the event originated from. " -"(``$NOTIFY_HOSTNAME``)" +"In case an user isn't able to login anymore because of an inaccessible " +"second factor, you can reset the user's 2FA method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:85 +#: ../settings/security/two-factor.rst:79 msgid "" -"Used to determine if a new event belongs to an existing ticket. Also used in " -"the subject line of the resulting article (“ is ”)." +"To do this, go to the user management and search for the relevant user. " +"After you found the account, click the button in the action column and " +"select \"Manage Two-Factor Authentication\":" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:96 -msgid "service" +#: ../settings/security/two-factor.rst:None +msgid "Context menu in action column in user management" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:89 +#: ../settings/security/two-factor.rst:87 msgid "" -"The name of the service that the event originated from. " -"(``$NOTIFY_SERVICEDESC``)" +"After selecting this, you can see a dialog where you can either reset one " +"2FA method or reset all of the user's 2FA methods:" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:92 -msgid "Used to determine if a new event belongs to an existing ticket." +#: ../settings/security/two-factor.rst:None +msgid "Dialog for resetting user's 2FA method" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:94 -#: ../system/integrations/checkmk/api-reference.rst:110 -msgid "Displayed as ``-`` when omitted." +#: ../settings/security/two-factor.rst:94 +msgid "" +"Choose the fitting one, click on the corresponding \"Remove ...\" button and " +"confirm your action. The user now has to setup a new 2FA method, depending " +"on your 2FA configuration." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:104 -msgid "state\\*" +#: ../settings/security/two-factor/authenticator-app.rst:2 +msgid "Authenticator App" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:99 +#: ../settings/security/two-factor/authenticator-app.rst:4 msgid "" -"The current state of the service or host in question. " -"(``$NOTIFY_SERVICESTATE`` / ``$NOTIFY_HOSTSTATE``)" +"The authenticator app method is a type of two-factor authentication that " +"uses a mobile application to generate one-time codes for account " +"verification. After setting up the authenticator app on their device, the " +"user links it to their Zammad account." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:102 +#: ../settings/security/two-factor/authenticator-app.rst:12 msgid "" -"Used to detect when a ticket should be auto-closed (*i.e.,* on ``OK``/" -"``UP``). Also used in the subject line of the resulting article (“ is " -"”)." +"When logging in, the user is prompted to enter a time-sensitive code " +"generated by the app, in addition to their password. This code acts as the " +"second factor of authentication, providing an extra layer of security as it " +"changes periodically and is unique to the user's device." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:110 -msgid "text" +#: ../settings/security/two-factor/authenticator-app.rst:None +msgid "Security Code in Google Authenticator App" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:107 +#: ../settings/security/two-factor/authenticator-app.rst:22 msgid "" -"The output of the process that triggered the event. " -"(``$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" +"The app generates codes based on a shared secret key stored securely on both " +"the user's device and the server, ensuring a synchronized and secure " +"authentication process. The method of generating the codes is sometimes also " +"called TOTP (time-based one-time password)." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:121 -msgid "" -"The Object Manager attribute panel displays built-in and custom\n" -"attribute names." +#: ../settings/security/two-factor/authenticator-app.rst:28 +msgid "Enabling the Authenticator App Method" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:121 -msgid "Find a complete list of ticket attributes in the Object Manager." +#: ../settings/security/two-factor/authenticator-app.rst:30 +#: ../settings/security/two-factor/security-keys.rst:28 +msgid "To enable the method, just toggle the switch on in the settings." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:123 -msgid "" -"Ticket attributes are entirely optional, and can be used to customize the " -"tickets that Checkmk creates. (Note that these attributes will be ignored if " -"a new event belongs to an existing ticket.)" +#: ../settings/security/two-factor/authenticator-app.rst:None +msgid "Authenticator App Switch in Settings" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:128 +#: ../settings/security/two-factor/authenticator-app.rst:36 msgid "" -"Why would you want to do this? Maybe you have only one IT guy, and all " -"system monitoring issues should be automatically assigned to him. Or, maybe " -"you're creating multiple notification rules so that database outages take " -"higher priority than disk space warnings." +"Now the users will be able to set up this two-factor authentication method " +"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " +"Once they do, on next sign-in with password, they will be asked to provide " +"an additional security code generated by their mobile device." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:135 -msgid "In most cases, you'll probably want to set one of the following:" +#: ../settings/security/two-factor/security-keys.rst:2 +msgid "Security Keys" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:137 -msgid "group" +#: ../settings/security/two-factor/security-keys.rst:4 +msgid "" +"The security keys method is a type of a two-factor authentication that uses " +"Web Authentication API in the browser for verifying user's identity. The " +"user can register multiple hardware or software security keys with their " +"Zammad account and then they can use it during the sign-in process." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:139 -msgid "state" +#: ../settings/security/two-factor/security-keys.rst:12 +msgid "" +"When logging in, the user is prompted to provide the same security key they " +"registered with their account, in addition to their password. This key acts " +"as the second factor of authentication, providing an extra layer of security." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:140 -msgid "priority" +#: ../settings/security/two-factor/security-keys.rst:None +msgid "Security Key dialog in Safari on macOS" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:142 +#: ../settings/security/two-factor/security-keys.rst:21 msgid "" -"but in practice, you can set almost any attribute, including :doc:`custom " -"ones you created through the Object Manager `." -msgstr "" - -#: ../system/integrations/checkmk/api-reference.rst:145 -msgid "Please note that the following attributes are **not customizable**:" +"The type of the key can range from hardware USB sticks to passkeys stored in " +"a device of user's choice. Which type can be used depends on the browser " +"flavor and the platform of the user." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:147 -msgid "title" +#: ../settings/security/two-factor/security-keys.rst:26 +msgid "Enabling the Security Keys Method" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:148 -msgid "id" +#: ../settings/security/two-factor/security-keys.rst:None +msgid "Security Keys Switch in Settings" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:149 -msgid "ticket number" +#: ../settings/security/two-factor/security-keys.rst:34 +msgid "" +"Now the users will be able to set up this two-factor authentication method " +"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " +"Once they do, on next sign-in with password, they will be asked to provide " +"the same security key they registered during the setup." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:151 -msgid "created_by_id" +#: ../settings/system/system-selfhosted.include.rst:3 +msgid "" +"Below settings are only available to self hosted users. In hosted " +"environments we're handling these settings for you to ensure service " +"stability." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:152 -msgid "updated_by_id" +#: ../settings/system/base.rst:11 +msgid "Fully Qualified Domain Name" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:155 -msgid "Which Values Can Be Set?" +#: ../settings/system/base.rst:7 +msgid "The URL of your Zammad installation." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:157 -msgid "😵 **Invalid values → unpredictable behavior**" +#: ../settings/system/base.rst:9 ../settings/system/base.rst:17 +msgid "This setting is used within :doc:`/misc/variables` and notifications." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:159 -msgid "" -"If you provide a value that Zammad doesn't understand (*e.g.,* ``-F " -"\"priority=high\"``), it's not always clear what will happen. In some cases, " -"a ticket will be created with the default values instead - but in others, it " -"may not be created at all!" +#: ../settings/system/system-base.include.rst:1 +msgid "It is automatically set by the *Getting Started wizard*." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:164 -msgid "So what values does Zammad understand, then? Well, it depends..." +#: ../settings/system/system-base.include.rst:5 +msgid "Changing this setting also changes callback URLs for your channels etc." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:168 -msgid "Use an email address or username:" +#: ../settings/system/system-base.include.rst:6 +msgid "This setting can have negative affects on being able to login." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:190 -msgid "group & priority" +#: ../settings/system/base.rst:19 +msgid "HTTP type" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:175 -msgid "Refer to the dropdown menus in the ticket pane:" +#: ../settings/system/base.rst:14 +msgid "" +"The HTTP type tells your installation how your clients connect. This is " +"relevant for authentication and cookie security." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:0 -msgid "See possible values for certain attributes in the ticket pane." +#: ../settings/system/base.rst:31 +msgid "SystemID" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:187 -msgid "🙅 **Ticket state CANNOT be set this way!**" +#: ../settings/system/base.rst:22 +msgid "" +"This ID is being used within your ticket number. In case you're " +"communicating with another ticket system with similar ticket number schemes " +"this ID greatly reduces the risk of false follow ups." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:189 +#: ../settings/system/base.rst:26 msgid "" -"Why? Because ``-F \"state=...\"`` is already used :ref:`as a Checkmk " -"parameter `." +"The SystemID is randomly selected upon installation of Zammad (``1-99``)." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:222 -msgid "Everything Else" +#: ../settings/system/base.rst:30 +msgid "" +"**Do not** change this setting in a productive system! Your Zammad " +"installation may no longer recognize old ticket number based follow ups upon " +"change!" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:193 -msgid "" -"To set any other attributes, it helps to know your way around the :docs:" -"`rails console `. Valid values are those that you can " -"set with a string:" +#: ../settings/system/frontend.rst:2 +msgid "Frontend" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:218 -msgid "These values can then be passed directly to the API:" +#: ../settings/system/frontend.rst:22 +msgid "Core Workflow Ajax Mode" msgstr "" -#: ../system/integrations/checkmk/index.rst:16 -msgid "How does it work?" +#: ../settings/system/frontend.rst:6 +msgid "" +"This setting allows administrators to enforce :doc:`/system/core-workflows` " +"to use Ajax-Calls instead of web sockets. You'll usually only need this if " +"you experience serious issues as noted below." msgstr "" -#: ../system/integrations/checkmk/index.rst:2 -msgid "Checkmk" +#: ../settings/system/frontend.rst:10 +msgid "**🤓 Possible (technical) reasons**" msgstr "" -#: ../system/integrations/checkmk/index.rst:4 +#: ../settings/system/frontend.rst:12 msgid "" -"`Checkmk `_ is a powerful IT monitoring tool that can " -"send real-time status alerts to Zammad via email or REST API. Set these " -"alerts up in Checkmk, and Zammad will automatically create, update, and " -"close tickets based on the health of your system:" +"In some cases, your network structure (e.g. firewalls, proxies) may " +"disconnect long web socket connections. This leads to select fields staying " +"empty (e.g. owner selection *after* selecting your group) or fields not " +"shown / hidden (e.g. when switching to or from pending states, the \"pending " +"till\" field not showing / hiding)." msgstr "" -#: ../system/integrations/checkmk/index.rst:14 -msgid "Screenshot of ticket created by Checkmk notifications" +#: ../settings/system/frontend.rst:18 +msgid "" +"Please keep in mind that the Ajax fallback may cause serious pressure on " +"your application server. If you have the choice stick to web sockets." msgstr "" -#: ../system/integrations/checkmk/index.rst:14 -msgid "Multiple alerts, same ticket." +#: ../settings/system/frontend.rst:22 +msgid "Default: ``no`` (inactive)" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:2 -msgid "Setup Guide" +#: ../settings/system/frontend.rst:53 +msgid "Show calendar weeks in the picker of date/datetime fields" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:4 +#: ../settings/system/frontend.rst:25 msgid "" -"Whenever the Checkmk integration is enabled, Zammad listens for messages on " -"its API and over email. As long as those messages follow the required " -"format, Zammad will create new tickets (or find and update existing ones) " -"based on the message contents." +"With this setting you can instruct Zammad to provide week number display " +"globally for all users. Calendar with week number display are usually used " +"in business sectors and may not be relevant for everyone." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:10 +#: ../settings/system/frontend.rst:29 msgid "" -"That means that “setting up Checkmk integration” is simply a matter of " -"**adding configuration to your Checkmk site**: telling it when to send these " -"messages and what to say. To do that, you'll need to create a new " -"**notification rule** (see `Checkmk's official docs `_ for help with that)." +"This setting affects *all areas* - you'll also see week numbers in the admin " +"panel for e.g. triggers and macros." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:17 -msgid "" -"As part of this new rule, you'll have to choose a **notification method** " -"(*i.e.,* a script to execute whenever the rule is triggered). This script " -"will be written by you (samples below), and contain the logic for sending " -"API/email messages to Zammad:" +#: ../settings/system/frontend.rst:32 +msgid "Default: ``no`` (not shown)" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:26 -msgid "Checkmk \"New Rule\" dialog" +#: ../settings/system/frontend.rst:53 +msgid "Here's the difference:" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:26 -msgid "" -"Find your custom scripts in the Checkmk WATO under **Notifications > New " -"Rule > Notification Method**." +#: ../settings/system/frontend.rst:0 +msgid "Screenshot showing Zammad's date picker (in the default way)" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:29 -msgid "" -"Once you're done setting up your new rule, you're all set! New tickets " -"should start coming in and auto-updating any time your rule is triggered." +#: ../settings/system/frontend.rst:41 +msgid "Set to ``no``" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:33 +#: ../settings/system/frontend.rst:0 msgid "" -"(If you need help troubleshooting, be sure to check the :ref:`checkmk-recent-" -"logs`.)" +"Screenshot showing Zammad's date picker with\n" +"week numbers enabled" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:38 -msgid "API Alerts" +#: ../settings/system/frontend.rst:50 +msgid "Set to ``yes``" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:40 +#: ../settings/system/index.rst:4 msgid "" -"To add these scripts in the Checkmk WATO, copy them into your Checkmk " -"installation directory and make them executable. (Be sure to replace the " -"``zammad.example.com`` callback URL with the one found in your admin panel.)" +"For your overview we split each tab within system settings into its own page:" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:60 -msgid "Service notification" +#: ../settings/system/index.rst:16 +msgid "Console Based Settings" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:46 +#: ../settings/system/index.rst:18 msgid "" -"For updates on the status of the software running on your server (*e.g.,* " -"postgres)." +"There's some console based settings we didn't put into the UI. However, you " +"may find them helpful - you can find them in our :docs:`hidden settings ` section." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:75 -msgid "Host notification" +#: ../settings/system/network.rst:2 +msgid "Network" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:63 -msgid "For updates on the status of the server itself." +#: ../settings/system/network.rst:8 +msgid "" +"The proxy settings can only be saved after successfully testing the proxy " +"connection." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:77 -msgid "🤔 **What's with all the env vars?**" +#: ../settings/system/network.rst:15 +msgid "Proxy Address." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:79 +#: ../settings/system/network.rst:12 msgid "" -"Whenever Checkmk runs these scripts, it needs to provide some information " -"about the event that triggered the notification. This information is passed " -"in the form of these ``$NOTIFY_*`` environment variables." +"Allows you to provide a proxy server if needed. This is relevant for network " +"communication by Zammad." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:85 -msgid "" -"You can specify additional parameters to pass to the script when you're " -"setting up your notification rule, but the ones you see here are all " -"provided by default." +#: ../settings/system/network.rst:15 +msgid "It **does not** affect the update process or Elasticsearch." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:90 -msgid "Email Alerts" +#: ../settings/system/network.rst:18 +msgid "Username for proxy connection." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:94 +#: ../settings/system/network.rst:18 msgid "" -"🐞 **There are known bugs** in Zammad's processing of email from Checkmk. " -"This section will be completed once they have been resolved. (Learn more at " -"GitHub issues `#2377 `_ & " -"`#2180 `_.)" +"If your proxy server requires authentication, provide the username here." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:100 -msgid "In the meantime, we encourage you to set up API alerts instead." +#: ../settings/system/network.rst:21 +msgid "Password for proxy connection." msgstr "" -#: ../system/integrations/clearbit.rst:2 -msgid "Clearbit" +#: ../settings/system/network.rst:21 +msgid "" +"If your proxy server requires authentication, provide the password here." msgstr "" -#: ../system/integrations/clearbit.rst:4 +#: ../settings/system/network.rst:26 +msgid "No proxy for the following hosts." +msgstr "" + +#: ../settings/system/network.rst:24 msgid "" -"With our Clearbit integration, you can easily enrich the information " -"provided by Zammad. If the customers or agents email address is known to " -"Clearbit, it will share all information it has regarding the user with " -"Zammad. Those information can include the following:" +"Exception list for hosts you can't or don't want to reach via proxy server." msgstr "" -#: ../system/integrations/clearbit.rst:9 -msgid "Avatar" +#: ../settings/system/network.rst:27 +msgid "Default: ``localhost,127.0.0.0,::1``" msgstr "" -#: ../system/integrations/clearbit.rst:10 -msgid "Address information" +#: ../settings/system/services.rst:2 +msgid "Services" msgstr "" -#: ../system/integrations/clearbit.rst:11 -msgid "Website information" +#: ../settings/system/services.rst:10 +msgid "Image Service" msgstr "" -#: ../system/integrations/clearbit.rst:12 -msgid "A BIO (as Note by default)" +#: ../settings/system/services.rst:5 +msgid "Defines the backend for user and organization image lookups." msgstr "" -#: ../system/integrations/clearbit.rst:14 -msgid "" -"If needed, you can add further custom objects and add mappings to them, so " -"the Clearbit information can be filled within the database. In general you " -"can get any information from Clearbit, as long as you have a mapping to an " -"Zammad object." +#: ../settings/system/services.rst:7 +msgid "Default: ``Zammad Image Service`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:21 +#: ../settings/system/services.rst:9 msgid "" -"Clearbit does have a mapping of fields like LDAP and Exchange have, but does " -"not \"win\" against Zammad information. This means that if you have e.g. the " -"last name field filled in already and Clearbit has other information on " -"that, it will not be updated." +"Make sure your on premise installation has ``HTTPS`` access to ``images." +"zammad.com``." msgstr "" -#: ../system/integrations/clearbit.rst:26 -msgid "" -"However: If let's say the last name has been set by Clearbit and Zammad " -"notices that the last name on the Clearbit source has changed, Zammad will " -"also update this value." +#: ../settings/system/services.rst:18 +msgid "Geo Calendar Service" msgstr "" -#: ../system/integrations/clearbit.rst:33 +#: ../settings/system/services.rst:13 msgid "" -"The configuration of Clearbit is really easy and done fast! Just login to " -"your Clearbit-Account, go to \"API\" and copy the secret-API-Key." +"Defines the backend for geo calendar lookups. Used for initial calendar " +"setup." msgstr "" -#: ../system/integrations/clearbit.rst:38 -msgid "" -"Now change to your Zammad instance, go to Integrations (System) -> Clearbit " -"in the admin panel. Paste your API-Key into the API-Key-Field and decide if " -"Zammad should create unknown Organizations automatically, if the user does " -"not have one yet (and Clearbit knows it). The shared option decides if the " -"new organizations Zammad creates with Clearbit should be shared ones." +#: ../settings/system/services.rst:16 +msgid "Default: ``Zammad GeoCalendar Service`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:47 +#: ../settings/system/services.include.rst:2 msgid "" -"If you're unsure what option to choose, better stick with \"no\". You can " -"also learn more about :doc:`/manage/organizations/index`." +"Make sure your on premise installation has ``HTTPS`` access to ``geo.zammad." +"com``." msgstr "" -#: ../system/integrations/clearbit.rst:52 -msgid "" -"The Mapping option works similar to the mapping within the Exchange and LDAP " -"sync. You can add further mappings for e.g. custom fields if you need more " -"information that Clearbit can provide." +#: ../settings/system/services.rst:26 +msgid "Geo IP Service" msgstr "" -#: ../system/integrations/clearbit.rst:58 +#: ../settings/system/services.rst:21 msgid "" -"If you want to add more Clearbit fields and want to learn more about " -"available fields on their API, you can take a look at their `API " -"documentation `_." +"Defines the backend for geo IP lookups. Shows also location of an IP address " +"if an IP address is shown." msgstr "" -#: ../system/integrations/clearbit.rst:62 -msgid "" -"If you're happy with the above chosen Settings and your mapping, just save " -"the changes and enable Clearbit integration. Zammad will now start polling " -"the Clearbit API as users contact you." +#: ../settings/system/services.rst:24 +msgid "Default: ``Zammad GeoIP Service`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:68 -msgid "" -"Zammad does not synchronize with Clearbit on a regular basis, but on demand " -"if needed. This saves API calls." +#: ../settings/system/services.rst:32 +msgid "Geo Location Service" msgstr "" -#: ../system/integrations/clearbit.rst:73 +#: ../settings/system/services.rst:29 msgid "" -"Below the Settings and Mappings, you'll find our Integration log. You can " -"see what requests Zammad sent to Clearbit and also the APIs Response." +"Defines the backend for geo location lookups to store geo locations for " +"addresses." msgstr "" -#: ../system/integrations/clearbit.rst:78 +#: ../settings/system/services.rst:32 msgid "" -"By the way, you can also view the API log on the Clearbit website - the " -"information seen is basically the same." -msgstr "" - -#: ../system/integrations/clearbit.rst:84 -msgid "Example When Adding a User" +"Default: ``OpenStreetMap (ODbL 1.0, http://osm.org/copyright)`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:86 +#: ../settings/system/services.rst:36 msgid "" -"To show you how fast information is added, we added a small Screencast " -"below. This shows the creation of the User Alex from Clearbit. As we already " -"set the last name of Alex to \"X\", Zammad did not update it. What Zammad " -"did was to add further information it received from Clearbit." +"You can find a detailed privacy information on what we store for how long on " +"our :docs:`Privacy Appendix ` inside of our System " +"Documentation." msgstr "" -#: ../system/integrations/cti/generic.rst:2 -msgid "CTI (generic)" +#: ../settings/system/storage.rst:2 +msgid "Storage" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:1 +#: ../settings/system/storage.rst:6 msgid "" -"This integration enables Zammad to provide a caller log to your agents. With " -"this your agents can greet your customers by their name and are supported by " -"Zammad with automatically opening a new ticket dialog or the user profile." +"Here you can define where Zammad stores attachments for tickets and the " +"knowledge base. By default, we're writing to the ``Database`` - you can " +"switch to ``Filesystem`` or ``Simple Storage (S3)`` at any time. In this " +"case please have a look on the following instructions." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:6 +#: ../settings/system/storage.rst:11 msgid "" -"Click the toggle next to the heading to activate or deactivate this " -"integration." +"If you have a busy Zammad instance, we strongly encourage you to use " +"filesystem storage instead of \"Database\". This will greatly improve system " +"performance (de-crease database load and size)." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:9 -msgid "" -"If you want to learn more on how your agents can use this function, please " -"refer the :user-docs:`user documentation `." +#: ../settings/system/storage.rst:19 +msgid "Database" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:14 +#: ../settings/system/storage.rst:17 msgid "" -"Automatically opening new ticket dialogues or user profiles requires agent " -"to extension mapping - see more below." -msgstr "" - -#: ../system/integrations/cti/includes/introduction.include.rst:20 -msgid "Please note the following limitations to reduce confusion later on:" +"This is the default storage method. The attachments are stored directly in " +"the database. If your Zammad instance grows, we recommend one of the other " +"methods to maintain performance." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:22 -msgid "CTI integrations provide caller log functions only." +#: ../settings/system/storage.rst:38 +msgid "Filesystem" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:23 +#: ../settings/system/storage.rst:22 msgid "" -"This integration does not provide any VoIP functionalities; you can't make " -"phone calls from within Zammad." +"This storage method is recommended for all Zammad instances, especially for " +"those with a higher load. If you choose filesystem, your files are written " +"to ``/opt/zammad/storage/``." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:25 +#: ../settings/system/storage.rst:26 msgid "" -"If your browser supports ``tel``-URLs, you can click on phone numbers for " -"automatic dialing. This requires additional software / configuration on your " -"agent's computers." +"Moving attachments from \"Database\" to \"Filesystem\" can be run during " +"production use. However, you should consider your framework conditions (e.g. " +"bandwidth, system load in production) to define the right moment." msgstr "" -#: ../system/integrations/cti/generic.rst:9 -#: ../system/integrations/cti/placetel.rst:14 -#: ../system/integrations/cti/sipgate.rst:14 -msgid "Please provide the following requirements:" +#: ../settings/system/storage.rst:32 +msgid "**You noticed slow updates of Zammad?**" msgstr "" -#: ../system/integrations/cti/generic.rst:11 +#: ../settings/system/storage.rst:34 msgid "" -"A telephone system that supports webhooks (outbound) (best option are those " -"that allow customizing the calls)." +"While Zammad is beeing updated, it enforces a recursive \"change " +"owner\" (chown) for this directory. For instances with many files this can " +"be time consuming. To mitigate that you can move your files and create a " +"symlink in ``/opt/zammad/storage/`` to the new directory. Of course you have " +"to make sure on your own that the permissions are always correct." msgstr "" -#: ../system/integrations/cti/generic.rst:13 -msgid "A unique Call-ID during the call session." +#: ../settings/system/storage.rst:95 +msgid "Simple Storage (S3)" msgstr "" -#: ../system/integrations/cti/generic.rst:14 -msgid "Call event data (both numbers and direction)." +#: ../settings/system/storage.rst:41 +msgid "" +"To use the Simple Storage (S3), you have to provide some settings, which " +"can't be accessed in the UI (see instructions below)." msgstr "" -#: ../system/integrations/cti/generic.rst:15 -msgid "Your Zammad instance must be reachable for your telephony system." +#: ../settings/system/storage.rst:44 +msgid "" +"⚠️ Please note that the current implementation is in its early stages and can " +"be modified in the future." msgstr "" -#: ../system/integrations/cti/generic.rst:17 +#: ../settings/system/storage.rst:47 msgid "" -"If you want to learn more on what kind of requests are supported by Zammad " -"and what it expects, please consult our :docs:`CTI-API documentation `." +"The prerequisite is to have access to a S3-compatible storage and to have " +"all necessary parameters available (which depends on your storage provider; " +"if in doubt, please ask there for help)." msgstr "" -#: ../system/integrations/cti/generic.rst:22 -#: ../system/integrations/cti/placetel.rst:27 -#: ../system/integrations/cti/sipgate.rst:30 -msgid "Available Settings" +#: ../settings/system/storage.rst:51 +msgid "Steps to configure S3:" msgstr "" -#: ../system/integrations/cti/generic.rst:29 -#: ../system/integrations/cti/placetel.rst:41 -#: ../system/integrations/cti/sipgate.rst:40 -msgid "Endpoint Settings" +#: ../settings/system/storage.rst:53 +msgid "" +"Copy ``config/zammad/storage.yml.dist`` to ``config/zammad/storage.yml``" msgstr "" -#: ../system/integrations/cti/generic.rst:25 -msgid "" -"Zammad will list your generic CTI endpoint here. It contains a unique token " -"so ensure to keep this URL save." +#: ../settings/system/storage.rst:54 +msgid "Edit the copied file in one of the following ways:" msgstr "" -#: ../system/integrations/cti/generic.rst:28 +#: ../settings/system/storage.rst:56 msgid "" -"You'll need this endpoint for your PBX to talk to Zammad, see :docs:`CTI-API " -"documentation `." +"Either provide your S3 configuration with one attribute per line like in the " +"upper area of the file" msgstr "" -#: ../system/integrations/cti/includes/important-dont-forget-saving.include.rst:3 +#: ../settings/system/storage.rst:58 msgid "" -"All following options **do not save automatically**. Always use the Save " -"button on the lower end of the integration page!" +"Or provide your S3 configuration as an URL (which you can find at the end of " +"the file). Note: you can also provide this URL as environment variable (:" +"docs:`see system documentation `) without using this yml-file." msgstr "" -#: ../system/integrations/cti/generic.rst:43 -#: ../system/integrations/cti/placetel.rst:49 -#: ../system/integrations/cti/sipgate.rst:52 -msgid "Call Settings" +#: ../settings/system/storage.rst:62 +msgid "" +"We recommend the deletion of the not used configuration style to avoid " +"inconsistencies." msgstr "" -#: ../system/integrations/cti/generic.rst:39 -#: ../system/integrations/cti/placetel.rst:49 -#: ../system/integrations/cti/sipgate.rst:37 -#: ../system/integrations/cti/sipgate.rst:50 -msgid "Inbound" +#: ../settings/system/storage.rst:65 +msgid "Restart Zammad so the config file / environment variable is loaded" msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:1 +#: ../settings/system/storage.rst:66 msgid "" -"This option allows you to block specific incoming caller IDs. It allows you " -"to temporarily reject e.g. spam callers without having to contact providers " -"or PBX administrators." +"Set the \"Storage Method\" in Zammad to ``Simple Storage (S3)`` in Settings " +"> System > Storage and click on \"Submit\". After that, Zammad checks your " +"configuration and the connection to the service and will raise an error " +"message if something is wrong." msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:11 -msgid "Caller ID to block" +#: ../settings/system/storage.rst:72 +msgid "A very simple storage configuration could look like this:" msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 -msgid "Provide caller IDs to block in ``E.164`` format." +#: ../settings/system/storage.rst:85 +msgid "" +"Before setting the storage method to ``Simple Storage (S3)`` (step 4), " +"please make sure to have a working setup." msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:8 +#: ../settings/system/storage.rst:88 msgid "" -"Your telephony system has to support this function. Zammad will send a " -"``reject`` response which will cause your telephony system to hang up the " -"call. To callers this usually will feel like the line is busy." +"You can verify this by running ``rails r 'Rails.logger = Logger.new(STDOUT); " +"pp Store::Provider::S3.ping?'`` in your Zammad directory. If everything is " +"fine, you should see ``true``, else you should see ``false`` and a simple " +"error message." msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:14 +#: ../settings/system/storage.rst:93 msgid "" -"Provide a meaningful note for your fellow administrators to remind yourself " -"why you've chosen to block the number." +"If you installed Zammad through a package manager (rather than from source), " +"replace ``rails r`` with ``zammad run rails r`` above. To learn more, see :" +"docs:`Administration via Console `." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 -#: ../system/integrations/cti/includes/outbound-calls.include.rst:17 -#: ../system/integrations/cti/sipgate.rst:40 -msgid "Outbound" +#: ../settings/ticket.rst:4 +msgid "" +"Here you can adjust general ticket settings. Additional ones for the ticket " +"composer interface can be found in the :doc:`/misc/composer`." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:1 -msgid "" -"In many cases you may want to use a different caller ID depending on the " -"destination you're calling. This may apply due to specific connection rates " -"to other countries or because you want your customer to feel you're calling " -"from the same country." +#: ../settings/ticket.rst:11 +msgid "Ticket Hook (default: ``Ticket#``)" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:6 -msgid "This option expects ``E.164`` number formats." +#: ../settings/ticket.rst:11 +msgid "The identifier for a ticket; *e.g.,* Ticket#, Call#, MyTicket#." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 -msgid "Destination caller ID" +#: ../settings/ticket.rst:38 +msgid "Ticket Hook Position (default: ``right``)" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:5 -msgid "The caller ID or number you're trying to call." +#: ../settings/ticket.rst:14 +msgid "" +"With this setting you can decide (if) where to insert the ticket number." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:7 -msgid "You can use wildcards for e.g. country specific outbound numbers like:" +#: ../settings/ticket.rst:20 +msgid "*Right*" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:9 -msgid "``49*`` for Germany" +#: ../settings/ticket.rst:17 +msgid "" +"This setting will add the ticket reference on the right site of the subject." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:10 -msgid "``4930*`` for Berlin / Germany landlines" +#: ../settings/ticket.rst:20 +msgid "Example: ``Some Subject [Ticket#12345]``" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 -msgid "``33*`` for France" +#: ../settings/ticket.rst:26 +msgid "*Left*" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:15 -msgid "Set Outbound caller ID" +#: ../settings/ticket.rst:23 +msgid "" +"This setting will add the ticket reference on the left site of the subject." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:14 -msgid "" -"The outbound caller ID to set (the number your customer sees on his display) " -"in ``E.164`` number format." +#: ../settings/ticket.rst:26 +msgid "Example: ``[Ticket#12345] Some Subject``" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 -msgid "Provide a short description for fellow administrators." +#: ../settings/ticket.rst:29 +msgid "*None*" msgstr "" -#: ../system/integrations/cti/includes/generic-cti-support-note.includes.rst:3 -msgid "" -"This option requires your PBX to send a specific request to Zammad *before " -"dialing*. Please consult the :docs:`CTI API ` in case " -"you're not sure." +#: ../settings/ticket.rst:29 +msgid "This will completely remove ticket references from the subject." msgstr "" -#: ../system/integrations/cti/generic.rst:52 -#: ../system/integrations/cti/placetel.rst:54 -#: ../system/integrations/cti/sipgate.rst:59 -msgid "Other Settings" +#: ../settings/ticket.rst:33 +msgid "" +"Please ensure to take a look at :doc:`/channels/email/settings` within the " +"email channel to ensure you have at least one reference that helps Zammad to " +"assign follow-ups correctly." msgstr "" -#: ../system/integrations/cti/includes/other-settings-intro.include.rst:1 +#: ../settings/ticket.rst:37 msgid "" -"Below you can find all available additional settings for this CTI " -"integration. For your overview we're sorting them by appearance and " -"reference their description first." +"Disabling this and not setting up any further follow up search will lead to " +"unexpected results!" msgstr "" -#: ../system/integrations/cti/includes/default-caller-id.include.rst:2 -#: ../system/integrations/cti/includes/default-caller-id.include.rst:1 -msgid "Default caller ID for outbound calls" +#: ../settings/ticket.rst:65 +msgid "" +"Ticket Last Contact Behaviour (default: ``Use the start time of the last " +"customer thread (which may consist of multiple articles).``)" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:16 -#: ../system/integrations/cti/includes/records-caller-log.include.rst:15 -msgid "Shown records in caller log" +#: ../settings/ticket.rst:41 +msgid "" +"This setting changes the way Zammad updates the ``Last Contact`` value of a " +"ticket. This is fairly important for overviews and what you expect upon " +"ticket updates of a customer." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:2 +#: ../settings/ticket.rst:52 msgid "" -"Allows you to set the number of shown caller log entries for all users. You " -"can choose from the following values:" +"Use the start time of the last customer thread (which may consist of " +"multiple articles)." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:5 -msgid "60 (default)" +#: ../settings/ticket.rst:46 +msgid "" +"If this option is chosen, Zammad will update the last updated value just " +"once if a customer replies. After that, Zammad will wait for an agent to " +"react." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:6 -msgid "120" +#: ../settings/ticket.rst:50 +msgid "" +"This comes in handy if you want to work tickets in the order of their first " +"update. This will not change ticket orders if customers decide to \"bump\" " +"the ticket affected." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:7 -msgid "180" +#: ../settings/ticket.rst:57 +msgid "Use the time of the very last customer article." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:8 -msgid "240" +#: ../settings/ticket.rst:55 +msgid "" +"When setting this option, Zammad will always update the last updated value. " +"This means that if ordering by ``Last Update``, ticket orders will change if " +"customers \"bump\" the ticket." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:9 -msgid "300" +#: ../settings/ticket.rst:64 +msgid "Last contact value used on :doc:`/manage/overviews`" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:11 -msgid "**🥵 Potential performance issue**" +#: ../settings/ticket.rst:65 +msgid "Last contact value used on :doc:`/manage/trigger`" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:13 +#: ../settings/ticket.rst:88 msgid "" -"Setting this setting higher than 60 may cause serious performance issues on " -"very busy instances. Keep in mind that this setting causes Zammad to poll " -"and send up to 300 records to *all active agent sessions* in very short time " -"periods." +"Ticket Organization Reassignment (default: ``Update the most recent tickets." +"``)" msgstr "" -#: ../system/integrations/cti/generic.rst:73 -msgid "Caller Log Filter" +#: ../settings/ticket.rst:68 +msgid "" +"This setting changes the way Zammad updates the organization field of the " +"tickets whenever the primary organization of a user is changed." msgstr "" -#: ../system/integrations/cti/generic.rst:55 -msgid "" -"This function allows you to provide call information based on e.g. queues " -"only to agents that really need the information." +#: ../settings/ticket.rst:74 +msgid "Update the most recent tickets." msgstr "" -#: ../system/integrations/cti/generic.rst:58 +#: ../settings/ticket.rst:72 msgid "" -"Why? If you have a team for several countries or departments, you don't want " -"to bug your agents from other departments. Leaving these options empty will " -"fallback to showing everything to everyone." +"If this option is chosen, Zammad will update the 100 most recent tickets " +"where the user is the ticket customer. The ticket organization field will be " +"automatically set to the new primary organization of the user." msgstr "" -#: ../system/integrations/cti/generic.rst:64 -msgid "Destination caller ID or Queue" +#: ../settings/ticket.rst:88 +msgid "Do not update any tickets." msgstr "" -#: ../system/integrations/cti/generic.rst:63 +#: ../settings/ticket.rst:77 msgid "" -"This depends on your PBX and usually is either a queue ID, phone number or " -"extension." +"When choosing this option, Zammad will not update any tickets when the " +"user's primary organization is changed." msgstr "" -#: ../system/integrations/cti/generic.rst:69 -msgid "Agents" +#: ../settings/ticket.rst:80 +msgid "**Use with care!**" msgstr "" -#: ../system/integrations/cti/generic.rst:67 +#: ../settings/ticket.rst:82 msgid "" -"Select the agents that are responsible for the group. These agents will then " -"see caller log entries and call notifications fitting to said queue." +"Using this option may lead to inconsistencies in the system as the ticket " +"organization may become decoupled from the ticket customer." msgstr "" -#: ../system/integrations/cti/generic.rst:0 +#: ../settings/ticket.rst:85 msgid "" -"Screenshot showing the caller log filter table with pre filled sample data" +"However, you may use this option if you wish to maintain :ref:`the shared " +"access ` to the ticket for all organization " +"members of the original organization of the customer." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:6 -msgid "" -"With recent logs Zammad allows you to view the latest calls for the CTI " -"functionality. This usually comes in handy, when you're looking for errors." +#: ../settings/ticket.rst:110 +msgid "Ticket Number Format (default: ``Increment (SystemID.Counter)``)" msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:0 +#: ../settings/ticket.rst:94 msgid "" -"Screenshot showing several incoming requests within Recent logs section." +"This setting defines the way Zammad's ticket number will look. Changing this " +"setting in production will cause follow up detection to fail." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:16 -msgid "I'm just here to clear floats up." +#: ../settings/ticket.rst:102 +msgid "Increment (SystemID.Counter)" msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:20 +#: ../settings/ticket.rst:98 msgid "" -"By clicking on the entry of interest, Zammad will provide more details on " -"the call in question. You'll see the payload it received and also the " -"response that was sent." +"The increment value contains the SystemID (automatically generated during " +"installation) and a increment which counts up with every new Ticket. The " +"increment will automatically get another digit if needed." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:0 -msgid "" -"Screenshot showing detailed information of a specific log entry of recent " -"logs" +#: ../settings/ticket.rst:102 +msgid "Examples: ``1010138``, ``1010139``" msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:31 -msgid "x" +#: ../settings/ticket.rst:110 +msgid "Date (Year.Month.Day.SystemID.Counter)" msgstr "" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 -#: ../system/integrations/cti/includes/troubleshooting.include.rst:9 -msgid "My Phone page stays blank, signalling does work..." +#: ../settings/ticket.rst:105 +msgid "" +"This version of the ticket number is fairly long. However, because it " +"contains the date of ticket creation, it also allows you to see when the " +"ticket has been created. You may feel familiar with this number format if " +"you've worked with OTRS already." msgstr "" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:5 -msgid "" -"If you've made sure that signalling works (check Recent logs) and your " -"Caller Log still stays empty, please ensure that you only configured one CTI " -"integration version. Specifically defining more than one agent mapping on " -"the different integration variants will be the issue." +#: ../settings/ticket.rst:110 +msgid "Examples: ``201206231010138``, ``201206231010139``" msgstr "" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 -msgid "Clear the not needed agent mapping and reload your browser page." +#: ../settings/ticket.rst:137 +msgid "OPTIONS" msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:1 +#: ../settings/ticket.rst:113 msgid "" -"By mapping your agents extension to their existing Zammad users, Zammad can " -"provide a new ticket dialog or open the user profile for the agent that " -"picks up the call." +"The below options allow you to further customize your ticket number. The " +"availability of options differ depending of the chosen ticket number format " +"above." msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:5 -msgid "" -"This speeds up ticket aiding, no matter if it's for existing tickets or new " -"ones!" +#: ../settings/ticket.rst:122 +msgid "Checksum (default: ``no``)" msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:8 +#: ../settings/ticket.rst:118 msgid "" -"To see it work from the agent's perspective, have a look on :user-docs:`user " -"documentation `." +"If set to yes, we'll built a checksum to further \"unique\" the ticket " +"number of your system. If you're dealing with many other ticket systems this " +"might help to prevent false positive follow up detection on tickets." msgstr "" -#: ../system/integrations/cti/placetel.rst:2 -msgid "Placetel CTI" +#: ../settings/ticket.rst:122 +msgid "This will also add another digit to the ticket number." msgstr "" -#: ../system/integrations/cti/placetel.rst:16 -msgid "You need an administrative Placetel account for your organization." +#: ../settings/ticket.rst:137 +msgid "Min. size of Number (default: ``5``)" msgstr "" -#: ../system/integrations/cti/placetel.rst:17 -#: ../system/integrations/cti/sipgate.rst:20 +#: ../settings/ticket.rst:125 msgid "" -"Your Zammad instance must be allowed to communicate to external services." +"This setting defines the minimum length of your ticket number. If your " +"counter is not yet high enough, Zammad will fill the number with zeros to " +"ensure the wanted length." msgstr "" -#: ../system/integrations/cti/placetel.rst:18 -msgid "Placetel must be able to reach your Zammad instance." -msgstr "" - -#: ../system/integrations/cti/placetel.rst:22 -msgid ":doc:`provider-configurations/placetel`" -msgstr "" - -#: ../system/integrations/cti/placetel.rst:21 +#: ../settings/ticket.rst:129 msgid "" -"Learn how to configure Placetel to enable Zammad and Placetel to communicate " -"with each other." +"Please note that the minimum length is ``3`` (SystemID + at least one digit " +"if below 10). Also, if the length is no longer long enough, the number will " +"automatically get one digit longer. Ticket-Numbers **do not overflow**, thus " +"it's save to keep it at 5 or set it lower if wanted." msgstr "" -#: ../system/integrations/cti/placetel.rst:32 +#: ../settings/ticket.rst:135 msgid "" -"The here listed endpoint settings are relevant for the :doc:`integration " -"configuration with Placetel `." +"This option is only available if ticket number format is set to " +"``Increment``!" msgstr "" -#: ../system/integrations/cti/placetel.rst:37 -#: ../system/integrations/i-doit.rst:53 -msgid "Endpoint" +#: ../settings/ticket.rst:142 +msgid "Auto-Assignment" msgstr "" -#: ../system/integrations/cti/placetel.rst:36 +#: ../settings/ticket.rst:144 msgid "" -"This endpoint will be required for the Zammad integration within the " -"Placetel web interface." -msgstr "" - -#: ../system/integrations/cti/placetel.rst:41 -msgid "API Token" +"In a larger Zammad environment, it happens that several agents open the same " +"ticket at the same time. Although collision detection is then effective, the " +"efficiency of processing can be increased by means of the automatic " +"assignment of tickets when a ticket is opened." msgstr "" -#: ../system/integrations/cti/placetel.rst:40 +#: ../settings/ticket.rst:149 msgid "" -"You'll receive this token within the ``Web API`` menu. Make sure to copy " -"this value, it's only shown once!" -msgstr "" - -#: ../system/integrations/cti/placetel.rst:71 -#: ../system/integrations/cti/sipgate.rst:77 -msgid "Phone Extension to Agent Mapping" +"The automatic assignment of tickets can be activated and configured in the " +"admin area under Settings > Ticket > Auto Assignment." msgstr "" -#: ../system/integrations/cti/placetel.rst:0 -msgid "Screenshot showing sample user mappings in between Placetel and Zammad" +#: ../settings/ticket.rst:152 +msgid "" +"The auto assignment only works if the ticket has no owner yet. By default, " +"the agent can always reset the ticket owner to ``-`` if needed." msgstr "" -#: ../system/integrations/cti/placetel.rst:64 +#: ../settings/ticket.rst:155 msgid "" -"You can find your agents Placetel username combination required within ⚙️ PBX " -"→ VoIP destinations. Within the \"Advanced settings\" section you're looking " -"for \"SIP user name\" and \"SIP server\"." +"If you want to use this function for only specific tickets, you can " +"configure the conditions accordingly to meet your requirement. By default " +"the condition affects all tickets with the state ``open``." msgstr "" -#: ../system/integrations/cti/placetel.rst:68 -msgid "Combine these two like so: ``@``." +#: ../settings/ticket.rst:161 +msgid "" +"If you need to exclude users (e.g. a group leader), you can search and " +"select the desired agents in the ``Exception Users`` list. The search " +"function in this area is only effective, if you have too many agents to " +"display at once to help you with the configuration." msgstr "" -#: ../system/integrations/cti/placetel.rst:0 -msgid "Sample VoIP credentials for a Placetel user" +#: ../settings/ticket.rst:167 +msgid "Notifications" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:2 -msgid "Setup Placetel connection for Zammad" +#: ../settings/ticket.rst:191 +msgid "Default Notifications" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:6 +#: ../settings/ticket.rst:170 msgid "" -"This configuration step requires a *full* administrative Placetel account. " -"You may receive forbidden error messages with Placetel in case your " -"permissions are not high enough." +"This setting allows you to configure the default ticket notifications that " +"will be applied to all new agent users (incl. users who were just assigned " +"agent role). Simply change the notification matrix to desired state and " +"press **Save**." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:10 +#: ../settings/ticket.rst:175 msgid "" -"The following actions can be configured via the `Placetel web interface " -"`_." -msgstr "" - -#: ../system/integrations/cti/provider-configurations/placetel.rst:29 -msgid "Step 1: Activate Zammad integration" +"In case an agent already exists, their ticket notification preferences will " +"be preserved. Optionally, you can also **Apply current defaults to all " +"agents**." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:14 +#: ../settings/ticket.rst:181 msgid "" -"Within Integrations, scroll down to Partner integrations and select Zammad." +"**Potential time-consuming action:** Applying default ticket notifications " +"to all agent users may take some time to complete, be patient! The exact " +"time will depend on the size of your system and the number of agents." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:17 +#: ../settings/ticket.rst:185 msgid "" -"You can alternatively filter by \"Ticket Systems\" to reduce the number of " -"entries on the page. You'll still want to look for Partner integrations. 🤓" +"**Active agents only!** When current default ticket notifications are " +"applied, only active agent users are considered. In case an agent is re-" +"activated *after* this action, they will still have the old notification " +"configuration." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:21 +#: ../settings/ticket.rst:190 msgid "" -"Within the Zammad integration now press \"Activate\". A new tab ``API`` " -"becomes available - open this tab." +"In case you want to go back to the initial state of ticket notifications, " +"you can click on **Reset to default** button." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:24 -msgid "" -"Now tick \"Enable Call Control / Notify API\" and paste the Placetel " -"endpoint from your Zammad instance into the field \"URL of your API " -"endpoint\". Save to apply the settings" +#: ../settings/ticket.rst:196 +msgid "Duplicate Detection" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 -msgid "Screencast showing how to activate the Zammad integration" +#: ../settings/ticket.rst:238 +msgid "Detect Duplicate Ticket Creation" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:51 -msgid "Step 2: Generate API Token for Placetel" +#: ../settings/ticket.rst:199 +msgid "" +"This setting turns on the duplicate ticket detection mechanism during ticket " +"creation. If similar tickets are found in the system, a suitable warning " +"will be shown to the user trying to create a ticket." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:32 -msgid "" -"Go back to the integrations page and scroll down to \"Web API\". Generate a " -"new API token by using the \"Create a new API token\" button." +#: ../settings/ticket.rst:206 +msgid "A Sample Duplicate Ticket Warning" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:37 +#: ../settings/ticket.rst:208 msgid "" -"If you already generated a token either use your existing token or reset it " -"by using above mentioned button. Placetel will ask you to conform this reset." +"You can choose which ticket attributes will be matched by selecting them in " +"**Attributes to compare** field. Only if the ticket attribute value provided " +"by the user in the ticket create form is *equal* with the attribute in an " +"existing ticket, the warning will be shown." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:41 -msgid "" -"Please keep in mind that existing API scripts may no longer work due to " -"token resets!" +#: ../settings/ticket.rst:213 +msgid "**Warning title** and **Warning message** are configurable as well." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:44 +#: ../settings/ticket.rst:215 msgid "" -"Copy the provided API token and insert it into the \"API Token\" field " -"within Zammad's Placetel integration." +"You can limit the detection only to certain user roles. By default, only " +"agents will see the warning." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:47 +#: ../settings/ticket.rst:218 msgid "" -"Apply your changes by using the \"Save\" button on the bottom of the " -"Placetel integration page and activate the Placetel integration." +"If you don't want to show the matched tickets as part of the warning, you " +"can set **Show matching ticket(s) in the warning** setting to *no*." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +#: ../settings/ticket.rst:221 msgid "" -"Screencast showing how to retrieve an API token from Placetel for Zammad" +"By default, **Permission level for looking up ticket** is set to *User*, " +"which means user permissions will be honored during sarch. The user will " +"see the warning only if tickets they have access to are matched. " +"Alternatively, you can set this setting to *System*, in which case the " +"search will happen within *all* tickets in the system, regardless of user " +"permissions." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:73 -#: ../system/integrations/cti/provider-configurations/sipgate.rst:77 -msgid "Step 3: Restrict the numbers to notify on" +#: ../settings/ticket.rst:227 +msgid "**🦺 Safety first!**" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:54 +#: ../settings/ticket.rst:229 msgid "" -"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " -"the the Integrations page of the Placetel web interface, go to \"Notify " -"API\"." +"Even if the permission level is set to *System*, the user will not be shown " +"the tickets they don't have access to in the warning, even if they match." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:58 +#: ../settings/ticket.rst:233 msgid "" -"Lower on the page Placetel allows you to restrict the numbers to notify on. " -"You'll find this within the \"External routing API\" part." +"However, just the confirmation about the existence of the tickets in the " +"system may be considered an unwanted information disclosure. Use this option " +"carefully!" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +#: ../settings/ticket.rst:237 msgid "" -"Screenshot showing a sample selection of phone numbers to use for the " -"Placetels notify API" +"Finally, you can configure between matching within **All tickets** or **Open " +"tickets** only by setting **Match tickets in following states**. Depending " +"on the current ticket state, a ticket may or not be matched." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:66 -msgid "" -"This menu point also provides a API request log from Placetel view. Just " -"open \"Recent responses of your API endpoint\" to learn more." +#: ../system/core-workflows.rst:2 +msgid "Core Workflows" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:69 +#: ../system/core-workflows.rst:4 msgid "" -"If you want to see Zammad's perspective, use the \"Recent Logs\" part from " -"within the Placetel integration page." +"Core Workflows allow you to adjust object attributes in many ways. For " +"example:" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 -msgid "Screenshot showing sample log entries for Placetels API calls to Zammad" +#: ../system/core-workflows.rst:7 +msgid "show / hide fields" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:77 -msgid "Step 4 (optional): Further configurations for Placetel" +#: ../system/core-workflows.rst:8 +msgid "adjust mandatory setting" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:76 +#: ../system/core-workflows.rst:9 +msgid "manipulate available options" +msgstr "" + +#: ../system/core-workflows.rst:11 msgid "" -"If needed, you can now configure Zammad's Placetel integration in more " -"detail. You can learn more about your options here: :ref:`Placetel " -"integration settings `." +"With this, you can provide exactly the information your users really need!" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:2 -msgid "Setup Sipgate connection for Zammad" +#: ../system/core-workflows.rst:15 +msgid "" +"If the pre-defined :doc:`/system/objects` are not enough, please add them " +"beforehand." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +#: ../system/core-workflows.rst:17 msgid "" -"Sipgate has no english web interface which is why this documentation page is " -"mixing up languages badly." +"If you experience slow or unreliable field updates, please see :ref:`Core " +"Workflow Ajax Modus `" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +#: ../system/core-workflows.rst:22 msgid "" -"Please also note that the availability of API addons highly depends on your " -"package trier. Usage of sipgate.io packages *is not free*, please check " -"their `pricing page `_ before!" +"This is a very enhanced functionality and can cause unexpected UI behavior. " +"Please ensure to test your use cases after configuration to reduce surprises." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:35 -msgid "Step 1: Book sipgate.io package" +#: ../system/core-workflows.rst:None +msgid "Dialogue for adding a new workflow" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:13 -msgid "Skip to step 2 if you already have the package booked!" +#: ../system/core-workflows/condition-operators.rst:2 +msgid "Core Workflow Condition Operators" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:15 +#: ../system/core-workflows/condition-operators.rst:4 msgid "" -"Login to an administrative Sipgate account and navigate to " -"``Accountverwaltung``. You'll see several different options depending on " -"your booked packages. Select ``Verträge & Produkte`` to continue." +"You might know that there is a separate section for explaining :doc:" +"`condition operators `. Head over there to " +"see a detailed explanation of many conditions and operators." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:19 +#: ../system/core-workflows/condition-operators.rst:8 msgid "" -"Scroll down to the section ``Zusätzliche Produkte buchen`` and look for " -"``sipgate.io`` - select this product by using the ``Produkte anzeigen``-" -"Button." -msgstr "" - -#: ../system/integrations/cti/provider-configurations/sipgate.rst:23 -msgid "" -"On the next page select either one of the ``sipgate.io`` packages or ``Push-" -"API Package Free``. Follow the dialogue by booking the addon. You'll be " -"returned to your contract overview and now should see the selected addon in " -"your list." +"Due to differences to other places in Zammad which are also using conditions " +"(e.g. triggers), you can find a dedicated description of operators for core " +"workflows below." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:30 +#: ../system/core-workflows/condition-operators.rst:12 msgid "" -"The availability for ``sipgate.io`` packages and their levels highly depends " -"on the overall account type and product you've booked with Sipgate." +"Be aware that the availability of the operators depends on the selected " +"attribute and its field type. Some of the operators may only be available " +"for system attributes (e.g. for \"tags\", \"active\")." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screencast showing the process on how to book the required sipgate.io addon" +#: ../system/core-workflows/condition-operators.rst:20 +msgid "Operator" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:52 -msgid "Step 2: Configure webhook for Zammad" +#: ../system/core-workflows/condition-operators.rst:22 +msgid "after (absolute)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:38 -msgid "" -"Within your ``Accountverwaltung`` navicate to your product ``sipgate.io``. " -"In the newly opened tab, switch from \"Clients\" to \"Webhooks\" and paste " -"the endpoint URLs from your Zammad instance like so:" +#: ../system/core-workflows/condition-operators.rst:23 +msgid "Matches if a date/time is after a specific point in time." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:42 -msgid "Inbound endpoint to \"Incoming\"" +#: ../system/core-workflows/condition-operators.rst:24 +msgid "after (relative)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:43 -msgid "Outbound endpoint to \"Outgoing\"" +#: ../system/core-workflows/condition-operators.rst:25 +msgid "Matches if a time span after a specified event has passed." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:47 -msgid "" -"Ensure to select at least one call group or phoneline within \"Sources\". " -"Other wise Sipgate will not indicate any incoming or outgoing calls to " -"Zammad." +#: ../system/core-workflows/condition-operators.rst:26 +msgid "before (absolute)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screencast showing how to add Zammad's endpoint URLs to sipgate.ios webhook " -"configuration" +#: ../system/core-workflows/condition-operators.rst:27 +msgid "Matches if a date/time is before a specific point in time." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:55 -msgid "" -"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " -"the Webhooks → URLs section of Sipgate you can select which *sources* " -"Sipgate should notify Zammad about in- and outgoing calls." +#: ../system/core-workflows/condition-operators.rst:28 +msgid "before (relative)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:59 -msgid "" -"Use either specific phone lines or use the option \"Use for all phonelines " -"and groups\" to notify Zammad about all existing lines of your Sipgate " -"account." +#: ../system/core-workflows/condition-operators.rst:29 +msgid "Matches if a time span after a specified event has not passed." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screenshot showing a sample selection of phone numbers to use for the " -"Sipgates webhooks API" +#: ../system/core-workflows/condition-operators.rst:30 +msgid "contains" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:68 -msgid "This section also allows you to enable a Debug log." +#: ../system/core-workflows/condition-operators.rst:31 +msgid "Matches if a specified value is present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "Screenshot showing an enabled Debug log option" +#: ../system/core-workflows/condition-operators.rst:33 +msgid "Matches if all of the specified values are present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:73 -msgid "" -"After enabling you can use the Debug log section to see all sent webhook " -"calls to Zammad. You'll also can see the response." +#: ../system/core-workflows/condition-operators.rst:35 +msgid "Matches if none of the specified values are present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screenshot showing sample log entries for Sipgates webhook calls to Zammad" +#: ../system/core-workflows/condition-operators.rst:36 +msgid "contains not" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:81 -msgid "Step 4 (optional): Further configurations for Sipgate" +#: ../system/core-workflows/condition-operators.rst:37 +msgid "Matches if a specified value is not present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:80 -msgid "" -"If needed, you can now configure Zammad's Sipgate integration in more " -"detail. You can learn more about your options here: :ref:`Sipgate " -"integration settings `." +#: ../system/core-workflows/condition-operators.rst:39 +msgid "Matches if one specified value is present." msgstr "" -#: ../system/integrations/cti/sipgate.rst:2 -msgid "Sipgate (sipgate.io)" +#: ../system/core-workflows/condition-operators.rst:41 +msgid "Matches if one specified value is not present." msgstr "" -#: ../system/integrations/cti/sipgate.rst:16 -msgid "You need an administrative Sipgate account for your organization." +#: ../system/core-workflows/condition-operators.rst:42 +msgid "does not match regex" msgstr "" -#: ../system/integrations/cti/sipgate.rst:17 -msgid "" -"Zammad requires a ``sipgate.io`` addon from the feature store (please note " -"that API calls are not free with Sipgate. Rates may apply and differ from " -"account to account)." +#: ../system/core-workflows/condition-operators.rst:43 +msgid "Matches if content doesn't fit to regex rule." msgstr "" -#: ../system/integrations/cti/sipgate.rst:21 -msgid "Sipgate must be able to reach your Zammad instance." +#: ../system/core-workflows/condition-operators.rst:44 +msgid "ends with" msgstr "" -#: ../system/integrations/cti/sipgate.rst:25 -msgid ":doc:`provider-configurations/sipgate`" +#: ../system/core-workflows/condition-operators.rst:45 +msgid "Matches if content ends with specified value." msgstr "" -#: ../system/integrations/cti/sipgate.rst:24 -msgid "" -"Learn how to configure Sipgate to enable Zammad and Sipgate to communicate " -"with each other." +#: ../system/core-workflows/condition-operators.rst:46 +msgid "ends with one of" msgstr "" -#: ../system/integrations/cti/sipgate.rst:33 -msgid "" -"Below endpoint settings affect the :doc:`sipgate.io configuration `." +#: ../system/core-workflows/condition-operators.rst:47 +msgid "Matches if content ends with one of the specified values." msgstr "" -#: ../system/integrations/cti/sipgate.rst:37 -msgid "This endpoint is required for incoming call hooks." +#: ../system/core-workflows/condition-operators.rst:48 +msgid "from (relative)" msgstr "" -#: ../system/integrations/cti/sipgate.rst:40 -msgid "This endpoint is required for outgoing call hooks." +#: ../system/core-workflows/condition-operators.rst:49 +msgid "Matches if date/time is after a period of time after an event." msgstr "" -#: ../system/integrations/cti/sipgate.rst:0 -msgid "Screenshot showing sample user mappings in between Sipgate and Zammad" +#: ../system/core-workflows/condition-operators.rst:51 +msgid "Matches if content is equal to a specified value." msgstr "" -#: ../system/integrations/cti/sipgate.rst:69 -msgid "" -"You can find your agent's Sipgate username within ``Accountverwaltung → " -"Benutzer``. You're looking for the SIP-ID." +#: ../system/core-workflows/condition-operators.rst:52 +msgid "is any of" msgstr "" -#: ../system/integrations/cti/sipgate.rst:0 -msgid "Sample VoIP credentials for a Sipgate user" +#: ../system/core-workflows/condition-operators.rst:53 +msgid "Matches if content is equal to any of specified values." msgstr "" -#: ../system/integrations/cti/sipgate.rst:77 -msgid "Users with several devices also have several SIP-IDs." +#: ../system/core-workflows/condition-operators.rst:54 +msgid "is modified" msgstr "" -#: ../system/integrations/elasticsearch.rst:2 -msgid "Elasticsearch (SaaS)" +#: ../system/core-workflows/condition-operators.rst:55 +msgid "Matches if content is modified." msgstr "" -#: ../system/integrations/elasticsearch.rst:4 -msgid "" -"The Elasticsearch integration allows you to create a read-only user to use " -"with your favorite reporting tool (e.g. like Grafana)." +#: ../system/core-workflows/condition-operators.rst:57 +#: ../system/core-workflows/condition-operators.rst:61 +msgid "True from the moment of changing content until form submit." msgstr "" -#: ../system/integrations/elasticsearch.rst:7 -msgid "" -"If you want to take full advantage of the Zammad reporting, have a look at " -"our :docs:`Grafana ` " -"setup page as well." +#: ../system/core-workflows/condition-operators.rst:58 +msgid "is modified to" msgstr "" -#: ../system/integrations/elasticsearch.rst:11 -#: ../system/subscription/index.rst:7 -msgid "**🚧 Hosted environment specific 🚧**" +#: ../system/core-workflows/condition-operators.rst:59 +msgid "Matches if content is modified to a specific value." msgstr "" -#: ../system/integrations/elasticsearch.rst:13 -msgid "" -"This integration is only available for Hosted setups. In order to use " -"Elasticsearch you'll need the **Plus** subscription." +#: ../system/core-workflows/condition-operators.rst:62 +msgid "is none of" msgstr "" -#: ../system/integrations/elasticsearch.rst:16 -msgid "" -"Self hosted users have all the control over their self hosted Elasticsearch " -"instances." +#: ../system/core-workflows/condition-operators.rst:63 +msgid "Matches if content is none of any specified values." msgstr "" -#: ../system/integrations/elasticsearch.rst:None -msgid "Elasticsearch integration page on SaaS environments" +#: ../system/core-workflows/condition-operators.rst:65 +msgid "Matches if content is not equal to a specified value." msgstr "" -#: ../system/integrations/elasticsearch.rst:27 -msgid "" -"Please note the following limitations of Elasticsearch access on hosted " -"environments:" +#: ../system/core-workflows/condition-operators.rst:67 +msgid "Matches if content is present." msgstr "" -#: ../system/integrations/elasticsearch.rst:30 -msgid "access to the Elasticsearch index is read-only access" +#: ../system/core-workflows/condition-operators.rst:68 +msgid "just changed" msgstr "" -#: ../system/integrations/elasticsearch.rst:31 -msgid "currently you're limited to user only" +#: ../system/core-workflows/condition-operators.rst:69 +msgid "Matches if content has changed." msgstr "" -#: ../system/integrations/elasticsearch.rst:32 +#: ../system/core-workflows/condition-operators.rst:71 +#: ../system/core-workflows/condition-operators.rst:75 msgid "" -"Reporting tools that require to write into the indexes (like Kibana) are not " -"supported" +"Only true for the moment of changing content until next form field action/" +"click." msgstr "" -#: ../system/integrations/elasticsearch.rst:34 -msgid "IP access restriction is currently not yet supported" +#: ../system/core-workflows/condition-operators.rst:72 +msgid "just changed to" msgstr "" -#: ../system/integrations/elasticsearch.rst:37 -msgid "Activating Elasticsearch Access" +#: ../system/core-workflows/condition-operators.rst:73 +msgid "Matches if content has changed to a specified value." msgstr "" -#: ../system/integrations/elasticsearch.rst:39 -msgid "" -"By default external access to your Elasticsearch index is not active. You " -"can enable the integration at any time if needed." +#: ../system/core-workflows/condition-operators.rst:76 +msgid "matches regex" msgstr "" -#: ../system/integrations/elasticsearch.rst:42 -msgid "" -"Please ensure to note down the password provided - you won't have access to " -"it afterwards." +#: ../system/core-workflows/condition-operators.rst:77 +msgid "Matches if value fits to regex rule." msgstr "" -#: ../system/integrations/elasticsearch.rst:None -msgid "Screencast showing activation of Elasticsearch integration" +#: ../system/core-workflows/condition-operators.rst:79 +msgid "Matches if no content is present." msgstr "" -#: ../system/integrations/elasticsearch.rst:51 -msgid "Connection Settings" +#: ../system/core-workflows/condition-operators.rst:80 +msgid "starts with" msgstr "" -#: ../system/integrations/elasticsearch.rst:53 -msgid "" -"This section holds the most important general information for accessing your " -"Elasticsearch indexes - such as:" -msgstr "" - -#: ../system/integrations/elasticsearch.rst:57 -msgid "A unique subdomain that does not tell your real instance URL." +#: ../system/core-workflows/condition-operators.rst:81 +msgid "Matches if content starts with specified value." msgstr "" -#: ../system/integrations/elasticsearch.rst:61 -msgid "Software" +#: ../system/core-workflows/condition-operators.rst:82 +msgid "starts with one of" msgstr "" -#: ../system/integrations/elasticsearch.rst:60 -msgid "" -"The major version of the search index being used. This is required by some " -"Reporting tools like Grafana." +#: ../system/core-workflows/condition-operators.rst:83 +msgid "Matches if content starts with one of the specified values." msgstr "" -#: ../system/integrations/elasticsearch.rst:64 -msgid "Authentication" +#: ../system/core-workflows/condition-operators.rst:84 +msgid "till (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:64 -msgid "The authentication type being supported. ``Basic Authentication``" +#: ../system/core-workflows/condition-operators.rst:85 +msgid "Matches if date/time is before a period of time before an event." msgstr "" -#: ../system/integrations/elasticsearch.rst:67 -msgid "Available Indexes" +#: ../system/core-workflows/condition-operators.rst:86 +msgid "today" msgstr "" -#: ../system/integrations/elasticsearch.rst:69 -msgid "" -"Within this section we're displaying the -in our opinion- most important " -"indexes for a Zammad instance." +#: ../system/core-workflows/condition-operators.rst:87 +msgid "Matches if date/time is today." msgstr "" -#: ../system/integrations/elasticsearch.rst:72 -msgid "" -"If you require all indexes or our listing is not good enough for you, point " -"your browser to the URL we're providing and append ``/_aliases?" -"pretty=true``. The result should look like this: ``https://.zammad.com/" -"_aliases?pretty=true``." +#: ../system/core-workflows/condition-operators.rst:88 +msgid "within last (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:77 +#: ../system/core-workflows/condition-operators.rst:89 msgid "" -"Your browser will automatically ask for your credentials - you'll then see " -"something like this:" +"Matches if date/time content is within specified period of time before now." msgstr "" -#: ../system/integrations/elasticsearch.rst:125 -msgid "Credentials" +#: ../system/core-workflows/condition-operators.rst:91 +msgid "within next (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:127 +#: ../system/core-workflows/condition-operators.rst:92 msgid "" -"Within this section Zammad displays your available users. The password is " -"provided once (upon activation) and cannot be retrieved after that." +"Matches if date/time content is within specified period of time after now." msgstr "" -#: ../system/integrations/elasticsearch.rst:131 -msgid "" -"If you need to change or reset your Elasticsearch user password, use the " -"\"Reset password\" button in the credentials table. Doing so creates a brand " -"new password for the account in question. This change is immediate, keep in " -"mind that this may affect third party tools connected to your instance." +#: ../system/core-workflows/how-do-they-work.rst:2 +msgid "How do they work?" msgstr "" -#: ../system/integrations/exchange.rst:2 -msgid "Exchange" +#: ../system/core-workflows/how-do-they-work.rst:4 +msgid "" +"Core Workflows are executed according to their priority. If two workflows " +"have the same priority, they are executed in alphabetical order based on " +"their **name**." msgstr "" -#: ../system/integrations/exchange.rst:4 +#: ../system/core-workflows/how-do-they-work.rst:8 msgid "" -"With Zammad's Exchange integration, you can easily use existing address " -"books without having to update more than one source." +"Because of the way Core Workflows work, all changes to attributes are " +"checked with the application server - please see :doc:`limitations` for " +"possible issues." msgstr "" -#: ../system/integrations/exchange.rst:7 +#: ../system/core-workflows/how-do-they-work.rst:12 msgid "" -"However, you should refrain from syncing all addresses, as the results may " -"not be what you expect (Exchange collects huge amounts of addresses). A " -"central address book of your company to sync makes more sense, as you can " -"ensure that Zammad gets only the data you need and want. Apart from this, it " -"is even not possible to sync the Global Address List (GAL) of your Exchange " -"system with Zammad." +"Below we're talking about settings that are important and not self-" +"explanatory." msgstr "" -#: ../system/integrations/exchange.rst:16 +#: ../system/core-workflows/how-do-they-work.rst:17 msgid "" -"**Exchange and LDAP:** The exchange sync can be overruled by Zammad's LDAP " -"integration. If you have the same users in both sources, the LDAP version " -"will always be Zammad's pick." +"Choose the object context you want to run the workflow in. This will decide " +"on your available attributes and actions." msgstr "" -#: ../system/integrations/exchange.rst:19 -msgid "" -"**One way sync:** the Exchange sync is one way. Exchange => Zammad. Changes " -"to your users inside of Zammad might be overwritten by the Exchange sync." +#: ../system/core-workflows/how-do-they-work.rst:20 +msgid "Ticket objects also have access to the ticket customer." msgstr "" -#: ../system/integrations/exchange.rst:24 +#: ../system/core-workflows/how-do-they-work.rst:25 msgid "" -"To configure Exchange integration, simply go to the System > Integrations > " -"Exchange in the admin panel. Press \"change\" and follow the wizard for " -"adding the needed Exchange information to Zammad. On the last two steps " -"Zammad will ask you for the address book(s) and your desired attribute " -"mapping. By default, Zammad only maps email address, first- and lastname. " -"Technically, you can map any Exchange object to a Zammad user object (this " -"also works for custom objects!)." +"Choose in which situation the workflow is applied. Contexts can be combined " +"to avoid duplicate workflows." msgstr "" -#: ../system/integrations/exchange.rst:35 -msgid "" -"If the SSL verification fails while connecting to Exchange, Zammad will ask " -"you to turn it off temporarily." +#: ../system/core-workflows/how-do-they-work.rst:30 +msgid "Creation mask" msgstr "" -#: ../system/integrations/exchange.rst:38 +#: ../system/core-workflows/how-do-they-work.rst:29 msgid "" -"Please be aware that **turning off SSL verification is a security risk**. It " -"should only be used temporarily or for testing purposes. If turned off, " -"there is no verification of the certificate, which means that every " -"presented certificate will be accepted." +"If selected, your conditions and actions will affect all applicable creation " +"masks." msgstr "" -#: ../system/integrations/exchange.rst:43 -msgid "" -"After pressing Continue, Zammad will check if the configuration is okay. You " -"can then enable Exchange and start your first sync. The sync will then run " -"hourly - if you need to change mappings or the address book(s), you can " -"change the configuration at any time." +#: ../system/core-workflows/how-do-they-work.rst:34 +msgid "Edit mask" msgstr "" -#: ../system/integrations/exchange.rst:50 +#: ../system/core-workflows/how-do-they-work.rst:33 msgid "" -"After the sync has finished, you can find the new Exchange contacts under " -"\"Users\". Zammad integrates them just as normal users." +"If selected, your conditions and actions will affect all applicable edit " +"masks." msgstr "" -#: ../system/integrations/exchange.rst:55 +#: ../system/core-workflows/how-do-they-work.rst:39 msgid "" -"In some cases you might see unique IDs as \"Login\" instead of the email " -"address. This is normal and doesn't affect the login or email mapping for " -"that entry." +"Zammad differentiates between selected and saved conditions. These can be " +"combined wherever needed." msgstr "" -#: ../system/integrations/github.rst:4 -msgid "" -"Use GitHub integration to track GitHub issues directly within Zammad " -"tickets. Add issue hyperlinks and get a live summary of metadata like status " -"(open/closed), assignee, labels, and more." +#: ../system/core-workflows/how-do-they-work.rst:42 +msgid "**⚠️ Restrict workflows to specific roles if needed!**" msgstr "" -#: ../system/integrations/github.rst:8 -msgid "Please note that our GitHub integration does not support pull requests." +#: ../system/core-workflows/how-do-they-work.rst:44 +msgid "" +"By default and unless configured in conditions, workflow rules are executed " +"for **all roles**. This also affects your customers!" msgstr "" -#: ../system/integrations/github.rst:None -msgid "Integration page for GitHub" +#: ../system/core-workflows/how-do-they-work.rst:50 +msgid "Selected Conditions" msgstr "" -#: ../system/integrations/github.rst:18 +#: ../system/core-workflows/how-do-they-work.rst:48 msgid "" -"In your GitHub settings, create a new API token under **Developer settings > " -"Personal access tokens > Generate new token**. Leave the **Scopes** section " -"empty." +"These conditions are based on form values and match if an appropriate " +"selection is made (e.g. choosing another group in the ticket without " +"saving). This applies for drafts (active selection) and currently saved " +"values." msgstr "" -#: ../system/integrations/github.rst:0 ../system/integrations/gitlab.rst:0 -msgid "Screencast showing how to create a new API token" +#: ../system/core-workflows/how-do-they-work.rst:64 +msgid "Saved Conditions" msgstr "" -#: ../system/integrations/github.rst:27 -msgid "Create a new API key with no scopes/privileges." +#: ../system/core-workflows/how-do-they-work.rst:53 +msgid "" +"These conditions only match if the selected values are stored in the " +"database. It ignores the current value or selection of the field, as long as " +"the changes are not saved (e.g. performing field operations for an existing " +"ticket, which is viewed/opened by an agent)." msgstr "" -#: ../system/integrations/github.rst:29 -msgid "🔒 **Will this work for private repos?**" +#: ../system/core-workflows/how-do-they-work.rst:60 +msgid "" +"Keep in mind that the value has to be available in the situation where you " +"need it. Otherwise the condition won't match." msgstr "" -#: ../system/integrations/github.rst:31 +#: ../system/core-workflows/how-do-they-work.rst:63 msgid "" -"No. To link private repo issues, **use the** ``repo`` **scope instead**. " -"Bear in mind that the resulting token will have `lots of permissions that it " -"doesn't actually need `_, which presents a security risk if your token ever falls into " -"the wrong hands." +"Example: you can't perform any actions with *saved condition* on a ticket in " +"creation, because there are no saved values at that time." msgstr "" -#: ../system/integrations/github.rst:37 +#: ../system/core-workflows/how-do-they-work.rst:66 msgid "" -"Unfortunately, because of how GitHub's OAuth token scopes are set up, this " -"is the only way to link issues on private repos." +"You can find a description of the condition operators for core workflows :" +"doc:`here `." msgstr "" -#: ../system/integrations/github.rst:40 -msgid "Enter your new API token in Zammad and enable GitHub integration." +#: ../system/core-workflows/how-do-they-work.rst:72 +msgid "" +"Which actions should we run on the relevant fields? The possible actions " +"depend on the object type. However, usually you can at least change the " +"visibility and whether the field is mandatory." msgstr "" -#: ../system/integrations/github.rst:0 -msgid "Screencast showing how to configure Zammad's GitHub integration" +#: ../system/core-workflows/how-do-they-work.rst:76 +msgid "Be aware that actions are not available for **related** context." msgstr "" -#: ../system/integrations/github.rst:47 +#: ../system/core-workflows/how-do-they-work.rst:78 msgid "" -"Use the default API endpoint (``https://api.github.com/graphql``) unless " -"you're using GitHub Enterprise Server." +"**Example:** Let's assume you are working in the ticket context. While you " +"can have customer *conditions*, you *can't adjust* objects with actions in " +"that scope. That's because this wouldn't have any impact on the ticket " +"dialog. Of course all ticket attributes (state, owner, ...) are available." msgstr "" -#: ../system/integrations/github.rst:50 +#: ../system/core-workflows/how-do-they-work.rst:84 msgid "" -"Once completed, a new GitHub issues tab will appear in the ticket pane. 🎉" +"Please also have a look at our :doc:`limitations` to be safe from surprises." msgstr "" -#: ../system/integrations/github.rst:59 ../system/integrations/gitlab.rst:52 -msgid "Token verification is taking a long time" +#: ../system/core-workflows/how-do-they-work.rst:88 +msgid "Available Operators" msgstr "" -#: ../system/integrations/github.rst:56 ../system/integrations/gitlab.rst:49 -msgid "" -"Slight delays are normal (<2 min.), especially for systems under heavy load." +#: ../system/core-workflows/how-do-they-work.rst:90 +msgid "The availability of operators depends on the object type and scope." msgstr "" -#: ../system/integrations/github.rst:58 +#: ../system/core-workflows/how-do-they-work.rst:94 msgid "" -"Self-hosted administrators, please check your network settings to ensure " -"that your Zammad server can reach ``api.github.com``." +"Please note that actions may or may not restrict API based access to " +"attributes. We're displaying the following icons for your overview to " +"understand these limits better:" msgstr "" -#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 -msgid "I reloaded the page and now the API token is gone" +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|api| This icon indicates the action affects the API." msgstr "" -#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 -msgid "" -"This may indicate that Zammad is still verifying your API token. Try " -"reloading the page again in a couple minutes." +#: ../system/core-workflows/how-do-they-work.rst:163 +msgid "api" msgstr "" -#: ../system/integrations/gitlab.rst:2 -msgid "GitLab" +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|ui| This icon indicates the action only affects the web interface." msgstr "" -#: ../system/integrations/gitlab.rst:4 -msgid "" -"Use GitLab integration to track GitLab issues directly within Zammad " -"tickets. Add issue hyperlinks and get a live summary of metadata like status " -"(open/closed), assignee, labels, and more." +#: ../system/core-workflows/how-do-they-work.rst:167 +msgid "ui" msgstr "" -#: ../system/integrations/gitlab.rst:8 -msgid "" -"Please note that our GitLab integration does not support merge requests." +#: ../system/core-workflows/how-do-they-work.rst:102 +msgid "show |ui|" msgstr "" -#: ../system/integrations/gitlab.rst:None -msgid "Integration page for GitLab" +#: ../system/core-workflows/how-do-they-work.rst:102 +msgid "Display the chosen field. Allows setting of values." msgstr "" -#: ../system/integrations/gitlab.rst:18 -msgid "" -"In your GitLab preferences, create a new API token under **Access Tokens**." +#: ../system/core-workflows/how-do-they-work.rst:109 +msgid "hide |ui|" msgstr "" -#: ../system/integrations/gitlab.rst:20 -msgid "Under **Select scopes**, choose ``read_api`` only." +#: ../system/core-workflows/how-do-they-work.rst:105 +msgid "" +"Hide the chosen field. However, it technically still allows setting the " +"field." msgstr "" -#: ../system/integrations/gitlab.rst:27 -msgid "🔒 **If you wish to link issues on any private repos...**" +#: ../system/core-workflows/how-do-they-work.rst:108 +msgid "" +"Please note that the field is **not** gone and still contains an existing " +"value (if set)! Consider *remove* instead, if you want this field to be gone." msgstr "" -#: ../system/integrations/gitlab.rst:29 -msgid "Your API token must belong to an account with access to those repos." +#: ../system/core-workflows/how-do-they-work.rst:112 +msgid "remove |ui|" msgstr "" -#: ../system/integrations/gitlab.rst:31 -msgid "Enter your new API token in Zammad and enable GitLab integration." +#: ../system/core-workflows/how-do-they-work.rst:112 +msgid "Entirely removes the field. The field value will not be evaluated." msgstr "" -#: ../system/integrations/gitlab.rst:0 -msgid "Screencast showing how to configure Zammad's GitLab integration" +#: ../system/core-workflows/how-do-they-work.rst:115 +msgid "set mandatory |ui| |api|" msgstr "" -#: ../system/integrations/gitlab.rst:40 -msgid "" -"Use the default API endpoint (``https://gitlab.com/api/graphql``) unless " -"you're a self-hosted GitLab user." +#: ../system/core-workflows/how-do-they-work.rst:115 +msgid "Sets the field to mandatory." msgstr "" -#: ../system/integrations/gitlab.rst:43 -msgid "" -"Once completed, a new GitLab issues tab will appear in the ticket pane. 🎉" +#: ../system/core-workflows/how-do-they-work.rst:118 +msgid "set optional |ui| |api|" msgstr "" -#: ../system/integrations/gitlab.rst:51 -msgid "" -"Self-hosted administrators, please check your network settings to ensure " -"that your Zammad server can reach ``gitlab.com``." +#: ../system/core-workflows/how-do-they-work.rst:118 +msgid "Sets the field to optional." msgstr "" -#: ../system/integrations/i-doit.rst:2 -msgid "i-doit" +#: ../system/core-workflows/how-do-they-work.rst:124 +msgid "add option |ui| |api|" msgstr "" -#: ../system/integrations/i-doit.rst:4 -msgid "" -"`i-doit `_ is an open-source **configuration " -"management database** - in other words, a tool for keeping tabs on every " -"single piece of your physical and digital infrastructure, from network " -"equipment to virtual machines on down to the faceplates on your rack shelves " -"and more." +#: ../system/core-workflows/how-do-they-work.rst:121 +msgid "Allows adding options to tree selects or selects." msgstr "" -#: ../system/integrations/i-doit.rst:10 +#: ../system/core-workflows/how-do-they-work.rst:123 msgid "" -"What's that got to do with Zammad? Well, if you used tickets to track issues " -"with all that hardware, you might start wishing there was a way they could " -"talk to each other." -msgstr "" - -#: ../system/integrations/i-doit.rst:14 -msgid "Zammad gives you two:" +"You have to use the \"remove option\" before performing this action. It " +"allows you to use *existing* configured values." msgstr "" -#: ../system/integrations/i-doit.rst:17 -msgid "1. Add i-doit Links to Zammad Tickets" +#: ../system/core-workflows/how-do-they-work.rst:128 +msgid "remove option |ui| |api|" msgstr "" -#: ../system/integrations/i-doit.rst:20 ../system/integrations/i-doit.rst:80 -msgid "What Users See" +#: ../system/core-workflows/how-do-they-work.rst:127 +msgid "" +"Allows removing options from tree selects or selects. It allows you to use " +"*existing* configured values." msgstr "" -#: ../system/integrations/i-doit.rst:26 -msgid "i-doit integration in Zammad's ticket pane" +#: ../system/core-workflows/how-do-they-work.rst:134 +msgid "set fixed to |ui| |api|" msgstr "" -#: ../system/integrations/i-doit.rst:26 -msgid "" -"The i-doit integration will appear under a new 🖨 tab in the ticket pane." +#: ../system/core-workflows/how-do-they-work.rst:131 +msgid "Reduces the available options by your selection." msgstr "" -#: ../system/integrations/i-doit.rst:28 +#: ../system/core-workflows/how-do-they-work.rst:133 msgid "" -"i-doit integration puts a new tab in Zammad's ticket pane where you can add " -"links to existing i-doit devices for easy reference. (See our :user-docs:" -"`user documentation ` to learn " -"how it works in practice)." +"This reduces your workflows in terms of *add option* and *remove option*." msgstr "" -#: ../system/integrations/i-doit.rst:36 ../system/integrations/i-doit.rst:93 -msgid "How to Set it Up" +#: ../system/core-workflows/how-do-they-work.rst:137 +msgid "fill in |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:38 -msgid "" -"It requires i-doit's `API Add-on `_. Make sure to have it properly set up. Use the following setting:" +#: ../system/core-workflows/how-do-they-work.rst:137 +msgid "Allows filling in of string and integer fields with your values." msgstr "" -#: ../system/integrations/i-doit.rst:42 -msgid "Active: ``Yes``" +#: ../system/core-workflows/how-do-they-work.rst:141 +msgid "fill in empty |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:43 -msgid "Enforce authentication by username and password: ``No``" +#: ../system/core-workflows/how-do-they-work.rst:140 +msgid "" +"Allows filling in of string and integer fields with your values **if the " +"field is empty**." msgstr "" -#: ../system/integrations/i-doit.rst:45 -msgid "" -"To set it up, enable the integration in the Zammad admin panel under " -"**System > Integrations > i-doit**:" +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "select |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "i-doit settings within the integration pages" +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "Select a specific value within a select, tree select or boolean field." msgstr "" -#: ../system/integrations/i-doit.rst:53 -msgid "The root URL of your i-doit installation." +#: ../system/core-workflows/how-do-they-work.rst:153 +msgid "auto select |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:62 -msgid "API token" +#: ../system/core-workflows/how-do-they-work.rst:147 +msgid "Helps users with tree select and select fields:" msgstr "" -#: ../system/integrations/i-doit.rst:56 +#: ../system/core-workflows/how-do-they-work.rst:149 msgid "" -"Found in the i-doit admin panel under **Interfaces / external data > JSON-" -"RPC API > Common Settings**." +"If the field has only one option available for selection and no value yet, " +"the value will be automatically set." msgstr "" -#: ../system/integrations/i-doit.rst:0 -msgid "i-doit administration interface with API configuration" +#: ../system/core-workflows/how-do-they-work.rst:152 +msgid "" +"This option only works if you have one value and doesn't work if there is " +"more than one option available." msgstr "" -#: ../system/integrations/i-doit.rst:67 -msgid "Client ID" +#: ../system/core-workflows/how-do-they-work.rst:157 +msgid "set readonly |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:65 -msgid "A unique name to identify Zammad within i-doit." +#: ../system/core-workflows/how-do-they-work.rst:156 +msgid "" +"Allows you to display an attribute as read only (which means no changes are " +"possible)." msgstr "" -#: ../system/integrations/i-doit.rst:67 -msgid "(Zammad does not require you to enter a value here, but i-doit might!)" +#: ../system/core-workflows/how-do-they-work.rst:161 +msgid "unset readonly |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:70 +#: ../system/core-workflows/how-do-they-work.rst:160 msgid "" -"Here you can decide if the certificate of your i-doit system has to be " -"verified or not. In case you are using custom certificates, please have a " -"look at :doc:`how to add them to Zammad `." -msgstr "" - -#: ../system/integrations/i-doit.rst:77 -msgid "2. List / Create Zammad Tickets in i-doit" +"In case a workflow set the field in question to read only, you can undo this " +"with option above." msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "Zammad integration in i-doit's device view" +#: ../system/core-workflows/how-do-they-work.rst:172 +msgid "Stop after match" msgstr "" -#: ../system/integrations/i-doit.rst:86 +#: ../system/core-workflows/how-do-they-work.rst:174 msgid "" -"i-doit's ticket system integration gives you a way to see all the tickets " -"for a given device without ever leaving i-doit. (See our :user-docs:`user " -"documentation ` to learn how it " -"works in practice)." +"Here you can decide if other workflows are executed after the current one." msgstr "" -#: ../system/integrations/i-doit.rst:95 +#: ../system/core-workflows/how-do-they-work.rst:176 msgid "" -"Enable this integration in the i-doit admin panel under **Interfaces / " -"external data > Trouble Ticket System (TTS) > Configuration**:" +"If set to ``no`` (default), further workflows will be executed if they match " +"the condition. In this case, it is possible that your actions from the " +"current workflow can be overwritten by another workflow." msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "i-doit administration interface with TTS configuration" +#: ../system/core-workflows/how-do-they-work.rst:180 +msgid "" +"If set to ``yes``, no further worflows will be executed after the current " +"one." msgstr "" -#: ../system/integrations/i-doit.rst:104 -msgid "TTS-Type" +#: ../system/core-workflows/how-do-they-work.rst:184 +msgid "Priority" msgstr "" -#: ../system/integrations/i-doit.rst:104 -msgid "``Zammad``" +#: ../system/core-workflows/how-do-they-work.rst:186 +msgid "" +"You can define the sequence, in which the workflows are executed. The " +"default value is ``500``." msgstr "" -#: ../system/integrations/i-doit.rst:115 -msgid "Username / Password" +#: ../system/core-workflows/how-do-they-work.rst:189 +msgid "" +"The workflows are executed in ascending order by their priority. That means " +"lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." msgstr "" -#: ../system/integrations/i-doit.rst:107 -msgid "Login credentials for a Zammad agent." +#: ../system/core-workflows/learn-by-example.rst:2 +msgid "Learn by Example" msgstr "" -#: ../system/integrations/i-doit.rst:109 +#: ../system/core-workflows/learn-by-example.rst:4 msgid "" -"This agent must have **read permission** for all :doc:`groups ` that plan on using the i-doit integration." +"This page provides some basic examples for Core Workflows. Of course you can " +"build much more complex workflows if needed." msgstr "" -#: ../system/integrations/i-doit.rst:113 +#: ../system/core-workflows/learn-by-example.rst:7 msgid "" -"You may even wish to create a dedicated agent account just for this " -"integration (otherwise, if the agent ever changes her password, you will " -"have to remember to update it here)." +"To learn about Core Workflows in detail, first go to :doc:`how-do-they-work`." msgstr "" -#: ../system/integrations/i-doit.rst:117 -msgid "URL incl. protocol" +#: ../system/core-workflows/learn-by-example.rst:10 +msgid "Group Based Examples" msgstr "" -#: ../system/integrations/i-doit.rst:118 -msgid "``https://your.zammad.domain``" +#: ../system/core-workflows/learn-by-example.rst:12 +msgid "" +"All following workflows have the same base configurations. The workflow may " +"not use them all." msgstr "" -#: ../system/integrations/index.rst:2 -msgid "Integrations" +#: ../system/core-workflows/learn-by-example.rst:15 +msgid "Groups:" msgstr "" -#: ../system/integrations/index.rst:4 +#: ../system/core-workflows/learn-by-example.rst:20 +msgid "Attributes:" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:22 +msgid "Category (Single tree selection field, not mandatory, agents only)" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:23 msgid "" -"Zammad offers numerous integrations that add rich features to your instance." +"Approved (Boolean field, not mandatory, not shown, ``false`` as default)" msgstr "" -#: ../system/integrations/index.rst:6 -msgid "We're still working on this part of our documentation, stay tight!" +#: ../system/core-workflows/learn-by-example.rst:24 +msgid "Operating System (Text field, not mandatory, not shown)" msgstr "" -#: ../system/integrations/index.rst:10 -msgid "Integrations for Phone Systems" +#: ../system/core-workflows/learn-by-example.rst:25 +msgid "Software used (Single selection field, not mandatory, not shown)" msgstr "" -#: ../system/integrations/index.rst:14 -msgid "" -"Your VoIP provider or telephony system is not listed? Possibly your provider " -"supports Zammad by using the generic CTI - if you're unsure ask your " -"provider." +#: ../system/core-workflows/learn-by-example.rst:68 +msgid "Group specific values and fields" msgstr "" -#: ../system/integrations/index.rst:18 +#: ../system/core-workflows/learn-by-example.rst:28 msgid "" -"Provider does not support Zammad? Consider creating a `feature request in " -"the Zammad Community `_." +"This workflow set depends on the category field. It reduces the available " +"set of values based on the group selected." msgstr "" -#: ../system/integrations/index.rst:31 -msgid "Integrations for Authentication and Customers" +#: ../system/core-workflows/learn-by-example.rst:33 +msgid "Workflow 2nd Level group" msgstr "" -#: ../system/integrations/index.rst:44 -msgid "Integrations for Monitoring Systems" +#: ../system/core-workflows/learn-by-example.rst:35 +msgid "" +"This reduces the category options to ``2nd Level/*``, ``Internal/*`` and " +"``Others``. It also sets further required fields to mandatory and visible." msgstr "" -#: ../system/integrations/index.rst:46 -msgid "This section currently misses the following integrations:" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for 2nd level" msgstr "" -#: ../system/integrations/index.rst:48 -msgid "Icinga" +#: ../system/core-workflows/learn-by-example.rst:43 +msgid "Workflow Support group" msgstr "" -#: ../system/integrations/index.rst:49 -msgid "Monit" +#: ../system/core-workflows/learn-by-example.rst:45 +msgid "" +"This reduces the category options to ``Support/*``, ``Internal/*`` and " +"``Others``. It also sets further required fields to visible." msgstr "" -#: ../system/integrations/index.rst:50 -msgid "Nagios" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for support" msgstr "" -#: ../system/integrations/index.rst:60 -msgid "Integrations for Issue Trackers" +#: ../system/core-workflows/learn-by-example.rst:53 +msgid "Workflow Sales group" msgstr "" -#: ../system/integrations/index.rst:70 -msgid "Other Integrations" +#: ../system/core-workflows/learn-by-example.rst:55 +msgid "" +"This reduces the category options to ``Sales/*``, ``Internal/*`` and " +"``Others``." msgstr "" -#: ../system/integrations/index.rst:72 -msgid "" -"This section will hold any other integration that can't be grouped up (yet)." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for sales" msgstr "" -#: ../system/integrations/ldap/index.rst:2 -msgid "LDAP / Active Directory" +#: ../system/core-workflows/learn-by-example.rst:68 +#: ../system/integrations/slack.rst:88 +msgid "The Result" msgstr "" -#: ../system/integrations/ldap/index.rst:4 +#: ../system/core-workflows/learn-by-example.rst:63 msgid "" -"Zammad comes with a powerful LDAP integration that allows you to have a " -"single source of truth. By this you reduce the number of login credentials " -"your user has to remember." +"This is what the agent would experience with the above workflows in place." msgstr "" -#: ../system/integrations/ldap/index.rst:10 +#: ../system/core-workflows/learn-by-example.rst:0 msgid "" -"The LDAP source is also a perfect candidate for Zammad's :docs:`Kerberos " -"Single Sign-On ` but also works as addition " -"to other :doc:`/settings/security/third-party`." +"Workflow shows objects and limits options based on selections on the group" msgstr "" -#: ../system/integrations/ldap/index.rst:None -msgid "Zammands LDAP management page" +#: ../system/core-workflows/learn-by-example.rst:90 +msgid "Approval process" msgstr "" -#: ../system/integrations/ldap/index.rst:25 -msgid "📝 :doc:`manage`" +#: ../system/core-workflows/learn-by-example.rst:71 +msgid "" +"In this case ``approved`` is visible to agents by default. For this " +"workflow, an additional role ``Approval person`` is required (no further " +"permissions)." msgstr "" -#: ../system/integrations/ldap/index.rst:25 -msgid "Add, modify, remove or re-arrange your LDAP-Sources as needed." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that restricts an approval attribute to specific roles" msgstr "" -#: ../system/integrations/ldap/index.rst:30 -msgid "Before you continue, please note the following limitations." +#: ../system/core-workflows/learn-by-example.rst:81 +msgid "" +"This workflow may work best in combination with a :doc:`trigger ` but technically, this is not required." msgstr "" -#: ../system/integrations/ldap/index.rst:32 -msgid "Mapping / Synchronizing organizations is not possible" +#: ../system/core-workflows/learn-by-example.rst:84 +msgid "" +"Select fields may be a better approach because they allow more values than " +"just a simple ``true`` or ``false``." msgstr "" -#: ../system/integrations/ldap/index.rst:36 +#: ../system/core-workflows/learn-by-example.rst:0 msgid "" -"You may want to consider using domain based assignments to overcome this " -"issue. Learn more on :doc:`/manage/organizations/index`." +"Workflow fixes possible values of \"Approved ?\" to a specific selection " +"depending on the users role" msgstr "" -#: ../system/integrations/ldap/index.rst:39 +#: ../system/core-workflows/learn-by-example.rst:103 +msgid "State dependent mandatory fields" +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:93 msgid "" -"Zammad's LDAP sync is one way. Editing user settings or permissions may be " -"overwritten upon the next sync depending on your configuration." +"This workflow sets ``Category`` to mandatory if the agent wants to set the " +"states ``closed`` or ``pending close`` to enforce categorization." msgstr "" -#: ../system/integrations/ldap/index.rst:41 -msgid "Nested groups are not supported." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that sets fields to mandatory on specific states" msgstr "" -#: ../system/integrations/ldap/index.rst:42 -msgid "Synchronizing user avatars from LDAP is not supported." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "" +"Workflow sets category field to mandatory upon choosing closed or pending " +"close as state" msgstr "" -#: ../system/integrations/ldap/index.rst:43 -msgid "Unlike user filters, group filters cannot be changed." +#: ../system/core-workflows/learn-by-example.rst:106 +msgid "Manual Ticket Handover Process" msgstr "" -#: ../system/integrations/ldap/index.rst:44 -msgid "" -"When a user originates from an LDAP server, Zammad will try to verify the " -"login credentials against LDAP first - if this fails Zammad will check its " -"local database." +#: ../system/core-workflows/learn-by-example.rst:108 +msgid "This example covers the handover of a ticket from one agent to another:" msgstr "" -#: ../system/integrations/ldap/index.rst:50 +#: ../system/core-workflows/learn-by-example.rst:110 msgid "" -"Users can have local passwords even if they're LDAP users! You can learn " -"more about user accounts in general on :doc:`/manage/users/index`." +"When the ticket owner is modified, a new text field (\"Handover\") shows up " +"for a comment" msgstr "" -#: ../system/integrations/ldap/index.rst:54 +#: ../system/core-workflows/learn-by-example.rst:112 msgid "" -"When several LDAP sources contain the same user (meaning the same email " -"address), the user in question will be updated with every source configured. " -"*The last LDAP source will win.*" +"This may only be visible when the owner is changed, therefore it has to be " +"hidden in general" msgstr "" -#: ../system/integrations/ldap/index.rst:58 -msgid "" -"This is subject to change with `Issue 4109 `_ in the future." +#: ../system/core-workflows/learn-by-example.rst:114 +msgid "The input in this handover text field is mandatory" msgstr "" -#: ../system/integrations/ldap/index.rst:60 +#: ../system/core-workflows/learn-by-example.rst:115 msgid "" -"Synchronization statistics currently affect *all* configured LDAP sources. " -"This also applies for newly added or updated sources." +"After submitting changes, the value of the handover field must be added as " +"an note to the ticket (via trigger)" msgstr "" -#: ../system/integrations/ldap/index.rst:63 -msgid "" -"This is subject to change with `Issue 4108 `_ in the future." +#: ../system/core-workflows/learn-by-example.rst:121 +msgid "Hiding handover field" msgstr "" -#: ../system/integrations/ldap/index.rst:65 -msgid "" -"Zammad currently has limited fallback server support. You can workaround " -"this by providing several sources - however, ensure to have the exact same " -"configuration on your fallback." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Hiding the handover field in core workflows" msgstr "" -#: ../system/integrations/ldap/index.rst:69 -msgid "" -"This is subject to improve with `Issue 4107 `_ in the future." +#: ../system/core-workflows/learn-by-example.rst:126 +msgid "Showing handover field and setting it to mandatory" msgstr "" -#: ../system/integrations/ldap/index.rst:76 -msgid "" -"This section holds all requests Zammad handled for all LDAP sources. These " -"entries can either contain synchronization information or logins " -"(authentication attempts via Zammad's login interface)." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Showing the handover field and set it as mandatory" msgstr "" -#: ../system/integrations/ldap/index.rst:80 -msgid "" -"By clicking on any request, Zammad will provide even more information. The " -"provided information can be useful when something does not work as expected." +#: ../system/core-workflows/learn-by-example.rst:131 +msgid "Trigger writing handover input to a new article" msgstr "" -#: ../system/integrations/ldap/index.rst:85 -msgid "" -"Especially a LDAP synchronization can cause many log entries. The web " -"interface will always limit the number of shown entries to the last 50 " -"entries." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Write handover content to a new article" msgstr "" -#: ../system/integrations/ldap/index.rst:None +#: ../system/core-workflows/learn-by-example.rst:133 msgid "" -"Screencast showing LDAP integration log entries and a detail view on\n" -"an entry." +"As a result, the ticket includes an article of the type note which includes " +"the predefined text and the handover comment." msgstr "" -#: ../system/integrations/ldap/manage.rst:2 -msgid "Manage LDAP-Sources" +#: ../system/core-workflows/limitations.rst:6 +msgid "Core Workflows do not replace Triggers" msgstr "" -#: ../system/integrations/ldap/manage.rst:6 +#: ../system/core-workflows/limitations.rst:5 msgid "" -"Please keep in mind all current limitations for the LDAP synchronization. " -"This will help to understand scopes of the following operations better." +"Workflows manipulate the behavior of fields. However, they do not set values " +"in fields because of actions." msgstr "" -#: ../system/integrations/ldap/manage.rst:65 -msgid "Add new source" +#: ../system/core-workflows/limitations.rst:16 +msgid "API calls are only partly affected" msgstr "" -#: ../system/integrations/ldap/manage.rst:10 +#: ../system/core-workflows/limitations.rst:9 msgid "" -"Using the *New Source* button allows you to add new LDAP sources to your " -"installation. You're not limited in the number of sources, however, keep in " -"mind that many sources will also take more time to synchronize." +"Some options affect UI only and thus do not restrict responses and calls." msgstr "" -#: ../system/integrations/ldap/manage.rst:14 -msgid "" -"You can choose between different encryption types, namely *SSL* and " -"*STARTTLS* or none of them (\"*No SSL*\"). If you choose *SSL* or " -"*STARTTLS*, Zammad will display an additional *SSL verification* option that " -"allows you to disable the verification, e.g. for self-signed SSL " -"certificates. You can also tell Zammad to use a different port by appending " -"``:`` to your hostname/IP." +#: ../system/core-workflows/limitations.rst:11 +msgid "This affects the following actions:" msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "" -"Screenshot of configuring a new LDAP source with SSL encryption and SSL " -"verification" +#: ../system/core-workflows/limitations.rst:13 +msgid "select" msgstr "" -#: ../system/integrations/ldap/manage.rst:26 -msgid "" -"New Source with SSL transport security enabled and certificate verification" +#: ../system/core-workflows/limitations.rst:14 +msgid "auto select" msgstr "" -#: ../system/integrations/ldap/manage.rst:30 -msgid "" -"Using an user filter can be a good idea if you only require a small subset " -"of your LDAP users in Zammad." +#: ../system/core-workflows/limitations.rst:15 +msgid "show" msgstr "" -#: ../system/integrations/ldap/manage.rst:42 -msgid "This especially affects inactive users" +#: ../system/core-workflows/limitations.rst:16 +msgid "hide" msgstr "" -#: ../system/integrations/ldap/manage.rst:34 -msgid "" -"As every LDAP behaves differently on which attributes and how they are set, " -"Zammad doesn't care about any flags." +#: ../system/core-workflows/limitations.rst:25 +msgid "Some fields stay unavailable to customers" msgstr "" -#: ../system/integrations/ldap/manage.rst:37 +#: ../system/core-workflows/limitations.rst:19 msgid "" -"Users that no longer are returned by your LDAP source will automatically be " -"set to inactive. Zammad assumes that the user was deactivated." +"For technical and security reasons, some default fields (the pale ones you " +"can't edit) stay unavailable for display and usage on customer permissions." msgstr "" -#: ../system/integrations/ldap/manage.rst:41 +#: ../system/core-workflows/limitations.rst:23 msgid "" -"Users will never be removed automatically! If you want to remove obsolete " -"users, use :doc:`/system/data-privacy`." +"If you require your customers to change e.g. priorities, please consider " +"using workarounds via :doc:`/system/objects` and :doc:`/manage/trigger`." msgstr "" -#: ../system/integrations/ldap/manage.rst:46 -msgid "Active Directory admins" +#: ../system/core-workflows/limitations.rst:29 +msgid "Ticket title changes not supported in edit mask" msgstr "" -#: ../system/integrations/ldap/manage.rst:45 +#: ../system/core-workflows/limitations.rst:28 msgid "" -"Active Directories are quite specific on how to filter for active users only " -"- please see the `Microsoft documentation `_ for more " -"information." +"It is currently not possible to perform changes of the ticket title in the " +"edit mask (e.g. renaming, set to read-only)." msgstr "" -#: ../system/integrations/ldap/manage.rst:51 -msgid "" -"*Do not* manually write pathes of either LDAP attributes or groups. If " -"Zammad does not display them, it either cannot find them or you have a lot " -"of users that don't have the attributes populated." +#: ../system/core-workflows/limitations.rst:37 +msgid "What is out of scope of Core Workflows?" msgstr "" -#: ../system/integrations/ldap/manage.rst:55 +#: ../system/core-workflows/limitations.rst:32 msgid "" -"Zammad will always only return attributes that are filled - this reduces the " -"returned list of attributes greatly." +"There are some things that would count as workflow but are either done via :" +"doc:`/manage/trigger` or :doc:`/manage/scheduler`." msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing how to add a new LDAP source" +#: ../system/core-workflows/limitations.rst:35 +msgid "Such as (but not limited to):" msgstr "" -#: ../system/integrations/ldap/manage.rst:63 -msgid "" -"If your LDAP system doesn't allow anonymous bind, Zammad detects it and " -"provides you an editable \"Base DN\" *text* field instead of a prefilled " -"*select* field." +#: ../system/core-workflows/limitations.rst:37 +msgid "up- or downgrade permissions of users" msgstr "" -#: ../system/integrations/ldap/manage.rst:81 -msgid "Review or edit existing source" +#: ../system/core-workflows/limitations.rst:38 +msgid "affecting article creation or listing" msgstr "" -#: ../system/integrations/ldap/manage.rst:68 +#: ../system/data-privacy.rst:2 +msgid "Data Privacy" +msgstr "" + +#: ../system/data-privacy.rst:4 msgid "" -"Clicking on a LDAP source will provide a configuration and mapping overview." +"For compliance with GDPR and other data privacy laws, you may wish to " +"**permanently delete users from the system**, along with **all of their " +"associated tickets**." msgstr "" -#: ../system/integrations/ldap/manage.rst:70 +#: ../system/data-privacy.rst:8 msgid "" -"If needed you can then use the *Change* button to update either the name, " -"active state or the whole configuration. If you're changing the whole " -"configuration, the dialogue will be identical to the source creation." +"You can create manual deletion tasks or even automated deletion tasks for " +"tickets and users based on custom conditions via :doc:`scheduler `!" msgstr "" -#: ../system/integrations/ldap/manage.rst:76 +#: ../system/data-privacy.rst:12 msgid "" -"Did your LDAP server change? Different LDAP servers have different " -"structures and default attributes. This causes the LDAP synchronization to " -"likely fail. Consider removing the affected source and re-add it." +"Access to this panel requires ``admin.data_privacy`` permissions (introduced " +"in Zammad 3.5)." msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing the update of the source name." +#: ../system/data-privacy.rst:15 +msgid "" +"On older systems that have not been updated yet, customers can also be :docs:" +"`deleted via the Zammad console `." msgstr "" -#: ../system/integrations/ldap/manage.rst:89 -msgid "Re-arrange LDAP source's order" +#: ../system/data-privacy.rst:22 +msgid "User deletion dialog in the Data Privacy panel" msgstr "" -#: ../system/integrations/ldap/manage.rst:84 +#: ../system/data-privacy.rst:22 msgid "" -"You can change the synchronization order for each source at any time. Zammad " -"will synchronize the sources from top to bottom." +"The user deletion dialog lists some of the tickets that will be removed from " +"the system along with the user." msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "" -"Screencasting showing how to change the source order by using\n" -"drag and drop." +#: ../system/data-privacy.rst:27 +msgid "Deleting Users via GUI" msgstr "" -#: ../system/integrations/ldap/manage.rst:101 -msgid "Remove a source" +#: ../system/data-privacy.rst:29 +msgid "🔥 **All deletions are FINAL!**" msgstr "" -#: ../system/integrations/ldap/manage.rst:92 -msgid "" -"If you no longer need the a LDAP source or simply want to start over, you " -"can remove them at any time. This will not remove synchronized users, data " -"synchronized or permissions." +#: ../system/data-privacy.rst:31 +msgid "Once you click “Delete”, the action cannot be canceled or undone." msgstr "" -#: ../system/integrations/ldap/manage.rst:98 +#: ../system/data-privacy.rst:33 msgid "" -"Not sure if you'd need the source later on? Set the source to inactive " -"instead of removing it - see *Review or edit existing source* for more." +"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." msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing how to remove LDAP sources." +#: ../system/data-privacy.rst:36 +msgid "**The following records cannot be deleted:**" msgstr "" -#: ../system/integrations/pgp/index.rst:2 -msgid "PGP" +#: ../system/data-privacy.rst:38 +msgid "your own account" msgstr "" -#: ../system/integrations/pgp/index.rst:7 -msgid "" -"Pretty Good Privacy (PGP) is another method for secure email communication. " -"With PGP, you can exchange **signed** and **encrypted** messages with others." +#: ../system/data-privacy.rst:39 +msgid "the system's last remaining administrator account" msgstr "" -#: ../system/integrations/pgp/index.rst:13 -#: ../system/integrations/smime/index.rst:17 -msgid "Signing" +#: ../system/data-privacy.rst:42 +msgid "Step 1: Find a User / Confirm Deletion" msgstr "" -#: ../system/integrations/pgp/index.rst:11 -msgid "is a proof that a message hasn't been manipulated on its way." +#: ../system/data-privacy.rst:44 +msgid "There are three ways to access the user deletion dialog:" msgstr "" -#: ../system/integrations/pgp/index.rst:13 -msgid "" -"In other words, it guarantees message **integrity** and **authenticity**." +#: ../system/data-privacy.rst:51 +msgid "**from the user's profile**" msgstr "" -#: ../system/integrations/pgp/index.rst:19 -#: ../system/integrations/smime/index.rst:22 -msgid "Encryption" +#: ../system/data-privacy.rst:0 +msgid "Accessing the user deletion dialog in a user profile" msgstr "" -#: ../system/integrations/pgp/index.rst:16 -#: ../system/integrations/smime/index.rst:20 -msgid "" -"scrambles a message so that it can only be unscrambled by the intended " -"recipient." +#: ../system/data-privacy.rst:51 +msgid "Click **Action > Delete**." msgstr "" -#: ../system/integrations/pgp/index.rst:19 -msgid "" -"In other words, it guarantees message **privacy** and **data security**." +#: ../system/data-privacy.rst:58 +msgid "**in the “Manage > Users” Admin Panel**" msgstr "" -#: ../system/integrations/pgp/index.rst:25 -msgid "Screenshot of ticket creation with encrypt and sign buttons" +#: ../system/data-privacy.rst:0 +msgid "Accessing the user deletion dialog under “Users” in the Admin Panel" msgstr "" -#: ../system/integrations/pgp/index.rst:25 -msgid "" -"Once PGP has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " -"appear in the ticket composer." +#: ../system/data-privacy.rst:58 +msgid "Use the **⋮ Actions** menu for the target user." msgstr "" -#: ../system/integrations/pgp/index.rst:28 -msgid "**Sign button not visible?**" +#: ../system/data-privacy.rst:66 ../system/data-privacy.rst:104 +msgid "**in the “System > Data Privacy” Admin Panel**" msgstr "" -#: ../system/integrations/pgp/index.rst:30 +#: ../system/data-privacy.rst:0 msgid "" -"Please note that the signing of emails is based on the outgoing email " -"account. That means you have to choose a group with a sender email account, " -"which has a private key assigned." +"Accessing the user deletion dialog under “Data Privacy” in the Admin Panel" msgstr "" -#: ../system/integrations/pgp/index.rst:35 -msgid "Handling of Keys" +#: ../system/data-privacy.rst:65 +msgid "" +"Use the **New Deletion Task** button. Search for users by name or email " +"address." msgstr "" -#: ../system/integrations/pgp/index.rst:36 -msgid "" -"To use the PGP function, you have to enable the integration (PGP) by " -"switching the toggle to *enabled*." +#: ../system/data-privacy.rst:79 +msgid "**Delete organizations**" msgstr "" -#: ../system/integrations/pgp/index.rst:39 +#: ../system/data-privacy.rst:69 msgid "" -"You can add keys by clicking the *add key* button. The keys can be imported " -"from a file or you can paste the content of the key in the text box." +"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:" msgstr "" -#: ../system/integrations/pgp/index.rst:42 -msgid "**Which keys do I have to import?**" +#: ../system/data-privacy.rst:0 +msgid "Deleting an organization via the user deletion dialog" msgstr "" -#: ../system/integrations/pgp/index.rst:44 +#: ../system/data-privacy.rst:78 msgid "" -"For **signing** *outgoing* emails, you have to import the private key of " -"your Zammad email account." +"If this option does not appear, make sure there are no pending deletion " +"tasks for other customers from this organization." msgstr "" -#: ../system/integrations/pgp/index.rst:47 -msgid "" -"For **encrypting** *outgoing* emails, you have to import the public key of " -"the customer's email account." +#: ../system/data-privacy.rst:82 +msgid "Step 2: Monitor Deletion Job Status" msgstr "" -#: ../system/integrations/pgp/index.rst:50 +#: ../system/data-privacy.rst:84 msgid "" -"For **verifying the signature** of signed *incoming* emails, you have to " -"import the public key of the customer." +"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:" msgstr "" -#: ../system/integrations/pgp/index.rst:53 -msgid "" -"For **decrypting** of encrypted *incoming* emails, you have to import the " -"private key of your Zammad email account." +#: ../system/data-privacy.rst:98 +msgid "**in the Activity Stream**" msgstr "" -#: ../system/integrations/pgp/index.rst:57 -msgid "Import Keys From a File" +#: ../system/data-privacy.rst:0 +msgid "Activity Stream showing data privacy tasks" msgstr "" -#: ../system/integrations/pgp/index.rst:58 -msgid "You can import keys from a file in the section **Upload key**:" +#: ../system/data-privacy.rst:94 +msgid "" +"For each deleted user, the Activity Stream will be updated twice—once when " +"the task is created, and once when it's complete." msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of adding a key via file" +#: ../system/data-privacy.rst:97 +msgid "" +"These notifications are only visible to users with ``admin.data_privacy`` " +"permissions." msgstr "" -#: ../system/integrations/pgp/index.rst:64 +#: ../system/data-privacy.rst:0 msgid "" -"**Supported file formats:** ASCII-armor as well as binary GPG format " -"(basically any GPG supported key format) is supported here." +"The task list within Data Privacy shows removals being in progress and " +"completed." msgstr "" -#: ../system/integrations/pgp/index.rst:68 -msgid "Import Keys by Pasting the Content" +#: ../system/data-privacy.rst:107 +msgid "Frequently Asked Questions" msgstr "" -#: ../system/integrations/pgp/index.rst:69 -msgid "You can also paste the key's content in the section **paste key**:" +#: ../system/data-privacy.rst:121 +msgid "What happens if I receive an email from a deleted customer?" msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of adding a key via pasting" +#: ../system/data-privacy.rst:110 +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/integrations/pgp/index.rst:75 +#: ../system/data-privacy.rst:115 msgid "" -"**Supported format:** Please note that only ASCII-armor is supported here." +"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**." msgstr "" -#: ../system/integrations/pgp/index.rst:78 -msgid "Deleting Keys" +#: ../system/data-privacy.rst:130 +msgid "What about user information stored in internal notes or other messages?" msgstr "" -#: ../system/integrations/pgp/index.rst:79 +#: ../system/data-privacy.rst:124 msgid "" -"If you want to delete a specific key, you can do it by clicking on the menu " -"in the *actions* column and select **delete**:" +"The deletion process removes **user accounts and associated tickets only**." msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of deleting a key" +#: ../system/data-privacy.rst:126 +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." msgstr "" -#: ../system/integrations/pgp/index.rst:88 -msgid "Downloading Keys" +#: ../system/data-privacy.rst:137 +msgid "I deleted an user and can still see a message they sent!" msgstr "" -#: ../system/integrations/pgp/index.rst:89 +#: ../system/data-privacy.rst:133 msgid "" -"If you want to download your keys, you can do this as well via corresponding " -"action buttons. Depending on the key, you can choose wether you want to " -"download the private or the public key." +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:95 -#: ../system/integrations/smime/manage-certificates.rst:76 -msgid "Default Behavior" +#: ../system/data-privacy.rst:141 +msgid "I removed a customer, now my reporting is off!" msgstr "" -#: ../system/integrations/pgp/index.rst:96 +#: ../system/data-privacy.rst:140 msgid "" -"Here you can adjust on per group basis, if *sign* and *encryption* is on or " -"off by default. Please be aware, that agents can always override the setting " -"for each individual article." +"When removing users and their tickets, all references are removed. This also " +"affects e.g. Reporting - these information are lost." msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Adjusting default behavior on per group basis" +#: ../system/data-privacy.rst:145 +msgid "How long does Zammad store created tasks?" msgstr "" -#: ../system/integrations/pgp/index.rst:107 +#: ../system/data-privacy.rst:144 msgid "" -"Here you can see the last actions regarding signing and encryption and if " -"they were successful." -msgstr "" - -#: ../system/integrations/pgp/index.rst:117 -msgid "**Sign button is not visible, but keys are imported.**" +"Please see the on-premise data section of the :docs:`data privacy ` chapter." msgstr "" -#: ../system/integrations/pgp/index.rst:115 -msgid "Did you choose a group in the ticket?" +#: ../system/data-privacy.rst:150 +msgid "What about re-assigned tickets? I want to delete them, too." msgstr "" -#: ../system/integrations/pgp/index.rst:116 +#: ../system/data-privacy.rst:148 msgid "" -"Did you import a private key for the email adress, which is used for " -"outgoing emails in the group?" +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:122 -msgid "**How to obtain keys?**" +#: ../system/data-privacy.rst:154 +msgid "Why are there so many deletion task entries, I didn't create them!" msgstr "" -#: ../system/integrations/pgp/index.rst:120 +#: ../system/data-privacy.rst:153 msgid "" -"You can create them yourself! There are some good tutorials on the web on " -"how to create them. Providing keys to Zammad is a prerequisite to use the " -"PGP feature." -msgstr "" - -#: ../system/integrations/pgp/index.rst:127 -msgid "**It says a passphrase is needed, but I haven't got one.**" +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:125 -msgid "" -"If the key is secured with a passphrase, you have to provide it for the " -"import in Zammad. It is possible that keys may have an empty passphrase. " -"However, this is *not* recommended." +#: ../system/integrations/checkmk/admin-panel-reference.rst:2 +msgid "Admin Panel Reference" msgstr "" -#: ../system/integrations/pgp/index.rst:132 -msgid "**How do my customers get my new key?**" +#: ../system/integrations/checkmk/admin-panel-reference.rst:None +msgid "Screenshot of Checkmk settings overview" msgstr "" -#: ../system/integrations/pgp/index.rst:130 +#: ../system/integrations/checkmk/admin-panel-reference.rst:12 msgid "" -"You have to provide your **public** key in advance. Your customer also has " -"to configure PGP in their email workflow and import your public key. The " -"other way round, you have to get the public key of your customer and have to " -"import it to Zammad." +"Which :doc:`group ` should Checkmk tickets be assigned " +"to as a default (*i.e.,* when none is specified)?" msgstr "" -#: ../system/integrations/slack.rst:2 -msgid "Slack" +#: ../system/integrations/checkmk/admin-panel-reference.rst:15 +msgid "(Applies to :ref:`API alerts ` only.)" msgstr "" -#: ../system/integrations/slack.rst:4 -msgid "**⚠️ Deprecation warning ⚠️**" +#: ../system/integrations/checkmk/admin-panel-reference.rst:21 +msgid "Auto close" msgstr "" -#: ../system/integrations/slack.rst:6 +#: ../system/integrations/checkmk/admin-panel-reference.rst:18 msgid "" -"Zammad 7 will no longer support this dedicated Slack integration. It is " -"recommended to switch to :doc:`pre-defined webhooks ` instead. Existing Slack integrations should " -"be migrated manually before this feature is dropped." +"Should Zammad automatically close tickets if a service has recovered on its " +"own?" msgstr "" -#: ../system/integrations/slack.rst:14 -msgid "" -"In order to use this feature, please add a new Slack app to your Workspace. " -"The App you need is called ``Incoming WebHooks`` ." +#: ../system/integrations/checkmk/admin-panel-reference.rst:21 +msgid "(Agents will receive notifications for such closures as appropriate.)" msgstr "" -#: ../system/integrations/slack.rst:18 -msgid "Why Do I Need This Feature?" +#: ../system/integrations/checkmk/admin-panel-reference.rst:30 +msgid "Auto-close state" msgstr "" -#: ../system/integrations/slack.rst:20 -msgid "" -"If you're already using Slack for your team communication, you'll love this " -"feature! Our Slack integration can push ticket notifications about the last " -"ticket article based on the following events:" +#: ../system/integrations/checkmk/admin-panel-reference.rst:24 +msgid "What ticket state should be applied when “auto-closing” a ticket?" msgstr "" -#: ../system/integrations/slack.rst:24 -msgid "on Ticket creation" +#: ../system/integrations/checkmk/admin-panel-reference.rst:26 +msgid "" +"You can choose from the seven built-in ticket states. If these states aren't " +"enough for you, you can :ref:`define a new ticket state ` for this purpose as well. This can be useful for tracking " +"tickets with :doc:`reports `, for example." msgstr "" -#: ../system/integrations/slack.rst:25 -msgid "on Ticket updates" +#: ../system/integrations/checkmk/admin-panel-reference.rst:35 +#: ../system/integrations/cti/includes/recent-logs.include.rst:2 +#: ../system/integrations/ldap/index.rst:74 +#: ../system/integrations/pgp/index.rst:106 +msgid "Recent Logs" msgstr "" -#: ../system/integrations/slack.rst:26 -msgid "on reached reminders" +#: ../system/integrations/checkmk/admin-panel-reference.rst:None +msgid "Screenshot of Checkmk \"Recent Logs\" section" msgstr "" -#: ../system/integrations/slack.rst:27 -msgid "a Ticket has escalated" +#: ../system/integrations/checkmk/admin-panel-reference.rst:41 +msgid "" +"If you're having trouble getting Zammad and Checkmk to play nicely together, " +"this section can help you troubleshoot." msgstr "" -#: ../system/integrations/slack.rst:28 -msgid "a Ticket is going to escalate" +#: ../system/integrations/checkmk/admin-panel-reference.rst:44 +msgid "" +"It contains a record of the fifty most recent transactions that Zammad knows " +"about, including each one's request/response details and return status." msgstr "" -#: ../system/integrations/slack.rst:30 -msgid "" -"Zammad will provide the Ticket title, a direct link to the Ticket, the event " -"type (creation, updated, escalation), the customer, time and the last " -"article that has triggered the notification." +#: ../system/integrations/checkmk/api-reference.rst:2 +msgid "API Reference" msgstr "" -#: ../system/integrations/slack.rst:34 +#: ../system/integrations/checkmk/api-reference.rst:4 msgid "" -"This will give you further options, as you can see e.g. escalating tickets " -"that are assigned to an agent that's e.g. absent. You can interact faster, " -"as you might see problems earlier (or even before the problem gets one)." +"For most users, :ref:`the sample scripts from the Setup Guide ` will do the job just fine. But if you want more fine-grained control" +"—for instance, to create high- and low-priority tickets for different types " +"of system events—then you'll have to customize the data those scripts send " +"to Zammad." msgstr "" -#: ../system/integrations/slack.rst:38 +#: ../system/integrations/checkmk/api-reference.rst:15 msgid "" -"If needed and wanted, you can even discuss directly about the topic before " -"sending an answer to the customer. Another possible use case would be a " -"agent monitoring new agents and their answers to tickets." +"This custom script will automatically set all tickets it creates to **high " +"priority** and **assign them to charlie@chrispresso.com**." msgstr "" -#: ../system/integrations/slack.rst:44 -msgid "Configure the Integration" +#: ../system/integrations/checkmk/api-reference.rst:32 +msgid "How Does it Work?" msgstr "" -#: ../system/integrations/slack.rst:46 +#: ../system/integrations/checkmk/api-reference.rst:34 msgid "" -"First of all, please go to your slack workspace - go to administration => " -"Manage Apps. If you don't have an app yet, you can simply add a new one - " -"just search for ``Incoming WebHooks`` and customize the app to your needs." +"There are two kinds of data you can pass to the API, both in the form of key-" +"value pairs:" msgstr "" -#: ../system/integrations/slack.rst:50 -msgid "" -"Choose (or create) the channel Zammad should post it's information to and " -"press on \"Add Incoming WebHooks integration\". If you're ready, copy the " -"provided WebHook URL and go to your Zammad installation." +#: ../system/integrations/checkmk/api-reference.rst:44 +msgid "Checkmk parameters" msgstr "" -#: ../system/integrations/slack.rst:56 +#: ../system/integrations/checkmk/api-reference.rst:38 msgid "" -"You need administrative rights on the Slack Workspace. The link to the app " -"directory is normally ``https://[workspace-name].slack.com/apps`` ." +"are required, and make up the **contents** of the resulting tickets/" +"articles. They also determine whether an event creates a new ticket or " +"updates/closes an existing one." msgstr "" -#: ../system/integrations/slack.rst:63 +#: ../system/integrations/checkmk/api-reference.rst:42 msgid "" -"To configure the slack integration, log in to Zammad and go to Integrations " -"(System) => Slack in the admin panel." +"These are the only values used in the sample scripts. **Use them as-is**; " +"technically, they can be customized, but it's hard to imagine a good reason " +"for it." msgstr "" -#: ../system/integrations/slack.rst:66 -msgid "" -"Here you can choose on what evens Zammad should post information about a " -"ticket to your Slack channel. Next you need to device what groups shall be " -"affected by this, as anybody with access to that specific Slack channel can " -"read at least parts of the ticket this might be a privacy issue, if you " -"select the wrong groups. The username is simply the name that Zammad uses as " -"display name inside the Slack chat. The channel defines the Slack channel " -"the information is being posted in. As last option, you can set a custom " -"icon for posting to slack." +#: ../system/integrations/checkmk/api-reference.rst:52 +msgid "Ticket attributes" msgstr "" -#: ../system/integrations/slack.rst:74 +#: ../system/integrations/checkmk/api-reference.rst:47 msgid "" -"When you're ready, just hit \"Submit\" and enable the integration. Zammad " -"will now post new ticket information based on the trigger you chose. Below " -"the options you have the recent log that shows the latest requests to Slack " -"for debugging if needed." +"are optional, and can be used to **adjust settings** on newly created " +"tickets (*e.g.,* set the owner, group, priority, or state)." msgstr "" -#: ../system/integrations/slack.rst:81 +#: ../system/integrations/checkmk/api-reference.rst:50 msgid "" -"If you leave the Icon URL empty, Zammad will use the Zammad logo instead. " -"The icon should be a square PNG file." +"If you want to customize your Checkmk alert script, do it with these. Simply " +"add an extra “form” option for each one (``-F \"key=value\"``) to your " +"script's ``curl`` command line, as in the example above." msgstr "" -#: ../system/integrations/slack.rst:90 -msgid "" -"The following figure shows how it will look if you choose to receive updates " -"on created and updated tickets. On every post Zammad sends to the Slack " -"channel, you can create new threads to discuss about the new article." +#: ../system/integrations/checkmk/api-reference.rst:54 +msgid "💡 **It's just an API endpoint!**" msgstr "" -#: ../system/integrations/slack.rst:96 +#: ../system/integrations/checkmk/api-reference.rst:56 msgid "" -"If you just want to keep track of soon escalating or already escalated " -"tickets, it will look the the following figure. Zammad changes the color in " -"front of the post so you can easily see the state of the ticket." +"When using Checkmk integration, messages need to be formatted in a certain " +"way, but that *doesn't mean the messages actually have to come from Checkmk*." msgstr "" -#: ../system/integrations/slack.rst:102 +#: ../system/integrations/checkmk/api-reference.rst:59 msgid "" -"If you change the state, Zammad will also put information on what state the " -"ticket gets and (if pending state) the date until it pends. You'll also " -"recognize the color codes in front of posts on slack, as they are exact the " -"same the ticket state colors you'll see in Zammad!" +"If you use another monitoring tool that's not officially supported by " +"Zammad, there's probably a way to make it work with your Checkmk callback " +"URL." msgstr "" -#: ../system/integrations/smime/index.rst:2 -msgid "S/MIME" +#: ../system/integrations/checkmk/api-reference.rst:63 +msgid "Checkmk Parameters" msgstr "" -#: ../system/integrations/smime/index.rst:11 +#: ../system/integrations/checkmk/api-reference.rst:65 msgid "" -"S/MIME is the most widely-supported method for secure email communication. " -"With S/MIME, you can exchange **signed** and **encrypted** messages with " -"others." +"When a notification is received, Zammad creates a new article containing the " +"details of the event that triggered it:" msgstr "" -#: ../system/integrations/smime/index.rst:15 -msgid "" -"is proof that a message hasn't been tampered with or sent by an impersonator." +#: ../system/integrations/checkmk/api-reference.rst:None +msgid "Checkmk article body" msgstr "" -#: ../system/integrations/smime/index.rst:17 +#: ../system/integrations/checkmk/api-reference.rst:72 msgid "" -"In other words, it guarantees a message's **integrity** and **authenticity**." +"These details come from the fields listed below, which correspond to " +"parameters provided by Checkmk (``$NOTIFY_*``)." msgstr "" -#: ../system/integrations/smime/index.rst:22 -msgid "In other words, it guarantees **privacy** and **data security**." +#: ../system/integrations/checkmk/api-reference.rst:75 +msgid "**Required fields are marked with an asterisk (\\*).**" msgstr "" -#: ../system/integrations/smime/index.rst:28 -msgid "Screencast demo of S/MIME features for both new tickets and replies" +#: ../system/integrations/checkmk/api-reference.rst:79 +msgid "event_id\\*" msgstr "" -#: ../system/integrations/smime/index.rst:28 +#: ../system/integrations/checkmk/api-reference.rst:78 msgid "" -"Once S/MIME has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " -"appear in the ticket composer." +"A unique ID for the system event. (``$NOTIFY_SERVICEPROBLEMID`` / " +"``$NOTIFY_HOSTPROBLEMID``)" msgstr "" -#: ../system/integrations/smime/index.rst:32 -msgid ":doc:`🔪 Prerequisites `" +#: ../system/integrations/checkmk/api-reference.rst:86 +msgid "host\\*" msgstr "" -#: ../system/integrations/smime/index.rst:31 +#: ../system/integrations/checkmk/api-reference.rst:82 msgid "" -"New to S/MIME? This section helps you to find certificate providers and " -"points out Limitations." +"The hostname of the system that the event originated from. " +"(``$NOTIFY_HOSTNAME``)" msgstr "" -#: ../system/integrations/smime/index.rst:35 -msgid ":doc:`📝 Manage Certificates `" +#: ../system/integrations/checkmk/api-reference.rst:85 +msgid "" +"Used to determine if a new event belongs to an existing ticket. Also used in " +"the subject line of the resulting article (“ is ”)." msgstr "" -#: ../system/integrations/smime/index.rst:35 -msgid "Add and download certificates; configure group default behaviors." +#: ../system/integrations/checkmk/api-reference.rst:96 +msgid "service" msgstr "" -#: ../system/integrations/smime/index.rst:38 -msgid ":doc:`😦 Troubleshooting `" +#: ../system/integrations/checkmk/api-reference.rst:89 +msgid "" +"The name of the service that the event originated from. " +"(``$NOTIFY_SERVICEDESC``)" msgstr "" -#: ../system/integrations/smime/index.rst:38 -msgid "Took a wrong turn? About recent logs and common issues." +#: ../system/integrations/checkmk/api-reference.rst:92 +msgid "Used to determine if a new event belongs to an existing ticket." msgstr "" -#: ../system/integrations/smime/index.rst:43 -msgid "" -"For more details on how S/MIME integration works on the agent side, see the :" -"user-docs:`user docs `." +#: ../system/integrations/checkmk/api-reference.rst:94 +#: ../system/integrations/checkmk/api-reference.rst:110 +msgid "Displayed as ``-`` when omitted." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:2 -msgid "Manage Certificates" +#: ../system/integrations/checkmk/api-reference.rst:104 +msgid "state\\*" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:4 +#: ../system/integrations/checkmk/api-reference.rst:99 msgid "" -"S/MIME is **disabled by default**. Enable it to start adding certificates." +"The current state of the service or host in question. " +"(``$NOTIFY_SERVICESTATE`` / ``$NOTIFY_HOSTSTATE``)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:10 -msgid "Dialogue to add new certificates or private keys" +#: ../system/integrations/checkmk/api-reference.rst:102 +msgid "" +"Used to detect when a ticket should be auto-closed (*i.e.,* on ``OK``/" +"``UP``). Also used in the subject line of the resulting article (“ is " +"”)." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:10 +#: ../system/integrations/checkmk/api-reference.rst:110 +msgid "text" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:107 msgid "" -"Manage certificates in the Admin Panel under **System > Integrations > S/" -"MIME**. Certificates may be pasted in as plain text or uploaded from a file." +"The output of the process that triggered the event. " +"(``$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:14 -msgid "Add Certificate Data" +#: ../system/integrations/checkmk/api-reference.rst:121 +msgid "" +"The Object Manager attribute panel displays built-in and custom\n" +"attribute names." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:36 -msgid "Add Certificate" +#: ../system/integrations/checkmk/api-reference.rst:121 +msgid "Find a complete list of ticket attributes in the Object Manager." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:17 +#: ../system/integrations/checkmk/api-reference.rst:123 msgid "" -"Import public-key certificates for both your own organization and your " -"contacts." +"Ticket attributes are entirely optional, and can be used to customize the " +"tickets that Checkmk creates. (Note that these attributes will be ignored if " +"a new event belongs to an existing ticket.)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:19 +#: ../system/integrations/checkmk/api-reference.rst:128 msgid "" -"You can also add a bunch of certificates in one go by providing a single " -"file with all relevant certificates." +"Why would you want to do this? Maybe you have only one IT guy, and all " +"system monitoring issues should be automatically assigned to him. Or, maybe " +"you're creating multiple notification rules so that database outages take " +"higher priority than disk space warnings." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:22 -msgid "🕵️ **ALWAYS verify certificates in-person or over the phone!**" +#: ../system/integrations/checkmk/api-reference.rst:135 +msgid "In most cases, you'll probably want to set one of the following:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:24 -msgid "" -"The whole point of signatures is to alert you when someone is trying to " -"pretend to be someone they're not. Never accept a certificate from someone " -"online without verifying it first." +#: ../system/integrations/checkmk/api-reference.rst:137 +msgid "group" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:28 -msgid "📇 **What about trusted certificate authorities?**" +#: ../system/integrations/checkmk/api-reference.rst:139 +msgid "state" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:30 -msgid "" -"In some cases (e.g. when dealing with large enterprises), you may be given a " -"certificate for an entire CA, rather than a single contact. Add it here to " -"trust *all* certificates issued by that CA." +#: ../system/integrations/checkmk/api-reference.rst:140 +msgid "priority" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:35 +#: ../system/integrations/checkmk/api-reference.rst:142 msgid "" -"Commercial CAs can usually be verified online. Zammad does not include a " -"list of built-in, trusted CAs." +"but in practice, you can set almost any attribute, including :doc:`custom " +"ones you created through the Object Manager `." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:57 -msgid "Add Private Key" +#: ../system/integrations/checkmk/api-reference.rst:145 +msgid "Please note that the following attributes are **not customizable**:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:39 -msgid "" -"Once you've added a public-key certificate, you can import its matching " -"private key." +#: ../system/integrations/checkmk/api-reference.rst:147 +msgid "title" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:42 -msgid "" -"Private keys are for **your own organization only**; never ask your contacts " -"for their private keys." +#: ../system/integrations/checkmk/api-reference.rst:148 +msgid "id" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:0 -msgid "" -"S/MIME integration showing configured certificates and possible issues with " -"Logging" +#: ../system/integrations/checkmk/api-reference.rst:149 +msgid "ticket number" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:50 -msgid "" -"A note is displayed on certificates with a matching private key (see line 2)." +#: ../system/integrations/checkmk/api-reference.rst:151 +msgid "created_by_id" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:52 -msgid "📤 **Certificates and private keys must be uploaded separately.**" +#: ../system/integrations/checkmk/api-reference.rst:152 +msgid "updated_by_id" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:54 -msgid "" -"If your certificate and private key are bundled together in the same file or " -"PEM block, import it twice (once using each button)." -msgstr "" - -#: ../system/integrations/smime/manage-certificates.rst:57 -msgid "Please note that bulk imports of private keys are not possible." +#: ../system/integrations/checkmk/api-reference.rst:155 +msgid "Which Values Can Be Set?" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:60 -msgid "Download Certificate Data" +#: ../system/integrations/checkmk/api-reference.rst:157 +msgid "😵 **Invalid values → unpredictable behavior**" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:62 +#: ../system/integrations/checkmk/api-reference.rst:159 msgid "" -"You can download the earlier provided certificates and private keys at any " -"time from your Zammad instance." +"If you provide a value that Zammad doesn't understand (*e.g.,* ``-F " +"\"priority=high\"``), it's not always clear what will happen. In some cases, " +"a ticket will be created with the default values instead - but in others, it " +"may not be created at all!" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:65 -msgid "" -"Please note that passphrase-protected private keys stay protected and when " -"you download them, you have to know the passphrase to use them after " -"downloading." +#: ../system/integrations/checkmk/api-reference.rst:164 +msgid "So what values does Zammad understand, then? Well, it depends..." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:73 -msgid "Dialogue to download certificates or private keys" +#: ../system/integrations/checkmk/api-reference.rst:168 +msgid "Use an email address or username:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:73 -msgid "Download stored certificates and their keys" +#: ../system/integrations/checkmk/api-reference.rst:190 +msgid "group & priority" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:78 -msgid "" -"The ticket composer will set all outgoing messages to **signed and " -"encrypted** by default (assuming the required certificates exist)." +#: ../system/integrations/checkmk/api-reference.rst:175 +msgid "Refer to the dropdown menus in the ticket pane:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:82 -msgid "These defaults can be modified on a per-group basis:" +#: ../system/integrations/checkmk/api-reference.rst:0 +msgid "See possible values for certain attributes in the ticket pane." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:None -msgid "Zammad allowing to choose the default behavior on per group basis" +#: ../system/integrations/checkmk/api-reference.rst:187 +msgid "🙅 **Ticket state CANNOT be set this way!**" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:89 +#: ../system/integrations/checkmk/api-reference.rst:189 msgid "" -"Of course, agents can always manually change these settings on each email " -"they send out." +"Why? Because ``-F \"state=...\"`` is already used :ref:`as a Checkmk " +"parameter `." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:4 -msgid "A certificate *and* private key for your own organization" +#: ../system/integrations/checkmk/api-reference.rst:222 +msgid "Everything Else" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:6 +#: ../system/integrations/checkmk/api-reference.rst:193 msgid "" -"(Use this to ✒️ **sign outgoing messages** and 🔓 **decrypt incoming " -"messages**.)" +"To set any other attributes, it helps to know your way around the :docs:" +"`rails console `. Valid values are those that you can " +"set with a string:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:9 -msgid "" -"Certificates belonging your contacts, or their issuing certificate authority " -"(CA)" +#: ../system/integrations/checkmk/api-reference.rst:218 +msgid "These values can then be passed directly to the API:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:11 -msgid "" -"(Use these to ✅ **verify incoming message signatures** and 🔒 **encrypt " -"outgoing messages**.)" +#: ../system/integrations/checkmk/index.rst:16 +msgid "How does it work?" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:14 -msgid "🙋 **I'm new to S/MIME. Where can I get a certificate?**" +#: ../system/integrations/checkmk/index.rst:2 +msgid "Checkmk" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:16 +#: ../system/integrations/checkmk/index.rst:4 msgid "" -"The easiest way to get certificates is to buy an annual subscription through " -"a commercial CA, such as:" +"`Checkmk `_ is a powerful IT monitoring tool that can " +"send real-time status alerts to Zammad via email or REST API. Set these " +"alerts up in Checkmk, and Zammad will automatically create, update, and " +"close tickets based on the health of your system:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:19 -msgid "" -"`Sectigo (formerly Comodo) `_" +#: ../system/integrations/checkmk/index.rst:14 +msgid "Screenshot of ticket created by Checkmk notifications" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:20 -msgid "`Secorio `_" +#: ../system/integrations/checkmk/index.rst:14 +msgid "Multiple alerts, same ticket." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:21 -msgid "`GlobalSign `_" +#: ../system/integrations/checkmk/setup-guide.rst:2 +msgid "Setup Guide" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:23 -msgid "(Zammad is not affiliated with these CAs in any way.)" +#: ../system/integrations/checkmk/setup-guide.rst:4 +msgid "" +"Whenever the Checkmk integration is enabled, Zammad listens for messages on " +"its API and over email. As long as those messages follow the required " +"format, Zammad will create new tickets (or find and update existing ones) " +"based on the message contents." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:25 +#: ../system/integrations/checkmk/setup-guide.rst:10 msgid "" -"You can also generate your own self-signed certificates, but the process is " -"complicated and usually 🙅 **involves extra work for your contacts**." +"That means that “setting up Checkmk integration” is simply a matter of " +"**adding configuration to your Checkmk site**: telling it when to send these " +"messages and what to say. To do that, you'll need to create a new " +"**notification rule** (see `Checkmk's official docs `_ for help with that)." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:29 +#: ../system/integrations/checkmk/setup-guide.rst:17 msgid "" -"Bear in mind that 🤝 **S/MIME only works if the other party is using it, too." -"**" +"As part of this new rule, you'll have to choose a **notification method** " +"(*i.e.,* a script to execute whenever the rule is triggered). This script " +"will be written by you (samples below), and contain the logic for sending " +"API/email messages to Zammad:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:32 -msgid "Certificate and Private Key Checks on Upload" +#: ../system/integrations/checkmk/setup-guide.rst:26 +msgid "Checkmk \"New Rule\" dialog" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:34 +#: ../system/integrations/checkmk/setup-guide.rst:26 msgid "" -"The certificate and public key validation is based on the ``X509v3`` " -"extensions." +"Find your custom scripts in the Checkmk WATO under **Notifications > New " +"Rule > Notification Method**." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:49 -msgid "Uploading a *client certificate*?" +#: ../system/integrations/checkmk/setup-guide.rst:29 +msgid "" +"Once you're done setting up your new rule, you're all set! New tickets " +"should start coming in and auto-updating any time your rule is triggered." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:41 -msgid "The following attributes are required then:" +#: ../system/integrations/checkmk/setup-guide.rst:33 +msgid "" +"(If you need help troubleshooting, be sure to check the :ref:`checkmk-recent-" +"logs`.)" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:39 -msgid "Subject Alternative Name (at least one email address has to be present)" +#: ../system/integrations/checkmk/setup-guide.rst:38 +msgid "API Alerts" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:40 -msgid "Key Usage (``Digital Signature`` and/or ``Key Encipherment``)" +#: ../system/integrations/checkmk/setup-guide.rst:40 +msgid "" +"To add these scripts in the Checkmk WATO, copy them into your Checkmk " +"installation directory and make them executable. (Be sure to replace the " +"``zammad.example.com`` callback URL with the one found in your admin panel.)" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:41 -msgid "Public key algorithm (either ``RSA`` or ``EC``)" +#: ../system/integrations/checkmk/setup-guide.rst:60 +msgid "Service notification" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:43 +#: ../system/integrations/checkmk/setup-guide.rst:46 msgid "" -"The Extended Key Usage attribute is optional. If the certificate provides " -"the named attribute, than it must contain the value ``E-mail Protection``." +"For updates on the status of the software running on your server (*e.g.,* " +"postgres)." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:46 -msgid "" -"Please note that any usable email adress has to be prefixed with ``email:`` " -"or ``rfc822:``." +#: ../system/integrations/checkmk/setup-guide.rst:75 +msgid "Host notification" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:49 -msgid "The named public key algorithms are mandatory for private keys as well." +#: ../system/integrations/checkmk/setup-guide.rst:63 +msgid "For updates on the status of the server itself." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:54 -msgid "Uploading a *CA certificate*?" +#: ../system/integrations/checkmk/setup-guide.rst:77 +msgid "🤔 **What's with all the env vars?**" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:52 +#: ../system/integrations/checkmk/setup-guide.rst:79 msgid "" -"In the case of an uploaded CA certificate, providing the value ``CA:TRUE`` " -"in the attribute *Basic Contstraints*, the previously mentioned attributes " -"are not verified." +"Whenever Checkmk runs these scripts, it needs to provide some information " +"about the event that triggered the notification. This information is passed " +"in the form of these ``$NOTIFY_*`` environment variables." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:56 +#: ../system/integrations/checkmk/setup-guide.rst:85 msgid "" -"In general, the usage of any expired (``Not After``) or not yet valid (``Not " -"Before``) certificate is denied for outgoing emails." +"You can specify additional parameters to pass to the script when you're " +"setting up your notification rule, but the ones you see here are all " +"provided by default." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:59 -msgid "Example certificate:" +#: ../system/integrations/checkmk/setup-guide.rst:90 +msgid "Email Alerts" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:85 +#: ../system/integrations/checkmk/setup-guide.rst:94 msgid "" -"Please note that Zammad will distrust senders by default. This means that " -"you're always required to provide certificate data, no matter if for signing " -"or encrypting." +"🐞 **There are known bugs** in Zammad's processing of email from Checkmk. " +"This section will be completed once they have been resolved. (Learn more at " +"GitHub issues `#2377 `_ & " +"`#2180 `_.)" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:89 -msgid "This is by design and can't be adjusted." +#: ../system/integrations/checkmk/setup-guide.rst:100 +msgid "In the meantime, we encourage you to set up API alerts instead." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:4 -msgid "" -"All of the system's latest S/MIME activity is displayed in the **Recent " -"Logs** section." +#: ../system/integrations/clearbit.rst:2 +msgid "Clearbit" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:11 -msgid "Sample entries of in- and outgoing S/MIME related emails." +#: ../system/integrations/clearbit.rst:4 +msgid "" +"With our Clearbit integration, you can easily enrich the information " +"provided by Zammad. If the customers or agents email address is known to " +"Clearbit, it will share all information it has regarding the user with " +"Zammad. Those information can include the following:" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:11 -msgid "" -"Logs report the status and details of all mail, both incoming and outgoing, " -"that used signing/verification or encryption/decryption." +#: ../system/integrations/clearbit.rst:9 +msgid "Avatar" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:14 -msgid "" -"This log does **not** include email sent by :doc:`triggers ` or the :doc:`scheduler `. For those, check your " -"``production.log``." +#: ../system/integrations/clearbit.rst:10 +msgid "Address information" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:20 -msgid "Common Issues" +#: ../system/integrations/clearbit.rst:11 +msgid "Website information" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:30 -msgid "I received a signed/encrypted email before I set up S/MIME integration" +#: ../system/integrations/clearbit.rst:12 +msgid "A BIO (as Note by default)" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:23 +#: ../system/integrations/clearbit.rst:14 msgid "" -"No problem. Once S/MIME has been enabled and the appropriate certificates " -"have been added, agents will be prompted to retry verification/decryption on " -"matching emails." +"If needed, you can add further custom objects and add mappings to them, so " +"the Clearbit information can be filled within the database. In general you " +"can get any information from Clearbit, as long as you have a mapping to an " +"Zammad object." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:0 -msgid "Screenshot of user prompt to retry decryption" +#: ../system/integrations/clearbit.rst:21 +msgid "" +"Clearbit does have a mapping of fields like LDAP and Exchange have, but does " +"not \"win\" against Zammad information. This means that if you have e.g. the " +"last name field filled in already and Clearbit has other information on " +"that, it will not be updated." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:38 -msgid "The 🔒 **Encrypt** button is disabled" +#: ../system/integrations/clearbit.rst:26 +msgid "" +"However: If let's say the last name has been set by Clearbit and Zammad " +"notices that the last name on the Clearbit source has changed, Zammad will " +"also update this value." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:33 -msgid "Have you added the recipient's certificate?" +#: ../system/integrations/clearbit.rst:33 +msgid "" +"The configuration of Clearbit is really easy and done fast! Just login to " +"your Clearbit-Account, go to \"API\" and copy the secret-API-Key." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:34 -msgid "Are you sure the recipient's certificate is valid?" +#: ../system/integrations/clearbit.rst:38 +msgid "" +"Now change to your Zammad instance, go to Integrations (System) -> Clearbit " +"in the admin panel. Paste your API-Key into the API-Key-Field and decide if " +"Zammad should create unknown Organizations automatically, if the user does " +"not have one yet (and Clearbit knows it). The shared option decides if the " +"new organizations Zammad creates with Clearbit should be shared ones." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:35 -msgid "Have you checked your ``production.log`` for more details?" +#: ../system/integrations/clearbit.rst:47 +msgid "" +"If you're unsure what option to choose, better stick with \"no\". You can " +"also learn more about :doc:`/manage/organizations/index`." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:37 +#: ../system/integrations/clearbit.rst:52 msgid "" -"If encryption doesn't work in the composer, it won't work in :doc:`triggers " -"` or the :doc:`scheduler ` either!" +"The Mapping option works similar to the mapping within the Exchange and LDAP " +"sync. You can add further mappings for e.g. custom fields if you need more " +"information that Clearbit can provide." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:42 -msgid "The ✅ **Sign** button is disabled" +#: ../system/integrations/clearbit.rst:58 +msgid "" +"If you want to add more Clearbit fields and want to learn more about " +"available fields on their API, you can take a look at their `API " +"documentation `_." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:41 +#: ../system/integrations/clearbit.rst:62 msgid "" -"Have you added **both the certificate and private key** for your " -"organization?" +"If you're happy with the above chosen Settings and your mapping, just save " +"the changes and enable Clearbit integration. Zammad will now start polling " +"the Clearbit API as users contact you." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:42 +#: ../system/integrations/clearbit.rst:68 msgid "" -"Does the email address on the certificate match the email address of the " -"agent/group composing the email?" +"Zammad does not synchronize with Clearbit on a regular basis, but on demand " +"if needed. This saves API calls." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:45 -msgid "Error: “Fingerprint already taken”" +#: ../system/integrations/clearbit.rst:73 +msgid "" +"Below the Settings and Mappings, you'll find our Integration log. You can " +"see what requests Zammad sent to Clearbit and also the APIs Response." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:45 -msgid "Are you sure you haven't added this certificate already?" +#: ../system/integrations/clearbit.rst:78 +msgid "" +"By the way, you can also view the API log on the Clearbit website - the " +"information seen is basically the same." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:48 -msgid "Error: “❌ invalid byte sequence in UTF-8”" +#: ../system/integrations/clearbit.rst:84 +msgid "Example When Adding a User" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:48 -msgid "Please ensure to provide PEM formatted certificate and keys." +#: ../system/integrations/clearbit.rst:86 +msgid "" +"To show you how fast information is added, we added a small Screencast " +"below. This shows the creation of the User Alex from Clearbit. As we already " +"set the last name of Alex to \"X\", Zammad did not update it. What Zammad " +"did was to add further information it received from Clearbit." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:49 -msgid "Did you check if the provided file is a valid certificate or key?" +#: ../system/integrations/cti/generic.rst:2 +msgid "CTI (generic)" msgstr "" -#: ../system/integrations/zabbix.rst:2 -msgid "Zabbix Integration" +#: ../system/integrations/cti/includes/introduction.include.rst:1 +msgid "" +"This integration enables Zammad to provide a caller log to your agents. With " +"this your agents can greet your customers by their name and are supported by " +"Zammad with automatically opening a new ticket dialog or the user profile." msgstr "" -#: ../system/integrations/zabbix.rst:5 +#: ../system/integrations/cti/includes/introduction.include.rst:6 msgid "" -"This guide describes how to integrate your Zabbix 5.4 installation with " -"Zammad using the Zabbix webhook feature. This guide will provide " -"instructions on setting up a media type, a user and an action in Zabbix." +"Click the toggle next to the heading to activate or deactivate this " +"integration." msgstr "" -#: ../system/integrations/zabbix.rst:12 -msgid "Zammad with enabled HTTP Token Authentication" +#: ../system/integrations/cti/includes/introduction.include.rst:9 +msgid "" +"If you want to learn more on how your agents can use this function, please " +"refer the :user-docs:`user documentation `." msgstr "" -#: ../system/integrations/zabbix.rst:13 -msgid "Zabbix version 5.4 or higher" +#: ../system/integrations/cti/includes/introduction.include.rst:14 +msgid "" +"Automatically opening new ticket dialogues or user profiles requires agent " +"to extension mapping - see more below." msgstr "" -#: ../system/integrations/zabbix.rst:16 -msgid "Setting up a Zammad" +#: ../system/integrations/cti/includes/introduction.include.rst:20 +msgid "Please note the following limitations to reduce confusion later on:" msgstr "" -#: ../system/integrations/zabbix.rst:18 -msgid "Enable **API Token Access** in Settings > System > API." +#: ../system/integrations/cti/includes/introduction.include.rst:22 +msgid "CTI integrations provide caller log functions only." msgstr "" -#: ../system/integrations/zabbix.rst:20 +#: ../system/integrations/cti/includes/introduction.include.rst:23 msgid "" -"Create a **new user** for a Zabbix alerter with an **email address** and " -"create a personal user token with **ticket.agent** permissions." +"This integration does not provide any VoIP functionalities; you can't make " +"phone calls from within Zammad." msgstr "" -#: ../system/integrations/zabbix.rst:24 -msgid "Zabbix Webhook Configuration" +#: ../system/integrations/cti/includes/introduction.include.rst:25 +msgid "" +"If your browser supports ``tel``-URLs, you can click on phone numbers for " +"automatic dialing. This requires additional software / configuration on your " +"agent's computers." msgstr "" -#: ../system/integrations/zabbix.rst:27 -msgid "Create a Global Macro" +#: ../system/integrations/cti/generic.rst:9 +#: ../system/integrations/cti/placetel.rst:14 +#: ../system/integrations/cti/sipgate.rst:14 +msgid "Please provide the following requirements:" msgstr "" -#: ../system/integrations/zabbix.rst:29 +#: ../system/integrations/cti/generic.rst:11 msgid "" -"Before setting up the **Webhook**, you need to setup the global macro " -"**{$ZABBIX.URL}**, which must contain the **URL** to the **Zabbix frontend**." +"A telephone system that supports webhooks (outbound) (best option are those " +"that allow customizing the calls)." msgstr "" -#: ../system/integrations/zabbix.rst:33 -msgid "" -"In the **Administration** > **Media types** section, import the `Template`_." +#: ../system/integrations/cti/generic.rst:13 +msgid "A unique Call-ID during the call session." msgstr "" -#: ../system/integrations/zabbix.rst:38 -msgid "Open the added **Zammad** media type and set:" +#: ../system/integrations/cti/generic.rst:14 +msgid "Call event data (both numbers and direction)." msgstr "" -#: ../system/integrations/zabbix.rst:40 -msgid "**zammad\\_access\\_token** to the your **Personal User Token**" +#: ../system/integrations/cti/generic.rst:15 +msgid "Your Zammad instance must be reachable for your telephony system." msgstr "" -#: ../system/integrations/zabbix.rst:41 +#: ../system/integrations/cti/generic.rst:17 msgid "" -"**zammad\\_url** to the **frontend URL** of your **Zammad** installation" +"If you want to learn more on what kind of requests are supported by Zammad " +"and what it expects, please consult our :docs:`CTI-API documentation `." msgstr "" -#: ../system/integrations/zabbix.rst:43 -msgid "**zammad\\_customer** to your **Zammad user email**." +#: ../system/integrations/cti/generic.rst:22 +#: ../system/integrations/cti/placetel.rst:27 +#: ../system/integrations/cti/sipgate.rst:30 +msgid "Available Settings" msgstr "" -#: ../system/integrations/zabbix.rst:44 -msgid "" -"**zammad\\_enable\\_tags** to **true** or **false** to enable or disable " -"trigger tags. **Important**: if you enable tag support, each tag is set with " -"a separate request." +#: ../system/integrations/cti/generic.rst:29 +#: ../system/integrations/cti/placetel.rst:41 +#: ../system/integrations/cti/sipgate.rst:40 +msgid "Endpoint Settings" msgstr "" -#: ../system/integrations/zabbix.rst:48 +#: ../system/integrations/cti/generic.rst:25 msgid "" -"If you want to prioritize issues according to **severity** values in Zabbix, " -"you can define mapping parameters:" -msgstr "" - -#: ../system/integrations/zabbix.rst:51 -msgid "**severity\\_**: Zammad priority ID" -msgstr "" - -#: ../system/integrations/zabbix.rst:53 -msgid "Click the **Update** button to save the **Webhook** settings." +"Zammad will list your generic CTI endpoint here. It contains a unique token " +"so ensure to keep this URL save." msgstr "" -#: ../system/integrations/zabbix.rst:55 +#: ../system/integrations/cti/generic.rst:28 msgid "" -"To receive notifications in **Zammad**, you need to create a **Zabbix user** " -"and add **Media** with the **Zammad** type." +"You'll need this endpoint for your PBX to talk to Zammad, see :docs:`CTI-API " +"documentation `." msgstr "" -#: ../system/integrations/zabbix.rst:58 +#: ../system/integrations/cti/includes/important-dont-forget-saving.include.rst:3 msgid "" -"For **Send to**: enter any text, as this value is not used, but is required." +"All following options **do not save automatically**. Always use the Save " +"button on the lower end of the integration page!" msgstr "" -#: ../system/integrations/zabbix.rst:61 -msgid "" -"For more information, use the `Zabbix documentation `_." +#: ../system/integrations/cti/generic.rst:43 +#: ../system/integrations/cti/placetel.rst:49 +#: ../system/integrations/cti/sipgate.rst:52 +msgid "Call Settings" msgstr "" -#: ../system/maintenance.rst:2 -msgid "Maintenance" +#: ../system/integrations/cti/generic.rst:39 +#: ../system/integrations/cti/placetel.rst:49 +#: ../system/integrations/cti/sipgate.rst:37 +#: ../system/integrations/cti/sipgate.rst:50 +msgid "Inbound" msgstr "" -#: ../system/maintenance.rst:4 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:1 msgid "" -"Zammad comes with a maintenance mode that you can use for e.g. updating the " -"instance or changing settings while restricting availability and functions." +"This option allows you to block specific incoming caller IDs. It allows you " +"to temporarily reject e.g. spam callers without having to contact providers " +"or PBX administrators." msgstr "" -#: ../system/maintenance.rst:13 -msgid "Mode" +#: ../system/integrations/cti/includes/inbound-calls.include.rst:11 +msgid "Caller ID to block" msgstr "" -#: ../system/maintenance.rst:8 -msgid "The mode setting allows you to enable or disable the maintenance mode." +#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 +msgid "Provide caller IDs to block in ``E.164`` format." msgstr "" -#: ../system/maintenance.rst:10 -msgid "Defaults to *off*." +#: ../system/integrations/cti/includes/inbound-calls.include.rst:8 +msgid "" +"Your telephony system has to support this function. Zammad will send a " +"``reject`` response which will cause your telephony system to hang up the " +"call. To callers this usually will feel like the line is busy." msgstr "" -#: ../system/maintenance.rst:12 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:14 msgid "" -"The maintenance mode will restrict access to administrative roles only. This " -"means agents and customers are logged off." -msgstr "" - -#: ../system/maintenance.rst:23 -msgid "@Login" -msgstr "" - -#: ../system/maintenance.rst:16 -msgid "" -"This setting allows you to provide a login message within a green banner " -"above the login screen. Click into the green banner in the settings page to " -"adjust your message. To activate the message, activate the *@Login* setting." -msgstr "" - -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing the default login message within the\n" -"settings page" -msgstr "" - -#: ../system/maintenance.rst:26 -msgid "" -"Send an informative message to **all active sessions**. This comes handy to " -"inform your agents e.g. about mayor outages or to force reloads after " -"configuration changes." -msgstr "" - -#: ../system/maintenance.rst:31 -msgid "This is the messages title (slightly bigger than the normal message)." -msgstr "" - -#: ../system/maintenance.rst:34 -msgid "The text you want to provide to your logged in sessions." -msgstr "" - -#: ../system/maintenance.rst:39 -msgid "Reload application" -msgstr "" - -#: ../system/maintenance.rst:37 -msgid "" -"Selecting this option will change the message acceptance button from *Close* " -"(with nothing happening) to *Continue session*, which forces the application " -"to reload." -msgstr "" - -#: ../system/maintenance.rst:43 -msgid "" -"If you have customers that are logged in to Zammad, they'll also be notified " -"if they're active in that moment." -msgstr "" - -#: ../system/maintenance.rst:48 -msgid "Example without reload application" +"Provide a meaningful note for your fellow administrators to remind yourself " +"why you've chosen to block the number." msgstr "" -#: ../system/maintenance.rst:52 -msgid "" -"Message setting within Zammad's admin settings without ticket reload " -"application setting." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:17 +#: ../system/integrations/cti/sipgate.rst:40 +msgid "Outbound" msgstr "" -#: ../system/maintenance.rst:0 +#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:1 msgid "" -"Screenshot showing the send message settings without ticket\n" -"reload application set" +"In many cases you may want to use a different caller ID depending on the " +"destination you're calling. This may apply due to specific connection rates " +"to other countries or because you want your customer to feel you're calling " +"from the same country." msgstr "" -#: ../system/maintenance.rst:61 ../system/maintenance.rst:85 -msgid "" -"The modal all other active sessions will see upon pressing *Send to clients*." +#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:6 +msgid "This option expects ``E.164`` number formats." msgstr "" -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing modal caused by maintenance's message\n" -"without reload application ticket" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 +msgid "Destination caller ID" msgstr "" -#: ../system/maintenance.rst:72 -msgid "Example with reload application" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:5 +msgid "The caller ID or number you're trying to call." msgstr "" -#: ../system/maintenance.rst:76 -msgid "" -"Message setting within Zammad's admin settings with ticket reload " -"application setting." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:7 +msgid "You can use wildcards for e.g. country specific outbound numbers like:" msgstr "" -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing the send message settings with ticket\n" -"reload application set" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:9 +msgid "``49*`` for Germany" msgstr "" -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing modal caused by maintenance's message\n" -"with reload application ticket" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:10 +msgid "``4930*`` for Berlin / Germany landlines" msgstr "" -#: ../system/monitoring.rst:2 -msgid "Monitoring" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 +msgid "``33*`` for France" msgstr "" -#: ../system/monitoring.rst:4 -msgid "" -"This function is only available in self hosted instances. If you use Zammad " -"in our cloud, we are monitoring the system on our own and take steps to fix " -"potential problems directly." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:15 +msgid "Set Outbound caller ID" msgstr "" -#: ../system/monitoring.rst:11 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:14 msgid "" -"On the monitoring page, you can see the current health state of Zammad under " -"\"*Current Status*\" at the bottom. This can be useful if you want to have a " -"look if everything is up and running. As an example, you could have a look " -"in the monitoring when you assume that some emails aren't processed from " -"Zammad." +"The outbound caller ID to set (the number your customer sees on his display) " +"in ``E.164`` number format." msgstr "" -#: ../system/monitoring.rst:17 -msgid "**Can't receive an email and the monitoring response is \"healthy\"?**" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 +msgid "Provide a short description for fellow administrators." msgstr "" -#: ../system/monitoring.rst:19 +#: ../system/integrations/cti/includes/generic-cti-support-note.includes.rst:3 msgid "" -"Zammad will just inform you about unprocessable emails. This is not the case " -"for oversized emails. You can adjust the maximum email size in :doc:`../" -"channels/email/settings`." +"This option requires your PBX to send a specific request to Zammad *before " +"dialing*. Please consult the :docs:`CTI API ` in case " +"you're not sure." msgstr "" -#: ../system/monitoring.rst:24 -msgid "Monitoring API" +#: ../system/integrations/cti/generic.rst:52 +#: ../system/integrations/cti/placetel.rst:54 +#: ../system/integrations/cti/sipgate.rst:59 +msgid "Other Settings" msgstr "" -#: ../system/monitoring.rst:26 +#: ../system/integrations/cti/includes/other-settings-intro.include.rst:1 msgid "" -"Beside the indication in the monitoring page, you can also use an external " -"monitoring tool to monitor Zammad's health. To request the health of Zammad, " -"you need to provide the API key (token) to the external monitoring tool. You " -"can copy the token from the \"*Current Token*\" field as well as the whole " -"API endpoint of your system (\"*Health Check*\" field), in which the API " -"token is already included." +"Below you can find all available additional settings for this CTI " +"integration. For your overview we're sorting them by appearance and " +"reference their description first." msgstr "" -#: ../system/monitoring.rst:37 -msgid "Screenshot showing Current Token and Health Check" +#: ../system/integrations/cti/includes/default-caller-id.include.rst:2 +#: ../system/integrations/cti/includes/default-caller-id.include.rst:1 +msgid "Default caller ID for outbound calls" msgstr "" -#: ../system/monitoring.rst:37 -msgid "Screenshot showing Token and Health Check" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:16 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:15 +msgid "Shown records in caller log" msgstr "" -#: ../system/monitoring.rst:39 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:2 msgid "" -"In addition to that, you can reset the auto-generated token to make sure " -"that already configured monitoring systems won't work anymore. So, please " -"use this \"*Reset*\" button only if you know what you do!" -msgstr "" - -#: ../system/monitoring.rst:44 -msgid "Example Output" -msgstr "" - -#: ../system/monitoring.rst:0 -msgid "No issues found" -msgstr "" - -#: ../system/monitoring.rst:48 ../system/monitoring.rst:60 -msgid "**Indicator in Zammad**:" -msgstr "" - -#: ../system/monitoring.rst:0 -msgid "Screenshot showing monitoring with no issues" -msgstr "" - -#: ../system/monitoring.rst:54 ../system/monitoring.rst:66 -msgid "**API response**::" -msgstr "" - -#: ../system/monitoring.rst:0 -msgid "Issues were found" -msgstr "" - -#: ../system/monitoring.rst:0 -msgid "Screenshot showing monitoring with issues" -msgstr "" - -#: ../system/objects.rst:2 -msgid "Objects" +"Allows you to set the number of shown caller log entries for all users. You " +"can choose from the following values:" msgstr "" -#: ../system/objects.rst:4 -msgid "" -"In Zammad you can add your own fields to tickets, users, organizations and " -"even groups (these are called \"objects\"). This can be useful if you need " -"to add further information to a ticket or any other object in Zammad and the " -"information doesn't fit in any existing field." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:5 +msgid "60 (default)" msgstr "" -#: ../system/objects.rst:11 -msgid "" -"Try to avoid deleting attributes (and disable them instead) as Zammad might " -"run into unexpected conditions if they are referenced somewhere." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:6 +msgid "120" msgstr "" -#: ../system/objects.rst:16 -msgid "" -"Here's an overview of object attributes. On the upper right you can add new " -"attributes. By default, there will be no custom fields - standard attributes " -"will be grayed out, you can't delete or change those. You can edit custom " -"attributes (they are displayed in black font and have a trash bin on the " -"right side) just by clicking on them." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:7 +msgid "180" msgstr "" -#: ../system/objects.rst:24 -msgid "" -"Attributes you add to Zammad, no matter if they have default values or not, " -"will not update existing information. This means a new ticket field " -"technically will be empty unless you populate it." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:8 +msgid "240" msgstr "" -#: ../system/objects.rst:28 -msgid "" -"Especially in ticket scope this also means that newly added attributes will " -"be indicated as \"changed\" to agents that view the ticket. This may " -"interfere with Zammad's tabs behavior." +#: ../system/integrations/cti/includes/records-caller-log.include.rst:9 +msgid "300" msgstr "" -#: ../system/objects.rst:40 -msgid "Ordering Attributes" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:11 +msgid "**🥵 Potential performance issue**" msgstr "" -#: ../system/objects.rst:42 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:13 msgid "" -"Since Zammad introduced :doc:`/system/core-workflows` the need to have a " -"custom positioning for attributes has become more important than ever." +"Setting this setting higher than 60 may cause serious performance issues on " +"very busy instances. Keep in mind that this setting causes Zammad to poll " +"and send up to 300 records to *all active agent sessions* in very short time " +"periods." msgstr "" -#: ../system/objects.rst:45 -msgid "" -"To adjust the position of such an attribute, simply click on the attribute " -"entry in question, scroll down and adjust the position number. Please note " -"that you cannot change the positioning of default attributes." +#: ../system/integrations/cti/generic.rst:73 +msgid "Caller Log Filter" msgstr "" -#: ../system/objects.rst:49 +#: ../system/integrations/cti/generic.rst:55 msgid "" -"In case two attributes have the same position value, Zammad will sort " -"alphabetically by name automatically." +"This function allows you to provide call information based on e.g. queues " +"only to agents that really need the information." msgstr "" -#: ../system/objects.rst:None +#: ../system/integrations/cti/generic.rst:58 msgid "" -"Screenshot showing custom attribute entries ordered in between default ones" +"Why? If you have a team for several countries or departments, you don't want " +"to bug your agents from other departments. Leaving these options empty will " +"fallback to showing everything to everyone." msgstr "" -#: ../system/objects.rst:56 -msgid "Updating Database After Adding or Editing Attributes" +#: ../system/integrations/cti/generic.rst:64 +msgid "Destination caller ID or Queue" msgstr "" -#: ../system/objects.rst:58 +#: ../system/integrations/cti/generic.rst:63 msgid "" -"When adding or changing attributes, Zammad will not apply the changes " -"instantly, but instead shows you the changed attributes first. If you're " -"ready to go, just click on \"Update database\" to apply the changes to " -"Zammad. If you made a mistake or just want to discard your changes, click " -"\"Discard changes\"." +"This depends on your PBX and usually is either a queue ID, phone number or " +"extension." msgstr "" -#: ../system/objects.rst:64 -msgid "" -"After applying the changes with \"Update Database\", a restart of Zammad is " -"**mandatory**. If you don't perform it, you may experience unexpected " -"behavior or even errors. You may want to do this kind of configuration " -"during maintenance windows." +#: ../system/integrations/cti/generic.rst:69 +msgid "Agents" msgstr "" -#: ../system/objects.rst:72 +#: ../system/integrations/cti/generic.rst:67 msgid "" -"Changes on objects require you to update the database to apply these changes." +"Select the agents that are responsible for the group. These agents will then " +"see caller log entries and call notifications fitting to said queue." msgstr "" -#: ../system/objects.rst:75 -msgid "**🤓 Service restarts can be automated**" +#: ../system/integrations/cti/generic.rst:0 +msgid "" +"Screenshot showing the caller log filter table with pre filled sample data" msgstr "" -#: ../system/objects.rst:0 -msgid "Hosted environments automatically restart for you." +#: ../system/integrations/cti/includes/recent-logs.include.rst:6 +msgid "" +"With recent logs Zammad allows you to view the latest calls for the CTI " +"functionality. This usually comes in handy, when you're looking for errors." msgstr "" -#: ../system/objects.rst:0 +#: ../system/integrations/cti/includes/recent-logs.include.rst:0 msgid "" -"If you're using a self-hosted installation you can use :docs:`environment " -"variables `" +"Screenshot showing several incoming requests within Recent logs section." msgstr "" -#: ../system/objects.rst:82 -msgid "System Attributes" +#: ../system/integrations/cti/includes/recent-logs.include.rst:16 +msgid "I'm just here to clear floats up." msgstr "" -#: ../system/objects.rst:84 +#: ../system/integrations/cti/includes/recent-logs.include.rst:20 msgid "" -"Zammad comes with pre-configured attributes. Some of them can't be edited " -"via UI (or at all). This is required for proper operation of Zammad and not " -"a bug." -msgstr "" - -#: ../system/objects.rst:90 -msgid "Ticket State" +"By clicking on the entry of interest, Zammad will provide more details on " +"the call in question. You'll see the payload it received and also the " +"response that was sent." msgstr "" -#: ../system/objects.rst:92 +#: ../system/integrations/cti/includes/recent-logs.include.rst:0 msgid "" -"If the pre-configured states aren't enough for you or you want to change " -"them, you can do so by clicking on the cogwheel icon in the state row in the " -"ticket tab. But you should be careful when changing pre-configured states. " -"This can lead to unwanted behavior in some cases." +"Screenshot showing detailed information of a specific log entry of recent " +"logs" msgstr "" -#: ../system/objects.rst:None -msgid "Screenshot showing highlighted ticket state attribute" +#: ../system/integrations/cti/includes/recent-logs.include.rst:31 +msgid "x" msgstr "" -#: ../system/objects.rst:122 -msgid "Handling of states" +#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 +#: ../system/integrations/cti/includes/troubleshooting.include.rst:9 +msgid "My Phone page stays blank, signalling does work..." msgstr "" -#: ../system/objects.rst:102 +#: ../system/integrations/cti/includes/troubleshooting.include.rst:5 msgid "" -"In the state configuration screen, you can add new states, disable states or " -"change states." +"If you've made sure that signalling works (check Recent logs) and your " +"Caller Log still stays empty, please ensure that you only configured one CTI " +"integration version. Specifically defining more than one agent mapping on " +"the different integration variants will be the issue." msgstr "" -#: ../system/objects.rst:0 -msgid "Screenshot showing table of default ticket states" +#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 +msgid "Clear the not needed agent mapping and reload your browser page." msgstr "" -#: ../system/objects.rst:110 +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:1 msgid "" -"To add a new state, click on the \"New Ticket State\" button in the top " -"right corner. To change an existing state, simply click on the affected " -"state. This opens an edit dialog." +"By mapping your agents extension to their existing Zammad users, Zammad can " +"provide a new ticket dialog or open the user profile for the agent that " +"picks up the call." msgstr "" -#: ../system/objects.rst:114 +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:5 msgid "" -"You can also clone a state or set them to \"Default for new tickets\" or " -"\"Default for follow-ups\" by clicking on the ⁝ action button and select the " -"desired function." +"This speeds up ticket aiding, no matter if it's for existing tickets or new " +"ones!" msgstr "" -#: ../system/objects.rst:118 +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:8 msgid "" -"*Default for new tickets* means that this state is used for every newly " -"created ticket." +"To see it work from the agent's perspective, have a look on :user-docs:`user " +"documentation `." msgstr "" -#: ../system/objects.rst:121 -msgid "" -"*Default for follow-ups* means that this state is used if the ticket is re-" -"opened after it was closed." +#: ../system/integrations/cti/placetel.rst:2 +msgid "Placetel CTI" msgstr "" -#: ../system/objects.rst:171 -msgid "Ticket state in detail" +#: ../system/integrations/cti/placetel.rst:16 +msgid "You need an administrative Placetel account for your organization." msgstr "" -#: ../system/objects.rst:125 +#: ../system/integrations/cti/placetel.rst:17 +#: ../system/integrations/cti/sipgate.rst:20 msgid "" -"Below you can find a description for each field and option. Please head over " -"to the :ref:`example ` to see the edit dialog." +"Your Zammad instance must be allowed to communicate to external services." msgstr "" -#: ../system/objects.rst:129 -msgid "" -"This is the name of the state and what you and your agents are seeing when " -"choosing a state somewhere (e.g. in tickets, trigger configuration)." +#: ../system/integrations/cti/placetel.rst:18 +msgid "Placetel must be able to reach your Zammad instance." msgstr "" -#: ../system/objects.rst:137 -msgid "" -"There are different state types you can choose from. By default, Zammad " -"comes with one state per state type." +#: ../system/integrations/cti/placetel.rst:22 +msgid ":doc:`provider-configurations/placetel`" msgstr "" -#: ../system/objects.rst:140 +#: ../system/integrations/cti/placetel.rst:21 msgid "" -"**new**: for states for tickets that are new and it hasn't been worked on " -"them" +"Learn how to configure Placetel to enable Zammad and Placetel to communicate " +"with each other." msgstr "" -#: ../system/objects.rst:142 +#: ../system/integrations/cti/placetel.rst:32 msgid "" -"**open**: for states for tickets that are in progress and agents are working " -"on them" -msgstr "" - -#: ../system/objects.rst:144 -msgid "**merged**: for states for tickets that are merged with other tickets" +"The here listed endpoint settings are relevant for the :doc:`integration " +"configuration with Placetel `." msgstr "" -#: ../system/objects.rst:145 -msgid "" -"**pending reminder**: for states for tickets that are in progress and you " -"want to set a reminder. (default example: *pending reminder*)" +#: ../system/integrations/cti/placetel.rst:37 +#: ../system/integrations/i-doit.rst:53 +msgid "Endpoint" msgstr "" -#: ../system/objects.rst:147 +#: ../system/integrations/cti/placetel.rst:36 msgid "" -"**pending action**: for states for tickets that are waiting for a specified " -"time and then change their state (default example: *pending close*)" +"This endpoint will be required for the Zammad integration within the " +"Placetel web interface." msgstr "" -#: ../system/objects.rst:150 -msgid "" -"**closed**: for states for tickets that are finished and do not need to be " -"processed further" +#: ../system/integrations/cti/placetel.rst:41 +msgid "API Token" msgstr "" -#: ../system/objects.rst:153 +#: ../system/integrations/cti/placetel.rst:40 msgid "" -"⚠️ Choosing the correct state type is important! If you are in doubt, have a " -"look on the default states and their types!" +"You'll receive this token within the ``Web API`` menu. Make sure to copy " +"this value, it's only shown once!" msgstr "" -#: ../system/objects.rst:158 -msgid "Ignore escalation" +#: ../system/integrations/cti/placetel.rst:71 +#: ../system/integrations/cti/sipgate.rst:77 +msgid "Phone Extension to Agent Mapping" msgstr "" -#: ../system/objects.rst:157 -msgid "" -"Here you can define whether tickets of this state will count to escalation " -"time or not." +#: ../system/integrations/cti/placetel.rst:0 +msgid "Screenshot showing sample user mappings in between Placetel and Zammad" msgstr "" -#: ../system/objects.rst:161 +#: ../system/integrations/cti/placetel.rst:64 msgid "" -"You can create a note for the state to inform other admins about the state. " -"This has no effect on tickets." +"You can find your agents Placetel username combination required within ⚙️ PBX " +"→ VoIP destinations. Within the \"Advanced settings\" section you're looking " +"for \"SIP user name\" and \"SIP server\"." msgstr "" -#: ../system/objects.rst:165 -msgid "Set the state to *active* or *inactive*." +#: ../system/integrations/cti/placetel.rst:68 +msgid "Combine these two like so: ``@``." msgstr "" -#: ../system/objects.rst:167 -msgid "" -"it is technically possible to set all states to inactive. To keep Zammad " -"working in such a case, the inactive flag of one of the states is ignored." +#: ../system/integrations/cti/placetel.rst:0 +msgid "Sample VoIP credentials for a Placetel user" msgstr "" -#: ../system/objects.rst:194 -msgid "Ticket state example" +#: ../system/integrations/cti/provider-configurations/placetel.rst:2 +msgid "Setup Placetel connection for Zammad" msgstr "" -#: ../system/objects.rst:174 +#: ../system/integrations/cti/provider-configurations/placetel.rst:6 msgid "" -"Let's assume we want to create a new state which indicates that the ticket " -"has to wait for a response of a third party (e.g. service contractor or " -"manufacturer) and we want to to be able to set a reminder." +"This configuration step requires a *full* administrative Placetel account. " +"You may receive forbidden error messages with Placetel in case your " +"permissions are not high enough." msgstr "" -#: ../system/objects.rst:178 +#: ../system/integrations/cti/provider-configurations/placetel.rst:10 msgid "" -"First we give the new state a proper name. In this example we call it " -"\"waiting for manufacturer\"." +"The following actions can be configured via the `Placetel web interface " +"`_." msgstr "" -#: ../system/objects.rst:181 -msgid "" -"As state type we choose \"pending reminder\". This indicates that the ticket " -"is still open and we can set a reminder. This reminder can be useful if our " -"manufacturer sometimes isn't responding or we want to remind him to give us " -"an answer." +#: ../system/integrations/cti/provider-configurations/placetel.rst:29 +msgid "Step 1: Activate Zammad integration" msgstr "" -#: ../system/objects.rst:186 +#: ../system/integrations/cti/provider-configurations/placetel.rst:14 msgid "" -"We choose \"no\" for \"ignore escalation\" because we want to escalate the " -"tickets even if we are waiting on the manufacturer's feedback." -msgstr "" - -#: ../system/objects.rst:189 -msgid "The **result** in the creation dialog will look like this:" +"Within Integrations, scroll down to Partner integrations and select Zammad." msgstr "" -#: ../system/objects.rst:0 -msgid "Screenshot showing ticket state creation dialog with example" +#: ../system/integrations/cti/provider-configurations/placetel.rst:17 +msgid "" +"You can alternatively filter by \"Ticket Systems\" to reduce the number of " +"entries on the page. You'll still want to look for Partner integrations. 🤓" msgstr "" -#: ../system/objects.rst:197 ../system/objects.rst:199 -msgid "Ticket Priority" +#: ../system/integrations/cti/provider-configurations/placetel.rst:21 +msgid "" +"Within the Zammad integration now press \"Activate\". A new tab ``API`` " +"becomes available - open this tab." msgstr "" -#: ../system/objects.rst:199 ../system/objects.rst:201 +#: ../system/integrations/cti/provider-configurations/placetel.rst:24 msgid "" -"If the pre-configured priorities aren't enough for you or you want to change " -"them, you can do so by clicking on the cogwheel icon in the priority row in " -"the ticket tab:" +"Now tick \"Enable Call Control / Notify API\" and paste the Placetel " +"endpoint from your Zammad instance into the field \"URL of your API " +"endpoint\". Save to apply the settings" msgstr "" -#: ../system/objects.rst:None -msgid "Screenshot showing highlighted ticket priority attribute" +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "Screencast showing how to activate the Zammad integration" msgstr "" -#: ../system/objects.rst:224 ../system/objects.rst:226 -msgid "Handling of priorities" +#: ../system/integrations/cti/provider-configurations/placetel.rst:51 +msgid "Step 2: Generate API Token for Placetel" msgstr "" -#: ../system/objects.rst:208 ../system/objects.rst:210 +#: ../system/integrations/cti/provider-configurations/placetel.rst:32 msgid "" -"In the priority configuration screen, you can add new priorities, disable " -"priorities or change priorities." +"Go back to the integrations page and scroll down to \"Web API\". Generate a " +"new API token by using the \"Create a new API token\" button." msgstr "" -#: ../system/objects.rst:0 -msgid "Screenshot showing table of default ticket priorities" +#: ../system/integrations/cti/provider-configurations/placetel.rst:37 +msgid "" +"If you already generated a token either use your existing token or reset it " +"by using above mentioned button. Placetel will ask you to conform this reset." msgstr "" -#: ../system/objects.rst:216 ../system/objects.rst:218 +#: ../system/integrations/cti/provider-configurations/placetel.rst:41 msgid "" -"To add a new priority, click on the \"New Priority\" button in the top right " -"corner. To change an existing priority, simply click on the affected " -"priority. This opens an edit dialog." +"Please keep in mind that existing API scripts may no longer work due to " +"token resets!" msgstr "" -#: ../system/objects.rst:220 ../system/objects.rst:222 +#: ../system/integrations/cti/provider-configurations/placetel.rst:44 msgid "" -"You can also clone a priority or set them to \"Default for new tickets\" by " -"clicking on the ⁝ action button and select the desired function." +"Copy the provided API token and insert it into the \"API Token\" field " +"within Zammad's Placetel integration." msgstr "" -#: ../system/objects.rst:223 ../system/objects.rst:225 +#: ../system/integrations/cti/provider-configurations/placetel.rst:47 msgid "" -"*Default for new tickets* means that this priority is used for every newly " -"created ticket." +"Apply your changes by using the \"Save\" button on the bottom of the " +"Placetel integration page and activate the Placetel integration." msgstr "" -#: ../system/objects.rst:246 ../system/objects.rst:248 -msgid "Priorities in detail" +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "" +"Screencast showing how to retrieve an API token from Placetel for Zammad" msgstr "" -#: ../system/objects.rst:227 ../system/objects.rst:229 -msgid "Below you can find a description for each field and option." +#: ../system/integrations/cti/provider-configurations/placetel.rst:73 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:77 +msgid "Step 3: Restrict the numbers to notify on" msgstr "" -#: ../system/objects.rst:230 ../system/objects.rst:232 +#: ../system/integrations/cti/provider-configurations/placetel.rst:54 msgid "" -"This is the name of the priority and what you and your agents are seeing " -"when choosing a priority somewhere (e.g. in tickets, trigger configuration)." +"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " +"the the Integrations page of the Placetel web interface, go to \"Notify " +"API\"." msgstr "" -#: ../system/objects.rst:240 ../system/objects.rst:242 -msgid "Highlight color" +#: ../system/integrations/cti/provider-configurations/placetel.rst:58 +msgid "" +"Lower on the page Placetel allows you to restrict the numbers to notify on. " +"You'll find this within the \"External routing API\" part." msgstr "" -#: ../system/objects.rst:235 ../system/objects.rst:237 +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 msgid "" -"Switch between *Low priority* (light blue), *High priority* (red) and - " -"(default). This affects the displayed color for ticket titles in overviews." +"Screenshot showing a sample selection of phone numbers to use for the " +"Placetels notify API" msgstr "" -#: ../system/objects.rst:239 ../system/objects.rst:241 -msgid "The color options are currently limited to the mentioned options." +#: ../system/integrations/cti/provider-configurations/placetel.rst:66 +msgid "" +"This menu point also provides a API request log from Placetel view. Just " +"open \"Recent responses of your API endpoint\" to learn more." msgstr "" -#: ../system/objects.rst:243 ../system/objects.rst:245 +#: ../system/integrations/cti/provider-configurations/placetel.rst:69 msgid "" -"You can create a note for the priority to inform other admins about the " -"priority. This has no effect on tickets." +"If you want to see Zammad's perspective, use the \"Recent Logs\" part from " +"within the Placetel integration page." msgstr "" -#: ../system/objects.rst:247 ../system/objects.rst:249 -msgid "Set the priority to *active* or *inactive*." +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "Screenshot showing sample log entries for Placetels API calls to Zammad" msgstr "" -#: ../system/objects/external-data-source-example.rst:2 -msgid "External Data Source" +#: ../system/integrations/cti/provider-configurations/placetel.rst:77 +msgid "Step 4 (optional): Further configurations for Placetel" msgstr "" -#: ../system/objects/external-data-source-example.rst:4 +#: ../system/integrations/cti/provider-configurations/placetel.rst:76 msgid "" -"We assume you already had a look on :doc:`types` where you can find a " -"description of the individual fields." +"If needed, you can now configure Zammad's Placetel integration in more " +"detail. You can learn more about your options here: :ref:`Placetel " +"integration settings `." msgstr "" -#: ../system/objects/external-data-source-example.rst:7 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:2 +msgid "Setup Sipgate connection for Zammad" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"To reproduce this example, choose a category you want to add a custom field, " -"click on *New Attribute* and select *External data source field* under " -"*Format*." +"Sipgate has no english web interface which is why this documentation page is " +"mixing up languages badly." msgstr "" -#: ../system/objects/external-data-source-example.rst:11 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"Our example story is to fetch data from an external product database. We " -"want to add our products to the tickets so that the products can be searched " -"and chosen from a list and also create a link to the product website." +"Please also note that the availability of API addons highly depends on your " +"package trier. Usage of sipgate.io packages *is not free*, please check " +"their `pricing page `_ before!" msgstr "" -#: ../system/objects/external-data-source-example.rst:16 -msgid "Base configuration" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:35 +msgid "Step 1: Book sipgate.io package" msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Initial steps to configure external data source object type" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:13 +msgid "Skip to step 2 if you already have the package booked!" msgstr "" -#: ../system/objects/external-data-source-example.rst:23 -#: ../system/variables.rst:85 -msgid "**Example:**" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:15 +msgid "" +"Login to an administrative Sipgate account and navigate to " +"``Accountverwaltung``. You'll see several different options depending on " +"your booked packages. Select ``Verträge & Produkte`` to continue." msgstr "" -#: ../system/objects/external-data-source-example.rst:25 -msgid "Name: *product*" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:19 +msgid "" +"Scroll down to the section ``Zusätzliche Produkte buchen`` and look for " +"``sipgate.io`` - select this product by using the ``Produkte anzeigen``-" +"Button." msgstr "" -#: ../system/objects/external-data-source-example.rst:26 -msgid "Display: *Product*" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:23 +msgid "" +"On the next page select either one of the ``sipgate.io`` packages or ``Push-" +"API Package Free``. Follow the dialogue by booking the addon. You'll be " +"returned to your contract overview and now should see the selected addon in " +"your list." msgstr "" -#: ../system/objects/external-data-source-example.rst:29 -msgid "External data source configuration" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:30 +msgid "" +"The availability for ``sipgate.io`` packages and their levels highly depends " +"on the overall account type and product you've booked with Sipgate." msgstr "" -#: ../system/objects/external-data-source-example.rst:31 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"First, enter the search URL making sure it contains ``#{search.term}`` as a " -"parameter:" +"Screencast showing the process on how to book the required sipgate.io addon" msgstr "" -#: ../system/objects/external-data-source-example.rst:34 -msgid "**Example:** ``https://dummyjson.com/products/search?q=#{search.term}``" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:52 +msgid "Step 2: Configure webhook for Zammad" msgstr "" -#: ../system/objects/external-data-source-example.rst:36 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:38 msgid "" -"After that, head down to the preview section and enter a search input for " -"the external data source." +"Within your ``Accountverwaltung`` navicate to your product ``sipgate.io``. " +"In the newly opened tab, switch from \"Clients\" to \"Webhooks\" and paste " +"the endpoint URLs from your Zammad instance like so:" msgstr "" -#: ../system/objects/external-data-source-example.rst:39 -msgid "**Example:** ``mac``" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:42 +msgid "Inbound endpoint to \"Incoming\"" msgstr "" -#: ../system/objects/external-data-source-example.rst:41 -msgid "Then you can find a preview of the response data below:" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:43 +msgid "Outbound endpoint to \"Outgoing\"" msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of JSON response based on search term" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:47 +msgid "" +"Ensure to select at least one call group or phoneline within \"Sources\". " +"Other wise Sipgate will not indicate any incoming or outgoing calls to " +"Zammad." msgstr "" -#: ../system/objects/external-data-source-example.rst:48 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"We recommend using the preview to have a look on the structure. There is a " -"top-level element called ``products``. One level below, you can find the " -"attributes ``id`` and ``title``." +"Screencast showing how to add Zammad's endpoint URLs to sipgate.ios webhook " +"configuration" msgstr "" -#: ../system/objects/external-data-source-example.rst:52 -msgid "**Search result response based on search from example:**" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:55 +msgid "" +"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " +"the Webhooks → URLs section of Sipgate you can select which *sources* " +"Sipgate should notify Zammad about in- and outgoing calls." msgstr "" -#: ../system/objects/external-data-source-example.rst:119 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:59 msgid "" -"To tell the remote system that the desired data is located below the " -"``products`` level, you have to put it in the field *Search result list key*." +"Use either specific phone lines or use the option \"Use for all phonelines " +"and groups\" to notify Zammad about all existing lines of your Sipgate " +"account." msgstr "" -#: ../system/objects/external-data-source-example.rst:122 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"After inserting ``products`` in the mentioned field, you get an extended " -"preview. You can find an additional box *Search result list* with a JSON " -"structure. This is the same response as before but stripped from the upper " -"``products`` element by the external data source." +"Screenshot showing a sample selection of phone numbers to use for the " +"Sipgates webhooks API" msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of JSON response search result list" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:68 +msgid "This section also allows you to enable a Debug log." msgstr "" -#: ../system/objects/external-data-source-example.rst:132 -msgid "" -"Now you need to provide the keys for the search result values and labels. As " -"already mentioned, we are looking for the ``id`` and the ``title`` of our " -"products. If you haven't already, it is now a good time to look at the " -"preview of the *Search result list*." +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "Screenshot showing an enabled Debug log option" msgstr "" -#: ../system/objects/external-data-source-example.rst:197 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:73 msgid "" -"After locating our two keys, we insert them in *search result value key* " -"(``id``) and in *Search result label key* (``title``)." +"After enabling you can use the Debug log section to see all sent webhook " +"calls to Zammad. You'll also can see the response." msgstr "" -#: ../system/objects/external-data-source-example.rst:200 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"Basically, we configured the external data source already and we can see a " -"table in the preview section:" -msgstr "" - -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of product table based on search term" +"Screenshot showing sample log entries for Sipgates webhook calls to Zammad" msgstr "" -#: ../system/objects/external-data-source-example.rst:208 -msgid "" -"According to our example story, now just the *Link template* is missing." +#: ../system/integrations/cti/provider-configurations/sipgate.rst:81 +msgid "Step 4 (optional): Further configurations for Sipgate" msgstr "" -#: ../system/objects/external-data-source-example.rst:210 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:80 msgid "" -"Please note that this is an optional feature. If you don't want to use such " -"links, of course you don't have to configure it." +"If needed, you can now configure Zammad's Sipgate integration in more " +"detail. You can learn more about your options here: :ref:`Sipgate " +"integration settings `." msgstr "" -#: ../system/objects/external-data-source-example.rst:213 -msgid "" -"We can add now an address where additional product information can be found." +#: ../system/integrations/cti/sipgate.rst:2 +msgid "Sipgate (sipgate.io)" msgstr "" -#: ../system/objects/external-data-source-example.rst:215 -msgid "Example: ``https://your_domain.com/q=#{ticket.product}``" +#: ../system/integrations/cti/sipgate.rst:16 +msgid "You need an administrative Sipgate account for your organization." msgstr "" -#: ../system/objects/external-data-source-example.rst:217 -msgid "In the example, the parameter means:" +#: ../system/integrations/cti/sipgate.rst:17 +msgid "" +"Zammad requires a ``sipgate.io`` addon from the feature store (please note " +"that API calls are not free with Sipgate. Rates may apply and differ from " +"account to account)." msgstr "" -#: ../system/objects/external-data-source-example.rst:219 -msgid "``#{}``: \"Frame\" for the insertion of information" +#: ../system/integrations/cti/sipgate.rst:21 +msgid "Sipgate must be able to reach your Zammad instance." msgstr "" -#: ../system/objects/external-data-source-example.rst:220 -msgid "``ticket``: object level, where you create your custom object" +#: ../system/integrations/cti/sipgate.rst:25 +msgid ":doc:`provider-configurations/sipgate`" msgstr "" -#: ../system/objects/external-data-source-example.rst:221 -msgid "``product``: name of the (custom) object" +#: ../system/integrations/cti/sipgate.rst:24 +msgid "" +"Learn how to configure Sipgate to enable Zammad and Sipgate to communicate " +"with each other." msgstr "" -#: ../system/objects/external-data-source-example.rst:223 +#: ../system/integrations/cti/sipgate.rst:33 msgid "" -"After configuring your *Link template*, there will be another column in the " -"preview. Hovering on the icons in the *Link* column will show you where it " -"forwards you." +"Below endpoint settings affect the :doc:`sipgate.io configuration `." msgstr "" -#: ../system/objects/external-data-source-example.rst:232 -msgid "" -"In our example, one of the links looks like: https://your_domain.com/q=6, " -"where the 6 is the product id." +#: ../system/integrations/cti/sipgate.rst:37 +msgid "This endpoint is required for incoming call hooks." +msgstr "" + +#: ../system/integrations/cti/sipgate.rst:40 +msgid "This endpoint is required for outgoing call hooks." msgstr "" -#: ../system/objects/external-data-source-example.rst:235 -msgid "You can find more information regarding the URL in :doc:`types`." +#: ../system/integrations/cti/sipgate.rst:0 +msgid "Screenshot showing sample user mappings in between Sipgate and Zammad" msgstr "" -#: ../system/objects/includes/adding-values-hint.include.rst:3 +#: ../system/integrations/cti/sipgate.rst:69 msgid "" -"Adding values can be tricky for first timers, don't forget to press \"➕ " -"Add\" after typing your values. Otherwise you may loose a value." +"You can find your agent's Sipgate username within ``Accountverwaltung → " +"Benutzer``. You're looking for the SIP-ID." msgstr "" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:1 -#: ../system/objects/includes/reposition-values.include.rst:1 -msgid "**↕️ This field type allows the positioning of its values ↔️**" +#: ../system/integrations/cti/sipgate.rst:0 +msgid "Sample VoIP credentials for a Sipgate user" msgstr "" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:3 -msgid "" -"In order to re-arrange the field values, first edit the field. Then you can " -"use ☰ to drag the values in question to the correct position. If you want to " -"change the layer depth, double click on ☰. With it you can cycle through the " -"available layers." +#: ../system/integrations/cti/sipgate.rst:77 +msgid "Users with several devices also have several SIP-IDs." msgstr "" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:8 -msgid "When you're ready, submit your changes to save the object attribute." +#: ../system/integrations/elasticsearch.rst:2 +msgid "Elasticsearch (SaaS)" msgstr "" -#: :0 ../system/objects/types.rst:0 +#: ../system/integrations/elasticsearch.rst:4 msgid "" -"Screencast showing how to re-position values on tree select like\n" -"fields" +"The Elasticsearch integration allows you to create a read-only user to use " +"with your favorite reporting tool (e.g. like Grafana)." msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:3 +#: ../system/integrations/elasticsearch.rst:7 msgid "" -"In order to re-arrange the field values, edit the field and scroll below the " -"values. Make sure to tick the option \"Use custom option sort\"." +"If you want to take full advantage of the Zammad reporting, have a look at " +"our :docs:`Grafana ` " +"setup page as well." msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:8 -msgid "" -"If you do not tick this field, all manual positioning you did above will be " -"lost upon saving! ☠️" +#: ../system/integrations/elasticsearch.rst:11 ../system/subscription.rst:7 +msgid "**🚧 Hosted environment specific 🚧**" msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:11 +#: ../system/integrations/elasticsearch.rst:13 msgid "" -"Now use ☰ to drag the values in question to the correct position. When " -"you're ready, submit your changes to save the object attribute." -msgstr "" - -#: :0 ../system/objects/types.rst:0 -msgid "Screencast showing how to re-position values" +"This integration is only available for Hosted setups. In order to use " +"Elasticsearch you'll need the **Plus** subscription." msgstr "" -#: ../system/objects/includes/url-template-hint.include.rst:3 +#: ../system/integrations/elasticsearch.rst:16 msgid "" -"This field allows using :ref:`URL fields (Link Templates) `." +"Self hosted users have all the control over their self hosted Elasticsearch " +"instances." msgstr "" -#: ../system/objects/permissions.rst:2 -msgid "Attribute Permissions" +#: ../system/integrations/elasticsearch.rst:None +msgid "Elasticsearch integration page on SaaS environments" msgstr "" -#: ../system/objects/permissions.rst:7 +#: ../system/integrations/elasticsearch.rst:27 msgid "" -"In the object attributes configuration you can define if a field is shown " -"and if the input in the field is mandatory, separated by different screens " -"and for different :doc:`roles/permissions `." +"Please note the following limitations of Elasticsearch access on hosted " +"environments:" msgstr "" -#: ../system/objects/permissions.rst:17 -msgid "Screenshot shows object attribute permission table" +#: ../system/integrations/elasticsearch.rst:30 +msgid "access to the Elasticsearch index is read-only access" msgstr "" -#: ../system/objects/permissions.rst:17 -msgid "" -"Some of the possible permissions and screen options for a user object " -"attribute." +#: ../system/integrations/elasticsearch.rst:31 +msgid "currently you're limited to user only" msgstr "" -#: ../system/objects/permissions.rst:19 +#: ../system/integrations/elasticsearch.rst:32 msgid "" -"Based on the object context (ticket, agent, organization, user), the " -"selectable roles (to be precise: the required permissions) and screens " -"differ. Be aware that these settings aren't affecting data creation via " -"other channels than the UI." +"Reporting tools that require to write into the indexes (like Kibana) are not " +"supported" msgstr "" -#: ../system/objects/permissions.rst:24 -msgid "" -"If you want to have further customization possibilities, you should have a " -"look at the :doc:`core workflows `." +#: ../system/integrations/elasticsearch.rst:34 +msgid "IP access restriction is currently not yet supported" msgstr "" -#: ../system/objects/permissions.rst:28 -msgid "Screens" +#: ../system/integrations/elasticsearch.rst:37 +msgid "Activating Elasticsearch Access" msgstr "" -#: ../system/objects/permissions.rst:30 +#: ../system/integrations/elasticsearch.rst:39 msgid "" -"In the table below you can find an overview about the different permissions " -"and the available screens Zammad distinguishes between." -msgstr "" - -#: ../system/objects/permissions.rst:37 -msgid "Screen" +"By default external access to your Elasticsearch index is not active. You " +"can enable the integration at any time if needed." msgstr "" -#: ../system/objects/permissions.rst:38 -msgid "Available for" +#: ../system/integrations/elasticsearch.rst:42 +msgid "" +"Please ensure to note down the password provided - you won't have access to " +"it afterwards." msgstr "" -#: ../system/objects/permissions.rst:40 -msgid "create" +#: ../system/integrations/elasticsearch.rst:None +msgid "Screencast showing activation of Elasticsearch integration" msgstr "" -#: ../system/objects/permissions.rst:41 ../system/objects/permissions.rst:52 -#: ../system/objects/permissions.rst:59 ../system/objects/permissions.rst:73 -msgid "admin.user" +#: ../system/integrations/elasticsearch.rst:51 +msgid "Connection Settings" msgstr "" -#: ../system/objects/permissions.rst:42 ../system/objects/permissions.rst:53 -#: ../system/objects/permissions.rst:60 -msgid "admin.organization" +#: ../system/integrations/elasticsearch.rst:53 +msgid "" +"This section holds the most important general information for accessing your " +"Elasticsearch indexes - such as:" msgstr "" -#: ../system/objects/permissions.rst:43 ../system/objects/permissions.rst:54 -#: ../system/objects/permissions.rst:61 -msgid "admin.group" +#: ../system/integrations/elasticsearch.rst:57 +msgid "A unique subdomain that does not tell your real instance URL." msgstr "" -#: ../system/objects/permissions.rst:44 -msgid "Creation dialog for not yet existing data" +#: ../system/integrations/elasticsearch.rst:61 +msgid "Software" msgstr "" -#: ../system/objects/permissions.rst:45 -msgid "create_middle" +#: ../system/integrations/elasticsearch.rst:60 +msgid "" +"The major version of the search index being used. This is required by some " +"Reporting tools like Grafana." msgstr "" -#: ../system/objects/permissions.rst:46 ../system/objects/permissions.rst:50 -#: ../system/objects/permissions.rst:57 ../system/objects/permissions.rst:66 -#: ../system/objects/permissions.rst:70 -msgid "ticket.customer" +#: ../system/integrations/elasticsearch.rst:64 +msgid "Authentication" msgstr "" -#: ../system/objects/permissions.rst:47 ../system/objects/permissions.rst:51 -#: ../system/objects/permissions.rst:58 ../system/objects/permissions.rst:69 -msgid "ticket.agent" +#: ../system/integrations/elasticsearch.rst:64 +msgid "The authentication type being supported. ``Basic Authentication``" msgstr "" -#: ../system/objects/permissions.rst:48 -msgid "Ticket create dialog (middle section)" +#: ../system/integrations/elasticsearch.rst:67 +msgid "Available Indexes" msgstr "" -#: ../system/objects/permissions.rst:49 -msgid "edit" +#: ../system/integrations/elasticsearch.rst:69 +msgid "" +"Within this section we're displaying the -in our opinion- most important " +"indexes for a Zammad instance." msgstr "" -#: ../system/objects/permissions.rst:55 -msgid "Editing dialog for already existing data" +#: ../system/integrations/elasticsearch.rst:72 +msgid "" +"If you require all indexes or our listing is not good enough for you, point " +"your browser to the URL we're providing and append ``/_aliases?" +"pretty=true``. The result should look like this: ``https://.zammad.com/" +"_aliases?pretty=true``." msgstr "" -#: ../system/objects/permissions.rst:56 -msgid "view" +#: ../system/integrations/elasticsearch.rst:77 +msgid "" +"Your browser will automatically ask for your credentials - you'll then see " +"something like this:" msgstr "" -#: ../system/objects/permissions.rst:62 -msgid "View-only dialog for already existing data" +#: ../system/integrations/elasticsearch.rst:125 +msgid "Credentials" msgstr "" -#: ../system/objects/permissions.rst:64 -msgid "(e.g. user or organization from search)" +#: ../system/integrations/elasticsearch.rst:127 +msgid "" +"Within this section Zammad displays your available users. The password is " +"provided once (upon activation) and cannot be retrieved after that." msgstr "" -#: ../system/objects/permissions.rst:65 -msgid "signup" +#: ../system/integrations/elasticsearch.rst:131 +msgid "" +"If you need to change or reset your Elasticsearch user password, use the " +"\"Reset password\" button in the credentials table. Doing so creates a brand " +"new password for the account in question. This change is immediate, keep in " +"mind that this may affect third party tools connected to your instance." msgstr "" -#: ../system/objects/permissions.rst:67 -msgid "Sign-up screen for new customers" +#: ../system/integrations/exchange.rst:2 +msgid "Exchange" msgstr "" -#: ../system/objects/permissions.rst:68 -msgid "invite_customer" +#: ../system/integrations/exchange.rst:4 +msgid "" +"With Zammad's Exchange integration, you can easily use existing address " +"books without having to update more than one source." msgstr "" -#: ../system/objects/permissions.rst:71 +#: ../system/integrations/exchange.rst:7 msgid "" -"Customer invitation screen (from :doc:`First Steps ` area)" +"However, you should refrain from syncing all addresses, as the results may " +"not be what you expect (Exchange collects huge amounts of addresses). A " +"central address book of your company to sync makes more sense, as you can " +"ensure that Zammad gets only the data you need and want. Apart from this, it " +"is even not possible to sync the Global Address List (GAL) of your Exchange " +"system with Zammad." msgstr "" -#: ../system/objects/permissions.rst:72 -msgid "invite_agent" +#: ../system/integrations/exchange.rst:16 +msgid "" +"**Exchange and LDAP:** The exchange sync can be overruled by Zammad's LDAP " +"integration. If you have the same users in both sources, the LDAP version " +"will always be Zammad's pick." msgstr "" -#: ../system/objects/permissions.rst:74 +#: ../system/integrations/exchange.rst:19 msgid "" -"Agent invitation screen (from :doc:`First Steps ` area)" +"**One way sync:** the Exchange sync is one way. Exchange => Zammad. Changes " +"to your users inside of Zammad might be overwritten by the Exchange sync." msgstr "" -#: ../system/objects/permissions.rst:78 -msgid "Screen Options" +#: ../system/integrations/exchange.rst:24 +msgid "" +"To configure Exchange integration, simply go to the System > Integrations > " +"Exchange in the admin panel. Press \"change\" and follow the wizard for " +"adding the needed Exchange information to Zammad. On the last two steps " +"Zammad will ask you for the address book(s) and your desired attribute " +"mapping. By default, Zammad only maps email address, first- and lastname. " +"Technically, you can map any Exchange object to a Zammad user object (this " +"also works for custom objects!)." msgstr "" -#: ../system/objects/permissions.rst:80 +#: ../system/integrations/exchange.rst:35 msgid "" -"For the different screens you can select \"show\" and \"required\" options." +"If the SSL verification fails while connecting to Exchange, Zammad will ask " +"you to turn it off temporarily." msgstr "" -#: ../system/objects/permissions.rst:82 -msgid "**shown:** Show (check) or hide (uncheck) a field." +#: ../system/integrations/exchange.rst:38 +msgid "" +"Please be aware that **turning off SSL verification is a security risk**. It " +"should only be used temporarily or for testing purposes. If turned off, " +"there is no verification of the certificate, which means that every " +"presented certificate will be accepted." msgstr "" -#: ../system/objects/permissions.rst:83 +#: ../system/integrations/exchange.rst:43 msgid "" -"**required:** Set a field to mandatory (check). Forces users (via UI and " -"API) to populate the field." -msgstr "" - -#: ../system/objects/types.rst:7 -msgid "Example external data source" +"After pressing Continue, Zammad will check if the configuration is okay. You " +"can then enable Exchange and start your first sync. The sync will then run " +"hourly - if you need to change mappings or the address book(s), you can " +"change the configuration at any time." msgstr "" -#: ../system/objects/types.rst:2 -msgid "Attribute types" +#: ../system/integrations/exchange.rst:50 +msgid "" +"After the sync has finished, you can find the new Exchange contacts under " +"\"Users\". Zammad integrates them just as normal users." msgstr "" -#: ../system/objects/types.rst:4 +#: ../system/integrations/exchange.rst:55 msgid "" -"When adding a new object attribute, you can choose between the following " -"attribute types." +"In some cases you might see unique IDs as \"Login\" instead of the email " +"address. This is normal and doesn't affect the login or email mapping for " +"that entry." msgstr "" -#: ../system/objects/types.rst:14 +#: ../system/integrations/github.rst:4 msgid "" -"You cannot change the attribute format / type as soon as it is applied. If " -"you no longer need an object attribute, consider disabling it instead of " -"removing." +"Use GitHub integration to track GitHub issues directly within Zammad " +"tickets. Add issue hyperlinks and get a live summary of metadata like status " +"(open/closed), assignee, labels, and more." msgstr "" -#: ../system/objects/types.rst:18 -msgid "**What about the translation of my attributes?**" +#: ../system/integrations/github.rst:8 +msgid "Please note that our GitHub integration does not support pull requests." msgstr "" -#: ../system/objects/types.rst:20 -msgid "" -"For some attribute types you can decide if they should be translatable or " -"not. To be precise, it works only for the selectable fields because the " -"possible choices are known and limited. For the following attribute types, " -"you can set the translatable flag:" +#: ../system/integrations/github.rst:None +msgid "Integration page for GitHub" msgstr "" -#: ../system/objects/types.rst:25 -msgid "*Boolean field*" +#: ../system/integrations/github.rst:18 +msgid "" +"In your GitHub settings, create a new API token under **Developer settings > " +"Personal access tokens > Generate new token**. Leave the **Scopes** section " +"empty." msgstr "" -#: ../system/objects/types.rst:26 -msgid "*Single selection field*" +#: ../system/integrations/github.rst:0 ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to create a new API token" msgstr "" -#: ../system/objects/types.rst:27 -msgid "*Multiple selection field*" +#: ../system/integrations/github.rst:27 +msgid "Create a new API key with no scopes/privileges." msgstr "" -#: ../system/objects/types.rst:28 -msgid "*Single tree selection field*" +#: ../system/integrations/github.rst:29 +msgid "🔒 **Will this work for private repos?**" msgstr "" -#: ../system/objects/types.rst:29 -msgid "*Multiple tree selection field*" +#: ../system/integrations/github.rst:31 +msgid "" +"No. To link private repo issues, **use the** ``repo`` **scope instead**. " +"Bear in mind that the resulting token will have `lots of permissions that it " +"doesn't actually need `_, which presents a security risk if your token ever falls into " +"the wrong hands." msgstr "" -#: ../system/objects/types.rst:31 +#: ../system/integrations/github.rst:37 msgid "" -"For these types, you can find an additional field *Translate field contents*:" +"Unfortunately, because of how GitHub's OAuth token scopes are set up, this " +"is the only way to link issues on private repos." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Screenshot showing translatable attribute types" +#: ../system/integrations/github.rst:40 +msgid "Enter your new API token in Zammad and enable GitHub integration." msgstr "" -#: ../system/objects/types.rst:38 -msgid "Screenshot with example of translatable attribute type" +#: ../system/integrations/github.rst:0 +msgid "Screencast showing how to configure Zammad's GitHub integration" msgstr "" -#: ../system/objects/types.rst:45 -msgid "Boolean field" +#: ../system/integrations/github.rst:47 +msgid "" +"Use the default API endpoint (``https://api.github.com/graphql``) unless " +"you're using GitHub Enterprise Server." msgstr "" -#: ../system/objects/types.rst:41 +#: ../system/integrations/github.rst:50 msgid "" -"Provides a drop-down field with display values for ``true`` and ``false``. " -"Setting a default is mandatory." +"Once completed, a new GitHub issues tab will appear in the ticket pane. 🎉" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Boolean fields" +#: ../system/integrations/github.rst:59 ../system/integrations/gitlab.rst:52 +msgid "Token verification is taking a long time" msgstr "" -#: ../system/objects/types.rst:55 -msgid "Date field" +#: ../system/integrations/github.rst:56 ../system/integrations/gitlab.rst:49 +msgid "" +"Slight delays are normal (<2 min.), especially for systems under heavy load." msgstr "" -#: ../system/objects/types.rst:48 -msgid "Provides a date picker field and does not allow default values." +#: ../system/integrations/github.rst:58 +msgid "" +"Self-hosted administrators, please check your network settings to ensure " +"that your Zammad server can reach ``api.github.com``." msgstr "" -#: ../system/objects/types.rst:52 -msgid "Default time diff (hours)" +#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 +msgid "I reloaded the page and now the API token is gone" msgstr "" -#: ../system/objects/types.rst:51 +#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 msgid "" -"This setting helps the user by highlighting the day from now plus the " -"provided value. It *does not* pre-fill the field." -msgstr "" - -#: ../system/objects/types.rst:0 -msgid "Available settings for Date fields" +"This may indicate that Zammad is still verifying your API token. Try " +"reloading the page again in a couple minutes." msgstr "" -#: ../system/objects/types.rst:73 -msgid "Date & time field" +#: ../system/integrations/gitlab.rst:2 +msgid "GitLab" msgstr "" -#: ../system/objects/types.rst:58 -msgid "Provides a date and time picker – does not allow default values" +#: ../system/integrations/gitlab.rst:4 +msgid "" +"Use GitLab integration to track GitLab issues directly within Zammad " +"tickets. Add issue hyperlinks and get a live summary of metadata like status " +"(open/closed), assignee, labels, and more." msgstr "" -#: ../system/objects/types.rst:62 -msgid "Allow future" +#: ../system/integrations/gitlab.rst:8 +msgid "" +"Please note that our GitLab integration does not support merge requests." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Forbid dates and times in the future." +#: ../system/integrations/gitlab.rst:None +msgid "Integration page for GitLab" msgstr "" -#: ../system/objects/types.rst:66 -msgid "Allow past" +#: ../system/integrations/gitlab.rst:18 +msgid "" +"In your GitLab preferences, create a new API token under **Access Tokens**." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Forbid dates and times in the past." +#: ../system/integrations/gitlab.rst:20 +msgid "Under **Select scopes**, choose ``read_api`` only." msgstr "" -#: ../system/objects/types.rst:70 -msgid "Default time diff (minutes)" +#: ../system/integrations/gitlab.rst:27 +msgid "🔒 **If you wish to link issues on any private repos...**" msgstr "" -#: ../system/objects/types.rst:69 -msgid "" -"This setting helps the user by highlighting the day from now plus the " -"provided value. It does not pre-fill the field." +#: ../system/integrations/gitlab.rst:29 +msgid "Your API token must belong to an account with access to those repos." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Date & time fields" +#: ../system/integrations/gitlab.rst:31 +msgid "Enter your new API token in Zammad and enable GitLab integration." msgstr "" -#: ../system/objects/types.rst:86 -msgid "Integer field" +#: ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to configure Zammad's GitLab integration" msgstr "" -#: ../system/objects/types.rst:76 +#: ../system/integrations/gitlab.rst:40 msgid "" -"Provides an input field that allows integer usage only. You may define a " -"default value. You cannot enforce comma separation." +"Use the default API endpoint (``https://gitlab.com/api/graphql``) unless " +"you're a self-hosted GitLab user." msgstr "" -#: ../system/objects/types.rst:80 -msgid "Minimal" +#: ../system/integrations/gitlab.rst:43 +msgid "" +"Once completed, a new GitLab issues tab will appear in the ticket pane. 🎉" msgstr "" -#: ../system/objects/types.rst:80 -msgid "The minimal value the field accepts." +#: ../system/integrations/gitlab.rst:51 +msgid "" +"Self-hosted administrators, please check your network settings to ensure " +"that your Zammad server can reach ``gitlab.com``." msgstr "" -#: ../system/objects/types.rst:83 -msgid "Maximal" +#: ../system/integrations/i-doit.rst:2 +msgid "i-doit" msgstr "" -#: ../system/objects/types.rst:83 -msgid "The maximum value the field accepts." +#: ../system/integrations/i-doit.rst:4 +msgid "" +"`i-doit `_ is an open-source **configuration " +"management database** - in other words, a tool for keeping tabs on every " +"single piece of your physical and digital infrastructure, from network " +"equipment to virtual machines on down to the faceplates on your rack shelves " +"and more." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Integer fields" +#: ../system/integrations/i-doit.rst:10 +msgid "" +"What's that got to do with Zammad? Well, if you used tickets to track issues " +"with all that hardware, you might start wishing there was a way they could " +"talk to each other." msgstr "" -#: ../system/objects/types.rst:99 -msgid "Multiple selection field" +#: ../system/integrations/i-doit.rst:14 +msgid "Zammad gives you two:" msgstr "" -#: ../system/objects/types.rst:89 -msgid "" -"Provides a selection field that allows the selection of one or more out of " -"several. This field does allow setting a default value." +#: ../system/integrations/i-doit.rst:17 +msgid "1. Add i-doit Links to Zammad Tickets" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Multiple selection fields" +#: ../system/integrations/i-doit.rst:20 ../system/integrations/i-doit.rst:80 +msgid "What Users See" msgstr "" -#: ../system/objects/types.rst:112 -msgid "Single selection field" +#: ../system/integrations/i-doit.rst:26 +msgid "i-doit integration in Zammad's ticket pane" msgstr "" -#: ../system/objects/types.rst:102 +#: ../system/integrations/i-doit.rst:26 msgid "" -"Provides a drop-down field that allows selection of one value out of " -"several. This field does allow setting a default value." +"The i-doit integration will appear under a new 🖨 tab in the ticket pane." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Single selection fields" +#: ../system/integrations/i-doit.rst:28 +msgid "" +"i-doit integration puts a new tab in Zammad's ticket pane where you can add " +"links to existing i-doit devices for easy reference. (See our :user-docs:" +"`user documentation ` to learn " +"how it works in practice)." msgstr "" -#: ../system/objects/types.rst:142 -msgid "Textarea field" +#: ../system/integrations/i-doit.rst:36 ../system/integrations/i-doit.rst:93 +msgid "How to Set it Up" msgstr "" -#: ../system/objects/types.rst:115 +#: ../system/integrations/i-doit.rst:38 msgid "" -"Provides a text area input field (multiple lines) and thus allows e.g. new " -"lines. You can set a default field value." +"It requires i-doit's `API Add-on `_. Make sure to have it properly set up. Use the following setting:" msgstr "" -#: ../system/objects/types.rst:120 -msgid "" -"Please note that this field *does not* support text formatting or HTML " -"content (rich text)." +#: ../system/integrations/i-doit.rst:42 +msgid "Active: ``Yes``" msgstr "" -#: ../system/objects/types.rst:123 -msgid "**🥵 This field can consume a lot of visual space**" +#: ../system/integrations/i-doit.rst:43 +msgid "Enforce authentication by username and password: ``No``" msgstr "" -#: ../system/objects/types.rst:125 +#: ../system/integrations/i-doit.rst:45 msgid "" -"Depending on where you use this field type, it may use a lot of visual space " -"if you provide a lot of text. This may be an issue to work with." +"To set it up, enable the integration in the Zammad admin panel under " +"**System > Integrations > i-doit**:" msgstr "" -#: ../system/objects/types.rst:130 -msgid "Default" +#: ../system/integrations/i-doit.rst:None +msgid "i-doit settings within the integration pages" msgstr "" -#: ../system/objects/types.rst:129 -msgid "" -"The here provided text will be shown within the text area field or new data " -"sets." +#: ../system/integrations/i-doit.rst:53 +msgid "The root URL of your i-doit installation." msgstr "" -#: ../system/objects/types.rst:134 ../system/objects/types.rst:160 -msgid "Maxlength" +#: ../system/integrations/i-doit.rst:62 +msgid "API token" msgstr "" -#: ../system/objects/types.rst:0 ../system/objects/types.rst:160 -msgid "You can pick the maximum length of the field." +#: ../system/integrations/i-doit.rst:56 +msgid "" +"Found in the i-doit admin panel under **Interfaces / external data > JSON-" +"RPC API > Common Settings**." msgstr "" -#: ../system/objects/types.rst:0 -msgid "The default length of this object is ``500``." +#: ../system/integrations/i-doit.rst:0 +msgid "i-doit administration interface with API configuration" msgstr "" -#: ../system/objects/types.rst:139 -msgid "Rows" +#: ../system/integrations/i-doit.rst:67 +msgid "Client ID" msgstr "" -#: ../system/objects/types.rst:0 -msgid "" -"Change the number of rows to dislay so that you can use only the space you " -"really need." +#: ../system/integrations/i-doit.rst:65 +msgid "A unique name to identify Zammad within i-doit." msgstr "" -#: ../system/objects/types.rst:0 -msgid "The default number of rows is ``4``." +#: ../system/integrations/i-doit.rst:67 +msgid "(Zammad does not require you to enter a value here, but i-doit might!)" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Textarea fields" +#: ../system/integrations/i-doit.rst:70 +msgid "" +"Here you can decide if the certificate of your i-doit system has to be " +"verified or not. In case you are using custom certificates, please have a " +"look at :doc:`how to add them to Zammad `." msgstr "" -#: ../system/objects/types.rst:165 -msgid "Text field" +#: ../system/integrations/i-doit.rst:77 +msgid "2. List / Create Zammad Tickets in i-doit" msgstr "" -#: ../system/objects/types.rst:145 -msgid "Provides a text field (one line) and allows choosing a default value." +#: ../system/integrations/i-doit.rst:None +msgid "Zammad integration in i-doit's device view" msgstr "" -#: ../system/objects/types.rst:148 +#: ../system/integrations/i-doit.rst:86 msgid "" -"Defines the type of the input field. This allows e.g. your browser to ensure " -"that you provide the specific type." +"i-doit's ticket system integration gives you a way to see all the tickets " +"for a given device without ever leaving i-doit. (See our :user-docs:`user " +"documentation ` to learn how it " +"works in practice)." msgstr "" -#: ../system/objects/types.rst:152 -msgid "Currently available:" +#: ../system/integrations/i-doit.rst:95 +msgid "" +"Enable this integration in the i-doit admin panel under **Interfaces / " +"external data > Trouble Ticket System (TTS) > Configuration**:" msgstr "" -#: ../system/objects/types.rst:155 -msgid "Phone" +#: ../system/integrations/i-doit.rst:None +msgid "i-doit administration interface with TTS configuration" msgstr "" -#: ../system/objects/types.rst:156 -msgid "Text" +#: ../system/integrations/i-doit.rst:104 +msgid "TTS-Type" msgstr "" -#: ../system/objects/types.rst:157 -msgid "Url *(URL fields disable link-template availability)*" +#: ../system/integrations/i-doit.rst:104 +msgid "``Zammad``" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Text fields" +#: ../system/integrations/i-doit.rst:115 +msgid "Username / Password" msgstr "" -#: ../system/objects/types.rst:174 -msgid "Single tree selection field" +#: ../system/integrations/i-doit.rst:107 +msgid "Login credentials for a Zammad agent." msgstr "" -#: ../system/objects/types.rst:168 +#: ../system/integrations/i-doit.rst:109 msgid "" -"Provides a select-like field with up to 6 layers of options. Does not allow " -"setting a default value." +"This agent must have **read permission** for all :doc:`groups ` that plan on using the i-doit integration." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Tree Select fields" +#: ../system/integrations/i-doit.rst:113 +msgid "" +"You may even wish to create a dedicated agent account just for this " +"integration (otherwise, if the agent ever changes her password, you will " +"have to remember to update it here)." msgstr "" -#: ../system/objects/types.rst:183 -msgid "Multiple tree selection field" +#: ../system/integrations/i-doit.rst:117 +msgid "URL incl. protocol" msgstr "" -#: ../system/objects/types.rst:177 -msgid "" -"Provides a select-like field with up to 6 layers of options allowing the " -"selection of multiple values. Does not allow setting a default value." +#: ../system/integrations/i-doit.rst:118 +msgid "``https://your.zammad.domain``" msgstr "" -#: ../system/objects/types.rst:302 -msgid "External Data Source field" +#: ../system/integrations/index.rst:2 +msgid "Integrations" msgstr "" -#: ../system/objects/types.rst:186 +#: ../system/integrations/index.rst:4 msgid "" -"Provides a searchable field which fetches data from an external system. This " -"can be useful if you have data outside of Zammad and don't want to maintain " -"both data sources." +"Zammad offers numerous integrations that add rich features to your instance." msgstr "" -#: ../system/objects/types.rst:190 -msgid "The feature works as follows:" +#: ../system/integrations/index.rst:6 +msgid "We're still working on this part of our documentation, stay tight!" msgstr "" -#: ../system/objects/types.rst:192 -msgid "" -"Zammad sends a query with a search string (free text from agent or based on " -"a variable) in a pre-defined format (\"Search URL\") to an external system." +#: ../system/integrations/index.rst:10 +msgid "Integrations for Phone Systems" msgstr "" -#: ../system/objects/types.rst:195 +#: ../system/integrations/index.rst:14 msgid "" -"This external system searches for matches and provides a response as a JSON " -"structure to Zammad." +"Your VoIP provider or telephony system is not listed? Possibly your provider " +"supports Zammad by using the generic CTI - if you're unsure ask your " +"provider." msgstr "" -#: ../system/objects/types.rst:197 +#: ../system/integrations/index.rst:18 msgid "" -"Zammad just looks for the defined list and value keys, reads the content and " -"displays the value to the user. There is no search on Zammad side." +"Provider does not support Zammad? Consider creating a `feature request in " +"the Zammad Community `_." msgstr "" -#: ../system/objects/types.rst:201 -msgid "" -"The usage of a PostgreSQL database for Zammad is required. In any other " -"case, Zammad will hide the external data source type and you are not able to " -"use it. If you want to use this feature, consider to :docs:`migrate your " -"database `." +#: ../system/integrations/index.rst:31 +msgid "Integrations for Authentication and Customers" msgstr "" -#: ../system/objects/types.rst:205 -msgid "Currently, only ``GET`` is supported as request method." +#: ../system/integrations/index.rst:44 +msgid "Integrations for Monitoring Systems" msgstr "" -#: ../system/objects/types.rst:206 -msgid "" -"The data structure must be in JSON format and provide the objects in an " -"array." +#: ../system/integrations/index.rst:46 +msgid "This section currently misses the following integrations:" msgstr "" -#: ../system/objects/types.rst:208 -msgid "" -"The endpoint for the external data source has to support search. On Zammad " -"side, there is no search/logic implemented; however, you can define the " -"output key and value based on the result(s) from the response (which " -"provides already filtered content based on the search)." +#: ../system/integrations/index.rst:48 +msgid "Icinga" msgstr "" -#: ../system/objects/types.rst:212 -msgid "" -"If you receive more results as expected, your external data source search " -"may not work properly or the structure of the URL is not correct. You should " -"get in touch with a responsible person from the external system." +#: ../system/integrations/index.rst:49 +msgid "Monit" msgstr "" -#: ../system/objects/types.rst:217 -msgid "" -"Please have a look :doc:`at our example `, where you can find a possible configuration for a public " -"dummy endpoint." +#: ../system/integrations/index.rst:50 +msgid "Nagios" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for external data source fields" +#: ../system/integrations/index.rst:60 +msgid "Integrations for Issue Trackers" msgstr "" -#: ../system/objects/types.rst:242 -msgid "Search URL" +#: ../system/integrations/index.rst:70 +msgid "Other Integrations" msgstr "" -#: ../system/objects/types.rst:227 +#: ../system/integrations/index.rst:72 msgid "" -"Set your endpoint where Zammad fetches the data. Please make sure to include " -"a valid search :doc:`variable <../variables>` as an URL parameter. Example " -"for a free text search at user input: ``#{search.term}``" +"This section will hold any other integration that can't be grouped up (yet)." msgstr "" -#: ../system/objects/types.rst:232 -msgid "" -"If in doubt, ask the responsible person for the external data source how " -"they expect the strucuture of the URL." +#: ../system/integrations/ldap/index.rst:2 +msgid "LDAP / Active Directory" msgstr "" -#: ../system/objects/types.rst:236 +#: ../system/integrations/ldap/index.rst:4 msgid "" -"Depending on your search variable, the preview might work or not. The reason " -"is that the context might not be available and it is no bug." +"Zammad comes with a powerful LDAP integration that allows you to have a " +"single source of truth. By this you reduce the number of login credentials " +"your user has to remember." msgstr "" -#: ../system/objects/types.rst:239 +#: ../system/integrations/ldap/index.rst:10 msgid "" -"Please also make sure to use a variable which is available in your object " -"context. For example you won't be able to search for a ticket in a user " -"object context." -msgstr "" - -#: ../system/objects/types.rst:252 -msgid "SSL Verification" +"The LDAP source is also a perfect candidate for Zammad's :docs:`Kerberos " +"Single Sign-On ` but also works as addition " +"to other :doc:`/settings/security/third-party`." msgstr "" -#: ../system/objects/types.rst:245 -msgid "Here you can switch the SSL verification to no." +#: ../system/integrations/ldap/index.rst:None +msgid "Zammands LDAP management page" msgstr "" -#: ../system/objects/types.rst:249 -msgid "" -"If your external data source system is using self signed certificates, " -"please have a look :doc:`here ` for " -"further information about how to handle them in Zammad, so you can keep the " -"SSL verification activated." +#: ../system/integrations/ldap/index.rst:25 +msgid "📝 :doc:`manage`" msgstr "" -#: ../system/objects/types.rst:258 -msgid "HTTP Authentication" +#: ../system/integrations/ldap/index.rst:25 +msgid "Add, modify, remove or re-arrange your LDAP-Sources as needed." msgstr "" -#: ../system/objects/types.rst:255 -msgid "" -"If your external data source requires an authentication, you can set it " -"here. You can leave it empty or choose between *Basic Authentication* or " -"*Authentication Token* (selecting one of the two methods leads to additional " -"fields where you can enter your credentials/token)." +#: ../system/integrations/ldap/index.rst:30 +msgid "Before you continue, please note the following limitations." msgstr "" -#: ../system/objects/types.rst:265 -msgid "Search result list key" +#: ../system/integrations/ldap/index.rst:32 +msgid "Mapping / Synchronizing organizations is not possible" msgstr "" -#: ../system/objects/types.rst:261 +#: ../system/integrations/ldap/index.rst:36 msgid "" -"Defines the level in the JSON structure which provides the list with search " -"results. You can leave it empty, if the data is already provided as an " -"array. If you have to go deeper in the structure, you can provide a path " -"with ``.`` as separators, e.g. ``key.subkey.sub-sub-key``." +"You may want to consider using domain based assignments to overcome this " +"issue. Learn more on :doc:`/manage/organizations/index`." msgstr "" -#: ../system/objects/types.rst:271 -msgid "Search result value key" +#: ../system/integrations/ldap/index.rst:39 +msgid "" +"Zammad's LDAP sync is one way. Editing user settings or permissions may be " +"overwritten upon the next sync depending on your configuration." msgstr "" -#: ../system/objects/types.rst:268 -msgid "" -"Defines the attribute in the structure in which your external data source " -"provides the *value* for your data. An example would be a product *number*. " -"If you have to go deeper in the structure, you can provide a path with ``.`` " -"as separators, e.g. ``key.subkey.sub-sub-key``." +#: ../system/integrations/ldap/index.rst:41 +msgid "Nested groups are not supported." msgstr "" -#: ../system/objects/types.rst:277 -msgid "Search result label key" +#: ../system/integrations/ldap/index.rst:42 +msgid "Synchronizing user avatars from LDAP is not supported." msgstr "" -#: ../system/objects/types.rst:274 -msgid "" -"Defines the attribute in the structure in which your external data source " -"provides the *label* for your data. An example would be a product *name*. If " -"you have to go deeper in the structure, you can provide a path with ``.`` as " -"separators, e.g. ``key.subkey.sub-sub-key``." +#: ../system/integrations/ldap/index.rst:43 +msgid "Unlike user filters, group filters cannot be changed." msgstr "" -#: ../system/objects/types.rst:280 +#: ../system/integrations/ldap/index.rst:44 msgid "" -"In the preview area, you can find the following items (depending on your " -"configuration above):" +"When a user originates from an LDAP server, Zammad will try to verify the " +"login credentials against LDAP first - if this fails Zammad will check its " +"local database." msgstr "" -#: ../system/objects/types.rst:283 +#: ../system/integrations/ldap/index.rst:50 msgid "" -"**Error/hint message** (only if configuration is not complete): Zammad tells " -"you, if there is a problem and what you should change in your configuration." +"Users can have local passwords even if they're LDAP users! You can learn " +"more about user accounts in general on :doc:`/manage/users/index`." msgstr "" -#: ../system/objects/types.rst:286 +#: ../system/integrations/ldap/index.rst:54 msgid "" -"**Search field**: search for an existing attribute in the data source to get " -"a preview. This is required for the fields below to show up." +"When several LDAP sources contain the same user (meaning the same email " +"address), the user in question will be updated with every source configured. " +"*The last LDAP source will win.*" msgstr "" -#: ../system/objects/types.rst:288 +#: ../system/integrations/ldap/index.rst:58 msgid "" -"**Search result response** (only if configuration is not complete): here you " -"can find a syntax highlighted JSON preview of the response, based on the " -"search term you entered." +"This is subject to change with `Issue 4109 `_ in the future." msgstr "" -#: ../system/objects/types.rst:291 +#: ../system/integrations/ldap/index.rst:60 msgid "" -"**Search result list** (only if *search result list key* is properly set): " -"output of the structure under the configured *search result list key*." +"Synchronization statistics currently affect *all* configured LDAP sources. " +"This also applies for newly added or updated sources." msgstr "" -#: ../system/objects/types.rst:294 +#: ../system/integrations/ldap/index.rst:63 msgid "" -"**Preview table** (when fully configured): Zammad shows you a table which " -"includes the found items based on the search string (value, label and " -"optional link). You can use this preview if you don't have the complete data " -"structure of the external system in mind." +"This is subject to change with `Issue 4108 `_ in the future." msgstr "" -#: ../system/objects/types.rst:299 +#: ../system/integrations/ldap/index.rst:65 msgid "" -"An example of a configured external data source field from agent perspective:" +"Zammad currently has limited fallback server support. You can workaround " +"this by providing several sources - however, ensure to have the exact same " +"configuration on your fallback." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Screencast showing the search for a product in a ticket" +#: ../system/integrations/ldap/index.rst:69 +msgid "" +"This is subject to improve with `Issue 4107 `_ in the future." msgstr "" -#: ../system/objects/types.rst:307 -msgid "URL fields (Link-Template)" +#: ../system/integrations/ldap/index.rst:76 +msgid "" +"This section holds all requests Zammad handled for all LDAP sources. These " +"entries can either contain synchronization information or logins " +"(authentication attempts via Zammad's login interface)." msgstr "" -#: ../system/objects/types.rst:311 +#: ../system/integrations/ldap/index.rst:80 msgid "" -"This function is restricted to Text, Select and External data source types " -"only." +"By clicking on any request, Zammad will provide even more information. The " +"provided information can be useful when something does not work as expected." msgstr "" -#: ../system/objects/types.rst:314 +#: ../system/integrations/ldap/index.rst:85 msgid "" -"Link-Templates are an amazing way to dynamically generate URLs. They allow " -"you to integrate other systems better without having to manually copy data " -"from Zammad if possible." +"Especially a LDAP synchronization can cause many log entries. The web " +"interface will always limit the number of shown entries to the last 50 " +"entries." msgstr "" -#: ../system/objects/types.rst:320 +#: ../system/integrations/ldap/index.rst:None msgid "" -"Another great way of communicating with another system may be Zammad's :doc:" -"`Webhooks `." +"Screencast showing LDAP integration log entries and a detail view on\n" +"an entry." msgstr "" -#: ../system/objects/types.rst:323 -msgid "" -"After filling a link-template enabled field, an URL icon will appear on its " -"right. Clicking on the icon opens a new tab." +#: ../system/integrations/ldap/manage.rst:2 +msgid "Manage LDAP-Sources" msgstr "" -#: ../system/objects/types.rst:328 +#: ../system/integrations/ldap/manage.rst:6 msgid "" -"Even though Zammad displays the link template within object edit and create " -"screens, the function is optional. It's only active if you populate the " -"field." +"Please keep in mind all current limitations for the LDAP synchronization. " +"This will help to understand scopes of the following operations better." msgstr "" -#: ../system/objects/types.rst:333 -msgid "" -"What's the difference between URL and text fields with link template...?!" +#: ../system/integrations/ldap/manage.rst:65 +msgid "Add new source" msgstr "" -#: ../system/objects/types.rst:335 +#: ../system/integrations/ldap/manage.rst:10 msgid "" -"Both fields have different use cases. Use ``text`` type text fields when " -"ever you have a *static* url that requires dynamic parameters. If you " -"require a drag & drop like field that you can put in any URL, use ``URL`` " -"type text fields." +"Using the *New Source* button allows you to add new LDAP sources to your " +"installation. You're not limited in the number of sources, however, keep in " +"mind that many sources will also take more time to synchronize." msgstr "" -#: ../system/objects/types.rst:340 +#: ../system/integrations/ldap/manage.rst:14 msgid "" -"The difference is easier to spot when comparing the fields directly, below " -"screencast shows the result - the dynamic approach uses existing values in " -"the moment of updating to built the URL - e.g. ``https://google.com/search?" -"q=cookies`` - while the URL approach uses the actual URL of the field - e.g. " -"``https://zammad.com``." +"You can choose between different encryption types, namely *SSL* and " +"*STARTTLS* or none of them (\"*No SSL*\"). If you choose *SSL* or " +"*STARTTLS*, Zammad will display an additional *SSL verification* option that " +"allows you to disable the verification, e.g. for self-signed SSL " +"certificates. You can also tell Zammad to use a different port by appending " +"``:`` to your hostname/IP." msgstr "" -#: ../system/objects/types.rst:None +#: ../system/integrations/ldap/manage.rst:0 msgid "" -"Screencast showing the differents in between URL and text type fields with " -"actual values" +"Screenshot of configuring a new LDAP source with SSL encryption and SSL " +"verification" msgstr "" -#: ../system/objects/types.rst:352 -msgid "How does this work...?!" +#: ../system/integrations/ldap/manage.rst:26 +msgid "" +"New Source with SSL transport security enabled and certificate verification" msgstr "" -#: ../system/objects/types.rst:354 +#: ../system/integrations/ldap/manage.rst:30 msgid "" -"As an example, let's say you have an attribute called ``amazing_attribute`` " -"and you want to open a google search directly with the input from that field." +"Using an user filter can be a good idea if you only require a small subset " +"of your LDAP users in Zammad." msgstr "" -#: ../system/objects/types.rst:357 -msgid "" -"Providing the link-template field below allows you to do so: ``https://www." -"google.com/search?q=#{ticket.amazing_attribute}``" +#: ../system/integrations/ldap/manage.rst:42 +msgid "This especially affects inactive users" msgstr "" -#: ../system/objects/types.rst:362 +#: ../system/integrations/ldap/manage.rst:34 msgid "" -"You can use any :doc:`Zammad variable ` as long as it's " -"available in the moment you need it." +"As every LDAP behaves differently on which attributes and how they are set, " +"Zammad doesn't care about any flags." msgstr "" -#: ../system/objects/types.rst:365 +#: ../system/integrations/ldap/manage.rst:37 msgid "" -"As a result, you are redirected to Google with a search for the value of the " -"attribute, if you click on the button in the ticket (as you can see in the " -"screencast above)." +"Users that no longer are returned by your LDAP source will automatically be " +"set to inactive. Zammad assumes that the user was deactivated." msgstr "" -#: ../system/packages.rst:2 -msgid "Packages" +#: ../system/integrations/ldap/manage.rst:41 +msgid "" +"Users will never be removed automatically! If you want to remove obsolete " +"users, use :doc:`/system/data-privacy`." msgstr "" -#: ../system/packages.rst:4 -msgid "That's the package management-area." +#: ../system/integrations/ldap/manage.rst:46 +msgid "Active Directory admins" msgstr "" -#: ../system/packages.rst:6 -msgid "Individual add-ons for Zammad can be installed and managed here." +#: ../system/integrations/ldap/manage.rst:45 +msgid "" +"Active Directories are quite specific on how to filter for active users only " +"- please see the `Microsoft documentation `_ for more " +"information." msgstr "" -#: ../system/sessions.rst:2 -msgid "Sessions" +#: ../system/integrations/ldap/manage.rst:51 +msgid "" +"*Do not* manually write pathes of either LDAP attributes or groups. If " +"Zammad does not display them, it either cannot find them or you have a lot " +"of users that don't have the attributes populated." msgstr "" -#: ../system/sessions.rst:4 +#: ../system/integrations/ldap/manage.rst:55 msgid "" -"Sessions management allows reviewing currently known user sessions and " -"allows to end these. The session timeout is affected by :ref:" -"`security_session_timeout` configurations from security settings." +"Zammad will always only return attributes that are filled - this reduces the " +"returned list of attributes greatly." msgstr "" -#: ../system/sessions.rst:None -msgid "Screenshot showing Zammad's session management" +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing how to add a new LDAP source" msgstr "" -#: ../system/sessions.rst:13 -msgid "Zammad will provide the following information:" +#: ../system/integrations/ldap/manage.rst:63 +msgid "" +"If your LDAP system doesn't allow anonymous bind, Zammad detects it and " +"provides you an editable \"Base DN\" *text* field instead of a prefilled " +"*select* field." msgstr "" -#: ../system/sessions.rst:16 -msgid "" -"The user account this session entry belongs to. It can be normal if a user " -"has several sessions in the list. This can be due to changed browser " -"information or if you use e.g. single sign on methods where the user does " -"not use the log off button." +#: ../system/integrations/ldap/manage.rst:81 +msgid "Review or edit existing source" msgstr "" -#: ../system/sessions.rst:22 -msgid "Browser" +#: ../system/integrations/ldap/manage.rst:68 +msgid "" +"Clicking on a LDAP source will provide a configuration and mapping overview." msgstr "" -#: ../system/sessions.rst:22 -msgid "The browser agent communicated to Zammad." +#: ../system/integrations/ldap/manage.rst:70 +msgid "" +"If needed you can then use the *Change* button to update either the name, " +"active state or the whole configuration. If you're changing the whole " +"configuration, the dialogue will be identical to the source creation." msgstr "" -#: ../system/sessions.rst:40 -msgid "Location" +#: ../system/integrations/ldap/manage.rst:76 +msgid "" +"Did your LDAP server change? Different LDAP servers have different " +"structures and default attributes. This causes the LDAP synchronization to " +"likely fail. Consider removing the affected source and re-add it." msgstr "" -#: ../system/sessions.rst:25 -msgid "" -"The anticipated location based on the users IP address. Depending on the IP " -"address the result shown may differ. This option depends on :doc:`/settings/" -"system/services`." +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing the update of the source name." msgstr "" -#: ../system/sessions.rst:29 -msgid "The following information can be shown:" +#: ../system/integrations/ldap/manage.rst:89 +msgid "Re-arrange LDAP source's order" msgstr "" -#: ../system/sessions.rst:33 -msgid "IP address" +#: ../system/integrations/ldap/manage.rst:84 +msgid "" +"You can change the synchronization order for each source at any time. Zammad " +"will synchronize the sources from top to bottom." msgstr "" -#: ../system/sessions.rst:32 +#: ../system/integrations/ldap/manage.rst:0 msgid "" -"Either if you set *Geo IP services* to inactive or you're using internal IP " -"address which do not provide location information." +"Screencasting showing how to change the source order by using\n" +"drag and drop." msgstr "" -#: ../system/sessions.rst:40 -msgid "Country (or Country + City)" +#: ../system/integrations/ldap/manage.rst:101 +msgid "Remove a source" msgstr "" -#: ../system/sessions.rst:36 +#: ../system/integrations/ldap/manage.rst:92 msgid "" -"If *Geo IP services* is enabled only. Depends on how detailed the available " -"IP address information are." +"If you no longer need the a LDAP source or simply want to start over, you " +"can remove them at any time. This will not remove synchronized users, data " +"synchronized or permissions." msgstr "" -#: ../system/sessions.rst:39 +#: ../system/integrations/ldap/manage.rst:98 msgid "" -"Be aware that results can be inaccurate - this technically is not an error." +"Not sure if you'd need the source later on? Set the source to inactive " +"instead of removing it - see *Review or edit existing source* for more." msgstr "" -#: ../system/sessions.rst:43 -msgid "Age" +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing how to remove LDAP sources." msgstr "" -#: ../system/sessions.rst:43 -msgid "Provides the time when the session initially has been created." +#: ../system/integrations/pgp/index.rst:2 +msgid "PGP" msgstr "" -#: ../system/sessions.rst:50 -msgid "Update" +#: ../system/integrations/pgp/index.rst:7 +msgid "" +"Pretty Good Privacy (PGP) is another method for secure email communication. " +"With PGP, you can exchange **signed** and **encrypted** messages with others." msgstr "" -#: ../system/sessions.rst:46 -msgid "" -"Provides the time the user used this session to open Zammad. This timestamp " -"is only updated if the user e.g. reloads, not during normal work on tickets." +#: ../system/integrations/pgp/index.rst:13 +#: ../system/integrations/smime/index.rst:17 +msgid "Signing" msgstr "" -#: ../system/sessions.rst:50 -msgid "This timestamp is being used for the session timeout." +#: ../system/integrations/pgp/index.rst:11 +msgid "is a proof that a message hasn't been manipulated on its way." msgstr "" -#: ../system/sessions.rst:53 +#: ../system/integrations/pgp/index.rst:13 msgid "" -"Use the delete button to remove a single session on behalf of your user." +"In other words, it guarantees message **integrity** and **authenticity**." msgstr "" -#: ../system/subscription/billing.rst:2 -msgid "Billing" +#: ../system/integrations/pgp/index.rst:19 +#: ../system/integrations/smime/index.rst:22 +msgid "Encryption" msgstr "" -#: ../system/subscription/billing.rst:4 +#: ../system/integrations/pgp/index.rst:16 +#: ../system/integrations/smime/index.rst:20 msgid "" -"Within the billing tab you can control all billing relevant information like " -"invoices, billing address and the option to cancel your subscription." -msgstr "" - -#: ../system/subscription/billing.rst:33 -msgid "Billing information" +"scrambles a message so that it can only be unscrambled by the intended " +"recipient." msgstr "" -#: ../system/subscription/billing.rst:8 +#: ../system/integrations/pgp/index.rst:19 msgid "" -"All adjusted billing information below only affect future invoices. If your " -"invoice was issued wrong, please contact `our sales team `_." +"In other words, it guarantees message **privacy** and **data security**." msgstr "" -#: ../system/subscription/billing.rst:14 -msgid "Billing address" +#: ../system/integrations/pgp/index.rst:25 +msgid "Screenshot of ticket creation with encrypt and sign buttons" msgstr "" -#: ../system/subscription/billing.rst:13 +#: ../system/integrations/pgp/index.rst:25 msgid "" -"Provide your company address here, make sure to include the companies name " -"in case required. This address will be referenced on your invoice." +"Once PGP has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " +"appear in the ticket composer." msgstr "" -#: ../system/subscription/billing.rst:18 -msgid "VAT ID" +#: ../system/integrations/pgp/index.rst:28 +msgid "**Sign button not visible?**" msgstr "" -#: ../system/subscription/billing.rst:17 +#: ../system/integrations/pgp/index.rst:30 msgid "" -"Provide your VAT ID here. If applicable your invoice will not contain German " -"VAT. Please make sure to pay the VAT in your country as required." +"Please note that the signing of emails is based on the outgoing email " +"account. That means you have to choose a group with a sender email account, " +"which has a private key assigned." msgstr "" -#: ../system/subscription/billing.rst:27 -msgid "Billing Email Address" +#: ../system/integrations/pgp/index.rst:35 +msgid "Handling of Keys" msgstr "" -#: ../system/subscription/billing.rst:21 +#: ../system/integrations/pgp/index.rst:36 msgid "" -"Usually the instance owner (the person that registered the instance) will " -"receive all emails including the invoices. In case you have your own billing " -"department, you can provide their email address here." +"To use the PGP function, you have to enable the integration (PGP) by " +"switching the toggle to *enabled*." msgstr "" -#: ../system/subscription/billing.rst:25 +#: ../system/integrations/pgp/index.rst:39 msgid "" -"All billing relevant information will then be sent to this email address." +"You can add keys by clicking the *add key* button. The keys can be imported " +"from a file or you can paste the content of the key in the text box." msgstr "" -#: ../system/subscription/billing.rst:27 -msgid "Invoices are sent as attachment (PDF) to this email address." +#: ../system/integrations/pgp/index.rst:42 +msgid "**Which keys do I have to import?**" msgstr "" -#: ../system/subscription/billing.rst:29 +#: ../system/integrations/pgp/index.rst:44 msgid "" -"Don't forget to press the *Submit* button after you changed above settings." +"For **signing** *outgoing* emails, you have to import the private key of " +"your Zammad email account." msgstr "" -#: ../system/subscription/billing.rst:0 +#: ../system/integrations/pgp/index.rst:47 msgid "" -"Screenshot showing options for billing information within the\n" -"subscription menu" -msgstr "" - -#: ../system/subscription/billing.rst:70 -msgid "Payment history" +"For **encrypting** *outgoing* emails, you have to import the public key of " +"the customer's email account." msgstr "" -#: ../system/subscription/billing.rst:36 +#: ../system/integrations/pgp/index.rst:50 msgid "" -"The payment history will display a history of all paid invoices. At this " -"point you can also download these in case you need them again." +"For **verifying the signature** of signed *incoming* emails, you have to " +"import the public key of the customer." msgstr "" -#: ../system/subscription/billing.rst:41 +#: ../system/integrations/pgp/index.rst:53 msgid "" -"You will only find *paid* invoices here. Invoices that are to be billed are " -"not available before the payment is completed." +"For **decrypting** of encrypted *incoming* emails, you have to import the " +"private key of your Zammad email account." msgstr "" -#: ../system/subscription/billing.rst:46 -msgid "Date" +#: ../system/integrations/pgp/index.rst:57 +msgid "Import Keys From a File" msgstr "" -#: ../system/subscription/billing.rst:46 -msgid "Date of the invoice creation." +#: ../system/integrations/pgp/index.rst:58 +msgid "You can import keys from a file in the section **Upload key**:" msgstr "" -#: ../system/subscription/billing.rst:49 -msgid "Amount" +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of adding a key via file" msgstr "" -#: ../system/subscription/billing.rst:49 -msgid "Invoice total including VAT if applicable." +#: ../system/integrations/pgp/index.rst:64 +msgid "" +"**Supported file formats:** ASCII-armor as well as binary GPG format " +"(basically any GPG supported key format) is supported here." msgstr "" -#: ../system/subscription/billing.rst:52 -msgid "" -"Contains contract period (monthly or yearly) and hosted plan for the " -"subscription period in question." +#: ../system/integrations/pgp/index.rst:68 +msgid "Import Keys by Pasting the Content" msgstr "" -#: ../system/subscription/billing.rst:63 -msgid "Payment method / Service period" +#: ../system/integrations/pgp/index.rst:69 +msgid "You can also paste the key's content in the section **paste key**:" msgstr "" -#: ../system/subscription/billing.rst:56 -msgid "" -"Used bank account or credit card as well as the subscription period the " -"invoice is about." +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of adding a key via pasting" msgstr "" -#: ../system/subscription/billing.rst:61 +#: ../system/integrations/pgp/index.rst:75 msgid "" -"It might happen that the invoice date and subscription period differ. This " -"is nothing to worry about, the subscription periods will be accounted later " -"on." +"**Supported format:** Please note that only ASCII-armor is supported here." msgstr "" -#: ../system/subscription/billing.rst:67 -msgid "Receipt" +#: ../system/integrations/pgp/index.rst:78 +msgid "Deleting Keys" msgstr "" -#: ../system/subscription/billing.rst:66 +#: ../system/integrations/pgp/index.rst:79 msgid "" -"Use the arrow to download the invoice in question. You can download all " -"available invoices any time you need to here!" +"If you want to delete a specific key, you can do it by clicking on the menu " +"in the *actions* column and select **delete**:" msgstr "" -#: ../system/subscription/billing.rst:0 -msgid "Screenshot showing payment history of a hosted instance" +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of deleting a key" msgstr "" -#: ../system/subscription/billing.rst:94 -msgid "Do you want to cancel your subscription?" +#: ../system/integrations/pgp/index.rst:88 +msgid "Downloading Keys" msgstr "" -#: ../system/subscription/billing.rst:73 +#: ../system/integrations/pgp/index.rst:89 msgid "" -"In case you no longer want to use Zammad's SaaS, you can cancel your " -"subscription by using the red *Yes, please cancel my subscription* button." +"If you want to download your keys, you can do this as well via corresponding " +"action buttons. Depending on the key, you can choose wether you want to " +"download the private or the public key." msgstr "" -#: ../system/subscription/billing.rst:76 -msgid "" -"Your subscription will end the day after your trial or billing period ends." +#: ../system/integrations/pgp/index.rst:95 +#: ../system/integrations/smime/manage-certificates.rst:76 +msgid "Default Behavior" msgstr "" -#: ../system/subscription/billing.rst:80 +#: ../system/integrations/pgp/index.rst:96 msgid "" -"We will remind you about your cancelled subscription several times up front. " -"After the subscription ended all instance data will be removed. A restore " -"*is not* possible after that point!" +"Here you can adjust on per group basis, if *sign* and *encryption* is on or " +"off by default. Please be aware, that agents can always override the setting " +"for each individual article." msgstr "" -#: ../system/subscription/billing.rst:0 -msgid "Screencast showing how to cancel a subscription" +#: ../system/integrations/pgp/index.rst:None +msgid "Adjusting default behavior on per group basis" msgstr "" -#: ../system/subscription/billing.rst:87 -msgid "**😖 Cancelled by accident?**" +#: ../system/integrations/pgp/index.rst:107 +msgid "" +"Here you can see the last actions regarding signing and encryption and if " +"they were successful." msgstr "" -#: ../system/subscription/billing.rst:89 -msgid "" -"You can always undo the cancellation via the *Yes, undo the cancellation of " -"my subscription* button up to the last subscription day!" +#: ../system/integrations/pgp/index.rst:117 +msgid "**Sign button is not visible, but keys are imported.**" +msgstr "" + +#: ../system/integrations/pgp/index.rst:115 +msgid "Did you choose a group in the ticket?" msgstr "" -#: ../system/subscription/billing.rst:0 +#: ../system/integrations/pgp/index.rst:116 msgid "" -"Screenshot showing a red button to cancel the subscription\n" -"cancellation" +"Did you import a private key for the email adress, which is used for " +"outgoing emails in the group?" msgstr "" -#: ../system/subscription/index.rst:2 -msgid "Subscription (SaaS)" +#: ../system/integrations/pgp/index.rst:122 +msgid "**How to obtain keys?**" msgstr "" -#: ../system/subscription/index.rst:4 +#: ../system/integrations/pgp/index.rst:120 msgid "" -"The subscription settings page allows you to configure your instances " -"package and number of agents required." +"You can create them yourself! There are some good tutorials on the web on " +"how to create them. Providing keys to Zammad is a prerequisite to use the " +"PGP feature." msgstr "" -#: ../system/subscription/index.rst:9 -msgid "" -"This setting section is only available for Hosted setups. If you're looking " -"for on premise support contracts, please see the `Zammad pricing page " -"`_." +#: ../system/integrations/pgp/index.rst:127 +msgid "**It says a passphrase is needed, but I haven't got one.**" msgstr "" -#: ../system/subscription/index.rst:20 +#: ../system/integrations/pgp/index.rst:125 msgid "" -"The subscription section currently consists of two tabs: Plan & Billing. For " -"your overview we've divided those two tabs into independent sub pages:" +"If the key is secured with a passphrase, you have to provide it for the " +"import in Zammad. It is possible that keys may have an empty passphrase. " +"However, this is *not* recommended." msgstr "" -#: ../system/subscription/index.rst:25 -msgid ":doc:`💰 Subscription plan `" +#: ../system/integrations/pgp/index.rst:132 +msgid "**How do my customers get my new key?**" msgstr "" -#: ../system/subscription/index.rst:24 +#: ../system/integrations/pgp/index.rst:130 msgid "" -"Everything affecting your instance subscription functions like number of " -"agents, package and payment method." +"You have to provide your **public** key in advance. Your customer also has " +"to configure PGP in their email workflow and import your public key. The " +"other way round, you have to get the public key of your customer and have to " +"import it to Zammad." +msgstr "" + +#: ../system/integrations/slack.rst:2 +msgid "Slack" msgstr "" -#: ../system/subscription/index.rst:28 -msgid ":doc:`🧾 Subscription billing `" +#: ../system/integrations/slack.rst:4 +msgid "**⚠️ Deprecation warning ⚠️**" msgstr "" -#: ../system/subscription/index.rst:28 +#: ../system/integrations/slack.rst:6 msgid "" -"Everything regarding billing address, invoices and account cancellation." +"Zammad 7 will no longer support this dedicated Slack integration. It is " +"recommended to switch to :doc:`pre-defined webhooks ` instead. Existing Slack integrations should " +"be migrated manually before this feature is dropped." msgstr "" -#: ../system/subscription/index.rst:33 -msgid "FAQ" +#: ../system/integrations/slack.rst:14 +msgid "" +"In order to use this feature, please add a new Slack app to your Workspace. " +"The App you need is called ``Incoming WebHooks`` ." msgstr "" -#: ../system/subscription/index.rst:37 -msgid "I set up a trial account but am missing functions to test" +#: ../system/integrations/slack.rst:18 +msgid "Why Do I Need This Feature?" msgstr "" -#: ../system/subscription/index.rst:36 +#: ../system/integrations/slack.rst:20 msgid "" -"The trial instance is running within the professional package allowing up to " -"three agents." +"If you're already using Slack for your team communication, you'll love this " +"feature! Our Slack integration can push ticket notifications about the last " +"ticket article based on the following events:" msgstr "" -#: ../system/subscription/index.rst:40 -msgid "Can I change package within the trial?" +#: ../system/integrations/slack.rst:24 +msgid "on Ticket creation" msgstr "" -#: ../system/subscription/index.rst:40 -msgid "No. As soon as the package is changed the subscription begins." +#: ../system/integrations/slack.rst:25 +msgid "on Ticket updates" msgstr "" -#: ../system/subscription/index.rst:45 -msgid "What happens to my trial instance after the trial period ended?" +#: ../system/integrations/slack.rst:26 +msgid "on reached reminders" msgstr "" -#: ../system/subscription/index.rst:43 -msgid "" -"Your instance will automatically be canceled for you. Please see *What " -"happens to my instance after it has been canceled?* for more." +#: ../system/integrations/slack.rst:27 +msgid "a Ticket has escalated" msgstr "" -#: ../system/subscription/index.rst:58 -msgid "What happens to my instance after it has been canceled?" +#: ../system/integrations/slack.rst:28 +msgid "a Ticket is going to escalate" msgstr "" -#: ../system/subscription/index.rst:48 -msgid "That depends slightly on your instance state:" +#: ../system/integrations/slack.rst:30 +msgid "" +"Zammad will provide the Ticket title, a direct link to the Ticket, the event " +"type (creation, updated, escalation), the customer, time and the last " +"article that has triggered the notification." msgstr "" -#: ../system/subscription/index.rst:54 -msgid "Trial instance" +#: ../system/integrations/slack.rst:34 +msgid "" +"This will give you further options, as you can see e.g. escalating tickets " +"that are assigned to an agent that's e.g. absent. You can interact faster, " +"as you might see problems earlier (or even before the problem gets one)." msgstr "" -#: ../system/subscription/index.rst:51 +#: ../system/integrations/slack.rst:38 msgid "" -"If you're still on trial, we will ice your instance and remind you once " -"again about your instance. We then will wait some days and remove your " -"instance from our system. This is the last time we will inform you by Email." +"If needed and wanted, you can even discuss directly about the topic before " +"sending an answer to the customer. Another possible use case would be a " +"agent monitoring new agents and their answers to tickets." msgstr "" -#: ../system/subscription/index.rst:58 -msgid "Paid instance" +#: ../system/integrations/slack.rst:44 +msgid "Configure the Integration" msgstr "" -#: ../system/subscription/index.rst:57 +#: ../system/integrations/slack.rst:46 msgid "" -"If you're a paying customer and canceled your subscription, the instance " -"removal will take place the day after your last subscription day." +"First of all, please go to your slack workspace - go to administration => " +"Manage Apps. If you don't have an app yet, you can simply add a new one - " +"just search for ``Incoming WebHooks`` and customize the app to your needs." msgstr "" -#: ../system/subscription/index.rst:60 -msgid "Can removed instances be restored?" +#: ../system/integrations/slack.rst:50 +msgid "" +"Choose (or create) the channel Zammad should post it's information to and " +"press on \"Add Incoming WebHooks integration\". If you're ready, copy the " +"provided WebHook URL and go to your Zammad installation." msgstr "" -#: ../system/subscription/index.rst:61 -msgid "No. Once your instance has been removed, a restoration is not possible." +#: ../system/integrations/slack.rst:56 +msgid "" +"You need administrative rights on the Slack Workspace. The link to the app " +"directory is normally ``https://[workspace-name].slack.com/apps`` ." msgstr "" -#: ../system/subscription/plan.rst:2 ../system/subscription/plan.rst:38 -msgid "Plan" +#: ../system/integrations/slack.rst:63 +msgid "" +"To configure the slack integration, log in to Zammad and go to Integrations " +"(System) => Slack in the admin panel." msgstr "" -#: ../system/subscription/plan.rst:16 -msgid "Subscription" +#: ../system/integrations/slack.rst:66 +msgid "" +"Here you can choose on what evens Zammad should post information about a " +"ticket to your Slack channel. Next you need to device what groups shall be " +"affected by this, as anybody with access to that specific Slack channel can " +"read at least parts of the ticket this might be a privacy issue, if you " +"select the wrong groups. The username is simply the name that Zammad uses as " +"display name inside the Slack chat. The channel defines the Slack channel " +"the information is being posted in. As last option, you can set a custom " +"icon for posting to slack." msgstr "" -#: ../system/subscription/plan.rst:5 +#: ../system/integrations/slack.rst:74 msgid "" -"On the top of the subscription summary you'll find the number of used and " -"available (booked) agent seats. By using the *see more* link you can also " -"expand an agent list to see the currently configured active agents. This " -"list *does not* count accounts with admin permissions only." +"When you're ready, just hit \"Submit\" and enable the integration. Zammad " +"will now post new ticket information based on the trigger you chose. Below " +"the options you have the recent log that shows the latest requests to Slack " +"for debugging if needed." msgstr "" -#: ../system/subscription/plan.rst:0 +#: ../system/integrations/slack.rst:81 msgid "" -"Within subscription you can always see how many agents are still\n" -"available to add and who uses the seats." +"If you leave the Icon URL empty, Zammad will use the Zammad logo instead. " +"The icon should be a square PNG file." msgstr "" -#: ../system/subscription/plan.rst:14 +#: ../system/integrations/slack.rst:90 msgid "" -"Learn more on how to manage your agents in general :doc:`here `." +"The following figure shows how it will look if you choose to receive updates " +"on created and updated tickets. On every post Zammad sends to the Slack " +"channel, you can create new threads to discuss about the new article." msgstr "" -#: ../system/subscription/plan.rst:19 +#: ../system/integrations/slack.rst:96 msgid "" -"This section gives you an overview of the available plans and their " -"functions / limits. If you require a more detailed table, check our " -"`detailed pricing table `_ for more." +"If you just want to keep track of soon escalating or already escalated " +"tickets, it will look the the following figure. Zammad changes the color in " +"front of the post so you can easily see the state of the ticket." msgstr "" -#: ../system/subscription/plan.rst:23 +#: ../system/integrations/slack.rst:102 msgid "" -"Your selection in this step will decide on the base agent price and e.g. " -"agent limits that might apply in the summary step." +"If you change the state, Zammad will also put information on what state the " +"ticket gets and (if pending state) the date until it pends. You'll also " +"recognize the color codes in front of posts on slack, as they are exact the " +"same the ticket state colors you'll see in Zammad!" msgstr "" -#: ../system/subscription/plan.rst:26 -msgid "" -"The green *Selected* button will also tell you what plan you're currently in." +#: ../system/integrations/smime/index.rst:2 +msgid "S/MIME" msgstr "" -#: ../system/subscription/plan.rst:30 +#: ../system/integrations/smime/index.rst:11 msgid "" -"Trial instances are running at Professional with 3 agents. The plan cannot " -"be changed during the trial for technical reasons, if you require more " -"agents for testing, please contact `our sales team `_ with a reason for the raise request." +"S/MIME is the most widely-supported method for secure email communication. " +"With S/MIME, you can exchange **signed** and **encrypted** messages with " +"others." msgstr "" -#: ../system/subscription/plan.rst:0 +#: ../system/integrations/smime/index.rst:15 msgid "" -"Screenshot showing three available packages for a hosted Zammad\n" -"instance" +"is proof that a message hasn't been tampered with or sent by an impersonator." msgstr "" -#: ../system/subscription/plan.rst:83 -msgid "Summary" +#: ../system/integrations/smime/index.rst:17 +msgid "" +"In other words, it guarantees a message's **integrity** and **authenticity**." msgstr "" -#: ../system/subscription/plan.rst:41 -msgid "" -"In this section you can adjust the settings of the previous selected plan." +#: ../system/integrations/smime/index.rst:22 +msgid "In other words, it guarantees **privacy** and **data security**." msgstr "" -#: ../system/subscription/plan.rst:45 -msgid "" -"Note that upgrading (more agents, higher package) is always possible, " -"however, downgrading will only happen when your billing period renews." +#: ../system/integrations/smime/index.rst:28 +msgid "Screencast demo of S/MIME features for both new tickets and replies" msgstr "" -#: ../system/subscription/plan.rst:49 +#: ../system/integrations/smime/index.rst:28 msgid "" -"Upgrading resets your billing period and existing credit will be deducted " -"from the new total." +"Once S/MIME has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " +"appear in the ticket composer." msgstr "" -#: ../system/subscription/plan.rst:58 -msgid "Billing cycle" +#: ../system/integrations/smime/index.rst:32 +msgid ":doc:`🔪 Prerequisites `" msgstr "" -#: ../system/subscription/plan.rst:53 +#: ../system/integrations/smime/index.rst:31 msgid "" -"You can choose between either monthly or yearly billing. The price per agent " -"will be cheaper if you decide for yearly billing." +"New to S/MIME? This section helps you to find certificate providers and " +"points out Limitations." msgstr "" -#: ../system/subscription/plan.rst:56 -msgid "" -"If you're still trying out things and are unsure of the right package for " -"your instance, you may want to choose monthly first and then upgrade to " -"yearly when you're sure." +#: ../system/integrations/smime/index.rst:35 +msgid ":doc:`📝 Manage Certificates `" msgstr "" -#: ../system/subscription/plan.rst:66 -msgid "Plan: (Starter|Professional|Plus) - Agents" +#: ../system/integrations/smime/index.rst:35 +msgid "Add and download certificates; configure group default behaviors." msgstr "" -#: ../system/subscription/plan.rst:61 -msgid "Choose the number of agents you require for your instance." +#: ../system/integrations/smime/index.rst:38 +msgid ":doc:`😦 Troubleshooting `" msgstr "" -#: ../system/subscription/plan.rst:63 -msgid "" -"Keep in mind that some packages may have agent limits. Depending on the " -"previous chosen package, you won't be able to exceed specific agent numbers. " -"Also note that setting less agents than currently configured is not possible." +#: ../system/integrations/smime/index.rst:38 +msgid "Took a wrong turn? About recent logs and common issues." msgstr "" -#: ../system/subscription/plan.rst:69 -msgid "Total" +#: ../system/integrations/smime/index.rst:43 +msgid "" +"For more details on how S/MIME integration works on the agent side, see the :" +"user-docs:`user docs `." msgstr "" -#: ../system/subscription/plan.rst:69 -msgid "This will be the net total you're going to be billed." +#: ../system/integrations/smime/manage-certificates.rst:2 +msgid "Manage Certificates" msgstr "" -#: ../system/subscription/plan.rst:71 +#: ../system/integrations/smime/manage-certificates.rst:4 msgid "" -"By using the *Update subscription* button, the instance package will be " -"adjusted immediately. If you didn't provide a payment method yet, Zammad " -"will request you to provide one at this point." +"S/MIME is **disabled by default**. Enable it to start adding certificates." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:10 +msgid "Dialogue to add new certificates or private keys" msgstr "" -#: ../system/subscription/plan.rst:77 +#: ../system/integrations/smime/manage-certificates.rst:10 msgid "" -"In case you're still within the trial period, this means that the trial will " -"be over immediately!" +"Manage certificates in the Admin Panel under **System > Integrations > S/" +"MIME**. Certificates may be pasted in as plain text or uploaded from a file." msgstr "" -#: ../system/subscription/plan.rst:80 -msgid "Down- or upgrading during the trial period *is not* possible." +#: ../system/integrations/smime/manage-certificates.rst:14 +msgid "Add Certificate Data" msgstr "" -#: ../system/subscription/plan.rst:0 -msgid "Screenshot showing payment options and a pricing summary" +#: ../system/integrations/smime/manage-certificates.rst:36 +msgid "Add Certificate" msgstr "" -#: ../system/subscription/plan.rst:99 -msgid "Payment method" +#: ../system/integrations/smime/manage-certificates.rst:17 +msgid "" +"Import public-key certificates for both your own organization and your " +"contacts." msgstr "" -#: ../system/subscription/plan.rst:86 -msgid "You can pay via credit card or SEPA mandate." +#: ../system/integrations/smime/manage-certificates.rst:19 +msgid "" +"You can also add a bunch of certificates in one go by providing a single " +"file with all relevant certificates." msgstr "" -#: ../system/subscription/plan.rst:91 -msgid "Credit card" +#: ../system/integrations/smime/manage-certificates.rst:22 +msgid "🕵️ **ALWAYS verify certificates in-person or over the phone!**" msgstr "" -#: ../system/subscription/plan.rst:89 +#: ../system/integrations/smime/manage-certificates.rst:24 msgid "" -"Simply follow the dialogue by clicking *authorize* and confirm -if required " -"by your bank- your consent to Zammad using your card for the payments." +"The whole point of signatures is to alert you when someone is trying to " +"pretend to be someone they're not. Never accept a certificate from someone " +"online without verifying it first." msgstr "" -#: ../system/subscription/plan.rst:95 -msgid "SEPA" +#: ../system/integrations/smime/manage-certificates.rst:28 +msgid "📇 **What about trusted certificate authorities?**" msgstr "" -#: ../system/subscription/plan.rst:94 +#: ../system/integrations/smime/manage-certificates.rst:30 msgid "" -"Provide the requested information of the bank account holder and update if " -"you're ready. You'll then receive an email with the SEPA mandate." +"In some cases (e.g. when dealing with large enterprises), you may be given a " +"certificate for an entire CA, rather than a single contact. Add it here to " +"trust *all* certificates issued by that CA." msgstr "" -#: ../system/subscription/plan.rst:97 +#: ../system/integrations/smime/manage-certificates.rst:35 msgid "" -"Technically there's also the possibility to pay via invoice, however - this " -"method only applies to a fairly low number of instances. Please contact `our " -"sales team `_ for more information." +"Commercial CAs can usually be verified online. Zammad does not include a " +"list of built-in, trusted CAs." msgstr "" -#: ../system/translations.rst:2 -msgid "Translations" +#: ../system/integrations/smime/manage-certificates.rst:57 +msgid "Add Private Key" msgstr "" -#: ../system/translations.rst:4 +#: ../system/integrations/smime/manage-certificates.rst:39 msgid "" -"Translations of Zammad are processed centrally in our `Weblate instance " -"`_. This allows non-developers to review " -"and update translation texts of the language they actually speak." +"Once you've added a public-key certificate, you can import its matching " +"private key." msgstr "" -#: ../system/translations.rst:9 +#: ../system/integrations/smime/manage-certificates.rst:42 msgid "" -"Your language is in an incomplete translation state or has typos? Please " -"consider helping us in sorting this out! All you need is either a GitHub " -"account or to register directly in our instance." +"Private keys are for **your own organization only**; never ask your contacts " +"for their private keys." msgstr "" -#: ../system/translations.rst:13 +#: ../system/integrations/smime/manage-certificates.rst:0 msgid "" -"Did you know? This is also where the documentation translations are handled. " -"🤓" +"S/MIME integration showing configured certificates and possible issues with " +"Logging" msgstr "" -#: ../system/translations.rst:15 +#: ../system/integrations/smime/manage-certificates.rst:50 msgid "" -"Have a look in our :docs:`contribution section ` in the system documentation to get started!" +"A note is displayed on certificates with a matching private key (see line 2)." msgstr "" -#: ../system/translations.rst:20 -msgid "Local Translations" +#: ../system/integrations/smime/manage-certificates.rst:52 +msgid "📤 **Certificates and private keys must be uploaded separately.**" msgstr "" -#: ../system/translations.rst:22 +#: ../system/integrations/smime/manage-certificates.rst:54 msgid "" -"Apart from these system translations, there's still local translations you " -"can manage. This is relevant if you added custom objects that require " -"translations or even custom states and priorities." +"If your certificate and private key are bundled together in the same file or " +"PEM block, import it twice (once using each button)." msgstr "" -#: ../system/translations.rst:None -msgid "Translation management screen within the admin menu" +#: ../system/integrations/smime/manage-certificates.rst:57 +msgid "Please note that bulk imports of private keys are not possible." msgstr "" -#: ../system/translations.rst:31 -msgid "Updating Translations" +#: ../system/integrations/smime/manage-certificates.rst:60 +msgid "Download Certificate Data" msgstr "" -#: ../system/translations.rst:33 +#: ../system/integrations/smime/manage-certificates.rst:62 msgid "" -"Because of how Zammad ships translations, the only way to update the system " -"translations is to update your Zammad installation. The benefit of this is " -"that you no longer need internet access during a Zammad upgrade as the " -"package has everything it requires already." +"You can download the earlier provided certificates and private keys at any " +"time from your Zammad instance." msgstr "" -#: ../system/translations.rst:39 -msgid "Translation of Custom Objects" +#: ../system/integrations/smime/manage-certificates.rst:65 +msgid "" +"Please note that passphrase-protected private keys stay protected and when " +"you download them, you have to know the passphrase to use them after " +"downloading." msgstr "" -#: ../system/translations.rst:41 -msgid "" -"No problem at all! You can customize any translation locally, even if it is " -"not initially provided by the system." +#: ../system/integrations/smime/manage-certificates.rst:73 +msgid "Dialogue to download certificates or private keys" msgstr "" -#: ../system/translations.rst:44 +#: ../system/integrations/smime/manage-certificates.rst:73 +msgid "Download stored certificates and their keys" +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:78 msgid "" -"Translation is supported for a broad number of features, including but not " -"limited to custom:" +"The ticket composer will set all outgoing messages to **signed and " +"encrypted** by default (assuming the required certificates exist)." msgstr "" -#: ../system/translations.rst:47 -msgid "Object Attributes" +#: ../system/integrations/smime/manage-certificates.rst:82 +msgid "These defaults can be modified on a per-group basis:" msgstr "" -#: ../system/translations.rst:48 -msgid "Ticket Macros" +#: ../system/integrations/smime/manage-certificates.rst:None +msgid "Zammad allowing to choose the default behavior on per group basis" msgstr "" -#: ../system/translations.rst:49 -msgid "Ticket Overviews" +#: ../system/integrations/smime/manage-certificates.rst:89 +msgid "" +"Of course, agents can always manually change these settings on each email " +"they send out." msgstr "" -#: ../system/translations.rst:50 -msgid "Ticket Priorities" +#: ../system/integrations/smime/prerequisites.rst:4 +msgid "A certificate *and* private key for your own organization" msgstr "" -#: ../system/translations.rst:51 -msgid "Ticket States" +#: ../system/integrations/smime/prerequisites.rst:6 +msgid "" +"(Use this to ✒️ **sign outgoing messages** and 🔓 **decrypt incoming " +"messages**.)" msgstr "" -#: ../system/translations.rst:54 -msgid "Customizing Translations" +#: ../system/integrations/smime/prerequisites.rst:9 +msgid "" +"Certificates belonging your contacts, or their issuing certificate authority " +"(CA)" msgstr "" -#: ../system/translations.rst:56 +#: ../system/integrations/smime/prerequisites.rst:11 msgid "" -"Within the translation screen, simply click on the **New Translation** " -"button." +"(Use these to ✅ **verify incoming message signatures** and 🔒 **encrypt " +"outgoing messages**.)" msgstr "" -#: ../system/translations.rst:None -msgid "New translation dialog" +#: ../system/integrations/smime/prerequisites.rst:14 +msgid "🙋 **I'm new to S/MIME. Where can I get a certificate?**" msgstr "" -#: ../system/translations.rst:62 +#: ../system/integrations/smime/prerequisites.rst:16 msgid "" -"In the dialog you can immediately enter the exact translation source (if you " -"know it) and your custom translation text for it and click **Submit**." +"The easiest way to get certificates is to buy an annual subscription through " +"a commercial CA, such as:" msgstr "" -#: ../system/translations.rst:65 +#: ../system/integrations/smime/prerequisites.rst:19 msgid "" -"Alternatively, try to search for translation suggestions in the list below. " -"Selecting an item from the list will pre-fill the translation source for you " -"and then you can just enter your custom translation." +"`Sectigo (formerly Comodo) `_" msgstr "" -#: ../system/translations.rst:69 -msgid "" -"The target language will always default to your current language selection. " -"If you need to translate for a different language, simply change the " -"selection before submitting." +#: ../system/integrations/smime/prerequisites.rst:20 +msgid "`Secorio `_" msgstr "" -#: ../system/translations.rst:73 -msgid "" -"All your custom translations will show up in the overview table when added. " -"And they will even persist across Zammad updates!" +#: ../system/integrations/smime/prerequisites.rst:21 +msgid "`GlobalSign `_" msgstr "" -#: ../system/translations.rst:76 -msgid "" -"Make sure to reload your browser if a translated string is not displayed." +#: ../system/integrations/smime/prerequisites.rst:23 +msgid "(Zammad is not affiliated with these CAs in any way.)" msgstr "" -#: ../system/translations.rst:80 -msgid "Reverting to Original Translations" +#: ../system/integrations/smime/prerequisites.rst:25 +msgid "" +"You can also generate your own self-signed certificates, but the process is " +"complicated and usually 🙅 **involves extra work for your contacts**." msgstr "" -#: ../system/translations.rst:82 +#: ../system/integrations/smime/prerequisites.rst:29 msgid "" -"If you want to revert a custom translation to original text, simply use the " -"appropriate action within the row of the overview table." +"Bear in mind that 🤝 **S/MIME only works if the other party is using it, too." +"**" msgstr "" -#: ../system/translations.rst:85 +#: ../system/integrations/smime/prerequisites.rst:32 +msgid "Certificate and Private Key Checks on Upload" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:34 msgid "" -"Depending on the type of the translation source, the action has a slightly " -"different name:" +"The certificate and public key validation is based on the ``X509v3`` " +"extensions." msgstr "" -#: ../system/translations.rst:88 -msgid "**Reset** for customized system translations" +#: ../system/integrations/smime/prerequisites.rst:49 +msgid "Uploading a *client certificate*?" msgstr "" -#: ../system/translations.rst:89 -msgid "**Remove** for customized local translations" +#: ../system/integrations/smime/prerequisites.rst:41 +msgid "The following attributes are required then:" msgstr "" -#: ../system/translations.rst:91 -msgid "" -"In both cases, the action will remove the customized translation after a " -"confirmation." +#: ../system/integrations/smime/prerequisites.rst:39 +msgid "Subject Alternative Name (at least one email address has to be present)" msgstr "" -#: ../system/translations.rst:None -msgid "Screenshot showing the location of the Remove action" +#: ../system/integrations/smime/prerequisites.rst:40 +msgid "Key Usage (``Digital Signature`` and/or ``Key Encipherment``)" msgstr "" -#: ../system/translations.rst:99 -msgid "Inline Translations" +#: ../system/integrations/smime/prerequisites.rst:41 +msgid "Public key algorithm (either ``RSA`` or ``EC``)" msgstr "" -#: ../system/translations.rst:101 +#: ../system/integrations/smime/prerequisites.rst:43 msgid "" -"If you prefer a more hands-on approach, you can activate the inline or on-" -"screen translation feature by pressing ``ctrl`` + ``alt`` + ``t`` at any " -"time and on any screen." +"The Extended Key Usage attribute is optional. If the certificate provides " +"the named attribute, than it must contain the value ``E-mail Protection``." msgstr "" -#: ../system/translations.rst:105 +#: ../system/integrations/smime/prerequisites.rst:46 msgid "" -"All customizable translation texts will be highlighted for you on the " -"screen. Just click into the highlighted area and update the text in place." +"Please note that any usable email adress has to be prefixed with ``email:`` " +"or ``rfc822:``." msgstr "" -#: ../system/translations.rst:None -msgid "Inline translation mode activated for the Overview screen" +#: ../system/integrations/smime/prerequisites.rst:49 +msgid "The named public key algorithms are mandatory for private keys as well." msgstr "" -#: ../system/translations.rst:112 +#: ../system/integrations/smime/prerequisites.rst:54 +msgid "Uploading a *CA certificate*?" +msgstr "" + +#: ../system/integrations/smime/prerequisites.rst:52 msgid "" -"When finished editing, simply press ``ctrl`` + ``alt`` + ``t`` again to " -"deactivate." +"In the case of an uploaded CA certificate, providing the value ``CA:TRUE`` " +"in the attribute *Basic Contstraints*, the previously mentioned attributes " +"are not verified." msgstr "" -#: ../system/translations.rst:117 +#: ../system/integrations/smime/prerequisites.rst:56 msgid "" -"Even though it's available on any screen, the inline translation feature " -"requires admin permissions. It works only for the current language " -"selection. If you need to translate a different language, first change the " -"language in your :user-docs:`profile settings `." +"In general, the usage of any expired (``Not After``) or not yet valid (``Not " +"Before``) certificate is denied for outgoing emails." msgstr "" -#: ../system/variables.rst:2 -msgid "Variables" +#: ../system/integrations/smime/prerequisites.rst:59 +msgid "Example certificate:" msgstr "" -#: ../system/variables.rst:4 +#: ../system/integrations/smime/prerequisites.rst:85 msgid "" -"Please note that this is just an overview of available variables. It might " -"be incomplete or variables might not be available within some functions. If " -"you're missing variables or are not sure if something is not working as " -"expected, feel free to ask over at the `Community `_." +"Please note that Zammad will distrust senders by default. This means that " +"you're always required to provide certificate data, no matter if for signing " +"or encrypting." msgstr "" -#: ../system/variables.rst:10 -msgid "" -"Variables can be called by typing ``::`` (just like text modules in the " -"frontend), as long as you're in a supported text field within the backend. " -"Zammad will display all variables being available within this context and " -"replace it to the variable as soon as you selected an entry." +#: ../system/integrations/smime/prerequisites.rst:89 +msgid "This is by design and can't be adjusted." msgstr "" -#: ../system/variables.rst:15 +#: ../system/integrations/smime/troubleshooting.rst:4 msgid "" -"You have an empty field which you referenced and it appears as ``-``? That's " -"currently working as designed - you might want to ensure that these fields " -"always have a value." +"All of the system's latest S/MIME activity is displayed in the **Recent " +"Logs** section." msgstr "" -#: ../system/variables.rst:20 -msgid "Variable Categories" +#: ../system/integrations/smime/troubleshooting.rst:11 +msgid "Sample entries of in- and outgoing S/MIME related emails." msgstr "" -#: ../system/variables.rst:31 -msgid "Wait, What About Custom Objects?" +#: ../system/integrations/smime/troubleshooting.rst:11 +msgid "" +"Logs report the status and details of all mail, both incoming and outgoing, " +"that used signing/verification or encryption/decryption." msgstr "" -#: ../system/variables.rst:33 +#: ../system/integrations/smime/troubleshooting.rst:14 msgid "" -"Good point! Of course, we can't predict what objects you might create, but " -"we can give you a hint on how to put the puzzle together to get your custom " -"values." +"This log does **not** include email sent by :doc:`triggers ` or the :doc:`scheduler `. For those, check your " +"``production.log``." +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:20 +msgid "Common Issues" +msgstr "" + +#: ../system/integrations/smime/troubleshooting.rst:30 +msgid "I received a signed/encrypted email before I set up S/MIME integration" msgstr "" -#: ../system/variables.rst:36 +#: ../system/integrations/smime/troubleshooting.rst:23 msgid "" -"For this, we'll talk about the inner part of the variable (so everything " -"within ``#{}``), please put the outer part around to have a valid variable. " -"The first part of the variable name consist of the object type. Currently " -"these are:" +"No problem. Once S/MIME has been enabled and the appropriate certificates " +"have been added, agents will be prompted to retry verification/decryption on " +"matching emails." msgstr "" -#: ../system/variables.rst:41 -msgid "Ticket (``ticket``)" +#: ../system/integrations/smime/troubleshooting.rst:0 +msgid "Screenshot of user prompt to retry decryption" msgstr "" -#: ../system/variables.rst:42 -msgid "User (``user``)" +#: ../system/integrations/smime/troubleshooting.rst:38 +msgid "The 🔒 **Encrypt** button is disabled" msgstr "" -#: ../system/variables.rst:43 -msgid "Organization (``organization``)" +#: ../system/integrations/smime/troubleshooting.rst:33 +msgid "Have you added the recipient's certificate?" msgstr "" -#: ../system/variables.rst:44 -msgid "Group (``group``)" +#: ../system/integrations/smime/troubleshooting.rst:34 +msgid "Are you sure the recipient's certificate is valid?" msgstr "" -#: ../system/variables.rst:46 -msgid "" -"The second part is the name of the object. This is the name you define " -"during object creation and can be found within the object menu at any time. " -"The first and second part of a variable is divided by a point, e.g.: " -"``ticket.number`` which will in total be ``#{ticket.number}``." +#: ../system/integrations/smime/troubleshooting.rst:35 +msgid "Have you checked your ``production.log`` for more details?" msgstr "" -#: ../system/variables.rst:51 +#: ../system/integrations/smime/troubleshooting.rst:37 msgid "" -"Now, in some situations it's possible that you'll need to use a third part. " -"The best example for such a situation would be a ``select`` or ``tree-" -"select`` field which will by default return the key value, not it's display " -"name. For this, just extend your variable with ``.value``. This will result " -"in ``#{ticket.select.value}``." +"If encryption doesn't work in the composer, it won't work in :doc:`triggers " +"` or the :doc:`scheduler ` either!" msgstr "" -#: ../system/variables.rst:60 -msgid "Using Translated Variables" +#: ../system/integrations/smime/troubleshooting.rst:42 +msgid "The ✅ **Sign** button is disabled" msgstr "" -#: ../system/variables.rst:62 +#: ../system/integrations/smime/troubleshooting.rst:41 msgid "" -"If you want to use a translated variable in triggers or schedulers, you can " -"extend the placeholder like this: ``#{t(ticket.state.name)}``. The ``t`` " -"tells Zammad to search for fitting translated strings. The used output " -"language is based on the system language of Zammad which you can set in the " -"admin panel under :doc:`/settings/branding` or based on the selected locale " -"in the trigger/scheduler edit dialog." +"Have you added **both the certificate and private key** for your " +"organization?" msgstr "" -#: ../system/variables.rst:69 +#: ../system/integrations/smime/troubleshooting.rst:42 msgid "" -"A possible use-case: you want to send your customers updates on tickets via " -"trigger or scheduler which should include the state of the ticket. Using the " -"default ``#{ticket.state.name}`` (without the translation flag ``t()``) " -"would lead to the output of the original (english) name of the state." +"Does the email address on the certificate match the email address of the " +"agent/group composing the email?" msgstr "" -#: ../system/variables.rst:75 -msgid "Date and Time Formatting" +#: ../system/integrations/smime/troubleshooting.rst:45 +msgid "Error: “Fingerprint already taken”" msgstr "" -#: ../system/variables.rst:77 -msgid "" -"The system (trigger/scheduler selected) locale and timezone predefines a " -"default format of date and timestamp. This format is customizable by using " -"the ``dt()`` method." +#: ../system/integrations/smime/troubleshooting.rst:45 +msgid "Are you sure you haven't added this certificate already?" msgstr "" -#: ../system/variables.rst:79 -msgid "The method arguments are as follows:" +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Error: “❌ invalid byte sequence in UTF-8”" msgstr "" -#: ../system/variables.rst:81 -msgid "The date or timestamp variable you want to format." +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Please ensure to provide PEM formatted certificate and keys." msgstr "" -#: ../system/variables.rst:82 -msgid "The output format string." +#: ../system/integrations/smime/troubleshooting.rst:49 +msgid "Did you check if the provided file is a valid certificate or key?" msgstr "" -#: ../system/variables.rst:83 -msgid "The timezone to apply (optional)." +#: ../system/integrations/zabbix.rst:2 +msgid "Zabbix Integration" msgstr "" -#: ../system/variables.rst:86 +#: ../system/integrations/zabbix.rst:5 msgid "" -"``#{dt(ticket.updated_at, \"%A %Y-%m-%d %H:%M in the office\", \"Europe/" -"Berlin\")}``" +"This guide describes how to integrate your Zabbix 5.4 installation with " +"Zammad using the Zabbix webhook feature. This guide will provide " +"instructions on setting up a media type, a user and an action in Zabbix." msgstr "" -#: ../system/variables.rst:87 -msgid "Monday, 2024-03-18 15:31 in the office" +#: ../system/integrations/zabbix.rst:12 +msgid "Zammad with enabled HTTP Token Authentication" msgstr "" -#: ../system/variables.rst:89 -msgid "" -"If you want to use our example, make sure to paste the string above without " -"formatting (``CTRL+Shift+v``), otherwise it won't work." +#: ../system/integrations/zabbix.rst:13 +msgid "Zabbix version 5.4 or higher" msgstr "" -#: ../system/variables.rst:93 -msgid "The following table lists available format directives:" +#: ../system/integrations/zabbix.rst:16 +msgid "Setting up a Zammad" msgstr "" -#: ../system/variables.rst:99 -msgid "Parameter" +#: ../system/integrations/zabbix.rst:18 +msgid "Enable **API Token Access** in Settings > System > API." msgstr "" -#: ../system/variables.rst:102 -msgid "``%Y``" +#: ../system/integrations/zabbix.rst:20 +msgid "" +"Create a **new user** for a Zabbix alerter with an **email address** and " +"create a personal user token with **ticket.agent** permissions." msgstr "" -#: ../system/variables.rst:103 -msgid "Year with 4 digits" +#: ../system/integrations/zabbix.rst:24 +msgid "Zabbix Webhook Configuration" msgstr "" -#: ../system/variables.rst:104 -msgid "Use ``%y`` for year with 2 digits" +#: ../system/integrations/zabbix.rst:27 +msgid "Create a Global Macro" msgstr "" -#: ../system/variables.rst:105 -msgid "``%m``" +#: ../system/integrations/zabbix.rst:29 +msgid "" +"Before setting up the **Webhook**, you need to setup the global macro " +"**{$ZABBIX.URL}**, which must contain the **URL** to the **Zabbix frontend**." msgstr "" -#: ../system/variables.rst:106 -msgid "Month of year (as number with zero-padding)" +#: ../system/integrations/zabbix.rst:33 +msgid "" +"In the **Administration** > **Media types** section, import the `Template`_." msgstr "" -#: ../system/variables.rst:107 -msgid "Use ``%-m`` for month without zero-padding" +#: ../system/integrations/zabbix.rst:38 +msgid "Open the added **Zammad** media type and set:" msgstr "" -#: ../system/variables.rst:108 -msgid "``%d``" +#: ../system/integrations/zabbix.rst:40 +msgid "**zammad\\_access\\_token** to the your **Personal User Token**" msgstr "" -#: ../system/variables.rst:109 -msgid "Day of month (as number with zero-padding)" +#: ../system/integrations/zabbix.rst:41 +msgid "" +"**zammad\\_url** to the **frontend URL** of your **Zammad** installation" msgstr "" -#: ../system/variables.rst:110 -msgid "Use ``%e`` for day without zero-padding" +#: ../system/integrations/zabbix.rst:43 +msgid "**zammad\\_customer** to your **Zammad user email**." msgstr "" -#: ../system/variables.rst:111 -msgid "``%H``" +#: ../system/integrations/zabbix.rst:44 +msgid "" +"**zammad\\_enable\\_tags** to **true** or **false** to enable or disable " +"trigger tags. **Important**: if you enable tag support, each tag is set with " +"a separate request." msgstr "" -#: ../system/variables.rst:112 -msgid "Hour of day in 24h notation with zero-padding" +#: ../system/integrations/zabbix.rst:48 +msgid "" +"If you want to prioritize issues according to **severity** values in Zabbix, " +"you can define mapping parameters:" msgstr "" -#: ../system/variables.rst:113 -msgid "Use ``%k`` for hour without zero-padding" +#: ../system/integrations/zabbix.rst:51 +msgid "**severity\\_**: Zammad priority ID" msgstr "" -#: ../system/variables.rst:114 -msgid "``%I``" +#: ../system/integrations/zabbix.rst:53 +msgid "Click the **Update** button to save the **Webhook** settings." msgstr "" -#: ../system/variables.rst:115 -msgid "Hour of day in 12h notation with zero-padding" +#: ../system/integrations/zabbix.rst:55 +msgid "" +"To receive notifications in **Zammad**, you need to create a **Zabbix user** " +"and add **Media** with the **Zammad** type." msgstr "" -#: ../system/variables.rst:116 +#: ../system/integrations/zabbix.rst:58 msgid "" -"Use ``%l`` for hour without zero-padding and ``%p`` / ``%P`` for meridian " -"indicator" +"For **Send to**: enter any text, as this value is not used, but is required." msgstr "" -#: ../system/variables.rst:117 -msgid "``%M``" +#: ../system/integrations/zabbix.rst:61 +msgid "" +"For more information, use the `Zabbix documentation `_." msgstr "" -#: ../system/variables.rst:118 -msgid "Minute of hour" +#: ../system/maintenance.rst:2 +msgid "Maintenance" msgstr "" -#: ../system/variables.rst:120 -msgid "``%S``" +#: ../system/maintenance.rst:4 +msgid "" +"Zammad comes with a maintenance mode that you can use for e.g. updating the " +"instance or changing settings while restricting availability and functions." msgstr "" -#: ../system/variables.rst:121 -msgid "Second of Minute" +#: ../system/maintenance.rst:13 +msgid "Mode" msgstr "" -#: ../system/variables.rst:123 -msgid "``%A``" +#: ../system/maintenance.rst:8 +msgid "The mode setting allows you to enable or disable the maintenance mode." msgstr "" -#: ../system/variables.rst:124 -msgid "Weekday name" +#: ../system/maintenance.rst:10 +msgid "Defaults to *off*." msgstr "" -#: ../system/variables.rst:125 -msgid "Use ``%a`` for abbreviated name or ``%^A`` for uppercase name" +#: ../system/maintenance.rst:12 +msgid "" +"The maintenance mode will restrict access to administrative roles only. This " +"means agents and customers are logged off." msgstr "" -#: ../system/variables.rst:126 -msgid "``%B``" +#: ../system/maintenance.rst:23 +msgid "@Login" msgstr "" -#: ../system/variables.rst:127 -msgid "Month name" +#: ../system/maintenance.rst:16 +msgid "" +"This setting allows you to provide a login message within a green banner " +"above the login screen. Click into the green banner in the settings page to " +"adjust your message. To activate the message, activate the *@Login* setting." msgstr "" -#: ../system/variables.rst:128 -msgid "Use ``%b`` for abbreviated name" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing the default login message within the\n" +"settings page" msgstr "" -#: ../system/variables.rst:129 -msgid "``%U``" +#: ../system/maintenance.rst:26 +msgid "" +"Send an informative message to **all active sessions**. This comes handy to " +"inform your agents e.g. about mayor outages or to force reloads after " +"configuration changes." msgstr "" -#: ../system/variables.rst:130 -msgid "Week number of current year" +#: ../system/maintenance.rst:31 +msgid "This is the messages title (slightly bigger than the normal message)." msgstr "" -#: ../system/variables.rst:131 -msgid "Use ``%W`` for a different calculation method" +#: ../system/maintenance.rst:34 +msgid "The text you want to provide to your logged in sessions." msgstr "" -#: ../system/variables.rst:134 +#: ../system/maintenance.rst:39 +msgid "Reload application" +msgstr "" + +#: ../system/maintenance.rst:37 msgid "" -"We support the known format directives for the Ruby built-in method " -"``strftime`` of the ``DateTime`` class. For more information, see `here " -"`_." +"Selecting this option will change the message acceptance button from *Close* " +"(with nothing happening) to *Continue session*, which forces the application " +"to reload." msgstr "" -#: ../system/variables/article.rst:2 -msgid "Articles" +#: ../system/maintenance.rst:43 +msgid "" +"If you have customers that are logged in to Zammad, they'll also be notified " +"if they're active in that moment." msgstr "" -#: ../system/variables/article.rst:4 ../system/variables/config.rst:4 -#: ../system/variables/current-user.rst:4 ../system/variables/ticket.rst:4 +#: ../system/maintenance.rst:48 +msgid "Example without reload application" +msgstr "" + +#: ../system/maintenance.rst:52 msgid "" -"If you're missing variables or are not sure if something is not working as " -"expected, feel free to ask over at the `Community `_." +"Message setting within Zammad's admin settings without ticket reload " +"application setting." msgstr "" -#: ../system/variables/article.rst:6 +#: ../system/maintenance.rst:0 msgid "" -"Below you can find all available ticket article-based variables within " -"Zammad. These can be called via Triggers for example. If you're unsure if " -"Zammad does support variables at the point you're at, you can try to type " -"``::`` to check." +"Screenshot showing the send message settings without ticket\n" +"reload application set" msgstr "" -#: ../system/variables/article.rst:9 ../system/variables/config.rst:9 -#: ../system/variables/ticket.rst:9 +#: ../system/maintenance.rst:61 ../system/maintenance.rst:85 msgid "" -"The below list gives you an example what kind of data you can expect, it's " -"not intended to explain the data itself." +"The modal all other active sessions will see upon pressing *Send to clients*." msgstr "" -#: ../system/variables/article.rst:11 -msgid "Article Variables" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing modal caused by maintenance's message\n" +"without reload application ticket" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "name" +#: ../system/maintenance.rst:72 +msgid "Example with reload application" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "variable" +#: ../system/maintenance.rst:76 +msgid "" +"Message setting within Zammad's admin settings with ticket reload " +"application setting." msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "example" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing the send message settings with ticket\n" +"reload application set" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Web" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing modal caused by maintenance's message\n" +"with reload application ticket" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.web}``" +#: ../system/monitoring.rst:2 +msgid "Monitoring" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``https://zammad.com`` or empty if not set in user object" +#: ../system/monitoring.rst:4 +msgid "" +"This function is only available in self hosted instances. If you use Zammad " +"in our cloud, we are monitoring the system on our own and take steps to fix " +"potential problems directly." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > VIP" +#: ../system/monitoring.rst:11 +msgid "" +"On the monitoring page, you can see the current health state of Zammad under " +"\"*Current Status*\" at the bottom. This can be useful if you want to have a " +"look if everything is up and running. As an example, you could have a look " +"in the monitoring when you assume that some emails aren't processed from " +"Zammad." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.vip}``" +#: ../system/monitoring.rst:17 +msgid "**Can't receive an email and the monitoring response is \"healthy\"?**" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -msgid "``true`` or ``false``" +#: ../system/monitoring.rst:19 +msgid "" +"Zammad will just inform you about unprocessable emails. This is not the case " +"for oversized emails. You can adjust the maximum email size in :doc:`../" +"channels/email/settings`." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Phone" +#: ../system/monitoring.rst:24 +msgid "Monitoring API" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.phone}``" +#: ../system/monitoring.rst:26 +msgid "" +"Beside the indication in the monitoring page, you can also use an external " +"monitoring tool to monitor Zammad's health. To request the health of Zammad, " +"you need to provide the API key (token) to the external monitoring tool. You " +"can copy the token from the \"*Current Token*\" field as well as the whole " +"API endpoint of your system (\"*Health Check*\" field), in which the API " +"token is already included." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``+4930123456789`` or empty if not set in user object" +#: ../system/monitoring.rst:37 +msgid "Screenshot showing Current Token and Health Check" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Note" +#: ../system/monitoring.rst:37 +msgid "Screenshot showing Token and Health Check" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.note}``" +#: ../system/monitoring.rst:39 +msgid "" +"In addition to that, you can reset the auto-generated token to make sure " +"that already configured monitoring systems won't work anymore. So, please " +"use this \"*Reset*\" button only if you know what you do!" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Some note about user`` or empty if not set in user object" +#: ../system/monitoring.rst:44 +msgid "Example Output" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Mobile" +#: ../system/monitoring.rst:0 +msgid "No issues found" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.mobile}``" +#: ../system/monitoring.rst:48 ../system/monitoring.rst:60 +msgid "**Indicator in Zammad**:" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Login" +#: ../system/monitoring.rst:0 +msgid "Screenshot showing monitoring with no issues" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.login}``" +#: ../system/monitoring.rst:54 ../system/monitoring.rst:66 +msgid "**API response**::" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -#: ../system/variables/ticket.rst:1 -msgid "``jdoe``" +#: ../system/monitoring.rst:0 +msgid "Issues were found" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Lastname" +#: ../system/monitoring.rst:0 +msgid "Screenshot showing monitoring with issues" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.lastname}``" +#: ../system/objects.rst:2 +msgid "Objects" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -#: ../system/variables/ticket.rst:1 -msgid "``Doe`` or empty if not set" +#: ../system/objects.rst:4 +msgid "" +"In Zammad you can add your own fields to tickets, users, organizations and " +"even groups (these are called \"objects\"). This can be useful if you need " +"to add further information to a ticket or any other object in Zammad and the " +"information doesn't fit in any existing field." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Firstname" +#: ../system/objects.rst:11 +msgid "" +"Try to avoid deleting attributes (and disable them instead) as Zammad might " +"run into unexpected conditions if they are referenced somewhere." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.firstname}``" +#: ../system/objects.rst:16 +msgid "" +"Here's an overview of object attributes. On the upper right you can add new " +"attributes. By default, there will be no custom fields - standard attributes " +"will be grayed out, you can't delete or change those. You can edit custom " +"attributes (they are displayed in black font and have a trash bin on the " +"right side) just by clicking on them." msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "``Joe`` or empty if not set" +#: ../system/objects.rst:24 +msgid "" +"Attributes you add to Zammad, no matter if they have default values or not, " +"will not update existing information. This means a new ticket field " +"technically will be empty unless you populate it." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Fax" +#: ../system/objects.rst:28 +msgid "" +"Especially in ticket scope this also means that newly added attributes will " +"be indicated as \"changed\" to agents that view the ticket. This may " +"interfere with Zammad's tabs behavior." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.fax}``" +#: ../system/objects.rst:40 +msgid "Ordering Attributes" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Email" +#: ../system/objects.rst:42 +msgid "" +"Since Zammad introduced :doc:`/system/core-workflows` the need to have a " +"custom positioning for attributes has become more important than ever." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.email}``" +#: ../system/objects.rst:45 +msgid "" +"To adjust the position of such an attribute, simply click on the attribute " +"entry in question, scroll down and adjust the position number. Please note " +"that you cannot change the positioning of default attributes." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``jdoe@example.com``" +#: ../system/objects.rst:49 +msgid "" +"In case two attributes have the same position value, Zammad will sort " +"alphabetically by name automatically." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Department" +#: ../system/objects.rst:None +msgid "" +"Screenshot showing custom attribute entries ordered in between default ones" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.department}``" +#: ../system/objects.rst:56 +msgid "Updating Database After Adding or Editing Attributes" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Sales`` or empty if not set in user object" +#: ../system/objects.rst:58 +msgid "" +"When adding or changing attributes, Zammad will not apply the changes " +"instantly, but instead shows you the changed attributes first. If you're " +"ready to go, just click on \"Update database\" to apply the changes to " +"Zammad. If you made a mistake or just want to discard your changes, click " +"\"Discard changes\"." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Address" +#: ../system/objects.rst:64 +msgid "" +"After applying the changes with \"Update Database\", a restart of Zammad is " +"**mandatory**. If you don't perform it, you may experience unexpected " +"behavior or even errors. You may want to do this kind of configuration " +"during maintenance windows." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.address}``" +#: ../system/objects.rst:72 +msgid "" +"Changes on objects require you to update the database to apply these changes." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Some street 1, 12345 Berlin`` or empty if not set in user object" +#: ../system/objects.rst:75 +msgid "**🤓 Service restarts can be automated**" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated" +#: ../system/objects.rst:0 +msgid "Hosted environments automatically restart for you." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_at}``" +#: ../system/objects.rst:0 +msgid "" +"If you're using a self-hosted installation you can use :docs:`environment " +"variables `" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``2019-10-08 15:24:47 UTC``" +#: ../system/objects.rst:82 +msgid "System Attributes" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Type > Name" +#: ../system/objects.rst:84 +msgid "" +"Zammad comes with pre-configured attributes. Some of them can't be edited " +"via UI (or at all). This is required for proper operation of Zammad and not " +"a bug." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.type.name}``" +#: ../system/objects.rst:90 +msgid "Ticket State" msgstr "" -#: ../system/variables/article.rst:1 +#: ../system/objects.rst:92 msgid "" -"``email`` (`list of article types `_)" +"If the pre-configured states aren't enough for you or you want to change " +"them, you can do so by clicking on the cogwheel icon in the state row in the " +"ticket tab. But you should be careful when changing pre-configured states. " +"This can lead to unwanted behavior in some cases." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > To" +#: ../system/objects.rst:None +msgid "Screenshot showing highlighted ticket state attribute" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.to}``" +#: ../system/objects.rst:122 +msgid "Handling of states" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``helpdesk@example.com``" +#: ../system/objects.rst:102 +msgid "" +"In the state configuration screen, you can add new states, disable states or " +"change states." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > TicketID" +#: ../system/objects.rst:0 +msgid "Screenshot showing table of default ticket states" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.ticket_id}``" +#: ../system/objects.rst:110 +msgid "" +"To add a new state, click on the \"New Ticket State\" button in the top " +"right corner. To change an existing state, simply click on the affected " +"state. This opens an edit dialog." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``1`` (not ticket number)" +#: ../system/objects.rst:114 +msgid "" +"You can also clone a state or set them to \"Default for new tickets\" or " +"\"Default for follow-ups\" by clicking on the ⁝ action button and select the " +"desired function." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Subject" +#: ../system/objects.rst:118 +msgid "" +"*Default for new tickets* means that this state is used for every newly " +"created ticket." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.subject}``" +#: ../system/objects.rst:121 +msgid "" +"*Default for follow-ups* means that this state is used if the ticket is re-" +"opened after it was closed." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``My amazing subject``" +#: ../system/objects.rst:171 +msgid "Ticket state in detail" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Sender > Name" +#: ../system/objects.rst:125 +msgid "" +"Below you can find a description for each field and option. Please head over " +"to the :ref:`example ` to see the edit dialog." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.sender.name}``" +#: ../system/objects.rst:129 +msgid "" +"This is the name of the state and what you and your agents are seeing when " +"choosing a state somewhere (e.g. in tickets, trigger configuration)." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Customer``, ``Agent`` or ``System``" +#: ../system/objects.rst:137 +msgid "" +"There are different state types you can choose from. By default, Zammad " +"comes with one state per state type." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Visibility" +#: ../system/objects.rst:140 +msgid "" +"**new**: for states for tickets that are new and it hasn't been worked on " +"them" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.internal}``" +#: ../system/objects.rst:142 +msgid "" +"**open**: for states for tickets that are in progress and agents are working " +"on them" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``false`` or ``true`` (false if not internal)" +#: ../system/objects.rst:144 +msgid "**merged**: for states for tickets that are merged with other tickets" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > From" +#: ../system/objects.rst:145 +msgid "" +"**pending reminder**: for states for tickets that are in progress and you " +"want to set a reminder. (default example: *pending reminder*)" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.from}``" +#: ../system/objects.rst:147 +msgid "" +"**pending action**: for states for tickets that are waiting for a specified " +"time and then change their state (default example: *pending close*)" msgstr "" -#: ../system/variables/article.rst:1 +#: ../system/objects.rst:150 msgid "" -"``Joe Doe `` may differ, depends on ``FROM`` of send mail" +"**closed**: for states for tickets that are finished and do not need to be " +"processed further" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Web" +#: ../system/objects.rst:153 +msgid "" +"⚠️ Choosing the correct state type is important! If you are in doubt, have a " +"look on the default states and their types!" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.web}``" +#: ../system/objects.rst:158 +msgid "Ignore escalation" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > VIP" +#: ../system/objects.rst:157 +msgid "" +"Here you can define whether tickets of this state will count to escalation " +"time or not." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.vip}``" +#: ../system/objects.rst:161 +msgid "" +"You can create a note for the state to inform other admins about the state. " +"This has no effect on tickets." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Phone" +#: ../system/objects.rst:165 +msgid "Set the state to *active* or *inactive*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.phone}``" +#: ../system/objects.rst:167 +msgid "" +"it is technically possible to set all states to inactive. To keep Zammad " +"working in such a case, the inactive flag of one of the states is ignored." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Note" +#: ../system/objects.rst:194 +msgid "Ticket state example" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.note}``" +#: ../system/objects.rst:174 +msgid "" +"Let's assume we want to create a new state which indicates that the ticket " +"has to wait for a response of a third party (e.g. service contractor or " +"manufacturer) and we want to to be able to set a reminder." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Mobile" +#: ../system/objects.rst:178 +msgid "" +"First we give the new state a proper name. In this example we call it " +"\"waiting for manufacturer\"." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.mobile}``" +#: ../system/objects.rst:181 +msgid "" +"As state type we choose \"pending reminder\". This indicates that the ticket " +"is still open and we can set a reminder. This reminder can be useful if our " +"manufacturer sometimes isn't responding or we want to remind him to give us " +"an answer." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Login" +#: ../system/objects.rst:186 +msgid "" +"We choose \"no\" for \"ignore escalation\" because we want to escalate the " +"tickets even if we are waiting on the manufacturer's feedback." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.login}``" +#: ../system/objects.rst:189 +msgid "The **result** in the creation dialog will look like this:" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Lastname" +#: ../system/objects.rst:0 +msgid "Screenshot showing ticket state creation dialog with example" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.lastname}``" +#: ../system/objects.rst:199 +msgid "Ticket Priority" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Firstname" +#: ../system/objects.rst:201 +msgid "" +"If the pre-configured priorities aren't enough for you or you want to change " +"them, you can do so by clicking on the cogwheel icon in the priority row in " +"the ticket tab:" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.firstname}``" +#: ../system/objects.rst:None +msgid "Screenshot showing highlighted ticket priority attribute" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Fax" +#: ../system/objects.rst:226 +msgid "Handling of priorities" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.fax}``" +#: ../system/objects.rst:210 +msgid "" +"In the priority configuration screen, you can add new priorities, disable " +"priorities or change priorities." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Email" +#: ../system/objects.rst:0 +msgid "Screenshot showing table of default ticket priorities" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.email}``" +#: ../system/objects.rst:218 +msgid "" +"To add a new priority, click on the \"New Priority\" button in the top right " +"corner. To change an existing priority, simply click on the affected " +"priority. This opens an edit dialog." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Department" +#: ../system/objects.rst:222 +msgid "" +"You can also clone a priority or set them to \"Default for new tickets\" by " +"clicking on the ⁝ action button and select the desired function." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.department}``" +#: ../system/objects.rst:225 +msgid "" +"*Default for new tickets* means that this priority is used for every newly " +"created ticket." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Address" +#: ../system/objects.rst:248 +msgid "Priorities in detail" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.address}``" +#: ../system/objects.rst:229 +msgid "Below you can find a description for each field and option." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created" +#: ../system/objects.rst:232 +msgid "" +"This is the name of the priority and what you and your agents are seeing " +"when choosing a priority somewhere (e.g. in tickets, trigger configuration)." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_at}``" +#: ../system/objects.rst:242 +msgid "Highlight color" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Cc" +#: ../system/objects.rst:237 +msgid "" +"Switch between *Low priority* (light blue), *High priority* (red) and - " +"(default). This affects the displayed color for ticket titles in overviews." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.cc}``" +#: ../system/objects.rst:241 +msgid "The color options are currently limited to the mentioned options." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``jdoe@example.com, company@example.com``" +#: ../system/objects.rst:245 +msgid "" +"You can create a note for the priority to inform other admins about the " +"priority. This has no effect on tickets." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Text" +#: ../system/objects.rst:249 +msgid "Set the priority to *active* or *inactive*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.body}``" +#: ../system/objects/external-data-source-example.rst:2 +msgid "External Data Source" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Test`` without formatting (plain)" +#: ../system/objects/external-data-source-example.rst:4 +msgid "" +"We assume you already had a look on :doc:`types` where you can find a " +"description of the individual fields." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article Text as HTML (not referenced)" +#: ../system/objects/external-data-source-example.rst:7 +msgid "" +"To reproduce this example, choose a category you want to add a custom field, " +"click on *New Attribute* and select *External data source field* under " +"*Format*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.body_as_html}``" +#: ../system/objects/external-data-source-example.rst:11 +msgid "" +"Our example story is to fetch data from an external product database. We " +"want to add our products to the tickets so that the products can be searched " +"and chosen from a list and also create a link to the product website." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Test`` with formatting" +#: ../system/objects/external-data-source-example.rst:16 +msgid "Base configuration" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "Ticket > Article#" +#: ../system/objects/external-data-source-example.rst:None +msgid "Initial steps to configure external data source object type" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "``#{ticket.article_count}``" +#: ../system/objects/external-data-source-example.rst:25 +msgid "Name: *product*" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``1`` number of ticket articles" +#: ../system/objects/external-data-source-example.rst:26 +msgid "Display: *Product*" msgstr "" -#: ../system/variables/config.rst:2 -msgid "Config" +#: ../system/objects/external-data-source-example.rst:29 +msgid "External data source configuration" msgstr "" -#: ../system/variables/config.rst:6 +#: ../system/objects/external-data-source-example.rst:31 msgid "" -"Below you'll find config related variables. These hold useful configuration " -"information that you can use within e.g. triggers to show necessary " -"information to your customer." +"First, enter the search URL making sure it contains ``#{search.term}`` as a " +"parameter:" msgstr "" -#: ../system/variables/config.rst:11 -msgid "Config Variables" +#: ../system/objects/external-data-source-example.rst:34 +msgid "**Example:** ``https://dummyjson.com/products/search?q=#{search.term}``" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Fully Qualified Domain Name" +#: ../system/objects/external-data-source-example.rst:36 +msgid "" +"After that, head down to the preview section and enter a search input for " +"the external data source." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.fqdn}``" +#: ../system/objects/external-data-source-example.rst:39 +msgid "**Example:** ``mac``" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``zammad.example.com``" +#: ../system/objects/external-data-source-example.rst:41 +msgid "Then you can find a preview of the response data below:" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Ticket Hook" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of JSON response based on search term" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.ticket_hook}``" +#: ../system/objects/external-data-source-example.rst:48 +msgid "" +"We recommend using the preview to have a look on the structure. There is a " +"top-level element called ``products``. One level below, you can find the " +"attributes ``id`` and ``title``." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``Ticket#``" +#: ../system/objects/external-data-source-example.rst:52 +msgid "**Search result response based on search from example:**" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > HTTP type" +#: ../system/objects/external-data-source-example.rst:119 +msgid "" +"To tell the remote system that the desired data is located below the " +"``products`` level, you have to put it in the field *Search result list key*." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.http_type}``" +#: ../system/objects/external-data-source-example.rst:122 +msgid "" +"After inserting ``products`` in the mentioned field, you get an extended " +"preview. You can find an additional box *Search result list* with a JSON " +"structure. This is the same response as before but stripped from the upper " +"``products`` element by the external data source." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``https`` or ``http``" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of JSON response search result list" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > SystemID" +#: ../system/objects/external-data-source-example.rst:132 +msgid "" +"Now you need to provide the keys for the search result values and labels. As " +"already mentioned, we are looking for the ``id`` and the ``title`` of our " +"products. If you haven't already, it is now a good time to look at the " +"preview of the *Search result list*." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.system_id}``" +#: ../system/objects/external-data-source-example.rst:197 +msgid "" +"After locating our two keys, we insert them in *search result value key* " +"(``id``) and in *Search result label key* (``title``)." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``31`` (value between 1 and 99)" +#: ../system/objects/external-data-source-example.rst:200 +msgid "" +"Basically, we configured the external data source already and we can see a " +"table in the preview section:" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Organization" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of product table based on search term" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.organization}``" +#: ../system/objects/external-data-source-example.rst:208 +msgid "" +"According to our example story, now just the *Link template* is missing." msgstr "" -#: ../system/variables/config.rst:1 +#: ../system/objects/external-data-source-example.rst:210 msgid "" -"``Zammad GmbH`` value set in `Branding `_" +"Please note that this is an optional feature. If you don't want to use such " +"links, of course you don't have to configure it." msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Product Name" +#: ../system/objects/external-data-source-example.rst:213 +msgid "" +"We can add now an address where additional product information can be found." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.product_name}``" +#: ../system/objects/external-data-source-example.rst:215 +msgid "Example: ``https://your_domain.com/q=#{ticket.product}``" msgstr "" -#: ../system/variables/config.rst:1 -msgid "" -"``Helpdesk`` value set in `Branding `_" +#: ../system/objects/external-data-source-example.rst:217 +msgid "In the example, the parameter means:" +msgstr "" + +#: ../system/objects/external-data-source-example.rst:219 +msgid "``#{}``: \"Frame\" for the insertion of information" msgstr "" -#: ../system/variables/current-user.rst:2 -msgid "Current User" +#: ../system/objects/external-data-source-example.rst:220 +msgid "``ticket``: object level, where you create your custom object" msgstr "" -#: ../system/variables/current-user.rst:6 -msgid "" -"Current user variables always return values of the current user that caused " -"e.g. a trigger to run." +#: ../system/objects/external-data-source-example.rst:221 +msgid "``product``: name of the (custom) object" msgstr "" -#: ../system/variables/current-user.rst:8 +#: ../system/objects/external-data-source-example.rst:223 msgid "" -"Due to the above fact, these variables are often not (yet) set or available " -"for usage." +"After configuring your *Link template*, there will be another column in the " +"preview. Hovering on the icons in the *Link* column will show you where it " +"forwards you." msgstr "" -#: ../system/variables/current-user.rst:10 +#: ../system/objects/external-data-source-example.rst:232 msgid "" -"In situations where e.g. schedulers or triggers run, this most likely is " -"nothing you want to use." -msgstr "" - -#: ../system/variables/current-user.rst:13 -msgid "Current User Variables" +"In our example, one of the links looks like: https://your_domain.com/q=6, " +"where the 6 is the product id." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Web" +#: ../system/objects/external-data-source-example.rst:235 +msgid "You can find more information regarding the URL in :doc:`types`." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.web}``" +#: ../system/objects/includes/adding-values-hint.include.rst:3 +msgid "" +"Adding values can be tricky for first timers, don't forget to press \"➕ " +"Add\" after typing your values. Otherwise you may loose a value." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``https://zammad.org`` or empty if not set" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:1 +#: ../system/objects/includes/reposition-values.include.rst:1 +msgid "**↕️ This field type allows the positioning of its values ↔️**" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > VIP" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:3 +msgid "" +"In order to re-arrange the field values, first edit the field. Then you can " +"use ☰ to drag the values in question to the correct position. If you want to " +"change the layer depth, double click on ☰. With it you can cycle through the " +"available layers." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.vip}``" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:8 +msgid "When you're ready, submit your changes to save the object attribute." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``false`` or ``true``" +#: :0 ../system/objects/types.rst:0 +msgid "" +"Screencast showing how to re-position values on tree select like\n" +"fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Web" +#: ../system/objects/includes/reposition-values.include.rst:3 +msgid "" +"In order to re-arrange the field values, edit the field and scroll below the " +"values. Make sure to tick the option \"Use custom option sort\"." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.web}``" +#: ../system/objects/includes/reposition-values.include.rst:8 +msgid "" +"If you do not tick this field, all manual positioning you did above will be " +"lost upon saving! ☠️" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > VIP" +#: ../system/objects/includes/reposition-values.include.rst:11 +msgid "" +"Now use ☰ to drag the values in question to the correct position. When " +"you're ready, submit your changes to save the object attribute." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.vip}``" +#: :0 ../system/objects/types.rst:0 +msgid "Screencast showing how to re-position values" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Phone" +#: ../system/objects/includes/url-template-hint.include.rst:3 +msgid "" +"This field allows using :ref:`URL fields (Link Templates) `." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.phone}``" +#: ../system/objects/permissions.rst:2 +msgid "Attribute Permissions" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``004930123456789`` or empty if not set" +#: ../system/objects/permissions.rst:7 +msgid "" +"In the object attributes configuration you can define if a field is shown " +"and if the input in the field is mandatory, separated by different screens " +"and for different :doc:`roles/permissions `." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Note" +#: ../system/objects/permissions.rst:17 +msgid "Screenshot shows object attribute permission table" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.note}``" +#: ../system/objects/permissions.rst:17 +msgid "" +"Some of the possible permissions and screen options for a user object " +"attribute." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Some note to this user`` or empty if not set" +#: ../system/objects/permissions.rst:19 +msgid "" +"Based on the object context (ticket, agent, organization, user), the " +"selectable roles (to be precise: the required permissions) and screens " +"differ. Be aware that these settings aren't affecting data creation via " +"other channels than the UI." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Mobile" +#: ../system/objects/permissions.rst:24 +msgid "" +"If you want to have further customization possibilities, you should have a " +"look at the :doc:`core workflows `." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.mobile}``" +#: ../system/objects/permissions.rst:28 +msgid "Screens" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``0049176123456789`` or empty if not set" +#: ../system/objects/permissions.rst:30 +msgid "" +"In the table below you can find an overview about the different permissions " +"and the available screens Zammad distinguishes between." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Login" +#: ../system/objects/permissions.rst:37 +msgid "Screen" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.login}``" +#: ../system/objects/permissions.rst:38 +msgid "Available for" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Lastname" +#: ../system/objects/permissions.rst:40 +msgid "create" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.lastname}``" +#: ../system/objects/permissions.rst:41 ../system/objects/permissions.rst:52 +#: ../system/objects/permissions.rst:59 ../system/objects/permissions.rst:73 +msgid "admin.user" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Firstname" +#: ../system/objects/permissions.rst:42 ../system/objects/permissions.rst:53 +#: ../system/objects/permissions.rst:60 +msgid "admin.organization" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.firstname}``" +#: ../system/objects/permissions.rst:43 ../system/objects/permissions.rst:54 +#: ../system/objects/permissions.rst:61 +msgid "admin.group" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``John`` or empty if not set" +#: ../system/objects/permissions.rst:44 +msgid "Creation dialog for not yet existing data" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Fax" +#: ../system/objects/permissions.rst:45 +msgid "create_middle" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.fax}``" +#: ../system/objects/permissions.rst:46 ../system/objects/permissions.rst:50 +#: ../system/objects/permissions.rst:57 ../system/objects/permissions.rst:66 +#: ../system/objects/permissions.rst:70 +msgid "ticket.customer" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``004930123464789`` or empty if not set" +#: ../system/objects/permissions.rst:47 ../system/objects/permissions.rst:51 +#: ../system/objects/permissions.rst:58 ../system/objects/permissions.rst:69 +msgid "ticket.agent" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Email" +#: ../system/objects/permissions.rst:48 +msgid "Ticket create dialog (middle section)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.email}``" +#: ../system/objects/permissions.rst:49 +msgid "edit" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``jdoe@customer.tld``" +#: ../system/objects/permissions.rst:55 +msgid "Editing dialog for already existing data" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Department" +#: ../system/objects/permissions.rst:56 +msgid "view" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.department}``" +#: ../system/objects/permissions.rst:62 +msgid "View-only dialog for already existing data" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Sales`` or empty if not set" +#: ../system/objects/permissions.rst:64 +msgid "(e.g. user or organization from search)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Avatar" +#: ../system/objects/permissions.rst:65 +msgid "signup" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.avatar(60,60)}``" +#: ../system/objects/permissions.rst:67 +msgid "Sign-up screen for new customers" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "avatar picture with width and height in pixel (e.g. 60,60)" +#: ../system/objects/permissions.rst:68 +msgid "invite_customer" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Address" +#: ../system/objects/permissions.rst:71 +msgid "" +"Customer invitation screen (from :doc:`First Steps ` area)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.address}``" +#: ../system/objects/permissions.rst:72 +msgid "invite_agent" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Some street 1, 12345 Berlin`` or empty if not set" +#: ../system/objects/permissions.rst:74 +msgid "" +"Agent invitation screen (from :doc:`First Steps ` area)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated at" +#: ../system/objects/permissions.rst:78 +msgid "Screen Options" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_at}``" +#: ../system/objects/permissions.rst:80 +msgid "" +"For the different screens you can select \"show\" and \"required\" options." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC``" +#: ../system/objects/permissions.rst:82 +msgid "**shown:** Show (check) or hide (uncheck) a field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Phone" +#: ../system/objects/permissions.rst:83 +msgid "" +"**required:** Set a field to mandatory (check). Forces users (via UI and " +"API) to populate the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.phone}``" +#: ../system/objects/types.rst:7 +msgid "Example external data source" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Shared organization" +#: ../system/objects/types.rst:2 +msgid "Attribute types" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.shared}``" +#: ../system/objects/types.rst:4 +msgid "" +"When adding a new object attribute, you can choose between the following " +"attribute types." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Note" +#: ../system/objects/types.rst:14 +msgid "" +"You cannot change the attribute format / type as soon as it is applied. If " +"you no longer need an object attribute, consider disabling it instead of " +"removing." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.note}``" +#: ../system/objects/types.rst:18 +msgid "**What about the translation of my attributes?**" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``A note to the organization of the user`` or empty if not set" +#: ../system/objects/types.rst:20 +msgid "" +"For some attribute types you can decide if they should be translatable or " +"not. To be precise, it works only for the selectable fields because the " +"possible choices are known and limited. For the following attribute types, " +"you can set the translatable flag:" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Name" +#: ../system/objects/types.rst:25 +msgid "*Boolean field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.name}``" +#: ../system/objects/types.rst:26 +msgid "*Single selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``Zammad GmbH``" +#: ../system/objects/types.rst:27 +msgid "*Multiple selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Domain based assignment" +#: ../system/objects/types.rst:28 +msgid "*Single tree selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.domain_assignment}``" +#: ../system/objects/types.rst:29 +msgid "*Multiple tree selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Domain" +#: ../system/objects/types.rst:31 +msgid "" +"For these types, you can find an additional field *Translate field contents*:" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.domain}``" +#: ../system/objects/types.rst:0 +msgid "Screenshot showing translatable attribute types" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``zammad.com`` or empty if not set" +#: ../system/objects/types.rst:38 +msgid "Screenshot with example of translatable attribute type" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > VIP" +#: ../system/objects/types.rst:45 +msgid "Boolean field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.vip}``" +#: ../system/objects/types.rst:41 +msgid "" +"Provides a drop-down field with display values for ``true`` and ``false``. " +"Setting a default is mandatory." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Note" +#: ../system/objects/types.rst:0 +msgid "Available settings for Boolean fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.note}``" +#: ../system/objects/types.rst:55 +msgid "Date field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Mobile" +#: ../system/objects/types.rst:48 +msgid "Provides a date picker field and does not allow default values." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.mobile}``" +#: ../system/objects/types.rst:52 +msgid "Default time diff (hours)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Login" +#: ../system/objects/types.rst:51 +msgid "" +"This setting helps the user by highlighting the day from now plus the " +"provided value. It *does not* pre-fill the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.login}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Date fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Lastname" +#: ../system/objects/types.rst:73 +msgid "Date & time field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.lastname}``" +#: ../system/objects/types.rst:58 +msgid "Provides a date and time picker – does not allow default values" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Firstname" +#: ../system/objects/types.rst:62 +msgid "Allow future" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.firstname}``" +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the future." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Fax" +#: ../system/objects/types.rst:66 +msgid "Allow past" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.fax}``" +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the past." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Email" +#: ../system/objects/types.rst:70 +msgid "Default time diff (minutes)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.email}``" +#: ../system/objects/types.rst:69 +msgid "" +"This setting helps the user by highlighting the day from now plus the " +"provided value. It does not pre-fill the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Department" +#: ../system/objects/types.rst:0 +msgid "Available settings for Date & time fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.department}``" +#: ../system/objects/types.rst:86 +msgid "Integer field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Web" +#: ../system/objects/types.rst:76 +msgid "" +"Provides an input field that allows integer usage only. You may define a " +"default value. You cannot enforce comma separation." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.web}``" +#: ../system/objects/types.rst:80 +msgid "Minimal" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > VIP" +#: ../system/objects/types.rst:80 +msgid "The minimal value the field accepts." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.vip}``" +#: ../system/objects/types.rst:83 +msgid "Maximal" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Phone" +#: ../system/objects/types.rst:83 +msgid "The maximum value the field accepts." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.phone}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Integer fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Note" +#: ../system/objects/types.rst:99 +msgid "Multiple selection field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.note}``" +#: ../system/objects/types.rst:89 +msgid "" +"Provides a selection field that allows the selection of one or more out of " +"several. This field does allow setting a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Mobile" +#: ../system/objects/types.rst:0 +msgid "Available settings for Multiple selection fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.mobile}``" +#: ../system/objects/types.rst:112 +msgid "Single selection field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Login" +#: ../system/objects/types.rst:102 +msgid "" +"Provides a drop-down field that allows selection of one value out of " +"several. This field does allow setting a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.login}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Single selection fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Lastname" +#: ../system/objects/types.rst:142 +msgid "Textarea field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.lastname}``" +#: ../system/objects/types.rst:115 +msgid "" +"Provides a text area input field (multiple lines) and thus allows e.g. new " +"lines. You can set a default field value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Firstname" +#: ../system/objects/types.rst:120 +msgid "" +"Please note that this field *does not* support text formatting or HTML " +"content (rich text)." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.firstname}``" +#: ../system/objects/types.rst:123 +msgid "**🥵 This field can consume a lot of visual space**" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Fax" +#: ../system/objects/types.rst:125 +msgid "" +"Depending on where you use this field type, it may use a lot of visual space " +"if you provide a lot of text. This may be an issue to work with." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.fax}``" +#: ../system/objects/types.rst:130 +msgid "Default" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Email" +#: ../system/objects/types.rst:129 +msgid "" +"The here provided text will be shown within the text area field or new data " +"sets." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.email}``" +#: ../system/objects/types.rst:134 ../system/objects/types.rst:160 +msgid "Maxlength" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Department" +#: ../system/objects/types.rst:0 ../system/objects/types.rst:160 +msgid "You can pick the maximum length of the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.department}``" +#: ../system/objects/types.rst:0 +msgid "The default length of this object is ``500``." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Avatar" +#: ../system/objects/types.rst:139 +msgid "Rows" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.avatar(60,60)}``" +#: ../system/objects/types.rst:0 +msgid "" +"Change the number of rows to dislay so that you can use only the space you " +"really need." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Address" +#: ../system/objects/types.rst:0 +msgid "The default number of rows is ``4``." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.address}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Textarea fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created at" +#: ../system/objects/types.rst:165 +msgid "Text field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_at}``" +#: ../system/objects/types.rst:145 +msgid "Provides a text field (one line) and allows choosing a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Avatar" +#: ../system/objects/types.rst:148 +msgid "" +"Defines the type of the input field. This allows e.g. your browser to ensure " +"that you provide the specific type." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.avatar(60,60)}``" +#: ../system/objects/types.rst:152 +msgid "Currently available:" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Address" +#: ../system/objects/types.rst:155 +msgid "Phone" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.address}``" +#: ../system/objects/types.rst:156 +msgid "Text" msgstr "" -#: ../system/variables/ticket.rst:6 -msgid "" -"Below you can find all available ticket-based variables within Zammad. These " -"can be called via Triggers for example. If you're unsure if Zammad does " -"support variables at the point you're at, you can try to type ``::`` to " -"check." +#: ../system/objects/types.rst:157 +msgid "Url *(URL fields disable link-template availability)*" msgstr "" -#: ../system/variables/ticket.rst:12 -msgid "Ticket Variables" +#: ../system/objects/types.rst:0 +msgid "Available settings for Text fields" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Web" +#: ../system/objects/types.rst:174 +msgid "Single tree selection field" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.web}``" +#: ../system/objects/types.rst:168 +msgid "" +"Provides a select-like field with up to 6 layers of options. Does not allow " +"setting a default value." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > VIP" +#: ../system/objects/types.rst:0 +msgid "Available settings for Tree Select fields" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.vip}``" +#: ../system/objects/types.rst:183 +msgid "Multiple tree selection field" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Phone" +#: ../system/objects/types.rst:177 +msgid "" +"Provides a select-like field with up to 6 layers of options allowing the " +"selection of multiple values. Does not allow setting a default value." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.phone}``" +#: ../system/objects/types.rst:302 +msgid "External Data Source field" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Note" +#: ../system/objects/types.rst:186 +msgid "" +"Provides a searchable field which fetches data from an external system. This " +"can be useful if you have data outside of Zammad and don't want to maintain " +"both data sources." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.note}``" +#: ../system/objects/types.rst:190 +msgid "The feature works as follows:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Mobile" +#: ../system/objects/types.rst:192 +msgid "" +"Zammad sends a query with a search string (free text from agent or based on " +"a variable) in a pre-defined format (\"Search URL\") to an external system." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.mobile}``" +#: ../system/objects/types.rst:195 +msgid "" +"This external system searches for matches and provides a response as a JSON " +"structure to Zammad." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Login" +#: ../system/objects/types.rst:197 +msgid "" +"Zammad just looks for the defined list and value keys, reads the content and " +"displays the value to the user. There is no search on Zammad side." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.login}``" +#: ../system/objects/types.rst:201 +msgid "" +"The usage of a PostgreSQL database for Zammad is required. In any other " +"case, Zammad will hide the external data source type and you are not able to " +"use it. If you want to use this feature, consider to :docs:`migrate your " +"database `." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Lastname" +#: ../system/objects/types.rst:205 +msgid "Currently, only ``GET`` is supported as request method." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.lastname}``" +#: ../system/objects/types.rst:206 +msgid "" +"The data structure must be in JSON format and provide the objects in an " +"array." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Firstname" +#: ../system/objects/types.rst:208 +msgid "" +"The endpoint for the external data source has to support search. On Zammad " +"side, there is no search/logic implemented; however, you can define the " +"output key and value based on the result(s) from the response (which " +"provides already filtered content based on the search)." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.firstname}``" +#: ../system/objects/types.rst:212 +msgid "" +"If you receive more results as expected, your external data source search " +"may not work properly or the structure of the URL is not correct. You should " +"get in touch with a responsible person from the external system." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Fax" +#: ../system/objects/types.rst:217 +msgid "" +"Please have a look :doc:`at our example `, where you can find a possible configuration for a public " +"dummy endpoint." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.fax}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for external data source fields" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Email" +#: ../system/objects/types.rst:242 +msgid "Search URL" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.email}``" +#: ../system/objects/types.rst:227 +msgid "" +"Set your endpoint where Zammad fetches the data. Please make sure to include " +"a valid search :doc:`variable ` as an URL parameter. " +"Example for a free text search at user input: ``#{search.term}``" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Department" +#: ../system/objects/types.rst:232 +msgid "" +"If in doubt, ask the responsible person for the external data source how " +"they expect the structure of the URL." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.department}``" +#: ../system/objects/types.rst:236 +msgid "" +"Depending on your search variable, the preview might work or not. The reason " +"is that the context might not be available and it is no bug." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Avatar" +#: ../system/objects/types.rst:239 +msgid "" +"Please also make sure to use a variable which is available in your object " +"context. For example you won't be able to search for a ticket in a user " +"object context." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.avatar(60,60)}``" +#: ../system/objects/types.rst:252 +msgid "SSL Verification" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Address" +#: ../system/objects/types.rst:245 +msgid "Here you can switch the SSL verification to no." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.address}``" +#: ../system/objects/types.rst:249 +msgid "" +"If your external data source system is using self signed certificates, " +"please have a look :doc:`here ` for " +"further information about how to handle them in Zammad, so you can keep the " +"SSL verification activated." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated at" +#: ../system/objects/types.rst:258 +msgid "HTTP Authentication" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_at}``" +#: ../system/objects/types.rst:255 +msgid "" +"If your external data source requires an authentication, you can set it " +"here. You can leave it empty or choose between *Basic Authentication* or " +"*Authentication Token* (selecting one of the two methods leads to additional " +"fields where you can enter your credentials/token)." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Title" +#: ../system/objects/types.rst:265 +msgid "Search result list key" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.title}``" +#: ../system/objects/types.rst:261 +msgid "" +"Defines the level in the JSON structure which provides the list with search " +"results. You can leave it empty, if the data is already provided as an " +"array. If you have to go deeper in the structure, you can provide a path " +"with ``.`` as separators, e.g. ``key.subkey.sub-sub-key``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "" -"``My amazing Subject`` (normally subject, can be edited within Interface and " -"thus differ)" +#: ../system/objects/types.rst:271 +msgid "Search result value key" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Accounted Time" +#: ../system/objects/types.rst:268 +msgid "" +"Defines the attribute in the structure in which your external data source " +"provides the *value* for your data. An example would be a product *number*. " +"If you have to go deeper in the structure, you can provide a path with ``.`` " +"as separators, e.g. ``key.subkey.sub-sub-key``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.time_unit}``" +#: ../system/objects/types.rst:277 +msgid "Search result label key" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``1``, ``2.75`` or empty response" +#: ../system/objects/types.rst:274 +msgid "" +"Defines the attribute in the structure in which your external data source " +"provides the *label* for your data. An example would be a product *name*. If " +"you have to go deeper in the structure, you can provide a path with ``.`` as " +"separators, e.g. ``key.subkey.sub-sub-key``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Tags" +#: ../system/objects/types.rst:280 +msgid "" +"In the preview area, you can find the following items (depending on your " +"configuration above):" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.tags}``" +#: ../system/objects/types.rst:283 +msgid "" +"**Error/hint message** (only if configuration is not complete): Zammad tells " +"you, if there is a problem and what you should change in your configuration." msgstr "" -#: ../system/variables/ticket.rst:1 +#: ../system/objects/types.rst:286 msgid "" -"Currently not available, see `Issue 2769 `_" +"**Search field**: search for an existing attribute in the data source to get " +"a preview. This is required for the fields below to show up." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > State > Name" +#: ../system/objects/types.rst:288 +msgid "" +"**Search result response** (only if configuration is not complete): here you " +"can find a syntax highlighted JSON preview of the response, based on the " +"search term you entered." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.state.name}``" +#: ../system/objects/types.rst:291 +msgid "" +"**Search result list** (only if *search result list key* is properly set): " +"output of the structure under the configured *search result list key*." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``new``, ``open``, ..." +#: ../system/objects/types.rst:294 +msgid "" +"**Preview table** (when fully configured): Zammad shows you a table which " +"includes the found items based on the search string (value, label and " +"optional link). You can use this preview if you don't have the complete data " +"structure of the external system in mind." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Priority > Name" +#: ../system/objects/types.rst:299 +msgid "" +"An example of a configured external data source field from agent perspective:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.priority.name}``" +#: ../system/objects/types.rst:0 +msgid "Screencast showing the search for a product in a ticket" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2 normal``" +#: ../system/objects/types.rst:307 +msgid "URL fields (Link-Template)" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Pending till" +#: ../system/objects/types.rst:311 +msgid "" +"This function is restricted to Text, Select and External data source types " +"only." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.pending_time}``" +#: ../system/objects/types.rst:314 +msgid "" +"Link-Templates are an amazing way to dynamically generate URLs. They allow " +"you to integrate other systems better without having to manually copy data " +"from Zammad if possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not set" +#: ../system/objects/types.rst:320 +msgid "" +"Another great way of communicating with another system may be Zammad's :doc:" +"`Webhooks `." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Web" +#: ../system/objects/types.rst:323 +msgid "" +"After filling a link-template enabled field, an URL icon will appear on its " +"right. Clicking on the icon opens a new tab." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.web}``" +#: ../system/objects/types.rst:328 +msgid "" +"Even though Zammad displays the link template within object edit and create " +"screens, the function is optional. It's only active if you populate the " +"field." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``https://zammad.com`` or empty if not set" +#: ../system/objects/types.rst:333 +msgid "" +"What's the difference between URL and text fields with link template...?!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > VIP" +#: ../system/objects/types.rst:335 +msgid "" +"Both fields have different use cases. Use ``text`` type text fields when " +"ever you have a *static* url that requires dynamic parameters. If you " +"require a drag & drop like field that you can put in any URL, use ``URL`` " +"type text fields." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.vip}``" +#: ../system/objects/types.rst:340 +msgid "" +"The difference is easier to spot when comparing the fields directly, below " +"screencast shows the result - the dynamic approach uses existing values in " +"the moment of updating to built the URL - e.g. ``https://google.com/search?" +"q=cookies`` - while the URL approach uses the actual URL of the field - e.g. " +"``https://zammad.com``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Phone" +#: ../system/objects/types.rst:None +msgid "" +"Screencast showing the differents in between URL and text type fields with " +"actual values" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.phone}``" +#: ../system/objects/types.rst:352 +msgid "How does this work...?!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Note" +#: ../system/objects/types.rst:354 +msgid "" +"As an example, let's say you have an attribute called ``amazing_attribute`` " +"and you want to open a google search directly with the input from that field." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.note}``" +#: ../system/objects/types.rst:357 +msgid "" +"Providing the link-template field below allows you to do so: ``https://www." +"google.com/search?q=#{ticket.amazing_attribute}``" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Mobile" +#: ../system/objects/types.rst:362 +msgid "" +"You can use any :doc:`Zammad variable ` as long as it's " +"available in the moment you need it." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.mobile}``" +#: ../system/objects/types.rst:365 +msgid "" +"As a result, you are redirected to Google with a search for the value of the " +"attribute, if you click on the button in the ticket (as you can see in the " +"screencast above)." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Login" +#: ../system/packages.rst:2 +msgid "Packages" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.login}``" +#: ../system/packages.rst:4 +msgid "That's the package management-area." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``agent``" +#: ../system/packages.rst:6 +msgid "Individual add-ons for Zammad can be installed and managed here." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Lastname" +#: ../system/sessions.rst:2 +msgid "Sessions" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.lastname}``" +#: ../system/sessions.rst:4 +msgid "" +"Sessions management allows reviewing currently known user sessions and " +"allows to end these. The session timeout is affected by :ref:" +"`security_session_timeout` configurations from security settings." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Mustermann`` or empty if not set" +#: ../system/sessions.rst:None +msgid "Screenshot showing Zammad's session management" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Firstname" +#: ../system/sessions.rst:13 +msgid "Zammad will provide the following information:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.firstname}``" +#: ../system/sessions.rst:16 +msgid "" +"The user account this session entry belongs to. It can be normal if a user " +"has several sessions in the list. This can be due to changed browser " +"information or if you use e.g. single sign on methods where the user does " +"not use the log off button." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Max`` or empty if not set" +#: ../system/sessions.rst:22 +msgid "Browser" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Fax" +#: ../system/sessions.rst:22 +msgid "The browser agent communicated to Zammad." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.fax}``" +#: ../system/sessions.rst:40 +msgid "Location" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Email" +#: ../system/sessions.rst:25 +msgid "" +"The anticipated location based on the users IP address. Depending on the IP " +"address the result shown may differ. This option depends on :doc:`/settings/" +"system/services`." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.email}``" +#: ../system/sessions.rst:29 +msgid "The following information can be shown:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``agent@company.tld`` or empty if not set" +#: ../system/sessions.rst:33 +msgid "IP address" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Department" +#: ../system/sessions.rst:32 +msgid "" +"Either if you set *Geo IP services* to inactive or you're using internal IP " +"address which do not provide location information." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.department}``" +#: ../system/sessions.rst:40 +msgid "Country (or Country + City)" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Support`` or empty if not set" +#: ../system/sessions.rst:36 +msgid "" +"If *Geo IP services* is enabled only. Depends on how detailed the available " +"IP address information are." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Avatar" +#: ../system/sessions.rst:39 +msgid "" +"Be aware that results can be inaccurate - this technically is not an error." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.avatar(60,60)}``" +#: ../system/sessions.rst:43 +msgid "Age" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Address" +#: ../system/sessions.rst:43 +msgid "Provides the time when the session initially has been created." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.address}``" +#: ../system/sessions.rst:50 +msgid "Update" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Shared organization" +#: ../system/sessions.rst:46 +msgid "" +"Provides the time the user used this session to open Zammad. This timestamp " +"is only updated if the user e.g. reloads, not during normal work on tickets." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.shared}``" +#: ../system/sessions.rst:50 +msgid "This timestamp is being used for the session timeout." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Note" +#: ../system/sessions.rst:53 +msgid "" +"Use the delete button to remove a single session on behalf of your user." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.note}``" +#: ../system/subscription.rst:2 +msgid "Subscription (SaaS)" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Name" +#: ../system/subscription.rst:4 +msgid "" +"The subscription settings page allows you to configure your instances " +"package and number of agents required." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.name}``" +#: ../system/subscription.rst:9 +msgid "" +"This setting section is only available for Hosted setups. If you're looking " +"for on premise support contracts, please see the `Zammad pricing page " +"`_." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Zammad GmbH`` or empty if not set" +#: ../system/subscription.rst:14 ../system/subscription.rst:34 +msgid "Plan" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Domain based assignment" +#: ../system/subscription.rst:16 +msgid "" +"Here you can set up everything affecting your instance subscription " +"functions like number of agents and package." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.domain_assignment}``" +#: ../system/subscription.rst:19 +msgid "" +"On top of the page you can find a subscription summary. You'll find the " +"number of used and available (booked) agent seats there. By using the *see " +"more* link you can also expand an agent list to see the currently configured " +"active agents. This list *does not* count accounts with admin permissions " +"only." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Domain" +#: ../system/subscription.rst:None +msgid "" +"Within subscription you can always see how many agents are still\n" +"available to add and who uses the seats." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.domain}``" +#: ../system/subscription.rst:29 +msgid "" +"Learn more on how to manage your agents in general :doc:`here `." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``domain.tld`` or empty if not set" +#: ../system/subscription.rst:36 +msgid "" +"This section gives you an overview of the available plans and their " +"functions / limits. If you require a more detailed table, check our " +"`detailed pricing table `_ for more." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > VIP" +#: ../system/subscription.rst:40 +msgid "" +"Your selection in this step will decide on the base agent price and e.g. " +"agent limits that might apply in the summary step." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.vip}``" +#: ../system/subscription.rst:43 +msgid "" +"The green *Selected* button will also tell you what plan you're currently in." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Number" +#: ../system/subscription.rst:47 +msgid "" +"Trial instances are running at Professional with 3 agents. The plan cannot " +"be changed during the trial for technical reasons, if you require more " +"agents for testing, please contact `our sales team `_ with a reason for the raise request." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.number}``" +#: ../system/subscription.rst:None +msgid "" +"Screenshot showing three available packages for a hosted Zammad\n" +"instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``31001``, ``201910731001``, ..." +#: ../system/subscription.rst:57 +msgid "" +"At the bottom of this block you can find a summary where you can adjust the " +"settings of the previous selected plan." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > ID" +#: ../system/subscription.rst:62 +msgid "" +"Note that upgrading (more agents, higher package) is always possible, " +"however, downgrading will only happen when your billing period renews." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.id}``" +#: ../system/subscription.rst:66 +msgid "" +"Upgrading resets your billing period and existing credit will be deducted " +"from the new total." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``17``, ``5281``, ..." +#: ../system/subscription.rst:75 +msgid "Billing cycle" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact (customer)" +#: ../system/subscription.rst:70 +msgid "" +"You can choose between either monthly or yearly billing. The price per agent " +"will be cheaper if you decide for yearly billing." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_customer_at}``" +#: ../system/subscription.rst:73 +msgid "" +"If you're still trying out things and are unsure of the right package for " +"your instance, you may want to choose monthly first and then upgrade to " +"yearly when you're sure." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "" -"``2019-10-07 16:25:00 UTC`` or empty if not applicable yet (Please note " -"`Ticket last contact behavior Settings `_ for this)" +#: ../system/subscription.rst:83 +msgid "Plan: (Starter|Professional|Plus) - Agents" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact" +#: ../system/subscription.rst:78 +msgid "Choose the number of agents you require for your instance." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_at}``" +#: ../system/subscription.rst:80 +msgid "" +"Keep in mind that some packages may have agent limits. Depending on the " +"previous chosen package, you won't be able to exceed specific agent numbers. " +"Also note that setting less agents than currently configured is not possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact (agent)" +#: ../system/subscription.rst:86 +msgid "Total" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_agent_at}``" +#: ../system/subscription.rst:86 +msgid "This will be the net total you're going to be billed." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable yet" +#: ../system/subscription.rst:88 +msgid "" +"By using the *Update subscription* button, the instance package will be " +"adjusted immediately. If you didn't provide a payment method yet, Zammad " +"will request you to provide one at this point." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Note" +#: ../system/subscription.rst:94 +msgid "" +"In case you're still within the trial period, this means that the trial will " +"be over immediately!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.note}``" +#: ../system/subscription.rst:97 +msgid "Down- or upgrading during the trial period *is not* possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Note about this group``" +#: ../system/subscription.rst:None +msgid "Screenshot showing payment options and a pricing summary" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Name" +#: ../system/subscription.rst:103 +msgid "Billing Information" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.name}``" +#: ../system/subscription.rst:105 +msgid "" +"You can control all billing relevant information like invoices, billing " +"address and the option to cancel your subscription." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Sales``" +#: ../system/subscription.rst:108 +msgid "" +"All adjusted billing information below only affect future invoices. If your " +"invoice was issued wrong, please contact `our sales team `_." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Follow-up possible" +#: ../system/subscription.rst:114 +msgid "Billing address" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.follow_up_possible}``" +#: ../system/subscription.rst:113 +msgid "" +"Provide your company address here, make sure to include the companies name " +"in case required. This address will be referenced on your invoice." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``no`` or ``yes``" +#: ../system/subscription.rst:118 +msgid "VAT ID" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Assign Follow-Ups" +#: ../system/subscription.rst:117 +msgid "" +"Provide your VAT ID here. If applicable your invoice will not contain German " +"VAT. Please make sure to pay the VAT in your country as required." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.follow_up_assignment}``" +#: ../system/subscription.rst:127 +msgid "Billing Email Address" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Assignment Timeout" +#: ../system/subscription.rst:121 +msgid "" +"Usually the instance owner (the person that registered the instance) will " +"receive all emails including the invoices. In case you have your own billing " +"department, you can provide their email address here." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.assignment_timeout}``" +#: ../system/subscription.rst:125 +msgid "" +"All billing relevant information will then be sent to this email address." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``20`` or empty if not configured" +#: ../system/subscription.rst:127 +msgid "Invoices are sent as attachment (PDF) to this email address." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > First response" +#: ../system/subscription.rst:129 +msgid "" +"Don't forget to press the *Update billing information* button after you " +"changed above settings." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.first_response_at}``" +#: ../system/subscription.rst:None +msgid "" +"Screenshot showing options for billing information within the\n" +"subscription menu" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Escalation at" +#: ../system/subscription.rst:137 +msgid "Payment Method" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.escalation_at}``" +#: ../system/subscription.rst:139 +msgid "You can pay via credit card or SEPA mandate." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable" +#: ../system/subscription.rst:144 +msgid "Credit card" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Web" +#: ../system/subscription.rst:142 +msgid "" +"Simply follow the dialogue by clicking *authorize credit card* and confirm -" +"if required by your bank- your consent to Zammad using your card for the " +"payments." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.web}``" +#: ../system/subscription.rst:148 +msgid "SEPA Direct Debit" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > VIP" +#: ../system/subscription.rst:147 +msgid "" +"Provide the requested information of the bank account holder and update if " +"you're ready. You'll then receive an email with the SEPA mandate." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.vip}``" +#: ../system/subscription.rst:150 +msgid "" +"Technically there's also the possibility to pay via invoice, however - this " +"method only applies to a fairly low number of instances. Please contact `our " +"sales team `_ for more information." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Phone" +#: ../system/subscription.rst:156 +msgid "Cancel Subscription" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.phone}``" +#: ../system/subscription.rst:158 +msgid "" +"Do you want to cancel your subscription? In case you no longer want to use " +"Zammad's SaaS, you can cancel your subscription by using the red *Yes, " +"please cancel my subscription* button." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Note" +#: ../system/subscription.rst:162 +msgid "" +"To cancel the description, enter the FQDN of your Zammad instance and " +"provide a reason for your cancellation." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.note}``" +#: ../system/subscription.rst:165 +msgid "" +"Your subscription will end the day after your trial or billing period ends." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Mobile" +#: ../system/subscription.rst:None +msgid "Screenshot showing subscription cancellation dialog" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.mobile}``" +#: ../system/subscription.rst:174 +msgid "" +"We will remind you about your cancelled subscription several times up front. " +"After the subscription ended all instance data will be removed. A restore " +"*is not* possible after that point!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Login" +#: ../system/subscription.rst:178 +msgid "**😖 Cancelled by accident?**" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.login}``" +#: ../system/subscription.rst:180 +msgid "" +"You can always undo the cancellation via the *Yes, undo the cancellation of " +"my subscription* button up to the last subscription day!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Lastname" +#: ../system/subscription.rst:0 +msgid "" +"Screenshot showing a red button to cancel the subscription\n" +"cancellation" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.lastname}``" +#: ../system/subscription.rst:189 +msgid "Payment History" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Firstname" +#: ../system/subscription.rst:191 +msgid "" +"The payment history will display a history of all paid invoices. At this " +"point you can also download these in case you need them again." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.firstname}``" +#: ../system/subscription.rst:196 +msgid "" +"You will only find *paid* invoices here. Invoices that are to be billed are " +"not available before the payment is completed." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Fax" +#: ../system/subscription.rst:201 +msgid "Date" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.fax}``" +#: ../system/subscription.rst:201 +msgid "Date of the invoice creation." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Email" +#: ../system/subscription.rst:204 +msgid "Amount" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.email}``" +#: ../system/subscription.rst:204 +msgid "Invoice total including VAT if applicable." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Department" +#: ../system/subscription.rst:207 +msgid "" +"Contains contract period (monthly or yearly) and hosted plan for the " +"subscription period in question." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.department}``" +#: ../system/subscription.rst:218 +msgid "Payment method / Service period" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Avatar" +#: ../system/subscription.rst:211 +msgid "" +"Used bank account or credit card as well as the subscription period the " +"invoice is about." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.avatar(60,60)}``" +#: ../system/subscription.rst:216 +msgid "" +"It might happen that the invoice date and subscription period differ. This " +"is nothing to worry about, the subscription periods will be accounted later " +"on." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Address" +#: ../system/subscription.rst:222 +msgid "Receipt" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.address}``" +#: ../system/subscription.rst:221 +msgid "" +"Use the arrow to download the invoice in question. You can download all " +"available invoices any time you need to here!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Web" +#: ../system/subscription.rst:None +msgid "Screenshot showing payment history of a hosted instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.web}``" +#: ../system/subscription.rst:229 +msgid "FAQ" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > VIP" +#: ../system/subscription.rst:233 +msgid "I set up a trial account but am missing functions to test" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.vip}``" +#: ../system/subscription.rst:232 +msgid "" +"The trial instance is running within the professional package allowing up to " +"three agents." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Phone" +#: ../system/subscription.rst:236 +msgid "Can I change package within the trial?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.phone}``" +#: ../system/subscription.rst:236 +msgid "No. As soon as the package is changed the subscription begins." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Note" +#: ../system/subscription.rst:241 +msgid "What happens to my trial instance after the trial period ended?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.note}``" +#: ../system/subscription.rst:239 +msgid "" +"Your instance will automatically be canceled for you. Please see *What " +"happens to my instance after it has been canceled?* for more." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Mobile" +#: ../system/subscription.rst:254 +msgid "What happens to my instance after it has been canceled?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.mobile}``" +#: ../system/subscription.rst:244 +msgid "That depends slightly on your instance state:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Login" +#: ../system/subscription.rst:250 +msgid "Trial instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.login}``" +#: ../system/subscription.rst:247 +msgid "" +"If you're still on trial, we will ice your instance and remind you once " +"again about your instance. We then will wait some days and remove your " +"instance from our system. This is the last time we will inform you by Email." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Lastname" +#: ../system/subscription.rst:254 +msgid "Paid instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.lastname}``" +#: ../system/subscription.rst:253 +msgid "" +"If you're a paying customer and canceled your subscription, the instance " +"removal will take place the day after your last subscription day." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Firstname" +#: ../system/subscription.rst:256 +msgid "Can removed instances be restored?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.firstname}``" +#: ../system/subscription.rst:257 +msgid "No. Once your instance has been removed, a restoration is not possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Fax" +#: ../system/system-report.rst:2 +msgid "System Report" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.fax}``" +#: ../system/system-report.rst:4 +msgid "" +"In this place you can't configure Zammad. Instead you can obtain a system " +"report about Zammad and its configuration." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Email" +#: ../system/system-report.rst:7 +msgid "" +"See the description in Zammad for an explanation. You can even find a " +"preview of the included data below the **Download** button." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.email}``" +#: ../system/system-report.rst:10 +msgid "" +"Zammad never sends this automatically to anyone. It is a manual process only " +"to provide better support based on your configuration." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Department" +#: ../system/translations.rst:2 +msgid "Translations" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.department}``" +#: ../system/translations.rst:4 +msgid "" +"Translations of Zammad are processed centrally in our `Weblate instance " +"`_. This allows non-developers to review " +"and update translation texts of the language they actually speak." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Avatar" +#: ../system/translations.rst:9 +msgid "" +"Your language is in an incomplete translation state or has typos? Please " +"consider helping us in sorting this out! All you need is either a GitHub " +"account or to register directly in our instance." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.avatar(60,60)}``" +#: ../system/translations.rst:13 +msgid "" +"Did you know? This is also where the documentation translations are handled. " +"🤓" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Address" +#: ../system/translations.rst:15 +msgid "" +"Have a look in our :docs:`contribution section ` in the system documentation to get started!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.address}``" +#: ../system/translations.rst:20 +msgid "Local Translations" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created at" +#: ../system/translations.rst:22 +msgid "" +"Apart from these system translations, there's still local translations you " +"can manage. This is relevant if you added custom objects that require " +"translations or even custom states and priorities." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_at}``" +#: ../system/translations.rst:None +msgid "Translation management screen within the admin menu" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "2019-10-07 16:25:00 UTC" +#: ../system/translations.rst:31 +msgid "Updating Translations" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Closing time" +#: ../system/translations.rst:33 +msgid "" +"Because of how Zammad ships translations, the only way to update the system " +"translations is to update your Zammad installation. The benefit of this is " +"that you no longer need internet access during a Zammad upgrade as the " +"package has everything it requires already." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.close_at}``" +#: ../system/translations.rst:39 +msgid "Translation of Custom Objects" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "2019-10-07 17:25:00 UTC" +#: ../system/translations.rst:41 +msgid "" +"No problem at all! You can customize any translation locally, even if it is " +"not initially provided by the system." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``3``, any number of articles existing in the ticket right now" +#: ../system/translations.rst:44 +msgid "" +"Translation is supported for a broad number of features, including but not " +"limited to custom:" msgstr "" -#: ../system/version.rst:2 -msgid "Version" +#: ../system/translations.rst:47 +msgid "Object Attributes" msgstr "" -#: ../system/version.rst:4 -msgid "Shows which version is currently being used on your Zammad-instance." +#: ../system/translations.rst:48 +msgid "Ticket Macros" msgstr "" -#: ../manage/roles/admin-permissions.rst:53 -msgid "``admin.checklist``" +#: ../system/translations.rst:49 +msgid "Ticket Overviews" msgstr "" -#: ../manage/roles/admin-permissions.rst:54 -msgid ":doc:`Manage > Checklist `" +#: ../system/translations.rst:50 +msgid "Ticket Priorities" msgstr "" -#: ../manage/roles/admin-permissions.rst:83 -msgid "``admin.channel_whatsapp``" +#: ../system/translations.rst:51 +msgid "Ticket States" msgstr "" -#: ../manage/roles/admin-permissions.rst:84 -msgid ":doc:`Channels > Whatsapp `" +#: ../system/translations.rst:54 +msgid "Customizing Translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:124 -msgid "``admin.public_links``" +#: ../system/translations.rst:56 +msgid "" +"Within the translation screen, simply click on the **New Translation** " +"button." msgstr "" -#: ../manage/roles/admin-permissions.rst:125 -msgid ":doc:`Manage > Public Links `" +#: ../system/translations.rst:None +msgid "New translation dialog" msgstr "" -#: ../manage/roles/admin-permissions.rst:151 -msgid "``admin.system_report``" +#: ../system/translations.rst:62 +msgid "" +"In the dialog you can immediately enter the exact translation source (if you " +"know it) and your custom translation text for it and click **Submit**." msgstr "" -#: ../manage/roles/admin-permissions.rst:152 -msgid ":doc:`System > System Report `" +#: ../system/translations.rst:65 +msgid "" +"Alternatively, try to search for translation suggestions in the list below. " +"Selecting an item from the list will pre-fill the translation source for you " +"and then you can just enter your custom translation." msgstr "" -#: ../manage/roles/admin-permissions.rst:166 -msgid "``admin.ticket_auto_assignment``" +#: ../system/translations.rst:69 +msgid "" +"The target language will always default to your current language selection. " +"If you need to translate for a different language, simply change the " +"selection before submitting." msgstr "" -#: ../manage/roles/admin-permissions.rst:167 -msgid ":ref:`Settings > Ticket > Auto Assignment `" +#: ../system/translations.rst:73 +msgid "" +"All your custom translations will show up in the overview table when added. " +"And they will even persist across Zammad updates!" msgstr "" -#: ../manage/roles/admin-permissions.rst:169 -msgid "``admin.ticket_duplicate_detection``" +#: ../system/translations.rst:76 +msgid "" +"Make sure to reload your browser if a translated string is not displayed." msgstr "" -#: ../manage/roles/admin-permissions.rst:170 -msgid ":ref:`Settings > Ticket > Duplicate Detection `" +#: ../system/translations.rst:80 +msgid "Reverting to Original Translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:172 -msgid "``admin.ticket_priority``" +#: ../system/translations.rst:82 +msgid "" +"If you want to revert a custom translation to original text, simply use the " +"appropriate action within the row of the overview table." msgstr "" -#: ../manage/roles/admin-permissions.rst:173 -msgid ":ref:`System > Objects >Ticket Priority `" +#: ../system/translations.rst:85 +msgid "" +"Depending on the type of the translation source, the action has a slightly " +"different name:" msgstr "" -#: ../manage/roles/admin-permissions.rst:175 -msgid "``admin.ticket_state``" +#: ../system/translations.rst:88 +msgid "**Reset** for customized system translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:176 -msgid ":ref:`System > Objects >Ticket State `" +#: ../system/translations.rst:89 +msgid "**Remove** for customized local translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:193 -msgid "``admin.webhook``" +#: ../system/translations.rst:91 +msgid "" +"In both cases, the action will remove the customized translation after a " +"confirmation." msgstr "" -#: ../manage/roles/admin-permissions.rst:194 -msgid ":doc:`Manage > Webhook `" +#: ../system/translations.rst:None +msgid "Screenshot showing the location of the Remove action" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:43 -msgid "``user_preferences.appearance``" +#: ../system/translations.rst:99 +msgid "Inline Translations" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:44 -msgid "Appearance configuration" +#: ../system/translations.rst:101 +msgid "" +"If you prefer a more hands-on approach, you can activate the inline or on-" +"screen translation feature by pressing ``ctrl`` + ``alt`` + ``t`` at any " +"time and on any screen." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:0 -msgid "Users can switch between dark, light and" +#: ../system/translations.rst:105 +msgid "" +"All customizable translation texts will be highlighted for you on the " +"screen. Just click into the highlighted area and update the text in place." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:0 -msgid "automatic mode." +#: ../system/translations.rst:None +msgid "Inline translation mode activated for the Overview screen" msgstr "" -#: ../system/system-report.rst:2 -msgid "System Report" +#: ../system/translations.rst:112 +msgid "" +"When finished editing, simply press ``ctrl`` + ``alt`` + ``t`` again to " +"deactivate." msgstr "" -#: ../system/system-report.rst:4 +#: ../system/translations.rst:117 msgid "" -"In this place you can't configure Zammad. Instead you can obtain a system " -"report about Zammad and its configuration." +"Even though it's available on any screen, the inline translation feature " +"requires admin permissions. It works only for the current language " +"selection. If you need to translate a different language, first change the " +"language in your :user-docs:`profile settings `." msgstr "" -#: ../system/system-report.rst:7 -msgid "" -"See the description in Zammad for an explanation. You can even find a " -"preview of the included data below the **Download** button." +#: ../system/version.rst:2 +msgid "Version" msgstr "" -#: ../system/system-report.rst:10 -msgid "" -"Zammad never sends this automatically to anyone. It is a manual process only " -"to provide better support based on your configuration." +#: ../system/version.rst:4 +msgid "Shows which version is currently being used on your Zammad-instance." msgstr "" diff --git a/locale/tr/LC_MESSAGES/admin-docs.po b/locale/tr/LC_MESSAGES/admin-docs.po index 2bfabfb3..d2f32aaa 100644 --- a/locale/tr/LC_MESSAGES/admin-docs.po +++ b/locale/tr/LC_MESSAGES/admin-docs.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Zammad\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-11-06 10:31+0100\n" +"POT-Creation-Date: 2024-11-12 16:31+0100\n" "PO-Revision-Date: 2024-09-27 17:00+0000\n" "Last-Translator: Rob \n" "Language-Team: Turkish Checklist `" +msgstr ":doc:`Yönetim > Metin Modülleri `" + #: ../manage/roles/admin-permissions.rst:56 msgid "``admin.channel_email``" msgstr "``admin.channel_email``" -#: ../manage/roles/admin-permissions.rst:54 #: ../manage/roles/admin-permissions.rst:57 msgid ":doc:`Channels > Email `" msgstr ":doc:`Kanallar > E-posta `" -#: ../manage/roles/admin-permissions.rst:56 #: ../manage/roles/admin-permissions.rst:59 msgid "``admin.channel_facebook``" msgstr "``admin.channel_facebook``" -#: ../manage/roles/admin-permissions.rst:57 #: ../manage/roles/admin-permissions.rst:60 msgid ":doc:`Channels > Facebook `" msgstr ":doc:`Kanallar > Facebook `" -#: ../manage/roles/admin-permissions.rst:58 #: ../manage/roles/admin-permissions.rst:61 msgid "" "Accessing Facebook tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:59 #: ../manage/roles/admin-permissions.rst:62 msgid "``admin.channel_formular``" msgstr "``admin.channel_formular``" -#: ../manage/roles/admin-permissions.rst:60 #: ../manage/roles/admin-permissions.rst:63 msgid ":doc:`Channels > Form `" msgstr ":doc:`Kanallar > Form `" -#: ../manage/roles/admin-permissions.rst:62 #: ../manage/roles/admin-permissions.rst:65 #, fuzzy msgid "``admin.channel_google``" msgstr "``admin.channel_web``" -#: ../manage/roles/admin-permissions.rst:63 #: ../manage/roles/admin-permissions.rst:66 #, fuzzy msgid ":doc:`Channels > Google `" msgstr ":doc:`Kanallar > E-posta `" -#: ../manage/roles/admin-permissions.rst:65 #: ../manage/roles/admin-permissions.rst:68 #, fuzzy msgid "``admin.channel_microsoft365``" msgstr "``admin.channel_sms``" -#: ../manage/roles/admin-permissions.rst:66 #: ../manage/roles/admin-permissions.rst:69 #, fuzzy msgid ":doc:`Channels > Microsoft 365 `" msgstr ":doc:`Kanallar > E-posta `" -#: ../manage/roles/admin-permissions.rst:68 #: ../manage/roles/admin-permissions.rst:71 msgid "``admin.channel_sms``" msgstr "``admin.channel_sms``" -#: ../manage/roles/admin-permissions.rst:69 #: ../manage/roles/admin-permissions.rst:72 #, fuzzy msgid ":doc:`Channels > SMS `" msgstr ":doc:`Kanallar > Form `" -#: ../manage/roles/admin-permissions.rst:71 #: ../manage/roles/admin-permissions.rst:74 msgid "``admin.channel_telegram``" msgstr "``admin.channel_telegram``" -#: ../manage/roles/admin-permissions.rst:72 #: ../manage/roles/admin-permissions.rst:75 msgid ":doc:`Channels > Telegram `" msgstr ":doc:`Kanallar > Telegram `" -#: ../manage/roles/admin-permissions.rst:73 #: ../manage/roles/admin-permissions.rst:76 msgid "" "Accessing Telegram tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:74 #: ../manage/roles/admin-permissions.rst:77 msgid "``admin.channel_twitter``" msgstr "``admin.channel_twitter``" -#: ../manage/roles/admin-permissions.rst:75 #: ../manage/roles/admin-permissions.rst:78 #, fuzzy msgid ":doc:`Channels > Twitter `" msgstr ":doc:`Kanallar > Twitter `" -#: ../manage/roles/admin-permissions.rst:76 #: ../manage/roles/admin-permissions.rst:79 msgid "" "Accessing Twitter/X tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:77 #: ../manage/roles/admin-permissions.rst:80 msgid "``admin.channel_web``" msgstr "``admin.channel_web``" -#: ../manage/roles/admin-permissions.rst:78 #: ../manage/roles/admin-permissions.rst:81 msgid ":doc:`Channels > Web `" msgstr ":doc:`Kanallar > Web `" -#: ../manage/roles/admin-permissions.rst:80 +#: ../manage/roles/admin-permissions.rst:83 +#, fuzzy +msgid "``admin.channel_whatsapp``" +msgstr "``admin.channel_chat``" + +#: ../manage/roles/admin-permissions.rst:84 +#, fuzzy +msgid ":doc:`Channels > Whatsapp `" +msgstr ":doc:`Kanallar > Sohbet `" + #: ../manage/roles/admin-permissions.rst:86 msgid "``admin.core_workflows``" msgstr "" -#: ../manage/roles/admin-permissions.rst:81 #: ../manage/roles/admin-permissions.rst:87 msgid ":doc:`System > Core Workflows `" msgstr "" -#: ../manage/roles/admin-permissions.rst:83 #: ../manage/roles/admin-permissions.rst:89 msgid "``admin.data_privacy``" msgstr "``admin.data_privacy``" -#: ../manage/roles/admin-permissions.rst:84 #: ../manage/roles/admin-permissions.rst:90 msgid ":doc:`System > Data Privacy `" msgstr ":doc:`Sistem > Veri Gizliliği `" -#: ../manage/roles/admin-permissions.rst:85 #: ../manage/roles/admin-permissions.rst:91 msgid "" "🔥 Be careful, it allows users to permanently delete data on the system." msgstr "" -#: ../manage/roles/admin-permissions.rst:86 #: ../manage/roles/admin-permissions.rst:92 msgid "``admin.group``" msgstr "``admin.group``" -#: ../manage/roles/admin-permissions.rst:87 #: ../manage/roles/admin-permissions.rst:93 msgid ":doc:`Manage > Groups `" msgstr ":doc:`Yönetim > Gruplar `" -#: ../manage/roles/admin-permissions.rst:89 #: ../manage/roles/admin-permissions.rst:95 msgid "``admin.integration``" msgstr "``admin.integration``" -#: ../manage/roles/admin-permissions.rst:90 #: ../manage/roles/admin-permissions.rst:96 #, fuzzy msgid ":doc:`System > Integrations `" msgstr ":doc:`Sistem > Entegrasyonlar `" -#: ../manage/roles/admin-permissions.rst:92 #: ../manage/roles/admin-permissions.rst:98 msgid "``admin.knowledge_base``" msgstr "``admin.knowledge_base``" -#: ../manage/roles/admin-permissions.rst:93 #: ../manage/roles/admin-permissions.rst:99 msgid ":doc:`Manage > Knowledge Base `" msgstr ":doc:`Yönetim > Bilgi Tabanı `" @@ -9001,57 +8996,46 @@ msgid "" "knowledge-base.html#editing-answers>`." msgstr "" -#: ../manage/roles/admin-permissions.rst:98 #: ../manage/roles/admin-permissions.rst:104 msgid "``admin.macro``" msgstr "``admin.macro``" -#: ../manage/roles/admin-permissions.rst:99 #: ../manage/roles/admin-permissions.rst:105 msgid ":doc:`Manage > Macros `" msgstr ":doc:`Yönetim > Makrolar `" -#: ../manage/roles/admin-permissions.rst:100 #: ../manage/roles/admin-permissions.rst:106 msgid "In some cases, macros may also require ``admin.tag``" msgstr "" -#: ../manage/roles/admin-permissions.rst:101 #: ../manage/roles/admin-permissions.rst:107 msgid "``admin.maintenance``" msgstr "``admin.maintenance``" -#: ../manage/roles/admin-permissions.rst:102 #: ../manage/roles/admin-permissions.rst:108 msgid ":doc:`System > Maintenance `" msgstr ":doc:`Sistem > Bakım `" -#: ../manage/roles/admin-permissions.rst:104 #: ../manage/roles/admin-permissions.rst:110 msgid "``admin.monitoring``" msgstr "``admin.monitoring``" -#: ../manage/roles/admin-permissions.rst:105 #: ../manage/roles/admin-permissions.rst:111 msgid ":doc:`System > Monitoring `" msgstr ":doc:`Sistem > İzleme `" -#: ../manage/roles/admin-permissions.rst:107 #: ../manage/roles/admin-permissions.rst:113 msgid "``admin.object``" msgstr "``admin.object``" -#: ../manage/roles/admin-permissions.rst:108 #: ../manage/roles/admin-permissions.rst:114 msgid ":doc:`System > Objects `" msgstr ":doc:`Sistem > Nesneler `" -#: ../manage/roles/admin-permissions.rst:110 #: ../manage/roles/admin-permissions.rst:116 msgid "``admin.organization``" msgstr "``admin.organization``" -#: ../manage/roles/admin-permissions.rst:111 #: ../manage/roles/admin-permissions.rst:117 #, fuzzy msgid ":doc:`Manage > Organizations `" @@ -9070,213 +9054,229 @@ msgstr "" msgid "They can even edit an organization's name, domain, and notes!" msgstr "" -#: ../manage/roles/admin-permissions.rst:115 #: ../manage/roles/admin-permissions.rst:121 msgid "``admin.overview``" msgstr "``admin.overview``" -#: ../manage/roles/admin-permissions.rst:116 #: ../manage/roles/admin-permissions.rst:122 msgid ":doc:`Manage > Overviews`" msgstr ":doc:`Yönetim > Genel Bakış `" -#: ../manage/roles/admin-permissions.rst:118 +#: ../manage/roles/admin-permissions.rst:124 +#, fuzzy +msgid "``admin.public_links``" +msgstr "``admin.api``" + +#: ../manage/roles/admin-permissions.rst:125 +#, fuzzy +msgid ":doc:`Manage > Public Links `" +msgstr ":doc:`Yönetim > Makrolar `" + #: ../manage/roles/admin-permissions.rst:127 msgid "``admin.package``" msgstr "``admin.package``" -#: ../manage/roles/admin-permissions.rst:119 #: ../manage/roles/admin-permissions.rst:128 msgid ":doc:`System > Packages `" msgstr ":doc:`Sistem > Paketler `" -#: ../manage/roles/admin-permissions.rst:121 #: ../manage/roles/admin-permissions.rst:130 msgid "``admin.report_profile``" msgstr "``admin.report_profile``" -#: ../manage/roles/admin-permissions.rst:122 #: ../manage/roles/admin-permissions.rst:131 msgid ":doc:`Manage > Report Profiles `" msgstr ":doc:`Yönetim > Profilleri Raporla `" -#: ../manage/roles/admin-permissions.rst:123 #: ../manage/roles/admin-permissions.rst:132 msgid "Access to view reports: ``report``" msgstr "" -#: ../manage/roles/admin-permissions.rst:124 #: ../manage/roles/admin-permissions.rst:133 msgid "``admin.role``" msgstr "``admin.role``" -#: ../manage/roles/admin-permissions.rst:125 #: ../manage/roles/admin-permissions.rst:134 #, fuzzy msgid ":doc:`Manage > Roles `" msgstr ":doc:`Yöneim > Roller `. 🧐" -#: ../manage/roles/admin-permissions.rst:127 #: ../manage/roles/admin-permissions.rst:136 msgid "``admin.scheduler``" msgstr "``admin.scheduler``" -#: ../manage/roles/admin-permissions.rst:128 #: ../manage/roles/admin-permissions.rst:137 #, fuzzy msgid ":doc:`Manage > Scheduler `" msgstr ":doc:`Yönetim > Metin Modülleri `" -#: ../manage/roles/admin-permissions.rst:129 #: ../manage/roles/admin-permissions.rst:138 #, fuzzy msgid "For automation on tickets" msgstr "Bir bilet oluşturma" -#: ../manage/roles/admin-permissions.rst:130 #: ../manage/roles/admin-permissions.rst:139 msgid "``admin.security``" msgstr "``admin.security``" -#: ../manage/roles/admin-permissions.rst:131 #: ../manage/roles/admin-permissions.rst:140 #, fuzzy msgid ":doc:`Settings > Security `" msgstr ":doc:`Ayarlar > Markalama `" -#: ../manage/roles/admin-permissions.rst:132 #: ../manage/roles/admin-permissions.rst:141 msgid "Settings of Zammad. This also covers third party authentications." msgstr "" -#: ../manage/roles/admin-permissions.rst:133 #: ../manage/roles/admin-permissions.rst:142 msgid "``admin.session``" msgstr "``admin.session``" -#: ../manage/roles/admin-permissions.rst:134 #: ../manage/roles/admin-permissions.rst:143 msgid ":doc:`System > Sessions `" msgstr ":doc:`Sistem > Oturumlar `" -#: ../manage/roles/admin-permissions.rst:136 #: ../manage/roles/admin-permissions.rst:145 msgid "``admin.setting_system``" msgstr "``admin.setting_system``" -#: ../manage/roles/admin-permissions.rst:137 #: ../manage/roles/admin-permissions.rst:146 #, fuzzy msgid ":doc:`Settings > System `" msgstr ":doc:`Ayarlar > Markalama `" -#: ../manage/roles/admin-permissions.rst:139 #: ../manage/roles/admin-permissions.rst:148 msgid "``admin.sla``" msgstr "``admin.sla``" -#: ../manage/roles/admin-permissions.rst:140 #: ../manage/roles/admin-permissions.rst:149 #, fuzzy msgid ":doc:`Manage > SLAs `" msgstr ":doc:`Yönetim > SLA'lar `" -#: ../manage/roles/admin-permissions.rst:142 +#: ../manage/roles/admin-permissions.rst:151 +#, fuzzy +msgid "``admin.system_report``" +msgstr "``admin.tag``" + +#: ../manage/roles/admin-permissions.rst:152 +#, fuzzy +msgid ":doc:`System > System Report `" +msgstr ":doc:`Sistem > Oturumlar `" + #: ../manage/roles/admin-permissions.rst:154 msgid "``admin.tag``" msgstr "``admin.tag``" -#: ../manage/roles/admin-permissions.rst:143 #: ../manage/roles/admin-permissions.rst:155 msgid ":doc:`Manage > Tags `" msgstr ":doc:`Yönetim > Etiketler `" -#: ../manage/roles/admin-permissions.rst:145 #: ../manage/roles/admin-permissions.rst:157 #, fuzzy msgid "``admin.template``" msgstr "``admin.tag``" -#: ../manage/roles/admin-permissions.rst:146 #: ../manage/roles/admin-permissions.rst:158 #, fuzzy msgid ":doc:`Manage > Templates `" msgstr ":doc:`Yönetim > Etiketler `" -#: ../manage/roles/admin-permissions.rst:148 #: ../manage/roles/admin-permissions.rst:160 msgid "``admin.text_module``" msgstr "``admin.text_module``" -#: ../manage/roles/admin-permissions.rst:149 #: ../manage/roles/admin-permissions.rst:161 msgid ":doc:`Manage > Text Modules `" msgstr ":doc:`Yönetim > Metin Modülleri `" -#: ../manage/roles/admin-permissions.rst:151 #: ../manage/roles/admin-permissions.rst:163 msgid "``admin.ticket``" msgstr "``admin.ticket``" -#: ../manage/roles/admin-permissions.rst:152 #: ../manage/roles/admin-permissions.rst:164 #, fuzzy msgid ":doc:`Settings > Tickets `" msgstr ":doc:`Ayarlar > Markalama `" -#: ../manage/roles/admin-permissions.rst:153 #: ../manage/roles/admin-permissions.rst:165 #, fuzzy msgid "Does not grant access to :doc:`/misc/composer`" msgstr "✍️ :doc:`/misc/composer` adresine göz at." -#: ../manage/roles/admin-permissions.rst:154 +#: ../manage/roles/admin-permissions.rst:166 +#, fuzzy +msgid "``admin.ticket_auto_assignment``" +msgstr "``admin.ticket``" + +#: ../manage/roles/admin-permissions.rst:167 +msgid ":ref:`Settings > Ticket > Auto Assignment `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:169 +#, fuzzy +msgid "``admin.ticket_duplicate_detection``" +msgstr "``admin.text_module``" + +#: ../manage/roles/admin-permissions.rst:170 +msgid ":ref:`Settings > Ticket > Duplicate Detection `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:172 +#, fuzzy +msgid "``admin.ticket_priority``" +msgstr "``admin.ticket``" + +#: ../manage/roles/admin-permissions.rst:173 +msgid ":ref:`System > Objects >Ticket Priority `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:175 +#, fuzzy +msgid "``admin.ticket_state``" +msgstr "``admin.ticket``" + +#: ../manage/roles/admin-permissions.rst:176 +msgid ":ref:`System > Objects >Ticket State `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:178 msgid "``admin.time_accounting``" msgstr "``admin.time_accounting``" -#: ../manage/roles/admin-permissions.rst:155 #: ../manage/roles/admin-permissions.rst:179 msgid ":doc:`Manage > Time Accounting `" msgstr ":doc:`Yönetim > Zaman Hesaplama `" -#: ../manage/roles/admin-permissions.rst:156 #: ../manage/roles/admin-permissions.rst:180 msgid "Also allows the export of timekeeping records." msgstr "" -#: ../manage/roles/admin-permissions.rst:157 #: ../manage/roles/admin-permissions.rst:181 msgid "``admin.translation``" msgstr "``admin.translation``" -#: ../manage/roles/admin-permissions.rst:158 #: ../manage/roles/admin-permissions.rst:182 #, fuzzy msgid ":doc:`System > Translations `" msgstr ":doc:`Sistem > Oturumlar `" -#: ../manage/roles/admin-permissions.rst:159 #: ../manage/roles/admin-permissions.rst:183 msgid "Also enables inline translation" msgstr "" -#: ../manage/roles/admin-permissions.rst:160 #: ../manage/roles/admin-permissions.rst:184 msgid "``admin.trigger``" msgstr "``admin.trigger``" -#: ../manage/roles/admin-permissions.rst:161 #: ../manage/roles/admin-permissions.rst:185 msgid ":doc:`Manage > Triggers `" msgstr ":doc:`Yönetim > Tetikleyiciler `" -#: ../manage/roles/admin-permissions.rst:163 #: ../manage/roles/admin-permissions.rst:187 msgid "``admin.user``" msgstr "``admin.user``" -#: ../manage/roles/admin-permissions.rst:164 #: ../manage/roles/admin-permissions.rst:188 msgid ":doc:`Manage > Users `" msgstr ":doc:`Yönetim > Kullanıcılar `" @@ -9295,6 +9295,16 @@ msgid "" "from-users-perspective>` ." msgstr "" +#: ../manage/roles/admin-permissions.rst:193 +#, fuzzy +msgid "``admin.webhook``" +msgstr "``admin.role``" + +#: ../manage/roles/admin-permissions.rst:194 +#, fuzzy +msgid ":doc:`Manage > Webhook `" +msgstr ":doc:`Yönetim > Makrolar `" + #: ../manage/roles/agent-permissions.rst:2 msgid "Agent Permissions" msgstr "Aracı İzinleri" @@ -9735,37 +9745,48 @@ msgid "than the user that generated them." msgstr "" #: ../manage/roles/user-preferences-permissions.rst:43 +#, fuzzy +msgid "``user_preferences.appearance``" +msgstr "``user_preferences.calendar``" + +#: ../manage/roles/user-preferences-permissions.rst:44 +#, fuzzy +msgid "Appearance configuration" +msgstr "Yapılandırma" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "Users can switch between dark, light and" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "automatic mode." +msgstr "" + #: ../manage/roles/user-preferences-permissions.rst:47 msgid "``user_preferences.avatar``" msgstr "``user_preferences.avatar``" -#: ../manage/roles/user-preferences-permissions.rst:44 #: ../manage/roles/user-preferences-permissions.rst:48 #, fuzzy msgid "Avatar settings" msgstr "Posta Sunucusu Ayarları" -#: ../manage/roles/user-preferences-permissions.rst:45 #: ../manage/roles/user-preferences-permissions.rst:49 msgid "Override the default Gravatar with a custom avatar" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:46 #: ../manage/roles/user-preferences-permissions.rst:50 msgid "``user_preferences.calendar``" msgstr "``user_preferences.calendar``" -#: ../manage/roles/user-preferences-permissions.rst:47 #: ../manage/roles/user-preferences-permissions.rst:51 msgid "Configure the calendar feed" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:49 #: ../manage/roles/user-preferences-permissions.rst:53 msgid "``user_preferences.device``" msgstr "``user_preferences.device``" -#: ../manage/roles/user-preferences-permissions.rst:50 #: ../manage/roles/user-preferences-permissions.rst:54 msgid "Manage device login sessions" msgstr "" @@ -9782,22 +9803,18 @@ msgstr "" msgid "To learn more, see :doc:`/manage/trigger/system-notifications`." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:54 #: ../manage/roles/user-preferences-permissions.rst:58 msgid "``user_preferences.language``" msgstr "``user_preferences.language``" -#: ../manage/roles/user-preferences-permissions.rst:55 #: ../manage/roles/user-preferences-permissions.rst:59 msgid "Configure the UI locale/language" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:57 #: ../manage/roles/user-preferences-permissions.rst:61 msgid "``user_preferences.linked_accounts``" msgstr "``user_preferences.linked_accounts``" -#: ../manage/roles/user-preferences-permissions.rst:58 #: ../manage/roles/user-preferences-permissions.rst:62 #, fuzzy msgid "Account linking" @@ -9823,7 +9840,6 @@ msgstr "İlk oturum açmada otomatik hesap bağlantısı" msgid "is the only way users can utilize third-party logins." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:63 #: ../manage/roles/user-preferences-permissions.rst:67 msgid "``user_preferences.notifications``" msgstr "" @@ -9852,7 +9868,6 @@ msgstr "" msgid "Customers can't receive ticket notifications at all." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:69 #: ../manage/roles/user-preferences-permissions.rst:73 msgid "``user_preferences.out_of_office``" msgstr "" @@ -9877,7 +9892,6 @@ msgstr "" msgid "they're replacing." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:75 #: ../manage/roles/user-preferences-permissions.rst:79 #, fuzzy msgid "``user_preferences.overview_sorting``" @@ -9907,12 +9921,10 @@ msgstr "" msgid "overviews has no effect on custom orders." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:82 #: ../manage/roles/user-preferences-permissions.rst:86 msgid "``user_preferences.password``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:83 #: ../manage/roles/user-preferences-permissions.rst:87 msgid "Change account password" msgstr "" @@ -9929,7 +9941,6 @@ msgstr "" msgid "your only allowed authentication method." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:87 #: ../manage/roles/user-preferences-permissions.rst:91 #, fuzzy msgid "``user_preferences.two_factor_authentication``" @@ -9968,7 +9979,7 @@ msgstr "" #: ../manage/scheduler.rst:19 msgid "" -"Schedulers can be used to send periodic reminder emails. Use :doc:`/system/" +"Schedulers can be used to send periodic reminder emails. Use :doc:`/misc/" "variables` to build highly-customized email templates." msgstr "" @@ -11025,7 +11036,7 @@ msgstr "" #: ../manage/text-modules.rst:57 #, fuzzy msgid "" -"The example text modules below use :doc:`/system/variables` to dynamically " +"The example text modules below use :doc:`/misc/variables` to dynamically " "insert information like the customer's or agent's names." msgstr "" "Aşağıdaki örnek metin modülleri, müşterinin veya aracının adları gibi " @@ -11400,8 +11411,8 @@ msgstr "Oluşturulma" #: ../misc/object-conditions/basics.rst:144 #: ../misc/object-conditions/basics.rst:160 #: ../misc/object-conditions/basics.rst:168 -#: ../misc/object-conditions/basics.rst:178 ../settings/ticket.rst:2 -#: ../system/variables/ticket.rst:2 +#: ../misc/object-conditions/basics.rst:178 ../misc/variables/ticket.rst:2 +#: ../settings/ticket.rst:2 msgid "Ticket" msgstr "Bilet" @@ -11640,7 +11651,7 @@ msgstr "" #: ../manage/trigger/how-do-they-work.rst:79 msgid "" -"Certain actions (such as *email*, *SMS* and *notes*) support :doc:`/system/" +"Certain actions (such as *email*, *SMS* and *notes*) support :doc:`/misc/" "variables`, which can be used to build highly-customized message templates." msgstr "" @@ -11669,7 +11680,7 @@ msgstr "" msgid "" "You can also combine static text with placeholders for text fields. Remember " "that the placeholders' values have to be known during trigger runtime. Learn " -"more about :doc:`/system/variables`." +"more about :doc:`/misc/variables`." msgstr "" #: ../manage/trigger/how-do-they-work.rst:105 @@ -12681,7 +12692,7 @@ msgstr "" msgid "" "When switched on, a code editor will be shown below, where you can configure " "custom payload for your webhook in JSON format. To insert supported :doc:`/" -"system/variables` use ``::`` or ``#{`` shortcuts for autocomplete." +"misc/variables` use ``::`` or ``#{`` shortcuts for autocomplete." msgstr "" #: ../manage/webhook/add.rst:103 @@ -15366,12314 +15377,12210 @@ msgid "" "powerful conditions with AND/OR relations." msgstr "" -#: ../settings/branding.rst:10 -#, fuzzy -msgid "Product Name" -msgstr "*Ürün adı*" +#: ../misc/variables.rst:2 +msgid "Variables" +msgstr "Değişkenler" -#: ../settings/branding.rst:7 +#: ../misc/variables.rst:4 msgid "" -"Defines the name of the application, shown in the web interface, tabs and " -"title bar of the web browser." +"Please note that this is just an overview of available variables. It might " +"be incomplete or variables might not be available within some functions. If " +"you're missing variables or are not sure if something is not working as " +"expected, feel free to ask over at the `Community `_." msgstr "" -"Web arayüzünde, sekmelerde ve web tarayıcısının başlık çubuğunda gösterilen " -"uygulamanın adını tanımlar." +"Lütfen bunun yalnızca mevcut değişkenlere genel bir bakış olduğunu " +"unutmayın. Eksik olabilir veya bazı işlevlerde değişkenler mevcut " +"olmayabilir. Değişkenleri kaçırıyorsanız veya bir şeyin beklendiği gibi " +"çalışmadığından emin değilseniz, \"Topluluk \" " +"adresinden soru sormaktan çekinmeyin." -#: ../settings/branding.rst:10 -msgid "Default value: ``Zammad Helpdesk``" +#: ../misc/variables.rst:10 +#, fuzzy +msgid "" +"Variables can be called by typing ``::`` (just like text modules in the " +"frontend), as long as you're in a supported text field within the backend. " +"Zammad will display all variables being available within this context and " +"replace it to the variable as soon as you selected an entry." msgstr "" +"Değişkenler, Backend içinde desteklenen bir metin alanında olduğunuz sürece " +"``::`` (tıpkı ön uçtaki metin modülleri gibi) yazılarak çağrılabilir. " +"Zammad, bu bağlamda mevcut olan tüm değişkenleri gösterecek ve bir girdi " +"seçtiğiniz anda onu değişkenle değiştirecektir." -#: ../settings/branding.rst:13 -msgid "Will be shown in the app and is included in email footers." -msgstr "Uygulamada gösterilecek ve e-posta altbilgilerine dahil edilecek." - -#: ../settings/branding.rst:19 +#: ../misc/variables.rst:15 #, fuzzy -msgid "Logo" -msgstr "*Logo*" +msgid "" +"You have an empty field which you referenced and it appears as ``-``? That's " +"currently working as designed - you might want to ensure that these fields " +"always have a value." +msgstr "" +"Referans verdiğiniz boş bir alanınız var ve ``-`` olarak mı görünüyor? Şu " +"anda tasarlandığı gibi çalışıyor - bu alanların her zaman bir değere sahip " +"olduğundan emin olmak isteyebilirsiniz (metin alanlarında `` `` bir " +"değerdir!)." -#: ../settings/branding.rst:16 +#: ../misc/variables.rst:20 +msgid "Variable Categories" +msgstr "Değişken Kategoriler" + +#: ../misc/variables.rst:31 #, fuzzy -msgid "Defines the logo of the application, shown in the login page of Zammad." -msgstr "Web arayüzünde gösterilen uygulamanın logosunu tanımlar." +msgid "Wait, What About Custom Objects?" +msgstr "Bekle, peki ya özelleştirilmiş nesneler?" -#: ../settings/branding.rst:18 +#: ../misc/variables.rst:33 msgid "" -"Ensure to hit the \"Submit\" button after uploading the logo. Otherwise your " -"change will not be saved." +"Good point! Of course, we can't predict what objects you might create, but " +"we can give you a hint on how to put the puzzle together to get your custom " +"values." msgstr "" +"İyi bir nokta! Elbette, hangi nesneleri yaratabileceğinizi tahmin " +"edemiyoruz, ancak özel değerlerinizi elde etmek için bulmacayı nasıl bir " +"araya getireceğiniz konusunda size bir ipucu verebiliriz." -#: ../settings/branding.rst:22 +#: ../misc/variables.rst:36 msgid "" -"Allows to set the default language of the Zammad instance. The here defined " -"locale mostly acts as a fallback for:" +"For this, we'll talk about the inner part of the variable (so everything " +"within ``#{}``), please put the outer part around to have a valid variable. " +"The first part of the variable name consist of the object type. Currently " +"these are:" msgstr "" +"Bunun için değişkenin iç kısmından bahsedeceğiz (yani ``#{}`` içindeki her " +"şey), lütfen dış kısmı geçerli bir değişkene sahip olacak şekilde " +"yerleştirin. Değişken adının ilk kısmı nesne türünden oluşur. Şu anda bunlar:" -#: ../settings/branding.rst:25 -msgid "user preferences (if Zammad can't detect the users locale)" +#: ../misc/variables.rst:41 +msgid "Ticket (``ticket``)" +msgstr "Bilet (``bilet``)" + +#: ../misc/variables.rst:42 +msgid "User (``user``)" +msgstr "Kullanıcı (``kullanıcı``)" + +#: ../misc/variables.rst:43 +msgid "Organization (``organization``)" +msgstr "Organizasyon (``organizasyon``)" + +#: ../misc/variables.rst:44 +msgid "Group (``group``)" +msgstr "Grup (``grup``)" + +#: ../misc/variables.rst:46 +#, fuzzy +#| msgid "" +#| "The second part is the name of the object. This is the name you define " +#| "during object creation and can be found within the object menu at any " +#| "time. The first and second part of a variable is divided by a point, e." +#| "g.: ``ticket.number`` which will in total be ``#{ticket.number}``." +msgid "" +"The second part is the name of the attribute. This is the name you define " +"during object creation and can be found within the object attribute menu at " +"any time. The first and second part of a variable is divided by a point, e." +"g.: ``ticket.number`` which will in total be ``#{ticket.number}``." msgstr "" +"İkinci kısım nesnenin adıdır. Bu, nesne oluşturma sırasında tanımladığınız " +"addır ve herhangi bir zamanda nesne menüsünde bulunabilir. Bir değişkenin " +"birinci ve ikinci kısmı bir noktayla bölünür, örneğin: \"ticket.number\", " +"toplamda \"#{ticket.number}\" olur." -#: ../settings/branding.rst:26 -msgid "CSV output (reporting, time accounting)" +#: ../misc/variables.rst:51 +msgid "" +"Now, in some situations it's possible that you'll need to use a third part. " +"The best example for such a situation would be a ``select`` or ``tree-" +"select`` field which will by default return the key value, not it's display " +"name. For this, just extend your variable with ``.value``. This will result " +"in ``#{ticket.select.value}``." msgstr "" +"Şimdi, bazı durumlarda üçüncü bir parça kullanmanız gerekebilir. Böyle bir " +"duruma en iyi örnek, varsayılan olarak görünen adını değil, anahtar değerini " +"döndürecek olan bir \"seç\" veya \"ağaç seçimi\" alanıdır. Bunun için " +"değişkeninizi ``.value`` ile genişletin. Bu, ``#{ticket.select.value}`` ile " +"sonuçlanacaktır." -#: ../settings/branding.rst:30 -msgid "Define the timezone of your Zammad installation." +#: ../misc/variables.rst:60 +#, fuzzy +msgid "Using Translated Variables" +msgstr "Çeviriler" + +#: ../misc/variables.rst:62 +msgid "" +"If you want to use a translated variable in triggers or schedulers, you can " +"extend the placeholder like this: ``#{t(ticket.state.name)}``. The ``t`` " +"tells Zammad to search for fitting translated strings. The used output " +"language is based on the system language of Zammad which you can set in the " +"admin panel under :doc:`/settings/branding` or based on the selected locale " +"in the trigger/scheduler edit dialog." msgstr "" -#: ../settings/branding.rst:32 +#: ../misc/variables.rst:69 msgid "" -"This does not have any effect on timings for your agents or how Zammad " -"stores date and time values." +"A possible use-case: you want to send your customers updates on tickets via " +"trigger or scheduler which should include the state of the ticket. Using the " +"default ``#{ticket.state.name}`` (without the translation flag ``t()``) " +"would lead to the output of the original (english) name of the state." msgstr "" -#: ../settings/branding.rst:35 -msgid "Changing this value has direct consequences on the following areas:" +#: ../misc/variables.rst:75 +msgid "Date and Time Formatting" msgstr "" -#: ../settings/branding.rst:37 -msgid ":doc:`/manage/scheduler` tasks" +#: ../misc/variables.rst:77 +msgid "" +"The system (trigger/scheduler selected) locale and timezone predefines a " +"default format of date and timestamp. This format is customizable by using " +"the ``dt()`` method." msgstr "" -#: ../settings/branding.rst:38 -msgid "search indexing (and thus reporting)" +#: ../misc/variables.rst:79 +msgid "The method arguments are as follows:" msgstr "" -#: ../settings/branding.rst:40 +#: ../misc/variables.rst:81 +msgid "The date or timestamp variable you want to format." +msgstr "" + +#: ../misc/variables.rst:82 #, fuzzy -msgid "calendar subscriptions" -msgstr "Açıklama" +msgid "The output format string." +msgstr "``Test`` biçimlendirme olmadan" -#: ../settings/branding.rst:41 -msgid "browser printing" +#: ../misc/variables.rst:83 +msgid "The timezone to apply (optional)." msgstr "" -#: ../settings/branding.rst:43 +#: ../misc/variables.rst:85 +#: ../system/objects/external-data-source-example.rst:23 +#, fuzzy +msgid "**Example:**" +msgstr "Örnek" + +#: ../misc/variables.rst:86 msgid "" -"Please note that some of above are fallbacks in case Zammad could not detect " -"the agents timezone correctly." +"``#{dt(ticket.updated_at, \"%A %Y-%m-%d %H:%M in the office\", \"Europe/" +"Berlin\")}``" msgstr "" -#: ../settings/branding.rst:77 -#, fuzzy -msgid "Pretty Date" -msgstr "*Güzel Tarih*" +#: ../misc/variables.rst:87 +msgid "Monday, 2024-03-18 15:31 in the office" +msgstr "" -#: ../settings/branding.rst:47 -#, fuzzy +#: ../misc/variables.rst:89 msgid "" -"This setting allows you to define how Zammad should display time stamps " -"within the interface to all users." +"If you want to use our example, make sure to paste the string above without " +"formatting (``CTRL+Shift+v``), otherwise it won't work." msgstr "" -"Bu bölüm, yerel kullanıcı hesapları için parola gereksinimlerini " -"tanımlamanıza olanak tanır." -#: ../settings/branding.rst:50 -msgid "" -"This does not have any effect on how Zammad returns e.g. time values via " -"variables." +#: ../misc/variables.rst:93 +msgid "The following table lists available format directives:" msgstr "" -#: ../settings/branding.rst:77 +#: ../misc/variables.rst:99 #, fuzzy -msgid "Choose in between the following options:" -msgstr "Aşağıdaki ayarlardan şunları düzenleyebilirsin:" +msgid "Parameter" +msgstr "Checkmk Parametreleri" -#: ../settings/branding.rst:64 -msgid "relative" +#: ../misc/variables.rst:102 +msgid "``%Y``" msgstr "" -#: ../settings/branding.rst:55 -msgid "" -"This timestamp shows a relative time span until it switches to a date. Over " -"time, it will change as follows:" +#: ../misc/variables.rst:103 +msgid "Year with 4 digits" msgstr "" -#: ../settings/branding.rst:58 -msgid "just now" +#: ../misc/variables.rst:104 +msgid "Use ``%y`` for year with 2 digits" msgstr "" -#: ../settings/branding.rst:59 -msgid "5 minutes ago" +#: ../misc/variables.rst:105 +msgid "``%m``" msgstr "" -#: ../settings/branding.rst:60 -msgid "3 days 1 hour ago" +#: ../misc/variables.rst:106 +msgid "Month of year (as number with zero-padding)" msgstr "" -#: ../settings/branding.rst:61 -msgid "``03/04/2022``" +#: ../misc/variables.rst:107 +msgid "Use ``%-m`` for month without zero-padding" msgstr "" -#: ../settings/branding.rst:63 -msgid "Hovering the timestamp helps, you'll always get a clean timestamp then." +#: ../misc/variables.rst:108 +msgid "``%d``" msgstr "" -#: ../settings/branding.rst:71 -msgid "absolute" +#: ../misc/variables.rst:109 +msgid "Day of month (as number with zero-padding)" msgstr "" -#: ../settings/branding.rst:67 -msgid "" -"This timestamp always includes the week day. For one week after creation, " -"the timestamp will not contain the date itself: Thursday 18:35." +#: ../misc/variables.rst:110 +msgid "Use ``%e`` for day without zero-padding" msgstr "" -#: ../settings/branding.rst:71 -msgid "After a week it will switch to: ``Friday 4. Mar 16:00``." +#: ../misc/variables.rst:111 +msgid "``%H``" msgstr "" -#: ../settings/branding.rst:76 -msgid "timestamp" +#: ../misc/variables.rst:112 +msgid "Hour of day in 24h notation with zero-padding" msgstr "" -#: ../settings/branding.rst:74 -msgid "" -"This will cause Zammad to show a complete timestamp according to your locale " -"defaults. For English this could be e.g. ``2022/12/03 2:40 pm`` or for " -"German e.g. ``12.03.2022 14:40``." +#: ../misc/variables.rst:113 +msgid "Use ``%k`` for hour without zero-padding" msgstr "" -#: ../settings/branding.rst:78 -msgid "Default setting: ``relative``." +#: ../misc/variables.rst:114 +msgid "``%I``" msgstr "" -#: ../settings/security.rst:2 -msgid "Security" -msgstr "Güvenlik" +#: ../misc/variables.rst:115 +msgid "Hour of day in 12h notation with zero-padding" +msgstr "" -#: ../settings/security.rst:4 +#: ../misc/variables.rst:116 msgid "" -"For your overview we split each tab within security settings into its own " -"page:" +"Use ``%l`` for hour without zero-padding and ``%p`` / ``%P`` for meridian " +"indicator" msgstr "" -#: ../settings/security/base.rst:2 ../settings/system/base.rst:2 -#: ../settings/ticket.rst:8 -msgid "Base" -msgstr "Temel" - -#: ../settings/security/base.rst:5 -msgid "New User Accounts" +#: ../misc/variables.rst:117 +msgid "``%M``" msgstr "" -#: ../settings/security/base.rst:9 -msgid "" -"Activates the `register as a new customer` function on the login page. If " -"set to ``no`` only administrators or agents can create new accounts manually." +#: ../misc/variables.rst:118 +msgid "Minute of hour" msgstr "" -#: ../settings/security/base.rst:13 ../settings/security/base.rst:38 -#: ../settings/security/base.rst:66 -msgid "Default setting: ``yes``" +#: ../misc/variables.rst:120 +msgid "``%S``" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing activated \"New User Accounts\" setting" +#: ../misc/variables.rst:121 +msgid "Second of Minute" msgstr "" -#: ../settings/security/base.rst:22 -msgid "" -"Deactivation of above function **does not** deactivate automatic account " -"creation! This means: If a user writes e.g. an email to Zammad and has no " -"account yet, Zammad will automatically create the account. User accounts are " -"a direct dependency of tickets and thus technically mandatory." +#: ../misc/variables.rst:123 +msgid "``%A``" msgstr "" -#: ../settings/security/base.rst:29 -msgid "Lost Password" +#: ../misc/variables.rst:124 +msgid "Weekday name" msgstr "" -#: ../settings/security/base.rst:33 -msgid "" -"Activates the `lost password` function on the login page. If set to ``no`` " -"only administrators may change the user's password - users may update their " -"own password if they're still logged in and they have the required :doc:" -"`permission `." +#: ../misc/variables.rst:125 +msgid "Use ``%a`` for abbreviated name or ``%^A`` for uppercase name" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing activated \"Lost Password\" setting" +#: ../misc/variables.rst:126 +msgid "``%B``" msgstr "" -#: ../settings/security/base.rst:49 -msgid "" -"With third party authentications - but especially LDAP - you may want to " -"disable this function. Zammad **will not** change third party login " -"passwords and instead set or change the local password!" +#: ../misc/variables.rst:127 +msgid "Month name" msgstr "" -#: ../settings/security/base.rst:56 -#, fuzzy -msgid "Password Login" -msgstr "Parola" +#: ../misc/variables.rst:128 +msgid "Use ``%b`` for abbreviated name" +msgstr "" -#: ../settings/security/base.rst:60 -msgid "" -"Activates the username & password login by default and if no third-party " -"login is activated. Disabling password login on the Zammad login page only " -"takes effect if you enable any :doc:`third-party`." +#: ../misc/variables.rst:129 +msgid "``%U``" msgstr "" -#: ../settings/security/base.rst:64 -msgid "See :doc:`third-party` for supported third-party logins." +#: ../misc/variables.rst:130 +msgid "Week number of current year" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing de-activated \"Password Login\" setting" +#: ../misc/variables.rst:131 +msgid "Use ``%W`` for a different calculation method" msgstr "" -#: ../settings/security/base.rst:77 +#: ../misc/variables.rst:134 msgid "" -"To help administrators to overcome \"login issues\", Zammad automatically " -"offers a password request for administrator users. This allows you to adjust " -"Third-Party applications even if the login does no longer work!" +"We support the known format directives for the Ruby built-in method " +"``strftime`` of the ``DateTime`` class. For more information, see `here " +"`_." msgstr "" -#: ../settings/security/base.rst:84 -msgid "Session Timeout" -msgstr "" +#: ../misc/variables/article.rst:2 +msgid "Articles" +msgstr "Makaleler" -#: ../settings/security/base.rst:86 +#: ../misc/variables/article.rst:4 ../misc/variables/config.rst:4 +#: ../misc/variables/current-user.rst:4 ../misc/variables/ticket.rst:4 msgid "" -"All settings below by default are set to ``4 weeks``. Session Timeout " -"defines the life time of a users session. As soon as it's reached, Zammad " -"will automatically log off the session in question." +"If you're missing variables or are not sure if something is not working as " +"expected, feel free to ask over at the `Community `_." msgstr "" +"Değişkenleri kaçırıyorsanız veya bir şeyin beklendiği gibi çalışmadığından " +"emin değilseniz, `Toplulukta `_ soru sormaktan çekinmeyin." -#: ../settings/security/base.rst:91 +#: ../misc/variables/article.rst:6 +#, fuzzy +#| msgid "" +#| "Below you can find all available ticket article-based variables within " +#| "Zammad. These can be called via Triggers for example. If you're unsure if " +#| "Zammad does support variables at the point you're at, you can try to type " +#| "``::`` to check." msgid "" -"Zammad takes the highest value set assigned for the user based on the " -"permissions." +"Below you can find all available ticket article-based variables within " +"Zammad. These can be called via triggers for example. If you're unsure if " +"Zammad does support variables at the point you're at, you can try to type " +"``::`` to check." msgstr "" +"Aşağıda, Zammad içindeki tüm bilet tabanlı değişkenleri bulabilirsiniz. " +"Bunlar örneğin Tetikleyiciler aracılığıyla çağrılabilir. Bulunduğunuz " +"noktada Zammad'ın değişkenleri destekleyip desteklemediğinden emin " +"değilseniz, kontrol etmek için ``::`` yazmayı deneyebilirsiniz." -#: ../settings/security/base.rst:94 -msgid "``admin``" +#: ../misc/variables/article.rst:9 ../misc/variables/config.rst:9 +#: ../misc/variables/ticket.rst:9 +msgid "" +"The below list gives you an example what kind of data you can expect, it's " +"not intended to explain the data itself." msgstr "" +"Aşağıdaki liste size ne tür veriler bekleyebileceğinize dair bir örnek " +"verir, verilerin kendisini açıklama amacı taşımaz." -#: ../settings/security/base.rst:96 -msgid "``ticket.customer``" -msgstr "" +#: ../misc/variables/article.rst:11 +msgid "Article Variables" +msgstr "Makale Değişkenleri" -#: ../settings/security/base.rst:97 -msgid "``default`` (fallback if user doesn't have above permissions set)" -msgstr "" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "name" +msgstr "ad" -#: ../settings/security/base.rst:99 -msgid "" -"All settings act independently from each other allowing you to disable the " -"timeouts for e.g. admins, but not agents." -msgstr "" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "variable" +msgstr "değişken" -#: ../settings/security/base.rst:115 -#: ../system/integrations/checkmk/api-reference.rst:13 -msgid "Example" -msgstr "Örnek" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "example" +msgstr "örnek" -#: ../settings/security/base.rst:107 -msgid "Let's suppose you configured the following session timeouts" -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "Article > Cc" +msgstr "Makale > Cc" -#: ../settings/security/base.rst:104 -msgid "default: 3 weeks" -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "``#{article.cc}``" +msgstr "``#{article.cc}``" -#: ../settings/security/base.rst:105 -msgid "admin: 2 weeks" -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "``jdoe@example.com, company@example.com``" +msgstr "``jdoe@example.com, company@example.com``" -#: ../settings/security/base.rst:106 -msgid "ticket.agent: 4 weeks" -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Address" +msgstr "Makale > Oluşturan > Adres" -#: ../settings/security/base.rst:107 -msgid "ticket.customer: 1 week" -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.address}``" +msgstr "``#{article.created_by.address}``" -#: ../settings/security/base.rst:115 -msgid "This results in the following situations" +#: ../misc/variables/article.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set in user object" msgstr "" +"``Örnek cadde 1, 12345 Berlin`` veya kullanıcı nesnesinde ayarlanmadıysa boş" -#: ../settings/security/base.rst:110 -msgid "a user with ``admin`` permission will have a timeout of 2 weeks" -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Department" +msgstr "Makale > Oluşturan > Bölüm" -#: ../settings/security/base.rst:111 -msgid "" -"a user with ``admin`` and ``ticket.agent`` permissions will have a timeout " -"of 2 weeks" -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.department}``" +msgstr "``#{article.created_by.department}``" -#: ../settings/security/base.rst:113 -msgid "" -"a user with ``ticket.customer`` permission will have a timeout of 1 week" -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "``Sales`` or empty if not set in user object" +msgstr "``Satışlar`` veya kullanıcı nesnesinde ayarlanmadıysa boş" -#: ../settings/security/base.rst:115 -msgid "" -"a user with neither ``admin``, ``ticket.agent`` nor ``ticket.customer`` " -"permissions will have a timeout of 3 weeks" -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Email" +msgstr "Makale > Oluşturan > E-posta" -#: ../settings/security/password.rst:4 -msgid "" -"This section allows you to define password requirements for the local user " -"accounts." -msgstr "" -"Bu bölüm, yerel kullanıcı hesapları için parola gereksinimlerini " -"tanımlamanıza olanak tanır." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.email}``" +msgstr "``#{article.created_by.email}``" -#: ../settings/security/password.rst:9 -msgid "" -"Zammad does **not** allow you to change your LDAP password, instead, it will " -"set a password in its local database which might confuse your users. This " -"might be addressed in the future by `#1169 `_." -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "``jdoe@example.com``" +msgstr "``jdoe@example.com``" -#: ../settings/security/password.rst:14 -msgid "**Exception for admins**" -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Fax" +msgstr "Makale > Oluşturan > Faks" -#: ../settings/security/password.rst:16 -msgid "" -"Please note that below password policies *do not* affect administrators " -"setting passwords on user accounts. While this seems strange and not safe we " -"believe that an administrator knowing an user's password is insecure as well." -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.fax}``" +msgstr "``#{article.created_by.fax}``" -#: ../settings/security/password.rst:21 -msgid "The suggested workflow is either:" -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "``+4930123456789`` or empty if not set in user object" +msgstr "``+4930123456789`` veya kullanıcı nesnesinde ayarlanmadıysa boş" -#: ../settings/security/password.rst:23 -msgid "" -"to use third party logins to not require local passwords at all **- or -**" -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Firstname" +msgstr "Makale > Oluşturan > Ad" -#: ../settings/security/password.rst:25 -msgid "to require your *user to reset the password* upon first login." -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.firstname}``" +msgstr "``#{article.created_by.firstname}``" -#: ../settings/security/password.rst:27 -msgid "" -"This way administrators are not required to set a user's password at all!" -msgstr "" +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Joe`` or empty if not set" +msgstr "``Joe`` veya ayarlanmadıysa boş" -#: ../settings/security/password.rst:31 -#, fuzzy -msgid "Maximum Failed Logins" -msgstr "Maksimum başarısız giriş" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Lastname" +msgstr "Makale > Oluşturan > Soyadı" -#: ../settings/security/password.rst:33 -msgid "" -"You can choose a value between ``4`` and ``20``. This defines how often a " -"login to a user account may fail until Zammad will lock it. Your users can " -"always use the \"forgot password\" function to change their password and " -"unlock their account." -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.lastname}``" +msgstr "``#{article.created_by.lastname}``" -#: ../settings/security/password.rst:38 -msgid "The default value is ``10``." -msgstr "" +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +#: ../misc/variables/ticket.rst:1 +msgid "``Doe`` or empty if not set" +msgstr "``Doe`` veya ayarlanmadıysa boş" -#: ../settings/security/password.rst:42 -msgid "Beside changing the user's password, you can also unlock accounts via" -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Login" +msgstr "Makale > Oluşturan > Giriş" -#: ../settings/security/password.rst:44 -msgid ":ref:`user management list `" -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.login}``" +msgstr "``#{article.created_by.login}``" -#: ../settings/security/password.rst:45 -msgid ":docs:`console `" -msgstr "" +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +#: ../misc/variables/ticket.rst:1 +msgid "``jdoe``" +msgstr "``jdoe``" -#: ../settings/security/password.rst:46 -msgid ":docs:`API `" -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Mobile" +msgstr "Makale > Oluşturan > Mobil" -#: ../settings/security/password.rst:50 -msgid "Failed logins via LDAP no longer lock accounts." -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.mobile}``" +msgstr "``#{article.created_by.mobile}``" -#: ../settings/security/password.rst:53 -#, fuzzy -msgid "2 Lower Case And 2 Upper Case Characters" -msgstr "2 küçük ve 2 büyük karakter" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Note" +msgstr "Makale > Oluşturan > Not" -#: ../settings/security/password.rst:55 -msgid "" -"You can add complexity to passwords by enforcing at least 2 upper and lower " -"case characters." -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.note}``" +msgstr "``#{article.created_by.note}``" -#: ../settings/security/password.rst:58 ../settings/security/password.rst:83 -msgid "The default value is ``no``." +#: ../misc/variables/article.rst:1 +msgid "``Some note about user`` or empty if not set in user object" msgstr "" +"``Kullanıcı hakkında örnek not`` veya kullanıcı nesnesinde ayarlanmadıysa boş" -#: ../settings/security/password.rst:62 -#, fuzzy -msgid "Minimum Length" -msgstr "Minimum uzunluk" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Phone" +msgstr "Makale > Oluşturan > Telefon" -#: ../settings/security/password.rst:64 -msgid "" -"This defines the minimum password length required for users to provide (from " -"``4`` to ``20``)." -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.phone}``" +msgstr "``#{article.created_by.phone}``" -#: ../settings/security/password.rst:67 -msgid "The default value is ``6``." -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > VIP" +msgstr "Makale > Oluşturan > VIP" -#: ../settings/security/password.rst:71 -#, fuzzy -msgid "Digit Required" -msgstr "Rakam gerekli" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.vip}``" +msgstr "``#{article.created_by.vip}``" -#: ../settings/security/password.rst:73 -msgid "This enforces your users to use at least one digit within the password." -msgstr "" +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +msgid "``true`` or ``false``" +msgstr "``doğru`` veya ``yanlış``" -#: ../settings/security/password.rst:75 -msgid "The default value is ``yes``." -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Web" +msgstr "Makale > Oluşturan > Web" -#: ../settings/security/password.rst:78 -msgid "Special Character Required" -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.web}``" +msgstr "``#{article.created_by.web}``" -#: ../settings/security/password.rst:80 -msgid "" -"This setting allows you to improve your password quality even more by " -"enforcing the password to contain at least one special character." -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "``https://zammad.com`` or empty if not set in user object" +msgstr "``https://zammad.com``` veya kullanıcı nesnesinde ayarlanmadıysa boş" -#: ../settings/security/ssl-certificates.rst:2 -#, fuzzy -msgid "SSL Certificates" -msgstr "Sertifika Ekle" +#: ../misc/variables/article.rst:1 +msgid "Article > Created" +msgstr "Makale > Oluşturulan" -#: ../settings/security/ssl-certificates.rst:7 -msgid "" -"Zammad offers the possibility to upload custom certificates and custom " -"Certificate Authority (CA) certificates. This can be useful if you want to " -"connect Zammad the secure way to other systems which are using custom " -"certificates." -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_at}``" +msgstr "``#{article.created_at}``" -#: ../settings/security/ssl-certificates.rst:12 -msgid "" -"An example usecase might be: You have an internal LDAP server that is not " -"accessible from the internet, and you want a SSL-encrypted connection, using " -"a custom certificate." -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "``2019-10-08 15:24:47 UTC``" +msgstr "``2019-10-08 15:24:47 UTC``" -#: ../settings/security/ssl-certificates.rst:19 -msgid "" -"You should have an existing custom certificate file and/or a custom CA " -"certificate file, which you want to add to Zammad. As filetype ``.crt`` is " -"supported and the certificate format has to be PEM (Base64 ASCII)." -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "Article > From" +msgstr "Makale > Kimden" -#: ../settings/security/ssl-certificates.rst:25 +#: ../misc/variables/article.rst:1 +msgid "``#{article.from}``" +msgstr "``#{article.from}``" + +#: ../misc/variables/article.rst:1 msgid "" -"When you import a custom CA certificate, all certificates generated with " -"this are trusted. This can be useful if you have more than one system/" -"certificate you want to connect to and the certificates are issued from the " -"same custom CA." +"``Joe Doe `` may differ, depends on ``FROM`` of send mail" msgstr "" +"``Joe Doe`` farklılık gösterebilir, postanın ``KİMDEN``olduğuna bağlıdır" -#: ../settings/security/ssl-certificates.rst:31 -#, fuzzy -msgid "Add a Certificate" -msgstr "Sertifika Ekle" +#: ../misc/variables/article.rst:1 +msgid "Article > Sender > Name" +msgstr "Makale > Gönderen > Ad" -#: ../settings/security/ssl-certificates.rst:33 -msgid "" -"To add a custom certificate or a custom CA certificate, head over to the " -"Admin panel > Settings > Security > SSL Certificates. Here you can find a " -"\"Add SSL Certificate\" button. In the dialog you can either select a " -"certificate file or paste the content of the certificate:" -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "``#{article.sender.name}``" +msgstr "``#{article.sender.name}``" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate adding dialog" -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "``Customer``, ``Agent`` or ``System``" +msgstr "``Müşteri``, ``Aracı`` veya ``Sistem``" -#: ../settings/security/ssl-certificates.rst:43 -msgid "" -"After selecting a file or pasting the content of the certificate, click on " -"the \"Add\" button to finally upload it to Zammad. Then, the certificates " -"are immediately effective, no restart or similar required." -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "Article > Subject" +msgstr "Makale > Konu" -#: ../settings/security/ssl-certificates.rst:49 -msgid "" -"Please note that only single certificate files are supported. That means if " -"you want to import a certificate / CA certificate, it must contain **only " -"one** certificate." -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "``#{article.subject}``" +msgstr "``#{article.subject}``" -#: ../settings/security/ssl-certificates.rst:54 -#, fuzzy -msgid "Certificate Overview" -msgstr "Sertifika Ekle" +#: ../misc/variables/article.rst:1 +msgid "``My amazing subject``" +msgstr "``Benim harika konum``" -#: ../settings/security/ssl-certificates.rst:56 -msgid "" -"After you added a certificate, you can see a table with information for each " -"added certificate:" -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "Article > Text" +msgstr "Makale > Metin" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing table of added certificates" -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "``#{article.body}``" +msgstr "``#{article.body}``" -#: ../settings/security/ssl-certificates.rst:64 -msgid "" -"Here you can download the certificate or delete it, if you don't need it " -"anymore." -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "``Test`` without formatting (plain)" +msgstr "``Test`` biçimlendirme olmadan (düz)" -#: ../settings/security/ssl-certificates.rst:68 -#, fuzzy -msgid "Deleting Certificates" -msgstr "Sertifika Ekle" +#: ../misc/variables/article.rst:1 +msgid "Article > TicketID" +msgstr "Makale > BiletID" -#: ../settings/security/ssl-certificates.rst:70 -msgid "" -"If you want to delete a specific certificate, you can do it by clicking on " -"the menu in the actions column and selecting delete:" -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "``#{article.ticket_id}``" +msgstr "``#{article.ticket_id}``" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate deletion button" -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "``1`` (not ticket number)" +msgstr "``1`` (bilet numarası değil)" -#: ../settings/security/ssl-certificates.rst:79 -#, fuzzy -msgid "Downloading Certificates" -msgstr "Sertifika Ekle" +#: ../misc/variables/article.rst:1 +msgid "Article > To" +msgstr "Makale > Kime" -#: ../settings/security/ssl-certificates.rst:81 -msgid "" -"If you want to download your certificates, you can do this as well via " -"corresponding action buttons." -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "``#{article.to}``" +msgstr "``#{article.to}``" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate download button" -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "``helpdesk@example.com``" +msgstr "``helpdesk@example.com``" -#: ../settings/security/third-party.rst:13 -msgid "Login Providers" -msgstr "Giriş Sağlayıcılar" +#: ../misc/variables/article.rst:1 +msgid "Article > Type > Name" +msgstr "Makale > Tür > Ad" -#: ../settings/security/third-party.rst:2 -msgid "Third-Party Applications" -msgstr "Üçüncü Parti Uygulamalar" +#: ../misc/variables/article.rst:1 +msgid "``#{article.type.name}``" +msgstr "``#{article.type.name}``" -#: ../settings/security/third-party.rst:4 +#: ../misc/variables/article.rst:1 msgid "" -"Third party authentication is a great way to help your users to login to " -"Zammad more easily. If the account is yet unknown, Zammad will create a new " -"user automatically, without the user needed to interact (e.g. type in his " -"name). Another big advantage of this feature is that your user doesn't need " -"to remember another password." +"``email`` (`list of article types `_)" msgstr "" +"``e-posta`` (`makale türlerinin listesi `_)" -#: ../settings/security/third-party.rst:10 -msgid "" -"You can deactivate logging in via :ref:`security_password_login` if any of " -"the mentioned authentication providers are enabled in your instance." -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Address" +msgstr "Makale > Güncelleyen > Adres" -#: ../settings/security/third-party.rst:27 -msgid "" -"We're currently missing documentation for the following login providers:" -msgstr "Şu anda aşağıdaki oturum açma sağlayıcıları için belgelerimiz yok:" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.address}``" +msgstr "``#{article.updated_by.address}``" -#: ../settings/security/third-party.rst:29 -msgid "LinkedIn" -msgstr "LinkedIn" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Department" +msgstr "Makale > Güncelleyen > Bölüm" -#: ../settings/security/third-party.rst:30 -msgid "Weibo" -msgstr "Weibo" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.department}``" +msgstr "``#{article.updated_by.department}``" -#: ../settings/security/third-party.rst:35 -#, fuzzy -msgid "Automatic Account Link on Initial Logon" -msgstr "İlk oturum açmada otomatik hesap bağlantısı" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Email" +msgstr "Makale > Güncelleyen > E-posta" -#: ../settings/security/third-party.rst:37 -msgid "" -"In general there's two possible options for Zammad on how to deal with " -"already known users as they try to authenticate against a third-party " -"application. By default, Zammad will not automatically link \"unknown\" " -"authentication providers to existing accounts." -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.email}``" +msgstr "``#{article.updated_by.email}``" -#: ../settings/security/third-party.rst:42 -msgid "" -"This means that the user has to manually link authentication providers to " -"their accounts (for more about this :user-docs:`consult the user " -"documentation `)." -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Fax" +msgstr "Makale > Güncelleyen > Faks" -#: ../settings/security/third-party.rst:46 -msgid "" -"Sometimes this doesn't come in handy as this also means you'll receive error " -"messages about \"email address being in use already\" for (yet) unknown " -"third-party authentication methods." -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.fax}``" +msgstr "``#{article.updated_by.fax}``" -#: ../settings/security/third-party.rst:50 -msgid "" -"If you want to allow your users to always be able to log in, no matter what, " -"you may want to enable ``Automatic account link on initial logon``." -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Firstname" +msgstr "Makale > Güncelleyen > Ad" -#: ../settings/security/third-party.rst:None -#, fuzzy -msgid "" -"Screenshot highlighting the \"Automatic account link on initial logon\"\n" -"setting" -msgstr "İlk oturum açmada otomatik hesap bağlantısı" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.firstname}``" +msgstr "``#{article.updated_by.firstname}``" -#: ../settings/security/third-party.rst:60 -#, fuzzy -msgid "Automatic Account Linking Notification" -msgstr "İlk oturum açmada otomatik hesap bağlantısı" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Lastname" +msgstr "Makale > Güncelleyen > Soyad" -#: ../settings/security/third-party.rst:64 -msgid "" -"To improve security and your users awareness, you can enable Zammad to " -"notify your users when a new third-party application has been linked to " -"their account." -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.lastname}``" +msgstr "``#{article.updated_by.lastname}``" -#: ../settings/security/third-party.rst:68 -msgid "" -"This notification is sent out once per third-party application. Zammad does " -"also mention the method used, e.g.: ``Microsoft``." -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Login" +msgstr "Makale > Güncelleyen > Giriş" -#: ../settings/security/third-party.rst:71 -msgid "By default this setting is not active (set to ``no``)." -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.login}``" +msgstr "``#{article.updated_by.login}``" -#: ../settings/security/third-party.rst:0 -msgid "" -"Screenshot showing sample notification mail after initial\n" -"third-party linking" -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Mobile" +msgstr "Makale > Güncelleyen > Mobil" -#: ../settings/security/third-party.rst:85 -msgid "" -"This notification is only sent if the account in question already exists. If " -"the login via the third-party also creates the missing account, the " -"notification will be skipped." -msgstr "" - -#: ../settings/security/third-party.rst:89 -msgid "This means it only affects:" -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.mobile}``" +msgstr "``#{article.updated_by.mobile}``" -#: ../settings/security/third-party.rst:91 -msgid "manual account linking within the third-party page of the users profile" -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Note" +msgstr "Makale > Güncelleyen > Not" -#: ../settings/security/third-party.rst:92 -msgid "" -"logging into an existing local account by utilizing the *automatic account " -"link on initial logon* functionality" -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.note}``" +msgstr "``#{article.updated_by.note}``" -#: ../settings/security/third-party.rst:None -msgid "" -"Screenshot showing the \"automatic account linking notification\"\n" -"setting" -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Phone" +msgstr "Makale > Güncelleyen > Telefon" -#: ../settings/security/third-party.rst:100 -msgid "No User Creation on Logon" -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.phone}``" +msgstr "``#{article.updated_by.phone}``" -#: ../settings/security/third-party.rst:102 -msgid "" -"By default, Zammad will create a new user account if the user logs in via a " -"third-party application and the account doesn't exist yet." -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > VIP" +msgstr "Makale > Güncelleyen > VIP" -#: ../settings/security/third-party.rst:105 -msgid "" -"If you want to prevent Zammad from creating new accounts on logon, you can " -"disable this feature by setting ``No user creation on logon`` to ``yes``." -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.vip}``" +msgstr "``#{article.updated_by.vip}``" -#: ../settings/security/third-party.rst:None -#, fuzzy -msgid "Screenshot showing the \"no user creation on logon\" setting" -msgstr "İlk oturum açmada otomatik hesap bağlantısı" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Web" +msgstr "Makale > Güncelleyen > Web" -#: ../settings/security/third-party/facebook.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via Facebook To do " -"so, you need to follow these steps:" -msgstr "" -"Facebook üzerinden yardım masanız için hızlı bir giriş oluşturmak mümkündür. " -"Bunu yapmak için şu adımları izlemeniz gerekir:" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.web}``" +msgstr "``#{article.updated_by.web}``" -#: ../settings/security/third-party/facebook.rst:9 -#, fuzzy -msgid "Register Facebook App" -msgstr "Facebook uygulamasına kaydol" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated" +msgstr "Makale > Güncellenen" -#: ../settings/security/third-party/facebook.rst:11 -msgid "" -"Visit [https://developers.facebook.com/apps/] and click on \"Add a new App\"" -msgstr "" -"[https://developers.facebook.com/apps/] adresini ziyaret edin ve \"Yeni " -"Uygulama Ekle\"yi tıklayın" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_at}``" +msgstr "``#{article.updated_at}``" -#: ../settings/security/third-party/facebook.rst:None -msgid "initial page" -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "Article > Visibility" +msgstr "Makale > Görünürlük" -#: ../settings/security/third-party/facebook.rst:17 -msgid "After that enter the app settings" -msgstr "Bundan sonra uygulama ayarlarını girin" +#: ../misc/variables/article.rst:1 +msgid "``#{article.internal}``" +msgstr "``#{article.internal}``" -#: ../settings/security/third-party/facebook.rst:None -msgid "Create App" -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "``false`` or ``true`` (false if not internal)" +msgstr "``yanlış`` veya ``doğru`` (dahili değilse yanlış)" -#: ../settings/security/third-party/facebook.rst:22 -msgid "Navigate to \"Settings\" and fill in this infromation" -msgstr "\"Ayarlar\"a gidin ve bu bilgileri doldurun" +#: ../misc/variables/article.rst:1 +msgid "Article Text as HTML (not referenced)" +msgstr "HTML olarak Makale Metni (referans değil)" -#: ../settings/security/third-party/facebook.rst:None -msgid "App Settings" -msgstr "" +#: ../misc/variables/article.rst:1 +msgid "``#{article.body_as_html}``" +msgstr "``#{article.body_as_html}``" -#: ../settings/security/third-party/facebook.rst:27 -msgid "Navigate to app review and Check \"Make [appname] public?\"" -msgstr "" -"Uygulama incelemesine gidin ve \"[uygulama adı] herkese açık hale getirilsin " -"mi?\" seçeneğini işaretleyin." +#: ../misc/variables/article.rst:1 +msgid "``Test`` with formatting" +msgstr "``Test`` biçimlendirme olmadan" -#: ../settings/security/third-party/facebook.rst:None -msgid "App Review" -msgstr "" +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "Ticket > Article#" +msgstr "Bilet > Makale#" -#: ../settings/security/third-party/facebook.rst:35 -#, fuzzy -msgid "Configure Zammad as Facebook App" -msgstr "Zammad'ı Facebook uygulaması olarak yapılandır" +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "``#{ticket.article_count}``" +msgstr "``#{ticket.article_count}``" -#: ../settings/security/third-party/facebook.rst:37 -#, fuzzy -msgid "" -"Navigate to \"Admin -> Security -> Third Party Applications\" and enter the " -"App ID and the App Secret. You can find this Key in the Dashbard of your " -"Facebok app." -msgstr "" -"\"Yönetici -> Güvenlik -> Üçüncü Taraf Uygulamaları\"na gidin ve Uygulama " -"Kimliğini ve Uygulama Sırrını girin. Bu Anahtarı Facebook uygulamanızın " -"Kontrol Panelinde bulabilirsiniz." +#: ../misc/variables/article.rst:1 +msgid "``1`` number of ticket articles" +msgstr "``1`` bilet makalelerinin numarası" -#: ../settings/security/third-party/facebook.rst:None -msgid "Zammad Configuration" -msgstr "" +#: ../misc/variables/config.rst:2 +msgid "Config" +msgstr "Yapılandırma" -#: ../settings/security/third-party/facebook.rst:44 -#: ../settings/security/third-party/github.rst:43 -#: ../settings/security/third-party/gitlab.rst:46 +#: ../misc/variables/config.rst:6 msgid "" -"Now you can link accounts via \"Avatar -> Profile -> Link Accounts\" or " -"login via Zammad login page." +"Below you'll find config related variables. These hold useful configuration " +"information that you can use within e.g. triggers to show necessary " +"information to your customer." msgstr "" -"Artık \"Avatar -> Profil -> Hesapları Bağla\" yoluyla hesapları bağlayabilir " -"veya Zammad giriş sayfası üzerinden giriş yapabilirsiniz." +"Aşağıda yapılandırmayla ilgili değişkenleri bulacaksınız. Bu değişkenler, " +"yararlı yapılandırma bilgilerini saklar ve müşterinize göstermeniz gereken " +"bilgiler için tetikleyicileri kullanabilirsiniz." -#: ../settings/security/third-party/github.rst:2 -#: ../system/integrations/github.rst:2 -msgid "GitHub" -msgstr "GitHub" +#: ../misc/variables/config.rst:11 +msgid "Config Variables" +msgstr "Yapılandırma Değişkenleri" -#: ../settings/security/third-party/github.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via GitHub. To " -"activate the quick login you need to enable OAuth for GitHub." -msgstr "" -"GitHub üzerinden yardım masanız için hızlı giriş oluşturmanız mümkündür. " -"Hızlı oturum açmayı etkinleştirmek için GitHub için OAuth'u etkinleştirmeniz " -"gerekir." +#: ../misc/variables/config.rst:1 +msgid "Config > Fully Qualified Domain Name" +msgstr "Yapılandırma > Tam Tanımlanmış Alan Adı" -#: ../settings/security/third-party/github.rst:8 -#, fuzzy -msgid "Register GitHub App" -msgstr "GitHub uygulamasına kaydol" +#: ../misc/variables/config.rst:1 +msgid "``#{config.fqdn}``" +msgstr "``#{config.fqdn}``" -#: ../settings/security/third-party/github.rst:10 -msgid "" -"Visit https://www.github.com/settings/applications/new and enter the app " -"settings. As callback URL enter \"https://zammad_host/auth/github/callback\" " -"where zammad_host has to be replaced with your Zammad FQDN" -msgstr "" -"https://www.github.com/settings/applications/new adresini ziyaret edin ve " -"uygulama ayarlarını girin. Geri arama URL'si olarak \"https://zammad_host/" -"auth/github/callback\" girin, burada zammad_host'un Zammad FQDN'nizle " -"değiştirilmesi gerekir" +#: ../misc/variables/config.rst:1 +msgid "``zammad.example.com``" +msgstr "``zammad.example.com``" -#: ../settings/security/third-party/github.rst:None -msgid "Register OAuth app on www.github.com" -msgstr "" +#: ../misc/variables/config.rst:1 +msgid "Config > HTTP type" +msgstr "Yapılandırma > HTTP türü" -#: ../settings/security/third-party/github.rst:19 -#, fuzzy -msgid "Configure Zammad as GitHub App" -msgstr "Zammad'ı GitHub uygulaması olarak yapılandır" +#: ../misc/variables/config.rst:1 +msgid "``#{config.http_type}``" +msgstr "``#{config.http_type}``" -#: ../settings/security/third-party/github.rst:21 -msgid "" -"Enter the \"APP ID\" and the \"APP SECRET\" from the GitHub OAUTH " -"Applications Dashboard" -msgstr "" +#: ../misc/variables/config.rst:1 +msgid "``https`` or ``http``" +msgstr "``https`` veya ``http``" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub config in Zammad admin interface" -msgstr "" +#: ../misc/variables/config.rst:1 +msgid "Config > Organization" +msgstr "Yapılandırma > Organizasyon" -#: ../settings/security/third-party/github.rst:28 +#: ../misc/variables/config.rst:1 +msgid "``#{config.organization}``" +msgstr "``#{config.organization}``" + +#: ../misc/variables/config.rst:1 msgid "" -"After you configured the GitHub credentials and activated the login method, " -"you should see a new icon on the login page." -msgstr "" +"``Zammad GmbH`` value set in `Branding `_" +msgstr "`Markalama `_da ``Zammad GmbH`` değer ayarı" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub logo on login page" -msgstr "" +#: ../misc/variables/config.rst:1 +msgid "Config > Product Name" +msgstr "Yapılandırma > Ürün Adı" -#: ../settings/security/third-party/github.rst:34 +#: ../misc/variables/config.rst:1 +msgid "``#{config.product_name}``" +msgstr "``#{config.product_name}``" + +#: ../misc/variables/config.rst:1 msgid "" -"If you click on the icon you will be redirected to GitHub and see something " -"similar to this:" -msgstr "" +"``Helpdesk`` value set in `Branding `_" +msgstr "`Markalama `_da ``Helpdesk`` değer ayarı" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub oauth page" -msgstr "" +#: ../misc/variables/config.rst:1 +msgid "Config > SystemID" +msgstr "Yapılandırma > SistemID" -#: ../settings/security/third-party/github.rst:40 -#: ../settings/security/third-party/gitlab.rst:42 -msgid "" -"When you grant the access you will be redirected to your Zammad instance and " -"logged in as a customer." -msgstr "" +#: ../misc/variables/config.rst:1 +msgid "``#{config.system_id}``" +msgstr "``#{config.system_id}``" -#: ../settings/security/third-party/gitlab.rst:2 -msgid "Gitlab" -msgstr "Gitlab" +#: ../misc/variables/config.rst:1 +msgid "``31`` (value between 1 and 99)" +msgstr "``31`` (1 ve 99 arasında değer)" -#: ../settings/security/third-party/gitlab.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via Gitlab. To " -"activate the quick login you need to enable OAuth for Gitlab." -msgstr "" +#: ../misc/variables/config.rst:1 +msgid "Config > Ticket Hook" +msgstr "Yapılandırma > Bilet Kancası" -#: ../settings/security/third-party/gitlab.rst:8 -#, fuzzy -msgid "Register Gitlab App" -msgstr "Gitlab uygulamasına kaydol" - -#: ../settings/security/third-party/gitlab.rst:10 -msgid "To register an app in Gitlab open your profile and select applications." -msgstr "" +#: ../misc/variables/config.rst:1 +msgid "``#{config.ticket_hook}``" +msgstr "``#{config.ticket_hook}``" -#: ../settings/security/third-party/gitlab.rst:12 -#, fuzzy -msgid "" -"As callback URL enter \"https://zammad-fqdn/auth/gitlab/callback\" where " -"zammad-fqdn has to be replaced with your Zammad FQDN" -msgstr "" -"https://www.github.com/settings/applications/new adresini ziyaret edin ve " -"uygulama ayarlarını girin. Geri arama URL'si olarak \"https://zammad_host/" -"auth/github/callback\" girin, burada zammad_host'un Zammad FQDN'nizle " -"değiştirilmesi gerekir" +#: ../misc/variables/config.rst:1 +msgid "``Ticket#``" +msgstr "``Bilet#``" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Register OAuth app on gitlab instance" -msgstr "" +#: ../misc/variables/current-user.rst:2 +msgid "Current User" +msgstr "Geçerli Kullanıcı" -#: ../settings/security/third-party/gitlab.rst:18 -msgid "Just select *read_user* under scopes as in the screenshot and save it." +#: ../misc/variables/current-user.rst:6 +msgid "" +"Current user variables always return values of the current user that caused " +"e.g. a trigger to run." msgstr "" +"Geçerli kullanıcı değişkenleri her zaman neden olan (ör. çalıştırılan bir " +"tetikleyici) geçerli kullanıcının değerlerini döndürür." -#: ../settings/security/third-party/gitlab.rst:21 +#: ../misc/variables/current-user.rst:8 #, fuzzy -msgid "Configure Zammad as Gitlab App" -msgstr "Zammad'ı Gitlab uygulaması olarak yapılandır" - -#: ../settings/security/third-party/gitlab.rst:23 msgid "" -"Enter the \"APP ID\" and the \"APP SECRET\" from the Gitlab OAUTH " -"Applications Dashboard and your Gitlab-URL in the \"SITE\" field." -msgstr "" - -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab config in Zammad admin interface" +"Due to the above fact, these variables are often not (yet) set or available " +"for usage." msgstr "" +"Yukarıdaki gerçek nedeniyle, bu değişkenler genellikle (henüz) " +"ayarlanmamıştır veya kullanım için uygun değildir." -#: ../settings/security/third-party/gitlab.rst:30 +#: ../misc/variables/current-user.rst:10 msgid "" -"After you configured the Gitlab credentials and activated the login method, " -"you should see a new icon on the login page." +"In situations where e.g. schedulers or triggers run, this most likely is " +"nothing you want to use." msgstr "" +"Aşağıdaki durumlarda ör. zamanlayıcılar veya tetikleyiciler çalışır, bu " +"büyük olasılıkla kullanmak istediğiniz bir şey değildir." -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab logo on login page" -msgstr "" +#: ../misc/variables/current-user.rst:13 +msgid "Current User Variables" +msgstr "Geçerli Kullanıcı Değişkenleri" -#: ../settings/security/third-party/gitlab.rst:36 -msgid "" -"If you click on the icon you will be redirected to Gitlab and see something " -"similar to this:" -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Address" +msgstr "Geçerli Kullanıcı > Adres" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab oauth page" -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.address}``" +msgstr "``#{user.address}``" -#: ../settings/security/third-party/google.rst:4 -msgid "" -"With some easy and fast steps, you can enable Zammad to authenticate your " -"users via Google." -msgstr "" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set" +msgstr "`Örnek cadde 1, 12345 Berlin`` veya ayarlanmadıysa boş" -#: ../settings/security/third-party/google.rst:8 +#: ../misc/variables/current-user.rst:1 #, fuzzy -msgid "Register a Google App" -msgstr "Bir Google uygulamasına kaydol" +msgid "Current User > Avatar" +msgstr "Geçerli Kullanıcı > Faks" -#: ../settings/security/third-party/google.rst:10 -msgid "" -"First of all, we need to create a new project - you can skip this step if " -"you already have one." -msgstr "" +#: ../misc/variables/current-user.rst:1 +#, fuzzy +msgid "``#{user.avatar(60,60)}``" +msgstr "``#{user.lastname}``" -#: ../settings/security/third-party/google.rst:15 -msgid "" -"Use this link to create a new project: https://console.cloud.google.com/" -"projectcreate" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "avatar picture with width and height in pixel (e.g. 60,60)" msgstr "" -#: ../settings/security/third-party/google.rst:18 -msgid "" -"Now expand the menu, expand \"APIs & Services\" and select \"Credentials\". " -"Go to the tab \"OAuth consent screen\" first and ensure to fill in the " -"requested information - without doing so you can't create credentials!" -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created at" +msgstr "Geçerli Kullanıcı > Oluşturulma tarihi" -#: ../settings/security/third-party/google.rst:None -msgid "Creating a consent screen" -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_at}``" +msgstr "``#{user.created_at}``" -#: ../settings/security/third-party/google.rst:25 -msgid "" -"After filling in and saving the consent screen information, you can go to " -"the \"Credentials\" tab and create new \"OAuth client ID\"-Credentials." -msgstr "" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC``" +msgstr "``2019-10-07 16:25:00 UTC``" -#: ../settings/security/third-party/google.rst:28 -msgid "" -"Fill in the necessary information as follows and replace ``zammad_host`` " -"with your FQDN:" -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Address" +msgstr "Geçerli Kullanıcı > Oluşturan > Adres" -#: ../settings/security/third-party/google.rst:31 +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.address}``" +msgstr "``#{user.created_by.address}``" + +#: ../misc/variables/current-user.rst:1 #, fuzzy -msgid "**Application type** ``[x] Web application``" -msgstr "**Uygulama türü** ``[x] Web uygulaması``" +msgid "Current User > Created by > Avatar" +msgstr "Geçerli Kullanıcı > Oluşturan > Faks" -#: ../settings/security/third-party/google.rst:34 -msgid "**Authorized JavaScript origins** ``https://zammad_host/``" -msgstr "" +#: ../misc/variables/current-user.rst:1 +#, fuzzy +msgid "``#{user.created_by.avatar(60,60)}``" +msgstr "``#{user.created_by.lastname}``" -#: ../settings/security/third-party/google.rst:37 -msgid "" -"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" -"callback``" -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Department" +msgstr "Geçerli Kullanıcı > Oluşturan > Bölüm" -#: ../settings/security/third-party/google.rst:None -msgid "Adding a new OAuth client ID" -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.department}``" +msgstr "``#{user.created_by.department}``" -#: ../settings/security/third-party/google.rst:43 -msgid "" -"After creating the credentials, go to your Zammad installation and navigate " -"to \"Admin > Security > Third Party Applications\" > Google. Enter your " -"Client ID and Client secret here." -msgstr "" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Sales`` or empty if not set" +msgstr "``Satışlar`` veya ayarlanmadıysa boş" -#: ../settings/security/third-party/google.rst:None -msgid "Zammad" -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Email" +msgstr "Geçerli Kullanıcı > Oluşturan > E-posta" -#: ../settings/security/third-party/google.rst:50 -msgid "After submitting, the login via Google can be used." -msgstr "Gönderdikten sonra, Google ile giriş kullanılabilir." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.email}``" +msgstr "``#{user.created_by.email}``" -#: ../settings/security/third-party/microsoft.rst:2 -#, fuzzy -msgid "Microsoft" -msgstr "Microsoft 365" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``jdoe@customer.tld``" +msgstr "``jdoe@customer.tld``" -#: ../settings/security/third-party/microsoft.rst:4 -msgid "" -"Zammad's Microsoft connection allows your users with Microsoft accounts to " -"login. This works for Azure users as well and can be an alternative to :doc:" -"`/system/integrations/ldap/index`." -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Fax" +msgstr "Geçerli Kullanıcı > Oluşturan > Faks" -#: ../settings/security/third-party/microsoft.rst:10 -msgid "" -"This documentation part does not cover our :doc:`📧 Microsoft 365 email " -"channel `." -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.fax}``" +msgstr "``#{user.created_by.fax}``" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screenshot showing Microsoft login button on Zammad login screen." -msgstr "" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``004930123464789`` or empty if not set" +msgstr "``004930123464789`` veya ayarlanmadıysa boş" -#: ../settings/security/third-party/microsoft.rst:30 -#: ../settings/security/third-party/microsoft.rst:53 -msgid "Supported account types:" -msgstr "Desteklenen hesap türleri:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Firstname" +msgstr "Geçerli Kullanıcı > Oluşturan > Ad" -#: ../settings/security/third-party/microsoft.rst:22 -msgid "" -"Please note that Zammad only supports these account types (App dependent):" -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.firstname}``" +msgstr "``#{user.created_by.firstname}``" -#: ../settings/security/third-party/microsoft.rst:35 -msgid "Avatars of signing in users:" -msgstr "" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``John`` or empty if not set" +msgstr "``John`` veya ayarlanmadıysa boş" -#: ../settings/security/third-party/microsoft.rst:33 -msgid "" -"Zammad currently ignores user avatars. If the user is registered with e.g. " -"Gravatar, Zammad will fetch the avatar from there if enabled. See :doc:" -"`Zammad Image Service ` for more." -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Lastname" +msgstr "Geçerli Kullanıcı > Oluşturan > Soyad" -#: ../settings/security/third-party/microsoft.rst:38 -msgid "Step 1 - Register a Microsoft App for Zammad" -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.lastname}``" +msgstr "``#{user.created_by.lastname}``" -#: ../settings/security/third-party/microsoft.rst:40 -msgid "" -"Login to the `Microsoft Azure Portal `_ and " -"navigate to App registrations to create a new app. Provide the requested " -"information as follows and register your app." -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Login" +msgstr "Geçerli Kullanıcı > Oluşturan > Giriş" -#: ../settings/security/third-party/microsoft.rst:46 -msgid "Name:" -msgstr "Ad:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.login}``" +msgstr "``#{user.created_by.login}``" -#: ../settings/security/third-party/microsoft.rst:45 -msgid "" -"Any meaningful name fitting, this name will be displayed to users trying to " -"authenticate with this app." -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Mobile" +msgstr "Geçerli Kullanıcı > Oluşturan > Mobil" -#: ../settings/security/third-party/microsoft.rst:49 -msgid "Choose one of the above mentioned account types (see Limitations)." -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.mobile}``" +msgstr "``#{user.created_by.mobile}``" -#: ../settings/security/third-party/microsoft.rst:51 -msgid "" -"The correct account type depends on your use case. If you want to use the " -"authentication internal only, choose the first option. If you're unsure, use " -"the \"Help me choose...\" link." -msgstr "" - -#: ../settings/security/third-party/microsoft.rst:58 -msgid "Redirect URI (optional):" -msgstr "" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``0049176123456789`` or empty if not set" +msgstr "``0049176123456789`` veya ayarlanmadıysa boş" -#: ../settings/security/third-party/microsoft.rst:56 -msgid "" -"Select web and provide your callback URL. The callback URL looks like this: " -"``https://zammad.domain.tld/auth/microsoft_office365/callback``" -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Note" +msgstr "Geçerli Kullanıcı > Oluşturan > Not" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to register a Microsoft app" -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.note}``" +msgstr "``#{user.created_by.note}``" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "Within **API permissions** add the following permissions:" -msgstr "" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Some note to this user`` or empty if not set" +msgstr "`Bu kullanıcı için bir not`` veya ayarlanmadıysa boş" -#: ../settings/security/third-party/microsoft.rst:69 -msgid "``User.Read``" -msgstr "``User.Read``" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Phone" +msgstr "Geçerli Kullanıcı > Oluşturan > Telefon" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "Contacts" -msgstr "İletişim" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.phone}``" +msgstr "``#{user.created_by.phone}``" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "``Contacts.Read``" -msgstr "``Contacts.Read``" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``004930123456789`` or empty if not set" +msgstr "``004930123456789`` veya ayarlanmadıysa boş" -#: ../settings/security/third-party/microsoft.rst:73 -msgid "" -"You can find these permissions within *Microsoft Graph → Delegated " -"permissions*." -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > VIP" +msgstr "Geçerli Kullanıcı > Oluşturan > VIP" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to add required API permissions" -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.vip}``" +msgstr "``#{user.created_by.vip}``" -#: ../settings/security/third-party/microsoft.rst:80 -msgid "" -"Within **Certificates & secrets** create a new client secret. Note down the " -"returned secret **value** for later. **Do not** use the secret ID!" -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Web" +msgstr "Geçerli Kullanıcı > Oluşturan > Web" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to create a new app secret" -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.web}``" +msgstr "``#{user.created_by.web}``" -#: ../settings/security/third-party/microsoft.rst:88 -msgid "" -"From **Overview** copy your apps *Application (client) ID*. If you're using " -"a single tenant app, please also copy *Directory (tenant) ID*. You now have " -"all required information for Zammad." -msgstr "" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``https://zammad.org`` or empty if not set" +msgstr "``https://zammad.org`` veya ayarlanmadıysa boş" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to retreive application client and tenant IDs" -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Department" +msgstr "Geçerli Kullanıcı > Bölüm" -#: ../settings/security/third-party/microsoft.rst:98 -msgid "Step 2 - Add App Credentials to Zammad" -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.department}``" +msgstr "``#{user.department}``" -#: ../settings/security/third-party/microsoft.rst:100 -msgid "" -"Navigate to Security > Third-party Applications (Tab) within Zammad's admin " -"settings. Scroll down to the section *Authentication via Microsoft* and fill " -"in the required information." -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Email" +msgstr "Geçerli Kullanıcı > E-posta" -#: ../settings/security/third-party/microsoft.rst:105 -msgid "App ID:" -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.email}``" +msgstr "``#{user.email}``" -#: ../settings/security/third-party/microsoft.rst:105 -msgid "This is your *Application (client) ID*." -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Fax" +msgstr "Geçerli Kullanıcı > Faks" -#: ../settings/security/third-party/microsoft.rst:108 -msgid "App secret:" -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.fax}``" +msgstr "``#{user.fax}``" -#: ../settings/security/third-party/microsoft.rst:108 -msgid "This is your *client secret* (value)." -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Firstname" +msgstr "Geçerli Kullanıcı > Ad" -#: ../settings/security/third-party/microsoft.rst:113 -msgid "App Tenant ID:" -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.firstname}``" +msgstr "``#{user.firstname}``" -#: ../settings/security/third-party/microsoft.rst:111 -msgid "" -"**optional** only required for apps that use account type *Accounts in this " -"organizational directory only (Default Directory only - Single tenant).*" -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Lastname" +msgstr "Geçerli Kullanıcı > Soyad" -#: ../settings/security/third-party/microsoft.rst:115 -msgid "" -"Apply your settings by pressing submit and activate *Authentication via " -"Microsoft*." -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.lastname}``" +msgstr "``#{user.lastname}``" -#: ../settings/security/third-party/microsoft.rst:None -msgid "" -"Screencast showing how to add app credentials and activating the\n" -"authentication method" -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Login" +msgstr "Geçerli Kullanıcı > Giriş" -#: ../settings/security/third-party/saml.rst:2 -msgid "SAML" -msgstr "SAML" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.login}``" +msgstr "``#{user.login}``" -#: ../settings/security/third-party/saml.rst:4 -msgid "" -"Connect your SAML (Security Assertion Markup Language) identity provider as " -"a single sign-on (SSO) method." -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Mobile" +msgstr "Geçerli Kullanıcı > Mobil" -#: ../settings/security/third-party/saml.rst:7 -msgid "" -"SAML is an open standard for SSO authentication (among other things). Sign-" -"ins are shared across multiple **service providers** and managed by a " -"central **identity provider** (IdP)." -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.mobile}``" +msgstr "``#{user.mobile}``" -#: ../settings/security/third-party/saml.rst:11 -msgid "" -"In this case, the service provider is Zammad, and the IdP is a software " -"service that you either host or subscribe to (*e.g.,* `Keycloak `_, `Redhat SSO Server `_, `ADFS `_, or `Okta `_)." -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Note" +msgstr "Geçerli Kullanıcı > Not" -#: ../settings/security/third-party/saml.rst:18 -msgid "" -"This guide assumes you are already using SAML within your organization (i." -"e., that your IdP is fully set up)." -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.note}``" +msgstr "``#{user.note}``" -#: ../settings/security/third-party/saml.rst:21 -msgid "" -"Please note: Our instructions are based on connecting Zammad with Keycloak." -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Domain based assignment" +msgstr "Geçerli Kullanıcı > Organizasyon > Alan adına göre atama" -#: ../settings/security/third-party/saml.rst:25 -msgid "Step 1: Configure Your IdP" -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.domain_assignment}``" +msgstr "``#{user.organization.domain_assignment}``" -#: ../settings/security/third-party/saml.rst:28 -msgid "Add Zammad as a Client/App" -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Domain" +msgstr "Geçerli Kullanıcı > Organizasyon > Alan adı" -#: ../settings/security/third-party/saml.rst:30 -msgid "" -"Import Zammad into your IdP using the XML configuration found at ``https://" -"your.zammad.domain/auth/saml/metadata``." -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.domain}``" +msgstr "``#{user.organization.domain}``" -#: ../settings/security/third-party/saml.rst:33 -msgid "" -"If your IdP doesn't support XML import, you will have to configure Zammad as " -"a new client/app manually using the above XML metadata file for reference." -msgstr "" +#: ../misc/variables/current-user.rst:1 +#, fuzzy +msgid "``zammad.com`` or empty if not set" +msgstr "``https://zammad.com``` veya ayarlanmadıysa boş" -#: ../settings/security/third-party/saml.rst:36 -msgid "For instance, when you see this tag:" -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Name" +msgstr "Geçerli Kullanıcı > Organizasyon > Ad" -#: ../settings/security/third-party/saml.rst:42 -msgid "" -"Set the **Assertion Consumer Service Binding URL** (sometimes also listed as " -"**Valid Redirect URIs**) to ``http://your.zammad.domain/auth/saml/callback``." -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.name}``" +msgstr "``#{user.organization.name}``" -#: ../settings/security/third-party/saml.rst:47 -msgid "Set Up User Attribute Mapping" -msgstr "" +#: ../misc/variables/current-user.rst:1 +#, fuzzy +msgid "``Zammad GmbH``" +msgstr "``Zammad``" -#: ../settings/security/third-party/saml.rst:49 -msgid "" -"Zammad requests the following user attributes (or “properties”) from the IdP:" -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Note" +msgstr "Geçerli Kullanıcı > Organizasyon > Not" -#: ../settings/security/third-party/saml.rst:51 -msgid "Email address (``email``)" -msgstr "E-posta adresi (``email``)" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.note}``" +msgstr "``#{user.organization.note}``" -#: ../settings/security/third-party/saml.rst:52 -msgid "Full name (``name``)" -msgstr "Tam isim (``name``)" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``A note to the organization of the user`` or empty if not set" +msgstr "`Kullanıcının organizasyonu için bir not`` veya ayarlanmadıysa boş" -#: ../settings/security/third-party/saml.rst:53 -msgid "Given name (``first_name``)" -msgstr "Verilen isim (``first_name``)" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Shared organization" +msgstr "Geçerli Kullanıcı > Organizasyon > Paylaşılan organizasyon" -#: ../settings/security/third-party/saml.rst:54 -msgid "Family name (``last_name``)" -msgstr "Aile ismi (``last_name``)" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.shared}``" +msgstr "``#{user.organization.shared}``" -#: ../settings/security/third-party/saml.rst:56 -msgid "" -"You may need to set up “mappers” (or “mappings”) to tell your IdP how user " -"attributes in SAML correspond to those in Zammad. For a more detailed " -"breakdown, refer to the XML metadata file referenced in the previous section." -msgstr "" +#: ../misc/variables/current-user.rst:1 +#, fuzzy +msgid "Current User > Organization > VIP" +msgstr "Geçerli Kullanıcı > Organizasyon > Not" -#: ../settings/security/third-party/saml.rst:62 -msgid "Per-IdP Instructions" -msgstr "" +#: ../misc/variables/current-user.rst:1 +#, fuzzy +msgid "``#{user.organization.vip}``" +msgstr "``#{user.organization.domain}``" -#: ../settings/security/third-party/saml.rst:102 -msgid "Keycloak" -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Phone" +msgstr "Geçerli Kullanıcı > Telefon" -#: ../settings/security/third-party/saml.rst:65 -msgid "" -"**To add Zammad as a client,** save the XML configuration to disk (``https://" -"your.zammad.domain/auth/saml/metadata``) and use **Clients > Clients list > " -"Import client** in the Keycloak admin panel." -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.phone}``" +msgstr "``#{user.phone}``" -#: ../settings/security/third-party/saml.rst:70 -msgid "" -"To help Zammad **match its own user accounts to Keycloak users**, create a " -"user attribute (or “property”) mapper. In **Clients list**, click on your " -"newly created Client ID, choose the tab **Client scopes** and click on the " -"link which refers to your Zammad instance. Choose **Add mapper > By " -"configuration > User Property** and create a mapper with the following " -"entries:" -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated at" +msgstr "Geçerli Kullanıcı > Güncelleme tarihi" -#: ../settings/security/third-party/saml.rst:78 -msgid "**Name**" -msgstr "**Adı**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_at}``" +msgstr "``#{user.updated_at}``" -#: ../settings/security/third-party/saml.rst:80 -msgid "**Mapper Type**" -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Address" +msgstr "Geçerli Kullanıcı > Güncelleyen > Adres" -#: ../settings/security/third-party/saml.rst:81 -#, fuzzy -msgid "``User Property``" -msgstr "``User-Agent``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.address}``" +msgstr "``#{user.updated_by.address}``" -#: ../settings/security/third-party/saml.rst:82 -msgid "**Property**" -msgstr "" +#: ../misc/variables/current-user.rst:1 +#, fuzzy +msgid "Current User > Updated by > Avatar" +msgstr "Geçerli Kullanıcı > Güncelleyen > Faks" -#: ../settings/security/third-party/saml.rst:83 +#: ../misc/variables/current-user.rst:1 #, fuzzy -msgid "``emailAddress``" -msgstr "epostaAdresi" +msgid "``#{user.updated_by.avatar(60,60)}``" +msgstr "``#{user.updated_by.lastname}``" -#: ../settings/security/third-party/saml.rst:84 -msgid "**SAML Attribute Name**" -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Department" +msgstr "Geçerli Kullanıcı > Güncelleyen > Bölüm" -#: ../settings/security/third-party/saml.rst:86 -msgid "**SAML Attribute NameFormat**" -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.department}``" +msgstr "``#{user.updated_by.department}``" -#: ../settings/security/third-party/saml.rst:87 -msgid "``basic``" -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Email" +msgstr "Geçerli Kullanıcı > Güncelleyen > E-posta" -#: ../settings/security/third-party/saml.rst:89 -msgid "" -"In the example above, we're telling Zammad that whenever it receives a SAML " -"login request, it should take the ``email`` property from Keycloak, look for " -"a Zammad user with the same ``email`` attribute, and create a new session " -"for that user." -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.email}``" +msgstr "``#{user.updated_by.email}``" -#: ../settings/security/third-party/saml.rst:95 -msgid "" -"If your Keycloak users' email addresses are stored on another property (*e." -"g.,* ``username``), adjust accordingly." -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Fax" +msgstr "Geçerli Kullanıcı > Güncelleyen > Faks" -#: ../settings/security/third-party/saml.rst:98 -msgid "" -"Back in **Settings**, enter the Client ID (``https://your.zammad.domain/auth/" -"saml/metadata``) in the field **Master SAML Processing URL**." -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.fax}``" +msgstr "``#{user.updated_by.fax}``" -#: ../settings/security/third-party/saml.rst:101 -msgid "You also need to enable **Sign assertions**." -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Firstname" +msgstr "Geçerli Kullanıcı > Güncelleyen > Ad" -#: ../settings/security/third-party/saml.rst:105 -msgid "Step 2: Configure Zammad" -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.firstname}``" +msgstr "``#{user.updated_by.firstname}``" -#: ../settings/security/third-party/saml.rst:107 -msgid "" -"Enable SAML and enter your IdP's details in the Admin Panel under **Settings " -"> Security > Third Party Applications > Authentication via SAML**:" -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Lastname" +msgstr "Geçerli Kullanıcı > Güncelleyen > Soyad" -#: ../settings/security/third-party/saml.rst:None -#, fuzzy -msgid "Example configuration of SAML part 1" -msgstr "Makale > Görünürlük" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.lastname}``" +msgstr "``#{user.updated_by.lastname}``" -#: ../settings/security/third-party/saml.rst:119 -#, fuzzy -msgid "Display name" -msgstr "Görünen Ad" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Login" +msgstr "Geçerli Kullanıcı > Güncelleyen > Giriş" -#: ../settings/security/third-party/saml.rst:116 -msgid "" -"Allows you to define a custom button name for SAML. This helps your users to " -"understand better what the button on the login page does." -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.login}``" +msgstr "``#{user.updated_by.login}``" -#: ../settings/security/third-party/saml.rst:119 -msgid "Defaults to ``SAML``." -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Mobile" +msgstr "Geçerli Kullanıcı > Güncelleyen > Mobil" -#: ../settings/security/third-party/saml.rst:123 -msgid "IDP SSO target URL" -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.mobile}``" +msgstr "``#{user.updated_by.mobile}``" -#: ../settings/security/third-party/saml.rst:122 -msgid "" -"This is the target URL Zammad shall redirect to when the user presses the " -"SAML button. For Keycloak, this needs to look like https://your.domain/" -"realms/your-realm/protocol/saml" -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Note" +msgstr "Geçerli Kullanıcı > Güncelleyen > Not" -#: ../settings/security/third-party/saml.rst:127 -msgid "IDP single logout target URL" -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.note}``" +msgstr "``#{user.updated_by.note}``" -#: ../settings/security/third-party/saml.rst:126 -msgid "" -"This is the URL to which the single logout request and response should be " -"sent." -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Phone" +msgstr "Geçerli Kullanıcı > Güncelleyen > Telefon" -#: ../settings/security/third-party/saml.rst:131 -#, fuzzy -msgid "IDP certificate" -msgstr "Sertifika Ekle" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.phone}``" +msgstr "``#{user.updated_by.phone}``" -#: ../settings/security/third-party/saml.rst:130 -msgid "" -"The public certificate of your IDP for Zammad to verify during the callback " -"phase." -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > VIP" +msgstr "Geçerli Kullanıcı > Güncelleyen > VIP" -#: ../settings/security/third-party/saml.rst:145 -#, fuzzy -msgid "IDP certificate fingerprint" -msgstr "Sertifika Ekle" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.vip}``" +msgstr "``#{user.updated_by.vip}``" -#: ../settings/security/third-party/saml.rst:134 -msgid "" -"The fingerprint of your IDPs public certificate to verify during callback " -"phase." -msgstr "" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``false`` or ``true``" +msgstr "``yanlış`` veya ``doğru``" -#: ../settings/security/third-party/saml.rst:137 -msgid "🔏 **For the IdP certificate / certificate fingerprint:**" -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Web" +msgstr "Geçerli Kullanıcı > Güncelleyen > Web" -#: ../settings/security/third-party/saml.rst:139 -msgid "" -"Provide **only one or the other**—do not provide both! (Between the two, we " -"recommend the signing certificate itself: fingerprints use SHA-1, which `has " -"been broken for a while now `_.)" -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.web}``" +msgstr "``#{user.updated_by.web}``" -#: ../settings/security/third-party/saml.rst:144 -msgid "" -"**Keycloak users:** Find your certificate in the Keycloak admin panel under " -"**Realm Settings > Keys > Algorithm: RS256 > Certificate**." -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > VIP" +msgstr "Geçerli Kullanıcı > VIP" -#: ../settings/security/third-party/saml.rst:151 -msgid "Name identifier format" -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.vip}``" +msgstr "``#{user.vip}``" -#: ../settings/security/third-party/saml.rst:148 -msgid "" -"This is the unique identifiers field type. Usually it should be ``urn:oasis:" -"names:tc:SAML:1.1:nameid-format:emailAddress``." -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Web" +msgstr "Geçerli Kullanıcı > Web" -#: ../settings/security/third-party/saml.rst:151 -msgid "Zammad **expects an email address as unique identifier**!" -msgstr "" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.web}``" +msgstr "``#{user.web}``" -#: ../settings/security/third-party/saml.rst:155 +#: ../misc/variables/ticket.rst:6 #, fuzzy -msgid "UID attribute name" -msgstr "Bilet Nitelikleri" - -#: ../settings/security/third-party/saml.rst:154 +#| msgid "" +#| "Below you can find all available ticket-based variables within Zammad. " +#| "These can be called via Triggers for example. If you're unsure if Zammad " +#| "does support variables at the point you're at, you can try to type ``::`` " +#| "to check." msgid "" -"Here you can define an attribute that uniquely identifies the user. If " -"unset, the name identifier returned by the IDP is used." +"Below you can find all available ticket-based variables within Zammad. These " +"can be called via triggers for example. If you're unsure if Zammad does " +"support variables at the point you're at, you can try to type ``::`` to " +"check." msgstr "" +"Aşağıda, Zammad içindeki tüm bilet tabanlı değişkenleri bulabilirsiniz. " +"Bunlar örneğin Tetikleyiciler aracılığıyla çağrılabilir. Bulunduğunuz " +"noktada Zammad'ın değişkenleri destekleyip desteklemediğinden emin " +"değilseniz, kontrol etmek için ``::`` yazmayı deneyebilirsiniz." -#: ../settings/security/third-party/saml.rst:None -#, fuzzy -msgid "Example configuration of SAML part 2" -msgstr "Makale > Görünürlük" +#: ../misc/variables/ticket.rst:12 +msgid "Ticket Variables" +msgstr "Bilet Değişkenleri" -#: ../settings/security/third-party/saml.rst:163 -msgid "" -"Decide if the certificate for the connection to the IdP service has to be " -"verified or not (default: ``yes``)." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Accounted Time" +msgstr "Bilet > Hesaplanan Zaman" -#: ../settings/security/third-party/saml.rst:169 -#, fuzzy -msgid "Signing & Encrypting" -msgstr "Şifreleme" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.time_unit}``" +msgstr "``#{ticket.time_unit}``" -#: ../settings/security/third-party/saml.rst:169 -msgid "" -"Define if you want to sign, encrypt, do both or nothing for the requests." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``1``, ``2.75`` or empty response" +msgstr "``1``, ``2.75`` veya boş yanıt" -#: ../settings/security/third-party/saml.rst:179 -#, fuzzy -msgid "Certificate (PEM)" -msgstr "Sertifika Ekle" +#: ../misc/variables/ticket.rst:1 +msgid "``3``, any number of articles existing in the ticket right now" +msgstr "``3``, şu anda bilette bulunan herhangi bir sayıda makale" -#: ../settings/security/third-party/saml.rst:172 -msgid "" -"Paste the public certificate of your Zammad SAML client, if you want to " -"encrypt the requests." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Closing time" +msgstr "Bilet > Kapanma zamanı" -#: ../settings/security/third-party/saml.rst:175 -#, fuzzy -msgid "Make sure the certificate is:" -msgstr "Alıcının sertifikasının geçerli olduğundan emin misiniz?" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.close_at}``" +msgstr "``#{ticket.close_at}``" -#: ../settings/security/third-party/saml.rst:177 -msgid "already valid and not yet expired" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "2019-10-07 17:25:00 UTC" +msgstr "2019-10-07 17:25:00 UTC" -#: ../settings/security/third-party/saml.rst:178 -#, fuzzy -msgid "no CA certificate" -msgstr "Sertifika Ekle" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created at" +msgstr "Bilet > Oluşturulma" -#: ../settings/security/third-party/saml.rst:179 +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_at}``" +msgstr "``#{ticket.created_at}``" + +#: ../misc/variables/ticket.rst:1 +msgid "2019-10-07 16:25:00 UTC" +msgstr "2019-10-07 16:25:00 UTC" + +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Address" +msgstr "Bilet > Oluşturan > Adres" + +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.address}``" +msgstr "``#{ticket.created_by.address}``" + +#: ../misc/variables/ticket.rst:1 #, fuzzy -msgid "valid for signing and encrypting" -msgstr "Şifreleme" +msgid "Ticket > Created by > Avatar" +msgstr "Bilet > Oluşturan > Faks" -#: ../settings/security/third-party/saml.rst:185 +#: ../misc/variables/ticket.rst:1 #, fuzzy -msgid "Private key (PEM)" -msgstr "Özel Anahtar Ekle" +msgid "``#{ticket.created_by.avatar(60,60)}``" +msgstr "``#{ticket.created_by.lastname}``" -#: ../settings/security/third-party/saml.rst:182 -msgid "" -"Paste the private key of your Zammad SAML client here, if you want to sign " -"the requests." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Department" +msgstr "Bilet > Oluşturan > Bölüm" -#: ../settings/security/third-party/saml.rst:185 -msgid "Make sure the key is an RSA key with a length of at least 2048 bits." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.department}``" +msgstr "``#{ticket.created_by.department}``" -#: ../settings/security/third-party/saml.rst:188 -#, fuzzy -msgid "Private key secret" -msgstr "Kişisel hesaplar" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Email" +msgstr "Bilet > Oluşturan > E-posta" -#: ../settings/security/third-party/saml.rst:188 -msgid "If your private key is secured with a secret, you can provide it here." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.email}``" +msgstr "``#{ticket.created_by.email}``" -#: ../settings/security/third-party/saml.rst:192 -msgid "Your callback URL" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Fax" +msgstr "Bilet > Oluşturan > Faks" -#: ../settings/security/third-party/saml.rst:191 -msgid "" -"This URL is needed for your IdP configuration so it knows where to redirect " -"to after successful authentication." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.fax}``" +msgstr "``#{ticket.created_by.fax}``" -#: ../settings/security/third-party/saml.rst:194 -msgid "" -"After saving your input by clicking on the \"Submit\" button, Zammad " -"verifies the provided keys/certificates (e.g. if they are valid for signing/" -"encrypting and if they aren't expired)." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Firstname" +msgstr "Bilet > Oluşturan > Ad" -#: ../settings/security/third-party/saml.rst:199 -msgid "" -"See :ref:`automatic account linking ` for details " -"on how to link existing Zammad accounts to IdP accounts." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.firstname}``" +msgstr "``#{ticket.created_by.firstname}``" -#: ../settings/security/third-party/saml.rst:205 -#, fuzzy -msgid "Automatic account linking doesn't work" -msgstr "Otomatik hesap bağlantısı çalışmıyor" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Lastname" +msgstr "Bilet > Oluşturan > Soyadı" -#: ../settings/security/third-party/saml.rst:206 -msgid "" -"Have you double-checked your IdP's user attribute mapping configuration?" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.lastname}``" +msgstr "``#{ticket.created_by.lastname}``" -#: ../settings/security/third-party/twitter.rst:4 -#, fuzzy -msgid "" -"It is possible to create a quick login for your helpdesk via Twitter. To do " -"so, you need to follow these steps:" -msgstr "" -"Facebook üzerinden yardım masanız için hızlı bir giriş oluşturmak mümkündür. " -"Bunu yapmak için şu adımları izlemeniz gerekir:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Login" +msgstr "Bilet > Oluşturan > Giriş" -#: ../settings/security/third-party/twitter.rst:8 -#, fuzzy -msgid "Register Twitter App" -msgstr "Twitter uygulamasına kaydol" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.login}``" +msgstr "``#{ticket.created_by.login}``" -#: ../settings/security/third-party/twitter.rst:10 -msgid "Go to https://dev.twitter.com/apps and login with your account." -msgstr "https://dev.twitter.com/apps adresine git ve hesabınla giriş yap." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Mobile" +msgstr "Bilet > Oluşturan > Mobil" -#: ../settings/security/third-party/twitter.rst:15 -msgid "Click on \"Create App\"" -msgstr "\"Uygulama Oluştur\"a tıkla" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.mobile}``" +msgstr "``#{ticket.created_by.mobile}``" -#: ../settings/security/third-party/twitter.rst:None -msgid "new app page" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Note" +msgstr "Bilet > Oluşturan > Not" -#: ../settings/security/third-party/twitter.rst:20 -msgid "" -"Enter app settings. As \"Callback URL\" you need to enter ``https://" -"zammad_host/api/v1/external_credentials/twitter/callback``. You need to " -"replace ``zammad_host`` with the domain of your Zammad system." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.note}``" +msgstr "``#{ticket.created_by.note}``" -#: ../settings/security/third-party/twitter.rst:24 -msgid "" -"After the app has been created, update the application icon and organization " -"attributes." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Phone" +msgstr "Bilet > Oluşturan > Telefon" -#: ../settings/security/third-party/twitter.rst:None -msgid "set permissions to receive and send direct messages" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.phone}``" +msgstr "``#{ticket.created_by.phone}``" -#: ../settings/security/third-party/twitter.rst:30 -#, fuzzy -msgid "" -"Next we need to set ``read, write and access direct messages`` permissions " -"for the app." -msgstr "*Okuma, yazma ve direkt mesajlara erişme*yi seç" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > VIP" +msgstr "Bilet > Oluşturan > VIP" -#: ../settings/security/third-party/twitter.rst:None -msgid "click on Keys & Access Token, note them" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.vip}``" +msgstr "``#{ticket.created_by.vip}``" -#: ../settings/security/third-party/twitter.rst:36 -msgid "" -"Go to \"Keys and Access Token\" tab and note the \"Consumer Key\" and " -"\"Consumer Secret\"." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Web" +msgstr "Bilet > Oluşturan > Web" -#: ../settings/security/third-party/twitter.rst:40 -#, fuzzy -msgid "Configure Zammad as Twitter App" -msgstr "Zammad'ı Twitter uygulaması olarak yapılandır" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.web}``" +msgstr "``#{ticket.created_by.web}``" -#: ../settings/security/third-party/twitter.rst:42 -msgid "" -"Go to \"Admin > Security > Twitter > Third Party Applications > Twitter\" " -"Section." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Address" +msgstr "Bilet > Müşteri > Adres" -#: ../settings/security/third-party/twitter.rst:None -#, fuzzy -msgid "Admin > Security > Third Party Applications" -msgstr "Üçüncü Parti Uygulamalar" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.address}``" +msgstr "``#{ticket.customer.address}``" -#: ../settings/security/third-party/twitter.rst:48 -msgid "" -"Fill in the \"Twitter Key\" and the \"Twitter Secret\" and click the " -"\"Submit\" button." -msgstr "" +#: ../misc/variables/ticket.rst:1 +#, fuzzy +msgid "Ticket > Customer > Avatar" +msgstr "Bilet > Müşteri > Faks" -#: ../settings/security/third-party/twitter.rst:51 +#: ../misc/variables/ticket.rst:1 #, fuzzy -msgid "" -"Now you can link accounts via \"Avatar > Profile > Link Accounts\" or login " -"via Zammad login page." -msgstr "" -"Artık \"Avatar -> Profil -> Hesapları Bağla\" yoluyla hesapları bağlayabilir " -"veya Zammad giriş sayfası üzerinden giriş yapabilirsiniz." +msgid "``#{ticket.customer.avatar(60,60)}``" +msgstr "``#{ticket.customer.lastname}``" -#: ../settings/security/two-factor.rst:11 -msgid "Two-factor Authentication Methods" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Department" +msgstr "Bilet > Müşteri > Bölüm" -#: ../settings/security/two-factor.rst:2 -msgid "Two-Factor Authentication" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.department}``" +msgstr "``#{ticket.customer.department}``" -#: ../settings/security/two-factor.rst:4 -msgid "" -"Two-factor authentication (2FA) enhances the security of Zammad accounts by " -"adding an extra layer of verification beyond a password. It requires users " -"to provide two different types of authentication factors, typically " -"something they know (like a password) and something they possess (like a " -"mobile device or a security token), to ensure that only authorized " -"individuals can access the account." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Email" +msgstr "Bilet > Müşteri > E-posta" -#: ../settings/security/two-factor.rst:19 -msgid "Enable Recovery Codes" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.email}``" +msgstr "``#{ticket.customer.email}``" -#: ../settings/security/two-factor.rst:21 -msgid "" -"Recovery codes are one-time use security codes that can be used by the user " -"if they lose access to their other two-factor authentication methods. They " -"cannot be used on their own, they can only be activated if at least one two-" -"factor authentication method is enabled." -msgstr "" - -#: ../settings/security/two-factor.rst:None -#, fuzzy -msgid "Enable Recovery Codes Setting" -msgstr "Posta Sunucusu Ayarları" - -#: ../settings/security/two-factor.rst:30 -msgid "" -"Recovery codes can only be used as a backup method. If enabled, they will be " -"automatically generated for the user once they set up their initial two-" -"factor authentication method." -msgstr "" - -#: ../settings/security/two-factor.rst:34 -msgid "" -"The user will be asked to print out or save the generated recovery codes in " -"a safe place. Once used, a recovery code cannot be reused." -msgstr "" - -#: ../settings/security/two-factor.rst:37 -msgid "" -"Users will also have an option to regenerate their recovery codes at any " -"time, which invalidates already existing recovery codes and provides them " -"with a list of fresh codes." -msgstr "" - -#: ../settings/security/two-factor.rst:41 -msgid "" -"After you enable this setting, when the user completes a setup of their " -"initial two-factor authentication method, they will be presented with a list " -"of recovery codes and instructed to save them for later use." -msgstr "" - -#: ../settings/security/two-factor.rst:None -msgid "Recovery Codes Generation Modal Dialog" -msgstr "" - -#: ../settings/security/two-factor.rst:50 -msgid "Enforce the Set Up of the Two-Factor Authentication" -msgstr "" - -#: ../settings/security/two-factor.rst:52 -msgid "" -"In case you wish to require your users to set up at least one two-factor " -"authentication method for their account, you can do this by selecting " -"specific user roles the requirement applies to in **Enforced for user " -"roles** setting. Of course you must have at least one two-factor " -"authentication method enabled for this setting to take effect." -msgstr "" - -#: ../settings/security/two-factor.rst:None -msgid "Enforced for User Roles Setting" -msgstr "" - -#: ../settings/security/two-factor.rst:62 -msgid "" -"After you change this setting, if the user has one of the selected roles on " -"their account, they will be forced to set up the two-factor authentication " -"upon next sign in or application reload." -msgstr "" - -#: ../settings/security/two-factor.rst:66 -msgid "" -"A modal dialog with instructions will be shown, and they will not be able to " -"do any work before they set up at least one two-factor method." -msgstr "" - -#: ../settings/security/two-factor.rst:None -msgid "Modal Dialog for Enforcing Two-Factor Authentication Set Up" -msgstr "" - -#: ../settings/security/two-factor.rst:74 -msgid "Reset Two-Factor Authentication for a Specific User" -msgstr "" - -#: ../settings/security/two-factor.rst:76 -msgid "" -"In case an user isn't able to login anymore because of an inaccessible " -"second factor, you can reset the user's 2FA method." -msgstr "" - -#: ../settings/security/two-factor.rst:79 -msgid "" -"To do this, go to the user management and search for the relevant user. " -"After you found the account, click the button in the action column and " -"select \"Manage Two-Factor Authentication\":" -msgstr "" - -#: ../settings/security/two-factor.rst:None -msgid "Context menu in action column in user management" -msgstr "" - -#: ../settings/security/two-factor.rst:87 -msgid "" -"After selecting this, you can see a dialog where you can either reset one " -"2FA method or reset all of the user's 2FA methods:" -msgstr "" - -#: ../settings/security/two-factor.rst:None -msgid "Dialog for resetting user's 2FA method" -msgstr "" - -#: ../settings/security/two-factor.rst:94 -msgid "" -"Choose the fitting one, click on the corresponding \"Remove ...\" button and " -"confirm your action. The user now has to setup a new 2FA method, depending " -"on your 2FA configuration." -msgstr "" - -#: ../settings/security/two-factor/authenticator-app.rst:2 -msgid "Authenticator App" -msgstr "" - -#: ../settings/security/two-factor/authenticator-app.rst:4 -msgid "" -"The authenticator app method is a type of two-factor authentication that " -"uses a mobile application to generate one-time codes for account " -"verification. After setting up the authenticator app on their device, the " -"user links it to their Zammad account." -msgstr "" - -#: ../settings/security/two-factor/authenticator-app.rst:12 -msgid "" -"When logging in, the user is prompted to enter a time-sensitive code " -"generated by the app, in addition to their password. This code acts as the " -"second factor of authentication, providing an extra layer of security as it " -"changes periodically and is unique to the user's device." -msgstr "" - -#: ../settings/security/two-factor/authenticator-app.rst:None -msgid "Security Code in Google Authenticator App" -msgstr "" - -#: ../settings/security/two-factor/authenticator-app.rst:22 -msgid "" -"The app generates codes based on a shared secret key stored securely on both " -"the user's device and the server, ensuring a synchronized and secure " -"authentication process. The method of generating the codes is sometimes also " -"called TOTP (time-based one-time password)." -msgstr "" - -#: ../settings/security/two-factor/authenticator-app.rst:28 -msgid "Enabling the Authenticator App Method" -msgstr "" - -#: ../settings/security/two-factor/authenticator-app.rst:30 -#: ../settings/security/two-factor/security-keys.rst:28 -msgid "To enable the method, just toggle the switch on in the settings." -msgstr "" - -#: ../settings/security/two-factor/authenticator-app.rst:None -msgid "Authenticator App Switch in Settings" -msgstr "" - -#: ../settings/security/two-factor/authenticator-app.rst:36 -msgid "" -"Now the users will be able to set up this two-factor authentication method " -"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " -"Once they do, on next sign-in with password, they will be asked to provide " -"an additional security code generated by their mobile device." -msgstr "" - -#: ../settings/security/two-factor/security-keys.rst:2 -#, fuzzy -msgid "Security Keys" -msgstr "Güvenlik" - -#: ../settings/security/two-factor/security-keys.rst:4 -msgid "" -"The security keys method is a type of a two-factor authentication that uses " -"Web Authentication API in the browser for verifying user's identity. The " -"user can register multiple hardware or software security keys with their " -"Zammad account and then they can use it during the sign-in process." -msgstr "" - -#: ../settings/security/two-factor/security-keys.rst:12 -msgid "" -"When logging in, the user is prompted to provide the same security key they " -"registered with their account, in addition to their password. This key acts " -"as the second factor of authentication, providing an extra layer of security." -msgstr "" - -#: ../settings/security/two-factor/security-keys.rst:None -msgid "Security Key dialog in Safari on macOS" -msgstr "" - -#: ../settings/security/two-factor/security-keys.rst:21 -msgid "" -"The type of the key can range from hardware USB sticks to passkeys stored in " -"a device of user's choice. Which type can be used depends on the browser " -"flavor and the platform of the user." -msgstr "" - -#: ../settings/security/two-factor/security-keys.rst:26 -msgid "Enabling the Security Keys Method" -msgstr "" - -#: ../settings/security/two-factor/security-keys.rst:None -msgid "Security Keys Switch in Settings" -msgstr "" - -#: ../settings/security/two-factor/security-keys.rst:34 -msgid "" -"Now the users will be able to set up this two-factor authentication method " -"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " -"Once they do, on next sign-in with password, they will be asked to provide " -"the same security key they registered during the setup." -msgstr "" - -#: ../settings/system/system-selfhosted.include.rst:3 -msgid "" -"Below settings are only available to self hosted users. In hosted " -"environments we're handling these settings for you to ensure service " -"stability." -msgstr "" -"Aşağıdaki ayarlar yalnızca kendi kendine barındırılan kullanıcılar " -"tarafından kullanılabilir. Barındırılan ortamlarda, hizmet istikrarını " -"sağlamak için bu ayarları sizin için hallediyoruz." - -#: ../settings/system/base.rst:11 -msgid "Fully Qualified Domain Name" -msgstr "" - -#: ../settings/system/base.rst:7 -msgid "The URL of your Zammad installation." -msgstr "" - -#: ../settings/system/base.rst:9 ../settings/system/base.rst:17 -msgid "This setting is used within :doc:`/system/variables` and notifications." -msgstr "" - -#: ../settings/system/system-base.include.rst:1 -#, fuzzy -msgid "It is automatically set by the *Getting Started wizard*." -msgstr "Bu ayar otomatik olarak Başlarken sihirbazı tarafından ayarlandı." - -#: ../settings/system/system-base.include.rst:5 -msgid "Changing this setting also changes callback URLs for your channels etc." -msgstr "" -"Bu ayarın değiştirilmesi, kanallarınız vb. için geri arama URL'lerini de " -"değiştirir." - -#: ../settings/system/system-base.include.rst:6 -msgid "This setting can have negative affects on being able to login." -msgstr "Bu ayarın giriş yapabilme üzerinde olumsuz etkileri olabilir." - -#: ../settings/system/base.rst:19 -msgid "HTTP type" -msgstr "HTTP türü" - -#: ../settings/system/base.rst:14 -msgid "" -"The HTTP type tells your installation how your clients connect. This is " -"relevant for authentication and cookie security." -msgstr "" - -#: ../settings/system/base.rst:31 -msgid "SystemID" -msgstr "SystemID" - -#: ../settings/system/base.rst:22 -msgid "" -"This ID is being used within your ticket number. In case you're " -"communicating with another ticket system with similar ticket number schemes " -"this ID greatly reduces the risk of false follow ups." -msgstr "" - -#: ../settings/system/base.rst:26 -msgid "" -"The SystemID is randomly selected upon installation of Zammad (``1-99``)." -msgstr "" - -#: ../settings/system/base.rst:30 -msgid "" -"**Do not** change this setting in a productive system! Your Zammad " -"installation may no longer recognize old ticket number based follow ups upon " -"change!" -msgstr "" - -#: ../settings/system/frontend.rst:2 -msgid "Frontend" -msgstr "Ön yüz" - -#: ../settings/system/frontend.rst:22 -msgid "Core Workflow Ajax Mode" -msgstr "" - -#: ../settings/system/frontend.rst:6 -msgid "" -"This setting allows administrators to enforce :doc:`/system/core-workflows` " -"to use Ajax-Calls instead of web sockets. You'll usually only need this if " -"you experience serious issues as noted below." -msgstr "" - -#: ../settings/system/frontend.rst:10 -msgid "**🤓 Possible (technical) reasons**" -msgstr "" - -#: ../settings/system/frontend.rst:12 -msgid "" -"In some cases, your network structure (e.g. firewalls, proxies) may " -"disconnect long web socket connections. This leads to select fields staying " -"empty (e.g. owner selection *after* selecting your group) or fields not " -"shown / hidden (e.g. when switching to or from pending states, the \"pending " -"till\" field not showing / hiding)." -msgstr "" - -#: ../settings/system/frontend.rst:18 -msgid "" -"Please keep in mind that the Ajax fallback may cause serious pressure on " -"your application server. If you have the choice stick to web sockets." -msgstr "" - -#: ../settings/system/frontend.rst:22 -msgid "Default: ``no`` (inactive)" -msgstr "" - -#: ../settings/system/frontend.rst:53 -msgid "Show calendar weeks in the picker of date/datetime fields" -msgstr "" - -#: ../settings/system/frontend.rst:25 -msgid "" -"With this setting you can instruct Zammad to provide week number display " -"globally for all users. Calendar with week number display are usually used " -"in business sectors and may not be relevant for everyone." -msgstr "" - -#: ../settings/system/frontend.rst:29 -msgid "" -"This setting affects *all areas* - you'll also see week numbers in the admin " -"panel for e.g. triggers and macros." -msgstr "" - -#: ../settings/system/frontend.rst:32 -msgid "Default: ``no`` (not shown)" -msgstr "" - -#: ../settings/system/frontend.rst:53 -msgid "Here's the difference:" -msgstr "" - -#: ../settings/system/frontend.rst:0 -msgid "Screenshot showing Zammad's date picker (in the default way)" -msgstr "" - -#: ../settings/system/frontend.rst:41 -msgid "Set to ``no``" -msgstr "" - -#: ../settings/system/frontend.rst:0 -msgid "" -"Screenshot showing Zammad's date picker with\n" -"week numbers enabled" -msgstr "" - -#: ../settings/system/frontend.rst:50 -#, fuzzy -msgid "Set to ``yes``" -msgstr "``hayır`` veya ``evet``" - -#: ../settings/system/index.rst:4 -msgid "" -"For your overview we split each tab within system settings into its own page:" -msgstr "" -"Genel bakışınız için sistem ayarlarındaki her sekmeyi kendi sayfasına " -"ayırdık:" - -#: ../settings/system/index.rst:16 -#, fuzzy -msgid "Console Based Settings" -msgstr "Konsol tabanlı ayarlar 🤓" - -#: ../settings/system/index.rst:18 -#, fuzzy -msgid "" -"There's some console based settings we didn't put into the UI. However, you " -"may find them helpful - you can find them in our :docs:`hidden settings ` section." -msgstr "" -"Kullanıcı arayüzüne koymadığımız bazı konsol tabanlı ayarlar var. Ancak, " -"bunları yararlı bulabilirsiniz - bunları `gizli ayarlar `_ bölümümüzde " -"bulabilirsiniz." - -#: ../settings/system/network.rst:2 -msgid "Network" -msgstr "Ağ" - -#: ../settings/system/network.rst:8 -msgid "" -"The proxy settings can only be saved after successfully testing the proxy " -"connection." -msgstr "" - -#: ../settings/system/network.rst:15 -#, fuzzy -msgid "Proxy Address." -msgstr "Proxy Adresi" - -#: ../settings/system/network.rst:12 -msgid "" -"Allows you to provide a proxy server if needed. This is relevant for network " -"communication by Zammad." -msgstr "" - -#: ../settings/system/network.rst:15 -msgid "It **does not** affect the update process or Elasticsearch." -msgstr "" - -#: ../settings/system/network.rst:18 -msgid "Username for proxy connection." -msgstr "" - -#: ../settings/system/network.rst:18 -msgid "" -"If your proxy server requires authentication, provide the username here." -msgstr "" - -#: ../settings/system/network.rst:21 -msgid "Password for proxy connection." -msgstr "" - -#: ../settings/system/network.rst:21 -msgid "" -"If your proxy server requires authentication, provide the password here." -msgstr "" - -#: ../settings/system/network.rst:26 -msgid "No proxy for the following hosts." -msgstr "" - -#: ../settings/system/network.rst:24 -msgid "" -"Exception list for hosts you can't or don't want to reach via proxy server." -msgstr "" - -#: ../settings/system/network.rst:27 -msgid "Default: ``localhost,127.0.0.0,::1``" -msgstr "Varsayılan: ``localhost,127.0.0.0,::1``" - -#: ../settings/system/services.rst:2 -msgid "Services" -msgstr "Servisler" - -#: ../settings/system/services.rst:10 -msgid "Image Service" -msgstr "" - -#: ../settings/system/services.rst:5 -msgid "Defines the backend for user and organization image lookups." -msgstr "" - -#: ../settings/system/services.rst:7 -msgid "Default: ``Zammad Image Service`` (active)" -msgstr "" - -#: ../settings/system/services.rst:9 -msgid "" -"Make sure your on premise installation has ``HTTPS`` access to ``images." -"zammad.com``." -msgstr "" - -#: ../settings/system/services.rst:18 -msgid "Geo Calendar Service" -msgstr "" - -#: ../settings/system/services.rst:13 -msgid "" -"Defines the backend for geo calendar lookups. Used for initial calendar " -"setup." -msgstr "" - -#: ../settings/system/services.rst:16 -msgid "Default: ``Zammad GeoCalendar Service`` (active)" -msgstr "" - -#: ../settings/system/services.include.rst:2 -msgid "" -"Make sure your on premise installation has ``HTTPS`` access to ``geo.zammad." -"com``." -msgstr "" - -#: ../settings/system/services.rst:26 -msgid "Geo IP Service" -msgstr "" - -#: ../settings/system/services.rst:21 -msgid "" -"Defines the backend for geo IP lookups. Shows also location of an IP address " -"if an IP address is shown." -msgstr "" - -#: ../settings/system/services.rst:24 -msgid "Default: ``Zammad GeoIP Service`` (active)" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Fax" +msgstr "Bilet > Müşteri > Faks" -#: ../settings/system/services.rst:32 -msgid "Geo Location Service" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.fax}``" +msgstr "``#{ticket.customer.fax}``" -#: ../settings/system/services.rst:29 -msgid "" -"Defines the backend for geo location lookups to store geo locations for " -"addresses." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Firstname" +msgstr "Bilet > Müşteri > Ad" -#: ../settings/system/services.rst:32 -msgid "" -"Default: ``OpenStreetMap (ODbL 1.0, http://osm.org/copyright)`` (active)" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.firstname}``" +msgstr "``#{ticket.customer.firstname}``" -#: ../settings/system/services.rst:36 -msgid "" -"You can find a detailed privacy information on what we store for how long on " -"our :docs:`Privacy Appendix ` inside of our System " -"Documentation." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Lastname" +msgstr "Bilet > Müşteri > Soyad" -#: ../settings/system/storage.rst:2 -msgid "Storage" -msgstr "Saklama" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.lastname}``" +msgstr "``#{ticket.customer.lastname}``" -#: ../settings/system/storage.rst:6 -msgid "" -"Here you can define where Zammad stores attachments for tickets and the " -"knowledge base. By default, we're writing to the ``Database`` - you can " -"switch to ``Filesystem`` or ``Simple Storage (S3)`` at any time. In this " -"case please have a look on the following instructions." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Login" +msgstr "Bilet > Müşteri > Giriş" -#: ../settings/system/storage.rst:11 -#, fuzzy -msgid "" -"If you have a busy Zammad instance, we strongly encourage you to use " -"filesystem storage instead of \"Database\". This will greatly improve system " -"performance (de-crease database load and size)." -msgstr "" -"Meşgul durumlarda dosya sistemi depolamasını kullanmanızı şiddetle tavsiye " -"ederiz. Bu, sistem performansını büyük ölçüde iyileştirir (veritabanı yükünü " -"ve boyutunu azaltır)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.login}``" +msgstr "``#{ticket.customer.login}``" -#: ../settings/system/storage.rst:19 -msgid "Database" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Mobile" +msgstr "Bilet > Müşteri > Mobil" -#: ../settings/system/storage.rst:17 -msgid "" -"This is the default storage method. The attachments are stored directly in " -"the database. If your Zammad instance grows, we recommend one of the other " -"methods to maintain performance." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.mobile}``" +msgstr "``#{ticket.customer.mobile}``" -#: ../settings/system/storage.rst:38 -#, fuzzy -msgid "Filesystem" -msgstr "Sistem" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Note" +msgstr "Bilet > Müşteri > Not" -#: ../settings/system/storage.rst:22 -#, fuzzy -msgid "" -"This storage method is recommended for all Zammad instances, especially for " -"those with a higher load. If you choose filesystem, your files are written " -"to ``/opt/zammad/storage/``." -msgstr "" -"Varsayılan olarak \"Veritabanı\"na yazıyoruz - istediğiniz zaman \"Dosya " -"Sistemi\"ne geçebilirsiniz. Dosya sistemini seçtiyseniz, dosyalarınız ``/opt/" -"zammad/fs/`` dizinine yazılır." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.note}``" +msgstr "``#{ticket.customer.note}``" -#: ../settings/system/storage.rst:26 -msgid "" -"Moving attachments from \"Database\" to \"Filesystem\" can be run during " -"production use. However, you should consider your framework conditions (e.g. " -"bandwidth, system load in production) to define the right moment." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Phone" +msgstr "Bilet > Müşteri > Telefon" -#: ../settings/system/storage.rst:32 -msgid "**You noticed slow updates of Zammad?**" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.phone}``" +msgstr "``#{ticket.customer.phone}``" -#: ../settings/system/storage.rst:34 -msgid "" -"While Zammad is beeing updated, it enforces a recursive \"change " -"owner\" (chown) for this directory. For instances with many files this can " -"be time consuming. To mitigate that you can move your files and create a " -"symlink in ``/opt/zammad/storage/`` to the new directory. Of course you have " -"to make sure on your own that the permissions are always correct." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > VIP" +msgstr "Bilet > Müşteri > VIP" -#: ../settings/system/storage.rst:95 -msgid "Simple Storage (S3)" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.vip}``" +msgstr "``#{ticket.customer.vip}``" -#: ../settings/system/storage.rst:41 -msgid "" -"To use the Simple Storage (S3), you have to provide some settings, which " -"can't be accessed in the UI (see instructions below)." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Web" +msgstr "Bilet > Müşteri > Web" -#: ../settings/system/storage.rst:44 -msgid "" -"⚠️ Please note that the current implementation is in its early stages and can " -"be modified in the future." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.web}``" +msgstr "``#{ticket.customer.web}``" -#: ../settings/system/storage.rst:47 -msgid "" -"The prerequisite is to have access to a S3-compatible storage and to have " -"all necessary parameters available (which depends on your storage provider; " -"if in doubt, please ask there for help)." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Escalation at" +msgstr "Bilet > Yükselme" -#: ../settings/system/storage.rst:51 -msgid "Steps to configure S3:" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.escalation_at}``" +msgstr "``#{ticket.escalation_at}``" -#: ../settings/system/storage.rst:53 -msgid "" -"Copy ``config/zammad/storage.yml.dist`` to ``config/zammad/storage.yml``" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable" +msgstr "``2019-10-07 16:25:00 UTC`` veya uygulanabilir değilse boş" -#: ../settings/system/storage.rst:54 -msgid "Edit the copied file in one of the following ways:" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > First response" +msgstr "Bilet > İlk yanıt" -#: ../settings/system/storage.rst:56 -msgid "" -"Either provide your S3 configuration with one attribute per line like in the " -"upper area of the file" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.first_response_at}``" +msgstr "``#{ticket.first_response_at}``" -#: ../settings/system/storage.rst:58 -msgid "" -"Or provide your S3 configuration as an URL (which you can find at the end of " -"the file). Note: you can also provide this URL as environment variable (:" -"docs:`see system documentation `) without using this yml-file." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable yet" +msgstr "``2019-10-07 16:25:00 UTC`` veya henüz uygulanabilir değilse boş" -#: ../settings/system/storage.rst:62 -msgid "" -"We recommend the deletion of the not used configuration style to avoid " -"inconsistencies." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Assign Follow-Ups" +msgstr "Bilet > Grup > Atanmış Takipler" -#: ../settings/system/storage.rst:65 -msgid "Restart Zammad so the config file / environment variable is loaded" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_assignment}``" +msgstr "``#{ticket.group.follow_up_assignment}``" -#: ../settings/system/storage.rst:66 -msgid "" -"Set the \"Storage Method\" in Zammad to ``Simple Storage (S3)`` in Settings " -"> System > Storage and click on \"Submit\". After that, Zammad checks your " -"configuration and the connection to the service and will raise an error " -"message if something is wrong." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Assignment Timeout" +msgstr "Bilet > Grup > Atanma Zaman Aşımı" -#: ../settings/system/storage.rst:72 -msgid "A very simple storage configuration could look like this:" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.assignment_timeout}``" +msgstr "``#{ticket.group.assignment_timeout}``" -#: ../settings/system/storage.rst:85 -msgid "" -"Before setting the storage method to ``Simple Storage (S3)`` (step 4), " -"please make sure to have a working setup." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``20`` or empty if not configured" +msgstr "``20`` veya yapılandırılmadıysa boş" -#: ../settings/system/storage.rst:88 -msgid "" -"You can verify this by running ``rails r 'Rails.logger = Logger.new(STDOUT); " -"pp Store::Provider::S3.ping?'`` in your Zammad directory. If everything is " -"fine, you should see ``true``, else you should see ``false`` and a simple " -"error message." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Follow-up possible" +msgstr "Bilet > Grup > Takip mümkün" -#: ../settings/system/storage.rst:93 -msgid "" -"If you installed Zammad through a package manager (rather than from source), " -"replace ``rails r`` with ``zammad run rails r`` above. To learn more, see :" -"docs:`Administration via Console `." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_possible}``" +msgstr "``#{ticket.group.follow_up_possible}``" -#: ../settings/ticket.rst:4 -msgid "" -"Here you can adjust general ticket settings. Additional ones for the ticket " -"composer interface can be found in the :doc:`/misc/composer`." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``no`` or ``yes``" +msgstr "``hayır`` veya ``evet``" -#: ../settings/ticket.rst:11 -msgid "Ticket Hook (default: ``Ticket#``)" -msgstr "Bilet Kancası (varsayılan: ``Bilet#``)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Name" +msgstr "Bilet > Grup > Ad" -#: ../settings/ticket.rst:11 -msgid "The identifier for a ticket; *e.g.,* Ticket#, Call#, MyTicket#." -msgstr "Bir bilet için tanımlayıcılar; *ör.,* Bilet#, Arama#, Biletim#." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.name}``" +msgstr "``#{ticket.group.name}``" -#: ../settings/ticket.rst:38 -msgid "Ticket Hook Position (default: ``right``)" -msgstr "Bilet Kancası Pozisyonu (varsayılan: ``sağ``)" +#: ../misc/variables/ticket.rst:1 +msgid "``Sales``" +msgstr "``Satışlar``" -#: ../settings/ticket.rst:14 -msgid "" -"With this setting you can decide (if) where to insert the ticket number." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Note" +msgstr "Bilet > Grup > Not" -#: ../settings/ticket.rst:20 -msgid "*Right*" -msgstr "*Sağ*" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.note}``" +msgstr "``#{ticket.group.note}``" -#: ../settings/ticket.rst:17 -msgid "" -"This setting will add the ticket reference on the right site of the subject." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``Note about this group``" +msgstr "``Bu grup hakkında not``" -#: ../settings/ticket.rst:20 -msgid "Example: ``Some Subject [Ticket#12345]``" -msgstr "Örnek: ``Konu [Bilet#12345]``" +#: ../misc/variables/ticket.rst:1 +#, fuzzy +msgid "Ticket > ID" +msgstr "Bilet > #" -#: ../settings/ticket.rst:26 -msgid "*Left*" -msgstr "*Sol*" +#: ../misc/variables/ticket.rst:1 +#, fuzzy +msgid "``#{ticket.id}``" +msgstr "``#{ticket.title}``" -#: ../settings/ticket.rst:23 -msgid "" -"This setting will add the ticket reference on the left site of the subject." -msgstr "" +#: ../misc/variables/ticket.rst:1 +#, fuzzy +msgid "``17``, ``5281``, ..." +msgstr "``yeni``, ``açık``, ..." -#: ../settings/ticket.rst:26 -msgid "Example: ``[Ticket#12345] Some Subject``" -msgstr "Örnek: ``[Bilet#12345] Konu``" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact (agent)" +msgstr "Bilet > Son iletişim (aracı)" -#: ../settings/ticket.rst:29 -msgid "*None*" -msgstr "*Hiçbiri*" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_agent_at}``" +msgstr "``#{ticket.last_contact_agent_at}``" -#: ../settings/ticket.rst:29 -msgid "This will completely remove ticket references from the subject." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact (customer)" +msgstr "Bilet > Son iletişim (müşteri)" -#: ../settings/ticket.rst:33 -msgid "" -"Please ensure to take a look at :doc:`/channels/email/settings` within the " -"email channel to ensure you have at least one reference that helps Zammad to " -"assign follow-ups correctly." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_customer_at}``" +msgstr "``#{ticket.last_contact_customer_at}``" -#: ../settings/ticket.rst:37 +#: ../misc/variables/ticket.rst:1 +#, fuzzy msgid "" -"Disabling this and not setting up any further follow up search will lead to " -"unexpected results!" +"``2019-10-07 16:25:00 UTC`` or empty if not applicable yet (Please note " +"`Ticket last contact behavior Settings `_ for this)" msgstr "" +"``2019-10-07 16:25:00 UTC`` veya henüz uygun değilse boş (Bunun için lütfen " +"`Bilet son iletişim davranışı Ayarları`_na dikkat edin)" -#: ../settings/ticket.rst:65 -msgid "" -"Ticket Last Contact Behaviour (default: ``Use the start time of the last " -"customer thread (which may consist of multiple articles).``)" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact" +msgstr "Bilet > Son iletişim" -#: ../settings/ticket.rst:41 -msgid "" -"This setting changes the way Zammad updates the ``Last Contact`` value of a " -"ticket. This is fairly important for overviews and what you expect upon " -"ticket updates of a customer." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_at}``" +msgstr "``#{ticket.last_contact_at}``" -#: ../settings/ticket.rst:52 -msgid "" -"Use the start time of the last customer thread (which may consist of " -"multiple articles)." -msgstr "" +#: ../misc/variables/ticket.rst:1 +#, fuzzy +msgid "Ticket > Number" +msgstr "bilet numarası" -#: ../settings/ticket.rst:46 -msgid "" -"If this option is chosen, Zammad will update the last updated value just " -"once if a customer replies. After that, Zammad will wait for an agent to " -"react." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.number}``" +msgstr "``#{ticket.number}``" -#: ../settings/ticket.rst:50 -msgid "" -"This comes in handy if you want to work tickets in the order of their first " -"update. This will not change ticket orders if customers decide to \"bump\" " -"the ticket affected." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``31001``, ``201910731001``, ..." +msgstr "``31001``, ``201910731001``, ..." -#: ../settings/ticket.rst:57 -msgid "Use the time of the very last customer article." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain based assignment" +msgstr "Bilet > Organizasyon > Alan adına göre atama" -#: ../settings/ticket.rst:55 -msgid "" -"When setting this option, Zammad will always update the last updated value. " -"This means that if ordering by ``Last Update``, ticket orders will change if " -"customers \"bump\" the ticket." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain_assignment}``" +msgstr "``#{ticket.organization.domain_assignment}``" -#: ../settings/ticket.rst:64 -msgid "Last contact value used on :doc:`/manage/overviews`" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain" +msgstr "Bilet > Organizasyon > Alan adı" -#: ../settings/ticket.rst:65 -msgid "Last contact value used on :doc:`/manage/trigger`" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain}``" +msgstr "``#{ticket.organization.domain}``" -#: ../settings/ticket.rst:88 -msgid "" -"Ticket Organization Reassignment (default: ``Update the most recent tickets." -"``)" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``domain.tld`` or empty if not set" +msgstr "``domain.tld``` veya ayarlanmadıysa boş" -#: ../settings/ticket.rst:68 -msgid "" -"This setting changes the way Zammad updates the organization field of the " -"tickets whenever the primary organization of a user is changed." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Name" +msgstr "Bilet > Organizasyon > Ad" -#: ../settings/ticket.rst:74 -msgid "Update the most recent tickets." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.name}``" +msgstr "``#{ticket.organization.name}``" -#: ../settings/ticket.rst:72 -msgid "" -"If this option is chosen, Zammad will update the 100 most recent tickets " -"where the user is the ticket customer. The ticket organization field will be " -"automatically set to the new primary organization of the user." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``Zammad GmbH`` or empty if not set" +msgstr "``Zammad GmbH``` veya ayarlanmadıysa boş" -#: ../settings/ticket.rst:88 -#, fuzzy -msgid "Do not update any tickets." -msgstr "biletleri günceller" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Note" +msgstr "Bilet > Organizasyon > Not" -#: ../settings/ticket.rst:77 -msgid "" -"When choosing this option, Zammad will not update any tickets when the " -"user's primary organization is changed." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.note}``" +msgstr "``#{ticket.organization.note}``" -#: ../settings/ticket.rst:80 -msgid "**Use with care!**" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Shared organization" +msgstr "Bilet > Organizasyon > Paylaşılan organizasyon" -#: ../settings/ticket.rst:82 -msgid "" -"Using this option may lead to inconsistencies in the system as the ticket " -"organization may become decoupled from the ticket customer." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.shared}``" +msgstr "``#{ticket.organization.shared}``" -#: ../settings/ticket.rst:85 -msgid "" -"However, you may use this option if you wish to maintain :ref:`the shared " -"access ` to the ticket for all organization " -"members of the original organization of the customer." -msgstr "" +#: ../misc/variables/ticket.rst:1 +#, fuzzy +msgid "Ticket > Organization > VIP" +msgstr "Bilet > Organizasyon > Not" -#: ../settings/ticket.rst:110 -msgid "Ticket Number Format (default: ``Increment (SystemID.Counter)``)" -msgstr "Bilet Numarası Formatı (varsayılan: ``Artış (SystemID.Counter)``)" +#: ../misc/variables/ticket.rst:1 +#, fuzzy +msgid "``#{ticket.organization.vip}``" +msgstr "``#{ticket.organization.domain}``" -#: ../settings/ticket.rst:94 -msgid "" -"This setting defines the way Zammad's ticket number will look. Changing this " -"setting in production will cause follow up detection to fail." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Address" +msgstr "Bilet > Sahip > Adres" -#: ../settings/ticket.rst:102 -msgid "Increment (SystemID.Counter)" -msgstr "Artış (SystemID.Counter)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.address}``" +msgstr "``#{ticket.owner.address}``" -#: ../settings/ticket.rst:98 -msgid "" -"The increment value contains the SystemID (automatically generated during " -"installation) and a increment which counts up with every new Ticket. The " -"increment will automatically get another digit if needed." -msgstr "" +#: ../misc/variables/ticket.rst:1 +#, fuzzy +msgid "Ticket > Owner > Avatar" +msgstr "Bilet > Sahip > Faks" -#: ../settings/ticket.rst:102 -msgid "Examples: ``1010138``, ``1010139``" -msgstr "Örnekler: ``1010138``, ``1010139``" +#: ../misc/variables/ticket.rst:1 +#, fuzzy +msgid "``#{ticket.owner.avatar(60,60)}``" +msgstr "``#{ticket.owner.lastname}``" -#: ../settings/ticket.rst:110 -msgid "Date (Year.Month.Day.SystemID.Counter)" -msgstr "Tarih (Year.Month.Day.SystemID.Counter)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Department" +msgstr "Bilet > Sahip > Bölüm" -#: ../settings/ticket.rst:105 -msgid "" -"This version of the ticket number is fairly long. However, because it " -"contains the date of ticket creation, it also allows you to see when the " -"ticket has been created. You may feel familiar with this number format if " -"you've worked with OTRS already." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.department}``" +msgstr "``#{ticket.owner.department}``" -#: ../settings/ticket.rst:110 -msgid "Examples: ``201206231010138``, ``201206231010139``" -msgstr "Örnekler: ``201206231010138``, ``201206231010139``" +#: ../misc/variables/ticket.rst:1 +msgid "``Support`` or empty if not set" +msgstr "``Destek`` veya ayarlanmadıysa boş" -#: ../settings/ticket.rst:137 -msgid "OPTIONS" -msgstr "SEÇENEKLER" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Email" +msgstr "Bilet > Sahip > E-posta" -#: ../settings/ticket.rst:113 -msgid "" -"The below options allow you to further customize your ticket number. The " -"availability of options differ depending of the chosen ticket number format " -"above." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.email}``" +msgstr "``#{ticket.owner.email}``" -#: ../settings/ticket.rst:122 -msgid "Checksum (default: ``no``)" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``agent@company.tld`` or empty if not set" +msgstr "``agent@company.tld`` veya ayarlanmadıysa boş" -#: ../settings/ticket.rst:118 -msgid "" -"If set to yes, we'll built a checksum to further \"unique\" the ticket " -"number of your system. If you're dealing with many other ticket systems this " -"might help to prevent false positive follow up detection on tickets." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Fax" +msgstr "Bilet > Sahip > Faks" -#: ../settings/ticket.rst:122 -msgid "This will also add another digit to the ticket number." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.fax}``" +msgstr "``#{ticket.owner.fax}``" -#: ../settings/ticket.rst:137 -msgid "Min. size of Number (default: ``5``)" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Firstname" +msgstr "Bilet > Sahip > Ad" -#: ../settings/ticket.rst:125 -msgid "" -"This setting defines the minimum length of your ticket number. If your " -"counter is not yet high enough, Zammad will fill the number with zeros to " -"ensure the wanted length." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.firstname}``" +msgstr "``#{ticket.owner.firstname}``" -#: ../settings/ticket.rst:129 -msgid "" -"Please note that the minimum length is ``3`` (SystemID + at least one digit " -"if below 10). Also, if the length is no longer long enough, the number will " -"automatically get one digit longer. Ticket-Numbers **do not overflow**, thus " -"it's save to keep it at 5 or set it lower if wanted." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``Max`` or empty if not set" +msgstr "``Max`` veya ayarlanmadıysa boş" -#: ../settings/ticket.rst:135 -msgid "" -"This option is only available if ticket number format is set to " -"``Increment``!" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Lastname" +msgstr "Bilet > Sahip > Soyadı" -#: ../settings/ticket.rst:142 -msgid "Auto-Assignment" -msgstr "Otomatik Atama" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.lastname}``" +msgstr "``#{ticket.owner.lastname}``" -#: ../settings/ticket.rst:144 -msgid "" -"In a larger Zammad environment, it happens that several agents open the same " -"ticket at the same time. Although collision detection is then effective, the " -"efficiency of processing can be increased by means of the automatic " -"assignment of tickets when a ticket is opened." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``Mustermann`` or empty if not set" +msgstr "``Mustermann`` veya ayarlanmadıysa boş" -#: ../settings/ticket.rst:149 -msgid "" -"The automatic assignment of tickets can be activated and configured in the " -"admin area under Settings > Ticket > Auto Assignment." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Login" +msgstr "Bilet > Sahip > Giriş" -#: ../settings/ticket.rst:152 -msgid "" -"The auto assignment only works if the ticket has no owner yet. By default, " -"the agent can always reset the ticket owner to ``-`` if needed." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.login}``" +msgstr "``#{ticket.owner.login}``" -#: ../settings/ticket.rst:155 -msgid "" -"If you want to use this function for only specific tickets, you can " -"configure the conditions accordingly to meet your requirement. By default " -"the condition affects all tickets with the state ``open``." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``agent``" +msgstr "``aracı``" -#: ../settings/ticket.rst:161 -msgid "" -"If you need to exclude users (e.g. a group leader), you can search and " -"select the desired agents in the ``Exception Users`` list. The search " -"function in this area is only effective, if you have too many agents to " -"display at once to help you with the configuration." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Mobile" +msgstr "Bilet > Sahip > Mobil" -#: ../settings/ticket.rst:167 -#, fuzzy -msgid "Notifications" -msgstr "Bildirimleri Engelle" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.mobile}``" +msgstr "``#{ticket.owner.mobile}``" -#: ../settings/ticket.rst:191 -#, fuzzy -msgid "Default Notifications" -msgstr "E-posta Bildirimi" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Note" +msgstr "Bilet > Sahip > Not" -#: ../settings/ticket.rst:170 -msgid "" -"This setting allows you to configure the default ticket notifications that " -"will be applied to all new agent users (incl. users who were just assigned " -"agent role). Simply change the notification matrix to desired state and " -"press **Save**." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.note}``" +msgstr "``#{ticket.owner.note}``" -#: ../settings/ticket.rst:175 -msgid "" -"In case an agent already exists, their ticket notification preferences will " -"be preserved. Optionally, you can also **Apply current defaults to all " -"agents**." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Phone" +msgstr "Bilet > Sahip > Telefon" -#: ../settings/ticket.rst:181 -msgid "" -"**Potential time-consuming action:** Applying default ticket notifications " -"to all agent users may take some time to complete, be patient! The exact " -"time will depend on the size of your system and the number of agents." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.phone}``" +msgstr "``#{ticket.owner.phone}``" -#: ../settings/ticket.rst:185 -msgid "" -"**Active agents only!** When current default ticket notifications are " -"applied, only active agent users are considered. In case an agent is re-" -"activated *after* this action, they will still have the old notification " -"configuration." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > VIP" +msgstr "Bilet > Sahip > VIP" -#: ../settings/ticket.rst:190 -msgid "" -"In case you want to go back to the initial state of ticket notifications, " -"you can click on **Reset to default** button." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.vip}``" +msgstr "``#{ticket.owner.vip}``" -#: ../settings/ticket.rst:194 ../settings/ticket.rst:196 -#, fuzzy -msgid "Duplicate Detection" -msgstr "Uygulama açıklaması" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Web" +msgstr "Bilet > Sahip > Web" -#: ../settings/ticket.rst:236 ../settings/ticket.rst:238 -#, fuzzy -msgid "Detect Duplicate Ticket Creation" -msgstr "Bilet oluşturulduğunda" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.web}``" +msgstr "``#{ticket.owner.web}``" -#: ../settings/ticket.rst:197 ../settings/ticket.rst:199 -msgid "" -"This setting turns on the duplicate ticket detection mechanism during ticket " -"creation. If similar tickets are found in the system, a suitable warning " -"will be shown to the user trying to create a ticket." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``https://zammad.com`` or empty if not set" +msgstr "``https://zammad.com``` veya ayarlanmadıysa boş" -#: ../settings/ticket.rst:204 ../settings/ticket.rst:206 -msgid "A Sample Duplicate Ticket Warning" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Pending till" +msgstr "Bilet > Bekleme süresi" -#: ../settings/ticket.rst:206 ../settings/ticket.rst:208 -msgid "" -"You can choose which ticket attributes will be matched by selecting them in " -"**Attributes to compare** field. Only if the ticket attribute value provided " -"by the user in the ticket create form is *equal* with the attribute in an " -"existing ticket, the warning will be shown." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.pending_time}``" +msgstr "``#{ticket.pending_time}``" -#: ../settings/ticket.rst:211 ../settings/ticket.rst:213 -msgid "**Warning title** and **Warning message** are configurable as well." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not set" +msgstr "``2019-10-07 16:25:00 UTC`` veya ayarlanmadıysa boş" -#: ../settings/ticket.rst:213 ../settings/ticket.rst:215 -msgid "" -"You can limit the detection only to certain user roles. By default, only " -"agents will see the warning." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Priority > Name" +msgstr "Bilet > Öncelik > Ad" -#: ../settings/ticket.rst:216 ../settings/ticket.rst:218 -msgid "" -"If you don't want to show the matched tickets as part of the warning, you " -"can set **Show matching ticket(s) in the warning** setting to *no*." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.priority.name}``" +msgstr "``#{ticket.priority.name}``" -#: ../settings/ticket.rst:219 ../settings/ticket.rst:221 -msgid "" -"By default, **Permission level for looking up ticket** is set to *User*, " -"which means user permissions will be honored during sarch. The user will " -"see the warning only if tickets they have access to are matched. " -"Alternatively, you can set this setting to *System*, in which case the " -"search will happen within *all* tickets in the system, regardless of user " -"permissions." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``2 normal``" +msgstr "``2 normal``" -#: ../settings/ticket.rst:225 ../settings/ticket.rst:227 -msgid "**🦺 Safety first!**" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > State > Name" +msgstr "Bilet > Durum > Ad" -#: ../settings/ticket.rst:227 ../settings/ticket.rst:229 -msgid "" -"Even if the permission level is set to *System*, the user will not be shown " -"the tickets they don't have access to in the warning, even if they match." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.state.name}``" +msgstr "``#{ticket.state.name}``" -#: ../settings/ticket.rst:231 ../settings/ticket.rst:233 -msgid "" -"However, just the confirmation about the existence of the tickets in the " -"system may be considered an unwanted information disclosure. Use this option " -"carefully!" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``new``, ``open``, ..." +msgstr "``yeni``, ``açık``, ..." -#: ../settings/ticket.rst:235 ../settings/ticket.rst:237 -msgid "" -"Finally, you can configure between matching within **All tickets** or **Open " -"tickets** only by setting **Match tickets in following states**. Depending " -"on the current ticket state, a ticket may or not be matched." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Tags" +msgstr "Bilet > Etiketler" -#: ../system/core-workflows.rst:2 -msgid "Core Workflows" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.tags}``" +msgstr "``#{ticket.tags}``" -#: ../system/core-workflows.rst:4 +#: ../misc/variables/ticket.rst:1 msgid "" -"Core Workflows allow you to adjust object attributes in many ways. For " -"example:" -msgstr "" - -#: ../system/core-workflows.rst:7 -msgid "show / hide fields" -msgstr "" +"Currently not available, see `Issue 2769 `_" +msgstr "Şu anda mevcut değil, `Issue 2769 `_a göz atın" -#: ../system/core-workflows.rst:8 -msgid "adjust mandatory setting" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Title" +msgstr "Bilet > Başlık" -#: ../system/core-workflows.rst:9 -msgid "manipulate available options" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.title}``" +msgstr "``#{ticket.title}``" -#: ../system/core-workflows.rst:11 +#: ../misc/variables/ticket.rst:1 msgid "" -"With this, you can provide exactly the information your users really need!" +"``My amazing Subject`` (normally subject, can be edited within Interface and " +"thus differ)" msgstr "" +"``Benim harika Konum`` (normalde konu, Arayüzden değiştirilebilir bu nedenle " +"farklı)" -#: ../system/core-workflows.rst:15 -msgid "" -"If the pre-defined :doc:`/system/objects` are not enough, please add them " -"beforehand." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated at" +msgstr "Bilet > Güncelleme" -#: ../system/core-workflows.rst:17 -msgid "" -"If you experience slow or unreliable field updates, please see :ref:`Core " -"Workflow Ajax Modus `" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_at}``" +msgstr "``#{ticket.updated_at}``" -#: ../system/core-workflows.rst:22 -msgid "" -"This is a very enhanced functionality and can cause unexpected UI behavior. " -"Please ensure to test your use cases after configuration to reduce surprises." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Address" +msgstr "Bilet > Güncelleyen > Adres" -#: ../system/core-workflows.rst:None -msgid "Dialogue for adding a new workflow" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.address}``" +msgstr "``#{ticket.updated_by.address}``" -#: ../system/core-workflows/condition-operators.rst:2 -msgid "Core Workflow Condition Operators" -msgstr "" +#: ../misc/variables/ticket.rst:1 +#, fuzzy +msgid "Ticket > Updated by > Avatar" +msgstr "Bilet > Güncelleyen > Faks" -#: ../system/core-workflows/condition-operators.rst:4 -msgid "" -"You might know that there is a separate section for explaining :doc:" -"`condition operators `. Head over there to " -"see a detailed explanation of many conditions and operators." -msgstr "" +#: ../misc/variables/ticket.rst:1 +#, fuzzy +msgid "``#{ticket.updated_by.avatar(60,60)}``" +msgstr "``#{ticket.updated_by.lastname}``" -#: ../system/core-workflows/condition-operators.rst:8 -msgid "" -"Due to differences to other places in Zammad which are also using conditions " -"(e.g. triggers), you can find a dedicated description of operators for core " -"workflows below." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Department" +msgstr "Bilet > Güncelleyen > Bölüm" -#: ../system/core-workflows/condition-operators.rst:12 -msgid "" -"Be aware that the availability of the operators depends on the selected " -"attribute and its field type. Some of the operators may only be available " -"for system attributes (e.g. for \"tags\", \"active\")." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.department}``" +msgstr "``#{ticket.updated_by.department}``" -#: ../system/core-workflows/condition-operators.rst:20 -msgid "Operator" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Email" +msgstr "Bilet > Güncelleyen > E-posta" -#: ../system/core-workflows/condition-operators.rst:22 -msgid "after (absolute)" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.email}``" +msgstr "``#{ticket.updated_by.email}``" -#: ../system/core-workflows/condition-operators.rst:23 -msgid "Matches if a date/time is after a specific point in time." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Fax" +msgstr "Bilet > Güncelleyen > Faks" -#: ../system/core-workflows/condition-operators.rst:24 -msgid "after (relative)" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.fax}``" +msgstr "``#{ticket.updated_by.fax}``" -#: ../system/core-workflows/condition-operators.rst:25 -msgid "Matches if a time span after a specified event has passed." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Firstname" +msgstr "Bilet > Güncelleyen > Ad" -#: ../system/core-workflows/condition-operators.rst:26 -msgid "before (absolute)" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.firstname}``" +msgstr "``#{ticket.updated_by.firstname}``" -#: ../system/core-workflows/condition-operators.rst:27 -msgid "Matches if a date/time is before a specific point in time." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Lastname" +msgstr "Bilet > Güncelleyen > Soyadı" -#: ../system/core-workflows/condition-operators.rst:28 -msgid "before (relative)" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.lastname}``" +msgstr "``#{ticket.updated_by.lastname}``" -#: ../system/core-workflows/condition-operators.rst:29 -msgid "Matches if a time span after a specified event has not passed." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Login" +msgstr "Bilet > Güncelleyen > Giriş" -#: ../system/core-workflows/condition-operators.rst:30 -#, fuzzy -msgid "contains" -msgstr "İletişim" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.login}``" +msgstr "``#{ticket.updated_by.login}``" -#: ../system/core-workflows/condition-operators.rst:31 -msgid "Matches if a specified value is present." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Mobile" +msgstr "Bilet > Güncelleyen > Mobil" -#: ../system/core-workflows/condition-operators.rst:33 -msgid "Matches if all of the specified values are present." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.mobile}``" +msgstr "``#{ticket.updated_by.mobile}``" -#: ../system/core-workflows/condition-operators.rst:35 -msgid "Matches if none of the specified values are present." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Note" +msgstr "Bilet > Güncelleyen > Not" -#: ../system/core-workflows/condition-operators.rst:36 -msgid "contains not" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.note}``" +msgstr "``#{ticket.updated_by.note}``" -#: ../system/core-workflows/condition-operators.rst:37 -msgid "Matches if a specified value is not present." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Phone" +msgstr "Bilet > Güncelleyen > Telefon" -#: ../system/core-workflows/condition-operators.rst:39 -msgid "Matches if one specified value is present." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.phone}``" +msgstr "``#{ticket.updated_by.phone}``" -#: ../system/core-workflows/condition-operators.rst:41 -msgid "Matches if one specified value is not present." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > VIP" +msgstr "Bilet > Güncelleyen > VIP" -#: ../system/core-workflows/condition-operators.rst:42 -msgid "does not match regex" -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.vip}``" +msgstr "``#{ticket.updated_by.vip}``" -#: ../system/core-workflows/condition-operators.rst:43 -msgid "Matches if content doesn't fit to regex rule." -msgstr "" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Web" +msgstr "Bilet > Güncelleyen > Web" -#: ../system/core-workflows/condition-operators.rst:44 -msgid "ends with" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.web}``" +msgstr "``#{ticket.updated_by.web}``" + +#: ../settings/branding.rst:10 +#, fuzzy +msgid "Product Name" +msgstr "*Ürün adı*" + +#: ../settings/branding.rst:7 +msgid "" +"Defines the name of the application, shown in the web interface, tabs and " +"title bar of the web browser." msgstr "" +"Web arayüzünde, sekmelerde ve web tarayıcısının başlık çubuğunda gösterilen " +"uygulamanın adını tanımlar." -#: ../system/core-workflows/condition-operators.rst:45 -msgid "Matches if content ends with specified value." +#: ../settings/branding.rst:10 +msgid "Default value: ``Zammad Helpdesk``" msgstr "" -#: ../system/core-workflows/condition-operators.rst:46 -msgid "ends with one of" -msgstr "" +#: ../settings/branding.rst:13 +msgid "Will be shown in the app and is included in email footers." +msgstr "Uygulamada gösterilecek ve e-posta altbilgilerine dahil edilecek." -#: ../system/core-workflows/condition-operators.rst:47 -msgid "Matches if content ends with one of the specified values." -msgstr "" +#: ../settings/branding.rst:19 +#, fuzzy +msgid "Logo" +msgstr "*Logo*" -#: ../system/core-workflows/condition-operators.rst:48 -msgid "from (relative)" -msgstr "" +#: ../settings/branding.rst:16 +#, fuzzy +msgid "Defines the logo of the application, shown in the login page of Zammad." +msgstr "Web arayüzünde gösterilen uygulamanın logosunu tanımlar." -#: ../system/core-workflows/condition-operators.rst:49 -msgid "Matches if date/time is after a period of time after an event." +#: ../settings/branding.rst:18 +msgid "" +"Ensure to hit the \"Submit\" button after uploading the logo. Otherwise your " +"change will not be saved." msgstr "" -#: ../system/core-workflows/condition-operators.rst:51 -msgid "Matches if content is equal to a specified value." +#: ../settings/branding.rst:22 +msgid "" +"Allows to set the default language of the Zammad instance. The here defined " +"locale mostly acts as a fallback for:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:52 -msgid "is any of" +#: ../settings/branding.rst:25 +msgid "user preferences (if Zammad can't detect the users locale)" msgstr "" -#: ../system/core-workflows/condition-operators.rst:53 -msgid "Matches if content is equal to any of specified values." +#: ../settings/branding.rst:26 +msgid "CSV output (reporting, time accounting)" msgstr "" -#: ../system/core-workflows/condition-operators.rst:54 -msgid "is modified" +#: ../settings/branding.rst:30 +msgid "Define the timezone of your Zammad installation." msgstr "" -#: ../system/core-workflows/condition-operators.rst:55 -msgid "Matches if content is modified." +#: ../settings/branding.rst:32 +msgid "" +"This does not have any effect on timings for your agents or how Zammad " +"stores date and time values." msgstr "" -#: ../system/core-workflows/condition-operators.rst:57 -#: ../system/core-workflows/condition-operators.rst:61 -msgid "True from the moment of changing content until form submit." +#: ../settings/branding.rst:35 +msgid "Changing this value has direct consequences on the following areas:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:58 -msgid "is modified to" +#: ../settings/branding.rst:37 +msgid ":doc:`/manage/scheduler` tasks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:59 -msgid "Matches if content is modified to a specific value." +#: ../settings/branding.rst:38 +msgid "search indexing (and thus reporting)" msgstr "" -#: ../system/core-workflows/condition-operators.rst:62 -msgid "is none of" +#: ../settings/branding.rst:40 +#, fuzzy +msgid "calendar subscriptions" +msgstr "Açıklama" + +#: ../settings/branding.rst:41 +msgid "browser printing" msgstr "" -#: ../system/core-workflows/condition-operators.rst:63 -msgid "Matches if content is none of any specified values." +#: ../settings/branding.rst:43 +msgid "" +"Please note that some of above are fallbacks in case Zammad could not detect " +"the agents timezone correctly." msgstr "" -#: ../system/core-workflows/condition-operators.rst:65 -msgid "Matches if content is not equal to a specified value." +#: ../settings/branding.rst:77 +#, fuzzy +msgid "Pretty Date" +msgstr "*Güzel Tarih*" + +#: ../settings/branding.rst:47 +#, fuzzy +msgid "" +"This setting allows you to define how Zammad should display time stamps " +"within the interface to all users." msgstr "" +"Bu bölüm, yerel kullanıcı hesapları için parola gereksinimlerini " +"tanımlamanıza olanak tanır." -#: ../system/core-workflows/condition-operators.rst:67 -msgid "Matches if content is present." +#: ../settings/branding.rst:50 +msgid "" +"This does not have any effect on how Zammad returns e.g. time values via " +"variables." msgstr "" -#: ../system/core-workflows/condition-operators.rst:68 +#: ../settings/branding.rst:77 #, fuzzy -msgid "just changed" -msgstr "Exchange" +msgid "Choose in between the following options:" +msgstr "Aşağıdaki ayarlardan şunları düzenleyebilirsin:" -#: ../system/core-workflows/condition-operators.rst:69 -msgid "Matches if content has changed." +#: ../settings/branding.rst:64 +msgid "relative" msgstr "" -#: ../system/core-workflows/condition-operators.rst:71 -#: ../system/core-workflows/condition-operators.rst:75 +#: ../settings/branding.rst:55 msgid "" -"Only true for the moment of changing content until next form field action/" -"click." +"This timestamp shows a relative time span until it switches to a date. Over " +"time, it will change as follows:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:72 -msgid "just changed to" +#: ../settings/branding.rst:58 +msgid "just now" msgstr "" -#: ../system/core-workflows/condition-operators.rst:73 -msgid "Matches if content has changed to a specified value." +#: ../settings/branding.rst:59 +msgid "5 minutes ago" msgstr "" -#: ../system/core-workflows/condition-operators.rst:76 -msgid "matches regex" +#: ../settings/branding.rst:60 +msgid "3 days 1 hour ago" msgstr "" -#: ../system/core-workflows/condition-operators.rst:77 -msgid "Matches if value fits to regex rule." +#: ../settings/branding.rst:61 +msgid "``03/04/2022``" msgstr "" -#: ../system/core-workflows/condition-operators.rst:79 -msgid "Matches if no content is present." +#: ../settings/branding.rst:63 +msgid "Hovering the timestamp helps, you'll always get a clean timestamp then." msgstr "" -#: ../system/core-workflows/condition-operators.rst:80 -msgid "starts with" +#: ../settings/branding.rst:71 +msgid "absolute" msgstr "" -#: ../system/core-workflows/condition-operators.rst:81 -msgid "Matches if content starts with specified value." +#: ../settings/branding.rst:67 +msgid "" +"This timestamp always includes the week day. For one week after creation, " +"the timestamp will not contain the date itself: Thursday 18:35." msgstr "" -#: ../system/core-workflows/condition-operators.rst:82 -msgid "starts with one of" +#: ../settings/branding.rst:71 +msgid "After a week it will switch to: ``Friday 4. Mar 16:00``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:83 -msgid "Matches if content starts with one of the specified values." +#: ../settings/branding.rst:76 +msgid "timestamp" msgstr "" -#: ../system/core-workflows/condition-operators.rst:84 -msgid "till (relative)" +#: ../settings/branding.rst:74 +msgid "" +"This will cause Zammad to show a complete timestamp according to your locale " +"defaults. For English this could be e.g. ``2022/12/03 2:40 pm`` or for " +"German e.g. ``12.03.2022 14:40``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:85 -msgid "Matches if date/time is before a period of time before an event." +#: ../settings/branding.rst:78 +msgid "Default setting: ``relative``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:86 -msgid "today" -msgstr "" +#: ../settings/security.rst:2 +msgid "Security" +msgstr "Güvenlik" -#: ../system/core-workflows/condition-operators.rst:87 -msgid "Matches if date/time is today." +#: ../settings/security.rst:4 +msgid "" +"For your overview we split each tab within security settings into its own " +"page:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:88 -msgid "within last (relative)" +#: ../settings/security/base.rst:2 ../settings/system/base.rst:2 +#: ../settings/ticket.rst:8 +msgid "Base" +msgstr "Temel" + +#: ../settings/security/base.rst:5 +msgid "New User Accounts" msgstr "" -#: ../system/core-workflows/condition-operators.rst:89 +#: ../settings/security/base.rst:9 msgid "" -"Matches if date/time content is within specified period of time before now." +"Activates the `register as a new customer` function on the login page. If " +"set to ``no`` only administrators or agents can create new accounts manually." msgstr "" -#: ../system/core-workflows/condition-operators.rst:91 -msgid "within next (relative)" +#: ../settings/security/base.rst:13 ../settings/security/base.rst:38 +#: ../settings/security/base.rst:66 +msgid "Default setting: ``yes``" msgstr "" -#: ../system/core-workflows/condition-operators.rst:92 -msgid "" -"Matches if date/time content is within specified period of time after now." +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"New User Accounts\" setting" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:2 -msgid "How do they work?" -msgstr "Nasıl çalışırlar?" - -#: ../system/core-workflows/how-do-they-work.rst:4 +#: ../settings/security/base.rst:22 msgid "" -"Core Workflows are executed according to their priority. If two workflows " -"have the same priority, they are executed in alphabetical order based on " -"their **name**." +"Deactivation of above function **does not** deactivate automatic account " +"creation! This means: If a user writes e.g. an email to Zammad and has no " +"account yet, Zammad will automatically create the account. User accounts are " +"a direct dependency of tickets and thus technically mandatory." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:8 -msgid "" -"Because of the way Core Workflows work, all changes to attributes are " -"checked with the application server - please see :doc:`limitations` for " -"possible issues." +#: ../settings/security/base.rst:29 +msgid "Lost Password" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:12 +#: ../settings/security/base.rst:33 msgid "" -"Below we're talking about settings that are important and not self-" -"explanatory." +"Activates the `lost password` function on the login page. If set to ``no`` " +"only administrators may change the user's password - users may update their " +"own password if they're still logged in and they have the required :doc:" +"`permission `." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:17 -msgid "" -"Choose the object context you want to run the workflow in. This will decide " -"on your available attributes and actions." +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"Lost Password\" setting" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:20 -msgid "Ticket objects also have access to the ticket customer." +#: ../settings/security/base.rst:49 +msgid "" +"With third party authentications - but especially LDAP - you may want to " +"disable this function. Zammad **will not** change third party login " +"passwords and instead set or change the local password!" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:25 +#: ../settings/security/base.rst:56 +#, fuzzy +msgid "Password Login" +msgstr "Parola" + +#: ../settings/security/base.rst:60 msgid "" -"Choose in which situation the workflow is applied. Contexts can be combined " -"to avoid duplicate workflows." +"Activates the username & password login by default and if no third-party " +"login is activated. Disabling password login on the Zammad login page only " +"takes effect if you enable any :doc:`third-party`." +msgstr "" + +#: ../settings/security/base.rst:64 +msgid "See :doc:`third-party` for supported third-party logins." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:30 -#, fuzzy -msgid "Creation mask" -msgstr "Makrolar Oluşturmak" +#: ../settings/security/base.rst:0 +msgid "Figure showing de-activated \"Password Login\" setting" +msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:29 +#: ../settings/security/base.rst:77 msgid "" -"If selected, your conditions and actions will affect all applicable creation " -"masks." +"To help administrators to overcome \"login issues\", Zammad automatically " +"offers a password request for administrator users. This allows you to adjust " +"Third-Party applications even if the login does no longer work!" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:34 -msgid "Edit mask" +#: ../settings/security/base.rst:84 +msgid "Session Timeout" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:33 +#: ../settings/security/base.rst:86 msgid "" -"If selected, your conditions and actions will affect all applicable edit " -"masks." +"All settings below by default are set to ``4 weeks``. Session Timeout " +"defines the life time of a users session. As soon as it's reached, Zammad " +"will automatically log off the session in question." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:39 +#: ../settings/security/base.rst:91 msgid "" -"Zammad differentiates between selected and saved conditions. These can be " -"combined wherever needed." +"Zammad takes the highest value set assigned for the user based on the " +"permissions." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:42 -msgid "**⚠️ Restrict workflows to specific roles if needed!**" +#: ../settings/security/base.rst:94 +msgid "``admin``" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:44 -msgid "" -"By default and unless configured in conditions, workflow rules are executed " -"for **all roles**. This also affects your customers!" +#: ../settings/security/base.rst:96 +msgid "``ticket.customer``" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:50 -msgid "Selected Conditions" +#: ../settings/security/base.rst:97 +msgid "``default`` (fallback if user doesn't have above permissions set)" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:48 +#: ../settings/security/base.rst:99 msgid "" -"These conditions are based on form values and match if an appropriate " -"selection is made (e.g. choosing another group in the ticket without " -"saving). This applies for drafts (active selection) and currently saved " -"values." +"All settings act independently from each other allowing you to disable the " +"timeouts for e.g. admins, but not agents." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:64 -msgid "Saved Conditions" +#: ../settings/security/base.rst:115 +#: ../system/integrations/checkmk/api-reference.rst:13 +msgid "Example" +msgstr "Örnek" + +#: ../settings/security/base.rst:107 +msgid "Let's suppose you configured the following session timeouts" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:53 -msgid "" -"These conditions only match if the selected values are stored in the " -"database. It ignores the current value or selection of the field, as long as " -"the changes are not saved (e.g. performing field operations for an existing " -"ticket, which is viewed/opened by an agent)." +#: ../settings/security/base.rst:104 +msgid "default: 3 weeks" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:60 -msgid "" -"Keep in mind that the value has to be available in the situation where you " -"need it. Otherwise the condition won't match." +#: ../settings/security/base.rst:105 +msgid "admin: 2 weeks" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:63 -msgid "" -"Example: you can't perform any actions with *saved condition* on a ticket in " -"creation, because there are no saved values at that time." +#: ../settings/security/base.rst:106 +msgid "ticket.agent: 4 weeks" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:66 -msgid "" -"You can find a description of the condition operators for core workflows :" -"doc:`here `." +#: ../settings/security/base.rst:107 +msgid "ticket.customer: 1 week" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:72 -msgid "" -"Which actions should we run on the relevant fields? The possible actions " -"depend on the object type. However, usually you can at least change the " -"visibility and whether the field is mandatory." +#: ../settings/security/base.rst:115 +msgid "This results in the following situations" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:76 -msgid "Be aware that actions are not available for **related** context." +#: ../settings/security/base.rst:110 +msgid "a user with ``admin`` permission will have a timeout of 2 weeks" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:78 +#: ../settings/security/base.rst:111 msgid "" -"**Example:** Let's assume you are working in the ticket context. While you " -"can have customer *conditions*, you *can't adjust* objects with actions in " -"that scope. That's because this wouldn't have any impact on the ticket " -"dialog. Of course all ticket attributes (state, owner, ...) are available." +"a user with ``admin`` and ``ticket.agent`` permissions will have a timeout " +"of 2 weeks" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:84 +#: ../settings/security/base.rst:113 msgid "" -"Please also have a look at our :doc:`limitations` to be safe from surprises." +"a user with ``ticket.customer`` permission will have a timeout of 1 week" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:88 -msgid "Available Operators" +#: ../settings/security/base.rst:115 +msgid "" +"a user with neither ``admin``, ``ticket.agent`` nor ``ticket.customer`` " +"permissions will have a timeout of 3 weeks" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:90 -msgid "The availability of operators depends on the object type and scope." +#: ../settings/security/password.rst:4 +msgid "" +"This section allows you to define password requirements for the local user " +"accounts." msgstr "" +"Bu bölüm, yerel kullanıcı hesapları için parola gereksinimlerini " +"tanımlamanıza olanak tanır." -#: ../system/core-workflows/how-do-they-work.rst:94 +#: ../settings/security/password.rst:9 msgid "" -"Please note that actions may or may not restrict API based access to " -"attributes. We're displaying the following icons for your overview to " -"understand these limits better:" +"Zammad does **not** allow you to change your LDAP password, instead, it will " +"set a password in its local database which might confuse your users. This " +"might be addressed in the future by `#1169 `_." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:0 -msgid "|api| This icon indicates the action affects the API." +#: ../settings/security/password.rst:14 +msgid "**Exception for admins**" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:163 -msgid "api" +#: ../settings/security/password.rst:16 +msgid "" +"Please note that below password policies *do not* affect administrators " +"setting passwords on user accounts. While this seems strange and not safe we " +"believe that an administrator knowing an user's password is insecure as well." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:0 -msgid "|ui| This icon indicates the action only affects the web interface." +#: ../settings/security/password.rst:21 +msgid "The suggested workflow is either:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:167 -msgid "ui" +#: ../settings/security/password.rst:23 +msgid "" +"to use third party logins to not require local passwords at all **- or -**" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:102 -msgid "show |ui|" +#: ../settings/security/password.rst:25 +msgid "to require your *user to reset the password* upon first login." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:102 -msgid "Display the chosen field. Allows setting of values." +#: ../settings/security/password.rst:27 +msgid "" +"This way administrators are not required to set a user's password at all!" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:109 -msgid "hide |ui|" -msgstr "" +#: ../settings/security/password.rst:31 +#, fuzzy +msgid "Maximum Failed Logins" +msgstr "Maksimum başarısız giriş" -#: ../system/core-workflows/how-do-they-work.rst:105 +#: ../settings/security/password.rst:33 msgid "" -"Hide the chosen field. However, it technically still allows setting the " -"field." +"You can choose a value between ``4`` and ``20``. This defines how often a " +"login to a user account may fail until Zammad will lock it. Your users can " +"always use the \"forgot password\" function to change their password and " +"unlock their account." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:108 -msgid "" -"Please note that the field is **not** gone and still contains an existing " -"value (if set)! Consider *remove* instead, if you want this field to be gone." +#: ../settings/security/password.rst:38 +msgid "The default value is ``10``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:112 -msgid "remove |ui|" +#: ../settings/security/password.rst:42 +msgid "Beside changing the user's password, you can also unlock accounts via" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:112 -msgid "Entirely removes the field. The field value will not be evaluated." +#: ../settings/security/password.rst:44 +msgid ":ref:`user management list `" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:115 -msgid "set mandatory |ui| |api|" +#: ../settings/security/password.rst:45 +msgid ":docs:`console `" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:115 -msgid "Sets the field to mandatory." +#: ../settings/security/password.rst:46 +msgid ":docs:`API `" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:118 -msgid "set optional |ui| |api|" +#: ../settings/security/password.rst:50 +msgid "Failed logins via LDAP no longer lock accounts." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:118 -msgid "Sets the field to optional." -msgstr "" +#: ../settings/security/password.rst:53 +#, fuzzy +msgid "2 Lower Case And 2 Upper Case Characters" +msgstr "2 küçük ve 2 büyük karakter" -#: ../system/core-workflows/how-do-they-work.rst:124 -msgid "add option |ui| |api|" +#: ../settings/security/password.rst:55 +msgid "" +"You can add complexity to passwords by enforcing at least 2 upper and lower " +"case characters." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:121 -msgid "Allows adding options to tree selects or selects." +#: ../settings/security/password.rst:58 ../settings/security/password.rst:83 +msgid "The default value is ``no``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:123 +#: ../settings/security/password.rst:62 +#, fuzzy +msgid "Minimum Length" +msgstr "Minimum uzunluk" + +#: ../settings/security/password.rst:64 msgid "" -"You have to use the \"remove option\" before performing this action. It " -"allows you to use *existing* configured values." +"This defines the minimum password length required for users to provide (from " +"``4`` to ``20``)." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:128 -msgid "remove option |ui| |api|" +#: ../settings/security/password.rst:67 +msgid "The default value is ``6``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:127 -msgid "" -"Allows removing options from tree selects or selects. It allows you to use " -"*existing* configured values." +#: ../settings/security/password.rst:71 +#, fuzzy +msgid "Digit Required" +msgstr "Rakam gerekli" + +#: ../settings/security/password.rst:73 +msgid "This enforces your users to use at least one digit within the password." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:134 -msgid "set fixed to |ui| |api|" +#: ../settings/security/password.rst:75 +msgid "The default value is ``yes``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:131 -msgid "Reduces the available options by your selection." +#: ../settings/security/password.rst:78 +msgid "Special Character Required" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:133 +#: ../settings/security/password.rst:80 msgid "" -"This reduces your workflows in terms of *add option* and *remove option*." +"This setting allows you to improve your password quality even more by " +"enforcing the password to contain at least one special character." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:137 -msgid "fill in |ui|" -msgstr "" +#: ../settings/security/ssl-certificates.rst:2 +#, fuzzy +msgid "SSL Certificates" +msgstr "Sertifika Ekle" -#: ../system/core-workflows/how-do-they-work.rst:137 -msgid "Allows filling in of string and integer fields with your values." +#: ../settings/security/ssl-certificates.rst:7 +msgid "" +"Zammad offers the possibility to upload custom certificates and custom " +"Certificate Authority (CA) certificates. This can be useful if you want to " +"connect Zammad the secure way to other systems which are using custom " +"certificates." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:141 -msgid "fill in empty |ui|" +#: ../settings/security/ssl-certificates.rst:12 +msgid "" +"An example usecase might be: You have an internal LDAP server that is not " +"accessible from the internet, and you want a SSL-encrypted connection, using " +"a custom certificate." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:140 +#: ../settings/security/ssl-certificates.rst:19 msgid "" -"Allows filling in of string and integer fields with your values **if the " -"field is empty**." +"You should have an existing custom certificate file and/or a custom CA " +"certificate file, which you want to add to Zammad. As filetype ``.crt`` is " +"supported and the certificate format has to be PEM (Base64 ASCII)." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:144 -msgid "select |ui|" +#: ../settings/security/ssl-certificates.rst:25 +msgid "" +"When you import a custom CA certificate, all certificates generated with " +"this are trusted. This can be useful if you have more than one system/" +"certificate you want to connect to and the certificates are issued from the " +"same custom CA." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:144 -msgid "Select a specific value within a select, tree select or boolean field." -msgstr "" +#: ../settings/security/ssl-certificates.rst:31 +#, fuzzy +msgid "Add a Certificate" +msgstr "Sertifika Ekle" -#: ../system/core-workflows/how-do-they-work.rst:153 -msgid "auto select |ui|" +#: ../settings/security/ssl-certificates.rst:33 +msgid "" +"To add a custom certificate or a custom CA certificate, head over to the " +"Admin panel > Settings > Security > SSL Certificates. Here you can find a " +"\"Add SSL Certificate\" button. In the dialog you can either select a " +"certificate file or paste the content of the certificate:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:147 -msgid "Helps users with tree select and select fields:" +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate adding dialog" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:149 +#: ../settings/security/ssl-certificates.rst:43 msgid "" -"If the field has only one option available for selection and no value yet, " -"the value will be automatically set." +"After selecting a file or pasting the content of the certificate, click on " +"the \"Add\" button to finally upload it to Zammad. Then, the certificates " +"are immediately effective, no restart or similar required." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:152 +#: ../settings/security/ssl-certificates.rst:49 msgid "" -"This option only works if you have one value and doesn't work if there is " -"more than one option available." +"Please note that only single certificate files are supported. That means if " +"you want to import a certificate / CA certificate, it must contain **only " +"one** certificate." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:157 -msgid "set readonly |ui|" -msgstr "" +#: ../settings/security/ssl-certificates.rst:54 +#, fuzzy +msgid "Certificate Overview" +msgstr "Sertifika Ekle" -#: ../system/core-workflows/how-do-they-work.rst:156 +#: ../settings/security/ssl-certificates.rst:56 msgid "" -"Allows you to display an attribute as read only (which means no changes are " -"possible)." +"After you added a certificate, you can see a table with information for each " +"added certificate:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:161 -msgid "unset readonly |ui|" +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing table of added certificates" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:160 +#: ../settings/security/ssl-certificates.rst:64 msgid "" -"In case a workflow set the field in question to read only, you can undo this " -"with option above." +"Here you can download the certificate or delete it, if you don't need it " +"anymore." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:172 -msgid "Stop after match" -msgstr "" +#: ../settings/security/ssl-certificates.rst:68 +#, fuzzy +msgid "Deleting Certificates" +msgstr "Sertifika Ekle" -#: ../system/core-workflows/how-do-they-work.rst:174 +#: ../settings/security/ssl-certificates.rst:70 msgid "" -"Here you can decide if other workflows are executed after the current one." +"If you want to delete a specific certificate, you can do it by clicking on " +"the menu in the actions column and selecting delete:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:176 -msgid "" -"If set to ``no`` (default), further workflows will be executed if they match " -"the condition. In this case, it is possible that your actions from the " -"current workflow can be overwritten by another workflow." +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate deletion button" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:180 +#: ../settings/security/ssl-certificates.rst:79 +#, fuzzy +msgid "Downloading Certificates" +msgstr "Sertifika Ekle" + +#: ../settings/security/ssl-certificates.rst:81 msgid "" -"If set to ``yes``, no further worflows will be executed after the current " -"one." +"If you want to download your certificates, you can do this as well via " +"corresponding action buttons." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:184 -msgid "Priority" +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate download button" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:186 +#: ../settings/security/third-party.rst:13 +msgid "Login Providers" +msgstr "Giriş Sağlayıcılar" + +#: ../settings/security/third-party.rst:2 +msgid "Third-Party Applications" +msgstr "Üçüncü Parti Uygulamalar" + +#: ../settings/security/third-party.rst:4 msgid "" -"You can define the sequence, in which the workflows are executed. The " -"default value is ``500``." +"Third party authentication is a great way to help your users to login to " +"Zammad more easily. If the account is yet unknown, Zammad will create a new " +"user automatically, without the user needed to interact (e.g. type in his " +"name). Another big advantage of this feature is that your user doesn't need " +"to remember another password." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:189 +#: ../settings/security/third-party.rst:10 msgid "" -"The workflows are executed in ascending order by their priority. That means " -"lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." +"You can deactivate logging in via :ref:`security_password_login` if any of " +"the mentioned authentication providers are enabled in your instance." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:2 +#: ../settings/security/third-party.rst:27 +msgid "" +"We're currently missing documentation for the following login providers:" +msgstr "Şu anda aşağıdaki oturum açma sağlayıcıları için belgelerimiz yok:" + +#: ../settings/security/third-party.rst:29 +msgid "LinkedIn" +msgstr "LinkedIn" + +#: ../settings/security/third-party.rst:30 +msgid "Weibo" +msgstr "Weibo" + +#: ../settings/security/third-party.rst:35 #, fuzzy -msgid "Learn by Example" -msgstr "Örnek ile öğren" +msgid "Automatic Account Link on Initial Logon" +msgstr "İlk oturum açmada otomatik hesap bağlantısı" -#: ../system/core-workflows/learn-by-example.rst:4 +#: ../settings/security/third-party.rst:37 msgid "" -"This page provides some basic examples for Core Workflows. Of course you can " -"build much more complex workflows if needed." +"In general there's two possible options for Zammad on how to deal with " +"already known users as they try to authenticate against a third-party " +"application. By default, Zammad will not automatically link \"unknown\" " +"authentication providers to existing accounts." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:7 +#: ../settings/security/third-party.rst:42 msgid "" -"To learn about Core Workflows in detail, first go to :doc:`how-do-they-work`." +"This means that the user has to manually link authentication providers to " +"their accounts (for more about this :user-docs:`consult the user " +"documentation `)." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:10 -#, fuzzy -msgid "Group Based Examples" -msgstr "Örnek" +#: ../settings/security/third-party.rst:46 +msgid "" +"Sometimes this doesn't come in handy as this also means you'll receive error " +"messages about \"email address being in use already\" for (yet) unknown " +"third-party authentication methods." +msgstr "" -#: ../system/core-workflows/learn-by-example.rst:12 +#: ../settings/security/third-party.rst:50 msgid "" -"All following workflows have the same base configurations. The workflow may " -"not use them all." +"If you want to allow your users to always be able to log in, no matter what, " +"you may want to enable ``Automatic account link on initial logon``." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:15 +#: ../settings/security/third-party.rst:None #, fuzzy -msgid "Groups:" -msgstr "Gruplar" +msgid "" +"Screenshot highlighting the \"Automatic account link on initial logon\"\n" +"setting" +msgstr "İlk oturum açmada otomatik hesap bağlantısı" -#: ../system/core-workflows/learn-by-example.rst:20 +#: ../settings/security/third-party.rst:60 #, fuzzy -msgid "Attributes:" -msgstr "Bilet Nitelikleri" +msgid "Automatic Account Linking Notification" +msgstr "İlk oturum açmada otomatik hesap bağlantısı" -#: ../system/core-workflows/learn-by-example.rst:22 -msgid "Category (Single tree selection field, not mandatory, agents only)" +#: ../settings/security/third-party.rst:64 +msgid "" +"To improve security and your users awareness, you can enable Zammad to " +"notify your users when a new third-party application has been linked to " +"their account." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:23 +#: ../settings/security/third-party.rst:68 msgid "" -"Approved (Boolean field, not mandatory, not shown, ``false`` as default)" +"This notification is sent out once per third-party application. Zammad does " +"also mention the method used, e.g.: ``Microsoft``." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:24 -msgid "Operating System (Text field, not mandatory, not shown)" +#: ../settings/security/third-party.rst:71 +msgid "By default this setting is not active (set to ``no``)." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:25 -msgid "Software used (Single selection field, not mandatory, not shown)" +#: ../settings/security/third-party.rst:0 +msgid "" +"Screenshot showing sample notification mail after initial\n" +"third-party linking" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:68 -msgid "Group specific values and fields" +#: ../settings/security/third-party.rst:85 +msgid "" +"This notification is only sent if the account in question already exists. If " +"the login via the third-party also creates the missing account, the " +"notification will be skipped." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:28 -msgid "" -"This workflow set depends on the category field. It reduces the available " -"set of values based on the group selected." +#: ../settings/security/third-party.rst:89 +msgid "This means it only affects:" +msgstr "" + +#: ../settings/security/third-party.rst:91 +msgid "manual account linking within the third-party page of the users profile" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:33 -msgid "Workflow 2nd Level group" +#: ../settings/security/third-party.rst:92 +msgid "" +"logging into an existing local account by utilizing the *automatic account " +"link on initial logon* functionality" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:35 +#: ../settings/security/third-party.rst:None msgid "" -"This reduces the category options to ``2nd Level/*``, ``Internal/*`` and " -"``Others``. It also sets further required fields to mandatory and visible." +"Screenshot showing the \"automatic account linking notification\"\n" +"setting" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for 2nd level" +#: ../settings/security/third-party.rst:100 +msgid "No User Creation on Logon" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:43 -msgid "Workflow Support group" +#: ../settings/security/third-party.rst:102 +msgid "" +"By default, Zammad will create a new user account if the user logs in via a " +"third-party application and the account doesn't exist yet." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:45 +#: ../settings/security/third-party.rst:105 msgid "" -"This reduces the category options to ``Support/*``, ``Internal/*`` and " -"``Others``. It also sets further required fields to visible." +"If you want to prevent Zammad from creating new accounts on logon, you can " +"disable this feature by setting ``No user creation on logon`` to ``yes``." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for support" -msgstr "" +#: ../settings/security/third-party.rst:None +#, fuzzy +msgid "Screenshot showing the \"no user creation on logon\" setting" +msgstr "İlk oturum açmada otomatik hesap bağlantısı" -#: ../system/core-workflows/learn-by-example.rst:53 -msgid "Workflow Sales group" +#: ../settings/security/third-party/facebook.rst:4 +msgid "" +"It is possible to create a quick login for your helpdesk via Facebook To do " +"so, you need to follow these steps:" msgstr "" +"Facebook üzerinden yardım masanız için hızlı bir giriş oluşturmak mümkündür. " +"Bunu yapmak için şu adımları izlemeniz gerekir:" -#: ../system/core-workflows/learn-by-example.rst:55 +#: ../settings/security/third-party/facebook.rst:9 +#, fuzzy +msgid "Register Facebook App" +msgstr "Facebook uygulamasına kaydol" + +#: ../settings/security/third-party/facebook.rst:11 msgid "" -"This reduces the category options to ``Sales/*``, ``Internal/*`` and " -"``Others``." +"Visit [https://developers.facebook.com/apps/] and click on \"Add a new App\"" msgstr "" +"[https://developers.facebook.com/apps/] adresini ziyaret edin ve \"Yeni " +"Uygulama Ekle\"yi tıklayın" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for sales" +#: ../settings/security/third-party/facebook.rst:None +msgid "initial page" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:68 -#: ../system/integrations/slack.rst:88 -msgid "The Result" +#: ../settings/security/third-party/facebook.rst:17 +msgid "After that enter the app settings" +msgstr "Bundan sonra uygulama ayarlarını girin" + +#: ../settings/security/third-party/facebook.rst:None +msgid "Create App" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:63 -msgid "" -"This is what the agent would experience with the above workflows in place." +#: ../settings/security/third-party/facebook.rst:22 +msgid "Navigate to \"Settings\" and fill in this infromation" +msgstr "\"Ayarlar\"a gidin ve bu bilgileri doldurun" + +#: ../settings/security/third-party/facebook.rst:None +msgid "App Settings" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "" -"Workflow shows objects and limits options based on selections on the group" +#: ../settings/security/third-party/facebook.rst:27 +msgid "Navigate to app review and Check \"Make [appname] public?\"" msgstr "" +"Uygulama incelemesine gidin ve \"[uygulama adı] herkese açık hale getirilsin " +"mi?\" seçeneğini işaretleyin." -#: ../system/core-workflows/learn-by-example.rst:90 -msgid "Approval process" +#: ../settings/security/third-party/facebook.rst:None +msgid "App Review" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:71 +#: ../settings/security/third-party/facebook.rst:35 +#, fuzzy +msgid "Configure Zammad as Facebook App" +msgstr "Zammad'ı Facebook uygulaması olarak yapılandır" + +#: ../settings/security/third-party/facebook.rst:37 +#, fuzzy msgid "" -"In this case ``approved`` is visible to agents by default. For this " -"workflow, an additional role ``Approval person`` is required (no further " -"permissions)." +"Navigate to \"Admin -> Security -> Third Party Applications\" and enter the " +"App ID and the App Secret. You can find this Key in the Dashbard of your " +"Facebok app." msgstr "" +"\"Yönetici -> Güvenlik -> Üçüncü Taraf Uygulamaları\"na gidin ve Uygulama " +"Kimliğini ve Uygulama Sırrını girin. Bu Anahtarı Facebook uygulamanızın " +"Kontrol Panelinde bulabilirsiniz." -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that restricts an approval attribute to specific roles" +#: ../settings/security/third-party/facebook.rst:None +msgid "Zammad Configuration" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:81 +#: ../settings/security/third-party/facebook.rst:44 +#: ../settings/security/third-party/github.rst:43 +#: ../settings/security/third-party/gitlab.rst:46 msgid "" -"This workflow may work best in combination with a :doc:`trigger ` but technically, this is not required." +"Now you can link accounts via \"Avatar -> Profile -> Link Accounts\" or " +"login via Zammad login page." msgstr "" +"Artık \"Avatar -> Profil -> Hesapları Bağla\" yoluyla hesapları bağlayabilir " +"veya Zammad giriş sayfası üzerinden giriş yapabilirsiniz." -#: ../system/core-workflows/learn-by-example.rst:84 +#: ../settings/security/third-party/github.rst:2 +#: ../system/integrations/github.rst:2 +msgid "GitHub" +msgstr "GitHub" + +#: ../settings/security/third-party/github.rst:4 msgid "" -"Select fields may be a better approach because they allow more values than " -"just a simple ``true`` or ``false``." +"It is possible to create a quick login for your helpdesk via GitHub. To " +"activate the quick login you need to enable OAuth for GitHub." msgstr "" +"GitHub üzerinden yardım masanız için hızlı giriş oluşturmanız mümkündür. " +"Hızlı oturum açmayı etkinleştirmek için GitHub için OAuth'u etkinleştirmeniz " +"gerekir." -#: ../system/core-workflows/learn-by-example.rst:0 +#: ../settings/security/third-party/github.rst:8 +#, fuzzy +msgid "Register GitHub App" +msgstr "GitHub uygulamasına kaydol" + +#: ../settings/security/third-party/github.rst:10 msgid "" -"Workflow fixes possible values of \"Approved ?\" to a specific selection " -"depending on the users role" +"Visit https://www.github.com/settings/applications/new and enter the app " +"settings. As callback URL enter \"https://zammad_host/auth/github/callback\" " +"where zammad_host has to be replaced with your Zammad FQDN" msgstr "" +"https://www.github.com/settings/applications/new adresini ziyaret edin ve " +"uygulama ayarlarını girin. Geri arama URL'si olarak \"https://zammad_host/" +"auth/github/callback\" girin, burada zammad_host'un Zammad FQDN'nizle " +"değiştirilmesi gerekir" -#: ../system/core-workflows/learn-by-example.rst:103 -msgid "State dependent mandatory fields" +#: ../settings/security/third-party/github.rst:None +msgid "Register OAuth app on www.github.com" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:93 +#: ../settings/security/third-party/github.rst:19 +#, fuzzy +msgid "Configure Zammad as GitHub App" +msgstr "Zammad'ı GitHub uygulaması olarak yapılandır" + +#: ../settings/security/third-party/github.rst:21 msgid "" -"This workflow sets ``Category`` to mandatory if the agent wants to set the " -"states ``closed`` or ``pending close`` to enforce categorization." +"Enter the \"APP ID\" and the \"APP SECRET\" from the GitHub OAUTH " +"Applications Dashboard" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that sets fields to mandatory on specific states" +#: ../settings/security/third-party/github.rst:None +msgid "GitHub config in Zammad admin interface" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 +#: ../settings/security/third-party/github.rst:28 msgid "" -"Workflow sets category field to mandatory upon choosing closed or pending " -"close as state" +"After you configured the GitHub credentials and activated the login method, " +"you should see a new icon on the login page." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:106 -msgid "Manual Ticket Handover Process" +#: ../settings/security/third-party/github.rst:None +msgid "GitHub logo on login page" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:108 -msgid "This example covers the handover of a ticket from one agent to another:" +#: ../settings/security/third-party/github.rst:34 +msgid "" +"If you click on the icon you will be redirected to GitHub and see something " +"similar to this:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:110 -msgid "" -"When the ticket owner is modified, a new text field (\"Handover\") shows up " -"for a comment" +#: ../settings/security/third-party/github.rst:None +msgid "GitHub oauth page" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:112 +#: ../settings/security/third-party/github.rst:40 +#: ../settings/security/third-party/gitlab.rst:42 msgid "" -"This may only be visible when the owner is changed, therefore it has to be " -"hidden in general" +"When you grant the access you will be redirected to your Zammad instance and " +"logged in as a customer." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:114 -msgid "The input in this handover text field is mandatory" -msgstr "" +#: ../settings/security/third-party/gitlab.rst:2 +msgid "Gitlab" +msgstr "Gitlab" -#: ../system/core-workflows/learn-by-example.rst:115 +#: ../settings/security/third-party/gitlab.rst:4 msgid "" -"After submitting changes, the value of the handover field must be added as " -"an note to the ticket (via trigger)" +"It is possible to create a quick login for your helpdesk via Gitlab. To " +"activate the quick login you need to enable OAuth for Gitlab." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:121 -msgid "Hiding handover field" -msgstr "" +#: ../settings/security/third-party/gitlab.rst:8 +#, fuzzy +msgid "Register Gitlab App" +msgstr "Gitlab uygulamasına kaydol" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Hiding the handover field in core workflows" +#: ../settings/security/third-party/gitlab.rst:10 +msgid "To register an app in Gitlab open your profile and select applications." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:126 -msgid "Showing handover field and setting it to mandatory" +#: ../settings/security/third-party/gitlab.rst:12 +#, fuzzy +msgid "" +"As callback URL enter \"https://zammad-fqdn/auth/gitlab/callback\" where " +"zammad-fqdn has to be replaced with your Zammad FQDN" msgstr "" +"https://www.github.com/settings/applications/new adresini ziyaret edin ve " +"uygulama ayarlarını girin. Geri arama URL'si olarak \"https://zammad_host/" +"auth/github/callback\" girin, burada zammad_host'un Zammad FQDN'nizle " +"değiştirilmesi gerekir" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Showing the handover field and set it as mandatory" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Register OAuth app on gitlab instance" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:131 -msgid "Trigger writing handover input to a new article" +#: ../settings/security/third-party/gitlab.rst:18 +msgid "Just select *read_user* under scopes as in the screenshot and save it." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Write handover content to a new article" -msgstr "" +#: ../settings/security/third-party/gitlab.rst:21 +#, fuzzy +msgid "Configure Zammad as Gitlab App" +msgstr "Zammad'ı Gitlab uygulaması olarak yapılandır" -#: ../system/core-workflows/learn-by-example.rst:133 +#: ../settings/security/third-party/gitlab.rst:23 msgid "" -"As a result, the ticket includes an article of the type note which includes " -"the predefined text and the handover comment." +"Enter the \"APP ID\" and the \"APP SECRET\" from the Gitlab OAUTH " +"Applications Dashboard and your Gitlab-URL in the \"SITE\" field." msgstr "" -#: ../system/core-workflows/limitations.rst:6 -msgid "Core Workflows do not replace Triggers" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab config in Zammad admin interface" msgstr "" -#: ../system/core-workflows/limitations.rst:5 +#: ../settings/security/third-party/gitlab.rst:30 msgid "" -"Workflows manipulate the behavior of fields. However, they do not set values " -"in fields because of actions." +"After you configured the Gitlab credentials and activated the login method, " +"you should see a new icon on the login page." msgstr "" -#: ../system/core-workflows/limitations.rst:16 -msgid "API calls are only partly affected" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab logo on login page" msgstr "" -#: ../system/core-workflows/limitations.rst:9 +#: ../settings/security/third-party/gitlab.rst:36 msgid "" -"Some options affect UI only and thus do not restrict responses and calls." +"If you click on the icon you will be redirected to Gitlab and see something " +"similar to this:" msgstr "" -#: ../system/core-workflows/limitations.rst:11 -msgid "This affects the following actions:" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab oauth page" msgstr "" -#: ../system/core-workflows/limitations.rst:13 -msgid "select" +#: ../settings/security/third-party/google.rst:4 +msgid "" +"With some easy and fast steps, you can enable Zammad to authenticate your " +"users via Google." msgstr "" -#: ../system/core-workflows/limitations.rst:14 -msgid "auto select" +#: ../settings/security/third-party/google.rst:8 +#, fuzzy +msgid "Register a Google App" +msgstr "Bir Google uygulamasına kaydol" + +#: ../settings/security/third-party/google.rst:10 +msgid "" +"First of all, we need to create a new project - you can skip this step if " +"you already have one." msgstr "" -#: ../system/core-workflows/limitations.rst:15 -msgid "show" +#: ../settings/security/third-party/google.rst:15 +msgid "" +"Use this link to create a new project: https://console.cloud.google.com/" +"projectcreate" msgstr "" -#: ../system/core-workflows/limitations.rst:16 -msgid "hide" +#: ../settings/security/third-party/google.rst:18 +msgid "" +"Now expand the menu, expand \"APIs & Services\" and select \"Credentials\". " +"Go to the tab \"OAuth consent screen\" first and ensure to fill in the " +"requested information - without doing so you can't create credentials!" msgstr "" -#: ../system/core-workflows/limitations.rst:25 -msgid "Some fields stay unavailable to customers" +#: ../settings/security/third-party/google.rst:None +msgid "Creating a consent screen" msgstr "" -#: ../system/core-workflows/limitations.rst:19 +#: ../settings/security/third-party/google.rst:25 msgid "" -"For technical and security reasons, some default fields (the pale ones you " -"can't edit) stay unavailable for display and usage on customer permissions." +"After filling in and saving the consent screen information, you can go to " +"the \"Credentials\" tab and create new \"OAuth client ID\"-Credentials." msgstr "" -#: ../system/core-workflows/limitations.rst:23 +#: ../settings/security/third-party/google.rst:28 msgid "" -"If you require your customers to change e.g. priorities, please consider " -"using workarounds via :doc:`/system/objects` and :doc:`/manage/trigger`." +"Fill in the necessary information as follows and replace ``zammad_host`` " +"with your FQDN:" msgstr "" -#: ../system/core-workflows/limitations.rst:29 -msgid "Ticket title changes not supported in edit mask" +#: ../settings/security/third-party/google.rst:31 +#, fuzzy +msgid "**Application type** ``[x] Web application``" +msgstr "**Uygulama türü** ``[x] Web uygulaması``" + +#: ../settings/security/third-party/google.rst:34 +msgid "**Authorized JavaScript origins** ``https://zammad_host/``" msgstr "" -#: ../system/core-workflows/limitations.rst:28 +#: ../settings/security/third-party/google.rst:37 msgid "" -"It is currently not possible to perform changes of the ticket title in the " -"edit mask (e.g. renaming, set to read-only)." +"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" +"callback``" msgstr "" -#: ../system/core-workflows/limitations.rst:37 -msgid "What is out of scope of Core Workflows?" +#: ../settings/security/third-party/google.rst:None +msgid "Adding a new OAuth client ID" msgstr "" -#: ../system/core-workflows/limitations.rst:32 +#: ../settings/security/third-party/google.rst:43 msgid "" -"There are some things that would count as workflow but are either done via :" -"doc:`/manage/trigger` or :doc:`/manage/scheduler`." -msgstr "" - -#: ../system/core-workflows/limitations.rst:35 -msgid "Such as (but not limited to):" +"After creating the credentials, go to your Zammad installation and navigate " +"to \"Admin > Security > Third Party Applications\" > Google. Enter your " +"Client ID and Client secret here." msgstr "" -#: ../system/core-workflows/limitations.rst:37 -msgid "up- or downgrade permissions of users" +#: ../settings/security/third-party/google.rst:None +msgid "Zammad" msgstr "" -#: ../system/core-workflows/limitations.rst:38 -msgid "affecting article creation or listing" -msgstr "" +#: ../settings/security/third-party/google.rst:50 +msgid "After submitting, the login via Google can be used." +msgstr "Gönderdikten sonra, Google ile giriş kullanılabilir." -#: ../system/data-privacy.rst:2 -msgid "Data Privacy" -msgstr "Veri Gizliliği" +#: ../settings/security/third-party/microsoft.rst:2 +#, fuzzy +msgid "Microsoft" +msgstr "Microsoft 365" -#: ../system/data-privacy.rst:4 +#: ../settings/security/third-party/microsoft.rst:4 msgid "" -"For compliance with GDPR and other data privacy laws, you may wish to " -"**permanently delete users from the system**, along with **all of their " -"associated tickets**." +"Zammad's Microsoft connection allows your users with Microsoft accounts to " +"login. This works for Azure users as well and can be an alternative to :doc:" +"`/system/integrations/ldap/index`." msgstr "" -#: ../system/data-privacy.rst:8 +#: ../settings/security/third-party/microsoft.rst:10 msgid "" -"You can create manual deletion tasks or even automated deletion tasks for " -"tickets and users based on custom conditions via :doc:`scheduler `!" +"This documentation part does not cover our :doc:`📧 Microsoft 365 email " +"channel `." msgstr "" -#: ../system/data-privacy.rst:12 +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screenshot showing Microsoft login button on Zammad login screen." +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:30 +#: ../settings/security/third-party/microsoft.rst:53 +msgid "Supported account types:" +msgstr "Desteklenen hesap türleri:" + +#: ../settings/security/third-party/microsoft.rst:22 msgid "" -"Access to this panel requires ``admin.data_privacy`` permissions (introduced " -"in Zammad 3.5)." +"Please note that Zammad only supports these account types (App dependent):" msgstr "" -#: ../system/data-privacy.rst:15 +#: ../settings/security/third-party/microsoft.rst:35 +msgid "Avatars of signing in users:" +msgstr "" + +#: ../settings/security/third-party/microsoft.rst:33 msgid "" -"On older systems that have not been updated yet, customers can also be :docs:" -"`deleted via the Zammad console `." +"Zammad currently ignores user avatars. If the user is registered with e.g. " +"Gravatar, Zammad will fetch the avatar from there if enabled. See :doc:" +"`Zammad Image Service ` for more." msgstr "" -#: ../system/data-privacy.rst:22 -msgid "User deletion dialog in the Data Privacy panel" +#: ../settings/security/third-party/microsoft.rst:38 +msgid "Step 1 - Register a Microsoft App for Zammad" msgstr "" -#: ../system/data-privacy.rst:22 +#: ../settings/security/third-party/microsoft.rst:40 msgid "" -"The user deletion dialog lists some of the tickets that will be removed from " -"the system along with the user." +"Login to the `Microsoft Azure Portal `_ and " +"navigate to App registrations to create a new app. Provide the requested " +"information as follows and register your app." msgstr "" -#: ../system/data-privacy.rst:27 -#, fuzzy -msgid "Deleting Users via GUI" -msgstr "Kullanıcıları Silmek" +#: ../settings/security/third-party/microsoft.rst:46 +msgid "Name:" +msgstr "Ad:" -#: ../system/data-privacy.rst:29 -#, fuzzy -msgid "🔥 **All deletions are FINAL!**" -msgstr "💣 **Tüm silmeler TAMAMLANDI!**" +#: ../settings/security/third-party/microsoft.rst:45 +msgid "" +"Any meaningful name fitting, this name will be displayed to users trying to " +"authenticate with this app." +msgstr "" -#: ../system/data-privacy.rst:31 -msgid "Once you click “Delete”, the action cannot be canceled or undone." +#: ../settings/security/third-party/microsoft.rst:49 +msgid "Choose one of the above mentioned account types (see Limitations)." msgstr "" -#: ../system/data-privacy.rst:33 +#: ../settings/security/third-party/microsoft.rst:51 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." +"The correct account type depends on your use case. If you want to use the " +"authentication internal only, choose the first option. If you're unsure, use " +"the \"Help me choose...\" link." msgstr "" -#: ../system/data-privacy.rst:36 -msgid "**The following records cannot be deleted:**" +#: ../settings/security/third-party/microsoft.rst:58 +msgid "Redirect URI (optional):" msgstr "" -#: ../system/data-privacy.rst:38 -msgid "your own account" -msgstr "kendi hesabınız" - -#: ../system/data-privacy.rst:39 -msgid "the system's last remaining administrator account" +#: ../settings/security/third-party/microsoft.rst:56 +msgid "" +"Select web and provide your callback URL. The callback URL looks like this: " +"``https://zammad.domain.tld/auth/microsoft_office365/callback``" msgstr "" -#: ../system/data-privacy.rst:42 -msgid "Step 1: Find a User / Confirm Deletion" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to register a Microsoft app" msgstr "" -#: ../system/data-privacy.rst:44 -msgid "There are three ways to access the user deletion dialog:" +#: ../settings/security/third-party/microsoft.rst:71 +msgid "Within **API permissions** add the following permissions:" msgstr "" -#: ../system/data-privacy.rst:51 -#, fuzzy -msgid "**from the user's profile**" -msgstr "**kullanıcının profilinden**" +#: ../settings/security/third-party/microsoft.rst:69 +msgid "``User.Read``" +msgstr "``User.Read``" -#: ../system/data-privacy.rst:0 -msgid "Accessing the user deletion dialog in a user profile" +#: ../settings/security/third-party/microsoft.rst:71 +msgid "Contacts" +msgstr "İletişim" + +#: ../settings/security/third-party/microsoft.rst:71 +msgid "``Contacts.Read``" +msgstr "``Contacts.Read``" + +#: ../settings/security/third-party/microsoft.rst:73 +msgid "" +"You can find these permissions within *Microsoft Graph → Delegated " +"permissions*." msgstr "" -#: ../system/data-privacy.rst:51 -msgid "Click **Action > Delete**." +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to add required API permissions" msgstr "" -#: ../system/data-privacy.rst:58 -msgid "**in the “Manage > Users” Admin Panel**" +#: ../settings/security/third-party/microsoft.rst:80 +msgid "" +"Within **Certificates & secrets** create a new client secret. Note down the " +"returned secret **value** for later. **Do not** use the secret ID!" msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Accessing the user deletion dialog under “Users” in the Admin Panel" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to create a new app secret" msgstr "" -#: ../system/data-privacy.rst:58 -msgid "Use the **⋮ Actions** menu for the target user." +#: ../settings/security/third-party/microsoft.rst:88 +msgid "" +"From **Overview** copy your apps *Application (client) ID*. If you're using " +"a single tenant app, please also copy *Directory (tenant) ID*. You now have " +"all required information for Zammad." msgstr "" -#: ../system/data-privacy.rst:66 ../system/data-privacy.rst:104 -msgid "**in the “System > Data Privacy” Admin Panel**" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to retreive application client and tenant IDs" msgstr "" -#: ../system/data-privacy.rst:0 -msgid "" -"Accessing the user deletion dialog under “Data Privacy” in the Admin Panel" +#: ../settings/security/third-party/microsoft.rst:98 +msgid "Step 2 - Add App Credentials to Zammad" msgstr "" -#: ../system/data-privacy.rst:65 +#: ../settings/security/third-party/microsoft.rst:100 msgid "" -"Use the **New Deletion Task** button. Search for users by name or email " -"address." +"Navigate to Security > Third-party Applications (Tab) within Zammad's admin " +"settings. Scroll down to the section *Authentication via Microsoft* and fill " +"in the required information." msgstr "" -#: ../system/data-privacy.rst:79 -#, fuzzy -msgid "**Delete organizations**" -msgstr "🏢 Organizasyon" +#: ../settings/security/third-party/microsoft.rst:105 +msgid "App ID:" +msgstr "" -#: ../system/data-privacy.rst:69 -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:" +#: ../settings/security/third-party/microsoft.rst:105 +msgid "This is your *Application (client) ID*." msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Deleting an organization via the user deletion dialog" +#: ../settings/security/third-party/microsoft.rst:108 +msgid "App secret:" msgstr "" -#: ../system/data-privacy.rst:78 -msgid "" -"If this option does not appear, make sure there are no pending deletion " -"tasks for other customers from this organization." +#: ../settings/security/third-party/microsoft.rst:108 +msgid "This is your *client secret* (value)." msgstr "" -#: ../system/data-privacy.rst:82 -msgid "Step 2: Monitor Deletion Job Status" +#: ../settings/security/third-party/microsoft.rst:113 +msgid "App Tenant ID:" msgstr "" -#: ../system/data-privacy.rst:84 +#: ../settings/security/third-party/microsoft.rst:111 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:" +"**optional** only required for apps that use account type *Accounts in this " +"organizational directory only (Default Directory only - Single tenant).*" msgstr "" -#: ../system/data-privacy.rst:98 -msgid "**in the Activity Stream**" +#: ../settings/security/third-party/microsoft.rst:115 +msgid "" +"Apply your settings by pressing submit and activate *Authentication via " +"Microsoft*." msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Activity Stream showing data privacy tasks" +#: ../settings/security/third-party/microsoft.rst:None +msgid "" +"Screencast showing how to add app credentials and activating the\n" +"authentication method" msgstr "" -#: ../system/data-privacy.rst:94 +#: ../settings/security/third-party/saml.rst:2 +msgid "SAML" +msgstr "SAML" + +#: ../settings/security/third-party/saml.rst:4 msgid "" -"For each deleted user, the Activity Stream will be updated twice—once when " -"the task is created, and once when it's complete." +"Connect your SAML (Security Assertion Markup Language) identity provider as " +"a single sign-on (SSO) method." msgstr "" -#: ../system/data-privacy.rst:97 +#: ../settings/security/third-party/saml.rst:7 msgid "" -"These notifications are only visible to users with ``admin.data_privacy`` " -"permissions." +"SAML is an open standard for SSO authentication (among other things). Sign-" +"ins are shared across multiple **service providers** and managed by a " +"central **identity provider** (IdP)." msgstr "" -#: ../system/data-privacy.rst:0 +#: ../settings/security/third-party/saml.rst:11 msgid "" -"The task list within Data Privacy shows removals being in progress and " -"completed." +"In this case, the service provider is Zammad, and the IdP is a software " +"service that you either host or subscribe to (*e.g.,* `Keycloak `_, `Redhat SSO Server `_, `ADFS `_, or `Okta `_)." msgstr "" -#: ../system/data-privacy.rst:107 -msgid "Frequently Asked Questions" -msgstr "Sıkça Sorulan Sorular" - -#: ../system/data-privacy.rst:121 -msgid "What happens if I receive an email from a deleted customer?" +#: ../settings/security/third-party/saml.rst:18 +msgid "" +"This guide assumes you are already using SAML within your organization (i." +"e., that your IdP is fully set up)." msgstr "" -#: ../system/data-privacy.rst:110 +#: ../settings/security/third-party/saml.rst:21 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." +"Please note: Our instructions are based on connecting Zammad with Keycloak." msgstr "" -#: ../system/data-privacy.rst:115 -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**." +#: ../settings/security/third-party/saml.rst:25 +msgid "Step 1: Configure Your IdP" msgstr "" -#: ../system/data-privacy.rst:130 -msgid "What about user information stored in internal notes or other messages?" +#: ../settings/security/third-party/saml.rst:28 +msgid "Add Zammad as a Client/App" msgstr "" -#: ../system/data-privacy.rst:124 +#: ../settings/security/third-party/saml.rst:30 msgid "" -"The deletion process removes **user accounts and associated tickets only**." +"Import Zammad into your IdP using the XML configuration found at ``https://" +"your.zammad.domain/auth/saml/metadata``." msgstr "" -#: ../system/data-privacy.rst:126 +#: ../settings/security/third-party/saml.rst:33 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." +"If your IdP doesn't support XML import, you will have to configure Zammad as " +"a new client/app manually using the above XML metadata file for reference." msgstr "" -#: ../system/data-privacy.rst:137 -msgid "I deleted an user and can still see a message they sent!" +#: ../settings/security/third-party/saml.rst:36 +msgid "For instance, when you see this tag:" msgstr "" -#: ../system/data-privacy.rst:133 +#: ../settings/security/third-party/saml.rst:42 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." +"Set the **Assertion Consumer Service Binding URL** (sometimes also listed as " +"**Valid Redirect URIs**) to ``http://your.zammad.domain/auth/saml/callback``." msgstr "" -#: ../system/data-privacy.rst:141 -msgid "I removed a customer, now my reporting is off!" +#: ../settings/security/third-party/saml.rst:47 +msgid "Set Up User Attribute Mapping" msgstr "" -#: ../system/data-privacy.rst:140 +#: ../settings/security/third-party/saml.rst:49 msgid "" -"When removing users and their tickets, all references are removed. This also " -"affects e.g. Reporting - these information are lost." +"Zammad requests the following user attributes (or “properties”) from the IdP:" msgstr "" -#: ../system/data-privacy.rst:145 -msgid "How long does Zammad store created tasks?" -msgstr "" +#: ../settings/security/third-party/saml.rst:51 +msgid "Email address (``email``)" +msgstr "E-posta adresi (``email``)" -#: ../system/data-privacy.rst:144 +#: ../settings/security/third-party/saml.rst:52 +msgid "Full name (``name``)" +msgstr "Tam isim (``name``)" + +#: ../settings/security/third-party/saml.rst:53 +msgid "Given name (``first_name``)" +msgstr "Verilen isim (``first_name``)" + +#: ../settings/security/third-party/saml.rst:54 +msgid "Family name (``last_name``)" +msgstr "Aile ismi (``last_name``)" + +#: ../settings/security/third-party/saml.rst:56 msgid "" -"Please see the on-premise data section of the :docs:`data privacy ` chapter." +"You may need to set up “mappers” (or “mappings”) to tell your IdP how user " +"attributes in SAML correspond to those in Zammad. For a more detailed " +"breakdown, refer to the XML metadata file referenced in the previous section." msgstr "" -#: ../system/data-privacy.rst:150 -msgid "What about re-assigned tickets? I want to delete them, too." +#: ../settings/security/third-party/saml.rst:62 +msgid "Per-IdP Instructions" msgstr "" -#: ../system/data-privacy.rst:148 -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." +#: ../settings/security/third-party/saml.rst:102 +msgid "Keycloak" msgstr "" -#: ../system/data-privacy.rst:154 -msgid "Why are there so many deletion task entries, I didn't create them!" +#: ../settings/security/third-party/saml.rst:65 +msgid "" +"**To add Zammad as a client,** save the XML configuration to disk (``https://" +"your.zammad.domain/auth/saml/metadata``) and use **Clients > Clients list > " +"Import client** in the Keycloak admin panel." msgstr "" -#: ../system/data-privacy.rst:153 +#: ../settings/security/third-party/saml.rst:70 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." +"To help Zammad **match its own user accounts to Keycloak users**, create a " +"user attribute (or “property”) mapper. In **Clients list**, click on your " +"newly created Client ID, choose the tab **Client scopes** and click on the " +"link which refers to your Zammad instance. Choose **Add mapper > By " +"configuration > User Property** and create a mapper with the following " +"entries:" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:2 -msgid "Admin Panel Reference" -msgstr "Yönetici Paneli Tercihleri" +#: ../settings/security/third-party/saml.rst:78 +msgid "**Name**" +msgstr "**Adı**" -#: ../system/integrations/checkmk/admin-panel-reference.rst:None -msgid "Screenshot of Checkmk settings overview" +#: ../settings/security/third-party/saml.rst:80 +msgid "**Mapper Type**" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:12 -msgid "" -"Which :doc:`group ` should Checkmk tickets be assigned " -"to as a default (*i.e.,* when none is specified)?" +#: ../settings/security/third-party/saml.rst:81 +#, fuzzy +msgid "``User Property``" +msgstr "``User-Agent``" + +#: ../settings/security/third-party/saml.rst:82 +msgid "**Property**" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:15 -msgid "(Applies to :ref:`API alerts ` only.)" +#: ../settings/security/third-party/saml.rst:83 +#, fuzzy +msgid "``emailAddress``" +msgstr "epostaAdresi" + +#: ../settings/security/third-party/saml.rst:84 +msgid "**SAML Attribute Name**" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:21 -msgid "Auto close" +#: ../settings/security/third-party/saml.rst:86 +msgid "**SAML Attribute NameFormat**" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:18 +#: ../settings/security/third-party/saml.rst:87 +msgid "``basic``" +msgstr "" + +#: ../settings/security/third-party/saml.rst:89 msgid "" -"Should Zammad automatically close tickets if a service has recovered on its " -"own?" +"In the example above, we're telling Zammad that whenever it receives a SAML " +"login request, it should take the ``email`` property from Keycloak, look for " +"a Zammad user with the same ``email`` attribute, and create a new session " +"for that user." +msgstr "" + +#: ../settings/security/third-party/saml.rst:95 +msgid "" +"If your Keycloak users' email addresses are stored on another property (*e." +"g.,* ``username``), adjust accordingly." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:21 -msgid "(Agents will receive notifications for such closures as appropriate.)" +#: ../settings/security/third-party/saml.rst:98 +msgid "" +"Back in **Settings**, enter the Client ID (``https://your.zammad.domain/auth/" +"saml/metadata``) in the field **Master SAML Processing URL**." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:30 -msgid "Auto-close state" +#: ../settings/security/third-party/saml.rst:101 +msgid "You also need to enable **Sign assertions**." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:24 -msgid "What ticket state should be applied when “auto-closing” a ticket?" +#: ../settings/security/third-party/saml.rst:105 +msgid "Step 2: Configure Zammad" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:26 +#: ../settings/security/third-party/saml.rst:107 msgid "" -"You can choose from the seven built-in ticket states. If these states aren't " -"enough for you, you can :ref:`define a new ticket state ` for this purpose as well. This can be useful for tracking " -"tickets with :doc:`reports `, for example." +"Enable SAML and enter your IdP's details in the Admin Panel under **Settings " +"> Security > Third Party Applications > Authentication via SAML**:" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:35 -#: ../system/integrations/cti/includes/recent-logs.include.rst:2 -#: ../system/integrations/ldap/index.rst:74 -#: ../system/integrations/pgp/index.rst:106 -msgid "Recent Logs" -msgstr "En Son Kayıtlar" +#: ../settings/security/third-party/saml.rst:None +#, fuzzy +msgid "Example configuration of SAML part 1" +msgstr "Makale > Görünürlük" -#: ../system/integrations/checkmk/admin-panel-reference.rst:None -msgid "Screenshot of Checkmk \"Recent Logs\" section" -msgstr "" +#: ../settings/security/third-party/saml.rst:119 +#, fuzzy +msgid "Display name" +msgstr "Görünen Ad" -#: ../system/integrations/checkmk/admin-panel-reference.rst:41 +#: ../settings/security/third-party/saml.rst:116 msgid "" -"If you're having trouble getting Zammad and Checkmk to play nicely together, " -"this section can help you troubleshoot." +"Allows you to define a custom button name for SAML. This helps your users to " +"understand better what the button on the login page does." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:44 -msgid "" -"It contains a record of the fifty most recent transactions that Zammad knows " -"about, including each one's request/response details and return status." +#: ../settings/security/third-party/saml.rst:119 +msgid "Defaults to ``SAML``." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:2 -msgid "API Reference" -msgstr "API Referansı" +#: ../settings/security/third-party/saml.rst:123 +msgid "IDP SSO target URL" +msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:4 +#: ../settings/security/third-party/saml.rst:122 msgid "" -"For most users, :ref:`the sample scripts from the Setup Guide ` will do the job just fine. But if you want more fine-grained control" -"—for instance, to create high- and low-priority tickets for different types " -"of system events—then you'll have to customize the data those scripts send " -"to Zammad." +"This is the target URL Zammad shall redirect to when the user presses the " +"SAML button. For Keycloak, this needs to look like https://your.domain/" +"realms/your-realm/protocol/saml" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:15 +#: ../settings/security/third-party/saml.rst:127 +msgid "IDP single logout target URL" +msgstr "" + +#: ../settings/security/third-party/saml.rst:126 msgid "" -"This custom script will automatically set all tickets it creates to **high " -"priority** and **assign them to charlie@chrispresso.com**." +"This is the URL to which the single logout request and response should be " +"sent." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:32 +#: ../settings/security/third-party/saml.rst:131 #, fuzzy -msgid "How Does it Work?" -msgstr "Nasıl çalışır?" +msgid "IDP certificate" +msgstr "Sertifika Ekle" -#: ../system/integrations/checkmk/api-reference.rst:34 +#: ../settings/security/third-party/saml.rst:130 msgid "" -"There are two kinds of data you can pass to the API, both in the form of key-" -"value pairs:" +"The public certificate of your IDP for Zammad to verify during the callback " +"phase." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:44 -msgid "Checkmk parameters" -msgstr "Checkmk parametreleri" +#: ../settings/security/third-party/saml.rst:145 +#, fuzzy +msgid "IDP certificate fingerprint" +msgstr "Sertifika Ekle" -#: ../system/integrations/checkmk/api-reference.rst:38 +#: ../settings/security/third-party/saml.rst:134 msgid "" -"are required, and make up the **contents** of the resulting tickets/" -"articles. They also determine whether an event creates a new ticket or " -"updates/closes an existing one." +"The fingerprint of your IDPs public certificate to verify during callback " +"phase." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:42 -msgid "" -"These are the only values used in the sample scripts. **Use them as-is**; " -"technically, they can be customized, but it's hard to imagine a good reason " -"for it." +#: ../settings/security/third-party/saml.rst:137 +msgid "🔏 **For the IdP certificate / certificate fingerprint:**" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:52 -msgid "Ticket attributes" -msgstr "Bilet nitelikleri" - -#: ../system/integrations/checkmk/api-reference.rst:47 +#: ../settings/security/third-party/saml.rst:139 msgid "" -"are optional, and can be used to **adjust settings** on newly created " -"tickets (*e.g.,* set the owner, group, priority, or state)." +"Provide **only one or the other**—do not provide both! (Between the two, we " +"recommend the signing certificate itself: fingerprints use SHA-1, which `has " +"been broken for a while now `_.)" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:50 +#: ../settings/security/third-party/saml.rst:144 msgid "" -"If you want to customize your Checkmk alert script, do it with these. Simply " -"add an extra “form” option for each one (``-F \"key=value\"``) to your " -"script's ``curl`` command line, as in the example above." +"**Keycloak users:** Find your certificate in the Keycloak admin panel under " +"**Realm Settings > Keys > Algorithm: RS256 > Certificate**." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:54 -msgid "💡 **It's just an API endpoint!**" +#: ../settings/security/third-party/saml.rst:151 +msgid "Name identifier format" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:56 +#: ../settings/security/third-party/saml.rst:148 msgid "" -"When using Checkmk integration, messages need to be formatted in a certain " -"way, but that *doesn't mean the messages actually have to come from Checkmk*." +"This is the unique identifiers field type. Usually it should be ``urn:oasis:" +"names:tc:SAML:1.1:nameid-format:emailAddress``." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:59 -msgid "" -"If you use another monitoring tool that's not officially supported by " -"Zammad, there's probably a way to make it work with your Checkmk callback " -"URL." +#: ../settings/security/third-party/saml.rst:151 +msgid "Zammad **expects an email address as unique identifier**!" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:63 -msgid "Checkmk Parameters" -msgstr "Checkmk Parametreleri" +#: ../settings/security/third-party/saml.rst:155 +#, fuzzy +msgid "UID attribute name" +msgstr "Bilet Nitelikleri" -#: ../system/integrations/checkmk/api-reference.rst:65 +#: ../settings/security/third-party/saml.rst:154 msgid "" -"When a notification is received, Zammad creates a new article containing the " -"details of the event that triggered it:" +"Here you can define an attribute that uniquely identifies the user. If " +"unset, the name identifier returned by the IDP is used." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:None -msgid "Checkmk article body" -msgstr "" +#: ../settings/security/third-party/saml.rst:None +#, fuzzy +msgid "Example configuration of SAML part 2" +msgstr "Makale > Görünürlük" -#: ../system/integrations/checkmk/api-reference.rst:72 +#: ../settings/security/third-party/saml.rst:163 msgid "" -"These details come from the fields listed below, which correspond to " -"parameters provided by Checkmk (``$NOTIFY_*``)." -msgstr "" - -#: ../system/integrations/checkmk/api-reference.rst:75 -msgid "**Required fields are marked with an asterisk (\\*).**" +"Decide if the certificate for the connection to the IdP service has to be " +"verified or not (default: ``yes``)." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:79 -msgid "event_id\\*" -msgstr "event_id\\*" +#: ../settings/security/third-party/saml.rst:169 +#, fuzzy +msgid "Signing & Encrypting" +msgstr "Şifreleme" -#: ../system/integrations/checkmk/api-reference.rst:78 +#: ../settings/security/third-party/saml.rst:169 msgid "" -"A unique ID for the system event. (``$NOTIFY_SERVICEPROBLEMID`` / " -"``$NOTIFY_HOSTPROBLEMID``)" +"Define if you want to sign, encrypt, do both or nothing for the requests." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:86 -msgid "host\\*" -msgstr "host\\*" +#: ../settings/security/third-party/saml.rst:179 +#, fuzzy +msgid "Certificate (PEM)" +msgstr "Sertifika Ekle" -#: ../system/integrations/checkmk/api-reference.rst:82 +#: ../settings/security/third-party/saml.rst:172 msgid "" -"The hostname of the system that the event originated from. " -"(``$NOTIFY_HOSTNAME``)" +"Paste the public certificate of your Zammad SAML client, if you want to " +"encrypt the requests." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:85 -msgid "" -"Used to determine if a new event belongs to an existing ticket. Also used in " -"the subject line of the resulting article (“ is ”)." +#: ../settings/security/third-party/saml.rst:175 +#, fuzzy +msgid "Make sure the certificate is:" +msgstr "Alıcının sertifikasının geçerli olduğundan emin misiniz?" + +#: ../settings/security/third-party/saml.rst:177 +msgid "already valid and not yet expired" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:96 -msgid "service" -msgstr "servis" +#: ../settings/security/third-party/saml.rst:178 +#, fuzzy +msgid "no CA certificate" +msgstr "Sertifika Ekle" -#: ../system/integrations/checkmk/api-reference.rst:89 +#: ../settings/security/third-party/saml.rst:179 +#, fuzzy +msgid "valid for signing and encrypting" +msgstr "Şifreleme" + +#: ../settings/security/third-party/saml.rst:185 +#, fuzzy +msgid "Private key (PEM)" +msgstr "Özel Anahtar Ekle" + +#: ../settings/security/third-party/saml.rst:182 msgid "" -"The name of the service that the event originated from. " -"(``$NOTIFY_SERVICEDESC``)" +"Paste the private key of your Zammad SAML client here, if you want to sign " +"the requests." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:92 -msgid "Used to determine if a new event belongs to an existing ticket." +#: ../settings/security/third-party/saml.rst:185 +msgid "Make sure the key is an RSA key with a length of at least 2048 bits." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:94 -#: ../system/integrations/checkmk/api-reference.rst:110 -msgid "Displayed as ``-`` when omitted." +#: ../settings/security/third-party/saml.rst:188 +#, fuzzy +msgid "Private key secret" +msgstr "Kişisel hesaplar" + +#: ../settings/security/third-party/saml.rst:188 +msgid "If your private key is secured with a secret, you can provide it here." +msgstr "" + +#: ../settings/security/third-party/saml.rst:192 +msgid "Your callback URL" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:104 -msgid "state\\*" -msgstr "state\\*" +#: ../settings/security/third-party/saml.rst:191 +msgid "" +"This URL is needed for your IdP configuration so it knows where to redirect " +"to after successful authentication." +msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:99 +#: ../settings/security/third-party/saml.rst:194 msgid "" -"The current state of the service or host in question. " -"(``$NOTIFY_SERVICESTATE`` / ``$NOTIFY_HOSTSTATE``)" +"After saving your input by clicking on the \"Submit\" button, Zammad " +"verifies the provided keys/certificates (e.g. if they are valid for signing/" +"encrypting and if they aren't expired)." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:102 +#: ../settings/security/third-party/saml.rst:199 msgid "" -"Used to detect when a ticket should be auto-closed (*i.e.,* on ``OK``/" -"``UP``). Also used in the subject line of the resulting article (“ is " -"”)." +"See :ref:`automatic account linking ` for details " +"on how to link existing Zammad accounts to IdP accounts." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:110 -msgid "text" -msgstr "metin" +#: ../settings/security/third-party/saml.rst:205 +#, fuzzy +msgid "Automatic account linking doesn't work" +msgstr "Otomatik hesap bağlantısı çalışmıyor" -#: ../system/integrations/checkmk/api-reference.rst:107 +#: ../settings/security/third-party/saml.rst:206 msgid "" -"The output of the process that triggered the event. " -"(``$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" +"Have you double-checked your IdP's user attribute mapping configuration?" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:121 +#: ../settings/security/third-party/twitter.rst:4 +#, fuzzy msgid "" -"The Object Manager attribute panel displays built-in and custom\n" -"attribute names." +"It is possible to create a quick login for your helpdesk via Twitter. To do " +"so, you need to follow these steps:" msgstr "" +"Facebook üzerinden yardım masanız için hızlı bir giriş oluşturmak mümkündür. " +"Bunu yapmak için şu adımları izlemeniz gerekir:" -#: ../system/integrations/checkmk/api-reference.rst:121 -msgid "Find a complete list of ticket attributes in the Object Manager." +#: ../settings/security/third-party/twitter.rst:8 +#, fuzzy +msgid "Register Twitter App" +msgstr "Twitter uygulamasına kaydol" + +#: ../settings/security/third-party/twitter.rst:10 +msgid "Go to https://dev.twitter.com/apps and login with your account." +msgstr "https://dev.twitter.com/apps adresine git ve hesabınla giriş yap." + +#: ../settings/security/third-party/twitter.rst:15 +msgid "Click on \"Create App\"" +msgstr "\"Uygulama Oluştur\"a tıkla" + +#: ../settings/security/third-party/twitter.rst:None +msgid "new app page" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:123 +#: ../settings/security/third-party/twitter.rst:20 msgid "" -"Ticket attributes are entirely optional, and can be used to customize the " -"tickets that Checkmk creates. (Note that these attributes will be ignored if " -"a new event belongs to an existing ticket.)" +"Enter app settings. As \"Callback URL\" you need to enter ``https://" +"zammad_host/api/v1/external_credentials/twitter/callback``. You need to " +"replace ``zammad_host`` with the domain of your Zammad system." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:128 +#: ../settings/security/third-party/twitter.rst:24 msgid "" -"Why would you want to do this? Maybe you have only one IT guy, and all " -"system monitoring issues should be automatically assigned to him. Or, maybe " -"you're creating multiple notification rules so that database outages take " -"higher priority than disk space warnings." +"After the app has been created, update the application icon and organization " +"attributes." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:135 -msgid "In most cases, you'll probably want to set one of the following:" +#: ../settings/security/third-party/twitter.rst:None +msgid "set permissions to receive and send direct messages" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:137 -msgid "group" -msgstr "grup" - -#: ../system/integrations/checkmk/api-reference.rst:139 -msgid "state" -msgstr "durum" +#: ../settings/security/third-party/twitter.rst:30 +#, fuzzy +msgid "" +"Next we need to set ``read, write and access direct messages`` permissions " +"for the app." +msgstr "*Okuma, yazma ve direkt mesajlara erişme*yi seç" -#: ../system/integrations/checkmk/api-reference.rst:140 -msgid "priority" -msgstr "öncelik" +#: ../settings/security/third-party/twitter.rst:None +msgid "click on Keys & Access Token, note them" +msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:142 +#: ../settings/security/third-party/twitter.rst:36 msgid "" -"but in practice, you can set almost any attribute, including :doc:`custom " -"ones you created through the Object Manager `." +"Go to \"Keys and Access Token\" tab and note the \"Consumer Key\" and " +"\"Consumer Secret\"." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:145 +#: ../settings/security/third-party/twitter.rst:40 #, fuzzy -msgid "Please note that the following attributes are **not customizable**:" -msgstr "Aşağıdaki ayarlardan şunları düzenleyebilirsin:" - -#: ../system/integrations/checkmk/api-reference.rst:147 -msgid "title" -msgstr "başlık" +msgid "Configure Zammad as Twitter App" +msgstr "Zammad'ı Twitter uygulaması olarak yapılandır" -#: ../system/integrations/checkmk/api-reference.rst:148 -msgid "id" -msgstr "id" +#: ../settings/security/third-party/twitter.rst:42 +msgid "" +"Go to \"Admin > Security > Twitter > Third Party Applications > Twitter\" " +"Section." +msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:149 -msgid "ticket number" -msgstr "bilet numarası" +#: ../settings/security/third-party/twitter.rst:None +#, fuzzy +msgid "Admin > Security > Third Party Applications" +msgstr "Üçüncü Parti Uygulamalar" -#: ../system/integrations/checkmk/api-reference.rst:151 -msgid "created_by_id" -msgstr "created_by_id" +#: ../settings/security/third-party/twitter.rst:48 +msgid "" +"Fill in the \"Twitter Key\" and the \"Twitter Secret\" and click the " +"\"Submit\" button." +msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:152 -msgid "updated_by_id" -msgstr "updated_by_id" +#: ../settings/security/third-party/twitter.rst:51 +#, fuzzy +msgid "" +"Now you can link accounts via \"Avatar > Profile > Link Accounts\" or login " +"via Zammad login page." +msgstr "" +"Artık \"Avatar -> Profil -> Hesapları Bağla\" yoluyla hesapları bağlayabilir " +"veya Zammad giriş sayfası üzerinden giriş yapabilirsiniz." -#: ../system/integrations/checkmk/api-reference.rst:155 -msgid "Which Values Can Be Set?" +#: ../settings/security/two-factor.rst:11 +msgid "Two-factor Authentication Methods" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:157 -msgid "😵 **Invalid values → unpredictable behavior**" -msgstr "😵 **Geçersiz değerler → beklenmeyen davranış**" +#: ../settings/security/two-factor.rst:2 +msgid "Two-Factor Authentication" +msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:159 +#: ../settings/security/two-factor.rst:4 msgid "" -"If you provide a value that Zammad doesn't understand (*e.g.,* ``-F " -"\"priority=high\"``), it's not always clear what will happen. In some cases, " -"a ticket will be created with the default values instead - but in others, it " -"may not be created at all!" +"Two-factor authentication (2FA) enhances the security of Zammad accounts by " +"adding an extra layer of verification beyond a password. It requires users " +"to provide two different types of authentication factors, typically " +"something they know (like a password) and something they possess (like a " +"mobile device or a security token), to ensure that only authorized " +"individuals can access the account." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:164 -msgid "So what values does Zammad understand, then? Well, it depends..." +#: ../settings/security/two-factor.rst:19 +msgid "Enable Recovery Codes" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:168 -msgid "Use an email address or username:" -msgstr "Bir e-posta adresi veya kullanıcı adı kullan:" +#: ../settings/security/two-factor.rst:21 +msgid "" +"Recovery codes are one-time use security codes that can be used by the user " +"if they lose access to their other two-factor authentication methods. They " +"cannot be used on their own, they can only be activated if at least one two-" +"factor authentication method is enabled." +msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:190 -msgid "group & priority" -msgstr "grup ve öncelik" +#: ../settings/security/two-factor.rst:None +#, fuzzy +msgid "Enable Recovery Codes Setting" +msgstr "Posta Sunucusu Ayarları" -#: ../system/integrations/checkmk/api-reference.rst:175 -msgid "Refer to the dropdown menus in the ticket pane:" +#: ../settings/security/two-factor.rst:30 +msgid "" +"Recovery codes can only be used as a backup method. If enabled, they will be " +"automatically generated for the user once they set up their initial two-" +"factor authentication method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:0 -msgid "See possible values for certain attributes in the ticket pane." +#: ../settings/security/two-factor.rst:34 +msgid "" +"The user will be asked to print out or save the generated recovery codes in " +"a safe place. Once used, a recovery code cannot be reused." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:187 -msgid "🙅 **Ticket state CANNOT be set this way!**" +#: ../settings/security/two-factor.rst:37 +msgid "" +"Users will also have an option to regenerate their recovery codes at any " +"time, which invalidates already existing recovery codes and provides them " +"with a list of fresh codes." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:189 +#: ../settings/security/two-factor.rst:41 msgid "" -"Why? Because ``-F \"state=...\"`` is already used :ref:`as a Checkmk " -"parameter `." +"After you enable this setting, when the user completes a setup of their " +"initial two-factor authentication method, they will be presented with a list " +"of recovery codes and instructed to save them for later use." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:222 -msgid "Everything Else" -msgstr "Diğer Her Şey" +#: ../settings/security/two-factor.rst:None +msgid "Recovery Codes Generation Modal Dialog" +msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:193 -msgid "" -"To set any other attributes, it helps to know your way around the :docs:" -"`rails console `. Valid values are those that you can " -"set with a string:" +#: ../settings/security/two-factor.rst:50 +msgid "Enforce the Set Up of the Two-Factor Authentication" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:218 -msgid "These values can then be passed directly to the API:" +#: ../settings/security/two-factor.rst:52 +msgid "" +"In case you wish to require your users to set up at least one two-factor " +"authentication method for their account, you can do this by selecting " +"specific user roles the requirement applies to in **Enforced for user " +"roles** setting. Of course you must have at least one two-factor " +"authentication method enabled for this setting to take effect." msgstr "" -#: ../system/integrations/checkmk/index.rst:16 -msgid "How does it work?" -msgstr "Nasıl çalışır?" +#: ../settings/security/two-factor.rst:None +msgid "Enforced for User Roles Setting" +msgstr "" -#: ../system/integrations/checkmk/index.rst:2 -msgid "Checkmk" -msgstr "Checkmk" +#: ../settings/security/two-factor.rst:62 +msgid "" +"After you change this setting, if the user has one of the selected roles on " +"their account, they will be forced to set up the two-factor authentication " +"upon next sign in or application reload." +msgstr "" -#: ../system/integrations/checkmk/index.rst:4 -#, fuzzy +#: ../settings/security/two-factor.rst:66 msgid "" -"`Checkmk `_ is a powerful IT monitoring tool that can " -"send real-time status alerts to Zammad via email or REST API. Set these " -"alerts up in Checkmk, and Zammad will automatically create, update, and " -"close tickets based on the health of your system:" +"A modal dialog with instructions will be shown, and they will not be able to " +"do any work before they set up at least one two-factor method." msgstr "" -"`Checkmk`_, e-posta veya REST API aracılığıyla Zammad'a gerçek zamanlı durum " -"uyarıları gönderebilen güçlü bir BT izleme aracıdır. Bu uyarıları Checkmk'te " -"ayarlayın ve Zammad, sisteminizin sağlığına göre otomatik olarak biletler " -"oluşturacak, güncelleyecek ve kapatacaktır:" -#: ../system/integrations/checkmk/index.rst:14 -msgid "Screenshot of ticket created by Checkmk notifications" +#: ../settings/security/two-factor.rst:None +msgid "Modal Dialog for Enforcing Two-Factor Authentication Set Up" msgstr "" -#: ../system/integrations/checkmk/index.rst:14 -msgid "Multiple alerts, same ticket." -msgstr "Çoklu uyarılar, aynı bilet." - -#: ../system/integrations/checkmk/setup-guide.rst:2 -msgid "Setup Guide" -msgstr "Kurulum Kılavuzu" +#: ../settings/security/two-factor.rst:74 +msgid "Reset Two-Factor Authentication for a Specific User" +msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:4 +#: ../settings/security/two-factor.rst:76 msgid "" -"Whenever the Checkmk integration is enabled, Zammad listens for messages on " -"its API and over email. As long as those messages follow the required " -"format, Zammad will create new tickets (or find and update existing ones) " -"based on the message contents." +"In case an user isn't able to login anymore because of an inaccessible " +"second factor, you can reset the user's 2FA method." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:10 +#: ../settings/security/two-factor.rst:79 msgid "" -"That means that “setting up Checkmk integration” is simply a matter of " -"**adding configuration to your Checkmk site**: telling it when to send these " -"messages and what to say. To do that, you'll need to create a new " -"**notification rule** (see `Checkmk's official docs `_ for help with that)." +"To do this, go to the user management and search for the relevant user. " +"After you found the account, click the button in the action column and " +"select \"Manage Two-Factor Authentication\":" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:17 +#: ../settings/security/two-factor.rst:None +msgid "Context menu in action column in user management" +msgstr "" + +#: ../settings/security/two-factor.rst:87 msgid "" -"As part of this new rule, you'll have to choose a **notification method** " -"(*i.e.,* a script to execute whenever the rule is triggered). This script " -"will be written by you (samples below), and contain the logic for sending " -"API/email messages to Zammad:" +"After selecting this, you can see a dialog where you can either reset one " +"2FA method or reset all of the user's 2FA methods:" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:26 -msgid "Checkmk \"New Rule\" dialog" +#: ../settings/security/two-factor.rst:None +msgid "Dialog for resetting user's 2FA method" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:26 +#: ../settings/security/two-factor.rst:94 msgid "" -"Find your custom scripts in the Checkmk WATO under **Notifications > New " -"Rule > Notification Method**." +"Choose the fitting one, click on the corresponding \"Remove ...\" button and " +"confirm your action. The user now has to setup a new 2FA method, depending " +"on your 2FA configuration." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:29 -msgid "" -"Once you're done setting up your new rule, you're all set! New tickets " -"should start coming in and auto-updating any time your rule is triggered." +#: ../settings/security/two-factor/authenticator-app.rst:2 +msgid "Authenticator App" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:33 +#: ../settings/security/two-factor/authenticator-app.rst:4 msgid "" -"(If you need help troubleshooting, be sure to check the :ref:`checkmk-recent-" -"logs`.)" +"The authenticator app method is a type of two-factor authentication that " +"uses a mobile application to generate one-time codes for account " +"verification. After setting up the authenticator app on their device, the " +"user links it to their Zammad account." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:38 -msgid "API Alerts" -msgstr "API Uyarıları" - -#: ../system/integrations/checkmk/setup-guide.rst:40 +#: ../settings/security/two-factor/authenticator-app.rst:12 msgid "" -"To add these scripts in the Checkmk WATO, copy them into your Checkmk " -"installation directory and make them executable. (Be sure to replace the " -"``zammad.example.com`` callback URL with the one found in your admin panel.)" +"When logging in, the user is prompted to enter a time-sensitive code " +"generated by the app, in addition to their password. This code acts as the " +"second factor of authentication, providing an extra layer of security as it " +"changes periodically and is unique to the user's device." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:60 -msgid "Service notification" -msgstr "Servis bildirimi" +#: ../settings/security/two-factor/authenticator-app.rst:None +msgid "Security Code in Google Authenticator App" +msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:46 +#: ../settings/security/two-factor/authenticator-app.rst:22 msgid "" -"For updates on the status of the software running on your server (*e.g.,* " -"postgres)." +"The app generates codes based on a shared secret key stored securely on both " +"the user's device and the server, ensuring a synchronized and secure " +"authentication process. The method of generating the codes is sometimes also " +"called TOTP (time-based one-time password)." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:75 -msgid "Host notification" +#: ../settings/security/two-factor/authenticator-app.rst:28 +msgid "Enabling the Authenticator App Method" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:63 -msgid "For updates on the status of the server itself." +#: ../settings/security/two-factor/authenticator-app.rst:30 +#: ../settings/security/two-factor/security-keys.rst:28 +msgid "To enable the method, just toggle the switch on in the settings." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:77 -#, fuzzy -msgid "🤔 **What's with all the env vars?**" -msgstr "🤔 **OAuth neyin nesi?**" - -#: ../system/integrations/checkmk/setup-guide.rst:79 -msgid "" -"Whenever Checkmk runs these scripts, it needs to provide some information " -"about the event that triggered the notification. This information is passed " -"in the form of these ``$NOTIFY_*`` environment variables." +#: ../settings/security/two-factor/authenticator-app.rst:None +msgid "Authenticator App Switch in Settings" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:85 +#: ../settings/security/two-factor/authenticator-app.rst:36 msgid "" -"You can specify additional parameters to pass to the script when you're " -"setting up your notification rule, but the ones you see here are all " -"provided by default." +"Now the users will be able to set up this two-factor authentication method " +"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " +"Once they do, on next sign-in with password, they will be asked to provide " +"an additional security code generated by their mobile device." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:90 -msgid "Email Alerts" -msgstr "E-posta Uyarıları" +#: ../settings/security/two-factor/security-keys.rst:2 +#, fuzzy +msgid "Security Keys" +msgstr "Güvenlik" -#: ../system/integrations/checkmk/setup-guide.rst:94 +#: ../settings/security/two-factor/security-keys.rst:4 msgid "" -"🐞 **There are known bugs** in Zammad's processing of email from Checkmk. " -"This section will be completed once they have been resolved. (Learn more at " -"GitHub issues `#2377 `_ & " -"`#2180 `_.)" +"The security keys method is a type of a two-factor authentication that uses " +"Web Authentication API in the browser for verifying user's identity. The " +"user can register multiple hardware or software security keys with their " +"Zammad account and then they can use it during the sign-in process." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:100 -msgid "In the meantime, we encourage you to set up API alerts instead." +#: ../settings/security/two-factor/security-keys.rst:12 +msgid "" +"When logging in, the user is prompted to provide the same security key they " +"registered with their account, in addition to their password. This key acts " +"as the second factor of authentication, providing an extra layer of security." msgstr "" -#: ../system/integrations/clearbit.rst:2 -msgid "Clearbit" -msgstr "Clearbit" +#: ../settings/security/two-factor/security-keys.rst:None +msgid "Security Key dialog in Safari on macOS" +msgstr "" -#: ../system/integrations/clearbit.rst:4 +#: ../settings/security/two-factor/security-keys.rst:21 msgid "" -"With our Clearbit integration, you can easily enrich the information " -"provided by Zammad. If the customers or agents email address is known to " -"Clearbit, it will share all information it has regarding the user with " -"Zammad. Those information can include the following:" +"The type of the key can range from hardware USB sticks to passkeys stored in " +"a device of user's choice. Which type can be used depends on the browser " +"flavor and the platform of the user." msgstr "" -#: ../system/integrations/clearbit.rst:9 -msgid "Avatar" -msgstr "Avatar" - -#: ../system/integrations/clearbit.rst:10 -msgid "Address information" -msgstr "Adres bilgisi" - -#: ../system/integrations/clearbit.rst:11 -msgid "Website information" -msgstr "Web site bilgisi" +#: ../settings/security/two-factor/security-keys.rst:26 +msgid "Enabling the Security Keys Method" +msgstr "" -#: ../system/integrations/clearbit.rst:12 -msgid "A BIO (as Note by default)" +#: ../settings/security/two-factor/security-keys.rst:None +msgid "Security Keys Switch in Settings" msgstr "" -#: ../system/integrations/clearbit.rst:14 +#: ../settings/security/two-factor/security-keys.rst:34 msgid "" -"If needed, you can add further custom objects and add mappings to them, so " -"the Clearbit information can be filled within the database. In general you " -"can get any information from Clearbit, as long as you have a mapping to an " -"Zammad object." +"Now the users will be able to set up this two-factor authentication method " +"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " +"Once they do, on next sign-in with password, they will be asked to provide " +"the same security key they registered during the setup." msgstr "" -#: ../system/integrations/clearbit.rst:21 +#: ../settings/system/system-selfhosted.include.rst:3 msgid "" -"Clearbit does have a mapping of fields like LDAP and Exchange have, but does " -"not \"win\" against Zammad information. This means that if you have e.g. the " -"last name field filled in already and Clearbit has other information on " -"that, it will not be updated." +"Below settings are only available to self hosted users. In hosted " +"environments we're handling these settings for you to ensure service " +"stability." msgstr "" +"Aşağıdaki ayarlar yalnızca kendi kendine barındırılan kullanıcılar " +"tarafından kullanılabilir. Barındırılan ortamlarda, hizmet istikrarını " +"sağlamak için bu ayarları sizin için hallediyoruz." -#: ../system/integrations/clearbit.rst:26 -msgid "" -"However: If let's say the last name has been set by Clearbit and Zammad " -"notices that the last name on the Clearbit source has changed, Zammad will " -"also update this value." +#: ../settings/system/base.rst:11 +msgid "Fully Qualified Domain Name" msgstr "" -#: ../system/integrations/clearbit.rst:33 -msgid "" -"The configuration of Clearbit is really easy and done fast! Just login to " -"your Clearbit-Account, go to \"API\" and copy the secret-API-Key." +#: ../settings/system/base.rst:7 +msgid "The URL of your Zammad installation." msgstr "" -#: ../system/integrations/clearbit.rst:38 -msgid "" -"Now change to your Zammad instance, go to Integrations (System) -> Clearbit " -"in the admin panel. Paste your API-Key into the API-Key-Field and decide if " -"Zammad should create unknown Organizations automatically, if the user does " -"not have one yet (and Clearbit knows it). The shared option decides if the " -"new organizations Zammad creates with Clearbit should be shared ones." +#: ../settings/system/base.rst:9 ../settings/system/base.rst:17 +msgid "This setting is used within :doc:`/misc/variables` and notifications." msgstr "" -#: ../system/integrations/clearbit.rst:47 -msgid "" -"If you're unsure what option to choose, better stick with \"no\". You can " -"also learn more about :doc:`/manage/organizations/index`." +#: ../settings/system/system-base.include.rst:1 +#, fuzzy +msgid "It is automatically set by the *Getting Started wizard*." +msgstr "Bu ayar otomatik olarak Başlarken sihirbazı tarafından ayarlandı." + +#: ../settings/system/system-base.include.rst:5 +msgid "Changing this setting also changes callback URLs for your channels etc." msgstr "" +"Bu ayarın değiştirilmesi, kanallarınız vb. için geri arama URL'lerini de " +"değiştirir." + +#: ../settings/system/system-base.include.rst:6 +msgid "This setting can have negative affects on being able to login." +msgstr "Bu ayarın giriş yapabilme üzerinde olumsuz etkileri olabilir." -#: ../system/integrations/clearbit.rst:52 -msgid "" -"The Mapping option works similar to the mapping within the Exchange and LDAP " -"sync. You can add further mappings for e.g. custom fields if you need more " -"information that Clearbit can provide." -msgstr "" +#: ../settings/system/base.rst:19 +msgid "HTTP type" +msgstr "HTTP türü" -#: ../system/integrations/clearbit.rst:58 +#: ../settings/system/base.rst:14 msgid "" -"If you want to add more Clearbit fields and want to learn more about " -"available fields on their API, you can take a look at their `API " -"documentation `_." +"The HTTP type tells your installation how your clients connect. This is " +"relevant for authentication and cookie security." msgstr "" -#: ../system/integrations/clearbit.rst:62 -msgid "" -"If you're happy with the above chosen Settings and your mapping, just save " -"the changes and enable Clearbit integration. Zammad will now start polling " -"the Clearbit API as users contact you." -msgstr "" +#: ../settings/system/base.rst:31 +msgid "SystemID" +msgstr "SystemID" -#: ../system/integrations/clearbit.rst:68 +#: ../settings/system/base.rst:22 msgid "" -"Zammad does not synchronize with Clearbit on a regular basis, but on demand " -"if needed. This saves API calls." +"This ID is being used within your ticket number. In case you're " +"communicating with another ticket system with similar ticket number schemes " +"this ID greatly reduces the risk of false follow ups." msgstr "" -#: ../system/integrations/clearbit.rst:73 +#: ../settings/system/base.rst:26 msgid "" -"Below the Settings and Mappings, you'll find our Integration log. You can " -"see what requests Zammad sent to Clearbit and also the APIs Response." +"The SystemID is randomly selected upon installation of Zammad (``1-99``)." msgstr "" -#: ../system/integrations/clearbit.rst:78 +#: ../settings/system/base.rst:30 msgid "" -"By the way, you can also view the API log on the Clearbit website - the " -"information seen is basically the same." +"**Do not** change this setting in a productive system! Your Zammad " +"installation may no longer recognize old ticket number based follow ups upon " +"change!" msgstr "" -#: ../system/integrations/clearbit.rst:84 -#, fuzzy -msgid "Example When Adding a User" -msgstr "Bir kullanıcı ekleme örneği" +#: ../settings/system/frontend.rst:2 +msgid "Frontend" +msgstr "Ön yüz" -#: ../system/integrations/clearbit.rst:86 -msgid "" -"To show you how fast information is added, we added a small Screencast " -"below. This shows the creation of the User Alex from Clearbit. As we already " -"set the last name of Alex to \"X\", Zammad did not update it. What Zammad " -"did was to add further information it received from Clearbit." +#: ../settings/system/frontend.rst:22 +msgid "Core Workflow Ajax Mode" msgstr "" -#: ../system/integrations/cti/generic.rst:2 -msgid "CTI (generic)" -msgstr "CTI (generic)" - -#: ../system/integrations/cti/includes/introduction.include.rst:1 +#: ../settings/system/frontend.rst:6 msgid "" -"This integration enables Zammad to provide a caller log to your agents. With " -"this your agents can greet your customers by their name and are supported by " -"Zammad with automatically opening a new ticket dialog or the user profile." +"This setting allows administrators to enforce :doc:`/system/core-workflows` " +"to use Ajax-Calls instead of web sockets. You'll usually only need this if " +"you experience serious issues as noted below." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:6 -msgid "" -"Click the toggle next to the heading to activate or deactivate this " -"integration." +#: ../settings/system/frontend.rst:10 +msgid "**🤓 Possible (technical) reasons**" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:9 +#: ../settings/system/frontend.rst:12 msgid "" -"If you want to learn more on how your agents can use this function, please " -"refer the :user-docs:`user documentation `." +"In some cases, your network structure (e.g. firewalls, proxies) may " +"disconnect long web socket connections. This leads to select fields staying " +"empty (e.g. owner selection *after* selecting your group) or fields not " +"shown / hidden (e.g. when switching to or from pending states, the \"pending " +"till\" field not showing / hiding)." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:14 +#: ../settings/system/frontend.rst:18 msgid "" -"Automatically opening new ticket dialogues or user profiles requires agent " -"to extension mapping - see more below." +"Please keep in mind that the Ajax fallback may cause serious pressure on " +"your application server. If you have the choice stick to web sockets." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:20 -msgid "Please note the following limitations to reduce confusion later on:" +#: ../settings/system/frontend.rst:22 +msgid "Default: ``no`` (inactive)" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:22 -msgid "CTI integrations provide caller log functions only." +#: ../settings/system/frontend.rst:53 +msgid "Show calendar weeks in the picker of date/datetime fields" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:23 +#: ../settings/system/frontend.rst:25 msgid "" -"This integration does not provide any VoIP functionalities; you can't make " -"phone calls from within Zammad." +"With this setting you can instruct Zammad to provide week number display " +"globally for all users. Calendar with week number display are usually used " +"in business sectors and may not be relevant for everyone." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:25 +#: ../settings/system/frontend.rst:29 msgid "" -"If your browser supports ``tel``-URLs, you can click on phone numbers for " -"automatic dialing. This requires additional software / configuration on your " -"agent's computers." +"This setting affects *all areas* - you'll also see week numbers in the admin " +"panel for e.g. triggers and macros." msgstr "" -#: ../system/integrations/cti/generic.rst:9 -#: ../system/integrations/cti/placetel.rst:14 -#: ../system/integrations/cti/sipgate.rst:14 -msgid "Please provide the following requirements:" +#: ../settings/system/frontend.rst:32 +msgid "Default: ``no`` (not shown)" msgstr "" -#: ../system/integrations/cti/generic.rst:11 -msgid "" -"A telephone system that supports webhooks (outbound) (best option are those " -"that allow customizing the calls)." +#: ../settings/system/frontend.rst:53 +msgid "Here's the difference:" msgstr "" -#: ../system/integrations/cti/generic.rst:13 -msgid "A unique Call-ID during the call session." +#: ../settings/system/frontend.rst:0 +msgid "Screenshot showing Zammad's date picker (in the default way)" msgstr "" -#: ../system/integrations/cti/generic.rst:14 -msgid "Call event data (both numbers and direction)." +#: ../settings/system/frontend.rst:41 +msgid "Set to ``no``" msgstr "" -#: ../system/integrations/cti/generic.rst:15 -msgid "Your Zammad instance must be reachable for your telephony system." +#: ../settings/system/frontend.rst:0 +msgid "" +"Screenshot showing Zammad's date picker with\n" +"week numbers enabled" msgstr "" -#: ../system/integrations/cti/generic.rst:17 +#: ../settings/system/frontend.rst:50 +#, fuzzy +msgid "Set to ``yes``" +msgstr "``hayır`` veya ``evet``" + +#: ../settings/system/index.rst:4 msgid "" -"If you want to learn more on what kind of requests are supported by Zammad " -"and what it expects, please consult our :docs:`CTI-API documentation `." +"For your overview we split each tab within system settings into its own page:" msgstr "" +"Genel bakışınız için sistem ayarlarındaki her sekmeyi kendi sayfasına " +"ayırdık:" -#: ../system/integrations/cti/generic.rst:22 -#: ../system/integrations/cti/placetel.rst:27 -#: ../system/integrations/cti/sipgate.rst:30 +#: ../settings/system/index.rst:16 #, fuzzy -msgid "Available Settings" -msgstr "Posta Sunucusu Ayarları" +msgid "Console Based Settings" +msgstr "Konsol tabanlı ayarlar 🤓" -#: ../system/integrations/cti/generic.rst:29 -#: ../system/integrations/cti/placetel.rst:41 -#: ../system/integrations/cti/sipgate.rst:40 +#: ../settings/system/index.rst:18 #, fuzzy -msgid "Endpoint Settings" -msgstr "Ayarlar Listesi" - -#: ../system/integrations/cti/generic.rst:25 msgid "" -"Zammad will list your generic CTI endpoint here. It contains a unique token " -"so ensure to keep this URL save." +"There's some console based settings we didn't put into the UI. However, you " +"may find them helpful - you can find them in our :docs:`hidden settings ` section." msgstr "" +"Kullanıcı arayüzüne koymadığımız bazı konsol tabanlı ayarlar var. Ancak, " +"bunları yararlı bulabilirsiniz - bunları `gizli ayarlar `_ bölümümüzde " +"bulabilirsiniz." -#: ../system/integrations/cti/generic.rst:28 +#: ../settings/system/network.rst:2 +msgid "Network" +msgstr "Ağ" + +#: ../settings/system/network.rst:8 msgid "" -"You'll need this endpoint for your PBX to talk to Zammad, see :docs:`CTI-API " -"documentation `." +"The proxy settings can only be saved after successfully testing the proxy " +"connection." msgstr "" -#: ../system/integrations/cti/includes/important-dont-forget-saving.include.rst:3 +#: ../settings/system/network.rst:15 +#, fuzzy +msgid "Proxy Address." +msgstr "Proxy Adresi" + +#: ../settings/system/network.rst:12 msgid "" -"All following options **do not save automatically**. Always use the Save " -"button on the lower end of the integration page!" +"Allows you to provide a proxy server if needed. This is relevant for network " +"communication by Zammad." msgstr "" -#: ../system/integrations/cti/generic.rst:43 -#: ../system/integrations/cti/placetel.rst:49 -#: ../system/integrations/cti/sipgate.rst:52 -#, fuzzy -msgid "Call Settings" -msgstr "Ayarlar" +#: ../settings/system/network.rst:15 +msgid "It **does not** affect the update process or Elasticsearch." +msgstr "" -#: ../system/integrations/cti/generic.rst:39 -#: ../system/integrations/cti/placetel.rst:49 -#: ../system/integrations/cti/sipgate.rst:37 -#: ../system/integrations/cti/sipgate.rst:50 -msgid "Inbound" +#: ../settings/system/network.rst:18 +msgid "Username for proxy connection." msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:1 +#: ../settings/system/network.rst:18 msgid "" -"This option allows you to block specific incoming caller IDs. It allows you " -"to temporarily reject e.g. spam callers without having to contact providers " -"or PBX administrators." +"If your proxy server requires authentication, provide the username here." msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:11 -#, fuzzy -msgid "Caller ID to block" -msgstr "arayan ID verisi" - -#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 -msgid "Provide caller IDs to block in ``E.164`` format." +#: ../settings/system/network.rst:21 +msgid "Password for proxy connection." msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:8 +#: ../settings/system/network.rst:21 msgid "" -"Your telephony system has to support this function. Zammad will send a " -"``reject`` response which will cause your telephony system to hang up the " -"call. To callers this usually will feel like the line is busy." +"If your proxy server requires authentication, provide the password here." msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:14 +#: ../settings/system/network.rst:26 +msgid "No proxy for the following hosts." +msgstr "" + +#: ../settings/system/network.rst:24 msgid "" -"Provide a meaningful note for your fellow administrators to remind yourself " -"why you've chosen to block the number." +"Exception list for hosts you can't or don't want to reach via proxy server." +msgstr "" + +#: ../settings/system/network.rst:27 +msgid "Default: ``localhost,127.0.0.0,::1``" +msgstr "Varsayılan: ``localhost,127.0.0.0,::1``" + +#: ../settings/system/services.rst:2 +msgid "Services" +msgstr "Servisler" + +#: ../settings/system/services.rst:10 +msgid "Image Service" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 -#: ../system/integrations/cti/includes/outbound-calls.include.rst:17 -#: ../system/integrations/cti/sipgate.rst:40 -msgid "Outbound" +#: ../settings/system/services.rst:5 +msgid "Defines the backend for user and organization image lookups." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:1 +#: ../settings/system/services.rst:7 +msgid "Default: ``Zammad Image Service`` (active)" +msgstr "" + +#: ../settings/system/services.rst:9 msgid "" -"In many cases you may want to use a different caller ID depending on the " -"destination you're calling. This may apply due to specific connection rates " -"to other countries or because you want your customer to feel you're calling " -"from the same country." +"Make sure your on premise installation has ``HTTPS`` access to ``images." +"zammad.com``." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:6 -msgid "This option expects ``E.164`` number formats." +#: ../settings/system/services.rst:18 +msgid "Geo Calendar Service" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 -#, fuzzy -msgid "Destination caller ID" -msgstr "Hedef Grup" +#: ../settings/system/services.rst:13 +msgid "" +"Defines the backend for geo calendar lookups. Used for initial calendar " +"setup." +msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:5 -msgid "The caller ID or number you're trying to call." +#: ../settings/system/services.rst:16 +msgid "Default: ``Zammad GeoCalendar Service`` (active)" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:7 -msgid "You can use wildcards for e.g. country specific outbound numbers like:" +#: ../settings/system/services.include.rst:2 +msgid "" +"Make sure your on premise installation has ``HTTPS`` access to ``geo.zammad." +"com``." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:9 -msgid "``49*`` for Germany" +#: ../settings/system/services.rst:26 +msgid "Geo IP Service" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:10 -msgid "``4930*`` for Berlin / Germany landlines" +#: ../settings/system/services.rst:21 +msgid "" +"Defines the backend for geo IP lookups. Shows also location of an IP address " +"if an IP address is shown." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 -msgid "``33*`` for France" +#: ../settings/system/services.rst:24 +msgid "Default: ``Zammad GeoIP Service`` (active)" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:15 -msgid "Set Outbound caller ID" +#: ../settings/system/services.rst:32 +msgid "Geo Location Service" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:14 +#: ../settings/system/services.rst:29 msgid "" -"The outbound caller ID to set (the number your customer sees on his display) " -"in ``E.164`` number format." +"Defines the backend for geo location lookups to store geo locations for " +"addresses." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 -msgid "Provide a short description for fellow administrators." +#: ../settings/system/services.rst:32 +msgid "" +"Default: ``OpenStreetMap (ODbL 1.0, http://osm.org/copyright)`` (active)" msgstr "" -#: ../system/integrations/cti/includes/generic-cti-support-note.includes.rst:3 +#: ../settings/system/services.rst:36 msgid "" -"This option requires your PBX to send a specific request to Zammad *before " -"dialing*. Please consult the :docs:`CTI API ` in case " -"you're not sure." +"You can find a detailed privacy information on what we store for how long on " +"our :docs:`Privacy Appendix ` inside of our System " +"Documentation." msgstr "" -#: ../system/integrations/cti/generic.rst:52 -#: ../system/integrations/cti/placetel.rst:54 -#: ../system/integrations/cti/sipgate.rst:59 -#, fuzzy -msgid "Other Settings" -msgstr "Ayarlar" +#: ../settings/system/storage.rst:2 +msgid "Storage" +msgstr "Saklama" -#: ../system/integrations/cti/includes/other-settings-intro.include.rst:1 +#: ../settings/system/storage.rst:6 msgid "" -"Below you can find all available additional settings for this CTI " -"integration. For your overview we're sorting them by appearance and " -"reference their description first." +"Here you can define where Zammad stores attachments for tickets and the " +"knowledge base. By default, we're writing to the ``Database`` - you can " +"switch to ``Filesystem`` or ``Simple Storage (S3)`` at any time. In this " +"case please have a look on the following instructions." msgstr "" -#: ../system/integrations/cti/includes/default-caller-id.include.rst:2 -#: ../system/integrations/cti/includes/default-caller-id.include.rst:1 -msgid "Default caller ID for outbound calls" +#: ../settings/system/storage.rst:11 +#, fuzzy +msgid "" +"If you have a busy Zammad instance, we strongly encourage you to use " +"filesystem storage instead of \"Database\". This will greatly improve system " +"performance (de-crease database load and size)." msgstr "" +"Meşgul durumlarda dosya sistemi depolamasını kullanmanızı şiddetle tavsiye " +"ederiz. Bu, sistem performansını büyük ölçüde iyileştirir (veritabanı yükünü " +"ve boyutunu azaltır)." -#: ../system/integrations/cti/includes/records-caller-log.include.rst:16 -#: ../system/integrations/cti/includes/records-caller-log.include.rst:15 -msgid "Shown records in caller log" +#: ../settings/system/storage.rst:19 +msgid "Database" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:2 +#: ../settings/system/storage.rst:17 msgid "" -"Allows you to set the number of shown caller log entries for all users. You " -"can choose from the following values:" -msgstr "" - -#: ../system/integrations/cti/includes/records-caller-log.include.rst:5 -msgid "60 (default)" +"This is the default storage method. The attachments are stored directly in " +"the database. If your Zammad instance grows, we recommend one of the other " +"methods to maintain performance." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:6 +#: ../settings/system/storage.rst:38 #, fuzzy -msgid "120" -msgstr "20" +msgid "Filesystem" +msgstr "Sistem" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:7 -msgid "180" +#: ../settings/system/storage.rst:22 +#, fuzzy +msgid "" +"This storage method is recommended for all Zammad instances, especially for " +"those with a higher load. If you choose filesystem, your files are written " +"to ``/opt/zammad/storage/``." msgstr "" +"Varsayılan olarak \"Veritabanı\"na yazıyoruz - istediğiniz zaman \"Dosya " +"Sistemi\"ne geçebilirsiniz. Dosya sistemini seçtiyseniz, dosyalarınız ``/opt/" +"zammad/fs/`` dizinine yazılır." -#: ../system/integrations/cti/includes/records-caller-log.include.rst:8 -msgid "240" -msgstr "240" - -#: ../system/integrations/cti/includes/records-caller-log.include.rst:9 -msgid "300" +#: ../settings/system/storage.rst:26 +msgid "" +"Moving attachments from \"Database\" to \"Filesystem\" can be run during " +"production use. However, you should consider your framework conditions (e.g. " +"bandwidth, system load in production) to define the right moment." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:11 -msgid "**🥵 Potential performance issue**" +#: ../settings/system/storage.rst:32 +msgid "**You noticed slow updates of Zammad?**" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:13 +#: ../settings/system/storage.rst:34 msgid "" -"Setting this setting higher than 60 may cause serious performance issues on " -"very busy instances. Keep in mind that this setting causes Zammad to poll " -"and send up to 300 records to *all active agent sessions* in very short time " -"periods." +"While Zammad is beeing updated, it enforces a recursive \"change " +"owner\" (chown) for this directory. For instances with many files this can " +"be time consuming. To mitigate that you can move your files and create a " +"symlink in ``/opt/zammad/storage/`` to the new directory. Of course you have " +"to make sure on your own that the permissions are always correct." msgstr "" -#: ../system/integrations/cti/generic.rst:73 -msgid "Caller Log Filter" +#: ../settings/system/storage.rst:95 +msgid "Simple Storage (S3)" msgstr "" -#: ../system/integrations/cti/generic.rst:55 +#: ../settings/system/storage.rst:41 msgid "" -"This function allows you to provide call information based on e.g. queues " -"only to agents that really need the information." +"To use the Simple Storage (S3), you have to provide some settings, which " +"can't be accessed in the UI (see instructions below)." msgstr "" -#: ../system/integrations/cti/generic.rst:58 +#: ../settings/system/storage.rst:44 msgid "" -"Why? If you have a team for several countries or departments, you don't want " -"to bug your agents from other departments. Leaving these options empty will " -"fallback to showing everything to everyone." +"⚠️ Please note that the current implementation is in its early stages and can " +"be modified in the future." msgstr "" -#: ../system/integrations/cti/generic.rst:64 -#, fuzzy -msgid "Destination caller ID or Queue" -msgstr "Hedef Grup" +#: ../settings/system/storage.rst:47 +msgid "" +"The prerequisite is to have access to a S3-compatible storage and to have " +"all necessary parameters available (which depends on your storage provider; " +"if in doubt, please ask there for help)." +msgstr "" -#: ../system/integrations/cti/generic.rst:63 +#: ../settings/system/storage.rst:51 +msgid "Steps to configure S3:" +msgstr "" + +#: ../settings/system/storage.rst:53 msgid "" -"This depends on your PBX and usually is either a queue ID, phone number or " -"extension." +"Copy ``config/zammad/storage.yml.dist`` to ``config/zammad/storage.yml``" msgstr "" -#: ../system/integrations/cti/generic.rst:69 -msgid "Agents" +#: ../settings/system/storage.rst:54 +msgid "Edit the copied file in one of the following ways:" msgstr "" -#: ../system/integrations/cti/generic.rst:67 +#: ../settings/system/storage.rst:56 msgid "" -"Select the agents that are responsible for the group. These agents will then " -"see caller log entries and call notifications fitting to said queue." +"Either provide your S3 configuration with one attribute per line like in the " +"upper area of the file" msgstr "" -#: ../system/integrations/cti/generic.rst:0 +#: ../settings/system/storage.rst:58 msgid "" -"Screenshot showing the caller log filter table with pre filled sample data" +"Or provide your S3 configuration as an URL (which you can find at the end of " +"the file). Note: you can also provide this URL as environment variable (:" +"docs:`see system documentation `) without using this yml-file." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:6 +#: ../settings/system/storage.rst:62 msgid "" -"With recent logs Zammad allows you to view the latest calls for the CTI " -"functionality. This usually comes in handy, when you're looking for errors." +"We recommend the deletion of the not used configuration style to avoid " +"inconsistencies." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:0 +#: ../settings/system/storage.rst:65 +msgid "Restart Zammad so the config file / environment variable is loaded" +msgstr "" + +#: ../settings/system/storage.rst:66 msgid "" -"Screenshot showing several incoming requests within Recent logs section." +"Set the \"Storage Method\" in Zammad to ``Simple Storage (S3)`` in Settings " +"> System > Storage and click on \"Submit\". After that, Zammad checks your " +"configuration and the connection to the service and will raise an error " +"message if something is wrong." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:16 -msgid "I'm just here to clear floats up." +#: ../settings/system/storage.rst:72 +msgid "A very simple storage configuration could look like this:" msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:20 +#: ../settings/system/storage.rst:85 msgid "" -"By clicking on the entry of interest, Zammad will provide more details on " -"the call in question. You'll see the payload it received and also the " -"response that was sent." +"Before setting the storage method to ``Simple Storage (S3)`` (step 4), " +"please make sure to have a working setup." +msgstr "" + +#: ../settings/system/storage.rst:88 +msgid "" +"You can verify this by running ``rails r 'Rails.logger = Logger.new(STDOUT); " +"pp Store::Provider::S3.ping?'`` in your Zammad directory. If everything is " +"fine, you should see ``true``, else you should see ``false`` and a simple " +"error message." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:0 +#: ../settings/system/storage.rst:93 msgid "" -"Screenshot showing detailed information of a specific log entry of recent " -"logs" +"If you installed Zammad through a package manager (rather than from source), " +"replace ``rails r`` with ``zammad run rails r`` above. To learn more, see :" +"docs:`Administration via Console `." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:31 -msgid "x" +#: ../settings/ticket.rst:4 +msgid "" +"Here you can adjust general ticket settings. Additional ones for the ticket " +"composer interface can be found in the :doc:`/misc/composer`." msgstr "" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 -#: ../system/integrations/cti/includes/troubleshooting.include.rst:9 -msgid "My Phone page stays blank, signalling does work..." -msgstr "" +#: ../settings/ticket.rst:11 +msgid "Ticket Hook (default: ``Ticket#``)" +msgstr "Bilet Kancası (varsayılan: ``Bilet#``)" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:5 -msgid "" -"If you've made sure that signalling works (check Recent logs) and your " -"Caller Log still stays empty, please ensure that you only configured one CTI " -"integration version. Specifically defining more than one agent mapping on " -"the different integration variants will be the issue." -msgstr "" +#: ../settings/ticket.rst:11 +msgid "The identifier for a ticket; *e.g.,* Ticket#, Call#, MyTicket#." +msgstr "Bir bilet için tanımlayıcılar; *ör.,* Bilet#, Arama#, Biletim#." -#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 -msgid "Clear the not needed agent mapping and reload your browser page." -msgstr "" +#: ../settings/ticket.rst:38 +msgid "Ticket Hook Position (default: ``right``)" +msgstr "Bilet Kancası Pozisyonu (varsayılan: ``sağ``)" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:1 +#: ../settings/ticket.rst:14 msgid "" -"By mapping your agents extension to their existing Zammad users, Zammad can " -"provide a new ticket dialog or open the user profile for the agent that " -"picks up the call." +"With this setting you can decide (if) where to insert the ticket number." msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:5 -msgid "" -"This speeds up ticket aiding, no matter if it's for existing tickets or new " -"ones!" -msgstr "" +#: ../settings/ticket.rst:20 +msgid "*Right*" +msgstr "*Sağ*" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:8 +#: ../settings/ticket.rst:17 msgid "" -"To see it work from the agent's perspective, have a look on :user-docs:`user " -"documentation `." +"This setting will add the ticket reference on the right site of the subject." msgstr "" -#: ../system/integrations/cti/placetel.rst:2 -msgid "Placetel CTI" -msgstr "Placetel CTI" +#: ../settings/ticket.rst:20 +msgid "Example: ``Some Subject [Ticket#12345]``" +msgstr "Örnek: ``Konu [Bilet#12345]``" -#: ../system/integrations/cti/placetel.rst:16 -#, fuzzy -msgid "You need an administrative Placetel account for your organization." -msgstr "🔑 **Organizasyonunuz için bir yönetici hesabı kullanın.**" +#: ../settings/ticket.rst:26 +msgid "*Left*" +msgstr "*Sol*" -#: ../system/integrations/cti/placetel.rst:17 -#: ../system/integrations/cti/sipgate.rst:20 +#: ../settings/ticket.rst:23 msgid "" -"Your Zammad instance must be allowed to communicate to external services." +"This setting will add the ticket reference on the left site of the subject." msgstr "" -#: ../system/integrations/cti/placetel.rst:18 -msgid "Placetel must be able to reach your Zammad instance." -msgstr "" +#: ../settings/ticket.rst:26 +msgid "Example: ``[Ticket#12345] Some Subject``" +msgstr "Örnek: ``[Bilet#12345] Konu``" -#: ../system/integrations/cti/placetel.rst:22 -msgid ":doc:`provider-configurations/placetel`" +#: ../settings/ticket.rst:29 +msgid "*None*" +msgstr "*Hiçbiri*" + +#: ../settings/ticket.rst:29 +msgid "This will completely remove ticket references from the subject." msgstr "" -#: ../system/integrations/cti/placetel.rst:21 +#: ../settings/ticket.rst:33 msgid "" -"Learn how to configure Placetel to enable Zammad and Placetel to communicate " -"with each other." +"Please ensure to take a look at :doc:`/channels/email/settings` within the " +"email channel to ensure you have at least one reference that helps Zammad to " +"assign follow-ups correctly." msgstr "" -#: ../system/integrations/cti/placetel.rst:32 +#: ../settings/ticket.rst:37 msgid "" -"The here listed endpoint settings are relevant for the :doc:`integration " -"configuration with Placetel `." +"Disabling this and not setting up any further follow up search will lead to " +"unexpected results!" msgstr "" -#: ../system/integrations/cti/placetel.rst:37 -#: ../system/integrations/i-doit.rst:53 -msgid "Endpoint" +#: ../settings/ticket.rst:65 +msgid "" +"Ticket Last Contact Behaviour (default: ``Use the start time of the last " +"customer thread (which may consist of multiple articles).``)" msgstr "" -#: ../system/integrations/cti/placetel.rst:36 +#: ../settings/ticket.rst:41 msgid "" -"This endpoint will be required for the Zammad integration within the " -"Placetel web interface." +"This setting changes the way Zammad updates the ``Last Contact`` value of a " +"ticket. This is fairly important for overviews and what you expect upon " +"ticket updates of a customer." msgstr "" -#: ../system/integrations/cti/placetel.rst:41 -msgid "API Token" +#: ../settings/ticket.rst:52 +msgid "" +"Use the start time of the last customer thread (which may consist of " +"multiple articles)." msgstr "" -#: ../system/integrations/cti/placetel.rst:40 +#: ../settings/ticket.rst:46 msgid "" -"You'll receive this token within the ``Web API`` menu. Make sure to copy " -"this value, it's only shown once!" +"If this option is chosen, Zammad will update the last updated value just " +"once if a customer replies. After that, Zammad will wait for an agent to " +"react." msgstr "" -#: ../system/integrations/cti/placetel.rst:71 -#: ../system/integrations/cti/sipgate.rst:77 -msgid "Phone Extension to Agent Mapping" +#: ../settings/ticket.rst:50 +msgid "" +"This comes in handy if you want to work tickets in the order of their first " +"update. This will not change ticket orders if customers decide to \"bump\" " +"the ticket affected." msgstr "" -#: ../system/integrations/cti/placetel.rst:0 -msgid "Screenshot showing sample user mappings in between Placetel and Zammad" +#: ../settings/ticket.rst:57 +msgid "Use the time of the very last customer article." msgstr "" -#: ../system/integrations/cti/placetel.rst:64 +#: ../settings/ticket.rst:55 msgid "" -"You can find your agents Placetel username combination required within ⚙️ PBX " -"→ VoIP destinations. Within the \"Advanced settings\" section you're looking " -"for \"SIP user name\" and \"SIP server\"." -msgstr "" - -#: ../system/integrations/cti/placetel.rst:68 -msgid "Combine these two like so: ``@``." +"When setting this option, Zammad will always update the last updated value. " +"This means that if ordering by ``Last Update``, ticket orders will change if " +"customers \"bump\" the ticket." msgstr "" -#: ../system/integrations/cti/placetel.rst:0 -msgid "Sample VoIP credentials for a Placetel user" +#: ../settings/ticket.rst:64 +msgid "Last contact value used on :doc:`/manage/overviews`" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:2 -msgid "Setup Placetel connection for Zammad" +#: ../settings/ticket.rst:65 +msgid "Last contact value used on :doc:`/manage/trigger`" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:6 +#: ../settings/ticket.rst:88 msgid "" -"This configuration step requires a *full* administrative Placetel account. " -"You may receive forbidden error messages with Placetel in case your " -"permissions are not high enough." +"Ticket Organization Reassignment (default: ``Update the most recent tickets." +"``)" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:10 +#: ../settings/ticket.rst:68 msgid "" -"The following actions can be configured via the `Placetel web interface " -"`_." +"This setting changes the way Zammad updates the organization field of the " +"tickets whenever the primary organization of a user is changed." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:29 -msgid "Step 1: Activate Zammad integration" +#: ../settings/ticket.rst:74 +msgid "Update the most recent tickets." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:14 +#: ../settings/ticket.rst:72 msgid "" -"Within Integrations, scroll down to Partner integrations and select Zammad." +"If this option is chosen, Zammad will update the 100 most recent tickets " +"where the user is the ticket customer. The ticket organization field will be " +"automatically set to the new primary organization of the user." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:17 +#: ../settings/ticket.rst:88 +#, fuzzy +msgid "Do not update any tickets." +msgstr "biletleri günceller" + +#: ../settings/ticket.rst:77 msgid "" -"You can alternatively filter by \"Ticket Systems\" to reduce the number of " -"entries on the page. You'll still want to look for Partner integrations. 🤓" +"When choosing this option, Zammad will not update any tickets when the " +"user's primary organization is changed." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:21 -msgid "" -"Within the Zammad integration now press \"Activate\". A new tab ``API`` " -"becomes available - open this tab." +#: ../settings/ticket.rst:80 +msgid "**Use with care!**" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:24 +#: ../settings/ticket.rst:82 msgid "" -"Now tick \"Enable Call Control / Notify API\" and paste the Placetel " -"endpoint from your Zammad instance into the field \"URL of your API " -"endpoint\". Save to apply the settings" +"Using this option may lead to inconsistencies in the system as the ticket " +"organization may become decoupled from the ticket customer." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 -msgid "Screencast showing how to activate the Zammad integration" +#: ../settings/ticket.rst:85 +msgid "" +"However, you may use this option if you wish to maintain :ref:`the shared " +"access ` to the ticket for all organization " +"members of the original organization of the customer." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:51 -msgid "Step 2: Generate API Token for Placetel" +#: ../settings/ticket.rst:110 +msgid "Ticket Number Format (default: ``Increment (SystemID.Counter)``)" +msgstr "Bilet Numarası Formatı (varsayılan: ``Artış (SystemID.Counter)``)" + +#: ../settings/ticket.rst:94 +msgid "" +"This setting defines the way Zammad's ticket number will look. Changing this " +"setting in production will cause follow up detection to fail." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:32 +#: ../settings/ticket.rst:102 +msgid "Increment (SystemID.Counter)" +msgstr "Artış (SystemID.Counter)" + +#: ../settings/ticket.rst:98 msgid "" -"Go back to the integrations page and scroll down to \"Web API\". Generate a " -"new API token by using the \"Create a new API token\" button." +"The increment value contains the SystemID (automatically generated during " +"installation) and a increment which counts up with every new Ticket. The " +"increment will automatically get another digit if needed." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:37 +#: ../settings/ticket.rst:102 +msgid "Examples: ``1010138``, ``1010139``" +msgstr "Örnekler: ``1010138``, ``1010139``" + +#: ../settings/ticket.rst:110 +msgid "Date (Year.Month.Day.SystemID.Counter)" +msgstr "Tarih (Year.Month.Day.SystemID.Counter)" + +#: ../settings/ticket.rst:105 msgid "" -"If you already generated a token either use your existing token or reset it " -"by using above mentioned button. Placetel will ask you to conform this reset." +"This version of the ticket number is fairly long. However, because it " +"contains the date of ticket creation, it also allows you to see when the " +"ticket has been created. You may feel familiar with this number format if " +"you've worked with OTRS already." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:41 +#: ../settings/ticket.rst:110 +msgid "Examples: ``201206231010138``, ``201206231010139``" +msgstr "Örnekler: ``201206231010138``, ``201206231010139``" + +#: ../settings/ticket.rst:137 +msgid "OPTIONS" +msgstr "SEÇENEKLER" + +#: ../settings/ticket.rst:113 msgid "" -"Please keep in mind that existing API scripts may no longer work due to " -"token resets!" +"The below options allow you to further customize your ticket number. The " +"availability of options differ depending of the chosen ticket number format " +"above." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:44 -msgid "" -"Copy the provided API token and insert it into the \"API Token\" field " -"within Zammad's Placetel integration." +#: ../settings/ticket.rst:122 +msgid "Checksum (default: ``no``)" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:47 +#: ../settings/ticket.rst:118 msgid "" -"Apply your changes by using the \"Save\" button on the bottom of the " -"Placetel integration page and activate the Placetel integration." +"If set to yes, we'll built a checksum to further \"unique\" the ticket " +"number of your system. If you're dealing with many other ticket systems this " +"might help to prevent false positive follow up detection on tickets." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 -msgid "" -"Screencast showing how to retrieve an API token from Placetel for Zammad" +#: ../settings/ticket.rst:122 +msgid "This will also add another digit to the ticket number." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:73 -#: ../system/integrations/cti/provider-configurations/sipgate.rst:77 -msgid "Step 3: Restrict the numbers to notify on" +#: ../settings/ticket.rst:137 +msgid "Min. size of Number (default: ``5``)" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:54 +#: ../settings/ticket.rst:125 msgid "" -"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " -"the the Integrations page of the Placetel web interface, go to \"Notify " -"API\"." +"This setting defines the minimum length of your ticket number. If your " +"counter is not yet high enough, Zammad will fill the number with zeros to " +"ensure the wanted length." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:58 +#: ../settings/ticket.rst:129 msgid "" -"Lower on the page Placetel allows you to restrict the numbers to notify on. " -"You'll find this within the \"External routing API\" part." +"Please note that the minimum length is ``3`` (SystemID + at least one digit " +"if below 10). Also, if the length is no longer long enough, the number will " +"automatically get one digit longer. Ticket-Numbers **do not overflow**, thus " +"it's save to keep it at 5 or set it lower if wanted." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +#: ../settings/ticket.rst:135 msgid "" -"Screenshot showing a sample selection of phone numbers to use for the " -"Placetels notify API" +"This option is only available if ticket number format is set to " +"``Increment``!" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:66 -msgid "" -"This menu point also provides a API request log from Placetel view. Just " -"open \"Recent responses of your API endpoint\" to learn more." -msgstr "" +#: ../settings/ticket.rst:142 +msgid "Auto-Assignment" +msgstr "Otomatik Atama" -#: ../system/integrations/cti/provider-configurations/placetel.rst:69 +#: ../settings/ticket.rst:144 msgid "" -"If you want to see Zammad's perspective, use the \"Recent Logs\" part from " -"within the Placetel integration page." -msgstr "" - -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 -msgid "Screenshot showing sample log entries for Placetels API calls to Zammad" -msgstr "" - -#: ../system/integrations/cti/provider-configurations/placetel.rst:77 -msgid "Step 4 (optional): Further configurations for Placetel" +"In a larger Zammad environment, it happens that several agents open the same " +"ticket at the same time. Although collision detection is then effective, the " +"efficiency of processing can be increased by means of the automatic " +"assignment of tickets when a ticket is opened." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:76 +#: ../settings/ticket.rst:149 msgid "" -"If needed, you can now configure Zammad's Placetel integration in more " -"detail. You can learn more about your options here: :ref:`Placetel " -"integration settings `." +"The automatic assignment of tickets can be activated and configured in the " +"admin area under Settings > Ticket > Auto Assignment." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:2 -msgid "Setup Sipgate connection for Zammad" +#: ../settings/ticket.rst:152 +msgid "" +"The auto assignment only works if the ticket has no owner yet. By default, " +"the agent can always reset the ticket owner to ``-`` if needed." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +#: ../settings/ticket.rst:155 msgid "" -"Sipgate has no english web interface which is why this documentation page is " -"mixing up languages badly." +"If you want to use this function for only specific tickets, you can " +"configure the conditions accordingly to meet your requirement. By default " +"the condition affects all tickets with the state ``open``." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +#: ../settings/ticket.rst:161 msgid "" -"Please also note that the availability of API addons highly depends on your " -"package trier. Usage of sipgate.io packages *is not free*, please check " -"their `pricing page `_ before!" +"If you need to exclude users (e.g. a group leader), you can search and " +"select the desired agents in the ``Exception Users`` list. The search " +"function in this area is only effective, if you have too many agents to " +"display at once to help you with the configuration." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:35 -msgid "Step 1: Book sipgate.io package" -msgstr "" +#: ../settings/ticket.rst:167 +#, fuzzy +msgid "Notifications" +msgstr "Bildirimleri Engelle" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:13 -msgid "Skip to step 2 if you already have the package booked!" -msgstr "" +#: ../settings/ticket.rst:191 +#, fuzzy +msgid "Default Notifications" +msgstr "E-posta Bildirimi" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:15 +#: ../settings/ticket.rst:170 msgid "" -"Login to an administrative Sipgate account and navigate to " -"``Accountverwaltung``. You'll see several different options depending on " -"your booked packages. Select ``Verträge & Produkte`` to continue." +"This setting allows you to configure the default ticket notifications that " +"will be applied to all new agent users (incl. users who were just assigned " +"agent role). Simply change the notification matrix to desired state and " +"press **Save**." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:19 +#: ../settings/ticket.rst:175 msgid "" -"Scroll down to the section ``Zusätzliche Produkte buchen`` and look for " -"``sipgate.io`` - select this product by using the ``Produkte anzeigen``-" -"Button." +"In case an agent already exists, their ticket notification preferences will " +"be preserved. Optionally, you can also **Apply current defaults to all " +"agents**." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:23 +#: ../settings/ticket.rst:181 msgid "" -"On the next page select either one of the ``sipgate.io`` packages or ``Push-" -"API Package Free``. Follow the dialogue by booking the addon. You'll be " -"returned to your contract overview and now should see the selected addon in " -"your list." +"**Potential time-consuming action:** Applying default ticket notifications " +"to all agent users may take some time to complete, be patient! The exact " +"time will depend on the size of your system and the number of agents." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:30 +#: ../settings/ticket.rst:185 msgid "" -"The availability for ``sipgate.io`` packages and their levels highly depends " -"on the overall account type and product you've booked with Sipgate." +"**Active agents only!** When current default ticket notifications are " +"applied, only active agent users are considered. In case an agent is re-" +"activated *after* this action, they will still have the old notification " +"configuration." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +#: ../settings/ticket.rst:190 msgid "" -"Screencast showing the process on how to book the required sipgate.io addon" +"In case you want to go back to the initial state of ticket notifications, " +"you can click on **Reset to default** button." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:52 -msgid "Step 2: Configure webhook for Zammad" -msgstr "" +#: ../settings/ticket.rst:196 +#, fuzzy +msgid "Duplicate Detection" +msgstr "Uygulama açıklaması" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:38 -msgid "" -"Within your ``Accountverwaltung`` navicate to your product ``sipgate.io``. " -"In the newly opened tab, switch from \"Clients\" to \"Webhooks\" and paste " -"the endpoint URLs from your Zammad instance like so:" -msgstr "" +#: ../settings/ticket.rst:238 +#, fuzzy +msgid "Detect Duplicate Ticket Creation" +msgstr "Bilet oluşturulduğunda" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:42 -msgid "Inbound endpoint to \"Incoming\"" +#: ../settings/ticket.rst:199 +msgid "" +"This setting turns on the duplicate ticket detection mechanism during ticket " +"creation. If similar tickets are found in the system, a suitable warning " +"will be shown to the user trying to create a ticket." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:43 -msgid "Outbound endpoint to \"Outgoing\"" +#: ../settings/ticket.rst:206 +msgid "A Sample Duplicate Ticket Warning" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:47 +#: ../settings/ticket.rst:208 msgid "" -"Ensure to select at least one call group or phoneline within \"Sources\". " -"Other wise Sipgate will not indicate any incoming or outgoing calls to " -"Zammad." +"You can choose which ticket attributes will be matched by selecting them in " +"**Attributes to compare** field. Only if the ticket attribute value provided " +"by the user in the ticket create form is *equal* with the attribute in an " +"existing ticket, the warning will be shown." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screencast showing how to add Zammad's endpoint URLs to sipgate.ios webhook " -"configuration" +#: ../settings/ticket.rst:213 +msgid "**Warning title** and **Warning message** are configurable as well." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:55 +#: ../settings/ticket.rst:215 msgid "" -"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " -"the Webhooks → URLs section of Sipgate you can select which *sources* " -"Sipgate should notify Zammad about in- and outgoing calls." +"You can limit the detection only to certain user roles. By default, only " +"agents will see the warning." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:59 +#: ../settings/ticket.rst:218 msgid "" -"Use either specific phone lines or use the option \"Use for all phonelines " -"and groups\" to notify Zammad about all existing lines of your Sipgate " -"account." +"If you don't want to show the matched tickets as part of the warning, you " +"can set **Show matching ticket(s) in the warning** setting to *no*." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +#: ../settings/ticket.rst:221 msgid "" -"Screenshot showing a sample selection of phone numbers to use for the " -"Sipgates webhooks API" -msgstr "" - -#: ../system/integrations/cti/provider-configurations/sipgate.rst:68 -msgid "This section also allows you to enable a Debug log." +"By default, **Permission level for looking up ticket** is set to *User*, " +"which means user permissions will be honored during sarch. The user will " +"see the warning only if tickets they have access to are matched. " +"Alternatively, you can set this setting to *System*, in which case the " +"search will happen within *all* tickets in the system, regardless of user " +"permissions." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "Screenshot showing an enabled Debug log option" +#: ../settings/ticket.rst:227 +msgid "**🦺 Safety first!**" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:73 +#: ../settings/ticket.rst:229 msgid "" -"After enabling you can use the Debug log section to see all sent webhook " -"calls to Zammad. You'll also can see the response." +"Even if the permission level is set to *System*, the user will not be shown " +"the tickets they don't have access to in the warning, even if they match." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +#: ../settings/ticket.rst:233 msgid "" -"Screenshot showing sample log entries for Sipgates webhook calls to Zammad" -msgstr "" - -#: ../system/integrations/cti/provider-configurations/sipgate.rst:81 -msgid "Step 4 (optional): Further configurations for Sipgate" +"However, just the confirmation about the existence of the tickets in the " +"system may be considered an unwanted information disclosure. Use this option " +"carefully!" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:80 +#: ../settings/ticket.rst:237 msgid "" -"If needed, you can now configure Zammad's Sipgate integration in more " -"detail. You can learn more about your options here: :ref:`Sipgate " -"integration settings `." +"Finally, you can configure between matching within **All tickets** or **Open " +"tickets** only by setting **Match tickets in following states**. Depending " +"on the current ticket state, a ticket may or not be matched." msgstr "" -#: ../system/integrations/cti/sipgate.rst:2 -msgid "Sipgate (sipgate.io)" +#: ../system/core-workflows.rst:2 +msgid "Core Workflows" msgstr "" -#: ../system/integrations/cti/sipgate.rst:16 -#, fuzzy -msgid "You need an administrative Sipgate account for your organization." -msgstr "🔑 **Organizasyonunuz için bir yönetici hesabı kullanın.**" - -#: ../system/integrations/cti/sipgate.rst:17 +#: ../system/core-workflows.rst:4 msgid "" -"Zammad requires a ``sipgate.io`` addon from the feature store (please note " -"that API calls are not free with Sipgate. Rates may apply and differ from " -"account to account)." +"Core Workflows allow you to adjust object attributes in many ways. For " +"example:" msgstr "" -#: ../system/integrations/cti/sipgate.rst:21 -msgid "Sipgate must be able to reach your Zammad instance." +#: ../system/core-workflows.rst:7 +msgid "show / hide fields" msgstr "" -#: ../system/integrations/cti/sipgate.rst:25 -msgid ":doc:`provider-configurations/sipgate`" +#: ../system/core-workflows.rst:8 +msgid "adjust mandatory setting" msgstr "" -#: ../system/integrations/cti/sipgate.rst:24 -msgid "" -"Learn how to configure Sipgate to enable Zammad and Sipgate to communicate " -"with each other." +#: ../system/core-workflows.rst:9 +msgid "manipulate available options" msgstr "" -#: ../system/integrations/cti/sipgate.rst:33 +#: ../system/core-workflows.rst:11 msgid "" -"Below endpoint settings affect the :doc:`sipgate.io configuration `." +"With this, you can provide exactly the information your users really need!" msgstr "" -#: ../system/integrations/cti/sipgate.rst:37 -msgid "This endpoint is required for incoming call hooks." +#: ../system/core-workflows.rst:15 +msgid "" +"If the pre-defined :doc:`/system/objects` are not enough, please add them " +"beforehand." msgstr "" -#: ../system/integrations/cti/sipgate.rst:40 -#, fuzzy -msgid "This endpoint is required for outgoing call hooks." -msgstr "Giden e-posta için kullanılan görünen ad." - -#: ../system/integrations/cti/sipgate.rst:0 -msgid "Screenshot showing sample user mappings in between Sipgate and Zammad" +#: ../system/core-workflows.rst:17 +msgid "" +"If you experience slow or unreliable field updates, please see :ref:`Core " +"Workflow Ajax Modus `" msgstr "" -#: ../system/integrations/cti/sipgate.rst:69 +#: ../system/core-workflows.rst:22 msgid "" -"You can find your agent's Sipgate username within ``Accountverwaltung → " -"Benutzer``. You're looking for the SIP-ID." +"This is a very enhanced functionality and can cause unexpected UI behavior. " +"Please ensure to test your use cases after configuration to reduce surprises." msgstr "" -#: ../system/integrations/cti/sipgate.rst:0 -msgid "Sample VoIP credentials for a Sipgate user" +#: ../system/core-workflows.rst:None +msgid "Dialogue for adding a new workflow" msgstr "" -#: ../system/integrations/cti/sipgate.rst:77 -msgid "Users with several devices also have several SIP-IDs." +#: ../system/core-workflows/condition-operators.rst:2 +msgid "Core Workflow Condition Operators" msgstr "" -#: ../system/integrations/elasticsearch.rst:2 -msgid "Elasticsearch (SaaS)" +#: ../system/core-workflows/condition-operators.rst:4 +msgid "" +"You might know that there is a separate section for explaining :doc:" +"`condition operators `. Head over there to " +"see a detailed explanation of many conditions and operators." msgstr "" -#: ../system/integrations/elasticsearch.rst:4 +#: ../system/core-workflows/condition-operators.rst:8 msgid "" -"The Elasticsearch integration allows you to create a read-only user to use " -"with your favorite reporting tool (e.g. like Grafana)." +"Due to differences to other places in Zammad which are also using conditions " +"(e.g. triggers), you can find a dedicated description of operators for core " +"workflows below." msgstr "" -#: ../system/integrations/elasticsearch.rst:7 +#: ../system/core-workflows/condition-operators.rst:12 msgid "" -"If you want to take full advantage of the Zammad reporting, have a look at " -"our :docs:`Grafana ` " -"setup page as well." +"Be aware that the availability of the operators depends on the selected " +"attribute and its field type. Some of the operators may only be available " +"for system attributes (e.g. for \"tags\", \"active\")." msgstr "" -#: ../system/integrations/elasticsearch.rst:11 -#: ../system/subscription/index.rst:7 -msgid "**🚧 Hosted environment specific 🚧**" +#: ../system/core-workflows/condition-operators.rst:20 +msgid "Operator" msgstr "" -#: ../system/integrations/elasticsearch.rst:13 -msgid "" -"This integration is only available for Hosted setups. In order to use " -"Elasticsearch you'll need the **Plus** subscription." +#: ../system/core-workflows/condition-operators.rst:22 +msgid "after (absolute)" msgstr "" -#: ../system/integrations/elasticsearch.rst:16 -msgid "" -"Self hosted users have all the control over their self hosted Elasticsearch " -"instances." +#: ../system/core-workflows/condition-operators.rst:23 +msgid "Matches if a date/time is after a specific point in time." msgstr "" -#: ../system/integrations/elasticsearch.rst:None -msgid "Elasticsearch integration page on SaaS environments" +#: ../system/core-workflows/condition-operators.rst:24 +msgid "after (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:27 -msgid "" -"Please note the following limitations of Elasticsearch access on hosted " -"environments:" +#: ../system/core-workflows/condition-operators.rst:25 +msgid "Matches if a time span after a specified event has passed." msgstr "" -#: ../system/integrations/elasticsearch.rst:30 -msgid "access to the Elasticsearch index is read-only access" +#: ../system/core-workflows/condition-operators.rst:26 +msgid "before (absolute)" msgstr "" -#: ../system/integrations/elasticsearch.rst:31 -msgid "currently you're limited to user only" +#: ../system/core-workflows/condition-operators.rst:27 +msgid "Matches if a date/time is before a specific point in time." msgstr "" -#: ../system/integrations/elasticsearch.rst:32 -msgid "" -"Reporting tools that require to write into the indexes (like Kibana) are not " -"supported" +#: ../system/core-workflows/condition-operators.rst:28 +msgid "before (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:34 -msgid "IP access restriction is currently not yet supported" +#: ../system/core-workflows/condition-operators.rst:29 +msgid "Matches if a time span after a specified event has not passed." msgstr "" -#: ../system/integrations/elasticsearch.rst:37 -msgid "Activating Elasticsearch Access" +#: ../system/core-workflows/condition-operators.rst:30 +#, fuzzy +msgid "contains" +msgstr "İletişim" + +#: ../system/core-workflows/condition-operators.rst:31 +msgid "Matches if a specified value is present." msgstr "" -#: ../system/integrations/elasticsearch.rst:39 -msgid "" -"By default external access to your Elasticsearch index is not active. You " -"can enable the integration at any time if needed." +#: ../system/core-workflows/condition-operators.rst:33 +msgid "Matches if all of the specified values are present." msgstr "" -#: ../system/integrations/elasticsearch.rst:42 -msgid "" -"Please ensure to note down the password provided - you won't have access to " -"it afterwards." +#: ../system/core-workflows/condition-operators.rst:35 +msgid "Matches if none of the specified values are present." msgstr "" -#: ../system/integrations/elasticsearch.rst:None -msgid "Screencast showing activation of Elasticsearch integration" +#: ../system/core-workflows/condition-operators.rst:36 +msgid "contains not" msgstr "" -#: ../system/integrations/elasticsearch.rst:51 -msgid "Connection Settings" +#: ../system/core-workflows/condition-operators.rst:37 +msgid "Matches if a specified value is not present." msgstr "" -#: ../system/integrations/elasticsearch.rst:53 -msgid "" -"This section holds the most important general information for accessing your " -"Elasticsearch indexes - such as:" +#: ../system/core-workflows/condition-operators.rst:39 +msgid "Matches if one specified value is present." msgstr "" -#: ../system/integrations/elasticsearch.rst:57 -msgid "A unique subdomain that does not tell your real instance URL." +#: ../system/core-workflows/condition-operators.rst:41 +msgid "Matches if one specified value is not present." msgstr "" -#: ../system/integrations/elasticsearch.rst:61 -msgid "Software" +#: ../system/core-workflows/condition-operators.rst:42 +msgid "does not match regex" msgstr "" -#: ../system/integrations/elasticsearch.rst:60 -msgid "" -"The major version of the search index being used. This is required by some " -"Reporting tools like Grafana." +#: ../system/core-workflows/condition-operators.rst:43 +msgid "Matches if content doesn't fit to regex rule." msgstr "" -#: ../system/integrations/elasticsearch.rst:64 -msgid "Authentication" +#: ../system/core-workflows/condition-operators.rst:44 +msgid "ends with" msgstr "" -#: ../system/integrations/elasticsearch.rst:64 -msgid "The authentication type being supported. ``Basic Authentication``" +#: ../system/core-workflows/condition-operators.rst:45 +msgid "Matches if content ends with specified value." msgstr "" -#: ../system/integrations/elasticsearch.rst:67 -msgid "Available Indexes" +#: ../system/core-workflows/condition-operators.rst:46 +msgid "ends with one of" msgstr "" -#: ../system/integrations/elasticsearch.rst:69 -msgid "" -"Within this section we're displaying the -in our opinion- most important " -"indexes for a Zammad instance." +#: ../system/core-workflows/condition-operators.rst:47 +msgid "Matches if content ends with one of the specified values." msgstr "" -#: ../system/integrations/elasticsearch.rst:72 -msgid "" -"If you require all indexes or our listing is not good enough for you, point " -"your browser to the URL we're providing and append ``/_aliases?" -"pretty=true``. The result should look like this: ``https://.zammad.com/" -"_aliases?pretty=true``." +#: ../system/core-workflows/condition-operators.rst:48 +msgid "from (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:77 -msgid "" -"Your browser will automatically ask for your credentials - you'll then see " -"something like this:" +#: ../system/core-workflows/condition-operators.rst:49 +msgid "Matches if date/time is after a period of time after an event." msgstr "" -#: ../system/integrations/elasticsearch.rst:125 -msgid "Credentials" +#: ../system/core-workflows/condition-operators.rst:51 +msgid "Matches if content is equal to a specified value." msgstr "" -#: ../system/integrations/elasticsearch.rst:127 -msgid "" -"Within this section Zammad displays your available users. The password is " -"provided once (upon activation) and cannot be retrieved after that." +#: ../system/core-workflows/condition-operators.rst:52 +msgid "is any of" msgstr "" -#: ../system/integrations/elasticsearch.rst:131 -msgid "" -"If you need to change or reset your Elasticsearch user password, use the " -"\"Reset password\" button in the credentials table. Doing so creates a brand " -"new password for the account in question. This change is immediate, keep in " -"mind that this may affect third party tools connected to your instance." +#: ../system/core-workflows/condition-operators.rst:53 +msgid "Matches if content is equal to any of specified values." msgstr "" -#: ../system/integrations/exchange.rst:2 -msgid "Exchange" -msgstr "Exchange" +#: ../system/core-workflows/condition-operators.rst:54 +msgid "is modified" +msgstr "" -#: ../system/integrations/exchange.rst:4 -msgid "" -"With Zammad's Exchange integration, you can easily use existing address " -"books without having to update more than one source." +#: ../system/core-workflows/condition-operators.rst:55 +msgid "Matches if content is modified." msgstr "" -#: ../system/integrations/exchange.rst:7 -msgid "" -"However, you should refrain from syncing all addresses, as the results may " -"not be what you expect (Exchange collects huge amounts of addresses). A " -"central address book of your company to sync makes more sense, as you can " -"ensure that Zammad gets only the data you need and want. Apart from this, it " -"is even not possible to sync the Global Address List (GAL) of your Exchange " -"system with Zammad." +#: ../system/core-workflows/condition-operators.rst:57 +#: ../system/core-workflows/condition-operators.rst:61 +msgid "True from the moment of changing content until form submit." msgstr "" -#: ../system/integrations/exchange.rst:16 -msgid "" -"**Exchange and LDAP:** The exchange sync can be overruled by Zammad's LDAP " -"integration. If you have the same users in both sources, the LDAP version " -"will always be Zammad's pick." +#: ../system/core-workflows/condition-operators.rst:58 +msgid "is modified to" msgstr "" -#: ../system/integrations/exchange.rst:19 -msgid "" -"**One way sync:** the Exchange sync is one way. Exchange => Zammad. Changes " -"to your users inside of Zammad might be overwritten by the Exchange sync." +#: ../system/core-workflows/condition-operators.rst:59 +msgid "Matches if content is modified to a specific value." msgstr "" -#: ../system/integrations/exchange.rst:24 -msgid "" -"To configure Exchange integration, simply go to the System > Integrations > " -"Exchange in the admin panel. Press \"change\" and follow the wizard for " -"adding the needed Exchange information to Zammad. On the last two steps " -"Zammad will ask you for the address book(s) and your desired attribute " -"mapping. By default, Zammad only maps email address, first- and lastname. " -"Technically, you can map any Exchange object to a Zammad user object (this " -"also works for custom objects!)." +#: ../system/core-workflows/condition-operators.rst:62 +msgid "is none of" msgstr "" -#: ../system/integrations/exchange.rst:35 -msgid "" -"If the SSL verification fails while connecting to Exchange, Zammad will ask " -"you to turn it off temporarily." +#: ../system/core-workflows/condition-operators.rst:63 +msgid "Matches if content is none of any specified values." msgstr "" -#: ../system/integrations/exchange.rst:38 -msgid "" -"Please be aware that **turning off SSL verification is a security risk**. It " -"should only be used temporarily or for testing purposes. If turned off, " -"there is no verification of the certificate, which means that every " -"presented certificate will be accepted." +#: ../system/core-workflows/condition-operators.rst:65 +msgid "Matches if content is not equal to a specified value." msgstr "" -#: ../system/integrations/exchange.rst:43 -msgid "" -"After pressing Continue, Zammad will check if the configuration is okay. You " -"can then enable Exchange and start your first sync. The sync will then run " -"hourly - if you need to change mappings or the address book(s), you can " -"change the configuration at any time." +#: ../system/core-workflows/condition-operators.rst:67 +msgid "Matches if content is present." msgstr "" -#: ../system/integrations/exchange.rst:50 -msgid "" -"After the sync has finished, you can find the new Exchange contacts under " -"\"Users\". Zammad integrates them just as normal users." -msgstr "" +#: ../system/core-workflows/condition-operators.rst:68 +#, fuzzy +msgid "just changed" +msgstr "Exchange" -#: ../system/integrations/exchange.rst:55 -msgid "" -"In some cases you might see unique IDs as \"Login\" instead of the email " -"address. This is normal and doesn't affect the login or email mapping for " -"that entry." +#: ../system/core-workflows/condition-operators.rst:69 +msgid "Matches if content has changed." msgstr "" -#: ../system/integrations/github.rst:4 +#: ../system/core-workflows/condition-operators.rst:71 +#: ../system/core-workflows/condition-operators.rst:75 msgid "" -"Use GitHub integration to track GitHub issues directly within Zammad " -"tickets. Add issue hyperlinks and get a live summary of metadata like status " -"(open/closed), assignee, labels, and more." +"Only true for the moment of changing content until next form field action/" +"click." msgstr "" -#: ../system/integrations/github.rst:8 -msgid "Please note that our GitHub integration does not support pull requests." +#: ../system/core-workflows/condition-operators.rst:72 +msgid "just changed to" msgstr "" -#: ../system/integrations/github.rst:None -msgid "Integration page for GitHub" +#: ../system/core-workflows/condition-operators.rst:73 +msgid "Matches if content has changed to a specified value." msgstr "" -#: ../system/integrations/github.rst:18 -msgid "" -"In your GitHub settings, create a new API token under **Developer settings > " -"Personal access tokens > Generate new token**. Leave the **Scopes** section " -"empty." +#: ../system/core-workflows/condition-operators.rst:76 +msgid "matches regex" msgstr "" -#: ../system/integrations/github.rst:0 ../system/integrations/gitlab.rst:0 -msgid "Screencast showing how to create a new API token" +#: ../system/core-workflows/condition-operators.rst:77 +msgid "Matches if value fits to regex rule." msgstr "" -#: ../system/integrations/github.rst:27 -msgid "Create a new API key with no scopes/privileges." +#: ../system/core-workflows/condition-operators.rst:79 +msgid "Matches if no content is present." msgstr "" -#: ../system/integrations/github.rst:29 -msgid "🔒 **Will this work for private repos?**" +#: ../system/core-workflows/condition-operators.rst:80 +msgid "starts with" msgstr "" -#: ../system/integrations/github.rst:31 -msgid "" -"No. To link private repo issues, **use the** ``repo`` **scope instead**. " -"Bear in mind that the resulting token will have `lots of permissions that it " -"doesn't actually need `_, which presents a security risk if your token ever falls into " -"the wrong hands." +#: ../system/core-workflows/condition-operators.rst:81 +msgid "Matches if content starts with specified value." msgstr "" -#: ../system/integrations/github.rst:37 -msgid "" -"Unfortunately, because of how GitHub's OAuth token scopes are set up, this " -"is the only way to link issues on private repos." +#: ../system/core-workflows/condition-operators.rst:82 +msgid "starts with one of" msgstr "" -#: ../system/integrations/github.rst:40 -msgid "Enter your new API token in Zammad and enable GitHub integration." +#: ../system/core-workflows/condition-operators.rst:83 +msgid "Matches if content starts with one of the specified values." msgstr "" -#: ../system/integrations/github.rst:0 -msgid "Screencast showing how to configure Zammad's GitHub integration" +#: ../system/core-workflows/condition-operators.rst:84 +msgid "till (relative)" msgstr "" -#: ../system/integrations/github.rst:47 -msgid "" -"Use the default API endpoint (``https://api.github.com/graphql``) unless " -"you're using GitHub Enterprise Server." +#: ../system/core-workflows/condition-operators.rst:85 +msgid "Matches if date/time is before a period of time before an event." msgstr "" -#: ../system/integrations/github.rst:50 -msgid "" -"Once completed, a new GitHub issues tab will appear in the ticket pane. 🎉" +#: ../system/core-workflows/condition-operators.rst:86 +msgid "today" msgstr "" -#: ../system/integrations/github.rst:59 ../system/integrations/gitlab.rst:52 -msgid "Token verification is taking a long time" +#: ../system/core-workflows/condition-operators.rst:87 +msgid "Matches if date/time is today." msgstr "" -#: ../system/integrations/github.rst:56 ../system/integrations/gitlab.rst:49 -msgid "" -"Slight delays are normal (<2 min.), especially for systems under heavy load." +#: ../system/core-workflows/condition-operators.rst:88 +msgid "within last (relative)" msgstr "" -#: ../system/integrations/github.rst:58 +#: ../system/core-workflows/condition-operators.rst:89 msgid "" -"Self-hosted administrators, please check your network settings to ensure " -"that your Zammad server can reach ``api.github.com``." +"Matches if date/time content is within specified period of time before now." msgstr "" -#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 -msgid "I reloaded the page and now the API token is gone" +#: ../system/core-workflows/condition-operators.rst:91 +msgid "within next (relative)" msgstr "" -#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 +#: ../system/core-workflows/condition-operators.rst:92 msgid "" -"This may indicate that Zammad is still verifying your API token. Try " -"reloading the page again in a couple minutes." +"Matches if date/time content is within specified period of time after now." msgstr "" -#: ../system/integrations/gitlab.rst:2 -msgid "GitLab" -msgstr "GitLab" +#: ../system/core-workflows/how-do-they-work.rst:2 +msgid "How do they work?" +msgstr "Nasıl çalışırlar?" -#: ../system/integrations/gitlab.rst:4 +#: ../system/core-workflows/how-do-they-work.rst:4 msgid "" -"Use GitLab integration to track GitLab issues directly within Zammad " -"tickets. Add issue hyperlinks and get a live summary of metadata like status " -"(open/closed), assignee, labels, and more." +"Core Workflows are executed according to their priority. If two workflows " +"have the same priority, they are executed in alphabetical order based on " +"their **name**." msgstr "" -#: ../system/integrations/gitlab.rst:8 +#: ../system/core-workflows/how-do-they-work.rst:8 msgid "" -"Please note that our GitLab integration does not support merge requests." -msgstr "" - -#: ../system/integrations/gitlab.rst:None -msgid "Integration page for GitLab" +"Because of the way Core Workflows work, all changes to attributes are " +"checked with the application server - please see :doc:`limitations` for " +"possible issues." msgstr "" -#: ../system/integrations/gitlab.rst:18 +#: ../system/core-workflows/how-do-they-work.rst:12 msgid "" -"In your GitLab preferences, create a new API token under **Access Tokens**." +"Below we're talking about settings that are important and not self-" +"explanatory." msgstr "" -#: ../system/integrations/gitlab.rst:20 -msgid "Under **Select scopes**, choose ``read_api`` only." +#: ../system/core-workflows/how-do-they-work.rst:17 +msgid "" +"Choose the object context you want to run the workflow in. This will decide " +"on your available attributes and actions." msgstr "" -#: ../system/integrations/gitlab.rst:27 -msgid "🔒 **If you wish to link issues on any private repos...**" +#: ../system/core-workflows/how-do-they-work.rst:20 +msgid "Ticket objects also have access to the ticket customer." msgstr "" -#: ../system/integrations/gitlab.rst:29 -msgid "Your API token must belong to an account with access to those repos." +#: ../system/core-workflows/how-do-they-work.rst:25 +msgid "" +"Choose in which situation the workflow is applied. Contexts can be combined " +"to avoid duplicate workflows." msgstr "" -#: ../system/integrations/gitlab.rst:31 -msgid "Enter your new API token in Zammad and enable GitLab integration." -msgstr "" +#: ../system/core-workflows/how-do-they-work.rst:30 +#, fuzzy +msgid "Creation mask" +msgstr "Makrolar Oluşturmak" -#: ../system/integrations/gitlab.rst:0 -msgid "Screencast showing how to configure Zammad's GitLab integration" +#: ../system/core-workflows/how-do-they-work.rst:29 +msgid "" +"If selected, your conditions and actions will affect all applicable creation " +"masks." msgstr "" -#: ../system/integrations/gitlab.rst:40 -msgid "" -"Use the default API endpoint (``https://gitlab.com/api/graphql``) unless " -"you're a self-hosted GitLab user." +#: ../system/core-workflows/how-do-they-work.rst:34 +msgid "Edit mask" msgstr "" -#: ../system/integrations/gitlab.rst:43 +#: ../system/core-workflows/how-do-they-work.rst:33 msgid "" -"Once completed, a new GitLab issues tab will appear in the ticket pane. 🎉" +"If selected, your conditions and actions will affect all applicable edit " +"masks." msgstr "" -#: ../system/integrations/gitlab.rst:51 +#: ../system/core-workflows/how-do-they-work.rst:39 msgid "" -"Self-hosted administrators, please check your network settings to ensure " -"that your Zammad server can reach ``gitlab.com``." +"Zammad differentiates between selected and saved conditions. These can be " +"combined wherever needed." msgstr "" -#: ../system/integrations/i-doit.rst:2 -msgid "i-doit" -msgstr "i-doit" - -#: ../system/integrations/i-doit.rst:4 -msgid "" -"`i-doit `_ is an open-source **configuration " -"management database** - in other words, a tool for keeping tabs on every " -"single piece of your physical and digital infrastructure, from network " -"equipment to virtual machines on down to the faceplates on your rack shelves " -"and more." +#: ../system/core-workflows/how-do-they-work.rst:42 +msgid "**⚠️ Restrict workflows to specific roles if needed!**" msgstr "" -#: ../system/integrations/i-doit.rst:10 +#: ../system/core-workflows/how-do-they-work.rst:44 msgid "" -"What's that got to do with Zammad? Well, if you used tickets to track issues " -"with all that hardware, you might start wishing there was a way they could " -"talk to each other." +"By default and unless configured in conditions, workflow rules are executed " +"for **all roles**. This also affects your customers!" msgstr "" -#: ../system/integrations/i-doit.rst:14 -msgid "Zammad gives you two:" +#: ../system/core-workflows/how-do-they-work.rst:50 +msgid "Selected Conditions" msgstr "" -#: ../system/integrations/i-doit.rst:17 -msgid "1. Add i-doit Links to Zammad Tickets" +#: ../system/core-workflows/how-do-they-work.rst:48 +msgid "" +"These conditions are based on form values and match if an appropriate " +"selection is made (e.g. choosing another group in the ticket without " +"saving). This applies for drafts (active selection) and currently saved " +"values." msgstr "" -#: ../system/integrations/i-doit.rst:20 ../system/integrations/i-doit.rst:80 -msgid "What Users See" +#: ../system/core-workflows/how-do-they-work.rst:64 +msgid "Saved Conditions" msgstr "" -#: ../system/integrations/i-doit.rst:26 -msgid "i-doit integration in Zammad's ticket pane" +#: ../system/core-workflows/how-do-they-work.rst:53 +msgid "" +"These conditions only match if the selected values are stored in the " +"database. It ignores the current value or selection of the field, as long as " +"the changes are not saved (e.g. performing field operations for an existing " +"ticket, which is viewed/opened by an agent)." msgstr "" -#: ../system/integrations/i-doit.rst:26 +#: ../system/core-workflows/how-do-they-work.rst:60 msgid "" -"The i-doit integration will appear under a new 🖨 tab in the ticket pane." +"Keep in mind that the value has to be available in the situation where you " +"need it. Otherwise the condition won't match." msgstr "" -#: ../system/integrations/i-doit.rst:28 +#: ../system/core-workflows/how-do-they-work.rst:63 msgid "" -"i-doit integration puts a new tab in Zammad's ticket pane where you can add " -"links to existing i-doit devices for easy reference. (See our :user-docs:" -"`user documentation ` to learn " -"how it works in practice)." +"Example: you can't perform any actions with *saved condition* on a ticket in " +"creation, because there are no saved values at that time." msgstr "" -#: ../system/integrations/i-doit.rst:36 ../system/integrations/i-doit.rst:93 -#, fuzzy -msgid "How to Set it Up" -msgstr "Nasıl etiketlenir" - -#: ../system/integrations/i-doit.rst:38 +#: ../system/core-workflows/how-do-they-work.rst:66 msgid "" -"It requires i-doit's `API Add-on `_. Make sure to have it properly set up. Use the following setting:" +"You can find a description of the condition operators for core workflows :" +"doc:`here `." msgstr "" -#: ../system/integrations/i-doit.rst:42 -msgid "Active: ``Yes``" +#: ../system/core-workflows/how-do-they-work.rst:72 +msgid "" +"Which actions should we run on the relevant fields? The possible actions " +"depend on the object type. However, usually you can at least change the " +"visibility and whether the field is mandatory." msgstr "" -#: ../system/integrations/i-doit.rst:43 -msgid "Enforce authentication by username and password: ``No``" +#: ../system/core-workflows/how-do-they-work.rst:76 +msgid "Be aware that actions are not available for **related** context." msgstr "" -#: ../system/integrations/i-doit.rst:45 +#: ../system/core-workflows/how-do-they-work.rst:78 msgid "" -"To set it up, enable the integration in the Zammad admin panel under " -"**System > Integrations > i-doit**:" +"**Example:** Let's assume you are working in the ticket context. While you " +"can have customer *conditions*, you *can't adjust* objects with actions in " +"that scope. That's because this wouldn't have any impact on the ticket " +"dialog. Of course all ticket attributes (state, owner, ...) are available." msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "i-doit settings within the integration pages" +#: ../system/core-workflows/how-do-they-work.rst:84 +msgid "" +"Please also have a look at our :doc:`limitations` to be safe from surprises." msgstr "" -#: ../system/integrations/i-doit.rst:53 -msgid "The root URL of your i-doit installation." +#: ../system/core-workflows/how-do-they-work.rst:88 +msgid "Available Operators" msgstr "" -#: ../system/integrations/i-doit.rst:62 -msgid "API token" +#: ../system/core-workflows/how-do-they-work.rst:90 +msgid "The availability of operators depends on the object type and scope." msgstr "" -#: ../system/integrations/i-doit.rst:56 +#: ../system/core-workflows/how-do-they-work.rst:94 msgid "" -"Found in the i-doit admin panel under **Interfaces / external data > JSON-" -"RPC API > Common Settings**." +"Please note that actions may or may not restrict API based access to " +"attributes. We're displaying the following icons for your overview to " +"understand these limits better:" msgstr "" -#: ../system/integrations/i-doit.rst:0 -msgid "i-doit administration interface with API configuration" +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|api| This icon indicates the action affects the API." msgstr "" -#: ../system/integrations/i-doit.rst:67 -msgid "Client ID" +#: ../system/core-workflows/how-do-they-work.rst:163 +msgid "api" msgstr "" -#: ../system/integrations/i-doit.rst:65 -msgid "A unique name to identify Zammad within i-doit." +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|ui| This icon indicates the action only affects the web interface." msgstr "" -#: ../system/integrations/i-doit.rst:67 -msgid "(Zammad does not require you to enter a value here, but i-doit might!)" +#: ../system/core-workflows/how-do-they-work.rst:167 +msgid "ui" msgstr "" -#: ../system/integrations/i-doit.rst:70 -msgid "" -"Here you can decide if the certificate of your i-doit system has to be " -"verified or not. In case you are using custom certificates, please have a " -"look at :doc:`how to add them to Zammad `." +#: ../system/core-workflows/how-do-they-work.rst:102 +msgid "show |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:77 -msgid "2. List / Create Zammad Tickets in i-doit" +#: ../system/core-workflows/how-do-they-work.rst:102 +msgid "Display the chosen field. Allows setting of values." msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "Zammad integration in i-doit's device view" +#: ../system/core-workflows/how-do-they-work.rst:109 +msgid "hide |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:86 +#: ../system/core-workflows/how-do-they-work.rst:105 msgid "" -"i-doit's ticket system integration gives you a way to see all the tickets " -"for a given device without ever leaving i-doit. (See our :user-docs:`user " -"documentation ` to learn how it " -"works in practice)." +"Hide the chosen field. However, it technically still allows setting the " +"field." msgstr "" -#: ../system/integrations/i-doit.rst:95 +#: ../system/core-workflows/how-do-they-work.rst:108 msgid "" -"Enable this integration in the i-doit admin panel under **Interfaces / " -"external data > Trouble Ticket System (TTS) > Configuration**:" +"Please note that the field is **not** gone and still contains an existing " +"value (if set)! Consider *remove* instead, if you want this field to be gone." msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "i-doit administration interface with TTS configuration" +#: ../system/core-workflows/how-do-they-work.rst:112 +msgid "remove |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:104 -msgid "TTS-Type" +#: ../system/core-workflows/how-do-they-work.rst:112 +msgid "Entirely removes the field. The field value will not be evaluated." msgstr "" -#: ../system/integrations/i-doit.rst:104 -msgid "``Zammad``" -msgstr "``Zammad``" - -#: ../system/integrations/i-doit.rst:115 -msgid "Username / Password" -msgstr "Kullanıcı adı / Parola" - -#: ../system/integrations/i-doit.rst:107 -msgid "Login credentials for a Zammad agent." +#: ../system/core-workflows/how-do-they-work.rst:115 +msgid "set mandatory |ui| |api|" msgstr "" -#: ../system/integrations/i-doit.rst:109 -msgid "" -"This agent must have **read permission** for all :doc:`groups ` that plan on using the i-doit integration." +#: ../system/core-workflows/how-do-they-work.rst:115 +msgid "Sets the field to mandatory." msgstr "" -#: ../system/integrations/i-doit.rst:113 -msgid "" -"You may even wish to create a dedicated agent account just for this " -"integration (otherwise, if the agent ever changes her password, you will " -"have to remember to update it here)." +#: ../system/core-workflows/how-do-they-work.rst:118 +msgid "set optional |ui| |api|" msgstr "" -#: ../system/integrations/i-doit.rst:117 -msgid "URL incl. protocol" +#: ../system/core-workflows/how-do-they-work.rst:118 +msgid "Sets the field to optional." msgstr "" -#: ../system/integrations/i-doit.rst:118 -msgid "``https://your.zammad.domain``" -msgstr "``https://your.zammad.domain``" +#: ../system/core-workflows/how-do-they-work.rst:124 +msgid "add option |ui| |api|" +msgstr "" -#: ../system/integrations/index.rst:2 -msgid "Integrations" -msgstr "Entegrasyonlar" +#: ../system/core-workflows/how-do-they-work.rst:121 +msgid "Allows adding options to tree selects or selects." +msgstr "" -#: ../system/integrations/index.rst:4 +#: ../system/core-workflows/how-do-they-work.rst:123 msgid "" -"Zammad offers numerous integrations that add rich features to your instance." +"You have to use the \"remove option\" before performing this action. It " +"allows you to use *existing* configured values." msgstr "" -"Zammad, bulut sunucunuza zengin özellikler ekleyen çok sayıda entegrasyon " -"sunar." - -#: ../system/integrations/index.rst:6 -msgid "We're still working on this part of our documentation, stay tight!" -msgstr "Dokümanımızın bu kısmı üzerinde hala çalışıyoruz, sıkı durun!" -#: ../system/integrations/index.rst:10 -#, fuzzy -msgid "Integrations for Phone Systems" -msgstr "Telefon sistemleri için entegrasyonlar" +#: ../system/core-workflows/how-do-they-work.rst:128 +msgid "remove option |ui| |api|" +msgstr "" -#: ../system/integrations/index.rst:14 +#: ../system/core-workflows/how-do-they-work.rst:127 msgid "" -"Your VoIP provider or telephony system is not listed? Possibly your provider " -"supports Zammad by using the generic CTI - if you're unsure ask your " -"provider." +"Allows removing options from tree selects or selects. It allows you to use " +"*existing* configured values." msgstr "" -#: ../system/integrations/index.rst:18 -msgid "" -"Provider does not support Zammad? Consider creating a `feature request in " -"the Zammad Community `_." +#: ../system/core-workflows/how-do-they-work.rst:134 +msgid "set fixed to |ui| |api|" msgstr "" -#: ../system/integrations/index.rst:31 -#, fuzzy -msgid "Integrations for Authentication and Customers" -msgstr "Kimlik doğrulama ve müşteriler için entegrasyonlar" +#: ../system/core-workflows/how-do-they-work.rst:131 +msgid "Reduces the available options by your selection." +msgstr "" -#: ../system/integrations/index.rst:44 -msgid "Integrations for Monitoring Systems" -msgstr "İzleme Sistemleri için Entegrasyonlar" +#: ../system/core-workflows/how-do-they-work.rst:133 +msgid "" +"This reduces your workflows in terms of *add option* and *remove option*." +msgstr "" -#: ../system/integrations/index.rst:46 -msgid "This section currently misses the following integrations:" -msgstr "Bu bölümde şu anda aşağıdaki entegrasyonlar eksik:" +#: ../system/core-workflows/how-do-they-work.rst:137 +msgid "fill in |ui|" +msgstr "" -#: ../system/integrations/index.rst:48 -msgid "Icinga" -msgstr "Icinga" +#: ../system/core-workflows/how-do-they-work.rst:137 +msgid "Allows filling in of string and integer fields with your values." +msgstr "" -#: ../system/integrations/index.rst:49 -msgid "Monit" -msgstr "Monit" +#: ../system/core-workflows/how-do-they-work.rst:141 +msgid "fill in empty |ui|" +msgstr "" -#: ../system/integrations/index.rst:50 -msgid "Nagios" -msgstr "Nagios" +#: ../system/core-workflows/how-do-they-work.rst:140 +msgid "" +"Allows filling in of string and integer fields with your values **if the " +"field is empty**." +msgstr "" -#: ../system/integrations/index.rst:60 -msgid "Integrations for Issue Trackers" -msgstr "Sorun Takipçileri için Entegrasyonlar" +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "select |ui|" +msgstr "" -#: ../system/integrations/index.rst:70 -msgid "Other Integrations" -msgstr "Diğer Entegrasyonlar" +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "Select a specific value within a select, tree select or boolean field." +msgstr "" -#: ../system/integrations/index.rst:72 -msgid "" -"This section will hold any other integration that can't be grouped up (yet)." +#: ../system/core-workflows/how-do-they-work.rst:153 +msgid "auto select |ui|" msgstr "" -"Bu bölüm, (henüz) gruplandırılamayan diğer tüm entegrasyonları içerecektir." -#: ../system/integrations/ldap/index.rst:2 -msgid "LDAP / Active Directory" -msgstr "LDAP / Active Directory" +#: ../system/core-workflows/how-do-they-work.rst:147 +msgid "Helps users with tree select and select fields:" +msgstr "" -#: ../system/integrations/ldap/index.rst:4 +#: ../system/core-workflows/how-do-they-work.rst:149 msgid "" -"Zammad comes with a powerful LDAP integration that allows you to have a " -"single source of truth. By this you reduce the number of login credentials " -"your user has to remember." +"If the field has only one option available for selection and no value yet, " +"the value will be automatically set." msgstr "" -#: ../system/integrations/ldap/index.rst:10 +#: ../system/core-workflows/how-do-they-work.rst:152 msgid "" -"The LDAP source is also a perfect candidate for Zammad's :docs:`Kerberos " -"Single Sign-On ` but also works as addition " -"to other :doc:`/settings/security/third-party`." +"This option only works if you have one value and doesn't work if there is " +"more than one option available." msgstr "" -#: ../system/integrations/ldap/index.rst:None -msgid "Zammands LDAP management page" +#: ../system/core-workflows/how-do-they-work.rst:157 +msgid "set readonly |ui|" msgstr "" -#: ../system/integrations/ldap/index.rst:25 -#, fuzzy -msgid "📝 :doc:`manage`" -msgstr ":doc:`Yönetim > Tetikleyiciler `" +#: ../system/core-workflows/how-do-they-work.rst:156 +msgid "" +"Allows you to display an attribute as read only (which means no changes are " +"possible)." +msgstr "" -#: ../system/integrations/ldap/index.rst:25 -msgid "Add, modify, remove or re-arrange your LDAP-Sources as needed." +#: ../system/core-workflows/how-do-they-work.rst:161 +msgid "unset readonly |ui|" msgstr "" -#: ../system/integrations/ldap/index.rst:30 -msgid "Before you continue, please note the following limitations." +#: ../system/core-workflows/how-do-they-work.rst:160 +msgid "" +"In case a workflow set the field in question to read only, you can undo this " +"with option above." msgstr "" -#: ../system/integrations/ldap/index.rst:32 -msgid "Mapping / Synchronizing organizations is not possible" +#: ../system/core-workflows/how-do-they-work.rst:172 +msgid "Stop after match" msgstr "" -#: ../system/integrations/ldap/index.rst:36 +#: ../system/core-workflows/how-do-they-work.rst:174 msgid "" -"You may want to consider using domain based assignments to overcome this " -"issue. Learn more on :doc:`/manage/organizations/index`." +"Here you can decide if other workflows are executed after the current one." msgstr "" -#: ../system/integrations/ldap/index.rst:39 +#: ../system/core-workflows/how-do-they-work.rst:176 msgid "" -"Zammad's LDAP sync is one way. Editing user settings or permissions may be " -"overwritten upon the next sync depending on your configuration." +"If set to ``no`` (default), further workflows will be executed if they match " +"the condition. In this case, it is possible that your actions from the " +"current workflow can be overwritten by another workflow." msgstr "" -#: ../system/integrations/ldap/index.rst:41 -msgid "Nested groups are not supported." +#: ../system/core-workflows/how-do-they-work.rst:180 +msgid "" +"If set to ``yes``, no further worflows will be executed after the current " +"one." msgstr "" -#: ../system/integrations/ldap/index.rst:42 -msgid "Synchronizing user avatars from LDAP is not supported." +#: ../system/core-workflows/how-do-they-work.rst:184 +msgid "Priority" msgstr "" -#: ../system/integrations/ldap/index.rst:43 -msgid "Unlike user filters, group filters cannot be changed." +#: ../system/core-workflows/how-do-they-work.rst:186 +msgid "" +"You can define the sequence, in which the workflows are executed. The " +"default value is ``500``." msgstr "" -#: ../system/integrations/ldap/index.rst:44 +#: ../system/core-workflows/how-do-they-work.rst:189 msgid "" -"When a user originates from an LDAP server, Zammad will try to verify the " -"login credentials against LDAP first - if this fails Zammad will check its " -"local database." +"The workflows are executed in ascending order by their priority. That means " +"lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." msgstr "" -#: ../system/integrations/ldap/index.rst:50 +#: ../system/core-workflows/learn-by-example.rst:2 +#, fuzzy +msgid "Learn by Example" +msgstr "Örnek ile öğren" + +#: ../system/core-workflows/learn-by-example.rst:4 msgid "" -"Users can have local passwords even if they're LDAP users! You can learn " -"more about user accounts in general on :doc:`/manage/users/index`." +"This page provides some basic examples for Core Workflows. Of course you can " +"build much more complex workflows if needed." msgstr "" -#: ../system/integrations/ldap/index.rst:54 +#: ../system/core-workflows/learn-by-example.rst:7 msgid "" -"When several LDAP sources contain the same user (meaning the same email " -"address), the user in question will be updated with every source configured. " -"*The last LDAP source will win.*" +"To learn about Core Workflows in detail, first go to :doc:`how-do-they-work`." msgstr "" -#: ../system/integrations/ldap/index.rst:58 +#: ../system/core-workflows/learn-by-example.rst:10 #, fuzzy -msgid "" -"This is subject to change with `Issue 4109 `_ in the future." -msgstr "Şu anda mevcut değil, `Issue 2769 `_a göz atın" +msgid "Group Based Examples" +msgstr "Örnek" -#: ../system/integrations/ldap/index.rst:60 +#: ../system/core-workflows/learn-by-example.rst:12 msgid "" -"Synchronization statistics currently affect *all* configured LDAP sources. " -"This also applies for newly added or updated sources." +"All following workflows have the same base configurations. The workflow may " +"not use them all." msgstr "" -#: ../system/integrations/ldap/index.rst:63 +#: ../system/core-workflows/learn-by-example.rst:15 #, fuzzy -msgid "" -"This is subject to change with `Issue 4108 `_ in the future." -msgstr "Şu anda mevcut değil, `Issue 2769 `_a göz atın" +msgid "Groups:" +msgstr "Gruplar" -#: ../system/integrations/ldap/index.rst:65 -msgid "" -"Zammad currently has limited fallback server support. You can workaround " -"this by providing several sources - however, ensure to have the exact same " -"configuration on your fallback." +#: ../system/core-workflows/learn-by-example.rst:20 +#, fuzzy +msgid "Attributes:" +msgstr "Bilet Nitelikleri" + +#: ../system/core-workflows/learn-by-example.rst:22 +msgid "Category (Single tree selection field, not mandatory, agents only)" msgstr "" -#: ../system/integrations/ldap/index.rst:69 -#, fuzzy +#: ../system/core-workflows/learn-by-example.rst:23 msgid "" -"This is subject to improve with `Issue 4107 `_ in the future." -msgstr "Şu anda mevcut değil, `Issue 2769 `_a göz atın" +"Approved (Boolean field, not mandatory, not shown, ``false`` as default)" +msgstr "" -#: ../system/integrations/ldap/index.rst:76 -msgid "" -"This section holds all requests Zammad handled for all LDAP sources. These " -"entries can either contain synchronization information or logins " -"(authentication attempts via Zammad's login interface)." +#: ../system/core-workflows/learn-by-example.rst:24 +msgid "Operating System (Text field, not mandatory, not shown)" msgstr "" -#: ../system/integrations/ldap/index.rst:80 -msgid "" -"By clicking on any request, Zammad will provide even more information. The " -"provided information can be useful when something does not work as expected." +#: ../system/core-workflows/learn-by-example.rst:25 +msgid "Software used (Single selection field, not mandatory, not shown)" msgstr "" -#: ../system/integrations/ldap/index.rst:85 -msgid "" -"Especially a LDAP synchronization can cause many log entries. The web " -"interface will always limit the number of shown entries to the last 50 " -"entries." +#: ../system/core-workflows/learn-by-example.rst:68 +msgid "Group specific values and fields" msgstr "" -#: ../system/integrations/ldap/index.rst:None +#: ../system/core-workflows/learn-by-example.rst:28 msgid "" -"Screencast showing LDAP integration log entries and a detail view on\n" -"an entry." +"This workflow set depends on the category field. It reduces the available " +"set of values based on the group selected." msgstr "" -#: ../system/integrations/ldap/manage.rst:2 -msgid "Manage LDAP-Sources" +#: ../system/core-workflows/learn-by-example.rst:33 +msgid "Workflow 2nd Level group" msgstr "" -#: ../system/integrations/ldap/manage.rst:6 +#: ../system/core-workflows/learn-by-example.rst:35 msgid "" -"Please keep in mind all current limitations for the LDAP synchronization. " -"This will help to understand scopes of the following operations better." +"This reduces the category options to ``2nd Level/*``, ``Internal/*`` and " +"``Others``. It also sets further required fields to mandatory and visible." msgstr "" -#: ../system/integrations/ldap/manage.rst:65 -#, fuzzy -msgid "Add new source" -msgstr "Yeni bir planlayıcı ekle" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for 2nd level" +msgstr "" -#: ../system/integrations/ldap/manage.rst:10 -msgid "" -"Using the *New Source* button allows you to add new LDAP sources to your " -"installation. You're not limited in the number of sources, however, keep in " -"mind that many sources will also take more time to synchronize." +#: ../system/core-workflows/learn-by-example.rst:43 +msgid "Workflow Support group" msgstr "" -#: ../system/integrations/ldap/manage.rst:14 +#: ../system/core-workflows/learn-by-example.rst:45 msgid "" -"You can choose between different encryption types, namely *SSL* and " -"*STARTTLS* or none of them (\"*No SSL*\"). If you choose *SSL* or " -"*STARTTLS*, Zammad will display an additional *SSL verification* option that " -"allows you to disable the verification, e.g. for self-signed SSL " -"certificates. You can also tell Zammad to use a different port by appending " -"``:`` to your hostname/IP." +"This reduces the category options to ``Support/*``, ``Internal/*`` and " +"``Others``. It also sets further required fields to visible." msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "" -"Screenshot of configuring a new LDAP source with SSL encryption and SSL " -"verification" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for support" msgstr "" -#: ../system/integrations/ldap/manage.rst:26 -msgid "" -"New Source with SSL transport security enabled and certificate verification" +#: ../system/core-workflows/learn-by-example.rst:53 +msgid "Workflow Sales group" msgstr "" -#: ../system/integrations/ldap/manage.rst:30 +#: ../system/core-workflows/learn-by-example.rst:55 msgid "" -"Using an user filter can be a good idea if you only require a small subset " -"of your LDAP users in Zammad." +"This reduces the category options to ``Sales/*``, ``Internal/*`` and " +"``Others``." msgstr "" -#: ../system/integrations/ldap/manage.rst:42 -msgid "This especially affects inactive users" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for sales" msgstr "" -#: ../system/integrations/ldap/manage.rst:34 -msgid "" -"As every LDAP behaves differently on which attributes and how they are set, " -"Zammad doesn't care about any flags." +#: ../system/core-workflows/learn-by-example.rst:68 +#: ../system/integrations/slack.rst:88 +msgid "The Result" msgstr "" -#: ../system/integrations/ldap/manage.rst:37 +#: ../system/core-workflows/learn-by-example.rst:63 msgid "" -"Users that no longer are returned by your LDAP source will automatically be " -"set to inactive. Zammad assumes that the user was deactivated." +"This is what the agent would experience with the above workflows in place." msgstr "" -#: ../system/integrations/ldap/manage.rst:41 +#: ../system/core-workflows/learn-by-example.rst:0 msgid "" -"Users will never be removed automatically! If you want to remove obsolete " -"users, use :doc:`/system/data-privacy`." +"Workflow shows objects and limits options based on selections on the group" msgstr "" -#: ../system/integrations/ldap/manage.rst:46 -#, fuzzy -msgid "Active Directory admins" -msgstr "LDAP / Active Directory" +#: ../system/core-workflows/learn-by-example.rst:90 +msgid "Approval process" +msgstr "" -#: ../system/integrations/ldap/manage.rst:45 +#: ../system/core-workflows/learn-by-example.rst:71 msgid "" -"Active Directories are quite specific on how to filter for active users only " -"- please see the `Microsoft documentation `_ for more " -"information." +"In this case ``approved`` is visible to agents by default. For this " +"workflow, an additional role ``Approval person`` is required (no further " +"permissions)." +msgstr "" + +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that restricts an approval attribute to specific roles" msgstr "" -#: ../system/integrations/ldap/manage.rst:51 +#: ../system/core-workflows/learn-by-example.rst:81 msgid "" -"*Do not* manually write pathes of either LDAP attributes or groups. If " -"Zammad does not display them, it either cannot find them or you have a lot " -"of users that don't have the attributes populated." +"This workflow may work best in combination with a :doc:`trigger ` but technically, this is not required." msgstr "" -#: ../system/integrations/ldap/manage.rst:55 +#: ../system/core-workflows/learn-by-example.rst:84 msgid "" -"Zammad will always only return attributes that are filled - this reduces the " -"returned list of attributes greatly." -msgstr "" - -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing how to add a new LDAP source" +"Select fields may be a better approach because they allow more values than " +"just a simple ``true`` or ``false``." msgstr "" -#: ../system/integrations/ldap/manage.rst:63 +#: ../system/core-workflows/learn-by-example.rst:0 msgid "" -"If your LDAP system doesn't allow anonymous bind, Zammad detects it and " -"provides you an editable \"Base DN\" *text* field instead of a prefilled " -"*select* field." +"Workflow fixes possible values of \"Approved ?\" to a specific selection " +"depending on the users role" msgstr "" -#: ../system/integrations/ldap/manage.rst:81 -msgid "Review or edit existing source" +#: ../system/core-workflows/learn-by-example.rst:103 +msgid "State dependent mandatory fields" msgstr "" -#: ../system/integrations/ldap/manage.rst:68 +#: ../system/core-workflows/learn-by-example.rst:93 msgid "" -"Clicking on a LDAP source will provide a configuration and mapping overview." +"This workflow sets ``Category`` to mandatory if the agent wants to set the " +"states ``closed`` or ``pending close`` to enforce categorization." msgstr "" -#: ../system/integrations/ldap/manage.rst:70 -msgid "" -"If needed you can then use the *Change* button to update either the name, " -"active state or the whole configuration. If you're changing the whole " -"configuration, the dialogue will be identical to the source creation." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that sets fields to mandatory on specific states" msgstr "" -#: ../system/integrations/ldap/manage.rst:76 +#: ../system/core-workflows/learn-by-example.rst:0 msgid "" -"Did your LDAP server change? Different LDAP servers have different " -"structures and default attributes. This causes the LDAP synchronization to " -"likely fail. Consider removing the affected source and re-add it." +"Workflow sets category field to mandatory upon choosing closed or pending " +"close as state" msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing the update of the source name." +#: ../system/core-workflows/learn-by-example.rst:106 +msgid "Manual Ticket Handover Process" msgstr "" -#: ../system/integrations/ldap/manage.rst:89 -msgid "Re-arrange LDAP source's order" +#: ../system/core-workflows/learn-by-example.rst:108 +msgid "This example covers the handover of a ticket from one agent to another:" msgstr "" -#: ../system/integrations/ldap/manage.rst:84 +#: ../system/core-workflows/learn-by-example.rst:110 msgid "" -"You can change the synchronization order for each source at any time. Zammad " -"will synchronize the sources from top to bottom." +"When the ticket owner is modified, a new text field (\"Handover\") shows up " +"for a comment" msgstr "" -#: ../system/integrations/ldap/manage.rst:0 +#: ../system/core-workflows/learn-by-example.rst:112 msgid "" -"Screencasting showing how to change the source order by using\n" -"drag and drop." +"This may only be visible when the owner is changed, therefore it has to be " +"hidden in general" msgstr "" -#: ../system/integrations/ldap/manage.rst:101 -msgid "Remove a source" +#: ../system/core-workflows/learn-by-example.rst:114 +msgid "The input in this handover text field is mandatory" msgstr "" -#: ../system/integrations/ldap/manage.rst:92 +#: ../system/core-workflows/learn-by-example.rst:115 msgid "" -"If you no longer need the a LDAP source or simply want to start over, you " -"can remove them at any time. This will not remove synchronized users, data " -"synchronized or permissions." +"After submitting changes, the value of the handover field must be added as " +"an note to the ticket (via trigger)" msgstr "" -#: ../system/integrations/ldap/manage.rst:98 -msgid "" -"Not sure if you'd need the source later on? Set the source to inactive " -"instead of removing it - see *Review or edit existing source* for more." +#: ../system/core-workflows/learn-by-example.rst:121 +msgid "Hiding handover field" msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing how to remove LDAP sources." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Hiding the handover field in core workflows" msgstr "" -#: ../system/integrations/pgp/index.rst:2 -msgid "PGP" +#: ../system/core-workflows/learn-by-example.rst:126 +msgid "Showing handover field and setting it to mandatory" msgstr "" -#: ../system/integrations/pgp/index.rst:7 -msgid "" -"Pretty Good Privacy (PGP) is another method for secure email communication. " -"With PGP, you can exchange **signed** and **encrypted** messages with others." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Showing the handover field and set it as mandatory" msgstr "" -#: ../system/integrations/pgp/index.rst:13 -#: ../system/integrations/smime/index.rst:17 -msgid "Signing" -msgstr "İmzalama" +#: ../system/core-workflows/learn-by-example.rst:131 +msgid "Trigger writing handover input to a new article" +msgstr "" -#: ../system/integrations/pgp/index.rst:11 -msgid "is a proof that a message hasn't been manipulated on its way." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Write handover content to a new article" msgstr "" -#: ../system/integrations/pgp/index.rst:13 -#, fuzzy +#: ../system/core-workflows/learn-by-example.rst:133 msgid "" -"In other words, it guarantees message **integrity** and **authenticity**." -msgstr "Başka bir deyişle, *gizlilik* ve *veri güvenliği*ni garanti eder." +"As a result, the ticket includes an article of the type note which includes " +"the predefined text and the handover comment." +msgstr "" -#: ../system/integrations/pgp/index.rst:19 -#: ../system/integrations/smime/index.rst:22 -msgid "Encryption" -msgstr "Şifreleme" +#: ../system/core-workflows/limitations.rst:6 +msgid "Core Workflows do not replace Triggers" +msgstr "" -#: ../system/integrations/pgp/index.rst:16 -#: ../system/integrations/smime/index.rst:20 +#: ../system/core-workflows/limitations.rst:5 msgid "" -"scrambles a message so that it can only be unscrambled by the intended " -"recipient." +"Workflows manipulate the behavior of fields. However, they do not set values " +"in fields because of actions." msgstr "" -#: ../system/integrations/pgp/index.rst:19 -#, fuzzy +#: ../system/core-workflows/limitations.rst:16 +msgid "API calls are only partly affected" +msgstr "" + +#: ../system/core-workflows/limitations.rst:9 msgid "" -"In other words, it guarantees message **privacy** and **data security**." -msgstr "Başka bir deyişle, *gizlilik* ve *veri güvenliği*ni garanti eder." +"Some options affect UI only and thus do not restrict responses and calls." +msgstr "" -#: ../system/integrations/pgp/index.rst:25 -msgid "Screenshot of ticket creation with encrypt and sign buttons" +#: ../system/core-workflows/limitations.rst:11 +msgid "This affects the following actions:" msgstr "" -#: ../system/integrations/pgp/index.rst:25 -msgid "" -"Once PGP has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " -"appear in the ticket composer." +#: ../system/core-workflows/limitations.rst:13 +msgid "select" msgstr "" -#: ../system/integrations/pgp/index.rst:28 -msgid "**Sign button not visible?**" +#: ../system/core-workflows/limitations.rst:14 +msgid "auto select" msgstr "" -#: ../system/integrations/pgp/index.rst:30 -msgid "" -"Please note that the signing of emails is based on the outgoing email " -"account. That means you have to choose a group with a sender email account, " -"which has a private key assigned." +#: ../system/core-workflows/limitations.rst:15 +msgid "show" msgstr "" -#: ../system/integrations/pgp/index.rst:35 -#, fuzzy -msgid "Handling of Keys" -msgstr "Makro Yönetimi" +#: ../system/core-workflows/limitations.rst:16 +msgid "hide" +msgstr "" -#: ../system/integrations/pgp/index.rst:36 +#: ../system/core-workflows/limitations.rst:25 +msgid "Some fields stay unavailable to customers" +msgstr "" + +#: ../system/core-workflows/limitations.rst:19 msgid "" -"To use the PGP function, you have to enable the integration (PGP) by " -"switching the toggle to *enabled*." +"For technical and security reasons, some default fields (the pale ones you " +"can't edit) stay unavailable for display and usage on customer permissions." msgstr "" -#: ../system/integrations/pgp/index.rst:39 +#: ../system/core-workflows/limitations.rst:23 msgid "" -"You can add keys by clicking the *add key* button. The keys can be imported " -"from a file or you can paste the content of the key in the text box." +"If you require your customers to change e.g. priorities, please consider " +"using workarounds via :doc:`/system/objects` and :doc:`/manage/trigger`." msgstr "" -#: ../system/integrations/pgp/index.rst:42 -msgid "**Which keys do I have to import?**" +#: ../system/core-workflows/limitations.rst:29 +msgid "Ticket title changes not supported in edit mask" msgstr "" -#: ../system/integrations/pgp/index.rst:44 +#: ../system/core-workflows/limitations.rst:28 msgid "" -"For **signing** *outgoing* emails, you have to import the private key of " -"your Zammad email account." +"It is currently not possible to perform changes of the ticket title in the " +"edit mask (e.g. renaming, set to read-only)." msgstr "" -#: ../system/integrations/pgp/index.rst:47 -msgid "" -"For **encrypting** *outgoing* emails, you have to import the public key of " -"the customer's email account." +#: ../system/core-workflows/limitations.rst:37 +msgid "What is out of scope of Core Workflows?" msgstr "" -#: ../system/integrations/pgp/index.rst:50 +#: ../system/core-workflows/limitations.rst:32 msgid "" -"For **verifying the signature** of signed *incoming* emails, you have to " -"import the public key of the customer." +"There are some things that would count as workflow but are either done via :" +"doc:`/manage/trigger` or :doc:`/manage/scheduler`." msgstr "" -#: ../system/integrations/pgp/index.rst:53 -msgid "" -"For **decrypting** of encrypted *incoming* emails, you have to import the " -"private key of your Zammad email account." +#: ../system/core-workflows/limitations.rst:35 +msgid "Such as (but not limited to):" msgstr "" -#: ../system/integrations/pgp/index.rst:57 -msgid "Import Keys From a File" +#: ../system/core-workflows/limitations.rst:37 +msgid "up- or downgrade permissions of users" msgstr "" -#: ../system/integrations/pgp/index.rst:58 -msgid "You can import keys from a file in the section **Upload key**:" +#: ../system/core-workflows/limitations.rst:38 +msgid "affecting article creation or listing" msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of adding a key via file" +#: ../system/data-privacy.rst:2 +msgid "Data Privacy" +msgstr "Veri Gizliliği" + +#: ../system/data-privacy.rst:4 +msgid "" +"For compliance with GDPR and other data privacy laws, you may wish to " +"**permanently delete users from the system**, along with **all of their " +"associated tickets**." msgstr "" -#: ../system/integrations/pgp/index.rst:64 +#: ../system/data-privacy.rst:8 msgid "" -"**Supported file formats:** ASCII-armor as well as binary GPG format " -"(basically any GPG supported key format) is supported here." +"You can create manual deletion tasks or even automated deletion tasks for " +"tickets and users based on custom conditions via :doc:`scheduler `!" msgstr "" -#: ../system/integrations/pgp/index.rst:68 -msgid "Import Keys by Pasting the Content" +#: ../system/data-privacy.rst:12 +msgid "" +"Access to this panel requires ``admin.data_privacy`` permissions (introduced " +"in Zammad 3.5)." msgstr "" -#: ../system/integrations/pgp/index.rst:69 -msgid "You can also paste the key's content in the section **paste key**:" +#: ../system/data-privacy.rst:15 +msgid "" +"On older systems that have not been updated yet, customers can also be :docs:" +"`deleted via the Zammad console `." msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of adding a key via pasting" +#: ../system/data-privacy.rst:22 +msgid "User deletion dialog in the Data Privacy panel" msgstr "" -#: ../system/integrations/pgp/index.rst:75 +#: ../system/data-privacy.rst:22 msgid "" -"**Supported format:** Please note that only ASCII-armor is supported here." +"The user deletion dialog lists some of the tickets that will be removed from " +"the system along with the user." msgstr "" -#: ../system/integrations/pgp/index.rst:78 +#: ../system/data-privacy.rst:27 #, fuzzy -msgid "Deleting Keys" +msgid "Deleting Users via GUI" msgstr "Kullanıcıları Silmek" -#: ../system/integrations/pgp/index.rst:79 -msgid "" -"If you want to delete a specific key, you can do it by clicking on the menu " -"in the *actions* column and select **delete**:" -msgstr "" - -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of deleting a key" -msgstr "" - -#: ../system/integrations/pgp/index.rst:88 +#: ../system/data-privacy.rst:29 #, fuzzy -msgid "Downloading Keys" -msgstr "Sertifika Ekle" +msgid "🔥 **All deletions are FINAL!**" +msgstr "💣 **Tüm silmeler TAMAMLANDI!**" -#: ../system/integrations/pgp/index.rst:89 -msgid "" -"If you want to download your keys, you can do this as well via corresponding " -"action buttons. Depending on the key, you can choose wether you want to " -"download the private or the public key." +#: ../system/data-privacy.rst:31 +msgid "Once you click “Delete”, the action cannot be canceled or undone." msgstr "" -#: ../system/integrations/pgp/index.rst:95 -#: ../system/integrations/smime/manage-certificates.rst:76 -msgid "Default Behavior" -msgstr "Varsayılan Davranış" - -#: ../system/integrations/pgp/index.rst:96 +#: ../system/data-privacy.rst:33 msgid "" -"Here you can adjust on per group basis, if *sign* and *encryption* is on or " -"off by default. Please be aware, that agents can always override the setting " -"for each individual article." +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Adjusting default behavior on per group basis" +#: ../system/data-privacy.rst:36 +msgid "**The following records cannot be deleted:**" msgstr "" -#: ../system/integrations/pgp/index.rst:107 -msgid "" -"Here you can see the last actions regarding signing and encryption and if " -"they were successful." -msgstr "" +#: ../system/data-privacy.rst:38 +msgid "your own account" +msgstr "kendi hesabınız" -#: ../system/integrations/pgp/index.rst:117 -msgid "**Sign button is not visible, but keys are imported.**" +#: ../system/data-privacy.rst:39 +msgid "the system's last remaining administrator account" msgstr "" -#: ../system/integrations/pgp/index.rst:115 -msgid "Did you choose a group in the ticket?" +#: ../system/data-privacy.rst:42 +msgid "Step 1: Find a User / Confirm Deletion" msgstr "" -#: ../system/integrations/pgp/index.rst:116 -msgid "" -"Did you import a private key for the email adress, which is used for " -"outgoing emails in the group?" +#: ../system/data-privacy.rst:44 +msgid "There are three ways to access the user deletion dialog:" msgstr "" -#: ../system/integrations/pgp/index.rst:122 -msgid "**How to obtain keys?**" -msgstr "" +#: ../system/data-privacy.rst:51 +#, fuzzy +msgid "**from the user's profile**" +msgstr "**kullanıcının profilinden**" -#: ../system/integrations/pgp/index.rst:120 -msgid "" -"You can create them yourself! There are some good tutorials on the web on " -"how to create them. Providing keys to Zammad is a prerequisite to use the " -"PGP feature." +#: ../system/data-privacy.rst:0 +msgid "Accessing the user deletion dialog in a user profile" msgstr "" -#: ../system/integrations/pgp/index.rst:127 -msgid "**It says a passphrase is needed, but I haven't got one.**" +#: ../system/data-privacy.rst:51 +msgid "Click **Action > Delete**." msgstr "" -#: ../system/integrations/pgp/index.rst:125 -msgid "" -"If the key is secured with a passphrase, you have to provide it for the " -"import in Zammad. It is possible that keys may have an empty passphrase. " -"However, this is *not* recommended." +#: ../system/data-privacy.rst:58 +msgid "**in the “Manage > Users” Admin Panel**" msgstr "" -#: ../system/integrations/pgp/index.rst:132 -msgid "**How do my customers get my new key?**" +#: ../system/data-privacy.rst:0 +msgid "Accessing the user deletion dialog under “Users” in the Admin Panel" msgstr "" -#: ../system/integrations/pgp/index.rst:130 -msgid "" -"You have to provide your **public** key in advance. Your customer also has " -"to configure PGP in their email workflow and import your public key. The " -"other way round, you have to get the public key of your customer and have to " -"import it to Zammad." +#: ../system/data-privacy.rst:58 +msgid "Use the **⋮ Actions** menu for the target user." msgstr "" -#: ../system/integrations/slack.rst:2 -msgid "Slack" -msgstr "Slack" - -#: ../system/integrations/slack.rst:4 -msgid "**⚠️ Deprecation warning ⚠️**" +#: ../system/data-privacy.rst:66 ../system/data-privacy.rst:104 +msgid "**in the “System > Data Privacy” Admin Panel**" msgstr "" -#: ../system/integrations/slack.rst:6 +#: ../system/data-privacy.rst:0 msgid "" -"Zammad 7 will no longer support this dedicated Slack integration. It is " -"recommended to switch to :doc:`pre-defined webhooks ` instead. Existing Slack integrations should " -"be migrated manually before this feature is dropped." +"Accessing the user deletion dialog under “Data Privacy” in the Admin Panel" msgstr "" -#: ../system/integrations/slack.rst:14 +#: ../system/data-privacy.rst:65 msgid "" -"In order to use this feature, please add a new Slack app to your Workspace. " -"The App you need is called ``Incoming WebHooks`` ." +"Use the **New Deletion Task** button. Search for users by name or email " +"address." msgstr "" -#: ../system/integrations/slack.rst:18 +#: ../system/data-privacy.rst:79 #, fuzzy -msgid "Why Do I Need This Feature?" -msgstr "Neden bu özelliğe ihtiyacım var?" +msgid "**Delete organizations**" +msgstr "🏢 Organizasyon" -#: ../system/integrations/slack.rst:20 +#: ../system/data-privacy.rst:69 msgid "" -"If you're already using Slack for your team communication, you'll love this " -"feature! Our Slack integration can push ticket notifications about the last " -"ticket article based on the following events:" +"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:" msgstr "" -#: ../system/integrations/slack.rst:24 -msgid "on Ticket creation" -msgstr "Bilet oluşturulduğunda" +#: ../system/data-privacy.rst:0 +msgid "Deleting an organization via the user deletion dialog" +msgstr "" -#: ../system/integrations/slack.rst:25 -msgid "on Ticket updates" -msgstr "Bilet güncellemelerinde" +#: ../system/data-privacy.rst:78 +msgid "" +"If this option does not appear, make sure there are no pending deletion " +"tasks for other customers from this organization." +msgstr "" -#: ../system/integrations/slack.rst:26 -msgid "on reached reminders" +#: ../system/data-privacy.rst:82 +msgid "Step 2: Monitor Deletion Job Status" msgstr "" -#: ../system/integrations/slack.rst:27 -msgid "a Ticket has escalated" -msgstr "Bir bilet yükseldi" +#: ../system/data-privacy.rst:84 +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:" +msgstr "" -#: ../system/integrations/slack.rst:28 -msgid "a Ticket is going to escalate" +#: ../system/data-privacy.rst:98 +msgid "**in the Activity Stream**" msgstr "" -#: ../system/integrations/slack.rst:30 +#: ../system/data-privacy.rst:0 +msgid "Activity Stream showing data privacy tasks" +msgstr "" + +#: ../system/data-privacy.rst:94 msgid "" -"Zammad will provide the Ticket title, a direct link to the Ticket, the event " -"type (creation, updated, escalation), the customer, time and the last " -"article that has triggered the notification." +"For each deleted user, the Activity Stream will be updated twice—once when " +"the task is created, and once when it's complete." msgstr "" -#: ../system/integrations/slack.rst:34 +#: ../system/data-privacy.rst:97 msgid "" -"This will give you further options, as you can see e.g. escalating tickets " -"that are assigned to an agent that's e.g. absent. You can interact faster, " -"as you might see problems earlier (or even before the problem gets one)." +"These notifications are only visible to users with ``admin.data_privacy`` " +"permissions." msgstr "" -#: ../system/integrations/slack.rst:38 +#: ../system/data-privacy.rst:0 msgid "" -"If needed and wanted, you can even discuss directly about the topic before " -"sending an answer to the customer. Another possible use case would be a " -"agent monitoring new agents and their answers to tickets." +"The task list within Data Privacy shows removals being in progress and " +"completed." msgstr "" -#: ../system/integrations/slack.rst:44 -#, fuzzy -msgid "Configure the Integration" -msgstr "Entegrasyonu yapılandır" +#: ../system/data-privacy.rst:107 +msgid "Frequently Asked Questions" +msgstr "Sıkça Sorulan Sorular" -#: ../system/integrations/slack.rst:46 -msgid "" -"First of all, please go to your slack workspace - go to administration => " -"Manage Apps. If you don't have an app yet, you can simply add a new one - " -"just search for ``Incoming WebHooks`` and customize the app to your needs." +#: ../system/data-privacy.rst:121 +msgid "What happens if I receive an email from a deleted customer?" msgstr "" -#: ../system/integrations/slack.rst:50 +#: ../system/data-privacy.rst:110 msgid "" -"Choose (or create) the channel Zammad should post it's information to and " -"press on \"Add Incoming WebHooks integration\". If you're ready, copy the " -"provided WebHook URL and go to your Zammad installation." +"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/integrations/slack.rst:56 +#: ../system/data-privacy.rst:115 msgid "" -"You need administrative rights on the Slack Workspace. The link to the app " -"directory is normally ``https://[workspace-name].slack.com/apps`` ." +"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**." msgstr "" -#: ../system/integrations/slack.rst:63 +#: ../system/data-privacy.rst:130 +msgid "What about user information stored in internal notes or other messages?" +msgstr "" + +#: ../system/data-privacy.rst:124 msgid "" -"To configure the slack integration, log in to Zammad and go to Integrations " -"(System) => Slack in the admin panel." +"The deletion process removes **user accounts and associated tickets only**." msgstr "" -#: ../system/integrations/slack.rst:66 +#: ../system/data-privacy.rst:126 msgid "" -"Here you can choose on what evens Zammad should post information about a " -"ticket to your Slack channel. Next you need to device what groups shall be " -"affected by this, as anybody with access to that specific Slack channel can " -"read at least parts of the ticket this might be a privacy issue, if you " -"select the wrong groups. The username is simply the name that Zammad uses as " -"display name inside the Slack chat. The channel defines the Slack channel " -"the information is being posted in. As last option, you can set a custom " -"icon for posting to slack." +"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." +msgstr "" + +#: ../system/data-privacy.rst:137 +msgid "I deleted an user and can still see a message they sent!" msgstr "" -#: ../system/integrations/slack.rst:74 +#: ../system/data-privacy.rst:133 msgid "" -"When you're ready, just hit \"Submit\" and enable the integration. Zammad " -"will now post new ticket information based on the trigger you chose. Below " -"the options you have the recent log that shows the latest requests to Slack " -"for debugging if needed." +"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." msgstr "" -#: ../system/integrations/slack.rst:81 -msgid "" -"If you leave the Icon URL empty, Zammad will use the Zammad logo instead. " -"The icon should be a square PNG file." +#: ../system/data-privacy.rst:141 +msgid "I removed a customer, now my reporting is off!" msgstr "" -#: ../system/integrations/slack.rst:90 +#: ../system/data-privacy.rst:140 msgid "" -"The following figure shows how it will look if you choose to receive updates " -"on created and updated tickets. On every post Zammad sends to the Slack " -"channel, you can create new threads to discuss about the new article." +"When removing users and their tickets, all references are removed. This also " +"affects e.g. Reporting - these information are lost." msgstr "" -#: ../system/integrations/slack.rst:96 -msgid "" -"If you just want to keep track of soon escalating or already escalated " -"tickets, it will look the the following figure. Zammad changes the color in " -"front of the post so you can easily see the state of the ticket." +#: ../system/data-privacy.rst:145 +msgid "How long does Zammad store created tasks?" msgstr "" -#: ../system/integrations/slack.rst:102 +#: ../system/data-privacy.rst:144 msgid "" -"If you change the state, Zammad will also put information on what state the " -"ticket gets and (if pending state) the date until it pends. You'll also " -"recognize the color codes in front of posts on slack, as they are exact the " -"same the ticket state colors you'll see in Zammad!" +"Please see the on-premise data section of the :docs:`data privacy ` chapter." msgstr "" -#: ../system/integrations/smime/index.rst:2 -msgid "S/MIME" -msgstr "S/MIME" +#: ../system/data-privacy.rst:150 +msgid "What about re-assigned tickets? I want to delete them, too." +msgstr "" -#: ../system/integrations/smime/index.rst:11 +#: ../system/data-privacy.rst:148 msgid "" -"S/MIME is the most widely-supported method for secure email communication. " -"With S/MIME, you can exchange **signed** and **encrypted** messages with " -"others." +"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." msgstr "" -#: ../system/integrations/smime/index.rst:15 -msgid "" -"is proof that a message hasn't been tampered with or sent by an impersonator." +#: ../system/data-privacy.rst:154 +msgid "Why are there so many deletion task entries, I didn't create them!" msgstr "" -#: ../system/integrations/smime/index.rst:17 -#, fuzzy +#: ../system/data-privacy.rst:153 msgid "" -"In other words, it guarantees a message's **integrity** and **authenticity**." -msgstr "Başka bir deyişle, *gizlilik* ve *veri güvenliği*ni garanti eder." +"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." +msgstr "" -#: ../system/integrations/smime/index.rst:22 -msgid "In other words, it guarantees **privacy** and **data security**." -msgstr "Başka bir deyişle, *gizlilik* ve *veri güvenliği*ni garanti eder." +#: ../system/integrations/checkmk/admin-panel-reference.rst:2 +msgid "Admin Panel Reference" +msgstr "Yönetici Paneli Tercihleri" -#: ../system/integrations/smime/index.rst:28 -msgid "Screencast demo of S/MIME features for both new tickets and replies" +#: ../system/integrations/checkmk/admin-panel-reference.rst:None +msgid "Screenshot of Checkmk settings overview" msgstr "" -#: ../system/integrations/smime/index.rst:28 +#: ../system/integrations/checkmk/admin-panel-reference.rst:12 msgid "" -"Once S/MIME has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " -"appear in the ticket composer." +"Which :doc:`group ` should Checkmk tickets be assigned " +"to as a default (*i.e.,* when none is specified)?" msgstr "" -#: ../system/integrations/smime/index.rst:32 -msgid ":doc:`🔪 Prerequisites `" +#: ../system/integrations/checkmk/admin-panel-reference.rst:15 +msgid "(Applies to :ref:`API alerts ` only.)" msgstr "" -#: ../system/integrations/smime/index.rst:31 -msgid "" -"New to S/MIME? This section helps you to find certificate providers and " -"points out Limitations." +#: ../system/integrations/checkmk/admin-panel-reference.rst:21 +msgid "Auto close" msgstr "" -#: ../system/integrations/smime/index.rst:35 -msgid ":doc:`📝 Manage Certificates `" +#: ../system/integrations/checkmk/admin-panel-reference.rst:18 +msgid "" +"Should Zammad automatically close tickets if a service has recovered on its " +"own?" msgstr "" -#: ../system/integrations/smime/index.rst:35 -msgid "Add and download certificates; configure group default behaviors." +#: ../system/integrations/checkmk/admin-panel-reference.rst:21 +msgid "(Agents will receive notifications for such closures as appropriate.)" msgstr "" -#: ../system/integrations/smime/index.rst:38 -msgid ":doc:`😦 Troubleshooting `" +#: ../system/integrations/checkmk/admin-panel-reference.rst:30 +msgid "Auto-close state" msgstr "" -#: ../system/integrations/smime/index.rst:38 -msgid "Took a wrong turn? About recent logs and common issues." +#: ../system/integrations/checkmk/admin-panel-reference.rst:24 +msgid "What ticket state should be applied when “auto-closing” a ticket?" msgstr "" -#: ../system/integrations/smime/index.rst:43 +#: ../system/integrations/checkmk/admin-panel-reference.rst:26 msgid "" -"For more details on how S/MIME integration works on the agent side, see the :" -"user-docs:`user docs `." +"You can choose from the seven built-in ticket states. If these states aren't " +"enough for you, you can :ref:`define a new ticket state ` for this purpose as well. This can be useful for tracking " +"tickets with :doc:`reports `, for example." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:2 -msgid "Manage Certificates" -msgstr "" +#: ../system/integrations/checkmk/admin-panel-reference.rst:35 +#: ../system/integrations/cti/includes/recent-logs.include.rst:2 +#: ../system/integrations/ldap/index.rst:74 +#: ../system/integrations/pgp/index.rst:106 +msgid "Recent Logs" +msgstr "En Son Kayıtlar" -#: ../system/integrations/smime/manage-certificates.rst:4 -msgid "" -"S/MIME is **disabled by default**. Enable it to start adding certificates." +#: ../system/integrations/checkmk/admin-panel-reference.rst:None +msgid "Screenshot of Checkmk \"Recent Logs\" section" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:10 -msgid "Dialogue to add new certificates or private keys" +#: ../system/integrations/checkmk/admin-panel-reference.rst:41 +msgid "" +"If you're having trouble getting Zammad and Checkmk to play nicely together, " +"this section can help you troubleshoot." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:10 +#: ../system/integrations/checkmk/admin-panel-reference.rst:44 msgid "" -"Manage certificates in the Admin Panel under **System > Integrations > S/" -"MIME**. Certificates may be pasted in as plain text or uploaded from a file." +"It contains a record of the fifty most recent transactions that Zammad knows " +"about, including each one's request/response details and return status." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:14 -#, fuzzy -msgid "Add Certificate Data" -msgstr "Sertifika Ekle" - -#: ../system/integrations/smime/manage-certificates.rst:36 -msgid "Add Certificate" -msgstr "Sertifika Ekle" +#: ../system/integrations/checkmk/api-reference.rst:2 +msgid "API Reference" +msgstr "API Referansı" -#: ../system/integrations/smime/manage-certificates.rst:17 +#: ../system/integrations/checkmk/api-reference.rst:4 msgid "" -"Import public-key certificates for both your own organization and your " -"contacts." +"For most users, :ref:`the sample scripts from the Setup Guide ` will do the job just fine. But if you want more fine-grained control" +"—for instance, to create high- and low-priority tickets for different types " +"of system events—then you'll have to customize the data those scripts send " +"to Zammad." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:19 +#: ../system/integrations/checkmk/api-reference.rst:15 msgid "" -"You can also add a bunch of certificates in one go by providing a single " -"file with all relevant certificates." +"This custom script will automatically set all tickets it creates to **high " +"priority** and **assign them to charlie@chrispresso.com**." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:22 -msgid "🕵️ **ALWAYS verify certificates in-person or over the phone!**" -msgstr "" +#: ../system/integrations/checkmk/api-reference.rst:32 +#, fuzzy +msgid "How Does it Work?" +msgstr "Nasıl çalışır?" -#: ../system/integrations/smime/manage-certificates.rst:24 +#: ../system/integrations/checkmk/api-reference.rst:34 msgid "" -"The whole point of signatures is to alert you when someone is trying to " -"pretend to be someone they're not. Never accept a certificate from someone " -"online without verifying it first." +"There are two kinds of data you can pass to the API, both in the form of key-" +"value pairs:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:28 -msgid "📇 **What about trusted certificate authorities?**" -msgstr "" +#: ../system/integrations/checkmk/api-reference.rst:44 +msgid "Checkmk parameters" +msgstr "Checkmk parametreleri" -#: ../system/integrations/smime/manage-certificates.rst:30 +#: ../system/integrations/checkmk/api-reference.rst:38 msgid "" -"In some cases (e.g. when dealing with large enterprises), you may be given a " -"certificate for an entire CA, rather than a single contact. Add it here to " -"trust *all* certificates issued by that CA." +"are required, and make up the **contents** of the resulting tickets/" +"articles. They also determine whether an event creates a new ticket or " +"updates/closes an existing one." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:35 +#: ../system/integrations/checkmk/api-reference.rst:42 msgid "" -"Commercial CAs can usually be verified online. Zammad does not include a " -"list of built-in, trusted CAs." +"These are the only values used in the sample scripts. **Use them as-is**; " +"technically, they can be customized, but it's hard to imagine a good reason " +"for it." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:57 -msgid "Add Private Key" -msgstr "Özel Anahtar Ekle" +#: ../system/integrations/checkmk/api-reference.rst:52 +msgid "Ticket attributes" +msgstr "Bilet nitelikleri" -#: ../system/integrations/smime/manage-certificates.rst:39 +#: ../system/integrations/checkmk/api-reference.rst:47 msgid "" -"Once you've added a public-key certificate, you can import its matching " -"private key." +"are optional, and can be used to **adjust settings** on newly created " +"tickets (*e.g.,* set the owner, group, priority, or state)." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:42 +#: ../system/integrations/checkmk/api-reference.rst:50 msgid "" -"Private keys are for **your own organization only**; never ask your contacts " -"for their private keys." +"If you want to customize your Checkmk alert script, do it with these. Simply " +"add an extra “form” option for each one (``-F \"key=value\"``) to your " +"script's ``curl`` command line, as in the example above." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:0 +#: ../system/integrations/checkmk/api-reference.rst:54 +msgid "💡 **It's just an API endpoint!**" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:56 msgid "" -"S/MIME integration showing configured certificates and possible issues with " -"Logging" +"When using Checkmk integration, messages need to be formatted in a certain " +"way, but that *doesn't mean the messages actually have to come from Checkmk*." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:50 +#: ../system/integrations/checkmk/api-reference.rst:59 msgid "" -"A note is displayed on certificates with a matching private key (see line 2)." +"If you use another monitoring tool that's not officially supported by " +"Zammad, there's probably a way to make it work with your Checkmk callback " +"URL." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:52 -msgid "📤 **Certificates and private keys must be uploaded separately.**" +#: ../system/integrations/checkmk/api-reference.rst:63 +msgid "Checkmk Parameters" +msgstr "Checkmk Parametreleri" + +#: ../system/integrations/checkmk/api-reference.rst:65 +msgid "" +"When a notification is received, Zammad creates a new article containing the " +"details of the event that triggered it:" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:None +msgid "Checkmk article body" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:54 +#: ../system/integrations/checkmk/api-reference.rst:72 msgid "" -"If your certificate and private key are bundled together in the same file or " -"PEM block, import it twice (once using each button)." +"These details come from the fields listed below, which correspond to " +"parameters provided by Checkmk (``$NOTIFY_*``)." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:57 -msgid "Please note that bulk imports of private keys are not possible." +#: ../system/integrations/checkmk/api-reference.rst:75 +msgid "**Required fields are marked with an asterisk (\\*).**" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:60 -#, fuzzy -msgid "Download Certificate Data" -msgstr "Sertifika Ekle" +#: ../system/integrations/checkmk/api-reference.rst:79 +msgid "event_id\\*" +msgstr "event_id\\*" -#: ../system/integrations/smime/manage-certificates.rst:62 +#: ../system/integrations/checkmk/api-reference.rst:78 msgid "" -"You can download the earlier provided certificates and private keys at any " -"time from your Zammad instance." +"A unique ID for the system event. (``$NOTIFY_SERVICEPROBLEMID`` / " +"``$NOTIFY_HOSTPROBLEMID``)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:65 +#: ../system/integrations/checkmk/api-reference.rst:86 +msgid "host\\*" +msgstr "host\\*" + +#: ../system/integrations/checkmk/api-reference.rst:82 msgid "" -"Please note that passphrase-protected private keys stay protected and when " -"you download them, you have to know the passphrase to use them after " -"downloading." +"The hostname of the system that the event originated from. " +"(``$NOTIFY_HOSTNAME``)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:73 -msgid "Dialogue to download certificates or private keys" +#: ../system/integrations/checkmk/api-reference.rst:85 +msgid "" +"Used to determine if a new event belongs to an existing ticket. Also used in " +"the subject line of the resulting article (“ is ”)." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:73 -msgid "Download stored certificates and their keys" -msgstr "" +#: ../system/integrations/checkmk/api-reference.rst:96 +msgid "service" +msgstr "servis" -#: ../system/integrations/smime/manage-certificates.rst:78 +#: ../system/integrations/checkmk/api-reference.rst:89 msgid "" -"The ticket composer will set all outgoing messages to **signed and " -"encrypted** by default (assuming the required certificates exist)." +"The name of the service that the event originated from. " +"(``$NOTIFY_SERVICEDESC``)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:82 -msgid "These defaults can be modified on a per-group basis:" +#: ../system/integrations/checkmk/api-reference.rst:92 +msgid "Used to determine if a new event belongs to an existing ticket." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:None -msgid "Zammad allowing to choose the default behavior on per group basis" +#: ../system/integrations/checkmk/api-reference.rst:94 +#: ../system/integrations/checkmk/api-reference.rst:110 +msgid "Displayed as ``-`` when omitted." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:89 +#: ../system/integrations/checkmk/api-reference.rst:104 +msgid "state\\*" +msgstr "state\\*" + +#: ../system/integrations/checkmk/api-reference.rst:99 msgid "" -"Of course, agents can always manually change these settings on each email " -"they send out." +"The current state of the service or host in question. " +"(``$NOTIFY_SERVICESTATE`` / ``$NOTIFY_HOSTSTATE``)" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:4 -msgid "A certificate *and* private key for your own organization" -msgstr "Organizasyonunuz için bir sertifika *ve* özel anahtar" - -#: ../system/integrations/smime/prerequisites.rst:6 +#: ../system/integrations/checkmk/api-reference.rst:102 msgid "" -"(Use this to ✒️ **sign outgoing messages** and 🔓 **decrypt incoming " -"messages**.)" +"Used to detect when a ticket should be auto-closed (*i.e.,* on ``OK``/" +"``UP``). Also used in the subject line of the resulting article (“ is " +"”)." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:9 +#: ../system/integrations/checkmk/api-reference.rst:110 +msgid "text" +msgstr "metin" + +#: ../system/integrations/checkmk/api-reference.rst:107 msgid "" -"Certificates belonging your contacts, or their issuing certificate authority " -"(CA)" +"The output of the process that triggered the event. " +"(``$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:11 +#: ../system/integrations/checkmk/api-reference.rst:121 msgid "" -"(Use these to ✅ **verify incoming message signatures** and 🔒 **encrypt " -"outgoing messages**.)" +"The Object Manager attribute panel displays built-in and custom\n" +"attribute names." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:14 -#, fuzzy -msgid "🙋 **I'm new to S/MIME. Where can I get a certificate?**" -msgstr "🙋 **S/MIME'da yeniyim. Nereden bir sertifika alabilirim?**" +#: ../system/integrations/checkmk/api-reference.rst:121 +msgid "Find a complete list of ticket attributes in the Object Manager." +msgstr "" -#: ../system/integrations/smime/prerequisites.rst:16 +#: ../system/integrations/checkmk/api-reference.rst:123 msgid "" -"The easiest way to get certificates is to buy an annual subscription through " -"a commercial CA, such as:" +"Ticket attributes are entirely optional, and can be used to customize the " +"tickets that Checkmk creates. (Note that these attributes will be ignored if " +"a new event belongs to an existing ticket.)" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:19 +#: ../system/integrations/checkmk/api-reference.rst:128 msgid "" -"`Sectigo (formerly Comodo) `_" +"Why would you want to do this? Maybe you have only one IT guy, and all " +"system monitoring issues should be automatically assigned to him. Or, maybe " +"you're creating multiple notification rules so that database outages take " +"higher priority than disk space warnings." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:20 -msgid "`Secorio `_" -msgstr "`Secorio `_" +#: ../system/integrations/checkmk/api-reference.rst:135 +msgid "In most cases, you'll probably want to set one of the following:" +msgstr "" -#: ../system/integrations/smime/prerequisites.rst:21 -msgid "`GlobalSign `_" -msgstr "`GlobalSign `_" +#: ../system/integrations/checkmk/api-reference.rst:137 +msgid "group" +msgstr "grup" -#: ../system/integrations/smime/prerequisites.rst:23 -msgid "(Zammad is not affiliated with these CAs in any way.)" -msgstr "" +#: ../system/integrations/checkmk/api-reference.rst:139 +msgid "state" +msgstr "durum" -#: ../system/integrations/smime/prerequisites.rst:25 -msgid "" -"You can also generate your own self-signed certificates, but the process is " -"complicated and usually 🙅 **involves extra work for your contacts**." -msgstr "" +#: ../system/integrations/checkmk/api-reference.rst:140 +msgid "priority" +msgstr "öncelik" -#: ../system/integrations/smime/prerequisites.rst:29 +#: ../system/integrations/checkmk/api-reference.rst:142 msgid "" -"Bear in mind that 🤝 **S/MIME only works if the other party is using it, too." -"**" +"but in practice, you can set almost any attribute, including :doc:`custom " +"ones you created through the Object Manager `." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:32 +#: ../system/integrations/checkmk/api-reference.rst:145 #, fuzzy -msgid "Certificate and Private Key Checks on Upload" -msgstr "Organizasyonunuz için bir sertifika *ve* özel anahtar" +msgid "Please note that the following attributes are **not customizable**:" +msgstr "Aşağıdaki ayarlardan şunları düzenleyebilirsin:" -#: ../system/integrations/smime/prerequisites.rst:34 +#: ../system/integrations/checkmk/api-reference.rst:147 +msgid "title" +msgstr "başlık" + +#: ../system/integrations/checkmk/api-reference.rst:148 +msgid "id" +msgstr "id" + +#: ../system/integrations/checkmk/api-reference.rst:149 +msgid "ticket number" +msgstr "bilet numarası" + +#: ../system/integrations/checkmk/api-reference.rst:151 +msgid "created_by_id" +msgstr "created_by_id" + +#: ../system/integrations/checkmk/api-reference.rst:152 +msgid "updated_by_id" +msgstr "updated_by_id" + +#: ../system/integrations/checkmk/api-reference.rst:155 +msgid "Which Values Can Be Set?" +msgstr "" + +#: ../system/integrations/checkmk/api-reference.rst:157 +msgid "😵 **Invalid values → unpredictable behavior**" +msgstr "😵 **Geçersiz değerler → beklenmeyen davranış**" + +#: ../system/integrations/checkmk/api-reference.rst:159 msgid "" -"The certificate and public key validation is based on the ``X509v3`` " -"extensions." +"If you provide a value that Zammad doesn't understand (*e.g.,* ``-F " +"\"priority=high\"``), it's not always clear what will happen. In some cases, " +"a ticket will be created with the default values instead - but in others, it " +"may not be created at all!" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:49 -msgid "Uploading a *client certificate*?" +#: ../system/integrations/checkmk/api-reference.rst:164 +msgid "So what values does Zammad understand, then? Well, it depends..." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:41 -msgid "The following attributes are required then:" +#: ../system/integrations/checkmk/api-reference.rst:168 +msgid "Use an email address or username:" +msgstr "Bir e-posta adresi veya kullanıcı adı kullan:" + +#: ../system/integrations/checkmk/api-reference.rst:190 +msgid "group & priority" +msgstr "grup ve öncelik" + +#: ../system/integrations/checkmk/api-reference.rst:175 +msgid "Refer to the dropdown menus in the ticket pane:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:39 -msgid "Subject Alternative Name (at least one email address has to be present)" +#: ../system/integrations/checkmk/api-reference.rst:0 +msgid "See possible values for certain attributes in the ticket pane." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:40 -msgid "Key Usage (``Digital Signature`` and/or ``Key Encipherment``)" +#: ../system/integrations/checkmk/api-reference.rst:187 +msgid "🙅 **Ticket state CANNOT be set this way!**" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:41 -msgid "Public key algorithm (either ``RSA`` or ``EC``)" +#: ../system/integrations/checkmk/api-reference.rst:189 +msgid "" +"Why? Because ``-F \"state=...\"`` is already used :ref:`as a Checkmk " +"parameter `." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:43 +#: ../system/integrations/checkmk/api-reference.rst:222 +msgid "Everything Else" +msgstr "Diğer Her Şey" + +#: ../system/integrations/checkmk/api-reference.rst:193 msgid "" -"The Extended Key Usage attribute is optional. If the certificate provides " -"the named attribute, than it must contain the value ``E-mail Protection``." +"To set any other attributes, it helps to know your way around the :docs:" +"`rails console `. Valid values are those that you can " +"set with a string:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:46 +#: ../system/integrations/checkmk/api-reference.rst:218 +msgid "These values can then be passed directly to the API:" +msgstr "" + +#: ../system/integrations/checkmk/index.rst:16 +msgid "How does it work?" +msgstr "Nasıl çalışır?" + +#: ../system/integrations/checkmk/index.rst:2 +msgid "Checkmk" +msgstr "Checkmk" + +#: ../system/integrations/checkmk/index.rst:4 +#, fuzzy msgid "" -"Please note that any usable email adress has to be prefixed with ``email:`` " -"or ``rfc822:``." +"`Checkmk `_ is a powerful IT monitoring tool that can " +"send real-time status alerts to Zammad via email or REST API. Set these " +"alerts up in Checkmk, and Zammad will automatically create, update, and " +"close tickets based on the health of your system:" msgstr "" +"`Checkmk`_, e-posta veya REST API aracılığıyla Zammad'a gerçek zamanlı durum " +"uyarıları gönderebilen güçlü bir BT izleme aracıdır. Bu uyarıları Checkmk'te " +"ayarlayın ve Zammad, sisteminizin sağlığına göre otomatik olarak biletler " +"oluşturacak, güncelleyecek ve kapatacaktır:" -#: ../system/integrations/smime/prerequisites.rst:49 -msgid "The named public key algorithms are mandatory for private keys as well." +#: ../system/integrations/checkmk/index.rst:14 +msgid "Screenshot of ticket created by Checkmk notifications" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:54 -msgid "Uploading a *CA certificate*?" -msgstr "" +#: ../system/integrations/checkmk/index.rst:14 +msgid "Multiple alerts, same ticket." +msgstr "Çoklu uyarılar, aynı bilet." -#: ../system/integrations/smime/prerequisites.rst:52 +#: ../system/integrations/checkmk/setup-guide.rst:2 +msgid "Setup Guide" +msgstr "Kurulum Kılavuzu" + +#: ../system/integrations/checkmk/setup-guide.rst:4 msgid "" -"In the case of an uploaded CA certificate, providing the value ``CA:TRUE`` " -"in the attribute *Basic Contstraints*, the previously mentioned attributes " -"are not verified." +"Whenever the Checkmk integration is enabled, Zammad listens for messages on " +"its API and over email. As long as those messages follow the required " +"format, Zammad will create new tickets (or find and update existing ones) " +"based on the message contents." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:56 +#: ../system/integrations/checkmk/setup-guide.rst:10 msgid "" -"In general, the usage of any expired (``Not After``) or not yet valid (``Not " -"Before``) certificate is denied for outgoing emails." +"That means that “setting up Checkmk integration” is simply a matter of " +"**adding configuration to your Checkmk site**: telling it when to send these " +"messages and what to say. To do that, you'll need to create a new " +"**notification rule** (see `Checkmk's official docs `_ for help with that)." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:59 -#, fuzzy -msgid "Example certificate:" -msgstr "Sertifika Ekle" - -#: ../system/integrations/smime/prerequisites.rst:85 +#: ../system/integrations/checkmk/setup-guide.rst:17 msgid "" -"Please note that Zammad will distrust senders by default. This means that " -"you're always required to provide certificate data, no matter if for signing " -"or encrypting." +"As part of this new rule, you'll have to choose a **notification method** " +"(*i.e.,* a script to execute whenever the rule is triggered). This script " +"will be written by you (samples below), and contain the logic for sending " +"API/email messages to Zammad:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:89 -msgid "This is by design and can't be adjusted." +#: ../system/integrations/checkmk/setup-guide.rst:26 +msgid "Checkmk \"New Rule\" dialog" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:4 +#: ../system/integrations/checkmk/setup-guide.rst:26 msgid "" -"All of the system's latest S/MIME activity is displayed in the **Recent " -"Logs** section." -msgstr "" - -#: ../system/integrations/smime/troubleshooting.rst:11 -msgid "Sample entries of in- and outgoing S/MIME related emails." +"Find your custom scripts in the Checkmk WATO under **Notifications > New " +"Rule > Notification Method**." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:11 +#: ../system/integrations/checkmk/setup-guide.rst:29 msgid "" -"Logs report the status and details of all mail, both incoming and outgoing, " -"that used signing/verification or encryption/decryption." +"Once you're done setting up your new rule, you're all set! New tickets " +"should start coming in and auto-updating any time your rule is triggered." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:14 +#: ../system/integrations/checkmk/setup-guide.rst:33 msgid "" -"This log does **not** include email sent by :doc:`triggers ` or the :doc:`scheduler `. For those, check your " -"``production.log``." +"(If you need help troubleshooting, be sure to check the :ref:`checkmk-recent-" +"logs`.)" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:20 -msgid "Common Issues" -msgstr "" +#: ../system/integrations/checkmk/setup-guide.rst:38 +msgid "API Alerts" +msgstr "API Uyarıları" -#: ../system/integrations/smime/troubleshooting.rst:30 -msgid "I received a signed/encrypted email before I set up S/MIME integration" +#: ../system/integrations/checkmk/setup-guide.rst:40 +msgid "" +"To add these scripts in the Checkmk WATO, copy them into your Checkmk " +"installation directory and make them executable. (Be sure to replace the " +"``zammad.example.com`` callback URL with the one found in your admin panel.)" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:23 +#: ../system/integrations/checkmk/setup-guide.rst:60 +msgid "Service notification" +msgstr "Servis bildirimi" + +#: ../system/integrations/checkmk/setup-guide.rst:46 msgid "" -"No problem. Once S/MIME has been enabled and the appropriate certificates " -"have been added, agents will be prompted to retry verification/decryption on " -"matching emails." +"For updates on the status of the software running on your server (*e.g.,* " +"postgres)." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:0 -msgid "Screenshot of user prompt to retry decryption" +#: ../system/integrations/checkmk/setup-guide.rst:75 +msgid "Host notification" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:38 -msgid "The 🔒 **Encrypt** button is disabled" +#: ../system/integrations/checkmk/setup-guide.rst:63 +msgid "For updates on the status of the server itself." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:33 -#, fuzzy -msgid "Have you added the recipient's certificate?" -msgstr "Alıcının sertifikasının geçerli olduğundan emin misiniz?" - -#: ../system/integrations/smime/troubleshooting.rst:34 +#: ../system/integrations/checkmk/setup-guide.rst:77 #, fuzzy -msgid "Are you sure the recipient's certificate is valid?" -msgstr "Alıcının sertifikasının geçerli olduğundan emin misiniz?" +msgid "🤔 **What's with all the env vars?**" +msgstr "🤔 **OAuth neyin nesi?**" -#: ../system/integrations/smime/troubleshooting.rst:35 -msgid "Have you checked your ``production.log`` for more details?" +#: ../system/integrations/checkmk/setup-guide.rst:79 +msgid "" +"Whenever Checkmk runs these scripts, it needs to provide some information " +"about the event that triggered the notification. This information is passed " +"in the form of these ``$NOTIFY_*`` environment variables." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:37 +#: ../system/integrations/checkmk/setup-guide.rst:85 msgid "" -"If encryption doesn't work in the composer, it won't work in :doc:`triggers " -"` or the :doc:`scheduler ` either!" +"You can specify additional parameters to pass to the script when you're " +"setting up your notification rule, but the ones you see here are all " +"provided by default." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:42 -msgid "The ✅ **Sign** button is disabled" -msgstr "" +#: ../system/integrations/checkmk/setup-guide.rst:90 +msgid "Email Alerts" +msgstr "E-posta Uyarıları" -#: ../system/integrations/smime/troubleshooting.rst:41 +#: ../system/integrations/checkmk/setup-guide.rst:94 msgid "" -"Have you added **both the certificate and private key** for your " -"organization?" +"🐞 **There are known bugs** in Zammad's processing of email from Checkmk. " +"This section will be completed once they have been resolved. (Learn more at " +"GitHub issues `#2377 `_ & " +"`#2180 `_.)" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:42 +#: ../system/integrations/checkmk/setup-guide.rst:100 +msgid "In the meantime, we encourage you to set up API alerts instead." +msgstr "" + +#: ../system/integrations/clearbit.rst:2 +msgid "Clearbit" +msgstr "Clearbit" + +#: ../system/integrations/clearbit.rst:4 msgid "" -"Does the email address on the certificate match the email address of the " -"agent/group composing the email?" +"With our Clearbit integration, you can easily enrich the information " +"provided by Zammad. If the customers or agents email address is known to " +"Clearbit, it will share all information it has regarding the user with " +"Zammad. Those information can include the following:" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:45 -msgid "Error: “Fingerprint already taken”" -msgstr "Hata: \"Parmak izi zaten alındı\"" +#: ../system/integrations/clearbit.rst:9 +msgid "Avatar" +msgstr "Avatar" -#: ../system/integrations/smime/troubleshooting.rst:45 -#, fuzzy -msgid "Are you sure you haven't added this certificate already?" -msgstr "Bu sertifikayı zaten eklemediğinizden emin misiniz?" +#: ../system/integrations/clearbit.rst:10 +msgid "Address information" +msgstr "Adres bilgisi" -#: ../system/integrations/smime/troubleshooting.rst:48 -msgid "Error: “❌ invalid byte sequence in UTF-8”" -msgstr "" +#: ../system/integrations/clearbit.rst:11 +msgid "Website information" +msgstr "Web site bilgisi" -#: ../system/integrations/smime/troubleshooting.rst:48 -msgid "Please ensure to provide PEM formatted certificate and keys." +#: ../system/integrations/clearbit.rst:12 +msgid "A BIO (as Note by default)" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:49 -msgid "Did you check if the provided file is a valid certificate or key?" +#: ../system/integrations/clearbit.rst:14 +msgid "" +"If needed, you can add further custom objects and add mappings to them, so " +"the Clearbit information can be filled within the database. In general you " +"can get any information from Clearbit, as long as you have a mapping to an " +"Zammad object." msgstr "" -#: ../system/integrations/zabbix.rst:2 -msgid "Zabbix Integration" -msgstr "Zabbix Entegrasyonu" - -#: ../system/integrations/zabbix.rst:5 +#: ../system/integrations/clearbit.rst:21 msgid "" -"This guide describes how to integrate your Zabbix 5.4 installation with " -"Zammad using the Zabbix webhook feature. This guide will provide " -"instructions on setting up a media type, a user and an action in Zabbix." +"Clearbit does have a mapping of fields like LDAP and Exchange have, but does " +"not \"win\" against Zammad information. This means that if you have e.g. the " +"last name field filled in already and Clearbit has other information on " +"that, it will not be updated." msgstr "" -#: ../system/integrations/zabbix.rst:12 -msgid "Zammad with enabled HTTP Token Authentication" +#: ../system/integrations/clearbit.rst:26 +msgid "" +"However: If let's say the last name has been set by Clearbit and Zammad " +"notices that the last name on the Clearbit source has changed, Zammad will " +"also update this value." msgstr "" -#: ../system/integrations/zabbix.rst:13 -#, fuzzy -msgid "Zabbix version 5.4 or higher" -msgstr "Zabbix versiyonu 5.0 veya daha yüksek" - -#: ../system/integrations/zabbix.rst:16 -msgid "Setting up a Zammad" +#: ../system/integrations/clearbit.rst:33 +msgid "" +"The configuration of Clearbit is really easy and done fast! Just login to " +"your Clearbit-Account, go to \"API\" and copy the secret-API-Key." msgstr "" -#: ../system/integrations/zabbix.rst:18 -msgid "Enable **API Token Access** in Settings > System > API." +#: ../system/integrations/clearbit.rst:38 +msgid "" +"Now change to your Zammad instance, go to Integrations (System) -> Clearbit " +"in the admin panel. Paste your API-Key into the API-Key-Field and decide if " +"Zammad should create unknown Organizations automatically, if the user does " +"not have one yet (and Clearbit knows it). The shared option decides if the " +"new organizations Zammad creates with Clearbit should be shared ones." msgstr "" -#: ../system/integrations/zabbix.rst:20 +#: ../system/integrations/clearbit.rst:47 msgid "" -"Create a **new user** for a Zabbix alerter with an **email address** and " -"create a personal user token with **ticket.agent** permissions." +"If you're unsure what option to choose, better stick with \"no\". You can " +"also learn more about :doc:`/manage/organizations/index`." msgstr "" -#: ../system/integrations/zabbix.rst:24 -#, fuzzy -msgid "Zabbix Webhook Configuration" -msgstr "Zabbix Webhook yapılandırması" +#: ../system/integrations/clearbit.rst:52 +msgid "" +"The Mapping option works similar to the mapping within the Exchange and LDAP " +"sync. You can add further mappings for e.g. custom fields if you need more " +"information that Clearbit can provide." +msgstr "" -#: ../system/integrations/zabbix.rst:27 -#, fuzzy -msgid "Create a Global Macro" -msgstr "Bir global makro oluştur" +#: ../system/integrations/clearbit.rst:58 +msgid "" +"If you want to add more Clearbit fields and want to learn more about " +"available fields on their API, you can take a look at their `API " +"documentation `_." +msgstr "" -#: ../system/integrations/zabbix.rst:29 +#: ../system/integrations/clearbit.rst:62 msgid "" -"Before setting up the **Webhook**, you need to setup the global macro " -"**{$ZABBIX.URL}**, which must contain the **URL** to the **Zabbix frontend**." +"If you're happy with the above chosen Settings and your mapping, just save " +"the changes and enable Clearbit integration. Zammad will now start polling " +"the Clearbit API as users contact you." msgstr "" -#: ../system/integrations/zabbix.rst:33 +#: ../system/integrations/clearbit.rst:68 msgid "" -"In the **Administration** > **Media types** section, import the `Template`_." +"Zammad does not synchronize with Clearbit on a regular basis, but on demand " +"if needed. This saves API calls." msgstr "" -#: ../system/integrations/zabbix.rst:38 -msgid "Open the added **Zammad** media type and set:" +#: ../system/integrations/clearbit.rst:73 +msgid "" +"Below the Settings and Mappings, you'll find our Integration log. You can " +"see what requests Zammad sent to Clearbit and also the APIs Response." msgstr "" -#: ../system/integrations/zabbix.rst:40 -msgid "**zammad\\_access\\_token** to the your **Personal User Token**" +#: ../system/integrations/clearbit.rst:78 +msgid "" +"By the way, you can also view the API log on the Clearbit website - the " +"information seen is basically the same." msgstr "" -#: ../system/integrations/zabbix.rst:41 +#: ../system/integrations/clearbit.rst:84 +#, fuzzy +msgid "Example When Adding a User" +msgstr "Bir kullanıcı ekleme örneği" + +#: ../system/integrations/clearbit.rst:86 msgid "" -"**zammad\\_url** to the **frontend URL** of your **Zammad** installation" +"To show you how fast information is added, we added a small Screencast " +"below. This shows the creation of the User Alex from Clearbit. As we already " +"set the last name of Alex to \"X\", Zammad did not update it. What Zammad " +"did was to add further information it received from Clearbit." msgstr "" -#: ../system/integrations/zabbix.rst:43 -msgid "**zammad\\_customer** to your **Zammad user email**." +#: ../system/integrations/cti/generic.rst:2 +msgid "CTI (generic)" +msgstr "CTI (generic)" + +#: ../system/integrations/cti/includes/introduction.include.rst:1 +msgid "" +"This integration enables Zammad to provide a caller log to your agents. With " +"this your agents can greet your customers by their name and are supported by " +"Zammad with automatically opening a new ticket dialog or the user profile." msgstr "" -#: ../system/integrations/zabbix.rst:44 +#: ../system/integrations/cti/includes/introduction.include.rst:6 msgid "" -"**zammad\\_enable\\_tags** to **true** or **false** to enable or disable " -"trigger tags. **Important**: if you enable tag support, each tag is set with " -"a separate request." +"Click the toggle next to the heading to activate or deactivate this " +"integration." msgstr "" -#: ../system/integrations/zabbix.rst:48 +#: ../system/integrations/cti/includes/introduction.include.rst:9 msgid "" -"If you want to prioritize issues according to **severity** values in Zabbix, " -"you can define mapping parameters:" +"If you want to learn more on how your agents can use this function, please " +"refer the :user-docs:`user documentation `." msgstr "" -#: ../system/integrations/zabbix.rst:51 -msgid "**severity\\_**: Zammad priority ID" +#: ../system/integrations/cti/includes/introduction.include.rst:14 +msgid "" +"Automatically opening new ticket dialogues or user profiles requires agent " +"to extension mapping - see more below." msgstr "" -#: ../system/integrations/zabbix.rst:53 -msgid "Click the **Update** button to save the **Webhook** settings." +#: ../system/integrations/cti/includes/introduction.include.rst:20 +msgid "Please note the following limitations to reduce confusion later on:" msgstr "" -#: ../system/integrations/zabbix.rst:55 -msgid "" -"To receive notifications in **Zammad**, you need to create a **Zabbix user** " -"and add **Media** with the **Zammad** type." +#: ../system/integrations/cti/includes/introduction.include.rst:22 +msgid "CTI integrations provide caller log functions only." msgstr "" -#: ../system/integrations/zabbix.rst:58 +#: ../system/integrations/cti/includes/introduction.include.rst:23 msgid "" -"For **Send to**: enter any text, as this value is not used, but is required." +"This integration does not provide any VoIP functionalities; you can't make " +"phone calls from within Zammad." msgstr "" -#: ../system/integrations/zabbix.rst:61 +#: ../system/integrations/cti/includes/introduction.include.rst:25 msgid "" -"For more information, use the `Zabbix documentation `_." +"If your browser supports ``tel``-URLs, you can click on phone numbers for " +"automatic dialing. This requires additional software / configuration on your " +"agent's computers." msgstr "" -#: ../system/maintenance.rst:2 -msgid "Maintenance" -msgstr "Bakım" +#: ../system/integrations/cti/generic.rst:9 +#: ../system/integrations/cti/placetel.rst:14 +#: ../system/integrations/cti/sipgate.rst:14 +msgid "Please provide the following requirements:" +msgstr "" -#: ../system/maintenance.rst:4 +#: ../system/integrations/cti/generic.rst:11 msgid "" -"Zammad comes with a maintenance mode that you can use for e.g. updating the " -"instance or changing settings while restricting availability and functions." +"A telephone system that supports webhooks (outbound) (best option are those " +"that allow customizing the calls)." msgstr "" -#: ../system/maintenance.rst:13 -msgid "Mode" -msgstr "Mod" +#: ../system/integrations/cti/generic.rst:13 +msgid "A unique Call-ID during the call session." +msgstr "" -#: ../system/maintenance.rst:8 -msgid "The mode setting allows you to enable or disable the maintenance mode." +#: ../system/integrations/cti/generic.rst:14 +msgid "Call event data (both numbers and direction)." msgstr "" -#: ../system/maintenance.rst:10 -msgid "Defaults to *off*." +#: ../system/integrations/cti/generic.rst:15 +msgid "Your Zammad instance must be reachable for your telephony system." msgstr "" -#: ../system/maintenance.rst:12 +#: ../system/integrations/cti/generic.rst:17 msgid "" -"The maintenance mode will restrict access to administrative roles only. This " -"means agents and customers are logged off." +"If you want to learn more on what kind of requests are supported by Zammad " +"and what it expects, please consult our :docs:`CTI-API documentation `." msgstr "" -#: ../system/maintenance.rst:23 -msgid "@Login" -msgstr "@Giriş" +#: ../system/integrations/cti/generic.rst:22 +#: ../system/integrations/cti/placetel.rst:27 +#: ../system/integrations/cti/sipgate.rst:30 +#, fuzzy +msgid "Available Settings" +msgstr "Posta Sunucusu Ayarları" -#: ../system/maintenance.rst:16 -msgid "" -"This setting allows you to provide a login message within a green banner " -"above the login screen. Click into the green banner in the settings page to " -"adjust your message. To activate the message, activate the *@Login* setting." -msgstr "" +#: ../system/integrations/cti/generic.rst:29 +#: ../system/integrations/cti/placetel.rst:41 +#: ../system/integrations/cti/sipgate.rst:40 +#, fuzzy +msgid "Endpoint Settings" +msgstr "Ayarlar Listesi" -#: ../system/maintenance.rst:0 +#: ../system/integrations/cti/generic.rst:25 msgid "" -"Screenshot showing the default login message within the\n" -"settings page" +"Zammad will list your generic CTI endpoint here. It contains a unique token " +"so ensure to keep this URL save." msgstr "" -#: ../system/maintenance.rst:26 +#: ../system/integrations/cti/generic.rst:28 msgid "" -"Send an informative message to **all active sessions**. This comes handy to " -"inform your agents e.g. about mayor outages or to force reloads after " -"configuration changes." +"You'll need this endpoint for your PBX to talk to Zammad, see :docs:`CTI-API " +"documentation `." msgstr "" -#: ../system/maintenance.rst:31 -msgid "This is the messages title (slightly bigger than the normal message)." +#: ../system/integrations/cti/includes/important-dont-forget-saving.include.rst:3 +msgid "" +"All following options **do not save automatically**. Always use the Save " +"button on the lower end of the integration page!" msgstr "" -#: ../system/maintenance.rst:34 -msgid "The text you want to provide to your logged in sessions." -msgstr "" +#: ../system/integrations/cti/generic.rst:43 +#: ../system/integrations/cti/placetel.rst:49 +#: ../system/integrations/cti/sipgate.rst:52 +#, fuzzy +msgid "Call Settings" +msgstr "Ayarlar" -#: ../system/maintenance.rst:39 -msgid "Reload application" +#: ../system/integrations/cti/generic.rst:39 +#: ../system/integrations/cti/placetel.rst:49 +#: ../system/integrations/cti/sipgate.rst:37 +#: ../system/integrations/cti/sipgate.rst:50 +msgid "Inbound" msgstr "" -#: ../system/maintenance.rst:37 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:1 msgid "" -"Selecting this option will change the message acceptance button from *Close* " -"(with nothing happening) to *Continue session*, which forces the application " -"to reload." +"This option allows you to block specific incoming caller IDs. It allows you " +"to temporarily reject e.g. spam callers without having to contact providers " +"or PBX administrators." msgstr "" -#: ../system/maintenance.rst:43 -msgid "" -"If you have customers that are logged in to Zammad, they'll also be notified " -"if they're active in that moment." -msgstr "" +#: ../system/integrations/cti/includes/inbound-calls.include.rst:11 +#, fuzzy +msgid "Caller ID to block" +msgstr "arayan ID verisi" -#: ../system/maintenance.rst:48 -msgid "Example without reload application" +#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 +msgid "Provide caller IDs to block in ``E.164`` format." msgstr "" -#: ../system/maintenance.rst:52 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:8 msgid "" -"Message setting within Zammad's admin settings without ticket reload " -"application setting." +"Your telephony system has to support this function. Zammad will send a " +"``reject`` response which will cause your telephony system to hang up the " +"call. To callers this usually will feel like the line is busy." msgstr "" -#: ../system/maintenance.rst:0 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:14 msgid "" -"Screenshot showing the send message settings without ticket\n" -"reload application set" +"Provide a meaningful note for your fellow administrators to remind yourself " +"why you've chosen to block the number." msgstr "" -#: ../system/maintenance.rst:61 ../system/maintenance.rst:85 -msgid "" -"The modal all other active sessions will see upon pressing *Send to clients*." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:17 +#: ../system/integrations/cti/sipgate.rst:40 +msgid "Outbound" msgstr "" -#: ../system/maintenance.rst:0 +#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:1 msgid "" -"Screenshot showing modal caused by maintenance's message\n" -"without reload application ticket" +"In many cases you may want to use a different caller ID depending on the " +"destination you're calling. This may apply due to specific connection rates " +"to other countries or because you want your customer to feel you're calling " +"from the same country." msgstr "" -#: ../system/maintenance.rst:72 -msgid "Example with reload application" +#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:6 +msgid "This option expects ``E.164`` number formats." msgstr "" -#: ../system/maintenance.rst:76 -msgid "" -"Message setting within Zammad's admin settings with ticket reload " -"application setting." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 +#, fuzzy +msgid "Destination caller ID" +msgstr "Hedef Grup" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:5 +msgid "The caller ID or number you're trying to call." msgstr "" -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing the send message settings with ticket\n" -"reload application set" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:7 +msgid "You can use wildcards for e.g. country specific outbound numbers like:" +msgstr "" + +#: ../system/integrations/cti/includes/outbound-calls.include.rst:9 +msgid "``49*`` for Germany" msgstr "" -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing modal caused by maintenance's message\n" -"with reload application ticket" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:10 +msgid "``4930*`` for Berlin / Germany landlines" msgstr "" -#: ../system/monitoring.rst:2 -msgid "Monitoring" -msgstr "İzleme" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 +msgid "``33*`` for France" +msgstr "" -#: ../system/monitoring.rst:4 -#, fuzzy -msgid "" -"This function is only available in self hosted instances. If you use Zammad " -"in our cloud, we are monitoring the system on our own and take steps to fix " -"potential problems directly." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:15 +msgid "Set Outbound caller ID" msgstr "" -"**Lütfen dikkat:** Barındırılan örnekleri izlediğimiz ve sorunları " -"düzelttiğimiz için bu yalnızca kendi kendine barındırılan örneklerde " -"kullanılabilir." -#: ../system/monitoring.rst:11 -#, fuzzy +#: ../system/integrations/cti/includes/outbound-calls.include.rst:14 msgid "" -"On the monitoring page, you can see the current health state of Zammad under " -"\"*Current Status*\" at the bottom. This can be useful if you want to have a " -"look if everything is up and running. As an example, you could have a look " -"in the monitoring when you assume that some emails aren't processed from " -"Zammad." +"The outbound caller ID to set (the number your customer sees on his display) " +"in ``E.164`` number format." msgstr "" -"İzleme sayfasında, Zammad'ın mevcut sağlık durumunu görebilirsiniz. Bu, " -"örneğin artık e-posta almadığınızı düşünüyorsanız, Sunucunuzda oturum " -"açmadan önce buraya bir göz atabilirsiniz." -#: ../system/monitoring.rst:17 -msgid "**Can't receive an email and the monitoring response is \"healthy\"?**" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 +msgid "Provide a short description for fellow administrators." msgstr "" -#: ../system/monitoring.rst:19 +#: ../system/integrations/cti/includes/generic-cti-support-note.includes.rst:3 msgid "" -"Zammad will just inform you about unprocessable emails. This is not the case " -"for oversized emails. You can adjust the maximum email size in :doc:`../" -"channels/email/settings`." +"This option requires your PBX to send a specific request to Zammad *before " +"dialing*. Please consult the :docs:`CTI API ` in case " +"you're not sure." msgstr "" -#: ../system/monitoring.rst:24 +#: ../system/integrations/cti/generic.rst:52 +#: ../system/integrations/cti/placetel.rst:54 +#: ../system/integrations/cti/sipgate.rst:59 #, fuzzy -msgid "Monitoring API" -msgstr "İzleme" +msgid "Other Settings" +msgstr "Ayarlar" -#: ../system/monitoring.rst:26 +#: ../system/integrations/cti/includes/other-settings-intro.include.rst:1 msgid "" -"Beside the indication in the monitoring page, you can also use an external " -"monitoring tool to monitor Zammad's health. To request the health of Zammad, " -"you need to provide the API key (token) to the external monitoring tool. You " -"can copy the token from the \"*Current Token*\" field as well as the whole " -"API endpoint of your system (\"*Health Check*\" field), in which the API " -"token is already included." +"Below you can find all available additional settings for this CTI " +"integration. For your overview we're sorting them by appearance and " +"reference their description first." msgstr "" -#: ../system/monitoring.rst:37 -msgid "Screenshot showing Current Token and Health Check" +#: ../system/integrations/cti/includes/default-caller-id.include.rst:2 +#: ../system/integrations/cti/includes/default-caller-id.include.rst:1 +msgid "Default caller ID for outbound calls" msgstr "" -#: ../system/monitoring.rst:37 -msgid "Screenshot showing Token and Health Check" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:16 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:15 +msgid "Shown records in caller log" msgstr "" -#: ../system/monitoring.rst:39 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:2 msgid "" -"In addition to that, you can reset the auto-generated token to make sure " -"that already configured monitoring systems won't work anymore. So, please " -"use this \"*Reset*\" button only if you know what you do!" +"Allows you to set the number of shown caller log entries for all users. You " +"can choose from the following values:" msgstr "" -#: ../system/monitoring.rst:44 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:5 +msgid "60 (default)" +msgstr "" + +#: ../system/integrations/cti/includes/records-caller-log.include.rst:6 #, fuzzy -msgid "Example Output" -msgstr "Örnek" +msgid "120" +msgstr "20" -#: ../system/monitoring.rst:0 -msgid "No issues found" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:7 +msgid "180" msgstr "" -#: ../system/monitoring.rst:48 ../system/monitoring.rst:60 -msgid "**Indicator in Zammad**:" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:8 +msgid "240" +msgstr "240" + +#: ../system/integrations/cti/includes/records-caller-log.include.rst:9 +msgid "300" msgstr "" -#: ../system/monitoring.rst:0 -msgid "Screenshot showing monitoring with no issues" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:11 +msgid "**🥵 Potential performance issue**" msgstr "" -#: ../system/monitoring.rst:54 ../system/monitoring.rst:66 -msgid "**API response**::" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:13 +msgid "" +"Setting this setting higher than 60 may cause serious performance issues on " +"very busy instances. Keep in mind that this setting causes Zammad to poll " +"and send up to 300 records to *all active agent sessions* in very short time " +"periods." msgstr "" -#: ../system/monitoring.rst:0 -msgid "Issues were found" +#: ../system/integrations/cti/generic.rst:73 +msgid "Caller Log Filter" msgstr "" -#: ../system/monitoring.rst:0 -msgid "Screenshot showing monitoring with issues" +#: ../system/integrations/cti/generic.rst:55 +msgid "" +"This function allows you to provide call information based on e.g. queues " +"only to agents that really need the information." msgstr "" -#: ../system/objects.rst:2 -msgid "Objects" -msgstr "Nesneler" +#: ../system/integrations/cti/generic.rst:58 +msgid "" +"Why? If you have a team for several countries or departments, you don't want " +"to bug your agents from other departments. Leaving these options empty will " +"fallback to showing everything to everyone." +msgstr "" -#: ../system/objects.rst:4 +#: ../system/integrations/cti/generic.rst:64 +#, fuzzy +msgid "Destination caller ID or Queue" +msgstr "Hedef Grup" + +#: ../system/integrations/cti/generic.rst:63 msgid "" -"In Zammad you can add your own fields to tickets, users, organizations and " -"even groups (these are called \"objects\"). This can be useful if you need " -"to add further information to a ticket or any other object in Zammad and the " -"information doesn't fit in any existing field." +"This depends on your PBX and usually is either a queue ID, phone number or " +"extension." msgstr "" -#: ../system/objects.rst:11 +#: ../system/integrations/cti/generic.rst:69 +msgid "Agents" +msgstr "" + +#: ../system/integrations/cti/generic.rst:67 msgid "" -"Try to avoid deleting attributes (and disable them instead) as Zammad might " -"run into unexpected conditions if they are referenced somewhere." +"Select the agents that are responsible for the group. These agents will then " +"see caller log entries and call notifications fitting to said queue." msgstr "" -#: ../system/objects.rst:16 +#: ../system/integrations/cti/generic.rst:0 msgid "" -"Here's an overview of object attributes. On the upper right you can add new " -"attributes. By default, there will be no custom fields - standard attributes " -"will be grayed out, you can't delete or change those. You can edit custom " -"attributes (they are displayed in black font and have a trash bin on the " -"right side) just by clicking on them." +"Screenshot showing the caller log filter table with pre filled sample data" msgstr "" -#: ../system/objects.rst:24 +#: ../system/integrations/cti/includes/recent-logs.include.rst:6 msgid "" -"Attributes you add to Zammad, no matter if they have default values or not, " -"will not update existing information. This means a new ticket field " -"technically will be empty unless you populate it." +"With recent logs Zammad allows you to view the latest calls for the CTI " +"functionality. This usually comes in handy, when you're looking for errors." msgstr "" -#: ../system/objects.rst:28 +#: ../system/integrations/cti/includes/recent-logs.include.rst:0 msgid "" -"Especially in ticket scope this also means that newly added attributes will " -"be indicated as \"changed\" to agents that view the ticket. This may " -"interfere with Zammad's tabs behavior." +"Screenshot showing several incoming requests within Recent logs section." msgstr "" -#: ../system/objects.rst:40 -#, fuzzy -msgid "Ordering Attributes" -msgstr "Bilet nitelikleri" +#: ../system/integrations/cti/includes/recent-logs.include.rst:16 +msgid "I'm just here to clear floats up." +msgstr "" -#: ../system/objects.rst:42 +#: ../system/integrations/cti/includes/recent-logs.include.rst:20 msgid "" -"Since Zammad introduced :doc:`/system/core-workflows` the need to have a " -"custom positioning for attributes has become more important than ever." +"By clicking on the entry of interest, Zammad will provide more details on " +"the call in question. You'll see the payload it received and also the " +"response that was sent." msgstr "" -#: ../system/objects.rst:45 +#: ../system/integrations/cti/includes/recent-logs.include.rst:0 msgid "" -"To adjust the position of such an attribute, simply click on the attribute " -"entry in question, scroll down and adjust the position number. Please note " -"that you cannot change the positioning of default attributes." +"Screenshot showing detailed information of a specific log entry of recent " +"logs" msgstr "" -#: ../system/objects.rst:49 +#: ../system/integrations/cti/includes/recent-logs.include.rst:31 +msgid "x" +msgstr "" + +#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 +#: ../system/integrations/cti/includes/troubleshooting.include.rst:9 +msgid "My Phone page stays blank, signalling does work..." +msgstr "" + +#: ../system/integrations/cti/includes/troubleshooting.include.rst:5 msgid "" -"In case two attributes have the same position value, Zammad will sort " -"alphabetically by name automatically." +"If you've made sure that signalling works (check Recent logs) and your " +"Caller Log still stays empty, please ensure that you only configured one CTI " +"integration version. Specifically defining more than one agent mapping on " +"the different integration variants will be the issue." msgstr "" -#: ../system/objects.rst:None +#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 +msgid "Clear the not needed agent mapping and reload your browser page." +msgstr "" + +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:1 msgid "" -"Screenshot showing custom attribute entries ordered in between default ones" +"By mapping your agents extension to their existing Zammad users, Zammad can " +"provide a new ticket dialog or open the user profile for the agent that " +"picks up the call." msgstr "" -#: ../system/objects.rst:56 -msgid "Updating Database After Adding or Editing Attributes" +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:5 +msgid "" +"This speeds up ticket aiding, no matter if it's for existing tickets or new " +"ones!" msgstr "" -#: ../system/objects.rst:58 +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:8 msgid "" -"When adding or changing attributes, Zammad will not apply the changes " -"instantly, but instead shows you the changed attributes first. If you're " -"ready to go, just click on \"Update database\" to apply the changes to " -"Zammad. If you made a mistake or just want to discard your changes, click " -"\"Discard changes\"." +"To see it work from the agent's perspective, have a look on :user-docs:`user " +"documentation `." msgstr "" -#: ../system/objects.rst:64 +#: ../system/integrations/cti/placetel.rst:2 +msgid "Placetel CTI" +msgstr "Placetel CTI" + +#: ../system/integrations/cti/placetel.rst:16 +#, fuzzy +msgid "You need an administrative Placetel account for your organization." +msgstr "🔑 **Organizasyonunuz için bir yönetici hesabı kullanın.**" + +#: ../system/integrations/cti/placetel.rst:17 +#: ../system/integrations/cti/sipgate.rst:20 msgid "" -"After applying the changes with \"Update Database\", a restart of Zammad is " -"**mandatory**. If you don't perform it, you may experience unexpected " -"behavior or even errors. You may want to do this kind of configuration " -"during maintenance windows." +"Your Zammad instance must be allowed to communicate to external services." msgstr "" -#: ../system/objects.rst:72 -msgid "" -"Changes on objects require you to update the database to apply these changes." +#: ../system/integrations/cti/placetel.rst:18 +msgid "Placetel must be able to reach your Zammad instance." msgstr "" -#: ../system/objects.rst:75 -msgid "**🤓 Service restarts can be automated**" +#: ../system/integrations/cti/placetel.rst:22 +msgid ":doc:`provider-configurations/placetel`" msgstr "" -#: ../system/objects.rst:0 -msgid "Hosted environments automatically restart for you." +#: ../system/integrations/cti/placetel.rst:21 +msgid "" +"Learn how to configure Placetel to enable Zammad and Placetel to communicate " +"with each other." msgstr "" -#: ../system/objects.rst:0 +#: ../system/integrations/cti/placetel.rst:32 msgid "" -"If you're using a self-hosted installation you can use :docs:`environment " -"variables `" +"The here listed endpoint settings are relevant for the :doc:`integration " +"configuration with Placetel `." msgstr "" -#: ../system/objects.rst:82 -#, fuzzy -msgid "System Attributes" -msgstr "Bilet nitelikleri" +#: ../system/integrations/cti/placetel.rst:37 +#: ../system/integrations/i-doit.rst:53 +msgid "Endpoint" +msgstr "" -#: ../system/objects.rst:84 +#: ../system/integrations/cti/placetel.rst:36 msgid "" -"Zammad comes with pre-configured attributes. Some of them can't be edited " -"via UI (or at all). This is required for proper operation of Zammad and not " -"a bug." +"This endpoint will be required for the Zammad integration within the " +"Placetel web interface." msgstr "" -#: ../system/objects.rst:90 -#, fuzzy -msgid "Ticket State" -msgstr "Bilet > Durum > Ad" +#: ../system/integrations/cti/placetel.rst:41 +msgid "API Token" +msgstr "" -#: ../system/objects.rst:92 +#: ../system/integrations/cti/placetel.rst:40 msgid "" -"If the pre-configured states aren't enough for you or you want to change " -"them, you can do so by clicking on the cogwheel icon in the state row in the " -"ticket tab. But you should be careful when changing pre-configured states. " -"This can lead to unwanted behavior in some cases." +"You'll receive this token within the ``Web API`` menu. Make sure to copy " +"this value, it's only shown once!" msgstr "" -#: ../system/objects.rst:None -msgid "Screenshot showing highlighted ticket state attribute" +#: ../system/integrations/cti/placetel.rst:71 +#: ../system/integrations/cti/sipgate.rst:77 +msgid "Phone Extension to Agent Mapping" msgstr "" -#: ../system/objects.rst:122 -#, fuzzy -msgid "Handling of states" -msgstr "Makro Yönetimi" +#: ../system/integrations/cti/placetel.rst:0 +msgid "Screenshot showing sample user mappings in between Placetel and Zammad" +msgstr "" -#: ../system/objects.rst:102 +#: ../system/integrations/cti/placetel.rst:64 msgid "" -"In the state configuration screen, you can add new states, disable states or " -"change states." +"You can find your agents Placetel username combination required within ⚙️ PBX " +"→ VoIP destinations. Within the \"Advanced settings\" section you're looking " +"for \"SIP user name\" and \"SIP server\"." msgstr "" -#: ../system/objects.rst:0 -msgid "Screenshot showing table of default ticket states" +#: ../system/integrations/cti/placetel.rst:68 +msgid "Combine these two like so: ``@``." msgstr "" -#: ../system/objects.rst:110 -msgid "" -"To add a new state, click on the \"New Ticket State\" button in the top " -"right corner. To change an existing state, simply click on the affected " -"state. This opens an edit dialog." +#: ../system/integrations/cti/placetel.rst:0 +msgid "Sample VoIP credentials for a Placetel user" msgstr "" -#: ../system/objects.rst:114 -msgid "" -"You can also clone a state or set them to \"Default for new tickets\" or " -"\"Default for follow-ups\" by clicking on the ⁝ action button and select the " -"desired function." +#: ../system/integrations/cti/provider-configurations/placetel.rst:2 +msgid "Setup Placetel connection for Zammad" msgstr "" -#: ../system/objects.rst:118 +#: ../system/integrations/cti/provider-configurations/placetel.rst:6 msgid "" -"*Default for new tickets* means that this state is used for every newly " -"created ticket." +"This configuration step requires a *full* administrative Placetel account. " +"You may receive forbidden error messages with Placetel in case your " +"permissions are not high enough." msgstr "" -#: ../system/objects.rst:121 +#: ../system/integrations/cti/provider-configurations/placetel.rst:10 msgid "" -"*Default for follow-ups* means that this state is used if the ticket is re-" -"opened after it was closed." +"The following actions can be configured via the `Placetel web interface " +"`_." msgstr "" -#: ../system/objects.rst:171 -#, fuzzy -msgid "Ticket state in detail" -msgstr "Bilet > Durum > Ad" - -#: ../system/objects.rst:125 -msgid "" -"Below you can find a description for each field and option. Please head over " -"to the :ref:`example ` to see the edit dialog." +#: ../system/integrations/cti/provider-configurations/placetel.rst:29 +msgid "Step 1: Activate Zammad integration" msgstr "" -#: ../system/objects.rst:129 +#: ../system/integrations/cti/provider-configurations/placetel.rst:14 msgid "" -"This is the name of the state and what you and your agents are seeing when " -"choosing a state somewhere (e.g. in tickets, trigger configuration)." +"Within Integrations, scroll down to Partner integrations and select Zammad." msgstr "" -#: ../system/objects.rst:137 +#: ../system/integrations/cti/provider-configurations/placetel.rst:17 msgid "" -"There are different state types you can choose from. By default, Zammad " -"comes with one state per state type." +"You can alternatively filter by \"Ticket Systems\" to reduce the number of " +"entries on the page. You'll still want to look for Partner integrations. 🤓" msgstr "" -#: ../system/objects.rst:140 +#: ../system/integrations/cti/provider-configurations/placetel.rst:21 msgid "" -"**new**: for states for tickets that are new and it hasn't been worked on " -"them" +"Within the Zammad integration now press \"Activate\". A new tab ``API`` " +"becomes available - open this tab." msgstr "" -#: ../system/objects.rst:142 +#: ../system/integrations/cti/provider-configurations/placetel.rst:24 msgid "" -"**open**: for states for tickets that are in progress and agents are working " -"on them" +"Now tick \"Enable Call Control / Notify API\" and paste the Placetel " +"endpoint from your Zammad instance into the field \"URL of your API " +"endpoint\". Save to apply the settings" msgstr "" -#: ../system/objects.rst:144 -msgid "**merged**: for states for tickets that are merged with other tickets" +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "Screencast showing how to activate the Zammad integration" msgstr "" -#: ../system/objects.rst:145 -msgid "" -"**pending reminder**: for states for tickets that are in progress and you " -"want to set a reminder. (default example: *pending reminder*)" +#: ../system/integrations/cti/provider-configurations/placetel.rst:51 +msgid "Step 2: Generate API Token for Placetel" msgstr "" -#: ../system/objects.rst:147 +#: ../system/integrations/cti/provider-configurations/placetel.rst:32 msgid "" -"**pending action**: for states for tickets that are waiting for a specified " -"time and then change their state (default example: *pending close*)" +"Go back to the integrations page and scroll down to \"Web API\". Generate a " +"new API token by using the \"Create a new API token\" button." msgstr "" -#: ../system/objects.rst:150 +#: ../system/integrations/cti/provider-configurations/placetel.rst:37 msgid "" -"**closed**: for states for tickets that are finished and do not need to be " -"processed further" +"If you already generated a token either use your existing token or reset it " +"by using above mentioned button. Placetel will ask you to conform this reset." msgstr "" -#: ../system/objects.rst:153 +#: ../system/integrations/cti/provider-configurations/placetel.rst:41 msgid "" -"⚠️ Choosing the correct state type is important! If you are in doubt, have a " -"look on the default states and their types!" +"Please keep in mind that existing API scripts may no longer work due to " +"token resets!" msgstr "" -#: ../system/objects.rst:158 -msgid "Ignore escalation" +#: ../system/integrations/cti/provider-configurations/placetel.rst:44 +msgid "" +"Copy the provided API token and insert it into the \"API Token\" field " +"within Zammad's Placetel integration." msgstr "" -#: ../system/objects.rst:157 +#: ../system/integrations/cti/provider-configurations/placetel.rst:47 msgid "" -"Here you can define whether tickets of this state will count to escalation " -"time or not." +"Apply your changes by using the \"Save\" button on the bottom of the " +"Placetel integration page and activate the Placetel integration." msgstr "" -#: ../system/objects.rst:161 +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 msgid "" -"You can create a note for the state to inform other admins about the state. " -"This has no effect on tickets." +"Screencast showing how to retrieve an API token from Placetel for Zammad" msgstr "" -#: ../system/objects.rst:165 -#, fuzzy -msgid "Set the state to *active* or *inactive*." -msgstr "aktifse veya değilse" +#: ../system/integrations/cti/provider-configurations/placetel.rst:73 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:77 +msgid "Step 3: Restrict the numbers to notify on" +msgstr "" -#: ../system/objects.rst:167 +#: ../system/integrations/cti/provider-configurations/placetel.rst:54 msgid "" -"it is technically possible to set all states to inactive. To keep Zammad " -"working in such a case, the inactive flag of one of the states is ignored." +"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " +"the the Integrations page of the Placetel web interface, go to \"Notify " +"API\"." msgstr "" -#: ../system/objects.rst:194 -#, fuzzy -msgid "Ticket state example" -msgstr "Bilet > Durum > Ad" - -#: ../system/objects.rst:174 +#: ../system/integrations/cti/provider-configurations/placetel.rst:58 msgid "" -"Let's assume we want to create a new state which indicates that the ticket " -"has to wait for a response of a third party (e.g. service contractor or " -"manufacturer) and we want to to be able to set a reminder." +"Lower on the page Placetel allows you to restrict the numbers to notify on. " +"You'll find this within the \"External routing API\" part." msgstr "" -#: ../system/objects.rst:178 +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 msgid "" -"First we give the new state a proper name. In this example we call it " -"\"waiting for manufacturer\"." +"Screenshot showing a sample selection of phone numbers to use for the " +"Placetels notify API" msgstr "" -#: ../system/objects.rst:181 +#: ../system/integrations/cti/provider-configurations/placetel.rst:66 msgid "" -"As state type we choose \"pending reminder\". This indicates that the ticket " -"is still open and we can set a reminder. This reminder can be useful if our " -"manufacturer sometimes isn't responding or we want to remind him to give us " -"an answer." +"This menu point also provides a API request log from Placetel view. Just " +"open \"Recent responses of your API endpoint\" to learn more." msgstr "" -#: ../system/objects.rst:186 +#: ../system/integrations/cti/provider-configurations/placetel.rst:69 msgid "" -"We choose \"no\" for \"ignore escalation\" because we want to escalate the " -"tickets even if we are waiting on the manufacturer's feedback." +"If you want to see Zammad's perspective, use the \"Recent Logs\" part from " +"within the Placetel integration page." msgstr "" -#: ../system/objects.rst:189 -#, fuzzy -msgid "The **result** in the creation dialog will look like this:" -msgstr "Final sonuçları aşağıdaki gibi görünecek:" +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "Screenshot showing sample log entries for Placetels API calls to Zammad" +msgstr "" -#: ../system/objects.rst:0 -msgid "Screenshot showing ticket state creation dialog with example" +#: ../system/integrations/cti/provider-configurations/placetel.rst:77 +msgid "Step 4 (optional): Further configurations for Placetel" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/placetel.rst:76 +msgid "" +"If needed, you can now configure Zammad's Placetel integration in more " +"detail. You can learn more about your options here: :ref:`Placetel " +"integration settings `." +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:2 +msgid "Setup Sipgate connection for Zammad" msgstr "" -#: ../system/objects.rst:197 ../system/objects.rst:199 -#, fuzzy -msgid "Ticket Priority" -msgstr "Bilet > Öncelik > Ad" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "" +"Sipgate has no english web interface which is why this documentation page is " +"mixing up languages badly." +msgstr "" -#: ../system/objects.rst:199 ../system/objects.rst:201 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"If the pre-configured priorities aren't enough for you or you want to change " -"them, you can do so by clicking on the cogwheel icon in the priority row in " -"the ticket tab:" +"Please also note that the availability of API addons highly depends on your " +"package trier. Usage of sipgate.io packages *is not free*, please check " +"their `pricing page `_ before!" msgstr "" -#: ../system/objects.rst:None -msgid "Screenshot showing highlighted ticket priority attribute" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:35 +msgid "Step 1: Book sipgate.io package" msgstr "" -#: ../system/objects.rst:224 ../system/objects.rst:226 -msgid "Handling of priorities" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:13 +msgid "Skip to step 2 if you already have the package booked!" msgstr "" -#: ../system/objects.rst:208 ../system/objects.rst:210 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:15 msgid "" -"In the priority configuration screen, you can add new priorities, disable " -"priorities or change priorities." +"Login to an administrative Sipgate account and navigate to " +"``Accountverwaltung``. You'll see several different options depending on " +"your booked packages. Select ``Verträge & Produkte`` to continue." msgstr "" -#: ../system/objects.rst:0 -msgid "Screenshot showing table of default ticket priorities" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:19 +msgid "" +"Scroll down to the section ``Zusätzliche Produkte buchen`` and look for " +"``sipgate.io`` - select this product by using the ``Produkte anzeigen``-" +"Button." msgstr "" -#: ../system/objects.rst:216 ../system/objects.rst:218 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:23 msgid "" -"To add a new priority, click on the \"New Priority\" button in the top right " -"corner. To change an existing priority, simply click on the affected " -"priority. This opens an edit dialog." +"On the next page select either one of the ``sipgate.io`` packages or ``Push-" +"API Package Free``. Follow the dialogue by booking the addon. You'll be " +"returned to your contract overview and now should see the selected addon in " +"your list." msgstr "" -#: ../system/objects.rst:220 ../system/objects.rst:222 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:30 msgid "" -"You can also clone a priority or set them to \"Default for new tickets\" by " -"clicking on the ⁝ action button and select the desired function." +"The availability for ``sipgate.io`` packages and their levels highly depends " +"on the overall account type and product you've booked with Sipgate." msgstr "" -#: ../system/objects.rst:223 ../system/objects.rst:225 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"*Default for new tickets* means that this priority is used for every newly " -"created ticket." +"Screencast showing the process on how to book the required sipgate.io addon" msgstr "" -#: ../system/objects.rst:246 ../system/objects.rst:248 -msgid "Priorities in detail" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:52 +msgid "Step 2: Configure webhook for Zammad" msgstr "" -#: ../system/objects.rst:227 ../system/objects.rst:229 -msgid "Below you can find a description for each field and option." +#: ../system/integrations/cti/provider-configurations/sipgate.rst:38 +msgid "" +"Within your ``Accountverwaltung`` navicate to your product ``sipgate.io``. " +"In the newly opened tab, switch from \"Clients\" to \"Webhooks\" and paste " +"the endpoint URLs from your Zammad instance like so:" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:42 +msgid "Inbound endpoint to \"Incoming\"" +msgstr "" + +#: ../system/integrations/cti/provider-configurations/sipgate.rst:43 +msgid "Outbound endpoint to \"Outgoing\"" msgstr "" -#: ../system/objects.rst:230 ../system/objects.rst:232 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:47 msgid "" -"This is the name of the priority and what you and your agents are seeing " -"when choosing a priority somewhere (e.g. in tickets, trigger configuration)." +"Ensure to select at least one call group or phoneline within \"Sources\". " +"Other wise Sipgate will not indicate any incoming or outgoing calls to " +"Zammad." msgstr "" -#: ../system/objects.rst:240 ../system/objects.rst:242 -msgid "Highlight color" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "" +"Screencast showing how to add Zammad's endpoint URLs to sipgate.ios webhook " +"configuration" msgstr "" -#: ../system/objects.rst:235 ../system/objects.rst:237 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:55 msgid "" -"Switch between *Low priority* (light blue), *High priority* (red) and - " -"(default). This affects the displayed color for ticket titles in overviews." +"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " +"the Webhooks → URLs section of Sipgate you can select which *sources* " +"Sipgate should notify Zammad about in- and outgoing calls." msgstr "" -#: ../system/objects.rst:239 ../system/objects.rst:241 -msgid "The color options are currently limited to the mentioned options." +#: ../system/integrations/cti/provider-configurations/sipgate.rst:59 +msgid "" +"Use either specific phone lines or use the option \"Use for all phonelines " +"and groups\" to notify Zammad about all existing lines of your Sipgate " +"account." msgstr "" -#: ../system/objects.rst:243 ../system/objects.rst:245 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"You can create a note for the priority to inform other admins about the " -"priority. This has no effect on tickets." +"Screenshot showing a sample selection of phone numbers to use for the " +"Sipgates webhooks API" msgstr "" -#: ../system/objects.rst:247 ../system/objects.rst:249 -#, fuzzy -msgid "Set the priority to *active* or *inactive*." -msgstr "aktifse veya değilse" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:68 +msgid "This section also allows you to enable a Debug log." +msgstr "" -#: ../system/objects/external-data-source-example.rst:2 -msgid "External Data Source" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "Screenshot showing an enabled Debug log option" msgstr "" -#: ../system/objects/external-data-source-example.rst:4 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:73 msgid "" -"We assume you already had a look on :doc:`types` where you can find a " -"description of the individual fields." +"After enabling you can use the Debug log section to see all sent webhook " +"calls to Zammad. You'll also can see the response." msgstr "" -#: ../system/objects/external-data-source-example.rst:7 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"To reproduce this example, choose a category you want to add a custom field, " -"click on *New Attribute* and select *External data source field* under " -"*Format*." +"Screenshot showing sample log entries for Sipgates webhook calls to Zammad" msgstr "" -#: ../system/objects/external-data-source-example.rst:11 -msgid "" -"Our example story is to fetch data from an external product database. We " -"want to add our products to the tickets so that the products can be searched " -"and chosen from a list and also create a link to the product website." +#: ../system/integrations/cti/provider-configurations/sipgate.rst:81 +msgid "Step 4 (optional): Further configurations for Sipgate" msgstr "" -#: ../system/objects/external-data-source-example.rst:16 -#, fuzzy -msgid "Base configuration" -msgstr "Yapılandırma" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:80 +msgid "" +"If needed, you can now configure Zammad's Sipgate integration in more " +"detail. You can learn more about your options here: :ref:`Sipgate " +"integration settings `." +msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Initial steps to configure external data source object type" +#: ../system/integrations/cti/sipgate.rst:2 +msgid "Sipgate (sipgate.io)" msgstr "" -#: ../system/objects/external-data-source-example.rst:23 -#: ../system/variables.rst:85 +#: ../system/integrations/cti/sipgate.rst:16 #, fuzzy -msgid "**Example:**" -msgstr "Örnek" +msgid "You need an administrative Sipgate account for your organization." +msgstr "🔑 **Organizasyonunuz için bir yönetici hesabı kullanın.**" -#: ../system/objects/external-data-source-example.rst:25 -msgid "Name: *product*" +#: ../system/integrations/cti/sipgate.rst:17 +msgid "" +"Zammad requires a ``sipgate.io`` addon from the feature store (please note " +"that API calls are not free with Sipgate. Rates may apply and differ from " +"account to account)." msgstr "" -#: ../system/objects/external-data-source-example.rst:26 -msgid "Display: *Product*" +#: ../system/integrations/cti/sipgate.rst:21 +msgid "Sipgate must be able to reach your Zammad instance." msgstr "" -#: ../system/objects/external-data-source-example.rst:29 -#, fuzzy -msgid "External data source configuration" -msgstr "Makale > Görünürlük" +#: ../system/integrations/cti/sipgate.rst:25 +msgid ":doc:`provider-configurations/sipgate`" +msgstr "" -#: ../system/objects/external-data-source-example.rst:31 +#: ../system/integrations/cti/sipgate.rst:24 msgid "" -"First, enter the search URL making sure it contains ``#{search.term}`` as a " -"parameter:" +"Learn how to configure Sipgate to enable Zammad and Sipgate to communicate " +"with each other." msgstr "" -#: ../system/objects/external-data-source-example.rst:34 -msgid "**Example:** ``https://dummyjson.com/products/search?q=#{search.term}``" +#: ../system/integrations/cti/sipgate.rst:33 +msgid "" +"Below endpoint settings affect the :doc:`sipgate.io configuration `." msgstr "" -#: ../system/objects/external-data-source-example.rst:36 -msgid "" -"After that, head down to the preview section and enter a search input for " -"the external data source." +#: ../system/integrations/cti/sipgate.rst:37 +msgid "This endpoint is required for incoming call hooks." msgstr "" -#: ../system/objects/external-data-source-example.rst:39 +#: ../system/integrations/cti/sipgate.rst:40 #, fuzzy -msgid "**Example:** ``mac``" -msgstr "Örnek" +msgid "This endpoint is required for outgoing call hooks." +msgstr "Giden e-posta için kullanılan görünen ad." -#: ../system/objects/external-data-source-example.rst:41 -msgid "Then you can find a preview of the response data below:" +#: ../system/integrations/cti/sipgate.rst:0 +msgid "Screenshot showing sample user mappings in between Sipgate and Zammad" msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of JSON response based on search term" +#: ../system/integrations/cti/sipgate.rst:69 +msgid "" +"You can find your agent's Sipgate username within ``Accountverwaltung → " +"Benutzer``. You're looking for the SIP-ID." msgstr "" -#: ../system/objects/external-data-source-example.rst:48 -msgid "" -"We recommend using the preview to have a look on the structure. There is a " -"top-level element called ``products``. One level below, you can find the " -"attributes ``id`` and ``title``." +#: ../system/integrations/cti/sipgate.rst:0 +msgid "Sample VoIP credentials for a Sipgate user" msgstr "" -#: ../system/objects/external-data-source-example.rst:52 -msgid "**Search result response based on search from example:**" +#: ../system/integrations/cti/sipgate.rst:77 +msgid "Users with several devices also have several SIP-IDs." msgstr "" -#: ../system/objects/external-data-source-example.rst:119 +#: ../system/integrations/elasticsearch.rst:2 +msgid "Elasticsearch (SaaS)" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:4 msgid "" -"To tell the remote system that the desired data is located below the " -"``products`` level, you have to put it in the field *Search result list key*." +"The Elasticsearch integration allows you to create a read-only user to use " +"with your favorite reporting tool (e.g. like Grafana)." msgstr "" -#: ../system/objects/external-data-source-example.rst:122 +#: ../system/integrations/elasticsearch.rst:7 msgid "" -"After inserting ``products`` in the mentioned field, you get an extended " -"preview. You can find an additional box *Search result list* with a JSON " -"structure. This is the same response as before but stripped from the upper " -"``products`` element by the external data source." +"If you want to take full advantage of the Zammad reporting, have a look at " +"our :docs:`Grafana ` " +"setup page as well." msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of JSON response search result list" +#: ../system/integrations/elasticsearch.rst:11 ../system/subscription.rst:7 +msgid "**🚧 Hosted environment specific 🚧**" msgstr "" -#: ../system/objects/external-data-source-example.rst:132 +#: ../system/integrations/elasticsearch.rst:13 msgid "" -"Now you need to provide the keys for the search result values and labels. As " -"already mentioned, we are looking for the ``id`` and the ``title`` of our " -"products. If you haven't already, it is now a good time to look at the " -"preview of the *Search result list*." +"This integration is only available for Hosted setups. In order to use " +"Elasticsearch you'll need the **Plus** subscription." msgstr "" -#: ../system/objects/external-data-source-example.rst:197 +#: ../system/integrations/elasticsearch.rst:16 msgid "" -"After locating our two keys, we insert them in *search result value key* " -"(``id``) and in *Search result label key* (``title``)." +"Self hosted users have all the control over their self hosted Elasticsearch " +"instances." msgstr "" -#: ../system/objects/external-data-source-example.rst:200 +#: ../system/integrations/elasticsearch.rst:None +msgid "Elasticsearch integration page on SaaS environments" +msgstr "" + +#: ../system/integrations/elasticsearch.rst:27 msgid "" -"Basically, we configured the external data source already and we can see a " -"table in the preview section:" +"Please note the following limitations of Elasticsearch access on hosted " +"environments:" msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of product table based on search term" +#: ../system/integrations/elasticsearch.rst:30 +msgid "access to the Elasticsearch index is read-only access" msgstr "" -#: ../system/objects/external-data-source-example.rst:208 -msgid "" -"According to our example story, now just the *Link template* is missing." +#: ../system/integrations/elasticsearch.rst:31 +msgid "currently you're limited to user only" msgstr "" -#: ../system/objects/external-data-source-example.rst:210 +#: ../system/integrations/elasticsearch.rst:32 msgid "" -"Please note that this is an optional feature. If you don't want to use such " -"links, of course you don't have to configure it." +"Reporting tools that require to write into the indexes (like Kibana) are not " +"supported" msgstr "" -#: ../system/objects/external-data-source-example.rst:213 -msgid "" -"We can add now an address where additional product information can be found." +#: ../system/integrations/elasticsearch.rst:34 +msgid "IP access restriction is currently not yet supported" msgstr "" -#: ../system/objects/external-data-source-example.rst:215 -msgid "Example: ``https://your_domain.com/q=#{ticket.product}``" +#: ../system/integrations/elasticsearch.rst:37 +msgid "Activating Elasticsearch Access" msgstr "" -#: ../system/objects/external-data-source-example.rst:217 -msgid "In the example, the parameter means:" +#: ../system/integrations/elasticsearch.rst:39 +msgid "" +"By default external access to your Elasticsearch index is not active. You " +"can enable the integration at any time if needed." msgstr "" -#: ../system/objects/external-data-source-example.rst:219 -msgid "``#{}``: \"Frame\" for the insertion of information" +#: ../system/integrations/elasticsearch.rst:42 +msgid "" +"Please ensure to note down the password provided - you won't have access to " +"it afterwards." msgstr "" -#: ../system/objects/external-data-source-example.rst:220 -msgid "``ticket``: object level, where you create your custom object" +#: ../system/integrations/elasticsearch.rst:None +msgid "Screencast showing activation of Elasticsearch integration" msgstr "" -#: ../system/objects/external-data-source-example.rst:221 -msgid "``product``: name of the (custom) object" +#: ../system/integrations/elasticsearch.rst:51 +msgid "Connection Settings" msgstr "" -#: ../system/objects/external-data-source-example.rst:223 +#: ../system/integrations/elasticsearch.rst:53 msgid "" -"After configuring your *Link template*, there will be another column in the " -"preview. Hovering on the icons in the *Link* column will show you where it " -"forwards you." +"This section holds the most important general information for accessing your " +"Elasticsearch indexes - such as:" msgstr "" -#: ../system/objects/external-data-source-example.rst:232 -msgid "" -"In our example, one of the links looks like: https://your_domain.com/q=6, " -"where the 6 is the product id." +#: ../system/integrations/elasticsearch.rst:57 +msgid "A unique subdomain that does not tell your real instance URL." msgstr "" -#: ../system/objects/external-data-source-example.rst:235 -msgid "You can find more information regarding the URL in :doc:`types`." +#: ../system/integrations/elasticsearch.rst:61 +msgid "Software" msgstr "" -#: ../system/objects/includes/adding-values-hint.include.rst:3 +#: ../system/integrations/elasticsearch.rst:60 msgid "" -"Adding values can be tricky for first timers, don't forget to press \"➕ " -"Add\" after typing your values. Otherwise you may loose a value." +"The major version of the search index being used. This is required by some " +"Reporting tools like Grafana." msgstr "" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:1 -#: ../system/objects/includes/reposition-values.include.rst:1 -msgid "**↕️ This field type allows the positioning of its values ↔️**" +#: ../system/integrations/elasticsearch.rst:64 +msgid "Authentication" msgstr "" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:3 -msgid "" -"In order to re-arrange the field values, first edit the field. Then you can " -"use ☰ to drag the values in question to the correct position. If you want to " -"change the layer depth, double click on ☰. With it you can cycle through the " -"available layers." +#: ../system/integrations/elasticsearch.rst:64 +msgid "The authentication type being supported. ``Basic Authentication``" msgstr "" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:8 -msgid "When you're ready, submit your changes to save the object attribute." +#: ../system/integrations/elasticsearch.rst:67 +msgid "Available Indexes" msgstr "" -#: :0 ../system/objects/types.rst:0 +#: ../system/integrations/elasticsearch.rst:69 msgid "" -"Screencast showing how to re-position values on tree select like\n" -"fields" +"Within this section we're displaying the -in our opinion- most important " +"indexes for a Zammad instance." msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:3 +#: ../system/integrations/elasticsearch.rst:72 msgid "" -"In order to re-arrange the field values, edit the field and scroll below the " -"values. Make sure to tick the option \"Use custom option sort\"." +"If you require all indexes or our listing is not good enough for you, point " +"your browser to the URL we're providing and append ``/_aliases?" +"pretty=true``. The result should look like this: ``https://.zammad.com/" +"_aliases?pretty=true``." msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:8 +#: ../system/integrations/elasticsearch.rst:77 msgid "" -"If you do not tick this field, all manual positioning you did above will be " -"lost upon saving! ☠️" +"Your browser will automatically ask for your credentials - you'll then see " +"something like this:" msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:11 -msgid "" -"Now use ☰ to drag the values in question to the correct position. When " -"you're ready, submit your changes to save the object attribute." +#: ../system/integrations/elasticsearch.rst:125 +msgid "Credentials" msgstr "" -#: :0 ../system/objects/types.rst:0 -msgid "Screencast showing how to re-position values" +#: ../system/integrations/elasticsearch.rst:127 +msgid "" +"Within this section Zammad displays your available users. The password is " +"provided once (upon activation) and cannot be retrieved after that." msgstr "" -#: ../system/objects/includes/url-template-hint.include.rst:3 +#: ../system/integrations/elasticsearch.rst:131 msgid "" -"This field allows using :ref:`URL fields (Link Templates) `." +"If you need to change or reset your Elasticsearch user password, use the " +"\"Reset password\" button in the credentials table. Doing so creates a brand " +"new password for the account in question. This change is immediate, keep in " +"mind that this may affect third party tools connected to your instance." msgstr "" -#: ../system/objects/permissions.rst:2 -#, fuzzy -msgid "Attribute Permissions" -msgstr "Bilet Nitelikleri" +#: ../system/integrations/exchange.rst:2 +msgid "Exchange" +msgstr "Exchange" -#: ../system/objects/permissions.rst:7 +#: ../system/integrations/exchange.rst:4 msgid "" -"In the object attributes configuration you can define if a field is shown " -"and if the input in the field is mandatory, separated by different screens " -"and for different :doc:`roles/permissions `." +"With Zammad's Exchange integration, you can easily use existing address " +"books without having to update more than one source." msgstr "" -#: ../system/objects/permissions.rst:17 -#, fuzzy -msgid "Screenshot shows object attribute permission table" +#: ../system/integrations/exchange.rst:7 +msgid "" +"However, you should refrain from syncing all addresses, as the results may " +"not be what you expect (Exchange collects huge amounts of addresses). A " +"central address book of your company to sync makes more sense, as you can " +"ensure that Zammad gets only the data you need and want. Apart from this, it " +"is even not possible to sync the Global Address List (GAL) of your Exchange " +"system with Zammad." msgstr "" -"Yönetici panelinin Makrolar sayfasında makro oluşturabilir veya " -"düzenleyebilirsiniz:" -#: ../system/objects/permissions.rst:17 +#: ../system/integrations/exchange.rst:16 msgid "" -"Some of the possible permissions and screen options for a user object " -"attribute." +"**Exchange and LDAP:** The exchange sync can be overruled by Zammad's LDAP " +"integration. If you have the same users in both sources, the LDAP version " +"will always be Zammad's pick." msgstr "" -#: ../system/objects/permissions.rst:19 +#: ../system/integrations/exchange.rst:19 msgid "" -"Based on the object context (ticket, agent, organization, user), the " -"selectable roles (to be precise: the required permissions) and screens " -"differ. Be aware that these settings aren't affecting data creation via " -"other channels than the UI." +"**One way sync:** the Exchange sync is one way. Exchange => Zammad. Changes " +"to your users inside of Zammad might be overwritten by the Exchange sync." msgstr "" -#: ../system/objects/permissions.rst:24 +#: ../system/integrations/exchange.rst:24 msgid "" -"If you want to have further customization possibilities, you should have a " -"look at the :doc:`core workflows `." +"To configure Exchange integration, simply go to the System > Integrations > " +"Exchange in the admin panel. Press \"change\" and follow the wizard for " +"adding the needed Exchange information to Zammad. On the last two steps " +"Zammad will ask you for the address book(s) and your desired attribute " +"mapping. By default, Zammad only maps email address, first- and lastname. " +"Technically, you can map any Exchange object to a Zammad user object (this " +"also works for custom objects!)." msgstr "" -#: ../system/objects/permissions.rst:28 -#, fuzzy -msgid "Screens" -msgstr "İmzalar" - -#: ../system/objects/permissions.rst:30 +#: ../system/integrations/exchange.rst:35 msgid "" -"In the table below you can find an overview about the different permissions " -"and the available screens Zammad distinguishes between." +"If the SSL verification fails while connecting to Exchange, Zammad will ask " +"you to turn it off temporarily." msgstr "" -#: ../system/objects/permissions.rst:37 -#, fuzzy -msgid "Screen" -msgstr "İmzalar" - -#: ../system/objects/permissions.rst:38 -#, fuzzy -msgid "Available for" -msgstr "değişken" - -#: ../system/objects/permissions.rst:40 -msgid "create" +#: ../system/integrations/exchange.rst:38 +msgid "" +"Please be aware that **turning off SSL verification is a security risk**. It " +"should only be used temporarily or for testing purposes. If turned off, " +"there is no verification of the certificate, which means that every " +"presented certificate will be accepted." msgstr "" -#: ../system/objects/permissions.rst:41 ../system/objects/permissions.rst:52 -#: ../system/objects/permissions.rst:59 ../system/objects/permissions.rst:73 -#, fuzzy -msgid "admin.user" -msgstr "``admin.user``" - -#: ../system/objects/permissions.rst:42 ../system/objects/permissions.rst:53 -#: ../system/objects/permissions.rst:60 -#, fuzzy -msgid "admin.organization" -msgstr "``admin.organization``" - -#: ../system/objects/permissions.rst:43 ../system/objects/permissions.rst:54 -#: ../system/objects/permissions.rst:61 -#, fuzzy -msgid "admin.group" -msgstr "``admin.group``" +#: ../system/integrations/exchange.rst:43 +msgid "" +"After pressing Continue, Zammad will check if the configuration is okay. You " +"can then enable Exchange and start your first sync. The sync will then run " +"hourly - if you need to change mappings or the address book(s), you can " +"change the configuration at any time." +msgstr "" -#: ../system/objects/permissions.rst:44 -msgid "Creation dialog for not yet existing data" +#: ../system/integrations/exchange.rst:50 +msgid "" +"After the sync has finished, you can find the new Exchange contacts under " +"\"Users\". Zammad integrates them just as normal users." msgstr "" -#: ../system/objects/permissions.rst:45 -#, fuzzy -msgid "create_middle" -msgstr "Oluşturulma" +#: ../system/integrations/exchange.rst:55 +msgid "" +"In some cases you might see unique IDs as \"Login\" instead of the email " +"address. This is normal and doesn't affect the login or email mapping for " +"that entry." +msgstr "" -#: ../system/objects/permissions.rst:46 ../system/objects/permissions.rst:50 -#: ../system/objects/permissions.rst:57 ../system/objects/permissions.rst:66 -#: ../system/objects/permissions.rst:70 -#, fuzzy -msgid "ticket.customer" -msgstr "``#{ticket.customer.web}``" +#: ../system/integrations/github.rst:4 +msgid "" +"Use GitHub integration to track GitHub issues directly within Zammad " +"tickets. Add issue hyperlinks and get a live summary of metadata like status " +"(open/closed), assignee, labels, and more." +msgstr "" -#: ../system/objects/permissions.rst:47 ../system/objects/permissions.rst:51 -#: ../system/objects/permissions.rst:58 ../system/objects/permissions.rst:69 -#, fuzzy -msgid "ticket.agent" -msgstr "``ticket.agent``" +#: ../system/integrations/github.rst:8 +msgid "Please note that our GitHub integration does not support pull requests." +msgstr "" -#: ../system/objects/permissions.rst:48 -msgid "Ticket create dialog (middle section)" +#: ../system/integrations/github.rst:None +msgid "Integration page for GitHub" msgstr "" -#: ../system/objects/permissions.rst:49 -msgid "edit" +#: ../system/integrations/github.rst:18 +msgid "" +"In your GitHub settings, create a new API token under **Developer settings > " +"Personal access tokens > Generate new token**. Leave the **Scopes** section " +"empty." msgstr "" -#: ../system/objects/permissions.rst:55 -msgid "Editing dialog for already existing data" +#: ../system/integrations/github.rst:0 ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to create a new API token" msgstr "" -#: ../system/objects/permissions.rst:56 -msgid "view" +#: ../system/integrations/github.rst:27 +msgid "Create a new API key with no scopes/privileges." msgstr "" -#: ../system/objects/permissions.rst:62 -msgid "View-only dialog for already existing data" +#: ../system/integrations/github.rst:29 +msgid "🔒 **Will this work for private repos?**" msgstr "" -#: ../system/objects/permissions.rst:64 -msgid "(e.g. user or organization from search)" +#: ../system/integrations/github.rst:31 +msgid "" +"No. To link private repo issues, **use the** ``repo`` **scope instead**. " +"Bear in mind that the resulting token will have `lots of permissions that it " +"doesn't actually need `_, which presents a security risk if your token ever falls into " +"the wrong hands." msgstr "" -#: ../system/objects/permissions.rst:65 -msgid "signup" +#: ../system/integrations/github.rst:37 +msgid "" +"Unfortunately, because of how GitHub's OAuth token scopes are set up, this " +"is the only way to link issues on private repos." msgstr "" -#: ../system/objects/permissions.rst:67 -msgid "Sign-up screen for new customers" +#: ../system/integrations/github.rst:40 +msgid "Enter your new API token in Zammad and enable GitHub integration." msgstr "" -#: ../system/objects/permissions.rst:68 -#, fuzzy -msgid "invite_customer" -msgstr "müşteri" +#: ../system/integrations/github.rst:0 +msgid "Screencast showing how to configure Zammad's GitHub integration" +msgstr "" -#: ../system/objects/permissions.rst:71 +#: ../system/integrations/github.rst:47 msgid "" -"Customer invitation screen (from :doc:`First Steps ` area)" +"Use the default API endpoint (``https://api.github.com/graphql``) unless " +"you're using GitHub Enterprise Server." msgstr "" -#: ../system/objects/permissions.rst:72 -msgid "invite_agent" +#: ../system/integrations/github.rst:50 +msgid "" +"Once completed, a new GitHub issues tab will appear in the ticket pane. 🎉" msgstr "" -#: ../system/objects/permissions.rst:74 -msgid "" -"Agent invitation screen (from :doc:`First Steps ` area)" +#: ../system/integrations/github.rst:59 ../system/integrations/gitlab.rst:52 +msgid "Token verification is taking a long time" msgstr "" -#: ../system/objects/permissions.rst:78 -#, fuzzy -msgid "Screen Options" -msgstr "Seçenek" +#: ../system/integrations/github.rst:56 ../system/integrations/gitlab.rst:49 +msgid "" +"Slight delays are normal (<2 min.), especially for systems under heavy load." +msgstr "" -#: ../system/objects/permissions.rst:80 +#: ../system/integrations/github.rst:58 msgid "" -"For the different screens you can select \"show\" and \"required\" options." +"Self-hosted administrators, please check your network settings to ensure " +"that your Zammad server can reach ``api.github.com``." msgstr "" -#: ../system/objects/permissions.rst:82 -msgid "**shown:** Show (check) or hide (uncheck) a field." +#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 +msgid "I reloaded the page and now the API token is gone" msgstr "" -#: ../system/objects/permissions.rst:83 +#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 msgid "" -"**required:** Set a field to mandatory (check). Forces users (via UI and " -"API) to populate the field." +"This may indicate that Zammad is still verifying your API token. Try " +"reloading the page again in a couple minutes." msgstr "" -#: ../system/objects/types.rst:7 -#, fuzzy -msgid "Example external data source" -msgstr "Makale > Görünürlük" - -#: ../system/objects/types.rst:2 -#, fuzzy -msgid "Attribute types" -msgstr "Bilet Nitelikleri" +#: ../system/integrations/gitlab.rst:2 +msgid "GitLab" +msgstr "GitLab" -#: ../system/objects/types.rst:4 +#: ../system/integrations/gitlab.rst:4 msgid "" -"When adding a new object attribute, you can choose between the following " -"attribute types." +"Use GitLab integration to track GitLab issues directly within Zammad " +"tickets. Add issue hyperlinks and get a live summary of metadata like status " +"(open/closed), assignee, labels, and more." msgstr "" -#: ../system/objects/types.rst:14 +#: ../system/integrations/gitlab.rst:8 msgid "" -"You cannot change the attribute format / type as soon as it is applied. If " -"you no longer need an object attribute, consider disabling it instead of " -"removing." +"Please note that our GitLab integration does not support merge requests." msgstr "" -#: ../system/objects/types.rst:18 -#, fuzzy -msgid "**What about the translation of my attributes?**" -msgstr "Bekle, peki ya özelleştirilmiş nesneler?" +#: ../system/integrations/gitlab.rst:None +msgid "Integration page for GitLab" +msgstr "" -#: ../system/objects/types.rst:20 +#: ../system/integrations/gitlab.rst:18 msgid "" -"For some attribute types you can decide if they should be translatable or " -"not. To be precise, it works only for the selectable fields because the " -"possible choices are known and limited. For the following attribute types, " -"you can set the translatable flag:" +"In your GitLab preferences, create a new API token under **Access Tokens**." msgstr "" -#: ../system/objects/types.rst:25 -#, fuzzy -msgid "*Boolean field*" -msgstr "Mantıksal" +#: ../system/integrations/gitlab.rst:20 +msgid "Under **Select scopes**, choose ``read_api`` only." +msgstr "" -#: ../system/objects/types.rst:26 -#, fuzzy -msgid "*Single selection field*" -msgstr "Posta Sunucusu Ayarları" +#: ../system/integrations/gitlab.rst:27 +msgid "🔒 **If you wish to link issues on any private repos...**" +msgstr "" -#: ../system/objects/types.rst:27 -#, fuzzy -msgid "*Multiple selection field*" -msgstr "Posta Sunucusu Ayarları" +#: ../system/integrations/gitlab.rst:29 +msgid "Your API token must belong to an account with access to those repos." +msgstr "" -#: ../system/objects/types.rst:28 -#, fuzzy -msgid "*Single tree selection field*" -msgstr "Posta Sunucusu Ayarları" +#: ../system/integrations/gitlab.rst:31 +msgid "Enter your new API token in Zammad and enable GitLab integration." +msgstr "" -#: ../system/objects/types.rst:29 -#, fuzzy -msgid "*Multiple tree selection field*" -msgstr "Posta Sunucusu Ayarları" +#: ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to configure Zammad's GitLab integration" +msgstr "" -#: ../system/objects/types.rst:31 +#: ../system/integrations/gitlab.rst:40 msgid "" -"For these types, you can find an additional field *Translate field contents*:" +"Use the default API endpoint (``https://gitlab.com/api/graphql``) unless " +"you're a self-hosted GitLab user." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Screenshot showing translatable attribute types" +#: ../system/integrations/gitlab.rst:43 +msgid "" +"Once completed, a new GitLab issues tab will appear in the ticket pane. 🎉" msgstr "" -#: ../system/objects/types.rst:38 -msgid "Screenshot with example of translatable attribute type" +#: ../system/integrations/gitlab.rst:51 +msgid "" +"Self-hosted administrators, please check your network settings to ensure " +"that your Zammad server can reach ``gitlab.com``." msgstr "" -#: ../system/objects/types.rst:45 -#, fuzzy -msgid "Boolean field" -msgstr "Mantıksal" +#: ../system/integrations/i-doit.rst:2 +msgid "i-doit" +msgstr "i-doit" -#: ../system/objects/types.rst:41 +#: ../system/integrations/i-doit.rst:4 msgid "" -"Provides a drop-down field with display values for ``true`` and ``false``. " -"Setting a default is mandatory." +"`i-doit `_ is an open-source **configuration " +"management database** - in other words, a tool for keeping tabs on every " +"single piece of your physical and digital infrastructure, from network " +"equipment to virtual machines on down to the faceplates on your rack shelves " +"and more." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Boolean fields" +#: ../system/integrations/i-doit.rst:10 +msgid "" +"What's that got to do with Zammad? Well, if you used tickets to track issues " +"with all that hardware, you might start wishing there was a way they could " +"talk to each other." msgstr "" -#: ../system/objects/types.rst:55 -msgid "Date field" +#: ../system/integrations/i-doit.rst:14 +msgid "Zammad gives you two:" msgstr "" -#: ../system/objects/types.rst:48 -msgid "Provides a date picker field and does not allow default values." +#: ../system/integrations/i-doit.rst:17 +msgid "1. Add i-doit Links to Zammad Tickets" msgstr "" -#: ../system/objects/types.rst:52 -msgid "Default time diff (hours)" +#: ../system/integrations/i-doit.rst:20 ../system/integrations/i-doit.rst:80 +msgid "What Users See" msgstr "" -#: ../system/objects/types.rst:51 +#: ../system/integrations/i-doit.rst:26 +msgid "i-doit integration in Zammad's ticket pane" +msgstr "" + +#: ../system/integrations/i-doit.rst:26 msgid "" -"This setting helps the user by highlighting the day from now plus the " -"provided value. It *does not* pre-fill the field." +"The i-doit integration will appear under a new 🖨 tab in the ticket pane." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Date fields" +#: ../system/integrations/i-doit.rst:28 +msgid "" +"i-doit integration puts a new tab in Zammad's ticket pane where you can add " +"links to existing i-doit devices for easy reference. (See our :user-docs:" +"`user documentation ` to learn " +"how it works in practice)." msgstr "" -#: ../system/objects/types.rst:73 -msgid "Date & time field" +#: ../system/integrations/i-doit.rst:36 ../system/integrations/i-doit.rst:93 +#, fuzzy +msgid "How to Set it Up" +msgstr "Nasıl etiketlenir" + +#: ../system/integrations/i-doit.rst:38 +msgid "" +"It requires i-doit's `API Add-on `_. Make sure to have it properly set up. Use the following setting:" msgstr "" -#: ../system/objects/types.rst:58 -msgid "Provides a date and time picker – does not allow default values" +#: ../system/integrations/i-doit.rst:42 +msgid "Active: ``Yes``" msgstr "" -#: ../system/objects/types.rst:62 -msgid "Allow future" +#: ../system/integrations/i-doit.rst:43 +msgid "Enforce authentication by username and password: ``No``" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Forbid dates and times in the future." +#: ../system/integrations/i-doit.rst:45 +msgid "" +"To set it up, enable the integration in the Zammad admin panel under " +"**System > Integrations > i-doit**:" msgstr "" -#: ../system/objects/types.rst:66 -msgid "Allow past" +#: ../system/integrations/i-doit.rst:None +msgid "i-doit settings within the integration pages" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Forbid dates and times in the past." +#: ../system/integrations/i-doit.rst:53 +msgid "The root URL of your i-doit installation." msgstr "" -#: ../system/objects/types.rst:70 -msgid "Default time diff (minutes)" +#: ../system/integrations/i-doit.rst:62 +msgid "API token" msgstr "" -#: ../system/objects/types.rst:69 +#: ../system/integrations/i-doit.rst:56 msgid "" -"This setting helps the user by highlighting the day from now plus the " -"provided value. It does not pre-fill the field." +"Found in the i-doit admin panel under **Interfaces / external data > JSON-" +"RPC API > Common Settings**." msgstr "" -#: ../system/objects/types.rst:0 -#, fuzzy -msgid "Available settings for Date & time fields" -msgstr "Posta Sunucusu Ayarları" - -#: ../system/objects/types.rst:86 -#, fuzzy -msgid "Integer field" -msgstr "Sayı" - -#: ../system/objects/types.rst:76 -msgid "" -"Provides an input field that allows integer usage only. You may define a " -"default value. You cannot enforce comma separation." +#: ../system/integrations/i-doit.rst:0 +msgid "i-doit administration interface with API configuration" msgstr "" -#: ../system/objects/types.rst:80 -msgid "Minimal" +#: ../system/integrations/i-doit.rst:67 +msgid "Client ID" msgstr "" -#: ../system/objects/types.rst:80 -msgid "The minimal value the field accepts." +#: ../system/integrations/i-doit.rst:65 +msgid "A unique name to identify Zammad within i-doit." msgstr "" -#: ../system/objects/types.rst:83 -msgid "Maximal" +#: ../system/integrations/i-doit.rst:67 +msgid "(Zammad does not require you to enter a value here, but i-doit might!)" msgstr "" -#: ../system/objects/types.rst:83 -msgid "The maximum value the field accepts." +#: ../system/integrations/i-doit.rst:70 +msgid "" +"Here you can decide if the certificate of your i-doit system has to be " +"verified or not. In case you are using custom certificates, please have a " +"look at :doc:`how to add them to Zammad `." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Integer fields" +#: ../system/integrations/i-doit.rst:77 +msgid "2. List / Create Zammad Tickets in i-doit" msgstr "" -#: ../system/objects/types.rst:99 -msgid "Multiple selection field" +#: ../system/integrations/i-doit.rst:None +msgid "Zammad integration in i-doit's device view" msgstr "" -#: ../system/objects/types.rst:89 +#: ../system/integrations/i-doit.rst:86 msgid "" -"Provides a selection field that allows the selection of one or more out of " -"several. This field does allow setting a default value." +"i-doit's ticket system integration gives you a way to see all the tickets " +"for a given device without ever leaving i-doit. (See our :user-docs:`user " +"documentation ` to learn how it " +"works in practice)." msgstr "" -#: ../system/objects/types.rst:0 -#, fuzzy -msgid "Available settings for Multiple selection fields" -msgstr "Posta Sunucusu Ayarları" +#: ../system/integrations/i-doit.rst:95 +msgid "" +"Enable this integration in the i-doit admin panel under **Interfaces / " +"external data > Trouble Ticket System (TTS) > Configuration**:" +msgstr "" -#: ../system/objects/types.rst:112 -msgid "Single selection field" +#: ../system/integrations/i-doit.rst:None +msgid "i-doit administration interface with TTS configuration" msgstr "" -#: ../system/objects/types.rst:102 -msgid "" -"Provides a drop-down field that allows selection of one value out of " -"several. This field does allow setting a default value." +#: ../system/integrations/i-doit.rst:104 +msgid "TTS-Type" msgstr "" -#: ../system/objects/types.rst:0 -#, fuzzy -msgid "Available settings for Single selection fields" -msgstr "Posta Sunucusu Ayarları" +#: ../system/integrations/i-doit.rst:104 +msgid "``Zammad``" +msgstr "``Zammad``" -#: ../system/objects/types.rst:142 -#, fuzzy -msgid "Textarea field" -msgstr "Metin" +#: ../system/integrations/i-doit.rst:115 +msgid "Username / Password" +msgstr "Kullanıcı adı / Parola" -#: ../system/objects/types.rst:115 +#: ../system/integrations/i-doit.rst:107 +msgid "Login credentials for a Zammad agent." +msgstr "" + +#: ../system/integrations/i-doit.rst:109 msgid "" -"Provides a text area input field (multiple lines) and thus allows e.g. new " -"lines. You can set a default field value." +"This agent must have **read permission** for all :doc:`groups ` that plan on using the i-doit integration." msgstr "" -#: ../system/objects/types.rst:120 +#: ../system/integrations/i-doit.rst:113 msgid "" -"Please note that this field *does not* support text formatting or HTML " -"content (rich text)." +"You may even wish to create a dedicated agent account just for this " +"integration (otherwise, if the agent ever changes her password, you will " +"have to remember to update it here)." msgstr "" -#: ../system/objects/types.rst:123 -msgid "**🥵 This field can consume a lot of visual space**" +#: ../system/integrations/i-doit.rst:117 +msgid "URL incl. protocol" msgstr "" -#: ../system/objects/types.rst:125 +#: ../system/integrations/i-doit.rst:118 +msgid "``https://your.zammad.domain``" +msgstr "``https://your.zammad.domain``" + +#: ../system/integrations/index.rst:2 +msgid "Integrations" +msgstr "Entegrasyonlar" + +#: ../system/integrations/index.rst:4 msgid "" -"Depending on where you use this field type, it may use a lot of visual space " -"if you provide a lot of text. This may be an issue to work with." +"Zammad offers numerous integrations that add rich features to your instance." msgstr "" +"Zammad, bulut sunucunuza zengin özellikler ekleyen çok sayıda entegrasyon " +"sunar." -#: ../system/objects/types.rst:130 +#: ../system/integrations/index.rst:6 +msgid "We're still working on this part of our documentation, stay tight!" +msgstr "Dokümanımızın bu kısmı üzerinde hala çalışıyoruz, sıkı durun!" + +#: ../system/integrations/index.rst:10 #, fuzzy -msgid "Default" -msgstr "Varsayılan değer" +msgid "Integrations for Phone Systems" +msgstr "Telefon sistemleri için entegrasyonlar" -#: ../system/objects/types.rst:129 +#: ../system/integrations/index.rst:14 msgid "" -"The here provided text will be shown within the text area field or new data " -"sets." +"Your VoIP provider or telephony system is not listed? Possibly your provider " +"supports Zammad by using the generic CTI - if you're unsure ask your " +"provider." msgstr "" -#: ../system/objects/types.rst:134 ../system/objects/types.rst:160 -msgid "Maxlength" +#: ../system/integrations/index.rst:18 +msgid "" +"Provider does not support Zammad? Consider creating a `feature request in " +"the Zammad Community `_." msgstr "" -#: ../system/objects/types.rst:0 ../system/objects/types.rst:160 +#: ../system/integrations/index.rst:31 #, fuzzy -msgid "You can pick the maximum length of the field." -msgstr "alanın maksimum uzunluğunu seçebilirsiniz." +msgid "Integrations for Authentication and Customers" +msgstr "Kimlik doğrulama ve müşteriler için entegrasyonlar" -#: ../system/objects/types.rst:0 -msgid "The default length of this object is ``500``." -msgstr "" +#: ../system/integrations/index.rst:44 +msgid "Integrations for Monitoring Systems" +msgstr "İzleme Sistemleri için Entegrasyonlar" -#: ../system/objects/types.rst:139 -msgid "Rows" -msgstr "" +#: ../system/integrations/index.rst:46 +msgid "This section currently misses the following integrations:" +msgstr "Bu bölümde şu anda aşağıdaki entegrasyonlar eksik:" -#: ../system/objects/types.rst:0 -msgid "" -"Change the number of rows to dislay so that you can use only the space you " -"really need." -msgstr "" +#: ../system/integrations/index.rst:48 +msgid "Icinga" +msgstr "Icinga" -#: ../system/objects/types.rst:0 -msgid "The default number of rows is ``4``." -msgstr "" +#: ../system/integrations/index.rst:49 +msgid "Monit" +msgstr "Monit" -#: ../system/objects/types.rst:0 -#, fuzzy -msgid "Available settings for Textarea fields" -msgstr "Posta Sunucusu Ayarları" +#: ../system/integrations/index.rst:50 +msgid "Nagios" +msgstr "Nagios" -#: ../system/objects/types.rst:165 -msgid "Text field" -msgstr "" +#: ../system/integrations/index.rst:60 +msgid "Integrations for Issue Trackers" +msgstr "Sorun Takipçileri için Entegrasyonlar" -#: ../system/objects/types.rst:145 -msgid "Provides a text field (one line) and allows choosing a default value." +#: ../system/integrations/index.rst:70 +msgid "Other Integrations" +msgstr "Diğer Entegrasyonlar" + +#: ../system/integrations/index.rst:72 +msgid "" +"This section will hold any other integration that can't be grouped up (yet)." msgstr "" +"Bu bölüm, (henüz) gruplandırılamayan diğer tüm entegrasyonları içerecektir." -#: ../system/objects/types.rst:148 +#: ../system/integrations/ldap/index.rst:2 +msgid "LDAP / Active Directory" +msgstr "LDAP / Active Directory" + +#: ../system/integrations/ldap/index.rst:4 msgid "" -"Defines the type of the input field. This allows e.g. your browser to ensure " -"that you provide the specific type." +"Zammad comes with a powerful LDAP integration that allows you to have a " +"single source of truth. By this you reduce the number of login credentials " +"your user has to remember." msgstr "" -#: ../system/objects/types.rst:152 -msgid "Currently available:" +#: ../system/integrations/ldap/index.rst:10 +msgid "" +"The LDAP source is also a perfect candidate for Zammad's :docs:`Kerberos " +"Single Sign-On ` but also works as addition " +"to other :doc:`/settings/security/third-party`." msgstr "" -#: ../system/objects/types.rst:155 -msgid "Phone" +#: ../system/integrations/ldap/index.rst:None +msgid "Zammands LDAP management page" msgstr "" -#: ../system/objects/types.rst:156 -msgid "Text" -msgstr "Metin" +#: ../system/integrations/ldap/index.rst:25 +#, fuzzy +msgid "📝 :doc:`manage`" +msgstr ":doc:`Yönetim > Tetikleyiciler `" -#: ../system/objects/types.rst:157 -msgid "Url *(URL fields disable link-template availability)*" +#: ../system/integrations/ldap/index.rst:25 +msgid "Add, modify, remove or re-arrange your LDAP-Sources as needed." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Text fields" +#: ../system/integrations/ldap/index.rst:30 +msgid "Before you continue, please note the following limitations." msgstr "" -#: ../system/objects/types.rst:174 -msgid "Single tree selection field" +#: ../system/integrations/ldap/index.rst:32 +msgid "Mapping / Synchronizing organizations is not possible" msgstr "" -#: ../system/objects/types.rst:168 +#: ../system/integrations/ldap/index.rst:36 msgid "" -"Provides a select-like field with up to 6 layers of options. Does not allow " -"setting a default value." +"You may want to consider using domain based assignments to overcome this " +"issue. Learn more on :doc:`/manage/organizations/index`." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Tree Select fields" +#: ../system/integrations/ldap/index.rst:39 +msgid "" +"Zammad's LDAP sync is one way. Editing user settings or permissions may be " +"overwritten upon the next sync depending on your configuration." msgstr "" -#: ../system/objects/types.rst:183 -msgid "Multiple tree selection field" +#: ../system/integrations/ldap/index.rst:41 +msgid "Nested groups are not supported." msgstr "" -#: ../system/objects/types.rst:177 -msgid "" -"Provides a select-like field with up to 6 layers of options allowing the " -"selection of multiple values. Does not allow setting a default value." +#: ../system/integrations/ldap/index.rst:42 +msgid "Synchronizing user avatars from LDAP is not supported." msgstr "" -#: ../system/objects/types.rst:302 -msgid "External Data Source field" +#: ../system/integrations/ldap/index.rst:43 +msgid "Unlike user filters, group filters cannot be changed." msgstr "" -#: ../system/objects/types.rst:186 +#: ../system/integrations/ldap/index.rst:44 msgid "" -"Provides a searchable field which fetches data from an external system. This " -"can be useful if you have data outside of Zammad and don't want to maintain " -"both data sources." +"When a user originates from an LDAP server, Zammad will try to verify the " +"login credentials against LDAP first - if this fails Zammad will check its " +"local database." msgstr "" -#: ../system/objects/types.rst:190 -msgid "The feature works as follows:" +#: ../system/integrations/ldap/index.rst:50 +msgid "" +"Users can have local passwords even if they're LDAP users! You can learn " +"more about user accounts in general on :doc:`/manage/users/index`." msgstr "" -#: ../system/objects/types.rst:192 +#: ../system/integrations/ldap/index.rst:54 msgid "" -"Zammad sends a query with a search string (free text from agent or based on " -"a variable) in a pre-defined format (\"Search URL\") to an external system." +"When several LDAP sources contain the same user (meaning the same email " +"address), the user in question will be updated with every source configured. " +"*The last LDAP source will win.*" msgstr "" -#: ../system/objects/types.rst:195 +#: ../system/integrations/ldap/index.rst:58 +#, fuzzy msgid "" -"This external system searches for matches and provides a response as a JSON " -"structure to Zammad." -msgstr "" +"This is subject to change with `Issue 4109 `_ in the future." +msgstr "Şu anda mevcut değil, `Issue 2769 `_a göz atın" -#: ../system/objects/types.rst:197 +#: ../system/integrations/ldap/index.rst:60 msgid "" -"Zammad just looks for the defined list and value keys, reads the content and " -"displays the value to the user. There is no search on Zammad side." +"Synchronization statistics currently affect *all* configured LDAP sources. " +"This also applies for newly added or updated sources." msgstr "" -#: ../system/objects/types.rst:201 +#: ../system/integrations/ldap/index.rst:63 +#, fuzzy msgid "" -"The usage of a PostgreSQL database for Zammad is required. In any other " -"case, Zammad will hide the external data source type and you are not able to " -"use it. If you want to use this feature, consider to :docs:`migrate your " -"database `." +"This is subject to change with `Issue 4108 `_ in the future." +msgstr "Şu anda mevcut değil, `Issue 2769 `_a göz atın" + +#: ../system/integrations/ldap/index.rst:65 +msgid "" +"Zammad currently has limited fallback server support. You can workaround " +"this by providing several sources - however, ensure to have the exact same " +"configuration on your fallback." msgstr "" -#: ../system/objects/types.rst:205 -msgid "Currently, only ``GET`` is supported as request method." +#: ../system/integrations/ldap/index.rst:69 +#, fuzzy +msgid "" +"This is subject to improve with `Issue 4107 `_ in the future." +msgstr "Şu anda mevcut değil, `Issue 2769 `_a göz atın" + +#: ../system/integrations/ldap/index.rst:76 +msgid "" +"This section holds all requests Zammad handled for all LDAP sources. These " +"entries can either contain synchronization information or logins " +"(authentication attempts via Zammad's login interface)." msgstr "" -#: ../system/objects/types.rst:206 +#: ../system/integrations/ldap/index.rst:80 msgid "" -"The data structure must be in JSON format and provide the objects in an " -"array." +"By clicking on any request, Zammad will provide even more information. The " +"provided information can be useful when something does not work as expected." msgstr "" -#: ../system/objects/types.rst:208 +#: ../system/integrations/ldap/index.rst:85 msgid "" -"The endpoint for the external data source has to support search. On Zammad " -"side, there is no search/logic implemented; however, you can define the " -"output key and value based on the result(s) from the response (which " -"provides already filtered content based on the search)." +"Especially a LDAP synchronization can cause many log entries. The web " +"interface will always limit the number of shown entries to the last 50 " +"entries." msgstr "" -#: ../system/objects/types.rst:212 +#: ../system/integrations/ldap/index.rst:None msgid "" -"If you receive more results as expected, your external data source search " -"may not work properly or the structure of the URL is not correct. You should " -"get in touch with a responsible person from the external system." +"Screencast showing LDAP integration log entries and a detail view on\n" +"an entry." msgstr "" -#: ../system/objects/types.rst:217 +#: ../system/integrations/ldap/manage.rst:2 +msgid "Manage LDAP-Sources" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:6 msgid "" -"Please have a look :doc:`at our example `, where you can find a possible configuration for a public " -"dummy endpoint." +"Please keep in mind all current limitations for the LDAP synchronization. " +"This will help to understand scopes of the following operations better." msgstr "" -#: ../system/objects/types.rst:0 +#: ../system/integrations/ldap/manage.rst:65 #, fuzzy -msgid "Available settings for external data source fields" -msgstr "Posta Sunucusu Ayarları" +msgid "Add new source" +msgstr "Yeni bir planlayıcı ekle" -#: ../system/objects/types.rst:242 -msgid "Search URL" +#: ../system/integrations/ldap/manage.rst:10 +msgid "" +"Using the *New Source* button allows you to add new LDAP sources to your " +"installation. You're not limited in the number of sources, however, keep in " +"mind that many sources will also take more time to synchronize." msgstr "" -#: ../system/objects/types.rst:227 +#: ../system/integrations/ldap/manage.rst:14 msgid "" -"Set your endpoint where Zammad fetches the data. Please make sure to include " -"a valid search :doc:`variable <../variables>` as an URL parameter. Example " -"for a free text search at user input: ``#{search.term}``" +"You can choose between different encryption types, namely *SSL* and " +"*STARTTLS* or none of them (\"*No SSL*\"). If you choose *SSL* or " +"*STARTTLS*, Zammad will display an additional *SSL verification* option that " +"allows you to disable the verification, e.g. for self-signed SSL " +"certificates. You can also tell Zammad to use a different port by appending " +"``:`` to your hostname/IP." msgstr "" -#: ../system/objects/types.rst:232 +#: ../system/integrations/ldap/manage.rst:0 msgid "" -"If in doubt, ask the responsible person for the external data source how " -"they expect the strucuture of the URL." +"Screenshot of configuring a new LDAP source with SSL encryption and SSL " +"verification" msgstr "" -#: ../system/objects/types.rst:236 +#: ../system/integrations/ldap/manage.rst:26 msgid "" -"Depending on your search variable, the preview might work or not. The reason " -"is that the context might not be available and it is no bug." +"New Source with SSL transport security enabled and certificate verification" msgstr "" -#: ../system/objects/types.rst:239 +#: ../system/integrations/ldap/manage.rst:30 msgid "" -"Please also make sure to use a variable which is available in your object " -"context. For example you won't be able to search for a ticket in a user " -"object context." +"Using an user filter can be a good idea if you only require a small subset " +"of your LDAP users in Zammad." msgstr "" -#: ../system/objects/types.rst:252 -#, fuzzy -msgid "SSL Verification" -msgstr "Doğrulama" +#: ../system/integrations/ldap/manage.rst:42 +msgid "This especially affects inactive users" +msgstr "" -#: ../system/objects/types.rst:245 -msgid "Here you can switch the SSL verification to no." +#: ../system/integrations/ldap/manage.rst:34 +msgid "" +"As every LDAP behaves differently on which attributes and how they are set, " +"Zammad doesn't care about any flags." msgstr "" -#: ../system/objects/types.rst:249 +#: ../system/integrations/ldap/manage.rst:37 msgid "" -"If your external data source system is using self signed certificates, " -"please have a look :doc:`here ` for " -"further information about how to handle them in Zammad, so you can keep the " -"SSL verification activated." +"Users that no longer are returned by your LDAP source will automatically be " +"set to inactive. Zammad assumes that the user was deactivated." msgstr "" -#: ../system/objects/types.rst:258 -msgid "HTTP Authentication" +#: ../system/integrations/ldap/manage.rst:41 +msgid "" +"Users will never be removed automatically! If you want to remove obsolete " +"users, use :doc:`/system/data-privacy`." msgstr "" -#: ../system/objects/types.rst:255 +#: ../system/integrations/ldap/manage.rst:46 +#, fuzzy +msgid "Active Directory admins" +msgstr "LDAP / Active Directory" + +#: ../system/integrations/ldap/manage.rst:45 msgid "" -"If your external data source requires an authentication, you can set it " -"here. You can leave it empty or choose between *Basic Authentication* or " -"*Authentication Token* (selecting one of the two methods leads to additional " -"fields where you can enter your credentials/token)." +"Active Directories are quite specific on how to filter for active users only " +"- please see the `Microsoft documentation `_ for more " +"information." msgstr "" -#: ../system/objects/types.rst:265 -msgid "Search result list key" +#: ../system/integrations/ldap/manage.rst:51 +msgid "" +"*Do not* manually write pathes of either LDAP attributes or groups. If " +"Zammad does not display them, it either cannot find them or you have a lot " +"of users that don't have the attributes populated." msgstr "" -#: ../system/objects/types.rst:261 +#: ../system/integrations/ldap/manage.rst:55 msgid "" -"Defines the level in the JSON structure which provides the list with search " -"results. You can leave it empty, if the data is already provided as an " -"array. If you have to go deeper in the structure, you can provide a path " -"with ``.`` as separators, e.g. ``key.subkey.sub-sub-key``." +"Zammad will always only return attributes that are filled - this reduces the " +"returned list of attributes greatly." msgstr "" -#: ../system/objects/types.rst:271 -#, fuzzy -msgid "Search result value key" -msgstr "Varsayılan değer" +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing how to add a new LDAP source" +msgstr "" -#: ../system/objects/types.rst:268 +#: ../system/integrations/ldap/manage.rst:63 msgid "" -"Defines the attribute in the structure in which your external data source " -"provides the *value* for your data. An example would be a product *number*. " -"If you have to go deeper in the structure, you can provide a path with ``.`` " -"as separators, e.g. ``key.subkey.sub-sub-key``." +"If your LDAP system doesn't allow anonymous bind, Zammad detects it and " +"provides you an editable \"Base DN\" *text* field instead of a prefilled " +"*select* field." msgstr "" -#: ../system/objects/types.rst:277 -msgid "Search result label key" +#: ../system/integrations/ldap/manage.rst:81 +msgid "Review or edit existing source" +msgstr "" + +#: ../system/integrations/ldap/manage.rst:68 +msgid "" +"Clicking on a LDAP source will provide a configuration and mapping overview." msgstr "" -#: ../system/objects/types.rst:274 +#: ../system/integrations/ldap/manage.rst:70 msgid "" -"Defines the attribute in the structure in which your external data source " -"provides the *label* for your data. An example would be a product *name*. If " -"you have to go deeper in the structure, you can provide a path with ``.`` as " -"separators, e.g. ``key.subkey.sub-sub-key``." +"If needed you can then use the *Change* button to update either the name, " +"active state or the whole configuration. If you're changing the whole " +"configuration, the dialogue will be identical to the source creation." msgstr "" -#: ../system/objects/types.rst:280 +#: ../system/integrations/ldap/manage.rst:76 msgid "" -"In the preview area, you can find the following items (depending on your " -"configuration above):" +"Did your LDAP server change? Different LDAP servers have different " +"structures and default attributes. This causes the LDAP synchronization to " +"likely fail. Consider removing the affected source and re-add it." msgstr "" -#: ../system/objects/types.rst:283 -msgid "" -"**Error/hint message** (only if configuration is not complete): Zammad tells " -"you, if there is a problem and what you should change in your configuration." +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing the update of the source name." msgstr "" -#: ../system/objects/types.rst:286 -msgid "" -"**Search field**: search for an existing attribute in the data source to get " -"a preview. This is required for the fields below to show up." +#: ../system/integrations/ldap/manage.rst:89 +msgid "Re-arrange LDAP source's order" msgstr "" -#: ../system/objects/types.rst:288 +#: ../system/integrations/ldap/manage.rst:84 msgid "" -"**Search result response** (only if configuration is not complete): here you " -"can find a syntax highlighted JSON preview of the response, based on the " -"search term you entered." +"You can change the synchronization order for each source at any time. Zammad " +"will synchronize the sources from top to bottom." msgstr "" -#: ../system/objects/types.rst:291 +#: ../system/integrations/ldap/manage.rst:0 msgid "" -"**Search result list** (only if *search result list key* is properly set): " -"output of the structure under the configured *search result list key*." +"Screencasting showing how to change the source order by using\n" +"drag and drop." msgstr "" -#: ../system/objects/types.rst:294 -msgid "" -"**Preview table** (when fully configured): Zammad shows you a table which " -"includes the found items based on the search string (value, label and " -"optional link). You can use this preview if you don't have the complete data " -"structure of the external system in mind." +#: ../system/integrations/ldap/manage.rst:101 +msgid "Remove a source" msgstr "" -#: ../system/objects/types.rst:299 +#: ../system/integrations/ldap/manage.rst:92 msgid "" -"An example of a configured external data source field from agent perspective:" +"If you no longer need the a LDAP source or simply want to start over, you " +"can remove them at any time. This will not remove synchronized users, data " +"synchronized or permissions." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Screencast showing the search for a product in a ticket" +#: ../system/integrations/ldap/manage.rst:98 +msgid "" +"Not sure if you'd need the source later on? Set the source to inactive " +"instead of removing it - see *Review or edit existing source* for more." msgstr "" -#: ../system/objects/types.rst:307 -msgid "URL fields (Link-Template)" -msgstr "URL alanları (Bağlantı-Şablon)" +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing how to remove LDAP sources." +msgstr "" -#: ../system/objects/types.rst:311 -msgid "" -"This function is restricted to Text, Select and External data source types " -"only." +#: ../system/integrations/pgp/index.rst:2 +msgid "PGP" msgstr "" -#: ../system/objects/types.rst:314 +#: ../system/integrations/pgp/index.rst:7 msgid "" -"Link-Templates are an amazing way to dynamically generate URLs. They allow " -"you to integrate other systems better without having to manually copy data " -"from Zammad if possible." +"Pretty Good Privacy (PGP) is another method for secure email communication. " +"With PGP, you can exchange **signed** and **encrypted** messages with others." msgstr "" -#: ../system/objects/types.rst:320 -msgid "" -"Another great way of communicating with another system may be Zammad's :doc:" -"`Webhooks `." +#: ../system/integrations/pgp/index.rst:13 +#: ../system/integrations/smime/index.rst:17 +msgid "Signing" +msgstr "İmzalama" + +#: ../system/integrations/pgp/index.rst:11 +msgid "is a proof that a message hasn't been manipulated on its way." msgstr "" -#: ../system/objects/types.rst:323 +#: ../system/integrations/pgp/index.rst:13 +#, fuzzy msgid "" -"After filling a link-template enabled field, an URL icon will appear on its " -"right. Clicking on the icon opens a new tab." -msgstr "" +"In other words, it guarantees message **integrity** and **authenticity**." +msgstr "Başka bir deyişle, *gizlilik* ve *veri güvenliği*ni garanti eder." -#: ../system/objects/types.rst:328 +#: ../system/integrations/pgp/index.rst:19 +#: ../system/integrations/smime/index.rst:22 +msgid "Encryption" +msgstr "Şifreleme" + +#: ../system/integrations/pgp/index.rst:16 +#: ../system/integrations/smime/index.rst:20 msgid "" -"Even though Zammad displays the link template within object edit and create " -"screens, the function is optional. It's only active if you populate the " -"field." +"scrambles a message so that it can only be unscrambled by the intended " +"recipient." msgstr "" -#: ../system/objects/types.rst:333 +#: ../system/integrations/pgp/index.rst:19 +#, fuzzy msgid "" -"What's the difference between URL and text fields with link template...?!" +"In other words, it guarantees message **privacy** and **data security**." +msgstr "Başka bir deyişle, *gizlilik* ve *veri güvenliği*ni garanti eder." + +#: ../system/integrations/pgp/index.rst:25 +msgid "Screenshot of ticket creation with encrypt and sign buttons" msgstr "" -#: ../system/objects/types.rst:335 +#: ../system/integrations/pgp/index.rst:25 msgid "" -"Both fields have different use cases. Use ``text`` type text fields when " -"ever you have a *static* url that requires dynamic parameters. If you " -"require a drag & drop like field that you can put in any URL, use ``URL`` " -"type text fields." +"Once PGP has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " +"appear in the ticket composer." msgstr "" -#: ../system/objects/types.rst:340 -msgid "" -"The difference is easier to spot when comparing the fields directly, below " -"screencast shows the result - the dynamic approach uses existing values in " -"the moment of updating to built the URL - e.g. ``https://google.com/search?" -"q=cookies`` - while the URL approach uses the actual URL of the field - e.g. " -"``https://zammad.com``." +#: ../system/integrations/pgp/index.rst:28 +msgid "**Sign button not visible?**" msgstr "" -#: ../system/objects/types.rst:None +#: ../system/integrations/pgp/index.rst:30 msgid "" -"Screencast showing the differents in between URL and text type fields with " -"actual values" +"Please note that the signing of emails is based on the outgoing email " +"account. That means you have to choose a group with a sender email account, " +"which has a private key assigned." msgstr "" -#: ../system/objects/types.rst:352 -msgid "How does this work...?!" -msgstr "Bu nasıl çalışır... ?!" +#: ../system/integrations/pgp/index.rst:35 +#, fuzzy +msgid "Handling of Keys" +msgstr "Makro Yönetimi" -#: ../system/objects/types.rst:354 +#: ../system/integrations/pgp/index.rst:36 msgid "" -"As an example, let's say you have an attribute called ``amazing_attribute`` " -"and you want to open a google search directly with the input from that field." +"To use the PGP function, you have to enable the integration (PGP) by " +"switching the toggle to *enabled*." msgstr "" -#: ../system/objects/types.rst:357 +#: ../system/integrations/pgp/index.rst:39 msgid "" -"Providing the link-template field below allows you to do so: ``https://www." -"google.com/search?q=#{ticket.amazing_attribute}``" +"You can add keys by clicking the *add key* button. The keys can be imported " +"from a file or you can paste the content of the key in the text box." msgstr "" -#: ../system/objects/types.rst:362 -msgid "" -"You can use any :doc:`Zammad variable ` as long as it's " -"available in the moment you need it." +#: ../system/integrations/pgp/index.rst:42 +msgid "**Which keys do I have to import?**" msgstr "" -#: ../system/objects/types.rst:365 +#: ../system/integrations/pgp/index.rst:44 msgid "" -"As a result, you are redirected to Google with a search for the value of the " -"attribute, if you click on the button in the ticket (as you can see in the " -"screencast above)." +"For **signing** *outgoing* emails, you have to import the private key of " +"your Zammad email account." msgstr "" -#: ../system/packages.rst:2 -msgid "Packages" -msgstr "Paketler" - -#: ../system/packages.rst:4 -msgid "That's the package management-area." -msgstr "Burası paket yönetim alanı." - -#: ../system/packages.rst:6 -msgid "Individual add-ons for Zammad can be installed and managed here." -msgstr "Zammad için özel eklentiler buradan kurulabilir ve yönetilebilir." - -#: ../system/sessions.rst:2 -msgid "Sessions" -msgstr "Oturumlar" - -#: ../system/sessions.rst:4 +#: ../system/integrations/pgp/index.rst:47 msgid "" -"Sessions management allows reviewing currently known user sessions and " -"allows to end these. The session timeout is affected by :ref:" -"`security_session_timeout` configurations from security settings." +"For **encrypting** *outgoing* emails, you have to import the public key of " +"the customer's email account." msgstr "" -#: ../system/sessions.rst:None -msgid "Screenshot showing Zammad's session management" +#: ../system/integrations/pgp/index.rst:50 +msgid "" +"For **verifying the signature** of signed *incoming* emails, you have to " +"import the public key of the customer." msgstr "" -#: ../system/sessions.rst:13 -#, fuzzy -msgid "Zammad will provide the following information:" -msgstr "Bu bölümde şu anda aşağıdaki entegrasyonlar eksik:" - -#: ../system/sessions.rst:16 +#: ../system/integrations/pgp/index.rst:53 msgid "" -"The user account this session entry belongs to. It can be normal if a user " -"has several sessions in the list. This can be due to changed browser " -"information or if you use e.g. single sign on methods where the user does " -"not use the log off button." +"For **decrypting** of encrypted *incoming* emails, you have to import the " +"private key of your Zammad email account." msgstr "" -#: ../system/sessions.rst:22 -msgid "Browser" +#: ../system/integrations/pgp/index.rst:57 +msgid "Import Keys From a File" msgstr "" -#: ../system/sessions.rst:22 -msgid "The browser agent communicated to Zammad." +#: ../system/integrations/pgp/index.rst:58 +msgid "You can import keys from a file in the section **Upload key**:" msgstr "" -#: ../system/sessions.rst:40 -#, fuzzy -msgid "Location" -msgstr "Bildirimleri Engelle" +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of adding a key via file" +msgstr "" -#: ../system/sessions.rst:25 +#: ../system/integrations/pgp/index.rst:64 msgid "" -"The anticipated location based on the users IP address. Depending on the IP " -"address the result shown may differ. This option depends on :doc:`/settings/" -"system/services`." +"**Supported file formats:** ASCII-armor as well as binary GPG format " +"(basically any GPG supported key format) is supported here." msgstr "" -#: ../system/sessions.rst:29 -msgid "The following information can be shown:" +#: ../system/integrations/pgp/index.rst:68 +msgid "Import Keys by Pasting the Content" msgstr "" -#: ../system/sessions.rst:33 -#, fuzzy -msgid "IP address" -msgstr "Proxy Adresi" - -#: ../system/sessions.rst:32 -msgid "" -"Either if you set *Geo IP services* to inactive or you're using internal IP " -"address which do not provide location information." +#: ../system/integrations/pgp/index.rst:69 +msgid "You can also paste the key's content in the section **paste key**:" msgstr "" -#: ../system/sessions.rst:40 -msgid "Country (or Country + City)" +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of adding a key via pasting" msgstr "" -#: ../system/sessions.rst:36 +#: ../system/integrations/pgp/index.rst:75 msgid "" -"If *Geo IP services* is enabled only. Depends on how detailed the available " -"IP address information are." +"**Supported format:** Please note that only ASCII-armor is supported here." msgstr "" -#: ../system/sessions.rst:39 -msgid "" -"Be aware that results can be inaccurate - this technically is not an error." -msgstr "" +#: ../system/integrations/pgp/index.rst:78 +#, fuzzy +msgid "Deleting Keys" +msgstr "Kullanıcıları Silmek" -#: ../system/sessions.rst:43 -msgid "Age" +#: ../system/integrations/pgp/index.rst:79 +msgid "" +"If you want to delete a specific key, you can do it by clicking on the menu " +"in the *actions* column and select **delete**:" msgstr "" -#: ../system/sessions.rst:43 -msgid "Provides the time when the session initially has been created." +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of deleting a key" msgstr "" -#: ../system/sessions.rst:50 +#: ../system/integrations/pgp/index.rst:88 #, fuzzy -msgid "Update" -msgstr "Güncelleme Zamanı" +msgid "Downloading Keys" +msgstr "Sertifika Ekle" -#: ../system/sessions.rst:46 +#: ../system/integrations/pgp/index.rst:89 msgid "" -"Provides the time the user used this session to open Zammad. This timestamp " -"is only updated if the user e.g. reloads, not during normal work on tickets." +"If you want to download your keys, you can do this as well via corresponding " +"action buttons. Depending on the key, you can choose wether you want to " +"download the private or the public key." msgstr "" -#: ../system/sessions.rst:50 -msgid "This timestamp is being used for the session timeout." -msgstr "" +#: ../system/integrations/pgp/index.rst:95 +#: ../system/integrations/smime/manage-certificates.rst:76 +msgid "Default Behavior" +msgstr "Varsayılan Davranış" -#: ../system/sessions.rst:53 +#: ../system/integrations/pgp/index.rst:96 msgid "" -"Use the delete button to remove a single session on behalf of your user." +"Here you can adjust on per group basis, if *sign* and *encryption* is on or " +"off by default. Please be aware, that agents can always override the setting " +"for each individual article." msgstr "" -#: ../system/subscription/billing.rst:2 -msgid "Billing" +#: ../system/integrations/pgp/index.rst:None +msgid "Adjusting default behavior on per group basis" msgstr "" -#: ../system/subscription/billing.rst:4 +#: ../system/integrations/pgp/index.rst:107 msgid "" -"Within the billing tab you can control all billing relevant information like " -"invoices, billing address and the option to cancel your subscription." +"Here you can see the last actions regarding signing and encryption and if " +"they were successful." msgstr "" -#: ../system/subscription/billing.rst:33 -#, fuzzy -msgid "Billing information" -msgstr "Web site bilgisi" - -#: ../system/subscription/billing.rst:8 -msgid "" -"All adjusted billing information below only affect future invoices. If your " -"invoice was issued wrong, please contact `our sales team `_." +#: ../system/integrations/pgp/index.rst:117 +msgid "**Sign button is not visible, but keys are imported.**" msgstr "" -#: ../system/subscription/billing.rst:14 -#, fuzzy -msgid "Billing address" -msgstr "E-posta Adresi" +#: ../system/integrations/pgp/index.rst:115 +msgid "Did you choose a group in the ticket?" +msgstr "" -#: ../system/subscription/billing.rst:13 +#: ../system/integrations/pgp/index.rst:116 msgid "" -"Provide your company address here, make sure to include the companies name " -"in case required. This address will be referenced on your invoice." +"Did you import a private key for the email adress, which is used for " +"outgoing emails in the group?" msgstr "" -#: ../system/subscription/billing.rst:18 -msgid "VAT ID" +#: ../system/integrations/pgp/index.rst:122 +msgid "**How to obtain keys?**" msgstr "" -#: ../system/subscription/billing.rst:17 +#: ../system/integrations/pgp/index.rst:120 msgid "" -"Provide your VAT ID here. If applicable your invoice will not contain German " -"VAT. Please make sure to pay the VAT in your country as required." +"You can create them yourself! There are some good tutorials on the web on " +"how to create them. Providing keys to Zammad is a prerequisite to use the " +"PGP feature." msgstr "" -#: ../system/subscription/billing.rst:27 -#, fuzzy -msgid "Billing Email Address" -msgstr "E-posta Adresi" - -#: ../system/subscription/billing.rst:21 -msgid "" -"Usually the instance owner (the person that registered the instance) will " -"receive all emails including the invoices. In case you have your own billing " -"department, you can provide their email address here." +#: ../system/integrations/pgp/index.rst:127 +msgid "**It says a passphrase is needed, but I haven't got one.**" msgstr "" -#: ../system/subscription/billing.rst:25 +#: ../system/integrations/pgp/index.rst:125 msgid "" -"All billing relevant information will then be sent to this email address." +"If the key is secured with a passphrase, you have to provide it for the " +"import in Zammad. It is possible that keys may have an empty passphrase. " +"However, this is *not* recommended." msgstr "" -#: ../system/subscription/billing.rst:27 -msgid "Invoices are sent as attachment (PDF) to this email address." +#: ../system/integrations/pgp/index.rst:132 +msgid "**How do my customers get my new key?**" msgstr "" -#: ../system/subscription/billing.rst:29 +#: ../system/integrations/pgp/index.rst:130 msgid "" -"Don't forget to press the *Submit* button after you changed above settings." +"You have to provide your **public** key in advance. Your customer also has " +"to configure PGP in their email workflow and import your public key. The " +"other way round, you have to get the public key of your customer and have to " +"import it to Zammad." msgstr "" -#: ../system/subscription/billing.rst:0 -msgid "" -"Screenshot showing options for billing information within the\n" -"subscription menu" -msgstr "" +#: ../system/integrations/slack.rst:2 +msgid "Slack" +msgstr "Slack" -#: ../system/subscription/billing.rst:70 -msgid "Payment history" +#: ../system/integrations/slack.rst:4 +msgid "**⚠️ Deprecation warning ⚠️**" msgstr "" -#: ../system/subscription/billing.rst:36 +#: ../system/integrations/slack.rst:6 msgid "" -"The payment history will display a history of all paid invoices. At this " -"point you can also download these in case you need them again." +"Zammad 7 will no longer support this dedicated Slack integration. It is " +"recommended to switch to :doc:`pre-defined webhooks ` instead. Existing Slack integrations should " +"be migrated manually before this feature is dropped." msgstr "" -#: ../system/subscription/billing.rst:41 +#: ../system/integrations/slack.rst:14 msgid "" -"You will only find *paid* invoices here. Invoices that are to be billed are " -"not available before the payment is completed." +"In order to use this feature, please add a new Slack app to your Workspace. " +"The App you need is called ``Incoming WebHooks`` ." msgstr "" -#: ../system/subscription/billing.rst:46 -msgid "Date" -msgstr "Tarih" +#: ../system/integrations/slack.rst:18 +#, fuzzy +msgid "Why Do I Need This Feature?" +msgstr "Neden bu özelliğe ihtiyacım var?" -#: ../system/subscription/billing.rst:46 -msgid "Date of the invoice creation." +#: ../system/integrations/slack.rst:20 +msgid "" +"If you're already using Slack for your team communication, you'll love this " +"feature! Our Slack integration can push ticket notifications about the last " +"ticket article based on the following events:" msgstr "" -#: ../system/subscription/billing.rst:49 -#, fuzzy -msgid "Amount" -msgstr "Hesaplar" +#: ../system/integrations/slack.rst:24 +msgid "on Ticket creation" +msgstr "Bilet oluşturulduğunda" -#: ../system/subscription/billing.rst:49 -msgid "Invoice total including VAT if applicable." -msgstr "" +#: ../system/integrations/slack.rst:25 +msgid "on Ticket updates" +msgstr "Bilet güncellemelerinde" -#: ../system/subscription/billing.rst:52 -msgid "" -"Contains contract period (monthly or yearly) and hosted plan for the " -"subscription period in question." +#: ../system/integrations/slack.rst:26 +msgid "on reached reminders" msgstr "" -#: ../system/subscription/billing.rst:63 -msgid "Payment method / Service period" +#: ../system/integrations/slack.rst:27 +msgid "a Ticket has escalated" +msgstr "Bir bilet yükseldi" + +#: ../system/integrations/slack.rst:28 +msgid "a Ticket is going to escalate" msgstr "" -#: ../system/subscription/billing.rst:56 +#: ../system/integrations/slack.rst:30 msgid "" -"Used bank account or credit card as well as the subscription period the " -"invoice is about." +"Zammad will provide the Ticket title, a direct link to the Ticket, the event " +"type (creation, updated, escalation), the customer, time and the last " +"article that has triggered the notification." msgstr "" -#: ../system/subscription/billing.rst:61 +#: ../system/integrations/slack.rst:34 msgid "" -"It might happen that the invoice date and subscription period differ. This " -"is nothing to worry about, the subscription periods will be accounted later " -"on." +"This will give you further options, as you can see e.g. escalating tickets " +"that are assigned to an agent that's e.g. absent. You can interact faster, " +"as you might see problems earlier (or even before the problem gets one)." msgstr "" -#: ../system/subscription/billing.rst:67 -msgid "Receipt" +#: ../system/integrations/slack.rst:38 +msgid "" +"If needed and wanted, you can even discuss directly about the topic before " +"sending an answer to the customer. Another possible use case would be a " +"agent monitoring new agents and their answers to tickets." msgstr "" -#: ../system/subscription/billing.rst:66 +#: ../system/integrations/slack.rst:44 +#, fuzzy +msgid "Configure the Integration" +msgstr "Entegrasyonu yapılandır" + +#: ../system/integrations/slack.rst:46 msgid "" -"Use the arrow to download the invoice in question. You can download all " -"available invoices any time you need to here!" +"First of all, please go to your slack workspace - go to administration => " +"Manage Apps. If you don't have an app yet, you can simply add a new one - " +"just search for ``Incoming WebHooks`` and customize the app to your needs." msgstr "" -#: ../system/subscription/billing.rst:0 -msgid "Screenshot showing payment history of a hosted instance" +#: ../system/integrations/slack.rst:50 +msgid "" +"Choose (or create) the channel Zammad should post it's information to and " +"press on \"Add Incoming WebHooks integration\". If you're ready, copy the " +"provided WebHook URL and go to your Zammad installation." msgstr "" -#: ../system/subscription/billing.rst:94 -msgid "Do you want to cancel your subscription?" +#: ../system/integrations/slack.rst:56 +msgid "" +"You need administrative rights on the Slack Workspace. The link to the app " +"directory is normally ``https://[workspace-name].slack.com/apps`` ." msgstr "" -#: ../system/subscription/billing.rst:73 +#: ../system/integrations/slack.rst:63 msgid "" -"In case you no longer want to use Zammad's SaaS, you can cancel your " -"subscription by using the red *Yes, please cancel my subscription* button." +"To configure the slack integration, log in to Zammad and go to Integrations " +"(System) => Slack in the admin panel." msgstr "" -#: ../system/subscription/billing.rst:76 +#: ../system/integrations/slack.rst:66 msgid "" -"Your subscription will end the day after your trial or billing period ends." +"Here you can choose on what evens Zammad should post information about a " +"ticket to your Slack channel. Next you need to device what groups shall be " +"affected by this, as anybody with access to that specific Slack channel can " +"read at least parts of the ticket this might be a privacy issue, if you " +"select the wrong groups. The username is simply the name that Zammad uses as " +"display name inside the Slack chat. The channel defines the Slack channel " +"the information is being posted in. As last option, you can set a custom " +"icon for posting to slack." msgstr "" -#: ../system/subscription/billing.rst:80 +#: ../system/integrations/slack.rst:74 msgid "" -"We will remind you about your cancelled subscription several times up front. " -"After the subscription ended all instance data will be removed. A restore " -"*is not* possible after that point!" +"When you're ready, just hit \"Submit\" and enable the integration. Zammad " +"will now post new ticket information based on the trigger you chose. Below " +"the options you have the recent log that shows the latest requests to Slack " +"for debugging if needed." msgstr "" -#: ../system/subscription/billing.rst:0 -msgid "Screencast showing how to cancel a subscription" +#: ../system/integrations/slack.rst:81 +msgid "" +"If you leave the Icon URL empty, Zammad will use the Zammad logo instead. " +"The icon should be a square PNG file." msgstr "" -#: ../system/subscription/billing.rst:87 -msgid "**😖 Cancelled by accident?**" +#: ../system/integrations/slack.rst:90 +msgid "" +"The following figure shows how it will look if you choose to receive updates " +"on created and updated tickets. On every post Zammad sends to the Slack " +"channel, you can create new threads to discuss about the new article." msgstr "" -#: ../system/subscription/billing.rst:89 +#: ../system/integrations/slack.rst:96 msgid "" -"You can always undo the cancellation via the *Yes, undo the cancellation of " -"my subscription* button up to the last subscription day!" +"If you just want to keep track of soon escalating or already escalated " +"tickets, it will look the the following figure. Zammad changes the color in " +"front of the post so you can easily see the state of the ticket." msgstr "" -#: ../system/subscription/billing.rst:0 +#: ../system/integrations/slack.rst:102 msgid "" -"Screenshot showing a red button to cancel the subscription\n" -"cancellation" +"If you change the state, Zammad will also put information on what state the " +"ticket gets and (if pending state) the date until it pends. You'll also " +"recognize the color codes in front of posts on slack, as they are exact the " +"same the ticket state colors you'll see in Zammad!" msgstr "" -#: ../system/subscription/index.rst:2 -#, fuzzy -msgid "Subscription (SaaS)" -msgstr "Açıklama" +#: ../system/integrations/smime/index.rst:2 +msgid "S/MIME" +msgstr "S/MIME" -#: ../system/subscription/index.rst:4 +#: ../system/integrations/smime/index.rst:11 msgid "" -"The subscription settings page allows you to configure your instances " -"package and number of agents required." +"S/MIME is the most widely-supported method for secure email communication. " +"With S/MIME, you can exchange **signed** and **encrypted** messages with " +"others." msgstr "" -#: ../system/subscription/index.rst:9 +#: ../system/integrations/smime/index.rst:15 msgid "" -"This setting section is only available for Hosted setups. If you're looking " -"for on premise support contracts, please see the `Zammad pricing page " -"`_." +"is proof that a message hasn't been tampered with or sent by an impersonator." msgstr "" -#: ../system/subscription/index.rst:20 +#: ../system/integrations/smime/index.rst:17 +#, fuzzy msgid "" -"The subscription section currently consists of two tabs: Plan & Billing. For " -"your overview we've divided those two tabs into independent sub pages:" -msgstr "" +"In other words, it guarantees a message's **integrity** and **authenticity**." +msgstr "Başka bir deyişle, *gizlilik* ve *veri güvenliği*ni garanti eder." -#: ../system/subscription/index.rst:25 -msgid ":doc:`💰 Subscription plan `" +#: ../system/integrations/smime/index.rst:22 +msgid "In other words, it guarantees **privacy** and **data security**." +msgstr "Başka bir deyişle, *gizlilik* ve *veri güvenliği*ni garanti eder." + +#: ../system/integrations/smime/index.rst:28 +msgid "Screencast demo of S/MIME features for both new tickets and replies" msgstr "" -#: ../system/subscription/index.rst:24 +#: ../system/integrations/smime/index.rst:28 msgid "" -"Everything affecting your instance subscription functions like number of " -"agents, package and payment method." +"Once S/MIME has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " +"appear in the ticket composer." msgstr "" -#: ../system/subscription/index.rst:28 -msgid ":doc:`🧾 Subscription billing `" +#: ../system/integrations/smime/index.rst:32 +msgid ":doc:`🔪 Prerequisites `" msgstr "" -#: ../system/subscription/index.rst:28 +#: ../system/integrations/smime/index.rst:31 msgid "" -"Everything regarding billing address, invoices and account cancellation." +"New to S/MIME? This section helps you to find certificate providers and " +"points out Limitations." msgstr "" -#: ../system/subscription/index.rst:33 -msgid "FAQ" +#: ../system/integrations/smime/index.rst:35 +msgid ":doc:`📝 Manage Certificates `" msgstr "" -#: ../system/subscription/index.rst:37 -msgid "I set up a trial account but am missing functions to test" +#: ../system/integrations/smime/index.rst:35 +msgid "Add and download certificates; configure group default behaviors." msgstr "" -#: ../system/subscription/index.rst:36 -msgid "" -"The trial instance is running within the professional package allowing up to " -"three agents." +#: ../system/integrations/smime/index.rst:38 +msgid ":doc:`😦 Troubleshooting `" msgstr "" -#: ../system/subscription/index.rst:40 -msgid "Can I change package within the trial?" +#: ../system/integrations/smime/index.rst:38 +msgid "Took a wrong turn? About recent logs and common issues." msgstr "" -#: ../system/subscription/index.rst:40 -msgid "No. As soon as the package is changed the subscription begins." +#: ../system/integrations/smime/index.rst:43 +msgid "" +"For more details on how S/MIME integration works on the agent side, see the :" +"user-docs:`user docs `." msgstr "" -#: ../system/subscription/index.rst:45 -msgid "What happens to my trial instance after the trial period ended?" +#: ../system/integrations/smime/manage-certificates.rst:2 +msgid "Manage Certificates" msgstr "" -#: ../system/subscription/index.rst:43 +#: ../system/integrations/smime/manage-certificates.rst:4 msgid "" -"Your instance will automatically be canceled for you. Please see *What " -"happens to my instance after it has been canceled?* for more." +"S/MIME is **disabled by default**. Enable it to start adding certificates." msgstr "" -#: ../system/subscription/index.rst:58 -msgid "What happens to my instance after it has been canceled?" +#: ../system/integrations/smime/manage-certificates.rst:10 +msgid "Dialogue to add new certificates or private keys" msgstr "" -#: ../system/subscription/index.rst:48 -msgid "That depends slightly on your instance state:" +#: ../system/integrations/smime/manage-certificates.rst:10 +msgid "" +"Manage certificates in the Admin Panel under **System > Integrations > S/" +"MIME**. Certificates may be pasted in as plain text or uploaded from a file." msgstr "" -#: ../system/subscription/index.rst:54 +#: ../system/integrations/smime/manage-certificates.rst:14 #, fuzzy -msgid "Trial instance" -msgstr "Örneğin:" +msgid "Add Certificate Data" +msgstr "Sertifika Ekle" + +#: ../system/integrations/smime/manage-certificates.rst:36 +msgid "Add Certificate" +msgstr "Sertifika Ekle" -#: ../system/subscription/index.rst:51 +#: ../system/integrations/smime/manage-certificates.rst:17 msgid "" -"If you're still on trial, we will ice your instance and remind you once " -"again about your instance. We then will wait some days and remove your " -"instance from our system. This is the last time we will inform you by Email." +"Import public-key certificates for both your own organization and your " +"contacts." msgstr "" -#: ../system/subscription/index.rst:58 -#, fuzzy -msgid "Paid instance" -msgstr "Örneğin:" - -#: ../system/subscription/index.rst:57 +#: ../system/integrations/smime/manage-certificates.rst:19 msgid "" -"If you're a paying customer and canceled your subscription, the instance " -"removal will take place the day after your last subscription day." +"You can also add a bunch of certificates in one go by providing a single " +"file with all relevant certificates." msgstr "" -#: ../system/subscription/index.rst:60 -msgid "Can removed instances be restored?" +#: ../system/integrations/smime/manage-certificates.rst:22 +msgid "🕵️ **ALWAYS verify certificates in-person or over the phone!**" msgstr "" -#: ../system/subscription/index.rst:61 -msgid "No. Once your instance has been removed, a restoration is not possible." +#: ../system/integrations/smime/manage-certificates.rst:24 +msgid "" +"The whole point of signatures is to alert you when someone is trying to " +"pretend to be someone they're not. Never accept a certificate from someone " +"online without verifying it first." msgstr "" -#: ../system/subscription/plan.rst:2 ../system/subscription/plan.rst:38 -msgid "Plan" +#: ../system/integrations/smime/manage-certificates.rst:28 +msgid "📇 **What about trusted certificate authorities?**" msgstr "" -#: ../system/subscription/plan.rst:16 -#, fuzzy -msgid "Subscription" -msgstr "Açıklama" - -#: ../system/subscription/plan.rst:5 +#: ../system/integrations/smime/manage-certificates.rst:30 msgid "" -"On the top of the subscription summary you'll find the number of used and " -"available (booked) agent seats. By using the *see more* link you can also " -"expand an agent list to see the currently configured active agents. This " -"list *does not* count accounts with admin permissions only." +"In some cases (e.g. when dealing with large enterprises), you may be given a " +"certificate for an entire CA, rather than a single contact. Add it here to " +"trust *all* certificates issued by that CA." msgstr "" -#: ../system/subscription/plan.rst:0 +#: ../system/integrations/smime/manage-certificates.rst:35 msgid "" -"Within subscription you can always see how many agents are still\n" -"available to add and who uses the seats." +"Commercial CAs can usually be verified online. Zammad does not include a " +"list of built-in, trusted CAs." msgstr "" -#: ../system/subscription/plan.rst:14 +#: ../system/integrations/smime/manage-certificates.rst:57 +msgid "Add Private Key" +msgstr "Özel Anahtar Ekle" + +#: ../system/integrations/smime/manage-certificates.rst:39 msgid "" -"Learn more on how to manage your agents in general :doc:`here `." +"Once you've added a public-key certificate, you can import its matching " +"private key." msgstr "" -#: ../system/subscription/plan.rst:19 +#: ../system/integrations/smime/manage-certificates.rst:42 msgid "" -"This section gives you an overview of the available plans and their " -"functions / limits. If you require a more detailed table, check our " -"`detailed pricing table `_ for more." +"Private keys are for **your own organization only**; never ask your contacts " +"for their private keys." msgstr "" -#: ../system/subscription/plan.rst:23 +#: ../system/integrations/smime/manage-certificates.rst:0 msgid "" -"Your selection in this step will decide on the base agent price and e.g. " -"agent limits that might apply in the summary step." +"S/MIME integration showing configured certificates and possible issues with " +"Logging" msgstr "" -#: ../system/subscription/plan.rst:26 +#: ../system/integrations/smime/manage-certificates.rst:50 msgid "" -"The green *Selected* button will also tell you what plan you're currently in." +"A note is displayed on certificates with a matching private key (see line 2)." msgstr "" -#: ../system/subscription/plan.rst:30 -msgid "" -"Trial instances are running at Professional with 3 agents. The plan cannot " -"be changed during the trial for technical reasons, if you require more " -"agents for testing, please contact `our sales team `_ with a reason for the raise request." +#: ../system/integrations/smime/manage-certificates.rst:52 +msgid "📤 **Certificates and private keys must be uploaded separately.**" msgstr "" -#: ../system/subscription/plan.rst:0 +#: ../system/integrations/smime/manage-certificates.rst:54 msgid "" -"Screenshot showing three available packages for a hosted Zammad\n" -"instance" +"If your certificate and private key are bundled together in the same file or " +"PEM block, import it twice (once using each button)." msgstr "" -#: ../system/subscription/plan.rst:83 -msgid "Summary" +#: ../system/integrations/smime/manage-certificates.rst:57 +msgid "Please note that bulk imports of private keys are not possible." msgstr "" -#: ../system/subscription/plan.rst:41 -msgid "" -"In this section you can adjust the settings of the previous selected plan." -msgstr "" +#: ../system/integrations/smime/manage-certificates.rst:60 +#, fuzzy +msgid "Download Certificate Data" +msgstr "Sertifika Ekle" -#: ../system/subscription/plan.rst:45 +#: ../system/integrations/smime/manage-certificates.rst:62 msgid "" -"Note that upgrading (more agents, higher package) is always possible, " -"however, downgrading will only happen when your billing period renews." +"You can download the earlier provided certificates and private keys at any " +"time from your Zammad instance." msgstr "" -#: ../system/subscription/plan.rst:49 +#: ../system/integrations/smime/manage-certificates.rst:65 msgid "" -"Upgrading resets your billing period and existing credit will be deducted " -"from the new total." +"Please note that passphrase-protected private keys stay protected and when " +"you download them, you have to know the passphrase to use them after " +"downloading." msgstr "" -#: ../system/subscription/plan.rst:58 -msgid "Billing cycle" +#: ../system/integrations/smime/manage-certificates.rst:73 +msgid "Dialogue to download certificates or private keys" msgstr "" -#: ../system/subscription/plan.rst:53 -msgid "" -"You can choose between either monthly or yearly billing. The price per agent " -"will be cheaper if you decide for yearly billing." +#: ../system/integrations/smime/manage-certificates.rst:73 +msgid "Download stored certificates and their keys" msgstr "" -#: ../system/subscription/plan.rst:56 +#: ../system/integrations/smime/manage-certificates.rst:78 msgid "" -"If you're still trying out things and are unsure of the right package for " -"your instance, you may want to choose monthly first and then upgrade to " -"yearly when you're sure." +"The ticket composer will set all outgoing messages to **signed and " +"encrypted** by default (assuming the required certificates exist)." msgstr "" -#: ../system/subscription/plan.rst:66 -msgid "Plan: (Starter|Professional|Plus) - Agents" +#: ../system/integrations/smime/manage-certificates.rst:82 +msgid "These defaults can be modified on a per-group basis:" msgstr "" -#: ../system/subscription/plan.rst:61 -msgid "Choose the number of agents you require for your instance." +#: ../system/integrations/smime/manage-certificates.rst:None +msgid "Zammad allowing to choose the default behavior on per group basis" msgstr "" -#: ../system/subscription/plan.rst:63 +#: ../system/integrations/smime/manage-certificates.rst:89 msgid "" -"Keep in mind that some packages may have agent limits. Depending on the " -"previous chosen package, you won't be able to exceed specific agent numbers. " -"Also note that setting less agents than currently configured is not possible." -msgstr "" - -#: ../system/subscription/plan.rst:69 -msgid "Total" +"Of course, agents can always manually change these settings on each email " +"they send out." msgstr "" -#: ../system/subscription/plan.rst:69 -msgid "This will be the net total you're going to be billed." -msgstr "" +#: ../system/integrations/smime/prerequisites.rst:4 +msgid "A certificate *and* private key for your own organization" +msgstr "Organizasyonunuz için bir sertifika *ve* özel anahtar" -#: ../system/subscription/plan.rst:71 +#: ../system/integrations/smime/prerequisites.rst:6 msgid "" -"By using the *Update subscription* button, the instance package will be " -"adjusted immediately. If you didn't provide a payment method yet, Zammad " -"will request you to provide one at this point." +"(Use this to ✒️ **sign outgoing messages** and 🔓 **decrypt incoming " +"messages**.)" msgstr "" -#: ../system/subscription/plan.rst:77 +#: ../system/integrations/smime/prerequisites.rst:9 msgid "" -"In case you're still within the trial period, this means that the trial will " -"be over immediately!" -msgstr "" - -#: ../system/subscription/plan.rst:80 -msgid "Down- or upgrading during the trial period *is not* possible." -msgstr "" - -#: ../system/subscription/plan.rst:0 -msgid "Screenshot showing payment options and a pricing summary" -msgstr "" - -#: ../system/subscription/plan.rst:99 -msgid "Payment method" -msgstr "" - -#: ../system/subscription/plan.rst:86 -msgid "You can pay via credit card or SEPA mandate." -msgstr "" - -#: ../system/subscription/plan.rst:91 -msgid "Credit card" +"Certificates belonging your contacts, or their issuing certificate authority " +"(CA)" msgstr "" -#: ../system/subscription/plan.rst:89 +#: ../system/integrations/smime/prerequisites.rst:11 msgid "" -"Simply follow the dialogue by clicking *authorize* and confirm -if required " -"by your bank- your consent to Zammad using your card for the payments." +"(Use these to ✅ **verify incoming message signatures** and 🔒 **encrypt " +"outgoing messages**.)" msgstr "" -#: ../system/subscription/plan.rst:95 -msgid "SEPA" -msgstr "" +#: ../system/integrations/smime/prerequisites.rst:14 +#, fuzzy +msgid "🙋 **I'm new to S/MIME. Where can I get a certificate?**" +msgstr "🙋 **S/MIME'da yeniyim. Nereden bir sertifika alabilirim?**" -#: ../system/subscription/plan.rst:94 +#: ../system/integrations/smime/prerequisites.rst:16 msgid "" -"Provide the requested information of the bank account holder and update if " -"you're ready. You'll then receive an email with the SEPA mandate." +"The easiest way to get certificates is to buy an annual subscription through " +"a commercial CA, such as:" msgstr "" -#: ../system/subscription/plan.rst:97 +#: ../system/integrations/smime/prerequisites.rst:19 msgid "" -"Technically there's also the possibility to pay via invoice, however - this " -"method only applies to a fairly low number of instances. Please contact `our " -"sales team `_ for more information." +"`Sectigo (formerly Comodo) `_" msgstr "" -#: ../system/translations.rst:2 -msgid "Translations" -msgstr "Çeviriler" - -#: ../system/translations.rst:4 -msgid "" -"Translations of Zammad are processed centrally in our `Weblate instance " -"`_. This allows non-developers to review " -"and update translation texts of the language they actually speak." -msgstr "" +#: ../system/integrations/smime/prerequisites.rst:20 +msgid "`Secorio `_" +msgstr "`Secorio `_" -#: ../system/translations.rst:9 -msgid "" -"Your language is in an incomplete translation state or has typos? Please " -"consider helping us in sorting this out! All you need is either a GitHub " -"account or to register directly in our instance." +#: ../system/integrations/smime/prerequisites.rst:21 +msgid "`GlobalSign `_" +msgstr "`GlobalSign `_" + +#: ../system/integrations/smime/prerequisites.rst:23 +msgid "(Zammad is not affiliated with these CAs in any way.)" msgstr "" -#: ../system/translations.rst:13 +#: ../system/integrations/smime/prerequisites.rst:25 msgid "" -"Did you know? This is also where the documentation translations are handled. " -"🤓" +"You can also generate your own self-signed certificates, but the process is " +"complicated and usually 🙅 **involves extra work for your contacts**." msgstr "" -#: ../system/translations.rst:15 +#: ../system/integrations/smime/prerequisites.rst:29 msgid "" -"Have a look in our :docs:`contribution section ` in the system documentation to get started!" +"Bear in mind that 🤝 **S/MIME only works if the other party is using it, too." +"**" msgstr "" -#: ../system/translations.rst:20 +#: ../system/integrations/smime/prerequisites.rst:32 #, fuzzy -msgid "Local Translations" -msgstr "Çeviriler" +msgid "Certificate and Private Key Checks on Upload" +msgstr "Organizasyonunuz için bir sertifika *ve* özel anahtar" -#: ../system/translations.rst:22 +#: ../system/integrations/smime/prerequisites.rst:34 msgid "" -"Apart from these system translations, there's still local translations you " -"can manage. This is relevant if you added custom objects that require " -"translations or even custom states and priorities." +"The certificate and public key validation is based on the ``X509v3`` " +"extensions." msgstr "" -#: ../system/translations.rst:None -msgid "Translation management screen within the admin menu" +#: ../system/integrations/smime/prerequisites.rst:49 +msgid "Uploading a *client certificate*?" msgstr "" -#: ../system/translations.rst:31 -#, fuzzy -msgid "Updating Translations" -msgstr "Çeviriler" +#: ../system/integrations/smime/prerequisites.rst:41 +msgid "The following attributes are required then:" +msgstr "" -#: ../system/translations.rst:33 -msgid "" -"Because of how Zammad ships translations, the only way to update the system " -"translations is to update your Zammad installation. The benefit of this is " -"that you no longer need internet access during a Zammad upgrade as the " -"package has everything it requires already." +#: ../system/integrations/smime/prerequisites.rst:39 +msgid "Subject Alternative Name (at least one email address has to be present)" msgstr "" -#: ../system/translations.rst:39 -msgid "Translation of Custom Objects" +#: ../system/integrations/smime/prerequisites.rst:40 +msgid "Key Usage (``Digital Signature`` and/or ``Key Encipherment``)" msgstr "" -#: ../system/translations.rst:41 -msgid "" -"No problem at all! You can customize any translation locally, even if it is " -"not initially provided by the system." +#: ../system/integrations/smime/prerequisites.rst:41 +msgid "Public key algorithm (either ``RSA`` or ``EC``)" msgstr "" -#: ../system/translations.rst:44 +#: ../system/integrations/smime/prerequisites.rst:43 msgid "" -"Translation is supported for a broad number of features, including but not " -"limited to custom:" +"The Extended Key Usage attribute is optional. If the certificate provides " +"the named attribute, than it must contain the value ``E-mail Protection``." msgstr "" -#: ../system/translations.rst:47 -#, fuzzy -msgid "Object Attributes" -msgstr "Bilet Nitelikleri" +#: ../system/integrations/smime/prerequisites.rst:46 +msgid "" +"Please note that any usable email adress has to be prefixed with ``email:`` " +"or ``rfc822:``." +msgstr "" -#: ../system/translations.rst:48 -#, fuzzy -msgid "Ticket Macros" -msgstr "Makrolar Oluşturmak" +#: ../system/integrations/smime/prerequisites.rst:49 +msgid "The named public key algorithms are mandatory for private keys as well." +msgstr "" -#: ../system/translations.rst:49 -#, fuzzy -msgid "Ticket Overviews" -msgstr "Genel Bakış" +#: ../system/integrations/smime/prerequisites.rst:54 +msgid "Uploading a *CA certificate*?" +msgstr "" -#: ../system/translations.rst:50 -#, fuzzy -msgid "Ticket Priorities" -msgstr "Bilet > Öncelik > Ad" +#: ../system/integrations/smime/prerequisites.rst:52 +msgid "" +"In the case of an uploaded CA certificate, providing the value ``CA:TRUE`` " +"in the attribute *Basic Contstraints*, the previously mentioned attributes " +"are not verified." +msgstr "" -#: ../system/translations.rst:51 -#, fuzzy -msgid "Ticket States" -msgstr "Bilet > Durum > Ad" +#: ../system/integrations/smime/prerequisites.rst:56 +msgid "" +"In general, the usage of any expired (``Not After``) or not yet valid (``Not " +"Before``) certificate is denied for outgoing emails." +msgstr "" -#: ../system/translations.rst:54 +#: ../system/integrations/smime/prerequisites.rst:59 #, fuzzy -msgid "Customizing Translations" -msgstr "Çeviriler" +msgid "Example certificate:" +msgstr "Sertifika Ekle" -#: ../system/translations.rst:56 +#: ../system/integrations/smime/prerequisites.rst:85 msgid "" -"Within the translation screen, simply click on the **New Translation** " -"button." +"Please note that Zammad will distrust senders by default. This means that " +"you're always required to provide certificate data, no matter if for signing " +"or encrypting." msgstr "" -#: ../system/translations.rst:None -#, fuzzy -msgid "New translation dialog" -msgstr "Makale > Görünürlük" +#: ../system/integrations/smime/prerequisites.rst:89 +msgid "This is by design and can't be adjusted." +msgstr "" -#: ../system/translations.rst:62 +#: ../system/integrations/smime/troubleshooting.rst:4 msgid "" -"In the dialog you can immediately enter the exact translation source (if you " -"know it) and your custom translation text for it and click **Submit**." +"All of the system's latest S/MIME activity is displayed in the **Recent " +"Logs** section." msgstr "" -#: ../system/translations.rst:65 -msgid "" -"Alternatively, try to search for translation suggestions in the list below. " -"Selecting an item from the list will pre-fill the translation source for you " -"and then you can just enter your custom translation." +#: ../system/integrations/smime/troubleshooting.rst:11 +msgid "Sample entries of in- and outgoing S/MIME related emails." msgstr "" -#: ../system/translations.rst:69 +#: ../system/integrations/smime/troubleshooting.rst:11 msgid "" -"The target language will always default to your current language selection. " -"If you need to translate for a different language, simply change the " -"selection before submitting." +"Logs report the status and details of all mail, both incoming and outgoing, " +"that used signing/verification or encryption/decryption." msgstr "" -#: ../system/translations.rst:73 +#: ../system/integrations/smime/troubleshooting.rst:14 msgid "" -"All your custom translations will show up in the overview table when added. " -"And they will even persist across Zammad updates!" +"This log does **not** include email sent by :doc:`triggers ` or the :doc:`scheduler `. For those, check your " +"``production.log``." msgstr "" -#: ../system/translations.rst:76 -msgid "" -"Make sure to reload your browser if a translated string is not displayed." +#: ../system/integrations/smime/troubleshooting.rst:20 +msgid "Common Issues" msgstr "" -#: ../system/translations.rst:80 -msgid "Reverting to Original Translations" +#: ../system/integrations/smime/troubleshooting.rst:30 +msgid "I received a signed/encrypted email before I set up S/MIME integration" msgstr "" -#: ../system/translations.rst:82 +#: ../system/integrations/smime/troubleshooting.rst:23 msgid "" -"If you want to revert a custom translation to original text, simply use the " -"appropriate action within the row of the overview table." +"No problem. Once S/MIME has been enabled and the appropriate certificates " +"have been added, agents will be prompted to retry verification/decryption on " +"matching emails." msgstr "" -#: ../system/translations.rst:85 -msgid "" -"Depending on the type of the translation source, the action has a slightly " -"different name:" +#: ../system/integrations/smime/troubleshooting.rst:0 +msgid "Screenshot of user prompt to retry decryption" msgstr "" -#: ../system/translations.rst:88 -msgid "**Reset** for customized system translations" +#: ../system/integrations/smime/troubleshooting.rst:38 +msgid "The 🔒 **Encrypt** button is disabled" msgstr "" -#: ../system/translations.rst:89 -msgid "**Remove** for customized local translations" +#: ../system/integrations/smime/troubleshooting.rst:33 +#, fuzzy +msgid "Have you added the recipient's certificate?" +msgstr "Alıcının sertifikasının geçerli olduğundan emin misiniz?" + +#: ../system/integrations/smime/troubleshooting.rst:34 +#, fuzzy +msgid "Are you sure the recipient's certificate is valid?" +msgstr "Alıcının sertifikasının geçerli olduğundan emin misiniz?" + +#: ../system/integrations/smime/troubleshooting.rst:35 +msgid "Have you checked your ``production.log`` for more details?" msgstr "" -#: ../system/translations.rst:91 +#: ../system/integrations/smime/troubleshooting.rst:37 msgid "" -"In both cases, the action will remove the customized translation after a " -"confirmation." +"If encryption doesn't work in the composer, it won't work in :doc:`triggers " +"` or the :doc:`scheduler ` either!" msgstr "" -#: ../system/translations.rst:None -msgid "Screenshot showing the location of the Remove action" +#: ../system/integrations/smime/troubleshooting.rst:42 +msgid "The ✅ **Sign** button is disabled" msgstr "" -#: ../system/translations.rst:99 -#, fuzzy -msgid "Inline Translations" -msgstr "Çeviriler" - -#: ../system/translations.rst:101 +#: ../system/integrations/smime/troubleshooting.rst:41 msgid "" -"If you prefer a more hands-on approach, you can activate the inline or on-" -"screen translation feature by pressing ``ctrl`` + ``alt`` + ``t`` at any " -"time and on any screen." +"Have you added **both the certificate and private key** for your " +"organization?" msgstr "" -#: ../system/translations.rst:105 +#: ../system/integrations/smime/troubleshooting.rst:42 msgid "" -"All customizable translation texts will be highlighted for you on the " -"screen. Just click into the highlighted area and update the text in place." +"Does the email address on the certificate match the email address of the " +"agent/group composing the email?" msgstr "" -#: ../system/translations.rst:None -msgid "Inline translation mode activated for the Overview screen" +#: ../system/integrations/smime/troubleshooting.rst:45 +msgid "Error: “Fingerprint already taken”" +msgstr "Hata: \"Parmak izi zaten alındı\"" + +#: ../system/integrations/smime/troubleshooting.rst:45 +#, fuzzy +msgid "Are you sure you haven't added this certificate already?" +msgstr "Bu sertifikayı zaten eklemediğinizden emin misiniz?" + +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Error: “❌ invalid byte sequence in UTF-8”" msgstr "" -#: ../system/translations.rst:112 -msgid "" -"When finished editing, simply press ``ctrl`` + ``alt`` + ``t`` again to " -"deactivate." +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Please ensure to provide PEM formatted certificate and keys." msgstr "" -#: ../system/translations.rst:117 -msgid "" -"Even though it's available on any screen, the inline translation feature " -"requires admin permissions. It works only for the current language " -"selection. If you need to translate a different language, first change the " -"language in your :user-docs:`profile settings `." +#: ../system/integrations/smime/troubleshooting.rst:49 +msgid "Did you check if the provided file is a valid certificate or key?" msgstr "" -#: ../system/variables.rst:2 -msgid "Variables" -msgstr "Değişkenler" +#: ../system/integrations/zabbix.rst:2 +msgid "Zabbix Integration" +msgstr "Zabbix Entegrasyonu" -#: ../system/variables.rst:4 +#: ../system/integrations/zabbix.rst:5 msgid "" -"Please note that this is just an overview of available variables. It might " -"be incomplete or variables might not be available within some functions. If " -"you're missing variables or are not sure if something is not working as " -"expected, feel free to ask over at the `Community `_." +"This guide describes how to integrate your Zabbix 5.4 installation with " +"Zammad using the Zabbix webhook feature. This guide will provide " +"instructions on setting up a media type, a user and an action in Zabbix." msgstr "" -"Lütfen bunun yalnızca mevcut değişkenlere genel bir bakış olduğunu " -"unutmayın. Eksik olabilir veya bazı işlevlerde değişkenler mevcut " -"olmayabilir. Değişkenleri kaçırıyorsanız veya bir şeyin beklendiği gibi " -"çalışmadığından emin değilseniz, \"Topluluk \" " -"adresinden soru sormaktan çekinmeyin." -#: ../system/variables.rst:10 -#, fuzzy -msgid "" -"Variables can be called by typing ``::`` (just like text modules in the " -"frontend), as long as you're in a supported text field within the backend. " -"Zammad will display all variables being available within this context and " -"replace it to the variable as soon as you selected an entry." +#: ../system/integrations/zabbix.rst:12 +msgid "Zammad with enabled HTTP Token Authentication" msgstr "" -"Değişkenler, Backend içinde desteklenen bir metin alanında olduğunuz sürece " -"``::`` (tıpkı ön uçtaki metin modülleri gibi) yazılarak çağrılabilir. " -"Zammad, bu bağlamda mevcut olan tüm değişkenleri gösterecek ve bir girdi " -"seçtiğiniz anda onu değişkenle değiştirecektir." -#: ../system/variables.rst:15 +#: ../system/integrations/zabbix.rst:13 #, fuzzy +msgid "Zabbix version 5.4 or higher" +msgstr "Zabbix versiyonu 5.0 veya daha yüksek" + +#: ../system/integrations/zabbix.rst:16 +msgid "Setting up a Zammad" +msgstr "" + +#: ../system/integrations/zabbix.rst:18 +msgid "Enable **API Token Access** in Settings > System > API." +msgstr "" + +#: ../system/integrations/zabbix.rst:20 msgid "" -"You have an empty field which you referenced and it appears as ``-``? That's " -"currently working as designed - you might want to ensure that these fields " -"always have a value." +"Create a **new user** for a Zabbix alerter with an **email address** and " +"create a personal user token with **ticket.agent** permissions." msgstr "" -"Referans verdiğiniz boş bir alanınız var ve ``-`` olarak mı görünüyor? Şu " -"anda tasarlandığı gibi çalışıyor - bu alanların her zaman bir değere sahip " -"olduğundan emin olmak isteyebilirsiniz (metin alanlarında `` `` bir " -"değerdir!)." -#: ../system/variables.rst:20 -msgid "Variable Categories" -msgstr "Değişken Kategoriler" +#: ../system/integrations/zabbix.rst:24 +#, fuzzy +msgid "Zabbix Webhook Configuration" +msgstr "Zabbix Webhook yapılandırması" -#: ../system/variables.rst:31 +#: ../system/integrations/zabbix.rst:27 #, fuzzy -msgid "Wait, What About Custom Objects?" -msgstr "Bekle, peki ya özelleştirilmiş nesneler?" +msgid "Create a Global Macro" +msgstr "Bir global makro oluştur" -#: ../system/variables.rst:33 +#: ../system/integrations/zabbix.rst:29 msgid "" -"Good point! Of course, we can't predict what objects you might create, but " -"we can give you a hint on how to put the puzzle together to get your custom " -"values." +"Before setting up the **Webhook**, you need to setup the global macro " +"**{$ZABBIX.URL}**, which must contain the **URL** to the **Zabbix frontend**." msgstr "" -"İyi bir nokta! Elbette, hangi nesneleri yaratabileceğinizi tahmin " -"edemiyoruz, ancak özel değerlerinizi elde etmek için bulmacayı nasıl bir " -"araya getireceğiniz konusunda size bir ipucu verebiliriz." -#: ../system/variables.rst:36 +#: ../system/integrations/zabbix.rst:33 msgid "" -"For this, we'll talk about the inner part of the variable (so everything " -"within ``#{}``), please put the outer part around to have a valid variable. " -"The first part of the variable name consist of the object type. Currently " -"these are:" +"In the **Administration** > **Media types** section, import the `Template`_." msgstr "" -"Bunun için değişkenin iç kısmından bahsedeceğiz (yani ``#{}`` içindeki her " -"şey), lütfen dış kısmı geçerli bir değişkene sahip olacak şekilde " -"yerleştirin. Değişken adının ilk kısmı nesne türünden oluşur. Şu anda bunlar:" -#: ../system/variables.rst:41 -msgid "Ticket (``ticket``)" -msgstr "Bilet (``bilet``)" +#: ../system/integrations/zabbix.rst:38 +msgid "Open the added **Zammad** media type and set:" +msgstr "" -#: ../system/variables.rst:42 -msgid "User (``user``)" -msgstr "Kullanıcı (``kullanıcı``)" +#: ../system/integrations/zabbix.rst:40 +msgid "**zammad\\_access\\_token** to the your **Personal User Token**" +msgstr "" -#: ../system/variables.rst:43 -msgid "Organization (``organization``)" -msgstr "Organizasyon (``organizasyon``)" +#: ../system/integrations/zabbix.rst:41 +msgid "" +"**zammad\\_url** to the **frontend URL** of your **Zammad** installation" +msgstr "" -#: ../system/variables.rst:44 -msgid "Group (``group``)" -msgstr "Grup (``grup``)" +#: ../system/integrations/zabbix.rst:43 +msgid "**zammad\\_customer** to your **Zammad user email**." +msgstr "" -#: ../system/variables.rst:46 +#: ../system/integrations/zabbix.rst:44 msgid "" -"The second part is the name of the object. This is the name you define " -"during object creation and can be found within the object menu at any time. " -"The first and second part of a variable is divided by a point, e.g.: " -"``ticket.number`` which will in total be ``#{ticket.number}``." +"**zammad\\_enable\\_tags** to **true** or **false** to enable or disable " +"trigger tags. **Important**: if you enable tag support, each tag is set with " +"a separate request." msgstr "" -"İkinci kısım nesnenin adıdır. Bu, nesne oluşturma sırasında tanımladığınız " -"addır ve herhangi bir zamanda nesne menüsünde bulunabilir. Bir değişkenin " -"birinci ve ikinci kısmı bir noktayla bölünür, örneğin: \"ticket.number\", " -"toplamda \"#{ticket.number}\" olur." -#: ../system/variables.rst:51 +#: ../system/integrations/zabbix.rst:48 msgid "" -"Now, in some situations it's possible that you'll need to use a third part. " -"The best example for such a situation would be a ``select`` or ``tree-" -"select`` field which will by default return the key value, not it's display " -"name. For this, just extend your variable with ``.value``. This will result " -"in ``#{ticket.select.value}``." +"If you want to prioritize issues according to **severity** values in Zabbix, " +"you can define mapping parameters:" msgstr "" -"Şimdi, bazı durumlarda üçüncü bir parça kullanmanız gerekebilir. Böyle bir " -"duruma en iyi örnek, varsayılan olarak görünen adını değil, anahtar değerini " -"döndürecek olan bir \"seç\" veya \"ağaç seçimi\" alanıdır. Bunun için " -"değişkeninizi ``.value`` ile genişletin. Bu, ``#{ticket.select.value}`` ile " -"sonuçlanacaktır." -#: ../system/variables.rst:60 -#, fuzzy -msgid "Using Translated Variables" -msgstr "Çeviriler" +#: ../system/integrations/zabbix.rst:51 +msgid "**severity\\_**: Zammad priority ID" +msgstr "" -#: ../system/variables.rst:62 -msgid "" -"If you want to use a translated variable in triggers or schedulers, you can " -"extend the placeholder like this: ``#{t(ticket.state.name)}``. The ``t`` " -"tells Zammad to search for fitting translated strings. The used output " -"language is based on the system language of Zammad which you can set in the " -"admin panel under :doc:`/settings/branding` or based on the selected locale " -"in the trigger/scheduler edit dialog." +#: ../system/integrations/zabbix.rst:53 +msgid "Click the **Update** button to save the **Webhook** settings." msgstr "" -#: ../system/variables.rst:69 +#: ../system/integrations/zabbix.rst:55 msgid "" -"A possible use-case: you want to send your customers updates on tickets via " -"trigger or scheduler which should include the state of the ticket. Using the " -"default ``#{ticket.state.name}`` (without the translation flag ``t()``) " -"would lead to the output of the original (english) name of the state." +"To receive notifications in **Zammad**, you need to create a **Zabbix user** " +"and add **Media** with the **Zammad** type." msgstr "" -#: ../system/variables.rst:75 -msgid "Date and Time Formatting" +#: ../system/integrations/zabbix.rst:58 +msgid "" +"For **Send to**: enter any text, as this value is not used, but is required." msgstr "" -#: ../system/variables.rst:77 +#: ../system/integrations/zabbix.rst:61 msgid "" -"The system (trigger/scheduler selected) locale and timezone predefines a " -"default format of date and timestamp. This format is customizable by using " -"the ``dt()`` method." +"For more information, use the `Zabbix documentation `_." msgstr "" -#: ../system/variables.rst:79 -msgid "The method arguments are as follows:" +#: ../system/maintenance.rst:2 +msgid "Maintenance" +msgstr "Bakım" + +#: ../system/maintenance.rst:4 +msgid "" +"Zammad comes with a maintenance mode that you can use for e.g. updating the " +"instance or changing settings while restricting availability and functions." msgstr "" -#: ../system/variables.rst:81 -msgid "The date or timestamp variable you want to format." +#: ../system/maintenance.rst:13 +msgid "Mode" +msgstr "Mod" + +#: ../system/maintenance.rst:8 +msgid "The mode setting allows you to enable or disable the maintenance mode." msgstr "" -#: ../system/variables.rst:82 -#, fuzzy -msgid "The output format string." -msgstr "``Test`` biçimlendirme olmadan" +#: ../system/maintenance.rst:10 +msgid "Defaults to *off*." +msgstr "" -#: ../system/variables.rst:83 -msgid "The timezone to apply (optional)." +#: ../system/maintenance.rst:12 +msgid "" +"The maintenance mode will restrict access to administrative roles only. This " +"means agents and customers are logged off." msgstr "" -#: ../system/variables.rst:86 +#: ../system/maintenance.rst:23 +msgid "@Login" +msgstr "@Giriş" + +#: ../system/maintenance.rst:16 msgid "" -"``#{dt(ticket.updated_at, \"%A %Y-%m-%d %H:%M in the office\", \"Europe/" -"Berlin\")}``" +"This setting allows you to provide a login message within a green banner " +"above the login screen. Click into the green banner in the settings page to " +"adjust your message. To activate the message, activate the *@Login* setting." msgstr "" -#: ../system/variables.rst:87 -msgid "Monday, 2024-03-18 15:31 in the office" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing the default login message within the\n" +"settings page" msgstr "" -#: ../system/variables.rst:89 +#: ../system/maintenance.rst:26 msgid "" -"If you want to use our example, make sure to paste the string above without " -"formatting (``CTRL+Shift+v``), otherwise it won't work." +"Send an informative message to **all active sessions**. This comes handy to " +"inform your agents e.g. about mayor outages or to force reloads after " +"configuration changes." msgstr "" -#: ../system/variables.rst:93 -msgid "The following table lists available format directives:" +#: ../system/maintenance.rst:31 +msgid "This is the messages title (slightly bigger than the normal message)." msgstr "" -#: ../system/variables.rst:99 -#, fuzzy -msgid "Parameter" -msgstr "Checkmk Parametreleri" +#: ../system/maintenance.rst:34 +msgid "The text you want to provide to your logged in sessions." +msgstr "" -#: ../system/variables.rst:102 -msgid "``%Y``" +#: ../system/maintenance.rst:39 +msgid "Reload application" msgstr "" -#: ../system/variables.rst:103 -msgid "Year with 4 digits" +#: ../system/maintenance.rst:37 +msgid "" +"Selecting this option will change the message acceptance button from *Close* " +"(with nothing happening) to *Continue session*, which forces the application " +"to reload." msgstr "" -#: ../system/variables.rst:104 -msgid "Use ``%y`` for year with 2 digits" +#: ../system/maintenance.rst:43 +msgid "" +"If you have customers that are logged in to Zammad, they'll also be notified " +"if they're active in that moment." msgstr "" -#: ../system/variables.rst:105 -msgid "``%m``" +#: ../system/maintenance.rst:48 +msgid "Example without reload application" msgstr "" -#: ../system/variables.rst:106 -msgid "Month of year (as number with zero-padding)" +#: ../system/maintenance.rst:52 +msgid "" +"Message setting within Zammad's admin settings without ticket reload " +"application setting." msgstr "" -#: ../system/variables.rst:107 -msgid "Use ``%-m`` for month without zero-padding" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing the send message settings without ticket\n" +"reload application set" msgstr "" -#: ../system/variables.rst:108 -msgid "``%d``" +#: ../system/maintenance.rst:61 ../system/maintenance.rst:85 +msgid "" +"The modal all other active sessions will see upon pressing *Send to clients*." msgstr "" -#: ../system/variables.rst:109 -msgid "Day of month (as number with zero-padding)" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing modal caused by maintenance's message\n" +"without reload application ticket" msgstr "" -#: ../system/variables.rst:110 -msgid "Use ``%e`` for day without zero-padding" +#: ../system/maintenance.rst:72 +msgid "Example with reload application" msgstr "" -#: ../system/variables.rst:111 -msgid "``%H``" +#: ../system/maintenance.rst:76 +msgid "" +"Message setting within Zammad's admin settings with ticket reload " +"application setting." msgstr "" -#: ../system/variables.rst:112 -msgid "Hour of day in 24h notation with zero-padding" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing the send message settings with ticket\n" +"reload application set" msgstr "" -#: ../system/variables.rst:113 -msgid "Use ``%k`` for hour without zero-padding" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing modal caused by maintenance's message\n" +"with reload application ticket" msgstr "" -#: ../system/variables.rst:114 -msgid "``%I``" -msgstr "" +#: ../system/monitoring.rst:2 +msgid "Monitoring" +msgstr "İzleme" -#: ../system/variables.rst:115 -msgid "Hour of day in 12h notation with zero-padding" +#: ../system/monitoring.rst:4 +#, fuzzy +msgid "" +"This function is only available in self hosted instances. If you use Zammad " +"in our cloud, we are monitoring the system on our own and take steps to fix " +"potential problems directly." msgstr "" +"**Lütfen dikkat:** Barındırılan örnekleri izlediğimiz ve sorunları " +"düzelttiğimiz için bu yalnızca kendi kendine barındırılan örneklerde " +"kullanılabilir." -#: ../system/variables.rst:116 +#: ../system/monitoring.rst:11 +#, fuzzy msgid "" -"Use ``%l`` for hour without zero-padding and ``%p`` / ``%P`` for meridian " -"indicator" +"On the monitoring page, you can see the current health state of Zammad under " +"\"*Current Status*\" at the bottom. This can be useful if you want to have a " +"look if everything is up and running. As an example, you could have a look " +"in the monitoring when you assume that some emails aren't processed from " +"Zammad." msgstr "" +"İzleme sayfasında, Zammad'ın mevcut sağlık durumunu görebilirsiniz. Bu, " +"örneğin artık e-posta almadığınızı düşünüyorsanız, Sunucunuzda oturum " +"açmadan önce buraya bir göz atabilirsiniz." -#: ../system/variables.rst:117 -msgid "``%M``" +#: ../system/monitoring.rst:17 +msgid "**Can't receive an email and the monitoring response is \"healthy\"?**" msgstr "" -#: ../system/variables.rst:118 -msgid "Minute of hour" +#: ../system/monitoring.rst:19 +msgid "" +"Zammad will just inform you about unprocessable emails. This is not the case " +"for oversized emails. You can adjust the maximum email size in :doc:`../" +"channels/email/settings`." msgstr "" -#: ../system/variables.rst:120 -msgid "``%S``" -msgstr "" +#: ../system/monitoring.rst:24 +#, fuzzy +msgid "Monitoring API" +msgstr "İzleme" -#: ../system/variables.rst:121 -msgid "Second of Minute" +#: ../system/monitoring.rst:26 +msgid "" +"Beside the indication in the monitoring page, you can also use an external " +"monitoring tool to monitor Zammad's health. To request the health of Zammad, " +"you need to provide the API key (token) to the external monitoring tool. You " +"can copy the token from the \"*Current Token*\" field as well as the whole " +"API endpoint of your system (\"*Health Check*\" field), in which the API " +"token is already included." msgstr "" -#: ../system/variables.rst:123 -msgid "``%A``" +#: ../system/monitoring.rst:37 +msgid "Screenshot showing Current Token and Health Check" msgstr "" -#: ../system/variables.rst:124 -msgid "Weekday name" +#: ../system/monitoring.rst:37 +msgid "Screenshot showing Token and Health Check" msgstr "" -#: ../system/variables.rst:125 -msgid "Use ``%a`` for abbreviated name or ``%^A`` for uppercase name" +#: ../system/monitoring.rst:39 +msgid "" +"In addition to that, you can reset the auto-generated token to make sure " +"that already configured monitoring systems won't work anymore. So, please " +"use this \"*Reset*\" button only if you know what you do!" msgstr "" -#: ../system/variables.rst:126 -msgid "``%B``" -msgstr "" +#: ../system/monitoring.rst:44 +#, fuzzy +msgid "Example Output" +msgstr "Örnek" -#: ../system/variables.rst:127 -msgid "Month name" +#: ../system/monitoring.rst:0 +msgid "No issues found" msgstr "" -#: ../system/variables.rst:128 -msgid "Use ``%b`` for abbreviated name" +#: ../system/monitoring.rst:48 ../system/monitoring.rst:60 +msgid "**Indicator in Zammad**:" msgstr "" -#: ../system/variables.rst:129 -msgid "``%U``" +#: ../system/monitoring.rst:0 +msgid "Screenshot showing monitoring with no issues" msgstr "" -#: ../system/variables.rst:130 -msgid "Week number of current year" +#: ../system/monitoring.rst:54 ../system/monitoring.rst:66 +msgid "**API response**::" msgstr "" -#: ../system/variables.rst:131 -msgid "Use ``%W`` for a different calculation method" +#: ../system/monitoring.rst:0 +msgid "Issues were found" msgstr "" -#: ../system/variables.rst:134 -msgid "" -"We support the known format directives for the Ruby built-in method " -"``strftime`` of the ``DateTime`` class. For more information, see `here " -"`_." +#: ../system/monitoring.rst:0 +msgid "Screenshot showing monitoring with issues" msgstr "" -#: ../system/variables/article.rst:2 -msgid "Articles" -msgstr "Makaleler" +#: ../system/objects.rst:2 +msgid "Objects" +msgstr "Nesneler" -#: ../system/variables/article.rst:4 ../system/variables/config.rst:4 -#: ../system/variables/current-user.rst:4 ../system/variables/ticket.rst:4 +#: ../system/objects.rst:4 msgid "" -"If you're missing variables or are not sure if something is not working as " -"expected, feel free to ask over at the `Community `_." +"In Zammad you can add your own fields to tickets, users, organizations and " +"even groups (these are called \"objects\"). This can be useful if you need " +"to add further information to a ticket or any other object in Zammad and the " +"information doesn't fit in any existing field." msgstr "" -"Değişkenleri kaçırıyorsanız veya bir şeyin beklendiği gibi çalışmadığından " -"emin değilseniz, `Toplulukta `_ soru sormaktan çekinmeyin." -#: ../system/variables/article.rst:6 +#: ../system/objects.rst:11 msgid "" -"Below you can find all available ticket article-based variables within " -"Zammad. These can be called via Triggers for example. If you're unsure if " -"Zammad does support variables at the point you're at, you can try to type " -"``::`` to check." +"Try to avoid deleting attributes (and disable them instead) as Zammad might " +"run into unexpected conditions if they are referenced somewhere." msgstr "" -"Aşağıda, Zammad içindeki tüm bilet tabanlı değişkenleri bulabilirsiniz. " -"Bunlar örneğin Tetikleyiciler aracılığıyla çağrılabilir. Bulunduğunuz " -"noktada Zammad'ın değişkenleri destekleyip desteklemediğinden emin " -"değilseniz, kontrol etmek için ``::`` yazmayı deneyebilirsiniz." -#: ../system/variables/article.rst:9 ../system/variables/config.rst:9 -#: ../system/variables/ticket.rst:9 +#: ../system/objects.rst:16 msgid "" -"The below list gives you an example what kind of data you can expect, it's " -"not intended to explain the data itself." +"Here's an overview of object attributes. On the upper right you can add new " +"attributes. By default, there will be no custom fields - standard attributes " +"will be grayed out, you can't delete or change those. You can edit custom " +"attributes (they are displayed in black font and have a trash bin on the " +"right side) just by clicking on them." msgstr "" -"Aşağıdaki liste size ne tür veriler bekleyebileceğinize dair bir örnek " -"verir, verilerin kendisini açıklama amacı taşımaz." - -#: ../system/variables/article.rst:11 -msgid "Article Variables" -msgstr "Makale Değişkenleri" - -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "name" -msgstr "ad" - -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "variable" -msgstr "değişken" - -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "example" -msgstr "örnek" - -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Web" -msgstr "Makale > Güncelleyen > Web" - -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.web}``" -msgstr "``#{article.updated_by.web}``" - -#: ../system/variables/article.rst:1 -msgid "``https://zammad.com`` or empty if not set in user object" -msgstr "``https://zammad.com``` veya kullanıcı nesnesinde ayarlanmadıysa boş" - -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > VIP" -msgstr "Makale > Güncelleyen > VIP" - -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.vip}``" -msgstr "``#{article.updated_by.vip}``" - -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -msgid "``true`` or ``false``" -msgstr "``doğru`` veya ``yanlış``" - -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Phone" -msgstr "Makale > Güncelleyen > Telefon" - -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.phone}``" -msgstr "``#{article.updated_by.phone}``" - -#: ../system/variables/article.rst:1 -msgid "``+4930123456789`` or empty if not set in user object" -msgstr "``+4930123456789`` veya kullanıcı nesnesinde ayarlanmadıysa boş" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Note" -msgstr "Makale > Güncelleyen > Not" - -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.note}``" -msgstr "``#{article.updated_by.note}``" - -#: ../system/variables/article.rst:1 -msgid "``Some note about user`` or empty if not set in user object" +#: ../system/objects.rst:24 +msgid "" +"Attributes you add to Zammad, no matter if they have default values or not, " +"will not update existing information. This means a new ticket field " +"technically will be empty unless you populate it." msgstr "" -"``Kullanıcı hakkında örnek not`` veya kullanıcı nesnesinde ayarlanmadıysa boş" - -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Mobile" -msgstr "Makale > Güncelleyen > Mobil" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.mobile}``" -msgstr "``#{article.updated_by.mobile}``" - -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Login" -msgstr "Makale > Güncelleyen > Giriş" - -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.login}``" -msgstr "``#{article.updated_by.login}``" - -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -#: ../system/variables/ticket.rst:1 -msgid "``jdoe``" -msgstr "``jdoe``" - -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Lastname" -msgstr "Makale > Güncelleyen > Soyad" - -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.lastname}``" -msgstr "``#{article.updated_by.lastname}``" - -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -#: ../system/variables/ticket.rst:1 -msgid "``Doe`` or empty if not set" -msgstr "``Doe`` veya ayarlanmadıysa boş" - -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Firstname" -msgstr "Makale > Güncelleyen > Ad" - -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.firstname}``" -msgstr "``#{article.updated_by.firstname}``" - -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "``Joe`` or empty if not set" -msgstr "``Joe`` veya ayarlanmadıysa boş" - -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Fax" -msgstr "Makale > Güncelleyen > Faks" - -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.fax}``" -msgstr "``#{article.updated_by.fax}``" - -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Email" -msgstr "Makale > Güncelleyen > E-posta" - -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.email}``" -msgstr "``#{article.updated_by.email}``" - -#: ../system/variables/article.rst:1 -msgid "``jdoe@example.com``" -msgstr "``jdoe@example.com``" - -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Department" -msgstr "Makale > Güncelleyen > Bölüm" - -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.department}``" -msgstr "``#{article.updated_by.department}``" - -#: ../system/variables/article.rst:1 -msgid "``Sales`` or empty if not set in user object" -msgstr "``Satışlar`` veya kullanıcı nesnesinde ayarlanmadıysa boş" - -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Address" -msgstr "Makale > Güncelleyen > Adres" - -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.address}``" -msgstr "``#{article.updated_by.address}``" - -#: ../system/variables/article.rst:1 -msgid "``Some street 1, 12345 Berlin`` or empty if not set in user object" +#: ../system/objects.rst:28 +msgid "" +"Especially in ticket scope this also means that newly added attributes will " +"be indicated as \"changed\" to agents that view the ticket. This may " +"interfere with Zammad's tabs behavior." msgstr "" -"``Örnek cadde 1, 12345 Berlin`` veya kullanıcı nesnesinde ayarlanmadıysa boş" - -#: ../system/variables/article.rst:1 -msgid "Article > Updated" -msgstr "Makale > Güncellenen" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_at}``" -msgstr "``#{article.updated_at}``" +#: ../system/objects.rst:40 +#, fuzzy +msgid "Ordering Attributes" +msgstr "Bilet nitelikleri" -#: ../system/variables/article.rst:1 -msgid "``2019-10-08 15:24:47 UTC``" -msgstr "``2019-10-08 15:24:47 UTC``" +#: ../system/objects.rst:42 +msgid "" +"Since Zammad introduced :doc:`/system/core-workflows` the need to have a " +"custom positioning for attributes has become more important than ever." +msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Type > Name" -msgstr "Makale > Tür > Ad" +#: ../system/objects.rst:45 +msgid "" +"To adjust the position of such an attribute, simply click on the attribute " +"entry in question, scroll down and adjust the position number. Please note " +"that you cannot change the positioning of default attributes." +msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.type.name}``" -msgstr "``#{article.type.name}``" +#: ../system/objects.rst:49 +msgid "" +"In case two attributes have the same position value, Zammad will sort " +"alphabetically by name automatically." +msgstr "" -#: ../system/variables/article.rst:1 +#: ../system/objects.rst:None msgid "" -"``email`` (`list of article types `_)" +"Screenshot showing custom attribute entries ordered in between default ones" msgstr "" -"``e-posta`` (`makale türlerinin listesi `_)" -#: ../system/variables/article.rst:1 -msgid "Article > To" -msgstr "Makale > Kime" +#: ../system/objects.rst:56 +msgid "Updating Database After Adding or Editing Attributes" +msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.to}``" -msgstr "``#{article.to}``" +#: ../system/objects.rst:58 +msgid "" +"When adding or changing attributes, Zammad will not apply the changes " +"instantly, but instead shows you the changed attributes first. If you're " +"ready to go, just click on \"Update database\" to apply the changes to " +"Zammad. If you made a mistake or just want to discard your changes, click " +"\"Discard changes\"." +msgstr "" -#: ../system/variables/article.rst:1 -msgid "``helpdesk@example.com``" -msgstr "``helpdesk@example.com``" +#: ../system/objects.rst:64 +msgid "" +"After applying the changes with \"Update Database\", a restart of Zammad is " +"**mandatory**. If you don't perform it, you may experience unexpected " +"behavior or even errors. You may want to do this kind of configuration " +"during maintenance windows." +msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > TicketID" -msgstr "Makale > BiletID" +#: ../system/objects.rst:72 +msgid "" +"Changes on objects require you to update the database to apply these changes." +msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.ticket_id}``" -msgstr "``#{article.ticket_id}``" +#: ../system/objects.rst:75 +msgid "**🤓 Service restarts can be automated**" +msgstr "" -#: ../system/variables/article.rst:1 -msgid "``1`` (not ticket number)" -msgstr "``1`` (bilet numarası değil)" +#: ../system/objects.rst:0 +msgid "Hosted environments automatically restart for you." +msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Subject" -msgstr "Makale > Konu" +#: ../system/objects.rst:0 +msgid "" +"If you're using a self-hosted installation you can use :docs:`environment " +"variables `" +msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.subject}``" -msgstr "``#{article.subject}``" +#: ../system/objects.rst:82 +#, fuzzy +msgid "System Attributes" +msgstr "Bilet nitelikleri" -#: ../system/variables/article.rst:1 -msgid "``My amazing subject``" -msgstr "``Benim harika konum``" +#: ../system/objects.rst:84 +msgid "" +"Zammad comes with pre-configured attributes. Some of them can't be edited " +"via UI (or at all). This is required for proper operation of Zammad and not " +"a bug." +msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Sender > Name" -msgstr "Makale > Gönderen > Ad" +#: ../system/objects.rst:90 +#, fuzzy +msgid "Ticket State" +msgstr "Bilet > Durum > Ad" -#: ../system/variables/article.rst:1 -msgid "``#{article.sender.name}``" -msgstr "``#{article.sender.name}``" +#: ../system/objects.rst:92 +msgid "" +"If the pre-configured states aren't enough for you or you want to change " +"them, you can do so by clicking on the cogwheel icon in the state row in the " +"ticket tab. But you should be careful when changing pre-configured states. " +"This can lead to unwanted behavior in some cases." +msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Customer``, ``Agent`` or ``System``" -msgstr "``Müşteri``, ``Aracı`` veya ``Sistem``" +#: ../system/objects.rst:None +msgid "Screenshot showing highlighted ticket state attribute" +msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Visibility" -msgstr "Makale > Görünürlük" +#: ../system/objects.rst:122 +#, fuzzy +msgid "Handling of states" +msgstr "Makro Yönetimi" -#: ../system/variables/article.rst:1 -msgid "``#{article.internal}``" -msgstr "``#{article.internal}``" +#: ../system/objects.rst:102 +msgid "" +"In the state configuration screen, you can add new states, disable states or " +"change states." +msgstr "" -#: ../system/variables/article.rst:1 -msgid "``false`` or ``true`` (false if not internal)" -msgstr "``yanlış`` veya ``doğru`` (dahili değilse yanlış)" +#: ../system/objects.rst:0 +msgid "Screenshot showing table of default ticket states" +msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > From" -msgstr "Makale > Kimden" +#: ../system/objects.rst:110 +msgid "" +"To add a new state, click on the \"New Ticket State\" button in the top " +"right corner. To change an existing state, simply click on the affected " +"state. This opens an edit dialog." +msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.from}``" -msgstr "``#{article.from}``" +#: ../system/objects.rst:114 +msgid "" +"You can also clone a state or set them to \"Default for new tickets\" or " +"\"Default for follow-ups\" by clicking on the ⁝ action button and select the " +"desired function." +msgstr "" -#: ../system/variables/article.rst:1 +#: ../system/objects.rst:118 msgid "" -"``Joe Doe `` may differ, depends on ``FROM`` of send mail" +"*Default for new tickets* means that this state is used for every newly " +"created ticket." msgstr "" -"``Joe Doe`` farklılık gösterebilir, postanın ``KİMDEN``olduğuna bağlıdır" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Web" -msgstr "Makale > Oluşturan > Web" +#: ../system/objects.rst:121 +msgid "" +"*Default for follow-ups* means that this state is used if the ticket is re-" +"opened after it was closed." +msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.web}``" -msgstr "``#{article.created_by.web}``" +#: ../system/objects.rst:171 +#, fuzzy +msgid "Ticket state in detail" +msgstr "Bilet > Durum > Ad" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > VIP" -msgstr "Makale > Oluşturan > VIP" +#: ../system/objects.rst:125 +msgid "" +"Below you can find a description for each field and option. Please head over " +"to the :ref:`example ` to see the edit dialog." +msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.vip}``" -msgstr "``#{article.created_by.vip}``" +#: ../system/objects.rst:129 +msgid "" +"This is the name of the state and what you and your agents are seeing when " +"choosing a state somewhere (e.g. in tickets, trigger configuration)." +msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Phone" -msgstr "Makale > Oluşturan > Telefon" +#: ../system/objects.rst:137 +msgid "" +"There are different state types you can choose from. By default, Zammad " +"comes with one state per state type." +msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.phone}``" -msgstr "``#{article.created_by.phone}``" +#: ../system/objects.rst:140 +msgid "" +"**new**: for states for tickets that are new and it hasn't been worked on " +"them" +msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Note" -msgstr "Makale > Oluşturan > Not" +#: ../system/objects.rst:142 +msgid "" +"**open**: for states for tickets that are in progress and agents are working " +"on them" +msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.note}``" -msgstr "``#{article.created_by.note}``" +#: ../system/objects.rst:144 +msgid "**merged**: for states for tickets that are merged with other tickets" +msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Mobile" -msgstr "Makale > Oluşturan > Mobil" +#: ../system/objects.rst:145 +msgid "" +"**pending reminder**: for states for tickets that are in progress and you " +"want to set a reminder. (default example: *pending reminder*)" +msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.mobile}``" -msgstr "``#{article.created_by.mobile}``" +#: ../system/objects.rst:147 +msgid "" +"**pending action**: for states for tickets that are waiting for a specified " +"time and then change their state (default example: *pending close*)" +msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Login" -msgstr "Makale > Oluşturan > Giriş" +#: ../system/objects.rst:150 +msgid "" +"**closed**: for states for tickets that are finished and do not need to be " +"processed further" +msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.login}``" -msgstr "``#{article.created_by.login}``" +#: ../system/objects.rst:153 +msgid "" +"⚠️ Choosing the correct state type is important! If you are in doubt, have a " +"look on the default states and their types!" +msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Lastname" -msgstr "Makale > Oluşturan > Soyadı" +#: ../system/objects.rst:158 +msgid "Ignore escalation" +msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.lastname}``" -msgstr "``#{article.created_by.lastname}``" +#: ../system/objects.rst:157 +msgid "" +"Here you can define whether tickets of this state will count to escalation " +"time or not." +msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Firstname" -msgstr "Makale > Oluşturan > Ad" +#: ../system/objects.rst:161 +msgid "" +"You can create a note for the state to inform other admins about the state. " +"This has no effect on tickets." +msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.firstname}``" -msgstr "``#{article.created_by.firstname}``" +#: ../system/objects.rst:165 +#, fuzzy +msgid "Set the state to *active* or *inactive*." +msgstr "aktifse veya değilse" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Fax" -msgstr "Makale > Oluşturan > Faks" +#: ../system/objects.rst:167 +msgid "" +"it is technically possible to set all states to inactive. To keep Zammad " +"working in such a case, the inactive flag of one of the states is ignored." +msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.fax}``" -msgstr "``#{article.created_by.fax}``" +#: ../system/objects.rst:194 +#, fuzzy +msgid "Ticket state example" +msgstr "Bilet > Durum > Ad" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Email" -msgstr "Makale > Oluşturan > E-posta" +#: ../system/objects.rst:174 +msgid "" +"Let's assume we want to create a new state which indicates that the ticket " +"has to wait for a response of a third party (e.g. service contractor or " +"manufacturer) and we want to to be able to set a reminder." +msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.email}``" -msgstr "``#{article.created_by.email}``" +#: ../system/objects.rst:178 +msgid "" +"First we give the new state a proper name. In this example we call it " +"\"waiting for manufacturer\"." +msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Department" -msgstr "Makale > Oluşturan > Bölüm" +#: ../system/objects.rst:181 +msgid "" +"As state type we choose \"pending reminder\". This indicates that the ticket " +"is still open and we can set a reminder. This reminder can be useful if our " +"manufacturer sometimes isn't responding or we want to remind him to give us " +"an answer." +msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.department}``" -msgstr "``#{article.created_by.department}``" +#: ../system/objects.rst:186 +msgid "" +"We choose \"no\" for \"ignore escalation\" because we want to escalate the " +"tickets even if we are waiting on the manufacturer's feedback." +msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Address" -msgstr "Makale > Oluşturan > Adres" +#: ../system/objects.rst:189 +#, fuzzy +msgid "The **result** in the creation dialog will look like this:" +msgstr "Final sonuçları aşağıdaki gibi görünecek:" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.address}``" -msgstr "``#{article.created_by.address}``" +#: ../system/objects.rst:0 +msgid "Screenshot showing ticket state creation dialog with example" +msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created" -msgstr "Makale > Oluşturulan" +#: ../system/objects.rst:199 +#, fuzzy +msgid "Ticket Priority" +msgstr "Bilet > Öncelik > Ad" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_at}``" -msgstr "``#{article.created_at}``" +#: ../system/objects.rst:201 +msgid "" +"If the pre-configured priorities aren't enough for you or you want to change " +"them, you can do so by clicking on the cogwheel icon in the priority row in " +"the ticket tab:" +msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Cc" -msgstr "Makale > Cc" +#: ../system/objects.rst:None +msgid "Screenshot showing highlighted ticket priority attribute" +msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.cc}``" -msgstr "``#{article.cc}``" +#: ../system/objects.rst:226 +msgid "Handling of priorities" +msgstr "" -#: ../system/variables/article.rst:1 -msgid "``jdoe@example.com, company@example.com``" -msgstr "``jdoe@example.com, company@example.com``" +#: ../system/objects.rst:210 +msgid "" +"In the priority configuration screen, you can add new priorities, disable " +"priorities or change priorities." +msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Text" -msgstr "Makale > Metin" +#: ../system/objects.rst:0 +msgid "Screenshot showing table of default ticket priorities" +msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.body}``" -msgstr "``#{article.body}``" +#: ../system/objects.rst:218 +msgid "" +"To add a new priority, click on the \"New Priority\" button in the top right " +"corner. To change an existing priority, simply click on the affected " +"priority. This opens an edit dialog." +msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Test`` without formatting (plain)" -msgstr "``Test`` biçimlendirme olmadan (düz)" +#: ../system/objects.rst:222 +msgid "" +"You can also clone a priority or set them to \"Default for new tickets\" by " +"clicking on the ⁝ action button and select the desired function." +msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article Text as HTML (not referenced)" -msgstr "HTML olarak Makale Metni (referans değil)" +#: ../system/objects.rst:225 +msgid "" +"*Default for new tickets* means that this priority is used for every newly " +"created ticket." +msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.body_as_html}``" -msgstr "``#{article.body_as_html}``" +#: ../system/objects.rst:248 +msgid "Priorities in detail" +msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Test`` with formatting" -msgstr "``Test`` biçimlendirme olmadan" +#: ../system/objects.rst:229 +msgid "Below you can find a description for each field and option." +msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "Ticket > Article#" -msgstr "Bilet > Makale#" +#: ../system/objects.rst:232 +msgid "" +"This is the name of the priority and what you and your agents are seeing " +"when choosing a priority somewhere (e.g. in tickets, trigger configuration)." +msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "``#{ticket.article_count}``" -msgstr "``#{ticket.article_count}``" +#: ../system/objects.rst:242 +msgid "Highlight color" +msgstr "" -#: ../system/variables/article.rst:1 -msgid "``1`` number of ticket articles" -msgstr "``1`` bilet makalelerinin numarası" +#: ../system/objects.rst:237 +msgid "" +"Switch between *Low priority* (light blue), *High priority* (red) and - " +"(default). This affects the displayed color for ticket titles in overviews." +msgstr "" -#: ../system/variables/config.rst:2 -msgid "Config" -msgstr "Yapılandırma" +#: ../system/objects.rst:241 +msgid "The color options are currently limited to the mentioned options." +msgstr "" -#: ../system/variables/config.rst:6 +#: ../system/objects.rst:245 msgid "" -"Below you'll find config related variables. These hold useful configuration " -"information that you can use within e.g. triggers to show necessary " -"information to your customer." +"You can create a note for the priority to inform other admins about the " +"priority. This has no effect on tickets." msgstr "" -"Aşağıda yapılandırmayla ilgili değişkenleri bulacaksınız. Bu değişkenler, " -"yararlı yapılandırma bilgilerini saklar ve müşterinize göstermeniz gereken " -"bilgiler için tetikleyicileri kullanabilirsiniz." -#: ../system/variables/config.rst:11 -msgid "Config Variables" -msgstr "Yapılandırma Değişkenleri" +#: ../system/objects.rst:249 +#, fuzzy +msgid "Set the priority to *active* or *inactive*." +msgstr "aktifse veya değilse" -#: ../system/variables/config.rst:1 -msgid "Config > Fully Qualified Domain Name" -msgstr "Yapılandırma > Tam Tanımlanmış Alan Adı" +#: ../system/objects/external-data-source-example.rst:2 +msgid "External Data Source" +msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.fqdn}``" -msgstr "``#{config.fqdn}``" +#: ../system/objects/external-data-source-example.rst:4 +msgid "" +"We assume you already had a look on :doc:`types` where you can find a " +"description of the individual fields." +msgstr "" -#: ../system/variables/config.rst:1 -msgid "``zammad.example.com``" -msgstr "``zammad.example.com``" +#: ../system/objects/external-data-source-example.rst:7 +msgid "" +"To reproduce this example, choose a category you want to add a custom field, " +"click on *New Attribute* and select *External data source field* under " +"*Format*." +msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Ticket Hook" -msgstr "Yapılandırma > Bilet Kancası" +#: ../system/objects/external-data-source-example.rst:11 +msgid "" +"Our example story is to fetch data from an external product database. We " +"want to add our products to the tickets so that the products can be searched " +"and chosen from a list and also create a link to the product website." +msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.ticket_hook}``" -msgstr "``#{config.ticket_hook}``" +#: ../system/objects/external-data-source-example.rst:16 +#, fuzzy +msgid "Base configuration" +msgstr "Yapılandırma" -#: ../system/variables/config.rst:1 -msgid "``Ticket#``" -msgstr "``Bilet#``" +#: ../system/objects/external-data-source-example.rst:None +msgid "Initial steps to configure external data source object type" +msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > HTTP type" -msgstr "Yapılandırma > HTTP türü" +#: ../system/objects/external-data-source-example.rst:25 +msgid "Name: *product*" +msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.http_type}``" -msgstr "``#{config.http_type}``" +#: ../system/objects/external-data-source-example.rst:26 +msgid "Display: *Product*" +msgstr "" -#: ../system/variables/config.rst:1 -msgid "``https`` or ``http``" -msgstr "``https`` veya ``http``" +#: ../system/objects/external-data-source-example.rst:29 +#, fuzzy +msgid "External data source configuration" +msgstr "Makale > Görünürlük" -#: ../system/variables/config.rst:1 -msgid "Config > SystemID" -msgstr "Yapılandırma > SistemID" +#: ../system/objects/external-data-source-example.rst:31 +msgid "" +"First, enter the search URL making sure it contains ``#{search.term}`` as a " +"parameter:" +msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.system_id}``" -msgstr "``#{config.system_id}``" +#: ../system/objects/external-data-source-example.rst:34 +msgid "**Example:** ``https://dummyjson.com/products/search?q=#{search.term}``" +msgstr "" -#: ../system/variables/config.rst:1 -msgid "``31`` (value between 1 and 99)" -msgstr "``31`` (1 ve 99 arasında değer)" +#: ../system/objects/external-data-source-example.rst:36 +msgid "" +"After that, head down to the preview section and enter a search input for " +"the external data source." +msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Organization" -msgstr "Yapılandırma > Organizasyon" +#: ../system/objects/external-data-source-example.rst:39 +#, fuzzy +msgid "**Example:** ``mac``" +msgstr "Örnek" -#: ../system/variables/config.rst:1 -msgid "``#{config.organization}``" -msgstr "``#{config.organization}``" +#: ../system/objects/external-data-source-example.rst:41 +msgid "Then you can find a preview of the response data below:" +msgstr "" + +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of JSON response based on search term" +msgstr "" -#: ../system/variables/config.rst:1 +#: ../system/objects/external-data-source-example.rst:48 msgid "" -"``Zammad GmbH`` value set in `Branding `_" -msgstr "`Markalama `_da ``Zammad GmbH`` değer ayarı" +"We recommend using the preview to have a look on the structure. There is a " +"top-level element called ``products``. One level below, you can find the " +"attributes ``id`` and ``title``." +msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Product Name" -msgstr "Yapılandırma > Ürün Adı" +#: ../system/objects/external-data-source-example.rst:52 +msgid "**Search result response based on search from example:**" +msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.product_name}``" -msgstr "``#{config.product_name}``" +#: ../system/objects/external-data-source-example.rst:119 +msgid "" +"To tell the remote system that the desired data is located below the " +"``products`` level, you have to put it in the field *Search result list key*." +msgstr "" -#: ../system/variables/config.rst:1 +#: ../system/objects/external-data-source-example.rst:122 msgid "" -"``Helpdesk`` value set in `Branding `_" -msgstr "`Markalama `_da ``Helpdesk`` değer ayarı" +"After inserting ``products`` in the mentioned field, you get an extended " +"preview. You can find an additional box *Search result list* with a JSON " +"structure. This is the same response as before but stripped from the upper " +"``products`` element by the external data source." +msgstr "" -#: ../system/variables/current-user.rst:2 -msgid "Current User" -msgstr "Geçerli Kullanıcı" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of JSON response search result list" +msgstr "" -#: ../system/variables/current-user.rst:6 +#: ../system/objects/external-data-source-example.rst:132 msgid "" -"Current user variables always return values of the current user that caused " -"e.g. a trigger to run." +"Now you need to provide the keys for the search result values and labels. As " +"already mentioned, we are looking for the ``id`` and the ``title`` of our " +"products. If you haven't already, it is now a good time to look at the " +"preview of the *Search result list*." msgstr "" -"Geçerli kullanıcı değişkenleri her zaman neden olan (ör. çalıştırılan bir " -"tetikleyici) geçerli kullanıcının değerlerini döndürür." -#: ../system/variables/current-user.rst:8 -#, fuzzy +#: ../system/objects/external-data-source-example.rst:197 msgid "" -"Due to the above fact, these variables are often not (yet) set or available " -"for usage." +"After locating our two keys, we insert them in *search result value key* " +"(``id``) and in *Search result label key* (``title``)." msgstr "" -"Yukarıdaki gerçek nedeniyle, bu değişkenler genellikle (henüz) " -"ayarlanmamıştır veya kullanım için uygun değildir." -#: ../system/variables/current-user.rst:10 +#: ../system/objects/external-data-source-example.rst:200 msgid "" -"In situations where e.g. schedulers or triggers run, this most likely is " -"nothing you want to use." +"Basically, we configured the external data source already and we can see a " +"table in the preview section:" msgstr "" -"Aşağıdaki durumlarda ör. zamanlayıcılar veya tetikleyiciler çalışır, bu " -"büyük olasılıkla kullanmak istediğiniz bir şey değildir." -#: ../system/variables/current-user.rst:13 -msgid "Current User Variables" -msgstr "Geçerli Kullanıcı Değişkenleri" - -#: ../system/variables/current-user.rst:1 -msgid "Current User > Web" -msgstr "Geçerli Kullanıcı > Web" - -#: ../system/variables/current-user.rst:1 -msgid "``#{user.web}``" -msgstr "``#{user.web}``" - -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``https://zammad.org`` or empty if not set" -msgstr "``https://zammad.org`` veya ayarlanmadıysa boş" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of product table based on search term" +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > VIP" -msgstr "Geçerli Kullanıcı > VIP" +#: ../system/objects/external-data-source-example.rst:208 +msgid "" +"According to our example story, now just the *Link template* is missing." +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.vip}``" -msgstr "``#{user.vip}``" +#: ../system/objects/external-data-source-example.rst:210 +msgid "" +"Please note that this is an optional feature. If you don't want to use such " +"links, of course you don't have to configure it." +msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``false`` or ``true``" -msgstr "``yanlış`` veya ``doğru``" +#: ../system/objects/external-data-source-example.rst:213 +msgid "" +"We can add now an address where additional product information can be found." +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Web" -msgstr "Geçerli Kullanıcı > Güncelleyen > Web" +#: ../system/objects/external-data-source-example.rst:215 +msgid "Example: ``https://your_domain.com/q=#{ticket.product}``" +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.web}``" -msgstr "``#{user.updated_by.web}``" +#: ../system/objects/external-data-source-example.rst:217 +msgid "In the example, the parameter means:" +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > VIP" -msgstr "Geçerli Kullanıcı > Güncelleyen > VIP" +#: ../system/objects/external-data-source-example.rst:219 +msgid "``#{}``: \"Frame\" for the insertion of information" +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.vip}``" -msgstr "``#{user.updated_by.vip}``" +#: ../system/objects/external-data-source-example.rst:220 +msgid "``ticket``: object level, where you create your custom object" +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Phone" -msgstr "Geçerli Kullanıcı > Güncelleyen > Telefon" +#: ../system/objects/external-data-source-example.rst:221 +msgid "``product``: name of the (custom) object" +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.phone}``" -msgstr "``#{user.updated_by.phone}``" +#: ../system/objects/external-data-source-example.rst:223 +msgid "" +"After configuring your *Link template*, there will be another column in the " +"preview. Hovering on the icons in the *Link* column will show you where it " +"forwards you." +msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``004930123456789`` or empty if not set" -msgstr "``004930123456789`` veya ayarlanmadıysa boş" +#: ../system/objects/external-data-source-example.rst:232 +msgid "" +"In our example, one of the links looks like: https://your_domain.com/q=6, " +"where the 6 is the product id." +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Note" -msgstr "Geçerli Kullanıcı > Güncelleyen > Not" +#: ../system/objects/external-data-source-example.rst:235 +msgid "You can find more information regarding the URL in :doc:`types`." +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.note}``" -msgstr "``#{user.updated_by.note}``" +#: ../system/objects/includes/adding-values-hint.include.rst:3 +msgid "" +"Adding values can be tricky for first timers, don't forget to press \"➕ " +"Add\" after typing your values. Otherwise you may loose a value." +msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Some note to this user`` or empty if not set" -msgstr "`Bu kullanıcı için bir not`` veya ayarlanmadıysa boş" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:1 +#: ../system/objects/includes/reposition-values.include.rst:1 +msgid "**↕️ This field type allows the positioning of its values ↔️**" +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Mobile" -msgstr "Geçerli Kullanıcı > Güncelleyen > Mobil" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:3 +msgid "" +"In order to re-arrange the field values, first edit the field. Then you can " +"use ☰ to drag the values in question to the correct position. If you want to " +"change the layer depth, double click on ☰. With it you can cycle through the " +"available layers." +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.mobile}``" -msgstr "``#{user.updated_by.mobile}``" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:8 +msgid "When you're ready, submit your changes to save the object attribute." +msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``0049176123456789`` or empty if not set" -msgstr "``0049176123456789`` veya ayarlanmadıysa boş" +#: :0 ../system/objects/types.rst:0 +msgid "" +"Screencast showing how to re-position values on tree select like\n" +"fields" +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Login" -msgstr "Geçerli Kullanıcı > Güncelleyen > Giriş" +#: ../system/objects/includes/reposition-values.include.rst:3 +msgid "" +"In order to re-arrange the field values, edit the field and scroll below the " +"values. Make sure to tick the option \"Use custom option sort\"." +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.login}``" -msgstr "``#{user.updated_by.login}``" +#: ../system/objects/includes/reposition-values.include.rst:8 +msgid "" +"If you do not tick this field, all manual positioning you did above will be " +"lost upon saving! ☠️" +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Lastname" -msgstr "Geçerli Kullanıcı > Güncelleyen > Soyad" +#: ../system/objects/includes/reposition-values.include.rst:11 +msgid "" +"Now use ☰ to drag the values in question to the correct position. When " +"you're ready, submit your changes to save the object attribute." +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.lastname}``" -msgstr "``#{user.updated_by.lastname}``" +#: :0 ../system/objects/types.rst:0 +msgid "Screencast showing how to re-position values" +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Firstname" -msgstr "Geçerli Kullanıcı > Güncelleyen > Ad" +#: ../system/objects/includes/url-template-hint.include.rst:3 +msgid "" +"This field allows using :ref:`URL fields (Link Templates) `." +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.firstname}``" -msgstr "``#{user.updated_by.firstname}``" +#: ../system/objects/permissions.rst:2 +#, fuzzy +msgid "Attribute Permissions" +msgstr "Bilet Nitelikleri" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``John`` or empty if not set" -msgstr "``John`` veya ayarlanmadıysa boş" +#: ../system/objects/permissions.rst:7 +msgid "" +"In the object attributes configuration you can define if a field is shown " +"and if the input in the field is mandatory, separated by different screens " +"and for different :doc:`roles/permissions `." +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Fax" -msgstr "Geçerli Kullanıcı > Güncelleyen > Faks" +#: ../system/objects/permissions.rst:17 +#, fuzzy +msgid "Screenshot shows object attribute permission table" +msgstr "" +"Yönetici panelinin Makrolar sayfasında makro oluşturabilir veya " +"düzenleyebilirsiniz:" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.fax}``" -msgstr "``#{user.updated_by.fax}``" +#: ../system/objects/permissions.rst:17 +msgid "" +"Some of the possible permissions and screen options for a user object " +"attribute." +msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``004930123464789`` or empty if not set" -msgstr "``004930123464789`` veya ayarlanmadıysa boş" +#: ../system/objects/permissions.rst:19 +msgid "" +"Based on the object context (ticket, agent, organization, user), the " +"selectable roles (to be precise: the required permissions) and screens " +"differ. Be aware that these settings aren't affecting data creation via " +"other channels than the UI." +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Email" -msgstr "Geçerli Kullanıcı > Güncelleyen > E-posta" +#: ../system/objects/permissions.rst:24 +msgid "" +"If you want to have further customization possibilities, you should have a " +"look at the :doc:`core workflows `." +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.email}``" -msgstr "``#{user.updated_by.email}``" +#: ../system/objects/permissions.rst:28 +#, fuzzy +msgid "Screens" +msgstr "İmzalar" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``jdoe@customer.tld``" -msgstr "``jdoe@customer.tld``" +#: ../system/objects/permissions.rst:30 +msgid "" +"In the table below you can find an overview about the different permissions " +"and the available screens Zammad distinguishes between." +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Department" -msgstr "Geçerli Kullanıcı > Güncelleyen > Bölüm" +#: ../system/objects/permissions.rst:37 +#, fuzzy +msgid "Screen" +msgstr "İmzalar" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.department}``" -msgstr "``#{user.updated_by.department}``" +#: ../system/objects/permissions.rst:38 +#, fuzzy +msgid "Available for" +msgstr "değişken" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Sales`` or empty if not set" -msgstr "``Satışlar`` veya ayarlanmadıysa boş" +#: ../system/objects/permissions.rst:40 +msgid "create" +msgstr "" -#: ../system/variables/current-user.rst:1 +#: ../system/objects/permissions.rst:41 ../system/objects/permissions.rst:52 +#: ../system/objects/permissions.rst:59 ../system/objects/permissions.rst:73 #, fuzzy -msgid "Current User > Updated by > Avatar" -msgstr "Geçerli Kullanıcı > Güncelleyen > Faks" +msgid "admin.user" +msgstr "``admin.user``" -#: ../system/variables/current-user.rst:1 +#: ../system/objects/permissions.rst:42 ../system/objects/permissions.rst:53 +#: ../system/objects/permissions.rst:60 #, fuzzy -msgid "``#{user.updated_by.avatar(60,60)}``" -msgstr "``#{user.updated_by.lastname}``" +msgid "admin.organization" +msgstr "``admin.organization``" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "avatar picture with width and height in pixel (e.g. 60,60)" +#: ../system/objects/permissions.rst:43 ../system/objects/permissions.rst:54 +#: ../system/objects/permissions.rst:61 +#, fuzzy +msgid "admin.group" +msgstr "``admin.group``" + +#: ../system/objects/permissions.rst:44 +msgid "Creation dialog for not yet existing data" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Address" -msgstr "Geçerli Kullanıcı > Güncelleyen > Adres" +#: ../system/objects/permissions.rst:45 +#, fuzzy +msgid "create_middle" +msgstr "Oluşturulma" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.address}``" -msgstr "``#{user.updated_by.address}``" +#: ../system/objects/permissions.rst:46 ../system/objects/permissions.rst:50 +#: ../system/objects/permissions.rst:57 ../system/objects/permissions.rst:66 +#: ../system/objects/permissions.rst:70 +#, fuzzy +msgid "ticket.customer" +msgstr "``#{ticket.customer.web}``" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Some street 1, 12345 Berlin`` or empty if not set" -msgstr "`Örnek cadde 1, 12345 Berlin`` veya ayarlanmadıysa boş" +#: ../system/objects/permissions.rst:47 ../system/objects/permissions.rst:51 +#: ../system/objects/permissions.rst:58 ../system/objects/permissions.rst:69 +#, fuzzy +msgid "ticket.agent" +msgstr "``ticket.agent``" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated at" -msgstr "Geçerli Kullanıcı > Güncelleme tarihi" +#: ../system/objects/permissions.rst:48 +msgid "Ticket create dialog (middle section)" +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_at}``" -msgstr "``#{user.updated_at}``" +#: ../system/objects/permissions.rst:49 +msgid "edit" +msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC``" -msgstr "``2019-10-07 16:25:00 UTC``" +#: ../system/objects/permissions.rst:55 +msgid "Editing dialog for already existing data" +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Phone" -msgstr "Geçerli Kullanıcı > Telefon" +#: ../system/objects/permissions.rst:56 +msgid "view" +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.phone}``" -msgstr "``#{user.phone}``" +#: ../system/objects/permissions.rst:62 +msgid "View-only dialog for already existing data" +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Shared organization" -msgstr "Geçerli Kullanıcı > Organizasyon > Paylaşılan organizasyon" +#: ../system/objects/permissions.rst:64 +msgid "(e.g. user or organization from search)" +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.shared}``" -msgstr "``#{user.organization.shared}``" +#: ../system/objects/permissions.rst:65 +msgid "signup" +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Note" -msgstr "Geçerli Kullanıcı > Organizasyon > Not" +#: ../system/objects/permissions.rst:67 +msgid "Sign-up screen for new customers" +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.note}``" -msgstr "``#{user.organization.note}``" +#: ../system/objects/permissions.rst:68 +#, fuzzy +msgid "invite_customer" +msgstr "müşteri" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``A note to the organization of the user`` or empty if not set" -msgstr "`Kullanıcının organizasyonu için bir not`` veya ayarlanmadıysa boş" +#: ../system/objects/permissions.rst:71 +msgid "" +"Customer invitation screen (from :doc:`First Steps ` area)" +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Name" -msgstr "Geçerli Kullanıcı > Organizasyon > Ad" +#: ../system/objects/permissions.rst:72 +msgid "invite_agent" +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.name}``" -msgstr "``#{user.organization.name}``" +#: ../system/objects/permissions.rst:74 +msgid "" +"Agent invitation screen (from :doc:`First Steps ` area)" +msgstr "" -#: ../system/variables/current-user.rst:1 +#: ../system/objects/permissions.rst:78 #, fuzzy -msgid "``Zammad GmbH``" -msgstr "``Zammad``" - -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Domain based assignment" -msgstr "Geçerli Kullanıcı > Organizasyon > Alan adına göre atama" +msgid "Screen Options" +msgstr "Seçenek" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.domain_assignment}``" -msgstr "``#{user.organization.domain_assignment}``" +#: ../system/objects/permissions.rst:80 +msgid "" +"For the different screens you can select \"show\" and \"required\" options." +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Domain" -msgstr "Geçerli Kullanıcı > Organizasyon > Alan adı" +#: ../system/objects/permissions.rst:82 +msgid "**shown:** Show (check) or hide (uncheck) a field." +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.domain}``" -msgstr "``#{user.organization.domain}``" +#: ../system/objects/permissions.rst:83 +msgid "" +"**required:** Set a field to mandatory (check). Forces users (via UI and " +"API) to populate the field." +msgstr "" -#: ../system/variables/current-user.rst:1 +#: ../system/objects/types.rst:7 #, fuzzy -msgid "``zammad.com`` or empty if not set" -msgstr "``https://zammad.com``` veya ayarlanmadıysa boş" +msgid "Example external data source" +msgstr "Makale > Görünürlük" -#: ../system/variables/current-user.rst:1 +#: ../system/objects/types.rst:2 #, fuzzy -msgid "Current User > Organization > VIP" -msgstr "Geçerli Kullanıcı > Organizasyon > Not" +msgid "Attribute types" +msgstr "Bilet Nitelikleri" + +#: ../system/objects/types.rst:4 +msgid "" +"When adding a new object attribute, you can choose between the following " +"attribute types." +msgstr "" + +#: ../system/objects/types.rst:14 +msgid "" +"You cannot change the attribute format / type as soon as it is applied. If " +"you no longer need an object attribute, consider disabling it instead of " +"removing." +msgstr "" -#: ../system/variables/current-user.rst:1 +#: ../system/objects/types.rst:18 #, fuzzy -msgid "``#{user.organization.vip}``" -msgstr "``#{user.organization.domain}``" +msgid "**What about the translation of my attributes?**" +msgstr "Bekle, peki ya özelleştirilmiş nesneler?" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Note" -msgstr "Geçerli Kullanıcı > Not" +#: ../system/objects/types.rst:20 +msgid "" +"For some attribute types you can decide if they should be translatable or " +"not. To be precise, it works only for the selectable fields because the " +"possible choices are known and limited. For the following attribute types, " +"you can set the translatable flag:" +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.note}``" -msgstr "``#{user.note}``" +#: ../system/objects/types.rst:25 +#, fuzzy +msgid "*Boolean field*" +msgstr "Mantıksal" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Mobile" -msgstr "Geçerli Kullanıcı > Mobil" +#: ../system/objects/types.rst:26 +#, fuzzy +msgid "*Single selection field*" +msgstr "Posta Sunucusu Ayarları" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.mobile}``" -msgstr "``#{user.mobile}``" +#: ../system/objects/types.rst:27 +#, fuzzy +msgid "*Multiple selection field*" +msgstr "Posta Sunucusu Ayarları" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Login" -msgstr "Geçerli Kullanıcı > Giriş" +#: ../system/objects/types.rst:28 +#, fuzzy +msgid "*Single tree selection field*" +msgstr "Posta Sunucusu Ayarları" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.login}``" -msgstr "``#{user.login}``" +#: ../system/objects/types.rst:29 +#, fuzzy +msgid "*Multiple tree selection field*" +msgstr "Posta Sunucusu Ayarları" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Lastname" -msgstr "Geçerli Kullanıcı > Soyad" +#: ../system/objects/types.rst:31 +msgid "" +"For these types, you can find an additional field *Translate field contents*:" +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.lastname}``" -msgstr "``#{user.lastname}``" +#: ../system/objects/types.rst:0 +msgid "Screenshot showing translatable attribute types" +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Firstname" -msgstr "Geçerli Kullanıcı > Ad" +#: ../system/objects/types.rst:38 +msgid "Screenshot with example of translatable attribute type" +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.firstname}``" -msgstr "``#{user.firstname}``" +#: ../system/objects/types.rst:45 +#, fuzzy +msgid "Boolean field" +msgstr "Mantıksal" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Fax" -msgstr "Geçerli Kullanıcı > Faks" +#: ../system/objects/types.rst:41 +msgid "" +"Provides a drop-down field with display values for ``true`` and ``false``. " +"Setting a default is mandatory." +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.fax}``" -msgstr "``#{user.fax}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Boolean fields" +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Email" -msgstr "Geçerli Kullanıcı > E-posta" +#: ../system/objects/types.rst:55 +msgid "Date field" +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.email}``" -msgstr "``#{user.email}``" +#: ../system/objects/types.rst:48 +msgid "Provides a date picker field and does not allow default values." +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Department" -msgstr "Geçerli Kullanıcı > Bölüm" +#: ../system/objects/types.rst:52 +msgid "Default time diff (hours)" +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.department}``" -msgstr "``#{user.department}``" +#: ../system/objects/types.rst:51 +msgid "" +"This setting helps the user by highlighting the day from now plus the " +"provided value. It *does not* pre-fill the field." +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Web" -msgstr "Geçerli Kullanıcı > Oluşturan > Web" +#: ../system/objects/types.rst:0 +msgid "Available settings for Date fields" +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.web}``" -msgstr "``#{user.created_by.web}``" +#: ../system/objects/types.rst:73 +msgid "Date & time field" +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > VIP" -msgstr "Geçerli Kullanıcı > Oluşturan > VIP" +#: ../system/objects/types.rst:58 +msgid "Provides a date and time picker – does not allow default values" +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.vip}``" -msgstr "``#{user.created_by.vip}``" +#: ../system/objects/types.rst:62 +msgid "Allow future" +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Phone" -msgstr "Geçerli Kullanıcı > Oluşturan > Telefon" +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the future." +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.phone}``" -msgstr "``#{user.created_by.phone}``" +#: ../system/objects/types.rst:66 +msgid "Allow past" +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Note" -msgstr "Geçerli Kullanıcı > Oluşturan > Not" +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the past." +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.note}``" -msgstr "``#{user.created_by.note}``" +#: ../system/objects/types.rst:70 +msgid "Default time diff (minutes)" +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Mobile" -msgstr "Geçerli Kullanıcı > Oluşturan > Mobil" +#: ../system/objects/types.rst:69 +msgid "" +"This setting helps the user by highlighting the day from now plus the " +"provided value. It does not pre-fill the field." +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.mobile}``" -msgstr "``#{user.created_by.mobile}``" +#: ../system/objects/types.rst:0 +#, fuzzy +msgid "Available settings for Date & time fields" +msgstr "Posta Sunucusu Ayarları" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Login" -msgstr "Geçerli Kullanıcı > Oluşturan > Giriş" +#: ../system/objects/types.rst:86 +#, fuzzy +msgid "Integer field" +msgstr "Sayı" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.login}``" -msgstr "``#{user.created_by.login}``" +#: ../system/objects/types.rst:76 +msgid "" +"Provides an input field that allows integer usage only. You may define a " +"default value. You cannot enforce comma separation." +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Lastname" -msgstr "Geçerli Kullanıcı > Oluşturan > Soyad" +#: ../system/objects/types.rst:80 +msgid "Minimal" +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.lastname}``" -msgstr "``#{user.created_by.lastname}``" +#: ../system/objects/types.rst:80 +msgid "The minimal value the field accepts." +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Firstname" -msgstr "Geçerli Kullanıcı > Oluşturan > Ad" +#: ../system/objects/types.rst:83 +msgid "Maximal" +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.firstname}``" -msgstr "``#{user.created_by.firstname}``" +#: ../system/objects/types.rst:83 +msgid "The maximum value the field accepts." +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Fax" -msgstr "Geçerli Kullanıcı > Oluşturan > Faks" +#: ../system/objects/types.rst:0 +msgid "Available settings for Integer fields" +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.fax}``" -msgstr "``#{user.created_by.fax}``" +#: ../system/objects/types.rst:99 +msgid "Multiple selection field" +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Email" -msgstr "Geçerli Kullanıcı > Oluşturan > E-posta" +#: ../system/objects/types.rst:89 +msgid "" +"Provides a selection field that allows the selection of one or more out of " +"several. This field does allow setting a default value." +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.email}``" -msgstr "``#{user.created_by.email}``" +#: ../system/objects/types.rst:0 +#, fuzzy +msgid "Available settings for Multiple selection fields" +msgstr "Posta Sunucusu Ayarları" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Department" -msgstr "Geçerli Kullanıcı > Oluşturan > Bölüm" +#: ../system/objects/types.rst:112 +msgid "Single selection field" +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.department}``" -msgstr "``#{user.created_by.department}``" +#: ../system/objects/types.rst:102 +msgid "" +"Provides a drop-down field that allows selection of one value out of " +"several. This field does allow setting a default value." +msgstr "" -#: ../system/variables/current-user.rst:1 +#: ../system/objects/types.rst:0 #, fuzzy -msgid "Current User > Created by > Avatar" -msgstr "Geçerli Kullanıcı > Oluşturan > Faks" +msgid "Available settings for Single selection fields" +msgstr "Posta Sunucusu Ayarları" -#: ../system/variables/current-user.rst:1 +#: ../system/objects/types.rst:142 #, fuzzy -msgid "``#{user.created_by.avatar(60,60)}``" -msgstr "``#{user.created_by.lastname}``" +msgid "Textarea field" +msgstr "Metin" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Address" -msgstr "Geçerli Kullanıcı > Oluşturan > Adres" +#: ../system/objects/types.rst:115 +msgid "" +"Provides a text area input field (multiple lines) and thus allows e.g. new " +"lines. You can set a default field value." +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.address}``" -msgstr "``#{user.created_by.address}``" +#: ../system/objects/types.rst:120 +msgid "" +"Please note that this field *does not* support text formatting or HTML " +"content (rich text)." +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created at" -msgstr "Geçerli Kullanıcı > Oluşturulma tarihi" +#: ../system/objects/types.rst:123 +msgid "**🥵 This field can consume a lot of visual space**" +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_at}``" -msgstr "``#{user.created_at}``" +#: ../system/objects/types.rst:125 +msgid "" +"Depending on where you use this field type, it may use a lot of visual space " +"if you provide a lot of text. This may be an issue to work with." +msgstr "" -#: ../system/variables/current-user.rst:1 +#: ../system/objects/types.rst:130 #, fuzzy -msgid "Current User > Avatar" -msgstr "Geçerli Kullanıcı > Faks" +msgid "Default" +msgstr "Varsayılan değer" + +#: ../system/objects/types.rst:129 +msgid "" +"The here provided text will be shown within the text area field or new data " +"sets." +msgstr "" + +#: ../system/objects/types.rst:134 ../system/objects/types.rst:160 +msgid "Maxlength" +msgstr "" -#: ../system/variables/current-user.rst:1 +#: ../system/objects/types.rst:0 ../system/objects/types.rst:160 #, fuzzy -msgid "``#{user.avatar(60,60)}``" -msgstr "``#{user.lastname}``" +msgid "You can pick the maximum length of the field." +msgstr "alanın maksimum uzunluğunu seçebilirsiniz." -#: ../system/variables/current-user.rst:1 -msgid "Current User > Address" -msgstr "Geçerli Kullanıcı > Adres" +#: ../system/objects/types.rst:0 +msgid "The default length of this object is ``500``." +msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.address}``" -msgstr "``#{user.address}``" +#: ../system/objects/types.rst:139 +msgid "Rows" +msgstr "" -#: ../system/variables/ticket.rst:6 +#: ../system/objects/types.rst:0 msgid "" -"Below you can find all available ticket-based variables within Zammad. These " -"can be called via Triggers for example. If you're unsure if Zammad does " -"support variables at the point you're at, you can try to type ``::`` to " -"check." +"Change the number of rows to dislay so that you can use only the space you " +"really need." msgstr "" -"Aşağıda, Zammad içindeki tüm bilet tabanlı değişkenleri bulabilirsiniz. " -"Bunlar örneğin Tetikleyiciler aracılığıyla çağrılabilir. Bulunduğunuz " -"noktada Zammad'ın değişkenleri destekleyip desteklemediğinden emin " -"değilseniz, kontrol etmek için ``::`` yazmayı deneyebilirsiniz." -#: ../system/variables/ticket.rst:12 -msgid "Ticket Variables" -msgstr "Bilet Değişkenleri" +#: ../system/objects/types.rst:0 +msgid "The default number of rows is ``4``." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Web" -msgstr "Bilet > Güncelleyen > Web" +#: ../system/objects/types.rst:0 +#, fuzzy +msgid "Available settings for Textarea fields" +msgstr "Posta Sunucusu Ayarları" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.web}``" -msgstr "``#{ticket.updated_by.web}``" +#: ../system/objects/types.rst:165 +msgid "Text field" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > VIP" -msgstr "Bilet > Güncelleyen > VIP" +#: ../system/objects/types.rst:145 +msgid "Provides a text field (one line) and allows choosing a default value." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.vip}``" -msgstr "``#{ticket.updated_by.vip}``" +#: ../system/objects/types.rst:148 +msgid "" +"Defines the type of the input field. This allows e.g. your browser to ensure " +"that you provide the specific type." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Phone" -msgstr "Bilet > Güncelleyen > Telefon" +#: ../system/objects/types.rst:152 +msgid "Currently available:" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.phone}``" -msgstr "``#{ticket.updated_by.phone}``" +#: ../system/objects/types.rst:155 +msgid "Phone" +msgstr "" + +#: ../system/objects/types.rst:156 +msgid "Text" +msgstr "Metin" + +#: ../system/objects/types.rst:157 +msgid "Url *(URL fields disable link-template availability)*" +msgstr "" + +#: ../system/objects/types.rst:0 +msgid "Available settings for Text fields" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Note" -msgstr "Bilet > Güncelleyen > Not" +#: ../system/objects/types.rst:174 +msgid "Single tree selection field" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.note}``" -msgstr "``#{ticket.updated_by.note}``" +#: ../system/objects/types.rst:168 +msgid "" +"Provides a select-like field with up to 6 layers of options. Does not allow " +"setting a default value." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Mobile" -msgstr "Bilet > Güncelleyen > Mobil" +#: ../system/objects/types.rst:0 +msgid "Available settings for Tree Select fields" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.mobile}``" -msgstr "``#{ticket.updated_by.mobile}``" +#: ../system/objects/types.rst:183 +msgid "Multiple tree selection field" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Login" -msgstr "Bilet > Güncelleyen > Giriş" +#: ../system/objects/types.rst:177 +msgid "" +"Provides a select-like field with up to 6 layers of options allowing the " +"selection of multiple values. Does not allow setting a default value." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.login}``" -msgstr "``#{ticket.updated_by.login}``" +#: ../system/objects/types.rst:302 +msgid "External Data Source field" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Lastname" -msgstr "Bilet > Güncelleyen > Soyadı" +#: ../system/objects/types.rst:186 +msgid "" +"Provides a searchable field which fetches data from an external system. This " +"can be useful if you have data outside of Zammad and don't want to maintain " +"both data sources." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.lastname}``" -msgstr "``#{ticket.updated_by.lastname}``" +#: ../system/objects/types.rst:190 +msgid "The feature works as follows:" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Firstname" -msgstr "Bilet > Güncelleyen > Ad" +#: ../system/objects/types.rst:192 +msgid "" +"Zammad sends a query with a search string (free text from agent or based on " +"a variable) in a pre-defined format (\"Search URL\") to an external system." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.firstname}``" -msgstr "``#{ticket.updated_by.firstname}``" +#: ../system/objects/types.rst:195 +msgid "" +"This external system searches for matches and provides a response as a JSON " +"structure to Zammad." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Fax" -msgstr "Bilet > Güncelleyen > Faks" +#: ../system/objects/types.rst:197 +msgid "" +"Zammad just looks for the defined list and value keys, reads the content and " +"displays the value to the user. There is no search on Zammad side." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.fax}``" -msgstr "``#{ticket.updated_by.fax}``" +#: ../system/objects/types.rst:201 +msgid "" +"The usage of a PostgreSQL database for Zammad is required. In any other " +"case, Zammad will hide the external data source type and you are not able to " +"use it. If you want to use this feature, consider to :docs:`migrate your " +"database `." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Email" -msgstr "Bilet > Güncelleyen > E-posta" +#: ../system/objects/types.rst:205 +msgid "Currently, only ``GET`` is supported as request method." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.email}``" -msgstr "``#{ticket.updated_by.email}``" +#: ../system/objects/types.rst:206 +msgid "" +"The data structure must be in JSON format and provide the objects in an " +"array." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Department" -msgstr "Bilet > Güncelleyen > Bölüm" +#: ../system/objects/types.rst:208 +msgid "" +"The endpoint for the external data source has to support search. On Zammad " +"side, there is no search/logic implemented; however, you can define the " +"output key and value based on the result(s) from the response (which " +"provides already filtered content based on the search)." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.department}``" -msgstr "``#{ticket.updated_by.department}``" +#: ../system/objects/types.rst:212 +msgid "" +"If you receive more results as expected, your external data source search " +"may not work properly or the structure of the URL is not correct. You should " +"get in touch with a responsible person from the external system." +msgstr "" -#: ../system/variables/ticket.rst:1 -#, fuzzy -msgid "Ticket > Updated by > Avatar" -msgstr "Bilet > Güncelleyen > Faks" +#: ../system/objects/types.rst:217 +msgid "" +"Please have a look :doc:`at our example `, where you can find a possible configuration for a public " +"dummy endpoint." +msgstr "" -#: ../system/variables/ticket.rst:1 +#: ../system/objects/types.rst:0 #, fuzzy -msgid "``#{ticket.updated_by.avatar(60,60)}``" -msgstr "``#{ticket.updated_by.lastname}``" +msgid "Available settings for external data source fields" +msgstr "Posta Sunucusu Ayarları" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Address" -msgstr "Bilet > Güncelleyen > Adres" +#: ../system/objects/types.rst:242 +msgid "Search URL" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.address}``" -msgstr "``#{ticket.updated_by.address}``" +#: ../system/objects/types.rst:227 +msgid "" +"Set your endpoint where Zammad fetches the data. Please make sure to include " +"a valid search :doc:`variable ` as an URL parameter. " +"Example for a free text search at user input: ``#{search.term}``" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated at" -msgstr "Bilet > Güncelleme" +#: ../system/objects/types.rst:232 +msgid "" +"If in doubt, ask the responsible person for the external data source how " +"they expect the structure of the URL." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_at}``" -msgstr "``#{ticket.updated_at}``" +#: ../system/objects/types.rst:236 +msgid "" +"Depending on your search variable, the preview might work or not. The reason " +"is that the context might not be available and it is no bug." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Title" -msgstr "Bilet > Başlık" +#: ../system/objects/types.rst:239 +msgid "" +"Please also make sure to use a variable which is available in your object " +"context. For example you won't be able to search for a ticket in a user " +"object context." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.title}``" -msgstr "``#{ticket.title}``" +#: ../system/objects/types.rst:252 +#, fuzzy +msgid "SSL Verification" +msgstr "Doğrulama" + +#: ../system/objects/types.rst:245 +msgid "Here you can switch the SSL verification to no." +msgstr "" -#: ../system/variables/ticket.rst:1 +#: ../system/objects/types.rst:249 msgid "" -"``My amazing Subject`` (normally subject, can be edited within Interface and " -"thus differ)" +"If your external data source system is using self signed certificates, " +"please have a look :doc:`here ` for " +"further information about how to handle them in Zammad, so you can keep the " +"SSL verification activated." msgstr "" -"``Benim harika Konum`` (normalde konu, Arayüzden değiştirilebilir bu nedenle " -"farklı)" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Accounted Time" -msgstr "Bilet > Hesaplanan Zaman" +#: ../system/objects/types.rst:258 +msgid "HTTP Authentication" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.time_unit}``" -msgstr "``#{ticket.time_unit}``" +#: ../system/objects/types.rst:255 +msgid "" +"If your external data source requires an authentication, you can set it " +"here. You can leave it empty or choose between *Basic Authentication* or " +"*Authentication Token* (selecting one of the two methods leads to additional " +"fields where you can enter your credentials/token)." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``1``, ``2.75`` or empty response" -msgstr "``1``, ``2.75`` veya boş yanıt" +#: ../system/objects/types.rst:265 +msgid "Search result list key" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Tags" -msgstr "Bilet > Etiketler" +#: ../system/objects/types.rst:261 +msgid "" +"Defines the level in the JSON structure which provides the list with search " +"results. You can leave it empty, if the data is already provided as an " +"array. If you have to go deeper in the structure, you can provide a path " +"with ``.`` as separators, e.g. ``key.subkey.sub-sub-key``." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.tags}``" -msgstr "``#{ticket.tags}``" +#: ../system/objects/types.rst:271 +#, fuzzy +msgid "Search result value key" +msgstr "Varsayılan değer" -#: ../system/variables/ticket.rst:1 +#: ../system/objects/types.rst:268 msgid "" -"Currently not available, see `Issue 2769 `_" -msgstr "Şu anda mevcut değil, `Issue 2769 `_a göz atın" +"Defines the attribute in the structure in which your external data source " +"provides the *value* for your data. An example would be a product *number*. " +"If you have to go deeper in the structure, you can provide a path with ``.`` " +"as separators, e.g. ``key.subkey.sub-sub-key``." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > State > Name" -msgstr "Bilet > Durum > Ad" +#: ../system/objects/types.rst:277 +msgid "Search result label key" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.state.name}``" -msgstr "``#{ticket.state.name}``" +#: ../system/objects/types.rst:274 +msgid "" +"Defines the attribute in the structure in which your external data source " +"provides the *label* for your data. An example would be a product *name*. If " +"you have to go deeper in the structure, you can provide a path with ``.`` as " +"separators, e.g. ``key.subkey.sub-sub-key``." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``new``, ``open``, ..." -msgstr "``yeni``, ``açık``, ..." +#: ../system/objects/types.rst:280 +msgid "" +"In the preview area, you can find the following items (depending on your " +"configuration above):" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Priority > Name" -msgstr "Bilet > Öncelik > Ad" +#: ../system/objects/types.rst:283 +msgid "" +"**Error/hint message** (only if configuration is not complete): Zammad tells " +"you, if there is a problem and what you should change in your configuration." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.priority.name}``" -msgstr "``#{ticket.priority.name}``" +#: ../system/objects/types.rst:286 +msgid "" +"**Search field**: search for an existing attribute in the data source to get " +"a preview. This is required for the fields below to show up." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2 normal``" -msgstr "``2 normal``" +#: ../system/objects/types.rst:288 +msgid "" +"**Search result response** (only if configuration is not complete): here you " +"can find a syntax highlighted JSON preview of the response, based on the " +"search term you entered." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Pending till" -msgstr "Bilet > Bekleme süresi" +#: ../system/objects/types.rst:291 +msgid "" +"**Search result list** (only if *search result list key* is properly set): " +"output of the structure under the configured *search result list key*." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.pending_time}``" -msgstr "``#{ticket.pending_time}``" +#: ../system/objects/types.rst:294 +msgid "" +"**Preview table** (when fully configured): Zammad shows you a table which " +"includes the found items based on the search string (value, label and " +"optional link). You can use this preview if you don't have the complete data " +"structure of the external system in mind." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not set" -msgstr "``2019-10-07 16:25:00 UTC`` veya ayarlanmadıysa boş" +#: ../system/objects/types.rst:299 +msgid "" +"An example of a configured external data source field from agent perspective:" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Web" -msgstr "Bilet > Sahip > Web" +#: ../system/objects/types.rst:0 +msgid "Screencast showing the search for a product in a ticket" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.web}``" -msgstr "``#{ticket.owner.web}``" +#: ../system/objects/types.rst:307 +msgid "URL fields (Link-Template)" +msgstr "URL alanları (Bağlantı-Şablon)" -#: ../system/variables/ticket.rst:1 -msgid "``https://zammad.com`` or empty if not set" -msgstr "``https://zammad.com``` veya ayarlanmadıysa boş" +#: ../system/objects/types.rst:311 +msgid "" +"This function is restricted to Text, Select and External data source types " +"only." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > VIP" -msgstr "Bilet > Sahip > VIP" +#: ../system/objects/types.rst:314 +msgid "" +"Link-Templates are an amazing way to dynamically generate URLs. They allow " +"you to integrate other systems better without having to manually copy data " +"from Zammad if possible." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.vip}``" -msgstr "``#{ticket.owner.vip}``" +#: ../system/objects/types.rst:320 +msgid "" +"Another great way of communicating with another system may be Zammad's :doc:" +"`Webhooks `." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Phone" -msgstr "Bilet > Sahip > Telefon" +#: ../system/objects/types.rst:323 +msgid "" +"After filling a link-template enabled field, an URL icon will appear on its " +"right. Clicking on the icon opens a new tab." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.phone}``" -msgstr "``#{ticket.owner.phone}``" +#: ../system/objects/types.rst:328 +msgid "" +"Even though Zammad displays the link template within object edit and create " +"screens, the function is optional. It's only active if you populate the " +"field." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Note" -msgstr "Bilet > Sahip > Not" +#: ../system/objects/types.rst:333 +msgid "" +"What's the difference between URL and text fields with link template...?!" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.note}``" -msgstr "``#{ticket.owner.note}``" +#: ../system/objects/types.rst:335 +msgid "" +"Both fields have different use cases. Use ``text`` type text fields when " +"ever you have a *static* url that requires dynamic parameters. If you " +"require a drag & drop like field that you can put in any URL, use ``URL`` " +"type text fields." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Mobile" -msgstr "Bilet > Sahip > Mobil" +#: ../system/objects/types.rst:340 +msgid "" +"The difference is easier to spot when comparing the fields directly, below " +"screencast shows the result - the dynamic approach uses existing values in " +"the moment of updating to built the URL - e.g. ``https://google.com/search?" +"q=cookies`` - while the URL approach uses the actual URL of the field - e.g. " +"``https://zammad.com``." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.mobile}``" -msgstr "``#{ticket.owner.mobile}``" +#: ../system/objects/types.rst:None +msgid "" +"Screencast showing the differents in between URL and text type fields with " +"actual values" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Login" -msgstr "Bilet > Sahip > Giriş" +#: ../system/objects/types.rst:352 +msgid "How does this work...?!" +msgstr "Bu nasıl çalışır... ?!" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.login}``" -msgstr "``#{ticket.owner.login}``" +#: ../system/objects/types.rst:354 +msgid "" +"As an example, let's say you have an attribute called ``amazing_attribute`` " +"and you want to open a google search directly with the input from that field." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``agent``" -msgstr "``aracı``" +#: ../system/objects/types.rst:357 +msgid "" +"Providing the link-template field below allows you to do so: ``https://www." +"google.com/search?q=#{ticket.amazing_attribute}``" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Lastname" -msgstr "Bilet > Sahip > Soyadı" +#: ../system/objects/types.rst:362 +msgid "" +"You can use any :doc:`Zammad variable ` as long as it's " +"available in the moment you need it." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.lastname}``" -msgstr "``#{ticket.owner.lastname}``" +#: ../system/objects/types.rst:365 +msgid "" +"As a result, you are redirected to Google with a search for the value of the " +"attribute, if you click on the button in the ticket (as you can see in the " +"screencast above)." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Mustermann`` or empty if not set" -msgstr "``Mustermann`` veya ayarlanmadıysa boş" +#: ../system/packages.rst:2 +msgid "Packages" +msgstr "Paketler" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Firstname" -msgstr "Bilet > Sahip > Ad" +#: ../system/packages.rst:4 +msgid "That's the package management-area." +msgstr "Burası paket yönetim alanı." -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.firstname}``" -msgstr "``#{ticket.owner.firstname}``" +#: ../system/packages.rst:6 +msgid "Individual add-ons for Zammad can be installed and managed here." +msgstr "Zammad için özel eklentiler buradan kurulabilir ve yönetilebilir." -#: ../system/variables/ticket.rst:1 -msgid "``Max`` or empty if not set" -msgstr "``Max`` veya ayarlanmadıysa boş" +#: ../system/sessions.rst:2 +msgid "Sessions" +msgstr "Oturumlar" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Fax" -msgstr "Bilet > Sahip > Faks" +#: ../system/sessions.rst:4 +msgid "" +"Sessions management allows reviewing currently known user sessions and " +"allows to end these. The session timeout is affected by :ref:" +"`security_session_timeout` configurations from security settings." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.fax}``" -msgstr "``#{ticket.owner.fax}``" +#: ../system/sessions.rst:None +msgid "Screenshot showing Zammad's session management" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Email" -msgstr "Bilet > Sahip > E-posta" +#: ../system/sessions.rst:13 +#, fuzzy +msgid "Zammad will provide the following information:" +msgstr "Bu bölümde şu anda aşağıdaki entegrasyonlar eksik:" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.email}``" -msgstr "``#{ticket.owner.email}``" +#: ../system/sessions.rst:16 +msgid "" +"The user account this session entry belongs to. It can be normal if a user " +"has several sessions in the list. This can be due to changed browser " +"information or if you use e.g. single sign on methods where the user does " +"not use the log off button." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``agent@company.tld`` or empty if not set" -msgstr "``agent@company.tld`` veya ayarlanmadıysa boş" +#: ../system/sessions.rst:22 +msgid "Browser" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Department" -msgstr "Bilet > Sahip > Bölüm" +#: ../system/sessions.rst:22 +msgid "The browser agent communicated to Zammad." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.department}``" -msgstr "``#{ticket.owner.department}``" +#: ../system/sessions.rst:40 +#, fuzzy +msgid "Location" +msgstr "Bildirimleri Engelle" -#: ../system/variables/ticket.rst:1 -msgid "``Support`` or empty if not set" -msgstr "``Destek`` veya ayarlanmadıysa boş" +#: ../system/sessions.rst:25 +msgid "" +"The anticipated location based on the users IP address. Depending on the IP " +"address the result shown may differ. This option depends on :doc:`/settings/" +"system/services`." +msgstr "" -#: ../system/variables/ticket.rst:1 -#, fuzzy -msgid "Ticket > Owner > Avatar" -msgstr "Bilet > Sahip > Faks" +#: ../system/sessions.rst:29 +msgid "The following information can be shown:" +msgstr "" -#: ../system/variables/ticket.rst:1 +#: ../system/sessions.rst:33 #, fuzzy -msgid "``#{ticket.owner.avatar(60,60)}``" -msgstr "``#{ticket.owner.lastname}``" +msgid "IP address" +msgstr "Proxy Adresi" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Address" -msgstr "Bilet > Sahip > Adres" +#: ../system/sessions.rst:32 +msgid "" +"Either if you set *Geo IP services* to inactive or you're using internal IP " +"address which do not provide location information." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.address}``" -msgstr "``#{ticket.owner.address}``" +#: ../system/sessions.rst:40 +msgid "Country (or Country + City)" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Shared organization" -msgstr "Bilet > Organizasyon > Paylaşılan organizasyon" +#: ../system/sessions.rst:36 +msgid "" +"If *Geo IP services* is enabled only. Depends on how detailed the available " +"IP address information are." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.shared}``" -msgstr "``#{ticket.organization.shared}``" +#: ../system/sessions.rst:39 +msgid "" +"Be aware that results can be inaccurate - this technically is not an error." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Note" -msgstr "Bilet > Organizasyon > Not" +#: ../system/sessions.rst:43 +msgid "Age" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.note}``" -msgstr "``#{ticket.organization.note}``" +#: ../system/sessions.rst:43 +msgid "Provides the time when the session initially has been created." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Name" -msgstr "Bilet > Organizasyon > Ad" +#: ../system/sessions.rst:50 +#, fuzzy +msgid "Update" +msgstr "Güncelleme Zamanı" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.name}``" -msgstr "``#{ticket.organization.name}``" +#: ../system/sessions.rst:46 +msgid "" +"Provides the time the user used this session to open Zammad. This timestamp " +"is only updated if the user e.g. reloads, not during normal work on tickets." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Zammad GmbH`` or empty if not set" -msgstr "``Zammad GmbH``` veya ayarlanmadıysa boş" +#: ../system/sessions.rst:50 +msgid "This timestamp is being used for the session timeout." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Domain based assignment" -msgstr "Bilet > Organizasyon > Alan adına göre atama" +#: ../system/sessions.rst:53 +msgid "" +"Use the delete button to remove a single session on behalf of your user." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.domain_assignment}``" -msgstr "``#{ticket.organization.domain_assignment}``" +#: ../system/subscription.rst:2 +#, fuzzy +msgid "Subscription (SaaS)" +msgstr "Açıklama" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Domain" -msgstr "Bilet > Organizasyon > Alan adı" +#: ../system/subscription.rst:4 +msgid "" +"The subscription settings page allows you to configure your instances " +"package and number of agents required." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.domain}``" -msgstr "``#{ticket.organization.domain}``" +#: ../system/subscription.rst:9 +msgid "" +"This setting section is only available for Hosted setups. If you're looking " +"for on premise support contracts, please see the `Zammad pricing page " +"`_." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``domain.tld`` or empty if not set" -msgstr "``domain.tld``` veya ayarlanmadıysa boş" +#: ../system/subscription.rst:14 ../system/subscription.rst:34 +msgid "Plan" +msgstr "" -#: ../system/variables/ticket.rst:1 -#, fuzzy -msgid "Ticket > Organization > VIP" -msgstr "Bilet > Organizasyon > Not" +#: ../system/subscription.rst:16 +msgid "" +"Here you can set up everything affecting your instance subscription " +"functions like number of agents and package." +msgstr "" -#: ../system/variables/ticket.rst:1 -#, fuzzy -msgid "``#{ticket.organization.vip}``" -msgstr "``#{ticket.organization.domain}``" +#: ../system/subscription.rst:19 +msgid "" +"On top of the page you can find a subscription summary. You'll find the " +"number of used and available (booked) agent seats there. By using the *see " +"more* link you can also expand an agent list to see the currently configured " +"active agents. This list *does not* count accounts with admin permissions " +"only." +msgstr "" -#: ../system/variables/ticket.rst:1 -#, fuzzy -msgid "Ticket > Number" -msgstr "bilet numarası" +#: ../system/subscription.rst:None +msgid "" +"Within subscription you can always see how many agents are still\n" +"available to add and who uses the seats." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.number}``" -msgstr "``#{ticket.number}``" +#: ../system/subscription.rst:29 +msgid "" +"Learn more on how to manage your agents in general :doc:`here `." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``31001``, ``201910731001``, ..." -msgstr "``31001``, ``201910731001``, ..." +#: ../system/subscription.rst:36 +msgid "" +"This section gives you an overview of the available plans and their " +"functions / limits. If you require a more detailed table, check our " +"`detailed pricing table `_ for more." +msgstr "" -#: ../system/variables/ticket.rst:1 -#, fuzzy -msgid "Ticket > ID" -msgstr "Bilet > #" +#: ../system/subscription.rst:40 +msgid "" +"Your selection in this step will decide on the base agent price and e.g. " +"agent limits that might apply in the summary step." +msgstr "" -#: ../system/variables/ticket.rst:1 -#, fuzzy -msgid "``#{ticket.id}``" -msgstr "``#{ticket.title}``" +#: ../system/subscription.rst:43 +msgid "" +"The green *Selected* button will also tell you what plan you're currently in." +msgstr "" -#: ../system/variables/ticket.rst:1 -#, fuzzy -msgid "``17``, ``5281``, ..." -msgstr "``yeni``, ``açık``, ..." +#: ../system/subscription.rst:47 +msgid "" +"Trial instances are running at Professional with 3 agents. The plan cannot " +"be changed during the trial for technical reasons, if you require more " +"agents for testing, please contact `our sales team `_ with a reason for the raise request." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact (customer)" -msgstr "Bilet > Son iletişim (müşteri)" +#: ../system/subscription.rst:None +msgid "" +"Screenshot showing three available packages for a hosted Zammad\n" +"instance" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_customer_at}``" -msgstr "``#{ticket.last_contact_customer_at}``" +#: ../system/subscription.rst:57 +msgid "" +"At the bottom of this block you can find a summary where you can adjust the " +"settings of the previous selected plan." +msgstr "" -#: ../system/variables/ticket.rst:1 -#, fuzzy +#: ../system/subscription.rst:62 msgid "" -"``2019-10-07 16:25:00 UTC`` or empty if not applicable yet (Please note " -"`Ticket last contact behavior Settings `_ for this)" +"Note that upgrading (more agents, higher package) is always possible, " +"however, downgrading will only happen when your billing period renews." msgstr "" -"``2019-10-07 16:25:00 UTC`` veya henüz uygun değilse boş (Bunun için lütfen " -"`Bilet son iletişim davranışı Ayarları`_na dikkat edin)" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact" -msgstr "Bilet > Son iletişim" +#: ../system/subscription.rst:66 +msgid "" +"Upgrading resets your billing period and existing credit will be deducted " +"from the new total." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_at}``" -msgstr "``#{ticket.last_contact_at}``" +#: ../system/subscription.rst:75 +msgid "Billing cycle" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact (agent)" -msgstr "Bilet > Son iletişim (aracı)" +#: ../system/subscription.rst:70 +msgid "" +"You can choose between either monthly or yearly billing. The price per agent " +"will be cheaper if you decide for yearly billing." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_agent_at}``" -msgstr "``#{ticket.last_contact_agent_at}``" +#: ../system/subscription.rst:73 +msgid "" +"If you're still trying out things and are unsure of the right package for " +"your instance, you may want to choose monthly first and then upgrade to " +"yearly when you're sure." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable yet" -msgstr "``2019-10-07 16:25:00 UTC`` veya henüz uygulanabilir değilse boş" +#: ../system/subscription.rst:83 +msgid "Plan: (Starter|Professional|Plus) - Agents" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Note" -msgstr "Bilet > Grup > Not" +#: ../system/subscription.rst:78 +msgid "Choose the number of agents you require for your instance." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.note}``" -msgstr "``#{ticket.group.note}``" +#: ../system/subscription.rst:80 +msgid "" +"Keep in mind that some packages may have agent limits. Depending on the " +"previous chosen package, you won't be able to exceed specific agent numbers. " +"Also note that setting less agents than currently configured is not possible." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Note about this group``" -msgstr "``Bu grup hakkında not``" +#: ../system/subscription.rst:86 +msgid "Total" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Name" -msgstr "Bilet > Grup > Ad" +#: ../system/subscription.rst:86 +msgid "This will be the net total you're going to be billed." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.name}``" -msgstr "``#{ticket.group.name}``" +#: ../system/subscription.rst:88 +msgid "" +"By using the *Update subscription* button, the instance package will be " +"adjusted immediately. If you didn't provide a payment method yet, Zammad " +"will request you to provide one at this point." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Sales``" -msgstr "``Satışlar``" +#: ../system/subscription.rst:94 +msgid "" +"In case you're still within the trial period, this means that the trial will " +"be over immediately!" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Follow-up possible" -msgstr "Bilet > Grup > Takip mümkün" +#: ../system/subscription.rst:97 +msgid "Down- or upgrading during the trial period *is not* possible." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.follow_up_possible}``" -msgstr "``#{ticket.group.follow_up_possible}``" +#: ../system/subscription.rst:None +msgid "Screenshot showing payment options and a pricing summary" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``no`` or ``yes``" -msgstr "``hayır`` veya ``evet``" +#: ../system/subscription.rst:103 +#, fuzzy +msgid "Billing Information" +msgstr "Web site bilgisi" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Assign Follow-Ups" -msgstr "Bilet > Grup > Atanmış Takipler" +#: ../system/subscription.rst:105 +msgid "" +"You can control all billing relevant information like invoices, billing " +"address and the option to cancel your subscription." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.follow_up_assignment}``" -msgstr "``#{ticket.group.follow_up_assignment}``" +#: ../system/subscription.rst:108 +msgid "" +"All adjusted billing information below only affect future invoices. If your " +"invoice was issued wrong, please contact `our sales team `_." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Assignment Timeout" -msgstr "Bilet > Grup > Atanma Zaman Aşımı" +#: ../system/subscription.rst:114 +#, fuzzy +msgid "Billing address" +msgstr "E-posta Adresi" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.assignment_timeout}``" -msgstr "``#{ticket.group.assignment_timeout}``" +#: ../system/subscription.rst:113 +msgid "" +"Provide your company address here, make sure to include the companies name " +"in case required. This address will be referenced on your invoice." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``20`` or empty if not configured" -msgstr "``20`` veya yapılandırılmadıysa boş" +#: ../system/subscription.rst:118 +msgid "VAT ID" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > First response" -msgstr "Bilet > İlk yanıt" +#: ../system/subscription.rst:117 +msgid "" +"Provide your VAT ID here. If applicable your invoice will not contain German " +"VAT. Please make sure to pay the VAT in your country as required." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.first_response_at}``" -msgstr "``#{ticket.first_response_at}``" +#: ../system/subscription.rst:127 +#, fuzzy +msgid "Billing Email Address" +msgstr "E-posta Adresi" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Escalation at" -msgstr "Bilet > Yükselme" +#: ../system/subscription.rst:121 +msgid "" +"Usually the instance owner (the person that registered the instance) will " +"receive all emails including the invoices. In case you have your own billing " +"department, you can provide their email address here." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.escalation_at}``" -msgstr "``#{ticket.escalation_at}``" +#: ../system/subscription.rst:125 +msgid "" +"All billing relevant information will then be sent to this email address." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable" -msgstr "``2019-10-07 16:25:00 UTC`` veya uygulanabilir değilse boş" +#: ../system/subscription.rst:127 +msgid "Invoices are sent as attachment (PDF) to this email address." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Web" -msgstr "Bilet > Müşteri > Web" +#: ../system/subscription.rst:129 +msgid "" +"Don't forget to press the *Update billing information* button after you " +"changed above settings." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.web}``" -msgstr "``#{ticket.customer.web}``" +#: ../system/subscription.rst:None +msgid "" +"Screenshot showing options for billing information within the\n" +"subscription menu" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > VIP" -msgstr "Bilet > Müşteri > VIP" +#: ../system/subscription.rst:137 +#, fuzzy +#| msgid "Method" +msgid "Payment Method" +msgstr "Yöntem" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.vip}``" -msgstr "``#{ticket.customer.vip}``" +#: ../system/subscription.rst:139 +msgid "You can pay via credit card or SEPA mandate." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Phone" -msgstr "Bilet > Müşteri > Telefon" +#: ../system/subscription.rst:144 +msgid "Credit card" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.phone}``" -msgstr "``#{ticket.customer.phone}``" +#: ../system/subscription.rst:142 +msgid "" +"Simply follow the dialogue by clicking *authorize credit card* and confirm -" +"if required by your bank- your consent to Zammad using your card for the " +"payments." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Note" -msgstr "Bilet > Müşteri > Not" +#: ../system/subscription.rst:148 +msgid "SEPA Direct Debit" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.note}``" -msgstr "``#{ticket.customer.note}``" +#: ../system/subscription.rst:147 +msgid "" +"Provide the requested information of the bank account holder and update if " +"you're ready. You'll then receive an email with the SEPA mandate." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Mobile" -msgstr "Bilet > Müşteri > Mobil" +#: ../system/subscription.rst:150 +msgid "" +"Technically there's also the possibility to pay via invoice, however - this " +"method only applies to a fairly low number of instances. Please contact `our " +"sales team `_ for more information." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.mobile}``" -msgstr "``#{ticket.customer.mobile}``" +#: ../system/subscription.rst:156 +#, fuzzy +msgid "Cancel Subscription" +msgstr "Açıklama" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Login" -msgstr "Bilet > Müşteri > Giriş" +#: ../system/subscription.rst:158 +msgid "" +"Do you want to cancel your subscription? In case you no longer want to use " +"Zammad's SaaS, you can cancel your subscription by using the red *Yes, " +"please cancel my subscription* button." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.login}``" -msgstr "``#{ticket.customer.login}``" +#: ../system/subscription.rst:162 +msgid "" +"To cancel the description, enter the FQDN of your Zammad instance and " +"provide a reason for your cancellation." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Lastname" -msgstr "Bilet > Müşteri > Soyad" +#: ../system/subscription.rst:165 +msgid "" +"Your subscription will end the day after your trial or billing period ends." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.lastname}``" -msgstr "``#{ticket.customer.lastname}``" +#: ../system/subscription.rst:None +#, fuzzy +msgid "Screenshot showing subscription cancellation dialog" +msgstr "İlk oturum açmada otomatik hesap bağlantısı" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Firstname" -msgstr "Bilet > Müşteri > Ad" +#: ../system/subscription.rst:174 +msgid "" +"We will remind you about your cancelled subscription several times up front. " +"After the subscription ended all instance data will be removed. A restore " +"*is not* possible after that point!" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.firstname}``" -msgstr "``#{ticket.customer.firstname}``" +#: ../system/subscription.rst:178 +msgid "**😖 Cancelled by accident?**" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Fax" -msgstr "Bilet > Müşteri > Faks" +#: ../system/subscription.rst:180 +msgid "" +"You can always undo the cancellation via the *Yes, undo the cancellation of " +"my subscription* button up to the last subscription day!" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.fax}``" -msgstr "``#{ticket.customer.fax}``" +#: ../system/subscription.rst:0 +msgid "" +"Screenshot showing a red button to cancel the subscription\n" +"cancellation" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Email" -msgstr "Bilet > Müşteri > E-posta" +#: ../system/subscription.rst:189 +msgid "Payment History" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.email}``" -msgstr "``#{ticket.customer.email}``" +#: ../system/subscription.rst:191 +msgid "" +"The payment history will display a history of all paid invoices. At this " +"point you can also download these in case you need them again." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Department" -msgstr "Bilet > Müşteri > Bölüm" +#: ../system/subscription.rst:196 +msgid "" +"You will only find *paid* invoices here. Invoices that are to be billed are " +"not available before the payment is completed." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.department}``" -msgstr "``#{ticket.customer.department}``" +#: ../system/subscription.rst:201 +msgid "Date" +msgstr "Tarih" -#: ../system/variables/ticket.rst:1 -#, fuzzy -msgid "Ticket > Customer > Avatar" -msgstr "Bilet > Müşteri > Faks" +#: ../system/subscription.rst:201 +msgid "Date of the invoice creation." +msgstr "" -#: ../system/variables/ticket.rst:1 +#: ../system/subscription.rst:204 #, fuzzy -msgid "``#{ticket.customer.avatar(60,60)}``" -msgstr "``#{ticket.customer.lastname}``" - -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Address" -msgstr "Bilet > Müşteri > Adres" +msgid "Amount" +msgstr "Hesaplar" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.address}``" -msgstr "``#{ticket.customer.address}``" +#: ../system/subscription.rst:204 +msgid "Invoice total including VAT if applicable." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Web" -msgstr "Bilet > Oluşturan > Web" +#: ../system/subscription.rst:207 +msgid "" +"Contains contract period (monthly or yearly) and hosted plan for the " +"subscription period in question." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.web}``" -msgstr "``#{ticket.created_by.web}``" +#: ../system/subscription.rst:218 +msgid "Payment method / Service period" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > VIP" -msgstr "Bilet > Oluşturan > VIP" +#: ../system/subscription.rst:211 +msgid "" +"Used bank account or credit card as well as the subscription period the " +"invoice is about." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.vip}``" -msgstr "``#{ticket.created_by.vip}``" +#: ../system/subscription.rst:216 +msgid "" +"It might happen that the invoice date and subscription period differ. This " +"is nothing to worry about, the subscription periods will be accounted later " +"on." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Phone" -msgstr "Bilet > Oluşturan > Telefon" +#: ../system/subscription.rst:222 +msgid "Receipt" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.phone}``" -msgstr "``#{ticket.created_by.phone}``" +#: ../system/subscription.rst:221 +msgid "" +"Use the arrow to download the invoice in question. You can download all " +"available invoices any time you need to here!" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Note" -msgstr "Bilet > Oluşturan > Not" +#: ../system/subscription.rst:None +msgid "Screenshot showing payment history of a hosted instance" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.note}``" -msgstr "``#{ticket.created_by.note}``" +#: ../system/subscription.rst:229 +msgid "FAQ" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Mobile" -msgstr "Bilet > Oluşturan > Mobil" +#: ../system/subscription.rst:233 +msgid "I set up a trial account but am missing functions to test" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.mobile}``" -msgstr "``#{ticket.created_by.mobile}``" +#: ../system/subscription.rst:232 +msgid "" +"The trial instance is running within the professional package allowing up to " +"three agents." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Login" -msgstr "Bilet > Oluşturan > Giriş" +#: ../system/subscription.rst:236 +msgid "Can I change package within the trial?" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.login}``" -msgstr "``#{ticket.created_by.login}``" +#: ../system/subscription.rst:236 +msgid "No. As soon as the package is changed the subscription begins." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Lastname" -msgstr "Bilet > Oluşturan > Soyadı" +#: ../system/subscription.rst:241 +msgid "What happens to my trial instance after the trial period ended?" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.lastname}``" -msgstr "``#{ticket.created_by.lastname}``" +#: ../system/subscription.rst:239 +msgid "" +"Your instance will automatically be canceled for you. Please see *What " +"happens to my instance after it has been canceled?* for more." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Firstname" -msgstr "Bilet > Oluşturan > Ad" +#: ../system/subscription.rst:254 +msgid "What happens to my instance after it has been canceled?" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.firstname}``" -msgstr "``#{ticket.created_by.firstname}``" +#: ../system/subscription.rst:244 +msgid "That depends slightly on your instance state:" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Fax" -msgstr "Bilet > Oluşturan > Faks" +#: ../system/subscription.rst:250 +#, fuzzy +msgid "Trial instance" +msgstr "Örneğin:" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.fax}``" -msgstr "``#{ticket.created_by.fax}``" +#: ../system/subscription.rst:247 +msgid "" +"If you're still on trial, we will ice your instance and remind you once " +"again about your instance. We then will wait some days and remove your " +"instance from our system. This is the last time we will inform you by Email." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Email" -msgstr "Bilet > Oluşturan > E-posta" +#: ../system/subscription.rst:254 +#, fuzzy +msgid "Paid instance" +msgstr "Örneğin:" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.email}``" -msgstr "``#{ticket.created_by.email}``" +#: ../system/subscription.rst:253 +msgid "" +"If you're a paying customer and canceled your subscription, the instance " +"removal will take place the day after your last subscription day." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Department" -msgstr "Bilet > Oluşturan > Bölüm" +#: ../system/subscription.rst:256 +msgid "Can removed instances be restored?" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.department}``" -msgstr "``#{ticket.created_by.department}``" +#: ../system/subscription.rst:257 +msgid "No. Once your instance has been removed, a restoration is not possible." +msgstr "" -#: ../system/variables/ticket.rst:1 +#: ../system/system-report.rst:2 #, fuzzy -msgid "Ticket > Created by > Avatar" -msgstr "Bilet > Oluşturan > Faks" +msgid "System Report" +msgstr "Filtreler" -#: ../system/variables/ticket.rst:1 -#, fuzzy -msgid "``#{ticket.created_by.avatar(60,60)}``" -msgstr "``#{ticket.created_by.lastname}``" +#: ../system/system-report.rst:4 +msgid "" +"In this place you can't configure Zammad. Instead you can obtain a system " +"report about Zammad and its configuration." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Address" -msgstr "Bilet > Oluşturan > Adres" +#: ../system/system-report.rst:7 +msgid "" +"See the description in Zammad for an explanation. You can even find a " +"preview of the included data below the **Download** button." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.address}``" -msgstr "``#{ticket.created_by.address}``" +#: ../system/system-report.rst:10 +msgid "" +"Zammad never sends this automatically to anyone. It is a manual process only " +"to provide better support based on your configuration." +msgstr "" + +#: ../system/translations.rst:2 +msgid "Translations" +msgstr "Çeviriler" + +#: ../system/translations.rst:4 +msgid "" +"Translations of Zammad are processed centrally in our `Weblate instance " +"`_. This allows non-developers to review " +"and update translation texts of the language they actually speak." +msgstr "" + +#: ../system/translations.rst:9 +msgid "" +"Your language is in an incomplete translation state or has typos? Please " +"consider helping us in sorting this out! All you need is either a GitHub " +"account or to register directly in our instance." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created at" -msgstr "Bilet > Oluşturulma" +#: ../system/translations.rst:13 +msgid "" +"Did you know? This is also where the documentation translations are handled. " +"🤓" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_at}``" -msgstr "``#{ticket.created_at}``" +#: ../system/translations.rst:15 +msgid "" +"Have a look in our :docs:`contribution section ` in the system documentation to get started!" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "2019-10-07 16:25:00 UTC" -msgstr "2019-10-07 16:25:00 UTC" +#: ../system/translations.rst:20 +#, fuzzy +msgid "Local Translations" +msgstr "Çeviriler" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Closing time" -msgstr "Bilet > Kapanma zamanı" +#: ../system/translations.rst:22 +msgid "" +"Apart from these system translations, there's still local translations you " +"can manage. This is relevant if you added custom objects that require " +"translations or even custom states and priorities." +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.close_at}``" -msgstr "``#{ticket.close_at}``" +#: ../system/translations.rst:None +msgid "Translation management screen within the admin menu" +msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "2019-10-07 17:25:00 UTC" -msgstr "2019-10-07 17:25:00 UTC" +#: ../system/translations.rst:31 +#, fuzzy +msgid "Updating Translations" +msgstr "Çeviriler" -#: ../system/variables/ticket.rst:1 -msgid "``3``, any number of articles existing in the ticket right now" -msgstr "``3``, şu anda bilette bulunan herhangi bir sayıda makale" +#: ../system/translations.rst:33 +msgid "" +"Because of how Zammad ships translations, the only way to update the system " +"translations is to update your Zammad installation. The benefit of this is " +"that you no longer need internet access during a Zammad upgrade as the " +"package has everything it requires already." +msgstr "" -#: ../system/version.rst:2 -msgid "Version" -msgstr "Versiyon" +#: ../system/translations.rst:39 +msgid "Translation of Custom Objects" +msgstr "" -#: ../system/version.rst:4 -msgid "Shows which version is currently being used on your Zammad-instance." -msgstr "Zammad örneğinizde şu anda hangi versiyonun kullanıldığını gösterir." +#: ../system/translations.rst:41 +msgid "" +"No problem at all! You can customize any translation locally, even if it is " +"not initially provided by the system." +msgstr "" -#: ../manage/roles/admin-permissions.rst:53 -#, fuzzy -msgid "``admin.checklist``" -msgstr "``admin.security``" +#: ../system/translations.rst:44 +msgid "" +"Translation is supported for a broad number of features, including but not " +"limited to custom:" +msgstr "" -#: ../manage/roles/admin-permissions.rst:54 +#: ../system/translations.rst:47 #, fuzzy -msgid ":doc:`Manage > Checklist `" -msgstr ":doc:`Yönetim > Metin Modülleri `" +msgid "Object Attributes" +msgstr "Bilet Nitelikleri" -#: ../manage/roles/admin-permissions.rst:83 +#: ../system/translations.rst:48 #, fuzzy -msgid "``admin.channel_whatsapp``" -msgstr "``admin.channel_chat``" +msgid "Ticket Macros" +msgstr "Makrolar Oluşturmak" -#: ../manage/roles/admin-permissions.rst:84 +#: ../system/translations.rst:49 #, fuzzy -msgid ":doc:`Channels > Whatsapp `" -msgstr ":doc:`Kanallar > Sohbet `" +msgid "Ticket Overviews" +msgstr "Genel Bakış" -#: ../manage/roles/admin-permissions.rst:124 +#: ../system/translations.rst:50 #, fuzzy -msgid "``admin.public_links``" -msgstr "``admin.api``" +msgid "Ticket Priorities" +msgstr "Bilet > Öncelik > Ad" -#: ../manage/roles/admin-permissions.rst:125 +#: ../system/translations.rst:51 #, fuzzy -msgid ":doc:`Manage > Public Links `" -msgstr ":doc:`Yönetim > Makrolar `" +msgid "Ticket States" +msgstr "Bilet > Durum > Ad" -#: ../manage/roles/admin-permissions.rst:151 +#: ../system/translations.rst:54 #, fuzzy -msgid "``admin.system_report``" -msgstr "``admin.tag``" +msgid "Customizing Translations" +msgstr "Çeviriler" -#: ../manage/roles/admin-permissions.rst:152 -#, fuzzy -msgid ":doc:`System > System Report `" -msgstr ":doc:`Sistem > Oturumlar `" +#: ../system/translations.rst:56 +msgid "" +"Within the translation screen, simply click on the **New Translation** " +"button." +msgstr "" -#: ../manage/roles/admin-permissions.rst:166 +#: ../system/translations.rst:None #, fuzzy -msgid "``admin.ticket_auto_assignment``" -msgstr "``admin.ticket``" +msgid "New translation dialog" +msgstr "Makale > Görünürlük" -#: ../manage/roles/admin-permissions.rst:167 -msgid ":ref:`Settings > Ticket > Auto Assignment `" +#: ../system/translations.rst:62 +msgid "" +"In the dialog you can immediately enter the exact translation source (if you " +"know it) and your custom translation text for it and click **Submit**." msgstr "" -#: ../manage/roles/admin-permissions.rst:169 -#, fuzzy -msgid "``admin.ticket_duplicate_detection``" -msgstr "``admin.text_module``" - -#: ../manage/roles/admin-permissions.rst:170 -msgid ":ref:`Settings > Ticket > Duplicate Detection `" +#: ../system/translations.rst:65 +msgid "" +"Alternatively, try to search for translation suggestions in the list below. " +"Selecting an item from the list will pre-fill the translation source for you " +"and then you can just enter your custom translation." msgstr "" -#: ../manage/roles/admin-permissions.rst:172 -#, fuzzy -msgid "``admin.ticket_priority``" -msgstr "``admin.ticket``" +#: ../system/translations.rst:69 +msgid "" +"The target language will always default to your current language selection. " +"If you need to translate for a different language, simply change the " +"selection before submitting." +msgstr "" -#: ../manage/roles/admin-permissions.rst:173 -msgid ":ref:`System > Objects >Ticket Priority `" +#: ../system/translations.rst:73 +msgid "" +"All your custom translations will show up in the overview table when added. " +"And they will even persist across Zammad updates!" msgstr "" -#: ../manage/roles/admin-permissions.rst:175 -#, fuzzy -msgid "``admin.ticket_state``" -msgstr "``admin.ticket``" +#: ../system/translations.rst:76 +msgid "" +"Make sure to reload your browser if a translated string is not displayed." +msgstr "" -#: ../manage/roles/admin-permissions.rst:176 -msgid ":ref:`System > Objects >Ticket State `" +#: ../system/translations.rst:80 +msgid "Reverting to Original Translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:193 -#, fuzzy -msgid "``admin.webhook``" -msgstr "``admin.role``" +#: ../system/translations.rst:82 +msgid "" +"If you want to revert a custom translation to original text, simply use the " +"appropriate action within the row of the overview table." +msgstr "" -#: ../manage/roles/admin-permissions.rst:194 -#, fuzzy -msgid ":doc:`Manage > Webhook `" -msgstr ":doc:`Yönetim > Makrolar `" +#: ../system/translations.rst:85 +msgid "" +"Depending on the type of the translation source, the action has a slightly " +"different name:" +msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:43 -#, fuzzy -msgid "``user_preferences.appearance``" -msgstr "``user_preferences.calendar``" +#: ../system/translations.rst:88 +msgid "**Reset** for customized system translations" +msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:44 -#, fuzzy -msgid "Appearance configuration" -msgstr "Yapılandırma" +#: ../system/translations.rst:89 +msgid "**Remove** for customized local translations" +msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:0 -msgid "Users can switch between dark, light and" +#: ../system/translations.rst:91 +msgid "" +"In both cases, the action will remove the customized translation after a " +"confirmation." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:0 -msgid "automatic mode." +#: ../system/translations.rst:None +msgid "Screenshot showing the location of the Remove action" msgstr "" -#: ../system/system-report.rst:2 +#: ../system/translations.rst:99 #, fuzzy -msgid "System Report" -msgstr "Filtreler" +msgid "Inline Translations" +msgstr "Çeviriler" -#: ../system/system-report.rst:4 +#: ../system/translations.rst:101 msgid "" -"In this place you can't configure Zammad. Instead you can obtain a system " -"report about Zammad and its configuration." +"If you prefer a more hands-on approach, you can activate the inline or on-" +"screen translation feature by pressing ``ctrl`` + ``alt`` + ``t`` at any " +"time and on any screen." msgstr "" -#: ../system/system-report.rst:7 +#: ../system/translations.rst:105 msgid "" -"See the description in Zammad for an explanation. You can even find a " -"preview of the included data below the **Download** button." +"All customizable translation texts will be highlighted for you on the " +"screen. Just click into the highlighted area and update the text in place." msgstr "" -#: ../system/system-report.rst:10 +#: ../system/translations.rst:None +msgid "Inline translation mode activated for the Overview screen" +msgstr "" + +#: ../system/translations.rst:112 msgid "" -"Zammad never sends this automatically to anyone. It is a manual process only " -"to provide better support based on your configuration." +"When finished editing, simply press ``ctrl`` + ``alt`` + ``t`` again to " +"deactivate." +msgstr "" + +#: ../system/translations.rst:117 +msgid "" +"Even though it's available on any screen, the inline translation feature " +"requires admin permissions. It works only for the current language " +"selection. If you need to translate a different language, first change the " +"language in your :user-docs:`profile settings `." msgstr "" +#: ../system/version.rst:2 +msgid "Version" +msgstr "Versiyon" + +#: ../system/version.rst:4 +msgid "Shows which version is currently being used on your Zammad-instance." +msgstr "Zammad örneğinizde şu anda hangi versiyonun kullanıldığını gösterir." + #~ msgid "" #~ "Please note that this part of our documentation currently is outdated. We " #~ "currently are working on solutions for this topic." diff --git a/locale/zh_Hans/LC_MESSAGES/admin-docs.po b/locale/zh_Hans/LC_MESSAGES/admin-docs.po index a43cf09c..48656989 100644 --- a/locale/zh_Hans/LC_MESSAGES/admin-docs.po +++ b/locale/zh_Hans/LC_MESSAGES/admin-docs.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Zammad\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-11-06 10:31+0100\n" +"POT-Creation-Date: 2024-11-12 16:31+0100\n" "PO-Revision-Date: 2023-08-14 12:18+0000\n" "Last-Translator: chen \n" "Language-Team: Chinese (Simplified) Checklist `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:56 msgid "``admin.channel_email``" msgstr "" -#: ../manage/roles/admin-permissions.rst:54 #: ../manage/roles/admin-permissions.rst:57 msgid ":doc:`Channels > Email `" msgstr "" -#: ../manage/roles/admin-permissions.rst:56 #: ../manage/roles/admin-permissions.rst:59 msgid "``admin.channel_facebook``" msgstr "" -#: ../manage/roles/admin-permissions.rst:57 #: ../manage/roles/admin-permissions.rst:60 msgid ":doc:`Channels > Facebook `" msgstr "" -#: ../manage/roles/admin-permissions.rst:58 #: ../manage/roles/admin-permissions.rst:61 msgid "" "Accessing Facebook tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:59 #: ../manage/roles/admin-permissions.rst:62 msgid "``admin.channel_formular``" msgstr "" -#: ../manage/roles/admin-permissions.rst:60 #: ../manage/roles/admin-permissions.rst:63 msgid ":doc:`Channels > Form `" msgstr "" -#: ../manage/roles/admin-permissions.rst:62 #: ../manage/roles/admin-permissions.rst:65 msgid "``admin.channel_google``" msgstr "" -#: ../manage/roles/admin-permissions.rst:63 #: ../manage/roles/admin-permissions.rst:66 msgid ":doc:`Channels > Google `" msgstr "" -#: ../manage/roles/admin-permissions.rst:65 #: ../manage/roles/admin-permissions.rst:68 msgid "``admin.channel_microsoft365``" msgstr "" -#: ../manage/roles/admin-permissions.rst:66 #: ../manage/roles/admin-permissions.rst:69 msgid ":doc:`Channels > Microsoft 365 `" msgstr "" -#: ../manage/roles/admin-permissions.rst:68 #: ../manage/roles/admin-permissions.rst:71 msgid "``admin.channel_sms``" msgstr "" -#: ../manage/roles/admin-permissions.rst:69 #: ../manage/roles/admin-permissions.rst:72 msgid ":doc:`Channels > SMS `" msgstr "" -#: ../manage/roles/admin-permissions.rst:71 #: ../manage/roles/admin-permissions.rst:74 msgid "``admin.channel_telegram``" msgstr "" -#: ../manage/roles/admin-permissions.rst:72 #: ../manage/roles/admin-permissions.rst:75 msgid ":doc:`Channels > Telegram `" msgstr "" -#: ../manage/roles/admin-permissions.rst:73 #: ../manage/roles/admin-permissions.rst:76 msgid "" "Accessing Telegram tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:74 #: ../manage/roles/admin-permissions.rst:77 msgid "``admin.channel_twitter``" msgstr "" -#: ../manage/roles/admin-permissions.rst:75 #: ../manage/roles/admin-permissions.rst:78 msgid ":doc:`Channels > Twitter `" msgstr "" -#: ../manage/roles/admin-permissions.rst:76 #: ../manage/roles/admin-permissions.rst:79 msgid "" "Accessing Twitter/X tickets for agents: :doc:`/manage/groups/access-levels`" msgstr "" -#: ../manage/roles/admin-permissions.rst:77 #: ../manage/roles/admin-permissions.rst:80 msgid "``admin.channel_web``" msgstr "" -#: ../manage/roles/admin-permissions.rst:78 #: ../manage/roles/admin-permissions.rst:81 msgid ":doc:`Channels > Web `" msgstr "" -#: ../manage/roles/admin-permissions.rst:80 +#: ../manage/roles/admin-permissions.rst:83 +msgid "``admin.channel_whatsapp``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:84 +msgid ":doc:`Channels > Whatsapp `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:86 msgid "``admin.core_workflows``" msgstr "" -#: ../manage/roles/admin-permissions.rst:81 #: ../manage/roles/admin-permissions.rst:87 msgid ":doc:`System > Core Workflows `" msgstr "" -#: ../manage/roles/admin-permissions.rst:83 #: ../manage/roles/admin-permissions.rst:89 msgid "``admin.data_privacy``" msgstr "" -#: ../manage/roles/admin-permissions.rst:84 #: ../manage/roles/admin-permissions.rst:90 msgid ":doc:`System > Data Privacy `" msgstr "" -#: ../manage/roles/admin-permissions.rst:85 #: ../manage/roles/admin-permissions.rst:91 msgid "" "🔥 Be careful, it allows users to permanently delete data on the system." msgstr "" -#: ../manage/roles/admin-permissions.rst:86 #: ../manage/roles/admin-permissions.rst:92 msgid "``admin.group``" msgstr "" -#: ../manage/roles/admin-permissions.rst:87 #: ../manage/roles/admin-permissions.rst:93 msgid ":doc:`Manage > Groups `" msgstr "" -#: ../manage/roles/admin-permissions.rst:89 #: ../manage/roles/admin-permissions.rst:95 msgid "``admin.integration``" msgstr "" -#: ../manage/roles/admin-permissions.rst:90 #: ../manage/roles/admin-permissions.rst:96 msgid ":doc:`System > Integrations `" msgstr "" -#: ../manage/roles/admin-permissions.rst:92 #: ../manage/roles/admin-permissions.rst:98 msgid "``admin.knowledge_base``" msgstr "" -#: ../manage/roles/admin-permissions.rst:93 #: ../manage/roles/admin-permissions.rst:99 msgid ":doc:`Manage > Knowledge Base `" msgstr "" @@ -8617,57 +8600,46 @@ msgid "" "knowledge-base.html#editing-answers>`." msgstr "" -#: ../manage/roles/admin-permissions.rst:98 #: ../manage/roles/admin-permissions.rst:104 msgid "``admin.macro``" msgstr "" -#: ../manage/roles/admin-permissions.rst:99 #: ../manage/roles/admin-permissions.rst:105 msgid ":doc:`Manage > Macros `" msgstr "" -#: ../manage/roles/admin-permissions.rst:100 #: ../manage/roles/admin-permissions.rst:106 msgid "In some cases, macros may also require ``admin.tag``" msgstr "" -#: ../manage/roles/admin-permissions.rst:101 #: ../manage/roles/admin-permissions.rst:107 msgid "``admin.maintenance``" msgstr "" -#: ../manage/roles/admin-permissions.rst:102 #: ../manage/roles/admin-permissions.rst:108 msgid ":doc:`System > Maintenance `" msgstr "" -#: ../manage/roles/admin-permissions.rst:104 #: ../manage/roles/admin-permissions.rst:110 msgid "``admin.monitoring``" msgstr "" -#: ../manage/roles/admin-permissions.rst:105 #: ../manage/roles/admin-permissions.rst:111 msgid ":doc:`System > Monitoring `" msgstr "" -#: ../manage/roles/admin-permissions.rst:107 #: ../manage/roles/admin-permissions.rst:113 msgid "``admin.object``" msgstr "" -#: ../manage/roles/admin-permissions.rst:108 #: ../manage/roles/admin-permissions.rst:114 msgid ":doc:`System > Objects `" msgstr "" -#: ../manage/roles/admin-permissions.rst:110 #: ../manage/roles/admin-permissions.rst:116 msgid "``admin.organization``" msgstr "" -#: ../manage/roles/admin-permissions.rst:111 #: ../manage/roles/admin-permissions.rst:117 msgid ":doc:`Manage > Organizations `" msgstr "" @@ -8684,202 +8656,211 @@ msgstr "" msgid "They can even edit an organization's name, domain, and notes!" msgstr "" -#: ../manage/roles/admin-permissions.rst:115 #: ../manage/roles/admin-permissions.rst:121 msgid "``admin.overview``" msgstr "" -#: ../manage/roles/admin-permissions.rst:116 #: ../manage/roles/admin-permissions.rst:122 msgid ":doc:`Manage > Overviews`" msgstr "" -#: ../manage/roles/admin-permissions.rst:118 +#: ../manage/roles/admin-permissions.rst:124 +msgid "``admin.public_links``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:125 +msgid ":doc:`Manage > Public Links `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:127 msgid "``admin.package``" msgstr "" -#: ../manage/roles/admin-permissions.rst:119 #: ../manage/roles/admin-permissions.rst:128 msgid ":doc:`System > Packages `" msgstr "" -#: ../manage/roles/admin-permissions.rst:121 #: ../manage/roles/admin-permissions.rst:130 msgid "``admin.report_profile``" msgstr "" -#: ../manage/roles/admin-permissions.rst:122 #: ../manage/roles/admin-permissions.rst:131 msgid ":doc:`Manage > Report Profiles `" msgstr "" -#: ../manage/roles/admin-permissions.rst:123 #: ../manage/roles/admin-permissions.rst:132 msgid "Access to view reports: ``report``" msgstr "" -#: ../manage/roles/admin-permissions.rst:124 #: ../manage/roles/admin-permissions.rst:133 msgid "``admin.role``" msgstr "" -#: ../manage/roles/admin-permissions.rst:125 #: ../manage/roles/admin-permissions.rst:134 msgid ":doc:`Manage > Roles `" msgstr "" -#: ../manage/roles/admin-permissions.rst:127 #: ../manage/roles/admin-permissions.rst:136 msgid "``admin.scheduler``" msgstr "" -#: ../manage/roles/admin-permissions.rst:128 #: ../manage/roles/admin-permissions.rst:137 msgid ":doc:`Manage > Scheduler `" msgstr "" -#: ../manage/roles/admin-permissions.rst:129 #: ../manage/roles/admin-permissions.rst:138 msgid "For automation on tickets" msgstr "" -#: ../manage/roles/admin-permissions.rst:130 #: ../manage/roles/admin-permissions.rst:139 msgid "``admin.security``" msgstr "" -#: ../manage/roles/admin-permissions.rst:131 #: ../manage/roles/admin-permissions.rst:140 msgid ":doc:`Settings > Security `" msgstr "" -#: ../manage/roles/admin-permissions.rst:132 #: ../manage/roles/admin-permissions.rst:141 msgid "Settings of Zammad. This also covers third party authentications." msgstr "" -#: ../manage/roles/admin-permissions.rst:133 #: ../manage/roles/admin-permissions.rst:142 msgid "``admin.session``" msgstr "" -#: ../manage/roles/admin-permissions.rst:134 #: ../manage/roles/admin-permissions.rst:143 msgid ":doc:`System > Sessions `" msgstr "" -#: ../manage/roles/admin-permissions.rst:136 #: ../manage/roles/admin-permissions.rst:145 msgid "``admin.setting_system``" msgstr "" -#: ../manage/roles/admin-permissions.rst:137 #: ../manage/roles/admin-permissions.rst:146 msgid ":doc:`Settings > System `" msgstr "" -#: ../manage/roles/admin-permissions.rst:139 #: ../manage/roles/admin-permissions.rst:148 msgid "``admin.sla``" msgstr "" -#: ../manage/roles/admin-permissions.rst:140 #: ../manage/roles/admin-permissions.rst:149 msgid ":doc:`Manage > SLAs `" msgstr "" -#: ../manage/roles/admin-permissions.rst:142 +#: ../manage/roles/admin-permissions.rst:151 +msgid "``admin.system_report``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:152 +msgid ":doc:`System > System Report `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:154 msgid "``admin.tag``" msgstr "" -#: ../manage/roles/admin-permissions.rst:143 #: ../manage/roles/admin-permissions.rst:155 msgid ":doc:`Manage > Tags `" msgstr "" -#: ../manage/roles/admin-permissions.rst:145 #: ../manage/roles/admin-permissions.rst:157 msgid "``admin.template``" msgstr "" -#: ../manage/roles/admin-permissions.rst:146 #: ../manage/roles/admin-permissions.rst:158 msgid ":doc:`Manage > Templates `" msgstr "" -#: ../manage/roles/admin-permissions.rst:148 #: ../manage/roles/admin-permissions.rst:160 msgid "``admin.text_module``" msgstr "" -#: ../manage/roles/admin-permissions.rst:149 #: ../manage/roles/admin-permissions.rst:161 msgid ":doc:`Manage > Text Modules `" msgstr "" -#: ../manage/roles/admin-permissions.rst:151 #: ../manage/roles/admin-permissions.rst:163 msgid "``admin.ticket``" msgstr "" -#: ../manage/roles/admin-permissions.rst:152 #: ../manage/roles/admin-permissions.rst:164 msgid ":doc:`Settings > Tickets `" msgstr "" -#: ../manage/roles/admin-permissions.rst:153 #: ../manage/roles/admin-permissions.rst:165 msgid "Does not grant access to :doc:`/misc/composer`" msgstr "" -#: ../manage/roles/admin-permissions.rst:154 +#: ../manage/roles/admin-permissions.rst:166 +msgid "``admin.ticket_auto_assignment``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:167 +msgid ":ref:`Settings > Ticket > Auto Assignment `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:169 +msgid "``admin.ticket_duplicate_detection``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:170 +msgid ":ref:`Settings > Ticket > Duplicate Detection `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:172 +#, fuzzy +msgid "``admin.ticket_priority``" +msgstr "优先级" + +#: ../manage/roles/admin-permissions.rst:173 +msgid ":ref:`System > Objects >Ticket Priority `" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:175 +msgid "``admin.ticket_state``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:176 +msgid ":ref:`System > Objects >Ticket State `" +msgstr "" + #: ../manage/roles/admin-permissions.rst:178 msgid "``admin.time_accounting``" msgstr "" -#: ../manage/roles/admin-permissions.rst:155 #: ../manage/roles/admin-permissions.rst:179 msgid ":doc:`Manage > Time Accounting `" msgstr "" -#: ../manage/roles/admin-permissions.rst:156 #: ../manage/roles/admin-permissions.rst:180 msgid "Also allows the export of timekeeping records." msgstr "" -#: ../manage/roles/admin-permissions.rst:157 #: ../manage/roles/admin-permissions.rst:181 msgid "``admin.translation``" msgstr "" -#: ../manage/roles/admin-permissions.rst:158 #: ../manage/roles/admin-permissions.rst:182 msgid ":doc:`System > Translations `" msgstr "" -#: ../manage/roles/admin-permissions.rst:159 #: ../manage/roles/admin-permissions.rst:183 msgid "Also enables inline translation" msgstr "" -#: ../manage/roles/admin-permissions.rst:160 #: ../manage/roles/admin-permissions.rst:184 msgid "``admin.trigger``" msgstr "" -#: ../manage/roles/admin-permissions.rst:161 #: ../manage/roles/admin-permissions.rst:185 msgid ":doc:`Manage > Triggers `" msgstr "" -#: ../manage/roles/admin-permissions.rst:163 #: ../manage/roles/admin-permissions.rst:187 msgid "``admin.user``" msgstr "" -#: ../manage/roles/admin-permissions.rst:164 #: ../manage/roles/admin-permissions.rst:188 msgid ":doc:`Manage > Users `" msgstr "" @@ -8898,6 +8879,14 @@ msgid "" "from-users-perspective>` ." msgstr "" +#: ../manage/roles/admin-permissions.rst:193 +msgid "``admin.webhook``" +msgstr "" + +#: ../manage/roles/admin-permissions.rst:194 +msgid ":doc:`Manage > Webhook `" +msgstr "" + #: ../manage/roles/agent-permissions.rst:2 msgid "Agent Permissions" msgstr "" @@ -9317,36 +9306,45 @@ msgid "than the user that generated them." msgstr "" #: ../manage/roles/user-preferences-permissions.rst:43 +msgid "``user_preferences.appearance``" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:44 +msgid "Appearance configuration" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "Users can switch between dark, light and" +msgstr "" + +#: ../manage/roles/user-preferences-permissions.rst:0 +msgid "automatic mode." +msgstr "" + #: ../manage/roles/user-preferences-permissions.rst:47 msgid "``user_preferences.avatar``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:44 #: ../manage/roles/user-preferences-permissions.rst:48 msgid "Avatar settings" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:45 #: ../manage/roles/user-preferences-permissions.rst:49 msgid "Override the default Gravatar with a custom avatar" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:46 #: ../manage/roles/user-preferences-permissions.rst:50 msgid "``user_preferences.calendar``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:47 #: ../manage/roles/user-preferences-permissions.rst:51 msgid "Configure the calendar feed" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:49 #: ../manage/roles/user-preferences-permissions.rst:53 msgid "``user_preferences.device``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:50 #: ../manage/roles/user-preferences-permissions.rst:54 msgid "Manage device login sessions" msgstr "" @@ -9363,22 +9361,18 @@ msgstr "" msgid "To learn more, see :doc:`/manage/trigger/system-notifications`." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:54 #: ../manage/roles/user-preferences-permissions.rst:58 msgid "``user_preferences.language``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:55 #: ../manage/roles/user-preferences-permissions.rst:59 msgid "Configure the UI locale/language" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:57 #: ../manage/roles/user-preferences-permissions.rst:61 msgid "``user_preferences.linked_accounts``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:58 #: ../manage/roles/user-preferences-permissions.rst:62 #, fuzzy msgid "Account linking" @@ -9403,7 +9397,6 @@ msgstr "" msgid "is the only way users can utilize third-party logins." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:63 #: ../manage/roles/user-preferences-permissions.rst:67 msgid "``user_preferences.notifications``" msgstr "" @@ -9431,7 +9424,6 @@ msgstr "" msgid "Customers can't receive ticket notifications at all." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:69 #: ../manage/roles/user-preferences-permissions.rst:73 msgid "``user_preferences.out_of_office``" msgstr "" @@ -9456,7 +9448,6 @@ msgstr "" msgid "they're replacing." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:75 #: ../manage/roles/user-preferences-permissions.rst:79 msgid "``user_preferences.overview_sorting``" msgstr "" @@ -9485,12 +9476,10 @@ msgstr "" msgid "overviews has no effect on custom orders." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:82 #: ../manage/roles/user-preferences-permissions.rst:86 msgid "``user_preferences.password``" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:83 #: ../manage/roles/user-preferences-permissions.rst:87 msgid "Change account password" msgstr "" @@ -9507,7 +9496,6 @@ msgstr "" msgid "your only allowed authentication method." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:87 #: ../manage/roles/user-preferences-permissions.rst:91 msgid "``user_preferences.two_factor_authentication``" msgstr "" @@ -9544,7 +9532,7 @@ msgstr "" #: ../manage/scheduler.rst:19 msgid "" -"Schedulers can be used to send periodic reminder emails. Use :doc:`/system/" +"Schedulers can be used to send periodic reminder emails. Use :doc:`/misc/" "variables` to build highly-customized email templates." msgstr "" @@ -10542,7 +10530,7 @@ msgstr "" #: ../manage/text-modules.rst:57 msgid "" -"The example text modules below use :doc:`/system/variables` to dynamically " +"The example text modules below use :doc:`/misc/variables` to dynamically " "insert information like the customer's or agent's names." msgstr "" @@ -10882,8 +10870,8 @@ msgstr "" #: ../misc/object-conditions/basics.rst:144 #: ../misc/object-conditions/basics.rst:160 #: ../misc/object-conditions/basics.rst:168 -#: ../misc/object-conditions/basics.rst:178 ../settings/ticket.rst:2 -#: ../system/variables/ticket.rst:2 +#: ../misc/object-conditions/basics.rst:178 ../misc/variables/ticket.rst:2 +#: ../settings/ticket.rst:2 msgid "Ticket" msgstr "" @@ -11118,7 +11106,7 @@ msgstr "" #: ../manage/trigger/how-do-they-work.rst:79 msgid "" -"Certain actions (such as *email*, *SMS* and *notes*) support :doc:`/system/" +"Certain actions (such as *email*, *SMS* and *notes*) support :doc:`/misc/" "variables`, which can be used to build highly-customized message templates." msgstr "" @@ -11147,7 +11135,7 @@ msgstr "" msgid "" "You can also combine static text with placeholders for text fields. Remember " "that the placeholders' values have to be known during trigger runtime. Learn " -"more about :doc:`/system/variables`." +"more about :doc:`/misc/variables`." msgstr "" #: ../manage/trigger/how-do-they-work.rst:105 @@ -12113,7 +12101,7 @@ msgstr "" msgid "" "When switched on, a code editor will be shown below, where you can configure " "custom payload for your webhook in JSON format. To insert supported :doc:`/" -"system/variables` use ``::`` or ``#{`` shortcuts for autocomplete." +"misc/variables` use ``::`` or ``#{`` shortcuts for autocomplete." msgstr "" #: ../manage/webhook/add.rst:103 @@ -14698,11964 +14686,11856 @@ msgid "" "powerful conditions with AND/OR relations." msgstr "" -#: ../settings/branding.rst:10 -msgid "Product Name" +#: ../misc/variables.rst:2 +msgid "Variables" msgstr "" -#: ../settings/branding.rst:7 +#: ../misc/variables.rst:4 msgid "" -"Defines the name of the application, shown in the web interface, tabs and " -"title bar of the web browser." +"Please note that this is just an overview of available variables. It might " +"be incomplete or variables might not be available within some functions. If " +"you're missing variables or are not sure if something is not working as " +"expected, feel free to ask over at the `Community `_." msgstr "" -#: ../settings/branding.rst:10 -msgid "Default value: ``Zammad Helpdesk``" +#: ../misc/variables.rst:10 +msgid "" +"Variables can be called by typing ``::`` (just like text modules in the " +"frontend), as long as you're in a supported text field within the backend. " +"Zammad will display all variables being available within this context and " +"replace it to the variable as soon as you selected an entry." msgstr "" -#: ../settings/branding.rst:13 -msgid "Will be shown in the app and is included in email footers." +#: ../misc/variables.rst:15 +msgid "" +"You have an empty field which you referenced and it appears as ``-``? That's " +"currently working as designed - you might want to ensure that these fields " +"always have a value." msgstr "" -#: ../settings/branding.rst:19 -msgid "Logo" +#: ../misc/variables.rst:20 +msgid "Variable Categories" msgstr "" -#: ../settings/branding.rst:16 -msgid "Defines the logo of the application, shown in the login page of Zammad." +#: ../misc/variables.rst:31 +msgid "Wait, What About Custom Objects?" msgstr "" -#: ../settings/branding.rst:18 +#: ../misc/variables.rst:33 msgid "" -"Ensure to hit the \"Submit\" button after uploading the logo. Otherwise your " -"change will not be saved." +"Good point! Of course, we can't predict what objects you might create, but " +"we can give you a hint on how to put the puzzle together to get your custom " +"values." msgstr "" -#: ../settings/branding.rst:22 +#: ../misc/variables.rst:36 msgid "" -"Allows to set the default language of the Zammad instance. The here defined " -"locale mostly acts as a fallback for:" +"For this, we'll talk about the inner part of the variable (so everything " +"within ``#{}``), please put the outer part around to have a valid variable. " +"The first part of the variable name consist of the object type. Currently " +"these are:" msgstr "" -#: ../settings/branding.rst:25 -msgid "user preferences (if Zammad can't detect the users locale)" +#: ../misc/variables.rst:41 +msgid "Ticket (``ticket``)" msgstr "" -#: ../settings/branding.rst:26 -msgid "CSV output (reporting, time accounting)" +#: ../misc/variables.rst:42 +msgid "User (``user``)" msgstr "" -#: ../settings/branding.rst:30 -msgid "Define the timezone of your Zammad installation." +#: ../misc/variables.rst:43 +msgid "Organization (``organization``)" msgstr "" -#: ../settings/branding.rst:32 +#: ../misc/variables.rst:44 +msgid "Group (``group``)" +msgstr "" + +#: ../misc/variables.rst:46 msgid "" -"This does not have any effect on timings for your agents or how Zammad " -"stores date and time values." +"The second part is the name of the attribute. This is the name you define " +"during object creation and can be found within the object attribute menu at " +"any time. The first and second part of a variable is divided by a point, e." +"g.: ``ticket.number`` which will in total be ``#{ticket.number}``." msgstr "" -#: ../settings/branding.rst:35 -msgid "Changing this value has direct consequences on the following areas:" +#: ../misc/variables.rst:51 +msgid "" +"Now, in some situations it's possible that you'll need to use a third part. " +"The best example for such a situation would be a ``select`` or ``tree-" +"select`` field which will by default return the key value, not it's display " +"name. For this, just extend your variable with ``.value``. This will result " +"in ``#{ticket.select.value}``." msgstr "" -#: ../settings/branding.rst:37 -msgid ":doc:`/manage/scheduler` tasks" +#: ../misc/variables.rst:60 +msgid "Using Translated Variables" msgstr "" -#: ../settings/branding.rst:38 -msgid "search indexing (and thus reporting)" +#: ../misc/variables.rst:62 +msgid "" +"If you want to use a translated variable in triggers or schedulers, you can " +"extend the placeholder like this: ``#{t(ticket.state.name)}``. The ``t`` " +"tells Zammad to search for fitting translated strings. The used output " +"language is based on the system language of Zammad which you can set in the " +"admin panel under :doc:`/settings/branding` or based on the selected locale " +"in the trigger/scheduler edit dialog." msgstr "" -#: ../settings/branding.rst:40 -msgid "calendar subscriptions" +#: ../misc/variables.rst:69 +msgid "" +"A possible use-case: you want to send your customers updates on tickets via " +"trigger or scheduler which should include the state of the ticket. Using the " +"default ``#{ticket.state.name}`` (without the translation flag ``t()``) " +"would lead to the output of the original (english) name of the state." msgstr "" -#: ../settings/branding.rst:41 -msgid "browser printing" +#: ../misc/variables.rst:75 +msgid "Date and Time Formatting" msgstr "" -#: ../settings/branding.rst:43 +#: ../misc/variables.rst:77 msgid "" -"Please note that some of above are fallbacks in case Zammad could not detect " -"the agents timezone correctly." +"The system (trigger/scheduler selected) locale and timezone predefines a " +"default format of date and timestamp. This format is customizable by using " +"the ``dt()`` method." msgstr "" -#: ../settings/branding.rst:77 -msgid "Pretty Date" +#: ../misc/variables.rst:79 +msgid "The method arguments are as follows:" msgstr "" -#: ../settings/branding.rst:47 -msgid "" -"This setting allows you to define how Zammad should display time stamps " -"within the interface to all users." +#: ../misc/variables.rst:81 +msgid "The date or timestamp variable you want to format." msgstr "" -#: ../settings/branding.rst:50 -msgid "" -"This does not have any effect on how Zammad returns e.g. time values via " -"variables." +#: ../misc/variables.rst:82 +msgid "The output format string." msgstr "" -#: ../settings/branding.rst:77 -msgid "Choose in between the following options:" +#: ../misc/variables.rst:83 +msgid "The timezone to apply (optional)." msgstr "" -#: ../settings/branding.rst:64 -msgid "relative" -msgstr "" +#: ../misc/variables.rst:85 +#: ../system/objects/external-data-source-example.rst:23 +#, fuzzy +msgid "**Example:**" +msgstr "例如" -#: ../settings/branding.rst:55 +#: ../misc/variables.rst:86 msgid "" -"This timestamp shows a relative time span until it switches to a date. Over " -"time, it will change as follows:" +"``#{dt(ticket.updated_at, \"%A %Y-%m-%d %H:%M in the office\", \"Europe/" +"Berlin\")}``" msgstr "" -#: ../settings/branding.rst:58 -msgid "just now" +#: ../misc/variables.rst:87 +msgid "Monday, 2024-03-18 15:31 in the office" msgstr "" -#: ../settings/branding.rst:59 -msgid "5 minutes ago" +#: ../misc/variables.rst:89 +msgid "" +"If you want to use our example, make sure to paste the string above without " +"formatting (``CTRL+Shift+v``), otherwise it won't work." msgstr "" -#: ../settings/branding.rst:60 -msgid "3 days 1 hour ago" +#: ../misc/variables.rst:93 +msgid "The following table lists available format directives:" msgstr "" -#: ../settings/branding.rst:61 -msgid "``03/04/2022``" +#: ../misc/variables.rst:99 +msgid "Parameter" msgstr "" -#: ../settings/branding.rst:63 -msgid "Hovering the timestamp helps, you'll always get a clean timestamp then." +#: ../misc/variables.rst:102 +msgid "``%Y``" msgstr "" -#: ../settings/branding.rst:71 -msgid "absolute" +#: ../misc/variables.rst:103 +msgid "Year with 4 digits" msgstr "" -#: ../settings/branding.rst:67 -msgid "" -"This timestamp always includes the week day. For one week after creation, " -"the timestamp will not contain the date itself: Thursday 18:35." +#: ../misc/variables.rst:104 +msgid "Use ``%y`` for year with 2 digits" msgstr "" -#: ../settings/branding.rst:71 -msgid "After a week it will switch to: ``Friday 4. Mar 16:00``." +#: ../misc/variables.rst:105 +msgid "``%m``" msgstr "" -#: ../settings/branding.rst:76 -msgid "timestamp" +#: ../misc/variables.rst:106 +msgid "Month of year (as number with zero-padding)" msgstr "" -#: ../settings/branding.rst:74 -msgid "" -"This will cause Zammad to show a complete timestamp according to your locale " -"defaults. For English this could be e.g. ``2022/12/03 2:40 pm`` or for " -"German e.g. ``12.03.2022 14:40``." +#: ../misc/variables.rst:107 +msgid "Use ``%-m`` for month without zero-padding" msgstr "" -#: ../settings/branding.rst:78 -msgid "Default setting: ``relative``." +#: ../misc/variables.rst:108 +msgid "``%d``" msgstr "" -#: ../settings/security.rst:2 -msgid "Security" +#: ../misc/variables.rst:109 +msgid "Day of month (as number with zero-padding)" msgstr "" -#: ../settings/security.rst:4 -msgid "" -"For your overview we split each tab within security settings into its own " -"page:" +#: ../misc/variables.rst:110 +msgid "Use ``%e`` for day without zero-padding" msgstr "" -#: ../settings/security/base.rst:2 ../settings/system/base.rst:2 -#: ../settings/ticket.rst:8 -msgid "Base" +#: ../misc/variables.rst:111 +msgid "``%H``" msgstr "" -#: ../settings/security/base.rst:5 -msgid "New User Accounts" +#: ../misc/variables.rst:112 +msgid "Hour of day in 24h notation with zero-padding" msgstr "" -#: ../settings/security/base.rst:9 -msgid "" -"Activates the `register as a new customer` function on the login page. If " -"set to ``no`` only administrators or agents can create new accounts manually." +#: ../misc/variables.rst:113 +msgid "Use ``%k`` for hour without zero-padding" msgstr "" -#: ../settings/security/base.rst:13 ../settings/security/base.rst:38 -#: ../settings/security/base.rst:66 -msgid "Default setting: ``yes``" +#: ../misc/variables.rst:114 +msgid "``%I``" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing activated \"New User Accounts\" setting" +#: ../misc/variables.rst:115 +msgid "Hour of day in 12h notation with zero-padding" msgstr "" -#: ../settings/security/base.rst:22 +#: ../misc/variables.rst:116 msgid "" -"Deactivation of above function **does not** deactivate automatic account " -"creation! This means: If a user writes e.g. an email to Zammad and has no " -"account yet, Zammad will automatically create the account. User accounts are " -"a direct dependency of tickets and thus technically mandatory." +"Use ``%l`` for hour without zero-padding and ``%p`` / ``%P`` for meridian " +"indicator" msgstr "" -#: ../settings/security/base.rst:29 -msgid "Lost Password" +#: ../misc/variables.rst:117 +msgid "``%M``" msgstr "" -#: ../settings/security/base.rst:33 -msgid "" -"Activates the `lost password` function on the login page. If set to ``no`` " -"only administrators may change the user's password - users may update their " -"own password if they're still logged in and they have the required :doc:" -"`permission `." +#: ../misc/variables.rst:118 +msgid "Minute of hour" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing activated \"Lost Password\" setting" +#: ../misc/variables.rst:120 +msgid "``%S``" msgstr "" -#: ../settings/security/base.rst:49 -msgid "" -"With third party authentications - but especially LDAP - you may want to " -"disable this function. Zammad **will not** change third party login " -"passwords and instead set or change the local password!" +#: ../misc/variables.rst:121 +msgid "Second of Minute" msgstr "" -#: ../settings/security/base.rst:56 -msgid "Password Login" +#: ../misc/variables.rst:123 +msgid "``%A``" msgstr "" -#: ../settings/security/base.rst:60 -msgid "" -"Activates the username & password login by default and if no third-party " -"login is activated. Disabling password login on the Zammad login page only " -"takes effect if you enable any :doc:`third-party`." +#: ../misc/variables.rst:124 +msgid "Weekday name" msgstr "" -#: ../settings/security/base.rst:64 -msgid "See :doc:`third-party` for supported third-party logins." +#: ../misc/variables.rst:125 +msgid "Use ``%a`` for abbreviated name or ``%^A`` for uppercase name" msgstr "" -#: ../settings/security/base.rst:0 -msgid "Figure showing de-activated \"Password Login\" setting" +#: ../misc/variables.rst:126 +msgid "``%B``" msgstr "" -#: ../settings/security/base.rst:77 -msgid "" -"To help administrators to overcome \"login issues\", Zammad automatically " -"offers a password request for administrator users. This allows you to adjust " -"Third-Party applications even if the login does no longer work!" +#: ../misc/variables.rst:127 +msgid "Month name" msgstr "" -#: ../settings/security/base.rst:84 -msgid "Session Timeout" +#: ../misc/variables.rst:128 +msgid "Use ``%b`` for abbreviated name" msgstr "" -#: ../settings/security/base.rst:86 -msgid "" -"All settings below by default are set to ``4 weeks``. Session Timeout " -"defines the life time of a users session. As soon as it's reached, Zammad " -"will automatically log off the session in question." +#: ../misc/variables.rst:129 +msgid "``%U``" msgstr "" -#: ../settings/security/base.rst:91 -msgid "" -"Zammad takes the highest value set assigned for the user based on the " -"permissions." +#: ../misc/variables.rst:130 +msgid "Week number of current year" msgstr "" -#: ../settings/security/base.rst:94 -msgid "``admin``" +#: ../misc/variables.rst:131 +msgid "Use ``%W`` for a different calculation method" msgstr "" -#: ../settings/security/base.rst:96 -msgid "``ticket.customer``" +#: ../misc/variables.rst:134 +msgid "" +"We support the known format directives for the Ruby built-in method " +"``strftime`` of the ``DateTime`` class. For more information, see `here " +"`_." msgstr "" -#: ../settings/security/base.rst:97 -msgid "``default`` (fallback if user doesn't have above permissions set)" +#: ../misc/variables/article.rst:2 +msgid "Articles" msgstr "" -#: ../settings/security/base.rst:99 +#: ../misc/variables/article.rst:4 ../misc/variables/config.rst:4 +#: ../misc/variables/current-user.rst:4 ../misc/variables/ticket.rst:4 msgid "" -"All settings act independently from each other allowing you to disable the " -"timeouts for e.g. admins, but not agents." +"If you're missing variables or are not sure if something is not working as " +"expected, feel free to ask over at the `Community `_." msgstr "" -#: ../settings/security/base.rst:115 -#: ../system/integrations/checkmk/api-reference.rst:13 -msgid "Example" -msgstr "例如" +#: ../misc/variables/article.rst:6 +msgid "" +"Below you can find all available ticket article-based variables within " +"Zammad. These can be called via triggers for example. If you're unsure if " +"Zammad does support variables at the point you're at, you can try to type " +"``::`` to check." +msgstr "" -#: ../settings/security/base.rst:107 -msgid "Let's suppose you configured the following session timeouts" +#: ../misc/variables/article.rst:9 ../misc/variables/config.rst:9 +#: ../misc/variables/ticket.rst:9 +msgid "" +"The below list gives you an example what kind of data you can expect, it's " +"not intended to explain the data itself." msgstr "" -#: ../settings/security/base.rst:104 -msgid "default: 3 weeks" +#: ../misc/variables/article.rst:11 +msgid "Article Variables" msgstr "" -#: ../settings/security/base.rst:105 -msgid "admin: 2 weeks" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "name" msgstr "" -#: ../settings/security/base.rst:106 -msgid "ticket.agent: 4 weeks" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "variable" msgstr "" -#: ../settings/security/base.rst:107 -msgid "ticket.customer: 1 week" +#: ../misc/variables/article.rst:1 ../misc/variables/config.rst:1 +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "example" msgstr "" -#: ../settings/security/base.rst:115 -msgid "This results in the following situations" +#: ../misc/variables/article.rst:1 +msgid "Article > Cc" msgstr "" -#: ../settings/security/base.rst:110 -msgid "a user with ``admin`` permission will have a timeout of 2 weeks" +#: ../misc/variables/article.rst:1 +msgid "``#{article.cc}``" msgstr "" -#: ../settings/security/base.rst:111 -msgid "" -"a user with ``admin`` and ``ticket.agent`` permissions will have a timeout " -"of 2 weeks" +#: ../misc/variables/article.rst:1 +msgid "``jdoe@example.com, company@example.com``" msgstr "" -#: ../settings/security/base.rst:113 -msgid "" -"a user with ``ticket.customer`` permission will have a timeout of 1 week" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Address" msgstr "" -#: ../settings/security/base.rst:115 -msgid "" -"a user with neither ``admin``, ``ticket.agent`` nor ``ticket.customer`` " -"permissions will have a timeout of 3 weeks" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.address}``" msgstr "" -#: ../settings/security/password.rst:4 -msgid "" -"This section allows you to define password requirements for the local user " -"accounts." +#: ../misc/variables/article.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:9 -msgid "" -"Zammad does **not** allow you to change your LDAP password, instead, it will " -"set a password in its local database which might confuse your users. This " -"might be addressed in the future by `#1169 `_." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Department" msgstr "" -#: ../settings/security/password.rst:14 -msgid "**Exception for admins**" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.department}``" msgstr "" -#: ../settings/security/password.rst:16 -msgid "" -"Please note that below password policies *do not* affect administrators " -"setting passwords on user accounts. While this seems strange and not safe we " -"believe that an administrator knowing an user's password is insecure as well." +#: ../misc/variables/article.rst:1 +msgid "``Sales`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:21 -msgid "The suggested workflow is either:" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Email" msgstr "" -#: ../settings/security/password.rst:23 -msgid "" -"to use third party logins to not require local passwords at all **- or -**" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.email}``" msgstr "" -#: ../settings/security/password.rst:25 -msgid "to require your *user to reset the password* upon first login." +#: ../misc/variables/article.rst:1 +msgid "``jdoe@example.com``" msgstr "" -#: ../settings/security/password.rst:27 -msgid "" -"This way administrators are not required to set a user's password at all!" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Fax" msgstr "" -#: ../settings/security/password.rst:31 -msgid "Maximum Failed Logins" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.fax}``" msgstr "" -#: ../settings/security/password.rst:33 -msgid "" -"You can choose a value between ``4`` and ``20``. This defines how often a " -"login to a user account may fail until Zammad will lock it. Your users can " -"always use the \"forgot password\" function to change their password and " -"unlock their account." +#: ../misc/variables/article.rst:1 +msgid "``+4930123456789`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:38 -msgid "The default value is ``10``." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Firstname" msgstr "" -#: ../settings/security/password.rst:42 -msgid "Beside changing the user's password, you can also unlock accounts via" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.firstname}``" msgstr "" -#: ../settings/security/password.rst:44 -msgid ":ref:`user management list `" +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Joe`` or empty if not set" msgstr "" -#: ../settings/security/password.rst:45 -msgid ":docs:`console `" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Lastname" msgstr "" -#: ../settings/security/password.rst:46 -msgid ":docs:`API `" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.lastname}``" msgstr "" -#: ../settings/security/password.rst:50 -msgid "Failed logins via LDAP no longer lock accounts." +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +#: ../misc/variables/ticket.rst:1 +msgid "``Doe`` or empty if not set" msgstr "" -#: ../settings/security/password.rst:53 -msgid "2 Lower Case And 2 Upper Case Characters" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Login" msgstr "" -#: ../settings/security/password.rst:55 -msgid "" -"You can add complexity to passwords by enforcing at least 2 upper and lower " -"case characters." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.login}``" msgstr "" -#: ../settings/security/password.rst:58 ../settings/security/password.rst:83 -msgid "The default value is ``no``." +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +#: ../misc/variables/ticket.rst:1 +msgid "``jdoe``" msgstr "" -#: ../settings/security/password.rst:62 -msgid "Minimum Length" +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Mobile" msgstr "" -#: ../settings/security/password.rst:64 -msgid "" -"This defines the minimum password length required for users to provide (from " -"``4`` to ``20``)." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.mobile}``" msgstr "" -#: ../settings/security/password.rst:67 -msgid "The default value is ``6``." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Note" msgstr "" -#: ../settings/security/password.rst:71 -msgid "Digit Required" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.note}``" msgstr "" -#: ../settings/security/password.rst:73 -msgid "This enforces your users to use at least one digit within the password." +#: ../misc/variables/article.rst:1 +msgid "``Some note about user`` or empty if not set in user object" msgstr "" -#: ../settings/security/password.rst:75 -msgid "The default value is ``yes``." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Phone" msgstr "" -#: ../settings/security/password.rst:78 -msgid "Special Character Required" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.phone}``" msgstr "" -#: ../settings/security/password.rst:80 -msgid "" -"This setting allows you to improve your password quality even more by " -"enforcing the password to contain at least one special character." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > VIP" msgstr "" -#: ../settings/security/ssl-certificates.rst:2 -msgid "SSL Certificates" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.vip}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:7 -msgid "" -"Zammad offers the possibility to upload custom certificates and custom " -"Certificate Authority (CA) certificates. This can be useful if you want to " -"connect Zammad the secure way to other systems which are using custom " -"certificates." +#: ../misc/variables/article.rst:1 ../misc/variables/current-user.rst:1 +msgid "``true`` or ``false``" msgstr "" -#: ../settings/security/ssl-certificates.rst:12 -msgid "" -"An example usecase might be: You have an internal LDAP server that is not " -"accessible from the internet, and you want a SSL-encrypted connection, using " -"a custom certificate." +#: ../misc/variables/article.rst:1 +msgid "Article > Created by > Web" msgstr "" -#: ../settings/security/ssl-certificates.rst:19 -msgid "" -"You should have an existing custom certificate file and/or a custom CA " -"certificate file, which you want to add to Zammad. As filetype ``.crt`` is " -"supported and the certificate format has to be PEM (Base64 ASCII)." +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_by.web}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:25 -msgid "" -"When you import a custom CA certificate, all certificates generated with " -"this are trusted. This can be useful if you have more than one system/" -"certificate you want to connect to and the certificates are issued from the " -"same custom CA." +#: ../misc/variables/article.rst:1 +msgid "``https://zammad.com`` or empty if not set in user object" msgstr "" -#: ../settings/security/ssl-certificates.rst:31 -msgid "Add a Certificate" +#: ../misc/variables/article.rst:1 +msgid "Article > Created" msgstr "" -#: ../settings/security/ssl-certificates.rst:33 -msgid "" -"To add a custom certificate or a custom CA certificate, head over to the " -"Admin panel > Settings > Security > SSL Certificates. Here you can find a " -"\"Add SSL Certificate\" button. In the dialog you can either select a " -"certificate file or paste the content of the certificate:" +#: ../misc/variables/article.rst:1 +msgid "``#{article.created_at}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate adding dialog" +#: ../misc/variables/article.rst:1 +msgid "``2019-10-08 15:24:47 UTC``" msgstr "" -#: ../settings/security/ssl-certificates.rst:43 -msgid "" -"After selecting a file or pasting the content of the certificate, click on " -"the \"Add\" button to finally upload it to Zammad. Then, the certificates " -"are immediately effective, no restart or similar required." +#: ../misc/variables/article.rst:1 +msgid "Article > From" msgstr "" -#: ../settings/security/ssl-certificates.rst:49 -msgid "" -"Please note that only single certificate files are supported. That means if " -"you want to import a certificate / CA certificate, it must contain **only " -"one** certificate." +#: ../misc/variables/article.rst:1 +msgid "``#{article.from}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:54 -msgid "Certificate Overview" +#: ../misc/variables/article.rst:1 +msgid "" +"``Joe Doe `` may differ, depends on ``FROM`` of send mail" msgstr "" -#: ../settings/security/ssl-certificates.rst:56 -msgid "" -"After you added a certificate, you can see a table with information for each " -"added certificate:" +#: ../misc/variables/article.rst:1 +msgid "Article > Sender > Name" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing table of added certificates" +#: ../misc/variables/article.rst:1 +msgid "``#{article.sender.name}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:64 -msgid "" -"Here you can download the certificate or delete it, if you don't need it " -"anymore." +#: ../misc/variables/article.rst:1 +msgid "``Customer``, ``Agent`` or ``System``" msgstr "" -#: ../settings/security/ssl-certificates.rst:68 -msgid "Deleting Certificates" +#: ../misc/variables/article.rst:1 +msgid "Article > Subject" msgstr "" -#: ../settings/security/ssl-certificates.rst:70 -msgid "" -"If you want to delete a specific certificate, you can do it by clicking on " -"the menu in the actions column and selecting delete:" +#: ../misc/variables/article.rst:1 +msgid "``#{article.subject}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate deletion button" +#: ../misc/variables/article.rst:1 +msgid "``My amazing subject``" msgstr "" -#: ../settings/security/ssl-certificates.rst:79 -msgid "Downloading Certificates" +#: ../misc/variables/article.rst:1 +msgid "Article > Text" msgstr "" -#: ../settings/security/ssl-certificates.rst:81 -msgid "" -"If you want to download your certificates, you can do this as well via " -"corresponding action buttons." +#: ../misc/variables/article.rst:1 +msgid "``#{article.body}``" msgstr "" -#: ../settings/security/ssl-certificates.rst:None -msgid "Screenshot showing certificate download button" +#: ../misc/variables/article.rst:1 +msgid "``Test`` without formatting (plain)" msgstr "" -#: ../settings/security/third-party.rst:13 -msgid "Login Providers" +#: ../misc/variables/article.rst:1 +msgid "Article > TicketID" msgstr "" -#: ../settings/security/third-party.rst:2 -msgid "Third-Party Applications" +#: ../misc/variables/article.rst:1 +msgid "``#{article.ticket_id}``" msgstr "" -#: ../settings/security/third-party.rst:4 -msgid "" -"Third party authentication is a great way to help your users to login to " -"Zammad more easily. If the account is yet unknown, Zammad will create a new " -"user automatically, without the user needed to interact (e.g. type in his " -"name). Another big advantage of this feature is that your user doesn't need " -"to remember another password." +#: ../misc/variables/article.rst:1 +msgid "``1`` (not ticket number)" msgstr "" -#: ../settings/security/third-party.rst:10 -msgid "" -"You can deactivate logging in via :ref:`security_password_login` if any of " -"the mentioned authentication providers are enabled in your instance." +#: ../misc/variables/article.rst:1 +msgid "Article > To" msgstr "" -#: ../settings/security/third-party.rst:27 -msgid "" -"We're currently missing documentation for the following login providers:" +#: ../misc/variables/article.rst:1 +msgid "``#{article.to}``" msgstr "" -#: ../settings/security/third-party.rst:29 -msgid "LinkedIn" +#: ../misc/variables/article.rst:1 +msgid "``helpdesk@example.com``" msgstr "" -#: ../settings/security/third-party.rst:30 -msgid "Weibo" +#: ../misc/variables/article.rst:1 +msgid "Article > Type > Name" msgstr "" -#: ../settings/security/third-party.rst:35 -msgid "Automatic Account Link on Initial Logon" +#: ../misc/variables/article.rst:1 +msgid "``#{article.type.name}``" msgstr "" -#: ../settings/security/third-party.rst:37 +#: ../misc/variables/article.rst:1 msgid "" -"In general there's two possible options for Zammad on how to deal with " -"already known users as they try to authenticate against a third-party " -"application. By default, Zammad will not automatically link \"unknown\" " -"authentication providers to existing accounts." +"``email`` (`list of article types `_)" msgstr "" -#: ../settings/security/third-party.rst:42 -msgid "" -"This means that the user has to manually link authentication providers to " -"their accounts (for more about this :user-docs:`consult the user " -"documentation `)." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Address" msgstr "" -#: ../settings/security/third-party.rst:46 -msgid "" -"Sometimes this doesn't come in handy as this also means you'll receive error " -"messages about \"email address being in use already\" for (yet) unknown " -"third-party authentication methods." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.address}``" msgstr "" -#: ../settings/security/third-party.rst:50 -msgid "" -"If you want to allow your users to always be able to log in, no matter what, " -"you may want to enable ``Automatic account link on initial logon``." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Department" msgstr "" -#: ../settings/security/third-party.rst:None -msgid "" -"Screenshot highlighting the \"Automatic account link on initial logon\"\n" -"setting" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.department}``" msgstr "" -#: ../settings/security/third-party.rst:60 -msgid "Automatic Account Linking Notification" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Email" msgstr "" -#: ../settings/security/third-party.rst:64 -msgid "" -"To improve security and your users awareness, you can enable Zammad to " -"notify your users when a new third-party application has been linked to " -"their account." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.email}``" msgstr "" -#: ../settings/security/third-party.rst:68 -msgid "" -"This notification is sent out once per third-party application. Zammad does " -"also mention the method used, e.g.: ``Microsoft``." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Fax" msgstr "" -#: ../settings/security/third-party.rst:71 -msgid "By default this setting is not active (set to ``no``)." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.fax}``" msgstr "" -#: ../settings/security/third-party.rst:0 -msgid "" -"Screenshot showing sample notification mail after initial\n" -"third-party linking" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Firstname" msgstr "" -#: ../settings/security/third-party.rst:85 -msgid "" -"This notification is only sent if the account in question already exists. If " -"the login via the third-party also creates the missing account, the " -"notification will be skipped." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.firstname}``" msgstr "" -#: ../settings/security/third-party.rst:89 -msgid "This means it only affects:" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Lastname" msgstr "" -#: ../settings/security/third-party.rst:91 -msgid "manual account linking within the third-party page of the users profile" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.lastname}``" msgstr "" -#: ../settings/security/third-party.rst:92 -msgid "" -"logging into an existing local account by utilizing the *automatic account " -"link on initial logon* functionality" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Login" msgstr "" -#: ../settings/security/third-party.rst:None -msgid "" -"Screenshot showing the \"automatic account linking notification\"\n" -"setting" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.login}``" msgstr "" -#: ../settings/security/third-party.rst:100 -msgid "No User Creation on Logon" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Mobile" msgstr "" -#: ../settings/security/third-party.rst:102 -msgid "" -"By default, Zammad will create a new user account if the user logs in via a " -"third-party application and the account doesn't exist yet." +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.mobile}``" msgstr "" -#: ../settings/security/third-party.rst:105 -msgid "" -"If you want to prevent Zammad from creating new accounts on logon, you can " -"disable this feature by setting ``No user creation on logon`` to ``yes``." +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Note" msgstr "" -#: ../settings/security/third-party.rst:None -msgid "Screenshot showing the \"no user creation on logon\" setting" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.note}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via Facebook To do " -"so, you need to follow these steps:" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Phone" msgstr "" -#: ../settings/security/third-party/facebook.rst:9 -msgid "Register Facebook App" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.phone}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:11 -msgid "" -"Visit [https://developers.facebook.com/apps/] and click on \"Add a new App\"" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > VIP" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "initial page" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.vip}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:17 -msgid "After that enter the app settings" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated by > Web" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "Create App" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_by.web}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:22 -msgid "Navigate to \"Settings\" and fill in this infromation" +#: ../misc/variables/article.rst:1 +msgid "Article > Updated" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "App Settings" +#: ../misc/variables/article.rst:1 +msgid "``#{article.updated_at}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:27 -msgid "Navigate to app review and Check \"Make [appname] public?\"" +#: ../misc/variables/article.rst:1 +msgid "Article > Visibility" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "App Review" +#: ../misc/variables/article.rst:1 +msgid "``#{article.internal}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:35 -msgid "Configure Zammad as Facebook App" +#: ../misc/variables/article.rst:1 +msgid "``false`` or ``true`` (false if not internal)" msgstr "" -#: ../settings/security/third-party/facebook.rst:37 -msgid "" -"Navigate to \"Admin -> Security -> Third Party Applications\" and enter the " -"App ID and the App Secret. You can find this Key in the Dashbard of your " -"Facebok app." +#: ../misc/variables/article.rst:1 +msgid "Article Text as HTML (not referenced)" msgstr "" -#: ../settings/security/third-party/facebook.rst:None -msgid "Zammad Configuration" +#: ../misc/variables/article.rst:1 +msgid "``#{article.body_as_html}``" msgstr "" -#: ../settings/security/third-party/facebook.rst:44 -#: ../settings/security/third-party/github.rst:43 -#: ../settings/security/third-party/gitlab.rst:46 -msgid "" -"Now you can link accounts via \"Avatar -> Profile -> Link Accounts\" or " -"login via Zammad login page." +#: ../misc/variables/article.rst:1 +msgid "``Test`` with formatting" msgstr "" -#: ../settings/security/third-party/github.rst:2 -#: ../system/integrations/github.rst:2 -msgid "GitHub" +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "Ticket > Article#" msgstr "" -#: ../settings/security/third-party/github.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via GitHub. To " -"activate the quick login you need to enable OAuth for GitHub." +#: ../misc/variables/article.rst:1 ../misc/variables/ticket.rst:1 +msgid "``#{ticket.article_count}``" msgstr "" -#: ../settings/security/third-party/github.rst:8 -msgid "Register GitHub App" +#: ../misc/variables/article.rst:1 +msgid "``1`` number of ticket articles" msgstr "" -#: ../settings/security/third-party/github.rst:10 -msgid "" -"Visit https://www.github.com/settings/applications/new and enter the app " -"settings. As callback URL enter \"https://zammad_host/auth/github/callback\" " -"where zammad_host has to be replaced with your Zammad FQDN" +#: ../misc/variables/config.rst:2 +msgid "Config" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "Register OAuth app on www.github.com" +#: ../misc/variables/config.rst:6 +msgid "" +"Below you'll find config related variables. These hold useful configuration " +"information that you can use within e.g. triggers to show necessary " +"information to your customer." msgstr "" -#: ../settings/security/third-party/github.rst:19 -msgid "Configure Zammad as GitHub App" +#: ../misc/variables/config.rst:11 +msgid "Config Variables" msgstr "" -#: ../settings/security/third-party/github.rst:21 -msgid "" -"Enter the \"APP ID\" and the \"APP SECRET\" from the GitHub OAUTH " -"Applications Dashboard" +#: ../misc/variables/config.rst:1 +msgid "Config > Fully Qualified Domain Name" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub config in Zammad admin interface" +#: ../misc/variables/config.rst:1 +msgid "``#{config.fqdn}``" msgstr "" -#: ../settings/security/third-party/github.rst:28 -msgid "" -"After you configured the GitHub credentials and activated the login method, " -"you should see a new icon on the login page." +#: ../misc/variables/config.rst:1 +msgid "``zammad.example.com``" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub logo on login page" +#: ../misc/variables/config.rst:1 +msgid "Config > HTTP type" msgstr "" -#: ../settings/security/third-party/github.rst:34 -msgid "" -"If you click on the icon you will be redirected to GitHub and see something " -"similar to this:" +#: ../misc/variables/config.rst:1 +msgid "``#{config.http_type}``" msgstr "" -#: ../settings/security/third-party/github.rst:None -msgid "GitHub oauth page" +#: ../misc/variables/config.rst:1 +msgid "``https`` or ``http``" msgstr "" -#: ../settings/security/third-party/github.rst:40 -#: ../settings/security/third-party/gitlab.rst:42 -msgid "" -"When you grant the access you will be redirected to your Zammad instance and " -"logged in as a customer." +#: ../misc/variables/config.rst:1 +msgid "Config > Organization" msgstr "" -#: ../settings/security/third-party/gitlab.rst:2 -msgid "Gitlab" +#: ../misc/variables/config.rst:1 +msgid "``#{config.organization}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:4 +#: ../misc/variables/config.rst:1 msgid "" -"It is possible to create a quick login for your helpdesk via Gitlab. To " -"activate the quick login you need to enable OAuth for Gitlab." +"``Zammad GmbH`` value set in `Branding `_" msgstr "" -#: ../settings/security/third-party/gitlab.rst:8 -msgid "Register Gitlab App" +#: ../misc/variables/config.rst:1 +msgid "Config > Product Name" msgstr "" -#: ../settings/security/third-party/gitlab.rst:10 -msgid "To register an app in Gitlab open your profile and select applications." +#: ../misc/variables/config.rst:1 +msgid "``#{config.product_name}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:12 +#: ../misc/variables/config.rst:1 msgid "" -"As callback URL enter \"https://zammad-fqdn/auth/gitlab/callback\" where " -"zammad-fqdn has to be replaced with your Zammad FQDN" +"``Helpdesk`` value set in `Branding `_" msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Register OAuth app on gitlab instance" +#: ../misc/variables/config.rst:1 +msgid "Config > SystemID" msgstr "" -#: ../settings/security/third-party/gitlab.rst:18 -msgid "Just select *read_user* under scopes as in the screenshot and save it." +#: ../misc/variables/config.rst:1 +msgid "``#{config.system_id}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:21 -msgid "Configure Zammad as Gitlab App" +#: ../misc/variables/config.rst:1 +msgid "``31`` (value between 1 and 99)" msgstr "" -#: ../settings/security/third-party/gitlab.rst:23 -msgid "" -"Enter the \"APP ID\" and the \"APP SECRET\" from the Gitlab OAUTH " -"Applications Dashboard and your Gitlab-URL in the \"SITE\" field." +#: ../misc/variables/config.rst:1 +msgid "Config > Ticket Hook" msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab config in Zammad admin interface" +#: ../misc/variables/config.rst:1 +msgid "``#{config.ticket_hook}``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:30 -msgid "" -"After you configured the Gitlab credentials and activated the login method, " -"you should see a new icon on the login page." +#: ../misc/variables/config.rst:1 +msgid "``Ticket#``" msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab logo on login page" +#: ../misc/variables/current-user.rst:2 +msgid "Current User" msgstr "" -#: ../settings/security/third-party/gitlab.rst:36 +#: ../misc/variables/current-user.rst:6 msgid "" -"If you click on the icon you will be redirected to Gitlab and see something " -"similar to this:" +"Current user variables always return values of the current user that caused " +"e.g. a trigger to run." msgstr "" -#: ../settings/security/third-party/gitlab.rst:None -msgid "Gitlab oauth page" +#: ../misc/variables/current-user.rst:8 +msgid "" +"Due to the above fact, these variables are often not (yet) set or available " +"for usage." msgstr "" -#: ../settings/security/third-party/google.rst:4 +#: ../misc/variables/current-user.rst:10 msgid "" -"With some easy and fast steps, you can enable Zammad to authenticate your " -"users via Google." +"In situations where e.g. schedulers or triggers run, this most likely is " +"nothing you want to use." msgstr "" -#: ../settings/security/third-party/google.rst:8 -msgid "Register a Google App" +#: ../misc/variables/current-user.rst:13 +msgid "Current User Variables" msgstr "" -#: ../settings/security/third-party/google.rst:10 -msgid "" -"First of all, we need to create a new project - you can skip this step if " -"you already have one." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Address" msgstr "" -#: ../settings/security/third-party/google.rst:15 -msgid "" -"Use this link to create a new project: https://console.cloud.google.com/" -"projectcreate" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.address}``" msgstr "" -#: ../settings/security/third-party/google.rst:18 -msgid "" -"Now expand the menu, expand \"APIs & Services\" and select \"Credentials\". " -"Go to the tab \"OAuth consent screen\" first and ensure to fill in the " -"requested information - without doing so you can't create credentials!" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Some street 1, 12345 Berlin`` or empty if not set" msgstr "" -#: ../settings/security/third-party/google.rst:None -msgid "Creating a consent screen" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Avatar" msgstr "" -#: ../settings/security/third-party/google.rst:25 -msgid "" -"After filling in and saving the consent screen information, you can go to " -"the \"Credentials\" tab and create new \"OAuth client ID\"-Credentials." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/google.rst:28 -msgid "" -"Fill in the necessary information as follows and replace ``zammad_host`` " -"with your FQDN:" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "avatar picture with width and height in pixel (e.g. 60,60)" msgstr "" -#: ../settings/security/third-party/google.rst:31 -msgid "**Application type** ``[x] Web application``" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created at" msgstr "" -#: ../settings/security/third-party/google.rst:34 -msgid "**Authorized JavaScript origins** ``https://zammad_host/``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_at}``" msgstr "" -#: ../settings/security/third-party/google.rst:37 -msgid "" -"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" -"callback``" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC``" msgstr "" -#: ../settings/security/third-party/google.rst:None -msgid "Adding a new OAuth client ID" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Address" msgstr "" -#: ../settings/security/third-party/google.rst:43 -msgid "" -"After creating the credentials, go to your Zammad installation and navigate " -"to \"Admin > Security > Third Party Applications\" > Google. Enter your " -"Client ID and Client secret here." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.address}``" msgstr "" -#: ../settings/security/third-party/google.rst:None -msgid "Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Avatar" msgstr "" -#: ../settings/security/third-party/google.rst:50 -msgid "After submitting, the login via Google can be used." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:2 -msgid "Microsoft" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Department" msgstr "" -#: ../settings/security/third-party/microsoft.rst:4 -msgid "" -"Zammad's Microsoft connection allows your users with Microsoft accounts to " -"login. This works for Azure users as well and can be an alternative to :doc:" -"`/system/integrations/ldap/index`." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.department}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:10 -msgid "" -"This documentation part does not cover our :doc:`📧 Microsoft 365 email " -"channel `." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Sales`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screenshot showing Microsoft login button on Zammad login screen." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Email" msgstr "" -#: ../settings/security/third-party/microsoft.rst:30 -#: ../settings/security/third-party/microsoft.rst:53 -msgid "Supported account types:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.email}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:22 -msgid "" -"Please note that Zammad only supports these account types (App dependent):" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``jdoe@customer.tld``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:35 -msgid "Avatars of signing in users:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Fax" msgstr "" -#: ../settings/security/third-party/microsoft.rst:33 -msgid "" -"Zammad currently ignores user avatars. If the user is registered with e.g. " -"Gravatar, Zammad will fetch the avatar from there if enabled. See :doc:" -"`Zammad Image Service ` for more." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.fax}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:38 -msgid "Step 1 - Register a Microsoft App for Zammad" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``004930123464789`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:40 -msgid "" -"Login to the `Microsoft Azure Portal `_ and " -"navigate to App registrations to create a new app. Provide the requested " -"information as follows and register your app." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Firstname" msgstr "" -#: ../settings/security/third-party/microsoft.rst:46 -msgid "Name:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.firstname}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:45 -msgid "" -"Any meaningful name fitting, this name will be displayed to users trying to " -"authenticate with this app." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``John`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:49 -msgid "Choose one of the above mentioned account types (see Limitations)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Lastname" msgstr "" -#: ../settings/security/third-party/microsoft.rst:51 -msgid "" -"The correct account type depends on your use case. If you want to use the " -"authentication internal only, choose the first option. If you're unsure, use " -"the \"Help me choose...\" link." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.lastname}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:58 -msgid "Redirect URI (optional):" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Login" msgstr "" -#: ../settings/security/third-party/microsoft.rst:56 -msgid "" -"Select web and provide your callback URL. The callback URL looks like this: " -"``https://zammad.domain.tld/auth/microsoft_office365/callback``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.login}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to register a Microsoft app" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Mobile" msgstr "" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "Within **API permissions** add the following permissions:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.mobile}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:69 -msgid "``User.Read``" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``0049176123456789`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "Contacts" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Note" msgstr "" -#: ../settings/security/third-party/microsoft.rst:71 -msgid "``Contacts.Read``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.note}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:73 -msgid "" -"You can find these permissions within *Microsoft Graph → Delegated " -"permissions*." +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``Some note to this user`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to add required API permissions" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Phone" msgstr "" -#: ../settings/security/third-party/microsoft.rst:80 -msgid "" -"Within **Certificates & secrets** create a new client secret. Note down the " -"returned secret **value** for later. **Do not** use the secret ID!" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.phone}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to create a new app secret" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``004930123456789`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:88 -msgid "" -"From **Overview** copy your apps *Application (client) ID*. If you're using " -"a single tenant app, please also copy *Directory (tenant) ID*. You now have " -"all required information for Zammad." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > VIP" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "Screencast showing how to retreive application client and tenant IDs" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.vip}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:98 -msgid "Step 2 - Add App Credentials to Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Created by > Web" msgstr "" -#: ../settings/security/third-party/microsoft.rst:100 -msgid "" -"Navigate to Security > Third-party Applications (Tab) within Zammad's admin " -"settings. Scroll down to the section *Authentication via Microsoft* and fill " -"in the required information." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.created_by.web}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:105 -msgid "App ID:" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``https://zammad.org`` or empty if not set" msgstr "" -#: ../settings/security/third-party/microsoft.rst:105 -msgid "This is your *Application (client) ID*." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Department" msgstr "" -#: ../settings/security/third-party/microsoft.rst:108 -msgid "App secret:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.department}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:108 -msgid "This is your *client secret* (value)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Email" msgstr "" -#: ../settings/security/third-party/microsoft.rst:113 -msgid "App Tenant ID:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.email}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:111 -msgid "" -"**optional** only required for apps that use account type *Accounts in this " -"organizational directory only (Default Directory only - Single tenant).*" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Fax" msgstr "" -#: ../settings/security/third-party/microsoft.rst:115 -msgid "" -"Apply your settings by pressing submit and activate *Authentication via " -"Microsoft*." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.fax}``" msgstr "" -#: ../settings/security/third-party/microsoft.rst:None -msgid "" -"Screencast showing how to add app credentials and activating the\n" -"authentication method" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Firstname" msgstr "" -#: ../settings/security/third-party/saml.rst:2 -msgid "SAML" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.firstname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:4 -msgid "" -"Connect your SAML (Security Assertion Markup Language) identity provider as " -"a single sign-on (SSO) method." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Lastname" msgstr "" -#: ../settings/security/third-party/saml.rst:7 -msgid "" -"SAML is an open standard for SSO authentication (among other things). Sign-" -"ins are shared across multiple **service providers** and managed by a " -"central **identity provider** (IdP)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.lastname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:11 -msgid "" -"In this case, the service provider is Zammad, and the IdP is a software " -"service that you either host or subscribe to (*e.g.,* `Keycloak `_, `Redhat SSO Server `_, `ADFS `_, or `Okta `_)." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Login" msgstr "" -#: ../settings/security/third-party/saml.rst:18 -msgid "" -"This guide assumes you are already using SAML within your organization (i." -"e., that your IdP is fully set up)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.login}``" msgstr "" -#: ../settings/security/third-party/saml.rst:21 -msgid "" -"Please note: Our instructions are based on connecting Zammad with Keycloak." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Mobile" msgstr "" -#: ../settings/security/third-party/saml.rst:25 -msgid "Step 1: Configure Your IdP" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.mobile}``" msgstr "" -#: ../settings/security/third-party/saml.rst:28 -msgid "Add Zammad as a Client/App" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Note" msgstr "" -#: ../settings/security/third-party/saml.rst:30 -msgid "" -"Import Zammad into your IdP using the XML configuration found at ``https://" -"your.zammad.domain/auth/saml/metadata``." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.note}``" msgstr "" -#: ../settings/security/third-party/saml.rst:33 -msgid "" -"If your IdP doesn't support XML import, you will have to configure Zammad as " -"a new client/app manually using the above XML metadata file for reference." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Domain based assignment" msgstr "" -#: ../settings/security/third-party/saml.rst:36 -msgid "For instance, when you see this tag:" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.domain_assignment}``" msgstr "" -#: ../settings/security/third-party/saml.rst:42 -msgid "" -"Set the **Assertion Consumer Service Binding URL** (sometimes also listed as " -"**Valid Redirect URIs**) to ``http://your.zammad.domain/auth/saml/callback``." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Domain" msgstr "" -#: ../settings/security/third-party/saml.rst:47 -msgid "Set Up User Attribute Mapping" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.domain}``" msgstr "" -#: ../settings/security/third-party/saml.rst:49 -msgid "" -"Zammad requests the following user attributes (or “properties”) from the IdP:" +#: ../misc/variables/current-user.rst:1 +msgid "``zammad.com`` or empty if not set" msgstr "" -#: ../settings/security/third-party/saml.rst:51 -msgid "Email address (``email``)" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Name" msgstr "" -#: ../settings/security/third-party/saml.rst:52 -msgid "Full name (``name``)" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.name}``" msgstr "" -#: ../settings/security/third-party/saml.rst:53 -msgid "Given name (``first_name``)" +#: ../misc/variables/current-user.rst:1 +msgid "``Zammad GmbH``" msgstr "" -#: ../settings/security/third-party/saml.rst:54 -msgid "Family name (``last_name``)" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Note" msgstr "" -#: ../settings/security/third-party/saml.rst:56 -msgid "" -"You may need to set up “mappers” (or “mappings”) to tell your IdP how user " -"attributes in SAML correspond to those in Zammad. For a more detailed " -"breakdown, refer to the XML metadata file referenced in the previous section." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.note}``" msgstr "" -#: ../settings/security/third-party/saml.rst:62 -msgid "Per-IdP Instructions" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``A note to the organization of the user`` or empty if not set" msgstr "" -#: ../settings/security/third-party/saml.rst:102 -msgid "Keycloak" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > Shared organization" msgstr "" -#: ../settings/security/third-party/saml.rst:65 -msgid "" -"**To add Zammad as a client,** save the XML configuration to disk (``https://" -"your.zammad.domain/auth/saml/metadata``) and use **Clients > Clients list > " -"Import client** in the Keycloak admin panel." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.shared}``" msgstr "" -#: ../settings/security/third-party/saml.rst:70 -msgid "" -"To help Zammad **match its own user accounts to Keycloak users**, create a " -"user attribute (or “property”) mapper. In **Clients list**, click on your " -"newly created Client ID, choose the tab **Client scopes** and click on the " -"link which refers to your Zammad instance. Choose **Add mapper > By " -"configuration > User Property** and create a mapper with the following " -"entries:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Organization > VIP" msgstr "" -#: ../settings/security/third-party/saml.rst:78 -msgid "**Name**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.organization.vip}``" msgstr "" -#: ../settings/security/third-party/saml.rst:80 -msgid "**Mapper Type**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Phone" msgstr "" -#: ../settings/security/third-party/saml.rst:81 -msgid "``User Property``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.phone}``" msgstr "" -#: ../settings/security/third-party/saml.rst:82 -msgid "**Property**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated at" msgstr "" -#: ../settings/security/third-party/saml.rst:83 -msgid "``emailAddress``" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_at}``" msgstr "" -#: ../settings/security/third-party/saml.rst:84 -msgid "**SAML Attribute Name**" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Address" msgstr "" -#: ../settings/security/third-party/saml.rst:86 -msgid "**SAML Attribute NameFormat**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.address}``" msgstr "" -#: ../settings/security/third-party/saml.rst:87 -msgid "``basic``" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Avatar" msgstr "" -#: ../settings/security/third-party/saml.rst:89 -msgid "" -"In the example above, we're telling Zammad that whenever it receives a SAML " -"login request, it should take the ``email`` property from Keycloak, look for " -"a Zammad user with the same ``email`` attribute, and create a new session " -"for that user." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/saml.rst:95 -msgid "" -"If your Keycloak users' email addresses are stored on another property (*e." -"g.,* ``username``), adjust accordingly." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Department" msgstr "" -#: ../settings/security/third-party/saml.rst:98 -msgid "" -"Back in **Settings**, enter the Client ID (``https://your.zammad.domain/auth/" -"saml/metadata``) in the field **Master SAML Processing URL**." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.department}``" msgstr "" -#: ../settings/security/third-party/saml.rst:101 -msgid "You also need to enable **Sign assertions**." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Email" msgstr "" -#: ../settings/security/third-party/saml.rst:105 -msgid "Step 2: Configure Zammad" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.email}``" msgstr "" -#: ../settings/security/third-party/saml.rst:107 -msgid "" -"Enable SAML and enter your IdP's details in the Admin Panel under **Settings " -"> Security > Third Party Applications > Authentication via SAML**:" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Fax" msgstr "" -#: ../settings/security/third-party/saml.rst:None -msgid "Example configuration of SAML part 1" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.fax}``" msgstr "" -#: ../settings/security/third-party/saml.rst:119 -msgid "Display name" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Firstname" msgstr "" -#: ../settings/security/third-party/saml.rst:116 -msgid "" -"Allows you to define a custom button name for SAML. This helps your users to " -"understand better what the button on the login page does." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.firstname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:119 -msgid "Defaults to ``SAML``." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Lastname" msgstr "" -#: ../settings/security/third-party/saml.rst:123 -msgid "IDP SSO target URL" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.lastname}``" msgstr "" -#: ../settings/security/third-party/saml.rst:122 -msgid "" -"This is the target URL Zammad shall redirect to when the user presses the " -"SAML button. For Keycloak, this needs to look like https://your.domain/" -"realms/your-realm/protocol/saml" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Login" msgstr "" -#: ../settings/security/third-party/saml.rst:127 -msgid "IDP single logout target URL" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.login}``" msgstr "" -#: ../settings/security/third-party/saml.rst:126 -msgid "" -"This is the URL to which the single logout request and response should be " -"sent." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Mobile" msgstr "" -#: ../settings/security/third-party/saml.rst:131 -msgid "IDP certificate" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.mobile}``" msgstr "" -#: ../settings/security/third-party/saml.rst:130 -msgid "" -"The public certificate of your IDP for Zammad to verify during the callback " -"phase." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Note" msgstr "" -#: ../settings/security/third-party/saml.rst:145 -msgid "IDP certificate fingerprint" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.note}``" msgstr "" -#: ../settings/security/third-party/saml.rst:134 -msgid "" -"The fingerprint of your IDPs public certificate to verify during callback " -"phase." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Phone" msgstr "" -#: ../settings/security/third-party/saml.rst:137 -msgid "🔏 **For the IdP certificate / certificate fingerprint:**" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.phone}``" msgstr "" -#: ../settings/security/third-party/saml.rst:139 -msgid "" -"Provide **only one or the other**—do not provide both! (Between the two, we " -"recommend the signing certificate itself: fingerprints use SHA-1, which `has " -"been broken for a while now `_.)" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > VIP" msgstr "" -#: ../settings/security/third-party/saml.rst:144 -msgid "" -"**Keycloak users:** Find your certificate in the Keycloak admin panel under " -"**Realm Settings > Keys > Algorithm: RS256 > Certificate**." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.vip}``" msgstr "" -#: ../settings/security/third-party/saml.rst:151 -msgid "Name identifier format" +#: ../misc/variables/current-user.rst:1 ../misc/variables/ticket.rst:1 +msgid "``false`` or ``true``" msgstr "" -#: ../settings/security/third-party/saml.rst:148 -msgid "" -"This is the unique identifiers field type. Usually it should be ``urn:oasis:" -"names:tc:SAML:1.1:nameid-format:emailAddress``." +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Updated by > Web" msgstr "" -#: ../settings/security/third-party/saml.rst:151 -msgid "Zammad **expects an email address as unique identifier**!" +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.updated_by.web}``" msgstr "" -#: ../settings/security/third-party/saml.rst:155 -msgid "UID attribute name" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > VIP" msgstr "" -#: ../settings/security/third-party/saml.rst:154 -msgid "" -"Here you can define an attribute that uniquely identifies the user. If " -"unset, the name identifier returned by the IDP is used." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.vip}``" msgstr "" -#: ../settings/security/third-party/saml.rst:None -msgid "Example configuration of SAML part 2" +#: ../misc/variables/current-user.rst:1 +msgid "Current User > Web" msgstr "" -#: ../settings/security/third-party/saml.rst:163 -msgid "" -"Decide if the certificate for the connection to the IdP service has to be " -"verified or not (default: ``yes``)." +#: ../misc/variables/current-user.rst:1 +msgid "``#{user.web}``" msgstr "" -#: ../settings/security/third-party/saml.rst:169 -msgid "Signing & Encrypting" +#: ../misc/variables/ticket.rst:6 +msgid "" +"Below you can find all available ticket-based variables within Zammad. These " +"can be called via triggers for example. If you're unsure if Zammad does " +"support variables at the point you're at, you can try to type ``::`` to " +"check." msgstr "" -#: ../settings/security/third-party/saml.rst:169 -msgid "" -"Define if you want to sign, encrypt, do both or nothing for the requests." +#: ../misc/variables/ticket.rst:12 +msgid "Ticket Variables" msgstr "" -#: ../settings/security/third-party/saml.rst:179 -msgid "Certificate (PEM)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Accounted Time" msgstr "" -#: ../settings/security/third-party/saml.rst:172 -msgid "" -"Paste the public certificate of your Zammad SAML client, if you want to " -"encrypt the requests." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.time_unit}``" msgstr "" -#: ../settings/security/third-party/saml.rst:175 -msgid "Make sure the certificate is:" +#: ../misc/variables/ticket.rst:1 +msgid "``1``, ``2.75`` or empty response" msgstr "" -#: ../settings/security/third-party/saml.rst:177 -msgid "already valid and not yet expired" +#: ../misc/variables/ticket.rst:1 +msgid "``3``, any number of articles existing in the ticket right now" msgstr "" -#: ../settings/security/third-party/saml.rst:178 -msgid "no CA certificate" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Closing time" msgstr "" -#: ../settings/security/third-party/saml.rst:179 -msgid "valid for signing and encrypting" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.close_at}``" msgstr "" -#: ../settings/security/third-party/saml.rst:185 -msgid "Private key (PEM)" +#: ../misc/variables/ticket.rst:1 +msgid "2019-10-07 17:25:00 UTC" msgstr "" -#: ../settings/security/third-party/saml.rst:182 -msgid "" -"Paste the private key of your Zammad SAML client here, if you want to sign " -"the requests." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created at" msgstr "" -#: ../settings/security/third-party/saml.rst:185 -msgid "Make sure the key is an RSA key with a length of at least 2048 bits." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_at}``" msgstr "" -#: ../settings/security/third-party/saml.rst:188 -msgid "Private key secret" +#: ../misc/variables/ticket.rst:1 +msgid "2019-10-07 16:25:00 UTC" msgstr "" -#: ../settings/security/third-party/saml.rst:188 -msgid "If your private key is secured with a secret, you can provide it here." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Address" msgstr "" -#: ../settings/security/third-party/saml.rst:192 -msgid "Your callback URL" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.address}``" msgstr "" -#: ../settings/security/third-party/saml.rst:191 -msgid "" -"This URL is needed for your IdP configuration so it knows where to redirect " -"to after successful authentication." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Avatar" msgstr "" -#: ../settings/security/third-party/saml.rst:194 -msgid "" -"After saving your input by clicking on the \"Submit\" button, Zammad " -"verifies the provided keys/certificates (e.g. if they are valid for signing/" -"encrypting and if they aren't expired)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.avatar(60,60)}``" msgstr "" -#: ../settings/security/third-party/saml.rst:199 -msgid "" -"See :ref:`automatic account linking ` for details " -"on how to link existing Zammad accounts to IdP accounts." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Department" msgstr "" -#: ../settings/security/third-party/saml.rst:205 -msgid "Automatic account linking doesn't work" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.department}``" msgstr "" -#: ../settings/security/third-party/saml.rst:206 -msgid "" -"Have you double-checked your IdP's user attribute mapping configuration?" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Email" msgstr "" -#: ../settings/security/third-party/twitter.rst:4 -msgid "" -"It is possible to create a quick login for your helpdesk via Twitter. To do " -"so, you need to follow these steps:" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.email}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:8 -msgid "Register Twitter App" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Fax" msgstr "" -#: ../settings/security/third-party/twitter.rst:10 -msgid "Go to https://dev.twitter.com/apps and login with your account." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.fax}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:15 -msgid "Click on \"Create App\"" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Firstname" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "new app page" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.firstname}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:20 -msgid "" -"Enter app settings. As \"Callback URL\" you need to enter ``https://" -"zammad_host/api/v1/external_credentials/twitter/callback``. You need to " -"replace ``zammad_host`` with the domain of your Zammad system." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Lastname" msgstr "" -#: ../settings/security/third-party/twitter.rst:24 -msgid "" -"After the app has been created, update the application icon and organization " -"attributes." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.lastname}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "set permissions to receive and send direct messages" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Login" msgstr "" -#: ../settings/security/third-party/twitter.rst:30 -msgid "" -"Next we need to set ``read, write and access direct messages`` permissions " -"for the app." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.login}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "click on Keys & Access Token, note them" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Mobile" msgstr "" -#: ../settings/security/third-party/twitter.rst:36 -msgid "" -"Go to \"Keys and Access Token\" tab and note the \"Consumer Key\" and " -"\"Consumer Secret\"." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.mobile}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:40 -msgid "Configure Zammad as Twitter App" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Note" msgstr "" -#: ../settings/security/third-party/twitter.rst:42 -msgid "" -"Go to \"Admin > Security > Twitter > Third Party Applications > Twitter\" " -"Section." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.note}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:None -msgid "Admin > Security > Third Party Applications" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Phone" msgstr "" -#: ../settings/security/third-party/twitter.rst:48 -msgid "" -"Fill in the \"Twitter Key\" and the \"Twitter Secret\" and click the " -"\"Submit\" button." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.phone}``" msgstr "" -#: ../settings/security/third-party/twitter.rst:51 -msgid "" -"Now you can link accounts via \"Avatar > Profile > Link Accounts\" or login " -"via Zammad login page." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > VIP" msgstr "" -#: ../settings/security/two-factor.rst:11 -msgid "Two-factor Authentication Methods" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.vip}``" msgstr "" -#: ../settings/security/two-factor.rst:2 -msgid "Two-Factor Authentication" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Created by > Web" msgstr "" -#: ../settings/security/two-factor.rst:4 -msgid "" -"Two-factor authentication (2FA) enhances the security of Zammad accounts by " -"adding an extra layer of verification beyond a password. It requires users " -"to provide two different types of authentication factors, typically " -"something they know (like a password) and something they possess (like a " -"mobile device or a security token), to ensure that only authorized " -"individuals can access the account." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.created_by.web}``" msgstr "" -#: ../settings/security/two-factor.rst:19 -msgid "Enable Recovery Codes" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Address" msgstr "" -#: ../settings/security/two-factor.rst:21 -msgid "" -"Recovery codes are one-time use security codes that can be used by the user " -"if they lose access to their other two-factor authentication methods. They " -"cannot be used on their own, they can only be activated if at least one two-" -"factor authentication method is enabled." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.address}``" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Enable Recovery Codes Setting" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Avatar" msgstr "" -#: ../settings/security/two-factor.rst:30 -msgid "" -"Recovery codes can only be used as a backup method. If enabled, they will be " -"automatically generated for the user once they set up their initial two-" -"factor authentication method." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.avatar(60,60)}``" msgstr "" -#: ../settings/security/two-factor.rst:34 -msgid "" -"The user will be asked to print out or save the generated recovery codes in " -"a safe place. Once used, a recovery code cannot be reused." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Department" msgstr "" -#: ../settings/security/two-factor.rst:37 -msgid "" -"Users will also have an option to regenerate their recovery codes at any " -"time, which invalidates already existing recovery codes and provides them " -"with a list of fresh codes." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.department}``" msgstr "" -#: ../settings/security/two-factor.rst:41 -msgid "" -"After you enable this setting, when the user completes a setup of their " -"initial two-factor authentication method, they will be presented with a list " -"of recovery codes and instructed to save them for later use." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Email" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Recovery Codes Generation Modal Dialog" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.email}``" msgstr "" -#: ../settings/security/two-factor.rst:50 -msgid "Enforce the Set Up of the Two-Factor Authentication" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Fax" msgstr "" -#: ../settings/security/two-factor.rst:52 -msgid "" -"In case you wish to require your users to set up at least one two-factor " -"authentication method for their account, you can do this by selecting " -"specific user roles the requirement applies to in **Enforced for user " -"roles** setting. Of course you must have at least one two-factor " -"authentication method enabled for this setting to take effect." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.fax}``" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Enforced for User Roles Setting" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Firstname" msgstr "" -#: ../settings/security/two-factor.rst:62 -msgid "" -"After you change this setting, if the user has one of the selected roles on " -"their account, they will be forced to set up the two-factor authentication " -"upon next sign in or application reload." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.firstname}``" msgstr "" -#: ../settings/security/two-factor.rst:66 -msgid "" -"A modal dialog with instructions will be shown, and they will not be able to " -"do any work before they set up at least one two-factor method." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Lastname" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Modal Dialog for Enforcing Two-Factor Authentication Set Up" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.lastname}``" msgstr "" -#: ../settings/security/two-factor.rst:74 -msgid "Reset Two-Factor Authentication for a Specific User" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Login" msgstr "" -#: ../settings/security/two-factor.rst:76 -msgid "" -"In case an user isn't able to login anymore because of an inaccessible " -"second factor, you can reset the user's 2FA method." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.login}``" msgstr "" -#: ../settings/security/two-factor.rst:79 -msgid "" -"To do this, go to the user management and search for the relevant user. " -"After you found the account, click the button in the action column and " -"select \"Manage Two-Factor Authentication\":" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Mobile" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Context menu in action column in user management" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.mobile}``" msgstr "" -#: ../settings/security/two-factor.rst:87 -msgid "" -"After selecting this, you can see a dialog where you can either reset one " -"2FA method or reset all of the user's 2FA methods:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Note" msgstr "" -#: ../settings/security/two-factor.rst:None -msgid "Dialog for resetting user's 2FA method" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.note}``" msgstr "" -#: ../settings/security/two-factor.rst:94 -msgid "" -"Choose the fitting one, click on the corresponding \"Remove ...\" button and " -"confirm your action. The user now has to setup a new 2FA method, depending " -"on your 2FA configuration." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Phone" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:2 -msgid "Authenticator App" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.phone}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:4 -msgid "" -"The authenticator app method is a type of two-factor authentication that " -"uses a mobile application to generate one-time codes for account " -"verification. After setting up the authenticator app on their device, the " -"user links it to their Zammad account." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > VIP" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:12 -msgid "" -"When logging in, the user is prompted to enter a time-sensitive code " -"generated by the app, in addition to their password. This code acts as the " -"second factor of authentication, providing an extra layer of security as it " -"changes periodically and is unique to the user's device." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.vip}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:None -msgid "Security Code in Google Authenticator App" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Customer > Web" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:22 -msgid "" -"The app generates codes based on a shared secret key stored securely on both " -"the user's device and the server, ensuring a synchronized and secure " -"authentication process. The method of generating the codes is sometimes also " -"called TOTP (time-based one-time password)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.customer.web}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:28 -msgid "Enabling the Authenticator App Method" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Escalation at" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:30 -#: ../settings/security/two-factor/security-keys.rst:28 -msgid "To enable the method, just toggle the switch on in the settings." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.escalation_at}``" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:None -msgid "Authenticator App Switch in Settings" +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable" msgstr "" -#: ../settings/security/two-factor/authenticator-app.rst:36 -msgid "" -"Now the users will be able to set up this two-factor authentication method " -"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " -"Once they do, on next sign-in with password, they will be asked to provide " -"an additional security code generated by their mobile device." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > First response" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:2 -msgid "Security Keys" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.first_response_at}``" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:4 -msgid "" -"The security keys method is a type of a two-factor authentication that uses " -"Web Authentication API in the browser for verifying user's identity. The " -"user can register multiple hardware or software security keys with their " -"Zammad account and then they can use it during the sign-in process." +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable yet" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:12 -msgid "" -"When logging in, the user is prompted to provide the same security key they " -"registered with their account, in addition to their password. This key acts " -"as the second factor of authentication, providing an extra layer of security." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Assign Follow-Ups" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:None -msgid "Security Key dialog in Safari on macOS" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_assignment}``" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:21 -msgid "" -"The type of the key can range from hardware USB sticks to passkeys stored in " -"a device of user's choice. Which type can be used depends on the browser " -"flavor and the platform of the user." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Assignment Timeout" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:26 -msgid "Enabling the Security Keys Method" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.assignment_timeout}``" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:None -msgid "Security Keys Switch in Settings" +#: ../misc/variables/ticket.rst:1 +msgid "``20`` or empty if not configured" msgstr "" -#: ../settings/security/two-factor/security-keys.rst:34 -msgid "" -"Now the users will be able to set up this two-factor authentication method " -"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " -"Once they do, on next sign-in with password, they will be asked to provide " -"the same security key they registered during the setup." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Follow-up possible" msgstr "" -#: ../settings/system/system-selfhosted.include.rst:3 -msgid "" -"Below settings are only available to self hosted users. In hosted " -"environments we're handling these settings for you to ensure service " -"stability." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.follow_up_possible}``" msgstr "" -#: ../settings/system/base.rst:11 -msgid "Fully Qualified Domain Name" +#: ../misc/variables/ticket.rst:1 +msgid "``no`` or ``yes``" msgstr "" -#: ../settings/system/base.rst:7 -msgid "The URL of your Zammad installation." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Name" msgstr "" -#: ../settings/system/base.rst:9 ../settings/system/base.rst:17 -msgid "This setting is used within :doc:`/system/variables` and notifications." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.name}``" msgstr "" -#: ../settings/system/system-base.include.rst:1 -msgid "It is automatically set by the *Getting Started wizard*." +#: ../misc/variables/ticket.rst:1 +msgid "``Sales``" msgstr "" -#: ../settings/system/system-base.include.rst:5 -msgid "Changing this setting also changes callback URLs for your channels etc." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Group > Note" msgstr "" -#: ../settings/system/system-base.include.rst:6 -msgid "This setting can have negative affects on being able to login." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.group.note}``" msgstr "" -#: ../settings/system/base.rst:19 -msgid "HTTP type" +#: ../misc/variables/ticket.rst:1 +msgid "``Note about this group``" msgstr "" -#: ../settings/system/base.rst:14 -msgid "" -"The HTTP type tells your installation how your clients connect. This is " -"relevant for authentication and cookie security." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > ID" msgstr "" -#: ../settings/system/base.rst:31 -msgid "SystemID" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.id}``" msgstr "" -#: ../settings/system/base.rst:22 -msgid "" -"This ID is being used within your ticket number. In case you're " -"communicating with another ticket system with similar ticket number schemes " -"this ID greatly reduces the risk of false follow ups." +#: ../misc/variables/ticket.rst:1 +msgid "``17``, ``5281``, ..." msgstr "" -#: ../settings/system/base.rst:26 -msgid "" -"The SystemID is randomly selected upon installation of Zammad (``1-99``)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact (agent)" msgstr "" -#: ../settings/system/base.rst:30 -msgid "" -"**Do not** change this setting in a productive system! Your Zammad " -"installation may no longer recognize old ticket number based follow ups upon " -"change!" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_agent_at}``" msgstr "" -#: ../settings/system/frontend.rst:2 -msgid "Frontend" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact (customer)" msgstr "" -#: ../settings/system/frontend.rst:22 -msgid "Core Workflow Ajax Mode" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_customer_at}``" msgstr "" -#: ../settings/system/frontend.rst:6 +#: ../misc/variables/ticket.rst:1 msgid "" -"This setting allows administrators to enforce :doc:`/system/core-workflows` " -"to use Ajax-Calls instead of web sockets. You'll usually only need this if " -"you experience serious issues as noted below." +"``2019-10-07 16:25:00 UTC`` or empty if not applicable yet (Please note " +"`Ticket last contact behavior Settings `_ for this)" msgstr "" -#: ../settings/system/frontend.rst:10 -msgid "**🤓 Possible (technical) reasons**" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Last contact" msgstr "" -#: ../settings/system/frontend.rst:12 -msgid "" -"In some cases, your network structure (e.g. firewalls, proxies) may " -"disconnect long web socket connections. This leads to select fields staying " -"empty (e.g. owner selection *after* selecting your group) or fields not " -"shown / hidden (e.g. when switching to or from pending states, the \"pending " -"till\" field not showing / hiding)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.last_contact_at}``" msgstr "" -#: ../settings/system/frontend.rst:18 -msgid "" -"Please keep in mind that the Ajax fallback may cause serious pressure on " -"your application server. If you have the choice stick to web sockets." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Number" msgstr "" -#: ../settings/system/frontend.rst:22 -msgid "Default: ``no`` (inactive)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.number}``" msgstr "" -#: ../settings/system/frontend.rst:53 -msgid "Show calendar weeks in the picker of date/datetime fields" +#: ../misc/variables/ticket.rst:1 +msgid "``31001``, ``201910731001``, ..." msgstr "" -#: ../settings/system/frontend.rst:25 -msgid "" -"With this setting you can instruct Zammad to provide week number display " -"globally for all users. Calendar with week number display are usually used " -"in business sectors and may not be relevant for everyone." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain based assignment" msgstr "" -#: ../settings/system/frontend.rst:29 -msgid "" -"This setting affects *all areas* - you'll also see week numbers in the admin " -"panel for e.g. triggers and macros." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain_assignment}``" msgstr "" -#: ../settings/system/frontend.rst:32 -msgid "Default: ``no`` (not shown)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Domain" msgstr "" -#: ../settings/system/frontend.rst:53 -msgid "Here's the difference:" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.domain}``" msgstr "" -#: ../settings/system/frontend.rst:0 -msgid "Screenshot showing Zammad's date picker (in the default way)" +#: ../misc/variables/ticket.rst:1 +msgid "``domain.tld`` or empty if not set" msgstr "" -#: ../settings/system/frontend.rst:41 -msgid "Set to ``no``" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Name" msgstr "" -#: ../settings/system/frontend.rst:0 -msgid "" -"Screenshot showing Zammad's date picker with\n" -"week numbers enabled" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.name}``" msgstr "" -#: ../settings/system/frontend.rst:50 -msgid "Set to ``yes``" +#: ../misc/variables/ticket.rst:1 +msgid "``Zammad GmbH`` or empty if not set" msgstr "" -#: ../settings/system/index.rst:4 -msgid "" -"For your overview we split each tab within system settings into its own page:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Note" msgstr "" -#: ../settings/system/index.rst:16 -msgid "Console Based Settings" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.note}``" msgstr "" -#: ../settings/system/index.rst:18 -msgid "" -"There's some console based settings we didn't put into the UI. However, you " -"may find them helpful - you can find them in our :docs:`hidden settings ` section." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > Shared organization" msgstr "" -#: ../settings/system/network.rst:2 -msgid "Network" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.shared}``" msgstr "" -#: ../settings/system/network.rst:8 -msgid "" -"The proxy settings can only be saved after successfully testing the proxy " -"connection." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Organization > VIP" msgstr "" -#: ../settings/system/network.rst:15 -msgid "Proxy Address." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.organization.vip}``" msgstr "" -#: ../settings/system/network.rst:12 -msgid "" -"Allows you to provide a proxy server if needed. This is relevant for network " -"communication by Zammad." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Address" msgstr "" -#: ../settings/system/network.rst:15 -msgid "It **does not** affect the update process or Elasticsearch." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.address}``" msgstr "" -#: ../settings/system/network.rst:18 -msgid "Username for proxy connection." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Avatar" msgstr "" -#: ../settings/system/network.rst:18 -msgid "" -"If your proxy server requires authentication, provide the username here." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.avatar(60,60)}``" msgstr "" -#: ../settings/system/network.rst:21 -msgid "Password for proxy connection." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Department" msgstr "" -#: ../settings/system/network.rst:21 -msgid "" -"If your proxy server requires authentication, provide the password here." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.department}``" msgstr "" -#: ../settings/system/network.rst:26 -msgid "No proxy for the following hosts." +#: ../misc/variables/ticket.rst:1 +msgid "``Support`` or empty if not set" msgstr "" -#: ../settings/system/network.rst:24 -msgid "" -"Exception list for hosts you can't or don't want to reach via proxy server." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Email" msgstr "" -#: ../settings/system/network.rst:27 -msgid "Default: ``localhost,127.0.0.0,::1``" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.email}``" msgstr "" -#: ../settings/system/services.rst:2 -msgid "Services" +#: ../misc/variables/ticket.rst:1 +msgid "``agent@company.tld`` or empty if not set" msgstr "" -#: ../settings/system/services.rst:10 -msgid "Image Service" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Fax" msgstr "" -#: ../settings/system/services.rst:5 -msgid "Defines the backend for user and organization image lookups." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.fax}``" msgstr "" -#: ../settings/system/services.rst:7 -msgid "Default: ``Zammad Image Service`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Firstname" msgstr "" -#: ../settings/system/services.rst:9 -msgid "" -"Make sure your on premise installation has ``HTTPS`` access to ``images." -"zammad.com``." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.firstname}``" msgstr "" -#: ../settings/system/services.rst:18 -msgid "Geo Calendar Service" +#: ../misc/variables/ticket.rst:1 +msgid "``Max`` or empty if not set" msgstr "" -#: ../settings/system/services.rst:13 -msgid "" -"Defines the backend for geo calendar lookups. Used for initial calendar " -"setup." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Lastname" msgstr "" -#: ../settings/system/services.rst:16 -msgid "Default: ``Zammad GeoCalendar Service`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.lastname}``" msgstr "" -#: ../settings/system/services.include.rst:2 -msgid "" -"Make sure your on premise installation has ``HTTPS`` access to ``geo.zammad." -"com``." +#: ../misc/variables/ticket.rst:1 +msgid "``Mustermann`` or empty if not set" msgstr "" -#: ../settings/system/services.rst:26 -msgid "Geo IP Service" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Login" msgstr "" -#: ../settings/system/services.rst:21 -msgid "" -"Defines the backend for geo IP lookups. Shows also location of an IP address " -"if an IP address is shown." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.login}``" msgstr "" -#: ../settings/system/services.rst:24 -msgid "Default: ``Zammad GeoIP Service`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "``agent``" msgstr "" -#: ../settings/system/services.rst:32 -msgid "Geo Location Service" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Mobile" msgstr "" -#: ../settings/system/services.rst:29 -msgid "" -"Defines the backend for geo location lookups to store geo locations for " -"addresses." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.mobile}``" msgstr "" -#: ../settings/system/services.rst:32 -msgid "" -"Default: ``OpenStreetMap (ODbL 1.0, http://osm.org/copyright)`` (active)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Note" msgstr "" -#: ../settings/system/services.rst:36 -msgid "" -"You can find a detailed privacy information on what we store for how long on " -"our :docs:`Privacy Appendix ` inside of our System " -"Documentation." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.note}``" msgstr "" -#: ../settings/system/storage.rst:2 -msgid "Storage" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Phone" msgstr "" -#: ../settings/system/storage.rst:6 -msgid "" -"Here you can define where Zammad stores attachments for tickets and the " -"knowledge base. By default, we're writing to the ``Database`` - you can " -"switch to ``Filesystem`` or ``Simple Storage (S3)`` at any time. In this " -"case please have a look on the following instructions." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.phone}``" msgstr "" -#: ../settings/system/storage.rst:11 -msgid "" -"If you have a busy Zammad instance, we strongly encourage you to use " -"filesystem storage instead of \"Database\". This will greatly improve system " -"performance (de-crease database load and size)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > VIP" msgstr "" -#: ../settings/system/storage.rst:19 -msgid "Database" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.vip}``" msgstr "" -#: ../settings/system/storage.rst:17 -msgid "" -"This is the default storage method. The attachments are stored directly in " -"the database. If your Zammad instance grows, we recommend one of the other " -"methods to maintain performance." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Owner > Web" msgstr "" -#: ../settings/system/storage.rst:38 -msgid "Filesystem" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.owner.web}``" msgstr "" -#: ../settings/system/storage.rst:22 -msgid "" -"This storage method is recommended for all Zammad instances, especially for " -"those with a higher load. If you choose filesystem, your files are written " -"to ``/opt/zammad/storage/``." +#: ../misc/variables/ticket.rst:1 +msgid "``https://zammad.com`` or empty if not set" msgstr "" -#: ../settings/system/storage.rst:26 -msgid "" -"Moving attachments from \"Database\" to \"Filesystem\" can be run during " -"production use. However, you should consider your framework conditions (e.g. " -"bandwidth, system load in production) to define the right moment." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Pending till" msgstr "" -#: ../settings/system/storage.rst:32 -msgid "**You noticed slow updates of Zammad?**" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.pending_time}``" msgstr "" -#: ../settings/system/storage.rst:34 -msgid "" -"While Zammad is beeing updated, it enforces a recursive \"change " -"owner\" (chown) for this directory. For instances with many files this can " -"be time consuming. To mitigate that you can move your files and create a " -"symlink in ``/opt/zammad/storage/`` to the new directory. Of course you have " -"to make sure on your own that the permissions are always correct." +#: ../misc/variables/ticket.rst:1 +msgid "``2019-10-07 16:25:00 UTC`` or empty if not set" msgstr "" -#: ../settings/system/storage.rst:95 -msgid "Simple Storage (S3)" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Priority > Name" msgstr "" -#: ../settings/system/storage.rst:41 -msgid "" -"To use the Simple Storage (S3), you have to provide some settings, which " -"can't be accessed in the UI (see instructions below)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.priority.name}``" msgstr "" -#: ../settings/system/storage.rst:44 -msgid "" -"⚠️ Please note that the current implementation is in its early stages and can " -"be modified in the future." +#: ../misc/variables/ticket.rst:1 +msgid "``2 normal``" msgstr "" -#: ../settings/system/storage.rst:47 -msgid "" -"The prerequisite is to have access to a S3-compatible storage and to have " -"all necessary parameters available (which depends on your storage provider; " -"if in doubt, please ask there for help)." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > State > Name" msgstr "" -#: ../settings/system/storage.rst:51 -msgid "Steps to configure S3:" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.state.name}``" msgstr "" -#: ../settings/system/storage.rst:53 -msgid "" -"Copy ``config/zammad/storage.yml.dist`` to ``config/zammad/storage.yml``" +#: ../misc/variables/ticket.rst:1 +msgid "``new``, ``open``, ..." msgstr "" -#: ../settings/system/storage.rst:54 -msgid "Edit the copied file in one of the following ways:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Tags" msgstr "" -#: ../settings/system/storage.rst:56 -msgid "" -"Either provide your S3 configuration with one attribute per line like in the " -"upper area of the file" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.tags}``" msgstr "" -#: ../settings/system/storage.rst:58 +#: ../misc/variables/ticket.rst:1 msgid "" -"Or provide your S3 configuration as an URL (which you can find at the end of " -"the file). Note: you can also provide this URL as environment variable (:" -"docs:`see system documentation `) without using this yml-file." +"Currently not available, see `Issue 2769 `_" msgstr "" -#: ../settings/system/storage.rst:62 -msgid "" -"We recommend the deletion of the not used configuration style to avoid " -"inconsistencies." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Title" msgstr "" -#: ../settings/system/storage.rst:65 -msgid "Restart Zammad so the config file / environment variable is loaded" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.title}``" msgstr "" -#: ../settings/system/storage.rst:66 +#: ../misc/variables/ticket.rst:1 msgid "" -"Set the \"Storage Method\" in Zammad to ``Simple Storage (S3)`` in Settings " -"> System > Storage and click on \"Submit\". After that, Zammad checks your " -"configuration and the connection to the service and will raise an error " -"message if something is wrong." +"``My amazing Subject`` (normally subject, can be edited within Interface and " +"thus differ)" msgstr "" -#: ../settings/system/storage.rst:72 -msgid "A very simple storage configuration could look like this:" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated at" msgstr "" -#: ../settings/system/storage.rst:85 -msgid "" -"Before setting the storage method to ``Simple Storage (S3)`` (step 4), " -"please make sure to have a working setup." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_at}``" msgstr "" -#: ../settings/system/storage.rst:88 -msgid "" -"You can verify this by running ``rails r 'Rails.logger = Logger.new(STDOUT); " -"pp Store::Provider::S3.ping?'`` in your Zammad directory. If everything is " -"fine, you should see ``true``, else you should see ``false`` and a simple " -"error message." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Address" msgstr "" -#: ../settings/system/storage.rst:93 -msgid "" -"If you installed Zammad through a package manager (rather than from source), " -"replace ``rails r`` with ``zammad run rails r`` above. To learn more, see :" -"docs:`Administration via Console `." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.address}``" msgstr "" -#: ../settings/ticket.rst:4 -msgid "" -"Here you can adjust general ticket settings. Additional ones for the ticket " -"composer interface can be found in the :doc:`/misc/composer`." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Avatar" msgstr "" -#: ../settings/ticket.rst:11 -msgid "Ticket Hook (default: ``Ticket#``)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.avatar(60,60)}``" msgstr "" -#: ../settings/ticket.rst:11 -msgid "The identifier for a ticket; *e.g.,* Ticket#, Call#, MyTicket#." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Department" msgstr "" -#: ../settings/ticket.rst:38 -msgid "Ticket Hook Position (default: ``right``)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.department}``" msgstr "" -#: ../settings/ticket.rst:14 -msgid "" -"With this setting you can decide (if) where to insert the ticket number." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Email" msgstr "" -#: ../settings/ticket.rst:20 -msgid "*Right*" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.email}``" msgstr "" -#: ../settings/ticket.rst:17 -msgid "" -"This setting will add the ticket reference on the right site of the subject." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Fax" msgstr "" -#: ../settings/ticket.rst:20 -msgid "Example: ``Some Subject [Ticket#12345]``" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.fax}``" msgstr "" -#: ../settings/ticket.rst:26 -msgid "*Left*" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Firstname" msgstr "" -#: ../settings/ticket.rst:23 -msgid "" -"This setting will add the ticket reference on the left site of the subject." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.firstname}``" msgstr "" -#: ../settings/ticket.rst:26 -msgid "Example: ``[Ticket#12345] Some Subject``" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Lastname" msgstr "" -#: ../settings/ticket.rst:29 -msgid "*None*" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.lastname}``" msgstr "" -#: ../settings/ticket.rst:29 -msgid "This will completely remove ticket references from the subject." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Login" msgstr "" -#: ../settings/ticket.rst:33 -msgid "" -"Please ensure to take a look at :doc:`/channels/email/settings` within the " -"email channel to ensure you have at least one reference that helps Zammad to " -"assign follow-ups correctly." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.login}``" msgstr "" -#: ../settings/ticket.rst:37 -msgid "" -"Disabling this and not setting up any further follow up search will lead to " -"unexpected results!" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Mobile" msgstr "" -#: ../settings/ticket.rst:65 -msgid "" -"Ticket Last Contact Behaviour (default: ``Use the start time of the last " -"customer thread (which may consist of multiple articles).``)" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.mobile}``" msgstr "" -#: ../settings/ticket.rst:41 -msgid "" -"This setting changes the way Zammad updates the ``Last Contact`` value of a " -"ticket. This is fairly important for overviews and what you expect upon " -"ticket updates of a customer." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Note" msgstr "" -#: ../settings/ticket.rst:52 -msgid "" -"Use the start time of the last customer thread (which may consist of " -"multiple articles)." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.note}``" msgstr "" -#: ../settings/ticket.rst:46 -msgid "" -"If this option is chosen, Zammad will update the last updated value just " -"once if a customer replies. After that, Zammad will wait for an agent to " -"react." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Phone" msgstr "" -#: ../settings/ticket.rst:50 -msgid "" -"This comes in handy if you want to work tickets in the order of their first " -"update. This will not change ticket orders if customers decide to \"bump\" " -"the ticket affected." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.phone}``" msgstr "" -#: ../settings/ticket.rst:57 -msgid "Use the time of the very last customer article." +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > VIP" msgstr "" -#: ../settings/ticket.rst:55 -msgid "" -"When setting this option, Zammad will always update the last updated value. " -"This means that if ordering by ``Last Update``, ticket orders will change if " -"customers \"bump\" the ticket." +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.vip}``" msgstr "" -#: ../settings/ticket.rst:64 -msgid "Last contact value used on :doc:`/manage/overviews`" +#: ../misc/variables/ticket.rst:1 +msgid "Ticket > Updated by > Web" msgstr "" -#: ../settings/ticket.rst:65 -msgid "Last contact value used on :doc:`/manage/trigger`" +#: ../misc/variables/ticket.rst:1 +msgid "``#{ticket.updated_by.web}``" msgstr "" -#: ../settings/ticket.rst:88 -msgid "" -"Ticket Organization Reassignment (default: ``Update the most recent tickets." -"``)" +#: ../settings/branding.rst:10 +msgid "Product Name" msgstr "" -#: ../settings/ticket.rst:68 +#: ../settings/branding.rst:7 msgid "" -"This setting changes the way Zammad updates the organization field of the " -"tickets whenever the primary organization of a user is changed." -msgstr "" - -#: ../settings/ticket.rst:74 -msgid "Update the most recent tickets." +"Defines the name of the application, shown in the web interface, tabs and " +"title bar of the web browser." msgstr "" -#: ../settings/ticket.rst:72 -msgid "" -"If this option is chosen, Zammad will update the 100 most recent tickets " -"where the user is the ticket customer. The ticket organization field will be " -"automatically set to the new primary organization of the user." +#: ../settings/branding.rst:10 +msgid "Default value: ``Zammad Helpdesk``" msgstr "" -#: ../settings/ticket.rst:88 -msgid "Do not update any tickets." +#: ../settings/branding.rst:13 +msgid "Will be shown in the app and is included in email footers." msgstr "" -#: ../settings/ticket.rst:77 -msgid "" -"When choosing this option, Zammad will not update any tickets when the " -"user's primary organization is changed." +#: ../settings/branding.rst:19 +msgid "Logo" msgstr "" -#: ../settings/ticket.rst:80 -msgid "**Use with care!**" +#: ../settings/branding.rst:16 +msgid "Defines the logo of the application, shown in the login page of Zammad." msgstr "" -#: ../settings/ticket.rst:82 +#: ../settings/branding.rst:18 msgid "" -"Using this option may lead to inconsistencies in the system as the ticket " -"organization may become decoupled from the ticket customer." +"Ensure to hit the \"Submit\" button after uploading the logo. Otherwise your " +"change will not be saved." msgstr "" -#: ../settings/ticket.rst:85 +#: ../settings/branding.rst:22 msgid "" -"However, you may use this option if you wish to maintain :ref:`the shared " -"access ` to the ticket for all organization " -"members of the original organization of the customer." +"Allows to set the default language of the Zammad instance. The here defined " +"locale mostly acts as a fallback for:" msgstr "" -#: ../settings/ticket.rst:110 -msgid "Ticket Number Format (default: ``Increment (SystemID.Counter)``)" +#: ../settings/branding.rst:25 +msgid "user preferences (if Zammad can't detect the users locale)" msgstr "" -#: ../settings/ticket.rst:94 -msgid "" -"This setting defines the way Zammad's ticket number will look. Changing this " -"setting in production will cause follow up detection to fail." +#: ../settings/branding.rst:26 +msgid "CSV output (reporting, time accounting)" msgstr "" -#: ../settings/ticket.rst:102 -msgid "Increment (SystemID.Counter)" +#: ../settings/branding.rst:30 +msgid "Define the timezone of your Zammad installation." msgstr "" -#: ../settings/ticket.rst:98 +#: ../settings/branding.rst:32 msgid "" -"The increment value contains the SystemID (automatically generated during " -"installation) and a increment which counts up with every new Ticket. The " -"increment will automatically get another digit if needed." +"This does not have any effect on timings for your agents or how Zammad " +"stores date and time values." msgstr "" -#: ../settings/ticket.rst:102 -msgid "Examples: ``1010138``, ``1010139``" +#: ../settings/branding.rst:35 +msgid "Changing this value has direct consequences on the following areas:" msgstr "" -#: ../settings/ticket.rst:110 -msgid "Date (Year.Month.Day.SystemID.Counter)" +#: ../settings/branding.rst:37 +msgid ":doc:`/manage/scheduler` tasks" msgstr "" -#: ../settings/ticket.rst:105 -msgid "" -"This version of the ticket number is fairly long. However, because it " -"contains the date of ticket creation, it also allows you to see when the " -"ticket has been created. You may feel familiar with this number format if " -"you've worked with OTRS already." +#: ../settings/branding.rst:38 +msgid "search indexing (and thus reporting)" msgstr "" -#: ../settings/ticket.rst:110 -msgid "Examples: ``201206231010138``, ``201206231010139``" +#: ../settings/branding.rst:40 +msgid "calendar subscriptions" msgstr "" -#: ../settings/ticket.rst:137 -msgid "OPTIONS" +#: ../settings/branding.rst:41 +msgid "browser printing" msgstr "" -#: ../settings/ticket.rst:113 +#: ../settings/branding.rst:43 msgid "" -"The below options allow you to further customize your ticket number. The " -"availability of options differ depending of the chosen ticket number format " -"above." +"Please note that some of above are fallbacks in case Zammad could not detect " +"the agents timezone correctly." msgstr "" -#: ../settings/ticket.rst:122 -msgid "Checksum (default: ``no``)" +#: ../settings/branding.rst:77 +msgid "Pretty Date" msgstr "" -#: ../settings/ticket.rst:118 +#: ../settings/branding.rst:47 msgid "" -"If set to yes, we'll built a checksum to further \"unique\" the ticket " -"number of your system. If you're dealing with many other ticket systems this " -"might help to prevent false positive follow up detection on tickets." +"This setting allows you to define how Zammad should display time stamps " +"within the interface to all users." msgstr "" -#: ../settings/ticket.rst:122 -msgid "This will also add another digit to the ticket number." +#: ../settings/branding.rst:50 +msgid "" +"This does not have any effect on how Zammad returns e.g. time values via " +"variables." msgstr "" -#: ../settings/ticket.rst:137 -msgid "Min. size of Number (default: ``5``)" +#: ../settings/branding.rst:77 +msgid "Choose in between the following options:" msgstr "" -#: ../settings/ticket.rst:125 -msgid "" -"This setting defines the minimum length of your ticket number. If your " -"counter is not yet high enough, Zammad will fill the number with zeros to " -"ensure the wanted length." +#: ../settings/branding.rst:64 +msgid "relative" msgstr "" -#: ../settings/ticket.rst:129 +#: ../settings/branding.rst:55 msgid "" -"Please note that the minimum length is ``3`` (SystemID + at least one digit " -"if below 10). Also, if the length is no longer long enough, the number will " -"automatically get one digit longer. Ticket-Numbers **do not overflow**, thus " -"it's save to keep it at 5 or set it lower if wanted." +"This timestamp shows a relative time span until it switches to a date. Over " +"time, it will change as follows:" msgstr "" -#: ../settings/ticket.rst:135 -msgid "" -"This option is only available if ticket number format is set to " -"``Increment``!" +#: ../settings/branding.rst:58 +msgid "just now" msgstr "" -#: ../settings/ticket.rst:142 -msgid "Auto-Assignment" +#: ../settings/branding.rst:59 +msgid "5 minutes ago" msgstr "" -#: ../settings/ticket.rst:144 -msgid "" -"In a larger Zammad environment, it happens that several agents open the same " -"ticket at the same time. Although collision detection is then effective, the " -"efficiency of processing can be increased by means of the automatic " -"assignment of tickets when a ticket is opened." +#: ../settings/branding.rst:60 +msgid "3 days 1 hour ago" msgstr "" -#: ../settings/ticket.rst:149 -msgid "" -"The automatic assignment of tickets can be activated and configured in the " -"admin area under Settings > Ticket > Auto Assignment." +#: ../settings/branding.rst:61 +msgid "``03/04/2022``" msgstr "" -#: ../settings/ticket.rst:152 -msgid "" -"The auto assignment only works if the ticket has no owner yet. By default, " -"the agent can always reset the ticket owner to ``-`` if needed." +#: ../settings/branding.rst:63 +msgid "Hovering the timestamp helps, you'll always get a clean timestamp then." msgstr "" -#: ../settings/ticket.rst:155 -msgid "" -"If you want to use this function for only specific tickets, you can " -"configure the conditions accordingly to meet your requirement. By default " -"the condition affects all tickets with the state ``open``." +#: ../settings/branding.rst:71 +msgid "absolute" msgstr "" -#: ../settings/ticket.rst:161 +#: ../settings/branding.rst:67 msgid "" -"If you need to exclude users (e.g. a group leader), you can search and " -"select the desired agents in the ``Exception Users`` list. The search " -"function in this area is only effective, if you have too many agents to " -"display at once to help you with the configuration." +"This timestamp always includes the week day. For one week after creation, " +"the timestamp will not contain the date itself: Thursday 18:35." msgstr "" -#: ../settings/ticket.rst:167 -msgid "Notifications" +#: ../settings/branding.rst:71 +msgid "After a week it will switch to: ``Friday 4. Mar 16:00``." msgstr "" -#: ../settings/ticket.rst:191 -msgid "Default Notifications" +#: ../settings/branding.rst:76 +msgid "timestamp" msgstr "" -#: ../settings/ticket.rst:170 +#: ../settings/branding.rst:74 msgid "" -"This setting allows you to configure the default ticket notifications that " -"will be applied to all new agent users (incl. users who were just assigned " -"agent role). Simply change the notification matrix to desired state and " -"press **Save**." +"This will cause Zammad to show a complete timestamp according to your locale " +"defaults. For English this could be e.g. ``2022/12/03 2:40 pm`` or for " +"German e.g. ``12.03.2022 14:40``." msgstr "" -#: ../settings/ticket.rst:175 -msgid "" -"In case an agent already exists, their ticket notification preferences will " -"be preserved. Optionally, you can also **Apply current defaults to all " -"agents**." +#: ../settings/branding.rst:78 +msgid "Default setting: ``relative``." msgstr "" -#: ../settings/ticket.rst:181 -msgid "" -"**Potential time-consuming action:** Applying default ticket notifications " -"to all agent users may take some time to complete, be patient! The exact " -"time will depend on the size of your system and the number of agents." +#: ../settings/security.rst:2 +msgid "Security" msgstr "" -#: ../settings/ticket.rst:185 +#: ../settings/security.rst:4 msgid "" -"**Active agents only!** When current default ticket notifications are " -"applied, only active agent users are considered. In case an agent is re-" -"activated *after* this action, they will still have the old notification " -"configuration." +"For your overview we split each tab within security settings into its own " +"page:" msgstr "" -#: ../settings/ticket.rst:190 -msgid "" -"In case you want to go back to the initial state of ticket notifications, " -"you can click on **Reset to default** button." +#: ../settings/security/base.rst:2 ../settings/system/base.rst:2 +#: ../settings/ticket.rst:8 +msgid "Base" msgstr "" -#: ../settings/ticket.rst:194 ../settings/ticket.rst:196 -msgid "Duplicate Detection" +#: ../settings/security/base.rst:5 +msgid "New User Accounts" msgstr "" -#: ../settings/ticket.rst:236 ../settings/ticket.rst:238 -msgid "Detect Duplicate Ticket Creation" +#: ../settings/security/base.rst:9 +msgid "" +"Activates the `register as a new customer` function on the login page. If " +"set to ``no`` only administrators or agents can create new accounts manually." msgstr "" -#: ../settings/ticket.rst:197 ../settings/ticket.rst:199 -msgid "" -"This setting turns on the duplicate ticket detection mechanism during ticket " -"creation. If similar tickets are found in the system, a suitable warning " -"will be shown to the user trying to create a ticket." +#: ../settings/security/base.rst:13 ../settings/security/base.rst:38 +#: ../settings/security/base.rst:66 +msgid "Default setting: ``yes``" msgstr "" -#: ../settings/ticket.rst:204 ../settings/ticket.rst:206 -msgid "A Sample Duplicate Ticket Warning" +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"New User Accounts\" setting" msgstr "" -#: ../settings/ticket.rst:206 ../settings/ticket.rst:208 +#: ../settings/security/base.rst:22 msgid "" -"You can choose which ticket attributes will be matched by selecting them in " -"**Attributes to compare** field. Only if the ticket attribute value provided " -"by the user in the ticket create form is *equal* with the attribute in an " -"existing ticket, the warning will be shown." +"Deactivation of above function **does not** deactivate automatic account " +"creation! This means: If a user writes e.g. an email to Zammad and has no " +"account yet, Zammad will automatically create the account. User accounts are " +"a direct dependency of tickets and thus technically mandatory." msgstr "" -#: ../settings/ticket.rst:211 ../settings/ticket.rst:213 -msgid "**Warning title** and **Warning message** are configurable as well." +#: ../settings/security/base.rst:29 +msgid "Lost Password" msgstr "" -#: ../settings/ticket.rst:213 ../settings/ticket.rst:215 +#: ../settings/security/base.rst:33 msgid "" -"You can limit the detection only to certain user roles. By default, only " -"agents will see the warning." +"Activates the `lost password` function on the login page. If set to ``no`` " +"only administrators may change the user's password - users may update their " +"own password if they're still logged in and they have the required :doc:" +"`permission `." msgstr "" -#: ../settings/ticket.rst:216 ../settings/ticket.rst:218 -msgid "" -"If you don't want to show the matched tickets as part of the warning, you " -"can set **Show matching ticket(s) in the warning** setting to *no*." +#: ../settings/security/base.rst:0 +msgid "Figure showing activated \"Lost Password\" setting" msgstr "" -#: ../settings/ticket.rst:219 ../settings/ticket.rst:221 +#: ../settings/security/base.rst:49 msgid "" -"By default, **Permission level for looking up ticket** is set to *User*, " -"which means user permissions will be honored during sarch. The user will " -"see the warning only if tickets they have access to are matched. " -"Alternatively, you can set this setting to *System*, in which case the " -"search will happen within *all* tickets in the system, regardless of user " -"permissions." +"With third party authentications - but especially LDAP - you may want to " +"disable this function. Zammad **will not** change third party login " +"passwords and instead set or change the local password!" msgstr "" -#: ../settings/ticket.rst:225 ../settings/ticket.rst:227 -msgid "**🦺 Safety first!**" +#: ../settings/security/base.rst:56 +msgid "Password Login" msgstr "" -#: ../settings/ticket.rst:227 ../settings/ticket.rst:229 +#: ../settings/security/base.rst:60 msgid "" -"Even if the permission level is set to *System*, the user will not be shown " -"the tickets they don't have access to in the warning, even if they match." +"Activates the username & password login by default and if no third-party " +"login is activated. Disabling password login on the Zammad login page only " +"takes effect if you enable any :doc:`third-party`." msgstr "" -#: ../settings/ticket.rst:231 ../settings/ticket.rst:233 -msgid "" -"However, just the confirmation about the existence of the tickets in the " -"system may be considered an unwanted information disclosure. Use this option " -"carefully!" +#: ../settings/security/base.rst:64 +msgid "See :doc:`third-party` for supported third-party logins." +msgstr "" + +#: ../settings/security/base.rst:0 +msgid "Figure showing de-activated \"Password Login\" setting" msgstr "" -#: ../settings/ticket.rst:235 ../settings/ticket.rst:237 +#: ../settings/security/base.rst:77 msgid "" -"Finally, you can configure between matching within **All tickets** or **Open " -"tickets** only by setting **Match tickets in following states**. Depending " -"on the current ticket state, a ticket may or not be matched." +"To help administrators to overcome \"login issues\", Zammad automatically " +"offers a password request for administrator users. This allows you to adjust " +"Third-Party applications even if the login does no longer work!" msgstr "" -#: ../system/core-workflows.rst:2 -msgid "Core Workflows" +#: ../settings/security/base.rst:84 +msgid "Session Timeout" msgstr "" -#: ../system/core-workflows.rst:4 +#: ../settings/security/base.rst:86 msgid "" -"Core Workflows allow you to adjust object attributes in many ways. For " -"example:" +"All settings below by default are set to ``4 weeks``. Session Timeout " +"defines the life time of a users session. As soon as it's reached, Zammad " +"will automatically log off the session in question." msgstr "" -#: ../system/core-workflows.rst:7 -msgid "show / hide fields" +#: ../settings/security/base.rst:91 +msgid "" +"Zammad takes the highest value set assigned for the user based on the " +"permissions." msgstr "" -#: ../system/core-workflows.rst:8 -msgid "adjust mandatory setting" +#: ../settings/security/base.rst:94 +msgid "``admin``" msgstr "" -#: ../system/core-workflows.rst:9 -msgid "manipulate available options" +#: ../settings/security/base.rst:96 +msgid "``ticket.customer``" msgstr "" -#: ../system/core-workflows.rst:11 -msgid "" -"With this, you can provide exactly the information your users really need!" +#: ../settings/security/base.rst:97 +msgid "``default`` (fallback if user doesn't have above permissions set)" msgstr "" -#: ../system/core-workflows.rst:15 +#: ../settings/security/base.rst:99 msgid "" -"If the pre-defined :doc:`/system/objects` are not enough, please add them " -"beforehand." +"All settings act independently from each other allowing you to disable the " +"timeouts for e.g. admins, but not agents." msgstr "" -#: ../system/core-workflows.rst:17 -msgid "" -"If you experience slow or unreliable field updates, please see :ref:`Core " -"Workflow Ajax Modus `" -msgstr "" +#: ../settings/security/base.rst:115 +#: ../system/integrations/checkmk/api-reference.rst:13 +msgid "Example" +msgstr "例如" -#: ../system/core-workflows.rst:22 -msgid "" -"This is a very enhanced functionality and can cause unexpected UI behavior. " -"Please ensure to test your use cases after configuration to reduce surprises." +#: ../settings/security/base.rst:107 +msgid "Let's suppose you configured the following session timeouts" msgstr "" -#: ../system/core-workflows.rst:None -msgid "Dialogue for adding a new workflow" +#: ../settings/security/base.rst:104 +msgid "default: 3 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:2 -msgid "Core Workflow Condition Operators" +#: ../settings/security/base.rst:105 +msgid "admin: 2 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:4 -msgid "" -"You might know that there is a separate section for explaining :doc:" -"`condition operators `. Head over there to " -"see a detailed explanation of many conditions and operators." +#: ../settings/security/base.rst:106 +msgid "ticket.agent: 4 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:8 -msgid "" -"Due to differences to other places in Zammad which are also using conditions " -"(e.g. triggers), you can find a dedicated description of operators for core " -"workflows below." +#: ../settings/security/base.rst:107 +msgid "ticket.customer: 1 week" msgstr "" -#: ../system/core-workflows/condition-operators.rst:12 -msgid "" -"Be aware that the availability of the operators depends on the selected " -"attribute and its field type. Some of the operators may only be available " -"for system attributes (e.g. for \"tags\", \"active\")." +#: ../settings/security/base.rst:115 +msgid "This results in the following situations" msgstr "" -#: ../system/core-workflows/condition-operators.rst:20 -msgid "Operator" +#: ../settings/security/base.rst:110 +msgid "a user with ``admin`` permission will have a timeout of 2 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:22 -msgid "after (absolute)" +#: ../settings/security/base.rst:111 +msgid "" +"a user with ``admin`` and ``ticket.agent`` permissions will have a timeout " +"of 2 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:23 -msgid "Matches if a date/time is after a specific point in time." +#: ../settings/security/base.rst:113 +msgid "" +"a user with ``ticket.customer`` permission will have a timeout of 1 week" msgstr "" -#: ../system/core-workflows/condition-operators.rst:24 -msgid "after (relative)" +#: ../settings/security/base.rst:115 +msgid "" +"a user with neither ``admin``, ``ticket.agent`` nor ``ticket.customer`` " +"permissions will have a timeout of 3 weeks" msgstr "" -#: ../system/core-workflows/condition-operators.rst:25 -msgid "Matches if a time span after a specified event has passed." +#: ../settings/security/password.rst:4 +msgid "" +"This section allows you to define password requirements for the local user " +"accounts." msgstr "" -#: ../system/core-workflows/condition-operators.rst:26 -msgid "before (absolute)" +#: ../settings/security/password.rst:9 +msgid "" +"Zammad does **not** allow you to change your LDAP password, instead, it will " +"set a password in its local database which might confuse your users. This " +"might be addressed in the future by `#1169 `_." msgstr "" -#: ../system/core-workflows/condition-operators.rst:27 -msgid "Matches if a date/time is before a specific point in time." +#: ../settings/security/password.rst:14 +msgid "**Exception for admins**" msgstr "" -#: ../system/core-workflows/condition-operators.rst:28 -msgid "before (relative)" +#: ../settings/security/password.rst:16 +msgid "" +"Please note that below password policies *do not* affect administrators " +"setting passwords on user accounts. While this seems strange and not safe we " +"believe that an administrator knowing an user's password is insecure as well." msgstr "" -#: ../system/core-workflows/condition-operators.rst:29 -msgid "Matches if a time span after a specified event has not passed." +#: ../settings/security/password.rst:21 +msgid "The suggested workflow is either:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:30 -msgid "contains" +#: ../settings/security/password.rst:23 +msgid "" +"to use third party logins to not require local passwords at all **- or -**" msgstr "" -#: ../system/core-workflows/condition-operators.rst:31 -msgid "Matches if a specified value is present." +#: ../settings/security/password.rst:25 +msgid "to require your *user to reset the password* upon first login." msgstr "" -#: ../system/core-workflows/condition-operators.rst:33 -msgid "Matches if all of the specified values are present." +#: ../settings/security/password.rst:27 +msgid "" +"This way administrators are not required to set a user's password at all!" msgstr "" -#: ../system/core-workflows/condition-operators.rst:35 -msgid "Matches if none of the specified values are present." +#: ../settings/security/password.rst:31 +msgid "Maximum Failed Logins" msgstr "" -#: ../system/core-workflows/condition-operators.rst:36 -msgid "contains not" +#: ../settings/security/password.rst:33 +msgid "" +"You can choose a value between ``4`` and ``20``. This defines how often a " +"login to a user account may fail until Zammad will lock it. Your users can " +"always use the \"forgot password\" function to change their password and " +"unlock their account." msgstr "" -#: ../system/core-workflows/condition-operators.rst:37 -msgid "Matches if a specified value is not present." +#: ../settings/security/password.rst:38 +msgid "The default value is ``10``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:39 -msgid "Matches if one specified value is present." +#: ../settings/security/password.rst:42 +msgid "Beside changing the user's password, you can also unlock accounts via" msgstr "" -#: ../system/core-workflows/condition-operators.rst:41 -msgid "Matches if one specified value is not present." +#: ../settings/security/password.rst:44 +msgid ":ref:`user management list `" msgstr "" -#: ../system/core-workflows/condition-operators.rst:42 -msgid "does not match regex" +#: ../settings/security/password.rst:45 +msgid ":docs:`console `" msgstr "" -#: ../system/core-workflows/condition-operators.rst:43 -msgid "Matches if content doesn't fit to regex rule." +#: ../settings/security/password.rst:46 +msgid ":docs:`API `" msgstr "" -#: ../system/core-workflows/condition-operators.rst:44 -msgid "ends with" +#: ../settings/security/password.rst:50 +msgid "Failed logins via LDAP no longer lock accounts." msgstr "" -#: ../system/core-workflows/condition-operators.rst:45 -msgid "Matches if content ends with specified value." +#: ../settings/security/password.rst:53 +msgid "2 Lower Case And 2 Upper Case Characters" msgstr "" -#: ../system/core-workflows/condition-operators.rst:46 -msgid "ends with one of" +#: ../settings/security/password.rst:55 +msgid "" +"You can add complexity to passwords by enforcing at least 2 upper and lower " +"case characters." msgstr "" -#: ../system/core-workflows/condition-operators.rst:47 -msgid "Matches if content ends with one of the specified values." +#: ../settings/security/password.rst:58 ../settings/security/password.rst:83 +msgid "The default value is ``no``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:48 -msgid "from (relative)" +#: ../settings/security/password.rst:62 +msgid "Minimum Length" msgstr "" -#: ../system/core-workflows/condition-operators.rst:49 -msgid "Matches if date/time is after a period of time after an event." +#: ../settings/security/password.rst:64 +msgid "" +"This defines the minimum password length required for users to provide (from " +"``4`` to ``20``)." msgstr "" -#: ../system/core-workflows/condition-operators.rst:51 -msgid "Matches if content is equal to a specified value." +#: ../settings/security/password.rst:67 +msgid "The default value is ``6``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:52 -msgid "is any of" +#: ../settings/security/password.rst:71 +msgid "Digit Required" msgstr "" -#: ../system/core-workflows/condition-operators.rst:53 -msgid "Matches if content is equal to any of specified values." +#: ../settings/security/password.rst:73 +msgid "This enforces your users to use at least one digit within the password." msgstr "" -#: ../system/core-workflows/condition-operators.rst:54 -msgid "is modified" +#: ../settings/security/password.rst:75 +msgid "The default value is ``yes``." msgstr "" -#: ../system/core-workflows/condition-operators.rst:55 -msgid "Matches if content is modified." +#: ../settings/security/password.rst:78 +msgid "Special Character Required" msgstr "" -#: ../system/core-workflows/condition-operators.rst:57 -#: ../system/core-workflows/condition-operators.rst:61 -msgid "True from the moment of changing content until form submit." +#: ../settings/security/password.rst:80 +msgid "" +"This setting allows you to improve your password quality even more by " +"enforcing the password to contain at least one special character." msgstr "" -#: ../system/core-workflows/condition-operators.rst:58 -msgid "is modified to" +#: ../settings/security/ssl-certificates.rst:2 +msgid "SSL Certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:59 -msgid "Matches if content is modified to a specific value." +#: ../settings/security/ssl-certificates.rst:7 +msgid "" +"Zammad offers the possibility to upload custom certificates and custom " +"Certificate Authority (CA) certificates. This can be useful if you want to " +"connect Zammad the secure way to other systems which are using custom " +"certificates." msgstr "" -#: ../system/core-workflows/condition-operators.rst:62 -msgid "is none of" +#: ../settings/security/ssl-certificates.rst:12 +msgid "" +"An example usecase might be: You have an internal LDAP server that is not " +"accessible from the internet, and you want a SSL-encrypted connection, using " +"a custom certificate." msgstr "" -#: ../system/core-workflows/condition-operators.rst:63 -msgid "Matches if content is none of any specified values." +#: ../settings/security/ssl-certificates.rst:19 +msgid "" +"You should have an existing custom certificate file and/or a custom CA " +"certificate file, which you want to add to Zammad. As filetype ``.crt`` is " +"supported and the certificate format has to be PEM (Base64 ASCII)." msgstr "" -#: ../system/core-workflows/condition-operators.rst:65 -msgid "Matches if content is not equal to a specified value." +#: ../settings/security/ssl-certificates.rst:25 +msgid "" +"When you import a custom CA certificate, all certificates generated with " +"this are trusted. This can be useful if you have more than one system/" +"certificate you want to connect to and the certificates are issued from the " +"same custom CA." msgstr "" -#: ../system/core-workflows/condition-operators.rst:67 -msgid "Matches if content is present." +#: ../settings/security/ssl-certificates.rst:31 +msgid "Add a Certificate" msgstr "" -#: ../system/core-workflows/condition-operators.rst:68 -msgid "just changed" +#: ../settings/security/ssl-certificates.rst:33 +msgid "" +"To add a custom certificate or a custom CA certificate, head over to the " +"Admin panel > Settings > Security > SSL Certificates. Here you can find a " +"\"Add SSL Certificate\" button. In the dialog you can either select a " +"certificate file or paste the content of the certificate:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:69 -msgid "Matches if content has changed." +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate adding dialog" msgstr "" -#: ../system/core-workflows/condition-operators.rst:71 -#: ../system/core-workflows/condition-operators.rst:75 +#: ../settings/security/ssl-certificates.rst:43 msgid "" -"Only true for the moment of changing content until next form field action/" -"click." +"After selecting a file or pasting the content of the certificate, click on " +"the \"Add\" button to finally upload it to Zammad. Then, the certificates " +"are immediately effective, no restart or similar required." msgstr "" -#: ../system/core-workflows/condition-operators.rst:72 -msgid "just changed to" +#: ../settings/security/ssl-certificates.rst:49 +msgid "" +"Please note that only single certificate files are supported. That means if " +"you want to import a certificate / CA certificate, it must contain **only " +"one** certificate." msgstr "" -#: ../system/core-workflows/condition-operators.rst:73 -msgid "Matches if content has changed to a specified value." +#: ../settings/security/ssl-certificates.rst:54 +msgid "Certificate Overview" msgstr "" -#: ../system/core-workflows/condition-operators.rst:76 -msgid "matches regex" +#: ../settings/security/ssl-certificates.rst:56 +msgid "" +"After you added a certificate, you can see a table with information for each " +"added certificate:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:77 -msgid "Matches if value fits to regex rule." -msgstr "" - -#: ../system/core-workflows/condition-operators.rst:79 -msgid "Matches if no content is present." +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing table of added certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:80 -msgid "starts with" +#: ../settings/security/ssl-certificates.rst:64 +msgid "" +"Here you can download the certificate or delete it, if you don't need it " +"anymore." msgstr "" -#: ../system/core-workflows/condition-operators.rst:81 -msgid "Matches if content starts with specified value." +#: ../settings/security/ssl-certificates.rst:68 +msgid "Deleting Certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:82 -msgid "starts with one of" +#: ../settings/security/ssl-certificates.rst:70 +msgid "" +"If you want to delete a specific certificate, you can do it by clicking on " +"the menu in the actions column and selecting delete:" msgstr "" -#: ../system/core-workflows/condition-operators.rst:83 -msgid "Matches if content starts with one of the specified values." +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate deletion button" msgstr "" -#: ../system/core-workflows/condition-operators.rst:84 -msgid "till (relative)" +#: ../settings/security/ssl-certificates.rst:79 +msgid "Downloading Certificates" msgstr "" -#: ../system/core-workflows/condition-operators.rst:85 -msgid "Matches if date/time is before a period of time before an event." +#: ../settings/security/ssl-certificates.rst:81 +msgid "" +"If you want to download your certificates, you can do this as well via " +"corresponding action buttons." msgstr "" -#: ../system/core-workflows/condition-operators.rst:86 -msgid "today" +#: ../settings/security/ssl-certificates.rst:None +msgid "Screenshot showing certificate download button" msgstr "" -#: ../system/core-workflows/condition-operators.rst:87 -msgid "Matches if date/time is today." +#: ../settings/security/third-party.rst:13 +msgid "Login Providers" msgstr "" -#: ../system/core-workflows/condition-operators.rst:88 -msgid "within last (relative)" +#: ../settings/security/third-party.rst:2 +msgid "Third-Party Applications" msgstr "" -#: ../system/core-workflows/condition-operators.rst:89 +#: ../settings/security/third-party.rst:4 msgid "" -"Matches if date/time content is within specified period of time before now." +"Third party authentication is a great way to help your users to login to " +"Zammad more easily. If the account is yet unknown, Zammad will create a new " +"user automatically, without the user needed to interact (e.g. type in his " +"name). Another big advantage of this feature is that your user doesn't need " +"to remember another password." msgstr "" -#: ../system/core-workflows/condition-operators.rst:91 -msgid "within next (relative)" +#: ../settings/security/third-party.rst:10 +msgid "" +"You can deactivate logging in via :ref:`security_password_login` if any of " +"the mentioned authentication providers are enabled in your instance." msgstr "" -#: ../system/core-workflows/condition-operators.rst:92 +#: ../settings/security/third-party.rst:27 msgid "" -"Matches if date/time content is within specified period of time after now." +"We're currently missing documentation for the following login providers:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:2 -msgid "How do they work?" +#: ../settings/security/third-party.rst:29 +msgid "LinkedIn" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:4 -msgid "" -"Core Workflows are executed according to their priority. If two workflows " -"have the same priority, they are executed in alphabetical order based on " -"their **name**." +#: ../settings/security/third-party.rst:30 +msgid "Weibo" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:8 -msgid "" -"Because of the way Core Workflows work, all changes to attributes are " -"checked with the application server - please see :doc:`limitations` for " -"possible issues." +#: ../settings/security/third-party.rst:35 +msgid "Automatic Account Link on Initial Logon" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:12 +#: ../settings/security/third-party.rst:37 msgid "" -"Below we're talking about settings that are important and not self-" -"explanatory." +"In general there's two possible options for Zammad on how to deal with " +"already known users as they try to authenticate against a third-party " +"application. By default, Zammad will not automatically link \"unknown\" " +"authentication providers to existing accounts." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:17 +#: ../settings/security/third-party.rst:42 msgid "" -"Choose the object context you want to run the workflow in. This will decide " -"on your available attributes and actions." -msgstr "" - -#: ../system/core-workflows/how-do-they-work.rst:20 -msgid "Ticket objects also have access to the ticket customer." +"This means that the user has to manually link authentication providers to " +"their accounts (for more about this :user-docs:`consult the user " +"documentation `)." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:25 +#: ../settings/security/third-party.rst:46 msgid "" -"Choose in which situation the workflow is applied. Contexts can be combined " -"to avoid duplicate workflows." +"Sometimes this doesn't come in handy as this also means you'll receive error " +"messages about \"email address being in use already\" for (yet) unknown " +"third-party authentication methods." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:30 -msgid "Creation mask" +#: ../settings/security/third-party.rst:50 +msgid "" +"If you want to allow your users to always be able to log in, no matter what, " +"you may want to enable ``Automatic account link on initial logon``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:29 +#: ../settings/security/third-party.rst:None msgid "" -"If selected, your conditions and actions will affect all applicable creation " -"masks." +"Screenshot highlighting the \"Automatic account link on initial logon\"\n" +"setting" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:34 -msgid "Edit mask" +#: ../settings/security/third-party.rst:60 +msgid "Automatic Account Linking Notification" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:33 +#: ../settings/security/third-party.rst:64 msgid "" -"If selected, your conditions and actions will affect all applicable edit " -"masks." +"To improve security and your users awareness, you can enable Zammad to " +"notify your users when a new third-party application has been linked to " +"their account." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:39 +#: ../settings/security/third-party.rst:68 msgid "" -"Zammad differentiates between selected and saved conditions. These can be " -"combined wherever needed." +"This notification is sent out once per third-party application. Zammad does " +"also mention the method used, e.g.: ``Microsoft``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:42 -msgid "**⚠️ Restrict workflows to specific roles if needed!**" +#: ../settings/security/third-party.rst:71 +msgid "By default this setting is not active (set to ``no``)." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:44 +#: ../settings/security/third-party.rst:0 msgid "" -"By default and unless configured in conditions, workflow rules are executed " -"for **all roles**. This also affects your customers!" +"Screenshot showing sample notification mail after initial\n" +"third-party linking" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:50 -msgid "Selected Conditions" +#: ../settings/security/third-party.rst:85 +msgid "" +"This notification is only sent if the account in question already exists. If " +"the login via the third-party also creates the missing account, the " +"notification will be skipped." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:48 -msgid "" -"These conditions are based on form values and match if an appropriate " -"selection is made (e.g. choosing another group in the ticket without " -"saving). This applies for drafts (active selection) and currently saved " -"values." +#: ../settings/security/third-party.rst:89 +msgid "This means it only affects:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:64 -msgid "Saved Conditions" +#: ../settings/security/third-party.rst:91 +msgid "manual account linking within the third-party page of the users profile" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:53 +#: ../settings/security/third-party.rst:92 msgid "" -"These conditions only match if the selected values are stored in the " -"database. It ignores the current value or selection of the field, as long as " -"the changes are not saved (e.g. performing field operations for an existing " -"ticket, which is viewed/opened by an agent)." +"logging into an existing local account by utilizing the *automatic account " +"link on initial logon* functionality" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:60 +#: ../settings/security/third-party.rst:None msgid "" -"Keep in mind that the value has to be available in the situation where you " -"need it. Otherwise the condition won't match." +"Screenshot showing the \"automatic account linking notification\"\n" +"setting" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:63 -msgid "" -"Example: you can't perform any actions with *saved condition* on a ticket in " -"creation, because there are no saved values at that time." +#: ../settings/security/third-party.rst:100 +msgid "No User Creation on Logon" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:66 +#: ../settings/security/third-party.rst:102 msgid "" -"You can find a description of the condition operators for core workflows :" -"doc:`here `." +"By default, Zammad will create a new user account if the user logs in via a " +"third-party application and the account doesn't exist yet." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:72 +#: ../settings/security/third-party.rst:105 msgid "" -"Which actions should we run on the relevant fields? The possible actions " -"depend on the object type. However, usually you can at least change the " -"visibility and whether the field is mandatory." +"If you want to prevent Zammad from creating new accounts on logon, you can " +"disable this feature by setting ``No user creation on logon`` to ``yes``." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:76 -msgid "Be aware that actions are not available for **related** context." +#: ../settings/security/third-party.rst:None +msgid "Screenshot showing the \"no user creation on logon\" setting" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:78 +#: ../settings/security/third-party/facebook.rst:4 msgid "" -"**Example:** Let's assume you are working in the ticket context. While you " -"can have customer *conditions*, you *can't adjust* objects with actions in " -"that scope. That's because this wouldn't have any impact on the ticket " -"dialog. Of course all ticket attributes (state, owner, ...) are available." +"It is possible to create a quick login for your helpdesk via Facebook To do " +"so, you need to follow these steps:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:84 +#: ../settings/security/third-party/facebook.rst:9 +msgid "Register Facebook App" +msgstr "" + +#: ../settings/security/third-party/facebook.rst:11 msgid "" -"Please also have a look at our :doc:`limitations` to be safe from surprises." +"Visit [https://developers.facebook.com/apps/] and click on \"Add a new App\"" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:88 -msgid "Available Operators" +#: ../settings/security/third-party/facebook.rst:None +msgid "initial page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:90 -msgid "The availability of operators depends on the object type and scope." +#: ../settings/security/third-party/facebook.rst:17 +msgid "After that enter the app settings" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:94 -msgid "" -"Please note that actions may or may not restrict API based access to " -"attributes. We're displaying the following icons for your overview to " -"understand these limits better:" +#: ../settings/security/third-party/facebook.rst:None +msgid "Create App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:0 -msgid "|api| This icon indicates the action affects the API." +#: ../settings/security/third-party/facebook.rst:22 +msgid "Navigate to \"Settings\" and fill in this infromation" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:163 -msgid "api" +#: ../settings/security/third-party/facebook.rst:None +msgid "App Settings" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:0 -msgid "|ui| This icon indicates the action only affects the web interface." +#: ../settings/security/third-party/facebook.rst:27 +msgid "Navigate to app review and Check \"Make [appname] public?\"" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:167 -msgid "ui" +#: ../settings/security/third-party/facebook.rst:None +msgid "App Review" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:102 -msgid "show |ui|" +#: ../settings/security/third-party/facebook.rst:35 +msgid "Configure Zammad as Facebook App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:102 -msgid "Display the chosen field. Allows setting of values." -msgstr "" - -#: ../system/core-workflows/how-do-they-work.rst:109 -msgid "hide |ui|" +#: ../settings/security/third-party/facebook.rst:37 +msgid "" +"Navigate to \"Admin -> Security -> Third Party Applications\" and enter the " +"App ID and the App Secret. You can find this Key in the Dashbard of your " +"Facebok app." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:105 -msgid "" -"Hide the chosen field. However, it technically still allows setting the " -"field." +#: ../settings/security/third-party/facebook.rst:None +msgid "Zammad Configuration" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:108 +#: ../settings/security/third-party/facebook.rst:44 +#: ../settings/security/third-party/github.rst:43 +#: ../settings/security/third-party/gitlab.rst:46 msgid "" -"Please note that the field is **not** gone and still contains an existing " -"value (if set)! Consider *remove* instead, if you want this field to be gone." +"Now you can link accounts via \"Avatar -> Profile -> Link Accounts\" or " +"login via Zammad login page." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:112 -msgid "remove |ui|" +#: ../settings/security/third-party/github.rst:2 +#: ../system/integrations/github.rst:2 +msgid "GitHub" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:112 -msgid "Entirely removes the field. The field value will not be evaluated." +#: ../settings/security/third-party/github.rst:4 +msgid "" +"It is possible to create a quick login for your helpdesk via GitHub. To " +"activate the quick login you need to enable OAuth for GitHub." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:115 -msgid "set mandatory |ui| |api|" +#: ../settings/security/third-party/github.rst:8 +msgid "Register GitHub App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:115 -msgid "Sets the field to mandatory." +#: ../settings/security/third-party/github.rst:10 +msgid "" +"Visit https://www.github.com/settings/applications/new and enter the app " +"settings. As callback URL enter \"https://zammad_host/auth/github/callback\" " +"where zammad_host has to be replaced with your Zammad FQDN" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:118 -msgid "set optional |ui| |api|" +#: ../settings/security/third-party/github.rst:None +msgid "Register OAuth app on www.github.com" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:118 -msgid "Sets the field to optional." +#: ../settings/security/third-party/github.rst:19 +msgid "Configure Zammad as GitHub App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:124 -msgid "add option |ui| |api|" +#: ../settings/security/third-party/github.rst:21 +msgid "" +"Enter the \"APP ID\" and the \"APP SECRET\" from the GitHub OAUTH " +"Applications Dashboard" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:121 -msgid "Allows adding options to tree selects or selects." +#: ../settings/security/third-party/github.rst:None +msgid "GitHub config in Zammad admin interface" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:123 +#: ../settings/security/third-party/github.rst:28 msgid "" -"You have to use the \"remove option\" before performing this action. It " -"allows you to use *existing* configured values." +"After you configured the GitHub credentials and activated the login method, " +"you should see a new icon on the login page." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:128 -msgid "remove option |ui| |api|" +#: ../settings/security/third-party/github.rst:None +msgid "GitHub logo on login page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:127 +#: ../settings/security/third-party/github.rst:34 msgid "" -"Allows removing options from tree selects or selects. It allows you to use " -"*existing* configured values." +"If you click on the icon you will be redirected to GitHub and see something " +"similar to this:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:134 -msgid "set fixed to |ui| |api|" +#: ../settings/security/third-party/github.rst:None +msgid "GitHub oauth page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:131 -msgid "Reduces the available options by your selection." +#: ../settings/security/third-party/github.rst:40 +#: ../settings/security/third-party/gitlab.rst:42 +msgid "" +"When you grant the access you will be redirected to your Zammad instance and " +"logged in as a customer." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:133 -msgid "" -"This reduces your workflows in terms of *add option* and *remove option*." +#: ../settings/security/third-party/gitlab.rst:2 +msgid "Gitlab" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:137 -msgid "fill in |ui|" +#: ../settings/security/third-party/gitlab.rst:4 +msgid "" +"It is possible to create a quick login for your helpdesk via Gitlab. To " +"activate the quick login you need to enable OAuth for Gitlab." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:137 -msgid "Allows filling in of string and integer fields with your values." +#: ../settings/security/third-party/gitlab.rst:8 +msgid "Register Gitlab App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:141 -msgid "fill in empty |ui|" +#: ../settings/security/third-party/gitlab.rst:10 +msgid "To register an app in Gitlab open your profile and select applications." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:140 +#: ../settings/security/third-party/gitlab.rst:12 msgid "" -"Allows filling in of string and integer fields with your values **if the " -"field is empty**." +"As callback URL enter \"https://zammad-fqdn/auth/gitlab/callback\" where " +"zammad-fqdn has to be replaced with your Zammad FQDN" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:144 -msgid "select |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Register OAuth app on gitlab instance" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:144 -msgid "Select a specific value within a select, tree select or boolean field." +#: ../settings/security/third-party/gitlab.rst:18 +msgid "Just select *read_user* under scopes as in the screenshot and save it." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:153 -msgid "auto select |ui|" +#: ../settings/security/third-party/gitlab.rst:21 +msgid "Configure Zammad as Gitlab App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:147 -msgid "Helps users with tree select and select fields:" +#: ../settings/security/third-party/gitlab.rst:23 +msgid "" +"Enter the \"APP ID\" and the \"APP SECRET\" from the Gitlab OAUTH " +"Applications Dashboard and your Gitlab-URL in the \"SITE\" field." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:149 -msgid "" -"If the field has only one option available for selection and no value yet, " -"the value will be automatically set." +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab config in Zammad admin interface" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:152 +#: ../settings/security/third-party/gitlab.rst:30 msgid "" -"This option only works if you have one value and doesn't work if there is " -"more than one option available." +"After you configured the Gitlab credentials and activated the login method, " +"you should see a new icon on the login page." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:157 -msgid "set readonly |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab logo on login page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:156 +#: ../settings/security/third-party/gitlab.rst:36 msgid "" -"Allows you to display an attribute as read only (which means no changes are " -"possible)." +"If you click on the icon you will be redirected to Gitlab and see something " +"similar to this:" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:161 -msgid "unset readonly |ui|" +#: ../settings/security/third-party/gitlab.rst:None +msgid "Gitlab oauth page" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:160 +#: ../settings/security/third-party/google.rst:4 msgid "" -"In case a workflow set the field in question to read only, you can undo this " -"with option above." +"With some easy and fast steps, you can enable Zammad to authenticate your " +"users via Google." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:172 -msgid "Stop after match" +#: ../settings/security/third-party/google.rst:8 +msgid "Register a Google App" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:174 +#: ../settings/security/third-party/google.rst:10 msgid "" -"Here you can decide if other workflows are executed after the current one." +"First of all, we need to create a new project - you can skip this step if " +"you already have one." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:176 +#: ../settings/security/third-party/google.rst:15 msgid "" -"If set to ``no`` (default), further workflows will be executed if they match " -"the condition. In this case, it is possible that your actions from the " -"current workflow can be overwritten by another workflow." +"Use this link to create a new project: https://console.cloud.google.com/" +"projectcreate" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:180 +#: ../settings/security/third-party/google.rst:18 msgid "" -"If set to ``yes``, no further worflows will be executed after the current " -"one." +"Now expand the menu, expand \"APIs & Services\" and select \"Credentials\". " +"Go to the tab \"OAuth consent screen\" first and ensure to fill in the " +"requested information - without doing so you can't create credentials!" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:184 -msgid "Priority" +#: ../settings/security/third-party/google.rst:None +msgid "Creating a consent screen" msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:186 +#: ../settings/security/third-party/google.rst:25 msgid "" -"You can define the sequence, in which the workflows are executed. The " -"default value is ``500``." +"After filling in and saving the consent screen information, you can go to " +"the \"Credentials\" tab and create new \"OAuth client ID\"-Credentials." msgstr "" -#: ../system/core-workflows/how-do-they-work.rst:189 +#: ../settings/security/third-party/google.rst:28 msgid "" -"The workflows are executed in ascending order by their priority. That means " -"lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." +"Fill in the necessary information as follows and replace ``zammad_host`` " +"with your FQDN:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:2 -#, fuzzy -msgid "Learn by Example" -msgstr "例如" +#: ../settings/security/third-party/google.rst:31 +msgid "**Application type** ``[x] Web application``" +msgstr "" -#: ../system/core-workflows/learn-by-example.rst:4 -msgid "" -"This page provides some basic examples for Core Workflows. Of course you can " -"build much more complex workflows if needed." +#: ../settings/security/third-party/google.rst:34 +msgid "**Authorized JavaScript origins** ``https://zammad_host/``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:7 +#: ../settings/security/third-party/google.rst:37 msgid "" -"To learn about Core Workflows in detail, first go to :doc:`how-do-they-work`." +"**Authorized redirect URIs** ``https://zammad_host/auth/google_oauth2/" +"callback``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:10 -#, fuzzy -msgid "Group Based Examples" -msgstr "例如" +#: ../settings/security/third-party/google.rst:None +msgid "Adding a new OAuth client ID" +msgstr "" -#: ../system/core-workflows/learn-by-example.rst:12 +#: ../settings/security/third-party/google.rst:43 msgid "" -"All following workflows have the same base configurations. The workflow may " -"not use them all." +"After creating the credentials, go to your Zammad installation and navigate " +"to \"Admin > Security > Third Party Applications\" > Google. Enter your " +"Client ID and Client secret here." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:15 -#, fuzzy -msgid "Groups:" -msgstr "组" - -#: ../system/core-workflows/learn-by-example.rst:20 -msgid "Attributes:" +#: ../settings/security/third-party/google.rst:None +msgid "Zammad" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:22 -msgid "Category (Single tree selection field, not mandatory, agents only)" +#: ../settings/security/third-party/google.rst:50 +msgid "After submitting, the login via Google can be used." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:23 -msgid "" -"Approved (Boolean field, not mandatory, not shown, ``false`` as default)" +#: ../settings/security/third-party/microsoft.rst:2 +msgid "Microsoft" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:24 -msgid "Operating System (Text field, not mandatory, not shown)" -msgstr "" - -#: ../system/core-workflows/learn-by-example.rst:25 -msgid "Software used (Single selection field, not mandatory, not shown)" +#: ../settings/security/third-party/microsoft.rst:4 +msgid "" +"Zammad's Microsoft connection allows your users with Microsoft accounts to " +"login. This works for Azure users as well and can be an alternative to :doc:" +"`/system/integrations/ldap/index`." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:68 -msgid "Group specific values and fields" +#: ../settings/security/third-party/microsoft.rst:10 +msgid "" +"This documentation part does not cover our :doc:`📧 Microsoft 365 email " +"channel `." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:28 -msgid "" -"This workflow set depends on the category field. It reduces the available " -"set of values based on the group selected." +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screenshot showing Microsoft login button on Zammad login screen." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:33 -msgid "Workflow 2nd Level group" +#: ../settings/security/third-party/microsoft.rst:30 +#: ../settings/security/third-party/microsoft.rst:53 +msgid "Supported account types:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:35 +#: ../settings/security/third-party/microsoft.rst:22 msgid "" -"This reduces the category options to ``2nd Level/*``, ``Internal/*`` and " -"``Others``. It also sets further required fields to mandatory and visible." +"Please note that Zammad only supports these account types (App dependent):" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for 2nd level" +#: ../settings/security/third-party/microsoft.rst:35 +msgid "Avatars of signing in users:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:43 -msgid "Workflow Support group" +#: ../settings/security/third-party/microsoft.rst:33 +msgid "" +"Zammad currently ignores user avatars. If the user is registered with e.g. " +"Gravatar, Zammad will fetch the avatar from there if enabled. See :doc:" +"`Zammad Image Service ` for more." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:45 -msgid "" -"This reduces the category options to ``Support/*``, ``Internal/*`` and " -"``Others``. It also sets further required fields to visible." +#: ../settings/security/third-party/microsoft.rst:38 +msgid "Step 1 - Register a Microsoft App for Zammad" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for support" +#: ../settings/security/third-party/microsoft.rst:40 +msgid "" +"Login to the `Microsoft Azure Portal `_ and " +"navigate to App registrations to create a new app. Provide the requested " +"information as follows and register your app." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:53 -msgid "Workflow Sales group" +#: ../settings/security/third-party/microsoft.rst:46 +msgid "Name:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:55 +#: ../settings/security/third-party/microsoft.rst:45 msgid "" -"This reduces the category options to ``Sales/*``, ``Internal/*`` and " -"``Others``." +"Any meaningful name fitting, this name will be displayed to users trying to " +"authenticate with this app." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that shows specific values and fields for sales" +#: ../settings/security/third-party/microsoft.rst:49 +msgid "Choose one of the above mentioned account types (see Limitations)." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:68 -#: ../system/integrations/slack.rst:88 -msgid "The Result" +#: ../settings/security/third-party/microsoft.rst:51 +msgid "" +"The correct account type depends on your use case. If you want to use the " +"authentication internal only, choose the first option. If you're unsure, use " +"the \"Help me choose...\" link." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:63 -msgid "" -"This is what the agent would experience with the above workflows in place." +#: ../settings/security/third-party/microsoft.rst:58 +msgid "Redirect URI (optional):" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 +#: ../settings/security/third-party/microsoft.rst:56 msgid "" -"Workflow shows objects and limits options based on selections on the group" +"Select web and provide your callback URL. The callback URL looks like this: " +"``https://zammad.domain.tld/auth/microsoft_office365/callback``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:90 -msgid "Approval process" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to register a Microsoft app" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:71 -msgid "" -"In this case ``approved`` is visible to agents by default. For this " -"workflow, an additional role ``Approval person`` is required (no further " -"permissions)." +#: ../settings/security/third-party/microsoft.rst:71 +msgid "Within **API permissions** add the following permissions:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that restricts an approval attribute to specific roles" +#: ../settings/security/third-party/microsoft.rst:69 +msgid "``User.Read``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:81 -msgid "" -"This workflow may work best in combination with a :doc:`trigger ` but technically, this is not required." +#: ../settings/security/third-party/microsoft.rst:71 +msgid "Contacts" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:84 -msgid "" -"Select fields may be a better approach because they allow more values than " -"just a simple ``true`` or ``false``." +#: ../settings/security/third-party/microsoft.rst:71 +msgid "``Contacts.Read``" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 +#: ../settings/security/third-party/microsoft.rst:73 msgid "" -"Workflow fixes possible values of \"Approved ?\" to a specific selection " -"depending on the users role" +"You can find these permissions within *Microsoft Graph → Delegated " +"permissions*." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:103 -msgid "State dependent mandatory fields" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to add required API permissions" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:93 +#: ../settings/security/third-party/microsoft.rst:80 msgid "" -"This workflow sets ``Category`` to mandatory if the agent wants to set the " -"states ``closed`` or ``pending close`` to enforce categorization." +"Within **Certificates & secrets** create a new client secret. Note down the " +"returned secret **value** for later. **Do not** use the secret ID!" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Sample workflow that sets fields to mandatory on specific states" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to create a new app secret" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 +#: ../settings/security/third-party/microsoft.rst:88 msgid "" -"Workflow sets category field to mandatory upon choosing closed or pending " -"close as state" +"From **Overview** copy your apps *Application (client) ID*. If you're using " +"a single tenant app, please also copy *Directory (tenant) ID*. You now have " +"all required information for Zammad." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:106 -msgid "Manual Ticket Handover Process" +#: ../settings/security/third-party/microsoft.rst:None +msgid "Screencast showing how to retreive application client and tenant IDs" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:108 -msgid "This example covers the handover of a ticket from one agent to another:" +#: ../settings/security/third-party/microsoft.rst:98 +msgid "Step 2 - Add App Credentials to Zammad" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:110 +#: ../settings/security/third-party/microsoft.rst:100 msgid "" -"When the ticket owner is modified, a new text field (\"Handover\") shows up " -"for a comment" +"Navigate to Security > Third-party Applications (Tab) within Zammad's admin " +"settings. Scroll down to the section *Authentication via Microsoft* and fill " +"in the required information." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:112 -msgid "" -"This may only be visible when the owner is changed, therefore it has to be " -"hidden in general" +#: ../settings/security/third-party/microsoft.rst:105 +msgid "App ID:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:114 -msgid "The input in this handover text field is mandatory" +#: ../settings/security/third-party/microsoft.rst:105 +msgid "This is your *Application (client) ID*." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:115 -msgid "" -"After submitting changes, the value of the handover field must be added as " -"an note to the ticket (via trigger)" +#: ../settings/security/third-party/microsoft.rst:108 +msgid "App secret:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:121 -msgid "Hiding handover field" +#: ../settings/security/third-party/microsoft.rst:108 +msgid "This is your *client secret* (value)." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Hiding the handover field in core workflows" +#: ../settings/security/third-party/microsoft.rst:113 +msgid "App Tenant ID:" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:126 -msgid "Showing handover field and setting it to mandatory" +#: ../settings/security/third-party/microsoft.rst:111 +msgid "" +"**optional** only required for apps that use account type *Accounts in this " +"organizational directory only (Default Directory only - Single tenant).*" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Showing the handover field and set it as mandatory" +#: ../settings/security/third-party/microsoft.rst:115 +msgid "" +"Apply your settings by pressing submit and activate *Authentication via " +"Microsoft*." msgstr "" -#: ../system/core-workflows/learn-by-example.rst:131 -msgid "Trigger writing handover input to a new article" +#: ../settings/security/third-party/microsoft.rst:None +msgid "" +"Screencast showing how to add app credentials and activating the\n" +"authentication method" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:0 -msgid "Write handover content to a new article" +#: ../settings/security/third-party/saml.rst:2 +msgid "SAML" msgstr "" -#: ../system/core-workflows/learn-by-example.rst:133 +#: ../settings/security/third-party/saml.rst:4 msgid "" -"As a result, the ticket includes an article of the type note which includes " -"the predefined text and the handover comment." -msgstr "" - -#: ../system/core-workflows/limitations.rst:6 -msgid "Core Workflows do not replace Triggers" +"Connect your SAML (Security Assertion Markup Language) identity provider as " +"a single sign-on (SSO) method." msgstr "" -#: ../system/core-workflows/limitations.rst:5 +#: ../settings/security/third-party/saml.rst:7 msgid "" -"Workflows manipulate the behavior of fields. However, they do not set values " -"in fields because of actions." +"SAML is an open standard for SSO authentication (among other things). Sign-" +"ins are shared across multiple **service providers** and managed by a " +"central **identity provider** (IdP)." msgstr "" -#: ../system/core-workflows/limitations.rst:16 -msgid "API calls are only partly affected" +#: ../settings/security/third-party/saml.rst:11 +msgid "" +"In this case, the service provider is Zammad, and the IdP is a software " +"service that you either host or subscribe to (*e.g.,* `Keycloak `_, `Redhat SSO Server `_, `ADFS `_, or `Okta `_)." msgstr "" -#: ../system/core-workflows/limitations.rst:9 +#: ../settings/security/third-party/saml.rst:18 msgid "" -"Some options affect UI only and thus do not restrict responses and calls." +"This guide assumes you are already using SAML within your organization (i." +"e., that your IdP is fully set up)." msgstr "" -#: ../system/core-workflows/limitations.rst:11 -msgid "This affects the following actions:" +#: ../settings/security/third-party/saml.rst:21 +msgid "" +"Please note: Our instructions are based on connecting Zammad with Keycloak." msgstr "" -#: ../system/core-workflows/limitations.rst:13 -msgid "select" +#: ../settings/security/third-party/saml.rst:25 +msgid "Step 1: Configure Your IdP" msgstr "" -#: ../system/core-workflows/limitations.rst:14 -msgid "auto select" +#: ../settings/security/third-party/saml.rst:28 +msgid "Add Zammad as a Client/App" msgstr "" -#: ../system/core-workflows/limitations.rst:15 -msgid "show" +#: ../settings/security/third-party/saml.rst:30 +msgid "" +"Import Zammad into your IdP using the XML configuration found at ``https://" +"your.zammad.domain/auth/saml/metadata``." msgstr "" -#: ../system/core-workflows/limitations.rst:16 -msgid "hide" -msgstr "" - -#: ../system/core-workflows/limitations.rst:25 -msgid "Some fields stay unavailable to customers" -msgstr "" - -#: ../system/core-workflows/limitations.rst:19 -msgid "" -"For technical and security reasons, some default fields (the pale ones you " -"can't edit) stay unavailable for display and usage on customer permissions." -msgstr "" - -#: ../system/core-workflows/limitations.rst:23 +#: ../settings/security/third-party/saml.rst:33 msgid "" -"If you require your customers to change e.g. priorities, please consider " -"using workarounds via :doc:`/system/objects` and :doc:`/manage/trigger`." +"If your IdP doesn't support XML import, you will have to configure Zammad as " +"a new client/app manually using the above XML metadata file for reference." msgstr "" -#: ../system/core-workflows/limitations.rst:29 -msgid "Ticket title changes not supported in edit mask" +#: ../settings/security/third-party/saml.rst:36 +msgid "For instance, when you see this tag:" msgstr "" -#: ../system/core-workflows/limitations.rst:28 +#: ../settings/security/third-party/saml.rst:42 msgid "" -"It is currently not possible to perform changes of the ticket title in the " -"edit mask (e.g. renaming, set to read-only)." +"Set the **Assertion Consumer Service Binding URL** (sometimes also listed as " +"**Valid Redirect URIs**) to ``http://your.zammad.domain/auth/saml/callback``." msgstr "" -#: ../system/core-workflows/limitations.rst:37 -msgid "What is out of scope of Core Workflows?" +#: ../settings/security/third-party/saml.rst:47 +msgid "Set Up User Attribute Mapping" msgstr "" -#: ../system/core-workflows/limitations.rst:32 +#: ../settings/security/third-party/saml.rst:49 msgid "" -"There are some things that would count as workflow but are either done via :" -"doc:`/manage/trigger` or :doc:`/manage/scheduler`." +"Zammad requests the following user attributes (or “properties”) from the IdP:" msgstr "" -#: ../system/core-workflows/limitations.rst:35 -msgid "Such as (but not limited to):" +#: ../settings/security/third-party/saml.rst:51 +msgid "Email address (``email``)" msgstr "" -#: ../system/core-workflows/limitations.rst:37 -msgid "up- or downgrade permissions of users" +#: ../settings/security/third-party/saml.rst:52 +msgid "Full name (``name``)" msgstr "" -#: ../system/core-workflows/limitations.rst:38 -msgid "affecting article creation or listing" +#: ../settings/security/third-party/saml.rst:53 +msgid "Given name (``first_name``)" msgstr "" -#: ../system/data-privacy.rst:2 -msgid "Data Privacy" +#: ../settings/security/third-party/saml.rst:54 +msgid "Family name (``last_name``)" msgstr "" -#: ../system/data-privacy.rst:4 +#: ../settings/security/third-party/saml.rst:56 msgid "" -"For compliance with GDPR and other data privacy laws, you may wish to " -"**permanently delete users from the system**, along with **all of their " -"associated tickets**." +"You may need to set up “mappers” (or “mappings”) to tell your IdP how user " +"attributes in SAML correspond to those in Zammad. For a more detailed " +"breakdown, refer to the XML metadata file referenced in the previous section." 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 `!" +#: ../settings/security/third-party/saml.rst:62 +msgid "Per-IdP Instructions" msgstr "" -#: ../system/data-privacy.rst:12 -msgid "" -"Access to this panel requires ``admin.data_privacy`` permissions (introduced " -"in Zammad 3.5)." +#: ../settings/security/third-party/saml.rst:102 +msgid "Keycloak" msgstr "" -#: ../system/data-privacy.rst:15 +#: ../settings/security/third-party/saml.rst:65 msgid "" -"On older systems that have not been updated yet, customers can also be :docs:" -"`deleted via the Zammad console `." -msgstr "" - -#: ../system/data-privacy.rst:22 -msgid "User deletion dialog in the Data Privacy panel" +"**To add Zammad as a client,** save the XML configuration to disk (``https://" +"your.zammad.domain/auth/saml/metadata``) and use **Clients > Clients list > " +"Import client** in the Keycloak admin panel." msgstr "" -#: ../system/data-privacy.rst:22 +#: ../settings/security/third-party/saml.rst:70 msgid "" -"The user deletion dialog lists some of the tickets that will be removed from " -"the system along with the user." +"To help Zammad **match its own user accounts to Keycloak users**, create a " +"user attribute (or “property”) mapper. In **Clients list**, click on your " +"newly created Client ID, choose the tab **Client scopes** and click on the " +"link which refers to your Zammad instance. Choose **Add mapper > By " +"configuration > User Property** and create a mapper with the following " +"entries:" msgstr "" -#: ../system/data-privacy.rst:27 -msgid "Deleting Users via GUI" +#: ../settings/security/third-party/saml.rst:78 +msgid "**Name**" msgstr "" -#: ../system/data-privacy.rst:29 -msgid "🔥 **All deletions are FINAL!**" +#: ../settings/security/third-party/saml.rst:80 +msgid "**Mapper Type**" msgstr "" -#: ../system/data-privacy.rst:31 -msgid "Once you click “Delete”, the action cannot be canceled or undone." +#: ../settings/security/third-party/saml.rst:81 +msgid "``User Property``" msgstr "" -#: ../system/data-privacy.rst:33 -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." +#: ../settings/security/third-party/saml.rst:82 +msgid "**Property**" msgstr "" -#: ../system/data-privacy.rst:36 -msgid "**The following records cannot be deleted:**" +#: ../settings/security/third-party/saml.rst:83 +msgid "``emailAddress``" msgstr "" -#: ../system/data-privacy.rst:38 -msgid "your own account" +#: ../settings/security/third-party/saml.rst:84 +msgid "**SAML Attribute Name**" msgstr "" -#: ../system/data-privacy.rst:39 -msgid "the system's last remaining administrator account" +#: ../settings/security/third-party/saml.rst:86 +msgid "**SAML Attribute NameFormat**" msgstr "" -#: ../system/data-privacy.rst:42 -msgid "Step 1: Find a User / Confirm Deletion" +#: ../settings/security/third-party/saml.rst:87 +msgid "``basic``" msgstr "" -#: ../system/data-privacy.rst:44 -msgid "There are three ways to access the user deletion dialog:" +#: ../settings/security/third-party/saml.rst:89 +msgid "" +"In the example above, we're telling Zammad that whenever it receives a SAML " +"login request, it should take the ``email`` property from Keycloak, look for " +"a Zammad user with the same ``email`` attribute, and create a new session " +"for that user." msgstr "" -#: ../system/data-privacy.rst:51 -msgid "**from the user's profile**" +#: ../settings/security/third-party/saml.rst:95 +msgid "" +"If your Keycloak users' email addresses are stored on another property (*e." +"g.,* ``username``), adjust accordingly." msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Accessing the user deletion dialog in a user profile" +#: ../settings/security/third-party/saml.rst:98 +msgid "" +"Back in **Settings**, enter the Client ID (``https://your.zammad.domain/auth/" +"saml/metadata``) in the field **Master SAML Processing URL**." msgstr "" -#: ../system/data-privacy.rst:51 -msgid "Click **Action > Delete**." +#: ../settings/security/third-party/saml.rst:101 +msgid "You also need to enable **Sign assertions**." msgstr "" -#: ../system/data-privacy.rst:58 -msgid "**in the “Manage > Users” Admin Panel**" +#: ../settings/security/third-party/saml.rst:105 +msgid "Step 2: Configure Zammad" msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Accessing the user deletion dialog under “Users” in the Admin Panel" +#: ../settings/security/third-party/saml.rst:107 +msgid "" +"Enable SAML and enter your IdP's details in the Admin Panel under **Settings " +"> Security > Third Party Applications > Authentication via SAML**:" msgstr "" -#: ../system/data-privacy.rst:58 -msgid "Use the **⋮ Actions** menu for the target user." +#: ../settings/security/third-party/saml.rst:None +msgid "Example configuration of SAML part 1" msgstr "" -#: ../system/data-privacy.rst:66 ../system/data-privacy.rst:104 -msgid "**in the “System > Data Privacy” Admin Panel**" +#: ../settings/security/third-party/saml.rst:119 +msgid "Display name" msgstr "" -#: ../system/data-privacy.rst:0 +#: ../settings/security/third-party/saml.rst:116 msgid "" -"Accessing the user deletion dialog under “Data Privacy” in the Admin Panel" +"Allows you to define a custom button name for SAML. This helps your users to " +"understand better what the button on the login page does." msgstr "" -#: ../system/data-privacy.rst:65 -msgid "" -"Use the **New Deletion Task** button. Search for users by name or email " -"address." +#: ../settings/security/third-party/saml.rst:119 +msgid "Defaults to ``SAML``." msgstr "" -#: ../system/data-privacy.rst:79 -msgid "**Delete organizations**" +#: ../settings/security/third-party/saml.rst:123 +msgid "IDP SSO target URL" msgstr "" -#: ../system/data-privacy.rst:69 +#: ../settings/security/third-party/saml.rst:122 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:" +"This is the target URL Zammad shall redirect to when the user presses the " +"SAML button. For Keycloak, this needs to look like https://your.domain/" +"realms/your-realm/protocol/saml" msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Deleting an organization via the user deletion dialog" +#: ../settings/security/third-party/saml.rst:127 +msgid "IDP single logout target URL" msgstr "" -#: ../system/data-privacy.rst:78 +#: ../settings/security/third-party/saml.rst:126 msgid "" -"If this option does not appear, make sure there are no pending deletion " -"tasks for other customers from this organization." +"This is the URL to which the single logout request and response should be " +"sent." msgstr "" -#: ../system/data-privacy.rst:82 -msgid "Step 2: Monitor Deletion Job Status" +#: ../settings/security/third-party/saml.rst:131 +msgid "IDP certificate" msgstr "" -#: ../system/data-privacy.rst:84 +#: ../settings/security/third-party/saml.rst:130 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:" -msgstr "" - -#: ../system/data-privacy.rst:98 -msgid "**in the Activity Stream**" +"The public certificate of your IDP for Zammad to verify during the callback " +"phase." msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Activity Stream showing data privacy tasks" +#: ../settings/security/third-party/saml.rst:145 +msgid "IDP certificate fingerprint" msgstr "" -#: ../system/data-privacy.rst:94 +#: ../settings/security/third-party/saml.rst:134 msgid "" -"For each deleted user, the Activity Stream will be updated twice—once when " -"the task is created, and once when it's complete." +"The fingerprint of your IDPs public certificate to verify during callback " +"phase." msgstr "" -#: ../system/data-privacy.rst:97 -msgid "" -"These notifications are only visible to users with ``admin.data_privacy`` " -"permissions." +#: ../settings/security/third-party/saml.rst:137 +msgid "🔏 **For the IdP certificate / certificate fingerprint:**" msgstr "" -#: ../system/data-privacy.rst:0 +#: ../settings/security/third-party/saml.rst:139 msgid "" -"The task list within Data Privacy shows removals being in progress and " -"completed." +"Provide **only one or the other**—do not provide both! (Between the two, we " +"recommend the signing certificate itself: fingerprints use SHA-1, which `has " +"been broken for a while now `_.)" msgstr "" -#: ../system/data-privacy.rst:107 -msgid "Frequently Asked Questions" +#: ../settings/security/third-party/saml.rst:144 +msgid "" +"**Keycloak users:** Find your certificate in the Keycloak admin panel under " +"**Realm Settings > Keys > Algorithm: RS256 > Certificate**." msgstr "" -#: ../system/data-privacy.rst:121 -msgid "What happens if I receive an email from a deleted customer?" +#: ../settings/security/third-party/saml.rst:151 +msgid "Name identifier format" msgstr "" -#: ../system/data-privacy.rst:110 +#: ../settings/security/third-party/saml.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." +"This is the unique identifiers field type. Usually it should be ``urn:oasis:" +"names:tc:SAML:1.1:nameid-format:emailAddress``." msgstr "" -#: ../system/data-privacy.rst:115 -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**." +#: ../settings/security/third-party/saml.rst:151 +msgid "Zammad **expects an email address as unique identifier**!" msgstr "" -#: ../system/data-privacy.rst:130 -msgid "What about user information stored in internal notes or other messages?" +#: ../settings/security/third-party/saml.rst:155 +msgid "UID attribute name" msgstr "" -#: ../system/data-privacy.rst:124 +#: ../settings/security/third-party/saml.rst:154 msgid "" -"The deletion process removes **user accounts and associated tickets only**." +"Here you can define an attribute that uniquely identifies the user. If " +"unset, the name identifier returned by the IDP is used." msgstr "" -#: ../system/data-privacy.rst:126 +#: ../settings/security/third-party/saml.rst:None +msgid "Example configuration of SAML part 2" +msgstr "" + +#: ../settings/security/third-party/saml.rst:163 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." +"Decide if the certificate for the connection to the IdP service has to be " +"verified or not (default: ``yes``)." msgstr "" -#: ../system/data-privacy.rst:137 -msgid "I deleted an user and can still see a message they sent!" +#: ../settings/security/third-party/saml.rst:169 +msgid "Signing & Encrypting" msgstr "" -#: ../system/data-privacy.rst:133 +#: ../settings/security/third-party/saml.rst:169 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." +"Define if you want to sign, encrypt, do both or nothing for the requests." msgstr "" -#: ../system/data-privacy.rst:141 -msgid "I removed a customer, now my reporting is off!" +#: ../settings/security/third-party/saml.rst:179 +msgid "Certificate (PEM)" msgstr "" -#: ../system/data-privacy.rst:140 +#: ../settings/security/third-party/saml.rst:172 msgid "" -"When removing users and their tickets, all references are removed. This also " -"affects e.g. Reporting - these information are lost." +"Paste the public certificate of your Zammad SAML client, if you want to " +"encrypt the requests." msgstr "" -#: ../system/data-privacy.rst:145 -msgid "How long does Zammad store created tasks?" +#: ../settings/security/third-party/saml.rst:175 +msgid "Make sure the certificate is:" msgstr "" -#: ../system/data-privacy.rst:144 -msgid "" -"Please see the on-premise data section of the :docs:`data privacy ` chapter." +#: ../settings/security/third-party/saml.rst:177 +msgid "already valid and not yet expired" msgstr "" -#: ../system/data-privacy.rst:150 -msgid "What about re-assigned tickets? I want to delete them, too." +#: ../settings/security/third-party/saml.rst:178 +msgid "no CA certificate" msgstr "" -#: ../system/data-privacy.rst:148 -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." +#: ../settings/security/third-party/saml.rst:179 +msgid "valid for signing and encrypting" msgstr "" -#: ../system/data-privacy.rst:154 -msgid "Why are there so many deletion task entries, I didn't create them!" +#: ../settings/security/third-party/saml.rst:185 +msgid "Private key (PEM)" msgstr "" -#: ../system/data-privacy.rst:153 +#: ../settings/security/third-party/saml.rst:182 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." -msgstr "" - -#: ../system/integrations/checkmk/admin-panel-reference.rst:2 -msgid "Admin Panel Reference" +"Paste the private key of your Zammad SAML client here, if you want to sign " +"the requests." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:None -msgid "Screenshot of Checkmk settings overview" +#: ../settings/security/third-party/saml.rst:185 +msgid "Make sure the key is an RSA key with a length of at least 2048 bits." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:12 -msgid "" -"Which :doc:`group ` should Checkmk tickets be assigned " -"to as a default (*i.e.,* when none is specified)?" +#: ../settings/security/third-party/saml.rst:188 +msgid "Private key secret" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:15 -msgid "(Applies to :ref:`API alerts ` only.)" +#: ../settings/security/third-party/saml.rst:188 +msgid "If your private key is secured with a secret, you can provide it here." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:21 -msgid "Auto close" +#: ../settings/security/third-party/saml.rst:192 +msgid "Your callback URL" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:18 +#: ../settings/security/third-party/saml.rst:191 msgid "" -"Should Zammad automatically close tickets if a service has recovered on its " -"own?" +"This URL is needed for your IdP configuration so it knows where to redirect " +"to after successful authentication." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:21 -msgid "(Agents will receive notifications for such closures as appropriate.)" +#: ../settings/security/third-party/saml.rst:194 +msgid "" +"After saving your input by clicking on the \"Submit\" button, Zammad " +"verifies the provided keys/certificates (e.g. if they are valid for signing/" +"encrypting and if they aren't expired)." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:30 -msgid "Auto-close state" +#: ../settings/security/third-party/saml.rst:199 +msgid "" +"See :ref:`automatic account linking ` for details " +"on how to link existing Zammad accounts to IdP accounts." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:24 -msgid "What ticket state should be applied when “auto-closing” a ticket?" +#: ../settings/security/third-party/saml.rst:205 +msgid "Automatic account linking doesn't work" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:26 +#: ../settings/security/third-party/saml.rst:206 msgid "" -"You can choose from the seven built-in ticket states. If these states aren't " -"enough for you, you can :ref:`define a new ticket state ` for this purpose as well. This can be useful for tracking " -"tickets with :doc:`reports `, for example." +"Have you double-checked your IdP's user attribute mapping configuration?" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:35 -#: ../system/integrations/cti/includes/recent-logs.include.rst:2 -#: ../system/integrations/ldap/index.rst:74 -#: ../system/integrations/pgp/index.rst:106 -msgid "Recent Logs" +#: ../settings/security/third-party/twitter.rst:4 +msgid "" +"It is possible to create a quick login for your helpdesk via Twitter. To do " +"so, you need to follow these steps:" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:None -msgid "Screenshot of Checkmk \"Recent Logs\" section" +#: ../settings/security/third-party/twitter.rst:8 +msgid "Register Twitter App" msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:41 -msgid "" -"If you're having trouble getting Zammad and Checkmk to play nicely together, " -"this section can help you troubleshoot." +#: ../settings/security/third-party/twitter.rst:10 +msgid "Go to https://dev.twitter.com/apps and login with your account." msgstr "" -#: ../system/integrations/checkmk/admin-panel-reference.rst:44 -msgid "" -"It contains a record of the fifty most recent transactions that Zammad knows " -"about, including each one's request/response details and return status." +#: ../settings/security/third-party/twitter.rst:15 +msgid "Click on \"Create App\"" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:2 -msgid "API Reference" +#: ../settings/security/third-party/twitter.rst:None +msgid "new app page" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:4 +#: ../settings/security/third-party/twitter.rst:20 msgid "" -"For most users, :ref:`the sample scripts from the Setup Guide ` will do the job just fine. But if you want more fine-grained control" -"—for instance, to create high- and low-priority tickets for different types " -"of system events—then you'll have to customize the data those scripts send " -"to Zammad." +"Enter app settings. As \"Callback URL\" you need to enter ``https://" +"zammad_host/api/v1/external_credentials/twitter/callback``. You need to " +"replace ``zammad_host`` with the domain of your Zammad system." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:15 +#: ../settings/security/third-party/twitter.rst:24 msgid "" -"This custom script will automatically set all tickets it creates to **high " -"priority** and **assign them to charlie@chrispresso.com**." +"After the app has been created, update the application icon and organization " +"attributes." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:32 -msgid "How Does it Work?" +#: ../settings/security/third-party/twitter.rst:None +msgid "set permissions to receive and send direct messages" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:34 +#: ../settings/security/third-party/twitter.rst:30 msgid "" -"There are two kinds of data you can pass to the API, both in the form of key-" -"value pairs:" +"Next we need to set ``read, write and access direct messages`` permissions " +"for the app." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:44 -msgid "Checkmk parameters" +#: ../settings/security/third-party/twitter.rst:None +msgid "click on Keys & Access Token, note them" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:38 +#: ../settings/security/third-party/twitter.rst:36 msgid "" -"are required, and make up the **contents** of the resulting tickets/" -"articles. They also determine whether an event creates a new ticket or " -"updates/closes an existing one." +"Go to \"Keys and Access Token\" tab and note the \"Consumer Key\" and " +"\"Consumer Secret\"." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:42 +#: ../settings/security/third-party/twitter.rst:40 +msgid "Configure Zammad as Twitter App" +msgstr "" + +#: ../settings/security/third-party/twitter.rst:42 msgid "" -"These are the only values used in the sample scripts. **Use them as-is**; " -"technically, they can be customized, but it's hard to imagine a good reason " -"for it." +"Go to \"Admin > Security > Twitter > Third Party Applications > Twitter\" " +"Section." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:52 -msgid "Ticket attributes" +#: ../settings/security/third-party/twitter.rst:None +msgid "Admin > Security > Third Party Applications" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:47 +#: ../settings/security/third-party/twitter.rst:48 msgid "" -"are optional, and can be used to **adjust settings** on newly created " -"tickets (*e.g.,* set the owner, group, priority, or state)." +"Fill in the \"Twitter Key\" and the \"Twitter Secret\" and click the " +"\"Submit\" button." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:50 +#: ../settings/security/third-party/twitter.rst:51 msgid "" -"If you want to customize your Checkmk alert script, do it with these. Simply " -"add an extra “form” option for each one (``-F \"key=value\"``) to your " -"script's ``curl`` command line, as in the example above." +"Now you can link accounts via \"Avatar > Profile > Link Accounts\" or login " +"via Zammad login page." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:54 -msgid "💡 **It's just an API endpoint!**" +#: ../settings/security/two-factor.rst:11 +msgid "Two-factor Authentication Methods" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:56 -msgid "" -"When using Checkmk integration, messages need to be formatted in a certain " -"way, but that *doesn't mean the messages actually have to come from Checkmk*." +#: ../settings/security/two-factor.rst:2 +msgid "Two-Factor Authentication" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:59 +#: ../settings/security/two-factor.rst:4 msgid "" -"If you use another monitoring tool that's not officially supported by " -"Zammad, there's probably a way to make it work with your Checkmk callback " -"URL." +"Two-factor authentication (2FA) enhances the security of Zammad accounts by " +"adding an extra layer of verification beyond a password. It requires users " +"to provide two different types of authentication factors, typically " +"something they know (like a password) and something they possess (like a " +"mobile device or a security token), to ensure that only authorized " +"individuals can access the account." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:63 -msgid "Checkmk Parameters" +#: ../settings/security/two-factor.rst:19 +msgid "Enable Recovery Codes" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:65 +#: ../settings/security/two-factor.rst:21 msgid "" -"When a notification is received, Zammad creates a new article containing the " -"details of the event that triggered it:" +"Recovery codes are one-time use security codes that can be used by the user " +"if they lose access to their other two-factor authentication methods. They " +"cannot be used on their own, they can only be activated if at least one two-" +"factor authentication method is enabled." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:None -msgid "Checkmk article body" +#: ../settings/security/two-factor.rst:None +msgid "Enable Recovery Codes Setting" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:72 +#: ../settings/security/two-factor.rst:30 msgid "" -"These details come from the fields listed below, which correspond to " -"parameters provided by Checkmk (``$NOTIFY_*``)." +"Recovery codes can only be used as a backup method. If enabled, they will be " +"automatically generated for the user once they set up their initial two-" +"factor authentication method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:75 -msgid "**Required fields are marked with an asterisk (\\*).**" +#: ../settings/security/two-factor.rst:34 +msgid "" +"The user will be asked to print out or save the generated recovery codes in " +"a safe place. Once used, a recovery code cannot be reused." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:79 -msgid "event_id\\*" +#: ../settings/security/two-factor.rst:37 +msgid "" +"Users will also have an option to regenerate their recovery codes at any " +"time, which invalidates already existing recovery codes and provides them " +"with a list of fresh codes." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:78 +#: ../settings/security/two-factor.rst:41 msgid "" -"A unique ID for the system event. (``$NOTIFY_SERVICEPROBLEMID`` / " -"``$NOTIFY_HOSTPROBLEMID``)" +"After you enable this setting, when the user completes a setup of their " +"initial two-factor authentication method, they will be presented with a list " +"of recovery codes and instructed to save them for later use." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:86 -msgid "host\\*" +#: ../settings/security/two-factor.rst:None +msgid "Recovery Codes Generation Modal Dialog" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:82 -msgid "" -"The hostname of the system that the event originated from. " -"(``$NOTIFY_HOSTNAME``)" +#: ../settings/security/two-factor.rst:50 +msgid "Enforce the Set Up of the Two-Factor Authentication" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:85 +#: ../settings/security/two-factor.rst:52 msgid "" -"Used to determine if a new event belongs to an existing ticket. Also used in " -"the subject line of the resulting article (“ is ”)." +"In case you wish to require your users to set up at least one two-factor " +"authentication method for their account, you can do this by selecting " +"specific user roles the requirement applies to in **Enforced for user " +"roles** setting. Of course you must have at least one two-factor " +"authentication method enabled for this setting to take effect." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:96 -msgid "service" +#: ../settings/security/two-factor.rst:None +msgid "Enforced for User Roles Setting" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:89 +#: ../settings/security/two-factor.rst:62 msgid "" -"The name of the service that the event originated from. " -"(``$NOTIFY_SERVICEDESC``)" +"After you change this setting, if the user has one of the selected roles on " +"their account, they will be forced to set up the two-factor authentication " +"upon next sign in or application reload." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:92 -msgid "Used to determine if a new event belongs to an existing ticket." +#: ../settings/security/two-factor.rst:66 +msgid "" +"A modal dialog with instructions will be shown, and they will not be able to " +"do any work before they set up at least one two-factor method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:94 -#: ../system/integrations/checkmk/api-reference.rst:110 -msgid "Displayed as ``-`` when omitted." +#: ../settings/security/two-factor.rst:None +msgid "Modal Dialog for Enforcing Two-Factor Authentication Set Up" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:104 -msgid "state\\*" +#: ../settings/security/two-factor.rst:74 +msgid "Reset Two-Factor Authentication for a Specific User" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:99 +#: ../settings/security/two-factor.rst:76 msgid "" -"The current state of the service or host in question. " -"(``$NOTIFY_SERVICESTATE`` / ``$NOTIFY_HOSTSTATE``)" +"In case an user isn't able to login anymore because of an inaccessible " +"second factor, you can reset the user's 2FA method." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:102 +#: ../settings/security/two-factor.rst:79 msgid "" -"Used to detect when a ticket should be auto-closed (*i.e.,* on ``OK``/" -"``UP``). Also used in the subject line of the resulting article (“ is " -"”)." +"To do this, go to the user management and search for the relevant user. " +"After you found the account, click the button in the action column and " +"select \"Manage Two-Factor Authentication\":" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:110 -msgid "text" +#: ../settings/security/two-factor.rst:None +msgid "Context menu in action column in user management" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:107 +#: ../settings/security/two-factor.rst:87 msgid "" -"The output of the process that triggered the event. " -"(``$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" +"After selecting this, you can see a dialog where you can either reset one " +"2FA method or reset all of the user's 2FA methods:" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:121 +#: ../settings/security/two-factor.rst:None +msgid "Dialog for resetting user's 2FA method" +msgstr "" + +#: ../settings/security/two-factor.rst:94 msgid "" -"The Object Manager attribute panel displays built-in and custom\n" -"attribute names." +"Choose the fitting one, click on the corresponding \"Remove ...\" button and " +"confirm your action. The user now has to setup a new 2FA method, depending " +"on your 2FA configuration." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:121 -msgid "Find a complete list of ticket attributes in the Object Manager." +#: ../settings/security/two-factor/authenticator-app.rst:2 +msgid "Authenticator App" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:123 +#: ../settings/security/two-factor/authenticator-app.rst:4 msgid "" -"Ticket attributes are entirely optional, and can be used to customize the " -"tickets that Checkmk creates. (Note that these attributes will be ignored if " -"a new event belongs to an existing ticket.)" +"The authenticator app method is a type of two-factor authentication that " +"uses a mobile application to generate one-time codes for account " +"verification. After setting up the authenticator app on their device, the " +"user links it to their Zammad account." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:128 +#: ../settings/security/two-factor/authenticator-app.rst:12 msgid "" -"Why would you want to do this? Maybe you have only one IT guy, and all " -"system monitoring issues should be automatically assigned to him. Or, maybe " -"you're creating multiple notification rules so that database outages take " -"higher priority than disk space warnings." +"When logging in, the user is prompted to enter a time-sensitive code " +"generated by the app, in addition to their password. This code acts as the " +"second factor of authentication, providing an extra layer of security as it " +"changes periodically and is unique to the user's device." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:135 -msgid "In most cases, you'll probably want to set one of the following:" +#: ../settings/security/two-factor/authenticator-app.rst:None +msgid "Security Code in Google Authenticator App" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:137 -msgid "group" -msgstr "组" - -#: ../system/integrations/checkmk/api-reference.rst:139 -msgid "state" -msgstr "状态" - -#: ../system/integrations/checkmk/api-reference.rst:140 -msgid "priority" -msgstr "优先级" - -#: ../system/integrations/checkmk/api-reference.rst:142 +#: ../settings/security/two-factor/authenticator-app.rst:22 msgid "" -"but in practice, you can set almost any attribute, including :doc:`custom " -"ones you created through the Object Manager `." +"The app generates codes based on a shared secret key stored securely on both " +"the user's device and the server, ensuring a synchronized and secure " +"authentication process. The method of generating the codes is sometimes also " +"called TOTP (time-based one-time password)." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:145 -msgid "Please note that the following attributes are **not customizable**:" +#: ../settings/security/two-factor/authenticator-app.rst:28 +msgid "Enabling the Authenticator App Method" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:147 -msgid "title" +#: ../settings/security/two-factor/authenticator-app.rst:30 +#: ../settings/security/two-factor/security-keys.rst:28 +msgid "To enable the method, just toggle the switch on in the settings." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:148 -msgid "id" +#: ../settings/security/two-factor/authenticator-app.rst:None +msgid "Authenticator App Switch in Settings" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:149 -msgid "ticket number" +#: ../settings/security/two-factor/authenticator-app.rst:36 +msgid "" +"Now the users will be able to set up this two-factor authentication method " +"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " +"Once they do, on next sign-in with password, they will be asked to provide " +"an additional security code generated by their mobile device." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:151 -msgid "created_by_id" +#: ../settings/security/two-factor/security-keys.rst:2 +msgid "Security Keys" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:152 -msgid "updated_by_id" +#: ../settings/security/two-factor/security-keys.rst:4 +msgid "" +"The security keys method is a type of a two-factor authentication that uses " +"Web Authentication API in the browser for verifying user's identity. The " +"user can register multiple hardware or software security keys with their " +"Zammad account and then they can use it during the sign-in process." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:155 -msgid "Which Values Can Be Set?" +#: ../settings/security/two-factor/security-keys.rst:12 +msgid "" +"When logging in, the user is prompted to provide the same security key they " +"registered with their account, in addition to their password. This key acts " +"as the second factor of authentication, providing an extra layer of security." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:157 -msgid "😵 **Invalid values → unpredictable behavior**" +#: ../settings/security/two-factor/security-keys.rst:None +msgid "Security Key dialog in Safari on macOS" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:159 +#: ../settings/security/two-factor/security-keys.rst:21 msgid "" -"If you provide a value that Zammad doesn't understand (*e.g.,* ``-F " -"\"priority=high\"``), it's not always clear what will happen. In some cases, " -"a ticket will be created with the default values instead - but in others, it " -"may not be created at all!" +"The type of the key can range from hardware USB sticks to passkeys stored in " +"a device of user's choice. Which type can be used depends on the browser " +"flavor and the platform of the user." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:164 -msgid "So what values does Zammad understand, then? Well, it depends..." +#: ../settings/security/two-factor/security-keys.rst:26 +msgid "Enabling the Security Keys Method" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:168 -msgid "Use an email address or username:" +#: ../settings/security/two-factor/security-keys.rst:None +msgid "Security Keys Switch in Settings" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:190 -msgid "group & priority" +#: ../settings/security/two-factor/security-keys.rst:34 +msgid "" +"Now the users will be able to set up this two-factor authentication method " +"for their accounts via \"Avatar -> Profile -> Password & Authentication\". " +"Once they do, on next sign-in with password, they will be asked to provide " +"the same security key they registered during the setup." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:175 -msgid "Refer to the dropdown menus in the ticket pane:" +#: ../settings/system/system-selfhosted.include.rst:3 +msgid "" +"Below settings are only available to self hosted users. In hosted " +"environments we're handling these settings for you to ensure service " +"stability." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:0 -msgid "See possible values for certain attributes in the ticket pane." +#: ../settings/system/base.rst:11 +msgid "Fully Qualified Domain Name" msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:187 -msgid "🙅 **Ticket state CANNOT be set this way!**" +#: ../settings/system/base.rst:7 +msgid "The URL of your Zammad installation." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:189 -msgid "" -"Why? Because ``-F \"state=...\"`` is already used :ref:`as a Checkmk " -"parameter `." -msgstr "" - -#: ../system/integrations/checkmk/api-reference.rst:222 -msgid "Everything Else" +#: ../settings/system/base.rst:9 ../settings/system/base.rst:17 +msgid "This setting is used within :doc:`/misc/variables` and notifications." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:193 -msgid "" -"To set any other attributes, it helps to know your way around the :docs:" -"`rails console `. Valid values are those that you can " -"set with a string:" +#: ../settings/system/system-base.include.rst:1 +msgid "It is automatically set by the *Getting Started wizard*." msgstr "" -#: ../system/integrations/checkmk/api-reference.rst:218 -msgid "These values can then be passed directly to the API:" +#: ../settings/system/system-base.include.rst:5 +msgid "Changing this setting also changes callback URLs for your channels etc." msgstr "" -#: ../system/integrations/checkmk/index.rst:16 -msgid "How does it work?" +#: ../settings/system/system-base.include.rst:6 +msgid "This setting can have negative affects on being able to login." msgstr "" -#: ../system/integrations/checkmk/index.rst:2 -msgid "Checkmk" +#: ../settings/system/base.rst:19 +msgid "HTTP type" msgstr "" -#: ../system/integrations/checkmk/index.rst:4 +#: ../settings/system/base.rst:14 msgid "" -"`Checkmk `_ is a powerful IT monitoring tool that can " -"send real-time status alerts to Zammad via email or REST API. Set these " -"alerts up in Checkmk, and Zammad will automatically create, update, and " -"close tickets based on the health of your system:" -msgstr "" - -#: ../system/integrations/checkmk/index.rst:14 -msgid "Screenshot of ticket created by Checkmk notifications" +"The HTTP type tells your installation how your clients connect. This is " +"relevant for authentication and cookie security." msgstr "" -#: ../system/integrations/checkmk/index.rst:14 -msgid "Multiple alerts, same ticket." +#: ../settings/system/base.rst:31 +msgid "SystemID" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:2 -msgid "Setup Guide" +#: ../settings/system/base.rst:22 +msgid "" +"This ID is being used within your ticket number. In case you're " +"communicating with another ticket system with similar ticket number schemes " +"this ID greatly reduces the risk of false follow ups." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:4 +#: ../settings/system/base.rst:26 msgid "" -"Whenever the Checkmk integration is enabled, Zammad listens for messages on " -"its API and over email. As long as those messages follow the required " -"format, Zammad will create new tickets (or find and update existing ones) " -"based on the message contents." +"The SystemID is randomly selected upon installation of Zammad (``1-99``)." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:10 +#: ../settings/system/base.rst:30 msgid "" -"That means that “setting up Checkmk integration” is simply a matter of " -"**adding configuration to your Checkmk site**: telling it when to send these " -"messages and what to say. To do that, you'll need to create a new " -"**notification rule** (see `Checkmk's official docs `_ for help with that)." +"**Do not** change this setting in a productive system! Your Zammad " +"installation may no longer recognize old ticket number based follow ups upon " +"change!" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:17 -msgid "" -"As part of this new rule, you'll have to choose a **notification method** " -"(*i.e.,* a script to execute whenever the rule is triggered). This script " -"will be written by you (samples below), and contain the logic for sending " -"API/email messages to Zammad:" +#: ../settings/system/frontend.rst:2 +msgid "Frontend" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:26 -msgid "Checkmk \"New Rule\" dialog" +#: ../settings/system/frontend.rst:22 +msgid "Core Workflow Ajax Mode" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:26 +#: ../settings/system/frontend.rst:6 msgid "" -"Find your custom scripts in the Checkmk WATO under **Notifications > New " -"Rule > Notification Method**." +"This setting allows administrators to enforce :doc:`/system/core-workflows` " +"to use Ajax-Calls instead of web sockets. You'll usually only need this if " +"you experience serious issues as noted below." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:29 +#: ../settings/system/frontend.rst:10 +msgid "**🤓 Possible (technical) reasons**" +msgstr "" + +#: ../settings/system/frontend.rst:12 msgid "" -"Once you're done setting up your new rule, you're all set! New tickets " -"should start coming in and auto-updating any time your rule is triggered." +"In some cases, your network structure (e.g. firewalls, proxies) may " +"disconnect long web socket connections. This leads to select fields staying " +"empty (e.g. owner selection *after* selecting your group) or fields not " +"shown / hidden (e.g. when switching to or from pending states, the \"pending " +"till\" field not showing / hiding)." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:33 +#: ../settings/system/frontend.rst:18 msgid "" -"(If you need help troubleshooting, be sure to check the :ref:`checkmk-recent-" -"logs`.)" +"Please keep in mind that the Ajax fallback may cause serious pressure on " +"your application server. If you have the choice stick to web sockets." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:38 -msgid "API Alerts" +#: ../settings/system/frontend.rst:22 +msgid "Default: ``no`` (inactive)" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:40 -msgid "" -"To add these scripts in the Checkmk WATO, copy them into your Checkmk " -"installation directory and make them executable. (Be sure to replace the " -"``zammad.example.com`` callback URL with the one found in your admin panel.)" +#: ../settings/system/frontend.rst:53 +msgid "Show calendar weeks in the picker of date/datetime fields" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:60 -msgid "Service notification" +#: ../settings/system/frontend.rst:25 +msgid "" +"With this setting you can instruct Zammad to provide week number display " +"globally for all users. Calendar with week number display are usually used " +"in business sectors and may not be relevant for everyone." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:46 +#: ../settings/system/frontend.rst:29 msgid "" -"For updates on the status of the software running on your server (*e.g.,* " -"postgres)." +"This setting affects *all areas* - you'll also see week numbers in the admin " +"panel for e.g. triggers and macros." msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:75 -msgid "Host notification" +#: ../settings/system/frontend.rst:32 +msgid "Default: ``no`` (not shown)" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:63 -msgid "For updates on the status of the server itself." +#: ../settings/system/frontend.rst:53 +msgid "Here's the difference:" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:77 -msgid "🤔 **What's with all the env vars?**" +#: ../settings/system/frontend.rst:0 +msgid "Screenshot showing Zammad's date picker (in the default way)" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:79 -msgid "" -"Whenever Checkmk runs these scripts, it needs to provide some information " -"about the event that triggered the notification. This information is passed " -"in the form of these ``$NOTIFY_*`` environment variables." +#: ../settings/system/frontend.rst:41 +msgid "Set to ``no``" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:85 +#: ../settings/system/frontend.rst:0 msgid "" -"You can specify additional parameters to pass to the script when you're " -"setting up your notification rule, but the ones you see here are all " -"provided by default." +"Screenshot showing Zammad's date picker with\n" +"week numbers enabled" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:90 -msgid "Email Alerts" +#: ../settings/system/frontend.rst:50 +msgid "Set to ``yes``" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:94 +#: ../settings/system/index.rst:4 msgid "" -"🐞 **There are known bugs** in Zammad's processing of email from Checkmk. " -"This section will be completed once they have been resolved. (Learn more at " -"GitHub issues `#2377 `_ & " -"`#2180 `_.)" +"For your overview we split each tab within system settings into its own page:" msgstr "" -#: ../system/integrations/checkmk/setup-guide.rst:100 -msgid "In the meantime, we encourage you to set up API alerts instead." +#: ../settings/system/index.rst:16 +msgid "Console Based Settings" msgstr "" -#: ../system/integrations/clearbit.rst:2 -msgid "Clearbit" +#: ../settings/system/index.rst:18 +msgid "" +"There's some console based settings we didn't put into the UI. However, you " +"may find them helpful - you can find them in our :docs:`hidden settings ` section." msgstr "" -#: ../system/integrations/clearbit.rst:4 +#: ../settings/system/network.rst:2 +msgid "Network" +msgstr "" + +#: ../settings/system/network.rst:8 msgid "" -"With our Clearbit integration, you can easily enrich the information " -"provided by Zammad. If the customers or agents email address is known to " -"Clearbit, it will share all information it has regarding the user with " -"Zammad. Those information can include the following:" +"The proxy settings can only be saved after successfully testing the proxy " +"connection." msgstr "" -#: ../system/integrations/clearbit.rst:9 -msgid "Avatar" +#: ../settings/system/network.rst:15 +msgid "Proxy Address." msgstr "" -#: ../system/integrations/clearbit.rst:10 -msgid "Address information" +#: ../settings/system/network.rst:12 +msgid "" +"Allows you to provide a proxy server if needed. This is relevant for network " +"communication by Zammad." msgstr "" -#: ../system/integrations/clearbit.rst:11 -msgid "Website information" +#: ../settings/system/network.rst:15 +msgid "It **does not** affect the update process or Elasticsearch." msgstr "" -#: ../system/integrations/clearbit.rst:12 -msgid "A BIO (as Note by default)" +#: ../settings/system/network.rst:18 +msgid "Username for proxy connection." msgstr "" -#: ../system/integrations/clearbit.rst:14 +#: ../settings/system/network.rst:18 msgid "" -"If needed, you can add further custom objects and add mappings to them, so " -"the Clearbit information can be filled within the database. In general you " -"can get any information from Clearbit, as long as you have a mapping to an " -"Zammad object." +"If your proxy server requires authentication, provide the username here." msgstr "" -#: ../system/integrations/clearbit.rst:21 -msgid "" -"Clearbit does have a mapping of fields like LDAP and Exchange have, but does " -"not \"win\" against Zammad information. This means that if you have e.g. the " -"last name field filled in already and Clearbit has other information on " -"that, it will not be updated." +#: ../settings/system/network.rst:21 +msgid "Password for proxy connection." msgstr "" -#: ../system/integrations/clearbit.rst:26 +#: ../settings/system/network.rst:21 msgid "" -"However: If let's say the last name has been set by Clearbit and Zammad " -"notices that the last name on the Clearbit source has changed, Zammad will " -"also update this value." +"If your proxy server requires authentication, provide the password here." msgstr "" -#: ../system/integrations/clearbit.rst:33 -msgid "" -"The configuration of Clearbit is really easy and done fast! Just login to " -"your Clearbit-Account, go to \"API\" and copy the secret-API-Key." +#: ../settings/system/network.rst:26 +msgid "No proxy for the following hosts." msgstr "" -#: ../system/integrations/clearbit.rst:38 +#: ../settings/system/network.rst:24 msgid "" -"Now change to your Zammad instance, go to Integrations (System) -> Clearbit " -"in the admin panel. Paste your API-Key into the API-Key-Field and decide if " -"Zammad should create unknown Organizations automatically, if the user does " -"not have one yet (and Clearbit knows it). The shared option decides if the " -"new organizations Zammad creates with Clearbit should be shared ones." +"Exception list for hosts you can't or don't want to reach via proxy server." msgstr "" -#: ../system/integrations/clearbit.rst:47 -msgid "" -"If you're unsure what option to choose, better stick with \"no\". You can " -"also learn more about :doc:`/manage/organizations/index`." +#: ../settings/system/network.rst:27 +msgid "Default: ``localhost,127.0.0.0,::1``" msgstr "" -#: ../system/integrations/clearbit.rst:52 -msgid "" -"The Mapping option works similar to the mapping within the Exchange and LDAP " -"sync. You can add further mappings for e.g. custom fields if you need more " -"information that Clearbit can provide." +#: ../settings/system/services.rst:2 +msgid "Services" msgstr "" -#: ../system/integrations/clearbit.rst:58 -msgid "" -"If you want to add more Clearbit fields and want to learn more about " -"available fields on their API, you can take a look at their `API " -"documentation `_." +#: ../settings/system/services.rst:10 +msgid "Image Service" msgstr "" -#: ../system/integrations/clearbit.rst:62 -msgid "" -"If you're happy with the above chosen Settings and your mapping, just save " -"the changes and enable Clearbit integration. Zammad will now start polling " -"the Clearbit API as users contact you." +#: ../settings/system/services.rst:5 +msgid "Defines the backend for user and organization image lookups." msgstr "" -#: ../system/integrations/clearbit.rst:68 -msgid "" -"Zammad does not synchronize with Clearbit on a regular basis, but on demand " -"if needed. This saves API calls." +#: ../settings/system/services.rst:7 +msgid "Default: ``Zammad Image Service`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:73 +#: ../settings/system/services.rst:9 msgid "" -"Below the Settings and Mappings, you'll find our Integration log. You can " -"see what requests Zammad sent to Clearbit and also the APIs Response." +"Make sure your on premise installation has ``HTTPS`` access to ``images." +"zammad.com``." msgstr "" -#: ../system/integrations/clearbit.rst:78 +#: ../settings/system/services.rst:18 +msgid "Geo Calendar Service" +msgstr "" + +#: ../settings/system/services.rst:13 msgid "" -"By the way, you can also view the API log on the Clearbit website - the " -"information seen is basically the same." +"Defines the backend for geo calendar lookups. Used for initial calendar " +"setup." msgstr "" -#: ../system/integrations/clearbit.rst:84 -msgid "Example When Adding a User" +#: ../settings/system/services.rst:16 +msgid "Default: ``Zammad GeoCalendar Service`` (active)" msgstr "" -#: ../system/integrations/clearbit.rst:86 +#: ../settings/system/services.include.rst:2 msgid "" -"To show you how fast information is added, we added a small Screencast " -"below. This shows the creation of the User Alex from Clearbit. As we already " -"set the last name of Alex to \"X\", Zammad did not update it. What Zammad " -"did was to add further information it received from Clearbit." +"Make sure your on premise installation has ``HTTPS`` access to ``geo.zammad." +"com``." msgstr "" -#: ../system/integrations/cti/generic.rst:2 -msgid "CTI (generic)" +#: ../settings/system/services.rst:26 +msgid "Geo IP Service" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:1 +#: ../settings/system/services.rst:21 msgid "" -"This integration enables Zammad to provide a caller log to your agents. With " -"this your agents can greet your customers by their name and are supported by " -"Zammad with automatically opening a new ticket dialog or the user profile." +"Defines the backend for geo IP lookups. Shows also location of an IP address " +"if an IP address is shown." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:6 -msgid "" -"Click the toggle next to the heading to activate or deactivate this " -"integration." +#: ../settings/system/services.rst:24 +msgid "Default: ``Zammad GeoIP Service`` (active)" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:9 +#: ../settings/system/services.rst:32 +msgid "Geo Location Service" +msgstr "" + +#: ../settings/system/services.rst:29 msgid "" -"If you want to learn more on how your agents can use this function, please " -"refer the :user-docs:`user documentation `." +"Defines the backend for geo location lookups to store geo locations for " +"addresses." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:14 +#: ../settings/system/services.rst:32 msgid "" -"Automatically opening new ticket dialogues or user profiles requires agent " -"to extension mapping - see more below." +"Default: ``OpenStreetMap (ODbL 1.0, http://osm.org/copyright)`` (active)" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:20 -msgid "Please note the following limitations to reduce confusion later on:" +#: ../settings/system/services.rst:36 +msgid "" +"You can find a detailed privacy information on what we store for how long on " +"our :docs:`Privacy Appendix ` inside of our System " +"Documentation." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:22 -msgid "CTI integrations provide caller log functions only." +#: ../settings/system/storage.rst:2 +msgid "Storage" msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:23 +#: ../settings/system/storage.rst:6 msgid "" -"This integration does not provide any VoIP functionalities; you can't make " -"phone calls from within Zammad." +"Here you can define where Zammad stores attachments for tickets and the " +"knowledge base. By default, we're writing to the ``Database`` - you can " +"switch to ``Filesystem`` or ``Simple Storage (S3)`` at any time. In this " +"case please have a look on the following instructions." msgstr "" -#: ../system/integrations/cti/includes/introduction.include.rst:25 +#: ../settings/system/storage.rst:11 msgid "" -"If your browser supports ``tel``-URLs, you can click on phone numbers for " -"automatic dialing. This requires additional software / configuration on your " -"agent's computers." +"If you have a busy Zammad instance, we strongly encourage you to use " +"filesystem storage instead of \"Database\". This will greatly improve system " +"performance (de-crease database load and size)." msgstr "" -#: ../system/integrations/cti/generic.rst:9 -#: ../system/integrations/cti/placetel.rst:14 -#: ../system/integrations/cti/sipgate.rst:14 -msgid "Please provide the following requirements:" +#: ../settings/system/storage.rst:19 +msgid "Database" msgstr "" -#: ../system/integrations/cti/generic.rst:11 +#: ../settings/system/storage.rst:17 msgid "" -"A telephone system that supports webhooks (outbound) (best option are those " -"that allow customizing the calls)." -msgstr "" - -#: ../system/integrations/cti/generic.rst:13 -msgid "A unique Call-ID during the call session." +"This is the default storage method. The attachments are stored directly in " +"the database. If your Zammad instance grows, we recommend one of the other " +"methods to maintain performance." msgstr "" -#: ../system/integrations/cti/generic.rst:14 -msgid "Call event data (both numbers and direction)." +#: ../settings/system/storage.rst:38 +msgid "Filesystem" msgstr "" -#: ../system/integrations/cti/generic.rst:15 -msgid "Your Zammad instance must be reachable for your telephony system." +#: ../settings/system/storage.rst:22 +msgid "" +"This storage method is recommended for all Zammad instances, especially for " +"those with a higher load. If you choose filesystem, your files are written " +"to ``/opt/zammad/storage/``." msgstr "" -#: ../system/integrations/cti/generic.rst:17 +#: ../settings/system/storage.rst:26 msgid "" -"If you want to learn more on what kind of requests are supported by Zammad " -"and what it expects, please consult our :docs:`CTI-API documentation `." +"Moving attachments from \"Database\" to \"Filesystem\" can be run during " +"production use. However, you should consider your framework conditions (e.g. " +"bandwidth, system load in production) to define the right moment." msgstr "" -#: ../system/integrations/cti/generic.rst:22 -#: ../system/integrations/cti/placetel.rst:27 -#: ../system/integrations/cti/sipgate.rst:30 -msgid "Available Settings" +#: ../settings/system/storage.rst:32 +msgid "**You noticed slow updates of Zammad?**" msgstr "" -#: ../system/integrations/cti/generic.rst:29 -#: ../system/integrations/cti/placetel.rst:41 -#: ../system/integrations/cti/sipgate.rst:40 -msgid "Endpoint Settings" +#: ../settings/system/storage.rst:34 +msgid "" +"While Zammad is beeing updated, it enforces a recursive \"change " +"owner\" (chown) for this directory. For instances with many files this can " +"be time consuming. To mitigate that you can move your files and create a " +"symlink in ``/opt/zammad/storage/`` to the new directory. Of course you have " +"to make sure on your own that the permissions are always correct." msgstr "" -#: ../system/integrations/cti/generic.rst:25 -msgid "" -"Zammad will list your generic CTI endpoint here. It contains a unique token " -"so ensure to keep this URL save." +#: ../settings/system/storage.rst:95 +msgid "Simple Storage (S3)" msgstr "" -#: ../system/integrations/cti/generic.rst:28 +#: ../settings/system/storage.rst:41 msgid "" -"You'll need this endpoint for your PBX to talk to Zammad, see :docs:`CTI-API " -"documentation `." +"To use the Simple Storage (S3), you have to provide some settings, which " +"can't be accessed in the UI (see instructions below)." msgstr "" -#: ../system/integrations/cti/includes/important-dont-forget-saving.include.rst:3 +#: ../settings/system/storage.rst:44 msgid "" -"All following options **do not save automatically**. Always use the Save " -"button on the lower end of the integration page!" +"⚠️ Please note that the current implementation is in its early stages and can " +"be modified in the future." msgstr "" -#: ../system/integrations/cti/generic.rst:43 -#: ../system/integrations/cti/placetel.rst:49 -#: ../system/integrations/cti/sipgate.rst:52 -msgid "Call Settings" +#: ../settings/system/storage.rst:47 +msgid "" +"The prerequisite is to have access to a S3-compatible storage and to have " +"all necessary parameters available (which depends on your storage provider; " +"if in doubt, please ask there for help)." msgstr "" -#: ../system/integrations/cti/generic.rst:39 -#: ../system/integrations/cti/placetel.rst:49 -#: ../system/integrations/cti/sipgate.rst:37 -#: ../system/integrations/cti/sipgate.rst:50 -msgid "Inbound" +#: ../settings/system/storage.rst:51 +msgid "Steps to configure S3:" msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:1 +#: ../settings/system/storage.rst:53 msgid "" -"This option allows you to block specific incoming caller IDs. It allows you " -"to temporarily reject e.g. spam callers without having to contact providers " -"or PBX administrators." +"Copy ``config/zammad/storage.yml.dist`` to ``config/zammad/storage.yml``" msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:11 -msgid "Caller ID to block" +#: ../settings/system/storage.rst:54 +msgid "Edit the copied file in one of the following ways:" msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 -msgid "Provide caller IDs to block in ``E.164`` format." +#: ../settings/system/storage.rst:56 +msgid "" +"Either provide your S3 configuration with one attribute per line like in the " +"upper area of the file" msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:8 +#: ../settings/system/storage.rst:58 msgid "" -"Your telephony system has to support this function. Zammad will send a " -"``reject`` response which will cause your telephony system to hang up the " -"call. To callers this usually will feel like the line is busy." +"Or provide your S3 configuration as an URL (which you can find at the end of " +"the file). Note: you can also provide this URL as environment variable (:" +"docs:`see system documentation `) without using this yml-file." msgstr "" -#: ../system/integrations/cti/includes/inbound-calls.include.rst:14 +#: ../settings/system/storage.rst:62 msgid "" -"Provide a meaningful note for your fellow administrators to remind yourself " -"why you've chosen to block the number." +"We recommend the deletion of the not used configuration style to avoid " +"inconsistencies." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 -#: ../system/integrations/cti/includes/outbound-calls.include.rst:17 -#: ../system/integrations/cti/sipgate.rst:40 -msgid "Outbound" +#: ../settings/system/storage.rst:65 +msgid "Restart Zammad so the config file / environment variable is loaded" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:1 +#: ../settings/system/storage.rst:66 msgid "" -"In many cases you may want to use a different caller ID depending on the " -"destination you're calling. This may apply due to specific connection rates " -"to other countries or because you want your customer to feel you're calling " -"from the same country." -msgstr "" - -#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:6 -msgid "This option expects ``E.164`` number formats." +"Set the \"Storage Method\" in Zammad to ``Simple Storage (S3)`` in Settings " +"> System > Storage and click on \"Submit\". After that, Zammad checks your " +"configuration and the connection to the service and will raise an error " +"message if something is wrong." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 -msgid "Destination caller ID" +#: ../settings/system/storage.rst:72 +msgid "A very simple storage configuration could look like this:" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:5 -msgid "The caller ID or number you're trying to call." +#: ../settings/system/storage.rst:85 +msgid "" +"Before setting the storage method to ``Simple Storage (S3)`` (step 4), " +"please make sure to have a working setup." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:7 -msgid "You can use wildcards for e.g. country specific outbound numbers like:" -msgstr "" - -#: ../system/integrations/cti/includes/outbound-calls.include.rst:9 -msgid "``49*`` for Germany" +#: ../settings/system/storage.rst:88 +msgid "" +"You can verify this by running ``rails r 'Rails.logger = Logger.new(STDOUT); " +"pp Store::Provider::S3.ping?'`` in your Zammad directory. If everything is " +"fine, you should see ``true``, else you should see ``false`` and a simple " +"error message." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:10 -msgid "``4930*`` for Berlin / Germany landlines" +#: ../settings/system/storage.rst:93 +msgid "" +"If you installed Zammad through a package manager (rather than from source), " +"replace ``rails r`` with ``zammad run rails r`` above. To learn more, see :" +"docs:`Administration via Console `." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 -msgid "``33*`` for France" +#: ../settings/ticket.rst:4 +msgid "" +"Here you can adjust general ticket settings. Additional ones for the ticket " +"composer interface can be found in the :doc:`/misc/composer`." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:15 -msgid "Set Outbound caller ID" +#: ../settings/ticket.rst:11 +msgid "Ticket Hook (default: ``Ticket#``)" msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:14 -msgid "" -"The outbound caller ID to set (the number your customer sees on his display) " -"in ``E.164`` number format." +#: ../settings/ticket.rst:11 +msgid "The identifier for a ticket; *e.g.,* Ticket#, Call#, MyTicket#." msgstr "" -#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 -msgid "Provide a short description for fellow administrators." +#: ../settings/ticket.rst:38 +msgid "Ticket Hook Position (default: ``right``)" msgstr "" -#: ../system/integrations/cti/includes/generic-cti-support-note.includes.rst:3 +#: ../settings/ticket.rst:14 msgid "" -"This option requires your PBX to send a specific request to Zammad *before " -"dialing*. Please consult the :docs:`CTI API ` in case " -"you're not sure." +"With this setting you can decide (if) where to insert the ticket number." msgstr "" -#: ../system/integrations/cti/generic.rst:52 -#: ../system/integrations/cti/placetel.rst:54 -#: ../system/integrations/cti/sipgate.rst:59 -msgid "Other Settings" +#: ../settings/ticket.rst:20 +msgid "*Right*" msgstr "" -#: ../system/integrations/cti/includes/other-settings-intro.include.rst:1 +#: ../settings/ticket.rst:17 msgid "" -"Below you can find all available additional settings for this CTI " -"integration. For your overview we're sorting them by appearance and " -"reference their description first." +"This setting will add the ticket reference on the right site of the subject." msgstr "" -#: ../system/integrations/cti/includes/default-caller-id.include.rst:2 -#: ../system/integrations/cti/includes/default-caller-id.include.rst:1 -msgid "Default caller ID for outbound calls" +#: ../settings/ticket.rst:20 +msgid "Example: ``Some Subject [Ticket#12345]``" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:16 -#: ../system/integrations/cti/includes/records-caller-log.include.rst:15 -msgid "Shown records in caller log" +#: ../settings/ticket.rst:26 +msgid "*Left*" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:2 +#: ../settings/ticket.rst:23 msgid "" -"Allows you to set the number of shown caller log entries for all users. You " -"can choose from the following values:" +"This setting will add the ticket reference on the left site of the subject." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:5 -msgid "60 (default)" +#: ../settings/ticket.rst:26 +msgid "Example: ``[Ticket#12345] Some Subject``" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:6 -msgid "120" +#: ../settings/ticket.rst:29 +msgid "*None*" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:7 -msgid "180" +#: ../settings/ticket.rst:29 +msgid "This will completely remove ticket references from the subject." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:8 -msgid "240" +#: ../settings/ticket.rst:33 +msgid "" +"Please ensure to take a look at :doc:`/channels/email/settings` within the " +"email channel to ensure you have at least one reference that helps Zammad to " +"assign follow-ups correctly." msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:9 -msgid "300" +#: ../settings/ticket.rst:37 +msgid "" +"Disabling this and not setting up any further follow up search will lead to " +"unexpected results!" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:11 -msgid "**🥵 Potential performance issue**" +#: ../settings/ticket.rst:65 +msgid "" +"Ticket Last Contact Behaviour (default: ``Use the start time of the last " +"customer thread (which may consist of multiple articles).``)" msgstr "" -#: ../system/integrations/cti/includes/records-caller-log.include.rst:13 +#: ../settings/ticket.rst:41 msgid "" -"Setting this setting higher than 60 may cause serious performance issues on " -"very busy instances. Keep in mind that this setting causes Zammad to poll " -"and send up to 300 records to *all active agent sessions* in very short time " -"periods." +"This setting changes the way Zammad updates the ``Last Contact`` value of a " +"ticket. This is fairly important for overviews and what you expect upon " +"ticket updates of a customer." msgstr "" -#: ../system/integrations/cti/generic.rst:73 -msgid "Caller Log Filter" +#: ../settings/ticket.rst:52 +msgid "" +"Use the start time of the last customer thread (which may consist of " +"multiple articles)." msgstr "" -#: ../system/integrations/cti/generic.rst:55 +#: ../settings/ticket.rst:46 msgid "" -"This function allows you to provide call information based on e.g. queues " -"only to agents that really need the information." +"If this option is chosen, Zammad will update the last updated value just " +"once if a customer replies. After that, Zammad will wait for an agent to " +"react." msgstr "" -#: ../system/integrations/cti/generic.rst:58 +#: ../settings/ticket.rst:50 msgid "" -"Why? If you have a team for several countries or departments, you don't want " -"to bug your agents from other departments. Leaving these options empty will " -"fallback to showing everything to everyone." +"This comes in handy if you want to work tickets in the order of their first " +"update. This will not change ticket orders if customers decide to \"bump\" " +"the ticket affected." msgstr "" -#: ../system/integrations/cti/generic.rst:64 -msgid "Destination caller ID or Queue" +#: ../settings/ticket.rst:57 +msgid "Use the time of the very last customer article." msgstr "" -#: ../system/integrations/cti/generic.rst:63 +#: ../settings/ticket.rst:55 msgid "" -"This depends on your PBX and usually is either a queue ID, phone number or " -"extension." +"When setting this option, Zammad will always update the last updated value. " +"This means that if ordering by ``Last Update``, ticket orders will change if " +"customers \"bump\" the ticket." msgstr "" -#: ../system/integrations/cti/generic.rst:69 -msgid "Agents" +#: ../settings/ticket.rst:64 +msgid "Last contact value used on :doc:`/manage/overviews`" msgstr "" -#: ../system/integrations/cti/generic.rst:67 -msgid "" -"Select the agents that are responsible for the group. These agents will then " -"see caller log entries and call notifications fitting to said queue." +#: ../settings/ticket.rst:65 +msgid "Last contact value used on :doc:`/manage/trigger`" msgstr "" -#: ../system/integrations/cti/generic.rst:0 +#: ../settings/ticket.rst:88 msgid "" -"Screenshot showing the caller log filter table with pre filled sample data" +"Ticket Organization Reassignment (default: ``Update the most recent tickets." +"``)" msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:6 +#: ../settings/ticket.rst:68 msgid "" -"With recent logs Zammad allows you to view the latest calls for the CTI " -"functionality. This usually comes in handy, when you're looking for errors." +"This setting changes the way Zammad updates the organization field of the " +"tickets whenever the primary organization of a user is changed." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:0 -msgid "" -"Screenshot showing several incoming requests within Recent logs section." +#: ../settings/ticket.rst:74 +msgid "Update the most recent tickets." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:16 -msgid "I'm just here to clear floats up." +#: ../settings/ticket.rst:72 +msgid "" +"If this option is chosen, Zammad will update the 100 most recent tickets " +"where the user is the ticket customer. The ticket organization field will be " +"automatically set to the new primary organization of the user." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:20 -msgid "" -"By clicking on the entry of interest, Zammad will provide more details on " -"the call in question. You'll see the payload it received and also the " -"response that was sent." +#: ../settings/ticket.rst:88 +msgid "Do not update any tickets." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:0 +#: ../settings/ticket.rst:77 msgid "" -"Screenshot showing detailed information of a specific log entry of recent " -"logs" +"When choosing this option, Zammad will not update any tickets when the " +"user's primary organization is changed." msgstr "" -#: ../system/integrations/cti/includes/recent-logs.include.rst:31 -msgid "x" +#: ../settings/ticket.rst:80 +msgid "**Use with care!**" msgstr "" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 -#: ../system/integrations/cti/includes/troubleshooting.include.rst:9 -msgid "My Phone page stays blank, signalling does work..." +#: ../settings/ticket.rst:82 +msgid "" +"Using this option may lead to inconsistencies in the system as the ticket " +"organization may become decoupled from the ticket customer." msgstr "" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:5 +#: ../settings/ticket.rst:85 msgid "" -"If you've made sure that signalling works (check Recent logs) and your " -"Caller Log still stays empty, please ensure that you only configured one CTI " -"integration version. Specifically defining more than one agent mapping on " -"the different integration variants will be the issue." +"However, you may use this option if you wish to maintain :ref:`the shared " +"access ` to the ticket for all organization " +"members of the original organization of the customer." msgstr "" -#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 -msgid "Clear the not needed agent mapping and reload your browser page." +#: ../settings/ticket.rst:110 +msgid "Ticket Number Format (default: ``Increment (SystemID.Counter)``)" msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:1 +#: ../settings/ticket.rst:94 msgid "" -"By mapping your agents extension to their existing Zammad users, Zammad can " -"provide a new ticket dialog or open the user profile for the agent that " -"picks up the call." +"This setting defines the way Zammad's ticket number will look. Changing this " +"setting in production will cause follow up detection to fail." msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:5 -msgid "" -"This speeds up ticket aiding, no matter if it's for existing tickets or new " -"ones!" +#: ../settings/ticket.rst:102 +msgid "Increment (SystemID.Counter)" msgstr "" -#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:8 +#: ../settings/ticket.rst:98 msgid "" -"To see it work from the agent's perspective, have a look on :user-docs:`user " -"documentation `." +"The increment value contains the SystemID (automatically generated during " +"installation) and a increment which counts up with every new Ticket. The " +"increment will automatically get another digit if needed." msgstr "" -#: ../system/integrations/cti/placetel.rst:2 -msgid "Placetel CTI" +#: ../settings/ticket.rst:102 +msgid "Examples: ``1010138``, ``1010139``" msgstr "" -#: ../system/integrations/cti/placetel.rst:16 -msgid "You need an administrative Placetel account for your organization." +#: ../settings/ticket.rst:110 +msgid "Date (Year.Month.Day.SystemID.Counter)" msgstr "" -#: ../system/integrations/cti/placetel.rst:17 -#: ../system/integrations/cti/sipgate.rst:20 +#: ../settings/ticket.rst:105 msgid "" -"Your Zammad instance must be allowed to communicate to external services." +"This version of the ticket number is fairly long. However, because it " +"contains the date of ticket creation, it also allows you to see when the " +"ticket has been created. You may feel familiar with this number format if " +"you've worked with OTRS already." msgstr "" -#: ../system/integrations/cti/placetel.rst:18 -msgid "Placetel must be able to reach your Zammad instance." +#: ../settings/ticket.rst:110 +msgid "Examples: ``201206231010138``, ``201206231010139``" msgstr "" -#: ../system/integrations/cti/placetel.rst:22 -msgid ":doc:`provider-configurations/placetel`" +#: ../settings/ticket.rst:137 +msgid "OPTIONS" msgstr "" -#: ../system/integrations/cti/placetel.rst:21 +#: ../settings/ticket.rst:113 msgid "" -"Learn how to configure Placetel to enable Zammad and Placetel to communicate " -"with each other." +"The below options allow you to further customize your ticket number. The " +"availability of options differ depending of the chosen ticket number format " +"above." msgstr "" -#: ../system/integrations/cti/placetel.rst:32 +#: ../settings/ticket.rst:122 +msgid "Checksum (default: ``no``)" +msgstr "" + +#: ../settings/ticket.rst:118 msgid "" -"The here listed endpoint settings are relevant for the :doc:`integration " -"configuration with Placetel `." +"If set to yes, we'll built a checksum to further \"unique\" the ticket " +"number of your system. If you're dealing with many other ticket systems this " +"might help to prevent false positive follow up detection on tickets." msgstr "" -#: ../system/integrations/cti/placetel.rst:37 -#: ../system/integrations/i-doit.rst:53 -msgid "Endpoint" +#: ../settings/ticket.rst:122 +msgid "This will also add another digit to the ticket number." msgstr "" -#: ../system/integrations/cti/placetel.rst:36 -msgid "" -"This endpoint will be required for the Zammad integration within the " -"Placetel web interface." +#: ../settings/ticket.rst:137 +msgid "Min. size of Number (default: ``5``)" msgstr "" -#: ../system/integrations/cti/placetel.rst:41 -msgid "API Token" +#: ../settings/ticket.rst:125 +msgid "" +"This setting defines the minimum length of your ticket number. If your " +"counter is not yet high enough, Zammad will fill the number with zeros to " +"ensure the wanted length." msgstr "" -#: ../system/integrations/cti/placetel.rst:40 +#: ../settings/ticket.rst:129 msgid "" -"You'll receive this token within the ``Web API`` menu. Make sure to copy " -"this value, it's only shown once!" +"Please note that the minimum length is ``3`` (SystemID + at least one digit " +"if below 10). Also, if the length is no longer long enough, the number will " +"automatically get one digit longer. Ticket-Numbers **do not overflow**, thus " +"it's save to keep it at 5 or set it lower if wanted." msgstr "" -#: ../system/integrations/cti/placetel.rst:71 -#: ../system/integrations/cti/sipgate.rst:77 -msgid "Phone Extension to Agent Mapping" +#: ../settings/ticket.rst:135 +msgid "" +"This option is only available if ticket number format is set to " +"``Increment``!" msgstr "" -#: ../system/integrations/cti/placetel.rst:0 -msgid "Screenshot showing sample user mappings in between Placetel and Zammad" +#: ../settings/ticket.rst:142 +msgid "Auto-Assignment" msgstr "" -#: ../system/integrations/cti/placetel.rst:64 +#: ../settings/ticket.rst:144 msgid "" -"You can find your agents Placetel username combination required within ⚙️ PBX " -"→ VoIP destinations. Within the \"Advanced settings\" section you're looking " -"for \"SIP user name\" and \"SIP server\"." +"In a larger Zammad environment, it happens that several agents open the same " +"ticket at the same time. Although collision detection is then effective, the " +"efficiency of processing can be increased by means of the automatic " +"assignment of tickets when a ticket is opened." msgstr "" -#: ../system/integrations/cti/placetel.rst:68 -msgid "Combine these two like so: ``@``." +#: ../settings/ticket.rst:149 +msgid "" +"The automatic assignment of tickets can be activated and configured in the " +"admin area under Settings > Ticket > Auto Assignment." msgstr "" -#: ../system/integrations/cti/placetel.rst:0 -msgid "Sample VoIP credentials for a Placetel user" +#: ../settings/ticket.rst:152 +msgid "" +"The auto assignment only works if the ticket has no owner yet. By default, " +"the agent can always reset the ticket owner to ``-`` if needed." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:2 -msgid "Setup Placetel connection for Zammad" +#: ../settings/ticket.rst:155 +msgid "" +"If you want to use this function for only specific tickets, you can " +"configure the conditions accordingly to meet your requirement. By default " +"the condition affects all tickets with the state ``open``." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:6 +#: ../settings/ticket.rst:161 msgid "" -"This configuration step requires a *full* administrative Placetel account. " -"You may receive forbidden error messages with Placetel in case your " -"permissions are not high enough." +"If you need to exclude users (e.g. a group leader), you can search and " +"select the desired agents in the ``Exception Users`` list. The search " +"function in this area is only effective, if you have too many agents to " +"display at once to help you with the configuration." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:10 -msgid "" -"The following actions can be configured via the `Placetel web interface " -"`_." +#: ../settings/ticket.rst:167 +msgid "Notifications" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:29 -msgid "Step 1: Activate Zammad integration" +#: ../settings/ticket.rst:191 +msgid "Default Notifications" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:14 +#: ../settings/ticket.rst:170 msgid "" -"Within Integrations, scroll down to Partner integrations and select Zammad." +"This setting allows you to configure the default ticket notifications that " +"will be applied to all new agent users (incl. users who were just assigned " +"agent role). Simply change the notification matrix to desired state and " +"press **Save**." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:17 +#: ../settings/ticket.rst:175 msgid "" -"You can alternatively filter by \"Ticket Systems\" to reduce the number of " -"entries on the page. You'll still want to look for Partner integrations. 🤓" +"In case an agent already exists, their ticket notification preferences will " +"be preserved. Optionally, you can also **Apply current defaults to all " +"agents**." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:21 +#: ../settings/ticket.rst:181 msgid "" -"Within the Zammad integration now press \"Activate\". A new tab ``API`` " -"becomes available - open this tab." +"**Potential time-consuming action:** Applying default ticket notifications " +"to all agent users may take some time to complete, be patient! The exact " +"time will depend on the size of your system and the number of agents." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:24 +#: ../settings/ticket.rst:185 msgid "" -"Now tick \"Enable Call Control / Notify API\" and paste the Placetel " -"endpoint from your Zammad instance into the field \"URL of your API " -"endpoint\". Save to apply the settings" +"**Active agents only!** When current default ticket notifications are " +"applied, only active agent users are considered. In case an agent is re-" +"activated *after* this action, they will still have the old notification " +"configuration." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 -msgid "Screencast showing how to activate the Zammad integration" +#: ../settings/ticket.rst:190 +msgid "" +"In case you want to go back to the initial state of ticket notifications, " +"you can click on **Reset to default** button." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:51 -msgid "Step 2: Generate API Token for Placetel" +#: ../settings/ticket.rst:196 +msgid "Duplicate Detection" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:32 -msgid "" -"Go back to the integrations page and scroll down to \"Web API\". Generate a " -"new API token by using the \"Create a new API token\" button." +#: ../settings/ticket.rst:238 +msgid "Detect Duplicate Ticket Creation" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:37 +#: ../settings/ticket.rst:199 msgid "" -"If you already generated a token either use your existing token or reset it " -"by using above mentioned button. Placetel will ask you to conform this reset." +"This setting turns on the duplicate ticket detection mechanism during ticket " +"creation. If similar tickets are found in the system, a suitable warning " +"will be shown to the user trying to create a ticket." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:41 +#: ../settings/ticket.rst:206 +msgid "A Sample Duplicate Ticket Warning" +msgstr "" + +#: ../settings/ticket.rst:208 msgid "" -"Please keep in mind that existing API scripts may no longer work due to " -"token resets!" +"You can choose which ticket attributes will be matched by selecting them in " +"**Attributes to compare** field. Only if the ticket attribute value provided " +"by the user in the ticket create form is *equal* with the attribute in an " +"existing ticket, the warning will be shown." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:44 +#: ../settings/ticket.rst:213 +msgid "**Warning title** and **Warning message** are configurable as well." +msgstr "" + +#: ../settings/ticket.rst:215 msgid "" -"Copy the provided API token and insert it into the \"API Token\" field " -"within Zammad's Placetel integration." +"You can limit the detection only to certain user roles. By default, only " +"agents will see the warning." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:47 +#: ../settings/ticket.rst:218 msgid "" -"Apply your changes by using the \"Save\" button on the bottom of the " -"Placetel integration page and activate the Placetel integration." +"If you don't want to show the matched tickets as part of the warning, you " +"can set **Show matching ticket(s) in the warning** setting to *no*." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +#: ../settings/ticket.rst:221 msgid "" -"Screencast showing how to retrieve an API token from Placetel for Zammad" +"By default, **Permission level for looking up ticket** is set to *User*, " +"which means user permissions will be honored during sarch. The user will " +"see the warning only if tickets they have access to are matched. " +"Alternatively, you can set this setting to *System*, in which case the " +"search will happen within *all* tickets in the system, regardless of user " +"permissions." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:73 -#: ../system/integrations/cti/provider-configurations/sipgate.rst:77 -msgid "Step 3: Restrict the numbers to notify on" +#: ../settings/ticket.rst:227 +msgid "**🦺 Safety first!**" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:54 +#: ../settings/ticket.rst:229 msgid "" -"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " -"the the Integrations page of the Placetel web interface, go to \"Notify " -"API\"." +"Even if the permission level is set to *System*, the user will not be shown " +"the tickets they don't have access to in the warning, even if they match." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:58 +#: ../settings/ticket.rst:233 msgid "" -"Lower on the page Placetel allows you to restrict the numbers to notify on. " -"You'll find this within the \"External routing API\" part." +"However, just the confirmation about the existence of the tickets in the " +"system may be considered an unwanted information disclosure. Use this option " +"carefully!" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +#: ../settings/ticket.rst:237 msgid "" -"Screenshot showing a sample selection of phone numbers to use for the " -"Placetels notify API" +"Finally, you can configure between matching within **All tickets** or **Open " +"tickets** only by setting **Match tickets in following states**. Depending " +"on the current ticket state, a ticket may or not be matched." msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:66 -msgid "" -"This menu point also provides a API request log from Placetel view. Just " -"open \"Recent responses of your API endpoint\" to learn more." +#: ../system/core-workflows.rst:2 +msgid "Core Workflows" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:69 +#: ../system/core-workflows.rst:4 msgid "" -"If you want to see Zammad's perspective, use the \"Recent Logs\" part from " -"within the Placetel integration page." +"Core Workflows allow you to adjust object attributes in many ways. For " +"example:" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:0 -msgid "Screenshot showing sample log entries for Placetels API calls to Zammad" +#: ../system/core-workflows.rst:7 +msgid "show / hide fields" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:77 -msgid "Step 4 (optional): Further configurations for Placetel" +#: ../system/core-workflows.rst:8 +msgid "adjust mandatory setting" msgstr "" -#: ../system/integrations/cti/provider-configurations/placetel.rst:76 -msgid "" -"If needed, you can now configure Zammad's Placetel integration in more " -"detail. You can learn more about your options here: :ref:`Placetel " -"integration settings `." +#: ../system/core-workflows.rst:9 +msgid "manipulate available options" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:2 -msgid "Setup Sipgate connection for Zammad" +#: ../system/core-workflows.rst:11 +msgid "" +"With this, you can provide exactly the information your users really need!" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +#: ../system/core-workflows.rst:15 msgid "" -"Sipgate has no english web interface which is why this documentation page is " -"mixing up languages badly." +"If the pre-defined :doc:`/system/objects` are not enough, please add them " +"beforehand." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +#: ../system/core-workflows.rst:17 msgid "" -"Please also note that the availability of API addons highly depends on your " -"package trier. Usage of sipgate.io packages *is not free*, please check " -"their `pricing page `_ before!" +"If you experience slow or unreliable field updates, please see :ref:`Core " +"Workflow Ajax Modus `" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:35 -msgid "Step 1: Book sipgate.io package" +#: ../system/core-workflows.rst:22 +msgid "" +"This is a very enhanced functionality and can cause unexpected UI behavior. " +"Please ensure to test your use cases after configuration to reduce surprises." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:13 -msgid "Skip to step 2 if you already have the package booked!" +#: ../system/core-workflows.rst:None +msgid "Dialogue for adding a new workflow" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:15 -msgid "" -"Login to an administrative Sipgate account and navigate to " -"``Accountverwaltung``. You'll see several different options depending on " -"your booked packages. Select ``Verträge & Produkte`` to continue." +#: ../system/core-workflows/condition-operators.rst:2 +msgid "Core Workflow Condition Operators" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:19 +#: ../system/core-workflows/condition-operators.rst:4 msgid "" -"Scroll down to the section ``Zusätzliche Produkte buchen`` and look for " -"``sipgate.io`` - select this product by using the ``Produkte anzeigen``-" -"Button." +"You might know that there is a separate section for explaining :doc:" +"`condition operators `. Head over there to " +"see a detailed explanation of many conditions and operators." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:23 +#: ../system/core-workflows/condition-operators.rst:8 msgid "" -"On the next page select either one of the ``sipgate.io`` packages or ``Push-" -"API Package Free``. Follow the dialogue by booking the addon. You'll be " -"returned to your contract overview and now should see the selected addon in " -"your list." +"Due to differences to other places in Zammad which are also using conditions " +"(e.g. triggers), you can find a dedicated description of operators for core " +"workflows below." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:30 +#: ../system/core-workflows/condition-operators.rst:12 msgid "" -"The availability for ``sipgate.io`` packages and their levels highly depends " -"on the overall account type and product you've booked with Sipgate." +"Be aware that the availability of the operators depends on the selected " +"attribute and its field type. Some of the operators may only be available " +"for system attributes (e.g. for \"tags\", \"active\")." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screencast showing the process on how to book the required sipgate.io addon" +#: ../system/core-workflows/condition-operators.rst:20 +msgid "Operator" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:52 -msgid "Step 2: Configure webhook for Zammad" +#: ../system/core-workflows/condition-operators.rst:22 +msgid "after (absolute)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:38 -msgid "" -"Within your ``Accountverwaltung`` navicate to your product ``sipgate.io``. " -"In the newly opened tab, switch from \"Clients\" to \"Webhooks\" and paste " -"the endpoint URLs from your Zammad instance like so:" +#: ../system/core-workflows/condition-operators.rst:23 +msgid "Matches if a date/time is after a specific point in time." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:42 -msgid "Inbound endpoint to \"Incoming\"" +#: ../system/core-workflows/condition-operators.rst:24 +msgid "after (relative)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:43 -msgid "Outbound endpoint to \"Outgoing\"" +#: ../system/core-workflows/condition-operators.rst:25 +msgid "Matches if a time span after a specified event has passed." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:47 -msgid "" -"Ensure to select at least one call group or phoneline within \"Sources\". " -"Other wise Sipgate will not indicate any incoming or outgoing calls to " -"Zammad." +#: ../system/core-workflows/condition-operators.rst:26 +msgid "before (absolute)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screencast showing how to add Zammad's endpoint URLs to sipgate.ios webhook " -"configuration" +#: ../system/core-workflows/condition-operators.rst:27 +msgid "Matches if a date/time is before a specific point in time." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:55 -msgid "" -"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " -"the Webhooks → URLs section of Sipgate you can select which *sources* " -"Sipgate should notify Zammad about in- and outgoing calls." +#: ../system/core-workflows/condition-operators.rst:28 +msgid "before (relative)" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:59 -msgid "" -"Use either specific phone lines or use the option \"Use for all phonelines " -"and groups\" to notify Zammad about all existing lines of your Sipgate " -"account." +#: ../system/core-workflows/condition-operators.rst:29 +msgid "Matches if a time span after a specified event has not passed." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screenshot showing a sample selection of phone numbers to use for the " -"Sipgates webhooks API" +#: ../system/core-workflows/condition-operators.rst:30 +msgid "contains" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:68 -msgid "This section also allows you to enable a Debug log." +#: ../system/core-workflows/condition-operators.rst:31 +msgid "Matches if a specified value is present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "Screenshot showing an enabled Debug log option" +#: ../system/core-workflows/condition-operators.rst:33 +msgid "Matches if all of the specified values are present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:73 -msgid "" -"After enabling you can use the Debug log section to see all sent webhook " -"calls to Zammad. You'll also can see the response." +#: ../system/core-workflows/condition-operators.rst:35 +msgid "Matches if none of the specified values are present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 -msgid "" -"Screenshot showing sample log entries for Sipgates webhook calls to Zammad" +#: ../system/core-workflows/condition-operators.rst:36 +msgid "contains not" msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:81 -msgid "Step 4 (optional): Further configurations for Sipgate" +#: ../system/core-workflows/condition-operators.rst:37 +msgid "Matches if a specified value is not present." msgstr "" -#: ../system/integrations/cti/provider-configurations/sipgate.rst:80 -msgid "" -"If needed, you can now configure Zammad's Sipgate integration in more " -"detail. You can learn more about your options here: :ref:`Sipgate " -"integration settings `." +#: ../system/core-workflows/condition-operators.rst:39 +msgid "Matches if one specified value is present." msgstr "" -#: ../system/integrations/cti/sipgate.rst:2 -msgid "Sipgate (sipgate.io)" +#: ../system/core-workflows/condition-operators.rst:41 +msgid "Matches if one specified value is not present." msgstr "" -#: ../system/integrations/cti/sipgate.rst:16 -msgid "You need an administrative Sipgate account for your organization." +#: ../system/core-workflows/condition-operators.rst:42 +msgid "does not match regex" msgstr "" -#: ../system/integrations/cti/sipgate.rst:17 -msgid "" -"Zammad requires a ``sipgate.io`` addon from the feature store (please note " -"that API calls are not free with Sipgate. Rates may apply and differ from " -"account to account)." +#: ../system/core-workflows/condition-operators.rst:43 +msgid "Matches if content doesn't fit to regex rule." msgstr "" -#: ../system/integrations/cti/sipgate.rst:21 -msgid "Sipgate must be able to reach your Zammad instance." +#: ../system/core-workflows/condition-operators.rst:44 +msgid "ends with" msgstr "" -#: ../system/integrations/cti/sipgate.rst:25 -msgid ":doc:`provider-configurations/sipgate`" +#: ../system/core-workflows/condition-operators.rst:45 +msgid "Matches if content ends with specified value." msgstr "" -#: ../system/integrations/cti/sipgate.rst:24 -msgid "" -"Learn how to configure Sipgate to enable Zammad and Sipgate to communicate " -"with each other." +#: ../system/core-workflows/condition-operators.rst:46 +msgid "ends with one of" msgstr "" -#: ../system/integrations/cti/sipgate.rst:33 -msgid "" -"Below endpoint settings affect the :doc:`sipgate.io configuration `." +#: ../system/core-workflows/condition-operators.rst:47 +msgid "Matches if content ends with one of the specified values." msgstr "" -#: ../system/integrations/cti/sipgate.rst:37 -msgid "This endpoint is required for incoming call hooks." +#: ../system/core-workflows/condition-operators.rst:48 +msgid "from (relative)" msgstr "" -#: ../system/integrations/cti/sipgate.rst:40 -msgid "This endpoint is required for outgoing call hooks." +#: ../system/core-workflows/condition-operators.rst:49 +msgid "Matches if date/time is after a period of time after an event." msgstr "" -#: ../system/integrations/cti/sipgate.rst:0 -msgid "Screenshot showing sample user mappings in between Sipgate and Zammad" +#: ../system/core-workflows/condition-operators.rst:51 +msgid "Matches if content is equal to a specified value." msgstr "" -#: ../system/integrations/cti/sipgate.rst:69 -msgid "" -"You can find your agent's Sipgate username within ``Accountverwaltung → " -"Benutzer``. You're looking for the SIP-ID." +#: ../system/core-workflows/condition-operators.rst:52 +msgid "is any of" msgstr "" -#: ../system/integrations/cti/sipgate.rst:0 -msgid "Sample VoIP credentials for a Sipgate user" +#: ../system/core-workflows/condition-operators.rst:53 +msgid "Matches if content is equal to any of specified values." msgstr "" -#: ../system/integrations/cti/sipgate.rst:77 -msgid "Users with several devices also have several SIP-IDs." +#: ../system/core-workflows/condition-operators.rst:54 +msgid "is modified" msgstr "" -#: ../system/integrations/elasticsearch.rst:2 -msgid "Elasticsearch (SaaS)" +#: ../system/core-workflows/condition-operators.rst:55 +msgid "Matches if content is modified." msgstr "" -#: ../system/integrations/elasticsearch.rst:4 -msgid "" -"The Elasticsearch integration allows you to create a read-only user to use " -"with your favorite reporting tool (e.g. like Grafana)." +#: ../system/core-workflows/condition-operators.rst:57 +#: ../system/core-workflows/condition-operators.rst:61 +msgid "True from the moment of changing content until form submit." msgstr "" -#: ../system/integrations/elasticsearch.rst:7 -msgid "" -"If you want to take full advantage of the Zammad reporting, have a look at " -"our :docs:`Grafana ` " -"setup page as well." +#: ../system/core-workflows/condition-operators.rst:58 +msgid "is modified to" msgstr "" -#: ../system/integrations/elasticsearch.rst:11 -#: ../system/subscription/index.rst:7 -msgid "**🚧 Hosted environment specific 🚧**" +#: ../system/core-workflows/condition-operators.rst:59 +msgid "Matches if content is modified to a specific value." msgstr "" -#: ../system/integrations/elasticsearch.rst:13 -msgid "" -"This integration is only available for Hosted setups. In order to use " -"Elasticsearch you'll need the **Plus** subscription." +#: ../system/core-workflows/condition-operators.rst:62 +msgid "is none of" msgstr "" -#: ../system/integrations/elasticsearch.rst:16 -msgid "" -"Self hosted users have all the control over their self hosted Elasticsearch " -"instances." +#: ../system/core-workflows/condition-operators.rst:63 +msgid "Matches if content is none of any specified values." msgstr "" -#: ../system/integrations/elasticsearch.rst:None -msgid "Elasticsearch integration page on SaaS environments" +#: ../system/core-workflows/condition-operators.rst:65 +msgid "Matches if content is not equal to a specified value." msgstr "" -#: ../system/integrations/elasticsearch.rst:27 -msgid "" -"Please note the following limitations of Elasticsearch access on hosted " -"environments:" +#: ../system/core-workflows/condition-operators.rst:67 +msgid "Matches if content is present." msgstr "" -#: ../system/integrations/elasticsearch.rst:30 -msgid "access to the Elasticsearch index is read-only access" +#: ../system/core-workflows/condition-operators.rst:68 +msgid "just changed" msgstr "" -#: ../system/integrations/elasticsearch.rst:31 -msgid "currently you're limited to user only" +#: ../system/core-workflows/condition-operators.rst:69 +msgid "Matches if content has changed." msgstr "" -#: ../system/integrations/elasticsearch.rst:32 +#: ../system/core-workflows/condition-operators.rst:71 +#: ../system/core-workflows/condition-operators.rst:75 msgid "" -"Reporting tools that require to write into the indexes (like Kibana) are not " -"supported" +"Only true for the moment of changing content until next form field action/" +"click." msgstr "" -#: ../system/integrations/elasticsearch.rst:34 -msgid "IP access restriction is currently not yet supported" +#: ../system/core-workflows/condition-operators.rst:72 +msgid "just changed to" msgstr "" -#: ../system/integrations/elasticsearch.rst:37 -msgid "Activating Elasticsearch Access" +#: ../system/core-workflows/condition-operators.rst:73 +msgid "Matches if content has changed to a specified value." msgstr "" -#: ../system/integrations/elasticsearch.rst:39 -msgid "" -"By default external access to your Elasticsearch index is not active. You " -"can enable the integration at any time if needed." +#: ../system/core-workflows/condition-operators.rst:76 +msgid "matches regex" msgstr "" -#: ../system/integrations/elasticsearch.rst:42 -msgid "" -"Please ensure to note down the password provided - you won't have access to " -"it afterwards." -msgstr "" - -#: ../system/integrations/elasticsearch.rst:None -msgid "Screencast showing activation of Elasticsearch integration" +#: ../system/core-workflows/condition-operators.rst:77 +msgid "Matches if value fits to regex rule." msgstr "" -#: ../system/integrations/elasticsearch.rst:51 -msgid "Connection Settings" +#: ../system/core-workflows/condition-operators.rst:79 +msgid "Matches if no content is present." msgstr "" -#: ../system/integrations/elasticsearch.rst:53 -msgid "" -"This section holds the most important general information for accessing your " -"Elasticsearch indexes - such as:" +#: ../system/core-workflows/condition-operators.rst:80 +msgid "starts with" msgstr "" -#: ../system/integrations/elasticsearch.rst:57 -msgid "A unique subdomain that does not tell your real instance URL." +#: ../system/core-workflows/condition-operators.rst:81 +msgid "Matches if content starts with specified value." msgstr "" -#: ../system/integrations/elasticsearch.rst:61 -msgid "Software" +#: ../system/core-workflows/condition-operators.rst:82 +msgid "starts with one of" msgstr "" -#: ../system/integrations/elasticsearch.rst:60 -msgid "" -"The major version of the search index being used. This is required by some " -"Reporting tools like Grafana." +#: ../system/core-workflows/condition-operators.rst:83 +msgid "Matches if content starts with one of the specified values." msgstr "" -#: ../system/integrations/elasticsearch.rst:64 -msgid "Authentication" +#: ../system/core-workflows/condition-operators.rst:84 +msgid "till (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:64 -msgid "The authentication type being supported. ``Basic Authentication``" +#: ../system/core-workflows/condition-operators.rst:85 +msgid "Matches if date/time is before a period of time before an event." msgstr "" -#: ../system/integrations/elasticsearch.rst:67 -msgid "Available Indexes" +#: ../system/core-workflows/condition-operators.rst:86 +msgid "today" msgstr "" -#: ../system/integrations/elasticsearch.rst:69 -msgid "" -"Within this section we're displaying the -in our opinion- most important " -"indexes for a Zammad instance." +#: ../system/core-workflows/condition-operators.rst:87 +msgid "Matches if date/time is today." msgstr "" -#: ../system/integrations/elasticsearch.rst:72 -msgid "" -"If you require all indexes or our listing is not good enough for you, point " -"your browser to the URL we're providing and append ``/_aliases?" -"pretty=true``. The result should look like this: ``https://.zammad.com/" -"_aliases?pretty=true``." +#: ../system/core-workflows/condition-operators.rst:88 +msgid "within last (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:77 +#: ../system/core-workflows/condition-operators.rst:89 msgid "" -"Your browser will automatically ask for your credentials - you'll then see " -"something like this:" +"Matches if date/time content is within specified period of time before now." msgstr "" -#: ../system/integrations/elasticsearch.rst:125 -msgid "Credentials" +#: ../system/core-workflows/condition-operators.rst:91 +msgid "within next (relative)" msgstr "" -#: ../system/integrations/elasticsearch.rst:127 +#: ../system/core-workflows/condition-operators.rst:92 msgid "" -"Within this section Zammad displays your available users. The password is " -"provided once (upon activation) and cannot be retrieved after that." +"Matches if date/time content is within specified period of time after now." msgstr "" -#: ../system/integrations/elasticsearch.rst:131 -msgid "" -"If you need to change or reset your Elasticsearch user password, use the " -"\"Reset password\" button in the credentials table. Doing so creates a brand " -"new password for the account in question. This change is immediate, keep in " -"mind that this may affect third party tools connected to your instance." +#: ../system/core-workflows/how-do-they-work.rst:2 +msgid "How do they work?" msgstr "" -#: ../system/integrations/exchange.rst:2 -msgid "Exchange" +#: ../system/core-workflows/how-do-they-work.rst:4 +msgid "" +"Core Workflows are executed according to their priority. If two workflows " +"have the same priority, they are executed in alphabetical order based on " +"their **name**." msgstr "" -#: ../system/integrations/exchange.rst:4 +#: ../system/core-workflows/how-do-they-work.rst:8 msgid "" -"With Zammad's Exchange integration, you can easily use existing address " -"books without having to update more than one source." +"Because of the way Core Workflows work, all changes to attributes are " +"checked with the application server - please see :doc:`limitations` for " +"possible issues." msgstr "" -#: ../system/integrations/exchange.rst:7 +#: ../system/core-workflows/how-do-they-work.rst:12 msgid "" -"However, you should refrain from syncing all addresses, as the results may " -"not be what you expect (Exchange collects huge amounts of addresses). A " -"central address book of your company to sync makes more sense, as you can " -"ensure that Zammad gets only the data you need and want. Apart from this, it " -"is even not possible to sync the Global Address List (GAL) of your Exchange " -"system with Zammad." +"Below we're talking about settings that are important and not self-" +"explanatory." msgstr "" -#: ../system/integrations/exchange.rst:16 +#: ../system/core-workflows/how-do-they-work.rst:17 msgid "" -"**Exchange and LDAP:** The exchange sync can be overruled by Zammad's LDAP " -"integration. If you have the same users in both sources, the LDAP version " -"will always be Zammad's pick." +"Choose the object context you want to run the workflow in. This will decide " +"on your available attributes and actions." msgstr "" -#: ../system/integrations/exchange.rst:19 -msgid "" -"**One way sync:** the Exchange sync is one way. Exchange => Zammad. Changes " -"to your users inside of Zammad might be overwritten by the Exchange sync." +#: ../system/core-workflows/how-do-they-work.rst:20 +msgid "Ticket objects also have access to the ticket customer." msgstr "" -#: ../system/integrations/exchange.rst:24 +#: ../system/core-workflows/how-do-they-work.rst:25 msgid "" -"To configure Exchange integration, simply go to the System > Integrations > " -"Exchange in the admin panel. Press \"change\" and follow the wizard for " -"adding the needed Exchange information to Zammad. On the last two steps " -"Zammad will ask you for the address book(s) and your desired attribute " -"mapping. By default, Zammad only maps email address, first- and lastname. " -"Technically, you can map any Exchange object to a Zammad user object (this " -"also works for custom objects!)." +"Choose in which situation the workflow is applied. Contexts can be combined " +"to avoid duplicate workflows." msgstr "" -#: ../system/integrations/exchange.rst:35 -msgid "" -"If the SSL verification fails while connecting to Exchange, Zammad will ask " -"you to turn it off temporarily." +#: ../system/core-workflows/how-do-they-work.rst:30 +msgid "Creation mask" msgstr "" -#: ../system/integrations/exchange.rst:38 +#: ../system/core-workflows/how-do-they-work.rst:29 msgid "" -"Please be aware that **turning off SSL verification is a security risk**. It " -"should only be used temporarily or for testing purposes. If turned off, " -"there is no verification of the certificate, which means that every " -"presented certificate will be accepted." +"If selected, your conditions and actions will affect all applicable creation " +"masks." msgstr "" -#: ../system/integrations/exchange.rst:43 -msgid "" -"After pressing Continue, Zammad will check if the configuration is okay. You " -"can then enable Exchange and start your first sync. The sync will then run " -"hourly - if you need to change mappings or the address book(s), you can " -"change the configuration at any time." +#: ../system/core-workflows/how-do-they-work.rst:34 +msgid "Edit mask" msgstr "" -#: ../system/integrations/exchange.rst:50 +#: ../system/core-workflows/how-do-they-work.rst:33 msgid "" -"After the sync has finished, you can find the new Exchange contacts under " -"\"Users\". Zammad integrates them just as normal users." +"If selected, your conditions and actions will affect all applicable edit " +"masks." msgstr "" -#: ../system/integrations/exchange.rst:55 +#: ../system/core-workflows/how-do-they-work.rst:39 msgid "" -"In some cases you might see unique IDs as \"Login\" instead of the email " -"address. This is normal and doesn't affect the login or email mapping for " -"that entry." +"Zammad differentiates between selected and saved conditions. These can be " +"combined wherever needed." msgstr "" -#: ../system/integrations/github.rst:4 -msgid "" -"Use GitHub integration to track GitHub issues directly within Zammad " -"tickets. Add issue hyperlinks and get a live summary of metadata like status " -"(open/closed), assignee, labels, and more." +#: ../system/core-workflows/how-do-they-work.rst:42 +msgid "**⚠️ Restrict workflows to specific roles if needed!**" msgstr "" -#: ../system/integrations/github.rst:8 -msgid "Please note that our GitHub integration does not support pull requests." +#: ../system/core-workflows/how-do-they-work.rst:44 +msgid "" +"By default and unless configured in conditions, workflow rules are executed " +"for **all roles**. This also affects your customers!" msgstr "" -#: ../system/integrations/github.rst:None -msgid "Integration page for GitHub" +#: ../system/core-workflows/how-do-they-work.rst:50 +msgid "Selected Conditions" msgstr "" -#: ../system/integrations/github.rst:18 +#: ../system/core-workflows/how-do-they-work.rst:48 msgid "" -"In your GitHub settings, create a new API token under **Developer settings > " -"Personal access tokens > Generate new token**. Leave the **Scopes** section " -"empty." +"These conditions are based on form values and match if an appropriate " +"selection is made (e.g. choosing another group in the ticket without " +"saving). This applies for drafts (active selection) and currently saved " +"values." msgstr "" -#: ../system/integrations/github.rst:0 ../system/integrations/gitlab.rst:0 -msgid "Screencast showing how to create a new API token" +#: ../system/core-workflows/how-do-they-work.rst:64 +msgid "Saved Conditions" msgstr "" -#: ../system/integrations/github.rst:27 -msgid "Create a new API key with no scopes/privileges." +#: ../system/core-workflows/how-do-they-work.rst:53 +msgid "" +"These conditions only match if the selected values are stored in the " +"database. It ignores the current value or selection of the field, as long as " +"the changes are not saved (e.g. performing field operations for an existing " +"ticket, which is viewed/opened by an agent)." msgstr "" -#: ../system/integrations/github.rst:29 -msgid "🔒 **Will this work for private repos?**" +#: ../system/core-workflows/how-do-they-work.rst:60 +msgid "" +"Keep in mind that the value has to be available in the situation where you " +"need it. Otherwise the condition won't match." msgstr "" -#: ../system/integrations/github.rst:31 +#: ../system/core-workflows/how-do-they-work.rst:63 msgid "" -"No. To link private repo issues, **use the** ``repo`` **scope instead**. " -"Bear in mind that the resulting token will have `lots of permissions that it " -"doesn't actually need `_, which presents a security risk if your token ever falls into " -"the wrong hands." +"Example: you can't perform any actions with *saved condition* on a ticket in " +"creation, because there are no saved values at that time." msgstr "" -#: ../system/integrations/github.rst:37 +#: ../system/core-workflows/how-do-they-work.rst:66 msgid "" -"Unfortunately, because of how GitHub's OAuth token scopes are set up, this " -"is the only way to link issues on private repos." +"You can find a description of the condition operators for core workflows :" +"doc:`here `." msgstr "" -#: ../system/integrations/github.rst:40 -msgid "Enter your new API token in Zammad and enable GitHub integration." +#: ../system/core-workflows/how-do-they-work.rst:72 +msgid "" +"Which actions should we run on the relevant fields? The possible actions " +"depend on the object type. However, usually you can at least change the " +"visibility and whether the field is mandatory." msgstr "" -#: ../system/integrations/github.rst:0 -msgid "Screencast showing how to configure Zammad's GitHub integration" +#: ../system/core-workflows/how-do-they-work.rst:76 +msgid "Be aware that actions are not available for **related** context." msgstr "" -#: ../system/integrations/github.rst:47 +#: ../system/core-workflows/how-do-they-work.rst:78 msgid "" -"Use the default API endpoint (``https://api.github.com/graphql``) unless " -"you're using GitHub Enterprise Server." +"**Example:** Let's assume you are working in the ticket context. While you " +"can have customer *conditions*, you *can't adjust* objects with actions in " +"that scope. That's because this wouldn't have any impact on the ticket " +"dialog. Of course all ticket attributes (state, owner, ...) are available." msgstr "" -#: ../system/integrations/github.rst:50 +#: ../system/core-workflows/how-do-they-work.rst:84 msgid "" -"Once completed, a new GitHub issues tab will appear in the ticket pane. 🎉" +"Please also have a look at our :doc:`limitations` to be safe from surprises." msgstr "" -#: ../system/integrations/github.rst:59 ../system/integrations/gitlab.rst:52 -msgid "Token verification is taking a long time" +#: ../system/core-workflows/how-do-they-work.rst:88 +msgid "Available Operators" msgstr "" -#: ../system/integrations/github.rst:56 ../system/integrations/gitlab.rst:49 -msgid "" -"Slight delays are normal (<2 min.), especially for systems under heavy load." +#: ../system/core-workflows/how-do-they-work.rst:90 +msgid "The availability of operators depends on the object type and scope." msgstr "" -#: ../system/integrations/github.rst:58 +#: ../system/core-workflows/how-do-they-work.rst:94 msgid "" -"Self-hosted administrators, please check your network settings to ensure " -"that your Zammad server can reach ``api.github.com``." +"Please note that actions may or may not restrict API based access to " +"attributes. We're displaying the following icons for your overview to " +"understand these limits better:" msgstr "" -#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 -msgid "I reloaded the page and now the API token is gone" +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|api| This icon indicates the action affects the API." msgstr "" -#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 -msgid "" -"This may indicate that Zammad is still verifying your API token. Try " -"reloading the page again in a couple minutes." +#: ../system/core-workflows/how-do-they-work.rst:163 +msgid "api" msgstr "" -#: ../system/integrations/gitlab.rst:2 -msgid "GitLab" +#: ../system/core-workflows/how-do-they-work.rst:0 +msgid "|ui| This icon indicates the action only affects the web interface." msgstr "" -#: ../system/integrations/gitlab.rst:4 -msgid "" -"Use GitLab integration to track GitLab issues directly within Zammad " -"tickets. Add issue hyperlinks and get a live summary of metadata like status " -"(open/closed), assignee, labels, and more." +#: ../system/core-workflows/how-do-they-work.rst:167 +msgid "ui" msgstr "" -#: ../system/integrations/gitlab.rst:8 -msgid "" -"Please note that our GitLab integration does not support merge requests." +#: ../system/core-workflows/how-do-they-work.rst:102 +msgid "show |ui|" msgstr "" -#: ../system/integrations/gitlab.rst:None -msgid "Integration page for GitLab" +#: ../system/core-workflows/how-do-they-work.rst:102 +msgid "Display the chosen field. Allows setting of values." msgstr "" -#: ../system/integrations/gitlab.rst:18 -msgid "" -"In your GitLab preferences, create a new API token under **Access Tokens**." +#: ../system/core-workflows/how-do-they-work.rst:109 +msgid "hide |ui|" msgstr "" -#: ../system/integrations/gitlab.rst:20 -msgid "Under **Select scopes**, choose ``read_api`` only." +#: ../system/core-workflows/how-do-they-work.rst:105 +msgid "" +"Hide the chosen field. However, it technically still allows setting the " +"field." msgstr "" -#: ../system/integrations/gitlab.rst:27 -msgid "🔒 **If you wish to link issues on any private repos...**" +#: ../system/core-workflows/how-do-they-work.rst:108 +msgid "" +"Please note that the field is **not** gone and still contains an existing " +"value (if set)! Consider *remove* instead, if you want this field to be gone." msgstr "" -#: ../system/integrations/gitlab.rst:29 -msgid "Your API token must belong to an account with access to those repos." +#: ../system/core-workflows/how-do-they-work.rst:112 +msgid "remove |ui|" msgstr "" -#: ../system/integrations/gitlab.rst:31 -msgid "Enter your new API token in Zammad and enable GitLab integration." +#: ../system/core-workflows/how-do-they-work.rst:112 +msgid "Entirely removes the field. The field value will not be evaluated." msgstr "" -#: ../system/integrations/gitlab.rst:0 -msgid "Screencast showing how to configure Zammad's GitLab integration" +#: ../system/core-workflows/how-do-they-work.rst:115 +msgid "set mandatory |ui| |api|" msgstr "" -#: ../system/integrations/gitlab.rst:40 -msgid "" -"Use the default API endpoint (``https://gitlab.com/api/graphql``) unless " -"you're a self-hosted GitLab user." +#: ../system/core-workflows/how-do-they-work.rst:115 +msgid "Sets the field to mandatory." msgstr "" -#: ../system/integrations/gitlab.rst:43 -msgid "" -"Once completed, a new GitLab issues tab will appear in the ticket pane. 🎉" +#: ../system/core-workflows/how-do-they-work.rst:118 +msgid "set optional |ui| |api|" msgstr "" -#: ../system/integrations/gitlab.rst:51 -msgid "" -"Self-hosted administrators, please check your network settings to ensure " -"that your Zammad server can reach ``gitlab.com``." +#: ../system/core-workflows/how-do-they-work.rst:118 +msgid "Sets the field to optional." msgstr "" -#: ../system/integrations/i-doit.rst:2 -msgid "i-doit" +#: ../system/core-workflows/how-do-they-work.rst:124 +msgid "add option |ui| |api|" msgstr "" -#: ../system/integrations/i-doit.rst:4 -msgid "" -"`i-doit `_ is an open-source **configuration " -"management database** - in other words, a tool for keeping tabs on every " -"single piece of your physical and digital infrastructure, from network " -"equipment to virtual machines on down to the faceplates on your rack shelves " -"and more." +#: ../system/core-workflows/how-do-they-work.rst:121 +msgid "Allows adding options to tree selects or selects." msgstr "" -#: ../system/integrations/i-doit.rst:10 +#: ../system/core-workflows/how-do-they-work.rst:123 msgid "" -"What's that got to do with Zammad? Well, if you used tickets to track issues " -"with all that hardware, you might start wishing there was a way they could " -"talk to each other." -msgstr "" - -#: ../system/integrations/i-doit.rst:14 -msgid "Zammad gives you two:" +"You have to use the \"remove option\" before performing this action. It " +"allows you to use *existing* configured values." msgstr "" -#: ../system/integrations/i-doit.rst:17 -msgid "1. Add i-doit Links to Zammad Tickets" +#: ../system/core-workflows/how-do-they-work.rst:128 +msgid "remove option |ui| |api|" msgstr "" -#: ../system/integrations/i-doit.rst:20 ../system/integrations/i-doit.rst:80 -msgid "What Users See" +#: ../system/core-workflows/how-do-they-work.rst:127 +msgid "" +"Allows removing options from tree selects or selects. It allows you to use " +"*existing* configured values." msgstr "" -#: ../system/integrations/i-doit.rst:26 -msgid "i-doit integration in Zammad's ticket pane" +#: ../system/core-workflows/how-do-they-work.rst:134 +msgid "set fixed to |ui| |api|" msgstr "" -#: ../system/integrations/i-doit.rst:26 -msgid "" -"The i-doit integration will appear under a new 🖨 tab in the ticket pane." +#: ../system/core-workflows/how-do-they-work.rst:131 +msgid "Reduces the available options by your selection." msgstr "" -#: ../system/integrations/i-doit.rst:28 +#: ../system/core-workflows/how-do-they-work.rst:133 msgid "" -"i-doit integration puts a new tab in Zammad's ticket pane where you can add " -"links to existing i-doit devices for easy reference. (See our :user-docs:" -"`user documentation ` to learn " -"how it works in practice)." +"This reduces your workflows in terms of *add option* and *remove option*." msgstr "" -#: ../system/integrations/i-doit.rst:36 ../system/integrations/i-doit.rst:93 -msgid "How to Set it Up" +#: ../system/core-workflows/how-do-they-work.rst:137 +msgid "fill in |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:38 -msgid "" -"It requires i-doit's `API Add-on `_. Make sure to have it properly set up. Use the following setting:" +#: ../system/core-workflows/how-do-they-work.rst:137 +msgid "Allows filling in of string and integer fields with your values." msgstr "" -#: ../system/integrations/i-doit.rst:42 -msgid "Active: ``Yes``" +#: ../system/core-workflows/how-do-they-work.rst:141 +msgid "fill in empty |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:43 -msgid "Enforce authentication by username and password: ``No``" +#: ../system/core-workflows/how-do-they-work.rst:140 +msgid "" +"Allows filling in of string and integer fields with your values **if the " +"field is empty**." msgstr "" -#: ../system/integrations/i-doit.rst:45 -msgid "" -"To set it up, enable the integration in the Zammad admin panel under " -"**System > Integrations > i-doit**:" +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "select |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "i-doit settings within the integration pages" +#: ../system/core-workflows/how-do-they-work.rst:144 +msgid "Select a specific value within a select, tree select or boolean field." msgstr "" -#: ../system/integrations/i-doit.rst:53 -msgid "The root URL of your i-doit installation." +#: ../system/core-workflows/how-do-they-work.rst:153 +msgid "auto select |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:62 -msgid "API token" +#: ../system/core-workflows/how-do-they-work.rst:147 +msgid "Helps users with tree select and select fields:" msgstr "" -#: ../system/integrations/i-doit.rst:56 +#: ../system/core-workflows/how-do-they-work.rst:149 msgid "" -"Found in the i-doit admin panel under **Interfaces / external data > JSON-" -"RPC API > Common Settings**." +"If the field has only one option available for selection and no value yet, " +"the value will be automatically set." msgstr "" -#: ../system/integrations/i-doit.rst:0 -msgid "i-doit administration interface with API configuration" +#: ../system/core-workflows/how-do-they-work.rst:152 +msgid "" +"This option only works if you have one value and doesn't work if there is " +"more than one option available." msgstr "" -#: ../system/integrations/i-doit.rst:67 -msgid "Client ID" +#: ../system/core-workflows/how-do-they-work.rst:157 +msgid "set readonly |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:65 -msgid "A unique name to identify Zammad within i-doit." +#: ../system/core-workflows/how-do-they-work.rst:156 +msgid "" +"Allows you to display an attribute as read only (which means no changes are " +"possible)." msgstr "" -#: ../system/integrations/i-doit.rst:67 -msgid "(Zammad does not require you to enter a value here, but i-doit might!)" +#: ../system/core-workflows/how-do-they-work.rst:161 +msgid "unset readonly |ui|" msgstr "" -#: ../system/integrations/i-doit.rst:70 +#: ../system/core-workflows/how-do-they-work.rst:160 msgid "" -"Here you can decide if the certificate of your i-doit system has to be " -"verified or not. In case you are using custom certificates, please have a " -"look at :doc:`how to add them to Zammad `." +"In case a workflow set the field in question to read only, you can undo this " +"with option above." msgstr "" -#: ../system/integrations/i-doit.rst:77 -msgid "2. List / Create Zammad Tickets in i-doit" +#: ../system/core-workflows/how-do-they-work.rst:172 +msgid "Stop after match" msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "Zammad integration in i-doit's device view" +#: ../system/core-workflows/how-do-they-work.rst:174 +msgid "" +"Here you can decide if other workflows are executed after the current one." msgstr "" -#: ../system/integrations/i-doit.rst:86 +#: ../system/core-workflows/how-do-they-work.rst:176 msgid "" -"i-doit's ticket system integration gives you a way to see all the tickets " -"for a given device without ever leaving i-doit. (See our :user-docs:`user " -"documentation ` to learn how it " -"works in practice)." +"If set to ``no`` (default), further workflows will be executed if they match " +"the condition. In this case, it is possible that your actions from the " +"current workflow can be overwritten by another workflow." msgstr "" -#: ../system/integrations/i-doit.rst:95 +#: ../system/core-workflows/how-do-they-work.rst:180 msgid "" -"Enable this integration in the i-doit admin panel under **Interfaces / " -"external data > Trouble Ticket System (TTS) > Configuration**:" +"If set to ``yes``, no further worflows will be executed after the current " +"one." msgstr "" -#: ../system/integrations/i-doit.rst:None -msgid "i-doit administration interface with TTS configuration" +#: ../system/core-workflows/how-do-they-work.rst:184 +msgid "Priority" msgstr "" -#: ../system/integrations/i-doit.rst:104 -msgid "TTS-Type" +#: ../system/core-workflows/how-do-they-work.rst:186 +msgid "" +"You can define the sequence, in which the workflows are executed. The " +"default value is ``500``." msgstr "" -#: ../system/integrations/i-doit.rst:104 -msgid "``Zammad``" +#: ../system/core-workflows/how-do-they-work.rst:189 +msgid "" +"The workflows are executed in ascending order by their priority. That means " +"lower values (e.g. ``100``) are executed before higher ones (e.g. ``999``)." msgstr "" -#: ../system/integrations/i-doit.rst:115 -msgid "Username / Password" -msgstr "" +#: ../system/core-workflows/learn-by-example.rst:2 +#, fuzzy +msgid "Learn by Example" +msgstr "例如" -#: ../system/integrations/i-doit.rst:107 -msgid "Login credentials for a Zammad agent." +#: ../system/core-workflows/learn-by-example.rst:4 +msgid "" +"This page provides some basic examples for Core Workflows. Of course you can " +"build much more complex workflows if needed." msgstr "" -#: ../system/integrations/i-doit.rst:109 +#: ../system/core-workflows/learn-by-example.rst:7 msgid "" -"This agent must have **read permission** for all :doc:`groups ` that plan on using the i-doit integration." +"To learn about Core Workflows in detail, first go to :doc:`how-do-they-work`." msgstr "" -#: ../system/integrations/i-doit.rst:113 +#: ../system/core-workflows/learn-by-example.rst:10 +#, fuzzy +msgid "Group Based Examples" +msgstr "例如" + +#: ../system/core-workflows/learn-by-example.rst:12 msgid "" -"You may even wish to create a dedicated agent account just for this " -"integration (otherwise, if the agent ever changes her password, you will " -"have to remember to update it here)." +"All following workflows have the same base configurations. The workflow may " +"not use them all." msgstr "" -#: ../system/integrations/i-doit.rst:117 -msgid "URL incl. protocol" -msgstr "" +#: ../system/core-workflows/learn-by-example.rst:15 +#, fuzzy +msgid "Groups:" +msgstr "组" -#: ../system/integrations/i-doit.rst:118 -msgid "``https://your.zammad.domain``" +#: ../system/core-workflows/learn-by-example.rst:20 +msgid "Attributes:" msgstr "" -#: ../system/integrations/index.rst:2 -msgid "Integrations" +#: ../system/core-workflows/learn-by-example.rst:22 +msgid "Category (Single tree selection field, not mandatory, agents only)" msgstr "" -#: ../system/integrations/index.rst:4 +#: ../system/core-workflows/learn-by-example.rst:23 msgid "" -"Zammad offers numerous integrations that add rich features to your instance." +"Approved (Boolean field, not mandatory, not shown, ``false`` as default)" msgstr "" -#: ../system/integrations/index.rst:6 -msgid "We're still working on this part of our documentation, stay tight!" +#: ../system/core-workflows/learn-by-example.rst:24 +msgid "Operating System (Text field, not mandatory, not shown)" msgstr "" -#: ../system/integrations/index.rst:10 -msgid "Integrations for Phone Systems" +#: ../system/core-workflows/learn-by-example.rst:25 +msgid "Software used (Single selection field, not mandatory, not shown)" msgstr "" -#: ../system/integrations/index.rst:14 -msgid "" -"Your VoIP provider or telephony system is not listed? Possibly your provider " -"supports Zammad by using the generic CTI - if you're unsure ask your " -"provider." +#: ../system/core-workflows/learn-by-example.rst:68 +msgid "Group specific values and fields" msgstr "" -#: ../system/integrations/index.rst:18 +#: ../system/core-workflows/learn-by-example.rst:28 msgid "" -"Provider does not support Zammad? Consider creating a `feature request in " -"the Zammad Community `_." -msgstr "" - -#: ../system/integrations/index.rst:31 -msgid "Integrations for Authentication and Customers" +"This workflow set depends on the category field. It reduces the available " +"set of values based on the group selected." msgstr "" -#: ../system/integrations/index.rst:44 -msgid "Integrations for Monitoring Systems" +#: ../system/core-workflows/learn-by-example.rst:33 +msgid "Workflow 2nd Level group" msgstr "" -#: ../system/integrations/index.rst:46 -msgid "This section currently misses the following integrations:" +#: ../system/core-workflows/learn-by-example.rst:35 +msgid "" +"This reduces the category options to ``2nd Level/*``, ``Internal/*`` and " +"``Others``. It also sets further required fields to mandatory and visible." msgstr "" -#: ../system/integrations/index.rst:48 -msgid "Icinga" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for 2nd level" msgstr "" -#: ../system/integrations/index.rst:49 -msgid "Monit" +#: ../system/core-workflows/learn-by-example.rst:43 +msgid "Workflow Support group" msgstr "" -#: ../system/integrations/index.rst:50 -msgid "Nagios" +#: ../system/core-workflows/learn-by-example.rst:45 +msgid "" +"This reduces the category options to ``Support/*``, ``Internal/*`` and " +"``Others``. It also sets further required fields to visible." msgstr "" -#: ../system/integrations/index.rst:60 -msgid "Integrations for Issue Trackers" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for support" msgstr "" -#: ../system/integrations/index.rst:70 -msgid "Other Integrations" +#: ../system/core-workflows/learn-by-example.rst:53 +msgid "Workflow Sales group" msgstr "" -#: ../system/integrations/index.rst:72 +#: ../system/core-workflows/learn-by-example.rst:55 msgid "" -"This section will hold any other integration that can't be grouped up (yet)." +"This reduces the category options to ``Sales/*``, ``Internal/*`` and " +"``Others``." msgstr "" -#: ../system/integrations/ldap/index.rst:2 -msgid "LDAP / Active Directory" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that shows specific values and fields for sales" msgstr "" -#: ../system/integrations/ldap/index.rst:4 -msgid "" -"Zammad comes with a powerful LDAP integration that allows you to have a " -"single source of truth. By this you reduce the number of login credentials " -"your user has to remember." +#: ../system/core-workflows/learn-by-example.rst:68 +#: ../system/integrations/slack.rst:88 +msgid "The Result" msgstr "" -#: ../system/integrations/ldap/index.rst:10 +#: ../system/core-workflows/learn-by-example.rst:63 msgid "" -"The LDAP source is also a perfect candidate for Zammad's :docs:`Kerberos " -"Single Sign-On ` but also works as addition " -"to other :doc:`/settings/security/third-party`." +"This is what the agent would experience with the above workflows in place." msgstr "" -#: ../system/integrations/ldap/index.rst:None -msgid "Zammands LDAP management page" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "" +"Workflow shows objects and limits options based on selections on the group" msgstr "" -#: ../system/integrations/ldap/index.rst:25 -msgid "📝 :doc:`manage`" +#: ../system/core-workflows/learn-by-example.rst:90 +msgid "Approval process" msgstr "" -#: ../system/integrations/ldap/index.rst:25 -msgid "Add, modify, remove or re-arrange your LDAP-Sources as needed." +#: ../system/core-workflows/learn-by-example.rst:71 +msgid "" +"In this case ``approved`` is visible to agents by default. For this " +"workflow, an additional role ``Approval person`` is required (no further " +"permissions)." msgstr "" -#: ../system/integrations/ldap/index.rst:30 -msgid "Before you continue, please note the following limitations." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that restricts an approval attribute to specific roles" msgstr "" -#: ../system/integrations/ldap/index.rst:32 -msgid "Mapping / Synchronizing organizations is not possible" +#: ../system/core-workflows/learn-by-example.rst:81 +msgid "" +"This workflow may work best in combination with a :doc:`trigger ` but technically, this is not required." msgstr "" -#: ../system/integrations/ldap/index.rst:36 +#: ../system/core-workflows/learn-by-example.rst:84 msgid "" -"You may want to consider using domain based assignments to overcome this " -"issue. Learn more on :doc:`/manage/organizations/index`." +"Select fields may be a better approach because they allow more values than " +"just a simple ``true`` or ``false``." msgstr "" -#: ../system/integrations/ldap/index.rst:39 +#: ../system/core-workflows/learn-by-example.rst:0 msgid "" -"Zammad's LDAP sync is one way. Editing user settings or permissions may be " -"overwritten upon the next sync depending on your configuration." +"Workflow fixes possible values of \"Approved ?\" to a specific selection " +"depending on the users role" msgstr "" -#: ../system/integrations/ldap/index.rst:41 -msgid "Nested groups are not supported." +#: ../system/core-workflows/learn-by-example.rst:103 +msgid "State dependent mandatory fields" msgstr "" -#: ../system/integrations/ldap/index.rst:42 -msgid "Synchronizing user avatars from LDAP is not supported." +#: ../system/core-workflows/learn-by-example.rst:93 +msgid "" +"This workflow sets ``Category`` to mandatory if the agent wants to set the " +"states ``closed`` or ``pending close`` to enforce categorization." msgstr "" -#: ../system/integrations/ldap/index.rst:43 -msgid "Unlike user filters, group filters cannot be changed." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Sample workflow that sets fields to mandatory on specific states" msgstr "" -#: ../system/integrations/ldap/index.rst:44 +#: ../system/core-workflows/learn-by-example.rst:0 msgid "" -"When a user originates from an LDAP server, Zammad will try to verify the " -"login credentials against LDAP first - if this fails Zammad will check its " -"local database." +"Workflow sets category field to mandatory upon choosing closed or pending " +"close as state" msgstr "" -#: ../system/integrations/ldap/index.rst:50 -msgid "" -"Users can have local passwords even if they're LDAP users! You can learn " -"more about user accounts in general on :doc:`/manage/users/index`." +#: ../system/core-workflows/learn-by-example.rst:106 +msgid "Manual Ticket Handover Process" msgstr "" -#: ../system/integrations/ldap/index.rst:54 -msgid "" -"When several LDAP sources contain the same user (meaning the same email " -"address), the user in question will be updated with every source configured. " -"*The last LDAP source will win.*" +#: ../system/core-workflows/learn-by-example.rst:108 +msgid "This example covers the handover of a ticket from one agent to another:" msgstr "" -#: ../system/integrations/ldap/index.rst:58 +#: ../system/core-workflows/learn-by-example.rst:110 msgid "" -"This is subject to change with `Issue 4109 `_ in the future." +"When the ticket owner is modified, a new text field (\"Handover\") shows up " +"for a comment" msgstr "" -#: ../system/integrations/ldap/index.rst:60 +#: ../system/core-workflows/learn-by-example.rst:112 msgid "" -"Synchronization statistics currently affect *all* configured LDAP sources. " -"This also applies for newly added or updated sources." +"This may only be visible when the owner is changed, therefore it has to be " +"hidden in general" msgstr "" -#: ../system/integrations/ldap/index.rst:63 -msgid "" -"This is subject to change with `Issue 4108 `_ in the future." +#: ../system/core-workflows/learn-by-example.rst:114 +msgid "The input in this handover text field is mandatory" msgstr "" -#: ../system/integrations/ldap/index.rst:65 +#: ../system/core-workflows/learn-by-example.rst:115 msgid "" -"Zammad currently has limited fallback server support. You can workaround " -"this by providing several sources - however, ensure to have the exact same " -"configuration on your fallback." +"After submitting changes, the value of the handover field must be added as " +"an note to the ticket (via trigger)" msgstr "" -#: ../system/integrations/ldap/index.rst:69 -msgid "" -"This is subject to improve with `Issue 4107 `_ in the future." +#: ../system/core-workflows/learn-by-example.rst:121 +msgid "Hiding handover field" msgstr "" -#: ../system/integrations/ldap/index.rst:76 -msgid "" -"This section holds all requests Zammad handled for all LDAP sources. These " -"entries can either contain synchronization information or logins " -"(authentication attempts via Zammad's login interface)." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Hiding the handover field in core workflows" msgstr "" -#: ../system/integrations/ldap/index.rst:80 -msgid "" -"By clicking on any request, Zammad will provide even more information. The " -"provided information can be useful when something does not work as expected." +#: ../system/core-workflows/learn-by-example.rst:126 +msgid "Showing handover field and setting it to mandatory" msgstr "" -#: ../system/integrations/ldap/index.rst:85 -msgid "" -"Especially a LDAP synchronization can cause many log entries. The web " -"interface will always limit the number of shown entries to the last 50 " -"entries." +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Showing the handover field and set it as mandatory" msgstr "" -#: ../system/integrations/ldap/index.rst:None -msgid "" -"Screencast showing LDAP integration log entries and a detail view on\n" -"an entry." +#: ../system/core-workflows/learn-by-example.rst:131 +msgid "Trigger writing handover input to a new article" msgstr "" -#: ../system/integrations/ldap/manage.rst:2 -msgid "Manage LDAP-Sources" +#: ../system/core-workflows/learn-by-example.rst:0 +msgid "Write handover content to a new article" msgstr "" -#: ../system/integrations/ldap/manage.rst:6 +#: ../system/core-workflows/learn-by-example.rst:133 msgid "" -"Please keep in mind all current limitations for the LDAP synchronization. " -"This will help to understand scopes of the following operations better." +"As a result, the ticket includes an article of the type note which includes " +"the predefined text and the handover comment." msgstr "" -#: ../system/integrations/ldap/manage.rst:65 -msgid "Add new source" +#: ../system/core-workflows/limitations.rst:6 +msgid "Core Workflows do not replace Triggers" msgstr "" -#: ../system/integrations/ldap/manage.rst:10 +#: ../system/core-workflows/limitations.rst:5 msgid "" -"Using the *New Source* button allows you to add new LDAP sources to your " -"installation. You're not limited in the number of sources, however, keep in " -"mind that many sources will also take more time to synchronize." +"Workflows manipulate the behavior of fields. However, they do not set values " +"in fields because of actions." msgstr "" -#: ../system/integrations/ldap/manage.rst:14 -msgid "" -"You can choose between different encryption types, namely *SSL* and " -"*STARTTLS* or none of them (\"*No SSL*\"). If you choose *SSL* or " -"*STARTTLS*, Zammad will display an additional *SSL verification* option that " -"allows you to disable the verification, e.g. for self-signed SSL " -"certificates. You can also tell Zammad to use a different port by appending " -"``:`` to your hostname/IP." +#: ../system/core-workflows/limitations.rst:16 +msgid "API calls are only partly affected" msgstr "" -#: ../system/integrations/ldap/manage.rst:0 +#: ../system/core-workflows/limitations.rst:9 msgid "" -"Screenshot of configuring a new LDAP source with SSL encryption and SSL " -"verification" +"Some options affect UI only and thus do not restrict responses and calls." msgstr "" -#: ../system/integrations/ldap/manage.rst:26 -msgid "" -"New Source with SSL transport security enabled and certificate verification" +#: ../system/core-workflows/limitations.rst:11 +msgid "This affects the following actions:" msgstr "" -#: ../system/integrations/ldap/manage.rst:30 -msgid "" -"Using an user filter can be a good idea if you only require a small subset " -"of your LDAP users in Zammad." +#: ../system/core-workflows/limitations.rst:13 +msgid "select" msgstr "" -#: ../system/integrations/ldap/manage.rst:42 -msgid "This especially affects inactive users" +#: ../system/core-workflows/limitations.rst:14 +msgid "auto select" msgstr "" -#: ../system/integrations/ldap/manage.rst:34 -msgid "" -"As every LDAP behaves differently on which attributes and how they are set, " -"Zammad doesn't care about any flags." +#: ../system/core-workflows/limitations.rst:15 +msgid "show" msgstr "" -#: ../system/integrations/ldap/manage.rst:37 -msgid "" -"Users that no longer are returned by your LDAP source will automatically be " -"set to inactive. Zammad assumes that the user was deactivated." +#: ../system/core-workflows/limitations.rst:16 +msgid "hide" msgstr "" -#: ../system/integrations/ldap/manage.rst:41 -msgid "" -"Users will never be removed automatically! If you want to remove obsolete " -"users, use :doc:`/system/data-privacy`." +#: ../system/core-workflows/limitations.rst:25 +msgid "Some fields stay unavailable to customers" msgstr "" -#: ../system/integrations/ldap/manage.rst:46 -msgid "Active Directory admins" +#: ../system/core-workflows/limitations.rst:19 +msgid "" +"For technical and security reasons, some default fields (the pale ones you " +"can't edit) stay unavailable for display and usage on customer permissions." msgstr "" -#: ../system/integrations/ldap/manage.rst:45 +#: ../system/core-workflows/limitations.rst:23 msgid "" -"Active Directories are quite specific on how to filter for active users only " -"- please see the `Microsoft documentation `_ for more " -"information." +"If you require your customers to change e.g. priorities, please consider " +"using workarounds via :doc:`/system/objects` and :doc:`/manage/trigger`." msgstr "" -#: ../system/integrations/ldap/manage.rst:51 -msgid "" -"*Do not* manually write pathes of either LDAP attributes or groups. If " -"Zammad does not display them, it either cannot find them or you have a lot " -"of users that don't have the attributes populated." +#: ../system/core-workflows/limitations.rst:29 +msgid "Ticket title changes not supported in edit mask" msgstr "" -#: ../system/integrations/ldap/manage.rst:55 +#: ../system/core-workflows/limitations.rst:28 msgid "" -"Zammad will always only return attributes that are filled - this reduces the " -"returned list of attributes greatly." +"It is currently not possible to perform changes of the ticket title in the " +"edit mask (e.g. renaming, set to read-only)." msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing how to add a new LDAP source" +#: ../system/core-workflows/limitations.rst:37 +msgid "What is out of scope of Core Workflows?" msgstr "" -#: ../system/integrations/ldap/manage.rst:63 +#: ../system/core-workflows/limitations.rst:32 msgid "" -"If your LDAP system doesn't allow anonymous bind, Zammad detects it and " -"provides you an editable \"Base DN\" *text* field instead of a prefilled " -"*select* field." +"There are some things that would count as workflow but are either done via :" +"doc:`/manage/trigger` or :doc:`/manage/scheduler`." msgstr "" -#: ../system/integrations/ldap/manage.rst:81 -msgid "Review or edit existing source" +#: ../system/core-workflows/limitations.rst:35 +msgid "Such as (but not limited to):" msgstr "" -#: ../system/integrations/ldap/manage.rst:68 -msgid "" -"Clicking on a LDAP source will provide a configuration and mapping overview." +#: ../system/core-workflows/limitations.rst:37 +msgid "up- or downgrade permissions of users" msgstr "" -#: ../system/integrations/ldap/manage.rst:70 -msgid "" -"If needed you can then use the *Change* button to update either the name, " -"active state or the whole configuration. If you're changing the whole " -"configuration, the dialogue will be identical to the source creation." +#: ../system/core-workflows/limitations.rst:38 +msgid "affecting article creation or listing" msgstr "" -#: ../system/integrations/ldap/manage.rst:76 -msgid "" -"Did your LDAP server change? Different LDAP servers have different " -"structures and default attributes. This causes the LDAP synchronization to " -"likely fail. Consider removing the affected source and re-add it." +#: ../system/data-privacy.rst:2 +msgid "Data Privacy" msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing the update of the source name." +#: ../system/data-privacy.rst:4 +msgid "" +"For compliance with GDPR and other data privacy laws, you may wish to " +"**permanently delete users from the system**, along with **all of their " +"associated tickets**." msgstr "" -#: ../system/integrations/ldap/manage.rst:89 -msgid "Re-arrange LDAP source's order" +#: ../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 `!" msgstr "" -#: ../system/integrations/ldap/manage.rst:84 +#: ../system/data-privacy.rst:12 msgid "" -"You can change the synchronization order for each source at any time. Zammad " -"will synchronize the sources from top to bottom." +"Access to this panel requires ``admin.data_privacy`` permissions (introduced " +"in Zammad 3.5)." msgstr "" -#: ../system/integrations/ldap/manage.rst:0 +#: ../system/data-privacy.rst:15 msgid "" -"Screencasting showing how to change the source order by using\n" -"drag and drop." +"On older systems that have not been updated yet, customers can also be :docs:" +"`deleted via the Zammad console `." msgstr "" -#: ../system/integrations/ldap/manage.rst:101 -msgid "Remove a source" +#: ../system/data-privacy.rst:22 +msgid "User deletion dialog in the Data Privacy panel" msgstr "" -#: ../system/integrations/ldap/manage.rst:92 +#: ../system/data-privacy.rst:22 msgid "" -"If you no longer need the a LDAP source or simply want to start over, you " -"can remove them at any time. This will not remove synchronized users, data " -"synchronized or permissions." +"The user deletion dialog lists some of the tickets that will be removed from " +"the system along with the user." msgstr "" -#: ../system/integrations/ldap/manage.rst:98 -msgid "" -"Not sure if you'd need the source later on? Set the source to inactive " -"instead of removing it - see *Review or edit existing source* for more." +#: ../system/data-privacy.rst:27 +msgid "Deleting Users via GUI" msgstr "" -#: ../system/integrations/ldap/manage.rst:0 -msgid "Screencast showing how to remove LDAP sources." +#: ../system/data-privacy.rst:29 +msgid "🔥 **All deletions are FINAL!**" msgstr "" -#: ../system/integrations/pgp/index.rst:2 -msgid "PGP" +#: ../system/data-privacy.rst:31 +msgid "Once you click “Delete”, the action cannot be canceled or undone." msgstr "" -#: ../system/integrations/pgp/index.rst:7 +#: ../system/data-privacy.rst:33 msgid "" -"Pretty Good Privacy (PGP) is another method for secure email communication. " -"With PGP, you can exchange **signed** and **encrypted** messages with others." +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:13 -#: ../system/integrations/smime/index.rst:17 -msgid "Signing" +#: ../system/data-privacy.rst:36 +msgid "**The following records cannot be deleted:**" msgstr "" -#: ../system/integrations/pgp/index.rst:11 -msgid "is a proof that a message hasn't been manipulated on its way." +#: ../system/data-privacy.rst:38 +msgid "your own account" msgstr "" -#: ../system/integrations/pgp/index.rst:13 -msgid "" -"In other words, it guarantees message **integrity** and **authenticity**." +#: ../system/data-privacy.rst:39 +msgid "the system's last remaining administrator account" msgstr "" -#: ../system/integrations/pgp/index.rst:19 -#: ../system/integrations/smime/index.rst:22 -msgid "Encryption" +#: ../system/data-privacy.rst:42 +msgid "Step 1: Find a User / Confirm Deletion" msgstr "" -#: ../system/integrations/pgp/index.rst:16 -#: ../system/integrations/smime/index.rst:20 -msgid "" -"scrambles a message so that it can only be unscrambled by the intended " -"recipient." +#: ../system/data-privacy.rst:44 +msgid "There are three ways to access the user deletion dialog:" msgstr "" -#: ../system/integrations/pgp/index.rst:19 -msgid "" -"In other words, it guarantees message **privacy** and **data security**." +#: ../system/data-privacy.rst:51 +msgid "**from the user's profile**" msgstr "" -#: ../system/integrations/pgp/index.rst:25 -msgid "Screenshot of ticket creation with encrypt and sign buttons" +#: ../system/data-privacy.rst:0 +msgid "Accessing the user deletion dialog in a user profile" msgstr "" -#: ../system/integrations/pgp/index.rst:25 -msgid "" -"Once PGP has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " -"appear in the ticket composer." +#: ../system/data-privacy.rst:51 +msgid "Click **Action > Delete**." msgstr "" -#: ../system/integrations/pgp/index.rst:28 -msgid "**Sign button not visible?**" +#: ../system/data-privacy.rst:58 +msgid "**in the “Manage > Users” Admin Panel**" msgstr "" -#: ../system/integrations/pgp/index.rst:30 -msgid "" -"Please note that the signing of emails is based on the outgoing email " -"account. That means you have to choose a group with a sender email account, " -"which has a private key assigned." +#: ../system/data-privacy.rst:0 +msgid "Accessing the user deletion dialog under “Users” in the Admin Panel" msgstr "" -#: ../system/integrations/pgp/index.rst:35 -msgid "Handling of Keys" +#: ../system/data-privacy.rst:58 +msgid "Use the **⋮ Actions** menu for the target user." msgstr "" -#: ../system/integrations/pgp/index.rst:36 +#: ../system/data-privacy.rst:66 ../system/data-privacy.rst:104 +msgid "**in the “System > Data Privacy” Admin Panel**" +msgstr "" + +#: ../system/data-privacy.rst:0 msgid "" -"To use the PGP function, you have to enable the integration (PGP) by " -"switching the toggle to *enabled*." +"Accessing the user deletion dialog under “Data Privacy” in the Admin Panel" msgstr "" -#: ../system/integrations/pgp/index.rst:39 +#: ../system/data-privacy.rst:65 msgid "" -"You can add keys by clicking the *add key* button. The keys can be imported " -"from a file or you can paste the content of the key in the text box." +"Use the **New Deletion Task** button. Search for users by name or email " +"address." msgstr "" -#: ../system/integrations/pgp/index.rst:42 -msgid "**Which keys do I have to import?**" +#: ../system/data-privacy.rst:79 +msgid "**Delete organizations**" msgstr "" -#: ../system/integrations/pgp/index.rst:44 +#: ../system/data-privacy.rst:69 msgid "" -"For **signing** *outgoing* emails, you have to import the private key of " -"your Zammad email account." +"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:" msgstr "" -#: ../system/integrations/pgp/index.rst:47 -msgid "" -"For **encrypting** *outgoing* emails, you have to import the public key of " -"the customer's email account." +#: ../system/data-privacy.rst:0 +msgid "Deleting an organization via the user deletion dialog" msgstr "" -#: ../system/integrations/pgp/index.rst:50 +#: ../system/data-privacy.rst:78 msgid "" -"For **verifying the signature** of signed *incoming* emails, you have to " -"import the public key of the customer." +"If this option does not appear, make sure there are no pending deletion " +"tasks for other customers from this organization." msgstr "" -#: ../system/integrations/pgp/index.rst:53 -msgid "" -"For **decrypting** of encrypted *incoming* emails, you have to import the " -"private key of your Zammad email account." +#: ../system/data-privacy.rst:82 +msgid "Step 2: Monitor Deletion Job Status" msgstr "" -#: ../system/integrations/pgp/index.rst:57 -msgid "Import Keys From a File" +#: ../system/data-privacy.rst:84 +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:" msgstr "" -#: ../system/integrations/pgp/index.rst:58 -msgid "You can import keys from a file in the section **Upload key**:" +#: ../system/data-privacy.rst:98 +msgid "**in the Activity Stream**" msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of adding a key via file" +#: ../system/data-privacy.rst:0 +msgid "Activity Stream showing data privacy tasks" msgstr "" -#: ../system/integrations/pgp/index.rst:64 +#: ../system/data-privacy.rst:94 msgid "" -"**Supported file formats:** ASCII-armor as well as binary GPG format " -"(basically any GPG supported key format) is supported here." -msgstr "" - -#: ../system/integrations/pgp/index.rst:68 -msgid "Import Keys by Pasting the Content" +"For each deleted user, the Activity Stream will be updated twice—once when " +"the task is created, and once when it's complete." msgstr "" -#: ../system/integrations/pgp/index.rst:69 -msgid "You can also paste the key's content in the section **paste key**:" +#: ../system/data-privacy.rst:97 +msgid "" +"These notifications are only visible to users with ``admin.data_privacy`` " +"permissions." msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Screenshot of adding a key via pasting" +#: ../system/data-privacy.rst:0 +msgid "" +"The task list within Data Privacy shows removals being in progress and " +"completed." msgstr "" -#: ../system/integrations/pgp/index.rst:75 -msgid "" -"**Supported format:** Please note that only ASCII-armor is supported here." +#: ../system/data-privacy.rst:107 +msgid "Frequently Asked Questions" msgstr "" -#: ../system/integrations/pgp/index.rst:78 -msgid "Deleting Keys" +#: ../system/data-privacy.rst:121 +msgid "What happens if I receive an email from a deleted customer?" msgstr "" -#: ../system/integrations/pgp/index.rst:79 +#: ../system/data-privacy.rst:110 msgid "" -"If you want to delete a specific key, you can do it by clicking on the menu " -"in the *actions* column and select **delete**:" +"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/integrations/pgp/index.rst:None -msgid "Screenshot of deleting a key" +#: ../system/data-privacy.rst:115 +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**." msgstr "" -#: ../system/integrations/pgp/index.rst:88 -msgid "Downloading Keys" +#: ../system/data-privacy.rst:130 +msgid "What about user information stored in internal notes or other messages?" msgstr "" -#: ../system/integrations/pgp/index.rst:89 +#: ../system/data-privacy.rst:124 msgid "" -"If you want to download your keys, you can do this as well via corresponding " -"action buttons. Depending on the key, you can choose wether you want to " -"download the private or the public key." -msgstr "" - -#: ../system/integrations/pgp/index.rst:95 -#: ../system/integrations/smime/manage-certificates.rst:76 -msgid "Default Behavior" +"The deletion process removes **user accounts and associated tickets only**." msgstr "" -#: ../system/integrations/pgp/index.rst:96 +#: ../system/data-privacy.rst:126 msgid "" -"Here you can adjust on per group basis, if *sign* and *encryption* is on or " -"off by default. Please be aware, that agents can always override the setting " -"for each individual article." +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:None -msgid "Adjusting default behavior on per group basis" +#: ../system/data-privacy.rst:137 +msgid "I deleted an user and can still see a message they sent!" msgstr "" -#: ../system/integrations/pgp/index.rst:107 +#: ../system/data-privacy.rst:133 msgid "" -"Here you can see the last actions regarding signing and encryption and if " -"they were successful." -msgstr "" - -#: ../system/integrations/pgp/index.rst:117 -msgid "**Sign button is not visible, but keys are imported.**" +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:115 -msgid "Did you choose a group in the ticket?" +#: ../system/data-privacy.rst:141 +msgid "I removed a customer, now my reporting is off!" msgstr "" -#: ../system/integrations/pgp/index.rst:116 +#: ../system/data-privacy.rst:140 msgid "" -"Did you import a private key for the email adress, which is used for " -"outgoing emails in the group?" +"When removing users and their tickets, all references are removed. This also " +"affects e.g. Reporting - these information are lost." msgstr "" -#: ../system/integrations/pgp/index.rst:122 -msgid "**How to obtain keys?**" +#: ../system/data-privacy.rst:145 +msgid "How long does Zammad store created tasks?" msgstr "" -#: ../system/integrations/pgp/index.rst:120 +#: ../system/data-privacy.rst:144 msgid "" -"You can create them yourself! There are some good tutorials on the web on " -"how to create them. Providing keys to Zammad is a prerequisite to use the " -"PGP feature." +"Please see the on-premise data section of the :docs:`data privacy ` chapter." msgstr "" -#: ../system/integrations/pgp/index.rst:127 -msgid "**It says a passphrase is needed, but I haven't got one.**" +#: ../system/data-privacy.rst:150 +msgid "What about re-assigned tickets? I want to delete them, too." msgstr "" -#: ../system/integrations/pgp/index.rst:125 +#: ../system/data-privacy.rst:148 msgid "" -"If the key is secured with a passphrase, you have to provide it for the " -"import in Zammad. It is possible that keys may have an empty passphrase. " -"However, this is *not* recommended." +"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." msgstr "" -#: ../system/integrations/pgp/index.rst:132 -msgid "**How do my customers get my new key?**" +#: ../system/data-privacy.rst:154 +msgid "Why are there so many deletion task entries, I didn't create them!" msgstr "" -#: ../system/integrations/pgp/index.rst:130 +#: ../system/data-privacy.rst:153 msgid "" -"You have to provide your **public** key in advance. Your customer also has " -"to configure PGP in their email workflow and import your public key. The " -"other way round, you have to get the public key of your customer and have to " -"import it to Zammad." +"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." msgstr "" -#: ../system/integrations/slack.rst:2 -msgid "Slack" +#: ../system/integrations/checkmk/admin-panel-reference.rst:2 +msgid "Admin Panel Reference" msgstr "" -#: ../system/integrations/slack.rst:4 -msgid "**⚠️ Deprecation warning ⚠️**" +#: ../system/integrations/checkmk/admin-panel-reference.rst:None +msgid "Screenshot of Checkmk settings overview" msgstr "" -#: ../system/integrations/slack.rst:6 +#: ../system/integrations/checkmk/admin-panel-reference.rst:12 msgid "" -"Zammad 7 will no longer support this dedicated Slack integration. It is " -"recommended to switch to :doc:`pre-defined webhooks ` instead. Existing Slack integrations should " -"be migrated manually before this feature is dropped." +"Which :doc:`group ` should Checkmk tickets be assigned " +"to as a default (*i.e.,* when none is specified)?" msgstr "" -#: ../system/integrations/slack.rst:14 -msgid "" -"In order to use this feature, please add a new Slack app to your Workspace. " -"The App you need is called ``Incoming WebHooks`` ." +#: ../system/integrations/checkmk/admin-panel-reference.rst:15 +msgid "(Applies to :ref:`API alerts ` only.)" msgstr "" -#: ../system/integrations/slack.rst:18 -msgid "Why Do I Need This Feature?" +#: ../system/integrations/checkmk/admin-panel-reference.rst:21 +msgid "Auto close" msgstr "" -#: ../system/integrations/slack.rst:20 +#: ../system/integrations/checkmk/admin-panel-reference.rst:18 msgid "" -"If you're already using Slack for your team communication, you'll love this " -"feature! Our Slack integration can push ticket notifications about the last " -"ticket article based on the following events:" +"Should Zammad automatically close tickets if a service has recovered on its " +"own?" msgstr "" -#: ../system/integrations/slack.rst:24 -msgid "on Ticket creation" +#: ../system/integrations/checkmk/admin-panel-reference.rst:21 +msgid "(Agents will receive notifications for such closures as appropriate.)" msgstr "" -#: ../system/integrations/slack.rst:25 -msgid "on Ticket updates" +#: ../system/integrations/checkmk/admin-panel-reference.rst:30 +msgid "Auto-close state" msgstr "" -#: ../system/integrations/slack.rst:26 -msgid "on reached reminders" +#: ../system/integrations/checkmk/admin-panel-reference.rst:24 +msgid "What ticket state should be applied when “auto-closing” a ticket?" msgstr "" -#: ../system/integrations/slack.rst:27 -msgid "a Ticket has escalated" +#: ../system/integrations/checkmk/admin-panel-reference.rst:26 +msgid "" +"You can choose from the seven built-in ticket states. If these states aren't " +"enough for you, you can :ref:`define a new ticket state ` for this purpose as well. This can be useful for tracking " +"tickets with :doc:`reports `, for example." msgstr "" -#: ../system/integrations/slack.rst:28 -msgid "a Ticket is going to escalate" +#: ../system/integrations/checkmk/admin-panel-reference.rst:35 +#: ../system/integrations/cti/includes/recent-logs.include.rst:2 +#: ../system/integrations/ldap/index.rst:74 +#: ../system/integrations/pgp/index.rst:106 +msgid "Recent Logs" msgstr "" -#: ../system/integrations/slack.rst:30 -msgid "" -"Zammad will provide the Ticket title, a direct link to the Ticket, the event " -"type (creation, updated, escalation), the customer, time and the last " -"article that has triggered the notification." +#: ../system/integrations/checkmk/admin-panel-reference.rst:None +msgid "Screenshot of Checkmk \"Recent Logs\" section" msgstr "" -#: ../system/integrations/slack.rst:34 +#: ../system/integrations/checkmk/admin-panel-reference.rst:41 msgid "" -"This will give you further options, as you can see e.g. escalating tickets " -"that are assigned to an agent that's e.g. absent. You can interact faster, " -"as you might see problems earlier (or even before the problem gets one)." +"If you're having trouble getting Zammad and Checkmk to play nicely together, " +"this section can help you troubleshoot." msgstr "" -#: ../system/integrations/slack.rst:38 +#: ../system/integrations/checkmk/admin-panel-reference.rst:44 msgid "" -"If needed and wanted, you can even discuss directly about the topic before " -"sending an answer to the customer. Another possible use case would be a " -"agent monitoring new agents and their answers to tickets." +"It contains a record of the fifty most recent transactions that Zammad knows " +"about, including each one's request/response details and return status." msgstr "" -#: ../system/integrations/slack.rst:44 -#, fuzzy -msgid "Configure the Integration" -msgstr "聊天小部件的配置" - -#: ../system/integrations/slack.rst:46 -msgid "" -"First of all, please go to your slack workspace - go to administration => " -"Manage Apps. If you don't have an app yet, you can simply add a new one - " -"just search for ``Incoming WebHooks`` and customize the app to your needs." +#: ../system/integrations/checkmk/api-reference.rst:2 +msgid "API Reference" msgstr "" -#: ../system/integrations/slack.rst:50 +#: ../system/integrations/checkmk/api-reference.rst:4 msgid "" -"Choose (or create) the channel Zammad should post it's information to and " -"press on \"Add Incoming WebHooks integration\". If you're ready, copy the " -"provided WebHook URL and go to your Zammad installation." +"For most users, :ref:`the sample scripts from the Setup Guide ` will do the job just fine. But if you want more fine-grained control" +"—for instance, to create high- and low-priority tickets for different types " +"of system events—then you'll have to customize the data those scripts send " +"to Zammad." msgstr "" -#: ../system/integrations/slack.rst:56 +#: ../system/integrations/checkmk/api-reference.rst:15 msgid "" -"You need administrative rights on the Slack Workspace. The link to the app " -"directory is normally ``https://[workspace-name].slack.com/apps`` ." +"This custom script will automatically set all tickets it creates to **high " +"priority** and **assign them to charlie@chrispresso.com**." msgstr "" -#: ../system/integrations/slack.rst:63 -msgid "" -"To configure the slack integration, log in to Zammad and go to Integrations " -"(System) => Slack in the admin panel." +#: ../system/integrations/checkmk/api-reference.rst:32 +msgid "How Does it Work?" msgstr "" -#: ../system/integrations/slack.rst:66 +#: ../system/integrations/checkmk/api-reference.rst:34 msgid "" -"Here you can choose on what evens Zammad should post information about a " -"ticket to your Slack channel. Next you need to device what groups shall be " -"affected by this, as anybody with access to that specific Slack channel can " -"read at least parts of the ticket this might be a privacy issue, if you " -"select the wrong groups. The username is simply the name that Zammad uses as " -"display name inside the Slack chat. The channel defines the Slack channel " -"the information is being posted in. As last option, you can set a custom " -"icon for posting to slack." +"There are two kinds of data you can pass to the API, both in the form of key-" +"value pairs:" msgstr "" -#: ../system/integrations/slack.rst:74 -msgid "" -"When you're ready, just hit \"Submit\" and enable the integration. Zammad " -"will now post new ticket information based on the trigger you chose. Below " -"the options you have the recent log that shows the latest requests to Slack " -"for debugging if needed." +#: ../system/integrations/checkmk/api-reference.rst:44 +msgid "Checkmk parameters" msgstr "" -#: ../system/integrations/slack.rst:81 +#: ../system/integrations/checkmk/api-reference.rst:38 msgid "" -"If you leave the Icon URL empty, Zammad will use the Zammad logo instead. " -"The icon should be a square PNG file." +"are required, and make up the **contents** of the resulting tickets/" +"articles. They also determine whether an event creates a new ticket or " +"updates/closes an existing one." msgstr "" -#: ../system/integrations/slack.rst:90 +#: ../system/integrations/checkmk/api-reference.rst:42 msgid "" -"The following figure shows how it will look if you choose to receive updates " -"on created and updated tickets. On every post Zammad sends to the Slack " -"channel, you can create new threads to discuss about the new article." +"These are the only values used in the sample scripts. **Use them as-is**; " +"technically, they can be customized, but it's hard to imagine a good reason " +"for it." msgstr "" -#: ../system/integrations/slack.rst:96 -msgid "" -"If you just want to keep track of soon escalating or already escalated " -"tickets, it will look the the following figure. Zammad changes the color in " -"front of the post so you can easily see the state of the ticket." +#: ../system/integrations/checkmk/api-reference.rst:52 +msgid "Ticket attributes" msgstr "" -#: ../system/integrations/slack.rst:102 +#: ../system/integrations/checkmk/api-reference.rst:47 msgid "" -"If you change the state, Zammad will also put information on what state the " -"ticket gets and (if pending state) the date until it pends. You'll also " -"recognize the color codes in front of posts on slack, as they are exact the " -"same the ticket state colors you'll see in Zammad!" -msgstr "" - -#: ../system/integrations/smime/index.rst:2 -msgid "S/MIME" +"are optional, and can be used to **adjust settings** on newly created " +"tickets (*e.g.,* set the owner, group, priority, or state)." msgstr "" -#: ../system/integrations/smime/index.rst:11 +#: ../system/integrations/checkmk/api-reference.rst:50 msgid "" -"S/MIME is the most widely-supported method for secure email communication. " -"With S/MIME, you can exchange **signed** and **encrypted** messages with " -"others." +"If you want to customize your Checkmk alert script, do it with these. Simply " +"add an extra “form” option for each one (``-F \"key=value\"``) to your " +"script's ``curl`` command line, as in the example above." msgstr "" -#: ../system/integrations/smime/index.rst:15 -msgid "" -"is proof that a message hasn't been tampered with or sent by an impersonator." +#: ../system/integrations/checkmk/api-reference.rst:54 +msgid "💡 **It's just an API endpoint!**" msgstr "" -#: ../system/integrations/smime/index.rst:17 +#: ../system/integrations/checkmk/api-reference.rst:56 msgid "" -"In other words, it guarantees a message's **integrity** and **authenticity**." +"When using Checkmk integration, messages need to be formatted in a certain " +"way, but that *doesn't mean the messages actually have to come from Checkmk*." msgstr "" -#: ../system/integrations/smime/index.rst:22 -msgid "In other words, it guarantees **privacy** and **data security**." +#: ../system/integrations/checkmk/api-reference.rst:59 +msgid "" +"If you use another monitoring tool that's not officially supported by " +"Zammad, there's probably a way to make it work with your Checkmk callback " +"URL." msgstr "" -#: ../system/integrations/smime/index.rst:28 -msgid "Screencast demo of S/MIME features for both new tickets and replies" +#: ../system/integrations/checkmk/api-reference.rst:63 +msgid "Checkmk Parameters" msgstr "" -#: ../system/integrations/smime/index.rst:28 +#: ../system/integrations/checkmk/api-reference.rst:65 msgid "" -"Once S/MIME has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " -"appear in the ticket composer." +"When a notification is received, Zammad creates a new article containing the " +"details of the event that triggered it:" msgstr "" -#: ../system/integrations/smime/index.rst:32 -msgid ":doc:`🔪 Prerequisites `" +#: ../system/integrations/checkmk/api-reference.rst:None +msgid "Checkmk article body" msgstr "" -#: ../system/integrations/smime/index.rst:31 +#: ../system/integrations/checkmk/api-reference.rst:72 msgid "" -"New to S/MIME? This section helps you to find certificate providers and " -"points out Limitations." +"These details come from the fields listed below, which correspond to " +"parameters provided by Checkmk (``$NOTIFY_*``)." msgstr "" -#: ../system/integrations/smime/index.rst:35 -msgid ":doc:`📝 Manage Certificates `" +#: ../system/integrations/checkmk/api-reference.rst:75 +msgid "**Required fields are marked with an asterisk (\\*).**" msgstr "" -#: ../system/integrations/smime/index.rst:35 -msgid "Add and download certificates; configure group default behaviors." +#: ../system/integrations/checkmk/api-reference.rst:79 +msgid "event_id\\*" msgstr "" -#: ../system/integrations/smime/index.rst:38 -msgid ":doc:`😦 Troubleshooting `" +#: ../system/integrations/checkmk/api-reference.rst:78 +msgid "" +"A unique ID for the system event. (``$NOTIFY_SERVICEPROBLEMID`` / " +"``$NOTIFY_HOSTPROBLEMID``)" msgstr "" -#: ../system/integrations/smime/index.rst:38 -msgid "Took a wrong turn? About recent logs and common issues." +#: ../system/integrations/checkmk/api-reference.rst:86 +msgid "host\\*" msgstr "" -#: ../system/integrations/smime/index.rst:43 +#: ../system/integrations/checkmk/api-reference.rst:82 msgid "" -"For more details on how S/MIME integration works on the agent side, see the :" -"user-docs:`user docs `." -msgstr "" - -#: ../system/integrations/smime/manage-certificates.rst:2 -msgid "Manage Certificates" +"The hostname of the system that the event originated from. " +"(``$NOTIFY_HOSTNAME``)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:4 +#: ../system/integrations/checkmk/api-reference.rst:85 msgid "" -"S/MIME is **disabled by default**. Enable it to start adding certificates." +"Used to determine if a new event belongs to an existing ticket. Also used in " +"the subject line of the resulting article (“ is ”)." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:10 -msgid "Dialogue to add new certificates or private keys" +#: ../system/integrations/checkmk/api-reference.rst:96 +msgid "service" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:10 +#: ../system/integrations/checkmk/api-reference.rst:89 msgid "" -"Manage certificates in the Admin Panel under **System > Integrations > S/" -"MIME**. Certificates may be pasted in as plain text or uploaded from a file." +"The name of the service that the event originated from. " +"(``$NOTIFY_SERVICEDESC``)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:14 -msgid "Add Certificate Data" +#: ../system/integrations/checkmk/api-reference.rst:92 +msgid "Used to determine if a new event belongs to an existing ticket." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:36 -msgid "Add Certificate" +#: ../system/integrations/checkmk/api-reference.rst:94 +#: ../system/integrations/checkmk/api-reference.rst:110 +msgid "Displayed as ``-`` when omitted." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:17 -msgid "" -"Import public-key certificates for both your own organization and your " -"contacts." +#: ../system/integrations/checkmk/api-reference.rst:104 +msgid "state\\*" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:19 +#: ../system/integrations/checkmk/api-reference.rst:99 msgid "" -"You can also add a bunch of certificates in one go by providing a single " -"file with all relevant certificates." -msgstr "" - -#: ../system/integrations/smime/manage-certificates.rst:22 -msgid "🕵️ **ALWAYS verify certificates in-person or over the phone!**" +"The current state of the service or host in question. " +"(``$NOTIFY_SERVICESTATE`` / ``$NOTIFY_HOSTSTATE``)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:24 +#: ../system/integrations/checkmk/api-reference.rst:102 msgid "" -"The whole point of signatures is to alert you when someone is trying to " -"pretend to be someone they're not. Never accept a certificate from someone " -"online without verifying it first." +"Used to detect when a ticket should be auto-closed (*i.e.,* on ``OK``/" +"``UP``). Also used in the subject line of the resulting article (“ is " +"”)." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:28 -msgid "📇 **What about trusted certificate authorities?**" +#: ../system/integrations/checkmk/api-reference.rst:110 +msgid "text" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:30 +#: ../system/integrations/checkmk/api-reference.rst:107 msgid "" -"In some cases (e.g. when dealing with large enterprises), you may be given a " -"certificate for an entire CA, rather than a single contact. Add it here to " -"trust *all* certificates issued by that CA." +"The output of the process that triggered the event. " +"(``$NOTIFY_SERVICEOUTPUT`` / ``$NOTIFY_HOSTOUTPUT``)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:35 +#: ../system/integrations/checkmk/api-reference.rst:121 msgid "" -"Commercial CAs can usually be verified online. Zammad does not include a " -"list of built-in, trusted CAs." +"The Object Manager attribute panel displays built-in and custom\n" +"attribute names." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:57 -msgid "Add Private Key" +#: ../system/integrations/checkmk/api-reference.rst:121 +msgid "Find a complete list of ticket attributes in the Object Manager." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:39 +#: ../system/integrations/checkmk/api-reference.rst:123 msgid "" -"Once you've added a public-key certificate, you can import its matching " -"private key." +"Ticket attributes are entirely optional, and can be used to customize the " +"tickets that Checkmk creates. (Note that these attributes will be ignored if " +"a new event belongs to an existing ticket.)" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:42 +#: ../system/integrations/checkmk/api-reference.rst:128 msgid "" -"Private keys are for **your own organization only**; never ask your contacts " -"for their private keys." +"Why would you want to do this? Maybe you have only one IT guy, and all " +"system monitoring issues should be automatically assigned to him. Or, maybe " +"you're creating multiple notification rules so that database outages take " +"higher priority than disk space warnings." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:0 -msgid "" -"S/MIME integration showing configured certificates and possible issues with " -"Logging" +#: ../system/integrations/checkmk/api-reference.rst:135 +msgid "In most cases, you'll probably want to set one of the following:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:50 -msgid "" -"A note is displayed on certificates with a matching private key (see line 2)." -msgstr "" +#: ../system/integrations/checkmk/api-reference.rst:137 +msgid "group" +msgstr "组" -#: ../system/integrations/smime/manage-certificates.rst:52 -msgid "📤 **Certificates and private keys must be uploaded separately.**" -msgstr "" +#: ../system/integrations/checkmk/api-reference.rst:139 +msgid "state" +msgstr "状态" -#: ../system/integrations/smime/manage-certificates.rst:54 +#: ../system/integrations/checkmk/api-reference.rst:140 +msgid "priority" +msgstr "优先级" + +#: ../system/integrations/checkmk/api-reference.rst:142 msgid "" -"If your certificate and private key are bundled together in the same file or " -"PEM block, import it twice (once using each button)." +"but in practice, you can set almost any attribute, including :doc:`custom " +"ones you created through the Object Manager `." msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:57 -msgid "Please note that bulk imports of private keys are not possible." +#: ../system/integrations/checkmk/api-reference.rst:145 +msgid "Please note that the following attributes are **not customizable**:" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:60 -msgid "Download Certificate Data" +#: ../system/integrations/checkmk/api-reference.rst:147 +msgid "title" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:62 -msgid "" -"You can download the earlier provided certificates and private keys at any " -"time from your Zammad instance." +#: ../system/integrations/checkmk/api-reference.rst:148 +msgid "id" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:65 -msgid "" -"Please note that passphrase-protected private keys stay protected and when " -"you download them, you have to know the passphrase to use them after " -"downloading." +#: ../system/integrations/checkmk/api-reference.rst:149 +msgid "ticket number" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:73 -msgid "Dialogue to download certificates or private keys" +#: ../system/integrations/checkmk/api-reference.rst:151 +msgid "created_by_id" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:73 -msgid "Download stored certificates and their keys" +#: ../system/integrations/checkmk/api-reference.rst:152 +msgid "updated_by_id" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:78 -msgid "" -"The ticket composer will set all outgoing messages to **signed and " -"encrypted** by default (assuming the required certificates exist)." +#: ../system/integrations/checkmk/api-reference.rst:155 +msgid "Which Values Can Be Set?" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:82 -msgid "These defaults can be modified on a per-group basis:" +#: ../system/integrations/checkmk/api-reference.rst:157 +msgid "😵 **Invalid values → unpredictable behavior**" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:None -msgid "Zammad allowing to choose the default behavior on per group basis" +#: ../system/integrations/checkmk/api-reference.rst:159 +msgid "" +"If you provide a value that Zammad doesn't understand (*e.g.,* ``-F " +"\"priority=high\"``), it's not always clear what will happen. In some cases, " +"a ticket will be created with the default values instead - but in others, it " +"may not be created at all!" msgstr "" -#: ../system/integrations/smime/manage-certificates.rst:89 -msgid "" -"Of course, agents can always manually change these settings on each email " -"they send out." +#: ../system/integrations/checkmk/api-reference.rst:164 +msgid "So what values does Zammad understand, then? Well, it depends..." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:4 -msgid "A certificate *and* private key for your own organization" +#: ../system/integrations/checkmk/api-reference.rst:168 +msgid "Use an email address or username:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:6 -msgid "" -"(Use this to ✒️ **sign outgoing messages** and 🔓 **decrypt incoming " -"messages**.)" +#: ../system/integrations/checkmk/api-reference.rst:190 +msgid "group & priority" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:9 -msgid "" -"Certificates belonging your contacts, or their issuing certificate authority " -"(CA)" +#: ../system/integrations/checkmk/api-reference.rst:175 +msgid "Refer to the dropdown menus in the ticket pane:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:11 -msgid "" -"(Use these to ✅ **verify incoming message signatures** and 🔒 **encrypt " -"outgoing messages**.)" +#: ../system/integrations/checkmk/api-reference.rst:0 +msgid "See possible values for certain attributes in the ticket pane." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:14 -msgid "🙋 **I'm new to S/MIME. Where can I get a certificate?**" +#: ../system/integrations/checkmk/api-reference.rst:187 +msgid "🙅 **Ticket state CANNOT be set this way!**" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:16 +#: ../system/integrations/checkmk/api-reference.rst:189 msgid "" -"The easiest way to get certificates is to buy an annual subscription through " -"a commercial CA, such as:" +"Why? Because ``-F \"state=...\"`` is already used :ref:`as a Checkmk " +"parameter `." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:19 -msgid "" -"`Sectigo (formerly Comodo) `_" +#: ../system/integrations/checkmk/api-reference.rst:222 +msgid "Everything Else" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:20 -msgid "`Secorio `_" +#: ../system/integrations/checkmk/api-reference.rst:193 +msgid "" +"To set any other attributes, it helps to know your way around the :docs:" +"`rails console `. Valid values are those that you can " +"set with a string:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:21 -msgid "`GlobalSign `_" +#: ../system/integrations/checkmk/api-reference.rst:218 +msgid "These values can then be passed directly to the API:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:23 -msgid "(Zammad is not affiliated with these CAs in any way.)" +#: ../system/integrations/checkmk/index.rst:16 +msgid "How does it work?" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:25 -msgid "" -"You can also generate your own self-signed certificates, but the process is " -"complicated and usually 🙅 **involves extra work for your contacts**." +#: ../system/integrations/checkmk/index.rst:2 +msgid "Checkmk" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:29 +#: ../system/integrations/checkmk/index.rst:4 msgid "" -"Bear in mind that 🤝 **S/MIME only works if the other party is using it, too." -"**" +"`Checkmk `_ is a powerful IT monitoring tool that can " +"send real-time status alerts to Zammad via email or REST API. Set these " +"alerts up in Checkmk, and Zammad will automatically create, update, and " +"close tickets based on the health of your system:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:32 -msgid "Certificate and Private Key Checks on Upload" +#: ../system/integrations/checkmk/index.rst:14 +msgid "Screenshot of ticket created by Checkmk notifications" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:34 -msgid "" -"The certificate and public key validation is based on the ``X509v3`` " -"extensions." +#: ../system/integrations/checkmk/index.rst:14 +msgid "Multiple alerts, same ticket." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:49 -msgid "Uploading a *client certificate*?" +#: ../system/integrations/checkmk/setup-guide.rst:2 +msgid "Setup Guide" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:41 -msgid "The following attributes are required then:" +#: ../system/integrations/checkmk/setup-guide.rst:4 +msgid "" +"Whenever the Checkmk integration is enabled, Zammad listens for messages on " +"its API and over email. As long as those messages follow the required " +"format, Zammad will create new tickets (or find and update existing ones) " +"based on the message contents." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:39 -msgid "Subject Alternative Name (at least one email address has to be present)" +#: ../system/integrations/checkmk/setup-guide.rst:10 +msgid "" +"That means that “setting up Checkmk integration” is simply a matter of " +"**adding configuration to your Checkmk site**: telling it when to send these " +"messages and what to say. To do that, you'll need to create a new " +"**notification rule** (see `Checkmk's official docs `_ for help with that)." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:40 -msgid "Key Usage (``Digital Signature`` and/or ``Key Encipherment``)" +#: ../system/integrations/checkmk/setup-guide.rst:17 +msgid "" +"As part of this new rule, you'll have to choose a **notification method** " +"(*i.e.,* a script to execute whenever the rule is triggered). This script " +"will be written by you (samples below), and contain the logic for sending " +"API/email messages to Zammad:" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:41 -msgid "Public key algorithm (either ``RSA`` or ``EC``)" +#: ../system/integrations/checkmk/setup-guide.rst:26 +msgid "Checkmk \"New Rule\" dialog" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:43 +#: ../system/integrations/checkmk/setup-guide.rst:26 msgid "" -"The Extended Key Usage attribute is optional. If the certificate provides " -"the named attribute, than it must contain the value ``E-mail Protection``." +"Find your custom scripts in the Checkmk WATO under **Notifications > New " +"Rule > Notification Method**." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:46 +#: ../system/integrations/checkmk/setup-guide.rst:29 msgid "" -"Please note that any usable email adress has to be prefixed with ``email:`` " -"or ``rfc822:``." -msgstr "" - -#: ../system/integrations/smime/prerequisites.rst:49 -msgid "The named public key algorithms are mandatory for private keys as well." +"Once you're done setting up your new rule, you're all set! New tickets " +"should start coming in and auto-updating any time your rule is triggered." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:54 -msgid "Uploading a *CA certificate*?" +#: ../system/integrations/checkmk/setup-guide.rst:33 +msgid "" +"(If you need help troubleshooting, be sure to check the :ref:`checkmk-recent-" +"logs`.)" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:52 -msgid "" -"In the case of an uploaded CA certificate, providing the value ``CA:TRUE`` " -"in the attribute *Basic Contstraints*, the previously mentioned attributes " -"are not verified." +#: ../system/integrations/checkmk/setup-guide.rst:38 +msgid "API Alerts" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:56 +#: ../system/integrations/checkmk/setup-guide.rst:40 msgid "" -"In general, the usage of any expired (``Not After``) or not yet valid (``Not " -"Before``) certificate is denied for outgoing emails." +"To add these scripts in the Checkmk WATO, copy them into your Checkmk " +"installation directory and make them executable. (Be sure to replace the " +"``zammad.example.com`` callback URL with the one found in your admin panel.)" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:59 -msgid "Example certificate:" +#: ../system/integrations/checkmk/setup-guide.rst:60 +msgid "Service notification" msgstr "" -#: ../system/integrations/smime/prerequisites.rst:85 +#: ../system/integrations/checkmk/setup-guide.rst:46 msgid "" -"Please note that Zammad will distrust senders by default. This means that " -"you're always required to provide certificate data, no matter if for signing " -"or encrypting." +"For updates on the status of the software running on your server (*e.g.,* " +"postgres)." msgstr "" -#: ../system/integrations/smime/prerequisites.rst:89 -msgid "This is by design and can't be adjusted." +#: ../system/integrations/checkmk/setup-guide.rst:75 +msgid "Host notification" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:4 -msgid "" -"All of the system's latest S/MIME activity is displayed in the **Recent " -"Logs** section." +#: ../system/integrations/checkmk/setup-guide.rst:63 +msgid "For updates on the status of the server itself." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:11 -msgid "Sample entries of in- and outgoing S/MIME related emails." +#: ../system/integrations/checkmk/setup-guide.rst:77 +msgid "🤔 **What's with all the env vars?**" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:11 +#: ../system/integrations/checkmk/setup-guide.rst:79 msgid "" -"Logs report the status and details of all mail, both incoming and outgoing, " -"that used signing/verification or encryption/decryption." +"Whenever Checkmk runs these scripts, it needs to provide some information " +"about the event that triggered the notification. This information is passed " +"in the form of these ``$NOTIFY_*`` environment variables." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:14 +#: ../system/integrations/checkmk/setup-guide.rst:85 msgid "" -"This log does **not** include email sent by :doc:`triggers ` or the :doc:`scheduler `. For those, check your " -"``production.log``." +"You can specify additional parameters to pass to the script when you're " +"setting up your notification rule, but the ones you see here are all " +"provided by default." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:20 -msgid "Common Issues" -msgstr "" - -#: ../system/integrations/smime/troubleshooting.rst:30 -msgid "I received a signed/encrypted email before I set up S/MIME integration" +#: ../system/integrations/checkmk/setup-guide.rst:90 +msgid "Email Alerts" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:23 +#: ../system/integrations/checkmk/setup-guide.rst:94 msgid "" -"No problem. Once S/MIME has been enabled and the appropriate certificates " -"have been added, agents will be prompted to retry verification/decryption on " -"matching emails." +"🐞 **There are known bugs** in Zammad's processing of email from Checkmk. " +"This section will be completed once they have been resolved. (Learn more at " +"GitHub issues `#2377 `_ & " +"`#2180 `_.)" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:0 -msgid "Screenshot of user prompt to retry decryption" +#: ../system/integrations/checkmk/setup-guide.rst:100 +msgid "In the meantime, we encourage you to set up API alerts instead." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:38 -msgid "The 🔒 **Encrypt** button is disabled" +#: ../system/integrations/clearbit.rst:2 +msgid "Clearbit" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:33 -msgid "Have you added the recipient's certificate?" +#: ../system/integrations/clearbit.rst:4 +msgid "" +"With our Clearbit integration, you can easily enrich the information " +"provided by Zammad. If the customers or agents email address is known to " +"Clearbit, it will share all information it has regarding the user with " +"Zammad. Those information can include the following:" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:34 -msgid "Are you sure the recipient's certificate is valid?" +#: ../system/integrations/clearbit.rst:9 +msgid "Avatar" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:35 -msgid "Have you checked your ``production.log`` for more details?" +#: ../system/integrations/clearbit.rst:10 +msgid "Address information" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:37 -msgid "" -"If encryption doesn't work in the composer, it won't work in :doc:`triggers " -"` or the :doc:`scheduler ` either!" +#: ../system/integrations/clearbit.rst:11 +msgid "Website information" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:42 -msgid "The ✅ **Sign** button is disabled" +#: ../system/integrations/clearbit.rst:12 +msgid "A BIO (as Note by default)" msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:41 +#: ../system/integrations/clearbit.rst:14 msgid "" -"Have you added **both the certificate and private key** for your " -"organization?" +"If needed, you can add further custom objects and add mappings to them, so " +"the Clearbit information can be filled within the database. In general you " +"can get any information from Clearbit, as long as you have a mapping to an " +"Zammad object." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:42 +#: ../system/integrations/clearbit.rst:21 msgid "" -"Does the email address on the certificate match the email address of the " -"agent/group composing the email?" +"Clearbit does have a mapping of fields like LDAP and Exchange have, but does " +"not \"win\" against Zammad information. This means that if you have e.g. the " +"last name field filled in already and Clearbit has other information on " +"that, it will not be updated." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:45 -msgid "Error: “Fingerprint already taken”" +#: ../system/integrations/clearbit.rst:26 +msgid "" +"However: If let's say the last name has been set by Clearbit and Zammad " +"notices that the last name on the Clearbit source has changed, Zammad will " +"also update this value." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:45 -msgid "Are you sure you haven't added this certificate already?" +#: ../system/integrations/clearbit.rst:33 +msgid "" +"The configuration of Clearbit is really easy and done fast! Just login to " +"your Clearbit-Account, go to \"API\" and copy the secret-API-Key." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:48 -msgid "Error: “❌ invalid byte sequence in UTF-8”" +#: ../system/integrations/clearbit.rst:38 +msgid "" +"Now change to your Zammad instance, go to Integrations (System) -> Clearbit " +"in the admin panel. Paste your API-Key into the API-Key-Field and decide if " +"Zammad should create unknown Organizations automatically, if the user does " +"not have one yet (and Clearbit knows it). The shared option decides if the " +"new organizations Zammad creates with Clearbit should be shared ones." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:48 -msgid "Please ensure to provide PEM formatted certificate and keys." +#: ../system/integrations/clearbit.rst:47 +msgid "" +"If you're unsure what option to choose, better stick with \"no\". You can " +"also learn more about :doc:`/manage/organizations/index`." msgstr "" -#: ../system/integrations/smime/troubleshooting.rst:49 -msgid "Did you check if the provided file is a valid certificate or key?" +#: ../system/integrations/clearbit.rst:52 +msgid "" +"The Mapping option works similar to the mapping within the Exchange and LDAP " +"sync. You can add further mappings for e.g. custom fields if you need more " +"information that Clearbit can provide." msgstr "" -#: ../system/integrations/zabbix.rst:2 -msgid "Zabbix Integration" +#: ../system/integrations/clearbit.rst:58 +msgid "" +"If you want to add more Clearbit fields and want to learn more about " +"available fields on their API, you can take a look at their `API " +"documentation `_." msgstr "" -#: ../system/integrations/zabbix.rst:5 +#: ../system/integrations/clearbit.rst:62 msgid "" -"This guide describes how to integrate your Zabbix 5.4 installation with " -"Zammad using the Zabbix webhook feature. This guide will provide " -"instructions on setting up a media type, a user and an action in Zabbix." +"If you're happy with the above chosen Settings and your mapping, just save " +"the changes and enable Clearbit integration. Zammad will now start polling " +"the Clearbit API as users contact you." msgstr "" -#: ../system/integrations/zabbix.rst:12 -msgid "Zammad with enabled HTTP Token Authentication" +#: ../system/integrations/clearbit.rst:68 +msgid "" +"Zammad does not synchronize with Clearbit on a regular basis, but on demand " +"if needed. This saves API calls." msgstr "" -#: ../system/integrations/zabbix.rst:13 -msgid "Zabbix version 5.4 or higher" +#: ../system/integrations/clearbit.rst:73 +msgid "" +"Below the Settings and Mappings, you'll find our Integration log. You can " +"see what requests Zammad sent to Clearbit and also the APIs Response." msgstr "" -#: ../system/integrations/zabbix.rst:16 -msgid "Setting up a Zammad" +#: ../system/integrations/clearbit.rst:78 +msgid "" +"By the way, you can also view the API log on the Clearbit website - the " +"information seen is basically the same." msgstr "" -#: ../system/integrations/zabbix.rst:18 -msgid "Enable **API Token Access** in Settings > System > API." +#: ../system/integrations/clearbit.rst:84 +msgid "Example When Adding a User" msgstr "" -#: ../system/integrations/zabbix.rst:20 +#: ../system/integrations/clearbit.rst:86 msgid "" -"Create a **new user** for a Zabbix alerter with an **email address** and " -"create a personal user token with **ticket.agent** permissions." +"To show you how fast information is added, we added a small Screencast " +"below. This shows the creation of the User Alex from Clearbit. As we already " +"set the last name of Alex to \"X\", Zammad did not update it. What Zammad " +"did was to add further information it received from Clearbit." msgstr "" -#: ../system/integrations/zabbix.rst:24 -msgid "Zabbix Webhook Configuration" +#: ../system/integrations/cti/generic.rst:2 +msgid "CTI (generic)" msgstr "" -#: ../system/integrations/zabbix.rst:27 -#, fuzzy -msgid "Create a Global Macro" -msgstr "宏" - -#: ../system/integrations/zabbix.rst:29 +#: ../system/integrations/cti/includes/introduction.include.rst:1 msgid "" -"Before setting up the **Webhook**, you need to setup the global macro " -"**{$ZABBIX.URL}**, which must contain the **URL** to the **Zabbix frontend**." +"This integration enables Zammad to provide a caller log to your agents. With " +"this your agents can greet your customers by their name and are supported by " +"Zammad with automatically opening a new ticket dialog or the user profile." msgstr "" -#: ../system/integrations/zabbix.rst:33 +#: ../system/integrations/cti/includes/introduction.include.rst:6 msgid "" -"In the **Administration** > **Media types** section, import the `Template`_." -msgstr "" - -#: ../system/integrations/zabbix.rst:38 -msgid "Open the added **Zammad** media type and set:" +"Click the toggle next to the heading to activate or deactivate this " +"integration." msgstr "" -#: ../system/integrations/zabbix.rst:40 -msgid "**zammad\\_access\\_token** to the your **Personal User Token**" +#: ../system/integrations/cti/includes/introduction.include.rst:9 +msgid "" +"If you want to learn more on how your agents can use this function, please " +"refer the :user-docs:`user documentation `." msgstr "" -#: ../system/integrations/zabbix.rst:41 +#: ../system/integrations/cti/includes/introduction.include.rst:14 msgid "" -"**zammad\\_url** to the **frontend URL** of your **Zammad** installation" +"Automatically opening new ticket dialogues or user profiles requires agent " +"to extension mapping - see more below." msgstr "" -#: ../system/integrations/zabbix.rst:43 -msgid "**zammad\\_customer** to your **Zammad user email**." +#: ../system/integrations/cti/includes/introduction.include.rst:20 +msgid "Please note the following limitations to reduce confusion later on:" msgstr "" -#: ../system/integrations/zabbix.rst:44 -msgid "" -"**zammad\\_enable\\_tags** to **true** or **false** to enable or disable " -"trigger tags. **Important**: if you enable tag support, each tag is set with " -"a separate request." +#: ../system/integrations/cti/includes/introduction.include.rst:22 +msgid "CTI integrations provide caller log functions only." msgstr "" -#: ../system/integrations/zabbix.rst:48 +#: ../system/integrations/cti/includes/introduction.include.rst:23 msgid "" -"If you want to prioritize issues according to **severity** values in Zabbix, " -"you can define mapping parameters:" +"This integration does not provide any VoIP functionalities; you can't make " +"phone calls from within Zammad." msgstr "" -#: ../system/integrations/zabbix.rst:51 -msgid "**severity\\_**: Zammad priority ID" +#: ../system/integrations/cti/includes/introduction.include.rst:25 +msgid "" +"If your browser supports ``tel``-URLs, you can click on phone numbers for " +"automatic dialing. This requires additional software / configuration on your " +"agent's computers." msgstr "" -#: ../system/integrations/zabbix.rst:53 -msgid "Click the **Update** button to save the **Webhook** settings." +#: ../system/integrations/cti/generic.rst:9 +#: ../system/integrations/cti/placetel.rst:14 +#: ../system/integrations/cti/sipgate.rst:14 +msgid "Please provide the following requirements:" msgstr "" -#: ../system/integrations/zabbix.rst:55 +#: ../system/integrations/cti/generic.rst:11 msgid "" -"To receive notifications in **Zammad**, you need to create a **Zabbix user** " -"and add **Media** with the **Zammad** type." +"A telephone system that supports webhooks (outbound) (best option are those " +"that allow customizing the calls)." msgstr "" -#: ../system/integrations/zabbix.rst:58 -msgid "" -"For **Send to**: enter any text, as this value is not used, but is required." +#: ../system/integrations/cti/generic.rst:13 +msgid "A unique Call-ID during the call session." msgstr "" -#: ../system/integrations/zabbix.rst:61 -msgid "" -"For more information, use the `Zabbix documentation `_." +#: ../system/integrations/cti/generic.rst:14 +msgid "Call event data (both numbers and direction)." msgstr "" -#: ../system/maintenance.rst:2 -msgid "Maintenance" +#: ../system/integrations/cti/generic.rst:15 +msgid "Your Zammad instance must be reachable for your telephony system." msgstr "" -#: ../system/maintenance.rst:4 +#: ../system/integrations/cti/generic.rst:17 msgid "" -"Zammad comes with a maintenance mode that you can use for e.g. updating the " -"instance or changing settings while restricting availability and functions." +"If you want to learn more on what kind of requests are supported by Zammad " +"and what it expects, please consult our :docs:`CTI-API documentation `." msgstr "" -#: ../system/maintenance.rst:13 -msgid "Mode" +#: ../system/integrations/cti/generic.rst:22 +#: ../system/integrations/cti/placetel.rst:27 +#: ../system/integrations/cti/sipgate.rst:30 +msgid "Available Settings" msgstr "" -#: ../system/maintenance.rst:8 -msgid "The mode setting allows you to enable or disable the maintenance mode." +#: ../system/integrations/cti/generic.rst:29 +#: ../system/integrations/cti/placetel.rst:41 +#: ../system/integrations/cti/sipgate.rst:40 +msgid "Endpoint Settings" msgstr "" -#: ../system/maintenance.rst:10 -msgid "Defaults to *off*." +#: ../system/integrations/cti/generic.rst:25 +msgid "" +"Zammad will list your generic CTI endpoint here. It contains a unique token " +"so ensure to keep this URL save." msgstr "" -#: ../system/maintenance.rst:12 +#: ../system/integrations/cti/generic.rst:28 msgid "" -"The maintenance mode will restrict access to administrative roles only. This " -"means agents and customers are logged off." -msgstr "" - -#: ../system/maintenance.rst:23 -msgid "@Login" +"You'll need this endpoint for your PBX to talk to Zammad, see :docs:`CTI-API " +"documentation `." msgstr "" -#: ../system/maintenance.rst:16 +#: ../system/integrations/cti/includes/important-dont-forget-saving.include.rst:3 msgid "" -"This setting allows you to provide a login message within a green banner " -"above the login screen. Click into the green banner in the settings page to " -"adjust your message. To activate the message, activate the *@Login* setting." +"All following options **do not save automatically**. Always use the Save " +"button on the lower end of the integration page!" msgstr "" -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing the default login message within the\n" -"settings page" +#: ../system/integrations/cti/generic.rst:43 +#: ../system/integrations/cti/placetel.rst:49 +#: ../system/integrations/cti/sipgate.rst:52 +msgid "Call Settings" msgstr "" -#: ../system/maintenance.rst:26 -msgid "" -"Send an informative message to **all active sessions**. This comes handy to " -"inform your agents e.g. about mayor outages or to force reloads after " -"configuration changes." +#: ../system/integrations/cti/generic.rst:39 +#: ../system/integrations/cti/placetel.rst:49 +#: ../system/integrations/cti/sipgate.rst:37 +#: ../system/integrations/cti/sipgate.rst:50 +msgid "Inbound" msgstr "" -#: ../system/maintenance.rst:31 -msgid "This is the messages title (slightly bigger than the normal message)." +#: ../system/integrations/cti/includes/inbound-calls.include.rst:1 +msgid "" +"This option allows you to block specific incoming caller IDs. It allows you " +"to temporarily reject e.g. spam callers without having to contact providers " +"or PBX administrators." msgstr "" -#: ../system/maintenance.rst:34 -msgid "The text you want to provide to your logged in sessions." +#: ../system/integrations/cti/includes/inbound-calls.include.rst:11 +msgid "Caller ID to block" msgstr "" -#: ../system/maintenance.rst:39 -msgid "Reload application" +#: ../system/integrations/cti/includes/inbound-calls.include.rst:6 +msgid "Provide caller IDs to block in ``E.164`` format." msgstr "" -#: ../system/maintenance.rst:37 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:8 msgid "" -"Selecting this option will change the message acceptance button from *Close* " -"(with nothing happening) to *Continue session*, which forces the application " -"to reload." +"Your telephony system has to support this function. Zammad will send a " +"``reject`` response which will cause your telephony system to hang up the " +"call. To callers this usually will feel like the line is busy." msgstr "" -#: ../system/maintenance.rst:43 +#: ../system/integrations/cti/includes/inbound-calls.include.rst:14 msgid "" -"If you have customers that are logged in to Zammad, they'll also be notified " -"if they're active in that moment." -msgstr "" - -#: ../system/maintenance.rst:48 -msgid "Example without reload application" +"Provide a meaningful note for your fellow administrators to remind yourself " +"why you've chosen to block the number." msgstr "" -#: ../system/maintenance.rst:52 -msgid "" -"Message setting within Zammad's admin settings without ticket reload " -"application setting." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:17 +#: ../system/integrations/cti/sipgate.rst:40 +msgid "Outbound" msgstr "" -#: ../system/maintenance.rst:0 +#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:1 msgid "" -"Screenshot showing the send message settings without ticket\n" -"reload application set" +"In many cases you may want to use a different caller ID depending on the " +"destination you're calling. This may apply due to specific connection rates " +"to other countries or because you want your customer to feel you're calling " +"from the same country." msgstr "" -#: ../system/maintenance.rst:61 ../system/maintenance.rst:85 -msgid "" -"The modal all other active sessions will see upon pressing *Send to clients*." +#: ../system/integrations/cti/includes/outbound-calls-intro.include.rst:6 +msgid "This option expects ``E.164`` number formats." msgstr "" -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing modal caused by maintenance's message\n" -"without reload application ticket" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 +msgid "Destination caller ID" msgstr "" -#: ../system/maintenance.rst:72 -msgid "Example with reload application" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:5 +msgid "The caller ID or number you're trying to call." msgstr "" -#: ../system/maintenance.rst:76 -msgid "" -"Message setting within Zammad's admin settings with ticket reload " -"application setting." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:7 +msgid "You can use wildcards for e.g. country specific outbound numbers like:" msgstr "" -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing the send message settings with ticket\n" -"reload application set" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:9 +msgid "``49*`` for Germany" msgstr "" -#: ../system/maintenance.rst:0 -msgid "" -"Screenshot showing modal caused by maintenance's message\n" -"with reload application ticket" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:10 +msgid "``4930*`` for Berlin / Germany landlines" msgstr "" -#: ../system/monitoring.rst:2 -msgid "Monitoring" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:11 +msgid "``33*`` for France" msgstr "" -#: ../system/monitoring.rst:4 -msgid "" -"This function is only available in self hosted instances. If you use Zammad " -"in our cloud, we are monitoring the system on our own and take steps to fix " -"potential problems directly." +#: ../system/integrations/cti/includes/outbound-calls.include.rst:15 +msgid "Set Outbound caller ID" msgstr "" -#: ../system/monitoring.rst:11 +#: ../system/integrations/cti/includes/outbound-calls.include.rst:14 msgid "" -"On the monitoring page, you can see the current health state of Zammad under " -"\"*Current Status*\" at the bottom. This can be useful if you want to have a " -"look if everything is up and running. As an example, you could have a look " -"in the monitoring when you assume that some emails aren't processed from " -"Zammad." +"The outbound caller ID to set (the number your customer sees on his display) " +"in ``E.164`` number format." msgstr "" -#: ../system/monitoring.rst:17 -msgid "**Can't receive an email and the monitoring response is \"healthy\"?**" +#: ../system/integrations/cti/includes/outbound-calls.include.rst:18 +msgid "Provide a short description for fellow administrators." msgstr "" -#: ../system/monitoring.rst:19 +#: ../system/integrations/cti/includes/generic-cti-support-note.includes.rst:3 msgid "" -"Zammad will just inform you about unprocessable emails. This is not the case " -"for oversized emails. You can adjust the maximum email size in :doc:`../" -"channels/email/settings`." +"This option requires your PBX to send a specific request to Zammad *before " +"dialing*. Please consult the :docs:`CTI API ` in case " +"you're not sure." msgstr "" -#: ../system/monitoring.rst:24 -msgid "Monitoring API" +#: ../system/integrations/cti/generic.rst:52 +#: ../system/integrations/cti/placetel.rst:54 +#: ../system/integrations/cti/sipgate.rst:59 +msgid "Other Settings" msgstr "" -#: ../system/monitoring.rst:26 +#: ../system/integrations/cti/includes/other-settings-intro.include.rst:1 msgid "" -"Beside the indication in the monitoring page, you can also use an external " -"monitoring tool to monitor Zammad's health. To request the health of Zammad, " -"you need to provide the API key (token) to the external monitoring tool. You " -"can copy the token from the \"*Current Token*\" field as well as the whole " -"API endpoint of your system (\"*Health Check*\" field), in which the API " -"token is already included." +"Below you can find all available additional settings for this CTI " +"integration. For your overview we're sorting them by appearance and " +"reference their description first." msgstr "" -#: ../system/monitoring.rst:37 -msgid "Screenshot showing Current Token and Health Check" +#: ../system/integrations/cti/includes/default-caller-id.include.rst:2 +#: ../system/integrations/cti/includes/default-caller-id.include.rst:1 +msgid "Default caller ID for outbound calls" msgstr "" -#: ../system/monitoring.rst:37 -msgid "Screenshot showing Token and Health Check" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:16 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:15 +msgid "Shown records in caller log" msgstr "" -#: ../system/monitoring.rst:39 +#: ../system/integrations/cti/includes/records-caller-log.include.rst:2 msgid "" -"In addition to that, you can reset the auto-generated token to make sure " -"that already configured monitoring systems won't work anymore. So, please " -"use this \"*Reset*\" button only if you know what you do!" +"Allows you to set the number of shown caller log entries for all users. You " +"can choose from the following values:" msgstr "" -#: ../system/monitoring.rst:44 -#, fuzzy -msgid "Example Output" -msgstr "例如" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:5 +msgid "60 (default)" +msgstr "" -#: ../system/monitoring.rst:0 -msgid "No issues found" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:6 +msgid "120" msgstr "" -#: ../system/monitoring.rst:48 ../system/monitoring.rst:60 -msgid "**Indicator in Zammad**:" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:7 +msgid "180" msgstr "" -#: ../system/monitoring.rst:0 -msgid "Screenshot showing monitoring with no issues" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:8 +msgid "240" msgstr "" -#: ../system/monitoring.rst:54 ../system/monitoring.rst:66 -msgid "**API response**::" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:9 +msgid "300" msgstr "" -#: ../system/monitoring.rst:0 -msgid "Issues were found" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:11 +msgid "**🥵 Potential performance issue**" msgstr "" -#: ../system/monitoring.rst:0 -msgid "Screenshot showing monitoring with issues" +#: ../system/integrations/cti/includes/records-caller-log.include.rst:13 +msgid "" +"Setting this setting higher than 60 may cause serious performance issues on " +"very busy instances. Keep in mind that this setting causes Zammad to poll " +"and send up to 300 records to *all active agent sessions* in very short time " +"periods." msgstr "" -#: ../system/objects.rst:2 -msgid "Objects" +#: ../system/integrations/cti/generic.rst:73 +msgid "Caller Log Filter" msgstr "" -#: ../system/objects.rst:4 +#: ../system/integrations/cti/generic.rst:55 msgid "" -"In Zammad you can add your own fields to tickets, users, organizations and " -"even groups (these are called \"objects\"). This can be useful if you need " -"to add further information to a ticket or any other object in Zammad and the " -"information doesn't fit in any existing field." +"This function allows you to provide call information based on e.g. queues " +"only to agents that really need the information." msgstr "" -#: ../system/objects.rst:11 +#: ../system/integrations/cti/generic.rst:58 msgid "" -"Try to avoid deleting attributes (and disable them instead) as Zammad might " -"run into unexpected conditions if they are referenced somewhere." +"Why? If you have a team for several countries or departments, you don't want " +"to bug your agents from other departments. Leaving these options empty will " +"fallback to showing everything to everyone." msgstr "" -#: ../system/objects.rst:16 -msgid "" -"Here's an overview of object attributes. On the upper right you can add new " -"attributes. By default, there will be no custom fields - standard attributes " -"will be grayed out, you can't delete or change those. You can edit custom " -"attributes (they are displayed in black font and have a trash bin on the " -"right side) just by clicking on them." +#: ../system/integrations/cti/generic.rst:64 +msgid "Destination caller ID or Queue" msgstr "" -#: ../system/objects.rst:24 +#: ../system/integrations/cti/generic.rst:63 msgid "" -"Attributes you add to Zammad, no matter if they have default values or not, " -"will not update existing information. This means a new ticket field " -"technically will be empty unless you populate it." +"This depends on your PBX and usually is either a queue ID, phone number or " +"extension." msgstr "" -#: ../system/objects.rst:28 -msgid "" -"Especially in ticket scope this also means that newly added attributes will " -"be indicated as \"changed\" to agents that view the ticket. This may " -"interfere with Zammad's tabs behavior." +#: ../system/integrations/cti/generic.rst:69 +msgid "Agents" msgstr "" -#: ../system/objects.rst:40 -#, fuzzy -msgid "Ordering Attributes" -msgstr "组织和部门名称" - -#: ../system/objects.rst:42 +#: ../system/integrations/cti/generic.rst:67 msgid "" -"Since Zammad introduced :doc:`/system/core-workflows` the need to have a " -"custom positioning for attributes has become more important than ever." +"Select the agents that are responsible for the group. These agents will then " +"see caller log entries and call notifications fitting to said queue." msgstr "" -#: ../system/objects.rst:45 +#: ../system/integrations/cti/generic.rst:0 msgid "" -"To adjust the position of such an attribute, simply click on the attribute " -"entry in question, scroll down and adjust the position number. Please note " -"that you cannot change the positioning of default attributes." +"Screenshot showing the caller log filter table with pre filled sample data" msgstr "" -#: ../system/objects.rst:49 +#: ../system/integrations/cti/includes/recent-logs.include.rst:6 msgid "" -"In case two attributes have the same position value, Zammad will sort " -"alphabetically by name automatically." +"With recent logs Zammad allows you to view the latest calls for the CTI " +"functionality. This usually comes in handy, when you're looking for errors." msgstr "" -#: ../system/objects.rst:None +#: ../system/integrations/cti/includes/recent-logs.include.rst:0 msgid "" -"Screenshot showing custom attribute entries ordered in between default ones" -msgstr "" - -#: ../system/objects.rst:56 -msgid "Updating Database After Adding or Editing Attributes" +"Screenshot showing several incoming requests within Recent logs section." msgstr "" -#: ../system/objects.rst:58 -msgid "" -"When adding or changing attributes, Zammad will not apply the changes " -"instantly, but instead shows you the changed attributes first. If you're " -"ready to go, just click on \"Update database\" to apply the changes to " -"Zammad. If you made a mistake or just want to discard your changes, click " -"\"Discard changes\"." +#: ../system/integrations/cti/includes/recent-logs.include.rst:16 +msgid "I'm just here to clear floats up." msgstr "" -#: ../system/objects.rst:64 +#: ../system/integrations/cti/includes/recent-logs.include.rst:20 msgid "" -"After applying the changes with \"Update Database\", a restart of Zammad is " -"**mandatory**. If you don't perform it, you may experience unexpected " -"behavior or even errors. You may want to do this kind of configuration " -"during maintenance windows." +"By clicking on the entry of interest, Zammad will provide more details on " +"the call in question. You'll see the payload it received and also the " +"response that was sent." msgstr "" -#: ../system/objects.rst:72 +#: ../system/integrations/cti/includes/recent-logs.include.rst:0 msgid "" -"Changes on objects require you to update the database to apply these changes." +"Screenshot showing detailed information of a specific log entry of recent " +"logs" msgstr "" -#: ../system/objects.rst:75 -msgid "**🤓 Service restarts can be automated**" +#: ../system/integrations/cti/includes/recent-logs.include.rst:31 +msgid "x" msgstr "" -#: ../system/objects.rst:0 -msgid "Hosted environments automatically restart for you." +#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 +#: ../system/integrations/cti/includes/troubleshooting.include.rst:9 +msgid "My Phone page stays blank, signalling does work..." msgstr "" -#: ../system/objects.rst:0 +#: ../system/integrations/cti/includes/troubleshooting.include.rst:5 msgid "" -"If you're using a self-hosted installation you can use :docs:`environment " -"variables `" +"If you've made sure that signalling works (check Recent logs) and your " +"Caller Log still stays empty, please ensure that you only configured one CTI " +"integration version. Specifically defining more than one agent mapping on " +"the different integration variants will be the issue." msgstr "" -#: ../system/objects.rst:82 -msgid "System Attributes" +#: ../system/integrations/cti/includes/troubleshooting.include.rst:10 +msgid "Clear the not needed agent mapping and reload your browser page." msgstr "" -#: ../system/objects.rst:84 +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:1 msgid "" -"Zammad comes with pre-configured attributes. Some of them can't be edited " -"via UI (or at all). This is required for proper operation of Zammad and not " -"a bug." +"By mapping your agents extension to their existing Zammad users, Zammad can " +"provide a new ticket dialog or open the user profile for the agent that " +"picks up the call." msgstr "" -#: ../system/objects.rst:90 -msgid "Ticket State" +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:5 +msgid "" +"This speeds up ticket aiding, no matter if it's for existing tickets or new " +"ones!" msgstr "" -#: ../system/objects.rst:92 +#: ../system/integrations/cti/includes/extenion-to-agent-mapping.include.rst:8 msgid "" -"If the pre-configured states aren't enough for you or you want to change " -"them, you can do so by clicking on the cogwheel icon in the state row in the " -"ticket tab. But you should be careful when changing pre-configured states. " -"This can lead to unwanted behavior in some cases." +"To see it work from the agent's perspective, have a look on :user-docs:`user " +"documentation `." msgstr "" -#: ../system/objects.rst:None -msgid "Screenshot showing highlighted ticket state attribute" +#: ../system/integrations/cti/placetel.rst:2 +msgid "Placetel CTI" msgstr "" -#: ../system/objects.rst:122 -msgid "Handling of states" +#: ../system/integrations/cti/placetel.rst:16 +msgid "You need an administrative Placetel account for your organization." msgstr "" -#: ../system/objects.rst:102 +#: ../system/integrations/cti/placetel.rst:17 +#: ../system/integrations/cti/sipgate.rst:20 msgid "" -"In the state configuration screen, you can add new states, disable states or " -"change states." +"Your Zammad instance must be allowed to communicate to external services." msgstr "" -#: ../system/objects.rst:0 -msgid "Screenshot showing table of default ticket states" +#: ../system/integrations/cti/placetel.rst:18 +msgid "Placetel must be able to reach your Zammad instance." msgstr "" -#: ../system/objects.rst:110 -msgid "" -"To add a new state, click on the \"New Ticket State\" button in the top " -"right corner. To change an existing state, simply click on the affected " -"state. This opens an edit dialog." +#: ../system/integrations/cti/placetel.rst:22 +msgid ":doc:`provider-configurations/placetel`" msgstr "" -#: ../system/objects.rst:114 +#: ../system/integrations/cti/placetel.rst:21 msgid "" -"You can also clone a state or set them to \"Default for new tickets\" or " -"\"Default for follow-ups\" by clicking on the ⁝ action button and select the " -"desired function." +"Learn how to configure Placetel to enable Zammad and Placetel to communicate " +"with each other." msgstr "" -#: ../system/objects.rst:118 +#: ../system/integrations/cti/placetel.rst:32 msgid "" -"*Default for new tickets* means that this state is used for every newly " -"created ticket." +"The here listed endpoint settings are relevant for the :doc:`integration " +"configuration with Placetel `." msgstr "" -#: ../system/objects.rst:121 -msgid "" -"*Default for follow-ups* means that this state is used if the ticket is re-" -"opened after it was closed." +#: ../system/integrations/cti/placetel.rst:37 +#: ../system/integrations/i-doit.rst:53 +msgid "Endpoint" msgstr "" -#: ../system/objects.rst:171 -msgid "Ticket state in detail" +#: ../system/integrations/cti/placetel.rst:36 +msgid "" +"This endpoint will be required for the Zammad integration within the " +"Placetel web interface." msgstr "" -#: ../system/objects.rst:125 -msgid "" -"Below you can find a description for each field and option. Please head over " -"to the :ref:`example ` to see the edit dialog." +#: ../system/integrations/cti/placetel.rst:41 +msgid "API Token" msgstr "" -#: ../system/objects.rst:129 +#: ../system/integrations/cti/placetel.rst:40 msgid "" -"This is the name of the state and what you and your agents are seeing when " -"choosing a state somewhere (e.g. in tickets, trigger configuration)." +"You'll receive this token within the ``Web API`` menu. Make sure to copy " +"this value, it's only shown once!" msgstr "" -#: ../system/objects.rst:137 -msgid "" -"There are different state types you can choose from. By default, Zammad " -"comes with one state per state type." +#: ../system/integrations/cti/placetel.rst:71 +#: ../system/integrations/cti/sipgate.rst:77 +msgid "Phone Extension to Agent Mapping" msgstr "" -#: ../system/objects.rst:140 -msgid "" -"**new**: for states for tickets that are new and it hasn't been worked on " -"them" +#: ../system/integrations/cti/placetel.rst:0 +msgid "Screenshot showing sample user mappings in between Placetel and Zammad" msgstr "" -#: ../system/objects.rst:142 +#: ../system/integrations/cti/placetel.rst:64 msgid "" -"**open**: for states for tickets that are in progress and agents are working " -"on them" +"You can find your agents Placetel username combination required within ⚙️ PBX " +"→ VoIP destinations. Within the \"Advanced settings\" section you're looking " +"for \"SIP user name\" and \"SIP server\"." msgstr "" -#: ../system/objects.rst:144 -msgid "**merged**: for states for tickets that are merged with other tickets" +#: ../system/integrations/cti/placetel.rst:68 +msgid "Combine these two like so: ``@``." msgstr "" -#: ../system/objects.rst:145 -msgid "" -"**pending reminder**: for states for tickets that are in progress and you " -"want to set a reminder. (default example: *pending reminder*)" +#: ../system/integrations/cti/placetel.rst:0 +msgid "Sample VoIP credentials for a Placetel user" msgstr "" -#: ../system/objects.rst:147 -msgid "" -"**pending action**: for states for tickets that are waiting for a specified " -"time and then change their state (default example: *pending close*)" +#: ../system/integrations/cti/provider-configurations/placetel.rst:2 +msgid "Setup Placetel connection for Zammad" msgstr "" -#: ../system/objects.rst:150 +#: ../system/integrations/cti/provider-configurations/placetel.rst:6 msgid "" -"**closed**: for states for tickets that are finished and do not need to be " -"processed further" +"This configuration step requires a *full* administrative Placetel account. " +"You may receive forbidden error messages with Placetel in case your " +"permissions are not high enough." msgstr "" -#: ../system/objects.rst:153 +#: ../system/integrations/cti/provider-configurations/placetel.rst:10 msgid "" -"⚠️ Choosing the correct state type is important! If you are in doubt, have a " -"look on the default states and their types!" +"The following actions can be configured via the `Placetel web interface " +"`_." msgstr "" -#: ../system/objects.rst:158 -msgid "Ignore escalation" +#: ../system/integrations/cti/provider-configurations/placetel.rst:29 +msgid "Step 1: Activate Zammad integration" msgstr "" -#: ../system/objects.rst:157 +#: ../system/integrations/cti/provider-configurations/placetel.rst:14 msgid "" -"Here you can define whether tickets of this state will count to escalation " -"time or not." +"Within Integrations, scroll down to Partner integrations and select Zammad." msgstr "" -#: ../system/objects.rst:161 +#: ../system/integrations/cti/provider-configurations/placetel.rst:17 msgid "" -"You can create a note for the state to inform other admins about the state. " -"This has no effect on tickets." +"You can alternatively filter by \"Ticket Systems\" to reduce the number of " +"entries on the page. You'll still want to look for Partner integrations. 🤓" msgstr "" -#: ../system/objects.rst:165 -msgid "Set the state to *active* or *inactive*." +#: ../system/integrations/cti/provider-configurations/placetel.rst:21 +msgid "" +"Within the Zammad integration now press \"Activate\". A new tab ``API`` " +"becomes available - open this tab." msgstr "" -#: ../system/objects.rst:167 +#: ../system/integrations/cti/provider-configurations/placetel.rst:24 msgid "" -"it is technically possible to set all states to inactive. To keep Zammad " -"working in such a case, the inactive flag of one of the states is ignored." +"Now tick \"Enable Call Control / Notify API\" and paste the Placetel " +"endpoint from your Zammad instance into the field \"URL of your API " +"endpoint\". Save to apply the settings" msgstr "" -#: ../system/objects.rst:194 -msgid "Ticket state example" +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "Screencast showing how to activate the Zammad integration" msgstr "" -#: ../system/objects.rst:174 -msgid "" -"Let's assume we want to create a new state which indicates that the ticket " -"has to wait for a response of a third party (e.g. service contractor or " -"manufacturer) and we want to to be able to set a reminder." +#: ../system/integrations/cti/provider-configurations/placetel.rst:51 +msgid "Step 2: Generate API Token for Placetel" msgstr "" -#: ../system/objects.rst:178 +#: ../system/integrations/cti/provider-configurations/placetel.rst:32 msgid "" -"First we give the new state a proper name. In this example we call it " -"\"waiting for manufacturer\"." +"Go back to the integrations page and scroll down to \"Web API\". Generate a " +"new API token by using the \"Create a new API token\" button." msgstr "" -#: ../system/objects.rst:181 +#: ../system/integrations/cti/provider-configurations/placetel.rst:37 msgid "" -"As state type we choose \"pending reminder\". This indicates that the ticket " -"is still open and we can set a reminder. This reminder can be useful if our " -"manufacturer sometimes isn't responding or we want to remind him to give us " -"an answer." +"If you already generated a token either use your existing token or reset it " +"by using above mentioned button. Placetel will ask you to conform this reset." msgstr "" -#: ../system/objects.rst:186 +#: ../system/integrations/cti/provider-configurations/placetel.rst:41 msgid "" -"We choose \"no\" for \"ignore escalation\" because we want to escalate the " -"tickets even if we are waiting on the manufacturer's feedback." +"Please keep in mind that existing API scripts may no longer work due to " +"token resets!" msgstr "" -#: ../system/objects.rst:189 -#, fuzzy -msgid "The **result** in the creation dialog will look like this:" -msgstr "最终结果将如下所示：" - -#: ../system/objects.rst:0 -msgid "Screenshot showing ticket state creation dialog with example" +#: ../system/integrations/cti/provider-configurations/placetel.rst:44 +msgid "" +"Copy the provided API token and insert it into the \"API Token\" field " +"within Zammad's Placetel integration." msgstr "" -#: ../system/objects.rst:197 ../system/objects.rst:199 -#, fuzzy -msgid "Ticket Priority" -msgstr "优先级" - -#: ../system/objects.rst:199 ../system/objects.rst:201 +#: ../system/integrations/cti/provider-configurations/placetel.rst:47 msgid "" -"If the pre-configured priorities aren't enough for you or you want to change " -"them, you can do so by clicking on the cogwheel icon in the priority row in " -"the ticket tab:" +"Apply your changes by using the \"Save\" button on the bottom of the " +"Placetel integration page and activate the Placetel integration." msgstr "" -#: ../system/objects.rst:None -msgid "Screenshot showing highlighted ticket priority attribute" +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "" +"Screencast showing how to retrieve an API token from Placetel for Zammad" msgstr "" -#: ../system/objects.rst:224 ../system/objects.rst:226 -msgid "Handling of priorities" +#: ../system/integrations/cti/provider-configurations/placetel.rst:73 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:77 +msgid "Step 3: Restrict the numbers to notify on" msgstr "" -#: ../system/objects.rst:208 ../system/objects.rst:210 +#: ../system/integrations/cti/provider-configurations/placetel.rst:54 msgid "" -"In the priority configuration screen, you can add new priorities, disable " -"priorities or change priorities." +"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " +"the the Integrations page of the Placetel web interface, go to \"Notify " +"API\"." msgstr "" -#: ../system/objects.rst:0 -msgid "Screenshot showing table of default ticket priorities" +#: ../system/integrations/cti/provider-configurations/placetel.rst:58 +msgid "" +"Lower on the page Placetel allows you to restrict the numbers to notify on. " +"You'll find this within the \"External routing API\" part." msgstr "" -#: ../system/objects.rst:216 ../system/objects.rst:218 +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 msgid "" -"To add a new priority, click on the \"New Priority\" button in the top right " -"corner. To change an existing priority, simply click on the affected " -"priority. This opens an edit dialog." +"Screenshot showing a sample selection of phone numbers to use for the " +"Placetels notify API" msgstr "" -#: ../system/objects.rst:220 ../system/objects.rst:222 +#: ../system/integrations/cti/provider-configurations/placetel.rst:66 msgid "" -"You can also clone a priority or set them to \"Default for new tickets\" by " -"clicking on the ⁝ action button and select the desired function." +"This menu point also provides a API request log from Placetel view. Just " +"open \"Recent responses of your API endpoint\" to learn more." msgstr "" -#: ../system/objects.rst:223 ../system/objects.rst:225 +#: ../system/integrations/cti/provider-configurations/placetel.rst:69 msgid "" -"*Default for new tickets* means that this priority is used for every newly " -"created ticket." +"If you want to see Zammad's perspective, use the \"Recent Logs\" part from " +"within the Placetel integration page." msgstr "" -#: ../system/objects.rst:246 ../system/objects.rst:248 -msgid "Priorities in detail" +#: ../system/integrations/cti/provider-configurations/placetel.rst:0 +msgid "Screenshot showing sample log entries for Placetels API calls to Zammad" msgstr "" -#: ../system/objects.rst:227 ../system/objects.rst:229 -msgid "Below you can find a description for each field and option." +#: ../system/integrations/cti/provider-configurations/placetel.rst:77 +msgid "Step 4 (optional): Further configurations for Placetel" msgstr "" -#: ../system/objects.rst:230 ../system/objects.rst:232 +#: ../system/integrations/cti/provider-configurations/placetel.rst:76 msgid "" -"This is the name of the priority and what you and your agents are seeing " -"when choosing a priority somewhere (e.g. in tickets, trigger configuration)." +"If needed, you can now configure Zammad's Placetel integration in more " +"detail. You can learn more about your options here: :ref:`Placetel " +"integration settings `." msgstr "" -#: ../system/objects.rst:240 ../system/objects.rst:242 -msgid "Highlight color" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:2 +msgid "Setup Sipgate connection for Zammad" msgstr "" -#: ../system/objects.rst:235 ../system/objects.rst:237 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"Switch between *Low priority* (light blue), *High priority* (red) and - " -"(default). This affects the displayed color for ticket titles in overviews." +"Sipgate has no english web interface which is why this documentation page is " +"mixing up languages badly." msgstr "" -#: ../system/objects.rst:239 ../system/objects.rst:241 -msgid "The color options are currently limited to the mentioned options." +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "" +"Please also note that the availability of API addons highly depends on your " +"package trier. Usage of sipgate.io packages *is not free*, please check " +"their `pricing page `_ before!" msgstr "" -#: ../system/objects.rst:243 ../system/objects.rst:245 -msgid "" -"You can create a note for the priority to inform other admins about the " -"priority. This has no effect on tickets." +#: ../system/integrations/cti/provider-configurations/sipgate.rst:35 +msgid "Step 1: Book sipgate.io package" msgstr "" -#: ../system/objects.rst:247 ../system/objects.rst:249 -msgid "Set the priority to *active* or *inactive*." +#: ../system/integrations/cti/provider-configurations/sipgate.rst:13 +msgid "Skip to step 2 if you already have the package booked!" msgstr "" -#: ../system/objects/external-data-source-example.rst:2 -msgid "External Data Source" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:15 +msgid "" +"Login to an administrative Sipgate account and navigate to " +"``Accountverwaltung``. You'll see several different options depending on " +"your booked packages. Select ``Verträge & Produkte`` to continue." msgstr "" -#: ../system/objects/external-data-source-example.rst:4 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:19 msgid "" -"We assume you already had a look on :doc:`types` where you can find a " -"description of the individual fields." +"Scroll down to the section ``Zusätzliche Produkte buchen`` and look for " +"``sipgate.io`` - select this product by using the ``Produkte anzeigen``-" +"Button." msgstr "" -#: ../system/objects/external-data-source-example.rst:7 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:23 msgid "" -"To reproduce this example, choose a category you want to add a custom field, " -"click on *New Attribute* and select *External data source field* under " -"*Format*." +"On the next page select either one of the ``sipgate.io`` packages or ``Push-" +"API Package Free``. Follow the dialogue by booking the addon. You'll be " +"returned to your contract overview and now should see the selected addon in " +"your list." msgstr "" -#: ../system/objects/external-data-source-example.rst:11 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:30 msgid "" -"Our example story is to fetch data from an external product database. We " -"want to add our products to the tickets so that the products can be searched " -"and chosen from a list and also create a link to the product website." +"The availability for ``sipgate.io`` packages and their levels highly depends " +"on the overall account type and product you've booked with Sipgate." msgstr "" -#: ../system/objects/external-data-source-example.rst:16 -msgid "Base configuration" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "" +"Screencast showing the process on how to book the required sipgate.io addon" msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Initial steps to configure external data source object type" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:52 +msgid "Step 2: Configure webhook for Zammad" msgstr "" -#: ../system/objects/external-data-source-example.rst:23 -#: ../system/variables.rst:85 -#, fuzzy -msgid "**Example:**" -msgstr "例如" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:38 +msgid "" +"Within your ``Accountverwaltung`` navicate to your product ``sipgate.io``. " +"In the newly opened tab, switch from \"Clients\" to \"Webhooks\" and paste " +"the endpoint URLs from your Zammad instance like so:" +msgstr "" -#: ../system/objects/external-data-source-example.rst:25 -msgid "Name: *product*" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:42 +msgid "Inbound endpoint to \"Incoming\"" msgstr "" -#: ../system/objects/external-data-source-example.rst:26 -msgid "Display: *Product*" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:43 +msgid "Outbound endpoint to \"Outgoing\"" msgstr "" -#: ../system/objects/external-data-source-example.rst:29 -msgid "External data source configuration" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:47 +msgid "" +"Ensure to select at least one call group or phoneline within \"Sources\". " +"Other wise Sipgate will not indicate any incoming or outgoing calls to " +"Zammad." msgstr "" -#: ../system/objects/external-data-source-example.rst:31 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 msgid "" -"First, enter the search URL making sure it contains ``#{search.term}`` as a " -"parameter:" +"Screencast showing how to add Zammad's endpoint URLs to sipgate.ios webhook " +"configuration" msgstr "" -#: ../system/objects/external-data-source-example.rst:34 -msgid "**Example:** ``https://dummyjson.com/products/search?q=#{search.term}``" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:55 +msgid "" +"Having a lot of numbers that shouldn't be used for notifying Zammad? Within " +"the Webhooks → URLs section of Sipgate you can select which *sources* " +"Sipgate should notify Zammad about in- and outgoing calls." msgstr "" -#: ../system/objects/external-data-source-example.rst:36 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:59 msgid "" -"After that, head down to the preview section and enter a search input for " -"the external data source." +"Use either specific phone lines or use the option \"Use for all phonelines " +"and groups\" to notify Zammad about all existing lines of your Sipgate " +"account." msgstr "" -#: ../system/objects/external-data-source-example.rst:39 -msgid "**Example:** ``mac``" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "" +"Screenshot showing a sample selection of phone numbers to use for the " +"Sipgates webhooks API" msgstr "" -#: ../system/objects/external-data-source-example.rst:41 -msgid "Then you can find a preview of the response data below:" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:68 +msgid "This section also allows you to enable a Debug log." msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of JSON response based on search term" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "Screenshot showing an enabled Debug log option" msgstr "" -#: ../system/objects/external-data-source-example.rst:48 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:73 msgid "" -"We recommend using the preview to have a look on the structure. There is a " -"top-level element called ``products``. One level below, you can find the " -"attributes ``id`` and ``title``." +"After enabling you can use the Debug log section to see all sent webhook " +"calls to Zammad. You'll also can see the response." msgstr "" -#: ../system/objects/external-data-source-example.rst:52 -msgid "**Search result response based on search from example:**" +#: ../system/integrations/cti/provider-configurations/sipgate.rst:0 +msgid "" +"Screenshot showing sample log entries for Sipgates webhook calls to Zammad" msgstr "" -#: ../system/objects/external-data-source-example.rst:119 -msgid "" -"To tell the remote system that the desired data is located below the " -"``products`` level, you have to put it in the field *Search result list key*." +#: ../system/integrations/cti/provider-configurations/sipgate.rst:81 +msgid "Step 4 (optional): Further configurations for Sipgate" msgstr "" -#: ../system/objects/external-data-source-example.rst:122 +#: ../system/integrations/cti/provider-configurations/sipgate.rst:80 msgid "" -"After inserting ``products`` in the mentioned field, you get an extended " -"preview. You can find an additional box *Search result list* with a JSON " -"structure. This is the same response as before but stripped from the upper " -"``products`` element by the external data source." +"If needed, you can now configure Zammad's Sipgate integration in more " +"detail. You can learn more about your options here: :ref:`Sipgate " +"integration settings `." msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of JSON response search result list" +#: ../system/integrations/cti/sipgate.rst:2 +msgid "Sipgate (sipgate.io)" msgstr "" -#: ../system/objects/external-data-source-example.rst:132 -msgid "" -"Now you need to provide the keys for the search result values and labels. As " -"already mentioned, we are looking for the ``id`` and the ``title`` of our " -"products. If you haven't already, it is now a good time to look at the " -"preview of the *Search result list*." +#: ../system/integrations/cti/sipgate.rst:16 +msgid "You need an administrative Sipgate account for your organization." msgstr "" -#: ../system/objects/external-data-source-example.rst:197 +#: ../system/integrations/cti/sipgate.rst:17 msgid "" -"After locating our two keys, we insert them in *search result value key* " -"(``id``) and in *Search result label key* (``title``)." +"Zammad requires a ``sipgate.io`` addon from the feature store (please note " +"that API calls are not free with Sipgate. Rates may apply and differ from " +"account to account)." msgstr "" -#: ../system/objects/external-data-source-example.rst:200 -msgid "" -"Basically, we configured the external data source already and we can see a " -"table in the preview section:" +#: ../system/integrations/cti/sipgate.rst:21 +msgid "Sipgate must be able to reach your Zammad instance." msgstr "" -#: ../system/objects/external-data-source-example.rst:None -msgid "Preview of product table based on search term" +#: ../system/integrations/cti/sipgate.rst:25 +msgid ":doc:`provider-configurations/sipgate`" msgstr "" -#: ../system/objects/external-data-source-example.rst:208 +#: ../system/integrations/cti/sipgate.rst:24 msgid "" -"According to our example story, now just the *Link template* is missing." +"Learn how to configure Sipgate to enable Zammad and Sipgate to communicate " +"with each other." msgstr "" -#: ../system/objects/external-data-source-example.rst:210 +#: ../system/integrations/cti/sipgate.rst:33 msgid "" -"Please note that this is an optional feature. If you don't want to use such " -"links, of course you don't have to configure it." +"Below endpoint settings affect the :doc:`sipgate.io configuration `." msgstr "" -#: ../system/objects/external-data-source-example.rst:213 -msgid "" -"We can add now an address where additional product information can be found." +#: ../system/integrations/cti/sipgate.rst:37 +msgid "This endpoint is required for incoming call hooks." msgstr "" -#: ../system/objects/external-data-source-example.rst:215 -msgid "Example: ``https://your_domain.com/q=#{ticket.product}``" +#: ../system/integrations/cti/sipgate.rst:40 +msgid "This endpoint is required for outgoing call hooks." msgstr "" -#: ../system/objects/external-data-source-example.rst:217 -msgid "In the example, the parameter means:" +#: ../system/integrations/cti/sipgate.rst:0 +msgid "Screenshot showing sample user mappings in between Sipgate and Zammad" msgstr "" -#: ../system/objects/external-data-source-example.rst:219 -msgid "``#{}``: \"Frame\" for the insertion of information" +#: ../system/integrations/cti/sipgate.rst:69 +msgid "" +"You can find your agent's Sipgate username within ``Accountverwaltung → " +"Benutzer``. You're looking for the SIP-ID." msgstr "" -#: ../system/objects/external-data-source-example.rst:220 -msgid "``ticket``: object level, where you create your custom object" +#: ../system/integrations/cti/sipgate.rst:0 +msgid "Sample VoIP credentials for a Sipgate user" msgstr "" -#: ../system/objects/external-data-source-example.rst:221 -msgid "``product``: name of the (custom) object" +#: ../system/integrations/cti/sipgate.rst:77 +msgid "Users with several devices also have several SIP-IDs." msgstr "" -#: ../system/objects/external-data-source-example.rst:223 -msgid "" -"After configuring your *Link template*, there will be another column in the " -"preview. Hovering on the icons in the *Link* column will show you where it " -"forwards you." +#: ../system/integrations/elasticsearch.rst:2 +msgid "Elasticsearch (SaaS)" msgstr "" -#: ../system/objects/external-data-source-example.rst:232 +#: ../system/integrations/elasticsearch.rst:4 msgid "" -"In our example, one of the links looks like: https://your_domain.com/q=6, " -"where the 6 is the product id." +"The Elasticsearch integration allows you to create a read-only user to use " +"with your favorite reporting tool (e.g. like Grafana)." msgstr "" -#: ../system/objects/external-data-source-example.rst:235 -#, fuzzy -msgid "You can find more information regarding the URL in :doc:`types`." -msgstr "您还可以在管理员区域中找到有关聊天自定义的更多信息。" - -#: ../system/objects/includes/adding-values-hint.include.rst:3 +#: ../system/integrations/elasticsearch.rst:7 msgid "" -"Adding values can be tricky for first timers, don't forget to press \"➕ " -"Add\" after typing your values. Otherwise you may loose a value." +"If you want to take full advantage of the Zammad reporting, have a look at " +"our :docs:`Grafana ` " +"setup page as well." msgstr "" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:1 -#: ../system/objects/includes/reposition-values.include.rst:1 -msgid "**↕️ This field type allows the positioning of its values ↔️**" +#: ../system/integrations/elasticsearch.rst:11 ../system/subscription.rst:7 +msgid "**🚧 Hosted environment specific 🚧**" msgstr "" -#: ../system/objects/includes/reposition-treeselect-values.include.rst:3 +#: ../system/integrations/elasticsearch.rst:13 msgid "" -"In order to re-arrange the field values, first edit the field. Then you can " -"use ☰ to drag the values in question to the correct position. If you want to " -"change the layer depth, double click on ☰. With it you can cycle through the " -"available layers." -msgstr "" - -#: ../system/objects/includes/reposition-treeselect-values.include.rst:8 -msgid "When you're ready, submit your changes to save the object attribute." +"This integration is only available for Hosted setups. In order to use " +"Elasticsearch you'll need the **Plus** subscription." msgstr "" -#: :0 ../system/objects/types.rst:0 +#: ../system/integrations/elasticsearch.rst:16 msgid "" -"Screencast showing how to re-position values on tree select like\n" -"fields" +"Self hosted users have all the control over their self hosted Elasticsearch " +"instances." msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:3 -msgid "" -"In order to re-arrange the field values, edit the field and scroll below the " -"values. Make sure to tick the option \"Use custom option sort\"." +#: ../system/integrations/elasticsearch.rst:None +msgid "Elasticsearch integration page on SaaS environments" msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:8 +#: ../system/integrations/elasticsearch.rst:27 msgid "" -"If you do not tick this field, all manual positioning you did above will be " -"lost upon saving! ☠️" +"Please note the following limitations of Elasticsearch access on hosted " +"environments:" msgstr "" -#: ../system/objects/includes/reposition-values.include.rst:11 -msgid "" -"Now use ☰ to drag the values in question to the correct position. When " -"you're ready, submit your changes to save the object attribute." +#: ../system/integrations/elasticsearch.rst:30 +msgid "access to the Elasticsearch index is read-only access" msgstr "" -#: :0 ../system/objects/types.rst:0 -msgid "Screencast showing how to re-position values" +#: ../system/integrations/elasticsearch.rst:31 +msgid "currently you're limited to user only" msgstr "" -#: ../system/objects/includes/url-template-hint.include.rst:3 +#: ../system/integrations/elasticsearch.rst:32 msgid "" -"This field allows using :ref:`URL fields (Link Templates) `." -msgstr "" - -#: ../system/objects/permissions.rst:2 -msgid "Attribute Permissions" +"Reporting tools that require to write into the indexes (like Kibana) are not " +"supported" msgstr "" -#: ../system/objects/permissions.rst:7 -msgid "" -"In the object attributes configuration you can define if a field is shown " -"and if the input in the field is mandatory, separated by different screens " -"and for different :doc:`roles/permissions `." +#: ../system/integrations/elasticsearch.rst:34 +msgid "IP access restriction is currently not yet supported" msgstr "" -#: ../system/objects/permissions.rst:17 -msgid "Screenshot shows object attribute permission table" +#: ../system/integrations/elasticsearch.rst:37 +msgid "Activating Elasticsearch Access" msgstr "" -#: ../system/objects/permissions.rst:17 +#: ../system/integrations/elasticsearch.rst:39 msgid "" -"Some of the possible permissions and screen options for a user object " -"attribute." +"By default external access to your Elasticsearch index is not active. You " +"can enable the integration at any time if needed." msgstr "" -#: ../system/objects/permissions.rst:19 +#: ../system/integrations/elasticsearch.rst:42 msgid "" -"Based on the object context (ticket, agent, organization, user), the " -"selectable roles (to be precise: the required permissions) and screens " -"differ. Be aware that these settings aren't affecting data creation via " -"other channels than the UI." +"Please ensure to note down the password provided - you won't have access to " +"it afterwards." msgstr "" -#: ../system/objects/permissions.rst:24 -msgid "" -"If you want to have further customization possibilities, you should have a " -"look at the :doc:`core workflows `." +#: ../system/integrations/elasticsearch.rst:None +msgid "Screencast showing activation of Elasticsearch integration" msgstr "" -#: ../system/objects/permissions.rst:28 -msgid "Screens" +#: ../system/integrations/elasticsearch.rst:51 +msgid "Connection Settings" msgstr "" -#: ../system/objects/permissions.rst:30 +#: ../system/integrations/elasticsearch.rst:53 msgid "" -"In the table below you can find an overview about the different permissions " -"and the available screens Zammad distinguishes between." +"This section holds the most important general information for accessing your " +"Elasticsearch indexes - such as:" msgstr "" -#: ../system/objects/permissions.rst:37 -msgid "Screen" +#: ../system/integrations/elasticsearch.rst:57 +msgid "A unique subdomain that does not tell your real instance URL." msgstr "" -#: ../system/objects/permissions.rst:38 -msgid "Available for" +#: ../system/integrations/elasticsearch.rst:61 +msgid "Software" msgstr "" -#: ../system/objects/permissions.rst:40 -msgid "create" +#: ../system/integrations/elasticsearch.rst:60 +msgid "" +"The major version of the search index being used. This is required by some " +"Reporting tools like Grafana." msgstr "" -#: ../system/objects/permissions.rst:41 ../system/objects/permissions.rst:52 -#: ../system/objects/permissions.rst:59 ../system/objects/permissions.rst:73 -msgid "admin.user" +#: ../system/integrations/elasticsearch.rst:64 +msgid "Authentication" msgstr "" -#: ../system/objects/permissions.rst:42 ../system/objects/permissions.rst:53 -#: ../system/objects/permissions.rst:60 -msgid "admin.organization" +#: ../system/integrations/elasticsearch.rst:64 +msgid "The authentication type being supported. ``Basic Authentication``" msgstr "" -#: ../system/objects/permissions.rst:43 ../system/objects/permissions.rst:54 -#: ../system/objects/permissions.rst:61 -#, fuzzy -msgid "admin.group" -msgstr "组" - -#: ../system/objects/permissions.rst:44 -msgid "Creation dialog for not yet existing data" +#: ../system/integrations/elasticsearch.rst:67 +msgid "Available Indexes" msgstr "" -#: ../system/objects/permissions.rst:45 -msgid "create_middle" +#: ../system/integrations/elasticsearch.rst:69 +msgid "" +"Within this section we're displaying the -in our opinion- most important " +"indexes for a Zammad instance." msgstr "" -#: ../system/objects/permissions.rst:46 ../system/objects/permissions.rst:50 -#: ../system/objects/permissions.rst:57 ../system/objects/permissions.rst:66 -#: ../system/objects/permissions.rst:70 -#, fuzzy -msgid "ticket.customer" -msgstr "宏" - -#: ../system/objects/permissions.rst:47 ../system/objects/permissions.rst:51 -#: ../system/objects/permissions.rst:58 ../system/objects/permissions.rst:69 -#, fuzzy -msgid "ticket.agent" -msgstr "宏" +#: ../system/integrations/elasticsearch.rst:72 +msgid "" +"If you require all indexes or our listing is not good enough for you, point " +"your browser to the URL we're providing and append ``/_aliases?" +"pretty=true``. The result should look like this: ``https://.zammad.com/" +"_aliases?pretty=true``." +msgstr "" -#: ../system/objects/permissions.rst:48 -msgid "Ticket create dialog (middle section)" +#: ../system/integrations/elasticsearch.rst:77 +msgid "" +"Your browser will automatically ask for your credentials - you'll then see " +"something like this:" msgstr "" -#: ../system/objects/permissions.rst:49 -msgid "edit" +#: ../system/integrations/elasticsearch.rst:125 +msgid "Credentials" msgstr "" -#: ../system/objects/permissions.rst:55 -msgid "Editing dialog for already existing data" +#: ../system/integrations/elasticsearch.rst:127 +msgid "" +"Within this section Zammad displays your available users. The password is " +"provided once (upon activation) and cannot be retrieved after that." msgstr "" -#: ../system/objects/permissions.rst:56 -msgid "view" +#: ../system/integrations/elasticsearch.rst:131 +msgid "" +"If you need to change or reset your Elasticsearch user password, use the " +"\"Reset password\" button in the credentials table. Doing so creates a brand " +"new password for the account in question. This change is immediate, keep in " +"mind that this may affect third party tools connected to your instance." msgstr "" -#: ../system/objects/permissions.rst:62 -msgid "View-only dialog for already existing data" +#: ../system/integrations/exchange.rst:2 +msgid "Exchange" msgstr "" -#: ../system/objects/permissions.rst:64 -msgid "(e.g. user or organization from search)" +#: ../system/integrations/exchange.rst:4 +msgid "" +"With Zammad's Exchange integration, you can easily use existing address " +"books without having to update more than one source." msgstr "" -#: ../system/objects/permissions.rst:65 -msgid "signup" +#: ../system/integrations/exchange.rst:7 +msgid "" +"However, you should refrain from syncing all addresses, as the results may " +"not be what you expect (Exchange collects huge amounts of addresses). A " +"central address book of your company to sync makes more sense, as you can " +"ensure that Zammad gets only the data you need and want. Apart from this, it " +"is even not possible to sync the Global Address List (GAL) of your Exchange " +"system with Zammad." msgstr "" -#: ../system/objects/permissions.rst:67 -msgid "Sign-up screen for new customers" +#: ../system/integrations/exchange.rst:16 +msgid "" +"**Exchange and LDAP:** The exchange sync can be overruled by Zammad's LDAP " +"integration. If you have the same users in both sources, the LDAP version " +"will always be Zammad's pick." msgstr "" -#: ../system/objects/permissions.rst:68 -msgid "invite_customer" +#: ../system/integrations/exchange.rst:19 +msgid "" +"**One way sync:** the Exchange sync is one way. Exchange => Zammad. Changes " +"to your users inside of Zammad might be overwritten by the Exchange sync." msgstr "" -#: ../system/objects/permissions.rst:71 +#: ../system/integrations/exchange.rst:24 msgid "" -"Customer invitation screen (from :doc:`First Steps ` area)" +"To configure Exchange integration, simply go to the System > Integrations > " +"Exchange in the admin panel. Press \"change\" and follow the wizard for " +"adding the needed Exchange information to Zammad. On the last two steps " +"Zammad will ask you for the address book(s) and your desired attribute " +"mapping. By default, Zammad only maps email address, first- and lastname. " +"Technically, you can map any Exchange object to a Zammad user object (this " +"also works for custom objects!)." msgstr "" -#: ../system/objects/permissions.rst:72 -msgid "invite_agent" +#: ../system/integrations/exchange.rst:35 +msgid "" +"If the SSL verification fails while connecting to Exchange, Zammad will ask " +"you to turn it off temporarily." msgstr "" -#: ../system/objects/permissions.rst:74 +#: ../system/integrations/exchange.rst:38 msgid "" -"Agent invitation screen (from :doc:`First Steps ` area)" +"Please be aware that **turning off SSL verification is a security risk**. It " +"should only be used temporarily or for testing purposes. If turned off, " +"there is no verification of the certificate, which means that every " +"presented certificate will be accepted." msgstr "" -#: ../system/objects/permissions.rst:78 -msgid "Screen Options" +#: ../system/integrations/exchange.rst:43 +msgid "" +"After pressing Continue, Zammad will check if the configuration is okay. You " +"can then enable Exchange and start your first sync. The sync will then run " +"hourly - if you need to change mappings or the address book(s), you can " +"change the configuration at any time." msgstr "" -#: ../system/objects/permissions.rst:80 +#: ../system/integrations/exchange.rst:50 msgid "" -"For the different screens you can select \"show\" and \"required\" options." +"After the sync has finished, you can find the new Exchange contacts under " +"\"Users\". Zammad integrates them just as normal users." msgstr "" -#: ../system/objects/permissions.rst:82 -msgid "**shown:** Show (check) or hide (uncheck) a field." +#: ../system/integrations/exchange.rst:55 +msgid "" +"In some cases you might see unique IDs as \"Login\" instead of the email " +"address. This is normal and doesn't affect the login or email mapping for " +"that entry." msgstr "" -#: ../system/objects/permissions.rst:83 +#: ../system/integrations/github.rst:4 msgid "" -"**required:** Set a field to mandatory (check). Forces users (via UI and " -"API) to populate the field." +"Use GitHub integration to track GitHub issues directly within Zammad " +"tickets. Add issue hyperlinks and get a live summary of metadata like status " +"(open/closed), assignee, labels, and more." msgstr "" -#: ../system/objects/types.rst:7 -msgid "Example external data source" +#: ../system/integrations/github.rst:8 +msgid "Please note that our GitHub integration does not support pull requests." msgstr "" -#: ../system/objects/types.rst:2 -msgid "Attribute types" +#: ../system/integrations/github.rst:None +msgid "Integration page for GitHub" msgstr "" -#: ../system/objects/types.rst:4 +#: ../system/integrations/github.rst:18 msgid "" -"When adding a new object attribute, you can choose between the following " -"attribute types." +"In your GitHub settings, create a new API token under **Developer settings > " +"Personal access tokens > Generate new token**. Leave the **Scopes** section " +"empty." msgstr "" -#: ../system/objects/types.rst:14 -msgid "" -"You cannot change the attribute format / type as soon as it is applied. If " -"you no longer need an object attribute, consider disabling it instead of " -"removing." +#: ../system/integrations/github.rst:0 ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to create a new API token" msgstr "" -#: ../system/objects/types.rst:18 -msgid "**What about the translation of my attributes?**" +#: ../system/integrations/github.rst:27 +msgid "Create a new API key with no scopes/privileges." +msgstr "" + +#: ../system/integrations/github.rst:29 +msgid "🔒 **Will this work for private repos?**" +msgstr "" + +#: ../system/integrations/github.rst:31 +msgid "" +"No. To link private repo issues, **use the** ``repo`` **scope instead**. " +"Bear in mind that the resulting token will have `lots of permissions that it " +"doesn't actually need `_, which presents a security risk if your token ever falls into " +"the wrong hands." msgstr "" -#: ../system/objects/types.rst:20 +#: ../system/integrations/github.rst:37 msgid "" -"For some attribute types you can decide if they should be translatable or " -"not. To be precise, it works only for the selectable fields because the " -"possible choices are known and limited. For the following attribute types, " -"you can set the translatable flag:" +"Unfortunately, because of how GitHub's OAuth token scopes are set up, this " +"is the only way to link issues on private repos." msgstr "" -#: ../system/objects/types.rst:25 -msgid "*Boolean field*" +#: ../system/integrations/github.rst:40 +msgid "Enter your new API token in Zammad and enable GitHub integration." msgstr "" -#: ../system/objects/types.rst:26 -msgid "*Single selection field*" +#: ../system/integrations/github.rst:0 +msgid "Screencast showing how to configure Zammad's GitHub integration" msgstr "" -#: ../system/objects/types.rst:27 -msgid "*Multiple selection field*" +#: ../system/integrations/github.rst:47 +msgid "" +"Use the default API endpoint (``https://api.github.com/graphql``) unless " +"you're using GitHub Enterprise Server." msgstr "" -#: ../system/objects/types.rst:28 -msgid "*Single tree selection field*" +#: ../system/integrations/github.rst:50 +msgid "" +"Once completed, a new GitHub issues tab will appear in the ticket pane. 🎉" msgstr "" -#: ../system/objects/types.rst:29 -msgid "*Multiple tree selection field*" +#: ../system/integrations/github.rst:59 ../system/integrations/gitlab.rst:52 +msgid "Token verification is taking a long time" msgstr "" -#: ../system/objects/types.rst:31 +#: ../system/integrations/github.rst:56 ../system/integrations/gitlab.rst:49 msgid "" -"For these types, you can find an additional field *Translate field contents*:" -msgstr "" - -#: ../system/objects/types.rst:0 -msgid "Screenshot showing translatable attribute types" +"Slight delays are normal (<2 min.), especially for systems under heavy load." msgstr "" -#: ../system/objects/types.rst:38 -msgid "Screenshot with example of translatable attribute type" +#: ../system/integrations/github.rst:58 +msgid "" +"Self-hosted administrators, please check your network settings to ensure " +"that your Zammad server can reach ``api.github.com``." msgstr "" -#: ../system/objects/types.rst:45 -msgid "Boolean field" +#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 +msgid "I reloaded the page and now the API token is gone" msgstr "" -#: ../system/objects/types.rst:41 +#: ../system/integrations/github.rst:62 ../system/integrations/gitlab.rst:55 msgid "" -"Provides a drop-down field with display values for ``true`` and ``false``. " -"Setting a default is mandatory." +"This may indicate that Zammad is still verifying your API token. Try " +"reloading the page again in a couple minutes." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Boolean fields" +#: ../system/integrations/gitlab.rst:2 +msgid "GitLab" msgstr "" -#: ../system/objects/types.rst:55 -msgid "Date field" +#: ../system/integrations/gitlab.rst:4 +msgid "" +"Use GitLab integration to track GitLab issues directly within Zammad " +"tickets. Add issue hyperlinks and get a live summary of metadata like status " +"(open/closed), assignee, labels, and more." msgstr "" -#: ../system/objects/types.rst:48 -msgid "Provides a date picker field and does not allow default values." +#: ../system/integrations/gitlab.rst:8 +msgid "" +"Please note that our GitLab integration does not support merge requests." msgstr "" -#: ../system/objects/types.rst:52 -msgid "Default time diff (hours)" +#: ../system/integrations/gitlab.rst:None +msgid "Integration page for GitLab" msgstr "" -#: ../system/objects/types.rst:51 +#: ../system/integrations/gitlab.rst:18 msgid "" -"This setting helps the user by highlighting the day from now plus the " -"provided value. It *does not* pre-fill the field." -msgstr "" - -#: ../system/objects/types.rst:0 -msgid "Available settings for Date fields" +"In your GitLab preferences, create a new API token under **Access Tokens**." msgstr "" -#: ../system/objects/types.rst:73 -msgid "Date & time field" +#: ../system/integrations/gitlab.rst:20 +msgid "Under **Select scopes**, choose ``read_api`` only." msgstr "" -#: ../system/objects/types.rst:58 -msgid "Provides a date and time picker – does not allow default values" +#: ../system/integrations/gitlab.rst:27 +msgid "🔒 **If you wish to link issues on any private repos...**" msgstr "" -#: ../system/objects/types.rst:62 -msgid "Allow future" +#: ../system/integrations/gitlab.rst:29 +msgid "Your API token must belong to an account with access to those repos." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Forbid dates and times in the future." +#: ../system/integrations/gitlab.rst:31 +msgid "Enter your new API token in Zammad and enable GitLab integration." msgstr "" -#: ../system/objects/types.rst:66 -msgid "Allow past" +#: ../system/integrations/gitlab.rst:0 +msgid "Screencast showing how to configure Zammad's GitLab integration" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Forbid dates and times in the past." +#: ../system/integrations/gitlab.rst:40 +msgid "" +"Use the default API endpoint (``https://gitlab.com/api/graphql``) unless " +"you're a self-hosted GitLab user." msgstr "" -#: ../system/objects/types.rst:70 -msgid "Default time diff (minutes)" +#: ../system/integrations/gitlab.rst:43 +msgid "" +"Once completed, a new GitLab issues tab will appear in the ticket pane. 🎉" msgstr "" -#: ../system/objects/types.rst:69 +#: ../system/integrations/gitlab.rst:51 msgid "" -"This setting helps the user by highlighting the day from now plus the " -"provided value. It does not pre-fill the field." +"Self-hosted administrators, please check your network settings to ensure " +"that your Zammad server can reach ``gitlab.com``." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Date & time fields" +#: ../system/integrations/i-doit.rst:2 +msgid "i-doit" msgstr "" -#: ../system/objects/types.rst:86 -msgid "Integer field" +#: ../system/integrations/i-doit.rst:4 +msgid "" +"`i-doit `_ is an open-source **configuration " +"management database** - in other words, a tool for keeping tabs on every " +"single piece of your physical and digital infrastructure, from network " +"equipment to virtual machines on down to the faceplates on your rack shelves " +"and more." msgstr "" -#: ../system/objects/types.rst:76 +#: ../system/integrations/i-doit.rst:10 msgid "" -"Provides an input field that allows integer usage only. You may define a " -"default value. You cannot enforce comma separation." +"What's that got to do with Zammad? Well, if you used tickets to track issues " +"with all that hardware, you might start wishing there was a way they could " +"talk to each other." msgstr "" -#: ../system/objects/types.rst:80 -msgid "Minimal" +#: ../system/integrations/i-doit.rst:14 +msgid "Zammad gives you two:" msgstr "" -#: ../system/objects/types.rst:80 -msgid "The minimal value the field accepts." +#: ../system/integrations/i-doit.rst:17 +msgid "1. Add i-doit Links to Zammad Tickets" msgstr "" -#: ../system/objects/types.rst:83 -msgid "Maximal" +#: ../system/integrations/i-doit.rst:20 ../system/integrations/i-doit.rst:80 +msgid "What Users See" msgstr "" -#: ../system/objects/types.rst:83 -msgid "The maximum value the field accepts." +#: ../system/integrations/i-doit.rst:26 +msgid "i-doit integration in Zammad's ticket pane" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Integer fields" +#: ../system/integrations/i-doit.rst:26 +msgid "" +"The i-doit integration will appear under a new 🖨 tab in the ticket pane." msgstr "" -#: ../system/objects/types.rst:99 -msgid "Multiple selection field" +#: ../system/integrations/i-doit.rst:28 +msgid "" +"i-doit integration puts a new tab in Zammad's ticket pane where you can add " +"links to existing i-doit devices for easy reference. (See our :user-docs:" +"`user documentation ` to learn " +"how it works in practice)." msgstr "" -#: ../system/objects/types.rst:89 +#: ../system/integrations/i-doit.rst:36 ../system/integrations/i-doit.rst:93 +msgid "How to Set it Up" +msgstr "" + +#: ../system/integrations/i-doit.rst:38 msgid "" -"Provides a selection field that allows the selection of one or more out of " -"several. This field does allow setting a default value." +"It requires i-doit's `API Add-on `_. Make sure to have it properly set up. Use the following setting:" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Multiple selection fields" +#: ../system/integrations/i-doit.rst:42 +msgid "Active: ``Yes``" msgstr "" -#: ../system/objects/types.rst:112 -msgid "Single selection field" +#: ../system/integrations/i-doit.rst:43 +msgid "Enforce authentication by username and password: ``No``" msgstr "" -#: ../system/objects/types.rst:102 +#: ../system/integrations/i-doit.rst:45 msgid "" -"Provides a drop-down field that allows selection of one value out of " -"several. This field does allow setting a default value." +"To set it up, enable the integration in the Zammad admin panel under " +"**System > Integrations > i-doit**:" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Single selection fields" +#: ../system/integrations/i-doit.rst:None +msgid "i-doit settings within the integration pages" msgstr "" -#: ../system/objects/types.rst:142 -msgid "Textarea field" +#: ../system/integrations/i-doit.rst:53 +msgid "The root URL of your i-doit installation." msgstr "" -#: ../system/objects/types.rst:115 -msgid "" -"Provides a text area input field (multiple lines) and thus allows e.g. new " -"lines. You can set a default field value." +#: ../system/integrations/i-doit.rst:62 +msgid "API token" msgstr "" -#: ../system/objects/types.rst:120 +#: ../system/integrations/i-doit.rst:56 msgid "" -"Please note that this field *does not* support text formatting or HTML " -"content (rich text)." +"Found in the i-doit admin panel under **Interfaces / external data > JSON-" +"RPC API > Common Settings**." msgstr "" -#: ../system/objects/types.rst:123 -msgid "**🥵 This field can consume a lot of visual space**" +#: ../system/integrations/i-doit.rst:0 +msgid "i-doit administration interface with API configuration" msgstr "" -#: ../system/objects/types.rst:125 -msgid "" -"Depending on where you use this field type, it may use a lot of visual space " -"if you provide a lot of text. This may be an issue to work with." +#: ../system/integrations/i-doit.rst:67 +msgid "Client ID" msgstr "" -#: ../system/objects/types.rst:130 -msgid "Default" +#: ../system/integrations/i-doit.rst:65 +msgid "A unique name to identify Zammad within i-doit." msgstr "" -#: ../system/objects/types.rst:129 +#: ../system/integrations/i-doit.rst:67 +msgid "(Zammad does not require you to enter a value here, but i-doit might!)" +msgstr "" + +#: ../system/integrations/i-doit.rst:70 msgid "" -"The here provided text will be shown within the text area field or new data " -"sets." +"Here you can decide if the certificate of your i-doit system has to be " +"verified or not. In case you are using custom certificates, please have a " +"look at :doc:`how to add them to Zammad `." msgstr "" -#: ../system/objects/types.rst:134 ../system/objects/types.rst:160 -msgid "Maxlength" +#: ../system/integrations/i-doit.rst:77 +msgid "2. List / Create Zammad Tickets in i-doit" msgstr "" -#: ../system/objects/types.rst:0 ../system/objects/types.rst:160 -msgid "You can pick the maximum length of the field." +#: ../system/integrations/i-doit.rst:None +msgid "Zammad integration in i-doit's device view" +msgstr "" + +#: ../system/integrations/i-doit.rst:86 +msgid "" +"i-doit's ticket system integration gives you a way to see all the tickets " +"for a given device without ever leaving i-doit. (See our :user-docs:`user " +"documentation ` to learn how it " +"works in practice)." msgstr "" -#: ../system/objects/types.rst:0 -msgid "The default length of this object is ``500``." +#: ../system/integrations/i-doit.rst:95 +msgid "" +"Enable this integration in the i-doit admin panel under **Interfaces / " +"external data > Trouble Ticket System (TTS) > Configuration**:" msgstr "" -#: ../system/objects/types.rst:139 -msgid "Rows" +#: ../system/integrations/i-doit.rst:None +msgid "i-doit administration interface with TTS configuration" msgstr "" -#: ../system/objects/types.rst:0 -msgid "" -"Change the number of rows to dislay so that you can use only the space you " -"really need." +#: ../system/integrations/i-doit.rst:104 +msgid "TTS-Type" msgstr "" -#: ../system/objects/types.rst:0 -msgid "The default number of rows is ``4``." +#: ../system/integrations/i-doit.rst:104 +msgid "``Zammad``" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Textarea fields" +#: ../system/integrations/i-doit.rst:115 +msgid "Username / Password" msgstr "" -#: ../system/objects/types.rst:165 -msgid "Text field" +#: ../system/integrations/i-doit.rst:107 +msgid "Login credentials for a Zammad agent." msgstr "" -#: ../system/objects/types.rst:145 -msgid "Provides a text field (one line) and allows choosing a default value." +#: ../system/integrations/i-doit.rst:109 +msgid "" +"This agent must have **read permission** for all :doc:`groups ` that plan on using the i-doit integration." msgstr "" -#: ../system/objects/types.rst:148 +#: ../system/integrations/i-doit.rst:113 msgid "" -"Defines the type of the input field. This allows e.g. your browser to ensure " -"that you provide the specific type." +"You may even wish to create a dedicated agent account just for this " +"integration (otherwise, if the agent ever changes her password, you will " +"have to remember to update it here)." msgstr "" -#: ../system/objects/types.rst:152 -msgid "Currently available:" +#: ../system/integrations/i-doit.rst:117 +msgid "URL incl. protocol" msgstr "" -#: ../system/objects/types.rst:155 -msgid "Phone" +#: ../system/integrations/i-doit.rst:118 +msgid "``https://your.zammad.domain``" msgstr "" -#: ../system/objects/types.rst:156 -msgid "Text" +#: ../system/integrations/index.rst:2 +msgid "Integrations" msgstr "" -#: ../system/objects/types.rst:157 -msgid "Url *(URL fields disable link-template availability)*" +#: ../system/integrations/index.rst:4 +msgid "" +"Zammad offers numerous integrations that add rich features to your instance." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Text fields" +#: ../system/integrations/index.rst:6 +msgid "We're still working on this part of our documentation, stay tight!" msgstr "" -#: ../system/objects/types.rst:174 -msgid "Single tree selection field" +#: ../system/integrations/index.rst:10 +msgid "Integrations for Phone Systems" msgstr "" -#: ../system/objects/types.rst:168 +#: ../system/integrations/index.rst:14 msgid "" -"Provides a select-like field with up to 6 layers of options. Does not allow " -"setting a default value." +"Your VoIP provider or telephony system is not listed? Possibly your provider " +"supports Zammad by using the generic CTI - if you're unsure ask your " +"provider." msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for Tree Select fields" +#: ../system/integrations/index.rst:18 +msgid "" +"Provider does not support Zammad? Consider creating a `feature request in " +"the Zammad Community `_." msgstr "" -#: ../system/objects/types.rst:183 -msgid "Multiple tree selection field" +#: ../system/integrations/index.rst:31 +msgid "Integrations for Authentication and Customers" msgstr "" -#: ../system/objects/types.rst:177 -msgid "" -"Provides a select-like field with up to 6 layers of options allowing the " -"selection of multiple values. Does not allow setting a default value." +#: ../system/integrations/index.rst:44 +msgid "Integrations for Monitoring Systems" msgstr "" -#: ../system/objects/types.rst:302 -msgid "External Data Source field" +#: ../system/integrations/index.rst:46 +msgid "This section currently misses the following integrations:" msgstr "" -#: ../system/objects/types.rst:186 -msgid "" -"Provides a searchable field which fetches data from an external system. This " -"can be useful if you have data outside of Zammad and don't want to maintain " -"both data sources." +#: ../system/integrations/index.rst:48 +msgid "Icinga" msgstr "" -#: ../system/objects/types.rst:190 -msgid "The feature works as follows:" +#: ../system/integrations/index.rst:49 +msgid "Monit" msgstr "" -#: ../system/objects/types.rst:192 -msgid "" -"Zammad sends a query with a search string (free text from agent or based on " -"a variable) in a pre-defined format (\"Search URL\") to an external system." +#: ../system/integrations/index.rst:50 +msgid "Nagios" msgstr "" -#: ../system/objects/types.rst:195 -msgid "" -"This external system searches for matches and provides a response as a JSON " -"structure to Zammad." +#: ../system/integrations/index.rst:60 +msgid "Integrations for Issue Trackers" msgstr "" -#: ../system/objects/types.rst:197 -msgid "" -"Zammad just looks for the defined list and value keys, reads the content and " -"displays the value to the user. There is no search on Zammad side." +#: ../system/integrations/index.rst:70 +msgid "Other Integrations" msgstr "" -#: ../system/objects/types.rst:201 +#: ../system/integrations/index.rst:72 msgid "" -"The usage of a PostgreSQL database for Zammad is required. In any other " -"case, Zammad will hide the external data source type and you are not able to " -"use it. If you want to use this feature, consider to :docs:`migrate your " -"database `." +"This section will hold any other integration that can't be grouped up (yet)." msgstr "" -#: ../system/objects/types.rst:205 -msgid "Currently, only ``GET`` is supported as request method." +#: ../system/integrations/ldap/index.rst:2 +msgid "LDAP / Active Directory" msgstr "" -#: ../system/objects/types.rst:206 +#: ../system/integrations/ldap/index.rst:4 msgid "" -"The data structure must be in JSON format and provide the objects in an " -"array." +"Zammad comes with a powerful LDAP integration that allows you to have a " +"single source of truth. By this you reduce the number of login credentials " +"your user has to remember." msgstr "" -#: ../system/objects/types.rst:208 +#: ../system/integrations/ldap/index.rst:10 msgid "" -"The endpoint for the external data source has to support search. On Zammad " -"side, there is no search/logic implemented; however, you can define the " -"output key and value based on the result(s) from the response (which " -"provides already filtered content based on the search)." +"The LDAP source is also a perfect candidate for Zammad's :docs:`Kerberos " +"Single Sign-On ` but also works as addition " +"to other :doc:`/settings/security/third-party`." msgstr "" -#: ../system/objects/types.rst:212 -msgid "" -"If you receive more results as expected, your external data source search " -"may not work properly or the structure of the URL is not correct. You should " -"get in touch with a responsible person from the external system." +#: ../system/integrations/ldap/index.rst:None +msgid "Zammands LDAP management page" msgstr "" -#: ../system/objects/types.rst:217 -msgid "" -"Please have a look :doc:`at our example `, where you can find a possible configuration for a public " -"dummy endpoint." +#: ../system/integrations/ldap/index.rst:25 +msgid "📝 :doc:`manage`" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Available settings for external data source fields" +#: ../system/integrations/ldap/index.rst:25 +msgid "Add, modify, remove or re-arrange your LDAP-Sources as needed." msgstr "" -#: ../system/objects/types.rst:242 -msgid "Search URL" +#: ../system/integrations/ldap/index.rst:30 +msgid "Before you continue, please note the following limitations." msgstr "" -#: ../system/objects/types.rst:227 -msgid "" -"Set your endpoint where Zammad fetches the data. Please make sure to include " -"a valid search :doc:`variable <../variables>` as an URL parameter. Example " -"for a free text search at user input: ``#{search.term}``" +#: ../system/integrations/ldap/index.rst:32 +msgid "Mapping / Synchronizing organizations is not possible" msgstr "" -#: ../system/objects/types.rst:232 +#: ../system/integrations/ldap/index.rst:36 msgid "" -"If in doubt, ask the responsible person for the external data source how " -"they expect the strucuture of the URL." +"You may want to consider using domain based assignments to overcome this " +"issue. Learn more on :doc:`/manage/organizations/index`." msgstr "" -#: ../system/objects/types.rst:236 +#: ../system/integrations/ldap/index.rst:39 msgid "" -"Depending on your search variable, the preview might work or not. The reason " -"is that the context might not be available and it is no bug." +"Zammad's LDAP sync is one way. Editing user settings or permissions may be " +"overwritten upon the next sync depending on your configuration." msgstr "" -#: ../system/objects/types.rst:239 -msgid "" -"Please also make sure to use a variable which is available in your object " -"context. For example you won't be able to search for a ticket in a user " -"object context." +#: ../system/integrations/ldap/index.rst:41 +msgid "Nested groups are not supported." msgstr "" -#: ../system/objects/types.rst:252 -msgid "SSL Verification" +#: ../system/integrations/ldap/index.rst:42 +msgid "Synchronizing user avatars from LDAP is not supported." msgstr "" -#: ../system/objects/types.rst:245 -msgid "Here you can switch the SSL verification to no." +#: ../system/integrations/ldap/index.rst:43 +msgid "Unlike user filters, group filters cannot be changed." msgstr "" -#: ../system/objects/types.rst:249 +#: ../system/integrations/ldap/index.rst:44 msgid "" -"If your external data source system is using self signed certificates, " -"please have a look :doc:`here ` for " -"further information about how to handle them in Zammad, so you can keep the " -"SSL verification activated." -msgstr "" - -#: ../system/objects/types.rst:258 -msgid "HTTP Authentication" +"When a user originates from an LDAP server, Zammad will try to verify the " +"login credentials against LDAP first - if this fails Zammad will check its " +"local database." msgstr "" -#: ../system/objects/types.rst:255 +#: ../system/integrations/ldap/index.rst:50 msgid "" -"If your external data source requires an authentication, you can set it " -"here. You can leave it empty or choose between *Basic Authentication* or " -"*Authentication Token* (selecting one of the two methods leads to additional " -"fields where you can enter your credentials/token)." -msgstr "" - -#: ../system/objects/types.rst:265 -msgid "Search result list key" +"Users can have local passwords even if they're LDAP users! You can learn " +"more about user accounts in general on :doc:`/manage/users/index`." msgstr "" -#: ../system/objects/types.rst:261 +#: ../system/integrations/ldap/index.rst:54 msgid "" -"Defines the level in the JSON structure which provides the list with search " -"results. You can leave it empty, if the data is already provided as an " -"array. If you have to go deeper in the structure, you can provide a path " -"with ``.`` as separators, e.g. ``key.subkey.sub-sub-key``." -msgstr "" - -#: ../system/objects/types.rst:271 -msgid "Search result value key" +"When several LDAP sources contain the same user (meaning the same email " +"address), the user in question will be updated with every source configured. " +"*The last LDAP source will win.*" msgstr "" -#: ../system/objects/types.rst:268 +#: ../system/integrations/ldap/index.rst:58 msgid "" -"Defines the attribute in the structure in which your external data source " -"provides the *value* for your data. An example would be a product *number*. " -"If you have to go deeper in the structure, you can provide a path with ``.`` " -"as separators, e.g. ``key.subkey.sub-sub-key``." +"This is subject to change with `Issue 4109 `_ in the future." msgstr "" -#: ../system/objects/types.rst:277 -msgid "Search result label key" +#: ../system/integrations/ldap/index.rst:60 +msgid "" +"Synchronization statistics currently affect *all* configured LDAP sources. " +"This also applies for newly added or updated sources." msgstr "" -#: ../system/objects/types.rst:274 +#: ../system/integrations/ldap/index.rst:63 msgid "" -"Defines the attribute in the structure in which your external data source " -"provides the *label* for your data. An example would be a product *name*. If " -"you have to go deeper in the structure, you can provide a path with ``.`` as " -"separators, e.g. ``key.subkey.sub-sub-key``." +"This is subject to change with `Issue 4108 `_ in the future." msgstr "" -#: ../system/objects/types.rst:280 +#: ../system/integrations/ldap/index.rst:65 msgid "" -"In the preview area, you can find the following items (depending on your " -"configuration above):" +"Zammad currently has limited fallback server support. You can workaround " +"this by providing several sources - however, ensure to have the exact same " +"configuration on your fallback." msgstr "" -#: ../system/objects/types.rst:283 +#: ../system/integrations/ldap/index.rst:69 msgid "" -"**Error/hint message** (only if configuration is not complete): Zammad tells " -"you, if there is a problem and what you should change in your configuration." +"This is subject to improve with `Issue 4107 `_ in the future." msgstr "" -#: ../system/objects/types.rst:286 +#: ../system/integrations/ldap/index.rst:76 msgid "" -"**Search field**: search for an existing attribute in the data source to get " -"a preview. This is required for the fields below to show up." +"This section holds all requests Zammad handled for all LDAP sources. These " +"entries can either contain synchronization information or logins " +"(authentication attempts via Zammad's login interface)." msgstr "" -#: ../system/objects/types.rst:288 +#: ../system/integrations/ldap/index.rst:80 msgid "" -"**Search result response** (only if configuration is not complete): here you " -"can find a syntax highlighted JSON preview of the response, based on the " -"search term you entered." +"By clicking on any request, Zammad will provide even more information. The " +"provided information can be useful when something does not work as expected." msgstr "" -#: ../system/objects/types.rst:291 +#: ../system/integrations/ldap/index.rst:85 msgid "" -"**Search result list** (only if *search result list key* is properly set): " -"output of the structure under the configured *search result list key*." +"Especially a LDAP synchronization can cause many log entries. The web " +"interface will always limit the number of shown entries to the last 50 " +"entries." msgstr "" -#: ../system/objects/types.rst:294 +#: ../system/integrations/ldap/index.rst:None msgid "" -"**Preview table** (when fully configured): Zammad shows you a table which " -"includes the found items based on the search string (value, label and " -"optional link). You can use this preview if you don't have the complete data " -"structure of the external system in mind." +"Screencast showing LDAP integration log entries and a detail view on\n" +"an entry." msgstr "" -#: ../system/objects/types.rst:299 -msgid "" -"An example of a configured external data source field from agent perspective:" +#: ../system/integrations/ldap/manage.rst:2 +msgid "Manage LDAP-Sources" msgstr "" -#: ../system/objects/types.rst:0 -msgid "Screencast showing the search for a product in a ticket" +#: ../system/integrations/ldap/manage.rst:6 +msgid "" +"Please keep in mind all current limitations for the LDAP synchronization. " +"This will help to understand scopes of the following operations better." msgstr "" -#: ../system/objects/types.rst:307 -msgid "URL fields (Link-Template)" +#: ../system/integrations/ldap/manage.rst:65 +msgid "Add new source" msgstr "" -#: ../system/objects/types.rst:311 +#: ../system/integrations/ldap/manage.rst:10 msgid "" -"This function is restricted to Text, Select and External data source types " -"only." +"Using the *New Source* button allows you to add new LDAP sources to your " +"installation. You're not limited in the number of sources, however, keep in " +"mind that many sources will also take more time to synchronize." msgstr "" -#: ../system/objects/types.rst:314 +#: ../system/integrations/ldap/manage.rst:14 msgid "" -"Link-Templates are an amazing way to dynamically generate URLs. They allow " -"you to integrate other systems better without having to manually copy data " -"from Zammad if possible." +"You can choose between different encryption types, namely *SSL* and " +"*STARTTLS* or none of them (\"*No SSL*\"). If you choose *SSL* or " +"*STARTTLS*, Zammad will display an additional *SSL verification* option that " +"allows you to disable the verification, e.g. for self-signed SSL " +"certificates. You can also tell Zammad to use a different port by appending " +"``:`` to your hostname/IP." msgstr "" -#: ../system/objects/types.rst:320 +#: ../system/integrations/ldap/manage.rst:0 msgid "" -"Another great way of communicating with another system may be Zammad's :doc:" -"`Webhooks `." +"Screenshot of configuring a new LDAP source with SSL encryption and SSL " +"verification" msgstr "" -#: ../system/objects/types.rst:323 +#: ../system/integrations/ldap/manage.rst:26 msgid "" -"After filling a link-template enabled field, an URL icon will appear on its " -"right. Clicking on the icon opens a new tab." +"New Source with SSL transport security enabled and certificate verification" msgstr "" -#: ../system/objects/types.rst:328 +#: ../system/integrations/ldap/manage.rst:30 msgid "" -"Even though Zammad displays the link template within object edit and create " -"screens, the function is optional. It's only active if you populate the " -"field." +"Using an user filter can be a good idea if you only require a small subset " +"of your LDAP users in Zammad." msgstr "" -#: ../system/objects/types.rst:333 -msgid "" -"What's the difference between URL and text fields with link template...?!" +#: ../system/integrations/ldap/manage.rst:42 +msgid "This especially affects inactive users" msgstr "" -#: ../system/objects/types.rst:335 +#: ../system/integrations/ldap/manage.rst:34 msgid "" -"Both fields have different use cases. Use ``text`` type text fields when " -"ever you have a *static* url that requires dynamic parameters. If you " -"require a drag & drop like field that you can put in any URL, use ``URL`` " -"type text fields." +"As every LDAP behaves differently on which attributes and how they are set, " +"Zammad doesn't care about any flags." msgstr "" -#: ../system/objects/types.rst:340 +#: ../system/integrations/ldap/manage.rst:37 msgid "" -"The difference is easier to spot when comparing the fields directly, below " -"screencast shows the result - the dynamic approach uses existing values in " -"the moment of updating to built the URL - e.g. ``https://google.com/search?" -"q=cookies`` - while the URL approach uses the actual URL of the field - e.g. " -"``https://zammad.com``." +"Users that no longer are returned by your LDAP source will automatically be " +"set to inactive. Zammad assumes that the user was deactivated." msgstr "" -#: ../system/objects/types.rst:None +#: ../system/integrations/ldap/manage.rst:41 msgid "" -"Screencast showing the differents in between URL and text type fields with " -"actual values" +"Users will never be removed automatically! If you want to remove obsolete " +"users, use :doc:`/system/data-privacy`." msgstr "" -#: ../system/objects/types.rst:352 -msgid "How does this work...?!" +#: ../system/integrations/ldap/manage.rst:46 +msgid "Active Directory admins" msgstr "" -#: ../system/objects/types.rst:354 +#: ../system/integrations/ldap/manage.rst:45 msgid "" -"As an example, let's say you have an attribute called ``amazing_attribute`` " -"and you want to open a google search directly with the input from that field." +"Active Directories are quite specific on how to filter for active users only " +"- please see the `Microsoft documentation `_ for more " +"information." msgstr "" -#: ../system/objects/types.rst:357 +#: ../system/integrations/ldap/manage.rst:51 msgid "" -"Providing the link-template field below allows you to do so: ``https://www." -"google.com/search?q=#{ticket.amazing_attribute}``" +"*Do not* manually write pathes of either LDAP attributes or groups. If " +"Zammad does not display them, it either cannot find them or you have a lot " +"of users that don't have the attributes populated." msgstr "" -#: ../system/objects/types.rst:362 +#: ../system/integrations/ldap/manage.rst:55 msgid "" -"You can use any :doc:`Zammad variable ` as long as it's " -"available in the moment you need it." +"Zammad will always only return attributes that are filled - this reduces the " +"returned list of attributes greatly." msgstr "" -#: ../system/objects/types.rst:365 -msgid "" -"As a result, you are redirected to Google with a search for the value of the " -"attribute, if you click on the button in the ticket (as you can see in the " -"screencast above)." +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing how to add a new LDAP source" msgstr "" -#: ../system/packages.rst:2 -msgid "Packages" +#: ../system/integrations/ldap/manage.rst:63 +msgid "" +"If your LDAP system doesn't allow anonymous bind, Zammad detects it and " +"provides you an editable \"Base DN\" *text* field instead of a prefilled " +"*select* field." msgstr "" -#: ../system/packages.rst:4 -msgid "That's the package management-area." +#: ../system/integrations/ldap/manage.rst:81 +msgid "Review or edit existing source" msgstr "" -#: ../system/packages.rst:6 -msgid "Individual add-ons for Zammad can be installed and managed here." +#: ../system/integrations/ldap/manage.rst:68 +msgid "" +"Clicking on a LDAP source will provide a configuration and mapping overview." msgstr "" -#: ../system/sessions.rst:2 -msgid "Sessions" +#: ../system/integrations/ldap/manage.rst:70 +msgid "" +"If needed you can then use the *Change* button to update either the name, " +"active state or the whole configuration. If you're changing the whole " +"configuration, the dialogue will be identical to the source creation." msgstr "" -#: ../system/sessions.rst:4 +#: ../system/integrations/ldap/manage.rst:76 msgid "" -"Sessions management allows reviewing currently known user sessions and " -"allows to end these. The session timeout is affected by :ref:" -"`security_session_timeout` configurations from security settings." +"Did your LDAP server change? Different LDAP servers have different " +"structures and default attributes. This causes the LDAP synchronization to " +"likely fail. Consider removing the affected source and re-add it." msgstr "" -#: ../system/sessions.rst:None -msgid "Screenshot showing Zammad's session management" +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing the update of the source name." msgstr "" -#: ../system/sessions.rst:13 -msgid "Zammad will provide the following information:" +#: ../system/integrations/ldap/manage.rst:89 +msgid "Re-arrange LDAP source's order" msgstr "" -#: ../system/sessions.rst:16 +#: ../system/integrations/ldap/manage.rst:84 msgid "" -"The user account this session entry belongs to. It can be normal if a user " -"has several sessions in the list. This can be due to changed browser " -"information or if you use e.g. single sign on methods where the user does " -"not use the log off button." +"You can change the synchronization order for each source at any time. Zammad " +"will synchronize the sources from top to bottom." msgstr "" -#: ../system/sessions.rst:22 -msgid "Browser" +#: ../system/integrations/ldap/manage.rst:0 +msgid "" +"Screencasting showing how to change the source order by using\n" +"drag and drop." msgstr "" -#: ../system/sessions.rst:22 -msgid "The browser agent communicated to Zammad." +#: ../system/integrations/ldap/manage.rst:101 +msgid "Remove a source" msgstr "" -#: ../system/sessions.rst:40 -msgid "Location" +#: ../system/integrations/ldap/manage.rst:92 +msgid "" +"If you no longer need the a LDAP source or simply want to start over, you " +"can remove them at any time. This will not remove synchronized users, data " +"synchronized or permissions." msgstr "" -#: ../system/sessions.rst:25 +#: ../system/integrations/ldap/manage.rst:98 msgid "" -"The anticipated location based on the users IP address. Depending on the IP " -"address the result shown may differ. This option depends on :doc:`/settings/" -"system/services`." +"Not sure if you'd need the source later on? Set the source to inactive " +"instead of removing it - see *Review or edit existing source* for more." msgstr "" -#: ../system/sessions.rst:29 -msgid "The following information can be shown:" +#: ../system/integrations/ldap/manage.rst:0 +msgid "Screencast showing how to remove LDAP sources." msgstr "" -#: ../system/sessions.rst:33 -msgid "IP address" +#: ../system/integrations/pgp/index.rst:2 +msgid "PGP" msgstr "" -#: ../system/sessions.rst:32 +#: ../system/integrations/pgp/index.rst:7 msgid "" -"Either if you set *Geo IP services* to inactive or you're using internal IP " -"address which do not provide location information." +"Pretty Good Privacy (PGP) is another method for secure email communication. " +"With PGP, you can exchange **signed** and **encrypted** messages with others." msgstr "" -#: ../system/sessions.rst:40 -msgid "Country (or Country + City)" +#: ../system/integrations/pgp/index.rst:13 +#: ../system/integrations/smime/index.rst:17 +msgid "Signing" +msgstr "" + +#: ../system/integrations/pgp/index.rst:11 +msgid "is a proof that a message hasn't been manipulated on its way." msgstr "" -#: ../system/sessions.rst:36 +#: ../system/integrations/pgp/index.rst:13 msgid "" -"If *Geo IP services* is enabled only. Depends on how detailed the available " -"IP address information are." +"In other words, it guarantees message **integrity** and **authenticity**." msgstr "" -#: ../system/sessions.rst:39 -msgid "" -"Be aware that results can be inaccurate - this technically is not an error." +#: ../system/integrations/pgp/index.rst:19 +#: ../system/integrations/smime/index.rst:22 +msgid "Encryption" msgstr "" -#: ../system/sessions.rst:43 -msgid "Age" +#: ../system/integrations/pgp/index.rst:16 +#: ../system/integrations/smime/index.rst:20 +msgid "" +"scrambles a message so that it can only be unscrambled by the intended " +"recipient." msgstr "" -#: ../system/sessions.rst:43 -msgid "Provides the time when the session initially has been created." +#: ../system/integrations/pgp/index.rst:19 +msgid "" +"In other words, it guarantees message **privacy** and **data security**." msgstr "" -#: ../system/sessions.rst:50 -msgid "Update" +#: ../system/integrations/pgp/index.rst:25 +msgid "Screenshot of ticket creation with encrypt and sign buttons" msgstr "" -#: ../system/sessions.rst:46 +#: ../system/integrations/pgp/index.rst:25 msgid "" -"Provides the time the user used this session to open Zammad. This timestamp " -"is only updated if the user e.g. reloads, not during normal work on tickets." +"Once PGP has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " +"appear in the ticket composer." msgstr "" -#: ../system/sessions.rst:50 -msgid "This timestamp is being used for the session timeout." +#: ../system/integrations/pgp/index.rst:28 +msgid "**Sign button not visible?**" msgstr "" -#: ../system/sessions.rst:53 +#: ../system/integrations/pgp/index.rst:30 msgid "" -"Use the delete button to remove a single session on behalf of your user." +"Please note that the signing of emails is based on the outgoing email " +"account. That means you have to choose a group with a sender email account, " +"which has a private key assigned." msgstr "" -#: ../system/subscription/billing.rst:2 -msgid "Billing" +#: ../system/integrations/pgp/index.rst:35 +msgid "Handling of Keys" msgstr "" -#: ../system/subscription/billing.rst:4 +#: ../system/integrations/pgp/index.rst:36 msgid "" -"Within the billing tab you can control all billing relevant information like " -"invoices, billing address and the option to cancel your subscription." -msgstr "" - -#: ../system/subscription/billing.rst:33 -msgid "Billing information" +"To use the PGP function, you have to enable the integration (PGP) by " +"switching the toggle to *enabled*." msgstr "" -#: ../system/subscription/billing.rst:8 +#: ../system/integrations/pgp/index.rst:39 msgid "" -"All adjusted billing information below only affect future invoices. If your " -"invoice was issued wrong, please contact `our sales team `_." +"You can add keys by clicking the *add key* button. The keys can be imported " +"from a file or you can paste the content of the key in the text box." msgstr "" -#: ../system/subscription/billing.rst:14 -msgid "Billing address" +#: ../system/integrations/pgp/index.rst:42 +msgid "**Which keys do I have to import?**" msgstr "" -#: ../system/subscription/billing.rst:13 +#: ../system/integrations/pgp/index.rst:44 msgid "" -"Provide your company address here, make sure to include the companies name " -"in case required. This address will be referenced on your invoice." +"For **signing** *outgoing* emails, you have to import the private key of " +"your Zammad email account." msgstr "" -#: ../system/subscription/billing.rst:18 -msgid "VAT ID" +#: ../system/integrations/pgp/index.rst:47 +msgid "" +"For **encrypting** *outgoing* emails, you have to import the public key of " +"the customer's email account." msgstr "" -#: ../system/subscription/billing.rst:17 +#: ../system/integrations/pgp/index.rst:50 msgid "" -"Provide your VAT ID here. If applicable your invoice will not contain German " -"VAT. Please make sure to pay the VAT in your country as required." +"For **verifying the signature** of signed *incoming* emails, you have to " +"import the public key of the customer." msgstr "" -#: ../system/subscription/billing.rst:27 -msgid "Billing Email Address" +#: ../system/integrations/pgp/index.rst:53 +msgid "" +"For **decrypting** of encrypted *incoming* emails, you have to import the " +"private key of your Zammad email account." msgstr "" -#: ../system/subscription/billing.rst:21 -msgid "" -"Usually the instance owner (the person that registered the instance) will " -"receive all emails including the invoices. In case you have your own billing " -"department, you can provide their email address here." +#: ../system/integrations/pgp/index.rst:57 +msgid "Import Keys From a File" msgstr "" -#: ../system/subscription/billing.rst:25 -msgid "" -"All billing relevant information will then be sent to this email address." +#: ../system/integrations/pgp/index.rst:58 +msgid "You can import keys from a file in the section **Upload key**:" msgstr "" -#: ../system/subscription/billing.rst:27 -msgid "Invoices are sent as attachment (PDF) to this email address." +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of adding a key via file" msgstr "" -#: ../system/subscription/billing.rst:29 +#: ../system/integrations/pgp/index.rst:64 msgid "" -"Don't forget to press the *Submit* button after you changed above settings." +"**Supported file formats:** ASCII-armor as well as binary GPG format " +"(basically any GPG supported key format) is supported here." msgstr "" -#: ../system/subscription/billing.rst:0 -msgid "" -"Screenshot showing options for billing information within the\n" -"subscription menu" +#: ../system/integrations/pgp/index.rst:68 +msgid "Import Keys by Pasting the Content" msgstr "" -#: ../system/subscription/billing.rst:70 -msgid "Payment history" +#: ../system/integrations/pgp/index.rst:69 +msgid "You can also paste the key's content in the section **paste key**:" msgstr "" -#: ../system/subscription/billing.rst:36 -msgid "" -"The payment history will display a history of all paid invoices. At this " -"point you can also download these in case you need them again." +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of adding a key via pasting" msgstr "" -#: ../system/subscription/billing.rst:41 +#: ../system/integrations/pgp/index.rst:75 msgid "" -"You will only find *paid* invoices here. Invoices that are to be billed are " -"not available before the payment is completed." +"**Supported format:** Please note that only ASCII-armor is supported here." msgstr "" -#: ../system/subscription/billing.rst:46 -msgid "Date" +#: ../system/integrations/pgp/index.rst:78 +msgid "Deleting Keys" msgstr "" -#: ../system/subscription/billing.rst:46 -msgid "Date of the invoice creation." +#: ../system/integrations/pgp/index.rst:79 +msgid "" +"If you want to delete a specific key, you can do it by clicking on the menu " +"in the *actions* column and select **delete**:" msgstr "" -#: ../system/subscription/billing.rst:49 -msgid "Amount" +#: ../system/integrations/pgp/index.rst:None +msgid "Screenshot of deleting a key" msgstr "" -#: ../system/subscription/billing.rst:49 -msgid "Invoice total including VAT if applicable." +#: ../system/integrations/pgp/index.rst:88 +msgid "Downloading Keys" msgstr "" -#: ../system/subscription/billing.rst:52 +#: ../system/integrations/pgp/index.rst:89 msgid "" -"Contains contract period (monthly or yearly) and hosted plan for the " -"subscription period in question." -msgstr "" - -#: ../system/subscription/billing.rst:63 -msgid "Payment method / Service period" +"If you want to download your keys, you can do this as well via corresponding " +"action buttons. Depending on the key, you can choose wether you want to " +"download the private or the public key." msgstr "" -#: ../system/subscription/billing.rst:56 -msgid "" -"Used bank account or credit card as well as the subscription period the " -"invoice is about." +#: ../system/integrations/pgp/index.rst:95 +#: ../system/integrations/smime/manage-certificates.rst:76 +msgid "Default Behavior" msgstr "" -#: ../system/subscription/billing.rst:61 +#: ../system/integrations/pgp/index.rst:96 msgid "" -"It might happen that the invoice date and subscription period differ. This " -"is nothing to worry about, the subscription periods will be accounted later " -"on." +"Here you can adjust on per group basis, if *sign* and *encryption* is on or " +"off by default. Please be aware, that agents can always override the setting " +"for each individual article." msgstr "" -#: ../system/subscription/billing.rst:67 -msgid "Receipt" +#: ../system/integrations/pgp/index.rst:None +msgid "Adjusting default behavior on per group basis" msgstr "" -#: ../system/subscription/billing.rst:66 +#: ../system/integrations/pgp/index.rst:107 msgid "" -"Use the arrow to download the invoice in question. You can download all " -"available invoices any time you need to here!" +"Here you can see the last actions regarding signing and encryption and if " +"they were successful." msgstr "" -#: ../system/subscription/billing.rst:0 -msgid "Screenshot showing payment history of a hosted instance" +#: ../system/integrations/pgp/index.rst:117 +msgid "**Sign button is not visible, but keys are imported.**" msgstr "" -#: ../system/subscription/billing.rst:94 -msgid "Do you want to cancel your subscription?" +#: ../system/integrations/pgp/index.rst:115 +msgid "Did you choose a group in the ticket?" msgstr "" -#: ../system/subscription/billing.rst:73 +#: ../system/integrations/pgp/index.rst:116 msgid "" -"In case you no longer want to use Zammad's SaaS, you can cancel your " -"subscription by using the red *Yes, please cancel my subscription* button." +"Did you import a private key for the email adress, which is used for " +"outgoing emails in the group?" msgstr "" -#: ../system/subscription/billing.rst:76 -msgid "" -"Your subscription will end the day after your trial or billing period ends." +#: ../system/integrations/pgp/index.rst:122 +msgid "**How to obtain keys?**" msgstr "" -#: ../system/subscription/billing.rst:80 +#: ../system/integrations/pgp/index.rst:120 msgid "" -"We will remind you about your cancelled subscription several times up front. " -"After the subscription ended all instance data will be removed. A restore " -"*is not* possible after that point!" +"You can create them yourself! There are some good tutorials on the web on " +"how to create them. Providing keys to Zammad is a prerequisite to use the " +"PGP feature." msgstr "" -#: ../system/subscription/billing.rst:0 -msgid "Screencast showing how to cancel a subscription" +#: ../system/integrations/pgp/index.rst:127 +msgid "**It says a passphrase is needed, but I haven't got one.**" msgstr "" -#: ../system/subscription/billing.rst:87 -msgid "**😖 Cancelled by accident?**" +#: ../system/integrations/pgp/index.rst:125 +msgid "" +"If the key is secured with a passphrase, you have to provide it for the " +"import in Zammad. It is possible that keys may have an empty passphrase. " +"However, this is *not* recommended." msgstr "" -#: ../system/subscription/billing.rst:89 -msgid "" -"You can always undo the cancellation via the *Yes, undo the cancellation of " -"my subscription* button up to the last subscription day!" +#: ../system/integrations/pgp/index.rst:132 +msgid "**How do my customers get my new key?**" msgstr "" -#: ../system/subscription/billing.rst:0 +#: ../system/integrations/pgp/index.rst:130 msgid "" -"Screenshot showing a red button to cancel the subscription\n" -"cancellation" +"You have to provide your **public** key in advance. Your customer also has " +"to configure PGP in their email workflow and import your public key. The " +"other way round, you have to get the public key of your customer and have to " +"import it to Zammad." msgstr "" -#: ../system/subscription/index.rst:2 -msgid "Subscription (SaaS)" +#: ../system/integrations/slack.rst:2 +msgid "Slack" msgstr "" -#: ../system/subscription/index.rst:4 -msgid "" -"The subscription settings page allows you to configure your instances " -"package and number of agents required." +#: ../system/integrations/slack.rst:4 +msgid "**⚠️ Deprecation warning ⚠️**" msgstr "" -#: ../system/subscription/index.rst:9 +#: ../system/integrations/slack.rst:6 msgid "" -"This setting section is only available for Hosted setups. If you're looking " -"for on premise support contracts, please see the `Zammad pricing page " -"`_." +"Zammad 7 will no longer support this dedicated Slack integration. It is " +"recommended to switch to :doc:`pre-defined webhooks ` instead. Existing Slack integrations should " +"be migrated manually before this feature is dropped." msgstr "" -#: ../system/subscription/index.rst:20 +#: ../system/integrations/slack.rst:14 msgid "" -"The subscription section currently consists of two tabs: Plan & Billing. For " -"your overview we've divided those two tabs into independent sub pages:" +"In order to use this feature, please add a new Slack app to your Workspace. " +"The App you need is called ``Incoming WebHooks`` ." msgstr "" -#: ../system/subscription/index.rst:25 -msgid ":doc:`💰 Subscription plan `" +#: ../system/integrations/slack.rst:18 +msgid "Why Do I Need This Feature?" msgstr "" -#: ../system/subscription/index.rst:24 +#: ../system/integrations/slack.rst:20 msgid "" -"Everything affecting your instance subscription functions like number of " -"agents, package and payment method." +"If you're already using Slack for your team communication, you'll love this " +"feature! Our Slack integration can push ticket notifications about the last " +"ticket article based on the following events:" msgstr "" -#: ../system/subscription/index.rst:28 -msgid ":doc:`🧾 Subscription billing `" +#: ../system/integrations/slack.rst:24 +msgid "on Ticket creation" msgstr "" -#: ../system/subscription/index.rst:28 -msgid "" -"Everything regarding billing address, invoices and account cancellation." +#: ../system/integrations/slack.rst:25 +msgid "on Ticket updates" msgstr "" -#: ../system/subscription/index.rst:33 -msgid "FAQ" +#: ../system/integrations/slack.rst:26 +msgid "on reached reminders" msgstr "" -#: ../system/subscription/index.rst:37 -msgid "I set up a trial account but am missing functions to test" +#: ../system/integrations/slack.rst:27 +msgid "a Ticket has escalated" +msgstr "" + +#: ../system/integrations/slack.rst:28 +msgid "a Ticket is going to escalate" msgstr "" -#: ../system/subscription/index.rst:36 +#: ../system/integrations/slack.rst:30 msgid "" -"The trial instance is running within the professional package allowing up to " -"three agents." +"Zammad will provide the Ticket title, a direct link to the Ticket, the event " +"type (creation, updated, escalation), the customer, time and the last " +"article that has triggered the notification." msgstr "" -#: ../system/subscription/index.rst:40 -msgid "Can I change package within the trial?" +#: ../system/integrations/slack.rst:34 +msgid "" +"This will give you further options, as you can see e.g. escalating tickets " +"that are assigned to an agent that's e.g. absent. You can interact faster, " +"as you might see problems earlier (or even before the problem gets one)." msgstr "" -#: ../system/subscription/index.rst:40 -msgid "No. As soon as the package is changed the subscription begins." +#: ../system/integrations/slack.rst:38 +msgid "" +"If needed and wanted, you can even discuss directly about the topic before " +"sending an answer to the customer. Another possible use case would be a " +"agent monitoring new agents and their answers to tickets." msgstr "" -#: ../system/subscription/index.rst:45 -msgid "What happens to my trial instance after the trial period ended?" +#: ../system/integrations/slack.rst:44 +#, fuzzy +msgid "Configure the Integration" +msgstr "聊天小部件的配置" + +#: ../system/integrations/slack.rst:46 +msgid "" +"First of all, please go to your slack workspace - go to administration => " +"Manage Apps. If you don't have an app yet, you can simply add a new one - " +"just search for ``Incoming WebHooks`` and customize the app to your needs." msgstr "" -#: ../system/subscription/index.rst:43 +#: ../system/integrations/slack.rst:50 msgid "" -"Your instance will automatically be canceled for you. Please see *What " -"happens to my instance after it has been canceled?* for more." +"Choose (or create) the channel Zammad should post it's information to and " +"press on \"Add Incoming WebHooks integration\". If you're ready, copy the " +"provided WebHook URL and go to your Zammad installation." msgstr "" -#: ../system/subscription/index.rst:58 -msgid "What happens to my instance after it has been canceled?" +#: ../system/integrations/slack.rst:56 +msgid "" +"You need administrative rights on the Slack Workspace. The link to the app " +"directory is normally ``https://[workspace-name].slack.com/apps`` ." msgstr "" -#: ../system/subscription/index.rst:48 -msgid "That depends slightly on your instance state:" +#: ../system/integrations/slack.rst:63 +msgid "" +"To configure the slack integration, log in to Zammad and go to Integrations " +"(System) => Slack in the admin panel." msgstr "" -#: ../system/subscription/index.rst:54 -msgid "Trial instance" +#: ../system/integrations/slack.rst:66 +msgid "" +"Here you can choose on what evens Zammad should post information about a " +"ticket to your Slack channel. Next you need to device what groups shall be " +"affected by this, as anybody with access to that specific Slack channel can " +"read at least parts of the ticket this might be a privacy issue, if you " +"select the wrong groups. The username is simply the name that Zammad uses as " +"display name inside the Slack chat. The channel defines the Slack channel " +"the information is being posted in. As last option, you can set a custom " +"icon for posting to slack." msgstr "" -#: ../system/subscription/index.rst:51 +#: ../system/integrations/slack.rst:74 msgid "" -"If you're still on trial, we will ice your instance and remind you once " -"again about your instance. We then will wait some days and remove your " -"instance from our system. This is the last time we will inform you by Email." +"When you're ready, just hit \"Submit\" and enable the integration. Zammad " +"will now post new ticket information based on the trigger you chose. Below " +"the options you have the recent log that shows the latest requests to Slack " +"for debugging if needed." msgstr "" -#: ../system/subscription/index.rst:58 -msgid "Paid instance" +#: ../system/integrations/slack.rst:81 +msgid "" +"If you leave the Icon URL empty, Zammad will use the Zammad logo instead. " +"The icon should be a square PNG file." msgstr "" -#: ../system/subscription/index.rst:57 +#: ../system/integrations/slack.rst:90 msgid "" -"If you're a paying customer and canceled your subscription, the instance " -"removal will take place the day after your last subscription day." +"The following figure shows how it will look if you choose to receive updates " +"on created and updated tickets. On every post Zammad sends to the Slack " +"channel, you can create new threads to discuss about the new article." msgstr "" -#: ../system/subscription/index.rst:60 -msgid "Can removed instances be restored?" +#: ../system/integrations/slack.rst:96 +msgid "" +"If you just want to keep track of soon escalating or already escalated " +"tickets, it will look the the following figure. Zammad changes the color in " +"front of the post so you can easily see the state of the ticket." msgstr "" -#: ../system/subscription/index.rst:61 -msgid "No. Once your instance has been removed, a restoration is not possible." +#: ../system/integrations/slack.rst:102 +msgid "" +"If you change the state, Zammad will also put information on what state the " +"ticket gets and (if pending state) the date until it pends. You'll also " +"recognize the color codes in front of posts on slack, as they are exact the " +"same the ticket state colors you'll see in Zammad!" msgstr "" -#: ../system/subscription/plan.rst:2 ../system/subscription/plan.rst:38 -msgid "Plan" +#: ../system/integrations/smime/index.rst:2 +msgid "S/MIME" msgstr "" -#: ../system/subscription/plan.rst:16 -msgid "Subscription" +#: ../system/integrations/smime/index.rst:11 +msgid "" +"S/MIME is the most widely-supported method for secure email communication. " +"With S/MIME, you can exchange **signed** and **encrypted** messages with " +"others." msgstr "" -#: ../system/subscription/plan.rst:5 +#: ../system/integrations/smime/index.rst:15 msgid "" -"On the top of the subscription summary you'll find the number of used and " -"available (booked) agent seats. By using the *see more* link you can also " -"expand an agent list to see the currently configured active agents. This " -"list *does not* count accounts with admin permissions only." +"is proof that a message hasn't been tampered with or sent by an impersonator." msgstr "" -#: ../system/subscription/plan.rst:0 +#: ../system/integrations/smime/index.rst:17 msgid "" -"Within subscription you can always see how many agents are still\n" -"available to add and who uses the seats." +"In other words, it guarantees a message's **integrity** and **authenticity**." msgstr "" -#: ../system/subscription/plan.rst:14 -msgid "" -"Learn more on how to manage your agents in general :doc:`here `." +#: ../system/integrations/smime/index.rst:22 +msgid "In other words, it guarantees **privacy** and **data security**." msgstr "" -#: ../system/subscription/plan.rst:19 -msgid "" -"This section gives you an overview of the available plans and their " -"functions / limits. If you require a more detailed table, check our " -"`detailed pricing table `_ for more." +#: ../system/integrations/smime/index.rst:28 +msgid "Screencast demo of S/MIME features for both new tickets and replies" msgstr "" -#: ../system/subscription/plan.rst:23 +#: ../system/integrations/smime/index.rst:28 msgid "" -"Your selection in this step will decide on the base agent price and e.g. " -"agent limits that might apply in the summary step." +"Once S/MIME has been enabled, 🔒 **Encrypt** and ✅ **Sign** buttons will " +"appear in the ticket composer." msgstr "" -#: ../system/subscription/plan.rst:26 -msgid "" -"The green *Selected* button will also tell you what plan you're currently in." +#: ../system/integrations/smime/index.rst:32 +msgid ":doc:`🔪 Prerequisites `" msgstr "" -#: ../system/subscription/plan.rst:30 +#: ../system/integrations/smime/index.rst:31 msgid "" -"Trial instances are running at Professional with 3 agents. The plan cannot " -"be changed during the trial for technical reasons, if you require more " -"agents for testing, please contact `our sales team `_ with a reason for the raise request." +"New to S/MIME? This section helps you to find certificate providers and " +"points out Limitations." msgstr "" -#: ../system/subscription/plan.rst:0 -msgid "" -"Screenshot showing three available packages for a hosted Zammad\n" -"instance" +#: ../system/integrations/smime/index.rst:35 +msgid ":doc:`📝 Manage Certificates `" msgstr "" -#: ../system/subscription/plan.rst:83 -msgid "Summary" +#: ../system/integrations/smime/index.rst:35 +msgid "Add and download certificates; configure group default behaviors." msgstr "" -#: ../system/subscription/plan.rst:41 -msgid "" -"In this section you can adjust the settings of the previous selected plan." +#: ../system/integrations/smime/index.rst:38 +msgid ":doc:`😦 Troubleshooting `" msgstr "" -#: ../system/subscription/plan.rst:45 -msgid "" -"Note that upgrading (more agents, higher package) is always possible, " -"however, downgrading will only happen when your billing period renews." +#: ../system/integrations/smime/index.rst:38 +msgid "Took a wrong turn? About recent logs and common issues." msgstr "" -#: ../system/subscription/plan.rst:49 +#: ../system/integrations/smime/index.rst:43 msgid "" -"Upgrading resets your billing period and existing credit will be deducted " -"from the new total." +"For more details on how S/MIME integration works on the agent side, see the :" +"user-docs:`user docs `." msgstr "" -#: ../system/subscription/plan.rst:58 -msgid "Billing cycle" +#: ../system/integrations/smime/manage-certificates.rst:2 +msgid "Manage Certificates" msgstr "" -#: ../system/subscription/plan.rst:53 +#: ../system/integrations/smime/manage-certificates.rst:4 msgid "" -"You can choose between either monthly or yearly billing. The price per agent " -"will be cheaper if you decide for yearly billing." +"S/MIME is **disabled by default**. Enable it to start adding certificates." +msgstr "" + +#: ../system/integrations/smime/manage-certificates.rst:10 +msgid "Dialogue to add new certificates or private keys" msgstr "" -#: ../system/subscription/plan.rst:56 +#: ../system/integrations/smime/manage-certificates.rst:10 msgid "" -"If you're still trying out things and are unsure of the right package for " -"your instance, you may want to choose monthly first and then upgrade to " -"yearly when you're sure." +"Manage certificates in the Admin Panel under **System > Integrations > S/" +"MIME**. Certificates may be pasted in as plain text or uploaded from a file." msgstr "" -#: ../system/subscription/plan.rst:66 -msgid "Plan: (Starter|Professional|Plus) - Agents" +#: ../system/integrations/smime/manage-certificates.rst:14 +msgid "Add Certificate Data" msgstr "" -#: ../system/subscription/plan.rst:61 -msgid "Choose the number of agents you require for your instance." +#: ../system/integrations/smime/manage-certificates.rst:36 +msgid "Add Certificate" msgstr "" -#: ../system/subscription/plan.rst:63 +#: ../system/integrations/smime/manage-certificates.rst:17 msgid "" -"Keep in mind that some packages may have agent limits. Depending on the " -"previous chosen package, you won't be able to exceed specific agent numbers. " -"Also note that setting less agents than currently configured is not possible." +"Import public-key certificates for both your own organization and your " +"contacts." msgstr "" -#: ../system/subscription/plan.rst:69 -msgid "Total" +#: ../system/integrations/smime/manage-certificates.rst:19 +msgid "" +"You can also add a bunch of certificates in one go by providing a single " +"file with all relevant certificates." msgstr "" -#: ../system/subscription/plan.rst:69 -msgid "This will be the net total you're going to be billed." +#: ../system/integrations/smime/manage-certificates.rst:22 +msgid "🕵️ **ALWAYS verify certificates in-person or over the phone!**" msgstr "" -#: ../system/subscription/plan.rst:71 +#: ../system/integrations/smime/manage-certificates.rst:24 msgid "" -"By using the *Update subscription* button, the instance package will be " -"adjusted immediately. If you didn't provide a payment method yet, Zammad " -"will request you to provide one at this point." +"The whole point of signatures is to alert you when someone is trying to " +"pretend to be someone they're not. Never accept a certificate from someone " +"online without verifying it first." msgstr "" -#: ../system/subscription/plan.rst:77 -msgid "" -"In case you're still within the trial period, this means that the trial will " -"be over immediately!" +#: ../system/integrations/smime/manage-certificates.rst:28 +msgid "📇 **What about trusted certificate authorities?**" msgstr "" -#: ../system/subscription/plan.rst:80 -msgid "Down- or upgrading during the trial period *is not* possible." +#: ../system/integrations/smime/manage-certificates.rst:30 +msgid "" +"In some cases (e.g. when dealing with large enterprises), you may be given a " +"certificate for an entire CA, rather than a single contact. Add it here to " +"trust *all* certificates issued by that CA." msgstr "" -#: ../system/subscription/plan.rst:0 -msgid "Screenshot showing payment options and a pricing summary" +#: ../system/integrations/smime/manage-certificates.rst:35 +msgid "" +"Commercial CAs can usually be verified online. Zammad does not include a " +"list of built-in, trusted CAs." msgstr "" -#: ../system/subscription/plan.rst:99 -msgid "Payment method" +#: ../system/integrations/smime/manage-certificates.rst:57 +msgid "Add Private Key" msgstr "" -#: ../system/subscription/plan.rst:86 -msgid "You can pay via credit card or SEPA mandate." +#: ../system/integrations/smime/manage-certificates.rst:39 +msgid "" +"Once you've added a public-key certificate, you can import its matching " +"private key." msgstr "" -#: ../system/subscription/plan.rst:91 -msgid "Credit card" +#: ../system/integrations/smime/manage-certificates.rst:42 +msgid "" +"Private keys are for **your own organization only**; never ask your contacts " +"for their private keys." msgstr "" -#: ../system/subscription/plan.rst:89 +#: ../system/integrations/smime/manage-certificates.rst:0 msgid "" -"Simply follow the dialogue by clicking *authorize* and confirm -if required " -"by your bank- your consent to Zammad using your card for the payments." +"S/MIME integration showing configured certificates and possible issues with " +"Logging" msgstr "" -#: ../system/subscription/plan.rst:95 -msgid "SEPA" +#: ../system/integrations/smime/manage-certificates.rst:50 +msgid "" +"A note is displayed on certificates with a matching private key (see line 2)." msgstr "" -#: ../system/subscription/plan.rst:94 -msgid "" -"Provide the requested information of the bank account holder and update if " -"you're ready. You'll then receive an email with the SEPA mandate." +#: ../system/integrations/smime/manage-certificates.rst:52 +msgid "📤 **Certificates and private keys must be uploaded separately.**" msgstr "" -#: ../system/subscription/plan.rst:97 +#: ../system/integrations/smime/manage-certificates.rst:54 msgid "" -"Technically there's also the possibility to pay via invoice, however - this " -"method only applies to a fairly low number of instances. Please contact `our " -"sales team `_ for more information." +"If your certificate and private key are bundled together in the same file or " +"PEM block, import it twice (once using each button)." msgstr "" -#: ../system/translations.rst:2 -msgid "Translations" +#: ../system/integrations/smime/manage-certificates.rst:57 +msgid "Please note that bulk imports of private keys are not possible." msgstr "" -#: ../system/translations.rst:4 -msgid "" -"Translations of Zammad are processed centrally in our `Weblate instance " -"`_. This allows non-developers to review " -"and update translation texts of the language they actually speak." +#: ../system/integrations/smime/manage-certificates.rst:60 +msgid "Download Certificate Data" msgstr "" -#: ../system/translations.rst:9 +#: ../system/integrations/smime/manage-certificates.rst:62 msgid "" -"Your language is in an incomplete translation state or has typos? Please " -"consider helping us in sorting this out! All you need is either a GitHub " -"account or to register directly in our instance." +"You can download the earlier provided certificates and private keys at any " +"time from your Zammad instance." msgstr "" -#: ../system/translations.rst:13 +#: ../system/integrations/smime/manage-certificates.rst:65 msgid "" -"Did you know? This is also where the documentation translations are handled. " -"🤓" +"Please note that passphrase-protected private keys stay protected and when " +"you download them, you have to know the passphrase to use them after " +"downloading." msgstr "" -#: ../system/translations.rst:15 -msgid "" -"Have a look in our :docs:`contribution section ` in the system documentation to get started!" +#: ../system/integrations/smime/manage-certificates.rst:73 +msgid "Dialogue to download certificates or private keys" msgstr "" -#: ../system/translations.rst:20 -msgid "Local Translations" +#: ../system/integrations/smime/manage-certificates.rst:73 +msgid "Download stored certificates and their keys" msgstr "" -#: ../system/translations.rst:22 +#: ../system/integrations/smime/manage-certificates.rst:78 msgid "" -"Apart from these system translations, there's still local translations you " -"can manage. This is relevant if you added custom objects that require " -"translations or even custom states and priorities." +"The ticket composer will set all outgoing messages to **signed and " +"encrypted** by default (assuming the required certificates exist)." msgstr "" -#: ../system/translations.rst:None -msgid "Translation management screen within the admin menu" +#: ../system/integrations/smime/manage-certificates.rst:82 +msgid "These defaults can be modified on a per-group basis:" msgstr "" -#: ../system/translations.rst:31 -msgid "Updating Translations" +#: ../system/integrations/smime/manage-certificates.rst:None +msgid "Zammad allowing to choose the default behavior on per group basis" msgstr "" -#: ../system/translations.rst:33 +#: ../system/integrations/smime/manage-certificates.rst:89 msgid "" -"Because of how Zammad ships translations, the only way to update the system " -"translations is to update your Zammad installation. The benefit of this is " -"that you no longer need internet access during a Zammad upgrade as the " -"package has everything it requires already." +"Of course, agents can always manually change these settings on each email " +"they send out." msgstr "" -#: ../system/translations.rst:39 -msgid "Translation of Custom Objects" +#: ../system/integrations/smime/prerequisites.rst:4 +msgid "A certificate *and* private key for your own organization" msgstr "" -#: ../system/translations.rst:41 +#: ../system/integrations/smime/prerequisites.rst:6 msgid "" -"No problem at all! You can customize any translation locally, even if it is " -"not initially provided by the system." +"(Use this to ✒️ **sign outgoing messages** and 🔓 **decrypt incoming " +"messages**.)" msgstr "" -#: ../system/translations.rst:44 +#: ../system/integrations/smime/prerequisites.rst:9 msgid "" -"Translation is supported for a broad number of features, including but not " -"limited to custom:" +"Certificates belonging your contacts, or their issuing certificate authority " +"(CA)" msgstr "" -#: ../system/translations.rst:47 -msgid "Object Attributes" +#: ../system/integrations/smime/prerequisites.rst:11 +msgid "" +"(Use these to ✅ **verify incoming message signatures** and 🔒 **encrypt " +"outgoing messages**.)" msgstr "" -#: ../system/translations.rst:48 -#, fuzzy -msgid "Ticket Macros" -msgstr "宏" - -#: ../system/translations.rst:49 -msgid "Ticket Overviews" +#: ../system/integrations/smime/prerequisites.rst:14 +msgid "🙋 **I'm new to S/MIME. Where can I get a certificate?**" msgstr "" -#: ../system/translations.rst:50 -#, fuzzy -msgid "Ticket Priorities" -msgstr "优先级" - -#: ../system/translations.rst:51 -msgid "Ticket States" +#: ../system/integrations/smime/prerequisites.rst:16 +msgid "" +"The easiest way to get certificates is to buy an annual subscription through " +"a commercial CA, such as:" msgstr "" -#: ../system/translations.rst:54 -msgid "Customizing Translations" +#: ../system/integrations/smime/prerequisites.rst:19 +msgid "" +"`Sectigo (formerly Comodo) `_" msgstr "" -#: ../system/translations.rst:56 -msgid "" -"Within the translation screen, simply click on the **New Translation** " -"button." +#: ../system/integrations/smime/prerequisites.rst:20 +msgid "`Secorio `_" msgstr "" -#: ../system/translations.rst:None -#, fuzzy -msgid "New translation dialog" -msgstr "新建电子邮件账户对话框" +#: ../system/integrations/smime/prerequisites.rst:21 +msgid "`GlobalSign `_" +msgstr "" -#: ../system/translations.rst:62 -msgid "" -"In the dialog you can immediately enter the exact translation source (if you " -"know it) and your custom translation text for it and click **Submit**." +#: ../system/integrations/smime/prerequisites.rst:23 +msgid "(Zammad is not affiliated with these CAs in any way.)" msgstr "" -#: ../system/translations.rst:65 +#: ../system/integrations/smime/prerequisites.rst:25 msgid "" -"Alternatively, try to search for translation suggestions in the list below. " -"Selecting an item from the list will pre-fill the translation source for you " -"and then you can just enter your custom translation." +"You can also generate your own self-signed certificates, but the process is " +"complicated and usually 🙅 **involves extra work for your contacts**." msgstr "" -#: ../system/translations.rst:69 +#: ../system/integrations/smime/prerequisites.rst:29 msgid "" -"The target language will always default to your current language selection. " -"If you need to translate for a different language, simply change the " -"selection before submitting." +"Bear in mind that 🤝 **S/MIME only works if the other party is using it, too." +"**" msgstr "" -#: ../system/translations.rst:73 -msgid "" -"All your custom translations will show up in the overview table when added. " -"And they will even persist across Zammad updates!" +#: ../system/integrations/smime/prerequisites.rst:32 +msgid "Certificate and Private Key Checks on Upload" msgstr "" -#: ../system/translations.rst:76 +#: ../system/integrations/smime/prerequisites.rst:34 msgid "" -"Make sure to reload your browser if a translated string is not displayed." +"The certificate and public key validation is based on the ``X509v3`` " +"extensions." msgstr "" -#: ../system/translations.rst:80 -msgid "Reverting to Original Translations" +#: ../system/integrations/smime/prerequisites.rst:49 +msgid "Uploading a *client certificate*?" msgstr "" -#: ../system/translations.rst:82 -msgid "" -"If you want to revert a custom translation to original text, simply use the " -"appropriate action within the row of the overview table." +#: ../system/integrations/smime/prerequisites.rst:41 +msgid "The following attributes are required then:" msgstr "" -#: ../system/translations.rst:85 -msgid "" -"Depending on the type of the translation source, the action has a slightly " -"different name:" +#: ../system/integrations/smime/prerequisites.rst:39 +msgid "Subject Alternative Name (at least one email address has to be present)" msgstr "" -#: ../system/translations.rst:88 -msgid "**Reset** for customized system translations" +#: ../system/integrations/smime/prerequisites.rst:40 +msgid "Key Usage (``Digital Signature`` and/or ``Key Encipherment``)" msgstr "" -#: ../system/translations.rst:89 -msgid "**Remove** for customized local translations" +#: ../system/integrations/smime/prerequisites.rst:41 +msgid "Public key algorithm (either ``RSA`` or ``EC``)" msgstr "" -#: ../system/translations.rst:91 +#: ../system/integrations/smime/prerequisites.rst:43 msgid "" -"In both cases, the action will remove the customized translation after a " -"confirmation." +"The Extended Key Usage attribute is optional. If the certificate provides " +"the named attribute, than it must contain the value ``E-mail Protection``." msgstr "" -#: ../system/translations.rst:None -msgid "Screenshot showing the location of the Remove action" +#: ../system/integrations/smime/prerequisites.rst:46 +msgid "" +"Please note that any usable email adress has to be prefixed with ``email:`` " +"or ``rfc822:``." msgstr "" -#: ../system/translations.rst:99 -msgid "Inline Translations" +#: ../system/integrations/smime/prerequisites.rst:49 +msgid "The named public key algorithms are mandatory for private keys as well." msgstr "" -#: ../system/translations.rst:101 -msgid "" -"If you prefer a more hands-on approach, you can activate the inline or on-" -"screen translation feature by pressing ``ctrl`` + ``alt`` + ``t`` at any " -"time and on any screen." +#: ../system/integrations/smime/prerequisites.rst:54 +msgid "Uploading a *CA certificate*?" msgstr "" -#: ../system/translations.rst:105 +#: ../system/integrations/smime/prerequisites.rst:52 msgid "" -"All customizable translation texts will be highlighted for you on the " -"screen. Just click into the highlighted area and update the text in place." +"In the case of an uploaded CA certificate, providing the value ``CA:TRUE`` " +"in the attribute *Basic Contstraints*, the previously mentioned attributes " +"are not verified." msgstr "" -#: ../system/translations.rst:None -msgid "Inline translation mode activated for the Overview screen" +#: ../system/integrations/smime/prerequisites.rst:56 +msgid "" +"In general, the usage of any expired (``Not After``) or not yet valid (``Not " +"Before``) certificate is denied for outgoing emails." msgstr "" -#: ../system/translations.rst:112 -msgid "" -"When finished editing, simply press ``ctrl`` + ``alt`` + ``t`` again to " -"deactivate." +#: ../system/integrations/smime/prerequisites.rst:59 +msgid "Example certificate:" msgstr "" -#: ../system/translations.rst:117 +#: ../system/integrations/smime/prerequisites.rst:85 msgid "" -"Even though it's available on any screen, the inline translation feature " -"requires admin permissions. It works only for the current language " -"selection. If you need to translate a different language, first change the " -"language in your :user-docs:`profile settings `." +"Please note that Zammad will distrust senders by default. This means that " +"you're always required to provide certificate data, no matter if for signing " +"or encrypting." msgstr "" -#: ../system/variables.rst:2 -msgid "Variables" +#: ../system/integrations/smime/prerequisites.rst:89 +msgid "This is by design and can't be adjusted." msgstr "" -#: ../system/variables.rst:4 +#: ../system/integrations/smime/troubleshooting.rst:4 msgid "" -"Please note that this is just an overview of available variables. It might " -"be incomplete or variables might not be available within some functions. If " -"you're missing variables or are not sure if something is not working as " -"expected, feel free to ask over at the `Community `_." +"All of the system's latest S/MIME activity is displayed in the **Recent " +"Logs** section." msgstr "" -#: ../system/variables.rst:10 -msgid "" -"Variables can be called by typing ``::`` (just like text modules in the " -"frontend), as long as you're in a supported text field within the backend. " -"Zammad will display all variables being available within this context and " -"replace it to the variable as soon as you selected an entry." +#: ../system/integrations/smime/troubleshooting.rst:11 +msgid "Sample entries of in- and outgoing S/MIME related emails." msgstr "" -#: ../system/variables.rst:15 +#: ../system/integrations/smime/troubleshooting.rst:11 msgid "" -"You have an empty field which you referenced and it appears as ``-``? That's " -"currently working as designed - you might want to ensure that these fields " -"always have a value." +"Logs report the status and details of all mail, both incoming and outgoing, " +"that used signing/verification or encryption/decryption." msgstr "" -#: ../system/variables.rst:20 -msgid "Variable Categories" +#: ../system/integrations/smime/troubleshooting.rst:14 +msgid "" +"This log does **not** include email sent by :doc:`triggers ` or the :doc:`scheduler `. For those, check your " +"``production.log``." msgstr "" -#: ../system/variables.rst:31 -msgid "Wait, What About Custom Objects?" +#: ../system/integrations/smime/troubleshooting.rst:20 +msgid "Common Issues" msgstr "" -#: ../system/variables.rst:33 -msgid "" -"Good point! Of course, we can't predict what objects you might create, but " -"we can give you a hint on how to put the puzzle together to get your custom " -"values." +#: ../system/integrations/smime/troubleshooting.rst:30 +msgid "I received a signed/encrypted email before I set up S/MIME integration" msgstr "" -#: ../system/variables.rst:36 +#: ../system/integrations/smime/troubleshooting.rst:23 msgid "" -"For this, we'll talk about the inner part of the variable (so everything " -"within ``#{}``), please put the outer part around to have a valid variable. " -"The first part of the variable name consist of the object type. Currently " -"these are:" +"No problem. Once S/MIME has been enabled and the appropriate certificates " +"have been added, agents will be prompted to retry verification/decryption on " +"matching emails." msgstr "" -#: ../system/variables.rst:41 -msgid "Ticket (``ticket``)" +#: ../system/integrations/smime/troubleshooting.rst:0 +msgid "Screenshot of user prompt to retry decryption" msgstr "" -#: ../system/variables.rst:42 -msgid "User (``user``)" +#: ../system/integrations/smime/troubleshooting.rst:38 +msgid "The 🔒 **Encrypt** button is disabled" msgstr "" -#: ../system/variables.rst:43 -msgid "Organization (``organization``)" +#: ../system/integrations/smime/troubleshooting.rst:33 +msgid "Have you added the recipient's certificate?" msgstr "" -#: ../system/variables.rst:44 -msgid "Group (``group``)" +#: ../system/integrations/smime/troubleshooting.rst:34 +msgid "Are you sure the recipient's certificate is valid?" msgstr "" -#: ../system/variables.rst:46 -msgid "" -"The second part is the name of the object. This is the name you define " -"during object creation and can be found within the object menu at any time. " -"The first and second part of a variable is divided by a point, e.g.: " -"``ticket.number`` which will in total be ``#{ticket.number}``." +#: ../system/integrations/smime/troubleshooting.rst:35 +msgid "Have you checked your ``production.log`` for more details?" msgstr "" -#: ../system/variables.rst:51 +#: ../system/integrations/smime/troubleshooting.rst:37 msgid "" -"Now, in some situations it's possible that you'll need to use a third part. " -"The best example for such a situation would be a ``select`` or ``tree-" -"select`` field which will by default return the key value, not it's display " -"name. For this, just extend your variable with ``.value``. This will result " -"in ``#{ticket.select.value}``." +"If encryption doesn't work in the composer, it won't work in :doc:`triggers " +"` or the :doc:`scheduler ` either!" msgstr "" -#: ../system/variables.rst:60 -msgid "Using Translated Variables" +#: ../system/integrations/smime/troubleshooting.rst:42 +msgid "The ✅ **Sign** button is disabled" msgstr "" -#: ../system/variables.rst:62 +#: ../system/integrations/smime/troubleshooting.rst:41 msgid "" -"If you want to use a translated variable in triggers or schedulers, you can " -"extend the placeholder like this: ``#{t(ticket.state.name)}``. The ``t`` " -"tells Zammad to search for fitting translated strings. The used output " -"language is based on the system language of Zammad which you can set in the " -"admin panel under :doc:`/settings/branding` or based on the selected locale " -"in the trigger/scheduler edit dialog." +"Have you added **both the certificate and private key** for your " +"organization?" msgstr "" -#: ../system/variables.rst:69 +#: ../system/integrations/smime/troubleshooting.rst:42 msgid "" -"A possible use-case: you want to send your customers updates on tickets via " -"trigger or scheduler which should include the state of the ticket. Using the " -"default ``#{ticket.state.name}`` (without the translation flag ``t()``) " -"would lead to the output of the original (english) name of the state." +"Does the email address on the certificate match the email address of the " +"agent/group composing the email?" msgstr "" -#: ../system/variables.rst:75 -msgid "Date and Time Formatting" +#: ../system/integrations/smime/troubleshooting.rst:45 +msgid "Error: “Fingerprint already taken”" msgstr "" -#: ../system/variables.rst:77 -msgid "" -"The system (trigger/scheduler selected) locale and timezone predefines a " -"default format of date and timestamp. This format is customizable by using " -"the ``dt()`` method." +#: ../system/integrations/smime/troubleshooting.rst:45 +msgid "Are you sure you haven't added this certificate already?" msgstr "" -#: ../system/variables.rst:79 -msgid "The method arguments are as follows:" +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Error: “❌ invalid byte sequence in UTF-8”" msgstr "" -#: ../system/variables.rst:81 -msgid "The date or timestamp variable you want to format." +#: ../system/integrations/smime/troubleshooting.rst:48 +msgid "Please ensure to provide PEM formatted certificate and keys." msgstr "" -#: ../system/variables.rst:82 -msgid "The output format string." +#: ../system/integrations/smime/troubleshooting.rst:49 +msgid "Did you check if the provided file is a valid certificate or key?" msgstr "" -#: ../system/variables.rst:83 -msgid "The timezone to apply (optional)." +#: ../system/integrations/zabbix.rst:2 +msgid "Zabbix Integration" msgstr "" -#: ../system/variables.rst:86 +#: ../system/integrations/zabbix.rst:5 msgid "" -"``#{dt(ticket.updated_at, \"%A %Y-%m-%d %H:%M in the office\", \"Europe/" -"Berlin\")}``" +"This guide describes how to integrate your Zabbix 5.4 installation with " +"Zammad using the Zabbix webhook feature. This guide will provide " +"instructions on setting up a media type, a user and an action in Zabbix." msgstr "" -#: ../system/variables.rst:87 -msgid "Monday, 2024-03-18 15:31 in the office" +#: ../system/integrations/zabbix.rst:12 +msgid "Zammad with enabled HTTP Token Authentication" msgstr "" -#: ../system/variables.rst:89 -msgid "" -"If you want to use our example, make sure to paste the string above without " -"formatting (``CTRL+Shift+v``), otherwise it won't work." +#: ../system/integrations/zabbix.rst:13 +msgid "Zabbix version 5.4 or higher" msgstr "" -#: ../system/variables.rst:93 -msgid "The following table lists available format directives:" +#: ../system/integrations/zabbix.rst:16 +msgid "Setting up a Zammad" msgstr "" -#: ../system/variables.rst:99 -msgid "Parameter" +#: ../system/integrations/zabbix.rst:18 +msgid "Enable **API Token Access** in Settings > System > API." msgstr "" -#: ../system/variables.rst:102 -msgid "``%Y``" +#: ../system/integrations/zabbix.rst:20 +msgid "" +"Create a **new user** for a Zabbix alerter with an **email address** and " +"create a personal user token with **ticket.agent** permissions." msgstr "" -#: ../system/variables.rst:103 -msgid "Year with 4 digits" +#: ../system/integrations/zabbix.rst:24 +msgid "Zabbix Webhook Configuration" msgstr "" -#: ../system/variables.rst:104 -msgid "Use ``%y`` for year with 2 digits" +#: ../system/integrations/zabbix.rst:27 +#, fuzzy +msgid "Create a Global Macro" +msgstr "宏" + +#: ../system/integrations/zabbix.rst:29 +msgid "" +"Before setting up the **Webhook**, you need to setup the global macro " +"**{$ZABBIX.URL}**, which must contain the **URL** to the **Zabbix frontend**." msgstr "" -#: ../system/variables.rst:105 -msgid "``%m``" +#: ../system/integrations/zabbix.rst:33 +msgid "" +"In the **Administration** > **Media types** section, import the `Template`_." msgstr "" -#: ../system/variables.rst:106 -msgid "Month of year (as number with zero-padding)" +#: ../system/integrations/zabbix.rst:38 +msgid "Open the added **Zammad** media type and set:" msgstr "" -#: ../system/variables.rst:107 -msgid "Use ``%-m`` for month without zero-padding" +#: ../system/integrations/zabbix.rst:40 +msgid "**zammad\\_access\\_token** to the your **Personal User Token**" msgstr "" -#: ../system/variables.rst:108 -msgid "``%d``" +#: ../system/integrations/zabbix.rst:41 +msgid "" +"**zammad\\_url** to the **frontend URL** of your **Zammad** installation" msgstr "" -#: ../system/variables.rst:109 -msgid "Day of month (as number with zero-padding)" +#: ../system/integrations/zabbix.rst:43 +msgid "**zammad\\_customer** to your **Zammad user email**." msgstr "" -#: ../system/variables.rst:110 -msgid "Use ``%e`` for day without zero-padding" +#: ../system/integrations/zabbix.rst:44 +msgid "" +"**zammad\\_enable\\_tags** to **true** or **false** to enable or disable " +"trigger tags. **Important**: if you enable tag support, each tag is set with " +"a separate request." msgstr "" -#: ../system/variables.rst:111 -msgid "``%H``" +#: ../system/integrations/zabbix.rst:48 +msgid "" +"If you want to prioritize issues according to **severity** values in Zabbix, " +"you can define mapping parameters:" msgstr "" -#: ../system/variables.rst:112 -msgid "Hour of day in 24h notation with zero-padding" +#: ../system/integrations/zabbix.rst:51 +msgid "**severity\\_**: Zammad priority ID" msgstr "" -#: ../system/variables.rst:113 -msgid "Use ``%k`` for hour without zero-padding" +#: ../system/integrations/zabbix.rst:53 +msgid "Click the **Update** button to save the **Webhook** settings." msgstr "" -#: ../system/variables.rst:114 -msgid "``%I``" +#: ../system/integrations/zabbix.rst:55 +msgid "" +"To receive notifications in **Zammad**, you need to create a **Zabbix user** " +"and add **Media** with the **Zammad** type." msgstr "" -#: ../system/variables.rst:115 -msgid "Hour of day in 12h notation with zero-padding" +#: ../system/integrations/zabbix.rst:58 +msgid "" +"For **Send to**: enter any text, as this value is not used, but is required." msgstr "" -#: ../system/variables.rst:116 +#: ../system/integrations/zabbix.rst:61 msgid "" -"Use ``%l`` for hour without zero-padding and ``%p`` / ``%P`` for meridian " -"indicator" +"For more information, use the `Zabbix documentation `_." msgstr "" -#: ../system/variables.rst:117 -msgid "``%M``" +#: ../system/maintenance.rst:2 +msgid "Maintenance" msgstr "" -#: ../system/variables.rst:118 -msgid "Minute of hour" +#: ../system/maintenance.rst:4 +msgid "" +"Zammad comes with a maintenance mode that you can use for e.g. updating the " +"instance or changing settings while restricting availability and functions." msgstr "" -#: ../system/variables.rst:120 -msgid "``%S``" +#: ../system/maintenance.rst:13 +msgid "Mode" msgstr "" -#: ../system/variables.rst:121 -msgid "Second of Minute" +#: ../system/maintenance.rst:8 +msgid "The mode setting allows you to enable or disable the maintenance mode." msgstr "" -#: ../system/variables.rst:123 -msgid "``%A``" +#: ../system/maintenance.rst:10 +msgid "Defaults to *off*." msgstr "" -#: ../system/variables.rst:124 -msgid "Weekday name" +#: ../system/maintenance.rst:12 +msgid "" +"The maintenance mode will restrict access to administrative roles only. This " +"means agents and customers are logged off." msgstr "" -#: ../system/variables.rst:125 -msgid "Use ``%a`` for abbreviated name or ``%^A`` for uppercase name" +#: ../system/maintenance.rst:23 +msgid "@Login" msgstr "" -#: ../system/variables.rst:126 -msgid "``%B``" +#: ../system/maintenance.rst:16 +msgid "" +"This setting allows you to provide a login message within a green banner " +"above the login screen. Click into the green banner in the settings page to " +"adjust your message. To activate the message, activate the *@Login* setting." msgstr "" -#: ../system/variables.rst:127 -msgid "Month name" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing the default login message within the\n" +"settings page" msgstr "" -#: ../system/variables.rst:128 -msgid "Use ``%b`` for abbreviated name" +#: ../system/maintenance.rst:26 +msgid "" +"Send an informative message to **all active sessions**. This comes handy to " +"inform your agents e.g. about mayor outages or to force reloads after " +"configuration changes." msgstr "" -#: ../system/variables.rst:129 -msgid "``%U``" +#: ../system/maintenance.rst:31 +msgid "This is the messages title (slightly bigger than the normal message)." msgstr "" -#: ../system/variables.rst:130 -msgid "Week number of current year" +#: ../system/maintenance.rst:34 +msgid "The text you want to provide to your logged in sessions." msgstr "" -#: ../system/variables.rst:131 -msgid "Use ``%W`` for a different calculation method" +#: ../system/maintenance.rst:39 +msgid "Reload application" msgstr "" -#: ../system/variables.rst:134 +#: ../system/maintenance.rst:37 msgid "" -"We support the known format directives for the Ruby built-in method " -"``strftime`` of the ``DateTime`` class. For more information, see `here " -"`_." +"Selecting this option will change the message acceptance button from *Close* " +"(with nothing happening) to *Continue session*, which forces the application " +"to reload." msgstr "" -#: ../system/variables/article.rst:2 -msgid "Articles" +#: ../system/maintenance.rst:43 +msgid "" +"If you have customers that are logged in to Zammad, they'll also be notified " +"if they're active in that moment." +msgstr "" + +#: ../system/maintenance.rst:48 +msgid "Example without reload application" msgstr "" -#: ../system/variables/article.rst:4 ../system/variables/config.rst:4 -#: ../system/variables/current-user.rst:4 ../system/variables/ticket.rst:4 +#: ../system/maintenance.rst:52 msgid "" -"If you're missing variables or are not sure if something is not working as " -"expected, feel free to ask over at the `Community `_." +"Message setting within Zammad's admin settings without ticket reload " +"application setting." msgstr "" -#: ../system/variables/article.rst:6 +#: ../system/maintenance.rst:0 msgid "" -"Below you can find all available ticket article-based variables within " -"Zammad. These can be called via Triggers for example. If you're unsure if " -"Zammad does support variables at the point you're at, you can try to type " -"``::`` to check." +"Screenshot showing the send message settings without ticket\n" +"reload application set" msgstr "" -#: ../system/variables/article.rst:9 ../system/variables/config.rst:9 -#: ../system/variables/ticket.rst:9 +#: ../system/maintenance.rst:61 ../system/maintenance.rst:85 msgid "" -"The below list gives you an example what kind of data you can expect, it's " -"not intended to explain the data itself." +"The modal all other active sessions will see upon pressing *Send to clients*." msgstr "" -#: ../system/variables/article.rst:11 -msgid "Article Variables" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing modal caused by maintenance's message\n" +"without reload application ticket" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "name" +#: ../system/maintenance.rst:72 +msgid "Example with reload application" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "variable" +#: ../system/maintenance.rst:76 +msgid "" +"Message setting within Zammad's admin settings with ticket reload " +"application setting." msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/config.rst:1 -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "example" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing the send message settings with ticket\n" +"reload application set" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Web" +#: ../system/maintenance.rst:0 +msgid "" +"Screenshot showing modal caused by maintenance's message\n" +"with reload application ticket" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.web}``" +#: ../system/monitoring.rst:2 +msgid "Monitoring" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``https://zammad.com`` or empty if not set in user object" +#: ../system/monitoring.rst:4 +msgid "" +"This function is only available in self hosted instances. If you use Zammad " +"in our cloud, we are monitoring the system on our own and take steps to fix " +"potential problems directly." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > VIP" +#: ../system/monitoring.rst:11 +msgid "" +"On the monitoring page, you can see the current health state of Zammad under " +"\"*Current Status*\" at the bottom. This can be useful if you want to have a " +"look if everything is up and running. As an example, you could have a look " +"in the monitoring when you assume that some emails aren't processed from " +"Zammad." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.vip}``" +#: ../system/monitoring.rst:17 +msgid "**Can't receive an email and the monitoring response is \"healthy\"?**" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -msgid "``true`` or ``false``" +#: ../system/monitoring.rst:19 +msgid "" +"Zammad will just inform you about unprocessable emails. This is not the case " +"for oversized emails. You can adjust the maximum email size in :doc:`../" +"channels/email/settings`." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Phone" +#: ../system/monitoring.rst:24 +msgid "Monitoring API" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.phone}``" +#: ../system/monitoring.rst:26 +msgid "" +"Beside the indication in the monitoring page, you can also use an external " +"monitoring tool to monitor Zammad's health. To request the health of Zammad, " +"you need to provide the API key (token) to the external monitoring tool. You " +"can copy the token from the \"*Current Token*\" field as well as the whole " +"API endpoint of your system (\"*Health Check*\" field), in which the API " +"token is already included." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``+4930123456789`` or empty if not set in user object" +#: ../system/monitoring.rst:37 +msgid "Screenshot showing Current Token and Health Check" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Note" +#: ../system/monitoring.rst:37 +msgid "Screenshot showing Token and Health Check" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.note}``" +#: ../system/monitoring.rst:39 +msgid "" +"In addition to that, you can reset the auto-generated token to make sure " +"that already configured monitoring systems won't work anymore. So, please " +"use this \"*Reset*\" button only if you know what you do!" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Some note about user`` or empty if not set in user object" -msgstr "" +#: ../system/monitoring.rst:44 +#, fuzzy +msgid "Example Output" +msgstr "例如" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Mobile" +#: ../system/monitoring.rst:0 +msgid "No issues found" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.mobile}``" +#: ../system/monitoring.rst:48 ../system/monitoring.rst:60 +msgid "**Indicator in Zammad**:" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Login" +#: ../system/monitoring.rst:0 +msgid "Screenshot showing monitoring with no issues" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.login}``" +#: ../system/monitoring.rst:54 ../system/monitoring.rst:66 +msgid "**API response**::" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -#: ../system/variables/ticket.rst:1 -msgid "``jdoe``" +#: ../system/monitoring.rst:0 +msgid "Issues were found" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Lastname" +#: ../system/monitoring.rst:0 +msgid "Screenshot showing monitoring with issues" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.lastname}``" +#: ../system/objects.rst:2 +msgid "Objects" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/current-user.rst:1 -#: ../system/variables/ticket.rst:1 -msgid "``Doe`` or empty if not set" +#: ../system/objects.rst:4 +msgid "" +"In Zammad you can add your own fields to tickets, users, organizations and " +"even groups (these are called \"objects\"). This can be useful if you need " +"to add further information to a ticket or any other object in Zammad and the " +"information doesn't fit in any existing field." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Firstname" +#: ../system/objects.rst:11 +msgid "" +"Try to avoid deleting attributes (and disable them instead) as Zammad might " +"run into unexpected conditions if they are referenced somewhere." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.firstname}``" +#: ../system/objects.rst:16 +msgid "" +"Here's an overview of object attributes. On the upper right you can add new " +"attributes. By default, there will be no custom fields - standard attributes " +"will be grayed out, you can't delete or change those. You can edit custom " +"attributes (they are displayed in black font and have a trash bin on the " +"right side) just by clicking on them." msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "``Joe`` or empty if not set" +#: ../system/objects.rst:24 +msgid "" +"Attributes you add to Zammad, no matter if they have default values or not, " +"will not update existing information. This means a new ticket field " +"technically will be empty unless you populate it." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Fax" +#: ../system/objects.rst:28 +msgid "" +"Especially in ticket scope this also means that newly added attributes will " +"be indicated as \"changed\" to agents that view the ticket. This may " +"interfere with Zammad's tabs behavior." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.fax}``" -msgstr "" +#: ../system/objects.rst:40 +#, fuzzy +msgid "Ordering Attributes" +msgstr "组织和部门名称" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Email" +#: ../system/objects.rst:42 +msgid "" +"Since Zammad introduced :doc:`/system/core-workflows` the need to have a " +"custom positioning for attributes has become more important than ever." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.email}``" +#: ../system/objects.rst:45 +msgid "" +"To adjust the position of such an attribute, simply click on the attribute " +"entry in question, scroll down and adjust the position number. Please note " +"that you cannot change the positioning of default attributes." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``jdoe@example.com``" +#: ../system/objects.rst:49 +msgid "" +"In case two attributes have the same position value, Zammad will sort " +"alphabetically by name automatically." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Department" +#: ../system/objects.rst:None +msgid "" +"Screenshot showing custom attribute entries ordered in between default ones" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.department}``" +#: ../system/objects.rst:56 +msgid "Updating Database After Adding or Editing Attributes" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Sales`` or empty if not set in user object" +#: ../system/objects.rst:58 +msgid "" +"When adding or changing attributes, Zammad will not apply the changes " +"instantly, but instead shows you the changed attributes first. If you're " +"ready to go, just click on \"Update database\" to apply the changes to " +"Zammad. If you made a mistake or just want to discard your changes, click " +"\"Discard changes\"." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated by > Address" +#: ../system/objects.rst:64 +msgid "" +"After applying the changes with \"Update Database\", a restart of Zammad is " +"**mandatory**. If you don't perform it, you may experience unexpected " +"behavior or even errors. You may want to do this kind of configuration " +"during maintenance windows." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_by.address}``" +#: ../system/objects.rst:72 +msgid "" +"Changes on objects require you to update the database to apply these changes." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Some street 1, 12345 Berlin`` or empty if not set in user object" +#: ../system/objects.rst:75 +msgid "**🤓 Service restarts can be automated**" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Updated" +#: ../system/objects.rst:0 +msgid "Hosted environments automatically restart for you." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.updated_at}``" +#: ../system/objects.rst:0 +msgid "" +"If you're using a self-hosted installation you can use :docs:`environment " +"variables `" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``2019-10-08 15:24:47 UTC``" +#: ../system/objects.rst:82 +msgid "System Attributes" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Type > Name" +#: ../system/objects.rst:84 +msgid "" +"Zammad comes with pre-configured attributes. Some of them can't be edited " +"via UI (or at all). This is required for proper operation of Zammad and not " +"a bug." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.type.name}``" +#: ../system/objects.rst:90 +msgid "Ticket State" msgstr "" -#: ../system/variables/article.rst:1 +#: ../system/objects.rst:92 msgid "" -"``email`` (`list of article types `_)" +"If the pre-configured states aren't enough for you or you want to change " +"them, you can do so by clicking on the cogwheel icon in the state row in the " +"ticket tab. But you should be careful when changing pre-configured states. " +"This can lead to unwanted behavior in some cases." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > To" +#: ../system/objects.rst:None +msgid "Screenshot showing highlighted ticket state attribute" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.to}``" +#: ../system/objects.rst:122 +msgid "Handling of states" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``helpdesk@example.com``" +#: ../system/objects.rst:102 +msgid "" +"In the state configuration screen, you can add new states, disable states or " +"change states." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > TicketID" +#: ../system/objects.rst:0 +msgid "Screenshot showing table of default ticket states" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.ticket_id}``" +#: ../system/objects.rst:110 +msgid "" +"To add a new state, click on the \"New Ticket State\" button in the top " +"right corner. To change an existing state, simply click on the affected " +"state. This opens an edit dialog." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``1`` (not ticket number)" +#: ../system/objects.rst:114 +msgid "" +"You can also clone a state or set them to \"Default for new tickets\" or " +"\"Default for follow-ups\" by clicking on the ⁝ action button and select the " +"desired function." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Subject" +#: ../system/objects.rst:118 +msgid "" +"*Default for new tickets* means that this state is used for every newly " +"created ticket." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.subject}``" +#: ../system/objects.rst:121 +msgid "" +"*Default for follow-ups* means that this state is used if the ticket is re-" +"opened after it was closed." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``My amazing subject``" +#: ../system/objects.rst:171 +msgid "Ticket state in detail" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Sender > Name" +#: ../system/objects.rst:125 +msgid "" +"Below you can find a description for each field and option. Please head over " +"to the :ref:`example ` to see the edit dialog." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.sender.name}``" +#: ../system/objects.rst:129 +msgid "" +"This is the name of the state and what you and your agents are seeing when " +"choosing a state somewhere (e.g. in tickets, trigger configuration)." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Customer``, ``Agent`` or ``System``" +#: ../system/objects.rst:137 +msgid "" +"There are different state types you can choose from. By default, Zammad " +"comes with one state per state type." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Visibility" +#: ../system/objects.rst:140 +msgid "" +"**new**: for states for tickets that are new and it hasn't been worked on " +"them" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.internal}``" +#: ../system/objects.rst:142 +msgid "" +"**open**: for states for tickets that are in progress and agents are working " +"on them" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``false`` or ``true`` (false if not internal)" +#: ../system/objects.rst:144 +msgid "**merged**: for states for tickets that are merged with other tickets" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > From" +#: ../system/objects.rst:145 +msgid "" +"**pending reminder**: for states for tickets that are in progress and you " +"want to set a reminder. (default example: *pending reminder*)" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.from}``" +#: ../system/objects.rst:147 +msgid "" +"**pending action**: for states for tickets that are waiting for a specified " +"time and then change their state (default example: *pending close*)" msgstr "" -#: ../system/variables/article.rst:1 +#: ../system/objects.rst:150 msgid "" -"``Joe Doe `` may differ, depends on ``FROM`` of send mail" +"**closed**: for states for tickets that are finished and do not need to be " +"processed further" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Web" +#: ../system/objects.rst:153 +msgid "" +"⚠️ Choosing the correct state type is important! If you are in doubt, have a " +"look on the default states and their types!" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.web}``" +#: ../system/objects.rst:158 +msgid "Ignore escalation" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > VIP" +#: ../system/objects.rst:157 +msgid "" +"Here you can define whether tickets of this state will count to escalation " +"time or not." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.vip}``" +#: ../system/objects.rst:161 +msgid "" +"You can create a note for the state to inform other admins about the state. " +"This has no effect on tickets." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Phone" +#: ../system/objects.rst:165 +msgid "Set the state to *active* or *inactive*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.phone}``" +#: ../system/objects.rst:167 +msgid "" +"it is technically possible to set all states to inactive. To keep Zammad " +"working in such a case, the inactive flag of one of the states is ignored." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Note" +#: ../system/objects.rst:194 +msgid "Ticket state example" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.note}``" +#: ../system/objects.rst:174 +msgid "" +"Let's assume we want to create a new state which indicates that the ticket " +"has to wait for a response of a third party (e.g. service contractor or " +"manufacturer) and we want to to be able to set a reminder." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Mobile" +#: ../system/objects.rst:178 +msgid "" +"First we give the new state a proper name. In this example we call it " +"\"waiting for manufacturer\"." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.mobile}``" +#: ../system/objects.rst:181 +msgid "" +"As state type we choose \"pending reminder\". This indicates that the ticket " +"is still open and we can set a reminder. This reminder can be useful if our " +"manufacturer sometimes isn't responding or we want to remind him to give us " +"an answer." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Login" +#: ../system/objects.rst:186 +msgid "" +"We choose \"no\" for \"ignore escalation\" because we want to escalate the " +"tickets even if we are waiting on the manufacturer's feedback." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.login}``" -msgstr "" +#: ../system/objects.rst:189 +#, fuzzy +msgid "The **result** in the creation dialog will look like this:" +msgstr "最终结果将如下所示：" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Lastname" +#: ../system/objects.rst:0 +msgid "Screenshot showing ticket state creation dialog with example" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.lastname}``" -msgstr "" +#: ../system/objects.rst:199 +#, fuzzy +msgid "Ticket Priority" +msgstr "优先级" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Firstname" +#: ../system/objects.rst:201 +msgid "" +"If the pre-configured priorities aren't enough for you or you want to change " +"them, you can do so by clicking on the cogwheel icon in the priority row in " +"the ticket tab:" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.firstname}``" +#: ../system/objects.rst:None +msgid "Screenshot showing highlighted ticket priority attribute" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Fax" +#: ../system/objects.rst:226 +msgid "Handling of priorities" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.fax}``" +#: ../system/objects.rst:210 +msgid "" +"In the priority configuration screen, you can add new priorities, disable " +"priorities or change priorities." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Email" +#: ../system/objects.rst:0 +msgid "Screenshot showing table of default ticket priorities" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.email}``" +#: ../system/objects.rst:218 +msgid "" +"To add a new priority, click on the \"New Priority\" button in the top right " +"corner. To change an existing priority, simply click on the affected " +"priority. This opens an edit dialog." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Department" +#: ../system/objects.rst:222 +msgid "" +"You can also clone a priority or set them to \"Default for new tickets\" by " +"clicking on the ⁝ action button and select the desired function." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.department}``" +#: ../system/objects.rst:225 +msgid "" +"*Default for new tickets* means that this priority is used for every newly " +"created ticket." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created by > Address" +#: ../system/objects.rst:248 +msgid "Priorities in detail" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_by.address}``" +#: ../system/objects.rst:229 +msgid "Below you can find a description for each field and option." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Created" +#: ../system/objects.rst:232 +msgid "" +"This is the name of the priority and what you and your agents are seeing " +"when choosing a priority somewhere (e.g. in tickets, trigger configuration)." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.created_at}``" +#: ../system/objects.rst:242 +msgid "Highlight color" msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Cc" +#: ../system/objects.rst:237 +msgid "" +"Switch between *Low priority* (light blue), *High priority* (red) and - " +"(default). This affects the displayed color for ticket titles in overviews." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.cc}``" +#: ../system/objects.rst:241 +msgid "The color options are currently limited to the mentioned options." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``jdoe@example.com, company@example.com``" +#: ../system/objects.rst:245 +msgid "" +"You can create a note for the priority to inform other admins about the " +"priority. This has no effect on tickets." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article > Text" +#: ../system/objects.rst:249 +msgid "Set the priority to *active* or *inactive*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.body}``" +#: ../system/objects/external-data-source-example.rst:2 +msgid "External Data Source" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Test`` without formatting (plain)" +#: ../system/objects/external-data-source-example.rst:4 +msgid "" +"We assume you already had a look on :doc:`types` where you can find a " +"description of the individual fields." msgstr "" -#: ../system/variables/article.rst:1 -msgid "Article Text as HTML (not referenced)" +#: ../system/objects/external-data-source-example.rst:7 +msgid "" +"To reproduce this example, choose a category you want to add a custom field, " +"click on *New Attribute* and select *External data source field* under " +"*Format*." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``#{article.body_as_html}``" +#: ../system/objects/external-data-source-example.rst:11 +msgid "" +"Our example story is to fetch data from an external product database. We " +"want to add our products to the tickets so that the products can be searched " +"and chosen from a list and also create a link to the product website." msgstr "" -#: ../system/variables/article.rst:1 -msgid "``Test`` with formatting" +#: ../system/objects/external-data-source-example.rst:16 +msgid "Base configuration" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "Ticket > Article#" +#: ../system/objects/external-data-source-example.rst:None +msgid "Initial steps to configure external data source object type" msgstr "" -#: ../system/variables/article.rst:1 ../system/variables/ticket.rst:1 -msgid "``#{ticket.article_count}``" +#: ../system/objects/external-data-source-example.rst:25 +msgid "Name: *product*" msgstr "" -#: ../system/variables/article.rst:1 -msgid "``1`` number of ticket articles" +#: ../system/objects/external-data-source-example.rst:26 +msgid "Display: *Product*" msgstr "" -#: ../system/variables/config.rst:2 -msgid "Config" +#: ../system/objects/external-data-source-example.rst:29 +msgid "External data source configuration" msgstr "" -#: ../system/variables/config.rst:6 +#: ../system/objects/external-data-source-example.rst:31 msgid "" -"Below you'll find config related variables. These hold useful configuration " -"information that you can use within e.g. triggers to show necessary " -"information to your customer." +"First, enter the search URL making sure it contains ``#{search.term}`` as a " +"parameter:" msgstr "" -#: ../system/variables/config.rst:11 -msgid "Config Variables" +#: ../system/objects/external-data-source-example.rst:34 +msgid "**Example:** ``https://dummyjson.com/products/search?q=#{search.term}``" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Fully Qualified Domain Name" +#: ../system/objects/external-data-source-example.rst:36 +msgid "" +"After that, head down to the preview section and enter a search input for " +"the external data source." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.fqdn}``" +#: ../system/objects/external-data-source-example.rst:39 +msgid "**Example:** ``mac``" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``zammad.example.com``" +#: ../system/objects/external-data-source-example.rst:41 +msgid "Then you can find a preview of the response data below:" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Ticket Hook" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of JSON response based on search term" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.ticket_hook}``" +#: ../system/objects/external-data-source-example.rst:48 +msgid "" +"We recommend using the preview to have a look on the structure. There is a " +"top-level element called ``products``. One level below, you can find the " +"attributes ``id`` and ``title``." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``Ticket#``" +#: ../system/objects/external-data-source-example.rst:52 +msgid "**Search result response based on search from example:**" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > HTTP type" +#: ../system/objects/external-data-source-example.rst:119 +msgid "" +"To tell the remote system that the desired data is located below the " +"``products`` level, you have to put it in the field *Search result list key*." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.http_type}``" +#: ../system/objects/external-data-source-example.rst:122 +msgid "" +"After inserting ``products`` in the mentioned field, you get an extended " +"preview. You can find an additional box *Search result list* with a JSON " +"structure. This is the same response as before but stripped from the upper " +"``products`` element by the external data source." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``https`` or ``http``" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of JSON response search result list" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > SystemID" +#: ../system/objects/external-data-source-example.rst:132 +msgid "" +"Now you need to provide the keys for the search result values and labels. As " +"already mentioned, we are looking for the ``id`` and the ``title`` of our " +"products. If you haven't already, it is now a good time to look at the " +"preview of the *Search result list*." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.system_id}``" +#: ../system/objects/external-data-source-example.rst:197 +msgid "" +"After locating our two keys, we insert them in *search result value key* " +"(``id``) and in *Search result label key* (``title``)." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``31`` (value between 1 and 99)" +#: ../system/objects/external-data-source-example.rst:200 +msgid "" +"Basically, we configured the external data source already and we can see a " +"table in the preview section:" msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Organization" +#: ../system/objects/external-data-source-example.rst:None +msgid "Preview of product table based on search term" msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.organization}``" +#: ../system/objects/external-data-source-example.rst:208 +msgid "" +"According to our example story, now just the *Link template* is missing." msgstr "" -#: ../system/variables/config.rst:1 +#: ../system/objects/external-data-source-example.rst:210 msgid "" -"``Zammad GmbH`` value set in `Branding `_" +"Please note that this is an optional feature. If you don't want to use such " +"links, of course you don't have to configure it." msgstr "" -#: ../system/variables/config.rst:1 -msgid "Config > Product Name" +#: ../system/objects/external-data-source-example.rst:213 +msgid "" +"We can add now an address where additional product information can be found." msgstr "" -#: ../system/variables/config.rst:1 -msgid "``#{config.product_name}``" +#: ../system/objects/external-data-source-example.rst:215 +msgid "Example: ``https://your_domain.com/q=#{ticket.product}``" msgstr "" -#: ../system/variables/config.rst:1 -msgid "" -"``Helpdesk`` value set in `Branding `_" +#: ../system/objects/external-data-source-example.rst:217 +msgid "In the example, the parameter means:" msgstr "" -#: ../system/variables/current-user.rst:2 -msgid "Current User" +#: ../system/objects/external-data-source-example.rst:219 +msgid "``#{}``: \"Frame\" for the insertion of information" msgstr "" -#: ../system/variables/current-user.rst:6 -msgid "" -"Current user variables always return values of the current user that caused " -"e.g. a trigger to run." +#: ../system/objects/external-data-source-example.rst:220 +msgid "``ticket``: object level, where you create your custom object" msgstr "" -#: ../system/variables/current-user.rst:8 -msgid "" -"Due to the above fact, these variables are often not (yet) set or available " -"for usage." +#: ../system/objects/external-data-source-example.rst:221 +msgid "``product``: name of the (custom) object" msgstr "" -#: ../system/variables/current-user.rst:10 +#: ../system/objects/external-data-source-example.rst:223 msgid "" -"In situations where e.g. schedulers or triggers run, this most likely is " -"nothing you want to use." -msgstr "" - -#: ../system/variables/current-user.rst:13 -msgid "Current User Variables" +"After configuring your *Link template*, there will be another column in the " +"preview. Hovering on the icons in the *Link* column will show you where it " +"forwards you." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Web" +#: ../system/objects/external-data-source-example.rst:232 +msgid "" +"In our example, one of the links looks like: https://your_domain.com/q=6, " +"where the 6 is the product id." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.web}``" -msgstr "" +#: ../system/objects/external-data-source-example.rst:235 +#, fuzzy +msgid "You can find more information regarding the URL in :doc:`types`." +msgstr "您还可以在管理员区域中找到有关聊天自定义的更多信息。" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``https://zammad.org`` or empty if not set" +#: ../system/objects/includes/adding-values-hint.include.rst:3 +msgid "" +"Adding values can be tricky for first timers, don't forget to press \"➕ " +"Add\" after typing your values. Otherwise you may loose a value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > VIP" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:1 +#: ../system/objects/includes/reposition-values.include.rst:1 +msgid "**↕️ This field type allows the positioning of its values ↔️**" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.vip}``" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:3 +msgid "" +"In order to re-arrange the field values, first edit the field. Then you can " +"use ☰ to drag the values in question to the correct position. If you want to " +"change the layer depth, double click on ☰. With it you can cycle through the " +"available layers." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``false`` or ``true``" +#: ../system/objects/includes/reposition-treeselect-values.include.rst:8 +msgid "When you're ready, submit your changes to save the object attribute." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Web" +#: :0 ../system/objects/types.rst:0 +msgid "" +"Screencast showing how to re-position values on tree select like\n" +"fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.web}``" +#: ../system/objects/includes/reposition-values.include.rst:3 +msgid "" +"In order to re-arrange the field values, edit the field and scroll below the " +"values. Make sure to tick the option \"Use custom option sort\"." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > VIP" +#: ../system/objects/includes/reposition-values.include.rst:8 +msgid "" +"If you do not tick this field, all manual positioning you did above will be " +"lost upon saving! ☠️" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.vip}``" +#: ../system/objects/includes/reposition-values.include.rst:11 +msgid "" +"Now use ☰ to drag the values in question to the correct position. When " +"you're ready, submit your changes to save the object attribute." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Phone" +#: :0 ../system/objects/types.rst:0 +msgid "Screencast showing how to re-position values" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.phone}``" +#: ../system/objects/includes/url-template-hint.include.rst:3 +msgid "" +"This field allows using :ref:`URL fields (Link Templates) `." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``004930123456789`` or empty if not set" +#: ../system/objects/permissions.rst:2 +msgid "Attribute Permissions" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Note" +#: ../system/objects/permissions.rst:7 +msgid "" +"In the object attributes configuration you can define if a field is shown " +"and if the input in the field is mandatory, separated by different screens " +"and for different :doc:`roles/permissions `." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.note}``" +#: ../system/objects/permissions.rst:17 +msgid "Screenshot shows object attribute permission table" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Some note to this user`` or empty if not set" +#: ../system/objects/permissions.rst:17 +msgid "" +"Some of the possible permissions and screen options for a user object " +"attribute." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Mobile" +#: ../system/objects/permissions.rst:19 +msgid "" +"Based on the object context (ticket, agent, organization, user), the " +"selectable roles (to be precise: the required permissions) and screens " +"differ. Be aware that these settings aren't affecting data creation via " +"other channels than the UI." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.mobile}``" +#: ../system/objects/permissions.rst:24 +msgid "" +"If you want to have further customization possibilities, you should have a " +"look at the :doc:`core workflows `." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``0049176123456789`` or empty if not set" +#: ../system/objects/permissions.rst:28 +msgid "Screens" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Login" +#: ../system/objects/permissions.rst:30 +msgid "" +"In the table below you can find an overview about the different permissions " +"and the available screens Zammad distinguishes between." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.login}``" +#: ../system/objects/permissions.rst:37 +msgid "Screen" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Lastname" +#: ../system/objects/permissions.rst:38 +msgid "Available for" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.lastname}``" +#: ../system/objects/permissions.rst:40 +msgid "create" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Firstname" +#: ../system/objects/permissions.rst:41 ../system/objects/permissions.rst:52 +#: ../system/objects/permissions.rst:59 ../system/objects/permissions.rst:73 +msgid "admin.user" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.firstname}``" +#: ../system/objects/permissions.rst:42 ../system/objects/permissions.rst:53 +#: ../system/objects/permissions.rst:60 +msgid "admin.organization" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``John`` or empty if not set" -msgstr "" +#: ../system/objects/permissions.rst:43 ../system/objects/permissions.rst:54 +#: ../system/objects/permissions.rst:61 +#, fuzzy +msgid "admin.group" +msgstr "组" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Fax" +#: ../system/objects/permissions.rst:44 +msgid "Creation dialog for not yet existing data" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.fax}``" +#: ../system/objects/permissions.rst:45 +msgid "create_middle" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``004930123464789`` or empty if not set" -msgstr "" +#: ../system/objects/permissions.rst:46 ../system/objects/permissions.rst:50 +#: ../system/objects/permissions.rst:57 ../system/objects/permissions.rst:66 +#: ../system/objects/permissions.rst:70 +#, fuzzy +msgid "ticket.customer" +msgstr "宏" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Email" -msgstr "" +#: ../system/objects/permissions.rst:47 ../system/objects/permissions.rst:51 +#: ../system/objects/permissions.rst:58 ../system/objects/permissions.rst:69 +#, fuzzy +msgid "ticket.agent" +msgstr "宏" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.email}``" +#: ../system/objects/permissions.rst:48 +msgid "Ticket create dialog (middle section)" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``jdoe@customer.tld``" +#: ../system/objects/permissions.rst:49 +msgid "edit" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Department" +#: ../system/objects/permissions.rst:55 +msgid "Editing dialog for already existing data" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.department}``" +#: ../system/objects/permissions.rst:56 +msgid "view" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Sales`` or empty if not set" +#: ../system/objects/permissions.rst:62 +msgid "View-only dialog for already existing data" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Avatar" +#: ../system/objects/permissions.rst:64 +msgid "(e.g. user or organization from search)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.avatar(60,60)}``" +#: ../system/objects/permissions.rst:65 +msgid "signup" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "avatar picture with width and height in pixel (e.g. 60,60)" +#: ../system/objects/permissions.rst:67 +msgid "Sign-up screen for new customers" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated by > Address" +#: ../system/objects/permissions.rst:68 +msgid "invite_customer" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_by.address}``" +#: ../system/objects/permissions.rst:71 +msgid "" +"Customer invitation screen (from :doc:`First Steps ` area)" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``Some street 1, 12345 Berlin`` or empty if not set" +#: ../system/objects/permissions.rst:72 +msgid "invite_agent" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Updated at" +#: ../system/objects/permissions.rst:74 +msgid "" +"Agent invitation screen (from :doc:`First Steps ` area)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.updated_at}``" +#: ../system/objects/permissions.rst:78 +msgid "Screen Options" msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC``" +#: ../system/objects/permissions.rst:80 +msgid "" +"For the different screens you can select \"show\" and \"required\" options." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Phone" +#: ../system/objects/permissions.rst:82 +msgid "**shown:** Show (check) or hide (uncheck) a field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.phone}``" +#: ../system/objects/permissions.rst:83 +msgid "" +"**required:** Set a field to mandatory (check). Forces users (via UI and " +"API) to populate the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Shared organization" +#: ../system/objects/types.rst:7 +msgid "Example external data source" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.shared}``" +#: ../system/objects/types.rst:2 +msgid "Attribute types" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Note" +#: ../system/objects/types.rst:4 +msgid "" +"When adding a new object attribute, you can choose between the following " +"attribute types." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.note}``" +#: ../system/objects/types.rst:14 +msgid "" +"You cannot change the attribute format / type as soon as it is applied. If " +"you no longer need an object attribute, consider disabling it instead of " +"removing." msgstr "" -#: ../system/variables/current-user.rst:1 ../system/variables/ticket.rst:1 -msgid "``A note to the organization of the user`` or empty if not set" +#: ../system/objects/types.rst:18 +msgid "**What about the translation of my attributes?**" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Name" +#: ../system/objects/types.rst:20 +msgid "" +"For some attribute types you can decide if they should be translatable or " +"not. To be precise, it works only for the selectable fields because the " +"possible choices are known and limited. For the following attribute types, " +"you can set the translatable flag:" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.name}``" +#: ../system/objects/types.rst:25 +msgid "*Boolean field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``Zammad GmbH``" +#: ../system/objects/types.rst:26 +msgid "*Single selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Domain based assignment" +#: ../system/objects/types.rst:27 +msgid "*Multiple selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.domain_assignment}``" +#: ../system/objects/types.rst:28 +msgid "*Single tree selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > Domain" +#: ../system/objects/types.rst:29 +msgid "*Multiple tree selection field*" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.domain}``" +#: ../system/objects/types.rst:31 +msgid "" +"For these types, you can find an additional field *Translate field contents*:" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``zammad.com`` or empty if not set" +#: ../system/objects/types.rst:0 +msgid "Screenshot showing translatable attribute types" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Organization > VIP" +#: ../system/objects/types.rst:38 +msgid "Screenshot with example of translatable attribute type" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.organization.vip}``" +#: ../system/objects/types.rst:45 +msgid "Boolean field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Note" +#: ../system/objects/types.rst:41 +msgid "" +"Provides a drop-down field with display values for ``true`` and ``false``. " +"Setting a default is mandatory." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.note}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Boolean fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Mobile" +#: ../system/objects/types.rst:55 +msgid "Date field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.mobile}``" +#: ../system/objects/types.rst:48 +msgid "Provides a date picker field and does not allow default values." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Login" +#: ../system/objects/types.rst:52 +msgid "Default time diff (hours)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.login}``" +#: ../system/objects/types.rst:51 +msgid "" +"This setting helps the user by highlighting the day from now plus the " +"provided value. It *does not* pre-fill the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Lastname" +#: ../system/objects/types.rst:0 +msgid "Available settings for Date fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.lastname}``" +#: ../system/objects/types.rst:73 +msgid "Date & time field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Firstname" +#: ../system/objects/types.rst:58 +msgid "Provides a date and time picker – does not allow default values" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.firstname}``" +#: ../system/objects/types.rst:62 +msgid "Allow future" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Fax" +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the future." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.fax}``" +#: ../system/objects/types.rst:66 +msgid "Allow past" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Email" +#: ../system/objects/types.rst:0 +msgid "Forbid dates and times in the past." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.email}``" +#: ../system/objects/types.rst:70 +msgid "Default time diff (minutes)" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Department" +#: ../system/objects/types.rst:69 +msgid "" +"This setting helps the user by highlighting the day from now plus the " +"provided value. It does not pre-fill the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.department}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Date & time fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Web" +#: ../system/objects/types.rst:86 +msgid "Integer field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.web}``" +#: ../system/objects/types.rst:76 +msgid "" +"Provides an input field that allows integer usage only. You may define a " +"default value. You cannot enforce comma separation." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > VIP" +#: ../system/objects/types.rst:80 +msgid "Minimal" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.vip}``" +#: ../system/objects/types.rst:80 +msgid "The minimal value the field accepts." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Phone" +#: ../system/objects/types.rst:83 +msgid "Maximal" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.phone}``" +#: ../system/objects/types.rst:83 +msgid "The maximum value the field accepts." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Note" +#: ../system/objects/types.rst:0 +msgid "Available settings for Integer fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.note}``" +#: ../system/objects/types.rst:99 +msgid "Multiple selection field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Mobile" +#: ../system/objects/types.rst:89 +msgid "" +"Provides a selection field that allows the selection of one or more out of " +"several. This field does allow setting a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.mobile}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Multiple selection fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Login" +#: ../system/objects/types.rst:112 +msgid "Single selection field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.login}``" +#: ../system/objects/types.rst:102 +msgid "" +"Provides a drop-down field that allows selection of one value out of " +"several. This field does allow setting a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Lastname" +#: ../system/objects/types.rst:0 +msgid "Available settings for Single selection fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.lastname}``" +#: ../system/objects/types.rst:142 +msgid "Textarea field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Firstname" +#: ../system/objects/types.rst:115 +msgid "" +"Provides a text area input field (multiple lines) and thus allows e.g. new " +"lines. You can set a default field value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.firstname}``" +#: ../system/objects/types.rst:120 +msgid "" +"Please note that this field *does not* support text formatting or HTML " +"content (rich text)." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Fax" +#: ../system/objects/types.rst:123 +msgid "**🥵 This field can consume a lot of visual space**" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.fax}``" +#: ../system/objects/types.rst:125 +msgid "" +"Depending on where you use this field type, it may use a lot of visual space " +"if you provide a lot of text. This may be an issue to work with." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Email" +#: ../system/objects/types.rst:130 +msgid "Default" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.email}``" +#: ../system/objects/types.rst:129 +msgid "" +"The here provided text will be shown within the text area field or new data " +"sets." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Department" +#: ../system/objects/types.rst:134 ../system/objects/types.rst:160 +msgid "Maxlength" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.department}``" +#: ../system/objects/types.rst:0 ../system/objects/types.rst:160 +msgid "You can pick the maximum length of the field." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Avatar" +#: ../system/objects/types.rst:0 +msgid "The default length of this object is ``500``." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.avatar(60,60)}``" +#: ../system/objects/types.rst:139 +msgid "Rows" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created by > Address" +#: ../system/objects/types.rst:0 +msgid "" +"Change the number of rows to dislay so that you can use only the space you " +"really need." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_by.address}``" +#: ../system/objects/types.rst:0 +msgid "The default number of rows is ``4``." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Created at" +#: ../system/objects/types.rst:0 +msgid "Available settings for Textarea fields" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.created_at}``" +#: ../system/objects/types.rst:165 +msgid "Text field" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Avatar" +#: ../system/objects/types.rst:145 +msgid "Provides a text field (one line) and allows choosing a default value." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.avatar(60,60)}``" +#: ../system/objects/types.rst:148 +msgid "" +"Defines the type of the input field. This allows e.g. your browser to ensure " +"that you provide the specific type." msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "Current User > Address" +#: ../system/objects/types.rst:152 +msgid "Currently available:" msgstr "" -#: ../system/variables/current-user.rst:1 -msgid "``#{user.address}``" +#: ../system/objects/types.rst:155 +msgid "Phone" msgstr "" -#: ../system/variables/ticket.rst:6 -msgid "" -"Below you can find all available ticket-based variables within Zammad. These " -"can be called via Triggers for example. If you're unsure if Zammad does " -"support variables at the point you're at, you can try to type ``::`` to " -"check." +#: ../system/objects/types.rst:156 +msgid "Text" msgstr "" -#: ../system/variables/ticket.rst:12 -msgid "Ticket Variables" +#: ../system/objects/types.rst:157 +msgid "Url *(URL fields disable link-template availability)*" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Web" +#: ../system/objects/types.rst:0 +msgid "Available settings for Text fields" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.web}``" +#: ../system/objects/types.rst:174 +msgid "Single tree selection field" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > VIP" +#: ../system/objects/types.rst:168 +msgid "" +"Provides a select-like field with up to 6 layers of options. Does not allow " +"setting a default value." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.vip}``" +#: ../system/objects/types.rst:0 +msgid "Available settings for Tree Select fields" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Phone" +#: ../system/objects/types.rst:183 +msgid "Multiple tree selection field" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.phone}``" +#: ../system/objects/types.rst:177 +msgid "" +"Provides a select-like field with up to 6 layers of options allowing the " +"selection of multiple values. Does not allow setting a default value." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Note" +#: ../system/objects/types.rst:302 +msgid "External Data Source field" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.note}``" +#: ../system/objects/types.rst:186 +msgid "" +"Provides a searchable field which fetches data from an external system. This " +"can be useful if you have data outside of Zammad and don't want to maintain " +"both data sources." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Mobile" +#: ../system/objects/types.rst:190 +msgid "The feature works as follows:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.mobile}``" +#: ../system/objects/types.rst:192 +msgid "" +"Zammad sends a query with a search string (free text from agent or based on " +"a variable) in a pre-defined format (\"Search URL\") to an external system." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Login" +#: ../system/objects/types.rst:195 +msgid "" +"This external system searches for matches and provides a response as a JSON " +"structure to Zammad." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.login}``" +#: ../system/objects/types.rst:197 +msgid "" +"Zammad just looks for the defined list and value keys, reads the content and " +"displays the value to the user. There is no search on Zammad side." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Lastname" +#: ../system/objects/types.rst:201 +msgid "" +"The usage of a PostgreSQL database for Zammad is required. In any other " +"case, Zammad will hide the external data source type and you are not able to " +"use it. If you want to use this feature, consider to :docs:`migrate your " +"database `." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.lastname}``" +#: ../system/objects/types.rst:205 +msgid "Currently, only ``GET`` is supported as request method." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Firstname" +#: ../system/objects/types.rst:206 +msgid "" +"The data structure must be in JSON format and provide the objects in an " +"array." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.firstname}``" +#: ../system/objects/types.rst:208 +msgid "" +"The endpoint for the external data source has to support search. On Zammad " +"side, there is no search/logic implemented; however, you can define the " +"output key and value based on the result(s) from the response (which " +"provides already filtered content based on the search)." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Fax" +#: ../system/objects/types.rst:212 +msgid "" +"If you receive more results as expected, your external data source search " +"may not work properly or the structure of the URL is not correct. You should " +"get in touch with a responsible person from the external system." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.fax}``" +#: ../system/objects/types.rst:217 +msgid "" +"Please have a look :doc:`at our example `, where you can find a possible configuration for a public " +"dummy endpoint." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Email" +#: ../system/objects/types.rst:0 +msgid "Available settings for external data source fields" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.email}``" +#: ../system/objects/types.rst:242 +msgid "Search URL" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Department" +#: ../system/objects/types.rst:227 +msgid "" +"Set your endpoint where Zammad fetches the data. Please make sure to include " +"a valid search :doc:`variable ` as an URL parameter. " +"Example for a free text search at user input: ``#{search.term}``" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.department}``" +#: ../system/objects/types.rst:232 +msgid "" +"If in doubt, ask the responsible person for the external data source how " +"they expect the structure of the URL." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Avatar" +#: ../system/objects/types.rst:236 +msgid "" +"Depending on your search variable, the preview might work or not. The reason " +"is that the context might not be available and it is no bug." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.avatar(60,60)}``" +#: ../system/objects/types.rst:239 +msgid "" +"Please also make sure to use a variable which is available in your object " +"context. For example you won't be able to search for a ticket in a user " +"object context." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated by > Address" +#: ../system/objects/types.rst:252 +msgid "SSL Verification" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_by.address}``" +#: ../system/objects/types.rst:245 +msgid "Here you can switch the SSL verification to no." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Updated at" +#: ../system/objects/types.rst:249 +msgid "" +"If your external data source system is using self signed certificates, " +"please have a look :doc:`here ` for " +"further information about how to handle them in Zammad, so you can keep the " +"SSL verification activated." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.updated_at}``" +#: ../system/objects/types.rst:258 +msgid "HTTP Authentication" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Title" +#: ../system/objects/types.rst:255 +msgid "" +"If your external data source requires an authentication, you can set it " +"here. You can leave it empty or choose between *Basic Authentication* or " +"*Authentication Token* (selecting one of the two methods leads to additional " +"fields where you can enter your credentials/token)." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.title}``" +#: ../system/objects/types.rst:265 +msgid "Search result list key" msgstr "" -#: ../system/variables/ticket.rst:1 +#: ../system/objects/types.rst:261 msgid "" -"``My amazing Subject`` (normally subject, can be edited within Interface and " -"thus differ)" +"Defines the level in the JSON structure which provides the list with search " +"results. You can leave it empty, if the data is already provided as an " +"array. If you have to go deeper in the structure, you can provide a path " +"with ``.`` as separators, e.g. ``key.subkey.sub-sub-key``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Accounted Time" +#: ../system/objects/types.rst:271 +msgid "Search result value key" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.time_unit}``" +#: ../system/objects/types.rst:268 +msgid "" +"Defines the attribute in the structure in which your external data source " +"provides the *value* for your data. An example would be a product *number*. " +"If you have to go deeper in the structure, you can provide a path with ``.`` " +"as separators, e.g. ``key.subkey.sub-sub-key``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``1``, ``2.75`` or empty response" +#: ../system/objects/types.rst:277 +msgid "Search result label key" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Tags" +#: ../system/objects/types.rst:274 +msgid "" +"Defines the attribute in the structure in which your external data source " +"provides the *label* for your data. An example would be a product *name*. If " +"you have to go deeper in the structure, you can provide a path with ``.`` as " +"separators, e.g. ``key.subkey.sub-sub-key``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.tags}``" +#: ../system/objects/types.rst:280 +msgid "" +"In the preview area, you can find the following items (depending on your " +"configuration above):" msgstr "" -#: ../system/variables/ticket.rst:1 +#: ../system/objects/types.rst:283 msgid "" -"Currently not available, see `Issue 2769 `_" +"**Error/hint message** (only if configuration is not complete): Zammad tells " +"you, if there is a problem and what you should change in your configuration." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > State > Name" +#: ../system/objects/types.rst:286 +msgid "" +"**Search field**: search for an existing attribute in the data source to get " +"a preview. This is required for the fields below to show up." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.state.name}``" +#: ../system/objects/types.rst:288 +msgid "" +"**Search result response** (only if configuration is not complete): here you " +"can find a syntax highlighted JSON preview of the response, based on the " +"search term you entered." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``new``, ``open``, ..." +#: ../system/objects/types.rst:291 +msgid "" +"**Search result list** (only if *search result list key* is properly set): " +"output of the structure under the configured *search result list key*." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Priority > Name" +#: ../system/objects/types.rst:294 +msgid "" +"**Preview table** (when fully configured): Zammad shows you a table which " +"includes the found items based on the search string (value, label and " +"optional link). You can use this preview if you don't have the complete data " +"structure of the external system in mind." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.priority.name}``" +#: ../system/objects/types.rst:299 +msgid "" +"An example of a configured external data source field from agent perspective:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2 normal``" +#: ../system/objects/types.rst:0 +msgid "Screencast showing the search for a product in a ticket" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Pending till" +#: ../system/objects/types.rst:307 +msgid "URL fields (Link-Template)" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.pending_time}``" +#: ../system/objects/types.rst:311 +msgid "" +"This function is restricted to Text, Select and External data source types " +"only." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not set" +#: ../system/objects/types.rst:314 +msgid "" +"Link-Templates are an amazing way to dynamically generate URLs. They allow " +"you to integrate other systems better without having to manually copy data " +"from Zammad if possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Web" +#: ../system/objects/types.rst:320 +msgid "" +"Another great way of communicating with another system may be Zammad's :doc:" +"`Webhooks `." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.web}``" +#: ../system/objects/types.rst:323 +msgid "" +"After filling a link-template enabled field, an URL icon will appear on its " +"right. Clicking on the icon opens a new tab." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``https://zammad.com`` or empty if not set" +#: ../system/objects/types.rst:328 +msgid "" +"Even though Zammad displays the link template within object edit and create " +"screens, the function is optional. It's only active if you populate the " +"field." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > VIP" +#: ../system/objects/types.rst:333 +msgid "" +"What's the difference between URL and text fields with link template...?!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.vip}``" +#: ../system/objects/types.rst:335 +msgid "" +"Both fields have different use cases. Use ``text`` type text fields when " +"ever you have a *static* url that requires dynamic parameters. If you " +"require a drag & drop like field that you can put in any URL, use ``URL`` " +"type text fields." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Phone" +#: ../system/objects/types.rst:340 +msgid "" +"The difference is easier to spot when comparing the fields directly, below " +"screencast shows the result - the dynamic approach uses existing values in " +"the moment of updating to built the URL - e.g. ``https://google.com/search?" +"q=cookies`` - while the URL approach uses the actual URL of the field - e.g. " +"``https://zammad.com``." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.phone}``" +#: ../system/objects/types.rst:None +msgid "" +"Screencast showing the differents in between URL and text type fields with " +"actual values" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Note" +#: ../system/objects/types.rst:352 +msgid "How does this work...?!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.note}``" +#: ../system/objects/types.rst:354 +msgid "" +"As an example, let's say you have an attribute called ``amazing_attribute`` " +"and you want to open a google search directly with the input from that field." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Mobile" +#: ../system/objects/types.rst:357 +msgid "" +"Providing the link-template field below allows you to do so: ``https://www." +"google.com/search?q=#{ticket.amazing_attribute}``" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.mobile}``" +#: ../system/objects/types.rst:362 +msgid "" +"You can use any :doc:`Zammad variable ` as long as it's " +"available in the moment you need it." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Login" +#: ../system/objects/types.rst:365 +msgid "" +"As a result, you are redirected to Google with a search for the value of the " +"attribute, if you click on the button in the ticket (as you can see in the " +"screencast above)." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.login}``" +#: ../system/packages.rst:2 +msgid "Packages" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``agent``" +#: ../system/packages.rst:4 +msgid "That's the package management-area." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Lastname" +#: ../system/packages.rst:6 +msgid "Individual add-ons for Zammad can be installed and managed here." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.lastname}``" +#: ../system/sessions.rst:2 +msgid "Sessions" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Mustermann`` or empty if not set" +#: ../system/sessions.rst:4 +msgid "" +"Sessions management allows reviewing currently known user sessions and " +"allows to end these. The session timeout is affected by :ref:" +"`security_session_timeout` configurations from security settings." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Firstname" +#: ../system/sessions.rst:None +msgid "Screenshot showing Zammad's session management" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.firstname}``" +#: ../system/sessions.rst:13 +msgid "Zammad will provide the following information:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Max`` or empty if not set" +#: ../system/sessions.rst:16 +msgid "" +"The user account this session entry belongs to. It can be normal if a user " +"has several sessions in the list. This can be due to changed browser " +"information or if you use e.g. single sign on methods where the user does " +"not use the log off button." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Fax" +#: ../system/sessions.rst:22 +msgid "Browser" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.fax}``" +#: ../system/sessions.rst:22 +msgid "The browser agent communicated to Zammad." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Email" +#: ../system/sessions.rst:40 +msgid "Location" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.email}``" +#: ../system/sessions.rst:25 +msgid "" +"The anticipated location based on the users IP address. Depending on the IP " +"address the result shown may differ. This option depends on :doc:`/settings/" +"system/services`." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``agent@company.tld`` or empty if not set" +#: ../system/sessions.rst:29 +msgid "The following information can be shown:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Department" +#: ../system/sessions.rst:33 +msgid "IP address" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.department}``" +#: ../system/sessions.rst:32 +msgid "" +"Either if you set *Geo IP services* to inactive or you're using internal IP " +"address which do not provide location information." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Support`` or empty if not set" +#: ../system/sessions.rst:40 +msgid "Country (or Country + City)" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Avatar" +#: ../system/sessions.rst:36 +msgid "" +"If *Geo IP services* is enabled only. Depends on how detailed the available " +"IP address information are." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.avatar(60,60)}``" +#: ../system/sessions.rst:39 +msgid "" +"Be aware that results can be inaccurate - this technically is not an error." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Owner > Address" +#: ../system/sessions.rst:43 +msgid "Age" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.owner.address}``" +#: ../system/sessions.rst:43 +msgid "Provides the time when the session initially has been created." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Shared organization" +#: ../system/sessions.rst:50 +msgid "Update" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.shared}``" +#: ../system/sessions.rst:46 +msgid "" +"Provides the time the user used this session to open Zammad. This timestamp " +"is only updated if the user e.g. reloads, not during normal work on tickets." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Note" +#: ../system/sessions.rst:50 +msgid "This timestamp is being used for the session timeout." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.note}``" +#: ../system/sessions.rst:53 +msgid "" +"Use the delete button to remove a single session on behalf of your user." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Name" +#: ../system/subscription.rst:2 +msgid "Subscription (SaaS)" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.name}``" +#: ../system/subscription.rst:4 +msgid "" +"The subscription settings page allows you to configure your instances " +"package and number of agents required." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Zammad GmbH`` or empty if not set" +#: ../system/subscription.rst:9 +msgid "" +"This setting section is only available for Hosted setups. If you're looking " +"for on premise support contracts, please see the `Zammad pricing page " +"`_." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Domain based assignment" +#: ../system/subscription.rst:14 ../system/subscription.rst:34 +msgid "Plan" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.domain_assignment}``" +#: ../system/subscription.rst:16 +msgid "" +"Here you can set up everything affecting your instance subscription " +"functions like number of agents and package." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > Domain" +#: ../system/subscription.rst:19 +msgid "" +"On top of the page you can find a subscription summary. You'll find the " +"number of used and available (booked) agent seats there. By using the *see " +"more* link you can also expand an agent list to see the currently configured " +"active agents. This list *does not* count accounts with admin permissions " +"only." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.domain}``" +#: ../system/subscription.rst:None +msgid "" +"Within subscription you can always see how many agents are still\n" +"available to add and who uses the seats." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``domain.tld`` or empty if not set" +#: ../system/subscription.rst:29 +msgid "" +"Learn more on how to manage your agents in general :doc:`here `." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Organization > VIP" +#: ../system/subscription.rst:36 +msgid "" +"This section gives you an overview of the available plans and their " +"functions / limits. If you require a more detailed table, check our " +"`detailed pricing table `_ for more." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.organization.vip}``" +#: ../system/subscription.rst:40 +msgid "" +"Your selection in this step will decide on the base agent price and e.g. " +"agent limits that might apply in the summary step." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Number" +#: ../system/subscription.rst:43 +msgid "" +"The green *Selected* button will also tell you what plan you're currently in." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.number}``" +#: ../system/subscription.rst:47 +msgid "" +"Trial instances are running at Professional with 3 agents. The plan cannot " +"be changed during the trial for technical reasons, if you require more " +"agents for testing, please contact `our sales team `_ with a reason for the raise request." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``31001``, ``201910731001``, ..." +#: ../system/subscription.rst:None +msgid "" +"Screenshot showing three available packages for a hosted Zammad\n" +"instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > ID" +#: ../system/subscription.rst:57 +msgid "" +"At the bottom of this block you can find a summary where you can adjust the " +"settings of the previous selected plan." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.id}``" +#: ../system/subscription.rst:62 +msgid "" +"Note that upgrading (more agents, higher package) is always possible, " +"however, downgrading will only happen when your billing period renews." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``17``, ``5281``, ..." +#: ../system/subscription.rst:66 +msgid "" +"Upgrading resets your billing period and existing credit will be deducted " +"from the new total." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact (customer)" +#: ../system/subscription.rst:75 +msgid "Billing cycle" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_customer_at}``" +#: ../system/subscription.rst:70 +msgid "" +"You can choose between either monthly or yearly billing. The price per agent " +"will be cheaper if you decide for yearly billing." msgstr "" -#: ../system/variables/ticket.rst:1 +#: ../system/subscription.rst:73 msgid "" -"``2019-10-07 16:25:00 UTC`` or empty if not applicable yet (Please note " -"`Ticket last contact behavior Settings `_ for this)" +"If you're still trying out things and are unsure of the right package for " +"your instance, you may want to choose monthly first and then upgrade to " +"yearly when you're sure." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact" +#: ../system/subscription.rst:83 +msgid "Plan: (Starter|Professional|Plus) - Agents" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_at}``" +#: ../system/subscription.rst:78 +msgid "Choose the number of agents you require for your instance." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Last contact (agent)" +#: ../system/subscription.rst:80 +msgid "" +"Keep in mind that some packages may have agent limits. Depending on the " +"previous chosen package, you won't be able to exceed specific agent numbers. " +"Also note that setting less agents than currently configured is not possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.last_contact_agent_at}``" +#: ../system/subscription.rst:86 +msgid "Total" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable yet" +#: ../system/subscription.rst:86 +msgid "This will be the net total you're going to be billed." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Note" +#: ../system/subscription.rst:88 +msgid "" +"By using the *Update subscription* button, the instance package will be " +"adjusted immediately. If you didn't provide a payment method yet, Zammad " +"will request you to provide one at this point." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.note}``" +#: ../system/subscription.rst:94 +msgid "" +"In case you're still within the trial period, this means that the trial will " +"be over immediately!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Note about this group``" +#: ../system/subscription.rst:97 +msgid "Down- or upgrading during the trial period *is not* possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Name" +#: ../system/subscription.rst:None +msgid "Screenshot showing payment options and a pricing summary" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.name}``" +#: ../system/subscription.rst:103 +msgid "Billing Information" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``Sales``" +#: ../system/subscription.rst:105 +msgid "" +"You can control all billing relevant information like invoices, billing " +"address and the option to cancel your subscription." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Follow-up possible" +#: ../system/subscription.rst:108 +msgid "" +"All adjusted billing information below only affect future invoices. If your " +"invoice was issued wrong, please contact `our sales team `_." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.follow_up_possible}``" +#: ../system/subscription.rst:114 +msgid "Billing address" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``no`` or ``yes``" +#: ../system/subscription.rst:113 +msgid "" +"Provide your company address here, make sure to include the companies name " +"in case required. This address will be referenced on your invoice." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Assign Follow-Ups" +#: ../system/subscription.rst:118 +msgid "VAT ID" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.follow_up_assignment}``" +#: ../system/subscription.rst:117 +msgid "" +"Provide your VAT ID here. If applicable your invoice will not contain German " +"VAT. Please make sure to pay the VAT in your country as required." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Group > Assignment Timeout" +#: ../system/subscription.rst:127 +msgid "Billing Email Address" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.group.assignment_timeout}``" +#: ../system/subscription.rst:121 +msgid "" +"Usually the instance owner (the person that registered the instance) will " +"receive all emails including the invoices. In case you have your own billing " +"department, you can provide their email address here." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``20`` or empty if not configured" +#: ../system/subscription.rst:125 +msgid "" +"All billing relevant information will then be sent to this email address." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > First response" +#: ../system/subscription.rst:127 +msgid "Invoices are sent as attachment (PDF) to this email address." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.first_response_at}``" +#: ../system/subscription.rst:129 +msgid "" +"Don't forget to press the *Update billing information* button after you " +"changed above settings." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Escalation at" +#: ../system/subscription.rst:None +msgid "" +"Screenshot showing options for billing information within the\n" +"subscription menu" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.escalation_at}``" +#: ../system/subscription.rst:137 +msgid "Payment Method" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``2019-10-07 16:25:00 UTC`` or empty if not applicable" +#: ../system/subscription.rst:139 +msgid "You can pay via credit card or SEPA mandate." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Web" +#: ../system/subscription.rst:144 +msgid "Credit card" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.web}``" +#: ../system/subscription.rst:142 +msgid "" +"Simply follow the dialogue by clicking *authorize credit card* and confirm -" +"if required by your bank- your consent to Zammad using your card for the " +"payments." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > VIP" +#: ../system/subscription.rst:148 +msgid "SEPA Direct Debit" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.vip}``" +#: ../system/subscription.rst:147 +msgid "" +"Provide the requested information of the bank account holder and update if " +"you're ready. You'll then receive an email with the SEPA mandate." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Phone" +#: ../system/subscription.rst:150 +msgid "" +"Technically there's also the possibility to pay via invoice, however - this " +"method only applies to a fairly low number of instances. Please contact `our " +"sales team `_ for more information." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.phone}``" +#: ../system/subscription.rst:156 +#, fuzzy +#| msgid "Description" +msgid "Cancel Subscription" +msgstr "描述" + +#: ../system/subscription.rst:158 +msgid "" +"Do you want to cancel your subscription? In case you no longer want to use " +"Zammad's SaaS, you can cancel your subscription by using the red *Yes, " +"please cancel my subscription* button." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Note" +#: ../system/subscription.rst:162 +msgid "" +"To cancel the description, enter the FQDN of your Zammad instance and " +"provide a reason for your cancellation." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.note}``" +#: ../system/subscription.rst:165 +msgid "" +"Your subscription will end the day after your trial or billing period ends." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Mobile" +#: ../system/subscription.rst:None +msgid "Screenshot showing subscription cancellation dialog" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.mobile}``" +#: ../system/subscription.rst:174 +msgid "" +"We will remind you about your cancelled subscription several times up front. " +"After the subscription ended all instance data will be removed. A restore " +"*is not* possible after that point!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Login" +#: ../system/subscription.rst:178 +msgid "**😖 Cancelled by accident?**" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.login}``" +#: ../system/subscription.rst:180 +msgid "" +"You can always undo the cancellation via the *Yes, undo the cancellation of " +"my subscription* button up to the last subscription day!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Lastname" +#: ../system/subscription.rst:0 +msgid "" +"Screenshot showing a red button to cancel the subscription\n" +"cancellation" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.lastname}``" +#: ../system/subscription.rst:189 +msgid "Payment History" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Firstname" +#: ../system/subscription.rst:191 +msgid "" +"The payment history will display a history of all paid invoices. At this " +"point you can also download these in case you need them again." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.firstname}``" +#: ../system/subscription.rst:196 +msgid "" +"You will only find *paid* invoices here. Invoices that are to be billed are " +"not available before the payment is completed." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Fax" +#: ../system/subscription.rst:201 +msgid "Date" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.fax}``" +#: ../system/subscription.rst:201 +msgid "Date of the invoice creation." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Email" +#: ../system/subscription.rst:204 +msgid "Amount" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.email}``" +#: ../system/subscription.rst:204 +msgid "Invoice total including VAT if applicable." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Department" +#: ../system/subscription.rst:207 +msgid "" +"Contains contract period (monthly or yearly) and hosted plan for the " +"subscription period in question." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.department}``" +#: ../system/subscription.rst:218 +msgid "Payment method / Service period" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Avatar" +#: ../system/subscription.rst:211 +msgid "" +"Used bank account or credit card as well as the subscription period the " +"invoice is about." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.avatar(60,60)}``" +#: ../system/subscription.rst:216 +msgid "" +"It might happen that the invoice date and subscription period differ. This " +"is nothing to worry about, the subscription periods will be accounted later " +"on." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Customer > Address" +#: ../system/subscription.rst:222 +msgid "Receipt" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.customer.address}``" +#: ../system/subscription.rst:221 +msgid "" +"Use the arrow to download the invoice in question. You can download all " +"available invoices any time you need to here!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Web" +#: ../system/subscription.rst:None +msgid "Screenshot showing payment history of a hosted instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.web}``" +#: ../system/subscription.rst:229 +msgid "FAQ" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > VIP" +#: ../system/subscription.rst:233 +msgid "I set up a trial account but am missing functions to test" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.vip}``" +#: ../system/subscription.rst:232 +msgid "" +"The trial instance is running within the professional package allowing up to " +"three agents." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Phone" +#: ../system/subscription.rst:236 +msgid "Can I change package within the trial?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.phone}``" +#: ../system/subscription.rst:236 +msgid "No. As soon as the package is changed the subscription begins." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Note" +#: ../system/subscription.rst:241 +msgid "What happens to my trial instance after the trial period ended?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.note}``" +#: ../system/subscription.rst:239 +msgid "" +"Your instance will automatically be canceled for you. Please see *What " +"happens to my instance after it has been canceled?* for more." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Mobile" +#: ../system/subscription.rst:254 +msgid "What happens to my instance after it has been canceled?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.mobile}``" +#: ../system/subscription.rst:244 +msgid "That depends slightly on your instance state:" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Login" +#: ../system/subscription.rst:250 +msgid "Trial instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.login}``" +#: ../system/subscription.rst:247 +msgid "" +"If you're still on trial, we will ice your instance and remind you once " +"again about your instance. We then will wait some days and remove your " +"instance from our system. This is the last time we will inform you by Email." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Lastname" +#: ../system/subscription.rst:254 +msgid "Paid instance" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.lastname}``" +#: ../system/subscription.rst:253 +msgid "" +"If you're a paying customer and canceled your subscription, the instance " +"removal will take place the day after your last subscription day." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Firstname" +#: ../system/subscription.rst:256 +msgid "Can removed instances be restored?" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.firstname}``" +#: ../system/subscription.rst:257 +msgid "No. Once your instance has been removed, a restoration is not possible." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Fax" +#: ../system/system-report.rst:2 +msgid "System Report" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.fax}``" +#: ../system/system-report.rst:4 +msgid "" +"In this place you can't configure Zammad. Instead you can obtain a system " +"report about Zammad and its configuration." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Email" +#: ../system/system-report.rst:7 +msgid "" +"See the description in Zammad for an explanation. You can even find a " +"preview of the included data below the **Download** button." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.email}``" +#: ../system/system-report.rst:10 +msgid "" +"Zammad never sends this automatically to anyone. It is a manual process only " +"to provide better support based on your configuration." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Department" +#: ../system/translations.rst:2 +msgid "Translations" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.department}``" +#: ../system/translations.rst:4 +msgid "" +"Translations of Zammad are processed centrally in our `Weblate instance " +"`_. This allows non-developers to review " +"and update translation texts of the language they actually speak." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Avatar" +#: ../system/translations.rst:9 +msgid "" +"Your language is in an incomplete translation state or has typos? Please " +"consider helping us in sorting this out! All you need is either a GitHub " +"account or to register directly in our instance." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.avatar(60,60)}``" +#: ../system/translations.rst:13 +msgid "" +"Did you know? This is also where the documentation translations are handled. " +"🤓" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created by > Address" +#: ../system/translations.rst:15 +msgid "" +"Have a look in our :docs:`contribution section ` in the system documentation to get started!" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_by.address}``" +#: ../system/translations.rst:20 +msgid "Local Translations" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Created at" +#: ../system/translations.rst:22 +msgid "" +"Apart from these system translations, there's still local translations you " +"can manage. This is relevant if you added custom objects that require " +"translations or even custom states and priorities." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.created_at}``" +#: ../system/translations.rst:None +msgid "Translation management screen within the admin menu" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "2019-10-07 16:25:00 UTC" +#: ../system/translations.rst:31 +msgid "Updating Translations" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "Ticket > Closing time" +#: ../system/translations.rst:33 +msgid "" +"Because of how Zammad ships translations, the only way to update the system " +"translations is to update your Zammad installation. The benefit of this is " +"that you no longer need internet access during a Zammad upgrade as the " +"package has everything it requires already." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``#{ticket.close_at}``" +#: ../system/translations.rst:39 +msgid "Translation of Custom Objects" msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "2019-10-07 17:25:00 UTC" +#: ../system/translations.rst:41 +msgid "" +"No problem at all! You can customize any translation locally, even if it is " +"not initially provided by the system." msgstr "" -#: ../system/variables/ticket.rst:1 -msgid "``3``, any number of articles existing in the ticket right now" +#: ../system/translations.rst:44 +msgid "" +"Translation is supported for a broad number of features, including but not " +"limited to custom:" msgstr "" -#: ../system/version.rst:2 -msgid "Version" +#: ../system/translations.rst:47 +msgid "Object Attributes" msgstr "" -#: ../system/version.rst:4 -msgid "Shows which version is currently being used on your Zammad-instance." -msgstr "显示当前在您的Zammad实例上使用的版本。" +#: ../system/translations.rst:48 +#, fuzzy +msgid "Ticket Macros" +msgstr "宏" -#: ../manage/roles/admin-permissions.rst:53 -msgid "``admin.checklist``" +#: ../system/translations.rst:49 +msgid "Ticket Overviews" msgstr "" -#: ../manage/roles/admin-permissions.rst:54 -msgid ":doc:`Manage > Checklist `" -msgstr "" +#: ../system/translations.rst:50 +#, fuzzy +msgid "Ticket Priorities" +msgstr "优先级" -#: ../manage/roles/admin-permissions.rst:83 -msgid "``admin.channel_whatsapp``" +#: ../system/translations.rst:51 +msgid "Ticket States" msgstr "" -#: ../manage/roles/admin-permissions.rst:84 -msgid ":doc:`Channels > Whatsapp `" +#: ../system/translations.rst:54 +msgid "Customizing Translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:124 -msgid "``admin.public_links``" +#: ../system/translations.rst:56 +msgid "" +"Within the translation screen, simply click on the **New Translation** " +"button." msgstr "" -#: ../manage/roles/admin-permissions.rst:125 -msgid ":doc:`Manage > Public Links `" -msgstr "" +#: ../system/translations.rst:None +#, fuzzy +msgid "New translation dialog" +msgstr "新建电子邮件账户对话框" -#: ../manage/roles/admin-permissions.rst:151 -msgid "``admin.system_report``" +#: ../system/translations.rst:62 +msgid "" +"In the dialog you can immediately enter the exact translation source (if you " +"know it) and your custom translation text for it and click **Submit**." msgstr "" -#: ../manage/roles/admin-permissions.rst:152 -msgid ":doc:`System > System Report `" +#: ../system/translations.rst:65 +msgid "" +"Alternatively, try to search for translation suggestions in the list below. " +"Selecting an item from the list will pre-fill the translation source for you " +"and then you can just enter your custom translation." msgstr "" -#: ../manage/roles/admin-permissions.rst:166 -msgid "``admin.ticket_auto_assignment``" +#: ../system/translations.rst:69 +msgid "" +"The target language will always default to your current language selection. " +"If you need to translate for a different language, simply change the " +"selection before submitting." msgstr "" -#: ../manage/roles/admin-permissions.rst:167 -msgid ":ref:`Settings > Ticket > Auto Assignment `" +#: ../system/translations.rst:73 +msgid "" +"All your custom translations will show up in the overview table when added. " +"And they will even persist across Zammad updates!" msgstr "" -#: ../manage/roles/admin-permissions.rst:169 -msgid "``admin.ticket_duplicate_detection``" +#: ../system/translations.rst:76 +msgid "" +"Make sure to reload your browser if a translated string is not displayed." msgstr "" -#: ../manage/roles/admin-permissions.rst:170 -msgid ":ref:`Settings > Ticket > Duplicate Detection `" +#: ../system/translations.rst:80 +msgid "Reverting to Original Translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:172 -#, fuzzy -msgid "``admin.ticket_priority``" -msgstr "优先级" - -#: ../manage/roles/admin-permissions.rst:173 -msgid ":ref:`System > Objects >Ticket Priority `" +#: ../system/translations.rst:82 +msgid "" +"If you want to revert a custom translation to original text, simply use the " +"appropriate action within the row of the overview table." msgstr "" -#: ../manage/roles/admin-permissions.rst:175 -msgid "``admin.ticket_state``" +#: ../system/translations.rst:85 +msgid "" +"Depending on the type of the translation source, the action has a slightly " +"different name:" msgstr "" -#: ../manage/roles/admin-permissions.rst:176 -msgid ":ref:`System > Objects >Ticket State `" +#: ../system/translations.rst:88 +msgid "**Reset** for customized system translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:193 -msgid "``admin.webhook``" +#: ../system/translations.rst:89 +msgid "**Remove** for customized local translations" msgstr "" -#: ../manage/roles/admin-permissions.rst:194 -msgid ":doc:`Manage > Webhook `" +#: ../system/translations.rst:91 +msgid "" +"In both cases, the action will remove the customized translation after a " +"confirmation." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:43 -msgid "``user_preferences.appearance``" +#: ../system/translations.rst:None +msgid "Screenshot showing the location of the Remove action" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:44 -msgid "Appearance configuration" +#: ../system/translations.rst:99 +msgid "Inline Translations" msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:0 -msgid "Users can switch between dark, light and" +#: ../system/translations.rst:101 +msgid "" +"If you prefer a more hands-on approach, you can activate the inline or on-" +"screen translation feature by pressing ``ctrl`` + ``alt`` + ``t`` at any " +"time and on any screen." msgstr "" -#: ../manage/roles/user-preferences-permissions.rst:0 -msgid "automatic mode." +#: ../system/translations.rst:105 +msgid "" +"All customizable translation texts will be highlighted for you on the " +"screen. Just click into the highlighted area and update the text in place." msgstr "" -#: ../system/system-report.rst:2 -msgid "System Report" +#: ../system/translations.rst:None +msgid "Inline translation mode activated for the Overview screen" msgstr "" -#: ../system/system-report.rst:4 +#: ../system/translations.rst:112 msgid "" -"In this place you can't configure Zammad. Instead you can obtain a system " -"report about Zammad and its configuration." +"When finished editing, simply press ``ctrl`` + ``alt`` + ``t`` again to " +"deactivate." msgstr "" -#: ../system/system-report.rst:7 +#: ../system/translations.rst:117 msgid "" -"See the description in Zammad for an explanation. You can even find a " -"preview of the included data below the **Download** button." +"Even though it's available on any screen, the inline translation feature " +"requires admin permissions. It works only for the current language " +"selection. If you need to translate a different language, first change the " +"language in your :user-docs:`profile settings `." msgstr "" -#: ../system/system-report.rst:10 -msgid "" -"Zammad never sends this automatically to anyone. It is a manual process only " -"to provide better support based on your configuration." +#: ../system/version.rst:2 +msgid "Version" msgstr "" +#: ../system/version.rst:4 +msgid "Shows which version is currently being used on your Zammad-instance." +msgstr "显示当前在您的Zammad实例上使用的版本。" + #, fuzzy #~ msgid "" #~ "Google is in the process of upgrading its security policies. To stay up-"